Logbook Feature Request

Would love to be able to have the ability to view the Logbook in DESC order.
using a option value in the Config file of ASC | DESC
and then modifying the logbook.py accordingly.
 QUERY_EVENTS_BETWEEN = """
    SELECT * FROM events WHERE time_fired > ? AND time_fired < ? ORDER BY time_fired DESC
"""

Unfortunately, I can't figure out the Option part or the Github part. :(
Example of DESC order of Logbook.
![] (http://i.imgur.com/mJQzldg.png)

The more I use HA, I'm surprised that DESC is not the default for the logbook.  As the day goes on, the current format makes the user scroll to the bottom for the most current events.  The list gets long when you are using some of the weather sensors that generate a lot of data points.  Scrolling is easier on the website but kind of a pain on mobile devices and seems unnecessary.
Was there a reason for the ASC view?  is it easier for the front end to just append new items on the bottom of the list dynamically?
From a functional perspective, I can't think of a reason to use ASC therefore I think going through the process of creating it as an option is not necessary. (unless it's a front-end thing)
Thoughts?

Well the idea is to be a log of changes. Means it should be chronological.
I have no objections against having both orders in the UI.
On Wed, Sep 2, 2015, 15:13 Carlo Costanzo<EMAIL_ADDRESS>wrote:

The more I use HA, I'm surprised that DESC is not the default for the
logbook. As the day goes on, the current format makes the user scroll to
the bottom for the most current events. The list gets long when you are
using some of the weather sensors that generate a lot of data points.
Scrolling is easier on the website but kind of a pain on mobile devices and
seems unnecessary.
Was there a reason for the ASC view? is it easier for the front end to
just append new items on the bottom of the list dynamically?
From a functional perspective, I can't think of a reason to use ASC
therefore I think going through the process of creating it as an option is
not necessary. (unless it's a front-end thing)
Thoughts?
—
Reply to this email directly or view it on GitHub
https://github.com/balloob/home-assistant/issues/288#issuecomment-137260692
.

So, I have added this functionality in pull request #315. I think this issue can be closed.

Fixed in 067993c8ab067c6512f12f1537995381ef88fcfd


API - How to upload a file

Is it possible to upload a file using the semantics API?
I know with jQuery, you can use FormData to send files such as $.ajax({ type: 'post', url: someUrl, data: new FormData($form[0]), contentType: false, processData: false }).
When I try to apply the same settings with the API, $form.api({ method: 'post', url: someUrl, data: new FormData($form[0]), cache: false, processData: false, contentType: false }), the script on the server cannot find any uploaded files.

I think it's not the semantic API problem. If you use PHP, please refer to https://www.sitepoint.com/file-uploads-with-php/. You should also check whether you have a right permission to write a file.

try this
$(".form").api({
   action:'post register',
   method:'POST',
   cache: false,
   processData: false,
   contentType: false,
   beforeSend: (settings)=>{
        settings.data = new FormData($(".form")[0]);
        return settings;
   },
   onResponse: (response)=> {
        return response;
   },
   successTest: (response)=> {
        return !response.error || false; //change this
   },
   onSuccess: (json)=>{
        console.log('successfull');
   },
   onFailure: (json)=>{
        console.log('error');
   }
});


WIP: port of microbit to embassy

Here is an early show of what an (untested) port to Embassy would look like (Issue #125). I've only modified the existing display-blocking and display-nonblocking examples:

display-blocking
display-nonblocking

Arguably the display is the most HAL/PAC reliant part of this crate, things using RTC directly can use the 'system timer' instead, but having a custom timer for the display should work.
Most of the peripherals have just changed types.
Next I plan to modify the RTIC example, and also add an async variant of the display driver, reusing some ideas from microbit-bsp combined with the nonblocking driver that is there.

@mattheww since you voiced some concerns about changes to use embassy-nrf, this may be of interest ^^

Is this based on a branch of embassy? The nonblocking display uses ticker.next_blocking(), but I don't see that in embassy main.
It looks like Board is willing to make RTC1 available to its owner, but embassy-nrf is programming it for its own purposes.
Does embassy have any equivalent of the GPIO typestate stuff that used to guarantee (for example) that if you had a DisplayPins instance then the pins were already configured as push-pull? If not, then maybe DisplayPins or Board should take over responsibility for ensuring that.

Is this based on a branch of embassy? The nonblocking display uses ticker.next_blocking(), but I don't see that in embassy main.

The original code used Instant to implement the ticker behavior, but I figured it makes more sense to put this blocking functionality into the ticker itself, I will PR it to embassy soon. Another reason I was using a branch is that there are some unreleased api changes that I wanted this work to build upon.

It looks like Board is willing to make RTC1 available to its owner, but embassy-nrf is programming it for its own purposes.

Good catch, this should probably be removed.

Does embassy have any equivalent of the GPIO typestate stuff that used to guarantee (for example) that if you had a DisplayPins instance then the pins were already configured as push-pull? If not, then maybe DisplayPins or Board should take over responsibility for ensuring that.

Currently DisplayPins does this configuration in degrade(), but it can be done earlier too.

Is ticker.next_blocking() putting the CPU to sleep or busy-waiting?

The next_blocking() essentially polls the RTC1 used for time-keeping in the HAL in a busy loop. Each poll in the loop ends up here checking the 'current time': https://github.com/embassy-rs/embassy/blob/main/embassy-nrf/src/time_driver.rs#L214-L219

Closing this as I think there are maintainers again for the microbit crate, and I will keep async stuff in the microbit-bsp for now.


Homogenous timeout

Call timeout check after verbose print and trajectory

Codecov Report

Merging #185 (d942cc0) into master (f6f895b) will decrease coverage by 0.10%.
The diff coverage is 45.90%.

:exclamation: Current head d942cc0 differs from pull request most recent head d1f906d. Consider uploading reports for the commit d1f906d to get more accurate results

@@            Coverage Diff             @@
##           master     #185      +/-   ##
==========================================
- Coverage   67.66%   67.55%   -0.11%
==========================================
  Files          13       13
  Lines        1670     1680      +10
==========================================
+ Hits         1130     1135       +5
- Misses        540      545       +5

Impacted Files
Coverage Δ

src/fw_algorithms.jl
77.22% <41.66%> (+0.74%)
:arrow_up:

src/blended_cg.jl
51.15% <48.27%> (-1.19%)
:arrow_down:

src/afw.jl
66.08% <50.00%> (+0.78%)
:arrow_up:

Continue to review full report at Codecov.

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


Dynamic configuration

Hello,
As I understood models enabled with corresponding lines in elasticsearch.yml, like:
ingest.opennlp.model.file.persons: en-ner-persons.bin
and such configuration parameters loaded during start, so in order to extend configuration, we need to restart the node or there is a way to do so without restart currently?
Otherwise, is there any plans to have dynamic configuration and store such information (links to models) in a dedicated index so new models can be enabled without restart? (with config reload from the index every x min)
thanks for a great ingest processor!

The files are in their own format and do not correspond to anything that could be indexed.
Reloading models can be achieved using the ResourceWatcherService (see https://github.com/elastic/elasticsearch/blob/master/server/src/main/java/org/elasticsearch/watcher/ResourceWatcherService.java)
If you want to work on that, I'll be happy to assist and review the PR.

It's not about files itself but their declaration in config
On Wed, Mar 7, 2018, 01:11 Alexander Reelsen<EMAIL_ADDRESS>wrote:

The files are in their own format and do not correspond to anything that
could be indexed.
Reloading models can be achieved using the ResourceWatcherService (see
https://github.com/elastic/elasticsearch/blob/master/server/src/main/java/org/elasticsearch/watcher/ResourceWatcherService.java
)
If you want to work on that, I'll be happy to assist and review the PR.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/spinscale/elasticsearch-ingest-opennlp/issues/23#issuecomment-370975640,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADGsjHIufKuad9lPMVXowXvcs9SDMVCuks5tbyW7gaJpZM4SfmVY
.

oh, then you need to make the MODEL_FILE_SETTINGS dynamic and add a cluster state listener so you can do reloading there

Is there any chances to have this feature in near feature?
requirement to restart the cluster in order to apply changes/extend list of models files makes plugin incompatible with any production clusters that continiously receive realtime events and used for others purposes so restart in order to reconfigure just one plugin is unacceptable in that case.
Thanks for a great plugin!

I am happy to accept pull requests and guide other people towards a well tested implementation, but I do not intend to work on this in the near future myself.


Approve merge with MDL

I would like to use a MDL date-picker, then I saw that you have worked out a PR, which is very nice! But it seems that you told MDL team not to merge due to bug fixes. Your issue tracker only has 1 issue labeled as bug, and that is already a few months old. In addition, I tried out your demo and didn't really find any bugs (Firefox 47.0, Windows 10). If that issue is solved, perhaps you could greenlight the merge with MDL? Thank you for creating this component. Let me know if there is anything I can help with to speed up the process.

It took me some time to do it, but PR finally submitted.


CIA-282: Remove hardcoded serverspec dir from rakefile template

Addresses #85.
Passes serverspec_dir through to rakefile template and uses that config value.

Question: What if serverspec_dir is not specified? During the rakefile file generation as the path would start with /. Maybe we should have a default value for it?

@rgreinho we set a default in molecule's config. Is that enough?
https://github.com/metacloud/molecule/blob/master/molecule/conf/defaults.yml#L13

Question: What if serverspec_dir is not specified? During the rakefile file generation as the path would start with /. Maybe we should have a default value for it?

The default is spec.  You can override this as @abrown-sg pointed out.

:+1:

That's perfect :) :+1: too


🐛 Fix SQLAlchemy version 1.4.36 breaks SQLModel relationships (#315)

Can we add unit tests ?

What would be a good test? I don't know how to write tests for different SA versions.

I guess just a test for relationships would work, then it breaks if the SA version is not compatible, and succeeds when yes.

OK, but there are plenty of those already. It would be nice if we could prove that it works for both 1.4.36 and older versions of SQLAlchemy.

Right - apparently tests just have not been run in Github Actions in 16d so the breakage does not show.
I don't think a test in itself can define the lib version but that would require something more, maybe like a branch where a different SA version is pinned.

Running tests without the fix results in broken tests, running with fix all tests pass. You can run them locally to verify

Any updates on when this will be merged?

@tiangolo Can you take a look at this, please? It is nasty that you have to pin the version of sqlalchemy at the moment. It would be nice if you could make a release after the merge so that the current version of sqlalchemy can be used again.

In this PR (https://github.com/leynier/sqlmodel/pull/37) pointing to a fork, you can see that the tests are successful. I think that It is not necessary to add extra tests for this PR because the existing tests validate the change since without the change of this PR the tests fail.

Awesome, thank you @byrman! :bow: :rocket:
And thanks everyone for the discussion.
This will be available in the next version, in the next hours. :tada:


Tweaked KBM comment, removed redundant assignment, and avoid sending key up for one case when not necessary

Summary of the Pull Request
What is this about?
This PR makes the tweaks mentioned in the title, found when writing the documentation for KBM.

Corrected a comment
Removed redundant assignment to isShortcutInvoked
Send key up for target key only if it is pressed (since action key can be released without resetting the state).

PR Checklist

[ ] Applies to #xxx
[ ] CLA signed. If not, go over here and sign the CLA
[X] Tests passed
[ ] Requires documentation to be updated
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Info on Pull Request
What does this include?
Validation Steps Performed
How does someone test & validate?
Tests passed. This should be sufficient.
For extra validate, try remapping Win+Ctrl+A->B and check that pressing Win+Ctrl+A, releasing A, Ctrl, then Win works fine and start menu doesn't appear. Also check that pressing Win+Ctrl+A then releasing Win while Ctrl+A is still held selects all text in text editor.

@arjunbalgovind .  With regards to 'Send key up for target key only if it is pressed (since action key can be released without resetting the state).'  Can you think of scenario that could be reproduced with out these changes, so we can reaffirm that we need these changes?

@arjunbalgovind . With regards to 'Send key up for target key only if it is pressed (since action key can be released without resetting the state).' Can you think of scenario that could be reproduced with out these changes, so we can reaffirm that we need these changes?

@ryanbodrug-microsoft, the scenario is the case I mentioned in the validation steps,
If you remap Win+Ctrl+A->B, when you press Win, Ctrl, A, the OS sees B as being pressed. Then when you release A the OS will no longer see B as being pressed (B key up is sent) . On releasing Ctrl, a key up for B was being sent again at this stage (whereas it wasn't actually required).
We still need to send it in some cases, such as you press Win, Ctrl, A and then release Ctrl. In this case key up needs to be sent for B since we are reverting back to the physical keys.

Shouldn't this PR have an associated Issue?

Shouldn't this PR have an associated Issue?

I had created the PR as I found a bug while working on the docs. I'll make an issue for it and link to it,


[Feature] - Spell checking for the data files

What feature would you like to see?
We are going to be using spellchecker-cli with husky to check to see if all the words are spelled correctly prior to committing. I don't know if there are any remaining flaws in their dependencies' or dependencies' dependencies but I will keep my eyes peeled.

Can we put this on hold till the developers behind Spell-checker CLI fix their punctuation issue?

Sure. You can just close the draft PR you have and then open it again later.

It'll be a while before this issue is ready to be tackled.


Mogg Preview

Adapt the song preview to work with moggs.

Might even try to disable this, as this probably is added strain on the server.


Java.net.SocketTimeoutException when running a feature file in Karate

When running my feature file i get this error.
java.lang.RuntimeException: java.net.SocketTimeoutException: Read timed out
I have tried to add a readTimeout by i get the same exception all the time.
* configure readTimeout = 10000

@Abigail-1992 please look at this links. https://stackoverflow.com/questions/33227244/how-the-sockettimeoutexception-occurred?noredirect=1&lq=1
https://stackoverflow.com/questions/17079273/java-net-sockettimeoutexception-read-timed-out-under-tomcat?noredirect=1&lq=1
Please post your issue (feature file) and other code you are executing, if any, in stackoverflow. And make sure to use guidelines when posting questions in stackoverflow. Also use tags like 'karate' while you post your query.

Thanks kodlist for your answer.
I have tried adding timeouts (2400000 ms) but the exception is always displayed.

do me a favor. please report your issue on stackoverflow.. with karate tag. and make sure to use guidelines, so you wont lose points. i will keep checking your issue on stackoverflow. and will answer as soon as i can.

@Abigail-1992 there is no use commenting here unless you follow this process: https://github.com/intuit/karate/wiki/How-to-Submit-an-Issue


Fixes URL for GET request

API for issues and pull_request comments is /repos/#{owner}/#{repo}/pulls/#{number}/comments
cf. https://developer.github.com/v3/pulls/comments/
GET /repos/:owner/:repo/pulls/:number/comments

Thank you! I will merge asap. Atm my home internet is gone and it may take few days for it to be fixed. Will merge when I get online again.

Great - thanks! Enjoy the disconnected time.
On Thu, Jan 26, 2017 at 6:55 AM, Piotr Murach<EMAIL_ADDRESS>wrote:

Thank you! I will merge asap. Atm my home internet is gone and it may take
few days for it to be fixed. Will merge when I get online again.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/piotrmurach/github/pull/294#issuecomment-275393407,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACHPgzgUKNe6Uzu6nbW3wCbarhjhqPmks5rWKXhgaJpZM4Lt2_C
.

Thanks :heart:


Existing or new added widgets can not be selected

Describe the bug
Existing or new added widgets can not be selected
To Reproduce
Steps to reproduce the behavior:

Update to vis2 v2.0.18
Existing widgets or new widgets can not be selected to change the settings and widget can not be moved

Expected behavior
Widget can be selected by mouse click
Screenshots & Logfiles
There is no output during this error in the browser console.

Versions:

Adapter version: vis2 v2.0.18

Exactly this error I tried to fix in 2.0.18

@GermanBluefox
The new widgets vis 2 -material widgets + Messgeräte + Energie Widgets are not affected of this issue.
But if I drag e.g. the widget "jqui botton link" or one of the map widgets in my view the bug is there.

Fixed in 2.0.19

Issue is fixed with 2.0.19
Thanks :-)


NEW RELEASE 1.0

Photon 1.0 RELEASE
Dear Photon User!
I am very proud to announce the release of Photon version 1.0! You are a follower of Photon and maybe you already know my extension framework „PhotonKit Components“ that extends the original Photon project on a high level. Sadly the original developer @connors was not abled to accept my contributions or answer me at least one time because he seems to be inactive since more than 2 years. This is very sad because Photon is a great tool to design native looking UI’s and there was a lot to do.
I was the only active developer who still keeps the project up to date.

Somedays I thought about the future of the project and the last commitment of @connors was 2 years ago. I realised that the only solution for the future of the project would be a complete new version 1.0
This release is a hard fork of the original project that redefines everything hardly and replaces the PhotonKitComponents project I made.
Getting Started
npm install electron-photon

Just have a look at the „ShowReel“ application or ask me for questions ;-)
GitHub
NPM
Questions? Ideas?
<EMAIL_ADDRESS>Kind regards,
Maurice Conrad

Thank you!

Thank you, this are great news!

Nice work man!

Thank you for your efforts but why did you gather our emails and spam?

@burakcan Sorry, I sent the stargazers of the original repo an email, of course you are a part of them. This is not totally great for the people who already read this post, I know... But I cannot exclude several mail addresses from a  list of 3385 addresses.

I don't believe those stargazers gave you permission to spam them?


check ISO 8601 duration

DANDI archive requires that Species.age be ISO 8601 duration format. We should check that it is. This can be done in json-schema with regex. There might be an easier way.

https://github.com/catalystneuro/neuroconv/blob/9999f7a4082846f716d1abc9edf2db9ed6587b7c/src/neuroconv/schemas/base_metadata_schema.json#L121


Codecov Report

Merging #11242 (36428f0) into master (e7e2aff) will increase coverage by 0.00%.
The diff coverage is 0.00%.

@@            Coverage Diff            @@
##           master   #11242     +/-   ##
=========================================
  Coverage    0.11%    0.11%
=========================================
  Files        2229     2174     -55
  Lines      119824   117278   -2546
  Branches    18126    17820    -306
=========================================
  Hits          137      137
+ Misses     119667   117121   -2546
  Partials       20       20

Flag
Coverage Δ

integration1temurin11
?

integration1temurin17
?

integration1temurin20
?

unittests1temurin17
?

unittests1temurin20
?

unittests2temurin11
?

unittests2temurin17
0.11% <0.00%> (-0.01%)
:arrow_down:

unittests2temurin20
?

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

Files Changed
Coverage Δ

.../core/query/reduce/filter/PredicateRowMatcher.java
0.00% <0.00%> (ø)

... and 57 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Update README.md

Emojis were added, and text was streamlined to create a friendlier, more engaging tone. Section titles were also reorganized for easier navigation and visual appeal.

Thank you so much for accepting my proposed changes! I’m thrilled to know that my contributions could add value to the project. Your feedback and collaboration make all the difference, and I’m excited to continue working together to make this even better. Thanks again for your support — looking forward to the next steps!


Changed config.toml from v1.17 to v1.18

As a part of Kubernetes 1.18 release work.
Signed-off-by: vineeth<EMAIL_ADDRESS>@jimangel @zacharysarah

sorry @zacharysarah accidentally I deleted this branch creating another PR on the same changes.
Here is the PR https://github.com/kubernetes/website/pull/18557


Update common-jvm dep to 0.71.2.

This fixes stack traces not being included in structured logging.

This change is

Based on #1371


Crash in com.google.crypto.tink

Describe the bug?
Okta android sdk com.okta.authfoundation has a hard dependency on com.google.crypto.tink, and there seems to be some bug in this crypto library, we are seeing many crashes.
Basically DeviceTokenProvider and SharedPreferencesTokenStorage are using com.google.crypto.tink, so whenever any crash happens in google's lib, our app will crash.
here's a stack trace
Caused by android.security.KeyStoreException
Signature/MAC verification failed
android.security.KeyStore2.getKeyStoreException (KeyStore2.java:356)
android.security.KeyStoreOperation.handleExceptions (KeyStoreOperation.java:78)
android.security.KeyStoreOperation.finish (KeyStoreOperation.java:127)
android.security.keystore2.KeyStoreCryptoOperationChunkedStreamer$MainDataStream.finish (KeyStoreCryptoOperationChunkedStreamer.java:228)
android.security.keystore2.KeyStoreCryptoOperationChunkedStreamer.doFinal (KeyStoreCryptoOperationChunkedStreamer.java:181)
android.security.keystore2.AndroidKeyStoreAuthenticatedAESCipherSpi$BufferAllOutputUntilDoFinalStreamer.doFinal (AndroidKeyStoreAuthenticatedAESCipherSpi.java:396)
android.security.keystore2.AndroidKeyStoreCipherSpiBase.engineDoFinal (AndroidKeyStoreCipherSpiBase.java:603)
javax.crypto.Cipher.doFinal (Cipher.java:2113)
com.google.crypto.tink.integration.android.AndroidKeystoreAesGcm.decryptInternal (AndroidKeystoreAesGcm.java:118)
com.google.crypto.tink.integration.android.AndroidKeystoreAesGcm.decrypt (AndroidKeystoreAesGcm.java:101)
com.google.crypto.tink.KeysetHandle.decrypt (KeysetHandle.java:919)
com.google.crypto.tink.KeysetHandle.readWithAssociatedData (KeysetHandle.java:804)
com.google.crypto.tink.KeysetHandle.read (KeysetHandle.java:785)
com.google.crypto.tink.integration.android.AndroidKeysetManager$Builder.readMasterkeyDecryptAndParseKeyset (AndroidKeysetManager.java:381)
com.google.crypto.tink.integration.android.AndroidKeysetManager$Builder.build (AndroidKeysetManager.java:297)
androidx.security.crypto.EncryptedSharedPreferences.create (EncryptedSharedPreferences.java:169)
com.okta.authfoundation.client.DeviceTokenProvider. (DeviceTokenProvider.kt:47)
com.okta.authfoundation.client.DeviceTokenProvider. (DeviceTokenProvider.kt:1)
com.okta.authfoundation.client.DeviceTokenProvider$Companion.initialize$auth_foundation_release (DeviceTokenProvider.kt:38)
com.okta.authfoundation.client.DeviceTokenInitializer.create (DeviceTokenInitializer.kt:23)
com.okta.authfoundation.client.DeviceTokenInitializer.create (DeviceTokenInitializer.kt:21)
androidx.startup.AppInitializer.doInitialize (AppInitializer.java:180)
androidx.startup.AppInitializer.discoverAndInitialize (AppInitializer.java:238)
androidx.startup.AppInitializer.discoverAndInitialize (AppInitializer.java:206)
androidx.startup.InitializationProvider.onCreate (InitializationProvider.java:45)
android.content.ContentProvider.attachInfo (ContentProvider.java:2404)
android.content.ContentProvider.attachInfo (ContentProvider.java:2374)
android.app.ActivityThread.installProvider (ActivityThread.java:7459)
android.app.ActivityThread.installContentProviders (ActivityThread.java:6976)
android.app.ActivityThread.handleBindApplication (ActivityThread.java:6747)
android.app.ActivityThread.access$1500 (ActivityThread.java:256)
android.app.ActivityThread$H.handleMessage (ActivityThread.java:2091)
android.os.Handler.dispatchMessage (Handler.java:106)
android.os.Looper.loopOnce (Looper.java:201)
android.os.Looper.loop (Looper.java:288)
android.app.ActivityThread.main (ActivityThread.java:7870)
java.lang.reflect.Method.invoke (Method.java)
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:548)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1003)
What is expected to happen?
No crash
What is the actual behavior?
The app crashes
Reproduction Steps?
It's not a always-happening issue, it happens sometimes, but often.
Additional Information?
We've been working with Okta support and we've figured out it's google's lib issue.  it's blocking us from using Okta's sdk to do authentication.
SDK Version and Artifact(s) used.
com.okta.kotlin:auth-foundation: 1.1.5
com.okta.kotlin:auth-foundation-bootstrap:1.1.5
com.okta.android:idx-kotlin: 2.2.0
Build Information
No response

Hi @xiaoqian0408, thanks for reporting this issue. Unfortunately this continues being an issue in the Google library, and I'm not sure when that will be resolved. Here are steps for a workaround currently:

You can block DeviceTokenInitializer from running by setting the following in your AppManifest.xml under the "application" section:

        <provider
            android:name="androidx.startup.InitializationProvider"
            android:authorities="${applicationId}.androidx-startup"
            android:exported="false"
            tools:node="remove">
            <meta-data android:name="com.okta.authfoundation.client.DeviceTokenInitializer"
                android:value="androidx.startup" />
        </provider>

Set AuthFoundationDefaults.cookieJar = CookieJar.NO_COOKIES before creating OidcConfiguration
Create a custom implementation of TokenStorage, and initialize CredentialBootstrap with CredentialBootstrap.initialize(oidcClient.createCredentialDataSource(customTokenStorageInstance)). You could create a similar implementation to existing SharedPreferencesTokenStorage with a different storage than EncryptedSharedPreferences.

These steps should allow you to completely bypass using EncryptedSharedPreferences. I am looking into reimplementing TokenStorage as well, but that will take some time. I hope this workaround will do the trick for the time being.

@rajdeepnanua-okta great, thanks.
regarding

I am looking into reimplementing TokenStorage as well

do you mean the crypto lib crash will be fixed in our new implementation?
thanks

@rajdeepnanua-okta would it be possible to allow lazy load of the DeviceTokenInitializer.
Currently it just crashes our app.
That way we can gracefully handle the failure until a long term fix is available?
Thanks.

@rajdeepnanua-okta great, thanks.
regarding

I am looking into reimplementing TokenStorage as well

do you mean the crypto lib crash will be fixed in our new implementation?
thanks

The crypto lib crash should be fixed with the new implementation, that is correct.

@rajdeepnanua-okta would it be possible to allow lazy load of the DeviceTokenInitializer. Currently it just crashes our app. That way we can gracefully handle the failure until a long term fix is available? Thanks.

Hi @nishant-mehta, steps 1 and 2 in this comment: https://github.com/okta/okta-mobile-kotlin/issues/270#issuecomment-1796514852 should cause DeviceTokenInitializer to not execute. Please make sure your AndroidManifest.xml has imported the tools schema like so: <manifest xmlns:android="http://schemas.android.com/apk/res/android"     xmlns:tools="http://schemas.android.com/tools">
You might also need to import androidx.startup:startup-runtime in your app's build.gradle.

Does this mean adding the manifest change and  setting AuthFoundationDefaults.cookieJar = CookieJar.NO_COOKIES  will fix the crash for time being

Hi @ABr751, I saw your other reported issue, and yes I believe this should fix your crash. You might run into a similar crash in SharedPreferencesTokenStorage since that makes use of the same library.

@rajdeepnanua-okta So what exactly should be  done to avoid this  crash in SharedPreferenceTokenStorage?

@ABr751, if you run into the same issue in SharedPreferencesTokenStorage, unfortunately there's not much you can do at the moment. I am working on creating a new implementation of TokenStorage without this issue. I will update this issue once that's completed.


Feature/fragment processing failure handling

IMPLEMENTATION IN PROGRESS
Description
Implementation of #466
Motivation and Context

Screenshots (if appropriate)
Upgrade notes (if appropriate)

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

I hereby agree to the terms of the Knot.x Contributor License Agreement.

Features implemented so far:
1. Simple blank fallback
just add knotx-data-fallback="BLANK" to your snippet:
<knotx-snippet data-knotx-knots="databridge,handlebars"
  data-knotx-databridge-name="unstable-service"
  data-knotx-fallback="BLANK">
      {{#if _result}}
{{_result.count}}
{{/if}}
</knotx-snippet>

2. Static markup fallback
create a fallback snippet with data-knotx-fallback-id attribute and point to it in your snippet:
<knotx-snippet data-knotx-knots="databridge,handlebars"
  data-knotx-databridge-name="unstable-service"
  data-knotx-fallback="CUSTOM">
      {{#if _result}}
{{_result.count}}
{{/if}}
</knotx-snippet>
<knotx:fallback data-knotx-fallback-id="CUSTOM">

error

</knotx:fallback>

3. Global blank fallback
to apply BLANK fallback to all snippets by default configure defaultFallback attribute within snippetOptions - apply these to both Splitter and FragmentAssembler.
  snippetOptions {
    tagName = knotx-snippet
    paramsPrefix = data-knotx-
    defaultFallback = BLANK
    ]
  }

4. Global fallback with custom markup
to apply custom markup fallback to all snippets by default:

configure defaultFallback attribute within snippetOptions
define your own fallbacks property within snippetOptions
apply these to both Splitter and FragmentAssembler.

  snippetOptions {
    tagName = knotx-snippet
    paramsPrefix = data-knotx-
    defaultFallback = CUSTOM_GLOBAL
    fallbacks = [
      {
        id = CUSTOM_GLOBAL
        markup = "<knotx:fallback data-knotx-fallback-id='CUSTOM_GLOBAL'>
error
</knotx:fallback>"
      }
    ]
  }

5. fallback with custom FallbackStrategy
you can deliver your own class that will be fired by the assembler if given fragment fails

implement FallbackStrategy interface

import io.knotx.dataobjects.Fragment;
import io.knotx.dataobjects.KnotContext;
import io.knotx.fallback.FallbackStrategy;

public class MyFallbackStrategy implements FallbackStrategy {

  @Override
  public String getId() {
    return "CUSTOM_STRATEGY";
  }

  @Override
  public String applyFallback(Fragment failed, Fragment fallback, KnotContext knotContext) {
    return "
markup
";
  }
}

make sure that ServiceLoader can discover this class - add its fully qualified name to /META-INF/services/io.knotx.fallback.FallbackStrategy file.
create a custom fallback snippet with linked strategy Id

<knotx-snippet data-knotx-knots="databridge,handlebars"
  data-knotx-databridge-name="unstable-service"
  data-knotx-fallback="CUSTOM">
      {{#if _result}}
{{_result.count}}
{{/if}}
</knotx-snippet>
<knotx:fallback data-knotx-fallback-id="CUSTOM" data-knotx-fallback-strategy="CUSTOM_STRATEGY">

error

</knotx:fallback>

I am wondering if this tag data-knotx-fallback="BLANK" is really required. We can assume that if there is no data-knotx-fallback-id tag defined, then the default fallback mechanism should handle the snippet.

According to 5:
We agreed that a fallback strategy should be configured as a chain, something like:
"fallbackStrategies": [
   { "name": "CUSTOM", conf":"{next:"DEFAULT"" }},
   { "name": "DEFAULT", "conf":"EMPTY" }
]

In that way our fallback strategy implementation should pass the flow to the next fallback. I thought about something similar to io.knotx.server.handler.knot.KnotEngineRoutingHandlerFactory.KnotxEngineHandler#handleRoute.

Can we move this comment to the SnippetFallback.md file - we could work on documentation in the same PR. We plan to move documentation from wiki to *.md files so it can be good option.

Please see my https://github.com/Cognifide/knotx/issues/466#issuecomment-435311790. I described there few implementation details that will make this solution easier to extend in the future.


breaks on servers

https://mclo.gs/Z7UNuOw

Maaaaaaaaaaay wanna post a log when you are only running the bare minimum of mods required to reproduce the crash, as a precaution. There may very well be some conflict, even if it only occurs in multiplayer.

I'll do a bare minimum test and send it later

https://mclo.gs/He8f6D2
shorter

dropped a considerable amount of mods but probably not the bare minimum. If you want me to go shorter I can

I found that the non-host client cannot access to ServerWorld. It's private and hidden in server unless I make a little server-side things to send it out. But this is not necessary for a pure client-side visual effect mod.
I'll disable pre-detect feature that depends on ServerWorld on non-host client.

So you'll have it completely disabled?
Or maybe have it disabled for now until maybe adding a function to detect if the mod is being used between client and server? So like if you have it on your own world it'd automatically detect that and enable the feature

Yep, pre-detect feature only runs when you play with integrated server now.
Specifically, you need in single play, or be the host in multiplayer to use this feature.

Would it be possible to install this mod server side then?

But this is not necessary for a pure client-side visual effect mod.

Wasn't sure if you meant you weren't going to have it as a server side or leave it as is

This mod is always client-side only.
---- Replied Message ----
| From | @.> |
| Date | 02/11/2023 11:50 |
| To | @.> |
| Cc | @.>、State @.> |
| Subject | Re: [Rivmun/SuperFancyCloudsRefabricated] breaks on servers (Issue #16) |
But this is not necessary for a pure client-side visual effect mod.
Wasn't sure if you meant you weren't going to have it as a server side or leave it as is
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.Message ID: @.***>

However, if you want to synchronize the cloud between clients connect to a same server (This is a very attractive feature that few mods can achieve it), open a new issue and I'll considering and learn how to do it.😀


⚠ Bofrost.de has degraded performance

In 0ef81d4, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1456 ms

Resolved: Bofrost.de performance has improved in 9a84e75 after 9 minutes.


liveReloadBaseUrl with absolute url no longer supported

In the past, we could use "liveReloadBaseUrl": "http://localhost:4200/" which is necessary for using ember-cli-deploy for a development workflow, i.e. accessing from http://localhost:3000/
However, with https://github.com/rwjblue/ember-cli-inject-live-reload/commit/3473a6479d65a73097a0ddb2e4298b714ed3cfad this no longer seems to work
Should this be
app.use((options.rootURL || options.baseURL) + 'ember-cli-live-reload.js', // ...

instead?

Hi, I'm the author of the mentioned commit.
There was a refactor before that commit (part of PR #28) and if you take a look at the full index.js file, you will see that:
var baseURL = options.liveReloadBaseUrl || options.rootURL || options.baseURL;
So if you set liveReloadBaseUrl if will be used. Do you say it shouldn't be used?
You said that it no longer seems to work. What are the symptoms? Do you get any errors or any unexpected output in HTML?

Thanks for the response @jgoclawski
To clarify, I'm using the ember-cli-deploy development workflow – index.html served on localhost:3000, ember server running on localhost:4200.
Previously (before your PR), using liveReloadBaseUrl: "http://localhost:4200/" would:

Inject <script src="http://localhost:4200/ember-cli-live-reload.js" type="text/javascript"> (when accessing from localhost:3000)

Because of app.use(options.baseURL + 'ember-cli-live-reload.js', serve the javascript via a relative path, i.e. app.use('/ember-cli-live-reload.js'

This allowed livereload to be served on http://localhost:4200/ember-cli-live-reload.js even when accessing from http://localhost:3000/index.html
With this change to use options.liveReloadBaseUrl, using absolute paths in liveReloadBaseUrl no longer work, because AFAIK app.use doesn't intercept absolute paths, i.e. point (2) above becomes app.use('http://localhost:4200/ember-cli-live-reload.js'

What are the symptoms?

The script is injected but I get a 404 for ember-cli-live-reload.js (because it's not being intercepted)

Do you say it shouldn't be used?

Perhaps using absolute paths in liveReloadBaseUrl was never intended and it worked by mistake in the past. If it's intended to work, perhaps liveReloadBaseUrl should be converted to a relative path before app.use?
Let me know if this makes sense? If needed I can try creating a repo to illustrate

Would https://github.com/ember-cli/ember-cli-inject-live-reload/pull/36 solve your problem?

@lukemelia yes, thanks -- tested and it works

@lukemelia test failed because now we have the same problem as #35

@pieter-v I did face above as well, but I think it's a separate issue, and can be dealt with in the meantime by defining "liveReloadOptions" in .ember-cli

@wongpeiyi  thanks specifying the 'liveReloadOptions' solved the problem

Closing (seems like #25, #36 and #40 should have fixed the various issues being discussed).

It looks like this was closed because (partially) #36 addresses the problem, however #36 is still open. Since #36 isn't merged/released yet, is there any way around this issue?

Ah, I misread a comment above. Pinning to 1.4.0 gets this working with liveReloadBaseUrl set appropriately. It'd be great to run the latest release and still have this functionality though!


goroutine 7 [running]

What is the issue?
Hello.
I am testing with olama. Using olama, the embedded model and LLM model are on gpu. As soon as you enter the question, the embedded and LLM models are sequentially performed.
And since we built a web server using streamlit, we have to handle a lot of question inputs. We ran the olama server by adding an option to quickly process a large number of requests using olama. The commands used to run the server are as follows. CUDA_VISIBLE_DEVICE=1 OLAMA_GPU_OVERHEAD=500000000 OLAMA_NUM_PARALLEL=11 OLAMA_KEEP_ALIVE=-1 olama service
Run the streamlit app and access the web server to input and answer questions well. However, at an unspecified time, olama outputs the following message.
The first picture is ollama 0.4.2, and the second picture is a message picture that occurred when using ollama 0.4.6.
In 0.4.2, the answer is not answered only when the error message has occurred, and the next question is generated again. However, after the error message in 0.4.6, the olama lm model is deallocated from gpu memory and the olama server is also stopped. For reference, the same phenomenon as 0.4.6 occurs in all 0.4.3 to 0.4.5.

OS
Docker
GPU
Nvidia
CPU
Intel
Ollama version
0.4.6, 0.4.2

Can you please post the full server log from when you run into the issue on 0.4.6? There's not enough context in the screenshot.
How consistently can you reproduce it?


feat: call method

Purpose of this PR

Testing status

No tests have been added.
Includes unit tests.
Includes performance tests.
Includes integration tests.

Manual testing status

Comments to reviewers

Hi! Well, first of all, thank you for your contribution!
Unfortunately, this solution is incorrect for the following reasons:

Your InspectorButton attribute can't be applied to the method itself. Its AttributeUsage is set to AttributeTargets.Field. Thus, it can be applied to the class fields only.
If you introduce the proper attribute with AttributeTargets.Method usage, this task is unsolvable with the custom PropertyDrawer.

It's cool though, that you managed to implement Playmode & EditorOnly modes for method invocation.
If you want to do another iteration on this - you can do it in another pull request.
Thank you for your contribution!
P.S. If you can give a bit more love to the pull request description next time, that would be awesome.


failureInInitialization

Running BurpSuite 2.0.16beta and just started getting "failureInInitialization" in the SAML Raider tab in the HTTP History > Request section.
The Extender > Extensions > Errors is spitting out:
java.lang.RuntimeException: java.lang.NoSuchMethodError: com.sun.org.apache.xml.internal.serialize.OutputFormat.(Lorg/w3c/dom/Document;)V
I've tried re-installing the Extension.
FWIW, running java -version on the BurpSuite Pro JRE gives me:
openjdk version "11.0.2" 2019-01-15

Update: attempting to build the app with Maven fails as well, using Oracle JDK 11.0.2 / Maven 3.6.0.
[ERROR] /D:/temp/saml_raider/SAMLRaider/src/main/java/model/BurpCertificateStore.java:[60,88] incompatible types: java.util.Enumeration<javax.swing.tree.TreeNode> cannot be converted to java.util.Enumeration<javax.swing.tree.DefaultMutableTreeNode>
[ERROR] /D:/temp/saml_raider/SAMLRaider/src/main/java/model/BurpCertificateStore.java:[98,88] incompatible types: java.util.Enumeration<javax.swing.tree.TreeNode> cannot be converted to java.util.Enumeration<javax.swing.tree.DefaultMutableTreeNode>
[ERROR] /D:/temp/saml_raider/SAMLRaider/src/main/java/helpers/XMLHelpers.java:[94,39] no suitable constructor found for OutputFormat(org.w3c.dom.Document)
constructor com.sun.org.apache.xml.internal.serialize.OutputFormat.OutputFormat() is not applicable (actual and formal argument lists differ in length)
constructor com.sun.org.apache.xml.internal.serialize.OutputFormat.OutputFormat(java.lang.String,java.lang.String,boolean) is not applicable (actual and formal argument lists differ in length)

Thanks for the update. I'll also fix that in the next release.

Hi buddy, I do have a fix for this issue, simply using another package for achieving that stuff. However, I need to make sure the fix will not break other things: currently I am not able to edit the SAML body. I can click, highlight, do whatever but I cannot type into the repeater tab where SAML Raider is loaded.
Do you have any input on that ?


(BUG) IOS: The pending/daily income pop-ups  are displayed with a big icon

Steps to reproduce:

Open the pending/daily income pop-up
Pay attention to the big icon (reproduce only for IOS)

Actual result: The pending/daily income pop-ups  are displayed with a big icon
Expected result: The pending/daily income pop-ups  should be displayed with a small icon
Note: The "From/To" text should be displayed within one line and without cropped as you can see this on the screenshot (reproduce for Android and IOS)
Checked on Dev env (V 0.20.0)
The device used:
LG V30+ // Android 8.0 // Google Chrome 81.0.4044.117
iPhone 8 Plus // iOS 13.1.3 // Google Chrome 80.0.3987.95
IOS screenshot:

Android screenshot:

Verified as done.
Dev env v0.20.1
Checked on the
iPhone 6S+ // iOS 12.4


TensorBoard Callback write_grads fails when using LSTM and embedding layer

[x] Check that you are up-to-date with the master branch of Keras. You can update with:
pip install git+git://github.com/fchollet/keras.git --upgrade --no-deps

[x] If running on TensorFlow, check that you are up-to-date with the latest version. The installation instructions can be found here.

[ ] If running on Theano, check that you are up-to-date with the master branch of Theano. You can update with:
pip install git+git://github.com/Theano/Theano.git --upgrade --no-deps

[x] Provide a link to a GitHub Gist of a Python script that can reproduce your issue (or just copy the script here if it is short).

The following error occurs when the TensorBoard callback is used and has write_grads=True with an embedding layer.
TypeError: Failed to convert object of type <class 'list'> to Tensor. Contents: [<tensorflow.python.framework.ops.IndexedSlices object at 0x7ff93c4a00f0>]. Consider casting elements to a supported type.

Code which can reproduce this:
from keras.models import Sequential
from keras.layers import Embedding, LSTM, Dense
from keras.callbacks import TensorBoard
import numpy as np

SEQUENCES = 5
TIME_STEPS = 10

model = Sequential()
model.add(Embedding(100, 4))
model.add(LSTM(32))
model.add(Dense(1))
model.compile(optimizer='rmsprop', loss='mse')

tensor_board = TensorBoard(log_dir='log', batch_size=2, write_graph=False,
                           write_grads=True, histogram_freq=4)

x_train = np.random.randint(100, size=(SEQUENCES, TIME_STEPS), dtype='int8')

y_train = np.random.rand(SEQUENCES)

model.fit(x_train, y_train, batch_size=2, epochs=4, shuffle=True, callbacks=[tensor_board])

Note, by simply setting write_grads=False, no errors occur.
I am running this with a GPU (GTX 1070) on Manjaro Linux. cuda 8.0.61-2, cudnn 6.0.21-2. Tensorflow back-end.
Hope this helps.

same situation, please help


Scene loads, but no vectors created and other issues

Following the steps on the README and getting pinecone, clerk, and convex all setup for the first time. Characters seem to move around, but things seem to be partially broken. I'm expecting to be able to see conversations happening between the characters at least, but I only see their intro text. There was a message about "sign in to view messages" and after I do that, the "sign in" message disappears, but I don't see any conversations still.

First thing I noticed was an authentication error in the JS, but I DO see my google account photo in the upper right hand corner, so not clear if that's actually an issue. I turned off all shields in brave and repeated the login process, but still get the same thing.

There was an issue with free pinecone I guess (noticed the closed PR related to the error). I un-commented the lines from convex/lib/pinecone.ts with the diff linked in the ticket, which resolved the immediate errors when running npm run dev it seemed, but I'm still getting errors here and there of a similar (cryptic) sort.

I also notice that pinecone has zero vectors, so I'm guessing this is related.

Looking at the embeddings in convex, they were added earlier it seems, but not recently..

Same thing for memories..

Any ideas?

Ah, Looks like I used the wrong name for my pinecone index name.. (Used the key name, not the index name).  I'm not getting that error anymore, but still not seeing anything in pinecone... just these messages.

I'm trying npx convex run init:reset but getting an error when I try that.
$ npx convex run init:reset
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
- Preparing Convex functions...

√ 22:24:56 Convex functions ready! (4.43s)
✖ Failed to run function "init:reset":
Error: Uncaught Error: Error: Not implemented: get body for Response: Try using .text(), .json(), blob(), or .arrayBuffer() instead. Consider calling an action defined in Node.js instead (https://docs.convex.dev/functions/actions).

    at async handler (../convex/init.ts:103:2)

OK - I misread this commit. Looks like these lines were meant to be commented out and my mistake with the pinecone index name just happened to cause a similar error. I undid those changes and now this succeeds.
npx convex run init:reset --no-push
.. and I'm seeing 17 vectors now in pinecone (note to others, the UI can take a second to load and show the correct amount on pinecone. Until then it shows 0)
For some reason after this, it took almost 10 minutes more before it started showing conversations, but it is doing that now finally. I see pinecone upserts and queries finally happening. Also convex logs are showing non-zero numbers.  Hope this helps someone else if they need to debug as well.

Sorry this was so much trouble!
Pinecone used to support namespaces on starter plans, which is what I was developing with, but it seems they've made those paid-only for newer indexes.
the init:reset will add a new world and kick off the pinecone inserts.
As for the 10 minute delay: my guess is something failed hard when processing a batch of agents, and they got stuck in a "thinking" state. Each agent will only be processed in one batch at a time, but there's a cron job that runs that checks if any agent has been thinking for >10min and resets them. There is a try/except in the action that processes the batch and tries to do cleanup by just having them walk away, but if there was another exception when trying to walk, then it could get stuck.
If you find a root cause it'd be great to know what to fix.

Sorry this was so much trouble!
No worries! Thanks to the team for creating this and I certainly didn't help matters by getting the Pinecone setup wrong.

A couple suggestions to help folks like me contribute and debug, but feel free to close this ticket as well:

Having a high-level flow/component diagram of what things are doing would be helpful. Obviously we can read the code, but I notice there are even some principals you posted on the discord already that could be codified into an FAQ or something. I get things are moving fast and this might be premature, but it would certainly help grok the architecture, especially the flow of a batch of agents, etc.
In lieu of that, the readme has one-word summaries of the third party services being used, but expanding on that a little bit would also help to understand when things go wrong where to focus on.
Finally a related topic is error reporting. Seems the serverless functions on Convex either don't respond with a helpful error messages  (in the Convex logs) or the functions themselves are not catching errors from like Pinecone and passing them through.

Thanks again for your work here, excited to see projects like this advance and I'll look for more ways to contribute!


Configurable enum

see #24

[x] Add the 2 configurable enum classes to the source code
[x] Add testing for those two classes
[x] Add more documentation about usage and examples
[x] Add enum autoconfiguration within the bundle extension

@J-Ben87 what do you think ?

I like it! You allowed the different solution in a non intrusive way, I can't think of a better solution.

What about the documentation ? Do you think it is clear enough ?

I think so. Maybe because I already know how to use it, but it seems pretty clear. You detailed all the ways to declare enums, how to integrate it with Sonata...
Maybe you could add a little note on how to use it in forms without type guessing, or on how to use the translated enum.

Just added more documentation, and fixed some important inconsistent issues with namespaces (from symfony 3 to symfony 4 conventions)


lost the ability to pass -f json for json output

tower-cli 3.0.3:
[notting@nostromo: ~/prog/tower-populate]$ tower-cli job_template get 13 --format json
{
  "id": 13,
  "type": "job_template",
  "url": "/api/v1/job_templates/13/",
  "related": {
...

tower-cli 3.1.1:
[notting@nostromo: ~/prog/tower-populate]$ tower-cli job_template get 13 --format json
Error: no such option: --format

We experience the same, that's an major issue not visible in the release notes and at the moment blocking us massively.

@sebastiangraf @wenottingham Thx for the feedback. That's a issue introduced by 3.1.1 and so sorry about the problem caused.
We've patched that up and it will ship with 3.1.2. For now two workarounds are available:

Directly set up config file, please see instructions here.
Use master branch with patch added.

The fix has been shipped in release 3.1.2, which is on PyPI now.

thanks a lot!


added a .editioconfig file to generate a consistent code style

This fixes the issue where my indentation defaults to tabs and not spaces. This should probably be customized by Fifty-Six and other very active maintainers of this project.

the commit should say .editorconfig and not .editioconfig

don't think it matters since it doesn't seem to affect the editor but better safe then sorry

Given that it's going to be customized, I'm just going to use the one from ReSharper.


⚠ ClamAV has degraded performance

In 1bd13d4, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 82 ms

Resolved: ClamAV performance has improved in a29ca20 after 541 days, 14 hours, 52 minutes.


Crash after taking photos with high-end iPhone camera ( > iPhone X )

Bug
When press the shoot button as soon as the camera opens, the app will be terminated with the following native code error. (maybe dual or triple camera)
 *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSDictionaryM setObject:forKey:]: object cannot be nil (key: data)'
*** First throw call stack:

Environment info
React native info output:
System:
    OS: macOS 10.14.6
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 742.69 MB / 16.00 GB
    Shell: 5.3 - /bin/zsh
  Binaries:
    Node: 10.19.0 - ~/.nvm/versions/node/v10.19.0/bin/node
    Yarn: 1.19.2 - /usr/local/bin/yarn
    npm: 6.13.4 - ~/.nvm/versions/node/v10.19.0/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
    Android SDK:
      API Levels: 28, 29
      Build Tools: 28.0.0, 28.0.1, 28.0.2, 28.0.3, 29.0.0, 29.0.1, 29.0.2
      System Images: android-28 | Android TV Intel x86 Atom, android-28 | China version of Wear OS Intel x86 Atom, android-28 | Wear OS Intel x86 Atom, android-28 | Intel x86 Atom, android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom, android-28 | Google Play Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom
  IDEs:
    Android Studio: 3.5 AI-191.8<IP_ADDRESS>77832
    Xcode: 11.2.1/11B500 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.9.0 => 16.9.0
    react-native: 0.61.5 => 0.61.5

Library version: 2.3.0(the latest)
Steps To Reproduce

launch camera

// Launch Camera:
ImagePicker.launchCamera(options, (response) => {
  // Same code as in above section!
});

press shoot button as soon as camera opens (black photo will be captured)
app crashes

Describe what you expected to happen:

The photo info will be passed normally

Reproducible sample code
      ImagePicker.launchCamera(options, response => {
        // Same code as in above section!
        alert(JSON.stringify(response));
      });

+1

Any solution to this?

This is also happening when selecting large photos from the image library on iOS with RN 0.61.5 and latest version of this package 2.3.0

+1

+1

I can reproduce a crash in the iOS simulator using the sample code slightly tweaked
Xcode Simulator
Version 11.4 (921.9)
SimulatorKit 581.9
CoreSimulator 704.12
package.json
    "react": "16.11.0",
    "react-native": "0.62.0",
    "react-native-image-picker": "^2.3.1",

In ImagePicker.showImagePicker I'm setting ImageType and ImageData
And in render:
{this.state.ImageData === null ? (
    <Text style={styles.imagePickerText}>Pic Required</Text>
  ) : (
    <Image
     style={styles.imagePicker}
     // source={{uri: this.state.ImageURI}} // This works
     source={{ uri: 'data:' + this.state.ImageType + ';base64,' + this.state.ImageData }} // This crashes
    />
  )}

Simulator Log Attached
SimulatorLog.txt

1.check the camera permission
2.add the code blow
// 返回选中相机图片后的正确路径
function getCameraImgUri(uri) {
return Platform.OS === 'android' ? uri : uri.replace('file://', '');
}
//拍照
ImagePicker.launchCamera(options, response => {
this.setState({ headerUrl: getCameraImgUri(response.uri) });
});

Same issue here, here's a stack trace from our analytics tool:
NSInvalidArgumentException *** -[__NSDictionaryM setObject:forKey:]: object cannot be nil (key: data)
    Frameworks/CoreFoundation.framework/CoreFoundation ___exceptionPreprocess
    /usr/lib/libobjc.A.dylib _objc_exception_throw
    Frameworks/CoreFoundation.framework/CoreFoundation __CFThrowFormattedException
    Frameworks/CoreFoundation.framework/CoreFoundation -[__NSDictionaryM setObject:forKey:].cold.2
    Frameworks/CoreFoundation.framework/CoreFoundation -[__NSDictionaryM setObject:forKey:]
    /Users/USER/Source_Code/Work/APP/node_modules/react-native-image-picker/ios/ImagePickerManager.m:390:17 __74-[ImagePickerManager imagePickerController:didFinishPickingMediaWithInfo:]_block_invoke
    PrivateFrameworks/UIKitCore.framework/UIKitCore -[UIPresentationController transitionDidFinish:]
    PrivateFrameworks/UIKitCore.framework/UIKitCore -[_UICurrentContextPresentationController transitionDidFinish:]
    PrivateFrameworks/UIKitCore.framework/UIKitCore ___56-[UIPresentationController runTransitionForCurrentState]_block_invoke.503
    PrivateFrameworks/UIKitCore.framework/UIKitCore -[_UIViewControllerTransitionContext completeTransition:]
    PrivateFrameworks/UIKitCore.framework/UIKitCore -[UITransitionView notifyDidCompleteTransition:]
    PrivateFrameworks/UIKitCore.framework/UIKitCore -[UITransitionView _didCompleteTransition:]
    PrivateFrameworks/UIKitCore.framework/UIKitCore -[UIViewAnimationBlockDelegate _didEndBlockAnimation:finished:context:]
    PrivateFrameworks/UIKitCore.framework/UIKitCore -[UIViewAnimationState sendDelegateAnimationDidStop:finished:]
    PrivateFrameworks/UIKitCore.framework/UIKitCore -[UIViewAnimationState animationDidStop:finished:]
    PrivateFrameworks/UIKitCore.framework/UIKitCore -[UIViewAnimationState animationDidStop:finished:]
    Frameworks/QuartzCore.framework/QuartzCore CA::Layer::run_animation_callbacks(void*)
    /usr/lib/system/libdispatch.dylib __dispatch_client_callout
    /usr/lib/system/libdispatch.dylib __dispatch_main_queue_callback_4CF$VARIANT$armv81
    Frameworks/CoreFoundation.framework/CoreFoundation ___CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__
    Frameworks/CoreFoundation.framework/CoreFoundation ___CFRunLoopRun
    Frameworks/CoreFoundation.framework/CoreFoundation _CFRunLoopRunSpecific
    PrivateFrameworks/GraphicsServices.framework/GraphicsServices _GSEventRunModal
    PrivateFrameworks/UIKitCore.framework/UIKitCore _UIApplicationMain
    APP/main.m:7:11 main
    /usr/lib/system/libdyld.dylib _start

Affected devices seem to be:
iPhone X
iPhone XR
iPhone 11
iPhone SE

Hey Bot, Is it fixed?

Same error here on iPhone 11.

Same error here on iPhone 11.

Same, on ios simulator when picking a image from gallery!

Never mind, my problem was due to Image component.
This issue

Any uploads on this issue?

+1

+1

Version 2.x.x is not longer supported, please upgrade to 3.x.x
I hope the issue is solved, create new issue with details I am happy to fix it.

Version 2.x.x is not longer supported, please upgrade to 3.x.x
I hope the issue is solved, create new issue with details I am happy to fix it.


What is the latest version?

The comments in the dist/ files and the changelog say 0.15.0, but the git tag says v0.16.0.

The latest release is v0.16.0 on both bower and npm
We will take a look at updating the changelog and dist files.


Delayed_job firing Mailer twice with .deliver

Running Rails 4.1.15 with delayed_job 4.0.1. When using a mailer, .deliver is no longer needed at the end of the call for the mailer to send the email. When running the mailer call without delay, only one email is sent even with .deliver in the method call (i.e. TestMailer.send_test_email.deliver sends one email). When the delay call is added (i.e. TestMailer.delay.send_test_email.deliver), the delayed_job worker sends the email twice.
Should the delayed_job worker work the same way as when the delay is not called?

https://github.com/collectiveidea/delayed_job#rails-3-mailers


Always picks up custom URL regardless of options - bug

Description
When specifying pro key or w/e, if you set the customurl to the localhost default then turn it back off, it'll still try to connect to localhost.
proposed fix
Guessing that there's something that's ignoring the the custom server enabled boolean in the settings
workaround
Enable the Custom Server in the settings and replace with https://app.fileorganizer2000.com then disable, everything works fine then
symptoms
loads of these errors in the console
plugin:fileorganizer2000:58010 Error: net::ERR_CONNECTION_REFUSED
    at SimpleURLLoaderWrapper.<anonymous> (node:electron/js2c/browser_init:2:49935)
    at SimpleURLLoaderWrapper.emit (node:events:513:28)

plugin:fileorganizer2000:57945 Uncaught (in promise) Error: net::ERR_CONNECTION_REFUSED
    at SimpleURLLoaderWrapper.<anonymous> (node:electron/js2c/browser_init:2:49935)
    at SimpleURLLoaderWrapper.emit (node:events:513:28)

other considerations
OS - mac m1
I had previously rolled out my own server for funsies, and it was working. then opted for subscribing and changed over to a pro account key
settings jsons
working
{
{...},
"defaultServerUrl": "https://app.fileorganizer2000.com",
"customServerUrl": "https://app.fileorganizer2000.com",
"usePro": true,
"useCustomServer": false,
{...}
}

busted
{...},
"defaultServerUrl": "https://app.fileorganizer2000.com",
"customServerUrl": "http://localhost:3000",
"usePro": true,
"useCustomServer": false,
{...}

I can take a looksee later in the weekend and see about slapping together a PR, but someone more familiar with the codebase might be able to knock this out in 30 seconds since it appears to be a missing flag check. (famous last words)

hi @benwalio thanks for reporting this, i think i can get it fixed in a few min with your explanations ;)
i'll ping you when new version is live

tested a bit looks like this should cover it:
https://github.com/different-ai/file-organizer-2000/commit/f64217ef0b58b2216485c56ce241cfa32463260d
you can update the plugin to latest (^1.5.14)
(didn't have too much time to test so keep me posted if it still doesn't behave as expected)

tested and it looked good! thank you!


Commit Search API implemented or not?

Hello,
Is the Commit Search API (in preview) already implemented in the library?
Thank you.

Please, could you perform a release once merged the related PR (#351)? Thanks.


"Allowed Values Should Actually Be Allowed" false positive on trivial UI definition

This is my UI definition:
{
  "$schema": "https://schema.management.azure.com/schemas/0.1.2-preview/CreateUIDefinition.MultiVm.json#",
  "handler": "Microsoft.Azure.CreateUIDef",
  "version": "0.1.2-preview",
  "parameters": {
    "basics": [
      {
        "name": "skuCode",
        "type": "Microsoft.Common.DropDown",
        "label": "App Service Server Type",
        "placeholder": "Select Your Server Infrastructure",
        "defaultValue": "Basic Server B3",
        "toolTip": "This option allows you to choose the underlying infrastructure for the applications. Please review Azure documentation for details of the options.",
        "multiselect": false,
        "selectAll": false,
        "filter": false,
        "filterPlaceholder": "Filter items ...",
        "multiLine": true,
        "defaultDescription": "A value for selection",
        "constraints": {
          "allowedValues": [
            {
              "label": "Basic Server B2",
              "description": "200 ACU, 2 cores, 3.5 GB RAM, manual scale up to 3 instances",
              "value": "B2"
            },
            {
              "label": "Basic Server B3",
              "description": "(Recommended) 400 ACU, 4 cores, 7 GB RAM, manual scale up to 3 instances",
              "value": "B3"
            }
          ],
          "required": true
        },
        "visible": true
      }
    ],
    "steps": [],
    "outputs": {
      "location": "[location()]",
      "skuCode": "[basics('skuCode')]"
    }
  }
}

When running the validation, it fails:
> Test-AzTemplate -Verbose -TemplatePath ./azure/demo/
                                                                                Validating demo\createUiDefinition.json
    AllFiles
        [+] JSONFiles Should Be Valid (6 ms)
    CreateUIDefinition
        [-] Allowed Values Should Actually Be Allowed (24 ms)
            Could not find skuCode in outputs

Adding another UI definition of ours failing the validation:
{
"$schema": "https://schema.management.azure.com/schemas/0.1.2-preview/CreateUIDefinition.MultiVm.json#",
"handler": "Microsoft.Azure.CreateUIDef",
"version": "0.1.2-preview",
"parameters": {
"config": {...},
"basics": [
{
"name": "getLAWorkspace",
"type": "Microsoft.Solutions.ArmApiControl",
"toolTip": "This filters by workspaces that exist in the Resource Group selected",
"condition": "[greater(length(resourceGroup().name),0)]",
"request": {
"method": "GET",
"path": "[concat(subscription().id,'/providers/Microsoft.OperationalInsights/workspaces?api-version=2020-08-01')]"
}
},
{
"name": "workspace",
"type": "Microsoft.Common.DropDown",
"label": "Workspace",
"placeholder": "Select a workspace",
"toolTip": "This dropdown will list only workspace that exists in the Resource Group selected",
"constraints": {
"allowedValues": "[map(filter(basics('getLAWorkspace').value, (filter) => contains(filter.id, toLower(resourceGroup().name))), (item) => parse(concat('{"label":"', item.name, '","value":"', item.name, '"}')))]",
"required": true
},
"visible": true
}
],
"steps": [
...
],
"outputs": {
"workspace-location": "[resourceGroup().location]",
"location": "[location()]",
"workspace": "[basics('workspace')]"
}
}
}
It has data for steps and config, added only the definition relevant to the scenario.

I am hitting the same issue, and opened https://github.com/Azure/arm-ttk/issues/446 , will close mine as dupe of this. The issue I opened has another example too if anyone needs more data points. Thanks!

ack - got the repros...

#561


Elements in use report breaks when a block contains an image shortcode with invalid width or height

Elemental 4.1.x-dev
Example content that will break the Elements in use report:

CWP 2 and SilverStripe 4 provide your agency with an intuitive, extensible CMS that is full of new features that make it faster, more secure, highly customisable, and easy-to-use for your content authors and developers.

[image src="/assets/Feature-Page-Images/910d0e396a/feature_image-v2.png" id="35" width="width" height="height" class="leftAlone ss-htmleditorfield-file image" title="feature image v2"]

The width="width" and height="height" attribute values causes exceptions when viewing the report:
[Emergency] Uncaught InvalidArgumentException: Width must be a numeric value
GET /admin/reports/show/DNADesign-Elemental-Reports-ElementsInUseReport
Line 1044 in /Users/robbieaverill/dev/cwp23/vendor/silverstripe/assets/src/ImageManipulation.php

We can catch this exception, but what should we do instead? Breaking the report seems wrong.

This would also affect the banner block module, and anyone using content fields in their own blocks. Maybe we can catch this exception in the report instead

Fixed in #665


Fix Placeholders not vertically centered in text inputs

Corrected Placeholders not vertically centered in text inputs. @chiragsalian kindly review pull request, please message me if any information missing from my side.  I closed previous pull request #4823 because I forgot to sign commit with gpg.
Details
Basically when there is no focus it shows ExpensiTextInputLabel.js component. We need to update top value for expensiTextInputLabel style within src/styles/styles.js file. i.e. change top: 14 to top: 16 as under:
expensiTextInputLabel: {
...
    top: 16,
...
},

So now we moved inactive label default position 2 pt down, So to keep the active label (i.e. when focused) at the same position we have to set ACTIVE_LABEL_TRANSLATE_Y = -12 (at present it is -10) within src/components/ExpensiTextInput/BaseExpensiTextInput.js  (line 12)
Fixed Issues
$ https://github.com/Expensify/App/issues/4675
Tests

Run app on any platform
Check  text input placeholder on Login screen, now it will show text input placeholder vertically centered when no input text.
For after login screen, Text input with no value will show placeholder vertically centered where text input used.

QA Steps

Login screen text input. When there is no focus on text input, placeholder shows vertically centered now. (previously it was vertically off centered)
After login any text input.  When there is no focus on text input, placeholder shows vertically centered now. (previously it was vertically off centered)

Tested On

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

Screenshots
Web

Mobile Web

Desktop

iOS

Android

Hi, @cead22, As soon as you get time kindly review my pull request 4874. This is my first pull request, if so anything missing then please message me. I will provide needed information as soon as possible. Thank you.

@PrashantMangukiya code looks good, but please include screenshots showing active text inputs and their labels like you did in the other PR for completeness

Hi @cead22  Attached is screenshots having text input value.
Web

Mobile Web

Desktop

iOS

Android

: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.

This has been deployed to production and is now subject to a 7-day regression period.
If no regressions arise, payment will be issued on 2021-09-10.  :confetti_ball:

🚀 Deployed to production by @roryabraham in version: 1.0.92-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Update Site settings “info”

Automatically generated by Netlify CMS

👷 Deploy Preview for sprightly-fox-9454ac processing.

Name
Link

🔨 Latest commit
0e64b4919003974f6c64f9f2e281025d991dfa64

🔍 Latest deploy log
https://app.netlify.com/sites/sprightly-fox-9454ac/deploys/62ebd21859398c0008b4ba9e


ReadMe out of date with 'go get'

If someone is trying to setup Comply with the example GO command with a newer version of Go
go get github.com/strongdm/comply
it should now be
go install github.com/strongdm/comply@latest

Hi @DevopsMercenary,
Thank you for bringing this to our attention. We'll update the page accordingly.
Have a good day
-Matt

FWIW There seems to be more to this change in the go command.  I'm on a Mac and I first had installed Comply via Brew.
When I run comply via brew on my mac to check the version installed....
[gregory@Gregorys-MBP workspace]$ /usr/local/bin/comply -version
comply version 1.6.0

Later I then used the go install github.com/strongdm/comply@latest.  Running the following, I get a different result than what the brew instance returns...
[gregory@Gregorys-MBP workspace]$ ~/go/bin/comply -version
Incorrect Usage. flag provided but not defined: -version

So while my go install comply is in the following path<EMAIL_ADDRESS>there appears to be some sort of difference.


Can I test the trained model of gesture recognition in RGB video?

You may want to see https://github.com/LZQthePlane/Online-Realtime-Action-Recognition-based-on-OpenPose

Thanks for replying~


[Bug]: Docker compose file not loading when using non-root user in remote server

Description
Trying to configure an application with Docker compose in Coolify has been really challenging and frustrating.
I've a project with a several docker compose configuration files that work ok in my local computer but when trying to select them from the Coolify instance I'm constantly getting the error Could not load base compose file from /docker-compose.yaml and getting the Docker Compose Location setting back to its original default.
There is no any extra information about why that error is happening, if the file was not found or was any errors parsing it.
I expend a couple of hours trying different file names, and different docker-compose file configuration but without any proper error logs it was imposible to find the error with my docker files.
Then I tried with a new rails project, a clean Dockerfile and docker-compose.yaml file and the error was the same.
I think docker-compose support is kind of broken in this last version.
I'm running the Coolify version v4.0.0-beta.271.
What is strange is that I've another instance with Coolify that is also now in v4.0.0-beta.271 but in that instance since I've install the project a week ago with docker-compose this project is now working. If a try to configure the same project with the same docker-compose.yml file in the brand new instance it does not work :/.
Minimal Reproduction (if possible, example repository)

Install v4.0.0-beta.271 of Coolify in brand new server.
Create a project and use this repository as source: https://github.com/maurobender/test-coolify-rails and selecting a remote server.
Try to select docker compose configuration.

The repository contains:

Brand new rails app.
Dockerfile
docker-compose.yaml file.

Exception or Error
There is not much information about what is happening, the error is Could not load base compose file from /docker-compose.yaml.
Version
v4.0.0-beta.271

I also got the same problem.
YAML::parse() method via Symphony.
it does not seem to be working properly.
I want try to modify it, but I've never participated in open source before,
so I'm not sure how to participate. 😅

Upon further research I found the problem was using a non-root user (experimental) when connecting to the remote server. Using the root user fixed the issue.

I'm encountering the same issue

me too

This will be fixed in the upcoming version.

Hi @andrasbacsai, I have encountered this same bug in beta 297, has this been regressed?

I will check, but it was hard to reproduce it.

@andrasbacsai, beta 306, docker-compose.yaml file at root of a public repo, the issue is still there

I'm trying to deploy using the Compose functionality and the issue seems to persist. For more context, the Coolify instance is on another server and I'm using a VPN to access it

I tried for both public and private repositories, both had the same problem
Out of curiosity, also tried deploying a Dockerfile to see if it was something related to my repo or permissions, but it worked. So, I guess this is related to Compose

we are having the same issue, v4.0.0-beta3.13.3 accessing on a remote server. tried renaming the files to the defaults, not using overrides, etc., still does not find it. there is a dockerfile in the same directory as the compose file for the main service, and that is found and built without issues.

same

Could you please provide more detailed reproduction steps for this issue after you have upgraded to the latest version of v4? This will help us investigate and resolve the issue.


[GHSA-pv7r-9vjg-g3f9] Duplicate advisory: swift-nio-http2 vulnerable to denial of service via invalid HTTP/2 HEADERS frame length

Updates

Affected products
CWEs
Description

Comments
Take down

Take off all of it


Expose dry-run output to stdout

Description
The dry run step output is suppressed from the terminal logs because we're using the --out flag for RSpec to output to a file. This makes it harder to diagnose errors when running the test splitter. This PR adds the progress formatter back in so that the dry run output is also logged to stdout.
Context
https://linear.app/buildkite/issue/TAT-262/bubble-up-dry-run-errors
Testing
Dry run output will be logged to stdout in test splitter with SBE turned on.

This prints out the output AND logs it to the file yeah? Is this only on for debug, or for all SBE enabled test collector uses? It seems like it would be quite noisy to print this all the time

I think it will only be printed when there is an error when running the dry-run.

In this PR, the dry-run output will be printed every time, no matter if there are errors or not. This is the trade-off with using the json file output for the dry-run.
I can amend this to only add the stdout output if debug is enabled?

I've updated this so it only prints on DEBUG:
Debug enabled:
2024/07/30 13:53:22 DEBUG: Discovering test files with include pattern: spec/**/*_spec.rb exclude pattern:
2024/07/30 13:53:22 DEBUG: Discovered 6 files
2024/07/30 13:53:22 DEBUG: Fetching test plan
2024/07/30 13:53:22 DEBUG: Sending request GET http://api.buildkite.localhost/v2/analytics/organizations/buildkite/suites/buildkite/test_plan?identifier=build_id/step_id_31241
2024/07/30 13:53:23 DEBUG: Response code 404
2024/07/30 13:53:23 DEBUG: No test plan found, creating a new plan
2024/07/30 13:53:23 DEBUG: Splitting by example
2024/07/30 13:53:23 DEBUG: Fetching timings for 6 files
2024/07/30 13:53:23 DEBUG: Sending request POST http://api.buildkite.localhost/v2/analytics/organizations/buildkite/suites/buildkite/test_files
2024/07/30 13:53:23 DEBUG: Response code 200
2024/07/30 13:53:23 DEBUG: Got timings for 4 files
2024/07/30 13:53:23 DEBUG: Getting examples for 3 slow files
2024/07/30 13:53:23 DEBUG: Running `rspec --dry-run`
2024/07/30 13:53:24 DEBUG: ....

Finished in 0.00056 seconds (files took 0.70886 seconds to load)
4 examples, 0 failures

2024/07/30 13:53:24 DEBUG: Got 4 examples within the slow files
2024/07/30 13:53:24 DEBUG: Creating test plan
2024/07/30 13:53:24 DEBUG: Sending request POST http://api.buildkite.localhost/v2/analytics/organizations/buildkite/suites/buildkite/test_plan
2024/07/30 13:53:25 DEBUG: Response code 200
2024/07/30 13:53:25 DEBUG: Test plan created. Identifier: "build_id/step_id_31241"
+++ Buildkite Test Splitter: Running tests
bundle exec rspec ./spec/all_passing/one_spec.rb:4 ./spec/split_by_example/slow_spec.rb:8 ./spec/split_by_example/fast_spec.rb
Run options: include {:locations=>{"./spec/all_passing/one_spec.rb"=>[4], "./spec/split_by_example/slow_spec.rb"=>[8]}}
...

Finished in 0.00751 seconds (files took 0.43902 seconds to load)
3 examples, 0 failures

2024/07/30 13:53:25 DEBUG: Sending request POST http://api.buildkite.localhost/v2/analytics/organizations/buildkite/suites/buildkite/test_plan_metadata
2024/07/30 13:53:25 DEBUG: Response code 200

Debug disabled:
❯ ./run-splitter                                                                                ruby-3.3.3 main 07c72c3 ✗
+++ Buildkite Test Splitter: Running tests
bundle exec rspec ./spec/all_passing/one_spec.rb:4 ./spec/split_by_example/slow_spec.rb:8 ./spec/split_by_example/fast_spec.rb
Run options: include {:locations=>{"./spec/all_passing/one_spec.rb"=>[4], "./spec/split_by_example/slow_spec.rb"=>[8]}}
...

Finished in 0.00619 seconds (files took 0.43377 seconds to load)
3 examples, 0 failures


Get the number of stars in group.data

If we can also get through the API the Unique Visitors per month that would be awesome.

We cannot get the unique visitors; there is no API endpoint for this.
PR: opencollective/opencollective-api#453

Ok


How to make Modal & Lighbox

This is not a bug but it is not so clear how to make bothmodal and lightbox together - modal with transparent background. I tried to find the way and decided to post a question. Is there any way to combine components on router level rather than make lighbox with fake modal animation?

What are you going for? They are separate because they do slightly different things. The example demonstrates using both, albeit not rendering at the same time IIRC.

@asciifaceman because in iOS it is currently a trend to make modal transparent transition, especially with blured background. modal is required to be natively according to iOS UIKit components transitions, but the transparent background is a bit like feature here. Look at mail app in iOS11 when new  message  is creating - it is something like what I'm talking about but without blured background.

@aksonov Why it is closed?

I don't understand the issue. Check Example project that uses Lightbox and Modal


Android Studio and Android application crashes with Filament Panic when trying several poly objects

I thought it gonna be easy to try to place some simple stop sign models onto an AR scene.
I  downloaded several stop sign models and a caution sign model from poly and all of them crashes Android Studio when I try to convert the obj (+ mtl + png) to sfa + sfb.
I see that Google (or JetBrains) receives a Crashlytics report about the crash, but I could gather some stderr info when I started the Studio from command line (and then you see the stderr):
N5utils17PreconditionPanicE
in filament::Material *filament::Material::Builder::build(filament::Engine &):86
reason: Material version mismatch. Expected 4 but received 1.
#0 /tmp/sceneform-filament-jni3535005164651508172/libfilament-jni.so(_ZN5utils6TPanicINS_17PreconditionPanicEE5panicEPKcS4_iS4_z+0x150) [0x7f87c18f1400]
#1 /tmp/sceneform-filament-jni3535005164651508172/libfilament-jni.so(_ZN8filament8Material7Builder5buildERNS_6EngineE+0x1ea) [0x7f87c1871fea]
#2 /tmp/sceneform-loader-jni3911963191015819184/libloader-jni.so(_ZN9sceneform6loader7details13BuildMaterialEPN8filament6EngineERKNS_12BufferAccessE+0x37) [0x7f87c15ea4b7]
#3 /tmp/sceneform-loader-jni3911963191015819184/libloader-jni.so(_ZN9sceneform6loader7details20CreateModelResourcesEPN8filament6EngineENSt3__u8functionIFNS_13OptionalErrorEN4absl11string_viewEPNS_12BufferAccessEEEEPKNS0_7schemas11LoadedModelEPNS_11TypedVectorIPNS2_12VertexBufferEEEPNSI_IPNS2_11IndexBufferEEEPNSI_IPNS2_7TextureEEEPNSI_IPNS2_8MaterialEEEPNSI_INS2_14TextureSamplerEEEPNS_12PairedVectorINS0_9ModelData14MaterialConfigENS_7TypedIdISW_tEEEEPNS1_16InflightCreationE+0xb0b) [0x7f87c15e26eb]
#4 /tmp/sceneform-loader-jni3911963191015819184/libloader-jni.so(_ZN9sceneform6loader7details7Creator11CreateModelEPN8filament6EngineEPNSt3__u10unique_ptrINS0_9ModelDataENS6_14default_deleteIS8_EEEE+0x13c) [0x7f87c15de33c]
#5 /tmp/sceneform-loader-jni3911963191015819184/libloader-jni.so(_ZN9sceneform6loader12LoaderInProc11CreateModelEPN8filament6EngineEPNSt3__u10unique_ptrINS0_9ModelDataENS5_14default_deleteIS7_EEEE+0x63) [0x7f87c15dd6c3]
#6 /tmp/sceneform-loader-jni3911963191015819184/libloader-jni.so(Java_com_google_ar_sceneform_assets_LoadedBundle_nCreateModelData+0x2f) [0x7f87c15d86ef]
terminating with uncaught exception of type utils::PreconditionPanic
Aborted

The sfa and sfb files are created though.
If I compile the file manually:
`$ ./build/sceneform_sdk/linux/converter -a -d --mat ./build/sceneform_sdk/default_materials/obj_material.sfm --outdir ./output/ ./sampledata/caution.obj
Warning: Imported asset was very large (2.6 x 4.3 x 2.0 m)
       : Setting scale to: 0.5000000 to compensate

There's no error message at all.
After that when I try either the Studio compiled version of sfb or the command line compiled one I get the same runtime error along with an application crash:
2019-09-14 14:23:44.203 22376-22376/? I/native: online_calibration_manager.cc:53 OnlineCalibrationManager: Could not open /data/user/0/com.valleydevfest.armap/cache/arcore-online-recalibration for reading.
2019-09-14 14:23:45.875 22376-22376/com.valleydevfest.armap I/native: cpu_feature_extractor.cc:60 Extracting FREAK descriptors.
2019-09-14 14:23:45.886 22376-22376/com.valleydevfest.armap I/native: device_provider.cc:1606 Identified device type: kOneplus6
2019-09-14 14:23:45.893 22376-22376/com.valleydevfest.armap I/native: session.cc:925 Entering Session::Resume.
2019-09-14 14:23:45.893 22376-22376/com.valleydevfest.armap I/native: android_camera.cc:675 Camera 0: State CLOSED: Reset cleanly got to CLOSED state.
2019-09-14 14:23:45.893 22376-22376/com.valleydevfest.armap I/native: pursuit_tracker.cc:1091 AugmentedRegion config changed, enabled:1, quad:true, downsample:true, global reacquisition:false, lite mode:false, adaptive frame delay:false
2019-09-14 14:23:45.894 22376-22459/com.valleydevfest.armap W/native: motion_analysis_calculator.cc:370 No input video header found. Downstream calculators expecting video headers are likely to fail.
2019-09-14 14:23:45.895 22376-22376/com.valleydevfest.armap I/CameraManagerGlobal: Connecting to camera service
2019-09-14 14:23:45.898 22376-22376/com.valleydevfest.armap W/CameraManagerGlobal: [soar.cts] ignore the status update of camera: 2
2019-09-14 14:23:45.898 22376-22376/com.valleydevfest.armap W/CameraManagerGlobal: [soar.cts] ignore the status update of camera: 3
2019-09-14 14:23:45.900 22376-22376/com.valleydevfest.armap I/native: session.cc:2396 Update Frame Delay to 3 frames.
2019-09-14 14:23:45.900 22376-22376/com.valleydevfest.armap I/native: android_sensors.cc:150 Starting thread.
2019-09-14 14:23:45.900 22376-22376/com.valleydevfest.armap I/native: cameras.cc:1118 Selected camera 0 stream 0 as feature extraction stream.
2019-09-14 14:23:45.900 22376-22465/com.valleydevfest.armap I/native: android_sensors.cc:28 Gyro min delay 5ms requesting 5ms
2019-09-14 14:23:45.912 22376-22465/com.valleydevfest.armap I/native: android_sensors.cc:28 Accel min delay 2.5ms requesting 5ms
2019-09-14 14:23:46.106 22376-22429/com.valleydevfest.armap I/native: cameras.cc:1269 Camera changed state from CLOSED to OPEN: Camera 0: State CLOSED: Camera device opened successfully.
2019-09-14 14:23:46.106 22376-22376/com.valleydevfest.armap I/native: session.cc:1055 Session::ResumeWithAnalytics returning OK.
2019-09-14 14:23:46.106 22376-22429/com.valleydevfest.armap I/native: cameras.cc:1269 Camera changed state from OPEN to CAPTURING: Started capture session.
2019-09-14 14:23:46.172 22376-22376/com.valleydevfest.armap E/native: session.cc:1784 Invalid ray produced by view data!
2019-09-14 14:23:46.183 22376-22393/com.valleydevfest.armap D/DecorView: onWindowFocusChangedFromViewRoot hasFocus: true, DecorView@46be38b[MainActivity]
2019-09-14 14:23:46.185 22376-22486/com.valleydevfest.armap I/OpenGLRenderer: Initialized EGL, version 1.4
2019-09-14 14:23:46.185 22376-22486/com.valleydevfest.armap D/OpenGLRenderer: Swap behavior 2
2019-09-14 14:23:46.178 22376-22376/com.valleydevfest.armap W/RenderThread: type=1400 audit(0.0:1706264): avc: denied { read } for name="u:object_r:vendor_default_prop:s0" dev="tmpfs" ino=15908 scontext=u:r:untrusted_app:s0:c37,c257,c512,c768 tcontext=u:object_r:vendor_default_prop:s0 tclass=file permissive=0
2019-09-14 14:23:46.190 22376-22486/com.valleydevfest.armap E/libc: Access denied finding property "vendor.debug.egl.changepixelformat"
2019-09-14 14:23:46.238 22376-22486/com.valleydevfest.armap E/libc: Access denied finding property "vendor.debug.egl.swapinterval"
2019-09-14 14:23:46.228 22376-22376/com.valleydevfest.armap W/RenderThread: type=1400 audit(0.0:1706265): avc: denied { read } for name="u:object_r:vendor_default_prop:s0" dev="tmpfs" ino=15908 scontext=u:r:untrusted_app:s0:c37,c257,c512,c768 tcontext=u:object_r:vendor_default_prop:s0 tclass=file permissive=0
2019-09-14 14:23:46.267 22376-22486/com.valleydevfest.armap E/libc: Access denied finding property "vendor.debug.egl.changepixelformat"
2019-09-14 14:23:46.258 22376-22376/com.valleydevfest.armap W/RenderThread: type=1400 audit(0.0:1706266): avc: denied { read } for name="u:object_r:vendor_default_prop:s0" dev="tmpfs" ino=15908 scontext=u:r:untrusted_app:s0:c37,c257,c512,c768 tcontext=u:object_r:vendor_default_prop:s0 tclass=file permissive=0
2019-09-14 14:23:46.293 22376-22486/com.valleydevfest.armap E/libc: Access denied finding property "vendor.debug.egl.changepixelformat"
2019-09-14 14:23:46.311 22376-22486/com.valleydevfest.armap E/libc: Access denied finding property "vendor.debug.egl.swapinterval"
2019-09-14 14:23:46.315 22376-22376/com.valleydevfest.armap E/Filament: Panic
    in filament::Material *filament::Material::Builder::build(filament::Engine &):86
    reason: Material version mismatch. Expected 3 but received 1.
2019-09-14 14:23:46.315 22376-22376/com.valleydevfest.armap A/libc: Fatal signal 6 (SIGABRT), code -6 (SI_TKILL) in tid 22376 (eydevfest.armap), pid 22376 (eydevfest.armap)
2019-09-14 14:23:46.328 22376-22466/com.valleydevfest.armap I/native: timebase_helpers.cc:168 Timebase offset intialized to 0
2019-09-14 14:23:46.330 22376-22459/com.valleydevfest.armap W/native: motion_analysis_calculator.cc:789 Requested image format in RegionFlowComputation does not match video stream format. Overriding.
2019-09-14 14:23:46.330 22376-22459/com.valleydevfest.armap I/native: region_flow_computation.cc:595 Instantiating and using NEON optimized non-OpenCV KLT.
2019-09-14 14:23:46.331 22376-22459/com.valleydevfest.armap I/native: motion_analysis_calculator.cc:618 Analyzed frame 1
2019-09-14 14:23:46.331 22376-22459/com.valleydevfest.armap W/native: parallel_invoker.h:300 Unsupported invoker mode selected on Android. Falling back to ThreadPool
2019-09-14 14:23:46.332 22376-22461/com.valleydevfest.armap W/native: tracking.cc:3303 Feature descriptors not exist
2019-09-14 14:23:46.332 22376-22461/com.valleydevfest.armap W/native: box_detector.cc:180 Detection skipped due to empty features or descriptors.
2019-09-14 14:23:46.348 22376-22443/com.valleydevfest.armap W/native: gyro_helper.cc:44 Gyro samples do not cover << [ 0 ; 1036182.20209369704 ] sec. Use identity R. Gyro samples cover [ 1036181.880060934 ; 1036182.24687504792 ] sec.
2019-09-14 14:23:46.349 22376-22444/com.valleydevfest.armap I/native: vio_initializer.cc:693 Not accepting frame as first BA keyframe.
2019-09-14 14:23:46.358 22376-22463/com.valleydevfest.armap W/native: tracking.cc:3303 Feature descriptors not exist
2019-09-14 14:23:46.358 22376-22463/com.valleydevfest.armap W/native: box_detector.cc:180 Detection skipped due to empty features or descriptors.
2019-09-14 14:23:46.398 22376-22461/com.valleydevfest.armap W/native: tracking.cc:3303 Feature descriptors not exist
2019-09-14 14:23:46.399 22376-22461/com.valleydevfest.armap W/native: box_detector.cc:180 Detection skipped due to empty features or descriptors.
2019-09-14 14:23:46.424 22376-22463/com.valleydevfest.armap W/native: tracking.cc:3303 Feature descriptors not exist
2019-09-14 14:23:46.424 22376-22463/com.valleydevfest.armap W/native: box_detector.cc:180 Detection skipped due to empty features or descriptors.
2019-09-14 14:23:46.444 22376-22444/com.valleydevfest.armap I/native: vio_initializer.cc:693 Not accepting frame as first BA keyframe.
2019-09-14 14:23:46.457 22376-22461/com.valleydevfest.armap W/native: tracking.cc:3303 Feature descriptors not exist
2019-09-14 14:23:46.457 22376-22461/com.valleydevfest.armap W/native: box_detector.cc:180 Detection skipped due to empty features or descriptors.
2019-09-14 14:23:46.494 22376-22460/com.valleydevfest.armap W/native: tracking.cc:3303 Feature descriptors not exist
2019-09-14 14:23:46.494 22376-22460/com.valleydevfest.armap W/native: box_detector.cc:180 Detection skipped due to empty features or descriptors.
2019-09-14 14:23:46.524 22376-22463/com.valleydevfest.armap W/native: tracking.cc:3303 Feature descriptors not exist
2019-09-14 14:23:46.524 22376-22463/com.valleydevfest.armap W/native: box_detector.cc:180 Detection skipped due to empty features or descriptors.
2019-09-14 14:23:46.552 22376-22444/com.valleydevfest.armap I/native: vio_initializer.cc:693 Not accepting frame as first BA keyframe.
2019-09-14 14:23:46.556 22376-22460/com.valleydevfest.armap W/native: tracking.cc:3303 Feature descriptors not exist
2019-09-14 14:23:46.556 22376-22460/com.valleydevfest.armap W/native: box_detector.cc:180 Detection skipped due to empty features or descriptors.
2019-09-14 14:23:46.589 22376-22461/com.valleydevfest.armap W/native: tracking.cc:3303 Feature descriptors not exist
2019-09-14 14:23:46.590 22376-22461/com.valleydevfest.armap W/native: box_detector.cc:180 Detection skipped due to empty features or descriptors.
2019-09-14 14:23:46.625 22376-22460/com.valleydevfest.armap W/native: tracking.cc:3303 Feature descriptors not exist
2019-09-14 14:23:46.625 22376-22460/com.valleydevfest.armap W/native: box_detector.cc:180 Detection skipped due to empty features or descriptors.
2019-09-14 14:23:46.656 22376-22461/com.valleydevfest.armap W/native: tracking.cc:3303 Feature descriptors not exist
2019-09-14 14:23:46.656 22376-22461/com.valleydevfest.armap W/native: box_detector.cc:180 Detection skipped due to empty features or descriptors.

I'm using Linux operating system
compileSdkVersion 28
minSdkVersion 24
targetSdkVersion 28
Android Studio 3.5
Google Sceneform Tools (Beta) 1.12.0
My application would be a simple concept but I'm kond of stuck because all models I tried so far does this. On the other hand the Sceneform Introduction codelab ran fine on my machine.
I'm giving more details below.

Another example with a stop sign model, Studio crashes cold with the same Filament Precondition Panic (material expected 4 but received 1). Command line verbose compilation shows no error whatsoever:
$ ./build/sceneform_sdk/linux/converter -v -a -d --mat ./build/sceneform_sdk/default_materials/obj_material.sfm --outdir ./output/ ./sampledata/stopSign.obj
Info: Applied 1 material paths to 2 surfaces by duplicating the last path
Info: Generated SFA from ./sampledata/stopSign.obj
Info: Version: 0.540000.2
    : - Geometry Center (m): <0.000, 2.483, -0.056>
    : - Geometry Size (m)  : <1.848, 4.925, 0.150>
    : - Model 0/1: 70 Vertices
    :   - Attribute 0/3: Position (Vec3f)
    :   - Attribute 1/3: TexCoord (Vec2f)
    :   - Attribute 2/3: Orientation (Vec4f)
    :   - Material 0/2: 'lambert11SG' (32 Triangles)
    :   - Material 1/2: 'lambert12SG' (12 Triangles)
    : - Texture 0/1: 'stopSignTxt' (./sampledata/stopSignTxt.jpg, 58095 bytes)
    :   - Usage type: 'Color'
    :   - Mag filter: 'Linear', Min Filter: 'NearestMipmapLinear'
    :   - Wrap S: 'Repeat', Wrap T: 'Repeat'
    : - Material 0/2 (compiled index 0)
    :   - Parameter 0/5: 'baseColor' = "stopSignTxt"
    :   - Parameter 1/5: 'baseColorTint' = [1.000000, 1.000000, 1.000000, 1.000000]
    :   - Parameter 2/5: 'metallic' = 0.000000
    :   - Parameter 3/5: 'roughness' = 1.000000
    :   - Parameter 4/5: 'opacity' = null
    : - Material 1/2 (compiled index 1)
    :   - Parameter 0/5: 'baseColor' = null
    :   - Parameter 1/5: 'baseColorTint' = [0.240000, 0.060000, 0.010000, 1.000000]
    :   - Parameter 2/5: 'metallic' = 0.000000
    :   - Parameter 3/5: 'roughness' = 1.000000
    :   - Parameter 4/5: 'opacity' = null
    : - Compiled Material 0/2: 80237 bytes
    :   - sha1sum: 6ad1ac9da50771d8bace7364490226740b51b8a3
    : - Compiled Material 1/2: 79344 bytes
    :   - sha1sum: 93fd6a25cdea76764d62bd3082bba9dd1afc75eb
    : - Collision Shape:
    :   - Center: x=0.000000, y=2.462570, z=-0.000000
    :   - Size: x=1.847759, y=4.925140, z=0.150252
    : --- totals ---
    : - vertices: 2520 bytes
    : - indices: 132 bytes
    : - textures: 58095 bytes
    : - materials : 159581 bytes
Info: Wrote SFA (json) to ./output/stopSign.sfa (1331 bytes)
Info: Wrote SFB to ./output/stopSign.sfb (225368 bytes)

Now the app runtime crashes again with exactly the same Filament Panic as with the caution sign (expected material 3 but got 1). See LogCat of that crash
The stop sign object
The caution sign object
I think the Android Studio Crash might not be because of the conversion but when it tries to open the sfb file and visualize it for me? When I completed some code labs the sfb file was never displayed graphically but just as binary sequence.
Screen recordings:
Crashing Android Studio when trying to convert caution sign object
AR Android app crash w caution sign crash and converting manually
Crashing Android Studio when trying to convert stop sign object + manual conversion later
AR Android app crash w caution sign crash and converting manually

It looks like this is a mismatch in the version of the converter you are running and Sceneform 1.12  The 1.12 Android Studio plugin is only compatible with SFB files converted with Sceneform SDK 1.12 because of Filament material version changes.
The same is also true of Sceneform SDK 1.12 (i.e. your SFB files won't work with Sceneform 1.12 on Android if you are running an old version of the converter)
If you want to stay on the previous version of the converter, you should install the corresponding Sceneform Tools Android Studio plugin from the version download page.

@tpsiaki I skimmed over the issues and I get that there can be binary format changes between sfb file versions. Even before that I erased the sfbs letting them regenerate, even so later I erased the sfas (along with removing the entries from the build.gradle so the sfas would also regenerate (and they are somewhat different actually)! However after the regeneration happens I thought there shouldn't be any crashes. During my manual regeneration attempts I use the converter executable which is populated by the plugin, so I guess the versions should match as well.

@tpsiaki The Android Studio crash I'm sure is when it'd try to open and show me the sfb. I could easily get over that, but then the built Android app crashes as well, that's the real blocker problem. How can I clearly identify what kind of version mismatch I'm dealing with? All I can see is that both "before" and "after" sfas say version 0.54:2.