Use file lock when updating settings

This PR adds the following changes:

Use file lock when saving settings into the settings file to eliminate race conditions
Only automatically update the settings file when the version in it is smaller than that of erathkit-data. Previously, the settings file was always updated when the version in it did not match the version of earthkit-data

Codecov Report
Attention: Patch coverage is 80.76923% with 5 lines in your changes missing coverage. Please review.

Please upload report for BASE (main@34286ff). Learn more about missing BASE report.

Files with missing lines
Patch %
Lines

tests/core/test_settings.py
80.76%
2 Missing and 3 partials :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #559   +/-   ##
=======================================
  Coverage        ?   90.24%
=======================================
  Files           ?      149
  Lines           ?    10931
  Branches        ?      518
=======================================
  Hits            ?     9865
  Misses          ?      899
  Partials        ?      167

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Cross domain issue patch for old ie browsers (<=7)

Refactored version of this request  https://github.com/documentcloud/backbone/pull/806

Sorry -- this completely broke all Router functionality in Internet Explorer. Reverted.

Nope, this bug isn't in my code, i have the same errors when i run tests without my patch.

I made some research. This bug occurs in IE 6,7,8, because window.location.hash = "mandel?a=b&c=d" will make you this "http://myhost.com/?a=b&c=d#mandel" URI.


Composer does not recognize valid bearer token

Describe the bug
Version
2.1.2-12d25794b
Browser

[ ] Electron distribution
[ ] Chrome
[ ] Safari
[ ] Firefox
[ x] Edge

OS

[ ] macOS
[x ] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

get Composer nightly build
yarn install + build + startall
open echobot sample
Configure / Development resources / Set up language understanding / Use existing
from bash run az login then az account get-access-token
copy valid token and paste into Composer
'Token expire or token invalid' error

Expected behavior
paste in valid token, get accepted, add LUIS and do other things.
Screenshots

Additional context
Why do we care given we can just paste in the key? Well I wonder if this error is the cause of the real problem, which is that Composer crashes with error "jwt.decode is not a function". I'll log that as a separate ticket.

Hi @OEvgeny, we'll review this one and let you know as soon as we have some information.
Thanks!

Hi @duncan-at-hicksons, @OEvgeny, we couldn't reproduce this issue. The only time we saw the error was when using an expired token.
Composer is using the jwt-decode package to decode the token, so the upgrade of jsonwebtoken shouldn't impact this functionality.
Additionally, in version 9 of jsonwebtoken, the decode function was refactored, but it is still present.
This method is used in the directline middleware, but we couldn't make this fail either.
When are you seeing the "jwt.decode is not a function" error?

Thanks @ceciliaavila
I was getting "jwt.decode is not a function" whenever I ran my bot in the nightly build and chose “test in webbrowser”. This crashed yarn.
I’ve dug into this and found my issue: I hadn’t run az account set –name “subscription name”
Doing so means the token is now accepted and also that jwt.decode is not a function is no longer the error message and yarn no longer crashes.
Instead I get a post 401:
An error occurred validating the Microsoft App Id and Microsoft App Password.AADSTS7000216: 'client_assertion', 'client_secret' or 'request' is required for the 'client_credentials' grant type. Trace ID: 58994067-9a97-4be8-9ab6-cf51222be600 Correlation ID: 5b8c6968-ae05-4d73-84f2-6f8c6b88bc50 Timestamp: 2023-03-27 22:21:48Z
It runs fine in emulator.
I don't suppose you have thoughts on that?
If it's preferred, should I start a separate ticket?
Background: this bot runs in emulator and web-browser in BFC 2.1.2. I am trying to get it to run in the nightly so that I can use the fix there for Form Recognizer in web-browser.

Hmm. Curious.  @ceciliaavila
So I can still replicate the original issue:

open EchoBot in the nightly and include a valid token.
put in a valid bot ID and password
start bot
try to view in web browser
yarn will crash with jwt.decode not found.

Hi @duncan-at-hicksons, thanks, we were able to reproduce the error. We are preparing the fix for the decode bug.


Broken docs with  and  tags

Do you want to request a feature or report a bug?
bug

What is the current behavior?

Documentation files that contain expandable/collapsible text are not being displayed properly.
There's no code formatting, syntax highlighting and </details> closing tag is being ignored - the text from the opening tag to the end of the file is collapsed.
It looks like an undocumented GitHub feature that was removed/is broken. The only info I found about it is a Gist file and the example there isn't working either: https://gist.github.com/ericclemmons/b146fe5da72ca1f706b2ef72a20ac39d
The latest comment there suggests that Markdown is no longer parsed inside the <details> tag.
If the current behavior is a bug, please provide the steps to reproduce.
Open a document that contains <details> and <summary> tags, eg. https://github.com/webpack/webpack/blob/master/examples/i18n/README.md
Look for ▶ symbol and expand it. You'll notice a </details> tag at the beginning of a code block and more content that should be displayed even if the details are collapsed.

What is the expected behavior?
The content is formatted and only unnecessary details are hidden, or everything is displayed.
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
Checked in the latest Chrome and Firefox.

I'm happy to submit a pull request if you let me know how you'd like to handle it.

The new github-flavored-markdown parser...

@sokra @bebraw I'd like to submit a fix. I did some research - looks like there's no other solution for collapsing/expanding with GitHub Markdown. So, I think we've got two options:

Replace collapsed (non-essential) code with a comment, eg. // Webpack require mechanism - ommited for brevity.
Keep the whole listing - just remove <details> and <summary> tags.

Which one do you guys prefer?

Both have their sides. 1. would be neater but lead to more maintenance perhaps. 2. would be easier.
Maybe 3. would be possible. What if we hid the output within HTML comments and render them through the site so that they fold?

