problem with wildcard certificates

I tried to run the following command:
docker run --rm \
  -e PLUGIN_SOURCE=target/mcMMO.jar \
  -e PLUGIN_TARGET=/mcmmo/mcMMO.jar \
  -e PLUGIN_BUCKET=artifacts \
  -e AWS_ACCESS_KEY_ID=xxx \
  -e AWS_SECRET_ACCESS_KEY=yyy \
  -e S3_ENDPOINT=https://storage.xxx.yyy \
  -v /home/andy/git/mcmmo_git:/home/andy/git/mcmmo_git \
  -w /home/andy/git/mcmmo_git \
  woodpeckerci/plugin-s3

and got this error message:
time="2021-10-20T11:25:14Z" level=error msg="Could not upload file" bucket=artifacts error="RequestError: send request failed\ncaused by: Put \"https://artifacts.storage.xxx.yyy/mcmmo/mcMMO.jar/mcMMO.jar\": x509: certificate is valid for *.xxx.yyy, not artifacts.storage.xxx.yyy" name=mcMMO.jar target=/mcmmo/mcMMO.jar/mcMMO.jar
time="2021-10-20T11:25:14Z" level=fatal msg="RequestError: send request failed\ncaused by: Put \"https://artifacts.storage.xxx.yyy/mcmmo/mcMMO.jar/mcMMO.jar\": x509: certificate is valid for *.xxx.yyy, not artifacts.storage.xxx.yyy"

It seems like there's a problem with the wildcard certificate. The certificate comes from letsencrypt. The endpoint is a minio instance behind an Nginx with reverse proxy.

I added PLUGIN_PATH_STYLE=true to my command and now it works fine


Support rehydration priority setting for storage acount blob In Track 2

Customer feedback requires to support the setting of rehydration priority for the storage blob in the CLI.
According to the rest API and parameters provided by @blueww that need to be supported:

https://docs.microsoft.com/en-us/rest/api/storageservices/copy-blob x-ms-access-tier, x-ms-rehydrate-priority
https://docs.microsoft.com/en-us/rest/api/storageservices/put-blob x-ms-access-tier
https://docs.microsoft.com/en-us/rest/api/storageservices/put-block-list x-ms-access-tier
https://docs.microsoft.com/en-us/rest/api/storageservices/set-blob-tier x-ms-access-tier, x-ms-rehydrate-priority

add to S171


added a slightly-fancy prompt

added slightly fancy prompt with path on the left and datetime on the right
todo - add some prompt configurability
todo - fix 'attack of the clones' - replace with &str
ran clippy, moved unwrap() to expect()
had to revert some of the previous code, specifically the position()?; in read_line and on buffer_paint, in order to get the prompt to function appropriately
have only tested on windows, crossing my fingers on mac and linux :)

would eventually like to get to this level of functionality (from fish shell)
/// This is the main function for the screen putput library. It is used to define the desired
/// contents of the screen. The screen command will use its knowledge of the current contents of the
/// screen in order to render the desired output using as few terminal commands as possible.
///
/// \param s the screen on which to write
/// \param left_prompt the prompt to prepend to the command line
/// \param right_prompt the right prompt, or NULL if none
/// \param commandline the command line
/// \param explicit_len the number of characters of the "explicit" (non-autosuggestion) portion of
/// the command line
/// \param colors the colors to use for the comand line
/// \param indent the indent to use for the command line
/// \param cursor_pos where the cursor is
/// \param pager the pager to render below the command line
/// \param page_rendering to cache the current pager view
/// \param cursor_is_within_pager whether the position is within the pager line (first line)
void s_write(screen_t *s, const wcstring &left_prompt, const wcstring &right_prompt,
             const wcstring &commandline, size_t explicit_len,
             const std::vector<highlight_spec_t> &colors, const std::vector<int> &indent,
             size_t cursor_pos, pager_t &pager, page_rendering_t &page_rendering,
             bool cursor_is_within_pager);

Looks good to me on linux, let's land


[Feature Pairity Request/Enhancement] reintroduce circular icons for user activity status to provide accessability for colorblindness

I personally think Quarrel should still be supplementing the new glow effects with some kind of icons, specifically drawn ones that can be differentiated in monochrome. This is the same reason Discordapp switched to the new icons they're using instead of just the colored circles.

Accessibility should never be low priority.

Accessibility should never be low priority.

To be clear I am not saying accessibility is low priority, just this specific UI change. If you would like to submit a PR making this change I would happily merge it.


[Feature] Develops an Ambari plugin about DS

Many companies now use ambari to manage their big data clusters，A ambari plugin about DolpinScheduler  can be directly integrated into their amabri, and the plugin will automatically get the service address and configuration information of zk, hdfs, hive, spark ... in the cluster, and automatically generate the configuration files required by DolpinScheduler . On Ambari, we can visually manage DS configuration parameters, and start, stop, upgrade DS services, etc
1、To develop an ambari plugin, DolpinScheduler needs to support installation as an rpm package and this can be achieved through rpm-maven-plugin
2、Develop an ambari plugin according to the ambari official documentation and interface
https://cwiki.apache.org/confluence/display/AMBARI/Defining+a+Custom+Service
to do list:

[x] Update DolpinScheduler pom add rpm-maven-plugin

[ ] Develop an ambari plugin according to the ambari official documentation and interface
https://cwiki.apache.org/confluence/display/AMBARI/Defining+a+Custom+Service

I will do my first task and plan to complete it on December 16, 2019

I will do the second task--the ambari plugin of DS.
It will be finished before 2020/01/01, i think


Capture stores wordnet conversion rather than original input.

In the case of an input capture like this:
+ *(1-6)
- ^save(name, <cap>)

