Query type results in data averaging

Hello,
While using this plugin we have noticed that some of the data values that are being plotted are really averages of two (or more) data points that occur close together in time.
I believe this plug-in is using Get Parameter Samples which states

This divides the query interval in a number of intervals and returns aggregated statistics (max,min,avg) about each interval. This operation is useful when making high-level overviews (such as plots) of a parameter’s value over large time intervals without having to retrieve each and every individual parameter value.

Is there any way to make another query type that does not average the incoming data and thus does not display data values in Grafana that are not actually in the Yamcs mission database?
Thank you!

I think this is compatible with most other Grafana datasource plugins. Sampling prevents transferring large quantities of data from Yamcs to Grafana. For example, if you look at a 1 year plot of a 1 Hz parameter, it would be really wasteful (and slow) to query for all individual values.
I would agree that for newly incoming values we could do a better job, for example by using the 'Streaming' option of Grafana. Then the incoming values would be appended to the older (sampled) values. This subject is yet to be explored.

Thanks for the reply. We can somewhat work around this for now by increasing the Max Data Points filed in the query options, it is an imprecise solution, however. We just increase it to some arbitrarily large number and hope that averaging doesn't occur.
I understand why it happens, but the graphs showing values that aren't actually in the database has confused some people since we never expect those values to occur. I suppose we can use another tool for now, or look into modifying this plugin to use List Parameter History instead. https://docs.yamcs.org/yamcs-http-api/parameter-archive/list-parameter-history/

i'm working on an update where you will also have the option to have series for min/max in addition to avg.
I also plan to add list-parameter-history (and get-parameter-value), but list-parameter-history will only do 1 page.
I think sampling plots is the only correct way, and is what happens on yamcs-web too. If you have 10 parameters for 1 pixel, you average the value server-side and avoid the data transfer, your user screen pixel density wouldn't be able to accurately show anyway.

You get also the min/max which are actual values. I guess you can have an option to display those instead of the average.
Note that yamcs-web in fact displays all three, like you can see in the screenshot below (the dark blue is the average and the light blue is min/max).

Thanks for the reply. We can somewhat work around this for now by increasing the Max Data Points filed in the query options; it is an imprecise solution, however. We just increase it to some arbitrarily large number and hope that averaging doesn't occur.
I understand why it happens, but the graphs showing values that aren't actually in the database has confused some people since we never expect those values to occur. I suppose we can use another tool for now, or look into modifying this plugin to use List Parameter History instead. https://docs.yamcs.org/yamcs-http-api/parameter-archive/list-parameter-history/

Could it be that you are not trying to plot analog values? A sensor (measuring a temperature for example) will be limited in accuracy anyway so the very exact value doesn't mean too much (there is always some noise).
If you want to display other values like enumerations which have a limited set of values, that is not the right query, this one is more appropriate:
https://docs.yamcs.org/yamcs-http-api/parameter-archive/get-parameter-ranges/
Some Grafana support for that will be added also at some point.

That's interesting. Showing either the min or the max for a given time point would be fine for our use case. I agree that requesting all the data and then being unable to show it due to limitations in the display is the wrong approach. I just also think showing values that don't exist in the database can be confusing for some users, especially when they never expect to see values in that range.
We have a channel that only has values around 0-0.05 or 220-270. When it transitions between those two values, there are averages that are around 120 which have confused those reading the graphs since those values should not be occurring in normal operation.
This isn't an enumeration channel. It's a true sensor reading. I appreciate you asking.

The get parameter ranges is meant for enumerations; it should work for the analog values but provide the most common n values if that is of any use.
I think for your use case we should have a get samples which is somehow aware of the two intervals and never averages between them but only inside. Then the result will hopefully make sense.
We should remember this use case for future improvements... for now the option for showing the min/max currently being implemented by Fabian is the best we have.

Thanks so much for the reply. I agree what you're describing sounds like a good approach -- average the values when they differ only a little, but stop averaging should they differ by a certain threshold, perhaps.
I'll look forward to the min/max implementation as a possible solution, and depend on increasing Max Data Points for the affected views for now.

Should be addressed in v2.0.0:

Added min/max/count (in addition to avg) for sampling queries.
Added a 'Get Parameter Value History' query type, which does not process the data, but returns only the most recent 500 points.

Let us know if you encounter bugs in the implementation.

Wow! That was fast. Thank you for the update!


ARROW-5512: [C++] Rough API skeleton for C++ Datasets API / framework

This is almost exclusively header files, so I caution all against debating small details like function signatures, names, or what kind of smart pointer to use (if any) in various places. Instead, does the high level structure seem reasonable (or at least, not horrible) as a starting point to do more work?
Some of the naming of things is inspired by related concepts in Apache Iceberg (incubating) (https://github.com/apache/incubator-iceberg), which is a vertically integrated dataset metastore and reading and writing system specialized for that metastore.
Here is the basic idea:

A Dataset (for reading, aka "scanning") consists of a schema (what kind of data you expect to receive) and one or more data sources
A DataSource abstractly yields an iterator of DataFragment
A DataFragment represents a roughly individual storage unit, like a file

As many interfaces involving collections are based around Iterators so that we have the option of implementating "lazy" Datasets that continue to discover their structure after we are already scanning. It is a common problem in data warehousing that creating a detailed manifest of what needs to be scanned grows linearly in time with the complexity of the dataset (e.g. the number of fragments).
I abstracted away the file-related logic from the high level interface since I would like to support other kinds of data sources other than file-based ones:

Flight streams: each endpoint from a DoGet operation in Flight corresponds to a DataFragment
Database-like clients: e.g. the results of a SQL query form a Fragment

There's some object layering issues that aren't worked out yet, and I think the only way to work them out is to work on implementation and refactor until we get things feeling right:

It is the job of a FileFormat implementation to translate between
Filtering can occur both at the Partition/Fragment level (i.e. "skip these files altogether") as well as at the post-materialization stage. In Iceberg these "post-materialization" filters are called "Residuals". For example, if the user wants filter1 & filter2 to be applied and only filter1 can be handled by the low-level file deserialization, we will have to apply filter2 against the unfiltered in-memory RecordBatch, returning the filtered RecordBatch to the user

As another matter, this objective of this framework is to draw a distinction between the Schema of a file and the Schema of the Dataset. This isn't reflected fully in the headers yet. To give an example, suppose that we wish to obtain a Dataset with schema
a: int64 nullable
b: double nullable
c: string nullable

When reading files in the Dataset, we might encounter fields are won't want, or fields that are missing. We must conform the physical data to the Dataset's desired Schema. Much of the hard labor will be in the file format implementations, so match up what's in the file with what the Dataset wants. We also must deal with other kinds of schema normalization issues, like one Parquet file having a field as "non-nullable" when the desired schema is "nullable".
Inferring the Schema of a Dataset when you don't know it outright is a whole separate matter. If you go to Scan a dataset without knowing it, you must necessarily do some amount of inference up front or just prior to scanning. We will need to offer both "low effort" (look at some, but not files, and do not expend too much energy on it -- e.g. in the case of CSV files you may reach a conclusion without parsing an entire file) and "high effort / exhaustive" Schema inference.
As far as the actual Scan execution we are likely to immediately suffer some thread scheduling issues when trying to Scan files in parallel as internally IO and CPU work is coordinated. The file reader implementations have their own internal parallelism so that's something to contemplate as well.
In any case, I suggest we start small by creating minimalistic interfaces to CSV and Parquet files to start, implement simple dataset discovery as we have now in pyarrow/parquet.py, but a bit more general, and then we can investigate the various more advanced features as described in https://docs.google.com/document/d/1bVhzifD38qDypnSjtf8exvpP3sSB5x_Kw9m-n66FB2c/edit piece by piece.

@pitrou @bkietz I posit that the csv/ and json/ subprojects could be nested under src/arrow/dataset as this project proceeds. I'd like to move src/parquet/arrow there also but that might be trickier since we have more users of that project who would be expecting to find the symbols in libparquet.so

@wesm at a high level this seems reasonable to me, but I'm refraining on nit-picking individual APIs  per your request :)
One question I had on the iterator concept, is as you mentioned it might take a while to iterate through all fragments that need to be loaded.  Does it make sense to expose some level of parallelism in the APIs to allow clients to consume fragments more quickly, or do you imagine this will happen behind the scenes?

Some concepts are a bit vague to me. "Scan" == "read in full" or "walk directories for metadata"? Why do we have fragments and partitions and datasources and filesources?

So "Scan" is essentially the universally-used term to describe "reading a dataset" in database systems. If you look at any database system, you will see "scan", "scan node", "scanner", etc. all referring to the process of iterating through materialized chunks of a dataset. See for example the HdfsScanner base class that Impala uses for all of its data source interfaces
https://github.com/apache/impala/blob/master/be/src/exec/hdfs-scanner.h#L74

It is difficult for me to understand how the different concepts are supposed to be used at the end. Is the user supposed to build all the scaffolding by hand? Or is there some automation behind the hood?

The API is currently lacking in user-facing API endpoints, which are responsible to assembling the data structures and providing a ready-to-scan Dataset. I don't know yet what these APIs need to look like until we actually implement all of the parts of the complete workflow and stitch them together.
I'll respond to some of your other comments.

I'm going to add a few more code comments, get the CI passing, and then merge this if there is no objection. I will begin opening follow up JIRA issues and tag them with "dataset" label so that this project can move forward

Updated this. Will merge on passing build

Appveyor build on my fork, will keep an eye on https://ci.appveyor.com/project/wesm/arrow/builds/25238050

Updated this. Will merge on passing build

Sounds fine to me.


Environment vars in command-line

Hi!
I'm not sure if this issue is related to the action itself, but when I try to use an environment var on the CMAKE arguments, it's not recognized.
I've tested setting the -DCMAKE_TOOLCHAIN_FILE using the ANDROID_SDK_ROOT environment variable in two ways, but no one have worked:
Just to clarify, I've already ensured the given toolchain file is on the runner image.
https://github.com/rickomax/assimp/runs/479700678?check_suite_focus=true
https://github.com/rickomax/assimp/runs/479685226?check_suite_focus=true

Setting the path manually without the ${ANDROID_SDK_ROOT} environment var on the arguments works. Strange...

@rickomax using this in the yml file should work:
${{ env.ANDROID_SDK_ROOT }}
You could also use the env variable using a syntax that the OS understand, but would have a different syntax per platform)

Oh, gonna try. Ty!

https://github.com/rickomax/assimp/runs/481149007?check_suite_focus=true

From the log, it looks like the ANDROID_SDK_ROOT variable is not set in the environment, as it is empty, as in it has been evaluated to not being set.
 -DCMAKE_TOOLCHAIN_FILE=/ndk-bundle/build/cmake/android.toolchain.cmake
