performance  bug

    implementation 'com.google.android.gms:play-services-base:15.0.1'
    implementation 'com.google.android.gms:play-services-maps:15.0.1'
    implementation 'com.google.android.gms:play-services-analytics:16.0.1'
    implementation 'com.google.firebase:firebase-core:16.0.1'
    implementation 'com.google.firebase:firebase-messaging:17.1.0'
    implementation 'com.google.firebase:firebase-crash:16.0.1'
    implementation 'com.google.firebase:firebase-perf:16.0.0'
    implementation 'com.google.android.gms:play-services-tagmanager:16.0.1'

my app met some mistakes about perf
1:
Exception java.lang.NullPointerException: Attempt to invoke virtual method 'boolean com.google.android.gms.internal.firebase-perf.zzq.zzb(com.google.android.gms.internal.firebase-perf.zzah)' on a null object reference
com.google.android.gms.internal.firebase-perf.zzg.zza ()
com.google.android.gms.internal.firebase-perf.zzg.zzb ()
com.google.android.gms.internal.firebase-perf.zzg.zza ()
com.google.android.gms.internal.firebase-perf.zzj.run ()
java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1113)
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:588)
java.lang.Thread.run (Thread.java:818)

2:
Exception java.lang.RuntimeException: Package manager has died
android.app.ApplicationPackageManager.getPackageInfo (ApplicationPackageManager.java:142)
com.google.android.gms.internal.firebase-perf.zzg.zzd ()
com.google.android.gms.internal.firebase-perf.zzg.zzp ()
com.google.android.gms.internal.firebase-perf.zzg.zzb ()
com.google.android.gms.internal.firebase-perf.zzh.run ()
java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1113)
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:588)
java.lang.Thread.run (Thread.java:818)

3:
Exception java.lang.NullPointerException: Null pointer exception during instruction 'monitor-enter v10'
android.os.Parcel.readException (Parcel.java:1620)
android.os.Parcel.readException (Parcel.java:1567)
android.app.ActivityManagerProxy.getContentProvider (ActivityManagerNative.java:3770)
android.app.ActivityThread.acquireProvider (ActivityThread.java:5249)
android.app.ContextImpl$ApplicationContentResolver.acquireUnstableProvider (ContextImpl.java:2138)
android.content.ContentResolver.acquireUnstableProvider (ContentResolver.java:1517)
android.content.ContentResolver.query (ContentResolver.java:482)
android.content.ContentResolver.query (ContentResolver.java:441)
com.google.android.gms.internal.firebase-perf.zza.zza ()
com.google.android.gms.internal.firebase-perf.zzq.<init> ()
com.google.android.gms.internal.firebase-perf.zzg.zzp ()
com.google.android.gms.internal.firebase-perf.zzg.zzb ()

@LiuDongCai apologies for the slow response, a few of us were on vacation.
Are you seeing this on your own device or just in customer crash reports?  Do you know what behavior causes any of these exceptions to happen?

Just in customer crash reports.
And I don't know how to reappear.But it has appeared many times.

I also have this happening in customer crash reports.
Devices:
1- Infinix - multiple models (Android 7.0)
2- TECNO - multiple models (Android 7.0)
Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean com.google.android.gms.internal.firebase-perf.zzq.zzb(com.google.android.gms.internal.firebase-perf.zzah)' on a null object reference
at com.google.android.gms.internal.firebase-perf.zzg.zza(Unknown Source)
at com.google.android.gms.internal.firebase-perf.zzg.zzb(Unknown Source)
at com.google.android.gms.internal.firebase-perf.zzg.zza(Unknown Source)
at com.google.android.gms.internal.firebase-perf.zzi.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:761)

Thanks everybody.  I don't have a good way to reproduce this myself right now but I have shown this thread to the Firebase Performance SDK team and I hope they can help dig into it.

java.lang.RuntimeException: android.os.DeadSystemException
at android.app.ActivityThread.acquireProvider(ActivityThread.java:5828)
at android.app.ContextImpl$ApplicationContentResolver.acquireUnstableProvider(ContextImpl.java:2434)
at android.content.ContentResolver.acquireUnstableProvider(ContentResolver.java:1554)
at android.content.ContentResolver.query(ContentResolver.java:525)
at android.content.ContentResolver.query(ContentResolver.java:476)
at com.google.android.gms.internal.clearcut.zzab.zzi(Unknown Source)
at com.google.android.gms.internal.clearcut.zzab.zzg(Unknown Source)
at com.google.android.gms.internal.clearcut.zzaf.zzp(Unknown Source)
at com.google.android.gms.internal.clearcut.zzae.zza(Unknown Source)
at com.google.android.gms.internal.clearcut.zzae.zzl(Unknown Source)
at com.google.android.gms.internal.clearcut.zzae.get(Unknown Source)
at com.google.android.gms.internal.clearcut.zzp.zza(Unknown Source)
at com.google.android.gms.clearcut.ClearcutLogger$LogEventBuilder.log(Unknown Source)
at com.google.android.gms.internal.firebase-perf.zzg.zza(Unknown Source)
at com.google.android.gms.internal.firebase-perf.zzg.zzb(Unknown Source)
at com.google.android.gms.internal.firebase-perf.zzg.zza(Unknown Source)
at com.google.android.gms.internal.firebase-perf.zzj.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:776)
Caused by: android.os.DeadSystemException

@samtstern
implementation 'com.google.firebase:firebase-perf:16.0.0'
It reproduce on phones without Play Services

@samtstern
targetSdkVersion  27

java.lang.NoClassDefFoundError: com.google.android.gms.common.internal.zzbq
at com.google.firebase.perf.provider.FirebasePerfProvider.attachInfo(Unknown Source)
at android.app.ActivityThread.installProvider(ActivityThread.java:4819)
at android.app.ActivityThread.installContentProviders(ActivityThread.java:4432)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4372)
at android.app.ActivityThread.access$1300(ActivityThread.java:141)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1294)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:5041)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
at dalvik.system.NativeStart.main(Native Method)

I believe this is the same as #536, which I was able to reproduce and we are now investigating.  Closing...

@samtstern
I think the recent release 16.1.0 fixed #536.
But didn't fix this. I am still having similar error report in crashlytics.
Seems the source of the problems are different.

We're also still getting these crashes. It looks like the Firebase Performance team is looking into it and updating things on this Stackoverflow thread.

@lognaturel I see you have an open source project which was experiencing the NoClassDefFoundError - would you potentially be able to share the released APK that you were seeing crashes on?
Like I mentioned on the StackOverflow question, I suspect this issue has to do with some of the FirebasePerformance classes not being in the main dex - and being able to analyze an APK on which you were seeing the crashes would be super useful!

@lognaturel Nvm, found the apk on your github page :) Thanks!

Thanks for looking into it, @tejasd and @seventhmoon! Do you have a consistent way to repro? Is there a way for us to verify that the fix does in fact work other than pushing to production and seeing if one of our users happens to get a crash? If not, we'll need to at least wait until the next beta before trying it out.

I'm also seeing this problem, from a customer crash report:
Session summary
2.237 (237)
9
TECNO SPARK 4 Air
Mar 13, 2020, 7:58:00 PM
Stack trace
Keys
Logs
Data
Device
Brand: TECNO MOBILE LIMITED
Model: TECNO SPARK 4 Air
Orientation: Portrait
RAM free: 535.73 MB
Disk free: 10.16 GB
Operating System
Version: 9
Orientation: Portrait
Rooted: No
Fatal Exception: java.lang.NullPointerException
Attempt to invoke virtual method 'void com.google.firebase.perf.internal.zzv.zzc(boolean)' on a null object reference
com.google.firebase.perf.internal.zzf.zzd (com.google.firebase:firebase-perf@@19.0.5:170)
com.google.firebase.perf.internal.zzi.run (com.google.firebase:firebase-perf@@19.0.5:2)
java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1167)
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:641)
java.lang.Thread.run (Thread.java:764)
pool-17-thread-3
com.crashlytics.android.core.CrashlyticsController.handleUncaughtException
com.crashlytics.android.core.CrashlyticsController$6.onUncaughtException (CrashlyticsController.java:301)
com.crashlytics.android.core.CrashlyticsUncaughtExceptionHandler.uncaughtException (CrashlyticsUncaughtExceptionHandler.java:42)
java.lang.ThreadGroup.uncaughtException (ThreadGroup.java:1068)
java.lang.Thread.dispatchUncaughtException (Thread.java:1955)

We're also seeing this issue come up from time to time in crashlytics, last two devices were

Samsung Galaxy S8+
Oppo AX7 (CPH1903)

We're using com.google.firebase:firebase-perf:19.0.7.
Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method 'void com.google.firebase.perf.internal.v.a(boolean)' on a null object reference
       at com.google.firebase.perf.internal.zzf.zzd(zzf.java:170)
       at com.google.firebase.perf.internal.zzi.run(zzi.java:2)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
       at java.lang.Thread.run(Thread.java:764)

Please re-open..

@tomblenz @fractalbob Thanks for your report! I've forwarded this to the folks currently taking care of this - but AFAICT these seem to be new bugs and so might be worth opening a new issue!

Thanks @tejasd for keeping an eye on this one.  Also to everyone: if you are experiencing bugs in the Firebase Android SDK please file those on the firebase-android-sdk repo.  We try to keep this repo for quickstart issues only.


fix(server): remove un-necessary listener

Types of changes

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

Description

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[ ] All new and existing tests are passing.

Codecov Report

Merging #9245 (3cecf38) into dev (c56d484) will increase coverage by 0.03%.
The diff coverage is 100.00%.

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

@@            Coverage Diff             @@
##              dev    #9245      +/-   ##
==========================================
+ Coverage   65.13%   65.16%   +0.03%
==========================================
  Files          94       94
  Lines        4101     4105       +4
  Branches     1124     1124
==========================================
+ Hits         2671     2675       +4
  Misses       1152     1152
  Partials      278      278

Flag
Coverage Δ

unittests
65.16% <100.00%> (+0.03%)
:arrow_up:

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

Impacted Files
Coverage Δ

packages/server/src/listener.js
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Expose heroTag of the FloatingActionButton inner widget.

The reason is that it will produce exception  in case this widget (or FloatingActionButton) is reused within the navigation stack with a default heroTag value

Thanks for pointing it out. Will look into it. 👍🏼

Thanks @arnold-parge! I appreciate


Allow for decorator chaining when a decorator modifies the kwargs

