MathematicaToPython.py needs refactoring

The MathematicaToPython.py utility script is out of date and needs to be refactored. It refers to changed/removed APIs in coxeter.
Moreover, its intended usage isn't very clear to me, despite the long comment at the top. Is it possible to include a corresponding Mathematica script in this repository so the data is reproducible?
Should this file be kept someplace outside the coxeter package directory, in a scripts folder or something like that?

It would be nice to write a Mathematica script for this. I think I spent a couple minutes once to figure out how to get the data, but I didn't spend the time to write one. I'm not sure whether this belongs in here at all; at this point maybe we just accept that these are the shapes from that paper, and not worry about how to regenerate them. If we want to keep it in, then I'm fine moving it to a scripts directory.


[upgrade] Ubuntu: Failed to update apt cache

14:26:10 INFO cli.engine.ansible.AnsibleCommand - TASK [common : Install selinux packages as prerequisite for SELinux module] *********************************************************************************************************
14:26:11 INFO cli.engine.ansible.AnsibleCommand - [WARNING]: Could not find aptitude. Using apt-get instead
14:26:11 INFO cli.engine.ansible.AnsibleCommand - ok: [vm-qa-upgrades-ubu-master-001]
14:27:43 INFO cli.engine.ansible.AnsibleCommand - fatal: [vm-qa-upgrades-ubu-node-001]: FAILED! => {"changed": false, "msg": "Failed to update apt cache: "}
14:27:43 INFO cli.engine.ansible.AnsibleCommand - fatal: [vm-qa-upgrades-ubu-node-002]: FAILED! => {"changed": false, "msg": "Failed to update apt cache: "}

modified outbound security rules on azure


Add missing --storage arguments to run_local.sh.

Closes #813.

-wallet wallet.json open-chain --to-public-key "$KEY"
KEY in wallet_2.json

-wallet wallet.json open-chain --to-public-key "$KEY"
KEY in wallet_2.json

Yes, it's meant to be that way: The owner of wallet.json creates a new chain for the owner of wallet_2.json.

