Repace pkg_resources with importlib.metadata

I think this is the only change needed to get rid of the dependence on pkg_resources. However, I can't really fully test this because I am not a user of this library. I hope it works!

Thanks for this contribution!
I've tested it and it works.
I also made the according changes in another project: https://github.com/Octoframes/jupyter_capture_output


Kinetic Augment can't shear sheep

It seems that kinetic augments cannot shear sheep, this means that it is impossible to automate sheep shearing, as shears are not a valid turtle upgrade.

You should be able to call turtle.place with the shears. We even have a test for it!
That said, this probably still is a bug - I'd definitely expect it to work!

this might be another case where the raytrace in kinetic augments is failing

I do recommend calling turtle.place with the shears in the future!


[module] Raymath Version

I donwloaded Raylib v4.0 from the red "Download Now" button on the start page of the "https://www.raylib.com/" website (the raylib_installer_v4.0.mingw.exe self extract executable) and I downloaded raylib from the GitHub repository (as a ZIP file) and I noticed a problem, both are supposed to be the 4.0 version however the "raymath.h" file that comes with the executable defines the function vector2angle as
RMAPI float Vector2Angle(Vector2 v1, Vector2 v2){
float result = atan2f(v2.y - v1.y, v2.x - v1.x)*(180.0f/PI);
if (result < 0) result += 360.0f;
return result;
}
which is wrong and the "raymath.h" file in the repository defines as
RMAPI float Vector2Angle(Vector2 v1, Vector2 v2){
float result = atan2f(v2.y, v2.x) - atan2f(v1.y, v1.x);
return result;
}
Both files, in their headers, say that this is raymath version 1.5. What's going on?

Well, the master branch on the repository is actually raylib 4.0-bis, and I guess that means raymath is 1.5-bis there because it is all under active development.
There should probably be some sort of management of version numbers to signify when something is under development and then when its version becomes a new stable.
But mainly, master is always under development.
I don't have a meaningful suggestion on how to distinguish that from a stable version corresponding to a release unless it would be to make a release branch.  That still leaves some murk around versions of individual components, such as raymath.h.

@leowribeiro raylib current master branch is raylib 4.1-dev. raymath.h was updated recently but not the version number, it will be updated in next release.


Basic profile page of contact

[ ] Make a profile page of the contact that only shows the posts of that contact.
[ ] Go to that page via whisper (extra option with right click on chat).
[ ] Go to that page via the contact dialog that shows up when you hover over a Post avatar in dashboard.

see https://github.com/threefoldtech/twin_aydo/issues/731#issuecomment-1238042616
for design


Support ProblemDetail

Spring is supporting new way to expose errors using ProblemDetail. Please support in the starter

I had a look and I could write a custom serializer that uses ProblemDetail, but I am having trouble knowing how to map. By default, this library uses code and message like this:
{
  "code": "USER_NOT_FOUND",
  "message": "Could not find user with id 123"
}

The code seems to be lacking in the specification. The closest seems to be type, but that expects an URI which is not something we have available.
How do you envision this working?

One idea might be to have the user configure a base URI for all error types. For example:
error.handling.rfc7807.base-uri=https://api.myservice.com/errors

Then the example could become:
{
    "type": "https://api.myservice.com/errors/user-not-found",
    "title": "Could not find user with id 123"
}

Note how we could use lower-snake-case to have the generated URI look nice.

Another example:
{
  "code": "VALIDATION_FAILED",
  "message": "Validation failed for object='exampleRequestBody'. Error count: 2",
  "fieldErrors": [
    {
      "code": "INVALID_SIZE",
      "property": "name",
      "message": "size must be between 10 and<PHONE_NUMBER>",
      "rejectedValue": "",
      "path": "name"
    },
    {
      "code": "REQUIRED_NOT_BLANK",
      "property": "favoriteMovie",
      "message": "must not be blank",
      "rejectedValue": null,
      "path": "favoriteMovie"
    }
  ]
}

Would become:
{
    "type": "https://api.myservice.com/errors/validation-failed",
    "title": "Validation failed for object='exampleRequestBody'. Error count: 2",
    "fieldErrors": [
    {
      "code": "INVALID_SIZE",
      "property": "name",
      "message": "size must be between 10 and<PHONE_NUMBER>",
      "rejectedValue": "",
      "path": "name"
    },
    {
      "code": "REQUIRED_NOT_BLANK",
      "property": "favoriteMovie",
      "message": "must not be blank",
      "rejectedValue": null,
      "path": "favoriteMovie"
    }
  ]
}

"code": "USER_NOT_FOUND",

We can achieve the same using problemDetail.setProperty("code", "USER_NOT_FOUND")  so migration will be easier as we are retaining earlier key name

The specification states:

Consumers MUST use the "type" string as the primary identifier for the problem type

So type is what code has always been for this library. A machine-readable string for consumers of the API to know the problem type.
I don't see any advantage of supporting ProblemDetail if we don't adhere to the specification.

It seems like type is an optional field?

When this member is not present, its value is assumed to be about:blank".

And it also states

The "about:blank" URI [RFC6694], when used as a problem type,
indicates that the problem has no additional semantics beyond that of
the HTTP status code.

When "about:blank" is used, the title SHOULD be the same as the
recommended HTTP status phrase for that code (e.g., "Not Found" for
404, and so on), although it MAY be localized to suit client
preferences (expressed with the Accept-Language request header).

Would that then be
{
    "title": "BAD_REQUEST",
    "fieldErrors": [
    {
      "code": "INVALID_SIZE",
      "property": "name",
      "message": "size must be between 10 and<PHONE_NUMBER>",
      "rejectedValue": "",
      "path": "name"
    },
    {
      "code": "REQUIRED_NOT_BLANK",
      "property": "favoriteMovie",
      "message": "must not be blank",
      "rejectedValue": null,
      "path": "favoriteMovie"
    }
  ]
}

For reference, or for people how need problem support now, there is another library: https://github.com/zalando/problem-spring-web which configures https://github.com/zalando/problem for Spring Boot.
Yes, the type is optional. When absent or "about:blank", it doesn't say anything about the shape of the problem JSON, and "indicates that the problem has no additional semantics beyond that of the HTTP status code." so that means that the JSON should just look something like
{
  "title": "Not Found",
  "status": 404
}

In practice, it still works fine when additional fields are provided, like
{
  "title": "Not Found",
  "status": 404,
  "detail": "Enity foo id=1 not found"
}

IMO, the closest thing to your code is the problem title,

"title" (string) - A short, human-readable summary of the problem
type.  It SHOULD NOT change from occurrence to occurrence of the
problem, except for purposes of localization ...

When the type is present, it should be a URI that defines and explains the shape of the problem JSON. For example, the Zalando library uses this URL https://opensource.zalando.com/problem/constraint-violation/ as type for constraint violations.
Tl;dr: to support the problem RFC, this library could

use title instead of code
use detail instead of message
simply omit the type, or define types to describe the default and the validation error response shapes, or leave it up to the user to define a type with an annotation. I guess the latter would already be possible with @ResponseErrorProperty.

Tl;dr: to support the problem RFC, this library could

use title instead of code
use detail instead of message

The problem spec requires title to contain "a short, human-readable summary of the problem type". Given that the code property is intended to be read by a machine, we should map message to title, rather than code

Another example:
{
  "code": "VALIDATION_FAILED",
  "message": "Validation failed for object='exampleRequestBody'. Error count: 2",
  "fieldErrors": [
    {
      "code": "INVALID_SIZE",
      "property": "name",
      "message": "size must be between 10 and<PHONE_NUMBER>",
      "rejectedValue": "",
      "path": "name"
    },
    {
      "code": "REQUIRED_NOT_BLANK",
      "property": "favoriteMovie",
      "message": "must not be blank",
      "rejectedValue": null,
      "path": "favoriteMovie"
    }
  ]
}

Would become:
{
    "type": "https://api.myservice.com/errors/validation-failed",
    "title": "Validation failed for object='exampleRequestBody'. Error count: 2",
    "fieldErrors": [
    {
      "code": "INVALID_SIZE",
      "property": "name",
      "message": "size must be between 10 and<PHONE_NUMBER>",
      "rejectedValue": "",
      "path": "name"
    },
    {
      "code": "REQUIRED_NOT_BLANK",
      "property": "favoriteMovie",
      "message": "must not be blank",
      "rejectedValue": null,
      "path": "favoriteMovie"
    }
  ]
}

In my opinion, this is a reasonable way to implement the RFC. I think you would also need to return application/problem+json for the Content-Type response header instead of application/json.
It's not necessary to return a full URI for the type property, a relative URI is acceptable, e.g.
"type": "validation-failed"

However, the spec recommends including the full path for relative URIs, so the following would be preferable
"type": "/problems/validation-failed"

It ought to be possible to change the default base path "/problems" via configuration.


Wrong value in defaults/main.yml file for ubtu22cis_grub_file variable

Describe the Issue
In my opinion, after analyzing why CIS reports a failure for rule  1.4.2 Ensure permissions on bootloader config are configured, the current value set in defaults/main.yml file for variable ubtu22cis_grub_file  is wrong.
I think it may ended up with this value, as this is a mix between:
- DEFAULT FILE: /etc/default/grub
- THE AUTO-GENERATED GRUB FILE: /boot/grub/grub.cfg
Expected Behavior
ubtu22cis_grub_file: /etc/grub/grub.cfg -> CIS reports rule 1.4.2 as passed
Actual Behavior
ubtu22cis_grub_file: /etc/default/grub.cfg -> CIS reports rule 1.4.2 as failed
Control(s) Affected
1.4.2
Environment (please complete the following information):

branch being used: devel

Possible Solution
I'll add a PR.

hi @ipruteanu-sie
This issue was merged to devel a couple of weeks ago.
I will close this Issue, if this does not resolve your issue please reopen.
Many thanks as always
uk-bolly


New-DLPPolicy not working

What is the expected value for EnvironmentType in New-DLPPolicy command?
It is a mandatory property and examples doesn't show anything, please let me know.
Thanks,
Dhawal Mehta

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

ID: 02f1be79-2b3a-31da-7a7d-ace1eac5d1f1
Version Independent ID: fa7c7450-15a6-edc8-5671-f45763267ca6
Content: PowerShell support - Power Platform
Content Source: power-platform/admin/powerapps-powershell.md
Service: power-platform
GitHub Login: @jimholtz
Microsoft Alias: jimholtz

@dhawal16
We have 4 predefined EnvironmentType.
public enum DLPPolicyEnvironmentType
{
    /// <summary>
    ///  Data Loss Prevention Policy Environment Type is not specified
    /// </summary>
    NotSpecified,

    /// <summary>
    ///  Data Loss Prevention Policy Environment Type is set to apply to all environments
    /// </summary>
    AllEnvironments,

    /// <summary>
    ///  Data Loss Prevention Policy Environment Type is set to apply to only specific environments
    /// </summary>
    OnlyEnvironments,

    /// <summary>
    ///  Data Loss Prevention Policy Environment Type is set to exclude specific environments
    /// </summary>
    ExceptEnvironments,

    /// <summary>
    ///  Data Loss Prevention Policy Environment Type is set to a single specific environment
    /// </summary>
    SingleEnvironment
}


Add --test-tool=nextest

Fixes #85

[x] Update manual
[x] Exercise from cargo-mutants' own CI
[x] Integration test
[ ] Build with cargo test --no-run and nextest run --no-run
[ ] Look at nextest exit codes and report if the test one is not "tests failed"

Performance on cargo-mutants
I tested this on cargo-mutants itself locally and in CI, and it works well. However, interestingly, it does currently seem to be significantly slower in sharded full-tree tests than is cargo test (about 8m vs >13m). (Example CI run.)
It's also somewhat slower, although not as much, locally:
; c r --release mutants --shard 1/10 --test-tool=nextest
   Compiling cargo-mutants v23.12.2 (/home/mbp/src/mutants)
    Finished release [optimized] target(s) in 4.49s
     Running `target/release/cargo-mutants mutants --shard 1/10 --test-tool=nextest`
Found 56 mutants to test
ok       Unmutated baseline in 13.9s build + 22.3s test
Auto-set test timeout to 1m 51s
56 mutants tested in 4m 22s: 40 caught, 16 unviable

; c r --release mutants --shard 1/10
    Finished release [optimized] target(s) in 0.08s
     Running `target/release/cargo-mutants mutants --shard 1/10`
Found 56 mutants to test
ok       Unmutated baseline in 13.8s build + 21.7s test
Auto-set test timeout to 1m 48s
56 mutants tested in 3m 46s: 40 caught, 16 unviable

Although it's probably better at stopping early, it may be paying a higher per-test overhead or maybe making less use of parallelism?
Performance on stackslib
I also tested this on a 1% sample of stackslib with
; c r --release mutants --shard 1/100 -d ~/src/stacks-core/ --test-tool nextest
    Finished release [optimized] target(s) in 0.18s
     Running `target/release/cargo-mutants mutants --shard 1/100 -d /home/mbp/src/stacks-core/ --test-tool nextest`
Found 112 mutants to test
ok       Unmutated baseline in 116.1s build + 244.5s test
Auto-set test timeout to 20m 22s
MISSED   src/burnchains/bitcoin/spv.rs:1150:55: replace > with == in SpvClient::get_target in 34.1s build + 256.1s test
MISSED   src/chainstate/burn/db/sortdb.rs:2893:25: replace == with != in SortitionDB::is_db_version_supported_in_epoch in 25.8s build + 283.8s test
3358.435171577s  INFO timeout after 1222.4s, terminating child process...
TIMEOUT  src/net/connection.rs:1334:9: replace NetworkConnection<P>::send_data -> Result<usize, net_error> with Ok(1) in 34.8s build + 1222.4s test
MISSED   src/chainstate/coordinator/comm.rs:105:9: replace SignalBools::receive_signal -> u8 with 0 in 38.0s build + 278.8s test
MISSED   src/main.rs:957:16: replace == with != in main in 24.3s build + 258.5s test
MISSED   src/net/p2p.rs:4235:9: replace PeerNetwork::need_block_or_microblock_stream -> Result<bool, net_error> with Ok(true) in 28.7s build + 267.8s test
MISSED   src/net/p2p.rs:1280:9: replace PeerNetwork::num_peers -> usize with 1 in 26.8s build + 311.8s test
test     src/clarity_vm/database/mod.rs:174:9: replace <impl HeadersDB for ChainstateTx<'a>>::get_burnchain_tokens_spent_for_block -> Option<u128> with Some(1) ... 233.0s
MISSED   src/net/http.rs:1730:9: replace HttpRequestType::get_proof_query -> bool with true in 33.5s build + 291.0s test
MISSED   src/util_lib/db.rs:656:20: replace > with == in tx_busy_handler in 35.5s build + 290.3s test
test     src/chainstate/stacks/db/unconfirmed.rs:443:9: replace UnconfirmedState::num_mined_txs -> usize with 0 s
└                PASS [  28.317s]                     blockstack-core clarity_vm::tests::costs::epoch_21_test_alt
47/112 mutants tested, 8 MISSED, 1 timeout, 24 caught, 14 unviable, 1h 49m 40s elapsed, about 2h 32m remaining

It looks like some of those tests are still pretty slow, but it is making progress.

Performance on stackslib
I also tested this on a 1% sample of stackslib with
; c r --release mutants --shard 1/100 -d ~/src/stacks-core/ --test-tool nextest

Hey @sourcefrog , thanks for updating cargo mutants with nextest!
In the above example, the mutants that you specified are run from the whole stacks-core workspace, not specifically from stackslib.
I've tested it on stackslib with mutants that are caught and the difference is truly significant ( excepting unmutated build and test, from 1 hour and 10 minutes to 6 minutes).
cargo test
; command containing the regex of the 4 mutants tested
; test-threads=1 and bitcoind_test=1 are required for stackslib in order to work properly with bitcoin
; BITCOIND_TEST=1 RUST_BACKTRACE=full cargo mutants -F "(stackslib/src/chainstate/nakamoto/mod.rs:2595:9: replace NakamotoChainState::set_aggregate_public_key with \(\))|(stackslib/src/chainstate/nakamoto/mod.rs:3059:9: replace NakamotoChainState::aggregate_public_key_bootcode with \(\))|(stackslib/src/net/relay.rs:661:9: replace Relayer::process_new_nakamoto_block -> Result<bool, chainstate_error> with Ok\(true\))|(stackslib/src/net/relay.rs:661:9: replace Relayer::process_new_nakamoto_block -> Result<bool, chainstate_error> with Ok\(false\))" -- --all-targets -- --test-threads 1

Found 4 mutants to test
ok       Unmutated baseline in 131.2s build + 1052.1s test
Auto-set test timeout to 1h 27m 40s
4 mutants tested in 1h 31m 41s: 4 caught

cargo nextest
; BITCOIND_TEST=1 RUST_BACKTRACE=full cargo mutants -F "(stackslib/src/chainstate/nakamoto/mod.rs:2595:9: replace NakamotoChainState::set_aggregate_public_key with \(\))|(stackslib/src/chainstate/nakamoto/mod.rs:3059:9: replace NakamotoChainState::aggregate_public_key_bootcode with \(\))|(stackslib/src/net/relay.rs:661:9: replace Relayer::process_new_nakamoto_block -> Result<bool, chainstate_error> with Ok\(true\))|(stackslib/src/net/relay.rs:661:9: replace Relayer::process_new_nakamoto_block -> Result<bool, chainstate_error> with Ok\(false\))" --test-tool=nextest -- --fail-fast --test-threads 1

Found 4 mutants to test
ok       Unmutated baseline in 130.8s build + 1054.7s test
Auto-set test timeout to 1h 27m 53s
4 mutants tested in 25m 22s: 4 caught

The baseline tests ran in ~20 minutes, meaning it took less than 6 minutes to run the mutants with nextest's fail-fast flag enabled, compared to cargo test's 1h 10m.
Documentation related as well, the -- --test-threads arg from cargo test does not apply to cargo nextest, which doesn't require the additional --, leaving it just as --test-threads.

Wow that's incredible @ASuciuX!

That's outstanding, thanks for letting us know!
I will do the couple of small items in the head of the PR including checking the docs about passing options to cargo test/nextest, and then push a release.
I don't think you need to set --fail-fast explicitly for nextest as that's the default.
Regarding test-threads, from previous conversations I think you are setting this because you have some non-hermetic tests that cannot be run in parallel. nextest actually has some nice specific features for this which once set up properly might give you more precise control.

You are right @sourcefrog , I've tried without --fail-fast and I had the same results.
Interesting features, thank you for sharing, I will take a look into those.


Critical: luajit can't pass nil as sol::object argument

Repro

sol::state lua;

lua["test1"] = [](sol::object) { std::cout << "ok1" << std::endl; };
lua["test2"] = [](sol::object, sol::object) { std::cout << "ok2" << std::endl; };
lua.script("test1(nil)", [](lua_State*, sol::protected_function_result pfr) {
    sol::error err = pfr;
    std::cout << err.what() << std::endl;
    return pfr;
});
lua.script("test2(nil, nil)", [](lua_State*, sol::protected_function_result pfr) {
    sol::error err = pfr;
    std::cout << err.what() << std::endl;
    return pfr;
});

Both scripts gives the following error:

stack index 1, expected anything, received nil:
stack traceback:
        [C]: in function 'test1'
        [string "test1(nil)"]:1: in main chunk
stack index 1, expected anything, received nil:
stack traceback:
        [C]: in function 'test2'
        [string "test2(nil, nil)"]:1: in main chunk

Compiler/IDE: Visual Studio
Language: C++
sol2 version: latest

I am facing a bug related to this one.
@ThePhD Am I missing something here? Because this fundamental kind of bugs are scary.
Thanks.

This is fixed in the latest commit, https://github.com/ThePhD/sol2/commit/ff3f254f7b47cfc8cf2976368d86f4cd726915ec

@ThePhD Hi,
I pulled the repo to the latest, still getting the same issue: stack index 1, expected anything, received nil.
Thanks, I appreciate your efforts for bringing this nice library.

@ThePhD Hi,
I pulled the repo to the latest, still getting the same issue: stack index 1, expected anything, received nil.
Thanks, I appreciate your efforts for bringing this nice library.

@deadlocklogic
did you try this fix?

Apparently I was linking against the vcpkg library instead of the main repo.
Indeed the issue is fixed.
Apologies.

@deadlocklogic
did you try https://github.com/ThePhD/sol2/issues/1344#issuecomment-1624548126 fix?

This fix is peculiar since it silences critical sections.


Match up with the latest torch version

Is your feature request related to a problem? Please describe.
Currently, it supports torch==1.8.1.  Due to some compatibility issue, I couldn't use this library locally conveniently with the other latest versions locally. So, I think it would be better to support torch>=1.8.1
https://github.com/openvinotoolkit/anomalib/blob/development/requirements/base.txt

@innat, we haven't fully tested the repo with >1.8.1, which is why we have it like this at the moment. We do want to support >1.8.1, for sure, which will be quite shortly.

@samet-akcay, I believe this has already been merge in #158


identify: Fix some issues with updateSelf.

Rebased onto the latest master to include the fixes made there

Going to merge this one and figure it out while we factor swarm. Going to separate the transports and the dialers with clear interfaces so we can add more than tcp


cmake31 does not install

Console output:
$ brew install cmake31 qt5 sdl2 dylibbundler
==> Installing cmake31 from homebrew/versions
Error: No available formula with the name "cmake28"

Issue introduced due to #1274.

Likely due to line 40 of cmake31.rb.


update README.md

Hi,
When activating a newly created environment on Anaconda,  $ source activate <env_name> doesn't seem to work (on Windows at least). Instead, Anaconda prompt suggests using $ conda activate <env_name>.
Here's what I found on StackOverflow: https://stackoverflow.com/questions/49600611/python-anaconda-should-i-use-conda-activate-or-source-activate-in-linux. Maybe need to update Readme.md?
Thanks a lot for the great work!

Thanks for your feedback. Indeed, conda activate seems to be the recommended way to go since Anaconda 4.4.


Attempt to paste file into chat results in ERROR CODE 1504

I tried to paste a file (happened to be a shell script if that matters) into a several keybase chats (at different times) and an error popup that said "ERROR CDOE 1504 - RPC Error: STREAM_EOF in method chat.1.local.makePreview at o.t"
Full error message attached

I encountered exactly the same error as mentioned above whenever I tried to add an empty file. Adding any non empty file (text and binary, various formats) worked.
(Actually, another error (ERROR CODE 218) occurred when tried to add a file for which I had no permissions. This obviously can't work, but I expected a nicer error message. But I assume this is not directly related anyway, except if there is a bug in the general way such errors are handled.)
Version:
Client:  1.0.47-20180330162235+ea57e4c687
Service: 1.0.47-20180330162235+ea57e4c687
Environment:
4.4.0-116-generic x86_64 GNU/Linux
Error:
ERROR CODE 1504 - RPC Error: STREAM_EOF in method chat.1.local.makePreview STREAM_EOF: ERROR CODE 1504 - RPC Error: STREAM_EOF in method chat.1.local.makePreview at o.t (file:///opt/keybase/resources/app/desktop/dist/index.bundle.js:1:392692) at o (file:///opt/keybase/resources/app/desktop/dist/index.bundle.js:1:392998) at a (file:///opt/keybase/resources/app/desktop/dist/index.bundle.js:1:392360) at t.convertToError (file:///opt/keybase/resources/app/desktop/dist/index.bundle.js:1:392558) at _rpcClient.invoke.t (file:///opt/keybase/resources/app/desktop/dist/index.bundle.js:1:349717) at file:///opt/keybase/resources/app/desktop/dist/index.bundle.js:1:1012976 at e.t.Deferrals.e._call (file:///opt/keybase/resources/app/desktop/dist/index.bundle.js:1:663738) at file:///opt/keybase/resources/app/desktop/dist/index.bundle.js:1:663889 at s (file:///opt/keybase/resources/app/desktop/dist/index.bundle.js:1:663518) at e.t.Deferrals.e._fulfill (file:///opt/keybase/resources/app/desktop/dist/index.bundle.js:1:663848)


Upgrade go.mod package versions

Fixes #RHOAIENG-10033
Implemented fixes on my fork and imported in my personal snyk account and made sure CVEs are eliminated.

@VaniHaripriya - can you append the UPSTREAM: <carry>: prefix in your commit message?  Otherwise LGTM

Closing this PR and opened a new one for the same.


Scrollbar issue with Bookmarklet under Firefox

See: https://github.com/shaarli/Shaarli/issues/1079
The only theme I could have gotten a different from the default bookmarklet would have been this one.
Thanks for looking into it!

Indeed some window features are missing. I'll fix that. In the meantime, as mentioned in the ticket you reference, you can quickly switch to default theme, add the bookmarklet from there and then switch back to Material theme.

Fixed by https://github.com/kalvn/Shaarli-Material/commit/773da1e65aea595c4a3961a74d687393d8745b16


Add Polycom People + Content IP.app v1.0.1

Updated as requested.

Thank you. Could you please squash your commits?

Apparently not. I think I'll close this and re-open a new pull request.


Fix glob for markdown lint and remaining issues

Looks like quotes make a big difference for globbing to work properly with the tool. Good catch. Doesn't seem like markdownlint-cli2-fix can actually fix these. Did you have to fix manually?

Had to fix manually. Seems like bash interprets **/*.md for you – but not me on zsh. 🤷


It is ALIVE! first draft of the R package and it works (sort of)

Hello @dsrivast , @kinwa91, @adletaw, and @lmguzman ,
Well, i've knocked together and R package that can read data directly from Jonathan's API, right into R.
Right now it does only one thing: get the species list:
bwg_auth("yourname", "yourpassword")
# note that this creates and object called "token"
bwg_get("species")

I would love to request a code review if anyone has the time or inclination to do that. Here are some points that I have quite a lot of doubt about:

is the name silly?
do the function names make any sense?
How hazardous is it to use <<- and create the token in the global environment? I'll leave line notes to show what I mean. That seems risky but I couldn't say exactly why. Perhaps we should save it via digest?

Questions for @kinwa91

I get the following warning in response to both GET and POST:  No encoding supplied: defaulting to UTF-8.. Is that problem on my end, or do you need to declare your character encoding in HTTP responses?

Thanks for your input :smile:
Andrew

BTW you can install this package yourself via
devtools::install_github("srivastavalab/bwgdbr#1")
or by cloning the repo and switching to the authenticate branch

This looks awesome!!!! Great job Andrew.  I will try it out!
On 02/01/2016 04:33 PM, Andrew MacDonald wrote:

Hello @dsrivast https://github.com/dsrivast , @kinwa91
https://github.com/kinwa91, @adletaw https://github.com/adletaw,
and @lmguzman https://github.com/lmguzman ,
Well, i've knocked together and R package that can read data directly
from Jonathan's API, right into R.
Right now it does only one thing: get the species list:
bwg_auth("yourname","yourpassword")
note that this creates and object called "token"
bwg_get("species")
I would love to request a code review if anyone has the time or
inclination to do that. Here are some points that I have quite a lot
of doubt about:

is the name silly?
do the function names make any sense?
How hazardous is it to use |<<-| and create the token in the
global environment? I'll leave line notes to show what I mean.
That seems risky but I couldn't say exactly why. Perhaps we should
save it via |digest|?

Questions for @kinwa91 https://github.com/kinwa91

I get the following warning in response to both |GET| and |POST|:
|No encoding supplied: defaulting to UTF-8.|. Is that problem on
my end, or do you need to declare your character encoding in HTTP
responses?

Thanks for your input :smile:
Andrew

    You can view, comment on, or merge this pull request online at:

https://github.com/SrivastavaLab/bwgdbR/pull/1
    Commit Summary

function to get the authorization token from the database server

download species table.

no examples

description and help pages

parse response correctly :blush:
File Changes

M DESCRIPTION
https://github.com/SrivastavaLab/bwgdbR/pull/1/files#diff-0 (5)

M NAMESPACE
https://github.com/SrivastavaLab/bwgdbR/pull/1/files#diff-1 (6)

A R/authenticate.R
https://github.com/SrivastavaLab/bwgdbR/pull/1/files#diff-2 (36)

A R/species.R
https://github.com/SrivastavaLab/bwgdbR/pull/1/files#diff-3 (48)

A man/bwg_auth.Rd
https://github.com/SrivastavaLab/bwgdbR/pull/1/files#diff-4 (21)

A man/bwg_get.Rd
https://github.com/SrivastavaLab/bwgdbR/pull/1/files#diff-5 (20)
Patch Links:

https://github.com/SrivastavaLab/bwgdbR/pull/1.patch

https://github.com/SrivastavaLab/bwgdbR/pull/1.diff

—
Reply to this email directly or view it on GitHub
https://github.com/SrivastavaLab/bwgdbR/pull/1.

--
Alathea D. L.
PhD Candidate, Srivastava Lab
www.zoology.ubc.ca/~srivast

Great to hear the API is working out! I have identify the encoding issue and will push a fix soon!

On Feb 1, 2016, at 5:44 PM, A.D. Letaw<EMAIL_ADDRESS>wrote:
This looks awesome!!!! Great job Andrew. I will try it out!
On 02/01/2016 04:33 PM, Andrew MacDonald wrote:

Hello @dsrivast https://github.com/dsrivast , @kinwa91
https://github.com/kinwa91, @adletaw https://github.com/adletaw,
and @lmguzman https://github.com/lmguzman ,
Well, i've knocked together and R package that can read data directly
from Jonathan's API, right into R.
Right now it does only one thing: get the species list:
bwg_auth("yourname","yourpassword")
note that this creates and object called "token"
bwg_get("species")
I would love to request a code review if anyone has the time or
inclination to do that. Here are some points that I have quite a lot
of doubt about:

is the name silly?
do the function names make any sense?
How hazardous is it to use |<<-| and create the token in the
global environment? I'll leave line notes to show what I mean.
That seems risky but I couldn't say exactly why. Perhaps we should
save it via |digest|?

Questions for @kinwa91 https://github.com/kinwa91

I get the following warning in response to both |GET| and |POST|:
|No encoding supplied: defaulting to UTF-8.|. Is that problem on
my end, or do you need to declare your character encoding in HTTP
responses?

Thanks for your input :smile:
Andrew

You can view, comment on, or merge this pull request online at:
https://github.com/SrivastavaLab/bwgdbR/pull/1
Commit Summary

function to get the authorization token from the database server
download species table.
no examples
description and help pages
parse response correctly :blush:

File Changes

M DESCRIPTION
https://github.com/SrivastavaLab/bwgdbR/pull/1/files#diff-0 (5)
M NAMESPACE
https://github.com/SrivastavaLab/bwgdbR/pull/1/files#diff-1 (6)
A R/authenticate.R
https://github.com/SrivastavaLab/bwgdbR/pull/1/files#diff-2 (36)
A R/species.R
https://github.com/SrivastavaLab/bwgdbR/pull/1/files#diff-3 (48)
A man/bwg_auth.Rd
https://github.com/SrivastavaLab/bwgdbR/pull/1/files#diff-4 (21)
A man/bwg_get.Rd
https://github.com/SrivastavaLab/bwgdbR/pull/1/files#diff-5 (20)

Patch Links:

https://github.com/SrivastavaLab/bwgdbR/pull/1.patch
https://github.com/SrivastavaLab/bwgdbR/pull/1.diff

—
Reply to this email directly or view it on GitHub
https://github.com/SrivastavaLab/bwgdbR/pull/1.

--
Alathea D. L.
PhD Candidate, Srivastava Lab
www.zoology.ubc.ca/~srivast
—
Reply to this email directly or view it on GitHub.

A more intuitive name for bwg_auth() might be connect().  Then you get the idea that you have to first connect() to the database, then do stuff.  It is not exactly what is actually happening, but I think it makes it easier to remember what to do.

The main issue with <<- is that you could overwrite something without realizing it.  You have skirted that issue by forcing the function to stop if token is found.  You might use assign instead of <<- just to make it really clear where the variable is being saved.

One thing that might be cool is to use connect to move the user into a new environment in which all of the bwgdb editing functions are present.  Then you don't have to worry about overwriting something when you generate the token.  Then you could have a disconnect function wherein you leave this new environment.  This is sort of the premise by which captioner works.

@adletaw , I had a thought this morning when chatting to @lmguzman : what if the bwg_auth() function is called inside of bwg_get()? then the token variable could be set only in the execution environment of bwg_get, and it would disappear when the function was done.
That might have a few advantages. First, it would allow the token to work on multiple GET requests. it would also avoid collision with other things.
Other options I considered -- using the package digest to encrypt and store the token. Or simply obtaining it and discarding it in the same function call (i.e. roll bwg_auth() and bwg_get() into the same function)

Of course, if you are in a new environment, it would be harder to access any objects you had ready in your global environment.  So you might need another function that grabs stuff from the global environment of a given name.  But the reason I like the general idea is that it gives the feeling of being connected into the database and having to interact with it in a particular way, and then being clearly disconnected.  Once you disconnect, the new environment is erased, so the token would be lost.

@kinwa91 it might help to know more about what you meant when you called it a "one-time" or "temporary" API key.

So when you used bwg_get you would have to specify the user name and password?  I think that would be fine too :)

@adletaw that idea about a new environment is very tidy indeed. What if I see your custom environments, and raise you R6 classes :spades: :diamonds:

It would help to think ahead about what you want to be able to do with the R interface to the bwgdb.  Just get stuff, right?  Then I think your method would work pretty great.  There are probably only a few things a person would want to get: dataset, species, bromeliads?

@aammd Then you would be a neRd.

I think the main thing is you don't want to have to type the user name and password into every function call.  That would probably be annoying, :smile:

You could also just explicitly generate the token, i.e. token <- bwg_auth("user", "password") then bwg_get(token, ...)

As for the digest, would that really add any extra security?  I'm trying to wrap my head around that one.

Well, people could set usernames and passwords in environment variables in their .Rprofile. that is a popular solution for other API packages.
Your idea about just generating and storing the token manually is probably simplest. Would we have to make sure people delete it at the end? eg. tell them to end their script with rm(list = ls())

Hmmm... that's kind of why I favor having a connect and disconnect.  Then it forces whatever you want to be deleted.  Probably they shouldn't be able to actually change the database via R.  You had in mind just reading, not writing, right?  As long as they can't write anything, it is not as dangerous if someone leaves their token lying around.  Probably, it is best to delete though.

But disconnect could just be a function that runs rm(list = ls())

In the parent environment of course


Is this repo not mantained anymore?

Some time ago I send this PR that solves some of the major issues with the project, but it hasn't been looked or reviewed since.
You don't have any time to work on this repo? Do you need mantainers?

Hey, thanks for the PRs!  This repo is maintained, I've just been a bit short on time lately. I've invited you to be a collaborator on this repo if you have time to make improvements. Thanks!

Hey thanks man!


netbsd ext attrs api addition

r? @Amanieu
(rust-highfive has picked a reviewer for you, use r? to override)

@bors r+

:pushpin: Commit 6e94888765d0efe1bfd9e9a976bcb42bf5c7eb87 has been approved by Amanieu

:hourglass: Testing commit 6e94888765d0efe1bfd9e9a976bcb42bf5c7eb87 with merge 2af710a6342f07f86c0ae2f4a8619de7343481fe...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13
Approved by: Amanieu
Pushing 2af710a6342f07f86c0ae2f4a8619de7343481fe to master...


Experiment: Produce wide index signatures from the spread of an index signature

Fixes #56431
Related: https://github.com/microsoft/TypeScript/issues/27273 (does not change the behavior of dropping index signatures from the left side of a spread)
This would need a lot more test coverage if it proves viable but wanted to run the top repos first.

@typescript-bot perf test this
@typescript-bot run dt
@typescript-bot user test this
@typescript-bot test top200


LinguisticMetadataID missing in cultures ?

Hello Daniel,
After adding several translations I managed to translate the model in a pbix file. But when I connect Dax studio to this file, there is only one LinguisticMetadataID in the $SYSTEM.TMSCHEMA_CULTURES DMV. Is it normal ? Sorry to disturb you if it is normal.

Tabular Editor does not currently have support for adding/removing/editing Linguistic Metadata (metadata used by Power BI Q&A). Do you need this functionality or is it sufficient to be able to add metadata translations?

Daniel, for the moment, I focus  on translating the visuals. I don't care about the Q&A. May be in the future. You can close the issue or keep it open as a reminder. Thank you!

I will close the issue, as I don't have any plans of adding support for linguistic metadata in the short term. Q&A in Power BI only supports English (and Spanish in preview), so I don't think there's much need for support in Tabular Editor at the moment.


Upgrading from 4.0.1 to 5.11.8. Question about IBuilderAware

I have some legacy code, where unity v4.0.1 is used. I've upgraded it to v5.11.8 (along with other related unity packages).
I noticed that IBuilderAware and BuilderAwareStrategy have been deleted, so I have lots of building errors and I'm not sure how to fix them.
The interface and strategy are used for post initialization. I was searching for any upgrade guidance or something, but I didn't manage to find them.
Could you please advise what I should use instead of IBuilderAware and BuilderAwareStrategy?
What kind of changes should I implement?
Thanks in advance.
Regards, Elena

Did you see this site?

Yes, I did. As I can see neither IBuilderAware nor BuilderAwareStrategy are mentioned in the ChangeLog. So I don't understand completely what I should use instead of them.
Please advise.
Thanks,
Elena

I'll try to provide a sample

@ElenaMakarova
These tests should demonstrate how it could be done. Let me know if you have more questions.


All my accounts have been banned

Hello, I download ~50 pics per day, with 3 accounts. I use my phone's user-id, use Instaloader 4.9.3, don't login at 3AM (only randomly at day), and basically follow all the tips and tricks found in other topics, but finally all my accounts have been totally banned. Instagram knows I am not using my phone, so is there any way to change it? I have no idea what to do anymore.

Nearly same question some hours ago in #1738.


Responsible bodies in support

Context
It's useful to see a list of responsible bodies in the support area of the service, so that:

DfE ops users can see engagement stats around both pilots
There is a jump-off points for further operations on the responsible bodies (e.g. managing users)

Changes proposed in this pull request

Add a list of responsible bodies in the support area, only accessible to DfE staff
Display some basic engagement stats per responsible body

Guidance to review
Is the table layout appropriate?

pros: can be copied directly into Excel for further manipulation
cons: not very compact or scannable

Does the microcopy make sense?
(I intend to add the extra mobile data requests later when the data model has been improved for reporting.)

Looks like a great idea. One thought would be does the additional text in the table make it a pain for users wanting to use this in Excel? i.e 1 user and 2 users signed in instead of plain 1 and 2 ?

Looks like a great idea. One thought would be does the additional text in the table make it a pain for users wanting to use this in Excel? i.e 1 user and 2 users signed in instead of plain 1 and 2 ?

Yep, you're right – I'll do a follow-up PR to properly separate things into a CSV and an HTML representation, and add a big green CSV button.


Change order of CRC high/low bytes

Could you please clarify if the reverse ordering of the checksum bytes is by design?
I needed to change the order to make the library compatible with my modbus slave which expects all words to be sent using hi/low ordering.

Hi! After digging deeper into the standard, it seems like it is my target is using an incorrect implementation of the modbus standard. this pull request may be closed off.


⚠ Bofrost.at has degraded performance

In d3799cf, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 3829 ms

Resolved: Bofrost.at performance has improved in 82fcbe6 after 44 minutes.


Feature Request: Config support for endWithSemicolon

Config support for endWithSemicolon:

'preserve' (don't do anything)
'always' (append semicolon at the end if doesn't exist)
'never' (remove semicolon from the end of the SQL if there is one) -- it sounds unlikely that someone will use this option, so the above two are fine as well.

A duplicate of #233
But glad to hear there's more interest in this feature.
Interestingly SQL standard mandates semicolons at the end of statements, but all implementations (as far as I know) treat them as separators between.
Another related thing is multiple semicolons in a row, like:
SELECT "hello";;;

Some dialects (like Postgres) allow such empty statements, while others (like MySQL, SQLite) give you an error.


When doing espflash→OTA→espflash, (sometimes?) the boot partition is not set

Basic overview, might be wrong:

Flash with a partition table that has ota_0 and ota_1; it presumably flashes to ota_0
Perform an OTA update to a firmware with changed behavior, which will write to ota_1 (the not-in-use partition) and set that as the boot partition
Flash with espflash again, again using a firmware that behaves differently

The result is that the ESP32 continues to behave as if step 3 never happened. I assume that it's always flashing to ota_0 and not setting it as the boot partition, so the ESP simply continues booting from ota_1.
I'm using current git version of espflash and an ESP32-C3. I accidentally made a String that slowly expands infinitely, did an OTA, then tried to fix it repeatedly using USB flashes that did not change the running code. Above is my best guess at what's going wrong.
ESP-IDF's otatool can set the boot partition, according to this doc. Alternatively erasing the otadata partition should also reset to ota_0.
Although I'm not entirely sure the description/repro is right, running otatool.py --port COM3 switch_ota_partition --slot 0 resulted in it running the firmware I was trying to run, so I'm fairly certain that the basic 'flashed firmware not being set to boot' issue is real.
Note that I might be doing something horribly wrong and I previously used the Arduino core to work with ESP32s, not the IDF or Rust.

Partition table
# Name,   Type, SubType, Offset,   Size, Flags
# Note: if you have increased the bootloader size, make sure to update the offsets to avoid overlap
nvs,      data, nvs,     ,        0x6000,
otadata,  data, ota,     ,        0x2000,
phy_init, data, phy,     ,        0x1000,
ota_0,    app,  ota_0,   ,        0x1C0000,
ota_1,    app,  ota_1,   ,        0x1C0000,

First up, it's good to see that I'm not the only one who uses 2 OTA partitions without a factory app :)

Above is my best guess at what's going wrong.

I think your guess is correct and I've seen this behaviour with esp-idf as well. My usual workflow was a simple idf.py flash monitor which absolutely didn't touch otadata, which wasted quite a bit of my time trying to figure out why my newest firmware wasn't running.
I guess in the long run, espflash might support flashing to arbitrary partitions, but for now the simplest solution might be to nuke otadata when the firmware would be written to an ota partition.

Apologies for taking so long to get to this!
I believe you are correct that we are simply not setting the correct OTA partition as the boot partition; this step was not included in esptool.py, which is mostly what this project is based on, so it was missed. I will try to get this resolved soon-ish.


gcc error

Why no \
 --- stderr
  gcc: error：C:ProjGameProjHeatEndtargetdebugbuildheatend-10131cee3e57bea3outresource.rc：No such file or directory

I check the file actually it exists

Could you please provide more details? (Version of Rust, Compiler, Visual Studio, and WinKit)


Update README to include updates to release strategy

To simplify branch management, we're changing the release process to:

Create release branch with bumped version numbers
Create PR to merge to master
Merge to master
Create PR to merge master to stable
Approve/merge PR

this will ensure the master and stable branches stay in sync.

Codecov Report

Merging #221 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #221   +/-   ##
=======================================
  Coverage   82.45%   82.45%
=======================================
  Files          19       19
  Lines         513      513
=======================================
  Hits          423      423
  Misses         90       90

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 2aecef2...652e48e. Read the comment docs.

LGTM


Bug: perfectionist/sort-switch-case breaks code with consecutive ENUM case statements

Describe the bug
perfectionist/sort-switch-case rule incorrectly reformats code using switch on consecutive ENUM cases into code with different behavior.
Code example
enum ApiRestMethodEnum {
  GET = 'GET',
  POST = 'POST',
}

let restMethod: string;
switch (restMethod) {
  case ApiRestMethodEnum.POST:
  case ApiRestMethodEnum.GET:
    console.log("Print me")
    break;
}

gets formatted into the following code:
enum ApiRestMethodEnum {
  GET = 'GET',
  POST = 'POST',
}

let restMethod: string;
switch (restMethod) {
  case ApiRestMethodEnum.GET:
    console.log("Print me")
    break;
  case ApiRestMethodEnum.POST:
}

ESLint version
8.57.0
ESLint Plugin Perfectionist version
3.0.0
Additional comments
Possibly related to #180:

Validations

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

Thank you for your issue!
This problem was solved in d07f5f77cdb54b8eec32269695ab04f31d85a5f7 and released in v3.1.0.


lost keybindings on auto loads

Please describe the bug
whenever we edited conf file it reloads and now any keybindings defined in config file want work so user needs to logout and then it started to work again till next editing and reload.
Steps to reproduce:
Do a, use program b...
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Anything else?
Log:
Please attach a log. (paste it into pastebin and paste here the url) The log can be found in a temp file located in /tmp/hypr/hypr.log.
Coredump:
If Hypr crashed, please attach a coredump. (paste into pastebind and paste here the url)
How to?
Systemd instructions:
coredumpctl
find the last ocurrence of Hypr and note the PID.
coredumpctl info <PID>
will print the coredump.
coredumpctl info <PID> --no-pager | xclip -sel clip
will copy it to the clipboard.

great. Zero logs, zero info, nothing. Doesn't happen to me or anyone else.


Create single place in gradle to specify the version of kotlin to use

https://discuss.kotlinlang.org/t/specifying-the-kotlin-version-in-gradle-multi-project-builds/23838
Adding this to buildSrc/build.gradle.kts:
dependencies {
    implementation("org.jetbrains.kotlin:kotlin-gradle-plugin:1.7.21")
}

gives error:
Build file '/home/snake/dev/github/electionguard-kotlin-multiplatform/egklib/build.gradle.kts' line: 10

Error resolving plugin [id: 'org.jetbrains.kotlin.multiplatform', version: '1.7.21']
> The request for this plugin could not be satisfied because the plugin is already on the classpath with an unknown version, so compatibility cannot be checked.

seems to interfere with the use of dependencyResolutionManagement in settings.gradle.kts

https://discuss.kotlinlang.org/t/specifying-the-kotlin-version-in-gradle-multi-project-builds/23838
create root level build.gradle.kts::
plugins {
    java
    kotlin("jvm") version "1.7.21" apply false
}

gives error:
org.gradle.internal.exceptions.LocationAwareException: Build file '/home/snake/dev/github/electionguard-kotlin-multiplatform/egklib/build.gradle.kts' line: 10
Error resolving plugin [id: 'org.jetbrains.kotlin.multiplatform', version: '1.7.21']
	at org.gradle.plugin.use.internal.DefaultPluginRequestApplicator.resolveToFoundResult(DefaultPluginRequestApplicator.java:233)

	... 185 more
Caused by: org.gradle.plugin.management.internal.InvalidPluginRequestException: The request for this plugin could not be satisfied because the plugin is already on the classpath with an unknown version, so compatibility cannot be checked.
	at org.gradle.plugin.use.resolve.internal.AlreadyOnClasspathPluginResolver.resolve(AlreadyOnClasspathPluginResolver.java:84)
	at org.gradle.plugin.use.internal.DefaultPluginRequestApplicator.resolveToFoundResult(DefaultPluginRequestApplicator.java:229)

Part of the problem may be that is that egklib and hacllib use:
kotlin("multiplatform") version "1.7.21"

but webapps uses
kotlin("jvm") version "1.7.21"

Would be nice to put
val kotlinVersion by extra("1.7.21")
in some common place, then use it like
   kotlin("multiplatform") version kotlinVersion
putting it in buildSrc/build.gradle.kts doesnt work
putting it in build.gradle.kts doesnt work

putting
kotlinVersion=1.7.21
into gradle.properties
and then can use
plugins {
    kotlin("multiplatform") version providers.gradleProperty("kotlinVersion").get()
    ...

but only if theres a
buildscript {
    repositories {
    }
}

above the plugins (ok to be empty), otherwise you get
/home/snake/dev/github/electionguard-kotlin-multiplatform/hacllib/build.gradle.kts:3:37: Unresolved reference: providers
The usual gradle "ya just gotta know" bullshit


Import Glibc in SKDResponse

In https://github.com/apple/sourcekit-lsp/pull/357 we forgot to update SDKReponse.swift. This PR fixes that.
From https://github.com/apple/sourcekit-lsp/pull/357:
These files rely on Glibc declarations in their public interface, even though they don’t import Glibc. Currently, these declarations are discovered through CoreFoundation, but due to implementation details, Swift canonicalizes the declarations and at the end uses declarations from Glibc (which is imported by other files in the module).
This is fragile as Foundation now relies on implementation details of Glibc, which in fact we are trying to change in apple/swift#32404.
This PR fixes the issue by explicitly importing Glibc in affected files.

@swift-ci please test


Performance Appraisal Form with Department List - Performance Appraisal List //  Notification For Per-Appri // Master setting For Employee wise Department wise Expiry Date setting

https://performance-appr.bubbleapps.io/version-test?debug_mode=false

closed


What type of update are you requesting?
A new version of an existing package
Current Package Identifier
DG0JBJ.HDSDR
Package Version
2.81-b10
Please describe the changes you would like to see
There is a new release (2.81-b10) available. Download Page Url: https://www.hdsdr.de (https://www.hdsdr.de/download/HDSDR281b10_install.exe)

Also feel free to add the previous 2.81-b9:
https://www.hdsdr.de/download/HDSDR281b9_install.exe


Use const instead of final

You use final often in cases where the value is known at compile time like final millisecondsPerDay = 86400000;. Dart has const for declaring variables that are known at compile time.

Thanks for the suggestion!
It's done on #3


gpu.drawLine

Side

[ ] Lua side
[ ] C# side
[ ] Other
[X] I don't know

Describe the bug
the drawRectangle works as if top,left is 1,1 and drawLine seems to think it's 0,0 (maybe?)
To Reproduce
Steps to reproduce the behavior:

gpu.drawRectangle(1, 1, 10, 10, 0xf0f0f0, 1)
gpu.drawLine(1, 1, 10, 1, 0xff00ff, 1)
the pink line skips the first pixel

also gpu.setSize(width, height) doesn't want to work... in the lua console gpu.setSize(320, 200) just returns "false" and is ignored in my .lua scripts.
other than that it's quite fun to play with =oD
Expected behavior

Screenshots
https://drive.google.com/file/d/1QqZGjJURalmwXRGJsTJgfzclTUNYqllv/view?usp=share_link
Desktop (please complete the following information):

OS: Windows 10
OS Version: [e.g. 22]
Capy64 Version: [e.g. 0.0.9-alpha]

Additional context
Add any other context about the problem here.

Hi, thanks for reporting this issue!
I will look into gpu.drawLine, normally every coordinate should be 1-based, like gpu.drawRectangle.
Regarding gpu.setSize, this is normal behaviour yet to be documented (I am working on redoing the entire documentation).
Since 0.0.10-alpha I added "classic" and "free" modes, classic mode has a fixed window size that cannot be changed and the Lua tickrate is set to 20 (20 updates per second).
Free mode allows gpu.setSize and manual resizing of the window, and the tickrate is set to 60.
The mode can be changed by setting "engineMode" to 0 or 1, respectively "classic" and "free", the settings file can be found in %APPDATA%/Capy64/settings.json.


Style Tag

Hello.The problem is that the style tag the first quotation mark is highlighted, but not the last quotation mark, which is why there is no substructure inside the style tag

I'm having the same problem as well. This issue was brought up (and fixed) in #70, but it looks like it snuck its way back in.


Implement tagged and dynamic metrics

This PR adds support for tagged and dynamic metrics, via a strongly-typed interface based on the monad-metrics-extensible package.
Haddocks for the new interface may be temporarily found here. A tutorial for this new interface has also been written -- see Tutorial.md.
This PR also addresses issues 24, 29, 31, and 41 of tibbe/ekg-core, incorporating work from PRs 25, 30, and 42 of tibbe/ekg-core.
This PR also drops support for older versions of GHC using base < 4.10.
Related PRs:

https://github.com/hasura/ekg-json/pull/2
https://github.com/hasura/ekg/pull/1
https://github.com/hasura/ekg-statsd/pull/2

This PR now also has approval from @jberryman. Merging now.


libpqxx: 6.2.4 -> 6.2.5

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/libpqxx/versions.
meta.description for libpqxx is: '"A C++ library to access PostgreSQL databases"'.
Release on GitHub
Compare changes on GitHub

Checks done (click to expand)

built on NixOS

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 6.2.5 with grep in /nix/store/sb4r6wcd5zhqhzkcnqixh83q2l3kwm6h-libpqxx-6.2.5

directory tree listing: https://gist.github.com/ef277869b9b1a6ea1faaf8e2cccafdaf

du listing: https://gist.github.com/bac75e1a360f915ef139847e21f64417

Instructions to test this update (click to expand)

One-time optional setup to skip building using Cachix:
nix-shell -p cachix --run 'cachix use r-ryantm'

Test this update by entering a nix shell, seeing what is inside the
result, and if applicable, running some binaries:
nix-shell --pure -I nixpkgs=https://github.com/r-ryantm/nixpkgs/archive/605821e1b2fac0ce7dca5ac5decb59418a491eab.tar.gz -p libpqxx
ls -la /nix/store/sb4r6wcd5zhqhzkcnqixh83q2l3kwm6h-libpqxx-6.2.5

cc @edolstra for testing.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: libpqxx
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on aarch64-linux (full log)
Attempted: libpqxx
Partial log (click to expand)
 /nix/store/5s4072bfj6q40mhw5hgb8y4lbmgwrbga-coreutils-8.30/bin/install -c -m 644 libpqxx.pc '/nix/store/l8m1pp6kfsc4dqb3gld5rxpjna8fr6mv-libpqxx-6.2.5/lib/pkgconfig'
make[2]: Leaving directory '/build/source'
make[1]: Leaving directory '/build/source'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/l8m1pp6kfsc4dqb3gld5rxpjna8fr6mv-libpqxx-6.2.5
shrinking /nix/store/l8m1pp6kfsc4dqb3gld5rxpjna8fr6mv-libpqxx-6.2.5/lib/libpqxx-6.2.so
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/l8m1pp6kfsc4dqb3gld5rxpjna8fr6mv-libpqxx-6.2.5/lib
patching script interpreter paths in /nix/store/l8m1pp6kfsc4dqb3gld5rxpjna8fr6mv-libpqxx-6.2.5
checking for references to /build in /nix/store/l8m1pp6kfsc4dqb3gld5rxpjna8fr6mv-libpqxx-6.2.5...

Success on x86_64-linux (full log)
Attempted: libpqxx
Partial log (click to expand)
 /nix/store/dzvbhkzfgwkq97ljkcvi4gs7vmflh6a0-coreutils-8.30/bin/install -c -m 644 libpqxx.pc '/nix/store/sb4r6wcd5zhqhzkcnqixh83q2l3kwm6h-libpqxx-6.2.5/lib/pkgconfig'
make[2]: Leaving directory '/build/source'
make[1]: Leaving directory '/build/source'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/sb4r6wcd5zhqhzkcnqixh83q2l3kwm6h-libpqxx-6.2.5
shrinking /nix/store/sb4r6wcd5zhqhzkcnqixh83q2l3kwm6h-libpqxx-6.2.5/lib/libpqxx-6.2.so
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/sb4r6wcd5zhqhzkcnqixh83q2l3kwm6h-libpqxx-6.2.5/lib
patching script interpreter paths in /nix/store/sb4r6wcd5zhqhzkcnqixh83q2l3kwm6h-libpqxx-6.2.5
checking for references to /build in /nix/store/sb4r6wcd5zhqhzkcnqixh83q2l3kwm6h-libpqxx-6.2.5...


feat: add messages schedule update

What is the motivation for this pull request?
feat: add messages schedule update
https://www.braze.com/docs/api/endpoints/messaging/schedule_messages/post_update_scheduled_messages/
What is the current behavior?
No method to update scheduled messages
What is the new behavior?
Method to update scheduled messages: braze.messages.schedule.update()
Checklist:

[x] Conventional Commits
[x] Tests
[x] Documentation

Codecov Report

Merging #47 (52b67bb) into master (03f7267) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #47   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           44        45    +1
  Lines          215       221    +6
  Branches         5         5
=========================================
+ Hits           215       221    +6

Impacted Files
Coverage Δ

src/Braze.ts
100.00% <100.00%> (ø)

src/messages/schedule/index.ts
100.00% <100.00%> (ø)

src/messages/schedule/update.ts
100.00% <100.00%> (ø)

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


Modules not supported

Modules do not currently seem to be supported. When running golint against the full path of a module, error output indicates that it is searching GOROOT and GOPATH only.
Example:
golint -set_exit_status github.com/jniedrauer/cloudwatch-log-streamer/cmd/log-streamer github.com/jniedrauer/cloudwatch-log-streamer/pkg/config
cannot find package "github.com/jniedrauer/cloudwatch-log-streamer/cmd/log-streamer" in any of:
	/usr/lib/golang/src/github.com/jniedrauer/cloudwatch-log-streamer/cmd/log-streamer (from $GOROOT)
	/home/jniedrauer/go/src/github.com/jniedrauer/cloudwatch-log-streamer/cmd/log-streamer (from $GOPATH)
cannot find package "github.com/jniedrauer/cloudwatch-log-streamer/pkg/config" in any of:
	/usr/lib/golang/src/github.com/jniedrauer/cloudwatch-log-streamer/pkg/config (from $GOROOT)
	/home/jniedrauer/go/src/github.com/jniedrauer/cloudwatch-log-streamer/pkg/config (from $GOPATH)

However, it does succeed when given a relative path:
$ golint -set_exit_status pkg/config/
pkg/config/config.go:9:1: comment on exported var Properties should be of the form "Properties ..."
Found 1 lint suggestions; failing.

There is a pending cl to convert golint to working with modules:
https://go-review.googlesource.com/c/lint/+/127695
If you would like to try it and tell us if it works for you it would help us have confidence in that change.

After building golint from d2339b0, my output has changed:
[~/github.com/jniedrauer/cloudwatch-log-streamer]0$ golint -set_exit_status github.com/jniedrauer/cloudwatch-log-streamer/pkg/config
Cannot load packages: packages not found
[~/github.com/jniedrauer/cloudwatch-log-streamer]1$ ~/go/bin/go1.11beta3 build github.com/jniedrauer/cloudwatch-log-streamer/pkg/config
[~/github.com/jniedrauer/cloudwatch-log-streamer]0$

(CWD and exit statuses included for demonstration purposes.) It doesn't seem to work as expected. The go binary is able to build the package outside GOPATH, however golint still is not able to identify that we are currently in the module. Maybe I am misunderstanding how this solution is supposed to work, but shouldn't this use the same mechanism as the go binary now? Shouldn't they behave exactly the same?
On the plus side, it continues to function as expected when I clone the module into GOPATH.

I tried it on your project, not on GOPATH, and it worked correctly. I also changed your code to make it fail so I could check it was really working.
It does invoke go list underneath, so you need the right version of go on your PATH.
It has fallbacks for older versions of go (we use newer features of go list for speed), but there were some 1.11 versions that will not work (you need the latest rc) and there are some issues with tests where the output may differ in older go versions that we are working on.

Confirmed, this is working as expected since installing go1.11 in GOROOT. I didn't realize it was calling multiple processes.
So this patch (d2339b0) does resolve the issue.


restore build_sdk files

Restoring the deleted build_sdk folder to patch & develop. @sjanzou sorry for mistakenly deleting these. These all belong in the ssc repo correct?

@sjanzou Could you take a look a this please?

@dguittet, we no longer distribute the sdk from this build process. The potential reason to restore is to have some code examples that would potentially be lost.

@cpaulgilman, @janinefreeman, please check through the 187 files that were removed and see if we would like to include any of the examples in the SAM-Documentation repo or if we want to keep the build_sdk folder in the ssc public repo or add the files to an ssc wiki.

@sjanzou Are the system requirements for the various wrappers located somewhere in the code generator code now?
The file  build_sdk/apiwrappers/python/openei_utilityrate_billcalculator.py and associated files could be worth keeping since it shows the details of downloading a rate from the URDB and calling a utility rate compute module, although it is utilityrate3 so maybe too outdated to be useful. I'll defer to @cpaulgilman on other files in the examples folder- a lot of them are old, but I'm not sure we have any other examples of the C wrappers etc.

@janinefreeman  No, no system requirements in the generated code folders. There several user support issues involving code generation. We could keep the pdfs and copy them over to the code generation folder.

@sjanzou Is this an old pull request that can be safely closed without merging?

@cpaulgilman, yes, this is old and out of date and the website has many more recent examples.


DevilutionX 1.4.1

Is there a way to upgrade at least to DevilutionX 1.4.0 so that Gillian's stash would be available?
Also ShowItemLabels option would be nice :)

You should be able to see item labels by holding Alt, and you can also set labels to be always on by toggling with right Ctrl. Or are you referring to a different feature that I'm not familiar with?
As for Gillian's stash, it's possible but very difficult and time-consuming for me to upgrade Apocrypha to DevilutionX 1.4.1 since I'm doing this all by myself, and I'm still very new to coding in general. I could re-enable the Cornerstone so that you can transfer items between characters the old-fashioned way, but that would bring back a method of duping which I'd be unhappy with. I can't promise that anything will change soon, but it's something I'll think about going forward. I appreciate your comment though!

I didn't know about right Ctrl (its doing exactly as ShowItemLabels in .ini) - thanks :)))
For me stash is mainly useful to hoard gold (5k limit for 1 inventory space sucks) and to not drop items on town floor. I hate that it is shared among characters (gold) but better this than nothing. Anyway, if you can add this, would be great, but without it, it seems that you done very good work - i have lots of fun playing your mod.

I'm glad to hear you're still enjoying the mod nonetheless! To be fully transparent, my original idea for this mod was to make it feel closer to a roguelike, and I'm also a speedrunner so I thought it would be fun to make a mod of the game that felt more balanced and fun for speedrunning (I don't care about the vanilla leaderboards; it's just a fun run, and even more fun if the game is balanced). This is why I haven't really prioritized the stash: I usually play a single character for a very short period of time and then delete it/start over. Eventually I thought it would be nice to extend my balance changes to the rest of the game and make nightmare/hell more fun while also making it more engaging to fully gear up a character, and having a stash would definitely be useful for that. It's just a lot of work for a coding noob like myself. But hey, if anyone wants to make a fork of Apocrypha and add the stash in, they're more than welcome to do that!


Add New PFPS

closes #62
successor to #64

size consistency of meowy is bugged

i did what i had to, and that is shrink some of em

Because meower svelte does not have the newer BetterMeower pfps, this pr makes meower svelte pfps incompatible with BetterMeower and vice versa.

Add the new BetterMeower pfps to avoid breaking compatibility.

BM is not active, so it really does not matter, if you want to do this then make a pr to this branch

Add the new BetterMeower pfps to avoid breaking compatibility.

BM is not active, so it really does not matter, if you want to do this then make a pr to this branch

It does matter, because when it becomes active again (after CL4 port), it will break a lot. According to tnix, CL4 svelte will be done by the end of January.

Add the new BetterMeower pfps to avoid breaking compatibility.

BM is not active, so it really does not matter, if you want to do this then make a pr to this branch

It does matter, because when it becomes active again (after CL4 port), it will break a lot. According to tnix, CL4 svelte will be done by the end of January.

if you want to do this then make a pr to this branch

Add the new BetterMeower pfps to avoid breaking compatibility.

BM is not active, so it really does not matter, if you want to do this then make a pr to this branch

It does matter, because when it becomes active again (after CL4 port), it will break a lot. According to tnix, CL4 svelte will be done by the end of January.

if you want to do this then make a pr to this branch

No you need to fix the issue in this branch

@CST1229 what do you think of above, i don't see it as important. because bm pfps cant be seen or selected rn anyway. Josh can add the pfps if he wants do but idc about doin it myself

@CST1229 what do you think of above, i don't see it as important. because bm pfps cant be seen or selected rn anyway. Josh can add the pfps if he wants do but idc about doin it myself

Well then that will break Meower Svelte, because BetterMeower pfps show as the new pfps, it is important.

@CST1229 what do you think of above, i don't see it as important. because bm pfps cant be seen or selected rn anyway. Josh can add the pfps if he wants do but idc about doin it myself

Well then that will break Meower Svelte, because BetterMeower pfps show as the new pfps, it is important.

BM is your client; it's not my job to have compatibility with it. Even more so I don't even have the BM pfps

@CST1229 what do you think of above, i don't see it as important. because bm pfps cant be seen or selected rn anyway. Josh can add the pfps if he wants do but idc about doin it myself

Well then that will break Meower Svelte, because BetterMeower pfps show as the new pfps, it is important.

BM is your client; it's not my job to have compatibility with it. Even more so I don't even have the BM pfps

I can send you the BetterMeower pfps, there are 5.

~snip~

No, that won't work, the PFP picker is not going to show them. I am not adding an additional week of stress to my already cluttered and stressful holidays to make it work either.

Maybe we should just decide on all of the default pfps we're going to have in CL4 port and later and then just don't change them. Custom pfps will be a thing in CL4 port and later, so it doesn't make much sense to keep adding more and more default pfps.

we should have like a few default pfps which in reality set your custom pfp .png data to that image. once cl4 port, bettermeower pfps will not break and will instead just show a .png of the user instead of a pfp_data int

nah, since most of the default pfps are SVGs

This pr is for 1.6

That would work perfectly, because then I can add BetterMeower pfps and not have them break svelte.

That would work perfectly, because then I can add BetterMeower pfps and not have them break svelte.

Default pfps used in Meower Svelte shouldn't be file uploads though, since most are SVGs and will use a ton of bandwidth uploading default pfps.
The current way I have it in CL4 port is pfps/icons have 2 properties, 1 for the type and 1 for the data, type can either be 0 for default pfp or 1 for custom pfp, then data is either like it is now for default pfps or a partial upload object for custom pfps.

It's svgs because of scratch

It's svgs because of scratch

And why should it not be an SVG in svelte? It's far higher quality than a PNG or JPEG.
Also we have to keep compatibility with Scratch throughout CL4 port.

It's svgs because of scratch

And why should it not be an SVG in svelte? It's far higher quality than a PNG or JPEG.
Also we have to keep compatibility with Scratch throughout CL4 port.

Yeah ik, also svgs fail to render on gh for meh

That would work perfectly, because then I can add BetterMeower pfps and not have them break svelte.

Default pfps used in Meower Svelte shouldn't be file uploads though, since most are SVGs and will use a ton of bandwidth uploading default pfps.
The current way I have it in CL4 port is pfps/icons have 2 properties, 1 for the type and 1 for the data, type can either be 0 for default pfp or 1 for custom pfp, then data is either like it is now for default pfps or a partial upload object for custom pfps.

We could also add an option for a PFP URL.

That would work perfectly, because then I can add BetterMeower pfps and not have them break svelte.

Default pfps used in Meower Svelte shouldn't be file uploads though, since most are SVGs and will use a ton of bandwidth uploading default pfps.

The current way I have it in CL4 port is pfps/icons have 2 properties, 1 for the type and 1 for the data, type can either be 0 for default pfp or 1 for custom pfp, then data is either like it is now for default pfps or a partial upload object for custom pfps.

We could also add an option for a PFP URL.

Or use gravatar

Why is this PR still blocked. the issue has been resolved. and the thing being discussed is not the point of this PR

Why is this PR still blocked. the issue has been resolved. and the thing being discussed is not the point of this PR

i forgot

kinda nitpicking here, this pfp could be made larger (making the meowy about the same size as the others)

That one is sticking out; if I did not change it's size it would look odd
On Mon, Jan 16, 2023, 11:12 PM CST1229 @.***> wrote:

kinda nitpicking here, this pfp could be made larger (making the meowy
about the same size as the others)
[image: image]
https://user-images.githubusercontent.com/68464103/212815263-a4a775a6-c931-4b8c-afe2-a0468c6671a3.png
—
Reply to this email directly, view it on GitHub
https://github.com/meower-media-co/Meower-Svelte/pull/71#issuecomment-1384842085,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQHW4P43W7OM5UPWLTNDA4TWSYS5RANCNFSM6AAAAAATXGKFFY
.
You are receiving this because you authored the thread.Message ID:
@.***>

t-mobile

~snip~

t-mobile

telstra better

might close this PR because we do not need a full page of default profile pictures when APIv1/CL4 port/Beta 6 is honestly around the corner, which will have profile picture upload support. i don't care about the support of the old scratch clients as no one really uses them anyways and they're going to be depreciated soon. we should not add more default profile pictures until Beta 6, and users don't need another 20 profile pictures anyway.
if you dislike my thoughts go ahead and complain about it, but this PR just doesn't make sense due to future features.

if you dislike my thoughts go ahead and complain about it, but this PR just doesn't make sense due to future features.

I did the opposite of that

might close this PR because we do not need a full page of default profile pictures when APIv1/CL4 port/Beta 6 is honestly around the corner, which will have profile picture upload support. i don't care about the support of the old scratch clients as no one really uses them anyways and they're going to be depreciated soon. we should not add more default profile pictures until Beta 6, and users don't need another 20 profile pictures anyway.
if you dislike my thoughts go ahead and complain about it, but this PR just doesn't make sense due to future features.

i wish you can react the skull emoji

~snip~

t-mobile

telstra better

t-mobile gets a data breach almost every day

might close this PR because we do not need a full page of default profile pictures when APIv1/CL4 port/Beta 6 is honestly around the corner, which will have profile picture upload support. i don't care about the support of the old scratch clients as no one really uses them anyways and they're going to be depreciated soon. we should not add more default profile pictures until Beta 6, and users don't need another 20 profile pictures anyway.
if you dislike my thoughts go ahead and complain about it, but this PR just doesn't make sense due to future features.

cl4 is a month away, maybe 2. I think its fair to add more meowy pfps

cl4 is a month away

tnix says it's going to be released at the end of the this month, so, it's a week away, not a month

After then, it is still a month away bc of rewrites, that are needed
On Wed, Jan 25, 2023, 9:56 AM M.D. Walters @.***> wrote:

cl4 is a month away
tnix says it's going to be released at the end of the this month, so, it's
a week away, not a month
—
Reply to this email directly, view it on GitHub
https://github.com/meower-media-co/Meower-Svelte/pull/71#issuecomment-1403838448,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQHW4P2DPGQSNLK3VNIKJ43WUFEK7ANCNFSM6AAAAAATXGKFFY
.
You are receiving this because you authored the thread.Message ID:
@.***>

ok

might close this PR because we do not need a full page of default profile pictures when APIv1/CL4 port/Beta 6 is honestly around the corner, which will have profile picture upload support. i don't care about the support of the old scratch clients as no one really uses them anyways and they're going to be depreciated soon. we should not add more default profile pictures until Beta 6, and users don't need another 20 profile pictures anyway.
if you dislike my thoughts go ahead and complain about it, but this PR just doesn't make sense due to future features.

cl4 is a month away, maybe 2. I think its fair to add more meowy pfps

No it's not, it's already finished. Just waiting on CL4 port Svelte, which is planned to be done by the end of the month

might close this PR because we do not need a full page of default profile pictures when APIv1/CL4 port/Beta 6 is honestly around the corner, which will have profile picture upload support. i don't care about the support of the old scratch clients as no one really uses them anyways and they're going to be depreciated soon. we should not add more default profile pictures until Beta 6, and users don't need another 20 profile pictures anyway.
if you dislike my thoughts go ahead and complain about it, but this PR just doesn't make sense due to future features.

cl4 is a month away, maybe 2. I think its fair to add more meowy pfps

No it's not, it's already finished. Just waiting on CL4 port Svelte, which is planned to be done by the end of the month

yeah, i think im going to close this.

This is cst's project tho, so

might close this PR because we do not need a full page of default profile pictures when APIv1/CL4 port/Beta 6 is honestly around the corner, which will have profile picture upload support. i don't care about the support of the old scratch clients as no one really uses them anyways and they're going to be depreciated soon. we should not add more default profile pictures until Beta 6, and users don't need another 20 profile pictures anyway.
if you dislike my thoughts go ahead and complain about it, but this PR just doesn't make sense due to future features.

cl4 is a month away, maybe 2. I think its fair to add more meowy pfps

No it's not, it's already finished. Just waiting on CL4 port Svelte, which is planned to be done by the end of the month

It's mostly done, I would say it's stable (up until today where I broke user sessions and CL events, sorry). Right now it's just adding features and cleaning up code/API endpoints. Tomorrow it'll be back in a stable state and can start to be implemented into clients. The beta server is delayed a bit, and Idk when it'll be out.

And iv already implemented the new PFPs into SvelteKit. so if the pfps are not added, a official client does not have support lmao

This is cst's project tho, so

it’s a pull request…

This is cst's project tho, so

it’s a pull request…

Im talking about Meower-Svelte

And iv already implemented the new PFPs into SvelteKit. so if the pfps are not added, a official client does not have support lmao

Same with BetterMeower, except the Meower Svelte team chose to add BetterMeower pfps, NOT while trying to merge a whole new release.


cleanup: kvm-storage - fix misleading error log

Description
Discussed here, https://github.com/apache/cloudstack/issues/5309#issuecomment-898330887
Log is not actually an ERROR level log.

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[x] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

@blueorangutan package

@shwstppr a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 1085

@blueorangutan test

@nvazquez a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

@blueorangutan package

@nvazquez a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 1144

@blueorangutan test

@nvazquez a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-1977)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 47016 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr5396-t1977-kvm-centos7.zip
Smoke tests completed. 88 look OK, 1 have errors
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_01_1_create_iso_with_checksum_sha1_negative
Error
66.46
test_iso.py

@blueorangutan test

Merging based on lgtms and Travis job 1, trivial log only change


Updated version as promised in issue #29

Sorry about that. Got caught up with some other things and just hadn't got a chance to update the pod. I do that right after I merge your PR. I'm looking to port some of the Starscream code over as I think it has a lot of fixes Jetfire could use. Just haven't got a chance to sit down and do it yet. :smile:

Thanks for the quick response! :)

0.1.3 should be out now. :smile:

Awesome!


is it possible tensorflow-gpu  on RK3399 mali t-860?

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): LUbuntu 16.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: RK3399
TensorFlow installed from (source or binary): pip3
TensorFlow version: tensorflow 1.14(cpu)
Python version: python3.5
Installed using virtualenv? pip? conda?: pip3
Bazel version (if compiling from source): none
GCC/Compiler version (if compiling from source): gcc 5.5
CUDA/cuDNN version: none
GPU model and memory: mali t-860

hi.
My problem is running time is too long tensorflow(cpu version)
so, i try to install tensorflow-gpu on RK3399  GPU- mali t-860 (ARM)
but i can't install yet.
is it possible?
if possible how to install it?
Thank you

https://www.tensorflow.org/install/source#tested_build_configurations these versions are for x86_64 devices.
For ARM build, you might need to build it by yourself.
If you want to try TFLite, check followings.

https://github.com/tensorflow/tensorflow/tree/master/tensorflow/lite/tools/pip_package#alternative-build-with-bazel-experimental
https://www.tensorflow.org/lite/guide/build_arm64


Add documentation_url to info section of corral.json

As part of the work I am doing on the pony library documentation
generation, this documentation_url is needed.
The documentation_url will allow a library to link to the documentation
of its dependencies from within its own documentation.

Hi @SeanTAllen,
The changelog - added label was added to this pull request; all PRs with a changelog label need to have release notes included as part of the PR. If you haven't added release notes already, please do.
Release notes are added by creating a uniquely named file in the .release-notes directory. We suggest you call the file 166.md to match the number of this pull request.
The basic format of the release notes (using markdown) should be:
## Title

End user description of changes, why it's important,
problems it solves etc.

If a breaking change, make sure to include 1 or more
examples what code would look like prior to this change
and how to update it to work after this change.

Thanks.

Hi @SeanTAllen,
The changelog - added label was added to this pull request; all PRs with a changelog label need to have release notes included as part of the PR. If you haven't added release notes already, please do.
Release notes are added by creating a uniquely named file in the .release-notes directory. We suggest you call the file 166.md to match the number of this pull request.
The basic format of the release notes (using markdown) should be:
## Title

End user description of changes, why it's important,
problems it solves etc.

If a breaking change, make sure to include 1 or more
examples what code would look like prior to this change
and how to update it to work after this change.

Thanks.

Windows failure is a known issue that @kulibali will be looking into when he has a chance.

Windows failure is a known issue that @kulibali will be looking into when he has a chance.


Bumping version to 1.1.2

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: StepFunctionsPythonSDK-integtests
Commit ID: 4ded0b5e7638c2832fc42bdf7e7f5b815ddc2816
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


KAFKA-14446: API forwarding support from zkBrokers to the Controller

KAFKA-14446: API forwarding support from zkBrokers to the controller
Changes

Enable EnvelopeRequest to support zkBroker to zkController forwarding.
Changes to BrokerToControllerChannelManager, which we use in every broker to maintain a channel to the controller node. This node and security protocol to connect to the node can keep changing during zk -> kraft migration. Also, added support to reinitialize the request thread used in BrokerToControllerChannelManager when the controller switches from zkBroker to kraftController and vice-versa.
Other peripheral changes required to support the above changes.

We can close #11042 and #11281 after merging this, but we can take a look to see whether we can port some useful code.

I think the better approach to take here would be to make the ControllerNodeProvider return a tuple of (isKraft, controller id) and then have it check the metadata cache to see if it needs to use a kraft controller.
Then have the inter broker send thread do something useful if it sees a transition. I agree that we might want to use an external thread for this (or possibly the scheduler) but that should just be for reinitialization


Remove ICS4Wrapper

Summary
Once WriteAcknowledgement and GetAppVersion funcs are removed

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged/assigned

This issue is being closed as the team has decided to move in another direction https://github.com/cosmos/ibc-go/issues/6941#issuecomment-2312559378 - it will be reopened if necessary


Updating all dependencies (#57)

Fix #57

Just found out that xml package is important differently and also need an update.
Should I add it to this one or in the next pr

Decided to  update xml package in this pr

i wonder if this package is still maintained 🤔
eventually thinking of forking and improving because i need this for musicpod

i wonder if this package is still maintained 🤔 eventually thinking of forking and improving because i need this for musicpod

You can take my fork for that


Question: how to visualise my own arch?

Hi all,
Same with many others, Adrian's great talk on State of Arts Microservices brought me here.
I am having my first go at Simianviz. Just created my own json arch by using the provided script to convert my docker compose file (name:"frontier_arch.json").  I can see now in the json_arch folder:

tree json_arch
json_arch
├── aws_ac_ra_web_arch.json
├── cassandra_arch.json
├── container_arch.json
├── frontier_arch.json
├── lamp_arch.json
├── netflix_arch.json
├── netflixoss_arch.json
├── test_arch.json
├── testyaml_arch.json
└── yogi_arch.json

I can see I could run spigo to simulate some load:

/spigo -a frontier -d 5 -j -g
2015/10/21 13:17:12 Loading architecture from json_arch/frontier_arch.json
2015/10/21 13:17:12 frontier.edda: starting
2015/10/21 13:17:12 Architecture: /Users/jasonw/java/projects/vagrant-docker-jenkins-frontier/frontier_sharefolder/docker-files/frontier-compose/docker-compose.yml compose yaml
2015/10/21 13:17:12 architecture: scaling to 100%
2015/10/21 13:17:12 Starting: {mysql1 machine instance frontier-mysql process monolith 1 3 []}
2015/10/21 13:17:12 frontier.us-east-1.zoneA.eureka0....eureka.eureka: starting
2015/10/21 13:17:12 frontier.us-east-1.zoneB.eureka1....eureka.eureka: starting
2015/10/21 13:17:12 frontier.us-east-1.zoneC.eureka2....eureka.eureka: starting
2015/10/21 13:17:12 Starting: {frontier_java_app_1 machine instance frontier-java-app process monolith 1 3 [mysql1]}
2015/10/21 13:17:12 Starting: {frontier_java_app_2 machine instance frontier-java-app process monolith 1 3 [mysql1]}
2015/10/21 13:17:12 Starting: {haproxy1 machine instance frontier-haproxy process monolith 1 3 [frontier_java_app_1 frontier_java_app_2]}
2015/10/21 13:17:12 frontier.us-east-1.zoneC.haproxy12....haproxy1.monolith activity rate  10ms
2015/10/21 13:17:17 asgard: Shutdown
2015/10/21 13:17:17 frontier.us-east-1.zoneC.eureka2....eureka.eureka: closing
2015/10/21 13:17:17 frontier.us-east-1.zoneA.eureka0....eureka.eureka: closing
2015/10/21 13:17:17 frontier.us-east-1.zoneB.eureka1....eureka.eureka: closing
2015/10/21 13:17:17 spigo: complete
2015/10/21 13:17:17 frontier.edda: closing

I started the server using
npm run dev
I assumed my architecture diagram would show up along with the 'lamp', 'netflix' ones in the dropdown but couldn't find it.
Am I missing something?
Another question is, when I am generating load using Spigo commandline, should I be expecting visual changes on the d3 diagrams?  Or the 'charge' on the page meant to be for that?
Many thanks,
Jason

To add a new arch to the menu you need to edit the menu in the UI at the end of this file
https://github.com/adrianco/spigo/blob/master/ui/js/toolbar/index.js
Sorry I didn't see this question earlier.
Spigo commandline saves files that the UI loads later. Charge pushes the nodes apart in the UI.


Settings: Settings can be extracted from UI

Brief description
Added option to extract current values into json file.
Description
Extraction takes current values and extract them to a json file. It takes all values no matter if are overriden or not. Values are stored under keys with double underscores to be able differentiate what is value and what are metadata. Also added option to paste values from clipboard that are copied from different source or when whole file is copied.
Additional information
Didn't add option to "open json file" because it would be hard to find out what user want's to do with it. This is not meant as backup of Project settings as it does not save only overrides but all values.
Testing notes
Extract values to file

Open settings UI
Right click on any item in settings and hit Extract to file
Select output file and hit Save
Check output

Using extracted file

Open settings UI
Copy file in file explorer
Right click in settings where would you like to paste values
Paste action should be visible and if the saved file contains path there should be also Paste to same place
Try them

Paste value as text

Open settings UI
Copy json content as text

# For example 'system_settings/modules/avalon'
{
    "AVALON_TIMEOUT": 666,
    "AVALON_THUMBNAIL_ROOT": {
        "windows": "D:/evil/directory",
        "darwin": "",
        "linux": ""
    }
}

Try to paste it into settings UI

Related to #3271


Reorder files for better reading experience

Check this out! https://github.com/arifulhaqueuc/python-multithreading-examples/issues/31


WoCCatalog [ARM|Release] Display Mode state is incorrect when returning to page

Phone: Lumia 950 device (14393 build)
Master commit: 4804ed9
Build/run WOCCatalog in Release.
Tap "DisplayMode"
Change Preset modes to "Tablet768x1024"
Navigate back to menu
Tap "DisplayMode"
Observe selected value for Present Modes
Expected:
Preset mode has "Tablet768x1024" selected
Actual:
Present mode has "Native" selected.
This is a regression

checked in the revert which causes this issue.


No error display with next branch?

When using the next branch of the boilerplate, I get no error display on the page when I add a syntax error to my component (although the error does show up in the console). When using the master branch, I do not have this issue. Was error reporting removed when switching to the next branch or is the branch not ready for use yet? Or am I just doing something wrong?
Steps to reproduce:

Go to the next branch, click the Clone or download button, and then click Download ZIP.
After unzipping the contents, run npm install, and then npm start.
Go to the Counter.js file and change
Counter: {this.state.counter}
 to <h2Counter: {this.state.counter}

As you can see, the error shows up in the console but there is no feedback on the page itself:

When using the boilerplate from the master branch, I DO get feedback:

Please let me know if I can provide any more information. Thanks very much.

It looks like I just needed to add overlay: true to the devServer options in webpack.config.js. Should this be in there by default? If not, feel free to close this.


C++: Make InitializeParameter and Uninitialized return memory results

The IR avoids having non-trivially-copyable and non-trivially-assignable types in register results, because objects of those types need to exist at a particular memory location. The InitializeParameter and Uninitialized instructions were violating this restriction because they returned register results, which were then stored into the destination location via a Store.
This change makes those two instructions take the destination address as an operand, and return a memory result representing the (un-)initialized memory, removing the need for a separate Store instruction.
Note: This PR is rebased on top of the commits for pending PR #67. Only commit 56db3c3 needs to be reviewed. Once #67 is merged, the other commits should disappear from this PR. I'll remove the WIP label once that happens.

#67 is merged. To make GitHub forget the overlapping commits, you may have to close and re-open. Or maybe rebase.

I think this change actually makes Uninitialized and InitializeParameter more like UnmodeledDefinition. UnmodeledDefinition already produces a memory result. This change makes InitializeParameter and Uninitialized do the same. All of these represent memory locations whose contents were defined external to the function.

To add the additional background you asked for:
InitializeParameter represents the initialization of the parameter with the argument value, which happens at the call site. The IR-based dataflow library will connect interprocedural flow between the definition of the argument in the caller and the corresponding InitializeParameter result in the callee.
Uninitialized is used to provide a definition for a local variable that does not have an initializer (implicit or explicit).

Thanks for the clarification. I think my confusion is over whether I should conceptually think of these instructions as storing an unknown value into the variable or as terminators of the loose source ends in the SSA graph. I agree that this change brings them closer to the latter.
Looking at the test output in its new and helpful format (:heart: #65), a function with a parameter x changes from this:
#   50|     r0_2(int)          = InitializeParameter[x] :
#   50|     r0_3(glval<int>)   = VariableAddress[x]     :
#   50|     m0_4(int)          = Store                  : r0_3, r0_2

to this:
#   50|     r0_2(glval<int>)   = VariableAddress[x]     :
#   50|     m0_3(int)          = InitializeParameter[x] : r0_2

That's an improvement, but I don't understand why x needs to be mentioned twice. If I shouldn't think of InitializeParameter as storing something at an address, maybe we can simplify it even further to this:
#   50|     m0_3(int)          = InitializeParameter[x] :

In order to do alias analysis and build SSA, we need to know what memory location (or locations) may be defined by the result of each instruction. There are currently four kinds of memory access that alias analysis knows about (from "MemoryAccessKind.qll": IndirectMemoryAccess, PhiMemoryAccess, EscapedMemoryAccess, and UnmodeledMemoryAccess. IndirectMemoryAccess is used wherever possible; the other three are more-or-less unavoidable special cases. IndirectMemoryAccess requires one of the operands of the instruction to be the address of the memory location being referenced.
Merging the VariableAddress+InitializeParameter pair into a single InitializeParameter means that we'd have to add another special case to the alias analysis, because we would no longer have the address as an operand. Keeping it as an indirect access is consistent with our existing approach of handling all variable accesses as indirect. If we ever decided that accessing a local variable should be a single LoadVariable or StoreVariable instruction, rather than a VariableAddress+Load|Store combo, we would want to remove the VariableAddress from the InitializeParameter sequence as well for consistency.
If we wanted to only mention x once, we would either have to leave it off of the InitializeParameter, or leave it off of the VariableAddress. Leaving it off the VariableAddress would be inconsistent with other usage of VariableAddress. Leaving it off of InitializeParameter would be OK. However, any interprocedural data flow, and probably some intraprocedural stuff too, would want to easily map from the Parameter to the corresponding InitializeParameter that defines its value, so we'd want a getParameter() predicate on it anyway.
I'd like to reconsider the whole "all memory accesses are indirect" decision after we've written one or two real queries on the IR. My original theory was that making everything indirect would mean fewer cases to handle in anything that used the IR. If it turns out that our real usage of the IR doesn't need to make that distinction, and only the guts of alias analysis and SSA construction care, then I'd probably be OK with introducing direct loads and stores of variables and fields to make the IR a bit smaller.