I can see the evalution done by enabling verbose output on steps/actions, that is:
https://github.com/actions/toolkit/blob/master/docs/action-debugging.md#step-debug-logs

I wonder how it's not set, if I can list it using the "run" action with bash....

run: echo $ANDROID_SDK_ROOT
run: echo $ANDROID_HOME

Yeah, it shows values for me

ok, can you enable step-debug-log as suggested and run the workflow again?

@rickomax i've investigate this further, and indeed the core.exec functions provided by actions/toolkit is not using a shell when launching commands. It looks like a solution would be to contribute back to actions/toolkit to add this functionality, or just do the logic in this action and use 'bash'/'cmd' according to platform and user preferences.

Running processes under the platform default shell helps indeed in being able to access to env var.  With v1 release you can use env var on the inputs of the action.


NoSuchMethodError: NoSuchMethodError: The getter 'name' was called on null. on Flutter 1.2 Stable release

Hey guys, so I upgraded Flutter to 1.2 and this is happening... please help me....
command
flutter run
exception
NoSuchMethodError: NoSuchMethodError: The getter 'name' was called on null.
Receiver: null
Tried calling: name
#0      Object.noSuchMethod (dart:core/runtime/libobject_patch.dart:50:5)
#1      AndroidDevice.startApp (package:flutter_tools/src/android/android_device.dart:388:41)
<asynchronous suspension>
#2      FlutterDevice.runHot (package:flutter_tools/src/resident_runner.dart:308:54)
<asynchronous suspension>
#3      HotRunner.run (package:flutter_tools/src/run_hot.dart:295:39)
<asynchronous suspension>
#4      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:405:37)
<asynchronous suspension>
#5      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:545:18)
#6      _asyncThenWrapperHelper.<anonymous closure> (dart:async/runtime/libasync_patch.dart:77:64)
#7      _rootRunUnary (dart:async/zone.dart:1132:38)
#8      _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#9      _FutureListener.handleValue (dart:async/future_impl.dart:126:18)
#10     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:639:45)
#11     Future._propagateToListeners (dart:async/future_impl.dart:668:32)
#12     Future._complete (dart:async/future_impl.dart:473:7)
#13     _SyncCompleter.complete (dart:async/future_impl.dart:51:12)
#14     _AsyncAwaitCompleter.complete (dart:async/runtime/libasync_patch.dart:28:18)
#15     _completeOnAsyncReturn (dart:async/runtime/libasync_patch.dart:294:13)
#16     RunCommand.usageValues (package:flutter_tools/src/commands/run.dart)
#17     _asyncThenWrapperHelper.<anonymous closure> (dart:async/runtime/libasync_patch.dart:77:64)
#18     _rootRunUnary (dart:async/zone.dart:1132:38)
#19     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#20     _FutureListener.handleValue (dart:async/future_impl.dart:126:18)
#21     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:639:45)
#22     Future._propagateToListeners (dart:async/future_impl.dart:668:32)
#23     Future._complete (dart:async/future_impl.dart:473:7)
#24     _SyncCompleter.complete (dart:async/future_impl.dart:51:12)
#25     _AsyncAwaitCompleter.complete (dart:async/runtime/libasync_patch.dart:28:18)
#26     _completeOnAsyncReturn (dart:async/runtime/libasync_patch.dart:294:13)
#27     AndroidDevice.targetPlatform (package:flutter_tools/src/android/android_device.dart)
#28     _asyncThenWrapperHelper.<anonymous closure> (dart:async/runtime/libasync_patch.dart:77:64)
#29     _rootRunUnary (dart:async/zone.dart:1132:38)
#30     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#31     _FutureListener.handleValue (dart:async/future_impl.dart:126:18)
#32     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:639:45)
#33     Future._propagateToListeners (dart:async/future_impl.dart:668:32)
#34     Future._complete (dart:async/future_impl.dart:473:7)
#35     _SyncCompleter.complete (dart:async/future_impl.dart:51:12)
#36     _AsyncAwaitCompleter.complete.<anonymous closure> (dart:async/runtime/libasync_patch.dart:33:20)
#37     _rootRun (dart:async/zone.dart:1124:13)
#38     _CustomZone.run (dart:async/zone.dart:1021:19)
#39     _CustomZone.bindCallback.<anonymous closure> (dart:async/zone.dart:947:23)
#40     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#41     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#42     _runPendingImmediateCallback (dart:isolate/runtime/libisolate_patch.dart:115:13)
#43     _RawReceivePortImpl._handleMessage (dart:isolate/runtime/libisolate_patch.dart:172:5)

flutter doctor
[✓] Flutter (Channel stable, v1.2.1, on Mac OS X 10.13.6 17G5019, locale en-DE)
    • Flutter version 1.2.1 at /Library/flutter
    • Framework revision 8661d8aecd (2 weeks ago), 2019-02-14 19:19:53 -0800
    • Engine revision 3757390fa4
    • Dart version 2.1.2 (build 2.1.2-dev.0.0 0a7dcf17eb)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/khaledah/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.1, Build version 10B61
    • ios-deploy 2.0.0
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 30.0.1
    • Dart plugin version 181.5656
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)

[✓] VS Code (version 1.31.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 2.23.1

[✓] Connected device (1 available)
    • POCOPHONE F1 • 6d56c9ac • android-arm64 • Android 9 (API 28)

• No issues found!

When i ran it using flutter run -v it gave me this error:
Error running com.peqas.peqas. Manifest versionCode not found
Unable to read manifest info from
/Users/...../peqas_app/build/app/outputs/apk/app.apk.

The stack trace in the first comment implies that package is null on this line:
    printTrace("Stopping app '${package.name}' on $name.");

That could be null if package = await AndroidApk.fromAndroidProject(project.android); returns null, which presumably is not what happened when it was run the second time (with -v), presumably it failed before returning null.

Or maybe it was null when the method was called?

@khalithartmann did you got any solution for this ?

The cause of the NPE is that we return early from await AndroidApk.fromAndroidProject(project.android) when we fail to parse the AndroidManifest. Only some of these branches include the appropriate error messages, which we should fix and then ensure that we exit the tool gracefully.
It sounds like there might be a problem in your AndroidManifest.xml, either it is malformed or missing in someway.

Hello @jonahwilliams
Sorry, but the #31400 solution has introduced an issue for my app.
In my AndroidManifest.xml I have "activity-alias" (with the ...MAIN action and the ...LAUNCHER category) instead of the "activity" xml entity. This alias points to the new .MainActivity.
The name of this alias is the old name for the launcher activity that existed several years ago. This alias is used so that people with old versions of the app don't loose the app icon after upgrading the app.
The code should also take into account 'activity-alias' tags (not just 'activity') to find out the launchActivity:
https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/application_package.dart#L214
https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/application_package.dart#L547
Otherwise I receive this error when trying to execute "flutter run" (after "flutter clean"):

package identifier or launch activity not found.
Please check .../android/app/src/main/AndroidManifest.xml for errors.
No application found for TargetPlatform.android_x86.
Is your project missing an android/app/src/main/AndroidManifest.xml?
Consider running "flutter create ." to create one.

Could you please take a look at this issue? Thank you!

I was getting the same error because my delete query was returning Future<int> instead of Future<void>.
Not working:
@Query("delete from Product")
Future<int> deleteAll();

working:
@Query("delete from Product")
Future<void> deleteAll();

I was getting the same error because my delete query was returning Future<int> instead of Future<void>.
Not working:
@Query("delete from Product")
Future<int> deleteAll();

working:
@Query("delete from Product")
Future<void> deleteAll();

Thank you so very much

Thanks a lot.

Thanks a lot.


Add "regular" background color selection

In syntax highlighting settings: Can't change the "regular" background color despite there being a grayed-out box for it (is fixed as white)

I think there's a reason this is the case, but don't remember the exact issue.  Will look into it to see if it's practical.


Update version matrix in readme

Codecov Report

Merging #542 (ebe5b42) into master (6afa402) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #542   +/-   ##
=======================================
  Coverage   37.69%   37.69%
=======================================
  Files          13       13
  Lines        2815     2815
=======================================
  Hits         1061     1061
  Misses       1673     1673
  Partials       81       81

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 6afa402...ebe5b42. Read the comment docs.


Minor typo fix

Just generated a project for myself using the rrplug_template. The design is very human. Very easy to use 🙂
Noticed a little typo so I figured I'd point it out. Thanks for making this library! I'll probably have questions for you on Discord about using it :P

lol


[SwipeableDrawer] Not scrolling content when anchor="bottom" on mobile

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

In mobile,  scrolling content within a SwipeableDrawer set with anchor='bottom' doesn't work at all. This only happens in mobile browsers.
Expected Behavior 🤔

Drawer content should be scrollable if the screen height is not big enough, no matter the anchor value.
Steps to Reproduce 🕹

Steps:

Go to https://andresbarreto.net using a mobile browser with a device that meets theme.breakpoints.down('sm') (default breakpoint values were not modified).
Tap on any image in the projects section (bottom of the page).
Put the device in landscape orientation (to force the content to be larger than the height of the screen)
Try to scroll content.

Following the same steps, the issue can also be reproduced with the Swipeable Temporary Drawer -> open bottom example on the demo page.
Context 🔦

Noticed that scrolling content is not an issue when the anchor is set to 'left' or 'right'.
Just in case, here's how I have set up the drawer in my project:
const isSmScreen = useMediaQuery(theme.breakpoints.down('sm'));
const iOS = process.browser && /iPad|iPhone|iPod/.test(navigator.userAgent);

// ...

  if (isSmScreen) {
    return (
      <SwipeableDrawer
        anchor="bottom"
        open={open}
        onClose={handleClose}
        onOpen={handleOpen}
        disableBackdropTransition={!iOS}
        disableDiscovery={iOS}
        aria-labelledby={selected.title}
      >
        {projectContent}
      </SwipeableDrawer>
    );
  }

Your Environment 🌎

Tech
Version

Material-UI
v4.3.1

React
v16.9.0

Browser
Chrome & Safari (Mobile)

@andresebr I can confirm the issue. The component doesn't check the scroll handlers in the drawer. This issue is most visible with the anchor top and bottom, but it's also present with the other variants. I had to solve this very same issue 3 years ago in react-swipeable-views. This is relatively simple to handle: https://github.com/oliviertassinari/react-swipeable-views/blob/1242299baceea36925cc98deb688d6d2e315f464/packages/react-swipeable-views/src/SwipeableViews.js#L473-L479, in case you want to submit a pull request :).

This issue still persists, even the demo on material-ui.com does not scroll if max-height is set in developer tools for demonstration.

@kamami see #22100

@oliviertassinari Hi! Seem's like an issue still persist on mobile when using SwipeableDrawer anchor="bottom" and anchor="top".  I have tested on Android Chrome and iOS Safari and i couldn't scroll a content.
Repo i have tested: https://codesandbox.io/s/material-demo-forked-8o4od?file=/demo.js
iOS Safari
https://user-images.githubusercontent.com/16666234/106383322-45322f00-63d6-11eb-9a04-bc02e933ccb9.MP4
Android Chrome
https://user-images.githubusercontent.com/16666234/106383439-02bd2200-63d7-11eb-8f2b-b76bc426d3cb.mp4

@oliviertassinari Hi! Seem's like an issue still persist on mobile when using SwipeableDrawer anchor="bottom" and anchor="top".  I have tested on Android Chrome and iOS Safari and i couldn't scroll a content.
Repo i have tested: https://codesandbox.io/s/material-demo-forked-8o4od?file=/demo.js
iOS Safari
https://user-images.githubusercontent.com/16666234/106383322-45322f00-63d6-11eb-9a04-bc02e933ccb9.MP4
Android Chrome
https://user-images.githubusercontent.com/16666234/106383439-02bd2200-63d7-11eb-8f2b-b76bc426d3cb.mp4

@VladSez It was fixed on v5: https://codesandbox.io/s/material-demo-forked-rqfjv?file=/package.json. Please always try the latest version.

@VladSez It was fixed on v5: https://codesandbox.io/s/material-demo-forked-rqfjv?file=/package.json. Please always try the latest version.

@VladSez It was fixed on v5: https://codesandbox.io/s/material-demo-forked-rqfjv?file=/package.json. Please always try the most recent version.

It would be great what solves this and why this was happening in the first place. thanks

I have a fix working:
https://github.com/buildrs/Share/blob/2ddbf31e00fcd7d409df6beb9afffb08929485a2/src/Components/MobileDrawer.jsx
I made it a persistent variant and set a couple of the properties conditionally on isOpen or not.. see L54 and L72.

@JeffinJ My workaround was to created a nested div with overflow: auto or overflow: scroll so that it wasn't affected by the overflow: visible on the parent Paper element.  Just make sure to the inner div height: 100%.
<SwipeableDrawer
    anchor='bottom'
    swipeAreaWidth={height}
    disableSwipeToOpen={false}
    ModalProps={{ keepMounted: true }}
    PaperProps={{
        sx: {
            // Since overflow is visible here and not 'auto' or 'scroll', the scrolling needs to happen in a nested div
            overflow: 'visible',
            height: `calc(90% - 73px)`
        }
    }}
>
    <Box
        sx={{
            bgcolor: 'white',
            position: 'absolute',
            top: '-73px',
            visibility: 'visible',
            right: 0,
            left: 0,
            height: '73px'
        }}
        alignItems='center'
    >
        Foobar
    </Box>
    <Box height='100%' overflow='auto'>
        <MyList />
    </Box>
</SwipeableDrawer>
);