If passing a wordnet matching input such as:

hi

Then ~emohello is what is captured rather than hi.
hi is what is expected.
Refs: #262

Will no longer happen in v1.0.0 since we'll no longer replace certain phrases in the message with the wordnet-like tags (e.g. hello to ~emohello), instead exposing them to plugin functions as message.tags.


Bug/activity indicator for android

The default color for ActivityIndicator on Android is a bug in the official library React native and should add a color property to fix it.
The bug is open, go to the link: https://github.com/facebook/react-native/pull/30057/files


[Question]connect oracle error

**For better global communication, Please describe it in English. If you feel the description in English is not clear, then you can append description in Chinese(just for Mandarin(CN)), thx! **
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior, for example:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Which version of Dolphin Scheduler:
-[1.1.0-preview]
Additional context
Add any other context about the problem here.
Requirement or improvement

Please describe about your requirements or improvement suggestions.

the OJDBC jar is placed in the Dolphin installation directory lib folder, restart the dolphin api-server and worker-server.

the OJDBC jar is placed in the Dolphin installation directory lib folder, restart the dolphin api-server and worker-server.

What is the version of OJDBC

What is the version of OJDBC

What is the version of OJDBC

What is the version of OJDBC

cannot open the picture

cannot open the picture

cannot open the picture

oracle jdbc driver

cannot open the picture

oracle jdbc driver

Close this question since it has been replied

where is the folder of driver??

where is the folder of driver??

the OJDBC jar is placed in the Dolphin installation directory lib folder, restart the dolphin api-server and worker-server.

where is the folder of driver??

$DOLPHINSCHEDULER/lib

I find it,It's works.  Thanks all.


Adds _make_df_eris_outcore to UCCSD

I added an outcore AO->MO routine for UCCSD + DF, which I thought would be useful to add to master.
The implementation was tested in two limits (examples below):

spin-symmetric solution of H2O@cc-pVDZ, comparing RCCSD+DF vs UCCSD+DF, which leads to a difference of ~1e-10 in the correlation energy
The radical NO2, comparing non-DF UCCSD/cc-pVDZ  with UCCSD/cc-pVDZ+DF(aug-cc-pV5Z-ri), which leads to a difference of ~2e-6, which I guess is reasonable for the remaining DF error?

test_1.py.txt
test_2.py.txt

Please add a small test for DF-UCCSD


Fixup Stratagem bugs and enhancements on the backend and wasm components

Fixes #1100.
Fixes #1107.
Fixes #1106.
Fixes #1075.
Fixes #1096.
Fixes #1105.
Fixes #1094.
Signed-off-by: Will Johnson<EMAIL_ADDRESS>

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1112   +/-   ##
=======================================
  Coverage   72.27%   72.27%
=======================================
  Files           3        3
  Lines         202      202
=======================================
  Hits          146      146
  Misses         56       56

Continue to review full report at Codecov.

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

Closing as this patch has been obsoleted by breaking it into smaller patches.


--test-adapter-path: required for .NET core, but not full framework

I suspect this is the wrong place for this issue, but never the less perhaps you might have some idea on the issue,
Why is it that when you run dotnet test --logger:xunit under .NET core you need to specify --test-adapter-path:., whereas under a .NET framework project you are able to omit this argument? The behaviour is pretty confusing and took me a reasonable amount of time to realise my error.

@optical we're fixing this in next update to dotnet test (https://github.com/Microsoft/vstest/issues/616, https://github.com/Microsoft/vstest/issues/557).

Aha, excellent. Thanks for that. What will the typical acquisition story be for that fix? My guess is it'll go out in a release of the dotnet sdk? If so, how would one figure out which version the fix will be contained in?

@optical  apology for responding so late. We have fixed it with TestPlatform release
I don't know the exact version of dotnet sdk which has this fix but the later version will sure have this.

Thanks for the follow up. Will check it out.


RuntimeError and ITK ERROR

When I use ITK to convert multiple .png into .nii.gz, the following error occurs
RuntimeError: Exception thrown in SimpleITK ImageFileWriter_Execute: /tmp/SimpleITK-build/ITK-prefix/include/ITK-5.3/itkImageFileWriter.hxx:245:
ITK ERROR: ImageFileWriter(0x3465190): Largest possible region does not fully contain requested paste IO regionPaste IO region: ImageIORegion (0x7ffe6ad51d00)
Dimension: 3
Index: 0 0 0
Size: 240 240 0
Largest possible region: ImageRegion (0x7ffe6ad51c40)
Dimension: 3
Index: [0, 0, 0]
Size: [240, 240, 0]
What should I do?

The z-size of zero does not seem right. Where is that coming from?

Assuming issue was resolved, please open if not.


test: Check env in a container

This will check the path, hostname and home of a container
Fixes #294
Signed-off-by: Gabriela Cervantes<EMAIL_ADDRESS>

@devimc changes applied

@devimc changes applied


Repo Indexer does not work with new migrated repositories from API /repo/migrate

Description
I'm using gitea 1.15.5 with Code Search feature, with elastic search as the engine. I use a script to import some repositories from a private Gitlab by API "/repo/migrate". But after migration, these repositories fail to appear in code search results.  I have to manually commit something new to the new repo to trigger report to elastic search, or delete the old elastic search topic and create a new index.
I have met this problem on websites, and reported  in this issue #16986 , then follow the bugfix of this issue. So I am sure that the code index works well when migrating from UI.
But API "/repo/migrate" has a different progress from websites.
Here is my guess: In routers\api\v1\repo\migrate.go, gitea use a defer function to notify repo migrate after creating a new empty repo by function repo_module.CreateRepository. Then start a migrate task. The repo is not empty after migration, but in defer function, it still use the original "repo" param, therefore repo.IsEmpty=true, and will not trigger gitea code index to report to elastic search.
routers\api\v1\repo\migrate.go

