Cannot load geniushub component

Home Assistant release with the issue:
Home Assistant
0.92.2
Last working Home Assistant release (if known):
0.92.0
Operating environment (Hass.io/Docker/Windows/etc.):
Docker
Component/platform:
https://www.home-assistant.io/components/geniushub/
Description of problem:
Notification in frontend - Component fails to load.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

geniushub:
  host: 192.168.86.xxx
  username: <my username>
  password: <my password>

Traceback (if applicable):
2019-05-03 11:28:33 ERROR (MainThread) [homeassistant.setup] Error during setup of component geniushub
Traceback (most recent call last):
  File "/usr/src/app/homeassistant/setup.py", line 153, in _async_setup_component
    hass, processed_config)
  File "/usr/src/app/homeassistant/components/geniushub/__init__.py", line 49, in async_setup
    await client.hub.update()
  File "/usr/local/lib/python3.7/site-packages/geniushubclient/__init__.py", line 654, in update
    _populate_zone(z)
  File "/usr/local/lib/python3.7/site-packages/geniushubclient/__init__.py", line 566, in _populate_zone
    zone_dict = self._convert_zone(zone_raw)
  File "/usr/local/lib/python3.7/site-packages/geniushubclient/__init__.py", line 260, in _convert_zone
    elif setpoint_temp != default_temp:                              # noqa: disable=F821; pylint: disable=used-before-assignment
UnboundLocalError: local variable 'setpoint_temp' referenced before assignment

Additional information:

Some more information available here:
https://github.com/zxdavb/geniushub-client/issues
A workaround is available in v0.4.9 of the client API.

@cgtobi Do you know why I wasn't pinged about this? - my git IDis in manifest.json?

Sorry, I have no idea.
David Bonnes<EMAIL_ADDRESS>schrieb am Di. 21. Mai 2019 um
19:01:

@cgtobi https://github.com/cgtobi Do you know why I wasn't pinged about
this? - my git IDis in manifest.json?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/23646?email_source=notifications&email_token=AAGRFTR6UVVAZW6QUFKUKHDPWQTF7A5CNFSM4HKS3LQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV4RKGI#issuecomment-494474521,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGRFTURAMSDTG2OJMZEZ7TPWQTF7ANCNFSM4HKS3LQA
.


Make sure sparkContext exists when canceling jobGroup

I rather hate this, but looks better than it was.
fixes #476

@andypetrella

:rocket:

we can improve this later if needed.


24khz & 48khz is indistinguishable

Hey, Sorry to make a new thread. I wanted to double check if I'm not doing something wrong here.
So far I've tested two configs. 16khz -> 48khz worked as great as I expected. but somehow 24khz -> 48khz doesn't seem to be doing anything. the outputs are 1:1 with the 24khz version.
I'm using a Shure SE535 IEM to compare the voices.

From the spectrogram on my end, extending the speech from 24kHz to 48kHz appears to be working fine.
I’m not entirely sure if, by “the outputs are 1:1 with the 24kHz version,” you mean that the 48kHz outputs sound similar to the 24kHz speech or that the high frequencies on the spectrogram are still empty, without achieving the extension.

From the spectrogram on my end, extending the speech from 24kHz to 48kHz appears to be working fine.
I’m not entirely sure if, by “the outputs are 1:1 with the 24kHz version,” you mean that the 48kHz outputs sound similar to the 24kHz speech or that the high frequencies on the spectrogram are still empty, without achieving the extension.

Thanks for the reply.
yeah I mean they sound perceptually very close to 24khz. now that you mentioned it, i also graphed the spectrograms which makes it clear.
48khz original:

48khz reconstructed:

the model was trained for 85k steps for the same dataset as before (750+ hours). the loss has stopped decreasing a long time ago. also, comparing different checkpoints gives the same result.

@yxlu-0102 to extend bandwidth properly from 24kHz to 48kHz we have to run python inference_16k.py or python inference_48k.py ?

@yxlu-0102 to extend bandwidth properly from 24kHz to 48kHz we have to run python inference_16k.py or python inference_48k.py ?

if the target sampling rate is 48, then inference_48 must be used. that's the case with yours.

From the spectrogram on my end, extending the speech from 24kHz to 48kHz appears to be working fine.
I’m not entirely sure if, by “the outputs are 1:1 with the 24kHz version,” you mean that the 48kHz outputs sound similar to the 24kHz speech or that the high frequencies on the spectrogram are still empty, without achieving the extension.

are the wav16 or wav files made by librosa.resample from 48khz to 8khz or 16khz?


Is there any benchmark comparison with other tool, like Unity JsonUtility ?

Yes.
See https://github.com/jacobdufault/fullserializer/issues/114
and the linked article http://jacksondunstan.com/articles/3584
Gist: FullSerializer is about 10x slower than Unity Json. Of course, FS does a lot more as well, so the comparison isn't totally fair.

A performance overhaul is planed and @jacobdufault is writing fastreflect to replace FS core. See https://github.com/jacobdufault/fullinspector/issues/203 for more on this.


Make a release?

Follow up of #3. Do we need a release? If so, astroconda, or PyPI, or both?

I'm inclined to leave this as a git submodule and bundle it via MANIFEST.in. I've had bad experiences in the past with astropy-helpers getting installed (accidentally or on purpose) into site-packages and  their little bootstrap script choosing the wrong version.
What are your thoughts? This package probably won't be useful to anyone outside of STScI.

I also have bad experiences with submodule in a package, which depends on another package, which also has the same submodule but pinned at a different point of history...
Submodule or external dependency both have their own pros and cons. I would have to defer to the infrastructure experts that are you (@jhunkeler ) and @rendinam .
Yes, won't be useful to people outside of STScI. But might be useful across divisions.

Good point. ci-watson's dependencies cannot be resolved unless it gets installed, or the package using it provides those dependencies in their setup.py.
This alone might be enough incentive to make it a standalone package (released on pypi, etc, etc). Now I have to ask... is there a point to implementing it as a submodule if the dependencies might not be resolved at build/run-time?

pytest is the only hard dependency of ci-watson after #3 is merged. I mean, astropy is still used in a function but it won't throw ImportError until that function is run, hence making astropy is an optional dependency. However, not all packages have pytest as a dependency. But... if they use astropy, pytest would be installed anyway... 🤷♀

Done in https://github.com/spacetelescope/ci_watson/releases/tag/0.1 and astroconda/astroconda-contrib#399


http_request is not enabled

Enviroment
platform: Ubuntu 22.04.3 / Windows 10
CPU: x64
Runtime: Nodejs 20
Issue
If run with js-sdk and use extism_http_request API, showhttp_request is not enabledmessage,
If run with extism cli, run success.
js code
const createPlugin = require("@extism/extism")

async function main() {
    const plugin = await createPlugin("./a.wasm",{
        useWasi: true,
        withAllowedHosts: ['www.google.com'],
        allowedHosts: ['www.google.com']
    })
    const ret = await plugin.call("hello")
    console.log(ret)
}
main()

c code
#define EXTISM_IMPLEMENTATION
#include "extism-pdk.h"
int32_t EXTISM_EXPORTED_FUNCTION(hello) {
	char req_str[] = "{\"method\":\"GET\",\"url\":\"http://www.google.com\"}";
	ExtismHandle req = extism_alloc_buf_from_sz(req_str);
	ExtismHandle res = extism_http_request(req, 0);
	extism_output_set_from_handle(res, 0, extism_length(res));
	return 0;
}

build and run
/opt/wasi-sdk/bin/clang -o a.wasm --target=wasm32-unknown-unknown -nostdlib -Wl,--no-entry a.c
node c.js

run result

Ah – since HTTP requests are asynchronous, http_request is only enabled when runInWorker is enabled. You might try passing that during your initial setup:
const createPlugin = require("@extism/extism")

async function main() {
    const plugin = await createPlugin("./a.wasm",{
        useWasi: true,
        withAllowedHosts: ['www.google.com'],
        allowedHosts: ['www.google.com'],
        runInWorker: true
    })
    const ret = await plugin.call("hello")
    console.log(ret)
}
main()

Thank you very much. And you fix  js-sdk referencewithAllowedHost.


[INLONG-4376][Manager] support sqlserver sink

Title Name:[INLONG-4376][Manager] support sqlserver sink
where XYZ should be replaced by the actual issue number.
Fixes #4376
support sqlserver sink
Explain here the context, and why you're making that change. What is the problem you're trying to solve?
Modifications
Describe the modifications you've done.
Verifying this change
(Please pick either of the following options)

[ ] This change is a trivial rework/code cleanup without any test coverage.

[ ] This change is already covered by existing tests, such as:
(please describe tests)

[ ] This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a follow-up issue for adding the documentation

Good job. I suggest add some describe about work in conversation.


[Docs] The new server side pagination changes should be updated for the table widget

Documentation Link

Disable the next option for the pagination
Tooltip for the new input fields
The display of input filed only when the server-side pagination is enabled.
The page size changes based on the table height
Header options is also too high and should be below actions

Describe the problem
Is the documentation missing? Or is it confusing? Why is it confusing?
Describe the improvement
The new server-side pagination changes should be updated for the table widget.

Pending pull request is available, Closing this here


IUXray: train test validation split affecting token/id mappings

Hello, I've attempted to reproduce the results seen in the report however after using your weights, I've been getting a shape error that is due to the size of the word mappings (token_to_id and id_to_token). I've made my own annotations.json file to split the data (70-10-20 as indicated in the paper) however the random split is causing a difference in how many words get embedded into meaningful tokens and how many are embedded as . May I ask how you split the data and if it's possible to have access to the original annotations.json file?

Hi, thanks for your interest. As for the data split, we follow the same data split as R2Gen and R2GenCMN to randomly split the data (70-10-20). I have updated the annotation file in files/iu_xray directory in this repo and hope this can help you successfully reproduce the results.

Hi, thanks for your interest. As for the data split, we follow the same data split as R2Gen and R2GenCMN to randomly split the data (70-10-20). I have updated the annotation file in files/iu_xray directory in this repo and hope this can help you successfully reproduce the results.

Hi, I'm sorry to bother you. May I ask you some questions about the code in R2Gen?
In the https://github.com/cuhksz-nlp/R2Gen/blob/5a2e63f6d8da670725b1926317b4bfd1393ec51b/modules/encoder_decoder.py#L134

the return is
 x + self.dropout(sublayer(self.norm(x, memory)))
Is this code correct? I don't think it corresponds to the diagram in the text. I think it should be
self.norm((x + self.dropout(sublayer(x))), memory)
Can you help me to distinguish? thanks a lot

