iFrame refresh

Even if I hardcoded the channel name without any other props, every some state values changes the iFrame refresh itself.

Thanks for filing an issue. Do you have any example code for what you are experiencing so I can reproduce the issue?

Going to close this for now. Most of the time if your state values are changing the iFrame in refreshing you might need to double-check how you're setting the passed props. It might think you're sending it new data when you actually now.

Sorry, I forgot to check the notifications.
Here's a basic example, every time I click on the button, the iframe refresh even with the channel name hardcoded
export default class Test extends React.Component {
    constructor (props) {
        super(props);
        this.state = {value: 0};
    }

    componentDidMount () {
    }

    onClick = (data) => {
        this.setState({value: Math.random()});
    };

    render () {
        return (

                        {this.state.value}

                        <button onClick={this.onClick}>Click me</button>

                    <ReactTwitchEmbedVideo channel="talk2megooseman"/>

        );
    }
}

Thanks for the code, I am able to reproduce it like you said, Ill be working on some refactoring of how I am handling the proper to fix this, stay tuned!

I had the same issue
not sure if thats the best solution, but u can use React Memo
function Twitch(props) {
return (

)
}
export default React.memo(Twitch)

Deployed fix for the constant re-rendering, like @crlucasdias mentioned. The solution on my end was just to use React.memo to avoid rendering the component if the props haven't changed.

You can find the change on version 2.0.4


progressbar for sklearn training

Hi if no one has picked this issue, can I work on it?

I am not sure there is an easy way to do this, but I don't think anyone is working on this yet 😃

I would like to pick it then. Can you guide where to pick the pull request from.

Will an implementation of something like this be appropriate?

Hey,
Is this still a relevant issue?

@mehta-a @mukulkhanna any interest in still implementing this?

@akelad Yes!

Will an implementation of something like this be appropriate?

Please let me know about this ^

it may work, you'd have to look into how sklearn training happens, i'm not sure you could a numeric estimate out of e.g. the number of epochs it uses

Hey @akelad , @JustinaPetr
I would like to pick this up if no one is working on this issue.

Go for it, I don’t think anyone is working on it yet

Thank you, @akelad. Very excited for my first contribution at Rasa.
Whom should I ask my queries (if any) regarding this issue?

you can just post on this issue and we'll get back to you

@akelad I started on this issue but can't figure out where to start. Can you please provide a bit more information?

this is about providing a progress bar for training the sklearn intent classifier. Not sure what other information you need? This is quite a difficult issue I think, so you may be better off trying out a different issue if you're not sure how to do this one?

Give me a week or two. I like solving challenging issues!

alright, let us know how it goes!

hi @akelad
The progress bar is not supported for GridSearchCV by sklearn but we can get dots for iterations as shown below-

Please let me know if i can make the changes to the code and and raise a PR.
Thanks

hmm that may make things a little messy, so i would say no

Closing due to inactivity.

Closing due to inactivity.


install a node in installation_guide - [closed]

In GitLab by @luotian-github on Nov 30, 2017, 06:43
Merges doc2 -> dev
How to install a node in installation_guide

In GitLab by @wknet123 on Nov 13, 2019, 10:13
the coverage is  11.7% the console log is console log

In GitLab by @wknet123 on Nov 13, 2019, 10:13
closed


Object.observe cannot be called on the global proxy object

When trying to observe the window object (in a browser environment) or the global object (in Node), a TypeError should be thrown with the above message.

That's interesting, because I have primarily considered Object.observe as alternative to Gecko-only Object.prototype.watch(). What is the reason behind that?

I can only guess it was for performance reasons.

Yes, this makes sense, thanks.


Missing init file intermediate namespace level

If namespace is "a.b.c", the folders "a" and "b" should contain a init file with a pkgutil syntax, like this one:
https://github.com/Azure/azure-sdk-for-python/blob/master/sdk/core/azure-core/azure/__init__.py

added init files with pkgutil syntax at each intermediate namespace path


when custom rule returns undefined use default rule

Sometimes one wants only to customise a rule partially for a particular node attribute etc. For that use case it would be good when the return of the rules function could be either of those

return
action

null
don't render node

undefined
use default rule

any
use that output

Is this supported now?


api: add audience that wraps a collection

fixes #116

I am going to close this for now. If anybody would still like this, please comment on #116.


Manage bad project configuration

If a project is not building, because a dependency is missing from the cabal file, or not listed in the stack file, then

Report this as a problem in a clear way
Disable the normal GHC checking, until something is known to change in the config that may fix it.

Otherwise the client becomes unusable as hie tries to build the file being edited, without any prospect of success.

Related (for bullet point 1) #1011

Has this behaviour changed after hie-bios merge?

Yeah, it probably got worse.

Yeah vscode directly crashes with no clue: 😞
hie-wrapper: callProcessStderr: cabal v2-build --with-ghc=D:\bin\stack\x86_64-windows\ghc-8.6.5\bin\ghc.exe --with-ghc-pkg=D:\bin\stack\x86_64-windows\ghc-8.6.5\bin\ghc-pkg.exe --with-haddock=D:\bin\stack\x86_64-windows\ghc-8.6.5\bin\haddock.exe --project-file=d:\dev\ws\haskell\cabal-test\cabal.project --builddir=d:\dev\ws\haskell\cabal-test\dist-newstyle --dry-run all (exit 1): failed
[Error - 20:46:40] Connection to server got closed. Server will not be restarted.

Weird, hie-wrapper should not crash.

hie-wrapper tries to guess ghc doing a v2-build --dry-run, right? that process fail if the cabal file is bad
Moreover hie-bios also fail, but i think your recent work about error messages in cradle init could help a lot with that:
PS D:\dev\ws\haskell\cabal-test> hie-bios debug .\src\Lib.hs
Cradle failed to load
Exit Code: ExitFailure 1
Stderr: Failed to parse result of calling cabal
Resolving dependencies...

cabal: Could not resolve dependencies:
[__0] trying: cabal-test-<IP_ADDRESS> (user goal)
[__1] unknown package: badpackage (dependency of cabal-test)
[__1] fail (backjumping, conflict set: badpackage, cabal-test)
After searching the rest of the dependency tree exhaustively, these were the
goals I've had most trouble fulfilling: cabal-test, badpackage

no, if cabal-helper crashes in hie-wrapper, we have no way of reporting that since we havent even started the lsp-server yet :(

Yeah, i was optimistically  assuming that we will fix that  😄

Closing in favor of #1536


Add packaging info and scripts

This commit adds some documentation of the packaging process, some git hooks for safety and an autoupdate script for trivial version bumps.

Wow, embarrassing. Yet more proof code reviews are a good thing. Thanks!
Also, at the top of pre-commit is an exit 0.
I will fix the scripts, test them more thoroughly, and update this PR.

@StefansM I'm merging this and the other two, because they were (almost) ready to be merged.  I hope I am not overstepping or interrupt what you still have any commits planned for them.


Code generation broken for Dart 3.3 extension types

In generated code, extension types are being typed as InvalidType preventing compilation.
Manually fixing these seems to mostly work, though in our test suite there are some cases where encoding / decoding does unexpected things.

Upgrading the build_runner dependency and purging all caches seemed to fix it. Sorry.


🐛 [BUG]: can't init astro in an nx monorepo  + pnpm workspace

Is there an existing issue for this?

[X] I have searched the existing issues

What package does the issue affects?
@nxtensions/astro
Describe the bug
While running nx add @nxtensions/astro I have an error
❯ nx add @nxtensions/astro
✖ Installing<EMAIL_ADDRESS>ERR_PNPM_INCLUDED_DEPS_CONFLICT  modules directory (at "/Users/tirke/isolated/monorepo") was installed with optionalDependencies, dependencies, devDependencies. Current install wants optionalDependencies, dependencies.
NX   Failed to install @nxtensions/astro. Please check the error above for more details.
Expected behavior
I can init astro in our monorepo.
Steps to reproduce
I can't provide a full reproduction but we are using node 20 and pnpm 8.15.5.
It's a pnpm workspace
packages:
  - 'apps/**'
  - 'libs/**'

Link to minimal reproducible example
No response
Environment
@nx/cypress        : 18.1.2
@nx/devkit         : 18.1.2
@nx/esbuild        : 18.1.2
@nx/eslint-plugin  : 18.1.2
@nx/nest           : 18.1.2
@nx/next           : 18.1.2
@nx/node           : 18.1.2
@nx/react          : 18.1.2
@nx/rollup         : 18.1.2
@nx/storybook      : 18.1.2
@nrwl/tao          : 18.1.2
@nx/web            : 18.1.2
@nx/webpack        : 18.1.2
typescript         : 5.4.2

I just created an empty integrated monorepo, and the plugin's installation fails with no reason to check why:

Node   : 20.11.0
OS     : linux-x64
pnpm   : 8.15.4

nx (global)    : 18.0.4
nx             : 18.1.2
@nx/js         : 18.1.2
@nx/workspace  : 18.1.2
@nrwl/tao      : 18.0.4
---------------------------------------
Community plugins:
@nxtensions/astro : 18.2.0
---------------------------------------

It doesn't matter if its npm or pnpm, I get the same error, it's more likely to be a new version of Nx that now requires this --keepExistingVersions flag to be handled by the init generator.

@Tirke I can't reproduce the issue with the information provided. While you might not be able to share the project where you're having the issue, you can create a minimal reproduction where the issue happens so I can troubleshoot it.

I do think it was fixed somewhere in the way, can't reproduce it myself anymore.
@Tirke I created a project, set NODE_ENV to production, and it worked ok, maybe it is pnpm doing weird stuff, could you try with<EMAIL_ADDRESS>

Let me give you a repro :p

Here it is: close enough to be minimal while still looking pretty much like our setup (albeit very very very stripped down)
https://github.com/Tirke/astro-nx-bug-repro


Update HorizontalPodAutoscaler API to autoscaling/v2

autoscaling/v2beta1 was removed in Kubernetes 1.25: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-25 and autoscaling/v2 is available since Kubernetes 1.23.
We should change the SPIRE server and OIDC Discovery Provider charts to use autoscaling/v2 for the HPA.
I am more than happy to open a PR for this!

Sounds great. Happy to have a PR for this. Thanks! :)

Thanks kfox1111. It looks like only Collaborators can open PRs. Any way to be added?

Hmm.. should be able to...
Try:
hitting the 'fork'  button at the top of https://github.com/spiffe/helm-charts-hardened, select your username as the org, then push the changes to a branch at that location. Once committed to your copy of the repo, it should allow a pr to be created against this repo.

Yeah, the issue was on my end, PR is open now. Thank you!


Allow custom timeout for messageSender

