revise synonyms for MONDO_0005550

addresses #750

@cmungall see question on ticket #750 (pasted here: in the current PR, I annotated "ID" as an abbreviation and as 'synonym to be removed from public release but maintained in edit version as record of external source' - does that properly address the issue?)

Can you undo your travis changes?

@cmungall  can you see #743 and then I'll undo it if you still think it is a bad idea. Undoing it will start to give overall "failed" statuses and one will need to look further to see if the Jenkins status succeeded. At this point the Travis status is effectively irrelevant since it is almost always timing out.

I think if we are a bit economical we can squeeze the duration of the overall pipeline on travis down to 40 min, well within the acceptable range. Many of the sparql tests are simply redundant!

pinging @cmungall and @ShahimEssaid - I think the next step are dependent on you two :)

Closing this. Make a new PR for the synonym change. Make a new change for travis if required.


Textfield and textarea issues

This is a multipart issue:
1. Padding in textfield component does not appear to work
https://jasonbase.com/things/AXj.json

2. Padding in the textarea component does not appear to work

Try changing the padding value for either issue above

3. Inconsistency in 'corner radius' for textarea component
If the value in a textarea is obtained from a cache item (e.g. $cache.about), then corner_radius does not appear to work. It only seems to work when the value of the textarea isn't a Jason object.

With the third part of the issue, turns out that the corner radius rendered properly after closing and reopening the app.

Please check the latest develop branch, the padding should work.

Nice!

Only thing I noticed was that it only worked with padding and not padding_left... but not sure whether that kind of control is necessary.

Yes, I started trying to implement padding_left, padding_top, et al, but realized this introduces a lot of hidden complexity. For now textareas and textfields only support padding.
Closing this for now since it works for padding. May revisit if we come across a critical case where padding_left, padding_top etc are very necessary.

That's perfectly reasonable, thanks!


Ensure that errors in Java appear coherently within napari

Errors in e.g. module execution do not appear as popups in napari; they are only printed on the console. They should appear in napari as well.
See this zulip thread for context.

@ctrueden so I dug into the issue a bit. napari tries to get the message of the exception here. Unfortunately, for Java exceptions, message is a method, not a field! The reason we don't get a popup is due to an error resulting from this discrepancy.
The easiest way forward is probably to just wrap Java exceptions as Python exceptions and just raise those :frowning:

I would suggest filing an issue in the JPype issue tracker about this discrepancy. Specifically: can we add @property to the message(self) method so that msg = getattr(exception, 'message', str(exception)) works as desired without special casing it on the napari side? (I tested it, and with the @property decorator, this getattr invocation works as desired.)

wrap Java exceptions as Python exceptions and just raise those

I am supportive of that, as long as we use scyjava.jstacktrace for the message of the Python exception, so that the entire Java stack trace is preserved.

wrap Java exceptions as Python exceptions and just raise those

I am supportive of that, as long as we use scyjava.jstacktrace for the message of the Python exception, so that the entire Java stack trace is preserved.

:+1:
There's an issue with my testing right now, though. ScriptModule doesn't actually throw Exceptions raised within scripts, it just prints their traces!

Yeah, the reason is so that the Script Editor, which had an existing stdout/stderr infrastructure already before SciJava came along, can still dump those streams to its text console. Unfortunately, there is no unified Module-level way of telling the framework to use your custom streams (which would allow you to then pass along this output to napari somehow more easily).
We might want to raise the issue of stdout/stderr with the napari folks, to see if they see any value in including a GUI stdout/stderr console inside napari, which pops up to the user when anything appears on stderr. This would solve our issue, and be more general besides. There will probably be pushback that there is already a console on the terminal when launching napari, but this rebuttal does not take into account the (future most common) use case of launching napari via a desktop icon.

Another thing we could do is update the SciJava script framework to actually throw those exceptions unless custom streams were provided for dumping them instead.

Woah, can we do that without breaking backwards compatibility?

Ahh, I didn't realize that if you add @property to something, then calling it as a method no longer works. Too bad. But maybe worth asking anyway?

Another thing we could do is update the SciJava script framework to actually throw those exceptions unless custom streams were provided for dumping them instead.

I like this idea better. Customization seems better and would allow us to proceed without effort on napari.

python's BaseException doesn't have an attribute for accessing the message at all, it's just part of napari's assumptions

Oof, thanks for clarifying that. Then yeah, it makes no sense to change it in JPype.

I checked.  message appears to always have been a function in JPype1 going back to 0.6.3.   (it was totally inconsistent with the rest of the code at the time, so it likely should have had @property)  Currently, it is a legacy method from when the Java and Python exceptions were split.   I recommend using the better named getMessage function as it is less likely to cause confusion.


Load_Platform fail

Hello,
I used ./setup-local.sh in order to configure my ADOP stack.
The creation is OK, but when I start the Load_Platform job, I get this issue:

10:57:11 + echo 'Repository already exists, skipping: platform-management'
10:57:11 Repository already exists, skipping: platform-management
10:57:11 + git remote add adop ssh://jenkins@gerrit:29418/platform-management
10:57:11 + git fetch adop
10:57:12 + git push adop '+refs/remotes/origin/:refs/heads/'
10:57:12 fatal: internal server error
10:57:12 fatal: Could not read from remote repository.
10:57:12
10:57:12 Please make sure you have the correct access rights
10:57:12 and the repository exists.
10:57:12 Build step 'Execute shell' marked build as failure
10:57:12 [ssh-agent] Stopped.
10:57:12 Finished: FAILURE

I did a docker exec inside Jenkins container, I started manually a git clone, and it seems that there is a RSA key issue:

root@79bcc2fc0b82:/tmp# git clone ssh://jenkins@gerrit:29418/platform-management
Cloning into 'platform-management'...
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.

Do you know how to fix it?
Thanks in advance!

@dcuenot is this a vanilla ADOP stack? If this has been resolved please can you close this issue?

@dcuenot I'm closing this issue as there was no response.


Attempt to call field 'setlabels' (a nil value)

Hello. I have started to use parser-gen and i have ran into a error. Whenever i try to require parse-gen, it gives me the error in the title. I have the newest version of lpeglabel and parser-gen from luarocks. Thank you. Here is a image if that helps.  https://i.imgur.com/9FicYjH.png

It seems like setlabels is not a function in relabel. You must have made a programming error or something.

Hey, I saw lpeglabel changed the syntax of the tool and that probably broke
compatibility. Try using an older version of lpeglabel.
On Mar 20, 2018 09:59, "Pancakeddd"<EMAIL_ADDRESS>wrote:

It seems like setlabels is not a function in relabel. You must have made a
programming error or something.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/vsbenas/parser-gen/issues/12#issuecomment-374607623,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZe9qxsN1e2kRHlsIeY9H8IMDuUO9pMlks5tgQsvgaJpZM4Sx6x_
.

It seems that i can't get the older version of lpeglabel.

Hmm. Idk what to do.

luarocks install LPegLabel 1.4.0-1 clears this up for me. versions 1.5 & 1.6 exhibit the error in the issue title.


Draco imported meshes doesn't Support secondary UV channel

in v1.4.1, meshes with secondary uv channel are loaded with a single uv channel when imported using the draco extension.
Draco compressed:

Normal version of the same glb:

I went through the source as well, as it seems the class PrimitiveCreateContext has the textcoord apply to mesh related functions, where as in case of a draco mesh class PrimitiveDracoCreateContext is using DracoMeshLoader.CreateMesh function to setup the mesh.
If you could at least show me a direction on where I could add the temporary uv2 support(if currently not supported for draco meshes using gltffast) that would also be of great help. Also thanks for all the amazing plugins.

If in case you need the sample Draco compressed GLB that I have shown in the above screenshot:
Coffee tableDracoButCombined.zip

Hi @prajwalshettydev ,
Thanks for reporting the issue!
I'd prefer to not fix this in 1.4.x anymore. Development on version 2.0.0-preview of DracoUnity is only having one remainging problem with weights/joints. It is a refactor with multiple UVs in mind (but not tested).
Feel free to test your model with the newer version. I've just pushed the corresponding glTFast branch, that works with DracoUnity 2.x.
hth

I gave this a try in 2.x, it didn't resolve my issue, It also threw a few exceptions, so I'm assuming these errors could be the reason behind it.


Fix applying DES-CBC when using OpenSSL 3

After calling #final on the cipher object, it will return garbage from that moment forward. The cipher object can therefore not be reused in the iteration over keys. Reinitialize it everytime instead.
This seems to be new behaviour in Ruby/OpenSSL3. See also:
https://ruby.github.io/openssl/OpenSSL/Cipher.html#class-OpenSSL::Cipher-label-Calling+Cipher-23final
This fixes #50.

We're hitting this issue with one of our Ruby gems too :+1:
The work around I had before finding this issue was:
       def apply_des(plain, keys)
         dec = OpenSSL::Cipher.new("des-cbc").encrypt
         dec.padding = 0
         keys.map {|k|
+          dec.reset
+          dec.iv = "\x00" * 8
           dec.key = k
           dec.update(plain) + dec.final
         }
       end

Ah, it doesn't look like this patch is available in the latest rubyntlm release on RubyGems
@mwrock It'd be great if this could be released as a patch version, let me know if I can help in anyway 🎉


chore: update prettier to v3.2.5

Current dependencies on/for this PR:

main

PR #2332   👈

This stack of pull requests is managed by Graphite.


Confusing strings

JMESPath differentiates between RAW_STRINGS and STRINGS based on whether the string is inside json or not.
The big difference is that it does not perform escape character processing on strings outside of JSON.
I find it confusing.
Given this input: {"B": 1, "D": 3}
These expressions give the following results:
'\u0042' => 1
"\u0042" => "\u0042"
`"\u0042"` => "B"
For string literals outside JSON, I think we should respect the escape sequences that are part of JSON: " / \ \b \f \n \r \t \uxxxx
Malformed unicode escape is an error e.g. "\ub", unnecessary escape sequences are an error
Then the results would be:
'\u0042' => 1
"\u0042" => "B"
`"\u0042"` => "B"
`"\D"`, "\D", '\D' => error

fixed


Squared sinc distribution to create triangular kernel shape

@mikeheddes, I added another sampling distribution to the FPE example script from @denkle.
It is a custom torch distribution that samples from a squared sinc function to get a triangular kernel shape in FPE.
This might be a helpful suggestion for other users because a linear kernel adds another useful one to the sinc and Gaussian shape.
I'm not sure if the implementation is the best to sample from the given distribution (rejection sampling) - maybe you have another idea for a better implementation.

