Bindings

According to Brian, we have to open the discussion regarding Bindings How we can map those into SwiftUI
https://hexdocs.pm/phoenix_live_view/bindings.html

FYI @carson-katri

Here are some ideas for how each binding could map to SwiftUI.

Note N/A does not mean it isn't possible to support, but instead that it doesn't map 1:1 with something from SwiftUI.

Binding
SwiftUI equivalent

Params

value-*
N/A

Click Events

phx-click
onTapGesture(count:perform:)

phx-click-away
N/A

Form Events

phx-change
N/A

phx-submit
N/A

phx-feedback-for
N/A

phx-disable-with
N/A

phx-trigger-action
N/A

phx-auto-recover
N/A

Focus Events

phx-blur
@FocusState

phx-focus
@FocusState

phx-window-blur
ScenePhase

phx-window-focus
ScenePhase

Key Events

phx-keydown
keyboardShortcut(_:)

phx-keyup
N/A

phx-window-keydown
keyboardShortcut(_:)

phx-window-keyup
N/A

phx-key
N/A

DOM Patching

phx-mounted
onAppear(action:)

phx-update
N/A

phx-remove
onDisappear(perform:)

JS Interop

phx-hook
N/A

Lifecycle Events

phx-mounted
onAppear(action:)

phx-disconnected
N/A

phx-connected
N/A

Rate Limiting

phx-debounce
N/A

phx-throttle
N/A

Static Tracking

phx-track-static
N/A

You read my mind, I started looking into this over the weekend but this is a much better representation of that


Move to latest Xunit packages

now consistent with AspNetCore-Tooling and only slightly ahead of Extensibility

Oddly, only the AspNetCore-helix-test check is in progress as I write this but many AspNetCore-ci jobs show that way. Not sure why GitHub and Azure Pipelines are out of sync…

FYI, despite my "oddly" point, the CI checks (other than Helix tests) were successful.


Implement Spectron Infrastructure

Create folder and code for setting up Spectron infrastructure.

This is done and pushed the changes


Why, when estimation a sequence, the depth between the frames is always different?

Why, when estimation a sequence, the depth between the frames is always different. Is it possible to averaged the value of the depth, like a implemented in Zoedepth?

Because estimation happens independently for each frame by design. There could be extensions of our method to aid this issue.
Please upvote this post so that we can estimate the importance of working on this issue

Temporally consistent video estimation would be HUGE. I have a set of VFX shots that need this right now.


Broadcast Server ID

Is your feature request related to a problem? Please describe.
I have a device that first needs to have the server id I want to communicate with set over the broadcast ID. The ModbusMessage does not allow creating messages with that ID tough.
Describe the solution you'd like
It would probably be the best case to add a solution, where I can send a ModbusMessage over the broadcast ID and then perhaps timeout with a seperate error like BroadCastServerID to signal that a broadcast ID was used when a timeout occurs.
Describe alternatives you've considered
I'm currently simply commenting out the line 441 in ModbusMessage.cpp, so I don't check if the server id is invalid anymore or not.
Additional context
Additionally line 154 of ModbusMessage.cpp sets the server ID as an error 0, that wouldn't work anymore if the check is removed so that would have to be replaced with an ID of 248 or above.

Oh well, the broadcast... It is not explicitly defined by the Modbus standard and the way you describe the application it only would work with a single server of that type on the bus.
We have an internal use for server id 0 already that means 'no valid server'. Changing that would be difficult as it is the intrinsic assumption.
As a workaround, you could try to use an empty ModbusMessage and fill it with a zero and all following bytes by hand, then send it with addRequest. You will get the timeout error, but at least it could work.

A solution could be to provide a broadcast(uint8_t *data, uint8_t len) method to the RTU client that will push out the data buffer prefixed with a zero byte and not wait for a response.
Worth investing time into it?

As far as I could see wouldn't it be possible to replace this line:
ModbusMessage.cpp / 154
if (MM_data.size() < 2) MM_data[0] = 0; // intentional invalid server ID!

With this:
ModbusMessage.cpp / 154
if (MM_data.size() < 2) MM_data[0] = 248; // intentional invalid server ID!

Meaning this code:
ModbusMessage.cpp / 440
Error ModbusMessage::checkServerFC(uint8_t serverID, uint8_t functionCode) {
  if (serverID == 0)      return INVALID_SERVER;   // Broadcast - not supported here
  if (serverID > 247)     return INVALID_SERVER;   // Reserved server addresses
  if (FCT::getType(functionCode) == FCILLEGAL)  return ILLEGAL_FUNCTION; // FC 0 does not exist
  return SUCCESS;
}

Could be replaced with this
ModbusMessage.cpp / 440
Error ModbusMessage::checkServerFC(uint8_t serverID, uint8_t functionCode) {
  if (serverID > 247)     return INVALID_SERVER;   // Reserved server addresses
  if (FCT::getType(functionCode) == FCILLEGAL)  return ILLEGAL_FUNCTION; // FC 0 does not exist
  return SUCCESS;
}

broadcast(uint8_t *data, uint8_t len) method to the RTU client
If that is not possible your idea would work good as well. As long as it is callable from the ModbusClientRTU as well.

broadcast(uint8_t *data, uint8_t len) method to the RTU client
If that is not possible your idea would work good as well. As long as it is callable from the ModbusClientRTU as well.

Of course, it would only be callable from a ModbusClientRTU instance. It would allow for a guarded treatment of broadcast requests - mind, the normal cycle is to wait for a response after a request, that ultimatively would run into a TIMEOUT with the regular flow.
I will implement the call these days, but am currently blocked by a malfunctioning internet connection. The service guys will come today and hopefully solve the issue.

We got a temporary bypass that is not guaranteed to last, so carpe diem is the motto ??
I pushed the changes into the Tiny-server branch - check that out, please.
ModbusClientRTU - send a broadcast request
ModbusClientRTU mbcr;
uint8_t message[] = "Broadcast to all folk!";
uint8_t msglen = strlen((const char *)message);
...
Error e = mbcr.addBroadcastMessage(message, msglen);
...

Error can be the new BROADCAST_ERROR, meaning the message length was invalid (0 or >253).
There will be no waiting for a response, the request is sent and forgotten.
ModbusServerRTU - receiving broadcast requests
ModbusServerRTU mbsr;
....
ModbusMessage WorkOnBroadcast(ModbusMessage request) {
  ...
  return NIL_RESPONSE;
}

The internal handling does require a ModbusMessage to be returned, although it is discarded right away. It is advised to return the pre-defined NIL_RESPONSE.
I tested this only sparsely, so any experiences are welcome.
[Update] Line is already down again, I am back to mobile now 😭

Oops, forgot to mention the server's callback register call:
registerBroadcastWorker(WorkOnBroadcast);

Thanks a lot will probably have a look tomorrow and good luck with your internet connection.

Will do.
There will be some more modifications, as I am planning to implement the proposed RTU sniffer mode alongside the Broadcast.

Sure no worries sounds good :D.

Done as intended. Broadcast workers now have a signature of void myBCworker(ModbusMessage m), so no return value any more.


Move global func into NodeController

This was a suggestion in an earlier PR by @ironcladlou after it was merged and I've finally gotten to it.
/cc @ddysher

LGTM.


recOrder uses MDA exposure settings which can create mostly unusable polarization data

When MM makes a multi-channel acquisition it lets you set different exposures for each channel. This feature is necessary for general MM use, but can lead to surprising/confusing behavior during polarization acquisitions via recOrder.
Problems arise when the user:

Opens MM with the default exposure (say, 10 ms).
Clicks "Acquire Birefringence" from recOrder.
(Naively) changes the exposure (say to 5 ms) from the MM main window.
Clicks "Acquire Birefringence" and get weird results because the acquisition uses (5, 10, 10, 10) ms exposures.

This behaviour accidentally bit @Soorya19Pradeep yesterday, and I can foresee it biting many new users in the future. I've also had to annoyingly reenter exposure times into the MDA window during sessions by myself and with @ieivanov.
I am considering two possible solutions:

Set the exposure from recOrder via a line edit box. I think this is the most modular design and will lead to the most predictable results.
Warn the user if they request a polarization MDA with different exposure times.

Extra context: in recOrder/acq/acq_functions.py lines 63-64 are:
#todo: think about how to deal with missing exposure
exposure = app.getChannelExposureTime(channel_group, chan, 10) # sets exposure to 10 if not found

I think we should only write to the MDA from recOrder, instead of reading and writing.

I agree with solution 1. From a user's perspective, being able to set the exposure in plugin is intuitive.

Thanks for the comment @ieivanov. I'm going back and forth here.
I agree with Ivan: MM already does a good job of handling exposure, and many users will be familiar with setting exposure in MM. Adding another exposure box could be confusing.
But if we're letting MM handle exposure, then why do we let the user choose Z stack settings from recOrder? These input fields face the same issues as the exposure fields: do MM inputs or recOrder inputs take precedence?
Our current solution gives MM exposure precedence and recOrder Z stack precedence, and I think we should shoot for consistency.
recOrder precedence is what I'm currently leaning towards. I'm imagining a user that opens MM, then opens recOrder+napari and leaves MM in the background w/o touching it. You can still set exposure setting for MM snaps, but if you hit "Acquire" from recOrder you'll use the recOrder settings.
MM precedence for functionality that MM provides is also a good option IMO. There's no duplication of input fields, and we can provide warnings from recOrder if something weird is going on.
Other options? I personally think consistency is most important, but maybe there are constraints I'm not thinking of. @ieivanov @mattersoflight @Soorya19Pradeep


Unable to capture screenshot in MX Linux 23.4

Title

Works if image captured via Flameshot and then pasted into Frog


In History Mode, a route containing a symbol . will be lost after refreshing

Describe the bug
In History Mode, a route containing a symbol . will be lost after refreshing the browser.
Reproduction

Create a vue project with npm create @vitejs/app.
Add vue-router with npm install vue-router@4.
Enable vue-router by using .
Change vue-router to HTML5 History Mode by adding createWebHistory(),
Set base path in vite.config.js like base:'/',
Add a new page and configure the route path, like '/page/:id'
Start the project with npm run dev
Visit the url http://localhost:3000/page/id.name through $router.push works, but direct visits raises error 404.

System Info
System: Mac OS 11.4
browser: Chrome 91.0.4472.164 (Official Build) (x86_64)
vue: 3.1.5
vue-router: 4.0.10
vite: 2.4.3

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

