firing pulse now relative in time

Closes #51, following the discussion in https://github.com/openquantumhardware/qick/issues/155, I'm moving all the timing from absolute to relative.
Now to play a pulse sequences [A, B, C] we are doing:
pulse(A, t=A.start)
pulse(B, t=B.start)
pulse(C, t=C.start)

After this PR it should become:
delay(A.start)
pulse(A)
delay(B.start - A.start)
pulse(B)
delay(B.start - C.start)
pulse(C)

this will fix a bug relative to the time sweepers and avoid the "mismatch" in the registers names that we thought existed.
In general this should not be extremely difficult, but I have some doubt that my current implementation will work for multiplexed readout. I will have to check.
Moreover, also a PR in qibolab needs to be opened to take into account this change
Checklist before merge:

[ ] Reviewers confirm new code works as expected.
[ ] Tests are passing.
[ ] Documentation is updated.

Codecov Report
Patch coverage: 87.75% and project coverage change: +0.15 :tada:

Comparison is base (b03e4c0) 72.92% compared to head (a72b2db) 73.07%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #52      +/-   ##
==========================================
+ Coverage   72.92%   73.07%   +0.15%
==========================================
  Files          10       10
  Lines         517      520       +3
==========================================
+ Hits          377      380       +3
  Misses        140      140

Flag
Coverage Δ

unittests
73.07% <87.75%> (+0.15%)
:arrow_up:

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

Impacted Files
Coverage Δ

src/qibosoq/programs/sweepers.py
93.33% <33.33%> (-1.27%)
:arrow_down:

src/qibosoq/programs/base.py
79.67% <90.69%> (+0.76%)
:arrow_up:

src/qibosoq/components.py
100.00% <100.00%> (ø)

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

Thanks @AleCandido!
I guess that sooner or later I will also have to fix test and coverage: this last error has passed the tests without problems...
I will merge this as soon I have tested the mux part on hardware

I guess that sooner or later I will also have to fix test and coverage: this last error has passed the tests without problems...

However, this error could simply be avoided with a type check. Next week, I will try to implement a workflow to run mypy, and we could use Qibosoq as an alpha tester.

This is a Mypy preview from the current apidoc branch:
❯ poetry run mypy src
src/qibosoq/components/pulses.py:46: error: Incompatible types in assignment (expression has type "None", variable has type "float")  [assignment]
src/qibosoq/components/pulses.py:56: error: Incompatible types in assignment (expression has type "None", variable has type "float")  [assignment]
src/qibosoq/components/pulses.py:58: error: Incompatible types in assignment (expression has type "None", variable has type "float")  [assignment]
src/qibosoq/components/base.py:36: error: Incompatible types in assignment (expression has type "None", variable has type "int")  [assignment]
src/qibosoq/components/base.py:52: error: Overloaded function signatures 1 and 2 overlap with incompatible return types  [misc]
src/qibosoq/components/base.py:72: error: Incompatible types in assignment (expression has type "None", variable has type "int")  [assignment]
src/qibosoq/components/base.py:74: error: Incompatible types in assignment (expression has type "None", variable has type "list[Parameter]")  [assignment]
src/qibosoq/components/base.py:76: error: Incompatible types in assignment (expression has type "None", variable has type "list[int | float]")  [assignment]
src/qibosoq/components/base.py:78: error: Incompatible types in assignment (expression has type "None", variable has type "list[int | float]")  [assignment]
src/qibosoq/components/base.py:80: error: Incompatible types in assignment (expression has type "None", variable has type "list[int]")  [assignment]
src/qibosoq/programs/base.py:10: error: Skipping analyzing "qick": module is installed, but missing library stubs or py.typed marker  [import]
src/qibosoq/programs/base.py:11: error: Skipping analyzing "qick.qick_asm": module is installed, but missing library stubs or py.typed marker  [import]
src/qibosoq/programs/base.py:11: note: See https://mypy.readthedocs.io/en/stable/running_mypy.html#missing-imports
src/qibosoq/programs/base.py:53: error: Need type annotation for "registered_waveform" (hint: "registered_waveform: List[<type>] = ...")  [var-annotated]
src/qibosoq/programs/base.py:121: error: "Pulse" has no attribute "rel_sigma"  [attr-defined]
src/qibosoq/programs/base.py:133: error: "Pulse" has no attribute "beta"  [attr-defined]
src/qibosoq/programs/base.py:142: error: "Pulse" has no attribute "beta"  [attr-defined]
src/qibosoq/programs/base.py:213: error: Need type annotation for "last_pulse_registered" (hint: "last_pulse_registered: Dict[<type>, <type>] = ...")  [var-annotated]
src/qibosoq/programs/base.py:214: error: Need type annotation for "muxed_pulses_executed" (hint: "muxed_pulses_executed: List[<type>] = ...")  [var-annotated]
src/qibosoq/programs/base.py:215: error: Need type annotation for "muxed_ro_executed_indexes" (hint: "muxed_ro_executed_indexes: List[<type>] = ...")  [var-annotated]
src/qibosoq/programs/base.py:268: error: Incompatible return value type (got "tuple[list[<nothing>], list[<nothing>]]", expected "tuple[ndarray[Any, dtype[floating[_64Bit]]], ndarray[Any, dtype[floating[_64Bit]]]]")  [return-value]
src/qibosoq/programs/base.py:289: error: Incompatible types in assignment (expression has type "ndarray[Any, dtype[Any]]", variable has type "list[int]")  [assignment]
src/qibosoq/programs/base.py:296: error: Incompatible types in assignment (expression has type "tuple[Any, int]", variable has type "tuple[Any, Any, int]")  [assignment]
src/qibosoq/programs/base.py:341: error: "Pulse" has no attribute "shape"  [attr-defined]
src/qibosoq/programs/base.py:352: error: Need type annotation for "mux_list" (hint: "mux_list: List[<type>] = ...")  [var-annotated]
src/qibosoq/programs/base.py:361: error: Incompatible types in assignment (expression has type "float", variable has type "int")  [assignment]
src/qibosoq/programs/flux.py:7: error: Skipping analyzing "qick": module is installed, but missing library stubs or py.typed marker  [import]
src/qibosoq/programs/flux.py:22: error: Need type annotation for "bias_sweep_registers" (hint: "bias_sweep_registers: Dict[<type>, <type>] = ...")  [var-annotated]
src/qibosoq/programs/sweepers.py:7: error: Skipping analyzing "qick": module is installed, but missing library stubs or py.typed marker  [import]
src/qibosoq/programs/sweepers.py:8: error: Skipping analyzing "qick.averager_program": module is installed, but missing library stubs or py.typed marker  [import]
src/qibosoq/programs/sweepers.py:25: error: No overload variant of "reversed" matches argument type "Iterable[Sweeper]"  [call-overload]
src/qibosoq/programs/sweepers.py:25: note: Possible overload variants:
src/qibosoq/programs/sweepers.py:25: note:     def [_T] reversed(self, Reversible[_T], /) -> reversed[_T]
src/qibosoq/programs/sweepers.py:25: note:     def [_T] reversed(self, SupportsLenAndGetItem[_T], /) -> reversed[_T]
src/qibosoq/programs/sweepers.py:64: error: Incompatible types in assignment (expression has type "ndarray[Any, dtype[Any]]", variable has type "list[int | float]")  [assignment]
src/qibosoq/programs/sweepers.py:65: error: Incompatible types in assignment (expression has type "ndarray[Any, dtype[Any]]", variable has type "list[int | float]")  [assignment]
src/qibosoq/programs/sweepers.py:75: error: "list[int | float]" has no attribute "astype"  [attr-defined]
src/qibosoq/programs/sweepers.py:76: error: "list[int | float]" has no attribute "astype"  [attr-defined]
src/qibosoq/programs/sweepers.py:96: error: "list[int | float]" has no attribute "astype"  [attr-defined]
src/qibosoq/programs/sweepers.py:97: error: "list[int | float]" has no attribute "astype"  [attr-defined]
src/qibosoq/programs/pulse_sequence.py:5: error: Skipping analyzing "qick": module is installed, but missing library stubs or py.typed marker  [import]
src/qibosoq/rfsoc_server.py:16: error: Skipping analyzing "qick": module is installed, but missing library stubs or py.typed marker  [import]
src/qibosoq/rfsoc_server.py:53: error: Incompatible types in assignment (expression has type "type[ExecuteSweeps]", variable has type "type[FluxProgram]")  [assignment]
src/qibosoq/rfsoc_server.py:54: error: Incompatible types in assignment (expression has type "tuple[Sweeper, ...]", variable has type "tuple[]")  [assignment]
src/qibosoq/rfsoc_server.py:67: error: "Handler" has no attribute "doRollover"  [attr-defined]
src/qibosoq/rfsoc_server.py:87: error: Incompatible types in assignment (expression has type "ndarray[Any, dtype[floating[_64Bit]]]", variable has type "list[list[Any]]")  [assignment]
src/qibosoq/rfsoc_server.py:95: error: "list[list[Any]]" has no attribute "tolist"  [attr-defined]
src/qibosoq/rfsoc_server.py:96: error: "list[list[Any]]" has no attribute "tolist"  [attr-defined]
Found 44 errors in 7 files (checked 13 source files)

Amazing... I suppose/hope these are just outdated type hints but for sure they have to be fixed

Speaking of worflows, I also think that there is some problem with codecov... It doesn't appear as a check in github and I am not sure if it even runs for every commit

Speaking of worflows, I also think that there is some problem with codecov... It doesn't appear as a check in github and I am not sure if it even runs for every commit

There is no Codecov configs in this repo (the .github/codecov.yml file I added in Qibolab), so everything is determined by the coverage upload (following default configurations).
This is actually happening:
https://github.com/qiboteam/qibosoq/actions/runs/5435461153/jobs/9884584791?pr=52#step:13:44
and the comment is also present:
https://github.com/qiboteam/qibosoq/pull/52#issuecomment-1614653481
So, true that the check has disappeared, but I have the feeling that is not up to us (maybe the App configuration in the qiboteam organization? maybe Codecov itself?)

Thanks, this should work now (I have updated settings).

Thanks, this should work now (I have updated settings).

Yes, now it's working! Thanks @scarrazza

Hardware tested! And now also delay sweepers work fine


wrong icons/logos url

Environment
No response
Reproduction
No response
Describe the bug
on the login page, the logo of each provider is not displayed.

Additional context
it just seems the URL for each image is not valid anymore
Logs
No response

Hey @Jericho1060 👋
Thanks for the report - yes, this is a very unfortunate problem that comes due to a repo-reorganization by next-auth! This is why the icons cannot be loaded anylonger.
It will be fixed by our upcoming switch to auth.js:  #117
I've added your issue to that issue and will close this one so that we have all tracking in one place. Checkout that issue for updated on this issue 🐑

No problem, was just reporting it.
Anyway, i'm using a custom page, with my own icons actually.
Just seen it while testing something for a new project.
Thank you for your answer.

yeah - and it's awesome that you did ❤

Hey @Jericho1060 👋
Small update: We're actually going to be able to fix this pre-auth.js bump as @balazsorban44 provided a release for the "old" next-auth that fixes this.
So we're jumping to 4.18.8 now and that will fix the icons issue. Next we do the jump to auth.js (:

Hey @BracketJohn
Thank you for the feedback.

Sure! Try out 0.4.0-alpha.3, icons are working again 🎊


Deprecate prefixed EME support

Prefixed EME has been deprecated for long time. We should deprecate prefixed EME support to clean things up a bit.

Resolved in v3.0.0 release


Fix Superalloy Plating's Vanilla Recipe Being Overridden

Because there wasn't an id_suffix, this recipe was overriding the vanilla recipe for welding a superalloy plating together out of superalloy sheets.
And yes, I realize this version of the mod hasn't gotten updated in a few months since the author is in the military. It'll be fine to wait until they get back.

Currently, I am unable to use a computer, but I can still do simple fixes using my phone. If I'm going on vacation anytime soon, I'll make sure to update Project: Pack Rat as well as what's in the Rogall modpack.


Fix/change code tag to blockquote tags for backend

I have gone through the Quality Assurance and Testing with Chai section and performed the following tasks:

Reformatted <code> blocks with <blockquote>.
Moved applicable instructions from Description sections to the Instructions section.
Made minor grammar and punctuation changes for clarity and legibility.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Closes #35413

@moT01 and @RandellDawson Please have a look and let me know If any changes are required.
Note: Can we merge both the commits? Since I made a few changes in the second commit which I had left in the first commit accidentally. Or I need to provide fresh commit containing all changes altogether in a single commit.

@Nitin96Bisht Two commits are fine.

@RandellDawson I checked my commits, There is something wrong with these commits. I had added <code> blocks in required places. I will close it and create new PR for Quality Assurance and Testing with Chai soon.
Kindly ignore this PR.


Tweets from people you follow

Hi-  I installed the module, it seems to only show what I tweet, but not the tweets of those whom I follow on my Twitter account.  Any ideas how I can display and update the display with the tweets of people I follow?
Thanks.

Hi, i don't know, if it's still important for you, but you just have to change the "with: 'user'," in the node_helper.js to "with: 'followings".

In addition to herrschrat's suggestion, please consult the Twitter API on what type of API access tokens you'll need to access different features. They compartmentalize pretty strictly.


Implementing a way of retrieving the maxlength value

Proposed changes
Adding a simple means of retrieving the maxlength attribute value of a given webelement
Checklist

[ ] Checkstyle and unit tests pass locally with my changes by running gradle check chrome htmlunit command
[X] I have added tests that prove my fix is effective or that my feature works
[X] I have added necessary documentation (if appropriate)

I am not sure that we should add it.

There is common method attr(String attributeName); and it is enough from my point of view.
@symonk why you can't use $().attr("maxlength")?

Max length for inputs can be stored in any dom elements attribut e.g. for Angular it is ngMaxlength. So users will be confused when they call $().maxLength() and it won't work correctly.

@symonk Agree with @BorisOsipov about using named attribute value instead of separate method.
In my opinion it is functionality duplication.

@BorisOsipov @rosolko after more thought, yes I agree with you both, especially when modern frameworks such as angular are using other attribute names, could cause end user confusion and unnecessary issue(s).  Thanks.

SO. Let's close out this PR for now.


[local_auth] Flutter 1.25.0-8.1.pre (beta) -- Because local_auth >=0.6.0+1 depends on intl >=0.15.1 <0.17.0 and my_app depends on intl ^0.17.0-nullsafety.2, local_auth >=0.6.0+1 is forbidden.

Steps to Reproduce

Upgrade to latest beta branch version: 1.25.0-8.1.pre
Add intl to your project: intl: ^0.16.1. You will get this error:

Because my_app depends on flutter_localizations any from sdk which depends on intl 0.17.0-nullsafety.2, intl 0.17.0-nullsafety.2 is required.

Add the latest release of local_auth to your project: local_auth: ^0.6.3+4
Update your intl to that version: intl: 0.17.0-nullsafety.2.
Now you will get this error:
Because local_auth >=0.6.0+1 depends on intl >=0.15.1 <0.17.0 and my_app depends on intl ^0.17.0-nullsafety.2, local_auth >=0.6.0+1 is forbidden.

Expected results:
Should be able to use local_auth on the latest beta channel release.
Actual results:
Unable to get packages on the latest beta channel release.

Logs

Hi @acoutts
Please see Conflict resolution section to see how to solve this version conflict.
Closing as this is not an issue with flutter itself. If you disagree please comment and I will reopen it.
Thank you

I think there is an issue because flutter 1.25.0-8.1.pre now uses the nullsafety pre-release of intl. There's no pub versions for flutter_localizations to change to, it has to be sdk. Now that the sdk has bumped its dependency on intl, packages using intl need to bump theirs too.
local_auth needs to use the nullsafety pre-release as well or else nobody can update beyond 1.24.0-10.2.pre.

@pedromassangocode

Hi @acoutts
I cannot reproduce the step #2 you mentioned, as you can see using Flutter beta and the two packages does not throws any error.

Can you please provide your pubspec.yaml?
Thank you

@pedromassango please include flutter_localizations too. This will reproduce the issue:
dependencies:
  flutter:
    sdk: flutter
  intl: ^0.16.1
  local_auth: ^0.6.3+3
  flutter_localizations:
    sdk: flutter

The local_auth package needs updated to use intl 0.17.0-nullsafety.2 like the sdk uses with flutter_localizations.

I was able to reproduce the issue.
Logs
Running "flutter pub get" in flutter_example...

Because local_auth >=0.6.0+1 depends on intl >=0.15.1 <0.17.0 and flutter_example depends on intl ^0.17.0-nullsafety.2, local_auth >=0.6.0+1 is forbidden.
So, because flutter_example depends on local_auth ^0.6.3+4, version solving failed.
pub get failed (1; So, because flutter_example depends on local_auth ^0.6.3+4, version solving failed.)
Process finished with exit code 1


python312Packages.aioaseko: 0.2.0 -> 1.0.0

Diff: https://github.com/milanmeu/aioaseko/compare/refs/tags/v0.2.0...v1.0.0
Changelog: https://github.com/milanmeu/aioaseko/releases/tag/v1.0.0
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
24.11 Release Notes (or backporting 23.11 and 24.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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

1 package failed to build:

home-assistant-component-tests.aseko_pool_live

4 packages built:

python311Packages.aioaseko
python311Packages.aioaseko.dist
python312Packages.aioaseko
python312Packages.aioaseko.dist


Synthesis failed for java-mediatranslation

Hello! Autosynth couldn't regenerate java-mediatranslation. :broken_heart:
Here's the output from running synth.py:
translation/v1beta1/StreamingTranslateSpeechRequestOrBuilder.java.
2021-01-11 02:30:34,536 synthtool [INFO] > Replaced '// Generated by the protocol buffer compiler.  DO NOT EDIT!' in /tmpfs/tmp/tmp1v9ekw_p/google-cloud-mediatranslation-v1beta1-java/proto-google-cloud-mediatranslation-v1beta1-java/src/main/java/com/google/cloud/mediatranslation/v1beta1/StreamingTranslateSpeechResultOrBuilder.java.
2021-01-11 02:30:34,536 synthtool [INFO] > Replaced '// Generated by the protocol buffer compiler.  DO NOT EDIT!' in /tmpfs/tmp/tmp1v9ekw_p/google-cloud-mediatranslation-v1beta1-java/proto-google-cloud-mediatranslation-v1beta1-java/src/main/java/com/google/cloud/mediatranslation/v1beta1/TranslateSpeechConfig.java.
2021-01-11 02:30:34,537 synthtool [INFO] > Replaced '// Generated by the protocol buffer compiler.  DO NOT EDIT!' in /tmpfs/tmp/tmp1v9ekw_p/google-cloud-mediatranslation-v1beta1-java/proto-google-cloud-mediatranslation-v1beta1-java/src/main/java/com/google/cloud/mediatranslation/v1beta1/StreamingTranslateSpeechResponseOrBuilder.java.
2021-01-11 02:30:34,541 synthtool [WARNING] > No replacements made in [PosixPath('/tmpfs/tmp/tmp1v9ekw_p/google-cloud-mediatranslation-v1beta1-java/proto-google-cloud-mediatranslation-v1beta1-java/src/**/*Name.java'), PosixPath('/tmpfs/tmp/tmp1v9ekw_p/google-cloud-mediatranslation-v1beta1-java/proto-google-cloud-mediatranslation-v1beta1-java/src/**/*Names.java')] for pattern /\*
 \* Copyright \d{4} Google LLC
 \*
 \* Licensed under the Apache License, Version 2.0 \(the "License"\); you may not use this file except
 \* in compliance with the License. You may obtain a copy of the License at
 \*
 \* http://www.apache.org/licenses/LICENSE-2.0
 \*
 \* Unless required by applicable law or agreed to in writing, software distributed under the License
 \* is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express
 \* or implied. See the License for the specific language governing permissions and limitations under
 \* the License.
 \*/
, maybe replacement is no longer needed?
2021-01-11 02:30:34,542 synthtool [INFO] > Replaced '^package (.*);' in /tmpfs/tmp/tmp1v9ekw_p/google-cloud-mediatranslation-v1beta1-java/grpc-google-cloud-mediatranslation-v1beta1-java/src/main/java/com/google/cloud/mediatranslation/v1beta1/SpeechTranslationServiceGrpc.java.
2021-01-11 02:30:34,572 synthtool [INFO] > Running java formatter on 11 files
2021-01-11 02:30:36,563 synthtool [INFO] > Running java formatter on 1 files
2021-01-11 02:30:38,265 synthtool [INFO] > Running java formatter on 11 files
2021-01-11 02:30:41,493 synthtool [DEBUG] > Using precloned repo /home/kbuilder/.cache/synthtool/synthtool
.github/CODEOWNERS
.github/ISSUE_TEMPLATE/bug_report.md
.github/ISSUE_TEMPLATE/feature_request.md
.github/ISSUE_TEMPLATE/support_request.md
.github/PULL_REQUEST_TEMPLATE.md
.github/blunderbuss.yml
.github/generated-files-bot.yml
.github/readme/synth.py
.github/release-please.yml
.github/snippet-bot.yml
.github/trusted-contribution.yml
.github/workflows/approve-readme.yaml
.github/workflows/auto-release.yaml
.github/workflows/ci.yaml
.github/workflows/samples.yaml
.kokoro/build.bat
.kokoro/build.sh
.kokoro/coerce_logs.sh
.kokoro/common.cfg
.kokoro/common.sh
.kokoro/continuous/common.cfg
.kokoro/continuous/java8.cfg
.kokoro/continuous/readme.cfg
.kokoro/dependencies.sh
.kokoro/linkage-monitor.sh
.kokoro/nightly/common.cfg
.kokoro/nightly/integration.cfg
.kokoro/nightly/java11.cfg
.kokoro/nightly/java7.cfg
.kokoro/nightly/java8-osx.cfg
.kokoro/nightly/java8-win.cfg
.kokoro/nightly/java8.cfg
.kokoro/nightly/samples.cfg
.kokoro/populate-secrets.sh
.kokoro/presubmit/clirr.cfg
.kokoro/presubmit/common.cfg
.kokoro/presubmit/dependencies.cfg
.kokoro/presubmit/integration.cfg
.kokoro/presubmit/java11.cfg
.kokoro/presubmit/java7.cfg
.kokoro/presubmit/java8-osx.cfg
.kokoro/presubmit/java8-win.cfg
.kokoro/presubmit/java8.cfg
.kokoro/presubmit/linkage-monitor.cfg
.kokoro/presubmit/lint.cfg
.kokoro/presubmit/samples.cfg
.kokoro/readme.sh
.kokoro/release/bump_snapshot.cfg
.kokoro/release/common.cfg
.kokoro/release/common.sh
.kokoro/release/drop.cfg
.kokoro/release/drop.sh
.kokoro/release/promote.cfg
.kokoro/release/promote.sh
.kokoro/release/publish_javadoc.cfg
.kokoro/release/publish_javadoc.sh
.kokoro/release/snapshot.cfg
.kokoro/release/snapshot.sh
.kokoro/release/stage.cfg
.kokoro/release/stage.sh
.kokoro/trampoline.sh
CODE_OF_CONDUCT.md
CONTRIBUTING.md
LICENSE
README.md
codecov.yaml
java.header
license-checks.xml
renovate.json
samples/install-without-bom/pom.xml
samples/pom.xml
samples/snapshot/pom.xml
samples/snippets/pom.xml
2021-01-11 02:30:41,665 synthtool [DEBUG] > existing pom file found (samples/pom.xml) - keeping the existing
2021-01-11 02:30:41,666 synthtool [DEBUG] > existing pom file found (samples/snippets/pom.xml) - keeping the existing
2021-01-11 02:30:41,667 synthtool [DEBUG] > existing pom file found (samples/snapshot/pom.xml) - keeping the existing
2021-01-11 02:30:41,667 synthtool [DEBUG] > existing pom file found (samples/install-without-bom/pom.xml) - keeping the existing
2021-01-11 02:30:44,711 synthtool [DEBUG] > Wrote metadata to synth.metadata.
2021-01-11 02:30:44,766 autosynth [INFO] > Changed files:
2021-01-11 02:30:44,766 autosynth [INFO] > M synth.metadata
2021-01-11 02:30:44,767 autosynth [DEBUG] > Running: git log fb53b6fb373b7c3edf4e55f3e8036bc6d73fa483 -1 --no-decorate --pretty=%s
2021-01-11 02:30:44,770 autosynth [DEBUG] > Running: git log fb53b6fb373b7c3edf4e55f3e8036bc6d73fa483 -1 --no-decorate --pretty=%b%n%nSource-Author: %an <%ae>%nSource-Date: %ad
2021-01-11 02:30:44,774 autosynth [DEBUG] > Running: git add -A
2021-01-11 02:30:44,779 autosynth [DEBUG] > Running: git status --porcelain
2021-01-11 02:30:44,785 autosynth [DEBUG] > Running: git commit -m chore(python): skip docfx in main presubmit

* chore(python): skip docfx in main presubmit

* fix: properly template the repo name

Source-Author: Bu Sun Kim<EMAIL_ADDRESS>Source-Date: Fri Jan 8 10:32:13 2021 -0700
Source-Repo: googleapis/synthtool
Source-Sha: fb53b6fb373b7c3edf4e55f3e8036bc6d73fa483
Source-Link: https://github.com/googleapis/synthtool/commit/fb53b6fb373b7c3edf4e55f3e8036bc6d73fa483
[autosynth-69 564de9a] chore(python): skip docfx in main presubmit
 1 file changed, 4 insertions(+), 4 deletions(-)
2021-01-11 02:30:44,791 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at 564de9a chore(python): skip docfx in main presubmit
2021-01-11 02:30:44,796 autosynth [DEBUG] > Running: git checkout autosynth
Switched to branch 'autosynth'
2021-01-11 02:30:44,801 autosynth [DEBUG] > Running: git diff HEAD..autosynth-69 -- . :(exclude)synth.metadata
2021-01-11 02:30:44,805 autosynth [DEBUG] > Running: git diff HEAD..autosynth-69 -- synth.metadata
2021-01-11 02:30:44,809 autosynth [DEBUG] > Running: git diff HEAD..autosynth-70 -- . :(exclude)synth.metadata
2021-01-11 02:30:44,814 autosynth [DEBUG] > Running: git diff HEAD autosynth-70
2021-01-11 02:30:44,818 autosynth [DEBUG] > Running: git apply /tmpfs/tmp/tmpp4fmtoqj/autosynth-70.patch
2021-01-11 02:30:44,822 autosynth [DEBUG] > Running: git add -A
2021-01-11 02:30:44,827 autosynth [DEBUG] > Running: git status --porcelain
2021-01-11 02:30:44,833 autosynth [DEBUG] > Running: git commit -m chore: update gapic-generator-java to 0.0.18

Committer: @miraleung
PiperOrigin-RevId: 350949863

Source-Author: Google APIs<EMAIL_ADDRESS>Source-Date: Sat Jan 9 14:01:49 2021 -0800
Source-Repo: googleapis/googleapis
Source-Sha: 91e206bcfeaf8948ea03fe3cb1b7616108496cd3
Source-Link: https://github.com/googleapis/googleapis/commit/91e206bcfeaf8948ea03fe3cb1b7616108496cd3
[autosynth 4251392] chore: update gapic-generator-java to 0.0.18
 6 files changed, 14 insertions(+), 7 deletions(-)
2021-01-11 02:30:44,842 autosynth [DEBUG] > Running: git log -1 --no-decorate --format=%B
2021-01-11 02:30:44,846 autosynth [DEBUG] > Running: git push --force origin autosynth
remote:
remote: Create a pull request for 'autosynth' on GitHub by visiting:
remote:      https://github.com/googleapis/java-mediatranslation/pull/new/autosynth
remote:
To https://github.com/googleapis/java-mediatranslation.git
 * [new branch]      autosynth -> autosynth
2021-01-11 02:30:48,629 autosynth [DEBUG] > Running: git log -1 --pretty=%b
2021-01-11 02:30:51,345 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 334, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 92, in synthesize_loop
    synthesize_inner_loop(fork, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 137, in synthesize_inner_loop
    synthesizer, len(toolbox.versions) - 1
  File "/tmpfs/src/github/synthtool/autosynth/synth_toolbox.py", line 259, in synthesize_version_in_new_branch
    synthesizer.synthesize(synth_log_path, self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:

Autosynth passed, closing! :green_heart:


Import shims directly in index.tsx to make starter consistent with others

To make this starter consistent with the others. Remove shims from webpack config and explicitly import in index.tsx before React
Tested in Chrome and IE.
Connected to rangle/rangle-starter#100

:shipit:


Cleanup md files

opensearch-security pull request intake form
Please provide as much details as possible to get feedback/acceptance on your PR quickly

Category: (Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation)
Maintenance

Github Issue # or road-map entry, if available:

Description of changes:

Why these changes are required?

What is the old behavior before changes and new behavior after changes? (Please add any example/logs/screen-shot if available)

Testing done: (Please provide details of testing done: Unit testing, integration testing and manual testing)

TO-DOs, if any: (Please describe pending items and provide Github issues# for each of them)

Is it backport from main branch? (If yes, please add backport PR # and commits #)

By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #1298 (098aa8b) into main (4abbafc) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main    #1298   +/-   ##
=========================================
  Coverage     64.73%   64.73%
- Complexity     3194     3195    +1
=========================================
  Files           247      247
  Lines         17230    17230
  Branches       3045     3045
=========================================
  Hits          11153    11153
  Misses         4528     4528
  Partials       1549     1549

Impacted Files
Coverage Δ

...a/org/opensearch/security/tools/SecurityAdmin.java
47.39% <0.00%> (-0.14%)
:arrow_down:

.../dlic/auth/ldap2/LDAPConnectionFactoryFactory.java
58.01% <0.00%> (+0.76%)
:arrow_up:

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 4abbafc...098aa8b. Read the comment docs.


Add instructions for migration to nav animation docs

Add instructions for how users can migrate from the jetpack Navigation
Compose APIs to Navigation Accompanist to make it clear to developers.
Also added a link to the Navigation Accompanist blog post.

Merged as part of #664


Error when inference

Hello! Thanks for the amazing work!
I'm meeting something wrong when inference:
FileNotFoundError: [Errno 2] No such file or directory: './preprocessed_data/VCTK/spker_embed/p317-spker_embed.npy'

What am I missing?
Thanks!

Hi @godspirit00 , thanks for your attention. It is because you don't have speaker embeddings. You need to get speaker embeddings beforehand(please check preprocess.yaml and preprocess.py). The other way is to modify the current synthesize.py to extract speaker embedding using DeepSpeaker at inference time.

Thanks for the reply! I will have a try.
Thanks again!


E2E: Heatmap tests

Tasks
No response
Use case
No response
Related Pull request
No response

please write at least in tasks what your intended scope is so that I can give feedback. E.g. what kind of tests.

I havent planned anything so far, waiting for this feature to be on dev first.


[WB-8934] Fix issue calling login() before PL logger with service

Fixes WB-8934
Description
When calling wandb.login() before initializing the new PL wandblogger we do not properly activate wandb service.
A quick (and temporary until we make service default) fix is:

on wandb.login(), mark the setup object as not having a manager.
If the user calls wandb.setup() or wandb.init(), then the manager will get setup.

Note 1: this code should be temporary as there are some benefits to having a manager setup for login in the future when service is default.. it should be easy to remove code related to _no_manager
Note 2: This code is a bit fragile.. wandb.setup() users in wandb_login will need to always use the internal version with no_manager flag.
Note 3:  this means that the following code wont work with PL now:
wandb.login()
wandb.setup()
wandb_logger = WandbLogger()
...

I think this is ok as we havent really talked much about setup() yet.   It is necessary that setup always initializes the manager.
TODO:

[ ] Add tests?
[ ] Add more comments about this being temporary until wandb service is default?
[ ] Clean up message about env changing (in wandb_init)

Testing
How was this PR tested?
Checklist

Name PR "[WB-NNNN][WB-MMMM] Add support for..." similar to entries in CHANGELOG.md
Include reference to internal ticket "Fixes WB-NNNN" (and github issue "Fixes #NNNN" if applicable)

Marking draft until the TODOs are taken care of.

This is not needed now that service is on by default


The wonderful world of email templates

Particularly for @chealsye and @JosephMcArthur whilst progressing through the email templates functionality today, I have some overarching questions for us to consider, not about one specific template or one specific functionality, so I will put them all here in one issue, so we can quickly get answers.
I may add more questions as comments as I proceed.

is it necessary to email a user when they just created a request, if the request has all the info we need to action it? If we do need some missing info we certainly will email them, but if we don't, then it seems unnecessary - because they will already know they just created it, they will be given the link, and have it opened for them too. So I think perhaps we should just email if there is missing info. That way a user knows if they get those emails in their inbox that there is action to take, and that they are not just notifications, so they could use them as reminders of ones they need to update later, if for some reason they do not immediately have time.

when support is added to a request, should we email the request creator and/or the contact author every time? That could get a bit extreme if any requests get very popular. Unfortunately it is also hard to be able to just send an email say every 10 requests, or every day/week with an update of how many new ones there are, because we cannot know what the count was the last time an email was sent. Adding that kind of tracking would take a long time. What we can do, as an alternative though, is to know that a request has changed in SOME way since last day/week (however long we want to wait before sending an update), and if there has been a change we can say "this request has had more support since last X". Is that OK? I think it is the best option, rather than potentially bombarding people.

When informing every supporter that a request is successful, can we send a generic email to them all, sent in bcc? Otherwise we risk (if we are very successful) sending thousands of individual emails to each supporter, which could quickly swamp our mail handler. We can send 10000 a month for free anyway, and can pay for more, but I would rather code it more efficiently in the first place if this is acceptable.

I am making templates based on what the system currently sends, and on a possibly old copy of what were the email drafts from a google doc at some point in the past, not sure when. Some changes may be necessary due to fitting things into how the functional flow goes, but assuming I make a bunch of templates and attach them to functionality, are you both happy that some tweaks will need to be made to the content, and some emails may merge/disappear? Once I have the code at a ready state, you could go through the templates I create and see how I used the variables, and can change the content as you think is necessary. If a need seems to come up for an email we don't yet have, we can discuss how to fit that into the functionality. (In future, once we have the fundamentals of the system in place, it should be quite easy to do this when we think of new email needs.)

This makes sense for now.
Makes sense.
Generic email is a-okay
Great.

example.txt and author_request.txt both now in the emails folder of oab_static, describing principles discussed above. Specific questions on what emails should exist and when they should be triggered will now be driven by the issues that are about the particular emails in question.


plot_file in diagnostic_provenance.yml cannot be a list

More than one plot file could be produced from the same diagnostic file, so it makes sense for 'plot_file' to be a list but currently this fails in esmvaltool/_provenance.py

After discussion with @hb326 on missing provenance info in the plots produced by some metrics (as decided for Magic, provenance is attached only to the first plot produced from a datafile), I return to discuss further this issue.
I see the point of @bouweandela that one day this could lead to an expansion and rethinking of the plotting/provenance system, but at the moment there are some magic-produced metrics which cannot attach provenance to all plots and this seems to be a problem in some cases.
The 5 lines of code which I mention at the beginning would allow to extend diagnostics which currently cannot attach provenance to plots to do so, by allowing the idea that in some case we can have 1 datafile --> multiple plots. This could then be reverted later if a better solution is developed.
Should I proceed, code and test it and make it into a PR ?

I have a good example for a case where allowing for multiple plots to be associated with the same data file is needed. The ensclus diagnostics performs a cluster analysis, creates a series of output files and then it creates a plot with multiple panels, one for each member in a large ensemble. The user can select (this is still in a development branch but a PR will follow soon) the maximum number of panels allowed in one page/plot. If the ensemble is really large and the maximum number of panels is exceeded, a second figure is created with the remaining panels. It would not make sense to split the datafile, this is really a case where two or more plots have to be produced from the same datafile. Allowing for plot_file to be a list would allow to attach provenance to all of the produced figures.

I just realised that actually I can use (or abuse?) the current interface in its current form to record provenance for both scenarios:

multiple plots being produced from the same diagnostic data file (*.nc)
multiple diagnostic *nc files are needed to create the same plot

An example for when case 1) is necessary is discussed above for ensclus (the same plot being splittend into multiple figures/files) and zmnam (multiple pressure levels from the same 3d output file are plotted). Case 2) would be if I make (like in the miles blocking diagnostic) a plot containing three panels with blocking diagnostics for a model, a reference and their difference (yes, I  understood that in this case it would be better to create a special separate file ...)
Now, if I simply add separate entries in diagnostic_provenance.yml also for the plot files, indicating the netcdf files used to make them as ancestors, the provenance info will be copied correctly from those files and correct provenance will be written to the plots. So for example in python what I do is to call  provenance_logger.log() also for the *png output files, with a provenance record which indicates the netcdf file used to make it as ancestors.  This seems to work nicely and provenance is correctly copied from the ancestor files into the exif of the plots.
To see an example, see this version of the ensclus diagnostic (in a branch with several improvements which I am preparing): https://github.com/ESMValGroup/ESMValTool/commit/3d25d7015e82acbf12b07bb7bb223a22c5aab4f8
Now, @bouweandela, what do you think, can this be done or is it a total misuse of the interface?
A secondary effect of this approach is that an xml and a svg file are also created for each figure (in addition to the exif info)

I think this is really something that should be discussed with the wider esmvaltool development team the next time we meet at DLR, https://github.com/ESMValGroup/ESMValTool/issues/801#issuecomment-459297757. I'm not sure when that will be exactly, possibly in May.
In the mean time, I think it's fine if you use the interface as you see fit. Provenance logging is a very new feature, so changes can be expected in the coming year as we gain experience with it, and we will have to adjust the existing diagnostics to those changes.

I kept experimenting with provenance for the figure .... Actually, @bouweandela  is it just my impression or provenance for figures through the 'plot_file' attribute is implemented only for png files and does not work e.g. for eps files ?

Yes


remove from parent controller

we add this controller as a child. I think we need to remove this from parent when we close or remove view

Thanks @lazarte! I am hoping that this solves https://github.com/stakes/JSSAlertView/issues/18 - I also added another master/detail example project to the repo to test against.


Electron 4 support?

Any chance we can get electron 4 (electron-v69) support?

I agree, now it doesn't work with actual Electron/Node.js versions at all.
What should we do, downgrade Electron or there are any better ways to get it to work?

Hi there, I did try to make prebuilt binaries for electron 4 but I hit some bugs.
I'll try to find some time to re-test it.
However the build is the same as describe in the docs

Nope, it's clearly out of my knowledge.
I Did some tests on travis : just adding the new target (electron 4.0.5, abi 69) got me an error :
[ 87%] Building CXX object CMakeFiles/iohook.dir/src/iohook.cc.o
In file included from /home/travis/build/wilix-team/iohook/src/iohook.h:3:0,
                 from /home/travis/build/wilix-team/iohook/src/iohook.cc:1:
/home/travis/build/wilix-team/iohook/node_modules/nan/nan.h:24:26: fatal error: node_version.h: No such file or directory
 #include <node_version.h>

Any C++ dev here ?

@DCzajkowski can you help us here ? thanks !

Well I've tried messing about with this for about 2 hours and haven't figured out a fix. I tried switching all the dependencies to nan v2.12.1 but that hasn't solved it (we've had nan troubles in the past, but seems to just be a red herring).
Search engines don't bring much luck.
Darn you node_version.h!

Some insight: https://github.com/electron/electron/issues/17072#issuecomment-465692213

Good catch. The problem here is you will need a c++11 compiler to use
cmakejs 4.x or 5.x (5.1 is the latest) but iohook still use a lot of c++99
code. Do you want to have a look? You can start by bumping cmakejs and look
into the flags used in cmakelist.txt
--
Julien
Le mer. 20 févr. 2019 à 19:14, Andrew Morgan<EMAIL_ADDRESS>a
écrit :

Some insight: electron/electron#17072 (comment)
https://github.com/electron/electron/issues/17072#issuecomment-465692213
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/wilix-team/iohook/issues/144#issuecomment-465693699,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABHZtCTN6_KLDSivdRwIifaxh-9slm_xks5vPZCVgaJpZM4a4S4O
.

Is c++11 not backwards compatible with c++99? I can start with what you've said. I really wanna get this working on Electron v4 for inclusion into https://github.com/vector-im/riot-web :D

So bumping cmake-js to "^5.1.0" seems to make it all just work???

This is not what I saw ahah. Can you make a PR with your code and see if
the CI passes ?
--
Julien
Le jeu. 21 févr. 2019 à 18:07, Andrew Morgan<EMAIL_ADDRESS>a
écrit :

So bumping cmake-js to "^5.1.0" seems to make it all just work???
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/wilix-team/iohook/issues/144#issuecomment-466082030,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABHZtKUcZQ-jYGWxLj2bEF7nRFuqcIRFks5vPtI0gaJpZM4a4S4O
.

#148

I've tried to bump cmake to ^5.1.0 and build, but got the following error:
><EMAIL_ADDRESS>build /Users/lovebeam/iohook
> cmake-js compile

[ '/usr/local/Cellar/node/11.5.0/bin/node',
  '/Users/lovebeam/iohook/node_modules/.bin/cmake-js',
  'compile' ]
info TOOL Using Unix Makefiles generator.
info CMD BUILD
info RUN cmake --build "/Users/lovebeam/iohook/build" --config Release
make: *** No targets specified and no makefile found.  Stop.
info REP Build has been failed, trying to do a full rebuild.
info CMD CLEAN
info RUN cmake -E remove_directory "/Users/lovebeam/iohook/build"
info CMD CONFIGURE
info RUN cmake "/Users/lovebeam/iohook" --no-warn-unused-cli -G"Unix Makefiles" -DCMAKE_JS_VERSION="5.1.0" -DCMAKE_BUILD_TYPE="Release" -DCMAKE_LIBRARY_OUTPUT_DIRECTORY="/Users/lovebeam/iohook/build/Release" -DCMAKE_JS_INC="/Users/lovebeam/.cmake-js/node-x64/v11.5.0/include/node;/Users/lovebeam/iohook/node_modules/nan" -DNODE_RUNTIME="node" -DNODE_RUNTIMEVERSION="11.5.0" -DNODE_ARCH="x64" -DCMAKE_CXX_FLAGS="-D_DARWIN_USE_64_BIT_INODE=1 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DBUILDING_NODE_EXTENSION" -DCMAKE_SHARED_LINKER_FLAGS="-undefined dynamic_lookup"
Not searching for unused variables given on the command line.
-- The C compiler identification is AppleClang <IP_ADDRESS>01145
-- The CXX compiler identification is AppleClang <IP_ADDRESS>01145
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
CMake Error at CMakeLists.txt:53 (add_library):
  No SOURCES given to target: uiohook

-- Build files have been written to: /Users/lovebeam/iohook/build
ERR! OMG Process terminated: 1
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: `cmake-js compile`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/lovebeam/.npm/_logs/2019-03-05T20_44_38_046Z-debug.log

Well, atleast it started to build.

Hey @Djiit, sorry for being so late to the party. I would really like to help, but unfortunately I have no clue how. The only thing I can do is wish you good luck :)


error while compiling

I got an error while compiling:
/usr/include/boost/variant/get.hpp: In instantiation of 'typename boost::add_reference<T>::type boost::strict_get(boost::variant<T0, TN ...>&) [with U = const CScriptID&; T0 = CNoDestination; TN = {CKeyID, CScriptID}; typename boost::add_reference<T>::type = const CScriptID&]':
/usr/include/boost/variant/get.hpp:284:33:   required from 'typename boost::add_reference<T>::type boost::get(boost::variant<T0, TN ...>&) [with U = const CScriptID&; T0 = CNoDestination; TN = {CKeyID, CScriptID}; typename boost::add_reference<T>::type = const CScriptID&]'
src/rpcrawtransaction.cpp:242:77:   required from here
/usr/include/boost/variant/get.hpp:212:5: error: static assertion failed: boost::variant does not contain specified type U, call to boost::get<U>(boost::variant<T...>&) will always throw boost::bad_get exception
     BOOST_STATIC_ASSERT_MSG(
     ^
Makefile:2199: recipe for target 'build/rpcrawtransaction.o' failed
make: *** [build/rpcrawtransaction.o] Error 1

I have boost 1.58.0 installed.

"Changing line 242 in src/rpcrawtransaction.cpp to "const CScriptID& hash = boost::get(address);" fixes this (same as bitcoin fix). Perhaps this is something to consider for supporting newer boost versions?"
See http://www.reddit.com/r/vertcoin/comments/372ydk/wallet_crashes_on_os_x_1075/crjk8gs and https://github.com/bitcoin/bitcoin/pull/6114/files

Indeed, I have pushed the fix to master. Thanks for showing me this fix.

Awesome! Thank you very much!
James Lovejoy writes:

Indeed, I have pushed the fix to master. Thanks for showing me this fix.

Reply to this email directly or view it on GitHub:
https://github.com/vertcoin/vertcoin/issues/49#issuecomment-105074266

--
Pax et bonum.
Jorge Araya Navarro.
ES: Diseñador Publicitario, Programador Python y colaborador en Parabola GNU/Linux-libre
EN: Ads Designer, Python programmer and contributor Parabola GNU/Linux-libre
EO: Anonco grafikisto, Pitino programalingvo programisto kai kontribuanto en Parabola GNU/Linux-libre
https://es.gravatar.com/shackra


Add "Licensing" Page Reflecting "MIT License" in Footer

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Hey @MAVRICK-1 and @sanket95droid
The current website lacks a dedicated licensing page, The repository is licensed under the MIT License, which clearly states under that the project is distributed. A licensing page should be added to the website reflecting the MIT License to ensure legal clarity and transparency for users and contributors.
I would like to add Licensing Page which reflects MIT license for the website:

Use Case

User Navigates to the website.
User Clicks on the "License" link in the website's navigation menu.
System Displays the licensing page with the full text of the MIT License.
The user can easily find and read the licensing terms under which the project is distributed.

Benefits

Transparency
Legal Clarity
Professionalism

Priority
Medium
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@MAVRICK-1 @dinxsh @sanket95droid please take a look at this issue and assign me

and how do you intend to show the license details

Like this: @dinxsh

@MastanSayyad thanx but not needed


[docs] Splashscreen example gives compilation errors

I've tried to get the splashscreen example to work, but when I run tauri dev, I get:
[tauri]: running dev
 app:spawn Running "cargo run" +0ms

   Compiling pw-all v0.1.0 (/Users/emile/github/pwall/src-tauri)
error[E0599]: no method named `handle` found for mutable reference `&mut webview_official::webview::Webview<'_>` in the current scope
  --> src/main.rs:12:28
   |
12 |       let handle = webview.handle();
   |                            ^^^^^^ method not found in `&mut webview_official::webview::Webview<'_>`

error[E0308]: mismatched types
  --> src/main.rs:14:33
   |
14 |       tauri::close_splashscreen(&handle);
   |                                 ^^^^^^^ types differ in mutability
   |
   = note: expected mutable reference `&mut webview_official::webview::Webview<'_>`
                      found reference `&_`

error: aborting due to 2 previous errors

Some errors have detailed explanations: E0308, E0599.
For more information about an error, try `rustc --explain E0308`.
error: could not compile `pw-all`.

Is there a simple ready-to-run example app somewhere?

I also tried it. but getting the same error. This issue has to be resolved.

This compiles, but just crashes for me on Windows.
tauri::AppBuilder::new()
        // The splashscreen is declared
        .splashscreen_html("
The app is loading...
")
        .setup(move |webview, _| {
            // The splashscreen is removed
            tauri::close_splashscreen(webview).expect("Failed to close splash screen");
        })

First, it tries to load C:\tauri.js which doesn't exist, and then if I change the code to load tauri.js from a location that does exist I get a STATUS_STACK_BUFFER_OVERRUN crash.

https://github.com/tauri-apps/tauri/pull/1173 fixes the code itself and https://github.com/tauri-apps/tauri-docs/pull/152 fixes the docs. Thanks for the report and the help debugging!

https://github.com/tauri-apps/tauri/pull/1173 fixes the code itself and https://github.com/tauri-apps/tauri-docs/pull/152 fixes the docs. Thanks for the report and the help debugging!


stop words.txt in ultimate_schedule

Before submitting an issue, make sure you have:

[x] Updated to the latest version
[x] Read the README and docs
[x] Searched the bugtracker for similar issues including closed ones

Purpose of your issue?

[ ] Bug report (encountered problems/errors)
[ ] Feature request (request for a new functionality)
[x] Question
[ ] Other

Hi there.
Does anyone know?
If I add to ultimate.py in ultimate_schedule
this:
bot = Bot(comments_file=config.COMMENTS_FILE,
          blacklist_file=config.BLACKLIST_FILE,
          whitelist_file=config.WHITELIST_FILE,
          friends_file=config.FRIENDS_FILE,
          stop_words=config.STOPWORDS_FILE)       <---

And in the file config.py add STOPWORDS_FILE = "stop_words.txt" and create a file stop_words.txt in which there will be a stop word in this form:
'Dagmar',
'Dahlgren',
'Dakine',
'Dale of Norway',
'Dan Post',
'Daniblack',
'Daniel Barbara',
'Daniel Green',
'Danielle Nicole',
'Danner',
'Dansk',

Will all this work?
I ask because I did it and I can't understand how correctly the accounts are filtered.
Thx!

Will all this work?

This will definitely not work, it's no magic.
OTOH this is not hard to implement yourself ;)

its seems mad that the ultimate and ultimate-schedule vary so much. surely ultimate schedule should be a duplicate of ultimate.py but with the schedule module added in.


Implement render mode fog_disabled for all rendering backends

This fixes #56374 (and its duplicates like #69268).
A new render mode called fog_disabled is added. It can be used in spatial shaders (using render_mode fog_disabled) and from BaseMaterial3D using the new toggle Disable Fog found in the Shading section.
This works for the Forward+, Mobile and Compatibility rendering backends.
Screenshots
Disable Fog setting enabled

Disable Fog setting disabled

Minimal reproduction project
The minimal reproduction project from #56374 has been modified to include a DirectionalLight3D (without which the volumetric fog wouldn't render anymore), and the new disable_fog property has been enabled on the unshaded additively blended mesh. I've also enabled the depth-based fog to test the effect on the Mobile and Compatibility render backends as they don't support volumetric fog. I also added a cube with a shader material using render_mode unshaded; to demonstrate this working as well.
It can be downloaded here:
Fog_Volume_Additive.zip

The flag needs to be documented, see the CI errors

I'm not quite sure what causes the failure in this pipeline: https://github.com/godotengine/godot/actions/runs/6067098408/job/16458879823?pr=81286
It seems to be related to freeing an invalid key in the the ClassDB?

Unrelated to this PR, sporadic error

Could you please squash your commits into one? Make sure that the final commit has a short but descriptive message (the title of this PR is a good option). See this documentation, if you need help with squashing.

Done :sparkles:

Thanks, and congrats on your first merged Godot PR!

Thank you!


Use user_domain_* instead of domain_*

@mcanevet Thank you for pointing this out. Rather than replacing DomainID with UserDomainID (and *Name), UserDomainID and UserDomainName need to be added as additional fields. We then need to determine the correct DomainID and DomainName setting by following the precedence shown here:
https://github.com/openstack/os-client-config/blob/master/os_client_config/config.py#L593-L609
I've opened issue #4 to track this:
https://github.com/gophercloud/utils/issues/4
If you'd like to work on this, you're more than welcome to. Otherwise, I can take a look in the next day or two.

@jtopjian where would you put the code that determines the correct DomainID and DomainName to use?

It could go in the AuthOptions function here:
https://github.com/gophercloud/utils/blob/master/openstack/clientconfig/requests.go#L104-L111
After re-reading the Python function again, I think it should be fine to add something like this:
	if auth.UserDomainID != "" {
		ao.DomainID = auth.UserDomainID
	}

	if auth.UserDomainName != "" {
		ao.DomainName = auth.UserDomainName
	}

I think this might cause some scoping issues in certain situations, but I think that would need to be dealt with in Gophercloud (https://github.com/gophercloud/gophercloud/issues/252).

@jtopjian PR amended.

@mcanevet looks good, but the unit tests aren't passing (we need to get Travis hooked up to this repo).
The Domain settings need to be updated in the testing/fixtures.go file.

@jtopjian unit tests fixed

@mcanevet I think something might have gone awry with the last push. I see less code than before :)

@jtopjian I think it's normal, I removed the changes I did on unit tests because they are not required anymore with your suggestion to add fields and set the correct DomainID and DomainName.


Missing imports when spreading Impl blocks in multiple files

Describe the bug
When having a struct and an Impl for the struct in one file, and another impl for the same struct in another file with 'use' statements which werent made in the other file, they will be missing on the dart side's merged class implementation.
Steps to reproduce

Logs
-

Expected behavior
No response
Generated binding code
No response
OS
No response
Version of flutter_rust_bridge_codegen
No response
Flutter info
No response
Version of clang++
No response
Additional context
No response

Hi, could you please provide an exact minimal reproducible sample?

https://github.com/kjzl/frb_impl_dart_missing_imports

Ah I see, then this is a bug. Feel free to PR for it, alternatively I will fix it later! Since this has simple workaround (move the multiple impl block for one single struct in one file), I may not fix it with highest priority.


Prepare embedded-can 0.4.0 release

Is there anything preventing this release?
cc. @timokroeger

Looks good, no objections from my side.


usage example needed for pip autocompletion

When I was using antigen, the below setup gave me pip autocompletion
antigen use oh-my-zsh
antigen bundle pip

I'm migrating to antidote, and I tried this
ohmyzsh/ohmyzsh path:lib                           # these were in tutorial
ohmyzsh/ohmyzsh path:plugins/colored-man-pages     # these were in tutorial
ohmyzsh/ohmyzsh path:plugins/magic-enter           # these were in tutorial
ohmyzsh/ohmyzsh path:plugins/pip                   # is this right?

the pip is for autocompletion so (I'm guessing) the path option may be not proper here, but I have no idea how I can setup properly. How can I import the autocomplete plugin defined in ohmyzsh/ohmyzsh:plugins/pip ? (and hopefully not others in that directory).

The path:plugins/pip annotation is correct. You can see what antidote is doing by just running its bundle command:
% antidote bundle ohmyzsh/ohmyzsh path:plugins/pip
fpath+=( $HOME/.zplugins/ohmyzsh/ohmyzsh/plugins/pip )
source $HOME/.zplugins/ohmyzsh/ohmyzsh/plugins/pip/pip.plugin.zsh

The bundle command sets fpath, giving you the completions from the _pip file. It also sources the pip.plugin.zsh file from Oh-My-Zsh as well.

Thanks for your kind explanation! But I think I'm not getting autocompletion like "pip ins" thing where I can when using antigen. What would be the reason?

The only reason I can think of that you wouldn’t have completions is if you didn’t call compinit.
https://github.com/mattmc3/antidote/discussions/74
Antigen may do this for you. Antidote (and antibody) do not.

Thanks! It works! You're awesome!


Docker image for Arm64 platform is required

Hi Team,
I am trying to use the Kaniko image on arm64 platform but it seems it is not available for arm64.
I have successfully built the image using the command docker build -t <image_name> . on the arm64 platform with small changes in the Dockerfile.
Commit Link -  4319692e3fd414b32b05ce3052e7b713126918ce
Docker Hub Link -  https://hub.docker.com/repository/docker/odidev/kaniko
Do you have any plans on releasing arm64 images?
May I know how the amd64 image is getting published on Dockerhub?
If interested, I will raise a PR.

@krancour , can you please look at above issue?

@odidev I believe we've had conversations about this before in other threads. Please understand that we cannot be forced into prioritizing arm64 support just by you opening more issues against more of our repos.
We are interested in arm64 support and intend to pursue it when we are able, but at present we do not have arm64 VMs at our disposal. Our hands are kind of tied until that changes.

@odidev my apologies if my response came off as harsh. I did not mean for it to.
We're just kinda stuck at the moment in a place where we don't have the infrastructure we need to do this.
Despite our love of "dogfooding" Brigade, these simple "helper images" like go-tools, kaniko, helm-tools, etc. are outliers in that we're letting DockerHub build these for us...
When time allows, I'll take a look at what it would take (or if it's even possible) to do multiarch builds directly on DockerHub. If it's possible, these would be the first baby steps toward arm64 support-- and they'd be steps taken partly on faith because we don't have the means to even validate the arm64 images at the moment.

We've unfortunately taken a step backward on this. Due to Docker pricing, we no longer automate any builds through DockerHub and we do everything with our "dogfood" Brigade cluster.
We still do not have arm64 VMs at our disposal.
I'm going to close this and allow the issue to be subsumed by a larger effort to get all of Brigade working on arm64 post v2.


Merge master in to resolve merge conflicts

This resolves merge conflicts in https://github.com/studentinsights/studentinsights/pull/1154 introduced by https://github.com/studentinsights/studentinsights/pull/1182.

Thank you for creating this PR, @kevinrobinson! Should I do a Rebase and merge, a Squash and merge or a Create merge commit? From what I know so far, rebase sounds like the way to go but wanted to double check.

@gabivoicu You can just merge this pull request here with the big green button in the GitHub UI.  That will merge these commits into the 1087-student-contact-info branch in your GitHub repo, and then on the command line you can git pull the gabivoicu/studentinsights repository down to your local machine to see the changes locally and keep working.
Let me know if you have any other questions or run into any issues!

@kevinrobinson The big green button on here has a drop down that gives those three options (Rebase, Squash and Create merge commit) and I know different teams have different preferences, that's what I was asking about. But if it doesn't make a difference, I can merge w/ a Create merge commit. Let me know if that would be a problem at all.

@gabivoicu ah sorry I didn't realize!  Sounds like you all talked this out on the caller earlier but let me know if there's anything else I can help with.


Fix issues with rule name translations

This fixes issues with rule name translations. Previously translations were under %{locale}.errors.rules, now they are under root, so %{locale}.rules.
Closes #52
Closes #57

Well done dude!


Rails 7.1 Obfuscates Errors

For example, when missing comma in object
const detailsEl = createElement({
    class: 'foo'
    content: 'hello world'
})

Results in:
Puma caught this error: undefined method `map' for nil:NilClass (NoMethodError)
/opt/homebrew/lib/ruby/gems/3.2.0/gems/activesupport-7.1.2/lib/active_support/syntax_error_proxy.rb:41:in `backtrace_locations'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/exception_wrapper.rb:274:in `build_backtrace'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/exception_wrapper.rb:56:in `initialize'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/exception_wrapper.rb:290:in `new'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/exception_wrapper.rb:290:in `block in wrapped_causes_for'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/exception_wrapper.rb:286:in `causes_for'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/exception_wrapper.rb:290:in `each'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/exception_wrapper.rb:290:in `map'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/exception_wrapper.rb:290:in `wrapped_causes_for'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/exception_wrapper.rb:51:in `initialize'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/show_exceptions.rb:35:in `new'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/show_exceptions.rb:35:in `rescue in call'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/railties-7.1.2/lib/rails/rack/logger.rb:37:in `call_app'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/railties-7.1.2/lib/rails/rack/logger.rb:24:in `block in call'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/activesupport-7.1.2/lib/active_support/tagged_logging.rb:135:in `block in tagged'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/activesupport-7.1.2/lib/active_support/tagged_logging.rb:39:in `tagged'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/activesupport-7.1.2/lib/active_support/tagged_logging.rb:135:in `tagged'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/activesupport-7.1.2/lib/active_support/broadcast_logger.rb:240:in `method_missing'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/railties-7.1.2/lib/rails/rack/logger.rb:24:in `call'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/remote_ip.rb:92:in `call'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/request_id.rb:28:in `call'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/rack-2.2.8/lib/rack/method_override.rb:24:in `call'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/rack-2.2.8/lib/rack/runtime.rb:22:in `call'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/activesupport-7.1.2/lib/active_support/cache/strategy/local_cache_middleware.rb:29:in `call'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/server_timing.rb:59:in `block in call'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/server_timing.rb:24:in `collect_events'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/server_timing.rb:58:in `call'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/executor.rb:14:in `call'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/actionpack-7.1.2/lib/action_dispatch/middleware/static.rb:25:in `call'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/rack-2.2.8/lib/rack/sendfile.rb:110:in `call'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/railties-7.1.2/lib/rails/engine.rb:529:in `call'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/puma-5.6.4/lib/puma/configuration.rb:252:in `call'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/puma-5.6.4/lib/puma/request.rb:77:in `block in handle_request'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/puma-5.6.4/lib/puma/thread_pool.rb:340:in `with_force_shutdown'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/puma-5.6.4/lib/puma/request.rb:76:in `handle_request'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/puma-5.6.4/lib/puma/server.rb:441:in `process_client'
/opt/homebrew/lib/ruby/gems/3.2.0/gems/puma-5.6.4/lib/puma/thread_pool.rb:147:in `block in spawn_thread'

Moving to malomalo/condenser


[Plugin][Bug]: GitHub token is empty

Issue validation

[X] I checked the issue to prevent duplicate
[X] I checked my configurations files and the documentation

Command used
No response
Plugin version
6.4.0
Describe the bug
I installed the plugin via Community Plugins, started configuring everything: set the repository name, username, generated a token and entered it. I pressed the Test connection button, and here is the result:

How to reproduce ?
No response
Minimal Reproducible Example
Obsidian v1.3.7, GitHub Publisher v6.4.0 installation with no other plugins

Configuration
{
  "github": {
    "branch": "master",
    "automaticallyMergePR": true,
    "tokenPath": "%configDir%/plugins/%pluginID%/env",
    "api": {
      "tiersForApi": "Github Free/Pro/Team (default)",
      "hostname": ""
    },
    "workflow": {
      "commitMessage": "[PUBLISHER] Merge",
      "name": ""
    },
    "verifiedRepo": true
  },
  "upload": {
    "behavior": "fixed",
    "defaultName": "",
    "rootFolder": "",
    "yamlFolderKey": "",
    "frontmatterTitle": {
      "enable": false,
      "key": "title"
    },
    "replaceTitle": [],
    "replacePath": [],
    "autoclean": {
      "enable": false,
      "excluded": []
    },
    "folderNote": {
      "enable": false,
      "rename": "index.md"
    },
    "metadataExtractorPath": ""
  },
  "conversion": {
    "hardbreak": false,
    "dataview": true,
    "censorText": [],
    "tags": {
      "inline": false,
      "exclude": [],
      "fields": []
    },
    "links": {
      "internal": false,
      "unshared": false,
      "wiki": false,
      "slugify": false
    }
  },
  "embed": {
    "attachments": true,
    "keySendFile": [],
    "notes": false,
    "folder": "",
    "convertEmbedToLinks": "keep",
    "charConvert": "->"
  }
}

Relevant log output
No response
OS
Linux
Anything else?
No response
Obsidian information
SYSTEM INFO:
	Obsidian version: v1.3.7
	Installer version: v1.3.7
	Operating system: #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jul 13 16:27:29 UTC 2 6.2.0-26-generic
	Login status: logged in
	Catalyst license: none
	Insider build toggle: off
	Live preview: on
	Legacy editor: off
	Base theme: dark
	Community theme: none
	Snippets enabled: 0
	Restricted mode: off
	Plugins installed: 1
	Plugins enabled: 1
		1: Github Publisher v6.4.0

RECOMMENDATIONS:
	Community plugins: for bugs, please first try updating all your plugins to latest. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community plugins.

Did you open the env in the plugin folder (.obsidian\plugins\obsidian-mkdocs-publisher) and check if the token is written ?

Did you open the env in the plugin folder (.obsidian\plugins\obsidian-mkdocs-publisher) and check if the token is written ?

I have no idea, but now it's saves fine.
However, it writes that the repository was not found despite the fact that the token has rights to the repositories and the repository really exists

When I change repository visibility to public, it's all fine.

Is it intended behavior?

Hmmm, it's pretty strange, I don't have the problem on my side, so I don't understand why. Maybe a problem around the token ?

i am having the same problem

i am using windows and it was not creating a env file in the path specified

What do you have in the console ?

I made a little update for the token in the plugin, where you can use a JSON syntax instead of the basic env.
Could you try it? You just need to add .json at the end of the path!

Nothing change in the settings, just paste the key as before. Don't forget to open the console (CTRL + MAJ + I) to capture the log if anything pop.


Added Quaternion Based 6DOF Spring Joint Bullet Class (GODOT 3.x)

btGeneric6DofSpringConstraintQuaternion
Based on btGeneric6DofSpring2Constraint.
This class was made to provide more control over spring joint "equilibrium" rotation using quaternions instead of Euler Axes. This makes it useful for "puppeteering" joint controlled active ragdolls.

This was made in response to this feature request:
https://github.com/godotengine/godot-proposals/issues/3891
The implementation involved modifying the "Generic6DOFJoint" node to use btGeneric6DofSpringConstraintQuaternion instead of btGeneric6DofSpring2Constraint meaning no new nodes were added minimizing changes on how users would interact with the node.
Angle parameters are passed in just as before thru the "angular_spring_[x,y,z]/equilibrium_point" parameters.
Here is an example of its use:

In the image above, note that the targetPosition(Slab(green)) is attached to a mesh node (point(blue)) rotated to the following degrees relative to the first RigidBody node(Pillar). A 6DOFJoint(Generic6DOFJoint2) is positioned where the "point" node is, connecting the two RigidBodies.

Passing the mentioned set angles as angular equilibrium parameters to Generic6DOFJoint2, the joint acts accordingly and rotates the rigid bodies in a stable manner (depending on the set stiffness and damping parameters) to the desired expected position:

compared to using the Euler axis based joint as before:

(you don't see it in the picture, but the whole thing is wiggling in game)
Here are some videos of the earlier prototypes:
(GDScript)

https://youtu.be/htMDZ0fXJWo

https://youtu.be/pFo2pOIqcXs

https://youtu.be/m_vrJUQA_s8

https://youtu.be/g4WuGlEvRG8
(C++ in Bullet Physics)

https://youtu.be/EoKXfdmpNz0
I also made a pull request on the Bullet Physics Repo(Review Pending). I didn't want to wait so here it is.

Right almost forgot...
Basically I went all this trouble to add 3 new properties to the Generic6DOFJoint class:

but I mostly had trouble at documention:

@19PHOBOSS98 While you may be done with your changes, this can't be merged in the current state even if approved. You have 26 commits, when your PR must only include one. You need to squash your commits and rebase them against the current 3.x branch, then force-push it.
See https://docs.godotengine.org/en/stable/community/contributing/pr_workflow.html#the-interactive-rebase for more information if you have trouble doing it.

@19PHOBOSS98 While you may be done with your changes, this can't be merged in the current state even if approved. You have 26 commits, when your PR must only include one. You need to squash your commits and rebase them against the current 3.x branch, then force-push it.
See https://docs.godotengine.org/en/stable/community/contributing/pr_workflow.html#the-interactive-rebase for more information if you have trouble doing it.

Ok, thanks

sorry, I was trying to fetch not push

right, I squashed it all into my first commit... Apparently I forgot to add a proper commit title for the first one... I should change that, brb.

by @aaronfranke 's suggestion, I'll be changing a few lines of code, but I'll do it in my local build to try and minimize my commit

is there anything else I missed?


Update the bug template

It's copied over from https://github.com/JosefNemec/PlayniteExtensions, but here it doesn't make sense to mention the Diagnostic ID.

https://github.com/XenorPLxx/playnite-library-psn/commit/53d8a67b91ab96000dc5d2808bfaed7c6e1ef9fd


Change table queue to in-memory queue and add callbacks

Reasons

For all the requests to finish, an INSERT on the _http_response table must be done, this reduces throughput. There are cases where the client doesn't care about the response so it doesn't need to be persisted. For example, function hooks don't do anything with the response.
As discussed in https://github.com/supabase/pg_net/pull/50#issuecomment-953796674, we don't have to ensure delivery and do retries since we're just an HTTP client, so we don't really need to persist the requests into http_request_queue.
The http_request_queue can grow big with many requests and cause production issues(internal link).
Users create FKs to our private tables https://github.com/supabase/pg_net/issues/44, making the bg worker crash when trying to do the TTL.

Proposal
Drop the _http_response and http_request_queue tables and instead use an in-memory queue, plus add two callbacks:
create or replace function net.http_get(
   url text,
-- ..,
   success_cb text default '',
   error_cb text default ''
)
returns void -- no id is returned now
as $$
-- ...
$$ language sql;

Which can be used like:
select net.http_get(
  url := 'http://domain.com',
, success_cb := $$ insert into my_table values ($1, $2, $3) $$ -- $1=status, $2=headers, $3=body
, error_cb := $$ do $_$begin raise exception 'Failed request on %: "%"', $1, $2; end$_$; $$ -- $1=url, $2=error_message
);

Pros

The callbacks are optional, so we don't have to start a transaction for each request if there are none provided. Throughput should be greatly increased from this.
The error_cb can also be an insert/update on a table, so the request can be retried if needed.

@olirice @soedirgo WDYT?

Ohh, so that's what you meant by callbacks. Nice! Also like that this makes the impl a lot simpler and more akin to typical HTTP clients.
How would go about implementing the in-memory queue? IIRC when I looked into it passing info from the client process to the bgworker process was nontrivial.

that looks great!
Is it correct that all http status codes (e.g. including 500) would still go through the success_cb and the error_cb applies to stuff like timeouts?

returns void -- no id is returned now

I think it would still be good to return a uuid and pass that through to the callbacks i.e.
select net.http_get(
  ...
, success_cb := $$ -- $1=status, $2=headers, $3=body $4=request_id $$,
, error_cb := $$ -- $1=url, $2=error_message, $3=request_id $$
); -- result is uuid (request_id)

so if people are firing off a large number of requests, or want to associate a request with a response they'll have the tools they need

I know pg_cron does a similar inline sql approach but afaik they don't have to deal with passing parameters. Are we sure theres a good way to do that?
if not, a backup solution might be
create or replace function net.http_get(
-- ..,
   success_cb regproc default null,
   error_cb regproc default null
)
...as $$
-- ...
$$ language sql;

where the function signature matches the callback requirements

I know pg_cron does a similar inline sql approach but afaik they don't have to deal with passing parameters. Are we sure theres a good way to do that?

Should be possible with the USING clause, though we should probably document that the callbacks are limited to plpgsql command strings.

How would go about implementing the in-memory queue?

There's an example in postgres/src/test/modules/test_shm_mq for how to use the shared memory queue.

Is it correct that all http status codes (e.g. including 500) would still go through the success_cb and the error_cb applies to stuff like timeouts?

Yes, correct. Things like "unable to resolve host" as well.

so if people are firing off a large number of requests, or want to associate a request with a response they'll have the tools they need

I think we should leave that to be done externally, users can pass an id on the callback like:
select net.http_get(
  -- url, headers, body..
, success_cb := format($$insert into responses values(%s, $1, $2, $3)$$, id);
);

And this id can come from a trigger on a table or maybe from a sequence used in a wrapper function. With that they can still associate a request/response if they want.

I know pg_cron does a similar inline sql approach but afaik they don't have to deal with passing parameters. Are we sure theres a good way to do that?

Yes, SPI_execute_with_args should take care of that.
I've also thought about supporting something like insert into tbl($status, $headers, $body) for better DX but that would require parsing and we'd loss perf. So I've just kept it simple at this stage.

Should be possible with the USING clause

cool! didn't know about that

I think we should leave that to be done externally, users can pass an id on the callback like:

I think we should leave that to be done externally, users can pass an id on the callback like:
select net.http_get(
  -- url, headers, body..
, success_cb := format($$insert into responses values(%s, $1, $2, $3)$$, id);
);

And this id can come from a trigger on a table or maybe from a sequence used in a wrapper function. With that they can still associate a request/response if they want.

ah nice, that works
IMO its a common enough case that it should have first class support with a parameter (so its obvious what to do from the docs), but if you don't agree I'm not gonna die on that hill :)

or maybe from a sequence used in a wrapper function. With that they can still associate a request/response if they want.

good point

I'm thinking that moving to an in-memory queue would allow for http requests during postgrest GET requests as well?
During GET requests, postgrest uses a read-only transaction, during which INSERTs and other modifications are not allowed. I'm currently having troubles with making http requests as part of my policy for performing SELECTs on some tables due to this.

I'm thinking that moving to an in-memory queue would allow for http requests during postgrest GET requests as well?

Yes, since an http_get wouldn't need an INSERT on the net.http_request_queue anymore.

We would lose observability if we go this route, currently customers can do:
-- requests with fail/success HTTP status codes
select count(*), status_code from net._http_response group by status_code;
 count | status_code
-------+-------------
   448 |         429
   821 |         500
  1182 |         408
  2567 |         200

-- rate limiting error
select content from net._http_response where status_code = 429 limit 1;
                          content
------------------------------------------------------------

429 Too Many Requests
                +
 You have sent too many requests in a given amount of time.+

Which is great for debugging and finding out why a webhook receiver might be failing.
To increase throughput, we could make the net tables UNLOGGED, remove indexes and PKs from them(this would also solve https://github.com/supabase/pg_net/issues/44).

+1 for just logging errors, in general making it as stateless as possible should help with stability.

Yeah, agree. Also forgot about https://github.com/supabase/pg_net/issues/49, observability would be better with logging.

Any plans to implement this new feature in the near future?


fix: RN GRPC issue

Successfully published:
 -<EMAIL_ADDRESS> -<EMAIL_ADDRESS> -<EMAIL_ADDRESS>


Init shogun util

This initializes the usage of the shogun-util for loading and parsing a remote application context.
Please note @terrestris/devs.

Thanks for this! Looks good so far (only shogun base url should be read from config file or other in future).


Dupe IDs are handled when use_existing_tensors=True

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
bug fix

What is the current behavior? (You can also link to an open issue here)
When use_existing_tensors=True and docs are added with duplicate IDs, a MarqoWebError with no status code is thrown.

What is the new behavior (if this is a feature change)?
When use_existing_tensors=True and docs are added with duplicate IDs, docs are added normally. The last doc in the list with the same ID is the one that gets kept.

MarqoWebError has a status code of 500 by default now.
Unit tests have been added to test duplicate IDs with and without use_existing_tensors

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No

Have unit tests been run against this PR? (Has there also been any additional testing?)
Yes

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[x] Tests for the changes have been added (for bug fixes/features)
[x] Docs have been added / updated (for bug fixes / features)

Run passed: 268 https://github.com/marqo-ai/marqo/actions/runs/4418255521/jobs/7745155005#logs

monitor: https://github.com/marqo-ai/marqo/actions/runs/4419170567

Reports on bug found by vitus "chunks" key error:
            {"_id": ["bad", "id"], "field_1": "zzz"},
            {"_id": "proper id 2", "field_1": 90}], 2)

error happens when adding this doc repeatedly

res_chunks
  '_index': 'my-test-index-1',
  '_primary_term': 1,
  '_seq_no': 0,
  '_source': {},
  '_version': 1,
  'found': True},

res_data
 {'_id': 'proper id',
  '_index': 'my-test-index-1',
  '_primary_term': 1,
  '_seq_no': 0,
  '_source': {'__chunks': [], 'field_1': 5678},
  '_version': 1,
  'found': True}```

question: why does res_chunks have no chunks? in what situation would _source be empty?

Another situation:
"""
Error happens with

available_product_codes: List and the one to remove is source_image_url
despite treat_urls_as_pointers
regardless of model used
"""

Diagnosis (3/15/23)
The error
_get_documents_for_upsert
    if result["_source"]["__chunks"] == []:
KeyError: '__chunks'

Happens when the following conditions occur

A document is created with no tensor fields, therefore it has no _source["__chunks"]
Add documents is called using use_existing_tensors with the id of the chunkless doc.

A chunkless doc is one of the following:

Doc without a string/list/anything else that gets tensorized as a field.

int, bool do not get tensorized
using non_tensor_fields on all fields to be tensorized will do this
Interestingly, lists should not get tensorized, but they do not have the same problem as int and bool

Solution:
If a doc is chunkless, one of the 2 results from _get_documents_for_upsert that was supposed to have chunks will have empty source like this: '_source': {}
# chunkless result
[{'_id': 'proper id 2',
  '_index': 'my-test-index-1',
  '_primary_term': 1,
  '_seq_no': 0,
  '_source': {},
  '_version': 1,
  'found': True},

 {'_id': 'proper id 2',
  '_index': 'my-test-index-1',
  '_primary_term': 1,
  '_seq_no': 0,
  '_source': {'__chunks': [], 'field_2': 123},
  '_version': 1,
  'found': True}]

If empty source is found, set that as res_chunks.

Running unit tests: https://github.com/marqo-ai/marqo/actions/runs/4432692586


Adds Streets Maps

Add Streets Maps 🗺
This PR adds the very first renditions of the "Streets of Tarkov" maps. These maps will soon be replaced with better maps in the future that have less jpeg

.deploy


Filesystem Quotas

Because it was trivial to set this property for zfs, I have  implemented per container filesystem quotas.
For obvious reason these includes also code needed for the zfs driver, with the quota patch applied on top.
TODO:

it would be great, if someone else could add support for other filesystems. Somebody has done this for btrfs. Devicemapper + ext4 should be also possible. I have extended the graphtest, to test this feature. If somebody get something working, they can send me a PR and I will merge it into this PR.
I don't like the current the way, I have extended the driver interface currently, in the best case it would  just be another optional interface, but this is not possible the NaiveDiffDriver hides any interfaces implemented in the underlying ProtoDriver.

Can you please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "quotas" git@github.com:Mic92/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~10
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

This will update the existing PR, so you do not need to open a new one.

The feature looks useful, but I'd rather seen #9411 merged into master before reviewing this PR in deep.
/cc @jfrazelle because she's assigned to #9411

This PR is certainly something to discuss after #9411. #9411 is something I really want to get merged.
Quotas are yet another feature I'd like to have in Docker, but that needs to be discussed first. The reason why it needs to be discussed is so that we ensure that:

it ties into everything it needs to - docker run, docker build and into volumes

we discuss ways to implement these quotas for the various storage backends

we need to figure out a way to make this work transparently for the users so they don't a) have to set something up before using these quotas and b) this doesn't affect their system in any way

is pretty easy to address, but 2) is an entirely different story.

Let's get #9411 and discuss file system quotas after that. It's OK if we come up with a strategy for some of the graph drivers and implement file system quotas for the others later on.
I'm going to close this PR for now and we can continue the discussion after we get #9411 merged.

@Mic92  hi , i am very Interest in “disk quota” ， this case can use “disk quota” in every container？ ths。

@blackfader the thing I did is exposing:  zfs set quota= zpool/container-rootfs
via docker command line, so there is a per container quota

@Mic92  it is cool! I don't understand docker not merge master， I want to use ， your fork docker project is not lastest ， I want merger this to docker master lastest.


Constant Warning Error in Logs is it an issue or a booting warning

From Logs on every restart
This error originated from a custom integration.
Logger: custom_components.meross_lan
Source: custom_components/meross_lan/helpers.py:23
Integration: Meross LAN (documentation, issues)
First occurred: 08:30:16 (3 occurrences)
Last logged: 08:30:16
MerossDevice(2009223902001190831148e1e9344bb8) error in async_http_request: Server disconnected
MerossDevice(2009222728525590831148e1e9343614) error in async_http_request: Server disconnected
MerossDevice(2009221363906590831148e1e934418a) error in async_http_request: Server disconnected
Info re HA
System Health
version: core-2022.2.3
installation_type: Home Assistant OS
dev: false
hassio: true
docker: true
user: root
virtualenv: false
python_version: 3.9.7
os_name: Linux
os_version: 5.10.96
arch: x86_64
timezone: Europe/London
GitHub API: ok
Github API Calls Remaining: 4719
Installed Version: 1.22.0
Stage: running
Available Repositories: 977
Downloaded Repositories: 24
logged_in: false
can_reach_cert_server: ok
can_reach_cloud_auth: ok
can_reach_cloud: ok
host_os: Home Assistant OS 7.3
update_channel: stable
supervisor_version: supervisor-2022.01.1
docker_version: 20.10.9
disk_total: 30.8 GB
disk_used: 18.3 GB
healthy: true
supported: true
board: ova
supervisor_api: ok
version_api: ok
installed_addons: Samba share (9.5.1), Check Home Assistant configuration (3.9.0), SSH & Web Terminal (10.0.2), Home Assistant Google Drive Backup (0.105.2), Studio Code Server (4.1.0), MariaDB (2.4.0), InfluxDB (4.3.0), Grafana (7.4.1), Mosquitto broker (6.0.1)
dashboards: 3
resources: 16
views: 75
mode: storage

It could be a device key issue then.
Or something else... if you're up for a bit of tracing I suggest you to enable the tracing feature on any (or all) of the 'warning' entities (instructions here).
If we're lucky enough we could grab a trace (it only traces 10 minutes of traffic) while the error gets logged and try to understand maybe the reason.
If you grab an error please post the trace then
@krahabb

I am still getting errors logs periodically so i have turned on the trace feature :)
This error originated from a custom integration.
Logger: custom_components.meross_lan
Source: custom_components/meross_lan/helpers.py:23
Integration: Meross LAN (documentation, issues)
First occurred: 08:11:54 (1 occurrences)
Last logged: 08:11:54
MerossDevice(2009222728525590831148e1e9343614) received signature error (incorrect key?)

It could be the devices are configured with a wrong 'key'
If you left it empty when adding to HA integrations it might explain the random disconnects issue.
You can check this post for an explanation on how to re-configure the correct key. At the moment the only way to recover the effective key for devices paired to the meross app is to delete/readd the integration configuration. Once done for a single device you can then manually copy over the key (it is the same for all of the same meross-account-paired devices) to the other devices.
There's a reference to the 'manual' way to recover the official key in this post so you don't have to remove the device from HA
I hope you really left the key empty in meross_lan device configuration since it would explain the issue...else we're a bit lost!

All  3 items have the identical key  plus some other number on the hub which i don’t have


Add a tag for side effects

I would need to tag when a function has side effects, say with:
@sideEffects: console.log, fs.writefile

Expected behavior
This is supposed to be an array of strings or links to functions documentation within the same code base or externally, or both.
@sideEffects: console.log, fs.writefile

or
@side_effects: console.log, {@link https://nodejs.org/api/fs.html#fs_fs_writefile_file_data_options_callback|fs.writefile}

It could be abbreviated as @sfx:
@sfx: console.log, fs.writefile

Related issues:

probably #833
@modifies doesn't seem to apply here

Has this been considered? It really would be a key feature for me, as a lot of methods do not return values in React but instead modify the parent class's state

@modifies already exist and is supposed to be used for this situation. But for some reason it has been added in 2018 and has been undocumented ever since


Don't use arrays for torrent meta

Since I don't plan to merge together duplicate torrents in favor of just skipping duplicates, this will make it much easier to build an algorithm to .Distinct() the categories and fix the browse page's slowness.

I wonder if skipping duplicates completely is good practice.  I selected two magnet links that had identical names but when both where opened in qbittorrent it merged the trackers instead of the popping up a notification saying "not added as it was a duplicate".  I believe this happens when I use two magnet links from seperate sites useing different trackers for the same file.  This help me speed up my download.  Maybe there is someway you can merge the trackers?  Or perhaps I'm barking up the wrong tree here.... TIA and great project btw, loving it

BitCannon actually doesn't tack on trackers to the magnet links. I forgot about this and I will definitely add it in the next release.
What I've actually done is a little cheat to not have to deal with storing trackers:
Since there are only a few trackers, I don't store trackers for every torrent, the config file just has a list of open trackers and I plan on just scraping them all for every torrent and hope that at least 1 tracker has the torrent. I did forget to add these trackers to the magnet link, though, so I'll make sure to do that so torrents won't download too slow.

Many Thanks.  I have seen many a post abouot you adding tracking scrapping, I take it this will be another point to add to the list then.