playlists#all undefined method `login' for nil:NilClass

Error in alonetone
ActionView::Template::Error in playlists#all
undefined method `login' for nil:NilClass
View on Bugsnag
Stacktrace
app/views/shared/_playlist.html.erb:2 - block in _app_views_shared__playlist_html_erb___3922616358317901537_47406148536800
app/helpers/record_tag_helper.rb:99 - content_tag_for_single_record
app/helpers/record_tag_helper.rb:85 - block in content_tag_for
app/helpers/record_tag_helper.rb:84 - map
app/helpers/record_tag_helper.rb:84 - content_tag_for
app/views/shared/_playlist.html.erb:1 - _app_views_shared__playlist_html_erb___3922616358317901537_47406148536800
app/views/playlists/all.html.erb:5 - _app_views_playlists_all_html_erb___1055281111046210064_70233471646220

View full stacktrace
Created by Jenya Zueva via Bugsnag

Fixed in here
https://github.com/sudara/alonetone/commit/94069abbcb7b891f442877ff25575cd7fa14ac05

An error linked to this issue has been reopened in Bugsnag
ActionView::Template::Error in playlists#all

An error linked to this issue has been reopened in Bugsnag
ActionView::Template::Error in playlists#all


Slide reach enormous dimensions with flexbox ONLY in safari

I found a lot of issues that is related to having the carousel inside a parent with display set to flexbox or table.
But non of the solutions worked for me, My issue is a little bit unique as the carousel works as expected in all browsers even IE except for Safari.

#carousel-movies {
    overflow: hidden;
    padding: 0 1rem;
    display: -webkit-box;
    display: -moz-box;
    display: box;
    display: -webkit-flex;
    display: -moz-flex;
    display: -ms-flexbox;
    display: flex;
    -webkit-flex-flow:column wrap;
    -ms-flex-flow:column wrap;
    flex-flow:column wrap;
    -webkit-box-pack: center;
    -webkit-justify-content: center;
    -ms-flex-pack: center;
    justify-content: center;
}
#carousel-movies-wrapper {
    -webkit-box-flex: 1;
    -webkit-flex: 0 auto;
    -ms-flex: 0 auto;
    flex: 0 auto;
}

Any idea how I could resolve this issue ?

I fixed the issue on your example by setting max-width to 100% for the #carousel-movies-wrapper
http://jsfiddle.net/ahmad/fmo50w7n/151/

hello
i wanna learn box-sizing and all of its family.
please Introduce a website for learning.
thanks.


[Storage-Preview] az storage file/directory Trailing dot support, add --disallow-trailing-dot and --disallow-source-trailing-dot

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

Storage-Preview


Create TypeScript type definitions for methods, events, and options

https://github.com/DefinitelyTyped/DefinitelyTyped

It is great to see this^^ waitring so long

You'll probably we waiting for a while still, unless someone picks this up and works on the feature. I'll be busy for a while with a number of other Fine Uploader related features and bugs.

Should be covered by #1719.


Add possibility to subscribe a sequence enty animation complete

Hello, it would be very handy if there been a possibility to subscribe an animation entry sequence. For example, we would like to to a fade-out => fade-in animation, and switch state when the view is invisible.
Here an example with scale animation:
Animated.sequence([
   Animated.timing(
      this.state.scale,
      {
         toValue: 0,
         duration: 300,
         onComplete: () => this.setState({someProp: 'new value'})
      }
   ),
   Animated.timing(
      this.state.scale,
      {
         toValue: 1,
         duration: 300
      }
   ),
]).start();

The feature is implemented with: https://github.com/facebook/react-native/pull/8494

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/add-possibility-to-subscribe-a-sequence-enty-animation-complete
Product Pains has been very useful in highlighting the top bugs and feature requests:
https://productpains.com/product/react-native?tab=top
Also, if this issue is a bug, please consider sending a pull request with a fix.


Move realm object mapping to background queue (to speedup the app) for changeset #4757

Closes #4757

After https://github.com/AlphaWallet/alpha-wallet-ios/issues/4755

After #4755

Could you have mixed up the number? :)


Question command: Update verbiage

Change description of the simpleCommands.js question! command, and update the associated test
Complete the following REQUIRED checkboxes:

[x] I have thoroughly read and understand The Odin Project Contributing Guide
[x] The title of this PR follows the location of change: brief description of change format, e.g. Callbacks command: Update verbiage

Complete the following checkboxes ONLY IF they are applicable to your PR. You can complete them later if they are not currently applicable:

[x] I have ensured all tests related to any command files included in this PR pass, and/or all snapshots are up to date

1. Because:
After a conversation regarding the possibility of changing the question command, the following prompt was accepted as a possible change.
2. This PR:
Updates the question prompt and the associated test.

@mgrigoriev8109 Hey! can you please attach a screenshot of what this looks like in chat?

Sure thing @I3uckwheat, let's see if this works.

Updated the command and associated test, this is what it currently looks like.


Run Full Stack Asset Transfer Guide tests on GHA

This PR runs the full stack asset transfer scenario tests on GitHub Actions.
🐢🐢🐢
🐇🐇🐇🐇🐇🐇🐇🐇🐇
Signed-off-by: Josh Kneubuhl<EMAIL_ADDRESS>

@jkneubuh I merged, but remember git commit --amend is preferable to making multiple commits :-)


docs(*): add details for hello world example

Add instructions for a quick set-up of a stand-alone hello world hyper server.
Closes #1265

[ ] The commit messages match the guidelines in https://github.com/hyperium/hyper/blob/master/CONTRIBUTING.md#git-commit-guidelines

Thanks for submitting the PR!
I'm curious, was it difficult to understand how the example worked without instructions like these? Or without seeing https://hyper.rs/guides?

I had no problems with the example. However, there are some people who read our README, see the line "See the Hello World example for a toy server using hyper.", clicked to see the file and do not immediately know how to get it running, as evidenced by issue #1265

Hm, sure. It probably makes most sense then to just have the README link to self-contained example in the guides.

The README has been updated by removing that line, and emphasizing looking at the guides instead. Ideally, there is only 1 place that needs to be kept up-to-date. Thanks for writing this up, though!

Ok cool!


Thoughts on repo & release management

I noticed two things that could cause surprises down the road:

The VERSION in dev doesn't reflect that it's a dev branch. This might cause confusion for users running on a checkout and reporting errors. Adding a -dev suffix until release should be a good safety measure

The master branch doesn't contain the commit history. This is a bit counterintuitive since informed users might want to check how a specific issue has been fixed - picking through the complete release-diff isn't very helpful in this regard. The dev branch seems to contain the complete history but this isn't assured to the user.

Good call on the version.  I'll do something about that.
Backrest uses the gitflow model which maintains two histories: release and development.  This would be worth adding to the docs to make it clear, though.

Oh, didn't know about gitflow - thanks, makes sense! Adding a pointer to it would be helpful!

I thought about it and I don't think having a special dev version makes sense in the gitflow model.  The idea is that master always holds the last released version and that dev can be released at any time without modification.
Since master is also the default branch, nobody should get a dev version unless they checkout the dev branch.  In that case will a version number really stop them?

Repo & release management documented in 5fce709.

Since master is also the default branch, nobody should get a dev version unless they checkout the dev branch. In that case will a version number really stop them?

Depends on your release cadence and how adventurous your users are ;)
I currently tail dev and reset the version number by hand as to not mislead any colleagues. In the end it's all about reducing confusion.

Sure, but it also increases the chances of introducing a dev version into master.  I may decide to renumber a release but there's generally no need.
My stance is that only power-users like you should even consider tailing dev and then they'll know what to do.  And I'm always happy to cut a release if there's need.  That's the benefit of having a stable dev branch.
Anyway - I'll keep thinking about it but for now leave as is.

:+1:


The renamed blob doesn't display after renaming one leased ADLS Gen2 blob

Storage Explorer Version: 1.10.1
Build: 20191029.11
Branch: rel/1.11.0
Platform/OS: Windows 10/ Linux Ubuntu 19.04/macOS High Sierra
Architecture: ia32/x64
Regression From: Not a regression
Steps to reproduce:

Expand one ADLS Gen2 storage account -> Blob Containers.
Create a new blob container -> Upload a blob to it -> Acquire lease for the blob.
Try to rename this blob and check the result.

Expect Experience:

The renamed blob shows well.
Fail to delete the original leased blob.

Actual Experience:
The renamed blob doesn't display.
More Info:

The renamed blob doesn't display after manually refresh.
This issue doesn't reproduce for one non-ADLS Gen2 blob.

@ v-limu as far as we can see, rename fails if you try to rename a leased blob. Can you check the activity log to see whether or not the rename worked?

Hi @MRayermannMSFT .

The log shows 'Failed to rename....'' in Activities.
The process of renaming is that create a new blob then delete the original blob. So try to rename one leased ADLS Gen2 blob. the result is that create one new blob (the renamed blob shows well in editor) and fail to delete the original blob.

Hi @MRayermannMSFT Please help to take a look. Thanks in advance!

The activity log details shows:

"message": "There is currently a lease on the resource and no lease ID was specified in the request.\nRequestId:2edbc025-801f-0059-4fb3-a5cbf8000000\nTime:2019-11-28T06:20:54.2933742Z",

For the second point above. The mechanism of renaming is for one regular leased blob. So is it the same for one leased ALDS Gen2 blob?

The error detail is clear:
"message": "There is currently a lease on the resource and no lease ID was specified in the request
For the rename action, it use different APIs between HNS-blobs and regulare blobs.


Cached engine with custom entrypoint working on debug but not on profile or release

Hi, I'm caching a flutter engine to reuse in another Activity. On debug mode it's working but it isn't on profile or release. I think that maybe it's about tree-shaking in my main.dart but don't know why because I'm already use @pragma annotation.
This error is blocking me for reusing the cached engine.
Steps to Reproduce

Added android:name=".MyApplication" in application tag in AndroidManifest.xml
Created MyApplication class

package productivity.timetracker.mytime

import android.app.Application
import io.flutter.embedding.engine.FlutterEngine
import io.flutter.embedding.engine.FlutterEngineCache
import io.flutter.embedding.engine.dart.DartExecutor
import io.flutter.view.FlutterMain.findAppBundlePath

class MyApplication : Application() {
    lateinit var flutterEngine : FlutterEngine

    override fun onCreate() {
        super.onCreate()

        // Instantiate a FlutterEngine.
        flutterEngine = FlutterEngine(this)

        // Start executing Dart code to pre-warm the FlutterEngine.
        flutterEngine.dartExecutor.executeDartEntrypoint(
            DartExecutor.DartEntrypoint(findAppBundlePath(),"mainLockScreen")
        )

        // Cache the FlutterEngine to be used by FlutterActivity.
        FlutterEngineCache
            .getInstance()
            .put("LockScreenEngine", flutterEngine)
    }
}

Added custom method in main.dart

@pragma('vm:entry-point')
void mainLockScreen() {
  debugPrint("mainLockScreen");
  ..... runApp...

}

Expected results: App runs normally as well as in debug mode
Actual results:
E/flutter (25371): [ERROR:flutter/shell/common/shell.cc(94)] Dart Unhandled Exception: NoSuchMethodError: No top-level getter 'mainLockScreen' declared.
E/flutter (25371): Receiver: top-level
E/flutter (25371): Tried calling: mainLockScreen, stack trace: #0      NoSuchMethodError._throwNew (dart:core-patch/errors_patch.dart:218)
E/flutter (25371):
E/flutter (25371): [ERROR:flutter/runtime/dart_isolate.cc(718)] Could not resolve main entrypoint function.
E/flutter (25371): [ERROR:flutter/runtime/dart_isolate.cc(202)] Could not run the run main Dart entrypoint.
E/flutter (25371): [ERROR:flutter/runtime/runtime_controller.cc(384)] Could not create root isolate.
E/flutter (25371): [ERROR:flutter/shell/common/shell.cc(574)] Could not launch engine with configuration.

flutter doctor:
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 2.8.1, on Microsoft Windows [versÃ£o 10.0.19043.1466], locale pt-BR)
[√] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.9.2)
[√] Android Studio (version 2021.1)
[√] VS Code (version 1.63.2)
[√] Connected device (4 available)
• No issues found!

Found an issue that is related to the problem #91841 , going back to version 2.5.3 solved the issue

That is correct. Closing this as a duplicate of https://github.com/flutter/flutter/issues/91841


Introduce support for something similar to "caffeinate" on macOS

📝 Provide a description of the new feature
What is the expected behavior of the proposed feature?  What is the scenario this would be used?
The idea is fairly simple - on macOS, there is a tool called caffeinate, that enables one to keep the computer from going to sleep. There is no such thing on Windows. There are hacky ways of doing this with a PowerShell script that constantly triggers a SCROLL LOCK call, but that is putting a bandaid on the real issue. A cleaner approach would be working with the Windows power management APIs. I can envision a custom power plan created, and then use PowerSetActiveScheme to get it to work.
If there are no resources on the team, I am happy to work together to make a pull request with the feature.

If you'd like to see this feature implemented, add a 👍 reaction to this post.

Great idea, already logged.
https://github.com/microsoft/PowerToys/issues/4246


Make gradle plugin to be jsonschema2pojo official plugin

See https://github.com/joelittlejohn/jsonschema2pojo/issues/1070#issuecomment-650546141

@eirnym  do you know when you will be able to review this MR ?

@eirnym is there active development here and this will be the official plugin, or not?
It is odd if it is said so but not really developed further?
Cannot see any responses from you either... 🤔


chore: remove async execution from grapqhl

Purpose

How does the solution address the problem

Changes made

prnet cleaned-up successfully


[PipeMethodCalls] Update package name

Overview: Due to security reasons with Coveo, I updated the package name to Coveo.PipeMethodCalls.
Next steps:

Once this PR is merged, we'll need to trigger a build in https://ctbuilds.dev.cloud.coveo.com/view/Connectors/job/Connectors_Publish_PipeMethodCalls_Nuget/ to create the Nuget package with the new name.
Then, we'll need to update the new package name in our connectors projects that use this library.

JIRA: https://coveord.atlassian.net/browse/CTCORE-7734

@ggingras @aveilleux @comagnan Hi guys! If you can check this PR out when you can, that'd be great! Super simple one ;)


WARNING: C:\Users\Administrator\workspace\xgboost-win64_release_1.0.0\src\learner.cc:328:  Parameters: { n_estimators } might not be used.    This may not be accurate due to some parameters are only used in language bindings but   passed down to XGBoost core.  Or some parameters are not used but slip through this   verification. Please open an issue if you find above cases.

Thanks for participating in the XGBoost community! We use https://discuss.xgboost.ai for any general usage questions and discussions. The issue tracker is used for actionable items such as feature proposals discussion, roadmaps, and bug tracking.  You are always welcomed to post on the forum first :)
Issues that are inactive for a period of time may get closed. We adopt this policy so that we won't lose track of actionable issues that may fall at the bottom of the pile. Feel free to reopen a new one if you feel there is an additional problem that needs attention when an old one gets closed.
For bug reports, to help the developer act on the issues, please include a description of your environment, preferably a minimum script to reproduce the problem.
For feature proposals, list clear, small actionable items so we can track the progress of the change.

Closing this, as it lacks the description of what went wrong.

The parameter is only used in sklearn interface, on native interface see the document of train method.


Going to parent folder with keybinding doesn't update hints

Reproduction:
Ctrl+O
Ctrl+U
What I see:
Suggestions didn't change
What I expect:
Suggestions changed to the parent directory
Note:
If you go to parent directory with .. then it works correctly

Thanks for the bug report! I can confirm that this appears to be broken - will investigate as soon as I find time to do so, hopefully within a week 👍

:tada: This issue has been resolved in version 0.5.0 :tada:
The release is available on:

Visual Studio Marketplace
GitHub release

Your semantic-release bot :package::rocket:


Added default and alternative search styles

Implemented the ideas of @raxod502 in https://github.com/raxod502/ctrlf/issues/83#issuecomment-774708394
* ctrlf.el (ctrlf-style-alist): Added `:fallback` field.
(ctrlf-mode-bindings): Update binding to use default and alternative
search functions.
(ctrlf-forward-default, ctrlf-backward-default)
(ctrlf-forward-alternate, ctrlf-backward-alternate): New functions.
(ctrlf-forward, ctrlf-backward): Add fallback argument.
(ctrlf-forward-literal, (ctrlf-backward-literal, ctrlf-forward-regexp)
(ctrlf-backward-regexp, ctrlf-forward-symbol): Refactor.

Done!


Macro: Parsing string fail when #{{...}} is inside the string

Parser got wrong while parsing macro with string
macro do_something(a, b)
  "{{a.id}}#{{b.id}}"
end

puts do_something("1", "2") #Expected: 1#2

This will fail to compile, as macro will ignore #{{b.id}}
However I'm not sure I'm doing it right. I've tried with different position of backslashes  \ to escaping it, but nothing is working.

@anykeyh
It would be fixed in next release. As a workaround you can use this.
  "%s#%s" % [{{a.id}}, {{b.id}}]

Better workaround for performance:
macro do_something(a, b)
  "#{{{a.id}}}##{{{b.id}}}"
end

puts do_something("1", "2") # puts "1#2"

Better workaround for performance again! (nothing at runtime):
macro do_something(a, b)
  "{{a.id}}{{'#'.id}}{{b.id}}"
end

puts do_something "1", "2" # => "1#2"

Having stumbled across this issue, I find it only intuitive that "#{{foo}}" is interpreted as a macro expansion prefixed by # and not string interpolation of a tuple. Macro expressions are on a higher level than other code so they should have precedence.
So #5288 is IMO wrong as it provides a workaround for what should be valid by default.

There is another solution: We could completely disable macro expansion inside literals. I don't think that is a necessary feature. There doesn't even seem to be a spec for that, so maybe it's something that just happens to be but nobody really thought about it?
The thing is: There are currently two types of expansions in string literals: string interpolation (#{}) and macro expansion ({{}}). The latter is rarely talked about and probably many developers are not aware of it. It is still applied in some occasions in stdlib and probably also in shards.
If macro expansions were removed from literals, it would make the language a bit simpler. They can easily be replaced by interpolation, either as a macro or at runtime.
# macro expansion
"foo {{ bar.id }}"
# macro string interpolation
{{ "foo #{bar.id}" }}
# runtime interpolation
"foo #{ {{ bar }} }"

The latter has a small performance impact because the string is composed at runtime. But that can be mitigated by using a  macro string interpolation. Apart from that, all three variants should be equivalent.


Fabric crash 1.19.2

shouldersurfing->@Redirect::doRenderCrosshair(Lnet/minecraft/class_5498;)Z with priority 1000, already redirected by zergatul.cheatutils.mixins.json:common.MixinGui from mod cheatutils->@Redirect::onRenderCrosshairIsFirstPerson(Lnet/minecraft/class_5498;)Z with priority 1000
[19:13:56] [main/ERROR]: [net.fabricmc.loader.impl.launch.FabricLauncherBase#handleFormattedException] Minecraft has crashed!
Pastebin :
https://pastebin.com/gXt7R16R

It's a conflict with some other mod.

Could you join mod discord and test jar I will try to build with fix for that?

Sure could you relink the discord plz?


More hidden-definition tests

Motivation
We've had a few regressions related to hidden-definition-finder not picking up on things it used to. This expands the test suite a bit so that it'll be harder to have those regressions.
Test plan

See included automated tests.

I think they should be reasonably stable but I'm not 100% sure: big changes to our symbol table output might change them, but I don't know how often our changes in practice are going to cause them to change. They don't take long to regenerate—on the order of a minute or so, I think, but I can double-check—so they don't add too much to the overall update_exp time.

Actually, on reflection, it will need to change whenever we add things to the RBI files (as many of those things were already picked up on as hidden methods, and moving them to the RBI files makes them no longer hidden) so it might be more common than I thought. They don't take long to regenerate, though: if you already have the relevant Ruby versions built for testing, then it takes about 7 seconds to regenerate all of them.


3.4.2: cis_hosts_allow_all_ips should accept list instead of string

There can be multiple IP ranges/subnets that would need access to the instance of this AMI in a secured environment. Would be good to have this var as a list rather than a single input.

Hi @Pratima,
are you okay to close this issue?

Closing assuming no answer as yes


add calculations to select model levels to keep

added as an option to level_to_height function, you can now pass levs=(fromlev, tolev). Where fromlev tolev are the indices to sue with isle. The last level included is tolev-1.
lets by default is None so if not slicing the levels can be omitted.


Crash on trying to analyse m68k binary after update

We can consistently crash Binary Ninja on starting the analysis of a m68k binary (using the Motorola 68k Architecture Plugin by Galen Williamson) having just updated from the previous release. Attaching GDB and inspecting state, we see the following stack trace indicating a bug in Binja itself, and the program closes with SIGSEGV:
Thread 34 "binaryninja" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff6904d700 (LWP 349454)]
0x00007fffee68924d in ?? () from /opt/binaryninja/libbinaryninjacore.so.1
sora:/home/dx-mon:gdb-34@None> bt
#0  0x00007fffee68924d in ?? () from /opt/binaryninja/libbinaryninjacore.so.1
#1  0x00007fffee3caf6e in ?? () from /opt/binaryninja/libbinaryninjacore.so.1
#2  0x00007fffee017acf in ?? () from /opt/binaryninja/libbinaryninjacore.so.1
#3  0x00007fffee044eb5 in ?? () from /opt/binaryninja/libbinaryninjacore.so.1
#4  0x00007fffee04d87e in ?? () from /opt/binaryninja/libbinaryninjacore.so.1
#5  0x00007fffee5e4494 in ?? () from /opt/binaryninja/libbinaryninjacore.so.1
#6  0x00007fffee6d3221 in ?? () from /opt/binaryninja/libbinaryninjacore.so.1
#7  0x00007ffff6d01ed0 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#8  0x00007ffff7e01ea7 in start_thread (arg=<optimized out>) at pthread_create.c:477
#9  0x00007fffebb27a2f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Binary Ninja Version: 3.2.3898 Personal, 16354a74
Platform: Debian GNU/Linux 11 (bullseye)
A listing of threads that were running is available on request (there are 40 so it's quite long).

This is quite probably due to a change I made last week, I'll try to get the possible fix pushed ASAP.

Builds >= 3899 contain that fix and appear to be working correctly. I tested on https://github.com/radareorg/radare2-testbins/blob/master/elf/analysis/busybox.m68k which was crashing on 3898 with that plugin.
If you're still experiencing a crash, let us know!

Confirmed, just updated and Binjary Ninja no longer crashes when working with m68k binaries. Many thanks for the quick turnaround!


tests: tenant attach and lack of polling of attachment_status

Test failure after attach; it's a real_s3 with simulate_failures=1 but looking around that test[^1] and our test suite, none of the tenant attaches have polling of attachment_status, some of the tests (not all) are polling until tenant is active.
Related: #5698 (recently merged)
Related: https://neondb.slack.com/archives/C0634NXQ6E7/p1698419362155059 (#investigation-2023-10-27-stuck-project...)
Instead of jumping into implementing this, is there are a reason why we are not dogfooding the attachment_status? I think a clear solution would be to do the things we list in openapi.yml, in this case, poll until attachment_status == "attached", otherwise we risk drift between "some other check" vs. what we expect the control plane to do, and clean up all "tenant is active" polling.
[^1]: The failing assert, logs show metrics reading before attaching completes

This was discussed on Slack: https://neondb.slack.com/archives/C033RQ5SPDH/p1699026222461769?thread_ts=1698950964.766459&cid=C033RQ5SPDH
tl;dr:
I.e., attachment_status was never intended as as general readiness field, but only as a field to indicate progress of the /attach call.

Instead of jumping into implementing this, is there are a reason why we are not dogfooding the attachment_status? I think a clear solution would be to do the things we list in openapi.yml, in this case, poll until attachment_status == "attached", otherwise we risk drift between "some other check" vs. what we expect the control plane to do, and clean up all "tenant is active" polling.

Yeah, we should have been polling for attachment status in the tests.
That'd be better, than, say, polling for state = Active.
Then again, the /attach API will be gone soon, so, I don't think it's worth the time to fix up the tests.

This is probably irrelevant now with the generation service.


feat: adding sdk links to each quickstart guide

Description

Updating each quickstart guide to have a link to our SDKs

Testing required outside of automated testing?

[ ] Not Applicable

Screenshots (if appropriate):

[ ] Not Applicable

Rollback / Rollforward Procedure

[ ] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

:tada: This PR is included in version 1.15.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Link to demo - site has been hijacked or is suspicious

The link in the readme leads to a site http://iyfbodn.com/?dn=easy-markdown-editor.tk... which is not the intended https://easy-markdown-editor.tk

Has the site been hijacked?
To Reproduce
Click the link in the readme or navigate to https://easy-markdown-editor.tk.
Expected behavior
A link leading to an actual demo.

Duplicate of #526


HDR Exposure

I don't know how possible this is in webgl, but it would be nice to be able to have HDR panoramas that can automatically adjust the exposure depending on the overall brightness of what's being looked at. Useful for panoramas where both an interior and exterior are visible.

It's definitely possible and has been something on my wishlist for a while. SpiderGL has a WebGL HDR demo that encodes an image as RGBE within a PNG, using the alpha channel for the exponent. I would tend to implement something similar but use a JPEG for the color data and a second grayscale JPEG for the exponent, to save bandwidth. Then it's just a matter of applying a metering algorithm to the viewable area.

I did some work on figuring out the best way to do this. I ended up creating an implementation based on BoostHDR. Now I just need to integrate it into Pannellum.

@mpetroff Is this still a thing or?

It's still on my list of things to work on.


Authorship module

Hi,
Do somebody has a step by step to add the authorship module on top of vue2editor ?

This issue is stale because it has been open for 60 days with no activity.

This issue was closed because it has been inactive for 7 days since being marked as stale.


Added Android multicast support for Discovery Fixes #2878

This will add support for turning on and off Multicast for Android devices.
It also contains an Android manifest editor that will add the appropriate permissions.

thanks for PR.
@Clancey what's the android manifest editor for?

On android multicast broadcasting is disabled to save battery. The code is there in Discovery, however it's also required to tell the OS that you need permission to do that. If you don't the calls will fail. If you check the docs, unity used to add that automatically for you if you used the old Networking.NetworkTransport.SetMulticastLock. However since Unity doesn't do that automatically for us. We need to or the call fails silently.

I think these two need the #if android  BeginMulticastLock(); EndpMulticastLock();
Maybe those Mirrors Devs/Advisors who do android builds can do a before and after build, to give it a final look over.
@SoftwareGuy you and anyone else you recommend?
Otherwise nicely investigated and put together, Thanks Clancey!

I was trying to avoid riddling the code with #ifdefs. Also I was debating making the 2 methods virtual so they could be overridden easily.

@JesusLuvsYooh I'd have to install the Android development stack for my Unity version and have a before and after thing to confirm it's working or not.

The built in discovery sample does not work on most android devices. You can even run it as is on an Oculus Quest. It just shows up windowed not VR.  You will see how it can't connect until you apply my patch.  Hopefully this can be merged to help others. But I will continue to use it in my project either way.

can anyone confirm if this is good or not?

can anyone confirm if this is good or not?

I did some test and It doesn't work (but maybe the problem is related to Android and something missing)

hi, I added yout code to my project but the discovery sample still doesn't work. I can connect to my PC but can't use my android device as a server. do you have a full running sample? do I need to check anything else? my router is a simple one, without restrictions. the device is a Galaxy Tab A. sometime I got this error from the Android device: AndroidJavaException: java.lang.RuntimeException: MulticastLock under-locked lock thanks

That error means the multilock cast was never locked, so it errored when it tried releasing it. There must be more to the logs before, when it tried to create the multicast lock

can anyone confirm if this is good or not?

I did some test and It doesn't work (but maybe the problem is related to Android and something missing)

Check the generated application manifest. Make sure it added the mutlicast lock. You can also debug the build to make sure it adds it: https://github.com/vis2k/Mirror/pull/2887/files#diff-b8db6271c1a5e274a1ff4834b30cd3b400c8fe5a108f8a91de9132eaf40cf232R45

Noting, this PR may still be a solution for those having Android problems.

Yeah, as Jesus posted above I referenced this PR to the user having issues and it resolved the problem for them.
Just one of the painful things you have to do to support mobile platforms.

can anyone confirm if this is good or not?

It worked flawlessly for me.


Plugin Error - App not Installed

Expected Behaviour
Application Get installed
Actual Behaviour
App not installed
Reproduce Scenario (including but not limited to)
When trying to install an android app that reference the Phonegap-plugin-push version 1.6.3, and i already have an application that use the plugin "com.phonegap.plugins.pushplugin". the result is App not installed.
If i remove the other application, the app get installed successfully
How we could fix that ?

@eliea85 This really isn't enough info for me to debug. What is the error message when you try to install? How do you try to install? Please see issue guidelines.

My mistake,
I just changed the widget id in the Config.xml and it works.


Change ErrInvalidHandle to ErrAlreadyClosed

ErrInvalidHandle is better named ErrAlreadyClosed.
Signed-off-by: Darren Stahl<EMAIL_ADDRESS>

LGTM


Download method not wait to complete

Package
dio
Version
5.1.1
Output of flutter doctor -v
[✓] Flutter (Channel stable, 3.7.12, on macOS 13.3.1 22E261 darwin-arm64, locale en-TR)
    • Flutter version 3.7.12 on channel stable at /Users/ibrahim/tools/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 4d9e56e694 (7 days ago), 2023-04-17 21:47:46 -0400
    • Engine revision 1a65d409c7
    • Dart version 2.19.6
    • DevTools version 2.20.1

[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
    • Android SDK at /Users/ibrahim/Library/Android/sdk
    • Platform android-33, build-tools 32.1.0-rc1
    • Java binary at: /Users/ibrahim/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/222.4459.24.2221.9862592/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.1)
    • Android Studio at /Users/ibrahim/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/221.6008.13.2211.9619390/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

[✓] Android Studio (version 2022.2)
    • Android Studio at /Users/ibrahim/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/222.4459.24.2221.9862592/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] VS Code (version 1.77.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (3 available)
    • Iphone7 Ofis (mobile) • 2375e3716bb5cc7b915c93fa8e122f93f47e71d3 • ios            • iOS 16.4.1 20E252
    • macOS (desktop)       • macos                                    • darwin-arm64   • macOS 13.3.1 22E261 darwin-arm64
    • Chrome (web)          • chrome                                   • web-javascript • Google Chrome 112.0.5615.137
    ! Error: Iphone7 Ofis is busy: Making Ratel’s iPhone ready for development. Xcode will continue when Iphone7 Ofis is finished. (code -10)

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Dart Version
2.19.6
Steps to Reproduce
Future<void> downloadFileWithDio(String url, String savePath) async {
  final dio = Dio();

  try {
    await dio.download(url, savePath, onReceiveProgress: (received, total) {
      final progress = (received / total) * 100;
      print('Download progress: $progress%');
    });

    print('File downloaded successfully: $savePath');
  } on DioError catch (e) {
    print('Failed to download file: $e');
  }
}

call this function for large file 50+ MB. I don't know it is happening with smaller files or not.
Expected Result
Complete the download and prints "File downloaded successfully: $savePath".
Actual Result
Starts the download, response code is 200 and prints "File downloaded successfully: $savePath", before wait to complete download.
I think the Dio download method actually completes the future when the headers are received, not when the entire download is complete.

We have a couple of unit tests that await for downloading to complete. I'm not sure the method can be interrupted by our implementation, but it'll seem more like the downloading has been aborted due to some reason during the process.

@AlexV525 Downloading was not aborted, it returns 200 OK before completes then it continues to download and triggers "onReceiveProgress" then complete the download. You can try my example code with https://ratel.sfo3.cdn.digitaloceanspaces.com/example_big_file.bin
I guess It is not only my issue, see: https://github.com/cfug/dio/issues/1327
I can download the same file with this code, so I don't think it is related with OS or Server issue.
  Future<void> _downloadFile() async {
    final file = File(savePath);
    final client = HttpClient();

    try {
      final request = await client.getUrl(Uri.parse(url));
      final response = await request.close();
      final total = int.parse(response.headers.value(HttpHeaders.contentLengthHeader) ?? '0');

      if (response.statusCode == 200) {
        int received = 0;
        final sink = file.openWrite();
        await for (final data in response) {
          received += data.length;
          progress = ((received / total) * 100).toInt();
          // print('Download progress: $progress%');
          sink.add(data);
        }
        await sink.close();

        print('File downloaded successfully: $savePath');
        _downloadFileCompleter.complete();
      } else {
        print('Failed to download file: ${response.statusCode}');
        _downloadFileCompleter.completeError(Exception("Hata"));
      }
    } catch (e) {
      print('Failed to download file: $e');
      _downloadFileCompleter.completeError(e);
    } finally {
      client.close();
    }
  }

Not sure if anyone else had this problem but I was getting an
OS Error: The process cannot access the file because it is being used by another process. while trying to rename a file immediately after a download.
 final dio = Dio();

  Future<void> downloadFile(String url,
      {String saveLocation = 'largeFile.bin'}) async {
    cachedTempDirectory = await getTemporaryDirectory();
    const tempExtension = '.tmp';

    File saveFile =
        File("${cachedTempDirectory!.path}/$saveLocation$tempExtension");

    final response = await dio.download(url, saveFile.path);
    saveFile = await saveFile.rename(saveFile.path
        .substring(0, saveFile.path.length - tempExtension.length));
  }

I was able to fix it by adding a mutex map around the download and rename operation.
  final dio = Dio();
  final _inProgressMutexMap = <String, Mutex>{};

  Future<void> downloadFile(String url,
      {String saveLocation = 'largeFile.bin'}) async {
    final tempDirectory = await getTemporaryDirectory();
    const tempExtension = '.tmp';

    File saveFile = File("${tempDirectory.path}/$saveLocation$tempExtension");

    final mutex = _inProgressMutexMap.putIfAbsent(saveLocation, () => Mutex());
    final response = await mutex.protect(() async {
      final response = await dio.download(url, saveFile.path);
      saveFile = await saveFile.rename(saveFile.path
          .substring(0, saveFile.path.length - tempExtension.length));
      return response;
    });
    if (!mutex.isLocked) {
      _inProgressMutexMap.remove(saveLocation);
    }
  }

Please attach more info or a minimal example if you can reproduce it consistently.


fix(readme): add a warning on using getAccessTokenSilently before isLoading is set to false #392

Description
Adds a warning on getAccessTokenSilently usage before isLoading is set to false in the usage section in the readme
References

#392

Checklist

[x] I have added documentation for new/changed functionality in this PR or in auth0.com/docs
[x] All active GitHub checks for tests, formatting, and security are passing
[x] The correct base branch is being used, if not master

Probably a better solution is to add a warning in the console whenever someone uses the getAccessTokenSilently function before isLoading is set to false in the SDK

Closing, see https://github.com/auth0/auth0-react/issues/392#issuecomment-1239224816


Support upsert update's argument

We have basic support already, but we should add more tests for corner cases.

I played around for a bit with upsert and discovered some bigger issues with update itself; please check
https://github.com/FerretDB/FerretDB/pull/546


Traffic light detection problems with lgsvl

When I am trying to detect traffic light in Borregas Ave map in lgsvl, it keeps detecting traffic lights even when I place a truck in front of the ego vehicle to block both the 6mm and 12mm camera.
And there is no message in apollo/perception/traffic_light channel when I run the simulation in CubeTown map. But after I add HD map annotation base_map.bin under modules/map/data/CubeTown, the module keeps detecting traffic lights even I block the cameras.
Does the traffic light detection module rely on the HD map annotation and does not consider the camera input at all?
The simulator version I am running is 2020.06. The Apollo version I am using is the master branch
System information

OS Platform and Distribution (e.g., Linux Ubuntu 18.04): Ubuntu 16.04.6 LTS
Apollo installed from (source or binary): source
Apollo version (3.5, 5.0, 5.5, 6.0): 6.0
Output of apollo.sh config if on master branch:
[INFO] Apollo Environment Settings:
[INFO]     APOLLO_ROOT_DIR: /apollo
[INFO]     APOLLO_CACHE_DIR: /apollo/.cache
[INFO]     APOLLO_IN_DOCKER: true
[INFO]     APOLLO_VERSION: master-2020-10-12-7978438212
[INFO]     DOCKER_IMG: dev-x86_64-18.04-20200926_1057
[INFO]     APOLLO_ENV:  STAGE=dev USE_ESD_CAN=false
[INFO]     USE_GPU: USE_GPU_HOST=1 USE_GPU_TARGET=1
[INFO] Usage: /apollo/scripts/apollo_config.sh [Options]
[INFO] Options:
[INFO]     -i|--interactive      Run in interactive mode
[INFO]     -n|--noninteractive   Run in non-interactive mode
[INFO]     -h|--help             Show this message and exit

Steps to reproduce the issue:

I built the Apollo 6.0 from master branch and run ./scripts/bootstrap_lgsvl.sh in the docker
In the DreamView, I chose Mkz Lgsvl mode, Lincoln2017MKZ (Apollo 5.0) vehicle and Borregas Ave map

Supporting materials (screenshots, command lines, code/script snippets):
normal traffic light detection

after blocking the cameras

Hi, are u using lgsvl's groundtruth traffic light sensor ?
The groundtruth sensor does not use the camera images to detect. It will always produce the output when there are traffic lights nearby.
If not using the groundtruth sensor, the Apollo's traffic light module might have projected the groundtruth location of the signals onto the camera images.
Thus it can search for the signals smaller region instead of the whole image.

Thank you for the reply.

are u using lgsvl's groundtruth traffic light sensor ?

I don't think I am using lgsvl's groundtruth traffic light sensor. My vehicle does not have "Signal Sensor" (Topic: /simulator/ground_truth/signals)  included.
The vehicle is just publishing Main Camera (Topic: /apollo/sensor/camera/front_6mm/image/compressed) and Telephoto Camera to Apollo (Topic: /apollo/sensor/camera/front_12mm/image/compressed).

If not using the groundtruth sensor, the Apollo's traffic light module might have projected the groundtruth location of the signals onto the camera images.
Thus it can search for the signals smaller region instead of the whole image.

So the TrafficLightBox messages (in particular, traffic_light_debug.projected_roi  and traffic_light_debug.rectified_roi) from /apollo/perception/traffic_light channel are the location on the camera images, right? But I find these messages unchanged all the time (not matter the cameras can see the traffic lights or not).

There is do traffic light info in hdmap, apollo will use this info(box) as a ROI. like below in base_map
But I wonder how do you draw the box in simulation, use what info to draw the box?
signal {
  id {
    id: "signal_0"
  }
  boundary {
    point {
      x:<PHONE_NUMBER>619812
      y: 4141593.0089969635
      z: 5.893528938293457
    }
    point {
      x:<PHONE_NUMBER>33081
      y: 4141593.4983654022
      z: 5.893528938293457
    }
    point {
      x:<PHONE_NUMBER>33081
      y: 4141593.4983654022
      z: 4.707310676574707
    }
    point {
      x:<PHONE_NUMBER>619812
      y: 4141593.0089969635
      z: 4.707310676574707
    }
  }
  subsignal {
    id {
      id: "0"
    }
    type: CIRCLE
    location {
      x:<PHONE_NUMBER>5134583
      y: 4141593.2536811829
      z: 5.7004199028015137
    }
  }

Hi, I will try to answer this question.Apollo perception module can get the approximate position of the traffic light by Hdmap, and we crop the patch of ROI then put it to our CNN model to do detection & recognition. So if Hdmap has label of traffic light but CNN can't detection bounding box, we will show the Hdmap roi region as bounding box and traffic light recognized as UNKONWN.

@daohu527 I use the TrafficLightBox message in traffic_light_debug to draw the box over the camera-captured images.

@xiaoMrzhang

So if Hdmap has label of traffic light but CNN can't detection bounding box, we will show the Hdmap roi region as bounding box and traffic light recognized as UNKONWN.

Thank you so much. This helps a lot.

Hi @hzssean @daohu527 @xiaoMrzhang @ntutangyun @hugomatic
To running Apollo 6.0
What does it mean by " NVIDIA Turing GPU is strongly recommended"? Will RTX 3080/3090 (not Turing Architecture) are also good and do a better job than RTX 2080/2080 Ti? I saw other comments that said the faster GPU the better.
If anyone knows the answer please help. I need to order a PC for my project (Apollo 6.0 + a Simulator).
Thank you.


python3Packages.readme_renderer: relax cmarkgfm constraint

Motivation for this change
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 153698 run on x86_64-linux 1

1 package failed to build:

home-assistant

54 packages built:

apache-airflow (python39Packages.apache-airflow)
check_systemd
evdevremapkeys
keepkey_agent (python39Packages.keepkey_agent)
ledger_agent (python39Packages.ledger_agent)
luigi
mailman-web (python39Packages.mailman-web)
mnemosyne
onlykey-agent
python38Packages.ansible-kernel
python38Packages.ansible-runner
python38Packages.apache-airflow
python38Packages.gtts
python38Packages.keepkey_agent
python38Packages.langcodes
python38Packages.language-data
python38Packages.ledger_agent
python38Packages.libagent
python38Packages.mailman-web
python38Packages.marisa-trie
python38Packages.nagiosplugin
python38Packages.ndjson
python38Packages.postorius
python38Packages.pypiserver
python38Packages.python-daemon
python38Packages.readme
python38Packages.readme_renderer
python38Packages.restview
python38Packages.salmon-mail
python38Packages.toggl-cli
python38Packages.trezor_agent
python38Packages.twine
python38Packages.wordfreq
python39Packages.ansible-kernel
python39Packages.ansible-runner
python39Packages.gtts
python39Packages.langcodes
python39Packages.language-data
python39Packages.libagent
python39Packages.marisa-trie
python39Packages.nagiosplugin
python39Packages.ndjson
python39Packages.postorius
python39Packages.pypiserver
python39Packages.python-daemon
python39Packages.readme
python39Packages.readme_renderer
python39Packages.restview
python39Packages.salmon-mail
python39Packages.toggl-cli
trezor_agent (python39Packages.trezor_agent)
twine (python39Packages.twine)
python39Packages.wordfreq
wlc

@ofborg build home-assistant

@ofborg build home-assistant


Merge 3.0 => 3.1

CentOS Production passed on re-run but AzDo isn't updating the status (https://dev.azure.com/dnceng/public/_build/results?buildId=434521&view=logs&jobId=935c00b8-5de8-597d-a783-42e7f079746c).  Merging.


WIP: store status

almost done. still missing:

[ ] tests
[ ] i18n
[ ] backend: deleting pickups when status is set to archived

Love the new store status UI!
The co-operating stores are the same colour as users though now, so they are not so clearly separated. Maybe it's ok though.

If users are active (all users right now, there is no non-active status), they can have the same color as cooperating stores?

Would be great to get this merged soon, looks so close!

Yep it's very nice! But can you maybe find another color so that active users and active stores don't look the same after all..? 😋 What about some kind of orange for users?

What if users can also be inactive in future?

Make them red but using a different shade. Or is there a limit to the amount of colors in use?

My feeling is that people are able to figure out the meaning 3-5 colors without much explanation. If we add more, we should add a legend, but there's not so much space on the minimap.
Also it would be nice to check at some point if people with color blindness are able to see a difference between the markers (and other highlight colors).

Ooops, there are some conflicts now.. seems a bit annoying to resolve, might take some more thinking..

I'm gunna have a look into this and try and get it working

Ok, I think should be ready, I did:

fixed conflicts from master
fixed broken tests
renamed delete/undelete to archive/restore (as that is what it does)
made archive/restore only patch the status field
added everything into i18n I could find
moved store ui options to src/services/storeStatus.js
capitalized and slightly reworded status text

I did not:

change the colours

Mobile store list is missing the status icons
Otherwise looks great, would be happy to merge soon.


Support for adding dynamic recovery filters

I have a need to ignore certain instances (mysql/vitess in a kubernetes pod) when doing automated recovery with orchestrator. I could only find hostname filters (RecoveryIgnoreHostnameFilters) and while my hostnames do include a pattern I could filter on, setting MySQLHostnameResolveMethod: @@hostname conflicts with my IP only setup.
It would be awesome if I could setup something to run a filter query on the failover target to validate its eligibility. For example, if I could select @@hostname and filter hosts that match a certain regex, would be perfect.
Alternatively allow setting a "display name" field via various methods (like @@hostname etc), and then have a matching RecoveryIgnoreDisplayNameFilters list.
It's also entirely possible I missed a config prop and this can easily be done in another way. Any ideas? Thanks!

@hmcgonig I believe you wish to look at something else: promotion-rules.
If I understand correctly, it's not that you wish to ignore those servers in general, you just never want them to be promoted. Is that correct?
Please see https://github.com/github/orchestrator/blob/master/docs/deployment.md#adding-promotion-rules
For each server, you will declare that its promotion rule is must_not. This happens dynamically. E.g. we have backup servers or testing servers in production we never want to promote, so we set up this cron entry in those hosts:
orchestrator-client -c register-candidate -i $(hostname) --promotion-rule must_not

I should add a promotion rule expires after an hour. You will want to continuously execute that in cron, as in:
*/5 * * * * /usr/bin/orchestrator-client -c register-candidate -i $(hostname) --promotion-rule must_not

This is perfect, exactly what I was looking for. Thank you so much.

So, I just tried this and noticed that using DetectPromotionRuleQuery overrides any promotion rules set via the API. I ended up solving my problem by modifying the query.
I run with vitess, so the default set of vitess config had
SELECT value FROM _vt.local_metadata WHERE name='PromotionRule'
which I changed to
SELECT CASE WHEN @@hostname REGEXP '.*(-backup)$' THEN 'must_not' ELSE value END FROM _vt.local_metadata WHERE name='PromotionRule'
this way anything with a .*-backup hostname is automatically set to PromotionRule: must_not

You are correct, and DetectPromotionRuleQuery overrides api. I should have connected the dots when you said you were using vitess.
Your solution is :+1:


Reduce Duplication Between SatisfyingAssignment and WitnessCS Structs

It has been observed that the SatisfyingAssignment (in this repo) and WitnessCS (in bellpepper) structs have significant overlap in their definitions. This duplication can lead to maintenance challenges and potential inconsistencies.
Similarities:

Purpose: Both structs serve as a ConstraintSystem that calculates witness values for a concrete instance of an R1CS circuit.
Fields: Both structs have fields input_assignment and aux_assignment.
Methods: Most methods in both structs are identical in both functionality and structure. This includes the implementation of the ConstraintSystem trait, as well as auxiliary methods such as scalar_inputs and scalar_aux.

Differences:

Generics:

SatisfyingAssignment is parameterized over G: Group and uses G::Scalar.
WitnessCS is parameterized over Scalar where Scalar: PrimeField.

Attributes & Derivations:

WitnessCS has the #[derive(Debug, Clone, PartialEq, Eq)] attribute, which provides automatic implementations of the Debug, Clone, PartialEq, and Eq traits.
SatisfyingAssignment provides its own fmt::Debug and PartialEq implementations and does not derive Clone or Eq.

Refactoring Potential:

Shared Trait or Base Struct: Given the similarity in behavior, a shared trait or a base struct could be created to capture the common functionalities. The specific implementations (SatisfyingAssignment and WitnessCS) can then extend or implement this shared definition.
Consolidate Attributes & Derivations: Determine whether SatisfyingAssignment requires its own Debug and PartialEq implementations. If not, it could use the derived implementations similar to WitnessCS.
Type Alias or Adaptors: If the core difference lies in the type parameters (G::Scalar vs. Scalar), consider type aliasing or using adaptors to harmonize the two.

i can take this!

Ok, got into looking at this today!
Given that:

Group::Scalar should be able to be seen as satisfying PrimeField by the compiler, given the appropriate type annotations and constructor hints

https://github.com/lurk-lab/arecibo/blob/170818e04d76f0f4c71ca797c62db4782cfae8e2/src/traits/mod.rs#L37-L43

The custom implementations for Debug and PartialEq were found to be unnecessary as the default implementations provided the required functionality, as verified by running the following commands with updated code:

cargo test --release
cargo run --release --example minroot
cargo nextest run --profile ci --workspace --cargo-profile dev-ci

The implementation of ConstraintSystem across SatisfyingAssignment in arecibo and WitnessCS are the same

I see two available options, where the deciding factor is how likely is SatisfyingAssignment going to need to diverge from WitnessCS going forward.
Newtype Pattern: Defining SatisfyingAssignment Struct
The most flexible or adaptable approach is to define SatisfyingAssignment like so:
pub struct SatisfyingAssignment<G: traits::Group>(WitnessCS<<G as Group>::Scalar>);

We would implement ConstraintSystem on our new type and simply call into the WitnessCS implementation. Further, we would expose aux_assignment and input_assignment as methods that would call into the wrapped WitnessCS instance. This both consolidates behavior and gives future developers the ability to differentiate if they so need.
Type Alias approach
The most straightforward way to consolidate shared behavior is to type alias SatisfyingAssignment in arecibo, ala
pub type SatisfyingAssignment<G> = WitnessCS<<G as Group>::Scalar>;

Unfortunately this 'direct' consolidation comes with it a small bit of a refactor where calls like this
let mut cs: SatisfyingAssignment<G> = SatisfyingAssignment::new();

turn into calls like this:
let mut cs: SatisfyingAssignment<G> = SatisfyingAssignment::<G>::new();

This occurs because the type alias introduces an intermediate step, requiring a bit more complexity for the programmer, as they have to be more explicit about the generic type. For example, specifying  helps the compiler understand the exact type being referred to.
In both cases, we would also need to do a small refactor in bellpepper where we make the WitnessCS struct's fields public, outside of just the crate.
I prefer the first approach, but perhaps someone more familiar with the codebase would think the second would be better suited.
Pending feedback, I can get started on a PR!

The Lurk-lab organization owns both bellpepper and lurk-rs. As a result, making PRs to bellpepper is acceptable.
The Type Alias approach is preferred as it provides more simplicity, eliminating the need to expose newtype methods.
For the compiler, only one type of information is required, which can be either:

let mut cs = SatisfyingAssignment::<G>::new();

OR
let mut cs: SatisfyingAssignment<G> = SatisfyingAssignment::new();

That seems fine!

Closed in #89


python3Packages.jupyterlab_server: create temp home for tests

Description of changes
Unbreaks jupyterlab_server, which is currently broken on Hydra. See also https://github.com/NixOS/nixpkgs/pull/179190#issuecomment-1167830207.
cc @friedelino (who posted the above comment)
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

@ofborg build python3Packages.jupyterlab_server

LGTM


Zipkin server unable to consume span events from kafka transport

Hi Team,
Services are able to publish span messages to kafka using spring cloud sleuth but zipkin server is not able to consume the messages from kafka. Here is my details.
dependencies
  compile "io.zipkin.java:zipkin-server:2.12.5"
  compile "io.zipkin.java:zipkin-autoconfigure-ui:2.12.6"
  compile "org.springframework.cloud:spring-cloud-starter-stream-kafka:2.1.0.RELEASE"

ApplicationClass
@SpringBootApplication
@EnableZipkinServer
public class ZipkinServiceApplication {
    @Bean
    ServletWebServerFactory servletWebServerFactory(){
        return new TomcatServletWebServerFactory();
    }

    public static void main( String[] args ) {
        SpringApplication.run(ZipkinServiceApplication.class, args);
    }
}

application.properties
spring:
  cloud:
    stream:
      kafka:
        binder:
          brokers: localhost:9092
          zkNodes: localhost:2181

Am i missing anything ? Zipkin is not able to consume messages from kafka and store it into the in-memory span store. So tracing is not showing on zipkin ui.

A couple things:

Is there a reason you can't run the server that we release as an executable jar and docker container? Our release includes kafka support built in https://github.com/openzipkin/zipkin/tree/master/zipkin-server#zipkin-server
@EnableZipkinServer is deprecated and our small community is not able to provide support for building custom servers

If after trying our server releases you still have problems please reach out to us in our support room: https://gitter.im/openzipkin/zipkin or on our users mailing list<EMAIL_ADDRESS>

@devinsba Even i tried with zipkin kafka collector but still having same issue. I am running zipkin server as a spring boot fatjar.
FYI : Same thing is working over Web transport. But stopped working when changed to Kafka.
dependencies
  compile "io.zipkin.java:zipkin-server:2.12.5"
  compile "io.zipkin.java:zipkin-autoconfigure-ui:2.12.6"
  compile "io.zipkin.java:zipkin-autoconfigure-collector-kafka:2.12.6"

application.properties
zipkin:
  collector:
    kafka:
      bootstrap-servers: localhost:9092
      topic: zipkin
      group-id: zipkin
      streams: 1

Again, we can't support custom servers. Please try with the default server before trying to build anything custom

@devinsba Sure. Thanks.


Show progress dialog during startup

This change adds a standard shell progress dialog during startup to give feedback to the user that we are gathering all the items that were selected (including items in subfolders).  This allows the user to know we are still doing work as well as provide a means to cancel the operation.

Applies to #9254

Minor nit: to be consistent, can we use the same .ico that we use in the Shell right-click context menu in the dialog topbar?

Minor nit: to be consistent, can we use the same .ico that we use in the Shell right-click context menu in the dialog topbar?

@chrdavis
Can you chage the word "fixes" to "Applies to". We don't use the wording "fixes" to not auto close the issue.

@chrdavis
Can you chage the word "fixes" to "Applies to". We don't use the wording "fixes" to not auto close the issue.

@chrdavis
Can you chage the word "fixes" to "Applies to". We don't use the wording "fixes" to not auto close the issue.

Done

@chrdavis
Can you chage the word "fixes" to "Applies to". We don't use the wording "fixes" to not auto close the issue.

Done

Any update on this review?

Any update on this review?

@chrdavis
is it expected that the progress dialog stays open for about 1 second after the PowerRename dialog opens?

@chrdavis
is it expected that the progress dialog stays open for about 1 second after the PowerRename dialog opens?

@chrdavis
is it expected that the progress dialog stays open for about 1 second after the PowerRename dialog opens?

The progress dialog should show only after a delay of a few seconds.  Perhaps I can wrap this in a better delay of my own on top of that.

@chrdavis
is it expected that the progress dialog stays open for about 1 second after the PowerRename dialog opens?

The progress dialog should show only after a delay of a few seconds.  Perhaps I can wrap this in a better delay of my own on top of that.

I updated SmartRename with a progress dialog that takes into account ~ 3s before being shown.  I'll let that get downloaded and used then port it here.

@chrdavis
what should we do with the current PR?

@chrdavis
what should we do with the current PR?

I ported the changes.  Please review when you get a chance.

@chrdavis
I tested the updated version and it looks like the progress bar is slowing down the file processing.
I used the repository folders so it's easy to replicate.
When renaming individual folders, it take in total 3-4 seconds.
But when renaming the folders together, the progress bar shows up and it takes over 10 seconds.
The overhead introduced by the progress bar keep increasing for larger folders.
I would guess that the problem is caused by updating the progress bar with the filenames, can the progress bar just show the bar and not the filenames?
Also, it takes about 3 seconds for the progress bar to show, what about lowering to 2 seconds or even 1.5 seconds?

Updated based on the feedback.  The updating of the progress dialog is replaced with a static message now so the slowdown should go away.  I also changed the delay from 3s to 1.5s.

@enricogior any reason why this can't be in?

@crutkas
it is still not working for me, after the last change, the progress dialog appears after the PowerRename dialog is shown.

@crutkas
it is still not working for me, after the last change, the progress dialog appears after the PowerRename dialog is shown.

Really?  Can you post a gif?

I just updated the timeout from 1500ms to 2500ms.  Originally it was 3000ms.

@chrdavis
this was before your last commit:

I'll rebuild it and test it again

@chrdavis
same behavior using the latest bits:

Yeah, we are competing on the UI thread.  I'll need to shuffle some things around.  I'll have an update next week.

Updated once again.  Progress UI is now invoked on a background thread.  No longer need the delay timer for the progress dialog.  Please try this out.

@crutkas  Is this tested and good to go for next release?

@enricogior assuming won't happen for 35 due to time. What needs to happen to review here.

@crutkas @chrdavis
I'll review it after 0.35 is released.

@chrdavis
tested, it works as expected, thanks for making it perfectly smooth!


Offline Mode Overhaul

[ ] Read later in offline mode
[x] Offline mode crashing subs when switching
[x] What to do with the bottom bar?
[ ] Audit settings

Same as #788


network::classic features passthrough

As patches were moved to separate crates, it's expected to use them now to import Patch implementations for different networks.
Although, sputnikvm defines a set of compile-time feature flags that are used, for instance, in sputnikvm-ffi for geth. Since now sputnikvm-ffi needs to also import classic network crate, we need to compile the sputnikvm dependency of the network crate with the same features as we do compile main sputnikvm dependency.
So in the end of the day we need to pass the features through the network crate, so we would not end up with code duplication from one dependency being built in different configurations.

@r8d8 default set of features is used if no flags are provided in the Cargo.toml of dependent crate.
This way we mirror the build configuration of SputnikVM itself when no flags are provided to it.
Makes little sense in just out ffi example, but would be useful for 3rd-party users.


[feature request] ready-command

[feature request] ready-command
ready-command:
-   do-this-then-that-later
This would allow to have the command echoed to the prompt but NOT yet executed.

Can you please provide more details about this? I'm not sure I understand what this should do

basically I want to start a session with a command for example:
sudo nmap -sA -sc -flag -flag -flag <IP_ADDRESS>
already typed out but NOT yet executed to still be able to make small change.
Thank you for your for consideration.


Implements mongodb sharding

The following commits implement the changes necessary
for the puppetlabs/mongodb module to allow one to automate
the sharding configuration.

All you remarks have been addressed but this one that I didn't get on params.pp. Could you give me more details ?

If $::mongodb::globals::version is undef then we don't need any of these parameters? This fails for me on missing $config_shard

I think the $config_shard variable disappeared in a rebase, or I was confused about which parameters I was looking at. What I see now is that you've defined parameters like $mongos_service_name and $mongos_config for the case when $::osfamily is 'RedHat' and $::mongodb::globals::manage_package_repo is true, but not for when $::mongodb::globals::manage_package_repo is false or $::osfamily is 'Debian'. This fails for me if I install from epel and I suspect it will fail similarly for Debian:
Error: Parameter path failed on File[undef]: File paths must be fully qualified, not 'undef' at /vagrant/puppet/mongodb/manifests/mongos/config.pp:24
Wrapped exception:
File paths must be fully qualified, not 'undef'

I took the bit about the sharding server (mongos) out of mongodb::server into mongodb::mongos. Does that pattern look better to you ? Doc + spec will come in an ammended commit if we agree on this pattern.

+1

@Spredzy the acceptance tests fail for me when using the default nodeset:
Failures:

  1) mongodb::server class behaves like normal tests default parameters with 10gen => true should work with no errors
     Failure/Error: apply_manifest(pp, :catch_changes  => true)
     Beaker::Host::CommandFailure:
       Host 'centos-65-x64' exited with 2 running:
         env PATH="/usr/bin:/opt/puppet-git-repos/hiera/bin:${PATH}" RUBYLIB="/opt/puppet-git-repos/hiera/lib:/opt/puppet-git-repos/hiera-puppet/lib:${RUBYLIB}" puppet apply --verbose --detailed-exitcodes /tmp/apply_manifest.pp.HKBWpS
       Last 10 lines of output were:
       	Info: Loading facts
       	Info: Loading facts
       	Notice: Compiled catalog for centos-65-x64.delivery.puppetlabs.net in environment production in 1.04 seconds
       	Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want to allow virtual packages, please explicitly set allow_virtual to false.
       	   (at /usr/lib/ruby/site_ruby/1.8/puppet/type/package.rb:430:in `default')
       	Info: Applying configuration version '1420824522'
       	Notice: /Stage[main]/Mongodb::Server::Service/Service[mongodb]/ensure: ensure changed 'stopped' to 'running'
       	Info: /Stage[main]/Mongodb::Server::Service/Service[mongodb]: Unscheduling refresh on Service[mongodb]
       	Notice: Finished catalog run in 0.30 seconds
     Shared Example Group: "normal tests" called from ./spec/acceptance/server_spec.rb:120
     # ./spec/acceptance/server_spec.rb:58:in `block (4 levels) in <top (required)>'

  2) mongodb::server class behaves like normal tests default parameters with 10gen => true Service "mongod" should be running
     Failure/Error: it { should be_running }
       expected Service "mongod" to be running
     Shared Example Group: "normal tests" called from ./spec/acceptance/server_spec.rb:120
     # ./spec/acceptance/server_spec.rb:71:in `block (5 levels) in <top (required)>'

