Add ImageMagick

ImageMagick
Create, edit, compose, or convert bitmap images in over 200 formats.

Thanks for the recommendation, if you would like it to be added to the list, please create an Pull Request Instead. Thanks for Understanding!

Thanks for the suggestion, but:

It's your list, not mine.
I'm not currently setup to do GitHub Pull Requests, which is too much hassle just for this.
Since you've not that interested in adding it, I'll just write it off as a waste of my time.

https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request

As I said, that's too much hassle.


WBXML is out of date

wbxml is out of date.
Support for EAS 16.1 is available upstream for more than a year
and fix for #2638 is currently waiting for merge.

All fixes are merged upstream, ready for pulling

We have no vested interest in WBXML support. If you or anyone else wants to see the version in mitmproxy updated, please send a PR! 😃

I'm closing this here as I have no particular interest in WBXML, but I'd still be happy to merge a PR. :)


drivers: ethernet: sam_gmac: Fix Kconfig device tree property reference

This commit fixes the path-based device tree property reference in
Kconfig, which contains SoC-specific GMAC device address (in this case,
SAM E70), to use alias instead.
Signed-off-by: Stephanos Ioannidis<EMAIL_ADDRESS>This fixes a bug/oversight introduced in #24057.

Ok, we should introduce compat variants of the kconfig functions then.  I'd prefer we avoid using aliases for this purpose.

Ok, we should introduce compat variants of the kconfig functions then. I'd prefer we avoid using aliases for this purpose.

Agreed. It would be nice to have DT_INST equivalent for kconfigfunctions. Could you look into this?
This effectively blocks #23031 and #23300.

@galak Agreed. It would be nice to have DT_INST equivalent for kconfigfunctions. Could you look into this?

i will.

Can we actually remove this functionality?  Can we have the Kconfig just have a max value and then do some error checking in the driver that the Kconfig value is less than the DT value?
There are a few reasons for this:

keeping Kconfig dt interactions to a minimum
there isn't a great way to do use a dt_inst_int_prop_int as the instance number isn't terribly useful from a Kconfig point of view.

Can we actually remove this functionality? Can we have the Kconfig just have a max value and then do some error checking in the driver that the Kconfig value is less than the DT value?
There are a few reasons for this:

keeping Kconfig dt interactions to a minimum
there isn't a great way to do use a dt_inst_int_prop_int as the instance number isn't terribly useful from a Kconfig point of view.

Here's a PR #24261 for doing it the way I'd prefer.

@galak Ideally, as you suggest, this should be an instance-specific configuration; it only kind of makes sense in this case because we are assuming that there will only ever be one GMAC instance, or multiple GMAC instances with identical max. queue count.
With that being the case, I am not necessarily against removing this feature; just not sure if we should leave range 1 6 in this case as this can be confusing/misleading -- especially when using menuconfig.

HI folks, I imagined this will create noise and I'm not happy with Kconfig too. I think we don't need block a feature as Ethernet because of a minor on Kconfig. We have plenty options and I'll suggest to address this simply opening an issue. We can set this issue to be closed before code freeze. This way we not forget about it.
@vlotech proposes another option:
range 1 $(dt_node_int_prop_int,/soc/ethernet@40050088,num-queues) if SOC_SERIES_SAME70
range 1 $(dt_node_int_prop_int,/soc/ethernet@40034000,num-queues) if SOC_SERIES_SAM4E

Well, this can hurt less than old Kconfig definition and give us time to talk about it.
What do you think?

range 1 $(dt_node_int_prop_int,/soc/ethernet@40050088,num-queues) if SOC_SERIES_SAME70
range 1 $(dt_node_int_prop_int,/soc/ethernet@40034000,num-queues) if SOC_SERIES_SAM4E

@nandojve Sure, for now, I guess that is the best we can do given that we cannot afford to miss the merge window for these new features. We can try to find a better in the long term.
@galak Do you agree? If so, I will close #24256 (this isue) and #24261 in favour of the above.

Closing this PR as the issue has been addressed in #23031 and #23300.


Double Render in prod.

Hey, thank you so much for making this repo public! This is pure gold. Just wanted to inform you about something I discovered while trying to extend on the logic you already provided. In your article you note:
"Another thing I missed was a dev environment double-render example. With NextJs 13.4+, React strcit mode is enabled by default on the dev environment. So if you have an initializing function that adds things like Primitives for example, you need to have a cleanup function so the same things don’t get added twice. I added an example in the repo on May 19 2024 tackling this. Or you can turn off React Strict mode… but I do not suggest you doing that!"
I think that your css styles are actually hiding the fact that there is two viewers initialized. That is why when you zoom in to the red ellipse given by the positions, the rendering starts to break down... take a look:
https://drive.google.com/file/d/1j9C1kiGAayKuzIhEz2QUg1ub8imGv-gB/view?usp=sharing
In the first part of the video, I am visiting your deployed version of the app. In the second example where the ellipse does not break down, I have disabled strict mode because when removing the default styling that your repo offers and installing tailwindcss I discovered that the viewer gets rendered twice. I am trying to combat this by fetching terrain data in a server component and passing as props but no luck yet. Doesn't seem to happen in prod though, but I suspect that your deployed app has two viewers overlayed on top of each other.
For reference here is a deployed version of my app (turned strict mode back on for deployment): https://flight-planner-next-git-se-d8bdb6-mauriciorojascareers-projects.vercel.app/

Hey Mauricio, I am glad that the repo has helped out. I can't view your Preview link as it's locked to your account / your Vercel team. As for the issue, I'm not convinced that the rendering errors you've faced on Cesium has anything to do with CSS as the clipping issue seems more like a 3D z-index issue from Cesium (maybe caused by the flat red ellipse/circle on top of a sphere with varying height). What are you trying to do exactly? I can try to diagnose the issue with you. I did so much work with Cesium lately that it's still fresh in my mind. www.satcat.com <- is where all of my work is in. Thanks! Hyun On Nov 17, 2024, at 11:25 AM, Mauricio A Rojas @.> wrote: Hey, thank you so much for making this repo public! This is pure gold. Just wanted to inform you about something I discovered while trying to extend on the logic you already provided. In your article you note: "Another thing I missed was a dev environment double-render example. With NextJs 13.4+, React strcit mode is enabled by default on the dev environment. So if you have an initializing function that adds things like Primitives for example, you need to have a cleanup function so the same things don’t get added twice. I added an example in the repo on May 19 2024 tackling this. Or you can turn off React Strict mode… but I do not suggest you doing that!" I think that your css styles are actually hiding the fact that there is two viewers initialized. That is why when you zoom in to the red ellipse given by the positions, the rendering starts to break down... take a look: https://drive.google.com/file/d/1j9C1kiGAayKuzIhEz2QUg1ub8imGv-gB/view?usp=sharing In the first part of the video, I am visiting your deployed version of the app. In the second example where the ellipse does not break down, I have disabled strict mode because when removing the default styling that your repo offers and installing tailwindcss I discovered that the viewer gets rendered twice. I am trying to combat this by fetching terrain data in a server component and passing as props but no luck yet. Doesn't seem to happen in prod though, but I suspect that your deployed app has two viewers overlayed on top of each other. For reference here is a deployed version of my app (turned strict mode back on for deployment): https://flight-planner-next-git-se-d8bdb6-mauriciorojascareers-projects.vercel.app/ — Reply to this email directly, view it on GitHub , or unsubscribe . You are receiving this because you are subscribed to this thread. Message ID: @.>

