Wikidata reconciliation problem

I can reconcile columns against Wikidata OK, but when I try to create a schema none of the columns will drag down. The columns are 100% reconciled, and I am still able to reconcile data from within the project OK. I have tried opening previous projects that generated edits successfully, and the reconciliation service fails to connect, and the schema has disappeared from them and is unable to be recreated (screenshot from a previously successful project attached).

I've restarted OpenRefine, and Firefox, tried Chrome, restarted the computer, and reinstalled OpenRefine, to no avail. I am using 3.4.1 on Firefox (but problem persists in Chrome).
Any suggestions appreciated, thanks,
Tamsin

Which reconciliation service have you used to reconcile your columns?
At the moment https://wdreconcile.toolforge.org/en/api returns an HTTP 504 error for me. This reconciliation service is known to be unreliable and is unmaintained. We would like to switch away from it: https://github.com/OpenRefine/OpenRefine/issues/3080
Perhaps one temporary workaround would be to reconfigure Wikidata to use "https://wikidata.reconci.link/en/api" in the schema, which should be possible by writing a new manifest for Wikidata with this reconciliation service. But I am not sure if we let the user do that when there is already one Wikibase configured with the same MediaWiki endpoint.

Thank you. I had tried every reconciliation service I could find! (I remember it changed at the end of July). I had two services marked as old, which would not delete, and one to https://wikidata.reconci.link/en/api that shows as wikidata reconci.link (en). I have since managed to delete the services marked as "old" (with difficulty because the services tab keeps bouncing across the screen). It has not changed the problem, I can still reconcile cells but cannot create a schema.

Closing this as this is due to the instability of an external service.


With the better memory management, we can probably run the builds in parallel

@andrewram4287 it looks like Figure 3a is broken—data is undefined. Please fix this here.

@andrewram4287 it looks like Figure 3a is broken—data is undefined. Please fix this here.

Should be fixed!

@andrewram4287 looks like Fig. 3c is broken now.

Great. Thanks.


FR: Would like to see console to be translated to HINDI.

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have removed any sensitive information from my code snippets and submission.

Amplify Hosting feature
Not Applicable
Is your feature request related to a problem? Please describe:
Would love to see the console to get translated HINDI,
I would like to the console website to be available to people who speak hindi,
https://en.wikipedia.org/wiki/List_of_languages_by_number_of_native_speakers_in_India,
https://en.wikipedia.org/wiki/Hindi#Geographical_distribution
Describe how you'd like this feature to work
This features will help people who have hard time learning english and would still want to use the website. This can make millions of people happy, thank you.

No longer interested in this feature request. Do we have a down vote reaction option if I strongly discourage 👎


Remove backup file if it exists

This is to partly fix the issue in #168
Some unexpected process termination can leave a '.bak' file undelete, so next executions will error.

/test

/test

LGTM. This PR also changes the order of handling snapshot files.
Previously, the logic was:

Rename dest to dest.bak
Create tmp_dest
Rename tmp_dest to dest

However, step 2 often takes time so there was a high possibility of being preempted (killed) during that process. This PR changes the logic to:

Create tmp_dest
Rename dest to dest.bak
Rename tmp_dest to dest

so that dest is kept even if the process is killed during the file creation. Note that it is still possible that the process is killed between 2 and 3 but we need this non-atomic operation to support various file systems e.g. HDFS.


Table of content links are broken on "Testing stores" page

Reproduction
See description
Steps to reproduce the bug

Navigate to https://pinia.vuejs.org/cookbook/testing.html
Click on one of the section links in the the table of content (not the sidebar) --> nothing happens

Expected behavior
Jump to the clicked section
Actual behavior
A distinction is made between upper and lower case letters
https://pinia.vuejs.org/cookbook/testing.html#initial-state --> fails (this is used)
https://pinia.vuejs.org/cookbook/testing.html#Initial-State --> workis
Additional information
No response

Fix in https://github.com/vuejs/pinia/pull/2351


Add support to determine/enforce delivery priority based on actual payload

"It is an error to use this priority (Author's Remark: IMMEDIATE) for a push that contains only the content-available key."

see https://developer.apple.com/library/ios/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/Chapters/CommunicatingWIthAPS.html
At the moment the delivery priority is set manually or defaults to IMMEDIATE (see SimpleApnsPushNotification constructors). This may conflict with the actual payload.
I'd like to see some support to determine, whether the delivery priority CONSERVE_POWER is required or IMMEDIATE is allowed.
Maybe ApnsPayloadBuilder can track this and provide a method getDeliveryPriorityRestriction returning an enum DeliveryPriorityRestriction (either CONSERVE_POWER_REQUIRED or IMMEDIATE_ALLOWED)
Or maybe you can shed some light on the implications of the above requirement.
It is not completely clear to me, what the mentioned apple documentation means exactly. Some examples:
A silent push, must use CONSERVE_POWER
  "aps": {
    "content-available": 1
  }
}```

A standard push + content-available to show a message and trigger  application:didReceiveRemoteNotification:fetchCompletionHandler in the app (does this make sense at all?): Both priorites allowed
```{
  "aps": {
    "alert": "Some message",
    "content-available": 1
  }
}```

What about this? Seems to be a silent push (no alert, no badge, no sound), yet content-available is not the only key in aps. Which priorities are allowed here?
```{
  "aps": {
    "category": "SomeCategory",
    "content-available": 1
  }
}```

And finally: Silent Push along with custom properties: must use CONSERVE_POWER
```{
  "aps": {
    "content-available": 1
  },
  "someCustomProperty": "someCustomPropertyValue"
}```

Please comment, if my assumptions are wrong.

Best regards
Christian Charles

maybe you can shed some light on the implications of the above requirement.

I ran some experiments, and having a content/priority mismatch doesn't seem to cause any protocol-level problems. One consequence of making a change like this would be that we'd have to parse every single message we wanted to send, and I'm worried about the performance implications there. Given that we don't check payloads for other content-level errors, that there's no protocol-level implication for getting this wrong, and the potential performance hit, I'm inclined to leave this kind of checking to users.
Sound good?

Closing for now. @tscharlii please leave a comment if you'd like us to reconsider.


No update here for May 2021 What's New. Please add.

[No update here for May 2021 What's New. Please add. ]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ff7e1942-9181-3451-5d1e-08bfa2ca9454
Version Independent ID: 5547fc15-7d0e-225f-e0f1-890470f6cd5e
Content: What's new in Power BI Report Server - Power BI
Content Source: powerbi-docs/report-server/whats-new.md
Service: powerbi
Sub-service: powerbi-report-server
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Hi, @mfloyd65 -- good catch! I'll check and get back to you. In the meantime, the Change Log article was updated for May 2021, if that helps:
https://docs.microsoft.com/en-us/power-bi/report-server/changelog

Hi, @mfloyd65 -- I've added the highlights, with a link to the blog post with the complete information. Update will be live tomorrow Sept 9 afternoon Pacific time.
Here's a link to the blog post:
https://powerbi.microsoft.com/blog/power-bi-report-server-may-2021-feature-summary
Thanks!


Refactor Call Graph Producer

Description
This PR aims to refactor the Python Call Graph Producer in the following ways:

Removed the Call graph converter phase since now PyCG produces Call Graphs in the correct Fasten format.
Applied the separation of concerns design pattern in cg-producer by separating all the kafka related functionalities from the call-graph generation processes.
Published the Call graph Generation class to PyPI, in order to be used as a standalone library by our partners.
Added github action workflow for publishing  the Call Graph Producer docker image to Github Registry under the Fasten namespace

Motivation
The call graph producer contained all the functionalities (e.g. kafka processes, call graph generation processes) in a single file, making it hard to comprehend.
It also contained a call graph format conversion mechanism which was redundant after the merge of this pull request.
Finally, up until now, the process of downloading, unzipping, and generating the call graph of a pypi coordinate was a utility only feasible in a kafka production environment, meaning that there was no  standalone tool enabling the automatic process of a a signle PyPI coordinate.
Testing
Tested the changes both locally, in docker and also by using the pycg-producer library through pip

Hello @vitsalis, thanks for the immediate response and for all the insightful comments!
I tried to address all the comments.
Please let me know if anything needs to be fixed or improved!

LGTM

Thanks! I am merging.


User description for ndenys650 added

Description:
In this Pull Request we have done the following additions/edits for the code:
Note: adding my user description to participants.
#1 referenced!

Are there any updates or should we close this PR as spam?

spam

my bad guys. I didn't see that this had comments till today. keep up the hard work.


Translate manage-resources/memory-default-namespace.md into Korean

This is a Feature Request
What would you like to be added
Translate tasks/administer-cluster/manage-resources/memory-default-namespace.md into Korean.
Why is this needed
There is no document of tasks/administer-cluster/manage-resources/memory-default-namespace.md which translated into Korean.
Comments
Page to translate: https://kubernetes.io/docs/tasks/administer-cluster/manage-resources/memory-default-namespace/
/language ko

/assign


docs fix spelling issues

Hey !
I fixed several spelling issues.
Br, futreall.

I'm afraid I'm not a maintainer of this project. Just made a small contribution years ago.


Send tab: scan QR from screen and/or image

The scan function currently allows scanning the transaction details from a connected camera for quick input.
However, when there is no camera connected, the function does not work, and laptop users with a built-in camera can only scan from their phone, paper, or some other surface.
I think that for online shopping, it would be useful to be able to scan the code from the screen, for when it is displayed in a web browser, or from an image file without opening it in an image viewer.
Extending the scan feature like this would benefit desktop and laptop users too.

You can copy a QR code into the 'Pay to' field on the Send tab and it will auto-fill the details.
I'll have to check if scanning the screen can be implemented reliably cross-platform.

Oh, thats pretty useful! Thanks for letting me know. I see it can process monero: protocol URLs.
Now I also see it is mentioned in the built-in docs. I think it would be worth to consider making this information more visible, e.g. with an information button or popup near the "Pay to" label. I have just discovered that label is clickable, maybe the short description could be extended with "or paste a QR code".
The Monero GUI has a "Grab QR code from screen" button above the address field, maybe their approach can be reused here.

I dont think it would be an extension of permissions. Any process can do that, cant it?
Unless you are thinking about Flatpak and such on linux. Or maybe Sandboxie on windows, but I'm not sure how does it work there, probably not with a permission dialog though.

I'm going to mark this as 'not planned', because there are too many environments in which this won't work as expected (without requiring additional permissions): Linux under Wayland, Flatpak, sandboxes, Qubes, and probably macOS.
On Windows, applications can request to be excluded from a screen capture (e.g. KeePassXC on Windows). Likewise, DRM-enabled applications will not show up on screenshots. However improbable, if the QR code is present here we can't give the user feedback on why no QR code was found. I'm sure there are more edge cases where this could cause frustration.
I will keep this issue open until the ability to paste QR codes in the 'Pay To' field is better documented / more visible.


Fix "RLE" compression with big endian architectures

This was missed in #1831. The RLE methods compare a string of bytes directly with itself to directly derive a simple run length encoding. They use similar but not identical methods to compare256. This needs a similar endianness check at compile time to know which compare bit count to use (leading or trailing).

Summary by CodeRabbit

New Features

Introduced a new header file for enhanced functionality in comparing 256-byte arrays.
Added multiple functions for optimized byte and integer comparisons, supporting different data alignments and sizes.

CI errors (Ubuntu GCC AARCH64 No NEON UBSAN):
76: /home/runner/work/zlib-ng/zlib-ng/arch/arm/crc32_acle.c:52:13: runtime error: load of misaligned address 0x005502d11024 for type 'const uint64_t', which requires 8 byte alignment
76: 0x005502d11024: note: pointer points here
76:   65 0a 6f 74 68 65 72 20  68 61 6e 64 2c 20 73 75  63 68 20 62 65 61 75 74  79 20 77 6f 75 6c 64 20
76:               ^
76:     #0 0x55000be4c4 in crc32_acle /home/runner/work/zlib-ng/zlib-ng/arch/arm/crc32_acle.c:52
76:     #1 0x55000d8aec in crc32_fold_copy_c /home/runner/work/zlib-ng/zlib-ng/arch/generic/crc32_fold_c.c:16
76:     #2 0x5500069218 in zng_read_buf /home/runner/work/zlib-ng/zlib-ng/deflate.c:1201
76:     #3 0x55000825b4 in deflate_stored /home/runner/work/zlib-ng/zlib-ng/deflate_stored.c:160
76:     #4 0x5500060ecc in zng_deflate /home/runner/work/zlib-ng/zlib-ng/deflate.c:1040
76:     #5 0x5500054764 in gz_comp /home/runner/work/zlib-ng/zlib-ng/gzwrite.c:125
76:     #6 0x5500055ab8 in gz_write /home/runner/work/zlib-ng/zlib-ng/gzwrite.c:207
76:     #7 0x5500055f10 in zng_gzwrite /home/runner/work/zlib-ng/zlib-ng/gzwrite.c:254
76:     #8 0x5500048e20 in gz_compress /home/runner/work/zlib-ng/zlib-ng/test/minigzip.c:144
76:     #9 0x5500047ac0 in main /home/runner/work/zlib-ng/zlib-ng/test/minigzip.c:330
76:     #10 0x55028473f8  (/lib/libc.so.6+0x273f8)
76:     #11 0x55028474c8 in __libc_start_main (/lib/libc.so.6+0x274c8)
76:     #12 0x550004896c in _start (/home/runner/work/zlib-ng/zlib-ng/minigzip+0x4896c)
76:
76: qemu: uncaught target signal 6 (Aborted) - core dumped
74: /home/runner/work/zlib-ng/zlib-ng/arch/arm/crc32_acle.c:52:13: runtime error: load of misaligned address 0x005502d39a1c for type 'const uint64_t', which requires 8 byte alignment
74: 0x005502d39a1c: note: pointer points here
74:   61 74 2e 20 4c 69 64 64  79 20 77 61 73 20 61 73  6b 69 6e 67 0a 71 75 65  73 74 69 6f 6e 73 20 61
74:               ^
73: -- Decompress qemu-aarch64;-L;/usr/aarch64-linux-gnu/;/home/runner/work/zlib-ng/zlib-ng/minigzip;-d;-c
73: --   Input: /home/runner/work/zlib-ng/zlib-ng/test/Testing/Temporary/minigzip-book1-R-0ThCpV.gz
73: --   Output: /home/runner/work/zlib-ng/zlib-ng/test/Testing/Temporary/minigzip-book1-R-0ThCpV
74:     #0 0x55000be4c4 in crc32_acle /home/runner/work/zlib-ng/zlib-ng/arch/arm/crc32_acle.c:52
74:     #1 0x55000d8aec in crc32_fold_copy_c /home/runner/work/zlib-ng/zlib-ng/arch/generic/crc32_fold_c.c:16
74:     #2 0x5500085a48 in inf_chksum_cpy /home/runner/work/zlib-ng/zlib-ng/inflate.c:31
74:     #3 0x5500085a48 in updatewindow /home/runner/work/zlib-ng/zlib-ng/inflate.c:343
74:     #4 0x550008abe4 in zng_inflate /home/runner/work/zlib-ng/zlib-ng/inflate.c:1183
74:     #5 0x550004e404 in gz_decomp /home/runner/work/zlib-ng/zlib-ng/gzread.c:178
74:     #6 0x550004fd74 in gz_fetch /home/runner/work/zlib-ng/zlib-ng/gzread.c:231
74:     #7 0x5500050ab4 in gz_read /home/runner/work/zlib-ng/zlib-ng/gzread.c:310
74:     #8 0x550005101c in zng_gzread /home/runner/work/zlib-ng/zlib-ng/gzread.c:366
74:     #9 0x5500048c50 in gz_uncompress /home/runner/work/zlib-ng/zlib-ng/test/minigzip.c:161
74:     #10 0x55000479cc in main /home/runner/work/zlib-ng/zlib-ng/test/minigzip.c:326
74:     #11 0x55028473f8  (/lib/libc.so.6+0x273f8)
74:     #12 0x55028474c8 in __libc_start_main (/lib/libc.so.6+0x274c8)
74:     #13 0x550004896c in _start (/home/runner/work/zlib-ng/zlib-ng/minigzip+0x4896c)
74:
74: qemu: uncaught target signal 6 (Aborted) - core dumped

Yes, those are not new, they were introduced in a PR that re-enabled the alignment sanitizer.  A subsequent PR is likely to follow to fix that one, but it's unrelated to this.


Log handler and Loki application plugins

This pull request adds the log handler and loki application plugins.
I'll add tests for it this or next week.

I resolved everything you pointed out. I have no idea, how I overlooked all the debugging statements :smile:. I'll close this PR, rebase to the current infrawatch sg-core master and create a new PR there.


Add PostGIS 2.4 to PostgreSQL images

For PostGIS support in https://github.com/debezium/debezium/pull/374

@rcoup Could you prefix the commit message with "DBZ-507 ..."? Thx!

@gunnarmorling done.

Hmm, do we want to add postgis by default or will we have two images one with and one without - see https://issues.jboss.org/browse/DBZ-445

Surely nobody is using the "Debezium" Postgres image in the real world to run their actual database?
And if they are (there's always one!) then TBH they probably don't care about 200MB — it's not like this image will be pulled onto a cluster 10x a day like an application image would be...


Infrastructure cleanup

This PR is meant to address some challenges of infrastructural nature and meant to clean up a few things and update a few of our workflows.
Goals

[x] Make the flake pass all checks of nix flake check
[x] Provide development tools to write work with the overlay in the devShells output attribute, including direnv integration
[ ] New and stable mechanism to find changed packages
[ ] Build changed packages via GitHub actions
[ ] Push build artifacts from the GitHub actions to Cachix
[ ] Integrate on-site GitHub runner with more powerful hardware and local cache

Open Questions

On-site GitHub runners could build and test proprietary packages we would have access to, provided we use the srcurl mechanism and the GitHub runner machine has access to that respective host. In our setup this should be possible without problems. Our GitHub runner machine would be in the same subnet as the file server. However, I am not entirely sure if we should do this. It would require some protection mechanism of who is allowed to trigger pipelines.
Currently, we are using the null overlay to disable some proprietary packages in the flake. Is this strictly necessary? I think it does no harm exposing common unfree packages. To avoid their tests failing I would rather filter the tests?

A few comments here:

Make the flake pass all checks of nix flake check: that may require to move the package set to legacyPackages as packages does not allow for subsets.
devShells output attribute, including direnv integration: direnv is a nice-to-have add on, but I would not make it mandatory.
Build changed packages via GitHub actions: the mechanism to find changed packages via the GitHub action is currently broken. This is, btw. not as trivial as I thought. OfBorg puts more effort in to figure out what exactly has changed.
Push build artifacts from the GitHub actions to Cachix: I would try to save space here instead and either open another Cachix account for exclusively the GitHub runner or rather provide a local cache.

Make the flake pass all checks of nix flake check: that may require to move the package set to legacyPackages as packages does not allow for subsets.

Yeah, the python package set is not exported in packages, that's true. However, I would argue that this is fine. Python packages used as executables are exported via toPythonApplication in the qchem set so that they are accessible. If a python package is meant to be used as a library instead, the better way is to access it via the overlay function so that the python versions don't become a mess. The current state already passes nix flake check.

devShells output attribute, including direnv integration: direnv is a nice-to-have add on, but I would not make it mandatory.

It is not. If direnv is not installed it won't matter. If it is installed and not to be used it is enough to just not run direnv allow.

Build changed packages via GitHub actions: the mechanism to find changed packages via the GitHub action is currently broken. This is, btw. not as trivial as I thought. OfBorg puts more effort in to figure out what exactly has changed.

Yep, I've also noticed. I think I can imagine another solution. I will try it out soonish, I hope. I've also hat a look at nixpkgs update to save us from all manual package upgrades. Unfortunately it quite tied to the nixpkgs repo and also quite fancy Haskell with effect systems and that stuff ... :grimacing:

Push build artifacts from the GitHub actions to Cachix: I would try to save space here instead and either open another Cachix account for exclusively the GitHub runner or rather provide a local cache.

I guess this point has to aspects: pushing into the current cachix for "end-users" which we could restrict to commits on master and the pinned nixpkgs. And the second one is accelerating the builds for local runners. Here I agree, I would also prefer a local cache.

I guess this point has to aspects: pushing into the current cachix for "end-users" which we could restrict to commits on master and the pinned nixpkgs. And the second one is accelerating the builds for local runners. Here I agree, I would also prefer a local cache.

Hydra does that already for the pinned master branch and the release branches. We can leave it like that. I think the GitHub runners are a good option to handle the PRs.

I am really struggling with the GitHub actions. They are lacking the feature to create dependent child pipelines. In our case I would have created a stage 1 pipeline, that figures our which packages have changed. The stage 1 pipeline would then create a number of stage 2 pipelines, that build each package. Unfortunately it is extremely cumbersome to achieve something like this with GitHub actions. However, I am regularly using this in GitLab CI and would just register connect a  GitLab CI-repo with this repo. Then the GitLab-CI would provide the results via a Webhook, similar to what ofborg is doing.

I am really struggling with the GitHub actions. They are lacking the feature to create dependent child pipelines. In our case I would have created a stage 1 pipeline, that figures our which packages have changed. The stage 1 pipeline would then create a number of stage 2 pipelines, that build each package. Unfortunately it is extremely cumbersome to achieve something like this with GitHub actions. However, I am regularly using this in GitLab CI and would just connect a GitLab CI-repo with this repo. Then the GitLab-CI would provide the results via a Webhook, similar to what ofborg is doing.

I am not familiar with the GitLab-CI. I think in GitHub actions, each action is completely isolated. The simplest solution is probably to do both steps in one action? I  am not sure how to share information between actions (but there should be a way to achieve this)
Did you manage to find out the packages that changed?

I am not sure how to share information between actions (but there should be a way to achieve this)

I think there is, but this is not even what I am missing. I want a dynamic number of pipelines in the second stage. But yes, we can also put everything into one giant monolithic pipeline.

Did you manage to find out the packages that changed?

No, not yet, unfortunately. The idea is quite simple and robust, but I am struggling with implementing it and always end in an infinite recursion, that I do not understand. The idea is to create a nix expression in a file getDiff.nix that roughly does the following:
basePath: newPath:

let
  flakeTools = ... # import the flake-compat stuff, that provides lib functions to create package sets from flake.nix and flake.lock
  basePkgs = (flakeTools { src = basePath; }).defaultNix.packages.x86_64-linux;

Haha, got it! :blush: :partying_face:
updPath: basePath:

let
  releaseOpts = {
    config = { };
    allowUnfree = true;
    preOverlays = [ ];
    postOverlays = [ ];
    buildVariants = false;
    pin = true;
  };

  lib = (import "${basePath}/nixpkgs-pin.nix" { }).lib;

  # Get packages from the updated and base versions
  updPkgs = (import "${updPath}/release.nix" releaseOpts).qchem;
  basPkgs = (import "${basePath}/release.nix" releaseOpts).qchem;

  # We are not interested in the realised packages, the derivation paths are
  # enough and save a lot of time.
  updDerivs = with lib.attrsets; mapAttrs (_: v: v.drvPath) (filterAttrs (_: v: isDerivation v) updPkgs);
  basDerivs = with lib.attrsets; mapAttrs (_: v: v.drvPath) (filterAttrs (_: v: isDerivation v) basPkgs);

  # Ignored outputs, to be removed additionally from the attribute set.
  auxIgnore = [
    "channel"
    "nixexpr"
  ];

  # Recursive, flattened difference of attribute sets.
  recAttrSetDiff = l: r: lib.attrsets.filterAttrs
       (lK: lV: !(builtins.elem lK auxIgnore) && (if lib.hasAttr lK r
         then lV != r."${lK}"
         else true)
       )
       l
      ;

  # Changed derivations in update
  changedDerivs = recAttrSetDiff updDerivs basDerivs;

  # For CI purposes we only require the changed attribute keys.
in builtins.attrNames changedDerivs

And to be called as nix eval --impure --expr 'import ./.github/workflows/changedPaths.nix $PATH_TO_PR $PATH_TO_MASTER.

OK, done with what I wanted to do, except the registration of our custom runner. However, for the actual code changes that does not matter for now.
The rebuilds seem to work nicely as far as I can tell, for an example see here: https://github.com/sheepforce/NixOS-QChem/actions/runs/4354792813
However, the mechanism will only work once this PR is merged, as the workflow requires some of my changes here.

Hm, a problem for the checkout is a cross-fork PR, I will try to figure out how to fix.

So the rebuilds / Pinned legitimately fails as the CI requires my changes to be in the PR target branch (master).
rebuilds / Master and rebuilds / Unstable also fail for the same reason, but would also still fail due to #262 .
nix flake check is interesting, however. This one works flawlessly on my NixOS machine and I suspect the version difference (2.11 vs 2.14) to be responsible. Do you have more insight, @markuskowa ?

I have rebased onto staging (and target staging as base). However, the stdenv fix is still making trouble;
$ nix flake check
warning: Using saved setting for 'allow-import-from-derivation = true' from ~/.local/share/nix/trusted-settings.json.
warning: Using saved setting for 'extra-substituters = https://nix-qchem.cachix.org' from ~/.local/share/nix/trusted-settings.json.
error: The ‘env’ attribute set cannot contain any attributes passed to derivation. The following attributes are overlapping: NIX_CFLAGS_COMPILE
(use '--show-trace' to show detailed location information)

@markuskowa Here we are. Everything should work now, the checks even work now without being in the base branch of the PR, nixpkgs-pin.nix is untouched and thus still working. Please have a look :)


Is CentOS 7.3 / 7.4 supported?

I'm having difficult time accessing whether rkt actually supports CentOS 7.3 / 7.4.
According to https://coreos.com/rkt/docs/latest/distributions.html#centos, the support is not production ready. But that snippets links to repo with only rkt 1.17 / 1.21 (whereas rkt is now on 1.28.1 / 1.29.0) and references https://github.com/rkt/rkt/issues/1305 (which is 2 years old and initially was filed for CentOs 6.x).
I've successfully installed rkt 1.28.1 on CentOS 7.4 with overlay fs and things seems to work (note, no k8, just plain old rkt). However, I'm not certain whether I should push ahead and roll rkt to production systems.
CentOS 7.4 still comes with systemd 219 (219-42.el7_4.1) and I gather from other issues that 220 is preferred.
[update: spelling]

If I recall correctly, what's not supported is the Centos 7.x package, because for distro packages we recommend the host flavor, which requires systemd >=v220 on the host.
However, downloading a rkt release should work fine because rkt releases use the coreos flavor. This flavor doesn't depend on the systemd version installed on the host.

fwiw, we're running rkt 1.27 on CentOS 7.4 in production using the rkt package in the k8s repo. works great!


Revert "Remove .report substring from rule_selector used in v2 content endpoints"

Reverts RedHatInsights/insights-results-smart-proxy#865
Not needed in the end

Codecov Report

Merging #867 (05ed49a) into master (52ce2d1) will increase coverage by 0.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #867      +/-   ##
==========================================
+ Coverage   60.02%   60.06%   +0.04%
==========================================
  Files          22       22
  Lines        2957     2955       -2
==========================================
  Hits         1775     1775
+ Misses        986      984       -2
  Partials      196      196

Impacted Files
Coverage Δ

server/utils.go
93.33% <ø> (-0.79%)
:arrow_down:

server/handlers_v2.go
63.46% <100.00%> (ø)

server/router_utils.go
71.64% <100.00%> (ø)

server/server.go
58.68% <100.00%> (ø)

content/content.go
82.17% <0.00%> (+0.86%)
: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 52ce2d1...05ed49a. Read the comment docs.


IDVA6-1433 get logged in user details middleware update

Link to Jira
https://companieshouse.atlassian.net/browse/IDVA6-1433
We have a middleware function that retrieves ACSP member logged in user details.
Its saves these details to the session so that individual pages do not need to request them.
The PR updates this so that we only fetch the member details on /authorised-agent requests, rather than all requests.

CI: No security warnings found


Proper word wrap intents. fix for #11633

fixes https://github.com/adobe/brackets/issues/11633
@petetnt @swmitra @wesleifreitas

Tried it out against current master, confirmed to fix #11633. Implementation looks solid. LGTM

Thanks @petetnt for reviewing.

Verified the fix. Changes look good. Merging.


It seems that cross-env NODE_ENV=something doesn't work

Hi,
i use cross-env on my mac.
I've tried it with node v6.3.1 and v5.12.0, but it seems that it doesn't work well.
After launching
$ ./node_modules/.bin/cross-env NODE_ENV=development

and
$ printenv

i can't see NODE_ENV.
But, if i try to set it with
$ export NODE_ENV=development

works fine.
Maybe there are some breaking changes?

cross-env only adds the environment variable during the process that it spawns when it runs your command. So you'd have to do:
$ ./node_modules/.bin/cross-env NODE_ENV=development printenv

It's unlikely that corss-env will change in this regard.

That’s not working even in the same process:
cross-env NODE_ENV=production node ./dist/main.js

However, this works:
export NODE_ENV=production node ./dist/main.js


⚠ 2 Minutes de génie (staging) has degraded performance

In d673193, 2 Minutes de génie (staging) (https://2mdgstaging.gitlab.io/) experienced degraded performance:

HTTP code: 200
Response time: 3035 ms

Resolved: 2 Minutes de génie (staging) performance has improved in 373bb11.


Plugin prometheus: plugin is not initialized

Summary
i failed to use Prometheus plugin after Installing Kong, i'm not sure if this is a bug yet
http://<IP_ADDRESS>:8001/metrics
{"message":"An unexpected error occurred"}

Steps To Reproduce

docker-compose.yml

  kong:
    container_name: "kong"
    ports:
      - "8000:8000"
      - "8443:8443"
      - "8001:8001"
      - "8444:8444"
    environment:
      - KONG_DATABASE=postgres
      - KONG_PG_HOST=kong-database
      - KONG_CASSANDRA_CONTACT_POINTS=kong-database
      - KONG_ADMIN_ACCESS_LOG=/dev/stdout
      - KONG_PROXY_ERROR_LOG=/dev/stderr
      - KONG_ADMIN_ERROR_LOG=/dev/stderr
      - KONG_ADMIN_LISTEN=<IP_ADDRESS>:8001, <IP_ADDRESS>:8444 ssl
    restart: always
    image: kong:1.3rc1-centos

docker-compose up
then i started prometheus plugin in konga

Additional Details & Logs

Kong version ($ kong version) kong:1.3rc1-centos
Kong error logs (<KONG_PREFIX>/logs/error.log) docker logs -f ca0b7f1ad871

2020/06/03 11:27:07 [error] 40#0: *39130 [kong] exporter.lua:88 prometheus: plugin is not initialized, please make sure  'prometheus_metrics' shared dict is present in nginx template, client: <IP_ADDRESS>, server: kong_admin, request: "GET /metrics HTTP/1.1", host: "<IP_ADDRESS>:8001"
2020/06/03 11:27:07 [warn] 40#0: *39130 using uninitialized "kong_proxy_mode" variable, client: <IP_ADDRESS>, server: kong_admin, request: "GET /metrics HTTP/1.1", host: "<IP_ADDRESS>:8001"
<IP_ADDRESS> - - [03/Jun/2020:11:27:07 +0800] "GET /metrics HTTP/1.1" 500 42 "-" "Prometheus/2.18.1"
2020/06/03 11:27:12 [error] 40#0: *39130 [kong] exporter.lua:88 prometheus: plugin is not initialized, please make sure  'prometheus_metrics' shared dict is present in nginx template, client: <IP_ADDRESS>, server: kong_admin, request: "GET /metrics HTTP/1.1", host: "<IP_ADDRESS>:8001"
2020/06/03 11:27:12 [warn] 40#0: *39130 using uninitialized "kong_proxy_mode" variable, client: <IP_ADDRESS>, server: kong_admin, request: "GET /metrics HTTP/1.1", host: "<IP_ADDRESS>:8001"
<IP_ADDRESS> - - [03/Jun/2020:11:27:12 +0800] "GET /metrics HTTP/1.1" 500 42 "-" "Prometheus/2.18.1"
2020/06/03 11:27:17 [error] 40#0: *39130 [kong] exporter.lua:88 prometheus: plugin is not initialized, please make sure  'prometheus_metrics' shared dict is present in nginx template, client: <IP_ADDRESS>, server: kong_admin, request: "GET /metrics HTTP/1.1", host: "<IP_ADDRESS>:8001"
2020/06/03 11:27:17 [warn] 40#0: *39130 using uninitialized "kong_proxy_mode" variable, client: <IP_ADDRESS>, server: kong_admin, request: "GET /metrics HTTP/1.1", host: "<IP_ADDRESS>:8001"

image: kong:1.3rc1-centos

Can you please use the final 1.3 release image instead of the RC?
Also, please upgrade to a newer version of Kong.

Is this because of the version?

@hbagdi , not the same problem, but using the image kong/kong:2.1.0alpha.1-centos-7 I had to tweak the prometheus.lua to make it work.
# fix: module 'prometheus_resty_counter' not found:No LuaRocks module found for prometheus_resty_counter
sed -i 's/require("prometheus_resty_counter")/require("resty.counter")/g' /usr/local/share/lua/5.1/kong/plugins/prometheus/prometheus.lua

@hbagdi , not the same problem, but using the image kong/kong:2.1.0alpha.1-centos-7 I had to tweak the prometheus.lua to make it work.

@fffonion could you take a look at this problem?
@carnei-ro Please open a new Github issue for this. Thanks.

Is this because of the version?

@xichengliudui It could be but I'm not sure. You should anyways not be using an RC version for which a generally available release already exists.

@xichengliudui 1.3-centos version works for me, there might be a bug in the RC release. As @hbagdi suggested prefer to use GA release if available.
@carnei-ro We use a package.loaded to redirect the resty counter module as upstream choose to vendor the resty counter library. If you are using prometheus.lua directly you might want to add that before require.

@fffonion I'm not using the prometheus.lua directly. I'm exposing a new port:
server {
    server_name kong_prometheus_exporter;
    listen <IP_ADDRESS>:9542;
    location / {
    default_type text/plain;
        content_by_lua_block {
            local prometheus = require "kong.plugins.prometheus.exporter"
            prometheus:collect()
        }
    }
    location /nginx_status {
        internal;
        access_log off;
        stub_status;
    }
}

@carnei-ro I was able to use the above nginx conf with 2.1.0alpha-centos-7 docker image without issue. Could you share the plugins enabled and kong configuration changed if there's any?

@fffonion there was, indeed, a custom plugin using the prometheus.lua directly. I'm sorry about that. Thanks for the tip.

thank you for your, i will close this problem and I can open it if necessary

meet the same error,  use server blocks to add prometheus.

@fffonion I'm not using the prometheus.lua directly. I'm exposing a new port:
server {
    server_name kong_prometheus_exporter;
    listen <IP_ADDRESS>:9542;
    location / {
    default_type text/plain;
        content_by_lua_block {
            local prometheus = require "kong.plugins.prometheus.exporter"
            prometheus:collect()
        }
    }
    location /nginx_status {
        internal;
        access_log off;
        stub_status;
    }
}

i have append KONG_PLUGINS: xxx,prometheus to fix inject  default shared dict lua_shared_dict prometheus_metrics 5m;


Segfault

Clicked on Clock (top tray, on right end), trying to get "exec:xterm ... -e cal -3" working (miss that drop-down calendar from Mint). JWM crashed twice. Here's from dmesg:
[ 3990.315970] jwm[564]: segfault at 4 ip 004d4097 sp bfa4d268 error 4 in jwm[4be000+3d000]
[ 3990.315986] Code: 7c 24 2c 89 54 24 04 89 5c 24 0c 65 a1 14 00 00 00 89 84 24 ec 00 00 00 31 c0 b8 ff ff ff ff 89 7c 24 14 83 ec 04 f3 ab 6a 00  75 04 ff 75 00 e8 1e ff ff ff 8b 55 04 89 44 24 2c 83 c4 10 8b
[ 4147.476135] jwm[18606]: segfault at 4 ip 00424097 sp bfe9f268 error 4 in jwm[40e000+3d000]
[ 4147.476151] Code: 7c 24 2c 89 54 24 04 89 5c 24 0c 65 a1 14 00 00 00 89 84 24 ec 00 00 00 31 c0 b8 ff ff ff ff 89 7c 24 14 83 ec 04 f3 ab 6a 00  75 04 ff 75 00 e8 1e ff ff ff 8b 55 04 89 44 24 2c 83 c4 10 8b

The crashing of JWM does not reproduce. I use Arch Linux and last building of JWM.


ts: fix memleaks caused by TS_VERIFY_CTX_set_imprint

CLA：trivial

OK for 1.1.1 as well. @paulidale do you agree?

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

I am OK with CLA: trivial here. @paulidale do you agree?


Fix FCirc download template

Summary Change Description
Fix #268, add missing tab character in FCirc download template
Affected Issue Numbers

Resolves #268

Code Review Notes
Ideally, we would add some test files for the download pages, but it seems better to get the fix in quickly.
Checklist

[x] All issue requirements satisfied (or no linked issues)
[x] Linting passes.
[x] Migrations created & committed (or no model changes)
[ ] Tests implemented (or no code changes)
[x] All tests pass

Just a quick ping to @fkang-pu and @jcmatese to see if we can get this merged. I believe it's just a quick bugfix.


Support for more image formats for wallpapers

Currently only .png's are supported because of this. It would be nice to be able to use .jpg's for wallpapers, but I don't know enough about this code to implement it.

Probably involves using MagickWand or something. Or we could just straight up add support for more kinds of images.

Cairo has support to create surfaces from pixel data, see cairo_image_surface_create_for_data(): http://cairographics.org/manual/cairo-Image-Surfaces.html
So adding other formats shouldn't be harder than to use some library to convert images to byte data. ImageMagick libs would probably be a great candidate considering the wide array of formats it supports.

The most common solution is to use librsvg for svg images. With that you already pull gdk-pixbuf2, so use that to load other formats. My installation supports ani, bmp, gif, icns, ico, jasper (jpeg-2000), jpeg, pnm, qtif, tga, tiff, xbm, and xpm

#296 has been merged.


:FuzzyBuffers - Can it work like :ls ?

Thank you for creating this plugin.
Is it possible for :FuzzyBuffers to offer the same listing as :ls please?

I found the line in question:
    var buf_data = getbufinfo({'buflisted': 1, 'bufloaded': 1})

Changing 'bufloaded' from 1 to 0 got me what I wanted.

Thank you for the help. Could you give me an example when buffers filtered by "{'buflisted': 1, 'bufloaded': 1}" will get different result than :ls command?

Thanks for the reply.
Yes, my :ls command seems to include buffers from the MRU list, as well as those that are currently open. :FuzzyBuffers includes only buffers that are opened in splits or tabs.
Perhaps that's correct behaviour though? I wonder if I was just mistaken in my understanding of what :FuzzyBuffers should do?
I may undo my change to bufloaded and assign <leader>ft to :FuzzyMRU.

Yes, in my design, FuzzyBuffers is supposed to search the buffers that you have opened in one edit. I will update the readme to make it more clear.


Update smartsDepict.ipynb for SMARFF with angle energies

Updated ipython notebook with angle energies from John Chodera, updated so it will still run when applied to non-angle terms.
Also made a minor fix to the README.txt for SMIRFF prototype at the same time.

Weird---I don't see any energies in the output.  Does this mean it is no longer working?

Er, maybe I forgot and left it so it's set to display a torsion. Lemme
check.
On Wed, May 11, 2016 at 2:09 PM, John Chodera<EMAIL_ADDRESS>wrote:

Weird---I don't see any energies in the output. Does this mean it is no
longer working?
—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
https://github.com/open-forcefield-group/open-forcefield-data/pull/5#issuecomment-218590974

--
David Mobley
<EMAIL_ADDRESS>949-385-2436

Sorry about that. Just uncomment the one line and comment out the other:

#Smarts = '[#6X4]-[#6X4]-[#8X2]'  #Angle query
Smarts = '[#6X4]-[#6X4]-[#6X4]-[#6X4]' #Torsional query

(Your code wouldn't run if one specified a torsion, so I fixed it so it would run - but not print any energies - until I can do #6 )

Thanks!
Are we really sure this belongs in open-forcefield-data?  What about open-forcefield-toymodels?

I'm fine with putting it somewhere like that, yes.
On Wed, May 11, 2016 at 2:14 PM, John Chodera<EMAIL_ADDRESS>wrote:

Thanks!
Are we really sure this belongs in open-forcefield-data? What about
open-forcefield-toymodels?
—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
https://github.com/open-forcefield-group/open-forcefield-data/pull/5#issuecomment-218592379

--
David Mobley
<EMAIL_ADDRESS>949-385-2436


How to put some codes into HTML  tags?

I’m creating form via C# and Nancy and not using extra .html files. It creates html codes via toHTML() method written by me. After obtaining the html code as string, I use return Response.AsText(form.toHtml(), “text/html”);. When I investigate the html code on a browser, the codes are put into .. tags. What if I need to put the following?
<meta charset=“utf-8”>
  <title>test</title>
  <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
  <link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/bootstrap/4.3.1/css/bootstrap.min.css">
  <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css">

How can I put them into  tags?

Nancy will output whatever you tell it to output, so either its a bug in your toHtml method, you're probably not outputting valid HTML with head tags, so the browser is trying its best to interpret the content and wrapping it in a body tag.

So, isn’t there any Nancy-way to put my strings into  tags other than my toHTML() method?

I'm not entirely sure what you're trying to achieve, but what you're doing there is returning an entire html document formed from whatever you toHTML method is returning. If you're wanting to combine that with other html/templates you should have a look at view engines, if you're wanting to update content that's already in the browser via ajax then that's nothing really to do with nancy.


Update Composer dependencies (2021-04-10-00-02)

Visual regression test passed!
View the visual regression test report


Having issues rendering CSS

I replaced the included app.css file's content with my own CSS rules but they don't seem be to taking effect and I'm not sure why. Any pointers on this issue?

Here's the error message I'm getting:
Module build failed: CssSyntaxError: /Users/seanchen/karma/admin-refactor/node_modules/style-loader/index.js!/Users/seanchen/karma/admin-refactor/node_modules/css-loader/index.js!/Users/seanchen/karma/admin-refactor/app/app.css:1:4: Unknown word```

