[WIP]  improve pure partition count star performance

Why is this PR needed?
To improve pure partition count star performance

currently the count(*) with filter whose culumns are all partition columns will load datamaps of these partitions including block info/minmax info, but it is no need to load them ,we can just read it from valid index files directly as the rowCount stored inside, and cache these info.

For no-sort partition table, minmax is almost no using but cost time.

What changes were proposed in this PR?
The detail of query flow as following if it is pure partition count star
Step 1. check whether it is pure partition count star by filter
Step 2. read tablestatus to get all valid segments, remove the segment file cache of invalid segment and expired segment
Step 3. use multi-thread to read segment files which not in cache and cache index files list of each segment into memory. If its index files already is eixst in cache, not require to read again.
Step 4. use multi-thread to prune segment and partition to get pruned index file list, which can prune most index files and reduce the files num.
Step 5. read the count from pruned index file directly and cache it, get from cache if exist in the index_file <-> rowCount map.
Does this PR introduce any user interface change?

No

Is any new testcase added?

No

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/977/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2690/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/980/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2693/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/994/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2707/

@Zhangshunyu : What do you mean pure partition ?  is it just normal "partition" ?
Also mention what was the bottleneck before in the description.

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1000/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2712/

@ajantha-bhat
We find that select count() for some partitons is time costly and worse than parquet, as currently the count() with filter whose culumns are all partition columns will load all datamaps of these partitions including block info/minmax info, but it is no need to load them ,we can just read it from valid index files directly using partition prune as the rowCount stored inside index files, and we can cache these info. For no-sort partition table, minmax is almost no using but cost time.

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2714/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1002/

@Indhumathi27 : we are already matching partition first, before the loading min max (your old PR)
That was done only for select * flow, not for count(*) flow ?

@ajantha-bhat  I mean cout star for partiton columns no need to load minmax

@ajantha-bhat It was done for filter on partition columns.

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2722/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1010/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1033/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2746/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/2781/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1068/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1733/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3475/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/3476/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/1734/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2354/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/4095/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/4096/

Build Failed  with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.5/2355/


Make the directory the shaders live in more clear.

Hopefully this kind of PR isn't more irritating that helpful. I think it might be helpful to newbs like me to name the directory where the shaders live shaders/.

@chrisduerr I've never done any "real" OpenGL programming, so I'm not familiar with this convention. Either way is fine then, just thought I'd throw this out there :P


Add more than 1000 emojis. Update dependencies. Add multi testing in …

…Github Actions

Codecov Report

Merging #14 (909ac61) into main (dc83be6) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #14   +/-   ##
=======================================
  Coverage   97.14%   97.14%
=======================================
  Files           1        1
  Lines          70       70
=======================================
  Hits           68       68
  Misses          2        2

Flag
Coverage Δ

unittests
97.14% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


ChildProcessError: Command failed: "/Users/xxxx/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "ps | grep (exited with error code 1) (code=1), stdout and stderr:

What happened?
17:00:29.659 detox[50442] i child-process:EXEC_FAIL ""/Users/xxx/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "ps | grep "com.xxx.xxx.xxx.android.dev$""" failed with error = ChildProcessError: Command failed: "/Users/xxxx/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "ps | grep "com.xxxx.xxxx.xxxx.android.dev$""
"/Users/mhorvat/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "ps | grep \"com\.xxxx\.xxxx\.xxxx\.android\.dev$\"" (exited with error code 1) (code=1), stdout and stderr:
What was the expected behaviour?
No response
Was it tested on latest Detox?

[X] I have tested this issue on the latest Detox release and it still reproduces.

Did your test throw out a timeout?

[X] I have followed the instructions under Identifying which synchronization mechanism causes us to wait too much.

Help us reproduce this issue!
run: detox test -c android.ci.debug --runInBand --reporters='default' --loglevel verbose
In what environment did this happen?
Detox version:
React Native version: 0.70.5
Has Fabric (React Native's new rendering system) enabled: (yes/no) no
Node v18.17.1
Device model: Emulator
Android version: 12
Test-runner (select one): jest / other: jest
Detox logs
Detox logs
paste logs here!

Device logs
Device logs
17:00:29.659 detox[50442] i child-process:EXEC_FAIL ""/Users/xxx/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "ps | grep \"com\.xxx\.xxx\.xxx\.android\.dev$\""" failed with error = ChildProcessError: Command failed: "/Users/xxxx/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "ps | grep \"com\.xxxx\.xxxx\.xxxx\.android\.dev$\""
 `"/Users/mhorvat/Library/Android/sdk/platform-tools/adb" -s emulator-5554 shell "ps | grep \"com\.xxxx\.xxxx\.xxxx\.android\.dev$\""` (exited with error code 1) (code=1), stdout and stderr:

More data, please!
No response

@mariushorvat please elaborate which android sdk and avd image you are using. 🤔

@noomorph Here are my gradle settings. Thanks for looking into!
buildToolsVersion = "31.0.0"
minSdkVersion = 23
compileSdkVersion = 31
targetSdkVersion = 33
kotlinVersion = '1.7.20'
classpath("com.android.tools.build:gradle:7.2.1")

reactivecircus/android-emulator-runner
        with:
          api-level: 31
          avd-name: Automation_Device
          force-avd-creation: true
          emulator-options: -no-window -noaudio -no-boot-anim
          disable-animations: true
          arch: x86_64

Locally on my Mac there aren't issues, everything runs smoothly. The problem it's only in the Github Actions. I would look into what you've have replied and report back. Thanks!

@mariushorvat that's rather foreseeable, so this is exactly why I'm asking to assist with retrieving that AVD image so we can see what's wrong with it.

@noomorph hey, I have this issue occurring locally with non-AOSP AVD images on API 33 & 34. Config attached.
AOSP images work fine.
Curiously on our CI (in headless mode) the install eventually succeeds, only failing the first few tests.
Detox version: 20.13.5
React Native version: 0.72.7
Has Fabric: no
Node v21.2.0
Device model: Emulator
Android version: 13
Test-runner: jest
config.txt


feat: finalize mdBook, document combined JSON

What ❔

Documents combined JSON output.
Fixed all mdBook rendering issues.

Checklist

[x] PR title corresponds to the body of PR (we generate changelog entries from PRs).
[x] Tests for the changes have been added / updated.
[x] Documentation comments have been added / updated.
[x] Code has been formatted via cargo fmt and checked with cargo clippy.

We can introduce https://github.com/tommilligan/mdbook-admonish later to add support for tip and info, etc.

Yeah, this thing will be awesome!
I've quickly HTML-ed warnings to have at least something in the upcoming release.


feat: add spaced repetition

Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes #74
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Manual Testing

Checklist:

[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings

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


Use LeaveOnClose event with Streams membership manager

The Streams membership manager did not use the LeaveOnClose event to faster leaving the group on closing. With the event the Streams membership manager leaves the group without invoking any callback for releasing the active tasks.
With this commit the Streams membership member uses the LeaveOnClose event.
Committer Checklist (excluded from commit message)

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

Call for review: @aliehsaeedii

SmokeTestDriverIntegrationTest takes 40s with this change.


Cache lifetime?

First of all, thanks for actively maintaining this repo and for providing examples for all frameworks 👍 . This is really great.
I could not find what the lifetime of the image cache is? Is it unlimited? Is there a way to set it? Is there a way to clear the whole cache?

There is .clear() a static method

@triniwiz Currently I am unable to get the .clear() function to properly clear the cache.

@CarissaHurt any error ?

@triniwiz There use to be an error on Android, however after upgrading to the most recent version, I do not get the error anymore. I believe the version we upgraded from was NS 6.1 -> 6.3.
Currently ts throws a warning for the .clear() function because it requests to have a src passed into the function, however after further research into the plugin code, it seems unnecessary.
To test I am using an iPhone simulator (exact version is iPhone 7 13.3). I get the saved cache src and follow it in my finder to view the folder the photos are being held in. Then I use the clear function, however all the photos are still held in that location. I could be missing something, any thoughts?


Move "Learn more" link beside "Got it!" button

Hi,
I was wondering if it's possible to move the "Learn more" link beside the "Got it!" button.
Any help would be appreciated.
Thanks in advance

@mrleemon Sorry for the delayed reply. Are you still looking for help with this?

No, I managed to find the solution myself. Thanks, anyway!


Watch Protocol

Hi !
I try to setup a watch in port 5093.. traccar recognizes the string but this switch to possitive lat and Lon...
This is the string:
[3G*6105117105*008D*UD2,210716,231601,V,-33.480366,N,-70.7630692,E,0.00,0.0,0.0,0,100,34,0,0,00000000,3,255,730,2,29731,54315,167,29731,54316,162,29731,54317,145]

And this is the traccar log (possitive):
id:<PHONE_NUMBER>, time: 2016-07-21 20:16:01, lat: 33.48037, lon: 70.76307, speed: 0.0, course: 0.0

I have added a workaround, but the message is invalid. It shows negative latitude, but says that it's in North hemisphere. Same with longitude.


Clicking on a column at the far right of screen causes a selection box

I fixed it by making a change in docview.lua:
  -- scroll to make caret visible and reset blink timer if it moved
  local line, col = self.doc:get_selection()
  if (line ~= self.last_line or col ~= self.last_col) and self.size.x > 0 then
    if core.active_view == self and self.mouse_selecting == false then
      self:scroll_to_make_visible(line, col)

My change was adding and self.mouse_selecting == false

The root of this issue was some other behaviour which I've now reverted as it ended up causing more problems than it solved


1062: Payment clarification

resolves #1062

Please adjust the label in the backend accordingly (unfortunately we have duplication of the labels...): https://github.com/digitalfabrik/entitlementcard/blob/main/backend/src/main/kotlin/app/ehrenamtskarte/backend/application/webservice/schema/create/WorkAtOrganization.kt#L30

@michael-markl done.


Span background does not work well with 16:10

When I enable span background on a 16:10 display (in my case its the legion go), I get black borders on all corners and the image does not look right at all. I have to keep using the default 16:9 background for now , but that leaves the top and the bottom be visible during loading screens and menu view

That's v1.0.2 out, it should hopefully address your issue.

Thanks a lot for your support, it seems the issue is now resolved with the latest version

Thanks a lot for your support, it seems the issue is now resolved with the latest version


Allow top-level await.

Await can easily be supported at the top level; this change allows it.
This change is designed to make CoffeeScript a more effective platform
for learning to program.  Allowing top-level await allows beginners
to write simple programs that work with asynchronous input before
learning how to use functions.
(This solves a key problem with teaching in Javascript.)
A sample program:
delay = (t) -> new Promise (resolve) -> setTimeout(resolve, t)

console.log('waiting for 5 seconds')
await delay 5000
console.log('done waiting')

@davidbau This feature makes sense to have cause it seems redundant and to need to create an IIFE to have async code run when all code in CS files is nested in a closure automatically.

Yup.  It seems redundant to require a "do ->" and an extra indent to make it work.  The beauty of CoffeeScript is that it is a very low ceremony language.  This would help keep it that way.
Would you be willing to merge this to include it in your pull request?


KeyError: 'KittiMultiViewDataset is not in the dataset registry'

When using Imvoxnet, the config file in configs/sv3d-inf/imvoxelnet/trainval_config.py uses KittiMultiViewDataset dataset type. However, the official version of mmdetection3d v0.17.1 doesn't have this type of dataset. In addition, I noticed that the Imvoxelnet in https://github.com/saic-vul/imvoxelnet contains KittiMultiViewDataset dataset, while the mmdetection3d v0.8.0 version is required.

When using Imvoxnet, the config file in configs/sv3d-inf/imvoxelnet/trainval_config.py uses KittiMultiViewDataset dataset type. However, the official version of mmdetection3d v0.17.1 doesn't have this type of dataset. In addition, I noticed that the Imvoxelnet in https://github.com/saic-vul/imvoxelnet contains KittiMultiViewDataset dataset, while the mmdetection3d v0.8.0 version is required.

Thanks for your remind. This config is suitable for the order version of mmdetection3d. You can also directly use the imvoxelnet config in mmdetection3d 0.17.1, which now can only support one class. We are collaborating with the mmdetection3d to build the new config of multiple class for imvoxelnet.

When using Imvoxnet, the config file in configs/sv3d-inf/imvoxelnet/trainval_config.py uses KittiMultiViewDataset dataset type. However, the official version of mmdetection3d v0.17.1 doesn't have this type of dataset. In addition, I noticed that the Imvoxelnet in https://github.com/saic-vul/imvoxelnet contains KittiMultiViewDataset dataset, while the mmdetection3d v0.8.0 version is required.

We have updated the ImvoxelNet config, checkpoint, and evaluation results with mmdetection3d==0.17.1. More details can refer to the commit https://github.com/AIR-THU/DAIR-V2X/commit/60332a6e8a32345941e1b4b9c19b71d5ab05468c.


JS error "undefined is not a function" in jquery.jstree.js

[captured JavaScript error] Uncaught TypeError: undefined is not a function in .../framework/thirdparty/jstree/jquery.jstree.js?m=1408922701:939:12
[13:18:52][Step 2/2] STACKTRACE:
[13:18:52][Step 2/2] TypeError: undefined is not a function

Don't think we've hit this in a while - closing.


In production, \Amp\Promise\some() allows you to pass Deferred instances to it.

In dev mode, \Amp\Promise\some() doesn't allow Deferred instances but in live mode, Deferred is optimised to a Promise and so some() doesn't throw an error. This is a change in behaviour between dev and live which shouldn't exist.

It is like there were an assertion in \Amp\Promise\some(): assert(!$promise instanceof \Amp\Deferred). As assertions are off in production, it obviously allows you to do it in production. But that's inherent to the nature of assertions, if you turn them off.
If you want to be strict in production, then, obviously, turn the assertions active and set zend.assertions=1 in your ini.

Duplicate of #155.
It's documented here: https://amphp.org/amp/promises/#promise-creation


Fix bugs in named interceptor test.

The PropertyQuery callback needs to return something in order for V8
to consider the property present in Node.js 10.
Fixes failing test test/js/namedinterceptors-test.js

Thank you. Merged.


[package] Update Reaction/react-html-parser to work well on the server

Here Force is being polyfilled to have access to DOMParser.

👍
#mergeOnGreen


[site-object] 🛢 Add basic site profile object

See https://trello.com/c/JG5FMRPZ/132-i-want-a-configurable-non-product-related-deployment-of-metadeploy

@jlantz @jgerigmeyer This is the start of what we need for https://trello.com/c/JG5FMRPZ/132-i-want-a-configurable-non-product-related-deployment-of-metadeploy
But I don't know what the full version of that story looks like. Can some of us get together and talk about it in the not-too-distant future and figure out what the acceptance criteria for this might be? Thanks!

@wlonk I think this is heading in the right direction.
name should be translated.
A separate installation would also potentially need the ability to customize the copyright notice.

@davisagli should name be translated? It didn't seem to me that it would vary per-language.
Customized copyright notice is good.
@jgerigmeyer do you want to query this object on the frontend, to populate those text areas? I can make an endpoint to that.

@wlonk I'm thinking of a site name that is like [brand] Installer

@davisagli ah ha, got it.

@wlonk This looks like a good start. Rather than adding an API query, can we just pass this data through the GLOBALS var that gets injected into the index.html template?

@jgerigmeyer much better idea! I will do it.

@wlonk Looks good to me. Go ahead and make the front-end adjustments as well?

@davisagli Just a heads-up that this removes "Salesforce.org" and the SFDO logo by default, so you'll want to edit the new site-object on any deployments. I left the salesforce-logo.png and salesforce-favicon.png files in the repo (static/images/) to make that easier, even tho they're not being used directly.

@davisagli As far as I'm aware this is ready to merge once you give your 👍.

@jgerigmeyer I saw this; was busy today but will try to get it merged and deployed tomorrow.

@jgerigmeyer I saw this; was busy today but will try to get it merged and deployed tomorrow.

No rush; just wanted to be sure you were aware.


Library mode does not respect the --mode flag

Describe the bug
I'm using the vite library mode in my monorepo to build the common packages between front and backend.
For development I used: vite build --mode development
and for production: vite build
After upgrading to vite 4, both commands seem to replace import.meta.env.PROD with true, before, it replaced it with false in development mode.
The replacement depending on the mode works in non library mode as far as I can tell
Reproduction
https://github.com/juliushuck/vite-issue/settings
Steps to reproduce
I have added the two commands i use in the package.json scripts
System Info
System:
  OS: macOS 13.0
  CPU: (10) arm64 Apple M1 Pro
  Memory: 76.44 MB / 16.00 GB
  Shell: 5.8.1 - /bin/zsh
Binaries:
  Node: 16.16.0 - ~/.nvm/versions/node/v16.16.0/bin/node
  Yarn: 3.3.0 - /opt/homebrew/bin/yarn
  npm: 8.11.0 - ~/.nvm/versions/node/v16.16.0/bin/npm
Browsers:
  Chrome: 108.0.5359.98
  Firefox: 105.0.3
  Safari: 16.0

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

This is expected in Vite 4. vite build will default to PROD by default, the mode defines the different type of build. If you want to get the old behaviour, you can set NODE_ENV=development in .env.development like in https://vitejs.dev/guide/env-and-mode.html#modes

Ok,
so I set NODE_ENV=development in .env-development. The import.meta.env.PROD value did not change, but .MODE changed to development. So I could use that, but I do not want to have to create .env files in my common packages every time I clone the repo, because I have other values in those .env files that I can not push to GitHub.
So I tried around and got this working:
const checkIsProductionMode = () => process.env.NODE_ENV === "production";

To be honest, I do not even know why it works, because I thought process is a node thing and does not work in the browser. But with that, it uses the --mode flag of the command I run the final package with (the one that uses the common package build output).

so I set NODE_ENV=development in .env-development. The import.meta.env.PROD value did not change

Ah this is a bug. I found the cause.

So I could use that, but I do not want to have to create .env files in my common packages every time I clone the repo, because I have other values in those .env files that I can not push to GitHub.

You can put the secrets in .env.development.local instead. .env.development can be commited to git.

You can put the secrets in .env.development.local instead. .env.development can be commited to git.

Ah, that's the trick, will use that with import.meta.env.MODE === "production" for now then


forum in spanish

create forum in Spanish?
I think it would be a good idea so people can ask questions and there is an archive of solved issues in Spanish.

I like this idea. do you propose to make a channel on forum.processing.org, a subdomain at that location (something like forum.processing.org/es), or use an alternative channel altogether?

I think it should be a channel on forum.processing.org, called "Preguntas en español", I don't like the idea of  a subdomain or alternative channel, I want both the English and the Spanish speaking communities to be aware of each other on the forum, to coexist on the same place.
I can do a manual for registering as a user, so we don't have to translate the forum site.
Or maybe tha Vanilla framework it runs on has a cool i18n feature to detect language of the browser,
or something like that, let me check.

sounds good to me. @REAS I think you are the forum master? is it cool if I add a channel once @montoyamoraga has created the spanish instructions?

Let's please have a quick roundtable about the Forum. Adding a channel is great, but... does the forum need a new approach in general? As is, a simple update, something more? Before expanding, I think it's worth evaluating it, even if we don't update anything.


apachestreampipes/pipeline-elements-all-flink:0.93.0 not found

Apache StreamPipes version
dev (current development state)
Affected StreamPipes components
Connect
What happened?
Can´t run the full docker-compose file, because .env defines 0.93. This tag does not exist for pipeline-elements-all-flink in docker-hub. Please update tag in docker hub.
Workaround: edit docker-compose.full.yml and adjust tag:
pipeline-elements-all-flink:
image: "${SP_DOCKER_REGISTRY}/pipeline-elements-all-flink:${SP_VERSION}"
to
pipeline-elements-all-flink:
image: "${SP_DOCKER_REGISTRY}/pipeline-elements-all-flink:0.93.0-SNAPSHOT"
How to reproduce?
docker compose -f docker-compose.full.yml up
log:
Error response from daemon: manifest for apachestreampipes/pipeline-elements-all-flink:0.93.0 not found: manifest unknown: manifest unknown
Expected behavior
just running as expected
Additional technical information
No response
Are you willing to submit a PR?
None

Hi @kruscho,
thank you verry much for opening this issue.
The Flink pipeline elements are currently not supported, due to version incompatibilities (#1740).
In the meantime, I propose to remove it from the compose file. (#2432)

Due to resolution in #2432, the error should not occur again.


-Zbuild-std is appended in the wrong position

Checklist

[X] I've looked through the issues and pull requests for similar reports

Describe your issue
Trying to pass extra arguments to clippy on a target with no std (x86_64-unknown-dragonfly, in my case), fails:
$ cross -v +nightly clippy --target x86_64-unknown-dragonfly -- -D warnings
+ cargo +nightly metadata --format-version 1 --filter-platform x86_64-unknown-dragonfly
+ rustc --print sysroot
+ /usr/bin/podman
+ /usr/bin/podman version -f '{{ .Server.Os }},,,{{ .Server.Arch }}'
+ /usr/bin/podman info -f '{{ .Version.OsArch }}'
+ rustup toolchain list
+ rustup target list --toolchain nightly-x86_64-unknown-linux-gnu
[cross] warning: using newer rustc `1.67.0-nightly (b833ad56f 2022-11-18)` for the target. Current active rustc on the host is `rustc 1.65.0 (897e37553 2022-11-02)`.
 > Update with `rustup update`
+ rustup component list --toolchain nightly-x86_64-unknown-linux-gnu
+ rustup component list --toolchain nightly-x86_64-unknown-linux-gnu
+ /usr/bin/podman run --userns host -e 'PKG_CONFIG_ALLOW_CROSS=1' -e 'XARGO_HOME=/home/gui/.xargo' -e 'CARGO_HOME=/home/gui/.local/share/cargo' -e 'CROSS_RUST_SYSROOT=/home/gui/.local/share/rustup/toolchains/nightly-x86_64-unknown-linux-gnu' -e 'CARGO_TARGET_DIR=/target' -e 'CROSS_RUNNER=' -e TERM -e 'USER=gui' -e 'CROSS_RUSTC_MAJOR_VERSION=1' -e 'CROSS_RUSTC_MINOR_VERSION=67' -e 'CROSS_RUSTC_PATCH_VERSION=0' --name cross-nightly-x86_64-unknown-linux-gnu-94e8e-b833ad56f-x86_64-unknown-dragonfly-ca725-1668874801982 --rm -v /home/gui/.xargo:/home/gui/.xargo:z -v /home/gui/.local/share/cargo:/home/gui/.local/share/cargo:z -v /home/gui/.local/share/cargo/bin -v /home/gui/dev/topgrade:/home/gui/dev/topgrade:z -v /home/gui/.local/share/rustup/toolchains/nightly-x86_64-unknown-linux-gnu:/home/gui/.local/share/rustup/toolchains/nightly-x86_64-unknown-linux-gnu:z,ro -v /home/gui/dev/topgrade/target:/target:z -w /home/gui/dev/topgrade -t ghcr.io/cross-rs/x86_64-unknown-dragonfly:main sh -c 'PATH="$PATH":"/home/gui/.local/share/rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin" cargo -v clippy --target x86_64-unknown-dragonfly -- -D warnings -Zbuild-std'
error: failed to run `rustc` to learn about target-specific information

Caused by:
  process didn't exit successfully: `/home/gui/.local/share/rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin/clippy-driver rustc - --crate-name ___ --print=file-names --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=cfg` (exit status: 1)
  --- stderr
  error: unknown unstable option: `build-std`

+ rustup component list --toolchain nightly-x86_64-unknown-linux-gnu
[cross] warning: rust-std is not available for x86_64-unknown-dragonfly
[cross] note: you may need to build components for the target via `-Z build-std=<components>` or in your cross configuration specify `target.x86_64-unknown-dragonfly.build-std`
              the available components are core, std, alloc, and proc_macro

I believe the issue is caused due to cross passing -Zbuild-std to clippy instead of cargo.
My Cross.toml:
[target.x86_64-unknown-dragonfly]
build-std = true

I've also tried without using Cross.toml, i.e. by setting RUSTFLAGS=-Zbuild-std manually, but I think I confused cross even further?
$ export RUSTFLAGS='-Zbuild-std'
$ cross -v +nightly clippy --target x86_64-unknown-dragonfly -- -D warnings
+ cargo +nightly metadata --format-version 1 --filter-platform x86_64-unknown-dragonfly
[cross] warning: unable to get metadata for package
        error: failed to run `rustc` to learn about target-specific information                Caused by:          process didn't exit successfully: `rustc - --crate-name ___ --print=file-names -Zbuild-std --target x86_64-unknown-dragonfly --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=cfg` (exit status: 1)          --- stderr          error: unknown unstable option: `build-std`
[cross] note: Falling back to `cargo` on the host.
+ cargo -v +nightly clippy --target x86_64-unknown-dragonfly -- -D warnings
error: no such subcommand: `+nightly`

	Cargo does not handle `+toolchain` directives.
	Did you mean to invoke `cargo` through `rustup` instead?

What target(s) are you cross-compiling for?
other (specify in description)
Which operating system is the host (e.g computer cross is on) running?

[ ] macOS
[ ] Windows
[X] Linux / BSD
[ ] other OS (specify in description)

What architecture is the host?

[X] x86_64 / AMD64
[ ] arm32
[ ] arm64 (including Mac M1)

What container engine is cross using?

[ ] docker
[X] podman
[ ] other container engine (specify in description)

cross version
cross 0.2.4 (6635e20 2022-11-16)
Example
git clone https://github.com/guihkx/topgrade.git -b ci-dragonfly
cd topgrade
cross -v +nightly clippy --target x86_64-unknown-dragonfly -- -D warnings

Additional information / notes
No response

Related to #1049. We can probably have an additional_args, so we add it to args but not to additional_args and then append -Zbuild-std to args and add additional_args later.

This should be closed in #1142, if you'd like to test to ensure it works that would be wonderful. The above example now works for me:
$ cross -v +nightly clippy --target x86_64-unknown-dragonfly -- -D warnings
+ cargo +nightly metadata --format-version 1 --filter-platform x86_64-unknown-dragonfly
+ rustc --print sysroot
+ /usr/bin/docker
+ /usr/bin/docker version -f '{{ .Server.Os }},,,{{ .Server.Arch }}'
+ rustup toolchain list
+ rustup target list --toolchain nightly-x86_64-unknown-linux-gnu
[cross] warning: using newer rustc `1.67.0-nightly (6284998a2 2022-11-12)` for the target. Current active rustc on the host is `rustc 1.62.0 (a8314ef7d 2022-06-27)`.
 > Update with `rustup update`
+ rustup component list --toolchain nightly-x86_64-unknown-linux-gnu
+ rustup component list --toolchain nightly-x86_64-unknown-linux-gnu
+ /usr/bin/docker run --userns host -e 'PKG_CONFIG_ALLOW_CROSS=1' -e 'XARGO_HOME=/home/ahuszagh/.xargo' -e 'CARGO_HOME=/home/ahuszagh/.cargo' -e 'CROSS_RUST_SYSROOT=/home/ahuszagh/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu' -e 'CARGO_TARGET_DIR=/target' -e 'CROSS_RUNNER=' -e TERM -e 'USER=ahuszagh' -e 'CROSS_RUSTC_MAJOR_VERSION=1' -e 'CROSS_RUSTC_MINOR_VERSION=67' -e 'CROSS_RUSTC_PATCH_VERSION=0' --name cross-nightly-x86_64-unknown-linux-gnu-de1a6-6284998a2-x86_64-unknown-dragonfly-2a8a9-1668878982010 --rm --user 1000:1000 -v /home/ahuszagh/.xargo:/home/ahuszagh/.xargo:z -v /home/ahuszagh/.cargo:/home/ahuszagh/.cargo:z -v /home/ahuszagh/.cargo/bin -v /home/ahuszagh/Desktop/cross/hello:/home/ahuszagh/Desktop/cross/hello:z -v /home/ahuszagh/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu:/home/ahuszagh/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu:z,ro -v /home/ahuszagh/Desktop/cross/hello/target:/target:z -w /home/ahuszagh/Desktop/cross/hello -t ghcr.io/cross-rs/x86_64-unknown-dragonfly:main sh -c 'PATH="$PATH":"/home/ahuszagh/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin" cargo -v clippy --target x86_64-unknown-dragonfly -Zbuild-std -- -D warnings'
    Finished dev [unoptimized + debuginfo] target(s) in 0.16

So, the invoked command inside the container is now cargo -v clippy --target x86_64-unknown-dragonfly -Zbuild-std -- -D warnings.

That was fast! And yeah, it worked perfectly for me as well. Thank you!
One question, is my second example incorrect? Because
$ RUSTFLAGS='-Zbuild-std' cargo -v +nightly clippy --target x86_64-unknown-dragonfly -- -D warnings
+ cargo +nightly metadata --format-version 1 --filter-platform x86_64-unknown-dragonfly
[cross] warning: unable to get metadata for package
        error: failed to run `rustc` to learn about target-specific information                Caused by:          process didn't exit successfully: `rustc - --crate-name ___ --print=file-names -Zbuild-std --target x86_64-unknown-dragonfly --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=cfg` (exit status: 1)          --- stderr          error: unknown unstable option: `build-std`
[cross] note: Falling back to `cargo` on the host.
+ cargo -v +nightly clippy --target x86_64-unknown-dragonfly -- -D warnings
error: no such subcommand: `+nightly`

	Cargo does not handle `+toolchain` directives.
	Did you mean to invoke `cargo` through `rustup` instead?

Still fails...🤔

Yes it is invalid, I believe. -Z build-std is a cargo option, not a rustc one, and therefore it would be an unknown option. This also makes sense conceptually, since rustc is the raw compiler, not the package manager, so it has no real concept of "building" std: you can build it externally and provide a path to link to it, but that's outside of the scope of rustc.
https://doc.rust-lang.org/cargo/reference/unstable.html

Makes sense! Thanks again.


Enabled periodic flush so that the events can be expired

Hi,
I believe this needs to be specifically enabled so that logstash will actually call flush. Currently the expiration of events does not seem to work.
I noted the issue here: https://github.com/logstash-plugins/logstash-filter-elapsed/issues/22
Let me know if this is Ok/ needs changes.
Thanks,
Artur Kronenberg

Hi @pandaadb, we have found your signature in our records, but it seems like you have signed with a different e-mail than the one used in yout Git commit. Can you please add both of these e-mails into your Github profile (they can be hidden), so we can match your e-mails to your Github profile?

I have added my email from the commit and confirmed it. Also signed the agreement.

Looking into this a bit more, it is not really necessary to merge the PR. However, if not, the documentation should be update to reflect that periodic flushing needs to be enabled for the timeout to work.  This is currently not mentioned on the official docs:
https://www.elastic.co/guide/en/logstash/current/plugins-filters-elapsed.html#plugins-filters-elapsed-periodic_flush

Closing as a duplicate of #36
Thanks for you contribution @pandaadb


AOT / trimmed support for .net 7

Describe the feature
Would like to use the SDK in AOT compiled mode.
This is already supported for java: https://aws.amazon.com/blogs/developer/graalvm-native-image-support-in-the-aws-sdk-for-java-2-x/
AOT works on lambda but without AWS SDK it's not very useful: https://github.com/awslabs/dotnet-nativeaot-labs
However in c# 7, I get trim warnings, and a crash on startup, using the S3 SDK with a console CLI program on linux.
/home/k/.nuget/packages/awssdk.core/<IP_ADDRESS>/lib/netcoreapp3.1/AWSSDK.Core.dll : warning IL2104: Assembly 'AWSSDK.Core' produced trim warnings. For more information see https://aka.ms/dotnet-illink/libraries [/home/k/github/aws-dotnet7/src/aot/aot.csproj]
/home/k/.nuget/packages/awssdk.core/<IP_ADDRESS>/lib/netcoreapp3.1/AWSSDK.Core.dll : warning IL3053: Assembly 'AWSSDK.Core' produced AOT analysis warnings. [/home/k/github/aws-dotnet7/src/aot/aot.csproj]
/home/k/.nuget/packages/runtime.linux-x64.microsoft.dotnet.ilcompiler/7.0.0/framework/System.Net.Http.dll : warning IL3053: Assembly 'System.Net.Http' produced AOT analysis warnings. [/home/k/github/aws-dotnet7/src/aot/aot.csproj]
/home/k/.nuget/packages/runtime.linux-x64.microsoft.dotnet.ilcompiler/7.0.0/framework/System.Private.Xml.dll : warning IL3053: Assembly 'System.Private.Xml' produced AOT analysis warnings. [/home/k/github/aws-dotnet7/src/aot/aot.csproj]
Unhandled Exception: System.TypeInitializationException: A type initializer threw an exception. To determine which type, inspect the InnerException's StackTrace property.
---> System.TypeInitializationException: A type initializer threw an exception. To determine which type, inspect the InnerException's StackTrace property.
---> System.MissingMethodException: No parameterless constructor defined for type 'Amazon.Util.Internal.PlatformServices.NetworkReachability'.
at System.ActivatorImplementation.CreateInstance(Type, Boolean) + 0x120
at Amazon.Util.Internal.PlatformServices.ServiceFactory..ctor() + 0x144
Use Case
Frustrated when CLI programs don't start fast.
Proposed Solution
No response
Other Information
No response
Acknowledgements

[ ] I may be able to implement this feature request
[ ] This feature might incur a breaking change

AWS .NET SDK and/or Package version used
Include="AWSSDK.S3" Version="<IP_ADDRESS>
Targeted .NET Platform
.net 7
Operating System and version
ubuntu

@kjpgit Thanks for submitting the feature request. Please refer the blog post Building serverless .NET applications on AWS Lambda using .NET 7 for the Native AOT support. As mentioned, currently, the AWSSDK.Core library used by all the .NET AWS SDKs must also be excluded from trimming. Please review if it provides explanation for the above issue and confirm if this ticket could be closed.
Thanks,
Ashish

Why on earth are you asking me to close a feature request before it has been implemented???

I'm not using lambda, just creating a CLI program.  But I read that blog post, and the exclude trimming steps do not work for me.
my aot.csproj:
Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <PublishAot>true</PublishAot>
    <StripSymbols>true</StripSymbols>

    <OutputType>Exe</OutputType>
    <TargetFramework>net7.0</TargetFramework>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="AWSSDK.Core" Version="<IP_ADDRESS>" />
    <PackageReference Include="AWSSDK.S3" Version="<IP_ADDRESS>" />
  </ItemGroup>

  <ItemGroup>
      <RdXmlFile Include="rd.xml" />
  </ItemGroup>

</Project>

my rd.xml:
<Directives xmlns="http://schemas.microsoft.com/netfx/2013/01/metadata">
    <Application>
        <Assembly Name="AWSSDK.Core" Dynamic="Required All"></Assembly>
        <Assembly Name="AWSSDK.S3" Dynamic="Required All"></Assembly>
        <Assembly Name="aot" Dynamic="Required All"></Assembly>
    </Application>
</Directives>

$ dotnet --version
7.0.100

$ NO_COLOR=1 dotnet publish -r linux-x64 -c Release
MSBuild version 17.4.0+18d5aef85 for .NET
  Determining projects to restore...
  All projects are up-to-date for restore.
  aot -> /home/karl/incoming/aws-dotnet7/src/aot/bin/Release/net7.0/linux-x64/aot.dll
  Generating native code
/home/karl/.nuget/packages/awssdk.core/<IP_ADDRESS>/lib/netcoreapp3.1/AWSSDK.Core.dll : warning IL2104: Assembly 'AWSSDK.Core' produced trim warnings. For more information see https://aka.ms/dotnet-illink/libraries [/home/karl/incoming/aws-dotnet7/src/aot/aot.csproj]
/home/karl/.nuget/packages/awssdk.core/<IP_ADDRESS>/lib/netcoreapp3.1/AWSSDK.Core.dll : warning IL3053: Assembly 'AWSSDK.Core' produced AOT analysis warnings. [/home/karl/incoming/aws-dotnet7/src/aot/aot.csproj]
/_/src/libraries/System.Security.Cryptography/src/System/Security/Cryptography/CryptoConfigForwarder.cs(21): Trim analysis warning IL2026: System.Security.Cryptography.CryptoConfigForwarder..cctor(): Using member 'System.Security.Cryptography.CryptoConfigForwarder.BindCreateFromName()' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. The default algorithm implementations might be removed, use strong type references like 'RSA.Create()' instead. [/home/karl/incoming/aws-dotnet7/src/aot/aot.csproj]
/home/karl/.nuget/packages/runtime.linux-x64.microsoft.dotnet.ilcompiler/7.0.0/framework/System.Private.Xml.dll : warning IL3053: Assembly 'System.Private.Xml' produced AOT analysis warnings. [/home/karl/incoming/aws-dotnet7/src/aot/aot.csproj

I see, even though there are still scary warnings from dotnet publish, it does NOT crash anymore when I run the exe.  It successfully does a S3 file listing for me.   So that's exciting, I guess.
You can close this ticket.  Hopefully the SDK will get better docs on this, and support trimming in the future.


Delinting future awaits round 2

#10754

@xster ping on this one too :-)

Both ready for a look (looks like travis just timed out)


What file to import

You can import a json file with the data format defined by rasa_nlu.
Please import the examples in rasa_nlu to have a try.

But sames the training out put json will miss the entity values and change it to a null value.
Don't know if it's effect by rasa_nlu version.

@yuxuan2015 you can import an existing rasa_nlu training dataset and give it an Agent name.


Nginx has no default user

Starting threebot server(and nginx) uses the default conf inside a container. The nginx process is owned by root and the outside cant reach the process' files.


the grid-template example could be made sortable via the keyboard easily

Sorry for not doing this the official way ... not ready to get familiar with the whole process , install proj etc. , yet the grid-component could be done sortable via the keyboard by adding the  tabindex="1" v-on:keyup.enter="sortBy(key)" :


Autocomplete demo component with TextField label

https://codesandbox.io/s/j74yvm2zkv
While label provided to TextField Component works fine (floats if there is a value and comes down to input field if input is empty), but with InputProps provided like in the Autocomplete demo, label doesn't floats if there is value. It floats only while input is focused.

[x] This is a v1.x issue.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior
Label should float if there is value in input field. Attached codesandbox link.
Current Behavior
Label doesn't float and no prop floatingLabelFixed found
Steps to Reproduce
Link:

https://codesandbox.io/s/j74yvm2zkv
https://material-ui.com/demos/autocomplete/

Context
If the label doesn't float, then we can not see the label if the chips are there in the input field.
Your Environment

Tech
Version

Material-UI
v1.4.3

React
16.4.2

browser
chrome

etc.

on your codepen, i saw that we can input a new value by pressing enter after writing something. this behavior is not available on the demo. Does the component support this already or is it a custom change you made?

That's a custom change, I am using creatable from react-select.

@abhijeetahuja this is the solution that I found for the problem.

InputLabelProps={{
shrink: true,
}}
And it seems is the same choose by @oliviertassinari


Attain parity with ES6 Promises

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise
Edit: Here are the items to add.

[ ] Promise.all https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/all
[ ] Promise.race https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/race
[x] Promise.reject https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/reject

Here is an article discussing a concise implementation of Promise.all and Promise.race. http://eddmann.com/posts/implementing-promise-all-and-promise-race-in-javascript/


Create builtin Elixir compiler to be able to include it in projects

What have to be done? What is the best way to implement that? I would like to do this 🙂

#25 Has the multiple file compiler.
All that needs to be done is a mix task, which does elmchemy aggregate parsed_directory
elmchemy is a binary that relies on elmchemy.js which is a node file.
So probably the easiest way would be to publish an npm package and hex package. Create a mix compiler then:
npm install -g elmchemy
mix archive.install git elmchemy/repo

and then add elmchemy to compiler

This repo has a good example how to write a Mix compiler:
https://github.com/wende/scalixir

Closed in #43


OZ L02; Spearbit 87; improved calldata checks

I think actions and params could overlap even with the improved checks, e.g. if the head of actions just points at one of the elements of params. I'm not sure that's problematic per se (based on usage in the code, which is read-only AFAICT), but it is weird.

closing for #346 due to @kmbarry1 's comment above


Need submodule (litecoin-foundation/loafwallet-core) updates from breadwallet/breadwallet-core to

1000 Crashes are due to the submodule (loafwallet-core) not being updated.  breadwallet-core recent updates are declared 'API-Breaking' and are causing the crashes we see in LoafWallet

Hey @losh11 This is what we are slacking about.

Fixed in 4ddfe34.


Box seal fixes

Thanks for the library.
I found a few problems when experimenting with Salty that are fixed by this PR:

Salty.Box.Curve25519xsalsa20poly1305.seal/2 was calling the wrong NIF primitive
the NIF function for box_curve25519xsalsa20poly1305_seal_open was returning the original ciphertext, not the decrypted plaintext, and
Compiling salty was deleting other dependencies.

3 is a bit weird: don't know if its an elixir/mix bug but having the compile alias call ["compile", &make/1] in that order was deleting other compiled dependencies in my project, i.e. the directories under _build/dev/lib were being deleted. This is on Elixir 1.5.2, OTP 20.
Switching the order of the compile commands fixed it (luckily).

Thanks for the catch!
I am unsure about the origin of point 3, will have to look into that.


Handle unregistered resources

Description
In #961 we added a check for most of the resources. When resource was unknown we silently skip it. This PR introduces a panic when we are unable to get resource metadata.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on stackrox/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
CI

Check generated files fails because in go < 1.18 conditions in templates are evaluated eagerly and then compared this is fixed by https://github.com/golang/go/issues/31103 so we need a workaround for now


Typechecker doesn't handle target types with a Parameterized type in a union

Description:
This occurs when we try to use the the checkIsType[1] method with the following parameters.
sourcetype : http:ClientError|http:Response
targetType : http:ClientError|(a parameterized type with member type http:Response)
When debugged, I could notice that this fails when trying to use the isUnionTypeMatch method.
The existing logic in isUnionTypeMatch method[2] is as follows.
    private static boolean isUnionTypeMatch(BUnionType sourceType, Type targetType, List<TypePair> unresolvedTypes) {
        for (Type type : sourceType.getMemberTypes()) {
            if (!checkIsType(type, targetType, unresolvedTypes)) {
                return false;
            }
        }
        return true;
    }

Shouldn't we change it to traverse through each memberType for targetType as well? Similar to the following?
    private static boolean isUnionTypeMatch(BUnionType sourceType, Type targetType, List<TypePair> unresolvedTypes) {
        if (targetType instanceof BUnionType) {
            targetType = getUpdatedUnionType((BUnionType) targetType);
        }
        if (sourceType instanceof BUnionType) {
            sourceType = getUpdatedUnionType(sourceType);
        }
        for (Type type : sourceType.getMemberTypes()) {
            if (!checkIsType(type, targetType, unresolvedTypes)) {
                return false;
            }
        }
        return true;
    }

    private static BUnionType getUpdatedUnionType(BUnionType targetType) {
        BUnionType updatedTargetType = new BUnionType();
        for (Type targetTypeMember : targetType.getMemberTypes()) {
            if (targetType.getTag() == TypeTags.PARAMETERIZED_TYPE_TAG) {
                Type bObjectType = ((ParameterizedType) targetTypeMember).getParamValueType();
                updatedTargetType.addMembers(bObjectType);
            } else {
                updatedTargetType.addMembers(targetTypeMember);
            }
        }
        return updatedTargetType;
    }

WDYT?
Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Since this isn't specific to unions, let me use a simple example with a single type. Note that I've used compile-time analysis for the example, but it applies similarly at runtime.
class Source {
   function func(typedesc<Foo> td) returns Foo => new Baz();
}

class Target {
   function func(typedesc<Foo> td) returns td = external;
}

class Foo {
   int i = 1;
}

// Subtype of `Foo` but not of `Baz`.
class Bar {
   int i = 1;
   float f = 1;
}

// Subtype of `Foo` but not of `Bar`.
class Baz {
   int i = 1;
   string f = "1";
}

Here if we type-checked as proposed, the following will be allowed.
Target t = new Source();

But now consider a method call for the particular method. This is valid since Bar is a subtype of Foo.
Bar bar = t.func(Bar);

Even though we expect a Bar value here, the actual method at this point (func of Source) returna a Baz value which is not a subtype of Bar leading to incorrect state at runtime. So we do not consider Source.func to be a subtype of Target.func.
Related spec discussion: https://github.com/ballerina-platform/ballerina-spec/issues/633

Ok makes sense @MaryamZi. Thanks for the explanation.


Discovering usernames via authentication timing

Hi Brock.
Just found this while doing some testing on our authentication app.  When you attempt to sign in with a valid username the authentication process can take > 500ms regardless of whether the password is correct or not due to the entered password being hashed (depending on hashing iterations).
However if you attempt to sign in with an invalid username, the sign in process returns 'immediately'.
So using this approach you can in theory discover what valid usernames are (or emails, if emails are the usernames) based on how long the sign in process takes.
Do you have any suggestions on how to mitigate this information leakage?
I was thinking of if no user was found with the username entered, to then hash a random string using the current password hashing method.
Thoughts?

I've noticed the same issue. The longer the normal login takes, the more pronounced the difference is. I had the same thought as you but I would just hash the entered password if the user doesn't exist.

Well, depends -- do you allow users to sef-register? If so, then they can discover usernames that way. If not, then you can always put a constant time middleware to ensure all login requests always take the same amount of time.

@brockallen - No, users do not self-register.
Do you know of any existing constant-time middleware packages?  I'd rather use something that is tried and tested than roll my own.

It'd be something like:
app.Use(async (ctx, next)=>{
    var now = DateTimw.Now;
    await next();
    var diff = DateTime.Now.Subtract(now);
    if (diff < TimeSpan.FromSeconds(5)){
       await Task.Delay(TimeSpan.FromSeconds(5).Subtract(diff));
    }
});

@brockallen  - Thanks for that. I was thinking along those lines as well, however would need to only do it for certain endpoints (e.g. sign in) and certain verbs.


Update commandhandler.cpp

changed except to accept
I saw "expect" on the documentation online, however I understand its similar but the correct wording I believe should be "Accept"
Documentation change checklist

[x] My documentation changes follow the docs style guide and any code examples follow the coding style guide.
[x] I tested that my change works before raising the PR (via running doxygen, and testing examples).
[x] I have not moved any existing pages or changed any existing URLs without strong justification as to why.
[x] I have not generated content using AI or a desktop utility such as grammarly.

Even if this wasn't closed, this PR wouldn't be accepted as both terms are perfectly okay.


DNM: test trigger on master

What problem does this PR solve?

Issue Number: close #xxx
What is changed and how it works?
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
Please refer to [Release Notes Language Style Guide](https://pingcap.github.io/tidb-dev-guide/contribute-to-tidb/release-notes-style-guide.html) to write a quality release note.

If you don't think this PR needs a release note then fill it with `None`.

/retest

/retest

/test ?

/test verify

/test ?

/test cdc-integration-kafka-test cdc-integration-pulsar-test


Usage of leading underscores

Normal Python usage, of course, uses leading underscores to indicate that a name is intended to be private. My understanding is that this library deviates from this convention by instead using leading underscores to limit what is included in the Sphinx-generated documentation. Names with leading underscores defined at module level are often used in other modules, and names with leading underscores defined at class level are often used outside the class, and even from other modules. In effect, such names are treated as private to the package. Is this understanding correct?
I would suggest looking into controlling visibility in the Sphinx-generated documentation separately and gradually migrating to normal Python usage.

My understanding is that this library deviates from this convention by instead using leading underscores to limit what is included in the Sphinx-generated documentation

Nope, we also use them to indicate the names are not intended as public.
Any specific examples you have in mind?

We talk about / think about private attributes / members at the level of library users, not necessarily within the library itself:

We consider private attributes / data members as being freely available to unit tests (some of them really have no other purpose, even).

Because they are about the user-facing API exposed by the library, we normally avoid using them from system tests, or exposing them in example snippets.

On a case-by-case basis, we have allowed use from within another module in the same package, in effect treating the using-module as a "friend" in the C++ / Java sense.

At least one of our sub-packages (gcloud.streaming) should really be private in terms of library users, but carries a public-looking name due to a quirk/bug in nose (it ignores packages whose names begin with _).  Nevertheless, it is heavily used by gcloud.storage.blob.

@tseaver Another big category is classes and module-level functions in "helper" modules.
This notion of things being private "at the level of library users" isn't really normal Python usage.
It's not just about generated docs?

Most of these helper modules are intentionally non-public, if that's what you mean.

@dhermes No, I mean that names defined at module level in helper modules are prefixed with leading underscores whether or not they are actually intended to be private to that helper module.

Yeah names in _helper modules could certainly all be public, since the module itself is not. That may have just been overly defensive programming. But the _helper modules themselves will never be picked up by Sphinx, so that isn't the cause of those names.

I don't see a bug here:  the helpers are not intended to be public, which means that renaming them makes them seem as though they might be public (e.g., when found from a module which imports them by name).

I don't care very much, though @jonparrott has said compelling things to me along these lines. As for public names from a private module, aren't imported members not "considered" part of the public API.


Query IncludeOptimized + QueryCache

Both features are currently not compatible.
The QueryCache should check first if an internal method (from our library) to general query exists for the specified query instead of trying to generate a query using the GetObjectQuery method.
This internal method should work also for the standalone version.

The issue has been fixed.
The fix should be available for Monday

The issue has been fixed in v1.4.4


Add way to get Location of Godot Editor

Is your feature request related to a problem? Please describe.
Currently, you have to navigate manually to where the version of Godot is installed, in order to get the path to it.
Describe the solution you'd like
Add a way to Godot Version Line, to be able to get the location of the installed version to be used in other things, such as Visual Studio Code.

Unless there is an environment variable for the path of godot, it might be difficult and maybe not time efficient to implement this.
I will look at my environment variables and we will see where to go from there.

This is not what I was talking about.  This is more to align with the same feature that is setup with Projects, where you can right click on the Project Line Entry, and select View Files or View Data Folder.  Maybe 3 Menu Items, for View Data Folder, View Installed Location, and Copy Installed Location, so that the location to the Executable can be placed on the Clipboard.


Improve error/debug messaging when Flyway Can't Calculate Checksum

Which version and edition of Flyway are you using? 6.4.0
Which client are you using? Command-line
Which database are you using SQL Server 2016
Which operating system are you using? Windows
What did you do?
Had this exact problem yesterday, ERROR: Unable to calculate checksum of

I'm unable to reproduce this just by copying the '©' character into a migration script. Can you share the script file itself (or a file with the bad comment in)?

Attached.
<EMAIL_ADDRESS>From: Mikiel Agutu<EMAIL_ADDRESS>Sent: Monday, May 4, 2020 9:55 AM
To: flyway/flyway<EMAIL_ADDRESS>Cc: Scero, Rick<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [flyway/flyway] Improve error/debug messaging when Flyway Can't Calculate Checksum (#2799)
I'm unable to reproduce this just by copying the '©' character into a migration script. Can you share the script file itself (or a file with the bad comment in)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/flyway/flyway/issues/2799#issuecomment-623478753, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGLE2LFNJ4JAQCMS7KVUDE3RP3CMZANCNFSM4MXEXEJA.

@rscero Unfortunately email attachments don't work! You'll have to share the file directly on GitHub on this issue page.

@rscero Any news?

Closing for lack of response.


Update to SLF4J to version 2.0.x

Version 2.0.7 of SLF4J was released: https://www.slf4j.org/news.html
The latest released version of HikariCP, version 5.0.1, depends, for Java 11 and newer, on slf4j-api version 2.0.0-alpha1:
https://github.com/brettwooldridge/HikariCP/blob/HikariCP-5.0.1/pom.xml#L555-L566
Since mixing 2.0.x and 1.7.x slf4j-api versions is not supported (cf. https://www.slf4j.org/faq.html#changesInVersion200), it would be nice if HikariCP could update to a current, stable version of SLF4J.

slf4j 2.x provides explicitly modularized jar files, and they also claim that v2 should be a drop in replacement for 1.x.
Is the reason that this ticket was closed to avoid causing chaos downstream?
Asking because I'm working on converting automatic jars to explicitly modularized ones, and I'm considering just excluding hikari's dependency on slf4j-api:1.x in favor of 2.x, and I'm curious to know if there is some technical reason why hikari does not depend on the newer versions.

I am seeing the same issue at https://github.com/ClickHouse/clickhouse-java/issues/2023 . com.clickhouse:clickhouse-jdbc:0.7.1-patch1 is using a newer version of org.slf4j:slf4j-api:2.0.7 which is causing a dependency conflict.


Upgrade sixel-rs dependency

This PR fixes the following security vulnerabilities:

RUSTSEC-2022-0013
RUSTSEC-2022-0006

Fixes #39

Sorry for the delay and thank you! I've been meaning to dive into how -sys crates work and do a fresh sixel one. They're all terribly outdated


feat: add ESM support

Not to detract from #45 but it is a little crowded with changes and it might be easier to review this way. This PR adds ESM interop for modules while keeping it backwards compatible as well as updates the typescript version.

Thanks for taking the time to put this together, @ericlewis !
We've rewritten the library, and the upcoming v4 has support for ESM. Please give it a try and let us know what you think!


Unable to compile app when adding @amplitude/analytics-react-native

Expected Behavior

Should compile
Current Behavior

Doesn't:
FAILURE: Build completed with 2 failures.

1: Task failed with an exception.
-----------
* Where:
Build file '/Users/mihai/dev/paced-breathing-3.0/react-native/android/app/build.gradle' line: 2

* What went wrong:
A problem occurred evaluating project ':app'.
> Failed to apply plugin 'com.facebook.react'.
   > The value for property 'languageVersion' is final and cannot be changed any further.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
==============================================================================

2: Task failed with an exception.
-----------
* What went wrong:
A problem occurred configuring project ':app'.
> com.android.builder.errors.EvalIssueException: compileSdkVersion is not specified. Please add it to build.gradle

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
==============================================================================

BUILD FAILED in 6s
error Failed to install the app. Command failed with exit code 1: ./gradlew app:installPlayDebug -PreactNativeDevServerPort=8081 FAILURE: Build completed with 2 failures. 1: Task failed with an exception.
-----------
* Where:
Build file '/Users/mihai/dev/paced-breathing-3.0/react-native/android/app/build.gradle' line: 2 * What went wrong:
A problem occurred evaluating project ':app'.
> Failed to apply plugin 'com.facebook.react'. > The value for property 'languageVersion' is final and cannot be changed any further. * Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
============================================================================== 2: Task failed with an exception.
-----------
* What went wrong:
A problem occurred configuring project ':app'.
> com.android.builder.errors.EvalIssueException: compileSdkVersion is not specified. Please add it to build.gradle * Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
============================================================================== BUILD FAILED in 6s.
info Run CLI with --verbose flag for more details.

This seems like nonsense errors:

I didn't change anything related to languageVersion or facebook/react
I do specify compileSdkVersion

Possible Solution

Steps to Reproduce

Update to:

RN 0.73.6
Gradle: gradle-8.7
Android gradle plug-in: 8.3.1
Target Android SDK 34
Java 17

run npx react-native run-android --mode=playDebug, everything compiles and runs works perfectly
npm install @amplitude/analytics-react-native@latest
run npx react-native run-android --mode=playDebug again, annnnd compile errors

I wasted a whole day dealing with this. As of now, I just ripped out Amplitude from our app entirely in favor of Firebase/GA which works more easily / hasn't caused us any problems.  If this gets fixed, could add Amp back, but atm it's just too much of a pain / not worth it.

This seems to be an issue with the plugin not being tested with React Native 0.73. Unfortunately the solution is to remove @amplitude/analytics-react-native.

You guys can’t just fix this? You’re just saying I have to find another analytics provider / can’t use Amplitude?

I can confirm that it's not working with RN 73, as mentioned in original post as soon as you add the plugin, it gives you the following error
`1: Task failed with an exception.

Where:
Build file '/Users/XXXX/android/app/build.gradle' line: 2

What went wrong:
A problem occurred evaluating project ':app'.

Failed to apply plugin 'com.facebook.react'.
The value for property 'languageVersion' is final and cannot be changed any further.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
Get more help at https://help.gradle.org.
==============================================================================

2: Task failed with an exception.

What went wrong:
A problem occurred configuring project ':app'.

com.android.builder.errors.EvalIssueException: compileSdkVersion is not specified. Please add it to build.gradle

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
Get more help at https://help.gradle.org.
==============================================================================`

@nmongiya @mihaibulic2 - I tried testing the amplitude library against both 0.73.6 and 0.74.1 and I am not running into this issue in there.
Here's a branch which has test apps with version 0.74.1 (Amplitude-TypeScript/examples/react-native/app_v2/) and 0.73.6 (Amplitude-TypeScript/examples/react-native/app_v2/)
Gradle version
izaaz.yunus@Izaazs-MacBook-Pro android % ./gradlew -v

------------------------------------------------------------
Gradle 8.7
------------------------------------------------------------

Build time:   2024-03-22 15:52:46 UTC
Revision:     650af14d7653aa949fce5e886e685efc9cf97c10

Kotlin:       1.9.22
Groovy:       3.0.17
Ant:          Apache Ant(TM) version 1.10.13 compiled on January 4 2023
JVM:          17.0.5 (Oracle Corporation 17.0.5+9-LTS-191)
OS:           Mac OS X 14.2.1 aarch64

Am I missing something in my test?
Also, could you please share your build.gradle file? Maybe y'all have something configured there which I haven't?

Closing this issue since I see it working with the latest version of RN. But if anyone has any more information to share, I'm happy to spend more time understand why it may not be working.

I'm having the same error when @amplitude/analytics-react-native version 1.4.9 is autolinked in my project that has React Native 0.72.10.

After upgrading to Gradle 8.7 I started getting 3 different errors rather than 2. It is still an app with React Native 0.72.10.
FAILURE: Build completed with 3 failures.

1: Task failed with an exception.
-----------
* Where:
Build file '/[my-app]/android/app/build.gradle' line: 3

* What went wrong:
A problem occurred evaluating project ':app'.
> Failed to apply plugin 'com.facebook.react'.
   > The value for property 'languageVersion' is final and cannot be changed any further.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
==============================================================================

2: Task failed with an exception.
-----------
* What went wrong:
A problem occurred configuring project ':app'.
> compileSdkVersion is not specified. Please add it to build.gradle

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
==============================================================================

3: Task failed with an exception.
-----------
* What went wrong:
Failed to query the value of property 'buildFlowServiceProperty'.
> Could not isolate value org.jetbrains.kotlin.gradle.plugin.statistics.BuildFlowService$Parameters_Decorated@1a5a7375 of type BuildFlowService.Parameters
   > A problem occurred configuring project ':app'.
      > compileSdkVersion is not specified. Please add it to build.gradle

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
==============================================================================


We should remove the --optimize feature of 'dspace stats-util'

Describe the bug
The so-called "optimization" of Solr cores is contrary to current advice from Solr's maintainers.  We shouldn't make it easy to do the wrong thing.  This option should be removed.

This seems reasonable to me. It's low priority, but adding to 7.1.  If we don't get to it then, we'll move to a later release.

Oh, I'm surprised to see that the optimize flag still exists here! It was removed from our index-discovery command years ago. There was a lot of discussion on the dspace-tech mailing list and Jira (now defunct) at the time. It has been commented out in my repository's scheduled tasks since 2016.
Some other references:

See comments on the DSpace 5.x wiki page for Scheduled Tasks via Cron
See upstream Solr issue from 2012 (!): https://issues.apache.org/jira/browse/SOLR-3141


Document how to configure deis and git clients

There should be a document that outlines how to configure the deis and git clients for at least the following Deis installation kinds:

When Deis is helm installed onto a k8s cluster running on a load balancer capable cloud provider
When Deis is helm installed onto a k8s cluster running on infrastructure where external load balancer creation is a no-op (e.g. bare metal or virtualbox)
When only workflow and builder are running (this will require app creation against the workflow cluster IP, then setting up a git remote directly to the builder cluster IP)

This issue follows from https://github.com/deis/router/issues/58.

I can tackle this :)

:100: @bacongobbler

Two things...
I'm a little confused by this issue.  What "configuration" is required for the deis and git clients?  Are we talking about how a user makes the determination of what URL to use with deis login?
If so, isn't the answer always deis.<platform domain>.  And how that's all set up for the various scenarios you mentioned is already documented pretty extensively in the installation docs.  Maybe all we need here is a link to that?
Second thing, I'm going to mark this as a showstopper only because I think @technosophos had expressed the other day that any doc issues that would make getting started with v2 alpha challenging should be treated as such.

Yes, the answer is to set up /etc/hosts to point to the minion nodes at deis.example.com and use deis register deis.example.com. We already have that doc now so we can just link to it... Or just say it's in the quickstart docs and close this out.


#3 getConstants implementation

@carte7000 What do you think about changing snake case to camel case while we are at it?
e.g.
blocks_per_roll_snapshot -> blocksPerRollSnapshot
blocks_per_voting_period -> blocksPerVotingPeriod
etc

I think it's a good idea to change it to camel case while we are just starting.

so I converted keys to camelCase
added casting to BigNumber
and tests
@carte7000 please reviews it again


fix issue 38

This issue seems to be there still with 1st time start... Let me investigate a little more...


API Link Error

I wanted to use the Python OFF Rest API, but the link https://openfoodfacts-api.herokuapp.com/ doesn't seem to work.
I'm getting the following error:
No such app/ There's nothing here yet

Currently you have to update your dump database to use this API application.
Another solution it to use the new API built-in on OFF website : https://en.wiki.openfoodfacts.org/API


No WIF SDK available

[Enter feedback here]
The link of WIF SDK given in this article for sample claim aware application is not working. It seems WIF 3.5 is obsolete and removed from the download link. Can we have another sample claim aware application instead?
https://www.microsoft.com/en-ca/download/details.aspx?id=4451
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f333201e-8d13-c621-6eac-f3ca7b2dcdc0
Version Independent ID: 07d1fd0e-6988-a6d5-c586-7de810bc0906
Content: Set up the lab environment for AD FS in Windows Server 2012 R2
Content Source: WindowsServerDocs/identity/ad-fs/deployment/Set-up-the-lab-environment-for-AD-FS-in-Windows-Server-2012-R2.md
Product: windows-server
Technology: ad-fs
GitHub Login: @billmath
Microsoft Alias: billmath

#assign:IngridAtMicrosoft

#label:"doc-bug"


Additional fixes for custom nullable types

This PR adds some more fixes around namespace and name construction for custom types.
Fixes: https://github.com/microsoft/typespec/issues/4635

API change check
API changes are not detected in this pull request.


Local Docker registry

Consider this idea again: let's make use of local docker registry by Racetrack (for keeping the jobs), not the external one.
At the first glance, it seems like using the external registry is pointless. Docker registry is only needed to keep the job images, which are used internally. In Kubernetes setup, image-builder pushes the image to registry, then k8s takes it back and creates a pod from it. So what happens in Racetrack, it stays in Racetrack and there's no reason to use it somewhere else. In other words, docker registry is only used to transfer image into the infrastructure. Thus, it could be local. Plus, the installation step where you need to configure your docker registry and provide the tokens might seem to be too complex and redundant for users.
However, the existence of the external registry is imposed by Kubernetes. As far as I tried, you can't instruct Kubernetes to pull the image from a registry that runs inside the cluster's pod. Kubernetes' nodes are actually responsible for pulling the images, so every node's docker daemon (in fact it's not even docker but Container Runtime or something) should be able to reach it and have it configured as a insecure registry. This kind of configuration might be too complex and not really doable in some cases (like AKS). Maybe there's another way out of here, it's worth researching.

Good point. Docker registry is the service that Racetrack relies on. Instead, it should be moved to an interface and implemented by infrastructure plugins. However, plugins can only implement logic at this point, they can't extend number of services, so it might be tough.


feat(): Allow for conversions between stream libraries

Allows interchangeability between all libraries supported
by the stream-conversions library. Injects a second parameter into
driver functions for converting streams from one library to another.

@TylorS Since, rx is optional, shouldn't it become a dependency rather than a peerDependency ?


Does this library work with staged rollouts?

Thanks for creating a very useful library. Does it work properly with staged rollouts? I don't want to show a dialog/notification if a user is not a part of the staged rollout group.

No, it doesn't. This library checks the latest update available on the web version of Google Play, so I think that the dialog/notification will be shown when the rollout is completed.


Running into this error every time I try to load a model from a previous session on the Colab

I can't seem to load my previous model. I've tried a new session, tried it from a different account, I just keep running into the same error with all my models.

same

Same, it worked literally 8 hours ago

Recent updates were pushed here: https://github.com/camenduru/stable-diffusion-webui-colab/tree/drive , you could use those colabs in the meantime.

same problem

same problem here

I would suggest clearing out all related files from your Google Drive that pertain to the Colab Web UI. Once that is done, attempt to run the Colabs again.

use the latest notebook, but you need to set the runtime to High-RAM


kapacitor.service file has bug

currently in kapacitor.service the last line:
Alias=kapacitor.service
which cause error on all update since kapacitor reference itself which is nonsense. this line should have to be deleted!
Failed to execute operation: Too many levels of symbolic links
warning: %post(kapacitor-1.3.2-1.x86_64) scriptlet failed, exit status 1
Non-fatal POSTIN scriptlet failure in rpm package kapacitor-1.3.2-1.x86_64

no one care about it

I don't see the line you want to have removed: https://github.com/influxdata/kapacitor/blob/master/scripts/kapacitor.service
Is there a different file to which you are referring?  Can you provide a link to it in our repo?

already fixed


[Question] IDE Test Output

Hey guys.
So my framework has had a bit of a boom and I've had a few questions from users that I'm not sure of the answers to.
People are asking how to see output in the test IDE.
So, in regards to testing platform, what do I need to do?
I've set StandardOutputProperty and StandardErrorProperty properties on the test nodes. Is that what would drive that?
And also do you know if the VS test output has been implemented yet or is it a WIP?

We've seen the video congrats on getting such a huge exposure 🙌🙌🙌
Looking at history Marco implemented the properties here:
https://github.com/microsoft/testfx/pull/3748
and backported to (upcoming) 1.4.1 here, https://github.com/microsoft/testfx/pull/3749
I think the plan is to release this week. The feature is flagged with TPEXP

Thanks @nohwnd !
I believe it's already in 1.4.0 because I'm already setting them here: https://github.com/thomhurst/TUnit/blob/964ec2626b05f91040b5a26b6730906bdf350f0a/TUnit.Engine/Services/SingleTestExecutor.cs#L226
I guess if nothing is showing it's just we have to wait for VS/Rider to implement the functionality.

Right, it's tagged 3.6.0 (== TP 1.4.0). https://github.com/microsoft/testfx/commit/ccf7de7eb21d773802ab940f110fd1308bf2b8fb

Thanks for the info 😄


There is no notion of "Config Env Vars" on the cli

On the UI we have split envars, so we now have RESIN_ special envars referred to as "Config Vars" but there is no equivalent on the CLI or SDK for that matter.

additionally the resin config command can be confused with this feature

Very much needed indeed!
Looking at the options, I think adding a new flag to resin envs and resin env add|rename|rm to work with config vars would be a better place. For example already has notion of app env vars and device env vars, (as it will be needed for "fleet config" and "device config").
Eg. env add RESIN_SUPERVISOR_DELTA 1 --device <UUID> --config

I was talking with @pcarranzav recently, and if I understood him correctly, the supervisor has no notion of config vs. env vars. I think it's confusing to the user to split them anywhere, including the UI (I know it confuses me). Is there a compelling reason we've kept them separate? Why not just indicate that any var beginning with RESIN_ will be treated differently by the supervisor, and put some nice UX around that in the dashboard?

It's the API that has (mostly) no notion of config vars, and stores both env and config vars in the same table.
The config/env split is done on the device state endpoint and the supervisor does distinguish between the two.
The original UI had env and config together, and then the split came to clarify the difference, and then the supervisor at some point stopped exposing the config vars to the app.
I think by now the differentiation is necessary, but I agree that we need a better UX around them.

This is no longer relevant, because we're going to rewrite all this entirely shortly for multicontainer support. I'm going to close this, we'll end up redesigning how the CLI should expose config/service vars as part of that work anyway.


Fix bug #8 (relative date deltas broken on Python 3.8+)

Here is a fix for issue #8. There is a check for extra (unknown) parameters being provided when creating a date object, but due to PyXBs internal date object actually being a datetime (with hh:mm:ss etc. set to 0), when creating a new date object on Python 3.8+ it detects (correctly) the extra parameters being provided. This patch ignores the extra zero values, and will only trigger an error if (other than the timezone) there are any extra non-zero parameters provided.
I've tested this patch on all releases of Python from 3.5 - 3.10 using the test harness in the github repo listed in issue #8.

This is great, thanks!


add DirectionalLightBundle similar to PointLightBundle

What problem does this solve or what need does it fill?
The PR https://github.com/bevyengine/bevy/pull/2112 added the DirectionalLight component, but in order to use it you need to spawn an entity with a Transform, GlobalTransform and DirectionalLight. This is cumbersome and can difficult to understand for an unexperienced bevy user.
What solution would you like?
A DirectionalLightBundle should be added similar to the PointLightBundle:
https://github.com/bevyengine/bevy/blob/cf221f9659127427c99d621b76c8085c4860e2ef/crates/bevy_pbr/src/entity.rs#L43-L49

Hey, new to rust. Will take a look at this

This issue should be closed since there's now a DirectionalLightBundle struct.


Create unbounded_knapsack.cpp

I am adding all the approaches for solving this problem like top - down and bottom up and it more space optimization.
Description of Change

Checklist

[ ] Added description of change
[ ] Added file name matches File name guidelines
[ ] Added tests and example, test must pass
[x] Added documentation so that the program is self-explanatory and educational - Doxygen guidelines
[ ] Relevant documentation/comments is changed or added
[ ] PR title follows semantic commit guidelines
[ ] Search previous suggestions before making a new one, as yours may be a duplicate.
[ ] I acknowledge that all my contributions will be made under the project's license.

Notes:

If i did mistake in any step please rectify me.


let's upgrade all public rooms from v1 and spec that all v1 rooms should be frozen henceforth

to stop the residual echos of hotel california ringing in our ears

possible approaches:

Put in the spec that v1 rooms do not accept new events anymore

Without heuristics to determine if a room was upgraded (as the tombstone can be reset away), we would imply that all rooms are upgraded.
Could put a date on it ("no new events after January 1st, 1970 at 00:00:00 UTC")

Implement a "soft-shutdown" for Synapse/homeservers that does Option A without preventing history from being usable (as shutting down a room blocks all access to the room).
Option C goes here.

I 100% support this, but the bridge crew would like a heads up so they can start migrating the many many many many many irc rooms still stuck on v1, which have so far been left like that because it's a matrix.org performance nightmare to migrate them at any sort of speed.

I'd strongly prefer to keep read-only access to the rooms without ability to send any new events, ever, with every homeserver generating a block of synthetic events (tombstone, power levels) so that well behaved clients could run business as usual without extra changes.


Add example cfg for performing regression with RDF

The default example config does not demonstrate how to use RDF for regression tasks.
Doing so requires that you set numeric features as well as the impurity measure in rdf as variance as opposed to entropy.
This config file demonstrates how to use rdf for regression.
Declaration:
This contribution is my original work and I license the work to the project under the project's open source license.

Check the end of src/site/markdown/docs/endusers.md -- these links can be updated

You're absolutely right - I've updated these in the latest commit with the new urls.
Happy to change other docs if applicable.


Record --> Map --> Inner Record conversion error

Description:
Converting a record to a map and then attempting to convert an element of the map, which was originally a record (say Person), to a record (of type Person) fails.
import ballerina/io;

type Person record {
    string fname,
    string lname,
    int age,
};

type Movie record {
    string title,
    string year,
    string released,
    Person writer,
};

public function main() {
    Movie theRevenant = {
        title: "The Revenant",
        year: "2015",
        released: "08 Jan 2016",
        writer: {
            fname: "Michael",
            lname: "Punke", age: 30
        }
    };

    map m = <map>theRevenant;
    Person writer = check <Person>m["writer"];
    io:println(writer.age);
}

fails with the error
error: error, message: 'map' cannot be cast to 'Person'
	at main(test.bal:28)

This fails at CPU checkCast, introduced because of the any to record conversion, since a map to record cast check is not defined.
Related Issues:
#10402

Current workaround is to convert the element to a map first and then to convert the map to the record.
map writerMap = check <map>m["writer"];
Person writer = check <Person>writerMap;

with introduction of stamp and convert methods with 0.990.0 we can write the above code as below.
import ballerina/io;

type Person record {
    string fname = "";
    string lname = "";
    int age = 0;
};

type Movie record {
    string title = "";
    string year = "";
    string released = "";
    Person writer;
};

public function main()  {
    Movie theRevenant = {
        title: "The Revenant",
        year: "2015",
        released: "08 Jan 2016",
        writer: {
            fname: "Michael",
            lname: "Punke", age: 30
        }
    };

    var m =  map<anydata>.convert(theRevenant);
    if (m is map<anydata>) {
        Person| error writer =  Person.convert(m["writer"]);
        if(writer is Person){
            io:println(writer.age);
        }
    }
}

This will output as 30. similer test case can be found here.
https://github.com/ballerina-platform/ballerina-lang/blob/master/tests/ballerina-unit-test/src/test/resources/test-src/expressions/conversion/native-conversion.bal#L644

Since we only allow conversions with anydata I guess the conversion working with map<anydata> is sufficient.
Closing the issue since it is now fixed.

Please update the example
https://ballerina.io/learn/by-example/json-struct-map-conversion.html
with this useful information, thanks

@ponsilva We've opened a PR https://github.com/ballerina-platform/ballerina-lang/pull/12765 to update this BBE. Thank you!