MacOS: Fix stretched mode in fixed display mode with gpu

I think this is similar to how JOGL handles DPI scaling on macs but not on other OSs, but I'm not really sure.
Fixes #13804
Fixes #14513 (which is a duplicate of #13804)

In exchange for fixing stretching in fixed mode, it seems that this PR breaks the ability to correctly switch from a stretched resizable mode to a stretched fixed mode. Unfortunately, I can't figure out how to fix one without breaking the other.
I think it's a good tradeoff, but not everyone may agree.

I found/pushed a solution for the issue the previous commit introduced, but at this point, this PR feels more like a workaround than a bugfix. 😓

fixed in bb43d232bb594c6e062e3342fa7db1b53f594c11


Nightly formatter removes multi line comments in extern blocks

Describe the bug
If I have A multi line comment in an extern block preceding a function declaration, it is removed. But not a single line comment.
To Reproduce
If I have this code:
extern "C" {
    // A comment that is
    // spread out over
    // multiple lines
    fn a();

    // A single line comment
    fn b();
}

And format it with the nightly formatter. I end up with:
extern "C" {
    fn a();

    // A single line comment
    fn b();
}

Expected behavior
I expect both comments to be retained. As far as I know it's not invalid or unidiomatic to write a comment multi line comment on an extern declaration.
Meta

rustfmt version: rustfmt 1.4.26-nightly (293d7d0 2020-11-14)
From where did you install rustfmt?: rustup
How do you run rustfmt: cargo +nighty fmt

Duplicate of #4528

Sorry, did not find that one when trying to look for a duplicate. Great it's being worked on already :+1:

No worries!


admin ui

check:

https://www.creative-tim.com/product/material-dashboard-react
https://www.creative-tim.com/product/vue-light-bootstrap-dashboard
https://www.creative-tim.com/product/paper-kit-2-angular
https://www.creative-tim.com/product/light-bootstrap-dashboard-react
https://www.creative-tim.com/product/now-ui-dashboard

more here https://github.com/creativetimofficial

https://tabler.github.io looks good

other related content located here https://github.com/kamilsk/form-api/issues/71

will be a part of client package


Broken link FIxed

#sign-off

#hold-off (premature sign-off)

Unfortunately, because the very first change in many files is the automatic conversion of a newline char, the remainder of the diff in those cases makes it appear that the entire file has changed. That makes it impossible to see the actual change(s). So that issue compounded with the fact that 113 files have been changed in this PR (which is a lot) makes this PR really difficult to verify.
I can approve it if necessary, but unfortunately the way it is I can't verify the links.
Alternatively, if you prefer, you could take a first pass through all the files making just any old change (for example adding a newline to the end of the file), and then I'd be happy to approve that if you describe what you've done. After that take another pass through, say, 10 files at a time making the actual link fixes. That would solve these two issues: a) it'll make the actual, real changes to the files show up in the diff, and b) it'll be more manageable for approvers signing off on the changes.
Thanks!
Steve

So, I'll go ahead and approve, and merge this one. :) In most cases, I can't actually see the change in order to verify it, but let's clear this one because then going forward we won't have the ^M issue, and we'll be able to see changes.
Thanks!
Steve

@v-rajagt : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@v-rajagt : Thanks for your contribution! The author(s) have been notified to review your proposed change.


It would be helpful to include the B series in the list above.

We are standing up a sandbox SQL Server in Azure for development and testing purposes.
We are likely to use a burst / B series VM as it better fits the budget for this need.
The B series is not currently included in the ACU performance list.
It would be helpful to bring this up to date.

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

ID: 53b9177e-fd0f-84ce-f02e-b32c04e1217c
Version Independent ID: b44a31b5-5fe9-9e03-08f6-709aa90cffeb
Content: Overview of the Azure Compute Unit
Content Source: articles/virtual-machines/windows/acu.md
Service: virtual-machines-windows
GitHub Login: @jonbeck7
Microsoft Alias: jonbeck

@SteveMinar Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

#in-progress

#please-close @SteveMinar I've checked with engineering and the ACU is somewhat variable because of the type of SKU that it is, so the burstable sizes don't have a stated ACU.

@cynthn that's useful information, but we just got a support request asking for the info. To prevent further confusion, can we add an explanatory note about the B series to the document directly? Thanks!


support the all option in the kill command.

relates: https://github.com/containers/youki/issues/531
cc: @guni1192

:rocket:


FMUv4 voltage scaling

@kd0aij Do you have a power module? Is the scaling wrong?
https://github.com/PX4/Firmware/blob/master/src/modules/sensors/sensors.cpp#L855

If we're talking about the new 8S ACSP4, I'm sure the scaling is different from the 3DR module.
I'll validate this when I get a chance to install an R12 and ACSP4 in a quad. I think Phil has already calculated and verified the scale factor.

