tests/kernel/device: extends test for code coverage

device_get_binding() compares pointers first before doing strcmp().
However, enabling coverage forces -O0 to disable any compiler
optimizations. There would be multiple copies of the same string,
and the code pathing doing pointer comparsion would not be tested
at all. So add this flag to merge string constants such that
the pointer comparison would be exercised.
This also adds a bad driver which fails initialization. This is
to make sure that execution path is covered.
Signed-off-by: Daniel Leung<EMAIL_ADDRESS>

Codecov Report

Merging #14995 into master will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #14995      +/-   ##
==========================================
+ Coverage   52.92%   52.94%   +0.01%
==========================================
  Files         309      309
  Lines       45266    45266
  Branches    10451    10451
==========================================
+ Hits        23955    23964       +9
+ Misses      16543    16539       -4
+ Partials     4768     4763       -5

Impacted Files
Coverage Δ

subsys/testsuite/ztest/src/ztest.c
72.72% <0%> (+4.13%)
:arrow_up:

kernel/device.c
97.77% <0%> (+8.88%)
:arrow_up:

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 500fa72...9f2c72c. Read the comment docs.


Fixed Utils.separated_str yielding first string by character

While unnoticeable with default config, this breaks GetAttr with compact set to True

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1106

Relevant Lines:
1106

💛  - Coveralls


Improve the fonts of the homepage

As a part of GSSOC'23, I would like to work on the font properties of the website to increase the readability. Kindly assign this issue to me.

assigned to @shruti8302
Complete this within 3-4 days and
Include a screenshot or deploy link to assess your project and thereafter include your project in the main code following the contributing.md guidelines.

@artimanputra Sure

@artimanputra Hey I want to ask that since I am just working on the font properties, can I just make changes in the main file itself but I will add the changes by creating another branch. I will then send u the screenshot of the website if u like it so u can merge it otherwise I will change them?


Support new NWC commands

This adds support for get_balance, get_info, make_invoice, and lookup_invoice.
Currently missing the multi commands as they'd require a larger refactor that I'd rather do as a follow up. Also left out keysends because that'd require a refactor for budgeting and list_transactions because I am not sure how we'd want to implement that while preserving privacy.
Closes #895

needs rebase

Failing tests

needs rebase

This adds support for get_balance, get_info, make_invoice, and lookup_invoice.
These should probably be allowed by default

These should probably be allowed by default

Done

Cool! How can I test this? do I need to create a new connection? I tried to create one and get "Unknown error occurred" - auto approve, 10000 sats, resets daily

This hasn't been deployed yet, should be by the end of the month

I tried the Mutiny latest update (PWA version) and am still having issues doing any requests outside of pay_invoice. Is it in this release?
I would love to see Mutiny working with some of the NWC-powered apps like the BuzzPay PoS https://github.com/getAlby/pos

If you make a new connection it should get the new commands.

I tried again today. make_invoice works, but lookup_invoice never seems to be updated so the PoS never gets a confirmation of the payment (it polls lookup_invoice). My mutiny wallet was open and I received the payment there.
I updated the PoS to be more relaxed and will show a confirmation rather than erroring if the wrong NWC permissions are given. You should be able to try it: https://github.com/getAlby/pos

In the logs I am getting these errors after it is paid, seems like something on your end, that error message isn't from us

@benthecarman that error happens when we get no reply from the wallet within a timeout. Can you check the reply payload you are sending?

hmm looks like rust-nostr is parsing for bolt11 but the spec is invoice :man_facepalming: my bad


purescm FFI for v6.0.0

Add foreign definitions (arrayExtend) and rebase all changes on top of v6.0.0.
Pending on some additions to the package-set.

Note that the test suite doesn't cover arrayExtend :| Seems that we have a lot of libs in core with no coverage.


vsock_proxy packaged with release v0.1.0 is buggy

It would be great to see next release soon, since vsock_proxy packaged with release v0.1.0
has bugs related to YAML allowlist parsing (it panics even with test config located in subdir).
vsock_proxy from main branch just works.

Our AL2 RPMs are at version 1.0, but it seems there are no equivalent github releases for them.

I've added Release and tag v1.0.10 to reflect the current AL2 release.


Updated libraries to use kotlin 1.6.10. With that upgraded every othe…

…r library I am using.

Fixes issue #23


Exception in initializing Routing Index Manager with version 7.5 on Ubuntu 18.04

