segmentation fault when built as a static binary

Is there an existing issue for this?

[X] I have searched the existing issues.

Is this issue related to iced?

[X] My hardware is compatible and my graphics drivers are up-to-date.

What happened?
I haven't been able to run any examples when compiling the binary as static with x86_64-unknown-linux-gnu target
it just segfault, running non statically works however.
What is the expected behavior?
for it to work.
Version
8.0
Operative System
Linux
Do you have any log output?
`zsh: segmentation fault (core dumped)  RUST_BACKTRACE=1 cargo run`

also, the issue doesn't happen with windows-gnu target.


adapter stopped working

Hi all, I just noticed that my telegram adapter has stopped working. I have a bot that was used successfully for quite a long time but not anymore. I am not aware of any change that might have caused this. Could anyone point me into a direction how to trouble-shoot this?
BR

Admin 7.1.5
Nodejs: v20.18.0
js-controller: 6.0.11
Telegram Adapter: 3.9.0
Instance-Status: green (all green)
used rsesponse to send a message ...
no log (debug)

@mcm1957
I'd classify this as bug .. but not sure .. information added above.

I still recommend to discuss this issue at the forum - you will get responses from more users there.
The above log is most likely no DEBUG log. There is no indication that you wrote anything to any state logged.
Please set instance to debug level and reproduce the problem.
How do you write data to responce state? Is ack set to false?

You were correct "debug" didn't stick .. but typing something via "response" still doesn't trigger anything. I already tried renewing all the objects.

telegram.0 | 2024-11-05 07:23:33.820 | debug | getMe:   {"id":765455045,"is_bot":true,"first_name":"ringbot","username":"ring53bot","can_join_groups":true,"can_read_all_group_messages":false,"supports_inline_queries":false,"can_connect_to_business":false,"has_main_web_app":false}
-- | -- | -- | --
telegram.0 | 2024-11-05 07:23:33.596 | debug | Start polling with: 300(number) ms interval
telegram.0 | 2024-11-05 07:23:33.390 | info | starting. Version 3.9.0 in /opt/iobroker/node_modules/iobroker.telegram, node: v20.18.0, js-controller: 6.0.11
telegram.0 | 2024-11-05 07:23:32.963 | debug | Plugin sentry Initialize Plugin (enabled=true)
telegram.0 | 2024-11-05 07:23:32.928 | debug | States connected to redis: <IP_ADDRESS>:9000
telegram.0 | 2024-11-05 07:23:32.869 | debug | States create User PubSub Client
telegram.0 | 2024-11-05 07:23:32.868 | debug | States create System PubSub Client
telegram.0 | 2024-11-05 07:23:32.857 | debug | Redis States: Use Redis connection: <IP_ADDRESS>:9000
telegram.0 | 2024-11-05 07:23:32.833 | debug | Objects connected to redis: <IP_ADDRESS>:9001
telegram.0 | 2024-11-05 07:23:32.826 | debug | Objects client initialize lua scripts
telegram.0 | 2024-11-05 07:23:32.788 | debug | Objects create User PubSub Client
telegram.0 | 2024-11-05 07:23:32.787 | debug | Objects create System PubSub Client
telegram.0 | 2024-11-05 07:23:32.785 | debug | Objects client ready ... initialize now
telegram.0 | 2024-11-05 07:23:32.755 | debug | Redis Objects: Use Redis connection: <IP_ADDRESS>:9001
telegram.0 | 2024-11-05 07:23:27.076 | info | Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
telegram.0 | 2024-11-05 07:23:27.074 | info | terminating
telegram.0 | 2024-11-05 07:23:26.572 | info | Got terminate signal TERMINATE_YOURSELF

As I mentioned .. I didn't change anything .. these settings worked. And I know the bot works because my n8n instance provides me with messages.

Diag shows adapter inactive .. in the GUI it's green. "iob start telegram" show no output.

@mcm1957
I removed the adapter and reinstalled it.
I made a new bot and used the new token.
I made a blockly that sends a test message every minute.
Nothing!

02Log-Größe: 2.1 MB

--

Ich bekomme aber auch keine bot started/stopped meldungen vom Bot.

Thanks for feedback.


Add more files to .npmignore

We probably forgot to add these files to .npmignore when creating them.

:+1:


Publish for Scala 3

Implemented in #97. Snapshots are now already published, next release will support scala 3 as well.


[PERF] testing with triangle

Includes ISPN-7367 (PR: https://github.com/infinispan/infinispan/pull/4774)
Partial work: removing the PrimaryAckCommand
Testing: Add NO_FC to BackupAck.
Some refactoring in small methods.

run performance tests please
library dist writes

run performance tests please
library dist writes

ops...

run performance tests please
library dist writes

run performance tests please
library dist writes

last try...


fix: terraform destroy fullstack error

Description
This fixes the failure to destroy resources for full stack solution , if terraform apply fails in between. Added extra check to find the keys in the object.
Types of changes in this PR
No release required

[ ] Examples or tests (addition or updates of examples or tests)
[ ] Documentation update
[ ] CI-related update (pipeline, etc.)
[ ] Other changes that don't affect Terraform code

Release required

[x] Bug fix (patch release (x.x.X): Change that fixes an issue and is compatible with earlier versions)
[ ] New feature (minor release (x.X.x): Change that adds functionality and is compatible with earlier versions)
[ ] Breaking change (major release (X.x.x): Change that is likely incompatible with previous versions)

Release notes content
Replace this text with information that users need to know about the bug fixes, features, and breaking changes. This information helps the merger write the commit message that is published in the release notes for the module.

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

Merge actions for mergers

Merge by using "Squash and merge".

Use a relevant conventional commit message that is based on the PR contents and any release notes provided by the PR author.
The commit message determines whether a new version of the module is needed, and if so, which semver increment to use (major, minor, or patch).

@kbiegert please approve

:tada: This PR is included in version 6.3.1 :tada:
The release is available on:

GitHub release
v6.3.1

Your semantic-release bot :package::rocket:


Implement initial background indexing of a project

Implements an initial background index when the project is opened.
The following will be implemented in follow-up PRs:

Resolving package dependencies
Preparing dependent modules
Watching for file updates

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test Windows

is it support other BSP or only Swift Package Manager?

To start off, I’m only aiming to support SwiftPM. I just opened https://github.com/apple/sourcekit-lsp/issues/1226 from my local to-do list so we can share ideas there. If you could comment there which BSP server you are using with SourceKit-LSP, that would be valuable.

Merging this to unblock further work on background indexing. Will address review comments in follow-up PRs.


txt2al shouldn't handle LineStart differences in delta files

the txt2al.exe of the latest bcinsider ("version": "14.0.26992.0" bcinsider.azurecr.io/bcsandbox-master:w1-ltsc2019) still cannot handle LineStart differences in delta files. Could you please change the txt2al.exe so it skips these LineStart PropertyModifications?
example delta file:
{ PropertyModification;
Target=OnBeforeCodeInsertInvLineFromShptLine(PROCEDURE 15);
Property=Attributes;
OriginalValue=[[Integration]][LineStart(352)]]];
ModifiedValue=[[Integration]][LineStart(363)]]] }

The fix for this issue has been checked in to the master branch. It will be available in the bcinsider.azurecr.io/bcsandbox-master Docker image starting from platform build number 28873.
If you don’t have access to these images you need to become part of the Ready2Go program: aka.ms/readytogo
For more details on code branches and docker images please read:
https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/
https://blogs.msdn.microsoft.com/freddyk/2018/04/16/which-docker-image-is-the-right-for-you/

The fix for this issue has been checked in to the master branch. It will be available in the bcinsider.azurecr.io/bcsandbox-master Docker image starting from platform build number 28873 and VS Code Extension Version 3.0.104165.
If you don’t have access to these images you need to become part of the Ready2Go program: aka.ms/readytogo
For more details on code branches and docker images please read:
https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/
https://blogs.msdn.microsoft.com/freddyk/2018/04/16/which-docker-image-is-the-right-for-you/

the problem isn`t fixed, issue #4914 created
the txt2al still goes berserk is on linestart diffs
tested in build BC14CU0 (14.0.29530) and tested in latest build (14.0.31388)

Hi @Pieterheinevdm, did you also re-generated the delta files using the command Compare-NAVApplicationObject? The fix was made there in order to ignore the attribute LineStart.


[Feature] Adopt Provincial Testing Sheet - Sleuthing and updating

We need assistance with someone who can adopt to update this file and also look for older entries [For example from provincial reports] like the Western Cape daily updates.
This is for total number of tests done per province.
We need to go back as much as we can and also get into a rhythm of updating this frequently as testing information comes in.
https://github.com/dsfsi/covid19za/blob/master/data/covid19za_provincial_cumulative_timeline_testing.csv

This needs to be done daily?

@Tensorflow13, not all data is updated daily by provinces. So it can be a scheduled update, like very 2 days.

I’ve only seen updates really from the following…and they lower they get…the less consistent
Regular:
WC
GP
Semi regular:
NW
MP
Rare:
KZN
Never:
EC
FS
LP
NC
On 04 May 2020, 09:29 +0200, Vukosi<EMAIL_ADDRESS>wrote:

@Tensorflow13, not all data is updated daily by provinces. So it can be a scheduled update, like very 2 days.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Thanks @uelsimon can you update those that have been regular and semi regular for the last 2 weeks or so?

May not be able to commit to updating the CSVs…. But how about this instead (as my contribution).
I already do the scour and dump in my own spreadsheet. Anyone from the team is welcome to grab it for there. I’ve been doing a pretty comprehensive scour for a few weeks, so what I have..should be pretty accurate.
Only use what’s on the Master Data tab https://docs.google.com/spreadsheets/d/1Pyt2nfOpH0KPB5LOxeYHkYbKA7F9cRPpapyfWGIUowE/edit?usp=sharing
€
On 04 May 2020, 10:04 +0200, Vukosi<EMAIL_ADDRESS>wrote:

Thanks @uelsimon can you update those that have been regular and semi regular for the last 2 weeks or so?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@uelsimon that is fine. If we can extract data from your sheet for the csvs and you can upload them here [for what you have] I can then commit them to improve the starting data. Let us know what other data you have and where we should put it.
The good thing about your doing the csv pull request yourself is it is recorded in github contributors.

Fair enough…. Lemme find a YouTube video for a refresher on the easiest way to do that lol…and I’ll jump in later on the live updates
As for the data I have, I’ve captured literally any stat that has been uttered from an official public source. ( think I started around mid march). The best source for consolidated data is twitter (speed and content). I’ve created this list as my jump-off point and I check it nightly, when most folks have updated their info for the day. https://twitter.com/i/lists/1251424430900871168
I record my data based on the press release date…and not the data date. ( what they say on may 4th, is recorded in my data on may 4th….even though they are reporting on the numbers for may 3rd as of midnight)
But I’ve intentionally kept everything on the one sheet, so I can get an overview of what is happening across the board. Zooming out, you will get a sense of the inconsistency in reporting…particularly at the province level…. But I don't know if its a capacity issue..or capability issue. And haven't reached out to find out if thats something they can use help with. (I haven't retroactively searched to fill initial gaps….but those Ive checked only started reporting late… like GP when they came back into session. KZN’s reporting is SMH for the level of cases they are dealing with.
€
On 04 May 2020, 10:19 +0200, Vukosi<EMAIL_ADDRESS>wrote:

@uelsimon that is fine. If we can extract data from your sheet for the csvs and you can upload them here [for what you have] I can then commit them to improve the starting data. Let us know what other data you have and where we should put it.
The good thing about your doing the csv pull request yourself is it is recorded in github contributors.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

We have a guide on pull requests here https://opensource.com/article/19/7/create-pull-request-github
You can also just create sheet pages on your google sheets and just ask me to review before you convert them to csv.

We need assistance with someone who can adopt to update this file and also look for older entries [For example from provincial reports] like the Western Cape daily updates.
This is for total number of tests done per province.
We need to go back as much as we can and also get into a rhythm of updating this frequently as testing information comes in.
https://github.com/dsfsi/covid19za/blob/master/data/covid19za_provincial_cumulative_timeline_testing.csv

I have have gone through all the Coronavirus Press Releases from the Western Cape Gov and extracted the data they provided into a Google Sheet.  I have added a infered date column as they have said they report at 5pm (now 1pm) the previous days numbers.
I have copied the data to a Google Sheet at https://docs.google.com/spreadsheets/d/17Jzxi_ejt5nO10TIQK3qXyIiNBsjCfYXJ8t7OY6G2RU/edit?usp=sharing
@vukosim I am happy to extract the WC Testing data and add it to the testing file.

@uelsimon Are you able to share your sheet.

https://docs.google.com/spreadsheets/d/1Pyt2nfOpH0KPB5LOxeYHkYbKA7F9cRPpapyfWGIUowE/edit?usp=sharing
I am slowly working my way to being able to directly make edits.  Downloaded GitHub desktop and cloned the repo.  But mostly challenged on time.
All my data is on the Master Data Sheet, derivatives and remixes are on other sheets…so I’d recommend just focusing on the Master Data Tab for what is needed.
On 10 May 2020, 15:25 +0200, Vukosi<EMAIL_ADDRESS>wrote:

@uelsimon Are you able to share your sheet.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

For testing data the NICD epidemiological briefs give comprehensive testing information at provincial level. eg.  https://www.nicd.ac.za/wp-content/uploads/2020/05/NICD-Weekly-Epidemiological-Brief_-Week-ending-09-May-2020-002-00000002-1.pdf   There only 3 briefs so far but hopefully they will be weekly.

Thanks @shaze we are keeping track of that. Just need some time or a volunteer to extract all that data.

@vukosim Am happy to do this though it will take me about a week to catch up The NICD reports give number of tests per capita in each province based on Stats SA 2019 mid-year estimates. But I see people here are working on this too and I don't want do duplicate it. While the NICD reports are only weekly and seem to come out a few days later I would recommend them as being highly reliable compared to trying to get from a whole miscellany of different sources.

Agreed, I just reviewed the provincial provided versions of tests...and the numbers are definitely not aligned. But this is to be expected as the NICD numbers and province numbers have never fully aligned.  So it is prolly best to limit this document to NICD periodic updates.

Let me know if you want me to do this.

Please do @shaze.  Thanks in advance

I have been doing this but there seems to be a duplication between this
https://github.com/dsfsi/covid19za/blob/master/data/district_data/provincial_testing_data.csv
and
https://github.com/dsfsi/covid19za/blob/master/data/covid19za_provincial_cumulative_timeline_testing.csv
There seems to be duplication between what I am doing and what @lrossouw is doing. We should only have one. Some overlaps between data is useful (for example, I have added cases to my tests file because the dates on which the difference department releases information is different and it's useful to be able to cross-reference) but these files are doing the same things. I am happy to step back with this if @lrossouw wants to run with it.

I had not seen the provincial table in the district folder.  I also think there are provincial data released sporadically by each province vs. provinical data release by NICD on (possibly) on a weekly basis.
I had not committed to updating it but did commit some numbers when I saw them.  I would say the right place for data released nationally for provinces would be data/covid19za_provincial_cumulative_timeline_testing.csv.  All other provincial data sits in that path. It would not make sense to make logical sense to put provincial data in a district folder but I don't know the folder hierarchy.
I though I might use it for a model I was building but not sure if I will.
I would try to update where I can.  Happy to take guidance from maintainer as to where what should be though :)

Agreed-- I think  @vukosim should make a call here.
I think we should avoid ad hoc release of data by individual provinces because it makes it very hard to compare across provinces (or rather if there is there is a province that releases this daily then there should be a separate file for it). And I think we should avoid secondary sources using only official resources like NICD or one of the departments of health.

@vukosim @lrossouw @SimonRosen173  I agree with @lrossouw  We don't want to duplicate work and I don't think we should have the same data in two different places as it is confusing and hard to maintain. Unless there are objections, I suggest to delete https://github.com/dsfsi/covid19za/blob/master/data/district_data/provincial_testing_data.csv and   that we should adopt covid19za_provincial_cumulative_timeline_testing.csv as the source for testing data.


Fix word overflow in file search page

Before:

After:

@yp05327 please fix the merge conflicts. :tea:

@yp05327 please fix the merge conflicts. 🍵

Where is the merge conflicts?
@lunny
Did you fix them?


md5 deprecation

As part of #903, removing MD5 references for high priority security advisories.

Removal of endpoints as dead code
This is cleanup of dead code no longer utilized in nb5.


Update aws library to support latest fargate features

Updating the vendored aws-sdk-go to be able to use the latest ECS features.

@iterion thanks for the PR. Did you use govendor to update the deps. I haven't done it in a while but I think the vendor.json would normally get updated with it.

Ah, apologies, I did not, I'll update with govendor and update this PR.

OK, this has been updated correctly with govendor.

Thanks @iterion


Incorrect url in apollo engine readme

Hi there.
In several Readme.md files the git clone url is incorrect. Should be for example:
git clone https://github.com/graphcool/graphql-yoga.git
cd graphql-yoga/examples/apollo-engine

instead of :
git clone https://github.com/graphcool/graphql-yoga/
cd graphql-yoga/examples/apollo-engine

The .git isn’t actually needed to clone a repository.

Yep, I thought the same thing but:
marcote@macross:~/code|⇒  git clone https://github.com/graphcool/graphql-yoga/
Cloning into 'graphql-yoga'...
ERROR: Repository not found.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Ah, maybe it is the trailing forward slash. Nonetheless, it’s merged now :)

Thanks!!

Thanks for correcting it!


[hmac,dv] Improve slightly fcov

replace auto bins by ranges as auto bins were giving coverage mostly on index 0, as this is calculated per seed. Now changed into ranges.
add sampling of cfg anytime hash_start/hash_continue are triggered to also sample error cases.
tweak a bit long messages to target more what this test intent is.

Thanks for this. I agree with @antmarzam about ways this could be cleaner, but that probably doesn't need to happen in this PR.


get item

Could not create branch /#87/get_item due to: refs/heads//#87/get_item is not a valid ref name. - https://docs.github.com/rest/git/refs#create-a-reference


[BEAM-6771] MetricsContainerStepMap#equals required for Spark.

Please see the jira for information. I have tested this with a local build of release-2.11.0 branch and my pipeline now succeeds on Spark 2.2.1.
This will also close BEAM-6546.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

R: @huygaa11
R: @robinyqiu
R: @lukecwik

R: @ajamato

Run Java PreCommit

Please update this PR with unit tests testing equality and inequality of the various equals() methods added

@ajamato Done! Anything else?

LGTM, thank you for this change :D


Swarm node missing

I already read https://github.com/docker/swarm/issues/563 but I think this issue is difference.
I'm not cloning VMs and I'm sure that all the key on Docker hosts is difference.
$ docker version
Client:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   a34a1d5
 Built:        Fri Nov 20 13:12:04 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      swarm/1.0.1
 API version:  1.21
 Go version:   go1.5.2
 Git commit:   744e3a3
 Built:
 OS/Arch:      linux/amd64

$ docker run --rm=true swarm list consul://consul.example.com:8500
bpl-nde-01.example.com:2376
bpl-nde-02.example.com:2376
bpl-nde-03.example.com:2376
bpl-nde-04.example.com:2376
bpl-nde-05.example.com:2376
bpl-ngn-01.pre-example.com:2376
bpl-ngn-02.pre-example.com:2376
bpl-ngx-01.example.com:2376
bpl-ngx-02.example.com:2376
bpl-ngx-03.example.com:2376

$ docker-machine ls
NAME             ACTIVE      URL       STATE     URL                                  SWARM                     DOCKER   ERRORS
bpl-prd-nde-01   -           generic   Running   tcp://bpl-nde-01.example.com:2376      bpl-pre-ngn-01            v1.9.1
bpl-prd-nde-02   -           generic   Running   tcp://bpl-nde-02.example.com:2376      bpl-pre-ngn-01            v1.9.1
bpl-prd-nde-03   -           generic   Running   tcp://bpl-nde-03.example.com:2376      bpl-pre-ngn-01            v1.9.1
bpl-prd-nde-04   -           generic   Running   tcp://bpl-nde-04.example.com:2376      bpl-pre-ngn-01            v1.9.1
bpl-prd-nde-05   -           generic   Running   tcp://bpl-nde-05.example.com:2376      bpl-pre-ngn-01            v1.9.1
bpl-prd-ngx-01   -           generic   Running   tcp://bpl-ngx-01.example.com:2376      bpl-pre-ngn-01            v1.9.1
bpl-prd-ngx-02   -           generic   Running   tcp://bpl-ngx-02.example.com:2376      bpl-pre-ngn-01            v1.9.1
bpl-prd-ngx-03   -           generic   Running   tcp://bpl-ngx-03.example.com:2376      bpl-pre-ngn-01            v1.9.1
bpl-pre-ngn-01   * (swarm)   generic   Running   tcp://bpl-ngn-01.pre-example.com:2376   bpl-pre-ngn-01 (master)   v1.9.1
bpl-pre-ngn-02   -           generic   Running   tcp://bpl-ngn-02.pre-example.com:2376   bpl-pre-ngn-01            v1.9.1

$ eval $(docker-machine env --swarm bpl-pre-ngn-01)
$ docker info
Containers: 24
Images: 102
Role: primary
Strategy: spread
Filters: health, port, dependency, affinity, constraint
Nodes: 8
 bpl-prd-nde-01: bpl-nde-01.example.com:2376
  └ Status: Healthy
  └ Containers: 2
  └ Reserved CPUs: 0 / 4
  └ Reserved Memory: 0 B / 8.179 GiB
  └ Labels: com.example.bpl-nde=true, executiondriver=native-0.2, kernelversion=3.19.0-47-generic, operatingsystem=Ubuntu 14.04.3 LTS, provider=generic, storagedriver=overlay
 bpl-prd-nde-03: bpl-nde-03.example.com:2376
  └ Status: Healthy
  └ Containers: 2
  └ Reserved CPUs: 0 / 4
  └ Reserved Memory: 0 B / 8.179 GiB
  └ Labels: com.example.bpl-nde=true, executiondriver=native-0.2, kernelversion=3.19.0-47-generic, operatingsystem=Ubuntu 14.04.3 LTS, provider=generic, storagedriver=overlay
 bpl-prd-nde-04: bpl-nde-04.example.com:2376
  └ Status: Healthy
  └ Containers: 2
  └ Reserved CPUs: 0 / 4
  └ Reserved Memory: 0 B / 8.179 GiB
  └ Labels: com.example.bpl-nde=true, executiondriver=native-0.2, kernelversion=3.19.0-47-generic, operatingsystem=Ubuntu 14.04.3 LTS, provider=generic, storagedriver=overlay
 bpl-prd-ngx-01: bpl-ngx-01.example.com:2376
  └ Status: Healthy
  └ Containers: 3
  └ Reserved CPUs: 0 / 2
  └ Reserved Memory: 0 B / 2.044 GiB
  └ Labels: com.example.bpl-ngx=true, executiondriver=native-0.2, kernelversion=3.19.0-47-generic, operatingsystem=Ubuntu 14.04.3 LTS, provider=generic, storagedriver=overlay
 bpl-prd-ngx-02: bpl-ngx-02.example.com:2376
  └ Status: Healthy
  └ Containers: 3
  └ Reserved CPUs: 0 / 2
  └ Reserved Memory: 0 B / 2.044 GiB
  └ Labels: com.example.bpl-ngx=true, executiondriver=native-0.2, kernelversion=3.19.0-47-generic, operatingsystem=Ubuntu 14.04.3 LTS, provider=generic, storagedriver=overlay
 bpl-prd-ngx-03: bpl-ngx-03.example.com:2376
  └ Status: Healthy
  └ Containers: 3
  └ Reserved CPUs: 0 / 2
  └ Reserved Memory: 0 B / 2.044 GiB
  └ Labels: com.example.bpl-ngx=true, executiondriver=native-0.2, kernelversion=3.19.0-47-generic, operatingsystem=Ubuntu 14.04.3 LTS, provider=generic, storagedriver=overlay
 bpl-pre-ngn-01: bpl-ngn-01.pre-example.com:2376
  └ Status: Healthy
  └ Containers: 5
  └ Reserved CPUs: 0 / 4
  └ Reserved Memory: 0 B / 8.179 GiB
  └ Labels: com.example.pre-bpl=true, executiondriver=native-0.2, kernelversion=3.19.0-47-generic, operatingsystem=Ubuntu 14.04.3 LTS, provider=generic, storagedriver=overlay
 bpl-pre-ngn-02: bpl-ngn-02.pre-example.com:2376
  └ Status: Healthy
  └ Containers: 4
  └ Reserved CPUs: 0 / 4
  └ Reserved Memory: 0 B / 8.179 GiB
  └ Labels: com.example.pre-bpl=true, executiondriver=native-0.2, kernelversion=3.19.0-47-generic, operatingsystem=Ubuntu 14.04.3 LTS, provider=generic, storagedriver=overlay
CPUs: 26
Total Memory: 47.03 GiB
Name: bpl-pre-ngn-01

$ docker pull nginx
Using default tag: latest
bpl-prd-nde-01: Pulling nginx:latest... : downloaded
bpl-prd-ngx-01: Pulling nginx:latest... : downloaded
bpl-prd-ngx-03: Pulling nginx:latest... : downloaded
bpl-prd-ngx-02: Pulling nginx:latest... : downloaded
bpl-pre-ngn-01: Pulling nginx:latest... : downloaded
bpl-pre-ngn-02: Pulling nginx:latest... : downloaded
bpl-prd-nde-03: Pulling nginx:latest... : downloaded
bpl-prd-nde-04: Pulling nginx:latest... : downloaded

At first when I create this cluster, all nodes are working as expected. But as you can see from above. Swarm node bpl-prd-nde-02 and bpl-prd-nde-05 is missing after few days.
Please let me know if you need any more information.

What's their STATE in machine's ls output?

Please see output of docker-machine ls on my first post. All states is Running.

Swarm node bpl-prd-nde-02 and bpl-prd-nde-05 is missing after few days.

So is dm output the same "after few days" ?

Yes. The output you see is the output from current status.

@winggundamth can you please try to update to swarm:1.1.0-rc2 ? nodes shouldn't disappear and you will see the error listed in docker info.
the node management was greatly improved in 1.1.0

@winggundamth did Swarm rc2 resolve your issue?

After I upgraded to Docker 1.10.0 and restart all node. Everything went back fine again.
@amitshukla btw how to upgrade swarm? I ran swarm in container that has been automatic setup by docker-machine --swarm but I couldn't find any document write about how to upgrade swarm.

Shall we close this?

Everything still work fine until now. So I'll close this issue. By the way I still have question how to upgrade swarm that has been setup with docker machine?

@winggundamth In your case there are 2 different ways to upgrade swarm. Swarm is run as a docker container in your case. You can start a new container to run latest swarm image or selected image as shown in (https://docs.docker.com/swarm/install-w-machine/). And remove the old containers.
If you follow (https://docs.docker.com/swarm/provision-with-machine/), the other way to upgrade is to provision a new docker-machine with swarm which by default runs the latest image. And remove the old docker-machine.


AVX512 not working with MSVC compiler VS 17.12.1

We use Simde 0.8.4 to port our MSVC project to macOS/ARM. For performance reasons, we use AVX2/AVX512 intrinsics a lot in the core algorithms.
The problem is:
As soon as we include avx512.h like this:
#define SIMDE_ENABLE_NATIVE_ALIASES
#include "simde/x86/avx512.h"
the Microsoft compiler shows these errors:
1>C:\Users\mtoeltsch\dev\DSS\DeepSkyStackerKernel\simde\x86\avx512\types.h(622,25): error C2371: '__m512': redefinition; different basic types
1>(compiling source file '/avx.cpp')
1> C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.42.34433\include\zmmintrin.h(47,61):
1> see declaration of '__m512'
1>C:\Users\mtoeltsch\dev\DSS\DeepSkyStackerKernel\simde\x86\avx512\types.h(623,26): error C2371: '__m512i': redefinition; different basic types
1>(compiling source file '/avx.cpp')
Note that we do not include zmmintrin.h or any other intrinsics header file.
BTW: You get similar problems, if you do the same with the Compiler Explorer ( https://simde.netlify.app/godbolt/demo ).

@mtoeltsch Thank you for your report. What is the MSVC version? Can you try a newer or older version?

@mtoeltsch Thank you for your report. What is the MSVC version? Can you try a newer or older version?

Hi Michael,
thanks for your quick reply. It's Visual Studio 17.12.1. There is no newer version. 17.12.0 had the same problem AFAI remember.
Hmmm, I could try to install one of the 17.11 versions, or - maybe quicker - could try different versions on Compiler Explorer.

I tried on Compiler Explorer:
VS 17.10
VS 17.0
VS 16.11
VS 16.0
They all have the same problem. Hundreds of errors and warnings as soon as you include "avx512.h".
Mainly redefinitions, e.g. of __m256. Etc.

Thank you @mtoeltsch for that additional information. We never tested SIMDE_ENABLE_NATIVE_ALIASES with MSVC, so that is why this was not found sooner.
A fix would be welcome. You can work around this by leaving out SIMDE_ENABLE_NATIVE_ALIASES and adding the simde_ prefix. To automate that, see the script test/native-aliases.sh.

You can work around this by leaving out SIMDE_ENABLE_NATIVE_ALIASES and adding the simde_ prefix. To automate that, see the script test/native-aliases.sh.

Puh, I'm very reluctant to make those changes to all our intrinsics in the code (adding simde_ ), there are about 2000 of them.
And probably another 1000-2000 variables of different vector types (__m256, __m512, ...).
It's not a question of automating that change, it's more a question of being "locked-in" to Simde. We would then always need Simde (8MB header files!) for compilation.
Can you please keep me posted as soon as a fix is available?
Thanks,
Martin

Can you please keep me posted as soon as a fix is available?

Of course, you will be informed via this issue.
Looking at https://github.com/simd-everywhere/simde/blob/60a3a24462d5c074f669ed8b39c85f5b1128108f/simde/x86/avx512/types.h#L45 it seems this is a general issue with MSVC, perhaps clang-cl will work better for you?
To set expectations, it is unlikely that I will be personally providing a fix. MSVC is outside the area of my expertise.

it seems this is a general issue with MSVC, perhaps clang-cl will work better for you?

I agree. It seems as MSVC always "consults/inspects" <immintrin.h> (not to say "includes"), even if you don't explicitlx #include it. No idea though, how/why this is done ...

To set expectations, it is unlikely that I will be personally providing a fix. MSVC is outside the area of my expertise.

No problem. At the moment we get away with include either <immintrin.h> or "simde/x86/..." depending on platform/compiler.
Just one question: Wouldn't it be better to put all your functions into an own namespace "simde" rather than work with prefixes? That I think would make life a lot easier, right?

Just one question: Wouldn't it be better to put all your functions into an own namespace "simde" rather than work with prefixes? That I think would make life a lot easier, right?

I don't think that would work for C users

MSVC's complex header file included with #include <complex> from simde header file (link) causes this problem.

The workaround I could find is to copy the header file and use the modified file.

MSVC's complex header file included with #include <complex> from simde header file (link) causes this problem.

Thanks for your analysis.

But why do you need to use simde library with MSVC compiler? How about writing this way?
#if _MSC_VER
#include <intrin.h>
#else
#define SIMDE_ENABLE_NATIVE_ALIASES
#include "simde/x86/avx512.h"
#endif

Yes, that's what we do anyway.
The disadvantage is just, that <immintrin.h> provides/implements different things than simde/x86/...  does (and vice versa). So we always have to use the "least common multiple" of both.


basic WifiManager replacement example?

This library sounds exactly like what I need right now - but I have to admit that I can't find any basic documentation on how to get it running?
It sounds as if this module offers the same functionality as WifiManager (start AP mode with wifi configuration captife portal) if the ESP8266 can't connect to its previous network), but allow the ESP8266 to run other stuff while in AP mode. If this is indeed the case, how do I actually do that?

the captive portal gets "http://<apmode_ip>/".
the webserver behind redirects "/" to "index.htm"

you must design an index.htm that will be displayed in captive portal mode or when calling "http://<apmode_ip>/" in a browser
this index htm shouds contain at least two links > for example "WiFi-manager stuff (target: /settings.htm)" and "other stuff (target: myStuff.htm)"
some APIs are available as default. For exampla /wifi, /wifi/rst,
you can create custom APIs (see examples > "server.on"-handlers
all htm files must be uploaded to the flash memory before running the project

Hi @JensW2000
How can I adapt this library to be used without SPIFFS? the idea is that the htm pages are inside the code in the .ino file


Lint Fixes

This PR resolves some linter issues. We are ignoring the code within contracts/revert since that's minified.

@Rishi556 this PR now has conflicts that need to be resolved.


octave interfaces and openmpi

Hi,
This is probably related to https://github.com/shogun-toolbox/shogun/issues/1856, which has been closed.
When octave is compiled with libhdf5-openmpi Shogun's octave interfaces (static and modular) don't build even if hdf5 is disabled in shogun (thanks to karlnapf's patch). OS is Ubuntu 14.04. 64 bit. Octave 3.8.2
Here are the errors

In file included from /home/bee/Downloads/shogun/build/src/interfaces/octave_modular/modshogunOCTAVE_wrap.cxx:154:0:
/usr/local/include/octave-3.8.2/octave/oct.h:31:20: fatal error: config.h: No such file or directory
#include config.h
^
compilation terminated.
In file included from /usr/include/hdf5.h:24:0,
from /usr/local/include/octave-3.8.2/octave/oct-hdf5.h:27,
from /usr/local/include/octave-3.8.2/octave/ov.h:42,
from /home/bee/Downloads/shogun/src/interfaces/octave_modular/sg_print_functions.cpp:3:
/usr/include/H5public.h:63:20: fatal error: mpi.h: No such file or directory
#include mpi.h
compilation terminated.
make[2]: *** [src/interfaces/octave_modular/CMakeFiles/octave_modular.dir/modshogunOCTAVE_wrap.cxx.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [src/interfaces/octave_modular/CMakeFiles/octave_modular.dir/sg_print_functions.cpp.o] Error 1
make[1]: *** [src/interfaces/octave_modular/CMakeFiles/octave_modular.dir/all] Error 2
make: *** [all] Error 2

This comment does not help to solve your problem; I am going to have a closer look right away and let you know if I can add something which may be helpful. Anyway, why do you want to have both Octave modular and static interfaces enabled? If you can afford modular (i.e. having Swig) just use it and ignore static.

Hi,
Thanks for taking a look. No, I am not trying to have both enabled. I have tried one after another, just saying that neither can be enabled.
Cheers.

some problem here,any progress?

(Caution:my octave version is 3.8.1)
I think it may be an octave issue,after modifying two files:
/usr/include/octave-3.8.1/octave/oct.h     line 31:#include <config.h>       ----->   #include "config.h"
/usr/include/octave-3.8.1/octave/oct.h     line 28:#include <base-list.h>   ----->   #include "base-list.h"
compilation passed without error.

In my case (Octave 3.8.2), the second change is in the file comment-list.h, not in oct.h.

After making the changes suggested above, you may still run into the trouble
$octave_root_dir/include/octave-3.8.2/octave/oct-hdf5.h:27:18: fatal error: hdf5.h: No such file or directory
 #include <hdf5.h>

because it seems that octave sets HAVE_HDF5 if it finds hdf5 in your system, no matter the dev package is installed or not. Of course, you can solve this by installing the dev hdf5 package.
In any case, this is an Octave issue rather than a Shogun issue.


HSEARCH-3347 Update the README for Search 6

https://hibernate.atlassian.net//browse/HSEARCH-3347

Pull Request Test Coverage Report for Build 1

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 86.475%

Totals

Change from base Build 32:
0.0%

Covered Lines:
10844

Relevant Lines:
12540

💛  - Coveralls

Fixed the typo and merged, thanks!


Loading Music Library

Checklist:

[x] I have checked that there are no issues with similar or the same content
I've searched through everything.
YOU SHOULD CHECK CLOSED ISSUES ASWELL
[x] I have checked the FAQ (https://github.com/MarshallOfSound/Google-Play-Music-Desktop-Player-UNOFFICIAL-/wiki/FAQ) and the answer I am looking for is not there
[x] I have double checked and can reproduce the issue

OS: Windows 10
GPMDP Version: 4.6.1
Issue Descriptions: Stuck on loading music library, it happened randomly.
Steps to Reproduce: Open the app and try to sign in.
I've tried deleting everything related to GPMDP in %APPDATA% as well as %LOCALAPPDATA%. I've uninstalled, redownloaded and reinstalled multiple times.
One thing I noticed is when I right click on the tray icon > Audio Devices > it says "Loading Devices..." although I'm not sure if it's always said that?
I looked through old issues about audio devices and didn't find solutions - only comments about people having theirs saying "Loading Devices" and that it was going to be fixed in an upcoming release.
Thanks for your assistance.

Hi there.
I am having the same issue.
Every time I start the Desktop Player, it's stuck on loading the library.
Deleted user files already and Google play music works fine in browser or via Station (another service for grabbing the play music service from the internet,)

Double check the first of your checklist :)
https://github.com/MarshallOfSound/Google-Play-Music-Desktop-Player-UNOFFICIAL-/issues/3640

I'm not sure how I missed that through all my searching, but this solution isn't working for me. I've tried opening the file in 7zip (and winrar) and get an error.

I had the same thing with 7zip, I think it's a special form that needs a plugin. In the end I used the zip version on the other issue.

I noticed this issue today. I restarted my PC and when I opened the app, it's stuck on loading library. I tried reinstalling the app and that didn't work either.
If I switch the service to YouTube music, it loads. (Right click on tray icon)

I had the same thing with 7zip, I think it's a special form that needs a plugin. In the end I used the zip version on the other issue.

I tried using the zipped one someone else provided and got errors when I launched GPMDP. Wouldn't even launch. :(

I noticed this issue today. I restarted my PC and when I opened the app, it's stuck on loading library. I tried reinstalling the app and that didn't work either.
If I switch the service to YouTube music, it loads. (Right click on tray icon)

This solves it for me, except for the awful YT Music UI.

I noticed this issue today. I restarted my PC and when I opened the app, it's stuck on loading library. I tried reinstalling the app and that didn't work either.
If I switch the service to YouTube music, it loads. (Right click on tray icon)

I am having the same issue.  Google Play Music will not load.  I can open YouTube Music, but then I don't have all the content and play lists I created in Google Play Music.

See https://github.com/MarshallOfSound/Google-Play-Music-Desktop-Player-UNOFFICIAL-/issues/3640

See #3640

Been there, didn't help.

Closing in favor of #3640. Please discuss there.

See #3640

I looked through #3640 and copied the app.asar zip file that crayfishuk posted in that thread and it resolved my issue.
Thanks for the hlep

See #3640

I looked through #3640 and copied the app.asar zip file that crayfishuk posted in that thread and it resolved my issue.
Thanks for the hlep

I tried copying that file and it didn't help me at all unfortunately.

Will there be a working program for windows 10 to install and use?


ARC context switch to interrupted thread busted with CONFIG_ARC_FIRQ=y and CONFIG_NUM_IRQ_PRIO_LEVELS=1

Describe the bug
The ARC can be configured with support for fast IRQs and only a single priority level.  In this configuration, fast IRQs is the only interrupt type supported by the hardware.
However, the _switch_return_from_firq implementation is expecting the lowest priority interrupt to perform a "regular" interrupt return and thus restore context from the stack.  This does not happen with fast IRQs and therefore the processor state is not restored correctly on such a context switch.  The system immediately goes off the rails as, among other things, neither the stack pointer nor the program counter are restored correctly.
To Reproduce
Steps to reproduce the behavior:

Configure the ARC interrupt controller with firq_option=true and number_of_levels=1, and configure Zephyr to match.
Run any application that performs a context switch to a previously-interrupted task (I called k_msleep twice: the first context switch to the idle thread works but the second crashes after the idle thread is interrupted by the timer).

Expected behavior
Processor state should be correctly restored.
Impact
Behaviour is essentially random, processor typically faults after a few instructions and the system halts.
Environment (please complete the following information):

OS: Zephyr
Toolchain Zephyr SDK
Version 2.6

The attached patch corrects the issue for me.
fix-arc-context-switch.patch.txt

Thanks Nick, for not only reporting the issue but also debugging and suggesting a fix.
Indeed the implicit assumption in the switch code is that a fake interrupt return can be done using the RIRQ. But, if the hardware is configured with only 1 priority (which is not very common, usually there are at least 2 levels), the rtie will follow the FIRQ sequence. We'll need to check if there are other corner cases for your configuration (are you using usermode?).
Would you like to submit your patch as a PR yourself, or do you prefer the ARC team to handle it further?

Probably best to have the ARC team handle it. The patch was the bare minimum to unblock our current project.

In discussion with the reporters, it was decided not to support the FIRQ with only single priority level. To avoid others run in the same issue, a constraint on the configurations is added in #39103.


Better errors for wrong schema

If you use {} instead of z.object({}) you get TypeError: keyValidator._parse is not a function which is not clear. There should be understandable error message that says you need z.object({}) instead of plain object.
Same thing on z.enum('value', 'value') there is error TypeError: array.map is not a function instead of telling you to wrap it in array like z.enum(['value', 'value']).

Also argument validation should be there for example if you pass arguments like z.string(pattern) when you meant z.string().regex(pattern) it works but should be error saying wrong arguments passed.

Thanks for opening this @cdtut.
Took me like 45 minutes to debug-I was passing zod.object instead of plain object into schema.extend()
I mean TS types did warn me, but in case you have the line ignored the error is mindboggling. Why doesn't it throw right there on the line where I call extend()?


Issues with fixed angles for calculating Fajr & Isha in places at high latitudes

What do you think of this article that says fixed degree around the year is not correct in places with high latitudes and low latitudes.
see the link below:
https://www.moonsighting.com/how-we.html

Following: https://github.com/batoulapps/adhan-java/issues/25


Callout updates

updated default, primary, secondary styles
added color mgmt mixin for util colors
added rows/cols for padding

Some style pattern thoughts: We are used to applying a primary prop and seeing a component that has the $primary bkgd color. This component deviates from this in that rev-Callout--primary keeps the default callout bkgd color (set in rev-settings) and only adds a dropshadow.
I think in this case it is an acceptable style deviation because

I personally never need a primary-colored callout
if you look at the button component as a comparison, .rev-Button--primary is only adding a dropshadow and maintains the default button color (although the default button color is $primary).
I would like to further separate primary and secondary classes/props from meaning color. I would like primary to mean 'important' and secondary to mean 'less important', regardless of color.
3a. As a small step towards making this happen, I have changed the $primary color var to $brand since I would like colors to be tied to branding vs. importance. Although there is still a $primary color var which by default is set to $brand. A little ass-backwards but my hope is that you can change your $primary color to be whatever means 'important' to you, and you can still maintain your brand colors.

Yeah, this is way better.


stackoverflow in 1.12.2-0.9.5

What Happened
While exploring on my dedicated server world for my pack World of Dragons a player crashed the server multiple times. The crash reports say it's a stackoverflow error and after the really long stack trace that implicates DynamicTrees the block being ticked is minecraft:fire.
Server Crash Reports
http://paste.ubuntu.com/p/hQ4ThZptf7/
http://paste.ubuntu.com/p/qYx3RtM4zn/
http://paste.ubuntu.com/p/MzJ88Kw8Jp/
http://paste.ubuntu.com/p/CC4gcBNwh2/
http://paste.ubuntu.com/p/bY87JjV7pB/

I've extracted following data from the crash reports:
Coordinate | Chunk | Region
(32002,79,-25680) | 2000,-1605 | 62,-51
(32004,81,-25680)
(32003,82,-25680)
(32002,81,-25678)
(32003,80,-25678)
So you can look at the chunk yourself. Looks like someone set off an explosion or an explosion event has taken place. There are ton of dynamic:falling_trees in the chunk.
r.62.-51.zip

got a screenshot. there is a natural lava flow and a dragon nearby that caused a whole section of forest to burn down.

+1
i am getting the same problem
https://hastebin.com/yaderufoxe.coffeescript

Same thing here. 2 players on the server try to join and we get the same error. Another 4 can join just fine.
[15:37:44] [Server thread/WARN] [net.minecraft.world.WorldServer]: Tried to add entity dynamictrees:falling_tree but it was marked as removed already [15:37:48] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: There are 3/144 players online: [15:37:48] [Server thread/INFO] [net.minecraft.server.dedicated.DedicatedServer]: Ma77h3hac83r, Vibration, Dave_ [15:37:54] [Server thread/WARN] [net.minecraft.server.MinecraftServer]: Can't keep up! Did the system time change, or is the server overloaded? Running 13479ms behind, skipping 269 tick(s) [15:38:00] [Server thread/ERROR] [net.minecraft.server.MinecraftServer]: Encountered an unexpected exception net.minecraft.util.ReportedException: Exception while ticking a block 	at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:762) ~[MinecraftServer.class:?] 	at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:397) ~[nz.class:?] 	at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:668) ~[MinecraftServer.class:?] 	at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:526) [MinecraftServer.class:?] 	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_212] Caused by: java.lang.StackOverflowError 	at com.ferreusveritas.dynamictrees.blocks.BlockRooty.analyse(BlockRooty.java:329) ~[BlockRooty.class:?] 	at com.ferreusveritas.dynamictrees.blocks.BlockBranchBasic.analyse(BlockBranchBasic.java:456) ~[BlockBranchBasic.class:?] 	at com.ferreusveritas.dynamictrees.blocks.BlockBranch.destroyBranchFromNode(BlockBranch.java:246) ~[BlockBranch.class:?] 	at com.ferreusveritas.dynamictrees.blocks.BlockBranch.sloppyBreak(BlockBranch.java:444) ~[BlockBranch.class:?] 	at com.ferreusveritas.dynamictrees.blocks.BlockBranch.func_180663_b(BlockBranch.java:526) ~[BlockBranch.class:?] 	at net.minecraft.world.chunk.Chunk.func_177436_a(Chunk.java:567) ~[axw.class:?] 	at net.minecraft.world.World.func_180501_a(World.java:343) ~[amu.class:?] 	at net.minecraft.world.World.func_175656_a(World.java:425) ~[amu.class:?] 	at com.ferreusveritas.dynamictrees.blocks.BlockBranch.func_180663_b(BlockBranch.java:527) ~[BlockBranch.class:?] 	at net.minecraft.world.chunk.Chunk.func_177436_a(Chunk.java:567) ~[axw.class:?]

happened again, are you absent @ferreusveritas?
https://pastebin.com/PPK7xeWS

In a manner of speaking, yes.  I'm more or less absent.  I haven't had any time to commit to MC modding.  If someone is willing to look over the source code, find a fix and submit a pull request then I'll look it over and merge it.  Otherwise we'll just have to wait until I get around to it when I have time.  I'm sorry.

iirc this has been fixed.  If not then I'll reopen it.


Update LWC Jest and tests following wire protocol reform

Jest LWC  benefits from a wire protocol reform that requires some test code changes.See this PR for a practical example.

You'll want to update @salesforce/sfdx-lwc-jest to 0.13.0.


Name of xarray object should be name of intake object

Outputting named xarray.DataArrays would make it easier to convert to xarray.Datasets and plot.
This should be very straightforward and large reward.

Where would the name come from? This applies only to rasterIO or also elsewhere?

Where would the name come from?

The name is the key in the catalog. It is already an attribute on the intake object. For example:
>>>cat.us_crime.name
'us_crime'

This applies only to rasterIO or also elsewhere?

I think it should apply everywhere, maybe in other plugins as well, but I haven't explored thoroughly.  The pandas analogy for an xr.DataArray is a pd.Series which can also have a name. Naming these things just makes it easier to go to the next order object (xr.Dataset or pd.DataFrame)

I see, that makes sense.


Not a collaborator

I'm not allowed to use your form to create a template because the button is disabled.  I updated the button properties to allow me to submit and got to the real issue: "You are not a collaborator on {user}/{repo}. You won't be able to save this template."
I am the owner of the repo and thus cannot be a collaborator (if I try to add myself as a collaborator, I get the error at Github "Repository owner cannot be a collaborator").
Do I really have to create a dummy Github account to assign collaborator permission in order to use your templating wizards?  I feel like we've missed something simple here (yes, I'm logged into issuetemplate.com with my github credentials and issue-template shows as an authorized application in my settings).

That's odd... Nobody else has reported this at all. I don't know what to
say... Sorry :-/

Kent C. Dodds

(Sent from my mobile device, please forgive typos or brevity)
On Jul 25, 2015 10:03 AM, "Peter Souza"<EMAIL_ADDRESS>wrote:

I'm not allowed to use your form to create a template because the button
is disabled. I updated the button properties to allow me to submit and got
to the real issue: "You are not a collaborator on {user}/{repo}. You won't
be able to save this template."
I am the owner of the repo and thus cannot be a collaborator (if I try to
add myself as a collaborator, I get the error at Github "Repository owner
cannot be a collaborator").
Do I really have to create a dummy Github account to assign collaborator
permission in order to use your templating wizards? I feel like we've
missed something simple here (yes, I'm logged into issuetemplate.com with
my github credentials and issue-template shows as an authorized application
in my settings).
—
Reply to this email directly or view it on GitHub
https://github.com/kentcdodds/issue-template/issues/39.

Let me know if there's something I can do to test.

I would try removing the app's permissions from your account and
reauthorizing.

Kent C. Dodds

(Sent from my mobile device, please forgive typos or brevity)
On Jul 25, 2015 10:10 AM, "Peter Souza"<EMAIL_ADDRESS>wrote:

Let me know if there's something I can do to test.
—
Reply to this email directly or view it on GitHub
https://github.com/kentcdodds/issue-template/issues/39#issuecomment-124858025
.

I'm experiencing the same as of now. Revoking app permissions did not work. @psouza4 did you ever get to work around this?

Nope, I had already tried Kent's suggestion a number of times and was never able to get this working.  I abandoned my attempts and am currently not using any templates, unfortunately.

Really sorry about that :-/ I don't have time to invest into figuring out what's going on. If you find anything out I'd be happy to accept PRs or update some auth configuration so this works for you.

Same here: "Create" button stays disabled, deleting its "disabled" property allows click bringing up "not a collaborator" warning.
Suggest rolling back to last functional version while fix upcoming.

It seems condition on line 19 of TemplateCtrl.js file is never fullfilled
Possibly due to the variable $scope.user.login always "undefined".
Tentative workaround (Using Firefox 40.0.2):
Of note: the exact labels of Firefox menus stated in what follows may not be
absolutely accurate as they result from my hastened translation from those of
my French Firefox interface.
Navigate to http://issuetemplate.com/#/new-template
Fill up at least mandatory fields of the web form.
(this may be skipped at this point but will end up being
more tedious to complete later-on in this workaround process
due to the use of debugger stop-points set in the javascripts
functions "watching" form entries).
Right click on "Create" button of the web form.
Select "inspect element" menu entry.
Should open Firefox dev tools
To the before last node of the following path:

       <form class="margin-top-medium ng-pristine ng-valid" role="form">

         <button class="btn btn-primary ng-binding" ga="" ng-click="submitTemplate()" ng-disabled="!isCollaborator" type="submit" disabled="disabled">Create</button>

Double click on disabled="disabled" of the last node should allow editing of this node section field.
Delete the text content of this node section field.
To be clear, content to be deleted reads as follows: disabled="disabled"
This should now allow the "Create" button of the web form to be responsive to mouse click.
However at this point, submitting the form would raise the "not a collaborator" warning message.
Access the Debugger tab of the Firefox dev tools.
In TemplateCtrl.js, add stop points at lines 18, 32 & 61.
These lines begin with:
18> function checkIfUserIsCollaborator() {
32> $scope.isCollaborator = false;
61> toastr.warning('You are not
Access the Debugger tab of the Firefox dev tools,
Press Ctrl+Shift+E
In the panel that slides in, set a new "spy expression" as follows: $scope.isCollaborator
Click the "Create" button of the web form.
Upon reaching the first stop-point,
Edit the value of $scope.isCollaborator displayed in the "spy expressions" section of the side panel,
From "false" to "true",
Then hit enter for validating, value "true" should now appear in red.
Click the "Play" button close to the top-left panel of the Debugger interface,
Until the "not a collaborator" warning message is raised.
Click warning message away.
If Debugger "Play" status is "Pause" (i.e. not "Play"),
Then clicking the "Create" button of the web form allows the form to be created. Yipee!
Updating the form follows a very similar course of action with the button of the web form being called "Update" instead of "Create",
However, in order to access the editing page you may need to begin by accessing the page of your form first,
Then add "/edit" at the end of the url and validate by pressing enter.
Of note: once the stop-points of the Debugger are activated, it is often necessary to press the "Play" button of the Debugger,
A few times until a stable "pause" position is reached in which the page is fully loaded and none of the script functions is running anymore.
Unless you do so, the elements of the web navigating Firefox window will not be responsive to mouse click.

Should be fixed now!

Still not working - merged but not deployed?

Indeed! Sorry, forgot that this is using the gh-pages branch rather than the master branch. Should be working now (or in a few seconds)...

Working now. Probably worth mentioning that when you enter both the user and repo name you get the pop up again (without pressing anything), but then everything works alright.


Raise exception if broker goes offline

Currently, when the broker goes offline, it seems like all is well from the client perspective. MQTT::V3::Client#ping and #publish still work and no exceptions are raised.

Ah i see this is what MQTT::Transport#on_close is for.


New audit mode for verifiers/policies

As a cluster administrator, I'd like to know when my existing running images are no longer in compliance with the policies I've specified.  For instance, a new vulnerability comes out, the images in container registry are scanned and updated with new vulnerability report, ratify's data source connected to something else listening to the source will alert/notify the cluster administrator of images no longer in compliance.
Engineering notes:
Ideally utilize the existing GK audit capabilities.
Since ratify only updates the external data provider on admission or config change, would need a mechanism to execute verifiers on everything running on cluster with configured/desired schedule to update the external data provider info.
Would need to determine potential methods for users to get alerts from execution/checks surfaced in external data provider.

Would this potentially tie in with a tool like Eraser? This type of functionality would also be great in conjunction with guac for storing dynamic details that may or may not be included in the artifact package in the OCI registry as touched on in #406 .

Closing as GK's audit functionality fully addresses this issue. Violation can be consumed via logs or pub/sub additions.


Allow importing any .envrc file in the project

Probably via the context menu.
Check if source_up works.

Since 07cc045


Keep motors off if battery power below voltage threshold

Do not activate the ENABLE line if the Vin voltage drops below the minimum required for the drivers/motor combination to function, or the minimum acceptable battery voltage.
A threshold slightly above 5V would prevent the drivers being activated while powered from USB, if the step-down leaks current from Vcc to Vin.
Note: also add 10K pull-up on ENABLE to avoid activating the drivers on power-up until setup() got around to setting up the pin.

Just not activating ENABLE is probably fine. The other case, where Vin was good and then drops due to battery depletion, could be a problem. Turning off motors with a heavy lens can slam the lens into the pano unit, so maybe a controlled descent is better (but we don't know when to stop).


Record dataLength from Chrome Dev Tools Protocol

Currently, we record encodedDataLength from Chrome Dev Tools Protocol, but not dataLength. It would be helpful to have both values to display to the end user as part of the waterfall chart flyout.
Associated ticket: https://github.com/elastic/kibana/issues/80166
Reference: https://chromedevtools.github.io/devtools-protocol/tot/Network/#event-dataReceived

Can you also add how we are planning to use these values in the UI or associated ticket.

Updated above.

For reference, the UI issue for this is https://github.com/elastic/kibana/issues/94741


WaitFor integration with Health Check Service

Description
This PR integrates WaitFor with health checks from the .NET hosting model. Extension methods like AddRedis(...) register a health check in DI which uses the connection string which is produced when the resource is provisioned.
A new annotation HealthCheckAnnotation keeps track of the health check names associated with each resource and a health check publisher implementation ResourceNotificationHealthCheckPublisher transcribes health check status from the health check report to a new property on the ResourceEvent (HealthStatus).
In WaitFor we determine whether a resources's dependencies has a HealthCheckAnnotation and if it does it waits for the health status to return healthy.
This PR also introduces a new event .... ConnectionStringAvailableEvent which is used by AddRedis(...) and AddPostgres(...) to detect when the connection string is available so we can store it in a captured string which is used by the health check. This is significant because it allows Azure hosted resources to participate in the health-check enabled WaitFor(...) experience.
In the case of DCP hosted resource sthe ConnectionStringAvailableEvent is fired at the same time as BeforeResourceStartedEvent - but in the case of the AzureProvisioner it is fired after the resource is online in Azure (so the order is roughly opposite) - hence why we needed another event (Azure hosted resources don't get endpoint allocated events).
Checklist

Is this feature complete?

[ ] Yes. Ready to ship.
[x] No. Follow-up changes expected.

Are you including unit tests for the changes and scenario tests if relevant?

[ ] Yes
[x] No

Did you add public API?

[x] Yes

If yes, did you have an API Review for it?

[ ] Yes
[ ] No

Did you add <remarks /> and <code /> elements on your triple slash comments?

[ ] Yes
[x] No

[ ] No

Does the change make any security assumptions or guarantees?

[ ] Yes

If yes, have you done a threat model and had a security review?

[ ] Yes
[x] No

[ ] No

Does the change require an update in our Aspire docs?

[x] Yes

Link to aspire-docs issue:

[ ] No

Microsoft Reviewers: Open in CodeFlow

This is functionally complete for Redis and Postgres (Postgres being an example of a resource with child resources). Moving on to working on tests and polish.
My plan is to merge this and then do other resources as subsequent commits to keep them relatively small and focused.

This needs tests

This needs tests

Yes it does! I didn't think you'd like me #YOLO merge this one.

/azp run


Error: asyncio.run() cannot be called from a running event loop

I encountered an issue when trying to run the code that results in the following error message:
asyncio.run() cannot be called from a running event loop
Followed the steps to create a key.
Added the page to the workspace.
Ran the code.

Hi @vigneshmj1997, I guess you're trying to run notion-haystack in a Jupyter Notebook? As explained in the example notebook, you need to run nest_asyncio in notebooks.


Remove AppChannelAllowInsecureTls flag

Description
Removes AppChannelAllowInsecurerTLS flag, as it needs to be removed in 1.13
Issue reference

Please reference the issue this PR will close: #7149
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

/ok-to-test


chore(release): 2.67.0

See CHANGELOG

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 7d9d75aa4d8d4a71ced9c4fddab39c31846905d9
Result: SUCCEEDED
Build Logs (available for 30 days)

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

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: df88d95b2962b7d736840d545a9b5ec979aa5926
Result: SUCCEEDED
Build Logs (available for 30 days)

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


comma: 1.2.3 -> 1.3.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/nix-community/comma/releases.
meta.description for comma is: "Runs programs without installing them"
meta.homepage for comma is: "https://github.com/nix-community/comma"
meta.changelog for comma is: ""
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 1.3.0 with grep in /nix/store/jffp1kyh1i0jfx6avqajz8ni8v8yigcp-comma-1.3.0
found 1.3.0 in filename of file in /nix/store/jffp1kyh1i0jfx6avqajz8ni8v8yigcp-comma-1.3.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
comma

Instructions to test this update (click to expand)

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

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

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

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

1 package built:

comma

Maintainer pings
cc @Enzime @Artturin for testing.

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

1 package built:

comma


SAS Key in Python SDK differs from C# by a leading '?'

var sasToken = share.GetSharedAccessSignature(sharedAccessFilePolicy); in c# will provide a sas token but with a '?' at the front.
The python equivalent, sas_token = fs.generate_share_shared_access_signature(FILE_SHARE_NAME, expiry=expiry, permission=file.models.SharePermissions(read=True, write=True, delete=True, list=True)) does not.
The issue lies in that if you try to use the C# key, the python sdk fails. Simply trimming the leading '?' allows it to work.

@crwilcox Thanks for bringing this to our attention. After discussing it with my colleagues, we concluded that the Python library actually has the correct behavior. There is no reason why a "?" needs to be added to the SAS token, besides making it easier to copy-paste. We will see how to make the .net library consistent. Thank you! 😃


CMake: allow to add laz-perf with add_subdirectory()

When laz-perf tree is added through add_subdirectory(), CMake generation fails with Run cmake from the top level of the source tree due to https://github.com/hobu/laz-perf/blob/2e3c316248fa534cdeba1b47b2e9fe1a0ecf5dca/cpp/CMakeLists.txt#L1-L3
Indeed CMAKE_PROJECT_NAME always refers to the top level project, not the closest one (which is PROJECT_NAME). I advice to completly remove those 3 lines.

There was no intent to support this configuration. Sorry.
On Sun, May 30, 2021 at 7:48 AM SpaceIm @.***> wrote:

When laz-perf tree is added through add_subdirectory(), CMake generation
fails with Run cmake from the top level of the source tree due to
https://github.com/hobu/laz-perf/blob/2e3c316248fa534cdeba1b47b2e9fe1a0ecf5dca/cpp/CMakeLists.txt#L1-L3
Indeed CMAKE_PROJECT_NAME always refers to the top level project, not the
closest one (which is PROJECT_NAME). I advice to completly remove those 3
lines.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hobu/laz-perf/issues/81, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKBMMAXNDAYHK6CHAMQ67DTQIQYFANCNFSM45ZIYEKQ
.

--
Andrew Bell
@.***

Are you taking an approach that you can build any directory test contains CMakeLists.txt independently? This seems unusual and not an expectation I have heard before.

It's very common to add an external library with add_subdirectory() in its own project (with a submodule, ie vendoring).
But actually here I use add_subdirectory() for conan to properly injects some flags with a wrapper CMakeLists.

The lines you reference were added to provide feedback to people who were attempting to build from the subdirectory in question. I'm not sure if there's a good way to satisfy your use case and that desire, though perhaps the feedback isn't necessary.

As I said, if you really want to keep this block, you can replace CMAKE_PROJECT_NAME by PROJECT_NAME.
But honestly, it's very unusual to see this kind of check.

Fixed with 99ec34f72aa468f522e956001fda058e2c8b1054


remove duplicated broker prometheus metrics type

Motivation
If there are multiple topics from different namespaces, the broker prometheus metrics will print out duplicated # TYPE definition for pulsar_ml_AddEntryBytesRate and other managed ledger metrics.
In fact, this problem can be verified by promtool https://github.com/prometheus/prometheus#building-from-source
On the broker, run this command to check validity of Pulsar broker metric format.
curl localhost:8080/metrics/ | ~/go/bin/promtool check metrics
Modifications
To prevent duplicated metrics type definition, the definition is now tracked and only printed out once. It leverages the existing metrics name Set already defined under parseMetricsToPrometheusMetrics() in PrometheusMetricsGenerator.java
Verifying this change

[ x] Make sure that the change passes the CI checks.

This change added tests and can be verified as follows:
Added two topics under new namespaces to trigger conditions that duplicated prometheus type could happen previously under testManagedLedgerStats() of PrometheusMetricsTest.java. Updated test cases checks this duplicated type problem.
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): no
The public API: no
The schema: no
The default values of configurations: no
The wire protocol: no
The rest endpoints: no
The admin cli options: no
Anything that affects deployment: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented?
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

@sijie @wolfstudy  can we pick this change to 2.6.3 and 2.7.1 ?

/pulsarbot run-failure-checks


added support for jsr233 script engine

Added support for JSR233 script engine API.
This will ease the use of MVEL for products supporting JSR233 API like Camunda BPMN engine to use it for conditions or scripts tasks.

@mariofusco Can we support JSR233 with next mvel release? I have attached a pull request for the same. Any comments regarding the implementation are most welcome.

@mariofusco Can you please point me to a location where i can update mvel documentation to indicate the added jsr233 support?


Want the solution for frontend Vuejs

Hello, you have used backend as nodejs in your repository but i want the only vuejs solution to get the user oauth token from front side  and then forward it to backend laravel, can you please provide me solution to authenticate user from frontside in vuejs with the source code or any other reference from your side.

Sorry that's not what this repo does.

Can you please help me out as a sample code to authenticate and login user in twittr from frontend in vuejs  ?


Forward metrics to Matomo or Posthog

We need a way to forward metrics to one of the following analytics platforms for visualization:

https://matomo.org/
https://posthog.com/

Added PostHog integration.


Boost.Coroutine is now deprecated

This is a question not a bug:
I was trying to build the websocket co-routine example, but I get the Boost.Coroutine deprication warning. I am using Boost 1.68. Is it because asio still using the old  co-routine library?
 #  warning                  "Boost.Coroutine is now deprecated. Please switch to Boost.Coroutine2. To disable this warning message, define BOOST_COROUTINES_NO_DEPRECATION_WARNING."
    ^~~~~~~

I am using Boost 1.68. Is it because asio still using the old co-routine library?

Yes. This is a sore subject, lol! That warning can be safely ignored. If the author of Boost.Coroutine removes the old coroutine library completely (which works perfectly fine and doesn't need to be fiddled with) then the author of Asio will likely just inline the relevant code into the Asio project itself.
In other words, Keep Calm and Carry On.


handleLLMEnd error - not valid JSON

Error in handler Handler, handleLLMEnd: SyntaxError: Unexpected token ']', ..."   },     ] }" is not valid JSON
I am receiving following error randomly. I am using initializeAgentExecutorWithOptions with ConversationSummaryBufferMemory and streaming true.
Please let me know why this error occurs?

The tool used is SERP and also please note the using openai functions. llm is ChatOpenAI gpt 4
const executor = await initializeAgentExecutorWithOptions(             tools,             chat,             {                 agentType: "openai-functions",                 memory: mem,                 verbose: true,                 agentArgs: {                     prefix: prompt,                 },                 //returnIntermediateSteps: true             },         );

Please close the issue as it was something on my end.


intermittent invalid credential errors

Client
Pubsub
Describe Your Environment
Docker container running on a GCE instance.
Expected Behavior
No intermittent auth errors.
Actual Behavior
We occasionally see
rpc error: code = Unauthenticated desc = Request had invalid authentication
    credentials. Expected OAuth 2 access token, login cookie or other valid authentication
    credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.

From sub.Receive. If we wrap the Receive call in a retry, this issue clears up within about a second.
Running on 0.25.0 of this library.

Also have seen rpc error: code = Unavailable desc = Authentication backend unavailable.

And rpc error: code = Unavailable desc = there is no connection available

As well as rpc error: code = Unavailable desc = the connection is draining.
Would this last one occur because we cancelled the context?

Are you using a service account or the default credentials? You should always use a service account in production. See #1047.

We are definitely using a service account with the instance.
Do we need to do anything special when creating the pubsub client and receiving to use the service account credentials?

If we're running the instance under the service account, do we need to do that?

@broady @jadekler @zombiezen any thoughts here?

Hi @nhooyr. When you create a service account, the next step is to create a key for that service account. The key is downloaded in the form of a JSON file.
Now that you have a json file - let's say it lives at /private/creds.json - you can do:
client, err := pubsub.NewClient(ctx, projID, option.WithCredentialsFile("/private/creds.json"))

Without this option, it's likely using default credentials which I believe are more transient - and therefore liable to failure (spitballing, but it's a reasonable guess as to why you're seeing errors I think).

If we're running the instance under the service account, do we need to do that?

I believe so, yes.

@jadekler
That seems wrong to me. Your linked documentation says

To use a service account outside of the Google Cloud Platform (on other platforms or on premise), you must establish the identity of the service account. Public/private key pairs will let you do that.

Those keys are only for when using a service account outside of GCP.

We sshed into an instance where this intermittent errors were occurring and ran:
$ toolbox
$ gcloud auth list

And there was only one account listed, the service account. So I don't think it because we're using the wrong credentials.

@nhooyr it's quite common to use service accounts like this even within GCP. You /must/ use a service account key outside GCP. When running inside GCP, you can use the metadata server, but you can /also/ use a service account key.
How often is this error happening? What percentage of requests? Or does it happen periodically?
If you could run:
creds, err := google.FindDefaultCredentials(ctx)
log.Print(creds.ProjectID == "", err)

How often is this error happening? What percentage of requests? Or does it happen periodically?
Have not measured how often but it occurs periodically for a second or so and then just stops.

Will run the code soon and get back to you.

@broady that returns
2018/08/09 17:38:10 false <nil>

(I'm @nhooyr's coworker)
Here's our data around when this occurs: https://docs.google.com/spreadsheets/d/1eh_rFRMLl3nMAxpuWaxUYIOZ32l2Qabke2yQk_ThWXg/edit#gid=1967454854

In case anyone cannot access @ammario's big query link, you'll need to enable the big query API and set up billing on gcloud.

I think that shows that you're using default credentials, though I'm less familiar with auth. Friendly ping to @broady.

That looks a lot more frequent than I'd expect. Your auth looks good (looks like a service account).
I agree, @pongad, this does look like a backend problem. I wonder if there are any logs on the backend that would be useful.
@ammario @nhooyr if you have a support account with GCP, could you please file a support ticket and link to this thread?

I believe I figured this out, turns out we had a context with a timeout being passed in to the client constructor.

Nvm, still seeing this rpc error: code = Unauthenticated desc = Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.

Well, this is embarrassing, we were closing the pubsub client early.

Whoops! Generally, you'd just keep the pub/sub client open for the duration of your program's life.

Wasn't that, still saw this. Issue was we were doing multiple Receive's for the same sub id and that was causing issues. Was due to the way we structured our app, it was easier to do multiple Receive's vs a single one and threading the messages throughout our app.

Fixed now.


Add list of vendors that bundle DITA-OT

To provide greater visibility of DITA-OT usage within the DITA ecosystem, the website should include a list of CCMS, editors, and other tools that bundle/embed DITA-OT.
This list could be featured on the landing page, possibly with vendor logos (like  https://playframework.com/#references, or other open-source projects that highlight companies using their solution).
We might also want to include a list of customer companies that use DITA-OT in their publishing toolchains, though this list is likely to require a separate page.

@keberlein has begun reaching out to vendors with this idea.

Reminder that companies need to get approval for us to use their logo - apart from that concern, I'm happy to have a list of tools that bundle DITA-OT. I do think the "companies that use" should be on a separate page. Both lists should have an easy way for representatives of the companies to contact us and have names added / removed.

@robander Current thinking is to use PRs for addition/removal requests, with copy something like this:

To add your company to this list, create an issue or open a pull request.

Sounds good - mostly wanted to make sure instructions were on the page, as newcomers possibly wouldn't know about those options.


fix(build): update latest even if higher prereleases are present

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build
What this PR does / why we need it:
If rules marked as 1.0.0, 1.0.1 and 2.0.0-rc1 are present, when 1.0.2 is released it should still be latest because 2.0.0 is not out yet. Fix the build process to consider this case (note the attached test)
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [LucaGuerra]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: incertum, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [LucaGuerra,incertum]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 22b5ec003a7e6789a2114af6f05851f22f42430a


pub trait for UnixStream

I could utilize the code: https://github.com/tmerr/i3ipc-rs/blob/master/src/lib.rs#L123 in my own project. Any chance you are willing to make that trait public?
It's only a bit of code and I have already copied the interesting bits but seen as I am already using this library sharing those methods would be nice.

Possibly, what is the use case?

The UnixStream trait implementation in i3ipc-rs is fairly general and should work for other modules that need to implement their own serialization and deserialization and also  send ints and &str on a stream. The latter part is general to i3ipc and should be easy to share.
The particular use case is an i3bar clone in Rust https://github.com/bpostlethwaite/rubar (eventually this will be several modules r3bar r3msg r3sensors etc). r3bar uses i3ipc-rs for the the workspace switching buttons. However to communicate with the status bar more generally it uses a superset i3ipc protocol in both server and client modes ("talking" i3ipc on msgtypes outside of the i3 band). That part implements the code in i3ipc-rs's UnixStream trait.
Admittedly this is not a huge value add as it is a small amount of straightforward code that won't likely change. Still I would rather reuse than rewrite.

Sorry for the delay. I am leaning toward no for this one, because I don't think enough people will use this to justify the deviation from the goal of the library, which is to abstract such things to make it easy to use. That said if anyone else would be interested in seeing this exposed, I would be willing to reconsider. For now I will be conservative since it is much harder to remove features than add them. Once again, it's a close call, and thank you for bringing up this possible use case!

No problems, thanks for the consideration.


Mic 4.4 changes

4.4 bundles specific change to run it as sane as possible.

retest this please.

Makefile still has 4.3.8 bundle version in it.


feat: release v1.20.0

:tada: This PR is included in version 1.20.0 :tada:
The release is available on:

v1.20.0
GitHub release

Your semantic-release bot :package::rocket:


Add version: CiderCollective.Cider version 1.5.0-beta-beta [FP-O]

Result: Installation Failed

Manifest
Add/Remove Programs

Name
Cider

Version
1.5.0-beta-beta

Publisher
Cider Collective

ProductCode

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 1859

do not push thru


Metamask appears in 3 places when attempting to connect wallet on ITS portal

Looks like this is already fixed.


#69 update scoped, multi-valued animation names

That's a proposition to fix #69. The CSS parser is introduced to parse and create AST.

Coverage remained the same at 100.0% when pulling e24799a1de6269fd4c315d155810b6278b5ad653 on msn0:master into 9c9f581340683051e5127c2ea08a059547f0a5df on rtsao:master.


Add createworkflow failure proto #minor

TL;DR
Adds createworkflow failure proto. This is for more concrete return values when a workflow fails to get created.
For context: https://github.com/flyteorg/flyteadmin/pull/487#issuecomment-1281212131
Type

[ ] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[ ] Code completed
[ ] Smoke tested
[ ] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
How did you fix the bug, make the feature etc. Link to any design docs etc
Tracking Issue
Remove the 'fixes' keyword if there will be multiple PRs to fix the linked issue
fixes https://github.com/flyteorg/flyte/issues/
Follow-up issue
NA
OR
https://github.com/flyteorg/flyte/issues/

@katrogan Would you mind taking a look at this? If it looks good to you, would you mind helping me compile the protobufs? This is out of my wheelhouse unfortunately 😞

hey @jerempy thanks for opening this! can you try these instructions for generating proto code and let me know if that works for you?

Hey there, I did try that and had difficulties. It looks dated since there is no "download_tooling" in the makefile. I tried looking at different things in the make file and couldn't figure out what I was missing. Any other ideas?

hey @jerempy thanks for opening this! can you try these instructions for generating proto code and let me know if that works for you?

Hey there, I did try that and had difficulties. It looks dated since there is no "download_tooling" in the makefile. I tried looking at different things in the make file and couldn't figure out what I was missing. Any other ideas?

ah @jerempy the top-level Makefile should import the boilerplate one with the target: https://github.com/flyteorg/flyteidl/blob/b24a555934138df9fb3d710fbbf77084cc395821/boilerplate/flyte/golang_test_targets/Makefile#L7

@katrogan thanks for all the input! I updated the type for the id - good spotting that!
Thanks for the direction on getting the compiler to work, but I just seem to not be having any luck. Maybe its cuz im on windows 10. I tried through my cmd prompt. I tried through wsl, and I tried to git bash.
When trying to run make command in wsl I would get this error:
Makefile:17: warning: overriding recipe for target 'generate'
boilerplate/flyte/golang_test_targets/Makefile:13: warning: ignoring old recipe for target 'generate'
Makefile:30: warning: overriding recipe for target 'test_unit'
boilerplate/flyte/golang_test_targets/Makefile:38: warning: ignoring old recipe for target 'test_unit'
make: boilerplate/flyte/golang_test_targets/download_tooling.sh: Command not found
make: *** [boilerplate/flyte/golang_test_targets/Makefile:9: download_tooling] Error 127

I tried running the .sh scripts directy and that didn't turn out so good. Wanted to delete 1200 files as a result 😨
So for now I just changed the types on the id and I think I'm a bit out of luck on this one. unfortunately. I might try again tomorrow

hey @jerempy do you mind filing an issue dumping what you ran into?
I can help you with the generation for now. But in the meantime, could I ask you to move the new proto message definitions to the admin workflow proto def: https://github.com/flyteorg/flyteidl/blob/master/protos/flyteidl/admin/workflow.proto rather than the core one you've defined them in now?

@katrogan ok great. thanks much for your help! and good spottin on the location - I moved it. Thanks! 🙏

@EngHabu since you also reviewed the corresponding admin PR, mind reviewing this one too?

@EngHabu thanks for reviewing! I updated the top comment to Include the issue. And thanks @katrogan for compiling for me!

@EngHabu @katrogan if possible, think we could merge this today? After this one is done then I still need to re-do the flyeadmin PR and then the flytekit PR to get this issue resolved and I only got 7 days left until the end of the month 🙏


Production mode: custom UglifyJSPlugin options or file-based devtool config not cached

Expected Behavior
When production mode is enabled, in either of the following cases I expect uglification and sourcemaps to be cache between builds:

Custom UglifyJSPlugin options passed into config.optimization.minimizers (ex. to enable sourceMaps: true
When the devtool setting is set to source-map or hidden-source-map

Actual Behavior
In the two above cases, sourcemaps and uglification are not cached between builds, which causes the build to take much longer than when cached.
Note that when no devtool config is set to none or eval (possibly others), and no customization of UglifyJSPlugin is passed into config.optimization.minimizers, uglification is cached.
Is an error being thrown?
No.
Steps to Reproduce
The default config in production mode will cache uglification between builds (note that in production mode, uglification is on by default, and no source maps are generated as expected since the default devtool setting is none):
config = {
    mode: 'production'
};

But in either of the following two cases, uglification and/or sourcemaps are not cached between builds:
config = {
    mode: 'production',
    devtool: 'source-map'
};

const UglifyJsPlugin = require('uglifyjs-webpack-plugin');
...
config = {
    mode: 'production';
    optimization: {
        minimizer: [
            new UglifyJsPlugin()
        ]
    }
};

Operating System, Node, and NPM dependency versions
Mac OS 10.13.5
Node 10.4.1

"dependencies": {
    "clean-webpack-plugin": "^0.1.19",
    "css-loader": "^0.28.11",
    "exports-loader": "^0.7.0",
    "expose-loader": "^0.7.5",
    "file-loader": "1.1.11",
    "hard-source-webpack-plugin": "0.9.0",
    "html-webpack-plugin": "^3.2.0",
    "imports-loader": "^0.8.0",
    "inline-manifest-webpack-plugin": "^4.0.0",
    "less": "2.6.1",
    "less-loader": "4.1.0",
    "null-loader": "0.1.1",
    "raw-loader": "0.5.1",
    "style-loader": "^0.21.0",
    "svgo": "1.0.5",
    "svgo-loader": "2.1.0",
    "uglifyjs-webpack-plugin": "^1.2.5",
    "webpack": "4.12.0",
    "webpack-bundle-analyzer": "^2.13.1",
    "webpack-cli": "^3.0.8"
    "eslint": "4.19.1",
    "eslint-loader": "2.0.0",
    "unused-files-webpack-plugin": "3.4.0",
}

@rmunch thank you for opening this issue. How are you determining that the work isn't cached? hard-source currently caches modules before they are uglified. Since their uglification depends on the rest of their container chunk their uglified state cannot be cached by hard-source. Are the pre-uglified modules not being cached? A simple test would be to see if the node_modules/.cache/hard-source grew in size.
My understanding is this later work is cached by UglifyJsPlugin and is done at a chunk level. Rebuilt chunks due to changes in modules need to re-uglified. Maybe there are configurations that UglifyJsPlugin cannot cache.

@mzgoddard everything appears to be cached up until the UglifyJsPlugin runs (and then source maps). Based on your explanation, it sounds like this issue is out of the scope of this plugin and depends on the UglifyJsPlugin's cache settings, so I'll go ahead and close this ticket.
Thank you for this great plugin!


please review my Website

https://github.com/gaushikmr
http://gaushik.netlify.app

Looks pretty neat!
On your landing page as a User I feel like I should be able to click on 'Web Designer", "App Developer", "Machine Learning Enthusiast" and be sent to your projects.
Do you have a link to the source code?

@AllanRegush nop i dont have any so i mentioned

@AllanRegush soon i will link

animations are good but this looks overly animated work improving the readability so that the visitor doesn't have to do much hard work while going through your site.


WoW Retail 10.0.2

Hey !
Is there an update planned for 10.0.2 ?

Sorry for the delay, I'll have it updated by this week

I just made a new pull request containing tracking for all new and returning dungeons as well. That should be good to go for the release of the expansion.