An action could not be found at the URI 'https://api.github.com/repos/actions/setup-node/tarball/v2

Hi, i've tried create action based on first example, but constantly have failed job starting
An action could not be found at the URI 'https://api.github.com/repos/actions/setup-node/tarball/v2'
My workflow

name: CI

# Controls when the action will run. Triggers the workflow on push or pull request
# events but only for the master branch
on:
  push:
    branches: [ master ]
  pull_request:
    branches: [ master ]

# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
  # This workflow contains a single job called "build"
  build:
    # The type of runner that the job will run on
    runs-on: ubuntu-latest

    # Steps represent a sequence of tasks that will be executed as part of the job
    steps:
      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
      - uses: actions/checkout@v2

      - uses: actions/setup-node@v2
        with:
          node-version: '12'
          check-latest: true

      - run: node --versrion |
          npm --version

very generic.
i will try to use @1 version, but overall situation is quite strange - if v2 is not available you probably should remove example which uses v2 action. Or do some other thing.

Yes it's quite problematic. v2-beta resolves to an older beta. While v2 doesn't resolve to anything. I ended up using v2.1.1 as it's the latest v2 beta. However, I'd rather not include a specific version.

Hello everyone!
We have recently released stable actions/setup-node@v2 that points to v2.1.4 that is marked as stable too.
I am closing this issue but please let me know if you have any concerns.


VirtualDevice expose .available()

Implements the available() on VirtualDevice to match methods exposed on Device. Fixes #278
.available() returns state based on what the cloud thinks the state of the device is on a hub getting info from logs topic stream and the return from a transition call. There could be times where the state does not line up.

+1


Content Layer page does not exist

When I tried to see what is in the link it gives me 404, so this is a broken link that need to be fixed 🙂
and also I see that 404 page does not have any UI

Links:
https://tx.shadcn.com/docs
https://tx.shadcn.com/docs/documentation/contentlayer

Hi @alieldeba , I don't think this is an issue, the creator is trying to create a new page with (/docs/documentation/contentlayer) instead of redirecting the user to contentLayers.dev. Please correct me if I am wrong. I found the cause though.

Hi @alieldeba , I don't think this is an issue, the creator is trying to create a new page with (/docs/documentation/contentlayer)which he has still not created as repo itself mentions that work is still in progress instead of redirecting the user to (contentlayers.dev.) Please correct me if I am wrong. I found the cause though.

oh if that is the case it is ok I thought that content layer page were deleted and he forgot to remove its links


Update samples to consume new features

Related Issue
Resolves 35357399 and 35368881, tracked in #5655
Description
Update Inputs.json and InputForm.json to use new features like label and errorMessage, to close the issues listed in #5655
How Verified
Manual verification

Does the version number at the top of the file need to be updated? The label attribute seems to be working fine without updating the version number but I'm not sure if we should still update it for consistency?

Just blocking over this comment. We definitely should update the version number because an author may copy-and-paste this card directly and expect it to work in 1.0. For reference, unsupported features are generally just dropped. So if you took this new card and put it in a v1.0 renderer, the label should just be dropped entirely (wow, so this card would look really bad haha).
A question I have though is, should we move this card out of the v1.0 folder then? Would that be bad for testing? Need insight from @paulcam206 Paul Campbell (DXP) FTE or @licanhua CanHua Li FTE here.

I think in this case it's probably fine to leave it (or update if you feel like pushing another commit) -- labels shipped long enough ago that at this point all major partners support them.
As for the various vX.X folders, we don't actually enforce anything based on the file path of the card, so it can stay in v1.0 :)

actually, I think the right fix here is to just delete these two samples. double-check me on this, but I believe we have InputsWithLabels.json and InputFormWithLabels.json that are the labeled versions of these...

That's a good call! Deleted the files


Don't log buffer on network send errors by default

Exposes a new environment flag DEBUG_LOG_BUFFERS, which when set to 1 will log the full payload.
If not set, the payload will be logged as:
{ "type": "Buffer", "data": "[filtered]"}

Fixes #172
@paambaati

I like the change but I think it will be hard to remember where the special env vars are, so any thoughts about where to keep this variable? I understand that the connection is where it's used, but I think having "random" envs lurking through the code will make it hard to maintain.

I had the same thought about where to put it. I considered resolving it somewhere high up and then pass it all the way down to the connection, but then testing that it gets passed all the way through the connection builder etc is a hassle. Another option I considered was to actually put it in the logger, but then I'd have to check recursively for buffers, which I most certainly don't want to do for performance reasons.
Let's chat and figure out where to put it.


Removed ONT code.

Closes #
Changes proposed in this pull request:

...

Kind of sad to see the GraphQL code disappearing 😞


Optimize planner to avoid excessive schema transform functions

Is your feature request related to a problem or challenge?
it was found that the planner calling schema transform functions excessively.
Experiment, lets take a simple query
        let sql = "select a, a + 1 b from (select 1 a union all select 2 a) x";

And increase rows in the x subquery by adding more and more rows, and we can see that schema function grows with every record

rows
new_with_metadata
merge

2
58
35

3
131
83

4
165
109

IMHO That is not expected, once the plan has built the schema calls should not increase with every new record in the dataset
Describe the solution you'd like
Ideally resolve excessive, more real is to reduce such calls
Describe alternatives you've considered
No response
Additional context
Follow up on https://github.com/apache/arrow-datafusion/pull/9104 investigations

The same basically happens with table
create table t1 as (select 1 a union all select 2 a )
let sql: &str = "select a, a + 1 b, a+2 from t1";

It seems planner phase like schema transform affects execution phase

Update: reading from table or parquet doesn't cause exponential schema calls growth.
Queries with literals causes that like
let sql = "select a, a + 1, a+2 b from (select 1 a union all select 2 a union all select 3 a union all select 4 a union all select 5 a union all select 6 a)";

But this is rare and won't be that critical.
However for reading parquet and tables another problem arises with wild card expansion
adding outer select * adds 50 new calls to with_new_metadata
    let sql = "select * from (select * from (select * from (select * from (select * from (select a, a+1, a+2, a+3, a+4, a+5, a+6, a+7, a+8, a+9 from t1)))))";

makes 359 calls


Implement FileContentsQuery

Description:
This PR adds the APIs associated with GetFileContents (aka FileContentsQuery), as well as tests and an accompanying example (GetFileContentsExample.cc).
Related issue(s):
Fixes #322
Checklist

[x] Documented (Code comments, README, etc.)
[x] Tested (unit, integration, etc.)

I ran all of the tests locally to double-check. Every test passed successfully.


rm: rm3.sh now passes

Changed the use of hard-coded prompts messages to use uucore::util_name instead
Rewrote prompt_write_protected and prompt_file into a single function prompt_file because I a lot of the code was being reused for both

Broke branch will have to make a new one


Smoke tests for Mac do not complete

CI is not passing as a result of this.

@DonJayamanne are you looking at this?

No

This doesn't seem to be a problem anymore.


Nicer error message if missing configuration

Wraps the error to give a bit more context, from this:
❯ gh slack auth
Error: could not find key "extensions"
To:
❯ gh slack auth
Error: failed to read gh-slack configuration: could not find key "extensions"

Oh nice, thanks! Is it also possible to include the path that it tries to load it from?

I've had a go at that and the error message now reads like:

Error: failed to read gh-slack configuration value "extensions.slack.team" from "/Users/rneatherway/.config/gh/config.yml": could not find key "slack"

What do you think of that?

Reads great, thanks for taking care of that!


tests: add integ test for mlflow-image module

Describe your changes

add integ test for mlflow-image module

Checklist before requesting a review

[ ] I updated CHANGELOG.MD with a description of my changes
[ ] If the change was to a module, I ran the code validation script (scripts/validate.sh)
[ ] If the change was to a module, I have added thorough tests
[ ] If the change was to a module, I have added/updated the module's README.md
[ ] If a module was added, I added a reference to the module to the repository's README.md
[ ] I verified that my code deploys successfully using seedfarmer apply

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: 439f2fd2495b4bd8cfc27f410016bca7eeb6bcb6
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: a011675376f9e07ebbd29748db28676a8bff8685
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: 6780d8bef48c552643585a3221370f6674a2d68b
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: 6780d8bef48c552643585a3221370f6674a2d68b
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: 6780d8bef48c552643585a3221370f6674a2d68b
Result: FAILED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: 3a106e71cba556279aaadc87e70acfcdf9567192
Result: SUCCEEDED
Build Logs (available for 30 days)

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

Note @LeonLuttenberger  - changelog

AWS CodeBuild CI Report

CodeBuild project: AIOpsModuleTestsInfrastruct-doMLXEYsnmxr
Commit ID: 5e33fe8b8c2e30decc93a7b5fe82beca5e5eab51
Result: SUCCEEDED
Build Logs (available for 30 days)

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


projects:ad7124_iio:Fixing STM Build error

Added stm32_i2c.h in app_config_stm32.h includes.
Corrected chip select Macro in app_config_stm32.c

@SaikiranGudla does this PR look good to merge?


refactor: create executable tx in the gateway process_tx

In this PR we create the executable_tx. This will be a member of MempoolInput.

This change is

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

#520
#519
#518
#517  👈
#516
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @ArniStarkware and the rest of your teammates on  Graphite

crates/gateway/src/gateway.rs line 139 at r1 (raw file):
Previously, ArniStarkware (Arnon Hod) wrote…
error!("Failed to convert Starknet API ClassInfo to Blockifier ClassInfo: {:?}", e);

Done.