Satcat is insanely impressive! This is using Next and Cesium? I can only
dream of building something like this haha. Here is an updated link to
deployment:
https://flight-planner-next-git-se-d8bdb6-mauriciorojascareers-projects.vercel.app/?_vercel_share=yT2ThnHcrDglE3KIIQN45NIvqqTi0LH1
I am trying to build a UAV flight planner. This tool already exists at my
company but the current standing repo is using vanilla html/js and
bootstrap and it is not scaling at all. I know Next pretty well, however
what you are doing here is the first I'm seeing of such patterns. I am
trying to experiment with your repo as I believe it will scale much better.
At the moment, I have a working viewer and even got tailwind working so
that I can implement some custom ui. I am using
try {
// Wait for the terrain provider to load asynchronously
const terrainProvider = await
CesiumJs.CesiumTerrainProvider.fromUrl(
 https://api.maptiler.com/tiles/terrain-quantized-mesh-v2/?key=${process.env.NEXT_PUBLIC_MAPTILER_KEY}
,
{
requestVertexNormals: true, // Enables smooth shading
requestWaterMask: true, // Enables water effects
}
);
for serving a terrain model that is a little more pronounced and accurate
than
cesiumViewer.current = new CesiumJs.Viewer(cesiumContainerRef.current, {
//Using the Sandcastle example below
//
https://sandcastle.cesium.com/?src=3D Tiles Feature Styling.html
terrain: CesiumJs.Terrain.fromWorldTerrain()
});
but I keep getting two viewers in the dev environment and it is annoying,
though I don't think it is entirely critical because it does not happen in
prod.
On Sun, Nov 17, 2024 at 10:43 AM Hyun Seo @.***> wrote:

Hey Mauricio, I am glad that the repo has helped out. I can't view your
Preview link as it's locked to your account / your Vercel team. As for the
issue, I'm not convinced that the rendering errors you've faced on Cesium
has anything to do with CSS as the clipping issue seems more like a 3D
z-index issue from Cesium (maybe caused by the flat red ellipse/circle on
top of a sphere with varying height). What are you trying to do exactly? I
can try to diagnose the issue with you. I did so much work with Cesium
lately that it's still fresh in my mind. www.satcat.com <- is where all
of my work is in. Thanks! Hyun On Nov 17, 2024, at 11:25 AM, Mauricio A
Rojas @.> wrote: Hey, thank you so much for making this repo
public! This is pure gold. Just wanted to inform you about something I
discovered while trying to extend on the logic you already provided. In
your article you note: "Another thing I missed was a dev environment
double-render example. With NextJs 13.4+, React strcit mode is enabled by
default on the dev environment. So if you have an initializing function
that adds things like Primitives for example, you need to have a cleanup
function so the same things don’t get added twice. I added an example in
the repo on May 19 2024 tackling this. Or you can turn off React Strict
mode… but I do not suggest you doing that!" I think that your css styles
are actually hiding the fact that there is two viewers initialized. That is
why when you zoom in to the red ellipse given by the positions, the
rendering starts to break down... take a look:
https://drive.google.com/file/d/1j9C1kiGAayKuzIhEz2QUg1ub8imGv-gB/view?usp=sharing
In the first part of the video, I am visiting your deployed version of the
app. In the second example where the ellipse does not break down, I have
disabled strict mode because when removing the default styling that your
repo offers and installing tailwindcss I discovered that the viewer gets
rendered twice. I am trying to combat this by fetching terrain data in a
server component and passing as props but no luck yet. Doesn't seem to
happen in prod though, but I suspect that your deployed app has two viewers
overlayed on top of each other. For reference here is a deployed version of
my app (turned strict mode back on for deployment):
https://flight-planner-next-git-se-d8bdb6-mauriciorojascareers-projects.vercel.app/
— Reply to this email directly, view it on GitHub , or unsubscribe . You
are receiving this because you are subscribed to this thread. Message ID:
@.>
—
Reply to this email directly, view it on GitHub
https://github.com/hyundotio/nextjs-ts-cesium-example/issues/1#issuecomment-2481362876,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AT4RJJ5D2HY7SCEYCKMKSW32BDBUFAVCNFSM6AAAAABR6C2BACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBRGM3DEOBXGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thank you! Yea Satcat uses Nextjs, Cesiumjs and some other tech of course.
Regarding your issue, how are you setting terrainProvier to the Cesium Viewer? Are you sure you're not making a new CesiumJs.Viewer every time the data updates or sets? (perhaps, sorry I don't have the full? Make sure you're make a new Viewer once then modify the existing Viewer.


Issue 87: pylint score

Attempt to go through the PyLint results. Have fixed a lot of small stuff, explicitly ignored some others (with explanatory comment) and put TODOs for some things that probably need dedicated PRs to address.
Also created .pylintrc with all defaults apart from max-attributes bumped up to 15.
Can raise new issues for the TODOs if you like.

Closes #87


Add maxcdn support

@matthewp let me know if I could be of any help.  Donejs looks awesome BTW. :+1:

@jdorfman Great, is there a Node library you recommend for push?  Any ftp library will do?

@matthewp Push zones are sftp only. These look like your best bet:

https://www.npmjs.com/package/grunt-sftp-deploy
https://www.npmjs.com/package/gulp-sftp
https://www.npmjs.com/package/sftp-upload

@jdorfman is it possible to upload the ssh public key to maxcdn? I don't see a place from the control panel.

@matthewp not at the moment.  We just put a ticket into our product team.  I will follow up once I know more.


docs: Add user guide for Add or invite someone to a stream feature

Automated message from Dropbox CLA bot
@synicalsyntax, it looks like you've already signed the Dropbox CLA. Thanks!

merged, thanks @synicalsyntax!


.github: use netcat to check hubble port-forward success

Use more robust method for checking if hubble port-forward is successful using netcat.
Do note that the workflows use on.pull_request_target therefore the changes will not be reflected in this PR checks, but we've tested these on the isovalent CI with success.
CC @michi-covalent
Will fix upcoming CI failure caused by: https://github.com/cilium/cilium/pull/35483

I think the AKS test failure is a flaky one, if someone with appropriate permissions could re-run it, that would be great.
Thank you!


Issue

Checklist for submitting an issue to KickThemOut:

[x] I have carefully read the README file and haven't managed to resolve my issue.
[ ] I have searched the issues of this repo and believe that this is not a duplicate.
[ ] I am running the latest version of KickThemOut.

OS name & version:
Python version:
Scapy version:
Nmap version:
Link of Gist:

Description:

issue-RROR: Requirements have not been satisfied properly. Please look at the README file for configuration instructions.

Please look at the README file for configuration instructions.

Maybe follow what it says, and close this issue? This is most likely an error on your end, and you've not read what the error says.

Please look at the README file for configuration instructions.

Maybe follow what it says, and close this issue? This is most likely an error on your end, and you've not read what the error says.

ERROR: Requirements have not been satisfied properly. Please look at the README file for configuration instructions.
If you still cannot resolve this error, please submit an issue here:
https://github.com/k4m4/kickthemout/issues

ERROR: Requirements have not been satisfied properly. Please look at the README file for configuration instructions.
If you still cannot resolve this error, please submit an issue here:
https://github.com/k4m4/kickthemout/issues

Details: [Errno 2] No such file or directory: b'liblibc.a'

Details: [Errno 2] No such file or directory: b'liblibc.a'

Please look at the README file for configuration instructions.

Please look at the README file for configuration instructions.

Please look at the README file for configuration instructions.

Please look at the README file for configuration instructions.

b'liblibc.a'

Error on your system, this isn't a KickThemOut issue.

b'liblibc.a'

Error on your system, this isn't a KickThemOut issue.


Principle 4.1 in its current wording conflicts with principle 1.1

Principle 1.1 states that "it must be possible to include any data or metadata in an information package regardless of its type or format" but principle 4.1 states that "metadata in the information package must conform to a standard". The text for principle 4.1 introduces the concept of "crucial metadata". Does 4.1 only apply to "crucial metadata"? In which case the principle needs to be more specific and in order for validation not to be problematic, acceptable "crucial metadata" standards need to be defined. Is "crucial metadata" the only metadata allowed in the /metadata folder?

When it was written principle 4.1 was for the crucial metadata but of course there can be other metadata.
This will be put on the agenda for the DILCIS Board.

Hej Karin
I have been analysing the existing CITS and I do see consistency in the placement of standardised vs non-standardised metadata, so will make appropriate changes in eHealth1 and note for 3D. One question; if there is non-standardised metadata, say techmd placed in a sub-folder in rep/data, should we refer to it in the dmdSec of the mets file?
Other than this I would also like to discuss Archival collections, this is likely a requirement for 3D Product Models (i.e. product assembly structures) and I am envisaging a master metadata only AIP which holds a product structure.
Also, my analysis of the current CITS has given me a good checklist of possible extension points and constraints for a new CITS. Is this useful for the Guideline?
Again also, I have identified anomalies and improvement points for CITS as well as for eHealth1, e,g, folder naming in eHealth2. Should I just raise these as issues in GitHub?
Thanks
Stephen
Stephen Mackey
Senior Consultant
Penwern Limited
+33 668 397 453
@.***
From: Karin Bredenberg @.>
Sent: Wednesday, July 19, 2023 1:29 PM
To: DILCISBoard/E-ARK-CSIP @.>
Cc: Stephen Mackey @.>; Author @.>
Subject: Re: [DILCISBoard/E-ARK-CSIP] Principle 4.1 in its current wording conflicts with principle 1.1 (Issue #706)
When it was written principle 4.1 was for the crucial metadata but of course there can be other metadata.
This will be put on the agenda for the DILCIS Board.
—
Reply to this email directly, view it on GitHubhttps://github.com/DILCISBoard/E-ARK-CSIP/issues/706#issuecomment-1641910945, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIKSFYLAA3C63MR7Z52VGR3XQ7AIXANCNFSM6AAAAAA2OKVVU4.
You are receiving this because you authored the thread.Message ID: @.***>

The issue have been discussed on todays DILCIS Board meeting and we agreed upon editing the wording so its a well-formed format instead. An update of the wording will be made and a PR will be made for the DILCIS Board to review later on.

The suggestion is:

Update of wording with this PR suggestion #717

Board members acknowledgment of the issue:
Tick the box in front of you name to indicate that you have looked at the suggestion.

[ ] Karin Bredenberg (Kommunalförbundet Sydarkivera, chair)
[ ] Anders Bo Nielsen (National Archives of Denmark)
[ ] Anja Paulič (National Archives of Slovenia)
[ ] Arne-Kristian Groven (National Archives of Norway)
[ ] Gregor Zavrsnik (Geoarh)
[ ] Janet Anderson (Highbury Research & Development Ltd.)
[ ] Maya Bangerter (Swiss Federal Archives)
[ ] Miguel Ferreira (KEEP Solutions)
[ ] Stephen Mackey (Penwern Limited)
[ ] Sven Schlarb (Austrian Institute of Technology)

Voting
(Decision making will be carried out on the basis of majority voting by all eligible members of the Board. In the case of a tied vote, decisions will be made at the discretion of the Chair)
Tick the box in front of you name to say yes to the suggestion.

[ ] Karin Bredenberg (Kommunalförbundet Sydarkivera, chair)
[ ] Anders Bo Nielsen (National Archives of Denmark)
[ ] Anja Paulič (National Archives of Slovenia)
[ ] Arne-Kristian Groven (National Archives of Norway)
[ ] Gregor Zavrsnik (Geoarh)
[ ] Janet Anderson (Highbury Research & Development Ltd.)
[ ] Maya Bangerter (Swiss Federal Archives)
[ ] Miguel Ferreira (KEEP Solutions)
[ ] Stephen Mackey (Penwern Limited)
[ ] Sven Schlarb (Austrian Institute of Technology)

7 DILCIS Board members have acknowledge the issue
7 DILCIS Board members agree with the solution
The PR will be part of the next release of the specifications


Rename WorkloadIAM to EntraWorkloadIAM

The extension type name of microsoft.workloadiam has been changed to microsoft.entraworkloadiam. This PR updates k8s-extension to recognize the new name.

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
az k8s-extension
General Guidelines

[X] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[X] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
[X] My extension version conforms to the Extension version schema

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

What happens to the customer that try to use microsoft.workloadiam and the customers who have setup CI pipeline with microsoft.workloadiam? Do we show any deprecation message or a way for them to know about the name change?

What happens to the customer that try to use microsoft.workloadiam and the customers who have setup CI pipeline with microsoft.workloadiam? Do we show any deprecation message or a way for them to know about the name change?

Right now we are in private preview, preparing for public preview. We know the customers that are using the extension and we are going to notify them of the change. We don't expect anyone to be using this extension in production.

Any updates about when this PR will be merged?


Solution: Fix all Elixir 1.2 warnings

@alPacino @theoretick ping :-)

@c-rack pong :)

Thanks :)


Doc Request: example in Button docs that shows setting the text of the button

I checked the FlatButton and I couldn't find the simple of example of "a button with text". There isn't an obvious "declare the text of the button here". I assume it's the child widget?
https://docs.flutter.io/flutter/material/FlatButton-class.html
It would be sufficient, IMO, to show a simple example snippet in the top of the docs.

cc @Hixie

I agree!
for instance here's a piece of code to update in documentation
            new RaisedButton(
              onPressed: _play,
              child: new Text('Play!'),
              color: Colors.blueAccent,
            ),

Yeah we should add sample code and screen shots to those API docs.


Webhook received but no handler found

