ALL RIGHTS RESERVED © 2019 Measurable AI should be 2020

Do not hardcode 2020. Use javascript to calculate it

Fixed.


Password prompt for public repositories using user/repo and SSH protocol

I always get prompted for my GitHub username and password, even for public repositories. This information is not even used (I can enter in garbage and the clone still works). This only happens when I run hub clone github/hub and not hub clone git@github.com:github/hub.git. Also, this only happens when my global .gitconfig has hub.protocol = ssh.

Hi, sorry I never got back to you on this one.
Hub will try to ask you for username/password once, even for public repositories, because it wants to store an OAuth token and use it whenever it needs to access the API. This is separate of git cloning operation. Before, if you entered gibberish, the clone still proceeded, because it's not strictly necessary for that operation, but later releases fixed this confusion by actually aborting the process if the password is invalid.
Once you authenticate with hub, it saves the token and doesn't ask you again.

This seems to be resolved now with an update to hub, but just to clarify, hub was not saving the token and I was being asked for my password repeatedly.

@michaelmior I'm glad an upgrade solved this for you! If you still have a problem with token not being remembered in your ~/.config/hub file, please reopen this. Thanks!


Missing hyperopt import

I'm getting an import error "cannot import name 'FMIN_CANCELLED_REASON_EARLY_STOPPING' from 'hyperopt.spark'". This occurred through databricks UI and automl api using runtimes 10.3 ML and 10.4 ML.
Any ideas on how to get past this? It seems to happen on import...from databricks.automl.supervised_learner import SupervisedLearner.

Hi @bstuddard. I haven't been able to reproduce your issue. I ran these imports on a 10.4 ML cluster, and they worked fine:
from databricks.automl.supervised_learner import SupervisedLearner
from hyperopt.spark import FMIN_CANCELLED_REASON_EARLY_STOPPING

Could you check if your cluster has the correct version of hyperopt installed?
import hyperopt
hyperopt.__version__

This should return 0.2.7+db1. Perhaps your cluster has some packages installed that changed the version of hyperopt.

Yes, that's the cause. The +db version indicates that the hyperopt package installed on ML Runtime by default contains some features that exist on Databricks, but not in open source hyperopt. FMIN_CANCELLED_REASON_EARLY_STOPPING is an example of that.
This probably happened because hyperopt was reinstalled, or packages that depend on hyperopt were modified. Could you check if there were package modifications, eg. in your notebook using %pip or in the cluster libraries UI? Databricks recommends not modifying python packages on the cluster you use to run automl, per requirements, to avoid this issue.

Yes, that's the cause. The +db version indicates that the hyperopt package installed on ML Runtime by default contains some features that exist on Databricks, but not in open source hyperopt. FMIN_CANCELLED_REASON_EARLY_STOPPING is an example of that.
This probably happened because hyperopt was reinstalled, or packages that depend on hyperopt were modified. Could you check if there were package modifications, eg. in your notebook using %pip or in the cluster libraries UI? Databricks recommends not modifying python packages on the cluster you use to run automl, per requirements, to avoid this issue.

That was it, thanks! I verified on a cluster without any other library dependencies, outside of the runtime pre-installed ones, and was able to get it working.

Glad it's working now! I'll close this ticket.


Additional axes (when opposite joystick button is pressed) get stuck

If handled as follows:

push left button to enable additional axis on right joystick
move right joystick and hold tilted position
release left button

This tilted position will get stuck until next left button press and resetting axis to dead zone.
Solution: when button is released move additional axis to neutral positions

Done through https://github.com/ytmytm/ksp-gegi/commit/de60adbf6b40d9aa9c27e8b634975a1b98cd9e19


Sidebar Icons are stretched, and There is a large strip across the top of the window

Did you read the README?

[ ] I have read the README, the theme is installed/configured correctly and the "Troubleshooting" section contains no information related to my problem

Do you have the latest versions of Spicetify, Spotify and Bloom?

[ ] I'm using the latest versions of Spicetify, Spotify and Bloom

Is there already an issue for your problem?

[ ] I have checked older issues, open and closed

Is your problem definitely caused by the theme?

[X] I have checked the app behavior without the theme and it is different
[ ] I have problem with a theme custom feature

Environment & Computer Info
- Spotify version: <IP_ADDRESS>1.ga588f749
- Installed from: Spotify site
- Spicetify version: 2.20.2
- Color scheme: All
- Extensions: Adblock
- Custom apps: None
- Bloom installation method: Spicetify Marketplace

Description
Sidebar Icons are stretched, and There is a large strip across the top of the window
Screenshots

Duplicate of #280


Why --uno-interface defaulting to --interface value instead of <IP_ADDRESS>

When I run unoserver as:
# unoserver --interface <IP_ADDRESS>
I find the LibreOffice server is waiting for connection at <IP_ADDRESS>:2002.
I understand that the --uno-interface value is used for communication between unoserver and the LibreOffice server, and that both typically run on the same host. In that case, it seems better that the default value of --uno-interface should always be <IP_ADDRESS>, regardless of the value of --interface.

Yeah, that makes sense.

2.0.1 released


Move player selection indication to center of screen

Many players failed to understand that their votes were shown on the right-hand side, so seeing the picks in the middle will help them understand what is happening.

Resolved in #11


Datepicker component no longer editable

Overview of the problem
Oruga latest
Vuejs version: latest
OS/Browser: any
Description
In the vue 2 version of oruga, the o-datepicker component used to have a prop named editable, which as its name suggested, allowed for the inline editing of the date. Now, in the latest version of oruga for vue 3, that prop is gone, and the only prop that resembles that is readonly, which acts as the native readonly attribute.
Steps to reproduce
I created a sandbox reproducing the issue.
Expected behavior
When the date is inline edited, if the text is a valid date, it should be set as the date.
Actual behavior
The date is either not changed or emptied.

A reproducible example:
<script setup lang="ts">
import { ODatepicker } from '@oruga-ui/oruga-next';
import { ref } from 'vue';

const date = ref(new Date());
const range = ref([new Date(), new Date()]);

</script>

<template>
  <OField label="Date">
    <ODatepicker v-model="date" :readonly="false" />
  </OField>
  <OField label="Date Range">
    <ODatepicker v-model="range" :readonly="false" range />
  </OField>
</template>

Trying to edit either date via the keyboard just clears it out once the control loses focus.
I suspect this logic is what's clearing the value.

@blm768 Thanks for the fix, seems good.
@theonelucas editable got renamed to readonly to get it inline with the other input components.
Maybe we should also change the default value of readonly to false instead of true? What do you think?

Maybe we should also change the default value of readonly to false instead of true? What do you think?

That would be closer to the standard behavior of the readonly property, which defaults to false like all HTML Boolean attributes. The readonly property for ODatepicker really doesn't behave like it does for other inputs, though. If I were just looking at the HTML specification rather than the Oruga documentation, I'd expect <ODatepicker readonly> to not allow any kind of user input, not even via the pop-up picker.

Yeah you are right, this is how it should be.


Defining top level properties on mainStep

Fixes #23
Working example
To reproduce
In cdk-ssm-document
npm run package

In your cdk project
pip install cdk-ssm-document/dist/python/cdk-ssm-document-0.0.0.tar.gz

Actual document definition
Document(
            self,
            "SSM-Automation-Document",
            name="Test-Automation-Thing",
            document_type="Automation",
            content=DocumentContent(
                schema_version="0.3",
                description="Does a inplace update or uninstall/reinstall of a thing",
                parameters={
                    "InstallType": DocumentParameter(
                        default="In-place update",
                        description="(Optional) Determines the way you want to install this package. Default is to add new or do an inplace update.",
                        type="String",
                        allowed_values=["In-place update", "Uninstall and reinstall"],
                    ),
                    "AutomationAssumeRole": DocumentParameter(
                        default="",
                        description="(Optional) The ARN of the role to run Automations on your behalf.",
                        type="String",
                    ),
                    "InstanceId": DocumentParameter(
                        description="InstanceId to run the Automation", type="String"
                    ),
                },
                main_steps=[
                    DocumentMainStep(
                        name="getEc2State",
                        max_attempts=2,
                        action="aws:executeAwsApi",
                        on_failure="Abort",
                        inputs={
                            "Service": "ec2",
                            "Api": "DescribeInstances",
                            "InstanceIds": ["{{InstanceId}}"],
                        },
                        outputs=[
                            {
                                "Name": "state",
                                "Selector": "$.Reservations[0].Instances[0].State.Name",
                                "Type": "String",
                            }
                        ],
                    )
                ],
            ),
       )

@udondan if you have any time to take a look at this and give your thoughts on it I'd be greatful. Would love to merge it and switch pip from from using my local directory 😁
I also see nuget was commented out in the ci file. Idk if this was part of the issue with it or not but the underlying issue effects more than just python.

@udondan Merge conflicts all cleaned up and ready for review

Sorry for ignoring you for so long @zendern. Life is just crazy...
I hope you're as happy as me, to hear this construct is no longer required. Starting with CDK 2.29.0 updates are supported by the CfnDocument construct. 🥳


Allow to override runtime through command line

Allow to override runtime through command line for projects which are developed for some runtime but can be easily built for another. E.g. between node.js, NW.js and electron.

pr merged


Fix idempotence issues creating tables and users

The mon.sql file was causing ansible-playbook to fail if run
on subsequent occasions, as it would error out trying to re-create
existing tables and users.  This change tweaks mon.sql to work
with new and existing Monasca MySQL databases.

Looks like you took out the user creation. How are they now being created?

The GRANT ... IDENTIFIED BY ... statement will create users if they do not already exist (which is the default behavior).
I tested this change out both ways, on new installations and on existing ones.

Looks good to me

I'm not convinced that skipping table creation if the table exists is the right behavior. The script is only run when it changes and then it will fail. Since we haven't yet implemented a way to update the schema this failure is an indication that something changed. With the change to skipping it will get past this and then the app could fail in some odd way as the schema does not match what is expected.
If the db already exists when you run ansible then you should just skip this part of the role.
That is nice that the grant will create the user, I like that change.

Currently the only way I know that the schema is changed when I upgrade Monasca is that the schema upgrade portion fails. I then manually remove the mon database (2-step process) and rerun the upgrade. This ensures that the latest schema is installed after the upgrade completes and there will be no test failures related to the schema change. If this step is ignored, then I echo what Tim says about possible random failures due to an old schema being used. In theory the schema updates should only be occurring while Monasca is under development, and stable after it is deployed ? The most valuable thing would be to have an automatic way for the schema to be updated during the upgrade.

I added a pull request to revert the table changes, we can continue the conversation there
https://github.com/hpcloud-mon/ansible-monasca-schema/pull/9


