Configuration to disable auto shutdown when plugin dev mode is enabled

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

Feature
What did you expect to see?

Title says it all; private plugins have been requested (https://github.com/traefik/plugindemo/issues/7) multiple (https://github.com/traefik/traefik/issues/7088) times (https://community.traefik.io/t/use-private-plugins-in-production/6993/3) but it seems the development team is currently focused on "open source plugins" (https://github.com/traefik/traefik/issues/7088#issuecomment-662599830)
In the spirit of open source and more broadly freedom of choice why not let users disable the current limitation of dev mode? https://github.com/traefik/plugindemo#dev-mode-limitations

Dev Mode Limitations
Note that only one plugin can be tested in dev mode at a time, and when using dev mode, Traefik will shut down after 30 minutes.

Using dev mode currently feels like an anti-feature or even worse some kind of trial version.

Hello @willymilkytron,
The dev mode for plugins has been designed for plugin developpers to allow them to test a plugin from their local machine.
Concerning the private plugins, as you said, it has already been addressed by the issue #7088.
Please feel free to interact into this issue (#7088) to follow up on that subject and give your inputs.
Accordingly, I'll close this issue as a duplicate.
Anyway, thanks for your contribution and your interest in Traefik !

@rtribotte how is this a duplicate? I'm not asking for private plugins, i'm just asking for some way to prevent Traefik from shutting down after 30 minutes when in dev mode.

Please reopen this different Feature request @rtribotte

Hi @willymilkytron, and thank you for your feedback.
Like you said in the initial message, Traefik supports and promotes open-source plugins. We designed the dev mode with plugin development in mind. Thus, we added limitations to ensure no one would run a non-production-ready instance in production.
Removing the 30-minute limitation with no alternative doesn't sound reasonable to me. Still, it sounds like you have proposals for better user experience, which I'm very much willing to hear about. (And we can reopen the issue if so.)
Having said that, and this is where the confusion comes from, you mentioned private plugins. I know that private plugins are a (very) popular request, and I would like to avoid mixing the two purposes (development mode / private plugin support).


chore(main): release 1.2.0

:robot: I have created a release beep boop
1.2.0 (2022-09-16)
Features

adjust新增git配置相关 (8d54986)

Docs

修改READEME折叠图片 (35147ca)
修改完善CONTRIBUTING文档 (eaf06d2)
完善文档 (edc33ec)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/WGrape/posture/releases/tag/v1.2.0 :sunflower:


mismatched interface file version (wanted "8063", got "8064")

I tried to install and run IHaskell on Manjaro following the instructions but end up with an error on kernel creation:
[I 22:25:17.387 NotebookApp] KernelRestarter: restarting kernel (4/5), new random ports
ihaskell: Bad interface file: /home/arsleust/.stack/programs/x86_64-linux/ghc-tinfo6-8.6.4/lib/ghc-8.6.4/base-<IP_ADDRESS>/Prelude.hi
    mismatched interface file versions (wanted "8063", got "8064")
Bad interface file: /home/arsleust/.stack/programs/x86_64-linux/ghc-tinfo6-8.6.4/lib/ghc-8.6.4/directory-<IP_ADDRESS>/System/Directory.hi
    mismatched interface file versions (wanted "8063", got "8064")
Bad interface file: /home/arsleust/.stack/programs/x86_64-linux/ghc-tinfo6-8.6.4/lib/ghc-8.6.4/unix-<IP_ADDRESS>/System/Posix/IO.hi
    mismatched interface file versions (wanted "8063", got "8064")
Bad interface file: /home/arsleust/.stack/programs/x86_64-linux/ghc-tinfo6-8.6.4/lib/ghc-8.6.4/base-<IP_ADDRESS>/System/IO.hi
    mismatched interface file versions (wanted "8063", got "8064")
Bad interface file: /home/arsleust/.stack/programs/x86_64-linux/ghc-tinfo6-8.6.4/lib/ghc-8.6.4/template-haskell-<IP_ADDRESS>/Language/Haskell/TH.hi
    mismatched interface file versions (wanted "8063", got "8064")

The other issues #986 and #958 did not help.
My setup:
$ ghc --version
The Glorious Glasgow Haskell Compilation System, version 8.6.3
$ stack --version
Version 1.9.3, Git revision 40cf7b37526b86d1676da82167ea8758a854953b (6211 commits) x86_64 hpack-0.31.1
$ jupyter notebook --version
5.7.4

I am new to Haskell development so it might be something really dumb, sorry about that.

See https://github.com/gibiansky/IHaskell#the-kernel-keeps-dying-ihaskell--stack. Your ~/.stack/global-project/stack.yaml probably lists a resolver with GHC 8.6.3 but the latest resolver uses GHC 8.6.4, hence the mismatch.

I have found this:
$ stack exec ghc -- --version
The Glorious Glasgow Haskell Compilation System, version 8.6.4
$ ghc --version
The Glorious Glasgow Haskell Compilation System, version 8.6.3

Clearly linked to my mismatch, isn't it ?


Remove entity picture of Tuya entity

Description:
This removes the default entity picture for all Tuya entities. Home Assistant will provide a generic icon based on the device type. We should only use entity picture to represent people/content.
We can use the icons again in the future when we introduce devices https://github.com/home-assistant/architecture/issues/36
CC @huangyupeng

@balloob I get it. Thanks.


modules: mbedtls: bring back SHA384 support

Before mbedTLS 3.0 there was just SHA512 option, which enabled both SHA384
and SHA512 support. mbedTLS 3.0 introduced SHA384 specific option, which
means that SHA384 got unsupported after merging
commit 4e6cfb67f91a ("modules: mbedTLS: Bump mbedTLS to 3.0").
Introduce SHA384 Kconfig options, so that support for it can be selected in
project configuration if needed. Since SHA384 still depends on SHA512 to be
selected, add such dependency in Kconfig.
Select SHA384 support in non-generic (not configured by Kconfig) mbedTLS
config headers, so that previous (before mbedTLS 3.0 was merged) behavior
is regained.
Fixes: 4e6cfb67f91a ("modules: mbedTLS: Bump mbedTLS to 3.0")

Can you split the pr in two commits, one bringing back sha384 and another one with the stack size change ?
The change looks fine for me though.


Hoxton.SR5 BOM inadvertently pulls in Spring Boot 2.3.0 when using the Gradle native BOM support

Describe the bug
Hoxton.SR5 BOM inadvertently pulls in Spring Boot 2.3.0 when using the Gradle native BOM support (i.e. when not using the Spring Boot Gradle plugin).
Link to gitter discussion
Sample
dependencies {
    compile platform("org.springframework.boot:spring-boot-dependencies:2.2.8.RELEASE")
    compile platform("org.springframework.cloud:spring-cloud-dependencies:Hoxton.SR5")
}

should result in Spring Boot 2.2.8 being brought in but it ends up brining in Spring Boot 2.3.0.
The older Hoxton.SR4 BOM does not have this issue.
(My Gradle version is 5.6.3 if it matters.)

Can you try with a later version of Gradle?

@spencergibb I tried with gradle 6.4.1 but it did not resolve the issue.
This is the example build.gradle that I'm using:
plugins {
    id 'org.springframework.boot' version '2.2.8.RELEASE'
    id 'java'
}

group = 'com.example'
version = '0.0.1-SNAPSHOT'
sourceCompatibility = '1.8'

repositories {
    mavenCentral()
}

dependencies {
    implementation platform("org.springframework.boot:spring-boot-dependencies:2.2.8.RELEASE")
    implementation platform("org.springframework.cloud:spring-cloud-dependencies:Hoxton.SR5")

    implementation 'org.springframework.cloud:spring-cloud-starter-sleuth'
    testImplementation('org.springframework.boot:spring-boot-starter-test') {
        exclude group: 'org.junit.vintage', module: 'junit-vintage-engine'
    }
}

test {
    useJUnitPlatform()
}

Doing a ./gradlew clean bootRun will print the Spring Boot 2.3.0 banner.

It was really a shot in the dark.

Closing due to age of issue.


Fix for Accent Color Change Theme bug

[x] I have read the contributing guidelines and I agree with the Code of Conduct
[x] Have you checked that there aren't other open pull requests for the same changes?
[x] Have you tested that the committed code can be executed without errors?

Hi there,
Accent color change in QT>=6.5 makes windows title bar go back to light mode and no method is currently available to prevent this - See: https://www.qt.io/blog/dark-mode-on-windows-11-with-qt-6.5. This code is currently hacky and sometimes fails to work or cause a flicker.
Video:

Before
After

https://github.com/marticliment/WingetUI/assets/106472154/2ff63f61-b449-497a-ac45-7a9d59bce2c9
https://github.com/marticliment/WingetUI/assets/106472154/eec61ccc-ad3a-465e-b510-78c3e4634a5f

Some other ways to reduce currently occurring problems -

We can increase the timeout to 2000ms or 3000ms for waiting for qt to finish changing the theme - decreases failure but causes the app show light mode for longer time.
Set app style to None - can have some unwanted behavior.

Thanks
Edit: Formatting

I have updated timer to wait for 3000ms. This makes the theme change back to selected one work most of the times.
Updated Video -
https://github.com/marticliment/WingetUI/assets/106472154/13621319-1909-406b-893a-3940562d6ec0

Seems fine until this bug gets fixed.
When ready let me know to be able to merge.
Thanks!

Checked on Windows 10 and the code is working correctly, ready to merge.

I have done my testing and it appears to work fine.
Thank you!


Add IT with using a code coverage tool

[...] If you’re adding your own class loaders you might also consider doing on-the-fly instrumentation within your class loaders. See our API example “CoreTutorial”: https://www.jacoco.org/jacoco/trunk/doc/api.html

By Marc Hoffmann at https://groups.google.com/d/msg/jacoco/yoKcvEwvgKg/EzxeT823DAAJ

Isolator creates the classloaders, so it should be a feature of this project.


[Fix]: space delete command

Current behavior
Fixes #6484

Proposed changes

Checks

[x] All commits in this Pull Request are signed and Verified by Github.
[x] All commits in this Pull Request follow the Ockam commit message convention.
[x] There are no Merge commits in this Pull Request. Ockam repo maintains a linear commit history. We merge Pull Requests by rebasing them onto the develop branch. Rebasing to the latest develop branch and force pushing to your Pull Request branch is okay.
[x] I have read and accept the Ockam Community Code of Conduct.
[x] I have read and accepted the Ockam Contributor License Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the build-trust/ockam repository. The easiest way to do this is to edit the CONTRIBUTORS.csv file in the github web UI and create a separate Pull Request, this will mark the commit as verified.

Hey @Tashuuuu! The PR looks good to merge but we first need you to accept our CLA before we can proceed. Here is how to do it:

I have read and accepted the Ockam Contributor License Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the build-trust/ockam repository. The easiest way to do this is to edit the CONTRIBUTORS.csv file in the github web UI and create a separate Pull Request, this will mark the commit as verified.

We also need your commits to be signed as described here:

All commits in this Pull Request are signed and Verified by Github.

Hey, I accepted the CLA but do I need to make a separate PR? In which my commits are signed

Hey, I accepted the CLA but do I need to make a separate PR? In which my commits are signed

You can just ammend your commit and force push. You can do that as follows
git commit -S --amend
git push --force

Make sure to do the same in your other PR's so we can merge them as well 👍

I did this in all the PRs, hope it's signed now. Do let me know if any problem occurs in them. Thank you for helping.


Check response title for setPassword validate code failure

cc @marcaaron
Details
This PR is a follow up to fix https://github.com/Expensify/App/pull/5398/files#diff-283c48b7349b0bf7aba66da8891bc8a9f9df70664bd06e7a875f56b19c6c02f9R275. We were checking the message instead of the title, so if the user clicks an expired or invalid validation link the error message won't be shown.
Tests/QA

Click on an old validation link, or open a validation link with a nonsense validation code (I used http://localhost:8080/setpassword/2/asdfabc123 on dev)
Set a new password and submit the form, confirm the error message shows

Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[x] iOS
[x] Android

Screenshots

No worries, I should've added it to the list of tests as well 🚀

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @marcaaron in version: 1.1.0-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @Jag96 in version: 1.1.1-8 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


[css] Automatically show css value suggestions after completing property name

From https://stackoverflow.com/questions/45470541/visual-studio-code-html-suggestion-not-working/45470614
Repo Steps
In a css file:
body {
   backgro|
}

Accept the suggestion for the background-position property name.
Feature request
After completing the property name, we should automatically show suggestions for the possible values. You currently have to start typing or trigger suggestions manually to see them.

@jrieken @joaomoreno not sure who owns 7/24 nowadays

@aeschli You could actually implement that yourself by use the post-completion command, just set it to trigger completions again.

@jrieken I tried that by putting the 'editor.action.triggerSuggest' to the proposals, but the new completion window is not sowing. I filed #34565.

It's in 1.19


Replace ADD with COPY instruction in Dockerfile

test-me-please

Thanks for the PR @juliengk. Could you add some explanation on the rationale behind the switch to the  commit message? (something as simple as "COPY only copies but ADD will unpack archives and fetch URLS" is fine). The change out of context is confusing.

test-me-please

Test failure seems unrelated, to do with failing to download the vagrant image. Will retrigger test run.

test-me-please

I have updated the Dockerfile in envoy directory. Let me know if that's good.
Do you want me to do the same for those dockerfiles as well?

Documentation/Dockerfile
contrib/packaging/deb/Dockerfile
contrib/packaging/rpm/Dockerfile


Can we get the button text from mouse click

Hi,
I was wondering can I get the button text from mouse click.
Thanks,
Attiqe

on [GlobalHookMouseDownExt] event, simply call:
MessageBox.Show(string.Format("MouseDown: {0}", e.Button));

It doesn't work, button contains "Left" or "Right", not button text as @attiqeurrehman asked.
Any other idea?
Thanks

I don't follow, what you guys mean then with Button Text? you mean the actual button name? not the button click?, please expand and clarify.


Implement JSON and JSONB codecs

Hi @mp911de! I'm opening this PR as an alternative to #39 but using Jackson dependency instead of GSON. I also took into account your suggestions to provide a certain level of flexibility and added return types for ByteBuf, byte[], String and InputStream.
I only added the codec to JSONB since we'll need another codec for JSON. This is because the doEncode(Object value) method does not have any way to choose which one it should encode: JSON or JSONB.
I can open another PR after this one with the JSON codec or add it to this PR if you think it would be ok 🙂
Cheers!

Thanks for your PR. As stated in #39, supporting JSON(Oid) is something that we want. What we do not want is including a dependency to any JSON library in the core driver. We should expose JSON payload as binary (byte array, ByteBuffer, ByteBuf?, InputStream) data type, similar for writing.
Any JSON processors should live on the client library or application level or can be contributed by driver extensions (driver extensibility is on our roadmap).
We’re happy to merge basic support for now, without Jackson.

@mp911de that makes sense! I updated the branch with the suggested approach, please let me know what you think 🙂
I cannot change the branch name so if you prefer I could close this PR and open a new one with a proper branch name

No worries, the branch name isn’t an issue at all. Codecs already look well. Recently we kept binary and text formats within a single codec (see https://github.com/r2dbc/r2dbc-postgresql/blob/master/src/main/java/io/r2dbc/postgresql/codec/AbstractNumericCodec.java). I’d suggest adding an AbstractJsonCodec with concrete subtypes for ByteBuffer, ByteBuf, byte[] and InputStream.
The need for multiple subtypes is current a flaw of our approach that we will need to cleanup.

@mp911de awesome, good to know we're going the right way! Just to be clear, we'll need the following codecs based on an AbstractJsonCodec right?

ByteBufferJsonCodec, ByteBufferJsonbCodec
ByteBufJsonCodec, ByteBufJsonbCodec
ByteArrayJsonCodec, ByteArrayJsonbCodec
InputStreamJsonCodec, InputStreamJsonbCodec

I'm not sure we can have JSON and JSONB in the same codec file since the doEncode(Object value) still doesn't have a way to know which one to use. Does this make sense? 🤔

Partially. AbstractJsonCodec  would resemble AbstractBinaryCodec to some extent. We don't require a distinction between Json and Jsonb codecs, they could be handled within the same codec.
Codec decoding is based on format, type oid and the requested Class. Encoding solely relies on the value/value type. For byte[] and ByteBuffer, all encoding would be handled by our binary codecs as we don't have a mechanism to enforce a JSON codec to encode the value.
We want to introduce with R2DBC 0.9 type descriptors so a value can be encoded using a more specific codec.

Thanks for your PR. I'm going to take it from here.

There's one fundamental issue that became obvious during integration testing requiring us to rethink the API. Using byte[], ByteBuffer or String as interchange type leads to:
 column "value" is of type jsonb but expression is of type bytea

as Postgres isn't able to convert between json/jsonb and bytea or varchar.
It seems that we should add a dedicated Json type so we can enforce a proper JSON type to encode outgoing values.

That's merged and polished now.


Clear Selection and Active Cell

I don't see any API methods that do this. But maybe I'm missing something. Is this currently possible?

grid.activeCell is a property, sorry about the lack of an entry in the documentation.  There appears to be a few undocumented properties/methods, I tried to clean them all up in the last release after realizing they were undocumented.  You should find grid.activeCell there now.
grid.selectArea can be used to clear the selection (set everything to -1), but that seemed annoying so I added a new method: grid.selectNone which you'll find in 0.16.9.

Sweet thank you! :)


[SPARK-26875][SS] Add an option on FileStreamSource to include modified files

What changes were proposed in this pull request?
The current behavior only the check the filename to determine if a file should be processed or not. I propose to add an option to also test the file timestamp if is greater than last time it was processed, as an indication that it's modified and have different content.
It is useful when the source producer eventually overrides files with new content.
How was this patch tested?
Added unit tests.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

First of all, I agree this would be one of valid use cases.
I'm just thinking out loud about edge-case (maybe that's why Spark restricts): when timestamp of file is modified in any chance (contents being added, some unintended modification, etc.), all of contents in file are reprocessed (as UT in this patch leverages it) which is not only breaking end-to-end exactly-once but also breaking stateful exactly-once because state will not be rolled back. So the option would fall into "at-least-once" semantic for such case which end users would expect at least stateful exactly-once. It needs to be warned.

Ah the title of PR is saying about processing "modified file" instead of new file being overwritten to same file name. Then what I stated is not for an edge-case but just for the case this PR addresses.

Yes, that why is important to keep this option as default false keeping the end-to-end exactly-once guarantee. I'll add a note clarifying that in case of modification the whole file content will be processed again.
I like the "modified file" because it's just what it is. If I change to "overwritten files" it might be misunderstood as a content comparison, which is harder to address.

The patch looks simple and clear: it seems to be just a matter of policy - allow or disallow possibly non-safe behavior via option.
Personally I'd a bit worried there might be some cases which last modified timestamp on file is modified unintentionally, then things got messed up. Even end users intend to enable this option, end users might complain when end users encounter reprocessing file as well as breaking semantic due to unintended reason. Thought about way to mitigate shortly - mostly regarding file offset - but new overwritten file could have same file length, as well as we also need to store file offset so doesn't seem to be good option as of now.
Maybe I'd worried too much, so need to hear other voices as well. (I'm just a one of contributor anyway and decision will be taken from committers so it's just my 2 cents.)

The users always have to understand their use-cases before activating non-default options. Take fileNameOnly option for example: If it gets activated in a wrong use-case it leads to data loss.
Same here, we just have to be clear about what will happen when activating the option in the docs.

The question is why some producer generates the same file again?
From data source perspective I see mainly 2 actually implemented ways:

Atomic move to a directory (several engines does that but Spark does it differently because S3 moves the files with copy for example)
Write the file a non-atomic way but update metadata file with the already properly written filename. Here the available files are coming from the metadata and all others considered junk.

+1 @HeartSaVioR  and I'm worried with this patch as well.

Let's take any filesystem, append a file 10k times and then close it. Is it guaranteed that only after the last append will the timestamp updated and no internal OS flush touch it? If there is no guarantee random exception will be thrown by the SQL engine because maybe half of a row written out.
Let's take S3 as another example. Even with S3 guard the file modified, the metadata shows the file is there but because of it's read-after-write consistency the file content can be

The original one
The new one
Empty file
This change may increase this behaviour.

All in all with my actual understanding I would change the producer.

Some producers does not care much about the uniqueness of filenames, leading into possible/often file overriding. The motivation of this patch is exactly when you can't change the producer's behavior 😄
In my view, this option is a good complimentary of https://github.com/apache/spark/pull/22952 where we would be able to archive/delete processed files. Without this option, if we upload a file with same name as the previous processed and deleted one, it wouldn't get processed leading into a non-intuitive behavior.
Addressing your concerns:

No random exception will be introduced by the option. It only changes the behavior of considering the file for processing or not for each microbatch. The possible race condition that you mention can happen even for a brand new file being written while processing, not related with the patch.
Again, the patch does not change anything about how the files are processed. It just introduces another option to control what files were already processed besides the filename. When enabled, it basically treats an already processed file with a new timestamp as a new file again.

you can't change the producer's behavior

and

No random exception will be introduced

is contradictory to me.
How would you deal with the simplest situation: Spark is archiving and producer is uploading the same?

Maybe is not clear that the patch does not change any processing behavior, it only adds an option to consider "is this file new and should be included on the micro-batch?"
This is the current FileSourceStream workflow:

When it starts, it read the checkpoint data to get a list of previously processed files and put them in a map called seenFiles where the key is filename and value is timestamp.
For each micro-batch, it lists all files in the directory and checks if the seenFiles map contains the filename to determine if it is a new file or not. Here is where I'm proposing the change.
With the list of new files, it creates a DataSource instance that will handle the correct file format and codecs on and setup a Dataset. These are the classes responsible for reading the file, not changing anything here.
The micro-batch gets the Dataset and executes it. When it finishes, update the checkpoint data with the processed filenames. Then it goes back to step 1.

Answering your question:

How would you deal with the simplest situation: Spark is archiving and producer is uploading the same?

includeModifiedFiles=true: the file content will be processed in the next micro-batch.
includeModifiedFiles=false: the file content will be ignored.

Regarding eventually race conditions, nothing is changed. Spark will deal with it using the Datasource current mechanisms.

Maybe @gaborgsomogyi is considering more than what it is as of now. Currently #22952 is implemented as synchronous approach, but @gaborgsomogyi had his voice to make archiving/deletion being async in #22952 (we talked about dealing with it in next TODO), and it's based on the assumption that we never process the file again even same file is added as new.
When the option is turned on, it breaks assumption and things will get changed very differently - including race condition what @gaborgsomogyi is stated. When we hit by race condition It would produce unintended result (maybe worse scenario would be archive/delete a new file before processing).
Not sure race condition occurs even archiving/deleting is synchronous.

I think that the archive/delete race condition can be addressed by checking the file timestamp before archive/delete. If it is the same as the processed, proceed. If not, skip. This extra step can be enabled only if includeModifiedFiles is enabled, which tells that files can be overridden.
Talking about end users expectations, if they upload a file and it gets deleted/archived, they probably expect a new file with the same name to be processed as well when uploaded again. Do not process the file is not intuitive and is also hard to debug which files names were processed in past. Why my file is not getting processed can be a frequently asked question.
I totally understand the implications of files been unintentionally modified as well pointed by @HeartSaVioR and that's why the option is false by default, but I do think we need to provide an option to cover more use-cases and give a solution for users who understand that their files can be overridden.

Can one of the admins verify this patch?

IMO, overwriting an existing file is an anti-pattern. Most of storage systems cannot handle this properly:

S3: overwriting will be eventually consistent. There is no guarantee that which version we will get.
Azure blob storage and data lake: reading a file that's being modified may throw a conflict error.
HDFS: I don't know whether it supports reading a file that's being modified.

Generally, file stream source requires the files appear in the directory atomically so that we don't need to handle the case that Spark reads a file that is still being written. Overwriting an existing file breaks this assumption.

Hi @zsxwing, thanks for taking time and share your thoughts. The idea of this configuration to add another condition to consider if a file should be processed or not. It does not make any assumption about concurrently modified files or anything else. Everything remains the same.
The scenario that I'm trying to solve here is:

User uploads the file  lastest_sales.csv to the source folder
Spark processes it
File lastest_sales.csv gets deleted (manually or via the new configuration https://github.com/apache/spark/pull/22952)
User uploads the file lastest_sales.csv to the source folder
Spark does not process it because it already processed the lastest_sales.csv filename
User gets confused. Even if explained/documented, there is no way to tell which filenames were already processed.

What this PR simply proposes is: If enabled, instead of only check the filename to determine if a file was already processed, check the file timestamp as well. Race conditions, file system specifics, stream semantics, and everything else remains the same.

@mikedias Thanks for giving the scenario. Yep, I understand this could be helpful. However, I would like to understand more about the use case. How does a user upload lastest_sales.csv to the source folder?

Writing directly. This is not recommended as it can potentially break the streaming query if it sees a partial file.
Rename into the source folder. Then since a rename operator is involved, why not add a uuid to the file name so overwriting a file is totally not necessary.

As I mentioned previously, overwriting a file makes everything complicated. The user has to think about when is the safe time to overwrite a file. Adding this option may make the user think Spark can handle file overwriting correctly, however we don't and cannot handle race conditions internally in Spark.

File lastest_sales.csv gets deleted (manually or via the new configuration #22952)

I don't think it is safe to delete the file manually outside of Spark, as it cannot be known whether the file is processed and added to the commit log. Checking whether the file is processed is not sufficient - it should ensure the file will be never accessed.
Assuming the file is deleted/archived from Spark, I'm seeing the possible confusion from user side as well since it's no longer an "overwrite" if the file is processed and cleaned up. So that seems to be a valid use case, though we may need to think how we let Spark differentiate "overwrite" and "add new file which was deleted or moved".

Thank you @zsxwing  @HeartSaVioR for taking time and reviewing this PR. Glad to see activity here :)
@zsxwing The files are uploaded directly to the source folder. I don't see a need for an intermediate step that moves files around.
@HeartSaVioR A common use case for deleting files outside Spark is to remove the old files sitting in the source folder impacting the performance of the ListObjects operation. We use S3 lifecycle policies to delete the files after 15 days (giving plenty of time to Spark process them).
I agree that having an option with  modified file in its name might suggest that Spark is providing extra guarantees for race conditions. But what if we rename it to something like: fileUniqueness: filename (default) and fileUniqueness: filename+timestamp? That would be more accurate to what the PR is trying to achieve and does not set wrong expectations.

@mikedias

A common use case for deleting files outside Spark is to remove the old files sitting in the source folder impacting the performance of the ListObjects operation. We use S3 lifecycle policies to delete the files after 15 days (giving plenty of time to Spark process them).

I agree that some manual operations have to be taken for such case, but as Spark has no idea about the current status of files if they can be modified, unfortunately that has to be with your own risk. There's an option spark.files.ignoreMissingFiles which helps to tolerate file deletion, but for "overwrite" there's no option to help tolerating this, and @zsxwing already explained how hard "in depth" to do it right.
SPARK-20568 provides the way to remove/archive processed files in safe manner officially, so I would agree there's a valid case if end users see the folder and confirm the file doesn't exist and put the file there while the other file with same path was actually processed and removed/archived. I guess that might be considered if we all agree about this as valid use case.

There's an option spark.files.ignoreMissingFiles which helps to tolerate file deletion, but for "overwrite" there's no option to help tolerating this
In fact, there's the option spark.sql.files.ignoreCorruptFiles that helps to deal with partial/corrupted files. We've been using it along with spark.sql.files.ignoreMissingFiles successfully in our stream queries.

In fact, there's the option spark.sql.files.ignoreCorruptFiles that helps to deal with partial/corrupted files.

If the partial file is readable by luck, then the query will not read the further content. That's not an option reserved for overwriting file.

See above comments - I think we already explained why it is not a good idea.

@HeartSaVioR If you don't mind, can you summarize the main concern here. I read all the comments here but it was hard to follow them and understand the reason why this is not approved.

https://github.com/apache/spark/pull/23782#issuecomment-555210613
This comment explains everything.
Also I do not agree that spark.sql.files.ignoreCorruptFiles is a rescue, likewise I commented above. If you ever require Spark to provide at-least-once fault tolerance, there should be never a change to the source on replay. If the input file is somehow overwritten between the batch failure and the reprocessing of the same batch, fault tolerance is going to be broken. It's a hard problem, not a trivial one.


ts-codegen updates

fix #420

update types for hackwasm

thank so much!
one small thing

[ ] Splits contract: ListMembersResponse  needs to be renamed to MemberListResponse

can be done via:
export_schema_with_title(&schema_for!(ThingName), &out_dir, "NewNameOfThing");


(docs) Explain what node_terminus setting does; clarify external_nodes setting

When this is merged, please resolve DOC-2939.

(The classifier terminus isn't part of base puppet, I'm leaving out the LDAP terminus, etc. etc., but since indirections are such a hairy extension point and the "node object" is such a weird construct, I'm trying to hit a solid 80/20 point with this description so people can understand what this setting is for without getting confused or going down a rabbit hole.)

CLA signed by all contributors.


consistency

improve data consistency IMO.
Atleast the chainid should be in every JSON part

The reason why this happened is because those contracts where deployed with different versions of the deployer script. Well done!


Fix port hint

This will fix #802

location.origin is not supported on IE 10 & under.
http://www.w3schools.com/jsref/prop_loc_origin.asp


wireless/bluetooth: Initialize private bt_driver_s member.

Summary
The priv member is currently unused but should not be null after the bt driver is registered.
Impact
None
Testing
Modified code and printed the value of priv. It is not NULL like it used to be.

@ldube please fix the below nxstyle warning:
Error: /home/runner/work/nuttx/nuttx/nuttx/include/nuttx/wireless/bluetooth/bt_driver.h:88:52: error: Block comment terminator must be on a separate line
Error: /home/runner/work/nuttx/nuttx/nuttx/include/nuttx/wireless/bluetooth/bt_driver.h:93:40: error: Block comment terminator must be on a separate line

you can verify the fix locally:
./tools/checkpath.sh -g HEAD~...HEAD


Cannot assign array containing string-type to union of Iterable and string.

I searched, but was unable to find anything that matched this.  The code in question is super simple:
type Instance = "t2.nano";

const types1: Iterable<Instance> | string = ["t2.nano"];
const types2: Instance[] | string = ["t2.nano"];

Also found here:
https://www.typescriptlang.org/play/#code/C4TwDgpgBAkgdgZ2AQzgY2gXigImAJgDo5UB7HAbgCgq1TFgpRIEBGALlmAgCdkAjADYQAPPCSoMAPigAfKEh4BLOAHMo2ANp4iJOOQC61OgybgICfJ3Ep0ETQbkLgytRqjaCxMjiNA
TS gives an error on types1:
Type 'string[]' is not assignable to type 'string | Iterable<"t2.nano">'.
  Type 'string[]' is not assignable to type 'string'.

This is a bit strange as the compiler has no problem with the second line (when assigning to Instance[].  Also, if i change the first like to const types1: Iterable<Instance> = ["t2.nano"]; then it's ok.
I can't quite reason about why types2 is ok, or why removing | string is ok, but why it's not ok to just say Iterable<Instance> | string = ....
Is this a bug?  Or is this intentional and falls out from some part of TS that I'm unaware of.  Thanks!

Tagging @RyanCavanaugh @DanielRosenwasser .   Sorry if this is something very obvious.  But we def found this very strange and unexpected.

It's not a bug in the sense of something not working the way it's supposed to, though the produced behavior is obviously not desirable.
The problem is that string is also an Iterable, so when you write
const types1: Iterable<Instance> | string = ...

it's not apparent whether the elements of the array should be contextually typed by the iterator type provided by Iterable<Instance> or string's iterator type... so both are, and your element contextual type is string | Instance which is not sufficient to cause a string literal to acquire a literal type.
The reduced form would be something like this:
// Error
const a: (Iterable<string> & { baz: string }) | Iterable<"foo"> = ["foo"];
// OK
const b: (Iterable<number> & { baz: string }) | Iterable<"foo"> = ["foo"];

Interesting... though i'm not quite understanding the problem.  If i'm reading what you're saying right, then because we have Iterable<Instance> | string then we are contextually typing the array literal to Iterable<Instance> | Iterable<string> which then contextually types to Iterable<Instance | string>.  But shouldn't the array literal contextually type wiht that?  Since "t2.nano" would match Instance | string?
Sorry for being obtuse here :)

Instance | string is really "t2.nano" | string which I believe gets subtype-reduced to string, and so the contextual type loses the literal value.

and so the contextual type loses the literal value.

Ok... but can you clarify why that's a problem.  If hte contextual type is string, shouldn't ["t2.nano"] then contextually type alright?  after all, there's a string in the array, so a string should match the string type.  Right?  (again... feeling dumb that what you're saying isn't clicking in my brain).

We only retain literal types if contextually typed by some other literal. When we try to get the iterated type from string[] | Iterable<"t2.nano">, we end up with the contextual type string | "t2.nano" which is just string.
When we calculate the valueof the right side (i.e. the expression ["t2.nano"]), we're left with string[]. Then we have to see if that's assignable to string[] | Iterable<"t2.nano">.
So string[] is clearly not assignable to a string - the latter is a primitive.
But is Array<string> assignable to a Iterable<"t2.nano">? We can see that it isn't in the case of an array like ["doom", "doom", "doom"].

Ah, it clicked.  You contxtually typed the RHS just fine.  But it's then trying to see if the RHS actually fits the actual specified type where things go bad.

So... what happens in a case like this?  It seems 'by design' in terms of the compiler faithfully executing the rules of the language.  But it also seems highly unfortunate in terms of the language not allowing something that makes total sense.
Brainstorming a bit, the part that unfortunately seems to go off the rails is that while i wrote Iterable<InstanceType> | string, that then merged into Iterable<InstanceType | string>.  While that seems reasonable to me in some cases, it feels more appropriate if it was a secondary step that happened after the language first said:

you have a union type of A | B | C.  I should first check if i can contextually type the RHS to any of those successfully.  If so, this succeed, and the RHS has that type.
If that fails, then i try to do my merging of these types into some other type that i will then contextually type with.

Would such a thing be possible?  Desirable?  Worst idea ever?

I think it depends. The problem is that you need to know when to ask to try the apparent contextual type vs. each constituent of a contextual type.
interface Dog { bark(): void }
interface Cat { meow(): void }

type Obj = { method(x: Dog): void } | { method(x: Cat): void };

let foo: Obj = {
  method(x) {
    // ...
  }
};

What type should the parameter x have in foo? If you try to contextually type the object by each union constituent, the first successful one will contextually type x with either Dog or Cat.
Technically, it would be best to make it Cat | Dog in this case. To do that, you actually need to start out with the union of object types and then do the right thing as you calculate the contextual type for method.

Note that today you have neither behavior - it's an implicit any and we force the user to choose one under stricter settings, because the options are picking the wrong one or needing to satisfy multiple signatures simultaneously. Picking the wrong signature could be surprising, and satisfying multiple signatures simultaneously is nearly impossible.

:(


Make sure ~./bash_profile is not edited multiple times upon running install multiple times in a row

After making multiple attempts to install docker using the one liner in README.md, I found that my .bash_profile file contained several instances of the same line, over and over:
# Docker (default for Vagrant based boxes)
export DOCKER_HOST=tcp://localhost:2375

# Docker (default for Vagrant based boxes)
export DOCKER_HOST=tcp://localhost:2375

# Docker (default for Vagrant based boxes)
export DOCKER_HOST=tcp://localhost:2375

# Docker (default for Vagrant based boxes)
export DOCKER_HOST=tcp://localhost:2375

# Docker (default for Vagrant based boxes)
export DOCKER_HOST=tcp://localhost:2375

Resolved by https://github.com/blinkreaction/boot2docker-vagrant/commit/baadd5740397db2ff49fd19c3d9974e2984c3f0d


Any other toyyo having a issue using this?

I didn't even try just want to make sure.

Can build for us baiyas

Can use for us baiyas

Feedback from some Jeppos would be helpful too

Can confirm that it works.I just mined a few coins just for fun (Had to use a docker since I am running Ubuntu 20) Looking forward to buy a piece of land from the port city in the future

Here's the Dockerfile if anyone needs

@teshanshanuka this is great! if you don't mind, can you make a PR to the original repo with the DOCKERFILE. Thanks!

Nice terminology. People who cannot use this, or are having an issue (building, installing etc.) should hereafter be labelled Toiya.


Update Service Project info

The service project info is described in the _config.yml file in the main directory. The serviceprojectImage file should go in the /img/sponsors directory.
Note: changes to the _config file require a jekyll-rebuild, so once you make the changes on your local machine, run bundle exec jekyll build and bundle exec jekyll serve before viewing the changes.

@tuckerk3 - are you the main contact for this year's service project? should we assign this one to you?

@kenirwin Yes, Marsha Miles and I are coordinating, so you can assign this one to me.

Closed by #114


[Subtask] Kyuubi Spark TPC-DS Connector - Add tiny scale

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

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

Describe the subtask
Current available scales: 0, 1, 10, 100, 300, 1000, 3000, 10000, 30000, 100000.
Event scale 1G is a little bit large for demo on laptop, we can introduce a scale 0.01 and name the database as tiny for demo purpose.
Parent issue
https://github.com/apache/incubator-kyuubi/issues/2538
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

I’m interested in taking this up.

Assigned, thx.


Only devices with static DHCP showing up

Hi, thank you for this great plugin!
One problem I have is that only the devices with static leases show up as device_tracker entities.
All others (dynamic leases) do not show up.
Is this intended? Is this a bug only I observe? Can I change sth about this?
I'm monitoring wifi devices across APs and SSIDs in HA with the help of openwrt and display the device entities according to where they are connected. I would love to also see devices with dynamic leases in there (as I don't set leases in a guest network e.g.)

Welcome!
You must explicitly select which entities you want to follow for device tracker and that process is not connected to dhcp at all, it strictly reads the arp table of opnsense.
Can you provide more detail and explain what leads you to believe the static entries are relevant?

I just figured it's opnsense which only puts clients with a static dhcp lease in the arp table (in contrast to openwrt where any dhcp lease is added to the arp table I think). Not a issue where I cannot see devices provided by the integration but being deactivated - I activated them all.
So this is not a bug or issue at all, it's just wrong assumption on my side.
Having devices with dynamic dhcp leases show up as device tracker entities would be nice though, so maybe you are able to join the arp table with dhcp lease table and result even more devices this way, just a suggestion.

Any device that has recently communicated with the router will have an entry in the arp table (regardless of dhcp or not). I don’t automatically add all devices in the arp table as device tracker entities on purpose as the number could be huge and generally folks want to track very specific devices.
So yeah, this integration you have to manually pick the specific devices you want to track (in the configuration screen), otherwise the devices are ignored.


Separate clusters from trust zones

Summary
Currently we have a model in which a trust zone/domain contains exactly one Kubernetes cluster. With SPIFFE/SPIRE it is possible to have a trust domain that includes multiple Kubernetes clusters, as well as other types of hosts (Linux, Windows, etc.). In this case the SPIRE server(s) for the trust zone/domain would reside in one of the clusters, or even outside of the clusters.
CLI UI
New CLI commands will be added:
cofidectl cluster list
cofidectl cluster add <name> --trust-zone <trust zone> --kubernetes-cluster <cluster> --kubernetes-context <context> --profile <profile>
cofidectl cluster helm override <name> --input-file <values-file>
cofidectl cluster helm values <name> --output-file <values-file>
cofidectl cluster status <name>

Consider whether the cluster name is scoped to the trust zone or global.
Data model
A new Cluster message will be added. Some of the TrustZone fields will need to move into the Cluster message.
Consider whether a TrustZone should have a clusters field containing a list of Cluster messages. This would be convenient, but probably not how it would be represented in a database.
We could start by retaining the 1:1 trust zone/cluster mapping (as a restriction on the list length), while moving the cluster-specific information into the new field.
Current:
message TrustZone {
  string name = 1;
  string trust_domain = 2;
  optional string kubernetes_cluster = 3;
  optional string kubernetes_context = 4;
  optional proto.trust_provider.v1alpha1.TrustProvider trust_provider = 5;
  optional string bundle_endpoint_url = 6;
  optional string bundle = 7;
  repeated proto.federation.v1alpha1.Federation federations = 8;
  repeated proto.ap_binding.v1alpha1.APBinding attestation_policies = 9;
  optional string jwt_issuer = 10;
  optional google.protobuf.Struct extra_helm_values = 11;
  optional BundleEndpointProfile bundle_endpoint_profile = 12;
  optional string profile = 13;
}

Proposed:
message TrustZone {
  string name = 1;
  string trust_domain = 2;
  optional string bundle_endpoint_url = 3;
  optional string bundle = 4;
  repeated proto.federation.v1alpha1.Federation federations = 5;
  repeated proto.ap_binding.v1alpha1.APBinding attestation_policies = 6;
  optional string jwt_issuer = 7;
  optional google.protobuf.Struct extra_helm_values = 8;
  optional BundleEndpointProfile bundle_endpoint_profile = 9;
  // Consider whether this is a good idea:
  repeated Cluster clusters = 10;
}

message Cluster {
  optional string name = 1;
  optional string trust_zone = 2;
  optional string kubernetes_cluster = 2;
  optional string kubernetes_context = 3;
  optional proto.trust_provider.v1alpha1.TrustProvider trust_provider = 4;
  optional google.protobuf.Struct extra_helm_values = 5;
  optional string profile = 6;
}

Data source
New methods would need to be added to the DataSource interface:
	GetCluster(string name) (*clusterpb.Cluster, error)
	ListClusters() ([]*clusterpb.Cluster, error)
	AddCluster(*clusterpb.Cluster, tzName string) (*clusterpb.Cluster, error)
	UpdateCluster(*clusterpb.Cluster) error

Provisioning
The Provision interface is at a high enough level that it would not need to change. However implementations of the interface would need to support the new Cluster message. If we support multiple clusters per trust zone, then this would add additional complexity to the provisioning process, particularly if some of the clusters do not include any SPIRE servers.
Non-Kubernetes clusters
Not to be implemented for this issue, but while implementing the feature consider the implications for non-Kubernetes clusters.

Consider whether a TrustZone should have a clusters field containing a list of Cluster messages. This would be convenient, but probably not how it would be represented in a database.

Would the alternative be a collection ClusterID (or similar) values that disambiguate between individual cluster objects, and the TrustZone just stores those IDs? One upside of this could be migrating a Cluster from TrustZone A -> TrustZoneB would be just a case of deleting and adding an ID instead of the full object (and maps to a fairly standard data model normalisation setup too)


Typing a map over object and retain the keys

When mapping a object, TS can't retain the keys accessor.
Following example uses lodash _.mapValues, which maps a object.
var newUsers = _.mapValues({
  'fred':    { 'user': 'fred',    'age': 40 },
  'pebbles': { 'user': 'pebbles', 'age': 1 }
}, function(o) { return o.age; }); // -> _.Dictionary<number>
let ageFred = newUsers['fred']; // is number
newUsers.fred // <-- invalid because TypeScript can't retain the keys.

I can't think a way to type _.mapValues so it would retain the keys. Retaining keys requires new kind of typing capabilities for the TypeScript.
I find myself needing to retain keys in surprising many places, e.g. when uncurrying a object full of functions.

You have to use [] to access properties in a dictionary. Dot notation does not work.

@FayneAldan oh I know, that is why TS requires a new typing capablities to support retaining the keys.

Keys are still retained. Dot notation is the same as using []. In regular JS, you would use [] if you need to access a property dynamically.

@FayneAldan it can't type check the keys afterwards, that is what I mean by retaining keys.
I had a issue #3708 that was fixed also, about retaining keys. Right now it can already retain keys if the object is "fresh" and is typed with <T extends { [k: string] : number }>.
But it can't retain the keys if I want to change the key values, it would be a good addition since it would allow to uncurry a object full of actions. E.g.
interface IActionProps {
	value?: number;
}

const increaseValue = (s: IActionProps): IActionProps => () => ({
    value: s.value + 1,
});

const decreaseValue = (s: IActionProps): IActionProps => () => ({
    value: s.value - 1,
});

const defaultActions = {
	increaseValue,
	decreaseValue
}

function mapActions(o) {
	return _.mapValues(o, (v) => {
		// Do something
		return () => {
			// Do something
		}
	})
}

let actions = mapActions(defaultActions);

// Now the actions is object like this:
// actions = {
// 	increaseValue: () => { /* Does something */ },
// 	decreaseValue: () => { /* Does something */ },
// }

// And should autocomplete as increaseValue
actions.increaseValue === () => void

But it's not possible to write types for this in TypeScript because I can't retain the keys, best thing I get is actions["increaseValue"] and it does not type check, which is what I'm after.

looks like a duplicate of #1295, or at least another aspect of it.


add deep link setting, add fallback implementation #246

Issue

close #246

Overview (Required)

add deep link setting to AndoridManifest.xml
add fallback implementation to find screens

I used these 👇 commands to take videos
adb shell am start -W -a android.intent.action.VIEW -d https://droidkaigi.jp/2021/other/contributor
adb shell am start -W -a android.intent.action.VIEW -d https://droidkaigi.jp/2021/feed/blog

Links

Screenshot

Before
After

👀

Thank you for implementing and checking!


Fix multilingual site

Noticed that the site has gone out of sync and made some adjustments to it.

Great work! merged in 24d8ac1


formatting the codes

Discussed in https://github.com/sButtons/sbuttons/discussions/1573

Originally posted by khanjanSanghavi November 21, 2021
In this 3 files the code was not formatted properly

dist/sbuttons.min.css
2) package-lock.json
3)package.json

So I decided to do it to help this community grow
hope maintainers will accept it

Thank you for opening an issue with this @khanjanSanghavi but these files don't need formatting.


App fails to load camera input

Camera access is accepted, but no video output is displayed on screen

On it, sir

By the way, please what's your iOS Model? 14?

Phone model: iPhone 11 Pro
iOS Version: 16.5.1
On Sun, 6 Aug 2023 at 21:12, Tea @.***> wrote:

By the way, please what's your iOS Model? 14?
—
Reply to this email directly, view it on GitHub
https://github.com/CovenantJunior/motion-sensor/issues/26#issuecomment-1666958254,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMS4B4ODO7Z6RGCNBQU6JI3XT73CLANCNFSM6AAAAAA3GBQSS4
.
You are receiving this because you authored the thread.Message ID:
@.***>


Claims UI styling

I think this regressed recently, though we are refactoring it into inventory.

Shifted it offscreen for now.


Data regions are not refreshed synchronously

Data regions are not refreshed synchronously

When I compile the address and display name

、

You changed both address and display name?
yes，The data is not refreshed after the change

Does a manual refresh (button) work?
yes

Should be fixed in the next update. The view contents will be updated only if

The debugger session is in a 'stopped' state
Or else it will be updated the next time the debugger enters the 'stopped' state -- an info bubble will pop up

Just released the update. If you change the expression, the window will update if the program is in the 'stopped' state.
You should also see the memory window update itself with proper line spacing as soon (tiny delay) as you change the font size.


add ForScience KSP 1.2.x version

this was updated for KSP 1.2.x but apparently nobody updated the
metadata.
also updated the license per the link on the top post in the
forum thread:
http://forum.kerbalspaceprogram.com/index.php?/topic/107803-12-forscience-v141-your-science-autopilot/&

Thanks for the heads-up. I think we might move this to automated discovery so we don't miss the next update.


Make the database feature a package

The provider database is dynamically imported based on the db config. It is designed to allow different database engines as long as an interface is provided. This feature should be pulled into its own package.

Nice to have, moved to low priority. Needs AC to move into backlog


Using dapper built in methods with query builders

before this package i was using Query multi mapping in the following manner:
connection.QueryAsync<BookingViewModel, UserViewModel, OperatorViewModel, BookingViewModel>(
                sqlQuery,
                (booking, user, bboperator) =>
                {
                    booking.BookedByUser = user;
                    booking.BookedByOperator = bboperator;
                    return booking;
                },
                parms,
                splitOn: "BookingId, UserId, OperatorId");

with the queryBuilder i would like to use the same with dapper support:
queryBuilder.QueryAsync<BookingViewModel, UserViewModel, OperatorViewModel, BookingViewModel>(
                (booking, user, bboperator) =>
                {
                    booking.BookedByUser = user;
                    booking.BookedByOperator = bboperator;
                    return booking;
                },
                splitOn: "BookingId, UserId, OperatorId");

Is it something possible in this package?

duplicate of https://github.com/Drizin/DapperQueryBuilder/issues/3


Refresh token balance after token send

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

39.0625 PSF tokens rewarded. TXID:
2cd6473188b6a6ce6a821235a88cb7fc78002508e7a5b0ace49caf7956de7dfc


Consider seperating wallet(+ KOS), miner and WASM bindings from codebase

Keeping the main codebase clean as much as possible could be good for security and stability reasons.

This has been discussed in-depth. There are a number of crates that are not a part of the main daemon and framework pipeline, so they don't affect stability or security of the core daemon.
WASM bindings are an integral part of the framework as they expose internal consensus functionality. It is not possible to move them out of the project due to reference dependencies. In fact to address this problem we had to scatter WASM bindings across all respective modules. (kind of hard to explain, but feel free to ping me on discord if u want a more detailed explanation).
KOS and CLI are internal tools used for testing, especially in the context of the framework functioning in the native and in the web+NodeJS environments.
Wallet framework is complimentary to the consensus layer. Due to performance considerations Rusty Kaspa is unable to provide certain information such as transaction information. It only provides UTXO information. The wallet framework provides tools that re-integrate this information within a context of the client. (I.e. unlike base layer that provides UTXO changes, the wallet framework provides transaction data - you receive not UTXOs but transactions made up of UTXOs). Send yourself a transaction made out of multiple UTXOs and you will see the issue I am describing. Most of the wallets treat UTXOs as transactions, which is not correct. Also the wallet framework provides Transaction Generator module that automates transaction creation for any number of UTXOs, which is difficult for anyone to do properly.
Last, but not least, within the context of a single workspace, all changes to the framework, consensus and RPC are reflective. Meaning that if developers make any changes to any data structures the workspace fails to compile as a whole, allowing us to address changes that would otherwise be isolated and will be cascading in nature, meaning that changes made in consensus framework could render dependency projects inoperable until they are fixed. I have a number of external crates and changes to the framework result in them breaking on regular basis.
There is no miner in the framework. The PoW-related functions are integral to consensus.
If you have any specific issues or concerns regarding the reasons you are asking about this, please be more specific. Security and stability of the framework as a whole is extremely important, however it is also important to understand that there are layers to the framework where the consensus layer is an isolate in these regards (at the same time these considerations apply to the framework as a whole). There are two key elements to the repository: the workspace and crates within this workspace. Daemon and consensus crates albeit located in the same workspace do not interact with other framework crates, but rather use them as dependencies.


Can't run pods on kubernetes 1.4.6 hosts with docker 1.10

Rancher Version:
v1.2.0-pre4-rc8
Docker Version:
1.10.3
OS and where are the hosts located? (cloud, bare metal, etc):
Ubuntu 14.04
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
single node rancher
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Kubernetes 1.4.6
Steps to Reproduce:

Install Rancher rc8
Wait until microservices are up and running
deploy kubernetes 1.4.6
try to deploy and pod

Results:
Pods are failed to run on hosts:
      /var/www/html from wordpress-ephemeral-storage (rw)
    Environment Variables:
      WORDPRESS_DB_PASSWORD:    wordpress
Conditions:
  Type          Status
  Initialized   True
  Ready         False
  PodScheduled  True
Volumes:
  wordpress-ephemeral-storage:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
  default-token-6kkcv:
    Type:       Secret (a volume populated by a Secret)
    SecretName: default-token-6kkcv
QoS Class:      BestEffort
Tolerations:    <none>
Events:
  FirstSeen     LastSeen        Count   From                                                            SubobjectPath  T
ype             Reason          Message
  ---------     --------        -----   ----                                                            -------------  -
------- ------          -------
  31m           31m             1       {default-scheduler }                                                           N
ormal           Scheduled       Successfully assigned wordpress to hussein-docker110-10acre-3.c.rancher-qa.internal
  31m           1s              889     {kubelet hussein-docker110-10acre-3.c.rancher-qa.internal}                     W
arning          FailedSync      Error syncing pod, skipping: failed to "SetupNetwork" for "wordpress_default" with Setup
NetworkError: "Failed to setup network for pod \"wordpress_default(23bd2df2-ade6-11e6-a65d-ae240b31d4cb)\" using network
 plugins \"cni\": netplugin failed but error parsing its diagnostic message \"\": unexpected end of JSON input; Skipping
 pod"

Rancher version: v1.2.0-pre4-rc9
Tested Kubernetes 1.4.6 and i was able to deploy pods successfully.


[Firmware] Use async wifi

This simultaneously fixes the broken wifi code, and overhauls it to use embassy-net. This is a WIP.

I have tested such that it works on wifi on esp32c3. @ImUrX any chance you can test esp32?
Also, I was unable to get bmi160 to work, but mpu6050 works fine. However, bmi160 worked in the past. I'm not sure what changed. It could just be a hardware issue on my end, perhaps you could test this too?


Replace standard alert and confirm with BootstrapDialog

Before

After

I was waiting for CI to pass. Ready for review

LGTM, look better than default alerts/confirm box.

I prefer the browser alert to this one.
The title box is quite useless here

@corneadoug we can remove the title box if necessary. Even in the standard alert/confirm there is nothing in the title box. IMHO the standard ones are not considered as good UX

We can always change the style later.
Could you please update the license for BootStrapDialog here:
https://github.com/apache/incubator-zeppelin/blob/b5e2e62f239d6b1b625add16405e3a302e8ff060/zeppelin-distribution/src/bin_license/LICENSE

Thanks, LGTM

Cool! LGTM
2015년 12월 9일 (수) 오후 5:44, CORNEAU Damien<EMAIL_ADDRESS>작성:

Thanks, LGTM
—
Reply to this email directly or view it on GitHub
https://github.com/apache/incubator-zeppelin/pull/501#issuecomment-163151792
.

Tested and LGTM.
Merging it into master.

Sorry to barge in a closed bug.
Neither the cancel nor the OK button has focus on them. Would be nice to have either pre-focussed.

Neither the cancel nor the OK button has focus on them. Would be nice to have either one pre-focussed.
@gauravkumar37 thanks for the feedback. I've created a new PR (#532) to address this issue. Will focus OK by default and enable Esc key for cancel popup. PR is currently WIP.

Thanks @r-kamath, will check that PR out.


Bot won't leave voicechannel after playback

This bot was working fine a few days ago, but now the bot wont leave the voicechannel after playback, and subsequent attempts at playing files/videos after the first one wont work at all.
Here is part of the code i use;
mybot.leaveVoiceChannel(message.author.voiceChannel);
	mybot.joinVoiceChannel(message.author.voiceChannel, function(error, voice) {
		//console.log(message.author+" aka <"+message.author.username+"> attempted to play this url, <"+para+">");
		mybot.voiceConnection.playFile(para, soundOptions, function(error, intent) {
			intent.on("end", function() {
				mybot.leaveVoiceChannel(message.author.voiceChannel);
			});

		if (error) {
			mybot.voiceConnection.stopPlaying();
			mybot.leaveVoiceChannel(message.author.voiceChannel);
			console.log(error);
		}
	});
});

The bot joins the voicechannel of the user who sent the command, and will join any voicechannel regardless of whether this bug is happening.
I also have gotten this error;
Error: No voice server details within 10 seconds
    at Timeout._onTimeout (C:\Users\Win 8 - Steer\node_modules\discord.js\lib\Client\InternalClient.js:397:14)
    at tryOnTimeout (timers.js:224:11)
    at Timer.listOnTimeout (timers.js:198:5)

They addressed this is the API updates on the Discord API server. Hotfix is coming out tonight.

Oh ok thank you, will close this issue


Pin dependencies

I'm not sure if this is something you want to merge or not - we had trouble at one point with an update of re2, so went and and pinned all the dependencies to known good versions for the sake of stability/predictability.

I think that's a good idea 👍


chore: fixed github icon color

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 80.706%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
7312

Relevant Lines:
8262

💛  - Coveralls


Grid layout

Hello, a previous question asked for a way to display the full image in the grid view. The response was to edit the lsf. I'd like to know more about how this can be done when deploying to azure? I'd also like to be able to see mask annotations in the grid view. Thanks, kate

@kateob Hello,

Could you please refer to the response?

How this can be done when deploying to azure
In a nutshell:
2.1. You have to go here - https://github.com/heartexlabs/label-studio-frontend, download this repo, fix the code you need (you should be familiar with React).
2.2. Make a new build of LS.
2.3. Then you need to clone LS - https://github.com/heartexlabs/label-studio - insert your build into label_studio/frontend/dist/lsf.
2.4. Build your own docker image and upload it to dockerhub.
2.5. Edit https://github.com/heartexlabs/label-studio/blob/develop/azuredeploy.json#L131 and specify your dockerhub account and LS image instead of heartexlabs/label-studio.

It's a super hard task, you should be super advanced in React


Explain native types and how they relate to is repr

The problem
The native type declaration is not documented. I have asked this question in SO
Suggestions
Improve the  is repr subsection with these, and maybe add them to the native types page. This is related to #2142 , but is probably more general.

According to the answer, it's compiler dependent. So no need to document it for the time being. I'm closing this issue.


Why auto selection not redirection at begining?

Hi,
self.carousal.defaultSelectedIndex = 4
self.carousal.didSetDefaultIndex = true
I have added above code, but its not redirecting anything, it is in ViewDidAppear method .
What is the issue? this is not working in example2 of your sample project?
My side i am trying with Drag view and assign a class, then IBOutlet, the redirection only not working at beginning.
Any help would be appreciated, Thanks in advance.

Ignore this question, i am able to fix it by calling below
self.carousal .selectItem(9, animated: true)


Empire start error

Empire Version
2.0
OS Information (Linux flavor, Python version)
Kali 2017.1 rolling
Expected behavior and description of the error, including any actions taken immediately prior to the error. The more detail the better.
After installed and trying to run script gives an error!
Screenshot of error, embedded text output, or Pastebin link to the error
root@a7f99h3kk5j69d77v3v5-android:~/Empire# ./empire
Traceback (most recent call last):
  File "./empire", line 1294, in <module>
    main = empire.MainMenu(args=args)
  File "/root/Empire/lib/common/empire.py", line 75, in __init__
    (self.isroot, self.installPath, self.ipWhiteList, self.ipBlackList) = helpers.get_config('rootuser, install_path,ip_whitelist,ip_blacklist')
TypeError: 'NoneType' object is not iterable
root@a7f99h3kk5j69d77v3v5-android:~/Empire#

Any additional information

you need to run ./reset.sh from the setup directory. Warning: this will clear the database.

Worked ..thanks a lot!


pip install numpy not work in pyenv install python 2.7.8

I have problem with pip installed numpy  in pyenv installed python2.
Details:
System: Ubuntu 14.04
Python: pyenv install 2.7.8
Python Env: pyenv virtualenv 2.7.8 test_env
Numpy: pip install numpy
The error is following:
$ python
Python 2.7.8 (default, Jan  7 2016, 17:45:25)
[GCC 4.8.4] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/shixd/.pyenv/versions/test_env/lib/python2.7/site-packages/numpy/__init__.py", line 180, in <module>
    from . import add_newdocs
  File "/home/shixd/.pyenv/versions/test_env/lib/python2.7/site-packages/numpy/add_newdocs.py", line 13, in <module>
    from numpy.lib import add_newdoc
  File "/home/shixd/.pyenv/versions/test_env/lib/python2.7/site-packages/numpy/lib/__init__.py", line 8, in <module>
    from .type_check import *
  File "/home/shixd/.pyenv/versions/test_env/lib/python2.7/site-packages/numpy/lib/type_check.py", line 11, in <module>
    import numpy.core.numeric as _nx
  File "/home/shixd/.pyenv/versions/test_env/lib/python2.7/site-packages/numpy/core/__init__.py", line 14, in <module>
    from . import multiarray
ImportError: /home/shixd/.pyenv/versions/test_env/lib/python2.7/site-packages/numpy/core/multiarray.so: undefined symbol: PyUnicodeUCS4_AsUnicodeEscapeString

I have found out that when pip was installing numpy, it only took 3-5 seconds, so I think pip is using pre-built numpy.
I solve the problem by manually install numpy with python setup.py install.
Why does pip  not work in my case? I don't have this problem before. (I am new in using pyenv)
How to make pip work then?

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/29762605-pip-install-numpy-not-work-in-pyenv-install-python-2-7-8?utm_campaign=plugin&utm_content=tracker%2F282009&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F282009&utm_medium=issues&utm_source=github).

Build problem with specific package isn't an issue of pyenv.


Make the + and options button in the chat view white not black

Hello, not sure if you were still looking to do this but I've recently done this my app! So try this code:
    Drawable iconDrawable = ContextCompat.getDrawable(getActivity(), R.drawable.your_drawable);

    iconDrawable = DrawableCompat.wrap(iconDrawable);
    DrawableCompat.setTint(iconDrawable, ContextCompat.getColor(getActivity(), android.R.color.white));

Then set the icon:
     item.setIcon(iconDrawable);


Any plan to include tetrahedral interpolation

Hi, quick question. Any plan to include tetrahedral interpolation?

No. Why you need it?
Currently trilinear interpolation is used with following performance on one core of Intel Core i5-8279U:

Thanks for sharing this, very good to know! I am thinking about mobile deployment. Not sure if there are any benchmark there. Also, speed aside, I am interested in the effects of different interpolation methods on visual quality (banding, block artifacts) on both images and videos.


Documentation forgets to refer to bdb 4.8?

In Step 2 of the HOWTO.md,
$ sudo apt-get install make g++ python-leveldb libboost-all-dev libssl-dev libdb++-dev pkg-config libevent-dev
If I did it like that then I would end up with bdb 5+, wouldn't I?
Instead I believe the user should add the bitcoin ppa and install bdb 4.8 from it.

Oh, apparently it just affects the wallet.  Would it not affect blockchain bootstrap files made then?

newer versions of bitcoin core (0.13.x) require  libdb+ it seems, not sure what's wrong with having bdb 5+.


multithreading issues with 0.9.10

Hi!
I'm experiencing multithreading issues with version 0.9.10.
With two threads accessing the same jar file i get the following Log Messages:
DEBUG Thread-1 2015-07-15 11:26:33,136 org.reflections.Reflections - going to scan these urls:
jar:file:/path/to/jar/myjar.jar!/
DEBUG Thread-2 2015-07-15 11:26:33,138 org.reflections.Reflections - going to scan these urls: ...
jar:file:/path/to/jar/myjar.jar!/
INFO Thread-1 2015-07-15 11:26:33,289 org.reflections.Reflections - Reflections took 153 ms to scan 3 urls, producing 207 keys and 529 values
Thread-2 crashes with this stack:
java.lang.IllegalStateException: zip file closed
at java.util.zip.ZipFile.ensureOpen(ZipFile.java:634)
at java.util.zip.ZipFile.access$200(ZipFile.java:56)
at java.util.zip.ZipFile$1.hasMoreElements(ZipFile.java:487)
at java.util.jar.JarFile$1.hasMoreElements(JarFile.java:241)
at org.reflections.vfs.ZipDir$1$1.computeNext(ZipDir.java:30)
at org.reflections.vfs.ZipDir$1$1.computeNext(ZipDir.java:26)
at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143)
at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138)
at org.reflections.Reflections.scan(Reflections.java:240)
at org.reflections.Reflections.scan(Reflections.java:204)
at org.reflections.Reflections.(Reflections.java:129)
at org.reflections.Reflections.(Reflections.java:170)
at org.reflections.Reflections.(Reflections.java:143)
The ZipDir seems to be created in DefaultUrlTypes.jarUrl.createDir(URL):
return new ZipDir(((JarURLConnection) urlConnection).getJarFile());
but sun.net.www.protocol.jar.JarURLConnection.getJarFile() uses (or may use) a cache:
this.jarFile = factory.get(getJarFileURL(), getUseCaches());
In my case both threads get the same instance of JarFile, and after the first thread has closed the ZipDir (which closes the JarFile) in
org.reflections.Reflections.scan(URL):260
the second one gets the IllegalStateException.
Cheers,
Christian

