Fix empty OIDC config prevents fresh application from starting

Possibly due to the empty config? Added a quick fix for now.
Edit: See the issue now -- openid_connect_providers is expected to be a JSON string now. If AUTH_OIDC is missing from the env then the default of [] applies, which is an elixir list. Updated to use a default of "{}"

Pull Request Test Coverage Report for Build c584e041e8d577a0a3e195e1c33aeeefb9a57d4f-PR-846

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.05%) to 68.958%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

apps/fz_http/lib/fz_http/oidc/start_proxy.ex
0
1
0.0%

Totals

Change from base Build 99867ce3b1bf01daa3f00cd90bd77cb3e1a5710f:
-0.05%

Covered Lines:
993

Relevant Lines:
1440

💛  - Coveralls

Found this in the logs. Is this related? I thought it'd automatically migrate.
 Notice: 25_19:38:22.23938 19:38:21.368 [notice] Application fz_http exited: FzHttp.Application.start(:normal, []) returned an error: shutdown: failed to start child: FzHttp.Conf.Cache
2022-07-25_19:38:22.23942     ** (EXIT) an exception was raised:
2022-07-25_19:38:22.23943         ** (Postgrex.Error) ERROR 42P01 (undefined_table) relation "configurations" does not exist
2022-07-25_19:38:22.23943
2022-07-25_19:38:22.23943     query: SELECT c0."id", c0."logo", c0."local_auth_enabled", c0."allow_unprivileged_device_management", c0."openid_connect_providers", c0."disable_vpn_on_oidc_error", c0."auto_create_oidc_users", c0."inserted_at", c0."updated_at" FROM "configurations" AS c0
2022-07-25_19:38:22.23943             (ecto_sql 3.8.3) lib/ecto/adapters/sql.ex:932: Ecto.Adapters.SQL.raise_sql_call_error/1
2022-07-25_19:38:22.23943             (ecto_sql 3.8.3) lib/ecto/adapters/sql.ex:847: Ecto.Adapters.SQL.execute/6
2022-07-25_19:38:22.23943             (ecto 3.8.4) lib/ecto/repo/queryable.ex:221: Ecto.Repo.Queryable.execute/4
2022-07-25_19:38:22.23944             (ecto 3.8.4) lib/ecto/repo/queryable.ex:19: Ecto.Repo.Queryable.all/3
2022-07-25_19:38:22.23944             (ecto 3.8.4) lib/ecto/repo/queryable.ex:155: Ecto.Repo.Queryable.one!/3
2022-07-25_19:38:22.23944             (fz_http 0.5.0) lib/fz_http/conf/cache.ex:27: FzHttp.Conf.Cache.init/1
2022-07-25_19:38:22.23944             (stdlib 4.0.1) gen_server.erl:848: :gen_server.init_it/2
2022-07-25_19:38:22.23945             (stdlib 4.0.1) gen_server.erl:811: :gen_server.init_it/6

Found this in the logs. Is this related? I thought it'd automatically migrate.
 Notice: 25_19:38:22.23938 19:38:21.368 [notice] Application fz_http exited: FzHttp.Application.start(:normal, []) returned an error: shutdown: failed to start child: FzHttp.Conf.Cache
2022-07-25_19:38:22.23942     ** (EXIT) an exception was raised:
2022-07-25_19:38:22.23943         ** (Postgrex.Error) ERROR 42P01 (undefined_table) relation "configurations" does not exist
2022-07-25_19:38:22.23943
2022-07-25_19:38:22.23943     query: SELECT c0."id", c0."logo", c0."local_auth_enabled", c0."allow_unprivileged_device_management", c0."openid_connect_providers", c0."disable_vpn_on_oidc_error", c0."auto_create_oidc_users", c0."inserted_at", c0."updated_at" FROM "configurations" AS c0
2022-07-25_19:38:22.23943             (ecto_sql 3.8.3) lib/ecto/adapters/sql.ex:932: Ecto.Adapters.SQL.raise_sql_call_error/1
2022-07-25_19:38:22.23943             (ecto_sql 3.8.3) lib/ecto/adapters/sql.ex:847: Ecto.Adapters.SQL.execute/6
2022-07-25_19:38:22.23943             (ecto 3.8.4) lib/ecto/repo/queryable.ex:221: Ecto.Repo.Queryable.execute/4
2022-07-25_19:38:22.23944             (ecto 3.8.4) lib/ecto/repo/queryable.ex:19: Ecto.Repo.Queryable.all/3
2022-07-25_19:38:22.23944             (ecto 3.8.4) lib/ecto/repo/queryable.ex:155: Ecto.Repo.Queryable.one!/3
2022-07-25_19:38:22.23944             (fz_http 0.5.0) lib/fz_http/conf/cache.ex:27: FzHttp.Conf.Cache.init/1
2022-07-25_19:38:22.23944             (stdlib 4.0.1) gen_server.erl:848: :gen_server.init_it/2
2022-07-25_19:38:22.23945             (stdlib 4.0.1) gen_server.erl:811: :gen_server.init_it/6

Yeah but I think that is being cause by this timeout:

        ================================================================================
        Error executing action `run` on resource 'ruby_block[restart_log_service]'
        ================================================================================

        Mixlib::ShellOut::ShellCommandFailed
        ------------------------------------
        Expected process to exit with [0], but received '1'
        ---- Begin output of /opt/firezone/embedded/bin/sv restart /opt/firezone/service/wireguard/log ----
        STDOUT: timeout: run: /opt/firezone/service/wireguard/log: (pid 14411) 31s, got TERM
        STDERR:
        ---- End output of /opt/firezone/embedded/bin/sv restart /opt/firezone/service/wireguard/log ----
        Ran /opt/firezone/embedded/bin/sv restart /opt/firezone/service/wireguard/log returned 1

The weird thing is we haven't touched that recipe in a long time. I'm investigating what the issue could be...

🥳

🎉 🎉 🎉


Teams#show is displaying inaccurate data for each player

It shows the full stats for each player across all teams, rather than just that team.
Fix it. Also consider adding a stats table to the Players#show page that shows the accumulated stats.

Implemented 49eacf8a4fe27d25b94aa34a08a3b39fd10c7e60


missing file/folder permissions for local-path-provisioner

@mysticaltech found some missing permissions.

Thanks @maaft, awesome!


envoy.reloadable_features.enable_type_url_downgrade_and_upgrade deprecation

Your change #12913 (Support mixed v2/v3 xDS request/responses ) introduced a runtime guarded feature. It has been 6 months since the new code has been exercised by default, so it's time to remove the old code path. This issue tracks source code cleanup so we don't forget.

Sure, will clean it up!


add markdown version of saulo's schema with toc

This can be an external document linked in the README. Or it needs better formatting, it's possible to add comments in yaml file without turning it to a markdown.

i added it to the dmel-hsa branch


Exported variables don't update in real-time

Godot version:
3.2 mono
OS/device including version:
ubuntu 19.10
Issue description:
If you export variady read the bles using tool, and change their value, it is only updated when you click another node and the click back to the changed node.
Steps to reproduce:

Create 2 nodes: A and B
At B attach a script (can not be built-in)
code this:

tool
extends Node

export var a:int = 0
export var update:bool = false

func process(delta):
   if update:
        a = int(rand_range(0,100))
        update = false

Save scene close it and open again to take effects
Value is changed, you cant see
Click Node A
Click Back to Node B
Should see the change

Minimal reproduction project:
N/A

you need to call property_list_changed_notify() after changing the values to update the inspector.

This is currently intended behavior as pointed out by @mrcdk. reduz has plans to move from an observer system to polling, which should eliminate the need to call property_list_changed_notify() after modifying a property's value.

Related: #41697

A similar issue in #43238, but in this case property_list_changed_notify() doesn't work.

This should be resolved in the master branch since the inspector is now updated via polling.
We still need to document the need to call property_list_changed_notify() in tool scripts that modify exported variables.


Instructions to obtain 'panoimages.lmdb'

Hi, thanks for the great work! I wonder if there is any instructions on how to obtain the panoimages.lmdb file?

Hi, I uploaded the script to create the lmdb file here.


Can't install in Yosemite

This are the errors I get: https://gist.github.com/mrfoto/4dc512a19a23bc03e962
I found via Googling that @drnic had a very similar error, but doesn't describe how he fixed it https://gist.github.com/drnic/4210300
All other gems are installing normally, I have latest gcc
gcc -v
Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 6.0 (clang-600.0.54) (based on LLVM 3.5svn)
Target: x86_64-apple-darwin14.0.0
Thread model: posix

Hey @alexwoll, can you please try to clone my fork, build a gem via rake gem and install from pkg directory?

There is a recommendation that GeStalt should not be used on Yosemite. NSProcessInfo is recommended instead for OS name, version etc.
Are you going to accept patches to darwin_sigar.c with this change?
Thanks


Should we allow scale up/down on an inactive service using webhooks ?

**Rancher Version:**Master
**Docker Version:**1.12.3
**OS and where are the hosts located? (cloud, bare metal, etc):**Ubuntu, Cloud
**Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)**Single node
Environment Type: (Cattle/Kubernetes/Swarm/Mesos) Cattle
Steps to Reproduce:

Create a cattle setup with webhook enabled DEFAULT_CATTLE_WEBHOOK_SERVICE_EXECUTE=true

On an inactive service, should we allow a scale up/down ?

Currently, a token can be generated for an inactive service and we can scale up/down using the token. The scale goes up/down in the UI first. When the service becomes active, the number of containers get adjusted accordingly.

It makes sense to have webhooks for active services at this time. If the community finds value in this type, we could look into adding it in.


Sub-button: icon animation ?

Is it possible to put an animation on an icon in the sub_button?
like for example for a fan:
styles:
icon:
- animation: rotating 1.5s linear infinite
thank you to you.

Yes, you can. You have to apply the styling on the main bubble card, not in the sub-button editor. Here's an example of a fan that spins and turns blue when on.
.bubble-sub-button-5 > ha-icon {   color: ${hass.states['fan.bedroom_floor_fan'].state === 'on' ? 'rgb(33, 150, 243)' : ''} !important; } .bubble-sub-button-5 > ha-icon {   animation: ${hass.states['fan.bedroom_floor_fan'].state === 'on' ? 'slow-rotate 2s linear infinite' : ''}; } @keyframes slow-rotate {   0% { transform: rotate(0deg); }   100% { transform: rotate(360deg); } }

Yes, you can. You have to apply the styling on the main bubble card, not in the sub-button editor. Here's an example of a fan that spins and turns blue when on.
.bubble-sub-button-5 > ha-icon {
  color: ${hass.states['fan.bedroom_floor_fan'].state === 'on' ? 'rgb(33, 150, 243)' : ''} !important;
}
.bubble-sub-button-5 > ha-icon {
  animation: ${hass.states['fan.bedroom_floor_fan'].state === 'on' ? 'slow-rotate 2s linear infinite' : ''};
}
@keyframes slow-rotate {
  0% { transform: rotate(0deg); }
  100% { transform: rotate(360deg); }
}

Thank you for answering him! This is indeed the way 👌


[1.12] - Can't merge PR with API

Gitea version (or commit ref): 1.12.3
Git version: 2.28.0 (on my computer)
Operating system: MacOS / Linux
Database (use [x]):

