JdbiUnitOfWork - 1.2 release is not found in maven

Hi @isopropylcyanide, thanks for this project. Are you continuing to maintain the project and do the new releases? The version is set to 1.2 in your examples, but the Maven public repositories don't have this version. Appreciate if there is any new release and if you can point me to it. Thank you

Hello @harshach , I routinely address vulnerabilities and dependenabot merges. However, I never realized that the project is used outside. If you are interested, you can bump up the version, or else I can do it and cut a release.

Hello @harshach , I routinely address vulnerabilities and dependenabot merges. However, I see that the project is not available on Maven Central.
Let me push a release.

Thank you @isopropylcyanide

@harshach Running into some issues talking to the key server for sonatype to publish releases. I suspect it's my work laptop firewall that's blocking all outbound. I'll try to push one in a couple of days once I arrange a non work laptop.
Please allow me some time.


[youtube] Extract channel subscribers

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[X] At least skimmed through contributing guidelines including yt-dlp coding conventions
[X] Searched the bugtracker for similar pull requests
[X] Checked the code with flake8

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[X] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[X] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
Extracts channel subscriber count.
Closes #2350
TODO:

[x] decide on field name
[x] update tests

document the field in readme


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 15:57:29 on 2023.08.21
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 3, errors out: 0
Original problem ID: 85845
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=85845

Problem has been resolved in 6m 0s at 16:03:29 on 2023.08.21
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 85845


Fix WebPack 2 query object in loader chain

Support WebPack 2 query objects.
Migrate APIs to accept single options object instead of variably ordered args per WebPack 2 convention. Necessary to differentiate between loader and options objects.
Copy error message from CommonChunksPlugin.
Delegate extract class function to instance method to eliminate copy pasta. Note that loader delegates the opposite direction.
Add query object test using CSS source maps.
Port original example to WebPack 2.
Update README

Will publish if necessary CC @andreypopp @antialias @gajus @haoxins @indeyets @jamiehodge @jsdf @ju1ius @kentcdodds @spicydonuts @timbru31

[Current coverage][cc-pull] is 86.04%

