[bug] 1.21-dev compilation with GCC 13

Bug Report
Good day!
I've encountered some Dogecoin Core 1.21 compilation issues as I wanted to examine more closely https://github.com/dogecoin/dogecoin/issues/2951 notes.
Current behavior:
In support/lockedpool.cpp:
support/lockedpool.cpp:102:20: error: ‘runtime_error’ is not a member of ‘std’
  102 |         throw std::runtime_error("Arena: invalid or double free");
      |                    ^~~~~~~~~~~~~
support/lockedpool.cpp:25:1: note: ‘std::runtime_error’ is defined in header ‘<stdexcept>’; did you forget to ‘#include <stdexcept>’?
   24 | #include <algorithm>
  +++ |+#include <stdexcept>

util/string.h:
./util/string.h:84:50: error: ‘uint8_t’ was not declared in this scope
   84 |                                 const std::array<uint8_t, PREFIX_LEN>& prefix)
      |                                                  ^~~~~~~
./util/string.h:17:1: note: ‘uint8_t’ is defined in header ‘<cstdint>’; did you forget to ‘#include <cstdint>’?
   16 | #include <vector>
  +++ |+#include <cstdint>

/util/bip32.h:
./util/bip32.h:13:75: error: ‘uint32_t’ was not declared in this scope
   13 | NODISCARD bool ParseHDKeypath(const std::string& keypath_str, std::vector<uint32_t>& keypath);
      |                                                                           ^~~~~~~~
./util/bip32.h:11:1: note: ‘uint32_t’ is defined in header ‘<cstdint>’; did you forget to ‘#include <cstdint>’?
   10 | #include <vector>
  +++ |+#include <cstdint>

Expected behavior
Program should compile normally without these errors.
Steps to reproduce:

GCC version: gcc (Gentoo 13.2.1_p20230826 p7) 13.2.1 20230826
protobuf: 23.3-r2 (libprotoc 23.3)
configure options:
./configure --prefix=${HOME}/projects/dogecoin-1.21-dev  --disable-bench --disable-tests CXXFLAGS="-std=c++14"
This is because the latest version of protobuf that I am using requires C++ standard to be at least 14.

Dogecoin Core version
1.21
Machine specs

OS: Calculate Linux (Gentoo-based)
CPU: Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz
RAM: 6
Disk size: 500GB
Disk Type (HD/SDD): HDD

These errors can be easily fixed by modifying these files to include required headers.  I'll be happy to submit a PR that fixes these issues, if necessary.
Probably my GCC version is causing these errors (I had to implement similar GCC 13 patch in my other project to fix it).  I think it may be a good idea to make 1.21 support newer GCC versions, and, perhaps, support C++ 14 standard also?
Thank you,
Victor.

What version of boost are you compiling against?

What version of boost are you compiling against?
Hi,
I'm using boost-1.81.0-r1 .

The first issue in support/lockedpool.cpp is the same error we fixed in #3335 for 1.14, feel free to PR that.
The errors in util/ are odd, I will try to reproduce these on Debian Sid to get some more insights

support C++ 14 standard also

1.21-dev requires c++17, this should be compatible with the protobuf requirement? I'm not sure what is causing errors for you? What error made you add the CXXFLAGS="-std=c++14"?

What error made you add the CXXFLAGS="-std=c++14"?

I was getting Protobuf only supports C++14 and newer when building 1.14.6 and 1.21 using installed version of protobuf-23.3-r2, so adding this CXXFLAGS option fixes this error.

1.21-dev requires c++17, this should be compatible with the protobuf requirement

Hmm, interesting.  I just quickly checked and there is --enable-c++17 configure option.  I wasn't using this option but I am certain protobuf should be compatible with c++17 if used 👍

I just quickly checked and there is --enable-c++17 configure option

My bad that I forgot this wasn't the default - but yes this should help.

The errors in util/ are odd, I will try to reproduce these on Debian Sid to get some more insights

I was able to reproduce this also on Debian w/ gcc13, consistently. I'm not sure what changed (something with --enable-cheaders defaults for glibstdc++?) and I'd want to investigate a bit further and figure out how we can best manage naive implementation on our side. However, in the meantime let's add the headers because they should be there. Would appreciate if you could do a PR for this. It'll be blocked by #3350 initially but as soon as that goes in, it can go through.
Re: protobuf, since it's not a dependency for 1.21, it is not related to this issue.


Remove coveralls token from travis.yml