crates/gateway/src/utils.rs line 39 at r13 (raw file):
Previously, dafnamatsry wrote…
and then you won't need the clone in the gateway...
In general, I think in most cases we only want to pass references as function arguments (unless you want to enforce that an object can't be used after the function call).

Discussed on DMs. Ignored.
The ownership-taking is by design.

Merge activity

Sep 8, 4:31 AM EDT: @ArniStarkware started a stack merge that includes this pull request via Graphite.


Add Edge collector

I needed to make a new fork for this repo, so I'm going to close this PR and open a new one


chore: :bookmark: release 1.1.0

:robot: I have created a release beep boop
1.1.0 (2024-11-02)
Features

:sparkles: Add background (05305d4)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.1.0
:sunflower:


AttributeError: 'NoneType' object has no attribute 'find'

Several weeks ago I can download images by it on my Mac, but now it suddenly don't work any more.
<urlopen error EOF occurred in violation of protocol (_ssl.c:833)>
Starting Download...
Traceback (most recent call last):
  File "/usr/local/bin/googleimagesdownload", line 11, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.6/site-packages/google_images_download/google_images_download.py", line 893, in main
    paths = response.download(arguments)  #wrapping response in a variable just for consistency
  File "/usr/local/lib/python3.6/site-packages/google_images_download/google_images_download.py", line 848, in download
    items,errorCount,abs_path = self._get_all_items(raw_html,main_directory,dir_name,limit,arguments)    #get all image items and download images
  File "/usr/local/lib/python3.6/site-packages/google_images_download/google_images_download.py", line 697, in _get_all_items
    object, end_content = self._get_next_item(page)
  File "/usr/local/lib/python3.6/site-packages/google_images_download/google_images_download.py", line 662, in _get_next_item
    start_line = s.find('rg_meta notranslate')
AttributeError: 'NoneType' object has no attribute 'find'

@jubyshu can you quickly forward me the complete query you are using? also are you behind a proxy?

closing due to inactivity.


Broken Pipe when Sending TCP Data to Loggly

I am using logspout to stream docker logs into Loggly over TCP.  This is done using the syslog+tcp://logs-01.loggly.com endpoint:
    /usr/bin/docker run --name logspout \
    -v=/var/run/docker.sock:/tmp/docker.sock \
    -e SYSLOG_STRUCTURED_DATA=[LOGGLY_CUSTOMER_TOKEN]@41058  \
    gliderlabs/logspout:master \
    syslog+tcp://logs-01.loggly.com:514

Way too frequently, however, I am seeing a broken pipe message and data streaming from logspout stops.  From the logspout logs:
2015/06/02 01:04:07 syslog: write tcp <IP_ADDRESS>:514: broken pipe
I am assuming this occurs when the Loggly Route 53 ingestion endpoint changes IP and the TCP connection is lost.
Logspout should be updated to attempt to reestablish this connection if it is lost.

This is definitely not a loggly-specific problem. It seems the new adaptor code causes this problem both for TCP and UDP (surprisingly). I am writing to a local syslog endpoint: with v2 or latest (i.e. release branch) I can write UDP, stop the endpoint, restart it, and logspout carries on writing. With master, using either TCP or UDP, if I restart the endpoint the connection is dropped and not recreated.

@rlister, thanks for the feedback.  I have updated to logspout v2 and will give this a shot.  I should be able to confirm in a couple days whether or not this solves my issue (it sounds like it will!).

Any updates on this. I am getting this error too with (raw+tcp)
logspout v3-master by gliderlabs
raw: write tcp :17000: broken pipe

FYI, I was not able to go back to a previous release v2 or latest (i.e. release branch) because it does not support the new endpoint format (to the best of my knowledge):
for example:
syslog+tcp://logs-01.loggly.com:514

Any updates on this?

would love to see this fixed as well. Currently logspout is not trying to reconnect after a broken pipe err, which effectively makes it very unreliable

Is there any workaround for this problem? Once the pipe breaks, I have to manually log in to my instance(s) and restart the logspout container. Not really an acceptable solution...

We're also experiencing this.  Do the adapters themselves need to be rewritten or is this a logspout core problem?

:+1: Have seen this as well...

+1

:+1:

Just saw this again. Not having continuous logs sucks. :-(

:+1: from me, experiencing this in production, and our only workaround is a cronjob that restarts the logspout container every hour. :cry:

I just want to say that after investing a significant amount of time in setting up logspout, we opted to use fluentd with a customized version of the fluent-plugin-docker-format.  This automatically picks up all new Docker containers, is fault-tolerant (if fluentd fails, it just picks up reading off of the docker log files where it picked off), performant, and as customizable as the fluentd plugin ecosystem.
While I like some of the core ideas behind logspout, I believe better solutions are now available.

Just saw this again.
Is this project being maintained?

Sometimes! I would love help. Can somebody confirm #150 fixes this?

I followed the approach from #150 to create a patched version of the logspout-logstash module for which I was seeing the same issue. It fixed the issue in that instance at least.

One more thumbs up?

@progrium Wonderful to hear. I'd love to verify #150 but don't have the Go chops (yet!) to handle that.

Here's another suggestion: instead of logging broken pipe and continuing execution, just exit (with whatever exit code makes sense). Docker and Kubernetes can restart the container automatically, and will keep a count of restarts.

@meonkeys I like the cleanliness of this, but it concerns me that logs may be lost during the switchover.

Yes, normally I'm all about fail fast and letting higher up supervisors
restart, but that would mean potential lost logs. If it couldn't reconnect
after a few tries, I'm happy to have it fail out.
On Fri, Jan 15, 2016 at 7:21 PM, Tom Mornini<EMAIL_ADDRESS>wrote:

@meonkeys https://github.com/meonkeys I like the cleanliness of this,
but it concerns me that logs may be lost during the switchover.
—
Reply to this email directly or view it on GitHub
https://github.com/gliderlabs/logspout/issues/107#issuecomment-172142561
.

--
Jeff Lindsay
http://progrium.com

Ah, got it, that makes sense. I assumed that k8s (or something else) was keeping logs safe/durable.

@meonkeys k8s?

Sorry, k8s is just shorthand for Kubernetes.

@progrium Any chance of cutting a release so I can give you some feedback?

I'd love to see this supported for raw TCP connections as well, instead of just syslog.

Hi currently tcp support for syslog servers is not working or is it work in progress,
I am trying to send container logs to syslog server through
syslog+tcp://:port. the logs are not going. but when i swtich to udp i see that logs start flowing into syslog, i required tcp with logspout. to send logs to syslog server

:+1:

@progrium Here's a report after 17 hours on v3
We deployed to 4 servers 17 hours ago ith syslog+tcp://logs-01.loggly.com:514
3 of the servers are still logging, 1 stopped logging entirely about 8.5 hours ago.
We ran docker logs on the Loggly container that has stopped logging and checked it's log:
# logspout v3 by gliderlabs
# adapters: tcp syslog raw tls udp
# options : persist:/mnt/routes
# jobs    : http[logs,routes]:80 pump
# routes  :
#   ADAPTER	ADDRESS			CONTAINERS	SOURCES	OPTIONS
#   syslog+tcp	logs-01.loggly.com:514				map[]

We checked logs on the rest of the containers and they've been logging the entire time.
So, it's a total mystery as to why the logging has stopped. Based upon previous behavior, we expect the rest of the servers will follow this one to the same condition eventually.

Okay. I have some ideas and at the very least know some simple additions
for better debugging. Anybody willing to sponsor this work?
On Thu, Mar 17, 2016 at 11:44 AM, Tom Mornini<EMAIL_ADDRESS>wrote:

@progrium https://github.com/progrium Here's a report after 17 hours on
v3
We deployed to 4 servers 17 hours ago ith syslog+tcp://
logs-01.loggly.com:514
3 of the servers are still logging, 1 stopped logging entirely about 8.5
hours ago.
We ran docker logs on the Loggly container that has stopped logging and
checked it's log:
logspout v3 by gliderlabs
adapters: tcp syslog raw tls udp
options : persist:/mnt/routes
jobs    : http[logs,routes]:80 pump
routes  :
ADAPTER ADDRESS         CONTAINERS  SOURCES OPTIONS
syslog+tcp  logs-01.loggly.com:514              map[]
We checked logs on the rest of the containers and they've been logging the
entire time.
So, it's a total mystery as to why the logging has stopped. Based upon
previous behavior, we expect the rest of the servers will follow this one
to the same condition eventually.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/gliderlabs/logspout/issues/107#issuecomment-197968968

--
Jeff Lindsay
http://progrium.com

@progrium Yes. I assume you accept Bitcoin?

I ... well I haven't, but I guess I could?
On Fri, Mar 18, 2016 at 1:51 AM, Tom Mornini<EMAIL_ADDRESS>wrote:

@progrium https://github.com/progrium Yes. I assume you accept Bitcoin?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/gliderlabs/logspout/issues/107#issuecomment-198231448

--
Jeff Lindsay
http://progrium.com

@progrium Ok, let's negotiate privately and get this underway!

my username at gmail if you lost my email. :)
On Mon, Mar 21, 2016 at 8:00 PM, Tom Mornini<EMAIL_ADDRESS>wrote:

@progrium https://github.com/progrium Ok, let's negotiate privately and
get this underway!
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/gliderlabs/logspout/issues/107#issuecomment-199567239

--
Jeff Lindsay
http://progrium.com

Please have a look to https://github.com/sematext/sematext-agent-docker it re-connects when the Logsene backend is not reachable, it buffers and re-transmit logs, which could no be shipped. If the connection to Docker Socket is lost the agent re-connects to Docker. Ahh, and the agent can parse your logs adds GeoIP info and gets performance metrics and Docker events. What has it common with Logspout?

Working with the Docker API, means it detects new containers and ships all logs (if no filter is set ...)
Support log routing by Docker Labels or ENV var from containers to full text indices
https://github.com/sematext/sematext-agent-docker#log-routing
We don't take bitcoins, but offer a free plan.

Any news on this @tmornini @progrium? :+1:

@schickling Yes, but not good news unfortunately.
We decided to use the syslog log driver to send the logs to the host where we configured rsyslog to send them through to Loggly.
We just deployed it today, will report back on how it works.
We use ECS, and our host rsyslog config file is at:
https://gist.github.com/tmornini/aa25e93556622b982d473899e5305e33

We've been running 3 days now without issue, the longest continuous and unbroken log stream since we started using Loggly which until now was always via logspout.
We have terrific filtering based upon:

syslog metadata
our metadata
example

TAG
product
subledger, demobot, billing

TAG
environment
ci, production

APP-NAME
task_name-task_version
ecs_task_name-ecs_task_version

MSGID
container_name
https-proxy

HOSTNAME
container_id
4c01db0b339c

PROCID
pid
4507

rsyslog config file gist: https://gist.github.com/tmornini/aa25e93556622b982d473899e5305e33

@tmornini Is there a reason you didn't just configure each local syslog to send directly to Loggly vs sending to a central rsyslog host?
I'm asking because I'm curious about various setup options here.

@josh-padnick I couldn't figure out how to map the metadata I wanted. If I could have, I'd have preferred it that way.
It is nice to have the host logs up in Loggly to, so if we're going to configure the host rsyslog, we might as well use it. :-)
I've updated the gist to include everything required to make this work on ECS.
It's grotesquely inefficient to run al those regexs per log line, and the regex themselves are ripe for tuning, but we're not able to visually detect the additional CPU required, so perhaps it's just not that big a deal. :-)

@tmornini Thanks for clarifying! I thought you were saying you send all logs to a separate server running rsyslog, but now I see you're just going from syslog to rsyslog on the same host.  What's nice is that, according to my understanding, (r)syslog will store logs on disk and have built-in retry for sending logs to a remote destination so it sounds like things are pretty fault-tolerant.
I've also had success running a fluentd daemon on the host that also saves logs to disk and will retry if it can't reach its destination. Probably the one benefit of fluentd over the rsyslog setup is that it's pretty easy to swap out different log destinations (e.g. Loggly vs. Elasticsearch), but to get the metadata we wanted, a custom version of the fluentd docker plugin was needed.

@progrium @mattaitchison @andyshinn where did this end up?

After reading this thread, it appears there may be multiple issues happening here. But the original issue would appear to be caused by the CNAME or A record changing (the IP is in AWS and would likely be a front end server or load balancer changing IPs).
Some debugging that would help confirm this would be to resolve logs-01.loggly.com when the error occurs to confirm that the IP from error and DNS record are indeed different.
The fix would need to be a retry mechanism that attempts to resolve the name again and reconnect (maybe a max retries + interval between retries option).

Status up on this issue? In our case, we use logspout to ship logs over TCP to the ELK stack. Certain container logs fail to make it to elasticsearch. When a TCP pipe for a container dies, it never recovers.

I'll work on getting #253 tested and merged

Potential fix + tests were merged in f18e503780b8f3abb3771ffaa97e5d2971199f9b


[opentelemetry-collector] Bump collector version to v0.103.0

Bumps Collector's version to v0.103.0.
https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.103.0

@ChrsMark this looks good . May I ask you to open a pr in the operator chart as well ?


Gh 344 fix tests

Just to see if tests pass on CI. Do not merge

Thanks @maciejwalkowiak! Can I cherry-pick this commit to my branch, or do you have something else in mind?

@tomazfernandes pushed to your branch after i chcked here that it works. See https://github.com/awspring/spring-cloud-aws/pull/374#issuecomment-1119976208


add QWERTZ layout support

Added additional adjacency graph to support QWERTZ keyboard layout, including German umlauts. Thanks to @androck for support!

I'd like to propose. You should update the script for generating code.
Following detail.
https://github.com/dropbox/zxcvbn/blob/master/data-scripts/build_keyboard_adjacency_graphs.py#L13-L41

I've proposed a modified Script in #172, but it got no attention until now. In my case it's working, feel free to comment, @vvatanabe.

I'm sorry for the continued delay on this feature -- I have plans to fix (with JIS, QWERTZ and others supported by default + support for adding custom maps). I'd rather wait for a larger fix vs incremental commits here, so, closing this pull request but I'll keep Issue #190 open until the issue is fixed.


vscode/flutter cannot find imports without reset

idk

VS Code Version:
OS Version:

ubuntu 21.04
vscode 1.59.1
I need to reload vscode in order for the errors to stop showing.  The variables are not found in the import until I reset the vscode.  This disturbs issues with hot reload and is annoying anyway.  I think I have only standard plugins from flutter.

Looks like the extension is here:
https://github.com/Dart-Code/Flutter


[DEVOPS-282] Fix cwd logic

Running the CI test for this locally revealed another bug. Working on that now.

@jmitchell this yields src paths to point to temporary folder, I have pushed fix-lib-reference branch on top of the existing working stack2nix commit so that my PR is unblocked :)