Regarding the first option - there shouldn't be more maintenance required. There's an examples parser (https://github.com/webpack/webpack/blob/master/examples/template-common.js#L46) that adds the <summary> and <details> tags - it should be pretty straightforward to replace those with a comment.
In terms of option 3 - at the moment the listings are not rendered to the page (checked both v1 and v2):

They are just links to the examples/ folder on GitHub. Are you suggesting that we render the examples to the page instead?

They are just links to the examples/ folder on GitHub. Are you suggesting that we render the examples to the page instead?

If it's useful, the site could pick up the examples too so you get <plugin>/examples/<example>.
Let's wait for Tobias on final decision.

fixed


[Bug] Build failure on macOS

Describe the bug
Build fails when building the Evercrypt crate.  Reporting it here because (a) the error is different when building OpenMLS than when building the Evercrypt crate directly, and (b) because @franziskuskiefer is in charge either way.
To Reproduce
On macOS 10.14.6, with homebrew-installed gcc 10.2.0_4.
git clone https://github.com/openmls/openmls.git
cd openmls
cargo build # works with or without --verbose --release

Expected behavior
It builds.
Actual behavior
It doesn't build.
Screenshots or debug log
https://gist.github.com/bifurcation/7b1df0a7f4447209c8a8b88d161c3dec
Platform (please complete the following information):

macOS 10.14.6
gcc 10.2.0_4 installed via homebrew (appears that it may not have been used)

Thanks for reporting @bifurcation! It appears to be a problem that recently occurred upstream in hacl. This might be related:
https://github.com/project-everest/hacl-star/issues/412
https://github.com/project-everest/hacl-star/issues/407
I filed this in the meantime: https://github.com/franziskuskiefer/evercrypt-rust/issues/20.

Looks unrelated to those two issues...


The preview feature "relationJoins" is not known.

Bug description
After updating to version 5.7.0, whenever I add relationJoins to the previewFeatures, a red line appears, indicating the following:

"The preview feature "relationJoins" is not known. Expected one of: deno, driverAdapters, fullTextIndex, fullTextSearch, metrics, multiSchema, postgresqlExtensions, tracing, views"

It does not interfere with npx prisma generate, as it is merely a visual bug. Is this issue specific to me? I have not come across any related problems during my search.

How to reproduce

Go to vscode and schema.prisma file
Add "relationJoins" in previewFeatures

Expected behavior
"relationJoins" is considered a known preview feature.
Prisma information
<! -- >
Environment & setup

OS: Debian
Database: PostgreSQL
Node.js version: 18.16.0

Prisma Version
Environment variables loaded from .env
prisma                  : 5.7.0
@prisma/client          : 5.7.0
Computed binaryTarget   : debian-openssl-1.1.x
Operating System        : linux
Architecture            : x64
Node.js                 : v18.16.0
Query Engine (Node-API) : libquery-engine 79fb5193cf0a8fdbef536e4b4a159cad677ab1b9 (at<EMAIL_ADDRESS>Schema Engine           : schema-engine-cli 79fb5193cf0a8fdbef536e4b4a159cad677ab1b9 (at<EMAIL_ADDRESS>Schema Wasm             : @prisma/prisma-schema-wasm 5.7.0-41.79fb5193cf0a8fdbef536e4b4a159cad677ab1b9
Default Engines Hash    : 79fb5193cf0a8fdbef536e4b4a159cad677ab1b9
Studio                  : 0.495.0
Preview Features        : fullTextSearch, relationJoins

Should be a way to set what version of Prisma the extension actually uses

@janpio, I am pleased to inform you that the mentioned issue has been satisfactorily resolved. Consequently, I request that we proceed with its closure. Thank you for your attention to this matter.


[DON'T MERGE] Add support for password-protected sentinels

Ref: https://issues.jboss.org/browse/THREESCALE-2620

It turns out that there was a bug in redis about this: https://github.com/redis/redis-rb/pull/856
They included the fix in redis-rb 4.1.2, but that version also drops support for Ruby < 2.3.0, so we cannot merge this.

Added a new commit that monkey patches the Sentinel client class to fix the issue without upgrading the gem.

Created an issue so we don't forget about this: https://github.com/3scale/apisonator/issues/102


Keyboard shortcuts to toggle individual utilities

Description of the new feature / enhancement
A system enabling shortcuts that toggle the activation status of modules/utilities.
Scenario when this would be used?
My specific issue is with QuickAccent: In one game I play regularly, I'm using the arrow keys for additional controls. If those are triggered while a primary key with available accents (like A or E) is being held, QuickAccent opens up. That results in a loss of control and/or the primary key becoming "stuck".
I find QuickAccent very useful, but this issue forces me to constantly have to open the PowerToys settings and toggle it. It would be much nicer to have optional keyboard shortcuts for toggling utilities.
Supporting information
No response

/needinfo


Bundler prints some warnings to standard output

For example, running bundle exec some_command when an outdated Bundler is installed produces output like:
The latest bundler is 1.15.3, but you are currently running 1.15.1.
To update, run `gem install bundler`

That is a helpful message to be sure, but the warning message is printed to STDOUT instead of STDERR, which is problematic if you are trying to consume the output of some_command. I could (almost) see Bundler being lax about where the output for Bundlers own commands like bundle install get printed, but bundle exec is there to provide a way to run Bundler-enabled scripts, which quite reasonably should not expect their output stream to contain messages from Bundler.

Bundler will print warnings to stderr in version 2

Also, in 1.15.3, that warning won't be printed at all when running bundle exec


Hadoop 2.9 again

Fixes #290. I'm having trouble remembering why we had to revert this change when we first did it a few months back, but iirc it had to do with a library which now depends on this Hadoop version, which I assume means this is fine now.
cc @ash211 @nartmal

Alright, good to go again as far as I'm concerned. The latest bump gets some stream metrics for s3a, and more excitingly, source JARs!


fix: Extra generation

Fix the generation of extra theme.
Use sky blue color for string.
Add color for yaml properties.
Regenerate colors.

Close #16


fix(cli): missing dependency

copilot:all

Current dependencies on/for this PR:

main

PR #3359   👈

This comment was auto-generated by Graphite.

@wittjosiah merged this pull request with Graphite.


Feature: option to only fill empty fields

Great extension! It's been very useful.
I was wondering if you'd be open to adding an option to only fill empty fields? There are times where I have forms that have default values that I'd prefer not to change.

@mcantrell "Ignore fields that already have content" option doesn't work for you?


[Suggestions] User controlled experience

Sebastian. I have so many thoughts, this is really fun. I think I might fork this project and start tinkering with it myself, but here are outstanding ideas that I thought were worth sharing:

Option to decrease curvature of the map. The world is big, but I think it could afford to be a bit bigger, especially when trying to target island nations or getting <50km accuracy on cities. For reference, the ISS circles at 408 km
Remove boundaries. I do like the light up effect, I think there's benefit in keeping that- but the world doesn't have boundaries (maybe as a 'hard mode option'). The current boundaries are not super useful for instance for Europe at night.

Game play mode ideas

Timed mode
All countries mode

Map "games" I enjoy:

Sporcle: https://www.sporcle.com/games/teedslaststand/find-world-countries)
On android Map World Quiz

FYI, you can also start Github Discussions: https://docs.github.com/en/discussions/collaborating-with-your-community-using-discussions/about-discussions
If you'd prefer more a chat medium over issues.

Thanks for the suggestions, and I've enabled Discussions now :)


Add code for school examples to examples repo #1295

Added PyMC3 code to generate models and later compared with the already available inference data.

Thanks for the PR! It is looking good!
We still have not clearly defined how exactly we want the examples to look so we may have to discuss a little to agree on something, we'll try to be quick

I have uploaded updated files that have following-

Underlying arviz and array versions are now updated. You can view the HTML formatted output which was not available in the previous submissions.
Also, I have added a code block for saving the model in .nc format using arviz.to_netcdf() API by passing arguments data & filename.

Thanks!

Also, I have added a code block for saving the model in .nc format using arviz.to_netcdf() API by passing arguments data & filename.

Can you add *.nc to the .gitignore? They should not be included to the repository due to their large size.

Thanks!

Also, I have added a code block for saving the model in .nc format using arviz.to_netcdf() API by passing arguments data & filename.

Can you add *.nc to the .gitignore? They should not be included to the repository due to their large size.

@sudip-padhye in addition to the .nc file should be removed entirely from the git commit tree. Unfortunately there's no easy way to do this other than removing the commit that introduces the file through a rebase, or using a tool like this one https://rtyley.github.io/bfg-repo-cleaner/

Deleting the file plus then us doing squash and merge should not include the nc files anywhere in the fit tree, I think there is no need to an extra rebase

Deleting the file plus then us doing squash and merge should not include the nc files anywhere in the fit tree, I think there is no need to an extra rebase

Ah yea that's easier.

This is great @sudip-padhye ! I'll merge once you delete the .nc files


fix webhook_config path

Couldn't get it to work and this seems to fix it. Maybe I am misunderstanding this but I think your run-hugo.sh script should point to /opt/container/webhooks.json like run-webhook.sh (from docker-nginx-unit-webhook) does.

You're correct, I was using /etc and one point and switched it over in the other unit but not this one.


ntr: normal protein transport along microtubule during vegetative growth

I'm being a bit picky here but I'm one term short
For this one I wanted
ntr: normal protein transport along microtubule to cell cortex of cell tip during vegetative growth

normal protein transport along microtubule to cell tip cortex during vegetative growth FYPO:0005841
edit file: 0b30150db46ca4fa9ec69fa8fc23d6647733f798
release: d7531c90d1f9889de8e57e611de9c402f4687db4

Hmm, why Oh why don't I put the PMID.... this could be one of about 10....

PMID:15177031


Overlapping vertex attributes break the API and GUI.

Description
Overlapping attributes break the internal api for RenderDoc and the api which RenderDoc uses to render its GUI when doing the steps listed below with the repository I linked.
After following the steps, I get a diagnostics log full of errors, and the gui starts to bug out if I switch to TextureViewer or move the window around on my screen:

Notice how I've selected the "Texture Viewer" tab and views from the "Mesh Viewer" and "Diagnostics Log" tabs appear.
Steps to reproduce
Here's my repo dedicated to this bug: https://github.com/OptimisticPeach/renderdocbug

Have Rust installed.
Have an internet connection to download dependencies.
Have a Vulkan-compatible driver.
Compile using cargo build or run directly with cargo run. (Give it a minute, this may take a while).

There's a RenderDoc capture there, along with a diagnostics log.
Relevant to RenderDoc:

Capture application (which is in <my repo>/target/debug/renderdocbug.exe.
Open captured frame.
Select relevant pass.
Open "Pipeline State" tab.
"Vertex Input" should be selected as the pipeline stage.
Click on "Mesh View".
View data (Should be fine)

Relevant shader is in <my repo>/src/terrain_shader.vert, recompile using make (Requires having glslangValidator available). The attributes which are overlapped are colour and example near the top of the file, and are decorated with layout(location = [2/3]) in attributes.
Vertex attributes are listed in the array at line 297 of src/main.rs. In this case I interpret a [u8; 4] (an array of exactly four unsigned bytes) both as a normalized vec4 in the shader (colour), and as a non-normalized value under ivec4 (example).
Environment

RenderDoc version: RenderDoc Version v1.9 (built from 22dbb188).
Operating System: Windows 10 Home version 1909.
Graphics API: Vulkan (Not sure what else to put here?).

Please do reply asking for more debugging information, I'd be very happy to give you more.

The capture provided contains an invalid mismatch between the pipeline vertex attribute descriptions and the shader. In the pipeline vertex attribute 3 is given format VK_FORMAT_R8G8B8A8_UINT but the shader declares an input as a signed integer (look at the GLSL, in ivec4 example). The base format of these must match, either both signed or both unsigned.
The validation layers identify this problem:

[UNASSIGNED-CoreValidation-Shader-InterfaceTypeMismatch] Validation Error: [ UNASSIGNED-CoreValidation-Shader-InterfaceTypeMismatch ] Object 0: handle = 0x4f0c9200000001e8, type = VK_OBJECT_TYPE_SHADER_MODULE; | MessageID = 0xb6cf33fe | Attribute type of VK_FORMAT_R8G8B8A8_UINT at location 3 does not match vertex shader input type of ptr to input vec4 of sint32
[UNASSIGNED-CoreValidation-Shader-InterfaceTypeMismatch] Validation Error: [ UNASSIGNED-CoreValidation-Shader-InterfaceTypeMismatch ] Object 0: handle = 0x4f0c9200000001e8, type = VK_OBJECT_TYPE_SHADER_MODULE; | MessageID = 0xb6cf33fe | Attribute type of VK_FORMAT_R8G8B8A8_UINT at location 3 does not match vertex shader input type of ptr to input vec4 of sint32

You should always make sure to fix any validation layer problems identified, as RenderDoc itself does not generally handle invalid API use. This may also break on some drivers depending on how the undefined behaviour manifests.


v0.3.10 error win32 x64

:warning:Please attach %TEMP%\vscode-java-installer\log.txt and %TEMP%\vscode-java-installer\AdoptOpenJDK-MSI.log for more details.
version: 0.3.10
env:
JAVA_HOME: undefined
PATH:
C:\Program Files\AdoptOpenJDK\jdk-<IP_ADDRESS>-hotspot\bin
C:\Program Files (x86)\Common Files\Oracle\Java\javapath
C:\Python39\Scripts\
C:\Python39\
C:\Program Files (x86)\mingw-w64\i686-8.1.0-posix-dwarf-rt_v6-rev0\mingw32\bin
C:\Users\RAMESH Pandey\AppData\Local\Programs\Python\Python38-32
C:\Program Files\Java\jdk1.8.0_121\bin
C:\Users\RAMESH Pandey\AppData\Local\Programs\Python\Python38-32\Scripts
C:\Program Files\nodejs\
C:\ProgramData\chocolatey\bin
C:\Program Files (x86)\mingw-w64\i686-8.1.0-posix-dwarf-rt_v6-rev0\mingw32\bin
C:\Users\RAMESH Pandey\AppData\Roaming\npm
C:\Users\RAMESH Pandey\AppData\Local\Programs\Microsoft VS Code\bin
JDKs:
C:\Program Files\AdoptOpenJDK\jdk-<IP_ADDRESS>-hotspot	env.PATH,DefaultLocation
C:\Program Files\Java\jdk1.8.0_121	env.PATH,DefaultLocation

log:
[9:18:41 PM] arch:x64
[9:23:06 PM] Download Visual Studio Code ... [Completed]
[9:23:06 PM] Install Visual Studio Code
[9:23:42 PM] Install Visual Studio Code ... [Completed]
[9:23:42 PM] Configure Java Settings
[9:23:42 PM] Error occurred
[9:23:42 PM] Error:  Please check if you have access to Windows Registry.

[9:23:42 PM] Error:  Please check if you have access to Windows Registry.

VS Code was installed but failed to be detected, because it searched Windows Registry for installation records...
You can manually install Java Extension Pack.


HUMAP

I just found the HUMAP online: https://github.com/wilsonjr/humap
Maybe it's worth a try? It's conda-installable and if it makes sense, we could add it to our list of dimensionality reduction techniques.

HUMAP seems like a very interesting method. However, it requires Eigen (C++), which would make plugin's installation more complex since Eigen needs to be downloaded as a zip file and extracted in the right location, and we aim to have ncp easily installable by beginners and as part of devbio-napari.
Therefore, at least for now, this issue will be closed.


Add more examples by using XLSX

Please add more examples for usage of XLSX

Confirm this! Examples are highly appreciated.


feat(station): Auto-approve requests from controllers when they are created

As discussed offline, we're going with different approach. Closing this.


Support for electric cars and their protocol is welcomed?

There is a android opensource app for OBD2 diagnosis where the developer ties to not spend that much time into implementing so much different protocols.
https://github.com/fr3ts0n/AndrOBD/issues/231
Are you interested at adding support for most protocols in this software or where did you cut the line?
Why have you decided to start a new project instead of working on existing ones like https://github.com/fenugrec/freediag ? I ask this because of being curious, not as a critic point.

After some research I was not happy with the open source solutions out there in Python. That is why i started to do it on my own. I am pretty new to the topic of OBD 2 and I am missing still protocols and commands. I welcome any sources and tips of protocols and commands for specific or any car models because I find it difficult to find any. I have the feeling that most of the interesting ones are gatekeeped by software companies on purpose which want licenses for money to get them.


add verbose flag for karmor probe

Signed-off-by: Anurag<EMAIL_ADDRESS>Fixes #226

Refactored the output of karmor probe.
The usual loading time is 1/3rd of the existing one.
I tested this on a 3 node GKE cluster and results are following.

# truncated
$ time ./kubearmor-client probe
./kubearmor-client probe  0.09s user 0.01s system 1% cpu 6.258 total
$ time ./kubearmor-client probe -v
./kubearmor-client probe -v  0.16s user 0.05s system 1% cpu 18.309 total

The new output looks something like this.

$ ./kubearmor-client probe

Found KubeArmor running in Kubernetes

Daemonset :
 	kubearmor 	Desired: 3	Ready: 3	Available: 3
Armored Up pods :
+-----------+------+--------+
| NAMESPACE | NAME | POLICY |
+-----------+------+--------+
| default   | pod  |        |
+-----------+------+--------+

@kranurag7 Kindly review the suggested changes.
cc: @nyrahul

This proposal is not planned as of now (as per our discussion in community meetings). Closing this. karmor probe does the job.


Synchronized groups support

Hi , please update documentation whether Synchronized groups supported or that is supported by cloud-only groups.
Also, can  you pls clarify whether PIM groups functionality supported if we nest AD groups into cloud groups?

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

ID: b427c59d-d87e-7b8d-f197-fe5ed529f74c
Version Independent ID: 57b69578-ed34-4906-65ca-4178f2befb5a
Content: Managing privileged Azure AD groups in Privileged Identity Management (PIM)
Content Source: articles/active-directory/privileged-identity-management/groups-features.md
Service: active-directory
Sub-service: pim
GitHub Login: @curtand
Microsoft Alias: curtand

Thank you for your feedback! We will review and update as appropriate.

@sokoloffmaks Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

any update on this? thanks

Hi @sokoloffmaks
Thanks for your interest and your contribution! The reason you have found no mention of the issues you care about is that PIM Privileged Access groups are based on using Azure AD role-assignable groups. The conceptual info about role-assignable groups is contained in the following article:
https://docs.microsoft.com/en-us/azure/active-directory/roles/groups-concept
To save you time, neither on-premises groups nor nested groups are supported for role-assignable groups. Thanks for your question!
#please-close


newIssue

test

I want to create a simple containerized nodejs app which runs a web page that displays information about myself.


"View" dialog should be closable by pressing Esc

The new "View" dialog does not react to pressing the escape button. It would be great to support that to be more in-line with how other software behaves.

Definitely, the feature is still fairly new and needs some improvements. As a long time user, may I ask what you use the dialog for?

Resolved with #702


TP: fixes bug that surfaces when trying to compare profiles without params

What does this PR (Pull Request) do?
This PR fixes a bug highlighted by a failing UI test. When comparing 2 profiles, if one or both of the profiles has no params, then the comparison page fails to load.

[x] This PR is not related to any Issue

No tests as this is a scenario covered by a current UI test

No documentation as this is simply a bug fix

No changelog.md entry as this bug was not released with any TC release

Which Traffic Control components are affected by this PR?

Traffic Portal

What is the best way to verify this PR?

In TP, navigate to the profiles view - tp.domain.com/#!/profiles
Select 2 profiles to compare. Ensure that at least one of those profiles has ZERO params associated with it
Ensure that the profile diff page is displayed correctly.

If this is a bug fix, what versions of Traffic Control are affected?

master (0974c74)

The following criteria are ALL met by this PR

[x] This PR includes tests OR I have explained why tests are unnecessary
[x] This PR includes documentation OR I have explained why documentation is unnecessary
[x] This PR includes an update to CHANGELOG.md OR such an update is not necessary
[x] This PR includes any and all required license headers
[x] This PR ensures that database migration sequence is correct OR this PR does not include a database migration
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Additional Information

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/4600/


Fix gallery examples

For #3983
Broken by https://github.com/uber/deck.gl/pull/3992 (no longer exposes all exports globally) and https://github.com/uber/deck.gl/pull/3880 (no longer adds auto controller)

Coverage decreased (-2.5%) to 80.639% when pulling 424485ed681f4992836b37a0ea4f813f568938fe on x/gallery-bugs into 3598b129fcce4437f2bfb2a88d9ced8593a2fd37 on master.


Upgrade deps and fix netlify

Fix Netlify to support PNPM
Upgrade react-scripts and react-testing-library
Remove jest-environment-jsdom-sixteen

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Added SSLVPN connection count per VDOM and IPSec status/traffic gauge

Thanks for this project!
sslvpn connection count
ipsec tunnel status + rx/tx traffic
I also changed the Dockerfile, greatly reducing the image size.
For some reason the interface speed was float so I changed the struct, not sure if this is differ from version to version
I just now realize I pushed some tls tweaking I had to to due to our slow firewall, might not be needed.

Oh! And please update the readme.md file to include the new metrics, thanks!

yes sure,
COPY --from=builder /etc/ssl/certs/ca-certificates.crt .
this should work just fine

Looks good to me, @Boolman are you happy with this or do you have more changes you want in before I merge this?

No im all gooood, thanks.


Use rich to replace tqdm, tabulate, etc.

If we end up adopting rich, we could maybe use some of its other features to reduce dependencies, for example replacing tqdm with rich.progress and tabulate with rich.table. It could also serve to implement a pager functionality for long output texts.

rich was added in https://github.com/mandiant/capa/pull/2086

@mr-tz, Is this task open for working?
I'm interested to work on this issue

yes, please go ahead!

Let's also replace termcolor.

Hi @Rana-KV, are you still working on this issue?

Unassigned due to inactivity.


Minor spelling/grammar/style fixes

Cuz it's hacktoberfest, and all. :)

Hah, the irony. ;) Will get on it right away.

Thanks @nlsdfnbch! Looks great. :) Sorry for being picky. ;)


ifconfig command not found on OS X with electron

Describe the bug
When trying to read the network interfaces on macOS, the electron console logs
/bin/sh: ifconfig: command not found and returns an empty array.
To Reproduce
Steps to reproduce the behavior:

used function si.networkInterfaces()
const interfaces = await si.networkInterfaces();
Inside an electron app (using vue-cli)
Error log: /bin/sh: ifconfig: command not found

Current Output
Empty array
Expected behavior
Array of network interfaces
Environment (please complete the following information):

systeminformation package version: 4.16.0
OS: macOS
Hardware MacBook Pro 2017

Additional context
I created a PR #312 that fixes this problem by including /sbin/ in the command like it is done at the other places in the code where ifconfig is called.

@OhKai fixed... Version 4.16.1 just released


NEPSE API Change

Nepse has changed its API to POST request with the payload of:
{"id": 326}

So many methods like get_company_detailed, get_company_live_data etc are broken.

Update:
The payload is being changed every time I try to fetch the data from NEPSE Site for every company. Am trying to figure out how they are getting those ids, cause there must be some way. WIll try to spoof the headers and have random ids as well.

Fixed it, as the payload's id stabilized to 281

Update:
The API's payload is again changing randomly and I need to figure out a solution. In the meantime don't use get_company_detailed, get_company_live_price, and use get_company instead

Fixed half in the pull request #30 , new mappings yet to be added

Pull request #32 adds new missing mappings.
Thanks to @avignya for the contribution


shellcheck not found on M1 Mac

I'm getting this error when I open a shell script:

The shellcheck program was not found (not installed?). Use the 'shellcheck.executablePath' setting to configure the location of 'shellcheck'

I have shellcheck installed via Homebrew:
% which shellcheck
/opt/homebrew/bin/shellcheck

Poking around a bit, I found what looks like the relevant source:
https://github.com/timonwong/vscode-shellcheck/blob/3a803d31912b863985405da042339db98fda0c56/src/linter.ts#L136
https://github.com/timonwong/vscode-shellcheck/blob/3a803d31912b863985405da042339db98fda0c56/src/linter.ts#L199
From that, I can see that there isn't a binary for the M1 architecture:
% tree ~/.vscode/extensions/timonwong.shellcheck-0.14.1/binaries
/Users/bhrutledge/.vscode/extensions/timonwong.shellcheck-0.14.1/binaries
├── darwin
│   └── x64
│       └── shellcheck
├── linux
│   ├── arm
│   │   └── shellcheck
│   ├── arm64
│   │   └── shellcheck
│   └── x64
│       └── shellcheck
└── win32
    └── x32
        └── shellcheck.exe

Still, I would have expected the default of shellcheck to work. I thought it might be related to my runtime PATH not being set properly, but looking at process.env.PATH from the VS Code Developer Tools shows that it includes /opt/homebrew/bin.
Of course, this is a minor annoyance, because I can set it manually, but it'd be nice if it just worked. 😄

Did you add shellcheck to shellcheck.executablePath?

Yep, setting "shellcheck.executablePath": "/opt/homebrew/bin/shellcheck" works as expected. I just thought this extension might discover it automatically if it was in my $PATH, since it looks like that's what the code is intended to do.
For reference, here's the issue for an M1 build of shellcheck: https://github.com/koalaman/shellcheck/issues/2109. As I noted in a comment just now, it's installable natively with Homebrew (as of a couple days ago), so hopefully the shellcheck folks will release an official build.

Did you try "shellcheck.executablePath": "shellcheck"?

Ah, yes, that works too.

But your complain is still valid, the extension should properly find it automatically when the bundled one is not found. I'm going to check.

@bhrutledge when possible please test this new version to confirm it fixes your issue.

Yep! Thank you!

@lu-yanda what's this hook, man? Seems like the extension is trying to use this hook (check your vscode settings), and the hook can't find shellcheck installed.

this is still an issue on Sonoma on apple silicon


Fix unlisted bug in std.typecons.Scoped.  writeln() has no place in prod...

...uction code in these cases and wasn't properly imported either.

Hrm.. any reason that's not just:  @disable this(this);
(ie, no body)

I don't know what the current status is but @disable was at one point buggy.  I think until it's thoroughly debugged it's a good practice to put an assert(false) in there to expose compiler bugs.

@disable can be as buggy as it want to be but body-less function will generate CT error and your approach will not. @braddr's approach should be used.


replace tiller grpc api error with grpc.Status

fix #2894

I'm not as familiar with the grpc side of things in tiller, but from what I recall Kubernetes is on an older version of grpc (1.2.1) hence why we need to stick with that.
Anyone else more familiar on why we're still using 1.2.1 or are we good to move forward with 1.3.0? If that's the case maybe we should bump this all the way up to v1.6.0.

I think most of our gRPC is just from the tiller side, I don't know if there is a transitive dependency problem though. @weiwei04 what k8s versions did you test this against?

I've deployed this modified tiller on our 1.7.3 kubernetes cluster :)

@weiwei04 Have you tried with the most up-to-date version of grpc? I agree with @bacongobbler that if we are going through the trouble of upgrading it, we may as well upgrade it all the way

/remove-lifecycle stale
/lifecycle frozen

As per the announcement on the mailing list, Helm 2.15.0 is the last release where we will be merging new features for Helm 2. Because of that, I'm closing this PR due to inactivity. Since the gRPC API has been removed as part of Tiller's removal in Helm 3, it doesn't appear to make sense to port this over to Helm 3. Thanks!


Add a public function that can be used to test macro expansions

Testing macros should be as easy as possible and we should thus make the  assertMacroExpansion function public.
While making the function public, I made the following changes:

Changed diagnosticMessages to expect DiagnsoticSpec similar to the parser tests. The only difference is that they take line and columns instead of location markers because the location markers have a slighgly high learning curve IMO.

Slightly unrelated, I also made the following changes:

Made a few minor improvements to SwiftParserTest/Assertions.swift
Changed FixIt.message to return a String instead of FixItMessage to match Diagnostic and Note
Fixed a bug in MacroApplication where the wrong syntax node was passed as the node parametertoaddDiagnostics`, leading to a highlight that was bigger than expected.

@swift-ci Please test

@swift-ci Please test macOS

@swift-ci Please test Windows

@swift-ci Please test macOS

@swift-ci Please test

@swift-ci Please test Linux

@swift-ci Please test Windows

@swift-ci Please test

@swift-ci Please test Windows

Note to self: This requires the BasicFormat improvements I’m merging in other PRs.

@swift-ci Please test

@swift-ci Please test Windows


trajectory model training

I am trying to use this training frame to train a baseline trajectory model (predict root node camera space position). It works but loss seems weird: the test MPJPE is always around 110.
Is there anything I miss? Have you tried train any trajectory model for PoseAug model?

Hi, thank you for the interest.
No, I didn't try trajectory model in single frame setting.
The VideoPose3D provide trajectory model for multi-frame setting, and I used it in PoseTriplet.

Thank you for your reply.
The single frame traj model from VideoPose3D (test MPJPE around 110) for Poseaug works pretty well! It just weird that test mpjpe is such high.


Suggestion: Allow comments

It'd be great if we could include comments in the broom files so that we can remember why we hide a file.
Any way you would filter the rules list to remove lines starting with '#'?
This changed is what worked for me.
https://github.com/mihaifm/broom/blob/786e81ac3380ffd318f2e13fd727cde291da54ba/mo2/Broom.py#L111-L116
Changed to this
globalRules = "\n".join(
    filter(
        lambda x: len(x) > 0,
        map(lambda x: x.strip(), [l for l in globalRules.splitlines() if not l.startswith('#')]),
    )
)

Comments are now supported in the latest release,
It took some time to release a new version, but I also added a feature to negate rules with "!", similar to what gitignore does.
Thanks for the help again.


Support DateTime64 param types in expressions

This PR fixes a bug we encountered where queries containing elixir DateTime params with sub-second granularity failed with DB::Exception errors.
I believe this bug is caused because the ch driver (reasonably) encodes these DateTimes to floats, but the ecto_ch adapter casts them to clickhouse's DateTime type rather than DateTime64. Only DateTime64 can parse floats.
The fix mirrors the ch driver's encoding logic.
Here's a redacted example query log before the fix:
[debug] QUERY ERROR source="api_logs" db=2.7ms idle=1921.4ms
SELECT ... FROM "api_logs" AS a0 WHERE ... AND (a0."inserted_at" >= {$1:DateTime}) AND (a0."inserted_at" < {$2:DateTime}) ORDER BY a0."inserted_at" DESC LIMIT {$3:Int64} [..., ~U[2023-11-13 22:19:05.146974Z], ~U[2023-12-13 22:19:05.146974Z], 26]

** (exit) an exception was raised:
    ** (Ch.Error) Code: 457. DB::Exception: Value<PHONE_NUMBER>.533782 cannot be parsed as DateTime for query parameter '$1' because it isn't parsed completely: only 10 of 17 bytes was parsed:<PHONE_NUMBER>. (BAD_QUERY_PARAMETER) (version <IP_ADDRESS> (official build))

And here's an example with the patch in place
[debug] QUERY OK source="api_logs" db=6.2ms decode=0.2ms idle=1783.0ms
SELECT ... FROM "api_logs" AS a0 WHERE ... AND (a0."inserted_at" >= {$1:DateTime64}) AND (a0."inserted_at" < {$2:DateTime64}) ORDER BY a0."inserted_at" DESC LIMIT {$3:Int64} [..., ~U[2023-11-13 22:21:36.779992Z], ~U[2023-12-13 22:21:36.779992Z], 26]

I briefly looked into adding tests but I think I'll need guidance from the repo maintainer on the best way to add tests. My plan is to merge without additional tests, point our application at this fork, then open a PR upstream and start a conversation with the repo maintainer(s).
Let me know what you think. I'm happy to make any changes and/or add more tests - I wasn't sure exactly where any new test cases should live. Note that I modified an existing test case - imo that test case had a bug - DateTime.utc_now() returns a datetime with microseconds, which ch will encode into a float. I'm relatively new to elixir/ecto/clickhouse though and may have misunderstood something - super open to feedback.
Thanks!
Reference:
https://clickhouse.com/docs/en/sql-reference/data-types/datetime64
https://clickhouse.com/docs/en/sql-reference/data-types/datetime

The CI fails due to some formatting issues, should be fixed in https://github.com/knocklabs/ecto_ch/pull/2 :)

@ruslandoga, I've merged that PR :)

@vlymar thank you! Merged. I'll cut a release tomorrow if it's OK :)

@ruslandoga absolutely!

I've released v0.3.2 which includes the fix: https://diff.hex.pm/diff/ecto_ch/0.3.1..0.3.2
Thank you!


update env and add commit id to version

update env dependence
add commit id to version message, like this:

$ cita-cli -V
cita-cli 0.18.0+08f9cfb926683ab6c750ca477e47d9e6ba442db9

https://github.com/cryptape/cita-common/blob/develop/util/src/build_info.rs#L68-L86
参考下这个函数，信息量更丰富

I think cli doesn't need so much information, as long as I can find the commit id.

@yangby-cryptape What's your opinion?


interactive bots: Create Giveaway bot by dob9601.

Automated message from Dropbox CLA bot
@dob9601, it looks like you've already signed the Dropbox CLA. Thanks!

Hi @dob9601!
Thanks for working on this!
I haven't tested the bot manually yet, since there are some issues I've noticed without running it and are pretty quick to fix:

Your code is failing Travis at the moment, due to linter errors - could you run ./tools/lint-all --pep8 locally to catch all the pep8 rules errors and fix them?
Your docs.md file is not rendering properly, since it's an .md file. Could you make sure it's readable as an .md file, using a Markdown preview to help you figure out some possible issues?
We tend to use American spelling in Zulip. It's a bit awkward to read when the spelling doesn't match in the codebase and docs.

Could you fix those before resubmitting?

Sure, no worries. I wasn't expecting a task like this to go through first time. This was more of a 'show the concept works' thing @trueskawka

@dob9601, looks cool. You need to remove all those extra commits.

@umairwaheed sorry, having to give up on this task as I have important exams coming up soon which require more focus than google code in.

Hi @dob9601!
Will you be willing to pick it up in the future, not necessarily as a GCI task? It's a cool bot :)

I would love to @trueskawka
my mocks are almost finished now so I'll try to finish this one then i may try to start working on another bot in the future :)

Closing.  This can be reopened if there is follow-up.


since last Update no connection to booth Ideal LED possible

as i wrote i had also no connection any more to my  two Ideal LED Christmas / Partlights.

Could you help? Any idea what is reason for?
Thanks

When did you update, and what did you update?  Was it all of HA or just the iDeal integration?
Do I understand correctly; things were working fine and then you updated and they broke?
Please can you:

Delete the device
Enable debugging
Try and add the device again
Turn off debugging again and attach the logs here?

I was a bluetooth problem by my side.


Duplicate class bcprov-jdk15on-1.70.jar  bcprov-jdk15to18-1.70.jar

Build/Submit details page URL
No response
Summary
1 WARNING: The option setting 'android.jetifier.ignorelist=bcprov' is experimental.
2 WARNING: The option setting 'android.jetifier.ignorelist=bcprov-jdk15on-1.70.jar' is experimental.
3 WARNING: The option setting 'android.jetifier.ignorelist=bcprov-jdk15to18-1.70' is experimental.
all error  as next ,and can`t build to success
 Duplicate class org.bouncycastle.jce.spec.ElGamalParameterSpec found in modules bcprov-jdk15on-1.70.jar -> bcprov-jdk15on-1.70 (org.bouncycastle:bcprov-jdk15on:1.70) and bcprov-jdk15to18-1.70.jar -> bcprov-jdk15to18-1.70 (org.bouncycastle:bcprov-jdk15to18:1.70)

 Go to the documentation to learn how to Fix dependency resolution errors.

Try:

Run with --stacktrace option to get the stack trace.

Run with --info or --debug option to get more log output.

Run with --scan to get full insights.
Get more help at https://help.gradle.org.
BUILD FAILED in 12m 51s
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.6/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
1474 actionable tasks: 1474 executed
Error: Gradle build failed with unknown error. See logs for the "Run gradlew" phase for more information.

Managed or bare?
android
Environment
package.json
{
"name": "expo",
"version": "1.0.0",
"scripts": {
"start": "expo start --dev-client",
"startTest": "NODE_ENV=test npx expo start",
"android": "expo run:android",
"ios": "expo run:ios",
"web": "expo start --web"
},
"dependencies": {
"@ant-design/icons-react-native": "^2.3.2",
"@ant-design/react-native": "^5.1.3",
"@babel/preset-env": "^7.1.6",
"@expo/config-plugins": "~8.0.0",
"@expo/status-bar-height": "^0.0.1",
"@kafudev/react-native-vconsole": "^0.1.11",
"@react-native-async-storage/async-storage": "^1.23.1",
"@react-native-community/masked-view": "^0.1.10",
"@react-native-community/netinfo": "11.3.1",
"@react-native-community/segmented-control": "^2.2.2",
"@react-native-community/slider": "4.5.2",
"@react-native-picker/picker": "2.7.5",
"@react-navigation/bottom-tabs": "^6.5.20",
"@react-navigation/native": "^6.1.17",
"@react-navigation/native-stack": "^6.9.26",
"bignumber.js": "^9.1.2",
"crypto-js": "4.2.0",
"expo": "^51.0.18",
"expo-build-properties": "^0.12.3",
"expo-camera": "~15.0.13",
"expo-clipboard": "^6.0.3",
"expo-device": "^6.0.2",
"expo-document-picker": "~12.0.2",
"expo-file-system": "~17.0.1",
"expo-font": "^12.0.7",
"expo-image-picker": "~15.0.7",
"expo-status-bar": "~1.12.1",
"expo-system-ui": "~3.0.7",
"expo-updates": "~0.25.18",
"hermes-engine": "^0.11.0",
"metro": "~0.80.8",
"metro-config": "~0.80.8",
"metro-resolver": "~0.80.8",
"mobx": "^6.0.3",
"mobx-persist": "^0.4.1",
"mobx-react-lite": "^4.0.7",
"mobx-utils": "^6.0.3",
"moment": "^2.29.1",
"prettier": "2.8.8",
"prop-type": "0.0.1",
"prop-types": "^15.7.2",
"react": "18.2.0",
"react-native": "0.74.3",
"react-native-autolink": "^4.2.0",
"react-native-background-timer": "^2.4.1",
"react-native-confirmation-code-field": "^7.4.0",
"react-native-dropdown-picker": "^5.4.6",
"react-native-extended-stylesheet": "^0.12.0",
"react-native-extra-dimensions-android": "1.2.5",
"react-native-fast-image": "^8.6.3",
"react-native-gesture-handler": "~2.16.1",
"react-native-get-random-values": "^1.11.0",
"react-native-gradients": "^2.1.1",
"react-native-image-picker": "^7.1.2",
"react-native-image-zoom-viewer": "^3.0.1",
"react-native-keyboard-spacer": "^0.4.1",
"react-native-linear-gradient": "^2.5.6",
"react-native-modalize": "^2.0.6",
"react-native-qrcode-svg": "^6.3.1",
"react-native-reanimated": "3.10.1",
"react-native-safe-area-context": "4.10.1",
"react-native-screens": "3.31.1",
"react-native-sensitive-info": "^5.5.8",
"react-native-spinner-button": "^1.0.3",
"react-native-svg": "14.1.0",
"react-native-svg-transformer": "^1.4.0",
"react-native-swipeout": "^2.3.6",
"react-native-tcp-socket": "^6.0.6",
"react-native-video": "^6.1.2",
"react-native-webview": "13.8.6",
"react-test-renderer": "18.0.0",
"rn-overlay": "^0.4.0",
"toggle-switch-react-native": "^3.3.0",
"typescript": "5.3.3",
"without-props": "^1.0.1",
"xlsx": "^0.18.5"
},
"devDependencies": {
"@babel/core": "^7.20.0",
"@babel/plugin-proposal-decorators": "^7.12.1",
"@babel/runtime": "^7.12.5",
"@react-native-community/eslint-config": "^3.2.0",
"babel-eslint": "^10.1.0",
"babel-jest": "^29.7.0",
"babel-plugin-import": "^1.13.8",
"eslint": "^8.57.0",
"eslint-plugin-react": "^7.34.2",
"eslint-plugin-react-hooks": "^4.2.0",
"eslint-plugin-react-native": "^4.1.0",
"jest": "^29.4.0",
"metro-react-native-babel-preset": "^0.77.0"
},
"resolutions": {
"react-native-reanimated": "~3.10.1"
},
"jest": {
"preset": "react-native"
},
"private": true
}
app.json
{
"expo": {
"name": "expo",
"slug": "qt",
"version": "1.0.0",
"orientation": "portrait",
"icon": "./assets/icon.png",
"userInterfaceStyle": "automatic",
"splash": {
"image": "./assets/splash.png",
"resizeMode": "contain",
"backgroundColor": "#ffffff"
},
"ios": {
"supportsTablet": true,
"usesIcloudStorage": true,
"bundleIdentifier": "com.qinglong.qwallet",
"infoPlist": {
"NSCameraUsageDescription": "This app uses the camera to scan barcodes on event tickets.",
"CFBundleAllowMixedLocalizations": true,
"EXUpdatesCheckOnLaunch": "NEVER",
"NSAppTransportSecurity": {
"NSAllowsArbitraryLoads": true,
"NSAllowsLocalNetworking": true,
"NSExceptionDomains": {
"<IP_ADDRESS>": {
"NSIncludesSubdomains": true,
"NSTemporaryExceptionAllowsInsecureHTTPLoads": true,
"NSTemporaryExceptionMinimumTLSVersion": "TLSv1.1"
}
}
}
},
"buildNumber": "19"
},
"android": {
"adaptiveIcon": {
"foregroundImage": "./assets/adaptive-icon.png",
"backgroundColor": "#ffffff"
},
"package": "com.qinglong.qwallet",
"permissions": [
"android.permission.CAMERA",
"android.permission.RECORD_AUDIO",
"android.permission.READ_EXTERNAL_STORAGE",
"android.permission.WRITE_EXTERNAL_STORAGE"
],
"versionCode": 70
},
"web": {
"favicon": "./assets/favicon.png"
},
"extra": {
"eas": {
"projectId": "0160f9bb-8641-49be-bb60"
}
},
"runtimeVersion": {
"policy": "appVersion"
},
"updates": {
"fallbackToCacheTimeout": 0,
"checkAutomatically": "ON_ERROR_RECOVERY",
"url": "https://u.expo.dev/0160f9bb-8641-49be-bb60"
},
"plugins": [
[
"./withModifyGradle.js"
],
[
"expo-build-properties",
{
"android": {
"usesCleartextTraffic": true
}
}
],
[
"expo-camera",
{
"cameraPermission": "Allow $(PRODUCT_NAME) to access your camera",
"microphonePermission": "Allow $(PRODUCT_NAME) to access your microphone",
"recordAudioAndroid": true
}
],
[
"expo-document-picker",
{
"iCloudContainerEnvironment": "Production"
}
],
[
"expo-image-picker",
{
"photosPermission": "The app accesses your photos to let you share them with your friends.",
"cameraPermission": "Allow $(PRODUCT_NAME) to open the camera",
"microphonePermission": false
}
]
],
}
}
Error output
Running 'gradlew :app:assembleRelease' in /home/expo/workingdir/build/android
Welcome to Gradle 8.6!
Here are the highlights of this release:

Configurable encryption key for configuration cache
Build init improvements
Build authoring improvements
For more details see https://docs.gradle.org/8.6/release-notes.html
To honour the JVM settings for this build a single-use Daemon process will be forked. For more on this, please refer to https://docs.gradle.org/8.6/userguide/gradle_daemon.html#sec:disabling_the_daemon in the Gradle documentation.
Daemon will be stopped at the end of the build
Path for java installation '/usr/lib/jvm/openjdk-17' (Common Linux Locations) does not contain a java executable

Task :expo-updates-gradle-plugin:checkKotlinGradlePluginConfigurationErrors
Task :gradle-plugin:checkKotlinGradlePluginConfigurationErrors
Task :expo-updates-gradle-plugin:pluginDescriptors
Task :expo-updates-gradle-plugin:processResources
Task :gradle-plugin:pluginDescriptors
Task :gradle-plugin:processResources
Task :gradle-plugin:compileKotlin
Task :gradle-plugin:compileJava
NO-SOURCE
Task :gradle-plugin:classes
Task :gradle-plugin:jar
Task :expo-updates-gradle-plugin:compileKotlin
Task :expo-updates-gradle-plugin:compileJava NO-SOURCE
Task :expo-updates-gradle-plugin:classes
Task :expo-updates-gradle-plugin:jar
Configure project :app
WARNING: The option setting 'android.jetifier.ignorelist=bcprov' is experimental.
ℹ  Applying gradle plugin 'expo-updates-gradle-plugin'<EMAIL_ADDRESS>Configure project :expo
Using expo modules

expo-asset (10.0.10)
expo-camera (15.0.13)
expo-clipboard (6.0.3)
expo-constants (16.0.2)
expo-device (6.0.2)
expo-document-picker (12.0.2)
expo-eas-client (0.12.0)
expo-file-system (17.0.1)
expo-font (12.0.8)
expo-image-loader (4.7.0)
expo-image-picker (15.0.7)
expo-json-utils (0.13.1)
expo-keep-awake (13.0.2)
expo-manifests (0.14.3)
expo-modules-core (1.12.19)
expo-structured-headers (3.8.0)
expo-system-ui (3.0.7)
expo-updates (0.25.19)

Configure project :react-native-reanimated
Android gradle plugin: 8.2.1
Gradle: 8.6
Configure project :react-native-video
useExoplayerIMA: false
useExoplayerSmoothStreaming: true
useExoplayerDash: true
useExoplayerHls: true
useExoplayerRtsp: false
buildFromSource: false
Path for java installation '/usr/lib/jvm/openjdk-17' (Common Linux Locations) does not contain a java executable
Checking the license for package Android SDK Platform 33 in /home/expo/Android/Sdk/licenses
License for package Android SDK Platform 33 accepted.
Preparing "Install Android SDK Platform 33 (revision 3)".

Task :react-native-community_slider:copyReleaseJniLibsProjectAndLocalJars
Task :react-native-community_slider:extractDeepLinksForAarRelease
Task :react-native-community_slider:extractReleaseAnnotations
Task :react-native-community_slider:mergeReleaseGeneratedProguardFiles
Task :react-native-community_slider:mergeReleaseConsumerProguardFiles
Task :react-native-community_slider:mergeReleaseShaders
Task :react-native-community_slider:compileReleaseShaders NO-SOURCE
Task :react-native-community_slider:generateReleaseAssets UP-TO-DATE
Task :react-native-community_slider:packageReleaseAssets
Task :react-native-community_slider:prepareLintJarForPublish
Task :react-native-community_slider:prepareReleaseArtProfile
Task :app:lintVitalRelease
Task :app:checkReleaseDuplicateClasses FAILED
Task :app:dexBuilderRelease
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:checkReleaseDuplicateClasses'.

A failure occurred while executing com.android.build.gradle.internal.tasks.CheckDuplicatesRunnable
Duplicate class org.bouncycastle.LICENSE found in modules bcprov-jdk15on-1.70.jar -> bcprov-jdk15on-1.70 (org.bouncycastle:bcprov-jdk15on:1.70) and bcprov-jdk15to18-1.70.jar -> bcprov-jdk15to18-1.70 (org.bouncycastle:bcprov-jdk15to18:1.70)
Duplicate class org.bouncycastle.asn1.ASN1ApplicationSpecific found in modules bcprov-jdk15on-1.70.jar -> bcprov-jdk15on-1.70 (org.bouncycastle:bcprov-jdk15on:1.70) and bcprov-jdk15to18-1.70.jar -> bcprov-jdk15to18-1.70 (org.bouncycastle:bcprov-jdk15to18:1.70)
Duplicate class org.bouncycastle.asn1.ASN1ApplicationSpecificParser found in modules bcprov-jdk15on-1.70.jar -> bcprov-jdk15on-1.70 (org.bouncycastle:bcprov-jdk15on:1.70) and bcprov-jdk15to18-1.70.jar -> bcprov-jdk15to18-1.70 (org.bouncycastle:bcprov-jdk15to18:1.70)

 Go to the documentation to learn how to Fix dependency resolution errors.

Try:

Run with --stacktrace option to get the stack trace.

Run with --info or --debug option to get more log output.

Run with --scan to get full insights.
Get more help at https://help.gradle.org.
BUILD FAILED in 12m 51s
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.6/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
1474 actionable tasks: 1474 executed
Error: Gradle build failed with unknown error. See logs for the "Run gradlew" phase for more information.

Reproducible demo or steps to reproduce from a blank project
a

const { withGradleProperties } = require('@expo/config-plugins');
module.exports = (config, customName) => {
return withGradleProperties(config, async config => {
config.modResults.push({
key: 'android.jetifier.ignorelist',
value: 'bcprov', // unable
type: 'property',
});
config.modResults.push({
key: 'android.jetifier.ignorelist',
value: 'bcprov-jdk15to18-1.70.jar', // unable
type: 'property',
});
config.modResults.push({
key: 'android.jetifier.ignorelist',
value: 'bcprov-jdk15on-1.70.jar', // unable
type: 'property',
});
config.modResults.push({
key: 'android.jetifier.ignorelist',
value: 'org.bouncycastle.*', // unable
type: 'property',
});
config.modResults.push({
  key: 'android.enableJetifier',
  value: true,
  type: 'property',
});

// /// Use the plugin
// module.exports = withJetifierIgnoring;


[POC] feat(*): refactor deisrel for checking component versions

@jchauncey
This is a POC refactor for a new deisrel
GH_TOKEN=<optional> deisrel <path to generate_params.toml>
workflowManager v2.2.0 -> v2.2.0 (clean)
fluentd v2.2.0 -> v2.2.0 (clean)
router v2.2.0 -> v2.2.0 (clean)
slugbuilder v2.2.0 -> v2.2.0 (clean)
builder v2.2.0 -> v2.2.0 (dirty)
	builder has unrelased changes. See https://github.com/deis/builder/compare/v2.2.0...master
registry v2.2.0 -> v2.2.0 (clean)
nsqd v2.2.0 -> v2.2.0 (clean)
database v2.2.0 -> v2.2.0 (clean)
loggerRedis v2.2.0 -> v2.2.0 (clean)
dockerbuilder v2.2.0 -> v2.2.0 (clean)
influxdb v2.2.0 -> v2.2.0 (clean)
grafana v2.2.0 -> v2.2.0 (clean)
telegraf v2.2.0 -> v2.2.0 (clean)
minio v2.2.0 -> v2.2.0 (clean)
controller v2.2.0 -> v2.2.0 (clean)
logger v2.2.0 -> v2.2.0 (clean)
slugrunner v2.2.0 -> v2.2.0 (clean)

This is super basic right now, but if there is sufficient interest I can add tests.
For easier reviewing, I'd just browse the files rather than look at the diff.

List is missing redis but other than that this looks really good

It's called loggerRedis because that is the name of the component in the manifest. I could add "clean" names to every component, but that would be a more significant abstraction.
Right now the list of components is a map[string][]string, because a repository can have multiple components.

nope thats fine i just didnt notice it. =)

can we sort them in alphabetical order

can we do a table alignment on the output to so it lines up?

@jchauncey Output is now alphabeticalyized and aligned. 💥

This is bad ass

:boom:

I refactored the command line parsing stuff in urfave/cli and added support for json output. Next up: support pulling list repositories from file and write tests for it all.

deisrel now takes a second argument, a json file in the format of map[string][]string that is used to supply the repository->component mapping.

I updated the readme. The only thing I could do still is write tests. The problem is that the only way to test is to use `httptest

Is it worth putting in the time to write these tests?

I think not for an internal tool such as this. I've tested this PR by hand and it works as advertised--although I did eventually get some GitHub rate-limiting warnings.
I only want to make sure we're not throwing away too much legacy code here. For example, I don't know if deisrel helm-stage is still relevant. Otherwise this is LGTM 💯 .

I think not for an internal tool such as this. I've tested this PR by hand and it works as advertised--although I did eventually get some GitHub rate-limiting warnings.

You can use a GH oauth token set to $GH_TOKEN.

I only want to make sure we're not throwing away too much legacy code here. For example, I don't know if deisrel helm-stage is still relevant.

I overlooked the fact that changelogs was still necessary, so I'm re-adding that. I'll take a look at deisrel helm-stage but the good news is that they are still in git history, so it's not to difficult to revive older commands if need be.

token set to $GH_TOKEN to avoid those.

Oh, I  only had GITHUB_ACCESS_TOKEN set. Works great with GH_TOKEN though.

I updated this PR to re-add deis changelogs.

This is great work (also love seeing code get ripped out!) but wondering where information needs to live around how exactly one would use the clean/dirty version output produced by deisrel.  This isn't mentioned in the README here, nor can I find evidence of it in the related docs PR https://github.com/deis/workflow/pull/410.  Thoughts @Joshua-Anderson @mboersma ?

@vdiceThe main intention of `clean/dirty

@Joshua-Anderson thanks, that makes sense.  I'll make a comment on https://github.com/deis/workflow/pull/410 requesting the addition of that info in the release process.

@vdice I'm going to merge deis/workflow#410 and then make an update PR after this merges, if that's ok. Also I'll review this. 😄

I noticed this when rebuilding deisrel on this PR:
$ make boostrap
...
[WARN]	Lock file may be out of date. Hash check of YAML failed. You may need to run 'update'

Not a blocker, but maybe we should regenerate the lockfile in this or a separate PR.

I regenerated the lockfile!


building library with examples

I have a simple library (say mylib.ml) and also want to compile an example of it's usage (say myex.ml).
Trying something like:
(jbuild_version 1)

(library
  ((name mylib)
))

(executable
             ((name example)
             (libraries (batteries))
             ))

gives an error: Multiple rules generated for _build/default/mylib.o.
How can I build something like this?

I'm not 100% certain about the jbuilder rules here, but you may need to put the example in its own directory with its own jbuild file.

The top level package is the library I am trying to build. If I put examples in sub-package under it they would need to depend on the library (parent package). I am not sure that would work....

This is not a bug or issue with Jbuilder - questions like this would be better posted on the OCaml Discuss forum, so please continue the discussion there if necessary. It's not a problem to answer them here, but there are more Jbuilder users on Discuss than there are developers monitoring the issue tracker.
The problem here is that your jbuild files lacks modules fields so both the library and the executable include mylib.ml. The error message could be clearer, but this is already a known problem. @hcarty is correct that putting the library and example in separate directories would solve the problem (and I'll come on to your comment about referring to the parent package shortly).
You cannot have an executable example defined in myex.ml, so correcting two bits of the jbuild file so far:

(jbuild_version 1)

(library
  ((name mylib)
   (modules (mylib))
))

(executable
             ((name examplemyex)
             (libraries (batteries))
             (modules (myex))
             ))

You can now run jbuilder build myex.exe and you will get an error about Mylib not being found. Regardless of whether you put the example in a separate directory with its own jbuild file or keep it in the current directory, you must refer to it in the libraries field of the executable stanza - i.e. you need mylib with batteries.
Note also that you're defining a library mylib and having a single module mylib.ml is probably not the effect you want. Here, for a toy example, you probably want to add (wrapped false) to your library stanza or if you add another module to your library you're going to get a surprise when that module is inaccessible from the example. Without (wrapped false) Jbuilder emulates namespaces for libraries. Suppose you have two files bar.ml and baz.ml, then this:
(library
  ((name foo)
   (modules (bar baz))))

creates a library where the modules are referred to as Foo.Bar and Foo.Baz. If you also provide foo.ml and include that in the modules field (which is effectively what you've done above) then this allows you to control which modules are exported, for example, foo.ml could contain:
module Bar = Foo__Bar

at which point the module Baz becomes internal to your library.


feat: added mouse inputs

@NEARworld thanks for this! Looks good except I think it's better to rename the functions to camelCase to better match AssemblyScript styling. What do you think?

@NEARworld thanks for this! Looks good except I think it's better to rename the functions to camelCase to better match AssemblyScript styling. What do you think?

Yes I agree! I will change it.


When User tries to edit Ellipse using diagonal dots - Figure becomes shifted

Affected Version: Remote
Steps to Reproduce:

Launch Ketcher.
Draw an Ellipse using 'Shape Ellipse' tool.
Click on Ellipse line.
Drag and drop diagonal dot to change the Ellipse size.

Expected Result:
Ellipse is edited correctly.
Actual Result:
Ellipse is shifted when User clicks on diagonal dot and starts resize.

Issue is related to https://github.com/epam/ketcher/issues/85
Need discussion with @ensemenova


[MIST-1158] Fix scaling in tasks is triggered only once

This PR closes #1158 via

Fix auto-scaling is triggered only once by using scheduleAtFixedRate().

LGTM. I will merge it


[Bug]: "waiting for the k3s server to start"

Description
EDIT: This is actually a duplicate, see: https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner/issues/1145#issuecomment-1875459438
Provisioning the servers using terraform apply does not work unfortunately:
module.kube-hetzner.null_resource.first_control_plane: Still creating... [2m20s elapsed]
module.kube-hetzner.null_resource.first_control_plane (remote-exec): Job for k3s.service failed because the control process exited with error code.
module.kube-hetzner.null_resource.first_control_plane (remote-exec): See "systemctl status k3s.service" and "journalctl -xeu k3s.service" for details.
module.kube-hetzner.null_resource.first_control_plane (remote-exec): Waiting for the k3s server to start...
╷
│ Error: remote-exec provisioner error
│
│   with module.kube-hetzner.null_resource.first_control_plane,
│   on .terraform/modules/kube-hetzner/init.tf line 73, in resource "null_resource" "first_control_plane":
│   73:   provisioner "remote-exec" {
│
│ error executing "/tmp/terraform_2100530671.sh": Process exited with status 124

Investigating the control planes journal yields:
Jan 04 20:10:19 k3s-control-plane-ads systemd[1]: Starting Lightweight Kubernetes...
Jan 04 20:10:19 k3s-control-plane-ads sh[1982]: + /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service
Jan 04 20:10:19 k3s-control-plane-ads (k3s)[1988]: k3s.service: Failed to locate executable /usr/local/bin/k3s: Permission denied
Jan 04 20:10:19 k3s-control-plane-ads (k3s)[1988]: k3s.service: Failed at step EXEC spawning /usr/local/bin/k3s: Permission denied
Jan 04 20:10:19 k3s-control-plane-ads systemd[1]: k3s.service: Main process exited, code=exited, status=203/EXEC
Jan 04 20:10:19 k3s-control-plane-ads systemd[1]: k3s.service: Failed with result 'exit-code'.

Although:
k3s-control-plane-ads:~ # stat -c "%U %G" /usr/local/bin/k3s
root root

Manual run works fine:
k3s-control-plane-ads:~ # /usr/local/bin/k3s server
INFO[0000] Starting k3s v1.28.5+k3s1 (5b2d1271)
INFO[0000] Managed etcd cluster initializing
...

Thank you alot for your efforts!
Kube.tf file
I only modified the nodepool settings:

control_plane_nodepools = [
    {
      name        = "control-plane",
      server_type = "cax11",
      location    = "fsn1",
      labels      = [],
      taints      = [],
      count       = 3
      # swap_size   = "2G" # remember to add the suffix, examples: 512M, 1G
      # zram_size   = "2G" # remember to add the suffix, examples: 512M, 1G
      # kubelet_args = ["kube-reserved=cpu=250m,memory=1500Mi,ephemeral-storage=1Gi", "system-reserved=cpu=250m,memory=300Mi"]

      # Enable automatic backups via Hetzner (default: false)
      # backups = true
    }
  ]

  agent_nodepools = [
    {
      name        = "agent-medium",
      server_type = "cax21",
      location    = "fsn1",
      labels      = [],
      taints      = [],
      count       = 2
      # swap_size   = "2G" # remember to add the suffix, examples: 512M, 1G
      # zram_size   = "2G" # remember to add the suffix, examples: 512M, 1G
      # kubelet_args = ["kube-reserved=cpu=50m,memory=300Mi,ephemeral-storage=1Gi", "system-reserved=cpu=250m,memory=300Mi"]

      # Enable automatic backups via Hetzner (default: false)
      # backups = true
    }
  ]

Screenshots
No response
Platform
WSL

Some digging with the help of almighty ChatGPT revealed an issue related to SELinux.
k3s-control-plane-1-myr:~ # sudo ausearch -m AVC -ts recent | grep k3s
type=AVC msg=audit(1704401173.178:542): avc:  denied  { execute } for  pid=2234 comm="(k3s)" name="k3s" dev="sda3" ino=279 scontext=system_u:system_r:init_t:s0 tcontext=unconfined_u:object_r:user_tmp_t:s0 tclass=file permissive=0
type=AVC msg=audit(1704401178.471:544): avc:  denied  { execute } for  pid=2251 comm="(k3s)" name="k3s" dev="sda3" ino=279 scontext=system_u:system_r:init_t:s0 tcontext=unconfined_u:object_r:user_tmp_t:s0 tclass=file permissive=0
type=AVC msg=audit(1704401183.721:546): avc:  denied  { execute } for  pid=2264 comm="(k3s)" name="k3s" dev="sda3" ino=279 scontext=system_u:system_r:init_t:s0 tcontext=unconfined_u:object_r:user_tmp_t:s0 tclass=file permissive=0
...

Running sudo restorecon -v /usr/local/bin/k3s allowed me to get past the issue on this control plane...

After running sudo restorecon -v /usr/local/bin/k3s on all machines deployment works!

I'm observing the same issue. Fixing this once might be fine but I presume the issue will come up if there is an automated upgrade of a node?

Today 2 k3s nodes got status not Ready, reboot not helped.
I made rollback system snaphot to 1 day ago use snapper rollback. After start k3s node comeback to status Ready.
rebuild Suse MicroOs  and try add new k3s node, but not success with same errors:
module.kube-hetzner.null_resource.agents["2-2-bots-large"]: Still creating... [2m10s elapsed]
module.kube-hetzner.null_resource.agents["2-2-bots-large"] (remote-exec): Waiting for the k3s agent to start...
module.kube-hetzner.null_resource.agents["2-2-bots-large"] (remote-exec): Waiting for the k3s agent to start...
module.kube-hetzner.null_resource.agents["2-2-bots-large"]: Still creating... [2m20s elapsed]
╷
│ Error: remote-exec provisioner error
│
│   with module.kube-hetzner.null_resource.agents["2-2-bots-large"],
│   on .terraform/modules/kube-hetzner/agents.tf line 107, in resource "null_resource" "agents":
│  107:   provisioner "remote-exec" {
│
│ error executing "/tmp/terraform_1588448047.sh": Process exited with status 124

How add new additional node to k3s?

When I connect to VM:
h-k3s-test-bots-large-wto:~ # journalctl -xeu k3s-agent
░░ The error number returned by this process is ERRNO.
Jan 05 07:49:17 h-k3s-test-bots-large-wto (k3s)[3475]: k3s-agent.service: Failed at step EXEC spawning /usr/local/bin/k3s: Permission denied
░░ Subject: Process /usr/local/bin/k3s could not be executed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The process /usr/local/bin/k3s could not be executed and failed.
░░
░░ The error number returned by this process is ERRNO.
Jan 05 07:49:17 h-k3s-test-bots-large-wto systemd[1]: k3s-agent.service: Main process exited, code=exited, status=203/EXEC

PS: Autoscaller create new 6 VMs and I don't see on k3s )))))

restorecon -v /usr/local/bin/k3s helped, too

See also: https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner/issues/1145#issuecomment-1875459438

@Silvest89  I think the work around is safe to do just after setup. I will introduce it right away. And will also update the k3s selinux package.

Thank you! All worked fine

@mysticaltech  I just ran into this issue while updating my cluster, remembered this issue and upgraded right away. All solved now. Just wanted to thank you for your effort 🙏🏻

I am getting the same error.
Newest Version, Mac, Fresh Install unchanged config (except hcloud token)


Crash on startup on 1.19.2 with the 1.1.0 version

Title! Attaching log file. Version 1.0 works perfectly fine, 1.1.0 crashes on startup.

Forge 43.3.5
MC 1.19.2
Mod version 1.1.0 1.18 to 1.19.3, tried both the Modrinth jar and the github jar.

The only mod active is ForgeLegalizer

crash.log

Hey, please test this build, if you can. (Scroll to the bottom, click on Artifacts, extract the downloaded ZIP and move /forge-1.18.2/build/libs/ForgeLegalizer-Forge-1.18.2to1.19.3-1.1.0.jar to your mods folder.

It works!


rm commas in block height, rm mono font for explorer table

Still gotta try this out, but I thought we wanted commas in the height after all? Maybe just at top of block page and not in table?
Also, I always felt that monospace was the nicest way to show hex strings, but like I said I haven't actually looked yet.  :)

See comma conversation in issue https://github.com/dcrdata/dcrdata/issues/200


In China, the location of the car shifts in HA when the device_tracker.xxx is updated

Describe the issue
When I restart HA or execute the following service, the gps location of the car in HA will shift to northwest:
service: homeassistant.update_entity
target:
  entity_id:
    - device_tracker.my_car

In #378, you fixed the coordinates shift. However, when the entity is updated, it seems that the conversion algorithm is executed again. If the homeassistant.update_entity service is called for 10 times, the coordinates of the car will shift 10 times far away from the correct location.
Expected behavior
When device_tracker.my_car is updated in HA, the location of the car will not shift.
Which Home Assistant version are you using?
core-2022.2.6
What was the last working version of Home Assistant Core?
No response
What is your region?
China
ConnectedDrive website

[X] I can still successfully login to the BMW ConnectedDrive website and the car status is available there.
[X] I have ConnectedDrive enabled for my vehicle.

Number of cars

[ ] I have 2 or more cars linked to the ConnectedDrive account.
[ ] I have a Mini vehicle linked to my account.

Output of bimmer_connected fingerprint
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response

Thanks for the report, the fix is easy but was also easy to miss (see #421).

Thanks for the report, the fix is easy but was also easy to miss (see #421).

Thanks. So when this new update will be available for HA? The 2022.3.0 version of HA has just been released, but I did not see the update of BMW Connected Drive.

It is included, but only visible in the full changelog at https://www.home-assistant.io/changelogs/core-2022.2
Seems they had to split it off otherwise it would have been too long.

It is included, but only visible in the full changelog at https://www.home-assistant.io/changelogs/core-2022.2
Seems they had to split it off otherwise it would have been too long.

Then this is strange. When I call the following service, the location of the car still shift in the official map of HA.
service: homeassistant.update_entity
target:
  entity_id:
    - device_tracker.my_car

My HA version information:
System Health

version
core-2022.2.9

installation_type
Home Assistant Supervised

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.9.7

os_name
Linux

os_version
5.10.60-v7l+

arch
armv7l

timezone
Asia/Shanghai

Home Assistant Community Store

GitHub API
ok

GitHub Content
failed to load: unreachable

GitHub Web
ok

GitHub API Calls Remaining
5000

Installed Version
1.23.0

Stage
running

Available Repositories
1066

Downloaded Repositories
22

Home Assistant Cloud

logged_in
false

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Raspbian GNU/Linux 10 (buster)

update_channel
stable

supervisor_version
supervisor-2022.01.1

docker_version
20.10.8

disk_total
58.2 GB

disk_used
17.2 GB

healthy
true

supported
failed to load: Unsupported

supervisor_api
ok

version_api
ok

installed_addons
File editor (5.3.3), Node-RED (10.2.0), Terminal & SSH (9.3.0), Portainer (2.0.0), AirSonos (3.2.0), Let's Encrypt (4.12.0), NGINX Home Assistant SSL proxy (3.1.1), Nginx Proxy Manager (0.11.0), ZeroTier One (0.12.2), AdGuard Home (4.4.2), InfluxDB (4.3.0)

Lovelace

dashboards
1

resources
16

views
4

mode
storage

Xiaomi Miot Auto

component_version
0.5.3

can_reach_server
ok

can_reach_spec
ok

logged_accounts
1

total_devices
30


Added support for Amazon Redshift and PostgreSQL support

Added support for both platforms at once as they are extremely similar.
Note: This PR is waiting on the PyPika PR here: https://github.com/kayak/pypika/pull/74 . Once that is merged, we can bump the PyPika version and then bump the minimum PyPika version in Fireant's requirements.txt and setup.py.

@x8lucas8x I believe this is due to PyPika not being the correct version. I'll update it when the new PyPika version is released.

Coverage increased (+0.3%) to 95.06% when pulling 0786c3e0926a4f0fe062d3e9262c8d0286dab282 on mikeengland:add-redshift-postgresql-support into 927aa3d9f38afa0ff29752586f87789ad309be7d on kayak:master.

Coverage increased (+0.3%) to 95.06% when pulling 763fa77eb2a6c15d3d96d71a7b318bcb94169cfa on mikeengland:add-redshift-postgresql-support into 927aa3d9f38afa0ff29752586f87789ad309be7d on kayak:master.


Azure CLI installed but can't run AZ commands

Describe the bug
I have installed Azure CLI from extensions, also from microsoft by ps script  but I can't run AZ commands. Says that it's not recognized. Also there is no selection of Azure CLI from terminal drop down. VS was restarted. What am I doing wrong?
Related command
az
Errors
az' is not recognized as an internal or external command,
operable program or batch file.
az : The term 'az' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1

az
~~

CategoryInfo          : ObjectNotFound: (az:String) [], CommandNotFoundException
FullyQualifiedErrorId : CommandNotFoundException

Issue script & Debug output
no debug
Expected behavior
i want to run azure cli from VS studio
Environment Summary
not working
Additional context
No response

Thank you for opening this issue, we will look into it.

I don't understand the problem, please read this first: https://learn.microsoft.com/en-us/cli/azure/install-azure-cli-windows?tabs=azure-cli


Ensure all CI packages are properly installing

Seems like at least OS/X is broken right now (probably since QML merge?).
I wonder, didn't we test this?
Is it possible to test-install a .dmg file and run Contour GUI on OS/X headless with something similar to echo "Hello, World" just to see if it is starting up? 🤔
While at it, ensure the MSI windows installer is working as well.
I've marked it as blocker because we can't release 0.4.0 (or anything) before that's working :)
Checklist

[ ] MacOS .dmg file properly installing and Contour GUI launching
[ ] Windows MSI properly installing and Contour GUI launching

I can not find any solutions for this problem.
Good things, we test both versions of Qt, so worst thing that can happen is that some qml package will be missing on one of this platforms.  We can at least check locally if everything is working on windows and macos

Finally fixed with #1339. We had to do some workaround (manual copy) as macdeployqt seems to miss out some files, but only on CI (it works on my local brew installed qt6) :-(


[Question] How to attend to memorized intervention?

When memorizing a sequence (1D intervention) is it possible to attend to it, as in 'where is GO->  located' (Stanford).?
I'd be interested in using pyreft for 'online-learning' similar to approaches with associative memory proposed in Larimar/MemoryLLM/CameLoT/Memory of Amortized Contexts. These projects lack implementations or usable interfaces and possiblities to transfer/ load learned behavior that pyreft comes with.
As an alternative would I train and load (hundreds of) partitioned SubLorefts to achieve the same?

@chris-aeviator thanks for the question. could you elaborate more on the memorization example? the current setup is to train an intervention to memorize the whole sequence. Could you explain the part of "attending"? Thanks!


Performance degradation with a big count of products.

Ticket based on support request SWAG-219398 B2B Suite - Performance issues
The customer has big cout of products in his DB about (700 000). Because of that degradation when he doing something in B2B debtor panel (Order List, Fastorder, Orders ...)
(Lust request customer in the end of tasks)
Here is identified problems:
The most common reason is the slow work of the method
\Shopware\B2B\LineItemList\Framework\LineItemListRepository::fetchOneListById() that called from method \Shopware\B2B\OrderList\Framework:fetchList() in cycle. Call of this method sometimes takes about 15s and it is called on most pages in B2B debtor dashboard.
Other big problems that affected for example this route /b2borderlistlineitemreference?orderlist=13&excludeMode=true&addAllToCart=true  is method
\Shopware\B2B\Shop\BridgePlatform\ProductService::fetchProductNamesByOrderNumbers(). SQL query that is executed in this method takes about 25s.

[public] Automated response: This issue is linked to the internal issue https://shopware.atlassian.net/browse/B2B-1084.
[created from B2B-1084, comment 485083]


Update ERC-7579: Update erc-7579 interface param names

Fixes typo, rename moduleType to moduleTypeId
This change can be verified from the reference implementation - https://github.com/erc7579/erc7579-implementation/blob/main/src/MSAAdvanced.sol#L249

I believe these changes have been made to the document. Please re-open if that isn't the case.


Multiple NRepls.cs improvements

Support for sending symbol metadata information via NRepl was incomplete because the :forms and :arglists typically present in symbol's metadata are expected to have different names: :forms-str and :arglists-str. This is related to the fact that these two keys usually contain edn that should not be parsed directly.
With this PR, the nrepl client in NRepl.cs now does the right thing and sends the -str version of the keys. This means that the argument list for user-defined fns and documentation for special forms (like let) should be now shown by most editor plugins. I've tested this behaviour to be correct both with Emacs (CIDER) and VSCode (Calva).
This PR also gets rid of a minor annoyance with Calva (and probably other editors that show documentation on mouse hover) where sometimes it would ask our nrepl server for an empty string, making it throw an exception that was logged to the Unity console. Now those empty string queries are properly ignored, making the Arcadia experience in Calva better.

I've also implemented automatically setting the ns to the current file's ns when that can be safely determined by folder structure. This gets rid of an annoying issue where you would eval a region of code before evaluating that file's ns form and evaluate that code in another namespace instead.
I believe the old behaviour was error-prone, as it lead to situations where, for instance, you would define a function in multiple namespaces by mistake. However, let me know if the original behaviour was the intended, and I'll rever this last commit, or we can put it behind a config flag instead.

I couldn't help myself and also implemented a simple version of Intellisense-like autocomplete :) Again, I've tested it to work with both CIDER and Calva.
Some highlights:

Autocomplete fns in current namespace: The system tries to complete all the symbols available to the current context. That is, the public vars of the current namespace, as well as any use or :refer :all imported symbols.
Autocomplete fns from other namespaces: You can also autocomplete things from other namespaces, both via alias str/split and fully qualified name clojure.string/split.
Autocomplete namespaces: The name of namespaces can also be autocompleted.
Autocomplete keywords: This tries to autocomplete browsing all the interned keywords in the system. NOTE: To implement this, I had to use reflection to access a private member field, similar to what the compliment library for JVM clojure does: https://github.com/alexander-yakushev/compliment/blob/master/src/compliment/sources/keywords.clj

As for the implementation details, I am not really satisfied with having clojure lambdas stored in strings inside the C# source. Suggestions are welcome!

This looks great, thanks for the hard work! We're testing now

Thanks! I'm glad to be able to help :D   Please let me know if there's anything that should be addressed.

@setzer22 this is awesome! just confirmed working for me in VSCode/Calva on Linux. the autocomplete is a real game changer. its the feature ive missed the most when working in clojure compared to F#, C# or JavaScript -- this is going to make the Arcadia experience really great!
Feedback on the implementation:

As for the implementation details, I am not really satisfied with having clojure lambdas stored in strings inside the C# source. Suggestions are welcome!

What we've done is implement functionality that is more naturally expressed in Clojure in a .clj file, required that file from the C# source, looked up the var and then invoked the var. It's a bit more bureaucracy but it keeps things clean.
There are examples of this approach in the NRepl.cs file. For example, our editor callback system is primarily written in Clojure and lives in Source/arcadia/internal/editor_callbacks.clj. To invoke arcadia.internal.editor-callbacks/add-callback  in NRepl.cs we:

Create a static Var field to hold the Var reference
Load the relevant namespace in the NRepl class's static constructor
Populate the static Var field using RT.var
Invoke the Var field whenever needed

You could move the Clojure functions that are currently inline into defns in a new file, maybe Source/arcadia/internal/nrepl_support.clj, and invoke them as above.

Note this addition may be a bit resource hungry (especially since I do no caching at all). This works fine on my machine and there's no noticeable slowdown. However, I think it would be best if we allow disabling it behind a config flag in configuration.edn.

Adding a flag to the configuration file makes sense. To do that:

Add an entry with the defualt value and documentation to configuration.edn
Load and invoke the arcadia.internal.config/config var from your C# source as above.
Cast the result to clojure.lang.APersistentMap
Invoke the valAt method passing in a Keyword instance that represents the keyword you are looking up.

Let me know if that makes sense. Thanks again for a great contribution!

Many thanks @nasser ! Again, I'm very glad to be able to contribute :D
I've pushed a new commits implementing your two suggested refactors. Let me know if you think something else can be improved!
I also added a CIDER-specific workaround that I think requires a bit more discussion. Let me ellaborate:
There seems to be an effort in cider to gradually replace middlewares with their own sideloaded implementations (https://github.com/clojure-emacs/cider/issues/2611) if those aren't present. That's actually good, but has an unfortunate side-effect: Since CIDER has no knowledge of CLR, it will assume ours is a Java nREPL and send some very JVM-specific code snippets to eval. If we do the right ting and throw an exception, CIDER acts strangely, and may even freeze.
One particular issue occurs when the "classpath" is not supported by the nrepl server (we have no classpath in CLR!). Cider will try to eval (seq (.split (System/getProperty "java.class.path") ":")) and fail, triggering the aforementioned issue. The workaround I've implemented for this will intercept this particular code string and return an empty list instead of an error. This mostly gets rid of the issue, but I think it's still a good idea to know when this is happening, so I added a LogWarning line that will print an explanatory message. At least affected users will then know what to ask.
Note that all these changes are pretty recent in cider (less than a year old). So it may very well be that some users are not experiencing this issue yet because their CIDER is not at the latest version. Could you please check if you can reproduce this behaviour? I suspect this issue affects Arcadia even prior to the changes introduced in this branch. Some minimal steps to reproduce on my machine are:

Start Unity and let it start Arcadia and the nREPL server
Go to emacs, open any namespace, run cider-connect.
Once connected, run cider-connect again, and repeat
The Unity console will print the following warning (on this branch): "Your clojure tooling (most likely CIDER) made a request to get the java.class.path which is not available on this platform". In older versions, cider would crash.

I've asked around in #cider at clojurians slack, and I may open an issue there to discuss this as well if they agree this is worth fixing. Hopefully we can get rid of this workaround. Another possibility would be to implement support for the "classpath" op, returning something that makes sense in CLR (a classpath equivalent, perhaps?). This may improve even more the nREPL experience in Arcadia so it's my preferred option.
Sorry for the wall of text! 😅

@nasser Done!
I've talked to @bozhidar from #cider and with his help I managed to get rid of the classpath workaround. Now we do a cleaner thing by implementing the classpath nrepl op. CLR has no "classpath" per se, but what I'm doing is sending the full path to the Assets folder as well as the Assets/Arcadia/Source. These are the two source roots for clojure code, so cider now does the right thing.
With this fix, more functionalities are now working: For instance, when you create a new file, cider will automatically detect the right namespace for that file, and add an ns declaration for you.

Feel free to ping me any time you need help with something nREPL related. :-)
Btw, is there any particular reason that you opted not to have the server as a separate project? I'm not sure if there's anything Arcadia specific in it, or it can be used by anyone interested in ClojureCLR.
I was also reminded of https://github.com/nrepl/bencode/pull/2/files today, as I wasn't sure if you plan to finish it or not.

@setzer22 This is looking really good! Added a note about ClojureCLR's "load path" which is the closest thing to the class path we have. If you can land that change we can support Leiningen projects and the whole thing would be less Arcadia dependent -- should be OK to merge after that!
@bbatsov No reason not to make the server its own project. It is in the Arcadia repository out of convenience more than anything else. I think with @setzer22 latest changes it would make sense to factor it out into its own project given how powerful its become.
wrt nrepl/bencode#2, we ended up continuing to build on our C# implementation that uses the Bencode.NET library, so the Clojure implementation hasn't been a priority. Realistically speaking I won't have time to come back to it any time soon, so it might make sense just to close that PR for now.

wrt nrepl/bencode#2, we ended up continuing to build on our C# implementation that uses the Bencode.NET library, so the Clojure implementation hasn't been a priority. Realistically speaking I won't have time to come back to it any time soon, so it might make sense just to close that PR for now.

Makes sense to me.

@bbatsov No reason not to make the server its own project. It is in the Arcadia repository out of convenience more than anything else. I think with @setzer22 latest changes it would make sense to factor it out into its own project given how powerful its become.

I think that'd be pretty cool indeed. The lack of a working nREPL implementation has long been a problem for wider ClojureCLR adoption (at least IMO).

@nasser  I'll start working on the changes soon!
About making a standalone CLR nREPL, I'm all in for that! I haven't used Clojure CLR outside of Arcadia, but that's partly due to the difficulty in setting up a good development environment.
As for the autocompletion support, I've found out @sogaiu, another member of the community, has a fork of the clojure-complete library for CLR: https://github.com/sogaiu/clojure-complete/tree/clr-support
Since that is more tested, and has a few interesting features, I'd suggest merging that with my implementation in nrepl_support.clj. One of the nice additions would be completing the static methods of a class, which would be a great for Unity interop.
In fact, the only thing that's missing is support for keyword completions, but I could patch in my implementation easily and we'd have a very complete implementation.
What do you think?

I went ahead and added the new autocompletion library I mentioned yesterday. I had to modify the original code slightly, and put it into a new namespace arcadia.internal.autocompletion. I've also added a short comment at the beginning listing the credits for the original contributors.
Let me know if you'd rather manage this as an external dependency. I am not aware we can do this yet in Arcadia, so I've just went the good ol' copy-paste approach 😄
The arcadia.internal.nrepl_support ns is now only used to bencode the results and call this other library. I've decided to split it this way so we can centralize all future nrepl features (e.g., better exception formatting) into this namespace.

Regarding the completion - you can also check this https://github.com/nrepl/nrepl/issues/174
I'm plan to adapt the original clojure-complete, so it returns completions in the same format (a sequence of maps) as cider-nrepl's "complete" op, and inline this into nREPL.

Hi @setzer22 thank you for this amazing contribution! How can I as a CIDER user make use of auto-completion?
I have checked my Arcadia/configuration.edn and the designated option is true.
I simply executed cider-connect at port 3722 but I don't get any autocomplete.. I get this warning:
;; Connected to nREPL server - nrepl://localhost:3722
;; CIDER 1.0.0snapshot
WARNING: Can't determine Clojure version.  The refactor-nrepl middleware requires clojure 1.8.0 (or newer)WARNING: No Clojure project was detected. The
refactor-nrepl middleware was not enabled. (You can mute this
warning by customizing `cljr-suppress-no-project-warning'.)

Thank you in advance!

Hi @lccambiaghi, I'm glad you like this :)
I don't have a lot of time to work on this right now. But I can tell you it used to work just fine in CIDER. Emacs is my main editor and I made sure every feature worked there. That being said, there might have been a breaking change in either cider, ClojureCLR/Arcadia or the NRepl implementation.
If I had to look somewhere, I'd start at the Unity console, see if you can find any errors there. Also, try having a look at the arcadia.internal.autocompletion namespace. You can open it in emacs and connect to the REPL, and you should be able to play around in it. Try invoking the autocompletion functions in there through the REPL and see whether they work that way.
I hope some of this helps you debug the issue :)

Thank you for your quick reply! It may very well be that I am doing something wrong. For example, should I have a project.clj? Do I need to do something particular other than cider-connect and set the port to 3722?
In the Unity console I read this error:
NullReferenceException: Object reference not set to an instance of an object
Arcadia.NRepl.HandleMessage (BencodeNET.Objects.BDictionary message, System.Net.Sockets.TcpClient client) (at Assets/Arcadia/Editor/NRepl.cs:471)
Arcadia.NRepl+<>c__DisplayClass36_0.<StartServer>b__1 () (at Assets/Arcadia/Editor/NRepl.cs:580)
UnityEngine.Debug:LogException(Exception)
Arcadia.<>c__

I understand you may not have the time! I wish I knew how to debug this ahah.. Thanks anyway!

Hi @setzer22 sorry to bother you again.. Would you be able to help me debug this issue? I tried to inspect the namespace indicated by you but I keep getting this NullReferenceExceptions..
What I could understand is that in the HandleMessage function either the client or the message is null.. When I connect with CIDER in the console I can see that the client is printed so I suspect the message? Do you have any recommendation on what I can do to enable the CIDER tooling? I feel like I am a few steps away from enabling the tools :D

Hello @lccambiaghi ! I also experience some issues with autocompletion using CIDER. I just found that by using CIDER v0.24.0, the autocompletion seems to work without issues. Unfortunately I'm not an expert so I can't pinpoint the cause of error, but I hope it helps.

Hi @FilipCon thank you so much!!! That fixed it!


Update main README

This should beautify the repo README a bit.
WARNING: this assumes that we already have distribution via krew in place.

Jep, that's the plan


Support for countries which use DD MM YYYY

Some countries don't use the USA layouts:
MM/DD/YYYY
but order the elements in least significant to most significant
i.e.
day then month then year.
And in reverse it goes:
YYYY MM DD
Does natty have a mode that allows switching to this type of Day/Month ordering?

Sorry, I accidentally closed this - reopening...

+1 for this - most of the world doesn't use the MMDDYY format - it's critical to be able to configure this to get the correct parse in many situations.

+1

+1 !
Natty really doesn't behave well for EU formatted dates.
For example "12/06/20" results in 6 DEC 2020, while it should be 12 JUNE 2020 .
"13/06/20" for example fails to parse at all, returning 13:00:00 for the current date.

+1
I actually wanted to use this to format data from an API but the format is DD/MM/YYYY and natty sees it as MM/DD/YYYY and that just does not work for me.