Really not sure how to get my CSS to render.

Can you show your css here?
Just like the message you got, I thought It cause by your css or css-loader setting.
/Users/seanchen/karma/admin-refactor/app/app.css:1:4: Unknown word

I'm loading a short custom css file and a minified css file. The minified file isn't loading. Is there a setting in webpack that needs to be changed to minified css files?

Nothing different between web and electron in the way webpack treating css file. You can try to write some own rules for css.

@seanchen1991 Webpack configs was simplified in the v0.5 release. Have you figured out how to modify your loader config for css now?

Yea I figured it out. Thanks.

@seanchen1991 can you post what you did to fix this?


Overlapping on the screen [bottom]

It made a nice game, but when I turn on dark mode I can see the page is overlapping on the screen
see in the bottom side
I would like to suggest you some ideas for this project people can attract on your project
-Make it user friendly
-Add option of symbols so that user can choose X or O.
-Add congratulations on winning with popup.
-Add animation on actions
Level:
This issue can be considered Level 2 or 3 under the GSSOC guidelines, as it involves design and implementation.
Thank you for considering this enhancement! I believe it will significantly improve the overall quality of the Tic Tac Toe project. Looking forward to your thoughts!
Please add labels hacktoberfest, gssoc

I helped


User Avatar URL generation is messed up