What version of OR-tools and what language are you using?
Version: 7.5
Language: Java
Which solver are you using (e.g. CP-SAT, Routing Solver, GLOP, BOP, Gurobi)
Routing Solver
What operating system (Linux, Windows, ...) and version?
Linux Ubuntu 18.04
What did you do?
Try to initialize Routing Index Manager.
Steps to reproduce the behavior
Code Snippet:
       val dd = dataModel.timeDistancePair.first

        val manager = RoutingIndexManager(dd.size, dataModel.mDriverList.size, dataModel.depot)
        val routing = RoutingModelWithoutGC(manager)

        val longUnaryOperator = LongUnaryOperator { fromIndex: Long ->
            val fromNode = manager.indexToNode(fromIndex)
            dataModel.demands[fromNode]
        }
        val demandCallbackIndex = routing.registerUnaryTransitCallback(longUnaryOperator)

        /* ============= Start driver distance constraint from depot ==========*/

        val longBinaryOperator = LongBinaryOperator { left, right ->
            val fromNode = manager.indexToNode(left)
            val toNode = manager.indexToNode(right)
            dd[fromNode][toNode]
        }

        val transitCallbackIndex = routing.registerTransitCallback(longBinaryOperator)
        routing.setArcCostEvaluatorOfAllVehicles(transitCallbackIndex)
        /* ============= End driver distance constraint from depot ==========*/

        routing.addDimensionWithVehicleCapacity(
            demandCallbackIndex, 0, // null capacity slack
            dataModel.vehicleCapacities.toLongArray(), // vehicle maximum capacities
            true, // start cumul to zero
            "Capacity"
        )

        val searchParameters = main.defaultRoutingSearchParameters()
            .toBuilder()
            .setFirstSolutionStrategy(FirstSolutionStrategy.Value.PATH_CHEAPEST_ARC)
            .build()
        val solution = routing.solveWithParameters(searchParameters)`

What did you expect to see
What did you see instead?
Exception in thread "OkHttp Dispatcher" java.lang.NoSuchMethodError: SwigDirector_PathOperator_OnNodeInitialization
at com.google.ortools.constraintsolver.mainJNI.swig_module_init(Native Method)
at com.google.ortools.constraintsolver.mainJNI.(mainJNI.java:2452)
at com.google.ortools.constraintsolver.RoutingIndexManager.(RoutingIndexManager.java:46)
at com.x.y.z.solver.MySolver.orToolsSolver(MySolver.kt:142) This line is  (val manager = RoutingIndexManager(dd.size, dataModel.mDriverList.size, dataModel.depot))
Anything else we should know about your project / environment

There won't be any maintenance effort for the v7.5, please try to update to the last version and see if the problem still occurs.


Use of a key/value db (boltdb) for future implementations.

I'd like to propose the use of a key/value db https://github.com/boltdb/bolt for the future implementations (store, treestore, transport cache data etc...).
The idea started by some consideration:

ql is really good and its perfectly doing its job, but, like any sql, impose a strict schema
the strict schema makes adding new fields hard (schema migrations etc...). On the other side makes adding new indexes easier
since ql needs serialized rw and ro accesses it can become a bottleneck when a function needs to call it a lot of times. Additionally (but this will need a good benchmark to demonstrate it) looks like db opening (probably caused by wal replying) uses a little time/cpu (that can become noticeable when continuously opening/closing the ql db): https://github.com/coreos/rkt/pull/2891#issuecomment-232444145
Cannot remove data from the db when the disk is full #2782
If we design the data structures correctly (considereing the required queries types) we won't probably need the full sql power but we can just use a k/v db. See the treestore proposed implementation in #2972 that can also handle, for example, an additional non unique index.

Pros:

Faster db opening/closing. It's a memory mapped file without a wal.
Supports transactions. Useful for implementing multiple indexes.
Embedded multi process locking that can provide concurrent RO access (or single RW access). Since in rkt reads are much more than writes this can help (for example the api-service that does a lot of queries to the image and tree stores).
Schemaless: we can save in the value any byte array. The idea is to use json documents.
Schemaless: adding new fields to the document won't require migration steps.

Cons:

since bolt uses one memory mapped file, on 32 bit, there's a 2GB file size limit. I think it'll be hard to hit this limit.
being schemaless if there's the need to change a data type or add an index this must require an adhoc migration procedure.
sorting (now used in rkt image list) needs to be implemented (can't rely on sql "order by").
documents needs to be marshalled/unmarshalled (I'm not sure how it will be slow in regards to ql own marshalling/unmarshalling). With json we can improve performances using https://github.com/ugorji/go and, in addition use messagepack to save some space and gain another bit of performance (also implemented by https://github.com/ugorji/go/codec).

cc @coreos/rkt-maintainers @coreos/rkt-engineering

@sgotti thank you for the detailed analysis, I agree with most of the points and since we don't utilize SQL that much (sorting with order by), moving to a KV store like Bolt shouldn't present a challenge on that front.
cc @s-urbaniak as per the discussion we had OOB a while back

Concerns:

Going schemaless may cause issues on upgrade (when renaming fields, changing content's semantic and such)
BoltDB has its own non-LMDB interoperable binary format, so we are locking ourself into it
This is already a binary format, I don't see any gain in putting the value as JSON (messagepack suggestion seems more reasonable)

Non-concerns:

The mmap-limit doesn't look like a big issue
image-list sorting looks like an optional feature that we can get rid of, in case we need to

Summing up, I'm all in favour of moving to a KV system if it bring us more advantages than disadvantages. I would have liked some better interoperability options, but I think it's not going to happen. Maybe we should start from non-critical data (like, caching info) and see how it goes?

msgpack vs. JSON: In https://github.com/ugorji/go-codec-bench we should be aware that https://github.com/ugorji/go/codec has benefits mainly in the space domain, not so much in the time domain; i.e. pure serialization/deserialization will not be dramatically faster (also https://github.com/alecthomas/go_serialization_benchmarks has some data), hence I wouldn't demonize the JSON format.

:+1: on using BoltDB (also being used in Prometheus), I agree on the pros on this solution.

I do share the concerns being schemaless.

Some simple benchmarks to test the required multiple db open/close calls (https://github.com/sgotti/benchqldb):
BenchmarkQLEmptyROTx-8              5000            258400 ns/op
BenchmarkBoltEmptyROTx-8           50000             20732 ns/op
BenchmarkQLEmptyRWTx-8              5000            261734 ns/op
BenchmarkBoltEmptyRWTx-8<PHONE_NUMBER>5 ns/op
BenchmarkQLROTx-8                   1000           1342380 ns/op
BenchmarkBoltROTx-8                50000             30386 ns/op
BenchmarkQLRWTx-8                     50          38686667 ns/op
BenchmarkBoltRWTx-8<PHONE_NUMBER>7 ns/op

So looks like that just opening/closing the db using an empty (RO for bolt) transaction takes much less with bolt (with a bolt RW but empty tx it takes much more probably just due to the tx setup). Since the db will be opened and closed at every call (due to the multi process locking) this loos like a good win.
With some real transaction cases looks like RW transaction are similar while RO transactions are much better (part of the gain is always related to db opening/closing).

@sgotti Great job!

#3071

@sgotti what do you think about putting up the proposals/ doc from #3071 as a PR, which we can review/merge to close this issue, and then consider the implementation in #3071?

@jonboulle The initial implementation, before #3071, was done in #2972 for the new treestore. Is it ok if I take just the boltdb part from it (boltdb vendoring and boltdb manager) in its own PR?


🐛 cannot find symbol new CameraPackage() in PackageList.java [com.mrousavy.camera.example.CameraPackage]

What were you trying to do?
Just updated to<EMAIL_ADDRESS>and<EMAIL_ADDRESS>and got these 2 errors. I've also tried to manually link react-native-vision-camera by following the example on v3 branch with no luck. Am I missing something?
Reproduceable Code
No response
What happened instead?
Build failed with an exception.
Relevant log output
/Users/ali/Documents/flipnpik-mobile/android/app/build/generated/rncli/src/main/java/com/facebook/react/PackageList.java:85: error: cannot find symbol
import com.mrousavy.camera.example.CameraPackage;
                                  ^
  symbol:   class CameraPackage
  location: package com.mrousavy.camera.example
/Users/ali/Documents/flipnpik-mobile/android/app/build/generated/rncli/src/main/java/com/facebook/react/PackageList.java:170: error: cannot find symbol
      new CameraPackage(),
          ^
  symbol:   class CameraPackage
  location: class PackageList

Generated PackageList.java

package com.facebook.react;

import android.app.Application;
import android.content.Context;
import android.content.res.Resources;

import com.facebook.react.ReactPackage;
import com.facebook.react.shell.MainPackageConfig;
import com.facebook.react.shell.MainReactPackage;
import java.util.Arrays;
import java.util.ArrayList;

// @invertase/react-native-apple-authentication
import com.RNAppleAuthentication.AppleAuthenticationAndroidPackage;
// @react-native-async-storage/async-storage
import com.reactnativecommunity.asyncstorage.AsyncStoragePackage;
// @react-native-community/blur
import com.reactnativecommunity.blurview.BlurViewPackage;
// @react-native-community/datetimepicker
import com.reactcommunity.rndatetimepicker.RNDateTimePickerPackage;
// @react-native-community/geolocation
import com.reactnativecommunity.geolocation.GeolocationPackage;
// @react-native-community/netinfo
import com.reactnativecommunity.netinfo.NetInfoPackage;
// @react-native-firebase/analytics
import io.invertase.firebase.analytics.ReactNativeFirebaseAnalyticsPackage;
// @react-native-firebase/app
import io.invertase.firebase.app.ReactNativeFirebaseAppPackage;
// @react-native-firebase/crashlytics
import io.invertase.firebase.crashlytics.ReactNativeFirebaseCrashlyticsPackage;
// @react-native-firebase/messaging
import io.invertase.firebase.messaging.ReactNativeFirebaseMessagingPackage;
// @sentry/react-native
import io.sentry.react.RNSentryPackage;
// @shopify/react-native-skia
import com.shopify.reactnative.skia.RNSkiaPackage;
// lottie-react-native
import com.airbnb.android.react.lottie.LottiePackage;
// react-native-appsflyer
import com.appsflyer.reactnative.RNAppsFlyerPackage;
// react-native-contacts
import com.rt2zz.reactnativecontacts.ReactNativeContacts;
// react-native-fast-image
import com.dylanvann.fastimage.FastImageViewPackage;
// react-native-fbsdk
import com.facebook.reactnative.androidsdk.FBSDKPackage;
// react-native-gesture-handler
import com.swmansion.gesturehandler.RNGestureHandlerPackage;
// react-native-image-crop-picker
import com.reactnative.ivpusic.imagepicker.PickerPackage;
// react-native-image-picker
import com.imagepicker.ImagePickerPackage;
// react-native-linear-gradient
import com.BV.LinearGradient.LinearGradientPackage;
// react-native-localize
import com.zoontek.rnlocalize.RNLocalizePackage;
// react-native-maps
import com.airbnb.android.react.maps.MapsPackage;
// react-native-navigation
import com.reactnativenavigation.react.NavigationPackage;
// react-native-otp-verify
import com.faizal.OtpVerify.RNOtpVerifyPackage;
// react-native-pager-view
import com.reactnativepagerview.PagerViewPackage;
// react-native-permissions
import com.zoontek.rnpermissions.RNPermissionsPackage;
// react-native-push-notification
import com.dieam.reactnativepushnotification.ReactNativePushNotificationPackage;
// react-native-reanimated
import com.swmansion.reanimated.ReanimatedPackage;
// react-native-safe-area-context
import com.th3rdwave.safeareacontext.SafeAreaContextPackage;
// react-native-share
import cl.json.RNSharePackage;
// react-native-sound
import com.zmxv.RNSound.RNSoundPackage;
// react-native-splash-screen
import org.devio.rn.splashscreen.SplashScreenReactPackage;
// react-native-svg
import com.horcrux.svg.SvgPackage;
// react-native-vector-icons
import com.oblador.vectoricons.VectorIconsPackage;
// react-native-vision-camera
import com.mrousavy.camera.example.CameraPackage;
// react-native-webview
import com.reactnativecommunity.webview.RNCWebViewPackage;
// react-native-worklets
import com.worklets.WorkletsPackage;

public class PackageList {
  private Application application;
  private ReactNativeHost reactNativeHost;
  private MainPackageConfig mConfig;

  public PackageList(ReactNativeHost reactNativeHost) {
    this(reactNativeHost, null);
  }

  public PackageList(Application application) {
    this(application, null);
  }

  public PackageList(ReactNativeHost reactNativeHost, MainPackageConfig config) {
    this.reactNativeHost = reactNativeHost;
    mConfig = config;
  }

  public PackageList(Application application, MainPackageConfig config) {
    this.reactNativeHost = null;
    this.application = application;
    mConfig = config;
  }

  private ReactNativeHost getReactNativeHost() {
    return this.reactNativeHost;
  }

  private Resources getResources() {
    return this.getApplication().getResources();
  }

  private Application getApplication() {
    if (this.reactNativeHost == null) return this.application;
    return this.reactNativeHost.getApplication();
  }

  private Context getApplicationContext() {
    return this.getApplication().getApplicationContext();
  }

  public ArrayList<ReactPackage> getPackages() {
    return new ArrayList<>(Arrays.<ReactPackage>asList(
      new MainReactPackage(mConfig),
      new AppleAuthenticationAndroidPackage(),
      new AsyncStoragePackage(),
      new BlurViewPackage(),
      new RNDateTimePickerPackage(),
      new GeolocationPackage(),
      new NetInfoPackage(),
      new ReactNativeFirebaseAnalyticsPackage(),
      new ReactNativeFirebaseAppPackage(),
      new ReactNativeFirebaseCrashlyticsPackage(),
      new ReactNativeFirebaseMessagingPackage(),
      new RNSentryPackage(),
      new RNSkiaPackage(),
      new LottiePackage(),
      new RNAppsFlyerPackage(),
      new ReactNativeContacts(),
      new FastImageViewPackage(),
      new FBSDKPackage(),
      new RNGestureHandlerPackage(),
      new PickerPackage(),
      new ImagePickerPackage(),
      new LinearGradientPackage(),
      new RNLocalizePackage(),
      new MapsPackage(),
      new NavigationPackage(reactNativeHost),
      new RNOtpVerifyPackage(),
      new PagerViewPackage(),
      new RNPermissionsPackage(),
      new ReactNativePushNotificationPackage(),
      new ReanimatedPackage(),
      new SafeAreaContextPackage(),
      new RNSharePackage(),
      new RNSoundPackage(),
      new SplashScreenReactPackage(),
      new SvgPackage(),
      new VectorIconsPackage(),
      new CameraPackage(),
      new RNCWebViewPackage(),
      new WorkletsPackage()
    ));
  }
}

Device
Android Emulator (API 29)
VisionCamera Version
3.0.0-rc.2
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

@AliMSbaee how were you able to fix this?

install from v3 branch
npm install "https://github.com/mrousavy/react-native-vision-camera.git#v3" --save

did you have any issues installing worklets?

@hkeithk
ty to install worklets from here https://github.com/chrfalch/react-native-worklets#d62d76c

@AliMSbaee how were you able to fix this?

install from v3 branch npm install "https://github.com/mrousavy/react-native-vision-camera.git#v3" --save

I received error:
Cannot find module 'react-native-vision-camera' or its corresponding type declarations

Hello,
I had the same issue using 3.0.0-rc.2 and it looks like there is a small typo in the AndroidManifest.xml file, here is my patch:
diff --git a/node_modules/react-native-vision-camera/android/src/main/AndroidManifest.xml b/node_modules/react-native-vision-camera/android/src/main/AndroidManifest.xml
index 2906763..f5a395b 100644
--- a/node_modules/react-native-vision-camera/android/src/main/AndroidManifest.xml
+++ b/node_modules/react-native-vision-camera/android/src/main/AndroidManifest.xml
@@ -1,4 +1,4 @@
 <manifest xmlns:android="http://schemas.android.com/apk/res/android"
-          package="com.mrousavy.camera.example">
+          package="com.mrousavy.camera">

 </manifest>

I can successfully build on Android after fixing that. Hope this can help some of you :)
Best regards.

Hey! I've rewritten the entire Android codebase of VisionCamera from CameraX to Camera2 in the efforts of ✨ VisionCamera V3.
I just now completed the Camera2 rewrite and I believe the core structure is running, but there might be some edge cases to iron out. Can you try and test the PR #1674 for me to see if you can still reproduce this issue here?
Here's an instruction on how you can test that: https://github.com/mrousavy/react-native-vision-camera/pull/1674#issuecomment-1684104217
If the issue cannot be reproduced with that version/PR anymore, then hoorayy, I fixed it! 🎉
Otherwise please let me know and I'll keep this issue open to keep track of it.
Thank you!


Vercel + Astro image compressions error

Turning on Astro's Vercel Adapter option for imageService to true returns can't find img error.
e.g.
Can't find img on disk src="/_vercel/image?examplepath"

Hi! Can you share a real life HTML extract with images so I can understand how the Vercel adapter does things here?

Sure thing, an img in my html output currently looks like this:
<img src="/_vercel/image?url=https%3A%2F%2Fwww.xxxx.com.au%2Fwp-content%2Fuploads%2Fsites%2F2%2F2023%2F08%2Fxxxx_dry_can_noShadow.png&w=640&q=100" title="xxxx_dry_can_noShadow.png" alt="xxxx_dry_can_noShadow.png" loading="lazy" width="auto" height="auto" decoding="async">
Let me know if there's anything else I can provide to help with this

Hello, did you fix the issue ?
If no, can you share me you're astro.config.* ?

New release 0.24.4 can exclude some src urls.
By default, /vercel/image?... is ignored now.


Exception when using user defined class with stl containers as attribute

May suggest a test that fails?
Insert a vector as an attribute
struct leak_checker {
leak_checker() { ++num_constructions; }

~leak_checker() { ++num_deletions; }

leak_checker(const leak_checker&) { ++num_constructions; }

leak_checker(leak_checker&&) { ++num_constructions; }

leak_checker& operator=(const leak_checker&) = default;
leak_checker& operator=(leak_checker&&) = default;

std::vector<float> numbers;

};

Really sorry for the inconveniences. Personally used the library only for POD structs and had no problems.
I am not sure about which test are you talking about though as there was an error for me which I fixed. Can you check if it is all OK now?

I just updated the repo code and test it again. It failed at the first test called "quick test for leaks".
Please, see the message below
projectd.exe is a Catch v1.9.6 host application.
Run with -? for options

-------------------------------------------------------------------------------
quick test for leaks
-------------------------------------------------------------------------------
c:\users\diego\projects\circular_buffer.git\test\main.cpp(51)
...............................................................................

c:\users\diego\projects\circular_buffer.git\test\main.cpp(63): FAILED:
  REQUIRE( num_constructions == num_deletions )
with expansion:
  138 == 132
with message:
  constructions: 138deletions: 132

===============================================================================
test cases:    19 |    18 passed | 1 failed
assertions: 36519 | 36518 passed | 1 failed

Pressione qualquer tecla para continuar. . .

yep fixed

Great job
Thank you
Em qui, 12 de jul de 2018 às 16:00, Justas Masiulis <
<EMAIL_ADDRESS>escreveu:

yep fixed
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/JustasMasiulis/circular_buffer/issues/3#issuecomment-404616332,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFpfhmAmf_X1Av-BIeZH4VyGFS1dL1c6ks5uF5y0gaJpZM4VKMPd
.


feat(maintenance): structured folder

Related Issue

Unstructured folder

Closes: #62
Describe the changes you've made
I have created a new folder with the proper names and put the files there. Maintained all the routes and functionalities working with proper functioning with correct importing and exporting.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Enhancement in the existing features
[x] Other

Mention any unusual behaviour of your code (Write NA if not)
Any unusual behaviour of your code
Checklist:

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly whereever it was hard to understand.
[x] My changes generate no new warnings.
[x] I have verified/tested my code by running it locally.

Files Added/Modified

model
db
utilits
controller

Screenshots / Videos / Gif

Additional Info (optional)

One error in model of doctor of missing comma which has been rectified.

hey @SnehaJaiswal123 can you resolve the conflicts? since the code was just updated, thanks

Hey @apeksha235 I am not getting your point. My issue was to update the server folder in the structured manner and that I have done.


"Ocoliș" is listed in the drop-down menu

Description:
"Ocoliș" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Ocoliș" in the search bar.

Expected results
The location is listed in the drop-down menu as "Ocoliș, Alba (Ocoliș)".


Update Townhall documentation to alert that "New Teams" is required to Join / Host events

Right now the documentation for the TownHall feature in Microsoft Teams that was recently release has no mention that you MUST have the New Teams client for the event to work.
https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/blob/public/Teams/plan-town-halls.md
Please add a banner to draw attention to this fact so users are aware that a migration to the new teams is a necessary action.
https://answers.microsoft.com/en-us/msteams/forum/all/town-hall-attendees-cant-sign-in-using-teams/363e2bed-8334-473f-b3ff-6ec7a6536a89#:~:text=Correct%2C town hall requires the,Sorry.

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.
As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.
If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.
With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.
Here's what the new experience looks like.
Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.
First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful
Article was unhelpful

Finally, select Submit and you're done!


Make ServerBuilder public

The Server::builder() method returns a ServerBuilder, but the type isn't public, so there's no way to see the constructor in the docs.

Closed in https://github.com/penumbra-zone/tower-abci/pull/25/files#diff-b1a35a68f14e696205874893c07fd24fdb88882b47c23cc0e0c80a30c7d53759R16


Fix build on FreeBSD

Fix _make_posix_spawn_file_actions_t and _make_pthread_t functions for FreeBSD. On FreBSD pthread_t and posix_spawn_file_actions_t are opaque pointers so they should be initialized with nil as on Darwin

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    OS X platform               | @swift-ci Please test OS X platform
    Linux platform              | @swift-ci Please test Linux platform

Note: Only members of the Apple organization can trigger swift-ci.

We could consolidate this the other way by making the types NilLiteralConvertible on all platforms, maybe.

@swift-ci Please test and merge


Updated Terraform deployment artifacts and instructions.

Made several updates to the Terraform deployment artifacts.

Update README.md:

Added instructions to create storage account for Terraform deployment.
Added instruction to create service principle with specific scope for AKS.
Added instructions related to destroy (or teardown) of Azure resources.
Added troubleshooting section.

Removed the reference of service principal from setup.sh for event hub, acr and azure storage.

All Submissions:

[X] Have you followed the guidelines in our Contributing document?
[X] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[X] Does your PR follow our Code of Conduct?
[X] Have you added an explanation of what your changes do and why you'd like us to include them?
[X] Does each method or function "do one thing well"? Reviewers may recommend methods be split up for maintainability and testability.
[X] Is this code designed to be testable?
[X] Is the code documented well?
[X] Does your submission pass existing tests (or update existing tests with documentation regarding the change)?
[X] Have you added tests to cover your changes?
[X] Have you linted your code prior to submission?
[X] Have you updated the documentation and README?
[X] Is PII treated correctly? In particular, make sure the code is not logging objects or strings that might contain PII (e.g. request headers).
[X] Have secrets been stripped before committing?

Nice additions to the Readme .. did you get a chance to test whether the deployments recreated as expected?

@margaretmeehan  If you are asking about the recreation of artifacts after a complete teardown then I did test that part.


Update 4v4 names

Add keys for leaderboards and convert queue names to snake case

Is this settled?

I would guess so. There hasn't been any movement in https://github.com/FAForever/db/pull/290 recently. I'm under the impression that it is ready, but the safe bet is probably to wait until that pr is merged


Fix build error around  src/context.ts:42:14 getUser(): user {

This PR fixes following error.
% npm run build

><EMAIL_ADDRESS>prebuild /xxx/clova-cek-sdk-nodejs
> rimraf dist

><EMAIL_ADDRESS>build /xxx/clova-cek-sdk-nodejs
> tsc --module commonjs && rollup -c rollup.config.ts && typedoc --out docs --target es6 --theme minimal --mode file src

src/context.ts:42:14 - error TS2304: Cannot find name 'user'.

42   getUser(): user {
                ~~~~

src/context.ts:42:14 - error TS4055: Return type of public method from exported class has or is using private name 'user'.

42   getUser(): user {
                ~~~~

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: `tsc --module commonjs && rollup -c rollup.config.ts && typedoc --out docs --target es6 --theme minimal --mode file src`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/JP20217/.npm/_logs/2018-08-26T02_22_07_219Z-debug.log
zsh: exit 1     npm run build

@shamenchens, @ozyozyo  I'm not familiar with nodejs but looks like https://github.com/line/clova-cek-sdk-nodejs/pull/3 brokes master branch.
Could you check it?

Ahh my bad, didn't notice this, thanks!


Implement Helm < 1.0.0 functionality as 3rd party libraries

With Helm 1.0.0, I got rid of a bit of the old functionality that didn't mesh with the subscription/command style. It'd be cool to see the following old core features be re-implemented as third party libraries:

FRP.Helm.Random: RNG that interacts with subscriptions/commands. It might be cool to have a subscription that triggers event randomly (although obviously it would need some use).
FRP.Helm.Automaton: it'd be cool to see something like the old automaton that works nicely with subs/commands.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

After further thought:

Cmd.execute is perfectly capable of running any of the random package's functions in the context of Helm
Automaton is unnecessary in the current version of Helm


Increase memory when bbduk runs out

bbduk can use a lot of memory and that can cause it to fail, especially in a shared computing environment like an HPC. Detect this, and auto increase the amount of memory reserved for the task then rerun the process. Additionally, increase the default memory reservation.

The command exit status of the bbduk process is 1, if it runs out of memory

#101 fixes this issue with BBDUK


Changed ObjectMapper configuration for deployment on Dell Boomi Cloud platform

Dell Boomi does not allow java to override access modifiers when using reflection. Therefore, added the following ObjectMapper configuration in the JWTParser.java class:
mapper.configure(MapperFeature.CAN_OVERRIDE_ACCESS_MODIFIERS, false);
Unit tests are running successfully.

That flag doesn't seem harmful so I'm fine with it. docs
But please, remove all the files in the PR and keep only the actual change in JWTParser. They are related to the IDE you're using. You can include these rules in the .gitignore file to prevent it. https://www.gitignore.io/api/eclipse

Changed PR with 1 source file that has been changed.

Modified the pull request. Why has the PR not been processed yet?

When will this one been processed?

I was waiting for the codecov checks to pass, but as far as I see something is broken and the upload fails if the last commit on the PR is part of a rebase.
Checking again the documentation on that flag it points out possible performance issues. I'll need to assert this impact before merging the PR.

Note that this setting may have significant performance implications, since access override helps remove costly access checks on each and every Reflection access. If you are considering disabling this feature, be sure to verify performance consequences if usage is performance sensitive

@mennodehaas any feedback/clue on the performance impact this flag has?
@skjolber While that can work and will be the preferred option for many devs, we don't want to expose external libraries' classes on the public API.

@lbalmaceda I created a quick performance benchmark on my machine generating 10.000 tokens and decoding 10.000 tokens.
java-jwt-3.3.0 release
Generated 10000 tokens in 1126 ms (0.1126 ms per token)
Decoded 10000 tokens in 964 ms (0.0964 ms per token)
java-jwt-3.3.0 release with mapper.configure(MapperFeature.CAN_OVERRIDE_ACCESS_MODIFIERS, false);
Generated 10000 tokens in 1238 ms (0.1238 ms per token)
Decoded 10000 tokens in 859 ms (0.0859 ms per token)

I'll share a JMH project later today for benchmarks / experiments. I suspect the impact of this issue will be low.

@mennodehaas try measuring using this: https://github.com/skjolber/java-jwt-benchmark
First run
./gradlew clean build  publishToMavenLocal
on the modified java-jwt project.

@skjolber what are the results? I don't have experience running JMH benchmarks.

Seems the performance impact is low, under a percent.

What is the progress on this PR?


Can't control kernel module load order

Description:
I would like to make sure that the kernel modules 'pci_stub' and 'vfio_pci' are loaded and initialized before 'nvidia' and it's kin. Setting the oder in `boot.kernelModules' seems to have no affect.
http://nixpaste.lbr.uno/II3eDmPW
Version info:
nixos-version
16.03.1287.6ac7ffd (Emu)
nix-env --version
nix-env (Nix) 1.11.2
Relevant configuration:
/etc/nixos/configuration.nix (truncated)
  # ... snip ...
  boot.kernelModules = [
    "pci_stub"
    "vfio"
    "vfio_iommu_type1"
    "vfio_pci"
    "nvidia"
    "nvidia_uvm"
  ];

  #boot.blacklistedKernelModules = [ "nouveau" "nvidia" ];

  boot.extraKernelParams = [
    "intel_iommu=on"
    "vfio_iommu_type1.allow_unsafe_interrupts=1"

    # Add GTX 1080 to vfio-pci
    "pci-stub.ids=10de:1b80,10de:10f0"
    "vfio-pci.ids=10de:1b80,10de:10f0"

    "kvm.allow_unsafe_assigned_interrupts=1"
    "kvm.ignore_msrs=1"

  ];
  # ... snip ...
  # Enable the X11 windowing system.
  services.xserver = {
    enable = true;
    layout = "us";
    videoDrivers = [ "nvidia" ];

    displayManager.slim.enable = true;

    desktopManager = {
      gnome3.enable = true;
      default = "gnome3";
    };

  };