A fix could be to disable JarURLConnection's caching in DefaultUrlTypes.jarUrl.createDir(URL):
if (connection instanceof JarURLConnection) {
JarURLConnection jarURLConnection =  (JarURLConnection) connection;
jarURLConnection.setUseCaches(false);
return new ZipDir(jarURLConnection.getJarFile());
}

A fix could be to disable URLConnection's caching in DefaultUrlTypes.jarUrl.createDir(URL):
        URLConnection urlConnection = url.openConnection();
        urlConnection.setUseCaches(false);
        if (urlConnection instanceof JarURLConnection) {
                return new ZipDir(((JarURLConnection) urlConnection).getJarFile());
        }

I got a similar issue !

I can see this in our development environment (Windows) but not in our target environment (Linux).
Quite easy to reproduce using two threads.
Problem does not exist in 0.9.9.

I can reproduce the issue with reflections in a wildfly environment.

Reproduced here as well, both on OSX and RHEL. For some reason RHEL doesn't throw the exception - it just hangs or silently fails (not sure which). Our workaround is to use v0.9.9.

I think I got hit with the same problem. While using a Play Framework application that uses the Katharsis Library (which in turn uses reflections). I downgraded to 0.9.9 (some other dependency updated to 0.9.10 and the problem started)

As pointed out in the first comment, this is indicative of a single java.util.zip.ZipFile instance being used in multiple threads.
This is not only a problem when one thread closes the ZipFile, which gave rise to this bug report, but also ZipFile actually has an internal lock that only grants access to one thread at a time (so Reflections is not making optimal use of CPU resources).