Hi, thanks for your interest. As for the data split, we follow the same data split as R2Gen and R2GenCMN to randomly split the data (70-10-20). I have updated the annotation file in files/iu_xray directory in this repo and hope this can help you successfully reproduce the results.

Hi, I'm sorry to bother you. May I ask you some questions about the code in R2Gen? In the https://github.com/cuhksz-nlp/R2Gen/blob/5a2e63f6d8da670725b1926317b4bfd1393ec51b/modules/encoder_decoder.py#L134
the return is  x + self.dropout(sublayer(self.norm(x, memory))) Is this code correct? I don't think it corresponds to the diagram in the paper. I think it should be self.norm((x + self.dropout(sublayer(x))), memory) Can you help me to distinguish? thanks a lot

Hi, generally speaking you are right, the valinna transformer uses the post-LN as what you described. However, as in paper On Layer Normalization in the Transformer Architecture, the position of Layer Normalization in Transformer implementation is used as pre-LN and post-LN. For example, Transformer Encoder-based BERT uses post-LN, but Vision Transformer uses pre-LN.
Hope this can help your figure out the problem.
Maybe this is a modification by the R2Gen authors to make the training more stable possibly according to their experiments.
I am not sure and you may need to discuss this with the R2Gen authors to gain the details.

Hi, thanks for your interest. As for the data split, we follow the same data split as R2Gen and R2GenCMN to randomly split the data (70-10-20). I have updated the annotation file in files/iu_xray directory in this repo and hope this can help you successfully reproduce the results.

Hi, I'm sorry to bother you. May I ask you some questions about the code in R2Gen? In the https://github.com/cuhksz-nlp/R2Gen/blob/5a2e63f6d8da670725b1926317b4bfd1393ec51b/modules/encoder_decoder.py#L134
the return is  x + self.dropout(sublayer(self.norm(x, memory))) Is this code correct? I don't think it corresponds to the diagram in the paper. I think it should be self.norm((x + self.dropout(sublayer(x))), memory) Can you help me to distinguish? thanks a lot

Hi, generally speaking you are right, the vanilla transformer uses the post-LN as what you described. However, as in paper On Layer Normalization in the Transformer Architecture, the position of Layer Normalization in Transformer implementation is used as pre-LN and post-LN. For example, Transformer Encoder-based BERT uses post-LN, but Vision Transformer uses pre-LN.
Hope this can help you figure out the problem.
Maybe this is a modification by the R2Gen authors to make the training more stable possibly according to their experiments.
I am not sure and you may need to discuss this with the R2Gen authors to gain the details.

Thank you very much. With your reply, I can completely understand.
As the author of R2Gen may not have focused on issues of his project, I was unable to contact him and confirm.
All in all, thank you again!

Hi, thanks for your interest. As for the data split, we follow the same data split as R2Gen and R2GenCMN to randomly split the data (70-10-20). I have updated the annotation file in files/iu_xray directory in this repo and hope this can help you successfully reproduce the results.

Hi, I'm sorry to bother you. May I ask you some questions about the code in R2Gen? In the https://github.com/cuhksz-nlp/R2Gen/blob/5a2e63f6d8da670725b1926317b4bfd1393ec51b/modules/encoder_decoder.py#L134
the return is  x + self.dropout(sublayer(self.norm(x, memory))) Is this code correct? I don't think it corresponds to the diagram in the paper. I think it should be self.norm((x + self.dropout(sublayer(x))), memory) Can you help me to distinguish? thanks a lot

Hi, generally speaking you are right, the vanilla transformer uses the post-LN as what you described. However, as in paper On Layer Normalization in the Transformer Architecture, the position of Layer Normalization in Transformer implementation is used as pre-LN and post-LN. For example, Transformer Encoder-based BERT uses post-LN, but Vision Transformer uses pre-LN.
Hope this can help you figure out the problem.
Maybe this is a modification by the R2Gen authors to make the training more stable possibly according to their experiments.
I am not sure and you may need to discuss this with the R2Gen authors to gain the details.

Hi! I'm sorry to bother you again! I hope to get your help.

Have you tried to reproduce the results using the weights provided by the author? I tried this, but the results(On IU X-ray) I got were not the same as those shown in the paper, which is higher than the paper.

Results on data set MIMIC-CXR. Why are the results in the following two tables different? The author mentioned "the number of memory slots is set to 3 by default" in the paper, but the results in Table 1 are different from the third row in Table 2, do you know why?

thanks again！


[SPARK-25167][SPARKR][TEST][MINOR] Minor fixes for R sql tests (timestamp comparison)

What changes were proposed in this pull request?
The "date function on DataFrame" test fails consistently on my laptop. In this PR
i am fixing it by changing the way we compare the two timestamp values. With this change i am able to run the tests clean.
How was this patch tested?
Fixed the failing test.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2685/
Test PASSed.

Test build #95440 has started for PR 22274 at commit de61460.

Test build #95440 has finished for PR 22274 at commit de61460.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95440/
Test PASSed.

The "date function on DataFrame" test fails consistently on my laptop.

@dilipbiswal, would you mind if I ask to list up R version (and additional env information if possible)?

@HyukjinKwon Sure.. here is the info. Please let me know if you need anything else.
> sessionInfo()
R version 3.5.1 (2018-07-02)
Platform: x86_64-apple-darwin15.6.0 (64-bit)
Running under: macOS High Sierra 10.13.3

Matrix products: default
BLAS: /Library/Frameworks/R.framework/Versions/3.5/Resources/lib/libRblas.0.dylib
LAPACK: /Library/Frameworks/R.framework/Versions/3.5/Resources/lib/libRlapack.dylib