In modules\notification\indexer\indexer.go Gitea only repo to index engine when repo.IsEmpty=false

Thanks for reading my question, look forward to your kind reply~~~
Gitea Version
1.15.5
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
kubectl
Database
MySQL

1.15.5 is incredibly out of date, please update to latest stable version (which at time of writing is 1.17.2) and try again. I am going to close this issue now, but please re-open if after opening it re-occurs.


Providing the Zuul source with two different approaches to a query: fast and verbose

Removed the source manager approach I was using until now.
Adding AggregatedQuery. Queries are now treated as a builder where each different action adds more to the output. Two options branch from here, a builder focused on getting as much data as possible and another on getting things done fast.
Adding ArgumentReview which will the interpret what the user is asking for.
The source will now treat each possible query: tenants, jobs, builds... as its own thing. Removing dependencies between them. This will make them easier to maintain.
The source will make queries based on what ArgumentReview says.

This PR is a proof of concept. Some tests may not run on this one, but that is expected. I am not going to merge this, it is meant to get it out there and get some feedback. From here I will prepare smaller, better defined PRs.

Closed in favor of #468


 Is that why I can't use mtmsn in Chinese corpus ?
But I see the "bert.tokenization" can handle the chinese word, I dont know what the problem is.
Is there any help ?
Thanks.

What is skip_when_all_empty for ?


Warn about circular deps and ensure no new ones are added

Actually I think this is not a way to go.
#1878 discuss it and the consensus is that circularity inside a single compilation unit is ok. The argument is that without circularity some code structures may be hard to describe.
As long as runtime is one compilation unit, the circular deps inside it are ok. Once we have a good reasons to split runtime into separate compilation units, then we should remove cycles between these units.
I will abandon this PR.


[QUERY] Location poller handling of 500 error incompatible with specs for OperationResults API.

Bug Report/Question
The operation result API that is used for the Location header polling URL states that, when the operation is finished, the final GET on the polling URL should return the exact same response as if the operation had been done synchronously

If the operation is complete, return the exact same response that would have been returned had the operation been executed synchronously

Our interpretation of this requirement is that, if the async operation fails with an InternalError, a synchronous operation would have returned 500 InternalServerError.
So that is what AKS operationResult API is doing.
As a result, the few APIs that uses the Location header to poll the result of async operations trigger an infinite polling.
Once the operation has failed on the async side with an internal Error, our OperationResults API will always return 500. and the poller includes 500 in its NonTerminalStates

I've tried to track the logic in the .net SDK. but it's pretty hard to figure it out because it's very fragmented.
I think that it boils down to this:
https://github.com/Azure/azure-sdk-for-net/blob/c4418cd3e85f2e01a92b702414244647ff3695df/sdk/core/Azure.Core/src/Shared/OperationInternal.cs#L122C63-L122C79
and this for the failure case:
https://github.com/Azure/azure-sdk-for-net/blob/c4418cd3e85f2e01a92b702414244647ff3695df/sdk/core/Azure.Core/src/Shared/OperationInternal.cs#L237C12-L237C91
but I don't see any code that would not consider a 500 a terminal failure.

I think the problem here is that we've conflated rules for retry with status codes we consider to be terminal failure. Off the cuff, what probably needs to happen is that for status codes that aren't terminal success, we let them be handled by the retry policy which, by default, will enforce a retry cap (need to experiment with this).

Ok it's more nuanced than that. For context, Poller[T].PollUntilDone() will exit IFF one of the following conditions is met.

the HTTP transport fails (governed by the retry policy)
the underlying poller reaches a terminal state
the context expires/is canceled

Here is the sequence of events. This assumes the default retry policy is in play.

PollUntilDone calls underlying poller.Poll
Poll creates the request and sends it through the pipeline
Service returns 500, the retry policy retries the request until the cap is hit
500 is returned to the underlying poller which is non-terminal
goto step 1

While we could augment the retry policy to tell PollUntilDone "my retry cap has been exceeded", it would tightly couple the two together which is not good (e.g. if the in-box retry policy has been replaced, now the logic is broken).
This might require updating PollUntilDone to exit after N number of transient status codes. This required some care though as it will multiply with the number of retries from the retry policy. i.e. if the retry policy retries three times on 500, and PollUntilDone retries three times on 500, the total number of requests will be nine (with exponential back-off from the retry policy to boot).


Using Foundation for Apps (with Gulp) in a Production Environment

Hello everyone!
I have had a blast learning the new apps and you guys have done a great job but I've hit a wall.
Using Foundation for Apps or Gulp in a production environment, how difficult would that be? For the gulp-connect plugin, just editing the host and port numbers or is there a much deeper process to do this?
I have been experimenting with it as a localhost, but I'm trying to get it to go live as well. How would I go about this?

@mikehuebner Yep, that's it! To expand on what @AntJanus said, Gulp, Grunt, et al. are build tools that are meant to be run in a development environment only, and are primarily used to deliver static code. The servers that you can run with Gulp and Grunt (and even frameworks like Django and Rails) are meant for convenience and testing only, not production.
You could automate this process in Gulp by creating a deployment task that uses rsync, FTP, SSH, etc. to upload the build folder for you. We do this to deploy the documentation.


Sponsored issue: The volume control doesn't work.

Priority Support

@drokbers is using  Mintycode to fund this issue.
You can receive  if you provide priority support to @drokbers.
To view the support request and terms go to  Mintycode.
Thank you in advance for helping.