An update on this, I was able to get pci-stub to bind to the desired graphics card by adding the kernel module to the boot.initrd.kernelModules so that it loads before any other modules. Reading through the systemd notes on kernel module initialization it may not be possible to have any more fine-grained control than this.


Cancel event drag&drop and resize

Is it possible to cancel event drag/drop? I need it in the following scenario: after an event is updated, an external api is called, and if that fails, the edit must be reverted

I have a similar problem, on event-drop, I check if there is an overlap, if there is, I need to cancel the event.

Is it possible to cancel event drag/drop? I need it in the following scenario: after an event is updated, an external api is called, and if that fails, the edit must be reverted

I've added a key ref to the calendar and I increment it when there is a conflict, it refreshes the calendar and since i didn't modify the event in the database it goes back to it's original position.

You can save the delete function in a variable and call it at the end of the drag if you want to return the slot to its initial position
onEventCreate (event, deleteEventFunction) {
this.deleteEventFunction = deleteEventFunction;
// code
}
onDrag (event) {
// code ...
this.deleteEventFunction ()
}
or if you use
@event-duration-change = "eventResizeOrDrop ($event)"
@ event-drop = "eventResizeOrDrop($event)"
you can reassign the old one to the new event
eventResizeOrDrop ({originalEvent, event}) {
//code...
let eventToRevert = this.events.find ( (el) => el.eventId == originalEvent.eventId);
eventToChange.start = new Date(originalEvent.start);
eventToChange.end = new Date(originalEvent.end);
}