Support for Multiple Network Devices in somltcp

Hello,
I'm new to somltcp and have a question about using multiple network devices (e.g., eth0 + loopback). I noticed that all the examples only use a single device, and from the source code, it appears that each Interface corresponds to only one network device.
Does this mean I need to manage multiple Interfaces myself if I want to use multiple network devices?
Thank you for your help.

I am interested in the answer to this as well.
I believe you may have to create an (Interface, Device) pair for each actual network interface


the num of FQ  question

Hi,
I think  the num of FQ is wrong ,  in the refmodel you set is 9 ,  so the  num of FQ is 2^(9+1) = 1024  ;
but in here  ,just loop 1023 time , and then said full ?    don't understand here ;
and why here  compare with the  FQH，  FQH here always is 0;

thank

A queue is empty if the head is equal to the tail. A queue is full if the tail is the head minus one. The head and tail wrap around when they reach the end of the circular buffer. When queue is of size 1024 then it is full when there are 1023 records i.e. when tail is one minus head.

The SMMU model implementation allows all N entries to be valid simultaneously rather than N-1 entries. However this requires tracking an additional wrap bit for the head and tail pointer each. The added complexity and state - though not high - both for SW and HW to use the one additional entry was considered not sufficiently motivated.


New feature request "Spreadsheet like delete cells" Cut out part but have rest of image "close in" to reduce image size by remvoing a part

New feature request
just like a spread sheet works, allow me to select an area and delete it via  a menu, which will have dymnamic outcomes depending on the area selected.
See https://youtu.be/8w6ZxJXMfNs
so the rest of the image will 'close in' occupy the deleted space from right side or bottom, depending on user selection
advantage have the important part of image be visible and less total area of image.

UI : a new menu item under edit, or two items (one for cut and move up and other for cut and move left, correct one or both will be enabled depending on current selection). If its a layer will be applicable to the layer/ single layer

Dont need support non rectangular selections.  Like cropping this wil help in reducing image dimensions and size.

This is an interesting idea, but you can already do this in one operation, if you select the region you want to move, and drag it to cover up the part you want gone.
If you want to line it up precisely you can use the arrow keys.

I don't think this is useful enough for a special feature.


Technical error message displayed when attempting to use biometrics for device without it being enabled

Describe the bug
"AuthScreen.errors.unenrolled" is displayed when trying to use biometrics without having it enabled on device or when having device that does not support it.
To Reproduce
Steps to reproduce the behavior:

Remove fingerprint enrollment on your device
Clear the app and go back to onboarding
Tab on Use biometric (an error should prompt)

Expected behavior
"To use Biometrics, please enroll your fingerprint in your device settings" should be displayed instead
Reproduced on
0.3.0 RC2 1.1.5

Verified on build linked in PR, works as expected for device with biometrics support. For devices without biometric support the button should be disabled, see https://github.com/idpass/inji/issues/181


Issue with using the StandardFargateSerice

There is an issue calling the StandardFargateService it defines a grace period which is an invalid parameter for a service that isn't connected to a load balancer
Resource handler returned message: "Invalid request provided: CreateService error: Health check grace period is only valid for services configured to use load balancers (Service: Ama
zonECS; Status Code: 400; Error Code: InvalidParameterException; Request ID: XXXed; Proxy: null)" (RequestToken: XXXXXXX8,
HandlerErrorCode: InvalidRequest)
https://github.com/truemark/cdk/blob/d55347e0b8da368a6a5b754b73f422c20ed92c43/aws-ecs/lib/standard-fargate-service.ts#L448C1-L449C62

This has been released in version 1.13.2.


Migrate to JVM SDK 1.0.0-RC1.

@lauraluiz can you please merge if the build is green and if it is red, fix it?

Thanks!


Wrong sort method in temp file queries