@scken thank you for adding this example, it is very helpful indeed! I am not sure how to sample more efficiently, my first thought was to do inverse transform sampling but that doesn't seem to be simple in this case since the sinc doesn't have a nice inverse. We can always improve in a future PR if someone knows about a better way.
Just some minor comments on the code, could you change the comment ## Gaussian kernel at the top of the cells you added to reflect the actually implemented kernel. And the first figure label is "Triangular kernel with HRR model" which I belief should be "Triangular kernel with FHRR model". I also see that you got an error in the 2D kernels Unknown projection '3d', if you could resolve the error and re-run the cells that would be great, otherwise everybody will see the error.
Other than that I think the code is great and ready to be merged.
Thanks again!

Thanks @mikeheddes for your comments. I have fixed the points and pushed the changes to the branch.

Looks great @scken, thank you for your contribution!


Properly checks that .length() is used in JS brackets notation challenges

Verified that this fix is working. Thanks!


launcher support for rm2fb

This task is to add the ability for launchers to use the LD_PRELOAD shim when launching applications.
Launchers:

draft: single task launcher
oxide: multi task launcher
remux: multi task launcher

The main issue with rm2fb and launchers is interacting with xochitl, since xochitl will spawn its own SWTCON thread.
Note that launchers will have to use rm2fb LD_PRELOAD shim to display to screen

i'd be fine with our first launcher being ddvk's remarkable-touchgestures + associated scripts to toggle between draft and xochitl

this works almost out of the box, as the LD_PRELOAD gets passed to the child processes.

@raisjn , did you manage to launch oxide on rm2?

Yes, I've run oxide on rM2, I don't recall if I got tarnish and everything else working, but I think I did at one point

this is now done through the toltec package and systemd environment variables


Move all build stages into Circle (instead of Netlify)

@m7kvqbe1 - to complete.

Moving deploy previews into Circle and deploying to Netlify via their CLI tool would mean we'd have no way of easily obtaining the autogenerated preview URL.
We'd lose some of the magic of Netlify and end up using it in much the same way as Firebase.

Closing this for now.

This is now a spike, attempting to answer the question: Will other platforms allow us to do branch deployments? Starting with AWS, but moving to GovPaas if we can't use AWS.


Color assets are not used in the output

When the option to "Export Color Assets" is enabled, the exported widgets do not use the generated color constants.
This is because the current implementation of Color Assets in XD simply associates a label with a color value, as opposed to creating a named color asset. For example, this means that if I create a textColor color asset with a value of #000000, then every place solid black is used in my file will become associated with the textColor label. This results in too many false positive matches to rely on it for export.

Would love to see  generated style guide one day


[bug] Inconsistent handling of app identifiers containing hyphens when building for Android

Describe the bug
Like most app development frameworks, Tauri uses reverse domain notation for the app identifiers.
Tauri only allows letters (a-z, A-Z), digits (0-9) and hyphens (-) in app identifiers. However, Android only allows underscores (_) in app identifiers, not hyphens; iOS, on the other hand, does allow hyphens, but no underscores.
Right now, this means that running cargo tauri android init panics if the app identifier contains hyphens or alternatively only contains of two parts (I think the latter is unintended, anyway).
To illustrate, let's assume I have an app identifier like tech.almost-senseless.jack-point. Trying to build this app for Android fails with a panic due to the hyphen in almost-senseless. Renaming it to tech.almostsenseless.jack-point or tech.almost-senseless works fine, though: In the first case, the generated Android package name and identifier would be tech.almostsenseless.jack_point, and in the latter case it would be tech.jack_point.
Evidently, the last part of the app identifier gets silently dropped and replaced with the product name, and in the product name, hyphens get replaced with underscores.
This has the side effect that running cargo tauri android init when the app identifier is com.tauri.dev works, by the way, because it becomes com.tauri.jack_point - I think that's not intended that way, is it?
So my problem boils down to that

Having hyphens in your app identifier shouldn't lead to a panic; rather, the hyphens should get replaced with underscores in the generated Android project.
The handling of the identifier should be more consistent, with the last part not getting silently dropped and replaced with the product name.

Reproduction

Create a Tauri project from any template, for instance using cargo create-tauri-app --beta. Please make sure mobile support was enabled.
Open tauri.conf.json and change the identifier to com.some-domain.some-app.
Run cargo tauri android init.

Expected behavior
The command should complete successfully, generating an Android project with the identifier com.some_domain.some_app.
Full tauri info output
WARNING: no lock files found, defaulting to npm

[✔] Environment
    - OS: Windows 10.0.22631 X64
    ✔ WebView2: 124.0.2478.80
    ✔ MSVC: Visual Studio Community 2022
    ✔ rustc: 1.80.0-nightly (e82c861d7 2024-05-04)
    ✔ cargo: 1.80.0-nightly (05364cb2f 2024-05-03)
    ✔ rustup: 1.27.0 (bbb9276d2 2024-03-08)
    ✔ Rust toolchain: nightly-x86_64-pc-windows-msvc (environment override by RUSTUP_TOOLCHAIN)
    - node: 20.11.0
    - npm: 10.5.0

[-] Packages
    - tauri [RUST]: 2.0.0-beta.17
    - tauri-build [RUST]: 2.0.0-beta.13
    - wry [RUST]: 0.39.3
    - tao [RUST]: 0.27.1
    - tauri-cli [RUST]: 2.0.0-beta.16
    - @tauri-apps/api : not installed!
    - @tauri-apps/cli [NPM]: 2.0.0-beta.16

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/

### Stack trace