Bug: Generating invalid TS code

What are the steps to reproduce this issue?

Prepare JSON input for orval which is a swagger output with following data:

{
  "/health/live": {
    "get": {
      "operationId": "HealthController_checkLiveness",
      "summary": "Live check",
      "parameters": [],
      "responses": {
        "200": {
          "description": "The Health Check is successful",
          "content": {
            "application/json": {
              "schema": {
                "type": "object",
                "properties": {
                  // other properties not significant for this use case
                  "details": {
                    "type": "object",
                    "example": {
                      "database": {
                        "status": "up"
                      }
                    },
                    "additionalProperties": {
                      "type": "object",
                      "properties": {
                        "status": {
                          "type": "string"
                        }
                      },
                      "additionalProperties": {
                        "type": "string"
                      }
                    }
                  }
                }
              }
            }
          }
        }
      }
    }
  }
}

What happens?
Generated code from orval looks like this:
export type HealthControllerCheckLiveness200Details = {
  [key: string]: {
    status?: string;
    [key: string]: string;
  };
};

Which is an invalid TypeScript code.
What were you expecting to happen?
Status shouldn't be optional
Any logs, error output, etc?
Property 'status' of type 'string | undefined' is not assignable to 'string' index type 'string'.(2411)
Any other comments?
TypeScript version: 4.7.3
What versions are you using?
6.8.1
Operating System: MacOS Monterey 12.4
Package Version: 6.8.1
Browser Version: Chrome 102.0.5005.61

Can you try 6.24.0 and report if it is still an issue?


PHEONIX-5243: PhoenixResultSet#next() closes the result set if scanner returns null

@twdsilva @ChinmaySKulkarni Could you please review this?

lgtm


Avatar Image

Is it possible to show the user instagram avatar/profile image next to the post?
My current code is as follows;
var userFeed = new Instafeed({
    get: 'user',
    userId: my_user_id,
    accessToken: 'my_token'
});,
template: ''
userFeed.run();

Thanks,
J

Yes, you can use  in your template to display the users profile picture!
For a complete list of properties that are under model see #21.

Excellent thanks for this plugin :)

Hi @stevenschobert ,
Great Extension!!! I tried to get profile picture from above mentioned approach using {{model.user.profile_picture}} in template but how can i get the profile picture only once, right now it is repeating with every post being pulled.
How can I get the profile only once?

Hi @johnnydevs @stevenschobert ,
I could retrieve bio from {{model.user.bio}}. Is this depricated?? I read API documentation from instagram and it suggest we could use "users/self/" endpoint to get data. I could get response of bio if i hit "https://api.instagram.com/v1/users/self/?access_token=ACCESS_TOKEN" .
How can I get it through this plugin??
Any idea?? I am stuck as I am using this for shopify and i can do cross platform request for AJAX.
Please help me!!!

Merhaba @stevenschobert ,
Büyük Uzatma !!! Şablonda {{model.user.profile_picture}} şablonunu kullanarak yukarıda belirtilen yaklaşımdan profil resmi almaya çalıştım, ancak profil resmini yalnızca bir kez nasıl alabilirim, şu anda her yazı çekildiğinde tekrar ediyor.
Profili yalnızca bir kez nasıl alabilirim?

Please reply, how it is made?

Hi @Serk4n,
I auto-translated your question, hopefully this is reasonable!

I tried to retrieve a profile picture from the above approach using the template {{model.user.profile_picture}} in the template, but how do I get the profile picture only once, it is repeating every time a post is drawn. How can I get the profile only once?

The template is used to render each Instagram post retrieved, so if you include {{model.user.profile_picture}}, you will see it displayed multiple times.
Instead, you can access the profile picture URL directly in javascript using the .success callback (see Advanced Options in the project README) and then accessing the user profile to get the image. See issue #21 for a reference to the properties of the image model.

Thanks @benjamin-hull


Is Mixed Chart Types Supported ?

As char.js documentation suggests a way of using mixed charts - https://www.chartjs.org/docs/latest/charts/mixed.html.
Is that supported here ?

Hello! No i don't think it's supported but it's a great feature to add!
I will work on a MixedChart component

@Manu-jayaprakash Sorry for the long wait.
After looking at it, it may be already supported!
Just use any Chart component you want in priority, and define mixed data with the chart-data prop!
https://codesandbox.io/s/demo-vue-chart-3-forked-e3yz2?file=/src/App.vue


Self-referential structs.

To do a typical self-referentially defined structure in C you typically have to do the following:
struct node; /* This is necessary ... */
struct node {
    char msg[128];
    struct node* next; /* ... so that the compiler knows what this is */
};

So the question is, why not make it so that in Nymph all named structs are scanned for and then just declared in bare format at the top of the preprocessed C file, so that you can omit this seemingly unnecessary redundant empty code from the user.

@websnarf
This is technically already implemented.
What I want to be able to do is this.
struct node {
    char msg[128];
    struct node next; /* ... so that the compiler knows what this is */
};


Not working HMR when edit scss file with css modules

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

Bug

Expected Behavior
I edit scss file, save it and styles in browser are changing.
Actual Behavior
I edit scss file, save it and in browser it happens nothing. I should reload page in beowser and only after this styles are applied.
Your Environment

Mac OS Sierra.
The latest Chrome.
Version of node - 10.0.0

@TotallWAR css/sass hot reloading is support in v2.6.0

Great! It works. Thank you!


Use a template to generate docker.list

The travis log is super weird. Going to restart the build see if output is different.

While I re-run and analyze I wonder if #4 will help.

I think we're going to need a vagrant file to test this. Such as on ansible-mesos. See Vagrantfile.