Finished in 18 minutes 57 seconds
38 examples, 2 failures

It seems like something is causing the mongod service to die, maybe a misconfiguration in /etc/mongod.conf ?

@cmurphy fixed.

There's still something wrong with the init scripts. service mongos status on RedHat says "mongos dead but pid file exists" and on Ubuntu says "Could not find /usr/bin/mongos".
We just added support for mongodb on RHEL 7 (it occurs to me now that we didn't document it, will do that in a bit), and I presume this won't work on a systemd environment yet. Could you add a note to the mongos section of the README that mongos isn't supported on RHEL 7 yet?

Hey @cmurphy I couldn't reproduce your issues on my setups, please find below the output
# CentOS 6 | manage_package_repo => false
[root@mongo vagrant]# rpm -qa | grep mongo
mongodb-server-2.4.12-2.el6.x86_64
mongodb-2.4.12-2.el6.x86_64
[root@mongo vagrant]# cat /etc/redhat-release
CentOS release 6.5 (Final)
[root@mongo vagrant]# service mongos status
mongos (pid  5255) is running...
[root@mongo vagrant]#

# CentOS 6 | manage_package_repo => true
[root@mongo vagrant]# rpm -qa | grep mongo
mongodb-org-shell-2.6.6-1.x86_64
mongodb-org-server-2.6.6-1.x86_64
mongodb-org-mongos-2.6.6-1.x86_64
[root@mongo vagrant]# cat /etc/redhat-release
CentOS release 6.5 (Final)
[root@mongo vagrant]# service mongos status
mongos (pid  5423) is running...
[root@mongo vagrant]#

# Ubuntu 12.04 | manage_package_repo => false
root@mongo:/home/vagrant# lsb_release  -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 12.04.2 LTS
Release:        12.04
Codename:       precise
root@mongo:/home/vagrant# dpkg -l | grep mongo
ii  mongodb-clients                   1:2.0.4-1ubuntu2.1           object/document-oriented database (client apps)
ii  mongodb-server                    1:2.0.4-1ubuntu2.1           object/document-oriented database (server package)
root@mongo:/home/vagrant# service mongos status
 * Checking status of database mongos
   ...done.
root@mongo:/home/vagrant# service mongos restart
 * Restarting database mongos
   ...done.
root@mongo:/home/vagrant#

# Ubuntu 12.04 | manage_package_repo => true
root@mongo:/home/vagrant# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 12.04.2 LTS
Release:        12.04
Codename:       precise
root@mongo:/home/vagrant# dpkg -l | grep mongo
ii  mongodb-org-mongos                       2.6.6                        MongoDB sharded cluster query router
ii  mongodb-org-server                       2.6.6                        MongoDB database server
ii  mongodb-org-shell                        2.6.6                        MongoDB shell client
root@mongo:/home/vagrant# service mongos status
 * Checking status of database mongos
   ...done.
root@mongo:/home/vagrant# service mongos restart
 * Restarting database mongos
   ...done.
root@mongo:/home/vagrant#

For RHEL7 it will work with the use of systemd-sysv package, as it will understand the /etc/init.d/mongos init script. But the fact to specify the mongos init script is temporary, the issues is packaging related and an issue has been raised in MongoDB tracking system https://jira.mongodb.org/browse/SERVER-3748.

Okay, it seems to be functional in any case so if someone else runs into my issue we can do a bugfix.
One more tiny note, then I think we're good.


AppCenter not showing iOS devices

HockeyApp shows the devices by extracting the provisioning profile from package uploaded.
Unfortunately, in AppCenter, no devices are seen.

I wonder if this is due to the Profile?
On our end, the "Install Profile" flow through AppCenter doesn't work as it just keeps kicking back to AppCenter; however, through HockeyApp (https://rink.hockeyapp.net/configuration) it does work.... which would be a Bug.

@xhashimks App Center releases page doesn't have any information on which devices are in the profile.
You can see the devices linked to an app, by enabling auto-provisioning for a distribution group - https://docs.microsoft.com/en-us/appcenter/distribution/auto-provisioning

Hi, you are able to see some device information related to provisioning in distribution->groups->devices

@botatoes I am not able to see. I have raised this as a concern and the AppCenter support team asked me to raise a feature request. In HockeApp, i used to see the provisioned devices (UDID and name) for which the iOS build is taken.

This is still missing.  To see the provisioned devices now with App Center, I have to download the IPA, extract the "embedded.mobileprovision" file, and view it in a text editor.  This issue is compounded with the fact that the list of users' devices for a build lies about which devices are provisioned.
I am troubleshooting the reason one of my colleagues can't see our latest iOS build in their App Center dashboard.  I just checked the list of devices in the App Center GUI and their device says "PROVISIONED" in the list.  Then I downloaded the IPA myself, extracted the "embedded.mobileprovision", and searched for their device's UDID, and it's not in there.  App Center doesn't seem to accurately show which devices are provisioned for the latest build, and I can't see the list without extracting it manually, unlike with HockeyApp where I could click a link to see the list right away.

This issue is still relevant.  We are still awaiting a simple link to a correct list of devices per build like HockeyApp had.  Downloading the IPA and opening the .mobileprovision file in a text editor with a spreadsheet I manually maintain to cross-reference UDIDs is an awfully annoying manual process that wasn't necessary in HockeyApp.  Please reinstate the list of devices.

This issue is still exactly as relevant as it was the last time I commented on June 29th.

(bump)

This issue is still exactly as relevant as it was the last time I commented on 2021-06-29.


Expose RestResources types for Typescript

Overview/summary
Currently you can not easily get the RestResource types for the specified API version.
Importing import type { RestResources } from '@shopify/shopify-api/rest/admin/2024-07'; gives you access to RestResource[''] but as these are typeof <Resource> values you only get access to the class static information.
Using the official types would be super handy when dealing with code that is reacting to events from webhooks as we want to be sure we're using what is specified by the set API version rather than relying on writing our own types and having to manually upgrade our types when we upgrade the version.

Thanks for flaging this!
I am going to move this to our teams backlog, to look into in the near future.


[Youtube] Ratebypass no longer works

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2018.01.14. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2018.01.14

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the -v flag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['_QdPW8JrYzQ', '-f', '251', '-v']
[debug] Encodings: locale cp936, fs mbcs, out cp936, pref cp936
[debug] youtube-dl version 2018.01.14
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.16299
[debug] exe versions: none
[debug] Proxy map: {}
[youtube] _QdPW8JrYzQ: Downloading webpage
[youtube] _QdPW8JrYzQ: Downloading video info webpage
[youtube] _QdPW8JrYzQ: Extracting video information
[debug] Invoking downloader on 'https://r13---sn-3c27sn7k.googlevideo.com/videoplayback?keepalive=yes&nh=IgpwcjAyLmticDAzKgkxMjcuMC4wLjE&pl=18&initcwndbps=1393750&sparams=clen%2Cdur%2Cei%2Cgir%2Cid%2Cinitcwndbps%2Cip%2Cipbits%2Citag%2Ckeepalive%2Clmt%2Cmime%2Cmm%2Cmn%2Cms%2Cmv%2Cnh%2Cpl%2Crequiressl%2Csource%2Cexpire&source=youtube&mt=1516289287&key=yt6&mime=audio%2Fwebm&clen=7554639&ipbits=0&itag=251&mn=sn-3c27sn7k&mm=31&signature=46139BF232DAF5CF4F6A41703F029BD78E20947A.4C3CADAF3E826381536E301B6764BC585681C323&gir=yes&dur=588.321&ms=au&mv=m&requiressl=yes&lmt=1497754431135135&ip=xxx.xxx.xxx.xxx&ei=W71gWtm_FYGA0wXt_b2ADw&expire=1516310971&id=o-AL9JmhKfh44w3MjmGvlb-zHtJxFQQE3QQMOXW724LeqE&ratebypass=yes'
[download] Destination: This is what happens when you reply to spam email _ James Veitch-_QdPW8JrYzQ.webm
[download] 100% of 7.20MiB in 02:16
...
<end of log>

Description of your issue, suggested solution and other information
ratebypass no longer has any effect, which results in extremely slow download speed. Observed in #15302, #15271, https://github.com/Tyrrrz/YoutubeExplode/issues/85. Only affects adaptive streams, muxed streams still work, which makes me think the issue is that ratebypass is not listed in sparams, while forcefully adding it breaks the signature.

Why was this issue closed? Has a solution been implemented?


postActivity responses to an Invoke return the string 'retry'

If you send an InvokeActivity to postActivity via dljs, a success will return an id with the activity ID. However, an Invoke can return other status codes for error/failure cases. When this happens, postActivity still calls the "success" trigger but with an id of 'retry'.
Repro code:
directLine.postActivity({
type: 'invoke',
name: 'good'
}).subscribe(
id => {
console.log("Posted activity, assigned ID ", id);    // this is called with a real id
},
error => {
console.log("Error posting activity", error);
}
);
directLine.postActivity({
type: 'invoke',
name: 'bad'
}).subscribe(
id => {
console.log("Posted activity, assigned ID ", id);    // this is called with an id of 'retry'
},
error => {
console.log("Error posting activity", error);
}
);
For the boy, just handle invokes and return an InvokeResponse of 409 or whatnot in that bad case, and an InvokeResponse of 200 in the good case:
Here is some C# code to do this:
protected override async Task OnInvokeActivityAsync(ITurnContext turnContext, CancellationToken cancellationToken)
{
await turnContext.SendActivityAsync("Got an invoke: " + turnContext.Activity.Name);
if (turnContext.Activity.Name == "good")
{
await turnContext.SendActivityAsync(
new Activity
{
Type = ActivityTypesEx.InvokeResponse,
Value = new InvokeResponse
{
Status = 200
},
}, cancellationToken).ConfigureAwait(false);
}
else if (turnContext.Activity.Name == "bad")
{
await turnContext.SendActivityAsync(
new Activity
{
Type = ActivityTypesEx.InvokeResponse,
Value = new InvokeResponse
{
Status = 409
},
}, cancellationToken).ConfigureAwait(false);
}
else
{
await base.OnInvokeActivityAsync(turnContext, cancellationToken);
}
}
Expected behavior:
(1) At least the error case should be called.
(2) It'd be nice to get the actual result code, or the 502 saying message wasn't processed properly by the bot if that's all DirectLine returns

Any update on this? The issue is open since January, no proper debugging is possible if the error is swallowed. Also because of how this lib is build its impossible to set a breakpoint in code because it is dynamically compiled during runtime....

Any news? Two years later and still have this error.
Deployed the bot with latest BotFrameworkComposer and updated this package.
By the way, when using the emulator the bot responds correctly


chore(test/linarith): remove stray variables from guard_msgs

Some of the #guard_msgs testing for errors in this file capture a pile of random unrelated variables. This scopes these variables to sections to avoid this behavior.
I also uncomment a test that doesn't seem to be problematic any more, and remove pp.mvars which wasn't actually having any useful effect.

Actually: I just pushed a commit removing the added autoImplicit true; reordering variables since I saw no point in the old order.

bors merge


Remove required variable - not used

https://github.com/JDACS4C-IMPROVE/IMPROVE/blob/7bdc917e9b7c68e06ec4458e834c06a06b60b326/improvelib/initializer/config.py#L637
We are using argparse syntax to define an option as required - is there a need to check later?

I think this propagated from candle. Unless somebody knows whether we need or don't need this, I suggest keeping this issue and decide regarding required before the release.


GPS fix, but getting wrong grid square.

Tried on laptop, tried on battery (power bank), and during two hours, not a single correct gridsquare (JN95):

Meanwhile, during this period assembled ICT tracker:

RPi Pico tracker should be easy and fast to set, but it is not so easy.
73, Milan, 9A4GE.
P.S. It has GPS fix, but it shows it on Antartic.:

this may have been fixed by the change I just pushed for Whallmann. if the current version still doesnt work please turn verbosity to 5 and try to capture some of the debug messages.

Now seems that it working just fine: JN95JG. Will test in next few hours.
73, Milan, 9A4GE


basic python 3 support

we are using the future package to get proper Queue support for both python 2.7 and > 3.0.
Thanks @Rosuav for the patch on #604

It looks sane, but how is it tested?

@hamishwillee I'm tweaking our CI configs so they run it on both Python versions, no need for more tests, the idea is that we should be able to run the same code on both versions until we drop one of them (hopefully 2.7 in the future)

OK. YOu'll have to re-merge. Perhaps @peterbarker should look at this too, but I'd be happy for you to self-merge :-)

