Extended URI wildcard

For https://github.com/StarcounterApps/SignIn/issues/89

@un-tone can you pls do the following:

Add tests for this change
Add mention to README.md about supported Catch URI patterns

Then we can merge the PR and make a follow up issue about improving the GetWildCardUrl method.

Added tests and updated README. @warpech please review


router-link within md-menu doesn't work

Hi!
I need a router-link within md-menu, I try
    <md-menu>
      <md-button md-menu-trigger>Open Menu</md-button>
      <md-menu-content>

        <router-link to="/foo" tag="md-menu-item">
          Go to Foo
        </router-link>

        <md-menu-item>
          <router-link to="/bar">
            Go to Bar
          </router-link>
        </md-menu-item>

      </md-menu-content>
    </md-menu>

http://codepen.io/anon/pen/dNLNOO
It doesn't work and looks awful, thanks

See this #470

@cawa-93 Even this workaround doesn't work https://github.com/marcosmoura/vue-material/issues/470

I will take a look at this issue. It seems that the mdMenuItem is preventing the click.

Any updates on this?  Has someone found a workaround?

Hello everyone.
This issue is the same as #470 (a workaround can be found there too @johnwebbcole ). I'm closing this issue for now and we'll fix it ASAP.
Thank you @johnwebbcole @romangit and @cawa-93 :D


Windows Compatibility

Are there any known issues with windows compatibility?
NPM is failing, with less than clear error messages. I have yet to install ghostscript or the pdf tool which might solve the errors, but I wanted to check and see if there might be something more subtle happening.

did you found a solution for that ?

I did!


biggest challenge in retrieval*

Lots of cool stuff built around leveraging realtime human created knowledge.
The biggest challenge I'm running into is 'back propagation' for the entire RAG/REML/RAML/R* pipeline.
Not sure the REST based 3rd party models belong in lower level efforts, btw.   They are too much flux / unreliable.  Very useful for sure, but probably best to keep them high level.

Thanks for the note. Let me know if there's a particular issue we can help with


Fix param name in action.yml

@rheaditi are you updating the readme in this PR? if yes then ill wait for the changes

@rheaditi are you updating the readme in this PR? if yes then ill wait for the changes

Done! Can you check now?

Link to rendered README.md: https://github.com/ClearTax/pr-lint/blob/chore/fix-param-name-actioyml/README.md


fix bug in token_bucket_set: correctly turuncate existing tokens

Thanks for the patch.  Can you provide a Signed-off-by?  See CONTRIBUTING.md for details.

Signed-off-by: Eziz Durdyyev<EMAIL_ADDRESS>

Thanks.  I applied this to master and branch-2.[543].


Run the Docker container as a non-root user

The container currently runs code as a root user which provides possibility to break the running instance of the container, at least until the Python server process is restarted. Let's create a non-root user in the Docker image and use that to run code. Perhaps something like this:
ENV USERNAME=fortran
RUN useradd \
  --no-log-init \
  --home-dir /home/$USERNAME \
  --create-home \
  --shell /bin/bash \
  $USERNAME
USER $USERNAME
WORKDIR /home/$USERNAME

Fixed by #52


SWRConfig cache Provider doens't work with Webpack & useSWRInfinite

Bug report
Description / Observed Behavior
A custom provider in the SWRConfig doesn't seem to be working when using Webpack / useSWRInfinite.
I tried to implement the LocalStorage Based Persistent Cache, somehow in the environment im working with, which is using Webpack to serve React, the Map always stays empty:

I made a repo where you can reproduce this misbehavior, the src/Test.component.js is where all the React/useSWR Code is in.
Strangely I found out that this exact same Test.component.js code, is working in this Vanilla JS Codesandbox
Expected Behavior
The custom provider should work in the webpack environment same as in the vanilla sandbox environment.
Repro Steps / Code Example
Clone the webpack repo

npm run start
browser should open on localhost:8080
open dev tools
click on load more
click on leave page
you should land in a breakpoint on line 60 in the Test.component.js file
appCache is '[]'

Also check the Vanilla JS Codesandbox as described
Additional Context
SWR version: 1.2.2
I also opened a discussions thread, which is outdated now: https://github.com/vercel/swr/discussions/1879
Use of the useSWRInfinite hook via an reusable data hook: https://swr.vercel.app/docs/getting-started#make-it-reusable

Looks like the issue is caused by different core swr files are resolved:

First swr/dist/index.esm.js is resolved
Then swr/infinite/dist/index.esm.js is resolved
The infinite tries to import from swr, but swr/dist/index.mjs is resolved

So the default cache has been overriden.
Looks like it's a webpack issue cause it works when I down grade the webpack to previous versions (e.g. 5.16.0)

Filed https://github.com/webpack/webpack/issues/15484 to see if there's any workaround from webpack side

@huozhi great work, thanks for finding out and vielen Dank! :)

@Westsaid  Seems that's caused by the plugin @babel/plugin-transform-modules-commonjs, I think you can safely remove it from babelrc.
webpack maintainers shared more about it here 👉  https://github.com/webpack/webpack/issues/15484#issuecomment-1060906189

@huozhi  Thank you so much for your effort! It's working now. 😍


[useScrollTrigger] Add passive flag to scroll trigger event listener #32437

[x] I have followed (at least) the PR section of the contributing guide.

Closes #32437

This seems to be working fine.
One small issue is that IE will interpret the third argument as useCapture (it doesn't support passive event handlers) and treat the object passed in as true. This shouldn't really matter in this particular case, so I'm OK with keeping this as proposed.
@oliviertassinari - are you fine with this approach?

For IE 11, the idea in https://mui.com/material-ui/getting-started/supported-platforms/#ie-11 is to say it's something we will do tradeoffs against. So trading degraded IE 11 support in exchange for better support of new browsers, yeah, that sounds like a great deal 💸.


Fixing login flake

What is the purpose of this change? What does it change?

Making each login test spec independent.
Was the change discussed in an issue?
https://github.com/openshift/odo/pull/2162#issuecomment-534467268

How to test changes?

make test-cmd-login-logout

This is not a good way to fix this issue.
If there is something that depends on the ondering it should be inside one test spec.
Each test spec needs to be from each onther
/hold

@amitkrout Shouldn't we run it close to 10 times to confirm that this patch will fix it?

I have locally tested it locally more than 10 time i guess

This is not a good way to fix this issue.
If there is something that depends on the ondering it should be inside one test spec.
Each test spec needs to be from each onther
/hold

That was my intention, but thought that it will increase the spec length and probably some early failure will cause many steps un executed.
hmm, let put it then in a single spec.

That was my intention, but thought that it will increase the spec length and probably some early failure will cause many steps un executed.
hmm, let put it then in a single spec.

ideally, we should identify what it is that makes this fail and fix it

That was my intention, but thought that it will increase the spec length and probably some early failure will cause many steps un executed.
hmm, let put it then in a single spec.

ideally, we should identify what it is that makes this fail and fix it. Not just blindly join everything together

https://github.com/openshift/odo/pull/2162#issuecomment-534467268

Failures encountered
odo component command tests Creating component with numeric named context
  should create default named component in a directory with numeric name
[...]
• Failure [112.447 seconds]
odo component command tests
/go/src/github.com/openshift/odo/tests/integration/cmd_cmp_test.go:13
  Creating component with numeric named context
  /go/src/github.com/openshift/odo/tests/integration/component.go:579
    should create default named component in a directory with numeric name []
    /go/src/github.com/openshift/odo/tests/integration/component.go:596
     Unexpected error:

        <*os.PathError | 0xc0000ada10>: {Op: "chdir", Path: "", Err: 0x2}
        chdir : no such file or directory
    occurred
     /go/src/github.com/openshift/odo/tests/helper/helper_filesystem.go:42

odo component command tests odo component delete, list and describe
  should fail outside a odo directory without component name as parameter
  /go/src/github.com/openshift/odo/tests/integration/component.go:513
 [...]
[odo]  ✓  Changes successfully pushed to component

Running odo with args [odo list --project scwcuiutpy]
[odo]  ✗  There are no components deployed.

[...]
 • Failure [72.480 seconds]
odo component command tests
/go/src/github.com/openshift/odo/tests/integration/cmd_cmp_test.go:13
  odo component delete, list and describe
  /go/src/github.com/openshift/odo/tests/integration/component.go:486
    should fail outside a odo directory without component name as parameter [It]
    /go/src/github.com/openshift/odo/tests/integration/component.go:513
     Failed after 0.214s.

    Running odo with args [odo list --project scwcuiutpy]
    Expected
        <int>: 0
    not to match exit code:
        <int>: 0

odo component command tests odo component delete, list and describe
  should pass outside a odo directory with component name as parameter
  /go/src/github.com/openshift/odo/tests/integration/component.go:525
 [...]
Running odo with args [odo describe nodejs --app app --project cjmwpnlhak -o json]
[odo] {"kind":"Component","apiVersion":"odo.openshift.io/v1alpha1","metadata":{"name":"nodejs","namespace":"cjmwpnlhak","creationTimestamp":null},"spec":{"app":"app","type":"nodejs","source":"file://./","env":[{"name":"DEBUG_PORT","value":"5858"}],"ports":["8080/TCP"]},"status":{"state":"Pushed"}}
[...]
 • Failure [67.511 seconds]
odo component command tests
/go/src/github.com/openshift/odo/tests/integration/cmd_cmp_test.go:13
  odo component delete, list and describe
  /go/src/github.com/openshift/odo/tests/integration/component.go:486
    should pass outside a odo directory with component name as parameter [It]
    /go/src/github.com/openshift/odo/tests/integration/component.go:525
     Expected

        <string>: {
          "kind": "Component",
          "apiVersion": "odo.openshift.io/v1alpha1",
          "metadata": {
            "name": "nodejs",
            "namespace": "cjmwpnlhak",
            "creationTimestamp": null
          },
          "spec": {
            "app": "app",
            "type": "nodejs",
            "source": "file://./",
            "env": [
              {
                "name": "DEBUG_PORT",
                "value": "5858"
              }
            ]
          },
          "status": {
            "state": "Pushed"
          }
        }
    to match JSON of
        <string>: {
          "kind": "Component",
          "apiVersion": "odo.openshift.io/v1alpha1",
          "metadata": {
            "name": "nodejs",
            "namespace": "cjmwpnlhak",
            "creationTimestamp": null
          },
          "spec": {
            "app": "app",
            "type": "nodejs",
            "source": "file://./",
            "env": [
              {
                "name": "DEBUG_PORT",
                "value": "5858"
              }
            ],
            "ports": [
              "8080/TCP"
            ]
          },
          "status": {
            "state": "Pushed"
          }
        }

    first mismatched key: "spec"
     /go/src/github.com/openshift/odo/tests/integration/component.go:541

Details - https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_odo/2164/pull-ci-openshift-odo-master-v4.2-integration/258

This pr blocks rest pr in pool to go in
ping @kadel @mohammedzee1000 @dharmit

We have less choice atm as its blocking, @amitkrout could you update the issue tracking this that this is a quick fix and a more formal fix needs to be done :)