The database doesn't get updated after a successful payment. Tested locally and on prod.
Webhook received but no handler found. with a 200 response code (checked
I've followed the docs and added 'lemon-squeezy/*' to App\Http\Middleware\VerifyCsrfToken except list
More info
Tested with a single payment variant
public function checkout(Request $request)
{
    return $request->user()
        →checkout(config('lemon-squeezy.lifetme_deal_variant_id'))
        →redirectTo(url(RouteServiceProvider::HOME));
}

The payment succeed and I'm redirected to the redirect URL, but the database doesn't get updated (customers and subscriptions)
On LM webhooks screen I see this:

Expected behavior:

Database gets updated accordingly

Can you please share more info here? What is this about? A single payment? A subscription? What code did you use, what happened and what did you expect to happen?

@driesvints updated

Hi there. Nothing is supposed to get updated here. Nothing gets handled for single payments, only for subscriptions. It says no handler was found because there is no handler (yet) for successful payments.

Thanks. I've created a custom handler.


network: reject addresses where there is no kernel support.

This support environments in which IPv4/IPv6 is not enabled at kernel
level.
Risk Level: Low
Testing: Manual; ran Envoy in our IPv6-only environment with IPv4
config. Testing for this in CI is not simple, since we don't have
an easy way to mock out kernel support.
Signed-off-by: Harvey Tuch<EMAIL_ADDRESS>

Also, if you add ::socket() to OsSysCalls, you can mock it and add test coverage.

@ggreenway I like the idea of mocking via OsSysCalls, but the static/singleton combination doesn't work well with this pattern; the unmocked IP family support values are cached before we hit this test in a multi-test binary. We could just unconditionally check for IP family support on each address instance creation..

No, checking before each instance creation is both expensive (2 syscalls) and runs into the same problem as the original PR: it'll throw if the system runs out of sockets. I'm ok with not mocking ::socket() since it doesn't work well in this case.

Yes, I agree. Can you approve?

Given that mocking ::socket() for this test doesn't work (and can't work), I think you should revert the last 2 commits. Leaving it as using OsSysCalls means someone else might try to mock that and break multi-test binaries.

Couldn't we still test as long as we make a dedicated test binary for just the required test?

You would need to exclude it from coverage due to the unified binary. Let
me know what you prefer here, I don't mind either way, I would be more
strongly motivated if this was an actual regression that we wanted to catch
in future.
On Fri, May 4, 2018 at 8:06 PM Matt Klein<EMAIL_ADDRESS>wrote:

Couldn't we still test as long as we make a dedicated test binary for just
the required test?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/envoyproxy/envoy/pull/3293#issuecomment-386763694,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKaLv8bHvvdrrNH5WyppTUrq2iO8MeErks5tvO0BgaJpZM4TzAx7
.

Bleh.  As it turns out, over 100 Envoy tests don't properly support v6-only machines.  Things like the MockHostDescription do resolveUrl(harcodedv4url) which now breaks, though we never create a socket around it.
I can fix up the tests this week but I think this change is going to be pretty hard on the v6-only user[s].   CircleCi currently protects us from us breaking things for v4-only users (by not supporting v6 by default)  but I suspect there will be regressions of people using v4-only addresses in other places which will only be caught when Google merges this code downstream.  If anyone has ideas of how to catch more of these in review/CI it'd be much appreciated!

I'm OK with a rollback of this PR as it's not critical (it was intended to unblock some internal tests in the first place) and I'm busyish this week at a summit.
I think we could roll forward with a new CI job that runs with the use of Api::OsSyscalls for socket(2) that allows us to simulate a pure IPv6 environment. Of course, if we can get CircleCI to provide us a pure IPv6 environment which will fail socket(2) for IPv4, that would be even better.

Short term I can just remove the throw() on our import, so it's not a huge problem.  But I'd like to remove it eventually so I'd just like a long term where we don't keep fixing up broken ipv4 tests :-)


Feature/184 add permission check to views

I need to remove the update button from the applicants detail page. will do that next


Improve readability of variation landscape

Is your feature request related to a problem? Please describe.
The variation landscape is hard to read for large genes.
Describe the solution you'd like
It would be nice to have a zoom and pan/scroll functionality such as the one offered by NCBI.
Describe alternatives you've considered
N/A
Additional context
N/A

Closed by https://github.com/bihealth/reev-frontend-lib/pull/94


Cannot view running application if window is too narrow

The good news is I was able to get Eve itself running from the tablet but I can't actually use it there. If I connect to any Eve environment with Chrome on a tablet, the display area is off the screen and it's not even possible to scroll to see it.

Which tablet you're using? Make, model, OS, chrome version would help :) I'm guessing it's an android tablet?

I using a Samsung Galaxy Tab A running Android 6.0.1 and Chrome 54.0.2840.85. I have attached a screenshot.

Ah okay, it's because the resolution is too low, and we don't scroll the workspace area. This should be fixed.

I also notice that the word "examples" has disappeared from the upper left (above "Flappy Eve") although it is still a clickable region and will take you back to the top level of examples if you touch there.

That's because it only appears on mouse hover, which should also probably change. We need to do some work to think about how the editor can be used on a tablet, but that will come down the line. Little fixes like these shouldn't be an issue though.

It was actually cool that I could get it running there at least and was able to attach to it form a laptop to verify it was working. I am using Termux which supports apt so I was able to install git, nodejs, and then just startup Eve.

That's awesome! What are you aiming to do on a tablet, out of curiosity?

Although I know my way around C/C++/C#, I'm more interested in languages that promote RAD and have been looking for ways to create Android apps using them. I was looking at using Python but am intrigued by Eve. My first attempts were going to be a shopping list app and one to connect to Habitica to provide functionality lacking in the existing app.

Cool, never heard of Habitica. I think you'll find the current state of Eve might fall a little short of your goal, there, but learning the language through a shopping list App will work out okay. We've already done some work in making stand-alone Eve apps, which will be merged soon: https://github.com/witheve/Eve/pull/571
And we're working on easy ways to connect Eve to external services like Habitica. I'll put that on the list to make sure it's easy for you.

I happened to discover a workaround for this today. If you click on the left pointing triangle in the table of contents pane to hide it, then the running application pane appears. I did this on my phone (not sure the resolution) and even in portrait mode could scroll between the code pane and the running application pane.


Remove REMIT from the code base

Since this will not be used, we should remove the corresponding code. It is at least still a component publishers can add in sanity

LGTM :thumbsup:


EV07s Tracker implementation

Hello,
is it possible to implement the EV07s (formerly EV07p) Tracker vom Eyevision?
Would be great!

EV-07S GPRS protocol (1).pdf

This protocol is already supported. It's called "minifinder" and by default uses port 5062.

Great to hear! Thanks a lot!


fix: update installer to use https for download

fix error with 403 on http://s3-us-west-2.amazonaws.com/dynamodb-local/dynamodb_local_latest.tar.gz

@AshanFernando several projects are now falling apart. Please fix this.

@rehrumesh @mjzone
Please review and merge this PR if possible

Looks good! Please approve!

merge please

Circling back here: I ditched this package (along with severless-dynamodb-local) and resorted to using Docker + DynamoDB. I modified the docker-compose file to use my desired port but otherwise kept the default configuration in place (as provided by AWS).
From there, I manually created needed tables inside the Docker image. To create tables in the Docker image, you append --endpoint-url http://localhost:[YOUR_PORT_HERE] to the regular create table command. From there, I was able to start my app using sls offline start. It's clear the author of these packages won't be updating anytime soon. I suggest people implement similar solutions and move off this expired package.
I'll update this comment once the problematic packages have been completely removed from my app.

I joined node_modules and edit directly the Dynamo Offline files with the changes of this PR and it worked!

For those of you directly editing node_modules - please understand the next time you run npm install or clear your cache (or any equivalent commands), you will overwrite your edits and it will be broken again. Please consider using different solutions.

@DeeWBee  I think the solution you are suggesting is a very complicated workaround and adding a new infra (docker) in project which may not be possible for all the projects. The "correct" fix is to patch the node_modules using https://github.com/ds300/patch-package.
note: I say this is correct as this would work on local/docker/CI-CD environments with minimal changes but YMMV.  If docker works for you then please continue doing that as you already tackled the most difficult part and made your project more robust.

thanks for merging. any idea when this will be published to npm?

if anyone needs this to work in your containers (for testing) until the package is updated, just throw those lines into your Dockerfile after installing your packages (npm install or yarn)
# until package is updated
RUN sed -i 's|http://s3-us-west-2.amazonaws.com/dynamodb-local/dynamodb_local_latest.tar.gz|https://s3.us-west-2.amazonaws.com/dynamodb-local/dynamodb_local_latest.tar.gz|g' node_modules/dynamodb-localhost/dynamodb/config.json
RUN sed -i 's|http|https|g' node_modules/dynamodb-localhost/dynamodb/installer.js

Or npm install --save 99x/dynamodb-localhost#db30898f8c40932c7177be7b2f1a81360d12876d should work while we wait.

Helllo, @AshanFernando
Can you publish this fix on npm too ?

Helllo, @AshanFernando
Can you publish this fix on npm too ?

I wish a new released version to bump dependency of dynamodb-localhost lib on package serverless-dynamodb-local

Please merge!

the PR was merged, but it is still an old version in the npm package.

This still doesn't work

looks like this needs a new npm release

FYI: Despite this PR being merged, this fix to the package (dynamodb-localhost) still hasn't been published, with no new releases to NPM in over 4 years.
Solution: You can use aws-dynamodb-local, a maintained fork, instead. (Disclaimer: I am a contributor to this fork). It is a drop-in replacement for this package, and is updated to fix this bug. If you're using serverless-dynamodb-local, you can also replace that with it's equivalent serverless-dynamodb.
Migrating takes about 2 minutes, with a full guide in the README. Of course, it's all still open-source and MIT licensed. Ownership of this new package sits with a registered charity, that is committed to maintaining the package into the future and is open to contributions from the community.


Sealing vault pod (via UI) only seals a single pod

Question
I'm running into an interesting issue. When sealing the vault via the UI, only a single pod seals -- the two remaining vault pods (running vault and init containers) run and remain unsealed.  Is this a limitation of running vault on K8S? If not, it's likely I have an issue between pods. Any thoughts?
Considerations

Running vault pro instead of vault

Using an internal type LB instead of public:

I'm running an internal type load balancer, which is different than your service YAML.
---
apiVersion: v1
kind: Service
metadata:
  name: vault
  annotations:
    cloud.google.com/load-balancer-type: "Internal"
  labels:
    app: vault
spec:
  type: LoadBalancer
  loadBalancerIP: 10.xxx.yyy.zzz
  selector:
    app: vault
  ports:
  - name: vault-port
    port: 443
    targetPort: 8200
    protocol: TCP

---
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: vault
  labels:
    app: vault
spec:
  serviceName: vault
  replicas: 3
  selector:
    matchLabels:
      app: vault
  template:
    metadata:
      labels:
        app: vault
    spec:
      affinity:
        podAntiAffinity:
          preferredDuringSchedulingIgnoredDuringExecution:
          - weight: 60
            podAffinityTerm:
              labelSelector:
                matchExpressions:
                - key: app
                  operator: In
                  values: ["vault"]
              topologyKey: kubernetes.io/hostname
      terminationGracePeriodSeconds: 10
      containers:
      - name: vault-init
        image: "sethvargo/vault-init:1.0.0"
        imagePullPolicy: IfNotPresent
        resources:
          requests:
            cpu: "100m"
            memory: "64Mi"
        env:
        - name: GCS_BUCKET_NAME
          value: "xxxxxx-vault-bucket"
        - name: KMS_KEY_ID
          value: "projects/xxxxxx/locations/northamerica-northeast1/keyRings/xxxxxxx/cryptoKeys/xxxxx-vault-key"
        - name: VAULT_ADDR
          value: "http://<IP_ADDRESS>:8200"
        - name: VAULT_SECRET_SHARES
          value: "1"
        - name: VAULT_SECRET_THRESHOLD
          value: "1"
        - name: GOOGLE_APPLICATION_CREDENTIALS
          value: /secrets/credentials/credentials.json
        volumeMounts:
        - mountPath: /secrets/credentials
          name: service-account-credentials
      - name: vault
        image: "gcr.io/xxx-yyy-zzz/vault-enterpise:0.11.5"
        imagePullPolicy: Always
        args: ["server"]
        securityContext:
          capabilities:
            add: ["IPC_LOCK"]
        ports:
        - containerPort: 8200
          name: vault-port
          protocol: TCP
        - containerPort: 8201
          name: cluster-port
          protocol: TCP
        resources:
          requests:
            cpu: "500m"
            memory: "256Mi"
        volumeMounts:
        - name: vault-tls
          mountPath: /etc/vault/tls
        - mountPath: /secrets/credentials
          name: service-account-credentials
        env:
        - name: VAULT_ADDR
          value: "http://<IP_ADDRESS>:8200"
        - name: POD_IP_ADDR
          valueFrom:
            fieldRef:
              fieldPath: status.podIP
        - name: GOOGLE_APPLICATION_CREDENTIALS
          value: /secrets/credentials/credentials.json
        - name: VAULT_LOCAL_CONFIG
          value: |
            api_addr     = "https://10.xxx.yyy.zzz"
            cluster_addr = "https://$(POD_IP_ADDR):8201"
            log_level = "warn"
            ui = true
            seal "gcpckms" {
              project    = "xxxx"
              region     = "northamerica-northeast1"
              key_ring   = "xxx-keyring"
              crypto_key = "xxx-vault-key"
            }
            storage "gcs" {
              bucket     = "xxxx-vault-bucket"
              ha_enabled = "true"
            }
            listener "tcp" {
              address     = "<IP_ADDRESS>:8200"
              tls_disable = "true"
            }
            listener "tcp" {
              address       = "$(POD_IP_ADDR):8200"
              tls_cert_file = "/etc/vault/tls/vault.pem"
              tls_key_file  = "/etc/vault/tls/vault.key"
              tls_disable_client_certs = true
            }
        readinessProbe:
          httpGet:
            path: /v1/sys/health?standbyok=true
            port: 8200
            scheme: HTTPS
          initialDelaySeconds: 5
          periodSeconds: 5
      volumes:
      - name: vault-tls
        secret:
          secretName: vault-tls
      - name: service-account-credentials
        secret:
          defaultMode: 420
          secretName: service-account-credentials

vault-init is going to sit in a loop and unseal anything it sees. So even if you seal, when 30s goes by (the default sleep time), it'll unseal them again.
The behavior you see is expected though. When you seal a Vault, you're sealing a Vault instance. You need to individually seal all the instances, even via the CLI. You can do this by hitting their IPs directly or by removing ?standbyok=true from the healthcheck and then unsealing 3x from the UI (each UI refresh will poingto the now-active node after you seal).

Thanks for the quick reply Seth, this makes good sense. Very much appreciate your dedication to this project, your work has been invaluable to us.
If an immediate need to seal comes up, we will simply scale to 0 unless we need to do some forensics.

Alternatively, you could switch to KMS-based auto-unsealing and drop vault-init entirely. I just haven't updated stuff yet to do that.


Adding Bandit security static analysis for CI/CD

Is your feature request related to a problem? Please describe.
Adding Bandit security static analysis for sanic code. Good to pick up on potential dangerous code added to project inadvertently.
Describe the solution you'd like
Add bandit comparability and deal with false positives.
Additional context
Bandit: https://pypi.org/project/bandit/ && https://bandit.readthedocs.io/en/latest/

PR: https://github.com/huge-success/sanic/pull/1612

closed by https://github.com/huge-success/sanic/pull/1612


Top Stories API Response: Different object types

When I am trying to parse the object from Top stories API. There are different types for:
"org_facet"
"per_facet"
"geo_facet"
"multimedia"
When the fields are empty the type is a string no is an array. It causes and error when I m trying to parse the json object:
Example:
Not empty
"org_facet": ["Islamic State in Iraq and Syria (ISIS)"]
Empty
"org_facet":""

Hey @leomindez have you found any solution for this issue ?
If so, can you please share ?

@RahulSDeshpande  Use version 2 of the API.

@leomindez Okay thanks for the quick response :)
I tried, but didn't work :(
It seems NYT's v2 API has been deprecated & 'news' API is not working, also I cannot find any documentation or swagger doc for the v2 API :(
Anyways, thanks !!
Let me know if you find anything 👍
Cheers !!


[NNVM] Move FTVMCompute registration of cast and comapre operators to C++.

This PR move following operator's registration to c++

cast
greter
less

@srkreddy1238 Would you review this?

@srkreddy1238 @PariksheetPinjari909 Thank you for your review.

Thanks @srkreddy1238 @PariksheetPinjari909 for the helpful reviews and @nishi-t for contributing the code, this is now merged!


Configuration merge problem

The bare minimum to recreate this problem, e.g. in a plugin's default configuration (plugins/comments/comments.yaml)
comments_form:
    fields:
        -
            name: 1
        -
            name: 2
        -
            name: 3

In the custom user configuration (user/config/plugins/comments.yaml)
comments_form:
    fields:
        -
            name: test

If I do
{{dump(grav.config.plugins.comments.comments_form.fields)}}
I get
array:3 [
  0 => array:1 [
    "name" => "something"
  ]
  1 => array:1 [
    "name" => 2
  ]
  2 => array:1 [
    "name" => 3
  ]
]

Buggy behavior: The array is merged, the first item is entered instead of the first item of the original config, but the rest is still added.
Expected behavior: I should only get the config option set in the user folder:
array:1 [
  0 => array:1 [
    "name" => "something"
  ]
]

I can't replicate this problem any more, must have been solved since it's been opened, in 1.1

Not yet solved after some inspection of #1285
The issue happens only when the plugin/theme blueprint defines the property as a list field.

Hi @flaviocopes , I wonder if any issue I am encountering is related? I have the following blueprint:
        -
            name: taxonomy.tag
            type: checkboxes
            label: 'Tag for Blog Post'
            options:
                tag1: 'Tag 1'
                tag2: 'Tag 2'
                tag3: 'Tag 3'
                tag4: 'Tag 4'

And the front matter generated looks like this:
---
taxonomy:
    tag:
        taxonomy.tag-tag1: tag1
        taxonomy.tag-tag3: tag3
---

What do you think? Is this an issue or am I missing something here?
Thanks very much,
Paul

@paulhibbitts looks like a different issue, can you open a new one?

Thanks @flaviocopes , will do!

Closing to due to inactivity


possible miss in parsing of Palo Alto logs for Category field with event "computer-and-internet-info,high-risk" with Splunk_TA_paloalto TA

PAN syslog events with "computer-and-internet-info,high-risk" have Category of "computer-and-internet-info" instead of "computer-and-internet-info,high-risk" for pan:threat logs

Expected behavior
Category is  "computer-and-internet-info,high-risk"

Current behavior
Category is "computer-and-internet-info" only

Possible solution

Steps to reproduce
The raw log data where it should multiple categories, that I also see when viewing directly in the Palo Alto Panorama Console. However, if you look at the parsed data below, you will not see “high-risk” and will only see the “computer-and-internet-info” category.
The domain/url example is sync.ipredictive.com/
FWPICSZ003.ntwk.example.org, 15:09:15,013101008579,THREAT,url,2305,2022/01/10 15:09:15,<IP_ADDRESS>,<IP_ADDRESS>,#.#.#.#,<IP_ADDRESS>,User Internet URL filter-Base,domain\kexample,,ssl,vsys1,Remotevpn,Internet,tunnel.12,ae1.401,EXAMPLE_Log_Forwarding,2022/01/10 15:09:15,34874725,1,51995,443,36068,443,0x40b000,tcp,alert,"sync.ipredictive.com/",(9999),computer-and-internet-info,informational,client-to-server,7038208499611954141,0xa000000000000000,<IP_ADDRESS>-<IP_ADDRESS>,United States,0,,0,,,0,,,,,,,,0,14,20,21,23,,FWPICSZ003,,,,,0,,0,,N/A,unknown,AppThreat-0-0,0x0,0,4294967295,,"computer-and-internet-info,high-risk",f2e4344b-4e53-4c98-91ff-3574e24a4890,0,
Your Environment

Version used: Splunk_TA_paloalto ver7.0.4 on Splunk server <IP_ADDRESS>
Environment name and version (e.g. Chrome 59, node.js 5.4, python 3.7.3): Chrome and Firefox
Operating System and version (desktop or mobile): Windows 10

Bump. We are experiencing similar issues. This has been opened since 11 Jan, Is there any movement on this?


[Question] Why WebSocket.SendAsync() doesn't send asynchronously

        public static async Task SendCmd(WebSocket socket, ArraySegment<byte> outgoing)
        {
            Console.WriteLine("socket.SendAsync >>> " + Thread.CurrentThread.ManagedThreadId);
            await socket.SendAsync(outgoing, WebSocketMessageType.Text, true, CancellationToken.None);
            Console.WriteLine("socket.SendAsync <<< " + Thread.CurrentThread.ManagedThreadId);
        }

Result
SendCmd >>> 14
SendCmd <<< 14

But if I add Task.Delay(1)
        public static async Task SendCmd(WebSocket socket, ArraySegment<byte> outgoing)
        {
            Console.WriteLine("socket.SendAsync >>> " + Thread.CurrentThread.ManagedThreadId);
            await Task.Delay(1);
            await socket.SendAsync(outgoing, WebSocketMessageType.Text, true, CancellationToken.None);
            Console.WriteLine("socket.SendAsync <<< " + Thread.CurrentThread.ManagedThreadId);
        }

Result
SendCmd >>> 14
SendCmd <<< 15

Why SendAsync() doesn't switch to another thread to send data?

Just because a continuation happens on the same thread, doesn't mean it isn't asynchronous :thinking:


[BUG] Error on migration from v3 to v4 (mysql)

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Hello! I have an issue while migrating to v4 mysql database.
The provided value for the column is too long for the column's type. Column: name
Migrating ticket<PHONE_NUMBER>646095962...
prisma:error
Invalid `prisma.archivedRole.create()` invocation:

Then I manually increased the size of the name column to 1024 and everything works as expected (tried 255, but that's not enough).
Also this. Increased the size of the name column of archivedChannels.
The provided value for the column is too long for the column's type. Column: name
Error:
Invalid `prisma.ticket.create()` invocation:

Expected Behavior
Expected no errors.
Steps To Reproduce
Migrate from v3 to v4 mysql database.
Environment
- OS: Ubuntu 20.04
- Node: v18
- NPM: 9.5.1
- Bot: v4

Anything else?
No response

Looks like this is because v3 encrypted role and channels names, while v4 does not.
I'll add decryption.

@potatoru please pull the latest changes, run npm i again and then run the script with -k <encryption key>.

All good now! Thanks!


Feature: sis theme prototype

brute clean-up of leftover ELLS things
initial conceptual mockup (mainly for homepage)

Builds atop PR #35

This one's now "done".
Notes:

Adds site wide header and footer
Adds a homepage mockup
It's all "dumb" and not connected  to the WP database

Also I've shared with Tamaryin and we know the homepage layout will change a lot. Mostly I'm trying to narrow in on the high-level look of how we use the Visual Framework and how much customisation we might need.

That does look very good :-)


Can't build on Linux

Hi, I want to build an application on Linux that will be using your package to send notification on Windows.
Whn building I have this error :
# github.com/electricbubble/go-toast x86_64-w64-mingw32-gcc: fatal error: cannot execute 'cc1obj': execvp: No such file or directory compilation terminated.
Is it possible to do what I want to do ? If yes, how can I bypass this issue ?

CGO_ENABLED=0 GOOS=windows GOARCH=amd64 go build ./main.go

Thanks.
When compiling on Linux with your version 0.2.0 (as I don't need the Objective C extension), I first have this issue :
/gopath/pkg/mod/github.com/electricbubble/go-toast@v0.2.0/toast_windows.go:46:13: undefined: os.WriteFile
/gopath/pkg/mod/github.com/electricbubble/go-toast@v0.2.0/toast_windows.go:203:11: undefined: os.WriteFile

When replacing os by ioutil, I then have this mistake :
/gopath/pkg/mod/github.com/electricbubble/go-toast@v0.2.0/toast.go:5:31: undefined: notification
/gopath/pkg/mod/github.com/electricbubble/go-toast@v0.2.0/toast.go:11:17: undefined: notification
/gopath/pkg/mod/github.com/electricbubble/go-toast@v0.2.0/toast.go:20:17: undefined: notification
/gopath/pkg/mod/github.com/electricbubble/go-toast@v0.2.0/toast.go:29:17: undefined: notification
/gopath/pkg/mod/github.com/electricbubble/go-toast@v0.2.0/toast.go:39:19: undefined: newNotification

And then :
Unknown field HideWindows in struct literal of type sscall.SysProcAttr
I didn't went further as it seems useless, but do you have any solution?

undefined: os.WriteFile

https://github.com/golang/go/blob/89044b6d423a07bea3b6f80210f780e859dd2700/src/io/ioutil/ioutil.go#L40-L47


Support Cypress 10

For compatibility for Cypress 10, a few changes are required, notably

changing the documentation on how to configure the plugin, moving from cypress/support/index.js to cypress.config.js
using excludeSpecPattern instead of ignoreTestFiles

I have a quick fix to get this plugin running with Cypress 10 until it's updated.
If you have this error :

Error running e2e.setupNodeEvents()

The ignoreTestFiles configuration option is now invalid when set on the config object in Cypress version 10.0.0.
It is now renamed to excludeSpecPattern and configured separately as a testing type property: e2e.excludeSpecPattern

You can remplace the config argument of cypressDataSnapshot in cypress.config.ts by an empty object.
const cypressDataSnapshot = require("cypress-data-snapshot/plugin");

function setupNodeEvents(on, config) => {
  cypressDataSnapshot(on, {});

  return config;
}

And add the excludeSpecPattern yourself in the Cypress config.

I don't know if it's because I use @badeball/cypress-cucumber-preprocessor or if it's an issue with Cypress 10, but I get an error when I try and create a snapshot:
Cannot read properties of null (reading 'match')
In order to fix this one I have to override the getTestFilePath command:
Cypress.Commands.add('getTestFilePath', () => {
  return cy.wrap(Cypress.spec.absolute);
});


feat(elastic): adds function to retrieve orphaned indices

Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Hi @nmbryant ! Thanks for the contrib. One question - I'm curious why this method is useful / necessary?

Also, where is the method being used?
Finally, we generally would like to see Java unit tests on things like this :)

Thanks!


Relations in pubtator not showing

I'm trying to read the BioRED file from here: https://ftp.ncbi.nlm.nih.gov/pub/lu/BioRED/
As you will see, it has pubtator formats. The annotations are read in propely, but when I try to read the relations, it doesn't provide any output
The relations are written as follows:
14510914	Association	D050033	D007454	No
14510914	Positive_Correlation	p|DEL|439_443|	C564766	Novel
14510914	Positive_Correlation	p|DEL|439_443|	D003409	Novel
14510914	Association	C564766	D007454	No

Is this something bioc.pubtator supports?

Thanks. Please try v2.0.post5


#23180 fix privileges recognition - add Server privileges to the admi…

fix privileges recognition - add Server privileges to the admin list
For QA Team: Please overview the Schema Privileges - Other Privileges section on MariaDB 11 and any MySQL. This section should contain only schema-based privileges (you can't grant it on specific schema)

verified


Routing not working properly with cmsData component

Routing is not working properly with cmsData component.
I've configured the Snowdog CMS API module in Magento and got CMS pages as response successfully at Vue Storefront.
But, When I clicked on the CMS page link from another CMS page, It will not fetch CMS page content.
For example, When I clicked a first time on About Us link it will get whole page content from Magento and render it and then I clicked on another page from here. it will not be working.
I've set the router and its link as below:
Path: router/index.js
{ name: 'about-us', path: '/about-us', component: CmsData, props: {identifier: 'about-us', type: 'Page', sync: true} },
{ name: 'terms-conditions', path: '/terms-conditions', component: CmsData, props: {identifier: 'terms-conditions', type: 'Page', sync: true} },
{ name: 'privacy-policy', path: '/privacy-policy', component: CmsData, props: {identifier: 'privacy-policy', type: 'Page', sync: true} },
{ name: 'delivery-and-return-policy', path: '/delivery-and-return-policy', component: CmsData, props: {identifier: 'delivery-and-return-policy', type: 'Page', sync: true} }

Path: src/themes/default/components/core/blocks/Footer/Footer.vue
<router-link :to="localizedRoute('/about-us')" exact>
  {{ $t('About Us') }}
</router-link>
<router-link :to="localizedRoute('/terms-conditions')" exact>
  {{ $t('Terms & Conditions') }}
</router-link>
<router-link :to="localizedRoute('/privacy-policy')" exact>
  {{ $t('Privacy Policy') }}
</router-link>
<router-link :to="localizedRoute('/delivery-and-return-policy')" exact>
  {{ $t('Delivery and Return Policy') }}
</router-link>

Current behavior
When I click first time on a link it will fetch content properly from Magento and render it but when click on another link from here, it will not work.

Expected behavior
It should be fetched page content for each link from Magento even clicked on another link from anywhere.
Can you handle fixing this bug by yourself?

[ ] YES
[X] NO

Which Release Cycle state this refers to? Info for developer.
Pick one option.

[ ] This is a bug report for test version on https://test.storefrontcloud.io - In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.
[ ] This is a bug report for current Release Candidate version on https://next.storefrontcloud.io - In this case Developer should create branch from release branch and create Pull Request 3. Stabilisation fix back to release.
[x] This is a bug report for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version hotfix - In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.

Environment details

Browser: Chrome
OS: Ubuntu 16.04
Node: v10.15.3
Code Version:

Hi there! I think it's related to: https://github.com/DivanteLtd/vue-storefront/issues/2499
Could You fix that one? It's just about commenting this condition :)

Hi @pkarw,
I've tried by commenting that line, but it won't work. :(

OK, the reason is You're using outdated CMS module. Please try the recommended one -> the CmsPage (the default routing is like: { name: 'cms-page', path: '/i/:slug', component: CmsPage })

More on the CMS before and after VS 1.6: https://docs.vuestorefront.io/guide/data/static-data.html

@pkarw ,
Thank you. :+1:
It works now :)


TypeError: Cannot read property 'table_name' of undefined

I am creating REST API using Database Connected and Select table from given DB Adapter.
When I click on  button. It will throws following JS Error.
table_name property is not found in javascript so, My Service is not generated based on selected Table.
TypeError: Cannot read property 'table_name' of undefined
    at a.e.ok (c22d22af.apigility.js:1)
    at 6a8334db.vendor.js:6
    at c.on.e (6a8334db.vendor.js:6)
    at k.$eval (6a8334db.vendor.js:5)
    at k.$apply (6a8334db.vendor.js:5)
    at HTMLButtonElement.<anonymous> (6a8334db.vendor.js:6)
    at HTMLButtonElement._.event.dispatch (6a8334db.vendor.js:2)
    at HTMLButtonElement.q.handle (6a8334db.vendor.js:2)(anonymous function) @ 6a8334db.vendor.js:5(anonymous function) @ 6a8334db.vendor.js:4k.$apply @ 6a8334db.vendor.js:5(anonymous function) @ 6a8334db.vendor.js:6_.event.dispatch @ 6a8334db.vendor.js:2q.handle @ 6a8334db.vendor.js:2

I have tried to resolve this issue:
And, I found issue is here:
//console.info(e.dbServices[0].table_name);
				if (e.dbServices[0].table_name && (e.dbServices = [{
								table_name : e.dbServices[0].table_name, //e.rest.table_name,
								columns : []
							}
						]), 0 == e.dbServices.length)

After doing above changes in vendor\zfcampus\zf-apigility-admin-ui\dist\apigility-ui\c22d22af.apigility.js file Rest service Collection and Entity file are generated.
But, get new error fields not generated.
Error: savings field.
PUT http://localhost:8888/apigility/api/module/MyDbAPI/rest/MyDbAPI-V1-Rest-User_login-Controller/input-filter 404 (Not Found)

I think this is a duplicate to https://github.com/zfcampus/zf-apigility-admin-ui/issues/74

I can confirm this is STILL and issue and has broken Apigility Admin UI for creating DB-Connected REST services at this time. Completely fresh installs using:
git clone https://github.com/zfcampus/zf-apigility-skeleton.git

or
curl -s https://getcomposer.org/installer | php --

or
download zip/tar from https://github.com/zfcampus/zf-apigility-skeleton/releases

followed by (command) if needed
composer install

ALL of the above yield:
TypeError: Cannot read property 'table_name' of undefined
at a.e.ok (http://localhost/myapp/public/apigility-ui/c22d22af.apigility.js:1:6663)
*snip*

in javascript console. This is installing per instructions in zf-apigility-skeleton and/or installing the skeleton instead.

This repository has been closed and moved to laminas-api-tools/api-tools-admin; a new issue has been opened at https://github.com/laminas-api-tools/api-tools-admin/issues/29.


Fixed incorrectly rendered chart when specified both configMap and customConf

Trying to render helm chart with following values:
cni:
    configMap: cni-configuration
    customConf: true

using command
helm lint cilium -f values.yaml

resulted in following error:
==> Linting cilium
[ERROR] templates/cilium-configmap.yaml: unable to parse YAML: error converting YAML to JSON: yaml: line 129: mapping values are not allowed in this context

due to the fact that {{- -}} removes whitespaces, which was generating following line in yaml:
read-cni-conf: /tmp/cni-configuration/cni-configwrite-cni-conf-when-ready: /host/etc/cni/net.d/05-cilium.conflist

Issue introduced by https://github.com/cilium/cilium/pull/24389

/test

/test


Make schema object compatible with JSON Schema specification

That's is related to #333
Given that all the major differences were removed in version 3, what is the reason to have remaining differences?

type as array is just a syntax sugar for anyOf
items - what is the reason to not support array syntax? APIs returning tuples and other heterogenous arrays are [regrettably] present. Why spec says items MUST be present? What's wrong with it not being present?
patternProperties - together with propertyNames added in draft-06 it is needed to support hash-maps rather than records.

Additional fields in schema are not a problem, but it still beats me why the restrictions are needed - they create nothing but inconvenience. The argument that certain functionality of tools can't be supported for the full JSON schema spec (see https://github.com/OAI/OpenAPI-Specification/issues/333#issuecomment-179367580 by @fehguy) is a very week one to not support full JSON schema in API spec.
Instead, OpenAPI can say that tools can choose to support full or restricted JSON-schema and make it clear in their documentation.
I understand that it means that the code in some language may not be possible to generate due to the restrictions of those languages. But it should be the problem constrained to the users of that particular language rather than to all users (using more dynamic/loosely typed languages). If I were to need to generate c++ code from OpenAPI spec, the generator would impose these restrictions and I would simplify the API definition file.
Having full JSON-schema spec allowed outweighs the benefit that ALL tools can always work with the schema - I believe it should be left to the developer's discretion to decide whether to use full/restricted schema rather than having "restricted" imposed by OpenAPI as the only possible option. This "nanny state" approach is very frustrating when using this spec.
It would also allow to simplify this spec by simply referencing JSON schema spec instead of redefining it here.

Great justification! I totally agree.

Re: patternProperties - is this any more difficult for tooling to support than additionalProperties ? I ask because I'm trying to ascertain how close we would be for an OpenAPI-described API to be able to serve its own OpenAPI definition via a schema-defined response. I'm using as my example the draft OpenAPI 3.0.x schema under development at google gnostic.

I don't really see the ability to define an OpenAPI definition that accepts an OpenAPI definition as a drive to support patternProperties. There are other reasons to support it, but this is not it.

@webron I know @handrews and @philsturgeon have been on OpenAPI steering calls of late, sorry I haven't been able to attend due to travel.
Has there been any further discussion or thoughts on this since 2017?

Maybe this is the same as #1443 ?

It's a shame that items does not support the array syntax. There is currently no way to define a tuple like
{
  "type": "array",
  "items": [
    { "type": "string" },
    { "type": "string" },
    { "type": "number" }
  ]
}

The closest thing is
{
  "type": "array",
  "items": {
    "anyOf": [
      { "type": "string" },
      { "type": "string" },
      { "type": "number" }
    ]
  }
  minItems: 3
  maxItems: 3
}

but ofc it's not the same.

@lpinca See #1736 - assuming tooling vendors support proper JSON Schema (hopefully more recent versions) as alternativeSchemas, this will be addressed in OAS 3.1.

@handrews awesome! Thank you.

Why not use an array of object?
{
  "type": "array",
  "items": {
    "type" : "object",
    "properties": {
      "s1": {
        "type": "string"
      },
      "s2": {
        "type": "string"
      },
      "i1": {
        "type": "integer"
      }
    }
  },
  "minItems": 3,
  "maxItems": 3
}

@lpinca, thank you for the explanation. I feel better now. :-)

Label Post 3.0 Proposal is not clear.
Looks like version 3 still doesn't support tuple syntax for arrays: https://github.com/OAI/OpenAPI-Specification/blob/04f659aeffd3082de70212189477def845c68aa6/schemas/v3.0/schema.json#L470?

There is another problem: null type is not supported https://github.com/OAI/OpenAPI-Specification/blob/04f659aeffd3082de70212189477def845c68aa6/schemas/v3.0/schema.json#L412

I was hoping that alternative schema would be the savior here, but the current approach is not what I hoped it would be: #1943
Instead https://github.com/OAI/OpenAPI-Specification/pull/1977 is a new effort at closing the gap on OpenAPI v3.1 and JSON Schema.

This was fixed in #1977 so we can close this.


Added Access-Control-Allow-Origin * header to both response objects

Description

What Changed?
[Brief Description of what changed]

Tests

Coverage?

[Description of what tests were written]
Links
Jira
Checklist

[ ] Code Review
[ ] Squash Commits

People To Reivew
[Add those who should review this]

Can one of the admins verify this patch?


Battleye SR #0

I am getting:
`"r select 3] call ExAd_fnc_prepareSlider;
_sliderR ctrlSetEventHandler ["SliderPosChanged", format["(_this select 0) ctrlSetTool"`
I tried to get rid of it with:
!="r select 3] call ExAd_fnc_prepareSlider;\n\n_sliderR ctrlSetEventHandler [\"SliderPosChanged\", format[\"(_this select 0) ctrlSetTool"
But it did not help at all. What can i do against this SR?
Thanks

use
!="_sliderR ctrlSetEventHandler [\"SliderPosChanged\", format[\"(_this select 0) ctrlSetTool"

That should solve it.

Thank you very much :+1: has helped a much ^^


Rename SoundComponent to LoopingSoundComponent

I'm pretty sure SoundComponent is actually a LoopingSoundComponent and everything is using it wrong.
Sounds that play once should use:
_entitySystemManager.GetEntitySystem<AudioSystem>().PlayFromEntity("/sound/path.ogg", Owner);

on it


Added new util script to find the longest data lenght in tests

This script helps to find the longest data length in test cases. We can set it for the tests in tests/docker-compose.yaml and crs-setup.conf, in rule 900005.

It sure is nice to be able to use msc_pyparser so swiftly. Thank you.
Would you mind adding support for --help? I do not mind if it only brings a link to the extensive README online, but I think a script has to explain itself at least a weeny bit.

Help added. I realized that we need an optional argument: if we are looking for the longest length payload between the test cases, because we want to add a test which exceeds that, then next time we must to ignore that test. So I introduced the -i or --ignoretests optional argument, where we can list the test id's, what we want to skip. For more info, see the README or the help.

I tested the script and it works! Looks good to me.

Merging, thanks!


Running "protect" scripts via Husky pre-commit hook fails on Windows with CRLF line endings

Describe the bug
When running protect via a pre-commit hook using husky, it fails with errors:
ERR warning: CRLF will be replaced by LF in xxx
ERR The file will have its original line endings in your working directory
...
husky > pre-commit hook failed (add --no-verify to bypass)

Running the protect script manually works, it only fails in pre-commit hooks.
My package,json:
...
  "scripts": {
    ...
    "scan-secrets:protect:windows": "docker run -v %cd%:/path zricethezav/gitleaks:latest protect --source=\"/path\" -v -c /path/gitleaks.toml",
    ...
  }
...

To Reproduce
Run the protect script on a project in the Windows file system as a Husky pre-commit hook.
My huskyrc.js:
module.exports = {
  hooks: {
    'pre-commit': 'docker run -v %cd%:/path zricethezav/gitleaks:latest detect --source=\"/path\" -v -c /path/gitleaks.toml",'
  }
};

Expected behavior
The commit should pass if no secrets are present.
Screenshots

Basic Info (please complete the following information):

OS: Windows 10 Pro (Build 19044.1415)
Gitleaks Version: 8.2.7 (used via docker run zricethezav/gitleaks:latest

cc @zricethezav

Just to clarify, the protect scripts works when running it in isolation. It only fails when running in a Husky pre-commit hook. See this output below where I first run the script manually and then via a pre-commit hook (I've hilighted the scripta steps in yellow)

@JPStrydom this error is coming from git. What happens when you run git log -p? I also don't know what Husky and don't claim to support it. Sounds like this issue should be opened for Husky. Closing this.

Husky is just a pre commit tool.  Will have a look at the git issue, but if your tool is causing pre-commit hooks on Windows, it might be worth checking out.

For those looking for a sollution/workaround - manually changing the line endings on all files to LF fixed the issue for me. Still wish they could add a propper fix for this, because the manual change can be quite tedious.

Try messing with the git config
from https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration#Formatting-and-Whitespace
Formatting and Whitespace

Formatting and whitespace issues are some of the more frustrating and subtle problems that many developers encounter when collaborating, especially cross-platform. It’s very easy for patches or other collaborated work to introduce subtle whitespace changes because editors silently introduce them, and if your files ever touch a Windows system, their line endings might be replaced. Git has a few configuration options to help with these issues.
core.autocrlf

If you’re programming on Windows and working with people who are not (or vice-versa), you’ll probably run into line-ending issues at some point. This is because Windows uses both a carriage-return character and a linefeed character for newlines in its files, whereas macOS and Linux systems use only the linefeed character. This is a subtle but incredibly annoying fact of cross-platform work; many editors on Windows silently replace existing LF-style line endings with CRLF, or insert both line-ending characters when the user hits the enter key.

Git can handle this by auto-converting CRLF line endings into LF when you add a file to the index, and vice versa when it checks out code onto your filesystem. You can turn on this functionality with the core.autocrlf setting. If you’re on a Windows machine, set it to true — this converts LF endings into CRLF when you check out code:

$ git config --global core.autocrlf true

If you’re on a Linux or macOS system that uses LF line endings, then you don’t want Git to automatically convert them when you check out files; however, if a file with CRLF endings accidentally gets introduced, then you may want Git to fix it. You can tell Git to convert CRLF to LF on commit but not the other way around by setting core.autocrlf to input:

$ git config --global core.autocrlf input

This setup should leave you with CRLF endings in Windows checkouts, but LF endings on macOS and Linux systems and in the repository.

If you’re a Windows programmer doing a Windows-only project, then you can turn off this functionality, recording the carriage returns in the repository by setting the config value to false:

$ git config --global core.autocrlf false


H3-K9 methylation at centromere central core

increased histone H3-K9 methylation at centromere central core
cf. fypo:5066, fypo:4324
PMID:25619765

increased histone H3-K9 methylation at centromere central core FYPO:0005169

edit file: ebca0e1b1a41864453d1f3390865d60e08d97bfe
release: 020228db7d447bce415182f4254f33c30be7c5d0


Can we get vehicle's heading info?

BO_ 723 ID2D3UI_solarData: 8 ChassisBus
SG_ UI_isSunUp : 25|2@1+ (1,0) [0|3] ""  Receiver
SG_ UI_minsToSunrise : 56|8@1+ (10,0) [0|2550] "min"  Receiver
SG_ UI_minsToSunset : 48|8@1+ (10,0) [0|2550] "min"  Receiver
SG_ UI_screenPCBTemperature : 40|8@1- (0.5,40) [-20|100] "C"  Receiver
SG_ UI_solarAzimuthAngle : 0|16@1- (1,0) [-32767|32767] "deg"  Receiver
SG_ UI_solarAzimuthAngleCarRef : 16|9@1- (1,0) [-256|254] "deg"  Receiver
SG_ UI_solarElevationAngle : 32|8@1- (1,0) [-128|126] "deg"  Receiver
Someone says UI_solarAzimuthAngle - UI_solarAzimuthAngleCarRef will be the vehicle's heading
https://www.teslaownersonline.com/threads/diagnostic-port-and-data-access.7502/page-105#post-349702
but i found those numbers continuous changes with nonsense, is ID2D3UI_solarData now has a multiplexor now?

Try UI_gpsVehicleSpeed UI_gpsVehicleHeading, you should be able to get the heading directly from the chassis bus
I don't think the solarData is mux'd, at least on 2024.3.10 it's still giving sensible solar elevation.
Fyi canserver discord is a better place to ask about general can signals. Are you looking for heading info in candash itself? how are you wanting it displayed?

Thanks for the reply.
I try UI_gpsVehicleHeading first, but i get 511 all the time, i will do more test
BO_ 985 ID3D9UI_gpsVehicleSpeed: 8 ChassisBus
SG_ UI_gpsVehicleHeading : 8|16@1+ (0.0078125,0) [0|511.992] "deg"  Receiver
When i try UI_solarAzimuthAngleCarRef and UI_solarAzimuthAngle ,they are continuous changes (within 3-4 numbers loop) so i suspect they are mux'd at first place.
Actually i'm not using canserver now, i'm developing some little fun project myself with two esp32 board (one for transmitter, one for the display unit), just like the roles canserver and candash to be. i use a round display so i think it's a good idea to add a north arrow as a simple compass when i'm driving.
I have been tormented by this question for several days. Maybe that I was too eager to find help, without considering that this might not be the best place to ask. If I have caused any inconvenience, I sincerely apologize.
I'll do more test and thank you again.

It's not an inconvenience, but you will probably find more people to help you on the canserver discord: https://discord.gg/W2pMGkhdcy
There's also a candash discord: https://discord.gg/Wr5VQaGY9M
People love home-brew solutions, no worries at all.


Allow to edit ACL from "api" page

Currently we can only "view". Would be good to be able to "edit" as well.

Fixed


Dataset Previews

Problem
During data discovery, dataset naming conventions and/or documentation do not always provide enough context to understand the relevance of a given dataset. Analysts and Data Scientists frequently run simple select * from ... limit 10 queries to get a better understanding of the shape of data and to determine if it is relevant to their use case.
This requires them to execute further discovery in their querying environment, thus requiring them to navigate to & from DataHub during research.
Proposed Solution
Datasets should have "data preview" results available in the UI so users do not have to navigate outside of DataHub to execute these common queries.
My assumption is that owners of DataHub will not want to schedule & publish updates for all datasets - this would cause unnecessary querying load on datasets that may not actually be relevant to their DataHub users;  worth considering if there is a way to configure a connection directly to the db to execute simple profiling queries on demand, then caching those results in the UI until there's a requested refresh by DH users.
Additional Context
This will likely require some sort of configurable obfuscation of field/column content to protect PII, but I don't have a well-formed opinion about what that should look like just yet.

Refer: #1854


Add nuisance password to site

Once we put logos on the site, we should put a basic password on it to prevent it from getting too public before the partners sign off.
The password does not have to be exceptionally secure, and should be cookied for returning visitors.

@d4weed mind if i ask how you secured the http://vizzuality.github.io/WRW-Prototype/ site? if you have an easy way of spinning up simple auth for these types of situations, i'd love to hear it. thanks!

Hey @apfister,
We just have a variable encoded in base64 (name and value) that is used to compare the input, and we then write a cookie for persistence.
since it's just about not having it explicitly public it's secure enough (someone digging in the code could break it, but it's not a big issue given it's public anyway)

Yeah, I think you just need a short module in your main app init that checks for a cookie and redirects to a login page, and the login page can check the password on the client side and write the cookie.
Something like this, but redirect instead of a blocking div https://github.com/fgassert/insec.js/blob/master/insec.js

the password is now password123

i've added a password to the site. how should we distribute it?

Excellent. We can just email folks when they ask for it.


Added distance unit selector

In search box the distance to a point is displayed in miles even though the unit says km. Instead of fixing that to either of the units, I added distanceUnit in config so admins can select which ever they prefer. I guess the most optimal would be to have it possible for users to select their preferred unit but making that happen was way beyond my skill level.

This is awesome, thank you! Going to test tonight.

 This is why old people need to die.

This option needs to die. Literally everything in the game uses (kilo)meters, notably routes which is user visible. RM also doesn't respect this option for routes.

 This is why old people need to die.

England has entered the chat


Provides means to assign columns and dtypes using indexing syntax

It will be very convenient to provide access to the colnames and dtypes (and other similar metadata that is linked to the columns) by using the indexing syntax. This can be done by using special names to avoid row-key collision and treating these like special rows of data.
The special names can avoid collisions with the row keys.
Assigning column names (in addition to when daf instance is created)
my_daf["$colnames"] = list_of_colnames

my_daf["$colnames"] = [f"col{idx}" for idx in my_daf.num_cols()]

my_daf["$colnames"] = Daf.gen_A1_colnames(my_daf.num_cols())      # create spreadsheet type column names

my_daf["$colnames"] = dict     # The keys are used to initialize the columns

Then reading colnames:
colnames = my_daf["$colnames"]        # instead of my_daf.columns()

Then for dtypes:
my_daf["$dtypes"] = type        # all columns are initialized with the same type

my_daf["$dtypes"] = list          # each column is assigned the value from the list.

my_daf["$dtypes"] = dict         # the row is initialized from the values according to the keys, like normal dict assignment to a row.

For example, if say three columns are not numeric data, and the rest are integers:
# first assign all values as integer type should probably allow both pure types and quoted types.
 my_daf[$dtypes"] = 'int'

# then assign a few columns to specific type
my_daf["$dtypes", ['mainkey, 'metadata1', 'metadata2']] = 'str'

Given a dtypes_dict, initialize the columns and dtypes:
my_daf["$colnames"] = dtypes_dict
my_daf["$dtypes"]      = dtypes_dict

Get the current colnames as a list:
colnames = my_daf[$colnames"]    # this always returns a list and not a daf with a row.

dtypes_dict = my_daf[$dtypes]       # normally returns a dict. This is normally what is required for other uses.
dtypes_list  = my_daf[$dtypes].values()  # the list of types in order.

We need to know what colnames have int datatypes
def keys_with_value(dictionary, value):
    return [key for key, val in dictionary.items() if val == value]

int_cols = my_daf["$dtypes"].keys_with_value('int')

Can build a reverse-lookup structure
dtypes_to_cols = utils.invert_da_to_dola(my_daf[$dtypes])
""" given a dict of vals where vals may be repeated,
    create a dict, where the keys are the vals and the
    values are lists of the prior keys.
    This allows reverse lookup of key based on values in the list.
"""

This function is similar to "value_counts()" operation but goes one step further and provides the keys where the values are found.
(I've need this frequently in data analysis for metadata type data esp. when that data needs to be correlated or when at least a few examples of when it occurs can be provided.)
For example, let's say we need the column names of a specific dtype:
int_cols = dtypes_to_cols['int']

For a given daf, it might be worth creating the reverse-lookup dola structure and saving in cache, or simply searching each time
For now, we can just do the lookup each time, as the dtypes data is not too voluminous.

Another option will be to provide cols and dtypes as property attributes, and use similar code to provide for indexing, including slicing, using lists of colnames, etc. Near term solution can be to provide methods that will provide the same flexibility, without resolving the [ ] syntax.

This issue as been set aside for now.


Updating Site Information Panel from page other than homepage doesnt work

Updating the site information  via Site information Panel of a modern site , both team (backed by O365 group) and communication sites,  only works from the home page of that site.
Category

[ ] Question
[ ] Typo
[x] Bug
[ ] Additional article idea

Expected or Desired Behavior
Updating site information should work regardless of where you are in the site.
Observed Behavior
Currently, while trying to update the site information we are only able to update it from the home page.
In communication site -
While trying to update it from the Site contents page, ( /_layouts/viewlsts.aspx ), it clears out the data. We can only insert data from the home page or the settings page (/_layouts/settings.aspx) page
In modern team site (backed by O365 group) -
The data doesn't get cleared, but when we try to save it we get a generic error as below:

Steps to Reproduce
Try to update the site properties in the Site Information panel from a page other than homepage or settings page in Modern team (backed by O365 group) and communication sites.

As this is not really developer issue, rather happening apparently with any tenant using oob capabilities, we cannot, unfortunately, process this through this channel. Please report this from the Office 365 Admin support channels as we can only concentrate on pure developer topics. Sorry for the inconvenience and slow response time, but closing this for now as we can't handle this. Please do report these in Tenant admin process. Thx.


Drop IS4

:white_check_mark: Build TheIdServer 7.0.0-end-of-is41-0072 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/b2dc5247b1 by @)

:white_check_mark: Build TheIdServer 7.0.0-end-of-is41-0073 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/62bd50eac1 by @)

:x: Build TheIdServer 7.0.0-end-of-is41-0076 failed (commit https://github.com/Aguafrommars/TheIdServer/commit/413060a2b3 by @)

:x: Build TheIdServer 7.0.0-end-of-is41-0077 failed (commit https://github.com/Aguafrommars/TheIdServer/commit/f715d45a19 by @)

:x: Build TheIdServer 7.0.0-end-of-is41-0078 failed (commit https://github.com/Aguafrommars/TheIdServer/commit/d0e45bdf5c by @)

:x: Build TheIdServer 7.0.0-end-of-is41-0079 failed (commit https://github.com/Aguafrommars/TheIdServer/commit/c8e85f5c03 by @)

:white_check_mark: Build TheIdServer 7.0.0-end-of-is41-0080 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/300e5d74a0 by @)


nodePackages: update and add bash-language-server, typescript-language-server, and speed-test

Motivation for this change
Wanted these node packages available in nixpkgs, rather than having to install them manually.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Hi there! We're going to try a different workflow for nodePackages. Right now there are a number of PRs targeting nodePackages, and the churn makes it hard for you to keep your generated .nix files free of merge conflicts.
Could you please remove your generated changes, and just leave your changes in the .json file? That will make it easy to update, review, and merge. Then later this week we are going to generate everybody's nodePackages changes at once.
Thank you!
cc: @ryantm
Feel free to join us in Freenode's #nixos if you have questions about this.

Done.


Update CF CLI

This library (specifically cutlass) assumes the CF CLI is v6. v6 is now deprecated, and so we should upgrade to v7.
In addition to using a supported version of the CF CLI, this will enable us (and any consumers) to use newer CF CLI features.
See also https://github.com/cloudfoundry/buildpacks-ci/issues/88

Closing as low-priority tech debt.


Fix issue with chunkById.

The chunkById method doesn't work with MongoDB, because the framework assumes that the ID will be numeric & doesn't provide an easy way for the user to override that at runtime. I was able to fix this by overriding the forPageAfterId method so that it would convert Laravel's assumed "zero" ID into an equivalent "zero" ObjectId.
I've also added a test to demonstrate the bug & fix.

@jenssegers Would you mind reviewing this when you have a chance? Thanks!


Scroll to first error

How can we scroll to the first error the form finds? If the form is big and error is at top, it's not visible.

i'm using this inside handleFormSubmit()
    if(errors){
      $('html, body').animate({
        scrollTop: $('.your-error-class').offset().top -100
      }, 1000);
    }

Thank you very much, this is exactly what I needed!


Standardize needs to check that data are available over the reference period

Right now, a RuntimeWarning: divide by zero encountered in divide is returned, but that corrupts the results; the method should instead remove records from the db if they don't have any overlap over the reference period.

Reconstructed the code a bit regarding standardize() and center() for both ProxyRecord and ProxyDatabase in commit 6fe18c.


Lost precision for large 64 bit numbers

Context: https://github.com/denoland/deno/issues/12212
Currently all 64 bit numbers are forwarded to use v8::Number which results in lost of precision for e.g. large 64 values like u64::MAX:
https://github.com/denoland/serde_v8/blob/edd2994ac0732b56bad30f32655afd1e6250775c/src/ser.rs#L472-L474
While logically we have BigInt we can switch to, I am unsure how bad the performance implication could be.

@DjDeveloperr Are you looking to pass around "opaque" pointers or u64s you want to do arithmetic on ?

IMO we should just allow pointer arithmetic, I don't think it's a good idea to hide pointer value from user

What if we return u/i64 as transmuted to f64, then the ffi code could use a DataView and convert it to BigInt64? I am not familiar enough with f64s to know if that will work for all numbers though...


Defer Config Initialization Until Before Server Start

Thanks, I was having this problem. You fixed it fast!

@obsidian29 Yeah, it was a really obscure bug with the config library that I use. I think it only happens on heavily modded servers. I had to get like over 170 mods to even trigger it. Glad the fix was well timed for you.


Dwarven Mine entrance materials

Adds materials to some objects around the Dwarven Mine.

Also this spiral staircase that is i assume everywhere

I pushed this to the wrong repo (meant to be Gim-fixes-6)
Don't make me redo it please :(


Updated validations.py python script.

Fixed the behavior of validate_user function in validations.py
Closes: #1

It's a good idea to open an issue first for discussion.

Added an if condition to check the first letter of the username.
[x] Tests pass
[x] Appropriate changes to README are included in PR

@googlebot I signed it!


Not working with Angular 10

The package is not working with angular 10 the error is following
**ERROR in 'graphviz-graph' is not a known element:

If 'graphviz-graph' is an Angular component, then verify that it is part of this module.
If 'graphviz-graph' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this
message. ("

[ERROR ->]<graphviz-graph graph="                                      digraph G {
")**

Thanks for the hint! Yes, it appears, that newer versions of Angular need to enable custom elements. There's a post about it on Stackoverflow and an article too.
Importing the custom element classes as named exports won't help in this case and creating the content by DOM API instead of using a template won't be reasonable. I'm considering producing and exporting the custom element manifest, which should allow the same validation for custom elements like it's possibel for the built-ins. But Angular probably doesn't load the custom element manifests yet.

VS Code IntelliSense and custom elements manifest were added in 1.2.0 and can be included in applications integrating the web components.


Retry import creation on client timeout

Description
When createMigrationSource fails with a client timeout, it would be nice if the CLI did a retry automatically.
[11:53] [DEBUG] HTTP POST: https://api.github.com/graphql
[11:53] [DEBUG] HTTP BODY: {"query":"mutation createMigrationSource($name: String!, $url: String!, $ownerId: ID!, $type: MigrationSourceType!) { createMigrationSource(input: {name: $name, url: $url, ownerId: $ownerId, type: $type}) { migrationSource { id, name, url, type } } }","variables":{"name":"GHEC Source","url":"https://github.com","ownerId":"REDACTED","type":"GITHUB_ARCHIVE"},"operationName":"createMigrationSource"}
[11:54] [ERROR] System.Threading.Tasks.TaskCanceledException: The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.
 ---> System.TimeoutException: The operation was canceled.
 ---> System.Threading.Tasks.TaskCanceledException: The operation was canceled.
 ---> System.IO.IOException: Unable to read data from the transport connection: Operation canceled.
 ---> System.Net.Sockets.SocketException (125): Operation canceled
   --- End of inner exception stack trace ---
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 )
   at System.Net.Security.SslStream.EnsureFullTlsFrameAsync[TIOAdapter](TIOAdapter )
   at System.Net.Security.SslStream.ReadAsyncInternal[TIOAdapter](TIOAdapter , Memory`1 )
   at System.Net.Http.HttpConnection.SendAsyncCore(HttpRequestMessage , Boolean , CancellationToken )
   --- End of inner exception stack trace ---
   at System.Net.Http.HttpConnection.SendAsyncCore(HttpRequestMessage , Boolean , CancellationToken )
   at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage , Boolean , Boolean , CancellationToken )
   at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.SendAsync(HttpRequestMessage , CancellationToken )
   at Microsoft.Extensions.Http.Logging.LoggingScopeHttpMessageHandler.SendAsync(HttpRequestMessage , CancellationToken )
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage , HttpCompletionOption , CancellationTokenSource , Boolean , CancellationTokenSource , CancellationToken )

This would be a good improvement. We intentionally don't retry StartMigration API call, as it could result in duplicate migrations attempted. But I don't think there's any harm in retrying CreateMigrationSource API, even if it results in multiple migration sources created, I don't think that poses any problems.


fix(types): Updates GluegunCommand type for Ignite plugins

This upgrades Gluegun and updates IgnitePlugin commands to use GluegunCommand<IgniteToolbox>[] generic.

:tada: This PR is included in version 3.1.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Enable mouse grabbing by a variable, not by detected features

Slightly better, but still warns when mouse detection disabled

See #62

@lezsakdomi I think this should have been solved by #61 .

Uh, you're right


Fix toggle of header

Fix toggling of header in 2 cases

single touch does not toggle header (#174)
Event 'mousemove' gets called after a single touch and 'mousemove' makes header appear; Solution is to prevent event 'mousemove' to be called after 'touchend'

swipe forward / backward toogles header
Swiping forward / backward triggers 'touchend' event, which toggles the header. Solution is to prevent toggling if 'swipeend' triggered loading of previous/next photo

:astonished:  Congrat for finding that one.

Btw, I am across a couple of code snipped where I didn't see the logic:

What's the purpose of this line?
https://github.com/LycheeOrg/Lychee-front/blob/fe0cb5415748340fc6529f5c623bf289c1cdd33f/scripts/main/init.js#L102
The events in the next section will not be triggered if you don't have a touch device.

Duplicates
There seem to be a duplicates:
https://github.com/LycheeOrg/Lychee-front/blob/fe0cb5415748340fc6529f5c623bf289c1cdd33f/scripts/view/main.js#L191
https://github.com/LycheeOrg/Lychee-front/blob/fe0cb5415748340fc6529f5c623bf289c1cdd33f/scripts/main/init.js#L28
and
https://github.com/LycheeOrg/Lychee-front/blob/7b21ec0b5fc573ddf72f02f7f80a5a9aee51ea80/scripts/main/lychee.js#L659
https://github.com/LycheeOrg/Lychee-front/blob/7b21ec0b5fc573ddf72f02f7f80a5a9aee51ea80/scripts/frame/main.js#L60

Hybrid devices
We bind many event to either click or touchend by this function:
https://github.com/LycheeOrg/Lychee-front/blob/7b21ec0b5fc573ddf72f02f7f80a5a9aee51ea80/scripts/frame/main.js#L60
This falls short in case of convertible laptops, e.g. the X1 Carbon Yoga series. Why do we need this function at all? Shouldn't click be also triggered on a touch device (although a bit later in the event cascade). Furthermore, as a convertible user, I would expect the app to behave the same if I use the mouse of my finder to navigate (in particular these lines https://github.com/LycheeOrg/Lychee-front/blob/fe0cb5415748340fc6529f5c623bf289c1cdd33f/scripts/main/init.js#L104-L117)

Tested. Did not see any problem.

Btw, I am across a couple of code snipped where I didn't see the logic:

What's the purpose of this line?
https://github.com/LycheeOrg/Lychee-front/blob/fe0cb5415748340fc6529f5c623bf289c1cdd33f/scripts/main/init.js#L102
The events in the next section will not be triggered if you don't have a touch device.

No clue.

Duplicates
There seem to be a duplicates:
https://github.com/LycheeOrg/Lychee-front/blob/fe0cb5415748340fc6529f5c623bf289c1cdd33f/scripts/view/main.js#L191
https://github.com/LycheeOrg/Lychee-front/blob/fe0cb5415748340fc6529f5c623bf289c1cdd33f/scripts/main/init.js#L28
and
https://github.com/LycheeOrg/Lychee-front/blob/7b21ec0b5fc573ddf72f02f7f80a5a9aee51ea80/scripts/main/lychee.js#L659
https://github.com/LycheeOrg/Lychee-front/blob/7b21ec0b5fc573ddf72f02f7f80a5a9aee51ea80/scripts/frame/main.js#L60

Gotta remove them then.

Hybrid devices
We bind many event to either click or touchend by this function:
https://github.com/LycheeOrg/Lychee-front/blob/7b21ec0b5fc573ddf72f02f7f80a5a9aee51ea80/scripts/frame/main.js#L60
This falls short in case of convertible laptops, e.g. the X1 Carbon Yoga series. Why do we need this function at all? Shouldn't click be also triggered on a touch device (although a bit later in the event cascade). Furthermore, as a convertible user, I would expect the app to behave the same if I use the mouse of my finder to navigate (in particular these lines https://github.com/LycheeOrg/Lychee-front/blob/fe0cb5415748340fc6529f5c623bf289c1cdd33f/scripts/main/init.js#L104-L117
)

Feel free to refactor that, I don't have a strong opinion. :smiley: