text:
Fix bug where bwt sendsd 2017 headers to electrum

It was causing this error in electrum 4.0.9:

E/i | interface.[localhost:50001] | Exception in wrapper_func: RequestCorrupted('expected 2016 headers but only got 2017')
Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/electrum/util.py", line 1056, in wrapper
    return await func(*args, **kwargs)
  File "/usr/lib/python3.9/site-packages/electrum/interface.py", line 481, in wrapper_func
    return await func(self, *args, **kwargs)
  File "/usr/lib/python3.9/site-packages/electrum/interface.py", line 505, in run
    await self.open_session(ssl_context)
  File "/usr/lib/python3.9/site-packages/electrum/interface.py", line 649, in open_session
    await group.spawn(self.monitor_connection)
  File "/usr/lib/python3.9/site-packages/aiorpcx/curio.py", line 242, in __aexit__
    await self.join()
  File "/usr/lib/python3.9/site-packages/aiorpcx/curio.py", line 211, in join
    raise task.exception()
  File "/usr/lib/python3.9/site-packages/electrum/interface.py", line 703, in run_fetch_blocks
    await self._process_header_at_tip()
  File "/usr/lib/python3.9/site-packages/electrum/interface.py", line 720, in _process_header_at_tip
    await self.sync_until(height)
  File "/usr/lib/python3.9/site-packages/electrum/interface.py", line 729, in sync_until
    could_connect, num_headers = await self.request_chunk(height, next_height)
  File "/usr/lib/python3.9/site-packages/electrum/interface.py", line 613, in request_chunk
    raise RequestCorrupted(f"expected {size} headers but only got {res['count']}")
electrum.interface.RequestCorrupted: expected 2016 headers but only got 2017

The assertion failed without the fix.

Thanks!
I wonder how I never ran into this, probably only happens if the wallet is in some unusual state?

authors: shesek stevenroose

repo: bwt-dev/bwt


text:
Refactor the codebase

Issue: https://github.com/byhbt/kwtool/issues/9
What happened
After a long time back to the IC, I found that the codebase structure need to be refactored to make it consistent with the
convention. Here is the list of thing updated in this PR.

[x] Store HTML result in a separate table, add new migration KeywordResult
[x] Update the npm packages version
[x] Rename the Context name from plural to singular

Insight
n/a
Proof Of Work
The tests should pass.

This PR is obsoleted.

source: gharchive/pull-request

repo: byhbt/kwtool

license: MIT

license_type: permissive

license_source: github-api


text:
--continue-on-success Gets "ACCESS_DENIED" After First Success

Steps to reproduce
cme smb dc01.storm.ctf -u users.txt -p welcome1 --continue-on-success
I'd post the output but it's of a client's network. --continue-on-success has never worked for me but I could really use it!

I have the same issue... can you confirm if within the password file welcome1, you have a password with characters like !#$@%$(?
It get errors on the smb and winrm module. I been testing it on a hackTheBox machine that I know the username and password is 100% accurate and it fails because the contents of the file has special characters... when I surround the password with single quotes or double quotes on the file, the errors are gone but of course the password doesn't match ...

Working on Windows 10 but not on Windows server 2016. I will look into it but it's probably related to impacket

It's linked to the smb signing, here is an example if smb signing is disabled

Ok I push a fix

source: gharchive/issue

license_source: bigquery


text:
wasmparser: Remove offset param in VisitOperator

Implementing VisitOperator is complicated by the additional passing-through of the offset everywhere. A much simpler alternative code wise is to stash the offset away within the implementation of VisitOperator before invoking SomeReader::visit_operator.
This raises some complications with visitors that depend on the offsets and rely on them for functional correctness, though. This is the case for the FuncValidator which uses offsets to verify that the very last end operator seen is at the same offset as the reader when the validator is finalized.

The main motivation behind the VisitOperator API was as a more efficient way to parse, validate and transform Wasm bytecode. I can understand the motivation behind this PR but really hope that we won't regress performance of validation or other means of using this API.

The main motivation behind the VisitOperator API was as a more efficient way to parse, validate and transform Wasm bytecode. I can understand the motivation behind this PR but really hope that we won't regress performance of validation or other means of using this API.

I definitely am aware of that. I wouldn’t have proposed this change if my intuition didn’t suggest the different ways of passing the offset around didn’t meaningfully change the perf characteristics of the code.