In the table listing Queries generating the most temporary files (#queries-generating-most-temporary-files), queries should be sorted by the number of query found (Count). But it seems that the count is not sorted on numerical reverse, but alphanumerical reverse, then we could get sort like that :
.1 7
.2 643
.3 6
.4 578
.5 4
Instead of :
.1 643
.2 578
.3 7
.4 6
.5 4

Commit d321274 might fix this issue.

Thank you, I can confirm that the bug is corrected.


(BUG) The  bymobile/  byemail/ bywalletAddress values aren't got

After changing mobile/email in the console should be displayed such values in GD_trust:
        goodDollarPublicKey: ".....",
        bymobile: ".......",
        byemail: ".....",
        bywalletAddress: "......",

Actual result:

Checked on DEV V0.24.1-2
LG V30+ // Android 8.0 // Google Chrome 83.0.4103.101
Desktop: Windows 10 // Google Chrome  83.0.4103.106

@sirpy
According to the goodserver's code:
const goodDollarPublicKey = GunDBPublic.user.is.pub
      const bymobile = await GunDBPublic.getIndexId('mobile')
      const byemail = await GunDBPublic.getIndexId('email')
      const bywalletAddress = await GunDBPublic.getIndexId('walletAddress')
      res.json({
        ok: 1,
        goodDollarPublicKey,
        bymobile,
        byemail,
        bywalletAddress
      })

the bymobile, byemail andbywalletAddress props also should be returned on /trust call
Earlier, during the #176 tests QA were getting the almost completed response:
bymobile: "kblzbvfz27QlGAxRdxP7~TkU0AvMNRUPpTpLtf2MlgmUINeAw8ITEfjzwyMgsWlo.46s2GSiRo98xhEoxsn_QFtRSeWJV3iUUCPPfdx9kTHg."
bywalletAddress: "kblzbw3ucg42yfKN3vsI~TkU0AvMNRUPpTpLtf2MlgmUINeAw8ITEfjzwyMgsWlo.46s2GSiRo98xhEoxsn_QFtRSeWJV3iUUCPPfdx9kTHg."
goodDollarPublicKey: "TkU0AvMNRUPpTpLtf2MlgmUINeAw8ITEfjzwyMgsWlo.46s2GSiRo98xhEoxsn_QFtRSeWJV3iUUCPPfdx9kTHg"
ok: 1

(just the byemail field was absent)
Now we have only goodDollarPublicKey

But the most interesting is that email / username / phone updates somehow, without having index id (GUN's references where its values should be stored) set

@serdiukov-o-nordwhale made some changes. should be ok now.

returns all four values (look at the screenshot)
Checked on the DEV V 0.24.1-3
Desktop: Windows 10 // Google Chrome  83.0.4103.106


Add py.typed

Hi and thank you for the amazing package! Just a small PR to add the py.typed file. The presence of py.typed lets type checkers like mypy know that the package contains type hints. Which means users like me do not get errors of the form
"Skipping analyzing "morfeus": module is installed, but missing library stubs or py.typed marker" when writing code against `morfeus`.

Thansk @lukasturcani for the heads-up! The PR is appreciated, I just added py.typed to another package that I am working on. Let me know if you have any other problems.

Release 0.7.2 should be on PyPI after the CI has processed it, while conda-forge might take a day or so.


Update ACS state in SDK

Docs Build status updates of commit 8a576a7:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Skype/WebSDK/docs/SkypeWebSDK.md
:warning:Warning

Details

Skype/AppSDK/SkypeAppSDK.md
:white_check_mark:Succeeded

Skype/WebSDK/docs/SkypeWebSDK.md

Line 31, Column 3: [Warning: file-not-found - See documentation] Invalid file link: './presenceevents'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 85d7db8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Skype/AppSDK/SkypeAppSDK.md
:white_check_mark:Succeeded

Skype/WebSDK/docs/SkypeWebSDK.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@lindalu-MSFT can you please help me merge this update of SfB SDK documentation with new ACS capability in GA

@tomaschladek Done! Thanks for tagging me, I only monitor this repo 1-2x a week.


log every single request

Softagram Impact Report for pull/1

:star: Dependency changes:
All changed elements and changed dependencies.

(click for full size)
:star: Impact in the codebase:
Changed files and their direct users. Heat map color of each file illustrates its number of external users.

(click for full size)
:mag: Softagram Risk Score:
No files with risk score higher than 10
:bulb: Softagram Risk Score explained
:page_facing_up: Full report

Permalink: Full report for pull/1

Softagram impact report is in Beta. Give us feedback at<EMAIL_ADDRESS>


just a test

Thanks for your contribution. We will consider your suggestions and update the docs as needed. Watch this space! /IBM


[multistage] [refactor] Introduce cancel on error API for MultiStageOperator and sending and receiving mailbox

Introduce cancel on error API for MultiStageOperator and mailbox.
This API will be used for MultiStageOperator to signal upstream operator there is an error occurring during execution.
cancel on error API is also introduced for sending and receiving mailbox so we can cancel the corresponding RPC.
waitForFinish API is introduced for sending mailbox because the mailbox send call is async . We need to wait for the RPC calls to be finished to clean up resources.

Codecov Report

Merging #10170 (dfcdd44) into master (4d7da0a) will decrease coverage by 21.24%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             master   #10170       +/-   ##
=============================================
- Coverage     34.84%   13.60%   -21.24%
+ Complexity      200      176       -24
=============================================
  Files          2006     1963       -43
  Lines        108718   106521     -2197
  Branches      16501    16247      -254
=============================================
- Hits          37880    14496    -23384
- Misses        67566    90884    +23318
+ Partials       3272     1141     -2131

Flag
Coverage Δ

integration1
?

integration2
?

unittests2
13.60% <0.00%> (-0.04%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

 Learn more

@xiangfu0


Stanford CoreNLP using MavenReference (.NET 6, IKVM 8.7.3, IKVM.Maven.Sdk 1.6.2)

Hi, I just tried to migrate CoreNLP tests to MavenReference and all tests failed in runtime
     at java.lang.ThreadLocal.nextHashCode()
     at java.lang.ThreadLocal..ctor()
     at ikvm.internal.IntrinsicThreadLocal..ctor()
     at java.nio.charset.Charset.__<tls>_0..ctor()
     at java.nio.charset.Charset..cctor()

here is runnable PR - https://github.com/sergey-tihon/Stanford.NLP.NET/pull/130 and errors from the CI https://github.com/sergey-tihon/Stanford.NLP.NET/actions/runs/7160234064/job/19494381165?pr=130
Full stack trace from one tests
  Error Message:
   System.TypeInitializationException : The type initializer for 'edu.stanford.nlp.pipeline.Annotation' threw an exception.
---- System.TypeInitializationException : The type initializer for 'edu.stanford.nlp.util.ArrayCoreMap' threw an exception.
-------- System.TypeInitializationException : The type initializer for 'java.lang.ThreadLocal' threw an exception.
------------ System.TypeInitializationException : The type initializer for 'java.util.concurrent.atomic.AtomicInteger' threw an exception.
---------------- System.TypeInitializationException : The type initializer for 'java.lang.Object' threw an exception.
-------------------- System.TypeInitializationException : The type initializer for 'java.nio.charset.Charset' threw an exception.
------------------------ System.NullReferenceException : Object reference not set to an instance of an object.
  Stack Trace:
     at edu.stanford.nlp.pipeline.Annotation..ctor(String text)
   at Stanford.NLP.CoreNLP.Tests.Samples.CorefTests.CorefTest() in /Users/sergey_tihon/git/Stanford.NLP.NET/tests/Stanford.NLP.CoreNLP.Tests/Samples/CorefTests.cs:line 29
----- Inner Stack Trace -----
   at edu.stanford.nlp.util.ArrayCoreMap.__<clinit>()
   at edu.stanford.nlp.pipeline.Annotation..cctor()
----- Inner Stack Trace -----
   at java.lang.ThreadLocal.withInitial(Supplier supplier)
   at edu.stanford.nlp.util.ArrayCoreMap..cctor()
----- Inner Stack Trace -----
   at java.util.concurrent.atomic.AtomicInteger..ctor()
   at java.lang.ThreadLocal..cctor()
----- Inner Stack Trace -----
   at java.lang.Object..ctor()
   at ikvm.internal.CallerID..ctor()
   at ikvm.internal.CallerID.2..ctor(RuntimeTypeHandle val$typeHandle)
   at ikvm.internal.CallerID.create(RuntimeTypeHandle typeHandle)
   at java.util.concurrent.atomic.AtomicInteger.__<GetCallerID>()
   at java.util.concurrent.atomic.AtomicInteger..cctor()
----- Inner Stack Trace -----
   at java.nio.charset.Charset.defaultCharset()
   at sun.nio.cs.StreamEncoder.forOutputStreamWriter(OutputStream out, Object lock, String charsetName)
   at java.io.OutputStreamWriter..ctor(OutputStream out)
   at java.io.PrintStream..ctor(Boolean autoFlush, OutputStream out)
   at java.io.PrintStream..ctor(OutputStream out, Boolean autoFlush)
   at java.lang.System.newPrintStream(FileOutputStream fos, String enc)
   at java.lang.System.initializeSystemClass()
   at __<MethodAccessor>__System__initializeSystemClass()
   at IKVM.Runtime.Accessors.Java.Lang.SystemAccessor.InvokeInitializeSystemClass()
   at IKVM.Runtime.JVM.EnsureInitialized()
   at java.lang.Object..cctor()
----- Inner Stack Trace -----
   at java.lang.ThreadLocal.nextHashCode()
   at java.lang.ThreadLocal..ctor()
   at ikvm.internal.IntrinsicThreadLocal..ctor()
   at java.nio.charset.Charset.__<tls>_0..ctor()
   at java.nio.charset.Charset..cctor()

Any idea why it happens?

Can you stick new java.lang.Object() as the first thing in the first method you call?

You are right, this works. https://github.com/sergey-tihon/Stanford.NLP.NET/pull/130/commits/ec1eb19e0ca98bdb4bb652edee6ca2197e723201
What is it?

https://github.com/ikvmnet/ikvm/issues/423
Haven't got around to figuring it out.

Interesting that I did not face this issue before when building jar files by myself...
May it be related to newer versions of IKVM or the way MavenReference works?

Closed as duplicate https://github.com/ikvmnet/ikvm/issues/423


Rolling testing repo builds failing due to MoveIt! dependency

MoveIt! seems to be having problems in the buildfarm currently, causing packages getting removed from the testing repo. This makes our pipelines building against the testing repo fail (binary and semi-binary).
We should first check, wether we can build against the latest MoveIt! release and then include this into the repos files until things have gone back to normal. Otherwise we are blind on issues coming from rolling testing at the moment.

Edit: MoveIt! has done a new release: https://github.com/ros/rosdistro/pull/36936. Maybe that fixes things.

This did indeed fix it


Performance regression on timestemp range join.

Describe the bug
For query in #8393, datafusion-cli v34 take 10s to finish the query. But it take 40s for datafusion-cli v36 to finish.
To Reproduce
Mostly same with #8393.
produce data.
CREATE
OR REPLACE TABLE pricing AS
SELECT
    t,
    RANDOM() as v
FROM
    range(
        '2022-01-01' :: TIMESTAMP,
        '2023-01-01' :: TIMESTAMP,
        INTERVAL 1 DAY
    ) ts(t);

COPY pricing to 'pricing.parquet' (format 'parquet');

CREATE
OR REPLACE TABLE timestamps AS
SELECT
    t
FROM
    range(
        '2022-01-01' :: TIMESTAMP,
        '2023-01-01' :: TIMESTAMP,
        INTERVAL 10 SECOND
    ) ts(t);

COPY timestamps to 'timestamps.parquet' (format 'parquet');

run query.
EXPLAIN ANALYZE WITH pricing_state AS (
    SELECT
        t as valid_from,
        COALESCE(
            LEAD(t, 1) OVER (
                ORDER BY
                    t
            ),
            '2077-12-31'
        ) as valid_to,
        v
    FROM
        'pricing.parquet'
)

SELECT
    t.t,
    p.v
FROM
	'timestamps.parquet' t
    LEFT JOIN pricing_state p ON t.t BETWEEN p.valid_from
    AND p.valid_to;

Expected behavior
No response
Additional context
And flamegraph is quite different.
v36

v34

see https://gist.github.com/my-vegetable-has-exploded/ba16c59c96c81fa20f52b56f254ea8be for more information.

Did the join order change?

Note that the first statement in this ticket does not run out of the box in main:
CREATE
OR REPLACE TABLE pricing AS
SELECT
    t,
    RANDOM() as v
FROM
    range(
        '2022-01-01' :: TIMESTAMP,
        '2023-01-01' :: TIMESTAMP,
        INTERVAL 1 DAY
    ) ts(t);
Error during planning: table function 'range' not found

I'll file a new issue for this shortly.

Sorry for late response. I found that I mistakenly used the debug version of the cli. In fact, the new version will work better.
Sorry for it.😭


Portuguese translation

Hi, I would like to ask if it's possible to add translation support to the character sheet and item sheet. Thanks!

Sorry, I found translation support here


Discarding unwanted ancillas

It'd be useful if unwanted ancillas can be dropped from a wavefunction object once they're no longer needed; lots of algorithms need big ancillary registers and it could be hard/cumbersome to read the output in these cases. E.g:
a|0000001>+b|0000010> -> a|01>+b|10>.

It'd be useful even if you had to manually declare which qubits are ancillary and only allow dropping of the totally uncomputed (i.e. all 0) registers, I think.

Hi @sam-pally, we will look into such a feature.

Could we implement this in in PyQuil with the wavefunction equivalent of the range operator? Something like:
twobit_wavefunction = wavefunction[0..2]

@stevenheidel Has this been implemented?


Do not use heading-tags in search results

The six heading elements, H1 through H6, must be used to denote section headings.

Title of the first result

Remove the
-tags and style the -tags accordingly.

This issue can be implemented at the same time as #477, #515, #488

Heading tags are still used as titles of the search results:

(chrome, https://admin-ch.github.io/styleguide/en/search.html#07-search-02-search-results)


Check static analysis cache

Do not submit - investigating static analysis CI step

Pull Request Functional Test Report for #2305 /<PHONE_NUMBER>c861ea8243ddc744e73dbdccb6ae23
No tests identified for validation.
Help

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1536

Relevant Lines:
3154

💛  - Coveralls


New MP environments for Data Platform

Environment details
Application Name
data-platform

Description of application

GitHub team slug
data-platform-labs

Environments

We currently have a sandbox, but we would like to extend this to Dev, Preprod, and Prod. Our sandbox account is called development currently - Open to suggestions as to how to align this with the 4 environments we need of sandbox, dev, preprod, and prod.

Environment
Access level

[ ] Development
[ ] view-only[ ] developer[ ] sandbox

[ ] Test
[ ] view-only[ ] developer

[x] Preproduction
[ ] view-only[x] developer

[x] Production
[ ] view-only[x] developer

Tags

tag
value

application
data-platform

business-unit
Platforms

infrastructure-support
<EMAIL_ADDRESS>

owner
<EMAIL_ADDRESS>

Networking options
Subnet sets

[ ] General - this application will use the same subnet as other applications in your business unit
[ ] Isolated - this application has highly sensitive data which must have its own isolated subnet with no network connectivity

How do users connect to the application?

[x] Over the public internet
[ ] With a purple cabled device (please give details)
[x] With a MoJ Official device

Connectivity to other applications or external parties

Additional features

[ ] Additional VPC Endpoints
[ ] Extended DNS Zones
[ ] Other - please specify

Other information

Definition of done

[ ] account created
[ ] customer informed

https://github.com/ministryofjustice/modernisation-platform/pull/4785/files << This PR shows an example of what I think @murdo-moj is after, only for a different application.

Request states they only want view-only so I will email to get confirmation. Not sure view only is really what they want/need

Clarified the requirements. Read only and developer are required.

Initial PR - #4871

We had a number of issues so there were a few other PRs #4873 #4876 #4877

Looks complete now


Fix router tests

What does this PR do?
Fixes router tests that was broken after last changes. Align them into Gaudi-specific code. With this change all tests from cargo test passed.

@regisss please review


Polygon2D polygon data member can only be updated when you assign a new polygon

Godot version:
3.2.2 stable
OS/device including version:
linux
Issue description:
A Polygon2D has a polygon property representing it. If you try to use the .set() method, the .remove() method or the .append() method on a Polygon2Ds polygon, absolutely nothing changes.
If you change the values in the debug window, then the polygon is updated ok.
However, if you create a new PoolVector2Array, then assign it to the polygon it changes fine.
This may have something to do with PoolVector2Array being passed by value, but if it were, then you would either think why have the set and other methods, why is it not documented, and why are there no helper methods of Polygon2D to make changes more obvious...
Please see below for it not working and the code to make it work. Note, this class is missing a shed load of documentation and a lot of the properties (I have no idea about) are flagged red.
func _ready_shard():
	width=shard_texture.get_width()
	height=shard_texture.get_height()

	#NOTE: image_shard refers to the Polygon2D node in the scene

	#this updates the image fine
	image_shard.texture=shard_texture

	#this does not set the value, it remains as it was :(
	image_shard.polygon.set(0,Vector2(0,0))
	image_shard.polygon.set(1,Vector2(width,0))
	image_shard.polygon.set(2,Vector2(width,height))
	image_shard.polygon.set(3,Vector2(0,height))

	#this does not remove anything :(
	image_shard.polygon.remove(0)
	image_shard.polygon.remove(1)
	image_shard.polygon.remove(2)
	image_shard.polygon.remove(3)

	#this does not add anything :(
	image_shard.polygon.append(Vector2(0,0))
	image_shard.polygon.append(Vector2(width,0))
	image_shard.polygon.append(Vector2(width,height))
	image_shard.polygon.append(Vector2(0,height))

	#this works :)
	var a=[Vector2(0,0),Vector2(width,0),
	           Vector2(width,height),Vector2(0,height)]
	var p=PoolVector2Array(a)
	image_shard.polygon=p

Steps to reproduce:
Minimal reproduction project:

Duplicate of #15265.

Why close this? the case you're referring to is Closed also and refers to the append method inside dictionaries. Or does this mean you're happy with this inability to modify a Polygon2D polygon data usefully and without any documentation to indicate how it's done?

The issue I linked is not closed.
Polygon2D is not relevant here, the issue is that polygon is a Pool*Array and Pool*Array types can't be mutated when they're accessed as members. You need to assign a new Pool*Array instance to the polygon property to mutate it, as you found yourself in the OP.

Sorry, I just sometimes can't figure out the nesting and threading of the github. Reading all the way down this duplicate says 'Closed' :)
I know how to do this now, but anyone else it'll be the same problem. In the meantime can it be suggested somebody update the documentation, at least for Pool array to say if this is part of another node it won't work as expected)? I'd like to but I don't really know the Godot workflow.

Sorry, I just sometimes can't figure out the nesting and threading of the github. Reading all the way down this duplicate says 'Closed' :)

What you might be seeing is other duplicate issues which have all been closed as duplicates of #15265.
#15265 itself is open:

It's a known limitation, and yes, until it's properly fixed in 4.0, it would be worth documenting in the description of all Pool*Array types.


Remove doctor-kafka.iml and add .gitignore file

Looks like this was already done in 3c6ff0f9d16d2cee2fb77c7fd8b947f6dec219eb.

Thanks to push --force!
https://github.com/hisener/doctorkafka/commits/master
https://github.com/pinterest/doctorkafka/commits/master
Hashes are different.

Looks like we didn't have branch protection enabled for this new repository. Sorry about that! It's on now.


Enforce in DBMS that local emails are unique. Fixes #719

Modify the schema so that the database enforces uniqueness
of email addresses when the provider is 'local'.
We depend on this, because we use the email address as the
identifier during login.
We enforce this at the Rails level, but that is subject to a race
condition because different Rails processes or threads might not
see this.  Also, enforcing important data structure requirements
at the DBMS level means that even if the code has a bug, it can't
violate this condition.
Signed-off-by: David A. Wheeler<EMAIL_ADDRESS>

Codecov Report

Merging #825 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #825   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          45     45
  Lines        1427   1427
=====================================
  Hits         1427   1427

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 2cc8eb4...dd5fb9a. Read the comment docs.


Inference on CPU

Can FocalNet inference on CPU?

yes, it can.

Thanks for the reply!
How about FocalNet-DINO models? Can they do inference on CPU? As far as I know, DINO only can do inference on GPU.


Investigate integration of beacon scanning

Eddystone
iBeacon

These both have some standards.  You can simulate these as well.
iBeacon should show up as:

(iBeacon) name in parens
AdvertisingType: Legacy
Company: Apple, Inc 0x004C
Type: Beacon 0x02

for starters.
A great cheatsheet on beacons: https://twitter.com/josryke/status/763006284052463617/photo/1

Some points about scanning for beacons
https://github.com/PhilipsHue/flutter_reactive_ble/issues/664

Seems there is a library out there for good ios/android beacon scanning.
https://github.com/jusahyv/simple_beacons_flutter
For any thoughts about ranging:
https://stackoverflow.com/a/22787597/796514


Get all avaiable values to object by one method/function?

Now when we use system information to get all data (CPU, RAM, Disk, GPU, etc...) we need to call a lot of methods/functions, so I would like to have functions getAllHW() and getAllUsage() to get all data about HardWare and Usage() which would return object with these data. So we can easilly use app.get('/hardware', si.getAllHW());
and in client-side let data = fetch('/hardware');
so I can easilly use interpolation/binding in view, to parse informations, like {{data.cpu.usage}} or {{data.ram.avaiable}}

@Mlocik97-issues I plan to build a function where you can specify (json object) what you would like to get back. This would be more flexible and will allow to get exactly those values back, that you need with one single function call. Hope this is ok for you.

yes, it would be really great.

I second this, awaiting 5 methods takes about 5 secs which is unfortunate.

@Mlocik97-issues I just released a new version 4.25.0 which includes a possibility to provide a value object to a get() function which results in an object with just the wanted properties. See example in the documentation https://systeminformation.io/general.html

thanks so much


MM T134 visual verification of tooltips

Summary
This PR validates that several tool-tips appear as expected in the main view when the associated element is hovered over. The tool-tips are for the following elements:

Member icon
Plug-in icon (the demo plugin is used)
Pinned posts - Recent Mentions
Flagged posts as well as
Add to Favorites
Remove from Favorites
Unmute (visible when channel is muted )
'Download' on download file icon
Long channel name (shown truncated on the LHS)
Hover effect wraps around Date and New Messages lines (no tooltip just proper post shading needs to be verified on hover)

Note that this last one does not have a tool-tip so I am not sure it should be included in this PR.
The PR creates a new instance, along with a test user and a test channel with a long name, then proceeds to validate the hover tool-tips. The demo plugin is also installed and enabled for testing of the plug-in tool-tip.
Ticket Links
vercel
TM4J

/update-branch

@srkgupta @saturninoabril I am not sure how to assert Hover effect wraps around Date and New Messages lines (no tooltip just proper post shading needs to be verified on hover" - Saturn - perhaps you could suggest a solution?
I am not sure this check should be in this test since it's not really a tool-tip.

Hover effect check removed (discussion with Saturn)
plugin work moved to api flow
after hook added for cleanup
test actions now performed by regular user

Hi @MikeworX
There are way more number of files changed in this PR. Looks like something is messed up while merging the PR. You may have to close this PR and create a fresh PR only with your changes on it.

starting PR over


SCP-2158: use the new CBOR tags that we have proposed

We've added a number of special tags for constructors to the CBOR
standard, which saves us some space and makes the encoding
non-ambiguous.
They are not quite accepted yet, but they nearly are, and it'll be a
lot easier to use them from the beginning than to change to using them
later, so this PR does it.

Pre-submit checklist:

Branch

[ ] Commit sequence broadly makes sense
[ ] Key commits have useful messages
[ ] Relevant tickets are mentioned in commit messages
[ ] Formatting, materialized Nix files, PNG optimization, etc. are updated

PR

[ ] Self-reviewed the diff
[ ] Useful pull request description
[ ] Reviewer requested

Pre-merge checklist:

[ ] Someone approved it
[ ] Commits have useful messages
[ ] Review clarifications made it into the code
[ ] History is moderately tidy; or going to squash-merge

I don't think anyone particularly cares about this, so I'll just merge it.

I'm sure I commented on this and Michael replied, but those seem to have disappeared completely.


No docs for features

@jgallagher
There doesn't seem to be docs for extra features of rusqlite v0.6. e.g. http://jgallagher.github.io/rusqlite/rusqlite/index.html?search=backup
I had to rely on source comments. Is this intended?

Nope, definitely not. Just an oversight in having to copy-paste features into the script I use for publishing them. It's fixed; hopefully in the future rust-lang/cargo#1173 is available and we can drop --all-features into the script instead.

Awesome. Thanks! :+1:


Please create new release (or provide helm dev installation instructions)

Describe the bug
I was trying to get Hajimari running via Helm to use the CRD support. However, turns out the CRD wasn't getting installed and after manually installing it, I wouldn't pick up any Application resources.
Turns out that v0.3.1 doesn't yet ship this functionality.
I'd really like to use Hajimari but do depend on the new CRD support.
Expected behavior
Is it possible to get a new release cut?
Or could you provide instructions how to run a development version?
Thank you!

Indeed, I was also looking for a new release to use the added CRD added. There have been 50 commits since then. Most of them are version updates.

it just works providing you install the lastest helm and use a latest image:
    image:
      tag: main-f77fe68

While that will probably work, I'd feel much better about it if it was actually declared as a stable version.


Comment Tags missing

see https://github.com/dotnet/docs/issues/18659

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

ID: 3e862820-a044-b4e5-63de-9c84778a3b2c
Version Independent ID: d0b7bf75-d2c3-5960-a4ca-0e560839045b
Content: Documentation comments - C# language specification
Content Source: spec/documentation-comments.md
Product: dotnet-csharp
Technology: csharp-spec
GitHub Login: @dotnet-bot
Microsoft Alias: wiwagn

I'm closing this based on these thoughts: https://github.com/dotnet/docs/issues/18659#issuecomment-635401173
In the language spec, we should continue to scope the discussion to the language rules only.


Capacity Constraint Skip Values...

Hi All,
I'm using the constraint solver in C# to solve an interesting Routing problem.
I have a vehicle with an arbitrary capacity of 10, but at any point in time this vehicle's capacity can never be between 4 & 6. Is there a way for me to ensure the Cumul Var of the Capacity Dimension never is between 4 & 6 during the setup of vehicle constraints?
I've tried the following with no luck, even adding lines for Model.TransitVar(Model.Start(i)... in all cases (would love a quick brief on some of these).
Not Between:
Model.solver().Add(Model.solver().MakeNotBetweenCt(Model.CumulVar(Model.Start(i), "CapacityDimension"), 4, 6));
Model.solver().Add(Model.solver().MakeNotBetweenCt(Model.CumulVar(Model.End(i), "CapacityDimension"), 4, 6));

Non Equality:
Model.solver().Add(Model.solver().MakeNonEquality(Model.CumulVar(Model.Start(i), "CapacityDimension"), 4));
Model.solver().Add(Model.solver().MakeNonEquality(Model.CumulVar(Model.End(i), "CapacityDimension"), 4));
Model.solver().Add(Model.solver().MakeNonEquality(Model.CumulVar(Model.Start(i), "CapacityDimension"), 5));
Model.solver().Add(Model.solver().MakeNonEquality(Model.CumulVar(Model.End(i), "CapacityDimension"), 5));
Model.solver().Add(Model.solver().MakeNonEquality(Model.CumulVar(Model.Start(i), "CapacityDimension"), 6));
Model.solver().Add(Model.solver().MakeNonEquality(Model.CumulVar(Model.End(i), "CapacityDimension"), 6));

Is Different:
Model.CumulVar(Model.Start(i), "CapacityDimension").IsDifferent(4);
Model.CumulVar(Model.Start(i), "CapacityDimension").IsDifferent(5);
Model.CumulVar(Model.Start(i), "CapacityDimension").IsDifferent(6);
Model.CumulVar(Model.End(i), "CapacityDimension").IsDifferent(4);
Model.CumulVar(Model.End(i), "CapacityDimension").IsDifferent(5);
Model.CumulVar(Model.End(i), "CapacityDimension").IsDifferent(6);

Member: (Where capacities is 1 - 10 excluding 4-6)
Model.CumulVar(Model.Start(i), "CapacityDimension").Member(capacities);
Model.CumulVar(Model.End(i), "CapacityDimension").Member(capacities);

SetValues: (Where capacities is 1 - 10 excluding 4-6)
Model.CumulVar(Model.Start(i), "CapacityDimension").SetValues(capacities);
Model.CumulVar(Model.End(i), "CapacityDimension").SetValues(capacities);

Let me know if there is any more information I can provide that'll help.

Hi @ConnerWestover , did you solve your problem? if you do, could you share me your solution, because I have a similar issue.Thanks in advanced.


Google Analytics + Transparency Report

-> Write up a transparency report on what we do, how it improves our products, and make sure we don't overstep our bounds

Half Done, need to publish the transparency report markedown file to github


Simplify multiprocessing

Problem
We want prettier logging and progress bars, but there is not a super simple way to integrate multiprocess.py with a tqdm-like loader bar. Also, multiprocess.py seems unnecessary (@lajz lmk if there's a good reason for this file).
Proposed solution
Delete multiprocessing.py and replace with Python's builtin multiprocessing imap. To integrate a tqdm loader in the future, all we would need to do is replace
pool.imap(_execute_retrieval, args)

with
tqdm(pool.imap(_execute_retrieval, args))

Verification
All tests pass and there is no time difference between the custom logic in multiprocessing.py and using imap.

did you try an extensive benchmark (eg 1,000 shots) to test out edge cases that might be missing from our test set, or simply to put the scheduler under a bit more stress?


Expose "add_offset" control in concatenate_epochs

https://github.com/mne-tools/mne-python/blob/5cafa0f4287ae02fb2beafa557c0f70db8b7a1ed/mne/epochs.py#L2916
I find myself frequently using concatenate_epochs function to unite several sets of epochs for different events, and then sorting the epochs afterwards. This proves a great pattern for working with a database-like structure for machine learning applications.
However, the function by default gives an offset to the sets of events, which means that the resulting event timestamps lose their valuable information. Examining the function I have found that it uses _concatenate_epochs where you can disable giving an offset to the events.
I was wondering if there was a specific reason to not expose this control in the public function, and if there wasn't, would it be ok for me to submit a pull request of the correction? Thanks.

you just want to expose add_offset param in concatenate_epochs right?
I am curious how you can still make sense of events and time stamps when
merging epochs from different runs/raw files.

you just want to expose add_offset param in concatenate_epochs right?

Exactly that.

I am curious how you can still make sense of events and time stamps when
merging epochs from different runs/raw files.

Let me try to describe, perhaps it is an interesting use case.
I have a large EEG dataset collected in an ecological task -- driving in a simulator. I have built a system to create sets of events, sometimes overlapping, sometimes not, for example, all brakes, or all accelerations, or only those brakes which happen before a turn, etc. There are a lot of sets like that, and new ones can be added. They all happen within the same long session (at least if you're talking about 1 subject), but when I do ML on them, I just want to select a few sets. I've built a query system which gets the data around a selected set of events (a tensor n_epochs x n_channels x time) and puts it into the mne.EpochArray [1].
This way I collect epochs from different queries and concatenate them, after which I sort them chronologically. But I have to have the unaltered timestamps for each of them after I concatenate [2].
So in the end I can make sense of them, as they are all on the same recording.
[1] After trying at first to create epochs from a raw file using mne segmentation, I found that for what I am trying to do, it turns out more straightforward and efficient.
[2] I could work around it and get sorting order form a set of queries, but it would make more sense to use Epoch.events.

I think I get it but I would have do it this way:

concatenate raws to have a single raw object
make events and associated metadata
make one big epochs (eventually not preloaded)
use query mechanism of epochs to use metadata.

See here for a demo of using metadata:
https://martinos.org/mne/stable/auto_tutorials/plot_metadata_epochs.html

That's an interesting workflow to consider, thank you. Although, wouldn't that require me to fit all of the raw recordings in RAM at the same time? You wouldn't be possible in my case, as I have over 100 GB of raw files. Getting epochs separately allows me to never load raw data at all.

maybe it will work with preload=False ?

It could work with some types of data stores, which mne can query in an out-of-memory mode, but I have a database, and it doesn't seem feasible.
So in the end, do you think "add_offset" would be a useful control to expose, or you think it may encourage a wrong workflow?

+0.5 to expose add_offset if it's needed for you. It's not too invasive
change.

@antopolskiy can you take a stab at exposing the param for your use case?


Grouped function overloads into single definitions

Union types available in typescript as of 1.4. Some semantically identical overloaded function definitions have been tidied up into single definitions.

@bencoveney thanks mate!


Man pages

Every good unix program needs a man page.

Done!
https://github.com/jeo/jeo-cli/pull/4
Jared


kinfocenter: add optional dependencies to path

Description of changes
kinfocenter requires some packages to show some types of information, and now the derivation adds these in PATH.
Fixes #168320.
Continuation of #175738.
One problem that I'm facing (the reason this is a draft) is that kinfocenter isn't a standalone application, but it's just a symbolic link to systemsettings5, which check argv0 to see in which mode it needs to open.
However, I'm having trouble to do that, so if someone knows how to do it, it would be welcome.
I'm guessing that .systemsettings5-wrapped is interfering, but it's called with exec -a "$0", so I don't understand...
Also, pciutils seemed to do nothing in buildInputs, so I removed it from there. I don't know if there are more that can be removed.
Finally, a weird thing, but if the symbolic link isn't removed (by rm), makeWrapper doesn't override the file already there, but it creates a new one on the symbolic link location. Is this normal?
EDIT: I noticed that exec -a kinfocenter systemsettings opens the regular settings, while exec -a kinfocenter /nix/store/hash-systemsettings-5.25.2-bin/bin/.systemsettings-wrapped opens kinfocenter correctly. Probably related to #150841.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Closing, since this PR has no use with the way kinfocenter has been changed.


Where is init_fields defined?

node.rb reads
    def respond_to_missing?(*args)
      init_fields
      args.length == 1 && fields.include?(args[0])
    end

When trying the Python parser for instance, we enter this routine, and die for lack of definition of init_fields.
Maybe exposing "fields" directly as method names was a dubious idea, I don't know.

It was defined before refctoring, e.g. here.
I will remove it. Thanks.


support get the app build number. (Only Android tested.)

Hi, there.
I just added get app build number function. Seems there is another pull request about this. Just found after submit pull request. Too bad
Thanks.

You can now get to this functionality with cordova.getAppVersion.getVersionCode(). See #36.


remove incorrect firewall rules test cases and fix a couple of lint errors

- What this PR does and why is it needed

remove duplicate order rules test cases which is impossible with the latest API.
fix lint issue in the event code.

- How to verify it

make test

KUBEBUILDER_ASSETS="/home/mmahmoud/go/src/ingress-node-firewall/testbin/bin" go test ./... -coverprofile cover.out
?       github.com/openshift/ingress-node-firewall      [no test files]
?       github.com/openshift/ingress-node-firewall/api/v1alpha1 [no test files]
?       github.com/openshift/ingress-node-firewall/cmd/daemon   [no test files]
?       github.com/openshift/ingress-node-firewall/cmd/syslog   [no test files]
ok      github.com/openshift/ingress-node-firewall/controllers  10.645s coverage: 77.5% of statements
?       github.com/openshift/ingress-node-firewall/pkg/apply    [no test files]
ok      github.com/openshift/ingress-node-firewall/pkg/ebpf     0.036s  coverage: 0.0% of statements
ok      github.com/openshift/ingress-node-firewall/pkg/ebpfsyncer       0.018s  coverage: 0.0% of statements
?       github.com/openshift/ingress-node-firewall/pkg/failsaferules    [no test files]
ok      github.com/openshift/ingress-node-firewall/pkg/interfaces       0.003s  coverage: 25.0% of statements
?       github.com/openshift/ingress-node-firewall/pkg/metrics  [no test files]
?       github.com/openshift/ingress-node-firewall/pkg/platform [no test files]
ok      github.com/openshift/ingress-node-firewall/pkg/render   0.024s  coverage: 78.8% of statements
ok      github.com/openshift/ingress-node-firewall/pkg/status   0.017s  coverage: 41.4% of statements
?       github.com/openshift/ingress-node-firewall/pkg/utils    [no test files]
?       github.com/openshift/ingress-node-firewall/pkg/version  [no test files]
ok      github.com/openshift/ingress-node-firewall/pkg/webhook  7.027s  coverage: 85.3% of statements
?       github.com/openshift/ingress-node-firewall/test/consts  [no test files]
?       github.com/openshift/ingress-node-firewall/test/e2e/client      [no test files]
?       github.com/openshift/ingress-node-firewall/test/e2e/functional/tests    [no test files]
?       github.com/openshift/ingress-node-firewall/test/e2e/ingress-node-firewall       [no test files]
?       github.com/openshift/ingress-node-firewall/test/e2e/k8sreporter [no test files]
?       github.com/openshift/ingress-node-firewall/test/e2e/namespaces  [no test files]
?       github.com/openshift/ingress-node-firewall/test/e2e/pods        [no test files]
?       github.com/openshift/ingress-node-firewall/test/e2e/validation/tests    [no test files]

make test-e2e

JUnit report was created: /tmp/test_e2e_logs/e2e_junit.xml

Ran 11 of 11 Specs in 265.334 seconds
SUCCESS! -- 11 Passed | 0 Failed | 0 Pending | 0 Skipped

The linting fixes LGTM. I don't have enough enough context for the removed test cases, though given that's largely code deletion then also LGTM.

/lgtm

ci errors are known and traced by #139
/override ci/prow/ingress-node-firewall-e2e-metal-ipi

/override ci/prow/ingress-node-firewall-e2e-metal-ipi

/override ci/prow/ingress-node-firewall-e2e-metal-ipi


Add the descriptor finder to ConfigValidator.ValidateConfig

Add descriptors.Finder as a parameter to ConfigValidator.ValidateConfig and update everything. Follow on PRs will actually make use of the finder.

This change is

Jenkins job mixer/presubmit passed

Don't bother reviewing this yet. We want to expose descriptors to the managers, but not the adapters. Today both managers and adapters implement the same set of interfaces so this isn't possible. I'm going to split the interfaces into manager and adapter versions so we can hide this kind of detail from adapters.

Ditching this in favor of the PR currently out for review.


MNT: rerender

Hi! This is the friendly automated conda-forge-webservice.
I've started rerendering the recipe as instructed in #35.
If I find any needed changes to the recipe, I'll push them to this PR shortly. Thank you for waiting!
Here's a checklist to do before merging.

[ ] Bump the build number if needed.

Fixes #35

@Tobias-Fischer this for the "unmigration" from metis 5.1.1 back to 5.1.0, see https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/5396 . Can you please bump the build number here? I opened a PR via the feedstock, but I realized only later that I could not modify it. Thanks!

bumped

Ready to merge?

Ready to merge?

Yes!


Frontend Project "Valient-Institute-Site-main" Review Section Content Alignment

Describe the Feature you want to end
Uneven alignment of the content.
Expected behavior
Content equally aligned from all sides.
Screenshots (optional)
Current Alignment

Expected Updated Alignment

Additional context (optional )
N/A

@MohitGupta121


Education toolkit translation to Vietnamese

Hi!
Refer to issue https://github.com/huggingface/education-toolkit/issues/46, I finished translating all the necessary files.
Please feel free to take a review and feedback.

[x] README.md
[x] 01_huggingface-hub-tour.md -> 01_khám-phá-huggingface-hub.md
[x] 02_ml-demos-with-gradio.ipynb -> 02_demos-với-gradio.ipynb
[x] 03_getting-started-with-transformers.ipynb -> 03_khởi-động-cùng-transformers.ipynb

Thank you for the translation @honghanhh! I added you to the contributor's list in the main README.


azure-core needs docstring updates for sphinx

ACTION NEEDED: All sphinx errors and warnings must be fixed by 2024-04-15. The build will begin to fail for this library if errors are not fixed.
This issue indicates that your library reference documentation is rendering with errors. To avoid customer issues, please ensure you take care of these errors and warnings ASAP.
Library name: azure-core
Sphinx build: Link to build (2023-12-31)
How to fix: Run the strict-sphinx tox command at the library package-level and resolve the docstring errors and warnings.

../azure-core>pip install "tox<5"

../azure-core>tox run -e strict-sphinx -c ../../../eng/tox/tox.ini --root .

Once resolved, set strict_sphinx = true in the package's pyproject.toml file.

See Sphinx and docstring checker for more information.

Done.


Random encoding issues in "Source file occurrence"

Hi,
We are randomly getting non-printable characters when using the very useful "Source file occurrences" feature.

I don't think there is an encoding issue with the source file itself because the bug appears and disappears without us editing the file.
Any ideas?
Thanks!

Can you please provide full reproduction instructions? There's certainly nothing "random" about this, but it's hard to investigate anything when all I have are some pictures. Please provide details about your OS, its version, Poedit version, attach relevant files and provide step-by-step instructions on what to do to see it myself. (See here for why I need this.)
At a glance, it's evident that charset detection changes between the two images, and without further information the most likely explanation is that it really changes, e.g. because you're saving the file somewhere in the meantime, differently. Part of the need for detailed step-by-step reproduction is to rule that out.

I am using version 2.2.3 on Windows 10.
I have attached a simple po file that exhibits the issue:
en.zip
Jumping into the source file repeatedly using the "References" context menu option sometimes displays the accentuated characters incorrectly for me. I was able to confirm using ProcessMonitor that no other process other than Poedit reads or writes to the source file during that time.

Can you please provide the information I asked for, i.e. precise step-by-step, keystroke-by-keystroke instructions on what to do with the files you attached? Specific actions, specific settings, specific strings, instead of high-level overviews like "use these files" or "jump around"; also where to put the files on disk (relative to each other and absolute, i.e. what kind of drive etc.). This may seem obvious to you, but isn't immediately clear to other people.
TIA!

The files you attached are not the files in the screenshot. The PO file contains only a single nonsense string àâéèêîïôùûçàâéèêîïôùûçàâéèêîïôùûçàâéèêîïôùûçàâéèêîïôùûçàâéèêîïôùûçàâéèêîïôùûçàâéèêîïôùûç and the source file is just that line repeated over and over.
It looks like something is seriously wrong outside of Poedit there.

Thank you for looking into this.
The specific content of the file doesn't matter. Any file file with accentuated characters will exhibit the behavior shown in the screenshot.
I'm sorry I can't provide you with an easily reproducible setup, the encoding issue does unfortunately seem to appear randomly.
Could there possibly be some sort of a race condition with wxConvAuto()? not always getting the encoding right in fileviewer.cpp?
I'll try to build poedit and investigate the issue sometime next week.

This bug was one of the more interesting wild goose chases.
Upon investigation, none of the above jumped-to conclusions were correct: it's deterministic (affected by OS memory management, but not random), there's no race condition and it affects only very particular files that are neither "any file with accentuated characters" nor is the presence of accents or diacritics required to trigger it.
Specifically, it only affected UTF-8 files with DOS line endings, no BOM (this combination is culturally rare: both CRLF and UTF-8 BOMs are a thing on Windows, but atypical anywhere else), just the right size and some non-ASCII characters to observe the difference.
The culprit is a bug in wxWidgets' conversion of buffers read from FILE*, due to CRT's behavior of implicitly converting DOS newlines to \n and thus returning fewer bytes than the file's size. While this was addressed in the code, the mitigation stopped being effective at some point in the past when support for embedded NULs in strings was added across the codebase… and nobody noticed this because strings tend to be converted into NUL-terminated C strings awfully often, hiding any corrupted tails.
https://github.com/wxWidgets/wxWidgets/commit/17e2f8c477e4064a042c8deea1adb2efde8109e8


unused_variables, add option to exclude a list of variable names

unused_variables, add option to exclude a list of variable names
use-case: P_TASK parameter is required for parallel processing using PERFORMING AT END OF TASK

see https://github.com/abaplint/abaplint/blob/master/packages/core/test/rules/naming/method_parameter_names.ts it has a similar feature

thanks, closing

thanks, closing


Update purescript-generics to 0.7.0

anyProxy is now gone, it's not even in Type.Proxy. Means the next release of purescript-batteries will require a major version bump.

:+1: Thanks!

Released in v0.4.0.


Adding qryn to the registry and vendor list

Hello Maintainers,
Opening this PR to add qryn to the list of integrations and vendors. Hopefully the template was correctly followed 🤞

Link to your distribution, if applicable

https://github.com/metrico/otel-collector

Link that proves that our offering is open source:

https://github.com/metrico/qryn/blob/master/LICENSE

GitHub handle or email address as a point of contact

@lmangani

Thanks in advance!

/fix:format

Thanks @svrnm 😍


Doubts with Port forwarding

Hello to all,
First of all thank you very much for this great tool.
I'm just starting to use it and no matter how many times I've tried I can't find a manual to clarify how to do a port forwarding.
I think it's a simple thing to do, but I can't get it done.
I will explain my case.
I have a redirection in my router that sends the requests that arrive on port 443 to the IP <IP_ADDRESS>:3208.
On the other hand, I have two domains. The domain A is the IP <IP_ADDRESS>
And the domain B is the IP <IP_ADDRESS>
I need that when a request arrives with the name of domain B, Nginx redirects the port 443 to the IP of domain B and port 3218.
i.e. to IP <IP_ADDRESS>:3218
How could I do this?
Thanks to those who can help me.

Hey, I think I can help you :)
What router do you have, I don't think that every router supports that, but I am not sure ?

Hey, I may help @npirtube :)
What you probably can do, is to set an SSL certificate, and turn on "Force SSL", to automatically redirect all traffic from 80 to 443 and then redirecting to your IP like this:

Hope this helps :)

Thanks for your help my friend, but that's not what I'm looking for.
I need to send what arrives on port 443 to 3218.


Composable Type mismatch Found Any

I'm using Kotlin 1.5.31
compose desktop 1.0.0-alpha4-build398
Gradle 7.1
IntelliJ IDEA Ultimate:
IntelliJ IDEA 2021.2.2 (Ultimate Edition)
Build #IU-212.5284.40, built on September 14, 2021
Runtime version: 11.0.12+7-b1504.28 x86_64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 11.6
GC: G1 Young Generation, G1 Old Generation
Memory: 6000M
Cores: 12
Non-Bundled Plugins: Batch Scripts Support (1.0.12), co.anbora.labs.firebase-syntax-highlighting (2.6.6), mobi.hsz.idea.gitignore (4.2.0), CMD Support (1.0.5), PlantUML integration (5.6.1), Pythonid (212.5284.44), intellij.prettierJS (212.5080.8), com.jetbrains.php (212.5284.49), com.github.iguissouma.nxconsole (0.33.0), com.intellij.nativeDebug (212.5284.19), org.jetbrains.kotlin (212-1.5.31-release-546-IJ4638.7), org.jetbrains.compose.desktop.ide (1.0.0-alpha4-build398), com.squareup.sqldelight (1.5.2)
Kotlin: 212-1.5.31-release-546-IJ4638.7

Here is an error that I think is happening due to the @Composable in the type system.
class Test(val flow: Flow<BufferedImage?>)

@Composable
private fun Screen(test: Test) {
    val capture: ImageBitmap = test.flow
        .map { it?.toComposeBitmap() }
        .collectAsState(Dispatchers.Default).value ?: return

    Image(capture, "")
}

Here is the error:
Type mismatch.
Required:
ImageBitmap
Found:
Any

When I break down  the code further you can see that the type problem is happening with the Composable function.

The work around  is to  cast:
class Test(val flow: Flow<BufferedImage?>)

@Composable
private fun Screen(test: Test) {
    val flow: Flow<BufferedImage?> = test.flow
    val imageBitmapFlow: Flow<ImageBitmap?> = flow.map { it?.toComposeImageBitmap() }
    val capture: ImageBitmap = imageBitmapFlow.collectAsState(Dispatchers.Default).value as ImageBitmap? ?: return

    Image(capture, "")
}

Nevermind. I see now that I've passed Dispatchers.Default as the initial state fort he collectAsState function which is what's  causing  this problem.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Feature Request: allow multiple groups to share Redis connections

Redis hosting plans which allow large numbers of connections tend to be quite expensive. My app is hitting dozens of API endpoints each with their own throttling scheme.
Is it technically feasible to allow groups with different minTime or maxConcurrent to share the same connections? This would save money on resources.
BeeQueue allows each group to share the same primary connection, and creates additional connections on-demand only when needed...

`Note that this [Redis config] can also be a node_redis RedisClient instance, in which case Bee-Queue will issue normal commands over it. It will duplicate() the client for blocking commands and PubSub subscriptions, if enabled.

Related: #84

Not at the moment, but simple connection sharing should be released within the next 2-3 weeks.

I've completed the functionality and tests for this feature, it will be released in v2.11.0 in a few days.
The solution I came up with is more flexible than BeeQueue's. You'll be able to either:

Pass a raw redis client and let Bottleneck create a new pubsub connection for every group and standalone limiter (same behavior as BeeQueue).
or
Reuse the same client+pubsub pair across all your groups and limiters, which will guarantee that never more than 2 connections are open.

@SGrondin docs look perfect. Thank you so much for your responsiveness. This will help a lot in keeping my bills down as I scale!
As for my use case, I'm doing web scraping for price monitoring of e-commerce sites.
I have a worker which tracks which URLs are due to be scraped and schedules them in BeeQueue at a random time in a window and limits the overall concurrency so as not to overload the worker.
I then have a bank of proxies and a load balancing algorithm which chooses a proxy balancing requests to each domain evenly across the proxies. Each proxy then has a master limiter in Bottleneck to prevent it from becoming overloaded. Each proxy-domain pair then has a Bottleneck limiter (chained to the master limiter) to reduce the chances of that proxy getting IP banned, and the settings can be customized to each domain.
So far I'm still in development on one worker getting the bugs worked out, but will soon scale to multiple workers.

v2.11.0 has been released

That's a really cool use case, @colinskow . I hope Bottleneck is meeting your expectations. If something is missing feel free to open another issue. Deciding how to expose a feature to users is always harder than developing it. I had already begun thinking about manual connections so that's why this was so quick.

I'd love to hear your thoughts on this @colinskow @gsmtamil @edwardupton @TheGame2500
I've been thinking about expanding Bottleneck into BeeQueue's territory since I began work on the Cluster feature a year ago. At the moment, I believe most Cluster users rely on some other library like BeeQueue or they just use their main SQL database as the queue. The publish() method I added recently was a first step in integrating this functionality into Bottleneck itself and it can be used to get around the current Clustering limitations.
The problem with adding this functionality is how to integrate it into the current library. Something like new Bottleneck.Task()? After using Sidekiq professionally for a few years, I have a whole new level of expectation for a background processing system. I view it as a related but distinct problem from what Bottleneck does. The reason I'm even considering this is because of the limitations when using Clustering: priorities are almost useless, counts and most events are local only, etc. It's hard to explain in the docs what is Cluster-wide and what is local.
So should a task processing system be integrated at all? Or should those hypothetical tasks have to call limiters manually? If it's manual then what even is the point of adding this to Bottleneck?

@SGrondin I have no experience whatsoever with BeeQueue though I have heard of it. Would you mind explaining how the newly integrated Task would be different to a queued job right now and potentially offer a use case  ?

Suppose this code is running on a Cluster of 10 computers:
const limiter1 = new Bottleneck({
  shareQueue: true,
  id: "process-spreadsheet",
  maxConcurrent: 2,
  minTime: 500,
  clientOptions: {}
});

limiter1.on("run", (arg1, arg2) => {
  // process job
});

limiter1.schedule({ priority: 1, expiration: 10*1000 }, arg1, arg2)
.then((result) => { /* ... */ });

In this example, any Nodejs process in the Cluster can add jobs. Any of those handling the "run" event might have to execute the job.
This is profoundly different from the current system. Not only can jobs be executed on a different process, it also means the arguments and results need to be serialized and passed over the network. What it gives us is priorities and counts that work cluster-wide and queues that are stored entirely inside Redis, so queued jobs aren't lost when a client disconnects.
It's an entirely different paradigm and I'd like to know if there's any interest. It would be a huge effort. Something like shareQueue: true is probably not a good idea because it means all of a limiter's features now need to work in this totally different paradigm. Maybe this needs to be a different library or maybe Bottleneck needs to have built-in integrations with something like BeeQueue.
Would any of this be useful?

It would certainly be nice to handle all scheduling and limiting with one API. But the queue and limiter do serve distinctly different roles, so I'm trying to wrap my head around how they would work together.
Currently I use BeeQueue to schedule jobs in approximate time windows, and the limiter to make sure resources don't get overloaded. Right now I have a function that handles queue jobs which are ready to run, and that then waits for the appropriate limiters (proxy, domain etc.) before executing the actual task.
It seems to work the way it's set up, but I'm always open to ideas for making it better!

Thanks for the feedback.

But the queue and limiter do serve distinctly different roles, so I'm trying to wrap my head around how they would work together.

The more I think about it, the more I think this is exactly right. Limiters do have a queue of their own, but trying to build a proper queue out of a limiter seems like the wrong way around.
I'll keep thinking about this and I might reach out to the BeeQueue maintainers to suggest integrating Bottleneck into BeeQueue as an optional setting.


[HUDI-8331] Remove excessive table validity check

Change Logs
Remove TableNotFoundException#checkTableValidity and its usages.
This method is excessive because Hudi should just fail later on if this path is not valid/does not exist. This check is also problematic because it adds excessive FS calls, which can be very expensive when interacting with object stores like S3.
Impact
none
Risk level (write none, low medium or high below)
low
Documentation Update
none

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

There is a test failure in azure CI but I cannot reproduce the issue locally, seems like a flaky test

+1, makes sense.


Elm watch

Resolves #440
Resolves #430
Actually addressed in last year, I forgot all of I wanted..

Closing for now to suppress noise


Release gax-nodejs v0.20.0

This pull request was generated using releasetool.

Please do not merge (yet), I need to run some tests first. That's a pretty scary change. ETA later today :)


Nore-Red alafile in node

Something is not working as expected:

In case fill "Name of file" dialog in node all work perfect (this node I use for import from *.xls file)
In case to input I send "msg.filename" (the same name as previous) node doesn't work = none outputs

Versions:
node-red-contrib-alasql = 2.0.1
node-red editor = v3.0.2
platform = linux Mint

Ok, i solved it myself. It work if i send msg.filename="pathtoyourfile" and msg.payload="true"

Ok, i solved it myself. It work if i send msg.filename="pathtoyourfile" and msg.payload="true"


im just stuck trying to use it i got everything else

i go to run python reroll.py and it says 2024-07-04 15:35:50,679 - ERROR - config.json not found! Please place it in the script's directory.

im just super lost
i got everything else to work


Allow _key set to null?

I've noticed that when you save a document and have _key set to null, you'll get an ArangoError "invalid document key". Would it be ok to allow this, having ArangoDB set the key as if it doesn't exist, when you save it?
It can be useful when creating objects like this for example:
class Person {
    constructor(id, name) {
        this._key = id;
        this.name = name;
    }
}

My case is that I'm using the transpiler language Haxe, where fields are set automatically when instantiated, so you'll always have _key == null, and the only way to save an object is to make some shady Reflection stuff, deleting the field.

undefined and null have different meanings in JavaScript. A field set to undefined will be omitted in the JSON representation, a field set to null indicates an intentionally empty value.
Can you solve this problem on your end by explicitly initialising the value to undefined instead or is this a limitation of Haxe?

That's the intention I was thinking about in this case, since _key cannot be empty in the database, setting the field to null could mean "set this for me, please". But it's no big issue for me.
Yes, it's a Haxe "limitation" :) It doesn't have undefined, unless you use some special functions and inject raw javascript. It would be nice to stay away from that, or using reflection.

Now that I think about it, there's never a reason for _key to be anything false-y, so it makes sense to clear the attribute if it would otherwise be something false-y (null, zero, empty string, what have you).

That's what I'm thinking too, the only thing I can think of would be if someone sets it by mistake. But _key is a well-known, special attribute, so I'd be surprised if someone doesn't know about it, in these circumstances.

Changing this would require modifying the data passed to arangojs before sending it to the server. Doing that to obscure a potential error by obscuring sloppy input seems like a bad idea. I'm closing this issue as this won't be implemented. If you want the API to support null values, I suggest opening an issue at ArangoDB instead.