might not be related but software volume control on mobile is rarely supported. on iOS it is not.


[BUG] docker buildx for amd64,arm64 and arm/v7 ->the later 2 fail

Trying to build lnbits for the above 3 architectures with this command:
docker buildx build --platform linux/amd64,linux/arm64,linux/arm/v7 -t petzsch/lnbits:0.11.3 --push .
Fails with the following:

Not sure why the poetry install hangs so long and eventuelly fails.
I've tried bumping the python image used in the dockerfile to bookworm but it didn't help. Any ideas would be greatly appreciated.

armv7 is practically dead but it makes sense to fix arm64

must have misread the output, ommitting arm/v7 and i'm able to build it. It's pushing now to docker hub.
will close the issue tomorrow, since armv7 doesn't seem to be relevant to fix.


enable-certificate-owner-ref chart placeholder

What this PR does / why we need it:
Includes commented-out arg reference for enabling certificate-owner feature flag... Pretty boring PR, I know. Little bit of inline "documentation" that will save some time for people trying to enable this
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
See also:
https://github.com/jetstack/cert-manager/issues/296
https://github.com/jetstack/cert-manager/pull/819
https://github.com/jetstack/cert-manager/issues/912
https://github.com/jetstack/cert-manager/pull/1705
https://github.com/jetstack/cert-manager/issues/296
Release note:
commented-out extraArg for enable-certificate-owner-ref

Thanks for the PR, and sorry for the delay looking at it...
/lgtm
/approve
/override dco
/release-note-none
/ok-to-test

No worries at all, no rush. Thanks for merging + thanks for the continued development of cert-manager.


feat: change default crypto provider to match rustls'

It would be confusing for rustls docs to say "by default it uses aws-lc-rs for implementing the cryptography in TLS" but discover that tokio-rustls changes the default.

If we want to match rustls we should remove default-features = false and default = [].

Any thoughts on this crate not setting (or re-exposing) any of the ring/aws_lc_rs crate features? Given the top-level API here requires an application to supply a ClientConfig/ServerConfig, all decisions relating to providers have already been made.
In fact, I think this crates features can be reduced to just early-data? Everything else reexposes rustls features, which are better set directly elsewhere in the dependency tree.
(Naturally for tests and example code, it would be necessary to depend on rustls with default features as a dev-dependency.)

Everything else reexposes rustls features, which are better set directly elsewhere in the dependency tree.

I'll make the case for surfacing all rustls features in this crate as a distinct concern from what the default features are: Currently tokio-rustls and futures-rustls reexport rustls, which means that a consuming crate can just add the async rustls flavor to their Cargo.toml as a façade for rustls. User code doesn't need to keep two independent versions of rustls synchronized in Cargo.toml, and there are no "same name, different types" errors when one version bumps before the other.
This is a cargo problem in that ideally we'd be able to enable features on transitive dependencies with something like tokio-rustls = { version = "0.25", features = ["rustls/ring"] }, but in the absence of that, it's awkward for people to have to add a transitive dependency as a direct dependency only to enable features, especially since there's no way to say "I want the same version that tokio-rustls is using, whatever that is."

Sorry, yes, I also agree with that. I think tokio-rustls often acts as a kind of wrapper crate, so we should actually mirror rustls' defaults and features -- the sibling transitive dependency is definitely a bit of an anti-pattern.

Thank you!


ability don't continue comment

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md

Module(s)
comments
Description
Can i change this behaviour

Press enter and get new commented line

I hardly ever write multiline comments, so this feature is bothering me.

This comes from built-in Neovim. See r flag in :h formatoptions.
You can properly disable it by adding this autocommand in your config: vim.cmd('autocmd FileType * setlocal formatoptions-=r').


Fake PR to test clang change from PR925

Please test with following pull request:
https://github.com/apple/llvm-project/pull/925
@swift-ci Please clean test

Build failed
Swift Test Linux Platform
Git Sha - 62bf3ba56fc0fc1050b792c58e983ad8cb317812

Build failed
Swift Test OS X Platform
Git Sha - 62bf3ba56fc0fc1050b792c58e983ad8cb317812

This is not proving the expected value, since it's failing with completely unrelated stuff. Closing


Merger: README

README.md for the relayer https://github.com/streamingfast/merger

Remove the "Installation & Usage" section
Add a link to the right section of the Firehose documentation (in Components)

Done.


Failed to setup

^[cCopying icon file - please wait ...
^[cError: Failed to copy icon file.
Please open an incident on GitHub:
https://github.com/scriptPilot/app-framework/issues
^[cError: Failed to setup app folder.
Please open an incident on GitHub:
https://github.com/scriptPilot/app-framework/issues

@teddysasmita - Please can you add details about your system and the steps you performed?

I am using Ubuntu 17.04 and NodeJs 6.11 with its npm. Thank you.

same issue.

Error: Failed to copy icon file.

Ubuntu 16.04.2 x64
node v8.1.2

https://github.com/scriptPilot/app-framework/blob/master/scripts/reset-app.js#L34
fs.copy(abs(__dirname, '../demo/icon.png'), abs(dest, 'icon.png'), function (err) {
from version 1.9.6 folder ../demo not included in npm package

Should be fixed with 1.9.7, please let me know there are still issues!

Solved in 1.9.7
@scriptPilot thanks for fix

Installation process is success.
Thank you for the fix.
I cannot wait to try your framework.
On Jul 2, 2017 01:43, "axjs"<EMAIL_ADDRESS>wrote:

Solved in 1.9.7
@scriptPilot https://github.com/scriptpilot thanks for fix
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/scriptPilot/app-framework/issues/617#issuecomment-312448952,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFLt98zr8d9qgl7GPBOMkltJJ3CMyLoCks5sJpNMgaJpZM4OIvS8
.


Dark Mode

Hey, is it possible to implement a Dark Mode? I primarily use the application before going to bed, as do many others, I presume. Having a Dark Mode would be highly beneficial, preventing me from being blinded every time I open it. Could this feature be considered for implementation?

Hi (nice bike 😉),
I've already got this on my list of necessary features. Sadly the "materialize css" framework (which is used) doesn't support light/dark mode transitions 😕
So this feature will only be included in a completely rewritten version of dailytxt (which will then probably be based on bootstrap).
But: the rewrite is several months away (not yet planned, but I will probably not start working on it within the next 12 months)!

Hi (thanks😂),
Yeah that really sounds like a lot of work. Thanks for your quick Answer👌
Marco Kümmel @.***> schrieb am Sa., 17. Feb. 2024,
10:37:

Hi (nice bike 😉),
I've already got this on my list of necessary features. Sadly the
"materialize css" framework (which is used) doesn't support light/dark mode
transitions 😕
So this feature will only be included in a completely rewritten version of
dailytxt (which will then probably be based on bootstrap).
But: the rewrite is several months away (not yet planned, but I will
probably not start working on it within the next 12 months)!
—
Reply to this email directly, view it on GitHub
https://github.com/PhiTux/DailyTxT/issues/40#issuecomment-1949916245,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXUCUZNX5MSG3UPB4WG7EKTYUB24RAVCNFSM6AAAAABDMZ7PWKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBZHEYTMMRUGU
.
You are receiving this because you authored the thread.Message ID:
@.***>


Report dimensions on init and Android focus()

Issue
Calling .focus() on Android does not focus the window
Specifically requesting focus on the webview seems to allow focus.

Enhancement
Report dimensions on init
This is something that enhances developer experience :-)
Regarding the timeout;
I'd expect new Quill() to be synchronous, but without a timeout wrong dimensions were reported.

released v0.7.15


Remove the self-type parameters from abstract builders

Motivation:
Self type parameters are useful when you write an abstract builder
with method chaining, but the Javadoc generated from it looks less
intuitive.
Modifications:

Remove the usage of the self-type parameters from abstract builders.
Miscellaneous:

Add CircuitBreakerClientBuilder.mapping().
Deprecate CircuitBreakerClientBuilder.circuitBreakerMapping().

Result:

Looks prettier to users
Increased maintanence burden for devs
Deprecation of CircuitBreakerClientBuilder.circuitBreakerMapping() in favor of mapping()

Thanks for reviewing.


GetLibraryPathAsync updated to use remote environment to determine lib path for user

Do PackageManagerIntegrationTests still pass?

👍

👍


Improve EnsureAssetsCompiled logic to wait for webpack process to finish

Because there may be situations where a user is running a webpack
process in watch mode in the background that will recompile the
assets, it is possible that if the build time is extremely long,
the user could start their test suite before the build completes. In this case,
EnsureAssetsCompiled would start compiling the assets again even
though there is already a webpack process doing that.
This commit adds behavior to EnsureAssetsCompiled to check whether
or not the webpack process is running in the background, and, if so, will
defer the responsibility of compilation to that process, re-checking
the compiled assets every second until they are up to date.

Looking great!

Reviewed 6 of 6 files at r1.
Review status: all files reviewed at latest revision, 4 unresolved discussions.

lib/react_on_rails/ensure_assets_compiled.rb, line 56 [r1] (raw file):
Please display a message how to do this more efficient, by running blah, blah, blah, etc. or a doc link.

lib/react_on_rails/ensure_assets_compiled.rb, line 63 [r1] (raw file):
It will be confusing if one or the other is not running. I'd recommend we error out  in the case of we detect one but not the other. FAIL FAST!

lib/react_on_rails/ensure_assets_compiled.rb, line 72 [r1] (raw file):
Did you test this?
It's (-w|--watch)
-watch is not correct

lib/react_on_rails/utils.rb, line 14 [r1] (raw file):
This is a global.
IDEALLY, we should run both client and server concurrently, rather than sequentially, but you can defer on that one.
Where are you capturing the results? and aborting if not success?

Comments from the review on Reviewable.io

Reviewed 2 of 6 files at r1.
Review status: all files reviewed at latest revision, 4 unresolved discussions.

lib/react_on_rails/ensure_assets_compiled.rb, line 56 [r1] (raw file):
Done.

lib/react_on_rails/ensure_assets_compiled.rb, line 63 [r1] (raw file):
Done.

lib/react_on_rails/ensure_assets_compiled.rb, line 72 [r1] (raw file):
Tested in one of those regex websites as well as the spec dummy (which uses just the -w so I forgot about the double dash when passing the long form).
Done.

lib/react_on_rails/utils.rb, line 14 [r1] (raw file):
WebpackAssetsCompiler#compile: https://github.com/shakacode/react_on_rails/blob/master/lib/react_on_rails/ensure_assets_compiled.rb#L36

Comments from the review on Reviewable.io

Reviewed 4 of 6 files at r1.
Review status: 4 of 6 files reviewed at latest revision, all discussions resolved.

Comments from the review on Reviewable.io

More great code. Couple minor comments.

Reviewed 3 of 3 files at r2.
Review status: all files reviewed at latest revision, 2 unresolved discussions, some commit checks failed.

lib/react_on_rails/ensure_assets_compiled.rb, line 57 [r2] (raw file):
Too vague. Show what you are matching. Plus a doc link!

lib/react_on_rails/ensure_assets_compiled.rb, line 79 [r2] (raw file):
:thumbsup:

lib/react_on_rails/utils.rb, line 14 [r1] (raw file):
Are we sure that we can rely on the content having error. Sometimes we have files with the word error in the file name. I prefer the exit code if that is reliable for knowing we failed. Or if we are SURE, then this is OK.

Comments from the review on Reviewable.io

Reviewed 2 of 3 files at r2.
Review status: 5 of 6 files reviewed at latest revision, 2 unresolved discussions.

lib/react_on_rails/ensure_assets_compiled.rb, line 57 [r2] (raw file):
Okay the link to the docs was a little long, so check how I did it. I can change if you want the full-length link in there. It's this, unless I can shorten it somehow but I can't remember?: https://github.com/shakacode/react_on_rails/blob/master/docs/additional_reading/rspec_configuration.md
I'm not sure what you meant by matching here though, I'm not matching anything. This is just the output that happens after we compile the bundle.

lib/react_on_rails/utils.rb, line 14 [r1] (raw file):
@justin808 wait I'm confused, you originally wrote it so it was grepping for the word "error," but my commit changes that to use the exit status. That link is to the current implementation of WebpackAssetsCompiler#compile on master, the new implementation uses this helper I wrote here.

Comments from the review on Reviewable.io

Reviewed 1 of 1 files at r3.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

lib/react_on_rails/ensure_assets_compiled.rb, line 57 [r2] (raw file):
You need the full URL. Yes, it's long. It's worth it.

lib/react_on_rails/utils.rb, line 14 [r1] (raw file):
OK -- so long as you can display the error when you exit due to this.

Comments from the review on Reviewable.io

Review status: 5 of 6 files reviewed at latest revision, 2 unresolved discussions.

lib/react_on_rails/ensure_assets_compiled.rb, line 57 [r2] (raw file):
Done.

lib/react_on_rails/utils.rb, line 14 [r1] (raw file):
@justin808 Yep, this method is the best of both worlds in this sense. Here is the link to the same place but how I have it in this PR: https://github.com/shakacode/react_on_rails/blob/rob/improve-ensure-assets-compiled/lib/react_on_rails/ensure_assets_compiled.rb#L54
Notice I'm still capturing the output of the process, then I check the exit code, and if the exit code is a failure, then I log an error message that includes the captured output so they know what the error was.

Comments from the review on Reviewable.io

Reviewed 1 of 3 files at r2, 1 of 1 files at r3.
Review status: 5 of 6 files reviewed at latest revision, all discussions resolved.

Comments from the review on Reviewable.io

Amazing job @robwise!

Reviewed 1 of 1 files at r4.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from the review on Reviewable.io

Please merge, ensure changelog updated, docs ready etc. and let me know if I should release later today.

Review status: :shipit: all files reviewed at latest revision, all discussions resolved, all commit checks successful.

Comments from the review on Reviewable.io

Latest code makes it so we only run once per suite run (assuming the suite has a feature test in it) instead of running every feature test.
Also, the config now allows for specifying where webpack is outputting generated files. By default, this is app/assets/javascripts/generated and app/assets/stylesheets/generated so that we don't break any current builds that are following the convention of the generators.
Lastly, we were using unix file separators in the configuration which I changed to be platform-dependent.
@justin808 I think I should just update the docs in PR 252 to include this information, right?

Reviewed 3 of 4 files at r5, 1 of 1 files at r6.
Review status: 6 of 7 files reviewed at latest revision, 2 unresolved discussions.

lib/react_on_rails/ensure_assets_compiled.rb, line 5 [r5] (raw file):
I had to do it this way because linter doesn't like it when I use @@. Supposedly that's a bad practice because subclasses have access to the variable. Whatevs

lib/react_on_rails/webpack_assets_status_checker.rb, line 14 [r5] (raw file):
This was only temporarily necessary, pls ignore

Comments from the review on Reviewable.io

Review status: 6 of 7 files reviewed at latest revision, 3 unresolved discussions.

lib/react_on_rails/ensure_assets_compiled.rb, line 5 [r5] (raw file):
Correct.

lib/react_on_rails/ensure_assets_compiled.rb, line 44 [r6] (raw file):
I personally think we should have one class per file.

Comments from the review on Reviewable.io

Review status: 6 of 7 files reviewed at latest revision, 7 unresolved discussions.

lib/react_on_rails/ensure_assets_compiled.rb, line 16 [r6] (raw file):
Is there a return value that is useful from this call? I don't see anything useful other than to call call from this created object.
Just use a static calls
You can make this one API:
ReactOnRails::EnsureAssetsCompiled.call(client_assets_checker:, server_assets_checker:, process_checker:)

lib/react_on_rails/ensure_assets_compiled.rb, line 21 [r6] (raw file):
This API is really awkward.

lib/react_on_rails/ensure_assets_compiled.rb, line 21 [r6] (raw file):
we don't need this method  -- just use static calls

lib/react_on_rails/ensure_assets_compiled.rb, line 27 [r6] (raw file):
Make this method static
return if @has_been_run

Comments from the review on Reviewable.io

A couple comments.

Reviewed 1 of 4 files at r5.
Review status: all files reviewed at latest revision, 7 unresolved discussions.

Comments from the review on Reviewable.io

Reviewed 1 of 4 files at r5.
Review status: all files reviewed at latest revision, 6 unresolved discussions.

lib/react_on_rails/ensure_assets_compiled.rb, line 16 [r6] (raw file):
@samnang what's your thoughts here? I was trying to follow the style you taught me when pairing, but maybe this is a different case?

lib/react_on_rails/ensure_assets_compiled.rb, line 21 [r6] (raw file):
@justin808 suggestions?

lib/react_on_rails/ensure_assets_compiled.rb, line 21 [r6] (raw file):
@justin808 I need DI for tests tho

lib/react_on_rails/ensure_assets_compiled.rb, line 44 [r6] (raw file):
@samnang what is the convention in Ruby if I'm creating a utility class that is only ever used by this other class

Comments from the review on Reviewable.io

Review status: all files reviewed at latest revision, 6 unresolved discussions.

lib/react_on_rails/ensure_assets_compiled.rb, line 27 [r6] (raw file):
I have instance-level dependencies in this method in the form of webpack_process_checker and webpack_assets_checker

Comments from the review on Reviewable.io

Review status: all files reviewed at latest revision, 5 unresolved discussions.

lib/react_on_rails/ensure_assets_compiled.rb, line 21 [r6] (raw file):
Please don't ever sacrifice the end code API for tests.

lib/react_on_rails/ensure_assets_compiled.rb, line 27 [r6] (raw file):
You can pass those, in just have defaults.

lib/react_on_rails/ensure_assets_compiled.rb, line 44 [r6] (raw file):
You can/should test the other classes. I don't see why you'd have multiple classes in one file.

Comments from the review on Reviewable.io

Review status: all files reviewed at latest revision, 3 unresolved discussions.

lib/react_on_rails/ensure_assets_compiled.rb, line 44 [r6] (raw file):
I can move the classes to separate files, I was just following what I was shown. I have extracted these other classes specifically because they are simple wrappers on third-party libraries/applications. This isolates dependencies on webpack and running webpack processes as well as using the pgrep. To test these would just be testing the unix pgrep utility or webpack themselves.

Comments from the review on Reviewable.io

lib/react_on_rails/ensure_assets_compiled.rb, line 44 [r6] (raw file):
If it's very simple class and ever used as their internal functionality, it's okay to leave it there, but if it's not simple, better to have it in another file, but it still in the namespace under it.

Comments from the review on Reviewable.io

lib/react_on_rails/ensure_assets_compiled.rb, line 16 [r6] (raw file):
In this case, you could inline here. The benefit to use dependency injection in constructor, so you could have more than one public methods, and extract some functionality in private methods. For static methods, if you want to extract methods, you have to always pass parameters, and then we don't get any benefit from encapsulation.

Comments from the review on Reviewable.io

Let's merge if this passes CI.

Reviewed 20 of 20 files at r7.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

Comments from the review on Reviewable.io

BOOM :tada:


ER_BAD_FIELD_ERROR: Unknown column 'student_name' in 'field list'

CREATE TABLE student (
    student_id INT PRIMARY KEY,
    student_name VARCHAR(20),
    major VARCHAR(20)
);
SELECT * FROM student;

INSERT INTO student(student_id, student_name) VALUES(3, 'Bob');

Every time I run this, it throws me an error. I would appreciate if someone could please help.
Thanks!

To the best of my knowledge,when you want to insert/update a string value onto the database,use single quotes or backslash. As of right now,the value is being read as student_name = Bob.
Using
INSERT INTO  student(student_id, student_name)  VALUES(3, " 'Bob' ");
or
INSERT INTO  student(student_id, student_name)  VALUES(3, ' \ 'Bob\' ');
should work.

I'm going to close as there was a response and seem to be a MySQL question unrelated to this module.


Add comments to android app code - Baylie & Karen

[ ] Add comments to code

[ ] Comments to android app code for Amplify initialization - Baylie & Karen
[ ] Comments to android app code for uploading to the bucket - Baylie & Karen

Test Cases:

[ ] Demonstrate the areas where comments have been added to the .java and manifest files

looks good.


Implemented: support for single logout functionality

Related Issues

Related Issue https://github.com/hotwax/dxp-components/issues/144
Short Description and Why It's Useful

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

Additional Information
Considering that when user tries to logout from the app and if for some reason api fails or returns error, then still we will logout the user from the app locally.

Closing as handled in https://github.com/hotwax/launchpad/pull/53


Questions about the reproducibility of the code and the results of the paper

I sincerely question the reproducibility of the code and the results of the paper, in this repo issue:

I have seen people using the same V100 GPU as the author in time, but unable to run through the code and experiencing OOM errors. No reply was forthcoming #1 #20
My own reproduction of the code does not achieve the results shown in the left panel of Figure 3 in the paper, and I do not understand why catastrophic forgetting does not occur when such statistical results occur. And even without using the Optionally diversifying prompt-selection method, I can't get this statistic, same as in the #18 #24 This issue comes with detailed statistics logs. By looking at the Histogram records, we can see that only four prompts were selected and that all tasks share these prompts. I think this is inevitably going to cause catastrophic forgetting.
The use of pre-trained ViT may have caused an information leak #11.
The given requirement.txt does not directly install the required runtime environment, and even if it does, it will only run on the CPU #1.

And, for myself:

This code is really hard to run on my RTX 3090 GPU, and even after a lot of effort and without any error reporting, the program is stuck at training step 5 of the first task.
I have not seen anyone in the issues who has successfully reproduced the results.

I very sincerely hope that the author will answer the above questions.

@zizhaozhang @KingSpencer

@zizhaozhang @KingSpencer

Hi,
Thanks for your interest in our work and your questions!
For the first 4 questions, I believe the answers already exist in their threads, respectively:

@miss-rain I found in the official document that when JAX executes the first JAX command, it pre-allocates 90% of the available GPU memory. As described in the document, I can either disable the pre-allocation or reduce the pre-allocation ratio to run the ViT-Base model. As a result, I was able to run on my GPUs 8 RTX 3090 and 8 A5000.

solved by re-installing cudnn

Great insight!
Actually we have not tried your suggested experiments, but it is definitely something worth trying. Regarding the "information leakage", I think we do make the assumption that we have a "well-pretrained" model, and we use the same pretrained model for all competitors, so the comparison is actually fair. Another thing I would like to highlight is that the idea of prompting is actually leveraging learned knowledge in the model, and trying to "instruct" the model to selectively use learned knowledge for coming tasks. Since large-scale pretrained model is prevalent these days, leveraging them is quite natural.
On the other hand, thinking about the extreme case that the pretrained model is totally off (e.g. trained on a totally different dataset, though we will not do it in practice), L2P will probably fail if the backbone is frozen. Thus, it will be interesting to see how and when to adapt the model backbone as a future direction.

Same as 1.

For your own questions:

Please carefully check if any one of the solutions mentioned above can help you out. There might be some environment mismatch.
People normally will not mention if they have successfully reproduced the codebase in "issues". As far as I know, some researchers have already reproduced the result with negligible difference, and we have exchanged emails privately to discuss about the results.

Hope all these help! Worst case, if you can not reproduce after all trials, feel free to send me your detailed configuration. I will try to find some time to help out.
Best,
Zifeng

Thank you for your timely reply! My confusion centres on the second of the fourth questions:

My own reproduction of the code does not achieve the results shown in the left panel of Figure 3 in the paper, and I do not understand why catastrophic forgetting does not occur when such statistical results occur. And even without using the Optionally diversifying prompt-selection method, I can't get this statistic, same as in the #18 #24 This issue comes with detailed [statistics logs]

I‘m not concerned with why the loss became nan. I'm more interested in knowing how to reproduce the statistics of the kind of prompts selection that appears on the left-hand side of Figure 3 of the paper, because as mentioned above, both my own version of the reproduction, the question posed by the person in #18 and the detailed logs given in #24 are showing that the top-k prompts are first selected randomly when training the first task and then optimizing the representation of its keys, which causes the same top-k prompts to continue to be selected for all subsequent tasks when training. This inevitably leads to catastrophic forgetting.
question from #18:

According to the contents of the paper and my understanding, the prompts in the prompt pool should be selected evenly for each task.
However, when I look at the prompt index and the Tensorboard histogram, it seems that only a few prompts are learned.
Only the 3rd, 6th, 7th, and 9th prompts are used in the official code of the reproduce result.

logs from #24:

I0920 13:10:04.959301<PHONE_NUMBER>88352 logging_writer.py:53] [50] Histogram for 'histogram_0' = {[0, 0.3): 992, [0.3, 0.6): 0, [0.6, 0.9): 0, [0.9, 1.2): 992, [1.2, 1.5): 0, [1.5, 1.8): 0, [1.8, 2.1): 992, [2.1, 2.4): 0, [2.4, 2.7): 0, [2.7, 3]: 992}
I0920 13:10:04.961827<PHONE_NUMBER>88352 logging_writer.py:53] [50] Histogram for 'histogram_1' = {[0, 0.3): 992, [0.3, 0.6): 0, [0.6, 0.9): 0, [0.9, 1.2): 992, [1.2, 1.5): 0, [1.5, 1.8): 0, [1.8, 2.1): 992, [2.1, 2.4): 0, [2.4, 2.7): 0, [2.7, 3]: 992}
...... delete histogram 2-8 for readability
I0920 13:10:04.987567<PHONE_NUMBER>88352 logging_writer.py:53] [50] Histogram for 'histogram_8' = {[0, 0.3): 992, [0.3, 0.6): 0, [0.6, 0.9): 0, [0.9, 1.2): 992, [1.2, 1.5): 0, [1.5, 1.8): 0, [1.8, 2.1): 992, [2.1, 2.4): 0, [2.4, 2.7): 0, [2.7, 3]: 992}
I0920 13:10:04.992606<PHONE_NUMBER>88352 logging_writer.py:53] [50] Histogram for 'histogram_9' = {[0, 0.3): 992, [0.3, 0.6): 0, [0.6, 0.9): 0, [0.9, 1.2): 992, [1.2, 1.5): 0, [1.5, 1.8): 0, [1.8, 2.1): 992, [2.1, 2.4): 0, [2.4, 2.7): 0, [2.7, 3]: 992}