going ahead and merging, travis fails on a pymavlink python3 known problem, this has been raised on https://github.com/ArduPilot/pymavlink/issues/4 and will soon be fixed, until then we can't really claim full python 3 support on dronekit


Fix Java clients generation

artman_.yaml config values meaning changes:

GAPIC_ONLY artman artifact type now means gapic-only (proto and grpc layers are not generated).
GRPC artman artifact type now means grpc + proto layers (makes it consistent with other languages, follows convention, when each higher-level layer implies generation of all lower-level layers).
GAPIC artman artifact type now means gapic+grpc+proto, as standalone packages, fat jar functionality is removed (was already in unmainteined state).
GRPC_COMMON artifact type is prepared to be removed (is equal to GRPC).

These changes also result into:

GAPIC_ONLY is prepared to be used for longrunning client generation.

Note, for golden tests to pass, https://github.com/googleapis/toolkit/pull/1867 should be pushed and integrated with artman docker image first.

@garrettjonesgoogle, @lukesneeringer PTAL

This looks fine to me.
The smoke test failure is probably something unrelated (@jbolinger removed Ruby from api-client-staging), and I am addressing it in #401.

@vam-google I will take the baton on this from here. Should be merged today (tomorrow at the latest) once I unblock the CI issue.

@lukesneeringer sounds good to me. This PR is closely connected to the toolkit change googleapis/toolkit#1867 and a pening updates in googleapis (please check the CL). When we merge, ideally we should merge all 3 together.

Okay; it is approved, so you can merge it when you see fit.


test(runtime-core): render element

Thanks for the PR - but these tests should be narrower in scope and not involve reactive, blocks or patchFlags (blocks and patchFlags should be tested in rendererOptimizedMode instead, feel free to work on that one instead)
Also see #699


Updated three diagrams

From flowchart to sequence diagram
I have not updated all the diagrams yet, if you think this is the way to go I can update the rest here.

Excellent work thank you!


Shader error on Mac OS

Hi,
This looks like a really cool and useful project!  I'm trying to evaluate whether it could be adopted for swarm robotics research.  However, I'm on a Mac and got the following error when trying to execute bots2dtest:
4.1 ATI-4.8.15
Failed to compile vertex
ERROR: 0:11: ';' : syntax error: syntax error

Failed to compile fragment
ERROR: 0:11: ';' : syntax error: syntax error

/Users/av/Downloads/bots2d/src/renderer/Shader.cpp 171 glAttachShader(program, vs) [OpenGL errer]: 1281
Assertion failed: (false), function GLLogCall, file /Users/av/Downloads/bots2d/src/renderer/GLError.cpp, line 15.
Abort trap: 6

I understand that this may be an OS-specific issue.  But maybe someone has some advice?

Sorry for late reply, haven't looked at this repo in a while. I have not tried to build this on MacOS. Might be possible to get it working, but OpenGL is deprecated on MacOS.


