[To rel/0.11] Overlapped data should be consumed first

I used sequence/root.group1/0/xxx-340.tsfile, xxx-344.tsfile and unsequence/root.group1/0/xxx-360.tsfile, xxx-362.tsfile, xxx-364.tsfile, xxx-366.tsfile, xxx-367.tsfile, xxx-368.tsfile, xxx-370.tsfile, xxx-371.tsfile to reproduce this overlap bug. Here is the reproduce process and result:
reproduce process

IoTDB v0.11.3

used sequence data:  sequence/root.group1/0/xxx-340.tsfile, xxx-344.tsfile

used unsequence data: unsequence/root.group1/0/xxx-360.tsfile, xxx-362.tsfile, xxx-364.tsfile, xxx-366.tsfile, xxx-367.tsfile, xxx-368.tsfile, xxx-370.tsfile, xxx-371.tsfile.

timestamp_precision set to us (because the system/schema/system.properties says so)

client query: select count(Channel101) from root.group1.J053102.T001.V1

reproduce result

IDEA

It shows that mergeReader.currentTimeValuePair().getTimestamp()=firstPageReader.getStatistics().getStartTime()=1621993751955000 us = 2021-05-26 09:49:11.955
used data visualization

The vertical line in this figure is the reported bug time<PHONE_NUMBER>955000 us = 2021-05-26 09:49:11.955
Zoom in and find that the vertical line is at the same time as the second series chunk in unseq-371.tsfile, and the first chunk in seq-344.tsfile

See the device data that root.group1.J053102.T001.V1 belongs to:

y-axis ordered by fileName:

or 2) y-axis ordered by timeseriesName (same as 1), with only y-axis order difference):

By the way, my last comment is not saying that this pr has bug. I was reproducing the bug reported before.

Thank you for your careful reproducing! :D


Release new version?

@ksnyde may you please release a new version. PR #1 was merged, but problem is not fixed on new install ;) Thanks

I did a new npm build 0.2.1, hopefully this addresses this for you.


Capacitor 6 support

Add support for capacitor 6

In the coming days I will.
I'll also address each issue that was opened

In the coming days I will. I'll also address each issue that was opened

FYI: I already tried using the v5 version of this plugin together with Capacitor v6 and things seem to still work.
Wanted to let you know as I think that's a good sign and might help reassure some people that this might come soon.
As I already upgraded to capacitor v6 and I had to add --force in all of my workflows feels very hacky. 😅
So, I am thankful that you are doing this soon, so I can remove the workaround. 🙏

@tchvu3 Any update?

oming days I will.
I'll also address each issue that was opened

Bump? :D

@tchvu3 I'm getting a bit worried. Are you ok? 🥺

@tchvu3 I created this PR that adds support for Capacitor 6. @Eraldo can you test it?

@tchvu3 I created this PR that adds support for Capacitor 6. @Eraldo can you test it?
Do you by any chance know how I can install from a PR via poetry? I didn't manage to get it to work.
That being said it looks good to me. :)

@tchvu3 I created this PR that adds support for Capacitor 6. @Eraldo can you test it?

"capacitor-voice-recorder": "github:tchvu3/capacitor-voice-recorder#pull/47/head",

=> Works nicely for me. :)
(Did some manual frontend record testing as well.) 👍

"capacitor-voice-recorder": "github:tchvu3/capacitor-voice-recorder#pull/47/head",

How can I test it (Install this PR) ?

@tchvu3 how is it going?

Hi, any suggested alternative package for V6 ?

For now I just use npm i --force, no bugs found (tested on iOS devices). Just waiting this issue to be resolved to remove --force from ci/cd pipelines.

@tchvu3 any updates on this?
As @Eraldo anticipated, updating to Capacitor 6 is mandatory for projects in order to support API 34 with Android 14, with the deadline on August 31st.
I hope you can review the @niconaso PR to release a Capacitor 6 compatible version soon.
Thanks in advance!

@tchvu3 any updates on this? 😇

Hi, any suggested alternative package for V6 ?

cc @midomario
I finally have used the approach commented by @Eraldo , installing the version from the PR of @niconaso
It works fine with Capacitor 6, although it's not a good thing to use the package from a PR...
If you are looking for some plugin alternatives, this one (seems to be maintained) could be fit your needs: https://github.com/mozartec/capacitor-microphone
Anyway, it would be nice that @tchvu3 review the PR and update the plugin with it.
On the other hand, I aim to all of you who wants an update to make some donations to him to support his work here: https://buymeacoffee.com/tchvu3
Hope it helps!

Thanks everyone for their interest in the plugin,
and thanks to @qmarcos for the nice gesture, its not taken for granted.
The plugin is not dead, and i will updated it in the following days, i was just very busy in my personal life.

Hi @tchvu3, great to hear that the plugin is not dead :)
Do you think adding CI/CD pipeline would help you and make maintenance a bit easier in the future?
I am thinking of something similar to what is used by the ionic team on the official plugins:

Verification
Deployment

If something like that is needed, please let me know and I would be happy to contribute.

Finished updating to v6.
@kstruempf thats awesome, I hope it will be useful to you and your company.
I will anyway continue to maintain the plugin as needed


Error while installing in Docker dev environment