Merging [#199][cc-pull] into [master][cc-base-branch] will increase coverage by 5.27%

@@             master       #199   diff @@
==========================================
  Files             4          4
  Lines           338        344     +6
  Methods          72         74     +2
  Messages          0          0
  Branches         71         73     +2
==========================================
+ Hits            273        296    +23
+ Misses           65         48    -17
  Partials          0          0

Powered by Codecov. Last updated by [2db50ee...2990a99][cc-compare]
[cc-base-branch]: https://codecov.io/gh/webpack/extract-text-webpack-plugin/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/webpack/extract-text-webpack-plugin/compare/2db50ee6279270e7f74319b22ad87fced150851a...2990a998fa9166646a8d6f49ab65c7830c77af4e
[cc-pull]: https://codecov.io/gh/webpack/extract-text-webpack-plugin/pull/199?src=pr

Not much I can do to improve patch coverage. The vast majority of missed lines are handling errors.

I don't really know the codebase well, but I don't see anything wrong with the PR

API discussion at https://gitter.im/webpack/webpack/developer?at=5763aed963ea0987306be32d.

It's tested in our app but not deployed yet @sokra 🙏

I just went through @kentcdodds egghead tutorial using webpack 2, but we can't deploy to production because I can't shrinkwrap without the peer dependency issue resolved. This would be really awesome to get this merged!

We'll publish our fork soon if we don't hear back. My impression is @sokra doesn't merge big PRs.

To anyone subscribed I'll be deleting my fork next week consequently shutting this PR. WebPack's maintainer has not only been unresponsive on multiple communication channels but tagged a new beta without addressing any outstanding PR notably including this one for WebPack 2 migration. Besides losing confidence in its maintainer our build broke irrevocably from upstream dependencies and lack of communication nor accepting meaningful contributions as evident in each repo's activity graph. Above all having delved into the source on several necessary occasions it's a bowl of spaghetti I won't bank our team's productivity on. He doesn't owe anyone support but I cannot commend his software either.

@texastoland before you jump ship, please reconsider reopening.

@texastoland before you jump ship, please reconsider reopening.

I appreciate what you're trying to do @TheLarkInn, but @texastoland is totally right in his decision. This has been a bit of a fiasco. I hope that the webpack project at large can improve the way it works with the community so this kind of thing doesn't happen again.

So I'm to blame for lack of communication. First and foremost getting that out of the way. I apoligize.
@kentcdodds @texastoland here's the low down.
We have discussed this repo for 2 weeks now. ExtractTextPlugin is a pain point for many people, whether it be speed, hackyness, bugs, etc. We have been so busy with documentation efforts and some of us being away or busy with real-life that it would be harmful to not spend the time looking over a PR in detail, especially one that already has problems. Communication certainly could have happened. I will personally ensure that this will certainly not happen again. Fuethermore in the future once we have assigned all new maintainers to these repositories, we can have a bit more leeway, flexibility, and autonomy. And if anyone has any trouble with this can personally reach out to me.


ErrorBorder not applied to error navigation widget

re #25328
I have "errorBorder": "#00ff00" and would have expected that it applies to the error navigation widget

Yeah, sounds like a good idea 👍

For the goto error peek we have the colors editorMarkerNavigationError.background and editorMarkerNavigationWarning.background.
I set the defaults to use editorError.foreground or editorError.border. Same for the warning color.


[add-resource] New Plugin/Theme

I would like to add my new plugin/theme to the Grav Repository._Here are the project details:
shane-zentz/Generallax
https://github.com/shane-zentz/Generallax

You need to create a release before it will be able to be added to GPM.


PlatformException(evaluateJavaScript_failed, Failed evaluating JavaScript, JavaScript string was: 'play()'

Hi there,
There is an issue with the youtube_player_flutter on iPhone XS version 12.3.1.
Exception:
Unhandled Exception: PlatformException(evaluateJavaScript_failed, Failed evaluating JavaScript, JavaScript string was: 'play()'
Error Domain=WKErrorDomain Code=4 "A JavaScript exception occurred" UserInfo={WKJavaScriptExceptionLineNumber=1, WKJavaScriptExceptionMessage=ReferenceError: Can't find variable: play, WKJavaScriptExceptionColumnNumber=5, WKJavaScriptExceptionSourceURL=about:blank, NSLocalizedDescription=A JavaScript exception occurred})
pubspec.yaml:
youtube_player_flutter: ^4.1.0
doctor:
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, v1.7.8+hotfix.4, on Mac OS X 10.13.6 17G65, locale en-VN)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 10.1)
[✓] iOS tools - develop for iOS devices
[✓] Android Studio (version 3.4)
[✓] Connected device (1 available)
• No issues found!
Btw, love the plugin though :)

I am having the same issue. Do you find any solution for this?

I have same issue.
flutter: Video mounted YoutubePlayerValue(isReady: false, isEvaluationReady: false, isLoaded: false, duration: 0:00:00.000000, position: 0:00:00.000000, buffered: 0.0, isPlaying: false, volume: 100, playerState: PlayerState.UNKNOWN, playbackRate: PlaybackRate.NORMAL, errorCode: 0)
flutter: Video mounted YoutubePlayerValue(isReady: false, isEvaluationReady: false, isLoaded: false, duration: 0:00:00.000000, position: 0:00:00.000000, buffered: 0.0, isPlaying: false, volume: 100, playerState: PlayerState.UNKNOWN, playbackRate: PlaybackRate.NORMAL, errorCode: 0)
[VERBOSE-2:ui_dart_state.cc(148)] Unhandled Exception: PlatformException(evaluateJavaScript_failed, Failed evaluating JavaScript, JavaScript string was: 'play()'
Error Domain=WKErrorDomain Code=4 "A JavaScript exception occurred" UserInfo={WKJavaScriptExceptionLineNumber=1, WKJavaScriptExceptionMessage=ReferenceError: Can't find variable: play, WKJavaScriptExceptionColumnNumber=5, WKJavaScriptExceptionSourceURL=about:blank, NSLocalizedDescription=A JavaScript exception occurred})
#0      StandardMethodCodec.decodeEnvelope (package:flutter/src/services/message_codecs.dart:569:7)
#1      MethodChannel.invokeMethod (package:flutter/src/services/platform_channel.dart:316:33)

#2      MethodChannelWebViewPlatform.evaluateJavascript (package:webview_flutter/src/webview_method_channel.dart:90:21)
#3      WebViewController.evaluateJavascript (package:webview_flutter/webview_flutter.dart:626:39)
#4      YoutubePlayerController._evaluateJS (package:youtube_player_flutter/src/youtube_pl<…>

Check #79


Prepare for 1.35.0 release

What does this PR do?
Manual preparation steps for 1.35.0 release

:broken_heart: Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-12-06T09:47:47.846+0000

Duration: 5 min 49 sec

Steps errors
Expand to view the steps failures

mvn install

Took 0 min 8 sec . View more details here
Description: ./mvnw clean install -DskipTests=true -Dmaven.javadoc.skip=true

mvn install

Took 0 min 3 sec . View more details here
Description: ./mvnw clean install -DskipTests=true -Dmaven.javadoc.skip=true

mvn install

Took 0 min 3 sec . View more details here
Description: ./mvnw clean install -DskipTests=true -Dmaven.javadoc.skip=true

mvn install

Took 0 min 3 sec . View more details here
Description: ./mvnw clean install -DskipTests=true -Dmaven.javadoc.skip=true

mvn install

Took 0 min 3 sec . View more details here
Description: ./mvnw clean install -DskipTests=true -Dmaven.javadoc.skip=true

:grey_exclamation: Flaky test report
No test was executed to be analysed.
:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run benchmark tests : Run the benchmark tests.

run jdk compatibility tests : Run the JDK Compatibility tests.

run integration tests : Run the Agent Integration tests.

run end-to-end tests : Run the APM-ITs.

run windows tests : Build & tests on windows.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)


fix: alignment of the image seen on no search results on application page

Description

Alignment of the image seen on no search results on the application page.

Fixes #13949
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Checked the alignment of the image is as expected

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:white_circle: Total coverage has not changed
// Code coverage diff between base branch:release and head branch: fix/no-results-image-align

Status
File
% Stmts
% Branch
% Funcs
% Lines

:red_circle:
app/client/src/sagas/InitSagas.ts
48.66 (-1.9)
33.85 (-2.82)
58.33 (0)
51.57 (-2.38)

:green_circle:
app/client/src/utils/WorkerUtil.ts
89.76 (0.78)
72.55 (1.96)
100 (0)
93.33 (0.95)

/ok-to-test sha=fde9a06

/ok-to-test sha=22200db

/ok-to-test sha=2c8259d

/ok-to-test sha=1a1a2cb

/ok-to-test sha=ac45cc7

/ok-to-test sha=2faf4cf

/ok-to-test sha=b165c34

/ok-to-test sha=e563fa2


Port missing LuisTelemetryConstants for 'topTwoIntents' from C#

Is your feature request related to a problem? Please describe.
Currently, we are only able to log the top scoring intent to AppInsights via the integrated TelemetryClient in the LuisRecognizer.
In C#, there is the option to pass TelemetryProperties that enable the logging of both the top scoring intent and the second highest scoring intent. This is not yet implemented in botbuilder-js.
Describe the solution you'd like
Port the LuisTelemetryConstants Intent2Property and IntentScore2Property from the C# luis telemetry constants.
To enable usage of those constants, the corresponding properties will also have to be defined in LuisRecognizer.fillTelemetryProperties(). This can also be ported from the C# project.
Also, the LuisTelemetryConstants are currently not exported from the package. This would have to be mitigated as well in order to enable easy use of them.
Describe alternatives you've considered
The current workaround is to create a custom telemetry event and log those properties there. However, this is additional code and effort that would not be necessary if those LuisTelemetryConstants were implemented.
[enhancement]

I've identified the PR and the commit where this was implemented in C#. I'm unsure why no issue was made to port this before.
@srinaath - I messaged you and am awaiting instruction

@jwiley84 Has volunteered to take the port. Assigning.

Acknowledging, as it seems assigning me to github issues is not working.

Hi @mrestorff Just wanted to let you know this is still on my plate. We're discussing it internally, and you should see a PR with the changes in a few days.  Thank you for your patience in this.

@jwiley84 I think this is still on your plate, right?

Yes.

Hi @mrestorff Still working on this with a goal to have completed by the weekend. Thank you for your patience!

@jwiley84, any update on this?

@jwiley84, revisit to this, any updates on this?

@jwiley84 do you have any updates on this issue?


Pagination experiments

This is gonna break like all of the tests, so there is no way I'll merge the PR as it is now, I'm just playing around, later I'll cherry pick the changes I like to a new PR. I just want to get the CI's opinion on this.

Closed by https://github.com/hydephp/develop/pull/814


Adding without getting a duplicate object

Adding without getting a duplicate object is not totally obvious. Current add-description leaves you experimenting first.

Passed to technical team to fully understand the concepts involved in lists

@TimvanSteenbergen thanks for drawing our attention to this. It seems that there is more within Change List that needs documenting more clearly and I am reviewing the behavior with the development team.
I will publish an updated document reflecting your changes shortly.

@TimvanSteenbergen - Thanks to your PR the teams are more aware of the issues and are making plans to collaborate on deciding how it should work.
As always, I can't promise when the improvements will make it to the product.
Thanks again for helping to improve Mendix.


Compiling fails when encountering new compiler warnings

Using
oqs = { version="0.7.2", default-features = false, features = ["kyber"] }

I get when building
   Compiling oqs-sys v0.7.2
error: failed to run custom build command for `oqs-sys v0.7.2`

Caused by:
  process didn't exit successfully: `/Users/bas/scm/rust-hpke/target/debug/build/oqs-sys-450355f50f2b9656/build-script-build` (exit status: 101)
  --- stdout
  CMAKE_TOOLCHAIN_FILE_x86_64-apple-darwin = None
  CMAKE_TOOLCHAIN_FILE_x86_64_apple_darwin = None
  HOST_CMAKE_TOOLCHAIN_FILE = None
  CMAKE_TOOLCHAIN_FILE = None
  CMAKE_GENERATOR_x86_64-apple-darwin = None
  CMAKE_GENERATOR_x86_64_apple_darwin = None
  HOST_CMAKE_GENERATOR = None
  CMAKE_GENERATOR = None
  CMAKE_PREFIX_PATH_x86_64-apple-darwin = None
  CMAKE_PREFIX_PATH_x86_64_apple_darwin = None
  HOST_CMAKE_PREFIX_PATH = None
  CMAKE_PREFIX_PATH = None
  CMAKE_x86_64-apple-darwin = None
  CMAKE_x86_64_apple_darwin = None
  HOST_CMAKE = None
  CMAKE = None
  running: "cmake" "/Users/bas/.cargo/registry/src/github.com-1ecc6299db9ec823/oqs-sys-0.7.2/liboqs" "-DCMAKE_OSX_ARCHITECTURES=x86_64" "-DOQS_BUILD_ONLY_LIB=Yes" "-DOQS_DIST_BUILD=Yes" "-DOQS_ENABLE_KEM_BIKE=No" "-DOQS_ENABLE_KEM_CLASSIC_MCELIECE=No" "-DOQS_ENABLE_KEM_FRODOKEM=No" "-DOQS_ENABLE_KEM_HQC=No" "-DOQS_ENABLE_KEM_KYBER=Yes" "-DOQS_ENABLE_KEM_NTRU=No" "-DOQS_ENABLE_KEM_NTRUPRIME=No" "-DOQS_ENABLE_KEM_SABER=No" "-DOQS_ENABLE_KEM_SIDH=No" "-DOQS_ENABLE_KEM_SIKE=No" "-DOQS_ENABLE_SIG_DILITHIUM=No" "-DOQS_ENABLE_SIG_FALCON=No" "-DOQS_ENABLE_SIG_PICNIC=No" "-DOQS_ENABLE_SIG_RAINBOW=No" "-DOQS_ENABLE_SIG_SPHINCS=No" "-DOQS_USE_OPENSSL=No" "-DCMAKE_INSTALL_PREFIX=/Users/bas/scm/rust-hpke/target/debug/build/oqs-sys-d30719a70bf74e8d/out" "-DCMAKE_C_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64 -arch x86_64" "-DCMAKE_C_COMPILER=/usr/bin/cc" "-DCMAKE_CXX_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64 -arch x86_64" "-DCMAKE_CXX_COMPILER=/usr/bin/c++" "-DCMAKE_ASM_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64 -arch x86_64" "-DCMAKE_ASM_COMPILER=/usr/bin/cc" "-DCMAKE_BUILD_TYPE=Release"
  -- Configuring done (0.1s)
  -- Generating done (0.3s)
  -- Build files have been written to: /Users/bas/scm/rust-hpke/target/debug/build/oqs-sys-d30719a70bf74e8d/out/build
  running: "cmake" "--build" "." "--target" "oqs" "--config" "Release"
  [  0%] Built target xkcp_low_keccakp_1600_plain64
  [  1%] Built target xkcp_low_keccakp_1600_avx2
  [  1%] Building C object src/kem/kyber/CMakeFiles/kyber_1024_90s_avx2.dir/pqcrystals-kyber_kyber1024-90s_avx2/indcpa.c.o
  [  1%] Building C object src/common/CMakeFiles/common.dir/aes/aes.c.o
  [  2%] Built target xkcp_low_keccakp_1600times4_avx2
  [  3%] Built target xkcp_low_keccakp_1600times4_serial
  [  4%] Building C object src/kem/kyber/CMakeFiles/kyber_512_ref.dir/kem_kyber_512.c.o
  [  5%] Building ASM object src/kem/kyber/CMakeFiles/kyber_512_avx2.dir/pqcrystals-kyber_kyber512_avx2/basemul.S.o
  [  5%] Building C object src/kem/kyber/CMakeFiles/kyber_512_ref.dir/pqcrystals-kyber_kyber512_ref/cbd.c.o
  [  6%] Building C object src/kem/kyber/CMakeFiles/kyber_512_avx2.dir/pqcrystals-kyber_kyber512_avx2/cbd.c.o
  [  7%] Building C object src/kem/kyber/CMakeFiles/kyber_768_ref.dir/kem_kyber_768.c.o
  [  8%] Building ASM object src/kem/kyber/CMakeFiles/kyber_768_avx2.dir/pqcrystals-kyber_kyber768_avx2/basemul.S.o
  [  9%] Building C object src/common/CMakeFiles/common.dir/aes/aes_c.c.o
  [  9%] Building C object src/kem/kyber/CMakeFiles/kyber_1024_90s_avx2.dir/pqcrystals-kyber_kyber1024-90s_avx2/kem.c.o
  [ 10%] Building C object src/kem/kyber/CMakeFiles/kyber_768_avx2.dir/pqcrystals-kyber_kyber768_avx2/cbd.c.o
  [ 10%] Building C object src/common/CMakeFiles/common.dir/aes/aes128_ni.c.o
  [ 11%] Building C object src/common/CMakeFiles/common.dir/aes/aes256_ni.c.o
  [ 11%] Building C object src/kem/kyber/CMakeFiles/kyber_512_avx2.dir/pqcrystals-kyber_kyber512_avx2/consts.c.o
  [ 12%] Building C object src/kem/kyber/CMakeFiles/kyber_1024_90s_avx2.dir/pqcrystals-kyber_kyber1024-90s_avx2/poly.c.o
  [ 12%] Building C object src/kem/kyber/CMakeFiles/kyber_768_avx2.dir/pqcrystals-kyber_kyber768_avx2/consts.c.o
  [ 13%] Building C object src/kem/kyber/CMakeFiles/kyber_1024_90s_avx2.dir/pqcrystals-kyber_kyber1024-90s_avx2/rejsample.c.o
  [ 14%] Building ASM object src/kem/kyber/CMakeFiles/kyber_768_avx2.dir/pqcrystals-kyber_kyber768_avx2/fq.S.o
  [ 15%] Building C object src/common/CMakeFiles/common.dir/sha2/sha2.c.o
  [ 16%] Building ASM object src/kem/kyber/CMakeFiles/kyber_512_avx2.dir/pqcrystals-kyber_kyber512_avx2/fq.S.o
  [ 16%] Building C object src/kem/kyber/CMakeFiles/kyber_768_avx2.dir/pqcrystals-kyber_kyber768_avx2/indcpa.c.o
  [ 16%] Building C object src/common/CMakeFiles/common.dir/sha2/sha2_c.c.o
  [ 16%] Building C object src/kem/kyber/CMakeFiles/kyber_512_avx2.dir/pqcrystals-kyber_kyber512_avx2/indcpa.c.o
  [ 17%] Building ASM object src/kem/kyber/CMakeFiles/kyber_768_avx2.dir/pqcrystals-kyber_kyber768_avx2/invntt.S.o
  [ 18%] Building C object src/common/CMakeFiles/common.dir/sha3/xkcp_sha3.c.o
  [ 19%] Building ASM object src/kem/kyber/CMakeFiles/kyber_512_avx2.dir/pqcrystals-kyber_kyber512_avx2/invntt.S.o
  [ 19%] Building C object src/common/CMakeFiles/common.dir/sha3/xkcp_sha3x4.c.o
  [ 20%] Building C object src/kem/kyber/CMakeFiles/kyber_768_avx2.dir/pqcrystals-kyber_kyber768_avx2/kem.c.o
  [ 21%] Building C object src/common/CMakeFiles/common.dir/common.c.o
  [ 27%] Built target kyber_1024_90s_avx2
  [ 28%] Building C object src/kem/kyber/CMakeFiles/kyber_512_avx2.dir/pqcrystals-kyber_kyber512_avx2/kem.c.o
  [ 28%] Building ASM object src/kem/kyber/CMakeFiles/kyber_768_avx2.dir/pqcrystals-kyber_kyber768_avx2/ntt.S.o
  [ 29%] Building C object src/kem/kyber/CMakeFiles/kyber_768_avx2.dir/pqcrystals-kyber_kyber768_avx2/poly.c.o
  [ 30%] Building C object src/kem/kyber/CMakeFiles/kyber_768_avx2.dir/pqcrystals-kyber_kyber768_avx2/polyvec.c.o
  [ 30%] Building ASM object src/kem/kyber/CMakeFiles/kyber_512_avx2.dir/pqcrystals-kyber_kyber512_avx2/ntt.S.o
  [ 31%] Building C object src/common/CMakeFiles/common.dir/pqclean_shims/nistseedexpander.c.o
  [ 31%] Building C object src/kem/kyber/CMakeFiles/kyber_768_avx2.dir/pqcrystals-kyber_kyber768_avx2/rejsample.c.o
  [ 31%] Building C object src/common/CMakeFiles/common.dir/pqclean_shims/fips202.c.o
  [ 32%] Building ASM object src/kem/kyber/CMakeFiles/kyber_768_avx2.dir/pqcrystals-kyber_kyber768_avx2/shuffle.S.o
  [ 33%] Building C object src/kem/kyber/CMakeFiles/kyber_512_avx2.dir/pqcrystals-kyber_kyber512_avx2/poly.c.o
  [ 34%] Building C object src/common/CMakeFiles/common.dir/pqclean_shims/fips202x4.c.o
  [ 35%] Building C object src/common/CMakeFiles/common.dir/rand/rand.c.o
  [ 36%] Building C object src/kem/kyber/CMakeFiles/kyber_512_avx2.dir/pqcrystals-kyber_kyber512_avx2/polyvec.c.o
  [ 36%] Building C object src/kem/kyber/CMakeFiles/kyber_768_avx2.dir/pqcrystals-kyber_kyber768_avx2/symmetric-shake.c.o
  [ 36%] Building C object src/common/CMakeFiles/common.dir/rand/rand_nist.c.o
  [ 36%] Building C object src/kem/kyber/CMakeFiles/kyber_512_avx2.dir/pqcrystals-kyber_kyber512_avx2/rejsample.c.o
  [ 37%] Building C object src/kem/kyber/CMakeFiles/kyber_768_avx2.dir/pqcrystals-kyber_kyber768_avx2/verify.c.o
  [ 38%] Building ASM object src/kem/kyber/CMakeFiles/kyber_512_avx2.dir/pqcrystals-kyber_kyber512_avx2/shuffle.S.o
  [ 38%] Building C object src/kem/kyber/CMakeFiles/kyber_512_avx2.dir/pqcrystals-kyber_kyber512_avx2/symmetric-shake.c.o
  [ 39%] Building C object src/kem/kyber/CMakeFiles/kyber_512_avx2.dir/pqcrystals-kyber_kyber512_avx2/verify.c.o
  [ 39%] Built target kyber_768_avx2
  [ 39%] Built target kyber_512_avx2
  [ 39%] Built target common

  --- stderr
  /Users/bas/.cargo/registry/src/github.com-1ecc6299db9ec823/oqs-sys-0.7.2/liboqs/src/kem/kyber/kem_kyber_512.c:9:31: error: a function declaration without a prototype is deprecated in all versions of C [-Werror,-Wstrict-prototypes]
  OQS_KEM *OQS_KEM_kyber_512_new() {
                                ^
                                 void
  1 error generated.
  make[3]: *** [src/kem/kyber/CMakeFiles/kyber_512_ref.dir/kem_kyber_512.c.o] Error 1
  make[3]: *** Waiting for unfinished jobs....
  /Users/bas/.cargo/registry/src/github.com-1ecc6299db9ec823/oqs-sys-0.7.2/liboqs/src/kem/kyber/kem_kyber_768.c:9:31: error: a function declaration without a prototype is deprecated in all versions of C [-Werror,-Wstrict-prototypes]
  OQS_KEM *OQS_KEM_kyber_768_new() {
                                ^
                                 void
  1 error generated.
  make[3]: *** [src/kem/kyber/CMakeFiles/kyber_768_ref.dir/kem_kyber_768.c.o] Error 1
  make[2]: *** [src/kem/kyber/CMakeFiles/kyber_768_ref.dir/all] Error 2
  make[2]: *** Waiting for unfinished jobs....
  make[2]: *** [src/kem/kyber/CMakeFiles/kyber_512_ref.dir/all] Error 2
  make[1]: *** [src/CMakeFiles/oqs.dir/rule] Error 2
  make: *** [oqs] Error 2
  thread 'main' panicked at '
  command did not execute successfully, got: exit status: 2

  build script failed, must exit now', /Users/bas/.cargo/registry/src/github.com-1ecc6299db9ec823/cmake-0.1.50/src/lib.rs:1098:5
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Rust version:
stable-x86_64-apple-darwin (default)
rustc 1.67.1 (d5a82bbd2 2023-02-07)

Fixed in main.

This is kind of a problem with how liboqs ends up getting packaged, with all compiler errors turned on. I've opened https://github.com/open-quantum-safe/liboqs/issues/1432 to discuss this upstream.

In the mean time, I need to consider if I want to set -Wno-error in build.rs...

Version in crates still has that issue

I've encountered a similar problem even after checking out main (508a13c0) I'm using rust 1.69.
oqs-sys = { git = "https://github.com/open-quantum-safe/liboqs-rust.git", branch = "main" }
oqs = { git = "https://github.com/open-quantum-safe/liboqs-rust.git", branch = "main", default-features = false, features = ["kyber", "std"] }

... snipped ...

  [100%] Building C object src/sig/sphincs/CMakeFiles/sphincs_shake256_192s_simple_clean.dir/pqclean_sphincs-shake256-192s-simple_clean/utils.c.o
  [100%] Building C object src/sig/sphincs/CMakeFiles/sphincs_shake256_256f_robust_clean.dir/pqclean_sphincs-shake256-256f-robust_clean/wots.c.o
  [100%] Building C object src/sig/sphincs/CMakeFiles/sphincs_shake256_256f_simple_clean.dir/pqclean_sphincs-shake256-256f-simple_clean/utils.c.o
  [100%] Building C object src/sig/sphincs/CMakeFiles/sphincs_shake256_256s_robust_clean.dir/pqclean_sphincs-shake256-256s-robust_clean/sign.c.o
  [100%] Building C object src/sig/sphincs/CMakeFiles/sphincs_shake256_256f_simple_clean.dir/pqclean_sphincs-shake256-256f-simple_clean/wots.c.o
  [100%] Building C object src/sig/sphincs/CMakeFiles/sphincs_shake256_256s_robust_clean.dir/pqclean_sphincs-shake256-256s-robust_clean/thash_shake256_robust.c.o
  [100%] Building C object src/sig/sphincs/CMakeFiles/sphincs_shake256_192s_simple_clean.dir/pqclean_sphincs-shake256-192s-simple_clean/wots.c.o
  [100%] Building C object src/sig/sphincs/CMakeFiles/sphincs_shake256_256s_robust_clean.dir/pqclean_sphincs-shake256-256s-robust_clean/utils.c.o
  [100%] Built target sphincs_shake256_192s_robust_clean
  [100%] Building C object src/sig/sphincs/CMakeFiles/sphincs_shake256_256s_robust_clean.dir/pqclean_sphincs-shake256-256s-robust_clean/wots.c.o
  [100%] Built target sphincs_shake256_256f_robust_clean
  [100%] Built target sphincs_shake256_256f_simple_clean
  [100%] Built target sphincs_shake256_192s_simple_clean
  [100%] Built target sphincs_shake256_256s_robust_clean
  [100%] Building C object src/CMakeFiles/oqs.dir/kem/kem.c.o
  [100%] Building C object src/CMakeFiles/oqs.dir/sig/sig.c.o
  [100%] Linking C static library ../lib/liboqs.a
  [100%] Built target oqs
  cargo:root=/Users/christopherpatton/cf-repos/CRYPTO/rustls_pq/target/debug/build/oqs-sys-ec6822a9eb5cd43c/out
  cargo:rustc-link-lib=static=oqs
  cargo:rustc-link-search=native=/Users/christopherpatton/cf-repos/CRYPTO/rustls_pq/target/debug/build/oqs-sys-ec6822a9eb5cd43c/out/build/lib

  --- stderr
  CMake Warning:
    Manually-specified variables were not used by the project:

      CMAKE_CXX_COMPILER
      CMAKE_CXX_FLAGS

  /Users/christopherpatton/cf-repos/CRYPTO/rustls_pq/target/debug/build/oqs-sys-ec6822a9eb5cd43c/out/build/include/oqs/common.h:14:10: fatal error: 'stdlib.h' file not found
  thread 'main' panicked at 'Unable to generate bindings: ClangDiagnostic("/Users/christopherpatton/cf-repos/CRYPTO/rustls_pq/target/debug/build/oqs-sys-ec6822a9eb5cd43c/out/build/include/oqs/common.h:14:10: fatal error: 'stdlib.h' file not found\n")', /Users/christopherpatton/.cargo/git/checkouts/liboqs-rust-4f844d0c84f6a965/508a13c/oqs-sys/build.rs:33:10
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

/Users/christopherpatton/cf-repos/CRYPTO/rustls_pq/target/debug/build/oqs-sys-ec6822a9eb5cd43c/out/build/include/oqs/common.h:14:10: fatal error: 'stdlib.h' file not found

stdlib.h not found sounds a bit more significant...

I'm afraid I will not have time to do anything for the next couple of days at least...

No worries!

I managed to resolve my specific issue by using homebrew's clang instead of Apple's (brew install llvm).

I managed to resolve my specific issue by using homebrew's clang instead of Apple's (brew install llvm). It would be great to cut a release: I can get main to compile but not 0.7.2.

That's odd. Like Thom said, something seems really wrong if stdlib.h cannot be found. Is it possible that you have not installed XCode Command Line Tools after upgrading your system? Normally xcode-select --install should work.

I tried deleting the xcode stuff and reinstalling, no dice. There is likely something going on with my environment that has nothing to do with liboqs :) In fact, the other day I ended up building clang version 12.0.0 from source and installing it, it's possible that has messed things up a bit. I am hopeless with macOS.

Should be fixed by release 0.8.0


Added me as contributor

Your pull request seems good, but must be checked by a human maintainer for the following reason(s):

Modifications to contributors.md must be checked manually, thanks for your submission.

Please be patient until a maintainer has time to look over your contribution.
This is an automated response, beep boop.
if you think there is a mistake, contact a maintainer

213955f31232f6d6f6e1c1c915d225ff0baa755b

This request's code has changed since approval. Re-Judging contents...
Your pull request needs further work because of the following reason(s):

You added/changed/deleted 2 files. You can only add three (3) files index.html main.js main.css.
You changed a file at Games, this is not allowed, you can only modify games/swaager
You changed a file called swaager, this is not one of the three allowed names.
Your main.js file was not found, it is a requirement (even if empty)
Your main.css file was not found, it is a requirement (even if empty)
Your index.html file was not found, this one should exist and be nonempty

Once you have resolved the issues, comment on this request to be re-judged
This is an automated response, beep boop.
if you think there is a mistake, contact a maintainer

03b2a0dfabdb649e14952d7b2e0505fd711c1d6c

Added myself and games added

Your pull request needs further work because of the following reason(s):

You added/changed/deleted 4 files. You can only add three (3) files index.html main.js main.css.
You changed a file at Games, this is not allowed, you can only modify games/swaager
Your main.js file was not found, it is a requirement (even if empty)
Your main.css file was not found, it is a requirement (even if empty)

Once you have resolved the issues, comment on this request to be re-judged
This is an automated response, beep boop.
if you think there is a mistake, contact a maintainer

3a1b08d4419d16e19e4cec75d3275e224426e1a0


Configurable no-implicit-dependencies Ignore to Support Absolute Path Imports

Bug Report

TSLint version: 5.8.0
TypeScript version: 2.5.3
Running TSLint via: CLI (yarn)

TypeScript code being linted
# webpack config
{
  #
  # omitted
  #
  resolve: {
    alias: {
      "react/lib/ReactMount": "react-dom/lib/ReactMount",
      react: __dirname + "/node_modules/react",
      "#": SRC_DIR,
    },
    extensions: [".json", ".js", ".ts", ".tsx", ".less", ".css"],
    modules: [SRC_DIR, "node_modules"],
    mainFields: ["module", "jsnext:main", "browser", "main"],
  },
  #
  # omitted
  #
}

# Some later file
import {CollectorState} from "#/store/collectorState";

with tslint.json configuration:
{
  "extends": [
    "tslint:latest",
    "tslint-config-prettier"
  ],
  "rules": {
    "interface-name": false,
    "member-access": false,
    "object-literal-sort-keys": false,
    "arrow-parens": false,
    "no-empty-interface": false,
    "no-console": false,
    "no-submodule-imports": [true, "#"],
    "max-classes-per-file": [true, 3]
  }
}

Actual behavior
src/services/SearchService.ts
ERROR: 5:43   no-implicit-dependencies  Module '#' is not listed as dependency in package.json

Expected behavior
I use webpack resolve to support absolute path imports and tslint, on two different linters (no-submodule-imports and no-implicit-dependencies), picks this up as a package import and throws an error. My ask is the ability to configure an ignore for certain import prefixes (or packages in this scenario). Similar to:
    "no-submodule-imports": [true, "#"],

I would like to keep the rule enabled as it did help me catch an implicit import but it breaks the above workflow.

There's just one question: how to add the whitelisted modules to the existing config?
Currently this rule has two config options, so you can write "no-submodule-imports": [true, "dev", "optional"] without whitelisting dev or optional.
Simply adding the whitelisted dependencies after that (or in between) makes the configuration rather confusing.
In addition there is the possiblity of conflict between config options and actual package names.
I think the best approach would be a config object:
"whitespace": [
  true,
  {
    "dev": true,
    "optional": true,
    "whitelist": ["#", "~"] // property could be named "ignore" as well
]

An aside:
I think @bmarcaur is looking to change the no-implicit-dependencies rule, not the no-submodule-imports rule, or the whitespace rule. You may already know this, but it is unclear to me if we are all on the same page.
My question/suggestion:
Is it possible to allow a config object OR two strings following true so that it does not break any current configs? So that either of the following would be acceptable:
"no-implicit-dependencies": [
  true,
  {
    "dev": true,
    "optional": true,
    "allow": ["#", "~", "/app"] // I like "allow" as the exception name
  }
]

"no-implicit-dependencies": [ true, "dev", "optional" ]

Yeah sorry my example above uses another tslint rule to show an example of what I would want not that I want to change no-submodule-imports. Sorry that is a bit confusing. Also I imagine that you want to support a heterogeneous API here where it supports both the old and the new format @ajafff to avoid the API break. For example:
"no-implicit-dependencies": [
 true,
 {
   "dev": true,
   "optional": true,
   "allow": ["#", "~", "/app"] // I like "allow" as the exception name, but ditch it if it conflicts with established conventions
 },
 "dev",
 "optional"
]

I just ran into this as well - I have no choice but to disable these rules in my tslint.json.

@viridia: You might consider doing some inline tslint disabling. That way, you'd still get feedback if you accidentally import something that is not in your package file.
That's what I settled on in the meantime. Of course, for my project, I didn't have very many places where I was importing in a way that caused an issue. If you do, it might be a bigger headache.

@happycollision I used absolute imports pervasively throughout the code - based on advice from this medium post: https://spin.atomicobject.com/2017/10/07/absolute-paths-javascript/

I'm also having an issue. This would be so great if we had a fix for this. I ended up disabling the rule in my tslint.json

For those interested have I figured out a very hacky workaround, while we are waiting for a real fix.

Any forecast if that will be implemented?

I would also benefit from this.

I had to disable the no-implicit-dependencies rule because I use absolute imports in my projects. This feature could be very useful.

Need this feature here, too.

this feature would be very much appreciated

https://github.com/palantir/tslint/releases/tag/5.11.0

v5.11.0
[new-rule-option] Add whitelist for no-implicit-dependencies (#3979)

I added "no-implicit-dependencies: [true, [...]]" with an array of absolute path I need. Does I still have to declare them in package.json  ?
I tried to declare them in "optionalDependencies" and not declare them at all but both didn't work.

Can documentation be added for this? I don't understand how to use it.
If I have
a. devDependencies
b. paths listed in tsconfig.json, e.g. ```
"paths": {
"@App/": [
"src/"
],
"@Shared/": [
"src/Shared/"
]
},

How would I use this?

I tried:

"no-implicit-dependencies": [true, "dev", ["@App", "@Shared"]],

But I get this error:

/Users/jeremynagel/dev/energylink-project/react-components/data-exporter2/src/DataJunction/DataJunctionTable.tsx
(22,8): Module '@Shared/BootstrapTableFormatters' is not listed as dependency in package.json

What about dev dependencies @ilearnio ?

@jeznag Hm, not sure if I'll ever need them in my app's code. So far all works good

@jeznag FYI if your paths start with @ then you need to specify the whole name (not just the package name) due to the way the package name is calculated (it seems to not split the name of if it’s starts with an @ symbol): see https://github.com/palantir/tslint/blob/9d7db479596c50bbf89fa87d498ab927763a6eec/src/rules/noImplicitDependenciesRule.ts#L113

Damn! That's a good catch @chris5287 ! I was using the @ to define my local path. I guess i'll start using the ~ from now.
My tslint.json
{
  "defaultSeverity": "error",
  "extends": ["tslint:latest", "tslint-config-prettier"],
  "rules": {
    "no-submodule-imports": [true, "~root", "~src"],
    "no-implicit-dependencies": [true, ["~root", "~src"]]
  },
  "linterOptions": {
    "exclude": ["node_modules/**/*", "dist/**/*", "test/**/*"]
  }
}

My tsconfig.json
{
  "compilerOptions": {
    "strict": true,
    "module": "ESNext",
    "moduleResolution": "node",
    "target": "ESNext",
    "allowSyntheticDefaultImports": true,
    "outDir": "dist",
    "sourceMap": true,
    "baseUrl": ".",
    "paths": {
      "~root/*": ["./*"],
      "~src/*": ["src/*"]
    }
  }
}

So I can now import local modules without tslint nor ts error.
Eg:
import requestIdMiddleware from '~src/middlewares/request-id';

Unfortunately, this "~" solution not work for me. Anyway

Submodule import paths from this package are disallowed; import from the root instead tslint(no-submodule-imports)

tsconfig.json:
"paths": {
      "~global-shared/": [
        "projects/global-shared"
      ],
      "~global-shared/*": [
        "projects/global-shared/*"
      ]
    }

tslint.json:
    "no-submodule-imports": [
      true,
      "@angular",
      "~global-shared"
    ],
    "no-implicit-dependencies": [
      true,
      ["~global-shared"]
    ]

Don't forget the wildcard (*) character! Easily missed but critical.
Incorrect:
"paths": {
      "path1/": ["dir/"]
    }

Correct:
"paths": {
      "path1/*": ["dir/*"]
    }

🤖 Beep boop! 👉  TSLint is deprecated 👈  and you should switch to typescript-eslint! 🤖
🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋


Please invite me to the GitHub Community Organization

Name
Ashish
Discord Username (if applicable)
justAsh#1176
Additional Context
I love every thing about computers and want get involved deeply with them, i accidently saw eddie's live stream today and got interested in opensource and i want to make my contribution towards community by being part of it.

thanks


 These things do not affect anyone else normally.

1
for availability we have very pendantic error flags... XCode complains 'availability not guarding ios availability' cause it is actually not meant to be used as bool part of a compound if

The include errors happen when you dont use xcode but instead a CLI buildsystem like buck.
Header search paths are much more strict outside stock xcode(build)
Trying to use "A.h" from outside A's parent module is generally not kosher though. That holds true for C(++) too:
Thats why there IS a distinction between " and < ...
"" = local
<> = non-local
:)
I guess it worked because 99.9% of ppl use xcode and not super strict errors

cause it is actually not meant to be used as bool part of a compound if

I actually want to bring this up on the mailing lists. I think that warning is ridiculous; it was probably added to stop someone from doing this:
@available(…) {
    // code
}

But in practice all it does is prevent you from using it outside of simple if statements, which is a problem. If you could add the appropriate flag to disable it on a per-file basis—I think we only use it like that twice or so—I would be greatful if you could show me how you added it to your build system so I can add it to the README 😊 I have no plans to remove the flag which disables this warning, at least not until someone on the LLVM mailing lists can convince me it isn't a bogus warning.
As for import statements, I have a hunch there must be a way to add the appropriate header search paths to your build configuration as well. Either every header in FLEX needs to be included with <> or none should, not this weird middle ground where only a handful of import statements have been modified here. Can you show me the relevant build system code that adds FLEX to your project? This is something else I'd like to add to the README for anyone not using Xcode ☺

I can look into the warning and wrap the code in pragma push and pop I guess.. maybe that works :)
The import paths are CLEARLY wrong and I dont see us changing the configuration to work around.
The problem is also ONLY with those 4 includes ppl added. The <> are used correctly in most cases
To put it simply: Everytime you use quotes in an import in a public header, this is 100% wrong:
Everytime you use dont use quotes for an import in an implementation/private header: it is ok but you should only do so for external headers

I won't currently accept a PR that wraps the code in #prama directives, but you're welcome to do that on your own if you don't want to try adding specific flags for those files if that's what you want to do :(
The import paths are not wrong; all of those files are a part of the same project, so they should all be free to include one another without any path prefixes like FLEX/, and they shouldn't need <> when including one another. We only have two public header files, and they both use the proper import statements: FLEX.h#L9
If you'd post your BUCK file, I can take a look to see what it would take to fix these without making a PR!

ok

Okay! I really would like to help if I can. I want anyone to be able to use this project without Xcode, and it would be super helpful to us if I could get it working for you somehow.

my comments stand. but is it is mainly that we make them public headers so we can reuse them for our extensions of flex:
e.g.
[[FLEXManager sharedManager] registerGlobalEntryWithName:@"\U0001F5C4  App Group Container File Browser"
                               viewControllerFutureBlock:^UIViewController *{
                                 NSURL *const containerURL = [[NSFileManager defaultManager] containerURLForSecurityApplicationGroupIdentifier:MSGAppGroupIdentifier()];
                                 if (containerURL) {
                                   return [[FLEXFileBrowserTableViewController alloc] initWithPath:[containerURL relativePath]];
                                 } else {
                                   UIAlertController *alertController = [UIAlertController alertControllerWithTitle:@"Not Available"

and more :)

Why not submit a PR to add an app group container browser?

:D that was just one example.. still that can be a point for you but counter question: why offer an extension api that noone should use? :)
is fixing 5 includes worth our time? this is not changing anything for you and 9/10 headers are already using <FLEX/ still imports so im not creating inconsistencies but closing them! :)

why offer an extension api that no one should use?

It's just not public yet. But it will be eventually! Be aware that since these APIs are not public, they are subject to change until they become public.

this is not changing anything for you and 9/10 headers are already using <FLEX/ style imports so im not creating inconsistencies but closing them even! :)

Which other headers are using <FLEX/*.h> style imports? Or even <>? The only one I see is FLEX.h—as intended—and the one from you recently merged PR, which I intend to change back.

is fixing 5 includes worth our time?

Well, I've just spent a couple hours trying to get buck to even build—it doesn't build out of the box anymore apparently—all to no avail, because I couldn't get around some weird error. I would appreciate it if you could give me the opportunity to help you here so I can make it easier for anyone else who might be using Buck to use FLEX.
I've managed used FLEX without Xcode without any problems. I want to help you do the same.

ah I assumed it was public by FlexManager.h:66 (#pragma mark - Extensions)
there also def. headers doing <FLEX/ to do EXACLTLY what I wanna do :D
just search for it and see FLEXGlobalsEntry.h and FLEXFileBrowserTableViewController.h

Oh! My bad, I was thinking of a different method. I'm doing a lot of refactoring on a private branch.
You can use that, but something like browsing app containers sounds like it would make a good addition to FLEX itself!

just search for it and see FLEXGlobalsEntry.h and FLEXFileBrowserTableViewController.h

These are the only results I get with  FLEX imports:

I am willing to add AppGroupContainer to FLEX:
itd mean a property on FLEXManager:
@property(copy) NSArray<NSString *> *appGroups
if thats agreeable, im going to put up a PR

the other import we need back. Flex2 or whatever version had it cause we rely on it right now

:) hope that is a compromise? :)

the other import we need back. Flex2 or whatever version had it cause we rely on it right now

I am confused, what are you referring to here? Has a public header been made private since then or something?

yes. if we plopp in a new version it doesnt compile. existing version does.
I only tried to keep status quo


#530 | Redesign navbar

Fixes #530
Description
This PR overhauls the navbar. it also adds the following changes:

removes staking altogether
adds new global variables to app.scss:

--grey-text-color - muted text color (adapts to light/dark mode)
--border-color - border for use on tables and buttons etc (adapts to light/dark mode)
--text-color - default text color for when it needs to be explicitly stated (dark in light mode, white in dark mode)

adds new high order button component, OutlineButton
adds new file src/lib/chain-utils.ts for holding chain info until we switch over to true multi chain support

Test scenarios

go to https://deploy-preview-549--teloscan-redesign.netlify.app/
check out the new header on different screen sizes

all elements should be accessible regardless of screen size (e.g. the Network button moves from the top right on desktop to the hamburger menu on mobile)
it should look good 😎
bottom part of menu should go away on scroll
entire menu should be keyboard accessible

log in using the connect wallet button
check out the wallet menu by clicking the wallet button

you should be able to view TLOS balance, copy address, view account page, and logout

change the language

the header text should all be localized

checkout locally and run on mainnet

you should see TLOS balance fiat value in the account menu after logging in
you should see gas and TLOS price in the top left
you should not see the testnet indicator on the logo

Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have cleaned up the code in the areas my change touches
[x] My changes generate no new warnings
[ ] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings
[x] I have removed any unnecessary console messages
[x] I have included all english text to the translation file and/or created a new issue with the required translations for the currently supported languages
[x] I have tested for mobile functionality and responsiveness
[ ] I have added appropriate test coverage

@ezra-sg great job on this! minor feedback

Having issues with network select links, they dont lead anywhere for me on desktop from local or https://deploy-preview-549--teloscan-redesign.netlify.app/ using pc chrome.


Feature request

Hi,
I really like the idea of this project and I also have a couple of ideas how to extend this library.
During my work on my thesis I recognized that calculating the F1-score / precision / recall given the ground-truth is not always that trivial and it would be great if you could add this function to the library.
So, the idea is that instead of only providing the library with the dirty dataset, we additionally provide it with the clean ground truth as well. If there is ground truth available the library would return all metrics that have been requested, such as F1-score / precision / recall ...
Another idea I had is to think about whether we provide some process for hyperparameter optimization for quantitative methods, such as dBoost.
It would be also great if there would be a short tutorial how to call the librarie's Python API for each of the supported tools. For example, I do not fully understand how the OpenRefine Tool is implemented.
Again, thanks for this great project.
Best regards,
Felix

Hi Felix,
Thanks for your good comments.

I see your point regarding to add other useful services such as evaluating data cleaning job by the precision, recall, and F1. Eventually, we will probably develop a comprehensive framework to provide different data cleaning services. This module is just a beginning.
About hyperparameter optimization, again as a final goal, our framework would be able to recommend the best tools and parameters for each dataset. You can consider it as some kind of hyperparameter optimization.
About the providing more tutorial for running different tools, you are right. The documentation should be more complete.
Thank you for sending your sample codes for calling OpenRefine. I did not know that OpenRefine has Python interface. We will use that.

Again, thank you for feedback.
Kind regards,
Mohammad

Sounds great :)
I had another idea: It would be also great to provide optimal parameter configurations for well known datasets, such as Hospital, Flights, ... for each supported tool.

As we discussed, calculation of effectiveness measures are added.


Switch from deprecated terminal module to new terminal module.

Switch from deprecated terminal module to replacement terminal module.

SA1019: package golang.org/x/crypto/ssh/terminal is deprecated: this package moved to golang.org/x/term.  (staticcheck)

Codecov Report

Merging #241 (df49ef7) into main (7b8bf1e) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##             main     #241   +/-   ##
=======================================
  Coverage   80.32%   80.32%
=======================================
  Files          20       20
  Lines         747      747
=======================================
  Hits          600      600
  Misses        133      133
  Partials       14       14

Impacted Files
Coverage Δ

plugins/vsphere/pkg/command/login.go
90.36% <0.00%> (ø)

Continue to review full report at Codecov.

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

Is this obsolet then @evankanderson ?


Incomplete type information on product availability

The type definition for ProductVariantAvailability appears to be incomplete because the response from the API includes the ID and version of the associated inventory entry.
It seems like definition for ProductVariantAvailability should be a superset of ProductVariantChannelAvailability with the addition of the channels map. This would be helpful since an inventory entry could be immediately updated given a product, rather than having to fetch the inventory entry for each variant.

@jenschude I realized that I forgot to mention our products are using an inventory entry without a channel. This means the resulting availability for a product looks like the following:
"availability": {
  "isOnStock": true,
  "availableQuantity": 20,
  "version": 1,
  "id": "f64af276-a1ad-4eea-a8bc-89c453742a40"
}

I also found that the ID and version are included in the Commercetools documentation for ProductVariantAvailability

Yes. It has been added today. The changes are already merged to this repository. Both fields will be available with the next release.
Please see also: https://github.com/commercetools/commercetools-sdk-typescript/pull/626/files

Awesome, thanks!

Closing this as completed. 🥂


[Bug] Cannot use repositories other than dockerhub in helm chart

Search before asking

[X] I searched the issues and found no similar issues.

KubeRay Component
ray-operator
What happened + What you expected to happen
Cannot use repositories other than dockerhub in helm chart
eg: values.yaml
image:
  repository: localhost:5550/ray
  tag: latest
  pullPolicy: IfNotPresent

Will fail:
    state:
      waiting:
        message: 'Failed to apply default image tag "localhost:5550/:latest": couldn''t
          parse image reference "localhost:5550/:latest": invalid reference format'
        reason: InvalidImageName

Reproduction script
Use a repository other than dockerhub in values.yaml (see example above)
Anything else
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

My bad, this actually works... I had an existing pods and updating the CRD does not restart existing pods (see #234 which is closed but is actually still unfixed)


how to get $metadata result into datatable?

we have https://services.odata.org/V2/Northwind/Northwind.svc/$metadata excute this link we got exception "json is not supported." so how we can get metadata directly and convert into datatable?

when we call GetMetadataAsync() this method we get nothing.

Hello! Do you want to obtain the metadata document? Then you need to use service endpoint  https://services.odata.org/V2/Northwind/Northwind.svc (without "$metadata") and call a method GetMetadataDocumentAsync() with await.
Hope this helps.

Hello,
I got Exception that Resource not found.
I am using 5.6.1 version when i go into detail exception then i came to know that Requested uri
going like below
https://services.odata.org/V4/Northwind/$metadata
which is wrong it should be executed like below
https://services.odata.org/V4/Northwind/Northwind.svc/$metadata
then only we will get the result.Please check it example
https://services.odata.org/V4/Northwind/Northwind.svc/$metadata

same things happened regarding trip pin service
https://services.odata.org/v4/TripPinService/
I am executing above link and call  var _response1 = await client.GetMetadataDocumentAsync();
its requested uri is https://services.odata.org/v4/$metadata
so above throw exception like not found so it should execute like below to get result
https://services.odata.org/v4/TripPinService/$metadata

https://js.devexpress.com/Demos/WidgetsGallery/odata/WeatherItems
the above odata service metadata i got perfectly by following code
var _response1 = await client.GetMetadataDocumentAsync();
So i don't know why it is work for some url and not work for some other
please check it .

@nighotatul Before releasing 5.6.1 I ran integration tests that validate behavior of sample services at odata.org (both for XML and JSON payload, OData versions 2, 3 and 4). The tests passed so I supposed there's something in your app that wasn't correctly set up. Can you checkout the library integration tests? If you are absolutely sure you set it up correctly, can you send an example of URLs and payload (that you can obtain from tools like Fiddler)?

Please closed this ticket issues has been solved.


How to install grasp?

I downloaded the zip file and unpacked it.
When I try to start the server, I get an error.
Maybe I need to do something else after unpacking?
$ server/grasp_server.py --path ~/PhpstormProjects/notes/_gtd/grasp_capture.org
  File "server/grasp_server.py", line 44
    globs: Dict[str, Any] = {}
         ^
SyntaxError: invalid syntax

Close.
Old version python 3.5.
Update python to 3.8, its OK now.


Fix Reader URL Link Immediately After Assigning Section

When in a section compiler, assign a section to a reader. The reader's name appears for that section.
The URL on the link for the reader's name has square brackets around the reader ID, so that the URL is invalid.
Example: https://librivox.org/reader/[6399]
This gets cleared and corrected when one refreshes the web page.
Is there a way to remove those square brackets, to the URL is valid right away?

The brackets are being added here (It's an array turned into a string) and it's being passed with the brackets into this where it becomes a URL. Could this be fixed by just stripping the first and last characters of reader_id? That seems like the safest way to fix it without breaking something else.

Could this be fixed by just stripping the first and last characters of reader_id? That seems like the safest way to fix it without breaking something else.

That would work. But it seems more like fixing the symptom than the cause. Which would probably be safer, but messier in the long run. I just submitted a PR with an alternate fix which also seems straightforward enough.


hacky tooltip displays badly in napari light mode

This comment suggests the opposite!

Right, IIRC one is true on my Ubuntu, but the opposite is true on my Mac 😂


supports scoped registry names

addresses #64

would love to see this get merged!

@hnrchrdl can you rebase with master? If you do that it'll trigger the checks to be run again, which have been updated/adjusted in a separate PR.

sorry, not possible, because the fork belongs to the org i am working for.
could you instead open a PR on the fork's feature branch? otherwise feel free to cherry-pick my commits however you like.

Got it. Makes sense. I'll likely just push your branch to a local one in this repo and re-open the PR.

another rebase followed by snapshot updates fixed tests again.

@hnrchrdl thanks for working on this!

Released in https://github.com/release-it-plugins/workspaces/releases/tag/v3.1.0


Fix typo in validation issue template

And this one!  Thanks!

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat[#18]: ajout d'un composant alignant le bouton d'affichage

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


Questions about the compare with traditional multi-category joint works

Hello,
I have carefully read your P2C paper and code. I noticed that your network is trained separately for each category. This differs from many other point cloud completion methods where multi-category joint training is commonly used, such as PCN,Pointr,Seedformer and other Point Completion network. I would like to ask the following:

In your comparison experiments, did you use the results from your single-category training to directly compare with the results from other networks trained in a multi-category joint manner? Theoretically, single-category training may better optimize for specific categories, while joint training tends to enhance the model's generalizability across categories. Could you share your perspective on the fairness of such comparisons and how it aligns with your task goals?

Your P2C method focuses on a self-supervised task, and you chose to train the network separately for each category. Does this design stem from specific considerations? For instance:

Does the self-supervised nature of the task require stronger reliance on intra-category geometric characteristics, making single-category training more effective to avoid inter-category interference?
Or is it due to significant geometric differences between categories, which might negatively impact performance under multi-category joint training?

Thank you so much for your interest in our work. It is true that supervised methods are trained on multi classes as you mentioned. However, we follow the protocol for unpaired method evaluation which trained category specific networks and evaluate. We did cited supervised methods trained with multi category data in our tables, but that just for a reference, the unpaired methods and weakly supervised methods are what we want to compare.
The reason that why unpaired and our methods only train category specific network is obviously that it is more difficult. Our method seems to rely a lot on a per category prior to do the completion. However, our evaluation is fair and a multi category method is an open question.
Let me know if you have further questions.


pass arguments to fnErrorPattern and fnErrorLength ?

@sinegovsky-ivan arguments? which ones?

fnErrorPattern and fnErrorLength have been deprecated. You can use the onError output event:
<inline-editor ... (onError)="myHandleError($event)" ...></inline-editor>

$event is a parameter of type InlineEditorError[] -> { type: string, message: string }[]


TFLu: Port squeeze op from TFLite

This is a fix for: https://github.com/tensorflow/tensorflow/issues/44789

Again, no changes needed until we hear from @petewarden but in the case there might be value in refactor to add a reference implementation of squeeze in lite/kernels/internal/reference and then have the Lite and Micro kernels make use of that shared code.
I haven't looked at this very carefully so very real chance of this comment being inaccurate, but it looks like the logic in the Prepare function might be shareable.

As discussed, let's continue with this PR.

@mansnils  Can you please resolve conflicts? Thanks!

@mansnils  Can you please resolve conflicts? Thanks!

@petewarden @advaitjain ping for review

@petewarden @advaitjain ping for review

@petewarden ping for re-review after resolving conflicts

@mansnils  Can you please resolve conflicts? Thanks!

@petewarden @advaitjain ping for review

@petewarden @advaitjain ping for review

@gbaned ping for merge

@gbaned ready for merge

@advaitjain is there problem merging?

@mansnils can you please sync your branch to master ? thank you

@rthadur branch is synced to master
@petewarden can you please re-approve? thanks


Tox travis that recommended by jazzband

https://jazzband.co/about/releases#travis
Purpose

easy maintenance

Relates

run result on travis: https://travis-ci.org/jazzband/django-redshift-backend/builds/447104819

I'm terribly sorry that I didn't see this PR before working on #55 which also implements this. Closing this as this is a duplicate in effect. Thank you!

Actually, this has more than just the changes in .travis.yml. Reopening.


Art progress

Thought I might as well have a place to track my art progress.
Currently, I'm working on this tile and several variations of it.

The brick isn't seamless yet, but this should be fixed with a couple pixels.

Controller overlay graphic (still needs some polish).

Polished version

I purposely left the Windows flag on the right. Thought it was a nice contrast to the Tux I added on the left :wink:
There'll be text for those are who color blind, introducing the controls in a rhyming fashion.

Dorothy, as of now.
I'm trying to come up with more gruesome and disturbing design ideas (although her scratching out her own eye is pretty disturbing already).
There won't be any animation for her. She'll just float around in a bubble. Maybe I'll animate the blood dripping from her leg and face, depending on how well these details even pop.

That's look grate. Don't forget that's we have 1 day and some hours till jam end

That looks great. Don't forget that's we have 1 day and some hours till jam end

I'm aware.
Do you think we can finish the gameplay loop today (the green orb mechanics, damage to the player and the player damaging the mobs, picking up book pages that display a full screen overlay that can be closed by pressing space/A, level transition after n minutes) and set up a proper main menu, then spend tomorrow applying some polish and dealing with level 2?
I think it's manageable. If a bit anxiety inducing.

Almost done with enemy type 1 (E1)
The other two will just be color variations of a zombie-like creature, so I can focus on other things and help finish the gameplay loop today, @RuinedKingg

Okay. I'm currently working on damage mechanics

Awesome! I'm currently finishing texture work, so we should hopefully have a nicely tiled map soon.
Thanks for the great work thus far!

Just merged some art changes. Added character sprites and an initial tileset.

Can you combine this yellow bricks into one atlas?

Can you combine this yellow bricks into one atlas? Like this

Done

TODO (for game jam)

Add tree sprite for #3
Add orb particles
Add consuming orb (brown bubble)
Add Tin Man animation
Add flying monkey animation
Add missing cut-scenes


Add PowerToys' shortcuts to the Shortcut Guide

Description of the new feature / enhancement
Add the custom shortcuts used for all of the other PowerToys features to the Shortcut Guide for when you forget what you had assigned.
Scenario when this would be used?
Now that PowerToys has so many useful features, I think it would be helpful to have all of the assigned shortcuts easily accesible so you can refresh your memory while you get used to using them.
Supporting information
No response

/dup #15405


[ci] run CI on a schedule

This project contains some unpinned dependencies, which means that changes in the project's dependencies can break the project.
Today, continuous integration (CI) jobs are only run on commits in pull requests.
As a result, this situation is possible:

today: everything is working
6 weeks from today: open a pull request and things totally unrelated to your PR are broken

That situation is not ideal because it makes maintenance work on the project "lumpy" instead of spreading it more smoothly over time. It also means that the project can break and remain broken for a while without maintainers knowing, extra likely in a project like this with very very few users and not much development activity.
How to fix this issue
Add a schedule to https://github.com/jameslamb/lightgbm-dask-testing/blob/main/.github/workflows/main.yml, running that pipeline once a week. Any day of the week / time is fine.
See https://docs.github.com/en/actions/reference/events-that-trigger-workflows#schedule for details on how to do this.
and / or consult the example at https://github.com/uptake/pkgnet/blob/96ac2f1636f80a943f8a4fd6f2e93f870ff27ebb/.github/workflows/smoke-tests.yaml#L4-L10
Notes
This will be even more valuable if / when #20 is added to the project's CI.

The introduction of dependabot in #64 is enough for this, I think. That should generate a handful of PRs every year.
This repo is only used by me, as far as I know... it's fine for it to be broken for a few weeks in the way described in this issue. Not worth the electricity and usage of GitHub's free resources to run CI on a regular schedule.


Add classifiers to setup.py file to explicitly support python 3

Is there a plan to support both python 2 and python 3 or to migrate fully over to python 3? https://caniusepython3.com/project/pvlib returns False but says there are no dependencies blocking transition to python 3. Any thoughts on this? Python 3 will soon (this year) be more widely supported than python 2. https://blogs.msdn.microsoft.com/pythonengineering/2016/03/08/python-3-is-winning/

pvlib is fully compatible with python 2.7, 3.4, and 3.5 on all platforms:
https://travis-ci.org/pvlib/pvlib-python
I don't know anything about that website, but I think it's wrong.
I'd prefer to only support Python 3, but that's not going to happen anytime soon.

Thanks @wholmgren for that link. Good to know! All of the other packages I am using like pandas, numpy, etc return True from caniusepython3. I'm not sure if there is some annotation or something to add to the codebase to get it to return True. That website (you can also pip install caniusepython3) seems to dynamically pull the library you are interested in and checks it for support or compatibility or soemthing.
>>> import caniusepython3
>>> caniusepython3.check(projects=['pandas'])
No handlers could be found for logger "ciu"
True
>>> caniusepython3.check(projects=['pvlib'])
False

After a very quick look on caniusepython3's github page, I think we need to add some classifiers to our setup.py file
https://docs.python.org/3/distutils/setupscript.html#additional-meta-data
https://pypi.python.org/pypi?%3Aaction=list_classifiers

Pydap is not yet python3 compliant which is a pain when you need OpenDAP data source like NOAA NAM forecasts.  Something to keep in mind as Will is prepping a forecast module.
Sent from my iPhone
On May 25, 2016, at 10:37 AM, Luke Witmer <notifications<EMAIL_ADDRESS>wrote:
Thanks @wholmgrenhttps://github.com/wholmgren for that link. Good to know! All of the other packages I am using like pandas, numpy, etc return True from caniusepython3. I'm not sure if there is some annotation or something to add to the codebase to get it to return True. That website (you can also pip install caniusepython3) seems to dynamically pull the library you are interested in and checks it for support or compatibility or something.

import caniusepython3
caniusepython3.check(projects=['pandas'])
No handlers could be found for logger "ciu"
True
caniusepython3.check(projects=['pvlib'])
False

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHubhttps://github.com/pvlib/pvlib-python/issues/181#issuecomment-221629365

Thanks for pointing that out, Cliff -- you're becoming a python expert! It looks like there's been some recent movement for Python 3 support in PyDAP. However, the forecast module that we wrote currently uses the Siphon package to get data from Unidata's THREDDS server, and that's all Python 3 compatible.

Following up after the new release (0.3.3) with new classifiers... caniusepython3 still reports no. I give up.

Hmm, no worries, and I think what you've done so far are steps in the right direction. The fact that it is python 3 compatible regardless of what caniusepython3 reports works for me for now. We will get it figured out eventually.


Element styling only for html2canvas?

I'm using the handy data-html2canvas-ignore tag on a few elements, but Firefox is giving me problems with elements with negative margins. I'd like to be able to add an html2canvas-only style tag for a particular element, such as: data-html2canvas-style="margin-left: 0".
Has anyone else had any luck doing something like this?

You can modify the contents of the document (which is a clone of the original) that will get rendered with the onclone option, for example:
html2canvas(document.body, {onclone: function(document) {
  document.querySelector('.something').style.marginLeft = 0;
}}).then(...)

Thanks Nik! Greatly appreciate your work on this library. Is this in the documentation?

No, unfortunately not. The documentation is greatly lacking in many respects at the moment...

My downloaded image isn't getting the proper styling so I'm using computed-style-to-inline-style to render it properly by converting all the styling to inline css. But the issue with that is it's affecting the original dom. So I want to do it for the cloned element instead inside the onclone function but it's not working and the image isn't properly styled. Any idea why it's happening?

I tried to do the same thing, here is how I implemented it and all my styles were properly downloaded:
const computedStyleToInlineStyle = require("computed-style-to-inline-style");

 html2canvas(document.querySelector(".someclass"), {onclone: function(document) {
     computedStyleToInlineStyle(document.querySelector(".someclass"), {
          recursive: true
      });
    }}).then(canvas => {
        const imgData = canvas.toDataURL('image/png');
        ...
    });

another way, my solution:
add to element for example :
data-html2canvas-class="!transform-none"
      onclone: (document) => {
        const els = document.querySelectorAll(
          '[data-html2canvas-class]',
        ) as NodeListOf<HTMLElement>

        els.forEach((el) => {
          const payloadClasses = el.getAttribute('data-html2canvas-class')
          if (payloadClasses) {
            el.className = [el.className.trim(), payloadClasses.trim()].join(
              ' ',
            )
          }
        })
      },


Microsoft Azure Bot Framework SDK 4: Send proactive message to specific users from bot using Node js

I am able to send message to specific users with older botbuilder SDK 3.13.1 by saving message.address field in database.
var connector = new builder.ChatConnector({
        appId: process.env.MicrosoftAppId,
        appPassword: process.env.MicrosoftAppPassword,
        openIdMetadata: process.env.BotOpenIdMetadata
    });
var bot = new builder.UniversalBot(connector);
var builder = require('botbuilder');
// please assume that I am fetching msgAddress from database of the specific user I want to send
// message to
var msg = new builder.Message().address(msgAddress);
msg.text('Hello, this is a notification');
bot.send(msg);

How can this be done with botbuilder SDK 4? I am aware of the Rest API but want to achieve this with the SDK itself because the SDK is the more preferred way of communication between the bot and user.
Thanks in advance.

The Microsoft Bot Framework team prefers that how to questions be submitted on Stack Overflow. The official Bot Framework Github repos are the preferred platform for submitting bug fixes and feature requests.

Thank you for replying @jwiley84. I have already asked this on Stack Overflow two weeks ago which has not been answered yet. https://stackoverflow.com/questions/53424861/microsoft-azure-bot-framework-sdk-4-send-proactive-message-to-specific-users-fr


HIGH TORQUE MOTOR

Step 1: What do you want?

Report an issue.
Improve code (and need help).
Suggest a new feature.
Present a new hardware adapter board or wiring.
Want to report my experience or measurement. (Please also add them to the wiki!)

Step 2: Describe your environment

Arduino IDE version or Toolchain: _____
dw1000 Library version: _____
Arduino device: _____
Used adapter board: _____

Step 3: Describe the problem
Affected file(s) or example(s):

Filename 1
Filename 2

Steps to reproduce:

Observed Results:

What happened?  This could be a description, log output, etc.

Expected Results:

What did you expect to happen?

Relevant Code:
  // TODO(you): code here to reproduce the problem

Hİ,
How do I find a motor with high torque? (60 N.m) Rpm is'nt important.  But motor must not be very big and heavy. Could you help me please?

No, go for other stuff, close this issue.


Make SingularityUI snappier

and update node/npm...
and remove the vulnerable dependencies...
and...
and...
WIP
cc @kwm4385

Summary so far:

Address most of the vulnerable dep changes. The bootstrap one requires an upgrade to bootstrap 4
Uses the request ids list (from global search) for the requests table until the regular request json finishes loading, will allow the user to start searching/filtering earlier.
Global search just uses request ids rather than requesting the full json (which was previously done on every page because of this)
remove a duplicate ravenjs dep, we are including sentry in other ways
remove select2 dep, unused that I could find
update node sass so we can run on newer node/npm

before:

after:

Code looks fine besides a few style nits, but I'm not worried about that since we don't have up to date linting on here (A project for another time perhaps).
Are we still sticking with the requests page as the index?

Yeah, seemed to be the consensus that requests was the most useful page to land on. The dashboard attempted to be more personalized, but most folks just went right to requests to filter for the thing they were looking for anyways

Gotcha, and now that its fast enough we don't have the need to make the global search the landing.
🚢


updating readme for Windows 10 support fixes #679

Updating the documentation for users on Windows 10
Fixes https://github.com/nodejs/node-gyp/issues/679

@TooTallNate can you or another maintainer take a look at this.
I didn't see this requiring any code updates. Just taking the steps necessary to get the environment correct.
Most notably I think having the latest version of NPM makes the biggest difference!

pings @TooTallNate

LGTM with a suggestion.  Can you squash the commits and write up a nice commit log?  Please capitalize and punctuate sentences.  Thanks.

@bnoordhuis you know how i can squash the commits after doing a PR? I've not done that before
thanks

@Jayflux Do git rebase -i origin/master locally, then git push your-remote +HEAD:updatingWindows10Doc.
If you google around, some people will tell you to git push -f but that force-pushes all branches and can be dangerous.

Oh, and please post a comment when you're done.  GH doesn't send notifications when you add or modify commits.

hmm @bnoordhuis not sure that did it, was i supposed to do something in the rebase console? I just closed

Yes, you should be doing that from the command line.

@bnoordhuis yep rebase opened up vim I think
You on IRC or something, im not great with rebase :/

@TooTallNate I think the changes have been reflected in this PR for some reason
Sorry for the confusion

Thanks Jason, landed in a8d441a.


Calculate deposit monthly NRR

Changes

Changes NativeStakingDepositTransactionInfo.montlyNrr to be NativeStakingDepositTransactionInfo.annualNrr / 12.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>7
Details

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

Totals

Change from base Build<PHONE_NUMBER>5:
0.0%

Covered Lines:
4729

Relevant Lines:
8194

💛  - Coveralls


Adding documentation for properties

Adding documentation for properties
Choose a PR Template
Switch to "Preview" on this description then select one of the choices below.
Click here to open a PR for a Data Plane API.
Click here to open a PR for a Control Plane (ARM) API.

@hamshavathimunibyraiah, @razvanbadea-msft, @rkmanda: This PR should not have been merged with changes to package-lock.json.  These files should only be changed by the repo maintainers (the Azure SDK EngSys team).
I will create a PR to revert these changes to package-lock.json, and I will create an issue to add a check to automatically block PRs which edit package.json or package-lock.json.


how is the import passed to dynamic not a function?

Unless they are transpiling it to be a function, the promise (and therefore request) will be created immediately. It's nice, but it's not how the import spec is supposed to be used.

As with the spec import() should return a promise.
next/dynamic is our thing. So, current it accept a promise.
But we may change it.


driver: uart: i2c: npcx: Support 20MHz APB clock for i2c/uart module.

Add APB 20MHz frequency support for i2c and uart module.

I mark this PR as "Ready for review". It provides an alternative clock setting in npcx7/9 series.


images?

I should probably just read the source, but thought I should be able to figure this out by fidding:
How do I include locally stored images? I tried just storing them among the ".md" files, and referencing them with an <img src="test.png"> but that didn't work. Also tried the wiki ![](test.png) syntax, but that also didn't work. Also tried ./test.png, as well as creating an img directory and referencing img/test.png, but none worked. I must be missing something simple, but ... ?

Sorry about sending you on a wild goose chase, but this feature doesn't exist yet :) Personally I've been using images hosted externally in my own little deadwiki, but it would be a lot nicer to have the images locally (and be able to use my wiki offline), so I am with you that this is important.
I just added initial support in bdd91c97da9bcb2e6e84cb427e57cebc6362daf0. All of the things you tried should now "just work" work in the newest dev version - test.png, ./test.png, /test.png, etc will all refer to the test.png image inside your wiki.
I am going to test this feature a bit more in a bit and then push out a new version of deadwiki today.
Thanks for opening the issue!

Yay! I've been adding <img...> links in the hopes it will just start working, and now it does!
I've created a fork to fix a small bug I think I can handle (won't say what it is yet). Hopefully a pull request will be coming soon.

Great! And sorry about the state of the code, I am sort of in the middle of moving all the logic out of the HTTP routes and into either templates or the deadDB module. My goal is for the routes to basically be empty, like a good little web app, and for deadDB to really be "the wiki".
Closing issues is helpful :+1: I grew up in the days of Bugzilla and people slamming issues shut with a WONTFIX, so I am still a bit hesitant to mark an issue with a big red "CLOSED" immediately after commenting...

No apologies needed - I haven't done any "modern web development", and yours seems concise and in the spirit of this framework, so I'm learning a lot.


Rancher is not creating Fleet agent in the imported clusters

After importing 300+ clusters simultaneously through terraform, Rancher is taking more than 1 hour to install fleet agent in the imported clusters. Until then nodes are not visible in Cluster Manager and it is in "Wait Check-in" state. However, Nodes are visible in Cluster Explorer.
Rancher version - 2.5.7
Observations in the downstream clusters -

Initially cattle-cluster-agent pod is getting created in one of the worker node and then after 20-30 mins, it is getting recreated in master node.

Fleet agent pod gets created only after the cattle-cluster agent pod gets created in master node.

Fleet-controller pod will be having below error for all the imported clusters until the the kubeconfig secret gets created
level=error msg="error syncing 'fleet-default/c-d5s4r': handler import-cluster: secrets "c-d5s4r-kubeconfig" not found, requeuing"

Is there any way we can speed up the process when multiple clusters are imported simultaneously?

Duplicate of https://github.com/rancher/rancher/issues/31911


[Ubuntu] Pro is now in GA

Link to product page on endoflife.date
https://endoflife.date/ubuntu
Details of incorrect and correct details you have found
Now that Ubuntu Pro is in GA, we should revamp the page to be more clear. This graphic for eg, from the Ubuntu Pro page is quite clear about the difference, and we should incorporate this in the text:

Another source of concern is this bit:

Ubuntu Pro (Infra-only) - only guarantees security fixes for packages in the main repository - other packages are on a best-effort basis.

Now that Canonical is actively maintaining Universe, and tracking security issues and intentionally only pushing them to esm-apps (Ubuntu Pro only), these fixes are unlikely to land in universe. So we should perhaps fix this wording about best-effort
See the discussion at https://news.ycombinator.com/item?id=34580360 for some more insights.

See additional discussions and common questions:

https://discourse.ubuntu.com/t/why-is-extended-security-maintenance-needed-for-apps-in-ubuntu-20-04-x-lts-in-2021/25871/41
Only x86 architectures are supported for Ubuntu Pro

Another discussion: https://news.ycombinator.com/item?id=34605980

Filed a PR here: https://github.com/endoflife-date/endoflife.date/pull/2424
Feedback welcome.

PR merged, closing this issue.


feat: add ssz support to LC updates by range endpoint

Motivation

https://github.com/ChainSafe/lodestar/issues/6841

Description
Adds SSZ support to getLightClientUpdatesByRange endpoint as defined in spec
Closes https://github.com/ChainSafe/lodestar/issues/6841

:tada: This PR is included in v1.23.0 :tada:


Wearable producer does Not stream data with network instability

During the last experiments for the teleoperation, we were running HDE on a MAC machine which was connected through WiFi to yarpserver as mentioned #116, and the connection was unstable.
The problems we were observing were:

We should try several times to connect a source port in MAC to a destination port in iCub-head.
After running the experiment for some time, the controller was working (we could walk with the robot) but we could not teleoperate the upper body of the robot. After plotting, we saw the reference values for the joint torques were fixed with small oscillations.

Investigating more, we reached to the point that the data coming from the HDE is fixed. After talking with @diegoferigo  and talking with @Yeshasvitvs , we ran a number of experiments to simulate the instability of the network. If the connection is lost between wearable (Windows machine connected through LAN) and IWearRemapper (on MAC, connected by WiFi), still the IWearRemapper exposes the last received data (from the wearable producer) to the human state provider, and therefore the human state provider continues running and stream joint pose through the yarp network ports.
As @diegoferigo suggested we check for the yarpnetwork now in IWearRemapper as an optional solution to this problem here.
After running again the wearables and HDE, we observed the following behaviors:

If we stop the HDE (MacOS) (ctrl+C), the wearables (Winodws machine) continue to stream data as expected. It makes new tmp ports and write to them. We can access to the streamed data in different machine.

If we change the Mac connected network (manually connect to IIT network) so that the Mac Machine does not access to yarpserver, we see following behaviors:

The Wearables in Windows Machine stop streaming data (even in Windows we can not read data from Wearables), therefore we need to restart the wearables and calibrate again the XSens suit.

If we reconnect to icub-green  network, HDE still runs as before and streams fixed value even if there is a check the port connections here.

We did not define the sampling time in HDE, therfore it should be its default value. At the begining, when HDE is running correctly,  every 0.5-1 sec it calls the IWearRemapper::run(), but when the network is broken (and even after the reconnection to icub-green) for 3-5 times it calls the run method with the same rate, but later I will call the method every 20-60seconds.

@Yeshasvitvs Feel free to comment and add if sth is missing or inaccurate!
CC @DanielePucci  @diegoferigo  @Yeshasvitvs  @diegoferigo

The Wearables in Windows Machine stop streaming data (even in Windows we can not read data from Wearables), therefore we need to restart the wearables and calibrate again the XSens suit.

This is weird. So if you disconnect your pc (which is the consumer of the data) from the windows machine (which is the producer), then you cannot read the data neither from the producer?

If we reconnect to icub-green network, HDE still runs as before and streams fixed value even if there is a check the port connections here.

As we discussed f2f, this can be due to the fact the new data is not arriving, and IK still tries to find a solution with the last sample received. You told me that this data slightly varies and I suspect this is due to the IK solution that is not exactly the same at every iteration.

We did not define the sampling time in HDE, therfore it should be its default value.

I don't get what you mean here, all devices of HDE implement PeriodThread and they run typically at 100Hz, with the exception of HumanStateProvider.

At the begining, when HDE is running correctly, every 0.5-1 sec it calls the IWearRemapper::run()

This should not be called by classes attached to the remapper. run() is the implementation of PeriodicThread. Since the computation of the remapper is triggered by a callback on the input ports, the run() is a dummy method linked to a thread with the only purpose to keep the object alive.

This is weird. So if you disconnect your pc (which is the consumer of the data) from the windows machine (which is the producer), then you cannot read the data neither from the producer?

Yes, it is weird, but that is what we have observed.  cc @Yeshasvitvs

As we discussed f2f, this can be due to the fact the new data is not arriving, and IK still tries to find a solution with the last sample received. You told me that this data slightly varies and I suspect this is due to the IK solution that is not exactly the same at every iteration.

Yes, that is my impression as well.

I don't get what you mean here, all devices of HDE implement PeriodThread and they run typically at 100Hz, with the exception of HumanStateProvider.

I meant, we did not define its period in the application description file(xml file), therefore its period should be the default one. This means that run method of the IWearReampper should be called with 100Hz, am I right?

This should not be called by classes attached to the remapper. run() is the implementation of PeriodicThread. Since the computation of the remapper is triggered by a callback on the input ports, the run() is a dummy method linked to a thread with the only purpose to keep the object alive.

Thank you for correction, yes I remember from our talk! The run() method should be called every period sec even if it is dummy, am I right?

I meant, we did not define its period in the application description file(xml file), therefore its period should be the default one. This means that run method of the IWearReampper should be called with 100Hz, am I right?

No, it is called at 1 Hz. Since the method used to be dummy, this rate is hardcoded:
https://github.com/robotology-playground/wearables/blob/04dd8b2a31aa30e7a2ed3e8e7e9532af0e463ccc/devices/IWearRemapper/src/IWearRemapper.cpp#L112-L115

@kouroshD please update the relevant details on the changes made to address this issue.

I opened a PR here  to merge what we did to face the network instability.
Additionally, we increased the number of LAN ports, so that we do not have the instability. By closing the PR, we can close this issue.

Since we closed the PR, I close this issue. Now, we use the lan networks and we do not have any more the problem with the network.


Support for watchOS

Made changes to work with watchOS

Those removed parts with #if statement, didn't build for watchOS target at all.
UIApplication and LABiometryType are not supported by watchOS.
I changed to watchOS 7 because of os.Logger, that is supported from watchOS 7, but maybe we can keep watchOS 6 in case  someone wants to develop on that platform and just set watchOS support for the Logger. What do you think @jnutting?


Repeat Discover Error - "Error: send EACCES "

Hi,
When running my initial discovery of LIFX bulbs this library always works perfectly, however on the second check (test at both 1m and 10m later), it consistently causes the following error and never returns the object of devices. My bulbs are not on 255.
Error: send EACCES <IP_ADDRESS>:56700
    at doSend (dgram.js:683:16)
    at defaultTriggerAsyncIdScope (internal/async_hooks.js:313:12)
    at afterDns (dgram.js:629:5)
    at processTicksAndRejections (internal/process/task_queues.js:85:21)
    at runNextTicks (internal/process/task_queues.js:66:3)
    at processTimers (internal/timers.js:489:9) {
  errno: 'EACCES',
  code: 'EACCES',
  syscall: 'send',
  address: '<IP_ADDRESS>',
  port: 56700
}

Does anyone have any suggestions what may be causing this?

After a little more investigation it turns out the issue only occurred when running lifx.discovery alongside regular lifx.setColorFilter updates to the bulb. Some overlap between the functions must have caused the error. My workaround has been to pause updates via setColorFilter while the discovery function is running, although it doesn't quite solve the problem as this introduces a period where the lights are static.


Allow for parsing jsx

Allow for parsing jsx files via detective(src, { parse: { jsx: true } });
I wasn't sure how to best document this, so I left it undocumented for now.

Is there a reason why you don't transform the jsx into plain js first?

That's definitely a better approach.  Thanks for the suggestion, I'm embarrassed I didn't think to do that in the first place.

no worries!


Redesign the left panel

Feature Request
Description
[update: some of the configs have been redesigned for accessibility, here's the design updates that could be made to update the rest]

Make scrollbar invisible so that it doesn't shift the content as it appears
Ensure s and  have sufficient colour contrast, even when readOnly
Give  buttons the info icon (make sure it's aria-hidden) and apply the same button across all configurations
Give the model selection its own visibly distinct area (e.g. a fieldset like the others?)
Adjust the model configurations that have sliders (e.g. Model Temperature, Top P ...) so that they look like the other configurations (e.g. Prompt Evaluation LLM). it's already a , just needs the same border, headings and buttons.

Screenshot of suggested changes:

Acceptance criteria
UI design ticket, no code changes and therefore no testing.

@dhinrichs-scottlogic to update with latest state and ideas for improvement / UX input.

Like these 👍
Do we want to change slider colour to the theme teal at the same time? It's odd that they're the only green controls.

Like these 👍
Do we want to change slider colour to the theme teal at the same time? It's odd that they're the only green controls.

yes, I like this 🎨

do you mind if i take on this ticket?

I'm still thinking about the Details "buttons", and how the native element has an arrow visually indicating its current state. I think that would be clearer than an info icon.

Doro has indicated that screen readers can output some seriously long-winded description of the default arrows of <details> elements, so we might instead want to use our own unicode chars wrapped in an aria-ignored span.

I'm not a huge fan of conveying meaning through icons as they can be difficult to understand and have different meanings between cultures.
We could use text, but that would give screen reader users confusing info for the summary button: "Expand, button, collapsed", "Collapse, button, expanded".
This is why I opted for the outset vs inset border as this is closer to how we visually perceive objects in the natural world (e.g. a physical button in the real world that isn't pressed would stand out from the background, like an outset border, whereas a button pressed in would look pushed into the background, like an inset border) and therefore a bit more intuitive. If it's too difficult to see the difference, maybe could adjust the colour or shading to make it more clear.
If folks still don't like inset/outset borders and would rather have an icon, then that's alright, we can do that, I just have one more thought on this: The triangle as an indication between collapsed and expanded is not very clear, as the difference is only a few degrees of rotation, so can we make it an arrow instead?

@dhinrichs-scottlogic I just thought keeping it as close to the native <details> element as possible would be a good thing.

@dhinrichs-scottlogic I just thought keeping it as close to the native <details> element as possible would be a good thing.

You'd think so, but for our Defence Configuration  element we're getting (NVDA on Firefox):
"Filled right pointing small triangle Defence Configuration button collapsed.
If you remove the triangle element, like I did for the Details Button within the configurations, NVDA doesn't read out the triangle description, so you only get: "Details Button, collapsed".
If I hadn't removed the default triangle, it would be: "Filled right pointing small triangle details button collapsed".
I'd rather go with what would work best in practice, rather than going with the default.

Bouncing back to review as noticed in edge and chrome, Scroll bar makes panel space smaller while in firefox scroll bar is invisible

closing since work has been done