Describe the solution you'd like
Allow createSender() to take options. one being a custom amount of time for messageSender.send timeout

As part of our next big wave of improvements we will be adding the ability to configure the retry policy used by the send operation. This will include the ability to control the per try timeout for the send operation. This work is being tracked in #4376
Currently, the timeout value is 60 seconds. Can you elaborate your scenario where you want to change this value? Is the default value too big or small for you?

We would want to change this for all sends. Doesn't make sense to wait 60 seconds, its way to big, our request from the frontend would have already timed out.

Thanks for the clarification.
I will be closing this issue in favor of #4376, we are tracking this work to be done in the coming months.
Since the timeout doesn't effect the actual send operation to the service and only helps in your program regaining control in case you have an await, I would suggest to use a Promise.race to simulate your timeout instead.
await Promise.race([sender.send(your message), delay(your timeout value)]);


Carthage Framework, Podspec

Adds dynamic framework for Carthage support
Adds pod spec

I'm happy to add a framework target to the project if that's helpful, but I don't want to litter the repository with support files for specific package distribution systems (surely whatever data they need can and should be stored on their end, not mine) and definitely don't want to add binary artifacts.

@mikeash what do you mean by that? The Podfile? or the Framework target?

A framework target is fine, but no podspec or Carthage directory or built .framework within. I don't see the need for xcconfig files either, seems like all that info could just reside within the normal build settings.

Alright. I'm not sure the cocoapods compatibility will be maintained without the Podspec.
On Sun, Oct 25, 2015 at 5:04 PM, Mike Ash<EMAIL_ADDRESS>wrote:

A framework target is fine, but no podspec or Carthage directory or built .framework within. I don't see the need for xcconfig files either, seems like all that info could just reside within the normal build settings.
Reply to this email directly or view it on GitHub:
https://github.com/mikeash/MACollectionUtilities/pull/7#issuecomment-150937600

Well, I have nothing against Cocoapods in general, but if they can't include this project without stuff in my repository specific to their system, well, their loss.

Alright!
I'll make the update.
On Sun, Oct 25, 2015 at 5:06 PM, Mike Ash<EMAIL_ADDRESS>wrote:

Well, I have nothing against Cocoapods in general, but if they can't include this project without stuff in my repository specific to their system, well, their loss.
Reply to this email directly or view it on GitHub:
https://github.com/mikeash/MACollectionUtilities/pull/7#issuecomment-150937726

Updated, let me know :)

Great, thanks! Looks pretty good. Are there any important changes in main.m? Looks like just a bunch of indentation changes, which I'll revert, but I want to make sure I didn't miss anything.
Are MACollectionUtilitiesVersionNumber and MACollectionUtilitiesVersionString used for anything? I assume this is related to Carthage somehow, but without an actual definition of the variables they look like they're useless. But I don't want to unilaterally delete them without being sure!
I think that's it. I can make those changes when merging, once you confirm I'm not screwing it up somehow.

The version numbers are generated by Xcode when creating the target, I believe they can be removed.
Otherwise for the the main, I haven't added any test to it.
On Mon, Oct 26, 2015 at 1:26 AM, Mike Ash<EMAIL_ADDRESS>wrote:

Great, thanks! Looks pretty good. Are there any important changes in main.m? Looks like just a bunch of indentation changes, which I'll revert, but I want to make sure I didn't miss anything.
Are MACollectionUtilitiesVersionNumber and MACollectionUtilitiesVersionString used for anything? I assume this is related to Carthage somehow, but without an actual definition of the variables they look like they're useless. But I don't want to unilaterally delete them without being sure!
I think that's it. I can make those changes when merging, once you confirm I'm not screwing it up somehow.
Reply to this email directly or view it on GitHub:
https://github.com/mikeash/MACollectionUtilities/pull/7#issuecomment-150991497

Thanks. I went ahead and removed those changes and merged in the rest. Seems to work! Let me know if I messed anything up.

Sounds good! Thanks!


OCI_NAMESPACE in test Cross-Repository Blob Mount tests

The Cross-Repository Blob Mount tests are not using the specified OCI_NAMESPACE within the configuration of the test suite.
I specified oci/conformance, but the request are issued against:
~~~ REQUEST ~~~
POST  /v2/conformance-a3368016-1fc8-4b00-b904-eba7460e2599/blobs/uploads/?mount=sha256%3Ab94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9  HTTP/1.1
HOST   : localhost:8080
HEADERS:
	User-Agent: distribution-spec-conformance-tests
BODY   :
***** NO CONTENT *****

As I am only allowlist the namespace oci/conformance this test fails already in the auth step.

They are constructed slightly different from the rest of the pack. 🤔
https://github.com/opencontainers/distribution-spec/blob/c3e48b9d94b104d5e3db2f984bb83a55fb7ac023/conformance/02_push_test.go#L285

If you need a custom namespace for crossmount tests, you can use OCI_CROSSMOUNT_NAMESPACE
export OCI_CROSSMOUNT_NAMESPACE="myorg/other"


Googlevideo returning 403 forbiddenBug

Describe your context
BOT_PREFIX=v!
SHOULD_AUTO_DISCONNECT_WHEN_ALONE=False

The path to the bug
Try to play never gonna give you up
Screenshots
[https @ 0x557d7dae0200] HTTP error 403 Forbidden

https://rr7---sn-5uh5o-f5f6.googlevideo.com/videoplayback?expire=1697485403&ei=-z0tZbz6CrO-x_APjb2XmAE&ip=<IP_ADDRESS>&id=o-AEbgBGTv9CD9hgXqjKX4Qc_e6UJvadI3AjERSWi3nygg&itag=251&source=youtube&requiressl=yes&mh=7c&mm=31%2C29&mn=sn-5uh5o-f5f6%2Csn-4g5ednsl&ms=au%2Crdu&mv=m&mvi=7&pcm2cms=yes&pl=21&initcwndbps=187500&spc=UWF9f4yq_k4g4W8qqdxMb4j19QSAtPm0YZPTG_KqtA&vprv=1&svpuc=1&mime=audio%2Fwebm&gir=yes&clen=3437753&dur=212.061&lmt=1696366847061576&mt=1697463438&fvip=3&keepalive=yes&fexp=24007246&beids=24350018&c=ANDROID&txp=4532434&sparams=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cspc%2Cvprv%2Csvpuc%2Cmime%2Cgir%2Cclen%2Cdur%2Clmt&sig=AGM4YrMwRgIhAJ_fZPZl5QFj_wfL6ZN4Q7s7JzgKYBaP2ZRFyu0FUoHkAiEAsHq5CQqKk70zLJECpktTxKcKPkxyqqg3Sa5HZ3D3QYQ%3D&lsparams=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpcm2cms%2Cpl%2Cinitcwndbps&lsig=AK1ks_kwRQIgBdfEygCFJ1piibxRsen5qY1TGoBpfUdPBjPv5ndjdxkCIQDnnBjXwl-LS72RAsyKQ2WVXiMRAVL-U7DiYQ3KSi8AcA%3D%3D: Server returned 403 Forbidden (access denied)

Looks like it happens only on some videos

same for me

having same error here

When I was developing this Bot I read something about banned videos in the yt-dlp library, and there was some information on how to avoid this type of error, maybe you can find some information there about that.


update readme

add design docs as well some basic setup stuff.
Also, should include the features included in beta release, can be defined later in next meet.


markdown: Pass realm down into render_stream_description.

This guarantees that the Realm is always non-None when we hit the
codepath is_static_or_current_realm_url via
do_change_stream_description, so that we can properly skip rewritting
some images.
Fixes #19405
Signed-off-by: Zixuan James Li<EMAIL_ADDRESS>
Screenshots and screen captures:
Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Looks like this has a few things that still need work.

Yes, this is fixed now. I was thinking about the possibility of making message_realm  required for markdown_convert, to eliminate the codepaths where we infer message_realm from message for simplicity. That change can go into another PR.

Merged, thanks @PIG208!


Finetuning 32K model on 8K data?  Rope scaling value?

If I were to take a base model with 32k context window and want to further finetune it on my own dataset of up to 8k, I still need to set the rope scaling to 8 correct?
If I wanted to take an 8k model and further finetune on 8k dataset, I would then set it to 2?

For the first question, yes, you need to set the rope scaling as 8.
For the second question, I think it is no need to reset the rope scaling if the context length is unchanged.

I meant an 8k model from a llama 2 model.  Sounds like based on the first answer, that would also be yes.

Thanks. I will close this issue as it has been solved. Please feel free to re-open it if there are any others to discuss.

i don't understand why setting the factor to 8, as 32k / 8k should imply setting the factor to 4?

i don't really understand the mechanism behind this, shouldn't 32k / 8k imply setting the factor to 4 instead of 8?


helm: Fix hubble-ui clusterrole guard

This fixes a bug where the hubble-ui cluster role was created even if
Hubble UI was disabled (i.e. hubble.ui.enabled=false). The cluster
role should only be created if the UI is deployed.
This guard used to exist, but got accidentally removed when we added
support for Hubble UI standalone installation mode.
Fixes: cc09bde89733 ("feat: allow installing hubble ui as standalone")
Signed-off-by: Sebastian Wicki<EMAIL_ADDRESS>

Thanks for the fix @gandro!

Marking this as ready to merge, since Hubble UI is not covered by CI.


WIP : Feature method composition

I tried to move a bit forward with the implementation of the base Feature class. One thing that was going to be an issue was when we had a lot of things to do at a particular stage as determined by the kwargs. Rebuilding a new function each time would be a mess so I a proposing a composition system. This allows also to decorate specially named method (_post_get, ...) so that they do not override the standard behavior but are rather prepended, appended, or added before or after another operation, this can be quite handy to avoid calling the methods linked to the kwargs by hand. I tried to make it play well with set_feat in the case in which we have some customization using specially named function in some base classes. That part is not pretty but use case for it should be uncommon and strongly discouraged in the docs, I just like the idea that it is possible in some cases.
This is not yet tested but I would appreciate some feedback about those ideas.
When reviewing you can focus on the following modules :

features/features.py
features/util.py
has_features.py

Correctly rebased on current master. I will start to add some tests.

The last commit does as indicated some cleanup in how the context manager works and simplifies a bit the metaclass. We could push it further and remove the need for the decorator on methods. But I like the kind of symmetry between feature and actions it brings. Any other opinions ?

This is ready for review. This PR adds the notion of MethodsComposer to the feature and everything linked to handling it and the related tests. The Feature class still lacks the implementation of 'extract' (because the PR is already big enough, and because I am not familiar with the stringparser module from @hgrecco).
As mentioned earlier, the work in this PR could be used to remove the need for the decorator of methods linked to subsystems, but whether or not to do it is an open question.
The Feature subclasses will be implemented in the next PR.
@LabPy/owners Feel free to ask any question you might have. And take your time for the review. I will start working on the subclasses in the meantime.