I've got a decorator that adds an additional kwarg to a function and have been using this with the default discord.py framework. This decorator helps integrate django with discord.py by using the user id in the context to fetch the user object from the django database. However, due to the code shown here:
https://github.com/EQUENOS/dislash.py/blob/6aa5f28c6c43799d9af089a2b98cf61affb978f7/dislash/slash_commands/slash_core.py#L365-L374
That kwarg never actually reaches the function.
Would it be possible to add support for additional custom kwargs by exposing all additional kwargs to the command function?

I'll add custom kwargs support in the nearest patch, thank you for sharing this issue

Additional custom kwargs are now supported in dislash.py v1.2.3


Enable stylecheck linter

Correct the variable and package names to be
compatible with stylecheck recommendations.
Signed-off-by: Janki Chhatbar<EMAIL_ADDRESS>

No more comments on my side, just what @tpantelis said & agreeing with "kubeproxy" instead of kubeproxyiptables, but that's a nit :-P :D


[CGP-376] Blockchain event triggers in wallet API

it's ready to review but I'm going to rebase onto master to get the nix change in

I feel like this is missing some helpful description :)

Also, the address of a pay-to-script output is now the hash of its validator script only

Is this a change to the extended UTxO model?

Is this a change to the extended UTxO model?

Yes I think it is (There is no precise definition of "address" in the docs though). I should probably include @mchakravarty as well

Seems like there is a loop now. Odd!