I tried to install tiktoken in Docker dev environment with Python 3.9 using the default approach: pip install tiktoken
But I got an error: Could not build wheels for tiktoken, which is required to install pyproject.toml-based projects
Here is the stack trace:
root ➜ /com.docker.devenvironments.code (master ✗) $ pip install tiktoken
Collecting tiktoken
  Using cached tiktoken-0.3.0.tar.gz (24 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Collecting blobfile>=2
  Using cached blobfile-2.0.1-py3-none-any.whl (73 kB)
Collecting requests>=2.26.0
  Using cached requests-2.28.2-py3-none-any.whl (62 kB)
Collecting regex>=2022.1.18
  Using cached regex-2022.10.31-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (769 kB)
Requirement already satisfied: lxml~=4.9 in /usr/local/lib/python3.9/dist-packages (from blobfile>=2->tiktoken) (4.9.2)
Requirement already satisfied: urllib3<3,>=1.25.3 in /usr/local/lib/python3.9/dist-packages (from blobfile>=2->tiktoken) (1.26.13)
Requirement already satisfied: filelock~=3.0 in /usr/local/lib/python3.9/dist-packages (from blobfile>=2->tiktoken) (3.8.2)
Collecting pycryptodomex~=3.8
  Using cached pycryptodomex-3.17-cp35-abi3-manylinux2014_aarch64.whl (2.1 MB)
Requirement already satisfied: charset-normalizer<4,>=2 in /usr/local/lib/python3.9/dist-packages (from requests>=2.26.0->tiktoken) (2.1.1)
Requirement already satisfied: idna<4,>=2.5 in /usr/local/lib/python3.9/dist-packages (from requests>=2.26.0->tiktoken) (2.10)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.9/dist-packages (from requests>=2.26.0->tiktoken) (2022.9.24)
Building wheels for collected packages: tiktoken
  Building wheel for tiktoken (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for tiktoken (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [37 lines of output]
      running bdist_wheel
      running build
      running build_py
      creating build
      creating build/lib.linux-aarch64-cpython-39
      creating build/lib.linux-aarch64-cpython-39/tiktoken
      copying tiktoken/registry.py -> build/lib.linux-aarch64-cpython-39/tiktoken
      copying tiktoken/__init__.py -> build/lib.linux-aarch64-cpython-39/tiktoken
      copying tiktoken/model.py -> build/lib.linux-aarch64-cpython-39/tiktoken
      copying tiktoken/core.py -> build/lib.linux-aarch64-cpython-39/tiktoken
      copying tiktoken/load.py -> build/lib.linux-aarch64-cpython-39/tiktoken
      creating build/lib.linux-aarch64-cpython-39/tiktoken_ext
      copying tiktoken_ext/openai_public.py -> build/lib.linux-aarch64-cpython-39/tiktoken_ext
      running egg_info
      writing tiktoken.egg-info/PKG-INFO
      writing dependency_links to tiktoken.egg-info/dependency_links.txt
      writing requirements to tiktoken.egg-info/requires.txt
      writing top-level names to tiktoken.egg-info/top_level.txt
      reading manifest file 'tiktoken.egg-info/SOURCES.txt'
      reading manifest template 'MANIFEST.in'
      warning: no files found matching 'Makefile'
      adding license file 'LICENSE'
      writing manifest file 'tiktoken.egg-info/SOURCES.txt'
      copying tiktoken/py.typed -> build/lib.linux-aarch64-cpython-39/tiktoken
      running build_ext
      running build_rust
      error: can't find Rust compiler

      If you are using an outdated pip version, it is possible a prebuilt wheel is available for this package but pip is not able to install from it. Installing from the wheel would avoid the need for a Rust compiler.

      To update pip, run:

          pip install --upgrade pip

      and then retry package installation.

      If you did intend to build this package from source, try installing a Rust compiler from your system package manager and ensure it is on the PATH during installation. Alternatively, rustup (available at https://rustup.rs) is the recommended way to download and update the Rust compiler toolchain.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for tiktoken
Failed to build tiktoken
ERROR: Could not build wheels for tiktoken, which is required to install pyproject.toml-based projects

Thanks, duplicate of https://github.com/openai/tiktoken/issues/52

@hauntsaninja you referenced my issue (duplicate of #52) but 52 it's this issue

Oops, duplicate of https://github.com/openai/tiktoken/issues/23


docs.trybadger.com

Set a proper subdomain for the Gitbook docs at https://flipside-crypto.gitbook.io/badger/integration-tutorials

Up and running!


ARROW-8036: [C++] Avoid gtest 1.10 deprecation warnings

Looks like there's a problem with the gtest 1.10 conda-forge package on Windows (as usual?).
https://ci.appveyor.com/project/pitrou/arrow/builds/31348643

Issue reported upstream: https://github.com/conda-forge/gtest-feedstock/issues/43

+1, will merge if green

AppVeyor: https://ci.appveyor.com/project/pitrou/arrow/builds/31426111

@pitrou is there a reference about the API change that made this work (TYPED_TEST_CASE -> TYPED_TEST_SUITE)?

There's https://github.com/google/googletest/releases/tag/release-1.10.0

Aha well there we go, thanks =)


Some method of indicating that each result can be expanded

Either add "Click any record to expand" to the right of the results counter at the top of the results table
OR else add ' v ' (the upside-down ^ that is used next to About) to the right side of each row, to indicate it can be expanded.

Let's just go with the 'v' symbol to the right (where the icon column now is). That should indicate expansion to users. Delete the "Click any record to expand" text


[Bug]: Install fails on a fresh Ubuntu 20.04.4 server

Is there an existing issue for this?

[X] I have searched the existing issues

Example public repository
coolify
Description
Running:
wget -q https://get.coollabs.io/coolify/install.sh \
-O install.sh; sudo bash ./install.sh

i get:
no such file or directory
Steps To Reproduce
deploy a fresh Ubuntu 20.04.4 server with firewall disabled and try to install coolify as in the documentation by running
wget -q https://get.coollabs.io/coolify/install.sh -O install.sh; sudo bash ./install.sh
Version
latest

deployed debian 11, same error occurs :(

is there anything that i am missing?

any help on this!

I tried both operating systems, and both worked well. Can you please paste the full log here? And also paste the debug logs by executing the same script with the -d flag.
wget -q https://get.coollabs.io/coolify/install.sh -O install.sh; sudo bash ./install.sh -d

this is what i get

no firewall is enabled, wget is working

total mystery :). deployed a fresh new ubuntu vm and it worked

After https there is a ; not a :.


The GetCountriesByContinentAsync(string continent) not working

That's because the corresponding API endpoint was removed.
The workaround is to get all countries first and apply a filter on the "Region" field using Linq.
var allCountries = await RESTCountriesAPI.GetAllCountriesAsync();
var europeCountries = countries.Where(c => c.Region.Equals("Europe")).OrderBy(c => c.Name).ToList(); ;


input-group-addon height on Safari

I have this issue with Safari http://imgur.com/lassFla in Chrome looks fine http://imgur.com/6oQBRsZ this is my markup:

      <input type="text" class="form-control ">
      Search

What i'm doing wrong?

Yes the docs http://twbs.github.io/bootstrap/components/#input-groups exhibit this problem.  Open in safari 5.1.7 on windows 8.1.  The middle user name and ad-on are correct but the large (upper) and small (lower) are the incorrect size.  My site uses the sm and it looks really bad, IE, chrome, and firefox seems fine.

Note that Safari on Windows is not supported by Bootstrap http://getbootstrap.com/getting-started/#support ... and Apple discontinued its development a few years ago as well.

I'm having the same problem on Safari Version 5.1.10 (6534.59.10) on OS X Snow Leopard. The docs example is affected by this problem when input-group-sm and input-group-lg are used.

I have the same issue using Bootstrap 3.3.2 on Safari 5.1.10 (6534.59.10) on OS X Snow Leopard. You can see it even from your docs examples:
http://getbootstrap.com/components/#input-groups-sizing


Causes problems with server mods

Apotheosis will cause problems with the instructions of the following two mods
https://www.curseforge.com/minecraft/mc-mods/htm
https://www.curseforge.com/minecraft/mc-mods/ledger

Are you sure this is a problem with Apotheosis? I'm not sure why it would be changing text from commands and such

I'm pretty sure, as you can see, I don't have any other mods installed
latest.log


Permutation argument in expression framework

This PR implements the permutation argument in the expression framework. This results in

some tweaks to the expression framework to support the necessary constants and functions
some changes to the verifier to use this expression version.

Note that this is not used by the prover, nor is it included in the total linearization. This is due to some quirks:

computing as the prover, we will detect the target domain size as > 8n, due to an off-by-one error
integrating this into the linearization will force the prover to use it in order to make it available to the verifier, because of how the verifier index is computed
otherwise exposing it in the linearization will change how the pickles circuit is computed, making this an incompatible change.

This change would make it trivial to add an evaluation for the final permutation coefficients column. Again, this is not done here because it would break compatibility.

@mrmr1993 Still relevant? (seems so.) Should be rebased towards master?


NamesController LocationsController CRUDify

Name and Location Controllers CRUDified
Non-CRUD actions namespaced and CRUDified

Locations
Countries, Descriptions, Help, Maps, Merges, Observations, ReverseNameOrder, Versions

Descriptions
Defaults, Merges, Moves, Versions

Names
Classification, Descriptions, EolData, Lifeforms, Maps, Synonyms, Trackers, Versions

Classification
Inherit, Propagate, Refresh
Descriptions
Defaults, Merges, Moves, Permissions, Publish, ReviewStatus, Versions
EolData
ExpandedReview, Preview
Lifeforms
Propagate
Synonyms
Approve, Deprecate
Trackers
Approve

Coverage: 92.142% (-0.6%) from 92.713% when pulling 230f7b4210b64701a55331c05da12a6af7386e0c on nimmo-CRUD-names-locations-descriptions into 02a4938ddc99213b2a038820b6ae007a97b58971 on master.

Yahoo! This PR is green. I'll be looking where coverage went down, to write some new tests. Also, working on some codeclimate stuff.
Meanwhile, please do test drive if you are so inclined.

A couple notes:

Yes, this is a massive PR. After working for months on a previous attempt at NamesController, I realized it's not worth it to break it up. If i try to do Names but not Locations, the exceptions I have to write for descriptions are confusing and kind of absurd, since they're more complex and they're temporary (until a Locations PR).
This uses concerns. I considered alternatives and I prefer concerns because they're core Rails, so they get autoloaded from the controllers directory with Zeitwerk, and they're a well-documented way for controllers to share functionality.
If we move to Trailblazer or another framework, the question of sharing logic via concerns will become obsolete.

New test coverage for description merges, moves, permission adjustments, publishing drafts, reverse location name.
Note: This PR now proposes removing controllers for LocationDescription permissions and drafts. They may be useful for NameDescriptions, but this level of control does not seem likely to be useful for Location descriptions.
@JoeCohen Do you think we need these?

Ready to rumble!

Formatting issue when I got to http://localhost:3000/names/402/versions?q=1oAhh&version=2.

Formatting issue fixed, plus ABC suggestions in versions_helper.rb

Thank you @mo-nathan for clicking around.
I hope it's clear that i'm not expecting code review here!
I'm asking for everyone to spend 5 minutes clicking around Names and Locations on this branch, to be sure everything is as expected. Very little code has changed, and all tests are passing, so anything that isn't right is likely to be in the front end, as in previous CRUD PRs.

Clicking around:  In the GlossaryTerm index, thumbnails are too small, but that's not new in this PR.

On show NameDescription page, the Destroy link/button should be next to Edit.

PS: I wouldn't mind if the Other Available Locations column went away.
It's approximately useless because it includes almost every defined Location.
And because it's not paged, it's awfully slow. (And if it were paged, it would be even hard to use.)
locations/merges/new lists every location,

@JoeCohen Thank you for that detailed walk-through.
I fixed the Edit | Destroy layout, and also improved the irregular "colored_notes_box" panels to use bootstrap default classes. I removed the "even/odd" arg that isn't used in the layout anymore, in any case, and renamed the method "notes_panel", because it is only used for description notes.
Re: Merges
I agree, the Other Locations column is next to useless. It takes 10 days to load all the locations — and this list is not exactly useful when it does arrive, by covered wagon.
However, I notice now that the action is available by other tab links, and it seems the "Locations::MergesController#new" action is the real problem here.
I think it should not be returning all locations as a fallback — this renders the page unresponsive. If the location doesn't match any existing location string, I think the form should offer simply an autocomplete box.
I'd also like to move the string matcher functions to a series of Location model scopes, since they are db queries.
What do you think?

I've got a new possible solution for the location merges page. #1302


Rekishi

Rekishi created by<EMAIL_ADDRESS>on 2018-12-12 17:42:11

<EMAIL_ADDRESS>replied, Still working on that sign in Ngardmau:Â  "Kedeb el Rekishi er a Omelai el Chidudes er a Rak er a 1938, e a Nanyo Aruminium Kogyo Kaisha el kombalii er a Siabal a milechelii a omelai el chidudes er a beluu er a Ngaremlengui."
Anyone know what "rekishi" is?Â  Rekisi (ã‚Œãã—) in Japanese means "history", so maybe "kedeb el rekishi" means "a short time".

<EMAIL_ADDRESS>replied, Jim, that's what it is as far as I know. Palauans pronounce it "reksi."
"Short history on bauxite mining. In the year 1938, Nanyo Aruminium Kogyo
Kaisha, a Japanese company, started bauxite mining in the state of
Ngeremlengui."

<EMAIL_ADDRESS>replied, Aleks, did you mark this complete?  When you mark one complete, please add a comment first explaining why you are completing it.  Did you add the word to the dictionary or what?  Thanks.

<EMAIL_ADDRESS>replied, ok.we already have this words as a REKSI. it would be useful to add REKISI as its var.

<EMAIL_ADDRESS>replied, Thanks Aleks.  If you add REKISI, please comment here that you have done
so, and close this issue.  Thanks!

<EMAIL_ADDRESS>replied, done


Remove duplicate WorkspaceEdit from LSP

WorkspaceEdit structure for LSP was duplicated twice, causing Godot 4 to break at compilation in #50378 . This PR fixes it by removing the duplicate and merging its function in to prevent API breakage.

Thanks!


[Feature] The site is not responsive as per the screen size :https://devlake.apache.org/

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Use case
No response
Description
[Feature] The site is not responsive as per the screen size :https://devlake.apache.org/
https://user-images.githubusercontent.com/67385503/206720420-491182dd-6a6a-4ae4-9815-c9f22e910918.mp4
Related issues
No response
Are you willing to submit a PR?

[x] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Thanks for the report, looking forward to your PR. 😊

I would like to add more this issue is present in more pages. DORA and Engineering Overview page has the same issue. Need to work on Header and Footer height and weight!

@miraz-mondal I just checked, and it is displayed properly on iPhone XR and other screens. I'll close the ticket for now.


error [Sonatype] [MISSING_PROFILE] Profile winitzki is not found. Check your sonatypeProfileName setting in build.sbt  - (Sonatype.scala:425)

Describe the bug
Cannot do sonatype commands due to "profile not found"
How to reproduce the issue
I am not able to publish my open-source project - https://github.com/Chymyst/curryhoward to Sonatype (but this worked around 3 years ago). I am publishing from the master branch and trying to use the latest versions of everything. Publishing commands are:
$ sbt
sbt> project curryhoward
sbt:curryhoward> +publishSigned
sbt:curryhoward> sonatypeBundleRelease

This fails at the last step with the output:
2021-08-23 12:30:31.832+0200  info [SonatypeService] sonatypeRepository  : https://oss.sonatype.org/service/local  - (SonatypeService.scala:23)
2021-08-23 12:30:31.841+0200  info [SonatypeService] sonatypeProfileName : winitzki  - (SonatypeService.scala:24)
[info] Preparing a new staging repository for [sbt-sonatype] curryhoward 0.3.8
2021-08-23 12:30:31.846+0200  info [SonatypeClient] Reading staging repository profiles...  - (SonatypeClient.scala:108)
2021-08-23 12:30:34.672+0200  info [SonatypeService] No previous staging repository for [sbt-sonatype] curryhoward 0.3.8 was found  - (SonatypeService.scala:96)
2021-08-23 12:30:34.673+0200 error [Sonatype] [MISSING_PROFILE] Profile winitzki is not found. Check your sonatypeProfileName setting in build.sbt  - (Sonatype.scala:425)

I have credentials set up in $HOME/.sbt/1.0/sonatype.sbt and I have gpg keyring set up. I have publishTo := sonatypePublishToBundle.value in my build.sbt. +publishSigned works. But sonatypeBundleRelease gives the error "Profile winitzki not found". The same error happens with all other sonatypeXYZ commands. My sonatype profile is active, I am able to log in to oss.sonatype.org and see my previous releases.

sbt version: 1.5.5
sbt-sonatype version: 3.9.7
Show your build settings:

$ sbt
> sonatypeProfileName
[info] winitzki
> sonatypeRepository
[info] https://oss.sonatype.org/service/local

GitHub repository: (Having a GitHub repository for reproducing the issue would be helpful)
https://github.com/Chymyst/curryhoward

Additional context
I am writing here because I cannot understand what is happening and cannot find any help about this error. I used to be able to publish my open-source project to sonatype using this plugin. A screenshot showing my sonatype profile is attached. My sonatype account was made in 2017 and has not been changed since then (so the authentication with s01.oss.sonatype.org is not an issue). I tried to use that authentication but it does not work, failing with 401 Unauthorized.

Here is a screenshot of my sonatype profile.

sonatypeProfileName should be a domain name prefix (e.g., org.xxx, com.github.xxx, etc.)

It has not been changed at all. The user name should be set at Credential https://github.com/xerial/sbt-sonatype#homesbtsbt-version-013-or-10sonatypesbt


VTOL: disable transitions in certain flight modes

Describe problem solved by this pull request
Transitions to fixed-wing mode close to ground are dangerous, plus the current px4 navigation logic doesn't handle it well if you transition in some flight stages (you can end up in a fly-away). I do not see any use case where a transition to FW would be needed during the takeoff or landing flight mode, and in Return mode it is at least controversial.
Describe your solution

Disable transition during takeoff
Disable transition to FW during Landing and Return mode

Describe possible alternatives
While preventing the transitions to FW in takeoff and land probably is of little controversy, doing so in the Return mode can be. E.g. you have a Quad-chute far away, the vehicle is though in hover and in Return. The user knows though that the fixed-wing system is okay, and it was only a wind gust that made the vehicle's bank angle exceed the limit. The user thus want to switch to FW to be able to reach home, and for that he would then need to "Pause" first, then transition, and then either resume the mission or switch to Return again.
I still think that this PR would increase the UX, as this is rather a corner case (quadchute, but vehicle's FW actuation still okay - pretty hard to judge by the user anyway), and I would rate the prevention of the danger of doing transitions in proximity of ground higher than this inconvenience for the user with one more action required.
Test data / coverage
SITL tested.
@RomanBapst fyi

This rejects the command, but what about the actual VTOL switch?

This rejects the command, but what about the actual VTOL switch?

This is primary meant to fix the UX for an end-user setting, which is usually without RC and only with what QGC has to offer for user inputs.
I think though that the RC VTOL switch anyway doesn't have any effect in these auto modes, does it? (if it has then we should change that, but that's a different story IMO).

When enable_manual_cntrol is true, transmission using RC is allowed. Therefore, the original RC transmission is invalid in the RTL / LAND / TAKEOFF stage, so this PR is no problem

Is it possible after quadchute  and changing the mode to position, we switch VTOL to fixedwing ?
https://github.com/PX4/Firmware/issues/13035

Yes that's possible. You could also "Pause" the RTL in hover mode, and then do a transition to fixed-wing, and then resume the RTL by selecting it again.

@sfuhrer I added a note here: https://github.com/PX4/px4_user_guide/pull/743
Can you check that it addresses this question?


Fix Flakiness in TestRmRestartingContainer

fixes https://github.com/docker/docker/issues/32306

opened https://github.com/docker/docker/pull/32312 to make these unit tests, but let me know if you think they would still be valuable as an integration test

@thaJeztah in your PR, I think you could remove the integration test then 👼


Replay heuristic

Alpha shall provide a replay heuristic that is fed with a list of predetermined choices (i.e. signed atoms) which it then chooses without modification.
If a choice specified by the list is not admissible or does not involve an active choice point, an exception shall be thrown.

Note: Choices not being admissible is currently only relevant on the domspec_heuristics branch, not on master.


CSApply: Handle unbound references to methods found via dynamic lookup

Builds on #41849
class Class {
  @objc func f() {}
}

let x: (AnyObject) -> (() -> Void)? = AnyObject.f

@swift-ci please smoke test

@swift-ci please smoke test

cc @xedin

Do you mind adding CHANGELOG entries for this and https://github.com/apple/swift/pull/41849?

#41849 made it to 5.7. Does it make sense to ship this alongside?

I think it's pretty low risk. Can you tag @hborla on the cherry-pick?

@swift-ci  please test source compatibility

@swift-ci please test source compatibility

Windows failure unrelated, source compat shows a UPASS from some earlier change.


ExpoAudioStreamModule.requestPermissionsAsync does not return granted value

Hi Arthur, first of all, I want to say thank you for making this awesome project public.
I ran into a tiny issue related to ExpoAudioStreamModule.
ExpoAudioStreamModule.requestPermissionsAsync returns only the status field, while it seems it should have the granted field at least, from example codes in the docs.
const response = await ExpoAudioStreamModule.requestPermissionsAsync();
console.log(response);

// android: {"canAskAgain": true, "expires": "never", "granted": true, "status": "granted"};
// iOS: {"status": "granted"}

// From the docs:
import {
    ExpoAudioStreamModule,
} from '@siteed/expo-audio-stream'

const requestPermissions = async () => {
    const { granted } =
        await ExpoAudioStreamModule.requestPermissionsAsync()
    if (granted) {
        console.log('Microphone permissions granted')
    } else {
        console.log('Microphone permissions denied')
    }
}

requestPermissions();

Probably, it is because of these lines in the file ExpoAudioStreamModule.swift.
AsyncFunction("requestPermissionsAsync") { (promise: Promise) in
    AVAudioSession.sharedInstance().requestRecordPermission { granted in
        if granted {
            promise.resolve(["status": "granted"])
        } else {
            promise.resolve(["status": "denied"])
        }
    }
}

It seems some other functions, such as getPermissionsAsync, also have status as the only returned field, while I'm not sure it is intended or not.

Hi @kimkanu , thanks for bringing this up. I will push a fix very soon.

Closing as it should be fixed,


Remove version: qBittorrent.qBittorrent version <IP_ADDRESS>

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://downloads.sourceforge.net/project/qbittorrent/qbittorrent-win32/qbittorrent-<IP_ADDRESS>/qbittorrent_<IP_ADDRESS>_x64_setup.exe
Status Code: 200
(Automated message - build 896)

Close with reason: Package still available.;


Server shutdown crashes when a connection had a socket error

If a connection has a socket error, and doesn't get drained before a server tries to shutdown, then an assert in requestDisconnect() will get tripped, due to trying to set fsr_blackhole twice. Here's an example test program (toggle CRASH to effect draining):
var mod_bunyan = require('bunyan');
var mod_fast = require('../lib/fast');
var mod_net = require('net');
var mod_vasync = require('vasync');

var LOG = mod_bunyan.createLogger({
    name: 'fast-test',
    src: true,
    streams: [ {
        stream: process.stderr,
        level: 'trace'
    } ]
});

var CRASH = true;

var PORT = 2000;

var SERVER_SOCK = null;
var SERVER_FAST = null;
var CLIENT_SOCK = null;
var CLIENT_FAST = null;

var RPC = null;

function endpoint(rpc) {
    RPC = rpc;
}

mod_vasync.pipeline({
    funcs: [
        function (_, cb) {
            LOG.info('setting up server');

            SERVER_SOCK = mod_net.createServer({ allowHalfOpen: false });

            SERVER_SOCK.on('error', cb);

            SERVER_SOCK.on('listening', function () {
                LOG.info('server listening');
                cb();
            });

            SERVER_FAST = new mod_fast.FastServer({
                log: LOG.child({ component: 'fast-server' }),
                server: SERVER_SOCK
            });

            SERVER_FAST.registerRpcMethod({
                rpcmethod: 'endpoint',
                rpchandler: endpoint
            });

            SERVER_SOCK.listen(PORT);
        },
        function (_, cb) {
            LOG.info('setting up client');

            CLIENT_SOCK = mod_net.connect(PORT, '<IP_ADDRESS>');

            CLIENT_SOCK.on('error', cb);

            CLIENT_SOCK.on('connect', function () {
                LOG.info('client socket connected');

                CLIENT_FAST = new mod_fast.FastClient({
                    log: LOG.child({ component: 'fast-client' }),
                    nRecentRequests: 100,
                    transport: CLIENT_SOCK
                });

                cb();
            });
        },
        function (_, cb) {
            LOG.info('performing rpc');

            var req = CLIENT_FAST.rpc({
                rpcmethod: 'endpoint',
                rpcargs: [ ],
                log: LOG
            });

            req.on('data', function (data) {
                LOG.info({ data: data }, 'RPC received data');
            });

            req.on('error', function (err) {
                LOG.info(err, 'RPC had error');
            });

            req.on('end', function (err) {
                LOG.info(err, 'RPC ended');
            });

            cb();
        },
        function (_, cb) {
            LOG.info('destroying client');

            // Now we close the socket to cause onConnectionError.
            CLIENT_FAST.detach();
            CLIENT_SOCK.destroy();

            LOG.info('server ends rpc');

            // Respond to generate a socket error
            RPC.write({ a: 'foo' });
            RPC.end();

            function finish() {
                LOG.info('server shutting down');

                // Server then goes to shut down
                SERVER_SOCK.on('close', function () {
                    SERVER_FAST.close();

                    cb();
                });
                SERVER_SOCK.close();
            }

            if (CRASH) {
                finish();
            } else {
                setImmediate(finish);
            }
        }
    ]
}, function (err) {
    if (err) {
        throw err;
    }

    LOG.info('finished');
});

It seems that fc_socket_error should be checked in the same places that fc_server_error is.

The issue here is that when the server goes to shut down, it calls connTerminate() on the connection, which checks fc_server_error to see if there's been a previous error that's caused the connection to begin termination and draining. If there's been a connection error though, then onConnectionError() will have been called for the connection, and it will have already set fc_socket_error and begun shutting down. When connTerminate() runs, it should consider any socket errors that have happened, and skip trying to disconnect requests.


fix proxy example to work in real environments

we only support http proxy urls and not https.
also moved {} around to make it clearer the individual pieces that need to be replaced.

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

#sign-off


Download Video and Video HLS from Any Websites

add features, Download Video and Video HLS from Any Websites from browser

+1
alternative: https://add0n.com/hls-downloader.html


Configuration mentioned at Hashicope Vault doc doesn't work

Description:
Please refer to https://github.com/wso2/micro-integrator/issues/2126
Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

Closing this as issue already exists.


Inconsistent capitalization on game message

"room" in "room Code"
"region"
Super minor issue

Haha yep, saw the same thing, hoped no one would notice...


VUE2 NUXT vue-social-sharing .   Error : Uncaught DOMException: An attempt was made to break through the security policy of the user agent.

Uncaught DOMException: An attempt was made to break through the security policy of the user agent.
at ie (https://www.XXXX.com/_nuxt/a1925a6.js:2:12130)
at Object.get [as popupWindow] (https://www.XXXX.com/_nuxt/a1925a6.js:2:10906)
at vo.get [as popupWindow] (https://www.XXXX.com/_nuxt/a1925a6.js:2:40591)
at https://www.XXXX.com/_nuxt/dadf402.js:2:64148

Please tell me how to solve this problem. If you know, thank you for your support.

Hello @nicolasbeauvais , We are also getting the same issue. Could you please, help! Atleast for starter, giving some insights  on the issue. ?

@suangencong : Did you find fix for this ? I am also facing the same problem.

I am also facing the same problem.


🐞The Stopping Staking Manager Recovery page is submittable with empty input

Describe the bug
The Stopping Staking Manager Recovery page can be submitted without the Transaction Hash field getting filled out.
To Reproduce

Go to a dapp page and navigate to DeFi/DeFi Offering.
Press Stop.
Scroll down and press Recovery.
Scroll down again and submit without filling out anything.
The page will now load and stop after a while.

Expected behavior
Ideally, the Start button should be disabled if the inputs are empty or an error should appear (without the long loading times).
Screenshots

Web3 Scenario (please complete the following information):

Env.: Desktop
OS: macOS 10.15
Browser: Safari
Version: 13.1.2
Provider: Metamask

Reward
Discord Username and #: the4kman#4895
ETH Wallet: 0x0De8947c2ABd59C201e5EcE142bFCd22253BFC0d

thank you to have opened this issue,
this is a design choice, because if you don't fill inputs everything works normally.
We made this choice, because users are able to fill just a recover input if they needs.
Have you some idea to improve the experience?
Issue From Bug to Improvement Proposal

@alet89 I would indicate somehow that the field is optional (for example, by adding the "(optional)" suffix to the placeholder text)


Prevent overwrite of Slim embedded options

Fixes #1925, and may also fix #1152.

Not quite ready for prime time: embedded Sass and SCSS not working correctly. Will fix and add tests.


Be able to overwrite a already saved map

Be able to save small change to a already done map to not need to redo all assignments of the the runs.

Take care if a team  has already scored on the actual map!! This may be very confusing for the system to handle.

Was fixed in rewrite branch


[server] End to end RMD chunking support for A/A store ingestion (First part)

[server] End to end RMD chunking support for A/A store ingestion (First part)
This PR implements end to end RMD chunking support for A/A store with some limitations. With the implementation, all PUT/UPDATE operations can be processed correctly when value chunking and RMD chunking is enabled. Value and RMD will be chunked accordingly and will be re-assembled during read. This PR also adds an integration test to verify this behavior.
Note: There are two know issues in this implementation and will be addressed in the following PR for easier review experience.

DELETE operation can also be too big when existing RMD record is too big. The support of DELETE chunking will be added in the next PR.
During the implementation, we found the repush does not carry RMD when A/A + Chunking is enabled. This is not the correct behavior. Also, in the above case, if the latest operation around a key is a DELETE, the current implementation does not send it to the new version topic. This issue will also be addressed in a separated PR.

How was this PR tested?
Added new integration test. Internal CI
Does this PR introduce any user-facing changes?

[x] No. You can skip the rest of this section.
[ ] Yes. Make sure to explain your proposed changes and call out the behavior change.

A side comment: why this Github VeniceCI run takes this long and fail? My Venice CI submission always pass within reasonable time...


Not able to build

I'm trying to build the latest version but no luck. I want to send a PR adding support for Data.wz clients, so you cna open up old clients, but no luck building. I saw you uploaded a september version on another issue and that built normally, but newest one can't.
Can you help me out?

Why PR? This supported Data.wz for a long time.
https://www.mediafire.com/file/t0t7bpjrpvc05fh/[MapleNecrocer](https://www.mediafire.com/file/t0t7bpjrpvc05fh/MapleNecrocer.zip/file).zip/file

I'll check that out!
About the Data.wz support, you are right! But for older versions it doesn't seem to work, so I wanna take a look.
Versions KMS 1.21 ~ 1.36. Beta/Alpha versions with the oldest UI.
If you are interested, this is the installer for the KMS 1.21: https://mega.nz/file/9p1xWKRT#V8TodI8Y2cBNnH2yQs9fQOPUkIFyD2kjdi5tU25lflE

The building now works! Thank you so much 😄
I'm now working on a fix for those REALLY old versions, turns out those versions only contain the string inside info folder, for Mob, Map, Character, Item, etc.

work.
Thanks for the PR and contribution.


Add CLI argument to open a specific file

Would be useful if planetmapper filename.fits did something

[ ] Add argparse type functionality

[ ] Version
[ ] Help
[x] Open specific file
[ ] Open multiple files?

[ ] Change CLI hook to dedicated function that defers importing planetmapper until after printing something helpful (to improve feeling of responsiveness so we don't have to wait for imports to happen before getting any feedback)

https://github.com/conda-forge/staged-recipes/pull/22991#pullrequestreview-1464502734 - add e.g. planetmapper --help to conda checks


Add the "repository", including "last change" to build events

When evaluating the "lead time for changes" metric, we need to be able to correlate change events to build events, so that we may discover which builds include a specific change. From the build we can then find out the associated deployment.
Build events today are relatively bare, only the type and optional artifact id are specified.
This extra data is needed:

the repository, like the one already included in change events
the last change, which could be an attribute of the repository or separate. It must be an identifier that can be passed to the SCM to ask whether a specific change is included or not.

I agree that we need to be able to correlate the build events with their corresponding change events, when such exists. I do however believe that we should not add mandatory properties to the build events with information that is duplicate of what is already provided in the change event(s). Instead we should make it possible to correlate the events with each other by other means, such as by "links" or by context type fields.
We should also be aware that it is not always a one-to-one mapping between an artifact and a source code repo. An artifact could take input from multiple source repos, and one source repo could produce multiple artifacts, so the solution we provide needs to cater for that. One way to deal with multiple sources used for one artifact would be through "compositions".

When it comes to the SLSA level 4 I interpret that it requires that the person/engine triggering the build can't add in parameters but all parameters must be part of a build script or an input. E.g. if we would have a composition event this could serve as an input.
When it comes to what information should be added in the events we probably should state that in the spec. We have earlier had a discussion about "heavy" and "lightweight" events and I guess we are circling back to that discussion here. I would vote for not including repository information in this event just as @e-backmark-ericsson pointed out.
Also, if we decide to go for a repository it would be good if we could put some wording on binary vs source code builds. Some builds will not just use source code (text) but may well include binaries as input to the build.
Regarding

a build is not necessarily associated to a change. There could be manually or periodically triggered builds for instance

If a build not associated to change why do you want to include the last change id?

When it comes to the SLSA level 4 I interpret that it requires that the person/engine triggering the build can't add in parameters but all parameters must be part of a build script or an input. E.g. if we would have a composition event this could serve as an input.
When it comes to what information should be added in the events we probably should state that in the spec. We have earlier had a discussion about "heavy" and "lightweight" events and I guess we are circling back to that discussion here.

I don't think this should bring back the discussion about "heavy" vs. "lightweight" but the fact that you bring this up is a signal that we should document out decisions about this in the spec or primer.
For me "lightweight" means that we include links to large content, rather than base64 encode it into a blob in the event.

I would vote for not including repository information in this event just as @e-backmark-ericsson pointed out.

I'm not quite sure I understand this, I think it would be useful to discuss in the cdevents meeting.
I'll add it to the agenda.

Also, if we decide to go for a repository it would be good if we could put some wording on binary vs source code builds. Some builds will not just use source code (text) but may well include binaries as input to the build.

I'm not sure I understand this either?  A source repo does not imply that there are no binary dependencies.
Usually dependencies (binary and not) are expressed in the form of one or more file that is in the source repo.
There may be multiple repositories involved, but I would suggest to start with the case of one and extend it from there when we get to that situation in a poc.

Regarding

a build is not necessarily associated to a change. There could be manually or periodically triggered builds for instance

If a build not associated to change why do you want to include the last change id?

The last change ID tells us the state of the repository against which the build was executed. The fact that the change happened at some point in time doesn't have to be the trigger of the current build.

Removed from the v0.1 scope. For the dora metrics we can rely on the artifact events alone.


switch naming convention and behavior for access log format vs encoding

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: GregHanson
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: hklai
If they are not already assigned, you can assign the PR to them by writing /assign @hklai in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

related to https://github.com/istio/istio/issues/10056

/test e2e-mixer-no_auth

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: GregHanson, rshriram
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [rshriram]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@GregHanson: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth.sh
3244ce369554987273f33e18fffcd9a70e9f434c
link
/test e2e-mixer-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-mixer-no_auth

@GregHanson: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth-mcp.sh
3244ce369554987273f33e18fffcd9a70e9f434c
link
/test e2e-mixer-no_auth-mcp

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


[Bug] Firebase for Unity v10.0.1 Cannot run on Android Platform in Editor Mode！

[REQUIRED] Please fill in the following fields:

Unity editor version: Unity2021.3.11f1
Firebase Unity SDK version: v10.0.1
Source you installed the SDK: .unitypackage (.unitypackage or Unity Package Manager)
Problematic Firebase Component: AppCore (Auth, Database, etc.)
Other Firebase Components in use: Crashlytics,Analytics (Auth, Database, etc.)
Additional SDKs you are using: Facebook,Applovin Max (Facebook, AdMob, etc.)
Platform you are using the Unity editor on: Mac (Mac, Windows, or Linux)
Platform you are targeting: Android (iOS, Android, and/or desktop)
Scripting Runtime: Mono (Mono, and/or IL2CPP)
Pre-built SDK from the website or open-source from this repo: Pre-built SDK

[REQUIRED] Please describe the issue here:
When run in editor mode with switched to Android Platform, FirebaseApp cannot be construct staticly!
See the following log:
DllNotFoundException: FirebaseCppApp-10_0_1 assembly: type: member:(null)

DllNotFoundException: FirebaseCppApp-10_0_1 assembly:<unknown assembly> type:<unknown type> member:(null)
Firebase.AppUtilPINVOKE+SWIGExceptionHelper..cctor () (at /Users/runner/work/firebase-unity-sdk/firebase-unity-sdk/android_unity/armeabi-v7a/app/swig/Firebase.App_fixed.cs:3916)
Rethrow as TypeInitializationException: The type initializer for 'SWIGExceptionHelper' threw an exception.
Firebase.AppUtilPINVOKE..cctor () (at /Users/runner/work/firebase-unity-sdk/firebase-unity-sdk/android_unity/armeabi-v7a/app/swig/Firebase.App_fixed.cs:3936)
Rethrow as TypeInitializationException: The type initializer for 'Firebase.AppUtilPINVOKE' threw an exception.
Firebase.AppUtil.SetLogFunction (Firebase.LogUtil+LogMessageDelegate arg0) (at /Users/runner/work/firebase-unity-sdk/firebase-unity-sdk/android_unity/armeabi-v7a/app/swig/Firebase.App_fixed.cs:4646)
Firebase.LogUtil..ctor () (at /Users/runner/work/firebase-unity-sdk/firebase-unity-sdk/app/src/LogUtil.cs:81)
Firebase.LogUtil..cctor () (at /Users/runner/work/firebase-unity-sdk/firebase-unity-sdk/app/src/LogUtil.cs:37)
Rethrow as TypeInitializationException: The type initializer for 'Firebase.LogUtil' threw an exception.
Firebase.FirebaseApp..cctor () (at /Users/runner/work/firebase-unity-sdk/firebase-unity-sdk/android_unity/armeabi-v7a/app/swig/Firebase.App_fixed.cs:1897)
Rethrow as TypeInitializationException: The type initializer for 'Firebase.FirebaseApp' threw an exception.
Pluto.LiteGame.Firebase.FirebaseInit.Awake () (at Assets/Scripts/Firebase/FirebaseInit.cs:27)
UnityEngine.Object:Instantiate(GameObject, Transform)
<InitDelayPrefabs>d__46:MoveNext() (at Assets/Scripts/UI/Common/AZ_GameInitLoading.cs:258)
UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr) (at /Users/bokken/buildslave/unity/build/Runtime/Export/Scripting/Coroutines.cs:17)

In the log, we can find firebase-unity-sdk/android_unity/armeabi-v7a/app/swig, it is an android implement? why you use android implement in Editor mode? why not use an eiditor implement?
Due to this issue, I cannot use FirebaseApp anytime in Editor mode with Android Platform.
(Please list the full steps to reproduce the issue. Include device logs, Unity logs, and stack traces if available.)
Steps to reproduce:
Have you been able to reproduce this issue with just the Firebase Unity quickstarts (this GitHub project)?
What's the issue repro rate? (eg 100%, 1/5 etc)
What happened? How can we make the problem occur?
This could be a description, log/console output, etc.
If you have a downloadable sample project that reproduces the bug you're reporting, you will
likely receive a faster response on your issue.
Relevant Code:
// TODO(you): code here to reproduce the problem

It looks like this is a duplicate of #449
I'll close this issue in order to keep the discussion together in #449

Reopening because as mentioned in https://github.com/firebase/firebase-unity-sdk/issues/449#issuecomment-1297966811, the other issue #449 mentioned docker containers or other context that does not apply here, so this is potentially a separate issue.

Ah, so there is a bit of confusion here.  There are two main files for each library, one for C# and one for C++.  C++ have a different version of the library for each platform, but C# has only two versions, one for iOS and one for everything else (the difference is whaat type of dllimport statement it uses, as described here: https://docs.unity3d.com/2021.1/Documentation/Manual/NativePlugins.html)
This is why it is using the "Android" version of the C# library, but it should work for the editor as well.
As for the issue you are seeing, there are a bunch of different reasons that the dll could not be found.  It should be looking for Firebase/Plugins/x86_64/FirebaseCppApp-10_0_1.bundle, so can you confirm that the file is there, and the editor settings indicate it is being linked correctly.
Another issue that can come up on Mac is the security and privacy settings.  Here is a video that covers the issue: https://www.youtube.com/watch?v=1DeG51P7BBc
Can you check that file, and make sure it seems correct?

This is what I can see on my Mac. Is it right?
I am sure it is not be deleted. If I reimport the .unitypackage file of the SDK, I have nothing new to import.

Has the problem been solved

Has the problem been solved

I dont think so.

That's too bad. I have the same problem. I can't get into the project

That's too bad. I have the same problem. I can't get into the project

Comment them in editor mode. using "#if define UNITY_EDITOR".

Hi @CodeMasterYi,
Unfortunately we can't seem to reproduce this issue with our standard quickstarts. The only thing that comes to mind is that the macOS security machanisms have blocked Unity's use of the Firebase Unity Package .dll files. Could you start with a fresh project and attempt to re-import the Firebase Unity Packages and note any and all windows that appear during the installation of the Firebase packages and the execution of the build on your machine?
Thanks!

The cause of this problem is the lack of a C++ compilation environment，Part of FirebaseDll is written in C++，Just install VS

The cause of this problem is the lack of a C++ compilation environment，Part of FirebaseDll is written in C++，Just install VS

@sunjiakungithub Don't you see the word Mac?

I think the issue I'm having is the same issue.
I think it has to do with mac Security & Privacy blocking it but not sure
https://github.com/firebase/firebase-unity-sdk/issues/510#issuecomment-1315098229


add a write sender adaptor

Usage:
auto sndr = write(read(cpo), with(cpo, value));
auto [result] = sync_wait(sndr).value();
assert(result == value);

refs #540

write is not in the current version of P2300, right?

Correct. I need to write a paper to propose a bunch of the environment manipulators.


[#3330] - push local_settings import to bottom

Pull Request Checklist:

[x] Positive Test Case Written by Dev

[x] Automated Testing

[x] Sufficient User and Developer Documentation

[ ] Passing Jenkins Build

[ ] Peer Code review and approval

Positive Test Case

When deployed ensure local_settings overwrite settings.  (I tested this on beta testing HSWS_ACTIVATED)

@phuongdm - Could you verify whether there is more work to be done with deployments for this change to stick?  My understanding is settings.py isn't touched on deployment anymore since we moved all machine specific settings to local_settings.

Yes, settings.py does not take any affect on deployment process


Can't  build apps on Asahi Linux

All,
I am wanting to move from MacOS to Asahi Linux (m2 silicon, arm64) and have one problem with media_kit when I try and build my app on Asahi Linux:
CMake Error at flutter/ephemeral/.plugin_symlinks/media_kit_video/linux/CMakeLists.txt:16 (add_library):
  Target "media_kit_video_plugin" links to target "PkgConfig::mpv" but the
  target was not found.  Perhaps a find_package() call is missing for an
  IMPORTED target, or an ALIAS target is missing?

I have tried both Fedora and Ubuntu spins of Asahi Linux and have ensured that (on Ubuntu for these names) libmpv-dev and mpv are both installed:
$ sudo apt install libmpv-dev mpv
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
libmpv-dev is already the newest version (0.36.0-1ubuntu1).
mpv is already the newest version (0.36.0-1ubuntu1).
$
$ locate mpv.pc
/usr/lib/aarch64-linux-gnu/pkgconfig/mpv.pc

Can anyone please point me in the right direction.

getting the same error on Fedora
[✓] Flutter (Channel stable, 3.16.8, on Nobara Linux 39 (KDE Plasma) 6.7.0-204.fsync.fc39.x86_64, locale
    en_US.utf8)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✗] Chrome - develop for the web (Cannot find Chrome executable at google-chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[✓] Linux toolchain - develop for Linux desktop
[✓] Android Studio (version 2023.1)
[✓] VS Code (version 1.85.1)
[✓] Connected device (1 available)
[✓] Network resources```

You must be familiar with your GNU/Linux distribution's package management. I haven't used every GNU/Linux flavor on planet.
In future, we might consider providing standalone static builds for GNU/Linux too like other platforms, however lack of time & interest.

Given I tested Ubuntu and the only difference being the architecture, I was hoping for a pointer of where to look next. It isn't like Ubuntu is an out-there option and I am happy to investigate; but I'm not sure where to start!


feaLib miscompiles chaining rules with non-single substitution lookup references

When a chaining substitution rule contains multiple lookup references, and those references are to anything more complex than single substitution lookups, then feaLib is liable to miscompile that rule.
Example 1 of section 5.f.i of the feature file spec contains such a rule:
    substitute [ a e i o u] f' lookup CNTXT_LIGS i' n' lookup CNTXT_SUB;

The spec explains that given the input glyph sequence a f i n, the output glyph sequence will be a f_i n.end. That means that lookup references are written after the glyphs they apply to, without considering how other referred-to lookups might shift sequence indices. In other words, this rule does what it seems like it obviously should do.
However, this is not what feaLib does. feaLib compiles each lookup reference with a sequence index of whatever the index is of the glyph in the rule, and the references are ordered in ascending order by sequence index. f is at index 0, so lookup CNTXT_LIGS gets a sequence index of 0. n is at index 2, so lookup CNTXT_SUB gets a sequence index of 2.  CNTXT_LIGS is applied before CNTXT_SUB. This produces the wrong behavior: by the time CNTXT_SUB applies, the input glyphs are f_i n, so there is nothing at index 2.
Here is a full example. It uses Noto Sans as a base for convenience but replaces its GSUB with something based on the spec’s example.
$ curl -LOs https://github.com/googlefonts/noto-fonts/raw/6ba0153eb79a01d69f96fbd87512fe1ca1e778ef/unhinted/otf/NotoSans/NotoSans-Regular.otf
$ python3 <<'EOF'
from fontTools.feaLib.builder import addOpenTypeFeaturesFromString
from fontTools.ttLib.ttFont import TTFont
with TTFont('NotoSans-Regular.otf') as font:
    del font['GPOS']
    addOpenTypeFeaturesFromString(font, '''
lookup CNTXT_LIG {
    substitute f i by fi;
} CNTXT_LIG;

lookup CNTXT_SUB {
    substitute e by uni2C78;
    substitute n by eng;
} CNTXT_SUB;

feature liga {
    substitute [a e i o u] f' lookup CNTXT_LIG i' n' lookup CNTXT_SUB e';
} liga;
''')
    font.save('test.otf')
EOF
$ hb-shape --no-positions test.otf afine
[a=0|fi=1|n=3|uni2C78=4]

The rule is clearly meant to apply CNTXT_SUB to n, not to e, so the correct output is a fi eng e.
One way to fix this is to compile the lookup references with sequence indices in descending order, instead of the current ascending order. That is, CNTXT_SUB would be applied at index 2, then CNTXT_LIG would be applied at index 0. People could be relying on the current order, but unfortunately I don’t see another way to make the example in the spec work.

This would be an extremely breaking change.

Moreover, makeotf also has the same issue.
$ curl -LOs https://github.com/silnrsi/font-nokyung/archive/refs/tags/v1.490.tar.gz
$ tar -zxf v1.490.tar.gz
$ cat >features.fea <<'EOF'
languagesystem DFLT dflt;
languagesystem latn dflt;

lookup CNTXT_LIG {
    substitute f i by fi;
} CNTXT_LIG;

lookup CNTXT_SUB {
    substitute e by E;
    substitute n by N;
} CNTXT_SUB;

feature liga {
    substitute [a e i o u] f' lookup CNTXT_LIG i' n' lookup CNTXT_SUB e';
} liga;
EOF
$ makeotf -f font-nokyung-1.490/source/Nokyung-Regular.ufo -o Nokyung-Regular.otf -ff features.fea >/dev/null
$ hb-shape Nokyung-Regular.otf afine
[a=0+936|fi=1+1016|n=3+991|E=4+970]

So the example in the spec is wrong. Never mind then.


Allow rotating the map

I find it very convenient how EveryDoor allows freely rotating the map even when showing aerial imagery. It's very useful to orient the map in the same way that you are facing so as to better match what you see with what's on the map.
So, as a follow up to #5, which asked for bypassing the max zoom level of the tiles, I would like to request also that the map be freely rotatable rather than having a fixed orientation with north pointing up.

Released in v1.7.0

Oh wow, that was FAST! Thanks so much for accepting the suggestion and the quick implementation! :star_struck:


Late variable problem & instance member 'user' can't be accessed in an initializer

Hello, I am trying to pass the user.uid from the NavigationPage to ProfilePage. BUT I get this error message under late ("Variables must be declared using the keywords 'const', 'final', 'var' or a type name. Try adding the name of the type of the variable or the keyword 'var'") and this error message under user ("The instance member 'user' can't be accessed in an initializer. Try replacing the reference to the instance member with a different expression"). I am using the following code:
class NavScreen extends StatefulWidget {

      _NavScreenState createState() => _NavScreenState();

}

class _NavScreenState extends State<NavScreen> {

      late final user = FirebaseAuth.instance.currentUser;

      final List<Widget> _screens = [

            ProfileScreen(profileId: user.uid),

      ];

}

Any ideas on a possible solution? Thanks

Hi!
What if you make your _screens list a late declaration? Like this:
late final List<Widget> _screens = [
  ProfileScreen(profileId: user.uid),
];

This way you can access a variable in a declaration.

Hi @Alvaro-99
It seems you are asking for assistance on personal code. Please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


Disabling animation via timingConfig breaks tab selection (requires two clicks)

Current behaviour
I disabled animation between tabs using the timingConfig property of TabView. However, after doing so, when selecting a tab, the content changes appropriately but the tab itself isn't highlighted until I click again (on the same or a different tab).
Expected behaviour
The tab highlight updates along with the content when animation is disabled.
Screenshots (if applicable)

What have you tried
Tried upgrading react-native-gesture-handler and react-native-reanimated but neither fixed the issue.
No known workarounds
Your Environment

software
version

ios or android
ios

react-native
0.61.5

react-native-tab-view
2.13.0

react-native-gesture-handler
1.5.0 (upgraded to 1.6.0)

react-native-reanimated
1.3.2 (upgraded to 1.7.0)

node
11.12.0

npm or yarn
6.7.0

yeah I get the same issue, is there another way of disabling the animation? (I'm using this library through react navigation)

I use 2.14.0, and experienced the problem when setting duration to zero, BUT any other really small value fixed it for me:
      timingConfig={{
        duration: 1,  // milliseconds
      }}

Works on the web as well (where I'm using it on the first place..).

I dug some more into this. I replaced the tabBar with my own tab bar component, and it turns out that the problem is with the animation code for the Tab Items. If I don't do any animations for the tab labels, things work out properly.
It seems the position prop given to the tab bar component is broken when the timingConfig prop is supplied. I don't know enough about animations to dig any deeper right now, but this might help.

duration: 0, onChange this.index and this.position not triggered on first click.
duration: 1-16, onChange this.position not triggered on first click.
duration: 17, onChange working for both this.index and this.position , but may result in slightly off this.position.
Any custom pager available without animation?

Also if I use my own tabbar component it breaks when i use duration: 0

Closing since this is no longer relevant in latest version at uses react-native-pager-view


adding 3x5 plates

The main PCB has extra holes between ring and pinky column in case the user decides to break away the last column next to pinky. But the plates have no 3x5 kicad or break away option. This PR adds a separate 3x5 plates for those who want it

@vgm106 Thank you for your PR. Could you rename to mini instead of 3-5?

Thank you for your contributions!


Breakage on thai characters: Invalid character in header content

Context:
I am using this package (v4.10.1) in my server on Lambda. I started getting some spam traffic, not really bothered by it except it is causing 500 - internal server error in my web service. I am using this package in conjunction with Next.js v13 but I don't think that part is the culprit.
Stack trace:
2023-02-09T21:19:15.973Z	d43c0d20-4a2f-4c10-a452-5d9ff4ab84a2	ERROR	TypeError [ERR_INVALID_CHAR]: Invalid character in header content ["Location"]
    at ServerlessResponse.setHeader (node:_http_outgoing:579:3)
    at ServerlessResponse.setHeader (/var/task/node_modules/@vendia/serverless-express/src/response.js:62:13)

Payload:
This is what the thai url is that's breaking everything

https://example.com/%E0%B8%96%E0%B8%AD%E0%B8%99-%E0%B8%9F%E0%B8%99-%E0%B8%84%E0%B8%94-%E0%B8%A3%E0%B8%B2%E0%B8%84%E0%B8%B2-%E0%B8%9B%E0%B8%A3%E0%B8%B0%E0%B8%81%E0%B8%99-%E0%B8%AA%E0%B8%87%E0%B8%84%E0%B8%A1/

Edit/Additional context:
What's happening here is that with the trailing slash, Next.js is trying to redirect to the same url but without the slash. That redirect means sending in a Location header, which is where its crashing. This same url works in "bare" Next.js server.

This seems to be unrelated to this package, and related to Next.js instead https://github.com/vercel/next.js/issues/17907
Closing as external


Method to get values from a label

Could we get a method to retrieve values from a given label.
Would be useful in situations where user is searching using the enum label, but we need to filter using the value.

In the meantime can filter on the labels array, but I think it may be a useful convenience method.

@Ezekiel-Webfox how would you handle the case of there being multiple items that have the same label? Return the first found? Return an array if there are multiple found? Always return an array?

@hailwood I would say always return an array for consistency


improvements to message replay code

This checks the first five boxes on #457. It's a bit fiddly, lots of edge cases and inadequately tested code paths.

Basically, uh, I started implementing #475, then as part of that I found several bugs in the bouncer code, and the fixes conflicted with work in this branch so I just made them on top.
The most significant bug is that the connection limiter was "leaking" IPs for bouncer sessions, i.e., if you attached an additional session to a nick from an IP, then disconnected that session, its entry in the connection limiter would never be cleaned up.
I made some architectural changes to make bugs like this a little less likely. One of them is that on a reattach, the old goroutine exits as quickly as possible without trying to play the registration burst --- that's deferred to the new goroutine.

This looks like a veeeery fun one! Gonna be interesting to see how the bugs shake out of this as it's used in the real world ;D
After those few changes are made (Draft -> proposed, and renaming junkTags to transientTags or maybe unstorableTags for the extra clarity), totally happy for this to be merged in as-is. Nice on separating the history stuff out into a separate module as much as we're able to.


Add support for Traffic Policy

Not sure if this is a bug in the upstream lib or not but I wasn't able to get my test working when I only had one of inbound or outbound. It required both, otherwise the builder returns an error:

  ✖ online › policy Rejected promise returned by test
  ─

  online › policy

  __test__/online.spec.mjs:525

   524:   const [httpServer, session] = await makeHttpAndSession();
   525:   const listener = await session.httpEndpoint().policy(policy).listen();
   526:   const response = await forwardValidateShutdown(t, httpServer, listener, listener.url());

  Rejected promise returned by test. Reason:

  Error {
    code: 'GenericFailure',
    message: 'Error parsing policy, failure to parse or generate policy',
  }

  › file://__test__/online.spec.mjs:525:49

  ─

  1 test failed

Probably a bug in rust land, it's set to generate defaults for anything missing, but may have missed something. Will look into.


Couple microphysics to prognostic EDMF

### Tasks
- [ ] https://github.com/CliMA/ClimaAtmos.jl/issues/2560
- [x] couple 1-moment microphysics to prognostic edmf

I know that there might be stability issues ahead, but we can tackle them in a separate issue


Shiki with iMac.kext causes NVidia Webdrivers to fail

When using the available iMac.kext.zip with Shiki 1.9.0 on 10.12.1 with a GTX980 it causes the Nvidia WebDrivers (3<IP_ADDRESS>f01) to fail to load properly.
The NVidia driver manager still claims the drivers are being used - however they are not and the graphics card is not detected at all:

You'd better write your own plist kext, because it depends on the gpu you use, and the iMac.kext you found is just an example which by no means is supported or expected to work.
If you have issues understanding it, well, it is out of Shiki project. You might want to ask igork at applelife.ru, but I do not know if he has any time to help you.


Inform the user in the UI if an artifact will be delete and when

There is no way to know when at artifact will be delete in the UI. Add to <ArtifactPanel/> some text to tell users if this will happen. E.g.  "Artifact will be automatically deleted shortly after the workflow completes"

  const spec = execSpec(workflow);
     const artifactGCStrategy =
         spec.templates.find(t => t.name === workflow.status.nodes[artifact.nodeId].templateName)?.outputs?.artifacts.find(a => a.name === artifact.name).artifactGC?.strategy ||
         spec.artifactGC?.strategy;


Support networkx.Graphs as input to Lattice

Summary
Closes #465.
Details and comments
Split 2/2 of PR #467.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

7 of 9 (77.78%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 82.243%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit_nature/problems/second_quantization/lattice/lattices/lattice.py
7
9
77.78%

Totals

Change from base Build<PHONE_NUMBER>:
0.002%

Covered Lines:
8323

Relevant Lines:
10120

💛  - Coveralls


bochs: Added support for customizing debugger

--with-gdb-stub will enable GDB debugger
--with-debugger will enable generic debugger

@BrewTestBot test this please.

@BrewTestBot test this please.

Merged. Thank you for your contribution to Homebrew!


[hip] add HIP_INIT_API/ihipLogStatus for hipExtLaunchMultiKernelMulti…

…Device API

@asalmanp I already had #1263 for this. I updated that. Let me know if something is still missing there.

Closing this in favor of #1263.


fix: added missing destruction of request after receiving the response and removing all listeners

Previously this resulted in a high file descriptor usage in Lambda until the function reached the hard limit
This is a fix for the IBM customer support ticket: TS016453828
More details about the detection of the problem and steps to reproduce are documented in the ticket.
A short summary of the problem:
Old requests were not correctly cleaned up which was mainly a problem for Lambda functions with a lot of reuse (warm Lambdas), since the number of file descriptors continued increasing over time until the Lambda hard limit was reached and the function crashed.
While this fixes the problem described above, I have the feeling the root rause which led to this problem becoming visible might be related to failing heartbeat checks and the actual extension binary which I couldn't check further.
Testing

Node version of the Lambda
File descriptor problem resolved
Traces received in Instana

Node 16.x
✅
✅

Node 18.x
✅
✅

Node 20.x
✅
✅

Successor of #1208 (using - instead of / in the branch name)

@janritter Thank you once again for creating the PR. It appears that the tests are failing; I will look into it as soon as possible.

Please note that the commit message should include a sign-off statement, as outlined in our contributing guidelines.

@aryamohanan sorry, I missed the sign-off part.
I pushed an updated version of the commit which is signed-off. I also included the test addition from your commit, I hope that's ok.

I have created another PR at https://github.com/instana/nodejs/pull/1217 and merged it into the main branch. There were two issues encountered with this PR:

Verification was missing (the commit appeared as unverified).
The commit length exceeded our CI's limit, causing it to fail.

@aryamohanan thanks, the verification thing is strange, especially since it's marked as verified in GitHub. For the commit length, the included commitlint seems to use a different length config.
Do you already have an estimate when the fix will be available as a Lambda Layer?

@janritter We are considering releasing it on Monday. Does that work for you?

@aryamohanan Can you let me know once the new version is available with the layer version numbers for eu-central-1 (I think the docs with the versions are usually updated a bit delayed)

@janritter We will release the new version at the earliest opportunity and will let you know as soon as it is available. Thank you for your patience.

Hello @janritter, we've rolled out a new version containing the fix. You can find more details at https://github.com/instana/nodejs/releases. The layer version for eu-central-1 is now 193 (arn:aws:lambda:eu-central-1:410797082306:layer:instana-nodejs:193). Thanks for your work on the fix, and please reach out if you encounter any issues.


Re-enable Get() that takes an acceptDateTime

Begun in https://github.com/Azure/azure-sdk-for-net/pull/8209

Is this additive? If so, it can come in next week.

Yes, it is -- removing blocking release tag.

Add the third overload with ConfigurationSetting setting, DateTimeOffset acceptDateTime)


SCTP support

Hello!
First of all thanks for the work on this extension. I'm currently entering a load test phase for a Diameter application and I this tool was as a great surprise in the K6 ecossystem.
From my understanding go-diameter supports the SCTP protocol, but I couldn't find any config options for the transport-layer protocol for this extension. Is there currently any way to configure the transport-layer protocol? If not, is there any plan to add this feature?

I'm glad to hear that the extension is helpful for your testing. Thank you for your PR and contribution.


Error with PHP Strict Standards

I thought it best to move this to a new issue...
 PHP Strict Standards:  Non-static method Imagick::getversion() should not be called statically, assuming $this from incompatible context in imthumb-http.class.php on line 73

Meeting strict standard requirements becomes more of an issue as hosting providers upgrade the installed version of PHP. E_STRICT is not included in E_ALL up to PHP 5.3, but is included in E_ALL for PHP 5.4 and newer. display_errors also defaults to on, which means that imthumb doesn't work out-of-the-box for recent versions of PHP.
I've just had a situation where a shared host upgraded to PHP 5.4, causing imthumb to break across a number of my client websites.

Think all that's needed to fix this error is to change...
$imVer = Imagick::getVersion();

...to...
$im = new Imagick();
$imVer = $im->getVersion();

This should be submitted as a pull request, I know, but I'm a Github newbie and I haven't learned how yet. Will submit it properly when I have time.

no worries I had time today, that should do it (:


Removed Reincarnate & Reinacarnate and notify from failure behavior

Closes #10
This PR is the prerequisite for https://github.com/PHOENIXCONTACT/MORYX-Platform/issues/20
The failure behavior Reincarnate and Reincarnate and notify shall be removed because it will be removed from the platform.

You have commited changes to the bundle.js - this must be reverted. What about the project.json.lock? Do you have updated packages?

The update yesterday did not work locally. After retranspiling the maintenance it worked. Please check that, I will revert the changes to bundle.js & project.lock


Auto-modify apiserver configuration during virtlet setup on kubeadm clusters

The following options need to be added to apiserver config:
--feature-gates=StreamingProxyRedirects=true --feature-gates=DynamicKubeletConfig=true
This can be done by a Job residing in the same .yaml file as Virtlet DaemonSet. It should also mark the cluster as 'ready for virtlet' somehow (maybe there's a cluster-wide way to query API server settings?) and Virtlet init containers that are responsible for CRI proxy bootstrap must wait for it before starting.

Looks like outdated issue. If it's still relevant - please reopen it.


Restructure repo to cookiecutter

See https://drivendata.github.io/cookiecutter-data-science/

Done in #71


Q: Why the hard limit at the 1997 season?

From what I can see the nbastats offers data from the 1970s even...
Is there a reason to limit the possible fetch to 1997?
Reasons I can think of:

Size of DB
Load time due to the initial population of the DB

See open issue #109 for a proposal of something to overcome this by making a request when "one has time"

Lack of consistency in the data (requires much more data cleaning and handling)
Limit on request by the NBA api

I couldn't find an explanation on the code or wiki so I am asking here

Hi sorry that I missed this. 97 is the oldest season that the NBA allows to query I believe. Not much else we can do.


Support additional parameters for infinityModel()

Additional options can be provided in the object passed to
InfinityRoute's infinityModel() for use by DS.Store.find().
The perPage and startingPage properties will still be passed as
per_page and page params, respectively.
Acceptance tests use a new /category/:category route in the
dummy application.
For #6.

Note: submitted this a bit prematurely; still adding support for _loadingMore use of find(). Working on this (and hopefully a good test).

This is now ready for review.

Really really nice!  thankyou @bruce !
If you can squash this into a single commit - and add something to README to reflect this change, I'll merge and release asap

Thanks! I'll get that in tonight/tomorrow morning.

@hhff Squashed and README content added. Thanks!


updated additional features with implementation examples

… duplicate matplotlib import in demos

Codecov Report

Merging #38 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #38   +/-   ##
=======================================
  Coverage   99.48%   99.48%
=======================================
  Files           6        6
  Lines         392      392
=======================================
  Hits          390      390
  Misses          2        2

Continue to review full report at Codecov.

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


Not all videos that are being cached

I have a list of videos which is try to cache but somehow only the first few videos are being cached.
    urls.map {
        proxy.registerCacheListener(listener, it)
        uriList.add(Uri.parse(proxy.getProxyUrl(it)))
    }
    val mediaSource = createConcatenatedMediaSource(uriList)
    player.prepare(mediaSource, true, false)

This is how the proxyCache Server is being created in the Application file
HttpProxyCacheServer.Builder(this)
            .maxCacheSize(1024 * 1024 * 1024)
            .cacheDirectory(VideoCacheUtils.getVideoCacheDir(this))
            .build()

Here is how I create the media source
private fun createConcatenatedMediaSource(uriList: List<Uri>): MediaSource {
    val mediaList: ArrayList<MediaSource> = ArrayList()
    uriList.map {
        mediaList.add(createMediaSource(it))
    }
    return ConcatenatingMediaSource(*mediaList.toTypedArray())
}
private fun createMediaSource(uri: Uri): MediaSource {
    val bandwidthMeter = DefaultBandwidthMeter()
    val dataSourceFactory = DefaultDataSourceFactory(context, Util.getUserAgent(context, "exoplayer-videos"), bandwidthMeter)
    return ExtractorMediaSource.Factory(dataSourceFactory).createMediaSource(uri)
}

And here is how i create the exo player
val videoTrackSelectionFactory = AdaptiveTrackSelection.Factory()
    val trackSelector = DefaultTrackSelector(videoTrackSelectionFactory)
    player =  ExoPlayerFactory.newSimpleInstance(context,
            DefaultRenderersFactory(context),
            trackSelector,
            DefaultLoadControl())

I checked the mediaSource. All of the videos are in the list.
I tried making the cache size bigger but that didn't fix the problem.
I tried making the cache size smaller to see if fewer videos will be cached, the number didn't change. SO obviously even 512 MB is enough for the videos that are being cached. Why would 1GB not be enough for the rest of it.
How do I increase the number of videos cached?

any update?


Scope confusion with if and while

Example (⬥ is my prompt):
⬥ if (x = $true; put $x) { echo $x }
Exception: variable $x not found
Traceback:
  [tty], line 1:
    if (x = $true; put $x) { echo $x }
  [tty], line 1:
    if (x = $true; put $x) { echo $x }
⬥ put $x
▶ $true

As can be seen, $x does exist after running the if. It should be in scope within the if body, for sure?
Of course,
⬥ x= if (x = $true; put $x) { echo $x }

works as expected, and is better code as it does not pollute the local namespace. But stil, I consider this a bug.
The same thing happens with while. In fact, that is how I discovered the bug  – with a more complicated expression in place of $true, of course.

This appears to be closely related to, if not exactly the same thing as, issue #532.
This issue raises an interesting question. Should temporary assignments even be legal when there is no associated command?

It seems that this now works as intended:
~> if (var x = $true; put $x) { put $x }
▶ $true

It seems that this now works as intended

It still seems broken in that x is not scoped to the if and leaks into the enclosing scope:
0.000151 elvish> put $x
compilation error: 4-6 in [tty]: variable $x not found
compilation error: variable $x not found
[tty 2], line 1: put $x
0.000056 elvish> if (var x = $true; put $x) { put $x }
▶ $true
0.000264 elvish> put $x
▶ $true

That's not how the Go equivalent behaves. Of course Elvish isn't restricted to behaving like Go in this regard but it seems to me like it should.

This has little to do with if as such. The point is that parenthesised code runs in the surrounding scope, a fact that I utilised once in my (now obsolete) trick to optionally load os-specific modules.
The scoping rule for parenthesised code seems to be by design, not by accident (though I am not sure I've heard that stated explicitly).

Yes, only lambdas introduce new scopes.

Yes, but a parenthesized output capture expression evaluated as an if conditional runs in the context of the if and side effects, such as defining a new var, should arguably be limited to the scope of the if. If the current behavior isn't changed the documentation needs to make this behavior clearer.

You may indeed argue that if, while, and for should all introduce their own scopes. The resulting behaviour might be somewhat less surprising, but on the other hand, introducing a special scoping rule for these commands complicates the language and makes it less consistent, or so it seems to me. So I think the current behaviour is OK, with the possible exception of the loop variable of a for loop.
Documentation is a different matter, and it definitely could use some improvement. Maybe make that a separate issue, seeing as this one has been closed? Hmm, I think I'll just go ahead and open one.


remove some test to decrease coverage

should fail the pull request checks

hmmm, coveralls.io check is not there.
Is it because the maintainer does the PR?

WTF? whre is Coverage check?


Payment status "Authorized" won't get updated to "Paid" later on

If a customer pays with e.g. Klarna and the payment reaches the status "Authorized", then the status will correctly be forwarded to Shopware. After a few days though the payment status usually changes from "Authorized" to "Paid" in Mollie, but it won't be forwarded to Shopware.
I checked all of our recent orders in Mollie and in Shopware - while in Mollie they're all marked as paid, in Shopware they're still marked as authorized and never updated.

@airplanemta thx for reporting this. We will have a check and come back to you

hi there
just did a pull request to fix this issue
https://github.com/mollie/Shopware6/pull/128

will be part of the next release, planned for next week

@airplanemta mollie release with fix will be on next Monday. We've got a public holiday yesterday. I had to reschedule the release

closed, fix released with v1.4.1


Gittio support

To be able to provide a Gittio package, you have to follow this naming convention for your release:
moduleid-platform-version.zip
While you release package right now is
TiPushNotification-0.1.0.zip
So, you need to rename the package to
TiPushNotification-commonjs-0.1.0.zip
and it will be automatically discovered by Gittio.

Done, thanks

You may need to increase the version number, for correct indexing in Gittio.

@drmas still not working, we need your help @FokkeZB (y)

2015-10-29 05:15:48:5421 #3946 [NOTICE] package: TiPushNotification
2015-10-29 05:15:48:6601 #3946 [NOTICE] https://api.github.com/repos/HazemKhaled/TiPushNotification/releases/2017753
2015-10-29 05:15:48:6602 #3946 [NOTICE]
2015-10-29 05:15:48:6603 #3946 [NOTICE] no match

The issue is that the zip should be in all lowercase. I thought Titaniumifier fixed that.

Finally working, but module id changed
http://gitt.io/component/ti-push-notification
@FokkeZB Please delete the old one http://gitt.io/component/TiPushNotification
Thanks

done!

Thanks a lot


Bugfixing localization problems in several UnitTests

This is a new pull request replacing the old pull request https://github.com/microsoft/azure-pipelines-agent/pull/3473 which included two changes. Both these changes of the old pull request have been splitted up according to the suggestion by @ismayilov-ismayil (the other new pull request being https://github.com/microsoft/azure-pipelines-agent/pull/4217). This pull request contains the UnitTest localization problem fixes.
Bug fixed:

Localization problems in several UnitTests (Bug https://github.com/microsoft/azure-pipelines-agent/issues/3950)

Localization problems in several UnitTests fixed

Some UnitTests always used the point as the decimal separator in strings with numbers. However, this is different in different cultures (it's a comma in German culture for example) and the UnitTests failed on such systems. Adapted these UnitTests to either use numbers in strings with the decimal separator of the current culture or being able to handle numbers with a point as the decimal separator.
Some UnitTests checked for a correct system user name or if a specific system user name can be found. However, these system user names can be different from the English/Default name in German, French, Italian and Spanish. The checks for these user names were expanded accordingly to also check for the system user names of these other languages so that these UnitTests won't fail any more just because they run on a German, French, Italian or Spanish windows system.

/azp run

Tested with uses cases:

Created windows OS with German culture
Run tests on German culture without current changes to reproduce errors
Run tests with current tests - no error
Run tests against default OS user - no error


Refactoring: Remove ExtraVerification in the import queue

We have this ExtraVerification parameter when creating the import queue that is totally unused. It's also unused in Polkadot. Let's remove it.
If this parameter turns out to be needed later, we can always revert this PR.

@tomaka You need to fix node-template.


Need a convenient way of fading images

Take an example of how I fade in an image with AlamofireImage:
dishImageView.af_setImageWithURL(URL, imageTransition: .CrossDissolve(0.2))

and the Kingfisher way:
dishImageView.kf_setImageWithURL(URL, placeholderImage: nil, optionsInfo: nil) {
    [weak self] (image, error, cacheType, imageURL) -> () in
    self?.dishImageView.alpha = 0
    UIView.animateWithDuration(0.3) {
        self?.dishImageView.alpha = 1
    }
}

It would be useful. I will take a look at how to implement it. Maybe it would be a good idea to add it in the optionsInfo.

Added in #109 .
Use like this:
imageView.kf_setImageWithURL(URL, placeholderImage: nil, optionsInfo: [.Transition: ImageTransition.Fade(1)]

You can also find other options in ImageTransition.