Cleanup build log before every build

Right now the build does not removed before the building, which is confusing because it is unclear where the previous one ends and the new one begins.

Added the new boolean setting qbs.clearOutputBeforeOperation, called as "Clear the output before starting the operation." If this setting is true, then the console output will be erased before starting any of such operations: Resolve, Clean, Build, ReBuild.
Done.


Drag and drop folders

Hi very useful program. Is it possible to add drag and drop for folders?

looks doable, give me some time

Hello, can You try latest pre-release (v1.0429.542) in Your environment ? Minor details need to be polished but, main window and scan dialog should react for dragged/dropped folder/file(s).

Yes, drag and drop works very well in main window and scan dialog. I had no problem. Really thank you very much for this program. Greetings


Grid selection error with different pages.

https://www.patricbrc.org/view/Taxonomy/570#view_tab=amr&filter=false

select the first row in page 1

move to page 2, and select any row

Due to the javascript error, detail info shows the previous selection and all the action buttons work on old info.

This is what Rebecca reported regarding wrong antibiotic page linking.
This problem occurs in all the grid not specific to this AMR phenotype.
Dustin, would you take a look at?

I believe I have fixed this, please test it out on alpha.

confirmed. on alpha. will deploy in a week or at most by end of this month (April release)

v3.3.6 has deployed on prod


Fix account logging

Usage related changes

Add logging of seed and initial balance of predeployed accounts
GET /predeployed_accounts was returning 0 for initial balance
Converted initial balance to be a hex string in output

Development related changes

Rename PredeployedAccount to SerializableAccount

was misleading because we have both Account and PredeployedAccount and the only purpose of what was PredeployedAccount is being serialized (hence the renaming)

CircleCI claims to be failing, but that's because https://github.com/0xSpaceShard/starknet-devnet-rs/pull/31 hasn't been merged.
Format the code (might clash with #31)
There are a couple of TODO comments in the code

we can consider implementing From/Into for Felt/String - might require a bigint library

Renamed fn predeployed_accounts to fn get_predeployed_accounts

should be a verb

Separate account logging into a separate function
Add +nightly to cargo fmt invocation

Checklist:

[x] Applied formatting - ./scripts/format.sh
[x] No linter errors - ./scripts/clippy_check.sh
[x] Performed code self-review
[x] Rebased to the last commit of the target branch (or merged it into my branch)
[x] Documented the changes
[ ] Linked the issues which this PR resolves
[ ] Updated the tests
[x] All tests are passing - cargo test

Why initial_account_balance type is changed to felt


Language selection

Hi,
I noticed that even if there are NLS files for 34 languages, the language is not selected automatically based on the browser's locale.

The apps are available in 30+ locales and in my testing the browser locale is used to determine the app language. Note that text like the app title is dependent on the underlying configuration or web map and is not localized. But search strings, tooltips, widgets etc are.

Ok I tested a fresh copy of the app without making any changes and language selection works. I must had messed someting up when configuring and customizing the app. Sorry about that.


Clean up src/ and tasks.py

I won't get to this until after the ICLR deadline, but I'd like to clean up the src/ directory so dependencies are a bit cleaner. Also, tasks.py is massive and we should really split it up.
Proposed structure:
src/
    allennlp_mods/
    cove/ [submodule]
    __init__.py
    evaluate.py
    models.py
    modules/
        cnns/
        __init__.py
        <several .py files with old contents of modules.py>
        edge_probing.py
        seq2seq_decoder.py
        generate_s2s.py
    preprocess.py
    tasks/
        __init__.py
        tasks.py    # core definitions and registry
        edge_probing.py
        <other .py files containing various groups of tasks>
    trainer.py
    utils/    # or "misc/" or "lib/"
        __init__.py
        config.py
        emails.py
        gcp.py
        hocon_writer.py
        retokenize.py
        serialize.py
        utils.py

SGTM!
On Tue, Sep 18, 2018 at 7:15 PM Ian Tenney<EMAIL_ADDRESS>wrote:

I won't get to this until after the ICLR deadline, but I'd like to clean
up the src/ directory so dependencies are a bit cleaner. Also, tasks.py
is massive and we should really split it up.
Proposed structure:
src/
allennlp_mods/
cove/ [submodule]
init.py
evaluate.py
models.py
modules/
cnns/
init.py
<several .py files with old contents of modules.py>
edge_probing.py
seq2seq_decoder.py
generate_s2s.py
preprocess.py
tasks/
init.py
tasks.py    # core definitions and registry
edge_probing.py
<other .py files containing various groups of tasks>
trainer.py
utils/    # or "misc/" or "lib/"
init.py
config.py
emails.py
gcp.py
hocon_writer.py
retokenize.py
serialize.py
utils.py
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jsalt18-sentence-repl/jiant/issues/420, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ABOZWQT_jpWWDpIMtwkuyw97iiZ8AW1Vks5ucX6hgaJpZM4WvDhk
.

I'm all for it
On Tue, Sep 18, 2018 at 7:41 PM Sam Bowman<EMAIL_ADDRESS>wrote:

SGTM!
On Tue, Sep 18, 2018 at 7:15 PM Ian Tenney<EMAIL_ADDRESS>wrote:

I won't get to this until after the ICLR deadline, but I'd like to clean
up the src/ directory so dependencies are a bit cleaner. Also, tasks.py
is massive and we should really split it up.
Proposed structure:
src/
allennlp_mods/
cove/ [submodule]
init.py
evaluate.py
models.py
modules/
cnns/
init.py
<several .py files with old contents of modules.py>
edge_probing.py
seq2seq_decoder.py
generate_s2s.py
preprocess.py
tasks/
init.py
tasks.py # core definitions and registry
edge_probing.py
<other .py files containing various groups of tasks>
trainer.py
utils/ # or "misc/" or "lib/"
init.py
config.py
emails.py
gcp.py
hocon_writer.py
retokenize.py
serialize.py
utils.py
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jsalt18-sentence-repl/jiant/issues/420, or mute the
thread
<
https://github.com/notifications/unsubscribe-auth/ABOZWQT_jpWWDpIMtwkuyw97iiZ8AW1Vks5ucX6hgaJpZM4WvDhk
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jsalt18-sentence-repl/jiant/issues/420#issuecomment-422595202,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFQ7G96xS3CfIWIoh3vpYId3huoRGkMiks5ucYStgaJpZM4WvDhk
.

Most of this is done now, but we might want to still split up modules.py. I shied away from doing this because of potential bugs this close to the NAACL deadline, but if someone (@W4ngatang maybe?) who knows this code better than I wants to take a stab at it, we could merge later in December.


Add constructor doc bloc for UploadedFile

I was going through the class and thought it might help others to have the doc bloc added.

Thanks @samsonasik. I'll get those changes made.

I incorporated feedback during merge.


Uses "raycast" which is only in minetest 0.5 or later

Investigate whether 0.4.16's "line of sight" function can be used as a fallback to allow backward compatibility. There might be issues with treating the player as an obstruction (will require the target point to be moved outside the player) and with not treating liquids as obstructions.

I've added code to use line_of_sight when Raycast isn't available, have yet to check if it's treating liquid as obstruction.

Confirmed, line_of_sight and raycast return the same results when I stand next to a standardized two-level-deep pool of lava.


fix: export  → import data mapping

description
Update data mapping for health check, endpoints and fail over data mapping for export import use case

:tada: This PR is included in version 0.1.0-alpha.11 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Docs and blog not visible to search engine (Google)

We have put a ton of effort into our docs and blog but they can't be searched using Google which is a pity.

Blog should be visible now that we switched to static pages. The docs require much more effort because of the interactive API explorer.

This is being investigated in ocular by @jckr.


⚠ Bofrost.fr has degraded performance

In 0af2587, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1335 ms

Resolved: Bofrost.fr performance has improved in c528576 after 3 hours, 2 minutes.


Moving ICU dependent classes into a separate project

Would this help to deal with ICU issues that people are encountering in using early versions of 4.8 port? Seems like a quick way to get past 64-bit issues while a long-term solution for ICU is found.
This PR moves Analysis.Common/Th/* and Util/SegmentingTokenizerBase into a separate project allowing to remove ICU4NET dependency from Lucene.Net.Analysis.Common.

👍
WDYT @NightOwl888 ?

No offense, but since @conniey has already provided a working solution to the ICU bitness issue, this seems like a step backward instead of a step forward. At the very least, this will create a lot of merge conflicts for #191 and an unneeded NuGet package to be created and then abandoned shortly afterward. Not to mention, naming the package Lucene.Net.Analysis.Common.ICU is a poor naming choice, since there is another package Lucene.Net.Analysis.ICU, which will cause lots of confusion if/when it is ported. We are getting very close to the point where #191 can be merged - we are probably just a few days away from that point, after which we will be able to get the pre-release on NuGet shortly afterward.
That said, it might pay off if some interested parties take a look at her demo and create prototypes to verify icu-dotnet works for all environments. That is what will happen anyway when we get the pre-release on NuGet, but we might be able to head off any remaining issues earlier with earlier feedback.
In the meantime, if anyone needs an immediate solution to this, they should choose one of the following options:

Manually build and pack #191 (recommended)
Manually build this branch (will require some extra work to pack if you need NuGet packages)
Use the MyGet packages and delete the ICU DLLs (assuming you don't need Thai support or to utilize the SegmentingTokenizerBase). This is not guaranteed to work, but has worked in at least one case.

@NightOwl888 I wasn't sure how close #191 was, that's why offered this as an option so that Analysis package could be released without ICU dependencies. I will go ahead and close this if it's not necessary and #191 is about to be merged in. Thanks.


How to get current page name from a separate class

I'm trying to get the current page name from a separate class, but i'm not sure how to handle this. I used the NavigationStack in normal Xamarin, but it doesn't work with this.

I'm not exactly sure what you mean.
But you could use CurrentPage from your ViewModel to access the... current page!


Java: Add Lrem command to BaseClient and BaseTransaction. (List commands)

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

Please, resolve conflicts


Timestamp added to container object.

Fixes #912
Signed-off-by: Kunal Kushwaha<EMAIL_ADDRESS>

Codecov Report

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

@@           Coverage Diff           @@
##           master     #933   +/-   ##
=======================================
  Coverage   59.55%   59.55%
=======================================
  Files           5        5
  Lines         759      759
=======================================
  Hits          452      452
  Misses        199      199
  Partials      108      108

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 7fc91b0...dcf8cee. Read the comment docs.

@kunalkushwaha are you missing a commit?  I don't see these fields being set anywhere?

Sorry looks like it got deleted during merge. Shall fix it by tomorrow. Out
of office today.
Regards,
Kunal Kushwaha

Sent from mobile device
On Jun 2, 2017 8:25 AM, "Michael Crosby"<EMAIL_ADDRESS>wrote:

@kunalkushwaha https://github.com/kunalkushwaha are you missing a
commit? I don't see these fields being set anywhere?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/containerd/containerd/pull/933#issuecomment-305647716,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACoXIdjRiWTgpOHAOTxOqk9dkKFvuk0sks5r_0hqgaJpZM4No0Vn
.

@kunalkushwaha no problem.  Thanks!

@crosbymichael  Updated the PR.

LGTM

LGTM


Get rid of pachctl port-forward, and talk directly to kubernetes

We get a kubernetes host using "kubectl get nodes" and choose host 0.
Notes:

I don't bother caching the IP of the k8s node I'm connecting to, because this lookup seemed to be pretty fast, and not caching it seemed much simpler
I'm not sure if these nodes are ordered deterministically. It might be that pachd always connects to the same kubernetes node, and if a bunch of people in a company are using it to put a file at the same time, the node becomes overwhelmed. This would be easy to fix (list all k8s nodes and pick a random one, instead of picking node 0), but this also didn't really seem necessary.

So with this patch there shouldn't be any need to do port forwarding at all since pachctl will be smart and find k8s nodes to connect to. Is that accurate? The only reason I could think of that maybe user would still want to use port forwarding is security concerns of opening up ports in their cluster. In which case you can still use ssh port-forwarding to a k8s node and then use ADDRESS to point at local host. And once we have a good security story even that will go away.
Code all LGTM here. I guess we're still waiting on #962 to merge.

So with this patch there shouldn't be any need to do port forwarding at all since pachctl will be smart and find k8s nodes to connect to. Is that accurate?

Yup, that's right

Just to update: This PR got a little bit stuck because #962 added a docker registry, so this PR needs to make sure that pachctl can talk to the docker registry even with port-forwarding turned off. Unfortunately, I haven't yet figured out how to talk to the docker registry remotely without TLS, so either we'll need to include a TLS certificate in our docker registry deployment, or I'll need to figure out how to override docker's default settings

I'm a little confused why this is a thing, kubernetes has the concept of a load-balancer for this reason. Why are we re-inventing the wheel here?

Even with a load-balancer users normally need to do some sort of proxying to get their laptops talking to kubernetes. Depending on how they deploy pachyderm this process is different so it's pretty difficult for us to have bullet proof documentation that will always get users up and running with a pachyderm cluster. This command was just an attempt to have a more bulletproof way of proxying the port since many users were getting stuck on that step.
Also this PR is actually removing that functionality because of how unperformant it was.

I agree with removing the port-forward from pachctl, seemed a bit redundant since kubectl offered that anyway. So this patch just addresses automagically locating kubernetes provided that it is reachable from your host and only if ADDRESS is not set. In which case, that makes sense.
Re the TLS comment, the only way to connect to an unsecure docker repo is to set a flag on the client side daemon and restart the service. This is not really ideal. You can create self signed certificates but that gets messy. Whats the reason for the registry deployment as opposed to just using offering like those from the cloud providers or docker hub.

We've actually removed the registry for all the reasons you just described. The idea was appealing because we were hoping we could make things more bulletproof to new users who aren't very familiar with Docker and Kubernetes but unfortunately things get too messy with certificates and stuff. So we now have a "bring your own registry" policy which I think is the best we can do.
Also @msteffen that means this pr should be mergable now.

I closed this PR on accident, but a) it's super old, and b) I'm not sure that it actually worked (it got the master node from kubectl and treated that as a regular cluster node by just sending traffic to the pachyderm NodePort port on that machine, and I'm not sure if that's legit)


[1.12.2] stellar API causes blindness effect to be near-total

forge <IP_ADDRESS>4, stellar API <IP_ADDRESS>.1
these two imgur shots show the same blindness effect, one taken with stellar API installed, the other taken during the same potion duration but with only forge installed.
the shot where no grass is visible is the shot with stellar API installed. no other mods were present in the test instance i produced these screenshots in.
if this is intentional, please will you provide a config option to enable vanilla behaviour?

Fixed on the last version.


Tutorial notebook renders incorrectly in dark mode

Reported as not fixed. #175 should resolve the issue.


[Azure Search] Add Translate and Conditional skills, and recursive skill inputs (for shaper)

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-go

@arv100kri

Automation for azure-sdk-for-python

The changes themselves look good, but there are a couple of merge conflicts which we don't like to part of the git history.
Could you possibly eliminate those merge commits and force push to your branch with the other more reasonable looking commits?

Can one of the admins verify this patch?

The changes themselves look good, but there are a couple of merge conflicts which we don't like to part of the git history.
Could you possibly eliminate those merge commits and force push to your branch with the other more reasonable looking commits?

I just did a new PR, was easier then trying to figure out the git weirdness since I had done a merge early on in my changes as well.  Here's the new one: https://github.com/Azure/azure-rest-api-specs/pull/6865


ERROR: Unable to download webpage: HTTP Error 403: Forbidden (caused by HTTPError()); please report this issue on https

PS D:.\youtube-dl.exe --update
youtube-dl is up-to-date (2020.03.24)
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--username', 'PRIVATE', '--password', 'PRIVATE', '-o', '%(chapter_number)s - %(chapter)s/%(playlist_index)s - %(title)s.%(ext)s',
'--playlist-start', '1', '--verbose', '--min-sleep-interval', '90', '--max-sleep-interval', '130',
'https://app.pluralsight.com/library/courses/commvault-virtualization-concepts-configuration']
[debug] Encodings: locale cp1252, fs mbcs, out cp1252, pref cp1252
[debug] youtube-dl version 2020.03.24
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.18362
[debug] exe versions: none
[debug] Proxy map: {}
[pluralsight:course] commvault-virtualization-concepts-configuration: Downloading JSON metadata
[download] Downloading playlist: Commvault® Virtualization
[pluralsight:course] playlist Commvault® Virtualization: Collected 7 video ids (downloading 7 of them)
[download] Downloading video 1 of 7
[pluralsight] Downloading login page
ERROR: Unable to download webpage: HTTP Error 403: Forbidden (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using
the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpjwbwqymm\build\youtube_dl\extractor\common.py", line 627, in _request_webpage
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpjwbwqymm\build\youtube_dl\YoutubeDL.py", line 2238, in urlopen
File "C:\Python\Python34\lib\urllib\request.py", line 470, in open
File "C:\Python\Python34\lib\urllib\request.py", line 580, in http_response
File "C:\Python\Python34\lib\urllib\request.py", line 508, in error
File "C:\Python\Python34\lib\urllib\request.py", line 442, in _call_chain
File "C:\Python\Python34\lib\urllib\request.py", line 588, in http_error_default
Sleep for 120 - END

i got the same bug


Dependency Conflict on React 18

it works with
npm install react-tailwind-table --force

Hi, is this dependency problem resolved? @mklef121


Recovery not belong to mac

I need to perform csrutil actions, but it shows

How should I do？

Set your default boot volume to Monterey and try again. This is expected behavior on these machines, nothing to do with Asahi (the same thing would happen with multiple macOS installs, you need to set the one you want to change boot stuff for as the default).

Thanks for your quick and valuable response! I'm outside now and will try it later today!
From @RoderickQiu

From: Hector Martin @.>
Sent: Sunday, July 10, 2022 8:29:04 PM
To: AsahiLinux/m1n1 @.>
Cc: r-q @.>; Author @.>
Subject: Re: [AsahiLinux/m1n1] Recovery not belong to mac (Issue #230)
Set your default boot volume to Monterey and try again. This is expected behavior on these machines, nothing to do with Asahi (the same thing would happen with multiple macOS installs, you need to set the one you want to change boot stuff for as the default).
—
Reply to this email directly, view it on GitHubhttps://github.com/AsahiLinux/m1n1/issues/230#issuecomment-1179719547, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKCUYVAVLDGW3QXVLPD2GATVTK6ZBANCNFSM53E5RODQ.
You are receiving this because you authored the thread.Message ID: @.***>

It does work, thanks.


Command groups idea

So I was asked to move this here:

•Can you add something like "command groups" so when I have bunch of objects with similar commands like "testcube.jump" they won't show in help menu?

What about prefixing the help string with a group name? Something like:
[RegisterCommand("cube.move", Help = "player/Move test cube")]
static void CommandMove(CommandArg[] args) { }

[RegisterCommand("cube.rotate", Help = "player/Rotate test cube")]
static void CommandRotate(CommandArg[] args) { }

Then calling the help command would only show "cube", and calling help cube would list all commands in the group.
That way this is only a documentation thing, and doesn't affect how commands are processed internally. Allowing it to be an optional feature.
Either way I think you make a valid point, my projects use enough commands that the help command isn't super useful, and I find my self using help command_name most of the time. Having groups would likely make the command documentation more organized and easier to navigate.

That would work, especially with new autocomplete

I've added this functionality to the help command. Example using ed as a group:

How about adding option not to create a help menu for command?
For example I have 3 objects and every object creates command with name "{name}.jump" and I don't want to show any of this groups in help menu?

So just a way to not show the command at all?
Also, why create a jump command for each object instead of having a single jump command that receives an identifier like jump {name}?

Because I don't need to create one object to hold all objects with jump command, instead every object can add it's own command, and autocomplete supports it.
When I think of it I can create static class to store objects which is good but there is still no autocomplete support.

Ah that makes sense, the groups would allow you to group all {name} objects together or all jump commands together. Why would you want to hide everything?
Something like:
[RegisterCommand("cube1.jump", Help = "jump/Cube1 jump")]
static void CommandJump1(CommandArg[] args) { }

[RegisterCommand("cube2.jump", Help = "jump/Cube2 jump")]
static void CommandJump2(CommandArg[] args) { }

would only show jump (not the individual cube.jump commands) in the help list, to see both commands you would use help jump.
By the way, you can add things to the autocomplete with Terminal.Autocomplete.Register("name"). But I get what you're saying, you want separate commands.

Making command structure like {object}.{group}.{command} is just more logical to me.
"equipment.gear.add helmet" is more logical to me than "add equipment gear helmet" or "equipment_add gear helmet"

But after some thought jump {name} might be more logical

I've added this functionality to the help command. Example using ed as a group:

Excuse me, is this already available?


Upgrade dependencies, remove resolutions

Upgrade gulp-purescript
Upgrade purescript-halogen, purescript-css

:fire: Please do not merge until Halogen 0.5.0 has been released, and this PR updated accordingly. :fire:

This is now safe to merge. @cryogenian Would you mind having a look?

Looks good to me!


Upload Project through website

Users can upload details of the project they want added to the site and I will get a notification. After reviewing, it will appear on the site

currently working on it in the dev branch


Add unit test coverage

AC:

Meaningful unit test coverage of the code
e2e test covering the happy path(s)

Stretch:

Add codecov tooling

Note: determine we can just add unit testing for the internal packages for now and hold off on testing the controller packages.

PR for internal/updater unit tests

PR for internal/helm-operator-plugins unit tests https://github.com/operator-framework/rukpak/pull/115

There was some consensus around breaking out the codecov work into a standalone ticket: https://github.com/operator-framework/rukpak/issues/196

Moving this out of the 0.4 milestone as our e2e suite is still pretty fleshed out at this point.

Since we have pretty good coverage now and this issue has sat for awhile I'm going to go ahead and close this. In the future we can break whatever remaining unit tests that we want into separate issues or reopen this if we find it pertinent.


Not working if scrollbar is present

So, I'm trying this plugin and from what I can see the width of the breakpoint settings are not correct if there is a scrollbar present.
If I have the following settings on a page with a scrollbar:
breakpoints: [{
    "name": "tablet",
        "width": 768 //will actually detect breakpoint at 785
    }, {
        "name": "desktop",
        "width": 1024 //will actually detect breakpoint at 1041
    }]

Thanks, I've just cut a release 1.8.1 to fix this:
Without scrollbar

With scrollbar


Added additional required dependencies

When loading up a new EC2 instance from AWS, it lacks packages such as cmake & build-essential, which are necessary for compiling the project.

Thank you @dragonsnapx


API endpoint /open_api/v1.3/event/track/

Hi is there any plans on adding support for the API endpoint /open_api/v1.3/event/track/, specifically for python? I can see there's POST /open_api/v1.3/pixel/batch/ but going off of your developer docs this was sunset 2024 H2

@samdaviestvg Yes, we do have plans to support more APIs including /open_api/v1.3/event/track/.  We currently estimate to support it Q1 in 2025!


aut.conf error on new version

Watchtower updated the container with the latest version you created few hours ago and now I can't start the container anymore. I'm getting the following error:
chown: /auth.conf: Read-only file system,
Changing /auth.conf ownership to nonrootuser with read only access...Error! (status 1),

Full logs here: Pastebin
I can't roll back to a previous version as I think you build all the version with latest tag.
Thank you for looking into this. I tried to recreate everything from clean, not working.

It's because you have auth.conf as ready only (:ro flag). I will fix it now on my side as well.

Thanks for the quick fix, re-deployed the container and it is working fine now.
Btw, do you use Watchtower to update containers? If yes, what is your Watchtower docker-compose?

No I don't use WatchTower because sometimes the container breaks (like I just did haha!). I prefer to update manually once i stop a container. I might set it up sometime for my own containers and official ones like alpine etc.


Ensure that CleanBC logo is loaded with the page

Describe the task
When loading the page, there is a flash of content without the CleanBC logo. It should come with the page, but does not for some reason.
~This is probably what is causing the logo to not appear in the Happo screenshots~ Apparently that didn't fix the happo screenshot rendering, see https://github.com/happo/happo.io/issues/223
Acceptance Criteria

[x] CleanBC logo is rendered without flashing
[ ] ~CleanBC logo is visible in the Happo screenshots~

Thank you @matthieu-foucault ! The CleanBC logo is displayed as expected and I see no flashing.


disable webrtc (gn)  kills build

chromum version 62.0.3202.45
patches, only inox
gn flags (all except disable safe browsing)
buildlog
https://p.teknik.io/S841g

WORKED with enable webrtc


propType warnings from valid examples (in 3.0)

In this example:
initialState = {star: 'wars'};
<Button label={ state.star } />

I get a propType warning:
Required prop `label` was not specified in `Button`

This happens only when the code is run for the first time to determine the initial state (see Preview.js). In render, all is OK and it works fine.
For now I was able to work around this by adding this to the init code:
var React = {createElement: _.noop, createClass: _.noop};

But it doesn't seem like a very good solution. 😕

Maybe this could be fixed by changing the initCode to this:
const initCode = `
    // Workaround for https://github.com/sapegin/react-styleguidist/issues/155
    var React = {}; // so React.createElement will throw
    var initialState = {};
    try {
        ${compiledCode}
    } catch (e) {
        // ignoring
    } finally {
        __initialStateCB(initialState);
    }
`;

Note that I assume that initialState will be assigned before any React elements are created. For my 116 examples it was true.

Looks like it works. I hope it doesn’t break anything ;-|


Using Cmd+D (add to selection, multiple cursors) in visual mode

I'm attempting to bind  (macOS Cmd-d) in visual mode so that it behaves as it does with a real VSCode selection. Pressing  in visual mode should:

convert the visual selection to a VSCode selection
search for the visually selected string
add the next match to the selection
leave me in insert mode with multiple selections

Is this possible? I'm having a lot of difficulty. I've tried following the instructions in the README and this is what I have:
# keybindings.json
 {
    "key": "cmd+d",
    "command": "vscode-neovim.send",
    "when": "editorFocus && neovim.mode == 'visual'",
    "args": "<D-d>"
  },

# vimrc
vnoremap <D-d>  <Cmd>call VSCodeNotifyVisual('editor.action.addSelectionToNextFindMatch', 1)<CR>

I also pasted the VSCodeNotifyVisual definition in the README into my vimrc, because it was otherwise undefined (this is not clear from the README, which suggests the function is defined by the extension).
However, this mapping doesn't have the desired effect. It does about half of what I want, but it seems to leave me with multiple selections in normal mode, and subsequent presses of Cmd+D don't work.
I would also settle for a binding that just converted my visual selection to a VSCode selection and left me in insert mode, but I can't figure out how to do that from the README.

clear from the README, which suggests the function is defined by the extension

It is, but that function is new and has not been released to the vscode marketplace.
I would try to enter insert mode, then add to next match. I don't have the time to figure it out, though I'll try to take a look at it sometime.

@asvetliakov Can we release a new version on Marketplace to cover the VSCodeNotifyVisual functionality?


Multiple

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@bf7abc3). Click here to learn what that means.
 Consider uploading reports for the commit dff6595 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #21   +/-   ##
=======================================
  Coverage        ?   85.97%
=======================================
  Files           ?      112
  Lines           ?     4056
  Branches        ?        0
=======================================
  Hits            ?     3487
  Misses          ?      569
  Partials        ?        0

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


#64: add assets for arm64

Closes #64

Codecov Report

Merging #67 (9780801) into main (5ac9740) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #67   +/-   ##
=======================================
  Coverage   94.06%   94.06%
=======================================
  Files           8        8
  Lines         236      236
=======================================
  Hits          222      222
  Misses         10       10
  Partials        4        4

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 5ac9740...9780801. Read the comment docs.


doesn't work with html5 -

Works fine with just  at the top of a file.
No longer works when using  instead.
Demo here:
http://100wires.com/dragscroll/index1.html
http://100wires.com/dragscroll/index3.html
The only difference between the two is the first line,  or

tested on chrome and it works there.  only doesn't work on firefox.

ok, reproduced, thanks for the feedback...

I cannot reproduce the issue on http://asvd.github.io/dragscroll/index.html
It also has the specified doctype, but it works. Can you provide simplier example, i.e. without the additional libs included? For now it seems like they break the dragscroll somehow only if the doctype is specified

I've taken out everything possible:
http://100wires.com/dragscroll/
http://100wires.com/dragscroll/index4.html

http://stackoverflow.com/questions/5769148/scrolltop-and-doctype
This is the reason, will prepare a fix soon

Fixed in v0.0.7


Multiline string settings are now supported in the settings editor

Hi! Just a note that you can now add the "editPresentation": "multilineText" key-value pair to any string setting that can take multiple lines (such as githubIssues.workingIssueFormatScm). In the settings editor, the setting will then display a textarea rather than a single-line inputbox. The feature is currently available in the Insiders edition of VS Code, and will be released to Stable in around two weeks.

To verify:

Install the Nightly version of the extension and disable the stable version if you have it installed
Open the settings editor and edit the setting githubIssues.workingIssueFormatScm.
Verify that it uses the multiline input box.


KAFKA-6521: Store record timestamps in KTable stores

More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Contains a lot of Java8 cleanup etc.
The actual store changes happens in KeyValueStoreMaterializer.java.
This implies, that all Processors using a store need to be updated from KeyValueStore to KeyValueWithTimestampStore. The PR include changes to leverage the timestamp to compute timestamp for the output records to get deterministic semantics.
We also need to update "KTable Getter", and forwarding tuple logic to carry forward the correct timestamp. The CachingStore needs a slight hack (this part might actually be required for the original PR for KIP-258 already). I hit a couple of other minor bugs, that need to be included there.
Test needed to be updated to expect ValueAndTimestamp<V> instead of V -- also, we need to set a timestamp when piping data throw the topology to get deterministic results.
The beauty of this PR is, that is after KIP-258 is merged, we can just redirect to AK/trunk to address KAFKA-6521 (it's touches almost only DSL code and should not be hard to rebase/clean up :) )


Update LAB[PL-200]_M02L01_Create_an_app.md

Module: 00
Lab/Demo: 00
Fixes # .
Changes proposed in this pull request:

Submitted by ParamRamki on behalf of MOC Labs Review

Need time to work through these conflicts. I cannot merge these right now. If you have a moment to resolve them, that would be helpful and appreciated. Thank you!

The change in this pull request is essentially the same as merged pull request #68. Closing this pull request.


unexpected that there is no Module entry for "/usr/src/app/node_modules/ioredis/built/index.js" in require.cache

unexpected that there is no Module entry for "/usr/src/app/node_modules/ioredis/built/index.js" in require.cache
when building with webpack

Can you create a reproducible example for it? I think there should be some issues in the webpack configuration. Note that ioredis only works in Node.js environment so it's rare that you need to use a bundler to build the project.

it was related to elastic-apm-node


GEODE-7178: Check operation if instance of Byte for older native clients

Co-authored-by: Blake Bender<EMAIL_ADDRESS>Co-authored-by: Michael Oleske<EMAIL_ADDRESS>Older Geode Native clients send Byte object, so it would be good to still check.
Back-filled unit tests for the getOperation
Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[x] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[x] Is your initial contribution a single, squashed commit?

[x] Does gradlew build run cleanly?

[x] Have you written or updated unit tests to verify your changes?

[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

Closing this because it was learned today that old code actually wasn't just using the Byte, it was specifically checking for Byte that is of Op.Destroy and use Operation.Remove.  Will be opening a new PR for this


Landscape primary/secondary preference in iOS

Is there a specific reason to make landscape primary a rotation to the right on landscape? What was the reasoning for this?
From what we can see in most apps with landscape rotation, the most used side is rotation to left.
Thanks

fixed in #64


TypeError NumberFormatter

What steps will reproduce the problem?
Yii::$app->formatter->asCurrency(
  '10000',
  'EUR',
  [
    NumberFormatter::MAX_FRACTION_DIGITS => 0,
    NumberFormatter::GROUPING_SIZE => 3,
    NumberFormatter::GROUPING_SEPARATOR_SYMBOL => '_'
  ]
);

What is the expected result?
10_000 €
What do you get instead?
TypeError
NumberFormatter::setAttribute(): Argument #2 ($value) must be of type int|float, string given
Additional info

Q
A

Yii version
<IP_ADDRESS>.

PHP version
8.0.6

Operating system

Yes, it is a problem on php 8. Untill we fix it please don't use NumberFormatter::GROUPING_SEPARATOR_SYMBOL => '_' the way you did. Instead you can set it like:
Yii::$app->formatter->thousandSeparator = '_';

or
Yii::$app->formatter->numberFormatterSymbols[NumberFormatter::GROUPING_SEPARATOR_SYMBOL] = '_';

I've realized that this is not a bug. You should use $textOptions instead of $options for that kind of a setting.
But since that is not really clear I think we can make it more user-friendly by adding better messages for the exceptions.

If I use NumberFormatter::GROUPING_SEPARATOR_SYMBOL => '_' in $textOptions instead of $options I don't get the desired result. The currency symbol get changed instead of the thousands separator.
This works:
Yii::$app->formatter->thousandSeparator = '_';

But this doesn't:
Yii::$app->formatter->numberFormatterSymbols[NumberFormatter::GROUPING_SEPARATOR_SYMBOL] = '_';

Hmm, yes, when we set thousandSeparator we set internally
$formatter->setSymbol(NumberFormatter::GROUPING_SEPARATOR_SYMBOL, $this->thousandSeparator);
$formatter->setSymbol(NumberFormatter::MONETARY_GROUPING_SEPARATOR_SYMBOL, $this->thousandSeparator);

so both would have to be set, better to just use thousandSeparator, that's what it's for.

Also in order for Yii::$app->formatter->thousandSeparator = '_'; to work, i also have to set NumberFormatter::GROUPING_SEPARATOR_SYMBOL => 1
I don't really know what this 1 is doing but it does the job 😃
Otherwise i don't get any separation symbol at all.

You mean NumberFormatter::GROUPING_USED? Hmm, should we set it as well?

No, i mean NumberFormatter::GROUPING_SEPARATOR_SYMBOL
The reason I've tried to put an integer there in the first place is because of the error. I've tried putting 0 - no separator is displayed. Then tested with 1 and a space appeared as thousands separator (without actually specifying any value for Yii::$app->formatter->thousandSeparator)

What is your locale value?

What is your locale value?

'bg'

I've tested it without Yii ( https://3v4l.org/a0nDu ) and looks like in case of currencies attributes are just ignored but most probably it all depends on the ICU version you have installed. I'm afraid we cannot do much about that apart from taking care of the proper error handling which is in my PR.


Api endpoint to add new cohort (post)

as a manager I want to be able to add new cohort name and start date of cohort so I can see new cohort on the board


L. casei & B. subtilis group not present in MetaPhlAn 3

Whole species groups like Lactobacillus casei group not present in MetaPhlAn 3
I have tried to use MetaPhlAn with samples that have Bacillus subtilis and Lactobacillus casei but in the profile tables they are not present.
I have found this paper where they say that "multiple species included by the NCBI taxonomy into a ‘species-group’ are identified with unique markers for the whole species groups such as Lactobacillus casei group, Bacillus subtilis group..."
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8096432/
But when I run metaphlan with the database mpa_v30_CHOCOPhlAn_201901 this species groups arent shown and my relative abundances are computed with out this species...
How can I get a profile table with the relative abundances of these species groups?

We are aware of this problem, something went wrong while re-packing the
database and we are working on it. Unfortunately, these were the only two
species groups that were lost.
Francesco Beghini, PhD
Lab. of Computational Metagenomics
Department of Cellular, Computational and Integrative Biology - CIBIO
University of Trento
Via Sommarive 9, 38123 Trento, Italy
On Thu, Oct 28, 2021 at 10:12 AM Adrian-Howard @.***>
wrote:

Whole species groups like Lactobacillus casei group not present in
MetaPhlAn 3
I have tried to use MetaPhlAn with samples that have Bacillus subtilis and
Lactobacillus casei but in the profile tables they are not present.
I have found this paper where they say that "multiple species included by
the NCBI taxonomy into a ‘species-group’ are identified with unique markers
for the whole species groups such as Lactobacillus casei group, Bacillus
subtilis group..."
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8096432/
But when I run metaphlan with the database mpa_v30_CHOCOPhlAn_201901 this
species groups arent shown and my relative abundances are computed with out
this species...
How can I get a profile table with the relative abundances of these
species groups?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/biobakery/MetaPhlAn/issues/161, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGKRKNMSYVN2UQSEAAWASLUJEHYXANCNFSM5G4HK6XQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


isUtc() does not seem to be working

Please find the steps to reproduce below
var utcDate = '2016-12-28T06:40:28Z';
moment(utcDate).isUtc();   // returns false

Even it is not recognizing moment generated UTC dates as UTC, see
var utcDate = moment.utc().format();
moment(utcDate).isUtc();    // returns false

What am I missing here?

This function isn't looking for an offset of z. It is looking to see if the moment object itself is in UTC mode, and thus computations are being performed in UTC. See:
http://momentjs.com/guides/#/parsing/local-utc-zone/
https://maggiepint.com/2016/05/14/moment-js-shows-the-wrong-date/


non-static forward method will be removed in 1.3

Hi, the version of my pytorch is 1.3. and the python version is 3.6.  when I run the code
y = net(x)
which is for the detection.
the warning is arise:
UserWarning: Legacy autograd function with non-static forward method is deprecated and will be removed in 1.3. Please use new-style autograd function with static forward method. (Example: https://pytorch.org/docs/stable/autograd.html#torch.autograd.Function)
I am very confused about how to solve that problem, so is there anyone have a clue?

I have same problem like you. my torch version is 1.4.0. But it seems that the problem has no effect to training. have you solve it?

Degrade the pytorch version to 1.2.0 or below will solve this problem.

Hi, the version of my pytorch is 1.3. and the python version is 3.6. when I run the code
y = net(x)
which is for the detection.
the warning is arise:
UserWarning: Legacy autograd function with non-static forward method is deprecated and will be removed in 1.3. Please use new-style autograd function with static forward method. (Example: https://pytorch.org/docs/stable/autograd.html#torch.autograd.Function)
I am very confused about how to solve that problem, so is there anyone have a clue?
Did you get the solution ?

Hi, version of colab is PyTorch1.5.0, I modified detection.py and ssd.py.
Since detection.py have torch.autograd.Function, I delete def init() and add @staticmethod.
I share my code and you can find in '# PyTorch1.5.0 support new-style autograd function' in source.
https://github.com/miyamotok0105/pytorch_handbook/blob/master/chapter7/layers/functions/detection.py

@ayukat1016  hello.I have modified the detection file.I am confused about where to add output = self.detection. apply() in the ssd.py file.

@fywsjz  Hello. You can find in line 63, 123.
https://github.com/miyamotok0105/pytorch_handbook/blob/master/chapter7/ssd.py

Thank you very much. I'll try it right away
| |
封亚炜
|
|
<EMAIL_ADDRESS>|
签名由网易邮箱大师定制
On 5/22/2020 10:53，Takuya<EMAIL_ADDRESS>wrote：
@fywsjz Hello. You can find in line 63, 123.
https://github.com/miyamotok0105/pytorch_handbook/blob/master/chapter7/ssd.py
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@ayukat1016 Thank you very much. It worked

Hi, version of colab is PyTorch1.5.0, I modified detection.py and ssd.py.
so that it works without warning and error.
Since detection.py have torch.autograd.Function, I delete def init() and add @staticmethod.
I also add output = self.detect.apply() in ssd.py.
I share my code and you can find in '# PyTorch1.5.0 support new-style autograd function' in source.
https://github.com/miyamotok0105/pytorch_handbook/blob/master/chapter7/layers/functions/detection.py

うまく動作する様になりました、ありがとうございます！

Hi, version of colab is PyTorch1.5.0, I modified detection.py and ssd.py.
so that it works without warning and error.
Since detection.py have torch.autograd.Function, I delete def init() and add @staticmethod.
I also add output = self.detect.apply() in ssd.py.
I share my code and you can find in '# PyTorch1.5.0 support new-style autograd function' in source.
https://github.com/miyamotok0105/pytorch_handbook/blob/master/chapter7/layers/functions/detection.py

Hi, it can work well like below:
Finished loading model!
im_detect: 1/4952 1.888s
im_detect: 2/4952 0.145s
...

Evaluating detections
Writing aeroplane VOC results file
Writing bicycle VOC results file
...

VOC07 metric? Yes

But after that, it will error:
Exception has occurred: KeyError at 317, eval.py
R = class_recs[image_ids[d]]
And here:
class_recs
{}

image_ids
['000002', '000002', '000002', '000002', '000002', '000002', '000003']

d
0

Do you know what here happening and can you help me?

I have not encountered the problem you described, you can try to find the answer in the issues at github, sorry for not being able to help you
| |
封亚炜
|
|
<EMAIL_ADDRESS>|
签名由网易邮箱大师定制
On 5/28/2020 16:43，Shirui<EMAIL_ADDRESS>wrote：
Hi, version of colab is PyTorch1.5.0, I modified detection.py and ssd.py.
so that it works without warning and error.
Since detection.py have torch.autograd.Function, I delete def init() and add @staticmethod.
I also add output = self.detect.apply() in ssd.py.
I share my code and you can find in '# PyTorch1.5.0 support new-style autograd function' in source.
https://github.com/miyamotok0105/pytorch_handbook/blob/master/chapter7/layers/functions/detection.py
Hi, it can work well like below:
Finished loading model!
im_detect: 1/4952 1.888s
im_detect: 2/4952 0.145s
...
Evaluating detections
Writing aeroplane VOC results file
Writing bicycle VOC results file
...
VOC07 metric? Yes
But after that, it will error:
Exception has occurred: KeyError at 317, eval.py
R = class_recs[image_ids[d]]
And here:
class_recs
{}
image_ids
['000002', '000002', '000002', '000002', '000002', '000002', '000003']
d
0
Do you know what here happening and can you help me?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

I have not encountered the problem you described, you can try to find the answer in the issues at github, sorry for not being able to help you | | 封亚炜 | |<EMAIL_ADDRESS>| 签名由网易邮箱大师定制 On 5/28/2020 16:43，Shirui<EMAIL_ADDRESS>wrote： Hi, version of colab is PyTorch1.5.0, I modified detection.py and ssd.py. so that it works without warning and error. Since detection.py have torch.autograd.Function, I delete def init() and add @staticmethod. I also add output = self.detect.apply() in ssd.py. I share my code and you can find in '# PyTorch1.5.0 support new-style autograd function' in source. https://github.com/miyamotok0105/pytorch_handbook/blob/master/chapter7/layers/functions/detection.py Hi, it can work well like below: Finished loading model! im_detect: 1/4952 1.888s im_detect: 2/4952 0.145s ... Evaluating detections Writing aeroplane VOC results file Writing bicycle VOC results file ... VOC07 metric? Yes But after that, it will error: Exception has occurred: KeyError at 317, eval.py R = class_recs[image_ids[d]] And here: class_recs {} image_ids ['000002', '000002', '000002', '000002', '000002', '000002', '000003'] d 0 Do you know what here happening and can you help me? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

Thanks anyway.

Hi, version of colab is PyTorch1.5.0, I modified detection.py and ssd.py.
so that it works without warning and error.
Since detection.py have torch.autograd.Function, I delete def init() and add @staticmethod.
I also add output = self.detect.apply() in ssd.py.
I share my code and you can find in '# PyTorch1.5.0 support new-style autograd function' in source.
https://github.com/miyamotok0105/pytorch_handbook/blob/master/chapter7/layers/functions/detection.py

Hi, I modified
detection.py
and
ssd.py
as yours.
Then I tried running eval.py, and actually got this problem:
RuntimeError: CUDA out of memory. Tried to allocate 4.08 GiB (GPU 0; 8.00 GiB total capacity; 200.34 MiB already allocated; 5.04 GiB free; 958.00 MiB reserved in total by PyTorch)
The GPU on the machine is 2070 super. In my opinion, its performance should be sufficient.
Then also I tried running eval.py by --cuda False,
and it can run:
...
im_detect: 997/4952 0.320s
im_detect: 998/4952 0.343s
...
Why can't it run on GPU? Do you have any ideas?

@fywsjz Hello. You can find in line 63, 123.
https://github.com/miyamotok0105/pytorch_handbook/blob/master/chapter7/ssd.py

Hi, version of colab is PyTorch1.5.0, I modified detection.py and ssd.py.
so that it works without warning and error.
Since detection.py have torch.autograd.Function, I delete def init() and add @staticmethod.
I also add output = self.detect.apply() in ssd.py.
I share my code and you can find in '# PyTorch1.5.0 support new-style autograd function' in source.
https://github.com/miyamotok0105/pytorch_handbook/blob/master/chapter7/layers/functions/detection.py

うまく動作する様になりました、ありがとうございます！

thank you so much for solving this error!!

Hi, version of colab is PyTorch1.5.0, I modified detection.py and ssd.py.
so that it works without warning and error.
Since detection.py have torch.autograd.Function, I delete def init() and add @staticmethod.
I also add output = self.detect.apply() in ssd.py.
I share my code and you can find in '# PyTorch1.5.0 support new-style autograd function' in source.
https://github.com/miyamotok0105/pytorch_handbook/blob/master/chapter7/layers/functions/detection.py

Thank you so much!

I got a easy way out:
just mordify the base class of Detect to 'object', and then modify the code in ssd.py:
        if self.phase == "test":             with torch.no_grad():                 output = self.detect.forward(                     loc.view(loc.size(0), -1, 4),                   # loc preds                     self.softmax(conf.view(conf.size(0), -1,                                  self.num_classes)),                # conf preds                     self.priors.type(type(x.data))                  # default boxes                 )

@fywsjz Hello. You can find in line 63, 123.
https://github.com/miyamotok0105/pytorch_handbook/blob/master/chapter7/ssd.py

thanks,i solve my issue

Hi, version of colab is PyTorch1.5.0, I modified detection.py and ssd.py.
so that it works without warning and error.
Since detection.py have torch.autograd.Function, I delete def init() and add @staticmethod.
I also add output = self.detect.apply() in ssd.py.
I share my code and you can find in '# PyTorch1.5.0 support new-style autograd function' in source.
https://github.com/miyamotok0105/pytorch_handbook/blob/master/chapter7/layers/functions/detection.py

I have question,  in pytorch1.5.0, must implement backward, but the class Detect() has no backward function,why?
RuntimeError: You must implement the backward function for custom autograd.Function.

In the case of my colleague, this error was circumvented by changing
self.detect = Detect(num_classes, 0, 200, 0.01, 0.45)

to
self.detect = Detect(num_classes, 0, 200, 0.01, 0.45).forward

(i.e., just attaching .foward)
in ssd.py.
https://github.com/amdegroot/ssd.pytorch/blob/master/ssd.py#L48


Unable to get the exact form of the tag

Hello,
We are using your library to parse ASN.1 files from EMV cards. It works pretty well but we have a problem for some tags.
In EMV standards, tags like 0x8F or 0x9F0F means different things while there are both a "application-specific not-structured tag of value 15".  Then it is not possible to differentiate them using BerObject tag property.
Would it be possible to add a way to access the exact representation of the tag (as a byte slice for example) ? That would be very useful, at least for non-universal tags.

Hmm, I did not suspect some protocols would assign different meanings for different encodings of the same value.
If that's indeed used, I'm in favor of adding a way to get the value. The problem I see is that BerTag only contains the tag value, and changing it would break a lot of code.
One possible solution would be to add this to BerObjectHeader.the other one to add it to BerObject (or to both). This means adding a lifetime to the header.
Also, maybe it needs to be stored in an Option or Cow type, if in the future serialization is added.
Any thoughts or preferred methods?
I'll experiment a bit around these ideas.

Additionally, the BerObjectContent::ContextSpecific and ::Unknown variants may require to store the original tag

Thanks for the response.
Personnally, having that in BerObject only would be sufficient (even under any sort of wrapper) if the addition of the lifetime parameter can potentially break some code and prevent adding it into the header.
But I really don't know if that's possible to implement this in BerObject without changing BerObjectHeader too as from_header_and_content would still need to construct a valid BerObject and I don't know if that's possible to reference the u32 of the BerTag as a &[u8].
A solution would be to copy the original tag in the BerObject but I understand it is not a great solution as everyone would have to pay for that copy even if they don't need to access the tag as their original value.
Maybe just a variant of parse_ber/parse_der which returns a BerResult<(&[u8], BerObject)> with the first element of the tuple referencing the original tag ?

This is now partially implemented in b02b2df (another commit will follow for BerObject) by adding an optional raw_tag field.
In terms of use, this commit does not really change things (except it requires to add all raw tags to tests)

Rest of implementation in 56aabdb
There may be some places where the raw tag is not kept, but it should currently work.
I intend to tag a version for an alpha release of der-parser 4.0 with the current features soon.

der-parser 4.0.0-alpha1 has been published to crates.io, containing (amongst other changes) the ability to get the raw tag.
Since the feature was added, I'm closing this issue, but since this is an alpha version please test it and open issues if you find anything (or would like to discuss the API),

Hey guys, any reason why der_obj.tag.0.to_le_bytes() wouldn't be sufficient?

Hey guys, any reason why der_obj.tag.0.to_le_bytes() wouldn't be sufficient?

if the encoding is canonical (like in DER), it should be equivalent.
However, in BER, you can have different encodings for the same value (for ex adding leading 0). I did not imagine at first that any specs would be crazy enough to use that, but clearly I was too optimistic! So accessing the raw tag is the only way to get the original encoding.


Support Opera browser on Android devices

There are bugs that affect the Opera browser on Android devices. You can check the behavior on the demo project using Opera on an Android device:

The "Show" button won't display the prompt.
Using "Show (force)" will display the prompt.
Pressing the "Install" button doesn't show the browser install prompt.

It's the same issue https://github.com/khmyznikov/pwa-install/issues/39 . Opera don't have any install promts, so the component can't do anything natively. Need to do the same workaround with instruction as for Safari.

Added in 0.5.0
Happy new year! 🎄


KAFKA-6937: In-sync replica delayed during fetch if replica throttle …

…is exceeded

Added a unit test.

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@benstopford : Does this fix look good to you?

Should we also replace quota.isThrottled(element.getKey) with shouldLeaderThrottle(quota, ...)?
Also, it seems that replicaManager.shouldLeaderThrottle(...) will still be used to determine the FetchResponse in DelayedFetch.tryComplete() and replicaManager.readFromLocalLog() even if the request is from client. Should we only apply the replica quota is the request is from a follower?

@lindong28

The replication quota is set to UnboundedQuota if the request is from a client in KafkaApis.replicationQuota(...) so that should ensure client requests are not throttled.
The SelectingIterator does not look correct. It appears to erroneously increase the quota metric if the partition is throttled but in sync, which would throw off the leader quota for any out of sync replicas being throttled on the same broker. The same is true for the isThrottled() call in ReplicaFetchThread.processPartitionData (for the follower quota).

@junrao logic/test in your change look good but I think the above point needs addressing. I can take a look at it on tuesday if that helps.

@benstopford : I think the KafkaApis.SelectingIterator logic is by design as described in KAFKA-4313. Once a replica is in-sync, we don't want it to be throttled, but we still want to account its traffic towards the replica quota so that the total replication traffic (in sync and not in-sync) doesn't exceed the specified replica quota.

@junrao Ah, OK - is see what you did here (it confused me because I think you took over my PR or something, in that the code looks like I wrote it, but the checkin is yours).
It might be worth adding a comment to ReplicaFetchThread.processPartitionData + SelectingIterator saying something like "update throttled replicas regardless of whether they are in sync to ensure total replication traffic doesn't exceed quota" as it's pretty subtle, even if you read the jira.

@junrao @benstopford Ah I see. Thanks for the explanation!


Utilize limitAggregateUsage without cluster administrator rights

Describe the solution you'd like
limitAggregateUsage currently won't work if credentials do not have cluster admin permissions. It does makes sense that it needs cluster permissions but cluster admin seems like a lot of permissions when the SVM is specifically done for this.
Maybe some cluster-viewer role?
Describe alternatives you've considered
None with out current practices.
I guess assigning an aggregate to a certain SVM would limit impacting other aggregates, however it could still impact itself if it doesn't have capacity awareness.
Additional context

cluster-admin is required for using the limitAggregateUsage

if k8s cluster credentials get compromised it could be used with malicious intent

Would be desired to have a limited user (vsadmin) that can have access to read the aggregate limit to avoid aggregate over committing.

Priority: Cannot go production w/ Trident as I cannot use cluster-admin for it. This a security risk.

Updated the description adding additional context.

Would like to add that we need this functionality for users that run in production where we restrict any harmful queries being run agains the cluster and only scoped to the particular VSM which the user/org maintain or own


Fixing typo in README.md

I just fixed a minor mistake in the README.  😃
Modified Files

README.md

Thanks for takingi a look at the project!


OpenID Connect didn't work with auto-discovery if <issuer>/.well-known/openid-configuration is beeing redirected.

Describe the Bug
If <issuer>/.well-known/openid-configuration is beeing redirected on OpenID Connect, i get
OIDC Discovery Error: Error discovering provider settings from issuer at URL https://ghg.berlin/.well-known/openid-configuration
Steps to Reproduce

Go to login-page
Click "Login with OIDC"

Expected Behaviour
If <issuer>/.well-known/openid-configuration is beeing redirected i expect that the app is follow the redirection.
Screenshots or Additional Context
In File 'app/Access/Oidc/OidcProviderSettings.php'
at 'loadSettingsFromIssuerDiscovery'
i inserted a new request to the redirection URI if we get a 301 or 302:
        $issuerUrl = rtrim($this->issuer, '/') . '/.well-known/openid-configuration';
        $request = new Request('GET', $issuerUrl);
        $response = $httpClient->sendRequest($request);
# inserted
        if ($response->getStatusCode() == 302 || $response->getStatusCode() == 301){
                $request = new Request('GET', $response->getHeader('Location')[0]);
                $response = $httpClient->sendRequest($request);
        }
# inserted END
        $result = json_decode($response->getBody()->getContents(), true);

Browser Details
Microsoft Edge Version 115.0.1901.203 (64-Bit) on Windows 11
Exact BookStack Version
23.06.2
PHP Version
8.2.8
Hosting Environment
ghcr.io/linuxserver/bookstack:v23.06.2-ls98
OIDC-Provider: IServ

Hi @code-baron,
For the OIDC implementations I stick very closely to the provided specs.
I could not see anything about supporting redirects within the spec.
Section 4.2 of the spec states:

A successful response MUST use the 200 OK HTTP status code and return a JSON object using the application/json content type [...]

I'd be very hesitant to support outside of the spec, since there may have been security considerations behind the rigidity of the spec, and I don't want to introduce complication for identity providers that fall outside spec.
If I've missed something in the spec though, which does allow redirects for this call, feel free to point that out and I can look to update my implementation.

Since there's been no further discussion or follow-up I'll go ahead and close this off.


Copy Data does not invoke the FlushAndCloseEvent on successful copy in adlsgen2

Steps to reproduce:

Create data pipline that copies data from source adlsgen2 filesystem to destination adlsgen2 file system
Create a data pipliene that is triggered by blob create events based on the destination adls gen2 file system and run a spark job
Simulate upload of files in source

Expected behavior spark job runs
Actual: spark job never runs, on monitoring the events in the destination filesystem we see only create file events and no FlushAndClose events

@samiarahman  Thanks for the feedback and bringing this to our notice . Can you please share the link of the document which you are following please ?

It's based on your blob trigger events and copy tool feature. You dont have documentation specific for our use case. Please advise if this has to reported somewhere else.

Since the blob trigger and copy tool feature are part of the ADF . Please share the feedback @
https://feedback.azure.com/forums/270578-data-factory/suggestions/19806988--azure-data-factory.
All of the feedback you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building Azure.
At this time we will go ahead and close this issue . At any point if you feel , you can always reopen the issue .


Update CI and semantic-release for the v6 branch

Closed by https://github.com/patternfly/react-console/pull/50


Add "Custom" option to Process Thread

enum ProcessThread {
IDLE,
PHYSICS,
CUSTOM
}
I then used this CUSTOM option for finer control via a global script would call x amount of the behaviorTrees each frame. This helped immensely with performance for 50+ nav_agents with skeleton3D animations/sounds/hitboxes. You could have that value be a curve that reacts to FPS or possibly another behavior tree that manages the update rate based on distance.

Interesting idea. Just to get this right: custom = off? That's usually what the disabled property on nodes is for (to disable automatic processing)


Update plan_id label in CR

The plain_id was not getting updated in case of updateInstance call. This PR fixes that issue!

Pull Request Test Coverage Report for Build 5684

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.02%) to 88.647%

Files with Coverage Reduction
New Missed Lines
%

broker/core/utils/src/RetryOperation.js
1
94.74%

broker/data-access-layer/cf/src/TokenIssuer.js
1
98.55%

Totals

Change from base Build 5680:
-0.02%

Covered Lines:
9718

Relevant Lines:
10581

💛  - Coveralls

Validation on k8s cluster: n+n+n failed.

Validation on k8s cluster: n is succeeded.

Validation on k8s cluster: n+n+n failed.

Validation on k8s cluster: n-1 is succeeded.

Validation on k8s cluster: n+n+n failed.

Validation on k8s cluster: n-2 is succeeded.

Validation on k8s cluster: n+n+n failed.

Validation on k8s cluster: n-1 is succeeded.

Validation on k8s cluster: n-2 is succeeded.