Expected behavior
Coveralls should run on Travis CI.
Actual behavior
Due to the $COVERALLS_TOKEN not being set, goveralls test crash on travis for my repository and during PRs. Goveralls should not need the repo-token argument to be used when running on Travis (https://github.com/mattn/goveralls#github-integration).

Coverage remained the same at 57.759% when pulling 293534a8a0ce01e9b88ca44788a15f6cf3baee4e on groyoh:fix_coveralls into 1df5f0cecee3d05be0343df2c01e9859dd2cca54 on vinci-proxy:master.


simplejson.errors.JSONDecodeError not excepted

requests uses simplejson when available and only json.decoder.JSONDecodeError excepted on _parse_json

Oh wow, I really appreciate you filing all these bugs! I'll have a look soon!

It appears in this discussion the requests team decided to get rid of simplejson three years ago.

just some notes:

if I looked correctly. simplejson import only removed from not yet released requests3, but not from requests2
on Ubuntu simplejson is still installed by default

(I removed simplejson from my system, so I don't actually care...)

Hmm it appears I closed this too soon then. Much appreciated.

Yeah, it was merged to a proposed:3.0 branch. I dislike the idea of depending on simplejson just for this, so I think its better to test the response contents before trying deserialisation to see if it should be JSON. Then if we try to

just some notes:

if I looked correctly. simplejson import only removed from not yet released requests3, but not from requests2
on Ubuntu simplejson is still installed by default

(I removed simplejson from my system, so I don't actually care...)

how you removed that ??

@Bhanuprakash111 Haven't worked with it, but most probably it's just a python package. So pip uninstall simplejson with your variants of python2/3 -m and pip2/3 ought to do it.


Allow user to collapse floater controls

The floater controls are big.  User wants to see the floaters over the map, without additional stuff.
Allow them to collapse the controls

Mockups to prompt discussion: https://www.figma.com/file/gKYVrWu6qfDTUgYKQuvaIy/SAM?node-id=991-14514&t=jQrnhVfZHQn6qlAk-4

From my cursory glance, it looks like all the visualization components (BarplotVisualization.tsx, BoxplotVisualization.tsx, HistogramVisualization.tsx, LineplotVisualization.tsx, etc) could be implemented with some <VisualizationControls> component that takes a prop to toggle hiding.

id like to know how this relates, if at all, to us adding axes controls for things like binning histograms and setting axes ranges

Fixed by https://github.com/VEuPathDB/web-monorepo/pull/535


Decompress suppresses Z_BUF_ERROR

The reader loop in decompress.hpp suppresses Z_BUF_ERROR so it doesn't detect truncated input files.
I think the right way to do it is probably as in this change to Tippecanoe's code copied and pasted from the same place: https://github.com/mapbox/tippecanoe/pull/604/commits/07ab90039380344a308d0a9446564e5474697a02.
With this change, the loop terminates only on Z_STREAM_END, so in the case of a truncated stream, it continues trying to decompress and reports Z_BUF_ERROR instead of the current behavior of terminating because the input has all been consumed even though the decompressor is still expecting more.
This also attempts to clean up what has always seemed like confusing logic to me about the size of the output buffer, the size of the output so far, and zlib's pointers into the buffer.

@ericfischer could https://github.com/madler/zlib/issues/289 be related?


Avoid or Optimize CoordinatedRequest serialization

The serialization and deserialization of CoordinatedRequests should be evaluated closely. This will become a performance issue, and serialization should be avoided at all costs so long as a request's execution stays within the same instance. This could be related to https://github.com/suborbital/reactr/pull/81 or whatever comes of that effort, as it will hopefully allow for strongly typed execution, even with Wasm Runnables.

This is being addressed in Reactr


Configuration of the proxied HTTP request version.

Adds configuration side to setting up Version and VersioningPolicy (for .NET 5 and higher) of an outbound HTTP Request.
Fixes #282

@Tratcher, @alnikola: I think I've addressed all comments except for the type-merging one, which I'd rather do separately if you're OK with it. I'll file an issue and look into it immediately. I'd just prefer to split the work.

@ManickaP Hey, I'm working on this PR to change configuration reading https://github.com/microsoft/reverse-proxy/pull/521. I'm going to wait until this PR is merged.

@alnikola : could you please give this another look? I cannot merge till you approve since you originally requested changes.


Unable to load conga32_64.so

I am using Linux source build, I did installation suggested by documentation. Although when I run ]tatin.publish it can not load conga32_64.so from tatin installation path (MyUCMDs). It searches for it in my apl path "/home/[myuser]/svn/trunk/apl/" but I have conga33_64.so, then cause "Command Execution Failed".

Will be fixed in the next version of Tatin


 Note: I have re installed and upgraded tvm packages. libc++abi: terminating due to uncaught exception of type tvm::runtime::InternalError: [11:11:01] /Users/j0g0w41/Documents/mlc/mlc-llm/3rdparty/tvm/src/runtime/relax_vm/vm.cc:705: InternalError: Check failed: (func.defined()) is false: Error: Cannot find PackedFunc vm.builtin.paged_attention_kv_cache_attention_with_fused_qkv in either Relax VM kernel library, or in TVM runtime PackedFunc registry, or in global Relax functions of the VM executable

Hey, any luck fixing it?

I also attempted building the TVM from source but still received the same error

Me too. Not sure where to go from here. 😢

+1 any solution ?

https://llm.mlc.ai/docs/deploy/ios.html# this should be fixed by latest ios sdk

My machine configuration is M1 Mac with 16GB RAM

Thanks @tqchen . I cloned and re built the latest iOS SDK. No crash is observed


GitAttributes.io is down

Not sure how/why the website would be down/unavailable, but it is (see here).

Thanks for the report. Let me check it, because the domain was paid for. I suspect the DNS server does not point to Cloudflare now.

The domain just disappeared from the Cloudflare. I will recreate DNS entries.

There was also a strange change in Azure from .NET Core 3 to .NET Framework 4.8 so the service was not running properly.
The website is accessible now.

Looks like this is down again.


New version: ART.ART 1.21.0

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Hi @pxwiz,
The InstallerUrl has the previous version number in it. This version appears to have not been released yet.

Hi @pxwiz,
The InstallerUrl has the previous version number in it. This version appears to have not been released yet.

Resubmitted on a new branch as #130496


[bug] Can't package with parcel because of "process" being undefined

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
2.5.8
Current Behavior
I've got a pretty simple app here, it looks like this
import React from "react";
import ReactDOM from "react-dom";
import { Player } from "@livepeer/react";

const div = document.createElement("div");
div.innerHTML = "hello";
div.id = "iameli-streams";
document.body.prepend(div);

const App = () => {
  return (
    <div>
      <Player playbackId="bb046er0yawh006o"></Player>
    </div>
  );
};

ReactDOM.render(<App />, document.querySelector("#iameli-streams"));

I'm attempting to build it with Parcel, with this configuration
{
  "name": "iameli-streams",
  "version": "1.0.0",
  "browser": "dist/iameli-streams.js",
  "license": "MIT",
  "dependencies": {
    "@livepeer/react": "^2.5.8",
    "nodemon": "^2.0.22",
    "npm-run-all": "^4.1.5",
    "parcel": "^2.9.3",
    "react": "^18.2.0",
    "react-dom": "^18.2.0"
  },
  "scripts": {
    "dev": "run-p dev:rebuild dev:ngrok",
    "dev:rebuild": "nodemon -w src/ -e tsx -x yarn run prepare",
    "dev:ngrok": "ngrok http file://$(realpath dist) --log=stderr --log-format=logfmt --host-header=rewrite",
    "prepare": "parcel build --target browser ./src/index.tsx --dist-dir dist"
  },
  "targets": {
    "main": false,
    "browser": {
      "context": "browser",
      "includeNodeModules": true,
      "outputFormat": "esmodule"
    }
  },
  "browserslist": "> 0.5%"
}

This builds just fine, but results in an error when executing on this line:
var $3sXIf$process = require("process");

Which yields:
iameli-streams.js?cache=1688335387859:1 Uncaught ReferenceError: require is not defined
    at iameli-streams.js?cache=1688335387859:1:22

My environment doesn't know what require or process are, I think. Is there maybe somewhere in the library where we're assuming Webpack/Next's conventions around that variable existing...?
I've successfully worked around the issue by adding an empty process field and aliasing it, so that's...
src/process.tsx:
export default {
  env: {},
};

And then this in package.json:
  "alias": {
    "process": "./src/process.tsx"
  }

But it'd be nice not to need that workaround; I think we just need to be conditional in places where we include process.env and not always assume it exists?

I think this a downstream issue with parcel, and unrelated to livepeer.js. Webpack or Browserify should help with this.

This should be fixed with https://github.com/livepeer/livepeer-react/pull/459


OAS : /v1/bequeath-your-data-and-die : callback : reference path needs update

Error description:
In callback "PromptForBequeathingDataCausesRObeingRequestedToNotifyApprovalsOfNewApplicationsToNewRelease" and "PromptForBequeathingDataCausesRObeingRequestedToNotifyWithdrawnApprovalsToNewRelease", we have request-body attribute "subscriber-operation", the reference path under description of the attribute needs an update. The path is intended to refer an operation-server ltp (alt-0-0-1-op-s-3001 and alt-0-0-1-op-s-3002), but the proceeding path points to operation-client.
Possible solution:
In the description, path needs an update to point to operation-server-interface-capability/operation-name as below.
For PromptForBequeathingDataCausesRObeingRequestedToNotifyApprovalsOfNewApplicationsToNewRelease, the current description contains /core-model-1-4:network-control-domain/control-construct=alt-0-0-1/logical-termination-point=alt-0-0-1-op-s-3001/layer-protocol=0/operation-client-interface-1-0:operation-client-interface-pac/operation-client-interface-configuration/operation-name, which actually would be
/core-model-1-4:network-control-domain/control-construct=alt-0-0-1/logical-termination-point=alt-0-0-1-op-s-3001/layer-protocol=0/operation-server-interface-1-0:operation-server-interface-pac/operation-server-interface-capability/operation-name
For PromptForBequeathingDataCausesRObeingRequestedToNotifyWithdrawnApprovalsToNewRelease, the current description would be updated as
/core-model-1-4:network-control-domain/control-construct=alt-0-0-1/logical-termination-point=alt-0-0-1-op-s-3002/layer-protocol=0/operation-server-interface-1-0:operation-server-interface-pac/operation-server-interface-capability/operation-name
Note: alt-0-0-1-op-s-3001 refers to /v1/regard-application and alt-0-0-1-op-s-3002 refers to /v1/disregard-application
Related issues:
https://github.com/openBackhaul/RegistryOffice/issues/91
https://github.com/openBackhaul/TypeApprovalRegister/issues/40
https://github.com/openBackhaul/ExecutionAndTraceLog/issues/41
https://github.com/openBackhaul/OamLog/issues/38
https://github.com/openBackhaul/AdministratorAdministration/issues/37
https://github.com/openBackhaul/OperationKeyManagement/issues/28

Sorry for the confusion. The description in issue might not be clear.
In PromptForBequeathingDataCausesRObeingRequestedToNotifyApprovalsOfNewApplicationsToNewRelease and PromptForBequeathingDataCausesRObeingRequestedToNotifyWithdrawnApprovalsToNewRelease, we have attributes in request body called "subscriber-operation". In the description of this attribute "subscriber-operation", the uuid is pointing to "alt-2-0-0-op-s-is-001" and "alt-2-0-0-op-s-is-002", but the path reference is pointing to operation-client.
This needs to be updated to operation-server/operation-name (line 507 and 603)


Unit tests improvements: exception checks should not be too broad

Description
Unit tests improvements: exception checks should not be too broad.
pytest.raises(Exception) etc. will catch any Exception and may catch errors that are
unrelated to the code under test. To avoid this, pytest.raises should be called with a match parameter.
Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library
[x] Unit tests

Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] PR has passed all pre-merge test jobs.
[ ] If it is a core feature, I have added thorough tests.

Testing

make test-unit

/lgtm

/approve


shell command not works proper in Mac default Terminal

Refs

https://stackoverflow.com/questions/25879183/can-terminal-app-be-made-to-respect-ansi-escape-codes

Fixed in firmware: https://github.com/kaluma-project/kaluma/issues/497


jupyter kernel message: add "off" as a reason

when you turn "off" a kernel like python, there is a yellow warning box (saying the kernel got a SIGKILL) and a link to https://doc.cocalc.com/howto/jupyter-kernel-terminated.html
on that page, nowhere is mentioned that this message happens due to such usage. it should just expand a bit in the beginning about capturing events of the underlying kernel process – and a regular "off" shutdown is one of them.

Done in 96f156e


Remove panic in nat package on invalid hostport

Closes #14621
This one grew to be much more than I expected so here's the story... :-)

when a bad port string (e.g. xxx80) is passed into container.create()
via the API it wasn't being checked until we tried to start the container.
While starting the container we trid to parse 'xxx80' in nat.Int()
and would panic on the strconv.ParseUint().  We should (almost) never panic.
In trying to remove the panic I decided to make it so that we, instead,
checked the string during the NewPort() constructor.  This means that
I had to change all casts from 'string' to 'Port' to use NewPort() instead.
Which is a good thing anyway, people shouldn't assume they know the
internal format of types like that, in general.
This meant I had to go and add error checks on all calls to NewPort().
To avoid changing the testcases too much I create newPortNoError() JUST
for the testcase uses where we know the port string is ok.
After all of that I then went back and added a check during container.create()
to check the port string so we'll report the error as soon as we get the
data.
If, somehow, the bad string does get into the metadata we will generate
an error during container.start() but I can't test for that because
the container.create() catches it now.  But I did add a testcase for that.

Signed-off-by: Doug Davis<EMAIL_ADDRESS>

LGTM

Updated per @cpuguy83 's suggestion

ping @cpuguy83 @LK4D4

LGTM


Hrule between different welcome view contributions?

Ref: #91269
It might be nice to insert hrules between welcome view contributions, currently it can be confusing which lines go together and the extension cant contribute their own hrules (even if they could that wouldn't work right as they dont know if something is above/below them.

This is a fair idea, however it goes against the inital design of the welcome view content.
For now leaving it open as a feature request and we might reconsider it in the future if there is too much content and the welcome views get cluttertd.
fyi @joaomoreno


add ; for amd dependency

What kind of change does this PR introduce?

bugfix
Did you add tests for your changes?
No
If relevant, did you update the documentation?
not relevant
Summary
This corrects the emitted code when resolving dynamic amd requires.

fixes #2318 for webpack1
Does this PR introduce a breaking change?

No
Other information

Current coverage is 11.76% (diff: 100%)

Merging #3409 into webpack-1 will not change coverage

@@           webpack-1      #3409   diff @@
===========================================
  Files              1          1
  Lines             34         34
  Methods            5          5
  Messages           0          0
  Branches           6          6
===========================================
  Hits               4          4
  Misses            30         30
  Partials           0          0

Powered by Codecov. Last update 5a56be9...92587c5

@sokra can you clarify, this indeed fixes the invalid amd resolution syntax created by webpack1

old. webpack 1. -> closing


Fix: enable opt out of slideover phx-click-away

Bug replication:

visit: http://localhost:4000/campaigns//messaging
try and insert an emoji
the slideover closes

This is a quick fix that allows you to disable the click-away for a slideover via an attribute. Not the best solution, but the user can still press the "X" to exit.

Can you try a different approach here?
https://emoji-button.js.org/ is the button we use. It looks like it's deprecated in favor of a new version: https://picmojs.com/
I notice that PicMo has a rootElement option when creating the button. I think that's the trick! click-away wont register as clicking away if the emoji picker element is a child of the slideover - Can you try switching to PicMo and setting the root element to be the button or something next to it and see if it fixes the issue?


dont also capture directories where SUID is set

I never came across such a case but it's good to have it in place. Thanks for your contribution! :+1:


Gitpod IDE (please complete the following information):

VSCode Desktop
Unknown
GamingLaptop
Windows, sshed into GitPod that is running Linux

Additional context
I set my own gpg signing key and uploaded to github yet I still see your face!! >:(

I should of read documentation

@BrycensRanch Hey Bryce, I'm really sorry for responding to this so late -- I never got notified of this issue. I'm just now catching up with a ton of stuff I missed over the last 6 months due to some health issues.
Just on a first glance it seems like my username and email are hardcoded somewhere... and the configuration is persisting in places it shouldn't. That's pretty concerning. I'm working on fixing this as we speak.
Once again sorry for the delayed response and the inconvenience of this bug

@BrycensRanch Looks like I just found what was causing this facepalm of a bug. The GIT_AUTHOR_* variables were being carried over from the .gitconfig template files that are used during the bootstrap process... At the time I assumed that Gitpod would always have defined those variables during the container build/prebuild step, but obviously that wasn't the case in your scenario.
 Sorry again for the inconvenience.
It should be fixed now but in case it isn't, I'll leave this issue open for the time being.

Hey, thank you. I've switched back to your gitpod in one of my other repos and it's working great now, thank you so much for the work you've done with this gitpod enhanced development environment. It's very nice to use. I'll be closing now, have a great day and I hope Thanksgiving is gonna be awesome for you, man.


Update docs to use flash command for updating firmware

While following the instructions on software-setup page for installing drivers on Grayskull card,
I tried to flash the firmware with the command mentioned : tt-flash --fw-tar <latest fwbundle file> --force
However, this command resulted in the following failure:

Solution:
Need to use tt-flash flash --fw-tar <fwbundle file> --force to run successfully.
Update needed in the doc here

You could update this by submitting a PR to https://github.com/tenstorrent/tenstorrent.github.io

Issue is not about tt-flash flash vs. tt-flash this was filed at my behest as a tracking issue for a different problem with the tt-flash command and error suggestions.  tt-flash and tt-flash flash continue to work as expected as the former is a compat option.
Actual error in question: If the .fwbundle is not as expected, in this specific case an lfs tracking file (text file) vs. a properly compressed blob we are expecting the error that comes back is:
$ tt-flash --fw-tar fw_pack-<IP_ADDRESS>.fwbundle
Stage: SETUP
Opening of fw_pack-<IP_ADDRESS>.fwbundle failed with - file could not be opened successfully
---
[... rest of help info follows]

What's happening is the fwbundle is getting loaded and it's incorrect, the error that's getting kicked out is incorrect in that it implies the file can't be opened, which is TRUE but it's more that it's in an incorrect format, not that it can't be actually opened.
This was intended as a tracking bug to deal with enhancing the error report there that I asked someone to file so I could jog my memory for what it was for.
Reopening bug, fixing title.


Adf Support priceType in Prebid Server

https://github.com/prebid/prebid-server/pull/2084

@fowler446 Please merge this PR since the corresponding Prebid Server PR has been merged. Thanks!


Added loading and disabled user feedback on batch actions button for cms...

https://github.com/silverstripe/silverstripe-cms/issues/441
Added images to "Go" .Action:submit button for ui-state-disabled -focus, -active and -default.
Added existing "Throbber.gif" for ui-state-focus and -active to show the batch actions as "working".
Also used existing icons for disabled and active states for better user feedback.
IE wouldn't clear ui-state-focus so had to force this in JavaScript LeftAndMain.BatchActions.js.
Safari and Firefox replace ui-state-focus with ui-state-active - so added additional CSS to account for this.
Before fix:

After Fix:

@chillu @clarkepaul @lukereative - is this worth sorting out or has SS4 work made this obsolete?

Having the loading indicator replace the text would still be good, in fact we're replacing the the text with the loading indicator for the main actions when loading. I think this is the indicator for the bigger actions .btn__loading-icon but it might be too big for the smaller area of the "Go" button.

This is what it looks like at the moment.

@lukereative (aka @LukePercy) are you keen to port this to 4.0 (the master branch)? We can't merge it into stable releases, and it doesn't merge cleanly in 4.0 at the moment. Closing for now, since this particular pull request against 3.1 won't be merged as-is.


[AutoRelease] t2-confidentialledger-2022-07-06-29362(Do not merge)

https://github.com/Azure/sdk-release-request/issues/2967
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=2674
BuildTargetingString
azure-mgmt-confidentialledger
Skip.CreateApiReview
true

issue link:https://github.com/Azure/sdk-release-request/issues/2967


ftp.ebi.ac.uk avaialable, but GTEx_ge_brain_frontal_cortex.all.tsv.gz times out

Thank for this fine package - very useful in our work on Alzheimer's Disease.
I find intermittent - sometimes lasting - problems with the ftp service the package uses.
Here is an example, establishing first that connectivity is good, then showing the error.
ping ftp.ebi.ac.uk
PING ftp.g.ebi.ac.uk (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: icmp_seq=0 ttl=53 time=164.786 ms
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=53 time=180.432 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=53 time=166.346 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=53 time=169.450 ms

The specific file request times out:
[E::hts_open_format] Failed to open file "ftp://ftp.ebi.ac.uk/pub/databases/spot/eQTL/csv/GTEx/ge/GTEx_ge_brain_frontal_cortex.all.tsv.gz" :
Operation timed out
Couldn't open "ftp://ftp.ebi.ac.uk/pub/databases/spot/eQTL/csv/GTEx/ge/GTEx_ge_brain_frontal_cortex.all.tsv.gz": Operation timed out
zcat: (stdin): unexpected end of file

I think this is a better problem report:
eQTL_Catalogue.fetch(unique_id="GTEx.brain_frontal_cortex", chrom="8",, bp_lower=27610984, bp_upper=27610987)
[1] "CONDA:: Could not identify tabix executable in echoR env. Defaulting to generic 'tabix' command"
[1] "tabix ftp://ftp.ebi.ac.uk/pub/databases/spot/eQTL/csv/GTEx/ge/GTEx_ge_brain_frontal_cortex.all.tsv.gz 8:27610984-27610987"
[E::hts_open_format] Failed to open file "ftp://ftp.ebi.ac.uk/pub/databases/spot/eQTL/csv/GTEx/ge/GTEx_ge_brain_frontal_cortex.all.tsv.gz" : Operation timed out
Couldn't open "ftp://ftp.ebi.ac.uk/pub/databases/spot/eQTL/csv/GTEx/ge/GTEx_ge_brain_frontal_cortex.all.tsv.gz": Operation timed out

My tabix is Cellar/htslib/1.14/bin/tabix

more info.  running on ubuntu, a different tabix, same problem:
tabix ftp://ftp.ebi.ac.uk/pub/databases/spot/eQTL/csv/GTEx/ge/GTEx_ge_brain_frontal_cortex.all.tsv.gz 8:27610984-276109801
[E::hts_open_format] Failed to open file "ftp://ftp.ebi.ac.uk/pub/databases/spot/eQTL/csv/GTEx/ge/GTEx_ge_brain_frontal_cortex.all.tsv.gz" : Operation timed out
Couldn't open "ftp://ftp.ebi.ac.uk/pub/databases/spot/eQTL/csv/GTEx/ge/GTEx_ge_brain_frontal_cortex.all.tsv.gz": Operation timed out

any thoughts?  It's clear this problem is outside of catalogueR!

Hi @paul-shannon, glad you're finding this tool useful. Thanks for pointing out this issue. I'll look into this and try to figure out what's going on here.
Some potential sources:

File names have changed.
I need to raise the timeout limit.
The FTP server (or connections to it) is unstable

@kauralasoo is there anything on eQTL Catalogue's end that might be causing unstable connections to the FTP server?
I just confirmed that the file paths haven't changed, so they do indeed seem to exist.

Thanks so much for the response @kauralasoo! This is all really helpful info. I'll make some adjustments to catalogueR and may make it so that the REST API is the default method.

Hi Brian,
One possible caution:  Kaur explained to me this about GTEx:
Unfortunately the uniformly processed GTEx summary statistics are currently
not available via the API. We hope to fix this with the next release
planned for January 2022. However, we do have the official GTEx V8 summary
statistics in the API. The study ID for those is GTEx_V8. Thus, this
command works:
https://www.ebi.ac.uk/eqtl/api/chromosomes/8/associations?paginate=False&study=GTEx_V8&qtl_group=Brain_Cortex&quant_method=ge&bp_lower=27603335&bp_upper=27608281
We've found that the official imported GTEx v8 summary statistics have
slightly better power than our re-processed ones, probably due to better
handling of covariates.
So perhaps, in your code, in the construction of the REST url, you could substitute like this, at least until the next release?
study=GTEx_V8    for   study=GTEX
As it is now, none of the valuable GTEx eQTLs are available when using the REST interface to catalogueR.

Paul

On Nov 30, 2021, at 7:48 AM, Brian M. Schilder @.***> wrote:
Thanks so much for the response @kauralasoo! This is all really helpful info. I'll make some adjustments to catalogueR and may make it so that the REST API is the default method.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

Thanks for the helpful info @paul-shannon, hadn't realized this!
catalogueR::eQTL_Catalogue.list_datasets currently relies on the metadata provided here, tabix_ftp_paths.tsv:
https://github.com/eQTL-Catalogue/eQTL-Catalogue-resources/blob/master/tabix/tabix_ftp_paths.tsv
It looks like there is another file called tabix_ftp_paths_imported.tsv:
https://github.com/eQTL-Catalogue/eQTL-Catalogue-resources/blob/master/tabix/tabix_ftp_paths_imported.tsv
I'll modify catalogueR::eQTL_Catalogue.list_datasets to integrate this second file as well (with a tryCatch in case it doesn't exist in the future).

I've just updated the metadata to include GTEX_V8. I also added a new arg to eQTL_Catalogue.list_datasets called include_imported. Setting this to TRUE (default) will integrate the additional datasets in /tabix_ftp_paths_imported.tsv


fix: Package installers CI step failing

Summary:
As described in #1567, the Github actions associated with the MacOS certificate imports, notarization, and stapling were dependent on open-source projects that are not available anymore. This PR implements the MacOS certificate imports, notarization, and stapling using XCode terminal commands.
Fixes #1567
Expected behavior:
GTFS Validator App is signed and notarized.
Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Run the unit tests with gradle test to make sure you didn't break anything
[x] Format the title like "feat: [new feature short description]". Title must follow the Conventional Commit Specification(https://www.conventionalcommits.org/en/v1.0.0/).
[x] Linked all relevant issues
[ ] Include screenshot(s) showing how this pull request works and fixes the issue(s)

Screenshot of the downloaded app showing properly notarized. Look for text ...Apple checked it for malicious software and none was detected....


Panel participants need updating

What it says on the title. The details in the schedule are from last year.

No that is this year's panel. Sculptor has to work with the marble he has got. Possibly won't have Van though if he is not coming.

I presume we're talking about this panel.  If so, have we asked any of the people on that list?

Well Van is probably not even coming and the rest, as Sarah said, are the
regulars (Russel Winder being the other one who is not listed), I will add
to the panel during the conference, basically we the crew just keep an
eye on who is witty during the conference.
Micheal Foord and Larry Hastings deal with technical python questions but
we ask the panelists to sum up the conference, so we will want Sarah from
the science track, someone from Djangogirls, someone from education track,
etc.
On 5 July 2015 at 19:34, Peter Inglesby<EMAIL_ADDRESS>wrote:

I presume we're talking about this panel
http://www.pyconuk.org/abstracts/#the-pycon-uk-panel. If so, have we
asked any of the people on that list?
—
Reply to this email directly or view it on GitHub
https://github.com/PyconUK/pyconuk.org/issues/47#issuecomment-118649248.


Add Nest control functionality

The idea here is to use the house as a battery, over-heating and over-cooling the house when extra power is being generated.

[x] add config options to config.yml to control the max/min temperatures for heating and cooling
[ ] integrate an existing, license-compatible, Python-based Nest control library
[ ] cache Nest settings, to avoid abusing Nest's API (I use that acronym loosely)
[ ] adjust Nest settings only when power levels have not been oscillating for the past X minutes

nestcontrol seems like the way to go.


Unable to build storage container in latest demo due to too thin base image

Building storage container keeps failing on the latest code due to missing dependencies, most probably caused by switching the base image.
A workaround is to switch to a full-blown image (or add missing packages).
--- a/deploy/docker/base/Dockerfile
+++ b/deploy/docker/base/Dockerfile
@@ -4,7 +4,7 @@
 ##  Please, refer to the LICENSE file in the root directory.
 ##  SPDX-License-Identifier: BSD-3-Clause
 ##
-FROM python:3.8.12-slim
+FROM python:3.8.12

 RUN pip3 install --upgrade pip

Error message
#6 2.200   ERROR: Failed building wheel for netifaces
#6 2.201   Running setup.py clean for netifaces
#6 2.291 Failed to build netifaces
#6 2.348 Installing collected packages: pytz, netifaces, netaddr, msgpack, wrapt, rfc3986, PyYAML, pyparsing, pbr, lxml, iso8601, stevedore, pynacl, packaging, oslo.i18n, os-service-types, debtcollector, bcrypt, paramiko, oslo.utils, oslo.config, keystoneauth1, oslo.serialization, python-keystoneclient
#6 2.405   Running setup.py install for netifaces: started
#6 2.598   Running setup.py install for netifaces: finished with status 'error'
#6 2.600   error: subprocess-exited-with-error
#6 2.600
#6 2.600   × Running setup.py install for netifaces did not run successfully.
#6 2.600   │ exit code: 1
#6 2.600   ╰─> [16 lines of output]
#6 2.600       running install
#6 2.600       running build
#6 2.600       running build_ext
#6 2.600       checking for getifaddrs...not found.
#6 2.600       checking for getnameinfo...not found.
#6 2.600       checking for socket IOCTLs...not found.
#6 2.600       checking for optional header files...none found.
#6 2.600       checking whether struct sockaddr has a length field...no.
#6 2.600       checking which sockaddr_xxx structs are defined...none!
#6 2.600       checking for routing socket support...no.
#6 2.600       checking for sysctl(CTL_NET...) support...no.
#6 2.600       checking for netlink support...no.
#6 2.600       building 'netifaces' extension
#6 2.600       gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DNETIFACES_VERSION=0.11.0 -I/usr/local/include/python3.8 -c netifaces.c -o build/temp.linux-aarch64-3.8/netifaces.o
#6 2.600       unable to execute 'gcc': No such file or directory
#6 2.600       error: command 'gcc' failed with exit status 1
#6 2.600       [end of output]
#6 2.600
#6 2.600   note: This error originates from a subprocess, and is likely not a problem with pip.
#6 2.601 error: legacy-install-failure
#6 2.601
#6 2.601 × Encountered error while trying to install package.
#6 2.601 ╰─> netifaces
#6 2.601
#6 2.601 note: This is an issue with the package mentioned above, not pip.
#6 2.601 hint: See above for output from the failure.
------
executor failed running [/bin/sh -c pip3 install -r deps/requirements.txt]: exit code: 1
ERROR: Service 'storage' failed to build : Build failed

I can't replicate on x86 (PC and Mac). Based on the other issue, I assume you're using an M1 Mac, but I don't have one to test.
It seems netifaces doesn't provide a binary for aarch64: https://pypi.org/project/netifaces/#files

You are most probably correct. And given the status of that project - https://github.com/al45tair/netifaces/issues/78 - it might be a while if ever that it starts being supported as wheel.

Hi @livenson, in the latest release we added gcc when creating the Storage image so it works on M2. Would that work also for an M1 device?

Works good, thanks!


How can we mock two responses for same request i.e, one on page load and other one on page request.

I have a scenario where I need to mock a http request two times. i.e., on page load it should return 401 status and on page when I fill the username, password and click on login button, it will request the same url and should return 200 status.
Below is the code snippet:
proxy.onLoad.when('GET','http://localhost:8080/login')
            .respond(function(method, url){return [401,{"message":"Authorization has been denied for this request."}];});

browser.get('http://localhost:8888');

proxy.when('GET','http://localhost:8080/login')
            .respond(function(method, url){return [200,{"message":"Authorization has been sucess for this request."}];});

I'm getting same response for onload and onpage request i.e., 401 status.
Please let me know how can I mock such scenario's.

This has nothing to do with the proxy but is a httpBackend question.  However the short answer is that you can't assign multiple response functions to the same endpoint.  You have to assign one response function the does what you want, namely return [401,{"message":"Authorization has been denied for this request."}] the first time it is called and [200,{"message":"Authorization has been sucess for this request."}] the second time.


Update Hyperdrive Config Origin model to include new fields

Description
This PR updates the Hyperdrive API model to include new forthcoming fields. Some downstream changes in https://github.com/cloudflare/terraform-provider-cloudflare will depend on these changes.
Has your change been tested?
Tests have been updated to account for the new fields.
Types of changes
What sort of change does your code introduce/modify?

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

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] This change is using publicly documented in cloudflare/api-schemas
and relies on stable APIs.

v2 has these changes at https://github.com/cloudflare/cloudflare-go/pull/2742. up to you which one you want to use in Terraform since both are supported.


Big Endian Operators

Summary
Previous PRs (#25, #35, #68) assume that the labels are little endian.
We (@mrossinek, @pbark, @woodsp-ibm) have discussed the endian and adopted the big endian for drivers and operators.
Qiskit qubit operators are little endian (https://github.com/Qiskit/qiskit-terra/issues/1148), so we need the conversion of the endian in mapper.
This PR depends on #68.

thanks @ikkoham !


The outcome somehow ignores some letters of the code...

Challenge Waypoint: Concatenating Strings with the Plus Equals Operator has an issue.
User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
// Example
var ourStr = "I come first. ";
ourStr += "I come second.";

// Only change code below this line

var myStr = 'This is the first sentence. ';
myStr += 'This is second sentence';

I have checked few times the code, and I can't figure out why the outcome it's missing few letter, nor why the code does not work

Nevermind, after refreshing page, I realized there were no bug, just a weird malfunction in the outcome screen and some typos on the text that prevent me from passing the exercise.


API specification must include requirement for Docker-Distribution-API-Version header

For registries to work with docker 1.5rc and the v2 protocol, the Docker-Distribution-API-Version must be present with the value "registry/2.0". This requirement should be added to the API specification.

Note that this header was put in place to declare the api version when a "/v2/" endpoint responds with a 401. The caller can't infer that the the registry doesn't implement the v2 api from just this information, since a v1 registry may respond in the same manner. Really, this header is a declaration of the max api implemented by the service and should be included regardless of the url (v1 or v2) if the server can support v2. Effectively, one can disable v2 support by excluding this header.
See #423 for details.


Allow submitting issues for anybody

Use GitReports for this:
https://gitreports.com/issue/ColasNahaboo/cgibashopts
And document it in Readme.md and personal wiki page

Works, tested via #2

Works, tested via #2


Make it possible to style columns in table header by its key

Add "column key" as a default class name for columns in table header.
Please tell me to write more tests if I missed something :smile:

I've updated the code and tests as well. Have a look when you have time @glittershark :smile:

Nice! Thanks for this

Good job, my friend ! Hire me !

Thanks for adding this! Found myself needing it today. :)


Creating a GitHub Action that tweets new Awesome Entries

Hey Awesome people,
Problem:
I love awesome lists but they do have one essential problem. It is very hard to follow new projects on awesome lists.
It would be nice to create a newsfeed for readers to stay informed about new entries.
Solution.
We created a simple GitHub Action that creates tweets based on the commit messages. Contributors can define there own custom tweet message by defining the Pull Request title in a corresponding way.
The script checks if the last commit message on the main branch contains https and creates a tweet based on the corresponding line.
https://github.com/protontypes/awesome-twitter-action

Add the Github Action Script to .github/workflows/tweet.yml
Create a Twitter Developer Account.
Add the Login data to your project secrets.
Activate your Github Actions by pressing the Activate GitHub Action for this Projects button on the Action Tab of your project.
Create a Commit Message with an URL. Since the title of a pull request is included in the commit message, contributors can create user-specific Twitter messages.

It would be nice to get your feedback. The action is already integrated here:
https://github.com/protontypes/awesome-robotic-tooling
Do you see any better integration that might be more intuitive and fit better in the Awesome list workflow? At the moment we assume that every commit is always a new project entry.

I am looking for a first project would this be a good fit for a beginner.

New entries are already tweeted

Use the google earth app to stretch size of pictures material

Follow this person margo2016tepa


Submit to WorkflowHub

At time of writing, the pipeline appears technically ready so submission to WFH except for the testing, which might be doable by generating tests from the results (?)

 One point of attention: relative paths to images in the README don't work on WFH. Should be absolute paths back to the repo.


USHIFT-2378: change sonobuoy command to match  the CNCF readme

change the  sonobuoy invocation command to match the  readme

/assign @pacevedom

@eslutsky , can you link the README in the PR description?

/cherry-pick release-4.15

/cherry-pick release-4.15


Added export PDF functionality

Using wkhtmltopdf is always tricky, you might want to check the manual, there are a few options for setting document margins and other interesting details https://wkhtmltopdf.org/usage/wkhtmltopdf.txt
  ...
  -B, --margin-bottom <unitreal>      Set the page bottom margin
  -L, --margin-left <unitreal>        Set the page left margin (default 10mm)
  -R, --margin-right <unitreal>       Set the page right margin (default 10mm)
  -T, --margin-top <unitreal>         Set the page top margin
  ...

Regarding to syntax highlight, you might need to check if the current syntax highlighter CSS is restricted to @media screen, as that CSS is not rendered if you "print" the document.
There are also some CSS tricks that might be useful https://www.smashingmagazine.com/2015/01/designing-for-print-with-css/
In Rails, there are some gems to use wkhtml2pdf in a friendlier manner: wicked_pdf and pdfkit. If we end up doing the effort to get this right, it might be useful to have a wrapper library for haskell..


Use htmlDecode instead of unescape

Currently _.unescape() is used to replace entities while html is being converted to text, however this function only replaces a limited number of entities resulting in only a part of the string being unescaped in a few cases. Because of this I've replaced it with Str.htmlDecode().
For example   is not unescaped by _.unescape() but is added in the replace function in line 36.
https://github.com/Expensify/expensify-common/blob/925e62744f784a92c3ad8947aabfc21c93bec221/lib/ExpensiMark.js#L23-L39
Fixed Issues
$ https://github.com/Expensify/App/issues/19789
Tests

What unit/integration tests cover your change? What autoQA tests cover your change?

Added html entities to the unescape test in ExpensiMark-test.js.
Previously & &amp; &lt; < was being unescaped to & & < <, now it'll be unescaped to & & < <.

What tests did you perform that validates your changed worked?

Made sure all unit tests passed.

QA

What does QA need to do to validate your changes?

Test the function with other HTML entities to verify that they are being unescaped or simply run all unit tests.

What areas to they need to test for regressions?

Directly pushing these changes to other repositories such as Expensify/App may cause some regressions.
While pushing these changes a few other changes have to be made. There are a few occurrences of Str.htmlDecode() being used on top of parser.htmlToText(), these will have to be changed to just parser.htmlToText() or it may result in a double unescape.

I have read the CLA Document and I hereby sign the CLA

@therealsujitk since the related issue currently does not have an accepted proposal, and is on hold, I'm going to hold off reviewing for now

@alex-mechler Assign me here, will handle this as a part of https://github.com/Expensify/App/issues/19789

Assign for review or assign as assignee?

I don't think we have assignee for PRs. So I think I will just be a reviewer

I had to add a review manually, not sure why we can't be asked for review. I think this is a known issue as we encountered this before


Subcommand structure should be correctly passed to application

Currently, one can specify a Description, Usage, and ArgsUsage for a subcommand. Currently however, the subcommand's Description is copied into the App's usage (unless the subcommand has no description, then its usage is copied into the App's usage), and the other fields are ignored. This means that if a subcommand specified a custom ArgsUsage, it cannot be used by a help template.
This PR fixes these issues by just copying over the fields as normal (as is currently done with the Flags, HideHelp, Before, After, and Action fields). To preserve the old default behavior, the default SubcommandHelpTemplate now uses the description if provided or falls back to the usage.
This leads to significantly fewer surprises when creating a custom subcommand help template.

Agreed, that existing conditional is pretty confusing; thanks for this!


ClientSSLSecurity now accepts a ca-certificate.

This is necessary if the server uses a self-signed certificate, which we want to trust, by setting it as the CA-certificate of our client.
+Test

Thanks a ton @Mik13 :+1:


Redis Keys / Redis Memory not shown in topom dashboard

Is this a regression?
No
Description
Redis Keys / Redis Memory not shown in topom dashboard
is this normal? will it be fixed? just want to know why that's all

Please provide a link to a minimal reproduction of the bug
No response
Screenshots or videos

Please provide the version you discovered this bug in (check about page for version information)
latest pika 3.5.2

Anything else?
No response

@AlexStocks what's the feedback to this?


Fix some typos (found by codespell and typos)

Description
Related issue: #1001
Motivation and Context
I noticed a typo while using the software.
How has this been tested?
Manual review of the changes.
Screenshots (if appropriate)
Types of Changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[x] Documentation content changes
[ ] Other (please describe):

Checklist

[x] I have read the contributor guide.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

coverage: 91.591%. remained the same
when pulling aa2a890bf4b72c161e85e12fbe5c1788aaf5a0ad on stweil:typos
into c945d7d9ef5efdccb2d7b41b914ff50ea6f7b49c on rdmorganiser:main.

why was this merged on the main branch? Thought we have currently the dev-2.2.0 for that...

My mistake :(

we need to check if the changes to translations in the migration files require new migrations..
and now the dev-2.2.0 related branches need to be rebased to this new main ..

I think we should rebase dev-2.2.0 after we merge most of the feature branches.

Migrations and translations seem ok. The changed migrations are old, and the translations were changed in the same way in the code and the .po files.


Add a subtitle property to LiturgicalDay object

As talked about in #295, we should add a property of subtitle to LiturgicalDay object, which could be used for alternative celebration names, for example for:

Sunday of the Word of God (3rd Sunday of Ordinary Time);
Sunday of the Divine Mercy (2nd Sunday of Easter);
Mission Sunday (second last Sunday of October);
Good Shepherd Sunday (5th Sunday of Lent);
Commemoration of the Lord’s Supper (Holy/Maundy Thursday);
Eighth Day within the Octave of the Nativity of the Lord (1 January):

I have no idea if mary_mother_of_god key value should be the celebration name and Eighth Day within the Octave of the Nativity of the Lord subtitle, or vice versa.

The main/standard celebration name would be the general name of the celebration (e.g. nth Sunday in Ordinary Time and key name would be based on it.

Thank you for the feature request. But we should discuss before adding it to a milestone, especially that I'm the only one developer on this project (unfortunately) and I can't do yet miracle 😄

I’m sorry for being to eager. :wink:

@emagnier @tukusejssirs i'd like to start working on some of the blockers. Is there any current objection to this? I'd like to pick back up on some of these now that my busy summer is over.

I think this one is a good candidate.
What’s your take on this? Currently, the localization files are mainly key-value pairs, with the values being strings used to name the corresponding liturgical day definition. Instead of being a string, it should probably be an object. Maybe something like this?
"liturgical_day_key": {
  title: "The liturgical day name", // or leave it undefined if this is generated automatically, e.g.: 2nd Sunday of Easter
  subtitle: "The liturgical day subtitle" // the optional subtitle
}

To push the ideas a bit further (this is off-topic here, but just to give a vision of how things could evolve later, maybe to guide the initial choices), I would consider merging the metadata from the martyrology file with the English locale file since English is our default language in this project, and we must have at least an English localization. The other localization files would only contain what is relevant to translate. I think this would give us more clarity (fewer scattered metadata across different file types, simplifying the code and documentation to manage all of this), and it would offer better tooling for string composition using a localization library in the future.


Change default values

Hi, exactly where on the code can I change the default opacity values that appears on the side bar menu?
I tried on the js but didnt work, maybe not the correct line or place.
Can I have some help with that?
Thanks

The options are set in Leaflet.StyleForms.js Starting from line 49 you can see that the value is set by the current value of the feature. If the feature does not have a value the default would be 1.
Leaflet has a default value of 0.5 for opacity, which is why this value is shown in the demo

thanks, that helps :)


Make checkbox fields explicit

@sadiekelly sorry to bug again... I thought this covered all the bases for checkbox fields by looking for fields with ___x in the name, but having looked again at some of the data files it's not clear to me that a lot of the symptom data wasn't also recorded as checkbox-like - e.g., the Guinea, Ghana & Uganda-v2 (these are just the first ones I checked) seem to have a data structure that suggests they use 0 as a default for admission symptoms/comorbidities, even though there are 'unknown' as options.
Any insights?

@sadiekelly sorry to bug again... I thought this covered all the bases for checkbox fields by looking for fields with ___x in the name, but having looked again at some of the data files it's not clear to me that a lot of the symptom data wasn't also recorded as checkbox-like - e.g., the Guinea, Ghana & Uganda-v2 (these are just the first ones I checked) seem to have a data structure that suggests they use 0 as a default for admission symptoms/comorbidities, even though there are 'unknown' as options.
Any insights?

hi @pipliggins for those databases you've mentioned, it is fine to treat these not as checkboxes - they were either radio button or dropdown lists for the Yes/No/Unknown options meaning that one option should be selected and if none were selected then the cell in the csv for that data item would just be blank, there would not be a default entry for these. I think your approach of identifying checkbox fields by the ___x pattern sounds sensible, this will definitely cover all redcap databases that used checkboxes. I think other database formats didn't tend to use checkboxes, it was quite a redcap thing. I can do a quick look through the data dictionaries to find non-redcap setups and look for any rogue checkboxes if that would be helpful?

Hi @sadiekelly if you have the spare capacity that would be great! The well filled-in radio fields make spotting these easily a bit more difficult, good to know.

@sadiekelly sorry to bug again... I thought this covered all the bases for checkbox fields by looking for fields with ___x in the name, but having looked again at some of the data files it's not clear to me that a lot of the symptom data wasn't also recorded as checkbox-like - e.g., the Guinea, Ghana & Uganda-v2 (these are just the first ones I checked) seem to have a data structure that suggests they use 0 as a default for admission symptoms/comorbidities, even though there are 'unknown' as options.
Any insights?

hi @pipliggins for those databases you've mentioned, it is fine to treat these not as checkboxes - they were either radio button or dropdown lists for the Yes/No/Unknown options meaning that one option should be selected and if none were selected then the cell in the csv for that data item would just be blank, there would not be a default entry for these. I think your approach of identifying checkbox fields by the ___x pattern sounds sensible, this will definitely cover all redcap databases that used checkboxes. I think other database formats didn't tend to use checkboxes, it was quite a redcap thing. I can do a quick look through the data dictionaries to find non-redcap setups and look for any rogue checkboxes if that would be helpful?

Hi @sadiekelly if you have the spare capacity that would be great! The well filled-in radio fields make spotting these easily a bit more difficult, good to know.

hi @pipliggins I've checked through the data dictionaries, most are REDCap format so will be covered by the ___x. Of the couple that are not, generally checkboxes were not used. I think predicovid may have been one, and the checkbox fields there are not mapped so no changes needed. Otherwise looks like the checkboxes have been accounted for so all good!

@sadiekelly sorry to bug again... I thought this covered all the bases for checkbox fields by looking for fields with ___x in the name, but having looked again at some of the data files it's not clear to me that a lot of the symptom data wasn't also recorded as checkbox-like - e.g., the Guinea, Ghana & Uganda-v2 (these are just the first ones I checked) seem to have a data structure that suggests they use 0 as a default for admission symptoms/comorbidities, even though there are 'unknown' as options.
Any insights?

hi @pipliggins for those databases you've mentioned, it is fine to treat these not as checkboxes - they were either radio button or dropdown lists for the Yes/No/Unknown options meaning that one option should be selected and if none were selected then the cell in the csv for that data item would just be blank, there would not be a default entry for these. I think your approach of identifying checkbox fields by the ___x pattern sounds sensible, this will definitely cover all redcap databases that used checkboxes. I think other database formats didn't tend to use checkboxes, it was quite a redcap thing. I can do a quick look through the data dictionaries to find non-redcap setups and look for any rogue checkboxes if that would be helpful?

Hi @sadiekelly if you have the spare capacity that would be great! The well filled-in radio fields make spotting these easily a bit more difficult, good to know.

hi @pipliggins I've checked through the data dictionaries, most are REDCap format so will be covered by the ___x. Of the couple that are not, generally checkboxes were not used. I think predicovid may have been one, and the checkbox fields there are not mapped so no changes needed. Otherwise looks like the checkboxes have been accounted for so all good!

Fab, thanks for checking this @sadiekelly!


This isn't an issue, but rather solving some problems that I had: '/Werror=incompatible-pointer-types' and 'C:\Users\Name\AppData\Roaming\..\Local\Google\Chrome\User Data\Profile 1\Network\Cookies'

The first was this error on the C++ compiler: '/Werror=incompatible-pointer-types'
The second the was this: 'C:\Users\Name\AppData\Roaming\..\Local\Google\Chrome\User Data\Profile 1\Network\Cookies'
The first issue is solved by downloading this and then extracting it:  https://github.com/PetterS/quickjs/files/12180440/quickjs-1.19.2-cp311-cp311-win_amd64.zip
You then "pip install path-to-said-file"
The second issue is solved by simply closing Chrome completely.
I have to thank you guys very much for this. This will be very useful in my projects to come.

@SomethingSimple4
Thanks for the report!


Custom Shader doesn't work on main menu but does on every other screen

I don't really know what is wrong, i followed the tutorial on the geode page and created menu-shader.fsh on the texture pack folder

you have geodify installed. disable/remove it completely or use its settings menu to disable it for menus you want to see menu shaders in.


Best way to add Context Vector at bottom of  UNet

Hello,
I am looking for a way to concatenate the vector at the bottom of a UNet - octree depth = 0 - with a global context vector before the upsampling portion of the network. I am not clear on the best way to accomplish this. I was looking at the col2octree function or ocnn.octree_update but didn't see a clear example.

You can refer to the O-CNN-based LeNet or ResNet. These networks are used for shape classification, and a global shape feature is produced.

Would you use octree2voxel for a 1D vector? Can I simply concatenate the data at depth 0 and then pass through the octree deconvolution layers?
For example:
data = self.pool(data,octree)  # assume data is at depth 0 - shape = (1, 256,1,1)
data = torch.cat((data,context_vector)) # new tensor shape is (1,512,1,1)
data = self.deconv(data,octree) # octree deconv layer.


Sending several hundred requests

What version of WordPress, PHP and Timber are you using?
Wordpress version : 5.3
PHP version : 7.3
TImber version : 1.12.0
How did you install Timber? (for example, from GitHub, Composer/Packagist, WP.org?)
Installed the latest version via WP plugin
Hi Support,
We are using the Timber on our WP site which has 4k - 5k articles and hosted on WP Engine. We are using the native WP search ( native WP Query, no any search plugin ) to create a search feature on the site. But it is causing the slow performance on the search because of the timber-library is sending several hundred requests for display.
Do you have any idea or plugin settings to make this run a little faster?
Here is the screen shot provided from WP Engine

And code example
search.php

search.twig

Let me know you need more information.
Thanks

@rhm-dennis hmmmm, nothing comes to mind immediately. But some ideas ...

Try some wolf-fencing to see if you can isolate which segment of code is driving the requests
I notice rushhour_ functions in there? Also another thing to isolate. I've found that more plug-ins than you might expect use Twig so it could be something unrelated it to Timber
Disable the various includes that you have in search.twig. I've sometimes screwed up and had unintended include loops in sites I've built

hope that helps!


selectConstraint should accept a string

As written in the docs, even in the next version, the property selectConstraint in the options should accept a string 'businessHours'.
Currently, this prevents the correct use of the constraints in case of different business hours each day because an array of BusinessHours doesn't work either, only an object BusinessHours works but we can't specify different hours for each day.
You can find the issue in the index.d.ts file, interface SelectionOptions.
Thanks

this issue deprecated.
<EMAIL_ADDRESS>released without Jquery,
try use<EMAIL_ADDRESS>with fulcalendar plugins


Feature/better logging

Description

Adds timber logging. Logs sync errors to Instabug/Mixpanel
Changes

Changed Log -> Timber

Issues

Tests

This code has been tested in the following ways:

Tasks:

[ ] Logged in to the application
[ ] Fill out a snapshot for a new family
[ ] Fill out a snapshot for an existing family
[ ] Fill out priorities for a snapshot
[ ] View a family and it's priorities

API Level:

[ ] API Level 19
[ ] API Level 22
[ ] API Level 25

Screen Size:

[ ] 7" screen size
[ ] 8" screen size
[ ] 10" screen size


gentoo-update update full

Where do I put my API key?

Follow these steps to use Sendgrid API:
Install sendgrid python library (from GURU):
# unmask library and it's dependencies
dev-python/sendgrid ~amd64
dev-python/python-http-client ~amd64
dev-python/starkbank-ecdsa ~amd64

# install lib
sudo emerge --ask dev-python/sendgrid

Add API key and other info to env variables
export SENDGRID_TO='<to_address>'
export SENDGRID_FROM='<from_address>'
export SENDGRID_API_KEY='<api_key>'

Send the report (if the update was done already)
gentoo-update report --send email

Will add this info to README later this week 🙂

Two things can you put gentoo-update update and report is the same string? 'Cause I couldn't make it work.  Second, I was semi-successful with gentoo-update report -s email, but I didn't receive email and not in my spam folders?

Can mode and report be run from gentoo-update? I tried and it gave me an
error.
bbox /home/hangint3n # gentoo-update update -m full -s email
usage: gentoo-update [-h] {update,report,version} ...
gentoo-update: error: unrecognized arguments: -s email
bbox /home/hangint3n # gentoo-update update -m full report -s email
usage: gentoo-update [-h] {update,report,version} ...
gentoo-update: error: unrecognized arguments: report -s email
bbox /home/hangint3n #
On Fri, Dec 1, 2023, 10:12 a.m. Stepan K. @.***> wrote:

Will add this info to README later this week 🙂
—
Reply to this email directly, view it on GitHub
https://github.com/Lab-Brat/gentoo_update/issues/30#issuecomment-1836283408,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4SVI36ARWE6PDJYPAXCVULYHHXVRAVCNFSM6AAAAABAC6Z3BKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZWGI4DGNBQHA
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

can you put gentoo-update update and report is the same string?

You can just use && to connect them 🙂
gentoo-update update -m full && gentoo-update report -s email

but I didn't receive email and not in my spam folders?

The issue is probably somewhere on the Sendgrid side...
Does your output looks like this?
2959553524c9 / # gentoo-update report -s email
email was sent successfully!

Also, is the report correctly generated? It should look something like this
2959553524c9 / # gentoo-update report
==========> Gentoo Update Report <==========
update status: SUCCESS
processed packages:
--- sys-libs/glibc 2.37-r3:2.2->2.37-r7:2.2
--- app-arch/libarchive ->3.7.1:0/13
--- app-crypt/rhash ->1.4.3
--- dev-libs/libuv ->1.46.0:0/1
--- dev-util/meson 1.1.1->1.2.3
--- dev-libs/jsoncpp ->1.9.5:0/25
--- dev-util/cmake ->3.27.7
--- net-libs/nghttp2 ->1.57.0:0/1.14
--- net-misc/curl 8.1.2->8.4.0

Disk Usage Stats:
Mount Point /
Free Space 269G => 269G
Used Space 161G => 161G
Used (%) 38% => 38%

Yup both of those outputs look like what I received running gentoo-update report -s email.  Thanks for the prompt reply.

Then it could be 2 things:

You have a very secure email provider that just doesn't deliver emails flagged as spam, for instance ProtonMail might do that.
There is some misconfiguration in Sendgrid.

In the future (maybe in 1-2 months) I am planning to a add a simpler mechanism to send out emails, people have been complaining about Sendgrid a lot 😓

I've read that come February Gmail is going to make change to there secure mailing that might make it more difficult to use.

Weirdly I ran the command gentoo-update report -s email
And I got a notification of a successful send, but this time I never got
the email. Just to be sure I did check the spam folder.
On Wed, Dec 13, 2023, 1:33 p.m. Stepan K. @.***> wrote:

Then it could be 2 things:

You have a very secure email provider that just doesn't deliver
emails flagged as spam, for instance ProtonMail might do that.
There is some misconfiguration in Sendgrid.

In the future (maybe in 1-2 months) I am planning to a add a simpler
mechanism to send out emails, people have been complaining about Sendgrid a
lot 😓
—
Reply to this email directly, view it on GitHub
https://github.com/Lab-Brat/gentoo_update/issues/30#issuecomment-1854505114,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4SVI37FKMNZVF3KJ7A4PELYJHYGTAVCNFSM6AAAAABAC6Z3BKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJUGUYDKMJRGQ
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Finally got around to experiment with local SMTP relays.
In the end I've decided not to implement the email sending mechanism into gentoo-update because it already works really well with relay tools such as msmtp, mailx or sendmail.
It could be a bit of a hassle to set it up, but afterwards you can just pipe the output from the reporter to the relay to send the email:
echo -e "Subject: Gentoo Update Report\n\n$(gentoo-update report)" | msmtp -a default<EMAIL_ADDRESS>
There are a lot of info out there how to set up Gmail (or other email providers...) with aforementioned tools, and I also wrote a blog post about it (Link here).
In the future I will probably implement report formatting in HTML to make it look a bit better, but for now I'm considering all email-related issues resolved. Closing the issue now 🐱


pgcraft sampling using hwmap

 hwmap: expose a function to inspect available accelerations, maybe rename to  hwmap: expose a function to inspect available image layouts as  a NGLI_IMAGE_LAYOUT_{DEFAULT,NV12,YUV} can be used in both cases (cpu / hw-interop).

 hwmap: expose a function to inspect available accelerations, maybe rename to  hwmap: expose a function to inspect available image layouts as a NGLI_IMAGE_LAYOUT_{DEFAULT,NV12,YUV} can be used in both cases (cpu / hw-interop).

Done:

hwmap: expose a function to inspect available image layouts
pgcraft: use hwmap to inspect available image layouts


working on parameterzing allowed hosts to environment (product, dev, …

…test); setting login/logout redirect URLs based on environment

To confirm, running development locally will not be possible against the current production api. Is there a need for this?

No, I don't need to run the API locally.
My changes only partially address this todo. Until their are multiple deployments of the APIs, the issue can't be fully addressed.

@bilalshaikh42 this is ready for merging

This will be preventing local  development frontends from querying the api. I don't see a reason to do that. I did overlook the redirect URI however. I can include that change in the next push

Access from localhost is still allowed. Eventually this access should be removed. But this can't be removed yet.
This allow fixes an issue with the login/logout redirect URLs


You need to add a step to the official guide to prevent a specific error

Device
iPhone 7
Version
ios 15.8.1
Passcode?

[ ] Passcode is enabled.

Start going into detail..
after the systemd usbmux step, you need to add this please:
sudo systemctl mask fwupd-offline-update.service
sudo systemctl mask fwupd-refresh.service
sudo systemctl mask fwupd-refresh.timer
sudo systemctl mask fwupd.service
thanks, otherwise the iphone fails to enter download mode after exiting DFU via CLI
Familiarity with palera1n

[X] I am familiar with palera1n and how to use it!

Familiarity with CLI

[X] I am familiar with the command-line!

Hi! This can solve the download mode error? (On mi ipad only still on black screen and dont do nothing, only appear that error)

This seems like a more temporary solution than a proper fix dont you think?


Integration Specs Completed

The 'integration specs' of the project completed on the branch 'integration_specs':

This was done through pair programming
-  The N+1 problem was solved when fetching all posts and their comments for a user.
--- Before fixing the N+1:

---After fixing the N+1:

-An Integration Specs was written, using the 'Capybara' gem' for the following:

User Index page
User show page
User post index page
User Post show page

Thanks @OyePriscilla .


remove legal documents

they are unused, these are from zkSNACKs era
see https://github.com/WalletWasabi/WalletWasabi/pull/12980
there are 3 files in the backend code where legal document is still mentioned/used.
Can these be removed aswell?
feel free to push on this branch
https://github.com/WalletWasabi/WalletWasabi/blob/121d7c9d2f08a23ce3eb2aac11a45f2101903608/WalletWasabi.Backend/Controllers/WasabiController.cs#L21
https://github.com/WalletWasabi/WalletWasabi/blob/121d7c9d2f08a23ce3eb2aac11a45f2101903608/WalletWasabi/Backend/Models/Responses/VersionsResponse.cs#L13
https://github.com/WalletWasabi/WalletWasabi/blob/121d7c9d2f08a23ce3eb2aac11a45f2101903608/WalletWasabi.Backend/Controllers/SoftwareController.cs#L19

Good initiative! I really don't remember how many times I have removed this sh*t but it resists to die. Now, there are more things to remove like the LegalController for example, and I am sure there are even more. We have to go to previous versions and see how they behave when the legal documents are not accessible anymore.

marked as draft, as I initially planned to open as draft because of such things.


Reporting on Fibaro FGS211 does not work

Hi there. I have the same problem, though with a FGS211 (Fibaro 1x3kW relay switch). I have the latest HA, latest Z-Wave JS to MQTT. This bug has been present for several months now. It had first appeared over 5-6 months ago, then disappeared for a short period, and returned to never disappear again. I have 8 of these relays, but only two of them are used using the physical switch inputs on the device - I use them to control garage door and the switch is used to trigger it manually. The relays are configured to turn off automatically after one second - they only signal "change" request to a motor controller (not a zwave device).
If the relay is switched on via HA, it works correctly. When it turns off automatically after one second it is also correctly shown in HA (zwavejs). But when controlled using the connected switch it doesn't seem to propagate back to HA (nor zwavejs). The statistics on the device does show messages received from it.
Attached you can find a "silly" level log, the device in question is Node 006. What can be seen in the log is:

I use the physical switch 3 times (to achieve "open gate", "stop gate", "close gate") - each press turns the relay on and it turns it self off automatically after 1 second.
Node re-interview
Repeat of 1 (three on/auto-off actions)

Thank you for looking into this.
zwavejs_2021-11-13.log
Originally posted by @jandado in https://github.com/zwave-js/zwavejs2mqtt/issues/1921#issuecomment-968121052

I think this has to do with Fibaro's weird choice to reuse the double switch firmware on their single switches. Z-Wave JS cannot detect that the endpoints are useless this way.
@jandado Can you test this file as it is described here?
You'll have to re-interview the device and the value IDs you use are likely going to change (from endpoint 1 to 0).

Thank you @AlCalzone. Sorry it took a while - I ran into an issue with the import of param #16 ("$import": "~/templates/master_template.json#state_after_power_failure_off_prev"), but was able to resolve that by manually importing required block.
There are now three binary switches (6-37-0, 6-37-1, 6-37-2), but it is working. Using the physical switch turns on the now available 6-37-0, and it turns itself of automatically. Turning on the 6-37-1 from HA / zwavejs works as previously, 6-37-2 does nothing - as previously.
Perhaps there should only be one binary switch (actual load on the relay) and two "sensors" (there can be two switches connected to the device). Is that achievable? But even if it stays this way it is much better than not having the state change registered :)
Would you need any more logs captured?

I would expect the behavior you describe. After the change, 6-37-1 should be ignored, but we currently don't have a compat flag to hide everything but the root endpoint 0.
Do you have a second switch attached by any chance so you can capture what's sent in that situation (if anything)? I wonder if we need to preserve endpoint 2.

I don't have a second switch attached to it, but I think it is worth trying it out to settle the behavior once and for all.
The problematic part of having endpoint 0 and 1 as it is now is that they don't work in sync, yet work on the same single (relay) switch. So currently turning 0 on keeps 1 showing as off, turning 1 on does nothing. Turning 1 off turns the relay off, though 0 stays showing as on - and vice versa. This behavior can not even be worked around in HA using a group of these two switches.
Re-interviewing the node gets them back in sync (though the correct state of both is not propagated back to HA - integration reload is required). So, ideally there should really be only one switch.
I will let you think about this :) In the mean time I will find a spare 30 minutes to try out attaching a second switch to the device and report back as soon as I get the log.

I think you need to ignore endpoint 1 for now. Question is whether exposing 2 is of any use.

Reporting back with second switch connected, @AlCalzone. Find attached a silly level log containing:

S2 turned on, back off (manually) - no impact on relay switch,
re-interview node just to make sure the device state / config is in the log,
repeat of step 1,
S1 turned on to show the difference - the relay turned on and automatically back off after one second - repeated three times to open/stop/close the garage door (still irrelevant for the purpose of this test, just to explain the repetition)
zwavejs_2021-11-14.log

I hope this helps.

Thanks, I do see all of that in the log. Looks like keeping endpoint 1 and 2 then makes more sense, but we need to map the root reports to endpoint 1 so they reach the application.

Can you test this version of the file to be sure?
The reports should now come in on endpoint 1 - endpoint 0 should disappear again.

I can confirm the behavior is as you describe, @AlCalzone - and I am more than happy with it :)

Worling with Current version: 0.1.48


SA1118 Cannot be suppressed in attributes

Hi,
I have an issue where I want to use an attribute RequiredIfTypeIsAttribute (a custom attribute for our project) where one of the parameter is a long line which upon code cleanup gets rewritten to multiple lines:
        [RequiredIfTypeIs(
            nameof(Type),
#pragma warning disable SA1118
            new[]
            {
                MyEnum.Value1,
                MyEnum.Value2,
                MyEnum.Value3,
                MyEnum.Value4,
                MyEnum.Value5,
                MyEnum.Value6,
                MyEnum.Value7,
                MyEnum.Value8,
                MyEnum.Value9,
            })]
#pragma warning restore SA1118
        public List<Guid>? Ids { get; set; }

I had to disable SA1118 on this line because I cannot instantiate this array using a const. How can I fix this?

Hi! The suppression in your code snippet works fine for me. Suppression is handled by the compiler, so if it doesn't work for you then file an issue here: https://github.com/dotnet/roslyn.

Yes, the suppression works fine, but I wanted to avoid the suppression, i.e. StyleCop should allow and not report SA1118 in this scenario because there is no alternative than the suppression.

Is this not a duplicate of #2916?

@sharwell Multi-line array initializers (and other exceptions) are allowed as e.g. method call arguments, but currently not in attribute arguments.

Weird. I can't find a reason for that distinction.


crash on startup

Edited with pastebin:
http://pastebin.com/KAFTaW1t

Did you modify your seed json at all?

no, just dragged your mod into mods folder and started minecraft.

Could I get a copy of your seed json?

sure if i knew where to find it  :D

../config/ResourcefulCrops/Seeds.json

its empty...

Well then, that's a problem...
For now, you can copy all this into it to (hopefully) avoid the crash.
http://tehnut.info/share/hUzMjubdD0.txt

ok it worked, thx

i have the same exact crash

ok dude, i dont know what  to say, sorry if i wasted your time.

I meant it more as a "This is weird, why would it happen to others and not me?"

Alright, so did some more testing. It does not happen alone. Only with other mods. That is why I couldn't reproduce. Hum...

 They query OreDictionary.getOres(entry) without checking OreDictionary.doesOreNameExist(entry) first. The latter checks if the entry exists without adding anything to the dictionary. The former checks if it exists and if not, it will add an entry with an empty list.
By querying OreDictionary.getOres(entry) blindly, it spams the OreDict with values that shouldn't be there.


Don't use gpt2 tokenizer etc in tests

HF tokenizers/model loading take a frankly absurd amount of time to load (10s on my macbook)
It's often 80%+ of test time.

just had CI fail because huggingface.co was unresponsive 👎

Would this help for CI purpose? https://x.com/StasBekman/status/1724519457790509310?s=20

And this tweet from the same person seems relevant to this issue: https://x.com/StasBekman/status/1762960092847333647?s=20

Hugging Face had an outage a couple days ago. Also, I believe tiktoken is a drop-in replacement with minimal dependencies for the GPT-2 tokenizer, but I haven't checked if it's exactly equivalent.

I mostly don't want to deal with tiktoken just so I don't have to make a wrapper, but it's not a bad idea (given we also need to work with llama etc)
I think we want to just break our dependence on the hub for tests, but it's probably not worth spending a ton of time on


Could not find androidx.datastore:datastore-preferences:1.0.0-alpha01

I am trying out the codelab but unable to resolve the dependency for datastore. I have tried the "preferences_datastore" branch too but the result is the same.
I could not find any information about datastore's Gradle dependency on Jetpack Explorer and AndroidX releases Page.
Kindly look into this. Thanks

I did find the datastore library in their codebase.
Could possibly be an error in version number.

It is currently not registered on google's maven repository(https://maven.google.com/web/index.html). So just wait till to be update.

Library was published. Try it out!


Confusing guidance on installation location

Homepage says:
Linuxbrew is a fork of Homebrew, the macOS package manager, for Linux.

It can be installed in your home directory and does not require root access.

However when you're installing, it says that installing as a different user is recommended:
 vadi  ~  ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Linuxbrew/install/master/install)"
-e:203: warning: Insecure world writable dir /home/vadi/Programs/Qt in PATH, mode 040777
==> Select the Linuxbrew installation directory
- Enter your password to install to /home/linuxbrew/.linuxbrew (recommended)
- Press Control-D to install to /home/vadi/.linuxbrew
- Press Control-C to cancel installation

This is confusing - which is recommended, installing in the home directory or as a different user?

It can be installed in your home directory if necessary, but it's recommended to install in /home/linuxbrew/.linuxbrew.
The precompiled binary bottles of non-relocatable bottles can only be used if you install in /home/linuxbrew/.linuxbrew, otherwise they have to be built from source. See the documentation below, but wherever it reads /usr/local, which is for macOS, read instead /home/linuxbrew/.linuxbrew.

http://docs.brew.sh/Installation.html#alternative-installs
http://docs.brew.sh/FAQ.html#why-do-you-compile-everything
http://docs.brew.sh/Bottles.html#cellar-cellar


Update Tour to promote the use of thread key

noticed that in the JS examples it is undefined, which we should discourage as it could save devs future migration annoyances to be using it already.

no rush


Fix CI build error on JDK 1.6 which cause by TLS upgrade of the server.

Modification:

Add maven settings.xml template for override the default settings.xml.

Result:
Fix #188

Codecov Report

Merging #190 into master will increase coverage by 0.07%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #190      +/-   ##
============================================
+ Coverage     71.14%   71.22%   +0.07%
- Complexity      952      954       +2
============================================
  Files           341      341
  Lines         14203    14210       +7
  Branches       2286     2286
============================================
+ Hits          10105    10121      +16
+ Misses         2904     2894      -10
- Partials       1194     1195       +1

Impacted Files
Coverage Δ
Complexity Δ

...n/java/com/alipay/sofa/rpc/client/RouterChain.java
56.57% <0%> (-0.76%)
0% <0%> (ø)

...om/alipay/sofa/rpc/common/json/JSONSerializer.java
64.93% <0%> (-0.43%)
0% <0%> (ø)

...n/java/com/alipay/sofa/rpc/filter/FilterChain.java
76.06% <0%> (-0.25%)
0% <0%> (ø)

.../com/alipay/sofa/rpc/common/utils/CommonUtils.java
83.92% <0%> (+0.29%)
0% <0%> (ø)
:arrow_down:

.../main/java/com/alipay/sofa/rpc/event/EventBus.java
70.21% <0%> (+0.64%)
0% <0%> (ø)
:arrow_down:

...alipay/sofa/rpc/registry/zk/ZookeeperRegistry.java
60.15% <0%> (+0.78%)
0% <0%> (ø)
:arrow_down:

.../main/java/com/alipay/sofa/rpc/tracer/Tracers.java
42.3% <0%> (+2.56%)
0% <0%> (ø)
:arrow_down:

...pc/transport/bolt/BoltClientConnectionManager.java
83.82% <0%> (+5.88%)
20% <0%> (+1%)
:arrow_up:

...m/alipay/sofa/rpc/module/FaultToleranceModule.java
93.33% <0%> (+26.66%)
5% <0%> (+1%)
: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 e5fdd06...1d4e3d0. Read the comment docs.


Vendor resources pulled in during runtime

Alertmanager should be able to run in an environment that is not connected to the internet.
Therefore, we must not pull in external resources like e.g. in https://github.com/prometheus/alertmanager/blob/master/web/templates/_base.html#L8

The new alertmanager isn't using any remote resources AFAICT.


COMPLETE button logic

Required
When the COMPLETE button is clicked, the work session timer stops and the session is counted towards completed.
Reason behind this feature: The aim of the Pomdoro technique is to finish a task at hand faster. So, if a user has completed a task, it is a valid reason to finish that session and go take a break earlier and not wait for the timer.
Expected Behaviour

COMPLETE buttons stops the timer.
Resets Toggle button to checked state so that the user can take a break.

Must start after #23 is resolved

This issue is in pursuance of #21

Interested in taking up this issue? Leave a comment expressing you interest along with your @slack id.abnd.
Each issue expects a 24hr turnaround time by default. In case where a student doesn't come back with an update after 24 hours have elapsed, the issue is up for grabs by anyone.

I would like to work on this issue.
Slack ID - @tirth.abnd

Cool! Assigned.


Readme for the dead code analysis mode

cc @ryyppy @cristianoc
I added a whole new section etc. Let me know if this is too much and you'd like this structured in another way.

LGTM


Prd hot fix

Hot fix to prevent duplicate entry during persisting records.

@scoen could you please review?  Thanks.

Build finished.

👍


Can I mark the multi-label classification task?

Can I mark the multi-label classification task? Still, you can only give each text a label

Yes, you can add multiple labels at the classification task.


Feature Request - option to run container rather than pull and run

Hello,
We are trying to utilize python_on_whales in a slightly unusual situation. We created a CLI which implements a subset of Docker commands to execute containers in the Kubernetes, instead of locally. A certain number of docker commands from the CLI of the cluster will (from the perspective of the user) appear to act just like they normally do. Since python_on_whales seems to primarily interface with docker through the CLI it is a great fit for us.
However, we are running into issues when calling python_on_whales.docker.run() method, as it calls docker image inspect and docker image pull. Kubernetes API does not have image management, as a result we cannot implement any of the docker image ... commands.
Ideally, python_on_whales would have an optional argument which rather than issuing docker image commands would simply perform a docker run command, which should work for us and also work in a local Docker environment as well.
Thank you for your time and consideration!
Cheers,
Ben

Hello, I think in recent version of Docker, there is an argument to docker run that would allow us to do that.
    --pull string                    Pull image before running ("always"|"missing"|"never") (default "missing")

In your case, if we use "never" then python-on-whales should not try to inspect and pull the docker image. We should implement this feature :)

That would be great if this was implemented!

No worries, with the implementation of @MisterOwlPT it should work out and never call docker image ... if you specify pull="never".

Fixed with the new flag pull="never" :)