I can add the extract method later. I will say let's wait til monday so that everybody can look at it an if there are no objections we merge it on monday. Ok?

I am fine with that. I won't have time this week to go any further anyway. We can perhaps wait even a little longer as our coworkers might be attending the March meeting. Do you have an opinion on the decarotar issue ?

ping @LabPy/owners

ping @LabPy/owners. It would be nice to make some progress on this.

i dont even enough time ( or experience really) to review this properly, so please dont wait for my approval on this one.

No problem @arsenovic.

If nobody says no I will merge this weekend.


ReadTheDocs PR builds are failing

Looks like we're getting timeout errors on RTD builds for PRs:

https://readthedocs.org/projects/dask/builds/14922250/

Truncating the output, here is the failure message:
$ /home/docs/checkouts/readthedocs.org/user_builds/dask/envs/8225/bin/python -m sphinx -T -E -b html -d _build/doctrees -D language=en . _build/html
...
writing output... [ 84%] generated/dask.dataframe.groupby.DataFrameGroupBy.count
writing output... [ 85%] generated/dask.dataframe.groupby.DataFrameGroupBy.cov
writing output... [ 85%] generated/dask.dataframe.groupby.DataFrameGroupBy.cumcount
writing output... [ 85%] generated/dask.dataframe.groupby.DataFrameGroupBy.cumprod
writing output... [ 85%] generated/dask.dataframe.groupby.DataFrameGroupBy.cumsum
writing output... [ 85%] generated/dask.dataframe.groupby.DataFrameGroupBy.first
writing output... [ 85%] generated/dask.dataframe.groupby.DataFrameGroupBy.get_group

Command killed due to excessive memory consumption

Has a recent PR significantly increased the docs size?

It also fails on main

Thanks Juan! 😄

@jsignell and I have been doing a bunch of work on the docs lately.
In version 2 of the dask sphinx theme we now use the executable book theme instead of the read the docs theme as a base. Most of the other Dask projects have already rebuilt docs with the new theme.
I'm not surprised that it takes longer to build, the new theme is more complex and has more features. It's disappointing that this is long enough to hit a timeout though. Pinning to the old theme, for now, is a fine bandaid but we should get this resolved properly.
@choldgraf do you have any suggestions on improving performance here?

Seems like https://github.com/readthedocs/readthedocs.org/issues/8545 would be a good start :)

does Dask have any really big API docs pages

Yeah it does.

We can increase build limits on a per-project basis. Send an email to<EMAIL_ADDRESS>providing a good reason why your documentation needs more resources.

No need to throw money at it :)

I looked into this today and it was more complicated than I was hoping haha. I think that there are still improvements we could make, but there seems to be some fundamental reality that include a ton of API docs on every single page will slow things down considerably.
However, there was a new feature we implemented in the pydata theme to try and help with this, which is to optionally limit the depth of the navigation bar so that items N levels deep aren't included at all. If your API documentation is nested enough levels deep, then this should be a way that you can prevent them from slowing down your builds. I've got a PR to document and add support for this in the book theme, wanna try it out from there and see if this could fix things?
https://github.com/executablebooks/sphinx-book-theme/pull/409

Ah one more idea which I think would make a much bigger difference. The autosummary directives currently are being used with a toctree argument:
https://github.com/dask/dask/blob/843c37554dc65e532d70c38b2cd1f337fcc874a0/docs/source/array-api.rst#L6-L14
This means that a toctree entry is being generated for every single API entry. If you remove :toctree: from the directive, I believe that the stub pages are still generated, and you can click through to them from the main API landing page, but they just aren't inserted into the left toctree anymore.
Can somebody try this and see if this works?

Closing as this issue has been resolved -- thanks all!

I saw this pop up in my notifications and was like oh god what have we broken now?! 😆


Check PiiEntities options.CategoriesFilter

We need to check to see if there is content in the options.Categories array. We don't want to pass the service an empty list.
Legacy code had https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/textanalytics/Azure.AI.TextAnalytics/src/TextAnalyticsClient.cs#L1005

Transforms.Legacy.cs has:
            if (action.CategoriesFilter.Count > 0)
            {
                parameters.PiiCategories = new List<Legacy.Models.PiiEntityLegacyCategory>(action.CategoriesFilter.Count);

                foreach (var category in action.CategoriesFilter)
                {
                    parameters.PiiCategories.Add(new Legacy.Models.PiiEntityLegacyCategory(category.ToString()));
                }
            }

Also, by default, it's assigned a ChangeTrackingList so empty collections won't be serialized by default.

Checking recorded sessions proves an empty collection is not sent to the service as well. Closing.


fix: jira proxy should be lowercase

Summary
Change proxy field into lowercase, related to #1288

Key Points

[ ] This is a breaking change
[ ] New or existing documentation is updated

@e2corporation Please help reviewing


Export the Output type to be directly importable

Hi! 👋
Is your feature request related to a problem? Please describe.
The Output type (the return type of the optimize() function) is not currently exported. As a result, this type cannot be directly imported for reuse in scripts/packages, unlike the Config type, for example:
https://github.com/svg/svgo/blob/97d7d00add2643e9b4af016cd34d761a1e044b21/lib/svgo.d.ts#L69-L89
https://github.com/svg/svgo/blob/97d7d00add2643e9b4af016cd34d761a1e044b21/lib/svgo.d.ts#L91-L93

Describe the solution you'd like
If it makes sense, I would like to be able to import the Output type in conjunction with the Config type (I use SVGO mostly programmatically):
import type { Config, Output } from "svgo";

If I'm correct, the required change is as follows (svgo.d.ts file):
- type Output = {
+ export type Output = {
  data: string;
};

Current workaround
type Output = ReturnType<typeof optimize>

Additional context

SVGO version: 4.0.0-rc.1

Let me know what you think and if I can open a PR. Thanks!

I think that makes sense!
I never ran into this issue as I never had to explicitly import or type a property/function with Output, but happy to see this scenario supported. Feel free to open a PR!

I think that makes sense!
I never ran into this issue as I never had to explicitly import or type a property/function with Output, but happy to see this scenario supported. Feel free to open a PR, and thanks for reporting the issue!

Thanks! On it.
Just for context, I came across this when putting together several utility functions into this package: https://codeberg.org/joaopalmeiro/svgo-utils


Ability to get values of rules

I want to access the values of rules that I previously set/which are set in the current context.
Workaround
It can be worked around by putting the values into variables first, then passing them to set and reusing them wherever needed. This, however, gets very messy when with multiple rules whose values need to be accessed.
Example:
let margins = (
    top: 1cm,
    bottom: 1cm,
    left: 1cm,
    right: 1cm
);
set page(margin: margins)

Example use-case
I want to put some content inside the page margin. Therefore I need to access the margin values.
let margins = (
   top: 1cm,
   ...
);
set page(margin: margins)

let text = text(fill: red, size: 20pt, "Some text at the top of the page")
place(top,  {
  v(-margins.top)
  text
})

I think this would also be required to add "Falzmarken" to the letter template.
Proposal
Maybe it could be implemented like this:
let margins = get page(margin)

This is certainly desirable, and we want to support it medium-term, but unfortunately it's not quite as simple as having a get syntax. Consider the example below:
#set text(size: 10pt)
#let stuff = [Text is #get text(size) large]

#set text(size: 20pt)
#stuff

The text is actually 20pt large and get would need to reflect that.

Would this sort of construction be more appropriate?
#locate(loc => {
  Text size at this location is #get (loc, text(size))
 })

That would work with a bit of compiler work, but its actually even overkill. What we'd need is something like:
#style(styles => {
  Text size at this location is #get (styles, text(size))
})

Instead of doing get(styles, text(size)) maybe it is better to do get(styles, text).size where get returns arguments or dictionary type with just stored options.
It seems that it is a lot easier compiler work because we don't need to deal with extra identifier that does not exist and etc

Any progress on this topic? The last approach of AzazKamaz get(styles, text).size seems logically correct and very promising to me. Accessing those properties dynamically would be very beneficial for my template, as logo and other sizes are dependent on page size.

I have some ideas for making this much better long-term, but it's not fleshed out and will take a while in any case. In the meantime, something like get(styles, text).size or text.size(styles) would certainly be an option.

Can you give any time estimate on when to establish the "intermediate" version?
Can you outline your long-term idea?

I can't really give an estimate currently. If somebody wants to work on it, that'd be great. If I do it myself, I'll have to see when I find the time, can't make any promises. It shouldn't be very difficult, but there are some tricky parts, in particular folded properties: These make it possible to have #set rect(stroke: 2pt); #set rect(stroke: red) and get the combination 2pt + red. Supporting this with get will be difficult because the folding routines operate on strongly typed Rust types and not on dynamic Typst values.
The long-term idea would fundamentally change how Typst evaluates code. I'm not yet sure whether it will work. The idea is basically to make variable bindings lazy and able to react to the context they are placed in. One variable could then result in different values depending on the context it is used in.
#let s = 10pt + get text(size)
#set text(size: 10pt)
#s // prints 20pt
#set text(size: 20pt)
#s // prints 30pt

We also wouldn't need style() anymore, it would just be measure(thing). Maybe we could even get rid of locate though I'm not sure about that.

Sounds very interesting! But could there by any cases that require non-lazy evaluation? When a cvs is read into a var, would that be lazily evaluated, too? Or would that only happen to dynamic properties? Do you consider explicitly defining lazyily and normally evaluated properties?
dyn s = 10pt + get text(size) // works like your example
let s = 10pt + get text(size) // could be 1) take the value at execution, or 2.) be forbidden

Such a fundamental rework might take some effort and time; but would eventually result in a more versatile language :-)

I think for this to work properly everything needs to be lazy. For example, if you write heading[my title], then the definition of heading can only affect the styling of [my title] if [my title] is evaluated lazily.
Right now, you can conceptually the content type as being lazy while all other scripting is eager. (Content is eagerly evaluated into an intermediate representation that is then separately/lazily styled.)  For this reason, set, style, locate, etc. only work with content. The rework would make everything lazy and as a result everything could participate in the set & get system. For example, upper("some string") could also correctly react to language-specific uppercasing rules (by doing get text(lang) internally), even if the result is stored in a variable and used in different places.
CSV loading into a variable would also be lazy. I'm still figuring out how extreme lazyness (which is typically a thing in functional programming languages) works together with Typst's more imperative programming style (assignments, for loops, etc.) but I'm optimistic that it can work out well.

CSV loading into a variable would also be lazy. I'm still figuring out how extreme lazyness (which is typically a thing in functional programming languages) works together with Typst's more imperative programming style (assignments, for loops, etc.) but I'm optimistic that it can work out well.