[x] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[x] No (It works with try.gitea.io
[ ] Not relevant

Log gist:

Description
I'm not able to merge a PR via the API
あ→ curl -X POST "https://my.server.com/api/v1/repos/organization/myrepo/pulls/80/merge?access_token=mytoken" -H "accept: application/json" -H "Content-Type: application/json" -d "{ \"Do\": \"merge\", \"MergeMessageField\": \"string\", \"MergeTitleField\": \"string\", \"force_merge\": true}"

# On my server
[Macaron] 2020-08-16 08:35:22: Completed POST /api/v1/repos/organization/myrepo/pulls/80/merge?access_token=40571200ebb3e7a1144ae50898d5790b8bdd1b3a 405 Method Not Allowed in 118.893987ms

However, i made the test on try.gitea.io and it works perfectly..
curl -X POST "https://try.gitea.io/api/v1/repos/toto/test/pulls/1/merge?access_token=myToken" -H "accept: application/json" -H "Content-Type: application/json" -d "{ \"Do\": \"merge\", \"MergeMessageField\": \"string\", \"MergeTitleField\": \"string\", \"force_merge\": true}"

Is the version 1.13 fixing the issue ?

What is the server response?
All of our errors should give a JSON output: {"Message":"message", "URL": "url"}

There was not answer, it is why i were on my server to inspect the logs

@Tchoupinax if a InternalServerError ocure the API only will tell the error if it is in Devmode vor sec-reasons
so you either have to switch to devmode on the instance or look at the logs

Thank you for the tip !
But it appears that i have not returned answer with my issue.
When i change the name of my repo for a wrong name, i have the following issue
{"documentation_url":"https://my.server.com/api/swagger","errors":null,"message":"Not Found"}

When i remove one character in my token, i have the following issue
{"message":"Only signed in user is allowed to call APIs."}

But with the "correct" query, i have no returned answer. Always the same "405 Method not allowed" in the server logs. (And this query is copied from Swagger page :) )

Then you are getting the error reported from either L680:
https://github.com/go-gitea/gitea/blob/ec48618d40c12cc14e902062f6393ebeb9b0e365/routers/api/v1/repo/pull.go#L679
or L732 here:
https://github.com/go-gitea/gitea/blob/ec48618d40c12cc14e902062f6393ebeb9b0e365/routers/api/v1/repo/pull.go#L730-L734
So either the pr is not mergable yet, is already merged or is a work in progress, or the provided merge style is invalid. Not sure why that is the case at the moment.
Clearly those lines should report back which one is the problem - it's just bad form to not say.

Ok, thank you a lot for diving into the code. What i did not understand is that all seem to be good for the PR and when i click on the merge button with the UI, it works as expected.
My settings is configured as this

Maybe the "Do": "Merge" action in the payload means the "commit merging" action and like i deactivated it, it does not work. Should i do a "Do": "Squash" ? (I juste realized it)

Ok, it is that. I'm sorry to did not realize it before ><'
Maybe the action to improve this issue is to make a more specific log for this kind of error ?
Anyway it works well !

OK I'm going to close this issue - but I've sent a PR that should mean we return something a lot clearer in future.

Thank you a lot 👍


i am unable to apply skinTest.

i am trying to apply the the skin test but it shows that there is no function of such kind


Rename in line with pointfree convention

Rename the package and the repository in line with pointfree conventions for composable family of modules.
Bonus suggestion, tag an 0.1.0 release after?

Hi @andreyz, have you had the chance to test the current implementation of the wrapper?
Sounds good, I will add the tag

@Miiha was going to migrate fully to composable client today, but got sidetracked by other bugs. Will keep you updated, as I will start using it in production app from next week.


Pass block explicitly in define_method calls for PG instrumentation query methods

https://github.com/open-telemetry/opentelemetry-ruby-contrib/issues/570
"As a result of the fact blocks are captured by closures they cannot be passed implicitly to methods created with define_method; they must instead be passed explicitly using the define_method(meth) { |args, &block| ... } syntax."
from https://banisterfiend.wordpress.com/2010/11/06/behavior-of-yield-in-define_method/
This PR changes the "exec-ish" and "exec-prepared-ish" methods to all optionally handle an explicit block, with a new separate test file specifically for these PG::Connection patches.
This PR does not change the "prepare-ish" methods as those don't seem to return anything anyway.

@Capncavedan thanks again for your help!
Please review and sign the Easy CLA so that we may start the PR review process.

@arielvalentin done

Thank you. Did you happen to have the ability to test this in a sample app?
If so would you be able to share some screen shots of the fix in action?

@arielvalentin Only in the repro script so far.  This bug manifested up in a background process of ours, and we patched it to process its Postgres queries differently.
Apologies if this is already clear - the bug isn't affecting telemetry, rather one specific way of issuing Postgres queries using the PG gem.

Fantastic. I’ll incorporate feedback early next week (I’m out this week) and update the PR. -DanOn Jul 25, 2023, at 14:12, kaylareopelle @.***> wrote:
@kaylareopelle commented on this pull request.
This looks good to me once require 'active_record' is removed from the tests.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Thanks @arielvalentin !


Create a Sci-Fi Movie Fan Page

Pull Request Details:

Title: Create a Sci-Fi Movie Fan Page
PR Link: #17
Issue: #16

Next Steps:
I'm ready for feedback and any necessary revisions. Please review at your earliest convenience, and feel free to provide comments or suggest improvements.

Hi Samir,
Thank you for your pull request. I appreciate your contribution to our project.
I have reviewed your changes and everything looks good. Please be patient, and I'll get back to you as soon as possible.
If you have any questions or need further assistance, don't hesitate to ask.
Best regards,
Jayesh


Snapshot with more than a handful of lines

Describe the bug
As per https://github.com/vitest-dev/vitest/issues/3201  ( @sheremet-va suggested I report a new bug ) ...
I am experiencing a failed snapshot, but the vite reporter doesn't report more than a couple of lines of the snapshot diff, so I'm unable to tell what the test failed on.
Reproduction
The issue was observed in the Gitlab actions run at https://github.com/cefn/watchable/actions/runs/7088197269/job/19290116297?pr=55 and originates from the test suite source at https://github.com/cefn/watchable/blob/32630d4bb29e6ad3c6f1fa29b613b47ad2913b24/packages/nevermore/test/strategies/concurrency.test.ts#L50-L63
The too-terse console output looks like this in github...

However, in retrospect I think this could be my non-conformant use of toMatchInlineSnapshot().
The expanded snapshot string version was overwhelmed with whitespace making it impossible to read, so I switched it to a javascript array, which seemed functional until it failed only in github (with no good feedback from the snapshot error). The tests were passing when run locally.
But maybe this was never meant to work. To align with expectations, perhaps I should have switched the signature of toMatchInlineSnapshot() to be toEqual() after refactoring the snapshot from a string to an array.
Until this point I found the pattern of switching the snapshot string to be an array to be fine in practice, but this may be why the error serialization is wrong - if it (maybe correctly) makes a strong assumption that snapshot is a string not an array. Feel free to close if Javascript objects/arrays are non-conformant snapshots.
System Info
npx envinfo --system --npmPackages '{vitest,@vitest/*,vite,@vitejs/*}' --binaries --browsers
Need to install the following packages:
<EMAIL_ADDRESS>Ok to proceed? (y) y

  System:
    OS: macOS 13.5
    CPU: (10) arm64 Apple M1 Pro
    Memory: 83.50 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.9.0 - /opt/homebrew/opt/nvm/versions/node/v20.9.0/bin/node
    Yarn: 1.22.19 - ~/.asdf/shims/yarn
    npm: 10.1.0 - /opt/homebrew/opt/nvm/versions/node/v20.9.0/bin/npm
    pnpm: 8.6.11 - /opt/homebrew/opt/nvm/versions/node/v20.3.1/bin/pnpm
  Browsers:
    Chrome: 119.0.6045.199
    Edge: 119.0.2151.97
    Safari: 16.6

### Used Package Manager

npm

### Validations

- [X] Follow our [Code of Conduct](https://github.com/vitest-dev/vitest/blob/main/CODE_OF_CONDUCT.md)
- [X] Read the [Contributing Guidelines](https://github.com/vitest-dev/vitest/blob/main/CONTRIBUTING.md).
- [X] Read the [docs](https://vitest.dev/guide/).
- [X] Check that there isn't [already an issue](https://github.com/vitest-dev/vitest/issues) that reports the same bug to avoid creating a duplicate.
- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/vitest-dev/vitest/discussions) or join our [Discord Chat Server](https://chat.vitest.dev).
- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.

This is not the correct usage of toMatchInlineSnapshot - you need to generate the string locally and then publish it with a string.


Allow scene configs to be merged

Description:
It is currently not possible to use scenes inside packages. This PR adds a PLATFORM_SCHEMA field to scene/__init__.py so that it can be analysed and merged on boot. Existing tests still pass locally.
Related issue (if applicable): fixes #6641
Example entry for configuration.yaml (if applicable):
Scenes configuration stays the same as defined in https://home-assistant.io/components/scene/
Checklist:
If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] Tests have been added to verify that the new code works.

Hi @Chris-V,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

I added config validation for scenes for a closed PR. I think that is the correct way. You can copy that if you like:
https://github.com/MartinHjelmare/home-assistant/commit/416031f2b5bbf4b32e403c564158574e7dfd1ba4

Nice work and thanks a lot! I had very limited time this week to look at this :)
I can cherry-pick your commit in this branch or you can open another PR. This way credit is given where credit is due ;)

@Chris-V
Thanks. I've opened a PR with my rebased commit. If you can test the PR to make sure that scenes can be used with packages, that would be great.


JIT provisioning - Removing locally assigned user roles in APIM 3.2.0

Description:
Locally assigned roles get removed after performing JIT provisioning again for the same provisioned user.
Steps to reproduce:

Configure the WSO2 Identity Server 5.10.0 as an external IDP for the API Manager 3.2.0
Perform a JIT provisioning by log into a portal. User will create in the API Manager side.
Assign roles to the provisioned user on the API Manager side.
Again perform a JIT provisioning by log into a portal.
Check the user roles list that is assigned to the provisioned user and assigned local roles will get removed.

Affected Product Version:
3.2.0

public PR already merged with https://github.com/wso2/carbon-identity-framework/pull/3478/files. Hence closing.


Possible to add with or against on WL endpoint as query param?

https://docs.opendota.com/#tag/players%2Fpaths%2F~1players~1{account_id}~1wl%2Fget
On the WL command it is possible to get your WL with another player by using that query and the included_account_id command. Between those two things I can find out my record with Player A and B.  However it is impossible to determine if the player was on my team or the enemy team. So I might get back 10-15 as Win Loss. But it could be 7 wins as a teammate, and 3 wins as an enemy in which I won.
I propose adding a "teammate" flag that is true, false or null. Null keeps it as is, true would return the win loss as a teammate and false would return win loss as an enemy. The alternative to this is grabbing.....let's just say well over an order of magnitude worth of API calls to get the actual match histories and compare the teams.
Edit* Furthermore it is even confusing on the opendota website itself, as you can see here it says "My Record With" https://puu.sh/CRhTW/6849ec75c0.png In which you would assume based on that I have won 3 times that I have played with this person and lost once. But really if you click on that it shows I have lost with him once, and beat him 3 times. Which has a very different meaning.

I think we can achieve this by implementing with_account_id/against_account_id filters here:
https://github.com/odota/core/blob/master/util/filter.js#L41


Draft: Add Bubble Tea Dependency and TUI Commadn

What

Add a mint tui command
Add Bubble Tea as a dependency

Why

Setup the dependency for supporting a TUI for images
Propose potential initial entrypoint for supporting a TUI

How Tested

mint tui
Press up and down keys
Observe change in the number
Press q to quit

Testing Path Two:

mint
tui
Up & down keys
Press Q to return to mint CLI

Demo:
tui.zip

tui doesn't need to be exposed through the interactive prompt mode. The idea there is to have one or the other. It's ok to keep tui in the prompt mode. Not a big deal.

tui doesn't need to be exposed through the interactive prompt mode. The idea there is to have one or the other. It's ok to keep tui in the prompt mode. Not a big deal.

Would the preferred pattern be:
CLI: mint images --tui
CLI -> Interactive: mint images --tui
Then for debug I would follow the same pattern?
With this approach there would be no tui command. Only a flag per command with tui support.


Jumpy / Disappearing Content on Back Swipe

I'm experiencing issues with the content of my UITableViewController when swiping to go back. I am using a stock UITableViewController (subclass). Implementation is the same for both UITableViewController subclasses. iOS 8.1.2. Not using storyboard, all in code.
- (void)viewDidLoad {
    [super viewDidLoad];

    // Scrolling Nav Bar
    [self.navigationController.navigationBar setTranslucent:NO];
    [self followScrollView:self.tableView withDelay:60];
    [self setUseSuperview:YES];

    // ...
}

- (void)viewWillDisappear:(BOOL)animated {
    [super viewWillDisappear:animated];
    [self showNavBarAnimated:NO];
}

I tried changing [self setUseSuperview:YES]; to [self setUseSuperview:NO]; as mentioned in the README, but it looks like it messes up the content insets at the top.
In addition, sometimes navigation elements (title and right bar button) will disappear and then reappear when swiping to go back but letting it cancel, not sure if it is a related issue, but including it here.
Here is a video of the first issue in action: https://www.dropbox.com/s/jvgbhrzdaonuan2/IMG_1345.MOV?dl=0

Hi @nmock
Sorry for the massive delay. This should be related to #125


[BUG] "Problems" pane has wrong state on load (needs clicking twice if errors occur after loading)

See screenshot. I just gave some bad compiler arguments to a scratch which caused the compilation to fail, but the navigation would minimise the already-minimised panel

OK, the up/down behaviour seems to be based on the height of the window..
UP (correct):

DOWN (wrong!):

Which looks like it's deliberately doing something, but its not doing what I want.


urql should be peer dependency

urql should be a peer dependency of this package. Because the package has no "JS compilation step" (which it doesn't need), bs.module declarations like this:
https://github.com/FormidableLabs/reason-urql/blob/d31d0e508dd5dccb8ad6d495f1c6b1c75296ce72/src/UrqlClient.re#L135-L144
will be transpiled into naked import Urql from "urql" statements in a JS code base, which causes the bundler (webpack in my case) to look for urql in the project's top-level node_modules, which it won't find because urql is specified as a direct dependency instead of peer dependency. Specifying urql as a peer dependency reminds the developer to install urql alongside this package.

👋 Hey @huy-nguyen, thanks for opening an issue. urql used to be a peerDependency of this project, but we abandoned that strategy starting at v1. The major reason was that we couldn't guarantee that the bindings would be in lock step with the latest urql versions. For example, if a user did install urql as a peerDependency of reason-urql, they'd have to know exactly which version of urql is compatible with the version of the bindings they're using. And sure, they'll get a console warn about an incorrect version, but in my experience folks tend to ignore anything that isn't an outright failure in the install step.
Moreover, behavior changes upstream in urql across minor versions, so even if you're in the correct version range and the binding is correct, the underlying behavior on the JS side might have changed in an unexpected way. By binding to a specific version of urql, we can guarantee that our bindings are correct for that particular version, and that the user gets a particular version of urql on disk that we've verified works.
In response to your issue with imports, I haven't seen that behavior before. urql should be installed in your node_modules directory where reason-urql is installed, since both Yarn and npm will flatten dependencies of dependencies into node_modules directly. So if I have my-project with a dependency on reason-urql, node_modules for that project should have both reason-urql and urql at the top level (./node_modules/reason-urql and './node_modules/urql should both exist). If you have a monorepo setup or are using yarn workspaces that could change where things are installed, but the flattening of dependencies of dependencies into node_modules is standard behavior for Yarn and npm as far as I'm aware. Could you maybe shed more light on your architecture or provide a repo that reproduces the issue you're experiencing? Thanks!

@parkerziegler Thanks for the detailed explanation. You're right. I was working in a repo that uses yarn workspace. I tried installing reason-urql in a regular repo and it does install urql alongside it.


Update to remove Note for GCC

GCC deployment is out. Remove Note: For Teams for Government (GCC, GCC High, DoD), the limit is still 250. We'll update this article when the government cloud limit increases from 250 to 300 and supports meeting overflow.

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@LolaJacobsen PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