Checkout vite plugin https://github.com/ivesia/vite-plugin-rewrite-all
This should fix the problem (see also https://github.com/vitejs/vite/issues/2190)

This issue was hard to find. I searched for 404 and .html, or 404's with filename extension and many combinations thereof and similar.
By my adding this comment despite this being a closed topic, hopefully others will find it with those keywords.
Also, why is this not fixed with the last merge?

duplicate of #2415


Map setting dialog shows Australia.

this should reflect US base maps.

Fixed via new entries for base_maps in APSViz DB catalog_base table.
Done for dev, prod, and AWS


Why Olric, and not Redis

Thank you for olric, it looks great.
Please add to the readme:
Why should I use olric and not redis?
Thank you

Hi @guettli, thank you for your interest. I'm going to update the readme file.


🐛 [firebase_auth] SMS Verification Code Request Failed with Unknown Status Code after Firebase Upgrade

Bug report
After upgrading the Firebase packages version from the previous version to the new version, when trying to log in using Firebase on Android, I encounter the error message "SMS verification code request failed: unknown status code: 17499 Internal error encountered" in the console. Additionally, I see the error message "firebase exception: code unknown message null" in the console. However, with the test number, logging in works perfectly on both Android and iOS. I am using Flutter version 3.7.10 and Dart version 2.9.16. The Firebase packages affected by the upgrade include firebase_auth, firebase_messaging, firebase_dynamic_links, firebase_database, and firebase_crashlytics. As a result, I am unable to log in using Firebase with my own number on Android, but it works fine on iOS.
Package                          |     Old Version    |     New Version
firebase_core                  |        2.3.0            |        ^2.9.0
firebase_analytics           |        10.0.6          |        ^10.2.0
firebase_auth                  |        4.1.4            |        ^4.2.2
firebase_messaging        |        14.1.2          |       ^14.4.0
firebase_dynamic_links   |        5.0.6            |       ^5.1.0
firebase_database           |       10.0.6           |       ^10.1.0
firebase_app_check        |        0.1.1+5        |       ^0.1.2
firebase_crashlytics         |        3.0               |       ^3.1.0

@belh-sara
Can you provide both complete error logs ?
Can you also confirm if you have SHA1 and SHA256 keys aren't corrupted and are proper ?
Have you enabled device check api in console ?
Moreover, is your firebase integrated using dart initialization or manually ? https://firebase.google.com/docs/flutter/setup?platform=android

here's  the complete error logs for the issue:
[+16811 ms] I/zzh     (14720): ForceRecaptchaFlow from phoneAuthOptions = false, ForceRecaptchaFlow from firebaseSettings = false
[   +1 ms] I/PlayCore(14720): UID: [10168]  PID: [14720] IntegrityService : requestIntegrityToken(IntegrityTokenRequest{nonce=Y3QLk-c_QfY9wAMQdzMIyqvQS_tICnFB_cGzkVWL3-c, cloudProjectNumber=551503664846})
[        ] I/PlayCore(14720): UID: [10168]  PID: [14720] IntegrityService : Initiate binding to the service.
[  +15 ms] I/PlayCore(14720): UID: [10168]  PID: [14720] IntegrityService : ServiceConnectionImpl.onServiceConnected(ComponentInfo{com.android.vending/com.google.android.finsky.integrityservice.IntegrityService})
[   +1 ms] I/PlayCore(14720): UID: [10168]  PID: [14720] IntegrityService : linkToDeath
[+1485 ms] I/PlayCore(14720): UID: [10168]  PID: [14720] OnRequestIntegrityTokenCallback : onRequestIntegrityToken
[        ] I/PlayCore(14720): UID: [10168]  PID: [14720] IntegrityService : Unbind from service.
[   +4 ms] W/System  (14720): Ignoring header X-Firebase-Locale because its value was null.
[ +409 ms] E/FirebaseAuth(14720): [SmsRetrieverHelper] SMS verification code request failed: unknown status code: 17499 Internal error encountered.
[   +2 ms] D/FirebaseAuth(14720): Invoking original failure callbacks after phone verification failure for +213[my_number], error - An internal error has occurred. [ Internal error encountered. ]
[   +3 ms] I/flutter (14720): firebase exception: code unknown message null

I also checked and confirmed that my SHA1 and SHA256 are not corrupted, and the device check API is enabled in the console. However,when I discovered that the issue was with the version of the Firebase packages I was using. After some troubleshooting, I downgraded the Firebase packages version and the authentication started working again.

i have same issue..., any solution?

Facing the same issue.
###using flutter.

firebase_auth: ^4.2.2

Dev Details:

[√] Flutter (Channel stable, 3.7.5, on Microsoft Windows [Version 10.0.22621.1555], locale en-IN)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[√] Chrome - develop for the web
[√] Visual Studio - develop for Windows (Visual Studio Build Tools 2019 16.11.16)
[!] Android Studio (version 2022.1)
[√] VS Code (version 1.77.3)

Error Details:
I/zzh     ( 9857): ForceRecaptchaFlow from phoneAuthOptions = false, ForceRecaptchaFlow from firebaseSettings = false
W/System  ( 9857): Ignoring header X-Firebase-Locale because its value was null.
I/PlayCore( 9857): UID: [10238]  PID: [9857] IntegrityService : requestIntegrityToken(IntegrityTokenRequest{nonce=[token], cloudProjectNumber=[num]})
I/PlayCore( 9857): UID: [10238]  PID: [9857] IntegrityService : Initiate binding to the service.
I/PlayCore( 9857): UID: [10238]  PID: [9857] IntegrityService : ServiceConnectionImpl.onServiceConnected(ComponentInfo{com.android.vending/com.google.android.finsky.integrityservice.IntegrityService})
I/PlayCore( 9857): UID: [10238]  PID: [9857] IntegrityService : linkToDeath
I/PlayCore( 9857): UID: [10238]  PID: [9857] OnRequestIntegrityTokenCallback : onRequestIntegrityToken
W/FirebaseAuth( 9857): [FirebaseAuthFallback:] App hash will not be appended to the request.
W/FirebaseAuth( 9857): [SmsRetrieverHelper] Timeout of 0 specified; SmsRetriever will not start.
W/System  ( 9857): Ignoring header X-Firebase-Locale because its value was null.
I/PlayCore( 9857): UID: [10238]  PID: [9857] IntegrityService : Unbind from service.
E/FirebaseAuth( 9857): [SmsRetrieverHelper] SMS verification code request failed: unknown status code: 17499 Internal error encountered.
D/FirebaseAuth( 9857): Invoking original failure callbacks after phone verification failure for +91 [MOBILE_NUM], error - An internal error has occurred. [ Internal error encountered. ]

Some test:
Working fine with this conf :
cloud_firestore: 4.4.5
cloud_functions: 4.0.13
firebase_analytics: 10.1.6
firebase_app_check: 0.1.1+14
firebase_auth: 4.3.0
firebase_storage: 11.0.16
firebase_core: 2.8.0
firebase_crashlytics: 3.0.17
firebase_dynamic_links: 5.0.17
firebase_messaging: 14.3.0
firebase_performance: 0.9.0+16
firebase_remote_config: 3.0.15
Updating only firebase_core from 2.8.0 to 2.9.0 throw same issue.

@PVerniolle Thank you for your suggestion! I updated the Firebase version to the one you suggested, and it worked for me too. It seems like the problem was with the latest version of Firebase. Thanks again for your help!

I tried to replicate using plugin example running on Android with latest versions and was able to sign in properly without any issues:
User(displayName: null, email<EMAIL_ADDRESS>emailVerified: true, isAnonymous: false, metadata: UserMetadata(creationTime: 2023-02-08 10:06:58.051Z, lastSignInTime: 2023-04-13 10:57:53.098Z), phoneNumber: null, photoURL: null, providerData, [UserInfo(displayName: null, email<EMAIL_ADDRESS>phoneNumber: null, photoURL: null, providerId: password, uid: dantesttest74@gmail.com)], refreshToken: , tenantId: null, uid: YoaNWphb46ZRW4OlIgCTJTQ0Btz1)

cloud_firestore: 4.4.5
cloud_functions: 4.0.13
firebase_analytics: 10.1.6
firebase_app_check: 0.1.1+14
firebase_auth: 4.3.0
firebase_storage: 11.0.16
firebase_core: 2.8.0
firebase_crashlytics: 3.0.17
firebase_dynamic_links: 5.0.17
firebase_messaging: 14.3.0
firebase_performance: 0.9.0+16
firebase_remote_config: 3.0.15

This uses specific version of the plugins as they don't seem to have the caret (^).
I'll keep this issue open and label for team's attention.
/cc @Lyokone

Hello @darshankawar, I just wanted to clarify that the issue I'm facing is specifically with firebase_core version 2.9. I did try the suggested version that @PVerniolle provided, and it worked perfectly fine. However, when I upgraded to firebase_core version 2.9, the issue arose once again. Thank you for your help.
For reference, here are the packages versions that I am facing the issue with:
firebase_core ^2.9.0
firebase_analytics ^10.2.0
firebase_auth ^4.2.2
firebase_messaging ^14.4.0
firebase_dynamic_links ^5.1.0
firebase_database ^10.1.0
firebase_app_check ^0.1.2
firebase_crashlytics ^3.1.0

Here are the package versions that worked for me, suggested by @PVerniolle:
  firebase_core: 2.8.0
  firebase_analytics: 10.1.6
  firebase_auth: 4.3.0
  firebase_messaging: 14.3.0
  firebase_dynamic_links: 5.0.17
  firebase_database: 10.0.16
  firebase_app_check: 0.1.1+14
  firebase_crashlytics: 3.0.17

I have the same issue.

I've tried to use an older version of firebase_core and firebase_auth. It still does not work for me.
firebase_auth: 4.3.0
firebase_core: 2.8.0

Hello,
Can you try to update to the latest flutterfire_cli version, and run flutterfire configure again?

Hello,
Can you try to update to the latest flutterfire_cli version, and run flutterfire configure again?

I've tried. It's the same issue.

Likewise, my production apps with a significant number of users now have SMS login disabled for Android. This is a high-priority (P0/P1) issue. @Lyokone @darshankawar

Latest version of Firebase core supports Play Integrity: https://firebase.google.com/support/release-notes/android#auth_v21-2-0, an upgrade to FlutterFire to AppCheck is in progress (using the latest Native SDK).
Which verification provider are you using?

I'm using the latest version of the Firebase core for Android and IOS version.
For Android I changed to Play Integrity.
I'm reverting all FlutterFire plugins update, I guess the actual versions are not ready for production.

@Lyokone

Latest version of Firebase core supports Play Integrity: https://firebase.google.com/support/release-notes/android#auth_v21-2-0, an upgrade to FlutterFire to AppCheck is in progress (using the latest Native SDK).
Which verification provider are you using?
Hello,
I'm currently using phone authentication as my verification provider

I am facing the same problem on Android using firebase_auth 4.4.0 and flutter 3.7.11.
The problem is happening on production and on debug mode (with actual phone numbers and not test numbers).

I'm using the latest version of the Firebase core for Android and IOS version.
For Android I changed to Play Integrity.
I'm reverted all FlutterFire plugins update, I guess the actual versions are not ready for production.

Could you please share the working versions for you?

Some test:
Working fine with this conf :
cloud_firestore: 4.4.5 cloud_functions: 4.0.13 firebase_analytics: 10.1.6 firebase_app_check: 0.1.1+14 firebase_auth: 4.3.0 firebase_storage: 11.0.16 firebase_core: 2.8.0 firebase_crashlytics: 3.0.17 firebase_dynamic_links: 5.0.17 firebase_messaging: 14.3.0 firebase_performance: 0.9.0+16 firebase_remote_config: 3.0.15
Updating only firebase_core from 2.8.0 to 2.9.0 throw same issue.

I thought I was losing it. Can confirm these work and rolling back.

Some test:
Working fine with this conf :
cloud_firestore: 4.4.5 cloud_functions: 4.0.13 firebase_analytics: 10.1.6 firebase_app_check: 0.1.1+14 firebase_auth: 4.3.0 firebase_storage: 11.0.16 firebase_core: 2.8.0 firebase_crashlytics: 3.0.17 firebase_dynamic_links: 5.0.17 firebase_messaging: 14.3.0 firebase_performance: 0.9.0+16 firebase_remote_config: 3.0.15
Updating only firebase_core from 2.8.0 to 2.9.0 throw same issue.

I thought I was losing it. Can confirm these work and rolling back.

I've switched to these versions on firebase packages but I'm still having the issue. It's interesting.

A reverted to:
  cloud_firestore: 4.5.1
  cloud_functions: 4.1.0
  firebase_analytics: 10.2.0
  firebase_app_check: 0.1.2+1
  firebase_auth: 4.4.1
  firebase_core: 2.9.0
  firebase_crashlytics: 3.1.0
  firebase_messaging: 14.4.0
  firebase_performance: 0.9.1

I reverted to:
  cloud_firestore: 4.4.3
  cloud_functions: 4.0.11
  firebase_analytics: 10.1.4
  firebase_app_check: 0.1.1+12
  firebase_auth: 4.2.9
  firebase_core: 2.7.0
  firebase_crashlytics: 3.0.15
  firebase_messaging: 14.2.5
  firebase_performance: 0.9.0+14
  firebase_storage: 11.0.14

I reverted to:
  cloud_firestore: 4.4.3
  cloud_functions: 4.0.11
  firebase_analytics: 10.1.4
  firebase_app_check: 0.1.1+12
  firebase_auth: 4.2.9
  firebase_core: 2.7.0
  firebase_crashlytics: 3.0.15
  firebase_messaging: 14.2.5
  firebase_performance: 0.9.0+14
  firebase_storage: 11.0.14

With these, I've been able to receive the OTP once. Then, the issue started occurring again.

@SametSahin10, have you tried cleaning your files with 'flutter clean'? If you are using iOS, I recommend running 'pod repo update' and 'pod install' in the iOS folder.
Note: If you require a specific version, avoid using the "^" symbol in your pubspec.yaml file.

Yes. I've run flutter clean. Then flutter pub get. It's the same issue. I'm testing on Android.

same issue here.. sms verification failed after upgrade...   firebase auth returns "unknown" error, but then after reverting to the old version firebase auth says that my number was blocked due to many attempts (though we've only tried to login once). I'm using Flutter 3.7.11... but it worked fine after setting my package versions as stated by @PVerniolle

Hi, i have same issue with firebase_core 2.9.0.
With firebase_core 2.8.0 it works but it uses safetynet for phone authentication.
I need firebase_core 2.9.0 to migrate to play integrity.
Did anyone fixed it?

Good morning! I wanted to share an update on the issue I was having. After some research, I found that the problem was related to Play Integrity. Specifically, I realized that my old code in android/app/build.gradle contained the following:
implementation 'com.google.android.play:integrity:1.1.0'
implementation 'com.google.android.gms:play-services-safetynet:18.0.1'

To fix the issue, I replaced this code with the following:

implementation platform('com.google.firebase:firebase-bom:31.5.0')
implementation 'com.google.firebase:firebase-appcheck-playintegrity'

This solved my initial problem, but I've encountered a new issue where the reCaptcha page still pops up even though I have configured Play Integrity. I'm currently investigating this issue and will update you if I find a solution. If you have any insights or suggestions, please let me know!

Hello again! I removed my previous message because I discovered that the latest version of Firebase Auth has solved my issue. I'm now using the following package versions:
firebase_core: ^2.9.0
firebase_analytics: ^10.2.0
firebase_auth: ^4.4.1
firebase_messaging: ^14.4.0
firebase_dynamic_links: ^5.1.0
firebase_database: ^10.1.0
firebase_app_check: ^0.1.2+1
firebase_crashlytics: ^3.1.0
Thank you for your help!

I checked the operation with the same version.
firebase_core: ^2.9.0
firebase_analytics: ^10.2.0
firebase_auth: ^4.4.1
firebase_messaging: ^14.4.0
firebase_dynamic_links: ^5.1.0
firebase_database: ^10.1.0
firebase_app_check: ^0.1.2+1
firebase_crashlytics: ^3.1.0

but there is a problem.
PlayCore: UID: [10584] PID: [1641] IntegrityService : requestIntegrityToken(IntegrityTokenRequest{nonce=xxxxxxxxxxxxxxxxxx, cloudProjectNumber=xxxxxxxxxxxxxxxxxxxxxxxxxx})
PlayCore: UID: [10584] PID: [1641] IntegrityService : Initiate binding to the service.
PlayCore: UID: [10584] PID: [1641] IntegrityService : ServiceConnectionImpl.onServiceConnected(ComponentInfo{com.android.vending/com. google.android.finsky.integrityservice.IntegrityService})
PlayCore: UID: [10584] PID: [1641] IntegrityService : linkToDeath
Finsky : [265] jxl.b(23): requestIntegrityToken() finished for [package_name]
PlayCore: UID: [10578] PID: [13639] OnRequestIntegrityTokenCallback : onRequestIntegrityToken
PlayCore: UID: [10578] PID: [13639] IntegrityService : Unbind from service.

I am installing from an actual device, Google PlayStore.
Is anyone else experiencing the same problem?

I checked the operation with the same version.

Hello again! I removed my previous message because I discovered that the latest version of Firebase Auth has solved my issue. I'm now using the following package versions:
firebase_core: ^2.9.0
firebase_analytics: ^10.2.0
firebase_auth: ^4.4.1
firebase_messaging: ^14.4.0
firebase_dynamic_links: ^5.1.0
firebase_database: ^10.1.0
firebase_app_check: ^0.1.2+1
firebase_crashlytics: ^3.1.0

Thank you for your help!

but there is a problem.
PlayCore: UID: [10584] PID: [1641] IntegrityService : requestIntegrityToken(IntegrityTokenRequest{nonce=xxxxxxxxxxxxxxxxxx, cloudProjectNumber=xxxxxxxxxxxxxxxxxxxxxxxxxx})
PlayCore: UID: [10584] PID: [1641] IntegrityService : Initiate binding to the service.
PlayCore: UID: [10584] PID: [1641] IntegrityService : ServiceConnectionImpl.onServiceConnected(ComponentInfo{com.android.vending/com. google.android.finsky.integrityservice.IntegrityService})
PlayCore: UID: [10584] PID: [1641] IntegrityService : linkToDeath
Finsky : [265] jxl.b(23): requestIntegrityToken() finished for [package_name]
PlayCore: UID: [10578] PID: [13639] OnRequestIntegrityTokenCallback : onRequestIntegrityToken
PlayCore: UID: [10578] PID: [13639] IntegrityService : Unbind from service.

I am installing from an actual device, Google PlayStore. Is anyone else experiencing the same problem?

I was getting the same IntegrityService logs. The issue of not being able receive OTP SMSs has been solved without making a single change on my case.

Hi,
Is anyone still facing this issue? I have tried with all latest packages of firebase, still same issue i'm getting. It was working perfectly before updating packages. Every time in SMS verification code, browser pops up with Recaptha with these logs mentioned in issue thread.

Yes, I'm still facing the same issue as well

Hello again! I removed my previous message because I discovered that the latest version of Firebase Auth has solved my issue. I'm now using the following package versions:
firebase_core: ^2.9.0
firebase_analytics: ^10.2.0
firebase_auth: ^4.4.1
firebase_messaging: ^14.4.0
firebase_dynamic_links: ^5.1.0
firebase_database: ^10.1.0
firebase_app_check: ^0.1.2+1
firebase_crashlytics: ^3.1.0

Thank you for your help!

Hi, can you please tell us how you fixed this issue. I agree it works with old package versions of firebase , but soon they will be deprecated or won't work with new android or other package updates. So we have to use new versions. Can we please not close any issue before having proper solution, if there is any proper solution can anyone please share?

after hours of trying various things, I think I fixed the problem now (or it was resolved spontaneously, who knows…)
I did two things that may have fixed the issue:

In Play Store Developer Console -> App integrity, I removed a test that I created for debugging
At the same page -> "Device Integrity" I selected the checkboxes "MEETS_BASIC_INTEGRITY" and "MEETS_STRONG_INTEGRITY"


Load HMR on the server-side render

Why there are no hot module replacement loaded on a development web server (server-side rendering) at http://localhost:8081?
I don't see any reason not doing that. In such case port 8080 might be removed at all, so everything could be at the one place.

HMR via SSR was added in 3.0.0 today, btw - https://github.com/leebenson/reactql/releases/tag/3.0.0


Hashid which encoded by php package is not equal to the hashid which encoded by the golang pacakage

Hi:
Hashid which encoded by php package is not equal to the hashid which encoded by the golang pacakage, using the same salt and length.
The php package is  compatible with golang package？
thx

Please show us example strings. What salt, alphabet and length are you using?

Closing due to inactivity.


Added options, methods, events, and API tweaks

This PR adds a number of options and features to Swiper, along with some tweaks to the UX and API. I would have liked to have separated them out, but I don't have them separate, so they're here as one. My apologies.
New Options:

longSwipeMs - lets you configure the number of milliseconds Swiper uses to determine what a "long" swipe is versus a "short" one. Decrease if swipes are happening unintentionally, increase if it's too hard to swipe.
minSwipePx - configures the number of pixels a user must swipe to cause a page change during a short swipe. Decrease to make swiping easier, increase to make it harder.
ignoreTouchClass - if an element with this class is touched the event will be ignored, this allows elements inside a swiper to use native scrolling. Allows #684

New Events
These are available as options, just like the other events.

onReachEnd( swiper ) - when the carousel has reached the last slide
onReachBeginning( swiper ) - when the carousel has reached the first slide
onScrollEnd( event ) - fired when a scrollContainer has finished scrolling.

onScrollEndEvent = {
    isAtLeft: bool, // only for horizontal swipers
    isAtRight: bool, // only for horizontal swipers
    isAtTop: bool, // only for vertical swipers
    isAtBottom: bool, // only for vertical swipers
    direction: string 'up', 'down', 'left' or 'right'
}

Features:

swiper.lock(), swiper.lockNext(), or swiper.lockPrev() - prevent swiping in one direction, the other, or both.
swiper.unlock(), swiper.unlockNext(), or swiper.unlockPrev() - the opposite of above.
swiper.setMode( 'horizontal or vertical' )-  changes the orientation of an existing carousel.

API Changes

Adding or removing a slide before the current slide will not change the visible slide, instead the current slide will be incremented or decremented.
If there is 100% resistance and you swipe past the end (or beginning) of a carousel, touch events will bubble up to a parent Swiper.

UX Changes

The method of determining swipe speed for scroll containers has been changed to compare the oldest move event up to 150 milliseconds before the latest touch event. This prevents anomalous lightning fast or very slow tosses, and ensures that swipe-stop-release doesn't have any momentum.
Changes to the transitionTimingFunction so that it matches native Android scrolling very closely.

Bug Fixes

End swipe when the browser triggers a touchcancel event. This prevents swiper from getting stuck between slides if the browser decided the swipe should end. It is treated as if the user lifted his/her finger.
Ensure className of elements is a string before seeing if it should be ignored, as this is an object on SVG elements.

Closing as new Swiper 3 released with different API and rewritten core


FineUploader Laravel Example with AWS SDK v3

This is a Laravel port with AWS SDKv3 if anyone interested.
https://gist.github.com/n7best/6d72092e4628e75f3452

Is this something you would be willing to contribute directly to the FineUploader org, ideally as a standalone repo?

Sure, hope it could save others sometime.

I'd by happy to create a new repo and add you to the organization to maintain it.

Glad I can help. Will do a pr after repo is up. :)

I just created a repo and invited you to administer it. Sorry for the late reply to your initial post - I was out of the country in December and this must have slipped under my radar.


Validation for Whatsapp and Telegram channels

Part of this issue

Telegram bot token is checked whenever a telegram channel is added / updated
I used the phonenumbers library to parse the phone number for whatsapp channels to E.164 format, which is globally unique (https://pypi.org/project/phonenumbers/#:~:text=but you also need to specify the country that the phone number is being dialled from (unless the number is in E.164 format%2C which is globally unique). This is also the format the Turn.io and Twilio parses their numbers. The library also throws an error when the phone number is invalid.

For instance, we consider a number without a country code invalid. Phone numbers can include hashes and spaces which will be automatically removed. See the test case for some valid and invalid examples. I also fixed the extra form errors that didn't show due to a double quote issue in JS (hence we replace all double quotes with single quotes in the message)
Twilio does not support setting whatsapp webhooks programatically, only the SmsUrl, which is not the same as the whatsapp webhook URL. This thread seems to support this claim. Also, I inspected all "incoming numbers" we have and all of their sms_urls are the same (https://demo.twilio.com/welcome/sms/reply). This does not look like the correct whatsapp webhook url, so this is deffs something else.

I think we should use the phonenumberslite library since it's might lighter on memory and we don't need the additional metadata (docs)

Good call, I'll update


Attribute mode doesn't read ng-model value

If I use it in attribute mode, in other words something like:
<input type="color" spectrum-colorpicker data-ng-model="rank.color" options="{showPaletteOnly: true}" palette="colorOptions" />
... then, the control seems to ignore any value of the ng-model that is not set by itself. When the page loads, the color picker will show up as black (default color) no matter what, and it won't react to any changes in the model, and will overwrite them when the picker is opened.
However, if I use it like this:
<spectrum-colorpicker  data-ng-model="rank.color" options="{showPaletteOnly: true}" palette="colorOptions"></spectrum-colorpicker>
... then everything works fine.

Oh thats not intended. But I'll not be able to provide a fix in the near future, would appreciate a PR here

The work around is to set options.color to desired pre-selected color in the controller.


YggdrasilNetwork.Yggdrasil version 0.5.6

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installer Verification Analysis Context Information:
Installer https://github.com/yggdrasil-network/yggdrasil-go/releases/download/v0.5.6/yggdrasil-0.5.6-arm.msi
Scan request id: 'c5dfc42f-9d1c-4bd3-98cc-236c22c5dc78'

Installer https://github.com/yggdrasil-network/yggdrasil-go/releases/download/v0.5.6/yggdrasil-0.5.6-x64.msi
Scan request id: 'ea740249-c335-4753-a4a0-23a58faf3c15'
Error information: BlockingDetectionFound
Installer https://github.com/yggdrasil-network/yggdrasil-go/releases/download/v0.5.6/yggdrasil-0.5.6-x86.msi
Scan request id: 'ad2c8fc1-1098-41c7-8532-437625ca672f'
Installer https://github.com/yggdrasil-network/yggdrasil-go/releases/download/v0.5.6/yggdrasil-0.5.6-arm64.msi
(Automated response - build 885.)

This might be due to a network block of data centers, to prevent automated downloads.
(Automated response - build 885.)

This might be due to a network block of data centers, to prevent automated downloads.

For what purpose GitHub can block downloads for CI workflows running on Azure? This isn't seems logical, so I think we just need to restart checks.

/azp run

Hi @SNMetamorph,
My script matched BlockingDetectionFound in the logs and applied the message and label based on this. The scenario you describe does seem unusual, but not unheard of.

Ok, I think we should trying again until it worked

/azp run

bump

/azp run

bump


Map rotation runtime error

Bug
The server is rotating to an incorrect game mode when the map is rotated automatically.
Steps to reproduce
Chinese Titanfall2 player here.I used DeepL to help me translate this Issues so please excuse my grammatical errors.
1.I'm trying to set up a dedicated server and I'm having some map rotation issues.
2.In ns_startup_args_dedi.txt I set “+mp_gamemode” to tdm.(My server is Attrition Only so I choose Team Death Match)
3.In autoexec_ns_server.cfg I set "ns_private_match_only_host_can_change_settings" to 2 and "ns_should_return_to_lobby" to 0 in order to to avoid players modifying my server configuration in the lobby.
4.After I finished testing the server and it worked perfectly, I came back a few hours later to recheck the server and found that the game mode was incorrectly switched to "Attrition" during the auto-rotation and the scoreboard at the top of the HUD was not displaying the score properly (but the TAB still showed the number of kills for each player)

(TAB translation: Score,kills,Titan Kills,Grunts Kills)
Specifications

Northstar version:1.4.0_CN_HOTFIX
Platform: Steam(Dedicated Server on Windows Server 2019 Data Center Edition 64-bit Chinese Version)

Assuming 1.4.0_CN_HOTFIX is based on v1.4.0, that version is quite old and might already be fixed in newer versions. I'd suggest updating to the newest version of NorthtstarCN and if that still has the issue, opening a github issue on their repo. To my knowledge no one mentioned such an issue on base Northstar.


Add support for TensorFlow in official docker

Description:
Follow of #18185

Looks like we went full circle @hunterjm 😄


salt sls files with python shebangs are not properly recognized

Some salt sls files are written in python directly, I've added those interpreters in a PR here https://github.com/chriskuehl/identify/pull/60 as well as disabled the executable checks since these files are not required to be and also disabled the optimization for skipping peeking at the file contents if we recognize the extension.. I do see how this a nice speedup though.. maybe the extensions.EXTENSIONS dict should be changed from:
EXTENSIONS = {
...
'sh': {'text', 'shell'},
'sls': {'text', 'salt'},
'so': {'binary'},
...
}
to something like:
EXTENSIONS = {
...
'sh': {
'tags': {'text', 'shell'},
},
'sls': {
'tags': {'text', 'salt'},
'always-peek': True,
},
'so': {
'tags': {'binary'},
},
...
}
By changing each value to its own dict which could have an optional key always-peek(?) so then you could .get('always-peek', False) to check if the file should be inspected?

Hmm, let me fix those failing unit tests first..

Should be happy now :)


Range Bar Implementation

Checklist

[X] I am running the latest version of the card
[X] I checked if there isn't another feature request opened with the same request
[X] I checked that the feature is not already available in the dev branch

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
Implementation of Range Bar Chart
Describe alternatives you've considered
Various other forms of chart types.
Additional context
I am the author of a custom component that manages irrigation systems. Essentially there are a number of valves or zones that are programmed to operate periodically. Each zone in the system has an associated entity in HA. I would like to display the upcoming and historical run times for each zone. Think of it as an appointment planner for a team of people.
I output the data for each zone/entity in an attribute as json formatted pairs of dates. It is straight forward enough to digest this information using the data generator. Each horizontal bar/row would represent the data from one of these entities. Something like the following.

The javascript used to produce the above.
var options = {
  series: [
  {
    data: [
      {
        x: 'Zone 1',
        y: [
          new Date('2019-03-06 05:30:00').getTime(),
          new Date('2019-03-06 05:40:00').getTime()
        ]
      },
      {
        x: 'Zone 1',
        y: [
          new Date('2019-03-07 18:40:00').getTime(),
          new Date('2019-03-07 18:45:00').getTime()
        ]
      },
      {
         x: 'Zone 1',
        y: [
          new Date('2019-03-07 05:35:00').getTime(),
          new Date('2019-03-07 05:40:00').getTime()
        ]
      },
      {
        x: 'Zone 2',
        y: [
          new Date('2019-03-06 07:30:00').getTime(),
          new Date('2019-03-06 07:50:00').getTime()
        ]
      },
      {
        x: 'Zone 2',
        y: [
          new Date('2019-03-07 05:40:10').getTime(),
          new Date('2019-03-07 05:50:10').getTime()
        ]
      },
      {
        x: 'Zone 3',
        y: [
          new Date('2019-03-06 05:50:20').getTime(),
          new Date('2019-03-06 06:00:20').getTime()
        ]
      },
      {
        x: 'Zone 3',
        y: [
          new Date('2019-03-07 05:50:20').getTime(),
          new Date('2019-03-07 06:00:20').getTime()
        ]
      }
    ]
  },
],
  chart: {
  height: 450,
  type: 'rangeBar'
 },
plotOptions: {
  bar: {
    horizontal: true,
    barHeight: '80%'
  },
},
xaxis: {
  type: 'datetime'
},
 stroke: {
  width: 1
},
fill: {
  type: 'solid',
  opacity: 0.6
 },
legend: {
  position: 'top',
  horizontalAlign: 'left'
},
};

var chart = new ApexCharts(document.querySelector("#chart"), options);
chart.render();

Thank you.

For now this format is not supported, but I'll see what I can do :)

Brilliant, thank you.

I'm definitely also interested in such a graph type. Though luckily I see the existence of the candlestick feature branch. That looks similar enough for me to make it work for my use cases.


Stop shipping core languages out of the box

Related to #45663

We would like to have insiders running without core languages for at least one milestone before going to stable. If translations team is ready, we can start 1.25.insiders without core languages and ship 1.25 stable without them.

[ ] Remove core languages from the build
[ ] Remove the prompt to download core language pack. This will be taken by the recommendation that @ramya-rao-a implemented.

@danyeh Let us know if all core language packs are available in the Market place so that we can go ahead and remove core languages from insiders build

OK. I generated new builds and now the installation of the language pack is correctly proposed. For example I get:

if I start code with --locale=ru
I not want to restart the whole discussion however I still think that it might be valuable to have some English text in this notification as well. The user might not be able to speak Russian and the rest of the UI is English.

@sandy081 & @ramya-rao-a can you test the latest builds from the dbaeumer/50588 branch on Mac & Linux and let me know if they behave OK for you?

@sandy081 & @ramya-rao-a were you able to test it. I would like to merge the branch back into master after getting your OK.

Yeah, I tested the build.

Recommendation prompts are shown correctly
On install and restart VS Code is shown in UI language

@ramya-rao-a any comment regarding https://github.com/Microsoft/vscode/issues/50588#issuecomment-397627975
I will merge the PR over to master. We can still address the string issue discussed in https://github.com/Microsoft/vscode/issues/50588#issuecomment-397627975

Agreed. Lets merge it to master and release new insiders for today. We can address issues as we see.

@dbaeumer We could add the string in both languages, but then the message will become a very loooong string.
Currently, the message is something like:
VS Code is available in {0}. Please install the language pack to change the display language.
VS Code is available in {0}. Search for language packs in the Marketplace to get started.
Maybe we can shorten it to
To change the display language to {0}, please install the language pack.
To change the display language to {0}, search for language packs in the Marketplace.

I see the point but shorting it by a couple of characters will not making a big difference. Could we fold the English text?

I see the point but shorting it by a couple of characters will not making a big difference. Could we fold the English text?

It doesn't look like much of a difference in English above, but am sure, once translated there would be a noticeable difference.
What do you mean by "folding the English text"?

Is this the right place to track the changes to documentation mentioned in #45663? Or would that be tracked as a separate issue?

@dbaeumer The notification service takes only strings. So I don't see how we can twists to fold the lines.
How about this:

For languages whose language pack do not have the translation needed to show the prompt:

@sandy081 I've created a PR to remove the prompt about core language support in the future. Please take a look. #52827
With that, we can close this issue.

Closing the issue then.


Fix build

Changing the name of the executable (or so I think that is from the PyInstaller docs) makes this go through.
Anyways, this gets rid of the cryptic error reported at: https://github.com/Capsize-Games/airunner/issues/15#issuecomment-1493222382
The error: ValueError: Resource '/app/dist/airunner' is not a valid file!

thanks to your PR i realized that i had set the "exclude_binaries" flag to False which was causing the EXE step to create a binary with the same name as the collected folder in the COLLECT step. This conflict is what caused the error message - flipping this bool to True gets me past this step. I'm testing more things locally and will then push all the changes


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter daswetter for common errors and appropiate suggestions to keep this adapter up to date.
This check is based the current head revisions (master / main  branch) of the adapter repository
Please see the result of the check below.
ioBroker.daswetter
   -
ERRORS:

[ ] :heavy_exclamation_mark: [E507] missing size attributes [xs,lg,xl] for checkbox at admin/jsonConfig.json/items/MainSettings/createCurrent
[ ] :heavy_exclamation_mark: [E507] missing size attributes [xs,lg,xl] for text at admin/jsonConfig.json/items/MainSettings/Days5Forecast
[ ] :heavy_exclamation_mark: [E507] missing size attributes [xs,lg,xl] for text at admin/jsonConfig.json/items/MainSettings/Days7Forecast
[ ] :heavy_exclamation_mark: [E507] missing size attributes [xs,lg,xl] for text at admin/jsonConfig.json/items/MainSettings/HourlyForecast
[ ] :heavy_exclamation_mark: [E507] missing size attributes [xs,lg,xl] for text at admin/jsonConfig.json/items/MainSettings/HourlyForecastJSON
[ ] :heavy_exclamation_mark: [E510] responsive check: maximum issues reached, please fix reported ones and recheck

WARNINGS:

[X] :eyes: [W034] @iobroker/adapter-core 3.1.6 specified. 3.2.2 is recommended. Please consider updating dependencies at package.json

SUGGESTIONS:

[X] :pushpin: [S522] Please consider migrating to admin 5 UI (jsonConfig).

Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
Suggestions reported by repository checker should be reviewed. Suggestions can be ignored due to a decision of the developer but they are reported as a hint to use a configuration which might get required in future or at least is used be most adapters. Suggestions are always optional to follow.
You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:
@iobroker-bot recheck
or
@iobroker-bot recreate
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence
Last update at Fri, 29 Nov 2024 02:39:29 GMT based on commit<PHONE_NUMBER>0d64ea22a1ed791ae49b28395d99c6
ioBroker.repochecker 3.2.2

@iobroker-bot recheck

@ioBroker-Bot recreate


end of central directory record signature not found

VSCode Version: Code - Insiders 1.8.0-insider (6a6ab1fc5e58227b56ffc3e5bea9951e5565c314, 2016-11-24T07:05:02.837Z)
OS Version: Darwin x64 16.3.0
When install extension(visual studio keymap), then error message shows like title.

Are you behind a proxy?

I will do more test and feedback later

Looks well after turn off proxy, that's looks so strange because other things works well behind the same proxy.

Closing

I'm also seeing this behind a corporate proxy on all extensions as of today.
Version 1.8.0-insider (1.8.0-insider)
4721762a2ac1e21f1e33094e810d4888052f3d8d
2016-11-29T07:03:09.021Z
@joaomoreno I'm not seeing any network requests in the VS Code developer tools window, so I'm unsure of what might be causing this. If I break in net.js at line 729 where the call to createWriteReq() starts, I get the following data parameter on Beautify (for example - it's similar on all other extensions):
"{"id":50,"type":0,"channelName":"extensions","name":"installFromGallery","arg":[{"id":"697255a9-3f36-44c8-b084-d3b91edfb23a","name":"beautify","version":"0.6.2","date":"2016-11-28T04:23:10.43Z","displayName":"beautify","publisherId":"901b401e-7657-4a33-8c9a-0854c569607e","publisher":"HookyQR","publisherDisplayName":"HookyQR","description":"Beautify code in place for VS Code","installCount":339711,"rating":4.625,"ratingCount":24,"assets":{"manifest":"https://hookyqr.gallerycdn.vsassets.io/extensions/hookyqr/beautify/0.6.2/1480306987732/Microsoft.VisualStudio.Code.Manifest","readme":"https://hookyqr.gallerycdn.vsassets.io/extensions/hookyqr/beautify/0.6.2/1480306987732/Microsoft.VisualStudio.Services.Content.Details","download":"https://hookyqr.gallerycdn.vsassets.io/extensions/hookyqr/beautify/0.6.2/1480306987732/Microsoft.VisualStudio.Services.VSIXPackage?install=true","icon":"https://hookyqr.gallerycdn.vsassets.io/extensions/hookyqr/beautify/0.6.2/1480306987732/Microsoft.VisualStudio.Services.Icons.Default?redirect=true","iconFallback":"https://hookyqr.gallerycdn.vsassets.io/extensions/hookyqr/beautify/0.6.2/1480306987732/Microsoft.VisualStudio.Services.Icons.Default","license":"https://hookyqr.gallerycdn.vsassets.io/extensions/hookyqr/beautify/0.6.2/1480306987732/Microsoft.VisualStudio.Services.Content.License"},"properties":{"dependencies":[],"engine":"^1.6.0"}},true]}"
Opening the download URL in that parameter in my browser downloads the zip file successfully.
Also referenced this issue in https://github.com/Microsoft/vscode/issues/2384#issuecomment-263580095.

Also seeing this.
So why is this issue closed if this is still a problem and no workaround is posted?


Add 'day' as possible plan interval

Fixes #26

Hi @artemave just a reminder that I'll be happy to merge this once you add a quick test for it. Thanks!

FYI this has been moved to https://github.com/Everapps/stripe-rails/pull/79 because I had to add a spec


Error 500 on /watchers & /stars

I open project page and click to watcher or start counter. This gives me error 500 (both org/repo/watchers and  org/repo/stars)
in logs:
...routers/repo/view.go:262 renderItems()] [E] getter: pq: syntax error at or near "."

Gogs v0.7.33
DB: Postgresql 9.3.10

The same error in <IP_ADDRESS>2

Thanks your feedback!
Can you dump the xorm.log here as well?

For this gogs.log record:
2015/12/14 01:34:13 [...routers/repo/view.go:260 renderItems()] [E] getter: pq: syntax error at or near "."

attached xorm.log.txt

Thanks!
Is this a valid SQL query in PostgreSQL?
SELECT * FROM "user" LEFT JOIN "watch" ON user.id=watch.user_id WHERE repo_id=1

If not, can you help debug which part is exactly wrong? The error from pg is so disappointing...

No, this is invalid SQL.

Does
SELECT * FROM "user"  LEFT JOIN "watch" ON `user`.id=watch.user_id WHERE repo_id=1;

would work?

Nope, only double quotes allowed. And user must be doublequoted - it is keyword

Hi, can you checkout develop branch and help test?

Yes I can)

Develop branch works fine. Thank you, Unknwon!

:clap: Thanks your confirmation!

I have got the same error 500, and the same message in xorm.log. Thank you for the fix.


Style/EmptyCaseCondition creates syntax error on autocorrect when following a return

Expected behavior
I don't know. Certainly rubocop corrections should not lead to syntax errors.
Actual behavior
def foo(bar)
  return case
         when bar == 1
           2
         when bar != 12
           3
         else
           4
         end
end

is corrected to
def foo(bar)
  return if bar == 1
           2
         elsif bar != 12
           3
         else
           4
         end
end

which is a syntax error, as the "return if bar == 1" is parsed as a postfix if.
Steps to reproduce the problem
see above
RuboCop version
$ [bundle exec] rubocop -V
1.42.0 (using Parser <IP_ADDRESS>, rubocop-ast 1.24.1, running on ruby 3.1.3) +server [x86_64-linux]

I was about to create a ticket for exactly this issue. Amazing to see that it's being worked on so quickly! Thank you. :)

@koic I think that some fixes that convert ternary to if statements have a similar issue. Do you want me to create an issue for that as well? I think I can quickly provide a simple test case.

@marvinthepa Thank you! Please open an issue if you like! 😃


Create Helm chart

Before you can really use diem, we will create a helm chart that will make it much easier to install the application

already available in the helm branch, just need to finish some instructions

done in branch helm


Setup wizard problem with a custom domain pointed bucket

Tried to setup the plugin with an existing bucket on Google Cloud Storage, named specifically to use with a custom domain, but had an error: Something went wrong.
Since the error message is not clear enough, I'm assuming it must be related to bucket name. Because when I try to delete the ready bucket from the console and create it with the plugin, it tells me: A bucket name can contain lowercase alphanumeric characters, hyphens, and underscores. Bucket names must start and end with an alphanumeric character.
My bucket name is similar to this: x.example.com.
Any ideas how to fix this? Can't really find anything in the logs.
Also, wonder if there is a manual setup option available?

Hey @alikuru - can you try these manual setup instructions? https://github.com/wpCloud/wp-stateless/wiki/Manual-Setup
Let me know how that goes.
Regarding your original issue, did you use the setup assistant to create the bucket or was it already created?

It was already created. Appreciated the link, will try setting manually.

Thanks @alikuru - if you don't mind, I'd like to learn more about this issue in case there is something we can do to fix this.
In the setup assistant, did you select your existing project and see your bucket listed in the following drop down? If so, did you select it? When did the Something went wrong. message appear?
Thanks!

I've selected my existing project and the bucket I'd like to use did appear in the drop-down. I chose it and hit continue. Something went wrong message appeared between the account information and the Google Cloud Project label.

Manual setup worked, thanks again for the help.

@ewsopp @alimuzzaman We show Something went wrong message on all failures during Setup Wizard process.
I think, for better troubleshooting we should include Error Code or some more details about the particular error.
E.g.:  Something went wrong. Error Code: 12345. Please ask UsabilityDynamics, Inc support for help.. Where 12345 code belongs to fail response on insertBucketAccessControls step.

@pemaxim In this particular case, I think our bucket name rules were being applied to an existing bucket. Since the bucket already exists, we don't need to apply those rules.


trailing whitespaces

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
@ksatchit @dargasudarshan please review.

@vijaysinghrawat1 Seems like duplicate PR.


Quartz ScheduleMessageJob takes down process when destination unroutable

Hi, we're using mass transit with Quartz and RabbitMQ.
We've got some garbage data in quartz caused by both developer's local machines and the dev environment pointing at the same quartz db. After upgrading from 3.1.2 we started noticing that unroutable destination addresses on messages coming off quartz were taking down the service.
I've tracked this to OnCacheItemRemoved/CleanupCacheItem in LazyMemoryCache. It looks like on the second attempt to grab the send endpoint for the bad address LazyMemoryCache sees that Task.IsFaulted is set and triggers a removal.
The removal callback then attempts to await the faulted task on a threadpool thread that is never joined, causing the service shutdown.
Wrapping CleanupCacheItem in a try/catch and swallowing the exception seems to have fixed the issue for us, but i'm not sure if there is something more correct to do. Any thoughts? I'd be happy to submit a pull request.

A pull request would be great, that's a good find. Faulted Tasks can be nasty when they're cached.

Fixed by #628 I believe.

Yes indeed, Thanks!


"Load data values" from multiple files but no overlay

Hi,
trying to solve the following problem: I want to create a vars.yml file (in order to deploy something with bosh with a templated manifest) and the variables in vars.yml come from different sources, e.g. environment specific settings like proxy, dns and output from terraform.
So I would like to use the "Load data values" feature but with multiple input files. Currently if i do so it triggers the overlay mechanism which complains if the input from different files have different keys. Is there a way to circumvent this?

ytt: Error: Overlaying data values (in following order: proxy.yml, dns.yml):
  Document on line dns.yml:2:
    Map item (key 'de') on line dns.yml:3:
      Expected number of matched nodes to be 1, but was 0

Hi, @damzog,
Because ytt needs to be able to support more complex merging behavior, it currently works by treating the first data values file as a base values file and then applying additional data values as overlays. Data values inputs follow the same ordering as overlays referenced here. This means you're not able to circumvent this behavior, but it allows you to use annotations to specify the merge behavior. In order to accomplish what you're trying you can use the #@overlay/match missing_ok=True annotation in your additional data values files. Here's an example of what that would look like.
Feel free to reach out if this doesn't solve your use case.

as a shortcut there is also a way to specify missing_ok=True fro the entire document:
#@data/values
#@overlay/match-child-defaults missing_ok=True
---
some_new_key: true

additionally we are planning to add first-class data values schemas (https://github.com/k14s/ytt/tree/develop/proposals/001-schemas) which in this case would allow multiple schemas to be be merged (assuming there is no conflicting instructions). then you wouldnt have add annotations to let ytt know that this is a new wanted key (a side effect of data values being used to specify and define data values).
finally, we recommend ytt templates to specify all data values used within templates in the base data values (even if there is no clear default). this acts as a way to "define" data values expected. example: https://github.com/cloudfoundry/cf-for-k8s/blob/master/config/values.yml. in most cases when this is done, you no longer have to worry about adding annotations to add new keys down the road.

closing, feel free to reopen or ping us on slack.


Dark mode's icon

Description
Currently the icon for an app can only be set to one, this will default to one icon for both light and dark mode, some icons (for example AFFiNE - from selfh.st's icon) are black and setting a light icon for dark mode and vice versa makes the interface unsightly.

Priority
Low (Nice-to-have)

Hi, icons should be visible in both dark and light modes. If this is not the case, the author of the icons should reconsider their colors. Most icons will be colorful by default for this exact reason. The additional complexity in Homarr is not worth the change.
As a workaround, you could...

Recolor the icon yourself
Ask the author to color differently
Use custom CSS (https://homarr.dev/docs/advanced/customizations/board-customization#custom-css) to manually override.

Side note, Homarr V1 supports a monochrome library of icons that you can color the way you want, straight in the URL.
If you're willing to test it out for us, join the early adopters on discord :)


TypeError: page.setUserAgent is not a function

Trying to run Codecept Tests with Playwright but get a warn log at the start of every test.
TypeError: page.setUserAgent is not a function
at codeceptjs-npm-3.0.7-bcb1d4968c-220cced1f6.zip/node_modules/codeceptjs/lib/helper/Playwright.js:615:26
Details

CodeceptJS version: 3.0.7
NodeJS Version: 14.13.1
Operating System: Mac Mojave
Playwright 1.10.0

Same here, Seems like dependency Injection does not work:
Scenario('Some test', async ({ I, App }) => {
  App.common.commonChat.chat()
});

Cannot read property 'commonChat' of undefined

Actually, there is no setUserAgent method in Playwright. You have to create a new context with the userAgent property to accomplish it (e.g. const context = await browser.newContext({userAgent: 'foo'});).
Read more about the issue
Perhaps, it was added by copy and paste mistake, because Puppeteer has this method.

Yeah thats what I mean, theres an issue in the codecept code itself as its calling page.setUserAgent in the Playwright file


reimplemented simplifyStrings for speed and correct behavior

I found another performance bottle neck in FACTORIE in the cc.factorie.app.strings.simplifyDigits method.  In one configuration, the profiler was showing that 12% of the CPU sampling was taking place in that method executing "findFirstIn".  So, I re-implemented the method using a more direct approach with string/character examination.  Also, I believe the logic of the original implementation is incorrect.  The value returned by simplfiyDigits("A1") is "" but I would expect it to be "A#".  I don't think it is possible for the third condition to be invoked based on the way the second one works.  This pull request adds a faster implementation of simplifyDigits and unit tests that capture what I think the exptected behavior should be.  The unit tests do not pass with the regex version of the method.  I didn't see any change in accuracy of the NER model I built with this change.
After making this fix, a process that once took 205 seconds now takes about 195 seconds and the time spent doing findFirstIn went from 12.4% to 5.2%.  I didn't track down where else the findFirstIn method was being called from.

Hi, thanks for the PR! Looks good to me aside from some style issues -- I'd be happy to accept if those are fixed (also, we use 2 spaces for indentation). I marked some of them but the rest should be obvious.

You are welcome.  Please format as you see fit.

In general, the author of the pull request should fix the formatting and other small issues found during code review. I'll be happy to merge the PR if you make those changes.

I have committed the various formatting changes requested.  After my first commit I realized that there were a few tabs still lurking in the contributed code and so the second commit removes the ones I noticed - hopefully everything is compliant now.

Thanks!


support error codes and user friendly errors on api response

Summary
Need to add support for application specific error codes and user friendly error responses in api responses.
For example:
We send the below error response when the grant cannot be renewed yet.
err: failed to create appeal: checking grant extension eligibility: existing grant is not eligible for extension
This error is just the system errors propagated through the stack and sent as API response on create appeal flow. Instead of this, if the api response would have been something like you already have access to this resource. you cannot extend it yet (as example) would have been more user friendly and readable without knowing the guardian domain knowledge.
Additional Context
the actual system errors can be in logs, but the api responses can be more readable. This can be achieved through by catching all errors at the handler level and sending back simplified error back as api response.

let's create a mapper of each error -> meaningful message in the handler layer?


sync with Atreidae branch

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

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

Checklist:

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

i dont know what im doing :D tried to sync changes you made to my branch


Theme uses apple store icon for marketplace

Provide a description of the new feature
Ok, so this is a Microsoft Fluent design system inspired theme... And yet you use the Apple store icon for the marketplace. Also, it just looks bad as the icon doesnt represent what the actual tab is for. Some better options could be a basket icon or some other icon to represent a market place and not the apple app store.
Additional Information
No response

Excuse my rudeness but this is something you definitely deserve IMO.
Why not open a PR for a "better" icon or link one here instead of just complaining about it? It's been that way for years and there was not a single person to complain. Also, the Spicetify Marketplace is the store for, well, Spicetify add-ons and themes. Isn't it normal for there to be a store icon instead of just a basket or something?
Again, contributions are welcome. Even the icons are pretty easy to find if you know how things are commonly organized throughout the websites (if you still can't figure out where, it's right in assets/fluentui-system-icons/ as vector drawable, named ic_fluent_app_store_24_*.svg). Just fork this repo, replace the icon in an editor like InkScape, change the references in code if you change the filename and you're done.
Oh, even better yet, why don't we ask the actual one who committed the icon, @TheChilledBuffalo, about this? I'm sure you can figure out that this person was the one who committed this if you just check the Git history of the file.
Sigh...enough ranting. If you really want an enhancement about this, go find some actual resources and/or references we can look at.
Thank you.

I'm sorry, @stel-bl , just some clarification, but how am I involved here? I didn't submit the App Store icons lol. My commits were the statistics, better local files and better library icons. And those icons were taken directly from microsoft's fluent icon library here on github: https://github.com/microsoft/fluentui-system-icons

And also, @Eatham532 , the App Store icons were also taken from Microsoft's own library of fluent icons: https://github.com/microsoft/fluentui-system-icons/blob/d32cd7114b430cbdcce2c354e5fa010566a2582b/assets/App Store/SVG/ic_fluent_app_store_24_filled.svg?plain=1
They have absolutely no issues providing assets of something of their "competitor" and it does seem like the an appropriate choice for Marketplace. So uhm... what's your deal?

I'm sorry, @stel-bl , just some clarification, but how am I involved here? I didn't submit the App Store icons lol. My commits were the statistics, better local files and better library icons. And those icons were taken directly from microsoft's fluent icon library here on github: https://github.com/microsoft/fluentui-system-icons

Pfft sorry @TheChilledBuffalo, I read the log incorrectly. Now checking it again and it seems to have been committed by someone without a GitHub account linked to the committer credentials (lemonbigbig<EMAIL_ADDRESS>- https://github.com/nimsandu/spicetify-bloom/commit/b97ea1ceba97f283d8df2582e707e0e191558a23). Guess I let my anger take over to the point I oversaw that. :sweat:

Lol ok...
I just never liked it because I was used to the normal marketplace icon. And seeing an Appstore icon on windows gave me weird vibes like I was on a mobile device.
Maybe instead of the AppStore icon use the Apps icon: https://github.com/microsoft/fluentui-system-icons/tree/d32cd7114b430cbdcce2c354e5fa010566a2582b/assets/Apps
Or the apps add in one: https://github.com/microsoft/fluentui-system-icons/tree/d32cd7114b430cbdcce2c354e5fa010566a2582b/assets/Apps Add In
The shopping bag could also work: https://github.com/microsoft/fluentui-system-icons/tree/d32cd7114b430cbdcce2c354e5fa010566a2582b/assets/Shopping Bag
Sorry for nitpicking. This theme is one of my favorites so I was just trying to help with the few things I don't really like.

Lol ok... I just never liked it because I was used to the normal marketplace icon. And seeing an Appstore icon on windows gave me weird vibes like I was on a mobile device.

Fair enough, it's alright.

Maybe instead of the AppStore icon use the Apps icon: https://github.com/microsoft/fluentui-system-icons/tree/d32cd7114b430cbdcce2c354e5fa010566a2582b/assets/Apps
Or the apps add in one: https://github.com/microsoft/fluentui-system-icons/tree/d32cd7114b430cbdcce2c354e5fa010566a2582b/assets/Apps Add In

This one looks far better IMHO. Good find!

The shopping bag could also work: https://github.com/microsoft/fluentui-system-icons/tree/d32cd7114b430cbdcce2c354e5fa010566a2582b/assets/Shopping Bag

Nah this looks way too out of place TBH. But yeah, the apps add-in one is a good find, I think we should give that one a try.

Sorry for nitpicking. This theme is one of my favorites so I was just trying to help with the few things I think could be improved. If you don't like the ideas there then that's ok. Don't feel like you have to follow through with my suggestions just because I have a different opinion to you.

Again, it's alright. I was mad because of the overhead I've been having trying to deal with the users that don't give a reference for the bug/suggestion. You're good, I'm sorry for my reaction.

No problem

I was mad because of the overhead I've been having trying to deal with the users that don't give a reference for the bug/suggestion.

Lol I understand. Those people can be so frustrating.


Stats do not update

After crafting a new item and placing it into my character equipment it does not update my defensive stats under character sheet.

Yeah, crafted items still do not appy to the character even in pre-release version.

Connected to #199


Fix home dir for www-data user

Fix image build after merging #17

Thank you so much @ihor-sviziev! Much appreciated.


fix: use timezones that allow the test to always be passing

This fixes #310 using Pacific/Tongatapu (UTC+13) and Pacific/Midway (UTC-11) timezones => always 24 hours of difference

thank you @jdambron


Able to assign a change request to a user without permission to view change requests

Currently, the list of assignees when creating a change request includes all members of an organisation. This can include users that do not have permission to view change requests in a given environment.
This causes an issue in that, when a user without permission, is assigned to a change request, they are sent an email notification but are unable to view the change request as they do not have permission, resulting in a slightly strange behaviour for that user.
There are a couple of solutions that we can develop here to fix the immediate issue:

The list of possible assignees should only include those that have permission to approve that change request. This would be very difficult to achieve with the current permissions model.
When the change request is created, it should review the list of assignees and make sure that they each have permission to approve the change request and only assign / send notifications to those that do have permission.

An alternative solution here, which perhaps would be developed in conjunction with item (2) above, is to allow users to assign change requests to a group of users rather than individual users. This would simplify the UX for larger teams.

@novakzaballa as discussed this morning, the behaviour that I'm expecting to see on the detail view of a change request, depending on the two flags is as follows:
users_as_reviewers disabled, groups_as_reviewers disabled

No 'Assignees' sections are shown for either.

users_as_reviewers enabled, groups_as_reviewers disabled

Assigned users section shown. If there are no users already assigned, just show the add users button. Add users button is always shown at the end of the list of any users that are already assigned.
Assigned groups section not shown at all (even if there are groups assigned)

users_as_reviewers disabled, groups_as_reviewers enabled

Assigned groups section shown. If there are no groups already assigned, just show the add groups button. Add groups button is always shown at the end of the list of any groups that are already assigned.
Assigned groups section not shown at all (even if there are groups assigned)

users_as_reviewers enabled, groups_as_reviewers enabled

Assigned users section shown. If there are no users already assigned, just show the add users button. Add users button is always shown at the end of the list of any users that are already assigned.
Assigned groups section shown. If there are no groups already assigned, just show the add groups button. Add groups button is always shown at the end of the list of any groups that are already assigned.

@matthewelwell got it, I will make the changes in that sense. Please notice that with this behavior, in case a client had the users (or groups) flag enabled and disable it, then the client will not be able to see or remove the assign users (or groups).

@matthewelwell got it, I will make the changes in that sense. Please notice that with this behavior, in case a client had the users (or groups) flag enabled and disable it, then the client will not be able to see or remove the assign users (or groups).

Yep, understood. That is fine.

@matthewelwell should we close this and create a new issue?

@matthewelwell should we close this and create a new issue?

I think we can just leave this one open and update the description? I will do that.


visible flag causes issues when repositioning visible=false DOCs

I have a thread open at http://www.html5gamedevs.com/topic/12076-documentobjectcontainervisible-false-causing-odd-behavior/
The DOCs don't update their position properly when setting the visible flag to false (or possibly, they "jump" when setting it to true, I can't tell really what's happening)
Here is a demo page of the problem in action. http://monsterisland.chimeracompanygames.com/secure/landing/PIXITestForForums
Click, drag and mousewheel(zoom) on that image to see how it'll occasionally jump (always after moving your mouse and then scaling after having been scaled previously) when swapping visibility between the 3 DOCs.
Here's why I think it's a bug and not my code. If I change the visible = false or true properties to alpha = 0 or 1, everything works as I intend for it to.
Here's a live example of using alpha instead of visible. http://monsterisland.chimeracompanygames.com/secure/landing/PIXITestForForumsWithAlpha
Click, drag and zoom on that page and notice how it never "jumps".
Thank you.

Setting visible = fase makes the updateTransform function (which updates the position among other things) not run. That is by design. Alpha does not do this, it just changes whether it is drawn.
In v3 we added back in the renderable property which will act like you are expecting. It prevents drawing but continue to update the object.

Yeah, sorry about the code being so complex. It was a idea sketchpad that I copied into jsfiddle. Way too ununkempt.
You say "so if you change position then set visible back to true then it will update to the correct position before renderering"
but just before it you say  "Setting visible = fase makes the updateTransform function (which updates the position among other things) not run."
How can it update the positioning if setting visible = false turns off positioning updates?
Can you further explain what you mean?

I think you misread what I said:

if you change position then set visible back to true it will update to the correct position before renderering

updateTransform is called, then the rendering is called. So if you change it back to true it will call the updateTransform funciton first then render.

Setting visible = fase makes the updateTransform function (which updates the position among other things) not run.

This isn't permanent, while visible is false, that function doesn't run. When you change it back, it runs.

I think I understand where my brain was having the hiccup.
I was having trouble separating the setting of the position property from the actual updating of the image on the screen.
The property can be set at any time, but when updateTransform is called by the render function it ignores something that has the visible = false flag. But when you set the flag to true, the next time updateTransform is called it will apply the new position property values.
So, if it updates to the correct position before rendering, then why does it seem to update to the wrong spot, when switching to using alpha 0 or 1 does not? That's literally the only change I make and it works as I would expect the visible flag to.
That's the big unknown for me still.
I don't have the time to try and make a more simple version of my jsfiddle for easier troubleshooting, but I'll try and make one if I can't come up with another solution.
If I don't adjust the visible property and just leave all 3 DOCs in my example visible at all times, there's no "jumping" either.
This is why I'm concerned that it has something to do with the visible property and how it acts.
Thanks.

Like I said I'm not sure, but the example you give isn't specific enough to debug the issues you describe. If you can build a small test case I'd be happy to look into it more.

ok, I'll see what I can do

Closing this since there has been no activity. If you get a case that shows this behavior then I'll reopen it.


Homebridge stops working after installing the update

Hi,
Homebridge is shutting down after installing the update:
[Homebridge] [5/14/2020, 08:47:17] Error: The requested platform "BlinkSecurityPlatform" was not registered by any plugin.
at API.platform (/usr/local/lib/node_modules/@hoobs/hoobs/lib/bridge/api.js:132:19)
at Server._loadPlatforms (/usr/local/lib/node_modules/@hoobs/hoobs/lib/bridge/server.js:289:47)
at Server.run (/usr/local/lib/node_modules/@hoobs/hoobs/lib/bridge/server.js:93:14)
at module.exports (/usr/local/lib/node_modules/@hoobs/hoobs/lib/bridge/cli.js:74:12)
at Object. (/usr/local/lib/node_modules/@hoobs/hoobs/lib/bridge/bin/homebridge:27:59)
at Module._compile (internal/modules/cjs/loader.js:959:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10)
at Module.load (internal/modules/cjs/loader.js:815:32)
at Function.Module._load (internal/modules/cjs/loader.js:727:14)
at Function.Module.runMain (internal/modules/cjs/loader.js:1047:10)
at internal/main/run_main_module.js:17:11[Homebridge] [5/14/2020, 08:47:17] Got SIGTERM, shutting down Homebridge...

I had to change the platform to "BlinkCameras". Also, don't forget to add the new required parameters for 2-factor authentication. Example:
    {
        "platform": "BlinkCameras",
        "name": "Blink System",
        "username"<EMAIL_ADDRESS>        "password": "secret password",
        "deviceId": "unique device id, can be anything",
        "deviceName": "homebridge",
        "discovery": true
    }

That's it. Thanks!


[CONS-6540] Better look for image name in podman DB

What does this PR do?

Motivation
Fix cases where the agent couldn’t find the container image name with podman.
Additional Notes
In the customer support case, the image_name tag missing from all data and wasn’t even visible in workload meta.
An analysis of the podman DB showed that the RawImageName field where the agent was looking at was empty:
sqlite3 -readonly /var/lib/containers/storage/db.sql 'SELECT ContainerConfig.JSON FROM ContainerConfig;' | jq .RawImageName
null
null
null
null
[…]

Yet, the podman CLI was able to find the image name of the containers from the same DB file:
podman ps --format '{{ .ID }}' | while read -r ctr; do sudo podman inspect "$ctr" | jq '.[] | .ImageName'; done
"docker.io/moby/buildkit:buildx-stable-1"
"docker.io/library/redis:6.0.5"
"docker.io/minio/minio:RELEASE.2023-01-20T02-05-44Z"
"docker.io/library/mysql:8.0.26"
[…]

And the only field where those image names could be found in the podman DB is in the rootfsImageName field:
sqlite3 -readonly /tmp/db.sql 'SELECT ContainerConfig.JSON FROM ContainerConfig;' | jq | grep docker.io
  "rootfsImageName": "docker.io/moby/buildkit:buildx-stable-1",
  "rootfsImageName": "docker.io/library/redis:6.0.5",
  "rootfsImageName": "docker.io/minio/minio:RELEASE.2023-01-20T02-05-44Z",
  "rootfsImageName": "docker.io/library/mysql:8.0.26",
[…]

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


SimpleRouteLocator prefix problem

The prefix of the Route always contains the global prefix when not empty, not related to 'StripPrefix'.
But the path of the Route(in the code is targetPath) controlled by StripPrefix.
https://github.com/spring-cloud/spring-cloud-netflix/blob/c8c4dbd0503b66353e82dc72ca2cdc74b7476634/spring-cloud-netflix-zuul/src/main/java/org/springframework/cloud/netflix/zuul/filters/SimpleRouteLocator.java#L140-L155
Route use path  and prefix create fullPath
https://github.com/spring-cloud/spring-cloud-netflix/blob/c8c4dbd0503b66353e82dc72ca2cdc74b7476634/spring-cloud-netflix-zuul/src/main/java/org/springframework/cloud/netflix/zuul/filters/Route.java#L27-L42
This will be a problem.
If I am correct, i think LocationRewriteFilter have some prefix problem too.
https://github.com/spring-cloud/spring-cloud-netflix/blob/c8c4dbd0503b66353e82dc72ca2cdc74b7476634/spring-cloud-netflix-zuul/src/main/java/org/springframework/cloud/netflix/zuul/filters/post/LocationRewriteFilter.java#L115-L135
route from RouteLocator, so the prefix maybe contains any prefix of global prefix or route prefix.
If i use global prefix and route prefix, and enable 'StripPrefix' both,
downstreamHasRoutePrefix(route) is false and the path will be global prefix + global prefix + route prefix.

Can you provide a sample that will demonstrate the problem?

@ryanjbaxter sample in here https://github.com/xiaoyao9184/spring-cloud-expansion/tree/master/samples/zuul-redirect/zuul-redirect-issue


[FEATURE REQUEST] Allow toggling shadow casting per entry

Describe the problem you're trying to solve in your project
It's sometimes advisable to disable shadow casting when placing a lot of small grass instances that are too small to cast meaningful shadows. It's currently not possible to disable that on a per entry basis.
Describe a feature you consider and how it will help you
It would be helpful to have an additional toggle to change the shadow casting mode in the property panel for each entry.
Describe alternatives you've considered
One possible alternative is to create a custom shader-material which has shadow casting disabled as render mode. The problem is that this then applies to all targets using this material, meaning it would require creating extra custom materials for imported scenes just to have them also be renderable with shadows disabled. And it's more steps involved when later deciding to scale up the painted grass instances and wanting them to then cast shadows again.
Describe how you imagine it would work. With code, pseudo-code, diagram or a drawing
The toggle would simply copy its state to the resulting multimesh's https://docs.godotengine.org/en/stable/classes/class_geometryinstance.html#class-geometryinstance-property-cast-shadow property

Edited and merged your suggestion with #21
Thanks!


Error: Method not found: 'GoogleAuthProvider.getCredential'

The problem
I'm learning Flutter and trying to create an app with Google sign in. But I get this output is VS Code:
Launching lib/main.dart on iPhone 12 Pro Max in debug mode...
lib/main.dart:1
Xcode build done.                                           27.1s
Failed to build iOS app
Error output from Xcode build:
↳
    ** BUILD FAILED **
Xcode's output:
↳
    lib/auth.dart:11:56: Error: Method not found: 'GoogleAuthProvider.getCredential'.
      final AuthCredential credential = GoogleAuthProvider.getCredential(
                                                           ^^^^^^^^^^^^^
    lib/auth.dart:19:53: Error: 'currentUser' isn't a function or method and can't be invoked.
      final User currentUser = await _fbAuth.currentUser();
                                                        ^^^^...
    Command PhaseScriptExecution failed with a nonzero exit code
    note: Using new build system
    note: Building targets in parallel
    note: Planning build
    note: Constructing build description
    warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.1.99. (in target 'AppAuth' from project 'Pods')
    warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.1.99. (in target 'GTMAppAuth' from project 'Pods')
    warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.1.99. (in target 'google_sign_in' from project 'Pods')
    warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.1.99. (in target 'Flutter' from project 'Pods')
    warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 14.1.99. (in target 'GoogleSignIn' from project 'Pods')
Could not build the application for the simulator.
Error launching application on iPhone 12 Pro Max.
Exited (sigterm)

Steps to Reproduce

Run flutter create bug.
Update the files as follows:
Add Firebase to the app and enable Google sign in
Update the lib folder: lib_folder.zip
Update the assets folder: assets_folder.zip
Update the pubspec.yaml file (I've removed the comments):

name: bug
description: A new Flutter project.
publish_to: 'none'
version: 1.0.0+1

environment:
  sdk: ">=2.7.0 <3.0.0"

dependencies:
  flutter:
    sdk: flutter
  cupertino_icons: ^1.0.0
  firebase_auth: ^0.20.0+1
  firebase_core: ^0.7.0
  google_sign_in: ^4.5.9

dev_dependencies:
  flutter_test:
    sdk: flutter

flutter:

  uses-material-design: true
  assets:
    - assets/

Expected results:
I wanted to see a "Sign in with Google" button that brings up the Google sign in page.
Actual results:
I got an error while building the app.
Logs
flutter-run-verbose.log

# output of "flutter analyze"
Analyzing learning_app...

  error • The method 'getCredential' isn't defined for the type 'GoogleAuthProvider' • lib/auth.dart:11:56 • undefined_method
  error • The expression doesn't evaluate to a function, so it can't be invoked • lib/auth.dart:19:34 • invocation_of_non_function_expression
   info • Unused import: 'post.dart' • lib/login.dart:5:8 • unused_import

# output of "flutter doctor -v"
[✓] Flutter (Channel stable, 1.22.6, on Mac OS X 10.15.7 19H512 darwin-x64, locale en-US)
    • Flutter version 1.22.6 at /Users/user/AppDependencies/flutter
    • Framework revision 9b2d32b605 (2 weeks ago), 2021-01-22 14:36:39 -0800
    • Engine revision 2f0af37152
    • Dart version 2.10.5

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/user/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.1, Build version 12A7403
    • CocoaPods version 1.10.1

[!] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.53.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.19.0

[✓] Connected device (1 available)
    • iPhone 12 Pro Max (mobile) • EFDE6DB3-4511-4D88-AB75-AC43706CE6D1 • ios • com.apple.CoreSimulator.SimRuntime.iOS-14-1 (simulator)

! Doctor found issues in 1 category.

Also, there's another issue I've been facing. I've installed the Flutter and Dart plugins in Android Studio, but the Flutter CLI isn't able to detect it.

Check the latest documentation. In flutter fire website https://firebase.flutter.dev/docs/auth/social#google
To get the current user is not async anymore.  User user = FirebaseAuth.instance.currentUser;
To login check this code fragment.
Future<UserCredential> signInWithGoogle() async {
  // Trigger the authentication flow
  final GoogleSignInAccount googleUser = await GoogleSignIn().signIn();

  // Obtain the auth details from the request
  final GoogleSignInAuthentication googleAuth = await googleUser.authentication;

  // Create a new credential
  final GoogleAuthCredential credential = GoogleAuthProvider.credential(
    accessToken: googleAuth.accessToken,
    idToken: googleAuth.idToken,
  );

  // Once signed in, return the UserCredential
  return await FirebaseAuth.instance.signInWithCredential(credential);
}

Thanks, I was wondering if it was different in the new version but I didn't know where to find the documentation.

I updated auth.dart to look like this:
import 'package:firebase_auth/firebase_auth.dart';
import 'package:google_sign_in/google_sign_in.dart';

final FirebaseAuth _fbAuth = FirebaseAuth.instance;
final GoogleSignIn _googleSignIn = GoogleSignIn();

Future<User> signInWithGoogle() async {
  // Trigger the authentication flow
  final GoogleSignInAccount googleUser = await _googleSignIn.signIn();

  // Obtain the auth details from the request
  final GoogleSignInAuthentication googleAuth = await googleUser.authentication;

  // Create a new credential
  final GoogleAuthCredential credential = GoogleAuthProvider.credential(
    accessToken: googleAuth.accessToken,
    idToken: googleAuth.idToken,
  );
  final UserCredential authResult =
      await _fbAuth.signInWithCredential(credential);
  final User user = authResult.user;
  assert(!user.isAnonymous);
  assert(await user.getIdToken() != null);
  final User currentUser = _fbAuth.currentUser;
  assert(currentUser.uid == user.uid);
  return user;
}

// final GoogleSignInAccount googleSignInAccount = await _googleSignIn.signIn();
// final GoogleSignInAuthentication googleSignInAuthentication =
//     await googleSignInAccount.authentication;
// final AuthCredential credential = GoogleAuthProvider.getCredential(
//     idToken: googleSignInAuthentication.idToken,
//     accessToken: googleSignInAuthentication.accessToken);
// final UserCredential authResult =
//     await _fbAuth.signInWithCredential(credential);
// final User user = authResult.user;
// assert(!user.isAnonymous);
// assert(await user.getIdToken() != null);
// final User currentUser = await _fbAuth.currentUser();
// assert(currentUser.uid == user.uid);
// return user;

And now my app crashes when I click the "Sign in with Google" button: https://user-images.githubusercontent.com/66139317/107186684-5668d600-69aa-11eb-8ed7-f276355a343b.mov

@Python3-8
Since you are using google_sign_in + firebase_auth, then, you'll need to raise this issue in firebase dedicated repo : https://github.com/FirebaseExtended/flutterfire/issues.
Closing from here.


LeWrapper is unsound

Several unsafe zerocopy traits are implemented unconditionally for LeWrapper, without any guarantee that the contents of the wrapper actually fulfils the requirements of these traits. Safe code somewhere else could implement VmediaType for some arbitrary type which isn't safe to convert to bytes (e.g. because it has padding), wrap an instance of the type in LeWrapper and then convert it to bytes with not unsafe block. This allows undefined behaviour in safe code, so is unsound.
The best solution is for LeWrapper<T> to only implement zerocopy traits if T implements the corresponding trait. This may require a change to v4l2r to implement the required traits on its bindgen-generated types. Alternatively VmediaType could be made an unsafe trait, with a safety requirement corresponding to those of the various zerocopy traits. Then it is up to the implementer of VmediaType to guarantee the requirements.

Yeah I'm really not happy about LeWrapper. I think making it unsafe is probably the easiest solution short-term. I'd prefer v4l2r types to derive the adequate zerocopy traits directly, but that would impose a specific version of zerocopy that its users might not be ready to use (e.g. 0.8 vs 0.7)...

I think you'll need to make VmediaType unsafe, as LeWrapper is a struct not a trait.


Proposal: Add support for conditionals in Single, Maybe and Completable

At the moment there are methods for handling if else checks and switch statements in Observable and Flowable. These checks can also be useful when handling Singles, Maybes and Completables.

Closing via #26.


5.0 release.json doesn't contain 5.0.7

Description
Note sure if this is the right place to put this issue or not, but the 5.0 specific releases.json on windows.net doesn't have 5.0.7 listed in it even though both the releases-index.json and 5.0 specific releases.json files in this repo do.

@rbhanda @leecow can you check this? I don't know how the windows.net location gets updated.

The file has been corrected.

Thanks @kalaskarsanket. Closing the issue then.