I got the same problem with 0.9.11

Same for us. Problem is presented in 0.9.11 also. Version 0.9.9 is working OK. We use it in maven mojo and when running parallel build, exception happens.

@LuboVarga My apologies to the author of Reflections for the promotion of my own project, but since this bug has been open for almost 2 years now... if this bug is a show-stopper for you, you could try FastClasspathScanner instead. It opens one ZipFile instance per zipfile per thread, so it does not suffer from this problem.

I encounter the same problem version 0.9.11 on the window platform in multi-threads env.

the regression was introduced with this PR: https://github.com/ronmamo/reflections/pull/57
i'm working on a patch

@andreabertagnolli the solution is to create a separate ZipFile instance for each thread -- this is what I had to do in FastClasspathScanner, which also does multithreaded scanning.
The exception on close issue is not the only problem here: without creating one ZipFile instance per thread, multithreading doesn't even speed up the scanning process, because all the methods within ZipFile are locked on a per-zipfile basis, so only one thread can access a given jar at one time.

You're right, but my PR is just a fix, it simply avoids the exception.
I never thought about performance, it's not the scope of this issue ;)
Il mar 7 nov 2017, 04:17 Luke Hutchison<EMAIL_ADDRESS>ha
scritto:

@andreabertagnolli https://github.com/andreabertagnolli the solution is
to create a separate ZipFile instance for each thread -- this is what I
had to do in FastClasspathScanner, which also does multithreaded scanning.
The exception on close issue is not the only problem here: without
creating one ZipFile instance per thread, multithreading doesn't even
speed up the scanning process, because all the methods within ZipFile are
locked on a per-zipfile basis, so only one thread can access a given jar at
one time.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ronmamo/reflections/issues/81#issuecomment-342363343,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AILIbq8csKPzDv2gGYuijlO_yiAfVyHnks5sz8vdgaJpZM4FY8bW
.

