chore(cloud-sources): enable feature flag by default

Description
Enable the Cloud Sources feature flag by default, since we also plan to release it with 4.4.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Here I tell how I validated my change

see CI passing.

Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.

Current dependencies on/for this PR:

#10079  👈
master

This stack of pull requests is managed by Graphite.

/retest


change input value won't trigger change

manually change the input value will not trigger the change event, only when rotating the file will trigger. Or is there something that I missed?
http://jsbin.com/matutunagu/edit?html,js,console,output

+1

Hooking into draw can be used in the meantime
    $(element).knob({
      'draw': function() {
        console.log(this.$.val());
      }
    });

You can also hook into release.


No query results for model [Konekt\Acl\Models\Role]

When running this migration
Migrating: 2018_12_09_193651_create_property_permissions
Getting this error:
No query results for model [Konekt\Acl\Models\Role].
Any advice please?

This migration is part of the Vanilo Framework and doesn't come from this module.
Still valid though, I'll transfer the issue there


Getting MemoryError:Java heap space for Log Files more than 600MB

11:06:07.079 [main] INFO com.joergeschmann.tools.loganalyzer.App - ================== Log excerpt start ====================
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:3332)
at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:124)
at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:448)
at java.lang.StringBuilder.append(StringBuilder.java:136)
at com.joergeschmann.tools.loganalyzer.processing.observer.LogEntry.appendMessageLine(LogEntry.java:63)
at com.joergeschmann.tools.loganalyzer.processing.observer.AbstractLogEntryObserver.notify(AbstractLogEntryObserver.java:47)
at
at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:448)
at java.lang.StringBuilder.append(StringBuilder.java:136)
at com.joergeschmann.tools.loganalyzer.processing.observer.LogEntry.appendMessageLine(LogEntry.java:63)
at com.joergeschmann.tools.loganalyzer.processing.observer.AbstractLogEntryObserver.notify(AbstractLogEntryObserver.java:47)
at com.joergeschmann.tools.loganalyzer.processing.observer.LogEntryConsoleAppenderObserver.notify(LogEntryConsoleAppenderObserver.java:17)
at com.joergeschmann.tools.loganalyzer.processing.AbstractFileProcessor.notifyObservers(AbstractFileProcessor.java:38)
at com.joergeschmann.tools.loganalyzer.processing.SingleFileProcessor.process(SingleFileProcessor.java:35)
at com.joergeschmann.tools.loganalyzer.App.run(App.java:62)
at com.joergeschmann.tools.loganalyzer.App.main(App.java:36)

Could you provide more information about this issue? I have just processed a 3GB log file and got no Exception...
What is your heap size for example?
What config/parameters are you using?
Could you share how a log line looks like and how much entries you have?

Hope this helps. I'm trying to debug the code but it failing at this point. Tried increasing the heap size but then I get the following error which I will send in my next email. Pls help as this tool will be a great asset to my project
Sent from my iPhone

On 3 Mar 2017, at 3:35 PM, Joerg Eschmann<EMAIL_ADDRESS>wrote:
Could you provide more information about this issue? I have just processed a 3GB log file and got no Exception...
What is your heap size for example?
What config/parameters are you using?
Could you share how a log line looks like and how much entries you have?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

hi joerge,
any update on this?
cheers

My Machine confiuration

Unless I am not able to reproduce the error it is hard to help...
How did you execute the app?
What parameters did you define, or how does your config.json looks like?
Do you have a repo/fork here on github for further investigation?
How does your log file look like?

cant upload the file as it is 64MB. let me try to fork github

do you need to add me as a member? Not able to push the files

sorry unfamiliar with github

https://github.com/sachindere76/log-analyzer.git

Could you also describe how a log entry of your log file looks like and what you are trying to achieve?
Do you want to extract certain values or entire log entries with a specific value in a field?

Hi jeorge
Let me try to send u tmmrw. Was trying to upload the Log file to GitHub plus Dropbox but it's more than 600MB
I only want to extract certain values ex certain exceptions based on date and time
I increased the heap size in my machine Using java_opts but no use
Thanks
Sent from my iPhone

On 6 Mar 2017, at 7:47 PM, Joerg Eschmann<EMAIL_ADDRESS>wrote:
Could you also describe how a log entry of your log file looks like and what you are trying to achieve?
Do you want to extract certain values or entire log entries with a specific value in a field?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi Joerg,
You can download the log file from here
https://www.dropbox.com/s/6ty1vace3wz1nmv/catalina.out?dl=0
Please try it out and see if you can recreate the issue
Thanks
Sent from my iPhone