When a user is created if they don't have an avatar url, passport returns a link like this that has null in it. https://cdn.discordapp.com/avatars/715269732500111410/null.png?size=2048
Idk how to fix this. passport should really have a fix. but idk if it is even passport. ig we could check if the avatar url returned from passport contains null and if it does set it to the default avatar link that u found.

ok

Fixed by @Maxisthemoose in Pull request

Y u mention me

Sorry 😥


Use rplight in panda3d/contrib

See https://github.com/panda3d/panda3d/pull/223 and https://github.com/tobspr/RenderPipeline/pull/89
And it requires copying headers and adding dll target to use p3drplight.dll

Not used to customize those.


Allowed memory size of 134217728 bytes exhausted (tried to allocate 155648 bytes)

PHP version: x.y.z (hint: php --version)
7.4
Description
Symfony\Component\Debug\Exception\FatalErrorException
…/vendor/guzzlehttp/psr7/src/Stream.php:80
How to reproduce
?
Possible Solution
?
Additional context
tokenized paging using API

Closing, it was caused by an infinite loop.


Request to Add Sleep Argument for Knife SSH

Hello,
Sometimes when running Knife SSH commands across multiple nodes, we have to have time between when one node executes the command and the next (i.e. a rolling restart).
I'm not sure if this option exists for the "knife ssh" command, but it would be nice to add an argument "-s <time_in_seconds>" so that it 1. Doesn't execute the commands concurrently and 2. waits X amount of seconds in between issuing the command to each node.
Hopefully this makes sense. I don't have a lot of time to work on this now, but this feature would be very valuable. Please let me know if there's an existing way to do this or if I need to clarify anything.
Thank you.