This is covered in PR 5475. I submitted after this was noticed to be duplicated. This PR can be closed.
Thanks,
Emily
From: Manuela Scanu<EMAIL_ADDRESS>Sent: Sunday, August 2, 2020 7:13 PM
To: MicrosoftDocs/OfficeDocs-SkypeForBusiness<EMAIL_ADDRESS>Cc: Emily Kirby<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/OfficeDocs-SkypeForBusiness] Update to remove Note for GCC (#5469)
@LolaJacobsenhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FLolaJacobsen&data=02|01|emkirby%40microsoft.com|9badff42c37d4302bf0608d83752ca91|72f988bf86f141af91ab2d7cd011db47|0|0|637320176010583448&sdata=XlNZRgl8afa3rIy%2Fz0KrLtUNTXmrgTkP%2FtbmVCMluM4%3D&reserved=0 PR has been copyedited and is ready for final review, could you please check and merge? Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FOfficeDocs-SkypeForBusiness%2Fpull%2F5469%23issuecomment-667766774&data=02|01|emkirby%40microsoft.com|9badff42c37d4302bf0608d83752ca91|72f988bf86f141af91ab2d7cd011db47|0|0|637320176010583448&sdata=TM%2Bpty0ObbuKeGwChSkI1L0oduj99YfoMkVygTKmqOs%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJCRYP4OVSE2TTEA3HDGIE3R6YML7ANCNFSM4PO2HFHA&data=02|01|emkirby%40microsoft.com|9badff42c37d4302bf0608d83752ca91|72f988bf86f141af91ab2d7cd011db47|0|0|637320176010593446&sdata=LvrHwnUic0pZQOLZcVHdKnomS8cSlDKidE19eaqJC%2FI%3D&reserved=0.

Hi, @emilykirby - per your instructions above, I'm closing this one (without merging).


Does the new version in the github still cant't be installed by pip?

The new version of the source code in the current github  support 2 dimensional shape feature,but we install the version of pyradiomics  installed by pip is sitll 2.1.2 which doesn't support 2 dimensional shape feature.If the only method to install the latest vertsion is install by source?Thanks

The 2d shape feature can't be found in the document,by in the source code ,there is Shape2d.py

@johnyanchen, that is correct. On pip, only the official releases of PyRadiomics can be installed, and the shape2D features were only added after that last release (next release is coming soon though).

documentation for the shape2D features have now also been added to the online documentation


RuntimeError: Unknown model (pretrain_mae_base_patch16_224)

Hi, guys, thanks a lot for a such good paper.
I wanted to investigate your model, but faced with mentioned in the title error from timm when I tried to run Pretrain/VideoMAE/run_mae_vis.py

and yes, I have not found timm==0.4.8 only 0.4.12

It's in Pretrain/VideoMAE/modeling_pretrain.py.
For timm, you can use pip install timm==0.4.8

Hmm, thanks for your answer, will try!

Hi, thanks for your great work.
I met the same error when I try to  run  run_videomae_vis.py, and I get the error below:
RuntimeError: Unknown model (vit_huge_patch16_224)

and I try
pip install timm ==0.4.8

but get the error below:
ERROR: Could not find a version that satisfies the requirement timm==0.4.8 (from versions: 0.1.1, 0.1.2, 0.1.4, 0.1.6, 0.1.8, 0.1.10, 0.1.12, 0.1.14, 0.1.16, 0.1.18, 0.1.20, 0.1.22, 0.1.24, 0.1.26, 0.1.28, 0.1.30, 0.2.1, 0.3.0, 0.3.1, 0.3.2, 0.3.3, 0.3.4, 0.4.5, 0.4.9, 0.4.12, 0.5.4, 0.6.2.dev0, 0.6.5, 0.6.7, 0.6.11, 0.6.12, 0.8.0.dev0, 0.8.2.dev0, 0.8.3.dev0, 0.8.6.dev0, 0.8.10.dev0, 0.8.11.dev0)
ERROR: No matching distribution found for timm==0.4.8

think this may be a Python version issue. Try updating to the another Python version.


infra: deploy to AWS

Ref: https://github.com/metriport/metriport-internal/issues/228
Dependencies

Upstream: https://github.com/metriport/metriport/pull/113
Downstream: https://github.com/metriport/metriport-internal/pull/371

Description

Create infra on AWS to publish ECR image
Create script to build and publish Docker image on AWS ECR
Create infra on AWS to deploy the FHIR server
Update README

⚠ CI/CD (ECR and ECS) to be done on an upcoming PR
Release Plan

already deployed on staging, when the PR is ready to review it can be merged into develop at any time
the merge into master needs to be coordinated

upstream needs to be merged/deployed into production before this
manually deploy the BaseStack on production
get the ECR address to be used on deploy-to-ecr.sh
publish the docker image on ECR - for production:

./deploy-to-ecr.sh -r us-west-1 -g <ECR-ADDRESS> -p metriport/fhir-server

deploy into production (get the ECS/Fargate image pointing to the latest image on ECR):

cdk deploy -c env=production FHIRServerStack

By the way, the FHIR server is working on staging, I just didn't update our Org on CW to point to api.staging.metriport.com instead of fhir.staging.metriport.com because of the debugging being done to figure out the issue with Document Retrieval.
If it start to take long, we can let them know the environment was updated and now the URL is different.


Set up Testcontainers for intergation tests

Done in https://github.com/jczuchnowski/zio-pulsar/commit/8cc685a4fd16a8fd3474038522bf98ac273fa3c9


Running Dagda in RHEL 7.2 and Fedora 22 not supported

Elias, i linked the new issue with the last one comment, i've expanded the information:
https://github.com/eliasgranderubio/dagda/issues/8#issuecomment-288339071
Thanks in advance.

Hi @scumfrog,
I would need more info for fixing de issues, so I comment you the next steps:

I have detected in Fedora > 22 that sometines the error Runtime error opening device /host/dev/sysdig0. occurs. I don't known the real reason but at the moment, a workaround will be install Sysdig as requirements:

How to Install Sysdig for Linux

I can't found where the DagdaError shown in the log trace is thrown <2017-03-22 09:46:40,371> <ERROR> <DagdaServer> <analyzer> <Unexpected exception of type DagdaError occured: ()> so, could you remove the try-except in https://github.com/eliasgranderubio/dagda/blob/master/dagda/analysis/analyzer.py#L55and attach me the stack trace?

Could you attach me the linux_distro result that you get in https://github.com/eliasgranderubio/dagda/blob/master/dagda/analysis/runtime/sysdig_falco_monitor.py#L58

Regards.

Hi @eliasgranderubio ,
Thanks for your answer. I followed your suggested steps, and apparantly, works, but when i run the analysis, the exception appers again:
<2017-03-22 11:37:35,375> <ERROR> <DagdaServer> <analyzer> <Unexpected exception of type DagdaError occured: ()>
But with sysdig installed, the last errors:
<2017-03-22 09:40:51,818> <ERROR> <DagdaServer> <dagda_server> <Runtime error opening device /host/dev/sysdig0.>
<2017-03-22 09:40:51,818> <WARNING> <DagdaServer> <dagda_server> <Runtime behaviour monitor disabled.>

dont happen again, so, good point for this workaround.
Trying to comment the try-except on analyzer.py but i cant get the stack trace, maybe for ignorance:
        # Get programming language dependencies
        dependencies = None
        #try:
            dependencies = dep_info_extractor.get_dependencies_from_docker_image(self.dockerDriver, image_name)
        #except Exception as ex:
            message = "Unexpected exception of type {0} occured: {1!r}".format(type(ex).__name__,  ex.args)
            DagdaLogger.get_logger().error(message)
            data['status'] = message

Could you help me with that?. For the falco_monitor output, here it is (for RHEL. Is where the issue appears):
>>> import platform
>>> platform.linux_distribution()
('Red Hat Enterprise Linux Server', '7.3', 'Maipo')

If you want to try me another method, tell me. I used platform.linux_distribution() instead of get_linux_distro(), but i think that the output is the same.
Thanks in advance.

@eliasgranderubio sorry for the double post. After the last post, anyway, i checked the report of the analysis that i run (despite the error), and looks good. The report works, but at the end of it, the "Unexpected exception of type DagdaError occured:" appears:
python3 dagda.py history image_example --id 58d2557f08540e11ae7f6376
[
{
"id": "58d2557f08540e11ae7f6376",
"image_name": "registry.lvtc.gsnet.corp/produban/wordpress",
"static_analysis": {
"os_packages": {
"ok_os_packages": 193,
"os_packages_details": [
{
"is_vulnerable": false,
"product": "acl",
"version": "2.2.52",
"vulnerabilities": []
},
-----CUT-----
{
"is_vulnerable": true,
"product": "bash",
"version": "4.3",
"vulnerabilities": [
"CVE-2014-6271",
"CVE-2014-6277",
"CVE-2014-6278",
"CVE-2014-7169",
"CVE-2014-7186",
"CVE-2014-7187",
"CVE-2016-7543",
"BID-70152",
"BID-92337",
"BID-92999",
"BID-93183"
]
},
-----CUT-----
},
"status": "Unexpected exception of type DagdaError occured: ()",
"timestamp": "2017-03-22 10:44:36.834589"
}
]
Thanks in advance,

The error shown below with Red Hat distributions already should not appears. Please, check it when you can and give me feedback.

<2017-03-22 10:04:35,305> <ERROR> <DagdaServer> <dagda_server> <Linux distribution not supported yet.>
<2017-03-22 10:04:35,305> <WARNING> <DagdaServer> <dagda_server> <Runtime behaviour monitor disabled.>

On the other hand, the status field in the report always shows the analysis status, that is way, if an error is thrown, the error will be the status value. In this case, DagdaError is only thrown when there is a problem with the deepfenceio/deepfence_depcheck docker image so:

What is your docker version?

When you run a new static analysis for <image_name>, if DagdaError occurrs, have you the /tmp/depcheck/<image_name> file?

Hello @eliasgranderubio
That's right, the previous error has not reappeared in RHEL, but i think that now i've another problem with the json parsing. After i pull again the project, i try populate the database, but new error appears (looks like fail with JSON parsing):
# python3.6 dagda.py vuln --init

Traceback (most recent call last):
  File "dagda.py", line 125, in <module>
    main(DagdaCLIParser())
  File "dagda.py", line 121, in main
    print(json.dumps(json.loads(r.content.decode('utf-8')), sort_keys=True, indent=4))
  File "/usr/lib64/python3.6/json/__init__.py", line 354, in loads
    return _default_decoder.decode(s)
  File "/usr/lib64/python3.6/json/decoder.py", line 339, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib64/python3.6/json/decoder.py", line 357, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

and again, reappared the sysdig/falco error:
<2017-03-23 09:49:24,687> <ERROR> <DagdaServer> <dagda_server> <Sysdig/falco output file not found.>
<2017-03-23 09:49:24,687> <WARNING> <DagdaServer> <dagda_server> <Runtime behaviour monitor disabled.>

solved with sysdig installation in RHEL too.
About your anwsers:
What is your docker version?

Fedora22:

# docker -v
Docker version 1.12.6, build ae7d637/1.12.6

RHEL 7.2:

# docker -v
Docker version 1.13.1, build 092cba3

Have you deepfenceio/deepfence_depcheck docker image if you run docker images

Fedora 22: YES

[root@breaknoise dagda]# docker images
REPOSITORY                                    TAG                 IMAGE ID            CREATED             SIZE
dadga                                         latest              fa45d790e89b        7 days ago          102 MB
docker.io/mongo                               latest              686238c7a975        3 weeks ago         402.1 MB
docker.io/golang                              1.8-alpine          0c838a44ab05        4 weeks ago         257.3 MB
docker.io/postgres                            latest              ecd991538a0f        5 weeks ago         265.4 MB
**docker.io/deepfenceio/deepfence_depcheck      latest              d7dc7da5d883        8 weeks ago         915 MB**
docker.io/python                              3.4.5-alpine        0eb0091592b3        12 weeks ago        82.36 MB
docker.io/sysdig/falco                        latest              285353e9835d        3 months ago        346 MB

RHEL 7.2: NO

[root@ansible-security dagda]# docker images
REPOSITORY                                      TAG                 IMAGE ID            CREATED             SIZE
mongo                                           latest              686238c7a975        3 weeks ago         402 MB
mysql                                           latest              7666f75adb6b        7 weeks ago         406 MB
postgres                                        latest              4023a747a01a        2 months ago        265 MB
sysdig/falco                                    latest              285353e9835d        3 months ago        346 MB
When you run a new static analysis for <image_name>, if DagdaError occurrs, have you the /tmp/depcheck/<image_name> file?
No, i just test running another analysis (in F22), and before and after execution the tmp file has not create.
Thanks in advance,

I can't reproduce any of your errors and I think we are mixing several issues in the same issue, so I propose you the next steps:

Remove the deepfenceio/deepfence_depcheck image manually with docker rmi command.
Remove the vuln_database database in your MongoDB (or drop all collections manually)
Ensure that you up-to-date with master branch.
Remove the try-except in https://github.com/eliasgranderubio/dagda/blob/master/dagda/analysis/analyzer.py#L55 before start the server. This will allow us review if there is any problem with deepfenceio/deepfence_depcheck docker image in your system.
Start Dagda and populate the database with CLI (review if any error occurs in the server log or CLI log)
Run a static analysis with any image that you have and review logs for errors again.

Important to note: Omit any error from sysdig or runtime  behaviour monitor. At the moment, we focus on static analysis in both F22 and RHEL7.

Following your suggestion, i restart with a fresh install of the enviroment (for Fedora 22). Then i clone the master branch of Dadga, pull the mongo image from docker.io (BTW, exist a new "bug" in mongo docker image solved by adding "-t" option to docker run). I started the server (at first without removing the try-except), populate the database with CLI and run an static analysis and the exception has happened again:
<2017-03-24 08:18:47,908> <ERROR> <DagdaServer> <analyzer> <Unexpected exception of type DagdaError occured: ()>
I checked the deepfence_depcheck docker log, maybe is usefull:
# docker logs 2d409b8d40f7
mkdir: cannot create directory '/tmp/depcheck': Permission denied
# ------------------------------------------------------------------------------
# OWASP Dependency Check for Container Images, v 0.1
# Running with following config
#
# Container image               = docker.io/mongo
# Scan type                     = all
# Proxy                         = none
# Debug messages logged to      = stdout
# Vulnerabilities logged to     = stderr, /tmp/depcheck/docker.io_mongo
# DB update                     = false
# Databases stored at           = /tmp/dependency-check, /tmp/.retire-cache
# JSON pretty printing          = true
# ------------------------------------------------------------------------------

tee: /tmp/depcheck/docker.io_mongo: No such file or directory
[INFO] OWASP Dependency Check is building initial database
[INFO] Retirejs is building initial database
[INFO] Saving docker.io/mongo
[INFO] Could not save image, error mkdir /tmp/tmpdir-725111738: permission denied

Before this, i've tried again, this time with this steps:

removing at firts all the images and containers:

docker rm $(docker ps -a -q)
docker rmi $(docker images -q)

commented the try-except from: https://github.com/eliasgranderubio/dagda/blob/master/dagda/analysis/analyzer.py#L55
Then i started the server, populate the BBDD, run a new analysis and surprisingly, it runs ok:

[
    {
        "id": "58d4cd7908540e240b270b24",
        "image_name": "docker.io/mongo",
        "static_analysis": {
            "os_packages": {
                "ok_os_packages": 104,
                "os_packages_details": [
                    {
[Omitted results]
                ],
                "total_os_packages": 113,
                "vuln_os_packages": 9
            },
            "prog_lang_dependencies": {
                "dependencies_details": {
                    "java": [],
                    "js": [],
                    "nodejs": [],
                    "php": [],
                    "python": [],
                    "ruby": []
                },
                "vuln_dependencies": 0
            }
        },
        "timestamp": "2017-03-24 07:40:53.061618"
    }
]

I'm going to try on RHEL and I'll tell you. Anyway, any more suggestion for F22? With the workaround, have not I removed functionality of dagda? Thanks in advance @eliasgranderubio

Hi @eliasgranderubio
I created a clean installation (installing a new docker service, packages, python3.4 from EPEL repos for more compatibility) of RHEL 7.2 but i'm facing the same problem:
Traceback (most recent call last):
  File "dagda.py", line 125, in <module>
    main(DagdaCLIParser())
  File "dagda.py", line 121, in main
    print(json.dumps(json.loads(r.content.decode('utf-8')), sort_keys=True, indent=4))
  File "/usr/lib64/python3.4/json/__init__.py", line 318, in loads
    return _default_decoder.decode(s)
  File "/usr/lib64/python3.4/json/decoder.py", line 343, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib64/python3.4/json/decoder.py", line 361, in raw_decode
    raise ValueError(errmsg("Expecting value", s, err.value)) from None
ValueError: Expecting value: line 1 column 1 (char 0)

Do you prefer open a new issue more specific and close this one? In the end, in F22 works, and the error, are not related to supported OS. Thanks in advance.

If it works in F22, that is a good new :-). Anyway, the mkdir: cannot create directory '/tmp/depcheck': Permission denied error sometimes occurs because this directory was created with diferent ownership and only if you delete it, the problem will be fixed.
The other issue that you have in RHEL is not related with the OS, so I create a new issue for fixing it.
Finally, if you confirm me that F22 problems shown in this issue are fixed, I will close this issue ;-).

Yes, i think that @eliasgranderubio. I close the issue. Anyway, im continue digging with the RHEL issue. I keep you informed. Thanks for your help :+1:

I've just create the new issue for fixing your RHEL problem.


cmd/link: request backport for ppc64le linker fix to go 1.8

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go 1.8.3
What operating system and processor architecture are you using (go env)?
Ubuntu ppc64le
A fix went upstream related to linking programs on ppc64le, affecting the build of very large programs as are found in Kubernetes and openshift.  I'm requesting to backport this fix to the go 1.8 branch so it is in a go1.8.x, since many builds are still using go 1.8.x and will continue to use that version for a while.
The issue is #20497 fixed by CL  45130.  If this is approved, I can take care of doing the backport.

I'll let @ianlancetaylor decide.
But we may be closed enough to Go 1.9 that the answer might be to wait.

I think it's OK to backport the CL for 1.8, but it's not enough to trigger a 1.8.4 release.  We may never do a 1.8.4 release.  I would suggest preparing the CL at your leisure, but don't commit it to the branch.

@jcajka The above CL is the Go 1.8 backport of the fix for openshift on ppc64le.

CL 45130 OK for Go 1.8.5.
It won't apply cleanly but this will be a good test.

go1.8.5 has been packaged and includes:

CL 70837

The release is posted at golang.org/dl.
— golang.org/x/build/cmd/releasebot, Oct 26 21:07:49 UTC


Mention html-to-react-components to start fresh boilerplate

https://github.com/roman01la/html-to-react-components

Also interesting to mention http://jxnblk.com/rebass/

I think this should be renamed to tips for React starter :)

Also mention flexbox polyfill.
https://github.com/10up/flexibility (There is no reason for me to not learning flexbox anymore)

Also http://jxnblk.com/reflexbox/


Add rust coverage data to coverage CI collection

Summary
This commit expands the existing coverage data collection for the github
actions coverage job to also include rust source coverage. To accomplish
this we need to build the qiskit-terra compiled extension with the rust
instrument-coverage compiler flag to instrument the binary. Then we use
grcov to generate an lcov file from the collected coverage data and
finally we combine the lcov files from rust and python into a single
file and upload that to coveralls. Ideally this will enable us to ensure
our python unittests provide sufficient coverage of compiled code in
Qiskit and highlight any potential gaps in test coverage.
Details and comments

Hmm, the coverage collection is "working" but only showing data from the import/module interfaces and none of the code executed. So something isn't quite working with the coverage collection on the rust binary. I'll do some investigation to try and figure out what's missing.

This is working for the unittest run, but the coverage collection isn't working when we run the second script tools/verify_parallel_map.py So the coverage data is missing the branches where we don't run in parallel. Almost there...


Error

687   flowtemp = {'q_gas' : q_gas, 'q_ch4' : q_ch4}
688   result = pd.concat([gasflow, flowtemp], ignore_index=True)
TypeError: cannot concatenate object of type '<class 'dict'>'; only Series and DataFrame objs are valid

I'm not sure of the exact version of Python and Pandas in which this behavior was changed to cause an error, but it's something I fixed in my fork of the project.


Install error on Eagle

After creating a conda environment in a bash file with
conda create -y --prefix "$MY_CONDA_PREFIX" -c conda-forge "pyarrow>=0.14" python=3.8 pandas

and then running
source activate "$MY_CONDA_PREFIX"

"$MY_CONDA_PREFIX/bin/pip" install git+ssh://git@github.com/NREL/jade.git@master

failed with the error:
Building wheels for collected packages: jade
  Building wheel for jade (PEP 517) ... done
  Created wheel for jade: filename=jade-number-py3-none-any.whl size=114672 sha256=ddccba07aa1db7671c99784e225d4ea88c8115b2113d81514ebce2e8050af0ee
  Stored in directory: /tmp/pip-ephem-wheel-cache-sbm3pkdc/wheels/d6/9e/64/c80fa3dc911ba0a566d6d10df981758756998f916ee6e9876d
  WARNING: Built wheel for jade is invalid: Metadata 1.2 mandates PEP 440 version, but 'number' is not
Failed to build jade
ERROR: Could not build wheels for jade which use PEP 517 and cannot be installed directly

pip install git+ssh://git<EMAIL_ADDRESS>
gave the same error:
Building wheels for collected packages: jade
  Building wheel for jade (PEP 517) ... done
  Created wheel for jade: filename=jade-number-py3-none-any.whl size=114602 sha256=ab2cd57cbb2e0ff80df4df81a447bf0e820eb492a4f39be434a601103ba9a67f
  Stored in directory: /tmp/pip-ephem-wheel-cache-jqwa3fje/wheels/12/f2/48/57c45f6357e101c1b54f91fd454851e440224f091b7cf5131c
  WARNING: Built wheel for jade is invalid: Metadata 1.2 mandates PEP 440 version, but 'number' is not
Failed to build jade
ERROR: Could not build wheels for jade which use PEP 517 and cannot be installed directly

Going back to v0.1.3 works--it installs with a warning. I do not know why this older version succeeds but the newest ones do not:
Building wheels for collected packages: jade
  Building wheel for jade (setup.py) ... done
  Created wheel for jade: filename=jade-number-py3-none-any.whl size=91158 sha256=05680fa37981a686a60d6c65374c05f1f2c04ed85cffdf3095a7ecb62acd11c7
  Stored in directory: /tmp/pip-ephem-wheel-cache-5onw1e37/wheels/a3/c5/ee/14e1b06fb6bf1362e947da1b811d8164049568c26ead0bcb9d
  WARNING: Built wheel for jade is invalid: Metadata 1.2 mandates PEP 440 version, but 'number' is not
Failed to build jade
Installing collected packages: scipy, patsy, numexpr, kiwisolver, cycler, toml, tables, statsmodels, pyyaml, psutil, prettytable, matplotlib, filelock, feather-format, click, jade
    Running setup.py install for jade ... done
  DEPRECATION: jade was installed using the legacy 'setup.py install' method, because a wheel could not be built for it. A possible replacement is to fix the wheel build issue reported above. You can find discussion regarding this at https://github.com/pypa/pip/issues/8368.

Installing v0.2.8 works for now, with the same warning as v0.1.3

@elainethale did you try using just 'conda activate' in the .sh file? conda activate causes me errors but perhaps the opposite is occurring here where 'source activate' is causing you errors? I was able to install JADE fine in my new environment with the "$MY_CONDA_PREFIX/bin/pip" install git+ssh://git@github.com/NREL/jade.git@master" line in the .sh file.

I didn't hit the "Unable to activate" error in our install script, and in any case, my additional tests with the other versions were just done on the command line, after the environment was activated. The error was replicated there, in addition to showing up when I ran our install script.

I'm fairly clueless on Python package management and not sure what is wrong yet. This worked for me. I'll look for a proper fix.
pip install<EMAIL_ADDRESS>--no-use-pep517 jade

This problem was introduced in v0.2.9 because I added pyproject.toml (in order to use the black formatting tool) without specifying the build system correctly. I removed the file until I have time to figure out how to do it properly. Now, pip install<EMAIL_ADDRESS>will work, but will give a warning message and a deprecation message. I'll leave the issue open until I properly fix it.
Sorry for the trouble.

This is now fixed.
pip install<EMAIL_ADDRESS>


HOW TO COMPILE a modification i the project??

How can I modify something and build? I have run "ng build" or "ng build --configuration=production" but I am getting the same error. Kip is not showing anything, just WHITE PAGE./ I click to "inspect" and show this error:
main.js:1 Uncaught TypeError: Cannot read properties of undefined (reading 'production')
at 5974 (main.js:1:64836)
at n (runtime.js:1:128)
at main.js:1:64914
at f (runtime.js:1:698)
at main.js:1:49
Thanks!!! : )