see #813
if !self.known_key_pairs.contains_key(&m.owner) {


Extend output port and remove selection halo

Pull Request Description
Closes #11463

Output port area extended twice
Selection halo is removed (but most of the code is still there – I understood we don’t want to remove everything before testing)

https://github.com/user-attachments/assets/4c6d7837-362e-4309-aa9b-5c0679d600e9
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[x] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
TypeScript,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
[x] Unit tests have been written where possible.
[x] If meaningful changes were made to logic or tests affecting Enso Cloud integration in the libraries,
or the Snowflake database integration, a run of the Extra Tests has been scheduled.

If applicable, it is suggested to paste a link to a successful run of the Extra Tests.

This looks really good. Let's go ahead and remove the code we can always get from git history if we need to later.


Projectiles from mobs not doing damage in town claims

Within town claims, skeletons cannot hurt you. We tested with other mobs, and they still deal damage.
This seems to also affect drowned with tridents.
https://youtu.be/eRqS1eQLZyw

Probably need to whitelist monster throwers damaging players


fix: do not send pooled transactions if pool is empty

This prevents us from sending a NewPooledTransactions message if the pool is empty. This also caused a hive devp2p test to fail because the test requests headers, and does not expect an empty NewPooledTransactionHashes  as the first message.
See this workflow run for the hive failure:
https://github.com/paradigmxyz/reth/actions/runs/4505504473/jobs/7931395605?pr=1348#step:7:14
# failed to get block headers: unexpected message received: (*ethtest.NewPooledTransactionHashes)({
#   Types: ([]uint8) {
#   },
#   Sizes: ([]uint32) {
#   },
#   Hashes: ([]common.Hash) {
#   }
# })

We already ensure that the pool is not empty in other calls to send_transactions_hashes:
https://github.com/paradigmxyz/reth/blob/1a2a22606f51d52311438326e16903295ac23572/crates/net/network/src/transactions.rs#L242-L264

Codecov Report

Merging #1949 (1a2a226) into main (01b4444) will decrease coverage by 12.26%.
The diff coverage is 0.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff             @@
##             main    #1949       +/-   ##
===========================================
- Coverage   73.12%   60.86%   -12.26%
===========================================
  Files         424      424
  Lines       51879    51882        +3
===========================================
- Hits        37934    31579     -6355
- Misses      13945    20303     +6358

Flag
Coverage Δ

integration-tests
19.47% <0.00%> (+0.01%)
:arrow_up:

unit-tests
54.56% <0.00%> (-12.86%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

crates/net/network/src/transactions.rs
18.59% <0.00%> (-0.11%)
:arrow_down:

... and 124 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Id refactoring

Heavily under-engineered the engine:

Switched to monotonic 64 bit integer record ids on all platforms
Re-implemented TTL's queue with AVL-tree

Coverage decreased (-0.9%) to 45.15% when pulling b7436b4df10b2e473c110f4c1a44c9e70e5d330c on id-refactoring into 8c4e984c6a2797d7fb0aacbdfb19287a849f2ff0 on master.


IOU - User able to start Money Request flow on IOU details page

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.60-12
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:
Precondition: user should be singed in

Open app
Open any chat with another user where there has been no money request in the past
Make a Money Request
Tap on the IOU preview
Tap on Plus button next to composer
Select "Request Money"
Write any amount and tap on continue
Navigate back to 1:1 DM chat with user
Tap on IOU preview
Make a Money Request
Tap on iOU preview
Tap on Plus button next to composer

Expected Result:
User should not be ablte to start the Money Request flow from the IOU details page
Actual Result:
User able to start Money Request flow on IOU details page when first IOU was made. When user made the second IOU, the Money Request option is no more available on IOU details page
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/9a09d7e7-9395-4e59-b88f-d3d195c1c7e6
View all open jobs on GitHub

@luacmartins  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

Agreed! We changed the layout of the chat reports, so this is expected now. Closing. @lanitochka17 please note that the new Expense report layout is now the same as the Expense thread if the Expense report has only one expense.


Close connection on fetch_committed_offsets/3

After request the connection should be closed

Any update?

What problem does this solve? I would assume that not eagerly closing the connection would allow us to reuse it soon afterwards. Does that reuse not happen?

Yes, it do not reuse the connection and for each call it spawn new process
1> brod:start_client([{"localhost", 9092}], c1, []).
ok
2> process_info(self(), [links]).
[{links,[<0.522.0>]}]
3> [brod:fetch_committed_offsets(c1, <<"some-group">>) || _ <- lists:seq(1, 10)].
[{ok,[]},
 {ok,[]},
 {ok,[]},
 {ok,[]},
 {ok,[]},
 {ok,[]},
 {ok,[]},
 {ok,[]},
 {ok,[]},
 {ok,[]}]
4> process_info(self(), [links]).
[{links,[<0.967.0>,<0.971.0>,<0.975.0>,<0.979.0>,<0.981.0>,
         <0.977.0>,<0.973.0>,<0.969.0>,<0.963.0>,<0.965.0>,
         <0.522.0>]}]

thank you for the PR
and sorry for the delay

included in 3.15.3, published to hex


Type safe native pointer wrappers

This PR adds type information to the native pointes. Ideally the native struct should have a corresponding Kotlin object and encapsulate operations on that type, but this would require reworking our current native memory management routines and would potentially overlap with any efforts in automatic generation of such classes from the core api. Without that rework we would introduce yet another level of indirection to get hold of the pointers. Thus, this implementation is a minimal implementation of a typed cinterop API that gives a type safe pointer system (which cannot be achieved directly through typealiases) that still allows taking advantage of inheritance relationship between pointer types (which isn't possible by value classes).

The current implementation doesn't differentiate RealmChangesPointer into RealmObjectChangesPointer and RealmCollectionChangesPointer. Doing that would introduce even more generic parameters to the whole notification registration infrastructure which in my opinion will make it too cluttered and not worth it.


Dangling symlinks cause upload errors with wildcards in filespecs

Describe the bug
When attempting to upload via a filespec that includes a pattern with a wildcard, if the current directory or any child directories contain dangling symlinks the upload will fail. This is regardless of whether or not the dangling symlink matches the pattern.
Current behavior
[Debug] Usage Report: Sending info...
[Debug] Sending HTTP GET request to: .../artifactory/api/system/version
[Error] stat broken.symlink: no such file or directory
[Error] stat broken.symlink: no such file or directory
[Debug] Uploaded 0 artifacts.
[Error] stat broken.symlink: no such file or directory
[Debug] Artifactory response: 200 OK
[Debug] JFrog Artifactory version is: 7.63.10
[Debug] Sending HTTP POST request to: .../artifactory/api/system/usage

Reproduction steps
Create the following structure:
.
├── a-test.txt
├── broken.symlink -> a-file.txt
└── upload.filespec

upload.filespec:
{
    "files": [
        {
            "pattern": "./*-test.txt",
            "target": "generic-test/",
            "props": "name=Test File"
        }
    ]
}

Run jfrog rt u --spec=upload.filespec
Expected behavior
Upload the relevant file and ignore the irrelevant broken symlink.
JFrog CLI version
2.67.0
Operating system type and version
AlmaLinux 9.4
JFrog Artifactory version
No response
JFrog Xray version
No response

The only workarounds I've found are to either clean up your broken symlinks prior to trying the upload, or make use of the --symlinks arg, e.g. jfrog rt u --symlinks --spec=upload.filespec. Using --symlinks changes functionality as it now uploads the symlink and not the file the symlink was pointing to.

Thanks. I went with cleaning dangling symlinks before uploading.
For reference, here is the command I used: find . -xtype l -exec rm {} +.
ChatGPT breakdown:

find .

This initiates a search starting from the current directory (.) and includes all subdirectories.

-xtype l

This option filters the search results to broken symbolic links.
Broken symbolic links are links pointing to a file or directory that no longer exists.

-exec rm {} +

This executes the rm (remove) command on each broken link found.
{} is a placeholder that find replaces with the file path of each broken link.
+ ensures multiple files are passed to rm in a single command, improving efficiency by reducing the number of calls to rm.


Canvas API score uploading

When scores are updated, they should automatically be pushed to bCourses if they change. Challenges:

Some students are enrolled under a different email. We should match students based on student ID instead of email.
We need to configure which scores get sent. Probably some mapping (OK assignment, score kind) -> bCourses assignment.
Deal with failure somehow - we can't ignore if a score does not get uploaded.

For a first pass, it would be sufficient to have a button on the assignment page that will attempt to export all scores to bCourses (if they change).
We have a repo with scripts to upload scores to bCourses already, which should make this a little easier. For reference, here are the Canvas API docs for grades.
Testing this might be hard. We should mock the API requests/responses for our tests. Testing in production should be done ASAP, before we make the bCourses course public.

Will take a look into this.

Is it okay if this is only supported for CS61A right now?

I think it should be generic enough for any course to use it - bCourses will be used for multiple courses next semester.
This semester three courses (at Berkeley) are using Ok.
What part of it is harder when we have multiple courses?

It's definitely doable. We will need to store the bCourse course id and assignment ids with ok. Any recommendations on the best way to do that? Looking at the scripts that were used for uploading before, it seems they were hardcoded.

See Slack (#ok-server)

Resolved by #986


Ontario Significant Discrepancies in cases.csv

Thank you very much for the work you do. Multiple provinces have some minor variances to official Canadian numbers due to timing. And this is fine. When it comes to Ontario, your data set shows almost 2,000 cases higher than Ontario/Canada officially reported to date. Please see the attached excel with COVID19 cases cross-validation. It is definitely not due to the timing, as the gap started a few months ago and keeps on widening. I am trying to understand the nature of the difference that is unique to Ontario. If you think the data need to be fixed, I can help. I am also happy to jump on a call to discuss.
Variances in COVID19 Daily New Cases Reporting by Province.xlsx

Hi There--Thanks for your comment.
On April 1 we switched to using numbers reported by each PHU as opposed to the Ontario Ministry dataset because the Ministry numbers tend to have significant lags. As a result, the numbers we report tend to be higher than those from other sources-- but they will align with what is released daily by each PHU. We explain this further in our "About the Data" section on our dashboard-- https://art-bd.shinyapps.io/covid19canada/
Hope that helps answer your question!


Add FBInstant.getLeaderboardAsync( )

And all operations on the leaderboards themselves: https://developers.facebook.com/docs/games/instant-games/sdk/fbinstant6.0#leaderboard

Hello! We really need this functionality, we are faced with the situation that we can not release the project without it. Can you please tell me when we can expect this feature?

I can ship the Leaderboard functionality during the week starting on Monday
the 9th.
On Tue, 26 Jun 2018, 14:42 anko91<EMAIL_ADDRESS>wrote:

Hello! We really need this functionality, we are faced with the situation
that we can not release the project without it. Can you please tell me when
we can expect this feature?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/defold/extension-fbinstant/issues/8#issuecomment-400293632,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABPY0KAkmKKW5Y2i-G-9YwNdVehRPxd-ks5uAiw4gaJpZM4Sxlyf
.

I can ship this functionality during the week starting on Monday the 9th.

FYI: Work is now in progress. Likely to be completed tomorrow.


Vue3 - May need an appropriate loader

Laravel Mix Version: 6.0.0-beta.6
Node Version (node -v): v12.18.2
NPM Version (npm -v): 6.14.8
OS: Fedora 32

Description:
Getting the following error when trying to run watch:
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders

package.json:
{
    "private": true,
    "scripts": {
        "dev": "npm run development",
        "development": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --config=node_modules/laravel-mix/setup/webpack.config.js",
        "watch": "npm run development -- --watch",
        "watch-poll": "npm run watch -- --watch-poll",
        "hot": "cross-env NODE_ENV=development node_modules/webpack-dev-server/bin/webpack-dev-server.js --inline --hot --disable-host-check --config=node_modules/laravel-mix/setup/webpack.config.js",
        "prod": "npm run production",
        "production": "cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --no-progress --config=node_modules/laravel-mix/setup/webpack.config.js"
    },
    "devDependencies": {
        "@vue/compiler-sfc": "^3.0.0",
        "axios": "^0.19",
        "cross-env": "^7.0",
        "laravel-mix": "^6.0.0-beta.6",
        "lodash": "^4.17.19",
        "resolve-url-loader": "^3.1.0",
        "vue": "^3.0.0",
        "vue-loader": "^16.0.0-beta.8"
    }
}

I tried to add in latest laravel-mix together with the vue3 dependencies mentioned in other projects, was I supposed to not add those? what's the correct process to get vue3 into latest beta?
Thanks!

Did you add mix.vue() to your webpack.mix.js file?

@JeffreyWay I didn't, as all the docs seemed to mention .js() - though if I do it like that:
mix.vue('resources/js/app.js', 'public/js')
    .postCss('resources/css/app.css', 'public/css', [
        //
    ]);

it only compiles the app.css, but not the app.js, is there more missing?

You're using a brand new release (v6). Please review the docs directly on GitHub.

For anybody having the same issue:

https://github.com/JeffreyWay/laravel-mix/blob/master/docs/vue.md
https://github.com/JeffreyWay/laravel-mix/blob/master/docs/api.md#vueoptions

So the correct usage is:
mix.js('resources/js/app.js', 'public/js')
    .vue()
    .postCss('resources/css/app.css', 'public/css', [
        //
    ]);


widen 'isMigrationError' to catch constraint errors

Issue Number

#1251
Overview

On start-up, we run persistent migrations and in case of migration issues, we
execute some particular handling (e.g. the pool db resets itself). Yet, we
failed at catching migration issues coming from constraints introduced later
and that can't be satisfied on already existing data. This commit fixes it.
Before
[cardano-wallet.network:Info:22] Jörmungandr is ready.
cardano-wallet-jormungandr: SQLite3 returned ErrorConstraint while attempting to perform step: NOT NULL constraint failed: pool_owner_backup.pool_owner_index
(exiting with an error code)

After
[cardano-wallet.network:Info:22] Jörmungandr is ready.
[cardano-wallet.stake-pool-db:Error:22]  Failed to migrate the database: : NOT NULL constraint failed: pool_owner_backup.pool_owner_index
[cardano-wallet.stake-pool-db:Notice:22] Non backward compatible database found. Removing old database and re-creating it from scratch. Ignore the previous error.
[cardano-wallet.stake-pool-db:Notice:22] 1 migrations were applied to the database.
(... and continuing as normal)

Comments

bors r+


Contribution

Can i contribute this project i will add some more features

Sure, feel free to contribute any code you believe will improve the project! I think it would be best to fork this repository and create a pull request then.


⚠ Bofrost.de has degraded performance

In 341cab1, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1501 ms

Resolved: Bofrost.de performance has improved in 95e811d after 15 minutes.


Wrap bytecode::Instruction

I think it makes sense to turn bytecode::Instruction from a type alias into a struct.  Something like this:
struct BytecodeInstruction {
   insn: AbstractInstruction<ConcreteOperands>
}

This would allow me then to hide AbstractInstruction and InstructionOperands from the API altogether.  I think that would be beneficial.  A similar thing could be done for AssemblyInstruction, allowing AssemblyOperands to be hidden also.

The problem with this, however, is that it would lose the enum I think.


05 - Azure AD Privileged Identity Management  aaduser2 not permanently eligible

Module: 01
Lab/Demo: 5/ ex1
Task: 03
Step: 07
Description of issue
aaduser2 is not permanently eligible. expires in 3 months

Repro steps:

MOC-Labs-Review did not encounter this Issue while running the course.

MOC-Labs-Review did not encounter this Issue while running the course.


[Feature][framework] Support using StarRocks as the storage/analysis engine

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Why
Currently, users can choose between mysql / pg as the database system to store and analyze collected data, it works fine in most cases. However, it poses some limitations when the dataset grows too large to handle. We had to shut down our demo server twice due to storage/memory overflow, so, we can easily project that it would not be practical if we needed some large-scale analysis with Traditional RDBS (mysql/pg).
What
I propose that we investigate the possibility of adopting Distributed Columnar DBS as our storage, like StarRocks
Pros:

it supports MySQL protocol
it is Distributed, thus unlimited storage / memory and computation
it is Columnar, more efficient in storage and search

Cons:

supports a subset of Standard SQL statement, thus some queries might not be possible
bad at updating (not support?) insertion(insert rows in the middle of the table)? thus we have to redesign our data-collect-update-convert logic

How
By introducing StarRocks, we may have unlimited storage and memory, thus, support for large-scale analysis becomes possible. We may support other kinds of Big-Data.
I propose that we approach with the following steps:

Assign a Veteran Developer to investigate the StarRocks DBS, and evaluate the feasibility of the adoption.
A report should be submitted to the Community within 5 workdays.
The PPMC members should evaluate the report and make a decision in 3 workdays while all Committer could share their thoughts
We will schedule the implementation afterward

Use case
Users may run large-scale analysis in Apache DevLake
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

Investigation finished, the conclusion and solution will be addressed in next Milestone


Media essentials contents

Should it be an array?
Should it have additional EDID fields or the whole EDID?

HDCP Support uin described in the EDID

To be confirmed in the EDID spec we will refer to? Not seen

Is the set XOR'd by the device, controller or both?

I'd like to go through the above questions in some kind of order (or add some of my own). Instead I ended up writing this long mini-paper.

TL;DR: Because resources are exposed on the network, any controller can access those resources (provided authentication and security), connections are dynamic, events from the Source/Sender and Destination/Receiver need to be handled, and the aggregate of connected Destination/Receivers matters, there needs to be an interoperable mechanism to represent the media presentation session. I think that IS-XX is in the right place for this, but do not see that it can have that role as currently architected.

In IS 05, when the applications requests a connection, there is no verification that the connection was successful in the response (?), and there is nothing that happens if/when the connection is broken. Everything is presumed to be static. The Broadcast (hereinafter System) Controller is in charge. (I believe that this current situation is considered to have gaps.)
In Pro AV use cases, and also possibly ones in production environments, things might be managed, or not. There could potentially be multiple apps that are capable of browsing an RDS registry, or there might not be a registry.
Also, we are dealing with and emulating the behavior familiar to anyone using HDMI/DisplayPort/DVI base band connections, where things are dynamic. The source may change the mode at any time (InfoFrames). The monitor may be unplugged and replugged in (HPD), or the monitor may simulate this event when it needs to change its EDID to restrict or enable a mode, like enabling/disable HDR or a similar setting. Also, there is the ability to dynamically change audio latency data reported by EDID, which is signaled through CEC (out of scope, but part of the context for EDID). Things get exponentially more complicated when multiple monitors are added, especially if they can be added from multiple controllers on the network.
To me, there are two main issues:

What is the beginning and end of a connection, when the Flow can be broken and remade (HPD/InfoFrames/etc.)?
What is it that controls this session, or to put it another way, what resource contains the context for this connection?

For question 1, the start of when devices should respond to these events seems to be when the IS-04 command is issued, but where is the end? Is there an NMOS disconnect command? Does disconnection happen when the user unplugs the laptop or monitor? What owns that start/end decision?
The second question follows from the first. Applications that attempt to make connections with Senders that are responding to events from display devices need an interoperable way of aggrigating the connected receivers and the sender to coordinate their events under one resource. We can't assume that there is only one System Controller that "knows all" and has the only policy that a device will be asked to respond to.
Consider this scenario:
I'm an employee and I am sitting in the back of a large conference room. Someone has put a spreadsheet up on the screen and the text is small enough that it's hard for me to see. I have an NMOS browser on my laptop and I can see the presenter's output as an NMOS device. Can I connect to that endpoint using my app and watch it on my Laptop's display, provided that I have I'm an authenticated user on the network with appropriate permissions to access the resources? If I'm allowed to access the resources sometimes, but not at other times (like during a speaker's presentation), how does that access get revoked or constrained when it is being used? What's to stop my connection from causing the source to reset its display to accommodate me and where does that policy get set?
Because these connections are dynamic and multiple controllers have access to NMOS devices, I see a need for something to represent the "media presentation context" (a place holder name) so that control over the presentation is clear and can be clearly deleted/released when the user says that it's over, independent of a Flow's existence. I see this as the base for, or an extension of, the IS-XX API / IPMX Device Control Resource in the current architecture.

Note: There might be no need for a "media presentation context", or maybe there is another way to bring order to a system where there is foreseeable potential for multiple controllers from multiple vendors to create connections with devices. This is all IMHO, I'm open to other ideas, and I don't wish to bloat the scope of this activity. I think there is a balance between keeping within the lines of the activity and recognizing the system and domain context of the activity. People may disagree on where and when these decisions should be made.

Some loose notes on a "media presentation context" (MPC) resource:

May be created by a System Controller to represent a presentation session between a source and 0..n receivers, independent of any Flows, provided the Sender is not currently captured by an existing MPC.
Acts as the context for the sender and connected receivers, encapsulating them. Maintains the URIs of Sender and all Receivers.
Connection requests sent directly to the Sender or connected Receivers that did not come from this resource would be redirected to this resource, which could carry out the request, keeping the state consistent.
May have a direct connection (IS-07/WebSocket/etc) with each receiver and the sender
Receives and transmits events to receivers and senders
Contains timing information (source clock, epoch, grain rate), current profile, and other information related to the presentation.
Aggregates Receiver Capabilities and has logic to reduce them to one set from the aggregate (XOR) (potentially could forward this set to another resource on change and receive the XOR'd set?)
Can limit the number of connected receivers (and express those limits), e.g. HDCP requirements
Can be nested*
Is deleted when the connection is done, independent of any Flows.

*The implementation of this resource might be made by the System Controller, or could be made by the device. If the device and the System Controller both implement an MPC resource, then the System Controller can encapsulate the device's MPC under its own, effectively limiting it to forwarding events to its own MPC. That is, the device is captured by its MPC, which is captured by the System Controller MPC. There might be other applications for this sort of nesting (out of scope), especially when there are processing devices in between.

HDCP Support uin described in the EDID. To be confirmed in the EDID spec we will refer to? Not seen

HDCP existence is not in the EDID payload. It is a separate register over the same I2C bus (in HDMI) and there is a protocol for discovering its existence. While it is not in the EDID payload, it's possible that we might want to consider it to be within scope, as it is part of the Destination's properties/capabilities. We may also decide to extend this API later, when we tackle support for EDID.

Should it have additional EDID fields or the whole EDID?

We should have an end point for the raw EDID, to cover improperly formed EDID data/debugging, and data not included in Receiver Capabilities.
I also think that we should do what is essential to create flows in this activity and define how manufacturers may include more EDID information, if desired. The goal should be interoperability and potentially the ability to round-trip EDID data, as much as it makes sense to do that.


Github thinks action ran OK when it failed

It looks like a transient error, but in the https://github.com/Mudlet/Mudlet/pull/4739/checks?check_run_id=1821768606 run the action failed - yet github thinks it was ok:

@vadi2 i spotted where the error is, thanks for the report!

@vadi2 fixed in v6.3

Thanks man.


Hey! This looks pretty sweet!

I was searching for something that wasn't MDX Deck and found this!
Looks like you have done a great job here than you so much, I was just trying to get my head around if I could import MDX Embed into this, I'm guessing I have to do it on a slide by slide basis?
Like with the wrapper components?

Hey, thanks for your interest in MDXP!
I kinda lost track of this project (still use almost weekly to create presentations though), but I will get back to it soon and fix some annoying things I noticed!
Now for MDX Embed, I don't really think you need anything special, seeing as one of their examples literally is to include their components into MDX.
I did not test anything, but I guess you have 2 options:

Add the MDX Embed components to the MDXProvider. You can do this with the components argument of Deck, which you can find in src/index.jsx, provided you used the webpack template.
Adding the components to the MDXProvider, simply means you do not need to import them into your MDX files. Unless they do something weird (eg. intialisation code) when importing the components, you should be able to import them straight in your MDX files as well:

import { CodePen } from 'mdx-embed';

# Slide 1

<CodePen />

---

Let me know if you have any other problems!

I used MDX Embed np, here's the presentation: https://i-have-a-hammer.vercel.app/#/normal/0/0
Sauce: https://github.com/spences10/i-have-a-hammer/

Thanks for sharing! Do you mind if I add it to the examples page ? :innocent:

Yeah, no probs
Regards,
Scott
Sign up to my Newsletter https://ss10.dev/nl for helpful links and tips.
scottspence.com
On Wed, 24 Feb 2021 at 14:33, 0phoff<EMAIL_ADDRESS>wrote:

Thanks for sharing! Do you mind if I add it to the examples page ? 😇
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/0phoff/MDXP/issues/2#issuecomment-785117027, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AABZJVEPS7TI6ZUK5VJQKDTTAUE3ZANCNFSM4XVFYXXA
.


Authorization manager check missing for WIF3.5

No exception is thrown when using WIF

Sorry - this repo is not maintained anymore.


Update Pages “TermiteInspectionCostOnTheGoldCoast”

Automatically generated by Netlify CMS

👷 Deploy Preview for chic-shortbread-66a66b processing.

Name
Link

🔨 Latest commit
4033aeadb4711b8c32944e784a5d1e1cae6adc9f

🔍 Latest deploy log
https://app.netlify.com/sites/chic-shortbread-66a66b/deploys/655309ec60ca930008e13db4


Add Joyent Triton discovery

This commit adds support for discovering containers running on a Joyent Triton cloud (private or public).
I have implemented a Prometheus compatible exporter for Triton. The architecture is described in RFD 27 and RFD 37. You can also take a look at the source by visiting triton-cmon and triton-cmon-agent
If you'd like to verify the functionality of this commit, you may do so by running Triton in a VM and then following the setup guide.
Alternatively, you can reach out to me and I will get you access to our east-3b public cloud beta deployment which has everything running already. The east-3b setup guide is located here

Thanks for your contribution.
Note that we have to apply a pretty high bar for adding more SD mechanisms to the Prometheus codebase. We strongly prefer supporting more SD mechanisms via the file-based SD. Have a look at #2221 for a similar discussion.
Essentially we need to be convinced that…

…you will be available to maintain the code and not just disappear at some point (as many others did, even after having pledged to maintain the code.)
…the SD mechanism in question is in common use and mature enough to justify direct integration.
…there is a technical advantage of direct integration (like the Kubernetes watches), i.e. the code in the main Prometheus binary is more than essentially a cron job moved into the Prometheus binary.

Please consider the points above and the discussion in PR #2221 and then follow up here with your conclusions.
The person most involved with SD and thus the most qualified gate keeper is probably @fabxc.

...you will be available to maintain the code and not just disappear at some point (as many others did, even after having pledged to maintain the code.)

Understood, and we (Joyent a fellow CNCF member) have no intention of abandoning this code, quite the opposite actually. Triton Service Discovery is an integral piece of our monitoring and metrics offering.
With that said, I believe the most compelling case I can make for non-abandonment is that we're integrating this into our mature and widely used product, which is also an open source project. Additionally, as CNCF members ourselves, we have a compelling reason to support and help maintain Prometheus.

...the SD mechanism in question is in common use and mature enough to justify direct integration.

Myself, colleagues, and a few early adopting customers have been using this SD mechanism for a while now. Unfortunately, without promoting our fork (which seems counterproductive since our intention is to help promote and foster usage of Prometheus), I'm not sure how it is possible to satisfy this requirement without actually being included in Prometheus already.

…there is a technical advantage of direct integration (like the Kubernetes watches), i.e. the code in the main Prometheus binary is more than essentially a cron job moved into the Prometheus binary.

The technical advantage of direct integration is that authentication and authorization are greatly simplified, as is labeling support. This is, however, on a timer because it was modeled after the SD mechanisms that had already been included in Prometheus many months ago. I could expose triggered events to Prometheus (similar to the Kubernetes watches functionality that is described in PR #2221) and remove the timer in favor of a push mechanism if that makes integration more compelling.
In PR #2221, they mention a lack of integration tests as a blocker. I would be happy to add integration tests to this PR. I actually have my own set of integration tests for our discovery endpoint and the main reason for not including integration tests with this PR is that I saw no clear example of how you and the other maintainers would like that to be done.
Thank you for your help and consideration. How shall we proceed?

...the SD mechanism in question is in common use and mature enough to justify direct integration.

Myself, colleagues, and a few early adopting customers have been using this SD mechanism for a while now. Unfortunately, without promoting our fork (which seems counterproductive since our intention is to help promote and foster usage of Prometheus), I'm not sure how it is possible to satisfy this requirement without actually being included in Prometheus already.

To clarify, @beorn7 meant general use of Triton's SD, not Prometheus-specific. So: are there many people out there in the world who use Triton's SD mechanism to discover services already, independently of Prometheus?

@juliusv Yes, there are a large number of people who use our endpoints for service discovery. Either via the cert based endpoint that this PR consumes or our HTTP-signature based endpoint.
Examples:

Hashicorp Terraform Triton Provider
-Autopilot
-Docker via sdc-docker

We also have a number of very large reference users (some of them customers, some of them open source) and I can investigate which ones I can name publicly if that is needed.

Thanks, those points (including willingness to maintain the code and supplying integration tests) all point in a good direction already. The decision here still lies with @fabxc and @beorn7 though.

Hey @fabxc and @beorn7, sorry that took so long. I believe I've addressed all of your review and I've added tests for Triton Discovery as well as added Triton Discovery to the config tests.
Let me know if I missed something. Thanks in advance for the review!

Thanks for the fixes. LGTM after comments.

👍 thanks.
To complete this, could you file a PR against the next-release branch of prometheus/docs adding the SD to https://github.com/prometheus/docs/blob/master/content/docs/operating/configuration.md?
The SD should be marked as "beta state" like several others.

@fabxc yep, can do. Thanks!


Configuration details，release configuration object pop-up window, change the lower right button to "release"

发布配置对象弹窗，右下角按钮文案修改为“发布”

resolved


Fixed #20495 -- Added login failure events to security logger.

https://code.djangoproject.com/ticket/20495

Closing per ticket.


why can't install ?

~/... $ pip install seasnake
Collecting seasnake
Could not find a version that satisfies the requirement seasnake (from versions: )
No matching distribution found for seasnake
what it can be?

If you check PyPI, you'll see that the "current version" is 0.0.0 - That is, I never uploaded a version to PyPI.
This project was an experiment; I've since abandoned the experiment, so you'll need to use a checkout of the code.


panic with --values

I'm probably misunderstanding the purpose of --values flag, but I was trying it on various JSON inputs and saw Go panics in some cases :boom: (and nothing in others).
Here are pretty small reproducers (on latest master), which are weirdly sensitive to whitespace:
$ printf '{"foo": 3}' | ./gron --values
$ printf '{"foo":\n3}' | ./gron --values
$ printf '{"foo":\n  3}' | ./gron --values
panic: runtime error: index out of range [0] with length 0

goroutine 1 [running]:
main.gronValues({0xc000196120?, 0xc00019a010?}, {0xc000192190?, 0x75e498?}, 0x1?)
	/home/beni/gron/main.go:411 +0x2af
main.main()
	/home/beni/gron/main.go:178 +0x6cd
$ printf '{"foo": 3\n}' | ./gron --values
$ printf '{"foo": 3\n  }' | ./gron --values
panic: runtime error: index out of range [0] with length 0

goroutine 1 [running]:
main.gronValues({0xc00007c180?, 0xc000016050?}, {0xc00001a2a8?, 0x75e498?}, 0x1?)
	/home/beni/gron/main.go:411 +0x2af
main.main()
	/home/beni/gron/main.go:178 +0x6cd

I saw this too and was confused. For example if I'm trying to extract some disk details:
$ nvme list -o json | gron -v
panic: runtime error: index out of range [0] with length 0

goroutine 1 [running]:
main.gronValues({0xc000126070?, 0xc00012a010?}, {0xc000142170?, 0x7555d8?}, 0x1?)
	github.com/tomnomnom/gron/main.go:411 +0x27f
main.main()
	github.com/tomnomnom/gron/main.go:178 +0x6bc

The solution is to run gron twice in a row:
$ nvme list -o json | gron | gron -v
/dev/nvme0n1

0
0

1
0
Non-Volatile memory controller: Toshiba Corporation NVMe SSD Controller
1

0
/dev/nvme1n1

1
0

1
0
Non-Volatile memory controller: Toshiba Corporation NVMe SSD Controller
1

0

This is alluded to in the comments:
https://github.com/tomnomnom/gron/blob/badf401da553eb41b7ffde4be6a64809ed0ed846/main.go#L401-L404
but not in the docs and it threw me off too. Maybe it can be explained with an example, or mentioning "Print just the values of gron-format assignments"?


SluggableBehavior causes memory exhausting with unique slug

The reason for this is UniqueValidator misconfiguration but at the moment it is not detected and causes memory exhausting through infinite validation loop.
With the current SluggableBehavior construction it is not possible to throw exception informing about this but should not be that difficult to fix. Anyway - just reporting this for your information.
What steps will reproduce the problem?

Create DB table with 'name' and 'slug' columns (among others).
Create ActiveRecord model for the table.
Add few records there with the same 'name'.
Add behavior configuration for the AR:

    public function behaviors()
    {
        return [
            [
                'class'           => \yii\behaviors\SluggableBehavior::className(),
                'immutable'       => false,
                'attribute'       => 'name',
                'ensureUnique'    => true,
                'uniqueValidator' => ['targetAttribute' => 'name'],
            ]
        ];
    }

(targetAttribute does not include slug attribute)
5. Update one of the previously added records.
What is the expected result?
InvalidConfigException thrown "UniqueValidator configuration doesn't allow to create unique slug".
What do you get instead?
Fatal error - memory exhausted.
Additional info
I know this is because of the UniqueValidator misconfiguration. makeUnique() method enters infinite loop here. Still - this configuration is good for one DB row so cannot be rejected all the time.
We could detect the problem by checking the validation query - if it's the same on the second loop iteration it means the validation will always return false - and exception can be thrown. The problem is there is no easy way to check this query right now.
What do you think?

It's just another way how you can shoot yourself in the foot :) Thank you for the report, but I don't think that it's really necessary to introduce more logic for each slug generation just to prevent misconfiguration.

@SilverFire i agree this is a missconfiguration, but I wanna call your attention on something else.
    protected function validateSlug($slug)
    {
        /* @var $validator UniqueValidator */
        /* @var $model BaseActiveRecord */
        $validator = Yii::createObject(array_merge(
            [
                'class' => UniqueValidator::className()
            ],
            $this->uniqueValidator
        ));
        $model = clone $this->owner;
        $model->clearErrors();
        $model->{$this->slugAttribute} = $slug;
        $validator->validateAttribute($model, $this->slugAttribute);
        return !$model->hasErrors();
    }

Wouldn't it make sense to make $validator and $model into static variables so they are not created and destroyed each validation?

I would like also to suggest optimisation of default unique slug creation mechanism. Instead of checking every slug-N+1 existing entry we could get the highest N at the beginning so for 101st row with the same base slug we can do 2 queries instead of 102.

https://github.com/yiisoft/yii2/pull/4675#discussion_r16093242


[fix]: Add responsiveness on mobile

closes #10
@phyleria @Khadeeejah

I've noticed some minor issues, with the community care width, I'll just create a PR for it @phyleria

Sure, please go ahead


Update it-IT translation

Idk but somethings wrong from appveyor with the translation. I'll try again


Show latest git commit SHA in rendered page

this should be simple:

use a solution from https://stackoverflow.com/questions/14989858/get-the-current-git-hash-in-a-python-script (also see #179 ) and then send this to the templates
in the base template, put the template variable in an HTML comment or as a meta tag

Why, out of curiosity? @sumanthratna

Why, out of curiosity? @sumanthratna

it's easier to tell if a change has been deployed (which is useful if the change was only in the backend)


Custom Properties on webpack config will be no longer allowed after beta.22

See: https://github.com/webpack/webpack/pull/2974
I know that you guys are not yet on webpack2. But I wanted to make ya'll are aware that we will start validating the configuration out of the box, and will prohibit custom properties on ones webpack config. You can see the migration path on the issue but I'll leave it here anyways.
Users now will need to use LoaderOptionsPlugin({}). Therefore the following example:
module.exports = config;

const config = {
  entry: './src/index.js',
  output: {
    filename: 'foo.chunk.js',
    path: './dist'
  },
  sassLoader: {
    includePaths: [
      /*...*/
    ]
  }

};

Will need to be migrated to look as follows:
const webpack = require('webpack');

module.exports = config;

const customLoaderOptions = {
  sassLoader: {
      includePaths: [
        /*...*/
      ]
    }
};

const config = {
  plugins: [
    webpack.LoaderOptionsPlugin({
      options: customLoaderOptions;
    });
  ]
};

Keep up all the good work. You guys are doing a great job for the community.

Thanks for the heads-up. Linked to this issue from #183 so I’ll close it.


Add option to get missing dependencies.

For some time now, depcheck also supports getting missing dependencies, i.e. dependencies that are being used in the code, but have not been added to the package.json file.
This was currently missing in gulp-depcheck, so I added it.

@mcasimir Ping ;-)

Ping ;-)


No cyber monitor channel info on aarch64 platform

We appreciate you go through Apollo documentations and search previous issues before creating an new one. If neither of the sources helped you with your issues, please report the issue using the following form. Please note missing info can delay the response time.
System information

OS Platform and Distribution (e.g., Linux Ubuntu 18.04): 18.04
Apollo installed from (source or binary): source
Apollo version (3.5, 5.0, 5.5, 6.0): 6.0
Output of apollo.sh config if on master branch:

Steps to reproduce the issue:

Please use bullet points and include as much details as possible:
After build with apollo.sh build_cpu on aarch64 platform, we run cyber monitor but couldn't see any channel info.
However we could see cyber monitor channel info with x86 platform, we launch cyber_monitor

In addition, tried to run setup on Dreamview, it didn't work properly.
Here is the mainboard log, could see lots of msg like "No HMIStatus was received"
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
W1013 13:20:06.310149 11783 scheduler_factory.cc:63] No sched conf found, use default conf.
I1013 13:20:06.338225 11860 processor.cc:42] processor_tid: 11860
I1013 13:20:06.343614 11862 processor.cc:42] processor_tid: 11862
I1013 13:20:06.345079 11863 processor.cc:42] processor_tid: 11863
I1013 13:20:06.346417 11864 processor.cc:42] processor_tid: 11864
I1013 13:20:06.347702 11865 processor.cc:42] processor_tid: 11865
I1013 13:20:06.348906 11866 processor.cc:42] processor_tid: 11866
I1013 13:20:06.350189 11868 processor.cc:42] processor_tid: 11868
I1013 13:20:06.351789 11869 processor.cc:42] processor_tid: 11869
I1013 13:20:06.352439 11870 processor.cc:42] processor_tid: 11870
I1013 13:20:06.354063 11872 processor.cc:42] processor_tid: 11872
I1013 13:20:06.358233 11876 processor.cc:42] processor_tid: 11876
I1013 13:20:06.359668 11879 processor.cc:42] processor_tid: 11879
I1013 13:20:06.360954 11880 processor.cc:42] processor_tid: 11880
I1013 13:20:06.362278 11881 processor.cc:42] processor_tid: 11881
I1013 13:20:06.364423 11882 processor.cc:42] processor_tid: 11882
I1013 13:20:06.365630 11883 processor.cc:42] processor_tid: 11883
I1013 13:20:06.368389 11783 init.cc:113] Register exit handle succ.
I1013 13:20:06.435165 11783 module_controller.cc:65] Start initialize dag: /apollo/modules/monitor/dag/monitor.dag
I1013 13:20:06.436000 11783 class_loader.cc:37] Begin LoadLibrary: /apollo/bazel-bin/modules/monitor/libmonitor.so
I1013 13:20:07.347242 11783 timer.cc:137] start timer [0]
I1013 13:20:07.852710 11919 scheduler.cc:55] create croutine: /internal/task0
I1013 13:20:07.855895 11919 scheduler.cc:55] create croutine: /internal/task1
I1013 13:20:07.856909 11919 scheduler.cc:55] create croutine: /internal/task2
I1013 13:20:07.857237 11919 scheduler.cc:55] create croutine: /internal/task3
I1013 13:20:07.857360 11919 scheduler.cc:55] create croutine: /internal/task4
I1013 13:20:07.857470 11919 scheduler.cc:55] create croutine: /internal/task5
I1013 13:20:07.857614 11919 scheduler.cc:55] create croutine: /internal/task6
I1013 13:20:07.857743 11919 scheduler.cc:55] create croutine: /internal/task7
I1013 13:20:07.857846 11919 scheduler.cc:55] create croutine: /internal/task8
I1013 13:20:07.857955 11919 scheduler.cc:55] create croutine: /internal/task9
I1013 13:20:07.858057 11919 scheduler.cc:55] create croutine: /internal/task10
I1013 13:20:07.858181 11919 scheduler.cc:55] create croutine: /internal/task11
I1013 13:20:07.858287 11919 scheduler.cc:55] create croutine: /internal/task12
I1013 13:20:07.858392 11919 scheduler.cc:55] create croutine: /internal/task13
I1013 13:20:07.858490 11919 scheduler.cc:55] create croutine: /internal/task14
I1013 13:20:07.858587 11919 scheduler.cc:55] create croutine: /internal/task15
W1013 13:20:07.863255 11919 rate.cc:96] Detect forward jumps in time
I1013 13:20:07.878255 11866 scheduler.cc:55] create croutine: monitor_/apollo/hmi/status
E1013 13:20:07.892388 11866 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:08.361491 11869 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:08.863502 11879 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:09.363525 11872 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:09.863494 11880 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:10.363456 11868 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:10.863510 11860 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:11.363548 11883 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:11.863476 11860 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:12.363576 11880 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:12.863494 11862 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:13.363538 11872 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:13.863463 11879 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:14.363478 11872 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:14.863478 11860 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:15.363478 11862 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:15.863483 11860 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:16.363474 11862 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:16.863448 11872 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:17.363523 11860 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:17.863483 11880 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:18.363514 11865 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:18.863505 11879 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:19.363400 11872 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:19.863559 11862 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:20.363462 11879 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:20.863569 11880 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:21.363499 11872 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:21.863554 11876 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:22.363487 11880 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:22.863570 11866 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:23.363569 11872 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:23.863485 11880 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:24.363533 11865 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:24.863487 11872 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:25.363541 11866 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:25.863483 11879 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:26.363481 11868 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:26.863539 11865 monitor_manager.cc:52] No HMIStatus was received.
E1013 13:20:27.364100 11879 monitor_manager.cc:52] No HMIStatus was received.
W1013 13:20:27.367861 11919 rate.cc:96] Detect forward jumps in time
E1013 13:20:27.866706 11866 monitor_manager.cc:52] No HMIStatus was received.
W1013 13:20:27.869680 11919 rate.cc:96] Detect forward jumps in time
W1013 13:20:27.869976 11919 rate.cc:96] Detect forward jumps in time
E1013 13:20:28.362707 11880 monitor_manager.cc:52] No HMIStatus was received.
W1013 13:20:28.365656 11919 rate.cc:96] Detect forward jumps in time
W1013 13:20:28.365849 11919 rate.cc:96] Detect forward jumps in time
E1013 13:20:28.862758 11882 monitor_manager.cc:52] No HMIStatus was received.
W1013 13:20:28.865278 11919 rate.cc:96] Detect forward jumps in time
E1013 13:20:29.362699 11876 monitor_manager.cc:52] No HMIStatus was received.
W1013 13:20:29.365859 11919 rate.cc:96] Detect forward jumps in time
E1013 13:20:29.864784 11866 monitor_manager.cc:52] No HMIStatus was received.
It looks like that communication was not established properly.
Is this issue related with fast-rtps?
We were told that fast-rtps has some problems for aarch64.
Supporting materials (screenshots, command lines, code/script snippets):