We have less choice atm as its blocking, @amitkrout could you update the issue tracking this that this is a quick fix and a more formal fix needs to be done :)

There is no more formal fix i guess. I just combine those dependent test and make it a single scenario.

/hold cancel

[odo]  ✗  Waiting for build to finish [30s]
[odo]  ✗  Failed to create component with name wo-wait-javaee-git-test. Please use `odo config view` to view settings used to create component. Error: unable to wait for build wo-wait-javaee-git-test-app-1 to run: timed out waiting for the condition

/test v4.1-e2e-scenarios


UDPHandler?

Hi Peter,
For my own use, I added a udp handler so I can send messages to a UDP listener.  It uses json to pickle the log record so it should be safer and lighter (though maybe less flexible) than the standard logging.handlers.DatagranHandler which uses pickle.
Any interest?
Mike

Hi Mike - sounds very interesting!  I think it's a little too niche for main package but if you've created a Fork with the UDP feature I think that would be a good place to maintain it... and I'd be really interested to see what you've done.
I'm a bit slow (sorry) but noticed a couple of minor things with the .find() method.  If I raise them as issues and suggest the tests that need to PASS, would you be kind enough to have another look at some point please?  No rush... but would be nice to get this 100% right (including my final tweaks to the README) before updating on PyPI.
All the best and thanks again for your enthusiasm and contributions!

Sure Peter. Something to do while the mince pies digest over the next couple of weeks :)
Open the issues and I'll take a look.

Hehe I think we both know those mince pies NEVER fully digest!!!
I've add a few issue now Mike - didn't have permission to assign them directly to you though.  I've made quite a lot of changes in the latest Merged Pull Request, both to the tests and to the variable names in the .find method.
Good luck, and I hope I haven't muddied the waters too badly...

PS strongly suggest you create your own fork from the latest version, then a new branch for each of the issues.  Then merge each branch back into your fork, and finally submit a Pull request to get those changes into my Master repository.  Hope that makes sense!

OK. Sorry should have commented here earlier perhaps.  Done and pull request submitted. :)


feat: add http command endpoint (v2)

Description
currently inverter commands are only accessible via MQTT.
This adds a http endpoint /command to the webserver to access the inverter commands.
You may invoke /command/list for a list of commands. All commands must be executed as HTTP POST with JSON encoded parameters in the body. Additionally the Content-Type of the body must be application/json to avoid CORS attacks.
As this feature is a potential security issue it has to be explicitly enabled in the config.
How Has This Been Tested?

[ ] Not applicable

Inverter type

[ ] Simulated inverter
[X] Growatt 3000 TL-X

Stick type

[X] Shine X
[ ] Shine S
[ ] Lolin32
[ ] Nodemcu32

Could we merge this?

I would be happy to merge this if we had tls support and an api. But at the moment this is not the case.


Verification of encryption data append in encrypt/decrypt file of AE_AES classes's methods

Implement verification of encryption data append in encrypt/decrypt file of AE_AES classes's methods.

fixed by https://github.com/alecgn/crypthash-net/commit/87e8a8e62bc66f49283663c493df67699b547bc3


torizon: add a literal Torizon container image

... which builds a container with the latest qemux86_64 common Torizon image and installs qemu-system to enable Torizon to run as an actual virtual machine.
Defaults to using kvm.

Hey @leonheldattoradex thanks for the contribution! This looks very promising. Did you see how it was implemented in the other projects, folders, in the repo? It would be cool if we continued following the same pattern. Let me know what you think.

Hey @microhobby I'm a bit confused regarding the json files. I understand the variable in the json are probably exported and them grabbed by the docker-compose.yml/Containerfile, but who exactly is supposed to parse this json and do that?

@leonheldattoradex thanks for the contribution. I partially added it here: 8f82adbb5905ebf9bafc85e451c519ec6115ca88
I removed the GitHub actions because we are following another pattern to build the Containers here.


Empty descriptions - meta data quality

@PixlTracer  @IvdL22 @vronk
As discussed in the meeting today:

[x] Provide a list of all courses with empty descriptions (Patrick)
[x] This will be discussed during the WG meeting, how moderators can contribute to fix this. (Anna & Iulliana)
[x] Do now allow empty descriptions. Validation in model and DB (Patrick)

@PixlTracer @vronk @IvdL22
Today I took a look at the production database and found 90 courses with an empty description. Those courses are all archived and not public shown.
So there won't be a list to discuss at the WG meeting?
For now we don't need to take an action on this?
The example I mentioned of a course with empty description happened at the end of last year and has been fixed by now.
Please understand that I don't look at every course separately.  So I only see things when testing a new feature. In that case, of course, I can mention this.
So the good news is that, in the active/public shown courses, we currently don't have this problem.
I have changed the model, so that the field description will be required in release 2023-05.
This can be tested here:
https://dev-dhcr.clarin-dariah.eu/courses/add
It is not changed in the database, since this is not possible because of the old courses without description.
Can you review this and change the label to done, when you agree that no further actions are needed?

Thank you @patrickakk (cc @PixlTracer ). This is fine now. Would it be possible to extend a bit the suggestion of the text in grey "Please provide the course descriptions in English."
Some participants of our second workshop yesterday at DARIAH2023 asked to encourage course, contributors, to also include the learning outcomes in the course descriptions. Hence, I would like to suggest the following text:
"Please add in English the general aims of the course/programme and the learning outcomes."
Ok to include this request in here or do you want me to open a new issue?
thank you

@IvdL22 (cc @PixlTracer ) It's fine to add it here. The change has been implemented in 2023-05. You can check it here:
https://dev-dhcr.clarin-dariah.eu/courses/add
Note: This text is only shown when the field description is empty, so when adding a new course. If you want a message which is also shown when the course is updated/edited, it could be done like the line below ECTS.
Can you change the label to "Done" when you're satisfied and this issue can be closed?

Hi all,
checked the Description Field in dev (screenshot) and it seems that the additional sentence proposed by Iulianna has not been implemented (yet?)
@patrickakk can you change the text in the description field from "Please provide the course description in English" to
"Please provide the course description in English, as well as the general aims of the course/programme and the learning outcomes."
thanks!