If you simply want to run locally to code, from the project root folder (kip folder) run command npm run-script start. To build a NPM release package use npm run-script build-npm.

Please don't spam all users!

I am just a bit desesperated.... Thank you @godind :)

i keep facen same issueee....  :(

You are running it from the  Signal K server?
What are you trying to do? What step?
First question before talking about deployment is can you run and test in your development IDE?
Tell me what tools and OS you are using.

Okey.
I installed Kip from Signalk but I want to do some modifications to it. Like colors in themes etc...
As I saw this repo in github I downloaded all the project and replace all the content of /.signalk/node_modules/@mxtommy/kip with what there is currently here in master, https://github.com/mxtommy/Kip
When I did this replce everything is fine, now I have this new version of kip runninf from signalk .
Now I want to do the updates. So I started changing a small thing , like for example a label of some html file, and I wanted to build it so I know I can do updates to the project and deploy them...
However when I do the npm run npm-buil and I go again to the endpoint of kip ,now everythin is in white, I go to inspect and see the error I mentioned before..  :(

You can't publish to KIP master branch or work from the installed KIP folders on your SK server. It won't work and anytime you want to keep up with KIP releases you will loose everything. Have a look the the KIP read me Instructions.
To build on Projects like KIP you need to fork the project to your own github repo.
Then using a development software (an IDE) such as VS Code (free), connect to your repo and check out your master locally. Once done, create a working branch from your master branch, check out and work on it. Once you are happy, merge your working branch onto your master, then make a pull request to KIP repo. We will review and merge into the product.
Use the


Validate prop not accessible in field custom component

I'm using redux-form: "7.1.2"
import CustomComponent from 'custom-component'
import { required } from 'validation';

<Field
component={CustomComponent}
name="firstname"
validate=[required]
/>

When I'm trying to access props in CustomComponent by this.props but validate prop is not available in CustomComponent.
What I want:
Which validation functions are applied to firstname field

Yes we can pass custom props to field and that will be available in CustomComponent.
But in my case, I've used Field multiple times at different places so instead of passing custom prop to each field Is there any way to access validate prop in CustomComponent. (because validate is already defined in each component)

@gustavohenke : I also got the same problem...Any solution ?

I agree, having to do something like the example bellow is not optimal.
<Field
  component={CustomComponent}
  name="firstname"
  validate={[required()]}
  required
/>

It would be nice if the validate props would be given to the custom field. In my case, I cannot add an asterisk for required Field. I could create an HOC for the Field component but I think it should be given to the custom field to manage different rendering regarding the validation. The required props could be given as meta if there is a required in the validate props but it doesn't cover others use cases.


Use git-worktree when relevant

This allows to share git objects between workspaces (and repos).
This would be a huge performance boost :)

This project has moved. See the matching issue at : https://gitlab.com/tsrc2/tsrc/-/issues/66

This project has moved. See the matching issue at : https://gitlab.com/tsrc2/tsrc/-/issues/66


widget_utils: use correct variable to clear interval

Hi
A clock I'm developing is using hideable widgets. I've noticed that every now-and-then the clock stops updating after showing the widgets. I'm using an interval (not timeout) to update the clock.
I think I found the culprit.

Thanks for spotting this! That's great to get sorted.
And no, unfortunately we can't bump the version - so we'd just have to wait until apps get updated/reinstalled.

Maybe the app loader could keep track of the latest date when an app was installed and when modules were last updated on github. With those data the user could be informed about apps that would benefit from being reinstalled.

So, when/how is this module updated on the Bangle?
Can I check which version is installed?

It should already be updated on the Developmen App Loader, as that is built automatically by github from this esruino/BangleApps repo whenever it has new commits made to it.
So just going to the Development App Loader and reinstall the relevant app/-s. There's a toggle under 'More...'->'Advanced' to let you reinstall without first uninstalling.
Also, I sometimes find an outdated version of the App Loader is probably cached in my browser. At those times I usually open it in the browsers private mode to get the most recent version.

I updated the main side around an hour ago so if you reinstall the app from banglejs.com/apps now you'll get the latest version.
On banglejs.com/apps I disable cacheing, but I can't for GitHub so the development app loader often requires you to force a full reload.
You can't tell which version is installed apart from by looking at the app's source on your watch and trying to figure out what's in the module that's added at the start of the file.
Some versioning could be good but it's a lot of extra complexity, and modules don't change that often. If a module changes a lot we should probably switch it to an app so it has all the versioning support.


Use real tile size rather than Cell Quadrant Size

Hi,
first of all, thanks for the tool, now my character doesn't get stuck on the ground any more!
However, for me, the CollisionShapes didn't fit the tiles.
This is due to using the Cell Quadrant Size as tile size. The Cell Quadrant Size is an optimization parameter and has nothing to do with tile size, as it says here.
This PR switches it out for the actual Tile Size.

Oops, I never noticed this. Thanks!


Removes OpenGeo connector

Fixes #60
This code has been deactivated for two reasons:

It makes CartoDB dependent on an external service.
It compromises intenet-disconected installations of CartoDB.

cc\ @rafatower @Kartones

:+1: didn't even knew it existed

CR please @rafatower


updatenotification creates zombie processes

I noticed my server had lots of zombie-processes where the parent was the container running magicmirror in serveronly-mode. By enabling only one module at a time I managed to locate the problematic module which is the updatenotification.
The cause of this seems to be partly my fault due to cloning my own modules with ssh instead of https (using url = git@github.com:xxx/xxx.git) and I guess this fails in the container since it doesn't have access to my username/password/ssh-keys.
But it's probably also something missing in the code that doesn't close the connection after the update-check, since I've seen a few git-http zombies too.
Would also be great to have a blacklist for modules not to update-check or at least a flag to only update check for the main project.

Should it be in the configuration for the updatenotification-module or as part of each module?
{
	module: "updatenotification",
	config: {
		moduleBlacklist: ["clock"] //empty array is default
	}
}

vs
{
	module: "clock",
	updateCheck: false //default is true
}

I prefer the first one. Thanks!

And maybe call it ignoreModules: []?

Made a PR for the ignoreModule functionality, guess I should make a PR for the documentation in the other repo now that its separate?.
This is the line that creates the zombie processes, the callback function is never called at all (I guess a timeout needs to be specified in some way, but can't really find it):
https://github.com/MichMich/MagicMirror/blob/d7295948fdb322c3bb267c08fb634719aa3f9fa5/modules/default/updatenotification/node_helper.js#L70
Found 2 other smaller problems when trying to debug this:

https://github.com/MichMich/MagicMirror/blob/d7295948fdb322c3bb267c08fb634719aa3f9fa5/modules/default/updatenotification/node_helper.js#L41 this line isn't blocking, so its only the "default"-module that will be checked the first time. Should probably convert this code to use Promises instead.
The refreshInterval configuration isn't in the documentation

Have done a bit more research about this.
As stated above the fetch()-method is never completed with error nor success.
It seems to be stuck waiting for keyboard-input from the user for this:
The authenticity of host '<host> (<ip>)' can't be established.
RSA key fingerprint is <fingerprint>.
Are you sure you want to continue connecting (yes/no)?

And when its run the next time it creates another process with the same issue. I tried to accept the host manually and then it goes to the error-handler for fetch() since it can't fetch it without my ssh-keys.
Adding this seems to make it not hang even without accepting the host:
	sg.git.env("GIT_SSH_COMMAND", "ssh -o BatchMode=yes");

Not really sure if that is a proper solution or if remotes that isn't http/https just should not be checked.

remotes that isn't http/https just should not be checked.

I would prefer this solution.
My setup seems similar to yours (docker container, module with<EMAIL_ADDRESS>as remote) but I have no such zombie-processes, but errors in the container logs (which is o.k. for me):
[2020-06-05 23:00:16.174] [LOG]    Starting node helper for: mmm-remote-docker
[2020-06-05 23:00:16.175] [LOG]    Connecting socket for: newsfeed
[2020-06-05 23:00:16.175] [LOG]    Starting module: newsfeed
[2020-06-05 23:00:16.176] [LOG]    Sockets connected & modules started ...
[2020-06-05 23:00:16.176] [LOG]
Ready to go! Please point your browser to: http://<IP_ADDRESS>:8080
[2020-06-05 23:00:16.823] [ERROR]  Host key verification failed.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

this problem is still present. I've never cloned a module using ssh - only http.
Same setup with docker server-only...

I noticed today, that the zombie processes occurr when the magicmirror has no internet

Maybe we should check to see if internet is working correctly before we fetch the repos? A PR on this is welcome!

Seems more like a workaround than a fix, what if the call for internet connectivity works but the update check call fails?
Proper timeout-handling and closing the process after the call is done is probably the correct way. Which I can't find in the documentation for simple-git, but there must be some way to do it?
Maybe update the simple-git dependency, there has been many new releases since the one specified in package.json?

A while back I reviewed all of the changes from the current version that MM uses and the current simple-git version and I didn't see any breaking changes. I also pulled in the latest on my local (2.20.1) and didn't see any issues.

Still happens in the current release, the update of simple-git didn't solve it.
> ps ax | grep "Z"
 430199 ?        Z      0:00 [git-remote-http] <defunct>

> pstree -p -s 430199
systemd(1)───containerd(385398)───containerd-shim(411902)───node(411920)───git-remote-http(430199)

And the only thing running in a container on the server and using node is magicmirror.

Maybe we should open een issue on the simple-git repo? Or is this a MagicMirror specific issue?

Mhhh... So can we assume that it is an issue in the simple-git library? Maybe open a bug report there and see what they say?

Damn @MichMich beat me by a second :-D

Muhahaha

Since my bug report the dev of simple-git (git-js) has added the possibility to set timeout for the git commands (see https://github.com/steveukx/git-js/blob/main/docs/PLUGIN-TIMEOUT.md) in v.2.36.
Is there anything stopping us from using async/await in the node_helper?

Is there anything stopping us from using async/await in the node_helper?

Only the question if we loose support for some browsers: https://caniuse.com/async-functions
ios10 is the only questionable here though I think

But node_helper isn't run on the client?

Then there is no reason for me to object :-) So, you want to go for a PR then?

Hopefully the PR I made will solve this, kinda hard to know without running the application for weeks.

Bah, been running the new version since release and logged in to my mirror today and was greeted with this:
=> There are 13 zombie processes.
And all of those are still like this:
11487 ?        Z      0:00 [git-remote-http] <defunct>
Annoying...

Annyoing indeed. How does one get that output to check on his own mirror?

The first output is from MOTD when I log in to my Ubuntu server, so I don't really know how to reproduce that on a RPi.
But all zombie processes can easily be found by:
ps ax | grep Z
  11487 ?        Z      0:00 [git-remote-http] <defunct>

To see where the process belongs to you can make this command:
pstree -s 11487
systemd───containerd───containerd-shim───node───git-remote-http

To see that it's node that spawning the process that becomes a zombie, the node process belongs to a container which is started by systemd in my case.

I can now confirm these zombie processes.
In the logs I found:
[16.04.2021 07:26.44.533] [ERROR] Failed to fetch git data for MMM-RepoStats: Error: block timeout reached
[16.04.2021 14:07.37.595] [ERROR] Failed to fetch git data for MMM-RepoStats: Error: block timeout reached
[16.04.2021 18:18.12.722] [ERROR] Failed to fetch git data for MMM-RMV: Error: block timeout reached
[17.04.2021 03:29.23.095] [ERROR] Failed to fetch git data for MMM-RMV: Error: block timeout reached
[17.04.2021 03:29.24.467] [ERROR] Failed to fetch git data for MMM-Strava: Error: block timeout reached
[17.04.2021 09:30.11.592] [ERROR] Failed to fetch git data for MMM-RMV: Error: block timeout reached
[17.04.2021 09:30.13.377] [ERROR] Failed to fetch git data for default: Error: block timeout reached
[17.04.2021 16:01.01.967] [ERROR] Failed to fetch git data for default: Error: block timeout reached

I had 8 zombie processes so may this is a 1:1 relation to the above logs.
The message block timeout reached is coming from this line.

I could reproduce this error for the mm-repo with every restart.
This is may caused by the default timout=1000 which seems to low.
I'm running now with timeout=15000 and it works (the error after start is gone), will see if it occours later.
One explanation for this is may that I´m using my docker setup where the mm-git-repo is cloned with git clone --depth 1 -b "${BuildRef}" --single-branch "${GitRepo}" so performing here a git fetch --dry-run will bring a long list of missing refs:
/opt/magic_mirror $ git fetch --dry-run
From https://github.com/MichMich/MagicMirror
   fd1913a7..ccf5bb93  develop    -> origin/develop
 * [new tag]           V2.2.1     -> V2.2.1
 * [new tag]           v.2.1.3    -> v.2.1.3
 * [new tag]           v2.0.0     -> v2.0.0
 * [new tag]           v2.0.1     -> v2.0.1
 * [new tag]           v2.0.2     -> v2.0.2
 * [new tag]           v2.0.3     -> v2.0.3
 * [new tag]           v2.0.4     -> v2.0.4
 * [new tag]           v2.0.5     -> v2.0.5
 * [new tag]           v2.1.0     -> v2.1.0
 * [new tag]           v2.1.1     -> v2.1.1
 * [new tag]           v2.1.2     -> v2.1.2
 * [new tag]           v2.10.0    -> v2.10.0
 * [new tag]           v2.10.1    -> v2.10.1
 * [new tag]           v2.11.0    -> v2.11.0
 * [new tag]           v2.12.0    -> v2.12.0
 * [new tag]           v2.13.0    -> v2.13.0
 * [new tag]           v2.14.0    -> v2.14.0
 * [new tag]           v2.15.0    -> v2.15.0
 * [new tag]           v2.2.0     -> v2.2.0
 * [new tag]           v2.2.2     -> v2.2.2
 * [new tag]           v2.3.0     -> v2.3.0
 * [new tag]           v2.3.1     -> v2.3.1
 * [new tag]           v2.4.0     -> v2.4.0
 * [new tag]           v2.4.1     -> v2.4.1
 * [new tag]           v2.5.0     -> v2.5.0
 * [new tag]           v2.6.0     -> v2.6.0
 * [new tag]           v2.7.0     -> v2.7.0
 * [new tag]           v2.7.1     -> v2.7.1
 * [new tag]           v2.8.0     -> v2.8.0
 * [new tag]           v2.9.0     -> v2.9.0
 * [new tag]           V2.2.1     -> V2.2.1
 * [new tag]           v.2.1.3    -> v.2.1.3
 * [new tag]           v2.0.0     -> v2.0.0
 * [new tag]           v2.0.1     -> v2.0.1
 * [new tag]           v2.0.2     -> v2.0.2
 * [new tag]           v2.0.3     -> v2.0.3
 * [new tag]           v2.0.4     -> v2.0.4
 * [new tag]           v2.0.5     -> v2.0.5
 * [new tag]           v2.1.0     -> v2.1.0
 * [new tag]           v2.1.1     -> v2.1.1
 * [new tag]           v2.1.2     -> v2.1.2
 * [new tag]           v2.10.0    -> v2.10.0
 * [new tag]           v2.10.1    -> v2.10.1
 * [new tag]           v2.11.0    -> v2.11.0
 * [new tag]           v2.12.0    -> v2.12.0
 * [new tag]           v2.13.0    -> v2.13.0
 * [new tag]           v2.14.0    -> v2.14.0
 * [new tag]           v2.15.0    -> v2.15.0
 * [new tag]           v2.2.0     -> v2.2.0
 * [new tag]           v2.2.2     -> v2.2.2
 * [new tag]           v2.3.0     -> v2.3.0
 * [new tag]           v2.3.1     -> v2.3.1
 * [new tag]           v2.4.0     -> v2.4.0
 * [new tag]           v2.4.1     -> v2.4.1
 * [new tag]           v2.5.0     -> v2.5.0
 * [new tag]           v2.6.0     -> v2.6.0
 * [new tag]           v2.7.0     -> v2.7.0
 * [new tag]           v2.7.1     -> v2.7.1
 * [new tag]           v2.8.0     -> v2.8.0
 * [new tag]           v2.9.0     -> v2.9.0

Maybe this exceeds the default timeout.
But this is not an explanation for other modules where this list is very short.

After increasing the timeout the zombie processes are gone.
@buxxi can you test this too?
If you can confirm this we should increase the default timeout here.

@khassel I recently upgraded to MagicMirror: v2.15.0 and was digging in the log files as a 3rd party module was preventing it from loading. I noticed that I was also receiving Error: block timeout reached for each of my modules on startup. After adjusting the timeout from 1000 to 15000, it no longer threw that error.

Well, increasing the timeout just makes it less likely to happen (and sure 1000 was a bit low as default). I had this issue a few times when there was no timeout at all.
This just means the timeout-handling isn't working as it should and the process probably needs to be killed since it can't quit by itself.

and as a side note, I have a private repo that gets the same error..

We have 2 problems here:

the default timeout is to low which produces Error: block timeout reached and the updatenotification for the affected module does not work. My tests with 5000 (instead of 1000) are working
running MM as docker container produces additional a zombie process for every above error

I will change my docker setup to get rid of this error. Meanwhile you can add the --init parameter to your docker run ... command or init: true in the docker-compose.yml file. You can read more about this error running npm in a docker container e.g. here.

@buxxi can you please test again and finally close this issue if it works on your side?

Ok, updated my container and lowered the timeout to 200ms, will check back in a day or two if the zombies are gone.

4 errors in the log and no zombies, so I guess we can call it fixed now. Thanks @khassel!

Hi Guys, I have all the same problems. I fixed it... sort of. I went into the updatenotification.js and changed the time to a ridiculous number
.register("updatenotification", {
// Define module defaults
defaults: {
updateInterval: 10 * 60 * 100000000, // A VERY LONG TIME
refreshInterval: 24 * 60 * 60 * 1000, // one day
ignoreModules: [],
timeout: 5000
it came back with an error when I rebooted.
I went back and modified the update interval to something more reasonable. It now works
.register("updatenotification", {
// Define module defaults
defaults: {
updateInterval: 10 * 60 * 10000, // every 10 minutes
refreshInterval: 24 * 60 * 60 * 1000, // one day
ignoreModules: [],
timeout: 5000
HOPE THIS HELPS SOMEONE


No longer working with CircuitPython 2.2.3

Updated my trinket M0 to CircuitPython 2.2.3 and the jupyter integration is no longer working. In my logs I get:
[I 20:19:36.190 NotebookApp] Saving file at /Documents/Github/Useful-python/Mircropython/Micropython with Adafruit M0 7-2-2018.ipynb
DEBUG:jupyter_micropython_kernel.kernel:Opening MicroPython board connection on port: /dev/cu.usbmodem14341 baud: 115200
Traceback (most recent call last):
  File "/anaconda3/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/anaconda3/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/anaconda3/lib/python3.6/site-packages/jupyter_micropython_kernel-0.1.0-py3.6.egg/jupyter_micropython_kernel/__main__.py", line 22, in <module>
    IPKernelApp.launch_instance(kernel_class=make_micropython_kernel(port, baud))
  File "/anaconda3/lib/python3.6/site-packages/traitlets/config/application.py", line 657, in launch_instance
    app.initialize(argv)
  File "<decorator-gen-123>", line 2, in initialize
  File "/anaconda3/lib/python3.6/site-packages/traitlets/config/application.py", line 87, in catch_config_error
    return method(app, *args, **kwargs)
  File "/anaconda3/lib/python3.6/site-packages/ipykernel/kernelapp.py", line 457, in initialize
    self.init_kernel()
  File "/anaconda3/lib/python3.6/site-packages/ipykernel/kernelapp.py", line 368, in init_kernel
    user_ns=self.user_ns,
  File "/anaconda3/lib/python3.6/site-packages/traitlets/config/configurable.py", line 412, in instance
    inst = cls(*args, **kwargs)
  File "/anaconda3/lib/python3.6/site-packages/jupyter_micropython_kernel-0.1.0-py3.6.egg/jupyter_micropython_kernel/kernel.py", line 42, in __init__
    self._board.enter_raw_repl()
  File "/anaconda3/lib/python3.6/site-packages/jupyter_micropython_kernel-0.1.0-py3.6.egg/jupyter_micropython_kernel/pyboard.py", line 204, in enter_raw_repl
    raise PyboardError('could not enter raw repl')

@robmarkcole hiya do you know when the last version it worked?
@tdicola on tidyday, please check this issue, and fix so circuitpython is functional again

Hi it worked with whatever firmware the Trinket M0 shipped with (did't ever check version) - I updated the firmware for the first time yesterday

I can't repro the issue, it seems to connect fine to a Trinket M0 with 2.2.3.  Here's one out of the box with 2.0:

And the same upgrade to 2.2.3:

You might try a different USB cable to make sure you're getting a good connection to the board.  Also try manually resetting the board and make sure there isn't a pre-existing main.py that might be running and spamming unexpected output.


documentation

where is the documentation ???

Hi @anbestephen,
We are currently working on documentation and examples for the client. Till it is ready, you can use the tests in the source as usage samples. We are here of course to support you with any question you may have.

thanks @eyalbe4 !!

Hi @eyalbe4 , i find good examples in the test cases. Is there any utility class to parse the RepoPath object's ItemPath  retrieved from ArtifactoryClient search  to {groupId, artifactId , version} , to a format which can be added to maven or gradle projects dependency?

Hi (: I'm trying to use this API but I can't get it to work. Would anyone help be kind to walk me through it?

@PastelBelem8 have you tried adding compile 'org.jfrog.artifactory.client:artifactory-java-client-api:1.2.2' to your project dependencies?

I'm using maven and I tried adding the dependency as explained in https://bintray.com/jfrog/artifactory-tools/artifactory-client-java/2.0.0

@PastelBelem8 can you give more detail on the issue you are encountering?

@PastelBelem8, Please follow the documentation in the project README.
You should add the following dependency in your Maven project:
<dependency>
    <groupId>org.jfrog.artifactory.client</groupId>
    <artifactId>artifactory-java-client-services</artifactId>
    <version>LATEST</version>
</dependency>


Remove Python 2 code.

Removes from __future__ import unicode_literals from all scripts.  I have not changed the FAQ topic which talks about Unicode, so it might be outdated now. Closes #70
Removes six as a requirement.  Six features were replaced with their Python 3 equivalents.  Closes #71
Removes functions backported from Python 3, and any Python 2 branches.
super() no longer needs arguments when called inside of methods.

I took a quick look, but haven't had time to finish / add in a couple of related updates. Wanted to drop a quick note saying thanks for opening this, really helpful! 🙂

Don't worry.  I can handle merge conflicts if any come up.

There are a couple of PRs I want to land that are adding bugfixes / new features.  Then I will do a fast release.
After that, I am going to see how much longer this takes.  If you are willing to rebase it I can keep adding commits here.  However this is stale and many moons ago, so I am also happy to just cherry pick things into different (smaller, one by one PRs).  There is no rush!  Just depends on your level of interest :+1:
Regardless, thank you for spending the time you did to get this PR here in the first place!

I'll try to keep this rebased onto master.  It'd be easy enough to split this into smaller PR's if you'd prefer that.

Thanks! Initial rebase was needed for CI fixes, if you want to rebase as things go that's great too.
At the end of this PR we'll just merge (rather than squash) things down, I may rewrite the history at the end. And hope it never needs to be bisected 😶
This will be good as one PR I think, I'm very excited about this one!

@svenevs For automatic migration of old python2 code you can use (pyupgrade)[https://github.com/asottile/pyupgrade]. It may be easier to run this tool by your own instead of investing time in rebase.


Added advanced 'quote' test

An later test to see that the 'quote' form still works as intended, even after more powerful features are added.
This test is included because it is possible to get all the way to part 6 with a faulty implementation for evaluating 'quote'.

Thanks, Joel!


Can't launch autoware with humble

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I'm convinced that this is not my fault but a bug.

Description
I am preparing a new setup with ROS2 humble. For some reason, Autoware fails to launch for some weird argument substitution failure when I try:
$ ros2 launch autoware_launch planning_simulator.launch.xml map_path:=../data/autoware_data_universe/sample-map-planning/ vehicle_model:=sample_vehicle sensor_model:=sample_sensor_kit

Logs with --debug
[DEBUG] [launch.launch_context]: emitting event synchronously: 'launch.events.IncludeLaunchDescription'
[INFO] [launch]: All log files can be found below /home/sig/.ros/log/2022-12-08-01-49-25-019569-vr-desktop-457560
[INFO] [launch]: Default logging verbosity is set to DEBUG
[DEBUG] [launch]: processing event: '<launch.events.include_launch_description.IncludeLaunchDescription object at 0x7f35ee31a050>'
[DEBUG] [launch]: processing event: '<launch.events.include_launch_description.IncludeLaunchDescription object at 0x7f35ee31a050>' ✓ '<launch.event_handlers.on_include_launch_description.OnIncludeLaunchDescription object at 0x7f35ee31b5e0>'
[DEBUG] [launch.launch_description_source]: Traceback (most recent call last):
  File "/opt/ros/humble/lib/python3.10/site-packages/launch/launch_description_source.py", line 68, in try_get_launch_description_without_context
    perform_substitutions(context, self.__location)
  File "/opt/ros/humble/lib/python3.10/site-packages/launch/utilities/perform_substitutions_impl.py", line 26, in perform_substitutions
    return ''.join([context.perform_substitution(sub) for sub in subs])
  File "/opt/ros/humble/lib/python3.10/site-packages/launch/utilities/perform_substitutions_impl.py", line 26, in <listcomp>
    return ''.join([context.perform_substitution(sub) for sub in subs])
  File "/opt/ros/humble/lib/python3.10/site-packages/launch/launch_context.py", line 240, in perform_substitution
    return substitution.perform(self)
  File "/opt/ros/humble/lib/python3.10/site-packages/launch/substitutions/launch_configuration.py", line 98, in perform
    raise SubstitutionFailure(
launch.substitutions.substitution_failure.SubstitutionFailure: launch configuration 'vehicle_launch_pkg' does not exist

[DEBUG] [launch.launch_description_source]: Failed to load the launch file without a context: launch configuration 'vehicle_launch_pkg' does not exist
[DEBUG] [launch.launch_description_source]: Traceback (most recent call last):
  File "/opt/ros/humble/lib/python3.10/site-packages/launch/launch_description_source.py", line 68, in try_get_launch_description_without_context
    perform_substitutions(context, self.__location)
  File "/opt/ros/humble/lib/python3.10/site-packages/launch/utilities/perform_substitutions_impl.py", line 26, in perform_substitutions
    return ''.join([context.perform_substitution(sub) for sub in subs])
  File "/opt/ros/humble/lib/python3.10/site-packages/launch/utilities/perform_substitutions_impl.py", line 26, in <listcomp>
    return ''.join([context.perform_substitution(sub) for sub in subs])
  File "/opt/ros/humble/lib/python3.10/site-packages/launch/launch_context.py", line 240, in perform_substitution
    return substitution.perform(self)
  File "/opt/ros/humble/lib/python3.10/site-packages/launch/substitutions/launch_configuration.py", line 98, in perform
    raise SubstitutionFailure(
launch.substitutions.substitution_failure.SubstitutionFailure: launch configuration 'sensor_launch_pkg' does not exist

[DEBUG] [launch.launch_description_source]: Failed to load the launch file without a context: launch configuration 'sensor_launch_pkg' does not exist

The logs says to the sensor_launch_pkg and vehicle_launch_pkg parameters are not set, but both are supposed to be set here:
https://github.com/autowarefoundation/autoware.universe/blob/01daebf42937a05a2d83f3dee2c0778389492e50/launch/tier4_sensing_launch/launch/sensing.launch.xml#L8
https://github.com/autowarefoundation/autoware.universe/blob/01daebf42937a05a2d83f3dee2c0778389492e50/launch/tier4_vehicle_launch/launch/vehicle.launch.xml#L10
And there are only use right after in their respective launch file.
Any idea?
Expected behavior
No launch error
Actual behavior
error
Steps to reproduce
launch autoware
Versions
No response
Possible causes
No response
Additional context
No response

@VRichardJP Could you tell me the versions of each repository using vcs export --exact src? Are they the latest?

It is on a fork of mine. The latest commit I have pulled is 41f47be4004bcf027d8c1188a6dbe7d8370f3287
But I don't have much changes in the launch files:
$ git diff origin/main --stat | grep "tier4_.*.launch.xml"
 launch/tier4_map_launch/launch/map.launch.xml      |   14 +-
 .../tier4_sensing_launch/launch/sensing.launch.xml |    4 +
 .../tier4_system_launch/launch/system.launch.xml   |   34 +-
 .../tier4_vehicle_launch/launch/vehicle.launch.xml |    2 +-

diff --git a/launch/tier4_vehicle_launch/launch/vehicle.launch.xml b/launch/tier4_vehicle_launch/launch/vehicle.launch.xml
index 0493e1ae0..436a48aee 100644
--- a/launch/tier4_vehicle_launch/launch/vehicle.launch.xml
+++ b/launch/tier4_vehicle_launch/launch/vehicle.launch.xml
@@ -13,7 +13,7 @@
   <group>
     <arg name="model_file" default="$(find-pkg-share tier4_vehicle_launch)/urdf/vehicle.xacro" description="path to the file of model settings (*.xacro)"/>
     <node name="robot_state_publisher" pkg="robot_state_publisher" exec="robot_state_publisher">
-      <param name="robot_description" value="$(command 'xacro $(var model_file) vehicle_model:=$(var vehicle_model) sensor_model:=$(var sensor_model) config_dir:=$(var config_dir)' 'warn')"/>
+      <param name="robot_description" value="$(command 'xacro $(var model_file) vehicle_model:=$(var vehicle_model) sensor_model:=$(var sensor_model) config_dir:=$(var config_dir)')"/>
     </node>
   </group>

diff --git a/launch/tier4_sensing_launch/launch/sensing.launch.xml b/launch/tier4_sensing_launch/launch/sensing.launch.xml
index af9e4481a..3d15a8708 100644
--- a/launch/tier4_sensing_launch/launch/sensing.launch.xml
+++ b/launch/tier4_sensing_launch/launch/sensing.launch.xml
@@ -1,9 +1,11 @@
 <launch>
   <arg name="launch_driver" default="true" description="do launch driver"/>
   <arg name="sensor_model" default="sample_sensor_kit" description="sensor model name"/>
+  <arg name="vehicle_param_file" default="$(find-pkg-share vehicle_info_util)/config/vehicle_info.param.yaml" description="path to the file of vehicle info yaml"/>
   <arg name="vehicle_mirror_param_file" default="$(find-pkg-share vehicle_info_util)/config/vehicle_mirror.param.yaml" description="path to the file of vehicle mirror position yaml"/>
   <arg name="use_pointcloud_container" default="false" description="launch pointcloud container"/>
   <arg name="pointcloud_container_name" default="pointcloud_container"/>
+  <arg name="coordinate_system_param_file" default=""/>

   <let name="sensor_launch_pkg" value="$(find-pkg-share $(var sensor_model)_launch)"/>

@@ -13,9 +15,11 @@
     <!-- Driver -->
     <include file="$(var sensor_launch_pkg)/launch/sensing.launch.xml">
       <arg name="launch_driver" value="$(var launch_driver)"/>
+      <arg name="vehicle_param_file" value="$(var vehicle_param_file)"/>
       <arg name="vehicle_mirror_param_file" value="$(var vehicle_mirror_param_file)"/>
       <arg name="use_pointcloud_container" value="$(var use_pointcloud_container)"/>
       <arg name="pointcloud_container_name" value="$(var pointcloud_container_name)"/>
+      <arg name="coordinate_system_param_file" value="$(var coordinate_system_param_file)"/>
     </include>
   </group>
 </launch>

In addition to autoware.universe itself, the consistency between repositories is important.
What are the versions of other repositories?

@VRichardJP I'm sorry I was unable to reproduce the problem.
Would it be possible for you to provide your .repos file so that others can test it easily?
Also, since it's probably not the bug of Autoware itself but maybe your fork or usage, is it okay to transfer this issue to the discussions?
If you want to keep this issue here, please provide more concrete steps to reproduce this issue.

I'll try to reproduce with the original autoware. If it works I'll close this and investigate my fork on my own.

I couldn't reproduce the problem with the same environment (docker, toolchain, etc) and latest autoware from github. Hopefully I will find the cause on my version.

Quick update: there is no problem on my fork anymore either.
I did not change anything to the source code, so I am a bit puzzled. I just repulled the base humble docker image and re-run colcon.
¯\_(ツ)_/¯


CRAYSAT-1945: Fix traceback error of session checks in CFS v2

Summary and Scope
Fixed the traceback error encountered during session checks in CFS v2 when using a smaller page size.
Issues and Related PRs
List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.

Resolves CRAYSAT-1945

Testing
List the environments in which these changes were tested.
Tested on:

<development system>
Local development environment
Virtual Shasta

Test description:
How were the changes tested and success verified? If schema changes were part of this change, how were those handled in your upgrade/downgrade testing?

Were the install/upgrade-based validation checks/tests run (goss tests/install-validation doc)?
Were continuous integration tests run? If not, why?
Was upgrade tested? If not, why?
Was downgrade tested? If not, why?
Were new tests (or test issues/Jiras) created for this change?

Risks and Mitigations
Are there known issues with these changes? Any other special considerations?
Pull Request Checklist

[ ] Version number(s) incremented, if applicable
[ ] Copyrights updated
[ ] License file intact
[ ] Target branch correct
[ ] CHANGELOG.md updated
[ ] Testing is appropriate and complete, if applicable
[ ] HPC Product Announcement prepared, if applicable

This PR has been obfuscated with the fix in the PR-https://github.com/Cray-HPE/sat/pull/306


Feature request for clear option into file transport

winston 3.2.1
In normal way after application restarting all logs will be appended into existing file.
In this case log file can be increased upto very huge size and we need to find where second logs started after first logs was finished. So would be greate if there is option for clear the log file if it exists at starting work - in this case logfile will only contain logs from latest application works.

@Alessar you can do this yourself easily on startup using fs.truncate() or fs.truncateSync
example:
const fs=require('fs');
fs.truncateSync('combined.log',0);
fs.truncateSync('error.log',0);

using this logic, you could even submit a pr to the library

A file transport can be cleared by setting the mode with options: { flags: "w" } like so:
export const logger = winston.createLogger({
    ...
    transports: [
        new winston.transports.File({
            ...
            options: { flags: "w" }
        }),
    ],
});

You can read about that here: https://github.com/winstonjs/winston/blob/master/docs/transports.md#file-transport


next-sass compile error, 'child_process' in 'worker-farm' not found

Hi,
I can't manage to set up sass plugin with my current Next settings. The issue is that when I am trying to compile my app, the following error is thrown

I couldn't find any solution either on the web or in currently existing issues.
My package.json
{
	"scripts": {
		"dev": "next",
		"build": "next build",
		"start": "next start"
	},
	"dependencies": {
		"@zeit/next-css": "^1.0.1",
		"@zeit/next-sass": "^1.0.1",
		"isomorphic-unfetch": "^3.0.0",
		"lodash": "^4.17.15",
		"next": "latest",
		"node-sass": "^4.13.0",
		"react": "^16.7.0",
		"react-dom": "^16.7.0"
	},
	"devDependencies": {
		"@testing-library/jest-dom": "^4.2.3",
		"@testing-library/react": "^9.3.2",
		"@types/jest": "^24.0.21",
		"@types/node": "^12.12.7",
		"@types/reach__router": "^1.2.6",
		"@types/react": "^16.9.11",
		"@types/react-dom": "^16.9.3",
		"@typescript-eslint/eslint-plugin": "^2.6.1",
		"eslint-config-prettier": "^6.1.0",
		"eslint-config-recommended": "^4.0.0",
		"eslint-plugin-react": "^7.14.3",
		"eslint-plugin-react-hooks": "^2.0.1",
		"prettier": "^1.18.2",
		"prop-types": "^15.7.2",
		"react-redux": "^7.1.0",
		"redux": "^3.6.0",
		"redux-devtools-extension": "^2.13.2",
		"redux-thunk": "^2.3.0",
		"typescript": "^3.7.2"
	}
}

next.config.js
const withSass = require('@zeit/next-sass');

exports.default = withSass({
	env: {
		DEV: true
	}
});

The entire repo is available at https://github.com/matkoson/next-sass-bug-repro
How to reproduce: yarn => yarn dev
All is working fine when I get rid of withCSS wrapper.
Please help.

Are you trying to use @zeit/next-css or @zeit/next-sass?
In your example repository, I only see @zeit/next-css in your next.config.js, which won't work for .scss files. If you want to use SASS, you will need to use the next-sass package.

Hi @jamesmosier ,
Thank you for the reply. I should mention I was experiencing exactly the same issue with css plugin as well. I have already pushed changes to the repo, now it uses next-sass

Hi, thanks for creating an issue. We currently recommend using https://nextjs.org/docs/basic-features/built-in-css-support as the plugins have been deprecated in favor of the built-in support.


$push->getErrors() not returns identifiers

Hello,
After calling $push->send() method I want to get which queues are not succeed.
In order to see that I'm calling $push->getErrors() method, but it gives that output:
Array
(
    [1] => Array
        (
            [MESSAGE] => ApnsPHP_Message Object
                (
                    [_bAutoAdjustLongPayload:protected] => 1
                    [_aDeviceTokens:protected] => Array
                        (
                            [0] => a60ea7356c4f6x5a8c34861907a1a7e9d5fa459467e412edceed7406b7edfb8c
                        )

                    [_sText:protected] => blablabla message
                    [_nBadge:protected] => 1
                    [_sSound:protected] => default
                    [_sCategory:protected] =>
                    [_bContentAvailable:protected] =>
                    [_aCustomProperties:protected] => Array
                        (
                            [key] => general
                        )

                    [_nExpiryValue:protected] => 604800
                    [_mCustomIdentifier:protected] => normalQueueId1
                )

            [BINARY_NOTIFICATION] => X�J$ ��5lOnZ�4������E�g����t�����{"aps":{"alert":{"body":"blablabla message"},"badge":1,"sound":"default"},"key":"general"}
            [ERRORS] => Array
                (
                    [0] => Array
                        (
                            [command] => 8
                            [statusCode] => 8
                            [identifier] => 1
                            [time] =><PHONE_NUMBER>
                            [statusMessage] => Invalid token
                        )

                )

        )
)

From that output, I can not access the identifier of the failed queue which is (normalQueueId1), because it is protected.
Is there another method that I can retrieve failed push notification queues with their full properties including identifier ?
Thank you.

Sorry, my mistake, there is already a method to retrieve identifier.
MESSAGE_OBJECT->getCustomIdentifier();