No indication that request to unlock publishing was previously submitted

Description
Once a request to publish has been submitted there is no feedback for users meaning they might be confused and resubmit multiple unlocking requests.
Steps to reproduce

Create an account
Unlock publishing
Create a form
Go to Settings
Unlock publishing (can do this multiple times)

Details

Browser: Edge
Operating system: Windows
Environment: App router PR
Language: French
Viewport: Tablet 100%

Expected behaviour
Feedback that the request is pending? Or that it has been submitted? Perhaps with a service standard or next step?
Screenshots or videos

@Abi-Nada @anikbrazeau
I believe this is the case with current staging as well --- the app currently isn't aware that a request was sent for publishing.
Can we look at how to fix outside of the app router branch?

+1 - it's good we have it noted as a bug, but let's descope this from the app router work for now. We'll keep it in New Issues with the bug label, but I'll take it out of the App Router epics


Question: Personaname to Friend ID?

HI,
can I convert PersonaName to FriendID? I don't find such a such in the code.
Greetings Björn,

Don't think it's possible. Persona names are not unique afaik, so it would be impossible to divine which id corresponds to one..

But if I click on guy's name in a chat, the official client referse to his profile. So there must be a thing how to get to this.

That's because the the object you're clicking is associated with the accountid of that user. The reborn client asks the GC the user list for the channel, which responds with a list of user objects.  Each one of those contains among others the account id and persona name of each user. The reborn client creates a panel for each user which shows the persona name, but is linked to the I'd as well. At no point does the client need to make the persona to account transformation, since both are kept in the same place. Take a look at chat.js in handlers and the protobuf related to chat. You'll see the info the client gets

Ok, I can get this if people joining (regarding to onOtherJoining), but I can't get this list on my own?