for the context, accessing the same jar concurrently from multiple threads sounds like something wrong is done. the better approach is to have one reflections instance scanning only once, with all relevant scanners and configuration. parallel scanning means each url scan goes in different thread, so there should not be contention.
this pr merged however, as it solves this misuse - correct me if I'm wrong.
@lukehutch promoting your open source is totally acceptable! sharing goes both ways, this is open source : )

@ronmamo Thanks for the pragmatic attitude :-)
@ronmamo @andreabertagnolli the PR should fix the issue, but at the cost of unzipping the same jars-within-jars multiple times, once per thread.
With the situation before this PR, the first thread to finish scanning would close the ZipFile, then other threads would not be able to complete their scanning of the jar, because the ZipFile instance was shared. The jar-within-jar was only extracted once, but only one thread could actually read from the jar at a time anyway (due to locking). With the new PR, parallel scanning is possible, but work is duplicated.

@lukehutch why would you scan the same jar twice and/or concurrently, again?

@ronmamo I was under the impression that you were parallelizing the scanning work within a given jarfile (in this case, for extracting jars from within jars, e.g. in the JBoss VFS, and assigning a different scanning thread to each nested jar (or simply assigning different threads to scan each classfile within a jar). Isn't this what was triggering the exception, when the first thread to finish scanning files in a jar closed the jar, triggering an exception in the other threads?

@ronmamo Please let us know when the patch will be released with the fix. We are stopping due to this issue.

I posted an explanation to a related bug about how to access ZipFile in a multithreaded environment. I'll repost here, since a lot of things link to this bug.
--
If you want multiple threads to read from the same zipfile in a scalable way, you must open one ZipFile instance per thread. That way, the per-thread lock in the ZipFile methods does not block all but one thread from reading from the zipfile at one time. It also means that when each thread closes the ZipFile after they're done reading, they close their own instance, not the shared instance, so you don't get an exception on the second and subsequent close.
Protip: if you really care about speed, you can get more performance by reading all the ZipEntry objects from the first ZipFile instance, and sharing them with all threads, to avoid duplicating work in reading ZipEntry objects for each thread separately. A ZipEntry object is not tied to a specific ZipFile instance per se, ZipEntry just records metadata that will work with any ZipFile object representing the same zipfile that the ZipEntry came from.

I had the same problem with version 0.9.11. After updating to 0.9.9 everything works fine for me!

We are having this problem in 0.9.11

    <dependency>
        <groupId>org.reflections</groupId>
        <artifactId>reflections</artifactId>
        <version>0.9.12</version>
    </dependency>

Invocation of init method failed; nested exception is java.lang.IllegalStateException: zip file closed
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1762)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:593)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:515)
at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:320)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:318)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:849)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:877)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:549)
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:142)
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:775)
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:316)
at com.ruibo.sys.web.Application.main(Application.java:37)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48)
at org.springframework.boot.loader.Launcher.launch(Launcher.java:87)
at org.springframework.boot.loader.Launcher.launch(Launcher.java:50)
at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:51)
Caused by: java.lang.IllegalStateException: zip file closed
at java.util.zip.ZipFile.ensureOpen(ZipFile.java:686)
at java.util.zip.ZipFile.access$200(ZipFile.java:60)
at java.util.zip.ZipFile$ZipEntryIterator.(ZipFile.java:499)
at java.util.zip.ZipFile.entries(ZipFile.java:552)
at java.util.jar.JarFile.access$001(JarFile.java:71)
at java.util.jar.JarFile$JarEntryIterator.(JarFile.java:250)
at java.util.jar.JarFile$JarEntryIterator.(JarFile.java:247)
at java.util.jar.JarFile.stream(JarFile.java:279)
at org.reflections.vfs.ZipDir.lambda$getFiles$2(ZipDir.java:21)
at org.reflections.Reflections.scan(Reflections.java:260)
at org.reflections.Reflections.scan(Reflections.java:216)
at org.reflections.Reflections.(Reflections.java:137)
at com.ruibo.canal.spring.event.AllTablePublicColumnSyncUpdateApplicationListener.afterPropertiesSet(AllTablePublicColumnSyncUpdateApplicationListener.java:113)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1821)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1758)