Add command to list all reactions on a message

Also does some refactoring for message commands by adding a MessageConv discord object converter.

Thanks @Ma-wa-re


Elevator state is not being publish on the ground floor

Environment

OS Version: Ubuntu Jammy
Source and Binary

Description

Expected behavior: The elevator should publish a message to it's state topic on each floor it is in.
Actual behavior: The elevator publish a message for all floors except the ground floor.

Steps to reproduce

Run the elevator.sdf file:

gz sim elevator.sdf

Subscribe to the elevator state:

gz topic -e -t /model/elevator/state

Publish a floor for the elevator to go. Example:

gz topic -t "/model/elevator/cmd" -m gz.msgs.Int32 -p "data: 2"

Output
We get the expected behavior when we send the elevator to any of the upper floors:

However, when we send the elevator to the ground floor (gz topic -t "/model/elevator/cmd" -m gz.msgs.Int32 -p "data: 0"), we stop receiving information on the console:

Interesting. I don't think it is critical to be able to echo it as long as the we still get the correct value on the subscription. My only concern is that it may confuse users that are not aware of that specific behavior. Maybe we could add a little comment at the top of the .sdf file? I can go ahead and create the appropriate PR if you agree on the "solution".

I think a comment would be helpful.
Or we can 1-index all of our arrays from now on. :wink:

I agree, let's go with the comment for now and keep it in mind from now on.


Map.get_Envelope() throws a NullReferenceException when an empty Linestring is added to a WritableLayer

When I add an empty Linsestring to a WritableLayer and then click on the map a NullReferenceException is thrown at Mapsui.Map.get_Envelope(), because the envelope of the Linestring is null. I think this needs a fix.

Thanks, I will add a unit test for it and fix it.

Fixed.


No access to NAS / USB since Android TV 11

Can't access the files on NAS of USB anymore since the Nvidia Shield updated to Android TV 11 even after de 9.0+ hotfix. Nvidia says that apps that can't acces the files anymore need to update the app.
Can you update it?

Please try updating to v0.90 (hopefully also available in the testing channel on Google Play shortly).

You might also try uninstalling and then installing the app again.

Thanks for your fast respons. I will delete it and install the new version v0.90 now and give you the feedback

Hey Moneytoo, I have installed version v0.90 and there is indeed an improvement thanks! I see all the USB and NAS drives again. The only problem is Just Player doesn't see any files in the folder. No video files and after long press also no subtitles. I hope you can fix this because I like your player very much and gives clean and msooth playback.

I'm afraid that I don't really know what's going on as (legacy) file access (for multimedia) works in Android TV 11 emulators as well as other devices. Are all other apps and video players able to access your files?
I believe I read that Nvidia will allow using the newer API (Storage Access Framework) on Shield with Android 11 which should make it on par with phones. So here I have a version which uses the newer system file chooser: Just.Player.v0.90-saf.apk. However I already received a feedback that while the chooser shows files, it cannot be controlled properly using directional pad.

Hey Moneytoo, It depends strongly on the app.
Works in: Kodi, File manager, X-plorer
Doesnt work (anymore) in: Just Player, Vimu (does when connected to nas in app instead of mount in in Android TV)

The workaround is to open it in File manager and then open file and choose just player as player. But this is not very consumer friendly and it is not possible to sideload subtitle (only embedded)

I'm afraid that I don't really know what's going on as (legacy) file access (for multimedia) works in Android TV 11 emulators as well as other devices. Are all other apps and video players able to access your files?
I believe I read that Nvidia will allow using the newer API (Storage Access Framework) on Shield with Android 11 which should make it on par with phones. So here I have a version which uses the newer system file chooser: Just.Player.v0.90-saf.apk. However I already received a feedback that while the chooser shows files, it cannot be controlled properly using directional pad.

Hey Moneytoo, Thanks for this latest version. Indeed the d-pad function does not work properly, but....... I found a work around for now. The Nvidia Shield has an telephone app and there you can control the shield with. Now in this app you can change between d-pad and trackpad. This gives you a cursor and now and can go to my nas en play the video files including loading an external subtitle. I hope you can make it compatible with the D-pad to make it more client friendly. Thanks for now and hope to see the updates coming.
This is by far the best player for me with large files. No stutters en very smooth picture quality!

Reading through https://www.nvidia.com/en-us/geforce/forums/shield-tv/9/481674/android-11-application-issues/ there are reports of issues even with apps like MX Player, VLC etc.
Could you try enabling media scanning as mentioned in the FAQ for Nova Video Player? Just Player works differently but you may give it a shot.
Maybe you could try installing this version: Just.Player.v0.91-legacy.apk to verify some of my theories... Does this one work?
How about even other players? mpv, Fermata...?
Thank you for all the feedback.

Maybe you could try installing this version: Just.Player.v0.91-legacy.apk to verify some of my theories... Does this one work?
He Moneytoo,
OMG you are the man!!! I installed this version and it works perfectly and just how it just to be.
Thank you for all the hard work!

Unfortunately, the legacy version is only a work around and such version cannot be distributed through Google Play.
It would be still useful if you could verify if media scanning option has anything to do with the visibility of files (per my previous comment).
Could you verify if any of these apps (updated after November 2021) works (list files)? VLC, Fermata Media Player, X-plore File Manager, Solid Explorer File Manager, Amaze File Manager, MiXplorer Silver?

Hey Moneytoo,
That's unfortunately. I just tested the media scanning option and turned it on. For now I don't see any difference in the apps that cannot acces the files (X-plorer file does work also without scanning). The most apps see the drives but not the files. Also the name in these apps starts with USB instead of the network (NAS) name since android tv 11. Maybe scanning takes time to fill up the database. So I will also check later on and let you know.

Ok I checked Nova Player and indeed in this app it works. When opening the app you will see a circle running in the top right corner and the files become visible. Others app who lack this feature there is still no difference. Hope this helps you.

What version of Nova Video Player are you using? The latest stable version from Google Play (v5.x?)? This version still targets older Android version so it works just like the -legacy version of Just Player. Latest version of Nova Video Player (v6.x) has similar issues.
Anyway, when you're talking about no access to files, is this only about external storages like NAS/USB or also the internal storage? Can you access video files that are stored directly on your device?

Hey Moneytoo, Its both External and Internal. So if i only see the folders and not the files in a certain app thats applies for both. I indeed use the play store version (latest) of Nova Player. Haven't tested the v6. version,

One more thought... In what directory path are your videos located? Could you try copying any video to the topmost \Movies folder and see if it's visible in there?

I copied a movie to the /movies folder and indeed VLC player (for example) does see the movie and can play it. When seaching on the NAS the folders are empty (The files do appear when manually searched through network in-app)

How about Just Player? Does moving videos to the Movies folder help make it visible to its file chooser (the stable version on Google Play)?

I will test it for you and give feedback.

How about Just Player? Does moving videos to the Movies folder help make it visible to its file chooser (the stable version on Google Play)?

I tested it with the stable (google play store 0.88v) version and indeed it sees the movie file in the internal movies folder and is playable. External is not visible.

Thank you a lot for all the tests.
I still planning on testing/confirming some cases myself later on but so far my best solution is to change the file chooser on Android TV 11 to using MediaStore and keep it optionally configurable.
Current WIP version is here: Just.Player.v0.92-mediastore.apk In advances settings (long tap the ⚙ gear to access it), you can change File access mode from Auto to:

Storage Access Framework - Native system file chooser with access to all files, used on phones but usually not available on TVs. It's available on Nvidia Shield but has problems with d-pad controls.
MediaStore - Lists files indexed by system media scanner. See this FAQ as indexing needs to be enabled for external storages.
Legacy - The old way of accessing storage, which is now problematic on Android TV 11

Your welcome was glad to help you with testing and thanks for the fast responses. Good luck with testing yourself en we see the updates coming. It's a great app!

0.92:

legacy; I can properly see my network shares, but can't see files
storage access framework; works a treat, as long as I use the Nvidia remote on my phone with trackpad indeed
mediastore/auto; I just see "Choose a file", but nothing else, empty list.

legacy; I can properly see my network shares, but can't see files

Yep, this is expected, only the special version has unrestricted access.

mediastore/auto; I just see "Choose a file", but nothing else, empty list. Media scanning is enabled in Android settings.

Have you tried rebooting? Maybe you could try the latest version of Nova Video Player. According to https://github.com/nova-video-player/aos-AVP/issues/539 enabling of scanning should resolve that.

So the Shield has a feature that allows you to mount your NAS or network shares to the Shield itself. This allows your network files to appear as local files to apps that do not have a built in smb setting. The scan for media option only seems to work for physically connected usb drives. Using Mediastore option in v92 only shows media from physically connected drives (not mounted storage) but it displays it all generically listed in alphabetical order, so basically it is a total mess. The v91 legacy allows access to mounted storage and is still organized as folders/files. Mediastore is simply not good for the Shield.

@Poker354
The look of MediaStore chooser is in my control and can be improved. I will try adding adding volume names and also handle startig/last used file. Multi level browsing structure could be probably possible as well.
The fact that mounted network volumes are not indexed is quite interesting. This means that only apps with the MANAGE_EXTERNAL_STORAGE can access it. Normally, this permission is only granted to apps like file managers, however large apps like VLC and MX Player managed to get an exception. Given that this (network volume mounts) feature is not a native Android feature, I worry that Google may not permit the use of this permission for Just Player, especially considering Nova Video Player was denied in the past. But I guess I could try...

So, does this version: Just.Player.v0.93-manage_external_storage.apk work / is able to access all mounts after manually granting the highest permission (see Nvidia KB)?

Yes. I have tested v93. I needed to completely uninstall Just Player and reinstall v93 to get it to work. I double checked app permissions and this time it was set to not allow. I changed it to always allow. The first time a tried Storage Access Framework an additional pop up asked for permission to access files. Both Storage Access Framework and Legacy are now working for Folder/Files. MediaStore still only shows USB connected and internal storage but it is unusable anyway do to it’s organization of the files.

Thanks @Poker354. I have just submitted a version using this permission for review to Google and I stated access to these network shares configured using 1st party (Nvidia) tool (in more details) as a reason. 🤞 But I wouldn't get my hopes too high. While VLC and MX Player managed to get access to this permission, others such as Nova Video Player or TiviMate failed.

Even if the permission won't be granted, I understand the the biggest trouble when using 3rd party file managers to browse and open videos is to load subtitle files as well. I guess I could register Just Player to handle subtitle files and append the subtitles selected from the file browser to the currently opened video. This should workaround the biggest annoyance IMHO.

Requested...

... and rejected:

Violation     All files access permission: Not a core feature
Details     The feature that you identified that is dependent on this permission does not appear to be critical to the core functionality of your app.

Violation     All files access permission: Need to use MediaStore API
Details     You have requested access to 'All files access' permission but it appears that your app’s core feature requires access to only media files.

Both Storage Access Framework and Legacy are now working for Folder/Files.

@Poker354 But as others mentioned, the (Android native) Storage Access Framework file chooser cannot be controlled fully/properly using only the Shield standalone remote, right?

On v93 test app the Storage Access Frame work functioned and looked identical to legacy, it did not bring up the GUI as in other versions. In apps/permissions there were 3 options with v93: do not allow, allow while using app and always allow. In other versions there are only 2 options, do not allow and allow while using the app. In V93 legacy and Storage Access Framework worked (but storage access frame work was the same as legacy).
Since Google rejected your request can you not continue with a Play Store version and a sideload version posted here of GitHub?

On v93 test app the Storage Access Frame work functioned and looked identical to legacy, it did not bring up the GUI as in other versions.

That was a bug it that test version, sorry for that. SAF should always bring up the full screen system file chooser.

Since Google rejected your request can you not continue with a Play Store version and a sideload version posted here of GitHub?

I can only not use the (MANAGE_EXTERNAL_STORAGE) permission which means that the Legacy file access in the version distributed through Google Play won't be able to fully access external storage volumes. I will continue providing the fully functional -legacy version for sideload here on GitHub.
I plan on checking for libraries providing some auto updating mechanism for this version. Right now I'm working on loading subtitle files from file managers.

Thanks and great work!

Thanks for your swift updates and hard work.

App updates on Google Play are still stuck in review (for 3 days).
As listed in the changelog of v0.95 (beta), it should be now possible to open subtitle files from external file managers - as the subtitle will be attached to currently opened video in Just Player. This is an alternative/backup way to access your files.

Unlike Just Player (and Nova Video Player or Tivimate), other video player apps like VLC, MX Player or Vimu all managed to get the MANAGE_EXTERNAL_STORAGE permission approved from Google.
As @courville already pointed out (after seeing my rant), at least in the case of VLC, it's because of support for exotic video formats not indexed by media scanner.

@moneytoo v93 actually was working with my Nvidia Shield Pro + Android 11 update stock FW + external HDD. Was even using JP last night.
However the app updated this morning to v97 from the play store, even though i've sideloaded v93. This has broken the ex HDD access again on the Shield.

@f0x135 Use the -legacy version from https://github.com/moneytoo/Player/releases

I'm assuming that all the 'official' versions will be like this until Google allows 'Manage External Storage'?

Google already denied my request so it will continue to work pretty much the same like right now.
If you want to use the Google Play version, enable media scanning for external devices.

Regarding shield update and USB storage, I had the same issue with my player https://github.com/nova-video-player/aos-AVP/issues/539 and it turns out that it was a problem with the nvidia shield that do not index usb drive by default anymore...
You can turn it back on in nvidia settings.

On latest version of the OS, Nvidia shield disables external storage Android indexing for performance enhancements. In order to get back external storage video files visibility, you need to enter Android settings/Device Preferences/Storage and enable Scan for media automatically option.
Alternatively you can expose in the same setting the local USB drive via SMB (Mount network storage option) and then use Nova SMB network shares indexing.

@f0x135 Use the -legacy version from https://github.com/moneytoo/Player/releases

I'm assuming that all the 'official' versions will be like this until Google allows 'Manage External Storage'?

Google already denied my request so it will continue to work pretty much the same like right now.
If you want to use the Google Play version, enable media scanning for external devices.

@moneytoo the legacy verions work when using the stand alone app but i actually coded Kodi to externally pass Dolby Vision media to JP, and for some reason none of the legacy versions are working with it.

you need to enter Android settings/Device Preferences/Storage and enable Scan for media automatically option.

@courville i do have that checked but the PLay store version of v97 still couldn;t acccess the files. Maybe with the 3 hotfixes Nvidia has released, but so far my Shield was all fine with stock FW for everything until JP got updated to v97.

Nvidia released Shield Experience Upgrade 9.0.1 and mentions:

Fixes storage permission issues on media players, file browsers, and emulator apps
Resolves navigation issues when selecting folders to grant files and media permissions

Any changes in the access to external storage volumes using the legacy file access mode in the Google Play version of Just Player?
How about Storage Access Framework? Does it mean that the system file picker UI can be controlled using d-pad of a physical remote?

Sorry but what's the "legacy file access mode" in the Google Play version of Just Player?
And sadly no, nothing has changed with the Google Play version after the latest 9.0.1 upgrade, still can't read my files/folders  inside the USB drive.

No change. Legacy setting can see folders but not the files within.
No change either. Navigation is improper, and files/folders are not properly highlighted when navigating.

@moneytoo no more update on this issue? :(

I'm going to close this as I don't think there's anything more to do with this. I will continue publishing the -legacy version which remains the only solution for some use cases.


False positive: "integer overflow"

I'm getting an 'integer overflow' from a few contracts scans with mythril. The warning also shows up on the OpenZeppelin ERC-20 standard token implementation.
Another e.g scanning this contract shows an int overflow
https://etherscan.io/token/0x58b6a8a3302369daec383334672404ee733ab239
==== Integer Overflow ====
Type: Warning
Contract: 0x58b6a8a3302369daec383334672404ee733ab239
Function name: _function_0xd73dd623
PC address: 3368
A possible integer overflow exists in the function _function_0xd73dd623.
The addition or multiplication may result in a value higher than the maximum representable integer.

Hi @ksloven,
Thanks for the report! We're aware of this particular issue: The add function in SafeMath.sol contains an integer overflow but rolls back the transaction after the overflow. It's explained in my recent article.
We're working on ways of eliminating this, but it still needs some experimentation.
@JoranHonig, FYI here is the output for the OpenZeppelin ERC20 token:
$ myth -x contracts/token/ERC20/StandardToken.sol
==== Exception state ====
Type: Informational
Contract: StandardToken
Function name: increaseApproval(address,uint256)
PC address: 4018
A reachable exception (opcode 0xfe) has been detected. This can be caused by type errors, division by zero, out-of-bounds array access, or assert violations. This is acceptable in most situations. Note however that `assert()` should only be used to check invariants. Use `require()` for regular input checking.
--------------------
In file: contracts/math/SafeMath.sol:45

assert(c >= a)

--------------------

==== Integer Overflow  ====
Type: Warning
Contract: StandardToken
Function name: increaseApproval(address,uint256)
PC address: 4005
A possible integer overflow exists in the function `increaseApproval(address,uint256)`.
The addition or multiplication may result in a value higher than the maximum representable integer.
--------------------
In file: contracts/math/SafeMath.sol:44

a + b

--------------------

Should be fixed in #184

This can be closed now

I found the problem, a LOG2 instruction is not handled correctly by the TaintRunner

Should be fixed with: https://github.com/b-mueller/laser-ethereum/pull/22#partial-pull-merging

Hi, maybe i'm doing something wrong but I installed mythril on iMac.

KLMs-iMac:~ KLM$ pip show laser-ethereum
Name: laser-ethereum
Version: 0.17.5
Summary: Symbolic Ethereum virtual machine
Home-page: UNKNOWN
Author: Bernhard Mueller
Author-email<EMAIL_ADDRESS>License: MIT

Running it against the contract above doesn't even show the other informational bugs.
Running it against the "batchOverflow" bug, as per the post herehttps://media.consensys.net/detecting-batchoverflow-and-similar-flaws-in-ethereum-smart-contracts-93cf5a5aaac8) yeilds the following:
KLMs-iMac:~ KLM$ myth -xia 0xC5d105E63711398aF9bbff092d4B6769C82F793D -v1
INFO:root:Using INFURA for RPC queries
INFO:root:LASER EVM initialized with dynamic loader: None
INFO:root:- Entering function 0xC5d105E63711398aF9bbff092d4B6769C82F793D:_function_0x06fdde03
INFO:root:- Entering function 0xC5d105E63711398aF9bbff092d4B6769C82F793D:_function_0x095ea7b3
INFO:root:- Entering function 0xC5d105E63711398aF9bbff092d4B6769C82F793D:_function_0x18160ddd
INFO:root:- Entering function 0xC5d105E63711398aF9bbff092d4B6769C82F793D:_function_0x23b872dd
INFO:root:- Entering function 0xC5d105E63711398aF9bbff092d4B6769C82F793D:_function_0x313ce567
INFO:root:- Entering function 0xC5d105E63711398aF9bbff092d4B6769C82F793D:_function_0x3f4ba83a
INFO:root:- Entering function 0xC5d105E63711398aF9bbff092d4B6769C82F793D:_function_0x54fd4d50
INFO:root:- Entering function 0xC5d105E63711398aF9bbff092d4B6769C82F793D:_function_0x5c975abb
INFO:root:- Entering function 0xC5d105E63711398aF9bbff092d4B6769C82F793D:_function_0x70a08231
INFO:root:- Entering function 0xC5d105E63711398aF9bbff092d4B6769C82F793D:_function_0x83f12fec
INFO:root:- Entering function 0xC5d105E63711398aF9bbff092d4B6769C82F793D:_function_0x8456cb59
INFO:root:- Entering function 0xC5d105E63711398aF9bbff092d4B6769C82F793D:_function_0x8da5cb5b
INFO:root:- Entering function 0xC5d105E63711398aF9bbff092d4B6769C82F793D:_function_0x95d89b41
INFO:root:- Entering function 0xC5d105E63711398aF9bbff092d4B6769C82F793D:_function_0xa9059cbb
INFO:root:- Entering function 0xC5d105E63711398aF9bbff092d4B6769C82F793D:_function_0xdd62ed3e
INFO:root:- Entering function 0xC5d105E63711398aF9bbff092d4B6769C82F793D:_function_0xf2fde38b
INFO:root:Execution complete
INFO:root:889 nodes, 888 edges, 15906 total states
INFO:root:Starting analysis
INFO:root:Executing <module 'delegatecall' from '/usr/local/lib/python3.6/site-packages/mythril/analysis/modules/delegatecall.py'>
INFO:root:Executing <module 'dependence_on_predictable_vars' from '/usr/local/lib/python3.6/site-packages/mythril/analysis/modules/dependence_on_predictable_vars.py'>
INFO:root:Executing <module 'depreciated_ops' from '/usr/local/lib/python3.6/site-packages/mythril/analysis/modules/depreciated_ops.py'>
INFO:root:Executing <module 'ether_send' from '/usr/local/lib/python3.6/site-packages/mythril/analysis/modules/ether_send.py'>
INFO:root:Executing <module 'exceptions' from '/usr/local/lib/python3.6/site-packages/mythril/analysis/modules/exceptions.py'>
INFO:root:Executing <module 'external_calls' from '/usr/local/lib/python3.6/site-packages/mythril/analysis/modules/external_calls.py'>
INFO:root:Executing <module 'integer' from '/usr/local/lib/python3.6/site-packages/mythril/analysis/modules/integer.py'>
INFO:root:Executing <module 'suicide' from '/usr/local/lib/python3.6/site-packages/mythril/analysis/modules/suicide.py'>
INFO:root:Executing <module 'transaction_order_independence' from '/usr/local/lib/python3.6/site-packages/mythril/analysis/modules/transaction_order_independence.py'>
INFO:root:Executing <module 'unchecked_retval' from '/usr/local/lib/python3.6/site-packages/mythril/analysis/modules/unchecked_retval.py'>
The analysis was completed successfully. No issues were detected.

I'm getting the same result with 0.17.5.
@JoranHonig, we should add those integer overflows to our test suite and make sure that they are still detected after adding fp detection code.

we should add those integer overflows to our test suite

...not the complete batchOverflow contract though, that takes very long to analyze!

What's interesting: When I analyze BECToken.sol from source, the integer overflow is detected successfully.
$ myth -x BECToken.sol:BecToken
==== Exception state ====
Type: Informational
Contract: BecToken
Function name: transfer(address,uint256)
PC address: 5260
A reachable exception (opcode 0xfe) has been detected. This can be caused by type errors, division by zero, out-of-bounds array access, or assert violations. This is acceptable in most situations. Note however that `assert()` should only be used to check invariants. Use `require()` for regular input checking.
--------------------
In file: BECToken.sol:28

assert(c >= a)

--------------------

==== Integer Overflow  ====
Type: Warning
Contract: BecToken
Function name: transfer(address,uint256)
PC address: 5247
A possible integer overflow exists in the function `transfer(address,uint256)`.
The addition or multiplication may result in a value higher than the maximum representable integer.
--------------------
In file: BECToken.sol:27

a + b

--------------------

==== Integer Overflow  ====
Type: Warning
Contract: BecToken
Function name: batchTransfer(address[],uint256)
PC address: 2460
A possible integer overflow exists in the function `batchTransfer(address[],uint256)`.
The addition or multiplication may result in a value higher than the maximum representable integer.
--------------------
In file: BECToken.sol:257

uint256(cnt) * _value

--------------------

So maybe the integer overflow module isn't the cause of the false negative?

I concur the local scan does detect the int overflow. so maybe the flaw lies elsewhere

@b-mueller I checked the BECToken contract before creating the pr. But we could try to get more overflow cases in the test suite

Maybe the contract at the address is different due to solidity

According to Etherscan, compiler version is solc v0.4.19+commit.c4cbbb05

I'm currently running analysis with several older versions to find which change caused the problem

At 8605d252797bcd582881edca0f1f887443d4bd47 shows the vulnerabilities.
At 37ed299f2295c4284c5005574ed68e5b78202388(newer) we dont see the vulnerabilities.
The only change here is the following:
To:
    if type(op0) is not int:
        op0_value = int(str(model.eval(op0, model_completion=True)))
        model0 = _try_constraints(node.constraints, [op0 != op0_value])

    if type(op1) is not int:
        op1_value = int(str(model.eval(op1, model_completion=True)))
        model1 = _try_constraints(node.constraints, [ op1 != op1_value])

From:
    if type(op0) is not int:
        op0_value = int(str(model.eval(op0, model_completion=True)))
        model0 = _try_constraints(node.constraints, [constraint, op0 != op0_value])

    if type(op1) is not int:
        op1_value = int(str(model.eval(op1, model_completion=True)))
        model1 = _try_constraints(node.constraints, [constrant, op1 != op1_value])

Applying the change to:8605d252797bcd582881edca0f1f887443d4bd47, does not change its output.
Therefore I believe that indeed the integer module is not the problem here

@b-mueller I think this last problem, where contracts from the network are somehow not correctly analysed belongs in a separate issue.
Also, once https://github.com/b-mueller/laser-ethereum/pull/22 is merged. This pr should be closed.

quick question @JoranHonig @b-mueller , initially we opened this issue for the int overflow false positive when running the scan on-chain, correct? But it appears that the false positive int overflow is not detected when running the scan on-chain. Does the fix (https://github.com/ConsenSys/mythril/pull/184) also address the issue of an assert that reverts the int overflow when it occurs as per the post (https://media.consensys.net/detecting-batchoverflow-and-similar-flaws-in-ethereum-smart-contracts-93cf5a5aaac8); specifically

function add(uint256 a, uint256 b) internal pure returns (uint256) {
uint256 c = a + b;
assert(c >= a);
return c;
}

@ksloven, the pr is merged so you can try it ;). But yes the overflow for a + b is not showed anymore


Unknown warning on Java 10

import io.restassured.RestAssured;

public static main(String[] org) {
	public static void main(String[] org) {
	}
}

after running the above set with eclipse which includes the lib from restAssured, the result below will show up and still can't find the reason. Is there anyone able to resolve it?

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.codehaus.groovy.reflection.CachedClass (file:/Users/dampion/Tools/java-rest-assured/rest-assured-3/rest-assured-3.1.0-deps/groovy-2.4.12.jar) to method java.lang.Object.finalize()
WARNING: Please consider reporting this to the maintainers of org.codehaus.groovy.reflection.CachedClass
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

Same error on Java 9.

Could this be due to the groovy version used? Could you try excluding groovy from rest-assured (see faq) and update to a newer version of groovy to see if it goes away?

@johanhaleby I upgraded the version of groovy I'm using locally from 2.4.12 (the version rest-assured depends on) to version 2.5.1 (the latest stable release of Groovy-all).
Here's my dependency tree showing the 2.4.12 getting overridden by the 2.5.1 dependency.
+--- io.rest-assured:rest-assured:3.1.0
|    +--- org.codehaus.groovy:groovy-xml:2.4.12 -> 2.5.1
|    |    \--- org.codehaus.groovy:groovy:2.5.1
|    +--- org.apache.httpcomponents:httpclient:4.5.3
|    |    +--- org.apache.httpcomponents:httpcore:4.4.6
|    |    \--- commons-codec:commons-codec:1.9 -> 1.11
|    +--- org.apache.httpcomponents:httpmime:4.5.1
|    |    \--- org.apache.httpcomponents:httpclient:4.5.1 -> 4.5.3 (*)
|    +--- org.hamcrest:hamcrest-core:1.3
|    +--- org.hamcrest:hamcrest-library:1.3 (*)
|    +--- org.ccil.cowan.tagsoup:tagsoup:1.2.1
|    +--- io.rest-assured:json-path:3.1.0
|    |    +--- org.codehaus.groovy:groovy-json:2.4.12 -> 2.5.1
|    |    |    \--- org.codehaus.groovy:groovy:2.5.1
|    |    \--- io.rest-assured:rest-assured-common:3.1.0
|    |         \--- org.apache.commons:commons-lang3:3.4
|    \--- io.rest-assured:xml-path:3.1.0
|         +--- org.codehaus.groovy:groovy-xml:2.4.12 -> 2.5.1 (*)
|         +--- io.rest-assured:rest-assured-common:3.1.0 (*)
|         +--- org.apache.commons:commons-lang3:3.4
|         +--- org.ccil.cowan.tagsoup:tagsoup:1.2.1
|         \--- javax.xml.bind:jaxb-api:2.2.12
\--- org.codehaus.groovy:groovy-all:2.5.1
     +--- org.codehaus.groovy:groovy:2.5.1
     +--- org.codehaus.groovy:groovy-ant:2.5.1
     |    +--- org.codehaus.groovy:groovy:2.5.1
     |    +--- org.apache.ant:ant:1.9.9
     |    |    \--- org.apache.ant:ant-launcher:1.9.9

Still getting the same problem though.
I've spent all of 10 minutes looking into this, but I think this may be code inside of rest-assured that needs to be changed.
Here's another project that had the same issue. There's also a commit there showing how they fixed it.
https://github.com/jqno/equalsverifier/issues/183

Multiple Groovy issues (e.g. mentioned GROOVY-8339 and GROOVY-9070 or GROOVY-8843 are already CLOSED. Do you have any update from REST Assured point of view?

Two of these are marked as fixed in Groovy 3.0 alpha/beta
I don't expect REST assured will do anything until Groovy 3.0 has an
official release.
On Fri, Jul 12, 2019 at 3:57 AM Lubomir Elko<EMAIL_ADDRESS>wrote:

Multiple Groovy issues (e.g. mentioned GROOVY-8339
https://issues.apache.org/jira/browse/GROOVY-8339 and GROOVY-9070
https://issues.apache.org/jira/browse/GROOVY-9070 or GROOVY-8843
https://issues.apache.org/jira/browse/GROOVY-8843 are already CLOSED.
Do you have any update from REST Assured point of view?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/rest-assured/rest-assured/issues/1027?email_source=notifications&email_token=AAWEVVHP7MO2S5VEW47JBH3P7A2M5A5CNFSM4FEQVIQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZZANIQ#issuecomment-510789282,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAWEVVGDHS7EEIP7FVPBJXDP7A2M5ANCNFSM4FEQVIQA
.

I get this warning on Java 11. Using rest-assured 4.2.0 with dependency to groovy 2.5.9. Groovy 3.0.0 is available since feb. Will rest-assured be updated shortly?

For people who searching for an answer. Start from version 4.3.0 RestAssured have upgraded from groovy 2.5.7 to 3.0.*
It fixes that annoying warning when you're running your app on jvm11 or above

@zhe-zhao I still get the warning using Java 11 and rest-assured 4.4.0, which uses groovy 3.0.8.
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.codehaus.groovy.vmplugin.v9.Java9 (file:/home/sasu/.m2/repository/org/codehaus/groovy/groovy/3.0.8/groovy-3.0.8.jar) to constructor java.lang.AssertionError(java.lang.String)
WARNING: Please consider reporting this to the maintainers of org.codehaus.groovy.vmplugin.v9.Java9
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release


Add quote service to demo charts

The new PHP quote service is missing from the demo charts.

I can't assign myself but I'm working on this.


Question confusion

What are we supposed to do to address the task (Write a function that calculates the actual frequency in useful units)? Any help will be appreciated.

Did you get your answer? If so, can you please explain it to me?

Tell me if you figured it out

We wrote a function. Check out fft.py on our main repo.


Why is RoomObjectProperties trait unsafe?

This one has been puzzling me for the last few days.
This trait is marked unsafe, yet I cannot find why.
pub unsafe trait RoomObjectProperties:
    AsRef<Reference> + Into<Reference> + HasPosition
{
    fn try_from(obj: RoomObject) -> Option<Self>;

    fn room(&self) -> Room {
        js_unwrap!(@{self.as_ref()}.room)
    }
}

None of the supertrait are unsafe, try_from seems memory safe and I don't see anymore problems here with js_unwrap!() than anywhere else in the package. So, I'm stumped.
I removed all the unsafe from objects/mod.rs and the compiler didn't complain. Am I too naive to believe this somehow validates my point?
Assuming I'm wrong, can we document what are the safety assumptions that are made?

The other option might be to explicitely deal with Results everywhere. Thing is, it would get heavy.

Yeah- I mean we could use Result for all these operations we expect to succeed, but it really would be bad style. If someone implements RoomObjectProperties for something it shouldn't be implemented for, I'd count that as a program logic error, and that's what panics are for.


Support new API changes

There have been a number of API changes to support buckets. you can refer to this PR: https://github.com/waifuvault/waifuVault-node-api/pull/15
Buckets are temprry virtual buckets that are managed with a single token
here are the outline of the changes:

uploadFile now takes an optinal path paramater that is a token. when supplied. it will call /uploadFile/{token} this is the bucket token
the file info and upload response now returns a bucket prop that is nullable. if the file belongs to a bucket, the bucket token will be there
createBucket endpoint that is a GET and takes no body (buckets are created once per IP). the endpoint is /rest/bucket/createBucket
deleteBucket endpoint a DELETE takes the bucxket token as a path param. the endpoint is /rest/bucket/${bucketToken}
getBucket endpoint, a POST that takes the the body of:

{
   "bucket_token": "bucketToken"
}

the response of the get is an object with the shape of
"token": "string",
"files": FileResponseObject[]

where FileResponseObject is whatever type you have defined in the response of getFileInfo.

you can see the new api docs and the schemeas here: https://waifuvault.moe/api-docs


License?

Where does this project stand in terms of licensing?
As per xdrop/fuzzywuzzy#35, xdrop/fuzzywuzzy#84, and xdrop/fuzzywuzzy#78, the parent project is currently licensed under GPLv2.0.
Because of this, this repo should be under GPL as well, no?
Whereas, this repo is under the Apache-2.0 license.
I'd love to use this in my project (solo-studios/PolyBot), but it is (currently) under MIT and I don't wish to step on any licenses' toes. Especially the GPL, since it's very invasive.

Yeah? Is it really a fork or a complete rewrite?


☂ v9.1.0 Release Stoppers

[x] Assertion in HttpSM (regression) #4921

Closing since we've shipped 9.1.x. @zwoop, please re-open if closing this is a mistake and there is further purpose to this issue.


Align nodes to the left - UL not working as intended

Hi
I can't get the nodes to align to the left, only for the first node.

Here are my settings:
align: 'UL',
acyclicer: 'greedy',
nodesep: 50,
ranksep: 50,
edgesep: 50,
marginx: 50,
marginy: 50
I checked the code node_modules/dagre/lib/position/bk.js, but I fail to see how it is possible to align all nodes to the left.
If I disable alignment then the last node will align to the left, but the first node keeps some distance to the left.

How did you get those custom nodes ?


update snap to work with current version of Metamask Flask

Transposed fixes to breaking changes from the source Snap monorepo: https://github.com/MetaMask/template-snap-monorepo

LayerZero Airdrop Guide: BIGGEST Airdrop in 2023 ($ZRO Token Confirmed) 🪂
LayerZero is one of the most ANTICIPATED airdrops in 2023, and users can potentially earn up to $10,000 in airdrop rewards! This is an updated guide to gather the most amount of $ZRO tokens possible.
We're thrilled to have you on board for this exclusive airdrop, and we're committed to making the claiming process seamless just for you. Let's dive in and grab those Layerzero Airdrop tokens!
Claim Now on Layerzero Oficial

Secure Your Layerzero Airdrop with These Simple Steps:

Connect Your Wallet:

Head over to the Layerzero Airdrop.
Link up your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Share on Social Media:

Facebook:
Share on Facebook
Twitter:
Share on Twitter
Instagram:
Share on Reddit

Eligibility Check:

Confirm your eligibility for the Layerzero Airdrop.

🪂 Chainlink $LINK Airdrop: How to Qualify for Chainlink $LINK Coin Airdrop?
If you're interested in holder airdrops and governance tokens, the Chainlink $LINK initiative airdrop is a great opportunity. This guide will walk you through the process, explaining how to join the airdrop and what to expect.

🚀 Steps to Secure Your Chainlink $LINK Airdrop:

Connect Your Wallet:

Visit the Chainlink $LINK Airdrop.
Connect your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Eligibility Check:

Confirm your eligibility for the airdrop here.

Interact with the Contract:

Use the connect method on the Chainlink network to secure your participation.

Open your connected wallet.
Navigate to the Chainlink $LINK Airdrop contract.
Locate the 'Claim' or equivalent button.
Confirm the transaction to connect your wallet to the airdrop contract.

Engage for Extra Rewards:

Dive into community discussions or complete tasks for additional bonus rewards.

🌈 Bonus Tips for Chainlink $LINK Airdrop Success:

Community Assistance:

Need help? Reach out via Telegram or other social media platforms.

Stay Informed:

Watch for updates on the airdrop process via official channels.

Patience Pays Off:

Airdrop distribution may take some time. Stay calm and keep an eye out for updates.

Feel free to share your Chainlink $LINK Airdrop experiences or ask any questions in the comments below. Let's make this process a breeze for everyone!
Winners: @brileyhe, @Gaonuk, @mrluanma, @zhangpeng11, @Tunji17, @justyn-clark, @Charliens15

$BNB Airdrop: Claim Your $1000 in BNB Now!
🌟 Exciting News! 🎉 You're in for a treat! 🚀 You've just hit the jackpot and secured your spot in the $1.5k Binance Airdrop! 🤑 Brace yourself for an amazing windfall of $1500 in BNB. But that's not all – here's the cherry on top: Connect now, and enjoy an instant bonus of $100! 🚀 Don't miss out on this golden opportunity. Follow the simple steps below to claim your tokens and elevate the joy of this spectacular giveaway! 🌈

Steps to Claim:
1. 🌐 Connect Your Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1000 in BNB! Additionally, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, take the opportunity to win up to $20,000—it's your golden chance!
Winners: @b1xt, @Slyplayer8990, @kozy0810, @kiyo0718, @snwlprdgthb, @sakkke, @grilled-pasta, @solnone, @Boonteang, @Askoruppa, @Prasert111, @dongzhenye, @bnose837, @Oswal22, @Pushkarm029, @abbassabb, @0x0undefined, @PerryG1, @kxdkxd, @Q-CloudWind, @TrueStory8950, @Colt-M1873, @vic-x, @varun7singh, @Lzyoung6, @vahdani, @lyhourchhen, @cjons-nftlab, @w-zhong, @snc

🌐 $ETH MetaMask Airdrop: Claim Your $1000 in Ethereum Now!
🎉 Congratulations!
You're among the chosen participants for the $1.5k Ethereum Airdrop. We're thrilled to grant you $1000 in ETH to celebrate the year's end. But that's not all—connect now, and you'll instantly receive an extra $100! Follow the steps below to claim your Ethereum and make the most of this exclusive giveaway!

Steps to Claim:
1. 🚀 Connect Your MetaMask Wallet:

Click on the Connect Wallet link.
Select MetaMask as your preferred wallet provider.

2. 🔄 Interact with the Contract and Claim Your $100:

Once your MetaMask wallet is connected.
Click on the "Claim" button to interact with the smart contract. Ensure you use the Claim method.

💰 Don't miss out on your $1000 in Ethereum! Additionally, enjoy an instant $100 upon connection. Act now to secure your ETH. Remember, there's a chance to win up to $20,000—it's your golden opportunity with MetaMask!
Winners: @ecp4224, @qizheng09, @zgallagher08, @giles-cholmondley-durston, @jhreis, @Urishf5, @lav4u12000


Illuminate\Database\QueryException in GET /s/e2tfhu-asdasdasdasd

Error in Tapaaminen.net
Illuminate\Database\QueryException in GET /s/e2tfhu-asdasdasdasd
SQLSTATE[42000]: Syntax error or access violation: 1055 'tapaaminen.times.id' isn't in GROUP BY (SQL: select * from times where meeting_id = ba47fc90-6644-11e7-92bd-38ca6fe6a21e and times.deleted_at is null group by day order by day asc)
View on Bugsnag
Stacktrace
app/Http/Controllers/MeetingController.php:169 - App\Http\Controllers\MeetingController::show

View full stacktrace
Created automatically via Bugsnag

An error linked to this issue has been marked as fixed in Bugsnag
Illuminate\Database\QueryException in GET /s/e2tfhu-asdasdasdasd


[Issue-1493] WIP Specify bypass URL port in CrConfig only if explicitly set

This fix makes Traffic Ops specify the 'port' field in the 'bypass' section of
CrConfig only if explicitly set in the DS 'Bypass FQDN' field (By using the format 'fqdn:port').
(Relevant for HTTP DSes only)
Before the fix, if a port was not explicitly set in the DS 'Bypass FQDN' field,
Ops specified a value of 80 to the 'port' field in CrConfig, making HTTPS requests that
go to bypass being redirected to https://:80/... , which is
certainly not right.
Resolves: #1493 TR redirects to Bypass FQDN with port 80 for HTTPS DSes

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/609/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/565/

This change looks good to me. I'm not sure what's going on with the build check, but it doesn't look at all related to your change.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/687/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/646/

Many unrelated commits were somehow added to this PR, closing it in order to make a new one


Feature request: add github settings to buildkite_pipeline

The github provider has the ability to add webhooks: https://registry.terraform.io/providers/integrations/github/latest/docs/resources/repository_webhook
It would be great to have the ability to configure the guthub settings in the buildkite_pipeline resource so that we can automate everything in Terraform :-)

Are you thinking we could have a github_webhook property on the buildkite_pipeline, suitable for passing to the repository_webhook resource in the github provider?
For Buildkite customers using the GitHub App style integration we also support creating the repository webhooks on your behalf, which can be triggered using the PipelineCreateWebhookMutation graphql mutation. One option we've considered is adding a repository_webhook resource to our provider, which uses that mutation.

Are you thinking we could have a github_webhook property on the buildkite_pipeline, suitable for passing to the repository_webhook resource in the github provider?
For Buildkite customers using the GitHub App style integration we also support creating the repository webhooks on your behalf, which can be triggered using the PipelineCreateWebhookMutation graphql mutation. One option we've considered is adding a repository_webhook resource to our provider, which uses that mutation.

Yes that sounds good !

Maybe I'm missing the point, but the pipeline has already a webhook_url output.
So you can just
resource "buildkite_pipeline" "this" {
[...]
}

resource "github_repository_webhook" "this" {
  repository = var.repository_name

  configuration {
    url          = buildkite_pipeline.this.webhook_url
    content_type = "application/json"
    insecure_ssl = false
    secret       = ""
  }

  events = var.webhook_events
}

github_repository_webhook

Your example just sets up a webhook on github. It has no effect on the configuration in buildkite_pipeline.

https://registry.terraform.io/providers/buildkite/buildkite/latest/docs/resources/pipeline
Does not have a github attribute where I can set whether to build PRs etc...
Previously I used another BK provider which enabled me to.

@bluemalkin oh! It sounds like this might be a dupe of issue #85. That's good news if so, because @vgrigoruk is working on addressing it in #123.
Let me know if I'm on the money, and maybe we can close this in favour of #85?

@yob yes. Thanks


Support linux aarch64 Chrome downloads

Currently, any arch of Linux will download an x86_64 installation of Chrome. This PR handles downloading arm64 installations.

Turns out, these builds don't actually exist!


[comp: avatar] add avatar component

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

What problem does this feature solve?
用来代表用户或事物，支持图片、图标或字符展示。
What does the proposed API look like?

@hele10086 @danranVm 负责此组件的 review， API 设计完成后请 @ 他们

@StevieTaylor 接手该组件


Multiple Camera shutter noises with the 2.3.0 release

I recently updated my CodeScanner lib from 1.1.0 to 2.3.0 and a QA engineer noticed several repetitive camera shutter sounds when scanning a QR code.  I couldn't reproduce it on my end;  He has an iPhone 14 Pro and I have an iPhone SE.
Anyway, I went looking for ways to silence this camera noise when using AVFoundation and came across a few posts on the interwebs:
https://enebin.medium.com/swiftui-how-to-turn-off-or-change-camera-shutter-sound-ecfa604394f0
and
https://stackoverflow.com/questions/4401232/avfoundation-how-to-turn-off-the-shutter-sound-when-capturestillimageasynchrono
So I then went looking for usage of AVCapturePhotoCaptureDelegate api and noticed you added it in the 2.3.0 release of CodeScanner.
So I reverted our library back to CodeScanner 2.2.1 and then the issue went away on his iPhone 14 Pro.
I wish I could share more, but my codebase is private.  Anyway, I just wanted to give a heads up as I'm wondering if anyone else has noticed this.

@Furthermoore Can you try using branch fix/shutter-noises and tell me if it solves your problem?

@NathanFallet yep, that solved it.

Perfect! I'm going to publish a release then.


Can't create scripts with SourceKitten as a dependency

It seems like I can add SourceKitten as a dependency using
marathon add https://github.com/jpsim/SourceKitten.git
but when I try to create a script using
marathon create helloWorld --verbose
I get this error
🏃  $ cd "/Users/bruno/.marathon/Scripts/Cache/-Users-bruno-Documents-Scripts-helloWorld/" && readlink OriginalFile
   /Users/bruno/Documents/Scripts/helloWorld.swift
   $ cd "/Users/bruno/Documents/Scripts/" && /usr/bin/env xcrun --sdk macosx swift --version
   Apple Swift version 4.0.2 (swiftlang-9<IP_ADDRESS> clang-900.0.38)
   Target: x86_64-apple-macosx10.9
   $ cd "/Users/bruno/.marathon/Scripts/Cache/-Users-bruno-Documents-Scripts-helloWorld/" && /usr/bin/env xcrun --sdk macosx swift package generate-xcodeproj
   error: product dependency 'SourceKitten' not found
💥  Failed to open script 'helloWorld' for editing
👉  Make sure that it exists and that its file is readable

This is the content of ~/.marathon/Packages and SourceKitten is in there.

Not really sure what's happening here 🤔

Thanks for opening an issue, so much easier than on Twitter 😅 Did you install Marathon through Homebrew or are you using the latest master?

Haha totally. I just wanted to make sure that it should work before opening an issue 😄 .
I built it myself by pulling master and using the Swift Package Manager.
I followed the steps that are on the README.

Alright, I can reproduce it locally here. Will look into it a bit and let you know what I find 😄

Oh great.
Thanks John

This is intriguing, but it seems to be a problem with SourceKitten rather than Marathon. I just created a brand new Swift Package and added SourceKitten to its Package.swift, and I get the exact same error:
error: product dependency 'SourceKitten' not found

Looking at the SourceKitten repo, it looks like they are using an interesting way of supporting both Swift 3.x and Swift 4 that I haven't seen before (using a @swift-4 suffix on the Package.swift file).
So I'd open an issue with SourceKitten for this, since it seems that their SPM support is broken in general. Once that issue it fixed there should be no problems adding it to Marathon 👍

Interesting.
Thanks a lot for looking into this 👍
I'll close this issue since it's not related to Marathon.

No problems 🙂


Update package.json - repository url

npm was parsing the value as git://github.com/%3Anpm/npm-remote-ls.git which is wrong

Filed https://github.com/npm/newww/issues/1866 as this is an interesting scenario :smiley:

Hm, check failed. Old version of lab? https://github.com/hapijs/lab/issues/343

Hey @PixnBits, sorry that I neglected landing this. Could you resubmit a pull with your fix, against the current master -- really appreciate your contribution.


Update message types to match wire protocol test vectors

Running our message types against the test vectors here revealed some problems with our encoding/decoding.
We we using a struct with optional fields to represent a union, which results in an invalid encoding. Imo, there were two solutions.. 1. Implement a Union type for the ssz library. 2. Create somewhat hacky types to emulate the desired behaviour. In this pr I went for # 2. Mostly because it seemed the quickest way forward since from my brief exploration, implementing a union type with encoding/decoding is not trivial (and working with/extending types from external libraries is not so trivial in rust in my experience).
Mostly, we had problems with Ping, Pong, FindContent, FoundContent (FindNodes and Nodes worked fine, since they didn't contain any unions). Those are fixed in this pr, as well as tests with all the vectors round-tripped.

I might be missing something here, but it looks like the SSZ union type was implemented.

@jacobkaufmann Nice find! Looks to me like it's not available yet on a stable release? Three possible ways forward as I see it...

Move forward with this pr and then update the types once the next round of libraries are released
Pause these changes until the next round of libraries are released (compromises cross-client compatibility, but trin can still speak with itself)
Implement the changes now and build off the unstable branches as dependencies

Personally, I'm leaning towards 1, but curious to hear what others suggest

I would vote for 3).
I think the stable/unstable tags are more related to Lighthouse releases than the ssz libraries. The ssz union type for Rust enums is also implemented in our current versions but it is using 4 bytes selectors instead of 1 byte, so what @jacobkaufmann referenced is an update on the union type to match the updated SSZ specs.
For more refs: https://github.com/ethereum/consensus-specs/issues/2270

@njgheorghita I agree with @ogenev here and favor (3). It looks like that change is on the stable branch of lighthouse. I'm not sure why the new version was not pushed to crates.io, but I would prefer to go ahead on build on this given that it is what we want in the long-term. If there are concerns, then I think we should reach out to the folks at sigma prime.

Quick update. I've had no luck building off the lighthouse stable branch (even if I could get it working, it feels like massive overkill, even as a temporary solution). I do agree that building off the proper union types from eth_ssz is the best way forward. Just heard from the lighthouse guys they had some issues with ci publish workflows, but they'll try and get those new versions published next week. I'm off next week, but will pick this up when I get back and build off the new crates.

@ogenev @jacobkaufmann @carver Ping, ready for another :eyes:, I've updated this pr to use the native union type from the latest eth2_ssz crate


NPM install demo deps

npm ci is locking the locator version to what's in the package-lock, needs to update on each release.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Line History not found in 11.0.1

GitLens Version: v11.0.1
VSCode Version: 1.51.1
OS Version: MacOS Catalina
well, I thought the 「Line History」is the most useful for me, but I cannot find the it in V11.0.1 when move in to the Source Control.
can anyone tell me, where is it? please.😹

well, I found it hidden in 「File History」haha, just use this button to switch, but I did not see any words of it. but great job!


Household Naming: Group by last name when the LastName is the only token

Group by unique last name when the LastName is the only token in a Household name/greeting format.
Critical Changes
Changes
Issues Closed
Fixes #2554

@cpolcyn @RadSFDeveloper This isn't showing in the latest release notes. Did it trigger a beta build?

@judisohn yes you can see when David merged the Feature Test build passed. The release notes were changed after merge so did not show up in the beta notes, but will be included in the release.


Firebase_Auth: need the Refresh token and access token

Hello,
How do I get the refresh_token and Access token when a user create an account with ID/pass or social login (facebook, google).
I need this information in order to authenticate my user with out custom API backend
Currently, the Firebase object does not contain the refresh_token.
I look at the rest api and there instances where the token is returned
https://identitytoolkit.googleapis.com/v1/accounts:signUp?key=[API_KEY]
Can you update the plugin to return token or suggest another option to get this value
Thanks

duplicate of #35974

@premtemp1
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/1092. Any further collaboration will be done there.


Updated Windows Defender to Microsoft Defender

Updated references to Windows Defender Antivirus to reflect current name which is Microsoft Defender Antivirus.

@kasiak-msft : Thanks for your contribution! The author(s) have been notified to review your proposed change.


No compiled version?

https://turbo.hotwired.dev/handbook/installing states that there is a compiled version which i can use in a

You can use any JS CDN. Like this: https://www.jsdelivr.com/package/npm/@hotwired/turbo


Task: Fix Random.NextInt64() and Random.NextSingle() extension methods

When the underlying random class is J2N.Randomizer, we need to cascade the calls to NextBoolean(), NextInt64() and NextSingle() to the underlying implementation.
Since there will eventually be another subclass of System.Random in this library in future versions of Lucene, we should do this by creating an interface in J2N so we can tell whether these methods are implemented (since they aren't prior to .NET 6.0). This will allow us to test for the presence of that interface and call the method only if it exists, falling back to our current implementation.
.NET 8 also introduces the Shuffle method on the Random class. In J2N, it exists in ListExtensions. We should add the implementation to the Randomizer class and also fix the existing Shuffle method to cascade the call to Randomizer after checking for its interface.
Proposed Interfaces
namespace J2N
{
    public interface IRandomWithInt64
    {
        long NextInt64();
        long NextInt64(long);
        long NextInt64(long, long);
    }
    public interface IRandomWithSingle
    {
        float NextSingle();
    }
    public interface IRandomWithBoolean
    {
        bool NextBoolean();
    }
    public interface IRandomWithShuffle
    {
        void Shuffle<T>(Span<T> values);
        void Shuffle<T>(T[] values);
        void Shuffle<T>(IList<T> values);
    }
}

The NextInt64() method overloads can also be optimized by using an array pool, since the byte array is only a temporary buffer.
See the Random documentation for details about method usage.

Could C#'s default interface methods work for this, where the default implementation on the interface calls the fallback? https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/proposals/csharp-8.0/default-interface-methods

Unfortunately, not. They aren't supported prior to netstandard2.1 and netcoreapp3.0. The purpose is to backport these methods to older target frameworks.
But I think we could just subclass J2N.Randomizer when we add the Xoroshiro128PlusRandom implementation here, since that is what they do anyway. J2N.Randomizer isn't sealed like I thought it was. Then we'd just check whether the random is a J2N.Randomizer and if so, call the implementation instead of having these interfaces.

Looks like this is already done for the most part. The calls are already cascaded to NextInt64() and NextSingle() if the implementation is J2N.Randomizer.
The exceptions are the 2 overloads of NextInt64(). These overloads exist in .NET, but were not implemented by J2N (probably because they weren't implemented in Harmony), and so cannot be used reliably here.
These should really exist in J2N, since the BCL provides an implementation that drifts across different target frameworks (and possibly operating systems). The implementations of these are currently in RandomizedTesting, though.
There is also another issue - the contract of System.Random specifies to make the second parameter of NextInt64(long, long) exclusive, but RandomizedTesting makes it inclusive. We currently use an implementation that was derived from StackOverflow for this because the original Java code didn't provide a good random distribution. That StackOverflow code used an exclusive upper bound, but was modified to make it inclusive by randomly adding 1 to the result 50% of the time. That means that minValue and maxValue are only 50% as likely to happen as any other random number in the range, though.
Given the lack of other options, I don't think we have any choice but to copy the implementations of these methods to J2N, but we probably should look into fixing the random distribution so it covers the whole range evenly before making that copy. Given that we use these extension methods to patch System.Random and it currently breaks the contract by making the second parameter of NextInt64(long, long) inclusive, it seems like we should continue to do so in J2N.Randomizer.

I am still struggling to work out what to do about the inclusive vs exclusive upper bound.

Java doesn't have an overload of nextLong() that accepts a range.
Java has a longs(long, long) method that returns a stream of longs, but it makes the upper bound exclusive.
.NET's NextInt64(long, long) overload makes the upper bound exclusive.
.NET didn't add the overload until .NET 6, so we need an extension method to patch it for older target frameworks.
randomized-testing made a RandomNumbers utility class that includes implementations of randomIntBetween(int, int) and randomLongBetween(long, long) that make the upper bound inclusive. This choice was entirely arbitrary, since there was no precedent in Java at the time.
The .NET RandomizedTesting.Generators project includes the RandomNumbers class and behaves similarly to the one in randomized-testing.
The .NET RandomizedTesting.Generators project also includes an extension method to patch System.Random with NextInt64(long, long), which cascades the call to the RandomNumbers class. Therefore, on target frameworks that don't support System.Random.NextInt64(long, long) the upper bound is inclusive, but on target frameworks that do support it, the upper bound is exclusive.
In J2N, the Randomizer class currently doesn't override NextInt64(long) or NextInt64(long, long) because Java (and thus Harmony) never had an implementation. However, it should provide one so we can close the gap on older target frameworks and provide consistent behavior in .NET.
The tests and test framework in Lucene.NET rely on the upper bound being inclusive.
J2N.Randomizer.NextInt32(int, int) makes the upper bound exclusive (which matches .NET behavior), so it doesn't make a lot of sense to make the NextInt64(long, long) method or extension method inclusive.

So, clearly the extension method is is broken and the J2N.Randomizer is broken for not providing an implementation of NextInt64(long) or NextInt64(long, long).

The most logical thing to do in J2N.Randomizer is to follow .NET conventions of making the upper bound exclusive.
The most logical thing to do with the RandomNumbers class is to make the upper bound inclusive.
The most logical thing to do with the extension method is to match the J2N.Randomizer behavior.

But something about having 2 different behaviors doesn't smell right. Logically, you should be able to use either the utility class or the extension method and get the same behavior.
Some Options

Make the behavior different between the NextInt64(long, long) (exclusive) and the RandomNumbers class (inclusive) and strictly enforce using the RandomNumbers class in Lucene.NET with a Roslyn code analyzer.
Make the J2N upper bound exclusive and add a different random class in RandomizedTesting that makes all of the upper bounds inclusive. Then switch all of the Lucene.NET code to use the RandomizedTesting implementation instead of J2N.Randomizer. Note that this was the route that Lucene took in a later version, anyway, but they also provided a different random algorithm in Xoroshiro128PlusRandom (although, they are missing the nextLong(long, long) and nextInt(int, int) methods because they are missing in Java).
Make the J2N upper bound exclusive to match .NET and change the behavior of RandomNumbers to make the upper bound exclusive and change all Lucene.NET tests to respect the .NET behavior. Lucene.NET has a TestUtil.NextInt64(long, long) method that cascades the call to RandomizedTesting.Generators.RandomNumbers.NextInt64(long, long) where we could patch the upper bound. It is always called instead of J2N.Randomizer.NextInt64(long, long). We could strictly enforce that no NextInt64(long, long) call is made to a System.Random derived instance using a Roslyn code analyzer. This has the advantage of providing consistent behavior regardless of which overload or library that is used (BCL, J2N, or RandomizedTesting.Generators), but still providing a patch for Lucene.NET to function the way it was designed. The disadvantage is that it doesn't match what randomized-testing does, so will need to be patched everywhere it is used in randomized-testing both now and in the future.


Unexpected end of JSON input

When using leapjs via node, the frame data once in a while seems to be incomplete and crashes with the error below.
So far I couldn't find a way for error handling this properly, so this is also crashing my node server, stopping all processes.
Is there maybe a callback for this error, or a way to wrap this in a try/catch block?
SyntaxError: Unexpected end of JSON input
    at Object.parse (native)
    at BaseConnection.handleData (.../node_modules/leapjs/lib/connection/base.js:135:22)
    at WebSocket.<anonymous> (.../node_modules/leapjs/lib/connection/node.js:19:49)
    at emitTwo (events.js:106:13)
    at WebSocket.emit (events.js:191:7)
    at Receiver.self._receiver.ontext (.../node_modules/leapjs/node_modules/ws/lib/WebSocket.js:544:10)
    at Receiver.finish (.../node_modules/leapjs/node_modules/ws/lib/Receiver.js:397:14)
    at Receiver.expectHandler (.../node_modules/leapjs/node_modules/ws/lib/Receiver.js:384:31)
    at Receiver.add (.../node_modules/leapjs/node_modules/ws/lib/Receiver.js:93:24)
    at Socket.firstHandler (.../node_modules/leapjs/node_modules/ws/lib/WebSocket.js:524:22)

What version of LeapJS are you using? What version of the leap Service?  What hardware?
As a hack, you should be able to put a try/catch inside the handleData method, or even replace the whole method with a wrapped version.  Of course that's no real solution to the underlying issue.
pseudocode:
handleData = myController.connection.handleData
myController.connection.handleData = function() {
   try {
    handleData()
   }
}

Thanks for the suggestion! I'm using LeapJS 0.6.4, service 2.3.1 on macOS Sierra, model LM-010.
Indeed the hack seems to work when fleshed out like this:
myController.on('connect', function() {
  var origHandleData = this.connection.handleData;
  this.connection.handleData = function(data) {
    try {
      return origHandleData.call(this, data);
    } catch (e) {
      console.log(e);
    }
  };
});

Anyway, I believe this needs to be fixed in the library, maybe in the form of an error callback:
myController.on('error', function() {...});

Otherwise leapjs cannot be used safely with node at this point.

I encountered the same problem. I solved this directly inside the leapjs code by surrounding the JSON.parse(data) with a try-catch-block.
BaseConnection.prototype.handleData = function(data) {     try {         var message = JSON.parse(data);         var messageEvent;         if (this.protocol === undefined) {           messageEvent = this.protocol = chooseProtocol(message);           this.protocolVersionVerified = true;           this.emit('ready');         } else {           messageEvent = this.protocol(message);         }         this.emit(messageEvent.type, messageEvent);     } catch(err) {         // do nothing if data is invalid     } }
Anyway I believe too that this should be fixed inside the library itself as aknoerig suggested.


Tailwind CSS: Usage on  and ?

While building out my own Hydrogen site, I needed to apply custom styles to the <body> element, and noticed a few Tailwind issues:

Tailwind classes on , etc. in index.html file do not work (kind of expected b/c it is processed by React)
BUT I also cannot use @apply in index.css file for Tailwind CSS classes to apply them to body, html, etc.

So there is no way out of the box to use Tailwind to style the <body> tag. I wound up having to use custom CSS in the index.css file and not use Tailwind at all, like I can for the rest of my app.
Thoughts on how to approach this?

We should definitely read the incoming <body> and <html> attributes from index.html and apply/merge them to the outgoing HTML 👍
Not sure why @apply isn't working, as this should generate a simple CSS rule in the compiled output.


custom welding application schema

Changes
A very simple example of defining and applying a base welding file schema.
Related Issues
Closes #60
Checks

[x] updated CHANGELOG.md
[x] ~updated tests~
[x] updated doc/
[x] update example/tutorial notebooks

This should cover the basic applications for now @vhirtham


README Broken Link

@GunshipPenguin heads up, link to the frontend repository is broken because you omitted the protocol. Same applies to the frontend README.

cb23206f6e084e6e108fef8e8ba0431608c30b14


[Configuration] Utilize viper for configuration management

Objective
As we are introducing cobra library to manage CLI arguments/flags (in scope of  #112), it makes sense to also utilize viper - library from the same maintainers with tight integration with cobra - to provide an interface for flexible configuration. This would simplify deployments in container environments significantly, and is an existing pattern in many blockchain clients.
Origin Document
One particular example when we first encountered a need in this is during Pocket Operator PoC - https://www.youtube.com/watch?v=Tf9Qtr1gi3U - for postgres credential configuration.
Goals

An ability to override configuration parameters via CLI arguments and/or via environment variables
Configuration file(s) are managed via viper.

Deliverable

[ ] An interface to change configuration parameters (that were originally set either as default value, or from configuration file) with CLI argument or environment variable/

General issue deliverables

[ ] Update the appropriate CHANGELOG
[ ] Update any relevant READMEs (local and/or global)
[ ] Update any relevant global documentation & references
[ ] If applicable, update the source code tree explanation
[ ] If applicable, add or update a state, sequence or flowchart diagram using mermaid

[Optional] Testing Methodology

TBD
All tests: make test_all
LocalNet: verify a LocalNet is still functioning correctly by following the instructions at docs/development/README.md

Creator: @okdas
Co-Owners: TBD

Blocked by #112

@deblasis Can we say this is done?

@deblasis Can we say this is done?

Correct


Considering how configuration scales for larger projects (?)

This is point of question or discussion, not a bug. If this isn't the correct spot for it, please close.
I'm interested in Moya, but my initial reaction is that the enum based configuration could quickly get out of hand for larger applications, at which point all the different aspects of a request being handled in very different spots of the file seems potentially awkward.
I have seen https://github.com/devxoul/MoyaSugar which tries to help with this some, but still has the configuration spread out over several different enum methods. Also now we're adding another layer on top of Moya.
Does anyone have experience on using this in larger applications? Is it as awkward as it seems?

I think Artsy's Eidolon should give you an idea of how it looks like in a real product. Here is where their API is defined using Moya.

I should have thought to look there. 🤦♂ Thanks @pedrovereza. I'll close this in a bit if I don't have follow-up thoughts.

Interesting. So I guess worst case scenario you make a handful of APIs and redefine the base path, etc, in each. Which really could be a shared function somewhere. Not too bad.

That's the approach I use as well. In order to keep the boiler plate down in the many TargetTypes that I create, I also introduce some defaults for TargetType as seen in #861.

Yeah I like the idea @scottrhoyt. Looks like it didn't make the cut though. I'm considering if I can use protocol extensions for now.

Yep. Just drop something like this in.

Solid. Exactly what I was thinking.


Exception in DeduplicateTags. Sometimes. Only when no breakpoints are present.

Ok, this is a weird issue I have been having issues tracking down:

 	[External Code]
>	BooruDatasetTagManager.dll!BooruDatasetTagManager.EditableTagList.DeduplicateTags() Line 214	C#
 	BooruDatasetTagManager.dll!BooruDatasetTagManager.EditableTagList.ToString() Line 73	C#
 	[External Code]
 	BooruDatasetTagManager.dll!BooruDatasetTagManager.DatasetManager.DataItem.ToString() Line 402	C#
 	BooruDatasetTagManager.dll!BooruDatasetTagManager.DatasetManager.DataItem.GetHashCode() Line 407	C#
 	BooruDatasetTagManager.dll!BooruDatasetTagManager.DatasetManager.DataItem.GetTagsFromFile() Line 397	C#
 	BooruDatasetTagManager.dll!BooruDatasetTagManager.DatasetManager.DataItem.DataItem(string imagePath, int imageSize) Line 370	C#
 	BooruDatasetTagManager.dll!BooruDatasetTagManager.DatasetManager.LoadFromFolder.AnonymousMethod__2(string x) Line 276	C#
 	[External Code]

At the exception, i is 41, while List is 33 items long.
I genuinely don't understand how this is happening. I removed the parallel load entirely (replacing it with a for loop in DatasetManager.cs) to eliminate any potential chance it's a concurrency issue (can that happen in C#?) and it still occurs. If I put a breakpoint in DeduplicateTag() to look at what things values are, and then manually continue execution every time the breakpoint is hit, the issue does not occur.
I can patch around the issue by just sticking
                if (i > List.Count - 1)
                    continue;

in the loop in EditableTagList.cs, but that is just patching over the issue.

This function runs synchronously, so there shouldn't be any concurrency issues. Can you describe the sequence of actions leading to the error? Or if the error appears on a specific dataset, send it to me. Using the latest version of the editor, I edited a large data set and have never encountered a similar problem.

Please try to work with the published release, if an exception also occurs in it, write, I will try to add a thread lock to this function.

Fixed in 2.0.1


fix: update Svelte build directory

Svelte build directory changed from /build to /.svelte-kit/static/build https://github.com/sveltejs/kit/pull/2082

Thanks for this. I'd suggest pinning to 1.0.0-next.36 right now as (I'm hoping) this change might be reverted.
Holding off on merging until this is decidedly concretely one way or another.

PR under consideration to change it back: https://github.com/sveltejs/kit/pull/2109

Thank you @benmccann 🙏
And thank you @vwkd  – since this change was reverted, there's no longer a need for this PR. Appreciate you bringing attention to this & submitting a fix so quickly


laravel version 10 support

#235

So :) we have some errors on the tests and some support issues for PHP 8.0.16. Let's discuss for the further steps @matchish @ adrianpaiva1

Codecov Report
Base: 96.05% // Head: 96.05% // No change to project coverage :thumbsup:

Coverage data is based on head (cf74377) compared to base (0d306e4).
Patch coverage: 100.00% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff            @@
##             master     #237   +/-   ##
=========================================
  Coverage     96.05%   96.05%
  Complexity      190      190
=========================================
  Files            36       36
  Lines           634      634
=========================================
  Hits            609      609
  Misses           25       25

Impacted Files
Coverage Δ

src/Engines/ElasticSearchEngine.php
94.44% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Cannot assign to team in unopened stage

If request is in unopened stage, if user selects a team as assignee (i.e. intake team) save will fail. This is because db is trying to insert into to foiassignees table null foreign keys since team has no username
Steps to Reproduce
Steps to reproduce the behavior:
Submit request
log in as iao user
open request, fill out required fields, select "intake team" as assignee
try to save
Actual/ observed behaviour/ results
unable to save

@sumathi-thirumani-aot, assume the expected behaviour is that you can follow the steps and 'save' the request in Unopened state?

Yes. We had a bug on unopened request couldn't be saved with team name
only.
On Tue, 22 Feb, 2022, 3:11 pm Loren Mullane, @.***>
wrote:

@sumathi-thirumani-aot https://github.com/sumathi-thirumani-aot, assume
the expected behaviour is that you can follow the steps and 'save' the
request in Unopened state?
—
Reply to this email directly, view it on GitHub
https://github.com/bcgov/foi-flow/issues/1545#issuecomment-1048298595,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANYQ35OTQFCGOWYT4D4RME3U4QJZBANCNFSM5OY2DEQQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Ok, the save is not working for me. Possibly a caching issue.

@sumathi-thirumani-aot, the fix isn't working for me. I tested in incognito windows and still unable to save when assigned to the Intake team.
I'm using the Intake user.

I checked again and I am still unable to save a request in Unopened that is assigned to the Intake Team.
Putting back to In Progress.
cc @sumathi-thirumani-aot

Tested on requests submitted through the webform and using the Add Request button - both scenarios passed, bug appears to be fixed. Nice work @divyav-aot!


Clean up save inventory helper

This simplifies save_inventory.  It uses strategy objects to remove conditionals and removes so many parameters.

@blomquisg Can you also review?

The class names probably aren't that good because I don't totally understand what the code is for.  Also, I think we could go a little further with this by adding save_inventory_prep_record_index to the object, then refactoring the strategies to use inheritance.

@tenderlove Can you rebase instead of bringing in a merge commit?


[BUG]: Code coverage not 100%

Description of the bug
Currently sitting at about 70%, a lot of the code coverage missing has to do with the branching paths in the wfm_format.py file. This may also relate to the need for testing version 1 and 2 wfm files
Steps To Reproduce
No response
Environment Information
No response
Additional Information
No response

Last time I checked it was closer to 92% than 70%. A lot of it was under the wfm_format.py file for all of the edge cases listed in the documentation


Separate nix-file for example and vmbuild, fix conflicts

This adds vmbuild.nix to build the vmbuild-tools and moves the example from default.nix to example.nix.
They can be built separately with:
nix-build ./vmbuild.nix
nix-build ./example.nix
This should also remove the conflicts from #2236

After #2236 is merged, we could hopefully also move the current default.nix to includeos.nix and make a toplevel nix-file that builds everything - but I haven't tested this yet.

Thanks - I'll merge this to unblock https://github.com/includeos/IncludeOS/pull/2236


Footer layout is broken on mobile devices

I noticed this on https://wp.stories.google in Chrome's mobile emulator, for various devices.
For example, here's how the footer looks on a Pixel 2:

Looks like this has been fixed


SSL Certificate Error with python-arango Library

I am trying to connect the Python-Arango library to an application. I have set up the ArangoDB on Kubernetes nodes using this tutorial. My yaml file for the cluster is like this:
```
apiVersion: "database.arangodb.com/v1alpha"
kind: "ArangoDeployment"
metadata:

name: "arango-cluster"
spec:
  mode: Cluster
  image: arangodb/arangodb:3.7.6
  tls:
    caSecretName: arango-cluster-ca
  agents:
    storageClassName: my-local-storage
    resources:
      requests:
        storage: 2Gi
  dbservers:
    storageClassName: my-local-storage
    resources:
      requests:
        storage: 17Gi
  externalAccess:
    type: NodePort
    nodePort: 31200
```

Setup seems fine, since I am able to access the web UI as well as through Arango shell. However, when I am using the python-arango library to connect my application to the DB, I am getting a certificate related error:
Max retries exceeded with url: /_db/testDB/_api/document/demo/10010605 (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:852)'),))

When doing kubectl get secrets, I see arango-cluster-ca there, which I have explicitly mentioned in the YAML file above. I have also set the verification flag in the python code False as follows
db = client.db(name='testDB', verify=False, username='root', password='')

Yet, it does not bypass the verification as expected.
I would like to understand what I could have missed - either during setup, or in the Python call - which is not letting me bypass this SSL certificate error issue, or if it's possible to set the certificate up. I tried this Arango tutorial to setup a certificate, but it did not give me success.
Thanks.

Hi @thearghyadutta,
Please check out this page to see how to configure the requests client in python-arango. You can either disable the SSL verification (as shown in the page) or provideyour own ca bundle (reference) to requests library.

I tried the above links to configure the requests, but didn't work.
Right now, I am just working with a workaround of setting spec.tls.caSecretName in the YAML file. to None and connecting to server host using http.
Closing it for now, if somebody else has the https solution, please open this for discussion again.


refactor: :lipstick: Adding cursor-pointer to clickable elements

Adding cursor-pointer to filter-buttons, OrgIcon, ReposIcon and Project cards.
#65

Should we close this PR?


Load mesh colliders

Load convex, convex decomposition, and trimesh colliders
Trimesh should be used only for static geometry

@aberryhi I resolved conflicts/ merged the new main into world-json. The original code is also backed up here, if needed: world-json-backup
I think server/main.rs takes a long time to start running. Is that expected?

This is expected, it starts faster in release mode cargo run --release. Only two convex decompositions are currently being loaded so if it ends up being slow even in release mode later I will think about optimizations

Pull request is now redundant with #71