WinAppSDK upgrade time! (after .84 is verified stable)

Summary of the Pull Request
This upgrades to WinAppSDK 1.6, updates WebView2 and CsWinRT
Learnings from: https://github.com/microsoft/PowerToys/pull/34437
We will also need Community Toolkit upgraded as well via https://github.com/microsoft/PowerToys/pull/34419

PR Checklist

[ ] Closes: #xxx
[ ] Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
[ ] Tests: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Dev docs: Added/updated
[ ] New binaries: Added on the required places

[ ] JSON for signing for new binaries
[ ] WXS for installer for new binaries and localization folder
[ ] YML for CI pipeline for new test projects
[ ] YML for signed pipeline

[ ] Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

Validation Steps Performed

/azp run

arm64 passed, x64 errored for some reason

I've fixed MeasureToolUI to remove the title bar and borders that WASDK 1.6 seems to have added:
https://github.com/microsoft/PowerToys/pull/34622/commits/90f9e4f4a3f64c0874fe4e94919a0f1a0e3a3ecf

@davidegiacometti please submit fix!

alternative, could this be "good enough" and get it in and do a PR to fix this


Warning: Encountered two children with the same key when enabled alongside Vercel Analytics

I just installed this package in my project, however, if Vercel Analytics is also installed I get the following browser console warning:
Warning: Encountered two children with the same key, ``. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version.