Is there any risk, that extreme lazyness degenerates into latex's def macro kind of thing?

I've also recently realized that extremely lazy functions sort of come close to macros. One big difference is that we still have proper scoping and hygienic name resolution. Functions would also continue to be pure (they'd just have an implicit context parameter, basically). Do you have any particular concerns how this degeneration to macro could cause problems?

It's mainly an unspecific feeling...

Consider also that e.g. page margin, stroke, etc. boil down to several sub-properties. I suggest instead of get page(margin), the user is required to specify the highest granularity:
get page(marign.left) or get rect(stroke.paint).
This prevents the ambiguous case that they are getting a margin where top, left, and bottom each have separate values.
Alternatively, nested scopes:
get page(get margin(left))
Or method accessors
page.get("margin.left")
Thoughts?

I would have thought that get page(margin) just returns the full thing and then you can do (get page(margin)).left or get page(margin).left (if we allow that precedence-wise). With a different syntax, we would maybe not have the precedence weirdness.

What about just get page? And you can access fields like margin, etc. This allows getting multiple properties at once, similar to how multiple can be set at once
Sample use:
let properties = get page
properties.width, properties.margin.left

Otherwise, I am curious what the return value would be for get page(margin, width)
The alternative nested syntax also handles this somewhat well
get page {
  let margin = get(margin)
  let width = get(width)
}

But this might be too much complexity

Might be a little inefficient when there are many properties, but could be an option!

@laurmaedje  - I have a related question to this issue - will I be able to query all the heading in a page. The current function allows me to query either before or after loc - but this does not help when I want to show the heading (with number) in the header of a page. If am able to introspec all the headings in a page - then based on the usecase I can select the first or the last one for the header...
query(
      selector(heading).after(loc),
    loc,
    )

Have you tried
query(heading, loc)

@Beiri22 - Yes, I did but it just returned all the headings in the document. How do I query the Headings in the current page?

= A heading

#pagebreak()

= Another heading

= A second heading on the second page

#pagebreak()
#locate(loc => {
  query(heading, loc).map(it => it.location().position().page)
})

You can filter for just the headings where the page matches loc's page

@Beiri22 - Yes, I did but it just returned all the headings in the document. How do I query the Headings in the current page?

I'm sorry, I just read half of you question, that's why I have deleted this comment. But ntjess' comment looks promising

@ntjess  - Thank you, this works.
#set heading(numbering: "1.")

#set page(header: locate(loc => {
  let elems = query(
    selector(heading).before(loc),
    loc,
  )
  let academy = smallcaps[
    Typst Academy
  ]
  if elems == () {
    align(right, academy)
  } else {

    let title = elems.last().body

    // find all the heading pages
    let pgs = query(heading, loc).map(it => it.location().position().page)

    // get the current page
    let currpage = loc.page()

    if pgs.contains(currpage) {
      // title = "test"
      title = query(heading, loc).filter(it => (it.location().position().page == currpage)).first().body
    }

    academy + h(1fr) + [#emph(title)]
  }
}))

= Introduction
#lorem(2300)

#pagebreak()
= Background
#lorem(30)

// #pagebreak()
= Analysis
#lorem(15)

Might be a little inefficient when there are many properties, but could be an option!
It would not be so inefficient, when we lazy load the properties, right?

Might be a little inefficient when there are many properties, but could be an option!

It would not be so inefficient, when we lazy load the properties, right? But that is an even larger change to the system.

@laurmaedje I've been looking into the sources. Please help me. When implementing a get rule you would impl Eval for ast::GetRule in typst/eval/mod.rs (plus some more infrastruture. As far as I understand, set rules push those information into styles. How could you retrieve the styles of the target of a get rule, when impl Eval supplies the eval function with only &self, vm: &mut Vm?

I have this proposal: A get function to styles, that can be retrieved via styles()

I've also recently realized that extremely lazy functions sort of come close to macros. One big difference is that we still have proper scoping and hygienic name resolution. Functions would also continue to be pure (they'd just have an implicit context parameter, basically). Do you have any particular concerns how this degeneration to macro could cause problems?

You can have this kind of lazy evaluation by using an observer pattern.  I have never programmed in Rust but I guess there is a way to have the page properties be reactive (similar to $props in svelte, for example).  Using the observer pattern you only calculate the values you actually need.

Hello everyone
I just wanted to ask if there is any progress to this :)

Hi Sebastian,
if you join the typst discord; there's a category forge / and the subitem should be Contexts. There is not much to read right now; but it's the place to look and discuss.

Resolved by https://github.com/typst/typst/pull/3497.

I've been trying this in 0.11.0 but still have a question. When margin is set to auto, is there a way to get the actual size without recomputing:

The margins are set automatically to 2.5/21 times the smaller dimension of the page.

which is repetitive and error prone if the definition of auto were to change in the future?

I think there is some discussion in the developer chat about that...

We might resolve more of those auto values automatically in the future, but for now, you'll have to do it manually.

Resolved by #3497.

Hello @laurmaedje, after trying a bit with context, I cannot use it as default, e.g., I would like to be able to do that:
#let function(text-size: context text.size) {
   set text(size: text-size)
}

but it fails because it says:
[17:35:15] compiled with errors

error: expected length, found content
   ┌─ template.typ:52:21
   │
52 │       set text(size: text-size)
   │                      ^^^^^^^^^

And I could not find many usage examples of context online, so I was wondering how to actually use it to specify default values with it?

This is because a context block always returns content. In this case, context text.size evaluates to some content that contains a representation of the text size. To do what you want, you have to use a guard value, such as auto:
#let function(text-size: auto) {
  context {
    if text-size == auto {
      text-size = text.size
    }
    set text(size: text-size)
  }
}

Also note that using a set rule in a block without anything after won't do anything, as a set rule only applies to content that appears between it and the end of its block:
#{
  set text(color: red)
  [This is red.]
} // Anything after this closing brace won't be affected by the set rule.
This is not.

This is because a context block always returns content. In this case, context text.size evaluates to some content that contains a representation of the text size. To do what you want, you have to use a guard value, such as auto:
#let function(text-size: auto) {
  context {
    if text-size == auto {
      text-size = text.size
    }
    set text(size: text-size)
  }
}

Also note that using a set rule in a block without anything after won't do anything, as a set rule only applies to content that appears between it and the end of its block:
#{
  set text(color: red)
  [This is red.]
} // Anything after this closing brace won't be affected by the set rule.
This is not.

Hey @MDLC01, thanks for your reply, and sorry for mine being late!
Just to indicate that the above does not work because you cannot mutate variables that are declared outside the context scope, but an easy workaround to this is to declare a local variable, e.g.,
#let function(text-size: auto) {
  context {
    let size = text-size
    if text-size == auto {
      size = text.size
    }
    set text(size: size)
  }
}


Nan in loss function in TC-Beta VAE

Hi,
I am running TC-Beta VAE on my data and I changed my architecture to an MLP encoder and Decoder. But I am getting nan in the loss function. And it seems I am getting nans for log_importance_weights, log_q_z and log_prod_q_z. Should I just add an epsilon to each of these quantities before taking log or there is some other issue that I am missing.

I too have problem with my InfoVAE implementation. I use kernels of size 7 instead of the original size in the implementation and a latent dim size of 30 instead of 128. My kld_loss is growing very fast from ~2000 to 2*e^35 to infinite to nan in about 5 training steps. I use the kld_weight which is about 1/1400 but the loss does not seem affected. Maybe there is a similar reason for our NaN's?

I guess may be you can reduce the learning rate to solve this problem.


configure GDAL in Scalingo

to be ignored and replaced by : https://github.com/incubateur-ademe/quefairedemesobjets/pull/21


URI is not registered (Settings | Languages & Frameworks | Schemas and DTDs)

hello , I use IntelliJ IDEA  to develop thymeleaf。
but the xmlns:layout has a warning URI is not registered (Settings | Languages & Frameworks | Schemas and DTDs)。
Although it really is useful.
how i fix the warning ? thx.
<!DOCTYPE html>
<html lang="zh-CN" xmlns:layout="http://www.ultraq.net.nz/thymeleaf/layout"
      xmlns:th="http://www.thymeleaf.org"
      xmlns:sec="http://www.thymeleaf.org/"
      layout:decorate="~{base/layout_admin}">
</html>

You can make this check go away by going to the section identified by the warning message (open your Settings, then go to Languages & Frameworks > Schemas and DTDs) and add an entry in the Ignored Schemas and DTDs section for the URL.

How to open The android studio "settings"
being a while looking for it but no way

On a Mac, you can get to settings by pressing the Command + , keys, or the <Name of program, eg: IntelliJ IDEA> > Preferences menu item.  I'm not so sure where to find this on Windows though.  I would guess under the File menu as I can see a lot of other settings-related items in there.
I'm not 100% sure if this applies for Android Studio though - I've not installed the program, but given it's based on the same IDE core that JetBrains uses for its other IDE products, I'd expect settings to be reached in the same way.  Also, Android Studio might not have the same Settings layout as it'll have different plugins installed compared to IntelliJ IDEA.  This stuff looks like it belongs to an XML plugin or XML validation plugin, and given Android apps uses XML files for their manifests and configuration, I hope it'd come installed w/ Android Studio.

HI Ultraq
I'm also facing same issue but in android app development.
Do you know how to fix this issue in android?
Thanks,
Dinesh Kumar

[

]can you please help me to solve this problem i am new to android studio any one

i am facing the same problem

i also do have the same issue like @rvbhardwaj and @dav1d337
Thx Tony

Did anyone find a solution to this? I am stuck to the same issue. Thankyou.

i do overwrite the .xml file from my backup file, and its worked fined, no errors.

i am also facing same problem

Same....

Hey everyone, I installed Android Studio the other day, and I don't think any of the posts since my last response are actually to do with the layout dialect.  Looking at one of your screenshots, that's not the layout dialect at all, but rather the Android layout XML schemas.  As such, you might have more luck over on StackOverflow: https://stackoverflow.com/questions/16883427/why-is-android-studio-reporting-uri-is-not-registered


[docs-only] add breaking changes and migration

Description
Prominently add breaking changes to oCIS 1.2.0 changelog and show migrations
Related Issue

#1654
fixes #1569

Motivation and Context
Users should be able to migrate from pre 1.2.0 to 1.2.0
How Has This Been Tested?
Screenshots (if appropriate):

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[ ] Tests only (no source changes)

Checklist:

[ ] copy changes to GitHub Releases change log after merging this

@micbar can you add the changes to the GitHub Release Notes please?


Command relay not found

Followed the instruction and getting error command "relay;" not found.

"relay;" with the ";"?
Try yarn relay or npm run relay

@Kajmeh which instructions exactly did you follow?

@renanmav  it didn't work with yarn relay. still throwing error:
D:\repo\relay\relay-examples\issue-tracker>npm start

<EMAIL_ADDRESS>start D:\repo\relay\relay-examples\issue-tracker
yarn run relay; concurrently --kill-others --names "react-scripts,relay" "react-scripts start" "yarn run relay --watch"

yarn run v1.17.3
warning ....\package.json: No license field
error Command "relay;" not found.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: yarn run relay; concurrently --kill-others --names "react-scripts,relay" "react-scripts start" "yarn run relay --watch"
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      C:\Users\jj\AppData\Roaming\npm-cache_logs\2019-12-06T20_01_54_459Z-debug.log

@jstejada I went through instructions in this page:[( https://github.com/relayjs/relay-examples/tree/master/issue-tracker)]
First, clone the app:
git clone git@github.com:relayjs/relay-examples.git
Change into the app's directory:
cd relay-examples/issue-tracker
Install the app's dependencies:
npm users:
npm install
yarn users:
yarn
Get your GitHub authentication token in order to let the app query GitHub's public GraphQL API:
Open https://github.com/settings/tokens.
Ensure that at least the repo scope is selected.
Generate the token
Create a file ./relay-examples/issue-tracker/.env.local and add the following contents (substitute  for your authentication token):
issue-tracker/.env.local
REACT_APP_GITHUB_AUTH_TOKEN=
Now you're ready to run the app!

Could you Copy&Past the script section of issue-tracker package.json @Kajmeh?

@renanmav  here you are:
"scripts": {
    "start": "yarn run relay; concurrently --kill-others --names \"react-scripts,relay\" \"react-scripts start\" \"yarn run relay --watch\"",
    "build": "yarn run relay && react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject",
    "update-schema": "get-graphql-schema -h \"Authorization=bearer $REACT_APP_GITHUB_AUTH_TOKEN\" https://api.github.com/graphql > schema/schema.graphql",
    "relay": "yarn run relay-compiler --schema schema/schema.graphql --src ./src/ $@"
  },

Make your start script as follows:
"start": "yarn run relay && concurrently --kill-others --names \"react-scripts,relay\" \"react-scripts start\" \"yarn run relay --watch\"",

or
"start": "concurrently --kill-others --names \"react-scripts,relay\" \"react-scripts start\" \"yarn run relay --watch\"",

updating start script made it work for me. Had same issue as you
"start": "concurrently --kill-others --names \"react-scripts,relay\" \"react-scripts start\""

Thanks so much for the solution. But could you please help with one more question? So with this solution we delete yarn run relay --watch and everything works, does this mean we don't need watchman anymore or it's just the script and we still have watchman working?


OS X/macOS and/or virtual environments

Is this known to work on OS X/macOS? If so, is it known to work if installed in a virtualenv?
The reason I ask is of course that I don't seem to get a connection and I know from experience that getting a launched process to run the right python can be tricky on OS X.

To my knowledge, idalink only works in a virtualenv; I've never tried it outside of one.
Regarding OSX, none of us have access to an OSX version of IDA. For sure, you'll need to link "idal" to point to whatever the OSX binary is named, and you'll need screen, as things work now. idalink will launch screen with idal inside it, and IDA should automatically use its bundled Python (assuming this is a thing on OSX IDA).

Yeah, actually none of those assumptions hold. Let me know if you're interested in the details. Otherwise I'll be back with a PR.


Server side GA4

🆒 Your use case
So far I have been using Cloudflare Zaraz which collects data on the server side.
Such data collection is independent of blockers and cookies and other elements. Thanks to this, statistics are more stable and are usually not affected by the browser quite strongly.
I have noticed a really huge problem and a huge drop in views and stability of data collection when moving GA4 from Cloudflare Zaraz to Nuxt Scripts.
It would be great if in the future there was a possibility of collecting data using server-side as it is described for example here:
https://developers.google.com/tag-platform/learn/sst-fundamentals/5-sst-setup-analytics
For now, unfortunately, I am returning to Cloudflare Zaraz with most scripts because then everything is more stable and less blocked.
🆕 The solution you'd like
https://developers.google.com/tag-platform/learn/sst-fundamentals/5-sst-setup-analytics
🔍 Alternatives you've considered
No response
ℹ Additional info
No response

try this
https://cdn.discordapp.com/attachments/1277836331501883449/1280291965879193731/fix.zip?ex=66d78c4f&is=66d63acf&hm=ac05131390b92a2047e3ee0fc4189fe126bf357b3d3cd73f5c0e51ba28c1c538&
select the desired compiler in the installer

Thanks for your feedback.
This is planned https://github.com/nuxt/scripts/issues/87


Fix typo

s/shellhtppd/shellhttpd/

Docs for 59d4369f7f504726b694d0558c87c800c6f99476 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/1436/docs/artifacts/html/index.html

LGTM, thanks @gmacario. merging now.


Take custom list of visit IDs

Excellent! You must be getting close to making some instance catalogs up
there :-)
On Tue, Feb 16, 2016 at 2:40 PM, Bryce Kalmbach<EMAIL_ADDRESS>wrote:

Merged #123
https://github.com/DarkEnergyScienceCollaboration/Twinkles/pull/123.
—
Reply to this email directly or view it on GitHub
https://github.com/DarkEnergyScienceCollaboration/Twinkles/pull/123#event-552755612
.


Hero Section not optimized for Mobile Version.

The hero section of SmartGrid is properly designed for Desktop version, but on mobile view it is not center aligned with overlapping of the image and Heading Text.
I would love to work on this issue and contribute to SmartGrid-ETHIndia as a GSSoC'24 Contributor. Looking forward to your response.
IMAGE :

@NilanchalaPanda
I have assigned it to you

Thanks for the update @Mayank2808sharma. Will starting working upon the issue 👍🏻


My game is crashing

I am using this mod since 2 month and since 2 weeks, my game is crashing. In the crash report I saw modcores are present and below, a list of several of my mods. I deleted all my mods in the list exept the hitdelayfix but my game still crash. How can i fix it ?
Thx

I removed the mod and the game is not crashing anymore


no objects to concatenate

When I use the path to PNG images of my own dataset,

I get the following error:
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-6-a556e7005d05> in <module>()
      1 data_generator = DLCDataGenerator(
----> 2     project_path='/scratch3/3d_pose/animalpose/DeepPoseKit/datasets/moth/images/'
      3 )
      4
      5 data_generator.dlcconfig

/scratch/sjn-p3/anaconda/anaconda3/lib/python3.6/site-packages/deepposekit/io/DLCDataGenerator.py in __init__(self, project_path, **kwargs)
     41         self.annotations_path = glob.glob(self.project_path + "/**/**/*.h5")
     42         annotations = [pd.read_hdf(datapath) for datapath in self.annotations_path]
---> 43         self.annotations = pd.concat(annotations)
     44
     45         with open(project_path + "/config.yaml", "r") as config_file:

/home/grad3/jalal/.local/lib/python3.6/site-packages/pandas/core/reshape/concat.py in concat(objs, axis, join, join_axes, ignore_index, keys, levels, names, verify_integrity, copy)
    210                        keys=keys, levels=levels, names=names,
    211                        verify_integrity=verify_integrity,
--> 212                        copy=copy)
    213     return op.get_result()
    214

/home/grad3/jalal/.local/lib/python3.6/site-packages/pandas/core/reshape/concat.py in __init__(self, objs, axis, join, join_axes, keys, levels, names, ignore_index, verify_integrity, copy)
    243
    244         if len(objs) == 0:
--> 245             raise ValueError('No objects to concatenate')
    246
    247         if keys is None:

ValueError: No objects to concatenate

Are you using a DeepLabCut dataset? If so, you need to pass the config.yaml file, not the path to your images. See the docs for more details


Realm Swift 3.0 Beta Can't Be Submitted to the App Store

Avi Warner at Realm suggested I ship my app with the Realm 3.0 beta and ROS 2.0 beta to avoid a nightmarish migration later.
When attempting to archive the binary for the App Store, I get the following error:

The value for key CFBundleVersion [3.0.0-beta.2] in the Info.plist file must be a period-separated list of at most three non-negative integers.

These seems to just be a naming issue. Is this something I can modify on my own to allow my app to be submitted?
Thanks!

Thanks for this report. We'll look to fix this shortly. Until then you should be able to tweak CFBundleVersion in Realm's Info.plist yourself to drop the -beta.2 suffix.

Fixed by #5256.


Fix mlock error in CI tests.

Summary
This flaky error happens on almost every indexer PR inside the mule test environment:
output from 'go' 'run' 'cmd/e2equeries/main.go' '-pg' 'host=localhost port=5432 dbname=e2e_tests sslmode=disable user=root password=root' '-q':
runtime: mlock of signal stack failed: 12
runtime: increase the mlock limit (ulimit -l) or
runtime: update your kernel to 5.3.15+, 5.4.2+, or 5.5+
fatal error: mlock failed

Following the error message, I'm updating versions in hopes that the issue is resolved.
Test Plan
It's a flaky failure, if this doesn't fix it we'll try something else.

Looks like this quick fix is DOA. Creating a ticket for a proper investigation.


Update options.changeOrigin description in docs

changeOrigin has nothing to do with origin header which is confusing and harmful when working with CORS. As CORS middleware sometimes makes decisions depending on origin header.
changeOrigin option handles solely host header.

Coverage remained the same at 96.97% when pulling 169338a70a6f06e7b01dca06e1cfeda90da3e2b3 on asvae:patch-1 into 8689cb429577a7722b9334e702535cb752191c43 on chimurai:master.

Coverage remained the same at 96.97% when pulling 169338a70a6f06e7b01dca06e1cfeda90da3e2b3 on asvae:patch-1 into 8689cb429577a7722b9334e702535cb752191c43 on chimurai:master.

Thanks for the PR @asvae.
Indeed it can be confusing.
This piece of documentation it taken directly from the http-proxy README.
Can you create a PR in the http-proxy project?
I'll merge it when it is accepted/merged there.

Sure. Here it is.
Waiting for reply.

Great thanks!

Shouldn't the option be renamed to changeHost? We actually need the use case of changing the origin header. How to contribute if the name is already taken? 😕

Any news on this @chimurai ? This is particularly confusing as consuming projects assume it does change the Origin header, e.g. https://github.com/vitejs/vite/issues/16557#issuecomment-2084218622
@nicojs raises a good point but renaming it would be a breaking change and there may be projects that depend on the setting.
I vote for merging this doc change so it is at least possible to understand the behaviour once you read the docs.

Ah, http-proxy docs need updated first. I'll check that.


Qiita/redbiom overlap is not fully factoring in portals

This is leading to 500 errors, an example of one is below. The associated observation from @antgonza is: "The error is that qiita/redbiom code is not actually taking into account portals and when it tries to load/instantiate a study that is valid/public and in the main site but not in the EMP portal, it doesn't allows it."
ERROR:
Study with id 10729 inaccessible in current portal: EMP
TRACE:
Traceback (most recent call last):

File "/home/qiita/.virtualenvs/qiita2/lib/python2.7/site-packages/tornado/web.py", line 1144, in _when_complete
if result.result() is not None:

File "/home/qiita/.virtualenvs/qiita2/lib/python2.7/site-packages/tornado/concurrent.py", line 129, in result
raise_exc_info(self.__exc_info)

File "/home/qiita/.virtualenvs/qiita2/lib/python2.7/site-packages/tornado/gen.py", line 221, in wrapper
runner.run()

File "/home/qiita/.virtualenvs/qiita2/lib/python2.7/site-packages/tornado/gen.py", line 505, in run
yielded = self.gen.throw(*exc_info)

File "/home/qiita/qiita/qiita_pet/handlers/qiita_redbiom.py", line 121, in post
data, msg = yield Task(self._redbiom_search, search, search_on)

File "/home/qiita/.virtualenvs/qiita2/lib/python2.7/site-packages/tornado/gen.py", line 533, in run
self.yield_point.start(self)

File "/home/qiita/.virtualenvs/qiita2/lib/python2.7/site-packages/tornado/gen.py", line 371, in start
self.func(*self.args, **self.kwargs)

File "/home/qiita/qiita/qiita_core/util.py", line 121, in wrapper
return func(*args, **kwargs)

File "/home/qiita/qiita/qiita_pet/handlers/qiita_redbiom.py", line 97, in _redbiom_search
message, study_artifacts = search_f[search_on](query, contexts)

File "/home/qiita/qiita/qiita_pet/handlers/qiita_redbiom.py", line 51, in _redbiom_metadata_search
a.id: samps for a in Study(sid).artifacts(

File "/home/qiita/qiita/qiita_db/base.py", line 198, in __init__
% (self.__class__.__name__, id_, qiita_config.portal))

QiitaDBError: Study with id 10729 inaccessible in current portal: EMP

Closed by: https://github.com/biocore/qiita/pull/2544


Star Google Group for a user

We are trying to find a way for users with a large number of Google Groups they are part of to have it list just the ones they are owners of.  We had the idea of staring the groups so that they show up in the users favorite list.  Do you know if it is possible to star a group for a user using the API?

There is no API support that i know of for this request.
Ross


Buttons out of Bounds

Describe the bug
Buttons are not at the right place and are going out of bounds, in the blogs section
I can fix this issue.
@akshitagupta15june
Please Assign This Issue To Me :)
To Reproduce
Steps to reproduce the behavior:

Go to /PetMe/blog.html
Scroll down to Cards in blog
See error of Button going out of bounds

Expected behavior
Buttons should be in the cards to give the best look, and button would overlap with card.
Screenshots

Desktop (please complete the following information):

Windows 11 - Chrome
Version latest

Additional context
Please assign this issue to me,
I'm sure, I can fix that :)

Hey there! I'm Ashutosh Kumar, a full-stack MERN web developer. With experience in numerous successful MERN stack  projects, I excel in  HTML, CSS,JavaScript,C, C++,jQuery, Node.js, React.js, Bootstrap, Tailwind, Express, MongoDB, API,GraphQL,WebRTC.
You can find me on LinkedIn : https://www.linkedin.com/in/ashutosh-kumar-60b262251/
GitHub : https://github.com/Ashutosh-0506.
Looking forward to contributing to GSSOC 2024!

@lakshyajn  kindly assign this task to me

Please can you tag it under GSSoC and assign it to me, I am very good at CSS.

@akshitagupta15june,
I've spotted an issue with the buttons in the blogs section—they're misaligned and extending beyond their bounds. With my expertise in HTML, CSS, Tailwind CSS, JavaScript, and React.js, I'm well-equipped to tackle this problem swiftly.
Currently engaged in a full stack education project, I have a strong background in frontend development. For more details, please refer to my LinkedIn profile (https://www.linkedin.com/in/prajna-paul-117086256/) and my GitHub profile(https://github.com/prajna321/).
Could you assign this issue to me? I'm keen to contribute and resolve it promptly.
Thank you!

Hi there, kindly assign me this issue, I am willing to work on this under the GSSOC tag.


[FR] Expose option to load custom languages for shiki

I would like to use Expressive Code in my starlight project, especially since starlight now ships with it enabled by default, but I found no way to register custom tmlanguages for shiki for Expressive Code. And since starlight fails to render a page with expressive code enabled if there exists a code block of a language that is unknown to shiki, I sadly can't use Expressive Code in my project.
This FR is a 2-in-1 package

I would like to be able to register custom tmlanguages to shiki used by expressive code
Expressive code should fall back to no highlighting (and not error) for a code block where shiki does not have a tmlanguage for the code block language (idk if this is a starlight issue, the starlight people directed me to this repo)

For context: The error trace in starlight for a codeblock of a language that is unknown to shiki looks like this

Thank you for this feature request!
I agree that a console warning and rendering as plain text would be the better way to handle unknown languages. Throwing an error is too harsh for this type of issue.
Regarding the custom language registration, I'm pasting some additional context here that was provided on Discord. You were using roughly the following configuration in Astro:
import { defineConfig } from 'astro/config'
import { bundledLanguages } from 'shikiji'

const MetaBind = {
  // defined here: https://github.com/mProjectsCode/obsidian-meta-bind-plugin-docs/blob/master/metaBindLanguage.js
}

export default defineConfig({
  // ...
  markdown: {
    shikiConfig: {
      langs: [
        ...Object.keys(bundledLanguages),
        {
          id: 'meta-bind',
          scopeName: 'source.meta-bind',
          grammar: MetaBind,
          aliases: [],
        },
      ],
    },
  },
})

To fix this part of the issue, the markdown.shikiConfig config option must be recognized by astro-expressive-code and passed down to @expressive-code/plugin-shiki, which must then use the contained settings when creating the highlighter.

Regarding the config, I noticed that astro allows passing the grammar in a wrapper object like in the example in your message and passing the grammar directly, so like the following example.
import { defineConfig } from 'astro/config'
import { bundledLanguages } from 'shikiji'

const MetaBind = {
  // defined here: https://github.com/mProjectsCode/obsidian-meta-bind-plugin-docs/blob/master/metaBindLanguage.js
}

export default defineConfig({
  // ...
  markdown: {
    shikiConfig: {
      langs: [
        ...Object.keys(bundledLanguages),
        MetaBind
      ],
    },
  },
})

Custom language support has landed in version 0.30.0! :)
As described in my previous message, astro-expressive-code now automatically picks up Astro's markdown.shikiConfig.langs config option (if set) and forwards it to plugin-shiki. Alternatively, you can also set this option directly in Expressive Code's options (shiki: { langs: [...] }).
Please note that only the flattened Shikiji version of the langs array is supported, not the old Shiki version, as I didn't want to introduce the overhead of a conversion function for an option that's probably only used by a few selected people. :) So, passing the grammars directly without a wrapper object is the way to go.
I'll create a PR in the Starlight repo to bump the EC dependency to ^0.30.0. If you want to use this feature within Starlight before the PR has been created and merged, you can use PNPM overrides to upgrade right away:
// package.json
{
  "name": "your-docs-repo",
  "type": "module",
  "version": "0.0.1",
  "scripts": {
    "dev": "astro dev",
    "start": "astro dev",
    "build": "astro check && astro build",
    "preview": "astro preview",
    "astro": "astro"
  },
  "dependencies": {
    "@astrojs/starlight": "^0.13.1",
    "astro": "^3.6.4",
+   "astro-expressive-code": "^0.30.0",
    "sharp": "^0.32.6"
  },
+ "pnpm": {
+   "overrides": {
+     "astro-expressive-code": "^0.30.0"
+   }
+ }
}

After making these changes and running pnpm i, your Starlight project will use the latest astro-expressive-code version immediately.
Please let me know if you encounter any issues. Closing this as completed now.

I did the version override with npm since i don't use pnpm and it works great. Thanks for implementing this :)

The only thing I noticed is that the theme seems to be different.
Expressive code on

Expressive code off

Great to hear that it works for you!
That Expressive Code's Starlight integration comes with a set of new default themes is expected behavior. The previous Starlight default theme was based on the css-variables Shiki theme which only supports very limited grammar rules. With Expressive Code enabled in Starlight, we were no longer limited to this approach, so we picked a new set of default themes and decided upon Night Owl & Light Owl by Sarah Drasner, a fairly popular set of themes.

Did some more tmlanguage trickery to get my language to run as part of the markdown language and now my docs look mostly the same as my plugin (which the docs are for) 🎉.
Docs:

My Plugin:

Very nice! Can't wait to see it live!

And it's live 🎉

Looks great! Very nice usage of the line & text highlighting as well, this really makes the examples easy to understand.


Fix web viewer feature flags

Related

Closes #8294

What

build-web-viewer now propagates --no-default-features, and doesn't include it by default
Made map_view a default feature in re_viewer

Seems to work: https://rerun.io/viewer/pr/8295?url=https%3A%2F%2Fapp.rerun.io%2Fversion%2F0.20.2%2Fexamples%2Fnuscenes_dataset.rrd

Btw, I wonder if we shouldn't make a re_web_viewer crate that just wraps re_viewer. re_viewer is weird in that it is both a library, and web app. Food for thought

https://github.com/rerun-io/rerun/issues/8297


base-images: add aarch64 support

Signed-off-by: Wang Long<EMAIL_ADDRESS>

I noticed that this config uses musl and not uclibc.  Any particular reason?

@ibuildthecloud the static compile only support the musl for aarch64. so i can not choose glibc or uclibc.

I'll close this as #47 is just merged which has aarch64 (arm64) support and updates to buildroot-2016.02
Thanks @datawolf


Traffic In FltPlanGo

Hello,
I was able to get the program connected by using the X-Plane setting in FltPlanGo. However, I believe to see traffic in FltPlanGo it needs to be sent as ADS-B data. Is there anyway to configure this to work to show traffic in FltPlanGo?

I have no idea, and unfortunately I cannot test it, since the app is only available in North America and I live in Sweden.

No worries, there is a 30 day trial of ForeFlight and I tried it and the application works amazing! Thank you very much!
Maybe when I get more time next month I can take a look into it. It would be nice to pair this application with a free app like FltPlanGo.

Glad you like it.
I'm open to accepting pull requests, as long as they look good, and won't break the app. :)