Implement initial num-traits

This implements the first 6 traits from num-traits when the num feature is enabled.

Bounded
Zero
WrappingAdd
WrappingSub
FromPrimitive
ToPrimitive

Aside from the conversion traits and Zero, these all correspond to methods already implemented.

currently these are stable

I've got an updated take on some of these here


removed test chapter

This is an example PR.

I pulled the latest of the repository:
git checkout master
git pull origin master

I created a local branch:
git checkout -b chapter-7

I did some "work":
git rm textbook/05/My\ Test.ipynb

I committed this work:
git commit

I pushed my committed changes:
git push origin HEAD

I clicked the Pull Request link returned from GitHub by the above command.

Note:

I didn't have to "stage" my changes (because they consisted of a deletion). If I had, that might have looked like: git commit --all.
I took advantage of a "shortcut" in my push command: HEAD. In this case, the "head" of my local repository pointed to the current state of the branch I wanted to push. This is useful! But, more generally, I might have said: git push origin chapter-7.
The chapter I'm deleting wasn't in the textbook's Table of Contents; so, no change to that file is needed. But, if I were to add or remove a chapter or sub-section, then a change to textbook/_toc.yml might also be required….

Oh boy! There are merge conflicts.
Hopefully this won't happen too often. When it does, there are many ways to handle it.
In this case, I'm going to use the "dark magic" of rebase. This will replay my changes on top of those I missed in origin/master:

git checkout chapter-7
git rebase origin/master

It looks like this file I'm trying to delete was edited in master. Generally I might care about that. In this case, I don't. I'll force through the change I was trying to make (achieving the same as would've occurred if I'd been up to date with changes in the first place):

git rm textbook/05/My\ Test.ipynb
git rebase --continue

I'm now up-to-date with origin/master and everyone's happy … except for my pull request branch origin/chapter-7. My use of rebase has rewritten history, and so git will complain when I push back to origin. No matter:

git push --force origin HEAD

And now my PR looks OK!

(Of course this is an example wherein I created a branch on the main repository. It might be even easier to create a fork of this repository, and create a pull request from there!)


Add automatic size for comment box

Summary
Add a feature to solve issue #981 (#1493 ).
This PR add a option for comment. With that option the comment can be set Automatic Size property.
usage:
sheet.getCell('C3').comment = {
    texts: ['This\nIs\nA\nComment\nThat\nNeed\nA\nLarge\nBox'],
    autoShape: true,  // with this option the size of comment box will be adjusted automatically
 };

The corresponding setting in excel is in the screenshot below:

Test plan

npm i && npm run test:all
All test cases has passed.
Questions
Should I update README.MD at the same time?

@csgka1 Could you please move over here? I'd be happy to merge this feature.

could this be merged, pretty please 👍


Assetto Corsa

TrackData done for konus tracks and a few other.
Ive made it so that local driver uses same way to get sector times and sectors as the opponents, that will give a more accurate gappoints, I know it will not match with the games sector times cause of the 100ms delay between reads.

I made a mistake. dont marge, sry just a sec.

Fixed!

I'm gonna colse this again, there seems to be issues with sector 3 beeing seen as the full lap.


fix alignment for SendEventDest

Use the implementation from https://github.com/rust-x-bindings/rust-xcb/pull/225 for this, rather than reimplementing the serialization logic inline.
refs: https://github.com/rust-x-bindings/rust-xcb/issues/229
refs: https://github.com/wez/wezterm/issues/3838

Thanks for this.
I understand it is the same issue, but I don't really get it.
Why is the alignment different?
In my understanding (which is apparently wrong), assigning to a pointer address is the same as copying the bytes to this address.

This sort of issue is more problematic on non-Intel architectures, as Intel has some stuff that compensates for alignment issues by default. I'm not sure if this panic is "just" Rust being helpful for writing more portable code across architectures or if this is a legit error on Intel.  On those other architectures, or on Intel when the processor is set to the strict alignment mode, unaligned accesses general a fault.
The issue here is with how the memory transfer gets compiled; the underlying word transfer opcode that results from a pointer indirection typically requires that the data be stored at an aligned address for both source and destination, which may not be guaranteed.  In wezterm that particular stack trace was for a struct that was constructed on the stack and I suppose (didn't verify) that it doesn't include any padding that would help it to be appropriately aligned for this kind of direct access.
Taking care to add that padding/alignment to the various structs might be another way to resolve this issue, but the simplest and most robust is to use copy_from_slice which internally is able to reason about alignment and switch to byte-wide operations around the edges of the underlying memory copy, but use full machine-word size transfers for the bulk of it, without triggering the alignment concern.
I'd recommend that you take a look at the various serialize operations and adjust them all to use copy_from_slice or layer them on top of other implementations that are using it, so that you can head off any other lingering similar issues!


mina.service still uses peer-list-file

With the update to version 0.4.2-245a3f7, it seem the way to load the peers is via:
--peer-list-url https://storage.googleapis.com/seed-lists/zenith_seeds.txt

However /usr/lib/systemd/user/mina.service still contains:
ExecStart=/usr/local/bin/coda daemon \
  -peer-list-file %h/peers.txt \

And the way to download peers.txt is no longer present in the documentation

Still present with release 1.0.0-fd39808


feat: Migrating Grid.js to getDerivedStateFromProps

follow up to #1009
cc @bvaughn

Any plans on merging this so we can unblock #1040 #1072 and #1028?

@azmenak there is currently 1 test is failing that I will be taking another look at this weekend. Hopefully soon!


update stylelint rules, add color palettes

Please always provide the Jira Issue your PR is for, as well as test URLs where your change can be observed (before and after):
Jira ID: https://jira.corp.adobe.com/browse/EXLM-116
Test URLs:

Before: https://main--exlm--adobe-experience-league.hlx.page/docs/integrations-learn/experience-cloud/solution-categories/content-management
After: https://feature-exlm-116-color-palette--exlm--adobe-experience-league.hlx.page/docs/integrations-learn/experience-cloud/solution-categories/content-management

Hi @ahmed-musallam,
I wanted to move the newly added variables to a separate file. Turns out the SASS compile code is not considering the ignore rules. Was it working for you when you tested in your local? If this is not a blocker for this PR, we can merge this.

@thomsebastin update this: https://github.com/adobe-experience-league/exlm/blob/main/sass-compile.js#L7
to ignore any files you want to ignore.
Even if the sass compile process compiles the variables file, it's not a blocking issue, just clutter we don't need

Overall, this looks good to me

@thomsebastin update this: https://github.com/adobe-experience-league/exlm/blob/main/sass-compile.js#L7 to ignore any files you want to ignore.
Even if the sass compile process compiles the variables file, it's not a blocking issue, just clutter we don't need

I did try in my local, but didn't work for me. I will check again.
Here's what I did:
Updated const IGNORED_FILES = []; to const IGNORED_FILES = ['sass']; and created a folder with my SASS variable file there. When I restarted the task it was compiling the CSS in SASS folder. Anyway, we can handle that separately. I will move this out of draft, so you can approve and merge.