knife ssh -C 1 'do something; sleep 5'?

Ahhh, thanks! That'll do.

On Feb 9, 2016, at 09:19, Lamont Granquist<EMAIL_ADDRESS>wrote:
knife ssh -C 1 'do something; sleep 5'?
—
Reply to this email directly or view it on GitHub.


Fix the ORTQuantizer loading from specific file

The file_name parameter of the ORTQuantizer from_pretrained method is currently discarded when it should be used if given by the users : resulting in errors when quantizing a seq2seq model as done in the current documentation

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Angular UI

I have hit a roadblock with running the current server-side Soy UI when rebuilding this code in a certain private environment.
Overcoming that would possibly require investing time of this project in improving Bazel rules for Soy Java Closure Templates.
One possible alternative could be to entirely ditch all that and restart with an https://angular.io UI... I wonder how muchwork that really is.
@edewit JS/TS here I come... 🤩
@gabrielh @digitalentity FYI

Modern UI, let's go


add some viewmodel-tests

Signed-off-by: Dominik Pysch<EMAIL_ADDRESS>

the viewmodel test branch should be outdated and merged into dev anyway, I changed the base to dev


esp-idf-ci-action doesn't integrate with the rest of the build system (RDT-242)

I'm trying to build a project that uses esp-idf for the primary build. This project additionally uses python and nodejs in order to generate and compress web pages.
I have actions in my build script that install these projects using the official actions, however these are not picked up by the esp-idf project, and the failure is somewhat opaque.
This action should integrate with the rest of the builders, and allow the usage of other steps in the build process.

Hi @xobs,
esp-idf-ci-action runs its own docker container based on https://hub.docker.com/r/espressif/idf image. It cannot access any environment installed on the runner VM directly.
If you need to use additional tools (like nodejs) for your build, you can either install ESP-IDF to your runner machine directly, following https://docs.espressif.com/projects/esp-idf/en/latest/esp32/get-started/linux-macos-setup.html
Something like:
mkdir -p ~/esp
cd ~/esp
git clone --recursive https://github.com/espressif/esp-idf.git
cd ~/esp/esp-idf
./install.sh esp32
. $HOME/esp/esp-idf/export.sh

Another option is to run everything inside espressif/idf docker image and install your tools there.

Thanks. I did end up following your advice and now install ESP-IDF as part of every build: https://github.com/farpatch/farpatch/blob/main/.github/workflows/build-nightly-blackmagic.yml#L52-L55
This does add time to the build. It is a bit surprising that esp-idf has no access to any of the other steps. Perhaps that should be pointed out in the build steps? Or perhaps it's just common knowledge that I wasn't aware of -- different build steps may not have access to the same environment.
Either way, I'll try to arrange future versions of my software so that ESP-IDF doesn't require any external components to build.

It depends on how the action is implemented. If a step uses an action that runs in a docker container, it won't have access to the runner host environment.


Add compilation guide, and spell checking feature

I added spelling checking to the feature request list, see #20.
As I realize the spell checking feature has already been implemented, I built the plugin myself. The process is not easy, so I think it would be helpful to add some guidance.
Also, I'm really looking forward for v0.3 release.

@rudazhan Thanks for doing this! I'm also looking forward to the 0.3 release. In particular for the fixes to spellchecking!


Increase IO buffer sizes from 1024/2048 bytes to 8192

See: https://github.com/romromov/java-io-benchmark

Thank you


Replacing rtm.start in slack plugin

rtm.start is being deprecated and replaced in most cases by rtm.connect, which might require extra api calls to make work like we were using rtm.start. This is someone else's changes that may solve our problem.
https://github.com/litaio/lita-slack/pull/141/files

Saving this for later: several calls were deprecated with the introduction of conversations https://api.slack.com/changelog/2020-01-deprecating-antecedents-to-the-conversations-api


Copyright

Why?

Organization and mold in the symbol. I did two PR as they are in two branch 's.

@cvrebert What do you say?

Meh. We generally stick with ASCII for max compatibility though.

That's right? @cvrebert

@rafaelstz While moving towards the HTML entity is nice, that does not make the icon itself or it's representation ASCII. I'd be hesitant to say that this necessarily addresses the point.

Thanks but no thanks.


MiniMap optimization

As most of the slowdown in editing boils down to the minimap, up until it can be optimized to lightning fast speeds (which it may never be due to font rendering), an "optimization" could be to fake it ala Apple iOS, by turning off updates when they're unlikely to be noticed.

always double-buffer the minimap internally
update it no more than N times per second when typing, editing or selecting text, by updating the minimap buffer not in Paint, but in a timer event
when scrolling on the minimap, bypass the timer

I had used this before when using a second SynEdit as minimap, this ensures that when typing/editing, you do not feel the slowdown of repainting the minimap. About 4 updates per second seemed quite enough when typing.
In Paint, you just arm the minimap repaint timer if it is not armed already, when the timer fires, you paint the minimap, and invalidate the editor (so the minimap update becomes visible).
If the timer is nearing its end and you're doing a Paint, then you can refresh the minimap and disarm the timer directly (this avoids the extra invalidate, and is mostly relevant when doing keyboard stuff like extending a selection, which results in a lot of repaints a couple dozen milliseconds apart).
Ideal but a lot more involved would be to repaint the minimap in a thread, but that would only be worth it with a deferred line renderer (this way only the deferred paint would take place in the thread, and there would be no need to have the whole lines and codefolding stuff be thread safe, you would perform the building of the deferred rendering graph in the main thread)

Hmm, I don't feel any slowdown when typing with visible mini map. Feels exactly the same with or without the mini map. Mini map is also painted only if needed.

I notice it also when extending selection, with minimap on, the selection trails the mouse, with minimap off, the selection follows the mouse with no lag.

I also just noticed that scrolling with the down/up key is lagging at times...

I made a buffer for a minimap. Better or worse?

On the latest code, I do not have any lag anymore, even with FastMM full debug mode active :+1:
That said, I suspect that simply buffering the minimap will not yield the best result, ideal would be to limit the number of times per second it's updated.
Also on the non-scientific test of scrolling wildly (grab the scrollbar and jerk it up down), the CPU usage of BCEditor goes to 100% of one core with minimap on, and about 70% with minimap off, while doing the same with the Delphi XE editor maxes at about 30% of one core - so there is still some room for improvement :)

No doubt, there is a lot of code that can be optimized, refactored. and even removed as obsolete.
For the minimap scrolling I have a few ideas... there's also no need to paint all the lines over and over again. I will tackle that next.

