Change dimensions of login window

This commit sets a more appropriate size for the login window (548 wide by 780 high).

@hughlilly is there an issue associated with this? why change it?

It’s just not the right size for the content, IMHO. Currently it looks like this (800x600):

Here is 548x736:

I think it looks a lot better.


Is it currently possible to have the Object Name field be autogenerated based on the title [question]

First off, this is package is awesome!
When a user creates a field, they have to fill out the object name for the backend. Is it possible for this to be disabled, and I just write code to generate the object name from the display name field?
so if the user is puts in the display name field: "Date Account Recovered", I could write something that strips out the spaces so the object name would be generated as "dateaccountrecovered" (or something like that).
Is there a way to do this currently?
Thanks for your help!

I don't believe this is currently possible, but we welcome PRs!
Probably have to make some changes in this file, among others.


Feature/push/setup dapp engine

It's hard to read it as it has current changes from develop as well. Before review we should either update setup_push branch or revert merge branch commit


Newline character (\n) in tagged template literals becomes "n"

From the comment here: https://github.com/chalk/chalk/issues/12#issuecomment-315685346

When using tagged template literals, \n does not work => n is output and there is no line break.

I just ran into this myself, so I figured I'd do as @Qix- asked.

It looks like part of your processing is eating the \. Multi-line template literals (or anything similar in other languages) always seem like a cool idea until you have code like this...
function run() {
	if (something) {
		if (somethingElse) {
			console.log(`this is the first line
			this is the second`);
		}
	}
}

...producing the output...
this is the first line
			this is the second

...which isn't optimal. You could pull the second line all the way to the margin, but that'd never fly with formatters or linters.
Maybe there's a better way for chalk to detect character escapes (certain character escapes) and not eat them?
As a workaround, it is possible to do something like this, though it's not very attractive:
console.log(chalk`{red NO} but...${'\n'}really, {green YES}`);

I know exactly why this happens and I agree it's not optimal.
@sindresorhus thoughts about this? I can fix it but I'm worried about how we'd release.

Interestingly, while using your library even more (the first good use of tagged template literals I've ever seen -- so slick and clean :+1:), I found out some more constraints for that workaround:
If a color block precedes it, it works:
> console.log(chalk`testing {blue hi}${'\n'}there`)
testing hi
there

If a color block follows it, it eats the \n:
> console.log(chalk`testing hi${'\n'}{blue there}`)
testing hithere

Probably doesn't matter if you know how you think you'd like to change it; but, I thought I'd mention it anyway.

thoughts about this? I can fix it but I'm worried about how we'd release.

It would be a patch release, it's a bug fix.

Hey guys. Just contributing what I can:

This converts to:

As you can see it strips out the newline character. I verified it goes into the function and is stripped out when it returns. Is there any way I can help?

const a = '\\'
chalk`{blue ${a}}`

Chalk will crash in this case.


Checking return code on commands

After each command in bash, the return code can be tested with $?. A command can also run dependent on another command succeeding with &&. This would be particularly useful if, as in the below screenshot, a directory wasn't created, and all the subsequent processes failed.

Yeah I use $? in some instances but not here. It shouldn't really fail in this area. However I had made some changes that I think I have now fixed. Hopefully so the issue should no longer be there


[RIP-7] Support multi-directory storage in DLedger.

FEATURE REQUEST

Please describe the feature you are requesting.
Multi-directory storage has been supported in 4.9.2, but it only supports master-slave deployment mode. We should also support this feature in DLedger deployment mode.

Provide any additional detail on your proposed use case for this feature.
Refer to this pr https://github.com/apache/rocketmq/pull/3357 to implement it.

Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?
Should-have.

If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:

[x] Task-1: Make DLedger support mult-directory storage.
[x] Task-2: Upgrade DLedger dependencies and adapt it. https://github.com/apache/rocketmq/pull/4122

We can combine this feature with RIP-31, because if a server has 12 disks, it is impossible for us to deploy 12 brokers. We can use this feature to allocate a few disks to each broker, so that each node of a group can be utilized and It can also ensure that a broker has enough space to use.

This motivation LGTM.

Merged


Readme 2.0.0 rc2

Codecov Report

Merging #553 into master will decrease coverage by 20.63%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             master     #553       +/-   ##
=============================================
- Coverage     84.98%   64.35%   -20.64%
+ Complexity     1546     1005      -541
=============================================
  Files           103      103
  Lines          4634     4634
  Branches        693      693
=============================================
- Hits           3938     2982      -956
- Misses          480     1287      +807
- Partials        216      365      +149

Flag
Coverage Δ
Complexity Δ

#fixedclientenvironment
27.42% <ø> (ø)
463 <ø> (ø)
:arrow_down:

#integration
57.74% <ø> (-0.05%)
895 <ø> (-2)

#livelocal
?
?

#unit
?
?

Impacted Files
Coverage Δ
Complexity Δ

...nter/xenon/filesystems/CopyCancelledException.java
0% <0%> (-100%)
0% <0%> (-1%)

...xenon/adaptors/filesystems/EndOfFileException.java
0% <0%> (-100%)
0% <0%> (-2%)

...non/schedulers/InvalidJobDescriptionException.java
0% <0%> (-100%)
0% <0%> (-2%)

.../adaptors/filesystems/ConnectionLostException.java
0% <0%> (-100%)
0% <0%> (-2%)

...enon/filesystems/InvalidResumeTargetException.java
0% <0%> (-100%)
0% <0%> (-2%)

...r/xenon/filesystems/FileSystemClosedException.java
0% <0%> (-100%)
0% <0%> (-2%)

...ptors/schedulers/IncompatibleVersionException.java
0% <0%> (-100%)
0% <0%> (-2%)

...esciencecenter/xenon/InvalidPropertyException.java
0% <0%> (-100%)
0% <0%> (-2%)

...ter/xenon/filesystems/InvalidOptionsException.java
0% <0%> (-100%)
0% <0%> (-2%)

...nl/esciencecenter/xenon/XenonRuntimeException.java
0% <0%> (-100%)
0% <0%> (-4%)

... and 65 more

Continue to review full report at Codecov.

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

Replace download badge with one from jitpack :
[![](https://jitpack.io/v/NLeSC/Xenon.svg)](https://jitpack.io/#NLeSC/Xenon)

Add steps to Xenon into a gradle build. Now you have to follow gitpack link to get instructions, I want to copy paste something from README directly.

Remove ./gradlew installDist command dont see users of Xenon library do this.

Replace print any exceptions example with
XenonException copyException = copyStatus.getException();
if (copyException != null)  {
  throw copyException;
}


[Python] Fix documentation linking to protos

What:
Fix text in first page of documentation to say something like "The .proto files used to create this client library are available on [github]".
Why:
The current text "defined in the [googleapis] git repository" is unclear.

@lukesneeringer Is this still relevant?

If this is still an issue I'd assert this will be a 'will not fix' in lieu of solving this in gapic-generator-python. @lukesneeringer if you disagree, please reopen.


Default Value does not match documentation - default is $(Agent.TempDirectory)

we are seeing the default value use the temp directory:
yaml:
- task: UseDotNet@2
      inputs:
        packageType: 'sdk'
        version: '3.0.x'

logs:
Found version 3.0.103 in channel 3.0 for user specified version spec: 3.0.x
Version 3.0.103 was not found in cache.
Getting URL to download .NET Core sdk version: 3.0.103.
Detecting OS platform to find correct download package for the OS.
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoLogo -Sta -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command "& 'E:\B\Agent1\_work\_tasks\UseDotNet_b0ce7256-7898-45d3-9cb5-176b752bfea6\2.165.0\externals\get-os-platform.ps1'"
Primary:win-x64
Detected platform (Primary): win-x64
Downloading: https://download.visualstudio.microsoft.com/download/pr/874a85a8-de9b-405d-b75e-9c3e9b3ddd0d/eb5f33724a7ba55d47fd12b2f1f8f764/dotnet-sdk-3.0.103-win-x64.zip
Extracting downloaded package E:\B\Agent1\_work\_temp\4c61ab91-723e-48d7-9de2-a6b4d6f17efc.

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

ID: f9660c58-3366-f1be-8380-d6cf1d3c0150
Version Independent ID: 226a4fd8-bce8-3333-d8d6-7af933c7b060
Content: Use .NET Core task - Azure Pipelines
Content Source: docs/pipelines/tasks/tool/dotnet-core-tool-installer.md
Product: devops
Technology: devops-cicd-tasks
GitHub Login: @pulkitaggarwl
Microsoft Alias: puagarw

I think this should be fixed. It could cause the next person who runs into this not waste 2 hours.

@steved0x should this be assigned to someone else?


how do I install the artifact-credprovider in a windows docker image

I am trying to utilize this inside a docker multi-stage build to get the cred provider to read my Azure DevOps NuGet feed.. however the sample docker file doesn't seem to work:
'wget' is not recognized as an internal or external command,
operable program or batch file.
The command 'cmd /S /C wget -qO- https://raw.githubusercontent.com/Microsoft/artifacts-credprovider/master/helpers/installcredprovider.sh | bash' returned a non-zero code: 255
##[error]C:\Program Files\Docker\docker.exe failed with return code: 255
If I attempt to use the sample found in the dotnet docker here (which uses curl instead of wget):
https://github.com/dotnet/dotnet-docker/blob/master/samples/snippets/nuget-credentials.md#using-the-azure-artifact-credential-provider
I get an error about bash not being a known command.. so.. I'm looking to find a way to utilize this inside my dockerfile successfully.

This is untested, but something like the following should get you there;
ADD https://raw.githubusercontent.com/microsoft/artifacts-credprovider/master/helpers/installcredprovider.ps1
RUN powershell .\installcredprovider.ps1 -AddNetfx

You can have a look at #148 . Seems like you should be able to use something like this:
RUN Invoke-WebRequest 'https://raw.githubusercontent.com/microsoft/artifacts-credprovider/master/helpers/installcredprovider.ps1' -OutFile installcredprovider.ps1; RUN .\installcredprovider.ps1 -Force  RUN Remove-Item .\installcredprovider.ps1;

I was able to get it working using curl and pwsh (I'm using dotnet/core/sdk:3.1 as my base image)
RUN curl https://raw.githubusercontent.com/Microsoft/artifacts-credprovider/master/helpers/installcredprovider.ps1 | pwsh

Hey @jeffpriz - are you still blocked here?

Closing this, pls reopen if needed.


Remove "http://" from --beacon-rpc-provider flag

Pull request for #86
Removed http:// from --beacon-rpc-provider http://<your address>:5053

Ah good catch - thank you for the fix!


KAFKA-16609: Update parse_describe_topic to support new topic describe output

The format of the 'describe topic' output was changed as part of KAFKA-15585 which required an update in the parsing logic used by system tests.
Committer Checklist (excluded from commit message)

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

@lucasbru—would you mind taking a look at this change? Thanks!


Implement the post processing mechanism.

Goal

Implement the post processing mechanism.

OK.
It have been implemented.


Remove trailing ")" from URL in readme

Fixing the link not working in the English readme

Thanks.

Thanks.


Provide Docker images for easier setup

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
I should be able to run the Toolpad editor, run the builds, and run Toolpad apps with Docker. I shouldn't be required to have Node.js installed on my system to use Toolpad.
Benchmarks

https://docs.tooljet.com/docs/setup/try-tooljet/

Hello I would like to try to do this. Can I go ahead? @Janpot @prakhargupta1

@IgnisDa Thanks for your interest. Which solution did you have in mind. I'm not sure whether at this point offering official images would be worth the maintenance overhead. As far as I can see, even if we offered official images, you'd still have to build your own on top if you want to deploy on Docker.
Such image would likely not comprise of more as a wrapper to our CLI on a standard node.js image. Perhaps it makes more sense to offer an example of a simple application + Dockerfile + docker-compose.yml file. What's your idea on this?


Create map only if it is required

Codecov Report

Merging #581 (93298d8) into main (c24a4c6) will increase coverage by 0.06%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##               main     #581      +/-   ##
============================================
+ Coverage     92.50%   92.56%   +0.06%
- Complexity     2441     2444       +3
============================================
  Files           253      253
  Lines          5110     5114       +4
  Branches        560      562       +2
============================================
+ Hits           4727     4734       +7
+ Misses          249      244       -5
- Partials        134      136       +2

Impacted Files
Coverage Δ

...n/java/net/datafaker/providers/base/BaseFaker.java
94.04% <100.00%> (+0.14%)
:arrow_up:

...rc/main/java/net/datafaker/service/FakeValues.java
83.03% <100.00%> (+0.30%)
:arrow_up:

.../main/java/net/datafaker/service/FakerContext.java
92.30% <0.00%> (+2.56%)
:arrow_up:

...ker/idnumbers/pt/br/IdNumberGeneratorPtBrUtil.java
96.29% <0.00%> (+3.70%)
:arrow_up:

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


[Bug] Single "count" aggregation fails

Bug report
If I have a single "count" aggregation:
type Block @entity(timeseries: true) {
  id: Int8!
  timestamp: Timestamp!
  hash: Bytes!
  number: Int!
}

type Stats @aggregation(intervals: ["hour", "day"], source: "Block") {
  id: Int8!
  timestamp: Timestamp!

  count: Int! @aggregate(fn: "count")
}

graph-node fails with invalid SQL expression error:
postgres-defi    | 2024-09-07 20:45:32.788 UTC [91] ERROR:  syntax error at or near "from" at character 205
postgres-defi    | 2024-09-07 20:45:32.788 UTC [91] STATEMENT:  insert into "sgd1"."stats_hour"(id, timestamp, block$, "count") select max(id) as id, timestamp, $3, count(*) as "count" from (select id, date_bin('3600s', timestamp, 'epoch'::timestamptz) as timestamp,  from "sgd1"."block" where "sgd1"."block".timestamp >= $1 and "sgd1"."block".timestamp < $2 order by "sgd1"."block".timestamp) data group by timestamp

Note "," before "from" that shouldn't be there.
Subgraph example: https://github.com/YaroShkvorets/common-subgraphs/tree/main/aggregation-broken
Relevant log output
No response
IPFS hash
No response
Subgraph name or link to explorer
No response
Some information to help us out

[ ] Tick this box if this bug is caused by a regression found in the latest release.
[ ] Tick this box if this bug is specific to the hosted service.
[X] I have searched the issue tracker to make sure this issue is not a duplicate.

OS information
None

PR: https://github.com/graphprotocol/graph-node/pull/5639


Rename description to describe

[X] Breaking change

Fixes a bug when description is never called resulting in a thrown error when running introspection queries. Because description is never called the scalar object type never overwrites the description property with the string value. To avoid this conflict, we can just rename description to describe` and resolution will therefore not try to use the default function. This is the unexpected error that you would have to dig into this module in order to diagnose:
    at StringScalar.create (node_modules/graphql-scalar-types/lib/base.js:85:19)
    at StringScalar.create (node_modules/graphql-scalar-types/lib/string.js:303:118)

As soon as I started calling .description it went away. Rather than try to detect if it was called, I decided to rename the function for simplicity sake. I like that it kinda fits in to the API with .create verbage.
Cheers!

@li-kai could I get a review here? :)


Remove or parametrize check-db timeout

Checks

[X] I have checked for existing issues.
[X] This report is about the User-Community Airflow Helm Chart.

Motivation
In our company we are currently setting up a cluster for airflow, and while debugging some networking issues between our cluster and rds we seem to constantly hit the timeout settings in here https://github.com/airflow-helm/charts/blob/main/charts/airflow/templates/_helpers/pods.tpl#L72-L75 , which once hit hides all of the important logs that we would have received if the process failed on it's on.
The way we handle it right now is by manually editing the container's command and setting the timeout to something higher.
Implementation
Here are some different ideas:

Include a variable under airflow.check-db that would allow us to set a custom timeout
Remove the timeout completely, since this should be handled internally by airflow with the CONNECTION_CHECK_SLEEP_TIME and CONNECTION_CHECK_MAX_COUNT variables (see https://airflow.apache.org/docs/docker-stack/entrypoint.html#waits-for-airflow-db-connection )  -- I prefer this solution

Are you willing & able to help?

[X] I am able to submit a PR!
[X] I can help test the feature!

We can pick the timeout value from values.yaml by using something like .Values.checkDb.timeout and add if else condition to use default timeout value?

@asosnovsky-sumologic @anuragphadnis
Thanks for raising this, I am not sure why I did not introduce a value to change the timeout length when I first introduced the timeout.
However, I do remember that there are situations when airflow checkdb and airflow db check will hang forever  without actually failing (like in your described situation of network issues, https://github.com/airflow-helm/charts/issues/153), so you probably would not see network logs if you remove the timeout anyway.
While you are correct that the airflow Dockerfile has an in-built check-db, this is not suitable for the chart for 2 primary reasons:

We want a separate init-container to perform the check-db (so that the main container does not even try and start if the db is down)
Older versions of the Dockerfile (like those for 1.10) do not have the check-db feature

My thought is that we can do two things:

Introduce a value like airflow.dbCheckTimeout (probably setting this to 0 disables the timeout).
Check if we get more logs when we lower the main signal to SIGINT, and introduce a KILL signal at a slightly later timeout to ensure the process ends:

The command might look something like: timeout --signal=INT --kill-after=5s 60s airflow checkdb
NOTE: I am not sure if SIGINT will actually terminate airflow db check, or if it will even give better logging (in network failure situations), we need to verify this, otherwise this change is not neeeded

Other thoughts:

60s is an incredibly long time for a timeout that literally just connects to a DB, if a connection takes more time than that, its very likely your DB is not functional
60s is the timeout for a single connection attempt, Kubernetes will retry the container (with exponential backoff) so its not like its 60s and then a permanent failure

In my case the check-db pod gets restarted after every 60 seconds and connection is not being able to establish in this time. This happens every time after check-db is restarted, and check-db does not log anything. It would be very useful if we can customize the value so that we can see logs or establish the connection.

@anuragphadnis
I agree with this line of thinking.
In my case I had a networking issue that restricted the db from being reachable by my cluster. The issue was hard to capture because when you do the math with CONNECTION_CHECK_SLEEP_TIME and CONNECTION_CHECK_MAX_COUNT no errors actually got thrown as it just silently kept on retrying. I actually think that the timeout should possibly be set as a dynamic value based on these two environment params?
Like do something along the lines of
{{- if .Values.airflow.legacyCommands }}
- "exec timeout {{mul .Values.config.CONNECTION_CHECK_SLEEP_TIME .Values.config.CONNECTION_CHECK_MAX_COUNT}}s airflow checkdb"
{{- else }}
- "exec timeout {{mul .Values.config.CONNECTION_CHECK_SLEEP_TIME .Values.config.CONNECTION_CHECK_MAX_COUNT}}s airflow db check"
{{- end }}

Or even provide these values under
# value.yaml
airflow:
 db_connection:
  check_max_count: 10
  check_sleep_time: 30

Yes, right now I have modified it to use value from config by changing the code and using that code to deploy the chart. I can create a PR if someone else is not working on it.

@anuragphadnis
I agree with this line of thinking. In my case I had a networking issue that restricted the db from being reachable by my cluster. The issue was hard to capture because when you do the math with CONNECTION_CHECK_SLEEP_TIME and CONNECTION_CHECK_MAX_COUNT no errors actually got thrown as it just silently kept on retrying. I actually think that the timeout should possibly be set as a dynamic value based on these two environment params?
Like do something along the lines of
{{- if .Values.airflow.legacyCommands }}
- "exec timeout {{mul .Values.config.CONNECTION_CHECK_SLEEP_TIME .Values.config.CONNECTION_CHECK_MAX_COUNT}}s airflow checkdb"
{{- else }}
- "exec timeout {{mul .Values.config.CONNECTION_CHECK_SLEEP_TIME .Values.config.CONNECTION_CHECK_MAX_COUNT}}s airflow db check"
{{- end }}

Or even provide these values under
# value.yaml
airflow:
 db_connection:
  check_max_count: 10
  check_sleep_time: 30

@anuragphadnis i don't mind taking this to completion. If your change is already merged, I can do the rest of the work and update the checkdb command :)

@asosnovsky @anuragphadnis @asosnovsky-sumologic
If anyone wants to pick up the tasks I suggested in https://github.com/airflow-helm/charts/issues/615#issuecomment-1220050680, I am happy to review/merge the PR, the tasks are:

Introduce a value like airflow.dbCheckTimeout (probably setting this to 0 disables the timeout).
Find a way to actually get logs when a timeout is hit (so people know what is happening):

We might be able to do this by lowering the main signal to SIGINT, and introducing a KILL signal at a slightly later timeout to ensure the process ends:

The command might look something like: timeout --signal=INT --kill-after=5s 60s airflow checkdb
NOTE: I am not sure if SIGINT will actually terminate airflow db check, we need to verify this


Improve unsubscription

This is to prevent the usual Warning

Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application.

Summary
I had a memory leak warning with the previous code, and opened a StackOverflow question to solve it.
I ended doing my own hook based on this code to solve the warning.

Compatibility

OS
Implemented

iOS
✅

Android
✅

Checklist

[x] I have tested this on a device and a simulator
[ ] I added the documentation in README.md
[ ] I mentioned this change in CHANGELOG.md
[ ] I updated the typed files (TS and Flow)
[ ] I added a sample use of the API in the example project (example/App.js)

Is this still something that needs fixing?

:rocket: PR was released in v2.4.4 :rocket:


Postgres : Wrong Information on Index section

System information:

Operating system (distribution) and version : OSX Mohave
DBeaver version : Version: <IP_ADDRESS>902031804
Java version : 1.8.0_192
Additional extensions

Connection specification:

Database name and version : Postgres 9.6
Driver name
Do you use tunnels or proxies (SSH, SOCKS, etc)?  NO

Describe the problem you're observing:
With recent feature https://github.com/dbeaver/dbeaver/issues/4605 Index Scans and its size were added into the index section page. But it seems it is not showing the correct information.
Steps to reproduce, if exist:
Check the image below. I have 3 different indexes with different columns but num scans and rel-size shows the same numbers and numbers are incorrect too.
Include any warning/errors/backtraces from the logs

Thanks for the bug report (it was table rel size, not index)


MessageJournal (not storage) and related changes

@AlexanderLitus, have a look at this pull request too. It already has compatibility fix for EngineShould test.


Question: is there a post/article with the best practices for build performance?

I'm trying to improve the performance of my Unity build.
And while I see some suggestions (like LFS caching) for the checkout step, I couldn't find a best practice article for the build step itself (besides library caching). Any suggestions?
Thank you,
Vitaly

I'm not aware of any good articles with regards to build performance.
The only suggestion I can make is to join our discord and ask there: http://game.ci/discord

At the moment we do not have a step-by-step guide for this, but next to asking questions on discord, I would also recommend having a look at this example workflow in our documentation.

At the moment we do not have a step-by-step guide for this, but next to asking questions on discord, I would also recommend having a look at this example workflow in our documentation.

Thank you!
I tried to use LFS caching, based on this and other examples, but my build failed. I suspect it's related to the fact that my project uses submodules, and submodules use LFS as well.
But unfortunately, I couldn't fix that so far.

You might wanna check out the sub-modules as well during or right after the initial checkout step.
Then for each submodule you'll have to:

git lfs install
git lfs pull and
apply the caching strategy that you mentioned. (might still work with the actions/cache action)

That sounds like a pretty enterprise level use-case though.
Unfortunately we'll likely not start documenting such complicated flows however, as in the end it's hard to cover all specifics for all users. I'd like to believe that teams that choose to use a complex workflow like this have a good reason for it (as it's expensive) and will have people that can manage with this added complexity.

Closing this issue, as the question has been answered as much as it can be for now.


RequestDispatcher cannot handle high concurrency load

Aditya ran perf micro-benchmarks and saw a huge decrease in performance when adding delays to the RequestHandler ( substituting delays for 'real work' ).
I removed the logic to run RequestHandler#handle calls on an executor because I was seeing what I thought were race conditions with the Request/Response dispatchers. I can add back the logic, or come up with a better strategy for running handlers. Either way, I need to handle this because we cannot ship with this performance.

@truncs fixed with #73 ?


Fix run in check mode and update changelog

Closes #22
Same as #19 , but with changelog entry
Requirements
none
Description of the Change
Add check_mode directives to fix running role in check mode
Benefits
It is now possible to run the role in ansible check mode
Possible Drawbacks
none
Applicable Issues
none

Hi @xshadow ! looks good to me, but please remember to change the dest branch from master to develop :)


Update ember-cli

@homu r+

:pushpin: Commit f99c3b8 has been approved by poteto

:zap: Test exempted - status


Install rvm as the vagrant user

RVM recommends an isolated install within a user's home directory:
https://rvm.io/rvm/install#installation-explained

Hey, Sam.
Thanks for the fix. You can merge in whenever you're happy :rocket:
Can't even believe you're into ruby now. I hope you're proud of yourself :see_no_evil:

Just tested out your changes too and jeeeez RVM takes a while to sort itself out.

Can't even believe you're into ruby now. I hope you're proud of yourself :see_no_evil:

Just a bit  of Jekyll and dokku fun I promise :smile:.

Just tested out your changes too and jeeeez RVM takes a while to sort itself out.

Yop :sob:. Tonight's eventual result: http://blog-sam.platform.mainthread.technology/


The mp4 test is not run since it depends on a feature that doesn't exist

While looking for what Custom ErrorKind became, I saw that there were still some references to it in the code. One of those is the tests/mp4.rs which depends on the stream feature which doesn't exist.

mp4 test compilation was fixed in 0efdfac


1366: Review TA permissions on GBNG entity provider

Delivers #1366.  Assumed my assertions weren't crazy and went ahead with it :fearful:
Three changes:

introduce checkInstructorOrTA so TAs can view edits of other users
disable drag and drop for TAs and leave sort-order update endpoints as instructor-only
remove the assignemnts list endpoint

Thanks @steveswinsburg.  I've updated the SecurityException wording in checkInstructorOrTA.


fix seq2seq example not working with GPU

As @lboloni pointed out, it does not work in GPU mode.
https://github.com/chainer/chainer/pull/4087#commitcomment-26328157

LGTM! Sorry, this should not have gotten away in the first place.


Unable to set Content-Type for request

Hello,
I'm unable to set Content-Type for request as this HTTP header is added to the request instead of replaced. See code bellow:
/** @var DriveItem $driveItem */
$driveItem = $graph->createRequest('PUT', '/drives/<drive identifier>/root/children/test.pdf/content')
	->attachBody($fileContent)
	->addHeaders(['Content-Type' => 'application/pdf'])
	->setReturnType(DriveItem::class)
	->execute();

This used to work, but from couple days ago the Graph API started returning: HTTP Error 400. The request has an invalid header name. So I dug into the request and found out, that Graph API sends actually two Content-Type headers (one default of application/json and second one the one I set manually in the code: application/pdf).

I was unable to replace Content-Type header instead of appending it to the request. Could you, please, add the feature to replace (or remove) already set header?
Thank you

Thanks for pointing this out @hubipe. Have a fix pending review & hopefully release this week.
Also, thanks for using our 2.0-preview!

@hubipe the latest Release Candidate contains this fix (https://github.com/microsoftgraph/msgraph-sdk-php/releases/tag/2.0.0-RC4)


simulating failure

Signed-off-by: Madhu Rajanna<EMAIL_ADDRESS>

/retest ci/circleci: build

@github.User{Login:"Madhu-1", ID:18114231, NodeID:"MDQ6VXNlcjE4MTE0MjMx", AvatarURL:"https://avatars.githubusercontent.com/u/18114231?v=4", HTMLURL:"https://github.com/Madhu-1", GravatarID:"", Type:"User", SiteAdmin:false, URL:"https://api.github.com/users/Madhu-1", EventsURL:"https://api.github.com/users/Madhu-1/events{/privacy}", FollowingURL:"https://api.github.com/users/Madhu-1/following{/other_user}", FollowersURL:"https://api.github.com/users/Madhu-1/followers", GistsURL:"https://api.github.com/users/Madhu-1/gists{/gist_id}", OrganizationsURL:"https://api.github.com/users/Madhu-1/orgs", ReceivedEventsURL:"https://api.github.com/users/Madhu-1/received_events", ReposURL:"https://api.github.com/users/Madhu-1/repos", StarredURL:"https://api.github.com/users/Madhu-1/starred{/owner}{/repo}", SubscriptionsURL:"https://api.github.com/users/Madhu-1/subscriptions"} ci/circleci: build test failed. Logs are available at https://circleci.com/gh/Madhu-1/retest-action/4?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link for debugging

@ ci/circleci: build test failed. Logs are available at https://circleci.com/gh/Madhu-1/retest-action/4?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link for debugging

/retest ci/circleci: build

/retest ci/circleci: build

@Madhu-1 ci/circleci: build test failed. Logs are available at https://circleci.com/gh/Madhu-1/retest-action/4?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link for debugging


Adding different plotting units for the x axis

Allow a selection of eV, MeV, GeV on a scroll bar
this will have to be an input to the plotter

solved in #15


Tagging Events in Data Prepper

Is your feature request related to a problem? Please describe.
Currently, Data Prepper does not support a standard concept for adding descriptions dynamically for what happens in individual sources, processors, and sinks. For example, if the grok processor fails to match, the user should be able to look at an Event and tell that it was not able to match. Otherwise, it can feel like grok is simply not working at all. Another example would be a json processor failing to parse json. The user needs to know if the parsing failed in order to pinpoint the problems with their configuration. Additionally, many users would like to check for certain tags when routing, or drop Events with those tags to save space. Lastly, users of OpenSearch would like to query based on tags in Events. Data Prepper needs a concept for easily handling these types of situations for any sink, processor, or source.
Describe the solution you'd like
A key that is dedicated to adding information of this sort. For example, if grok fails to match, then the event will add a tags key with [grok_match_failure] as a value. The value of tags will be a Set, as it is not helpful to have duplicate tags.
{ "message": "a log", "tags": ["grok_match_failure"] }

Now a grok user is able to quickly tell that there was no match for this Event. If this Event then went through a json parser and failed to parse, you can add json_parse_failure to the tags key, like this.
{ "message": "a log", "tags": ["grok_match_failure", "json_parse_failure"] }

To make this functionality consistent between plugins, the Event class could have a new function
void addTag(String tagName);

which would add tagName to the set of tags.
In order to separate tags from the rest of the Event, checking for tags with conditional expressions would look like this:
drop:
     when: 'event.hasTag("grok_parse_failure")'

While I don't believe it to be required for the first iteration of tagging, a processor to control the adding and removing of custom tags could exist.  It would look something like this:
processor:
     - tag_manager:
          add_tags: ["tag3", "tag4"]
          remove_tags: ["tag1", "tag2"]

This processor could also be split into two, with one called add_tags and one called remove_tags.
Describe alternatives you've considered (Optional)
This problem could be solved at the plugin level. So given the same scenario with grok match failure, the Event would become something like
{ "message": "a log", "grok_match_failure": true }

and then after the json parsing fails, the Event would become something like
{ "message": "a log", "grok_match_failure": true, "json_parse_failure": true }

As you can tell, this solution doesn't scale as well. You can imagine that with a large amount of sources, processors, and sinks adding their own booleans to an Event, the Event could quickly become cluttered, and the querying for tags in OpenSearch would also become more of a pain.
Add the tags to the EventMetadata
Additionally, the tags could be added to the EventMetadata rather than the actual Event. This would make the Events cleaner, and the overall tagging options more configurable and extracted from the event data itself. The EventMetadata would contain the following:
Set<String> getTags();

This approach would allow for conditional checks on tags, but it needs a little more implementation to make the tags a part of the sink output. For example, the OpenSearch sink could have a configuration option like the following:
opensearch:
  host: ["localhost:9200"]
  save_tags: false (default would be true)

This would give individual sinks the ability to configure tags however they please (they could change the name of the tags key or remove certain tags at the sink level)
The one concern with this is that it would result in some unnecessary duplicate code, but it is entirely likely that some sinks would like to have the tags in the Event itself, and some would not. To make some options like the save_tags logic reusable, a plugin could be created that would handle the logic for adding the tags from the EventMetadata to the Event itself before it is shipped to the sink.
Additional context
Please provide alternatives to solve this problem if there are other ideas that make more sense than the tagging concept described here.

Thanks for proposal. Yes, this would be helpful.
Regarding the idea of using an array, I believe this is also best for OpenSearch documents. It should be easier to query documents by querying matches on tag than doing a boolean match.
I think it would be appropriate to make this a concept directly on Event. This should promote consistency across plugins.
Perhaps the following method can be added to Event:
void addTag(String tagName);

A few questions I have:

Should the tags field be a protected field in the event? Can rename_key, 'copy_key', 'delete_key', etc. alter the tags?
What happens if an event contains a tags that is not a set?

@cmanning09 After thinking about your comments for a while, I think I am more in favor of tags being a part of the EventMetadata, and then creating a plugin that can be used by all sinks to handle tagging. This way, all the functionality of choosing the tag name and whether they are sent to the sink as part of the Event is configurable, and it can be made very clear that mutate processors cannot be configured by the user to directly alter the tags. This approach also makes the conditional expressions based on tags less confusing, as it would be more apparent that /tags or hasKey("tags") would actually check the Event for a literal "tags" key, while getTags() == { "grok_match_failure", "json_parse_failure" }  or hasTag("grok_match_failure") would only check the tags in the EventMetadata. The full plugin would look something like this by default
- opensearch:
     tagging:
        include_tags_in_event: false
        tags_key_name: "tags"

And this configuration would not include the tags as part of the Event sent to the OpenSearch sink.
and this same plugin could be utilized by, for example, by an s3 sink as well (in this case it is sending the tags to the sink as part of the Event under the newTagsKey key.
- s3:
     tagging:
        include_tags_in_event: true
        tags_key_name: "newTagsKey"

This way, tags are completely decoupled from the Event until right before they are sent to the sink, and could be serialized into the Event with a separate method such as event.toJsonStringWithTags("newTagsKey") for the sinks to use if include_tags_in_event is true and tag_key_name is newTagsKey. Even if the user had a tags Integer in the Event already and still used the default of tags for tag_key_name (which they should know not to do), nothing would collide and cause errors or data overwriting, and there would just be 2 different json keys for tags. This also provides some interesting query functionality in OpenSearch for the case of multiple sinks that use the same OpenSearch cluster with the same index, as one would still be able to figure out which path an Event took quickly by querying on the assigned tag key.

@dlvenable it depends on what this issue includes. We have to add support to add tags at many places. Not sure if this issue is supposed to be for all those cases.

I think the processor also should have a support for condition optionally. So, the processor config should look something likes
processor:
   - tag_manager:
          add_tags: ["tag3", "tag4"]
          add_when: <condition1>
          remove_tags: ["tag1", "tag2"]
          remove_when: <condition2>

@kkondaka , I think the only item left here is to include tags in the documents for OpenSearch.
If we don't get this in for 2.3, can you create a new GitHub issue for this addition?

The feature for writing tags to OpenSearch documents was not included in this version and will be worked as part of #2827.


Update README.md to include acknowledgements

Fixes #219

Should probably also include:
Funding: D-PLACE was developed with generous support from the National Evolutionary Synthesis Center (www.nescent.org), the Max Planck Institute for the Science of Human History (http://www.shh. mpg.de/en), and the National Science Foundation (award numbers 1519987, BCS-1423711, and EF- 0905606).

...and this from the paper:
D-PLACE would not exist without the cultural datasets upon which it relies; we would like to acknowledge the years of work by George P. Murdock and Lewis R. Binford, and the enormous contributions made by other scholars in the field towards their maintenance and updating. Robert Colwell, Karen Cranston, Michael Dunn, Robert Dunn, Robert Forkel, Harald Ham- marström, Amber Johnson and Carl Simon provided valuable insights into the data or struc- ture of D-PLACE.
Finally, a number of people provided assistance in preparing data for inclusion in D-PLACE, including Christopher Blackford, Kaylin Clements, Anna Kellogg, Hannah Haynie, Patrick Kavanagh, Ameena Khan, Beata Opalinska, Anum Rafiq, Anastasia Stellato, and George Tsourounis.

added the extra info here https://github.com/D-PLACE/dplace-data/commit/653f539ef5b2b029bf29d8b1b74ed4b5db05b647


ARROW-13097: [C++] Provide simple reflection utility

Provides nameof<T>() which yields a string representation of the name of T, as well as reflection for simple structs, allowing generic get/set/nameof each member

Argh: membername is broken for MSVC https://ci.appveyor.com/project/ApacheSoftwareFoundation/arrow/builds/39649979/job/undvcpp9ynmsib1o#L902


rename value in the input files

proposed changes:

simulator.scheme -> simulator.integrator

Also for the input file spec:
Mjolnir allows to split an input file to several toml files to avoid too long input file. Currently, adding table name to the splitted input file is discouraged.
# input.toml
[[systems]]
file_name = "system1.toml"

The above input file requires a toml file like the following.
# system1.toml
# [system] <- currently discouraged because
#             it is already clear that
#             this file is dedicated to a system.
particles = [
# ...
]

But now I think it is better to have a tabl in the splitted input files to show explicitly what does the file define. Of course one can guess what is defined in the file because each table requires different values, but it takes time to understand what is the content (and also requires knowledge about the input file). With a table name, we can easily see what is defined in the file. Users will be enforced to write the information explicitly in the file by requiring table, but I think it is better than to write comments manually.
So, here I propose changing the requirements for the splitted input files. It also introduce an extra complexity to read_* because the current implementation also allows to define a table. To simplify the code, we also need to decide the way to split an input file.
The splitted input files correspond to one element of arrays of tables, [[systems]], [[forcefields]] or something like that, so it is good to require a table for each file (e.g. [system] for a file that defines an element of [[systems]]).

ExcludedVolumePotential that is used with a global interaction requires radius for all the particles. But ExcludedVolumeWallPotential that is used with an external interaction (it acts as a wall!) requires sigma.
It should be fixed. I think radius is better because it's clearer.

Finally I found that it is not clear to use different name and data type for the same table defined in a different file (like, [forcefield.global] for an individual file and [[forcefields.global]] in a separated file).
For now, I decided to use the same name, [[systems]] and [[forcefields.global]] for separated input files.

done.


Upgrade - Testing Dev Environment

Test the dev environment once upgrade is deployed to it.
https://digital-journeys-dev.apps.silver.devops.gov.bc.ca/form
Tasks

Mat/Par - Fazil
Cold/Flu - Jerry/Stella
1.10 - Andrew/Ayush
Telework - Chris
SL Review - Andrew/Stella

Work with Mike to discuss test cases before the deployment
Scope - Only Dev, namespace is NOT is scope, Namespace will be done in #1616

After discussing with Bhumin, we concluded to perform End to End testing with common test scenarios for the forms listed above. Below is a general checklist of what to test on each form/page:

Functionality
Validation errors
Content changes
Form submissions
Emails and PDFs

The Formio version upgrade will also need testing, but will require Forms Designer access to test certain functions:

Filter Form/Resources: To the right of the search bar there is a new option to filter forms and resources.

Form History: As a forms designer click view/edit a form, on the top right it will show form history and duplicate form. To test - edit a form with any
small change, such as a content or title change, save the form, go back to form history and you will see any changes made there. If you want to
switch to a previous version, go to history and select a version, edit and save form. It will overwrite the form with a past version.

Form Versioning: is now an option to create a new form version. To test - submit a copy of any form. Edit the original form to add a new field and
check the box where it asks, “do you want to save a new version of this form?” There will now be two versions, an old and new version of the form.
New form versions will have the updated fields, but old forms will not. This is also the case with submitted forms.

Drafts: Need to retest if drafts work properly because of form versioning. The yellow warning box should show up if you have a draft when you
try to create a new form.

Search: You should be able to search submitted forms by form or candidate name.

Form Name Sorting: Click on up/down arrows to the left of the search bar to check if sorting form names cause any delay or lag.

Closing forms: Open a form, copy the URL, go into forms editor for the selected form and disable it for the end user by unchecking “Publish this
form for Client Users”. Paste the copied URL into the browser and it should show that the form is not published.

Form Submissions and Workflow: For all forms, we will need to do End to End testing with common test scenarios. The main concern here is that
the emails and PDF triggers are working properly after a submission is made, eg. email is sent to applicants and supervisors, they contain the
proper content, PDFs properly summarize the form, etc.

Search: You should be able to search submitted forms by form or candidate name.

For this one, please noted this is only applying to cold/flu and mat/par forms. And the form submitted after this name searching function implemented. So better to create new submission and test.

Tested 1.10 with Andrew! He is adding our findings in the comment below!

@fazil-ey  be sure to check the review page in new version as per #1583

For cold/flu,
Positive

submit the form
after submission, I can see in submitted page
as admin, I can edit in submitted page

Negative

name searching will show blank page

In the dev env, I cannot upload an attachment. I have tried two times and get the following error:

@bhumin-fw Hi Bhumin, can you look into this error. I have tried 2 times to upload ADM Supporting document for 3+ days and get the error object message as seen above. Thank you. C.

Also, when I try to create a new form, its asks for a path. How do I know what path to choose or write:

As a forms designer I tested:
Filter Form/Resources: DONE/Works great
Form History: DONE/Works great
Form Versioning: DONE/Works great
Drafts: DONE/Works great
Search: DONE/Works great
Form Name Sorting: DONE/Works great
Closing forms: DONE/Works great
Form Submissions and Workflow: Done for telework - issue with attaching/uploading Word doc, read above

@chriscaldwell-psa I have fixed upload document error. Please review it.
I'll check with Kunal and find its permanent solution, It is due to files services that stopped working couple week back on DEV environment.

@jerry-ey regarding your comment for not searching by name.
It should have required hidden field, that's the only requirements for it.

Let me know if you have any case in mind which in which it is not working.

@bhumin-fw  re: ADM supporting doc to upload - Thank you for fixing this so quickly. It works now.

1.10 works well.
Tested workflow for all routes, logic and validation for all fields.

Bhumin, refer to #1667 and https://github.com/bcgov/digital-journeys/pull/1668 for name search issue.

Tested SL Review.
All components, their logic and validation works well.
But, I am not able to validate and make the 'Final Submission'. The options are greyed out.

@bhumin-fw  is taking a look at this error. I will retest once the error is resolved.

Update to the above comment: Stella & Andrew is also not able to 'edit' the form. They are also just able to 'view' the form.
@bhumin-fw is actively working on this.

All Devs have resolved the above states error in SL Review.
Working perfectly now :)

Update - Mat/Pat

Reviewed validation and field logic, looks good
emails and pdf look good

No new issues found due to the upgrade


Upgrade chardet to 3.0.2

Description:
The issue which we needed to catch with #7063 seems to be fixed now (as far as I understand it).
This PR is to test it.

aiohttp is still not pinning chardet to a specific release.

So I initially added it because the last version had a breaking change. I think that it's smart to keep it as part of our requirements as long as aiohttp does not keep it pinned. This will prevent a similar situation in the future.


GetStreamingEvents returning undefined

I am only receiving undefined when my stream times out.
I use defineStream to subscribe to the inbox, sentitems, and calendar folder (arguments below). Then I initiate the stream. After 1 minute the stream closes, returns undefined, and my console logs '----- STREAM CONNECT ERROR -----'.
I await for the subscriptionId to be returned before I open the connection so I know its not that. I am wondering what else could be the issue?
public defineStream() {
        var ewsFunction = 'Subscribe';

        var ewsArgs = {
            'StreamingSubscriptionRequest': {
                'FolderIds' : {
                    'DistinguishedFolderId': [
                        {'attributes': {
                            'Id': 'inbox'
                        }},
                        {'attributes': {
                            'Id': 'sentitems'
                        }},
                        {'attributes': {
                            'Id': 'calendar'
                        }}
                    ]
                },
                'EventTypes': {
                    'EventType': ['CreatedEvent', 'ModifiedEvent']
                }
            }
        };
        //I Run ews here and get the subscriptionId.
    }

public initiateStream(subscriptionId) {
        var ewsFunction = 'GetStreamingEvents';

        var ewsArgs = {
            'SubscriptionIds': {
               'SubscriptionId':
                    subscriptionId
            },
            'ConnectionTimeout': '1'
        };

        this.ews.run(ewsFunction, ewsArgs, ExchangeConnector.ewsSoapHeader)
            .then(result => {
                console.log(JSON.stringify(result));;
                console.log('----- STREAM CONNECT SUCCESS -----')
            }).catch(err => {
                console.log(err.stack);
                console.log('----- STREAM CONNECT ERROR -----');
            })
}```

The undefined means that err.stack is not defined. Try console.log(err) and see what you get. Also, for more detailed debugging I use util (https://nodejs.org/api/util.html) to go deeper into the objects as the default is only like 3 levels.
Example
console.log(new Date().toISOString(),"| Error:",util.inspect(err,true,5,true))
Also, the problem I found with streaming requests as seen in problem #48 is that the responses need to be handled in real time as the server will send multiple envelopes with or without events during the time the connection is open resulting in a malformed XML structure. Unfortunately I haven't had time play with this, but I'd be curious if you can get it working.

Ah I read your issue before posting but I didn't realize it was the same issue. Thank you for the response! I ran console.log(err) as you suggested and got the response below. There are multiple envelopes in the body of the response. I will see what I can do.


IntelliSense?

Would it be possible to have IntelliSense-type code completion in nbterm? How so?
Thanks very much.

Hi @swetepete, thanks for your interest in nbterm!
I'm planning to rewrite nbterm using Textual. I think this kind of features would make sense in this new project, but it has not really started yet.


Player Head Generation

Support the generation of player Head and mobhead item stacks

I don't see why this can't be a plugin of it's own, since that would make more sense to me.
StickyAPI is just a library of common code and such. These are just my thoughts ^^

It's common for use in GUIs, etc. It already exists just needs to get its own proper branch.

It's basically code that takes a UUID, StickyUser, Player/OfflinePlayer, or name and texture, and makes an itemstack of it

If this solely creates the item stack, this fits in the API, it's unrelated to a command like /head :3

It just creates the stack or gets info out of a stack


[EPIC]: Add Identity

Add Identity Application to the single chart. Dependency of #126.

[ ] Add Keycloak dependency

[ ] https://github.com/codecentric/helm-charts/tree/master/charts/keycloak
[ ] https://bitnami.com/stack/keycloak/helm (might be prefered)
[ ] Add postgress

[ ] Add Identity as new sub chart

[ ] configure identity to access keycloak

[ ] Adjust existing services, like tasklist and operate to use identity
[ ] Add all possible variables to the values.yaml
[ ] Document values, based https://github.com/camunda/camunda-cloud-helm/blob/main/CONTRIBUTING.md#documentation
[ ] Write tests for identity templates see https://github.com/camunda/camunda-cloud-helm/blob/main/CONTRIBUTING.md
[ ] Update architecture image, you can find the source in google drive. zeebe/ccsm-helm/CCSM Helm Architecture Image.
[ ] Add documentation about identity to the camunda docs

Docker-compose: https://github.com/camunda-cloud/operate/pull/2415/files#diff-b358236a4158adf30757eb495bb0d551609faa7a3a796cac4d8d02d523d608ce

Keycloak does it similar with their passwords, they create a default secret and mount it into the statefulset:
  containers:
        - name: keycloak
          image: docker.io/bitnami/keycloak:16.1.1-debian-10-r52
          imagePullPolicy: IfNotPresent
          securityContext:
            runAsNonRoot: true
            runAsUser: 1001
          env:
            - name: KUBERNETES_NAMESPACE
              valueFrom:
                fieldRef:
                  apiVersion: v1
                  fieldPath: metadata.namespace
            - name: BITNAMI_DEBUG
              value: "false"
            - name: KEYCLOAK_ADMIN_PASSWORD
              valueFrom:
                secretKeyRef:
                  name: zell-keycloak
                  key: admin-password
            - name: KEYCLOAK_MANAGEMENT_PASSWORD
              valueFrom:
                secretKeyRef:
                  name: zell-keycloak
                  key: management-password
            - name: KEYCLOAK_DATABASE_PASSWORD
              valueFrom:
                secretKeyRef:
                  name: zell-keycloak-postgresql
                  key: password

\cc @menski

Worth to read https://itnext.io/manage-auto-generated-secrets-in-your-helm-charts-5aee48ba6918

https://artifacthub.io/packages/helm/bitnami/common/1.3.4 is used to generate secrets
See
https://github.com/bitnami/charts/blob/master/bitnami/keycloak/templates/secrets.yaml#L18-L19

@Zelldon one thing I forgot to ask: is it possible to create file mounts from a remote source? We have a custom keycloak theme that we could add to a github release as f.e. a zip archive.

Hey @dlavrenuek it seems https://github.com/bitnami/charts/tree/master/bitnami/keycloak allows to configure init containers and extraVolumes, might be possible with that. But I think this would be something I would do only after we get it running :D So lower prio for me, maybe also something we can add later?

Just sorting my thoughts, reading along https://github.com/bitnami/charts/tree/master/bitnami/keycloak and https://docs.bitnami.com/kubernetes/apps/keycloak/configuration/manage-passwords/
Current idea:
We create a secret for keycloak (admin password) and for postegress (admin pw), mount that via keycloak.auth.existingSecret and keycloak.postgress.existingSecret. This secret contains default values like admin:admin, which is also mounted into identity.
The user can specify an own secret, which can be mounted than in keycloak, postgress and identity and replaces our default secrets. We will then not deploy own secrets.
Example secret:
existingSecret:
  name: mySecret
  keyMapping:
    admin-password: myPasswordKey
    management-password: myManagementPasswordKey
    database-password: myDatabasePasswordKey
    tls-keystore-password: myTlsKeystorePasswordKey
    tls-truststore-password: myTlsTruststorePasswordKey

https://docs.bitnami.com/kubernetes/apps/keycloak/configuration/manage-passwords/
\cc @menski

Small update:
I run a test where I deployed the following secret:
apiVersion: v1
kind: Secret
metadata:
  name: ccsm-keycloak-secrets
type: Opaque
stringData:
  admin-password: "admin"
  password: "admin"
  management-password: "admin"

This can be seen as our default secret we would deploy in our helm charts, (btw if we see the need this could also be random values). For simplicity with integrating with identity I sticked to the admin:admin thingy.
I run helm install zell-keycloak bitnami/keycloak --dry-run -f values.yaml --debug, to see what the manifests would look like.
The values file looks like this:
## Keycloak authentication parameters
## ref: https://github.com/bitnami/bitnami-docker-keycloak#admin-credentials
##
auth:
  ## @param auth.adminUser Keycloak administrator user
  ##
  adminUser: admin
  ## @param auth.existingSecret An already existing secret containing auth info
  ## e.g:
  ## existingSecret:
  ##   name: mySecret
  ##   keyMapping:
  ##     admin-password: myPasswordKey
  ##     management-password: myManagementPasswordKey
  ##     tls-keystore-password: myTlsKeystorePasswordKey
  ##     tls-truestore-password: myTlsTruestorePasswordKey
  ##
  ##
  existingSecret:
    name: ccsm-keycloak-secrets

postgresql:
  auth:
    existingSecret: "ccsm-keycloak-secrets"

This causes to deploy a keycloak with the following env vars:
...
      containers:
        - name: keycloak
          image: docker.io/bitnami/keycloak:16.1.1-debian-10-r52
          imagePullPolicy: IfNotPresent
          securityContext:
            runAsNonRoot: true
            runAsUser: 1001
          env:
            - name: KUBERNETES_NAMESPACE
              valueFrom:
                fieldRef:
                  apiVersion: v1
                  fieldPath: metadata.namespace
            - name: BITNAMI_DEBUG
              value: "false"
            - name: KEYCLOAK_ADMIN_PASSWORD
              valueFrom:
                secretKeyRef:
                  name: ccsm-keycloak-secrets
                  key: admin-password
            - name: KEYCLOAK_MANAGEMENT_PASSWORD
              valueFrom:
                secretKeyRef:
                  name: ccsm-keycloak-secrets
                  key: management-password
            - name: KEYCLOAK_DATABASE_PASSWORD
              valueFrom:
                secretKeyRef:
                  name: ccsm-keycloak-secrets
                  key: password

And postgress also uses our configured secret:
  containers:
        - name: postgresql
          image: docker.io/bitnami/postgresql:14.2.0-debian-10-r35
          imagePullPolicy: "IfNotPresent"
          securityContext:
            runAsUser: 1001
          env:
            - name: BITNAMI_DEBUG
              value: "false"
            - name: POSTGRESQL_PORT_NUMBER
              value: "5432"
            - name: POSTGRESQL_VOLUME_DIR
              value: "/bitnami/postgresql"
            - name: PGDATA
              value: "/bitnami/postgresql/data"
            # Authentication
            - name: POSTGRES_USER
              value: "bn_keycloak"
            - name: POSTGRES_POSTGRES_PASSWORD
              valueFrom:
                secretKeyRef:
                  name: ccsm-keycloak-secrets
                  key: postgres-password
            - name: POSTGRES_PASSWORD
              valueFrom:
                secretKeyRef:
                  name: ccsm-keycloak-secrets
                  key: password
            - name: POSTGRES_DB
              value: "bitnami_keycloak"

This now allows us to deploy the secret per default, and the user could potentially replace it with an own secret.

@Zelldon If it is possible to have all secrets being randomly generated, we should do it. Having default secrets will always lead to security risks because there will be users who forget to update it or just don't know/understand how to do it.

Hey @dlavrenuek and @menski
yesterday I made some good progress, and had a breakthrough :tada:

All services where up and running and seem to connect to each other.
But there came up some questions form me which I would like to clarify, you can have a look at the changes here https://github.com/camunda/camunda-platform-helm/pull/251
BTW @dlavrenuek thanks for your input! I removed our default secret and reuse the secrets generated by the keycloak helm chart, which are random generated if not specified.
Questions:

If I port forward to the identity and open it in the browser it redirects immediately to localhost:18080/ (you can see that URL in the image above). This seems to redirect to Keycloak? I Had to port-forward to Keycloak as well to see the login mask. Is this expected?
What would be the credentials here to login? The admin user seem to not work here?
Is there anything I can do to login via CLI? Or direct http requests and get a cookie ? I want to use that in our integration tests, to verify whether login works and I can access the other services. Does this make sense?

Would be really nice if you could check the questions above and maybe also have a small look at the PR #251 , whether the configuration makes sense to you.

If I port forward to the identity and open it in the browser it redirects immediately to localhost:18080/ (you can see that URL in the image above). This seems to redirect to Keycloak? I Had to port-forward to Keycloak as well to see the login mask. Is this expected?

Yes this is expected right now as you need access to KeyCloaks web interface, it serves the Login page, but also you might want to login to keycloak to configure LDAP etc.

What would be the credentials here to login? The admin user seem to not work here?

As you are about to login to the Camunda Platform this are our default credentials demo:demo

Is there anything I can do to login via CLI? Or direct http requests and get a cookie ? I want to use that in our integration tests, to verify whether login works and I can access the other services. Does this make sense?

I will check it out, not sure yet

One think I saw during manually testing is that identity crashloops until keycloak is available, maybe we can add here a better handling. Like we do in operate/tasklist? @menski @dlavrenuek

@Zelldon a user can be added per env variables f.e. like here:
https://github.com/camunda-cloud/identity/blob/main/docker-compose-e2e.yml#L37
or here without a name but with the Operate role to access operate:
https://github.com/camunda-cloud/operate/blob/master/config/docker-compose.identity.yml#L26
Note that if Operate should be initialized in Identity, two additional values need to be added as in https://github.com/camunda-cloud/operate/blob/master/config/docker-compose.identity.yml#L24
      KEYCLOAK_INIT_OPERATE_SECRET: the-cake-is-alive
      KEYCLOAK_INIT_OPERATE_ROOT_URL: http://localhost:8080

Nice thanks @dlavrenuek this helps for the Operate integration I will do after https://github.com/camunda/camunda-platform-helm/pull/251 is merged and we have the next release candidate

@Zelldon is it possible to specify Keycloak as a dependency to Identity in a way so Identity is only started after Keycloak did? We do it in docker-compose with depends_on:... but it does not support a readiness probe, so the Identity container is restarted multiple times.

This is not possible in K8s, see also https://stackoverflow.com/a/53059163/2165134
Normally afaik applications retry and support a readiness and liveness check, here we can add a delay

Identity was successful integrated with all services and added to the helm charts


Fix misplaced paragraph in WARP docs

Restructured the title, description, table order for all of the sections. thanks for pointing out the confusion


Skips all songs

Describe the bug
When playing an album or a playlist, Spot skips all the songs and never plays any of them.
To Reproduce
Steps to reproduce the behavior:

Go to album or playlist
Click on play.

Expected behavior
Play each song of the album or playlist with its estimated time.
 This comment "resolved" the issue on my computer however it's more of a hack than anything.

I retested the app and it works fine


Feat: Improve the Ask Ubuntu scraper for other forms of questions

Describe the feature
Have to improve the ask ubuntu website to get the newest question, question with high scores and the active questions.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC 23 contributor
[X] I want to work on this issue

Go ahead @Mihan786Chistie |


Patch issue #157

If I did this correctly, this should patch issue #157. I'd appreciate any feedback on this PR as I'm unfamilar with camperbot's codebase.

Closed as stale.


remove warnings

DDI-1042

@chrisolsen There's so more errors to look into, specifically when running npm run build:all or more specifically nx run react-components:build-lib. Specifically The 'this' keyword is equivalent to 'undefined' at the top level of an ES module, and has been rewritten and "default" is imported from external module "react" but never used in.
Also in that first command, or nx run angular-demo:build-production, there is Warning: initial exceeded maximum budget. Budget 500.00 kB was not met by 74.80 kB with a total of 574.80 kB.
Also more warnings when running nx run angular-demo-e22:lint, but I'm not sure if we really care about these ones.
There's errors when linting web-components.
And errors when linting angular-demo and react-demo.
Also, not sure why it's not failing here, but when I run tests on web-components, it's failing. Specifically with src/components/dropdown/Dropdown.spec.ts
We could also reduce the output of the unit tests with something like this, https://eloquentcode.com/reduce-verbose-output-and-show-only-failing-tests-in-jest

:tada: This PR is included in version 2.0.0-alpha.6 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 4.0.0-alpha.79 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.120 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.18 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Create lsif-go.yml

Codecov Report

Merging #22 (323a766) into main (6a93669) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #22   +/-   ##
=======================================
  Coverage   54.48%   54.48%
=======================================
  Files          16       16
  Lines         569      569
=======================================
  Hits          310      310
  Misses        251      251
  Partials        8        8

Continue to review full report at Codecov.

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


android does not recognize gesture

my package.json is
{
"name": "Test",
"version": "0.0.1",
"private": true,
"scripts": {
"android": "react-native run-android",
"ios": "react-native run-ios",
"start": "react-native start",
"test": "jest",
"lint": "eslint ."
},
"dependencies": {
"@react-native-community/image-editor": "^2.1.0",
"react": "16.13.1",
"react-native": "0.63.2",
"react-native-gesture-handler": "^1.6.1",
"react-native-reanimated": "^1.8.0",
"react-native-redash": "^12.0.2",
"react-native-simple-image-cropper": "^3.1.0"
},
"devDependencies": {
"@babel/core": "^7.11.6",
"@babel/runtime": "^7.11.2",
"@react-native-community/eslint-config": "^2.0.0",
"babel-jest": "^26.3.0",
"eslint": "^7.9.0",
"jest": "^26.4.2",
"metro-react-native-babel-preset": "^0.63.0",
"react-test-renderer": "16.13.1"
},
"jest": {
"preset": "react-native"
}
}
when i run example project, it works fine. but when i install and run with 'npm install' android device doesn't recognize gestures.

Are you using a Modal or a View?

I fixed it by wrapping App.tsx in


Don't have phone default control

on my device it don't have button like bellow:

How to enable it?

Your device use physical buttons. Scrcpy does not emimate them, so you can use  the shortcuts instead. See #7.

okay thanks


JSON Error logging into Sagemcom Fast 5688w

I'm thinking my Sagemcom Fast 5688W updated in the past few days. The app worked fine, but now I'm getting a json error:

Same error 2024-01-02.  Will not connect.

I believe this may be a firmware issue and not necessarily related to Hint Control.  When I try Hint Control, I get this error.
@hannbah can you try the T-Mobile Internet application to see if you are also stuck in a loop?  When I try to access http://<IP_ADDRESS>/TMI/v1/gateway/?get=all it doesn't load at all — but if I browse to http://<IP_ADDRESS>/  it loads instantly.
I'm also seeing this:

It says I'm not connected, but I very much am (it's my primary internet).
Last thing: If you check the reviews you'll see people complaining of the same type of issues.
This is my guess.

I have the Sagemcomm as well I had to downgrade the app sadly...thanks for all your hard work zacharee if I were a wealthy man i would pay you handsomely and let u hand ick a team to just crack each router wide open. This is ridiculous.... Anyways thank you  so much for all your hard work don't give up!

This is maybe related to #2, but it's likely an issue with the gateway firmware.


Claude API key error

What happened?
Hi Team.
Whenever I paste my Claude API key, it says "Check failed". Please advise. Thanks.
Punk
Steps to reproduce
I am pasting the Claude key from Anthropic site. I need the key to summarize the transcript.
What OS are you seeing the problem on?
Window
Relevant log output
No response

I'll check it soon
https://github.com/tauri-apps/plugins-workspace/issues/2055

Fixed in https://github.com/thewh1teagle/vibe/releases/tag/v2.6.7


Update boehm-gc to 7.6

Issue description
Currently there is a patch applies to boehm-gc when building on cygwin:
https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/libraries/boehm-gc/cygwin.patch
It would be nice if we can update boehm-gc to 7.6 without breaking it on cygwin, but I have no idea how to do this.
cc @garbas
Thank you.

By the way, the current way I build the new version of boehm-gc is a172266a83fda28dea376c83d24a5aaa873cf2ca. (a workaround for me)
It seems that the new version of boehm-gc requires libatomic_ops to be installed or have its source avaliable before building. The strange thing is buildInputs = [ libatomic_ops ]; have no effect (libatomic_ops still cannot be found when configuring), so I use the latter approach.

It gets found when pkgconfig is added: https://github.com/dezgeg/nixpkgs/commit/6d786fe7259ce25ddccfc8ea62430534c5dd4f51
I checked the cygwin patch and at appears to be already applied in the 7.6 branch.
However, what's currently confusing me (if I'm looking at it right) is that the latest 7.6.x release doesn't appear to have a fix for this CVE: https://github.com/ivmai/bdwgc/issues/135

@dezgeg The vuln isn't new though, is it? Unless it is, there's no real need to hold a version upgrade back.


Where did the specification links go?

Prior to 48580b039197f45574f309b1c2ade18c17c2933b there was a folder called conventions.
Is there a recommended place to find this information now?

It's in their own repo now.. EG: https://github.com/stevemao/conventional-changelog-angular/blob/master/convention.md

@stephanebachelier Thanks!


Fix/governance fixes

Fixes issue where the governance token was being fetched for the proposals creator and not for the current connected wallet
Makes the design move slightly toward @campbellssource latest as it was a bit confusing what parameter was actually changing
Makes the single proposal page just fetch a single proposal by id
Adds containers for governance queries
Make table CSS consistent

Tested the fix on Staging and everything looks in order.
The new updated design changes for Governance Page works

When a user has 0 associated Vega tokens they cannot see the voting buttons on Governance page for updating network parameters proposals

And when the user has minimum associated Vega tokens they are able to vote on update network parameters goverance proposals


Unified line width for sashimi plot?

Hi, thanks for the great package. This is one of the very few tools that meet our need for Sashimi plot. I am wondering whether there is a way to set a unified linewidth range for more than one tracks. Right now different tracks have their different ranges of linewidths. This difference clearly represented in the y-axis. But I hope to make comparisons among samples (tracks) by just looking at the line width without the need to read the axis. I think that would make the difference among samples visually clearer.
Thanks

Hi,
This is currently not implemented but I can imagine that something similar to transform argument of the coverage could also do the job here. I will look at it.

As i wrote, it is not yet implemented.

Hi,
I added sashimiTransformation argument  to AlignmentsTrack, which works similarly to transformation and also expects single argument function. If  only transfromation is provided, the same function is applied to coverage and to sashimi score.
Available in version 1.33.1.


Typo in documentation $.Deferred should be $.Deferred()

In documentation at http://vitalets.github.io/x-editable/docs.html in Editable options -> url, in code example it says $.Deferred, but it should be $.Deferred().

Fixed!


Crashes while attempting to extract

Backtrace:
[Default] extracting binaries from '/home/whitequark/Applications/qFlipper-x86_64-1.3.2.AppImage'...
[ScriptingProvider] Exception in thread Thread-2:
[ScriptingProvider] Traceback (most recent call last):
[ScriptingProvider]   File "/usr/lib/python3.12/threading.py", line 1075, in _bootstrap_inner
[ScriptingProvider]     self.run()
[ScriptingProvider]   File "/home/whitequark/Applications/binaryninja/plugins/../python/binaryninja/plugin.py", line 1056, in run
[ScriptingProvider]     self.task.run()
[ScriptingProvider]   File "/home/whitequark/.binaryninja/repositories/official/plugins/Vector35_blobextractor/tasks.py", line 196, in run
[ScriptingProvider]     files = _extract_from_file(self.filepath, extract_dir, scan_only=True)
[ScriptingProvider]             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ScriptingProvider]   File "/home/whitequark/.binaryninja/repositories/official/plugins/Vector35_blobextractor/tasks.py", line 63, in _extract_from_file
[ScriptingProvider]     config = ExtractionConfig(
[ScriptingProvider]              ^^^^^^^^^^^^^^^^^
[ScriptingProvider] TypeError: ExtractionConfig.__init__() got an unexpected keyword argument 'entropy_depth'

This is with the following Python packages freshly installed:
Package         Version
--------------- --------
appdirs         1.4.4
arpy            2.3.0
attrs           24.2.0
cffi            1.17.1
click           8.1.7
cryptography    43.0.3
cstruct         5.3
dissect.cstruct 4.2
fs              2.4.16
jefferson       0.4.5
lark            1.2.2
lief            0.15.1
lz4             4.3.3
lzallright      0.2.4
markdown-it-py  3.0.0
mdurl           0.1.2
pip             24.3.1
plotext         5.3.2
pluggy          1.5.0
pycparser       2.22
pyfatfs         1.1.0
Pygments        2.18.0
pyperscan       0.3.0
python-magic    0.4.27
rarfile         4.2
rich            13.9.4
setuptools      75.5.0
six             1.16.0
structlog       24.4.0
treelib         1.7.0
ubi-reader      0.8.9
unblob          24.11.13
unblob-native   0.1.5

Downgrading to unblob-24.9.30 solves the issue.

Fixed in this commit: https://github.com/Vector35/blob_extractor/commit/cfed8a817b8f221b55cdd81121361d5528d2c805 (and cut a 1.0.3 release).
If you installed the plugin from GitHub, you should be safe to git pull and then upgrade unblob back to 24.11.13. I've included a requirements.txt to pin the Unblob package version to 24.11.13. If you installed from the plugin manager, the new version should be approved shortly. Once you upgrade the plugin, it will hopefully upgrade unblob to the version in the requirements.txt.
As always, thanks for reporting this @whitequark! Let me know if you have any other issues.

Apologies for this. We do our best not to release API breaking changes but this one had to be done. We'll send notifications in the future now that we know this plugin exists :)

@qkaiser no problem, easy fix =)
I appreciate you keeping an eye out for us in the future.


chore: add more trace nodes, for better profiling data

Description:
Stacked on:

[x] #209
[x] #204

Testing:
What tests have been run? Did make all succeed for your changes? Was
conformance testing successful on an Aarch64 machine? Yes
License:
By submitting this pull request, I confirm that my contribution is
made under the terms of the Apache 2.0 license.

@shigoel rebased on main, this is now ready for review

Also, I cherry-picked the changes from #214 onto this PR, to reduce the amount of open PRs


Refactor merge_prefactors functions and the relevant tests.

Codecov Report

Merging #107 (256696b) into computgraph_daniel (469a1dc) will increase coverage by 0.98%.
The diff coverage is 95.45%.

@@                  Coverage Diff                   @@
##           computgraph_daniel     #107      +/-   ##
======================================================
+ Coverage               55.00%   55.99%   +0.98%
======================================================
  Files                      51       51
  Lines                    2907     2929      +22
======================================================
+ Hits                     1599     1640      +41
+ Misses                   1308     1289      -19

Impacted Files
Coverage Δ

src/computational_graph/transform.jl
59.78% <95.45%> (+11.21%)
:arrow_up:

src/quantum_operator/operator.jl
76.92% <0.00%> (+2.56%)
:arrow_up:

src/computational_graph/io.jl
18.26% <0.00%> (+18.26%)
:arrow_up:

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


feat: add Stable token factory

Thanks for the review @boojamya 🔥

Any reason you got rid of all the previous app/upgrades folders? Or just a cleanup?

This is strictly a cleanup.

We will want to add the new stabletokenfactory to the OnRecPacket in the blockibc middleware.

Very nice catch! Made this change in https://github.com/strangelove-ventures/noble/pull/269/commits/ab3b6ff9e6ff069980fc475ee17e03b3dd6fe45f, feel free to check it out!
I also have one more change coming, which allows the x/tariff module to have multiple different fee denoms (right now it only supports one, namely uusdc).

@Mergifyio backport release/v4.1.x


External Auth not functional when auth service inside mesh

Bug description
When  running an authentication service inside the service mesh - for usage in the ext_auth filter in envoy - the cluster_name created will not be usable over gRPC due to the previously reported issue #5331, where the | is an invalid character for the authority header in gRPC.
The example envoy filter that would be utilising the invalid cluster_name is as follows:
apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
  name: external-auth-my-app
  namespace: default
spec:
  workloadLabels:
    app: my-app
  filters:
  - insertPosition:
      index: FIRST
    listenerMatch:
      listenerType: SIDECAR_INBOUND
      listenerProtocol: HTTP
    filterType: HTTP
    filterName: "envoy.ext_authz"
    filterConfig:
      grpc_service:
        timeout: 5s
        envoy_grpc:
          cluster_name: outbound|8083||auth.default.svc.cluster.local

In this case, what would be a potential solution to reference a cluster_name which is valid? This described scenario works fine if the authentication service runs outside the Service Mesh and I reference the in-cluster DNS name instead.
Affected product area (please put an X in all that apply)
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ x] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[x ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
External Authentication should work over gRPC when the authentication service runs inside the Service Mesh
Steps to reproduce the bug
Try and set up an authentication service which runs over gRPC and attempt to setup the previously described EnvoyFilter with ext_auth
Version (include the output of istioctl version --remote and kubectl version)
any version
How was Istio installed?
helm
Environment where bug was observed (cloud vendor, OS, etc)
gke
Additionally, please consider attaching a cluster state archive by attaching
the dump file to this issue.

@diemtvu Could you take a look or triage this issue?

@mandarjog may have better idea how this was fixed before.

FYI, https://github.com/istio/istio/issues/21841


DBeaver becomes irresponsive when scrolling through file with one very long line (MacOS)

Hi, I love DBeaver as an environment, but I've had lots of trouble with SQL files that contain long lines. I attached a file to this ticket. When I open it in Beaver 7.0.1 and try scroll to the bottom, it freezes up when it reaches line 168, and stays irresponsive for minutes almost melting my cpu.
Is this a bug, or a known limitation ?
dbeaver_crash.txt

I run macOS High Sierra (10.13.6)

Hi @MathiasVersichele ,
cannot reproduce it. Is it still actual for you?
Sorry for the late response

probably similar to #7777 .
Closed as duplicate


installation error

unable to install it on Pyton 3.12.
can you fix this? or help me to install?

Hi,
thanks for reaching out. Currently the libraray is pinned up until Python 3.11 (see in the toml)
In release 0.90 (next release I will include Python 3.12 as well (PR).
If you want to test it until then, you could do the following steps:

clone the repo
change the Python dependency to also cover 3.12
create a conda env: conda create -n "env_name"
in that conda env: pip install poetry
then: poetry install

Then you should be able to run BlueCast in the env.

In the PR itself I added Python 3.12 and the wheels (under dist folder) are updated already. So you could also download them and install from wheel to bridge the time until BlueCast 0.90 is out.

Thank you, Thomas, for your explanation. While I couldn't use the BlueCast with the provided instructions, I will attempt it later.

Feel free to open a new issue.The new release should be a matter of days only though.

Sure! thanks again!

BlueCast 0.90 released. Let me know in case you face any issues on Python 3.12


Can't install zmap

When ever I type sudo apt install zmap I get "unable to locate package zmap"

What OS and version are you using? Ex: Ubuntu 18.04

I'm using the latest version of kali linux
On Mon, Jan 22, 2024, 12:46 AM Phillip Stephens @.***>
wrote:

What OS and version are you using? Ex: Ubuntu 18.04
—
Reply to this email directly, view it on GitHub
https://github.com/zmap/zmap/issues/762#issuecomment-1902791617, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BFNFWVE6GM2FUHDBDL3HAPTYPWLF7AVCNFSM6AAAAABB6Q5X26VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBSG44TCNRRG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Looks like ZMap was removed from the Kali Linux package manager earlier this month. Kali Linux isn't presently one of our core supported OS's so we don't maintain it in the package manager. I'd follow the build-from-source instructions available here for Debian-based distros.
Moving forward, we're planning on a new ZMap release version soon and I'll be sure to get it back in the Kali Linux package manager at that point. Leaving this issue open and I'll close when its installable from the package manager again.

Looks like this was addressed on 1/31/24.


syzkaller: how to use it in android vts test

i found syzkaller source code in android/external/syzkaller

i found syzkaller test py files in android/test/vts-testcase/fuzz/kernel/syzkaller ,
and VtsKernelFuzzTest in android-vts/testcaes/

if run vts like below:

run vts -m VtsKernelFuzzTest

the reuslt will be like below:
No tests to be run.
===============================
===== TEST PHASE STARTING =====
05-12 14:36:55 D/ITestSuite: abi 'armeabi' is supported by device but not by this suite build ([armeabi-v7a, arm64-v8a]), tests will not run against it.
05-12 14:36:55 D/BaseTestSuite: Initializing ModuleRepo
ABIs:[{arm64-v8a, bitness=64}, {armeabi-v7a, bitness=32}]
Test Args:[com.android.tradefed.testtype.AndroidJUnitTest:rerun-from-file:true, com.android.tradefed.testtype.AndroidJUnitTest:fallback-to-serial-rerun:false, com.android.tradefed.testtype.VtsMultiDeviceTest:ltp-number-of-threads:1]
Module Args:[]
Includes:{armeabi-v7a VtsKernelFuzzTest=[VtsKernelFuzzTest], arm64-v8a VtsKernelFuzzTest=[VtsKernelFuzzTest]}
Excludes:{}
05-12 14:36:58 I/ITestSuite: No config were loaded. Nothing to run.
05-12 14:36:58 I/ITestSuite: No tests to be run.
05-12 14:36:58 D/PrettyPrintDelimiter:
===== TEST PHASE ENDING =====

Hi @yzj509,
We don't have any relation to that. Please ask android vts maintainers.


Vite 6 release

Hello,
Vite has released a new version (https://github.com/vitejs/vite/releases/tag/v6.0.3), when trying to update it I get:
npm error Could not resolve dependency:
npm error peer<EMAIL_ADDRESS>|| ^4.0.0 || ^5.0.0" from<EMAIL_ADDRESS>Is there a plan on updating the vite version used on vite-svg-2-webfont?

Yes, I plan to get to it.
If you feel like opening a PR to add it, that would be happily accepted!


Uncaught TypeError: Cannot read property 'contentWindow' of undefined

It's been a loong time since I've dealt with iframes, so this may be a silly question.
I'm testing using seamless.js within a Drupal installation. My "parent" page contains the following:
<head>
<script type="text/javascript" src="https://cdn.rawgit.com/travist/seamless.js/master/build/seamless.parent.js"></script>

<script type="text/javascript">
<!--//--><![CDATA[//><!--

  (function($) {
    $("#myiframe").seamless({
      container: "body"
    });
  }(jQuery));

//--><!]]>
</script>
</head>

<iframe id="myiframe" src="/d7_dev1/sites/all/modules/seamless/templates/index.html" style="width:100%;border:none;"></iframe>

The "child" page (index.html) includes the appropriate JS file:
<head>
  <script type="text/javascript" src="https://cdn.rawgit.com/travist/seamless.js/master/build/seamless.child.js"></script>
</head>

The child page is loading up in the iframe, but I am receiving the following error:
( Chrome 53.0.2)

seamless.parent.js:847 Uncaught TypeError: Cannot read property 'contentWindow' of undefined

(Firefox 48.0.1)

seamless.parent.js:847:5 TypeError: iframe[0] is undefined

Adding a timeout() to the inline JS resolves the error, but then I get the "Loading..." prompt followed by An error has been detected on this page. Click here to open in a separate window. This is what I would expect if my child page were on another domain, which it isn't.
I'm at a bit of a loss so would appreciate any pointers. Thanks in advance!

This is because you are checking for the iframe before it is a part of the DOM. I recommend wrapping the seamless call in a window.onload to ensure the DOM is loaded before calling into seamless.


Clone Play2Help into Play2Work, Play2Learn, Play2Health

Clone the play2helpNext into
Play2Learn
Play2Health
Play2Work
Change the contents , try to change the designs in a way so that they will different

Clone the play2helpNext into
Play2Learn
Play2Health
Play2Work
Change the contents , try to change the designs in a way so that they will different

Ok. I will do.


[GH-340] - Added support and default to docker engine 1.7.1 binary.

added support for 1.7.1 (with checksums) in helpers-new.rb parse_version()
change default to 1.7.1 in helpers-new.rb parsed_version()

Docker Engine 1.7.1 Changelog:
https://github.com/docker/docker/blob/v1.7.1/CHANGELOG.md

+1

Checksum validation steps:
# Linux Binary
$ curl -sSL -O https://get.docker.com/builds/Linux/x86_64/docker-1.7.1.sha256
$ cat docker-1.7.1.sha256
4d535a62882f2123fb9545a5d140a6a2ccc7bfc7a3c0ec5361d33e498e4876d5  docker-1.7.1

# Darwin Binary
$ curl -sSL -O https://get.docker.com/builds/Darwin/x86_64/docker-1.7.1.sha256
$ cat docker-1.7.1.sha256
b8209b4382d0b4292c756dd055c12e5efacec2055d5900ac91efc8e81d317cf9  docker-1.7.1

LGTM

@bflad any update on merging this?  Pretty simple change.

ping, any update @bflad

poke @someara @tduffield

Hey there. This is currently planned for the upcoming 1.0.0 release.
-s
On Wed, Aug 5, 2015 at 6:16 PM, Ryan Trauntvein<EMAIL_ADDRESS>wrote:

poke @someara https://github.com/someara @tduffield
https://github.com/tduffield
—
Reply to this email directly or view it on GitHub
https://github.com/bflad/chef-docker/pull/341#issuecomment-128165903.

Master is working with 1.7.1... moving right along to 1.8.1. =\


Adding custom build tags

I was wondering if there's a directive or something for adding build tags to the install process.
Example
go.mod
// +heroku goTags customtag

Build
Running: go install -v -tags heroku customtag some/package

Cheers.

No, there isn't.
Can you describe your use case so that we can understand the need(s)?

My application uses a build tag that modifies certain functions to increase performance while sacrificing metric collection. I'd like to enable that setting on when running on Heroku.
The reason I use built tags rather than a variable is because by combining constants and build tags the go compiler can optimize out unreachable code which then makes the function smaller and causes the compiler to inline the function.
I could reverse the constants so that you have to opt in for the extensive metrics but I don't really believe that's a good default - you should only enable the performance tags if you need them.

This is possible now by using the heroku build tag.
// +build existingTag heroku
// ^ existingTag OR heroku : https://golang.org/pkg/go/build/#hdr-Build_Constraints

The readme includes this comment: "This buildpack adds a heroku build constraint, to enable heroku-specific code."

Ah I had totally forgotten about the OR keyword. Thanks.

Sorry it wasn't clear for me.How can i pass fts5 tag for sqlite3 in such way?


Logging/trace has raw ANSI/garbage characters under Microsoft Windows

Extract:
<IP_ADDRESS> - - [08/Feb/2024 18:38:56] "?[33mGET / HTTP/1.1?[0m" 404 -
<IP_ADDRESS> - - [08/Feb/2024 18:38:56] "?[33mGET /favicon.ico HTTP/1.1?[0m" 404 -
<IP_ADDRESS> - - [08/Feb/2024 18:39:02] "?[33mGET /admin HTTP/1.1?[0m" 404 -
<IP_ADDRESS> - - [08/Feb/2024 18:39:11] "?[33mGET /resources HTTP/1.1?[0m" 404 -

Opened https://github.com/cs91chris/flask_autocrud/pull/10


Adding ability to give default QueryJobConfig to Client

closes #5183
This isn't a complete request (I need to do things like fill out the Contributor License Agreements, get coverage all the way to 100%, etc), but I wanted to begin the discussion to see if this was an acceptable direction. Only QueryJobConfig has been implemented, but the other types shouldn't be too difficult, since I've added a _JobConfig.fill_from_default method.

@blainehansen
Making a PR from your master branch makes things hard for you over the long term:  it creates barriers to synchronizing with this repository's master over time.
WRT the test failures, there is missing line / branch coverage for:
google/cloud/bigquery/client.py               374      1    160      1    99%   1244, 1236->1244

which is the case where no job_config is passed.

@tseaver Sorry about not creating a feature branch ha, I don't expect to maintain a fork for a long period, I was just hoping to include this feature, but I shouldn't have cut corners.

:+1: yeah making that private is definitely a better choice :smile:

:confetti_ball: :confetti_ball: :confetti_ball:
Thanks everyone!


Docker-Compose V1 Fix - v3.0.1

This fixes an issue introduced by v3.0.0 for old Docker-Compose V1 systems.
The compose-dash.sh will dynamically use V1 compatible powerwall*.yml configuration files based on configuration setting (default or solar-only).
This add two YML files:

powerwall-v1.yml
powerwall-v1-solar.yml

Close #388

✅ Docker-Compose V1 Upgrade
Upgrade Powerwall-Dashboard from 3.0.1 to 3.0.1
---------------------------------------------------------------------
This script will attempt to upgrade you to the latest version without
removing existing data. A backup is still recommended.

Upgrade - Proceed? [y/N] y

Resetting Timezone to Default...

Pull influxdb.sql, dashboard.json, telegraf.conf, and other changes...

No local changes to save
Already up to date.
Current branch main is up to date.

Setting Timezone back to America/Los_Angeles...

Updating Powerwall-Dashboard stack...
Running Docker Compose...
pypowerwall is up-to-date
influxdb is up-to-date
grafana is up-to-date
weather411 is up-to-date
telegraf is up-to-date

Waiting for InfluxDB to start...
 up!

Add downsample continuous queries to InfluxDB...
2023/11/19 07:41:48 error: retention policy already exists
2023/11/19 07:41:48 error: retention policy already exists
2023/11/19 07:41:48 error: retention policy already exists
2023/11/19 07:41:48 error: continuous query already exists
2023/11/19 07:41:48 error: continuous query already exists

Deleting old pyPowerwall...
pypowerwall
pypowerwall

Deleting old telegraf...
telegraf
telegraf

Deleting old weather411...
weather411
weather411

Restarting Powerwall-Dashboard stack...
Running Docker Compose...
influxdb is up-to-date
Creating pypowerwall ...
grafana is up-to-date
Creating weather411 ...
Creating pypowerwall
Creating pypowerwall ... done
Creating telegraf ...
Creating telegraf ... done

---------------[ Update Dashboard ]---------------
Open Grafana at http://localhost:9000/

From 'Dashboard/Browse', select 'New/Import', and
upload 'dashboard.json' located in the folder
/home/tesla/Powerwall-Dashboard/dashboards/

Please note, you may need to select data sources
for 'InfluxDB' and 'Sun and Moon' via the
dropdowns and use 'Import (Overwrite)' button.


Build docs and Lite deployment in ReadTheDocs

Resolves #208
Hooray! https://jupytergis--275.org.readthedocs.build/en/275/lite/lab/index.html?path=france_hiking.jGIS
Looks like linting is failing unrelated to my change -- perhaps a new release of typescript-eslint modifying detection logic or fixing a bug that was producing false negatives? What's y'all's preference? Deal with the linter errors in this PR or in another PR?

I am confused how I managed to break linting :laughing:

Working! JupyterLite in RTD: https://jupytergis--275.org.readthedocs.build/en/275/lite/lab/index.html?path=france_hiking.jGIS

The docs index page now has a badge linking to the lite deployment.

Ack how did I break this

Is the build perhaps a bit flaky? The only change between successful build and failing build was a pull request "opened" automation:
https://github.com/geojupyter/jupytergis/compare/f498a5e73fb7a46216676cd71ac530f9e0f37a61...4cd79b92fc7ac1300f3b5a273ea0b8bdfcddd21d
Failed: https://app.readthedocs.org/projects/jupytergis/builds/26699339/
Passed: https://app.readthedocs.org/projects/jupytergis/builds/26699052/

The check links failure was caused by the new jupyterlite button in the docs that I added. It's a relative link to lite/, and the link checker seems to be assuming that all relative links will have a corresponding file in the source. Perhaps we can tell the link checker to ignore that. I haven't started looking yet :)

Is the build perhaps a bit flaky?

Looks like yes, re-running the build on the latest commit passed it: https://app.readthedocs.org/projects/jupytergis/builds/26702609/

Wat? Now only 4 checks are running? Is GitHub Actions having a problem? There should be 12 checks.

GitHub is not claiming any outage... but I don't see how my change adding inputs to the check links action could cause 8 actions to not run. I'm going to push the commit again and see what happens.

Yup, re-pushing the commit triggered all the actions. It must be an issue on GitHub's side that they're not aware of yet.

Link check is fixed by ignoring the lite/ link in GHA config.


Assigned full semver to Action dependencies

Current dependencies on/for this PR:

main

PR #395   👈

This comment was auto-generated by Graphite.