Finally, I look forward to hearing from you again.

Hi,
Actually it's a great catch! I checked the configs carefully and think that there may be a typo in the configuration file line 109 config.prompt_pool_param.batchwise_prompt = True. This actually encourages prompt selection to be more concentrated and finally "collapse" to a limited set of prompts. By changing it to False, it should make prompt selection in a more free way. I will update the codebase accordingly.
Best,
Zifeng

Btw - I have been able to reproduce the results with my own implementation. I will vouch for the paper's reproducibility :)

@jamessealesmith Is that in pytorch? Would be plan to release the implementation? If so, I think it help help the community a lot.

Yes, the implementation is in pytorch! We will release it, planning before the end of 2022.

I already implemented L2P and DualPrompt in PyTorch.
It was released on my repository (l2p-pytorch, dualprompt-pytorch) about 2-3 months ago.
I hope that we can discuss it freely :)


[Windows] Enable Extended UTs

Rebase https://github.com/intel/torch-xpu-ops/pull/844 with https://github.com/intel/torch-xpu-ops/pull/782, https://github.com/intel/torch-xpu-ops/pull/828

@PenghuiCheng Please review.

@PenghuiCheng Please review.

approved


Hide audio/video mute buttons if no corresponding track is detected

Fixes #202
Also enable the new travis environment

LGTM.


update Run the library in a container section in README.md

from unstructured.partition.pdf import partition_pdf does not work anymore with the re structure.

Thanks @PieterjanCriel! We've actually reorganized the structure again so pdf.py is in the partition directory, so that command is accurate again :)