@pkocmoud Users report incorrect voltage readings. So I really need to know what the right scales are (and this is another thing that dropped, because I don't recall signing off on the final scaling values or having a chance of discussing it with the community).

I'm seeing voltage_battery=0 in SYS_STATUS with ACSP4 connected using only one cable.
The BATTERY_STATUS message is all zero and -1, so it must not be getting updated.

Normal customers seem to get voltage out. Can't comment without hardware.

just measured voltage sense output of 742.7mV for input of 10.01V to ACSP4
ratio is .0742
full scale would be about 44.5V
8S is 8*4.2 = 33.6V max
But the firmware shows vehicle_status.voltage_battery = 0

What is the scaling for current?

I fixed it myself now in b2237ce.


Handle failing tests for build command

resolves #3597
Description
This PR add additional edges to the DAG representation of node dependencies for a compiled project. It "just works" with how node selection is designed. The major takeaway here is we want a given node to depend on tests belonging to any upstream nodes. The caveat is that the test can only depend on nodes that are upstream of the given node in order to create this dependency, else this could open up the possibility of circular dependencies (ew, we love DAGs). This ensures that when running tasks that execute multiple different types of resources (dbt build), models will depend on all upstream dependencies having passing tests, else it will be skipped during execution.
Checklist

[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have updated the CHANGELOG.md and added information about my change to the "dbt next" section.

I've put this through a lot of testing locally, but would love some help making sure this covers all use cases. Please call out any specific use cases we should add some automated testing for as well!

This all looks great @kwigley!  My only concern with this approach (and the reason I didn't use something similar) is that doing a lot of graph re-creation may chew through more CPU than we'd like (especially given networkx doesn't utilize multiple cores IIRC).  Have you A/B tested this on some large  project a-la internal-analytics?  Might be worth checking so we know what to expect.

This looks really good! And excellent comments too.
I do wonder if we could store information in the nodes so that we don't have to loop through the entire list of manifest nodes, but that's something we can look at in the future.

@gshank I agree, there is room for refactor. This leads to my only concern that @iknox-fa noted, perf. I'll get a sense of timing and report any further concerns.


UPS api request failed: Invalid Authentication Information. (250002)

Hello @rawilk
Giving the exact correct credentials I'm facing the following issue in the shipping API

Solved


FTexture::generateMipmaps assertion is too restrictive

The assert inside FTexture::generateMipmaps is too restrictive:
// The OpenGL spec for GenerateMipmap stipulates that it returns INVALID_OPERATION unless
// the sized internal format is both color-renderable and texture-filterable.
if (!ASSERT_POSTCONDITION_NON_FATAL(isColorRenderable(engine, mFormat),
        "Texture format must be color renderable")) {
    return;
}

Metal is able to reshape texture formats into 3 components. We should probably move this assertion into the OpenGL driver.

@pixelflinger thoughts on moving it to the OpenGL driver?

Instead of moving it to the driver could we add an isMipmappable() or something that would return a value driver-specific?

Yeah, I think that could work too.


Replace getcurpos with getpos to support older Vim

getcurpos() was added from Vim 7.4.313, so it's not available in older
versions (For example, RHEL/CentOS 7 comes with Vim 7.4.160).
Replace getcurpos() with getpos('.') which is no different for this
plugin.
Fix for #190

Ok, thanks

i just meet this issue, thx!


python38Packages.micawber: 0.5.2 -> 0.5.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python38Packages.micawber is: "A small library for extracting rich content from urls"
meta.homepage for python38Packages.micawber is: "https://micawber.readthedocs.io/en/latest/"
meta.changelog for python38Packages.micawber is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.5.3 with grep in /nix/store/nwkwp5x8hdxlx21rwxhc8x8yx4cph78n-python3.8-micawber-0.5.3

found 0.5.3 in filename of file in /nix/store/nwkwp5x8hdxlx21rwxhc8x8yx4cph78n-python3.8-micawber-0.5.3

directory tree listing: https://gist.github.com/3ad039e56440020ac74a1cacaeb15ae1

du listing: https://gist.github.com/5f9c808a20262b1fe408ce9df5df85d3

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

8 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
2 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
python38Packages.micawber
python39Packages.micawber

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/nwkwp5x8hdxlx21rwxhc8x8yx4cph78n-python3.8-micawber-0.5.3 \
  --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 python38Packages.micawber https://github.com/r-ryantm/nixpkgs/archive/91e5e5a0dda117ed4532d1a4f4a2b1bf17b93420.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/nwkwp5x8hdxlx21rwxhc8x8yx4cph78n-python3.8-micawber-0.5.3
ls -la /nix/store/nwkwp5x8hdxlx21rwxhc8x8yx4cph78n-python3.8-micawber-0.5.3/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

2 packages built:

python38Packages.micawber
python39Packages.micawber

Maintainer pings
cc @davidak for testing.

Result of nixpkgs-review pr 117706 at 91e5e5a0 run on aarch64-linux 1

2 packages built successfully:

python38Packages.micawber
python39Packages.micawber

Result of nixpkgs-review pr 117706 run on x86_64-linux 1

2 packages built:

python38Packages.micawber
python39Packages.micawber


Header/Footer Html

Is it possible to directly put Html for HeaderSettings, FooterSettings as-well? now it is only possible to link via HtmUrl.

Is not possible to pass HTML directly to the Header and Footer settings. For more details see issues on wkhtmltopdf page:

2879
2280

I can live with setting the header via HtmUrl, but is it possible to set the header height? It seems to be fixed.


[explore]filter custom SQL editor is broken, adding undefined clause

latest master 11pm 1/4/2021
this is a further regression of what we encountered during the holiday.

last week on master

@kgabryje P1 issue, release blocker. please address it asap. 🙏

I am unable to repro the undefined undefined problem on master, but did notice that writing a custom filter doesn't enable the Save button unless the simple filter has been populated (see pic below). I'll work on fixing that, now.

I am unable to repro the undefined undefined problem on master, but did notice that writing a custom filter doesn't enable the Save button unless the simple filter has been populated (see pic below). I'll work on fixing that, now.

Confirming this issue is resolved in latest master 01/09/2021 @ 6:38pm (UTC)
cc @graceguo-supercat @ktmud @zuzana-vej @mistercrunch

Confirming this issue is resolved in latest master 01/09/2021 @ 6:38pm (UTC)
cc @graceguo-supercat @ktmud @zuzana-vej @mistercrunch


Create .env file for the ports

[ ] - A new, gitignored file called/dev-overrides.env will allow developers to override env variables in development environment.
[ ] - This override system should not affect test environments.

For example, if dev.env contains:
FOO=1
BAR=2
BAZ=3

And dev-overrides.env contains the following:
FOO=2

Then the result will be
FOO = 2
BAR = 2
BAZ = 3

This is being worked on by Kharak.


Use rhel-9-golang-1.20-openshift-4.14 as a builder image

/hold
Requires https://github.com/openshift/release/pull/41142

Will be addressed in https://issues.redhat.com/browse/CORS-2750

Requires https://github.com/openshift/release/pull/43307

/retest-required

/retest-required


Inter-annotator agreement

An interesting question when choosing sentences from the COWLH2 corpus is: what to do with the different annotators. Perhaps for now, we could just choose the annotations which both annotators put in (to reduce noise). We are not data hungry in this case.

Annotator1 has annotated much more, and much more consistently it seems (at least in all most of the mismatches, the mismatch is due to a mistake by Annotator2). So perhaps just use Annotator1?


Question: Can I use the reserved  field inside desc?

I'd like to extend the functionality of memory desc to store some info, about several bytes. Can I use the reserved for that purpose? I know that one day this might come into conflict with DNNL's design, but for the short term, am I supposed to use these 200 bytes from high address (reserved[199]) or from low address (reserved[0])?

Hi @pinzhenx,
Could you please share some insights on what you are trying to achieve?
In general, the reserved areas are not designed to store additional information, as the library can (in theory) override it with 0 during the initialization. It also might break the comparison function, as it is unclear if the same memory descriptors with only difference in un-interpret-able reserved should be treated as the same or not (currently it would be treated as the same).
Leaving all these cautions aside, I don't see any technical problems though -- e.g, if you want to do some quick experiment or so. Please find my comments on the approach below.

I see the reserved[200] belongs to the dnnl_rnn_packed_desc_t structure, that is a part of the union:
 937 typedef struct {
 ...
 970     /// Memory format kind.
 971     dnnl_format_kind_t format_kind;
 972     union {
 975         dnnl_blocking_desc_t blocking;
 977         dnnl_wino_desc_t wino_desc;
 979         dnnl_rnn_packed_desc_t rnn_packed_desc; // <-- part of
 981     } format_desc;                              //     this union
 982
 983     dnnl_memory_extra_desc_t extra;
 984 } dnnl_memory_desc_t;

This mean that depending on the format_kind the memory descriptor can not use rnn_packed_desc but, say, blocking descriptor.
However, dnnl_memory_extra_desc_t field is always available, which also has char reserved[64]:
 920 /// Description of extra information stored in memory
 921 typedef struct {
 922     /// The flags contain arbitrary extra information, such as compensation.
 923     /// @sa dnnl_memory_extra_flags_t
 924     uint64_t flags;
 925     /// Compensation mask
 926     int compensation_mask;
 927     /// Scale applied to the data
 928     float scale_adjust;
 929     /// For future backwards compatibility
 930     char reserved[64];
 931 } dnnl_memory_extra_desc_t;

We currently don't use either reserved bits, but the plan is that if we need something, we will add a field and shrink the reserved buffer. Hence the safest way would be to use something like:
size_t required_size = 2; // e.g. you need 2 bytes of space
size_t reserved_size = sizeof( ((dnnl_memory_extra_desc_t *)0)->reserved );
assert(reserved_size >= required_size);
size_t offset = reserved_size - required_size;
md.extra.reserved[offset] = (uint16_t)data;

I checked the way we compare memory descriptors -- we check field by field, so even if there would be some unknown information in reserved area of extra field we will ignore that. This may be a desired or not desired behavior for you. Please pay attention to that.
Also, please note, that init_memory_desc() or similar functions first zero the resulting memory descriptor. So, be careful to not lose the information.
Apart from that I don't see why this idea would not work.
Needless to say, I don't recommend doing that, though. 😅

Hi @emfomenk
Thanks for your guidance. What I'm trying to do is to hide the difference of grouped weights from the framework, i.e., not let the framework perceive the change in weight dimensions.
From the perspective of DNNL, a grouped 4d weights is basically a plain 5d memory. But if I got a 5d memory, how can I get this 'grouped' info back?
So now I need some extra info, under current tag-free design, to indicate if a memory is grouped or not.

Hi @pinzhenx,
Thanks for the explanation! Though, I am still slightly confused: from the memory organization perspective (read memory format) there is no difference between regular 5D tensor and 4D weights for grouped convolution (which leads to the 5D tensor as well). So, the only place where you need to know whether a tensor represents 4D weights w/ groups or 5D activations is typically somewhere closer to the convolution operation itself. But in this case you already know what kind of the tensor it is, since you work on the operation (sorry for the pun).
I guess, you use some form of an abstraction (to simplify the programming DNNL), but I am not sure I understand why exactly you need that / what problem you are solving. I would appreciate if you elaborate on this more.

From the perspective of DNNL, a grouped 4d weights is basically a plain 5d memory. But if I got a 5d memory, how can I get this 'grouped' info back?

Our idea was that the memory descriptor and memory format don't have any semantics attached to the memory itself. Their sole purpose is to describe physical layout in memory address space. We hoped that all the semantics would be carried by the upper level application.
So, my answer on your question is:

You either look at the convolution configuration for which these weights come from and derive whether it is grouped 4D weights or proper 5D weights;
You have your own tensor meta data that encapsulates DNNL memory desciptor, but carries any additional required information, such as the purpose of the tensors (e.g. weights or activations), the number of logical dimensions (if your framework consider groups as not an additional dimension) and whatnot:my_fwk_tensor_descriptor_t {
    tensor_type type; // activations or weights
    int logical_dims; // 4 even for grouped weights, if FWK treats
                      // weights like [ G * OC / G, IC / G, KH, KW ]
    dnnl_memory_desc_t dnnl_md; // data for DNNL
};


Move aws_smithy_http::operation::error::BuildError into aws-smithy-types

Motivation and Context

Description
A draft PR till all tests have been confirmed to pass.
Testing

Checklist

[ ] I have updated CHANGELOG.next.toml if I made changes to the smithy-rs codegen or runtime crates

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

do you think this makes more sense in aws-smithy-runtime-api

Yeah, that distinction is blurry to me. For things like BuildError in particular, I don't have a guiding principle of which crate is a better home.


the script can't read some files

here's the error:
[11:35:02]@swing • Could not read file: /home/hananelroe/anaconda3/envs/3dRenderer/lib/python3.1/site-packages/scipy/io/tests/data/test-8000Hz-be-3ch-5S-24bit.wav
[11:35:02]@swing • Could not read file: /home/hananelroe/anaconda3/lib/python3.9/site-packages/scipy/io/tests/data/test-8000Hz-be-3ch-5S-24bit.wav
[11:35:02]@swing • Could not read file: /home/hananelroe/Desktop/phone backup/Music/רכבת לילה לקהיר.mp3
[11:35:02]@swing • Could not read file: /home/hananelroe/anaconda3/lib/python3.9/site-packages/scipy/io/tests/data/test-44100Hz-be-1ch-4bytes.wav
[11:35:02]@swing • Could not read file: /home/hananelroe/Desktop/phone backup/Music/כמה הייתי רוצה.mp3
I thought that some of it might be because the filenames are in hebrew, but it managed to read most of the hebrew files.

The files are most probably broken and their metatags can't be read. You won't see these audio files in the app.

but I know they aren't broken because other apps are able to play them...

That's interesting. I'll investigate with some of my files and see what's going on.

if you'd like i could send you the faulty file(s)

That would be nice. Send them over. Thanks

We'll check them out. Thanks


add try catch to decodeURIComponent call

This is to prevent our server from throwing when we pass in a malformed url into the router. Currently when the URL path is malformed we are not catching the error which is causing a 500 error instead of a 404.

Coverage decreased (-0.3%) to 94.515% when pulling 1ba91e347f2e3f947da2dda713570723a750d861 on GhostGroup:bug/add-try-catch-to-decode-uri-call into 08e8bbeaa76c5ec194abea388a193bedac7f35fc on fridays:master.


please change license

Others are reselling your code/components and closing the source code. Please ensure any derivatives of your source/license modified or otherwise should always retain your name and stay open source.
Also it would be great if you can sell some basic themes for ASP MVC 5 Admins sites, with identity built in, that would benefit everyone.

could you please send me an email (found at the end of this page) providing links to the places where others resell TwitterBootstrapMVC?


Return to list of publications/datasets after wizard should sort by creation date?

Describe the improvement
After adding one or more publications or datasets,
you are redirected to your list of publication/datasets,
but .. those are sorted by (publication) year.
Shouldn't that be sorted by "Added (newest first)".
That way you are reminded of your own recent
additions.
@sdebodt

@nicolasfranck as discussed yesterday in the meeting, it would be useful to have a sorting in which the recently added publication/dataset appears on top of the list. I use "Updated (newest first)" as then I also have the publications/datasets edited recently in the beginning of the list.

@nics I see that the backend already has a default sort: ["date_updated.desc", "year.desc"]. Which is more advanced than what we can get by selecting Updated (newest first).
When no sorting option is selected, the first element in the list is shown, i.e. Year (newest first),
which is not the one selected, but the first element just happened to be on top.
biblio-backend does not know what librecat is choosing as its sorting option.
Either way, a few things are needed:

let the biblio-backend decide what the default is?
or let librecat return what the choosen sort option was, so it can be "injected" in the url query, as if the user selected this?
the list of sort options should be a controlled list of options, not
just a list that one happens to select correctly. That also gives
use the opportunity to add further underlying sorting. e.g. when you
sort on year, then sort on updated, then ..


Cannot declare a dictionary with option type

Describe the bug
When trying to declare a dictionary variable, trying to use the option type results in a repeating loop of confusing syntax errors of either 'identifier is expected' or '',' is expected'. It looks like the compiler is accepting the option type, but doesn't know how to handle the option members, or lack there of, maybe the commas between option members is the cause.
To Reproduce
Declare a dictionary variable like the following
OptionByGuid: Dictionary of [Guid, Option] // Syntax error, identifier is expected (at ']')
OptionByGuid2: Dictionary of [Guid, Option "a","b"] // Syntax error, ',' is expected (at ']')

Expected behavior
Either the compiler should disallow option types in dictionaries (i.e. 'The type 'Option' cannot be used as a type argument in this context.'), or the option type should be allowed (with or without members, probably without)
Version

AL Language: 5.0.254558
Business Central: AU Business Central 15.3 (Platform 15.0.40073.40791 + Application 15.3.40074.40822)

Hi @shuyusheng,
Have you tried using enums?

Hi @shuyusheng,
Have you tried using enums?

Yes, dictionaries with enums work fine.

Is there any reason to not use enums? Considering the number of requests and our capacity, it might take a long time until we get to look at this issue.

Is there any reason to not use enums? Considering the number of requests and our capacity, it might take a long time until we get to look at this issue.

We have been using enums so no rush


"Options" button only works once

When the site loads, clicking "options" on one of the contacts shows a menu with two links and a button. If I do one of the following:

Delete a contact
Edit a contact
View a contact (and then click "back")
Then the options buttons no longer have an effect. No error shows in the console. This happens for me in both Firefox and Chrome (Mac).

Great htmx example, though. :)

Hey @JonathanHarford, thanks for reporting this bug! It's fixed in the latest commit.


Possible to prefix version number with tilde? (~)

Is it possible to prefix version numbers in the package.json file with a tilde, indicating it can use any patch version of that package?
Thanks!

@ashleyw hey, how about I add an optional commandline parameter --tilide  and this will in turn make all package numbers tlide if I understand correctly for example:
this:
"dependencies": {     "commander": "2.11.0",     "yarn-lock-convert": "1.0.2"   }
would become:
"dependencies": {     "commander": "~2.11.0",     "yarn-lock-convert": "~1.0.2"   }

I think, changing the regex currentVersion.match(/(^[\^><=]+)/); to currentVersion.match(/(^[~^><=]+)/); would be fine.
See https://github.com/npm/node-semver/blob/master/README.md#tilde-ranges-123-12-1
Thanks in advance.

Hi, very useful project, it's upsetting that yarn doesn't have something similar build-in :(

Hey since i accepted the pull request i will close this issue. Feel free to reopen if needed.


default option model terminate early when stuck

yeah I remember that too, I couldn't find it. we must have removed it at some point


fix SIGSEGV in is_connected() when no system is connected

Fixes an issue in which if an application (e.g., offboard_velocity) is started
before the simulator is started, a segmentation fault is caused because it
tries to dereference a null pointer.
Signed-off-by: Gabriel Moreno<EMAIL_ADDRESS>

I'm not sure why jenkins chas somehow changed from branch to pr-head again, I'll ignore it for now. @dagar thoughts?

You're probably only seeing branches for PRs that have a branch off the main repo.
It's a setting here. http://ci.px4.io:8080/job/Dronecode/configure

Thanks for your response @dagar. It looks like the Jenkins settings have changed quite a bit as well, maybe that's why it stopped working. Or maybe the difference is that this comes from a fork. I'll play around and see.


Display referenced resources in the dashboard

I think it would be pretty useful to see what resources a resource is referencing in the dashboard.
builder.AddProject<Projects.MyFrontend>("frontend")
       .WithReference(basketService)
       .WithReference(catalogService.GetEndpoint("http"));

In the example above, the frontend resource would have two references. A reference would have:

Resource name, e.g. catalogservice
Endpoint name, e.g. http
Value - URI string?, e.g. http://localhost:5653/

The resource model today doesn't have references, just the env vars used by the app. You could try to reverse engineer references by looking at environment variables, but it would be a pain in the butt. It is much easier to model it explicitly and display values from the model.
Edit: We could also display the reverse. What resources reference the current resource, e.g. basketservice is referenced by frontend and apigateway.
In the UI, call it dependencies and used by? That's what NuGet does:

Dependencies - https://www.nuget.org/packages/Grpc.Net.Client#dependencies-body-tab
Used by - https://www.nuget.org/packages/Grpc.Net.Client#usedby-body-tab

Note: I looks like the app model doesn't have this information (just env vars are added).
It would need to be added to the app model, returned in the resource service, the added to the resource detail UI.

cc @davidfowl @DamianEdwards

Here is the original issue and PR for modeling dependencies:

https://github.com/dotnet/aspire/issues/183
https://github.com/dotnet/aspire/pull/1138

This is the latest PR: https://github.com/dotnet/aspire/pull/2594. The goal is to move to a richer way of modeling references in things like environment variables and connection strings. Are you thinking we only show connection string references and endpoint references or more?

Also related https://github.com/dotnet/aspire/issues/1436

cc @IEvangelist was interested in this as well.

Yeah, I had imagined that we should display a visual representation of the network topology.

This was drafted up with mermaid, assuming that we might want to use that in the dashboard. I wrote a Razor library POC to test out using mermaid.js, with the idea that it might be used for something like this. Ideally, we could either query the App Model or maybe even the manifest. With the dependency graph and some other runtime data, we could create a mermaid chart and render it like that. All of this was just an idea though...

Love this thought / direction and it would be super helpful!!!

Remaining work here is to add a graph view of resource relaitonships.


changed type definition of HttpCollectionCreateReq

while using httpclient to create collection just by passsing "collectionName" which is the only required field, I was getting Collection.collectionName is required error, then I passed  config dbname and collectionName error disappears and getting dimension is required error. I updated HttpCollectionCreateReq type definition to work right out of the box with the correct required fields.

False alert, It was an object prototyping issue from the graphql Object.


Actual changelog. Pls read

Ninja: Disabled. Idk how to do it and can't build with it enabled due to gauge issues.
Fixes:
Reaper: Added executioner skills & reorganized a bit.
Samurai: Added level checks since positionals used to appear when they shouldnt & reorganized a bit.
Dragoon: Fixed positionals. Reorganized a a bit.
Viper: Typo

Thank you!


Application Services Service must override exists() to build proper uri

The uri for a service object on the BigIP follows the convention <base_uri>~<partition>~<<service_name>.app>~<service_name>
This must be built in the exists function, just as it is done in load. Implementing the override and the tests to keep 100% coverage.

Closed by PR #243


Feat: ADDING GSAP ANIMATION TO NAVBAR | GSSOC_EXT | LEVEL 3

Describe the feature
i wan to add smooth animation to navbar when the website is loaded for the first time
please assign this to me
Add ScreenShots
NA
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a gssoc-24-extd contributor
[X] I want to work on this issue

@Hamza1821 Which type of any example

I am talking about some sliding down animation to navbar with stagger effect

actually we are going to implement our new UI so nor need for now


Hijack.Host warning from MalwareBytes

Microsoft PowerToys version
0.64.0
Installation method
Microsoft Store
Running as admin
Yes
Area(s) with issue?
Hosts File Editor
Steps to reproduce
This morning while booting up Windows MalwareBytes did the scheduled scan in the background and warned about a file hosts takeover.
scan.txt
✔ Expected Behavior
Avoid false warning for File Host editing
❌ Actual Behavior
No response
Other Software
Windows 10 x64 22H2 build 19045.2194

did you tweak your host file?  /needinfo

Hi Clint, yes! I am sorry I forgot to include that.
This is what it looked like before editing, and I can't remember when I added those lines!
`# Copyright (c) 1993-2009 Microsoft Corp.

This is a sample HOSTS file used by Microsoft TCP/IP for Windows.

This file contains the mappings of IP addresses to host names. Each
entry should be kept on an individual line. The IP address should
be placed in the first column followed by the corresponding host name.
The IP address and the host name should be separated by at least one
space.

Additionally, comments (such as these) may be inserted on individual
lines or following the machine name denoted by a '#' symbol.

For example:

localhost name resolution is handled within DNS itself.
Start of entries inserted by Spybot Anti-Beacon for Windows 10
This list is Copyright 2000-2017 Safer-Networking Ltd.
End of entries inserted by Spybot Anti-Beacon for Windows 10
<IP_ADDRESS>  rhino.acme.com              # source server
<IP_ADDRESS>   x.acme.com                  # x client host
<IP_ADDRESS>     localhost
::1           localhost
<IP_ADDRESS>       app-sj01.marketo.com
<IP_ADDRESS>       analytics.ff.avast.com
<IP_ADDRESS>       analytics.ns1.ff.avast.com
<IP_ADDRESS>       v7event.stats.avcdn.net
<IP_ADDRESS>       v7.stats.avcdn.net
<IP_ADDRESS>       analytics.rollout.io
<IP_ADDRESS>       a.fiksu.com
<IP_ADDRESS>       sdk.fiksu.com
<IP_ADDRESS>       static.hotjar.com
<IP_ADDRESS>       flow.lavasoft.com
<IP_ADDRESS>       telemetry.servers.getgo.com
<IP_ADDRESS>       ws.mcafee.com
<IP_ADDRESS>       analytics.ccs.mcafee.com
<IP_ADDRESS>       analyticsdcs.ccs.mcafee.com
<IP_ADDRESS>       h.online-metrix.net
<IP_ADDRESS>       analytics.paddle.com
<IP_ADDRESS>       carcharodon.trendmicro.com
<IP_ADDRESS>       cdn.segment.com
<IP_ADDRESS>       api.segment.io
<IP_ADDRESS>       mobile-service.segment.com`

Are you still experiencing this issue? /needinfo

No, sorry I don't have MalwareBytes installed anymore.


Default capabilities for meltano.yml target cookiecutter update

Migrated from GitLab: https://gitlab.com/meltano/sdk/-/issues/375
Originally created by @vischous on 2022-05-05 05:35:21

https://gitlab.com/meltano/sdk/-/blob/main/cookiecutter/target-template/'Reference to deleted milestone 7'B%7Bcookiecutter.target_id%7D%7D/meltano.yml#L11-13
Maybe just list about? Not clear to me what should be there other than what's currently there can't work.

View 2 previous comments from the original issue on GitLab

Addressed by https://github.com/meltano/sdk/pull/1093


Bump to buildah v1.14.5

Signed-off-by: Daniel J Walsh<EMAIL_ADDRESS>

@mheon @baude @giuseppe @vrothberg @TomSweeneyRedHat @QiWang19 @jwhonce PTAL

LGTM

Interesting that more lines are removed than added. Less code is always nice :)


Compiling on MacOS 10.12

While compiling Yosys on MacOS 10.12, I received the following errer:
frontends/ast/dpicall.cc:25:10: fatal error: 'ffi.h' file not found
I added "-L/usr/local/opt/libffi/lib" to the Makefile under the Darwin specific flags
LDFLAGS += -L/opt/local/lib -L/usr/local/opt/readline/lib -L/usr/local/opt/libffi/lib
and compilation completed, passing all tests

hmm.. Why does adding a -L option fix a not found include file? Why do the ffi pkg-config commands not work in this case? I don't have a Mac, so I cannot test this.

TLDR; Build worked fine on my 10.12 machine, OPs pkg-config might be screwed up.
The average Developers Mac has multiple installations of pkg-config. E.g. there is a default Mac OS one, there might be one from the Homebrew package manager and maybe another one from Macports, like OP seems to have. Depending on how well the software using pkg-config is written it might uses hardcoded paths and ignores environment vars.
So OP might has libffi installed via macports, but his PKG_CONFIG_PATH variable might point elsewhere. Also his fix wouldn't work on my machine because i do not use Macports wich keeps stuff in /opt/ (which is sacrilege IMHO) but Homebrew, wich keeps stuff in /usr/local/.
Installing 10.12 might has screwed up something else, i'd recommend running
xcode-select --install

just in case.

I have an idea why this is. I will put together a PR 😬.

Apologies, the error is on my system.  After upgrading MacOS and Xcode, I thought I'd ran xcode-select after the upgrade (I'd even wiped and re-installed homebrew and it's packages without issue; no macports), but I ran it again and was able to compile without the above change.
Thanks @maknoll!


Updated python-quiz.ts

I have added question in this sheet kindly review it and merge it.
Checklist:

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)

Closes #XXXXX

Kindly Merage is ASAP.

Kindly Merge it ASAP.

This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it.
We do not accept submissions from external quiz sites like these
https://www.sarthaks.com/2439438/which-of-these-is-the-definition-for-packages-in-python
Please come up with your own quiz questions and answers 👍


Allow to run PHPUnit without arguments and run Behat with strict mode on Travis CI

Thank you, Kamil! :tada:


Import Error undefined symbol Py_InitModule3

Great module, or looks great anyway. Looking to use with Python 3.6.0 anaconda build, but no look through github clone install or pip install through github - can't import with error as in title. :(

Unfortunately, this module doesn't currently support Python 3, so that's likely the cause of the error you're seeing.

Well. This makes perfect sense. Thanks.


⚠ Bofrost.at has degraded performance

In 6bddfd0, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2597 ms

Resolved: Bofrost.at performance has improved in 9cfed01 after 13 minutes.


Media sources are assumed to be entities

Title mostly says it; there appear to be some spots in Islandora functionality working with media which assume that the source_field references an entity of some kind, which isn't necessarily the case (i.e. for those sourced remotely).
STR

Create a new media type
As its 'Media source', use 'Remote video'
Create a media of that media type, using a YouTube video or some other valid source.
Try to edit that media
Some errors come up

Notes
Specifically, this was observed in a couple places where:
$media->get('whatever_the_source_field_is')->referencedEntities();

is in use. But $media->get('whatever_the_source_field_is') doesn't necessarily return an object implementing EntityInterface - as in the case of OEmbed sources. In fact, as far as I can tell, there isn't a whole lot of guarantee what comes back from the source field. Sure as heck isn't a MediaSourceInterface since it gives you the actual file entity.
It wouldn't be so much of a problem if an assumption was made that repository items don't reference remote media, but this is breaking any non-entity-sourced media on the site, not just ones used in Islandora; for example, if you wanted to embed a video on the front page from YouTube to introduce your site, you couldn't currently do that. Supporting embedded media keeps us in line with I7 features anyhow.

@ajstanley opened up https://github.com/Islandora/documentation/issues/1273 about this recently.  Can we close one of the two?
And did you get far into this @ajstanley?

Heck I'm sorry, I completely missed the other one. My github-search-fu is pretty terrible? I mean we can just close this and reference as a comment on "some investigation was done"

This was fixed here
https://github.com/Islandora/islandora/blob/8.x-1.x/src/EventSubscriber/MediaLinkHeaderSubscriber.php#L73-L77

way back in the olden days.

On Tue, Dec 3, 2019 at 10:40 AM Daniel Aitken<EMAIL_ADDRESS>wrote:

Heck I'm sorry, I completely missed the other one. My github-search-fu is
pretty terrible? I mean we can just close this and reference as a comment
on "some investigation was done"
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Islandora/documentation/issues/1374?email_source=notifications&email_token=AADY2JY55SPOLJQABHYYEUTQWZVWFA5CNFSM4JUFRGC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFZTARI#issuecomment-561197125,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADY2J2D2MOGDEXC4Y44FJLQWZVWFANCNFSM4JUFRGCQ
.

--
Alan Stanley
Developer and Training Specialist
Agile Humanities

Ok, so I'll close out the old ticket and we'll keep this one to track work to hit up all the other spots where we assume.

@qadan Are you looking at 1.0.0 or are you running from HEAD?

@qadan it seems like Danny was suggesting this feature was fixed. We're not sure if it is - can you re-open with details if this remains an issue?


Fox Sports 503, ESPN2 510

Both channels seem to have disappeared.

looks like Kayo has implemented DRM on most channels now

I can only see Fox Sports 507, beIN Sports 2, Fox League, ESPN1, Fox Footy and Fox Cricket now. :(
I take it there's nothing you can do with DRM channels?

not in kayo unfortunately :(

The Kayo app doesn't have a TV guide, this plugin was the only way to make it usable.

The Kayo app doesn't have a TV guide, this plugin was the only way to make it usable.

Just use the foxtel tv guide

The Kayo app doesn't have a TV guide, this plugin was the only way to make it usable.

Just use the foxtel tv guide

It's a whole extra step, though, as is scrolling all the way to the live channels in the app. Had it all in my Emby server with all my other TV channels, could record things, just leave ESPN on for NBL double headers, skip back and forward in ten second chunks with one press of the arrow key instead of being limited to skipping 30 seconds at a time and having to press the select key before being able to navigate...

Only 507 and 509 remaining.

Just finished moving from plex to jellyfin just so i could use this with the IPTV and have everything in the one place :(

So there's really no workaround or other way to do this anymore?


Feature request: string.join(".")

Feature request:
Want method StringArray.join(".")
Like a PHP implode: http://php.net/manual/en/function.implode.php
example:
Usage:
    var splitted = ["mpv", "open", "dvd"]
    var joined = splitted.join(".")
    print(joined)

Output:
    "mpv.open.dvd"

Something like this?
func _ready():
	print(join(PoolStringArray(["mpv", "open", "dvd"]),"."))

func join(array,filler):
	var rs = ""

	for s in array:
		rs += s+filler

	rs.erase( rs.length()-1, 1)
	return rs

I think it won't work only with ["mpv", "open", "dvd"] because this is an Array.
Adding join to PoolStringArray will result in this example.
var splitted = ["mpv", "open", "dvd"]
var joined = PoolStringArray(splitted).join(".")
print(joined)

So what do you think Array or PoolStringArray  or ...?

var splitted = ["mpv", "open", "dvd"]
var joined = PoolStringArray(splitted).join(".")
print(joined)

Look good.
I like it.
Why not StringArray.join(".") ?
See:
print ("a.b.c".split("."))
["a", "b", "c"]

print (typeof("a.b.c".split(".")))
25

25 - TYPE_STRING_ARRAY
...and StringArray logically neater.
What is PoolStringArray?
Not found it in documentation of v2.1.2. New feature?

I am using 3.0 Master right now.
String.split returns an PoolStringArray in 3.0
I think PoolStringArray  is now 25 - TYPE_STRING_ARRAY
The thing is when you create the Array like this it will always be a simple Array
var splitted = ["mpv", "open", "dvd"] -> TYPE_ARRAY = 21

Hm... I love clean syntax.
Like a ["mpv", "open", "dvd"].split(".")
It will be good.
It conflict with something?

I want 3.0 as fast as possible. Yes. )

@vitalfadeev This issue is not solved yet, but just finished with discussion. We still need someone to implement it :wink:
To clarify:
We want PoolStringArray to get a join method, which accepts a string parameter for the delimiter, and returns the joined string:
String PoolStringArray::join(String delimiter) {...}

Fixed by #7882.


Contributing to PkgDev?

I like the interactive version very much and the customization step by step it provides. I wonder what made you start a new package from scratch instead of adding these features to PkgDev? It is hard to keep up with the pace of Julia, there are many eyes in PkgDev already to update any missing files or formats when new releases come out. It is a lot on the shoulders of a single contributor I would say? :)
Anyways, we definitely this type of flexibility when generating packages, thanks for sharing!

Sorry I didn't get to this earlier! Both packages do pretty similar things, but internally they don't work the same. The key difference here is modularity via the plugin system which is the focus of PkgTemplates, but not really present at all in PkgDev. Because of this, it's not really practical for either package to contain the other.


Buttons in library are grayed out

🐛 Bug Report

[✓] 📁 I've Included a ZIP file containing my librephotos log files
[✓ ] ❌ I have looked for similar issues (including closed ones)
[✓ ] 🎬 (If applicable) I've provided pictures or links to videos that clearly demonstrate the issue

📝 Description of issue:
On fresh installation buttons in the "Library" (including Scan Library) are grayed out. The "Rescan" button works. Rescan is able to find all my photos.
🔁 How can we reproduce it:
Install librephotos via docker compose (docker-compose-v2) on local machine with Ubuntu 24.04 LTS using this guide. Go to http://localhost:3000/library. Almost all the buttons are grayed out and are not clickable
.
The same issue is present with a fresh installation via docker-compose on Ubuntu 20.04 LTS.
An archive with logs, console output during reinstallation process, configuration files and videos demonstrating the problem:
issue.zip.
Similar issues:
#1269 has similar error messages, no answers
https://www.reddit.com/r/librephotos/comments/sit3jz/help_configuring_and_starting/
Similar symptoms, but I can't understand what "myPhotos" is. And there are no answers.
Please provide additional information:

💻 Operating system: Ubuntu 24.04 LTS
⚙ Architecture (x86 or ARM): x86
🔢 Librephotos version: Version: 2024w28
📸 Librephotos installation method (Docker, Kubernetes, .deb, etc.): docker compose (docker-compose-v2)

🐋 If Docker or Kubernets, provide docker-compose image tag: reallibrephotos/librephotos:latest

📁 How is you picture library mounted (Local file system (Type), NFS, SMB, etc.): Local file system

There is probably a long-running job that seems to be running in the admin dashboard. If it is actually finished, because it crashed or is stuck, then just remove it from the list, and then you can start another one

Thank you!


Fix mem issues and enable debug build

Some bad things fixed reported by Valgrind, done in this patch

enable debug build
fix invalid read by avoiding premature free
fix uninitialized data read by zeroing local_addr struct
fix invalid read on non \0 terminated buffer

Thanks.

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


The function of "Get" in leveldb has a bug?

The memtable uses a skiplist, the level of a node is randomly generated。 When the internal keys have same user_key, but their seqs are not same, and small seq  key has higher level.It will not work because of the current code logic.

@wonderspig why not work ? insert node into the skiplist will insure the seqs, and the seqs is not relevant to the level.


Add connection retrying on startup and SIGHUP, Fix #742

This adds a capped exponential backoff(base is 1 second, cap is 32 seconds, arbitrarily picked, could be improved) for retrying the db connection in a background thread.
This thread is started at postgREST startup and leaves it rejecting all requests with a 503 with no parsing or further processing, it's in an unavailable state until connection succeeds; this thread can also be started on SIGHUP.
I considered that postgREST is in an available state when the dbStructure is successfully obtained, and that's what the connectionWorker works on, I'll explain why:
At first I had an available IORef for when the connection succeeded but got some issues when the dbStructure was not obtained, for example postgREST succeeded with requests like:
GET /clients
GET /clients?select=id,name

But gived an error with requests like:
GET /
GET /clients?select=id,name,projects{*}

For what I've seen the first requests escaped the sections of the code that operated on dbStructure, so if the dbStructure is not obtained then postgREST is in a broken state, so instead of having two IORefs to maintain I decided that the IORef dbstructure should indicate the available state.
I think this is useful as it is but I don't know an easy way to add tests. Thoughts?

this gets us to the "set it and forget it" state :)

Btw, to manually test this what I do is to set the pool timeout to a higher value, like 3600, here https://github.com/begriffs/postgrest/blob/master/main/Main.hs#L68, otherwise postgREST reconnects fast on its own, after that you can just stop or restart your PostgreSQL instance and check the reconnection process output, whether at startup or at SIGHUP.

This is helpful to make the server more robust, and to deal with docker-compose races too. Very nice.
I'll review the specifics of the code soon, and will think about how to test as well...

Does this also apply when PostgREST is running normally but the database temporarily goes down?

For now just at startup and at SIGHUP, but if it works well as it is I could extend the connection retrying to work automatically whenever an user request gets a 503 response.

@steve-chavez Wouldn't it make more sense to have some sort of a heartbeat process instead of waiting for a user request to fail?

I consider recovering from temporary database connection failures necessary for closing #742. I could open a separate issue for that however.

@ajnsit If the db is down the reconnection is not guaranteed to be fast, could take a long time depending on the recovery of the db, so the user request would still fail, having a heartbeat process would not avoid that.
Also I think that the hearbeat would be more wasteful since to do that I'll have to do a background thread that sends something like SELECT 1 in intervals and waits for failure all the time, better to just run a thread eventually.
@jackfirth I'll see if I can add the automatic connection retrying in this PR.

Note it's getting too late for me to review this one tonight, but I'll get to it tomorrow night.

Tried this locally and it works nicely when I kill the db and send postgrest a SIGHUP. During the interim it sends back 503, and reconnects when the db is back.
I agree with @jackfirth that detecting disconnection on a failed web request is important. When I kill the db and issue a request (no SIGHUP) postgrest currently sends back a lackluster error:
HTTP 500
{
  "details":"FATAL:  role \"postgrest_test_authenticator\" does not exist\n",
  "code":"",
  "message":"Database connection error"
}

The message of the error is good, but the details are misleading and HTTP 503 would be preferable to indicate the temporary nature of the problem.
Having trouble coming up with tests for the test suite. We'd need a way to mock the database or something and make it die while expecting reconnection attempts. Sounds hard and un-haskelly. I guess I'm good if we smoke test it and it works.

I'll wait to look at the code in greater depth until after you've worked on the non-sighup disconnection detection in case that work causes reorganization of the code.

@begriffs the code in this pr is already useful in a lot of cases, especially docker. Let's have it reviewed and merged and leave the "mid production disconnect" for another PR. It already took a long time having this implemented.

@ruslantalpa I tentatively disagree.
The automatic reconnection detection seems like the primary feature actually. Sighup handling is a special case that would be unnecessary if postgrest could auto reconnect on lost connection. (Well maybe it would still be useful to trigger an immediate retry if postgrest had reached a very large wait value for exponential backoff...) I'm imagining the reconnection attempt on startup to be a special case of reconnecting whenever the connection drops.
Merging this feature in the current state might be dangerous in that it's sorta kinda good enough for some cases and then we'd be less likely to revisit it. If we add features to postgrest I want us to do it right.
Thoughts?

The initial connect failure is the important feature. Once the db structure is introspected, the db can go down and PostgREST will recover because db connections are released from the pool after 1s (if not used). Without this feature, if the db is not present at startup, PostgREST never recovers, so you need to revert to tricks to control the boot order.
Also, this PR introduces the primitives (which will not need changing later) that will be used to implement the mid process disconnect.
The two features while in the same category are not dependent on one another, they can be added separately, in stages. I can understand your reasoning if somehow this code would later need a rewrite, but i don't think that is the case, the mid disconnect case was considered from the very beginning and the primitives were created in such a way to later support that feature (hence the global ioref and the 503).
Lastly, not merging a feature because it will be "less likely to revisit" (a second related feature)  does not increase chances of the second feature being implemented (but rather decrease them :) )

@ruslantalpa I'm not sure I understand what you mean, so I'd like to clarify what I think is necessary for closing #742. Specifically, I think this flow should be possible:

User sends request to PostgREST, receives normal response.
Database goes down, all attempts to connect fail.
User sends request to PostgREST, receives error response.
Database comes back up, new connections can now be opened.
User sends request to PostgREST, receives normal response.

This PR as far as I know only addresses how PostgREST behaves at startup. Are you saying that due to the way PostgREST pools connections, this currently happens already? Or are you saying that PostgREST currently does not handle this situation, but this PR somehow interacts with connection pooling to address it?
And when you say "mid process disconnect", do you mean when the database temporarily fails while PostgREST is processing a request? So retrying a temporary failure there would prevent the user from seeing a failure at the cost of greater latency?

Yes, because of how pool connections work, this happens already, provided more then 1s passes between http requests so that the db connections in the pool are closed and the new ones will work.
This does not happen if there is a constant stream of requests (more then 1 per second)

by mid process i mean the situation you describe, not mid request

So in the flow I described, if PostgREST gets more than one query per second in total traffic continuously it will not recover from a temporary failure? That seems like a pretty big deal, I would not call #742 fixed in that case.

it's a big deal, and no one is calling #742 fixed

Okay good, thanks for the clarification.

@begriffs I've added the automatic connection retrying, this happens whenever an user gets a 503. Also corrected that error code status you mentioned to 503. Now it needs review and manual testing.

@steve-chavez you are such a rockstar! 🤘 I'll give it a look this evening and try hitting it with a bunch of concurrent requests/sighups while bringing the db up and down just to check for any concurrency issues.

I was able to find odd behavior. To reproduce, create these scripts:
sighup.sh:
while [ 1 ]
do
    killall -HUP postgrest
    sleep 0.23
done

getrequest.sh:
while [ 1 ]
do
    curl -I http://localhost:3000 -s | head -n 1 | cut -d$' ' -f2
    sleep 0.1
done

Start the db and then start postgrest
Run getrequest.sh, which should give a bunch of 200s
In another terminal run sighup.sh
Getrequest will show alternating 200 and 503. Maybe this is because it takes time to reload the db schema and during the reload it temporarily wipes out the structure cache?

Yes, it's because of the time it takes to reload the dbStructure, but that was deliberate, the idea was to put PostgREST in an 'unavailable' state and respond quickly with 503, avoiding parsing etc., while retrying the connection.

Accidentally deleted my previous comment with Vimium. Yes, it's because the time it takes to obtain the dbStructure, but that was deliberate, the idea was to put PostgREST in an unavailable state and respond with 503 quickly, without parsing ,etc., while the connection retrying is happening.
Do you think that his behavior should be improved?. I think is good enough, even if getting the dbStructure is avoided and we just retry the connection it would still give 503 to some concurrent requests.

Makes sense. Repeatedly sending sighup is not even a realistic thing, and a brief 503 should be fine. Just wanted to double check it with you.

It's looking good, I verified that

concurrent sighup and requests work when taking db down and up
everything still shuts down properly if isServerVersionSupported returns false
it retries for connection on startup if needed and gets it successfully

My only question about functionality at this point is about the retry timing and sighup. Let's say postgrest has tried reconnecting a number of times and the next try won't be for quite a while. It would be nice if sighup could reset the backoff and make it check right away. That way if I notice the db is down I can bring it up and get postgrest reconnected fast.
Things are working great right now and that sighup improvement is totally optional. If you think it's a pain to make that change I can just merge this as it is, let me know.

Right now the code is so that only a connectionWorker thread can run at a time no matter how many SIGHUP's are made, this also works when doing SIGHUP's and the connectionWorker is already on because of a failed request with 503; adding that timer reset and handling it concurrently would make this feature more complex.
The retrying is done in exponential backoff and when it hits 32 seconds, it doesn't keep increasing and the next retrying is 32s, next 32s, and so on(capped at 32s), so if the idea is not making the user wait for too long one option could be to reduce this cap, but for now I don't know what number will be more appropriate.
Other option would be, and this was the original intention, to do a cyclic exp backoff so if it hits 32s it restarts again from 1s, that would make the wait shorter, but I couldn't get that to work with the retry lib, see https://github.com/Soostone/retry/issues/47, @begriffs maybe you could check that I may have complicated myself and turns out its a one liner and then I could add that to this PR, if it's not simple then I think it'll be better if I give it more time and implement this option in another PR.

As a frequent PostgREST and constant Docker user, I'm really glad to see this implemented. Thanks a ton @steve-chavez!

I overlooked that the wait time maxes out at 32 seconds. That's not so bad.
I think it's merge time! 🚀


Some fixes and a little bit of refactoring

I used the template function relURL to make the link to the CSS stylesheet aware of the configured baseURL. Without this the browser cannot find the stylesheet when baseurl is set to a subdirectory of a server, i.e. baseurl = "http://example.com/hugo/".

Oh I just noticed that after this commit the site does not work any more, if for example baseurl = "http://example.com/hugo/ and relativeURLs = true in config.toml... @masa0221 you may wait until you accept this pull request... :-)

I just noticed that github automatically update this PR when I alter my master branch. I hope it's okay to have one big PR. The bug mentioned in my previous comment seem to be due to https://github.com/spf13/hugo/issues/2227 and I hope it will be fixed in the future...

@kulla
Thank you for Pull request, and great refactoring!
Sorry for the late response.
I confirmed all modified sources.
Sounds great!


Earlgrey: prim_sram_arbiter.sv doesn't work in Verilator

Parsing prim_sram_arbiter.sv file fails in Verilator:
%Error: Could not get lowconn handle for port, aborting
%Error: Internal Error: ../V3Ast.cpp:344: Null item passed to setOp1p

This file requires: prim_fifo_sync.sv (#256), prim_arbiter_tree.sv (#259), prim_arbiter_ppc.sv (#258).

Removed from the list in https://github.com/antmicro/verilator/pull/470


Where is the manual? such as ':h image'

I just want to enhanced customize configuration.

since there is no doc folder there is no help file


Source code

Thank you for making this project available.
IIUC, currently the kernels themselves are only available in binary form. It would be great to have access to the source to help build on top of your impressive research. Do you have plans to release the source for the kernels as well?

Thanks for your interest. We are currently working on CUDA code cleanning to reduce repetition and improve readability. Source code will be released in the future.

Thank you very much for your excellent work. We are eagerly looking forward to viewing the source code implementation of the CUDA kernel for this project.


Summon fails: json: cannot unmarshal object into Go struct field DifferentialRevision.reviewers of type []string

Hi,
We're currently using the newest versions of Phabricator (Docker image bitnami/phabricator:2017.13-r0)  and Phabulous (built from source last night). Almost everything is working as intended, except the summon command fails with the following error: json: cannot unmarshal object into Go struct field DifferentialRevision.reviewers of type []string
Thank you for any help you can provide!

Submitted two fix PR's:

https://github.com/etcinit/gonduit/pull/9
https://github.com/etcinit/phabulous/pull/58


openamp: Bump to v2022.04.0

Bump OpenAMP to v2022.04.0 and fix Zephyr terminology linked to OpenAMP.
Note: there is still some terminology to fix in Zephyr but this PR is only fixing what's strictly related to OpenAMP.

Due to the suppression of potentially objectionable terms  some build warning should occurs
to avoid this
VIRTIO_DEV_SLAVE should be replaced by VIRTIO_DEV_DEVICE in:
-samples/subsys/ipc/openamp_rsc_table/src/main_remote.c

subsys/ipc/ipc_service/lib/ipc_static_vrings.c
subsys/ipc/ipc_service/backends/ipc_rpmsg_static_vrings.h

VIRTIO_DEV_MASTER should be replaced by VIRTIO_DEV_DRIVER in:

subsys/ipc/ipc_service/lib/ipc_static_vrings.c
subsys/ipc/ipc_service/backends/ipc_rpmsg_static_vrings.h

RPMSG_MASTER sould be replaced by RPMSG_HOST in

subsys/ipc/ipc_service/lib/ipc_rpmsg.c
subsys/ipc/rpmsg_service/rpmsg_backend.c
samples/subsys/ipc/openamp/src/main.c
samples/subsys/ipc/openamp_performance/src/main.c

CONFIG_OPENAMP_MASTER and CONFIG_OPENAMP_SLAVE cthat are Zephyr config are optional to update

@arnopo I should have already addressed your comments in this PR

@arnopo I should have already addressed your comments in this PR

Also a wrong review here?  I don't know wat i have reviewed but certainly not the good one.  Another time my apologizes

Should the CONFIG_OPENAMP_MASTER and CONFIG_OPENAMP_SLAVE be updated also?

Yes, but that will break a lot of users so it must be done carefully with deprecation. I'll push another PR for that.


Deleting a node deletes all animation tracks referencing that node.

I noticed this while working on a game for Global Game Jam this past weekend. Say you have an animation set up in the animation player, and you are referencing a node that exists in the current scene file; If you then delete that node, any tracks that reference it will also be deleted.
I can see how this might make sense, but I found myself in a situation where I lost a good chunk of work:
I had a item–a sword specifically–attached to the player, and was animating it from the player scene. I later decided that it should be a pickup and removed it from the player, deleting several animations. Since you can create animations that reference a node path that doesn't exist, and then add the node via script at run time, I had assumed this would work, but instead wound up having to redo my work.
Given that we can create an animation with an invalid path, and that the engine will provide a helpful error if the path isn't valid at runtime, should Godot not keep the animation tracks? Or ask before deleting them?

I believe Godot allows you to save animations to a file so they can be reused (have you tried doing that)?

I think you can disable this behavior in the project settings... but maybe
we could add something with quiker access (within anim editor) to
enable/disable the behavior?
On Tue, Feb 2, 2016 at 9:48 PM, Ace-Dragon<EMAIL_ADDRESS>wrote:

I believe Godot allows you to save animations to a file so they can be
reused (have you tried doing that)?
—
Reply to this email directly or view it on GitHub
https://github.com/godotengine/godot/issues/3562#issuecomment-178921425.

or maybe when you delete, remind the user that some animation tracks will
be erased?
On Tue, Feb 2, 2016 at 9:52 PM, Juan Linietsky<EMAIL_ADDRESS>wrote:

I think you can disable this behavior in the project settings... but maybe
we could add something with quiker access (within anim editor) to
enable/disable the behavior?
On Tue, Feb 2, 2016 at 9:48 PM, Ace-Dragon<EMAIL_ADDRESS>wrote:

I believe Godot allows you to save animations to a file so they can be
reused (have you tried doing that)?
—
Reply to this email directly or view it on GitHub
https://github.com/godotengine/godot/issues/3562#issuecomment-178921425
.

Maybe just a pop-up with a question? For example "This node is animated. Do you want to delete all it's animation tracks as well?"and yes, no buttons?

or maybe when you delete, remind the user that some animation tracks will be erased?

+1, I got hit by this one when renaming an AnimationPlayer node too, all its animations were lost when doing so (actually I was then able to port them easily to use the new name by editing the tscn directly, but if not they simply got removed from the scene).

We already have the "Clean-Up Animation" option, so it would be really nice if "invalid" keys/tracks were marked red or something and leave it to the user to clean them up either on pop-up dialog or later.
I just got burned by merging a scene, apparently deleting some of the merged anim-reliant nodes in a bad order, which led to all my animations getting wiped everywhere without warning, and I didn't manage to recover the .tscn in time.

Maybe just a pop-up with a question? For example "This node is animated. Do you want to delete all it's animation tracks as well?"and yes no buttons?

I suggest doing this. When you delete the Node through the editor, there's already a confirmation dialog:

The related code could be expanded to also check if the node being deleted is used in animations, and if so show a different dialog with the option to delete the node and remove any tracks referencing it, delete the node but keep the tracks, or abort.

I had a look at this and added a checkbox to the Confirmation Dialog to directly see and change the editor setting that controls if animation tracks are deleted or left alone. That effectively implements what @akien-mga suggested. But: see the draft PR #42001 for some issues that I think should be decided on.


feat: To store user's Intercom email share consent on backend

Description
Currently, there is no way for us to know any details about a user when they reach out to support via Intercom. Thus, we are not able to offer the right level of support to them basis their current plan.
The idea is to ask for consent to share user details with Appsmith before Intercom is enabled for a user, the basis which support can determine the right level of support.
This PR helps to store and retrieve the flag variable for a particular user which says whether the consent was given or not.
Fixes #22611
Type of change

New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Manual
JUnit

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

/ok-to-test sha=dec3b7c657dcb3d1780a42d9eb448c603971c88c

/ok-to-test sha=2be01cd33f8c5495f903a48d62605425b4028488


[BUG] Turn a node down and up, workload takes longer time to come back online in Longhorn v1.2.0

Describe the bug
When a node is turned down and turned back on. It takes 15 minutes for the statefulset/deployment workload to come back online in v1.2.0 compare to 7 minutes in the older Longhorn version.
To Reproduce

Try the test https://longhorn.github.io/longhorn-tests/manual/pre-release/node/improve-node-failure-handling/
Observe that it take 15 minutes for  statefulset/deployment workload to come back online

Expected behavior
Should be as quick if not quicker than the older Longhorn version
Environment:

Longhorn version: Longhorn v1.2.0-rc1

Test steps:

Deploy a statefulset of cale 1 that use PVC provisioned by Longhorn.
Set Pod Deletion Policy When Node is Down setting to delete-both-statefulset-and-deployment-pod
Find and turn off the node where the pod is running on.
I should takes less than 8 mins the pod to recover.
Repeat the above steps with deployment instead of statefuleset.

Before the fix

Event
Elapsed Time
Additional Info

Node become note ready
0:37

Pod enter terminating (has the deletion timestamp)
5:54

Pod is force deleted
6:32

Pod is recreate and in ContainerCreating
6:32
Multi-Attach error for volume "pvc-51e196b9-4f93-42a2-b362-b744fa05b07f" Volume is already exclusively attached to one node and can't be attached to another

VA is deleted
12:34

New VA is created
12:34

Pod is running
14:50

After the fix

Event
Elapsed Time

Node become note ready
0:37

Pod enter terminating (has the deletion timestamp)
5:44

VA is deleted
6:34

Pod is force deleted
6:38

Pod is recreate and in ContainerCreating
6:38

New VA is created
7:15

Pod is running
7:45s

Verified on master-head (longhorn-manager 8e7d947) by following the test steps.
Creating a statefulset, and stopping the node where the statefulset pod is running and starting monitoring pod status, the pod would recover in less than 8 mins:
2022-07-15 11:00:27.621	 pods	 NAME                 READY   STATUS    RESTARTS   AGE
2022-07-15 11:00:27.623	 pods	 test-statefulset-0   1/1     Running   0          97s
2022-07-15 11:01:34.969	 pods	 test-statefulset-0   1/1     Running   0          2m44s
2022-07-15 11:06:40.155	 pods	 test-statefulset-0   1/1     Terminating   0          7m50s
2022-07-15 11:06:54.585	 pods	 test-statefulset-0   1/1     Terminating   0          8m4s
2022-07-15 11:06:54.602	 pods	 test-statefulset-0   1/1     Terminating   0          8m4s
2022-07-15 11:06:54.608	 pods	 test-statefulset-0   0/1     Pending       0          0s
2022-07-15 11:06:54.614	 pods	 test-statefulset-0   0/1     Pending       0          0s
2022-07-15 11:06:54.637	 pods	 test-statefulset-0   0/1     ContainerCreating   0          0s
2022-07-15 11:07:16.544	 pods	 test-statefulset-0   1/1     Running             0          22s

2022-07-15 10:59:34.471	 va	 NAME                                                                   ATTACHER             PV                                         NODE          ATTACHED   AGE
2022-07-15 10:59:34.474	 va	 csi-db63425a72822a49a6850ad1f8abe1056a745260b27e12910fb14830c197b345   driver.longhorn.io   pvc-7b0f4b4a-e72b-43f8-aeaa-39406d93c0ae   ip-10-0-1-6   true       40s
2022-07-15 11:06:40.171	 va	 csi-db63425a72822a49a6850ad1f8abe1056a745260b27e12910fb14830c197b345   driver.longhorn.io   pvc-7b0f4b4a-e72b-43f8-aeaa-39406d93c0ae   ip-10-0-1-6   true       7m46s
2022-07-15 11:06:42.301	 va	 csi-db63425a72822a49a6850ad1f8abe1056a745260b27e12910fb14830c197b345   driver.longhorn.io   pvc-7b0f4b4a-e72b-43f8-aeaa-39406d93c0ae   ip-10-0-1-6   false      7m48s
2022-07-15 11:06:42.302	 va	 csi-db63425a72822a49a6850ad1f8abe1056a745260b27e12910fb14830c197b345   driver.longhorn.io   pvc-7b0f4b4a-e72b-43f8-aeaa-39406d93c0ae   ip-10-0-1-6   false      7m48s
2022-07-15 11:06:54.666	 va	 csi-c5d1ba9d76a1736e3fdbe7e99d830e092a3d184c4c7a7ca5beaa7b081492a35e   driver.longhorn.io   pvc-7b0f4b4a-e72b-43f8-aeaa-39406d93c0ae   ip-10-0-1-38   false      0s
2022-07-15 11:06:54.673	 va	 csi-c5d1ba9d76a1736e3fdbe7e99d830e092a3d184c4c7a7ca5beaa7b081492a35e   driver.longhorn.io   pvc-7b0f4b4a-e72b-43f8-aeaa-39406d93c0ae   ip-10-0-1-38   false      0s
2022-07-15 11:06:54.683	 va	 csi-c5d1ba9d76a1736e3fdbe7e99d830e092a3d184c4c7a7ca5beaa7b081492a35e   driver.longhorn.io   pvc-7b0f4b4a-e72b-43f8-aeaa-39406d93c0ae   ip-10-0-1-38   false      0s
2022-07-15 11:06:55.717	 va	 csi-c5d1ba9d76a1736e3fdbe7e99d830e092a3d184c4c7a7ca5beaa7b081492a35e   driver.longhorn.io   pvc-7b0f4b4a-e72b-43f8-aeaa-39406d93c0ae   ip-10-0-1-38   false      1s
2022-07-15 11:07:07.805	 va	 csi-c5d1ba9d76a1736e3fdbe7e99d830e092a3d184c4c7a7ca5beaa7b081492a35e   driver.longhorn.io   pvc-7b0f4b4a-e72b-43f8-aeaa-39406d93c0ae   ip-10-0-1-38   true       13s

Creating a deployment, then stopping the node where the deployment pod is running and starting monitoring pod status, the pod would recover in less than 8 mins:
2022-07-15 11:59:20.217	 pods	 NAME                               READY   STATUS    RESTARTS   AGE
2022-07-15 11:59:20.219	 pods	 longhorn-test-nfs                  1/1     Running   0          86m
2022-07-15 11:59:20.220	 pods	 test-deployment-56f74b48c7-5fxkv   1/1     Running   0          67s
2022-07-15 11:59:51.056	 pods	 test-deployment-56f74b48c7-5fxkv   1/1     Running   0          98s
2022-07-15 12:04:56.192	 pods	 test-deployment-56f74b48c7-5fxkv   1/1     Terminating   0          6m43s
2022-07-15 12:04:56.216	 pods	 test-deployment-56f74b48c7-ddpfv   0/1     Pending       0          0s
2022-07-15 12:04:56.224	 pods	 test-deployment-56f74b48c7-ddpfv   0/1     Pending       0          0s
2022-07-15 12:04:56.244	 pods	 test-deployment-56f74b48c7-ddpfv   0/1     ContainerCreating   0          0s
2022-07-15 12:05:50.273	 pods	 test-deployment-56f74b48c7-ddpfv   1/1     Running             0          54s
2022-07-15 12:07:24.640	 pods	 test-deployment-56f74b48c7-5fxkv   1/1     Terminating         0          9m11s
2022-07-15 12:07:24.642	 pods	 test-deployment-56f74b48c7-5fxkv   1/1     Terminating         0          9m11s

2022-07-15 11:59:28.040	 va	 NAME                                                                   ATTACHER             PV       NODE          ATTACHED   AGE
2022-07-15 11:59:28.041	 va	 csi-a907b52c92be366c9f4d27d3d950caeeecb1e641e45ca42f0b335699831f1cf8   driver.longhorn.io   test-1   ip-10-0-1-6   true       75s
2022-07-15 12:04:56.216	 va	 csi-a907b52c92be366c9f4d27d3d950caeeecb1e641e45ca42f0b335699831f1cf8   driver.longhorn.io   test-1   ip-10-0-1-6   true       6m43s
2022-07-15 12:04:58.976	 va	 csi-a907b52c92be366c9f4d27d3d950caeeecb1e641e45ca42f0b335699831f1cf8   driver.longhorn.io   test-1   ip-10-0-1-6   false      6m45s
2022-07-15 12:04:58.980	 va	 csi-a907b52c92be366c9f4d27d3d950caeeecb1e641e45ca42f0b335699831f1cf8   driver.longhorn.io   test-1   ip-10-0-1-6   false      6m45s
2022-07-15 12:05:22.309	 va	 csi-1701210dbf2b0a0dccc464bf02bc3711b88f088c9c700a41658fc6465572b172   driver.longhorn.io   test-1   ip-10-0-1-186   false      0s
2022-07-15 12:05:22.310	 va	 csi-1701210dbf2b0a0dccc464bf02bc3711b88f088c9c700a41658fc6465572b172   driver.longhorn.io   test-1   ip-10-0-1-186   false      0s
2022-07-15 12:05:24.767	 va	 csi-1701210dbf2b0a0dccc464bf02bc3711b88f088c9c700a41658fc6465572b172   driver.longhorn.io   test-1   ip-10-0-1-186   false      2s
2022-07-15 12:05:32.449	 va	 csi-1701210dbf2b0a0dccc464bf02bc3711b88f088c9c700a41658fc6465572b172   driver.longhorn.io   test-1   ip-10-0-1-186   true       10s
2022-07-15 12:05:34.510	 va	 csi-1701210dbf2b0a0dccc464bf02bc3711b88f088c9c700a41658fc6465572b172   driver.longhorn.io   test-1   ip-10-0-1-186   true       12s
2022-07-15 12:05:34.695	 va	 csi-1701210dbf2b0a0dccc464bf02bc3711b88f088c9c700a41658fc6465572b172   driver.longhorn.io   test-1   ip-10-0-1-186   false      0s
2022-07-15 12:05:36.645	 va	 csi-1701210dbf2b0a0dccc464bf02bc3711b88f088c9c700a41658fc6465572b172   driver.longhorn.io   test-1   ip-10-0-1-186   false      2s
2022-07-15 12:05:46.660	 va	 csi-1701210dbf2b0a0dccc464bf02bc3711b88f088c9c700a41658fc6465572b172   driver.longhorn.io   test-1   ip-10-0-1-186   true       12s
2022-07-15 12:05:54.670	 va	 csi-1701210dbf2b0a0dccc464bf02bc3711b88f088c9c700a41658fc6465572b172   driver.longhorn.io   test-1   ip-10-0-1-186   true       20s
2022-07-15 12:05:56.767	 va	 csi-1701210dbf2b0a0dccc464bf02bc3711b88f088c9c700a41658fc6465572b172   driver.longhorn.io   test-1   ip-10-0-1-186   false      22s
2022-07-15 12:05:56.768	 va	 csi-1701210dbf2b0a0dccc464bf02bc3711b88f088c9c700a41658fc6465572b172   driver.longhorn.io   test-1   ip-10-0-1-186   false      22s
2022-07-15 12:06:22.321	 va	 csi-1701210dbf2b0a0dccc464bf02bc3711b88f088c9c700a41658fc6465572b172   driver.longhorn.io   test-1   ip-10-0-1-186   false      0s
2022-07-15 12:06:22.323	 va	 csi-1701210dbf2b0a0dccc464bf02bc3711b88f088c9c700a41658fc6465572b172   driver.longhorn.io   test-1   ip-10-0-1-186   false      0s
2022-07-15 12:06:24.669	 va	 csi-1701210dbf2b0a0dccc464bf02bc3711b88f088c9c700a41658fc6465572b172   driver.longhorn.io   test-1   ip-10-0-1-186   false      2s
2022-07-15 12:06:25.280	 va	 csi-a907b52c92be366c9f4d27d3d950caeeecb1e641e45ca42f0b335699831f1cf8   driver.longhorn.io   test-1   ip-10-0-1-6     false      0s
2022-07-15 12:06:25.286	 va	 csi-a907b52c92be366c9f4d27d3d950caeeecb1e641e45ca42f0b335699831f1cf8   driver.longhorn.io   test-1   ip-10-0-1-6     false      0s
2022-07-15 12:06:25.287	 va	 csi-a907b52c92be366c9f4d27d3d950caeeecb1e641e45ca42f0b335699831f1cf8   driver.longhorn.io   test-1   ip-10-0-1-6     false      0s
2022-07-15 12:06:25.287	 va	 csi-a907b52c92be366c9f4d27d3d950caeeecb1e641e45ca42f0b335699831f1cf8   driver.longhorn.io   test-1   ip-10-0-1-6     false      0s
2022-07-15 12:06:27.333	 va	 csi-a907b52c92be366c9f4d27d3d950caeeecb1e641e45ca42f0b335699831f1cf8   driver.longhorn.io   test-1   ip-10-0-1-6     false      2s
2022-07-15 12:06:32.556	 va	 csi-1701210dbf2b0a0dccc464bf02bc3711b88f088c9c700a41658fc6465572b172   driver.longhorn.io   test-1   ip-10-0-1-186   true       10s
2022-07-15 12:06:34.579	 va	 csi-1701210dbf2b0a0dccc464bf02bc3711b88f088c9c700a41658fc6465572b172   driver.longhorn.io   test-1   ip-10-0-1-186   true       12s
2022-07-15 12:06:35.324	 va	 csi-a907b52c92be366c9f4d27d3d950caeeecb1e641e45ca42f0b335699831f1cf8   driver.longhorn.io   test-1   ip-10-0-1-6     false      10s
2022-07-15 12:06:51.296	 va	 csi-a907b52c92be366c9f4d27d3d950caeeecb1e641e45ca42f0b335699831f1cf8   driver.longhorn.io   test-1   ip-10-0-1-6     false      26s
2022-07-15 12:06:54.636	 va	 csi-a907b52c92be366c9f4d27d3d950caeeecb1e641e45ca42f0b335699831f1cf8   driver.longhorn.io   test-1   ip-10-0-1-6     false      29s
2022-07-15 12:06:56.724	 va	 csi-a907b52c92be366c9f4d27d3d950caeeecb1e641e45ca42f0b335699831f1cf8   driver.longhorn.io   test-1   ip-10-0-1-6     false      31s
2022-07-15 12:08:42.299	 va	 csi-1701210dbf2b0a0dccc464bf02bc3711b88f088c9c700a41658fc6465572b172   driver.longhorn.io   test-1   ip-10-0-1-186   false      0s
2022-07-15 12:08:42.301	 va	 csi-1701210dbf2b0a0dccc464bf02bc3711b88f088c9c700a41658fc6465572b172   driver.longhorn.io   test-1   ip-10-0-1-186   false      0s
2022-07-15 12:08:52.346	 va	 csi-1701210dbf2b0a0dccc464bf02bc3711b88f088c9c700a41658fc6465572b172   driver.longhorn.io   test-1   ip-10-0-1-186   true       10s


New errror: wifi noTIM!! (IDFGH-804)

Environment

Development Kit:      [none]
Kit version (for WroverKit/PicoKit/DevKitC): [n/a]
Module or chip used:  [ESP32-WROOM-32]
IDF version (run git describe --tags to find it): latest as of today 2019/3/19
Build System:         [Make|CMake]
Compiler version (run xtensa-esp32-elf-gcc --version to find it): v5.2.0
Operating System:     [Windows]
Power Supply:         [external 3.3V]

Problem Description
At random times and without and identifiable set of preceding events the error message appears. Have searched the web for the error message but very little available other than an explanation that it normally indicates the absence of Traffic Indication Map info.
https://en.wikipedia.org/wiki/Traffic_indication_map
Expected Behavior
No error message and no loss of communications
Actual Behavior
Get error message and sometimes loss of communications requiring a reboot
Steps to reproduce
Cannot reproduce at all.
Code to reproduce this issue
Debug Logs
Other items if possible

The noTIM!! error message is often followed by another unknown new/error being:
wifi wifi state wrong txa_flags=9
Any chance of shedding some light on these failures?

HI @ammaree , "wifi wifi state wrong txa_flags=9" doesn't indicate a bug, it means ESP32 has sent the AddBA request to AP but AP doesn't reply AddBA response within specified time (1 second). Maybe we should remove the log in future.
I think "sometimes loss of communications requiring a reboot" should have no relationship with the log, it also has no relationship with TIM.
Need more detailed description about the problem before we can investigate it, e.g.:

Does "sometimes loss of communications requiring a reboot" mean WiFi disconnect or socket disconnect?
log

I think we can close this issue. The errors have gone away, not sure whether as a result of the AP reconfiguration or the latest Wifi libraries.


Sample code does not work

Thanks for the great work, here are errors from my side (one host with eight V100 GPUs):
CUDA_VISIBLE_DEVICES=0 python llama_inference.py /home/xxx/models/hf_converted_llama/7B/ --wbits 4 --groupsize 128 --load llama7b-4bit-128g.pt --text "this is llama"
Loading model ...
Found 3 unique KN Linear values.
Warming up autotune cache ...
100%|████████████████████| 12/12 [00:33<00:00,  2.80s/it]
Found 1 unique fused mlp KN values.
Warming up autotune cache ...
0%|                                                                                | 0/12 [00:00<?, ?it/s]python: /project/lib/Analysis/Allocation.cpp:42: std::pair<llvm::SmallVector, llvm::SmallVector > mlir::triton::getCvtOrder(const mlir::Attribute&, const mlir::Attribute&): Assertion `!(srcMmaLayout && dstMmaLayout) && "Unexpected mma -> mma layout conversion"' failed.
Aborted (core dumped)

I have the same issue.

have you tried to use the --no_fused_mlp option when running the command? If this solves the issue we can add it to the readme and close this issue. I added the option because I had the same error.


Circular dependency in include files

I'm trying to compile the library using CMake and Ninja instead of the Visual Studio generators. I was aware that IntelliSense is smarter when used in tandem with MSBuild, as it picks up global information of the build and doesn't operate solely based on translation units. When building with Ninja, after realizing that PCH isn't a build acceleration method but is actually a hard requirement of the build, I added target_precompiled_header invocation and realized that the project still doesn't build. I started adding #includes directives to the headers to please the compiler, but ultimately engaged in cyclic include directives. A lot of headers arrive to including DeviceChild.hpp which in turn requires ImmediateContext.hpp which in turn requires Resource.hpp which then requires DeviceChild.hpp again. Removing any of these includes results in undefined types when compiling the very same pch.hpp the build otherwise relies on.
Can anyone comment on how to untie this knot?

Are you still trying to use MSVC as the compiler, or are you trying to use a different compiler? From my skim of the code in DeviceChild.hpp, I don't see why that file would need ImmediateContext.hpp, at least with MSVC's broken template parsing. A forward declaration of the ImmediateContext class should be sufficient to satisfy any non-template code.
As I said in the readme, currently MSVC is the only compiler that we've tried to use to build this code, though given the announcement of WSL support, we do have aspirations to make it cross-platform, since it serves as the basis of the OpenCLOn12 component, which we plan to leverage in WSL.

As a random thought this morning it has occured to me it is likely my CMake toolchain file causing the issue, where I enable /permissive- unconditionally for all builds (I'm a cross-platform dev) and that likely changes the semantics of template parsing, hence the forward declaration isn't enough in this mode. With WSL support in place, even though Clang may be forced to imitate MSVCs lazy template parsing, it may be a better choice forward to make it ISO C++ conformant, in case distros using GCC would actually wanted to include these packages (or parts of it) in their repos.

Yeah, ISO C++ conformance is the first step to making this code cross-platform. The second step is removing Windows-only concepts and embracing std:: replacements whenever possible. Both of these are on our roadmap, and I'd be happy to accept pull requests that help us along towards that path.

It seems MSVC is moving away from permissive:

/std:c++latest now implies /permissive-. This means that customers currently relying on the permissive behavior of the compiler in combination with /std:c++latest are required to now apply /permissive on the command line.

Switching permissive on in the project options does not work anymore, it is ignored, you literally have to pass /permissive on the command line (under additional options in the command line section of the project options). Just a heads-up for anyone trying to make use of the latest C++ features while including the D3D12 translation layer headers.


bin: updated common.bash yq commands to work with yq v4.18+

What this PR does / why we need it:
This PR changes the sops config generation and validations command to work with yq v4.18+
Which issue this PR fixes (use the format fixes #<issue number>(, fixes #<issue_number>, ...) to automatically close the issue when PR gets merged): fixes #
Public facing documentation PR (if applicable)

Special notes for reviewer:
Checklist:

[ ] Proper commit message prefix on all commits
[ ] Updated the public facing documentation
Is this changeset backwards compatible for existing clusters? Applying:

[ ] is completely transparent, will not impact the workload in any way.
[ ] requires running a migration script.
[ ] requires draining and/or replacing nodes.
[ ] will break the cluster.
I.e. full cluster migration is required.

We've already upgraded to yq4 https://github.com/elastisys/compliantkubernetes-kubespray/pull/209


GSSoC: design the link page

@Swarnendu0123  assign this issue for design the link page.

Copy issue, checkout #6


Update Spire to depend on typelevel/algebra

This is a really big PR. It introduces a dependency on algebra (and transitively on cats-kernel) for many of its fundamental type classes. We don't currently have version-to-version compatibility guarantees, but this is still going to be a breaking change for some people.
(Thanks to @rklaehn for taking the first stab at it and getting us most of the way there.)
The most noticeable change is the addition of a Gcd type class, and the removal of gcd-related methods from EuclideanRing. There are aliases in place so we can still refer to spire.algebra.Ring, which is now an alias for algebra.ring.Ring. I left all our instances as-is -- we're not currently reusing any instances for algebra.
At this point, I have all the tests passing, and have removed all the non-test warnings. Before merging I'd like to do the following:

[ ] Remove all test warnings
[ ] Run benchmarks here and in master to ensure no performance regressions
[ ] Update the documentation to explain where the external type classes are coming from

Other non-mandatory changes that might be nice to have are:

Update law-checking to use algebra's exported laws.
Use algebra's instances in some cases.
Restructure build files to be more similar to these newer projects

We're currently on Spire 0.11.0. I think we should do a release just before merging this PR, to ensure that every other bugfix/feature we have is available before the change. This is definitely one of the last milestones we need before a future Spire 1.0.0 release.
Review by @tixxit, @johnynek, @rklaehn, and others.

OMG, thanks so much for doing this!!!! I'll start plodding through it!

I did a first pass. A few minor things, but overall looks really great. Thanks again!

The PR hasn't made it obvious but I took all of @johnynek's suggestions.

Regarding EuclideanRing and Gcd: we need to separate the division-with-remainder, and the fmod operations. I have a summary here, please tell me if you need any clarifications:
https://github.com/denisrosset/algebra/blob/master/EuclidianRing.md

Woo! Algebird merged today too: https://github.com/twitter/algebird/pull/523
Now we should coordinate the next release so we can push the one true common algebra core!

@johnynek fantastic!


Fix: Caching thread safety

This aims to fix caching thread safety in Mbed CLI. It uses directory creation which is atomic operation on all operating systems. I've tested with the script @adamelhakham wrote. Additionally @adamelhakham tested it in their CI. I'd still advise to try it in staging CI rather than live.
Addresses https://github.com/ARMmbed/mbed-cli/issues/660
CC @teetak01 @yogpan01

Will fix the Py3 issues. Please ignore for now.

cc: @adamelhakham


Added ability to update a submodule

This wraps git_submodule_update.

Looks great, thanks!

That was fast, thank you!
Do you think implementing Repository::clone_recurse to clone and update all submodules would make sense (basically git clone --recursive)?

Yeah seems reasonable to me!

Thank you. I will look into it.

After looking into it more, I think adding an equivalent of git clone --recursive requires more thought and design, especially to do it in parallel like the --jobs option. This would need new callback types that are Send. Even without making it parallel, some questions don't have an obvious answer. For example, CheckoutBuilder has the ability to specify the directory to check out to and if clone_recurse takes a single instance of it, it is not clear to me how this instance can be used to check out multiple submodules.
In summary, this may need more thought to come up with a versatile and elegant design and I have other priorities at the moment. Hopefully, having git_submodule_update already helps, combined with the existing submodule functionality.

Ok no worries!


Rename "type" to "dataType"

Sometime we need to specify data type in the parsed result.
For now this is a "type" field. But also we use "type" keyword as determine type of actions and transforms . So we need to rename "type" to "dataType" in cases when it has data type meaning.

Would wait.js be a good example of a field that needs dataType instead of type
"wait.js" line 72:
const { type, urlPattern } = event;

While the Actions folder mostly needs type?
"actionsFactory.js" line 57-60:
addAction(type, action) {
      if (typeof type !== 'string' || typeof action !== 'function') {
          throw new Error('addAction accept type as string and action if function which must return a promise');
     }
}

I would love to help in the completion of this issue, just need to know exactly which files would be needing dataType vs regular type


Ollama server inaccessible when requested from different network

When hosting ollama on host1, and ollama-webui on host1, and attempting to access via host2 on a seperate network, the webui will refuse to connect to ollama, while working on host1.
To Reproduce

Install & Run Ollama
Install & Run Ollama WebUI
Port Forward
Attempt to access from any client other than the locally on server
It would be expected to function appropriately, however it for whatever reason pretends as if it cannot connect to the Ollama server, despite working just fine locally. Even if you port forward Ollama and point it to the public Ollama endpoint (verified) it will still not work whatsoever.

Server:

OS: Arch Linux
Version: v1.0.0-alpha

Client:

OS: Windows 11
Browser: Chrome Developer Channel

Hi, most likely a CORS problem. Were you able to check everything outlined in the troubleshooting section in readme.md? If you did and still experiencing the same issue, it would be helpful if you could provide a console log from your browser's developer tool. Thanks.

strange, it appears to be not obeying the provided parameter

changing the default in the env file appears to have the expected effect.
I was under the false assumption that the requests were run server side, and was testing the server url via the settings menu.

the only issue now is that setting the url via the settings menu is not working, should i rename this issue or make a new one?

#70 should fix the issue. Please try again by building from the latest commit and let me know how it goes, Thanks!


Translation: fix translation for faq/general/partners

/assign @rootsongjc @fleeto

/lgtm

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

Needs approval from an approver in each of these files:

content_zh/OWNERS [rootsongjc]

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


New package: PRAMMol v0.0.1

Registering package: PRAMMol
Repository: https://github.com/byu-cig/PRAMMol.jl
Created by: @jmeziere
Version: v0.0.1
Commit: fc4a5b835b14e29b3058c7d3f3082ee71a5c4327
Reviewed by: @jmeziere
Reference: https://github.com/byu-cig/PRAMMol.jl/commit/fc4a5b835b14e29b3058c7d3f3082ee71a5c4327#commitcomment-130003861

Please make sure to add a description of the package and some basic documentation like a usage example in the README before registering.

Could you explain what the name of your package stands for? (Just the need of me asking this is a sign that the name is not great)

Yes, sorry, I was a bit hasty to register the package. This is my first time doing this.
If it is possible, can we close this and I will fix things up and re-register it when I am ready?

Due to my comment, this will no merge. Just re-start the registration process once you are ready.


Devel

Codecov Report

Merging #2 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master      #2   +/-   ##
======================================
  Coverage    86.4%   86.4%
======================================
  Files           4       4
  Lines         103     103
======================================
  Hits           89      89
  Misses         14      14

Impacted Files
Coverage Δ

src/filemapsservice/resources.py
97.67% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d7561c0...f7dff47. Read the comment docs.