Fix to typo in project "Build an interactive soundoard with p5js"

Closes #issue

[ ] My project tutorial topic has already been approved by the Codédex team.
[ ] My project tutorial file renders properly in mdx.
[ ] My .mdx file follows the project template, as well as what's recommended in the content guidelines.
[ ] The content written is my own, and not plagiarized from other sources.
[ ] All code written is thoroughly functional and commented (or documented).
[ ] I have already completed a self-review of the project tutorial.
[ ] I will comply with changes made or recommended by the Codédex team about my project tutorial.

FYI, this PR is linked to this issue.


Fixes for rdpdr

Fix bug when path is NULL for Linux dynamic disks
Implement FileAllocationInformation to truncate files correctly
Implement FileBasicInformation to set CreationTime, LastAccessTime, ChangeTime on Windows
Add dynamic disks hotplug support for MacOS client

@freerdp-bot can you test this please ?

Ok, iOS, I didn't tested it, cmake APPLE is for OSX and IOS ...

@freerdp-bot be a nice bot and test this please

Come on @freerdp-bot , do your bot job and test the new changes !

@freerdp-bot test please

Looks like the @freerdp-bot doesn't want to test that PR, just wondering why...

@hardening maybe the github crash. I can close this PR and start again.

@DavBfr If this request @freerdp-bot to test fails it would be a good idea.

@freerdp-bot test.

@DavBfr The pull looks promising, but I'd recommend rebasing it after #3079 is merged and add the appropriate stream size checks to your code too.

Ok I have landed #3079. Sorry @DavBfr the PR now needs rebasing.

@DavBfr Good, what about my comments?

@akallabeth I agree with you to move the code to winpr. It would endup with more than implementing SetFilePointerEx and SetFileTime to do it cleanly. I have no time now to do it but sure I'll do it later. I started with SetFileTime but not fully tested yet.
For the 8 bytes vs 4 bytes size bug, I suspect a bug in the Microsoft documentation. The data is not consistent with what they say and others Rdp implementations I seen uses 4 bytes unsigned, Microsoft say 8 bytes signed. This signed data seems strange for a file size.

@DavBfr Ah, ok. Could you add a comment on that 8 vs 4 byte thing, otherwise this will be corrected during the next hardening sweep when someone reads the docs.

@DavBfr The pull itself is not consistent regarding code style with respect to { } placement. Can you please change all occurrences to match the style we use in FreeRDP:
if (...)
{
    ...
}
else
{
   ....
}

Of course the same counts for typedefs, for-loops, etc.
Thanks!

Fixed the code style, reworked the commits and fixed the INT64 issue.

@freerdp-bot test.

@DavBfr Nice job! I'd say +1
But looking at drive_file.c a follow up pull would be required, this file mostly reimplements the file API provided by winpr.

@freerdp-bot test

I'll wait  #3164 to be included or it will not build.

@freerdp-bot test

@DavBfr PR builds fine now - if you fix the few formatting issues I'll merge the PR - thanks for your help!

@freerdp-bot test


Command to open specific file, not current selected

Is there a command similar to ${command:livePreview.start.preview.atFile} which accepts the desired file to be shown as a parameter?
Thanks :)

duplicate of #388


Support for inheritance

Does this library offer support for inheritance or is there any plan to support it ?  I have tested serializing an object of a class which inherits from another class and it is not working as expected.

At the moment only including the superclass as field is supported, but not expanding from an existing class. But it is a good idea for a next version.


[Usage]:

Your current environment
The output of `python collect_env.py`

How would you like to use vllm
Hello, I would like to know the difference between using SamplingType.RANDOM_SEED or SamplingType.RANDOM. As far as I follow the code, it seems to be the same. I couldnt fine where the 'seed' argument from SamplingParams is used.
Thank you
Before submitting a new issue...