Yes I think it is (There is no precise definition of "address" in the docs though). I should probably include @mchakravarty as well
(EDIT: The change we are talking about here is from address = hash(validatorscript + datascript) to address = hash(validatorscript) for a pay-to-script output. Source

Hmm, maybe I haven't made this sufficiently clear in the extended UTxO page, but the new situation (address = hash of validator script alone) is exactly what I had in mind.

I'd suggest to clearly document this as a simplification of the mockchain for now and revisit the issue after PlutusFest.
(...)
another trigger predicate that we need is one that results in a notification when a specific transaction is validated

OK I'll add/implement those two

in some cases, will probably also want to be able to wait for the confirmation of a transaction submitted by another wallet (Not so sure about that, but it seems like this is something you'll want to be able to do. What do you think?)

It would be easy to do if we have the hash of the transaction, but that feature is only slightly different from being able to watch an address. The hash also includes things like the coin selection, so it would be a very specific condition to wait for (are you thinking about another wallet of the same user, or of a different user?) And that information would be relevant only for a small period of time, namely between submitting the transaction to the chain, and receiving the confirmation. An address seems a bit more long-lived. But it's probably best to just implement it and then see if people are using it.
Also, regarding the question of how far we should go back to start watching an address. Maybe we could assume that a light wallet holds on a (configurable) number of recently validated blocks. Because a block is an exact unit of time we would be able to say that we can cover the last 24 hours or something. That would give uses some more time to set up the triggers, and its cost would be constant (not proportional to the chain size). I'm assuming that some amount of blocks has to be kept around because of rollbacks in any case.

@j-mueller

in some cases, will probably also want to be able to wait for the confirmation of a transaction submitted by another wallet (Not so sure about that, but it seems like this is something you'll want to be able to do. What do you think?)

It would be easy to do if we have the hash of the transaction, but that feature is only slightly different from being able to watch an address. The hash also includes things like the coin selection, so it would be a very specific condition to wait for (are you thinking about another wallet of the same user, or of a different user?) And that information would be relevant only for a small period of time, namely between submitting the transaction to the chain, and receiving the confirmation. An address seems a bit more long-lived. But it's probably best to just implement it and then see if people are using it.

As far as coordination code is concerned, it cannot be sure that a given transaction gets validated at all. Somebody else might spend an output that the transaction wants to consume before that transaction gets confirmed. Hence, before you can do anything that depends on a transaction being on the chain, you will need for that transactions confirmation (just submitting it isn't safe as a pre-condition).
I think, I do understand now, why you earlier used script hash + data hash as a script address. Then, you can wait for that to appear in the UTxO set as fairly close a proxy for a transaction being confirmed. With script addresses being the validator address only, you can wait for payments to the validator, but that may be in the form of a range of transactions.
In any case, I am pretty sure, we need the ability to, say, wait with doing a particular action until see you see a specific transaction. If it is a transaction you submit yourself (i.e., being submitted by the wallet the contract runs in), I don't think, it matters that this includes coin selection etc.
(We really need to say what are the most convenient conditions to wait for by exploring a range of contracts.)

Also, regarding the question of how far we should go back to start watching an address. Maybe we could assume that a light wallet holds on a (configurable) number of recently validated blocks. Because a block is an exact unit of time we would be able to say that we can cover the last 24 hours or something. That would give uses some more time to set up the triggers, and its cost would be constant (not proportional to the chain size). I'm assuming that some amount of blocks has to be kept around because of rollbacks in any case.

If a transaction gets submitted and a trigger installed right after, there is no danger, as transaction validation is not instantaneous. Cardano produces a block (at most) every 20sec. I am sure, there'll be buffering etc, but I don't think, we need to worry about that now.
I think, for now, the most important thing is to explore what are the blockchain conditions that contracts generally want to wait for. We'll call the PlutusFest version of the wallet API a pre-release and fix the specific API after we got some feedback from users and our own exploration.


Add pre-configured test container for MongoDB

Is your feature request related to a problem? Please describe.
I started working on my personal project that is using multiple different databases and I'm using dotnet-testcontainers for more convenient way of testing. However as there's no pre-configured test container of MongoDB, I decided to write it for my own purposes, but as well I can also share it.
Describe the solution you'd like
I would like to see a pre-configured test container of MongoDB as is for other databases like Oracle, MySQL etc.
Additional context
Here's link to the branch from my fork as a potential PR: link

👍 I'll take a look at it next week or the week after.

Your changes look good, thanks. I would prefer to provide modules in separate dependencies to support more module specific functions, but we do not have the infrastructure yet.
A PR is more than welcome! Thanks, again.


Add explicit Weights and Biases support

changes in readme.md and default examples/7b.yml file for more explicit wandb variable use

Also a more explcit name for lora weights, like we discussed! ;)


Microsoft /AL: Business Central: "The Item Ledger Entry does not exist. Identification fields and values: Entry No.='0'"

"The Item Ledger Entry does not exist. Identification fields and values: Entry No.='0'" error message when you post a sales invoice with drop shipment where some sales lines have item tracking and others not.
We noticed that in NAV2018 we had the same error. This is fixed in NAV2018 CU6. When can we expect this to be fixed in Business Central?
267926
COD 90

If this is fixed in a CU then it should be available in the next release of Business Central in Fall.
Note that this repo should only be used for AL development related issues and not for regular application bugs.


⚠ Bofrost.es has degraded performance

In 894d5ae, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1764 ms

Resolved: Bofrost.es performance has improved in 879041c after 20 minutes.


Refactor schedule management responsibilities into a single class

Right now, BreaksPlanner plans the next break, but executing that break is handled by code in main.js. This means the 'what state are we in?' logic is split between these two files, with a complex interaction bouncing between them through interval timers.
In #93, I integrated the idle time break skipping into BreaksPlanner, but this solution feels somewhat hacky.
I think it might help to have a single schedule management object that is responsible for all aspects of planning both the start and the ends of breaks, as well as monitoring idle time for natural breaks. It can be an EventEmitter and use events to tell the UI to show/hide the break window, update break progress bars, etc. It can also serve as a single source of information about the current state of the break timings (simplifying the solution to #63), in addition to cleaning up my solution to #59. It would further make it easier to use the idle time detection logic to make the 'in a break' timer only tick down when you're actually stopping use of the computer, like Workrave.
This object may also benefit from a defined state machine to record different states, but I haven't thought enough about what the state machine would look like to have a good handle on how useful it would be.

Hi, I totally agree. To be honest, stretchly is learning exercise of nodejs/JS for me. I wanted to create single object responsible for everything you mentioned, but I did not/do not have knowledge of how to do it node way. Basically, I hoped one day stretchly would get some attention and someone would come and critique my code and help me learn something. So I am glad you started this issue.
Eg, right now I am doing constructor (settings, microbreakFunc, breakFunc)which I am not sure it's good or bad.
I am not familiar with EvenEmmiters but if you could write simple pseudo code of how you imagine it could work, that would be great. I guess more people with experience can comment.

Glad to help!
Life is made easier since you're using ES6 classes :). You can write:
class BreakManager extends EventEmitter {
}

The EventEmitter base class takes care of all the event handler management for you. So then code in the break manager can write:
this.emit('start-break');
this.emit('break-progress-update', {total: 300000, elapsed: 102383})

And other code can write:
manager.on('start-break', () => {
    // show the break window
});

I personally think it would be a better separation of concerns if the manager is responsible for starting and stopping the break on its own, and all the event handlers do is show/hide windows, instead of having the 'start-break' listener arrange for the next break to be scheduled.

For the sake of other people and me reminding myself, here is how it's working now:

Scheduler - takes in function and delay and basically calling setTimeout when doingscheduler.plan()
BreaksPlanner - takes care of planning next break (figuring out what kind of break it should be based on settings) and returns Scheduler (also skipping to micro/break, pause, resume, reset)

some functions returns Scheduler, some already plan it, which is bad
also creates status message for tray

main.js

when app starts, we create breakPlanner and plan first break
when break starts, we create timer to finish it, which when called, is asking breakPlanner to plan next break

On this topic, I wanted to inquire, I'm a little confused why the scheduler has the plan function in the first place. I know in some spots you call nextBreak and then check that the result was not null before calling plan, but I don't really see what that accomplishes. Every instance of that happening is basically like
let nb = breakPlanner.nextBreak()
if (nb)
    nb.plan()
    //other logic

I think that the setTimeout call could just occur in the constructor for Scheduler, and then there would be less risk of forgetting to actually call plan, like happened with the bug with the reset function that I fixed. The other logic that relies on nextbreak not being null can still happen, it would just get reduced to
let nb = breakPlanner.nextBreak()
if (nb) //nb != null means setTimeout already occurred
    //other logic

With a break scheduler/planner/manager responsible for everything, there's yet another design that would be my go-to that doesn't even require Scheduler, and makes the break manager more like a state machine.
Basically, have a method BreakManager.update() that runs periodically and does a few things:

Get current idle time (if enabled)
See if we need to transition states (start or stop a break, update progress, cancel a break because of idle, etc.)
Activate state transition
Figure out how long to wait until the next update is need (if idle time is enabled, should be e.g. 5s to check idle again)
Schedule its next invocation

@sxmanton plan was to have BreaksScheduler only schedule breaks, do not actually create timers. When I created it, I wasn't sure what would be the node way to talk between processes/objects and so on, so I did it the way I did it. I agree it could be simplified, I hope we gonna find some good consensus here.
@mdekstrand that could be interesting as well. Maybe we can try different approaches and make PR to see if its good idea? I didn't have time yet to check how Events works, but I plan to find some. I hope to refactor break scheduling before working on other features.

Guys, feel free to check changes I made and comment.

Had a quick skim over and it looked pretty good to me. I can try to review more thoroughly sometime, although also I think @mdekstrand has a better understanding of event emitter architecture, so mostly will defer to his thoughts on this one.


Google Cloud deployment SSH not working

Sorry if this is an obvious question - I'm new to gcloud and am pretty baffled by it.
I've got SSH set up on my computer (OSX), using gcloud tool. Now I can SSH into my instance from Terminal just fine. But the mupx deployment script can't get SSH access to the Google Cloud instance.
The gcloud auto-generated SSH key is stored here:
~/.ssh/google_compute_engine
So in my mup.json config file, I've done this:
"servers": [
  {
    "host": "XXX.XXX.XXX.XXX",
    "username"<EMAIL_ADDRESS>    "pem": "~/.ssh/google_compute_engine",
    "env": {}
  }
],

But can't deploy. I get this error:
Error: All configured authentication methods failed
at tryNextAuth (/usr/local/lib/node_modules/mup/node_modules/nodemiral/node_modules/ssh2/lib/client.js:290:17)
at SSH2Stream.onUSERAUTH_FAILURE (/usr/local/lib/node_modules/mup/node_modules/nodemiral/node_modules/ssh2/lib/client.js:469:5)
at SSH2Stream.EventEmitter.emit (events.js:98:17)
at parsePacket (/usr/local/lib/node_modules/mup/node_modules/nodemiral/node_modules/ssh2/node_modules/ssh2-streams/lib/ssh.js:3649:10)
at SSH2Stream._transform (/usr/local/lib/node_modules/mup/node_modules/nodemiral/node_modules/ssh2/node_modules/ssh2-streams/lib/ssh.js:555:13)
at SSH2Stream.Transform._read [as __read] (_stream_transform.js:179:10)
at SSH2Stream._read (/usr/local/lib/node_modules/mup/node_modules/nodemiral/node_modules/ssh2/node_modules/ssh2-streams/lib/ssh.js:213:15)
at SSH2Stream.Transform._write (_stream_transform.js:167:12)
at doWrite (_stream_writable.js:226:10)
at writeOrBuffer (_stream_writable.js:216:5)

Is there some other configuration I need to do with mupx or with Google Cloud? I should be using my Google email address that I use to login to Google Cloud, right?

With gcloud, you need to put the IP address, pem file since we don't
support OS level hostfile config.
For the username, you need to set the server's username. Not your gcloud
login.
On Wed, Jul 1, 2015 at 7:27 AM dkmooers<EMAIL_ADDRESS>wrote:

Sorry if this is an obvious question - I'm new to gcloud and am pretty
baffled by it.
I've got SSH set up on my computer (OSX), using gcloud tool. Now I can SSH
into my instance from Terminal just fine. But the mupx deployment script
can't get SSH access to the Google Cloud instance.
The gcloud auto-generated SSH key is stored here:
~/.ssh/google_compute_engine
So in my mup.json config file, I've done this:
"servers": [
{
"host": "XXX.XXX.XXX.XXX",
"username"<EMAIL_ADDRESS>"pem": "~/.ssh/google_compute_engine",
"env": {}
}
],
But can't deploy. I get this error:
Error: All configured authentication methods failed
at tryNextAuth (/usr/local/lib/node_modules/mup/node_modules/nodemiral/node_modules/ssh2/lib/client.js:290:17)
at SSH2Stream.onUSERAUTH_FAILURE (/usr/local/lib/node_modules/mup/node_modules/nodemiral/node_modules/ssh2/lib/client.js:469:5)
at SSH2Stream.EventEmitter.emit (events.js:98:17)
at parsePacket (/usr/local/lib/node_modules/mup/node_modules/nodemiral/node_modules/ssh2/node_modules/ssh2-streams/lib/ssh.js:3649:10)
at SSH2Stream._transform (/usr/local/lib/node_modules/mup/node_modules/nodemiral/node_modules/ssh2/node_modules/ssh2-streams/lib/ssh.js:555:13)
at SSH2Stream.Transform._read [as __read] (_stream_transform.js:179:10)
at SSH2Stream._read (/usr/local/lib/node_modules/mup/node_modules/nodemiral/node_modules/ssh2/node_modules/ssh2-streams/lib/ssh.js:213:15)
at SSH2Stream.Transform._write (_stream_transform.js:167:12)
at doWrite (_stream_writable.js:226:10)
at writeOrBuffer (_stream_writable.js:216:5)
Is there some other configuration I need to do with mupx or with Google
Cloud? I should be using my Google email address that I use to login to
Google Cloud, right?
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/507.

Got it, thanks! Changed the username to my local computer username, as per this article:
https://cloud.google.com/compute/docs/instances/

USER
[Required] The username to log in that instance. Typically, this is the username of the local user running gcloud compute.

In other case, you can also add SSH keys directly to the instance via
metadata.
Then, server's username is the username.
On Wed, Jul 1, 2015 at 9:03 AM dkmooers<EMAIL_ADDRESS>wrote:

Got it, thanks! Changed the username to my local computer username, as per
this article:
https://cloud.google.com/compute/docs/instances/
USER
[Required] The username to log in that instance. Typically, this is the
username of the local user running gcloud compute.
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/507#issuecomment-117425031.

You mean then the server's username is my Google Cloud account login? (I'm not aware of any other username attached to the server)

Hey Im very new to google cloud and I was wondering if I could get some help with the authentication so I can use meteor-up? I see the issue is closed so sorry If Im violating some protocol. Thanks.

Hmm. .. the link above is good. Leads to this one too.
https://cloud.google.com/compute/docs/instances/managing-ssh-keys
It has a getting started guide...
https://cloud.google.com/compute/docs/quickstart
Are you using gcloud or ssh?
By default you should be able to SSH.
Try to get it so you can SSH from the local dev machine to your target instance. Report back with progress or potential issues and/or questions, thanks.
We also like to know more about your situation to be able to provide help.
Everything from your mup settings to "DEBUG =* mupx deploy" logs, OS type & versions for node, etc.
Also I like ti ask if you're having trouble with mup to try mupx but at this point we are only concerned with you SSH and less about mup(x). That's next let's just clarify your SSH connection.

I tried using both, I was able to use ssh locally from cloud console but not from my machine or through gcloud. Gonna work on this again today for now I was able to deploy to a linode and host the db on compose.


Example in README not working

Hey @VictorDenisov im playing around with this library but havent grasped Conduits and Monad transformers yet.
I do not know if listUsers is missing or how to use it.
Thanks in advance!

I need to look into this. It's been sometime since I worked on it. Maybe it's outdated already. I'll let you know once I find this out.

@triblix The line you want to use is:
l <- rz $ getUsers $$ CL.consume

I'll update the readme file shortly.

Done.


bandage 0.8.0

[x] Commit message includes cask’s name (and new version, if applicable).
[x] brew cask audit --download {{cask_file}} is error-free.
[ ] brew cask style --fix {{cask_file}} left no offenses.

❯❯❯ brew cask style bandage
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/specification.rb:2007:in `raise_if_conflicts': Unable to activate rubocop-cask-0.5.0, because rubocop-0.39.0 conflicts with rubocop (~> 0.37.0) (Gem::LoadError)
	from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/specification.rb:1176:in `activate'

https://github.com/caskroom/homebrew-cask/issues/20806 is the issue related to rubocop

Also, check out cask-repair, it makes Cask updates like this quite easy (details in CONTRIBUTING)

Thanks!


fix!: Allow ignoring 50001 during sync

About
This pull request is about (X), which does (Y).
Checklist

[x] I've ran pre-commit to format and lint the change(s) made.
[ ] I've checked to make sure the change(s) work on 3.8.6 and higher.
[ ] This fixes/solves an Issue.

(If existent):

[ ] I've made this pull request for/as: (check all that apply)

[ ] Documentation
[ ] Breaking change
[ ] New feature/enhancement
[x] Bugfix

This pull request is about (X), which does (Y).

This pull request is about (X), which does (Y).

Removing it breaks astro afaik, but the title explains it... but ok, I'll change it


Invalid content /en/shelley/resources/community/

Where does the issue occur?
Link to the file or location on the website where the issue occurs. Optionally add screenshots for context.
This issue occurs in two links in the community resources page on the Cardano Testnets page.
Describe the issue
A clear and concise description of what the issue is.
The first issue is the link "Create your own Cardano Haskell node" is a broken link. The second issue is the link under "Testnet stake pool tutorials" is a link that links to bigpey's tutorial playlist. Well this is bigpey and he updated these tutorials for all of the new CLI changes. These tutorials are also much more concise and will help new pool operators more.
Expected changes
A clear and concise description of what you expected to change.
Please fix the first broken link that I mentioned. But most importantly update the link with this link "https://www.youtube.com/playlist?list=PLyThQPJpttTJ4r9wUdlWi1DMty4nAT85d", I would also appreciate it if that text was "bigpey's testnet stakepool videos".
Additional context
Add any other context about the problem here.

thank you for your feedback, we are resolving this issue, thank you.

this has been fixed.


DRAFT: Dead letter implementations

It might be a little hard to see WriteExceptionHandler is all we really need to add to fit all the use cases.
This PR should demonstrate how you should be able to fit the most common usecases within the WriteExceptionHandler framework.
I want to write out the original byte array to a dead-letter-table
In theory (i.e. NOT definitively proven yet) ...
For the usecase of writing out the original Kafka key/value byte arrays, we have to do a little bit of work:
- My idea here would be to write a Converter/SMT which preserves the original key/value byte arrays somewhere.
- I'm thinking in the SinkRecord's key or the SinkRecord's headers or SinkRecords schemas parameters
- This SinkRecord is passed to the SinkTask.put method
- When an exception is thrown, our WriteExceptionHandler.handle method would pull out the key/value byte arrays from the SinkRecord's parameters/headers/key and return a new SinkRecord with those values
- The connector would then write that new SinkRecord to the dead-letter table
Importantly, what I'm trying to avoid is having special record structure that the connector code needs to understand in order to do the right thing. The ideal situation for me is the connector is oblivious to "good" and "dead-letter-records-from-Converter/SMT-failures."
I want to write out the original JSON to the dead-letter-table
Same approach as above
I want to capture deserialization/SMT failures somehere!
Two options:

Use kafka-connect's built-in DLQ
Use dynamic-tables mode + an SMT that on error produces a SinkRecord destined for your dead-letter-table (see sample implementation in this PR)

I want to capture null records somewhere!
Two options:

Use kafka-connect's built-in DLQ by throwing a NullRecordException :D
Use dynamic-tables mode + an SMT that for null records produces a SinkRecord destined for your null-records table

I don't want to write bad records to Iceberg, I want to write to Kafka!
See KafkaDLQ for a sample implementation.

@tabmatfournier the other PR just FYI

Importantly, what I'm trying to avoid is having special record structure that the connector code needs to understand in order to do the right thing. The ideal situation for me is the connector is oblivious to "good" and "dead-letter-records-from-Converter/SMT-failures."

TBH you are still doing this, you're just changing the shape of what the special record is.

I'm thinking in the SinkRecord's key or the SinkRecord's headers or SinkRecords schemas parameters

Not this simple.
SinkRecord's key:

the key may be null, a string, a json, a struct, a map, or some other value.  You would have to overwrite the key and assume no one is using it downstream
SinkRecord may not have a schema (it's possible it's a Map for instance, in which case the schema is null).

Headers are probably the best bet but least nice to work with.  This is why I went for the custom struct approach.  Either way you are writing some custom code that knows how to dig this out of the record, and putting that into the connector.  In my approach this was determined by a config option --not using dead letter/error transform? nothing goes looking for this (no runtime cost).

The connector has to know about dead-letter-records-from-converter during failure in order to dig out the original bytes.

The connector code doesn't need to know.
The WriteExceptionHandler code will need to know.

SinkRecord may not have a schema (it's possible it's a Map for instance, in which case the schema is null). Even if it does have a schema, the parameters are a Map<String, String> so you have have to base64 encode your bytes in order to put them in (and decode them out later) if you wanted to do this.

Let's definitely not use schema parameters then lol (that's why I had it last in the list)

You would have to overwrite the key and assume no one is using it downstream if you want to use the key.

Yea absolutely, but I thought the idea with the ExceptionHandlingTransform was it would be the one and only SMT involved (it can run user supplied SMTs internally). So there would be no downstream (other than SinkTask.put obviously)?
Even with your approach, if another SMT is involved downstream of the ExceptionHandlingTransform, it could break things, no?

Headers are probably the best bet but least nice to work with.

I would prefer key for that reason personally.

In my approach this was determined by a config option --not using dead letter/error transform? nothing goes looking for this (no runtime cost).

This approach should also have no runtime cost if you're not using a WriteExceptionHandler.
(The code will use the MultiTableWriter instead of wrapping that in an ExceptionHandlingTableWriter if no WriteExceptionHandler is supplied).


Create example python file for both Bi-SQUID and SQUID

We provide a script file for DC Bi-SQUID in example folder, but we don't have for DC SQUID, we should improve our example folder.


chore(splitbutton): add storybook stories & template

Description

How and where has this been tested?

How this was tested:
Browser(s) and OS(s) this was tested with:

Screenshots

To-do list

[ ] If my change impacts other components, I have tested to make sure they don't break.
[ ] If my change impacts documentation, I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have tested these changes in Windows High Contrast mode.

[ ] This pull request is ready to merge.

@pfulton One quick note - it doesn't seem like the size control is working?


After updating to 0.8.1-RC1 Elastic search turned into init state .

Description

upgrading of my openebs-0.8.0 cluster to 0.8.1-RC1 facing error :
pod status after updating volume :
`logging              elasticsearch-logging-0                                           0/1       Init:0/1           0          2h
`

Current Behavior

After Cstor_volume_Upgrade every volume and workloads are working fine expect elestic search .

pod Describe :
Events:
  Type     Reason       Age                From                                                      Message
  ----     ------       ----               ----                                                      -------
  Warning  FailedMount  10m (x21 over 1h)  kubelet, gke-workload-openebs-default-pool-cb15d787-hcb2  MountVolume.WaitForAttach failed for volume "pvc-4941f9c2-f5bc-11e8-ba31-42010af00275" : failed to get any path for iscsi disk, last err seen:
iscsi: failed to attach disk: Error: iscsiadm: Could not login to [iface: default, target: iqn.2016-09.com.openebs.cstor:pvc-4941f9c2-f5bc-11e8-ba31-42010af00275, portal: <IP_ADDRESS>,3260].
iscsiadm: initiator reported error (8 - connection timed out)
iscsiadm: Could not log into all portals
Logging in to [iface: default, target: iqn.2016-09.com.openebs.cstor:pvc-4941f9c2-f5bc-11e8-ba31-42010af00275, portal: <IP_ADDRESS>,3260] (multiple)
 (exit status 8)
  Warning  FailedMount  59s (x40 over 1h)  kubelet, gke-workload-openebs-default-pool-cb15d787-hcb2  Unable to mount volumes for pod "elasticsearch-logging-0_logging(dbb9f559-2e09-11e9-a3ac-42010af00342)": timeout expired waiting for volumes to attach or mount for pod "logging"/"elasticsearch-logging-0". list of unmounted volumes=[elasticsearch-logging]. list of unattached volumes=[elasticsearch-logging elasticsearch-logging-token-m8lw7]

this scenario tracked through #2391 .. hence closing this


feat(core): bind

Shall we bind?

shut! It turns out that the build failed and we are getting the green button? :thinking: That's not good...

Ok... Let's bind, I guess... :grimacing: I'm a bit nervous about this TBH, but let's do it! :rocket:


Wrong number of "dots" at the bottom of the fullscreen gallery

When clicking on a photo, the bottom of the lightbox displays a "mini-preview" dot for each photo in the gallery.
For now there are twice as many dots as actual photos, and we only cycle through the first half.

Fixed by #28 and the move to lightGallery


Incompatible with Python 3

The AFSK library doesn't load properly when I run it on my Fedora 30 system with Python 3.7.
Some of the issues that occur:
>>> import afsk
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python3.7/site-packages/afsk/__init__.py", line 2, in <module>
    from afsk import encode
ImportError: cannot import name 'encode' from 'afsk' (/usr/local/lib/python3.7/site-packages/afsk/__init__.py)

I experienced further errors in the 'audiogen' library, but it appears these have already been reported in https://github.com/casebeer/audiogen/issues/2.

+1


Error message when trying to create Admin account

Hallo having installed grav-v1.7.43 on my local harddrive with Xampp. Installed the admin, email, error, form and login Plug-ins. When trying to create an Admin account the error message comes 'foreach() argument must be of type array|object, null given', see att.
What is the problem and how can I solve it?

What version of PHP?

PHP 8.2.4

@rhukster Hallo do you have any advise what to do?

@rhukster Where can I find help?

To be honest, the best place is our Grav discord server.  Link at top of website.  More likely to fin d fellow window users to help you out.

Ok going there. Thanks

Same issue here. Discord is no good as knowledge base, so why not share the answer here?


[Groups Infra] core endpoints view_filter

https://www.notion.so/dust-tt/Engineering-e0f834b5be5a43569baaf76e9c41adf2?p=5d15a65989da4b11aa99ed1c213f9fb3&pm=s

Enforce on all read endpoints


Adjoints: specify which are forward/reverse mode autodiff compatible

For each adjoint method, it would be convenient to include a table specifying which are compatible with each kind of autodifferentiation.

Closing as this will be accomplished in the next version.


The home page works, but there are 404 on the others.

I have error 404 when trying to go to subpages.
In the docker console I have:
api_1         | INFO django.server "OPTIONS /graphql/ HTTP/1.1" 200 0 [PID:9:Thread-3] api_1         | INFO django.server "OPTIONS /graphql/ HTTP/1.1" 200 0 [PID:9:Thread-3] api_1         | INFO django.server "OPTIONS /graphql/ HTTP/1.1" 200 0 [PID:9:Thread-3] api_1         | ERROR graphql.execution.executor An error occurred while resolving field Query.shop [PID:9:Thread-3] api_1         | Traceback (most recent call last): api_1         |   File "/usr/local/lib/python3.8/site-packages/graphql_jwt/utils.py", line 86, in get_payload api_1         |     payload = jwt_settings.JWT_DECODE_HANDLER(token, context) api_1         |   File "/usr/local/lib/python3.8/site-packages/graphql_jwt/utils.py", line 45, in jwt_decode api_1         |     return jwt.decode( api_1         |   File "/usr/local/lib/python3.8/site-packages/jwt/api_jwt.py", line 91, in decode api_1         |     decoded = super(PyJWT, self).decode( api_1         |   File "/usr/local/lib/python3.8/site-packages/jwt/api_jws.py", line 155, in decode api_1         |     self._verify_signature(payload, signing_input, header, signature, api_1         |   File "/usr/local/lib/python3.8/site-packages/jwt/api_jws.py", line 223, in _verify_signature api_1         |     raise InvalidSignatureError('Signature verification failed') api_1         | jwt.exceptions.InvalidSignatureError: Signature verification failed

Clearing the browser cache will solve the problem.


Do we still need paragonie/sodium_compat?

We don't support any version of PHP below 8.0, and Sodium has been bundled into PHP core since 7.2.
So...do we still need to depend on this library? Or should we just remove it and move ext-sodium into our true runtime dependencies?

Pinging @xjm and @davidstrauss for input here.

hi, that was our result last time we asked: https://mobile.twitter.com/SniperSister/status/1319916377143152641

To me, that says we might want to drop the dependency on paragonie/sodium_compat and instead require ext-sodium. Better to have fewer external dependencies, and I imagine the number of PHP installations with Sodium natively available will only go up.
@tedbow, what do you think?

We probably need a core issue to explicitly require the sodium extension so it gets added to https://www.drupal.org/docs/getting-started/system-requirements/php-requirements
Shouldn't be controversial at all because it's bundled everywhere, but saves someone complaining because their custom compiled PHP isn't supported.


Use C++14 standard when building

We have upgraded CI to use a recent compiler already and thus can also
increase the C++ standard now. After this, we'll also have to update
Gitian build to work with C++14 as well, but this is going to happen in
separate commits/PRs.

I remember a couple years ago Bitcoin had delayed updating to C++11 for compatibility reasons w/older environments, but I like that we are able to move forward with more modern standards. I think this is the right move, and would force any non-C++14 compatible build environments to update. Move forward or get left behind. 😉 👍
utACK


bug fixes and more

process_id must be a str not an int, esp. for process_mets.sh
active job status must use PID from $REMOTEDIR/ocrd.pid (on Controller), not from $PID (on Manager)
add missing job status D
jobs: show (and sort by) time created/terminated
use /workflows volume
active jobs: add kill button (dummy for now)

add kill button (dummy for now)

@SvenMarcus to implement this, we would need to "log in" to the Manager and kill the given process ID. But I don't like the Monitor to hold the keys. Perhaps we should instead start implementing our minimalistic web server in the Manager itself – delegating to for_production.sh, for_presentation.sh (which we will need for new jobs) and to the killer.
Sry, I'll update the CI tests shortly.

All right thanks. When the "pytest" problem is solved I give my approve.


entities vs. state_attr

Not an issue as such!!!
Thank you for your troubles, cool card!!
I am using sensor.kuche_fenster_shutter1_position but that does not update when the shutter is moving. I would need to use "state_attr('cover.kuche_fenster_cover_1','current_position')" to get the current position. This is updated as the window cover moves.
So how do I get this to work with the bar-card? In mushroom I have got this all worked out as "secondary information" and the % text is updated nicely as the cover moves. When using sensor.kuche_fenster_shutter1_position, the update occurs seconds after the cover has stopped moving. Not nice and also not very informative as it is not updated in real time.
Can't figure out, how to implement this with the bar-card.
Regards from Germany,
Robert
Was looking around and found, there is a "attribute"!! Can't figure out, how to get this info there....

`type: custom:bar-card
title: ''
columns: '3'
color: grey
min: '0'
max: '100'
positions:
icon: 'off'
indicator: 'off'
minmax: 'off'
title: inside
value: inside
entities:

entity: cover.tm_c_livingroom_cover_1_2
name: Wohnnen
icon: mdi:window-shutter-open
attribute: current_position
entity: cover.wohnzimmer_tur_cover_1
name: Tür
icon: mdi:window-shutter-open
attribute: current_position
entity: cover.kuche_fenster_cover_1
name: Küche
icon: mdi:window-shutter-open
attribute: current_position
unit_of_measurement: '%'
severity:
color: green
from: '100'
to: '100'
from: '0'
to: '0'
color: red
from: '1'
to: '99'
color: grey
`
Figured it out. Very cool, you thought of everything....   ;-)


⚠ Bofrost.de has degraded performance

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

HTTP code: 200
Response time: 1670 ms

Resolved: Bofrost.de performance has improved in 2887ed3 after 310 days, 20 hours, 49 minutes.


save data (state restore) - how does it work?

Hi! Great emulator, I got a custom Gameboy instance working very quickly in my environment. However, I think I am struggling with state restore/save data. I'm saving the get_cartridge_ram() to disk and pass it as save_data in the ctor, but the game I'm trying out is always starting from the beginning. I've tried saving both during the run-loop and afterwards, and data seem to be written (there is binary data in the file). Am I misunderstanding something, or is it maybe the ROM I'm using that is to blame?

Ah, cool then I think I understand what to expect better! 🙏🏻


remove

How to remove animated splash screen  after adding it ?

@obaijar I guess we have taken care of this already.
Meanwhile, I will introduce this feature on the next update


Test loss of access to a task

Some API operations indirectly lead to the loss of access to a given task group (and then to one or more tasks):

The TaskGroupV2.user_group_id is changed from being set to being unset, so that only the task-group owner maintains access.
A TaskGroupV2 is associated to a UserGroup, and a user is removed by that group.

If a user looses access to a task that they never imported into a workflow, this requires no special handling.
Here we are concerned with the case where a user looses access to a task that they had already imported into a workflow. We describe a user story based on case 2 above:

User<EMAIL_ADDRESS>belongs to user group team1
Task group my_pkg_1.2.3 is associated to user group team1
When the users gets a task list, this list also includes task from my_pkg_1.2.3. In the webclient: when the user wants to add a task into a workflow, they also see my_pkg_1.2.3 tasks in the dropdown menu.
The user imports a given my_pkg_1.2.3 task into their workflow my_wf
The user possibly runs some jobs based on workflow my_wf
An admin removes the user from user group team1
When the users gets a task list, tasks from my_pkg_1.2.3 are not there any more.
If the user tries to get a given my_pkg_1.2.3 task via its ID, the API responds with some Unauthorized error.
The database WorkflowTaskV2/TaskV2 relationship still exists and is still valid.
When the user gets the information about their workflow my_wf, the API responds correctly. This means that the user can still see the task in the workflow task list, as if they had access.
When the user tries to run my_wf, the API responds with some Unauthorized error.

The crucial point here is that if a user ever imported a task, we cannot fully remove their knowledge of such task. We can prevent them from importing it again in new workflows, and we can prevent them to run an old workflow including such task. But the user should still be able to see what they did in the past.
To rephrase it: we are stating that the access-control rules should not apply to the read operation for something you already had access to in the past.

The crucial point here is that if a user ever imported a task, we cannot fully remove their knowledge of such task. We can prevent them from importing it again in new workflows, and we can prevent them to run an old workflow including such task. But the user should still be able to see what they did in the past.
To rephrase it: we are stating that the access-control rules should not apply to the read operation for something you already had access to in the past.

Great summary, that's the target outcome! And fully agreed with the user story above.

The database WorkflowTaskV2/TaskV2 relationship still exists and is still valid.

Looks like a nice benefit of this WorkflowTask & Task model! :)


Confirm prompt before shutdown / reboot from PowerToys Run

Description of the new feature / enhancement
Add a check prompt before shutting down (reboot) from PT run to prevent accidents.
Scenario when this would be used?
For example, trying to type su to open sublime text but the shutdown option come up first and press on Enter.
The computer will be shut down accidentally and get no change to save some un-save work.
Adding the confirm prompt will preventing this kind of accident.
Supporting information
No response

Just found out this is a duplicate of #12293 by myself. Closing this.😅


New maintainers?

Hi there,
It seems this great project is sinking in oblivion, no commit for more than a year and pull requests that are piling up. I also have ideas to improve but without maintainers... Would it be possible to do something about that?
Cheers ✌

Hi I would like to maintain this project. Can you please add me as a maintainer?

Thank you @florenthobein 🤗. I would love to get a great team in place 👍 I've added you as a maintainer. Feel free to contribute what you can. Anyone else interested, please keep an eye to contribute by sending/reviewing PRs and responding to issues.
@florenthobein please tag me when we're ready for a new release.

Embarrassingly just realized this issue is from 2 1/2 years ago. I don’t know if you’re still interested @florenthobein (or anyone else who might see this), but any help would be great.


Adding type time to list of primitive types

Addresses https://github.com/MicrosoftDocs/powerquery-docs/issues/38

Docs Build status updates of commit ef20a52:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

query-languages/m/m-spec-consolidated-grammar.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Reviewer has approved this one. Merging.


[Flake] Backup integration tests still timing out in coverage builds

I just had a presubmit test and a continuous integration test fail with:
 1/11 Test #62: backup_integration_test ..................***Timeout 2400.07 sec
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from BackupTestWithCleanup
[ RUN      ] BackupTestWithCleanup.BackupTestSuite

11/11 Test #72: samples ..................................***Timeout 2400.10 sec
Running instance admin samples on test-instance-2

Running get-instance sample

https://source.cloud.google.com/results/invocations/92669f4b-6a1e-4f55-8cdc-41b972d867a4
https://source.cloud.google.com/results/invocations/a2b71fa0-d802-46cf-8766-4c36ad1cb32a

Another one:
https://source.cloud.google.com/results/invocations/b5df577f-4c3b-4e5c-9aff-06e1bb780646/targets

I am tempted to disable the Backup tests in the coverage build, thoughts?

SGTM, until we can come up w/ a better solution.
Also, 2 questions:

Are the Backup integration tests run in any other build besides coverage?

(If yes to above) Why are the Backup tests so slow in the coverage build and not other builds?

SGTM, until we can come up w/ a better solution.
Also, 2 questions:

Are the Backup integration tests run in any other build besides coverage?

No, they are only enabled if the RUN_SLOW_INTEGRATION_TESTS environment variable is set to yes, and we only do that for the code coverage build. There are a few other tests and examples that are slow, but the ones for backups are the ones timing out.

(If yes to above) Why are the Backup tests so slow in the coverage build and not other builds?

N/A

I found out that, some of the backup operations took 30 or 40 mins.
I'd like to 1) clean up the temporary instances and 2) try only using us-west1 before disabling it.

No, the backup operation in us-west-1 was also slow. I'd let the Spanner team look at this.


[2201.7.x] Fix test report bug on windows

Purpose
$subject
Fixes https://github.com/ballerina-platform/ballerina-lang/issues/41779
7.x PR of https://github.com/ballerina-platform/ballerina-lang/pull/41812
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Changes re introduced with https://github.com/ballerina-platform/ballerina-lang/pull/41935


EventsLoopProxy::wakeup does not fire until mouse is moved over window (Windows)

The problem is this: I have a Window, which stores the EventsLoop. Now, webrender, which I use for drawing, is async in nature, so if I say "render a frame", I don't know when the frame is going to be finished. For this, webrender has a RenderNotifier trait, which I can implement to call EventsLoopProxy::wakeup().
The wakeup() is called correctly, but I don't get an "awakened" event until the mouse is moved over the window. But Event::Awakened is not a window event, it doesn't have anything to do with the window. This is especially noticable when resizing windows:
The code where I am trying this is here:
RenderNotifier: https://github.com/maps4print/azul/blob/402f21d72e012530f07156044def701d79043321/src/window.rs#L318-L334
Submitting new frames: https://github.com/maps4print/azul/blob/402f21d72e012530f07156044def701d79043321/src/app.rs#L567-L568
Polling: https://github.com/maps4print/azul/blob/402f21d72e012530f07156044def701d79043321/src/app.rs#L159-L164
Handling the awakened event: https://github.com/maps4print/azul/blob/402f21d72e012530f07156044def701d79043321/src/app.rs#L517-L520
I poll indefinitely (but not using run_forever(), because reasons). In theory it should always print:
generating frame...
sending wakeup event...
received awakened event...

However, all I get is the first two messages, only if I move the mouse over the window, then it updates the screen. If the mouse is over the window, but doesn't move, it doesn't send the Awakened event either. You can clone the repository and run cargo run --example debug to replicate this.
Initial state:

After resizing:

After moving the mouse over the window:

The problem is that while I could swap the buffers at 60FPS, this blocks until the backbuffer is finished, so I'd be waiting on webrender to finish, which blocks events to be processed immediately and leads to lagging when resizing the window, so I'd rather not do that. I'm currently experiencing this on Windows 8, I'm not sure if this also happens on other windowing systems.

I would've appreciated a heads up that this requires nightly, since things compile pretty slowly on my laptop. Maybe you could add a rust-toolchain file?
Anyway, I can reproduce this on Windows 10. Do you only have this issue with trying to awaken after resizing, or is it with any event?

If you run this:
extern crate winit;

use std::sync::{Arc, Mutex};

fn main() {
    let mut events_loop = winit::EventsLoop::new();

    let _window = winit::WindowBuilder::new()
        .with_title("A fantastic window!")
        .build(&events_loop)
        .unwrap();

    let proxy = events_loop.create_proxy();

    let count = Arc::new(Mutex::new(0usize));
    {
        let count = Arc::clone(&count);
        std::thread::spawn(move || {
            // Wake up the `events_loop` once every second.
            loop {
                std::thread::sleep(std::time::Duration::from_secs(1));
                proxy.wakeup().unwrap();
                *count.lock().unwrap() += 1;
            }
        });
    }

    events_loop.run_forever(|event| {
        match event {
            winit::Event::Awakened => {
                println!("WAKE UP {}", count.lock().unwrap());
                winit::ControlFlow::Continue
            }
            winit::Event::WindowEvent { event: winit::WindowEvent::CloseRequested, .. } =>
                winit::ControlFlow::Break,
            _ => winit::ControlFlow::Continue,
        }
    });
}

You'll see that any wakeup messages sent during a resize are eaten. If your issue is specific to resizing (which has special handling), then it seems quite likely to be related to this.

It shouldn't require nightly... rustc 1.26 stable works for me, which is also what I'm using for CI. What problems did you have with that? Maybe you had an older compiler installed (1.26 is rather recent)?
Your example works for me, too - the timer is incremented, but the wakeup event is ignored. This example confirms the bug, no? I do not know if other events "eat" the wakeup events, too. For now, if it would just work properly during resize events, that'd be great.
That would explain why the screen doesn't even update after the resize is finished - the wakeup event gets eaten, and the events loop never knows that the next frame is ready and it should just swap the buffers.
But I'm curious why the events loop is different for resizing vs custom events. Isn't it just one big queue that both the resize event (called by Windows) and the .wakeup() have access to?

Maybe you had an older compiler installed (1.26 is rather recent)?

Ah, that's surely the case; I only use my Windows machine for working on winit, so I never really update. Sorry.

But I'm curious why the events loop is different for resizing vs custom events

So you remember #506? Well, just like that, this comes down to the same problem that #445 exists to solve. Due to how Windows works, resizing the window blocks the event processing thread (which is why we have it on a separate thread in the first place). The details are outlined more in #459.
Seeing as that complexity has foiled you twice now, I'll give you another update on the resolution timeline.

Last time I said that HiDPI support had to happen first, and as you know, that's going to be a solved issue by the end of this week.
Since we've managed to converge on a new EventLoop design, work can ostensibly begin right after that.
I promised to add a Windows raw input and macOS backend to gilrs once the owner finishes a refactor, so that's going to occupy about a week of my time at an unknown point during this month.
For the new EventLoop design, I'll be the one who restructures the X11, macOS, Emscripten, Android, and iOS backends, so that's going to be something of a bottleneck.
Besides everything else, I also have to fix bugs that get reported and do other maintainer stuff, so there could be unforeseen diversions of significant duration or quantity.

So, with all of that, this could probably be fixed by July 4th!
Alternatively, I could stick a pending_wakeup: Arc<AtomicBool> into EventsLoop like we do on X11, and then you'll get the Awakened late instead of never. That could be included in 0.15.1, so you'd have a fix this week.

Any news on this? Just asking.

#459 is in flux again, and at this point, my attention to winit is mostly limited to essential maintenance duties. @Osspial also seems to be busy?

#459 is in flux again

I got the impression that the overall design of #459 has stabilized?

I think it became "in flux" again after https://github.com/tomaka/winit/issues/459#issuecomment-404698442, after which several questions / alternative proposals came in.

Ah right, but Now we seem to be getting close to something. I think @Osspial is doing a great job of summarizing the thread.

Does #634 help with this?


Facilitate fully dynamic response generation by default in "prism proxy" scenario

Description
Currently, Prism Proxy lacks support for enabling dynamic mode by default, which necessitates the manual addition of the "Prefer: dynamic=true" header to each request. This approach poses challenges, particularly when integrating the Faker library for API property simulation, and detracts from user experience. Without the header addition the only response that can be generated is something like

Proposal
I suggest enhancing Prism Proxy to allow users to run it in default dynamic mode, eliminating the need for manual header assignment. This would significantly improve usability and streamline the integration process.
Proposed Solution
Introduce a command syntax enabling dynamic mode by default:
prism proxy -d <api_def.yaml> http://localhost:8080
Expected Behavior
With dynamic mode enabled by default, users can seamlessly integrate Prism Proxy into their workflows without the overhead of manually configuring headers for each request.
Impact
This enhancement will enhance user experience, particularly for scenarios involving Faker library integration, by simplifying the process and reducing manual effort.

This does look like something we should add as a command line option for proxy mode!
Potential Solution:
Move dynamic and json-schema-faker-fillProperties from the mock commands  into the shared options. Any tests needed for dynamic mode in proxy, along with documentation updates for new cli command usages.


I don't need full screen

I don't need full screen, then how can I set?

@XXboy: Simply create and use instance of NVActivityIndicatorView.

Close this, reopen if need be.


Setup a CI to build demo sites

It'd be great if we had a ci that built a series of popular github repos so people can see what a standard repo looks like when built with landr

This is an amazing idea!


expose git commit API for other extensions

Issue Type: Feature Request
https://github.com/Microsoft/vscode/blob/1acabe663a4ec79cb728ea4966278ca4387ac35b/extensions/git/src/api/git.d.ts#L168-L176
third-party extension needs this API for custom commit.
Why third-party extension does not implement the commit interface by itself?
calling the built-in Git extension interface is to keep Commit's behavior consistent and maintain a consistent user experience
VS Code version: Code 1.31.1 (1b8e8302e405050205e69b59abb3559592bb9e60, 2019-02-12T02:16:38.656Z)
OS version: Darwin x64 18.2.0

PR welcome. Until then, closing this.


FIx: Renamed the StatsChart to BarGraph and updated its usage

Fixes Issue
Closes #9408

Changes proposed

Rename StatsChart to BarGraph in BioDrop/components/statistics/StatsChart.js.
And updated its usage in  BioDrop/pages/account/statistics/index.js
and  BioDrop/pages/account/statistics/index.js

Check List (Check all the applicable boxes)

[X] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[X] This PR does not contain plagiarized content.
[X] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

The reason the build is failing, is because the imports were updated but the filename was not - they don't match
./pages/account/statistics/index.js
Module not found: Can't resolve '../../../components/statistics/BarGraph'

https://nextjs.org/docs/messages/module-not-found

./pages/account/statistics/link/[id].js
Module not found: Can't resolve '../../../../components/statistics/BarGraph'

https://nextjs.org/docs/messages/module-not-found

It has ben 2 weeks, I will fix via temporary branch.


ClusterIp Service support

Fixes #187
The goal of this is to make the Service source a bit more flexible and provide the ability to publish DNS entries for the ClusterIP services.  I have this working for both the FQDN template and the explicit annotation.
I considered not supporting the implicit FQDN mapping since you typically don't want internal dns information leaking into public DNS entries.
Would it be preferable/advisable to make the processing of ClusterIP services an explicit "opt in" thing via the configuration?  I would be happy to update the PR if that is the direction people would like to go.

I think this should be somewhat opt-in. Since every service has a cluster IP this means that every service is registered in DNS by default. This could be a blocker for some people. @ideahitme what do you think and what would be a good appraoch? We could do a separate source or introduce additional flags as modifiers for sources (similar to --google-project for the --provider=google).

We could also have modifiers in the flag itself. E.g. something like --source=service:type=nodePort to only consider nodePort services in the service source. Experimenting with different ways to use flags here :)

I agree with the overall sentiment and think making it opt-in does allow for more flexibility, however this does only impact the fqdn-template flow.  Users that are explicitly annotating their services, so IMO it should be expected that something would be done with that.
I understand this deviates from the current processing and I am not opposed to any suggestions.  I personally like the types approach for the service however I could see this being somewhat onerous.

Yes, this seems fine. Let's hear out @ideahitme.

Any suggestion on how you would like to proceed.  I can really go either way, an explicit feature flag, a custom --source value or the source sub-types suggestion.
Thinking about it a bit more though, the source sub-types would just need some though as we would want to keep current configurations operational without significant change I'm assuming.

@jrnt30 Thanks for your continued effort!
Let's go with another flag "that also includes all services that have a cluster ip but lack a load balancer ip" (exactly how you did it).
If you agree, l suggest adding a --include-internal-services(or similar) that enables your changes and that's false by default to keep the current behaviour.

LGTM with @linki suggested approach

I think I've addressed the requests, the ClusterIP source will now only be evaluated if the --publish-internal-services flag is provided

Is there anything else that you would like addressed here?  Is this still a direction the project is willing to support?

@jrnt30 lgtm. Can you also a quick entry for the changelog? Also @ideahitme want to have a look as well?

few comments otherwise LGTM

I merged the conflict in CHANGELOG and used the format we used before. However, I think I like the next version (unreleased) heading.

Thanks @jrnt30 !

@linki sorry, I caused a conflict by merging #318 --- we should update the CHANGELOG again to reflect https://github.com/kubernetes-incubator/external-dns/releases

Resolved.  Someone hit the merge button before we have it happen again! 👿

Released: https://github.com/kubernetes-incubator/external-dns/releases/tag/v0.4.4 :tada:

hey @jrnt30 there is a little issue while exposing cluster IPs from the service when multiple annotations exists.
I run kubectl apply -f  to update my deployments, and 2nd annotation is automatically added by kubernetes:
Name:			evaldas-app
Namespace:		evaldas
Labels:			app=evaldas-app
			tier=frontend
Annotations:		external-dns.alpha.kubernetes.io/hostname=evaldas-app.domain.com
			kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"v1","kind":"Service","metadata":{"annotations":{"external-dns.alpha.kubernetes.io/hostname":"evaldas-app.domain.com."},"labels":{"app"...
Selector:		app=evaldas-app,tier=frontend
Type:			NodePort
IP:			<IP_ADDRESS>

any workarounds for this to still work? Thanks! :)

What is the issue/error you are seeing?

hey @jrnt30 , it does not throw any error at all.
kubectl apply -f adds second annotation line by default (not sure how to disable it)
DNS tools stops working correctly. It says no new DNS entries has been found... if we have kubectl.kubernetes.io/last-applied-configuration line under annotations.

Can you create an issue then please?  A few things that will be helpful would be:

Did it work for the first application? Was there an initial entry created?
What version are you running on?
Have you turned up the logging to debug to get any additional context?  Anything useful there?
Is this just for the ClusterIP services that you see this?


FluentNumberField Display and Edit format

Hello,
I'd like to format the value displayed in the FluentNumberField using the Italian culture using the comma (,) as decimal separator.
It seems that the component always uses the dot (.) as decimal separator.
What's the best way to achieve that?

That is not possible with the current underlying web component.
This has been asked and answered before. Closing this. Duplicate


LND unable to determine prune state of Litecoin-core (litecoind) node version 0.21.2rc1

Background
LND unable to determine prune state of Litecoin-core (litecoind) node version 0.21.2rc1
Your environment

LND Version: 0.14.1-beta commit=v0.14.1-beta, build=production, logging=default, debuglevel=info
Linux 4.19.0-18-amd64 # 1 SMP Debian 4.19.208-1 (2021-09-29) x86_64 GNU/Linux
Litecoin Core version v0.21.2rc1
Running in an LXC container

Steps to reproduce
Update working litecoind v0.18.1 to 0.21.2rc1. Start previously working LND systemd service and unlock LND wallet.
Expected behaviour
good things
Actual behaviour
2022-02-02 12:59:07.843 [ERR] LTND: unable to create partial chain control: unable to determine if bitcoind is pruned: json: cannot unmarshal object into Go struct field SoftForks.softforks of type []*btcjson.SoftForkDescription
2022-02-02 12:59:07.843 [ERR] LTND: Shutting down because error in main method: error creating wallet config: unable to create partial chain control: unable to determine if bitcoind is pruned: json: cannot unmarshal object into Go struct field SoftForks.softforks of type []*btcjson.SoftForkDescription
2022-02-02 12:59:07.846 [INF] LTND: Shutdown complete
also opening this issue against litecoin-project/litecoin

This failure is likely caused by a new bip8/9 version bit that's unknown to lnd. At first glance: patch the new version bit into ltcd, or btcd, this means that lnd will also fail to start on future pruned nodes with new feature activation bits.

@HannahMR
If @losh11 is correct and unknown version bits indeed breaks dialog with the chain node then it ends up being a wider scoped issue -- perhaps a review of the "nice to have" triage tag may be warranted, no?

I have this as well. Unfortunately I am brand new to both lightning and reasonably new to litecoin and so far it's not a great experience. I've just been following online tutorials trying to get a basic lightning node to work so I can try out what's supposed to be the future of money that grandma's going to use to pay Joe the plumber. Did you manage to find a workaround to get it to work? What is a version bit and do I have any control over that?

Closing this issue as LND will not be supporting Litecoin from 0.18 onwards


Pytorch compile compatibility

Hi! Thank you for your amazing work!
When I'm compiling unet with torch.compile(unet) decoupled text/image attention seems to stop working. Do you have fix for that?

@thepowerfuldeez I tested the torch.compile, it can run well:
# load ip-adapter
ip_model = IPAdapter(pipe, image_encoder_path, ip_ckpt, device)
ip_model.pipe.unet = torch.compile(ip_model.pipe.unet)


Trusted users and actions

There should be a way to configure trusted users and actions.
These actions are only allowed to be performed by the trusted users.

Inviting the bot to a channel ( #52 ) can be a trusted action.

Yeah I second this. Trusted users should be able to !trust/!untrust other users. There would need to be 2 tiers of trust though (one that can't be removed with this command), so we can keep board members permanently trusted.

Also managing the twitter mappings could be a trusted action. !twitter-alias eligrey ^EG


Help on OTP/MFA and SSO

Hello, I wanted your input on the use of SSO with MFA and use of the CLI..
i.e. I've been able to use your plugin with Keycloak/SSO  (via nginx and vouch proxy)
I can get the redirect to the IDP, and am able to use MFA (username/pass and authy), and then I'm redirected back to nexus, and can login!!
However, this breaks when attempting to auth via a developer workstation i.e. mvn cli.
Do you have ideas/recommendations on use?

I can use a different keycloak realm and hit that endpoint to bypass SSO/Vouch proxy.. but I guess it would be awesome if nexus had the free token realm   :-(

@IMbiea Sorry for so late reply, I didn't get the notification from github :(.
Actually, we should use different authorization verifications for the web users and the CLI users when enabling SSO.
The SSO should be disabled temporarily when the HTTP header Authorization is specified or User-Agent is Maven or Docker. For Nginx, its configuration should be like (see develop/nginx-gateway/vhost.d/nexus3.conf#L19):
        set $oidc_disabled "false";
        # Disable OIDC when using maven client
        if ($http_user_agent ~* "^(Apache-Maven|docker)/.+$") {
            set $oidc_disabled "true";
        }
        # And disable OIDC when the header Authorization was specified
        if ($http_authorization !~* "^$") {
            set $oidc_disabled "true";
        }

And the variable $oidc_disabled will be passed to the OIDC script and to skip token requests when it's true, like develop/nginx-gateway/vhost.d/oidc.lua#L191.

@flytreeleft  So CLI users can't be authencatied by keycloak?

@WestFarmer The CLI still can be working well, the command mvn will pass the username and password via the header Authorization which will be authenticated by Keycloak in the background.

@flytreeleft that happens in the java code , right?

@WestFarmer Yes, it is.

Close the inactive issue, if it's not resolved, please just append the problem to this issue. Thanks :)


Issue with smaller content size

For iOS, it works fine only when the content size inside the pull refresh layout is bigger than the pull refresh layout's size. I tested the sample available on GitHub (scrollview XAML) with fewer boxes/items inside the scroll view e.g. 2. Now when I try to pull the list down, nothing happens.

I have fixed this issue. Can you please merge that change or allow me to commit/push my change in this repository. Here is the change I mage after doing the Fork:
https://github.com/HaiderAbbas/Xamarin.Forms-Awesome-Controls/commit/8789b71a5845c8a8b5967d9f80c6c8b478479291

PUlled in and pushing an update


Run the program & Post a screenshot of it over here

You are required to first clone this repository to your desktop. Before that make sure to fork this repo to your profile. You can clone it using the terminal and the command below, provided you have git installed in your terminal :
git clone https://github.com/{your-username}/Artificial-Neural-Network/
After cloning it, you are required to run the the python file and post the screenshot of the output from your terminal as a comment on this issue thread itself.
This issue is for everyone to complete and make sure that you run the ann_class.py file


Pagination improvements and make cursor based pagination default

add support for cursor based pagination and make it default since it applies to most endpoints and it is recommended by the zdesk API documentation.
offer possibility to fall back to offset based pagination.
incremental API has a different pagination mechanics. Improve the support for these endpoints.

If you wish to run the tests:

copy tests/zdtestcfg.py.example to tests/zdtestcfg.py and fill in with credentials for the zendesk sandbox instance. Then run pytest or just use the VS Code extensions for running the tests.

LGTM! also pytest 🚀

If I get to work on another repo using pytest, I'll let you know @tudorBonca . I'd gladly hand it over if you're nostalgic about it :D


Eliminate // +build comments when Go 0.18.0 is released

This is meant as a reminder that lines like this in the source should be removed when Go 0.18.0 is released:
// +build !windows,!plan9

The above should be converted to the now preferred form introduced by Go 0.17.0 if that hasn't already been done:
//go:build !windows && !plan9

See https://golang.org/doc/go1.16#go/build/constraint for more context. I noticed this wasn't already an open issue when looking at the files in pkg/shell/. The redundant build tags confused me for a moment until I remembered that the //go:build syntax is extremely new.
P.S., I was looking at those files because I was trying to understand why my interactive Elvish shell on Windows 10 wasn't sourcing my rc.elv script that I had rsync'd from my primary UNIX system. Specifically, from my "home dir" on MacOS to my "home dir" on my Windows 10 VM. I see that this difference in behavior is documented but it probably needs more documentation since I had no idea it would be using this path (from an embedded fmt.Printf in pkg/shell/paths_windows.go):
 "C:\\Users\\krade\\AppData\\Roaming\\elvish\\rc.elv"

I expected a path like ~/.config/elvish/rc.elv (which does exist by virtue of my rsync command). I am an infrequent MS Windows user so I have no idea what is the optimal Elvish behavior in this context. Would some support for traditional UNIX path resolution on Windows cause problems?

I'm closing this because it's not necessary to be reminded of this; the legacy constraints will be removed by go fix when Elvish requires Go 1.18 (https://go.googlesource.com/proposal/+/master/design/draft-gobuild.md#transition).


There should be a CompileError if trying to transpile async functions or await expressions

It should be similar to Generators are not supported.

Since ab84650 there's the support data available for async/await.

I actually implemented that in 598b4b143ed4d69f27fd0c9e66a7919e44ef8eaf.


Datepicker component return undefined

Expected behavior
Component rendered
Actual behavior
React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

any updates on this issue?

@nWidart I forgot what was the problem, but its blocking me. So I decided to use https://github.com/YouCanBookMe/react-datetime instead.


[PE-D][Tester E] Check Group feature: Confusion between "requirement" and "encouraged"

For a group with all same gender it returns:

But in your help window it states it is not a requirement, just an encouragement, so the Check Group should return a more appropriate message.

Labels: severity.Low type.FeatureFlaw
original: yanghengtang/ped#5

Change warning message


Latest distribution...?

Hello.
I'm not sure how to go about building this project from source. I see there have been a number of updates to the code fairly recently, and the version number is now 0.15.0.
If I grab the remark-latest.min.js from remarkjs.com it seems to be version 0.14.1 (from looking in the code).
Is there a compiled version of the latest code somewhere?
Thanks, and sorry if I'm being dumb!
Steve

Rather for people reaching out this issue - https://remarkjs.com/downloads/remark-0.15.0.min.js (as - currently - already mentioned in README).

Thank you, @szpak.
Where on the README is that URL mentioned? I see only https://remarkjs.com/downloads/remark-latest.min.js.
…which btw should be the right permanent URL, but apparently remark-latest.min.js contains/points to 0.14.1 while there is also remark-0.15.0.min.js with that newer version…
@gnab, I take it that remarkjs.com is a separate (private) repo of yours? If so, shouldn't you update the symlink to the latests release?

Where on the README is that URL mentioned? I see only https://remarkjs.com/downloads/remark-latest.min.js.

In fact, I see, it was a mental shortcut. There is https://remarkjs.com/downloads/remark-latest.min.js mentioned in the README, and checking the gh-pages branch, I've found 0.15.0:
https://github.com/gnab/remark/commit/b01c7dcef72a8c73b35ee96b4cd98576bf2e4a7c

but apparently remark-latest.min.js contains/points to 0.14.1

Looking at the commits, it 0.15.0 was in fact added only as a separate file. Linking latest to 0.14.1 could be misleading...


⚠ LEGO (abakus backend) has degraded performance

In 9b0cb4b, LEGO (abakus backend) (https://lego.abakus.no/health) experienced degraded performance:

HTTP code: 200
Response time: 14049 ms

Resolved: LEGO (abakus backend) performance has improved in 2559677 after 15 minutes.


Update GrafanaFolder example syntax

The example values for a CR are used when creating a new instance of that CR in the OpenShift web-console. The example attribute json: is not valid for a GrafanaFolder. This Pull Request updates the example to set a custom title using the title: attribute.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


fix: sync editable region and jaws

refactor: remove ambiguity about editable region
fix: make jaws follow the highlighted region

Closing in favour of https://github.com/freeCodeCamp/freeCodeCamp/pull/43537


Error: Output stream closed when trying to stream an mp3 file with express

Version information

fluent-ffmpeg version: 2.1.2
ffmpeg version:
OS: Windows 10

Code to reproduce
const express = require('express')

const server = express()

const ffmpeg = require('fluent-ffmpeg')
ffmpeg.setFfmpegPath('ffmpeg.exe')

server.get('/', (req, res) => {
    res.set('Content-Type', 'audio/mp3')

    ffmpeg()
        .input('track.mp3')
        .toFormat('mp3')
        .pipe(res, { end: true })
});

Expected results
track.mp3 to be streamed to the express server on root
Observed results
Error: Output stream closed
    at Timeout._onTimeout (C:\Users\Shahar_2\Desktop\Projects\CUNTMUSIC-Server\node_modules\fluent-ffmpeg\lib\processor.js:491:25)
    at listOnTimeout (internal/timers.js:549:17)
    at processTimers (internal/timers.js:492:7)
Emitted 'error' event on FfmpegCommand instance at:
    at emitEnd (C:\Users\Shahar_2\Desktop\Projects\CUNTMUSIC-Server\node_modules\fluent-ffmpeg\lib\processor.js:424:16)
    at Timeout._onTimeout (C:\Users\Shahar_2\Desktop\Projects\CUNTMUSIC-Server\node_modules\fluent-ffmpeg\lib\processor.js:491:17)
    at listOnTimeout (internal/timers.js:549:17)
    at processTimers (internal/timers.js:492:7)

Checklist

[ ] I have read the FAQ
[ ] I tried the same with command line ffmpeg and it works correctly (hint: if the problem also happens this way, this is an ffmpeg problem and you're not reporting it to the right place)
[ ] I have included full stderr/stdout output from ffmpeg

The terminateTimeout option (PR https://github.com/fluent-ffmpeg/node-fluent-ffmpeg/pull/1292) could solve this issue.


fix: update importer log message with error details

Add error message into the log for better debugging

You might also want to print out the type of the exception. E.g. e.__class__.__name__. See https://stackoverflow.com/questions/9823936/how-do-i-determine-what-type-of-exception-occurred


Feature: Add support for running multiple replicas

Requirements:

Proposal:

Hi, ¿is vaultwarden possible use multiple replicas to deploy in HA?
Thank you @guerzon for this chart.

¡Hola @fhera!
Right now there are issues running multiple copies of Vaultwarden. For example, the data directory (/data by default) contains application data such as attachments and it has to be visible to the multiple replicas.
It is possible to put it in an NFS filesystem, but I'm not sure if that's something you can do or even want. There might be other cloud-native alternatives for this though (?). Personally, I would like to see S3 support so we could point /data to an S3 bucket instead. If you or your organization has the resources, I encourage you to sponsor or submit a pull request on https://github.com/dani-garcia/vaultwarden.
One hack I found was to disable the ORG_ATTACHMENT_LIMIT but I'm pretty sure this is not enough.
I opened a discussion here to discuss the topic further.
Lester

i don't think that the chart should take care of concurrent access to /data/, that is something that usually is managed by kubernetes itself, using ReadWriteMany PVCs, so it should be sufficient to add the PVC type and a good Kubernetes admin must know if he needs to use a RWO or RWX volume.
All in all, given how Bitwarden works there are not many concurrent accesses, 'cause the client(s) sync the vault when needed, then do not access the server at all, unless users use the WEB UI instead of any client.
One need for multiple replicas indeed could be related to HA, having two pods would help for rolling updates or in case of fault of one node, but still Kubernetes would take care of it, rescheduling  pods on other nodes and doing, well, rolling upgrades, so there will always be a running pod.

I've tested this a bit and it seems to work on this configuration:
kind: Statefulset (each replica has its own persistent storage, which is not sync'd)
datase: postgres
extra stuff: Service configured with traefik sticky sessions annotations:
traefik.ingress.kubernetes.io/service.sticky.cookie: "true"
traefik.ingress.kubernetes.io/service.sticky.cookie.name: "vaultwarden-sticky"
without the sticky sessions strange stuff happens as i get logged out immediately after logging in, i assume some sort of in memory data that is not yet shared with other replicas.

I am using a loadbalancer service and an apache2 as a proxy for Vaultwarden.
When running > 1 replicas of Vaultwarden I am usually required to login multiple times.

I am using a loadbalancer service and an apache2 as a proxy for Vaultwarden.
When running > 1 replicas of Vaultwarden I am usually required to login multiple times.

You need to setup some sort of sticky sessions, otherwise it doesn't work properly.

I am using a loadbalancer service and an apache2 as a proxy for Vaultwarden.
When running > 1 replicas of Vaultwarden I am usually required to login multiple times.

You need to setup some sort of sticky sessions, otherwise it doesn't work properly.

I added
  sessionAffinity: ClientIP
  sessionAffinityConfig:
    clientIP:
      timeoutSeconds: 10800

to my loadbalancer service yml and this seems to do the proper job.

A PR would be very welcome for this feature.

Thanks all for the inputs. PR #131 created and merged.


BC break with SncRedisBundle >=4.0 when calling multi()

I had code which was working just fine with SncRedisBundle 3.* branch:
        $redis = $this->redisClient->multi();
        foreach ($items as $item) {
            $redis->zAdd(self::QUEUE_KEY, $item->getAuditDefinitionId(), $this->serialize($item));
        }
        $result = $redis->exec();

After upgrading to 4.0 it started to cause multiple errors in tests:

NOTE; the offending line 31 is the one which starts multi transaction
This can be solved by setting mode value manually when calling multi:
        $redis = $this->redisClient->multi(\Redis::MULTI);
        foreach ($items as $item) {
            $redis->zAdd(self::QUEUE_KEY, $item->getAuditDefinitionId(), $this->serialize($item));
        }
        $result = $redis->exec();

NOTE; I am explicitly using value which is supposed to be used by default according to phpredis documentation
When I lock this bundle to version below <4.0 everything runs as before.
Configuration details:
PHP version:

PHP Redis extension:

Bundle configuration in Symfony:

Symfony version: 5.4.1

I've created https://github.com/phpredis/phpredis/issues/2044 as issue should be solved there.


Minor antag name fix

About the PR

Why / Balance

Technical details

Media

[ ] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:trollface:


Route gets called twice when using params and throwing error

I really thought I was going crazy, but after lots of debugging I was finally able to write a simple reproducible test case. This is for express 4.0.0-rc3.
When having routes that uses params (app.get('/test/:id', ...)) and throws an error, the route will be called twice. It also ignores when my custom error handler writes to the socket and uses the default 500 to output a page to the client.

var express = require('express');

var incomingRequests = 0;
var routeCalled = 0;

app = express();

app.use(function (req, res, next) {
  incomingRequests += 1;
  next();
});

app.get('/test/:id', function (req, res) {
  routeCalled += 1;

  console.log(' --- ');
  console.log('incomingRequests', incomingRequests);
  console.log('routeCalled', routeCalled);
  console.log(' --- ');

  throw new Error('Error in get');
});

app.listen(1337);

Start the app and hit the route:

node twice.js
curl localhost:1337/test/2

I am having the same problem with "express": "^4.16.3",
let router = express.Router();
router.use((req, res, next) => {
console.log("ccccccccccccc");
console.log(req.headers);
//console.log(res.getHeaders());
console.log("dddddddddddddddddddd");
//fnTokenAuthenticateOne(req, res, next);
next();
});
and the out put is
ccccccccccccc
{ host: 'localhost',
connection: 'keep-alive',
'access-control-request-method': 'GET',
origin: 'http://localhost:3005',
'user-agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36',
'access-control-request-headers': 'access_token,secret_token,type',
accept: '/',
referer: 'http://localhost:3005/courses',
'accept-encoding': 'gzip, deflate, br',
'accept-language': 'en-US,en;q=0.9' }
{ 'x-powered-by': 'Express',
'access-control-allow-origin': 'http://localhost:3005',
'access-control-allow-methods': 'GET,PUT,POST,DELETE,OPTIONS',
'access-control-allow-headers': 'Content-type, Authorization,access_token,secret_token,type' }
dddddddddddddddddddd
ccccccccccccc
{ host: 'localhost',
connection: 'keep-alive',
accept: 'application/json, text/plain, /',
origin: 'http://localhost:3005',
access_token: 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjViOWJlZWQ3MTJhOWEwMmRlYzU1MzliZiIsImlhdCI6MTU1MTgxMDk5MywiZXhwIjoxNTUxODE0NTkzfQ.et30EP19MTxiV7VJ15g5HV39xi-wrpph1XIN6IgUKlk',
type: 'local',
'user-agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36',
secret_token: 'undefined',
referer: 'http://localhost:3005/courses',
'accept-encoding': 'gzip, deflate, br',
'accept-language': 'en-US,en;q=0.9' }
{ 'x-powered-by': 'Express',
'access-control-allow-origin': 'http://localhost:3005',
'access-control-allow-methods': 'GET,PUT,POST,DELETE,OPTIONS',
'access-control-allow-headers': 'Content-type, Authorization,access_token,secret_token,type' }
dddddddddddddddddddd

@purusingh This is a very old issue.  If you are having new issues, feel free to open a new issue, but from what you posted here your best bet is to start with Stack Overflow or the express gitter.


This is support for pressing Enter key to "Add All"

As suggested, I've added a boolean option "pressEnterKeyToAddAll". The option "pressEnterKeyToAddAll" defaults to false, so the original behavior has not changed.
When enabled, pressing the Enter key will mimic clicking "Add All", so any items in the filtered list will be added to the Selected List. Also, pressing the Enter key will only Add All if there is text in the input.

Thanks again for contributing!

You're welcome. I hope to do more in the future.