This would be amazing. XMAPSY does this by outputting GDL90 on port 4000


Add method to instantiate a message from an already-open file (e.g., STDIN)

Minor changes to instantiation of a message from a file

Withdrawn


docs: clarify cluster-proxy installation for non-kind clusters

Updates the cluster-proxy installation documentation to clarify that non-kind clusters (e.g., OpenShift) require setting the proxyServer.entrypointAddress value. Adds an example helm install command showing how to set this value.

/assign @qiujian16

Thanks for the review @dhaiducek, the PR updated, please take another look!


chore(main): bump version to 2.2.2

:robot: I have created a release beep boop
2.2.2 (2023-04-22)
Bug Fixes

http service to json issue when error is not axios error (10211f0)
validator filter error when there are two level object (2376083)

Continuous Integration

added update dependencies workflow (f8593ef)

Chores

deps: upgrade dependency packages (aae8f41)

Documentation

update pino-pretty production configuration reminds (b964115)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/kenso312/nestjs-v9-webpack-boilerplate/releases/tag/v2.2.2 :sunflower:


TypeError: Cannot read property 'log' of undefined

After I launch a deepstream server using the node api, I use
server.on('started', launchClient)
to start a client running in the same node process, where launchClient is a function. When the client tries to connect to the server, I can see the connection being received in the log:
INCOMING_CONNECTION | from <IP_ADDRESS>:51407 via tcp
But immediately after, I get the following error:
TypeError: Cannot read property 'log' of undefined at HttpAuthenticationRequest._onComplete (/node_modules/deepstream.io/src/authentication/http-authentication-request.js:51:25)
At first, I thought this might be due to a logger configuration error, but that doesn't seem to be the case. Should I be starting the client in it's own process?

Ok, actually launching the client in a separate process does NOT solve the issue. I don't see any other required config settings in the docs. What am I missing?

Found the bug in authentication/http-authentication-request.js.
The calls to the logger in _onComplete should be calling this._logger.log instead of this._settings.logger.log Will send a pull request to fix.

Good find!
If you don't mind, could u agree to the cla first?
https://deepstream.io/info/community/cla/
Thanks!

Sure thing, just submitted the cla.

got it, cheers


empty cpu profile (profiling haproxy on fedora)

some repro steps:
git clone https://github.com/haproxy/haproxy
cd haproxy

make all ERR=1 TARGET=linux-glibc USE_OPENSSL=1 LDFLAGS="-lprofiler"

curl -fsSL https://github.com/summerwind/h2spec/releases/download/v2.6.0/h2spec_linux_amd64.tar.gz -o h2spec.tar.gz
tar xvf h2spec.tar.gz
chmod +x h2spec

CPUPROFILE=haproxy.prof ./haproxy -f .github/h2spec.config -d &
sleep 5
./h2spec -Svtk -h <IP_ADDRESS> -p 8443

killall  haproxy

file haproxy.prof appears, but it's empty
ilia@fedora:~/temp/haproxy-profile$ ls -l haproxy.prof
-rw-r--r-- 1 ilia ilia 0 Jan  7 16:05 haproxy.prof
ilia@fedora:~/temp/haproxy-profile$

OS: Fedora 39
gperftools: gperftools-libs-2.9.1-6.fc39.x86_64

I've just noticed that Fedora is using pretty old gperftools.
give me some time to try the latest release

well, I tested on 2.15, the same zero size haproxy.prof

This is because profile is dumped on program shutdown. If it dies from signal, there is no profile flushing.
Have your program stop normally, or have it stop normally on signal. Or arrange profiling for specific duration and Stop it yourself.
As somewhat crude (and not 100% reliable) workaround people have contributed CPUPROFILESIGNAL. Which allows you to toggle profiling on/off by sending that signal. Feel free to look it up in the code.
Yes, we could turn our profile dumping design to be continuous (via mmap-ed files) and crash-only. But this is an enhancement.
Let me turn this ticket into such enhancement. If there is anyone willing to volunteer several days of work into this, I am willing to guide such person.

hello, @alk
thank you for you help. I previously tried CPUPROFILESIGNAL, but it also behaves in strange way
as far as I understand, I must send it twice: to begin collecting and to end collecting.
git clone https://github.com/haproxy/haproxy
cd haproxy

make all ERR=1 TARGET=linux-glibc USE_OPENSSL=1 LDFLAGS="-lprofiler"

curl -fsSL https://github.com/summerwind/h2spec/releases/download/v2.6.0/h2spec_linux_amd64.tar.gz -o h2spec.tar.gz
tar xvf h2spec.tar.gz
chmod +x h2spec

CPUPROFILE=haproxy.prof CPUPROFILESIGNAL=12 ./haproxy -f .github/h2spec.config -d &
sleep 5
killall -12 haproxy
./h2spec -Svtk -h <IP_ADDRESS> -p 8443
killall -12 haproxy
sleep 5

killall  haproxy

no haproxy.prof was created
ilia@fedora:~/temp/haproxy-profile$ ls -l haproxy.prof
ls: cannot access 'haproxy.prof': No such file or directory
ilia@fedora:~/temp/haproxy-profile$

nevermind, I've managed with "31" signal. 12 was just handled by haproxy itself


UDP send after connect not possible

Once a UDP socket is connected in libuv, you have to call send with a null address or else you get UV_EISCONN and nothing is sent. There seems to be no way to do this through the uvw API, since the addr parameter is passed by reference. In udp.cc the wrappers are like:
UVW_INLINE void UDPHandle::send(const sockaddr &addr, std::unique_ptr<char[]> data, unsigned int len) {
...
    req->send(get(), &addr);
}

Empirically it works to call it like
   sock->send(*(sockaddr *)nullptr, txbuf, txbuf_size);

But this is undefined behavior in C++, and the compiler (at least Clang++-10) warns accordingly.
I think the right answer is to have versions of UDPHandle::send that don't take an address parameter.
References:
http://docs.libuv.org/en/v1.x/udp.html in the uv_udp_send section

Sounds reasonable. We're working on a v3 branch that flips the project on its head. We'll add this function there probably. 👍

Hello! Would you accept a pull request to add a variant without the address, or should I fork it, or is v3 coming soon?

Do you mean a variant as in std::variant? Why not a function overload as suggested initially? @baldvin-kovacs

Hi @skypjack ,
Is there any progress with this? We would also like this overload.
Thanks.

Not yet, sorry, I'm working on uvw to improve things but I don't have much spare time at the moment.


Error while opening socket

Description of the issue
zigbee2mqtt regularly crashes and the watchdog tries to restart it, but zigbee2mqtt fails to start with the error "Error while opening socket"
A manual 'Start' from its Addon page works without issue.
This is possibly related to an older issue: Error while opening socket #405
Here is my configuration:

Addon version
1.36.1-1
Platform
Core 2024.4.3
Supervisor 2024.04.0
Operating System 12.2
Frontend 20240404.2
Raspberry Pi 5
Logs of the issue (if applicable)
[19:59:14] INFO: Preparing to start...
[19:59:15] INFO: Socat not enabled
[19:59:15] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info  2024-04-22 19:59:17: Logging to console and directory: '/config/zigbee2mqtt/log/2024-04-22.19-59-17' filename: log.txt
Zigbee2MQTT:info  2024-04-22 19:59:17: Starting Zigbee2MQTT version 1.36.1 (commit #unknown)
Zigbee2MQTT:info  2024-04-22 19:59:17: Starting zigbee-herdsman (0.40.3)
Zigbee2MQTT:error 2024-04-22 19:59:18: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2024-04-22 19:59:18: Failed to start zigbee
Zigbee2MQTT:error 2024-04-22 19:59:18: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2024-04-22 19:59:18: Exiting...
Zigbee2MQTT:error 2024-04-22 19:59:18: Error: Error while opening socket
at Socket. (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:198:24)
at Socket.emit (node:events:529:35)
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at processTicksAndRejections (node:internal/process/task_queues:82:21)

I am having this exact log output and fail to start after trying to move my Sonoff Zigbee stick over to a Remote Adapter using ser2net on a raspberry pi. Any luck on this? I can't seem to find anything.


don't process repeated fields when they are empty

If the repeated field is empty, don't serialize it to json, as this just yields lots of empty arrays when a repeated field is defined but unused.

It may mean something when a field is empty sometimes.


Could commpile with BABEL_4_X_DEV__PG_16_X

Hi,
When I try compile BABEL_4_X_DEV with postgresql_modified_for_babelfish/BABEL_4_X_DEV__PG_16_X, here are some erors:

BIO_[get/set]_data() is replace with BIO_[get/set]_app_data() in 21b3a29.
Some multiple definition errors.

Here are two commits for this, please take a look!

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 72.238%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
40400

Relevant Lines:
55926

💛  - Coveralls


Links on NPM package is broken

Description
Links on NPM package is broken
Steps to Reproduce
Visit https://www.npmjs.com/package/@concordium/node-sdk
click on "Note that this package contains and exports the functions from the common-sdk, check the readme of that package for an overview of those."
Expected Result
It should redirect to a readme file
Actual Result
it shows a 404 not found page.

This has been fixed in the latest releases. Thank you.


OLA:  Initialize output buffer with zeros

Correct a bug in which output shorter than a full 512 channels sends uninitialized data to the OLA server.  Now fills buffer with zero bytes before copy.  Uses Massimo's suggested version of the change.

OK, sorry, ignore my previous comment.
I always forget that Q_ASSERT behaves on an inverse logic !
Wondering why the Qt guys wrote it like that...

Merged, thanks :+1:

Note to why is Q_ASSERT implemented that way: Q_ASSERT(condition) works the same way as standard assert() from  - it complains if the condition is false. Read "Q_ASSERT(condition)" or "assert(condition)" as "assert/assume/verify here, that condition holds true". If condition is not valid here i.e. the assertion is not valid, report to the user (dialog box/log message/breakpoint).

This is how I think about asserts... They are there to explicitly specify what your program expects in order to operate properly.  Asserts are meant to say "this thing must be true otherwise something is HORRIBLY wrong with the logic of my program."  Their purpose is partially to test that your program works as intended but also to document your code.  They should not be used for normal error checking within your program.  They can be compiled out of your code with preprocessor macro QT_NO_DEBUG.
Thanks for merging my commits!   I might have more interesting changes to OLA in the near future.


Support spawn setting of 0 to mean number of cpus

Description
When setting up the agent config some setups may not have the number of CPUs available but want to spawn one worker per CPU. In this case we can interpret 0 to mean all CPUs.
Other options I considered were treating spawn as a string and doing some simple math but this seems saner (not to mention simpler).
Context
I'd like to run 1 agent worker per process running under NixOS, declaratively so can't use nproc other means.
Testing

[x] Tests have run locally (with go test ./...). Buildkite employees may check this if the pipeline has run automatically.
[x] Code is formatted (with go fmt ./...)

Yep that works for me!

@moskyb I've updated the PR. I'm not sure I follow your use case for ceil when the cli flag already implies scaling by the number of cpus. Can you clarify?
In the meantime here's the output of some manual testing:
[17:31:06]-[~/c/g/b/agent]-[manny@c3mnix]
./bk-agent start --build-path ../build-path --token some-uuid 2>&1 | grep -e  Registering -e fatal | grep -v POST
2024-04-10 17:31:06 INFO   Registering agent with Buildkite...
[17:31:12]-[~/c/g/b/agent]-[manny@c3mnix]
./bk-agent start --build-path ../build-path --token some-uuid --spawn 2 2>&1 | grep -e  Registering -e fatal | grep -v POST
2024-04-10 17:31:12 INFO   Registering agent 1 of 2 with Buildkite...
[17:31:20]-[~/c/g/b/agent]-[manny@c3mnix]
./bk-agent start --build-path ../build-path --token some-uuid --spawn-per-cpu 1 2>&1 | grep -e  Registering -e fatal | grep -v POST
2024-04-10 17:31:20 INFO   Registering agent 1 of 48 with Buildkite...
[17:31:25]-[~/c/g/b/agent]-[manny@c3mnix]
./bk-agent start --build-path ../build-path --token some-uuid --spawn-per-cpu 2 2>&1 | grep -e  Registering -e fatal | grep -v POST
2024-04-10 17:31:25 INFO   Registering agent 1 of 96 with Buildkite...
[17:31:35]-[~/c/g/b/agent]-[manny@c3mnix]
./bk-agent start --build-path ../build-path --token some-uuid --spawn 2 --spawn-per-cpu 2 2>&1 | grep -e  Registering -e fatal | grep -v POST
fatal: You can't specify spawn and spawn-per-cpu ath the same time

:partying_face:


Output dns info once dns entries have bee…

…n created.
Solo: @poveyd

This is a copy and paste from what I wrote on Slack:
We would need to also change the documentation as a result of that, if we merge it. Can we please have a chat before that, involving @iain.gordon as well?

Closed following decision in meeting on 17/7/18


1.1.0 documentation

This PR contains documentation for the v1.1.0 release. Please wait for @jackjia-ibm to merge it.
@reviewers, you can validate your changes in this release by checking the Files changed tab. If all is good, no action is required. Any changes needed, you can continue to submit edits/fixes to docs-staging before this PR is merged on the 1.1.0 delivery date. Thanks!

@janan07 - your last commit didn't have DCO sign off.  If you follow the "Details" link where it it shows DCO Action Required above it will let you know what to do.  @nannanli - do you want to override the DCO for this pull request ?

Thanks for pointing this out. I am still adding additional content to the API ML release notes.


Get rid of NeuroSynth library dependency as it seems to not be maintained anymore

Currently we depend on the Neurosynth library https://github.com/NeuroLang/NeuroLang/blob/bc6acb71fbb8700bd8df2afe951eed47b349b2a1/neurolang/frontend/neurosynth_utils.py#L25 . However, this could be changed for direct access to the database as it's done in https://github.com/NeuroLang/NeuroLang/blob/bc6acb71fbb8700bd8df2afe951eed47b349b2a1/examples/plot_neurosynth_implementation.py#L31
This will help as NeuroSynth seems to not be maintained anymore.

Also, Neurosynth (& NeuroQuery) have updated their data repository so scripts to fetch Neurosynth / Neuroquery databases need to be updated.
See https://github.com/neurosynth/neurosynth-data/pull/6


Fix ci.yaml syntax error

Broken in #22761
@jrafanie @kbrock Please review.

2.7 passed the gem install, so this might end up being good.


Update manifests/f/femtoCommunity/LegendUtil/0.1.0-beta.3/femtoCommunity.LegendUtil.locale.ja-JP.yaml

Fixes an issue where this package has multiple different monikers
Microsoft Reviewers: Open in CodeFlow

[Policy] Reset Labels


surport fedora

This tool is awsome. Can it surport fedora later?

raycast-openai-translator is a extension of macOS app Raycast. You could try openai-translator, which supports Linux.


Fix a ReadConsoleOutputCharacter regression

TBA
Closes #16892
Validation Steps Performed
TBA

There's no inbox servicing to be done any longer, unless this is a P0.

@DHowett Should be good now. 🙂 I also added a feature test.


Carousel prev/next not responding

Carousel prev/next buttons do not work in dev environment (local web server) but work by loading the HTML static file. Seems like the carousel finds the prev/next links, but doesn't detect their href target. As there is a data-target attribute that works the same way, I used it to circumvent the problem.
The webpack is pretty standard, it imports bootstrap as a whole.
Chrome console reports:
Uncaught DOMException: Failed to execute 'querySelector' on 'Document': '/#carousel_element_15' is not a valid selector.
    at Object.getSelectorFromElement (webpack-internal:///2:149:35)
    at HTMLAnchorElement._dataApiClickHandler (webpack-internal:///2:1065:27)
    at HTMLDocument.dispatch (webpack-internal:///0:5183:27)
    at HTMLDocument.elemData.handle (webpack-internal:///0:4991:28)
getSelectorFromElement @ bootstrap.js?2b72:149
_dataApiClickHandler @ bootstrap.js?2b72:1065
dispatch @ jquery.js?eedf:5183
elemData.handle @ jquery.js?eedf:4991

Ambient:

Tried on v4.1 and v4.2.1
Happens on real HTML code and on demo sample from the website
webpack compiled JS/CSS bundle
macOS Mojave
Safari and Chrome, latest production

I would like to express my gratitude for the work that all the community is doing. In no particular order, from the programmers to the testers, the supporters and the documentation writers.

Same as other issues, that's not a valid selector and you should fix it eventually because it can break again.
That being said it's fixed in v4-dev and will be in the next version.


Small 508 changes after running Lighthouse/ANDI

This PR ...
Updates minor 508 issues ID'ed by running Lighthouse/ANDI. Fixes #852 .
Test Steps:

Include steps to test these changes

Changes

Small updates to content, alts, aria-*
Removes a reference to empty content on the homepage under the map. Was printing an empty <h3>
Fix for h3/h1 order issue

Checklist
Testing

[x] Tested locally?
[ ] Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?
[ ] Added tests?

Process

[ ] Are there licensing issues with any new dependencies introduced?
[ ] Includes a summary of what a code reviewer should test/verify?
[ ] Updated the release notes?
[ ] Database changes are submitted as a separate PR?
[ ] DevOps team has been notified if PR requires ops support?

Fixes

#852

To Be Done
Create GitHub issues to track the work remaining, if any

#issue

Specific Security-related subjects a reviewer should pay specific attention to

Does this PR introduce new endpoints?

new endpoint A
new endpoint B

Does this PR include changes in authentication and/or authorization of existing endpoints?
Does this change introduce new dependencies that need vetting?
Does this change require changes to our infrastructure?
Does logging contain sensitive data?
Does this PR include or remove any sensitive information itself?

If you answered 'yes' to any of the questions above, conduct a detailed Review that addresses at least:

What are the potential security threats and mitigations? Please list the STRIDE threats and how they are mitigated

Spoofing (faking authenticity)

Threat T, which could be achieved by A, is mitigated by M

Tampering (influence or sabotage the integrity of information, data, or system)
Repudiation (the ability to dispute the origin or originator of an action)
Information disclosure (data made available to entities who should not have it)
Denial of service (make a resource unavailable)
Elevation of Privilege (reduce restrictions that apply or gain privileges one should not have)

Have you ensured logging does not contain sensitive data?
Have you received any additional approvals needed for this change?

Closing this draft. Moved these changes over to another PR more up to date with master.


Fix/drawer issues

Fixing placement of drawer.

Codecov Report

Merging #607 (09845c0) into dev (d488f18) will decrease coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              dev     #607      +/-   ##
==========================================
- Coverage   89.22%   89.20%   -0.03%
==========================================
  Files         172      174       +2
  Lines        4185     4223      +38
  Branches     1391     1406      +15
==========================================
+ Hits         3734     3767      +33
- Misses        230      232       +2
- Partials      221      224       +3

Impacted Files
Coverage Δ

...ges/react-magma-dom/src/components/Modal/Modal.tsx
97.82% <100.00%> (+2.03%)
:arrow_up:

...kages/react-magma-dom/src/components/List/List.tsx
72.00% <0.00%> (ø)

...s/react-magma-dom/src/components/List/ListItem.tsx
100.00% <0.00%> (ø)

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 bb5e7d9...09845c0. Read the comment docs.


Add custom preference key

In our current setup, we have chosen not to use the Java Preferences API for various reasons. For instance, we want our advance users to be able to manually edit/add settings and we want users to be able to send their settings file to us in case we have problems recreating an issue. I found out you have the option to add a custom StorageHandler which is great for us, since it allows us to store the settings wherever we want. However, we already have a key for each setting that we would prefer to keep using instead of the breadcrumb hash.
I know the breadcrumb approach has been discussed before and that it is a question of the maximum amount of characters, but I would like to propose an option to make the breadcrumb optional instead of replacing it. First I was thinking about adding it as another variable to the constructors, but I realized it would mean a lot of additional lines and it might risk confusing anyone. So my suggestion would be to add a method in the Settings class called setCustomPreferenceKey(String key) or something like that and in the method saveSettingsValue change the line to look like this: storageHandler.saveObject(key.isEmpty() ? getBreadcrumb() : key, value.getValue()); That should prevent users from accidentally setting it and it would use the breadcrumb approach unless something else is deliberately set.
For our project it would mean that we could reuse our existing preference file quite easily, but I'm sure more users would appreciate the option to set humanly readable keys. I just wanted to check with you if you would be willing to consider something like that if I created a PR for it and if you have anything else you think I need to take into account first in that case?

Implemented in #60


Update site content

Changes proposed by this PR
Update contributor of the month blog post to point to the permanent contributors list
Updates to community page
Adding recent presentations to Resources page

closes #

Release Note

PR Checklist
Note: Please do not remove items. Mark items as done [x] or use ~strikethrough~ if you believe they are not relevant

[ ] Linked to a relevant issue. Eg: Fixes #123 or Updates #123
[ ] Removed non-atomic or wip commits
[ ] Filled in the Release Note section above
[ ] Modified the docs to match changes

Replaced by #789


Wrong default language alias in the cli container deployment

Should be "PYTHON3_SME", not "PYTHON3_TE".

In fact, there is no reason to have the language alias as a parameter if its value is hardcoded in the scripts.