When your bot itself joins the chat channel, you receive a list of all people currently in the channel, it's in the response.  Then there's also the following functions (which haven't been implemented yet, so feel free to contribute):

CMsgDOTAChatGetUserList -> k_EMsgDOTAChatGetUserList
CMsgDOTAChatGetUserListResponse -> k_EMsgDOTAChatGetUserListResponse
CMsgClientToGCPrivateChatInfoRequest -> k_EMsgClientToGCPrivateChatInfoRequest
CMsgGCToClientPrivateChatInfoResponse -> k_EMsgClientToGCPrivateChatInfoResponse

I did some tinkering with k_EMsgDOTAChatGetUserList but it doesn't seem to return anything. On the other hand, node-dota2 automatically keeps track of all people joining and leaving the channel. The chatChannels property contains an array of all chat channels you've joined, with their current member list.


luci-app-statistics: weekly graphs are sometimes plotted with very few data points

Sometimes, weekly graphs are plotted with very few data points used on the x-axis. Daily and hourly graphs look fine.

There is nothing suspicious about the rrd database itself.

I have noticed the same since the move to JS based graphs, but the graphs have always corrected themselves after vising a few other apps & tabs. I think that I have also seen that happening also with the daily graph.
Apparently some times the timescale index gets somehow skewed by one, and the data for the next longer time period is used instead of the correct one (thus reducing the amount of data points).
So far I have not been able to figure out the reason.

I've noticed as well that the issue corrects itself after a few hours. When the bug manifests itself, all weekly graphs are affected. What does not work is emptying the image cache in /tmp/rrdimg, the recalculated graphs look just as before.

Try playing with the -s and -e value here when this happens: https://github.com/openwrt/luci/blob/master/applications/luci-app-statistics/htdocs/luci-static/resources/statistics/rrdtool.js#L337
The -e was an addition I made when converting to the client side, the intent here was avoiding an open gap at the graph end when displaying the hourly graph. Maybe it has a negative effect on long time range renderings.

Thanks for the hint about the change you made in the JS transition.  I will try to figure it out the next time.
Comparing master to the 19.07 code, there is that -e addition, but apparently there is not much more relevant difference.
The -e is always "NOW - 60 seconds". The time scale makes no difference, so even in the weekly data, the required scale is upto this minute (instead of scaled like NOW - 2 hours ago).
Based on that, a guess of the possible situation:

Possibly rrdtool automatically determines the suitable data table based on the length of the required period.
Earlier it was given NOW-week as start and automatic end(?)
Now it gets NOW-week and NOW-60sec.  Maybe that time period is slightly longer than the data found in the averaged data table in RRD.  Maybe we would need 102 data items, but the daily data only has 100 items. So rrdtool switches to the next longer period and uses the monthly data for the week table.

Or something similar.  The earliest required data just goes beyond the data in the table?
I have a hunch that we should either have a few items more in the RRD tables
(currently 100, in practice there seems to be 101-120 items...)
root@router1:~# rrdtool info /tmp/rrd/router1/entropy/entropy.rrd
filename = "/tmp/rrd/router1/entropy/entropy.rrd"
rrd_version = "0001"
step = 30
last_update =<PHONE_NUMBER>
ds[value].type = "GAUGE"
ds[value].minimal_heartbeat = 60
ds[value].min = 0.0000000000e+00
ds[value].max = 4.2949672950e+09
ds[value].last_ds = "UNKN"
ds[value].value = 2.2544000000e+04
ds[value].unknown_sec = 0
rra[0].cf = "AVERAGE"
rra[0].rows = 120
rra[0].pdp_per_row = 1
rra[0].xff = 1.0000000000e-01
rra[0].cdp_prep[0].value = NaN
rra[0].cdp_prep[0].unknown_datapoints = 0
rra[1].cf = "AVERAGE"
rra[1].rows = 103
rra[1].pdp_per_row = 28
rra[1].xff = 1.0000000000e-01
rra[1].cdp_prep[0].value = 2.0634933333e+04
rra[1].cdp_prep[0].unknown_datapoints = 0
rra[2].cf = "AVERAGE"
rra[2].rows = 101
rra[2].pdp_per_row = 201
rra[2].xff = 1.0000000000e-01
rra[2].cdp_prep[0].value = 5.4665333333e+03
rra[2].cdp_prep[0].unknown_datapoints = 0
rra[3].cf = "AVERAGE"
rra[3].rows = 101
rra[3].pdp_per_row = 892
rra[3].xff = 1.0000000000e-01
rra[3].cdp_prep[0].value = 5.4144620000e+05
rra[3].cdp_prep[0].unknown_datapoints = 0
rra[4].cf = "AVERAGE"
rra[4].rows = 101
rra[4].pdp_per_row = 10540
rra[4].xff = 1.0000000000e-01
rra[4].cdp_prep[0].value = 5.2331778667e+06
rra[4].cdp_prep[0].unknown_datapoints = 3357

Right now the graph suddenly switched to displaying longer period data:
Time is 22:27 and the oldest data in daily table is from yesterday 22:40

Now time is 22:30 and graph is again ok:

A few minutes earlier there was still 22:26 data item from yesterday and the graph was ok, but once that disappeared, the graph got wrong for 1-2 minutes (wrong maybe between 22:28-22:29).
                <database>
                        <!-- 2020-05-16 22:26:00 EEST /<PHONE_NUMBER> --> <row><v> 2.0638047619e+03 </v></row>
                        <!-- 2020-05-16 22:40:00 EEST /<PHONE_NUMBER> --> <row><v> 1.9962452381e+03 </v></row>

After update
                <database>
                        <!-- 2020-05-16 22:40:00 EEST /<PHONE_NUMBER> --> <row><v> 1.9962452381e+03 </v></row>
                        <!-- 2020-05-16 22:54:00 EEST /<PHONE_NUMBER> --> <row><v> 1.8190857143e+03 </v></row>
                        <!-- 2020-05-16 23:08:00 EEST /<PHONE_NUMBER> --> <row><v> 1.6542809524e+03 </v></row>

My guess is that the rough data granularity set by us, only 100 data items, plays wrong for some short periods when the nearest data point of the required start time gets calculated.  collectd seems to create 120 point for the hourly data, as that is the minimum for 30sec intervals. But for longer periods it seems to be pretty much the required 100 plus 1 item. (but for daily data 103 for some reason).
Might be that the error has been there also earlier, but we have just noticed it now.
In any case, the error is likely reproduceable by changing the required time period.

So maybe we should simply increase the amount of data points? The original values are extremely conservative and date back over ten years, when this thing was supposed to run on wrt54gl style devices...

I will play with this a bit and try to figure out a bit more.
But your idea might be the right one.
Other option might be to force 1-2 more data points to be created by collectd.

Might be that the error has been there also earlier, but we have just noticed it now.

I am on 19.07 (footer of webpage says Powered by LuCI openwrt-19.07 branch (git-20.057.55219-13dd17f) / OpenWrt 19.07.2 r10947-65030d81f3), so likely the bug wasn't introduced with the move to JS.

Summary:
The bug/feature is likely a combination of data sets from different periods.
I got the wrong graphs on times when the newest weekly datapoint had been stored after the last daily datapoint.
On those times, the longer period dataset apparently provided a better match for the time period asked by LuCI
Mitigation proposal:
change the default RRARows 100 to 144, which seems to lead to nice even averaged data RRA periods:
(30 sec, 10 min, 70 min, 5h10min, 2d13h)

Teh bug was a bit harder to reproduce than I thought.
I managed to get faulty graphs again at midnight, but I failed at a few previous database change points (and I did not get faulty graphs at the next interval after the faulty one...)
This time the faulty period was for a few minutes just before the new data update (while the time was after the stored time from yesterday, but before the next update point today).
root@router1:~# date; rrdtool dump /tmp/rrd/router1/entropy/entropy.rrd  | head -n 162 | tail -n 3 ; echo "..."; rrd
tool dump /tmp/rrd/router1/entropy/entropy.rrd  | head -n 264 | tail -n 3
Mon May 18 00:04:05 EEST 2020
                <database>
                        <!-- 2020-05-17 00:04:00 EEST /<PHONE_NUMBER> --> <row><v> 2.0779928571e+03 </v></row>
                        <!-- 2020-05-17 00:18:00 EEST /<PHONE_NUMBER> --> <row><v> 1.8566261905e+03 </v></row>
...
                        <!-- 2020-05-17 23:38:00 EEST /<PHONE_NUMBER> --> <row><v> 1.4186928571e+03 </v></row>
                        <!-- 2020-05-17 23:52:00 EEST /<PHONE_NUMBER> --> <row><v> 1.3693309524e+03 </v></row>
                </database>
root@router1:~# echo wrong
wrong

root@router1:~# date; rrdtool dump /tmp/rrd/router1/entropy/entropy.rrd  | head -n 162 | tail -n 3 ; echo "..."; rrd
tool dump /tmp/rrd/router1/entropy/entropy.rrd  | head -n 264 | tail -n 3
Mon May 18 00:05:57 EEST 2020
                <database>
                        <!-- 2020-05-17 00:04:00 EEST /<PHONE_NUMBER> --> <row><v> 2.0779928571e+03 </v></row>
                        <!-- 2020-05-17 00:18:00 EEST /<PHONE_NUMBER> --> <row><v> 1.8566261905e+03 </v></row>
...
                        <!-- 2020-05-17 23:38:00 EEST /<PHONE_NUMBER> --> <row><v> 1.4186928571e+03 </v></row>
                        <!-- 2020-05-17 23:52:00 EEST /<PHONE_NUMBER> --> <row><v> 1.3693309524e+03 </v></row>
                </database>
root@router1:~# echo wrong
wrong
root@router1:~# date; rrdtool dump /tmp/rrd/router1/entropy/entropy.rrd  | head -n 162 | tail -n 3 ; echo "..."; rrd
tool dump /tmp/rrd/router1/entropy/entropy.rrd  | head -n 264 | tail -n 3
Mon May 18 00:06:20 EEST 2020
                <database>
                        <!-- 2020-05-17 00:18:00 EEST /<PHONE_NUMBER> --> <row><v> 1.8566261905e+03 </v></row>
                        <!-- 2020-05-17 00:32:00 EEST /<PHONE_NUMBER> --> <row><v> 1.6983690476e+03 </v></row>
...
                        <!-- 2020-05-17 23:52:00 EEST /<PHONE_NUMBER> --> <row><v> 1.3693309524e+03 </v></row>
                        <!-- 2020-05-18 00:06:00 EEST /<PHONE_NUMBER> --> <row><v> 1.3437261905e+03 </v></row>
                </database>
root@router1:~# echo ok
ok

Looking at the rrdtool sources, there is a determination logic for selecting the rrd period table to fetch data. The logic is in rrd_fetch.c roughly at lines 170-220. It aims for covering the whole data period and if that is not possible, the next best partial data set.  It uses the time step size several times in defining the "realistic period & step" vs. the original wishes.
The bug is likely a combination of data sets from different periods.
I think that I got the wrong graphs on times when the weekly datapoint had been stored after the last daily datapoint.
Last weekly datapoints:
                        <!-- 2020-05-17 22:19:30 EEST /<PHONE_NUMBER> --> <row><v> 1.3326341625e+03 </v></row>
                        <!-- 2020-05-18 00:00:00 EEST /<PHONE_NUMBER> --> <row><v> 1.4034275290e+03 </v></row>

I got the faulty graphs at ~22:27  and now at ~00:04 , both right after the latest update to the weekly data had been made, but before the next update of the shorter period.  I did not get faulty graphs at the daily data update points in between.
Possible solutions / mitigations:

Increasing the amount of datapoints (to decrease the time step interval) may be the easiest mitigation. We now define 100 items, which leads to 14 minutes step for daily data, and 100.5 minutes for the weekly data. Increasing the default item count to 120 or 150 would shorten the steps, shortening the periods when the mismatch happens. My suggestion is actually 144, (24x7)

LuCI side: shorten a bit the required time period (scaled to the required period). E.g. remove 1% of the earliest data, or move the required endpoint earlier by not fixed 60 seconds, but depending on the time scale 5 minutes, 50 minutes, or a few hours earlier.  ( Instead of asking exactly a week, ask for "now-week+1hour" - "now-1hour" )

Third possibility might be to patch collectd to originally create 1-2 extra data points to the RRD table, but that might unnecessarily complicated. However, that might be a solution instead of just a mitigation

My suggestion is to change the default from 100 to 144, which seems to lead to nice even averaged data RRA periods:
(30 sec, 10 min, 70 min, 5h10min, 2d13h)
filename = "/tmp/rrd/router1/entropy/entropy.rrd"
rrd_version = "0001"
step = 30
last_update =<PHONE_NUMBER>
ds[value].type = "GAUGE"
ds[value].minimal_heartbeat = 60
ds[value].min = 0.0000000000e+00
ds[value].max = 4.2949672950e+09
ds[value].last_ds = "UNKN"
ds[value].value = 2.7867000000e+04
ds[value].unknown_sec = 0
rra[0].cf = "AVERAGE"
rra[0].rows = 144
rra[0].pdp_per_row = 1
rra[0].xff = 1.0000000000e-01
rra[0].cdp_prep[0].value = NaN
rra[0].cdp_prep[0].unknown_datapoints = 0
rra[1].cf = "AVERAGE"
rra[1].rows = 144
rra[1].pdp_per_row = 20
rra[1].xff = 1.0000000000e-01
rra[1].cdp_prep[0].value = 2.5899000000e+03
rra[1].cdp_prep[0].unknown_datapoints = 0
rra[2].cf = "AVERAGE"
rra[2].rows = 144
rra[2].pdp_per_row = 140
rra[2].xff = 1.0000000000e-01
rra[2].cdp_prep[0].value = 6.3229000000e+03
rra[2].cdp_prep[0].unknown_datapoints = 97
rra[3].cf = "AVERAGE"
rra[3].rows = 144
rra[3].pdp_per_row = 620
rra[3].xff = 1.0000000000e-01
rra[3].cdp_prep[0].value = 6.3229000000e+03
rra[3].cdp_prep[0].unknown_datapoints = 377
rra[4].cf = "AVERAGE"
rra[4].rows = 144
rra[4].pdp_per_row = 7320
rra[4].xff = 1.0000000000e-01
rra[4].cdp_prep[0].value = 6.3229000000e+03
rra[4].cdp_prep[0].unknown_datapoints = 2297

I changed the default from 100 to 144 with 591b918e.
Hopefully that is enough as the first fix.
If there is no negative feedback, I will backport that to 19.07 at some point.
Tackling the problem fully would require shortening the requested time period a bit more, in a scaled way, but I think that it is an overkill for a cosmetic problem that manifests itself only rarely.

@jow-
Returning to the amount to data points in the LuCI statistics RRD databases.
I increased the default number from 100 to 144 in early 2020.
100 was really extremely conservative, like you said, and the current 144 is still really minimized.
That produces a quite roughly averaged graphs (especially with the daily and weekly periods).
Now I am considering to double the amount to 288, which would again produce nice database summary periods with our current duration definitions.
288 with our current durations (1h,1d,1w,1m,1y) would
generate RRD with 30s, 5min, 35min, 2h35min, 1d6h30min averaging periods
instead of the current 30s, 10min, 70min, 5h10min, 2d13h.
I have been testing it in one of my routers for a while, and especially the daily and weekly periods look much more detailed.
Any objections for that change?
It would double the size of the RRD database (in RAMdisk), but that should not cause any trouble for modern devices.

Fine with me, please go ahead!


Adjust notify service for icc

Adjust notify service for icc
Enable notify via new ICC integration.
Adjust previously used connection manager to use
new communiction manager
Attach osListenEditing to motion detail to get ICC notifications for
edits

@FinnStutzenstein please review later


[Windows] Fix borderless window flag toggle and restoring minimized borderless window.

Fixes #58257

Thanks!


Strip leading characters in git tag

Hi there, thanks for making this tool.
We create our git tags with a leading v i.e. v1.2.3.
I am creating automatic helm releases in CI and git-semver includes the leading v as our tags include this.
The leading v is actually not SemVer compliant. Would it be possible for you to add an option to strip any leading characters?

I added a -no-prefix-option in release 6.7.1.


VizPanel: Limit series feature

I really like https://github.com/grafana/scenes/pull/912 as a feature but there is something about the implementation that feels a bit messy / complex, feels like there should be an simpler way to accomplish this (I blame scenes arch here for making this tricky)
This is one approach where it's implemented more as rendering optimization feature inside VizPanel rendering instead of as a data state feature via SceneDataTransformer. A lot of the complexity in https://github.com/grafana/scenes/pull/912 is dealing with the wrapping of the already set data provider and for the title item to find and update the data transformer.
There is benefit to that data provider approach and that is that other behaviors attached to VizPanel that are using sceneGraph.getData to get the data would also get that limited set of series, but maybe that could also be seen as a limitation of the approach.
One downside with this approach is that it makes VizPanel itself a bit more complex where as https://github.com/grafana/scenes/pull/912 is "extending" it more via external title items & data providers

so...what about implementing value pagination and series pagination at the VizPanel level?
right now we have it implemented manually in Table and StateTimeline, but would be great to just have the vizpanel chunk into pages with some settings. :thinking:

i guess pagination gets tricky without sorting/filtering also being implemented in the same place :cry:

@leeoniya I agree, pagination would be a good next step, but for now I'd like to get something released that can replace the app-specific hack in Explore Logs to keep browser resources from being devoured by many high cardinality time series in breakdowns, and also get this in the hands of other app developers ASAP

@leeoniya

so...WDYT about implementing value pagination and series pagination at the VizPanel level?
right now we have it implemented manually in Table and StateTimeline, but would be great to just have the vizpanel chunk into pages with some settings.and render the pagination uniformly in the panel footer

Not sure, it's so visualization-specific, but maybe it could work

@gtk-grafana yeah, i did not mean in this PR :rofl:

Oh, one thing that did come to mind it would be nice to have a VizPanelBuilder option for seriesLimit, for those that are not using the VizPanel constructor

@gtk-grafana can you add it the builders?

@torkelo Absolutely. I'll follow up in another PR as I might not have time until Monday due to the US holiday, and I don't want to hold this up.


[rhash] update to 1.4.2

Library name: RHash
New version number: 1.4.2
https://github.com/rhash/RHash/releases/tag/v1.4.2

@PriitUring May I ask why you're requesting that many (24) port updates during the last few days?

@Thomas1664
I'm sorry if I sent too many requests today, just didn't see if there's any specific request limit, waited when most get merged or other specific time to pass or timeframes to honour to request updates or if I should had made a single list or tried to create a pull requests instead.
Maybe good to add some reminders, links or extra info to read before being allowed to request or post something. Wiki page seems empty here aswell.
I'm not in a rush to get something specific updated here.
Just noticed that some haven't been updated in VCPKG for a long time and some might take months or longer to have updated if at all if new issues arise.
If these can't be updated or if I should have given chance to others to request updates instead or waited for certain time to pass or if I should had written if worth updating anything at all, then I'm ok if these currently get closed.
Sorry if my wording is not good enough or just too long reply, thank you for reading.
I was planning to take a break and will take a break, will try my best not to bother anyone anywhere for a while.

First, note that my intention was not to make you stop opening issues/ request port updates.

Just noticed that some haven't been updated in VCPKG for a long time and some might take months or longer to have updated if at all if new issues arise.

That sounds like you're not using/ want to use those ports . In this case, maintainers (note that I'm not a maintainer) would prefer if you opened a PR instead. Again, there is nothing wrong with opening one or more issues to request updates. In most cases, updating a port is very easy, so feel free to open up a PR. To get started, please have a look at the maintainer guide. Taking a look at some PRs that closed one of your update requests might me helpful as well.