If you are not running across physical machines, cyber just uses shared memory for communication. So I don't think this is a problem for fastrtps.
Can you observe and provide more information?

Thx for your comment:-). we will check it.
For your information, we built an apollo on arm64 container on top of x86 machine and run cyber monitor.
Do you think that this is a problem?
Cross compile doesn't work?
One question, we build an apollo with arm64 container on top of x86 machine and copy all libs which is required apollo module into arm64 machine and run apollo.
Apollo can work with this use case?

Can you show your gcc version in docker?
gcc -v

gcc version is 7.5.0 in the docker.

Could you pls print the whole info

Here we go.
[yschung@in-dev-docker:/apollo]$ gcc -v
Using built-in specs.
COLLECT_GCC=/usr/bin/gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/aarch64-linux-gnu/7/lto-wrapper
Target: aarch64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 7.5.0-3ubuntu1~18.04' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs --enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-7 --program-prefix=aarch64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-libquadmath --disable-libquadmath-support --enable-plugin --enable-default-pie --with-system-zlib --enable-multiarch --enable-fix-cortex-a53-843419 --disable-werror --enable-checking=release --build=aarch64-linux-gnu --host=aarch64-linux-gnu --target=aarch64-linux-gnu
Thread model: posix
gcc version 7.5.0 (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04)