I'm also having this issue with 0.9.12. Switching back to 0.9.9 solved the problem.

Are there any plans to release this fix in a new release?

I'm also having this issue with 0.9.12. Switching back to 0.9.9 solved the problem.

thx


OCM-8848 | test: automate id:74402,74403,73731 upgrade/delete roles with attaching arbitrary policies

OCM-8848 | test: automate id:74402,74403,73731 upgrade/delete roles with attaching arbitrary policies
Logs: https://privatebin.corp.redhat.com/?f8e9c754f600eea1#96YYCSwUsQmUKn7d7V6knUKbTQ2v5S1Qc2uMY8ih8KFf

/test test

/test coverage

/test test

/test test

@xueli181114 Updated in latest commit? Could you help review again?

/test e2e-presubmits-images

/test e2e-presubmits-images

@xueli181114 All tests are passed and your comment has also update. Could you help take a look again?Thanks

/lgtm

@ciaranRoche Could you help review then approve it?Thanks.

/test coverage

/test coverage

@ciaranRoche Could you help review again, new commit has updated with your comments.

/lgtm

/approve


An error occurs when creating/deleting several storage accounts at the same time

OS: Mac/Linux
Build Version: v0.15.4-alpha.0
Repro Steps:

Create several storage accounts at the same time, such as create 3 storage account at the same time.
Check whether no error occurs when creating several storage accounts at the same time.