@Thomas1664
Well I couldn't find anything positive or proper valuable discussion when I searched online for  "vcpkg signing agreement".
Only reply to another users several concerns about some unfavorable or not suitable wording for European residents, legal aspects, non Microsoft employees, not really open source agreement etc in 2019 issue post was that there's no plans to update the agreement. Issue nr. in GitHub: 6899
So bit skeptical to share personal details and agree to something when officially there's no proper easy to understand explanation how safe or worry free should an average person be when wishing to try helping out and signing the agreement.
So even if I provide my personal address, email and signature to tryout updating some packages versions in vcpkg. I'll still at least need to know:

So should I worry about anything before I sign the agreement and then try updating various package versions?

If packages versions have been regularly updated by specific contributors or maintainers then is it still ok and doesn't really matter who creates a newer version update pull request?

You wrote you're not maintainer, yet it seems as if you do update packages versions in vcpkg and you shared with me a link to maintainers guide, so shouldn't there be extra guides added for new contributors or non maintainers and is there any noticeable difference between certain contributors or knowing the word difference doesn't really matter?

If I start contributing, then I can assign my self to fix my own or other users issues and add labels to issues?

So should I worry about anything before I sign the agreement and then try updating various package versions?

You have to provide your real name and your real email address. If you don't want to have your email included in commits, there is a GitHub setting to use an anonymous GitHub email instead. @BillyONeal can probably provide more information on this.

If packages versions have been regularly updated by specific contributors or maintainers then is it still ok and doesn't really matter who creates a newer version update pull request?

Nobody takes some kind of "ownership" on a port. Feel free to update any port you like.

You wrote you're not maintainer, yet it seems as if you do update packages versions in vcpkg and you shared with me a link to maintainers guide, so shouldn't there be extra guides added for new contributors or non maintainers and is there any noticeable difference between certain contributors or knowing the word difference doesn't really matter?

Yes, I'm just e very active community member. However, there are people like @FrankXie05 that are marked as contributors but are actually maintainers. Those people are usually assigned to issues/ PRs (this doesn't mean that you can't work on an issue).
Yes, better documentation for newcomers is definitely needed.

If I start contributing, then I can assign my self to fix my own or other users issues and add labels to issues?

No, the people who are assigned to an issue are maintainers. If you want to work on an issue, just start, no need to ask for permission. If you open issues that you want to fix by yourself, it's probably better to mention this in the first few issues. The way I do it is I don't open an issue at all before I start updating a port; You don't have to open an issue at first to update a port.

@Thomas1664
Ok, so I shouldn't worry about any legal stuff, licence ownership and my residency when signing the agreement before trying to update ports?
What about licence files of ports, should certain ports with specific license or a missing licence be better left for maintainers to update or as long as some kind of source code is available for download it's fine for everyone else to update in vcpkg?
Latest port versions Git Tree and source SHA512 hash is somewhere hidden or somehow automatically given or updated if I can't find these written in source website?

Ok, so I shouldn't worry about any legal stuff, licence ownership and my residency when signing the agreement before trying to update ports?

Again, if you have any concerns, either DM Billy on Discord or write an email to<EMAIL_ADDRESS>You can read the CLA here: https://cla.opensource.microsoft.com/microsoft/vcpkg. I'm not the right person to ask any legal questions.

What about licence files of ports, should certain ports with specific license or a missing licence be better left for maintainers to update or as long as some kind of source code is available for download it's fine for everyone else to update in vcpkg?

You don't have to care about that too much. Because every port must install a copyright file, there is always some kind of license included.

Latest port versions Git Tree and source SHA512 hash is somewhere hidden or somehow automatically given or updated if I can't find these written in source website?

If you're referring to port-version in manifest files, you increment it if you modified the port but didn't update the version. If you update a port, you remove port-version. This resets it to 0. git-tree in the version database is updated by running vcpkg x-add-version <port name>. If you already ran vcpkg x-add-version <port name> but modified the port again in the same PR, you append --overwrite-version. The easiest way to get SHA512 is to set it to 0 and look at the error message when you try to install that port (vcpkg install <port name>. There you will find something like expected hash.

@Thomas1664
Ok, thank you taking time for answering.
Will think through what to ask if I do send an email to try to get clarification of certain things that haven't been publicly answered to other users long ago and maybe only then see later how easy it is to do the port version updating etc.
I did notice that some ports don't have licence type line at all or are later written "Null", when some do their pull requests. And some ports have date numbers instead of any specific release version number.

Will think through what to ask if I do send an email to try to get clarification of certain things that haven't been publicly answered to other users long ago and maybe only then see later how easy it is to do the port version updating etc.

Don't worry, most of your questions on how to do port updates will likely be answered after you created some PRs.

I did notice that some ports don't have licence type line at all or are later written "Null", when some do their pull requests. And some ports have date numbers instead of any specific release version number.

We're adding license information when we update a port. Currently, we have to manually research the right license identifier. There are plans to automate this. Some ports have version-date because they don't provide any version tags or they didn't release a version for a long time, but the port was updated to a newer git commit. See manifest guide. (We don't use version-string the way this page suggests. It's only used for versions that don't follow the x.y.z scheme like deprecated or 1.1.1.n.)

@Thomas1664
Ok, thank you.
Will hide and mark my previous replies as resolved for now.
Will maybe later try out and see how things work exactly.
Will need to read and look around more why some ports are still updated with date number when release version numbers and source files for that release are also publicly available.

@Thomas1664 @PriitUring
Thank you very much Thomas for your reply. As the maintainer of vcpkg, we are very willing to see more and more users participating in the improvement. If you have any suggestions or questions, please feel free to submit an issue or pull request , We will guarantee to respond within 12 hours, of course, you can also consult contributors: such as Thomas, dg0yt , Neumann-A , Osyotr, etc. Thanks again for your many recent submissions and Thomas for the replies. :)


Typo in shebang

Thanks for correcting this! Fixed in 7e6010a3624c6e0c88398b806af784df275134b9 and 4934889b9ed6478d07d3def3fbb34e90f33b96a0 (chose to change it directly on dev to avoid merging conflicts).


Add query or API to see what queries are running in the cluster

We need visibility into what queries are running in the cluster on which nodes and for how long. This should be a new query type like:
list running queries

Which return a table of results like:
[
  {
    "name":"running queries",
    "columns": ["id", "start_time", "host", "query", "running_time", "user"],
    "points" : [...]
  }
]

Closing in favor of #5939.


Add cypress test: Content is automatically saved after 5 secs

Implemented in #211

Implemented in #211

It's better to link the issue to the PR (section "Development" on the right)


Add flags for Keyrock permission

Proposed changes
This PR adds flags for Keyrock permission.
ngsi applications permissions create
ngsi applications permissions update

   --regex, -R                      use resource with regex (default: false)
   --serviceHeader VALUE, -S VALUE  set authorization service header

Types of changes
What types of changes does your code introduce to the project: Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Update only documentation, not any source code.

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code.

[X] I have read the CONTRIBUTING doc
[ ] I have signed the CLA
[X] I have added tests that prove my fix is effective or that my feature works
[X] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Further comments
N/A

coverage: 100.0%. remained the same when pulling 7ccd191a9cc02c35630fd9176056c0f29fd9546a on fisuda:feature/permission_flags into b6c7be6b5624d50ad16cc3ebfe2561ed5c12e026 on lets-fiware:main.


Revised API Documentation

Requirements
As a Guardian OS Software User, I would like to review additional documentation around the Guardian API that is super-accurate.
Pre-requisite

Discovery Sessions
Revised IA Diagram
Revised FSD's

Definition of Done

Updated and Approved by Stakeholder Documentation

Acceptance Criteria:

Corrected Grammar int the Postman and Swagger API Documentation

Andrey has completed his part as of today but there is one step that needs to happen. He has completed Swagger Documentation, but now the Postman API needs to be updated, but Andrey doesn't know how to do this, so we need the Developers when they are back in on Monday, 1/10/2022.


rather an question than an issue add custimized shutdown2 script

mm i see that we don't need the effects folder to cp anymore, but could you guys please add shutdown2.py (its the same as the original shutdown, without the 3 times blinking), which makes it an awesome boot effect for me/us.
atm i still need to manually cp it to usr/share/hyperion/effects.
Here is the files
effects.zip

you could still load effects via effects folder.
Overall: It would be better to modify the old .py with a additional boolean that enables a real shutdown if wanted (and probably skips the effect)
The effect system is powerfull, just use it and create a PR if you are done :)
Basic informations: https://hyperion-project.org/wiki/a-Effect-development

with a additional boolean that enables a real shutdown if wanted

already in since I add the effect.
just copy the shutdown.json in effects folder and modify script filename with leading :
--> this:
{
"name"   : "System Shutdown",
"script" : ":shutdown.py",
"args"   :
{
"speed"            : 1.2,
"alarm-color"      : [255,0,0],
"post-color"       : [255,174,11],
"shutdown-enabled" : false
}
}

oh. never had a closer look, sorry :)

and when set both colors to black, then it looks like no effect

no what im sating is that i use the customized shutdown2.py as a boot script

Then make a pr with your effect. But please dont name it shutdown .... be more creative

What is an pr and yes I can rename it to startup but still need permission from the author cause it's his script with some lines removed. Do you know who made it? I tried to find out but couldn't find the author

I made it ... a pr is a pull request. This hyperion repository is mainly for developers.

I reviewed your modification and I disagree. It is the wrong way to do what you want. It duplicates most of the code - this is always wrong! Why you don't add an option to disable the alert color? Should be about 2 lines of python code and one line of json.
Behind code lines are always an idea. For this one the idea was to make it possible to shutdown the pi via hyperion android app. The alert effect is the countdown to abort, when accidentally selected on remote. I made shutdown function as an option and set to false, because user who don't understand what the shutdown effect is for, don't accidentally shutdown the system.
So from your code I think your intention was to make an effect that enlightens the leds from bottom top top. Yeah that's cool, why not - but then it should be more clean, creative and versatile. E.g.

remove the shutdown code
give a speaking name that describes what it does
add an option for fill direction - in degrees would be very nice to have a "fill effect" e.g. diagonal
what about a gradients
or looping
or ...

... thats what I mean, changing a parameter is more or less a personal thing - everybody can do this. We want cool things, not the x variant of what we already have ...

I would love to have that, but i have no such skills as you guys, im pretty prout of my setup atm but this toughes the sky for me, thats why i made an request for it, i know copy the code is a bad idea, but this was the only way i could get it to work. Would you please mind to make such an booteffect, i tought the name launch woult fit.
Anyway if you have no such time, which i respect, cause this hyperion project is awesome. I would like to have you personal approval to edit youre file for local use only. i wont share the customized script. My friend also say its really awesome without the blinking as an startup. (i also implented it in autoexec.py) each time i start a movie i will let it "initiate to start".

you can post it in our forum if you want


Sequential mail sending aborts after mail is rejected by mailserver.

Describe the bug
Sequential mail sending aborts after one mail is rejected by the mailserver.
To Reproduce
Steps to reproduce the behavior:
We use cloud-sdk to send emails sequentially.
Given we have got two addresses<EMAIL_ADDRESS><EMAIL_ADDRESS>When the mailserver rejects an email, the following emails won't be sent - sending seems to be aborted.

Send Emails to both recipients sequentially
First recipient is rejected
Can't send mail - all recipients were rejected: 550 5.1.1<EMAIL_ADDRESS>Recipient address rejected: Address not found.
Second mail is not delivered

*** Mail Client Options ***
const mailerOptions: MailClientOptions = {
  'requireTLS': true,
  'sdkOptions': {
    parallel: false
  },
  'tls': {
    'rejectUnauthorized': false
  }
}

Expected behavior
We expect all valid emails to be delivered.
Used Versions:

node version 20.15.1
npm version 10.7.0
SAP Cloud SDK version 3.22.2

Impact / Priority
Affected development phase: e.g. Production
Impact: Impaired
Timeline: already-live.

Hi @rFranzr,
Thanks for approaching.
Have you tried to send them in parallel?
Could you please share your code snippets?
What will happen, if you just send the second mail? Will it be delivered?

Hi @jjtang1985,
Sending emails in parallel leads to the same result.
Sending to just one valid recipient works.
`
const destinationOption: DestinationFetchOptions = {
'destinationName': 'smtp'
}
export const sendMails = async (mailConfigs: MailConfig[]): Promise => {
const validatedMails = mailConfigs.filter(validateMailRecipients)
if (validatedMails.length === 0) {
LOG.warn('No valid Mails to send.')
return
}
LOG.info('Sending %s mails.', [validatedMails.length])
const mailResponses = await sendMail(
destinationOption,
validatedMails,
mailerOptions
)
await handleMailSendingResponses(mailResponses)
}
`

Hi @rFranzr , I created a canary version if you want to try it out. We'll release a new version tomorrow.

The fix is now available in the latest v3.23.0.
I'll close the issue, please reopen if you need further support.

@deekshas8 Thanks for the great support and quick fix!


Fixes #1278 split services into 2 projects for scala.js

@kkasravi
here is an example about how to define custom output path of fastOpts output.
http://stackoverflow.com/questions/29371654/scala-js-compilation-destination

Looks like there is an error in Pack.scala about an ambiguous reference to dsl (imported from both sbt._ and Build._). I'll correct.

2 references that I've borrowed from are the following:
https://github.com/vmunier/play-with-scalajs-example/blob/master/build.sbt
https://github.com/ochrons/scalajs-spa-tutorial/blob/master/project/build.scala
Both do a fair amount with IO.copy, etc - the former doing it in the Play plugin to copy files from the shared directory. Both use crossProject.

@kkasravi
This takes us a lot of time. I will submit a fix PR as followup.
+1

@clockfly for the choice of either doing
artifactPath in fastOptJS :=
  (resourceManaged in jvm in Compile).value /
    ((moduleName in fastOptJS).value + "-fastopt.js"))

or
  lazy val js2jvmSettings = Seq(fastOptJS, fullOptJS, packageJSDependencies) map { packageJSKey =>
    crossTarget in(serviceJS, Compile, packageJSKey) := file(distDashboardDirectory)
  }

The later takes care of all steps fastOptJS, fullOptJS and packageJSDependencies.

Yes - if you see better alternative please make the required changes. Thanks for detailed review.


This project is dead

See https://github.com/wonderworks-software/PyFlow/issues/106.
@IlgarLunin Please archive this repo to mark it as read-only.

the tools menu is can't work well

I'm trying to keep it up to date with the no much time I have, but in general is working, if you find bugs please report them or make a pull request and I will try to keep it up to date!


[main] Upgrade to latest dependencies

Cron. -knative-prow-robot
/cc knative/networking-wg-leads
/assign knative/networking-wg-leads
Produced via:
./hack/update-deps.sh --upgrade --release v0.23
./hack/update-codegen.sh

Details:
bumping knative.dev/pkg b51994e...b80a192:
  > b80a192 Improve state reporting in kube checks (# 2082)

/lgtm
/approve


HTTP Timeout?

I'm getting a timeout trying to run an instance in EC2 from my home machine:
$ mix run
=INFO REPORT==== 20-Aug-2016::18:47:06 ===
    application: logger
    exited: stopped
    type: temporary
** (Mix) Could not start application matchmaker: exited in: MatchMaker.start(:normal, [])
    ** (EXIT) exited in: GenServer.call(ExAws.Config.AuthCache, {:refresh_config, %{access_key_id: [{:system, "SECRET"}, :instance_role], host: %{"ap-northeast-1" => "s3-ap-northeast-1.amazonaws.com", "ap-southeast-1" => "s3-ap-southeast-1.amazonaws.com", "ap-southeast-2" => "s3-ap-southeast-2.amazonaws.com", "eu-central-1" => "s3-eu-central-1.amazonaws.com", "eu-west-1" => "s3-eu-west-1.amazonaws.com", "sa-east-1" => "s3-sa-east-1.amazonaws.com", "us-east-1" => "s3.amazonaws.com", "us-west-1" => "s3-us-west-1.amazonaws.com", "us-west-2" => "s3-us-west-2.amazonaws.com"}, http_client: ExAws.Request.HTTPoison, json_codec: Poison, region: "us-east-1", scheme: "https://", secret_access_key: [{:system, "PASSWORD"}, :instance_role]}}, 5000)
        ** (EXIT) time out

Sometimes I'm getting this one:
$ mix run

=INFO REPORT==== 20-Aug-2016::18:48:07 ===
    application: logger
    exited: stopped
    type: temporary
** (Mix) Could not start application matchmaker: exited in: MatchMaker.start(:normal, [])
    ** (EXIT) exited in: GenServer.call(ExAws.Config.AuthCache, {:refresh_config, %{access_key_id: [{:system, "SECRET"}, :instance_role], host: %{"ap-northeast-1" => "s3-ap-northeast-1.amazonaws.com", "ap-southeast-1" => "s3-ap-southeast-1.amazonaws.com", "ap-southeast-2" => "s3-ap-southeast-2.amazonaws.com", "eu-central-1" => "s3-eu-central-1.amazonaws.com", "eu-west-1" => "s3-eu-west-1.amazonaws.com", "sa-east-1" => "s3-sa-east-1.amazonaws.com", "us-east-1" => "s3.amazonaws.com", "us-west-1" => "s3-us-west-1.amazonaws.com", "us-west-2" => "s3-us-west-2.amazonaws.com"}, http_client: ExAws.Request.HTTPoison, json_codec: Poison, region: "us-east-1", scheme: "https://", secret_access_key: [{:system, "PASSWORD"}, :instance_role]}}, 5000)
        ** (EXIT) an exception was raised:
            ** (CaseClauseError) no case clause matching: {:error, %{__exception__: true, id: nil, reason: :ehostunreach}}
                (ex_aws) lib/ex_aws/instance_meta.ex:5: ExAws.InstanceMeta.request/2
                (ex_aws) lib/ex_aws/instance_meta.ex:15: ExAws.InstanceMeta.security_credentials/1
                (ex_aws) lib/ex_aws/config/auth_cache.ex:37: ExAws.Config.AuthCache.refresh_config/2
                (ex_aws) lib/ex_aws/config/auth_cache.ex:27: ExAws.Config.AuthCache.handle_call/3
                (stdlib) gen_server.erl:615: :gen_server.try_handle_call/4
                (stdlib) gen_server.erl:647: :gen_server.handle_msg/5
                (stdlib) proc_lib.erl:247: :proc_lib.init_p_do_apply/3

Is there a way to check which HTTP request is being done internally?
Is there anyway to increase the HTTP timeout?

Is this happening on an EC2 instance? Or a local box?
Instance role auth is only available on EC2 instances with a configured role.

This was happening because I was accessing the API outside of EC2. It seems that http://<IP_ADDRESS>/latest/meta-data/ is only available within EC2.


provide BDD documentation (cucumber)

subj

done. newdocumentation should appear after releasing 7.0.0

done. newdocumentation should appear after releasing 7.0.0

@vdelendik where we should see this new documentation?

@vdelendik where we should see this new documentation?

Documentation is verified in pull request. Need to check on release version.

Documentation is verified in pull request. Need to check on release version.

Verified in git.
Cucumber report need to fix -> https://github.com/qaprosoft/carina/blob/master/docs/cucumber.md

Verified in git.
Cucumber report need to fix -> https://github.com/qaprosoft/carina/blob/master/docs/cucumber.md

merged. @okamara, please review.

merged. @okamara, please review.

Images are fixed.