I don't have ideas about cross-compilation problem for now, so I suggest you check the log to see if there is more information

Regarding cyber_monitor issue, which logs should I check? Do you have any idea?

my suggestion is

Use the sample "cyber\examples\talker.cc" and "cyber\examples\listener.cc" to ensure can't receive messages.
If still can't receive msgs try to find some error msg in mainborad.INFO

Thx for your input.
Checked talker and listener.
When I had a test, couldn't find any mainboard.INFO.
My test step.
Step 1. run talker
Step 2. run listener
Talker log
Log file created at: 2020/10/15 09:30:44
Running on machine: in-dev-docker
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
I1015 09:30:44.221801 17400 global_data.cc:153] host ip: <IP_ADDRESS>
W1015 09:30:44.278313 17400 scheduler_factory.cc:63] No sched conf found, use default conf.
I1015 09:30:44.286744 17404 processor.cc:42] processor_tid: 17404
I1015 09:30:44.289849 17405 processor.cc:42] processor_tid: 17405
I1015 09:30:44.291539 17406 processor.cc:42] processor_tid: 17406
I1015 09:30:44.292129 17407 processor.cc:42] processor_tid: 17407
I1015 09:30:44.293061 17408 processor.cc:42] processor_tid: 17408
I1015 09:30:44.294042 17409 processor.cc:42] processor_tid: 17409
I1015 09:30:44.294667 17410 processor.cc:42] processor_tid: 17410
I1015 09:30:44.295504 17411 processor.cc:42] processor_tid: 17411
I1015 09:30:44.296382 17412 processor.cc:42] processor_tid: 17412
I1015 09:30:44.297646 17413 processor.cc:42] processor_tid: 17413
I1015 09:30:44.298421 17414 processor.cc:42] processor_tid: 17414
I1015 09:30:44.299028 17415 processor.cc:42] processor_tid: 17415
I1015 09:30:44.300446 17416 processor.cc:42] processor_tid: 17416
I1015 09:30:44.301184 17417 processor.cc:42] processor_tid: 17417
I1015 09:30:44.301800 17418 processor.cc:42] processor_tid: 17418
I1015 09:30:44.302968 17419 processor.cc:42] processor_tid: 17419
I1015 09:30:44.305274 17400 init.cc:113] Register exit handle succ.
I1015 09:30:44.416141 17400 talker.cc:43] talker sent a message! No. 0
I1015 09:30:45.416399 17400 talker.cc:43] talker sent a message! No. 1
I1015 09:30:46.414901 17400 talker.cc:43] talker sent a message! No. 2
I1015 09:30:47.414952 17400 talker.cc:43] talker sent a message! No. 3
I1015 09:30:48.414937 17400 talker.cc:43] talker sent a message! No. 4
I1015 09:30:49.414943 17400 talker.cc:43] talker sent a message! No. 5
I1015 09:30:50.414965 17400 talker.cc:43] talker sent a message! No. 6
I1015 09:30:51.414912 17400 talker.cc:43] talker sent a message! No. 7
I1015 09:30:52.414950 17400 talker.cc:43] talker sent a message! No. 8
I1015 09:30:53.414894 17400 talker.cc:43] talker sent a message! No. 9
I1015 09:30:54.414960 17400 talker.cc:43] talker sent a message! No. 10
I1015 09:30:55.414888 17400 talker.cc:43] talker sent a message! No. 11
I1015 09:30:56.414906 17400 talker.cc:43] talker sent a message! No. 12
I1015 09:30:57.414965 17400 talker.cc:43] talker sent a message! No. 13
I1015 09:30:58.414959 17400 talker.cc:43] talker sent a message! No. 14
I1015 09:30:59.414875 17400 talker.cc:43] talker sent a message! No. 15
I1015 09:31:00.414963 17400 talker.cc:43] talker sent a message! No. 16
I1015 09:31:01.414921 17400 talker.cc:43] talker sent a message! No. 17
I1015 09:31:02.414955 17400 talker.cc:43] talker sent a message! No. 18
I1015 09:31:03.414945 17400 talker.cc:43] talker sent a message! No. 19
I1015 09:31:04.414911 17400 talker.cc:43] talker sent a message! No. 20
I1015 09:31:05.414896 17400 talker.cc:43] talker sent a message! No. 21
I1015 09:31:06.414896 17400 talker.cc:43] talker sent a message! No. 22
I1015 09:31:07.414953 17400 talker.cc:43] talker sent a message! No. 23
I1015 09:31:08.414950 17400 talker.cc:43] talker sent a message! No. 24
I1015 09:31:09.414903 17400 talker.cc:43] talker sent a message! No. 25
I1015 09:31:10.414952 17400 talker.cc:43] talker sent a message! No. 26
I1015 09:31:11.414954 17400 talker.cc:43] talker sent a message! No. 27
listener log
Log file created at: 2020/10/15 09:31:43
Running on machine: in-dev-docker
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
I1015 09:31:43.466289 17809 global_data.cc:153] host ip: <IP_ADDRESS>
W1015 09:31:43.522676 17809 scheduler_factory.cc:63] No sched conf found, use default conf.
I1015 09:31:43.531294 17820 processor.cc:42] processor_tid: 17820
I1015 09:31:43.533795 17821 processor.cc:42] processor_tid: 17821
I1015 09:31:43.535776 17822 processor.cc:42] processor_tid: 17822
I1015 09:31:43.536972 17823 processor.cc:42] processor_tid: 17823
I1015 09:31:43.538237 17824 processor.cc:42] processor_tid: 17824
I1015 09:31:43.539523 17825 processor.cc:42] processor_tid: 17825
I1015 09:31:43.540091 17826 processor.cc:42] processor_tid: 17826
I1015 09:31:43.540760 17827 processor.cc:42] processor_tid: 17827
I1015 09:31:43.542351 17828 processor.cc:42] processor_tid: 17828
I1015 09:31:43.543697 17829 processor.cc:42] processor_tid: 17829
I1015 09:31:43.544430 17830 processor.cc:42] processor_tid: 17830
I1015 09:31:43.545033 17831 processor.cc:42] processor_tid: 17831
I1015 09:31:43.546715 17832 processor.cc:42] processor_tid: 17832
I1015 09:31:43.547336 17833 processor.cc:42] processor_tid: 17833
I1015 09:31:43.548130 17834 processor.cc:42] processor_tid: 17834
I1015 09:31:43.548754 17835 processor.cc:42] processor_tid: 17835
I1015 09:31:43.551106 17809 init.cc:113] Register exit handle succ.
I1015 09:31:43.649137 17809 scheduler.cc:55] create croutine: listener_channel/chatter
With this logs, couldn't find any clue what's going wrong.:-(
Any idea?

There is too little prompt information, you can open the debug log.

modify the "apollo/cyber/setup.bash"

 # for DEBUG log
 #export GLOG_minloglevel=-1   // DO NOT ENABLE THIS!!!
 export GLOG_v=4

Enable environment variables

source cyber/setup.bash

Then run the example and see the debug log

Running aarch64 CyberRT docker image on top of x86_64 host is not recommended or supported officially by the team.
Tested playing the demo_3.5.record on Xavier, and use cyber_monitor to observe, everything seems OK.
python3 docs/demo_guide/record_helper.py demo_3.5.record
cyber_recorder play -f demo_3.5.record --loop
# Another terminal
cyber_monitor

So this issue is going to be closed. Thanks for using Apollo.

For your information, we built an apollo on arm64 container on top of x86 machine and run cyber monitor.
Do you think that this is a problem?
Cross compile doesn't work?
One question, we build an apollo with arm64 container on top of x86 machine and copy all libs which is required apollo module into arm64 machine and run apollo.
Apollo can work with this use case?

@younggam94 did you have solved this?


Auto-Login Implemented - Add FC Function Support

General

Cleaner Code and more Comments
Added config_functions.py (with 2 config functions that can be used with discord_rich_presence.py and nso_functions.py)
Updated the requirements.txt with new Packages
Setup.py has a Upgrade PIP to latest version function (because Python 3.6.X has a lower PIP version)
Updated the README.md

Cookie Generation

The user can finally choose between two methods: Auto-Login Cookie Generation(Faster) and Manual Cookie Generation (Using mitmproxy, safer)
Fixed a problem when the RP won't start right up after the Cookie has been manually retrieved
Added a link to the Cookie Generation Section (from the Splatnet2Statink Rep.) at the beginning of the code to warn the user before choosing a desired method.

Friend Code

Created a new function where the user can add their Switch FC (after choosing a desired Cookie Generation Method)
User can also decide to skip this part when they're not feeling it (the RP will show then "FC: Not Given"

Misc

The Video Tutorial will be updated because of these changes. Of course I'll credit you in the vid for making this awesome RP! =)

I'd like to report an error that happened to me when I was trying to run the script (Auto login worked BTW)

Huh, that's a bit weird. Cause I've tested it on 3 different machines (my Laptop, my PC and my Work PC) and functioned normal after running the script. I will take a look how to fix it when I'm back home.
At least thank you for letting me know! And good to hear the Auto-Login works!

If this has fixed auto login, then I'm happy to merge this - the other bug is likely something that can be fixed in an upcoming commit.

Ah, I see that Wolfy is using Python 3.7.X. I'm currently using Pyhton 3.6.0 and the script works fine with that. Maybe that could be the problem? (Just a thought)

https://github.com/valknight/Splatnet2-Rich-Presence/blob/1ad92cf70c9c9e676693f1c18a96de52810fa0dc/nso_functions.py#L277
You've essentially taken the entirety of my project's iksm.py without asking, but whatever...
I've noticed you're using "splatnet2statink" as your user agent, falsely masquerading as my script both to me and NexusMine's API (which he has presumably not given you permission to use). This puts all projects at risk of being shut down due to unauthorized usage of another user's API. In addition, unless I missed something, you didn't reach out to me to get permission to send requests to my API and are violating the usage guidelines by 1) not requesting permission or notifying me, which I gladly would have given you; 2) as specified before, not sending a unique user agent.
Please address this ASAP.

Thank you for your comment.
First, I want to apologize you for not reaching you out to ask for any Permission and not giving you an unique user agent.
I'm gonna give your wiki (from your Splatnet2statink) a better read regarding the api, security and privacy. I will also delete my fork just in case.
Again, thank you for addressing this and I'm sorry.
I hope there's a way to undo this merge.

The commits has been reversed - if anyone wants to do this without using an API endpoint without permission, that would be rad.

@valknight Sorry for the late reply here! (@HHK3, also saw your Twitter message last night right as I was headed to bed but haven't had a chance to reply yet, but think this should address that as well.)
To both of you, sorry if my comments came off as harsh or drastic. Typed it on mobile too so I was a bit more rushed. I'm 100% fine with you using the s2s API or re-implementing the login/cookie generation code in your script (it is public & available in even more detail than combing through my code or docs, after all)! – just that I would appreciate you using a unique user agent so I know what requests are coming from who and all scripts or projects using it are being faithful about their identities… Of course there's no real way to 100% enforce this – any number of people could be spoofing s2s or other user agents for whatever reason – but on the basis of good faith, I wanted to just make you aware of the user agent issue as it existed, and to note that I believe it's a benefit to all (including your users) to be transparent about these sorts of API requests, etc. especially as this is all working in a domain not really supported or endorsed by Nintendo. The docs also contain other (hopefully) useful information that I think is good for others – developers and users – to know. Let's work to add this functionality back in to your project, though, as it will definitely benefit users.
I would note that I'd also reach out to NexusMine on Twitter (Google Translate + DM him at the very least?) to ask if you can use his API to generate f tokens, given a hash provided by mine (which he gave me instructions on how to do). Where this is coming from is that he's been a little reluctant to even let me use his API in the past – he created it on what he's described as a small, unstable, personal server just for his closed-source app, it has 0 documentation, etc. –and I just fear any increase in requests without notice may make him consider reversing that decision for all other current or potential developers as a whole.

Also (at risk of being sounding a little too anal about this), if you do want to directly use the code from my project's iksm.py (with credit at the top of the file, please), I'd request that you change this repo's license from MIT to the tiny-bit-more-restrictive GPLv3, which splatnet2statink is licensed under (MIT is compatible with GPL but not vice versa). This ensures the code which is being repurposed in your repo doesn't get used by others in a non-open source manner.

Thank you for the comment, @frozenpandaman . I'm pleased to hear from you that we can add this functionality back into the project, as it will definitely benefit the user. Also, thank you for your explanation about User-Agents. I'll attempt to contact NexusMine on Twitter in the next few days.
In case you don't mind and @valknight is okay with changing the repo's license from MIT to GPLv3, I'd like to use your "Cookie Generation" code from your project's iksm.py (I’ll make sure to give credits to you and NexusMine on the top of nso_functions.py). I'll also be sure to use a custom User-Agent in the code.
I am also planning to create a video tutorial on how users can set up the Splatoon 2 Rich Presence on their Discord profile. If you and NexusMine (which I’m going to ask as well) want to, I'll credit you two and ValKnight at the beginning of the video and in the description. I will also provide step-by-step instructions on how to generate it automatically and making sure to alert viewers that generating a cookie automatically involves making requests to a non-Nintendo server. In addition, I will also show how it can be done manually using Mitmproxy and the Android emulator Nox.
I hope to hear from you soon. Thank you and have a nice day! =)


Unusable with devise/warden authentication

Hi,
We are using Devise and I wanted to map out the current API documentation so that we can move it over to a stateless one. For now however a regular devise session/cookie implementation is used for authentication. I have been unsuccessful in finding a solution that works. What are you using behind the scenes? I have been trying both acceptance (capybara) and controller specs but both fail on the authentication. I've tried stubbing warden but that doesn't help either and nothing in https://github.com/plataformatec/devise/wiki/How-To:-Test-controllers-with-Rails-3-and-4-(and-RSpec) seems to help.
# app/controllers/api/accounts_controller_spec.rb
class Api::AccountsController < Api::BaseController
  def show
    @account = AccountShow.get(customer_uid: current_user.customer_uid, account_id: params[:id])
  end
end

# spec/controllers/api/accounts_controller_spec.rb
require 'acceptance_helper'
RSpec.describe Api::AccountsController, type: :controller do
  let(:user) { FactoryGirl.create :user }

  resource 'Account' do
    context 'signed in' do
    end
    before do
      sign_in user
      header 'Content-Type', 'application/json'
      header 'Accept', 'application/json'
    end

    get '/api/accounts/:id' do
      let(:id) { user.id }
      example_request 'Get account by id' do
        expect(path).to eq("/api/accounts/#{id}")
        expect(status).to eq(200)
        expect(headers).to match('Content-Type' => 'application/json', 'Accept' => 'application/json')
      end
    end
  end
end

# spec/acceptance_helper.rb
require 'spec_helper'
require 'rspec_api_documentation'
require 'rspec_api_documentation/dsl'

module ControllerHelpers
  def login_user
    before(:each) do
      @request.env['devise.mapping'] = Devise.mappings[:user]
      user = FactoryGirl.create(:user)
      user.confirm! # or set a confirmed_at inside the factory. Only necessary if you are using the "confirmable" module
      sign_in user
    end
  end
end

RspecApiDocumentation.configure do |config|
  config.app = Rails.application
  config.format = [:json, :markdown, :html]
  # config.curl_host = 'http://localhost:3000'
  config.api_name = 'Cubits API'
end

RSpec.configure do |config|
  config.include Warden::Test::Helpers
  config.include Devise::TestHelpers
  config.include ControllerHelpers
end

Any suggestions?

Solution is to use wardens test helpers instead
module ControllerHelpers
  def login_user
    before(:each) do
      @request.env['devise.mapping'] = Devise.mappings[:user]
      login_as(user, scope: :user, run_callbacks: false)
    end
  end
end


Const codec methods

Codecs can be generated so that encode and decode methods are const methods. Furthermore, a lot of methods in IMap and other containers can be made const.

Due to the non-const serialization APIs, this is really not easy task and we can not really change the user APIs.


[macos] Hard to work with seemingly infinite debug logs.

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

Create a new flutter project
Run the new flutter project on macos
Change the window size around and scroll.
Slowly many logs will get built up and sometimes it just keeps on going.

Expected results
To show some startup logs and then be on the way to development as usual.
Actual results
Starts spawning infinite logs making it very hard to work and also slows down vscode.
Code sample
Code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key, required this.title});

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  int _counter = 0;

  void _incrementCounter() {
    setState(() {
      _counter++;
    });
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: Center(
        child: GridView(
          gridDelegate: const SliverGridDelegateWithFixedCrossAxisCount(crossAxisCount: 2),
          children: <Widget>[
            for (int i = 0; i <= 1000; i++) ...[
              Text("this is $i & $_counter")
            ]
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: const Icon(Icons.add),
      ),
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration
https://user-images.githubusercontent.com/59999892/232819205-3dc51c1d-fadd-4ce9-916e-04f116d34db3.mp4

Logs
Logs
https://pastebin.com/CCpM4pmu

Flutter Doctor output
Doctor output

[✓] Flutter (Channel stable, 3.7.11, on macOS 13.2.1 22D68 darwin-arm64, locale en-SG)
    • Flutter version 3.7.11 on channel stable at /Users/skywar56/Documents/Flutter/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f72efea43c (7 days ago), 2023-04-11 11:57:21 -0700
    • Engine revision 1a65d409c7
    • Dart version 2.19.6
    • DevTools version 2.20.1

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/skywar56/Library/Android/sdk
    • Platform android-33, build-tools 30.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14B47b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] VS Code (version 1.78.0-insider)
    • VS Code at /Applications/Visual Studio Code - Insiders.app/Contents
    • Flutter extension version 3.62.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 13.2.1 22D68 darwin-arm64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 112.0.5615.121

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

I just tried on dartpad your example everything is fine, did you run out of memory on your pc ?

@superciccio I have 32 gb ram so I really don't think I ran out of memory. Also this happens specifically when you run it on a macos build. I don't think dartpad is counted as one if I am not mistaken?

Fixed thanks to this:
https://github.com/flutter/flutter/issues/117663#issuecomment-1397139911


refactor: dropping 'new' from TxEffect's properties

Having "new" in the naming of tx effect properties is not necessary as it's clear that the values are related to the given tx effect. This PR does the renamings.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

#4861  👈
#4858
master

This stack of pull requests is managed by Graphite.


Recommended example doesn't work, pathToArray invalid argument

Pim@AS-DEV06 MINGW64 /c/dev/autodll/examples/recommended (master)
$ npm start

<EMAIL_ADDRESS>start C:\dev\autodll\examples\recommended
webpack-dev-server --history-api-fallback --config ./webpack.config.js

Project is running at http://localhost:8080/
webpack output is served from /
404s will fallback to /index.html
AutoDllPlugin: is valid cache? false
AutoDllPlugin: cleanup
AutoDllPlugin: compile
{ Error: invalid argument
at pathToArray (C:\dev\autodll\node_modules\memory-fs\lib\MemoryFileSystem.js:44:10)
at MemoryFileSystem.writeFileSync (C:\dev\autodll\node_modules\memory-fs\lib\MemoryFileSystem.js:200:13)
at C:\dev\autodll\lib\createMemory.js:62:11
at tryCatcher (C:\dev\autodll\node_modules\bluebird\js\release\util.js:16:23)
at Object.gotValue (C:\dev\autodll\node_modules\bluebird\js\release\reduce.js:155:18)
at Object.gotAccum (C:\dev\autodll\node_modules\bluebird\js\release\reduce.js:144:25)
at Object.tryCatcher (C:\dev\autodll\node_modules\bluebird\js\release\util.js:16:23)
at Promise._settlePromiseFromHandler (C:\dev\autodll\node_modules\bluebird\js\release\promise.js:512:31)
at Promise._settlePromise (C:\dev\autodll\node_modules\bluebird\js\release\promise.js:569:18)
at Promise._settlePromiseCtx (C:\dev\autodll\node_modules\bluebird\js\release\promise.js:606:10)
at Async._drainQueue (C:\dev\autodll\node_modules\bluebird\js\release\async.js:138:12)
at Async._drainQueues (C:\dev\autodll\node_modules\bluebird\js\release\async.js:143:10)
at Immediate.Async.drainQueues (C:\dev\autodll\node_modules\bluebird\js\release\async.js:17:14)
at runCallback (timers.js:649:20)
at tryOnImmediate (timers.js:622:5)
at processImmediate [as _immediateCallback] (timers.js:594:5)
code: 'EINVAL',
errno: 18,
message: 'invalid argument',
path: '\assets\vendor_5526a1788371ac712b7d.js' }
npm version 4.1.2
node version 6.9.4

Seems related to https://github.com/asfktz/autodll-webpack-plugin/pull/71

Hi @codemasterover9000, I've just released a new version with #71, can you please confirm that it works now? thanks


Polyfill for keylog API

This is not (at least initially) intended to be merged, just as a proposal.
Basically implements a polyfill that:

for Node.JS >= 11.9.0, calls SSL_CTX_set_keylog_callback natively and emits keylog events based on it
for Node.JS < 11.9.0, emulates the OpenSSL API by manually assembling the CLIENT_RANDOM line as we do now, and emitting keylog events.
for Node.JS >= v12.3.0 (probably), if it detects that keylog is available natively, does nothing

Polyfilling the keylog API would allow us to implement index.js without needing the native module:
require('./lib/pollyfill.js');

E.filename = // ... (no changes)
E.set_log = // ... (no changes)
E.log_line = line => fs.appendFile(E.filename, line, err => {
    if (err) console.error(`Warning: Failed to log to SSLKEYLOGFILE: ${err}`);
});

E.hook_socket = socket => socket.on('keylog', E.log_line);
E.hook_server = server => server.on('keylog', E.log_line);
E.hook_agent = // ... (no changes)
E.hook_all = // ... (no changes)

Which would in turn allow us to skip building the native module entirely, if the native API is present. So, for recent Node.JS versions, this would simply be a small JS module for easy SSLKEYLOGFILE logging.
The downside is that we'd have to drop update_log and get_session_key. If someone needs custom logging he can subscribe to keylog directly, and only use this module as a polyfill. The second one is not entirely replaceable, but you can parse keylog lines to get the secrets you need (with TLSv1.3 this should be even more reliable than calling get_session_key manually, IMHO). What are your thoughts on this?

Hi Alba, sorry for pause, busy days.. Everything sounds logical, and you're right - advantages are clear. Let's move along the way you've suggested, and we'll see how it will work out. I'll add more comments after reading proposed code.

No worries, and thanks for your time ^^

Hi, long time no see! I reviewed all the code (and thanks for tests!), and I'd like to merge it to move forward. What do you think?

Hi! Seems good to me, I've been using it for a while, it works well


Is posible to show Dialog Crash Error

When detect error crash, is posible show a dialog with buttons (close,detaile, report) without notification?
Detaile -> open crash report
report -> open email for send a developer

I need this too, because android TV don't have a status bar

ok, I will do it as part of the next release.


FGA closes itself in Vivo phone

Preparation

[X] I tested the latest release
[X] I looked at other issues (even the closed ones)
[X] I read the Troubleshooting Guide

FGO server
NA
FGA build number
1483
Describe the bug
The app gets killed during the first or second wave. The first video shows the app running just fine until FGA crashes abruptly. About 30 seconds after the app crashes, the play button returns but cant be clicked. I recorded the second video showing this.
I have done everything as mentioned in https://dontkillmyapp.com/vivo and checked the previous issues. The closest issue i found to my problem was #41 .
Edit: I should also mention that FGA was running perfectly well about 2 months ago. I had stopped playing and came back a few days ago. The above mentioned problem appeared. I realised that a new verson of FGA was released, since i had the previous verson of FGA installed (the verson fom 2 months ago). I installed the new verson but the problem still continues.
Video
1st vid --> https://youtu.be/El8FziI97to
2nd vid --> https://youtu.be/F4faP25sM5w

Device model
Vivo 1904
Android version
Android 11
Screen size
720 x 1544 pixels
RAM
3GB

Since the old issue is about RAM usage, can you check this? https://fossbytes.com/check-ram-usage-android/
The crash reason could also be written in the logs. You can check them like this: https://github.com/Fate-Grand-Automata/FGA/issues/282#issuecomment-678614896

So, this is from the RAM usage :

And here's the log file:
logcat.log
I think the log of the time at which the video was recorded is at: 08-31 22:45:59.764 , although there are a lot of other instances at which i could find 'FGA' and 'fate' keywords when i searched.

There was a missing line in the source code which made the error log useless.
Can you please try again with build 1484 once it's released? (in a few minutes)

logcat.log
This is the log at build 1484.
The crash is at: 09-01 08:00:48.521

@reconman The Null exceptions in the logs is expected on service start since media projection won't be initialised at that point. it's only logging that error, won't crash due to that.

I should also mention that FGA was running perfectly well about 2 months ago. I had stopped playing and came back a few days ago. The above mentioned problem appeared. I realised

That clearly indicates a battery saver/accessibility issue.
I assume you've tried restarting your phone or force stopping FGA after making those changes.
By any chance, did you suppress the ongoing notification that pops up when FGA runs scripts?

I should also mention that FGA was running perfectly well about 2 months ago. I had stopped playing and came back a few days ago. The above mentioned problem appeared. I realised

That clearly indicates a battery saver/accessibility issue.
I assume you've tried restarting your phone or force stopping FGA after making those changes.
By any chance, did you suppress the ongoing notification that pops up when FGA runs scripts?

No

So, I just restarted my device again and the app works fine now. It didn't work when i restarted twice yesterday so idk whats up with that.
Closing this issue now. Sorry to waste everyone's time and thankyou @MathewSachin and @reconman for the help.


Default ExitOnFatal to true

Default the value of ExitOnFatal to true so when log.Fatal is called os.Exit(1) is triggered.

thanks @LloydGriffiths


Web build broken: "RuntimeError: memory access out of bounds"

It's crashing during the call to oxid_common.init. A debug print added right before that call goes through, but a debug print added to the top of oxid_common.init is not hit.

fixed


Fix #182

A picture tells a thousand words
Before this PR

After this PR

Coverage remained the same at 42.808% when pulling 56749aa6a05731ef19149bf778c7311cb46be571 on fix_#182 into 2be8c1782b55f27dd30e87374362d08ef74c5ac8 on master.


Add logic for deselect item chart to hide the chart again

heyo :) thx a lot for the project
I stumbled upon the behaviour that the chart is popping up once the user selects the "chart" icon on the specific item in the list, however the chart does not correctly hide again, on deselecting the "chart" icon.
This PR aims to fix this behaviour by adding a simple else if check for the reverse logic and adding the hidden tag again to the chart.

Not unhiding is intentional. If you have a long item list, scroll down, select chart, scroll up to look at the chart, then scroll down to unselect, the unselect would change the scroll position.
I'm overall not happy how the charting works, but I don't think this is a better solution.

Alright no problem, thanks for looking into the PR
hm may I ask, why not have the close chart button, directly near or preferably next to the chart ?
This would solve the problem of having the user, scroll down all the way to the item and unselecting it there


Question: Why are all the commits to this repo not showing up on my profile (> . <)

@alvinkatojr I feel robbed!
But no, seriously... why not?

Ahh... got it. Because it is a fork, all commits are only counted once merged in a pull request. o_O

ha ha :-)


Feature: Improve CI

Feature Details

Evaluate CI and decide what is useful and what is burdensome
Look for ways to cut back on runtime without affecting code quality/early flagging of code issues

Remove this file since it's redundant - this is accomplished in r-cmd-check-dev/main.


Some mistake on the camera-lidar odometry task

I want to experiment with whether this dataset can validate the fusion odometry method we proposed. Unfortunately, when processing sequence boreas-2020-12-18-13-44, we attempted to test the provided pose ground truth, but the results seem problematic. We computed a relatively accurate 3D point cloud result by processing the lidar data and its corresponding poses.

However, when we project the lidar points onto the camera coordinate system using the T_camera_lidar matrix, the projected points seem to have issues when using the camera pose, with significant drift occurring in many places.

Obviously, there is a problem with the T_camera_lidar matrix. Is there a suitable solution to address this tricky issue? Thank you.

Hello,
We have a python tutorial notebook for doing lidar projection onto a camera image. Can you have a look at that as a reference to fix your problem?
https://github.com/utiasASRL/pyboreas/blob/master/pyboreas/tutorials/lidar_camera_projection.ipynb
It's hard to tell what the problem is here without seeing your code.


Use TrueClass and FalseClass in resources

Apply fixes from the latest Cookstyle
Signed-off-by: Tim Smith<EMAIL_ADDRESS>

          1 Warning

:warning:
This Pull Request is probably missing tests.

  Generated by :no_entry_sign: Danger


Dialog opening causes custom fonts re-render [Next.js]

Describe the bug
I use next.js and I want to add some non-system fonts.
Once I add the fonts AND link rel="preload" in the head to preload the fonts to avoid initial font flickering I get the font glitching after the intercom dialog opening.
To Reproduce
Steps to reproduce the behavior:

Use default next.js bootstrap setup
Add any custom font to a project (i.e. montserrat)
Add link rel="preload" to the head and specify path to custom fonts
install and configure react-use-intercom
boot intercom and open the dialog
Pay attention to the font on the page

Expected behavior
The font shouldn't be re-rendered
Screenshots
https://user-images.githubusercontent.com/10371454/147265924-0c655004-b790-4086-941f-18cbf0a53476.mov
Desktop (please complete the following information):

OS: macOS
Browser: Chrome
Version 96

Additional context
font-display property doesn't help much either. The best solution I found is to use font-display: fallback; but the blank flickering is still present.

Thanks for creating this issue. This doesn't seem something related to react-use-intercom (or in general for intercom).
However, I can take a quick look if you provide a reproduction (you can use https://stackblitz.com/). At the moment I've no idea how you use nextjs, css, load the font...

@devrnt , thanks for the attention and quick response!
Hm, maybe you are right and this issue is related to the iframes and how preloaded fonts work with them. But anyway I don't understand why this is happening so I would really appreciate any help or hint.
I'm not sure if I can use https://stackblitz.com/ since it doesn't support files uploading (I need to upload the fonts files) and if I use link to font's CDN I cannot reproduce the issue in stackblitz.
Would it be okay if I just push this example to GitHub so you can check it in the repository?
https://github.com/AlexanderZanin/next-fonts
Sorry for inconvenience.

I checked it out and it's indeed flickering. However, this seems not related to this package.
I suggest loading the fonts like mentioned in https://nextjs.org/docs/basic-features/font-optimization or via https://fontsource.org. I've tried both solutions and they work (without flickering)
Let me know if you need anything else


Using pnpm/action-setup in a subdirectory of a git repoository is giving: ENOENT: no such file or directory

WHAT?
Hi, I'm trying to use this GitHub Action in a project that looks like this:
myproject
  |-- .github/workflows/client-ci.yml
  |-- backend
  |-- client

I want to use pnpm inside myproject/client/package.json folder but this action:
 - name: Setup pnpm
        uses<EMAIL_ADDRESS>
It's giving this error:
Running self-installer...
  [Error: ENOENT: no such file or directory, open '/home/runner/work/myproject/myproject/package.json'] {
    errno: -2,
    code: 'ENOENT',
    syscall: 'open',
    path: '/home/runner/work/myproject/myproject/package.json'
  }

Specify destination
I also tried setting destination. But I get the same error.
 - name: Setup pnpm
        uses<EMAIL_ADDRESS>        with:
          dest: ~+/client

I would appreciate any help. Thanks!

Ok I made some "progress" but not sure is the way to go:
To solve the package.json ENOENT not found file error I duplicated the package.json inside myproject/client/package.json outside in myproject/package.json
And that allowed the CI move to fail in the Build, lint and type-check step which is my Turbo repo project with pnpm
With this error:

This is my full .github/workflows/client-ci.yml file
name: CI client

on:
  push:
    paths:
      - client/**
    branches:
      - main
  pull_request:
    types:
      - opened
      - reopened
      - synchronize
      - ready_for_review

concurrency:
  group: ${{ github.ref }}-client
  cancel-in-progress: true

env:
  TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
  TURBO_TEAM: ${{ secrets.TURBO_TEAM }}

jobs:
  changes:
    name: Check changes files
    runs-on: ubuntu-latest
    outputs:
      client: ${{ steps.filter.outputs.client }}
    steps:
      - uses: actions/checkout@v2
      - uses: dorny/paths-filter@v2
        id: filter
        with:
          filters: |
            client:
              - 'client/**'
  lint_and_types:
    name: Lint and Type check
    runs-on: ubuntu-latest
    needs: changes
    if: ${{ needs.changes.outputs.client == 'true' && (github.event_name == 'push' || !github.event.pull_request.draft) }}
    steps:
      - name: Checkout repo
        uses: actions/checkout@v3

      - name: Setup pnpm
        uses<EMAIL_ADDRESS>
      - name: Setup Node 18
        uses: actions/setup-node@v3
        with:
          node-version: 18

      - name: Get pnpm store directory
        id: pnpm-cache
        run: |
          echo "pnpm_cache_dir=$(pnpm store path)" >> $GITHUB_OUTPUT

      - name: Setup pnpm cache
        uses: actions/cache@v3
        with:
          path: ${{ steps.pnpm-cache.outputs.pnpm_cache_dir }}
          key: ${{ runner.os }}-pnpm-store-${{ hashFiles('**/pnpm-lock.yaml') }}
          restore-keys: |
            ${{ runner.os }}-pnpm-store-

      - name: Install deps (with cache)
        run: pnpm install

      - name: Build, lint and type-check
        run: pnpm turbo build lint types
        env:
          SKIP_ENV_VALIDATION: true

      - name: Check workspaces
        run: pnpm manypkg check

Ok I found what was my issue.
This line is looking always in the root of the repo: https://github.com/pnpm/action-setup/blob/11dd14d0c0916e1ad9ff1938d8d4ea509bebfe10/src/install-pnpm/run.ts#L47
The solution was to use version param:
- name: Setup pnpm
  uses<EMAIL_ADDRESS>  with:
    version: 7.15.0

So this way this action doesn't try to find a package.json in root of the repo.
I hope this can help someone : )

Is there a fix without pinning the version to 7.x.x?

Doesn't this mean that it pins the version...?!
https://github.com/pnpm/action-setup#version
Sorry if I'm being dumb.

I guess if you put a version there that's the version used by the github action. So yes, that would be pinned.
But I think anyway is a good practice to pin your project to an specific pnpm version. Either by setting packageManager in your root package.json or by setting it in the github action.

Okay, gotcha, thanks!
I'm working with a similar setup, do you just add working-directory: foo whenever you run a command or is there a way to take care of that generally?

For future reference, you can pin any version and it will work.
Originally I thought you specifically had to pin verison 7.15.0, but any version will do.
@andresgutgon thanks for the tips!

@andresgutgon @robotkutya I'm facing a similar issue, I've read through the docs and I saw run_install.cwd should configure this but I haven't gotten it to work. Does anyone have a working example that we could add to the docs?

Here's a code snippet of what I would expect work based on the docs (my working directory is web)
- uses: pnpm/action-setup@v2
        with:
          run_install: |
            cwd: web

I found a solution by adding version: 7
- uses: pnpm/action-setup@v2
        with:
          version: 7
          run_install: |
            - cwd: client

However I do think this should be changed in a future version to use the more common syntax working-directory from the defaults like @andresgutgon showed above


Add Hybrid Application Service component

This PR adds a component for HAS to the AppStudio staging environment.
In all, the following is done by this PR:

CatalogSource, OperatorGroup and Subscription yaml files for the HAS operator added under components/has

The catalogsource points to quay.io/redhat-appstudio/application-service-catalog:sha-4f97678
The OperatorGroup targets the application-service namespace
The Subscription installs the application-service.v0.0.1 OLM bundle into the application-service namespace

An ArgoCD application resource (has.yaml) added under argo-cd-apps/base that references the aforementioned has component.

I've also verified on my own OCP cluster that running kustomize build argo-cd-apps/overlays/staging | oc apply -f - properly deploys HAS:

This PR should not be merged until https://github.com/redhat-appstudio/application-service/pull/17 is merged, but I wanted to get this PR up now for review/comments.

This PR creates a namespace, application-service, that folks from HAS would ideally have readonly / view access to. Should I also add a file to add a view role for that namespace to https://github.com/redhat-appstudio/infra-deployments/tree/main/components/authentication?

Removing WIP label since https://github.com/redhat-appstudio/application-service/pull/17 has been merged.


error: cannot find symbol import com.github.barteksc.pdfviewer.util.FitPolicy;

I am getting this issue
error: cannot find symbol
import com.github.barteksc.pdfviewer.util.FitPolicy;
while installing while project gradle is 2.2.2
react-native is 0.48.0^

me the same problem


Update CHANGELOG.md

carry https://github.com/docker/docker/pull/21825
closes https://github.com/docker/docker/pull/21825

ping @tiborvass @mlaventure  :smile:

LGTM

SGTM

LGTM

author LGTM no CI needed on this one

@cpuguy83 thanks! I'll open a PR to remove those