@PixlTracer Did you check the link, specified in the comment above ?  (https://github.com/acdh-oeaw/dhcr-main/issues/74#issuecomment-1582324053)
(cc @IvdL22 )
The text -as specified by Iulliana- is there ? See screenshot:

Can you change the label to "Done" when you're satisfied and this issue can be closed?

@patrickakk Done, thanks!

The change above is implemented in 2023-05.

When using another approach, it seems like there are still a lot of courses with empty descriptions.
I'll check that and get back on it.

Moved to November milestone, since we're still not finished with cleaning up duplicate user accounts. (See #50).
And too much "lists" might be confusing.


Cleaned up lots of unused css rules in the 2048 game.

Changes:

Removed most of the -webkit  , -ms , -moz prefixes (As most of the browsers now supports the normal version of those rules.
Moved the  image-rendering: pixelated rule to the .tile class to avoid repetition.

Checked using chrome, firefox, microsoft edge and everything works as indented. Didn't test  on Safari but it should work  too.

Things to improve:

Use img tags instead of background-image css rule in the tiles. This will fix: #2

ty!


cmd/go: the go command converts uppercase characters to !+ lowercase characters.

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go version devel +c54bc34 Thu Jul 19 00:23:07 2018 +0000 linux/amd64
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
baas@SZX1000428520:~/git/go/src/go-langserver [master]$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/baas/.cache/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/baas/git/go"
GOPROXY="http://<IP_ADDRESS>:9090"
GORACE=""
GOROOT="/home/baas/my/go"
GOTMPDIR=""
GOTOOLDIR="/home/baas/my/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/baas/git/go/src/go-langserver/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build071732067=/tmp/go-build -gno-record-gcc-switches"

What did you do?
I am using the go 1.11 moudle function, I developed a go module proxy and used it by setting the environment variable GOPROXY
What did you expect to see?
the go module proxy can work well.
What did you see instead?

client

$ go get github.com/SimpleMessageNotification/smn-sdk-go@latest
go get github.com/SimpleMessageNotification/smn-sdk-go@latest: cannot find module providing package github.com/SimpleMessageNotification/smn-sdk-go

server

$ ./vgoproxy
0719 10:48:40.33 go config:
{
   "gopath": "/data1/baas/.gomod",
   "http": [
      "code.huawei.com",
      "rnd-isource.huawei.com",
      "rnd-github.huawei.com"
   ],
   "replace": {},
   "sortKeys": null
}
0719 10:48:40.33 start go proxy server at :9090
0719 10:49:23.565 GET /github.com/!simple!message!notification/smn-sdk-go/@v/list from <IP_ADDRESS>:47174
0719 10:49:23.565 new url /github.com/!simple!message!notification/smn-sdk-go/@v/list
0719 10:49:23.566 go: list version failed: invalid github.com/ import path "github.com/!simple!message!notification/smn-sdk-go"
0719 10:49:23.58 GET /github.com/!simple!message!notification/@v/list from <IP_ADDRESS>:47174
0719 10:49:23.58 new url /github.com/!simple!message!notification/@v/list
0719 10:49:23.58 go: list version failed: invalid github.com/ import path "github.com/!simple!message!notification"
0719 10:49:23.591 GET /github.com/@v/list from <IP_ADDRESS>:47174
0719 10:49:23.591 new url /github.com/@v/list
0719 10:49:24.718 go: list version failed: unrecognized import path "github.com" (parse https://github.com?go-get=1: no go-import meta tags ())

As @magical said, this appears to be working as intended. You need to decode the path before you use it.
https://github.com/golang/go/blob/c54bc3448390d4ae4495d6d2c03c9dd4111b08f1/src/cmd/go/internal/module/module.go#L455

@magical @magical
Thank you very much.
github.com/golang/vgo does not sync the latest code

github.com/golang/vgo does not sync the latest code

Correct. Per Russ's recent email to golang-dev,

Work on the module support will now be done exclusively in the main repo. We will automatically export the main repo to the x/vgo repo when we have a snapshot we want to make available to people using "vgo".

https://groups.google.com/forum/#!topic/golang-dev/a5PqQuBljF4


cuDNN error when using scan and 3D convolution

I am trying to recurrently apply a neural network to a tensor. I am using Flax and the flax.linen.scan transform which is a modified jax.lax.scan. I get an error related to cuDNN.
Environment specs

python 3.9.7
jax 0.2.24
jaxlib 0.1.73+cuda11.cudnn805
flax 0.4.0
CUDA 11.1 and cuDNN 8.1.1
Nvidia V100 32GB GPU

Code to reproduce
import jax
import jax.numpy as jnp
from flax import linen as nn
from functools import partial

class CNN(nn.Module):
    @nn.compact
    def __call__(self, x, *args):
        conv = partial(nn.Conv, features=3, kernel_size=(3, 3, 3))
        x = conv()(x)
        x = nn.relu(x) # Commenting this line makes the error go away
        return x, x

class CNNScan(nn.Module):
    @nn.compact
    def __call__(self, x):
        rollout = nn.scan(
            CNN,
            variable_broadcast='params',
            split_rngs={'params': False},
            length=8,
            out_axes=1
        )

        _, out = rollout()(x, None)

        return out

rng = jax.random.PRNGKey(0)
cnn = CNNScan()
init_cnn = cnn.init(rng, jnp.ones([1, 64, 64, 64, 3]))

Error message
File /home/nagabhushana/anaconda3/envs/ddp_v2/lib/python3.9/site-packages/flax/core/axes_scan.py:144, in scan.<locals>.scan_fn(broadcast_in, init, *args)
    141   out_flat.append(const)
    142 broadcast_in, constants_out = jax.tree_unflatten(out_tree(), out_flat)
--> 144 c, ys = lax.scan(body_fn, init, xs, length=length, reverse=reverse)
    145 ys = jax.tree_multimap(transpose_from_front, out_axes, ys)
    146 ys = jax.tree_multimap(lambda ax, const, y: (const if ax is broadcast else y),
    147                        out_axes, constants_out, ys)

... skipping hidden 13 frame

File /home/nagabhushana/anaconda3/envs/ddp_v2/lib/python3.9/site-packages/jax/interpreters/xla.py:369, in backend_compile(backend, built_c, options)
    366 def backend_compile(backend, built_c, options):
    367   # we use a separate function call to ensure that XLA compilation appears
    368   # separately in Python profiling results
--> 369   return backend.compile(built_c, compile_options=options)

RuntimeError: UNKNOWN: Failed to determine best cudnn convolution algorithm: INTERNAL: All algorithms tried for %cudnn-conv-bias-activation = (f32[1,64,64,64,3]{3,2,1,4,0}, u8[0]{0}) custom-call(f32[1,64,64,64,3]{3,2,1,4,0} %get-tuple-element.8, f32[3,3,3,3,3]{2,1,0,3,4} %get-tuple-element.5, f32[3]{0} %get-tuple-element.6), window={size=3x3x3 pad=1_1x1_1x1_1}, dim_labels=b012f_012io->b012f, custom_call_target="__cudnn$convBiasActivationForward", metadata={op_type="conv_general_dilated" op_name="jit(scan)/body/conv_general_dilated[\n  batch_group_count=1\n  dimension_numbers=ConvDimensionNumbers(lhs_spec=(0, 4, 1, 2, 3), rhs_spec=(4, 3, 0, 1, 2), out_spec=(0, 4, 1, 2, 3))\n  feature_group_count=1\n  lhs_dilation=(1, 1, 1)\n  lhs_shape=(1, 64, 64, 64, 3)\n  padding=((1, 1), (1, 1), (1, 1))\n  precision=None\n  preferred_element_type=None\n  rhs_dilation=(1, 1, 1)\n  rhs_shape=(3, 3, 3, 3, 3)\n  window_strides=(1, 1, 1)\n]" source_file="/home/nagabhushana/anaconda3/envs/ddp_v2/lib/python3.9/site-packages/flax/linen/linear.py" source_line=305}, backend_config="{\"algorithm\":\"0\",\"tensor_ops_enabled\":false,\"conv_result_scale\":1,\"activation_mode\":\"2\",\"side_input_scale\":0}" failed. Falling back to default algorithm.

Convolution performance may be suboptimal.  To ignore this failure and try to use a fallback algorithm, use XLA_FLAGS=--xla_gpu_strict_conv_algorithm_picker=false.  Please also file a bug for the root cause of failing autotuning.

Observations

The error only occurs when recurrently applying the CNN using scan, i.e, the CNN on it's own runs fine.
The code runs successfully after commenting out the nn.relu activation function.
The code runs successfully if I use 2D convolutions instead of 3D convolutions, by changing kernel_size to (3, 3) and the input tensor shape to [1, 64, 64, 3].
The code runs successfully if I disable JIT compilation, using config.update('jax_disable_jit', True).

I'd be grateful if someone can help me solve this issue.

I think this is already fixed in the current JAX release. I was able to reproduce your problem with jax==0.2.24
and jaxlib==0.1.73+cuda11.cudnn805, but not with the current release (jax==0.3.4, jaxlib==jaxlib==0.3.2+cuda11.cudnn805).
Please use an up to date JAX release?


Resource fixes for Target Mode

Description
Add warning if Target Mode is executed as non-root. Fix bugs with sudo, package, rhsm_subscription, rhsm_register, selinux_install
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] I have read the CONTRIBUTING document.
[x] I have run the pre-merge tests locally and they pass.
[x] All new and existing tests passed.
[x] All commits have been signed-off for the Developer Certificate of Origin.

Pipeline failures seem to be a CI/CD issue, so marking this as "ready"

@thheinen There was this regression introduced in the previous target mode PR #14397 (comment) if you can get it corrected as well that will be good. Thanks.

Sorry for that! Added to the most recent commit


Fixing cross-compile issue

Os/user needs cgo so I change it by https://github.com/mitchellh/go-homedir.
Now we can cross-compile influxdb

Thanks for the patch @shinji62 . We actually have coding policy to avoid using 3rd packages unless it's absolutely necessary. Instead we prefer to find ways to solve problems using the standard libraries if at all possible.
So this PR:
https://github.com/influxdb/influxdb/pull/2039
is how we plan to fix this. Instead of the panic, the user will be informed that we can't determine sensible place for default storage and they need to tell us.


Update README

Reference: https://github.com/apollographql/apollo-server/pull/7601
Examples should demonstrate configuring the new precomputedNonce option for the landing page.

This has been resolved another way in Apollo Server v4.7.4 and this option shouldn't be used.


[CUDA] Support codegen for a dispatch with reduction + elementwise ops.

Request description
With the change in the dispatch fusion at https://github.com/iree-org/iree/pull/9693, we can put reduction and elementwise ops together in a dispatch, but the CUDA backend fails to compile. (x86_64, ARM, and vulkan are fine.)
LLVMGPUReduceToGPU fails to compile. See more info at https://github.com/iree-org/iree/pull/9693#issuecomment-1172760969
On the CPU side the loop for reduction is serialized, but for GPU, we might use warp reduction + block reduction to exploit the parallelism.
Bert-like models like miniLM heavily uses the pattern, so the benefit would be great.
What component(s) does this issue relate to?
Compiler
Additional context
No response

I believe this is done by @ThomasRaoux.

@ThomasRaoux Please close!

Solved by https://github.com/iree-org/iree/pull/9858


Unittesting docs

fixes #96

Good stuff here. A couple of nits left.

Thanks, really good suggestions.


whatis parse for rclone(1) failed

Hi,
following the Linux install guide, http://rclone.org/install/, I encountered this error while doing performing the last command, sudo mandb (these are the latest records):
Processing manual pages under /usr/local/share/man...
Updating index cache for path `/usr/local/share/man/man1'. Wait...mandb: warning: /usr/local/share/man/man1/rclone.1: whatis parse for rclone(1) failed
done.
Checking for stray cats under /usr/local/share/man...
Checking for stray cats under /var/cache/man/local...
1 man subdirectory contained newer manual pages.
1 manual page was added.
0 stray cats were added.
0 old database entries were purged.

I'm trying to install/use rclone v1.29 (rclone-v1.29-linux-amd64) on Ubuntu 14.04 LTS.
Even when trying to grab the rclone version is printing a failed error:
root@mysrv:~/rclone-v1.29-linux-amd64# rclone -V
2016/04/28 13:13:41 Failed to load config file "/root/.rclone.conf" - using defaults: open /root/.rclone.conf: no such file or directory
rclone v1.29

Is rclone not compatible with Ubuntu 14.04 LTS?

I don't think the whatis parse for rclone(1) failed is a problem - it is only a warning.  It probably means rclone won't appear in the whatis database.
As for Failed to load config file "/root/.rclone.conf" - using defaults: open /root/.rclone.conf: no such file or directory - then next step is to run rclone config to make the configuration for the remote fs.
So yes rclone should work fine with ubuntu 14.04 (I develop it on ubuntu!).

Yes, forgot to update. Seem to work properly. Thanks @ncw .


hikey.mk: write proper recipes for the 'loader' and 'temp' files

The 'loader' and 'temp' files are created and deleted by two targets
whose recipes may run concurrently (l-loader.bin and recovery.bin).
This can lead to build errors such as:
$ make -j8 hikey ...
[...]
python gen_loader_hikey.py -o l-loader.bin --img_loader=temp --img_bl1=bl2.bin
rm -f loader temp
Traceback (most recent call last):
File "gen_loader_hikey.py", line 181, in
main(sys.argv[1:])
File "gen_loader_hikey.py", line 176, in main
loader.create(img_loader, img_bl1, img_ns_bl1u, output_img)
File "gen_loader_hikey.py", line 145, in create
self.add(4, img_loader)
File "gen_loader_hikey.py", line 60, in add
fsize = os.path.getsize(fname)
File "/usr/lib/python2.7/genericpath.py", line 57, in getsize
return os.stat(filename).st_size
OSError: [Errno 2] No such file or directory: 'temp'
hikey.mk:25: recipe for target 'l-loader.bin' failed
Fix the problem by writing proper recipes for each file involved in the
build process.
Signed-off-by: Jerome Forissier<EMAIL_ADDRESS>

Ping?

Is this project still maintained?


ToC

Is it at all possible to get this back in the ToC somewhere?
I assume we're trying to push Azure Monitor for VMs, which is great, but in support I often have situations where I need to advise a customer on how to set up Log Analytics just for a specific log type and they may not want all of Monitor for VMs. It would be great to have this document back in the ToC.
Doc is still linked as "Manually from the Azure portal" through this page.
https://docs.microsoft.com/en-us/azure/azure-monitor/platform/log-analytics-agent
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: cfb49644-fb30-6357-708b-d2007fcab408
Version Independent ID: 3c6c3cac-e738-52c3-bf89-6476ba04e816
Content: Collect data from an Azure virtual machine with Azure Monitor - Azure Monitor
Content Source: articles/azure-monitor/learn/quick-collect-azurevm.md
Service: azure-monitor
Sub-service: logs
GitHub Login: @bwren
Microsoft Alias: bwren

@dcbrown16,  Thanks for the feedback! We are taking a look into this and will get back to you soon.

Assigning @bwren for visibility, review and document / ToC enhancement consideration as appropriate.

Sorry for this horribly late replay. Cleaning up some old issues that we missed. We actually have several updates coming on this topic. We need to highlight Arc as the primary hybrid story, and we're going to soon start shifting focus to the Azure Monitor agent instead of the Log Analytics agents as the means to collect log data. We're also restructuring the quickstarts and tutorials. We are definitely presenting Azure Monitor for VMs as the primary means to monitor VMs and to install the agent, but we'll be clear that there are other options.
#please-close


Details clean up

This should get detailsOfObject working again, as well as eliminate redundant details (as @pjrobertson is trying to do with #613).
Was there ever a reason to show an HFS path? Didn’t make sense to me, so I killed it.
As for the actual fix, what do you think? I can’t help wondering if the “correct” way to handle this is to make sure [self bundle] is returning something useful so we don’t need to test it at all. But I’m not sure what it’s supposed to be for a garden-variety QSObject. The bundle for the plug-in that created the object maybe?
Right now, it’s trying to get a bundle using the object’s identifier, which seems like it will never work. Some debugging shows that it currently only works for actions and file objects (where the identifier is a path).
In any case, I think this fix is good. Even if we can get a valid bundle returned in most cases, we shouldn't assume it will always be there.

Oh, and it also causes the details to show up for actions (which should be a great help to new users). Did anyone even remember that they existed? :-)

in my change, the whole business of trying to setting the height, cutting it if it's more than 100 chars etc. is only run if it's really needed.

I admit I didn't fully understand what you were doing, but now that I do, that's a good point.

This change will mean that that code (linked to above) is run every time - kind of wasteful IMO. Probably only a few µs, but they all count...

I think we should always prefer speed over code that's easier to wrap our heads around. Many details strings could be “processed” in a very short time, so I think it's worth it.
I think we should keep both our changes. You're calling the details method and then testing to see if it's nil (among other things). With my change, it will be nil if name and label are identical and the code will be skipped.
Maybe you could even simplify your check by eliminating the string comparison (since it will have already taken place in details)? In other words, you could get rid of all the code that sets up BOOL detailsAndNameDifferent and instead just test if (detailsString).

I admit I didn't check the code fully - limited internet and time etc. but with what you've explained, I now realised the details method you modified gets called by the code that I modified.
Looking at it - yeah, I think what you said above is the best. i.e. do the check in the details method as opposed to in the method I was modifying.
To slim down objects, would it be worth changing what you've done in the details method to be:
  if ([details isEqualToString:[self displayName]]) {
        [meta setObject:nil forKey:lQSObjectDetails];

so that the object is tidied up a bit, or is it worth keeping the details as is?
actually... after typing that, surely the correct thing to do would be to never set the details to be the same as the display name. There must be a piece of code somewhere which is going
if there's nothing else useful, set the details to be the display name

Looking at it - yeah, I think what you said above is the best. i.e. do the check in the details method as opposed to in the method I was modifying.

Ah, but then I reversed myself on that. :-)

actually... after typing that, surely the correct thing to do would be to never set the details to be the same as the display name. There must be a piece of code somewhere which is going

if there's nothing else useful, set the details to be the display name

I thought about that, but after what I ran into yesterday, I don’t think there’s a practical way to intercept that. Yeah, that check is probably happening somewhere, but there are lots of other ways details can be set. We could put a check in setDetails:, but in many cases, the details don’t even exist until they’re requested by the details method (which will try a few things to create them on the fly if they were never set).
Bottom line, I think #613 gives us what we want. (And then this one will make the details show up as intended.)

You mean the old 247 or the new 247? Looks like you linked to the new one, but QSGetLocalizationStatus() doesn’t get called at all after my change, so I’m confused. :-)
Are you wondering why we never saw the colons in paths if QSGetLocalizationStatus() was always true? I never saw them until I fixed the details method. The result of detailsOfObject: was almost universally being blown away and replaced with nil.
Having said that, this : business was present in B54 where detailsOfObject: was working, but it was based on a test of QSIsLocalized instead. Looked around a bit and I can’t explain why the HFS path didn’t show up in B54, too. I have a theory. (This is getting way too long - sorry.) The QSGetLocalizationStatus() function just figures out and returns QSIsLocalized. Why switch from the variable to the function (as someone did post-54)? Maybe the variable wasn’t set in that scope, so the if was always false, and that’s why we never saw the colon substitution before. That function is strange anyway. It seems to be checking whether or not English is one of the available localizations. Not the active one, just one of them period. Won’t that always be true?
Anyway, can you think of any reason why we should ever show the HFS path?

I haven't really caught up on all of this yet, but I wanted to comment on one of Rob's remarks:

I think we should always prefer speed over code that's easier to wrap our heads around.

 I totally completely disagree. I think we should always keep the code that easier to read and only try to speed things up if we can keep the code readable AND once we have proven, that this part of the code actually slows down the user experience AND that the change actually makes things significantly faster.
There are a few reasons for my very strong opinion about this:

Speed problems mostly solve themselves. Computers get faster by the minute. What seems like slow today wont be a problem on the next generation of Macs.
Anything that hurts maintainability is bad bad bad! QS is such a mess because of lots of those little changes "oh, lets try to make this little thing a little faster"
Until you tested the speed before and after the change, you have no way to know if it actually speeds things up. Even if you are absolutely sure that it would help, profiling often reveals surprising things.
And even if it speeds things up, was it enough to matter? Was it enough to justify sacrificing maintainability?

Of course every little bit of speed we can get out of QS is nice, but only worth it if we don't make things worse somewhere else.
Again, I haven't read the whole discussion and don't really know what you are talking about. But this sentence jumped out to me, because I have very strong feelings about this.

@HenningJ - considering what you've said, I'd definitely agree. Obviously the optimum solution is to have best maintainability and best speed ;-)
There was no real tradeoff between the two solutions in the end anyway as you'll find out if you read through everything (Rob's method 'could' cause various problems later on down the line)
Probably completely unrelated, but I came across this when testing filenames with slashes in them:

Create a/b/c.txt on your desktop
Invoke QS and perform: a/b/c.txt | copy to... | somewhere. (or move to...)
The file copies but you get an error saying it didn't copy.

About the function being funny - I looked at it just now and the only reasoning I can come up with is that it returns 'nil' if there aren't any localised files. E.g. if a file isn't localized it'll be called 'file.strings' whereas if it is localised, it'll be a group with 'file.strings (English)' etc. inside it.

But doesn’t [NSBundle mainBundle] always refer to Quicksilver? So won’t it always be the same? And why show an HFS path simply because an English localization exists (ignoring whether or not it’s the one being used)? So many question. None of which need to be answered since you aren’t pushing for HFS paths in the details. :-)

I've played with this, and bar my comment here [1] this all seems fine.
I'll wait incase @HenningJ has anything to add.
[1] https://github.com/quicksilver/Quicksilver/pull/624#issuecomment-3483253
On 13 January 2012 18:21, Rob McBroom <
<EMAIL_ADDRESS>
wrote:

About the function being funny - I looked at it just now and the only
reasoning I can come up with is that it returns 'nil' if there aren't any
localised files. E.g. if a file isn't localized it'll be called
'file.strings' whereas if it is localised, it'll be a group with
'file.strings (English)' etc. inside it.

But doesnt [NSBundle mainBundle] always refer to Quicksilver? So wont
it always be the same? And why show an HFS path simply because an English
localization exists (ignoring whether or not its the one being used)? So
many question. None of which need to be answered since you arent pushing
for HFS paths in the details. :-)

Reply to this email directly or view it on GitHub:
https://github.com/quicksilver/Quicksilver/pull/624#issuecomment-3483918

I think we should always prefer speed over code that's easier to wrap our heads around.

 I totally completely disagree. I think we should always keep the code that easier to read and only try to speed things up if we can keep the code readable AND once we have proven, that this part of the code actually slows down the user experience AND that the change actually makes things significantly faster.

Let me amend my statement to include the phrase “within reason” somewhere. You make a good case (given Quicksilver’s history), so I’m with you in 90% of the cases. But there will be exceptions. For instance, a recent change I made to the iTunes plug-in is far more complicated than I would like. There is a way to do the same thing with a one or two line change, but it maxes out your CPU for several minutes before any music starts playing. The convoluted technique I came up with runs in under 0.5s.
The main exception I would make to your argument is: If Quicksilver becomes too slow to keep up with a human’s typing, it’s a deal breaker. It seems unlikely we’ll ever run into that issue. (Meaning that if we do something to slow it down that much, we probably won’t have a super-complicated-but-faster alternative.) That’s sort of what was at issue when I made that statement.

The file copies but you get an error saying it didn't copy.

I can’t reproduce this. I tried with master and saw no problems, so then I tried with various pull requests (including this one) merged in and it seems to copy and move just fine. Another user just reported the same behavior you describe, but it involves large files (and the name doesn’t matter).

Rob's method 'could' cause various problems later on down the line

A method that was reverted and is no longer part of this pull request, in case that isn’t clear. :-)

The file copies but you get an error saying it didn't copy.

I cant reproduce this.

OK so I rebuilt in 32 bit mode and it works fine. May have been an issue
with me building in 64 bit even though master is not quite ready for it.
@HenningJ have you had a chance to read through this and see what you think?
On 13 January 2012 19:06, Rob McBroom <
<EMAIL_ADDRESS>
wrote:

The file copies but you get an error saying it didn't copy.

I cant reproduce this. I tried with master and saw no problems, so then I
tried with various pull requests (including this one) merged in and it
seems to copy and move just fine. Another user just reported the same
behavior you describe, but it involves large files (and the name doesnt
matter).

Rob's method 'could' cause various problems later on down the line

A method that was reverted and is no longer part of this pull request, in
case that isnt clear. :-)

Reply to this email directly or view it on GitHub:
https://github.com/quicksilver/Quicksilver/pull/624#issuecomment-3484574

Let me amend my statement to include the phrase “within reason” somewhere.

Good that you cleared that up. You're right, sometimes we have to take the ugly way out.
I'm happy now. :-)

@HenningJ have you had a chance to read through this and see what you think?

No, I haven't. I was sick in bed most of yesterday and couldn't really concentrate on anything.
But since Rob reverted the thing I took issue with long before I commented, I'm fine with anything.

I was sick in bed most of yesterday

:( Get well soon.
I'll merge this then :)


expand stats

Reformatting GraphQL queries for maintainability
Refactored curl for gh api calls, enhancements
Removing unnecessary first:1 for totalCount use
Expand data captured, predictable order

Example of running changes:
$ gh repo-stats -o tinyfists

######################################################
######################################################
############# GitHub repo list and sizer #############
######################################################
######################################################

------------------------------------------------------
Falling back to GitHub token via 'gh auth token'
Creating file header...
------------------------------------------------------
Getting repositories for org: tinyfists
Rate limits remaining: 5,000 GraphQL points  14,986 REST calls
Analyzing Repo: actions-experiments
Analyzing Repo: archived-template
Analyzing Repo: archived-template-demo
Analyzing Repo: asdfasdf
Analyzing Repo: git-xargs
Analyzing Repo: git-xargs-1
Analyzing Repo: git-xargs-2
Analyzing Repo: git-xargs-3
Analyzing Repo: githubcustomer
Analyzing Repo: intro-to-github-niall
Rate limits remaining: 5,000 GraphQL points  14,986 REST calls
Analyzing Repo: issue-driven-github-admin
Analyzing Repo: issue-form-preview
Analyzing Repo: multi-runner-poc
Analyzing Repo: old-repo-name
Analyzing Repo: old-repo-name-2
Analyzing Repo: pages-demo
Analyzing Repo: publish-packages-to-repo-demo
Analyzing Repo: required-workflows
Analyzing Repo: required-workflows-demo
Analyzing Repo: secret-scanning-tests
Rate limits remaining: 5,000 GraphQL points  14,986 REST calls
Analyzing Repo: services
Analyzing Repo: spring-framework
Analyzing Repo: stacks-experiment
Analyzing Repo: stacks-experiment-01
Analyzing Repo: template-bar
Gathered all repositories for org: tinyfists

######################################################
The script has completed

Results file:[tinyfists-all_repos-202304281302.csv]
######################################################

Resulting output: tinyfists-all_repos-202304281302.csv
Example of debug output:
$ gh repo-stats -o tinyfists -d

######################################################
######################################################
############# GitHub repo list and sizer #############
######################################################
######################################################

------------------------------------------------------
Falling back to GitHub token via 'gh auth token'
* Request at 2023-04-28 13:09:28.235137 -0400 EDT m=+0.034106872
* Request to https://api.github.com/user
> GET /user HTTP/1.1
> Host: api.github.com
> Accept:
> Authorization: token ████████████████████
> Content-Type: application/json; charset=utf-8
> Time-Zone: America/New_York
> User-Agent: GitHub CLI 2.25.1

< HTTP/2.0 200 OK
< Access-Control-Allow-Origin: *
< Access-Control-Expose-Headers: ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Resource, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, X-GitHub-SSO, X-GitHub-Request-Id, Deprecation, Sunset
< Cache-Control: private, max-age=60, s-maxage=60
< Content-Security-Policy: default-src 'none'
< Content-Type: application/json; charset=utf-8
< Date: Fri, 28 Apr 2023 17:09:28 GMT
< Etag: W/"f38c9d9ee03086d45fdb02a98cf38d306d1cb1e0d444f39f4996f8853effc6dd"
< Last-Modified: Wed, 26 Apr 2023 15:20:07 GMT
< Referrer-Policy: origin-when-cross-origin, strict-origin-when-cross-origin
< Server: GitHub.com
< Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
< Vary: Accept, Authorization, Cookie, X-GitHub-OTP
< Vary: Accept-Encoding, Accept, X-Requested-With
< X-Accepted-Oauth-Scopes:
< X-Content-Type-Options: nosniff
< X-Frame-Options: deny
< X-Github-Api-Version-Selected: 2022-11-28
< X-Github-Media-Type: github.v3; format=json
< X-Github-Request-Id: FAB0:7023:9FFEA:148FA5:644BFDC8
< X-Oauth-Client-Id: 178c6fc778ccc68e1d6a
< X-Oauth-Scopes: admin:enterprise, admin:org, admin:org_hook, gist, project, repo, workflow
< X-Ratelimit-Limit: 15000
< X-Ratelimit-Remaining: 14985
< X-Ratelimit-Reset:<PHONE_NUMBER>
< X-Ratelimit-Resource: core
< X-Ratelimit-Used: 15
< X-Xss-Protection: 0

{
  "login": "andyfeller",
  "id": 2089743,
  "node_id": "MDQ6VXNlcjIwODk3NDM=",
  "avatar_url": "https://avatars.githubusercontent.com/u/2089743?v=4",
  "gravatar_id": "",
  "url": "https://api.github.com/users/andyfeller",
  "html_url": "https://github.com/andyfeller",
  "followers_url": "https://api.github.com/users/andyfeller/followers",
  "following_url": "https://api.github.com/users/andyfeller/following{/other_user}",
  "gists_url": "https://api.github.com/users/andyfeller/gists{/gist_id}",
  "starred_url": "https://api.github.com/users/andyfeller/starred{/owner}{/repo}",
  "subscriptions_url": "https://api.github.com/users/andyfeller/subscriptions",
  "organizations_url": "https://api.github.com/users/andyfeller/orgs",
  "repos_url": "https://api.github.com/users/andyfeller/repos",
  "events_url": "https://api.github.com/users/andyfeller/events{/privacy}",
  "received_events_url": "https://api.github.com/users/andyfeller/received_events",
  "type": "User",
  "site_admin": true,
  "name": "Andy Feller",
  "company": "GitHub",
  "blog": "",
  "location": null,
  "email"<EMAIL_ADDRESS>  "hireable": null,
  "bio": "DevOps Engineer with GitHub's Expert Services, I'm a self proclaimed disciple of J. Wellington Wimpy and Shawn Spencer, looking for delicious flavor.",
  "twitter_username": null,
  "public_repos": 43,
  "public_gists": 10,
  "followers": 32,
  "following": 9,
  "created_at": "2012-08-03T13:23:51Z",
  "updated_at": "2023-04-26T15:20:07Z"
}

* Request took 183.287732ms
Successfully validated access to GHE Instance...
Version: cloud
Creating file header...
 Getting Repo Stats
------------------------------------------------------
Getting repositories for org: tinyfists
* Request at 2023-04-28 13:09:28.789282 -0400 EDT m=+0.037580291
* Request to https://api.github.com/rate_limit
> GET /rate_limit HTTP/1.1
> Host: api.github.com
> Accept:
> Authorization: token ████████████████████
> Content-Type: application/json; charset=utf-8
> Time-Zone: America/New_York
> User-Agent: GitHub CLI 2.25.1

< HTTP/2.0 200 OK
< Access-Control-Allow-Origin: *
< Access-Control-Expose-Headers: ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Resource, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, X-GitHub-SSO, X-GitHub-Request-Id, Deprecation, Sunset
< Cache-Control: no-cache
< Content-Security-Policy: default-src 'none'
< Content-Type: application/json; charset=utf-8
< Date: Fri, 28 Apr 2023 17:09:29 GMT
< Referrer-Policy: origin-when-cross-origin, strict-origin-when-cross-origin
< Server: GitHub.com
< Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
< Vary: Accept-Encoding, Accept, X-Requested-With
< X-Accepted-Oauth-Scopes:
< X-Content-Type-Options: nosniff
< X-Frame-Options: deny
< X-Github-Api-Version-Selected: 2022-11-28
< X-Github-Media-Type: github.v3; format=json
< X-Github-Request-Id: FAB2:0A48:BED20:1863A8:644BFDC8
< X-Oauth-Client-Id: 178c6fc778ccc68e1d6a
< X-Oauth-Scopes: admin:enterprise, admin:org, admin:org_hook, gist, project, repo, workflow
< X-Ratelimit-Limit: 15000
< X-Ratelimit-Remaining: 14984
< X-Ratelimit-Reset:<PHONE_NUMBER>
< X-Ratelimit-Resource: core
< X-Ratelimit-Used: 16
< X-Xss-Protection: 0

{
  "resources": {
    "core": {
      "limit": 15000,
      "used": 16,
      "remaining": 14984,
      "reset":<PHONE_NUMBER>
    },
    "search": {
      "limit": 30,
      "used": 0,
      "remaining": 30,
      "reset":<PHONE_NUMBER>
    },
    "graphql": {
      "limit": 5000,
      "used": 37,
      "remaining": 5000,
      "reset":<PHONE_NUMBER>
    },
    "integration_manifest": {
      "limit": 5000,
      "used": 0,
      "remaining": 5000,
      "reset":<PHONE_NUMBER>
    },
    "source_import": {
      "limit": 100,
      "used": 0,
      "remaining": 100,
      "reset":<PHONE_NUMBER>
    },
    "code_scanning_upload": {
      "limit": 1000,
      "used": 0,
      "remaining": 1000,
      "reset":<PHONE_NUMBER>
    },
    "actions_runner_registration": {
      "limit": 10000,
      "used": 0,
      "remaining": 10000,
      "reset":<PHONE_NUMBER>
    },
    "scim": {
      "limit": 15000,
      "used": 0,
      "remaining": 15000,
      "reset":<PHONE_NUMBER>
    },
    "dependency_snapshots": {
      "limit": 100,
      "used": 0,
      "remaining": 100,
      "reset":<PHONE_NUMBER>
    }
  },
  "rate": {
    "limit": 15000,
    "used": 16,
    "remaining": 14984,
    "reset":<PHONE_NUMBER>
  }
}

* Request took 146.329116ms
Rate limits remaining: 5,000 GraphQL points  14,984 REST calls
Getting repos
* Request at 2023-04-28 13:09:29.077208 -0400 EDT m=+0.034324082
* Request to https://api.github.com/graphql
> POST /graphql HTTP/1.1
> Host: api.github.com
> Accept:
> Authorization: token ████████████████████
> Content-Length: 2325
> Content-Type: application/json; charset=utf-8
> Time-Zone: America/New_York
> User-Agent: GitHub CLI 2.25.1

GraphQL query:
query($login: String!, $pageSize: Int!, $endCursor: String) {
    organization(login: $login) {
      repositories(first: $pageSize, after: $endCursor, orderBy: {field: NAME, direction: ASC}) {
        totalDiskUsage
        pageInfo {
          endCursor
          hasNextPage
        }
        nodes {
          branches: refs(refPrefix:"refs/heads/") {
            totalCount
          }
          branchProtectionRules {
            totalCount
          }
          commitComments {
            totalCount
          }
          collaborators {
            totalCount
          }
          diskUsage
          discussions {
            totalCount
          }
          hasWikiEnabled
          isEmpty
          isFork
          issues(first: $pageSize) {
            totalCount
            pageInfo {
              endCursor
              hasNextPage
            }
            nodes {
              timeline {
                totalCount
              }
              comments {
                totalCount
              }
            }
          }
          milestones {
            totalCount
          }
          name
          owner {
            login
          }
          projects {
            totalCount
          }
          pullRequests(first: $pageSize) {
            totalCount
            pageInfo {
              endCursor
              hasNextPage
            }
            nodes {
              comments {
                totalCount
              }
              commits {
                totalCount
              }
              number
              reviews(first: $pageSize) {
                totalCount
                pageInfo {
                  endCursor
                  hasNextPage
                }
                nodes {
                  comments {
                    totalCount
                  }
                }
              }
              timeline {
                totalCount
              }
            }
          }
          pushedAt
          releases {
            totalCount
          }
          tags: refs(refPrefix: "refs/tags/") {
            totalCount
          }
          updatedAt
        }
      }
    }
  }
GraphQL variables: {"login":"tinyfists","pageSize":10}

Let's address the checks and we can proceed. @andyfeller

@ssulei7 : we're on the same page 👍  I'm also working on updating the documentation and potentially changing some of the flags because this is going to now rely upon gh api, so the flags for tokens and url should behave differently


forgot to update the doc [has > contains]

http://sugarjs.com/api/String/has
cf 9df9ec01f06ccc45b7dbecd90eabef13b25c1f48
You could keep it as an alias.
#463 is related.

This will be affected when 1.5 goes out (will update all the docs at that time).

Just a quick note, old version docs are now supported on the site. Look for the little vertical "..." next to the menu bar to change the version.

@andrewplummer I am not seeing contains mentioned in either versions though.

Ah sorry. I commented in #463, but forgot to comment here as well. has is now includes in v2 but is a polyfill for the ES6 method. has will continue on in v1 as is.  The original change you commented on has moved on, but contains was effectively reverted.


Handle split reads

Handle split reads when used with tcp input for exemple.
I replaced input buffer processing with BufferedTokenizer to handle the case when a line is not read completely.
Also, i strip the carriage return if any so that the grok can work correctly.

Jenkins standing by to test this. If you aren't a maintainer, you can ignore this comment. Someone with commit access, please review this and clear it for Jenkins to run; then  say 'jenkins, test it'.

@doubret - I'm sorry for not picking up this PR sooner.
This codec is going through some big changes at the moment, and the code now is not as it was when you branched.
Further, I do not believe that this codec needs this modification.  Its stated goal and whole reason for being is to gather multiple lines that belong together into one event.  Note the emphasis on lines - meaning that the upstream source of data really should honour this "contract" and feed this codec whole lines.
After all Its only the upstream source that "knows" about the structure and format of the data that it is receiving.


Added frozen lockfile option on ci and dev workflows

Added frozen lockfile option on ci and dev yarn install to fail if the lockfile is out of date

Prevents review work like https://github.com/hotwired/turbo/pull/1010#issuecomment-1727675122

Nice, thanks @shiftyp 🙏


Broken link

Needs to be re-pointed to the correct page

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

ID: 13e03a42-8e14-e95f-a6dc-998cf9f99e94
Version Independent ID: 80a356ef-6cc7-5538-93ee-42b7ccde3dd8
Content: Which fields can be synchronized between Dynamics 365 and Outlook?
Content Source: ce/outlook-addin/admin-guide/which-fields-synchronized.md
Service: crm-online
GitHub Login: @mduelae
Microsoft Alias: mkaur

Thanks for bringing this to our attention. The link has been fixed.


Failure to generate azure-mgmt-network

Describe the issue
I'm running into errors generating azure-mgmt-network (have only tried 2019-11 and 2019-09). I get the following error:
Error: The 'title' across provided OpenAPI definitions has to match. Found: 'NetworkManagementClient', 'ExpressRouteCrossConnection REST APIs', 'VirtualWANAsAServiceManagementClient', 'WebApplicationFirewallManagement'. Please adjust or provide an override (--title=...).
** REQUIRED **
ModelerFour version: 4.6.199
AutoRest-core version: 3.0.6198
CommandLine : autorest-beta test\services\azure-mgmt-network\README.md --use=. --tag=package-2019-11 (running from root of my local autorest.python repo)
OpenAPI/Swagger file: Here's the readme file i'm using for network:

readme.md has title defined. It should get picked.
title: NetworkManagementClient
description: Network Client
openapi-type: arm

Or you can add --title=NetworkManagementClient to autorest-beta
I think the real problem is that --tag is no longer supported in v3.
java works fine with 2019-06-01 (after tag is somehow handled).

@weidongxu-microsoft tag is now supported in v3, you can try generating with the latest version of autorestv3 (it's readme contains the latest versions of autorest-core and modelerfour as well)


fix smpeg2 to use SDL2d in debug mode

Simple tweak so that smpeg2 compiled in debug mode uses SDL2d instead of SDL2.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: MerickOWA sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Looks great, thanks for the PR!


GitHub Action

Reference Issues/PRs
#24
What does this implement/fix? Explain your changes.

Test system modified

Any other comments?

Codecov Report

Merging #25 (a6641b9) into dev (c4f3bb1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev      #25   +/-   ##
=======================================
  Coverage   95.66%   95.66%
=======================================
  Files           2        2
  Lines         161      161
  Branches       18       18
=======================================
  Hits          154      154
  Misses          4        4
  Partials        3        3

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 c4f3bb1...a6641b9. Read the comment docs.

Codecov Report

Merging #25 (a6641b9) into dev (c4f3bb1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev      #25   +/-   ##
=======================================
  Coverage   95.66%   95.66%
=======================================
  Files           2        2
  Lines         161      161
  Branches       18       18
=======================================
  Hits          154      154
  Misses          4        4
  Partials        3        3

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 c4f3bb1...a6641b9. Read the comment docs.


MH-13593: Incorrect default waveform colors

Resolving the white waveform image issue:

This patch resolves an issue where the waveform workflow operation overwrote the service-wide defaults with its current settings.
The waveform service's service wide setting was also (by default) blank, which leads to white images, which are invisible in the current UI.
Set the default of black when the waveform WOH's color parameter was blank.

I see @lkiesow was a little faster than me with #932.  Whoever takes these please only merge one of them :)

This is a coincidence, I made the same solution (Only that default to black if there was an empty string instead of a null one) last Tuesday, but I discarded because the All in one installation don't have this problem.
For Me the problem is not in this part, it is a consequence of something in the way that there are sent or received the messages.
Anyways this works and creates a layer of redundancy,

Should be ready for review again!


Remove Clone from IbcEvent and all its variants

Closes: #2485

PR author checklist:

[ ] Added changelog entry, using unclog.
[ ] Added tests: integration (for Hermes) or unit/mock tests (for modules).
[ ] Linked to GitHub issue.
[ ] Updated code comments and documentation (e.g., docs/).
[ ] Tagged one reviewer who will be the one responsible for shepherding this PR.

Reviewer checklist:

[ ] Reviewed Files changed in the GitHub PR explorer.
[ ] Manually tested (in case integration/unit/mock tests are absent).

Will opt for a different solution.


Governance. Vote. Wrong signer is shown on QR modal window

Description
When user try to Vote as a multisig - QR modal window shows the multisig wallet as a signer:

Expected Behavior
Selected signer wallet
Actual Behavior
The multisig itself
Environment
https://github.com/novasamatech/nova-spektr/commit/f0478b0ec6f2c9a4089e196925d183a21f1c4f22
Test data:
accounts.json
wallets.json

Status verification: ✅


Add new algorithm for face recognition

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Approach to be followed (optional)
A clear and concise description of the approach to be followed.
Additional context
Add any other context or screenshots about the feature request here.

hey @akshitagupta15june , Hope you are doing ,  I would gladly prefer to work on the above issue , I have compatible skills and experience for this issue.  So please assign it to me
Thank You

Hi @akshitagupta15june,
I have recognized the issue regarding to implementing a new algorithm for face recognition to enhance our project’s accuracy and performance. , e.g., "the misclassification of neutral expressions as negative sentiment". The solution involved libraries or modules languages describe the fix, e.g., "FaceNet uses deep learning with triplet loss to distinguish subtle differences between facial expressions, reducing misclassification.". Please give me the chance and let me do the  further adjustments that are needed.
Best,
Darakhshan

Hello @akshitagupta15june,
Could you please assign me this issue??


consistently pin against Lotus v1.9.0

(see commit message)

I'm worried that once we do this we are going to have to have a pretty constant stream of updates that we don't have automation on in order to keep the lotus we're testing against up to date. There's a pretty rapid release schedule, and in order to test deal successes, we want the bot to always be against the latest version. I wonder if we have a way to know which version has been promoted to infra and automatically have our tests also run against that?

You're right, though always using the latest master has the same problem and also makes CI/testing more unreliable.
How often does infra get its Lotus version updated, and how? In that process, we could possibly introduce a sed find-and-replace command to update the version picked for testing, too. cc @coryschwartz

@willscott what do you want to do here, then? We can agree that pinning Lotus in separate ways for testing and deploying is not great, but not pinning Lotus at all for testing seems worse however you look at it :) Especially since we're currently following master, which could break in unexpected ways at any moment.
I'm happy to look at ways to make the testing and deploying pinning to always be in sync, but I'll need some collaboration with infra on that.

I'd rather see tests break and realize it's lotus as a heads up, rather than having that happen first in an infra deployment?
Lotus has a fairly high bar before they merge to master, so i don't think we run into lotus breaking, and if things have been accepted/merged that break this, that's probably a thing we want to know through tests at that point and be able to make noise about it.

@willscott I've undone the bits about pinning lotus, as I think the other changes are still worth merging :)


vscode intellisense not working

I do really trouble in vscode, I restarted it and reboot my computer again and again. The IntelliSense is not working and this just happened in javascript(.js).

and in .css or .vue lookes like that:

But when I just opened vscode, IntelliSense will work in a second in javascript.
Did anyone else face this problem?

Please file out the issue template
/needsMoreInfo

This same issue occurred to me,  re-installed vscode, uninstalled all extensions, re-installed npm but nothing seems to fix it.
It was working just fine few days ago, i guess before the last update.
Also, i use eslint in my project if that helps.

Duplicate of #87034

@xuwentao93 Downgrading to 1.40.2 seems to resolve this issue.

@walidbagh still not working...

@walidbagh still not working...

For me , that fixed it.
You need to make sure, you disabled updates, after installing 1.40.2 (or any earlier version) or else vscode will auto update on the first restart.

@xuwentao93 Again, please fill out the issue template and provide steps to reproduce. Otherwise we can't investigate this issue

I don't know how to explain it, briefly, just a new system with new vscode, but intellisense is not working. Maybe after I use create-react-app to create a new project.

I find it will work in typescript, but when I type in javascript, both are not work.

oh, I think it must caused by create-react-app or vue-cli, I can use normally in any .js when I config the webpack myself.


retry_on_status setting does not work as expected with requests that should not be retried immediately

Steps to reproduce:
Happens for me on clusters of 8.12 and 8.13 with clients of same versions, I assume it happens in earlier clusters as well.

Have a cluster that's rather small (I used 2GB RAM Elasticsearch in Elastic Cloud)
Have a script that bombs this cluster with bulk requests that will eventually lead to this cluster returning 429 back.
Have another script that just does search on this cluster with Elasticsearch client that is initialised with default retry_on_status - presumably, it should retry 429s.

What happens is - client in 3. actually retries 429, but fails almost immediately as it does not try to sleep with any sort of backoff strategy, so it retries a couple times in a row within a second and give up.
Expected behaviour
Client allows to retry with a backoff strategy. Additionally, if the client is closed, would be great if the pending retry immediately wakes up and exits without retrying (see https://github.com/elastic/elasticsearch-py/issues/2484)

I transferred this issue from elasticsearch-py as retries are implemented in the transport. Implementation itself is simple enough. Without considering tests for now, this diff is enough:
diff --git a/elastic_transport/_async_transport.py b/elastic_transport/_async_transport.py
index 1e66f74..20e6d6a 100644
--- a/elastic_transport/_async_transport.py
+++ b/elastic_transport/_async_transport.py
@@ -47,6 +47,7 @@ from ._transport import (
     NOT_DEAD_NODE_HTTP_STATUSES,
     Transport,
     TransportApiResponse,
+    backoff_time,
     validate_sniffing_options,
 )
 from .client_utils import resolve_default
@@ -366,6 +367,7 @@ class AsyncTransport(Transport):
                 if not retry or attempt >= max_retries:
                     return TransportApiResponse(resp.meta, body)
                 else:
+                    await asyncio.sleep(backoff_time(attempt))
                     _logger.warning(
                         "Retrying request after non-successful status %d (attempt %d of %d)",
                         resp.meta.status,
diff --git a/elastic_transport/_transport.py b/elastic_transport/_transport.py
index bf1de58..9621806 100644
--- a/elastic_transport/_transport.py
+++ b/elastic_transport/_transport.py
@@ -86,6 +86,10 @@ class TransportApiResponse(NamedTuple):
     meta: ApiResponseMeta
     body: Any

+def backoff_time(attempts: int, base: int = 1, cap: int = 60):
+    # Full Jitter from https://aws.amazon.com/blogs/architecture/exponential-backoff-and-jitter/
+    return random.uniform(0, min(cap, base * 2 ** (attempts - 1)))
+

 class Transport:
     """
@@ -444,6 +448,7 @@ class Transport:
                 if not retry or attempt >= max_retries:
                     return TransportApiResponse(resp.meta, body)
                 else:
+                    time.sleep(backoff_time(attempt))
                     _logger.warning(
                         "Retrying request after non-successful status %d (attempt %d of %d)",
                         resp.meta.status,

However, I have two concerns:

Is it considered a breaking change to suddenly sleep between retries? This introduces sleeps for all retries: on status on the same node, but also on timeouts/connection errors on another node.
Are the sleeping defaults good enough? I'm using the "Full Jitter" algorithm from https://aws.amazon.com/blogs/architecture/exponential-backoff-and-jitter/ with base = 1 and cap = 60. If all retries get exhausted, 95% of total sleep times will be between ~60s and ~180s, with a median of ~120s.

Is it considered a breaking change to suddenly sleep between retries? This introduces sleeps for all retries: on status on the same node, but also on timeouts/connection errors on another node.

For me it might be hard to say - if we're concerned about it, might be worth to make it configurable and make default setting emulate previous behaviour?

Are the sleeping defaults good enough? I'm using the "Full Jitter" algorithm from https://aws.amazon.com/blogs/architecture/exponential-backoff-and-jitter/ with base = 1 and cap = 60. If all retries get exhausted, 95% of total sleep times will be between ~60s and ~180s, with a median of ~120s.

I think so. Especially since number of retries is configurable.

Thanks Artem! I also got feedback from @miguelgrinberg:

I'd say that the backoff_time function should be configurable, or at the least the base and cap arguments to it should be configurable. And maybe the default should be for them to be 0 so that the behavior does not change unless the user explicitly wants to use delays between retries.

I'm planning to make base and cap configurable (with better names like initial_sleep and maximum_sleep - to be confirmed). And will make sure that the default behavior does not change now (no sleep between retries).

It would also be nice to be able to say which status codes need a sleep between retries, but this is maybe overengineering.

I'll wait for an user to complain before having retries that sleep and other that don't. It is possible today to configure the status code that are retried and the ones that are not.


Clean up examples in API docs

This modifies the examples slightly so that the coding style is more in line with the doc site's top-level examples page (and getting started guides).

Yeah, I did a manual pass through the re-rendered pages to make sure nothing was amiss. Not much else you could really do!


Incorrect parent/child arrow direction for link that is both explicit and inferred

I have a note called Animal with the text [[Cat]], and a note called Cat with the text Parent:: [[Animal]].
When viewing Cat, the link is shown in the correct direction:

When viewing Animal however, the direction is inversed:

If I remove the [[Cat]] link in Animal, then the arrow direction is correct regardless of which note is selected.

I also have the same problem, despite deactivate the inferred button.

same problem here. A solution could be to override the unnamed back/forlink setting if a named relation (parent:: [[animal]]) is set as well between the two notes; at least I currently think this is what I would expect ;-)


The initialization window matches the editor base color or splash background color

Now, any window created by godot will be initialized to match the background color set by splash bg, and then the editor mode will be adapted to theme base color, which is to prevent the setting color and theme base color contrast over too large causing visual flicker. Yes,You can have it both ways. (only windows)
https://user-images.githubusercontent.com/14953625/137633490-586d1791-b2dc-4ce4-8987-3b680b623662.mp4

Would be very nice to get this one rebased or  salvaged for 4.0.

Why close?

I believe @CodeLazier mistakenly pushed the upstream master branch on their fork instead of their own rebased master branch with this PR's changes. And GitHub automatically closes PRs when their base branch has no difference with upstream (and they can't be reopened).
@CodeLazier You'll have to open a new PR with the contents of https://github.com/godotengine/godot/commit/f82ab2898a109b92818c4287242d783a60ba51b2.


Can't resolve 'fs'

When requiring this library for browser frontend use, I get this error.
Everything works otherwise, it's just this error showing in the console is annoying.

Same for me, using preact-cli

same here using straight node

appears that by adding the following export into my webpack config that the library works:
node: {
    fs: 'empty'
},

Same here in Angular project, it prevents compilation too.

The issue has been with the function save which works fine in node.js environment. However, a web browser does not have an open access to the file system, thus resulting in an error (require('fs'))
Hope the issue has been resolved with the version 1.1.0. Invoking the save(...) in a web browser will kindly pass the error in a callback function.

The issue has been with the function save which works fine in node.js environment. However, a web browser does not have an open access to the file system, thus resulting in an error (require('fs'))
Hope the issue has been resolved with the version 1.1.0. Invoking the save(...) in a web browser will kindly pass the error in a callback function.

Hi, do you means we cannot use this library with frontend code?
But it is working fine at this example https://codepen.io/bocko/pen/YLWNgj

Yes, the library works fine within the browser (frontend) - the algorithm is pure JavaScript after all.
Just to make it clear - only the save function is not available in the browser.

The problem is still there for angular projects. It does build but with a warning
/node_modules/qrcode-svg/lib/qrcode.js:413:13-26 - Warning: Module not found: Error: Can't resolve 'fs' in '...\node_modules\qrcode-svg\lib'
Why do we even need this save function that writes just the qrcode to a file?
Most of the time I just need the qrcode to insert it in a document, maybe save in a database, and send it to the printer.

For laravel-mix:
// webpack.mix.js

mix.webpackConfig({
    resolve: {
        fallback: {
            fs: false
        }
    }
});


A lof of uncaught exceptions

Hi, is there a way to hide these messages? Setting the log level doesn't hide them
Uncaught exception in update manager: [TD::Types::Message.new] :sender is missing in Hash input
Uncaught exception in update manager: [TD::Types::MessageReplyInfo.new] :recent_repliers is missing in Hash input
Uncaught exception in update manager: [TD::Types::Message.new] :sender is missing in Hash input
Uncaught exception in update manager: [TD::Types::MessageReplyInfo.new] :recent_repliers is missing in Hash input
Uncaught exception in update manager: [TD::Types::MessageReplyInfo.new] :recent_repliers is missing in Hash input
Uncaught exception in update manager: [TD::Types::MessageReplyInfo.new] :recent_repliers is missing in Hash input
Uncaught exception in update manager: [TD::Types::MessageReplyInfo.new] :recent_repliers is missing in Hash input
Uncaught exception in update manager: [TD::Types::Message.new] :sender is missing in Hash input
Uncaught exception in update manager: [TD::Types::Message.new] :sender is missing in Hash input
Uncaught exception in update manager: Can't find class for videoChat
Uncaught exception in update manager: [TD::Types::Message.new] :sender is missing in Hash input
Uncaught exception in update manager: [TD::Types::MessageReplyInfo.new] :recent_repliers is missing in Hash input
Uncaught exception in update manager: [TD::Types::MessageReplyInfo.new] :recent_repliers is missing in Hash input
Uncaught exception in update manager: [TD::Types::Message.new] :sender is missing in Hash input
Uncaught exception in update manager: [TD::Types::Message.new] :sender is missing in Hash input
Uncaught exception in update manager: [TD::Types::Message.new] :sender is missing in Hash input
Uncaught exception in update manager: [TD::Types::ChatMemberStatus::Administrator.new] :can_manage_voice_chats is missing in Hash input
Uncaught exception in update manager: Can't find class for videoChat
Uncaught exception in update manager: [TD::Types::MessageReplyInfo.new] :recent_repliers is missing in Hash input
Uncaught exception in update manager: [TD::Types::MessageReplyInfo.new] :recent_repliers is missing in Hash input
Uncaught exception in update manager: [TD::Types::MessageReplyInfo.new] :recent_repliers is missing in Hash input

I see this is unmaintained :cry:
Using https://github.com/seorgiy/tdlib-schema most of the exceptions are gone.
Also the env RUBYOPT="-W0" can be used to hide them all


Make publicKeyFromBech32 an Effect

The foreign import was incorrectly not in Effect, this PR makes the necessary changes to the import and the impacted code
https://github.com/Plutonomicon/cardano-transaction-lib/blob/d3ce766c4718c6924356c952dec0f1c70be92a89/src/Serialization.js#L97

Thanks for catching this!
But I think we can remove Effect entirely here and stick to just Maybe. Since we catch all exceptions, it would be safe.

@klntsky I thought that too, but wasn't sure if the reference is mutable in the wasm side of csl

Technically it's mutable: there's a free method. However, we don't use it from PS, so we can treat it as pure.
We do that already for some other types.


Passthrough generates conversion missing warning

I'm using a passthrough code block to specify the Google Analytics script:
++++
<script>
</script>
++++

No errors from the HTML generation. The PDF error generates:
asciidoctor: WARNING: conversion missing in backend pdf for pass

That's correct. Asciidoctor PDF does not support the passthrough block (since it doesn't bare much meaning). You need to filter this out using preprocessor directives.
ifdef::basebackend-html[]
++++
<script>
</script>
++++
endif::[]

This may be worth mentioning in the README. Therefore, I will keep it open as a documentation issue.

I'm pretty new to this... where can I find info on preprocessor directives?
On Fri, Jan 15, 2016 at 3:57 AM, Dan Allen<EMAIL_ADDRESS>wrote:

That's correct. Asciidoctor PDF does not support the passthrough block
(since it doesn't bare much meaning). You need to filter this out using
preprocessor directives.
ifdef::basebackend-html[]
++++

++++
endif::[]
This may be worth mentioning in the README. Therefore, I will keep it open
as a documentation issue.
—
Reply to this email directly or view it on GitHub
https://github.com/asciidoctor/asciidoctor-pdf/issues/390#issuecomment-171933019
.

--
Thanks,
Gunnar
If you think you can you can, if you think you can't you're right.

Unfortunately, it's one of the features we're behind on documenting in the user manual. See this open issue to find key resources and information. https://github.com/asciidoctor/asciidoctor.org/issues/283

Btw, it's probably better to add the Google Analytics via an extension. In fact, you can find such an extension in the extensions lab.

https://github.com/asciidoctor/asciidoctor-extensions-lab/blob/master/lib/google-analytics-postprocessor.rb

See https://github.com/asciidoctor/asciidoctor-extensions-lab#using-an-extension for how to apply it.

how to deal with mathematical formulas to PDF?
[latexmath,file="tex-formula-2.png"]
++++
\begin{align}
\dot{x} & = \sigma(y-x) \\
\dot{y} & = \rho x - y - xz \\
\dot{z} & = -\beta z + xyp
\end{align}
++++

i have same error:
asciidoctor: WARNING: conversion missing in backend pdf for pass

You need to the asciidoctor-mathematical extension to handle latexmath blocks. See https://github.com/asciidoctor/asciidoctor-mathematical/.

Thank you. Will it work on windows-7?
I tried to run the gem install asciidoctor-mathematical, began dependent software installation process. On the program mathematical process fails, the need to install Ruby DevKit, then I found out that is not enough cmake, it was not in the description of dependencies [gjtorikian/mathematical] (https://github.com/gjtorikian/mathematical) .
At the moment, I do not install cmake, I am in thought - how much more can all be required?

I do not know the exact requirements. You'll need to ask in that module (or on the Asciidoctor mailinglist).
I plan to publish another module named asciidoctor-mathoid that uses mathoid to generate the math image. That should be more portable as it only depends on Node. However, I haven't gotten it all working yet. See https://github.com/asciidoctor/asciidoctor-extensions-lab/tree/master/lib/mathoid-treeprocessor for a prototype.

Thanks for the answer
One day (maybe a year ago), I was faced with installing Node.js on WindowsXP. I do not remember for what program is needed.
Just remember that I did not achieve the work program.
I am afraid as though Node again did not become a stumbling block.
P.S. Now I use AsciidocFX, very friendly program, but with PDF as long as it is a lot of problems, I will have to deal with editing configuration files.

@mojavelinux what would be recommended way add underlined text that would work with pdf and html?
typically one would use +++<u>text</u>+++ or pass:[] macro.

never mind
looks like [underline]# text # works fine
Thank you

This happens because the basebackend for the PDF converter is html (that's just how the PDF converter works).
If you want to filter out content from the PDF, then you need to check ifdef::backend-html5 or ifndef::backend-pdf.

Btw, you should absolutely not be embedding a <style> element directly in your content. This is what docinfo is for. (docinfo can be contributed from a file or an extension).


Install failed

When clicking the link at the bottom of your README, HomeAssistant doesn't mange to install it. I get the error:
Error
The configuration flow could not be loaded: [object Object]

When looking at the console, I get: homeassistant.loader.IntegrationNotFound: Integration 'heatzy' not found.

It wasn't mentioned that Hacs was needed for this module (or at least the easiest/best way), so now I got it working.


Make SessionContext::enable_url_table consume self

Which issue does this PR close?
Fixes https://github.com/apache/datafusion/issues/12551
Rationale for this change
As described on https://github.com/apache/datafusion/issues/12551 the current non consuming API was confusing and caused silently ignored bugs
What changes are included in this PR?

Make SessionContext::enable_url_table consume self
Fix bug in example use
Add an "into_builder" API to SessionContext to make it easier to work with the builder pattern
Update documentation

Are these changes tested?

Are there any user-facing changes?

Thanks @andygrove  and @goldmedal


Feat(serialization): AsBytes Refactor and Improvements

AsBytes Refactor and Improvements
Description
Partially Closes #744.

[x] Change the Serializable trait to AsBytes, and .serialize() to .as_bytes(). This is more consistent with how other [x] - structures in Rust works, like Strings
[x] For all types that support .as_bytes(), support into() to create a Vec::
[x] For all types that support .as_bytes(), support try_into() to try to convert the data into an [u8] (Derived from From implementation)

Checklist

[x] Linked to Github Issue

Pat, this should solves task1, right ?

@MauroToscano From<_> implements into() as well.


Release 8.4.0

Summary of the Pull Request
OneFuzz release 8.4.0
8.4.0
Added

Agent: Include debug info in the release binaries to improve backtraces and debuggability #3194
Agent: Added a timeout when closing the app insight channels #3181
Agent/CLI/Service: Added extra_output container, rename extra container #3064
CLI: Added command onefuzz repro get_files for downloading files to locally reproduce a crash #3160

Changed

Agent: Removed agent traces from AppInsights #3143
Agent: Include debug info in the release binaries to improve backtraces and debuggability #3194
Deployment/Service: Enable Custom Metrics App Config Value #3190
Service: Moved authentication into middleware #3133
Service: Store authentication information in KeyVault #3127
Service: Port current logging implementation to ILogger #3173
Service: Added improved error reporting from scale-in protection modification #3184

Fixed

Agent: Skip entire function if entry offset excluded #3172
Agent: Make coverage-recording errors non-fatal #3166
Agent: Try to kill debuggee if Linux recording times out #3177
Service: Bumped C# and Rust dependencies #3200, #3165, #3168, #3153, #3169, #3185, #3191, #3163

Codecov Report

Merging #3201 (8e07742) into main (181545d) will decrease coverage by 6.78%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #3201      +/-   ##
==========================================
- Coverage   32.40%   25.63%   -6.78%
==========================================
  Files         180      152      -28
  Lines       22767    16289    -6478
==========================================
- Hits         7377     4175    -3202
+ Misses      15390    12114    -3276

see 332 files with indirect coverage changes