Expect:
No error occurs when creating several storage accounts at the same time.
Actual:
An error occurs when creating several storage accounts at the same time.

More Info:

Another error occurs when deleting several storage accounts at the same time.

We are not sure if this issue related to the network speed.

Certainly caused by #1310 😢


disk: sdhc: spi: leave SPI CS GPIO handling to the SPI controller driver

Leave the SPI CS GPIO handling to the SPI controller driver and make SPI CS GPIO optional for SDHC disk access via SPI.
The SPI SDHC implementation relies on SPI_HOLD_ON_CS so we need to explicitly release the SPI controller driver after ending transmissions to force the CS line to be de-asserted.
Fixes #27444.
Signed-off-by: Henrik Brix Andersen<EMAIL_ADDRESS>

Initial tests on my STM32F407 look positive, I haven't done any high load tests yet.


Movie start time doesn't display correctly

Upon entering a start time of 7pm when creating a new movie run, it displays on the movie list as 2am. Curiously, this only happens for me on the Heroku/Firebase deployed site, the dev version displays correctly.

After exhaustive console logs, I believe the issue lies with the server side code. Some sort of M-Lab discrepancy with Moment.js or the like?


Mirror network

From what I can tell, there are no plans to distribute the index or the packages across a mirror network. Maybe you have plans which are not documented yet, but in case you don't, here are some arguments to use a mirror network:
pros