locale:
[1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base

other attached packages:
[1] testthat_1.0.2

loaded via a namespace (and not attached):
[1] compiler_3.5.1 magrittr_1.5   R6_2.2.2       crayon_1.3.4

Test build #95520 has started for PR 22274 at commit 4b6cd9f.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2725/
Test PASSed.

Test build #95520 has finished for PR 22274 at commit 4b6cd9f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95520/
Test PASSed.

maybe also your laptop's system time zone? could you also check that?

interesting. maybe something to do with newer R release - I scanned through the rel note though but didn't find what might be related.

possible - but since this passes for you and in jenkins/appveyor you change seem to work both ways, which is good enough for me

merged to master

@felixcheung Thank you very much !!


chore: update useSWRInfinite import

Per https://github.com/vercel/swr/pull/1272

quite the fantastic addition if I must say so myself! why indeed!


Invite to org

Name: Aman Kumar
Why would you like to join the organisation? Contribute to the profiles and all.

Check your email or org github page

🎉🎊Welcome to Jaidev Studio🎉🎊!!

Why not contribute to...
Unique-Github-Profiles!

Check your email or org github page

CHECK YOUR EMAIL OR GITHUB PAGE CLICK HERE


MP4 video play error: Leaf atom defines extended atom size (unsupported).

Version
ExoPlayer 2.18.2
More version details
No response
Devices that reproduce the issue

xiaomi 11 Android 13
all devices

Devices that do not reproduce the issue
No response
Reproducible in the demo app?
Yes
Reproduction steps
play source
Expected result
play success
Actual result
play error Leaf atom defines extended atom size (unsupported).
Media
https://video.twimg.com/amplify_video/1704654962834214912/vid/avc1/1280x720/50-birosgYs_rDGX.mp4?tag=14
Bug Report

[ ] You will email the zip file produced by adb bugreport to<EMAIL_ADDRESS>after filing this issue.

Hi @Caij,
This failure occurred because the mvhd leaf atom defines an extended atom size for the media URL above.
The structure of the mvhd box is defined by the ISO/IEC 14496-12 standard, and it has a fixed format with specific fields, such as creation time, modification time, time scale, and others. The structure and length of these fields are well-defined by the standard, and there is no provision for extending the header length or using a wide atom in the mvhd box itself.


Add uml diagrams and update DG

Will need to remove a couple of white spaces before this can be merged.

There is some format issues here that fail the CI test. Shall we resolve them first?

There is some format issues here that fail the CI test. Shall we resolve them first?

Fixed them! Thanks for reminding!


Reload fails: "tsnet: listener already open for tailscale, :80"

The usual systemd unit for caddy includes an ExecReload= option:
ExecReload=/usr/bin/caddy reload --config /etc/caddy/Caddyfile --force

When this is run on a caddy service that already connected to Tailscale, we get this error: loading config: loading new config: http app module: start: listening on tailscale/nitter:80: tsnet: listener already open for tailscale, :80
Dec 26 21:10:05 hydrangea systemd[1]: Reloading Caddy.
Dec 26 21:10:05 hydrangea caddy[2407]: {"level":"info","ts":1672089005.6320755,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":""}
Dec 26 21:10:05 hydrangea caddy[2031]: {"level":"info","ts":1672089005.6348317,"logger":"admin.api","msg":"received request","method":"POST","host":"localhost:2019","uri":"/load","remote_ip":"<IP_ADDRESS>","remote_port":"40046","headers":{"Accept-Encoding":["gzip"],"Content-Length":["203"],"Content-Type":["application/json"],"Origin":["http://localhost:2019"],"User-Agent":["Go-http-client/1.1"]}}
Dec 26 21:10:05 hydrangea caddy[2031]: {"level":"info","ts":1672089005.6360798,"logger":"admin","msg":"admin endpoint started","address":"localhost:2019","enforce_origin":false,"origins":["//localhost:2019","//[::1]:2019","//<IP_ADDRESS>:2019"]}
Dec 26 21:10:05 hydrangea caddy[2031]: {"level":"warn","ts":1672089005.6363716,"logger":"http","msg":"server is listening only on the HTTP port, so no automatic HTTPS will be applied to this server","server_name":"srv0","http_port":80}
Dec 26 21:10:05 hydrangea caddy[2031]: {"level":"info","ts":1672089005.636495,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0xc000354a10"}
Dec 26 21:10:05 hydrangea caddy[2031]: {"level":"info","ts":1672089005.63655,"logger":"tls.cache.maintenance","msg":"stopped background certificate maintenance","cache":"0xc000354a10"}
Dec 26 21:10:05 hydrangea caddy[2031]: {"level":"error","ts":1672089005.6366794,"logger":"admin.api","msg":"request error","error":"loading config: loading new config: http app module: start: listening on tailscale/nitter:80: tsnet: listener already open for tailscale, :80","status_code":400}
Dec 26 21:10:05 hydrangea caddy[2407]: Error: sending configuration to instance: caddy responded with error: HTTP 400: {"error":"loading config: loading new config: http app module: start: listening on tailscale/nitter:80: tsnet: listener already open for tailscale, :80"}
Dec 26 21:10:05 hydrangea caddy[2031]: {"level":"info","ts":1672089005.6377842,"logger":"admin","msg":"stopped previous server","address":"localhost:2019"}
Dec 26 21:10:05 hydrangea systemd[1]: caddy.service: Control process exited, code=exited, status=1/FAILURE
Dec 26 21:11:35 hydrangea systemd[1]: caddy.service: Reload operation timed out. Killing reload process.

Restarting the service works fine, as expected.

Full Caddyfile (most of this is boilerplate from my usual template):
{
        admin localhost:2019
        email<EMAIL_ADDRESS>}

(global) {
        encode zstd gzip
        handle_errors {
                respond "{http.error.status_code} {http.error.status_text}"
        }
        header cache-control "public, max-age=0, must-revalidate"
        log {
                output file /var/log/caddy/access.log
        }
}

:80 {
        bind tailscale/nitter
        respond / "butts"
}

I'm not able to reproduce this now, so I'm fairly certain it got fixed in #30, which added proper listener shutdown.  Could you try again with the latest version of the plugin, and see if you still run into this behavior?

I don't have anything presently using this plugin so I can only agree with "likely fixed".

I've just run into this myself, using caddy-docker-proxy, as AstraLuma mentioned

Dockerfile
ARG CADDY_VERSION=2.8
FROM caddy:${CADDY_VERSION}-builder AS builder

RUN xcaddy build \
  --with github.com/lucaslorentz/caddy-docker-proxy/v2 \
  --with github.com/tailscale/caddy-tailscale

FROM caddy:${CADDY_VERSION}-alpine

COPY --from=builder /usr/bin/caddy /usr/bin/caddy

CMD ["caddy", "docker-proxy"]

Base Caddyfile
(read by caddy-docker-proxy and merged with config from docker labels)
{
	acme_dns cloudflare {$CLOUDFLARE_DNS_API_TOKEN}
	acme_ca https://acme-staging-v02.api.letsencrypt.org/directory

	tailscale {
		auth_key {$TS_AUTHKEY}
		state_dir /data/tailscale
	}
}

(internal) {
	abort
}

http://*.example.com:80 https://*.example.com:443  {
	import internal
	bind tailscale/caddy
}

http://*.example.com:80 https://*.example.com:443  {
	import internal
	bind <IP_ADDRESS>
}

barebones docker-compose.yml
services:
  test:
    container_name: test
    image: crccheck/hello-world
    labels:
      caddy: (internal)
<EMAIL_ADDRESS>test.example.com
      caddy.route: "@test"
      caddy.route.reverse_proxy: "{{upstreams 8000}}"

  test2:
    container_name: test2
    image: crccheck/hello-world
    labels:
      caddy: (internal)
<EMAIL_ADDRESS>test2.example.com
      caddy.route: "@test2"
      caddy.route.reverse_proxy: "{{upstreams 8000}}"

  caddy:
    container_name: caddy
    build: ./caddy/
    restart: unless-stopped
    ports:
      - "6080:80"
      - "6443:443"
    environment:
      # - CADDY_INGRESS_NETWORKS=caddy
      - CLOUDFLARE_DNS_API_TOKEN=${CLOUDFLARE_DNS_API_TOKEN}
      - CADDY_DOCKER_CADDYFILE_PATH=/etc/caddy/Caddyfile
      - CADDY_DOCKER_POLLING_INTERVAL=2s
      - CADDY_DOCKER_PROCESS_CADDYFILE=false
      - TS_AUTHKEY=${TS_CADDY_PROXY_AUTHKEY}
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - ./network/caddy/Caddyfile:/etc/caddy/Caddyfile
      - caddydata:/data

volumes:
  caddydata:

Error log entry
caddy                        | {"level":"error","ts":1720330017.807547,"logger":"admin.api","msg":"request error","error":"loading config: loading new config: http app module: start: listening on tailscale/caddy:443: tsnet: listener already open for tcp, :443","status_code":400}
caddy                        | {"level":"error","ts":1720330017.8076308,"logger":"docker-proxy","msg":"Error response from server","server":"localhost","status code":400,"body":"{\"error\":\"loading config: loading new config: http app module: start: listening on tailscale/caddy:443: tsnet: listener already open for tcp, :443\"}\n"}

On a fresh restart it does work just fine, similar to what iliana mentioned

So I've tried out a horrible proof of concept, basically just lifting caddy's listenReusable to wrap the Listeners + PacketConns from tsnet and it seems to resolve the issue.
Though I also haven't checked out what run-on impacts there are for that

Running into this issue today as I use lucaslorentz/caddy-docker-proxy and it can't reload new config if there's a caddy-tailscale listener in the mix.
My workaround so far is to have a second instance of Caddy that just runs caddy-tailscale with a fixed config. It's not ideal, but at least the rest of the system still works dynamically and I only have to manually work on the things I'm only serving into the Tailnet.


Form items are not aligned

Current behaviour
Form items are not aligned.

Expected behaviour
Form items are aligned.
Version
1.0.2

fixed

@bassemmagdy fixed in which branch? I don't see fix in integration branch.

@bassemmagdy When you have time, please confirm if this has been fixed and pending merge.

@cryptoBeliever @coiki should be fixed already on integration branch

@bassemmagdy checked on integration branch
Harvesting view (private keys "Not linked" not aligned):

Aggregate (supply change) not aligned:

@cryptoBeliever would you check #1507?

Ok. I tough it should check on integration branch because of your comment (https://github.com/nemgrouplimited/symbol-desktop-wallet/issues/1445#issuecomment-858619496).
On branch gh1446-fix-icons-consistency it's fixed :+1:


OpenSSL 1.1 compatibility

Tried to compile FreeRDP against the current OpenSSL master (1.1)
Looks like this will be quite a beast to tame,

many structures are now opaque
The direct data structure access in tls.c is no longer working.

TODO:

[ ] Merge libfreerdp and winpr function wrappers for SSL in winpr
[ ] Add winpr implementations for the function wrapper for OpenSSL 1.0
[ ] Add winpr implementations for the function wrapper for OpenSSL 1.1
[ ] Add winpr implementations for the function wrapper for MBEDTLS
[ ] Add winpr implementations for the function wrapper for OSX security framework #3022
[ ] Add winpr implementations for the function wrapper for ...

Making the struct opaque is quite nice, anyway we needed some internal access to set the error code when shutting down with TLS. I hope they have added a public method to do it...

Failing to build with OpenSSL 1.1 is now a release critical bug in Debian, see https://bugs.debian.org/828142 .

A draft patch to gain OpenSSL 1.1 compatibility is now available in the Debian bug report.  I believe it need some more work before it is ready.

@petterreinholdtsen Thank you for the update, unfortunately the main issue with OpenSSL 1.1 compatibility is the use of BIO in tls.c and tcp.c. That will need some work.

[akallabeth]

@petterreinholdtsen Thank you for the update, unfortunately the main
issue with OpenSSL 1.1 compatibility is the use of BIO in tls.c and
tcp.c. That will need some work.

OK.  I did not notice any build errors in that part, so I did not have a
look.  Glad to know you are on the case. :)
--
Happy hacking
Petter Reinholdtsen

Great news, @nfedera fixed it with #3615


Change return value to false form true on DefaultMemberAccess#setup method #47

I've ficed #47 on master branch.

LGTM 👍

thanks!!


Add basic support for gemini models

Preliminary support for gemini.
What's currently missing:

Async
Partials/Streaming
Tool use

:rocket: This description was created by Ellipsis for commit 25c28bbaa9355dd9acd247882a34be4311a5bf84

Summary:
This PR introduces basic support for Gemini models in the Instructor library, including a new client, updated documentation, and test cases.
Key points:

Added basic support for Gemini models in the Instructor library.
Introduced a new client for handling Gemini model interactions.
Updated documentation and examples to include Gemini model usage.
Added test cases for Gemini model functionality.
Modified retry logic and response handling to accommodate Gemini-specific features.

Generated with :heart: by ellipsis.dev

can you add a note in the patching notes

@ellipsis-dev can you try and update the documentation on patch.md docs

Will try and get these in today @jxnl.
Also came across https://github.com/jxnl/instructor/pull/624, and it's best if we don't have to introduce new syntax. Taking a stab at standardising Gemini api calls as well.

Out of curiosity - Is there a reason this isn't using the official function calling API? https://cloud.google.com/vertex-ai/generative-ai/docs/multimodal/function-calling

Out of curiosity - Is there a reason this isn't using the official function calling API? https://cloud.google.com/vertex-ai/generative-ai/docs/multimodal/function-calling

I have function calling on a branch but the responses are inconsistent and the response payload structure varies with every call. Not reliable enough to recommend at this time.

are we ready to merge
lets move evals to https://github.com/instructor-ai/evals at some point, so lets not worry about that

Yes this is good to go!

whoo @ssonal found a bug in imports #697


marisa-python: fix build

Motivation for this change
Fixed build procedure for the package.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg  build python27Packages.marisa python37Packages.marisa

Is this package supposed to be compatible with python3?
$ nix build --no-link --keep-going --max-jobs 4 --option build-use-sandbox true -f /home/joerg/.cache/nix-review/pr-57013/build.nix
error: build of '/nix/store/6bqgikqaxnbmsf9h5prnw44zsqq3awaf-python3.7-marisa-1.3.40.drv' on<EMAIL_ADDRESS>failed: builder for '/nix/store/6bqgikqaxnbmsf9h5prnw44zsqq3awaf-python3.7-marisa-1.3.40.drv' failed with exit code 1
builder for '/nix/store/6bqgikqaxnbmsf9h5prnw44zsqq3awaf-python3.7-marisa-1.3.40.drv' failed with exit code 1; last 10 log lines:
  marisa-swig_wrap.cxx:2549:13: note: suggested alternative: ‘PyLong_FromVoidPtr’
         obj = PyCObject_FromVoidPtr(descriptor, NULL);
               ^~~~~~~~~~~~~~~~~~~~~
               PyLong_FromVoidPtr
  marisa-swig_wrap.cxx: At global scope:
  marisa-swig_wrap.cxx:2512:22: warning: ‘swig_empty_runtime_method_table’ defined but not used [-Wunused-variable]
     static PyMethodDef swig_empty_runtime_method_table[] = { {NULL, NULL, 0, NULL} };/* Sentinel */
                        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  error: command 'gcc' failed with exit status 1
  builder for '/nix/store/6bqgikqaxnbmsf9h5prnw44zsqq3awaf-python3.7-marisa-1.3.40.drv' failed with exit code 1
cannot build derivation '/nix/store/rb736bdh5v642fv8x9zq4f0f4fqb11q8-env.drv': 1 dependencies couldn't be built
[5 built (1 failed), 18 copied (120.4 MiB), 31.1 MiB DL]
error: build of '/nix/store/rb736bdh5v642fv8x9zq4f0f4fqb11q8-env.drv' failed
https://github.com/NixOS/nixpkgs/pull/57013
1 package failed to build:
python37Packages.marisa

Otherwise please use the disable attribute to mark it as broken on python3.

Is this package supposed to be compatible with python3?

I guess it isn't since CObject API is considered deprecated since Python 3.1 and the only package (AFAIK)  which depends on pythonPackages.marisa -- is libkkc which uses python2Packages.

Otherwise please use the disable attribute to mark it as broken on python3.

Done.

@GrahamcOfBorg build python27Packages.marisa

nix-review looks ok now

backported to 19.03: 52e59ba4ad1 , cc #56826


Update gamelift patches to sdkv2

Upstream recently made a change
so that a service cannot have resources across both sdkv1 and sdkv2.
This PR updates the aws_gamelift_matchmaking_configuration &
aws_gamelift_matchmaking_rule_set resources to sdkv2.
$ make testacc TESTS=TestAccMatchmakingConfiguration PKG=gamelift
make: Verifying source code with gofmt...
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go1.22.6 test ./internal/service/gamelift/... -v -count 1 -parallel 20 -run='TestAccMatchmakingConfiguration'  -timeout 360m
=== RUN   TestAccMatchmakingConfiguration_basic
=== PAUSE TestAccMatchmakingConfiguration_basic
=== RUN   TestAccMatchmakingConfiguration_tags
=== PAUSE TestAccMatchmakingConfiguration_tags
=== RUN   TestAccMatchmakingConfiguration_disappears
=== PAUSE TestAccMatchmakingConfiguration_disappears
=== CONT  TestAccMatchmakingConfiguration_basic
=== CONT  TestAccMatchmakingConfiguration_disappears
=== CONT  TestAccMatchmakingConfiguration_tags
--- PASS: TestAccMatchmakingConfiguration_disappears (12.48s)
--- PASS: TestAccMatchmakingConfiguration_tags (19.75s)
--- PASS: TestAccMatchmakingConfiguration_basic (27.17s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/gamelift   31.040s

$ make testacc TESTS=TestAccMatchmakingRuleSet PKG=gamelift
make: Verifying source code with gofmt...
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go1.22.6 test ./internal/service/gamelift/... -v -count 1 -parallel 20 -run='TestAccMatchmakingRuleSet'  -timeout 360m
=== RUN   TestAccMatchmakingRuleSet_basic
--- PASS: TestAccMatchmakingRuleSet_basic (12.93s)
=== RUN   TestAccMatchmakingRuleSet_disappears
=== PAUSE TestAccMatchmakingRuleSet_disappears
=== CONT  TestAccMatchmakingRuleSet_disappears
--- PASS: TestAccMatchmakingRuleSet_disappears (10.39s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/gamelift   27.193s

re #4479

We have TestGameLift coverage as well which seems to be passing. Thank you!


Make body of  function declaration always a Block

The body of a function declaration currently is a Statement and can either be a single statement or a Block. In 99 % of the cases it's a block and we have to do an annoying (smart) cast to assert it's a block. Could we just change this to a Block for v9 and wrap single-statement functions into an implicit block to be consistent with other functions?

The early decision was to not make it a block as we did not see its necessity. Any handling of a statement, would then handle the body and if it was a block the statements would be handled appropriately within. So that idea did not need casting of any sorts.
I would agree to make every body a Block if the smartcasts are actually necessary. If they are just a symptom of us not having appropriated indirection in our handler structures, I would not do so because the same logic that "handles" a block might be used in other places, sometimes not even a body but the child of another structure, e.g. if, while, and there we want to have that indirection over a handle() that then dispatches to a handleBlock. I am aware that we have different naming in the passes.
Can you provide some examples where this causes Issues such that we can investigate together if we need the casts or if we are insufficiently working with the dispatching concepts?

At first glance: 18 times cast to "as Block" (https://github.com/search?q=repo%3AFraunhofer-AISEC%2Fcpg "as Block"&type=code) and 21 times cast to "as? Block" (https://github.com/search?q=repo%3AFraunhofer-AISEC%2Fcpg+"as%3F+Block"&type=code), probably more as I did just a string search, so I would argue that we can remove at least 50 casts. 18 of them are actually just plain wrong since they assume that it is a Block, when in theory it could not be.


Getting Fatal error Out of memory on ReflectionClass

Hi,
The Parser::blockTypes() use $this->_blockTypes array. Is it possible to do the same pattern in Parser::inlineMarkers()?
The reflection is costly operation and I'm getting Fatal error when parsing more texts in the row.
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /var/www/html/vendor/cebe/markdown/Parser.php on line 275

Sorry, my mistake. i overlooked bug in my code and it was failing in yours.
But getting list of inline parsers should be somehow cached anyway.

Please close the issue then. Thanks.


Add email-related gems needed by Rails that Ruby is removing

It appears I tested incorrectly - not only does the latest Rails not fix the gem problem we're seeing, but in fact Rails cannot directly add those as a dependency because of a weird double-inclusion problem.
So for now, we'll need to add the three email-related gems used by Rails that used to be builtins (net-smtp, net-pop, net-imap) to our Gemfile. That's also what Rails is doing for newly-created Rails apps in latest head-of-master.

I should downgrade Bundler. I haven't been careful with Bundler version in the Gemfile, and I don't think the newer Bundler should be needed to add these gems.
Here's a link to the double-inclusion problem: https://bugs.ruby-lang.org/issues/17873
Short version (as I understand it) is that the not-built-into-Ruby versions of these gems depend on other not-built-into-Ruby versions of gems, which conflict with the versions built into Ruby :-( The digest gem is a dependency here that causes this problem, though I can't recall if there are others.
You can see Rails choosing to use the same fix (adding it to each individual app's Gemfile, not gems-as-deps-of-Rails-gem) here: https://github.com/rails/rails/blob/acee501edd0274acb1b073aac1ac41a3181aafdd/Gemfile#L172-L182

Thanks for the information. This seems all unfortunate.
The error from above seems to come from io-wait 0.1.1 not existing on RubyGems: https://rubygems.org/gems/io-wait
And probably it only exists as a default gem of Ruby 3.1-dev.


No wagtailcore_revision is created when a page is moved

Issue Summary
When moving a page in Wagtail, no revision is created indicating the change in parent and subsequent change in URL.
Steps to Reproduce

Create a page.
Publish it.
Validate wagtailcore_revision has current path and url_path.
Move page to a different place in the tree.
Check wagtailcore_revision and see only the original revision is there.

Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?
Expect that key changes to a page, such as url_path and path would be captured in a revision.

Hi @cyface - I'd say this is the expected behaviour. While tree location is a property of a page model (and so a change of location could be regarded as an edit), logically it has to be a property that exists outside of the concept of revision history - otherwise you'd run into situations such as a draft revision of a page existing in a different location to the live revision, or rolling back to an earlier revision and having it move to a previous location (at which point there's no guarantee that the parent page in question still exists).
Moving a page does create an entry in the audit log (wagtailcore_pagelogentry), so these kinds of 'global' changes are still captured.


Fix bad prop name for "noSubscriptions"

Coverage remained the same at 94.615% when pulling a93c206161622f8fc73f608c99af4104c5b6ac77 on bendrucker:patch-1 into d99ec6c0917fc57988b011a2ee6ffe21e1ef9c4e on yoshuawuyts:master.

Ooooh, great catch! - thank you :sparkles:

Released as v7.0.5 :sparkles:


cider: 1.5.7 -> 1.6.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/cider/versions.
meta.description for cider is: "A new look into listening and enjoying Apple Music in style and performance."
meta.homepage for cider is: "https://github.com/ciderapp/Cider"
meta.changelog for cider is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.6.0 with grep in /nix/store/96sj1yn8v6mxnr74cs85if6malwzckcx-cider-1.6.0
found 1.6.0 in filename of file in /nix/store/96sj1yn8v6mxnr74cs85if6malwzckcx-cider-1.6.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
cider

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/96sj1yn8v6mxnr74cs85if6malwzckcx-cider-1.6.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cider https://github.com/r-ryantm/nixpkgs/archive/f797afbc26ae566604fd210845e8ec34b4c637eb.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/96sj1yn8v6mxnr74cs85if6malwzckcx-cider-1.6.0
ls -la /nix/store/96sj1yn8v6mxnr74cs85if6malwzckcx-cider-1.6.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

cider

Maintainer pings
cc @cigrainger for testing.

@ofborg build cider cider.passthru.tests


Allow compareing Timestamp & Date in queries

Changes needed to fix https://github.com/quasar-analytics/quasar/issues/1762

Current coverage is 63.45% (diff: 0.00%)

Merging #1771 into master will decrease coverage by 0.02%

@@             master      #1771   diff @@
==========================================
  Files           354        354
  Lines         16701      16705     +4
  Methods       16339      16343     +4
  Messages          0          0
  Branches        217        217
==========================================
- Hits          10602      10600     -2
- Misses         6099       6105     +6
  Partials          0          0

Powered by Codecov. Last update 7030a31...294a025

This is being closed as implementation is correct. The tests were incorrect (you can not compare date and timestamp)


OPCT-209: bump UBI to fix security issues on container

Bump UBI to fix security issues before releasing v0.4.
References:

https://catalog.redhat.com/software/containers/ubi8/ubi-minimal/5c359a62bed8bd75a2c3fba8
https://issues.redhat.com/browse/OPCT-209
https://quay.io/repository/ocp-cert/opct?tab=tags

Before:

After:

/assign @rvanderp3 @faermanj


Can a new release of Anax-MVC be published?

Can you release a new version of Anax-MVC so I can get the latest version with composer?

Tagged v2.0.6.


chore: add changesets for publishing

Codecov Report

Merging #95 (27504f3) into master (f1aa2ce) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #95   +/-   ##
=======================================
  Coverage   98.13%   98.13%
=======================================
  Files          12       12
  Lines         698      698
=======================================
  Hits          685      685
  Misses         13       13

Continue to review full report at Codecov.

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


Using dynamic url for dashboard state transitions and adding it to web-cloud

I just played around with this branch in a web-admin project, I interacted with a dashboard, and the URL didn't update. It never added a state query parameter. @AdityaHegde, can you test it on web-admin too?


Clair responded with a failure: Got response 404 with message Not Found

Description of Problem:
When attempting to scan an image, e.g with the following command:
./clair-scanner --ip  <IP_ADDRESS> postgres:9.6

clair responds with:
018/06/01 01:39:04 [CRIT] ▶ Could not analyze layer: Clair responded with a failure: Got response 404 with message Not Found

Expected Outcome:
When using a local image scanner (e.g clair-scanner), clair shoudl respond with sensible analysis of the docker image.
Actual Outcome:
Clair fails scan the image layers:
root@lol:/opt/clair# ./clair-scanner --ip  <IP_ADDRESS> postgres:9.6
2018/06/01 04:09:43 [INFO] ▶ Start clair-scanner
2018/06/01 04:09:46 [INFO] ▶ Server listening on port 9279
2018/06/01 04:09:46 [INFO] ▶ Analyzing 4b781935f93a2e1bc05b9591021e51646ea4ecac64320cd58dc8c619c1fc407a
2018/06/01 04:09:46 [CRIT] ▶ Could not analyze layer: Clair responded with a failure: Got response 404 with message Not Found

Here are some logs from the clair container:
{"Event":"pagination key is empty, generating...","Level":"warning","Location":"config.go:110","Time":"2018-06-01 03:22:39.246664"}
{"Detectors":"alpine-release,apt-sources,lsb-release,os-release,redhat-release","Event":"Clair registered components","Level":"info","Listers":"apk,dpkg,rpm","Location":"main.go:103","Time":"2018-06-01 03:22:39.246935","Updaters":"rhel,ubuntu,alpine,debian,oracle"}
{"Event":"running database migrations","Level":"info","Location":"pgsql.go:270","Time":"2018-06-01 03:22:39.255074"}
{"Event":"database migration ran successfully","Level":"info","Location":"pgsql.go:277","Time":"2018-06-01 03:22:39.848536"}
{"Event":"starting grpc server","Level":"info","Location":"server.go:155","Time":"2018-06-01 03:22:39.848746","addr":"[::]:6060"}
{"Event":"updater service started","Level":"info","Location":"updater.go:91","Time":"2018-06-01 03:22:39.848732","lock identifier":"001dd8fc-1fe9-4b15-a77f-4cd35c9afd93"}
{"Event":"starting health API","Level":"info","Location":"api.go:62","Time":"2018-06-01 03:22:39.848756","addr":"<IP_ADDRESS>:6061"}
{"Event":"grpc server is configured without client certificate authentication","Level":"warning","Location":"server.go:199","Time":"2018-06-01 03:22:39.849096"}
{"Event":"notifier service is disabled","Level":"info","Location":"notifier.go:76","Time":"2018-06-01 03:22:39.849412"}
{"Event":"updating vulnerabilities","Level":"info","Location":"updater.go:191","Time":"2018-06-01 03:22:39.851176"}
{"Event":"fetching vulnerability updates","Level":"info","Location":"updater.go:271","Time":"2018-06-01 03:22:39.851290"}
{"Event":"Start fetching vulnerabilities","Level":"info","Location":"debian.go:63","Time":"2018-06-01 03:22:39.851367","package":"Debian"}
{"Event":"Start fetching vulnerabilities","Level":"info","Location":"rhel.go:92","Time":"2018-06-01 03:22:39.851364","package":"RHEL"}
{"Event":"Start fetching vulnerabilities","Level":"info","Location":"oracle.go:119","Time":"2018-06-01 03:22:39.851444","package":"Oracle Linux"}
{"Event":"Start fetching vulnerabilities","Level":"info","Location":"ubuntu.go:88","Time":"2018-06-01 03:22:39.851458","package":"Ubuntu"}
{"Event":"Start fetching vulnerabilities","Level":"info","Location":"alpine.go:52","Time":"2018-06-01 03:22:39.851407","package":"Alpine"}
{"Event":"finished fetching","Level":"info","Location":"updater.go:290","Time":"2018-06-01 03:22:44.456218","updater name":"alpine"}
{"Event":"finished fetching","Level":"info","Location":"updater.go:290","Time":"2018-06-01 03:22:44.913842","updater name":"debian"}
{"Event":"finished fetching","Level":"info","Location":"updater.go:290","Time":"2018-06-01 03:25:47.127418","updater name":"ubuntu"}
{"Event":"finished fetching","Level":"info","Location":"updater.go:290","Time":"2018-06-01 03:35:34.003670","updater name":"rhel"}
{"Event":"finished fetching","Level":"info","Location":"updater.go:290","Time":"2018-06-01 03:49:26.118770","updater name":"oracle"}
{"Event":"adding metadata to vulnerabilities","Level":"info","Location":"updater.go:317","Time":"2018-06-01 03:49:26.133465"}
{"Event":"update finished","Level":"info","Location":"updater.go:256","Time":"2018-06-01 03:52:29.706441"}
{"Event":"Handled HTTP request","Level":"info","Location":"server.go:105","Time":"2018-06-01 04:09:46.644098","elapsed time (ms)":0.057273,"method":"POST","remote addr":"<IP_ADDRESS>:36020","request uri":"/v1/layers","status":"404"}

Environment:

Clair version/image: latest
Clair client name/version:  clair-scanner
Host OS:  Ubuntu 16.04
Kernel (e.g. uname -a):  Linux lol 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux- Kubernetes version (use kubectl version):
Helm version (use helm version):  n/a
Network/Firewall setup:  default docker

It looks like the client you're using is for the stable release of Clair and not for the latest git version. Please try using the quay.io/coreos/clair:latest.

I am using the latest image getting same error.
2018/07/18 22:56:23 [CRIT] ▶ Could not analyze layer: Clair responded with a failure: Got response 404 with message Not Found


[BUG] Bad color style for light theme

What version of Node.js are you using?
does not matter
What version of npm are you using?
does not matter
What operating system are you using?
does not matter
Describe the Bug
Bad color style for light theme

Expected Behavior

To Reproduce
No response

Ah whoops! Will get this fixed later today.


RuntimeError with customized loss while running loss.backward()

I wrote a simple loss function in {eval_rcnn.py → eval_one_epoch_joint() → for loop (for data in dataloader: ...)}.
I have enabled all gradient propagation by replacing "torch.no_grad()" with "torch.set_grad_enabled(True)" and set "inputs.requires_grad = True". Here is the use of my loss:

    Z_rcnn_t = rcnn_cls.float()
    loss_adv_cls = - Z_rcnn_t.sum()
    model.zero_grad()
    loss_adv_cls.backward()

The ".backward()"  end up with a Runtime Error:

File "/home/jqwu/Codes/PointRCNN/tools/simple_attack.py", line 974, in
eval_single_ckpt(root_result_dir)
File "/home/jqwu/Codes/PointRCNN/tools/simple_attack.py", line 832, in eval_single_ckpt
eval_one_epoch(model, test_loader, epoch_id, root_result_dir, logger)
File "/home/jqwu/Codes/PointRCNN/tools/simple_attack.py", line 759, in eval_one_epoch
ret_dict = eval_one_epoch_joint(model, dataloader, epoch_id, result_dir, logger)
File "/home/jqwu/Codes/PointRCNN/tools/simple_attack.py", line 580, in eval_one_epoch_joint
loss_adv_cls.backward()
File "/home/jqwu/.conda/envs/PointRCNN-py37/lib/python3.7/site-packages/torch/tensor.py", line 195, in backward
torch.autograd.backward(self, gradient, retain_graph, create_graph)
File "/home/jqwu/.conda/envs/PointRCNN-py37/lib/python3.7/site-packages/torch/autograd/init.py", line 99, in backward
allow_unreachable=True)  # allow_unreachable flag
RuntimeError: Expected isFloatingType(grads[i].type().scalarType()) to be true, but got false.  (Could this error message be improved?  If so, please report an enhancement request to PyTorch.)

I have tried the following solutions, but they didn't work in my case:

https://github.com/qiqihaer/votenet-kitti/issues/5
https://github.com/HaozheQi/P2B/issues/8

I am using CUDA 10.1, torch 1.4, python 3.7.
I have spent a lot of time on this. Anyone has solved a similar problem? 😿

Have you solved this problem？解决了么

Have you solved this problem？解决了么

Not yet....


Several updates in prepation for 1.0.0 release

Updated package names in core module to include core in prefix
Made SharedBatchWriter package private
Added '@since 1.0.0' annotations

+1


Award chains / levels

From #52

@numberZero
That sounds more like “multi-level” award. As in some modern games, where you can complete a level with different rating (e.g. 1 to 3 stars).

@rubenwardy
Yeah, I'm wondering whether this should actually be displayed in one award as a rating, and the progress to the next rating. So say 1 and 2 are unlocked, all you would see is 2 in the list with a progress bar towards 3.

For straightforward progress, yes, that should be a rating inside the award. (Ratings might be labelled with some MT resources, like bronze, gold, diamonds =) e.g. they may correspond to tool levels, wood→stone→iron→bronze→mese→diamond)


Fatal error when running npx quartz sync --no-pull

Describe the bug
I get the error message when I run the command npx quartz sync --no-pull during installation. I am following the steps on the website and in the youtube video linked.
To Reproduce
Steps to reproduce the behavior:

follow the installation instructions
create a remote repo
as per "In your terminal of choice, navigate to the root of your Quartz folder. " I go to the content folder, this i also see in the linked youtube video.
add the remote origin as instructed (as https)
run the npx command
see error:

node:fs:581
return binding.open(
^
Error: ENOENT: no such file or directory, open './package.json'
at Object.openSync (node:fs:581:18)
at readFileSync (node:fs:460:35)
at file:///home/wiebo/fighting-computers/quartz/quartz/cli/constants.js:14:39
at ModuleJob.run (node:internal/modules/esm/module_job:218:25)
at async ModuleLoader.import (node:internal/modules/esm/loader:323:24)
at async loadESM (node:internal/process/esm_loader:28:7)
at async handleMainPromise (node:internal/modules/run_main:120:12) {
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: './package.json'
}
the file package.json is indeed not present in the folder with the other json files  in the 'cli' folder.
Expected behavior
I expect to see the sync and the adding of files in the content folder. this does not happen. the script stops.
Screenshots and Source
none.
You can help speed up fixing the problem by either

providing a simple reproduction
linking to your Quartz repository where the problem can be observed

Desktop (please complete the following information):

Quartz Version: 4.something ( github pull on 2024-01-26)
node Version: v21.6.1
npm version:  v10.2.4
OS: Linux Mint
Browser: firefox

Additional context
Add any other context about the problem here.

You need to run it from the root, not from the content folder. Can you show the output of the ls command?

You are absolutely right, I used the wrong folder. When I run the command in the root folder of quartz, it works. I'm so sorry for wasting your time. I'll close this issue.

No worries, this is what troubleshooting is for :)


Confluence Serialization of lists is broken

Hi,
when generating a page with a bullet list, everything following the list is also part of the list as the list is not properly terminated by a new line ('\n').
Further there is no support for numbered lists yet.

fixed in pull request fix for issue #89


Syntax error on line 56 of /etc/modsecurity/rules/REQUEST-941-APPLICATION-ATTACK-XSS.conf

Hi,
I have installed version 3 of the modsecurity rules and when I start the apache server I get this error below;
service apache2 restart

Restarting web server apache2                                                                                [fail]
The apache2 configtest failed.
Output of config test was:
AH00526: Syntax error on line 56 of /etc/modsecurity/rules/REQUEST-941-APPLICATION-ATTACK-XSS.conf:
Error creating rule: Failed to resolve operator: detectXSS
Action 'configtest' failed.
The Apache error log may have more information.

Line 56 of the suspect conf file is setvar:tx.%{rule.id}-OWASP_CRS/WEB_ATTACK/XSS-%{matched_var_name}=%{tx.0}"
The apache log do not seem to indicate much as to the cause of this error;
tail -f /var/log/apache2/error.log  [Tue Feb 07 17:15:25.172925 2017] [core:notice] [pid 1263] AH00094: Command line: '/usr/sbin/apache2' [Tue Feb 07 17:26:08.825041 2017] [mpm_prefork:notice] [pid 1263] AH00169: caught SIGTERM, shutting down [Tue Feb 07 17:26:10.000216 2017] [:notice] [pid 1829] ModSecurity for Apache/2.7.7 (http://www.modsecurity.org/) configured. [Tue Feb 07 17:26:10.000355 2017] [:notice] [pid 1829] ModSecurity: APR compiled version="1.5.1-dev"; loaded version="1.5.1-dev" [Tue Feb 07 17:26:10.000360 2017] [:notice] [pid 1829] ModSecurity: PCRE compiled version="8.31 "; loaded version="8.31 2012-07-06" [Tue Feb 07 17:26:10.000367 2017] [:notice] [pid 1829] ModSecurity: LUA compiled version="Lua 5.1" [Tue Feb 07 17:26:10.000369 2017] [:notice] [pid 1829] ModSecurity: LIBXML compiled version="2.9.1" [Tue Feb 07 17:26:11.003272 2017] [mpm_prefork:notice] [pid 1830] AH00163: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations [Tue Feb 07 17:26:11.003344 2017] [core:notice] [pid 1830] AH00094: Command line: '/usr/sbin/apache2' [Tue Feb 07 18:02:48.775470 2017] [mpm_prefork:notice] [pid 1830] AH00169: caught SIGTERM, shutting down
I am not quite sure how to debug this error further and I need help. Thanks.

The OWASP Core Rule Set v3.0.0 requires a modern version (less than a few years old) of ModSecurity 2.8 or greater. Prior to this time libinjection wasn't part of the modsecurity platform. This is likely why you are seeing this message. Please update your ModSecurity :)


Dynamic URLs

By submitting this PR, I am indicating to the Numberscope maintainers that I have read and understood the contributing guidelines and that this PR follows those guidelines to the best of my knowledge. I have also read the pull request checklist and followed the instructions therein.

This PR is first in the PR merge chain.
URLs
Specimen

Changed the constructor to automatically pull from the export modules instead of requiring an already constructed visualizer and sequence to be passed in.
Changes getters and setters to reflect that keys are the primary way to interface with the specimen now.
Adds a fromURL function that constructs a specimen from a url.

Scope

Updates URL when changes are made to a sequence/visualizer.

Sequences

Are either a family (constructed for each specimen) or an instance (singleton for all)
Each export module contains a default name and description dedicated for the gallery and modal switchers (this applies as well to visualizers)

Thanks for submitting these PRs and clearly marking the desired merge order. I will start by reviewing this one. If we don't get through the usual back-and-forth of review for the end of the semester, we will take it from whatever point we do reach.
But one initial question about this PR: a good fraction of the changes consist of changing the export modules of sequences and visualizers to get their names and descriptions from constants in their source files, rather than from properties of the classes that define them, roughly reverting a change from the prior PR. It would help us to understand:
(a) What is the motivation for these changes?
(b) Are they needed for the URL encoding/decoding of Specimen parameters, or is it a separate change that happened to be included in this PR?

(a) What is the motivation for these changes?

Ah, I think I understand now. I think it is because the approach from the previous PR actually simply didn't work, even though it typechecked and compiled and seemed to run. I will continue the review on that basis, although I am unfortunately out of time for tonight.

OK, I have found the URLs to update and load correctly across some different Visualizers and Sequences. I could not "trick" the system into producing a bad URL by e.g. entering a formula that would not parse and then copying the URL. This seems to work well and be reasonably limited in scope. So I am comfortable with merging it as soon as the above code review comments are addressed. I am willing to add a commit or two that addresses them myself in the interest of expediency, if that seems reasonable to either @katestange or @Vectornaut, so please just let me know (or the team can just go ahead and address them if someone has time). Thanks!

OK, I have found the URLs to update and load correctly across some different Visualizers and Sequences. I could not "trick" the system into producing a bad URL by e.g. entering a formula that would not parse and then copying the URL. This seems to work well and be reasonably limited in scope. So I am comfortable with merging it as soon as the above code review comments are addressed. I am willing to add a commit or two that addresses them myself in the interest of expediency, if that seems reasonable to either @katestange or @Vectornaut, so please just let me know (or the team can just go ahead and address them if someone has time). Thanks!

I would say go for it @gwhitney , that way if something more important to contact the delft team about lies in wait in a later PR, we are more likely to get to it while we still have some contact with them.  That was a complicated sentence, sorry.  Also, you have all the changes fresh in mind and they look fairly simple (merge errors etc).

OK, in progress, one small commit out of roughly 3 projected.

OK, have made all of the suggested changes. Merging.


Feature/add food list

Hi @Ellon-M
In this PR, the following milestones have been implemented:

[x] Built login page and registration page using devise
[x] Food list
Should display a list of food added by the logged-in user as in the wireframe
Should lead to a form that allows users to add new food

APPROVED! 🏆
Hi @willy836  👋
Your project is complete ✔
There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉

Cheers and Happy coding!👏👏👏


Remove useless frame setting

The frame is already set by calling  super.init(frame: frame) above.
It makes no sense to set the same value again. 👍

Hey,
fixed this in v2.4.3, thank you for the suggestion.

Hey,
fixed this in v2.4.3, thank you for the suggestion.


'steps' property may be invalid

https://github.com/PoslinskiNet/ember-introjs#1-declare-your-steps
This section seems useless, intro can't find the elements that defined in controller.

Thanks for the catch @Ghostubborn. It was confusing a little. I've updated README so now it should be easier to determinate the fact, that there are 2 different approaches to use this package to get an intro in your application.


User Profile picture

Just a small add-on to add profile pictures to users.
To avoid errors :

Add “pictures” folder to content
Add "picture" to admin entry in database

Can be seen on http://zerokeyboard.com/blog

Hi Xavier, I am changin the admin panel and other components because of this the branch is in conflicts. Thanks.

OK let me know when I should update this and repull

Implemented.

Nice ! Keep the good work !


Broken Filter when selecting part of graph

I selected part of the graph to drill down to see where an error was happening and I got an error loading stats.
Something annoying was it took me a while to realise that my search had actually caused an error, I got a message about stats not working but I didn't really click that it was to do with the filter, it would be cool if the colour of the icons on the top bar could turn red if this kind of error happened for example.
The request:
http://.../api/v2/stats?filter=fixed:false+hidden:false&offset=60&time=2015-02-20T17:45:59-2015-02-20T18:12:36

The Response:
{
  "message": "An error has occurred. Please check your search filter."
}

That search query looks right does it still error out every time? I'm not seeing any failures on our server side for stats (we log all of them).
Yeah, I agree there should be some kind of visual clue that the search filter might be bad but I'm not sure when we should highlight the ui for it. The query could fail for a number of reasons not related to the search filter.

It errors everytime.

Yeah, I'll try a few things after the initial 2.0 release and see how we can make this better.

I was able to reproduce the error and I am taking a look into it.


Kirstie TO DO list | 11 September 2019

I'm wildly behind on all my tasks..... so I figured I'd make a master list of everything I need to do! 😱
Autistica Summit

[x] Review applications, call w Lorcan
[ ] 1 page description of "what is AI"

Autistica Citizen Science

[ ] Go through issues & PRs? Ask @GeorgiaHCA to prioritise for me 🙏
[x] Create Heroku account & team & transfer ownership of demo repo
[ ] Tell AH about the demo, check on license

Editing

[ ] Elife
[ ] Neuroimage

Lab stuff

[ ] Merge blog posts
[ ] Write last week's blog post
[ ] Add updates to hackmd
[ ] Update who's who page on website
[ ] Letter of recommendation for JL

Turing Way

[ ] Advertise collab cafe in bulletin
[ ] Advertise reproducible research drop in session in bulletin

BIDS

[ ] Review hackmds

ABCD RR

[ ] Edit overleaf

Heya! For priorities for the issues and PRs - I would say the main ones are probably the September newsletter (in pull requests) - and questions for the focus groups (in issues). The other things like adding contributors and updating ethics docs are probs less urgent :)

Thank you @GeorgiaHCA! Giving me priorities is super super helpful! If you can watch slack tomorrow and Friday I'll try to do bitty things in between talks at the conference 🤞

You're a star THANK YOU :D

Closing - going to start a new one!


Documentation, again

This supercedes #122. Read the build version here.
Still needed:

Examples of using plugins with AD
Documentation of the standard low-level (get, put) and high-level (read, describe) interfaces
Documentation of read_attrs, configuration_attrs

can you put a table at the top of the interactive commands?
in positioners move the positioner entry above the pseudo pos docs so it is adjacent to the example
Signal needs mention that it can be used to inject python-only stuff into Devices
many plugins missing from inheritance diagram

I made the diagram non-comprehensive on purpose. (See the prose above the diagram.) Bad call?

I think those diagrams are most useful when they are comprehensive.  We probably need to turn it to be up-down due to the depth of our tree.

I experimented with left-to-right and top-down and found this way most readable. The knobs controlling font size did not work for me.

self-merging (docs only + a little API import that passes the tests)
remaining issues are not super quick, punting to a future issue -- could be awhile before we return to this

Your arrows are backwards for an inheritance diagram. Children point to their parents. [Example] (http://www.zentut.com/wp-content/uploads/2013/03/php-inheritance-class-diagram.png). I agree with Tom that it should probably be top-to-bottom instead of left-to-right. It is challenging to read on this smartphone
Docs and class diagrams are painful and tedious... Thanks for doing this!

Interesting. This would be an issue with sphinx then. Feel free to report it there and see what they say. Maybe there are different conventions in different subfields?

That is very strange then, because UML class diagrams are pretty clearly specified.


Modify delay time

Hi & thanks for the great project!
One simple question - how can I modify the delay (waiting/pause) time between rechecks? For example, one particular account I follow runs many short lives throughout the day, sometimes even under 5 minutes each. So I'd like to set 2 minute intervals between rechecks, if possible (even with the risk of running into some IP blocking by TT).

For now, it is not possible to do this from the command line.
You can still do it by changing:
AUTOMATIC_MODE = 5
to
AUTOMATIC_MODE = 2
in
https://github.com/Michele0303/TikTok-Live-Recorder/blob/main/enums.py#L12


feat: new icons

This PR adds an icon for the topic "Gewalterfahrung" and uses a more general, fitting icon for "Schwangerschaft".

:tada: This PR is included in version 1.2.0-rc.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


npm install -g create-react-app fails

I am trying to create a new react project with

npm install -g create-react-app create-react-app my-app

but I get an error as such :

[3/4] Linking dependencies...
[4/4] Building fresh packages...
[1/1] ⡀ uglifyjs-webpack-plugin
[-/1] ⡀ waiting...
[-/1] ⡀ waiting...
[-/1] ⡀ waiting...
error C:\Users\shaha\my-app\node_modules\uglifyjs-webpack-plugin: Command failed.
Exit code: 1
Command: node lib/post_install.js
Arguments:
Directory: C:\Users\shaha\my-app\node_modules\uglifyjs-webpack-plugin
Output:
internal/modules/cjs/loader.js:550
throw err;
^
Error: Cannot find module 'C:\Users\shaha\my-app\node_modules\uglifyjs-webpack-plugin\lib\post_install.js'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:548:15)
at Function.Module._load (internal/modules/cjs/loader.js:475:25)

I am using NPM version

C:\Users\shaha>npm --version
5.6.0

and since it installs all the dependencies , it is painstaking for me to go through every configuration manually with yarn
same deal is faced with

npx create-react-app my-app

could you help me overcome this issue ?

Can you check if this npx -p create-react-app -c "create-react-app my-app --use-npm" works for you?

and since it installs all the dependencies , it is painstaking for me to go through every configuration manually with yarn

I don't understand what this means.
If you're experiencing npm bugs, you can install Yarn. Then you can run yarn create react-app myapp and it will use Yarn automatically.
Unfortunately we can't fix npm bugs. What you describe looks like one.

Yarn has also failed me

C:\Users\shaha\Desktop>yarn create react-app zxc
yarn create v1.6.0
[1/4] Resolving packages...
[2/4] Fetching packages...
warning Pattern ["object-assign@latest"] is trying to unpack in the same destination "C:\Users\shaha\AppData\Local\Yarn\Cache\v1
pm-object-assign-4.1.1-2109adc7965887cfc05cbbd442cac8bfbb360863" as pattern ["object-assign@^4.1.0","object-assign@^4"]. This could result in non-deterministic behavior, skipping.
info<EMAIL_ADDRESS>The platform "win32" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Installed<EMAIL_ADDRESS>with binaries:
- create-react-app
[#############################################################################################################] 296/296internal/modules/cjs/loader.js:550
throw err;
^
Error: Cannot find module 'commander'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:548:15)
at Function.Module._load (internal/modules/cjs/loader.js:475:25)
at Module.require (internal/modules/cjs/loader.js:598:17)
at require (internal/modules/cjs/helpers.js:11:18)
at Object. (C:\Users\shaha\AppData\Local\Yarn\Data\global\node_modules\create-react-app\createReactApp.js:39:19)
at Module._compile (internal/modules/cjs/loader.js:654:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:665:10)
at Module.load (internal/modules/cjs/loader.js:566:32)
at tryModuleLoad (internal/modules/cjs/loader.js:506:12)
at Function.Module._load (internal/modules/cjs/loader.js:498:3)
error Command failed.
Exit code: 1
Command: C:\Users\shaha\AppData\Local\Yarn\bin\create-react-app
Arguments: zxc
Directory: C:\Users\shaha\Desktop
Output:
info Visit https://yarnpkg.com/en/docs/cli/create for documentation about this command.

Can you check if this npx -p create-react-app -c "create-react-app my-app --use-npm" works for you?

This actually worked , Wow , I am amazed , I had 0 expectation

I had another weird error with create-react-app breaking down. Confirming - That command worked! Wonderful! Thank you very much.


Support automatic delegating for client registered extensions

Adds general support for routing service extension requests to the clients which registered them via the vm service protocol. The service implementations will never see these requests - they will get routed to the appropriate clients instead.
Note that this is only for services registered via the service protocol, extensions can also be registered via dart:developer and those will still be forwarded to the service implementation.

Renamed VmServer to VmServerConnection - you should create one of these for each client that connects (it only handled one client at a time before, the new name is just to make that more clear).

The service and registry fields should be shared across these connections, unless you have multiple instances of the service.

Added a ServiceExtensionRegistry class which maps registered extensions to the clients in which they were registered.

Note that you should view this PR without whitespace diffs (add w=1 as a query param to the url).


how to run dist() in spark

i had a big dataset, dim(dataset)= 80000+ ,700+
i wanna dist(dataset) , but it takes too large memory costs .
is there a way to accomplish it with spark(standalone) or tensorflow?
@javierluraschi

See https://stackoverflow.com/questions/37809834/how-to-compute-the-distance-matrix-in-spark, doesn't seem Spark supports something out of the box.
However, with some work, you might be able to use spark_apply():

First, you would need to partition by row and pass the matrix (since it's not that big) into the context parameter.
Then, you would have to calculate the distance in each row against all entries in the context rows, maybe using purrr and dist() between every two row combinations.


KYLIN-4041 minor,fix it

Can one of the admins verify this patch?

Codecov Report

Merging #714 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master    #714      +/-   ##
===========================================
+ Coverage      25.7%   25.7%   +<.01%
- Complexity     6012    6013       +1
===========================================
  Files          1386    1386
  Lines         82513   82513
  Branches      11568   11568
===========================================
+ Hits          21206   21214       +8
+ Misses        59262   59252      -10
- Partials       2045    2047       +2

Impacted Files
Coverage Δ
Complexity Δ

...he/kylin/job/impl/threadpool/DefaultScheduler.java
74.41% <0%> (-2.33%)
12% <0%> (ø)

...rg/apache/kylin/cube/inmemcubing/MemDiskStore.java
70.21% <0%> (+0.91%)
7% <0%> (ø)
:arrow_down:

...eam/core/storage/columnar/DataSegmentFragment.java
59.01% <0%> (+1.63%)
18% <0%> (+1%)
:arrow_up:

.../apache/kylin/cube/cuboid/TreeCuboidScheduler.java
66.15% <0%> (+2.3%)
0% <0%> (ø)
:arrow_down:

...ream/core/storage/columnar/ColumnarStoreCache.java
54.65% <0%> (+3.48%)
8% <0%> (ø)
:arrow_down:

Continue to review full report at Codecov.

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

Pull Request Test Coverage Report for Build 4665

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.004%) to 28.186%

Files with Coverage Reduction
New Missed Lines
%

core-cube/src/main/java/org/apache/kylin/cube/inmemcubing/MemDiskStore.java
3
78.42%

Totals

Change from base Build 4660:
0.004%

Covered Lines:
23257

Relevant Lines:
82513

💛  - Coveralls


[full-ci] Remove Resharing

Removes resharing from codebase
Backend part of https://github.com/owncloud/ocis/issues/8744

When I created a view only user share for file in a project space it becomes a share with custom permissions with this PR. IS that intended? Why does it not detect the view permission? Are the heuristics broken?

Seems to have been a hiccup. I cannot reproduce.


settings to use dedicated card by default in PRIME machines

I successfully installed this on an older dell xps with the 37-470 line of drivers. The laptop runs 100% of the time powered by ac and I’m wondering what kind of configuration could be done to make the dedicated gpu the default so the desktop experience and all apps are launched running off the nvidia. Ideally gnome would be accelerated along with video players and ff/chrome etc.
Thanks!

I actually figured this out,  but just a warning, setting this up is what led to #200. But, if you really want to do this:

Open  /etc/supergfx.conf (I think thats the name, it's there, you might have to poke around a bit with shell autocompletion), and change the default mode from "Hybrid" to "NvidiaNoModeset."
Create /etc/udev/rules.d/61-mutter-default-gpu.rules and put the line from here in it.
Reboot


Website update

Add a sidebar on the right with the table of contents
When on mobile, the right sidebar appears together with the left sidebar and each one takes 50% of the screen. so it is a fullscreen menu now!
Add a new style for the color scheme switch (now, it is on the right sidebar)
Style home page actions

Since the start idea was to make a single page with all the documentation, i made the table of content h2 titles disappear when it's h1 title wasn't active, because it could get quite big. That's not necessary anymore, so this feature was removed.
For some reason, the favicon didn't have a transparent background. Now it's fixed!

For some reason, the favicon didn't have a transparent background. Now it's fixed!

I deliberately gave it a background (It should have been noted in one of my previous PRs). In a dark mode browser the favicon looks really bad because the black is invisible.

Didn't notice, sorry. i'll revert the commit

All good! I think the one I replaced it with still looks pretty bad. Is there some variant you think would look good on a light/dark background?

(Your changes look great though! Feel free to merge whenever you like)

@sebmck Next update, i'll try all yellow and see how it looks!


first_etcd check

Check there's a first_etcd set

only_if { node['cookbook-openshift3']['openshift_HA'] }
may need to be added to the upgrade code - I noticed this when running the upgrade on a simple single-master setup.

Need to test this first.


Question about UUID

While implementing ULink library, I found some weird behaviors on validating UUID.
After some tracing, I'm not quite sure about the implementation here. It seems like it doesn't correspond to protocol-spec.
https://github.com/eclipse-uprotocol/uprotocol-rust/blob/main/src/proto/uprotocol/uuid.rs#L77
To be more specific, my questions are

Why do we need to check the version is Version::Custom here?
Is there any expected way to generate UUID that can pass is_uprotocol_uuid?

Older versions of the protocol used v6 so for Java we had to support both, for Rust I think you're safe to be v8 (platforms are being updated now to support v8 using the newer sdks)
You cannot build it with rust SDK but if you are passed a different format UUID you need to make sure it is formatted correctly per the spec.

2. Is there any expected way to generate UUID that can pass is_uprotocol_uuid?

Hi @evshary , do you mean that sentence exactly like that? If yes, the expected way to generate such a UUID is the uuidbuilder.rs/UUIDv8Builder. In case there is a 'not' missing from your question, Steven answered that in his comment ;-)

Hi @evshary , do you mean that sentence exactly like that? If yes, the expected way to generate such a UUID is the uuidbuilder.rs/UUIDv8Builder. In case there is a 'not' missing from your question, Steven answered that in his comment ;-)

Thanks! That's exactly what I want.
Although I still don't quite understand how is_uprotocol_uuid works (why do we need to compare the version of UUID with Version::Custom), I think the information is enough for me to continue the project.


Live stream crash after update

Hi
Updated Homebridge
updated Homebridge-Nest-cam
and now all of a sudden my live stream of cameras are crashing. Running the setup on RPi3. Was working fine before the update.
this is the crash:
/usr/lib/node_modules/homebridge-nest-cam/lib/streamer.js:339
let ssrc = crypto.randomBytes(4).readUInt32BE(0, true);
^
ReferenceError: crypto is not defined
at NexusStreamer.prepareStream (/usr/lib/node_modules/homebridge-nest-cam/lib/streamer.js:339:18)
at NestCam.prepareStream (/usr/lib/node_modules/homebridge-nest-cam/lib/nestcam.js:115:14)
at StreamController._handleSetupWrite (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/StreamController.js:540:23)
at Characteristic.SetupEndpoints. (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/StreamController.js:271:12)
at emitMany (events.js:147:13)
at Characteristic.SetupEndpoints.emit (events.js:224:7)
at Characteristic.SetupEndpoints.Characteristic.setValue (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Characteristic.js:319:10)
at Accessory. (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:867:22)
at Array.forEach ()
at Accessory._handleSetCharacteristics (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:807:8)
What could be the issue?
Here are the npm version details
{ npm: '5.5.1',
ares: '1.10.1-DEV',
cldr: '31.0.1',
http_parser: '2.7.0',
icu: '59.1',
modules: '57',
nghttp2: '1.25.0',
node: '8.9.1',
openssl: '1.0.2m',
tz: '2017b',
unicode: '9.0',
uv: '1.15.0',
v8: '6.1.534.47',
zlib: '1.2.11' }

Sorry. Please try the updated v0.0.7.

Huh this is interesting. Would you mind give v0.0.9 a try?

Updated. Seems to be working much more reliably now. Tried loading 3 different streams from 3 different cameras and all loaded live stream in under 10 seconds on first try! Thank you so much for such quick response and fix!

No problem! Feel free to re-open the issue if this happens again.


Update accessibility-report.md

I updated the wording of the Accessibility report to make it more clear to the reader.


Imperfect parts

1、No "second" item can be selected for user.
2、can't select year,month,or day item respectively.

can you make a pull request for that ?


CIP-0095 | Misspelling of DeprecatedCertificate

Minor wording improvements to the standard committed alongside.

@nilscodes I'm backing out my previous ✅ for these changes until we can be sure you are done force-pushing to this branch.  Please post here when you're done making changes and then we'll get all the editors to make an assessment of it.

Hey Robert - yeah, I had already reached out to @Ryun1 to talk about this. To be honest, wanted to make a draft into my own repo before making the official MR, but GitHub snuck up on me. There will be no further force pushing, and I'll update y'all here on the conversations with Ryan, he said he might reply directly, too.

Great catches @nilscodes
thanks for taking the time and creating this PR
I do worry that changing the error codes could break existing compatibility, although more likely to break dApp handelling of the errorcode than wallets
I will reach out to known implementors and make sure that this is okay (tagging a few @Scitz0, @refi93, @mchappell, @mirceahasegan)

Great catches @nilscodes thanks for taking the time and creating this PR
I do worry that changing the error codes could break existing compatibility, although more likely to break dApp handelling of the errorcode than wallets I will reach out to known implementors and make sure that this is okay (tagging a few @Scitz0, @refi93, @mchappell, @mirceahasegan)

Sounds good. I've already reached out to Eternl, since their non english speaking nature may not have alerted them to the misspell. Also, it may be that the implementers used the correct spelling and did not even realize the misspell in the CIP, leading to inconsistent implementations.
I just pushed some more changes, based on the clarity of the DRepID / DRepPublicKey ordering in CIP-0105 to clarify one depends on the other, and proposed a clarification in the first paragraph as indicated by my comment before. Let me know if that works.

We will/have made the change in error response to DeprecatedCertificate in Eternl. We just used error codes as defined in CIP initially even though I fully agree with the change.

I just pushed some more changes, based on the clarity of the DRepID / DRepPublicKey ordering in CIP-0105 to clarify one depends on the other, and proposed a clarification in the first paragraph as indicated by my comment before. Let me know if that works.

How does this align with CIP-129 regarding DRep ID definition?

CIP-129

Yeah, I have not changed any of the definitions, just reordered them to match CIP-0105 (because the DRepID is derived from the DrepPubKey). And I don't believe CIP-0129 contains any references to the error codes. Thanks for getting back on this so quickly 🙏
~ Nils

How does this align with CIP-129 regarding DRep ID definition?
I guess that's its own CIP and should not impact this one.

Since CIP95 returns just pub keys, without any encoding CIP129 (if adopted) shouldnt impact it

Great catches @nilscodes thanks for taking the time and creating this PR
I do worry that changing the error codes could break existing compatibility, although more likely to break dApp handelling of the errorcode than wallets I will reach out to known implementors and make sure that this is okay (tagging a few @Scitz0, @refi93, @mchappell, @mirceahasegan)

No issue from Lace side. Thank you for tagging me!

As this one hasn't been merged yet, I propose another change to CIP-95 regarding signData.
Its currently defined as:

To construct an address for DRep Key, the client application should construct a type 6 address. Using an appropriate Network Tag and a hash of a public DRep Key.

This is NOT how for example Ledger has implemented signData. No address %b0110 | NETWORK-TAG is added to the protected header address field, just the raw key hash bytes. I think this makes sense. Why try to treat a key, be it pool, drep, cc_hot or cc_cold as an address when its not?

that sounds like a good point (https://github.com/cardano-foundation/CIPs/pull/875#issuecomment-2275998500) @Scitz0 - can you submit a PR for it, or open an issue if you think the approach to such a change is debatable or needs clarification / confirmation first?

that sounds like a good point (#875 (comment)) @Scitz0 - can you submit a PR for it, or open an issue if you think the approach to such a change is debatable or needs clarification / confirmation first?

I would, if it weren't for the fact that I leave for a 1½ week vacation in the morning. So if someone else has the time, feel free to do so... else it will have to wait a bit.

that sounds like a good point (#875 (comment)) @Scitz0 - can you submit a PR for it, or open an issue if you think the approach to such a change is debatable or needs clarification / confirmation first?

I would, if it weren't for the fact that I leave for a 1½ week vacation in the morning. So if someone else has the time, feel free to do so... else it will have to wait a bit.

I would do it, if I felt confident I knew exactly what to change, but I'm not deep enough in the material unfortunately. Maybe @Ryun1 can help out?

@nilscodes it seems proper based on the last https://github.com/cardano-foundation/CIPs/pull/875#issuecomment-2284222377 to tag this Waiting for Author (and we do have to keep it tagged something) but @Ryun1 we are also waiting for you to advise 100% one way or the other about whether to merge this... avoiding compounded difficulties, which I think are not likely to get better as long as the misspelling persists... or disqualifying the correction in the name of backward compatibility.

@nilscodes it seems proper based on the last #875 (comment) to tag this Waiting for Author (and we do have to keep it tagged something) but @Ryun1 we are also waiting for you to advise 100% one way or the other about whether to merge this... avoiding compounded difficulties, which I think are not likely to get better as long as the misspelling persists... or disqualifying the correction in the name of backward compatibility.

Since the comment from @Scitz0 was not primarily related to my changes, not sure this MR should wait for it - here we really should finalize if we change the error codes or not. Not a lot of tooling is using any of this yet, most affected would be wallets and potentially MeshSDK.

Since the comment from @Scitz0 was not primarily related to my changes, not sure this MR should wait for it - here we really should finalize if we change the error codes or not. Not a lot of tooling is using any of this yet, most affected would be wallets and potentially MeshSDK.

Agree, I created a separate PR for that change now here https://github.com/cardano-foundation/CIPs/pull/897.


Access to the path 'C:\Run\Collation.txt' is denied.

We have problems with docker 4.7.1 and differents version of Windows 10 and Windows 11. It's not possible to create a container. We are using next script:
$ContainerName = 'namecontainer'
$imageName = 'bc'
$artifactUrl = Get-BCArtifactUrl -country 'es' -type "Sandbox"
$licenseFile = 'C:\License.flf'
$UserName = 'name'
$Password = ConvertTo-SecureString "pass123" -AsPlainText -Force
$Credential = New-Object System.Management.Automation.PSCredential ($UserName, $Password)
New-BCContainer -accept_eula                  -containername $containername
-auth NavUserPassword                  -Credential $credential
-assignPremiumPlan                  -multitenant: $false
-imageName $imageName                  -artifactUrl $artifactUrl
-licenseFile $licenseFile                  -accept_outdated
-updateHosts -isolation hyperv `
-additionalParameters @("--env CustomNavSettings=EnableThreadThrottling=False,EnablePrioritizedThreadThrottling=False") #para evitar errores en debugge

I am seeing the same error after upgrading to BcContainerHelper 3.0.6. I managed to set up a container yesterday (with real-time protection disabled) with 3.0.5.

I finally uninstalled and installed docker again and it let me create the container. Thank you!


Fixed dark mode bug in image_classification/ios

Fixed invisible string in dark mode.

@googlebot I signed it!

@googlebot I signed it!

Please unsubscribe me. I did several Times but it did. Not work!
Tranks
SH
Von meinem iPhone gesendet

Am 20.03.2020 um 22:56 schrieb Koki Nishihara<EMAIL_ADDRESS>
Reopened #177.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

@jdduke @yyoon @lintian06
What do you think should I do?

@yyoon
Thank you for testing and reviewing : D