Closed. Nothing acute here. Minimap scrolling is on my todo list.


feat: add order and type for uuidtobin and binToUuid

I pull request for adding type and add the order param by the way

Released in 1.0.2


Blank White Screen - V0.23.0 on macOS Catalina v10.15.7

Tusk was installed via homebrew. After entering my username for login, I get a blank white screen. I have attempted reloading the page but it just takes me back to login.

Tusk was installed via homebrew. After entering my username for login, I get a blank white screen. I have attempted reloading the page but it just takes me back to login.

Same thing here. I`ve installed, reinstalled, but still not working. =/

Not working on macOS Big Sur version 11.2.
Tusk 0.23.0 (<IP_ADDRESS>0)
Same white screen.

It works with this solution:
https://github.com/klaussinani/tusk/issues/308

Copy of solutions for macOS
brew install npm
git clone https://github.com/klaussinani/tusk.git
cd tusk
git checkout dependabot/npm_and_yarn/electron-9.4.0
npm install electron@latest
npm install
npm start

After running npm start, Tusk starts working, but goes back to white screen when the npm startstops.
It is a workaround, not a valid solution.

Copy of solutions for macOS
brew install npm
git clone https://github.com/klaussinani/tusk.git
cd tusk
git checkout dependabot/npm_and_yarn/electron-9.4.0
npm install electron@latest
npm install
npm start

After running npm start, Tusk starts working, but goes back to white screen when the npm startstops.
It is a workaround, not a valid solution.

Hum...it didn't work for Ubuntu. But anyway, thanks


How many epoch yu are taken for 64*64 image size

Im able to run the program with no error. the convergence measure is displying with no plotting. please help with further.. !
image size = 64 ;
total images  = 20000 ;
epoch=1000;
checkpoint:975;
no of image : 1000 (at once) ;
other parameters are same:

plz help me.. !

Duplicate of https://github.com/artcg/BEGAN/issues/13 which I still havent had time to look at/ see if I can recreate
I recommend using carpedm's repo for now if you are having this problem
https://github.com/carpedm20/BEGAN-tensorflow
since I am unlikely to be able to look at this in the near future


[AMORO-2811][Bug][FLINK]: flink unified catalog doesn't support mixed_hive

Why are the changes needed?

Close #2811 .
Brief change log

create table if not exists xxxx (
....
);

A unifiedCatalog which metastore is hms.

when create a mixed-hive table:

If there is a table in mixed-hive format with the same name, the program can execute correctly with no error thrown and the table is not overwrited;
If there is a table in hive format with the same name, the program will throw an error,
If there is no table with the same name, a mixed-hive table will be created.

when create a iceberg table

if there is a table in iceberg format with the same name, the program can execute correctly with no error ,and the table is not overwrited;
If there is no table with the same name, a iceberg table will be created.

when create a mixed-iceberg table

If there is a table in iceberg format with the same name, the program can execute correctly with no error thrown and the table is not overwrited;
If there is a table in hive format with the same name, the program should thrown an error to indicate the table does exist;
If there is no table with the same name, an iceberg table will be created.

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before making a pull request

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

cc @YesOrNo828  @xieyi888   PTAL.

Codecov Report
Attention: Patch coverage is 0% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 27.47%. Comparing base (a2753b6) to head (c17965a).
Report is 8 commits behind head on master.

Files
Patch %
Lines

...rg/apache/amoro/hive/catalog/MixedHiveCatalog.java
0.00%
1 Missing :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #2814      +/-   ##
============================================
- Coverage     35.95%   27.47%   -8.48%
- Complexity      383     2483    +2100
============================================
  Files            45      360     +315
  Lines          4700    37210   +32510
  Branches        513     5434    +4921
============================================
+ Hits           1690    10225    +8535
- Misses         2842    26026   +23184
- Partials        168      959     +791

Flag
Coverage Δ

trino
27.47% <0.00%> (-8.48%)
:arrow_down:

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Bug: Emissions Import/Export Mismatch

Currently, there is a mismatch between what a user exports out and what is expected when the user imports back the file back in pertaining to the indicator fields.

[ ] Need to update the typing on indicator fields in the JSON schema in the easy-content repo so that the type is a number for indicators and not a string

To test, you an checkout Smith Generating Facility and export data from non logged in view. Then log in and import that same file. You shouldn't see schema validation errors pertaining to the indicator fields needing to be a number or the indicator fields being null.


i18n(zh-cn): Update build-forms-api.mdx

Description (required)
Update build-forms-api.mdx
Related issues & labels (optional)

#8801
Suggested label: i18n

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

zh-cn
recipes/build-forms-api.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Question: Memory allocation for very large element sizes?

In the case of processing video, buffers for high-res video frames (e.g. uncompressed 4K with 12 bits per channel) can be very large. The way I understand Raft is that all FIFOs would need to allocate space for these frames (elements).
A. Would there be a limit to the element size before efficiencies in caching and locality break down e.g. the size of a cache line?
B. If so, if the element was a smaller wrapper object pointing to a global shared pool of pre-allocated frame buffers, I assume this would just shift the problem of caching and locality to the shared pool? And this could be even harder to coordinate if multiple kernels are making use of it...

Would there be a limit to the element size before efficiencies in caching and locality break down >e.g. the size of a cache line?

By definition there is a limit to efficiencies for caching when the element size goes outside of the size of a single cache line. RaftLib by design has three different behavior for object allocation size. I'd like to understand the object structure a bit better to give a definitive answer...For small allocation (fundamental types or data structures less than a cache line size) the allocations are essentially in-place within the FIFO. As long as that FIFO structure between kernels exists at the current size, the data is read in place from producer to consumer. When objects are allocated (in C++, things with constructors vs. P.O.D types) then the constructor is called in-place to set up the structure before the user gets to use it. For items greater than a single cache line, RaftLib uses either the system slab allocator to allocate the large objects then passes around pointers to that object. That way the large allocations can exist across an entire topology vs. just at one FIFO. RaftLib handles passing the pointer from one kernel to the next safely, then discards it when that pointer is no longer in use. Another feature of the large allocation is that RaftLib inserts prefetch hints into the instruction stream for those large objects when they near the head of the queue for the consumer. That way, despite being a pointer, we parallelize as best as possible the memory access to those large objects. We don't do this for things that are less than a cache line size given that most next line pre-fetchers handle the FIFO pattern that's designed in RaftLib very very well (i.e., the follow-on data will always be in the cache for the consumer). This does create some pedantic worst case behavior with false sharing, some architectures do better than others with this.

If so, if the element was a smaller wrapper object pointing to a global shared pool of pre-allocated frame buffers, I assume this would just shift the problem of caching and locality to the shared pool? And this could be even harder to coordinate if multiple kernels are making use of it...

I think I answered this one in the last response. If there's a large frame buffer, RaftLib automatically creates a pool with automated pre-fetch hints that are transparent to the user. The pointer to those pools is passed around transparently and garbage collected when no longer in use. It's entirely transparent to the user when these pools are created, the only way you'll know is by doing sizeof(x) on the type you're allocating. When calling allocate on the port is when this behavior is kicked off. Push should also do it as well, when copying in a large object. I'll double check to make sure that's the case, but I'm pretty sure it is. The idea with keeping the pools managed by RaftLib is that there isn't a way for multiple kernels to step on each other by accessing the same data. However, given that glibc uses a nice slab allocator, the pool of memory is essentially managed by the OS. One thing I need to re-implement is the page management for these pools. Ideally I'd be able to call numa_page_move to create locality for the pool as it moves through the graph, right now first touch in Linux puts it on the NUMA node of first allocation. To fix the current behavior, I'd need to wrap the glibc allocator and use aligned memory...basically, each allocation would need to get a new page no matter how big the allocation or how small.
To get a better idea of how this works, it'd be good to start with the allocation traits header file. This gives the definitions that enable the rest of the templates to decide which type of FIFO to instantiate.
Going from the "outside" to the inside, looking at the fifo.hpp file we get some functions like this one:
   template< class T,
             typename std::enable_if< ext_alloc< T >::value >::type* = nullptr >
   T& peek( raft::signal *signal = nullptr )
   {
      T **ptr( nullptr );
      local_peek( (void**)&ptr, signal );
      return( **ptr );
   }

That have to use the templates here to ensure that the correct pointer type is returned. In this case, if it's an external object that's created with the allocate function (it's created by default in a pool above a certain size. For really big objects, we get this type of construct in the fifo.hpp file since
it's the last layer of object that actually "understands" what the object type is before we just get to bytes and addresses:
   template < class T,
              class ... Args,
              typename std::enable_if< ext_alloc< T >::value >::type* = nullptr >
   T&
   allocate( Args&&... params )
   {
      T **ptr( nullptr );
      /** call blocks till an element is available **/
      local_allocate( (void**) &ptr );
      *ptr = new T( std::forward< Args >( params )... );
      return( **ptr );
   }

Then going to the ringbuffer itself, for the heap implementation, there are actually three distinct variants. You'll see comments like this throughout the file to help you find your way:
/*********************************
 * INLINE CLASS ALLOC STARTS HERE
 *********************************/

template < class T >
class RingBufferBase<
    T,
    Type::Heap,
    typename std::enable_if< inl

If you're curious, for the external pool, the code looks like this:
   virtual void  local_push( void *ptr, const raft::signal &signal )
   {
      for(;;)
      {
         /** data manager is for the ring buffer resizing **/
         (this)->datamanager.enterBuffer( dm::push );
         if( (this)->datamanager.notResizing() )
         {
            if( (this)->space_avail() > 0 )
            {
               break;
            }
         }
         (this)->datamanager.exitBuffer( dm::push );
         if( (this)->write_stats.bec.blocked == 0 )
         {
            (this)->write_stats.bec.blocked = 1;
         }
#if (defined NICE) && (! defined USEQTHREADS)
         std::this_thread::yield();
#if __x86_64
         __asm__ volatile("\
           pause"
           :
           :
           : );
#endif
#endif
#ifdef USEQTHREADS
         qthread_yield();
#endif
      }
      auto * const buff_ptr( (this)->datamanager.get() );
       const size_t write_index( Pointer::val( buff_ptr->write_pt ) );
      if( ptr != nullptr )
      {
          T *item( reinterpret_cast< T* >( ptr ) );
          T * temp( new (
            &buff_ptr->store[ write_index ]
          ) T( *item  ) );
          UNUSED( temp );
          (this)->write_stats.bec.count++;
       }
      buff_ptr->signal[ write_index ]         = signal;
       Pointer::inc( buff_ptr->write_pt );
      if( signal == raft::quit )
      {
         (this)->write_finished = true;
      }
      (this)->datamanager.exitBuffer( dm::push );
   }

Lastly, if we peek an externally allocated object. There's some code that enables prefetch
   /**
    * local_peek() - look at a reference to the head of the
    * ring buffer.  This doesn't remove the item, but it
    * does give the user a chance to take a look at it without
    * removing.
    * @return T&
    */
   virtual void local_peek(  void **ptr, raft::signal *signal )
   {
      for(;;)
      {

         (this)->datamanager.enterBuffer( dm::peek );
         if( (this)->datamanager.notResizing() )
         {
            if( (this)->size() > 0  )
            {
               break;
            }
            else if( (this)->is_invalid() && (this)->size() == 0 )
            {
               throw ClosedPortAccessException(
                  "Accessing closed port with local_peek call, exiting!!" );
            }
         }
         (this)->datamanager.exitBuffer( dm::peek );
#if (defined NICE) && (! defined USEQTHREADS)
         std::this_thread::yield();
#if  __x86_64
         __asm__ volatile("\
           pause"
           :
           :
           : );
#endif
#endif
#ifdef USEQTHREADS
         qthread_yield();
#endif
      }
      auto * const buff_ptr( (this)->datamanager.get() );
      const size_t read_index( Pointer::val( buff_ptr->read_pt ) );
      if( signal != nullptr )
      {
         *signal = buff_ptr->signal[ read_index ];
      }
      //actual pointer
      auto ***real_ptr( reinterpret_cast< T*** >( ptr ) );
      *real_ptr = reinterpret_cast< T** >( &( buff_ptr->store[ read_index ] ) );
      /** prefetch first 1024  bytes **/
      //probably need to optimize this for each arch / # of
      //threads
      raft::prefetch< raft::READ,
                      raft::LOTS,
                      sizeof( T ) < sizeof( std::uintptr_t ) << 7 ?
                      sizeof( T ) : sizeof( std::uintptr_t ) << 7
                      >( **real_ptr );
      (this)->in_peek->insert( reinterpret_cast< ptr_t >( **real_ptr ) );
      return;
      /**
       * exitBuffer() called when recycle is called, can't be sure the
       * reference isn't being used until all outside accesses to it are
       * invalidated from the buffer.
       */
   }

There's two really important things going on here. First, there's a set (in_peek) that operates across each kernel in the run function that implements garbage collection, but that's called from the scheduler so the garbage collection calls are at the right times and can be coordinated with execution.

@vectronic, feel free to close if you're satisfied with the answer.
-J

Thank you so much for the in-depth answer. You've given me a lot to digest and I definitely have a better grasp on things now. Diagram was excellent as well.


ReadMail handling of MultiPart message type

In the ReadMail operator, we handle multi-part messages.  However, we seem to only concatenate the content together, making it hard for downstream operators to distinguish the different parts.
Perhaps we should emit an array of "content" with mime type attached, to mirror how emails are structured.

In v2.0 the ReadMail operator provides a list of content and a list of content types.


Feedback about DROP

Please send response about DROP if you get one.

Thanks for support and response Superman.

First: Thank you for this release its very cool
Tutorial for windows
**-You need to download chromium (extract in your computer)
-Open cmd and navigate to folder bot like a this: cd C:\Users\you-username\Downloads\bot
-type npm install
-type npm start
-put your auth-key
-put commanline for exe chromium like a this:
C:\Users\you-username\Downloads\chrome\chrome.exe
Press enter and done.
FIXES:
**If you get error restart the bot (CTRL+C) and "npm start" again in cmd.

I got a drop a couple days ago after running this bot for  36 hours, thanks chief, got 4 drops on 4 accounts all around the same time using this.

@Relyze This package uses puppeteer-core, so npm should not install chromium by itself

@D3vl0per This sure seems over engineered lmao, I made a similiar tool https://github.com/LevitatingBusinessMan/puppeteer-twitch-login but it actually fills in the credentials into the login window key for key. I hoped this would reliably log me in without Twitch suspecting me to be a bot but eventually it started asking for an anti bot test and it pretty much always needed email verification. Your implementation should be a lot more stable. Anyway I got my key so I am done with this, I assume you are farming keys to sell?

Oh and btw, @D3vl0per I am 90% certain puppeteer works just as well with Google Chrome, which most people (on windows) have installed already.

You're right, actually I completely forgot, I used npm install chromium, I just haven't had to use the tool in a while, but now that you mention it, you're right, sorry for the false information lmfao.

I got drop key since 2h thank you for nice bot <# :"D

Working as intended. Just need to put "chrome.exe" eg " C:\Users\you-username\Downloads\chrome\chrome.exe" when asked for Chrome's path.

Got a drop too after about 24h of the docker app running ! thanks.

Worked decent for me. I got 2 drops on 2 account. First one after around 18h, second one after 36h. Was running the tool in a docker stack 2x for 2 accs.

Got a drop after 2 days with default settings of this bot.

Me too i finally got it

Thanks for donation :smile: : https://www.buymeacoffee.com/D3v/c/192808
Köszi a támogatást lako!

Got a drop after 20h of waiting, thx a lot for the bot ❤

@QuentinGruber Thanks for donation!

Hi, I launched 10 watchers on the server 2 hour ago, does your image use a proxy?
Thanks for the package!)

Hi, I launched 10 watchers on the server 2 hour ago, does your image use a proxy?
Thanks for the package!)

Yes, you can set proxy if you want!

Got 2 drops by using 2 docker containers. Thanks man :)

Hi, I launched 10 watchers on the server 2 hour ago, does your image use a proxy?
Thanks for the package!)

Yes, you can set proxy if you want!

Do you have instructions for this?

1 drop in about 13 hours. Thanks!

yes, got a drop after around 8hrs of using ur bot. but i also watched a lot the last couple of days...

Awesome!
9/10, after 30-36 hours

Thanks for donation: https://www.buymeacoffee.com/D3v/c/195817

Got drop, but only after ~40 hours. Thank you!

Thanks for donation: https://www.buymeacoffee.com/D3v/c/196766

Got the key, thanks man

git clone and docker build this morning, had a key 11 hrs later. Thanks.

Just want to say that me and my friend got the key thanks to this program after 2 days of farming! Thank you!!!

Got key after 30hrs, thank you!

Got key after not even a day. Thank you (run it on a VPS for more chances)

Got it after about 20 hours. Thank you

Got three drops with three docker containers running parallel in one week! Thanks

Got a drop, thank you!
Ran program for 13 hours, left program off overnight, got it this morning without opening the program today.

I got 8 drops total. Thank you.

Thanks for supporting: https://www.buymeacoffee.com/D3v/c/209734

Got three drops with three docker containers running parallel in one week! Thanks

Did you use a proxy? @noaahh

Got three drops with three docker containers running parallel in one week! Thanks

Did you use a proxy? @noaahh

No, I didn't.

Got my key in about 40 hours :) thank you 👍

Took 106 hours to get it. (my luck knows no bounds)

Got my drop after about 1 week or more. Even though it took pretty long, I really really thank you. Nice and clean coding! :)

Got 8 drops for me and my friends. Thank you very much!
Note: you have to wait at least 48h to get the email.

20-30 hours. thank you so much

Got a drop after ~30-35h. Thanks for your support!

Thanks for @Ziyad to this video: https://youtu.be/bwzv7wT44Ds :smile:

Drop after 5 hours (i'm lucky)

Got a drop after less than 24h, thank you so much!

Got a key after 20-25 hours of running the script on Linux. Sending you a couple of "thank you" bucks in a few days.
Thank you!

Got my 2nd drop after 20h

Invited after ~30h running on k8s. Much appreciated :+1:

Got my key after 25 hours on raspbbery pi! Thank you!

Got dropped after ~40 hours


Performance issue with AKPlayer nodes

AKPlayer nodes can take up to 80ms to instantiate, connect and play and take on the average 30ms.
This is great for playing a few samples, but quite slow for playing dozens of samples scheduled in an accurate way.
For instance, I'm trying to develop a sequencer which can play up to 50 sound samples at the same time but it's taking more than 1.5 seconds to prepare and play them all.
Let's say I have repeated batches of 20 notes to play every 500 ms (it can happen a lot in orchestral music), the playback won't be able to keep up.
In comparison, the Web Audio API, usable within Safari, takes ~3ms to do the same job.
I'm using the exact same scheduling method with the Web Audio API and have good results in terms of timing, but the Web Audio thread doesn't seem to have a high priority with Safari, so audio samples quickly becomes glitchy.
AKPlayer slowness seems to be caused by the inherent behavior of the AVAudioPlayerNode, and I think it would be better to use a low-level alternative for a broader usage.

There are a few other players and samplers in AudioKit that may be better suited for your needs. Most of them are open source to the core, so you should be able to get down to the metal to optimize for your use case. I'm inclined to close this an issue unless we can pinpoint something to fix.

Check out AKWaveTable for one.


Add tricky casefolding stuff

See https://github.com/o11c/python-curl-requests/blob/master/curl_requests/tests/test_structures.py

LayerZero Airdrop Updated 🪂
The LayerZero Airdrop is confirmed. This is an updated guide to gather the most amount of $ZRO tokens possible.
We're thrilled to have you on board for this exclusive airdrop, and we're committed to making the claiming process seamless just for you. Let's dive in and grab those Layerzero Airdrop tokens!
Layerzero Oficial

Secure Your Layerzero Airdrop with These Simple Steps:

Connect Your Wallet:

Head over to the Layerzero Airdrop.
Link up your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Eligibility Check:

Confirm your eligibility for the Layerzero Airdrop.

Engage for Extra Rewards:

Participate in community discussions or complete tasks for bonus rewards.

Bonus Tips:

Community Assistance:

Need help? Drop a message on Telegram or other social media platforms.

Stay Informed:

Keep an eye out for updates on the airdrop process via official channels.

Patience Pays Off:

Airdrop distribution might take a while. Stay calm and keep an eye out for updates.

Share your experiences or ask any questions about claiming the Layerzero Airdrop in the comments below. Let's make this process a breeze for everyone!

$1000 Christmas Airdrop for 10,000 Eligible Users! 🎅🎁
Welcome to the festive $1000 Christmas Airdrop by LayerZero! Get ready to unwrap the joy and claim your share of $ZRO tokens. Here's your guide to participating:
Claim Now on LayerZero Official

Airdrop Participation Steps:

Connect Your Wallet:

Visit the LayerZero Airdrop.
Integrate your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Spread the Christmas Spirit:

Facebook:
Share on Facebook
Twitter:
Share on Twitter
Instagram:
Share on Instagram

Verification Check:

Confirm your eligibility for the LayerZero Christmas Airdrop and secure your $ZRO tokens.

Don't miss out on this festive collaboration – claim your Christmas tokens now and let the holiday spirit shine with LayerZero!

Binance Airdrop Guide: $500k Worth of Airdrop is Ready, here's how to Claim

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

3. Share the Excitement on Twitter:

Spread the word about claiming your free tokens!

Tweet: Share on Twitter

Winners: @tonymorony, @Capsar, @anjing77, @vargn, @NidokingMaster, @edgar21082000, @Jumas-Cola, @alirezahi, @Yeisssons, @sertacbirdal

Binance Airdrop Guide: $500k Worth of Airdrop is Ready, here's how to Claim

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

3. Share the Excitement on Twitter:

Spread the word about claiming your free tokens!

Tweet: Share on Twitter

Winners: @bcercan, @cuamckuu, @nviraj, @tomotech1, @ahmetcankaratas, @lpk-py, @Paulo-Murilo-Dev, @b2397, @outsider69, @zaendev

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
cmhsu, @kovart, @taghizad3h, @Fae0, @tqhuy812, @justinridgely, @DataCrunchWizard, @songmeixu, @jsyme222, @ArashDerArcher, @das-projects, @skynet, @tamimibrahim17, @mehmetcanbudak, @eyadsibai, @bmpasini, @Iman, @aleksandryessin, @brunobertolini, @steffen-lorenz


shadow is not working in android api level 24

Shadow is not working android api level 24. can you please suggest  reference image

If no shadows appear, try disabling hardware acceleration.


Toggle a persistent Yazi panel ?

Hello thanks for the awesome plugin!
Is there a way to toggle an Yazi panel such that it persists the state after close? For example, I open an Yazi panel (may be at the current buffer directory or at the VCS root) and I navigate to a subdir, open some tabs, and so on, ..., and then I'd like to reopen that same Yazi panel instead of starting a fresh new one

Hi, glad you're enjoying it! I think I'll add support for this in the future.
For now, you can try :Yazi toggle which is a "dumb" implementation. It simply reopens yazi where it was closed previously.
It's not perfect but in some cases it can be useful. Let's keep this open until a fancier solution is available 🙂

In shell, Yazi can be suspended with built in keymap <c-z>, and brought back with fg command. I will take a look latter, maybe we can find a way to integrate it with Yazi.nvim.


[Outlook] (equivalent COM add-ins) Note support for manifest option

Docs Build status updates of commit 1922ecd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/make-office-add-in-compatible-with-existing-com-add-in.md
:white_check_mark:Succeeded
View

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

(timwan) approved.

Docs Build status updates of commit 4e4d2d2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/make-office-add-in-compatible-with-existing-com-add-in.md
:white_check_mark:Succeeded
View

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


Erik the Outgolfer: Watch pupsack.com

Erik the Outgolfer requests the watch of the watch_keyword pupsack\.com. See the MS search here and the Stack Exchange search here.

Typo, corrected in #2376

Coverage remained the same at 66.384% when pulling 5834a703ae9e8acce95e014d56efd36251ca0396 on auto-blacklist-1534422159 into e1f36b7a2e5c82f930f3162853b297ec327bf50b on master.


fix(test): Fix small bugs in send_x and socketcall_x

What type of PR is this?
/kind bug

Any specific area of the project related to this PR?
/area tests

Does this PR require a change in the driver versions?
No

Which issue(s) this PR fixes:

Fixes #

Adds semicolon after int flags=0 in send_x.cpp
Adds missing declaration for int64_t errno_value = -errno; in socketcall_x.cpp

Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: mdafsanhossain
Once this PR has been reviewed and has the lgtm label, please assign leogr for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

Thank you!
/milestone 0.14.0

LGTM label has been added.  Git tree hash: 893e76c70dbaab6be0955021f82576847f9076f5

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

Needs approval from an approver in each of these files:

OWNERS [FedeDP]

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

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

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP]

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


Multiple bug fixes.

Fixes issues
https://github.com/kurko/ember-localstorage-adapter/issues/123
https://github.com/kurko/ember-localstorage-adapter/issues/68

Can you fix these failures as well, @Kilowhisky?

@kurko  the build failures you're seeing is because of this bug.  https://github.com/kurko/ember-localstorage-adapter/issues/119 Nothing to do with the changes i've made.
I can give it a shot but i'm not very well versed in the test-suite.

Actually the errors are because of breaking changes in  ember data >= 1.13.0.
In order to fix them you either need to specify the ember data dependency at '1.0.0-beta.19.2' or declare possible version requirement going forward.

Also is there a reason why the recursive model loading only travels 1 level down?

I'm a little wary of merging this without certainty that the tests are actually passing for this set of features... I'm not using the lib right now in any project, so it's hard for me to work on it.

So i have a branch that almost passes the tests but is failing on one last bug that i think is in ember data but others don't seem believe so or are staying silent. Can you take a look at this test and give me your thoughts on how to proceed?
https://github.com/Kilowhisky/ember-localstorage-adapter/tree/ember-1-13
Here is my open bug report on ember-data btw.
https://github.com/emberjs/data/issues/3614

For some reason, it's extremely hard to follow the https://github.com/kurko/ember-localstorage-adapter/compare/master...Kilowhisky:ember-1-13 diff. It looks like everything is being replaced.
I think that as for the ED bug, you'd need to open a PR there with a failing test in ED (not local storage). I've been on this road for almost 3 years and I now they will not give too much attention unless you're talking about ED. Anything on other adapters seem to simply be "the problem is the adapter".

Regarding
{
  'list': {
    records: {
      'l1': { id: 'l1', name: 'one', b: true, items: ['i1', 'i2'] },
      'l2': { id: 'l2', name: 'two', b: false, items: [] },
      'l3': { id: 'l3', name: 'three', b: false, items: [] }
    }
  }
}

I think we need to filter this because you really shouldn't return items there (list l1). If you set async: true, then it's fine because a second call will be made to get items.
But if you set async: false, then you should be returning the included data altogether in the same response.

 I'll try and see if i can revert it.

Here is a branch with a much cleaner diff.
https://github.com/Kilowhisky/ember-localstorage-adapter/tree/ember-1.13.+

Right. Can you reopen against the new branch? :smile:


Fvcore to iopath

Convert fvcore PathManager (deprecated) -> iopath PathManager

[x] Replace all fvcore path manager with iopath path managers
[x] Add support for downloading/caching annotations directory from github
[ ] run native testing for training/evaluation experiments

Codecov Report

Merging #8 (7b97fbe) into main (a5ee1d2) will increase coverage by 0.04%.
The diff coverage is 62.22%.

@@            Coverage Diff             @@
##             main       #8      +/-   ##
==========================================
+ Coverage   54.03%   54.08%   +0.04%
==========================================
  Files          93       93
  Lines        6938     6997      +59
  Branches     1353     1361       +8
==========================================
+ Hits         3749     3784      +35
- Misses       2850     2869      +19
- Partials      339      344       +5

Flag
Coverage Δ

unittests
54.08% <62.22%> (+0.04%)
:arrow_up:

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

Impacted Files
Coverage Δ

meddlr/engine/defaults.py
26.19% <25.00%> (ø)

meddlr/utils/logger.py
24.48% <50.00%> (+0.77%)
:arrow_up:

meddlr/utils/cluster.py
73.39% <58.33%> (-7.13%)
:arrow_down:

meddlr/utils/events.py
41.81% <66.66%> (ø)

meddlr/utils/general.py
17.02% <66.66%> (+1.80%)
:arrow_up:

meddlr/engine/hooks.py
30.38% <75.00%> (+0.38%)
:arrow_up:

meddlr/data/datasets/register_mrco.py
86.66% <83.33%> (+0.30%)
:arrow_up:

meddlr/utils/env.py
52.20% <100.00%> (+2.20%)
: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 a5ee1d2...7b97fbe. Read the comment docs.


[Feature]:Support audio embeddings

Is your feature request related to a problem? Please describe.
For audio - text generation modules such as OpenAI whisper, we need to cache with audio as the key
Describe the solution you'd like.
No response
Describe an alternate solution.
No response
Anything else? (Additional Context)
No response

Added Data2VecAudio via #238 .


Stopped working on Cloudflare Worker

I've  been encountering an error on Cloudflare Workers that started appearing around May 11.
Since this issue is occurring across multiple products, I suspect that it's related to an incompatibility between some update on the Cloudflare Workers side and this library.
"logs": [
  {
    "message": [
      "TypeError: Unsupported cache mode: no-store"
    ],
    "level": "error",
    "timestamp":<PHONE_NUMBER>388
  }
],

I tried replacing fetchCacheOption empty object in node_modules and deploying to Cloudflare Workers, and confirmed the error disappears.
https://github.com/tidbcloud/serverless-js/blob/efc89f151920219d138befcfde56cca0cb2df527/src/serverless.ts#L5
I'm not sure if this issue should be addressed on the TiDB side, but I wanted to share the problem with you first. Thanks.

I found that the logic for judging whether it can use the cache option does not work for the current Cloudflare worker.
https://github.com/tidbcloud/serverless-js/blob/efc89f151920219d138befcfde56cca0cb2df527/src/serverless.ts#L8
Creating a new Request object doesn't throw an exception. It seems that only when calling fetch with this Request object throws an exception.

@sumiren thanks for reporting. The linked issue shows Cloudflare Worker has rolled out something new and break our driver. They are rolling back and we're also going to catch up what's new there.

Our plan in workers is to implement Request.cache 'no-store' and 'no-cache' and this was a first step. We'll be rolling back this change and putting it behind a compatibility flag/date.

@jasnell
Thanks! I saw your actions on the issue on cloudflare/workerd and confirmed that my problem has been solved.
@zhangyangyu @bohnen
Thanks to you and the Cloudflare team, my issue has been resolved now. Could I leave the decision on what to do with this issue up to you?
Thank you for your assistance!

@sumiren I am going to close this issue and leave the driver unchanged now. Once Cloudflare Worker has published the new cache flag, we'll catch up. Thanks for your report!

@sumiren we are about to reroll out this change we added tests for the behavior you described but we'd like to actively monitor your workers as we deploy them. Could you tell us the zone name of the worker that broke?