If I add a key to <GoogleAnalytics /> the warning goes away. Not sure if it was something you needed to be aware of.
import { GoogleAnalytics, event } from 'nextjs-google-analytics';
import { Analytics } from '@vercel/analytics/react';

function MyApp({ Component, pageProps }: AppProps) {
    return (
        <>
             <GoogleAnalytics
                trackPageViews={{ ignoreHashChange: true }}
               key={0}
             />
             <Component {...pageProps} key={router.asPath} />
             <Analytics />
    );
}

Hello @jinsley8 !
I was not aware of this, thanks for bringing it up.
Do you think adding a note on the README.md would be useful?

I haven't checked yet if it works properly on a production site but the warning goes away.
I don't see any reason why it wouldn't work so updating the README would be fine.

I encountered a similar problem where GA worked fine in local development, but when pushed to production on Vercel, no data was ever sent to Google Analytics.
I removed the @vercel/analytics dependency, which solved my problem. This works for me as a temporary solution, but ideally I would like to use both analytics tools.

I encountered a similar problem where GA worked fine in local development, but when pushed to production on Vercel, no data was ever sent to Google Analytics.
I removed the @vercel/analytics dependency, which solved my problem. This works for me as a temporary solution, but ideally I would like to use both analytics tools.

I don't see any reason for google analytics to fail while vercel analytics is also active, but will do some research to see if I can find something, thanks for bringing this up @wiah .
Just in case: "I encountered a similar problem where GA worked fine in local development", is the env variable properly set in production? What's your setup?