availability of the index in case of outages
availability of packages regardless of the original project repository
archival of old versions
avoiding SPOF (Hackage down, what do we do?)
distributing the load across a mirror network like CPAN and FLOSS OSes do
it's a model which has been used successfully by major projects for decades
depending on from where you access the network, a specific mirror may be the only way of using remote packages
maintaining organization wide local mirrors for dev teams
it's an important provision for scalability
allows Cargo to automatically fall back to other mirrors if a selected mirror is down
given widespread use of Rust, many projects' CI setups are going to rely on it, and for that availability is critical

cons

A configured mirror may lag behind master instance, but this can also be of advantage, and if you always need the latest the moment it's published, you can configure to prefer a certain mirror.

how

the same way as a BSD, a Linux distro, or CPAN
ideally, support incremental (binary delta) update of index and/or packages

@tuncer Now that crates.io actually exists, feel free to continue this ticket over at https://github.com/rust-lang/crates.io/issues

This requires changes in both cargo and the index+archive, so I'm not sure it's more suitable to file a new ticket over there.
Summary:

Uploads go to master.
Master is used to sync mirrors.
Index is updated and synced.
Clients must preferably use mirrors or a redirector.
A paid-for CDN can be one of many mirrors.
Index needs to be more like Fedora's or Debian's (delta updates, etc.).
archive of all published releases
git is unsuitable as index storage. What we need is the history of a crate's versions, not the history of index changes. The index points to crates, and for each crate to N releases.
It's much more likely to get free mirrors like FreeBSD, Debian, and CTAN than getting sponsorship for a single super CDN.
Mirrors mean master can go down and clients can still fetch (only r/o operations), and only index changes will be affected.
Naturally, the index is also mirrored together with the archive.