```text
thread 'main' panicked at C:\Users\timjb\.cargo\registry\src\index.crates.io-6f17d22bba15001f\tauri-cli-2.0.0-beta.16\src\mobile\mod.rs:322:6:
called `Result::unwrap()` on an `Err` value: DomainInvalid { domain: "almost-senseless.tech", cause: NotAsciiAlphanumeric { bad_chars: ['-'] } }

Additional context
No response

Hi,
I am having the same issue. It used to be possible to have _ in the android application name but since the last updates, this is not possible anymore. I have published an android application with an underscore and now cannot update it anymore due to that. I would be happy with the solution proposed by almost-senseless-coder.
I think it is related to this change https://github.com/tauri-apps/cargo-mobile2/commit/29921ff025ebed31546e33dc82696dc0c8fce2e0, but I am really not sure as I don't have a deep knowledge of the way tauri works.

@FabianLars It looks like you don't have the manpower to handle that. What would be your preferred solution?

Allowing - in the identifier and converting it for Android
Having an option to manually specify the appid for android (and other OS will be implemented later if needed)?
Something else?

I personally would lean towards the first option, but not sure. Let's ask @lucasfernog and @amrbashir

Hi, I am having the same issue. It used to be possible to have _ in the android application name but since the last updates, this is not possible anymore. I have published an android application with an underscore and now cannot update it anymore due to that. I would be happy with the solution proposed by almost-senseless-coder.
I think it is related to this change tauri-apps/cargo-mobile2@29921ff, but I am really not sure as I don't have a deep knowledge of the way tauri works.

I wonder how you manage to do so 😂 looks like we need even more changes to support _ in the package identifier

Hi, I am having the same issue. It used to be possible to have _ in the android application name but since the last updates, this is not possible anymore. I have published an android application with an underscore and now cannot update it anymore due to that. I would be happy with the solution proposed by almost-senseless-coder.
I think it is related to this change tauri-apps/cargo-mobile2@29921ff, but I am really not sure as I don't have a deep knowledge of the way tauri works.

I wonder how you manage to do so 😂 looks like we need even more changes to support _ in the package identifier

I am good enough to break anything :joy:
There was a few modifications required for my app in the build.gradle.kts which I managed by simply modifying it in my repository (including the appid). Unfortunately, there has been some changes in tauri that forces the appid in build.gradle.kts to match the identifier in the configuration file. If they don't match, I get an undefined reference to in Logger.kt. I tried making links, moving directories, copying files, ... but it does not work.
I know it is not something very standard, so I am ready to help if you need.

Fix will be released soon. Note that you'll need to run cargo update in the src-tauri folder to apply it.

I can confirm that the fix works with tauri-cli rc7. Thanks for your help!


(#11) Converting pretty printer to Reason.

Thanks to @jordwalke for helping out once again.
This correctly builds now.
I guess we now also need a way to generate the binary AST when modifying the pretty printer. Any thoughts on that?

If we want we can revisit this later.


adds a couple of bool proofs; adds subset type

adds bool proofs for true_isnt_false & vice_versa
adds subset
adds bool.test.different_elem
these were all ported from Soonad/Base.fm

ran the latest fmc; all checks passed

Thanks for the commit! I had already added Sigma.fmc for Subset, but you're right that the b in
(make: (a: A) -> <b: B(a)> -> P(Subset.make<A><B>(a)<b>))

should be erased. And Subset is a better name anyway, so I'll remove the Sigma files in favor of this


Laravel 5.3 Shift

This pull request includes the changes for upgrading to Laravel 5.3. Feel free to commit any additional changes to the shift-2316 branch.
Before merging, you should:

Checkout the shift-2316 branch
Review all pull request comments for additional changes
Run composer update (if the pre-commands fail, add --no-scripts)
Thoroughly test your application

If you would like more help with your upgrade, check out the human services from Laravel Shift. And if you want to level-up your Git skills, check out Getting Git.

❌ I could not upgrade the following core files since they differed from the default Laravel version. You need to compare these configuration files against the Laravel 5.3 versions and merge any changes:

[ ] resources/lang/en/auth.php

❌ Looks like you already have a app/Http/Controllers/Auth/ResetPasswordController.php. Laravel 5.3 added this as a core file. You should compare your file to the 5.3 version and upgrade your project accordingly.

❌ Laravel 5.3 split the Auth/AuthController.php into the Auth/LoginController.php and the Auth/RegisterController.php. Since yours appears to be customized, I did not remove it. You should compare your Auth/AuthController.php with the newly added controllers and merge your changes accordingly.

ℹ Laravel 5.3 updated the  app/Jobs folder by default. It is created for you when you make your first Job using artisan. I did not remove yours as it appears to differ from the default. However, if your app does not use Jobs, you can remove this folder manually to keep your app streamlined.

❌ Looks like you already have a app/Http/Controllers/Auth/ForgotPasswordController.php. Laravel 5.3 added this as a core file. You should compare your file to the 5.3 version and upgrade your project accordingly.

❌ Laravel 5.3 renamed the Auth/PasswordController.php to Auth/ResetPasswordController.php. Since yours appears to be customized, I did not remove it. You should compare your Auth/PasswordController.php against the added Auth/ResetPasswordController.php and merge your changes accordingly.

❌ Looks like you already have a app/Http/Controllers/Auth/LoginController.php. Laravel 5.3 added this as a core file. You should compare your file to the 5.3 version and upgrade your project accordingly.

⚠ If you are using Authentication, you should upgrade any routes using AuthController and PasswordController to use the new authentication controllers. Laravel recommends using the Auth::routes() which registers the proper routes for the new authentication controllers. This method also registers a POST route for /logout instead of a GET route.

❌ I was not able to update your app/Providers/RouteServiceProvider.php. You will need to compare yours against the 5.3 version and merge the new changes.

ℹ Laravel 5.3 changed the redirect URL for an authenticated user from / to /home in app/Http/Middleware/RedirectIfAuthenticated.php. You may wish to change this depending on your app configuration. Otherwise, it may cause an infinite redirection loop.

❌ I could not upgrade the following configuration files since they differed from the default Laravel version. You need to compare these configuration files against the Laravel 5.3 configuration files and merge any changes:

[ ] config/auth.php
[ ] config/database.php
[ ] config/services.php

❌ Laravel 5.2 introduced Middleware Groups, which are now used in Laravel 5.3. It appears you have not upgraded to Middleware Groups. You should review Middleware Groups in more detail. Then compare your app/Http/Kernel.php with the 5.3 version and update manually.

❌ I was not able to update your app/Providers/AuthServiceProvider.php. You will need to compare yours against the 5.3 version and merge the new changes.

⚠ Laravel 5.3 now includes a top-level routes folder. In addition, it separates routes into API, console, and web files.I have included a default routes/api.php and routes/console.php as well as migrated your app/Http/routes.php to routes/web.php. You should review your routes to see if they should be separated into one of the new route files.

❌ Looks like you already have a app/Providers/BroadcastServiceProvider.php. Laravel 5.3 added this as a core file. You should compare your file to the 5.3 version and upgrade your project accordingly.

⚠ The default behavior of Route::resource() changed in Laravel 5.3. All resource route parameters are now singularized by default and URL prefixes no longer affect the route names.You should review your resource routes and verify this singularized naming will not affect your parameters (or if you were doing this manually, you can remove the parameter). In addition, verify you are no longer appending the URI prefix to the route name.
Found Route::resource() in:

[ ] routes/web.php

❌ I see you are using the Forms and HTML package by the Laravel Collective. The recommended version is 5.3.* for Laravel 5.3. You should review your laravelcollective/html dependency to ensure it is compatible. Review the Installation Docs for more details.

❌ I could not upgrade the following project files since they differed from the default Laravel version. You need to compare these project files against the default Laravel 5.3 versions and merge any changes:

[ ] gulpfile.js
[ ] package.json

❌ The Query Builder returns collections, instead of plain arrays, in Laravel 5.3. You will need to upgrade your code to use collections or chain the all() method onto your query to return a plain array.
You should review the following usages of Query Builder:

[ ] app/Http/Controllers/FaucetsController.php
[ ] database/seeds/UsersTableSeeder.php
[ ] database/seeds/ReferraInfoTableSeeder.php
[ ] database/seeds/BaseSeeder.php
[ ] routes/web.php

⚠ The lists() method on Collection objects was deprecated in Laravel 5.2 and removed in Laravel 5.3. I replaced usages of lists() with pluck(), you can review the Shift deprecations commit to verify this change.

❌ Laravel 5.3 has a development dependency for symfony/dom-crawler of 3.1.*. You have a modified dependency for symfony/dom-crawler in your composer.json. Ensure it meets the new version requirement of 3.1.*.

❌ Laravel 5.3 has a development dependency for symfony/css-selector of 3.1.*. You have a modified dependency for symfony/css-selector in your composer.json. Ensure it meets the new version requirement of 3.1.*.

ℹ If you are using Queues, you no longer need to specify the --daemon option when calling the queue:work. This is assumed in Laravel 5.3. Use the --once option to process a single job.

❌ Laravel 5.3 where performs a "loose" comparison. In addition, the strict parameter was removed. If you need to perform a "strict" comparison, you can use whereStrict instead.
You should review the following usages of where to ensure you do not require "strict" compaison:

[ ] app/Console/Commands/SendRandomFaucetTweet.php
[ ] app/Helpers/Functions/Ads.php
[ ] app/Helpers/Social/Twitter.php
[ ] app/Http/Controllers/AdBlockController.php
[ ] app/Http/Controllers/FaucetsController.php
[ ] database/seeds/ReferraInfoTableSeeder.php

ℹ If you are using the database driver for your Queue, you will need to update your jobs and failed_jobs table. Review the Queue section of the Laravel 5.3 Upgrade Guide for more details and feel free to use the migrations from Laravel Shift.

ℹ If you have manually upgraded your app for previous versions of Laravel, I recommend running the Laravel Linter to ensure your app is fully upgraded to the latest version of Laravel.

⚠ Laravel 5.3 added configuration for your application name in config/app.php. Be sure to set this value as it is used in notifications, like the password reset email.

ℹ Laravel 5.3 updated several of the default assets as well as adding support for Vue.js. If you are using Laravel to compile assets you may want to review the latest versions of resources/assets/js/app.js and resources/assets/sass/app.scss and update your project accordingly.


Timer keeps reseting / losing track of ticks

I just installed the most recent windows updates which may be linked to this - issue did not exist before. Seems to happen on all weapons

Yes i am having this exact same issue. Good to see it is just not me because i have tried everything to fix.
Overhead attack timer countdown goes like 5,4,3 and then disapears at 3.
Only weapon it still works for is whip but everything else seems broken.
Hopefully this can get fixed somehow because i love this plugin!

any solution matt?

Sounds like a duplicate of https://github.com/ngraves95/attacktimer/issues/26. I'm going to close until someone reports this getting repro-ed.


C API var_atom_t is confusing and unneeded

This is a very minor point, but I think C API functions would be more orthogonal is they dealt individually with Variable Atoms and other bound Atoms, rather than bundling both together into a var_atom_t
This was probably my biggest point of confusion when I was first learning the API.  My assumption was that the var_atom_t was a single variable atom.  However it's actually a parallel way to express variable bindings.
This is not a big deal, but I feel like it would simplify the C API to unpack binding as variable-atom pairs.
If a single struct still makes sense to you, I propose the name var_binding_t instead.

Thinking more about this - I actually don't mind that there is a C struct for a single Bindings.  I don't love it, but it doesn't bother me.
However, I am very bothered by the fact that people will think var_atom_t is a "variable atom type", which it absolutely is not.

var_atom_t is an attempt to represent one variable binding, and I agree the name is confusing. I also not sure it is a best way to represent bindings at the moment. As we now have bindings_t in C API may be we can replace var_atom_t by calling Bindings::resolve() method.

I ended up leaving the API functional semantics alone, for now, around adding and traversing bindings.  I just changed the function signatures to accept and provide single var-atom pairs, to line up with Rust.
I think we will want to reevaluate Bindings and BindingsSet representation and traversal when we implement comprehensions and non-determinism / inference control.  But that's a big project and I don't have a totally clear vision yet.

Changes merged.  Closing


Searching text "phone" inside a project

Hi,
First I would like to thank you for open-sourcing such a wonderful project. Thank you.
An issue I noticed on testing the 1.03 version.
I searched in project level and it works. But when I searched text phone lite crashes and throws
Fatal error in src/rencache.c: exhausted command buffer
When looking at code I noticed the error was thrown from https://github.com/rxi/lite/blob/23cf193026014a9d720e9690979299eb513f980e/src/rencache.c#L83
Is there a way we can increase this buffer size something similar to LITE_SCALE ?
Thank you once again for the beautiful project.

I'm assuming this was in a file with with long lines, if so this issue is a duplicate of #64

ok. I am not sure this was in a file with long lines for I cannot debug it. Is there a way we can understand this happened on X file / line ?

I'm a little confused how you don't know if the file you were searching had long lines or not. Without any more information I'm just going to assume this is the same issue as the one I mentioned above.

@rxi there are multiple files in the project. Some of them are js files. So it may be having long lines. But I am not sure which file is causing the issue for the error doesn't mention this happened in X file or I can see a log to check what happened for the failure.
I also guess this is same as the one you mentioned. But I cannot gaurantee that it is right for the current time. I can open if the issue you mentioned has been fixed and same error happened after that.
Question : Is there a way we can see more log? I noticed plugin loaded etc. But not anything like error happened at this line after search.

I can open if the issue you mentioned has been fixed and same error happened after that.

That sounds like the best approach.

Is there a way we can see more log? I noticed plugin loaded etc. But not anything like error happened at this line after search.

This issue happens on the C layer, for those kinds of errors there isn't a way of propagating more information to the UI the way unhandled lua errors do -- for example, the errors you'd encounter when developing a plugin would be logged to the UI with a traceback. Luckily the C layer specific to lite is small enough that there are few points of failure -- this is the only crash on this level I've experienced and I already have an idea of why it's happening and how to approach fixing it; these aren't errors that should be popping up frequently.

This looks fixed to some extend. Currently it logs the error to terminal. But good for now.


add jpa pagination for retrieve all transaction query

Codecov Report

Merging #781 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #781      +/-   ##
============================================
+ Coverage     99.43%   99.43%   +<.01%
- Complexity     1916     1918       +2
============================================
  Files           288      288
  Lines          5699     5708       +9
  Branches        289      290       +1
============================================
+ Hits           5667     5676       +9
  Misses            5        5
  Partials         27       27

Impacted Files
Coverage Δ
Complexity Δ

...um/tessera/transaction/TransactionManagerImpl.java
100% <100%> (ø)
36 <10> (+1)
:arrow_up:

...ssera/transaction/EncryptedTransactionDAOImpl.java
100% <100%> (ø)
7 <2> (+1)
:arrow_up:

...uorum/tessera/data/migration/JdbcDataExporter.java
100% <0%> (ø)
4% <0%> (ø)
:arrow_down:

...rum/tessera/data/migration/SqliteDataExporter.java
100% <0%> (ø)
4% <0%> (ø)
:arrow_down:

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 36ec657...070df2a. Read the comment docs.


Tokens section

Maybe "JBX Tokens" with sublabels "Total supply", and "Yours" ?

@peripheralist

good call. updating


types: ensure location attrs exists

Initial checklist

[x] I read the support docs
[x] I read the contributing guide
[x] I agree to follow the code of conduct
[x] I searched issues and couldn’t find anything (or linked relevant results below)
[x] If applicable, I’ve added docs and tests

Description of changes
TypeScript can't quite infer that location.attr is not undefined from the loop, this gives TS an extra hint.

Ping!


TN-713 service token management

New scheduled job (on both systems) to run a daily check for expired tokens (deletes stale) and nearly expired service tokens (emails sponsor).

Hello @pbugni! Thanks for submitting the PR.

In the file portal/models/auth.py, following are the PEP8 issues :

Line 409:1: E302 expected 2 blank lines, found 1


Suggest french translation for vue readme

Suggest french translation for vue3 readme file readme file
Did you build the project before submitting the PR?

[ ] Yes
[X] No

I usually do one PR per file that I translate on other projects, it's easier afterwards to correct / discuss about typos if there are any, but yes, on my way 🙂


Cleanup collection

Grammar and formatting fixes
Fix a reference link
Capitalize keywords
Wordsmith a few sentences to improve clarity

Thank you.


Can not add the device

I can not add the device, which was added before (and deleted after that).
The log shows just the following:
2023-01-04 19:16:46.036 INFO (MainThread) [custom_components.tuya_local.device] Setting protocol version for Test to 3.3.
2023-01-04 19:16:46.040 DEBUG (SyncWorker_7) [custom_components.tuya_local.device] Refreshing device state for Test.
...
2023-01-04 19:17:31.096 DEBUG (SyncWorker_7) [custom_components.tuya_local.device] Retrying after exception 'dps'
2023-01-04 19:17:31.097 INFO (SyncWorker_7) [custom_components.tuya_local.device] Setting protocol version for Test to 3.1.
...
2023-01-04 19:28:33.489 ERROR (SyncWorker_7) [custom_components.tuya_local.device] Failed to refresh device state for Test.

no more details.
Tried both the latest version (2022.12.1) and 0.20.5. Tried when according yaml available and when it is not.
When I add the device, just the configuration window is shown with loading indicator:

and then after 10 minutes of waiting

Unable to connect to your device with those details. It could be an intermittent issue, or they may be incorrect.

Hmm, I've deleted the device from Tuya and added it again and it started to be found by your addon. Not sure what was the problem (id remains the same, ip is the same, just local key is changed).


SparkAggregationFuzzerTest doesn't share the default AggregationFuzzerRunner::customVerificationFunctions_ list

Description
This problem was discovered in https://github.com/facebookincubator/velox/pull/5711.
Some aggregation functions require special handling during verification in fuzzer. There is a default list of them in AggregationFuzzerRunner. Both the Presto and Spark aggregation fuzzer test uses AggregationFuzzerRunner. However, the Presto aggregation fuzzer test uses this default AggregationFuzzerRunner::customVerificationFunctions_, while the Spark aggregation fuzzer test passes its own customVerificationFunctions list to AggregationFuzzerRunner::runFuzzer() and this replaces the default one. This means that if there is an aggregation function used in both Presto and Spark and require custom verification, we'll need to add it to both AggregationFuzzerRunner::customVerificationFunctions_ and customVerificationFunctions in SparkAggregationFuzzerTest, which is not the best setting.
https://github.com/facebookincubator/velox/blob/7543853b46c5dfe1451e2c70b31ef5dd1f661c84/velox/exec/tests/AggregationFuzzerRunner.h#L83-L115
https://github.com/facebookincubator/velox/blob/7543853b46c5dfe1451e2c70b31ef5dd1f661c84/velox/exec/tests/SparkAggregationFuzzerTest.cpp#L59-L63
If we step back and look at the design, there are three situations:

If there are separate Presto and Spark aggregation functions in Velox that have the same function name, then having a shared customVerificationFunctions_ list in AggregationFuzzerRunner doesn't make sense. Instead, individual lists of custom-verification functions should be defined in the Presto and Spark aggregation fuzzer tests separately.
If all Presto and Spark aggregation functions of the same names share the same implementation, the custom-verification-functions list defined in SparkAggregationFuzzerTest should be complementary to AggregationFuzzerRunner::customVerificationFunctions_ rather than a replacement of it.
If some Presto and Spark aggregation functions of the same names share the same implementation and some are implemented separately, then we can take the same approach as case (1).

Error Reproduction
N/A
Relevant logs
N/A

If some Presto and Spark aggregation functions of the same names share the same implementation and some are implemented separately, then we can take the same approach as case (1).

Looks the third case is closer to current status, then below action should be applied base on the suggestion from case (1), am I right?

Individual lists of custom-verification functions should be defined in the Presto and Spark aggregation fuzzer tests separately.


added/updated new cmdlets for October 2018 Release

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/docs-conceptual/sharepoint-pnp/sharepoint-pnp-cmdlets.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPDocumentSet.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPFile.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPProvisioningSequence.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPProvisioningSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPProvisioningSubSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPProvisioningTemplate.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Apply-PnPProvisioningHierarchy.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Clear-PnpRecycleBinItem.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPException.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPField.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPHubSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPLabel.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPListItem.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPProvisioningSequence.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPProvisioningSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPSearchCrawlLog.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPTerm.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPUnifiedGroup.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPProvisioningCommunicationSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPProvisioningHierarchy.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPProvisioningSequence.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPProvisioningTeamNoGroupSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPProvisioningTeamNoGroupSubSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPProvisioningTeamSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPProvisioningTemplate.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/New-PnPSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Read-PnPProvisioningHierarchy.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Read-PnPProvisioningTemplate.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Remove-PnPWebPart.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Restore-PnpRecycleBinItem.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Save-PnPProvisioningHierarchy.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Save-PnPProvisioningTemplate.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPLabel.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Set-PnPWeb.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Submit-PnPSearchQuery.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-pnp/Test-PnPProvisioningHierarchy.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Remove unecessary sorts, add undefined check to packageJson sort

Nx 13+ already handles sorting the TsConfig paths and Workspace projects so I've removed them from the command so this now only sorts the package.json scripts property now.
Added an undefined check to the sort function so that it doesn't add the property if it doesn't exist. Should never happen since package.json should always have the scripts property.
Fixes:
#152

Merged in #154


Add Python 3 support

Various commands are hardcoded to run python2.7 which prevents this project from being used by users of Django 1.5+ on Python 3. It may also be good to clarify supported Python versions in setup.py and the README.

Fixed in 2.14.5


Render the Readme from Github

As an OSS Concourse User when I click on a particular resource I am brought to the details page.
I see the Readme file from Github displayed on the page. The Readme file should be no older than 24 hours.
So that I can understand more detail about the resource including what the Resource does and how I should use it.
Acceptance
Scenario 1
Given I am on the Duty Free home page
When I click on a particular resource
I see the details page for that resource which displays the Readme file for the same resource that I clicked on.
Scenario 2
Given I am on the Duty Free home page
When I click on a particular resource that has been updated more than 24 hours ago
I see the details page for that resource which displays the correct Readme file for the same resource that I clicked on.
Dev Notes

retrieve rendered html: curl -H 'Accept: application/vnd.github.VERSION.html' https://api.github.com/repos/carlo-colombo/telegram-resource/readme
unrendered markdown: curl -H 'Accept: application/vnd.github.VERSION.raw' https://api.github.com/repos/carlo-colombo/telegram-resource/readme

Dev tasks

[ ] generate a token for duty free team/repository moving away from personal
[x] refactor tests to use mock github server instead of real gh
[x] add token to lastpass account
[x] use token in pipeline to generate html

@concourse/duty-free what we should do if retrieving the readme generate an error (eg github is down)

At the moment we are using a personal token instead of one from a machine user (@concourse-bot), add to the pipeline to run every day (morning utc time) to rebuild the website to keep the readme fresh

Accepted by @Pivotal-Kevin-Curley. Behaviour is as per acceptance criteria.


run on google Colab

Hello, can you please help to run the code on google colab?
How to view images on the colab without doing much work? For each file? Probably creating a directory on the notebook colab folder, where I put all the images?
Right now I get this error:
Image(filename='images/03_01.png', width=400)
---------------------------------------------------------------------------
FileNotFoundError                         Traceback (most recent call last)
<ipython-input-149-4c8da45e0c5c> in <module>()
----> 1 Image(filename='images/04_01.png', width=400)

Then there's the watermark problem, which is easy, I've just added pip install to your files:
# add this to run in colab:
!pip install -q -U watermark
# this is the same
%load_ext watermark
%watermark -a "Sebastian Raschka" -u -d -p numpy,pandas,matplotlib,sklearn

Hi there.
Like you said, the errors are due to the missing images. There are multiple options you can try.

You could download the image folder from https://github.com/rasbt/python-machine-learning-book-3rd-edition/tree/master/ch03/images and then upload it to Google Colab. It should be relatively easy now with their drag and drop interface.

You could comment out or disable those cells because they are not really needed. I just have them in the notebooks so it is easier to find the respective code when looking at the notebooks

You could replace the relative links by links to the images on github, but this would probably be tedious.


pg_compat_window.slt fails when target_partitions >= 32

Describe the bug
error: test failed, to rerun pass `-p datafusion --test sqllogictests`

Error: query failed: DataFusion error: Arrow error: External error: Arrow error:
External error: Arrow error: External error: Arrow error: External error:
Arrow error: Invalid argument error:
number of columns(27) must match number of fields(35) in schema

[SQL] SELECT
    SUM(c4) OVER(ORDER BY c3 DESC GROUPS BETWEEN 3 PRECEDING AND 1 FOLLOWING) as summation1,
    SUM(c4) OVER(ORDER BY c3 DESC GROUPS BETWEEN 3 PRECEDING AND 2 PRECEDING) as summation2,
    SUM(c5) OVER(ORDER BY c4 DESC GROUPS BETWEEN 2 PRECEDING AND 2 PRECEDING) as summation3,
    SUM(c4) OVER(ORDER BY c3 DESC GROUPS BETWEEN 1 FOLLOWING AND 3 FOLLOWING) as summation4,
    SUM(c3) OVER(ORDER BY c4 DESC GROUPS BETWEEN 1 FOLLOWING AND 1 FOLLOWING) as summation5,
    SUM(c5) OVER(ORDER BY c3 DESC GROUPS 2 PRECEDING) as summation6,
    SUM(c5) OVER(ORDER BY c3 DESC GROUPS BETWEEN CURRENT ROW AND 3 FOLLOWING) as summation7,
    SUM(c5) OVER(ORDER BY c4 DESC GROUPS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING) as summation8,
    SUM(c4) OVER(ORDER BY c4 DESC GROUPS UNBOUNDED PRECEDING) as summation9,
    SUM(c5) OVER(ORDER BY c4 DESC GROUPS CURRENT ROW) as summation10,
    SUM(c5) OVER(ORDER BY c4 DESC GROUPS BETWEEN CURRENT ROW AND UNBOUNDED FOLLOWING) as summation11,
    SUM(c5) OVER(ORDER BY c4 DESC GROUPS BETWEEN 1 PRECEDING AND UNBOUNDED FOLLOWING) as summation12,
    SUM(c5) OVER(ORDER BY c4 DESC GROUPS BETWEEN 1 FOLLOWING AND UNBOUNDED FOLLOWING) as summation13,
    SUM(c4) OVER(PARTITION BY c4 ORDER BY c3 GROUPS BETWEEN 3 PRECEDING AND 1 FOLLOWING) as summation21,
    SUM(c4) OVER(PARTITION BY c4 ORDER BY c3 GROUPS BETWEEN 3 PRECEDING AND 2 PRECEDING) as summation22,
    SUM(c5) OVER(PARTITION BY c4 ORDER BY c4 GROUPS BETWEEN 2 PRECEDING AND 2 PRECEDING) as summation23,
    SUM(c4) OVER(PARTITION BY c4 ORDER BY c3 GROUPS BETWEEN 1 FOLLOWING AND 3 FOLLOWING) as summation24,
    SUM(c3) OVER(PARTITION BY c4 ORDER BY c4 GROUPS BETWEEN 1 FOLLOWING AND 1 FOLLOWING) as summation25,
    SUM(c5) OVER(PARTITION BY c4 ORDER BY c3 GROUPS 2 PRECEDING) as summation26,
    SUM(c5) OVER(PARTITION BY c4 ORDER BY c3 GROUPS BETWEEN CURRENT ROW AND 3 FOLLOWING) as summation27,
    SUM(c5) OVER(PARTITION BY c4 ORDER BY c4 GROUPS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING) as summation28,
    SUM(c4) OVER(PARTITION BY c4 ORDER BY c4 GROUPS UNBOUNDED PRECEDING) as summation29,
    SUM(c5) OVER(PARTITION BY c4 ORDER BY c4 GROUPS CURRENT ROW) as summation30,
    SUM(c5) OVER(PARTITION BY c4 ORDER BY c4 GROUPS BETWEEN CURRENT ROW AND UNBOUNDED FOLLOWING) as summation31,
    SUM(c5) OVER(PARTITION BY c4 ORDER BY c4 GROUPS BETWEEN 1 PRECEDING AND UNBOUNDED FOLLOWING) as summation32,
    SUM(c5) OVER(PARTITION BY c4 ORDER BY c4 GROUPS BETWEEN 1 FOLLOWING AND UNBOUNDED FOLLOWING) as summation33,
    SUM(c4) OVER(ORDER BY c5, c3 GROUPS BETWEEN 3 PRECEDING AND 1 FOLLOWING) as summation41,
    SUM(c4) OVER(ORDER BY c5, c3 GROUPS BETWEEN 3 PRECEDING AND 2 PRECEDING) as summation42,
    SUM(c5) OVER(ORDER BY c5, c4 GROUPS BETWEEN 2 PRECEDING AND 2 PRECEDING) as summation43,
    SUM(c4) OVER(ORDER BY c5, c3 GROUPS BETWEEN 1 FOLLOWING AND 3 FOLLOWING) as summation44,
    SUM(c3) OVER(ORDER BY c5, c4 GROUPS BETWEEN 1 FOLLOWING AND 1 FOLLOWING) as summation45,
    SUM(c5) OVER(ORDER BY c5, c3 GROUPS 2 PRECEDING) as summation46,
    SUM(c5) OVER(ORDER BY c5, c3 GROUPS BETWEEN CURRENT ROW AND 3 FOLLOWING) as summation47,
    SUM(c5) OVER(ORDER BY c5, c4 GROUPS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING) as summation48,
    SUM(c4) OVER(ORDER BY c5, c4 GROUPS UNBOUNDED PRECEDING) as summation49,
    SUM(c5) OVER(ORDER BY c5, c4 GROUPS CURRENT ROW) as summation50,
    SUM(c5) OVER(ORDER BY c5, c4 GROUPS BETWEEN CURRENT ROW AND UNBOUNDED FOLLOWING) as summation51,
    SUM(c5) OVER(ORDER BY c5, c4 GROUPS BETWEEN 1 PRECEDING AND UNBOUNDED FOLLOWING) as summation52,
    SUM(c5) OVER(ORDER BY c5, c4 GROUPS BETWEEN 1 FOLLOWING AND UNBOUNDED FOLLOWING) as summation53,
    SUM(c4) OVER(ORDER BY c3 GROUPS BETWEEN 3 PRECEDING AND 1 FOLLOWING) as summation61,
    SUM(c4) OVER(ORDER BY c3 GROUPS BETWEEN 3 PRECEDING AND 2 PRECEDING) as summation62,
    SUM(c5) OVER(ORDER BY c4 GROUPS BETWEEN 2 PRECEDING AND 2 PRECEDING) as summation63,
    SUM(c4) OVER(ORDER BY c3 GROUPS BETWEEN 1 FOLLOWING AND 3 FOLLOWING) as summation64,
    SUM(c3) OVER(ORDER BY c4 GROUPS BETWEEN 1 FOLLOWING AND 1 FOLLOWING) as summation65,
    SUM(c5) OVER(ORDER BY c3 GROUPS 2 PRECEDING) as summation66,
    SUM(c5) OVER(ORDER BY c3 GROUPS BETWEEN CURRENT ROW AND 3 FOLLOWING) as summation67,
    SUM(c5) OVER(ORDER BY c4 GROUPS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING) as summation68,
    SUM(c4) OVER(ORDER BY c4 GROUPS UNBOUNDED PRECEDING) as summation69,
    SUM(c5) OVER(ORDER BY c4 GROUPS CURRENT ROW) as summation70,
    SUM(c5) OVER(ORDER BY c4 GROUPS BETWEEN CURRENT ROW AND UNBOUNDED FOLLOWING) as summation71,
    SUM(c5) OVER(ORDER BY c4 GROUPS BETWEEN 1 PRECEDING AND UNBOUNDED FOLLOWING) as summation72,
    SUM(c5) OVER(ORDER BY c4 GROUPS BETWEEN 1 FOLLOWING AND UNBOUNDED FOLLOWING) as summation73
FROM aggregate_test_100_by_sql
ORDER BY c9;
at tests/sqllogictests/test_files/pg_compat/pg_compat_window.slt:417

To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here.

I get this when running cargo test against the master branch as well

I also meet this bug.
It seems this is relative to the config of datafusion.execution.target_partitions, I can reproduce it with datafusion-cli. When target_partitions is less than 32, this test will success, but when I set it to 32, test will fail.

Thanks @ygf11! That saved me a ton of time this morning. I will ignore this test for now by moving it into a different directory so I can create the 17.0.0 release candidate.

This test was added in https://github.com/apache/arrow-datafusion/pull/4834 by @melgenek

cc @melgenek
I think we should hard code the target partitions in the sqllogictest test runner (which will be needed for deterministic plans anyways). I'll get a PR up for this

https://github.com/apache/arrow-datafusion/pull/5089 proposed fix

cc @metesynnada @mustafasrepo


Switch goes unavailable every hour

Version of the integration

1.6.1
Configuration

Several devices with the following:

Name: P110
Firmware: 1.1.6 Build 221114 Rel.203339
Hardware: 1.0

And one P100

Name: P110
Firmware: 1.4.10 Build 20211104 Rel. 35882
Hardware: 1.20.0

Error fetching tapo data: Error communication with API: Cannot connect to host <IP_ADDRESS>:80 ssl:default [Connect call failed ('<IP_ADDRESS>', 80)]
Error fetching tapo data: Error communication with API: Cannot connect to host <IP_ADDRESS>:80 ssl:default [Connect call failed ('<IP_ADDRESS>', 80)]
Error fetching tapo data: Error communication with API: Cannot connect to host <IP_ADDRESS>:80 ssl:default [Connect call failed ('<IP_ADDRESS>', 80)]
Error fetching tapo data: Error communication with API: Cannot connect to host <IP_ADDRESS>:80 ssl:default [Connect call failed ('<IP_ADDRESS>', 80)]

Describe the bug
Checking the logs and history of the integration with some the Tapo switches, I've seen a common pattern where literally every hour or every XX:58-59:XX, the devices goes unavailable and comes back again after a few minutes. Check the image below:

If you check above, there are little white bars that indicates the unavailability of the device. It's something that's is messing up with some automations I have in place and was wondering if it's a known issue or if it's normal.
It worths mentioning though, my password credentials contains uppercase and special characters but I don't see how that can be related when they are able to connect for 1 hour in periods.
Additionally, the time the switch remains unavailable is 30 seconds that I guess should be a polling interval set somewhere.
Debug log

023-03-02 09:01:16.198 ERROR (MainThread) [custom_components.tapo.common_setup] Error fetching tapo data: Unexpected exception:
2023-03-02 09:01:16.200 DEBUG (MainThread) [custom_components.tapo.common_setup] Finished fetching tapo data in 10.004 seconds (success: False)
2023-03-02 09:01:16.226 ERROR (MainThread) [custom_components.tapo.common_setup] Error fetching tapo data: Unexpected exception:
2023-03-02 09:01:16.228 DEBUG (MainThread) [custom_components.tapo.common_setup] Finished fetching tapo data in 10.004 seconds (success: False)
2023-03-02 09:01:40.525 DEBUG (MainThread) [custom_components.tapo.common_setup] Finished fetching tapo data in 0.243 seconds (success: True)
2023-03-02 09:01:40.613 DEBUG (MainThread) [custom_components.tapo.common_setup] Finished fetching tapo data in 0.216 seconds (success: True)
2023-03-02 09:01:41.562 DEBUG (MainThread) [custom_components.tapo.common_setup] Finished fetching tapo data in 0.416 seconds (success: True)
2023-03-02 09:01:46.314 INFO (MainThread) [custom_components.tapo.common_setup] Fetching tapo data recovered
2023-03-02 09:01:46.314 DEBUG (MainThread) [custom_components.tapo.common_setup] Finished fetching tapo data in 0.090 seconds (success: True)
2023-03-02 09:01:46.334 INFO (MainThread) [custom_components.tapo.common_setup] Fetching tapo data recovered

From the code here, I see it's sending a cookie token, could it be that the cookies have an expiration time of approx 60 min ? Although I also see the cookies' jar is being cleared here.

Also, I've realized that the uncaught exception on the logs is because there is a a 10 seconds timeout set that does not raise any message, that's why it's empty.
It does not explain why every hour though.

@petretiandrea any hint or something else I could try to debug it? Sorry for the direct mention though.

Try v2.0.0


Can't get orders, positions or wallets

Hi,
I can place orders fine but the code:
wss = BtfxWss(key, secret)
wss.start()
wss.authenticate()
wss.orders.empty()
Always returns True, how can I get my orders, positions and wallets using btfxwss?

Hey @FelipeSBonetto and thanks for reporting this issue!
I need a few more details to help you out:

Can you confirm that authentication works? Are there any errors raised or logged?
Confirm that you are receiving data on the other authenticated channels (as a reference, check this file, starting at line 58, to see what private channels you can try polling). If all are empty, there may be something wrong with the authentication.
Could you run the above code with debugging enabled and attach the log file? You just have to add the following lines and it should work:

import logging
logging.basicConfig(filename="btfxwss.log", level=logging.DEBUG)

wss=BtfxWss(key, secret, log_level=logging.DEBUG)
...

I have a sense that I'm doing something fundamentaly wrong, because I can actually see my balance in the log file. Probably I just don't know how to use the functions.
I'll be happy to help you write a documentation for this code.
btfxwss.txt
PS.: I saw in other forks a function to see Bids and Offers out of the Order Book. Have this function become discontinued in recent commits? Why?
Thanks!

Hey @FelipeSBonetto ,
So it turns out that I hadn't implemented the _handle_account() method in the main routine of QueueProcessor (#28), which is what you can see in the logs (it logs errors for all messages from channel id 0). I fixed this in my last commit, so give it another try and let me know if this works now - im on vacation atm, and can't verify it myself.
As for the bids and offers:
The client, as it is currently implemented, is just meant to abstract away the process of connecting to the api and receiving the data. That's why all data is provided as it is received via Queue objects. These are accessed via properties or methods of BtfxWss instances.
So, to answer your question: You CAN access this data, but it is raw - meaning that you will have to build an order book yourself if you want to see the current bids and asks, for example.
You can get this data by calling these:
wss = BtfxWss()
wss.books('BTCUSD')  # Returns order book data for BTCUSD

Now that I'm looking at it, it would perhaps be better to make them all available as a property, instead of part method, part property.

Hello @nlsdfnbch, thanks for your reply!
I tried to run this code:
wss.wallets.get()
but got:
_handle_account() missing 1 required positional argument: 'ts'
Not shure if it's a bug or if it's me. Tried to look for some clues on the code but couldn't figure it out

That issue should be handled now - PR #30 is now merged into dev, so if you use the dev branch it should now work for you!
I'll update the pypi release once i'm back from vacation.
Thanks for your help!


Updates for the actions module

move to parsing via whatever we define in #63
better parsing for deletion vectors
types.rs -> actions.rs (a bit confusing as we'll have actions::actions)

Already done as part of #109


Feature request: add a visual browser for credhub

Problem
The credhub CLI includes a great way to explore the entire tree of creds via the command line.
Its difficulty comes when trying to get/set multiple fields. The import command was enabled to help alleviate this.
When it comes to exploring the data, export helped immensely. Being able to see all the values are transverse the tree is very useful.
With any of these mechanisms, it can be repetitive to lookup fields, remember all the options to set, etc. Editing large YAML files can be difficult as it is YAML and remembering what’s on line 10 is hard when on line 1001.
Proposal
The data for credhub is structured by types (ie password, username, etc) it fits well into the shape of a form. An HTML form would be useful to edit/add/delete values from credhub.
I’d like to propose credhub-cli web or maybe credhub-cli explorer.
When enabled from the local command line, it would start a local server, that only the current user can use (via the targeting creds on the machine), to explore their remote credhub.
Something similar to vault ui.
Features

Tree explorer, which just allows you to expand/fold creds through the path of all the keys.
Add, edit, or remove a specific key.

I’m happy to help work on this. I’d like to start a discussion to see if this a viable feature.

@jtarchie ah yes, the CredHub UI question. I would recommend one of two things.

Check out this UI that another community member built: https://github.com/shreddedbacon/credhub-webui. The CredHub team does not support this, but you could reach out to the maintainer to chat with them about it.
Talk to @jparnala. He has had a lot of good thoughts about where CredHub could go in the future, and where a UI fits into that future.

Sweet! Thanks for the follow up.
I'll close as there is a solution.


Script no longer working

So the site recently updated to 2.0 and now what i see is a black screen. I have tried refreshing and reopening browser but none of it works...

yup,, this happened 2 hours ago+-

@LePoissonBleu
yeah the site was down for a long time.

Hi, please check #26 for more information.


field basedOn on referral task

reading the cookbook v0.1, I see that a referral task must be linked to a prescription via its basedOn field. In the profile https://build.fhir.org/ig/hl7-be/referral/StructureDefinition-be-referral-task.html, you should mark this field as must support.

WG: we agree.


Strings are being trimmed

If you are reporting bug/issue, please provide detailed Repro instructions.
Repro Steps

Create a .NET (Full Framework) app
Submit a Trace in the following way:

string message = "          I have 10 leading spaces"
var trace = new TraceTelemetry
{
     Timestamp = timestamp,
     Message = message
};

trace.Properties["BackupMessage"] = message;
TelemetryClient.TrackTrace(trace);

Actual Behavior
Both Message and BackupMessage are set to "I have 10 leading spaces" (leading whitespace is being trimmed).
Expected Behavior
Both Message and BackupMessage should be set to "          I have 10 leading spaces".
Version Info
SDK Version : 2.8.1
.NET Version : 4.7.2
How Application was onboarded with SDK(VisualStudio/StatusMonitor/Azure Extension) : VisualStudio
OS : Windows 10
Hosting Info (IIS/Azure WebApps/ etc) : Console app

This appears to be due to https://github.com/Microsoft/ApplicationInsights-dotnet/blob/bd0368b1fb01bda56cd177c0c1518968728d49f3/src/Microsoft.ApplicationInsights/DataContracts/TraceTelemetry.cs#L155
At the moment this detail seems to be hidden from the user, this should be made clear to the user, and ideally should be optional.


Implement relu

Hello,
I started to implement the relu function for the genann library on a fork under my name (https://github.com/kasey-/genann) before sending you a PR:
double inline genann_act_relu(const struct genann *ann unused, double a) {
    return (a > 0.0) ? a : 0.0;
}

But I am a bit lost in the way you compute the back propagation of the neural network. The derivative of relu formula is trivial (a > 0.0) ? 1.0 : 0.0  But I cannot understand were I should plug-it inside your formula as I do not understand how do you compute your back propagation. Did you implemented only the derivate of the sigmoid ?

I would like ReLU in genann too, but the back propagation is also something I understand here :(

Yes, In the code derivate of sigmoid "ddxσ(x)=σ(x)(1−σ(x))" is only implemented. I think we have to write a generic function of derivatives so that, we can add other activation functions like tanh and Relu
check the code here
https://github.com/kasey-/genann/blob/27c4c4288728791def0c5fd175c1c3999057ad9d/genann.c#L335
If you agree I can also work on this.

Hi everyone,
To actually implement Relu and linear what exactly should we be looking at other than the back propagation derivative?
Would it also require any additional functions like how sigmoid has genann_act_sigmoid_cached and genann_init_sigmoid_lookup?
Any advice...

Hi everyone, To actually implement Relu and linear what exactly should we be looking at other than the back propagation derivative? [snip]

It's right there at the top of this bug report thread, double inline genann_act_relu.


RUMM-2039 Always send data when device has external power source

What does this PR do?
A brief description of the change being made with this pull request.
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #858 (865822b) into develop (c88de23) will increase coverage by 0.04%.
The diff coverage is 92.31%.

@@             Coverage Diff             @@
##           develop     #858      +/-   ##
===========================================
+ Coverage    81.64%   81.69%   +0.04%
===========================================
  Files          256      256
  Lines         8568     8578      +10
  Branches      1452     1453       +1
===========================================
+ Hits          6995     7007      +12
  Misses        1239     1239
+ Partials       334      332       -2

Impacted Files
Coverage Δ

...datadog/android/core/internal/system/SystemInfo.kt
87.50% <50.00%> (+0.83%)
:arrow_up:

...id/core/internal/data/upload/DataUploadRunnable.kt
100.00% <100.00%> (ø)

...rnal/system/BroadcastReceiverSystemInfoProvider.kt
97.62% <100.00%> (+0.56%)
:arrow_up:

...id/webview/internal/rum/WebViewRumEventConsumer.kt
76.74% <0.00%> (-9.30%)
:arrow_down:

...android/rum/internal/ndk/DatadogNdkCrashHandler.kt
87.95% <0.00%> (+1.20%)
:arrow_up:

...ain/java/com/datadog/opentracing/PendingTrace.java
60.68% <0.00%> (+1.71%)
:arrow_up:

...main/java/com/datadog/exec/CommonTaskExecutor.java
51.02% <0.00%> (+4.08%)
:arrow_up:


DRILL-6478: enhance debug logs for batch sizing

@kkhatua simple change. can you quickly review ?

@ppadma  looks like the primary enhancement is to have the logging limited to a single line. If that is it, then it LGTM. +1

@ppadma - Can you please look into the travis failures ?

@sohami it is some timeout issue. I built and ran tests fine on my local mac.

@ppadma you always can re-start Travis in case build failed with timeout or any other unrelated failure.

@arina-ielchiieva That button is only enabled for committers. If your not a committer the only way to restart the build is to open and close the PR or to push a new commit.

@sohami addressed review comments. please take a look.

@sohami ok, made the change.

LGTM +1


Subaru: move to flags within PlatformConfig

any thoughts on this?

honda will need this framework first, because it uses the HONDA_BOSCH set within CarInfo

going to merge this and try with toyota, if we don't like it we can revert or change stuff

I can do the Toyota one with these changes and see how it goes


Test & review the Azure deployment templates & docs we got from Microsoft

[x] Get account set up to use Microsoft Azure
[ ] Test the Azure Resource Manager template (JSON) Microsoft sent to us (to install BigchainDB on a VM on Azure)
[ ] Provide feedback to Microsoft
[ ] More?

I have a Microsoft account that I could use with Microsoft Azure, but first I asked around to see if we have any (e.g. a corporate account or whatever).
As it happens, Bruce signed up for the Microsoft BizSpark program to give deals to startup companies some time ago. His<EMAIL_ADDRESS>account initiated that and then he (or someone) added four more team members, all of whom could get the deals. (You can only have five team members total.) Two of the team members were since "deleted" but we can't add any more.
Bottom line: currently there are three BigchainDB (the company) -related Microsoft accounts that can get 130 Euros per month of Azure usage for free (until our BizSpark deals expire in about a year): Bruce, Dimi and Trent.


FormFileModelBinder should support IFormFileCollection

Doing this:
        [HttpPost]
        public IActionResult Index(IFormFileCollection files)
        {
            return View();
        }

Gives you this:
System.ArgumentException: Object of type 'System.Collections.Generic.List`1[Microsoft.AspNet.Http.IFormFile]' cannot be converted to type 'Microsoft.AspNet.Http.IFormFileCollection'.
   at System.RuntimeType.TryChangeType(Object value, Binder binder, CultureInfo culture, Boolean needsSpecialCast)
   at System.RuntimeType.CheckValue(Object value, Binder binder, CultureInfo culture, BindingFlags invokeAttr)
   at System.Reflection.MethodBase.CheckArguments(Object[] parameters, Binder binder, BindingFlags invokeAttr, CultureInfo culture, Signature sig)
   at System.Reflection.RuntimeMethodInfo.InvokeArgumentsCheck(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at Microsoft.AspNet.Mvc.Controllers.ControllerActionExecutor.ExecuteAsync(MethodInfo actionMethodInfo, Object instance, Object[] orderedActionArguments)
   at Microsoft.AspNet.Mvc.Controllers.ControllerActionInvoker.<InvokeActionAsync>d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at Microsoft.AspNet.Mvc.Controllers.FilterActionInvoker.<InvokeActionFilterAsync>d__48.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNet.Mvc.Controllers.FilterActionInvoker.<InvokeAsync>d__39.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNet.Mvc.Infrastructure.MvcRouteHandler.<RouteAsync>d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNet.Mvc.Routing.InnerAttributeRoute.<RouteAsync>d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNet.Routing.RouteCollection.<RouteAsync>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNet.Builder.RouterMiddleware.<Invoke>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNet.Diagnostics.DeveloperExceptionPageMiddleware.<Invoke>d__7.MoveNext()

Even if we don't want to support this type, we're doing the wrong check here:  https://github.com/aspnet/Mvc/blob/dev/src/Microsoft.AspNet.Mvc.Core/ModelBinding/FormFileModelBinder.cs#L36
This means that we'll attempt to bind anything that implements IEnumerable<IFormFile> to a List<IFormFile. This should only attempt to bind when we can actually do the binding successfully.

Let's fix the casting issue and also add support for IFormFileColleciton.

FYI updated link to the code: https://github.com/aspnet/Mvc/blob/dev/src/Microsoft.AspNetCore.Mvc.Core/ModelBinding/FormFileModelBinder.cs#L36-L37

Other cleanup and fixes:

49ffeb1 (test fix)
f889965 (simplify IsAssignableFrom() use; improve KeyValuePairModelBinder type handling)

d3c2463


InkWell splash doesn't work in a stack layout

I was writing a code. I was using stack and inside it there is an image and an inkwell widgets. when I am pressing on inkwell, shadow is being casted behind the image.
You can do this emulation very easily. Just take an image and inkwell do the padding on the right or left any side. So we can expose the background of the image to inkwell half way. And then press on the inkwell. You see the shadow should be casted below the inkwell above the image but it is having some weird behaviour.
Tested my code on 2.10.4
MaterialApp(
      home: Scaffold(
        body: Center(
          child: Stack(
            alignment: AlignmentDirectional.bottomEnd,
            children: [
              Padding(
                padding: const EdgeInsets.all(16.0),
                child: Image.network('https://picsum.photos/200'),
              ),
              InkWell(
                onTap: () {},
                child: const Icon(
                  Icons.undo_rounded,
                  size: 50,
                ),
              ),
            ],
          ),
        ),
      ),
    );

I like to add one more thing if it's helpful.
I after failed to use inkwell. Used elevated button to achieve the task and it's working properly.

this happens because InkWell draws its splash on the nearest Material.
Images are not Materials, but they are drawn on top of it, covering it and hiding the splash.
This is working as intended.
If you want to show the splash on top of the image, you can insert a transparent Material between the InkWell and the Image.
Stack(
  alignment: AlignmentDirectional.bottomEnd,
  children: [
    Padding(
      padding: const EdgeInsets.all(16.0),
      child: Image.network('https://picsum.photos/200'),
    ),
    Material(
      type: MaterialType.transparency,
      child: InkWell(
        onTap: () {},
        child: const Icon(
          Icons.undo_rounded,
          size: 50,
        ),
      ),
    )
  ],
);


How do I properly unmount the camera with react-navigation❓

Question
How do I properly unmount the camera with react-navigation using useIsFocused() ?
What I tried
I've tried the necessary unmounting methods from the docs using isForeground hook from the example and  isFocussed from react navigation. The is isForeground works but when I go back to previous screen the green indicator still active.

Deps
"dependencies": {
    "@react-navigation/native": "^6.1.6",
    "@react-navigation/native-stack": "^6.9.12",
    "react": "18.1.0",
    "react-native": "0.70.6",
    "react-native-safe-area-context": "^4.5.3",
    "react-native-screens": "^3.20.0",
    "react-native-vision-camera": "^2.15.4"
  },

Screens
export default function App() {
  return (
    <NavigationContainer>
      <Stack.Navigator>
        <Stack.Screen name="Home" component={HomeScreen} />
        <Stack.Screen name="Camera" component={CameraScreen} />
      </Stack.Navigator>
    </NavigationContainer>
  );
}

function HomeScreen() {
  const navigation = useNavigation();
  return (
    <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
      <Button
        title="navigate to camera"
        onPress={() => navigation.navigate('Camera')}
      />
    </View>
  );
}
function CameraScreen({navigation}) {
  const devices = useCameraDevices();
  const device = devices.back;
  const isForeground = useIsForeground();

  const isFocussed = useIsFocused();

  if (device == null) {
    return null;
  }
  const isActive = isForeground && isFocussed;
  return (
    <Camera
      style={StyleSheet.absoluteFill}
      device={device}
      isActive={isActive}
    />
  );
}

Device
Android
Preview
https://github.com/mrousavy/react-native-vision-camera/assets/44619375/56729ec4-820e-4669-a5ec-7fb2fea930a2
VisionCamera Version
2.15.4
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar questions in the issues page as well as in the discussions page and found none.

You can use navigation events (focus & blur).
https://reactnavigation.org/docs/navigation-events/

Closing as this is a stale issue - this might have been fixed with the full rewrite in VisionCamera V3 (🥳) - if not, please create a new issue.
If your issue has been fixed, consider sponsoring me on GitHub to say thanks 💖

@amjadbouhouch can you please share the solution if you solved it?

My project version is "react-native": "0.72.6" , "react-native-vision-camera": "^3.6.17" ,
I also encountered the same problem. Is there a solution available? After uninstalling the camera in Android, it still remains active. I have set the isActive={false} attribute。

@amjadbouhouch can you please share the solution if you solved it?

@JoyceQuerubino I don't, I was testing and playing around.


Add Reflect impls for various components

Related to #32, while trying to debug my invisible outlines, I popped open bevy_inspector_egui to (hopefully) tweak various outline parameters.
However, the outline components don't impl Reflect, so this isn't currently possible.

Fixed in 0.7.1.


[SPARK-47623][PYTHON][CONNECT][TESTS] Use QuietTest in parity tests

What changes were proposed in this pull request?
1, add def quiet in both ReusedPySparkTestCase and ReusedConnectTestCase;
2, replace existing QuietTest(self.sc) with self.quiet();
3, remove unnecessary overridden parity tests;
Why are the changes needed?
there are a lot of tests not enabled in parity test due to the usage of sc in with QuietTest(self.sc), some of them were break into def check_ and call the check_ functions in the parity tests;
However, there are still such tests not enabled.
This PR aims to enable QuietTest within parity tests and make it easier to enable the remaining tests (def check_ no longer needed).
Does this PR introduce any user-facing change?
no, test only
How was this patch tested?
ci
Was this patch authored or co-authored using generative AI tooling?
no

Merged to master.


Errors during building the demo app.

I was trying to build a demo app when the following issue appeared. Am I using wrong package manager or a node version?
How to reproduce

Clone the repository
Run yarn install
Run yarn run demo
See the following error :

Creating a build of the demo app...
Failed to compile.

chunk main [entry]
index.js
Missing external configuration for type:commonjs2

error Command failed with exit code 1.

Version information

Node Version: v10.14.2
yarn Version: 1.13.0
npm Version: 6.4.1
OS: macOS v10.14.3
Browser: Chrome
Browser Version: v72.0.3626.119

This issue should be fixed in the upcoming 0.3.0 release. There was a missing declaration in the webpack config specifically for the demo build.
If you'd like to try it sooner, our release candidate is available for testing, version 0.3.0-rc.0 is now published.

@james-martin-jd thank you, I'll give it a try on release candidate 👍

Version 0.3.0 is release, which fixes this issue


Addition of footer at blog page

Related Issue
#603
Description
Added footer on blog page
Type of PR

[ ] Bug fix
[x] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
**

**
check at this page
https://hemav009.github.io/AgriLearnNetwork/
Checklist:

[x] I have performed a self-review of my code
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

Additional context:
[Include any additional information or context that might be helpful for reviewers.]

The footer should be same as in home page. I can see you have placed the quick links towards right

@Suchitra-Sahoo  updated

Some changes have been made in search bar. You can look for those through website link. Those are not reflecting in your branch.

ok will update soon

@Suchitra-Sahoo  updated


Upgrade to .NET 8 and refactorings

Upgrade to .NET 8.
Refactor code to improve DI compatibility and mitigate possible HttpClient issues.
Added unit tests.

Looks perfect


Support for  Bert BETO

Ktrain should document how to provide support to use other BERT models (models in other languages) like  BETO  bert-base-spanish-wwm-uncased
https://github.com/dccuchile/beto
https://huggingface.co/dccuchile/bert-base-spanish-wwm-uncased
Regards,

This tutorial explains how to run other models.  For instance, this notebook uses the AraBERT model for Arabic.


chore: remove unused text fields

Currently we simply hard code the AlgoD client in the code and don't actually use the text fields to change AlgoD client. It causes unnecessary clutter and confusion so this PR removes it.

LGTM


Move the script tag to the body in the example

This means that the script won't block rendering earlier than needed. A preferable solution would be to use the async HTML attribute, but that would require a way to put the custom code in a callback, and this library isn't ready for that yet.
Here's an article on Javascript that blocks rendering: https://developers.google.com/speed/docs/insights/BlockingJS

Moving the script around is something developers should do on their own.
Yes it is "best-practice" but, depending on their scripting setup could lead to bad results. Best just leave the docs as they are and developers that are using the polyfill should know the best place to put it by default depending on their sites infrastructure.

If you don't want to change the example code, than at least document that the script tag's location is not required to be in the <head> section. As it stands, developers that are using the polyfill do not know the best place to put it by default as you said, because it doesn't just depend on the site infrastructure, it also depends on the behaviour of the script. For example, if a script is calling document.write, it will behave differently depending on whether it's in the <head> section or not. Even if I fully review the script's code and determine that it behaves correctly when included in the <body> section now, I don't have the reassurances of the documentation that an upgrade won't break it.

Please resubmit with the CLA signed if you feel strongly about this.

I'll do the busy work you require of me if you want. I'm not sure what benefit this is to the project, the contribution is a good one, and there is nothing left to do other than simply accept the pull request or reject the pull request. This "are you still alive" ping could be needlessly throwing away good contributions.


Adding references to page for better understanding

Adding all required reference links to the page for better navigations to understand related concepts.

/assign @xiangpengzhao

This change LGTM. I'd like to defer to sig-apps folks for a lgtm label.
/approve
also
/cc @janetkuo @erictune

Hi @janetkuo , @erictune, Can you please review it. This is already approved.

/lgtm


feat(router): implement ApiKeyInterface for MockDb

Type of Change

[ ] Bugfix
[x] New feature
[ ] Enhancement
[ ] Refactoring
[ ] Dependency updates
[ ] Documentation
[ ] CI/CD

Description

Stores API keys in a vector in MockDB.
Additional Changes

[ ] This PR modifies the API contract
[ ] This PR modifies the database schema
[ ] This PR modifies application configuration/environment variables

Motivation and Context

Resolves #996.
How did you test it?

Wrote a unit test (included in the PR, but ignored). It passes locally if I make some unrelated changes to allow the test to run without needing redis, but I have it ignored for now because of that (the tests can probably be removed too, they arent vital just wanted to verify it worked)
Checklist

[x] I formatted the code cargo +nightly fmt --all
[x] I addressed lints thrown by cargo clippy
[x] I reviewed submitted code
[x] I added unit tests for my changes where possible
[ ] I added a CHANGELOG entry if applicable

@derekleverenz can we have your twitter / LinkedIn handles? Would love to give you a shoutout!

Sure! Im @coaxmetal on twitter and https://www.linkedin.com/in/derek-leverenz-b0787858/ at linkedin

Thanks! Can you please enable tagging on LinkedIn, we are unable to tag your profile

Ah yep, should be enabled now


Boilerplate Enhancement: Crash Reporting

Crash reporting is one of the first things we add to new Ignite projects. It would be great to have a defined place to add this.
My current idea is to add a crash-reporting.ts file to the boilerplate with some comments:
/**
 * This is where you put your crash reporting service initialization code.
 * If you're using Crashlytics: <link to Crashlytics docs>
 * If you're using Sentry: <link to Sentry docs>
 * If you're using Bugsnag: <link to Bugsnag docs>
 */

We could potentially add a generic interface that works with all three of those systems, so it's easier to swap them in and out:
export function reportCrash(error) {
  // Sentry.captureException(error)
  // crashlytics().recordError(error)
  // Bugsnag.notify(error)
}

Open to additional feedback on this. I would recommend putting this file in app/config/crash-reporting.ts

Implemented in #1996
Will be included in Ignite v8: Maverick #1987


Reference position tracking

Note:
This is still in development and needs real-time testing. Posting this PR in case the next student might be interested in using this code.
Main Changes
This PR is about the implementation of a reference position tracker.
It implements;

A QR-Camera based heading and (x, y) coordinate tracker.
A Kalman filter for estimating the (x, y) coordinates along with the corresponding velocities (vx, vy).
An LQR for position reference tracking.

Tests
Only preliminary simulations.

This is based on a very old branch. Try to merge dev into this branch first.

Done! Please have a look.


[RFE] Add support for Azure storage type StandardSSD_LRS

Internal reference: SURE-3116
Reported in 2.5.8
There's a request to add the ability to select storage types when creating or editing node templates for Azure.
Requested choices:
StandardSSD LRS
https://azure.microsoft.com/fr-fr/blog/preview-standard-ssd-disks-for-azure-virtual-machine-workloads/
UltraSSD LRS (this won't be possible yet for reasons listed in the comments)
https://azure.microsoft.com/nl-nl/blog/announcing-the-general-availability-of-azure-ultra-disk-storage/
Actual behavior:
The disk choices aren't available
Expected behavior:
The disk choices should be available
@HarrisonWAffel had mentioned this in the midst of research, though no ticket found in rancher/rancher repo:

Can you confirm if the user is asking us to enhance the list of currently available storage types when creating an Azure VM (typically called an OS disk), or if they are asking us to provide support for creating and managing Data-disks within node templates?

Data-disks are additional storage options that do not contain the OS. I only ask because the UltraSSD LRS option cannot be used as a OS disk for an Azure VM and can only be used as a data-disk. This is detailed in the Azure documentation https://learn.microsoft.com/en-us/azure/virtual-machines/disks-enable-ultra-ssd?tabs=azure-portal#ga-scope-and-limitations. Currently the storage type option within the node template for Azure refers to the OS disk used by the VM. The StandardSSD LRS option can be added to the current node template, but currently there is no way to manage data-disks for Azure VM's from within Rancher. If they are only asking us to expand the option for OS disks then the scope of work is quite small.

Assuming that the user is requesting an enhancement to the current list of Azure VM OS storage disks, I believe that changes would be localized to the Rancher dashboard. I've done my best to determine the required changes and story point estimates, however the UI team should have final say.

Dashboard Changes (0.5 pt, need confirmation with UI team)

The storage types defined in dashboard/shell/machine-config/azure.vue would need to be updated to include a new entry
-- It should be named Standard SSD LRS and have a value of StandardSSD_LRS
The storage type UltraSSD LRS cannot be added to the dashboard for Azure VM OS disks, as Ultra-SSD's can only be used a data-disks. At the moment, Rancher does not provide a means of creating or managing data-disks for Azure VM's. The documentation listing the limitations of Ultra-disks can be found here: https://learn.microsoft.com/en-us/azure/virtual-machines/disks-types#ultra-disk-limitations

(Still need to confirm if the request is for us to "implement support for Azure Data-disk management within Rancher" as that would require changes.)

It looks like most of the Azure related changes are related to node templates, which only apply to RKE1 clusters. Are these options just for RKE1 node templates, or do they also need to be added to the node pool forms for RKE2 provisioning?

While we're waiting for an answer about Ultradisk, I've gone ahead and added StandardSSD as an option:

RKE1: https://github.com/rancher/ui/pull/4905
RKE2/K3s: https://github.com/rancher/dashboard/pull/7254

Since Ultradisk would be more complicated to add, should it be tracked in a separate issue?
Side note: It would also be a little more complicated to add Ultradisk on the UI side due to the fact that Ultradisk is not available in all regions. Ideally, if the user has selected a region where the option is not available, I'd like that option to be disabled with a tooltip saying "Not available in the selected region." (That's not needed for StandardSSD because it's available in all regions.)

@catherineluse I checked with @HarrisonWAffel and it's a 'will not do':

UltraDisks are considered 'data-disks' and right now there isn't a way to manage those in Rancher. The reporters latest comments indicate to me that they aren't asking us to support them so I think that disk type can be disregarded.

This may change down the road, of course, but for now, let's do the minimum and when we get a request, we can file a ticket later to add UltraDisks.

Waiting on https://github.com/rancher/machine/pull/198 to land to make this workable. As noted, Ultradisk won't work so we'll explore a warning in case someone tries to pick it (or we just hide it with an explanation). As to whether future storage types run into this issue, then we may have to look at some other futureproofing.

Backend complete, so they're awaiting UI before handing to QA: https://github.com/rancher/rancher/issues/39672 though they will await for all related Azure AD tickets to be completed before testing begins.

QA Template
What was fixed, or what changes have occurred
Added the StandardSSD_LRS storage option for RKE1 and RKE2/K3s Azure clusters
Areas or cases that should be tested

RKE1 Azure clusters - see screenshot https://github.com/rancher/ui/pull/4905
RKE2/K3s Azure clusters - see screenshot https://github.com/rancher/dashboard/pull/7254

@gaktive @catherineluse , just to clarify something. https://github.com/rancher/dashboard/issues/7177#issuecomment-1317761114 mentions Rancher machine changes are needed for this, but from what I see StorageType was available prior to the change and this issue is about adding an extra option for this field. Correct?

I was able to verify that the node template was created successfully but was not able to test cluster provisioning as I am blocked by 7636 and will validate the cluster provisioning once the issue is fixed.

Moving to QA blocked until blocker is resolved

Test Environment:
Rancher version: v2.7-head a2ef50b
Rancher cluster type: HA
Docker version: 20.10
Downstream cluster type: rke1 & rke2 azure node driver

Testing:
I seem to have found an issue with the StandardSSD_LRS selection for both rke1 and rke2. The rest of the dropdown list omits the SSD part in the name and when I checked the azure site where they list the SkuName, I saw that there did not seem to be an option for Standard_SSD_LRS

When trying to create a cluster using the node template I get the following error for rke1 and rke2
RKE1
Error creating machine: Error in driver during machine creation: storage.AccountsClient#Create: Failure sending request: StatusCode=0 -- Original Error: Code="InvalidAccountType" Message="AccountType StandardSSD_LRS is invalid. For more information, see - https://aka.ms/storageaccountskus":Timeout waiting for ssh key

RKE2
Error creating machine: Error in driver during machine creation:
storage.AccountsClient#Create: Failure sending request: StatusCode=0 --
Original Error: Code="InvalidAccountType" Message="AccountType
StandardSSD_LRS is invalid. For more information, see -
https://aka.ms/storageaccountskus"

Here are the options in the dropdown list for both rke1 and rke2
RKE2

RKE1

@catherineluse could you take a look? thanks!

@thaneunsoo StandardSSD_LRS requires you use a Managed Disk type, in your screenshot it looks like you used unmanaged disks. Though, we should probably have a UI hint as to this requirement, since the error returned from Azure is not very informative.

I created separate PRs that show an error message/UI hint if StandardSSD_LRL is selected without managed disks enabled:

RKE2/K3s: https://github.com/rancher/dashboard/issues/7743
RKE1: https://github.com/rancher/dashboard/issues/7744

I created separate issues linked to each of them so that this one can be closed out.

Closing this issue based on below comments.


Otterize-cli fails to start on mac amd64 (bus error: 10)

Logs:
$ curl -LJO https://get.otterize.com/otterize-cli/v0.1.12/otterize_macOS_x86_64_notarized.zip
$ tar xf otterize_macOS_x86_64_notarized.zip
$ ./otterize
Bus error: 10

Build version: v0.1.12

Solved by https://github.com/otterize/otterize-cli/pull/88