site connection-mode uses --set param and does not have subcommand to list

Unlike other inconsistent commands, site connection-mode's default - to display the current mode - does not appear in site info's info. To standardize, we would change the set command to site set-connection-mode and the --set param would be --mode, but where would the user get the current connection mode if we did this?
One way to do it would be to retrieve the attributes of each environment when requested, but what would the command be? site environments info? If so, wouldn't many environment-acting site subcommands also belong to this subcommand?

Related to #524

I would really love your thoughts on this, @ronan & @joshkoenig.

Good catch! Let's fix this before 1.0.
It is possible that we may want a terminus site environment-info or environments-info command much like site-info but specifically provides information about the environment.
However, I think we'd need more of a use-case than just getting the connection mode. I'm tempted to say we can go 1.0 without a way of "fetching" the current state of the connection mode. If you're going to change it, it's an atomic operation. Changing it to the value it's already at is a no-op.
Let's move forward with set-connection-mode, and see if there's other specific environment-info that would be of use for such a command.

Actually, if we look at the results from the API for an environment now:
https://dashboard.pantheon.io/api/sites//environments/dev
The on_server_development value tells us if it's in SFTP mode. I think this is useful info. It helpfully includes the target ref/tag for test and live as well:
https://dashboard.pantheon.io/api/sites//environments/test
https://dashboard.pantheon.io/api/sites//environments/live
This would make sense to expose as a site environment-info command, which would naturally take a --env flag.
The status of the environment HTTP-AUTH lock, the target ref, and whether SFTP mode is on or off are a worthwhile set of data to expose.

It would be pretty quick to add the connection mode to the output of site environments which would be probably good enough for people but less so for scripts.

Oops, cross-post. I guess I didn't realize that 'OnServer Dev?' is in fact the connection mode. Should that be changed to be consistent with the language in the dashboard (Connection Mode: SFTP/Git)?