Implemented: Shift-JIS encoding conversion for export packed orders feed.

Related Issues

Closes #
Short Description and Why It's Useful

Added support to convert the encoding into Shift-JIS format for export packed orders feed when user locale is Japanese.
Screenshots of Visual Changes before/after (If There Are Any)

IMPORTANT NOTICE - Remember to add changelog entry
Contribution and Currently Important Rules Acceptance

[x] I read and followed contribution rules

Changes verified and working fine in release v2.4.3. File type shown is us-ascii which is expected.


Pluggable Components Quickstart

Description:
This issue is to track work for the Pluggable Component quickstart
Ideally we'd like to have a quickstart created for Pluggable Components targeted for 1.9. For this quickstart, we can utilize the early Pluggable Component demo as a starting place and contribute that back as a quickstart for users.
Requirements: Quickstart covers

[ ] Perquisites needed to get started
[ ] Process of setting up environment
[ ] Process of invoking a pluggable component
[ ] Entire quickstart packaged as github template. Something similar to this dapr-pubsub-servicebus quickstart
[ ] Only language used in demo will need to be supported (i.e., .NET Redis demo). We'll release other quickstart languages in later versions. This is just to get something out there that users can interact with and get an understanding of pluggable components works

@nyemade-uversky is this about showing how to use an example pluggable component, or how to write one?  I feel like it may be too narrow of a topic to dedicate a quickstart to writing one.  And for using an actual pluggable component, I would see that being doc'd right next to the component itself.

Pluggable components are just components in usage so I would not have this in the Quickstarts. Suggest having this in each SDK per the pluggable component SDKs. This issue can be closed.

Closing since this is a per Pluggable SDK topic.


[BUG] [v1.0.x] PostgreSQL 10 yum repository not available

Describe the bug
PostgreSQL 10 reached EOL a few months ago.
Now RHEL repositories for PostgreSQL 10 have been removed and are no longer available.
https://download.postgresql.org/pub/repos/yum/
Epicli v1.0.x is affected.
It fails executing the download-requirements.sh script and trying to add an non-existent repository:
Adding repository: postgresql-10", "Executing: rpm --import https://download.postgresql.org/pub/repos/yum/RPM-GPG-KEY-PGDG", "https://download.postgresql.org/pub/repos/yum/10/redhat/rhel-7Server-x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found

How to reproduce
Steps to reproduce the behavior:

execute epicli init ... (with params)
edit config file
execute epicli apply ...

Expected behavior
A clear and concise description of what you expected to happen.
Config files
If applicable, add config files to help explain your problem.
Environment

Cloud provider: [AWS | Azure | All | None]
OS: [e.g. Ubuntu 20.04.3 LTS, you can use cat /etc/os-release]

epicli version: [epicli --version]
Additional context
Add any other context about the problem here.

DoD checklist

Changelog

[ ] updated
[ ] not needed

COMPONENTS.md

[ ] updated
[ ] not needed

Schema

[ ] updated
[ ] not needed

Backport tasks

[ ] created
[ ] not needed

Documentation

[ ] added
[ ] updated
[ ] not needed

[ ] Feature has automated tests
[ ] Automated tests passed (QA pipelines)

[ ] apply
[ ] upgrade
[ ] backup/restore

[ ] Idempotency tested
[ ] All conversations in PR resolved

Fixed in #3390


Sagmor central configuration

@sagmor I have added specs here to your branch. Will merge this as soon as, it is green.

Fixes #127 @sagmor thank you for your contributing to Invoker.

You beat me on the specs.
Thanks for the merge, and it's a pleasure to help.


Analyze CPI Workshop Survey

Following the CPI Workshop survey captured in Ticket #242, this ticket documents the analysis of the results.

[x] Send first round of responses to key stakeholders (requested in March 3 Sprint Review)
[x] Analyze responses
[x] Create report & disseminate

Notes:

Survey close date: March 18.

Report can be found in Scrum Team/Files/Research/CPI-Survey.html
https://bcgov.sharepoint.com/:u:/r/teams/00608-ScrumTeam/Shared Documents/Scrum Team/Research/CPI-Survey.html?csf=1&web=1

Thank you @elliottSlee ! So fascinating to see the results from the survey.


perf: lazy load not found route

#415  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @davidlj95 and the rest of your teammates on  Graphite


Invalid endpoint URL for topic unsubscribe

This relates to messaging package, where topic unsubscribe action uses wrong op. This causes incorrect endpoint to be hit, i.e. iid/v1:batchAdd instead of iid/v1:batchRemove.

Thanks for pointing this out. Will fix for next release.


Improve wording for private updates

Update form

Should be:

Check this to limit access to the content of this update to the target audience only

Update

Based on the notificationAudience, this should be:

FINANCIAL_CONTRIBUTORS

This update is for contributors only

COLLECTIVE_ADMINS

This update is for hosted collective admins only

Otherwise:

This update is for members only

@Betree
Kindly assign this task to me, allowing me to engage in meaningful work and make valuable contributions to the project.

How to check if the update is private or not?
@Betree

How to check if the update is private or not?
@Betree

They have a "Private update" tag, as in the 2nd screenshot of the issue's body

How to check if the notificationAudience is FINANCIAL_CONTRIBUTER or COLLECTIVE_ADMINS or All
@Betree

You select that when you create an update, at the 2nd step, before publishing, in the drop-down next to "Who should be notified"


Weeb Central webview/open in browser while inside a chapter appends unnecessary formatting in url which results in a website that u can't interact with to view comments, next chapter etc.

Source information
Weeb Central 1.4.5
Source language
English
Steps to reproduce

Open any chapter of any manga
Open in webview or browser

Expected behavior
Regular website of chapter without formatting should open.
Actual behavior
Formatted website of chapter opens which consists of manga pages only with no way to do anything else.
Mihon/Tachiyomi version
0.17.0
Android version
Android 14
Other details
Example:
https://weebcentral.com/chapters/01JD2G6FZWE7NPKFNWWPTSFZJW/images?is_prev=False&reading_style=long_strip
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.15.3.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Add a :+1: reaction to issues you find important.

It's not about reading in browser. It's a fallback for reading in case app refuse to load. I also like reading comments from time to time for on going manga and you can only do it in webview. I'm not trying to annoy you by reporting this. Other extensions have normal url, so i assumed it's a bug. If you consider this as correct behaviour, then so be it. I just liked the soon to be deprecated mangasee and wanted the new weebcentral to work correctly.