On 6 Mar 2017, at 7:47 PM, Joerg Eschmann<EMAIL_ADDRESS>wrote:
Could you also describe how a log entry of your log file looks like and what you are trying to achieve?
Do you want to extract certain values or entire log entries with a specific value in a field?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Your log file structure is not compatible with the LogEntryParser (https://github.com/sachindere76/log-analyzer/blob/master/src/main/java/com/joergeschmann/tools/loganalyzer/processing/observer/LogEntryParser.java). Currently, you have to implement your own LogEntry and LogEntryParser to correctly parse your log file. I will publish a new release in about a week. With that version it is far more convenient to handle different log file structures.

Thanks jeorge looking forward for it
Sent from my iPhone

On 8 Mar 2017, at 2:07 PM, Joerg Eschmann<EMAIL_ADDRESS>wrote:
Your log file structure is not compatible with the LogEntryParser (https://github.com/sachindere76/log-analyzer/blob/master/src/main/java/com/joergeschmann/tools/loganalyzer/processing/observer/LogEntryParser.java). Currently, you have to implement your own LogEntry and LogEntryParser to correctly parse your log file. I will publish a new release in about a week. With that version it is far more convenient to handle different log file structures.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

There is a new version in the dev branch (https://github.com/joergeschmann/log-analyzer/tree/dev). I still need to add some more unit tests and documentation until it is ready for a merger into the master branch. However, you should be able to parse your log file with this version.
Furthermore, I figured out that your log file does not have a consistent structure, like this part:
14-Nov-2016 16:49:31.193 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["ajp-nio-8009"]
14-Nov-2016 16:49:31.193 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["ajp-nio-8009"]
DEBUG 14 Nov 2016 16:49:33 [http-nio-8181-exec-8] [com.ebglobal.vbroker.utils.DBUtil - getConnection() - inside get connecton]
DEBUG 14 Nov 2016 16:56:43 [http-nio-8181-exec-11] [com.ebglobal.vbroker.utils.DBUtil - getConnection() - inside get connecton]
The prerequisite for this tool is to have a consistent structure. Otherwise the logic would get too complicated. Therefore, I suggest that you split your large file into multiple files that every slice is consistent.

Thanks jeorge. Let me go through it when I get back to the office
Sent from my iPhone

On 22 Mar 2017, at 1:27 AM, Joerg Eschmann<EMAIL_ADDRESS>wrote:
There is a new version in the dev branch (https://github.com/joergeschmann/log-analyzer/tree/dev). I still need to add some more unit tests and documentation until it is ready for a merger into the master branch. However, you should be able to parse your log file with this version.
Furthermore, I figured out that your log file does not have a consistent structure, like this part:
14-Nov-2016 16:49:31.193 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["ajp-nio-8009"]
14-Nov-2016 16:49:31.193 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["ajp-nio-8009"]
DEBUG 14 Nov 2016 16:49:33 [http-nio-8181-exec-8] [com.ebglobal.vbroker.utils.DBUtil - getConnection() - inside get connecton]
DEBUG 14 Nov 2016 16:56:43 [http-nio-8181-exec-11] [com.ebglobal.vbroker.utils.DBUtil - getConnection() - inside get connecton]
The prerequisite for this tool is to have a consistent structure. Otherwise the logic would get too complicated. Therefore, I suggest that you split your large file into multiple files that every slice is consistent.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Big files are no problem if the log file has a consistent structure.


[Scenario] The Innsmouth Trial

What kind of mission do you want to add (mark with an X, e.g. [X] Descent)?

[X] Mansions of Madness
[ ] Descent

What expansions does the scenario require?

[ ] Conversion Kit (CK)
[X] First Edition (MoM1E) - Also Recurring Nightmares
[ ] Fatal Alchemy (FA) - Also Suppressed Memories
[X] Call of the Wild (CotW) - Also Suppressed Memories
[X] Beyond the Threshold (BtT)
[X] Streets of Arkham (SoA)
[X] Sunctum of Twilight (SoT)
[X] Horrific Journeys (HJ)
[ ] Path of the Serpent (PotS)

What expansions can the scenario optionally use?

[ ] Conversion Kit (CK)
[ ] First Edition (MoM1E) - Also Recurring Nightmares
[ ] Fatal Alchemy (FA) - Also Suppressed Memories
[ ] Call of the Wild (CotW) - Also Suppressed Memories
[ ] Beyond the Threshold (BtT)
[ ] Streets of Arkham (SoA)
[ ] Sunctum of Twilight (SoT)
[ ] Horrific Journeys (HJ)
[ ] Path of the Serpent (PotS)

Please enter the GitHub Url to your scenario here
https://github.com/vidimus/DomeAcolyte/tree/main/Lost_chronicles_07
After being captured by the Innsmouth Mob, a band of outsiders is taken to face trial.
Another scenario from Dome Acolyte.

Added to manifest and statistics sheets


fix: fix type radio in input component

Pull Request Test Coverage Report for Build 1426

47 of 53 (88.68%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.4%) to 71.834%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/components/Input/inputBase/index.js
23
26
88.46%

src/components/Input/inputRadio/index.js
19
22
86.36%

Totals

Change from base Build 1422:
0.4%

Covered Lines:
896

Relevant Lines:
1184

💛  - Coveralls

fix: #292


Piazetta pelletstove Natural mode?

Hi,
Not really willing to report a issue, but more a question. In version 0.1.8 i got the Natural mode functionality which i really liked, i did not need to use the MyPiazetta app to turn off the fan anymore.
Since 0.2.0+ versions i am missing this mode again. Now having only 4 available sensors, where before i had 6. Is this something that can be added back in newer versions?
Thanks a lot for your work!
Kr,
Bart

Hi Bart, I did not remove that functionality so this must be a regression. Can you please share your diagnostics file?

Many thanks, it's back now !


[Improve][SDK] Go SDK pressure test and optimization

Description
Localtion:
inlong-sdk/dataproxy-sdk-golang
Requirements:

An SDK pressure testing report.
Troubleshoot performance bottlenecks based on pressure testing reports.
Some performance optimization.

This issue is a dedicated issue for the 2024 Tencent Rhino-bird Open Source Talent Training event and is only available for college students to claim
【Claim the issue】Sign up for the corresponding issue in columns M~R of the Research and Study Base "issue Camp" to be considered as successfully claimed.
【Complete the issue】For students who have claimed the issue, please also reply "Successfully claimed this issue" in the comment section of this issue; if there is no progress submitted within 7 days, including but not limited to comments, commits, or Pull Requests, it will be considered as voluntarily giving up the issue and the committee will release the issue to the next person in line.
InLong Component
InLong SDK
Are you willing to submit PR?

[ ] Yes, I am willing to submit a PR!

Code of Conduct

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

您好，想请问一下直接在腾讯文档上填写姓名+GitHub就算认领issuse成功了么？这个issue是只需要对inlong-sdk/dataproxy-sdk-golang这个sdk进行压力测试和优化是么？具体优化哪些部分？

Successfully claimed this issue


Cannot wasm-pack build when using a js_sys array method (filter or map)

Describe the Bug
When I run wasm-pack build --target web --release build fails if I use an Array method like filter or map (I havn't tried other methods). The strange part is that wasm-pack build --target web --dev runs perfectly
Cargo.toml
[package]
name = "transforms-wasm"
version = "0.1.0"
authors = ["Nicolas Bruère<EMAIL_ADDRESS>edition = "2018"

[lib]
crate-type = ["cdylib"]

[features]
default = ["console_error_panic_hook"]

[dependencies]
wasm-bindgen = "0.2.93"
js-sys = "0.3.70"

# The `console_error_panic_hook` crate provides better debugging of panics by
# logging them with `console.error`. This is great for development, but requires
# all the `std::fmt` and `std::panicking` infrastructure, so isn't great for
# code size when deploying.
console_error_panic_hook = { version = "0.1.7", optional = true }

[dev-dependencies]
wasm-bindgen-test = "0.3.43"

[profile.release]
# Tell `rustc` to optimize for small code size.
opt-level = "s"

lib.rs
#[wasm_bindgen]
pub fn get_histogram(input: &Array, binsize: f64, min: f64, max: f64, dimension: i32) -> Array {
    let output = Array::new();

    let mut i = min;
    while i <= max {
        let arr = Array::new();
        arr.push(&JsValue::from_f64(i));
        let count = input.filter(&mut |item, _, _| {
            let row = Array::from(&item);
            let o = row.at(dimension).as_f64().unwrap();
            if o >= i && o < (i + binsize) {
                return true;
            }
            false
        }).length();
        arr.push(&JsValue::from(count));
        output.push(&arr);
        i += binsize;
    }

    output
}

The error output:
[INFO]: ⬇  Installing wasm-bindgen...
error: failed to generates bindings for adapter

Caused by:
    no function table found in module
Error: Running the wasm-bindgen CLI
Caused by: Running the wasm-bindgen CLI
Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1
  full command: "/Users/nicolas.bruere/Library/Caches/.wasm-pack/wasm-bindgen-507ae24572712ef8/wasm-bindgen" "/Users/nicolas.bruere/workspace/reco-explorer/transforms-wasm/target/wasm32-unknown-unknown/release/transforms_wasm.wasm" "--out-dir" "/Users/nicolas.bruere/workspace/reco-explorer/transforms-wasm/pkg" "--typescript" "--target" "web"

Steps to Reproduce

Run wasm-pack build --target web --release => you get an error
Run wasm-pack build --target web --dev => you get 0 error

https://we.tl/t-V6pMfd5I4B
Expected Behavior
I'd like to have the same behavior whether I'm building on dev or release. I'd be ok if both return an error since it might be a mistake I made ;)
Actual Behavior
The build command outputs an error on release mode and no errors on dev mode

For whatever reasons, all references to these functions are removed by some pre-processing done in wasm-bindgen, which then asks Walrus to do some cleanup in which this table is removed.
This would require some digging into to find out exactly what is being removed here and why.

Thank you for your answer @daxpedda 👍 I'm sorry I'm not comfortable enough in Rust to do this digging


[第一組] Make template for different LLM clients

Purpose
Increase expandability of LLM clients, making it easier to add other LLM clients in the future.
Changes
Created the template for LLM clients, added the two clients openai_client and anthropic_client, while putting real API keys into the .env file to make the code run with non-mock responses.

Your CI didn't pass!


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-main" workflow

Codecov Report

Merging #264 (a210890) into main (2974dfe) will increase coverage by 8.93%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #264      +/-   ##
==========================================
+ Coverage   83.33%   92.26%   +8.93%
==========================================
  Files           2        1       -1
  Lines         126      349     +223
  Branches       31       34       +3
==========================================
+ Hits          105      322     +217
- Misses         21       27       +6

Impacted Files
Coverage Δ

src/index.ts
92.26% <100.00%> (+10.26%)
:arrow_up:

example/src/main.ts

Continue to review full report at Codecov.

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


Chore add some profile on ReaderInit

What problem does this PR solve?
add some profile on ReaderInit
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
Release note
None
Check List (For Author)

Test

[ ] Regression test
[ ] Unit Test
[ ] Manual test (add detailed scripts or steps below)
[ ] No need to test or manual test. Explain why:

[ ] This is a refactor/code format and no logic has been changed.
[ ] Previous test can cover this change.
[ ] No code files have been changed.
[ ] Other reason

Behavior changed:

[ ] No.
[ ] Yes.

Does this need documentation?

[ ] No.
[ ] Yes.

Check List (For Reviewer who merge this PR)

[ ] Confirm the release note
[ ] Confirm test cases
[ ] Confirm document
[ ] Add branch pick label

run buildall

run buildall

run buildall

run buildall

run buildall


[relay] Feature/relay integration r53

Describe your changes
Support route53 for TLS handling
Issue ticket number and link
Checklist

[ ] Is it a bug fix
[ ] Is a typo/documentation fix
[x] Is a feature enhancement
[ ] It is a refactor
[ ] Created tests that fail without the change (if possible)
[ ] Extended the README / documentation, if necessary

Can you please check how we can avoid this case:
Your sites will be served over HTTPS automatically using an automated CA.
By continuing, you agree to the CA's terms of service.
Please enter your email address to signify agreement and to be notified
in case of issues. You can leave it blank, but we don't recommend it.
  Email address:

We should not expect an interactive input when deploying the relay on containers. So we should always skip the email if the user didn't provide it

Actually, I can not reproduce the issue on my machine (I tried with the example command that you provided), but I pushed a commit what could fix it.


Not able to make a TLS post request in android 4.3

I am trying to use OKhttp to make a post web service request to a WCF web service (saop web service) that requires TLS (not SSL) and client certificate. i am testing on Android S3 version 4.3. i have followed the same example in :
https://github.com/square/okhttp/blob/master/samples/guide/src/main/java/com/squareup/okhttp/recipes/CustomTrust.java
its exactly what i need, but every time it returns forbidden 403 http code. i used Apache http client to accomplish the same thing, and it worked perfectly but not TLS, since apache httpcleint does not support TLS, instead it uses SSL. i used the same KeyStore and TrustStore, but with OKhttp i have no luck to make it work. is there something i am missing. if needed i can provide the code.
please advice, thanks in advance.

Please ask on Stack Overflow. The server returning 403 means that the HTTP client is working properly, just the server doesn't like your request.


Add codecov to README.md

JIRA link (if applicable)
RDM-2250
Change description
Add codecov to README.md
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

Nearly there.  Need a master to for base report
https://codecov.io/gh/hmcts/ccd-user-profile-api/pull/23


dart format hangs on Windows when reading from stdin in the presubmit

The script below hangs on Windows but works fine on other platforms (change the hard coded depot_tools location in the script before running it):
#!/usr/bin/env python3

import imp
import os
import subprocess
import sys

depot_tools = '/Users/user/src/depot_tools'
sys.path.append(depot_tools)
import scm

utils = imp.load_source('utils', os.path.join('tools', 'utils.py'))
dart = os.path.join(utils.CheckedInSdkPath(), 'bin', 'dart')

windows = utils.GuessOS() == 'win32'
if windows:
    dart += '.exe'

args = [
    dart,
    'format',
    '--set-exit-if-changed',
    '--output=none',
    '--summary=none',
]

print('Body builder from git')
contents = scm.GIT.Capture(['show', 'c9d954efe7c7a71d2bf2c2ca385855b82fbfb379:pkg/front_end/lib/src/fasta/kernel/body_builder.dart'],
                                strip_out=False)
process = subprocess.run(args, input=contents, text=True)
print(process.returncode)

For some reason, dart format hangs reports weird formatting errors and starts to print messages like this:
Attempt:11 waiting for isolate vm-isolate to check in
Attempt:11 waiting for isolate dartdev to check in

On other platforms, the script exits normally and dart format finds no formatting issues.
@bkonyi @munificent Any ideas about what could go wrong here? Perhaps line ending confusion?
/cc @johnniwinther

Note that simpler test cases like these work even on Windows:
contents = """
void main()                     {}
"""
print('Format change')
process = subprocess.run(args, input=contents, text=True)
print(process.returncode)

contents = """
void main()                     {
"""
print('Syntax errror')
process = subprocess.run(args, input=contents, text=True)
print(process.returncode)

contents = """void main() {}
"""
print('No change')
process = subprocess.run(args, input=contents, text=True)
print(process.returncode)

Is this a duplicate of https://github.com/dart-lang/sdk/issues/46600 (though that one was marked as fixed).

I don't think so. Before #46600, this would hang on macOS as well. Now it seems to only happen on Windows for specific inputs.
Also, a part of the fix was 44ffad59d2a5d54d7b68bd81e2875fa6d3886f9b which may have masked the issue. It removed the process.communicate causing the presubmit to no longer block on the dart format call. That broke the formatting check. This was fixed in d2bd43f43e6636036a3d250eadcd429c444b7540 which re-enabled the formatting checks.

The checked-in SDK is currently at 2.14.0-377.4.beta, which has the dart_style fixes for #44600.

Any update on this? I am forced to upload most of my CLs with --bypass-hook because of this, and who knows how many badly formatted files have been committed due to this.

Sorry for the delay. I was out on vacation.

For some reason, dart format hangs reports weird formatting errors and starts to print messages like this:
Attempt:11 waiting for isolate vm-isolate to check in
Attempt:11 waiting for isolate dartdev to check in

I've never seen anything like that before, sorry. :( I also don't have a Windows machine to try to repro this on.
For what it's worth, dart_style does have tests for reading from stdin and I believe those tests are run and pass on Windows in the SDK. However, those tests also weren't sufficient to catch #46600. I don't recall exactly why. I think maybe because the tests spawn dart format not using a shell, which affects the behavior?


Partner artist bio blurb not displayed properly

Re: https://artsy.slack.com/archives/partner-s-help/p1484006740001128
Still need to confirm but looks like the blurb (that uses dotdotdot) doesn't display the multi-paragraph content when it is fewer than 4 lines.

This cropped up again. https://artsy.slack.com/archives/partner-s-help/p1484770312001570

This was reported again: https://artsy.slack.com/archives/partner-s-help/p1486138878003209
I ended up just editing the bio to make it not trigger the bug. I removed one newline and that was enough to get it to behave. The original, busted bio:
(b.1974 in Cracow) was educated at the Cracow’s Academy of Fine Arts (1995-2000).
2003-2009 he vied and worked in Florence
2009- 2012 he lives and works in Cracow, by 2009  employed on Academy of Fine Arts in Cracow
His works have been purchased by the Frissiras Museum in Athen,  and appear in  private collections.
He was selected for shortlist  for „100 Painters of Tomorrow” – orgenised by Thames&Hudson and Beers. Lambert.


[Feature request] Current playing stops if removed from playlist

If the current song is removed from the playlist, the song stops halfway. I feel it would be better if the song keeps on playing while it completes, and no more. In other words, it is removed from the playlist, but it plays to completion anyway. Request acknowledgment/improvement.

The remove operation signifies that user doesn't want to have that song in his playlist, which is probably because he doesn't want to listen to it. So why would he want to play it to completion?
This currently happens not primarily because the song is removed but because next song is highlighted and it starts playing. If a song were playing which is not in the playlist, that would leave the player in an indeterminate state. Such a feature could be implemented when the last song of the playlist is removed.


Internet connectivity is lost after restarting the OVA

Problem
After restarting the OVA, sometimes the internet connectivity is lost, the IP address of the VM is also lost; commands that don't require the internet like hctl status raises an error.
This issue was also experienced during the hackathon, multiple users were using the same pre-configured OVA in cloudshare.
The solution was to revert back to an earlier snapshot or deploy/install a new OVA for the users which is not an ideal solution.
Expected behavior

Internet connection and/or IP address should not be lost after restarting a VM in this case OVA.

How to reproduce
Setup a new OVA, reboot the VM, then check is the vm has an IP address and if you can ping google.com
Note  This occurred in some VMs while in others, reboot was working with no issues.
Deployment information
VMware Workstation 16 Pro running on a Windows 10 machine using PI-7 doc
Additional information
No response

For the convenience of the Seagate development team, this issue has been mirrored in a private Seagate Jira Server: https://jts.seagate.com/browse/CORTX-33842. Note that community members will not be able to access that Jira server but that is not a problem since all activity in that Jira mirror will be copied into this GitHub issue.

@rshenoy0831, did you tested this scenario as raised?

@mukul-seagate11 we have tested this scenario. we have not observed this behaviour.

@r-wambui, as commented by Rahul who haven't observed this issue during QA validation so might be we can close this issue as we are also in the process of starting the next OVA release where most of the know bugs will be fixed

@mukul-seagate11 it sounds like since the team hasn't observed this issue, it wouldn't be a known isssue that would be fixed in a new release? We should probably identify the cause of this issue. Has anyone attempted to replicate this issue? We observed mulitple times. Before we close it, we'd like to know for certain that it has been fixed, or is no longer applicable in newer releases.

ova issues which are reported by community https://github.com/Seagate/cortx/issues?q=is%3Aopen+is%3Aissue+label%3Aova will be further raised to QA and tracked in next sprint

Havent observed this issue as per https://github.com/Seagate/cortx/pull/1644

https://github.com/Seagate/cortx/pull/1657 is validated as per latest OVA image and no issue is observed as well this was passed during the test entry criteria in https://seagate-systems.atlassian.net/wiki/spaces/PRIVATECOR/pages/1170014209/PI-8+Test+Entry+Criteria+Dev+OVA+Community+Build

@mukul-seagate11 were you able to replicate this in the tests for the release in which it occurred?


Improved color combination for the points

The blue dots on a grey background are really hard to see.
The yellow for selected dots is great.
I suggest white, cyan, or a very pale red/green/blue would all work well and make selecting loose points at the edge of the object much easier.

Done in #258


Technic Pack

Hello, I am running a server with the Technic Pack mod, http://technicpack.net for now it is currently 1.8.
My issue here is that: When I launch the server without "SimpleServer" everything is fine without any errors and that. When I launch it with "SimpleServer" and I log in, my character falls through the ground endlessly without dying or anything, but I can see the mobs (zombie, etc). Yes I used the 'SimpleServer' for 1.8. I also read the compatibility with the mods, I also tried running only IndustrialCraft, same effect. What am I doing wrong?
Regards.

Alright, I thank you for your support.


Implement step to connect db

#10 Added new Interfaces. And redesign step connection to database.

@rultor merge

@rultor merge

@smallcreep Done! FYI, the full log is here (took me 10min)


BugFix for case when subcommand contains command name

Before, this would fail to list commands which contain "sub-", like sub-sub-deploy.
The commands always include ${path} as evidenced by the line above, so including ${path} in the regex here is more precise.

Smart. Thank you!


(vlc) Added portable package as stream

closes #908

Per 1.1.7 default aliases are allowed. We already had this discussion number of times.

As per previous PR comment 1.1.7 states:
Use aliases sparingly. If you use them, limit their use to the default aliases which are read-only (can not be modified by the user), well known, and will be supported in the future versions of Powershell. Also ensure they are compatible with PowerShell v2+. (my emphasis)
1,1.7 doesn't allow the allow the use of aliases that are not read-only.

I will change that to reference  'default' aliases and remove all other notes which apparently only confuse people. It doesn't make any sense that I am allowed to use ri which nobody knows instead rm which everybody knows. Similar ls versus Get-ChildItem.

I wholly disagree with changing the documenation to fit the code style. The documentation is there to give everybody guidelines on what aliases should and should not be used. It's not confusing. It's very clear that non read-only aliases should not be used. They shouldl be used as:

It's bad practice;
Microsoft recommend against it;
And those two above are because aliases on an end user system are for the user to configure as they see fit. You don't know what those aliases point to. A script using ls that expects traditional ls output will break on my system here for example as I've customised it;

It doesn't make any sense that I am allowed to use ri which nobody knows instead rm which everybody knows. Similar ls versus Get-ChildItem.
I'm not sure I understand this argument.  The alias system is there to allow you to have shortcuts to your faviourite commands. ls is a default shortcut / alias for Get-ChildItem as it's a command used on Linux systems (which I'm sure you know) and therefore Linux admins get an easier transition over to PS. The same applies for dir for Windows people.
The alias system is there to be used by the end user.
But there are two issues you bring up. The first is something running on the end user device in a known environment. The other is why you write scripts.
RI is meaningless. It's two letters. Remove-Item is very clear. I can see right off the bat what it does. It removes an item. Same with any other alias. So the reason you don't use aliases, from that perspective is that it's not clear what an alias does. But the cmdlet is.
The reason the documenation (I'm assuming) says don't use non read-only aliases is that you do not know what they are on the end user device. The non read-only alias system is not a known environment. The read-only alias system IS a known environment (because you can guarantee that RI will be Remove-Item).
When I write scripts I don't use any aliases. That's my preference. However using the read-only ones is as close as you can get to that. Using the non read-only ones is asking for trouble. And when scripts start breaking on the end users system and they start complaining what are you going to tell them? That they amended their aliases which they are allowed to, and encouraged, to do? All that happnes there is that the reliability of Chocolatey packages that you maintain starts to disappear as people stop trusting your packages. And as a result Chocolatey will suffer too.

It's not confusing.

I consider myself master in Powershell and I never knew this. What do you think will be reaction of general user ?

I wholly disagree with changing the documenation to fit the code style.

You propopose that we change 200+ packages here to fit the documentation ?

It's bad practice

Its not, its a coding style.

Microsoft recommend against it

MS gives suggestion, not an obligation.

A script using ls that expects traditional ls output will break on my system here for example as I've customised it.

Its because you didn't use correct way, via proxy functions. Your system will break bunch of stuff without them.

The alias system is there to allow you to have shortcuts to your faviourite commands

This is your interpretation of alias system. Mine is that it reduces cognitive load.

The reason the documenation (I'm assuming) says don't use non read-only aliases is that you do not know what they are on the end user device

Since I wrote almost the complete guidelines, I am remember how it happened - we assumed default aliases are all readonly.

The read-only alias system is not and neither is changing the default cmdlets.

You can redefine read-only aliases too AFAIK. CBB to find the link now.

Using the non read-only ones is asking for trouble

That is retoric, not a fact. Here is the fact:  we didn't have any problems with aliases so far, there was only a single report for non existing alias once during last year.

All that happens there is that the reliability of Chocolatey packages that you maintain starts to disappear as people stop trusting your packages. And as a result Chocolatey will suffer too.

I think reliability of packages in this repository are leaps and bound over what we had a year before. Embedding and automation improves reliability the most, not the aliases or any other stuff.

Anyway, there are a lot of things to be done to improve packages. More automation, more helper functions, more testing etc. Aliases are the last thing we should discuss.

Besides all that I said here, making ALL packages here non-aliased and pushing fix version is basically trivial (expand aliases recursively and force update ), because we have a good system in place.

I consider myself master in Powershell and I never knew this.

I'm not sure what that adds.

What do you think will be reaction of general user ?

To?

You propopose that we change 200+ packages here to fit the documentation ?

No I propose that as we move forward that you remove aliases from your scripts. Just because it hasn't been done that way in the past doesn't mean you have to continue doing it that way. Do you propose to continue to use aliases that could potentially cause problems?

Its not, its a coding style.
MS gives suggestion, not an obligation.

https://blogs.technet.microsoft.com/heyscriptingguy/2012/04/21/when-you-should-use-powershell-aliases/
https://blogs.technet.microsoft.com/heyscriptingguy/2011/05/01/best-practice-for-using-aliases-in-powershell-scripts/
http://www.powertheshell.com/bp_script_alias/
https://github.com/PowerShell/PSScriptAnalyzer/issues/214
That's just the first ones that come up. PSScriptAnalyzer will flag you use aliases in scripts. Microsoft maintains PSScriptAnalyzer now. That's enough for me.

Its because you didn't use correct way, via proxy functions. Your system will break bunch of stuff without them.

My system doesn't break anything. I have no issues with anything, with the exception of your AU module which also uses aliases (I don't want to drag that into the discussion just making it clear that there are no issues except with one). If I had issues I'd revert back.
Aliases are not for you to use. They are for me to use, change, customise, edit, remove and generally do as I want with them. That's why some are  read-only (which I cant change) and some are not read-only (which I can). If aliases were to be used for distributed scripts they woudl make them all read-only so no matter which system you ran it on it would run as expected.

This is your interpretation of alias system. Mine is that it reduces cognitive load.

It's very far from my interpretation from the alias system. It's the way it was designed.
But you are right, it does reduce cognitive load and that's why they are for use on the command line. You know your environment. If you have access to the command line on another system you know the environment on there so you can using aliases without any issue. If you control the end system you know what aliases are on there too (for example at work you mnight have all of the end user devices have a particular set of aliases). But when you are distributing it to the wider world you don't have that control and you have no idea what those non read-only aliases map to.

Since I wrote almost the complete guidelines, I am remember how it happened - we assumed default aliases are all readonly.

They're not. Here are the red only ones get-alias | where { $_.options -match 'ReadOnly'}

You can redefine read-only aliases too AFAIK. CBB to find the link now.

I'm sure you can. That's what I was hinting at. You can also redefine cmdlets.
The point is that the alias system has read-only and non read-only aliases. If Microsoft didn't want you to change ANY aliases they'd have made them all read-only. If they enocuraged you to change any alias they'd have made none of them read-only. But they didn't. They made some read-only and some non read-only. So they give you the option of customising some aliases.
 So you are going to break something.
The same is said of overwriting Get-ChildItem (for example) with something else entirely. You are going to break things.
It's common sense. Customise what is intended to be customised (non read-only aliases) and leave the rest alone as you know you are not meant to do that (non read-only aliases and core cmdlets).

That is retoric, not a fact.

It's fact. Your AU module breaks on my system because it uses aliases. Nothing else EVER has broken on my system except that. I have 97 modules installed - 3 downloaded from Github, 6 installed by Choco or came with Windows 10, 12 downloaded from the PowerShell Gallery and the rest core modules. Every single one of them works without issues.

Here is the fact: we didn't have any problems with aliases so far, there was only a single report for non existing alias once during last year.

That's like saying I've never crashed my car so there is no need for me to wear a seat belt or get insurance. Non read-only aliases have the potential to cause problems which I have outlined. Just because it's nto been reported doesn't mean you shoudln't fix this issue. You don't get new tyres for the car when you have a blow out, you get them when it's pointed out to you that they have the potential to cuase you problems (ie. they are bald).
You've had at least 2 issues with AU (I know I mention it again but I'm trying to draw the distinction with aliases in both) that I have seen with regards to the use of aliases, one from me.
Here is also a fact: the use of aliases in scripts are considered bad practice by every single person I have ever spoken with, communicated with, know or respect in the PS community. They have the potential to cause issues which I have highlighted.

I think reliability of packages in this repository are leaps and bound over what we had a year before. Embedding and automation improves reliability the most, not the aliases or any other stuff.

Your missing the point entirely. You can't just point to something and say 'thats good' and ignore what's not. Otherwise nothing will evolve. The only reason that the embedding and automation was introduced is because somebody looked at what was there at the time and thought they could improve upon it. Do you stop improving the packages now? Do we not do any more evolution in the package design, moderation or checking?

Anyway, there are a lot of things to be done to improve packages. More automation, more helper functions, more testing etc. Aliases are the last thing we should discuss.

I absolutely disagree with you. I appreciate that you don't want to discuss them but that doesn't mean they shouldn't be. Not using aliases in packages is a quick fix. Just stop using them. And when future packages are amended, remove them. Install scripts are generally small so it will take seconds, perhaps a couple of minutes tops. And as it is a continuous process it won't add much to it.
I really do not understand your resistance to this. If something has the potential to cause the project problems, whether that potential hasn't been realised yet, or whether it's small or huge, it should be tackled. You weigh up the amount of work involved in tackling the issue with the risk and the gain. The amount of work to change new packages as you go along is tiny.

Besides all that I said here, making ALL packages here non-aliased and pushing fix version is basically trivial (expand aliases recursively and force update ), because we have a good system in place.

That's not what I was suggesting - what I was suggesting is amending packages as we go along. But if it's trivial to do all packages then that's a win win.

I'm not going to say anything about aliases, so you two can discuss that without me.
Anyways, @majkinetor don't forget to remove the upstream packages from Robs repo

vlc.portable isn't  on robs repo as far as I can see.

hmm, odd. Well, I guess I'll add the choco user then and merge this one in

no wait, it's still the meta package that still needs to be considered before we can start merge.
Currently the meta package isn't handled (unless I'm being blind)

I considered the metapackage and and didn't do it because the current package is not meta. I will not work on this package any more, I personally do not  think vlc portable is useful at all, I just did it to test streams PoC which wasn't well accepted anyway.


Freeze OSH repos

Currently the OSH are tracking master, which is a fast moving
target.
This is a problem, as master has introduced regressions in the
past.
This fixes it by setting a SHA for each of the consumed repos,
so that we have a more stable interface.

Yes it can be easily passed in user space.


Parsing Multiple Signing Certificates from IDP Metadata fails

https://github.com/onelogin/python3-saml/blob/34d22e005d21b7888d02588021bdf5a92391607b/src/onelogin/saml2/idp_metadata_parser.py#L203
I believe the first check len(certs) == 1 is not correct.  In the case where there are multiple signing certs, but no encryption certs, it throws away signing certs and only keeps the first one.  This is not correct behavior.

Can you provide a PR?

I will put one up shortly.

ty

https://github.com/onelogin/python3-saml/pull/65

Merged


Update pipeline generator tool version

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

Running them off branches. I'm doing a prepare-pipelines run first to test then will do the global one. Will link.

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

Passing js prepare pipelines run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1281480&view=results


Dragons should be pettable

Description

LET ME PET THE DERGIES!
Reproduction

Screenshots

Additional context

to handle this look at other uses of InteractionPopup in YAML, check where the localization strings for those are defined, and then add your own for dragon. and a sound + attribution if you want


Redirecting the angular login after api authentication

Hi, I am quite new with Angular, however am quite fluent in Laravel. Your framework is a breath of fresh air and i find it amazingly easy to use and fluent.
Having said that, could you please give me insight into how to redirect the angular app/views to a different page after a authentication request is successfull through the api?
I have followed your docs and tutorials, and get the toast popups validating authentication, however, I would like to extend this to allow for a redirect to a different angular route.
I hope I made the question clear enough.
Please let me know if you need more information

Laravel & Angular version: 3.2.0

I'm glad you enjoy developing using this starter 😄
Seems like this question is resolved, feel free to open a new issue if you more questions


How to map objects within other objects that are within other objects?

Documentation Related To Component:
"Map" in object
Please check those that apply

[ ] typo
[ ] documentation doesn't exist
[ ] documentation needs clarification
[ ] error(s) in example
[x] needs example

Description Of The Issue
I've been studying nodejs and I need to map all the path's of an obj.
See the object:
{
    path: 'mtw',
    return: 'hi',
    obj: {
        path: 'he-mele-no-lilo',
        return: 'hi',
        obj: {
            path: 'hawaiian',
            return: 'hi',
            obj: {
                path: 'swiss',
                return: 'hi',
                obj: {
                    path: 'altendorf',
                    return: 'hi',
                }
            }
        }
    }
}

I need to "map" all paths, taking into account that they can vary.
From what I read this is possible to be done with rxjs but I don't know how. Can anyone give me a "light"?

Stack Overflow would be a better forum for this question.


A few small changes.

Allow for "begin" and "after" operators to work on mix of unix timestamps and non unix timestamps.
Add tp.duration.to_string to the API (alias for tp.core.data.duration_utils.duration_abbreviation).
Run black .

Thanks

@achoum I think the docs are failing because you're missing the __init__.py inside temporian/api

@achoum I think the docs are failing because you're missing the __init__.py inside temporian/api

Awesome catch. Thanks.


feature: support management of local lua files.

Did you check the docs?

[X] I have read all the lazy.nvim docs

Is your feature request related to a problem? Please describe.
Use lazy.nvim to manage a local lua module.
Many people has their own lua snippet in vim's config path but not exist as a repo like module. They were hard to handle lazy loading/demand-on-loading/depends/event/cmd/keys.
Describe the solution you'd like
return {
  "configs/utils.lua" -- utils.lua was in $HOME/.config/nvim/lua/configs
  cmd = { "MyToggle" },
  keys = { { "<leader>t", "<cmd>MyToggle<cr>", desc = "MyToggle" } },
  dependencies = { "nvim-lua/plenary.nvim" },
}

Describe alternatives you've considered
Without this future, I could load it in VeryLazy event. But still needs to handle dependencies manually.
Additional context
No response

You can use dir= for that


deps: upgrade<EMAIL_ADDRESS>

Valid thing to check for sure - looking at the deep-equal changelog  and version history, these do serve their role in addressing more cases (fixing several bugs, though nothing stands out as obviously affecting us here) and some performance improvements in form of optimization.
Seems worth it to me, though not super clear-cut.
FWIW, as for dev, tape has also upgraded this dependency in #89, so the combination of these two is not as large of a net-increase in lockfile entries as it may first appear

To address thew question about size, when measured by yarn install --prod: This commit is an increase of 3284 b (27368 - 24084).
The main contributor here is object.assign clocking in at 1284b. It seems the maintainer is optimizing heavily for backwards-compatibility: https://github.com/inspect-js/node-deep-equal/pull/100
This package is using babel to address that. I think you're right @mcmire that this one isn't worth it.
Is object.assign et al worth filling in for still? Might be worth replacing deep-equal alltogether for something more appropriate.
Alternatively, 2.0.2 is the last version not depending on object.assign.

(then on the other hand, in context of metamask-extension, we already have a runtime dependency on the same version of object.assign :shrug: )


Degree-based orderings

Should we add it in the release 0.4.0 ?

It's not ready yet and it's not breaking so I'd say no. Bringing it up to speed with the latest developments isn't much work, the trouble is rather finding ways to test that the orders are correct


Add grafana dashboard for SS proxy

A grafana dashboard with charts to track various sliding sync proxy metrics

Some people have told me this works for them, so let's land it now rather than letting this fester.


Upgrade to Accounts 2.0.22.Final and Commons 0.4.0.Final

@lucasponce could you please review and eventually merge?

@jshaughn in master it's missing the commits from 1.0.0.Final version to create the next iteration.
Please can you push them before merging this one ?


Remove m.hotmail.com

I'm requesting to remove m.hotmail.com from Telemetry/hosts, the reason is explained here:
https://github.com/StevenBlack/hosts/issues/193

Telemetry was purged.
See https://github.com/StevenBlack/hosts/tree/master/data/WindowsSpyBlocker

Fine, but I'm on Linux. And my client can't fetch new emails from the live mail.
Have you checked if that connection occurs when you use a local account? Because if I'm not wrong on Win10 your emails will be synchronised automatically if you use a MS account.

Simpy add m.hotmail.com and other reqired domain to whitelist file and regenerate hosts file.


Typo "[Microsoft Teams Room recovery tool]"→"[Microsoft Teams Rooms r…

…ecovery tool]"
https://docs.microsoft.com/en-us/microsoftteams/rooms/rooms-operations
https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/blob/live/Teams/rooms/rooms-operations.md
#PingMSFTDocs

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


WIP: Initial Evaluation Predictions

This is an initial PR to predict a set of output heatmaps for one given data generated image.
Example command to run evaluation.py (make sure the model json and model weights are in the current directory):
python evaluation.py --model-json hpe_hourglass_stacks_04_batchsize_012.json --model-weights hpe_epoch39_val_loss_23851522048.0000_train_loss_0.0192.hdf5 --subset 0.1 --hourglass 4
I've been writing the heatmap images to local disk and overlayed the 17 outputted heatmaps on top of each other into result.png, but they tend to cancel each other out, we might want to find a better way of converting this output back into keypoints before we merge them.

Looks great @nicolepeverley ! yeah overlaying all the heat maps might be an issue. I think we shouldn't stack the heatmaps together yet. At least, not until our model does something. I think the most useful would be a tiling of outputs in one of the following forms:

for each output layer (including intermediate layers), generate a set of all 17 outputs in a row (np.hstack should do the trick), followed by the corresponding ground truths on the row below (maybe even overlay the ground truth on the original image).
similar to 1, but the first row has the ground truths, and then each layer below is the output from layer 0 to layer n (which is the final output). Basically, 1 but vertically stack each row (np.vstack I think).

I think (2) would be better since we can see the progression of predictions across each HG stack. @julianrocha thoughts?
The image names ideally should keep track of the epoch information. Easiest way is to probably find some way to reuse the filename since it should be ..._epoch_{:02d}_....

Looks great so far. I agree with @robertklee that there is gonna be quite a bit of work to get a nice plot setup that captures the model output in an understandable way. I think in an ideal world option (2) that Robert suggested would give us the most insight. In all cases, overlaying a heatmap over an image rather than plotting the heatmap by itself would be preferable. Obviously, that's gonna take some time to configure perfectly so we can start with just one joint, or the last hourglass layer and work from there. My only suggestion would be to change the plots to be generated online without needing to write to disk as it would be quicker to try different images but this is contingent on us figuring out the matplot versioning issues that are plaguing some of our local python env setups. That being said, some of these 17kp*(8hg + 1 gt) grids of heatmap plots are probably gonna be massive, so an image file that can be zoomed on may be easier to work with. Your call.

Stacked output of each hourglass set of heatmaps and ground truth heatmaps for a given image:

The last commit stacks the output for better visualization, I'm going to check to see if these images need to be saved to disk to accomplish this or not 👍 @julianrocha

Looks great!!!

@Airborne95 and I discussed evaluation moving forward and we're going to update the architecture to look similar to data_generator.py and data_generator_tests.py stay tuned!

Okay so the reason I was having trouble vertically stacking/concatenating the predicted heatmaps and ground truth heatmaps  is because the ground truth heatmaps get returned as 3 dimensional np arrays (our predicted heatmaps are 2 dimensional np arrays). I'm not sure how to get around this so for now I've left it that if you want to see the predicted heatmaps and ground truth heatmaps stacked together you'll have to save them!

We can explore this tiny QOL improvement after merging though


Authconfig structure is overloaded

We should keep configuration consistent across projects. We are adding compartment and instance principal logic to the AuthConfig struct which doesn't make logical sense.

I think that we should leave the AuthConfig alone, however we should move the instance principles flag out of the AuthConfig and into Config. Both Auth and UseInstancePrincipals can be made optional with the logic to validate one or the other exists.


Passive feedback form crashing on iOS & not closing properly on Android

Opening the passive feedback form on iOS
A crash occurs if the back button is pressed. Also selecting the stars option and feeding in the gender info crashes our app. The error in both cases is *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'Application tried to present modally an active controller <UIViewController: 0x7fef40622520>.'.
I tested this with the latest release v0.8.0. 😎
Closing the passive feedback form on Android
On a positive note, the form doesn't crash on Android. However, since there's no method to close the form with, navigating back with the hardware button closes our app.
Screenshots
Here's the feedback form. Other than opening, it really doesn't work on our app's iOS version. 🔥 🚒

We have this problem in our production build on iOS. The form crashes frequently.
How quickly can you guys get this crashing phenomenon resolved?

Hi @klaevv ,
I just did a test with our test app that we have provided in this repository: https://github.com/usabilla/usabilla-u4a-react-native/tree/master/UsabillaSampleApp
I have no problem providing feedback through star ratings or with closing the form. Also tested with the latest release v0.8.0. I would advise you to check the app.js script in the example app to see how you can implement Usabilla successfully.
I hope this helps. Please let me know if you have any further questions.

I double checked and the implementation is in accordance with your example app. It does work on Android, so the implementation is probably ok.
I also debugged the callbacks and noticed that setFormDidLoadSuccessfully calls its function reference twice, which could be why the crahs occurs. Other than that, I don't see anything unusual with the app regarding the feedback form.
Do you think the double callback is the issue?

Hi @klaevv ,
If you've followed the same implementation as outlined in the example app then there might be an issue with that specific formID for iOS specifically.
What I can do is to test with your formID on iOS, just to be sure there are no account-specific issues you're running into. Also, is there a specific device you're testing with or does the crash occur on all iOS devices? Feel free to send your Usabilla account name and formID to<EMAIL_ADDRESS>Looking forward to your reply.

The crash has occurred on multiple iOS devices. I'll send the details via mail. Thanks.

Hi @klaevv,
I just had a test with your formID and I'm able to leave feedback and closing the form without any issues. Here is the feedback item.

If you have any other steps to reproduce this, then please let me know.

I was able to get the form working with your demo project. However it remains a mystery why the crash occurs on iOS with our app.
While our app is more complex than the provided example, the passive feedback form is implemented exactly as the documentation says. I had to disable it on our iOS version for now 🌚

Hi @klaevv ,
Great to hear you made it work with the example project. Then you at least have something to cross-reference with. If the implementation is done in the same way then maybe it's time to look at the differentiators between the working example and yours. There might be some other underlying things interfering with the Usabilla form. Following the stack trace should at least give you the source of the initiator of the crash.

Support delivered through email, closing thread


Adv. Solar Panel uncraftable due to crash.

https://gist.github.com/anonymous/58fc8d103cdc00494aa518a82d7151b1

Do not use the TC crafting table.


VM: Fix unmount race during LXD startup of running VMs

Fixes an issue introduced by advertiseVsockAddress by removing mount & unmount calls from generateAgentCert.
We expect the callers of generateAgentCert to have ascertained whether the VM is running (and therefore mounted) before calling this function.
By making this change it prevents a mount/unmount race when LXD starts up during the devicesRegister function call.
During this function call, each instance has its IsRunning() function called to check if it needs its devices registered. For disk devices of running instances its important that their Registerfunctions are called on LXD start in order to initialise the mount counter for that disk (so that a subsequent unmount call isn't incorrectly run if LXD incorrectly thinks that the disk volume isn't in use anymore).
For VMs the initial call to IsRunning() is also important as that triggers a reconnection to the QEMU QMP monitor in the running VM and allows for gathering the lxd-agent run status.
The mount/unmount race before the disk devices have been registered is caused because the IsRunning call initialises the getMonitorEventHandler and causes it to call the advertiseVsockAddress function, which in turn uses generateAgentCert as part of creating a connection to the lxd-agent over vsock.
The getMonitorEventHandler handler is run in a separate goroutine and thus it can race the disk device's Register function (which would initialise the mount counter so that an unmount call would not be issued as the volume would be considered in use).
If the generateAgentCert function finishes before the disk device's Register function then an unmount call is incorrectly attempted on the running VM's root disk causing delays to LXDs start up (as the unmount call blocks for several seconds).
By removing the mount management from the generateAgentCert function it ensures that no early unmount attempt can occur, and doesn't affect the operation of the function as it is required that the VM be running (and thus mounted) in order to connect to the lxd-agent anyway.

Testsuite passed


New version: UnifyJustTheDocs v0.3.6

Registering package: UnifyJustTheDocs
Repository: https://github.com/neelsmith/UnifyJustTheDocs.jl
Created by: @neelsmith
Version: v0.3.6
Commit: cccd4c76a3e1436ce49631afe48c709e94e6fb87
Git reference: main
Description: Create a single markdown string from a web site organized using YAML headers from the just-the-docs theme.
Release notes:

Allow modern version of Documenter

Probably simplest to resubmit a new PR since 0.3.5 is merged now.


Add support for DVRLIVE

Description

Problem
We do not support the DVRLIVE feature from YoSpace yet. The DVRLIVE feature allows us to not relly on metadata events but use the current time instead also for live streams.
Changes
Added a new DVRLIVE option to the YospaceAssetType and handle it accordingly in the YoSpace integration. See comments below for details.
Checklist (for PR submitter and reviewers)

[x] CHANGELOG entry

@dweinber Please have a dedicated look at my relative playhead time reporting workaround here: 7996fdf

Code looks good so far 👍
One thing though: With the DVRLive type we don't need the serviceworker anymore in Safari, which we needed (for most scenarios) with Linear. In the BitmovinYospacePlayer we "enforce" its usage by setting the serviceworker script location and enabling the native_hls_parsing tweak:
...

As discussed offline, we keep the service worker stuff as it is for now.


Service in csv file with Lat Long Not Showing Up on App: ISSofBC Welcome Centre - Surrey

Testing:
Production V1.7.0, Server V1.3.12
iOS 13.1.2 iPhone 7 plus
at Surrey Public Library on Oct 4, 2019
Issue:
ISSofBC Welcome Centre - Surrey (ID 59807644) did not show up on the app although the service record is included in the uploaded csv file with the correct lat long (49.11588, -122.80003) on bc211 dataset.
Acceptance Criteria

[ ] ISSofBC Welcome Centre - Surrey should be in the service listing under the topic "Contact workers at your local settlement agency" when you're testing in Surrey

Steps for QA: (Location: Surrey)

Go to Home page
Under "Things to do right away", select topic "Contact workers at your local settlement agency"
Click "Find related services near me" button
Check the service listing for ISSofBC Welcome Centre

Here are the services that currently show up under this topic in Surrey:

Tested Staging V1.6.0 server 1.3.13 at Prado Cafe near Surrey Central Station on iOS 13.1.2 iPhone 7 Plus: ISSofBC Welcome Centre - Surrey now appears in the search results for the topic "Contact workers at your local settlement agency"
Note:
When I searched "contact workers at your local settlement agency" the first time, the search results in Prod V1.7.0 Server 1.3.12 and those in Staging V1.6.0 server 1.3.13 are the same (total count: 30 services), EXCEPT:

Prod V1.7.0 Server 1.3.12 results contain: MOSAIC - Family Centre (service ID 9509477), but not ISS of BC - Welcome Centre Surrey (service ID 59807644)
Staging V1.6.0 server 1.3.13 results contain: ISS of BC Welcome Centre - Surrey (service ID 59807644), but not MOSAIC - Family Centre (service ID 9509477)

The second time searching from the same spot using same wifi, ISS of BC Welcome Centre - Surrey appeared in both Prod and Staging search results. Maybe due to latlong changes every time a search is run.

Screenshots of search results from Staging 1.6.0 Server 1.3.13 on this topic can be found here https://drive.google.com/drive/folders/122lWk7OoLj-d0XR5G4VRPC9UQGuorKNf?usp=sharing


There is another bug in "invoke_func" function

Similar to this issue, nan:0x200000 and -nan:0x200000 cannot be parsed, and the same error message "invalid float literal" is reported.
In addition, -nan is parsed into nan, which is incorrect. nan and-nan represent different meanings, and their bits are different.

Yes this is expected as the CLI uses the Rust standard libray to parse floats right now, which is not the same as the text format of WebAssembly.

Yes this is expected as the CLI uses the Rust standard libray to parse floats right now, which is not the same as the text format of WebAssembly.

Is that going to fix the problem?

Sorry I'm not sure if I understand your question?
To clarify what I'm saying, the parsing of f32/f64 in the CLI isn't specified right now in Wasmtime and it's "whatever rust libstd happens to implement". The syntax you're describing here I think is probably coming from the text format of WebAssembly, however, which isn't plumbed into this part of Wasmtime right now. Assuming you want the same text format of WebAssembly then yes I believe that will resolve this issue.

Yes brother, I shouldn't describe it as a problem, this format is from webAssembly. It would be great if wasmtime should support this format in the future.


How to use own theme and image flickering

First thanks for the module. It's nice, easy and seems to work how a gallery should.
There should an option to change the colorAccent without having to implement your own theme. I just wanted to change all the purple to my app color. If I use my own theme, I lose the Toolbar navigation.  The only thing I've been able to do is manually add the module to my project then change the colors.
Do you know what I need to do in order to use the Theme option for my theme and still see the back arrows and close button?
2nd when you preview an image in a bucket, it sometimes flickers multiple times.

Hi @tolew1, Thanks.
For your first question, we currently don't have an official API for changing just one colour of Fallery, but you can override the colours below with your desired colours in the colors.xml file.
<color name="fallery_dracula_colorAccent" tools:node="replace">{Your Desired Color}</color>
<color name="fallery_light_colorAccent" tools:node="replace">{Your Desired Color}</color>

Here you can see all the colours you can override for both themes.
  <!-- dracula theme colors -->
    <color name="fallery_dracula_backgroundColor">#151e27</color>
    <color name="fallery_dracula_colorPrimary">#212d3b</color>
    <color name="fallery_dracula_colorPrimaryDark">#151e27</color>
    <color name="fallery_dracula_colorAccent">#5ea3de</color>
    <color name="fallery_dracula_iconTintColor">#7a8694</color>
    <color name="fallery_dracula_toolbarIconTintColor">#ffffff</color>
    <color name="fallery_dracula_primaryTextColor">#ffffff</color>
    <color name="fallery_dracula_secondaryTextColor">#7c8896</color>
    <color name="fallery_dracula_hint_text_color">#697686</color>
    <color name="fallery_dracula_place_holder_color">#1d2733</color>
    <color name="fallery_dracula_toolbar_text_color">#FFFFFF</color>

    <!-- light theme colors -->
    <color name="fallery_light_backgroundColor">#ffffff</color>
    <color name="fallery_light_colorPrimary">#ffffff</color>
    <color name="fallery_light_colorPrimaryDark">#CFD8DC</color>
    <color name="fallery_light_colorAccent">#A11183</color>
    <color name="fallery_light_iconTintColor">#504f4f</color>
    <color name="fallery_light_toolbarIconTintColor">#504f4f</color>
    <color name="fallery_light_primaryTextColor">#000000</color>
    <color name="fallery_light_secondaryTextColor">#999999</color>
    <color name="fallery_light_hint_text_color">#999999</color>
    <color name="fallery_light_place_holder_color">#EEEEEE</color>
    <color name="fallery_light_toolbar_text_color">#000000</color>

For your second question, please share more information with me: the device model and Android version. Also, if you can record the screen, it would be great.
Thanks for your contributions.

Hi, I'll try and see if I can get a screen cap


feat(worksheet): add implementation for worksheet

What type of PR is this?
type-feature

What this PR does / why we need it:
add implementation for worksheet
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Additional documentation e.g., usage docs, etc.:

@yizhouxw I've implemented your suggestion, please take a look when you have a chance.


history.getCurrentLocation key differs when calling in server and browser

Originally reported here: https://github.com/reactjs/react-router-redux/issues/528#issuecomment-280062297
history.getCurrentLocation()
When called on server yields a key of null and has a key in the browser.
Can the logic used to create this key be equal in both environments?
Thank you!

I'm not supporting version 3 any more. Please send a PR if you'd like to get this fixed.

Is this fixed in v4?

history.getCurrentLocation is gone in v4. Instead, you use history.location directly.
In the browser, location.key will always be null on the initial page load. If you need a key, just use some other constant like "root".

OK great, I'll try to update the example on github with latest history/react-router-redux/react-router.

@mjackson this is still an issue in v4. The location.key differs from client and server. Should I open a new issue with reproduction case?

@michaelBenin Yes, if you've got a problem with how the code works please open an issue. Even better would be to open a PR with a suggested fix :)

Sure thing! Thank you!

Hey @mjackson before I add this feature I wanted to ask if I was possibly missing something.
When we call createHistory from browserHistory how would you feel about passing an initial key there? This would prevent the invariant error I'm finding.
Currently I have this working:
const browserHistory = createHistory();
browserHistory.location.key = bootstrappedConfig.routing.location.key;

Where bootstrapped config is my redux store from the server.
It would be great if we could pass createBrowserHistory the key that is generated from the server.
Here is the code on the server which creates that location:
const memoryHistory = createMemoryHistory(req.url);

Moved to an open issue: https://github.com/ReactTraining/history/issues/458


Feature/timetable feature grid2

Issue

??

Overview (Required)

Added very basic gridview to iOS timetable
Will need additional fixes before full release

Links

Screenshot (Optional if screenshot test is present or unrelated to UI)

Before
After

Movie (Optional)

Before
After

@shin-usu Tested with the new TimetableRoom location and there are no problems.

New build fail due to movement of shape?

timetableItem.room.shape

This built locally but I will investigate the error and fix it before moving forward

Looks like a merge just right after my last pull broke it. I will look for a work-around

@shin-usu Responded to comments.

also @ry-itto I responded to your comments.

No other places of concern other than ry-itto's comment.
Thanks for the correction😊
Please wait ry-itto's review.

@ry-itto Fixed as recommended. Thank you


Does Cooperative A* work?

Describe the bug
WWWWWWWWWWWWWWWWWWWW
WW___________________WWWWWW
W_A___B____________goalB_goalA_W
WWWWWWWWWWWWWWWWWWWW
Robot A can't find its path in the scenario above.
To Reproduce
Steps to reproduce the behavior:

Set the wall and A,B in the above
Run simulation

Expected behavior
A and B finds its path, respectively.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Ubuntu 20.04
Browser Chrome

Additional context
I see "WARNING Path not found for agent [A]" in the terminal.

Hi there,
There's some significant work to be done on Cooperative A*. This situation is one of them. If you switch B and A it will work. I'll see what I can do but I think it might just be re-running an A* on the agents that failed to find a path after computing other's paths. Eitherway, I'll soon get going on Enhanced Conflict Based Search (ECBS) that will be significantly better than CA*, which to be honest I don't like at all.

Hi again @yjkim046, can you share the snippet of code for initialization of the World/Agents so I can reproduce the same sequence ?

Hi @yjkim046, from a first look at the problem it seems as if it is failing because there arises a case of "collision" during the plan. In the sense that once robot B has found the goal, it is acting like an obstacle for robot A's plan. I am not entirely sure if this is the exact cause of the problem, but maybe you can provide us with either the log or the application code for the bug to reproducable, as @guilyx said.


underscores/snake case vs camelCase naming conventions

When looking at the gtfs-realtime.proto file, field names use underscores like active_period in Alert or current_stop_sequence in VehiclePosition.
Likewise, the ASCII representation example shows all field names with underscores: https://developers.google.com/transit/gtfs-realtime/examples/trip-updates-full  As does the reference on both https://gtfs.org/reference/realtime/v2/ and https://developers.google.com/transit/gtfs-realtime/reference
However, to use the nodejs bindings (I haven't checked the others), it requires all attributes to be in camelCase and this applies for both input and output, so you get activePeriod and currentStopSequence.
We use fromObject to convert a JSON GTFS-RT representation into Protobuf, and this was developed using underscores in field names. We can pass the data through a converter to change to camelCase, but wondering if I am missing something here? Shouldn't documentation (linked above) either refer to fields in camelCase or the bindings use underscores for both input/output?
It also means the example code here for nodejs doesn't work and should actually be entity.tripUpdate?
var feed = GtfsRealtimeBindings.transit_realtime.FeedMessage.decode(body);
    feed.entity.forEach(function(entity) {
      if (entity.trip_update) {
        console.log(entity.trip_update);
      }
});

Furthermore, looking to confirm that camelCase on field names is expected for GTFS-RT feeds globally? Passing ones through the FeedMessage.decode function definitely makes this seem the case.

@nzphoenix Good question! So there are several questions here, and I'll try to answer them to the best of my knowledge.

When looking at the gtfs-realtime.proto file, field names use underscores like active_period in Alert or current_stop_sequence in VehiclePosition.

Yes - this is the canonical way to represent field names in Protocol Buffer .proto files, with message names in CamelCase. See https://developers.google.com/protocol-buffers/docs/style#message_and_field_names.

However, to use the nodejs bindings (I haven't checked the others), it requires all attributes to be in camelCase and this applies for both input and output, so you get activePeriod and currentStopSequence.

This differs depending on the programming language and protocol buffer compiler used to generate the bindings. If you look at the above link, using the official Google compiler C++ uses snake_case and Java uses camelCase.

It also means the example code here for nodejs doesn't work and should actually be entity.tripUpdate?

I haven't used the NodeJS bindings myself, but I just added another commit (https://github.com/MobilityData/gtfs-realtime-bindings/commit/9354c5073badbd4fbfc54bbed17f5c4428afebcd) to test this, and it looks like you're right - this test passes for me in IntelliJ:
assert.equal(vehicle.trip.tripId, "t0")

So the notation to access the trip ID variable is camelCase for NodeJS, and we should fix the example - please let me know if you can confirm that the above test (or a similar one also testing camelCase access) works for you.

We use fromObject to convert a JSON GTFS-RT representation into Protobuf, and this was developed using underscores in field names. We can pass the data through a converter to change to camelCase, but wondering if I am missing something here? Shouldn't documentation (linked above) either refer to fields in camelCase or the bindings use underscores for both input/output?

The primary use case for Protocol Buffers is writing to binary and then parsing from binary, in which case you don't have an intermediate text format at all - this is how I'm used to using Protocol Buffers. The only case where I've used the text functions is to transform the binary into something human readable to see the contents - but in this case the naming convention doesn't matter because I'm not using it as something machine readable. Unlike the binary format, I'm not sure if the generated text format is standardized across different protocol buffer compilers and languages. I'd welcome feedback from anyone else that has more information about this.

According to Google's documentation, Proto3 supports a canonical encoding in JSON, which can be used for serializing protobuf data into a text-based format that can also be handled by all other languages that support Proto3. However, the GTFS-RT uses Proto2 syntax rather than Proto3, which means that (as far as I'm aware... and as far as I can find in the official documentation) you can't reliably depend on transferring this Proto2 data by use of JSON serialization helper methods.

Closing this issue, the question has been answered. Thanks @jameslinjl  and @barbeau !


[Feature]: add codeql workflow for Python

Describe the feature
The repository contains code in Python , it does not have workflow for code scanning.
How would you like to see it implemented?
I aim to implement the CodeQL workflow to automate security checks. CodeQL, GitHub's code analysis engine, will identify vulnerabilities in the code and present the findings as code scanning alerts. This workflow will be activated for every push, commit, and pull request through GitHub Actions.
Record

[X] I'm a SSOC'24 contributor
[X] I agree to follow project's code of conduct
[X] I want to work on this issue

@harmeetsingh11 not required.


xss defacement bug is removed can you tell me which version was it [🚀]

Hello team,
I want to try the xss webpage defacement and I have installed the latest version of it. But when I try in it didn't work, the xss on the username is not working.
can you please tell me in which version it is available on.

Username has a persisted XSS vuln, so in case you're using Docker or Heroku, the challenge might just be disabled by default. Check https://pwning.owasp-juice.shop/companion-guide/latest/part1/challenges.html#_potentially_dangerous_challenges for details.


[WARNING] Expected identifier but found "*"

🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑
Please do not file questions or support requests on the GitHub issues tracker.
You can get your questions answered using other communication channels. Please see:
https://github.com/angular/angular-cli/blob/master/CONTRIBUTING.md#question
Thank you!
🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑

Thanks for reporting this issue. However, you didn't provide sufficient information for us to understand and reproduce the problem. Please check out our submission guidelines to understand why we can't act on issues that are lacking important information.
If the problem still exists in your application, please open a new issue and follow the instructions in the issue template.


VS Code Integrated terminal colors don't match external terminal themes

The terminal colors for the VS Code theme don't match what is available for the terminal theme.
Can these colors be added/fixed?
Integrated terminal colors documentation
Correct (Alacritty)

Incorrect (VS Code Integrated Terminal)

Hi @redoxeon , since we can have more than one external terminal and different people can use different terminals and these terminals as ports will probably never go without differences, it will be troublesome to try to combine a specific one, for now I believe keeping vscode as it is better. 💜


Automatically manage trailing commas when running with --google-style

Commas are added/removed according to the following rules:

Lambda param lists => remove
Single element lists => remove
Lists that fit on one line => remove
All other lists (multiline lists) => add

@davidtorosyan @hick209 @cgrushko
I know we talked about this idea a bit several months ago. I've limited the impl to --google-style, but it could easily be expanded to more styles, or possibly a separate flag.

@hick209 Is anyone available to review?

Hey @nreid260, sorry I'm out on paternity leave.
I'll ping the group internally to get into this though

Ooooh, yeah that seems fine.


deactivate cards

I can't find how to deactivate cards in the sdk:
https://github.com/Mangopay/mangopay2-nodejs-sdk/blob/master/docs/Cards.md

I found a way looking into the code
mpay.Cards.update({Id: cardId, Active: false}).then(result => {...})
A function like for the IBAN would be more intuitive, plus it's not documented that Id will serve as path.

Hello @dfa1234 !
Happy to see you've found by yourself :)
We could add a proper function to deactivate card, but updates available through our API on cards are very limited that we did not feel useful to add dedicated function for it.
But thanks a lot for your feedback, I'll keep it in mind.
Mickaël


function createCampaign

mutation.ts:261 Error: Function "createCampaign" requires 6 arguments, but 0 were provided.
Expected function signature: contract.call("createCampaign", [_owner: string, _title: string, _description: string, _target: BigNumberish, _deadline: BigNumberish, _image: string]): Promise
at ContractWrapper.call (contract-publisher-29ba9ed4.browser.esm.js:8532:13)
at SmartContract.call (contract-publisher-29ba9ed4.browser.esm.js:20300:33)
at Object.mutationFn (useTransactions-5b3be9b8.browser.esm.js:2859:21)
at Object.fn (mutation.ts:179:31)
at run (retryer.ts:147:31)
at createRetryer (retryer.ts:204:5)
at executeMutation (mutation.ts:174:22)
at Mutation.execute (mutation.ts:216:26)
at async publishCampaign (index.jsx:18:26)
at async CreateCampaign.jsx:32:9

We can solve this bug just adding args:[] inside the publicCampaign
File Path
client > src > context > index.js

// Here we are connecting web3 with the client

import React, { useContext, createContext } from 'react';
import { useAddress, useContract, useMetamask, useContractWrite } from '@thirdweb-dev/react';
import { ethers } from "ethers";

const StateContext = createContext();

export const StateContextProvider = ({ children }) => {
    const { contract } = useContract('0x7045fe828a26e4B24B46A6902998C5F73aeF7144');
    const { mutateAsync: createCampaign } = useContractWrite(contract, 'createCampaign')

    const address = useAddress();
    const connect = useMetamask();

    const publishCampaign = async (form) => {
        try {
            const data = await createCampaign({args: [
                    address, // owner
                    form.title, // title
                    form.description, // description
                    form.target,
                    new Date(form.deadline).getTime(), // deadline
                    form.image // image
            ]});

            console.log("contract call success", data)
        } catch (error) {
            console.log("contract call failure", error)
        }
    }

    return (
        <StateContext.Provider
            value={{
                address,
                contract,
                connect,
                createCampaign: publishCampaign,
            }}
        >
            {children}
        </StateContext.Provider>
    )
}

export const useStateContext = () => useContext(StateContext);


OSError: Cannot identify image file

Hello,
Currently, I am trying to train the U-Net Model for the classification of land cover. The input image is a 16-bit unsigned integer Tiff file of 4 bands (Blue, Green, Red and NIR). The training data are in vector format which I converted to unsigned int 8 bit Tiff as well as Exported the Traning data for Deep Learning as "Classified Tiles" per Instructions shown in the link. (Extracting Building Footprint from Drone Data). But I'm stuck in data preparation it gives an error as "Cannot Identify Image File".
Could you suggest how can I resolve this issue?

Hi,
The training works on 8 bit 3 band data. You would need to apply a  Extract Band function/tool to the input image to make it 3 bands before exporting and training.

Thank you. It did work after I converted them to 8 bit.

I get same error: OSError: Cannot identify image file.
I have converted to 8 bit but this couldnt resolve this problem. Can you help me in this regard.


New version

Hi!
I saw that you have a new version out! Where can I read more about what is new?

Hi @luuude, thank you for asking!
We also released new arXiv version of our paper here 👉https://arxiv.org/pdf/2406.01493👈
Basically, we proposed a new training and inference strategy to improve temporal consistency, see 3.2 section in the paper.


routerMiddleware.global.js call twice on server

Environment

Operating System: Linux
Node Version:     v16.14.2
Nuxt Version:     3.4.2
Nitro Version:    2.3.3
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
https://stackblitz.com/edit/nuxt-starter-ebbpgn?file=pages%2Findex.vue,pages%2Fforbidden.vue,app.vue,middleware%2FrouterMiddleware.global.js
open /forbidden link on client, and reload page. Result in terminal console.
Describe the bug
router middleware calling twice, when using navigateTo.
Additional context
No response
Logs
No response

This is vue-router behaviour and is not caused by Nuxt: see https://stackblitz.com/edit/github-8dvck9?file=src/router.ts.


Largest word in a sentence question

Description
This is one of the questions that will tell us how play with the line in c++ , So I will explain everything in the question which will be great for learning of basics about string.
Domain
CPP
Type of Contribution
Addition
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of LearnCPP.

/assign

/assign


Prevent eval breakage in CUDA extensions

Description of changes
For both cuDNN and TensorRT, add a fallback mechanism when passed a CUDA version not in the table of default package versions for CUDA versions.  Previously, adding a new CUDA version would break these extensions.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

See also #185557

I'm getting the following evaluation error when attempting to run nixpkgs-review:
skainswo in doodoo in nixpkgs on  master [$] took 23s
❯ nixpkgs-review pr --post-result --build-args "--max-jobs 192" 192958
$ git -c fetch.prune=false fetch --no-tags --force https://github.com/NixOS/nixpkgs master:refs/nixpkgs-review/0 pull/192958/head:refs/nixpkgs-review/1
remote: Enumerating objects: 18, done.
remote: Counting objects: 100% (18/18), done.
remote: Compressing objects: 100% (13/13), done.
remote: Total 18 (delta 6), reused 14 (delta 5), pack-reused 0
Unpacking objects: 100% (18/18), 56.35 KiB | 801.00 KiB/s, done.
From https://github.com/NixOS/nixpkgs
   252244a9fd7..70168c4fde0  master                -> refs/nixpkgs-review/0
   54fd3e5b7f3..356a60d23d9  refs/pull/192958/head -> refs/nixpkgs-review/1
$ git worktree add /home/skainswo/.cache/nixpkgs-review/pr-192958/nixpkgs 70168c4fde028ec5f7876da7c662cd9a7854c267
Preparing worktree (detached HEAD 70168c4fde0)
Updating files: 100% (31952/31952), done.
HEAD is now at 70168c4fde0 crun: drop criu workaround
$ nix-env --option system x86_64-linux -f /home/skainswo/.cache/nixpkgs-review/pr-192958/nixpkgs -qaP --xml --out-path --show-trace
$ git merge --no-commit --no-ff 356a60d23d97bc678efdbf24ddbe681c80191126
Automatic merge went well; stopped before committing as requested
$ nix-env --option system x86_64-linux -f /home/skainswo/.cache/nixpkgs-review/pr-192958/nixpkgs -qaP --xml --out-path --show-trace --meta
error: attribute 'cudnn_8_3_2' missing

       at /home/skainswo/.cache/nixpkgs-review/pr-192958/nixpkgs/pkgs/development/libraries/science/math/cudnn/extension.nix:30:32:

           29|     # Set the default attributes, e.g. cudnn = cudnn_8_3_1;
           30|     defaultBuild = { "cudnn" = allBuilds.${computeName cuDnnDefaultVersion}; };
             |                                ^
           31|   in allBuilds // defaultBuild;

       … while evaluating the attribute 'cudnn'

       at /home/skainswo/.cache/nixpkgs-review/pr-192958/nixpkgs/pkgs/development/libraries/science/math/cudnn/extension.nix:30:22:

           29|     # Set the default attributes, e.g. cudnn = cudnn_8_3_1;
           30|     defaultBuild = { "cudnn" = allBuilds.${computeName cuDnnDefaultVersion}; };
             |                      ^
           31|   in allBuilds // defaultBuild;

       … while evaluating 'isDerivation'

       at /home/skainswo/.cache/nixpkgs-review/pr-192958/nixpkgs/lib/attrsets.nix:427:18:

          426|   */
          427|   isDerivation = x: x.type or null == "derivation";
             |                  ^
          428|

       … from call site

       at /home/skainswo/.cache/nixpkgs-review/pr-192958/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:193:8:

          192|   checkDependencyList' = positions: name: deps: lib.flip lib.imap1 deps (index: dep:
          193|     if lib.isDerivation dep || isNull dep || builtins.typeOf dep == "string" || builtins.typeOf dep == "path" then dep
             |        ^
          194|     else if lib.isList dep then checkDependencyList' ([index] ++ positions) name dep

       … while evaluating anonymous lambda

       at /home/skainswo/.cache/nixpkgs-review/pr-192958/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:192:81:

          191|   checkDependencyList = checkDependencyList' [];
          192|   checkDependencyList' = positions: name: deps: lib.flip lib.imap1 deps (index: dep:
             |                                                                                ^
          193|     if lib.isDerivation dep || isNull dep || builtins.typeOf dep == "string" || builtins.typeOf dep == "path" then dep

       … from call site

       at /home/skainswo/.cache/nixpkgs-review/pr-192958/nixpkgs/lib/lists.nix:117:32:

          116|   */
          117|   imap1 = f: list: genList (n: f (n + 1) (elemAt list n)) (length list);
             |                                ^
          118|

       … while evaluating anonymous lambda

       at /home/skainswo/.cache/nixpkgs-review/pr-192958/nixpkgs/lib/lists.nix:117:29:

          116|   */
          117|   imap1 = f: list: genList (n: f (n + 1) (elemAt list n)) (length list);
             |                             ^
          118|

       … from call site

       … while evaluating anonymous lambda

       at /home/skainswo/.cache/nixpkgs-review/pr-192958/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:221:13:

          220|       (map (drv: drv.__spliced.hostHost or drv) (checkDependencyList "depsHostHost" depsHostHost))
          221|       (map (drv: drv.crossDrv or drv) (checkDependencyList "buildInputs" buildInputs))
             |             ^
          222|     ]

       … from call site

       … while evaluating 'getOutput'

       at /home/skainswo/.cache/nixpkgs-review/pr-192958/nixpkgs/lib/attrsets.nix:598:23:

          597|   */
          598|   getOutput = output: pkg:
             |                       ^
          599|     if ! pkg ? outputSpecified || ! pkg.outputSpecified

       … from call site

       … while evaluating the attribute 'buildInputs' of the derivation 'caffe-1.0'

       at /home/skainswo/.cache/nixpkgs-review/pr-192958/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:270:7:

          269|     // (lib.optionalAttrs (attrs ? name || (attrs ? pname && attrs ? version)) {
          270|       name =
             |       ^
          271|         let

       … while querying the derivation named 'caffe-1.0'
https://github.com/NixOS/nixpkgs/pull/192958 failed to build
$ git worktree prune

Is there a nix mechanism to raise a warning to the user when we are unable to find a compatible version?

As far as I know, you can only do that for errors.  I hope I'm wrong.

I also got that error from nixpkgs-review, and it looks like ofborg has thrown up the same error.  It looks like it's happening when building the package caffe, but when I run,
NIXPKGS_ALLOW_UNFREE=1 nix-build -A caffe

From my nixpkgs checkout, it builds just fine.  How do we find out what nix expression is being evaluated that hits this error?

I still don't know why caffe builds without error for me, but from looking over the trace a bit more, I can see that it's specifically cudaPackages_10_1.cudnn that is broken with these changes.
❯ NIXPKGS_ALLOW_UNFREE=1 nix repl .
Welcome to Nix 2.8.1. Type :? for help.

Loading '.'...
Added 17005 variables.

nix-repl> :b cudaPackages_10_1.cudnn
error: attribute 'cudnn_8_3_2' missing

       at /home/aidan/src/nixpkgs/pkgs/development/libraries/science/math/cudnn/extension.nix:30:32:

           29|     # Set the default attributes, e.g. cudnn = cudnn_8_3_1;
           30|     defaultBuild = { "cudnn" = allBuilds.${computeName cuDnnDefaultVersion}; };
             |                                ^
           31|   in allBuilds // defaultBuild;

It turns out that the ? operator does not do what I thought it does, so the expression defaultVersions ? cudaVersion is checking whether defaultVersions has cudaVersion as an attribute, instead of using the value of cudaVersion.  I should have been using builtins.hasAttr.

a.attr or 1 defaults to 1 if attr doesn't exist, probably wanted that?

Thanks!  I didn't even think to try that because I thought a.attr when attr does not exist was always an error, no matter what operator you put after that.

Thanks! I didn't even think to try that because I thought a.attr when attr does not exist was always an error, no matter what operator you put after that.

Huh, yeah I expected the same. Seems though if a sub-expression errors, any parent expression ought to error as well... TIL!

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

Ok, well Nothing to be built. as far as nixpkgs-review is concerned. I'm guessing this is bc I have CAS enabled. So everything builds fine for me.
Only remaining issue is if we can get a warning when the version is not found. Does anyone know if such a thing is possible in Nix?

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

Only remaining issue is if we can get a warning when the version is not found. Does anyone know if such a thing is possible in Nix?

I think the meta.broken predicate serves the same purpose.  If a user tries to build any version of cudnn against an unsupported CUDA version, they will get the "this package is marked as broken" error, along with instructions on how to proceed anyway.  This could be made clearer if there was some kind of "reason" field to go along with the meta.broken attribute, instead of requiring the user to find the derivation's source file in nixpkgs and hope there is a comment there.

Ah yeah, that's a fair point. I think as long as they're marked as meta.broken then we're all good.


Adding hideMode to Tabs

Defaulting to unmounted - not mounting inactive tabs. display mode will mount inactive tabs but keep them hidden.
Closes #709

This is my first PR to this project. This will address #709. Please let me know if you want me to adjust anything.
I wasn't sure about how to update the docs for the Tabs so I manually added the new prop to the Tabs' readme. If you think it's worth an example I can include that.
Thanks!

Great!! I love when you guys contribute with tests, it's something we need to do with the lib. Great work, thank you!


Move resource template generator out of endpoints

Currently, generateResourceMessage is hosted in endpoints/slash/resources/resources.js - this should be moved under the /data/ folder to better be in line with the templates being separate from the commands.

Holding until #42 gets merged, to avoid further clashes.