[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

Please update the title of your issue with the topic.
RANDOM_SEED is set when a seed is given, RANDOM when no seed is set.

If seed is set, then an explicit torch.Generator using that seed is created and added to the SequenceGroupToSample:
https://github.com/vllm-project/vllm/blob/cc4325b66ac49e403ed9e1a8c38156a5324e1174/vllm/model_executor/sampling_metadata.py#L268-L270
https://github.com/vllm-project/vllm/blob/cc4325b66ac49e403ed9e1a8c38156a5324e1174/vllm/model_executor/sampling_metadata.py#L341-L351
https://github.com/vllm-project/vllm/blob/cc4325b66ac49e403ed9e1a8c38156a5324e1174/vllm/model_executor/sampling_metadata.py#L38-L39


cond of pmap results in internal assertion error

The following code should either work or throw a friendlier error message:
    num_devices = jax.device_count()
    x = jnp.arange(num_devices * 3, dtype=jnp.float32).reshape(num_devices, -1)
    lax.cond(True, pmap(jnp.sin), lambda x: x, x)

@apaszke Do you expect cond(pmap) to work? I think it should, just like jit(pmap) works.

BTW, the assertion that fails is
assert not ragged

in xla.axis_groups.

XLA does place restrictions on parallelism in cond branches. For example, if I recall correctly, a collective HLO is not allowed in a cond branch. I'm not sure that XLA's constraints rule out supporting pmap in a branch altogether, but I wonder if we rely on this check to guard us from producing invalid HLO today.

In principle, a pmap inside a cond should work, lifting the pmap to the top level as we do for jit. But it makes sense to not allow a collective in a cond branch, so perhaps the easiest and clearest strategy is to disallow it and to give a nice error message.

This seems like a tough call, and IMO we should also forbid pmap/xmap inside conditionals too, because otherwise we might violate the user expectation on how many devices the function actually uses.

Hi @gnecula
I executed the aforementioned code using two GPUs, and it produced the expected output, accompanied by a user warning indicating that the jitted function cond includes a pmap. Could you please verify this behavior with JAX 0.4.23 and confirm closure of this issue once resolved?
import jax
print(jax.__version__) # -> 0.4.23

import jax.numpy as jnp
import jax.lax as lax
num_devices = jax.device_count()
print('num_devices: ', num_devices) # -> num_devices:  2

x = jnp.arange(num_devices * 3, dtype=jnp.float32).reshape(num_devices, -1)
lax.cond(True, jax.pmap(jnp.sin), lambda x: x, x)

Output:
/home/selamw/.local/lib/python3.8/site-packages/jax/_src/dispatch.py:290: UserWarning: The jitted function cond includes a pmap.
Using jit-of-pmap can lead to inefficient data movement, as the outer jit does not preserve sharded data representations and instead collects input and output arrays onto a single device. Consider removing the outer jit unless you know what you're doing. See https://github.com/google/jax/issues/2926.
  warnings.warn(
Array([[ 0.        ,  0.841471  ,  0.90929747],
       [ 0.14112   , -0.7568025 , -0.9589243 ]], dtype=float32)


Add files via upload

Reads the whole name of the manga rather than just the first word.

It didn't accept manga names bigger than a single word.

It looks like you might be using different whitespace, can you revert that to format the diff to only show your changes?  I'm having a little trouble identifying the fix here.

so basically in the manga.py where it is
for manga in args:
over here it takes it as a list rather than a string and str(args) doesn't work nor does removing the loop all together .
so
x=[1]
for manga in x:
manga=str(args)
this takes the whole name and runs the loop only once.

I think that before we can move forward with the code review, it'd be better if you do what @jiaweihli is suggesting. It'd seem like you formatted your whole code and now your diff shows that every single line has changed.
I have three more suggestions that would help the code review, if I may:

I'm seeing that even though your fork was made from a104fb2fc33ae0f578e99fa8828239ea5c50caa1, you are missing the changes from 72c09ace77adb9fb4d7f50098f4a7b7474d7d723 through d195e405761210cf00e60a38c4b6cdeac90ac4f5 which add the Tankoubon functionality. Could it be that you manually copied and pasted your changes for the whole file and overwrote those changes? This will become evident once you revert your whitespace changes as @jiaweihli is saying.
It is not really clear what you are trying to fix in this Pull Request, your title states that you want to "Add files via upload" but from what I'm getting in the comments and the few changes I can distinguish, you actually wanted to add support to get mangas with more than one word in the name. So which is which?
manga_downloader supports specifying more than one manga per download session, are you sure you are not breaking this with your change? This is not really evident because the diff is messed up, but it looks like you are removing the ability to read multiple mangas and just taking the first one.

By the way, manga_downloader already supports mangas with more than one word in the name, you just need to enclose them in quotes:
python manga.py -d /home/myuser/mangas "shingeki no kyojin" bleach naruto
This will instruct manga_downloader to look for the three mangas, Shingeki no Kyojin, Bleach and Naruto and will download all chapters individually.
I just tested this in both Windows and Linux successfully using the latest master branch code.
From this, and unless anybody has any objections, I think we can close the Pull Request @jiaweihli, I don't think we need to merge or do anything else here.

Yup, it sounds like what @CharlieCorner suggested should fix your issue @Rishabh4275.
Please re-open if you're still running into any issues!


fix: #997 frontend small fixes

fixed white spaces caused by using primevue button styles
added cursor pointer to profile toggle button

looks good, thanks Jota!


lunatic: 0.10.0 -> 0.10.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/lunatic-solutions/lunatic/releases.
meta.description for lunatic is: "An Erlang inspired runtime for WebAssembly"
meta.homepage for lunatic is: "https://lunatic.solutions"
meta.changelog for lunatic is: "https://github.com/lunatic-solutions/lunatic/blob/v0.10.1/RELEASES.md"
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.10.1 with grep in /nix/store/zi7zf22h8mgp7x4y40107ki00a4v5mkf-lunatic-0.10.1
found 0.10.1 in filename of file in /nix/store/zi7zf22h8mgp7x4y40107ki00a4v5mkf-lunatic-0.10.1

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
lunatic

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/zi7zf22h8mgp7x4y40107ki00a4v5mkf-lunatic-0.10.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A lunatic https://github.com/r-ryantm/nixpkgs/archive/d95a7a5b00b73a550533b3a76f447429e16a70a5.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zi7zf22h8mgp7x4y40107ki00a4v5mkf-lunatic-0.10.1
ls -la /nix/store/zi7zf22h8mgp7x4y40107ki00a4v5mkf-lunatic-0.10.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

Maintainer pings
cc @figsoda for testing.

already updated in #193028


Move iOS and Android gitignore rules into folders

Description
Rather than have a monolithic .gitignore covering all platforms in the
app template, have each platform folder contain its own rules.
Related Issues
Fixes #40793
Tests
I added the following tests: None
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (Please read Handling breaking changes). Replace this with a link to the e-mail where you asked for input on this proposed change.
[x] No, this is not a breaking change.

I suspect there's a lot of cruft in at least the iOS rules (for files only created by older versions of Xcode), but I opted for just preserving all the existing rules. We may want to clean this up in the future though.


How well does this work with large arrays

I'm looking for an alternative to ui-select. I need something that can handle large arrays or datasets? Is this capable of handling something like 10k dropdown times?

I've never used this with something quite so large, but of the libraries i've tried, including ui-select, it is the best performing.

I'm currently trying Angular material's md-autocomplete. It has a lot of features I think are useful for dealing with large data like minimum input and remote loading of data but it triggers the on change event too often, even on clear, which is becoming a problem. I'll give this a shot tomorrow and see if it works for me. Thanks.

You might want to use remote for your search, would that work for you?

Hey,
Yea I ended up pulling the data remotely and using minimum input so the dom wouldn't generate so many nodes.
It seems to work pretty well.


Add tensor noise amplitude parameters for perturbation methods

Earth2Studio Pull Request
Description
This is a backward compatible PR that adds the ability to pass broadcastable tensors as noise amplitudes in relevant perturbation methods.
Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.
[x] The CHANGELOG.md is up to date with these changes.
[ ] An issue is linked to this pull request.

Currently there's not mechanism to ensure the noise vector is on the same device as the input tensor.
I would maybe suggest converting floats to a tensor in the inits.
Then inside each call function, the amplitude is moved onto the same device as x.device is it does not match at the moment.
Because the workflow determines the device, we shouldn't assume that the user will know what the device is at the time of construction.

Thanks for the catch, just pushed an update to include these suggestions.


controller/phy: mark ununsed var in ble_phy.h

My compiler was angry at me for that one little unused parameter...
Fixing this one line did also enable me to build NimBLE with RIOTs default gcc configuration (removing the #   CFLAGS += -Wno-unused-but-set-variable from the packages Makefile).

all green -> lets go.


ios contacts

in ios does not came guides. also we cant see contact permissin in phone settings

As a user, it seems that there are two issues you're experiencing with iOS. Firstly, you mentioned that there are no guides available. It's unfortunate that you're unable to access the guides you need, as they can be helpful for navigating and understanding the iOS Robotic system. Secondly, you mentioned that you're unable to see the contact permission in the phone settings. This could indicate a potential issue with the iOS settings or a specific app that requires contact access. It may be worth reaching out to Apple support or checking for any available software updates to address these concerns.


Sub-optimal texture sizes

A bunch of textures are weird resolutions so Optifine has to do extra work to scale them up to a standard size (16x16, 32x32, 64x64 etc). In some cases, doubling the pixel width.
Needs fixing. Think they're mostly in the Lindon pack.

OptiFine] Scaled non power of 2: acblocks:blocks/wicker_dark_bottom, 31 -> 32
[OptiFine] Scaled non power of 2: acblocks:blocks/scale_pane, 33 -> 64
[OptiFine] Scaled non power of 2: acblocks:blocks/telescope_elven, 33 -> 64
[OptiFine] Scaled non power of 2: acblocks:blocks/abacus, 33 -> 64
[OptiFine] Scaled non power of 2: acblocks:blocks/wicker_dark_top, 31 -> 32
[OptiFine] Scaled non power of 2: acblocks:blocks/wicker_dark_side, 31 -> 32
[OptiFine] Scaled non power of 2: acblocks:blocks/astrolabe_elven, 33 -> 64
[OptiFine] Scaled non power of 2: acblocks:blocks/measuring_device, 33 -> 64
[OptiFine] Scaled non power of 2: acblocks:blocks/astrolabe, 33 -> 64
[OptiFine] Scaled too small texture: acblocks:blocks/green_screen_nolight, 1 -> 16
[OptiFine] Scaled non power of 2: acblocks:blocks/weather_vane_2, 33 -> 64
[OptiFine] Scaled non power of 2: acblocks:blocks/weather_vane_1, 33 -> 64
[OptiFine] Scaled too small texture: acblocks:blocks/invisible_ghost, 1 -> 16
[OptiFine] Scaled non power of 2: acblocks:blocks/globe, 33 -> 64
[OptiFine] Scaled non power of 2: acblocks:blocks/telescope, 33 -> 64
[OptiFine] Scaled non power of 2: acblocks:blocks/interior_pillar, 31 -> 32
[OptiFine] Scaled non power of 2: acblocks:blocks/hourglass, 33 -> 64

Seems to be an issue with many more textures including ctm textures, will move to the main issue tracker


Add support for Windows Server 2022 LTSC

resolves #190

Testing in progress...

WRT "todo". The only working solution I see is that we provide -dllimage=<image> command-line argument. This is like older (and no longer existing since #187) -dlldir=<dir>, but image.

"Custom base tag" is a simpler variant of the "Insider" problem, so -dllimage seems reasonable. We could use -baseimage for "Insider", which also would support using a prepared base image from a local repo that builds on server core, as an alternative to building on top of the final images for site-local requirements.
Shouldn't block this change though.

Tested this against 4.20.3, looks fine.


Fix legacy formulations to pass catchment ID to CatchmentAggrDataSelector

#437 fixed this issue for BMI formulations, but it also needs to be addressed with the non-BMI formulations (Simple_Lumped, t_shirt). Believe these are Catchment_Formulation subclasses, so the same approach should be usable... if not, reassess.
Current behavior
These formulations will not pass a catchment ID to the DataProvider selector, so they will get data from an undefined (usually first) catchment.
Expected behavior
Should pass a catchment ID to the selector
Steps to replicate behavior (include URLs)

Screenshots

Notably, #432 now fixes this for LSTM_Realization.


Please update JabRef

JabRef released a newer version and it seems that @Vaquero84 (or @thigg?) just has to regenerate chocolateyInstall.ps1.

New versions are commited to the chocolatey package feed. Waiting for approval.

Yeah, 3.5 made it, but now, 3.6 has been released.  :innocent:

JabRef 3.6 is available on chocolatey since August, 29 and awaiting moderation. Thank you for the quick update!

The problem lies with the jre dependency and the recent chocolatey update to not allow for empty checksums. The JRE package wasn't yet updated to include checksums, so the installation of the jabref package on their validation system fails as well. The admins had been informed immediately and told me they are working on it with the maintainer, but nothing happened so far...

JabRef 3.7 was released. Is it OK to ask here for an update? 😇

I'll try to update the package as soon as an issue with chocopackageupdater is resolved, which unfortunately doesn't work on my freshly setup system.
Am 14.11.2016 um 14:47 schrieb Oliver Kopp:

JabRef 3.7 was released. Is it OK to ask here for an update? 😇
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Vaquero84/chocolatey-packages/issues/6#issuecomment-260338170,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEaohTrRSdBE3LFXFVaE3kA9-kougpT3ks5q-GZbgaJpZM4JWHZq.

We released JabRef 3.8 today. Maybe this could convince the issue to go away :)

The issue is with chocolatey. I was swamped as of late, but I'll get behind this this weekend. I may turn to the Google User Group for help as I want to be able to update packages again as soon as possible.
Thanks for letting me know!
Am 16.12.2016 um 23:10 schrieb Oliver Kopp:

We released JabRef 3.8 today. Maybe this could convince the issue to go
away :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Vaquero84/chocolatey-packages/issues/6#issuecomment-267708129,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEaohfdZ2iV0feTFKZvc9c2Otc8Gtg0pks5rIww_gaJpZM4JWHZq.

Yeah, chocolatey package 3.8.1 was approved yesterday 🎉. We also released JabRef 3.8.2 yesterday. Is it possible to update it? 🤞

My setup now looks every day for an update again.

The automatic update seems to fail for JabRef 5.0 (https://github.com/JabRef/jabref/releases/download/v5.0/JabRef-5.0.msi for Windows). Could you have a look please?

Thanks for the report and sorry for the delay in response.
Actually, I thought @tobiasdiez was working on taking over maintainership for the chocolatey packages by incorporating them into the build process.
But I see, my AU script is failing with jabref for a while now.
I'll have a look. I also see there's a portable version, so I'll take the opportunity to create a package for it as well.

At this point I could maybe even add the development snapshots as a stream. But this would require that the version number changes for each snapshot, since I only compare those to determine if there's a new version available.

My PR https://github.com/JabRef/jabref/pull/5378 concerns only the development version. I think it is easier to include the dev-stream as part of our deployment scripts (because it has access to the code to determine the exact version etc.).
If you want we can also include the chocolatey packages for the stable releases in the JabRef repository. But as you did a awesome job maintaining them so far there is no real need for action!

He started working on it at https://github.com/JabRef/jabref/pull/5378. In our last JabRef devcall (https://github.com/JabRef/jabref/wiki/Minutes#2020-03-17-8oo --> SnapCraft dev build), we decided to

keep JabRef stable chocolatey package as is (comparable to VLC https://chocolatey.org/packages/vlc)
introduce a beta channel (not sure whether this is possible)
introduce a nightly channel (comparable to VLC Nightly https://chocolatey.org/packages/vlc-nightly)

I volunteered to drive this as it seems "only" to be an issue with our GitHub actions (especially embedding https://github.com/marketplace/actions/chocolatey-action). I was just starting to understand what's going on and how the whole thing works.
@OlafHaag I would be happy if you kept maintaining the JabRef Chocolatey package - then the development team could focus on improving JabRef itself. 🎉

Thanks for the update! Last night I went ahead and created new packages. Since I changed the setup to so-called virtual packages, I introduced 2 new packages (jabref.install & jabref.portable) which yet have to be approved by a chocolatey admin.
I also added a stream for the development snapshots, but that didn't quite work out the way I was expecting, because chocolatey only pushes the first updated stream and I couldn't manually push, because the stable packages weren't approved. So I'm glad you still have plans for that.
I'll let my script keep updating the stable releases.
If you want to have the descriptions changed for the packages, just let me know!

Thanks for the update! Last night I went ahead and created new packages. Since I changed the setup to so-called virtual packages, I introduced 2 new packages (jabref.install & jabref.portable) which yet have to be approved by a chocolatey admin.

Seems they are approved:

https://chocolatey.org/packages/jabref.install
https://chocolatey.org/packages/jabref.portable

I also added a stream for the development snapshots, but that didn't quite work out the way I was expecting, because chocolatey only pushes the first updated stream and I couldn't manually push, because the stable packages weren't approved. So I'm glad you still have plans for that.

OK, I will work on it and hopefully succeed. Currently, https://chocolatey.org/packages/JabRef shows "JabRef 5.1-dev". Can you change that back to "JabRef"?

I'll let my script keep updating the stable releases.

Thank you!

Unfortunately they are not approved yet. They both have the READY status, so some moderator can appove them. They only passed the automatic validation and verification.
This manual process of approval seems quite slow, I assume it's due to a huge number of packages and a limited number of moderators.
There's also a textbox saying

This version is in moderation and has not yet been approved.

The jabref package is a trusted package, meaning it bypasses manual approval (they must think I know what I'm doing). Since I changed it to a meta-package which only installs the jabref.install dependency that somehow works, even though the dependency isn't yet approved. From a security standpoint this should probably not be possible.
The website of the package only shows the latest version as a title, even if it's a pre-release, If you search for the package instead, it shows the latest stable version.
When I updated the dev-stream, the jabref 5,1-dev package went through, because it is trusted and a pre-release, but the jabref.install 5,1-dev and jabref.portable 5,1-dev packages were rejected and couldn't be pushed,  because there's no approved version of them yet.
I can't change the package version once it's pushed. I can only push the same version as long as it is not approved, reject the package, unlist it, or push another version.
So now I wait. I could then try to push the 2 dev packages again or unlist/reject the 5.1-dev package and not push the missing packages until you have your setup ready.
What will the naming of the dev version be like? In the choco docs there's something about how it sorts them and determines which version is the most recent.

Thank you for the long explanation!

What will the naming of the dev version be like?

I will go for `jabref-nightly. (Similar to vlc --> https://chocolatey.org/packages/vlc-nightly).

I will go for `jabref-nightly. (Similar to vlc --> https://chocolatey.org/packages/vlc-nightly).

Aha, so you want to create a new package instead of pushing to the already existing packages?
I remember reading somewhere in the choco docs that it was encouraged to publich pre-release versions to the same package, only mark the version as pre-release, e.g. jabref <IP_ADDRESS>00402-nightly, which in this case would only have a dependency on jabref.install <IP_ADDRESS>00402-nightly.
But then, I guess, you can't choco install them side-by-side to still have the stable release around. Except for when one is the portable version...

@OlafHaag It seems, I understood something wrong. 😇 - Very good idea to have a pre-release version of the same package. Not sure what you mean by

At this point I could maybe even add the development snapshots as a stream. But this would require that the version number changes for each snapshot, since I only compare those to determine if there's a new version available.

(https://github.com/OlafHaag/chocolatey-packages/issues/6#issuecomment-602298689)
JabRef shows the updated version number in the about dialog (somewhere hidden since our switch to jpackage)

In our builds server (https://builds.jabref.org/master/), the time stamp changes, the filename does not. - Would it be possible to "just" create a new development snapshot each night? Maybe, it would be possibel to check for the timestamp on the server? Not sure? Maybe similar to wget -nc?

If I make the date in the download links become part of the chocolatey package version for the nightly builds, then it should work.
If choco now allows SemVer2.0.0 then it could be 5.1-dev.20200331, but the status of chocolatey/choco#1610 suggests otherwise. So it would have to be <IP_ADDRESS>00331-dev, for example.
Chocolatey allows for 4 version segments and the fourth is reserved for fix-notation, which may be suitable for jabref nightly builds, since the old nightly builds don't seem to be available for download anymore, hence breaking those packages.
The only problem rigt now is that those packages are still not approved and as long as that's the case, I can't push new package versions. I'll contact some admin about that.

For pull requests, we create following SemVer:
"FullSemVer":"5.1.0-PullRequest6232.201",

(Using GitVersion)
"FullSemVer":"5.1.0-ci.193",

The number 193 is distance in number of commits from the latest release. This should be OK, shouldn't it?

This should be OK, if choco supports SemVer2.0.0. Otherwise the 193 must be moved to the fourth version segment.

We discussed again internally. What I understood: Chocolatey offers full releases and pre-releses. No third mode. Since JabRef offers full releases and beta releases (e.g., 5.0-beta), we would like to have the alpha and beta releases published as pre-release.
I would then focus again on https://github.com/JabRef/jabref/pull/5378 to offer jabref-nightly. Beging fully aware that parallel setup won't work (besides the user chooses the portable version for the one and the installed version for the other package).
Does that make sence?

I think that makes sense. Users installing pre-releases are willingly taking the risk of using possibly unstable software. Even though a beta is probably more ready than a nightly build.

At least the jabref.install package is approved now, so once you become a maintainer of the packages on chocolatey.org you should be able to push the nightly builds. The jabref.portable package is still awaiting approval. The admins told me the majority of reviewers do that in their spare time so it can take quite some time.

I think, the decision is that we are very happy that you @OlafHaag continues with updating the packages. With the dev versions, we had issues (because of deploying nightly builds). We currently don't have time to work on that (therefore, we closed https://github.com/JabRef/jabref/pull/5378).
As the most recent version of JabRef is available, I am closing this issue.

I think, the decision is that we are very happy that you @OlafHaag continues with updating the packages. With the dev versions, we had issues (because of deploying nightly builds). We currently don't have time to work on that (therefore, we closed https://github.com/JabRef/jabref/pull/5378).
As the most recent version of JabRef is available, I am closing this issue.

Hi, we just released Version 5.11 an the website still lists 6.0 pre release
https://community.chocolatey.org/packages/JabRef#versionhistory

Sorry it took so long for me to take a look. I don't actively use choco much anymore.
I used web-scraping before to find latest releases, so each time github would change their release page, it could break. I now switched to the Github REST API for the jabref repo's latest release which should be much more robust.
I also downgraded the dev-version, since it wasn't accepting "older" versions than 6.0.
New release packages are awaiting automatic validation/moderation.


ne: 3.0.1 -> 3.1.1

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/ne/versions.
These checks were done:

built on NixOS
/nix/store/3fg6chzj3d06c3vgdg6nm31s8wh0rcy7-ne-3.1.1/bin/ne passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 3.1.1 with grep in /nix/store/3fg6chzj3d06c3vgdg6nm31s8wh0rcy7-ne-3.1.1
directory tree listing: https://gist.github.com/42510d37e15dd038fe5cb41d40afdd1b
du listing: https://gist.github.com/bc434bb32e50be446738c27c6e76a14e

meta.description for ne is: '"The nice editor"'.
Experimental: this build is cached with Cachix. To use the cache follow these experimental instructions:
One time setup in nixpkgs Git checkout:
cachix use r-ryantm
git remote add r-ryantm https://github.com/r-ryantm/nixpkgs.git

Test this build:
git fetch r-ryantm && git checkout 7fa6eff0bc4a714ef9caa673be05bac3532a4b8a && nix-shell --pure -I nixpkgs=. -p ne

Success on x86_64-linux (full log)
Attempted: ne
Partial log (click to expand)
install-info --dir-file=/nix/store/3fg6chzj3d06c3vgdg6nm31s8wh0rcy7-ne-3.1.1/share/info/dir /nix/store/3fg6chzj3d06c3vgdg6nm31s8wh0rcy7-ne-3.1.1/share/info/ne.info.gz
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/3fg6chzj3d06c3vgdg6nm31s8wh0rcy7-ne-3.1.1
shrinking /nix/store/3fg6chzj3d06c3vgdg6nm31s8wh0rcy7-ne-3.1.1/bin/ne
gzipping man pages under /nix/store/3fg6chzj3d06c3vgdg6nm31s8wh0rcy7-ne-3.1.1/share/man/
strip is /nix/store/21ymadblbmsbb2bk4q7gl4kjasp8zmgd-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/3fg6chzj3d06c3vgdg6nm31s8wh0rcy7-ne-3.1.1/bin
patching script interpreter paths in /nix/store/3fg6chzj3d06c3vgdg6nm31s8wh0rcy7-ne-3.1.1
checking for references to /build in /nix/store/3fg6chzj3d06c3vgdg6nm31s8wh0rcy7-ne-3.1.1...
/nix/store/3fg6chzj3d06c3vgdg6nm31s8wh0rcy7-ne-3.1.1

Success on x86_64-darwin (full log)
Attempted: ne
Partial log (click to expand)
cp -p doc/ne.1 /nix/store/wwwqxgxvabl58a00h10gjl931whn03mx-ne-3.1.1/share/man/man1
cp -pR doc/html doc/ne.txt doc/default.* README.md COPYING NEWS CHANGES /nix/store/wwwqxgxvabl58a00h10gjl931whn03mx-ne-3.1.1/share/doc/ne
if [ -f doc/ne.pdf ]; then cp -p doc/ne.pdf /nix/store/wwwqxgxvabl58a00h10gjl931whn03mx-ne-3.1.1/share/doc/ne ; fi
cp -p doc/ne.info.gz /nix/store/wwwqxgxvabl58a00h10gjl931whn03mx-ne-3.1.1/share/info
install-info --dir-file=/nix/store/wwwqxgxvabl58a00h10gjl931whn03mx-ne-3.1.1/share/info/dir /nix/store/wwwqxgxvabl58a00h10gjl931whn03mx-ne-3.1.1/share/info/ne.info.gz
post-installation fixup
gzipping man pages under /nix/store/wwwqxgxvabl58a00h10gjl931whn03mx-ne-3.1.1/share/man/
strip is /nix/store/yyak5sjv68n9vdgnkd2cb5djk1l9sqj5-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/wwwqxgxvabl58a00h10gjl931whn03mx-ne-3.1.1/bin
patching script interpreter paths in /nix/store/wwwqxgxvabl58a00h10gjl931whn03mx-ne-3.1.1

Failure on aarch64-linux (full log)
Attempted: ne
Partial log (click to expand)
          ^
../src/spvw_sigsegv.d:82:5: note: here
     default:
     ^~~~~~~
make: *** [Makefile:1374: spvw.o] Error 1
builder for '/nix/store/72wyf6r6vp4vbkm5hrpw7zigkpw7zyvx-clisp-2.49.drv' failed with exit code 2
cannot build derivation '/nix/store/araah9qlw7kqdziqx2bvccya7i5h1b9r-texlive-xindy.bin-2017.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/pnnqq7xcd44s2vrmpyl2di305rwrgsgl-texlive-combined-medium-2017.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/l6jh4bb1wyhcxyjf4hbnljdnvaj677ny-ne-3.1.1.drv': 1 dependencies couldn't be built
error: build of '/nix/store/l6jh4bb1wyhcxyjf4hbnljdnvaj677ny-ne-3.1.1.drv' failed


JDBC data store is always updated on terraform apply

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version
Terraform v0.14.6
Affected Resource(s)
pingfederate_jdbc_data_store
Terraform Configuration Files
resource "pingfederate_jdbc_data_store" "this" {
  name           = "test"
  driver_class   = var.jdbc_driver_class
  user_name      = var.jdbc_username
  password       = var.jdbc_password
  max_pool_size  = 10
  connection_url = var.jdbc_connection_url
  connection_url_tags {
    connection_url = var.jdbc_connection_url
    default_source = true
  }
}

Debug Output
Panic Output
Expected Behavior
Expected no update if Terraform configuration file not changed.
Actual Behavior
$ terraform apply
pingfederate_jdbc_data_store.this: Refreshing state... [id=JDBC-E463B3A46AFCDB3261A3355C02D346A22A8F8642]

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # pingfederate_jdbc_data_store.this will be updated in-place
  ~ resource "pingfederate_jdbc_data_store" "this" {
      - encrypted_password           = "eyJhbGciOiJkaXIiLCJlbmMiOiJBMTI4Q0JDLUhTMjU2Iiwia2lkIjoiMEh4WHlYR2RvWSIsInZlcnNpb24iOiIxMC4xLjIuMCJ9..8TWYRLLJt_ZNigxlQsSyww.rBO00UfGWaA5ek1a0UeMyxfb3whxlsN44xYvAjCdFBg.AJE30fRpPDRiNYbqDAgY9A" -> null
        id                           = "JDBC-E463B3A46AFCDB3261A3355C02D346A22A8F8642"
        name                         = "test"
        # (10 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

pingfederate_jdbc_data_store.this: Modifying... [id=JDBC-E463B3A46AFCDB3261A3355C02D346A22A8F8642]
pingfederate_jdbc_data_store.this: Modifications complete after 0s [id=JDBC-E463B3A46AFCDB3261A3355C02D346A22A8F8642]

Apply complete! Resources: 0 added, 1 changed, 0 destroyed.
$ terraform apply
pingfederate_jdbc_data_store.this: Refreshing state... [id=JDBC-E463B3A46AFCDB3261A3355C02D346A22A8F8642]

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # pingfederate_jdbc_data_store.this will be updated in-place
  ~ resource "pingfederate_jdbc_data_store" "this" {
      - encrypted_password           = "eyJhbGciOiJkaXIiLCJlbmMiOiJBMTI4Q0JDLUhTMjU2Iiwia2lkIjoiMEh4WHlYR2RvWSIsInZlcnNpb24iOiIxMC4xLjIuMCJ9..i0UVOvUPWrmyv-TuvJ22jw.elM-K-InzRF4FrPAnOnm12gaor53tfQsBl9Clmutz-E.sS5pt0bpiRkcCxZEtieDjQ" -> null
        id                           = "JDBC-E463B3A46AFCDB3261A3355C02D346A22A8F8642"
        name                         = "test"
        # (10 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

pingfederate_jdbc_data_store.this: Modifying... [id=JDBC-E463B3A46AFCDB3261A3355C02D346A22A8F8642]
pingfederate_jdbc_data_store.this: Modifications complete after 0s [id=JDBC-E463B3A46AFCDB3261A3355C02D346A22A8F8642]

Apply complete! Resources: 0 added, 1 changed, 0 destroyed.

Steps to Reproduce
repeat terraform apply without modifying Terraform configuration file
Important Factoids
References

#0000

This is already fixed on master and will be in the next release.

Fixed in v0.0.11


Benny/tez address

Changes:

Added new ChainPubKeyInput and ChainPubKey types to the graphQL schema
Added respective go types
Changed verify signature to take in a pub key

actually @bennycio i think this needs to be updated as well:


fix: Code: update the LSP server without asking

Most LSP extensions seem to do the same thing, and this is causing some
confusion for users who don't notice the update prompt before Code hides
it.

I guess that makes sense! The original thinking was that we don't want to call home without explicit opt-in (via nightly channel), but I guess, as we can not not download the binary, the user-experienced is pretty bad. The ideal solution would be for the VS Code marketplace to allow for distribution of binaries, but it doesn't look like it's comming.
Let's update the Securty section of the manual though, to mention that we now do http by default when downloading the server.

Alternative ideal solution -- ship rust-analyzer on stable rustup. Doesn't look any more comminger.

But then you only get an update every six weeks :-).

Let's update the Security section of the manual though

Yeah, we should probably move the PRIVACY.md stuff under there.

TIL we have privacy.md! Yeah, makes sense, although we probably should link security section from the readme then

r? @matklad

The ideal solution would be for the VS Code marketplace to allow for distribution of binaries, but it doesn't look like it's comming.

Technically this appears to be possible - I know of at least one extension that’s including rust binaries ;). Is there a policy that’s preventing this?

We build binaries for 7 platforms (soon to be 8?), so we can't pack every one of them in the vsix. matklad meant platform-specific vsixes.

Maybe it should ask, but contain "don't ask again" checkbox?
Users with expensive network connections may download xpi file separately, expect that that's a complete extension and be surprised that it then downloads a large file from internet without asking anything.

There's a preference you can toggle to disable this (look at the change). I suggest disabling Code extension updates too, in order to avoid the situation you mentioned.


how to add a animated sprite in the background between the characters

Describe your problem here.
i'm trying to add an animated sprite between the characters in the background but i don't know how
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
No response

it's because it dont have a folder in assets/songs or because the folder name is with Mayús


jq not installed on Ubuntu for quickstart

Current Behavior
On a fresh install, running make quickstart errors on not finding the jq command
Expected Behavior

Installs jq
Successful installation

Possible Solution
Fix make file to install jq when running on linux host
Steps to Reproduce

Fresh ubuntu vm
make quickstart
profit

Context
Your Environment

Fresh ubuntu vm, any version

Fixed by #259


Updating to Swagger 3.0

Hi! Thank you for this great project! It helped me to solve issue with CORS. I guess Electron apps don't not have the same restrictions for requests as browser.
Can you please update this project to swagger-ui v3? Using it intensely is hard without having latest swagger version. I tried to do it by changing swagger-ui.js, but failed.

Yes. I will work on that this weekend. Thanks for the request.


Add Django 2.2 and Python 3.7 to tests

Add Django 2.1 and 2.2 to test suite
Add Python 3.7 to test suite
Update .travis.yml to run tests for all python versions
Use tox-travis to smartly run the correct python+django version combos defined in the tox.ini
Update sandbox/settings.py to resolve errors thrown by django 2.2

Also, I went out on a limb and updated the changelog, recognizing there's a decent chance that ends up being unhelpful.

I'm not sure why Travis tests aren't being reported here, but the tests are passing: https://travis-ci.org/crgwbr/asymmetric-jwt-auth/pull_requests


expect($$('li').count()).toBe(0); throws error if empty

I want to test if my list is empty, if I remove all list items, but sadly this doesn't work.
// default list
expect($$('li').count()).toBe(1);  // works

// ...remove lit item

// new list
expect($$('li').count()).toBe(0); // throws error

The error is Error: Index out of bound. Trying to access element at index: 0, but there are only 0 elements that match locator. This probably can make sense, but for me it feels weird as "there are only 0 elements" is exactly what I want to verify .

Sorry! It was a following expect which throw the error!


add solution to build-javascript-objects.portuguese.md

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

Closes #XXXXX

@cslv Instead of having 5 separate PRs which add solutions to challenges, we prefer that you add the solutions in a single PR.  Please close this PR and make the same changes to your first PR #37203.  Please see your first PR for additional instructions related to adding solutions to challenges.
Thank you.

@cslv Closing this PR, so you can add the changes and test the changes on the other PR (#37203).


WalletConnect v2 #3413

Closes #3413

@oa-s Do you think this is working sufficiently well and safe to merge, i.e. it doesn't break WalletConnect v1? If it is, can you help to clean it up, rebase and let's merge it.

@hboon is this ok that deployment target version increased to 13?

Ok. Let’s do it.


Add ability to use third party error tracking software for expressjs

Added a config property that looks like so.  All error handlers (sentry, rollbar, etc.) need their error handler to be injected before all other error handling software.  This code sets it if supplied by the user.
	errorTracking: {
		requestHandler: Sentry.Handlers.requestHandler,
		errorHandler: Sentry.Handlers.errorHandler
	}

This looks pretty good to me. I like the idea of allowing people to be able to inject their own middleware to support more custom behaviors. @jonterrylee Let me know what you think but I am good with merging this in.
Once we do, I want to add this as another item on #119, this would be something useful to document and looks like it simply accepts any function that returns valid express middleware. We may need to think about any warnings, such as not calling next and breaking the chain of middleware (if they do this and don't return an operation outcome for an error, their implementation may no longer be conformant). I don't think we need to code anything around this, rather just mention it in our wiki.


[BUG] Nav Bar Hover Effect

Nav Bar should have a hover effect

https://med-space.vercel.app/

Please add hactoberfest and GSSoC24 tag. You can assign me for this issue.

sorry, but not needed


Error while trying to build

I have a Dockerfile that I use for trying to build below located here https://gist.github.com/dc510ccd122e6c13d6271833dd1cbcee   I keep getting the following error while trying to build the HEAD , the tag v0.5.0 builds just fine.

#15 105.6    Compiling num_enum_derive v0.5.4
#15 105.7    Compiling cursive v0.16.3
#15 107.1    Compiling cursive_buffered_backend v0.5.0
#15 107.7    Compiling below-common v0.5.0 (/src/below/below/common)
#15 107.8    Compiling num_enum v0.5.4
#15 108.2    Compiling btrfs v0.5.0 (/src/below/below/btrfs)
#15 108.4    Compiling below-gpu-stats v0.5.0 (/src/below/below/gpu_stats)
#15 108.7 error: `#[derive]` can't be used on a `#[repr(packed)]` struct that does not derive Copy (error E0133)
#15 108.7     --> below/btrfs/src/btrfs_api/open_source/btrfs_sys.rs:4997:10
#15 108.7      |
#15 108.7 4997 | #[derive(Debug)]
#15 108.7      |          ^^^^^
#15 108.7      |
#15 108.7      = note: `#[deny(unaligned_references)]` on by default
#15 108.7      = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
#15 108.7      = note: for more information, see issue #82523 <https://github.com/rust-lang/rust/issues/82523>
#15 108.7      = note: this error originates in the derive macro `Debug` (in Nightly builds, run with -Z macro-backtrace for more info)
#15 108.7
#15 108.8 error: could not compile `btrfs` due to 2 previous errors
#15 108.8 warning: build failed, waiting for other jobs to finish...
------
executor failed running [/bin/sh -c /root/.cargo/bin/cargo build --release --all-targets]: exit code: 101
make: *** [build] Error 1
(ins)lrfurtado-mbp:below_build lrfurtado$

Hi Luciano, we believe that this will be fixed by updating the version of bindgen that we use in order to generate the btrfs_sys.rs file.
We will take a look at it tomorrow and get back to you. Likely, the newer version of bindgen contains a fix.

Hi Luciano, the latest commit contains a newer version of btrfs_sys.rs file that is build with the newest bindgen. We believe that this should fix your issue. Let us know if you are still running into issues

it worked


feat: stacking support in CLI

This PR adds CLI support for stacking using the new @stacks/stacking lib.
Type of Change

[x] New feature
[ ] Bug fix
[ ] API reference/documentation update
[ ] Other

Does this introduce a breaking change?
No
Are documentation updates required?
Yes

[ ] Link to documentation updates:

Testing information
Checklist

[x] Code is commented where needed
[ ] Unit test coverage for new or modified code paths
[x] npm run test passes
[ ] Changelog is updated
[ ] Tag 1 of @yknl or @zone117x for review

@yknl as per our discussions, could you please create some documentation for this. The most important goal would be for QAing by @timstackblock. But, we also would need content for the docs

https://github.com/blockstack/stacks.js/issues/886


Is there a way to prepend text from dataviewJS?

It would be amazing to prepend the result of a dataviewJS query. This would give you endless possibilities with custom prepends for links.
Is there any way to do this?

That's definitely an interesting proposal. It's out of scope for me right now, but a PR is welcome.


Encode query semicolons

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you expect to see?
I can see PR https://github.com/traefik/traefik/pull/9943 is merged but it still not added in latest chart 23.1.0 . Can I use it in same chart or will be added in later version?

related to #889

Hello @kapilag123,
Thanks for your interest in Traefik.
The fix https://github.com/traefik/traefik/pull/9943 is available in Traefik Proxy 2.10.2
A new release of this chart should happen this week, after a new release of Traefik Proxy.
I close this issue since it's a duplicate of #886.


How do i change filesize limit

I am trying to figure out how to increase the limit from 10MB. i have updated the nginx config to allow larger but it seems to be coded into the actual site somewhere as it will give an error message saying the image is larger than the max allowed of 10MB where can i configure this limit to be larger?

Previously it wasn't really possible without editing the code, as it was just hardcoded in both the backend and frontend, but I've now made it configurable through a configuration file.
There's an example configuration at: https://github.com/forbjok/blazebooru/blob/master/backend/core/src/config/default_config.toml
This file should be called "config.toml" and be placed in a directory somewhere, and in order to use it via the docker compose setup, you can override the environment variable "BLAZEBOORU_CONFIG_PATH" with the path to that configuration directory. (NOT including the filename, just the parent directory that contains the config.toml file)

closed by b86f585ce1cb25a31510e689db1acddb4c96572c  :D


rename license.txt to LICENSE

To make consistent with docblock comment:
 * For the full copyright and license information, please view the LICENSE
 * file that was distributed with this source code.

Checklist:

[x] Securely signed commits

This is duplicate of #3828

Oops, ok, closing


Can't filter objects with missing date field values

Environment
Python version: Any
Nautobot version: 1.3.2
Any objects with date fields can't be filtered to search those with missing values.
This is related to #795.  While most fields you can now search with "null" to find objects with missing values if the field is a date field the UI will not let you enter "null" and if you change the URL to include ?cf_date_field=null the filter is not applied.  The easiest way to reproduce this is with a custom date field which is allowed to be null.
Expected Behavior
Only objects with missing (empty) value in a given date (custom or otherwise) fields should have been returned.
Observed Behavior
All objects were returned regardless of the date field.

May be solved by #2126


fixed art-bot query using catalogs

/hold

@ashwindasr now it is working also if we have multiple CDNs or deliveries. Please test it.

@ashwindasr
there are still two things I don't like:

when we have i.e. the component_name: ose-cluster-policy-controller-container
there does not exist a distgit for this repo, but for cluster-policy-controller.
When it is easy to strip -container it is not clear how to look if ose is needed or not.

When accessing an URL like https://art-dash-server-art-dashboard-server.apps.artc2023.pc3z.p1.openshiftapps.com/api/v1/pipeline-image?starting_from=distgit&name=golang-github-prometheus-alertmanager&version=4.16 it takes a lot of time (also when you browse to this URL).
So the command for art -bot: What catalogs are associated with  takes very long! I don't think we can accelerate this.

@mbiarnes

We store the brew package name in the image metadata (ocp-build-data config file) itself, so doozer runtime will have the mapping (since the distgit key is the file name)
Yes right now its not optimized, but it has the potential to be cached on the server side, if you are looking to optimize it

what catalog are associated with  works.
Before it could fetch from the json file ['config']['config']['label'] the url, but this doesn't work any more.
The resulting catalog url has to be constructed by accessing urls like:
https://art-dash-server-art-dashboard-server.apps.artc2023.pc3z.p1.openshiftapps.com/api/v1/pipeline-image?starting_from=distgit&name=ose-alibaba-cloud-controller-manager&version=4.16
and retrieving from the json answer
delivery_repo_id and delivery_repo_name
The access to https://art-dash-server-art-dashboard-server.apps.artc2023.pc3z.p1.openshiftapps.com/api/v1/pipeline-image?starting_from=distgit&name=>calatog_name>&version=<MAJ.MIN) takes a long amount of time

/unhold


Added Data Validation

Checking the Heroku config before running shell commands. If config is incorrect, throw an error and show the problem.

Makes sure that dyno_counts are:

present
integer
more than 0

Makes sure that dyno_type is:

present
string
one of the official dyno types

~/Git/heroku-deploy$ python deploy.py /home/damir/bentoml/repository/IrisClassifier/20210923152106_C95F2E test-script heroku_config.json
Traceback (most recent call last):
  File "deploy.py", line 47, in <module>
    deploy_heroku(bento_bundle_path, deployment_name, config_json)
  File "deploy.py", line 7, in deploy_heroku
    heroku_config = get_configuration_value(config_json)
  File "/home/damir/Git/heroku-deploy/utils/__init__.py", line 31, in get_configuration_value
    validate_configuration_value(configuration)
  File "/home/damir/Git/heroku-deploy/utils/__init__.py", line 70, in validate_configuration_value
    raise Exception(
Exception: Config validation failed {'dyno_counts': ['min value is 1']}

Quick update: talked to Jithin and I'll make a PR to make heroku-deploy work as an operator with bcdt


docs: Doctrine instability in long-running runtime

Is still still an issue after the changes they merged regarding APP_RUNTIME_MODE?

@KDederichs I still have the issue.

I had similar issues with Doctrine and Symfony ... rebooting the kernel between requests fixed it in my case. See https://github.com/php-runtime/runtime/pull/166

This is now fixed in Symfony! Thanks for your help @vasilvestre!!
https://github.com/symfony/symfony/pull/53214


Uncaught Invariant Violation: Unknown DraftEntity key: null.

Thanks for this library in advance!
When typing to the end of last word of any paragraph (segment) I'm having the following error
Uncaught Invariant Violation: Unknown DraftEntity key: null.
and the error on developer console is as follows:

I have spent few days to solve this but so far no luck. It looks like a bug and persists on both Chrome & Firefox. Somehow, when you add new characters to the end of last word of any paragraph, last element of the list returned from contentBlock.getChildrenList() method is null and causing this error.
Any idea, help, advice is appreciated

@afacar did you manage to get this resolved? I am having the same issue

I couldn't find a proper way but do a hacky/temp solution.
I modified draftjs library under node_modules (getEntitityKeyForSelection.js)

@afacar did you manage to get this resolved? I am having the same issue

I couldn't find a proper way but do a hacky/temp solution.
I modified draftjs library under node_modules (getEntitityKeyForSelection.js)

@afacar did you manage to get this resolved? I am having the same issue

I couldn't find a proper way but do a hacky/temp solution.
I modified draftjs library under node_modules (getEntitityKeyForSelection.js)

Do you mind sharing with me the modified getEntitityKeyForSelection.js file?

Note that this is not the ideal solution and can cause another problems. You can replace the original file's content with this one's
getEntityKeyForSelection.js.txt

@afacar I see thanks, now the issue is with updating the new blockMap


access to environment variable

Hello!
If i am use for migrate this command:
./vendor/bin/phinx migrate -e testing
Can i get value of "-e" option in ./phinx.php

Any update here?


fix forgotten link in rpc specfile

Following up to #745

Preview is available here:http://developers-pr747.previews.kube001.services.stellar-ops.com


Bitmap editor...

[BitMapEditor - Delphi] (https://github.com/EverestSoftwareLLC/BitMapEdtior-Delphi). `[Delphi]`  This is code for a single form, simple, bitmap editor for Delphi.

Added, thanks!


Bump dependency golang.org/x/net to v0.23.0

Merge Checklist

[ ] Followed patch format from upstream recommendation: https://github.com/kata-containers/community/blob/main/CONTRIBUTING.md#patch-format

[ ] Included a single commit in a given PR - at least unless there are related commits and each makes sense as a change on its own.

[ ] Aware about the PR to be merged using "create a merge commit" rather than "squash and merge" (or similar)
[ ] The upstream/missing label (or upstream/not-needed) has been set on the PR.

Summary
This PR bumps indirect dependency golang.org/x/net to fix CVE-2023-39325 & CVE-2023-45288
The dependencies bumped are
golang.org/x/sys v0.7.0 -> v0.18.0
golang.org/x/net v0.8.0 -> v0.23.0
Test Methodology

Fixes CVE-2023-45288 & CVE-2023-39325


[TW#12790] Feature request: simple BT to UART bridge

Hi,
I have some experience with ESP8266 and HC-05. And I was kind of hoping to meet here any analog to this functionality. I have no idea what is HCI, Gatt, BT Classic, Bluedroid, etc.. which are used in examples.
What will be really helpful (I guess for lots of ESP32 users) is to have some "getting started" example which will contain something like Arduino's software serial :
`_if (uart0.available()) {
uart1.write(uart0.read());
}
if (uart1.available()) {
uart0.write(uart1.read());
}_`
where uart0 is connected to PC through FTDI(usb to uart) and uart1 is connected to PC (or phone) via BT.

There is no support for SPP at the moment (which is what HC-05 uses), so this may take some time to implement. Suggest reading a bit about GATT in the meantime...

@igrr, thanks for clear answer. Does anybody have planse to implement it?
Sure I'll get falimiar with GATT. just wanted to start with something simple

We do plan to support SPP in ESP-IDF, but it's currently low priority. So maybe a couple of releases down the road...

Need this for my current project aswell, sooner please ? ;)

@PhilColbert We will release used uart command to control BLE in the next version(2.1) of SDK, thanks.

Thank you :)

I have a question. Using GATT let me connect an hc05 bluetooth module with BLE like in esp32?


Apply deprecated evaluation_strategy

What does this PR do?
This PR applies the deprecated evaluation_strategy from https://github.com/huggingface/transformers/pull/30190.
TL;DR: evaluation_strategy -> eval_strategy
(Should go live in v4.41.0, but opening now so it's here when ready!)
Fixes # (issue)
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?

Who can review?

ONNX Runtime Training: @JingyaHuang

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

@muellerzr @IlyasMoutawwakil could we merge this?
It currently breaks examples with transformers>=4.41 because evaluation_strategy is set to None (https://github.com/huggingface/transformers/blob/main/src/transformers/training_args.py#1375, which errors at https://github.com/huggingface/optimum/blob/main/optimum/onnxruntime/training_args.py#L129 because EvaluationStrategy expects one of ['no', 'steps', 'epoch']


Host verification failed

On the server I can clone my repo using a ~/.ssh/config file just fine.
However during pm2 deploy via GH actions and using SSH-Agent GH Action I get those errors:
[PM2] Spawning PM2 daemon with pm2_home=/home/runner/.pm2
[PM2] PM2 Successfully daemonized
--> Deploying to production environment
--> on host xxxxxxxxxxxxxxxxxx
fatal: HEAD does not point to a branch
  ○ deploying origin/master
  ○ executing pre-deploy-local
  ○ hook pre-deploy
Host key verification failed.
  ○ fetching updates
  ○ full fetch
Host key verification failed.
  fetch failed

Deploy key and SSH-Agent Secret are properly setup. What could I check on the server to see whats going wrong? I also have GH in the known_hosts file like this:
|1|wyuE7qS7vMnqwGKn1OijR6fiFkM=|oIz+ibUAaBVq7/k7nnm878bvAWc= ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==
|1|bkTHcwltNJR2PnF9J8vpT/+Va2k=|FHr/SLp19tu9KuMUCZ05dYWnbec= ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==
|1|xH47HLpSxWip8wMGVikJLn6BvFw=|Zf+DbrlxHdy2MtAG5cVKmd4ZPs4= ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==

It seems when I disable strict host checking in the ecosystem file I am getting this result:
[PM2] Spawning PM2 daemon with pm2_home=/home/runner/.pm2
[PM2] PM2 Successfully daemonized
--> Deploying to production environment
--> on host MY.SERVER
fatal: HEAD does not point to a branch
  ○ deploying origin/master
  ○ executing pre-deploy-local
  ○ hook pre-deploy
Warning: Permanently added '[MY.SERVER]:36077,[<IP_ADDRESS>]:36077' (ECDSA) to the list of known hosts.

So the problem was that the HOST server that is deployed to was not in the known_hosts file of the CI system (GitHub). Is my conclusion correct? And should that maybe added to the FAQ?

@pke
I had same problem in GitHub Actions and
I just updated ssh option in my ecosystem.json.
"ssh_options": "StrictHostKeyChecking=no",

and it just works.

Sure this works and its a hack to circumvent security features ;)


Can't prevent default input in TextInput in controlled component

Description
The comment in #24585 suggested creating another issue for this. It's also similar to #23578.
The problem is that you can't prevent the default behavior of controlled TextInput in ReactNative.
I've asked this on StackOverflow: How to prevent adding typed keys into controlled TextInput in React-Native?. But looking at similar issues this is a bug (or missing feature) in ReactNative.
React Native Version
0.71.8
Output of npx react-native info
info Fetching system and libraries information...
System:
OS: Linux 5.19 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)
CPU: (8) x64 Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz
Memory: 19.22 GB / 30.98 GB
Shell: 5.1.16 - /bin/bash
Binaries:
Node: 20.3.0 - ~/.nvm/versions/node/v20.3.0/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v20.3.0/bin/yarn
npm: 9.6.7 - ~/.nvm/versions/node/v20.3.0/bin/npm
Watchman: Not Found
SDKs:
Android SDK: Not Found
IDEs:
Android Studio: Not Found
Languages:
Java: 1.8.0_362 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.2.0 => 18.2.0
react-native: 0.71.8 => 0.71.8
npmGlobalPackages:
react-native: Not Found
info React Native v0.72.1 is now available (your project is running on v0.71.8).
info Changelog: https://github.com/facebook/react-native/releases/tag/v0.72.1
info Diff: https://react-native-community.github.io/upgrade-helper/?from=0.71.8
info For more info, check out "https://reactnative.dev/docs/upgrading".
Steps to reproduce
Type the number into the input field with the code below. The code works on the Expo playground but fails on Android Emulator (didn't tested on a real device).
From the demo I expect the input to not change.

Snack, code example, screenshot, or link to a repository
const ControlledComponent = () => {
  const [state, setState] = useState('0.00');
  const cursor = 1;
  return (
    <TextInput
      ref={ref}
      autoFocus
      onKeyPress={() => { /* empty */ }}
      selection={{start: cursor, end: cursor}}
      value={state}
      keyboardType="numeric"
    />
  );
};

event.preventDefault() also doesn't work:
const ControlledComponent = () => {
  const [state, setState] = useState('0.00');
  const cursor = 1;
  return (
    <TextInput
      ref={ref}
      autoFocus
      onKeyPress={(e) => { e.preventDefault() }}
      selection={{start: cursor, end: cursor}}
      value={state}
      keyboardType="numeric"
    />
  );
};

I'm using expo I'm not sure how to update react-native got an error when I do:
Some dependencies are incompatible with the installed expo version:
<EMAIL_ADDRESS>- expected version: 0.71.8
Your project may not work correctly until you install the correct versions of the packages.
Install individual packages by running npx expo install<EMAIL_ADDRESS>

I'm using Expo. I'm not sure how to update react-native. Got an error when I do:

Can you try on a non-Expo project and verify that the issue is happening also there?

Sure will try to create a demo, but it may take a while since I never used raw react-native.

I'm not able to run React-native on Linux because of #26097 none of the solutions works.

I can confirm the same happen in React-Native without expo, tested on 0.72.1
$ npx react-native info
info Fetching system and libraries information...
System:
  OS: Linux 6.3 Fedora Linux 38 (Xfce)
  CPU: (8) x64 Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
  Memory: 6.23 GB / 15.27 GB
  Shell:
    version: 5.2.15
    path: /bin/bash
Binaries:
  Node:
    version: 18.16.0
    path: ~/.nvm/versions/node/v18.16.0/bin/node
  Yarn:
    version: 1.22.19
    path: ~/.nvm/versions/node/v18.16.0/bin/yarn
  npm:
    version: 9.5.1
    path: ~/.nvm/versions/node/v18.16.0/bin/npm
  Watchman: Not Found
SDKs:
  Android SDK: Not Found
IDEs:
  Android Studio: Not Found
Languages:
  Java:
    version: 17.0.7
    path: /usr/bin/javac
  Ruby:
    version: 3.2.2
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.72.1
    wanted: 0.72.1
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found

I can confirm the same happen in React-Native without expo, tested on 0.72.1

Can you also share a repro?

Sure, it's the default app created with react-native with the component in the original post.
But here is it: https://github.com/jcubic/react-native-bug

Hi @jcubic, & @cortinico, this looks like a good first contribution, can I pick this up, and debug more?

Hi @jcubic, & @cortinico, this looks like a good first contribution, can I pick this up, and debug more?

Please do 🙏

Any tips on where I should look in the code?

Hi!
I am just a newbie and learning the core react-native aspects, It could be using an incorrect approach for this, but here is something that I found.
The SyntheticEvents class prototype looks good, in terms of handling the event.stopPropagation callback and the event.preventDefault callback.
The conditions excel and I took a look around the native dispatchKeyEventOrEnqueue callback from the ReactEditTextInputConnectionWrapper class, under the setComposingText function overwritten from the InputConnectionWrapper class which I am currently debugging and seems to be the culprit, but I need some time going around this, and to be able to confirm the exact changes needed.
It seems that there is a condition on the setComposingText function:
boolean cursorMovedBackwardsOrAtBeginningOfInput =
        (currentSelectionStart < previousSelectionStart) || currentSelectionStart <= 0;

And we might have to add in a similar Boolean condition for a preventDefault/stopPropagation scenario, which would remove the bubbling of the key input, and thereby overwrite the nativeEvent property, and achieve event.stopPropagation behavior.
Again, this is something from the perspective of a beginner community contributor, I could be wrong.

@vision72 did you try to make your change and test locally if it works? Experimentation is the best way to test if you're right.
Now I have more free time and I will also try to debug this, unless you will solve this first.
It was really annoying that I needed to implement my own keyboard to get rid of this bug, I'm not in that project anymore but I can see if I can fix this issue.

@jcubic Use defaultValue instead of value

same issue, have any update?

same issue, have any update?


Add axis label format 'automatic'

Description

What was changed in this pull request?

The axis label format option 'automatic' was added which corresponds to the current option 'scientific'. 'automatic' is the new default. 'scientific' has been changed to be strictly exponential notation.

Why is it necessary?

Make axis format options more clear.
Note: This is a breaking change. Existing view configs have to be updated in order to use the same label format as before.
Checklist

[x] Set proper GitHub labels (e.g. v1.6+, ignore if you don't know)
[x] Unit tests added or updated
[x] Documentation added or updated
[x] Example(s) added or updated
[ ] Update schema.json if there are changes to the viewconf JSON structure format
[ ] Screenshot for visual changes (e.g. new tracks or UI changes)
[x] Updated CHANGELOG.md

The fact that this is a breaking change is of course not great. Not so sure anymore if it is worth it.

Is there a real need for this change besides making the axis format more explicit? I.e., have people complained about the current behavior?
If not I would not be in favor of not introducing yet another option.
On the other hand, if this is something people want, how about introducing a new "strict" mode? This boolean option could be called axisLabelFormattingStrict and be set to false by default. That would allow us to introduce strict formatting without introducing a breaking change. It would also allow us to have multiple formats that can have strict and automatic behavior.

Yeah, I don't think anybody complained. This just would be the cleanest way to do it in my opinion. axisLabelFormattingStrict would be a way to avoid the breaking change but it adds complexity.
The whole thing is probably not important enough to justify a breaking change for now. Maybe it could be incorporated at a time when there are some other major changes to the view config and users have to review them anyway?


Addition of citation feature in population models

Fixes #46 .
Description of the Change
I have added a citation feature for all three population models in the following way:

Updated the .asdf files for the three models to include a citation of the form ["10.3847/1538-4357/ab5fd3", "10.3847/1538-4357/aca09d"].
Updated model.py and test_model.py to account for this new feature and confirmed it was behaving as expected.
Updated documentation, including tutorials.rst and popsycle_model_example.ipynb, to explain this adjustment and prevent potential errors.

Checklist
Please check all that apply to your proposed changes

[ ] Added package dependency
[ ] Added data
[x] Documentation change
[x] code change

Additional context
I had issues simply adding the citation feature in the raithel18.asdf file, so I rewrote the file with the change and replaced the previous version. The other two files gave no trouble adding the change. Just thought it might be worth noting that the raithel.asdf file is new, but does not seem to be creating any problems.

Whoops, you are completely right! I fixed the typo in the notebook and all should (hopefully) be good to go now :)

Whoops, you are completely right! I fixed the typo in the notebook but the test is still failing :( Any idea why this might be the case?

Its because the notebooks import the pypi version of popclass not the cutting edge dev version. This will resolve its self when I push a new package version :) I added a setting to get the notebooks to ignore the errors for now.

Will merge now, great work :)

Thank you, happy it's all working out!!


Enable Travis CI

I'll be using this PR to investigate some Travis CI woes, don't merge just yet

Closed. Added issue #1309 for tests in Travis.


Interface configuration

Implement the following configuration options:

Interface IPv4/IPv6 addresses
Interface admin status
Interface MTU
VLAN subinterfaces

Example configuration (CLI):
interfaces interface eth1.10
 type ietf-if-extensions:ethSubInterface
 encapsulation dot1q-vlan outer-tag vlan-id 10
 parent-interface eth1
 !
 ipv4 mtu 1500
 ipv4 address <IP_ADDRESS>
  prefix-length 24
!

Example configuration (JSON):
{
  "ietf-interfaces:interfaces": {
    "interface": [
      {
        "name": "eth1.10",
        "type": "ietf-if-extensions:ethSubInterface",
        "ietf-if-extensions:encapsulation": {
          "ietf-if-vlan-encapsulation:dot1q-vlan": {
            "outer-tag": {
              "vlan-id": 10
            }
          }
        },
        "ietf-if-extensions:parent-interface": "eth1",
        "ietf-ip:ipv4": {
          "mtu": 1500,
          "address": [
            {
              "ip": "<IP_ADDRESS>",
              "prefix-length": 24
            }
          ]
        }
      }
    ]
  }
}

Verification (kernel):
# ip -4 addr show dev eth1.10
6: eth1.10@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth1.10
       valid_lft forever preferred_lft forever
# ip -d link show dev eth1.10
6: eth1.10@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether e2:9f:e6:d8:35:bb brd ff:ff:ff:ff:ff:ff promiscuity 0  allmulti 0 minmtu 0 maxmtu 65535
    vlan protocol 802.1Q id 10 <REORDER_HDR> addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 tso_max_size 524280 tso_max_segs 65535 gro_max_size 65536

If the interface isn't available at the OS-level upon configuration, the configuration will be automatically applied once the interface becomes available. Similarly, VLAN subinterfaces are automatically created as soon as their parent interface is available.
Closes #11

Thanks for this PR !
Testing it right now. As a first comment interface description needs to have its behavior adjusted:
r1# configure
r1(config)# interfaces interface eth1
r1(config/interface[eth1])# description my description
% unknown command
r1(config/interface[eth1])# description my_description
r1(config/interface[eth1])# show candidate
!
interfaces interface eth1
 description my_description
 type iana-if-type:ethernetCsmacd
 ipv4
 !
 ipv4 address <IP_ADDRESS>
  prefix-length 24
!
r1(config/interface[eth1])#
r1(config/interface[eth1])# description my description
% unknown command
r1(config/interface[eth1])# description "my description"
% unknown command
r1(config/interface[eth1])# description 'my description'
% unknown command
r1(config/interface[

A decision needs to be made :

Description after description keyword ends at the end of the line.
-> description my super long description
Description is surrounded by double quote.
-> description "my personal description"
Description is surrounded by double quote.
-> description 'my personal description'
Or no  in description which is not ideal.
-> Docs needs to be updated and explicitly mention this.

Should a maximum length need to be set for description field.

@frederic-loui Yeah that's a known limitation. The CLI is pretty primitive at this point, it doesn't support string values containing spaces. I think it would be a good idea to file an issue in the holo-cli repo to keep track of that problem.

Second comment: (using containerlab environment compiled with PR#19)

R6[holo] --- R7[freertr]
Configure R6[holo-router] Eth3@R6:

!
interfaces interface eth3
 description r6->r7
 type iana-if-type:ethernetCsmacd
 ipv4
 !
 ipv4 address <IP_ADDRESS>
  prefix-length 24
!

interface is effectively configured at holo:

460: eth3@if461: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether aa:c1:ab:e5:89:fd brd ff:ff:ff:ff:ff:ff link-netnsid 2
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth3
       valid_lft forever preferred_lft forever
    inet6 fe80::a8c1:abff:fee5:89fd/64 scope link
       valid_lft forever preferred_lft forever

--> First thing we notice is that the default MTU is set to 9500.

we set MTU to 1500:

r6(config)# show running
!
interfaces interface eth3
 description r6->r7
 type iana-if-type:ethernetCsmacd
 ipv4
 ipv4 mtu 1500
 !
 ipv4 address <IP_ADDRESS>
  prefix-length 24
!

ping from freertr->r6 (same setup was working using iproute2 command ipv4 address configuration)

rare#ping <IP_ADDRESS> vrf CORE
pinging <IP_ADDRESS>, src=null, vrf=CORE, cnt=5, len=64, df=false, tim=1000, gap=0, ttl=255, tos=0, sgt=0, flow=0, fill=0, alrt=-1, sweep=false, multi=false
.!!!!
result=80.0%, recv/sent/lost/err=4/5/1/0, took 1004, min/avg/max/dev rtt=0/0.2/1/0.1, ttl 64/64.0/64/0.0, tos 0/0.0/0/0.0
rare#

--> Shouldn't interface MTU default set to 1500 ?

A decision needs to be made :

Description after description keyword ends at the end of the line.
-> description my super long description
Description is surrounded by double quote.
-> description "my personal description"
Description is surrounded by double quote.
-> description 'my personal description'
Or no  in description which is not ideal.
-> Docs needs to be updated and explicitly mention this.

I think option #1 would be the way to go, that's how the "description" command works on most vendors.

Should a maximum length need to be set for description field.

Indeed, it would be good to define a maximum length. That can be done either using a YANG deviation or northbound validation callback. I'll think about that.

Shouldn't interface MTU default set to 1500 ?

Currently, if an explicit MTU isn't specified, the one learned from the kernel will be used. I think this behavior is good to accommodate users using holod solely for routing, and handling interface configuration separately.

no interface <INTERFACE-NAME> does not deconfigure the ip address.
Steps to reproduce: (example)

configure interface eth3 with ip address <IP_ADDRESS>/24 at holo level:

holo(config)# show running
!
interfaces interface eth3
 type iana-if-type:ethernetCsmacd
 ipv4
 !
 ipv4 address <IP_ADDRESS>
  prefix-length 24
!

at linux host level:

root@rt6:/# ip a show eth3
573: eth3@if574: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9500 qdisc noqueue state UP group default
    link/ether aa:c1:ab:c7:c8:98 brd ff:ff:ff:ff:ff:ff link-netnsid 3
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth3
       valid_lft forever preferred_lft forever
    inet6 fe80::a8c1:abff:fec7:c898/64 scope link
       valid_lft forever preferred_lft forever

ping test check from adjacent node

rare#ping <IP_ADDRESS> vrf CORE
pinging <IP_ADDRESS>, src=null, vrf=CORE, cnt=5, len=64, df=false, tim=1000, gap=0, ttl=255, tos=0, sgt=0, flow=0, fill=0, alrt=-1, sweep=false, multi=false
.!!!!
result=80.0%, recv/sent/lost/err=4/5/1/0, took 1018, min/avg/max/dev rtt=1/1.0/1/0.0, ttl 64/64.0/64/0.0, tos 0/0.0/0/0.0
rare#

deconfigure interface eth3

holo(config)# no interfaces interface eth3
holo(config)# commit
% configuration committed successfully
holo(config)# show running
!
holo(config)#

Problem: interface eth3 is still configured

573: eth3@if574: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9500 qdisc noqueue state UP group default
    link/ether aa:c1:ab:c7:c8:98 brd ff:ff:ff:ff:ff:ff link-netnsid 3
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth3
       valid_lft forever preferred_lft forever
    inet6 fe80::a8c1:abff:fec7:c898/64 scope link
       valid_lft forever preferred_lft forever

Adjacent router still pinging:

rare#ping <IP_ADDRESS> vrf CORE
pinging <IP_ADDRESS>, src=null, vrf=CORE, cnt=5, len=64, df=false, tim=1000, gap=0, ttl=255, tos=0, sgt=0, flow=0, fill=0, alrt=-1, sweep=false, multi=false
!!!!!
result=100.0%, recv/sent/lost/err=5/5/0/0, took 4, min/avg/max/dev rtt=0/0.6/1/0.2, ttl 64/64.0/64/0.0, tos 0/0.0/0/0.0
rare#

Configuring IP

holo(config)# show running
!
interfaces interface eth3
 type iana-if-type:ethernetCsmacd
 ipv4
 !
 ipv4 address <IP_ADDRESS>
  prefix-length 24
!

Before removing IP

655: eth3@if656: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9500 qdisc noqueue state UP group default
    link/ether aa:c1:ab:7a:4e:84 brd ff:ff:ff:ff:ff:ff link-netnsid 1
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth3
       valid_lft forever preferred_lft forever
    inet6 fe80::a8c1:abff:fe7a:4e84/64 scope link
       valid_lft forever preferred_lft forever

ping OK !

rare#ping <IP_ADDRESS> vrf CORE
pinging <IP_ADDRESS>, src=null, vrf=CORE, cnt=5, len=64, df=false, tim=1000, gap=0, ttl=255, tos=0, sgt=0, flow=0, fill=0, alrt=-1, sweep=false, multi=false
.!!!!
result=80.0%, recv/sent/lost/err=4/5/1/0, took 1032, min/avg/max/dev rtt=0/1.0/2/0.4, ttl 64/64.0/64/0.0, tos 0/0.0/0/0.0
rare#

Removing IP

holo(config)# no interfaces interface eth3
holo(config)# commit
% configuration committed successfully
holo(config)# show running
!

Check eth3 from linux host perspective

root@rt6:/# ip add show eth3
655: eth3@if656: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9500 qdisc noqueue state UP group default
    link/ether aa:c1:ab:7a:4e:84 brd ff:ff:ff:ff:ff:ff link-netnsid 1
    inet6 fe80::a8c1:abff:fe7a:4e84/64 scope link
       valid_lft forever preferred_lft forever
root@rt6:/#

-> Test have also been done with 802.1q VLAN and passed !

Is this behavior normal?
Other vendor tends:

to replace existing IPv4
or consider primary, secondary IPv4 address

holo(config/interface[eth3.666])# show running
!
interfaces interface eth3
 type iana-if-type:ethernetCsmacd
!
interfaces interface eth3.666
 type ietf-if-extensions:ethSubInterface
 parent-interface eth3
 ipv4
 !
 ipv4 address <IP_ADDRESS>
  prefix-length 24
 !
 ipv4 address <IP_ADDRESS>
  prefix-length 24
 !
 ipv4 address <IP_ADDRESS>
  prefix-length 24
 ipv6
 !
 ipv6 address fd00:2200::6
  prefix-length 120
!

2: eth3.666@eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9500 qdisc noqueue state UP group default qlen 1000
    link/ether aa:c1:ab:7a:4e:84 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth3.666
       valid_lft forever preferred_lft forever
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth3.666
       valid_lft forever preferred_lft forever
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth3.666
       valid_lft forever preferred_lft forever
    inet6 fd00:2200::6/120 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::a8c1:abff:fe7a:4e84/64 scope link
       valid_lft forever preferred_lft forever
root@rt6:/#

@frederic-loui Yes, that's the desired behavior. ietf-ip models the list of IP addresses using a simple list, without distinguishing between primary and secondary addresses. The Linux kernel doesn't have the concept of primary and secondary addresses either.
All protocol implementations are prepared to handle interfaces with multiple addresses. In the case of OSPFv2, the first received address will be considered to be the primary address used for protocol operation.

all lgtm !
PS: Please let me know when/if holo-yang would switch to a new version number (0.4.1 ?) so that I can bump holo-cli dependency.

Thanks, I had forgotten about that. Bumped to 0.4.1! It shouldn't be necessary to update holo-cli, as it currently depends on holo-yang = "0.4.0", which will include minor version updates such as 0.4.1.


docs: add a note about missing mocked network requests

What kind of change does this PR introduce?
Docs update
@icyJoseph

Coverage remained the same at 100.0% when pulling 15a05a2f2c689fae4967ef3bee7288af310ec110 on docs-jest-fetch into ef7a9ff25e472f0400c54625b8020ff7177f285b on master.


dbeaver/pro#2493 Change query to read Sybase procedures

Please check both Sybase instances (12 and 16) with the big script
And check separately Sybase EE and Sybase CE
And any Azure database (that procedures DDLs are still readable)

verified


Products Page should toggle between flavors

https://projects.invisionapp.com/d/main#/console/6565457/140910240/preview

That way user doesn't click Our Flavors, then clicks a product. Our Flavors will take them directly to Chocolate Chunk (the most popular), then they can click the top links to other flavors. Can load as separate pages.

This is a new feature. There won't be a products landing page. If you click Our Flavors, it will take you to Chocolate Chunk. But there will be links between flavors.


Default requests to limits in Workload

What would you like to be added:
If limit is specified, but the corresponding request is not, set request equal to limit.
Why is this needed:
This is the defaulting that k8s API does for Pods, but that wouldn't apply until the Pods are created.
https://github.com/kubernetes/kubernetes/blob/42a5eb48184547465ef4be962af2a07422311f82/pkg/apis/core/v1/defaults.go#L149-L177
Completion requirements:
This enhancement requires the following artifacts:

[ ] Design doc
[ ] API change
[ ] Docs update

The artifacts should be linked in subsequent comments.

/assign


resolve 'NODE_ENV' is not recognised when running test in windows

fix the error when npm test show
'NODE_ENV' is not recognised as an internal or external command.....
This PR resolve #169 and #162 , so whose who are running npm test in Windows OS would be fine!! :smiley::smiley:

Pull Request Test Coverage Report for Build 416

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 38.725%

Totals

Change from base Build 415:
0.0%

Covered Lines:
116

Relevant Lines:
240

💛  - Coveralls


Error: read ECONNRESET

Hello guys.
When I try to connect to my server, it says that I'm connected but a few second later I have this error: "read ECONNRESET".
My ftpconfig is correct so I don't know why I got this :/
Thank you for your help !

Having the same issue, spent the last 3 days trying to find an answer. Any luck fixing error?

I also have this issue, Ihave tried different ftp upload/download packages they all failed.
The probleme may be somewhere else.

Changing the name of my folder I was trying to connect did the trick.

@samwyness Can you post the folder name to give us a hint?

@jpxd I changed the theme folder I was trying to upload.

I've the same issue, my ftp works well on chrome, but in atom I got this "Remote FTP: Error: read ECONNRESET" , any one can help us ?

This is also happening to me. I have opened: https://github.com/mgrenier/remote-ftp/issues/595

I was also having this issue. Turns out the server I was using didn't support SCP/SFTP, so I had to do it over plain old vanilla FTP. Working fine, now.

i am able to connect when on linux but when i try logging on using windows i get that error too

After update Remote-FTP to latest version - not connect to any host with error ECONNRESET - in other ftp clients all works fine.

Same

@gahmed92 @jpxd Also check https://github.com/yongkangchen/remote-sync/issues/343 it seems that the issue could be related to specific hosting providers.
I have the same issue as per #343, but only on Win10.

conversation locked, see #585


Create a new pull request by comparing

Pull Request Test Coverage Report for Build 432179545

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 94.332%

Totals

Change from base Build 429455779:
0.0%

Covered Lines:
1884

Relevant Lines:
1951

💛  - Coveralls


docs(tutorial): rename tutorial subsections

Signed-off-by: kminoda<EMAIL_ADDRESS>Description
Although the readers expect the tutorial page to be a "tutorial" for total Autoware beginners, the title of the subsections in the tutorial may be not descriptive enough.
For example, it is confusing to the readers that two pages with the exact same name of "planning simulation" exist both in the "Adhoc simulation" and "Scenario simulation" sections, because:

readers may misunderstand "Adhoc simulation > planning simulation" and "Scenario simulation > planning simulation" as two independent functions, whereas the latter one is dependent on the former one
the words "adhoc" and "scenario" themselves are (IMHO) not that common

This PR aims to provide more concrete titles for these subsections to clarify the goal of each page. To this end, I propose to rename the title of subsections as follows:

Adhoc Simulation -> Simulating Autoware

Planning simulation -> Using a planning simulation
Rosbag replay simulation -> Using a rosbag replay simulation
Digital twin simulation -> Using a digital twin simulation

Scenario Simulation -> Running a scenario test

Planning simulation -> Running a scenario test with a planning simulation
Rosbag replay simulation -> Running a scenario test with a rosbag replay simulation
Digital twin simulation -> Running a scenario test with a digital twin simulation

I believe, with this modification, the difference between "adhoc simulation" and "scenario simulation" will be more clear to the readers.
Any comments are welcome including the improvement of the rename.
(Also, I think it is also common to start the title of the pages in tutorial section with "[verb]ing ~" in ROS community. ex: ROS tutorial, ROS2 tutorial)

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The Reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

Since simply this is a problem with English technical writing, I'll leave the decision to Lalith-san.

I will leave this as a draft until https://github.com/autowarefoundation/autoware-documentation/pull/124 is merged.

I will leave this as a draft until #124 is merged.

#124 is now merged!

@LalithVipulananthan I appreciate it if you could give me some feedback on this PR. Thanks!

@LalithVipulananthan I appreciate it if you could give me some feedback on this PR. Thanks!

Hmm. I see the reasoning behind making the changes, but even if we make these changes, I feel that someone will still ask "So what's the difference between Simulating Autoware and Running a scenario test?". I also note that we refer to "scenarios" in the scenario_simulator_v2 documentation, so if the word is considered to be uncommon then perhaps it is something that we can define in one of these tutorials.
We could potentially split these into Basic simulations and Advanced simulations? Possible overlap with #126 though, as we would have basic and advanced tutorials, then basic and advanced simulations within the basic tutorials section. 😅

Thank you for the comment!
First, the subtitle Simulating Autoware may be inappropriate. Maybe something like Running simulations is better.
I agree that Basic simulations and Advanced simulations is better than the current one in the main branch, but it is still confusing since they seem to be two parallel concepts, while in reality "scenario planning simulation" is built on "planning simulator (=adhoc planning simulation)".
I didn't mention it in the description, but I think that "Scenario Simulation" or "Running a scenario test" should be eventually moved to "How-to guides" section, since it is not for total beginners (e.g. a student or some researchers in University who are completely new to Autoware) but rather for intermediate users (e.g. autonomous driving researchers or engineers who already have developed their algorithms based on Autoware and want to perform a quantitative evaluation on a scenario basis to maintain reproducibility).
If the above is achieved and "Simulating Autoware" and "Running a scenario test" is no longer in the same page, then I think that the question So what's the difference between Simulating Autoware and Running a scenario test won't arise.

Unfortunately, I do not have a suggestion that I am 100% happy with, but how about this?

Autoware Simulations

Using the Planning Simulator
Using the Rosbag Replay Simulator
Using the Digital twin Simulator

Autoware Scenario Tests

Running a scenario test with the Planning Simulator
Running a scenario test with the Rosbag Replay Simulator
Running a scenario test with the Digital Twin Simulator

@LalithVipulananthan (Apologies for forgetting to respond to your comment)
Thanks for the suggestion! That also looks good to me. I've reflected that comment at https://github.com/autowarefoundation/autoware-documentation/pull/127/commits/003895393879ee7e22425f11722ecd32bf62f568.
Any further comments on this? (cc. @kenji-miyake @soblin @shmpwk )

@kminoda Thank you for your proposal, but I don't understand the points well.

For example, it is confusing to the readers that two pages with the exact same name of "planning simulation" exist both in the "Adhoc simulation" and "Scenario simulation" sections, because:

You can change the name, but as a fact, the "planning simulation" exists in both of them.
Also, I've explained the definitions of "Adhoc simulation" and "Scenario simulation" at the top page. There is a matrix of simulation patterns.

the words "adhoc" and "scenario" themselves are (IMHO) not that common

But surely there are the concepts of "adhoc" and "scenario".

This PR aims to provide more concrete titles for these subsections to clarify the goal of each page. To this end, I propose to rename the title of subsections as follows:

I'm confused with this proposal.
Why scenario test isn't named simulation even though it uses simulations? :thinking:

@kenji-miyake Thanks for the comments!
I understood that defining adhoc and scenario simulation in a similar way is reasonable so I would close this PR. I would instead consider proposing a better way to describe the difference between those two simulations.


advanced query result title looks bad

when I use advanced query and specify the title, the title in the result looks bad. some text is overlapped by the title.
here is the demo query to reproduce the problem.
#+BEGIN_QUERY
{
    :title [:h2 "🔨 doing"]
    :query [
        :find (pull ?b [*])
    ...
}

if I use h1,

Same problem here.
I think the questions should not be "Is people should or should not use custom title in advanced query".
The fact is the feature is available. So as far the feature is available, no doubt that people will use it.
I personally use advanced query to manage complex data consolidation that help me on a daily basis.
I have a kind of summary pages where several queries are setup. Each advanced query can be position at different indentation level base on my personal needs and the way I want to consolidate datas.
Having this custom title compatible with heading level is not a nice to have for me, this is a must have.
HTH

just to add my 2 cents, I think the question here is to relocate the " x results' text at the right of the title instead of bellow.


Add dependence on Lexicon

Simply cloning this package was not enough. I also needed to Pkg.add("Lexicon").
That should be added as an explicit dependence (however that works in Julia these days).

Actually, remove Lexicon at all, but added StatsBase to a new REQUIRE file.