My dev machine isn’t really set-up for quality benchmarking, with a ton of stuff running in there, but here are the results:
parse/tests             time:   [2.5424 ms 2.5431 ms 2.5438 ms]
                        change: [+1.2777% +2.1963% +2.9292%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 2 outliers among 100 measurements (2.00%)
  2 (2.00%) high mild

validate/tests          time:   [9.2935 ms 9.2974 ms 9.3014 ms]
                        change: [-1.5510% -1.1343% -0.8100%] (p = 0.00 < 0.05)
                        Change within noise threshold.
Found 1 outliers among 100 measurements (1.00%)
  1 (1.00%) high mild

validate/bz2            time:   [953.63 µs 954.91 µs 956.74 µs]
                        change: [-0.2498% -0.1441% -0.0084%] (p = 0.02 < 0.05)
                        Change within noise threshold.
Found 2 outliers among 100 measurements (2.00%)
  1 (1.00%) high mild
  1 (1.00%) high severe

parse/bz2               time:   [578.27 µs 578.31 µs 578.35 µs]
                        change: [+0.9696% +1.0978% +1.1982%] (p = 0.00 < 0.05)
                        Change within noise threshold.
Found 7 outliers among 100 measurements (7.00%)
  6 (6.00%) high mild
  1 (1.00%) high severe

validate/intgemm-simd   time:   [1.9817 ms 1.9839 ms 1.9867 ms]
                        change: [+0.6718% +0.7915% +0.9672%] (p = 0.00 < 0.05)
                        Change within noise threshold.
Found 1 outliers among 100 measurements (1.00%)
  1 (1.00%) high severe

Benchmarking parse/intgemm-simd: Warming up for 3.0000 s
Warning: Unable to complete 100 samples in 5.0s. You may wish to increase target time to 5.6s, enable fla
t sampling, or reduce sample count to 60.
parse/intgemm-simd      time:   [1.1027 ms 1.1030 ms 1.1035 ms]
                        change: [+1.8445% +1.9715% +2.0582%] (p = 0.00 < 0.05)
                        Performance has regressed.
Found 11 outliers among 100 measurements (11.00%)
  1 (1.00%) low mild
  3 (3.00%) high mild
  7 (7.00%) high severe

validate/pulldown-cmark time:   [2.2530 ms 2.2542 ms 2.2555 ms]
                        change: [+0.8914% +0.9679% +1.0370%] (p = 0.00 < 0.05)
                        Change within noise threshold.
Found 1 outliers among 100 measurements (1.00%)
  1 (1.00%) high mild

Benchmarking parse/pulldown-cmark: Warming up for 3.0000 s
Warning: Unable to complete 100 samples in 5.0s. You may wish to increase target time to 6.7s, enable fla
t sampling, or reduce sample count to 60.
parse/pulldown-cmark    time:   [1.3279 ms 1.3281 ms 1.3285 ms]
                        change: [+0.8563% +0.8996% +0.9471%] (p = 0.00 < 0.05)
                        Change within noise threshold.
Found 16 outliers among 100 measurements (16.00%)
  1 (1.00%) low severe
  6 (6.00%) high mild
  9 (9.00%) high severe

Benchmarking validate/spidermonkey: Warming up for 3.0000 s
Warning: Unable to complete 100 samples in 5.0s. You may wish to increase target time to 5.7s, or reduce
sample count to 80.
validate/spidermonkey   time:   [56.373 ms 56.653 ms 57.075 ms]
                        change: [+0.9209% +1.4428% +2.2000%] (p = 0.00 < 0.05)
                        Change within noise threshold.
Found 2 outliers among 100 measurements (2.00%)
  2 (2.00%) high severe

parse/spidermonkey      time:   [33.288 ms 33.293 ms 33.299 ms]
                        change: [+0.7947% +0.8221% +0.8500%] (p = 0.00 < 0.05)
                        Change within noise threshold.
Found 9 outliers among 100 measurements (9.00%)
  8 (8.00%) high mild
  1 (1.00%) high severe

the benchmark runner is indeed reporting some regressions over the baseline, however where there are regressions, they are definitely still within run-to-run variance on my machine, as running the same benchmark will readily report an improvement of about as many percent.

This seems reasonable to me and I like the way it's integrated with FuncValidator. Was there anything else you wanted to add before merging?
For benchmarking using criterion is not useful to detect very small changes, which if this has any effect it'd be quite small. I would hope, though, that any slowdown could be recovered via other means rather than plumbing offset everywhere.

I think this is ready to merge at this point. I wasn’t thinking of making any significant additional changes in this PR, except for addressing any feedback.

authors: Robbepop alexcrichton nagisa

repo: bytecodealliance/wasm-tools


text:
wasmtime demo command fail to execute markdown.wasm

Following the demo in this youtube video with a clone of this directory, I was unable to use wasmtime to run wasmtime markdown.wasm --invoke render "# Hello"
wasmtime version 0.9.0
Error:
~/wasmtime-demos/markdown(master) » wasmtime markdown.wasm --invoke render "# Hello"
Error: failed to run main module `markdown.wasm`

Caused by:
    func type returns multiple values (at offset 47)

I'm going to now that we've temporarily removed interface types support, but stay tuned to https://github.com/bytecodealliance/wasmtime/issues/677 for future updates!

authors: alexcrichton whalelephant

repo: bytecodealliance/wasmtime-demos


text:
Clock print error ?

Steps to Reproduce
(1) The cfile is :
#define _POSIX_C_SOURCE 199309L

#include <stdio.h>
#include <stdlib.h>
#include <time.h>

int clock_time_get(clockid_t clock_id) {
    struct timespec tp;

    if (clock_gettime(clock_id, &tp) == 0) {
        printf("Successfully get the clock time.\n");
        printf("seconds: %ld\n", tp.tv_sec);
        printf("nano seconds: %ld\n", tp.tv_nsec);
    } else {
        perror("Failed to get the clock time.\n");
        return 1;
    }

    return 0;
}

int clock_time_geto2Ei6c4mXI (){
    clockid_t clock_id = CLOCK_MONOTONIC;
    return clock_time_get(clock_id);
}

int main() {
    clock_time_geto2Ei6c4mXI ();
}

(2)compile the c file into wasm: ./wasi-sdk-16.0/bin/clang --target=wasm32-unkown-wasi --sysroot=./wasi-sdk-16.0/share/wasi-sysroot clock.c -o clock.wasm
(3)exeute clock.wasm
wasmtime run  clock.wasm
Expected Results
Using gcc clock.c -o clock and ./clock to execute get the following result:
Successfully get the clock time.
seconds: 17709947
nano seconds: 519650825
And wamr, wasmedge,wasmer also print the above message.
Actual Results
wasmtime prints:
Successfully get the clock time.
seconds: 0
nano seconds: 1053984
wasmtime print the seconds is zero ? I'm not sure whether this is a bug.
Sorry for bothering you. Thanks a lot !
Versions and Environment
wasmtime 13.0.0
Operating system: Ubuntu 20.04
Architecture: x86_64

https://github.com/bytecodealliance/wasmtime/blob/2f83f97c9f4f7f98750eb2be19a336339da931e2/crates/wasi-common/src/snapshots/preview_1.rs#L97-L100 It is supposed to work at least. Not sure what the issue is here.

The monotonic clock is relative to an arbitrary point in time, and Wasmtime's arbitrary point is the start of the instance itself, so what's happening here is the time is being measured shortly after the instance starts. This is to avoid leaking information about the host's own clocks to the guest which doesn't need to know that information by default.

@orangeC23 is there perhaps something we can help you out with at a higher level? You've opened a number of issues here which appear to be mostly poking at WASI behavior. Is there a way we could perhaps help out with that and/or help steer? I'm curious how these programs are coming into existence for example and if it might be good to file issues for clarifications/etc on the WASI specifications themselves for example.

repo: bytecodealliance/wasmtime


text:
Don't implicitly create empty files in VirtualDir::openat

Prior to this change, non-existent files opened inside the wasi/wasm binary via std::fs::read_to_string() would show up as existing and empty.
Any guidance on where tests should be added would be most helpful.
Not sure who should review?

Good catch, thank you! The changes look good, but (as you've noted) it would be good to have a test around this too. A non-OFLAGS_CREAT counterpart to https://github.com/bytecodealliance/wasmtime/blob/main/crates/test-programs/wasi-tests/src/bin/path_open_create_existing.rs should do the trick. The virtfs testing uses the same test binaries as real-filesystem wasi tests, since they ought to behave the same.
(the actual test generation happens here if you're curious - if a test uses the filesystem, it gets two suites. if not, just one)

Hmm, possibly dumb question - how do I run those tests? I've inserted a panic in the test you pointed to, and I don't see a failure with cargo test, in either the root dir, or in the test-programs crate.

Ah I forgot about that, it's been a minute - I fished around in the CI config and found
        cargo test \
            --features test-programs/test_programs \
            --all \
            --exclude lightbeam \
            --exclude peepmatic \
            --exclude peepmatic-automata \
            --exclude peepmatic-fuzzing \
            --exclude peepmatic-macro \
            --exclude peepmatic-runtime \
            --exclude peepmatic-test

test-programs is a feature you have to enable to get them run in cargo test

I see you found it :)

Haha I found that magic incantation in the wasi-common readme too. Copied it to the test-programs readme to hopefully avoid confusion for others.

I'm completely befuddled as to why CI is failing. The line it's pointing to in the error doesn't seem to line up with the code in this PR (the line number is wrong).

wasmtime tests run against a temporary merge commit against the target branch - you've got a clean merge but semantically this conflicts with https://github.com/bytecodealliance/wasmtime/pull/2201. you can drop the types:: prefix and it should all be good. If you wouldn't mind rebasing on main that'll get you a clean and working test locally too.


text:
String array mapping

Hi,
am I missing something or is there no mapping for any array db type?

I have already added it some time ago, but apparently forgot to release it. I will release a new NuGet Version later today and then it will be available. See: https://github.com/bytefish/PostgreSQLCopyHelper/blob/master/PostgreSQLCopyHelper/PostgreSQLCopyHelper/PostgreSQLCopyHelper/Extensions/ArrayTypeExtensions.cs.

I have uploaded the latest Version 1.2 to NuGet, so it should be available soon.
Here is how to use it.
Imagine you have the following Domain model:
private class StringArrayEntity
{
    public String[] Array { get; set; }
}

var subject = new PostgreSQLCopyHelper<StringArrayEntity>("sample", "unit_test")
    .MapArray("col_array", x => x.Array);

StringArrayEntity entity0 = new StringArrayEntity()
{
    Array = new string[] { "ValueA", "ValueB" }
};

StringArrayEntity entity1 = new StringArrayEntity()
{
    Array = new string[] { "ValueA", "ValueB" }
};

subject.SaveAll(connection, new[] { entity0, entity1 });

Please let me know, if this fixes your problem. 😅

@bytefish I didn't see your response right away.
When I've pulled the code I figured out that there is actually a way to do it, like this:
.Map("TextArrayField", x => x.TextArrayField, NpgsqlDbType.Array | NpgsqlDbType.Text)
But I guess your proposed solution is just a bit more elegant way of doing it.

Good, that it works! Thanks for the Feedback.:+1:

authors: bytefish talfirevic

repo: bytefish/PostgreSQLCopyHelper

license: mit


text:
Fixed byuErrors

This change is

Reviewed 7 of 7 files at r1.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

app/src/main/java/edu/byu/suite/features/calendars/controller/CalendarActivity.java, line 86 at r1 (raw file):

			Call<List<Event>> calendarCall = api.getCalendar(url, String.format("%dMO", offset));
			addCall(calendarCall);
			calendarCall.enqueue(new ByuCallback<List<Event>>(CalendarActivity.this,ERROR_MESSAGE) {

Actually, remove this one. The only time we need a custom error is when it's a widely used feature, or the message is specific

app/src/main/java/edu/byu/suite/features/sickVacation/controller/SickVacationMainActivity.java, line 37 at r1 (raw file):

		Call<LeaveDataWrapper> call = ((SickVacationClient.Api) ByuApiGenerator.createApi(this, new SickVacationClient())).getBalanceData();
		addCall(call);
		call.enqueue(new ByuCallback<LeaveDataWrapper>(this,ERROR_MESSAGE) {

Remove this one as well

Comments from Reviewable

Reviewed 2 of 2 files at r2.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

app/src/main/java/edu/byu/suite/features/calendars/controller/CalendarActivity.java, line 40 at r2 (raw file):

	private int offset = 3;
	private EventAdapter adapter = new EventAdapter(null);
	private final String ERROR_MESSAGE = "An error occurred while trying to load more events";

You should be able to delete this now too

app/src/main/java/edu/byu/suite/features/sickVacation/controller/SickVacationMainActivity.java, line 23 at r2 (raw file):

public class SickVacationMainActivity extends ByuActivity {
	private final static String LOAD_MESSAGE = "Loading Sick and Vacation Data. Please Wait...";
	private final static String ERROR_MESSAGE = "Error Loading Sick and Vacation Data. Please try again.";

Delete this

Comments from Reviewable

Reviewed 2 of 2 files at r3.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


text:
Made lists in University Class Schedule searchable. Closes #149

This change is

Reviewed 24 of 24 files at r1.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

support/src/main/java/edu/byu/support/client/registrationClient/model/Section.java, line 136 at r1 (raw file):

		if (children != null) {
			for (Section child : children) {
				matches |= child.matchesQuery(lowerCaseQuery);

Short circuit

Comments from Reviewable

Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

Comments from Reviewable

Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


text:
feature/personDirectory

This change is

Reviewed 2 of 2 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

repo: byu-oit-appdev/ios-byuSuite


text:
MBC2 fixes

Fix MBC2 emulation to pass the following Mooneye GB tests:

emulator-only/mbc2/bits_ramg.gb
emulator-only/mbc2/bits_romb.gb
emulator-only/mbc2/ram.gb

Fixed by 06212f1cbcf8025f471d6c45c4836e59f97b0758 and fd267c49b28493b361dce582b08b95995aeda1f2.

repo: c-sp/AGE


text:
Fix init() got an unexpected keyword argument 'disable_ssl_certificate_validation'

I just updated bitHopper and now get these errors:
16:17:17|api: arsbitcoin api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: btcg api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: mtred api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: asspenny api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: bcpool api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: bitchomp api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: bitfarms api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: bitp api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: bitpenny api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: btcmine api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: btcserv api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: coinotron api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: guildminers api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: itzod api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: masterpool api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: namebit api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: nmcbit api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: nofeemining api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: ozco api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: yourbtc api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: slush api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: triple api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: deepbit api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: bitclockers api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: bithasher api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: bloodys api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: digbtc api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: kiwipool api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
16:17:17|api: simplecoin api error:init() got an unexpected keyword argument 'disable_ssl_certificate_validation'
I tried to solve it myself, but Google isn't very helpful with this error.
Could this be a httplib2 version incompatibility? I've followed the README, though. I've Ubuntu 11.10.

Yes it is. I modified the readme which should hopefully fix it. You probably don't have ssl libs installed.

Thanks, I did
sudo pip install gevent setuptools gitpython httplib2 --upgrade
and it solved the issue!


text:
🛑 cms2.alejtech.eu is down

In f807050, cms2.alejtech.eu (http://cms2.alejtech.eu/UserSystem/login/login.alej) was down:

HTTP code: 403
Response time: 575 ms

Resolved: cms2.alejtech.eu is back up in 62ba169.


text:
🛑 www.priklady.eu is down

In de247a1, www.priklady.eu (https://www.priklady.eu/sk/Index.alej) was down:

HTTP code: 503
Response time: 1016 ms

Resolved: www.priklady.eu is back up in 15ebb26 after 20 minutes.


text:
Upgrade android dev tools: android studio 4.0.1, android.gradle plugin-4.0.1, gradle-6.5.1, sdk build tool 29.0.2

See title

For the documentation on Windows OS/Android Studio deployment:
Set an environment variable ANDROID_NDK_HOME=
=> Android build is running out of the box (on my developer environment)
BUT: I have to remove this  .so from src/man/jniLibs/   <<<< should be removed via build/not part of the 3d party stuff

Hint for Android build out of the box:
Remove *.so from src/man/jniLibs/ before starting the build.

Can easy to auto package .so to apk


text:
add support for the version to the URL that shows the Oncotree GUI?

Add version name/number in the URL

This feature has been added in https://github.com/cBioPortal/oncotree/pull/35

repo: cBioPortal/oncotree


text:
Docker compose is wrong.

The docker-compose.yml is wrong and doesn't even pull the correct docker image for this project. I recommend you post a docker-compose.yml like this.
version: "3.1"
services:
  cabernet:
    container_name: cabernet
    environment:
      - PGID=1000
      - PUID=1000
      - TZ=America/Chicago
    image: ghcr.io/cabernetwork/cabernet:latest
    ports:
      - "5004:5004"    # Port used to stream
      - "6077:6077"    # Web Interface Port
      - "65001:65001"  # HDHomeRun Port
    restart: unless-stopped
    volumes:
      - /home/docker/cabernet:/app/data/

I would recommend you look at using linuxserver ubuntu as the base so you can get the ability to pick the user the docker runs as.

I have not been able to get it to play in docker using plex. the web page works, i get a channel list but it won't stream

updated

repo: cabernetwork/cabernet


text:
🛑 CBTB Coffee House Shop is down

In c7a972d, CBTB Coffee House Shop (https://shop.cbtb.coffee/) was down:

HTTP code: 403
Response time: 1250 ms

Resolved: CBTB Coffee House Shop is back up in 9f7fa24.

repo: cachetech/service-status


text:
🛑 CBTB Coffee House Shop is down

In 8f64355, CBTB Coffee House Shop (https://shop.cbtb.coffee/) was down:

HTTP code: 403
Response time: 1021 ms

Resolved: CBTB Coffee House Shop is back up in 13a7169 after 46 minutes.


text:
Defaultrefererfix

Relaxing getReferer() visibility to 'protected' in order to unit test it
directly; replacing several test methods for referer check with
redirect/forward with a single method that tests the getReferer()
returned value in various situations

that sounds nice to me, @valeriolopes! thanks for doing this.
I'll wait a few more time to get more reviews before merge it.

Done as @lucascs asked, breaking down the test method into more specific methods.
Besides, added a more safe check on the referer path, because the previous condition doesn't cover all cases:
return refererPath.startsWith(ctxPath) ? refererPath.substring(ctxPath.length()) : refererPath;
If the context path strings appears in the beggining of the url path but it is not the context path (ex: context path = /vrap; url path = /vrapanything/test), this would return anything/test, a wrong path. It's a very specific condition but it can occur.
In order to remove the context path from the url, it should appear in the beggining of the url path in one of those conditions: 1) being followed by a '/' and anything (or nothing) after it; 2) be equal to the url path (nothing should come after it).In this case, we return what's after the context path. This covers all cases:
Context path = /ctx
http://vraptor.com/ctx - return ""
http://vraptor.com/ctx - return "/"
http://vraptor.com/ctxtest/tef/ctx/test/ctx - return /ctxtest/tef/ctx/test/ctx
http://vraptor.com/ctx/test/ctx/ok - return /test/ctx/ok
I thought using a regexp to test this  - ^/ctx(/.*|$) would do it - but thought again because I would have to compile the regex every time the referer was requested since the context path is not a fixed value (well.. it's a fixed value after the web app is started but I would have to capture that info somewhere and save it.. to much work). Ended up staying with plain old string and it char array.

Done

thanks!

YW -- It was an honor giving this tiny contribution to vraptor. If you guys need more hands to help I'll be around (maybe fixing bug reports or whatever else). Is there any technical documentation of the framework or the code is the only (and prob the best) document?

that was a nice contribution... not tiny at all :+1:

If you guys need more hands to help
I'll be around (maybe fixing bug reports or whatever else)

great! if you want to, you can check our issues

Is there any technical documentation of the framework
or the code is the only (and prob the best) document?

take a look on http://www.vraptor.org/en/docs/one-minute-guide/

From the framework user perspective I have a good knowledge; I meant something about its internals (how it is organized from inside), but since the code is well structured with some study one should learn about it.
BTW, how do you guys organize these issues?You just pick up one issue, branch it, do whatever you want and then submit it for review?

You can use our test coverage to get into the framework, it's a very effective
way to learn about a project :) About the issues, yes, anyone can choose one
issue that is not assigned, implement it in a fork and send us a PR for review.

authors: Turini valeriolopes


text:
Still Canvas Crash on selecting Tokens ....

"Still" as i have write about it on the Issue#4 last comment .... on this error log it was an full foundry freeze after selecting an Token (not always, but on 4 times from 5)...
Now it works better , but get still Cancas Freezes sometimes on select an token
Log :
libWrapper-wrapper.js:513 Uncaught TypeError: constrainedTokenBorder.toPolygon is not a function [Detected 4 packages: tokenvisibility, lib-wrapper, perfect-vision, levels]     at Area3d._targetWithinLimitedAngleVision (Area3d.js:418:42)     at Area3d.percentAreaVisible (Area3d.js:435:16)     at Area3d.hasLOS (Area3d.js:159:33)     at testLOSArea3d (visibility_los.js:246:17)     at DetectionModeBasicSight._testLOSDetectionMode (visibility_los.js:138:16)     at 🎁DetectionMode.prototype._testLOS#0 (libWrapper-wrapper.js:187:52)     at 🎁DetectionModeBasicSight.prototype._testPoint#perfect-vision (detection-mode.js:160:23)     at 🎁DetectionModeBasicSight.prototype._testPoint#0 (libWrapper-wrapper.js:187:52)     at foundry.js:40919:36     at Array.some (<anonymous>)     at DetectionModeBasicSight.testVisibility (foundry.js:40919:18)     at 🎁call_wrapped [as call_wrapped] (libWrapper-wrapper.js:507:22)     at 🎁DetectionMode.prototype.testVisibility#levels (wrappers.js:170:20)     at 🎁DetectionMode.prototype.testVisibility#0 (libWrapper-wrapper.js:187:52)     at 🎁call_wrapped [as call_wrapped] (libWrapper-wrapper.js:507:22)     at 🎁DetectionModeBasicSight.prototype.testVisibility#perfect-vision (detection-mode.js:140:28)     at 🎁DetectionModeBasicSight.prototype.testVisibility#0 (libWrapper-wrapper.js:187:52)     at CanvasVisibility.testVisibility (foundry.js:33566:39)     at 🎁call_wrapped [as call_wrapped] (libWrapper-wrapper.js:507:22)     at CanvasVisibility.testVisibilityCanvasVisibility (visibility_range.js:47:10)     at CanvasVisibility.visibilityWrapper (wrappers.js:132:25)     at 🎁CanvasVisibility.prototype.testVisibility#0 (libWrapper-wrapper.js:187:52)     at get isVisible [as isVisible] (foundry.js:45865:38)     at CanvasVisibility.restrictVisibility (foundry.js:33489:68)     at 🎁call_wrapped [as call_wrapped] (libWrapper-wrapper.js:507:22)     at 🎁CanvasVisibility.prototype.restrictVisibility#perfect-vision (visibility.js:46:20)     at 🎁CanvasVisibility.prototype.restrictVisibility#0 (libWrapper-wrapper.js:187:52)     at 🎁CanvasVisibility.prototype.refresh#perfect-vision (visibility.js:392:18)     at 🎁call_wrapper [as call_wrapper] (libWrapper-wrapper.js:591:14)     at 🎁CanvasVisibility.prototype.refresh#0 (libWrapper-wrapper.js:189:20)     at #update (foundry.js:41683:58)     at t.emit (ticker.min.mjs:8:622)     at e.update (ticker.min.mjs:8:3473)     at _tick (ticker.min.mjs:8:1482)

I think this is fixed in v0.4.0. If still an issue, please feel free to comment.

repo: caewok/fvtt-token-visibility


text:
data.alert required

Can you elaborate the following implementation:
https://github.com/caffeinalab/ti.goosh/blob/5e490fcae8dd9ccbd1e4900d70757edfa0b46e72/android/src/ti/goosh/IntentService.java#L117
Is the alert property meant to be the body property as seen here:
https://firebase.google.com/docs/cloud-messaging/http-server-ref#notification-payload-support
I'm confused why it is required. Can you put something in the docs for this or clarify here?

@Bertuzb Yes the alert property is meant to be the body of the notification. The module requires alert to keep compatibility with iOS


text:
[question] extend a module through another module

I was wondering but having a feeling that you can't but anyways,
Is there any to extend a module based on another module?
For example, adding relationships: You start of with a typical user model but then decide to split out the blog functionality into it's own module. But you are left with the issue of adding the relationship back to the blog within the user module.

I believe what you want are polymorphic relationships.

Thanks, I'll look into them.

repo: caffeinated/modules


text:
fixed text on the assistant page

misspelled word.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant kuzushi

repo: caido/documentation


text:
Generate coordinates on save / import

Hello there.
So I'm importing locations with django-import-export, which have a city, state and country. I use them as based_fields.
When I import them the location field is empty, though. No coordinates were computed. They only get computed if I manually enter the data again in the admin form.
Is there a way to let the coordinates compute on import? Also, how do I render the Google Maps widget in a view/html, so I can show the location on the map to visitors?
EDIT1: It seems to be enough to touch (as in: change value and change it back) one of the based_fields in the admin form for every other based_field to be considered for the computing of the coordinates. Am I assuming correctly that the computation of the coordinates is based on the javascript portion of this package?
EDIT2: I'm implementing a geocoding-step on save of a model now through the geocoder package. Trying to figure out right now how to use "def clean_???" to update the plain location fields coordinates on save.

So if anyone else might encounter this problem you can do it like this in the model class:
    def save(self, *args, **kwargs):
        if self.country and self.state:
            g = geocoder.arcgis(self.city + ", " + self.state.label + ", " + self.country.label)
        elif self.country and not self.state:
            g = geocoder.arcgis(self.city + ", " + self.country.label)
        else:
            g = geocoder.arcgis(self.city)
        if len(g.latlng) != 0:
            self.location = str(g.latlng[0]) + ", " + str(g.latlng[1])

        super(Location, self).save(self, *args, **kwargs)

Thanks for sharing your thoughts here!
Just to clarify:

Am I assuming correctly that the computation of the coordinates is based on the javascript portion of this package?

Yes. Coordinates only comes from client-side.
Although I think its time to add such functionality in the server-side. :)

You can use my code or something alike to accomplish this easily.

authors: Braintelligence caioariede

repo: caioariede/django-location-field


text:
fix: 🐛 fix nominatim address search

Due to a change in allowed URL formats, the nominatim OpenStreetMap search broke. This PR fixes it.
Background information

Issue and discussion on Nominatim: https://github.com/osm-search/Nominatim/issues/3134
Example of previous and now incorrect request and its result: https://nominatim.openstreetmap.org/search/?q=Augsburg&format=json

Merged since the only tests that failed are for Python 2.7 which are no longer supported by GitHub Actions

authors: caioariede wolfskaempf


text:
Example Extension

please provide an example extension or a tutorial in wiki

We do have an extension you can use for reference. It’s located at https://github.com/cairoshell/cairoshell/tree/master/Cairo Desktop/Extensions/CairoDesktop.Extensions.Places.ShellFolders
On Dec 27, 2018, at 5:25 AM, Sam Johnson <notifications@github.commailto:notifications@github.com> wrote:
Great idea, will do! The extension api is not close to finished so it will be a living document.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcairoshell%2Fcairoshell%2Fissues%2F222%23issuecomment-450123963&data=02|01||9d2b652795984ef7224108d66be5a487|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636815031375542291&sdata=UuCTKLCmZ%2BINWC3bN1k2w9fdsjK%2FfUafU8LntNelGrc%3D&reserved=0, or mute the threadhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGxXAUqzTW6Y5sx6CB3yIMbLs5eWl8Puks5u9KAggaJpZM4ZimeC&data=02|01||9d2b652795984ef7224108d66be5a487|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636815031375542291&sdata=udwpE0OPWZZHKTsZnA24h0%2B%2Bw2KuU3y13W%2FcWmbinLU%3D&reserved=0.

https://github.com/cairoshell/CairoExtensionSamples

authors: dremin furesoft josuave

repo: cairoshell/cairoshell


text:
DefaultPackageInstaller should select correct TFM

See code here https://github.com/mholo65/cake-server/blob/278d5128695b173165c695b7e476218fb4b90ef6/src/Cake.Bakery/Packaging/DefaultPackageInstaller.cs#L78

Use Cake.NuGet instead once it's pushed.

Solved in #23

repo: cake-build/bakery


text:
(maint) Update Cake.Wyam to 0.17.0

Fixes #56

@pascalberger damn you are good! This was on my list of things to do later. :D


text:
🛑 XMR Asia Servers is down

In f27e51f, XMR Asia Servers ($XMR_ASIA) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XMR Asia Servers is back up in 097abe4 after 17 minutes.

repo: cake-tech/upptime-cakewallet


text:
🛑 XMR Asia Servers is down

In 83b01fb, XMR Asia Servers ($XMR_ASIA) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XMR Asia Servers is back up in 7b2eeb4 after 7 minutes.


text:
🛑 XMR Asia Servers is down

In c967ebe, XMR Asia Servers ($XMR_ASIA) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XMR Asia Servers is back up in 35ae105 after 5 minutes.


text:
New feature request: setting LED clock brightness

Not sure if this is so new an addition to the Alexa devices newest generation where they added the LED clock.  I can set the brightness by speaking to the device or using the app.  But they don't have it as an option to set it in a routine.  So not sure if its available in the API or not?
I'd like to have the ability to set the LED brightness from node-red routines like turning it down to 1 at night and back up to 7 during the day.  I can't find any way to automate this yet.

Are you sure you cant do it in a routine?  You should be able to do a customised action and put in what you would normally say to alexa to get the brightness to change.  Then its just a case of triggering your routine from nodered.  It does have the side effect of alexa saying 'ok' when triggered, and I dont think there is a way to avoid, but it at least gives you an option to automate this.
Note: You are unlikely to get this feature added via an issue here - the core functionality is provided by the library linked below which would need to add support for this first.. (if its needed, see above)
https://github.com/Apollon77/alexa-remote

I've been searching online as well as having double checked.  It doesn't look like Amazon opened that up unless its hidden somewhere.  Other threads talking about it have said its not something you can set other than the slider in the app or speaking to the device.   There is no routine option I can find yet.  Could be its a new enough feature on the new devices its not fleshed out yet.  I'll look into custom actions.  I haven't ever used that and don't know how that works.   Also new enough to using Node Red and the github site I couldn't see where to post comments to the person who seemed to have taken over this node-red code that's now the cakebaked version.  Just throwing this out there.

So you dont have customised action in your alexa app then?  What country are you in?  Its definitely in UK & US.  Top option below when setting up a routine, see screenshot.

I have it.  I just said I've never used that feature before so I'd have to look into how to do something custom like this using it.  So far everything I've needed to do with Alexa is just triggering rules in my Hubitat hub or turning on/off a device in the smart home settings.  I only resorted to Node Red to set volumes and DND settings across 7 devices more easily by having it pick up a virtual switch being set in the hub then the Node Red flow sets volumes and DND settings across all the devices at night to lower everything then sets them higher again during the day.   Not sure if you saw my previous post on this thread about problems I've had with errors in this cakebaked code trying to set the Alarm volume.   But since I was here posting that I just threw in this comment about setting the LED brightness as well as that is something I would work into a flow like this.    If I can get it working via a custom routine line and have it have to speak out a response that would work, but not quite as clean as I'd like.

Not seen the alarm issue but it may work via a similar workaround.  Using a routine with cusomised action is a good workaround when there isnt direct support from the nodered module to do whatever.

invalid input: "{"option":"alarmVolume","value":{"device":"G091JJ0910440BRQ","volume":"40"}}"
I use the Alexa Echo node, pick the Alarm Volume, set it to a string 40 and pick one of the echo devices.  I get this error showing up in the debug node.   I tried googling using that feature and to see if any other posts popped up regarding it or problems and couldn't find anything.   I'll give it a shot using your suggestion of custom actions.  It may be next week till I have time to dig back into it.

I think to use the Custom option in Node Red I have to figure out how to pass in a JSON object?  I see the option to select custom in a node but its kind of free form for what you pass in.  Haven't experimented with it yet.   But I did just resolve the alarm volume problem.   It looks like the node-red node code is bugged in that you can only pass in a string value which causes the errors because it needs a number.  Trying environment variables that are numbers didn't work neither did the $abs(#) function which should return a number, it just puts a blank value in the input.    But, when you use the custom command in an Alexa command it tells you it needs a value from 1 to 10.   But in the Node Red code you need to send in a value from 1 to 100.   Setting the payload to a number like 50 and passing that in and setting the Alarm Volume to the msg.payload got past the errors and that is working now.

If you know how to structure the command in the node red node.  I've been trying at it for a couple hours.  Online examples are scarse and I've tried a few variations like setting the msg.payload or using the json option but keep getting errors. If you or anyone can tell me how to structure the json or payload string would help.  Or point me at some documentation that describes exactly what Alexa is looking for.
payload version:   (this gives me Invalid property expression: unexpected ' ' at position 14")
msg.payload={type: "speak", payload: { type: "regular", text: "set clock brightness to 1", devices: "XX91JJ09051603PR"}}
JSON version:  (this gives me unexpected token " at position 4)
[ { “id”: “3ff3c45d.20249c”, “type”: “alexa-remote-routine”, “z”: “c8594bdc.1ed9d8”, “name”: “”, “account”: “My Echos”, “routineNode”: { “type”: “speak”, “payload”: { “type”: “regular”, “text”: { “type”: “str”, “value”: “this is a test” }, “devices”: [ “XX91JJ09051603PR” ] } } } ]
JSON version 2:  (this gives me unexpected token 2 at position 2)
[{type: "speak", payload: { type: "regular", text: "set clock brightness to 1", devices: "XXF0071863430BD6"}}]

For the customised action routine workaround you shouldn’t need any Json setup.

Create routine in Alexa app using customised commands to do whatever you want. Test it works in the Alexa app.

In node red flow with an Alexa-remote routine node execute the routine. Should come up in the dropdown.

I tried that but I wasn't getting it to work the way I need.  I give the verbal commands from another room and the echos with the clocks I want set are in other rooms.  Saying something like "set brightness to 1 on bedroom echo" results in errors.  Maybe I haven't figured out the exact phrasing yet to do it from another room.   I also just wanted to keep all my alexa settings contained in a single node red flow since that was the point of this exercise.   I'm trying to add it as a node to this flow.

I'm out of town for a couple days and will pick this up later.  I found someone did a Hubitat custom alexa driver I'll look at, maybe with that I can do it, or at least figure out how to automate a custom command that I can move over to this flow.  This is just a fun project anyway, not really too important.  Thanks for helping.

For reference the routine I use has customised action with "Alexa, show front door on study echo show" which works ok.  Also tested "Alexa, set volume to max on lounge echo dot" and that worked too.  If you arent already make sure the 'From' part of the routine as the alexa device you are trying to set?  Screenshots below of the routine and node red routine node config.
Failing that maybe the brightness is special and wont work from customised routines :(

I'm familiar with making calls from one device to another including setting up one to talk to another one.  Just haven't gotten it to work with the new led brightness on this latest generation.  Also, was thinking it through and it wouldn't really work for me as a complete solution to have it issued from an alexa device as a custom command.  While I do give a verbal command to an alexa device to activate a routine that sets lights/blinds/heaters/xbox/sonos/etc. when going to bed that would work for lowering the led brightness in the bedroom for example.  But we don't give alexa commands on the other direction to turn on the home.  That happens via motion sensors, time of day, home vs away modes that trigger Hubitat rules.  I have virtual switches that get set in Hubitat that Node Red picks up and that is how I'm kicking off the node red alexa flows and that's how I'd be setting the led brightness back to a daytime level.

I use the above without talking to Alexa.
In my case I have a motion sensor which when triggered sends an mqtt msg, picked up in node red flow which then notifies me via Alexa talking and then starts the routine with customised action to show the camera view on my echo show.

Been trying all sorts of variations on setting the led brightness from a different device, all give "[device name] doesn't support that.  Only issuing the command directly to the device is the only thing that works "set brightness to X".    Things like set brightness to X on entertainment echo and other variations doesn't work.   But I did get it to work by making a routine that uses a timer and then set a custom routine "set brightness to X" from Entertainment Echo.
That means to dim/undim 2 devices at night and morning will take 4 different Alexa routines.  Not exactly an elegant or flexible solution that just works with everything else, but its workable for now.

authors: IanLauder peteakalad


text:
string to be encoded contains characters outside of Latin1 range

I get this error when polling a result (containing characters like ♫ and ♪) from my database:

Uncaught DOMException: Failed to execute 'btoa' on 'Window': The string to be encoded contains characters outside of the Latin1 range

I could fix the issue for me by replacing "btoa(string)" by "btoa(unescape(encodeURIComponent(string)))" using this google-result
Unfortunately I couldn't reproduce this error in a simple environment:
namespace App\Http\Livewire;
use Livewire\Component;
class Counter extends Component
{
    public $string;

    public function mount()
    {
        $this->string = '♪ ♫ ♫';
    }

    public function hydrate()
    {
        $this->string = '♪ ♫ ♫';
    }

    public function render()
    {
        return view('livewire.counter');
    }
}

<div wire:poll="$refresh">
    {!! $string !!}
</div>

Maybe somebody else has more luck, or my fix helps others experiencing the same error.

I'd love a PR for that fix if it works for you

Issue is fixed

authors: calebporzio erikscheepers

repo: calebporzio/livewire


text:
Allow users to specify delimiter when copying to csv file

Currently, .to_csv() creates a comma-delimited file. But PostgreSQL's COPY TO statement allows users to specify any one-byte character (e.g., tab) via the DELIMITER parameter. We might add this option, but keep , as the default delimiter.
TODO:

[ ] Add a delimiter kwarg to .to_csv()
[ ] Write tests to confirm default behavior and example of specifying delimiter
[ ] Update docs

This is done!

authors: gordonje palewire


text:
Typescript type error in component returned by withStyles()

When using withStyles() hoc in typescript, I am getting the following error when trying to use the returned component:
Type '{}' is not assignable to type 'IntrinsicAttributes & IntrinsicClassAttributes<App> & Readonly<{ children?: ReactNode; }> & Reado...'.
  Type '{}' is not assignable to type 'Readonly<WithStyles<"main">>'.
    Property 'classes' is missing in type '{}'.

[x] I have searched the issues of this repository and believe that this is not a duplicate.

It appears this change to the type definition might be related to this issue.
Expected Behavior

Given the App component code below, I should be able to use the component <App /> without the type error as I did in 1.0.0-beta.10.
Current Behavior

Given the App component code below, trying to use <App /> results in the aforementioned error.
The Code
import * as React from 'react';
import { withStyles } from 'material-ui/styles';

const styles = {
    main: {
        marginTop: 48,
        padding: 10,
    },
    foo: {
        margin: 0,
    },
};

interface Props {
    message: string;
};

type ClassNames = { classes: { [className in keyof typeof styles]: string } };

class App extends React.Component<Props & ClassNames> {
    render() {
        const { classes, message } = this.props;
        return (

                    Hello World! {message}

        );
    }
}

export default withStyles(styles)(App);

Context

The code worked fine in 1.0.0-beta.10, when I upgraded to 1.0.0-beta.12 I got the type error.
In the code snippet provided I used the keyof typeof styles trick so that I would not need to define a list of class names twice (I strongly dislike the repetitiveness). I have also tried other variations:
type ClassNames = WithStyles<keyof typeof styles>;

and doing it the more common way (as seen in styles.spec.tsx):
type ComponentClassNames = 'main' | 'foo';
type ClassNames = WithStyles<ComponentClassNames>;

I still get the same error.
It seems the previous type definition would return a component whose props type would be StyledComponentProps which has an optional classes property. The new definition...
<P, C extends React.ComponentClass<P & StyledComponentProps<Names>>>(
    component: C
  ): C;

...returns the same type C as the component, this means that passing ClassNames which is not marked optional propagates to the returned component. I see mentioned here the use of Partial<> which I think it an unsightly hack.
Your Environment

Tech
Version

Material-UI
1.0.0-beta.12

React
15.6.1

browser
Chrome 61.0.3163.100

@cfilipov when decorating a component class you should use StyledComponentProps instead of WithStyles, and if in strict type checking mode you need to use the non-null assertion operator ! to extract the fields of classes. This is a compromise to allow the use of withStyles as a class decorator. Class decorators in type script suffer from the limitation that their return type must match the argument type. The only options given this limitation are

don't support using withStyles as a class decorator
require that you pass a dummy classes prop when constructing an element of the decorated component type (#8267)
require that classes be considered nullable inside the component, forcing you to use the ! operator when accessing its fields (the current compromise)

I would highly recommend that if your component has no state you use a stateless functional component, which will require fewer type annotations and be more type safe:
export default withStyles(styles)<Props>(({ classes, message }) => (

      Hello World! {message}

)

I see mentioned here the use of Partial<> which I think it an unsightly hack.

If you read my followup to that comment you'll see that Partial<> is not required.

If you read my followup to that comment you'll see that Partial<> is not required.

I saw your comment regarding Partial<>. Using StyledComponentProps essentially amounts to the same thing (it's using Partial<> in that definition). My gripe with that is now class names must be accessed with ! (as you mentioned). I think passing a dummy classes prop or requiring the use of ! are both poor compromises.
To clarify, I guess the root issue I am having here is the choice to introduce a regression to the hoc in an effort to work around a limitation of an experimental feature of typescript. I admit to some bias since I don't care for decorators, whereas others clearly do, but the tradeoff here doesn't make sense to me.

@cfilipov my first refactor of the withStyles typings was to choose option (1), i.e. make the typings completely correct for both class and function components, at the expense of using withStyles as a class decorator. I then got feedback that using the decorator syntax was a popular request, so I switched to option (3). I'm happy to revisit that decision; I too would prefer type safety to supporting decorators in their current semifunctional state.

Using StyledComponentProps essentially amounts to the same thing (it's using Partial<> in that definition).

It should be noted that no matter what, you're going to need to specify something like Props & StyledComponentProps when using class components.

Yeah, I understand the desire to support a popular request like this. I want to use decorators too, but I keep running into many issues with them every time I do (outside of mui) so I personally decided to not use them until they are ready.
It sounds like you share my concern and I don't have much more to add so hopefully other people can provide feedback in this direction to help influence it.

I switched to beta.13 from beta.10 to see if anything had changed and Yes this is a real issue. To throw my 2 cents in here, for me, decorators are experimental. They obviously could be changed in the future. And until then I would fully support the 100% accurate way. I would much rather have coherent type safety to hacking my types to make things work.

#8550 looks like further evidence that people are confused by this, and we should consider not supporting @withStyles() as a decorator.

This is what it would look like to "decorate" a class if we made the typings correct:
type NonStyleProps = {
  text: string
}

type styles = {
  root: {
    backgroundColor: 'red',
  }
}

const DecoratedComponent = withStyles(styles)(
  class extends React.Component<NonStyleProps & WithStyles<'root'>> {
    render() {
      const { classes, text } = this.props;
      return (

          {text}

      );
    }
  }
);

@pelotom I have yet to move forward from beta.10 because of this issue. I made comment about the styling of a class with Redux's connect method before. I think its relatively easy and robust. in  #8059 the third comment is myself with the types.

@pelotom Thank so much for educating us on this issue. I am a big user of TS decorators but in that instance, I would be happy for withStyles to drop its decorating support  in order to have better type safey.

we should consider not supporting @withStyles() as a decorator (in TypeScript).

@pelotom I'm personally in favor of this change. @sebald What do you want to do here?

It's a simple change; I went ahead and opened a PR in case you want to go with it 🙂

@pelotom would the typings still work if I used them like this?
interface IStyles {
    // styles interface
}
interface IHeaderInfoStyles {
    classes: any;
}
interface IHeaderInfoProps {
    // properties resulting from dispatches
}
interface IHeaderInfoInjectedProps {
   // props injected from parent if any
}
interface IHeaderInfoDispatchProps {
    // dispatches
}
interface IHeaderInfoState {
    // your state for the class
}

type HeaderInfoProps = IHeaderInfoProps & IHeaderInfoInjectedProps & IHeaderInfoDispatchProps & IHeaderInfoStyles;

class HeaderInfo extends Component<HeaderInfoProps, IHeaderInfoState> {

export const HeaderInfo_container = withStyles<IHeaderInfoInjectedProps, IStyles>(styles)(
    connect<IHeaderInfoProps, IHeaderInfoDispatchProps, (IHeaderInfoInjectedProps & IHeaderInfoStyles)>(mapStateToProps, mapDispatchToProps)(HeaderInfo),
);

@marcusjwhelan withStyles no longer takes 2 type parameters, and you shouldn't have to provide a type parameter for styles (it can be inferred from styles). You should instead be able to write
withStyles(styles)<NonStyleProps>(...);

If you give the types for mapStateToProps and mapDispatchToProps I might be able to show you what this would look like for your example.

tl;dr; Let's do the changes and see what the backlash is, I guess 👷🏻

@oliviertassinari @pelotom ¯_(ツ)_/¯ I do not use decorators, so personally, I really don't care about this change, because I am not affected. But it seems like a lot of people do care about this "feature". That's why we added it in the first place. That's IMHO what has priority here.
I am very happy with the changes of withStyles, but when you take a look at other more functional libraries, like ramda or recompose, the typings aren't that strict, neither are they super type-safe. Often times you have to pass in a generic, which represents the return value of a function. Not pretty but it will work for a 99.9% of the users.
Why can't we bring back the old typings that worked for the people using decorators? Because it did have two generics, we may be able to have both typings side by side.
Also, I am a bit confused what peoples issues with decorators are (regarding "not working"). Libs like Angular and https://nestjs.com/ make heavy use of them after all.

@sebald

Why can't we bring back the old typings that worked for the people using decorators? Because it did have two generics, we may be able to have both typings side by side.

I'm not sure what you mean. There was never any typing that allowed people to use decorators painlessly. The first implementation suffered from #8267, which was that you couldn't construct an element of a decorated component without passing a dummy classes prop, e.g.

authors: HenrikBechmann cfilipov chrislambe doppio eps1lon iamjem isman-usoh lookfirst marcusjwhelan nishmeht7 oliviertassinari otroboe parkenergy pchodak pelotom sebald svachmic valoricDe valorize wcandillon yehudamakarov

repo: callemall/material-ui


text:
[SvgIcon] Fix react@16 issue with focusable

Fixes #8092

@NLincoln Thank

authors: NLincoln oliviertassinari


text:
Configurable scroll container

See #50

Using this version of Jump going forward until container support is merged into main

Any chance of getting this merged in? Can we do something to help with this?

I would love to see this merged.
One potential block is that master was updated to use ESLint a few days after this PR was created. Once merged, ESLint is complaining, but the fixes are simple:

Add a space after all function names
Add a space after switch keywords

@callmecavs Are there any plans to merge this and support this feature? Looks like there's quite a bit of interest.

any reason to hesitating about merging this PR?

any updates?

authors: MilllerTime Sam-Hoult dehypnosis josdejong jprodrigues70 niksy scottyeck


text:
feat: implement Spatial API

Summary:
This PR is still WIP

Try to cross-reference the WebXR/OpenXR API to see if we can find a middle ground between them and visionOS specifics. It would be nice to be able to use this API across XR devices.

@matthargett Looks like equivalent for WebXR is navigator.xr.requestSession() we can rename the API to XR and methods to:

Spatial.openImmersiveSpace(ID) -> XR.requestSession(ID)
Spatial.dismissImersiveSpace() -> XR.endSession()

WebXR returns session object and it ends the session by calling .end() on this object. I think the closest we can get is XR.endSession()

authors: matthargett okwasniewski

repo: callstack/react-native-visionos


text:
Prepare release 1.1 for location-verification + README + CHANGELOG

What type of PR is this?

correction
subproject management

What this PR does / why we need it:
Prepare location-verification for r1.1
Some fixes after review
Update README (for the 3 APIs)
Update CHANGELOG (for location-verification + placeholders for the others)

Before creating the r1.1 release we have to:

Merge the pending PRs for geofencing (maybe with the exception of the test plan)
Create a PR for geofencing adjusting versions for r1.1
Merge the PR for location-retrieval for r1.1
Merge this PR for location-verification + README/CHANGELOG for r1.1

repo: camaraproject/DeviceLocation


text:
Folder structure for release Branches

the main branch has a new folder structure, with subfolders for each APIs. The same structure is not adopted in the release branches. how can we fix this?

A proposal based on https://github.com/camaraproject/Commonalities/issues/66 :
release-0.8.1: it is ok: it still has the old folder structure without subfolder for each API in the Family. This is correct because the branch is a snapshot done when the Edge Cloud Family had that folder structure.
release-0.9.0, 1.0.0, 2.0.0: currently they are branches used for development while according to https://github.com/camaraproject/Commonalities/issues/66 these branches should be used as snapshot from Main when we decide to deliver a stable version.
I suggest to:

rename these branches with the prefix "dev-", for example: "dev-release-0.9.0". It is up to who is using that branches to restructure them according to the new folder structure.
create new PRs to push the relevant developed code into Main

@FabrizioMoggio  Yes, as agreed in the call 12-12-23 I will:

delete release-1.0.0 and release-2.0.0
rename release-0.9.0 to dev-release-0.9.0

...however, I don't have permissions to do this as they are 'protected branches' (hence require admin permissions). @MarkusKuemmerle please can you advise..?

@MarkusKuemmerle, @gunjald I think that also release-0.9.0 can be deleted at this point in time

@Kevsy @FabrizioMoggio: On request of @Kevsy I have:

deleted release-1.0.0 and release-2.0.0
renamed release-0.9.0 to obsolete-0.9.0 (that will allow code owners to rename/delete it as needed)

Please be aware of updating-a-local-clone-after-a-branch-name-changes in case you have local clones.

authors: FabrizioMoggio Kevsy hdamker

repo: camaraproject/EdgeCloud


text:
Prepare release r1.1

What type of PR is this?
Add one of the following kinds:

subproject management

What this PR does / why we need it:
Prepare the release r1.1:

[x] Update CHANGELOG.med
[x] Update README.md
[x] Set versions in quality-on-demand and qos-profiles
[x] Set version in qos-provisioning (check all "wip", including event version)
[x] Update API Readiness Checklists

Which issue(s) this PR fixes:

Fixes #334
Special notes for reviewers:
Still in draft mode ... please review the initial content within CHANGELOG.md

@RandyLevensalor @jlurien have a look on the r1.1 section in CHANGELOG.md.

Release PR is almost complete ... just waiting for the merge of #299 and the ability to set the version in the new API qos-provisioning to 0.1.0-rc.1

Replaced all "wip" in qod-provisioning.yaml:

in version and server field according to guidelines
in org.camaraproject.qod-provisioning.vwip.status-changed to org.camaraproject.qod-provisioning.v0.status-changed.

There is no specific guideline for initial API versions
The event version should be decoupled from the API version (as the API can have breaking changes, but keep the event structure stable) ... so if the event structure will change with a later initial API version we can still then use another number.
BTW: I would not reset to wip as long as there is no breaking change to the event structure within a PR

in https://api.example.com/qod-provisioning/v0.1/device-qos/... set to the current one, but as it is only an example, wouldn't matter too much if we miss this one going forward

@camaraproject/quality-on-demand_maintainers @camaraproject/release-management_maintainers
The release PR for r1.1 is now complete and ready for review.
Note: #325 has to be merged first before this PR can be merged and the release created.

repo: camaraproject/QualityOnDemand


text:
Parser for includes.

Depending on how we comment an include :
//`include foo
// `include bar

the script for dependency tracking consider that foo is a dependency, but not bar. When I expect the two to not be dependencies (as they are commented).
I guess connectal used the first form of comment as a feature to signal weird dependies invisible to bluespec but visible to connectal?
The code involved is in bsvdependencies.py:
 m = re.match('//`include "([^\"]+)"', line)
 m1 = re.match('//`include(.*)', line)
 if m:
                iname = m.group(1)
                if iname in abspaths:
                    iname = abspaths[iname]
                else:
                    iname = 'obj/%s' % iname
                includes.append(iname)

I am not sure why this special case. I don't have the full picture.
If connectal really need to do this kind of commented include that should not be seen by BSV, perhaps connectal could use a special form of include like `includeConnectal, that would be in the comment section?

Hi threonorm, Jamey is on vacation with limited email access, so your question may not be answered in time. It sounds like the error is due to some hacky-ness in bsvdependencies.py , would you be able suggest a fix for this? I think you are correct that none of these two cases should generate a dependency.

Hi hanw, thanks for your answer!
I have a "fix" where I just consider every commented dependency to be not a dependency, this work for my use of the bsvdependencies functions, but I suspect that Jamey uses it in a different way somewhere else where he actually wants to keep this feature. (The way the code is written make me believe that this is really a feature)
For this reason, I don't want to pull request yet, waiting for his opinion is definitely a good idea :).

I guess it would be less Jaclyn if bsvpreprocess returned a list of included files as well as the expanded source code. Do you have time to make that change? Then it could ignore all commented out includes.

In case you did not see the comments I made in one of the chat channels:
I think this is an artifact of the interaction between bsvpreprocess and
bsvdepend. It's a bit too hackish, now, so probably it would be better if
bsvpreprocess returned a list of the included files along with the
preprocessed text and then we do not have to treat commented out includes
specially.
Either that, or we need a much more unique tag for the commented includes.
How about a commented out attribute?
// (* included_file="filename.bsvi" *)
It's too bad the BSV compiler does not support the equivalent of C/C++
#line directive, which is used for just this purpose.
If you have a chance to make a pull request along either of these lines I
would greatly appreciate it.
Happy holidays!
On Fri, Dec 2, 2016 at 3:03 PM threonorm notifications@github.com wrote:

Hi hanw, thanks for your answer!
I have a "fix" where I just consider every commented dependency to be not
a dependency, this work for my use of the bsvdependencies functions, but I
suspect that Jamey uses it in a different way somewhere else where he
actually wants to keep this feature. (The way the code is written make me
believe that this is really a feature)
For this reason, I don't want to pull request yet, waiting for his opinion
is definitely a good idea :).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cambridgehackers/connectal/issues/132#issuecomment-264549277,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACU3s-ktGy7VqAi3VAL82uMkgZU-4Kluks5rEHmjgaJpZM4LC4WU
.

Hello Jamey,
I am not sure I understand the problem properly : I don't understand what is
this special kind of include for and where/what it used for. (What are those include that are commented, but still considered as include?)
Though if abstractly speaking you just need a special kind of include, only
seen by connectal build system, and added by connectal automatically somehow, I
think I agree with your second suggestion, I can modify bsvdependencies to
special pick something like //CONNECTALINCLUDE "nameoffile"
I can definitely make the one line change in bsvdependencies, but I would
break everything by doing so, because I don't know where I should  change
things as well. (I guess some script add those special include for connectal
somewhere : I think those special include are not hand written, are they ? And
if they are, it means that I will break every project that is using them.).
Thomas
Excerpts from Jamey Hicks's message of 2016-12-30 08:10:02 -0500:

In case you did not see the comments I made in one of the chat channels:
I think this is an artifact of the interaction between bsvpreprocess and
bsvdepend. It's a bit too hackish, now, so probably it would be better if
bsvpreprocess returned a list of the included files along with the
preprocessed text and then we do not have to treat commented out includes
specially.
Either that, or we need a much more unique tag for the commented includes.
How about a commented out attribute?
// (* included_file="filename.bsvi" *)
It's too bad the BSV compiler does not support the equivalent of C/C++
#line directive, which is used for just this purpose.
If you have a chance to make a pull request along either of these lines I
would greatly appreciate it.
Happy holidays!
On Fri, Dec 2, 2016 at 3:03 PM threonorm notifications@github.com wrote:

Hi hanw, thanks for your answer!
I have a "fix" where I just consider every commented dependency to be not
a dependency, this work for my use of the bsvdependencies functions, but I
suspect that Jamey uses it in a different way somewhere else where he
actually wants to keep this feature. (The way the code is written make me
believe that this is really a feature)
For this reason, I don't want to pull request yet, waiting for his opinion
is definitely a good idea :).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cambridgehackers/connectal/issues/132#issuecomment-264549277,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACU3s-ktGy7VqAi3VAL82uMkgZU-4Kluks5rEHmjgaJpZM4LC4WU
.

authors: hanw jameyhicks threonorm

repo: cambridgehackers/connectal


text:
Unhandled characters in build info arg: 'MP1

Hello, im getting a weird error, something about MultipleProcessSupport flag?
here is the log
0x180000000`
thread 'main' panicked at src/cpp/module.rs:873:36:
Unhandled characters in build info arg: 'MP1...'
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Im running the script on ubuntu 22.04 and rustc 1.74.0

even if i try avoid getting panicked, another error comes up
Unhandled characters in build info arg: 'O14...'

Hey there, I've implemented a fix for /MP compiler options in commit 9b61f77, which should resolve your first issue. The second issue seems a little odd, does it still happen after the aforementioned fix? If so, is this PDB file publicly available so that I can debug it locally? The /O14 flag isn't documented, which you can see here: https://learn.microsoft.com/en-us/cpp/build/reference/o-options-optimize-code?view=msvc-170

Hello, first of all thanks for the fast response, you are right after fixing the first error now i get a different one
not yet implemented: arg switch 'Zf...'
please ignore /O14 not sure how i got that error
unfortunately the pdf is not public

No problem, if you don't mind reporting on any missing build info arg support in here, then I'll do what I can to get them implemented. I have added support for the /Zf option in commit 521a802.

sure, gotta catch them all i guess?
next one is
Unhandled characters in build info arg: 'experimental'

ok, next one
Unhandled characters in build info arg: 'experimental:deterministic'

OK that one should be fixed with commit 86a5d79.

next
Unhandled characters in build info arg: 'GR-3...'

That's a strange one because it doesn't seem to follow the documentation of the /GR option as specified here: https://learn.microsoft.com/en-us/cpp/build/reference/gr-enable-run-time-type-information?view=msvc-160
I've made a change that includes the build info args when an unexpected character is encountered in commit 2ff0ba3. Could you include the entire new error message so that I can verify the context and ensure it's not a parsing error?

the full error is like the others
thread 'main' panicked at src/cpp/module.rs:825:40:
Unhandled characters in build info arg: 'GR-3...'
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I think your local copy might be out of date. Could you verify that your src/cpp/module.rs has the same message string as the repository's at line 825? https://github.com/camden-smallwood/pdb-decompiler/blob/main/src/cpp/module.rs#L825

do you have telegram? i found the GR-3 issue i think

Yes I do, my account is @camdensmallwood

i seem to be having a similair issue but with source-charset:utf-8 here is the log:
Running target/release/pdb-decompiler --out=outp --pdb=fnaf9-Win64-Shipping.pdbthread 'main' panicked at 'Unhandled characters in build info arg: 'source-charset:utf-8'; Data: "-Zc:inline -nologo -Oi -c -Gw -Gy -Zm1000 -wd4819 -D_CRT_STDIO_LEGACY_WIDE_SPECIFIERS=1 -D_SILENCE_STDEXT_HASH_DEPRECATION_WARNINGS=1 -D_DISABLE_EXTENDED_ALIGNED_STORAGE -source-charset:utf-8 -execution-charset:utf-8 -Ob2 -Ox -Ot -GF -errorreport:prompt -D_HAS_EXCEPTIONS=0 -Z7 -MD -bigobj -fp:fast -Zo -Zp8 -we4456 -we4458 -we4459 -wd4463 -we4668 -wd4244 -wd4838 -ID:\BuildAgent\work\FNAF9\Engine\Source -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Launch\Private -ID:\BuildAgent\work\FNAF9\Engine\Source\Developer\DerivedDataCache\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\TraceLog\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Core\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\CoreUObject -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\CoreUObject\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\Engine -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Engine\Classes -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Engine\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\NetCore -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Net -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Net\Core\Classes -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Net\Core\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\ApplicationCore\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\RHI\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Json\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\SlateCore -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\SlateCore\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\InputCore -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\InputCore\Classes -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\InputCore\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\Slate -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Slate\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\ImageWrapper -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\ImageWrapper\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Messaging\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\MessagingCommon\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\RenderCore\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Analytics -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Analytics\AnalyticsET\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Analytics\Analytics\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Sockets\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Net\Common\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\AssetRegistry -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\AssetRegistry\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\EngineMessages -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\EngineMessages\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\EngineSettings -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\EngineSettings\Classes -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\EngineSettings\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\SynthBenchmark\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\Renderer -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Renderer\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\GameplayTags -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\GameplayTags\Classes -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\GameplayTags\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\DeveloperSettings -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\DeveloperSettings\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\PacketHandler -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\PacketHandlers -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\PacketHandlers\PacketHandler\Classes -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\PacketHandlers\PacketHandler\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\PacketHandlers\ReliabilityHandlerComponent\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\AudioPlatformConfiguration -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\AudioPlatformConfiguration\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\MeshDescription -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\MeshDescription\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\StaticMeshDescription -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\StaticMeshDescription\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\PakFile\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\RSA\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\NetworkReplayStreaming -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\NetworkReplayStreaming\NetworkReplayStreaming\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\PhysicsCore -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\PhysicsCore\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\Chaos -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Experimental -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Experimental\Chaos\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Experimental\ChaosCore\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\ThirdParty\Intel -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Experimental\Voronoi\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\ThirdParty -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\SignalProcessing\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\AudioExtensions -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\AudioExtensions\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\AudioMixerCore\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\PropertyAccess -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\PropertyAccess\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\ClothingSystemRuntimeInterface -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\ClothingSystemRuntimeInterface\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\AudioMixer -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\AudioMixer\Classes -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\AudioMixer\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Developer -ID:\BuildAgent\work\FNAF9\Engine\Source\Developer\TargetPlatform\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\AnimationCore -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\AnimationCore\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\MoviePlayer -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\MoviePlayer\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Networking\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Projects\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\SandboxFile\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\Serialization -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Serialization\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Cbor\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\Overlay -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Overlay\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\PreLoadScreen\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\InstallBundleManager\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\HeadMountedDisplay -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\HeadMountedDisplay\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\AugmentedReality -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\AugmentedReality\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\MRMesh -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\MRMesh\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\MediaUtils -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\MediaUtils\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Media\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\ClothingSystemRuntimeNv -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\ClothingSystemRuntimeNv\Public -ID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Inc\ClothingSystemRuntimeCommon -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\ClothingSystemRuntimeCommon\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Developer\AutomationController\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Developer\TaskGraph\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\SlateNullRenderer\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\SlateRHIRenderer\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\Launch\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\Runtime\SessionServices\Public -ID:\BuildAgent\work\FNAF9\Engine\Source\ThirdParty\PhysX3\PxShared\include -ID:\BuildAgent\work\FNAF9\Engine\Source\ThirdParty\PhysX3\PxShared\include\cudamanager -ID:\BuildAgent\work\FNAF9\Engine\Source\ThirdParty\PhysX3\PxShared\include\filebuf -ID:\BuildAgent\work\FNAF9\Engine\Source\ThirdParty\PhysX3\PxShared\include\foundation -ID:\BuildAgent\work\FNAF9\Engine\Source\ThirdParty\PhysX3\PxShared\include\pvd -ID:\BuildAgent\work\FNAF9\Engine\Source\ThirdParty\PhysX3\PxShared\include\task -ID:\BuildAgent\work\FNAF9\Engine\Source\ThirdParty\PhysX3\PhysX_3.4\Include -ID:\BuildAgent\work\FNAF9\Engine\Source\ThirdParty\PhysX3\PhysX_3.4\Include\cooking -ID:\BuildAgent\work\FNAF9\Engine\Source\ThirdParty\PhysX3\PhysX_3.4\Include\common -ID:\BuildAgent\work\FNAF9\Engine\Source\ThirdParty\PhysX3\PhysX_3.4\Include\extensions -ID:\BuildAgent\work\FNAF9\Engine\Source\ThirdParty\PhysX3\PhysX_3.4\Include\geometry -ID:\BuildAgent\work\FNAF9\Engine\Source\ThirdParty\PhysX3\APEX_1.4\include -ID:\BuildAgent\work\FNAF9\Engine\Source\ThirdParty\PhysX3\APEX_1.4\include\clothing -ID:\BuildAgent\work\FNAF9\Engine\Source\ThirdParty\PhysX3\APEX_1.4\include\nvparameterized -ID:\BuildAgent\work\FNAF9\Engine\Source\ThirdParty\PhysX3\APEX_1.4\include\legacy -ID:\BuildAgent\work\FNAF9\Engine\Source\ThirdParty\PhysX3\APEX_1.4\include\PhysX3 -ID:\BuildAgent\work\FNAF9\Engine\Source\ThirdParty\PhysX3\APEX_1.4\common\include -ID:\BuildAgent\work\FNAF9\Engine\Source\ThirdParty\PhysX3\APEX_1.4\common\include\autogen -ID:\BuildAgent\work\FNAF9\Engine\Source\ThirdParty\PhysX3\APEX_1.4\framework\include -ID:\BuildAgent\work\FNAF9\Engine\Source\ThirdParty\PhysX3\APEX_1.4\framework\include\autogen -ID:\BuildAgent\work\FNAF9\Engine\Source\ThirdParty\PhysX3\APEX_1.4\shared\general\RenderDebug\public -ID:\BuildAgent\work\FNAF9\Engine\Source\ThirdParty\PhysX3\APEX_1.4\shared\general\PairFilter\include -ID:\BuildAgent\work\FNAF9\Engine\Source\ThirdParty\PhysX3\APEX_1.4\shared\internal\include -I"C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\INCLUDE" -I"C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.2\include\um" -I"C:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\ucrt" -I"C:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\shared" -I"C:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\um" -I"C:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\winrt" -FID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Shipping\Engine\SharedPCH.Engine.ShadowErrors.h -YuD:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Shipping\Engine\SharedPCH.Engine.ShadowErrors.h -FpD:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Shipping\Engine\SharedPCH.Engine.ShadowErrors.h.pch -FID:\BuildAgent\work\FNAF9\fnaf9\Intermediate\Build\Win64\fnaf9\Shipping\Launch\Definitions.Launch.h -TP -GR- -W4 -showIncludes -X"', src/cpp/module.rs:1211:32 note: run withRUST_BACKTRACE=1 environment variable to display a backtrace

authors: MSeba1 Tamashh camden-smallwood

repo: camden-smallwood/pdb-decompiler


text:
FUSETOOLS2-1465 - fix logging mechanism

the file wasn't created. It seems that the java.io.tmpdir wasn't
replaced. So migrated to log4j2
There is a compatibility layer which allows to read log4 1 files but
well as I was at it, it also allows to use a more advanced mechanism -
rolling files and a better feedback on what is happening to investigate.
Signed-off-by: Aurélien Pupier apupier@redhat.com

we hopefully use the version of log4j without CVE?

we hopefully use the version of log4j without CVE?

yes https://github.com/camel-tooling/camel-debug-adapter/blob/9db8720b4b9f8abe05f2606a717090818d34a2fd/pom.xml#L124

authors: apupier lhein

repo: camel-tooling/camel-debug-adapter


text:
how to add different SD Checkpoints?

Hello Camenduru,
Thanks a lot for the Colab Collection, it's a really pleasant experience, especially for those without good graphics cards.
I wanted to run SD with different checkpoints, in detail DreamShaper3.3(HuggingFace|CivitAI) and DungeonsAndDiffusion(HuggingFace|Checkpoint)
(not both at the same time)
i tried editing a notbook and changed the links for the *.ckpt, but that did not work :/
Any easy way to get a specific checkpoint working without the need to download it during a running Notebook?
Cheers!

afaik there's a civitai extension tab, go to that tab on webui, and search for the model you need.

make sure for huggingface model, you need to right click that arrow beside the lfs image, then click copy link address for the actual link

CivitAI down

authors: Surlix etherealxx megazaz80

repo: camenduru/stable-diffusion-webui-colab

license: Unlicense


text:
Deploying to GKE with LoadBalancer results in 404

I've deployed to my GCE /  GKE environment with ./deploy.
After after everything is up, I can proxy to all instances.
But if I deploy the Nginx ingress over tools/ingress/init.sh I'm getting first a 400 error in the UI.
This could be solved with changing the service type from ClusterIP to NodePort for all services.
Now the status looks good and I can reach my test domain grafana.example.com
But I get a 404 error for all files except the initial html document.
Any idea?

Hi @khaefeli, sorry for the late response. Have to do more tests on Google Cloud. I'm using AWS and didn't test it much on Google Cloud. I'll set a cluster and test it in the next couple of weeks.

authors: camilb khaefeli

repo: camilb/prometheus-kubernetes


text:
Create Database

1 hr

Didn't create the database but setup the backend (just the expressjs/node) with eslint. This should enable Atlas to be setup later after later discussion.

authors: jkailee rhtakaha


text:
fix(sks): module error when keycloak is disabled

The keycloak_admin_password output can't be set when keycloak is disabled
because the kubernetes secret doesn't exist.
This solution doesn't rely on whether the secret exists or not, but on whether
keycloak is disabled in the app_of_apps_overrides variable. The only drawback
I see is that this condition will have to be changed if the default value for
apps.keycloak.enabled is ever changed (in modules/values.tmpl.yaml).
This PR replaces #768

Darn it, yamldecode fails with an empty string (default value of the app_of_apps_override variable). More work is needed :disappointed:

Maybe we could default to --- or use coalesce()

Closing this PR because it's not needed in any current project anymore, and not relevant to the next modular version.

authors: ckaenzig mcanevet

repo: camptocamp/devops-stack


text:
Upgade to Micronaut 4.3.4

Fixes #201

Thanks @saw303 👍


text:
fix(docs): update the auth disabling variable

Hello team,
First of all thanks for the SDK, it really helped us a lot for our testing the Self-Deployed Camunda 8.
When I was trying and testing the SDK for the first time, I noticed the following difference between the code and the documentation. In the end, I figured it out how to do it. To save others time, I decided to created a PR for this change.
I hope it is helpful for you as well.
Keep up the good work

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Gokhan Kocyigit seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant gkocyigit


text:
deps: update modeling deps

@bpmn-io/properties-panel@3.13.0
camunda-bpmn-js@3.7.0

closes #3929, closes #3884, closes #3941

@marstamm we just released form-js@0.14.1 and form-playground@0.10.1 that update the properties panel version. You might want to bump the versions if that helps you to avoid workarounds 👍

As I understand it, this change
- @import '~@camunda/form-playground/dist/assets/form-js-editor.css';
+ @import '~@camunda/form-playground/dist/assets/form-js-editor-base.css';
+ @import '~@camunda/form-playground/dist/assets/dragula.css';

also prevents us from loading the properties-panel.css twice. I think we want to keep this, as it also prevents possible css clashes in the future and makes debugging easier.

Not intended, I changed the commit message with 8d97b29

authors: marstamm pinussilvestrus

repo: camunda/camunda-modeler


text:
[TASK] Rename camunda-platform-helm to camunda-helm

Related to:
This task is to rename the helm chart, and any referencing CI to camunda-helm instead of camunda-platform-helm.

Overview:
This task is planned for after the 8.5 alpha2 release.  And the reason we want to do it is to prevent any miscommunication about what "the platform" means.

Actions:
[ ] move charts/camunda-platform  to  charts/camunda
[ ] consider whether we should rename the github repository.

I will work on this once all the 8.5 changes are merged into the main branch.

The rename will not happen in 8.5 but for 8.6

repo: camunda/camunda-platform-helm


text:
🛑 Ubuntu.com USN page is down

In 5e2aa03, Ubuntu.com USN page (https://ubuntu.com/security/notices/USN-4697-2) was down:

HTTP code: 503
Response time: 75 ms

Resolved: Ubuntu.com USN page is back up in bc6f9d3.

repo: canonical-web-and-design/upptime


text:
🛑 Ubuntu.com kubernetes docs is down

In 4faa1ac, Ubuntu.com kubernetes docs (https://ubuntu.com/kubernetes/docs) was down:

HTTP code: 503
Response time: 146 ms

Resolved: Ubuntu.com kubernetes docs is back up in aac40c4.


text:
Cassandra fails to restart when adding the monitoring relation

In some cases, when adding the monitoring relation, Cassandra fails to restart with these errors in the pod logs:
2021-08-17T15:05:35.745Z [cassandra] Caused by: picocli.CommandLine$ExecutionException: Error while calling command (com.zegelin.cassandra.exporter.Agent@2f9f7dcf): java.net.BindException: Address already in use
2021-08-17T15:05:35.745Z [cassandra]     at picocli.CommandLine.execute(CommandLine.java:1016)
2021-08-17T15:05:35.745Z [cassandra]     at picocli.CommandLine.access$900(CommandLine.java:142)
2021-08-17T15:05:35.745Z [cassandra]     at picocli.CommandLine$RunLast.handle(CommandLine.java:1199)
2021-08-17T15:05:35.745Z [cassandra]     at picocli.CommandLine$RunLast.handle(CommandLine.java:1167)
2021-08-17T15:05:35.745Z [cassandra]     at picocli.CommandLine$AbstractParseResultHandler.handleParseResult(CommandLine.java:1075)
2021-08-17T15:05:35.745Z [cassandra]     at picocli.CommandLine.parseWithHandlers(CommandLine.java:1358)
2021-08-17T15:05:35.745Z [cassandra]     at com.zegelin.cassandra.exporter.Agent.premain(Agent.java:52)
2021-08-17T15:05:35.745Z [cassandra]     ... 6 more
2021-08-17T15:05:35.745Z [cassandra] Caused by: java.net.BindException: Address already in use
2021-08-17T15:05:35.745Z [cassandra]     at sun.nio.ch.Net.bind0(Native Method)
2021-08-17T15:05:35.745Z [cassandra]     at sun.nio.ch.Net.bind(Net.java:461)
2021-08-17T15:05:35.745Z [cassandra]     at sun.nio.ch.Net.bind(Net.java:453)
2021-08-17T15:05:35.745Z [cassandra]     at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:222)
2021-08-17T15:05:35.745Z [cassandra]     at io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:128)
2021-08-17T15:05:35.745Z [cassandra]     at io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:501)
2021-08-17T15:05:35.745Z [cassandra]     at io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1218)
2021-08-17T15:05:35.746Z [cassandra]     at io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:496)
2021-08-17T15:05:35.746Z [cassandra]     at io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:481)
2021-08-17T15:05:35.746Z [cassandra]     at io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:965)
2021-08-17T15:05:35.746Z [cassandra]     at io.netty.channel.AbstractChannel.bind(AbstractChannel.java:210)
2021-08-17T15:05:35.746Z [cassandra]     at io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:355)
2021-08-17T15:05:35.746Z [cassandra]     at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:399)
2021-08-17T15:05:35.746Z [cassandra]     at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:446)
2021-08-17T15:05:35.746Z [cassandra]     at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:131)
2021-08-17T15:05:35.746Z [cassandra]     at java.lang.Thread.run(Thread.java:748)

The Pod remains then a "zombie": active for Juju, but no actual productive workload running inside it.

Actually, it seems from my tests that the units are all in zombie state even if they get created as the monitoring relation is already established.

This should be fixed in the latest edge release. Are you ever still running in to this @mmanciop?
ps: The fact that it still reports active in this case is a pebble limitation. The pebble team is working on it.

authors: dstathis mmanciop

repo: canonical/cassandra-operator


text:
feat: enable auto-generation of generic resources

Exposes lightkube.load_all_yaml()'s create_resources_for_crds argument as KubernetesResourceHandler.render_manifests(create_resources_for_crds=True).  This lets users of the KubernetesResourceHandler automatically generate generic resources as they load new CRDs.

cc @DomFleischmann.  I think this is what you need for your use case

repo: canonical/charmed-kubeflow-chisme


text:
Make sure Grafana is up before hitting the API to check password validity

Since an HTTPError is also checked for in the password action, it's
possible to encounter a race where the action informs users that the
password has been changed when Grafana is simply not available yet.
No tests since Harness cannot check actions and we can't reliably reproduce a race in the integration tests.

I should have clarified :| Of course, it's a Turing-complete language, anything can be done. Whether or not we should attempt to fake out actions by manually invoking private methods and mocking ActionEvent is another question.

Tbh this solution does not horrify me much. AFAICT OF does comparably little lifting for actions, as opposed to relations.

I'll write the test here, but we should really make an effort to push on OF to implement actions in harness before this becomes a pattern.

Yep we should.


text:
test-branch/execute-job/fork-branch/7f7a177a-6406-4e8f-863c-c09c50104605

PR for testing 6c542cdf052525909e9fc1ab03d2ea69611ea1e5

padding /canonical/self-hosted-runners/run-workflows 6c542cdf052525909e9fc1ab03d2ea69611ea1e5 padding

repo: canonical/repo-policy-compliance-tests


text:
add get_ca action

Description
This change adds an action that returns the CA cert. This is needed in order to connect to the charms using certs generated by this charm.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[ ] I have added tests that validate the behaviour of the software
[ ] I validated that new and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[ ] I have bumped the version of the library (No lib changed)

I will add tests shortly.

Duplicates https://github.com/canonical/self-signed-certificates-operator/pull/14

authors: dstathis sed-i


text:
🛑 Ubuntu.com CVE list is down

In 7e93dfa, Ubuntu.com CVE list (https://ubuntu.com/security/cve) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ubuntu.com CVE list is back up in 81678f6.

repo: canonical/upptime