Shortcut when using EQs just for element units

Sometimes I use element queries just for being able to use element-based units, eg:
@element #some > .long > selector + here {
  #some > .long > selector + here {
    padding: 0px 10ew;
  }
}

Is there / could there be a shortcut for avoiding the repetition of the (potentially long) selector? eg
@element #some > .long > selector + here {
  = {
    padding: 0px 10ew;
  }
}

In Sass there's "&" but then my polyglot HTML/XML files need CDATA sections :) So I'd prefer a character that's not relevant for XML-wellformedness.

Somehow :self doesn't work. On https://tobireif.com/ , when I replace
@element #portfolio > .fullWidth {
  #portfolio > .fullWidth {

with
@element #portfolio > .fullWidth {
  :self {

the CSS fails.

When I try this demo, :self seems to work:

Portfolio
fullWidth

As for the original question - ideally you would use a self-targeting selector there, rather than a raw one, originally it was just $this that was supported, but now any of the following will work just because of the way it's being parsed:

$this
:this
:self
$self
eq_this
eq_self

But to add = as an alias for those seems like it might make it more fragile since that's likely to appear inside other selectors like [id=one] and be replaced more than it needs to.
Also, I'm not sure if I shared with you yet or not, but I've been working on a collection of plugins that together replicate all of the functionality of EQCSS, but do it with much simpler code, 1 feature per plugin, and since they are designed as JavaScript modules, it's easy to import only the features you need into each stylesheet you're using.
Check out this element query demo for example, that pulls in jsincss and jsincss-element-query: https://tomhodgins.github.io/jsincss-element-query/test/index
The main stylesheet for that demo is here: https://github.com/tomhodgins/jsincss-element-query/blob/master/test/element-query.js
The reason I bring it up is because one of the plugins I published recently does just element units and nothing else: http://npmjs.com/package/jsincss-element-units
Here's a quick test of using them: https://codepen.io/tomhodgins/pen/JpydVB
So hopefully that gives you some additional flexibility with how you can use the concept of element-based units while you're building :D

I figured out the issue with :self - support for that begins in v1.8.0, changing your code to $this worked with the version you have (v1.7.0) or upgrading to a newer version would let you use :self if you wanted to :D

I had gotten the latest release from
https://github.com/eqcss/eqcss/releases
which is 1.7.0 .

I'll try this one:
https://github.com/eqcss/eqcss/archive/gh-pages.zip

With the latest version from https://github.com/eqcss/eqcss/archive/gh-pages.zip
(version 1.9.0) I'm getting three identical redundant s, and :self doesn't work.

(also with 1.8.0)

(I realized that on https://github.com/eqcss/eqcss/releases several releases were contracted and can be expanded. Anyways, thus far no luck with 1.9 or 1.8)

Hi! I have just updated the 'releases' on Github, I didn't realize anybody was using that to determine versions so I recently stopped doing it :P The current stable version is always what's on npm, and CDNjs makes all versions available, so I hadn't anticipated anybody was looking at Github's 'releases' for that.
What do you mean by this?

I'm getting three identical redundant s, and :self doesn't work.

If I take your 'copy-of-tobyreif_com' folder and replace your link to vendor/EQCSS.min.js with http://elementqueries.com/EQCSS.js (v1.9.0 hosted by Github pages) it works (the text is red).

These are the redundant style elements:
https://user-images.githubusercontent.com/80411/36161961-5b528d62-10e5-11e8-8b34-b17e8297cd6f.png
You can (at least currently) see them at https://tobireif.com/ . I removed all my EQCSS JS and still got these redundant style elements.

On tobyreif.com I see EQCSS.js v1.9.0, I also see what appear to be the right number of style tags:

Here's another zip, this time with EQCSS 1.9.0:
copy_of_tobireif_com_number_2.zip
Please see the lines at "@element #portfolio > .fullWidth" incl. ":self". When I use ":self" I can't override the (necessary) pure-CSS defaults.

Again, thanks for EQSSS and for investigating!

When I load https://tobireif.com/ (has version 1.9.0) in Chrome and do shift-reload I get this:

Three s for "#portfolio > .fullWidth", two of which are redundant.

I think it's just a matter of specificity here. When you write a query like this:
@element div {
  :self {}
}

The plugin is assigning an attribute to each matching element, something like data-eqcss-0-0, and then in the stylesheets it outputs, it would write a selector like [data-eqcss-0-0] to select it. This means that the specificity of :self is always pretty low, which can make it more useful. In this case, a single attribute selector isn't stronger than the 'default styles' you've added in CSS because the selector you've used in CSS is stronger. But with EQCSS you've still got full flexibility to add to :self to increase the specificity.
Suppose in this case, the default styles were #portfolio > .fullWidth. When you use :self to target the same element with a selector like [data-eqcss-0-0] isn't not going to overpower #portfolio > .fullWidth, but what about writing something like this: #portfolio > .fullWidth:self, which would turn into something like #portfolio > .fullWidth[data-eqcss-0-0] :D that would be strong enough to overpower the default CSS styles. In fact, if even just .fullWidth:self is strong enough to make those rules apply :D
@element #portfolio and (max-width: 660px) {
  :self > * {
    -ms-flex-preferred-size: calc(50% - 21px);
    -webkit-flex-basis:calc(50% - 21px);
    flex-basis: calc(50% - 21px);
  }
}
@element #portfolio and (max-width: 440px) {
  :self > * {
    -ms-flex-preferred-size: calc(100%);
    -webkit-flex-basis: calc(100%);
    flex-basis: calc(100%);
  }
}

#portfolio > .fullWidth {
  -ms-flex: 0 0 100%;
  -webkit-flex: 0 0 100%;
  flex: 0 0 100%;
  min-height: 0px;
  /* For IE10: */
  max-width: 100%;
  margin: 0px;
  margin-top: 10px;
  margin-bottom: 10px;
  padding-right: 30px;
  padding-left: 30px;
}
@element #portfolio > .fullWidth {
  .fullWidth:self {
    padding-right: 3ew;
    padding-left: 3ew;
  }
}

Try some queries like this and see if that helps the specificity. I've also made a couple of plugins that use a technique like this to let you customize the specificity of the rules you're applying separately from the specificity of the select you use to target them:

https://github.com/tomhodgins/respec
https://github.com/tomhodgins/jsincss-custom-specificity

And here's a video explaining more about this technique: https://www.youtube.com/watch?v=z9FtZGJHKYY

I'll stay with the repeated selector, because it works - I can override the default styles.
@element #portfolio > .fullWidth {
  #portfolio > .fullWidth {
    padding-right: 3ew;
    padding-left: 3ew;
  }
}

what about writing something like this: #portfolio > .fullWidth:self

Not short enough :)
If :self would be a drop-in replacement for the repeated selector then I'd use :self, but since the styles applied via :self have lower specificity and don't override my (necessary) pure-CSS defaults, ":self" (as it is now) is of no use for me, unfortunately.

even just .fullWidth:self is strong enough to make those rules apply

For me, the repeated selector is very clear & expressive. Using :self would be nice because it's very & short (and makes the code easier to maintain), but it would have to have the exact same specificity. (Perhaps it could simply copy the exact same selector string it references - then it would always work as drop-in replacement, even in my case).

The redundant s are strange, I hope that can be avoided in a future release.

one thing to keep in mind is that you can define selectors anywhere in JS (as a string, array, or a function that returns text) and easily output that anywhere inside of an EQCSS stylesheet, even as a selector.
In this demo I've included a few lists of selectors as arrays, then used eval('') in lieu of the selector list in the stylesheet: https://codepen.io/tomhodgins/pen/KgwVOR
If you don't want to add to JS to make use of this functionality, you can still set a selector to a variable in the first place you use it, then use eval('') thereafter to re-use the same list:
@element #portfolio > .fullWidth {
  eval('s = "#portfolio > .fullWidth"') {
    background: lime;
  }
  eval('s') {
    background: orange;
  }
}

This will work, everywhere that s is evaluated it will expand to the text: portfolio > .fullWidth. If you don't want to 'pollute' the global namespace by creating global variables, you can always define these selector lists inside the EQCSS object too, like eval("EQCSS.s =  …"), as long as you don't overwrite the existing objects in there like EQCSS.data and EQCSS.load, etc.
As for the redundant , I'm not sure what you're talking about. What's a  in this context? Where are there redundant ones? In general I'm not sure how much more development or new features will be added to EQCSS. Most of my active development is on these jsincss plugins, which do have smarter, more flexible ways to register these stylesheets and the events (and elements) they should be watching. The latest of these stylesheet loaders, jsincss also has enough smarts not to replace a stylesheet that is verbatim with what's already there. If you're looking for better performance and more innovation on top of what EQCSS started, check out the more recent plugins that are under active development! They're much smaller and easier to reason with, and more powerful on every front.

Thanks for your reply, but repeating the selector is cleaner for me than using eval.

As for the redundant , I'm not sure what you're talking about.

Please see https://github.com/eqcss/eqcss/issues/88 .

What's a  in this context?

There are three shown by the dev tools (please see the screenshot), and all three have the same content. Two of the three are redundant - that's bug 😀

So  is just a

  portfolio

    fullwidth

I used some of your earlier advice, the current state is at https://tobireif.com/ .
Thanks!

Regarding using element queries as part of js-in-css:
I'm not fundamentally against using JS for styling stuff, in some cases it's the best option. But eg for element queries I prefer writing them using the CSS-syntax, hoping that your syntax or something similar will be specd by the W3C and implemented natively by browser vendors. And I also like having them right there with my other styles and any media queries.


Update default value of minimum property in uui-slider

Description

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Chore (minor updates related to the tooling or maintenance of the repository, does not impact compiled assets)

Motivation and context

How to test?
Screenshots (if appropriate)
Checklist

[ ] If my change required a change to the documentation, I have updated the documentation in this pull request.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Good noticed, sorry we are moving things a bit round to get everything in good shape. Can I ask you to fix conflict, and then I will happily merge this :-)

@nielslyngsoe I didn't see any merge conflicts, but I have fetched latest changes from dev branch.


image is not up loading after login

after integrating the project  image is not uploading ... Giving error as image uploading failed

Hi! Can you be more specific about the error you are getting and provide more details about what your app/project configuration is about?


Nexus 4 crash on rotate when recording hint set to Still Only

Not so much a bug but a viable workaround.
The Nexus 7 2012 needs a recording hint of "Still Only" to record videos. This setting though cause the camera to stop recording on the front camera of the Nexus 4 when rotated from landscape to portrait or vice versa.
Creating a profile for the Nexus 7 2012 can avoid this.
Profile Title: cwac_camera_profile_asus_nakasi.xml
The XML:
<!--Nexus 7 2012-->
<deviceProfile>
      <recordingHint>
          STILL_ONLY
      </recordingHint>
</deviceProfile>

I'm pretty sure that I was able to record videos on the 2012 Nexus 7 without STILL_ONLY. What were your symptoms?

It would freeze as soon as the camera was started.

@mikescamell Sorry, but I cannot reproduce your problem. I have no difficulty recording videos using the demo app on a Nexus 7 2012 running Android 5.1. Can you reproduce this using the demo app?

I'll give it a go when i'm at work, but this honestly solved the issue i was having with it. It could obviously be due to my setup of your library.

I forgot, a colleague who was also having an issue with the Nexus 7 2012 also had to set it to STILL_ONLY.

@mikescamell It's also possible that the problem manifests on Android 5.0 (or something else the Nexus 7 2012 used to have) and not on 5.1. You're welcome to leave your fix in place, of course. I'm just hesitant to change the library to include this fix without having reproduced the problem.

Completely understandable :)
My Nexus 2012 has been updated to 5.1 so i'll give it a go when i get a chance and get back to you.

@commonsguy finally got a chance to test the Nexus 7 on 5.1.1. I could start and stop video recording but no videos seem to have been saved to the device and would occasionally get "stop failed" messages along with "Attempt to invoke virtual method 'void android.media.MediaRecorder.stop()' on a null object reference.

@mikescamell I cannot reproduce your problem. On a Nexus 7 (2012) running Android 5.1.1, in landscape, I can record videos off of the FFC without issue using the demo/ app. I am having difficulty seeing them via MTP (i.e., mounting external storage as a drive or volume), but they are there when viewed using adb shell ls /mnt/shell/emulated/0/Movies and the Android Device Monitor's file explorer.

Sorry @commonsguy i didn't realise vids were being stored in Movies, expected to see them in DCIM. Videos are in there but obviously that doesn't explain the errors i was getting above. First recording seems to work fine, but i get the previous messages on subsequent records/stops.
As to my STILL_ONLY issues, as you mentioned before it's obviously not worth implementing them if you and i both can record without freezing. I guess it must have been something i was setting in my CameraHost that was causing the issue. I'd look into it more but unfortunately i'm in the middle of a large project at work.
Apologies for wasting your time.

@mikescamell

First recording seems to work fine, but i get the previous messages on subsequent records/stops.

I did two recordings in succession and did not crash. Now, it's possible that I did something between those two recordings that somehow changed matters and therefore did not trigger the bug.

I'd look into it more but unfortunately i'm in the middle of a large project at work.

No worries. If you come up with steps to reproduce the crash, comment here and I can reopen the issue.


⚠ DesiTorrents has degraded performance

In 5cf667a, DesiTorrents ($DST) experienced degraded performance:

HTTP code: 200
Response time: 818 ms

Resolved: DesiTorrents performance has improved in 22bb011.


Check for previous/existing GitHub issues/module proposals

[X] I have checked for previous/existing GitHub issues/module proposals.

Check this module doesn't already exist in the module indexes

[X] I have checked for that this module doesn't already exist in the module indexes.

Bicep or Terraform?
Bicep
Module Classification?
Resource Module
Module Name
avm/utl/types/avm-common-type
Module Details
This module is based on @jtracey93's comment here, effectively proposing a module that just provides the most common AVM types as documented here.
As such, the module would exclusively contain types with the @export() annotation, one for each variant of our specs (with maybe the exception of e.g. tags)
Do you want to be the owner of this module?
Yes
Module Owner's GitHub Username (handle)
AlexanderSehr
(Optional) Secondary Module Owner's GitHub Username (handle)
No response

Hi @AlexanderSehr,
Thanks for requesting/proposing to be an AVM module owner!
We just want to confirm you agree to the below pages that define what module ownership means:

Team Definitions & RACI
Shared Specification (Bicep & Terraform)
Module Support

Any questions or clarifications needed, let us know!
If you agree, please just reply to this issue with the exact sentence below (as this helps with our automation 👍):
"I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER"
Thanks,
The AVM Core Team
#RR

Marking this as long term, until @AlexanderSehr is back from his annual leave.

Hi @AlexanderSehr,
Thanks for confirming that you wish to own this AVM module and understand the related requirements and responsibilities!
Before starting development, please ensure ALL the following requirements are met.
Please use the following values explicitly as provided in the module index page:

For your module:

ModuleName - for naming your module
TelemetryIdPrefix - for your module's telemetry

For your module's repository:

Repo name and folder path are defined in RepoURL
Create GitHub teams for module owners and contributors and grant them permissions as outlined here.
Grant permissions for the AVM core team and PG teams on your GitHub repo as described here.

Check if this module exists in the other IaC language. If so, collaborate with the other owner for consistency. 👍
You can now start the development of this module! ✅ Happy coding! 🎉
Please respond to this comment and request a review from the AVM core team once your module is ready to be published! Please include a link pointing to your PR, once available. 🙏
Any further questions or clarifications needed, let us know!
Thanks,
The AVM Core Team

Hey @matebarabas, small correction: I guess it should be avm-common-type (singular) not avm-common-types (plural) as per our specs?

PR ready for review: https://github.com/Azure/bicep-registry-modules/pull/3397

[x] Module published.
[x] GitHub teams are available and assigned to their parents.
[x] CODEOWNERS file updated.
[x] Issue template file updated.

Thank you for your work @AlexanderSehr!


Display player title in profile bar

It is often helpful to know what your title or position is during the experiment. If there is a title specified for the player player.get("title") then display it in the player profile bar (https://github.com/Watts-Lab/deliberation-empirica/blob/main/client/src/Profile.jsx)

Instead of "Time Remaining", replace it with the player's title and leave it blank if no title.
Before and after screenshots:


Start search on the current pane cwd location

If I have 3 panes, each with a different directory set with cwd, when I start monocle to search, it seems to be using only the last cwd in my layout file. Even if I change pane, it will keep the last cwd as the search path.
Ideally, it would be able to use the last focused pane's cwd.

Hey umm... isn't this already how it is in the latest Zellij and the latest Monocle? That's how it works for me...

For me, it's always using the directory from where I started the zellij session.
I'm using zellij 0.40.0 and the latest monocle.wasm

Edit : I think I got it, I wasn't closing the monocle floating pane so it didn't refresh with the new cwd

This issue I have with this is that one has to constantly close the existing floating pane when switching between directories.
When Monocle is started with --kiosk true --in-place, the behaviour is what I would want: the pane with Monocle instance immediately replaces itself with the opened file (effectively stopping the running Monocle instance), allowing for opening a "second" Monocle pane in a different directory. However, I would like to be able to open a floating pane with Monocle (helps me focus on the search better), search for a file and open the file in a new embedded pane, and automatically close the floating pane with the Monocle plugin running. This would allow to afterwards switch to another directory, and repeat, without having to close the running Monocle instance.
@imsnif Am I right that this use case is currently not possible?


Support for non-rectangular displays (e.g. notches)

What is missing?

Foundation 6 currently doesn't account for notches in displays.
As is also the case with the toolbar on the iPhone X for instance.
IMHO Foundation for Sites needs to support this out of the box as more devices with non-rectangular displays will emerge.
What is wrong now ?

Display notches and (iPhone) toolbars interfere with the layout.
Example of iPhone toolbar interfering with sticky bottom menubar:

Possible Solution

The use of css environment variables (user agent-defined constants) will solve the issue:

For iOS 11.0 - 11.2:
padding-top: constant(safe-area-inset-top);
padding-right: constant(safe-area-inset-right);
padding-bottom: constant(safe-area-inset-bottom);
padding-left: constant(safe-area-inset-left);

For later OSes:
padding-top: env(safe-area-inset-top);
padding-right: env(safe-area-inset-right);
padding-bottom: env(safe-area-inset-bottom);
padding-left: env(safe-area-inset-left);

For the environment variables to work viewport-fit=cover needs to be added to the content attribute of the <meta name="viewport"> tag e.g. <meta name="viewport" content="viewport-fit=cover">.

In my fork of Foundation for Sites I made some edits:
foundation.util.mediaQuery.js
line ~91 just before:
var self = this;
var $meta = $('meta.foundation-mq');

I added:
var $metaViewport =  $('meta[name="viewport"]');
var $metaViewportFit = $('meta[content*="viewport-fit=cover"]');
// add meta viewport tag if not present
if (!$metaViewport.length) {
  $('head').append('<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no, viewport-fit=cover">');
} else {
  // add viewport-fit=cover if not present which is mandatory for the use of css environment variables
  if (!$metaViewportFit.length) {
    $metaViewport.attr('content', (i, value) => \`${value || ""}, viewport-fit=cover\`);
  }
}

to make sure a correct meta viewport tag is present.
_global.scss
line ~161 just after:
body {
  margin: 0;
  padding: 0;

I added:
  // using environment variables to account for non-rectangular displays e.g. phones with notches
  padding-top: constant(safe-area-inset-top);
  padding-right: constant(safe-area-inset-right);
  padding-bottom: constant(safe-area-inset-bottom);
  padding-left: constant(safe-area-inset-left);

  padding-top: env(safe-area-inset-top);
  padding-right: env(safe-area-inset-right);
  padding-bottom: env(safe-area-inset-bottom);
  padding-left: env(safe-area-inset-left);

Extra suggestion
A mixin may be handy so that it can be applied to any element:
@mixin safe-padding($areas, $fallback:'') {
	$padding-no-env: 0;
	@if $fallback != '' {
		$padding-no-env: $fallback;
		$fallback: ", " + $fallback;
	}

	/* padding for browsers that do not support environment variables */
	@each $area in $areas {
		padding-#{$area}: #{$padding-no-env};
	}

	@supports (top: constant(safe-area-inset-top)){
		/* support for iOS 11.0 - 11.2 */
		@each $area in $areas {
			padding-#{$area}: constant(safe-area-inset-#{$area}#{$fallback});
		}
	}

	@supports (top: env(safe-area-inset-top)){
		@each $area in $areas {
			padding-#{$area}: env(safe-area-inset-#{$area}#{$fallback});
		}
	}
}

Usage examples:

body { @include safe-padding( top right bottom left ) }
output:

body {
  /* padding for browsers that do not support environment variables */
  padding-top: 0;
  padding-right: 0;
  padding-bottom: 0;
  padding-left: 0;
}
@supports (top: constant(safe-area-inset-top)) {
  body {
    /* support for iOS 11.0 - 11.2 */
    padding-top: constant(safe-area-inset-top);
    padding-right: constant(safe-area-inset-right);
    padding-bottom: constant(safe-area-inset-bottom);
    padding-left: constant(safe-area-inset-left);
  }
}
@supports (top: env(safe-area-inset-top)) {
  body {
    padding-top: env(safe-area-inset-top);
    padding-right: env(safe-area-inset-right);
    padding-bottom: env(safe-area-inset-bottom);
    padding-left: env(safe-area-inset-left);
  }
}

.className { @include safe-padding( top, 1rem ) }
output:

.className {
  /* padding for browsers that do not support environment variables */
  padding-top: 1rem;
}
@supports (top: constant(safe-area-inset-top)) {
  .className {
    /* support for iOS 11.0 - 11.2 */
    padding-top: constant(safe-area-inset-top, 1rem);
  }
}
@supports (top: env(safe-area-inset-top)) {
  .className {
    padding-top: env(safe-area-inset-top, 1rem);
  }
}

References:

MDN Web docs env()
CSS Tricks: “The Notch” and CSS

Context

I created a menubar to stick to the bottom of the screen. It turned out the menubar got stuck behind the toolbar of the iPhone X and was therefore unusable
After doing some research, I found out the same problem arises with notches in displays.
Your Environment

Foundation version(s) used: 6.6.3
Browser(s) name and version(s): Any
Device, Operating System and version: any device with non-rectangular displays e.g. with notches in its display

Checklist

[x] I have read and follow the CONTRIBUTING.md document.
[x] There are no other issues similar to this one.
[x] The issue title and template are correctly filled.

Related: https://github.com/foundation/foundation-sites/issues/11188

Yes, I saw that one too after I posted.
I apologize, it's because of a spelling error (nodge instead of notch) that I didn't find it before posting...
I still think it's a good idea since I expect more devices with non-rectangular displays to come in to existance.
Devices with rounded corners on displays, or round displays you currently see on smartwatches, but larger. And even notches might resurface. And what about device attributes such as toolbars that may interfere...
A variable to turn on or off as was mentioned in that post could work as a compromise, but that's only for people that work with Sass.
For the time being I'll use my mixin :)

I apologize, it's because of a spelling error (nodge instead of notch) that I didn't find it before posting...

No problem, I just link the issue so all relevant details are available and others can check both issues.

In my fork of Foundation for Sites I made some edits:

The changes look good. A PR is very welcome.

In my fork of Foundation for Sites I made some edits:

The changes look good. A PR is very welcome.

PR #12199


fix line serialization

breaking: Line.to_dict() outputs a dictionary, where the element elements is another dictionary
Line.from_dict() accepts both the legacy input where elements is a list (and where element_names are the respective names), and the present input where elements is a dict, and where element_names contains names (possibly repeated) ordering the members of elements

Addresses xsuite/xsuite#149

merged manually into release/v0.18.0


Unit test fixes

Fix bug in lport group umem setup
Fix bug in jcfg test that exits early if a file cannot be parsed
Fix pktcpy test and disable color output when using meson test since it writes to a file, not a terminal
Update the GitHub Smoke test action to upload the resulting testlog.txt to help debug errors

Smoke test isn't running since upload-artifact isn't allowed in the allowed actions list. I updated that, but there's no way to re-run a failed job that failed because of a disallowed action. I'm going to close and re-open to see if the CI runs.


Multiple file upload over https hangs

I've downloaded the master files and run the demo on IIS 8.5 and IIS 10.0. Everything is working fine on http. If I try to upload multiple files on https the upload progress (overall progress bar and every single file's progress bar) hangs after a while (After ~2MB total upload). The upload progress goes on with long delays. 5 files (Total ~4 MB) take 7 mins to upload.
maxAllowedContentLength and maxRequestLength values are set as max on IIS. I couldn't find out what the problem is.

I found what the problem is. It's about HTTP/2 Protocol. I had to disable it. Then worked fine.
You can try it with chrome --disable-http2

Thanks for the report @senolkulbay.
This sounds more like an issue with IIS and not with this project, as this is not reproducible for me on the demo or the provided Docker environment.
I'll close this for now, but feel free to comment if you believe this assessment is incorrect.


Package is not available on NPM

Error message:
$ npm install --save gatsby-transformer-remark gatsby-remark-bibliography bibtex-parse-js
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/gatsby-remark-bibliography - Not found
npm ERR! 404
npm ERR! 404  'gatsby-remark-bibliography@latest' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

Installing from Github works:
npm install --save https://github.com/ptigas/gatsby-remark-bibliography


Reset password without exception

If PHPMailer is not configured, reset password service do not throw exception.

Resolved as shown in the example:
https://github.com/PHPMailer/PHPMailer#a-simple-example


Added RedHat provisioning script - tested on RHEL 7.1

Looks good. Thanks for adding instructions for RHEL!


Writing a ChunkedStream may pause until there is no more input

Netty version: 3.10.0.Final
Context:
Chunked downloads of a large InputStream can lag writing data to the client until the whole stream is read if the socket's output buffer becomes full.
To reproduce:

Start the below application
Run wget -S 'http://localhost:8080/index'

At some point during the download, it should stop receiving data.  I've had it happen as early as 0% (<3Mb) or as late as 100MB into the transfer. If you wait long enough, the InputStream will finish being read and the download will very quickly complete, sending the remaining data in a very short amount of time.
If you remove the line bootstrap.setOption("child.sendBufferSize", 65536);, it may not freeze. If you add a break point at Line 222 of AbstractNioWorker, you'll catch the threads when the problem manifests.
Example application:
package io.netty;

import org.jboss.netty.bootstrap.ServerBootstrap;
import org.jboss.netty.channel.*;
import org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory;
import org.jboss.netty.handler.codec.http.*;
import org.jboss.netty.handler.stream.ChunkedStream;
import org.jboss.netty.handler.stream.ChunkedWriteHandler;

import java.io.IOException;
import java.io.InputStream;
import java.net.InetSocketAddress;
import java.util.Random;
import java.util.concurrent.Executors;

public class Example {
    public static class VeryLargeStream extends InputStream {
        public static int LIMIT = 500000000;
        private int pos = 0;
        private Random random = new Random(1L);

        @Override
        public int read() throws IOException {
            pos++;
            if (pos % 1000000 == 0) try {
                Thread.sleep(random.nextInt(500));
            } catch (InterruptedException e) {}
            return pos <= LIMIT ? 0 : -1;
        }

        @Override
        public int available() throws IOException {
            return LIMIT - pos > 0 ? random.nextInt(LIMIT - pos) : 0;
        }
    }

    public static class ExampleHandler extends SimpleChannelUpstreamHandler {
        private int FIVE_KB_CHUNK_SIZE = 5 * 1024;

        @Override
        public void messageReceived(ChannelHandlerContext ctx, MessageEvent e) throws Exception {
            if (e.getMessage() instanceof HttpRequest) {
                DefaultHttpResponse response = new DefaultHttpResponse(HttpVersion.HTTP_1_1, HttpResponseStatus.OK);
                response.setChunked(true);
                response.headers().set(HttpHeaders.Names.TRANSFER_ENCODING, HttpHeaders.Values.CHUNKED);
                response.headers().set(HttpHeaders.Names.CONTENT_LENGTH, VeryLargeStream.LIMIT);
                e.getChannel().write(response);
                e.getChannel().write(new ChunkedStream(new VeryLargeStream(), FIVE_KB_CHUNK_SIZE));
            } else {
                super.messageReceived(ctx, e);
            }
        }
    }

    public static void main( String[] args ) {
        int port = 8080;
        String host = "<IP_ADDRESS>";

        NioServerSocketChannelFactory socketChannelFactory = new NioServerSocketChannelFactory(
                Executors.newCachedThreadPool(),
                Executors.newCachedThreadPool());

        ServerBootstrap bootstrap = new ServerBootstrap(socketChannelFactory);

        bootstrap.setPipelineFactory(new ChannelPipelineFactory() {
            @Override
            public ChannelPipeline getPipeline () {
                ChannelPipeline pipeline = Channels.pipeline();
                pipeline.addLast("HttpRequestDecoder", new HttpRequestDecoder());
                pipeline.addLast("HttpChunkAggregator", new HttpChunkAggregator(1 * 1024 * 1024));
                pipeline.addLast("HttpResponseEncoder", new HttpResponseEncoder());
                pipeline.addLast("Streamer", new ChunkedWriteHandler());
                pipeline.addLast("ExampleHandler", new ExampleHandler());

                return pipeline;
            }
        });

        bootstrap.setOption("child.sendBufferSize", 65536);

        bootstrap.bind(new InetSocketAddress(host, port ));
    }
}

$ java -version
java version "1.7.0_65"
OpenJDK Runtime Environment (IcedTea 2.5.3) (7u71-2.5.3-0ubuntu<IP_ADDRESS>)
OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)

Operating system: Ubuntu Linux 14.04.1 64-bit
$ uname -a
Linux myhost 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

A few more details on this:
The problem doesn't occur because of changing the sendBufferSize, that simply encourages the problem. (I was able to reproduce it without changing the sendBufferSize, although less frequently.)
It seems to occur when the AbstractNioWorker isn't able to transfer a full buffer's worth of bytes into the WriteableByteChannel.  It drops into this else block and suspends writing to the channel.
While that seems like the right thing to do for a time, it doesn't actually restart sending data over the socket until the rest of the InputStream is read.  (Subsequent calls to write and eventually sendDownStream eventually get to line 139 in AbstractNioWorker.) In the case of a very large file (or a slow or infinite stream), the client request may time-out because it hasn't received any data in a very long time.

I did some testing with Netty 4.0.25.Final and can confirm that this is not an issue as of that version.  NioSocketChannel doesn't use the writeSuspend flag like 3.x did, which resolves the issue.
Please feel free to close this if you have no plans to address this in the 3.x branch.

Thank you for your patience @mfulgo. Let me close this issue for now.

This is was also fixed in the 3.10 branch, as of version 3.10.2.Final.  I'm pretty sure it was fixed by https://github.com/netty/netty/commit/452df0454d34fdd5e0022f40c20ad7c45e7f1895

That's great. Thanks for following-up, @mfulgo


add fast path for specific assigns

this should considerably speed up xt::zeros and xt::ones
I would like to use the same methods for assigning reducers (and accumulators, should we ever have lazy ones :)
What do you think @JohanMabille @SylvainCorlay @ukoethe ?

fantastic, even the tests pass now :)

@SylvainCorlay shall we merge this?


Fixed issue of extra margins in create image modal (bsc#1086354)

The create image modal -> metadata sub headings have some extra margins
which is caused by the login page logo styling overwritten.

screen shot after fix

screenshot before fix

@rsalevsky  can I get added to the project collaborators for this to gain +2 ability? thanks!


Semantic HTML

Semantic HTML
User Story
AS A marketing agency,
I WANT a codebase that follows accessibility standards,
SO THAT our own site is optimized for search engines.
Acceptance Criteria
GIVEN a webpage meets accessibility standards,
WHEN I view the source code,
THEN I find semantic HTML elements.

Semantic HTML was added, as was a functioning id for the search-engine-optimization menu item.


NIFI-7572: Force ScriptedTransformRecord to recompile the script when started

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
The reference to the compiled script was not being cleared out before restarting the processor, so any changes made to the script were not applied. This PR simply resets the compiled script to null when the processor is scheduled.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically main)?

[x] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[x] Have you written or updated unit tests to verify your changes?
[x] Have you verified that the full build is successful on JDK 8?
[ ] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Reviewing...

Sorry for the delay, had some unrelated test failures occurring because of networking changes on my machine. Verified the expected behavior, contrib-check, and all tests. Thanks Matt.


Report Error : object of type 'generator' has no len()

D:\test>nuitka --version
<IP_ADDRESS>
3.7.0 (v3.7.0:1bf9cc5093, Jun 27 2018, 04:59:51) [MSC v.1914 64 bit (AMD64)]
D:\Python37\python.exe

D:\test>nuitka hello.py
scons: *** [hello.build__constants.obj] TypeError : object of type 'generator'
has no len()
Traceback (most recent call last):
File "D:\Python37\lib\site-packages\nuitka\build\inline_copy\bin..\lib\scons-
3.0.1\SCons\Taskmaster.py", line 241, in execute
if not t.retrieve_from_cache():
File "D:\Python37\lib\site-packages\nuitka\build\inline_copy\bin..\lib\scons-
3.0.1\SCons\Node\FS.py", line 2925, in retrieve_from_cache
return self.get_build_env().get_CacheDir().retrieve(self)
File "D:\Python37\lib\site-packages\nuitka\build\inline_copy\bin..\lib\scons-
3.0.1\SCons\Environment.py", line 1016, in get_CacheDir
cd = SCons.CacheDir.CacheDir(path)
File "D:\Python37\lib\site-packages\nuitka\build\inline_copy\bin..\lib\scons-
3.0.1\SCons\CacheDir.py", line 163, in init
if os.path.isdir(path) and len(f for f in os.listdir(path) if os.path.basena
me(f) != "config") != 0:
TypeError: object of type 'generator' has no len()

Hello.py
print("Hello")

Seems my attempt to fix that scons issue is not working properly. I pushed a fix to factory and will include it in the next release, early next week. It's a race. If you put the len() expression in [] brackets, it will work for you.

This is in the current pre-release which is become a release any day now, closing therefore.


Fix the API docs of install_jax

Description
Changed the >>> prompt to a text prompt and provided instructions on how to run the command in the terminal, to prevent mistakenly running the docstring in the Python interpreter.
Fixes #2728
Type of change
Please add a line in the relevant section of CHANGELOG.md to document the change (include PR #) - note reverse order of PR #s. If necessary, also add to the list of breaking changes.

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

Key checklist:

[x] No style issues: $ pre-commit run (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
[X] All tests pass: $ python run-tests.py --all
[X] The documentation builds: $ python run-tests.py --doctest

@Saransh-cpp  @tinosulzer. This PR is ready for review and can be merged.

Thanks, @jeromtom! A minor change -
The docstring of install_jax renders weirdly on the website. You might need to check how other docstrings are written and format this one accordingly. I think you can get rid of -
Command Line Interface:
-----------------------

The rendered docs - https://pybamm--2729.org.readthedocs.build/en/2729/source/api/util.html

Command Line Interface is rendered as a sub-heading. https://docutils.sourceforge.io/docs/user/rst/quickref.html

Removing the underscore string would fix it. Doing it now.

@Saransh-cpp, looks better now rt?

@jeromtom I hope you are building the docs locally to visualize your changes -
cd docs
make clean
make html

instead of relying on the RTD action.
Also, some general open-source tips -

While it is okay to have a messed up git commit history, your commit messages should be meaningful (and not Update file.name)
PR titles should ideally describe the changes done in the PR (something like "Fix the API docs of install_jax")

I didn't do it yet. Will do it soon. Thanks for the tips.

How do I fix this?

Have you installed pybamm from the source?

Yes

Hey, I have fixed the error, working on the PR now.

I have fixed the issue but will have to create a new PR.

Jnkjnfjwnekjf

@Saransh-cpp, thank you for the approval. There is one codecov failing check, noticed that some of the earlier merged PRs had this test failing. Is there anything I can do to fix it?

In this case it's not related to your changes, sometimes it gets it wrong when another PR is merged in between


Pandas inplace argument is not  explicit True or False

Any Serie or DataFrame method with arguments inplace != [0, False, None, [], {}] process inplace operation.
Is not explicit True or False like in the documentation.
Other methods tested: where, mask, sort_index
Any bool(arg) == True is accepted
Like: inplace='Fail' , inplace=3, inplace=[0]
Maybe is not a bug, but can generate problems if someone is not careful using positional arguments, like me.
Code Sample, a copy-pastable example if possible
df = pd.DataFrame({'A': [1, 2, 3], 'B': [4, 5, 6], 'C': [7, 8, 9]})
df.where(lambda x: x > 4, lambda x: x + 10, 'fail')

Expected Output
Out[72]:
    A   B  C
0  11  14  7
1  12   5  8
2  13   6  9

output of pd.show_versions()
pd.show_versions()

INSTALLED VERSIONS
------------------
commit: None
python: 2.7.11.final.0
python-bits: 64
OS: Windows
OS-release: 7
machine: AMD64
processor: AMD64 Family 18 Model 1 Stepping 0, AuthenticAMD
byteorder: little
LC_ALL: None
LANG: None

pandas: 0.18.1
nose: 1.3.7
pip: 8.1.2
setuptools: 25.1.6
Cython: 0.23.4
numpy: 1.11.1
scipy: 0.18.0
statsmodels: 0.6.1
xarray: 0.8.1
IPython: 5.1.0
sphinx: 1.3.5
patsy: 0.4.1
dateutil: 2.5.1
pytz: 2016.2
blosc: None
bottleneck: 1.1.0
tables: 3.2.2
numexpr: 2.6.1
matplotlib: 1.5.1
openpyxl: 2.3.2
xlrd: 0.9.4
xlwt: 1.0.0
xlsxwriter: 0.8.4
lxml: 3.6.0
bs4: 4.4.1
html5lib: 0.999
httplib2: None
apiclient: None
sqlalchemy: 1.0.12
pymysql: None
psycopg2: None
jinja2: 2.8
boto: 2.39.0
pandas_datareader: 0.2.0

Interesting -- I agree that this is a little misleading. Unless this is the expected/desired behavior or someone has worked on fixing it already, I'd love to see if I can help. I'm a new contributor and looking for something to get my feet wet with. Would love to get the input of someone with more experience before digging in. My initial thought was a common function enforce_bool_type that checks that the value is of type bool before returning, raising a TypeError otherwise, and changing if bool_value to if enforce_bool_type(bool_value) throughout the code base. Would love feedback!

sure this is possible, you can just do:
if not is_bool(inplace):
    raise ValueError(....nice error message...)

with some tests would be great

great, thanks @jreback !

For example in where method here.
For me explicit would be: if inplace == True:
But I'm only a panda's user, i don't know nothing how it works.

The same holds for the copy argument. Also not explicit.


a11y

We need content to help people build skills on web accessibility

Free Google/Udacity Course here: https://www.udacity.com/course/web-accessibility--ud891


Issue 380 fix : move postinstall script to presecurity:test

Fixes #380, but showed that #383 should be fixed as well for testing it on popular linux distributions ( at least ubuntu-based plus arch-based ones).

Coverage remained the same at 96.159% when pulling 147a6dea82d5487c3b3965c6e86eaf3d3dda5daa on issue-380-postinstall-fails into 64f45e949a3e5e1cf02c591a64624e88ed4870f4 on master.

Coverage remained the same at 96.159% when pulling 2ceb669a451d87e9bafa6f599fbb33ca5e118534 on issue-380-postinstall-fails into 64f45e949a3e5e1cf02c591a64624e88ed4870f4 on master.


Detail Window is still open

I wonder if this a feature or a bug :)
Step #1: Open a Tab and do run some commands
Step #2: Open a Second tab, list some services and see everything in the details window (right side).
...Then close the Details Window.

I've notice back on the first Tab, the details windows is still open.

hi @maltron thanks for this issue, keep them coming!
this is indeed a feature: Kui has a separate sidecar for every tab. we have thought about making the sidecar global. which would you prefer?

@starpit Thanks for getting back to me. I usually use the sidecar to investigate details of a particular resource in that particular tab.
So my vote will be NOT making globally available.
Of course, as an alternative, one could think of a checkbox that it would make globally available. (similar on what some Desktop Windows offers: Available on all workspaces).

ah, i see. this is actually a regression from the work to port the sidecar over to React componentry. we'll look into it! thanks again!

this should be fixed in 8.6.1


fix(artifacts): remove directory-only restriction on path_prefix

Description

Related to WB-18778

Accept path prefixes that correspond to non-directory path names, e.g. path_prefix=xzy will match xzy-file.txt. Our current implementation only allows complete directory names to be specified, which doesn't match how we've explained the feature to users

Update the docstring to explain usage

Simplify the implementation by removing abstraction around checking the path prefix (we don't check anything else, so it's misleading to hide it in a should_download method)

Add system test for downloading partial artifacts

[x] I updated CHANGELOG.md, or it's not applicable

Testing

Removes the unit tests for the (deleted) abstractions for checking path prefix
Adds a system-test to ensure download with path_prefix works as-expected [note: disabled for core until #7640 is merged]

Also it seems that this change doesn’t work in wandb-core any plans to enable this test?

Yes, in https://github.com/wandb/wandb/pull/7640

Also it seems that this change doesn’t work in wandb-core any plans to enable this test?

Yes, in #7640

Ah thanks!


Fixes flutter_test deprecations

Updates minimum version of golden_toolkit to remove reference to deprecated addTime method.

Resolves #1210

Just to add context:

Here's the flutter PR removing the deprecations that causes the issue
Here is the output from the failing test when the addTime method is removed.

Dashboard
Output

Here's the fix for the issue in the golden_toolkit repo, which was published in version 0.13.0.

I was able to reproduce the test failure locally with the modified version of flutter and pinning the version of golden_toolkit to 0.11.0, and confirmed locally that updating the minimum version of golden_toolkit to 0.13.0 resolves the test failures.

@angelosilvestre can you cherry pick this to stable?


[1.10] Train 230

This is train 230 meant for the 1.10.1 release. It includes the following pull requests:

#1908 (Add cluster ID to diagnostics bundle for 1.10)
#1959 (dcos_installer: Don't run genconf validation twice [1.10 backport])
#1972 (Bump DC/OS version to 1.10.1)

@mesosphere-mergebot bump-ee

teamcity/dcos/test/docker/smoke  failure is handled/discussed here: https://jira.mesosphere.com/browse/DCOS_OSS-1681

@mesosphere-mergebot bump-ee


[BUG]:Drizzle-Kit 0.19.0 Fails to Generate Migrations

What version of drizzle-orm are you using?
0.27.0
What version of drizzle-kit are you using?
0.19.0
Describe the Bug
I was using Drizzle Kit version of 0.18.1 and generating migrations with this command.
drizzle-kit generate:pg --config=drizzle.config.ts
As soon as I updated drizzle-kit to 0.19.0 version this command doesn't work anymore throwing the error
TypeError [ERR_INVALID_RETURN_PROPERTY_VALUE]: Expected a url string to be returned for the "url" from the "drizzle-kit/loader.mjs 'resolve'" function but got instance of String.
Expected behavior
No response
Environment & setup
No response

Can you show you drizzle.config.ts file?

import type { Config } from 'drizzle-kit';

if (!process.env.DATABASE_URL) {
  throw new Error('DATABASE_URL is missing');
}

export default {
  schema: './db/schema.ts',
  out: './db/migrations',
  connectionString: process.env.DATABASE_URL,
} satisfies Config;

Will add an error for deprecated Config keys in a patch release. 1-2 hours
But the reason is that there are breaking changes in 0.19.0 release. You can check the release notes for that: https://github.com/drizzle-team/drizzle-kit-mirror/releases/tag/v0.19.0
You need to write it this way now
import type { Config } from 'drizzle-kit';

if (!process.env.DATABASE_URL) {
  throw new Error('DATABASE_URL is missing');
}

export default {
  schema: './db/schema.ts',
  out: './db/migrations',
  driver: 'pg',
  dbCredentials: {
    connectionString: process.env.DATABASE_URL,
  }
} satisfies Config;

Unfortunately, the error still persists. I'm using the same schema and migration generate command as before in 0.18.1 and have updated the drizzle.config.ts as you have mentioned, but am still getting an error.
Here is the link to the repo if somebody wants to inspect it.

So, I just cloned your repo, and it worked fine for me. The only thing I've added is import 'dotenv/config' to make sure that the connection string was in the environment variables.
import type { Config } from 'drizzle-kit';
import 'dotenv/config'

if (!process.env.DATABASE_URL) {
  throw new Error('DATABASE_URL is missing');
}

export default {
  schema: './db/schema.ts',
  out: './db/migrations',
  driver: 'pg',
  dbCredentials: {
    connectionString: process.env.DATABASE_URL,
  },
} satisfies Config;

and did get the migrations generated

I'm also getting this error, am on Windows 11 if that helps. Never used drizzle before I just copied the config from the docs.

Yes. I've just spin up a new VM instance (linux) and everything works fine. Something strange is going on my machine (windows), so I decided to downgrade kit and orm and everything works again.

Also dealing with this, using windows 11

Thanks we’re fixing that. Seems like it’s an issue with a Windows only
Will update you here after fix is ready

The temporary solution I used was to just switch WSL. This obviously won't work for everyone and every project. So far no more issues.

@AndriiSherman also experiencing this error when using with SST
import type { Config } from "drizzle-kit";

const connection = {
  connectionString: process.env["SST_Secret_value_NEON_CONNECTION_STRING"]!,
};

export default {
  out: "./migrations/",
  schema: "./src/db/schema.sql.ts",
  driver: "pg",
  dbCredentials: {
    connectionString: connection.connectionString,
  }
} satisfies Config;

Even tried this but same error:
import type { Config as DrizzleConfig } from "drizzle-kit";
import { Config } from "sst/node/config";

const dbConfig = {
  out: "./migrations/",
  schema: "./src/db/schema.sql.ts",
  driver: "pg",
  dbCredentials: {
    connectionString: Config.NEON_CONNECTION_STRING,
  }
} satisfies DrizzleConfig;

export default dbConfig;

Error screenshot:

@xinha-sh update ESBuild, fixed for me

@miljan-code @TiltedToast can you please try drizzle-kit@win

@AlexBlokh still getting an error.
TypeError [ERR_INVALID_RETURN_PROPERTY_VALUE]: Expected undefined or a fully resolved  URL string to be returned for the "responseURL" from the "drizzle-kit/loader.mjs 'load'" function but got instance of String.

@miljan-code what version of node?

@AlexBlokh 18.16.0

@AlexBlokh Tried it out with the new version, getting a different error now
> drizzle-kit push:mysql --config ./src/db/drizzle.config.ts

node:internal/process/esm_loader:97
    internalBinding('errors').triggerUncaughtException(
                              ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@esbuild-kit/esm-loader' imported from E:\coding-projects\hifumi-js\
Did you mean to import @esbuild-kit+esm-loader<EMAIL_ADDRESS>    at new NodeError (node:internal/errors:399:5)
    at packageResolve (node:internal/modules/esm/resolve:889:9)
    at moduleResolve (node:internal/modules/esm/resolve:938:20)
    at defaultResolve (node:internal/modules/esm/resolve:1153:11)
    at nextResolve (node:internal/modules/esm/loader:163:28)
    at ESMLoader.resolve (node:internal/modules/esm/loader:838:30)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
    at ESMLoader.import (node:internal/modules/esm/loader:525:22)
    at initializeLoader (node:internal/process/esm_loader:75:58)
    at loadESM (node:internal/process/esm_loader:90:11) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Node.js v18.16.0

Can confirm that I am getting the same on Mac.
Using latest version 0.19.0
Latest config and everything based on the new release notes.

I have my schema split into multiple files and that causes it to now fail with Error [ERR_MODULE_NOT_FOUND]. If I move everything into 1 schema file, then it starts working, but only if I'm not importing anything from a another file (e.g. ./shared)

@amosbastian please try npm i -D drizzle-kit@win

It now gives:
/Users/amosbastian/Development/project/libs/db/src/lib/schema/chat.ts:1
import { InferModel, relations } from "drizzle-orm";
^^^^^^

SyntaxError: Cannot use import statement outside a module

if (!process.env.DATABASE_URL) {
  throw new Error('DATABASE_URL is missing');
}

This problem was fixed when I downgraded to 0.18 version of drizzle-kit.

only way to fix for now urgent devs is to migrate to old version: check out this repo https://github.com/gitdagray/nextjs-mysql-drizzle/blob/main/package.json
and update the package.json run npm i or yarn.

I am surprised to see that drizzle-kit is not open-source.

The latest version drizzle-kit@cjs from this morning finally fixed the issue for me.

we've rolled back ESM support and we'll keep it in a separate branch until we find a proper way for everybody to use

I'm having a different error. Using drizzle-kit 0.19.1 on Node.js v18.16.0
Running drizzle-kit generate throw this error
node:internal/errors:490
    ErrorCaptureStackTrace(err);
    ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'esbuild' imported from /Users/ranyefet/Code/feature-flags-service/node_modules/drizzle-kit/loader.mjs
    at new NodeError (node:internal/errors:399:5)
    at packageResolve (node:internal/modules/esm/resolve:889:9)
    at moduleResolve (node:internal/modules/esm/resolve:938:20)
    at defaultResolve (node:internal/modules/esm/resolve:1153:11)
    at nextResolve (node:internal/modules/esm/loader:163:28)
    at ESMLoader.resolve (node:internal/modules/esm/loader:838:30)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:77:40)
    at link (node:internal/modules/esm/module_job:76:36) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Am I supposed to install esbuild separately?

@ranyefet could you please reinstall cjs and try 1 more time?

It fixes it for me 👍 thanks!

We've decided to rollback ESM support for drizzle-kit, as it was causing a lot of issues on Windows and some issues on Mac. We want to unblock drizzle-kit and give all of you the opportunity to get new ORM and kit updates.

Note: all new features will be still available. We just rollbacked esm settings that we thought should work

We have gathered a lot of feedback, and errors have appeared. Additionally, we have managed to set up proper test environments for Windows, Mac, and Linux, which has been really helpful.
We will be working on improvements on another branch at a pace that suits us, so that we can ensure we are not blocking anyone here.
Thank you all for your patience and for reporting the issues and sharing information!
The rollback is already available under the drizzle-kit@cjs tag and will be included in the latest version today

@RIP21 it shouldn't be a problem, the only thing we don't support is top level await
can you please provide a sample repo so I can have a look?

repro-drizzle-kit.zip
Here you have it :)
pnpm install
pnpm generate-migration

hmmmm, I see

I'm experiencing the same issue as @RIP21 with v0.19.13, both push and generate are failing with Error: Cannot find module

Having problems generating and the drizzle-kit@cjs doesn't seem to solve it. Any ideas?
NodeJS-version: 20.5.1
NPM-version: 10.0.0
Computer: MacBook Pro M1
Package.json: "scripts": {     ...     "generate": "drizzle-kit generate:pg --config=drizzle.config.ts",   },   ...   "dependencies": {     "dotenv": "^16.3.1",     "drizzle-orm": "^0.27.0",     "express": "^4.18.2",     "pg": "^8.11.3",     "postgres": "^3.3.5"   },   "devDependencies": {     ...     "@types/pg": "^8.10.2",     "drizzle-kit": "^0.19.2-0fc6b10",     "ts-node": "^10.9.1"   }

The problem appears to be related to ESBUILD's inability to properly transform the schema file into the CommonJS (CJS) format.
I encountered this issue while working on a personal project using Next.js and the Cloudflare D1 SQLite database.
Initially, I attempted to run a migration by targeting a migrations folder and splitting table definitions across multiple files. However, this resulted in the error: "Transforming const to the configured target environment ("es5") is not supported yet."
I then installed the drizzle-kit using the @cjs tag, but this did not resolve the issue.
I also attempted to consolidate all table definitions into a single schema file, but I encountered the same error.
I manually converted a single table definition to CommonJS syntax and changed the extension of my schema file from "schema.ts" to "schema.cjs." After making this change, the migration ran successfully.
Additionally, I noticed that the auto-generated tsconfig.json file for Next.js had its compilerOptions.target set to "es5." To investigate whether ESBUILD might be using my root directory's tsconfig.json as a parameter for the compilation target, I changed this value to "ESNext." I then attempted to run the migration again using the original setup (TypeScript files in a schema folder, each containing a table definition). This time, the migration ran successfully, and all tables and columns were created as expected.

The problem appears to be related to ESBUILD's inability to properly transform the schema file into the CommonJS (CJS) format.
I encountered this issue while working on a personal project using Next.js and the Cloudflare D1 SQLite database.
Initially, I attempted to run a migration by targeting a migrations folder and splitting table definitions across multiple files. However, this resulted in the error: "Transforming const to the configured target environment ("es5") is not supported yet."
I then installed the drizzle-kit using the @cjs tag, but this did not resolve the issue.
I also attempted to consolidate all table definitions into a single schema file, but I encountered the same error.
I manually converted a single table definition to CommonJS syntax and changed the extension of my schema file from "schema.ts" to "schema.cjs." After making this change, the migration ran successfully.
Additionally, I noticed that the auto-generated tsconfig.json file for Next.js had its compilerOptions.target set to "es5." To investigate whether ESBUILD might be using my root directory's tsconfig.json as a parameter for the compilation target, I changed this value to "ESNext." I then attempted to run the migration again using the original setup (TypeScript files in a schema folder, each containing a table definition). This time, the migration ran successfully, and all tables and columns were created as expected.

I still don't get mine to work. Removed the node_modules folder and re-installed. But the only thing you had to do was to change the target of the tsconfig.json target to "ESNext"?. Did you still use the drizzle-kit@cjs package?

Additionally, I noticed that the auto-generated tsconfig.json file for Next.js had its compilerOptions.target set to "es5." To investigate whether ESBUILD might be using my root directory's tsconfig.json as a parameter for the compilation target, I changed this value to "ESNext." I then attempted to run the migration again using the original setup (TypeScript files in a schema folder, each containing a table definition). This time, the migration ran successfully, and all tables and columns were created as expected.

I still don't get mine to work. Removed the node_modules folder and re-installed. But the only thing you had to do was to change the target of the tsconfig.json target to "ESNext"?. Did you still use the drizzle-kit@cjs package?

My tsconfig.json already has target: "ESNext" and it doesn't work so might not be a fix for everyone.

I created a minimal reproduction repository scaffolding a NextJS project to attempt isolating what is definitely solving things on my end.
This time I just installed the latest versions of both drizzle-orm and drizzle-kit using pnpm i drizzle-orm and pnpm i -D drizzle-kit and tried generating migrations without changing anything other than creating the migrations folder itself and running "generate": "drizzle-kit generate:sqlite --schema=./src/database/schema --out=./migrations" with pnpm run generate.
This resulted in the same error as before: Transforming const to the configured target environment ("es5") is not supported yet
I then changed tsconfig.json target field from target: "es5" to target: "ESNext and ran pnpm run generate again, this time the migrations ran successfully.
Here is the minimal reproduction repo: https://github.com/oparin10/drizzle-kit-repro
Try cloning the repo onto your machine, installing the packages with your package manager then run the generate command defined in the package.json to see if the migrations run on your machine so we can compare results.
I'm currently on:
Node version: v19.9.0
OS:  Arch Linux (WSL2)
Like previously mentioned, this might not be a fix for every case, but at least it's a possible fix for some until there is final solution.

I created a new branch in the reproduction repository where I reverted the tsconfig.json compilerOptions.target change to es5 and exported all schema definitions declaring the variables with var instead of const.
From this:
import { integer, sqliteTable as table, text } from "drizzle-orm/sqlite-core";

export const company = table("company", {
  id: integer("id").primaryKey(),
  name: text("name").notNull(),
});

To this:
import { integer, sqliteTable as table, text } from "drizzle-orm/sqlite-core";
// just changed to "const" to "var"
export var company = table("company", {
  id: integer("id").primaryKey(),
  name: text("name").notNull(),
});

This enabled me to generate migrations without any issues, even without changing my tsconfig.json settings.
Just leaving this update in case this works for someone else having the same issue.
Here is the repo branch where I committed this workaround to: https://github.com/oparin10/drizzle-kit-repro/tree/export-var

I encountered this issue while using ban, and I tried the solutions mentioned above, but none of them worked. The only way I found to resolve the problem was to roll back Node to version 16.20.2. Is there any other solution that doesn't require this?

I had the same problem.
I temporarily set the target to ESNext  and imported dotenv/config since process.env does not get populated when running the script.
I hope this gets fixed soon

Can someone help me with this error please? I tried to run the following code: npm run generate  but I get this:
$ npm run generate

><EMAIL_ADDRESS>generate
> drizzle-kit generate:pg

""-S"" is not recognized as an internal or external command, operable program or batch file

this is my package.json:
{
  "name": "server",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "build": "tsc",
    "dev": "ts-node src/index.ts",
    "start": "node dist/index.js",
    "start:prod": "NODE_ENV=production ts-node src/index.ts",
    "generate": "drizzle-kit generate:pg",
    "migrate": "ts-node migrate"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "dependencies": {
    "dotenv": "^16.3.1",
    "drizzle-orm": "^0.28.6",
    "express": "^4.18.2",
    "pg": "^8.11.3",
    "postgres": "^3.4.1"
  },
  "devDependencies": {
    "@types/express": "^4.17.20",
    "@types/node": "^20.8.9",
    "@types/pg": "^8.10.7",
    "drizzle-kit": "^0.19.0",
    "ts-node": "^10.9.1"
  }
}

Changing the "const" to "var" works pretty well, I'm running on Windows 10.


Query Manager - save logs to files - no file is created

Hello,
I am not sure, how "Save logs to a file" functionality works. Should it create log file after Query is run?
Because it doesn't create a file for me.

So how do I get logs to a file?
Thank you.

You need to restart DBeaver for these changes to take effect.
I'll add info about that on prefs page.


[Feature] Improve dark mode toggle button

Description
Currently the dark mode button is a simple one and there is dark mode written on the side of it.
Instead, I wanna add dark mode icon and light mode icon for dark mode and light mode respectively which will indicate the action done by the button.
P.S. I wish to contribute to this wonderful project under GSSoC '23. Thank You !
Screenshots
current version:

Checklist

[X] I have checked the existing issues
[X] I have read the [Contributing Guidelines]
[X] I have read the discussion tab thoroughly and got the project idea
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

@rishuraj1 we are removing the dark mode as it is causing many problems and our main concern is for the functionality of the app first the we can enhance the looks


Make idempotent

It'd be ideal if this checked whether it was run previously. Easiest way would probably be to check if postcss.config.cjs exists and already contains tailwindcss, and to abort the script if it exists.
That would prevent it acting twice on the same code base, which will break a project until postcss.config.cjs is cleaned up again, overwrites a user's custom tailwind config, etc. (I intentionally ran the command twice to check if it was idempotent, with the below result for postcss.config.cjs).
const tailwindcss = require("@tailwindcss/jit");
const tailwindcss = require("@tailwindcss/jit");
const autoprefixer = require("autoprefixer");
const cssnano = require("cssnano");

const mode = process.env.NODE_ENV;
const dev = mode === "development";

module.exports = {
	plugins: [
		// Some plugins, like postcss-nested, need to run before Tailwind

		tailwindcss,

		// But others, like autoprefixer, need to run after

		// Some plugins, like postcss-nested, need to run before Tailwind

		tailwindcss,

		// But others, like autoprefixer, need to run after

		autoprefixer,

		!dev && cssnano({
			preset: "default",
		}),
	],
};

This is definitely not a bad idea, but I don't think it brings enough benefit to prioritize implementing it over anything else.

Don't be confused by the wontfix label. It just signals that I can't fix this in the current state of things. Wait like 2-3 weeks for the rewrite (I'm really busy for the next week).
This will be solved in a future rewrite of svelte-add: https://github.com/svelte-add/svelte-adders/issues/12
Specifically, it won't be allowed to run svelte-add after the project initialization process https://github.com/svelte-add/svelte-adders/issues/17 so idempotency won't be needed.

Not ideal. People may start a project and later decide they want TailwindCSS, etc. But I'm sure you're aware of this

Not ideal. People may start a project and later decide they want TailwindCSS, etc. But I'm sure you're aware of this

It is almost quite literally impossible for an automated tool to solve this. People can follow tutorials or replicate what this tool does themselves.

No, it's really not. https://www.ansible.com solves it. Even NextJS's Tailwind npx command runs checks to see if Tailwind has already been installed. I also wrote JS code showing how such checks could be achieved in JS too in a previous issue on this repo.
I think we just have a difference of opinion on how a tool like this should behave: I'm looking for idempotency and expect such a tool to not add demo cruft or to alter any files in the project except those needed to achieve its goal. It was fun to playing with this--thanks for writing it. I'll probably end up writing my own scripts, it sounds like. Cheers.

Idempotency is the easy one, but supporting modifying code that we don't know anything about is practically impossible.
Excluding demos has been documented for a few weeks: https://github.com/svelte-add/svelte-add#-excluding-examples

Not ideal. People may start a project and later decide they want TailwindCSS, etc. But I'm sure you're aware of this

It is almost quite literally impossible for an automated tool to solve this. People can follow tutorials or replicate what this tool does themselves.

@websocket98765 I relent. It'll still be possible (will be made more possible than the current state of things) to run the svelte-add command at a later time than project initialization.
There will be a warning message to inform that if it doesn't work, the issue should be reported and if they want instant results they should run the project initializer again.
(Reminder not to be confused by the wontfix label -- it just signals that the issue cannot be solved until the rewrite, which can be tracked here: https://github.com/orgs/svelte-add/projects/1#card-59584691)


added sql method

@dustmop I'm not sure if this fits in clienty.py, but I took a stab at it and it worked in a notebook for me.

Thanks for the PR, approved, merging!


Accordian not working properly

I am using bootstrap version 5.0.1 and made an accordian which works well in my local PC at the time of making it but when i hosted it online it isn't working. I tried changing the version too but no change.
My hosted site : Krix Discord bot
I hope I will get a response soon.

Make sure your URLs are correct when uploading. Since it works locally and not remotely, guessing the problem is in your setup.

I have reason to believe the person who hacked my accounts is using an enterprise account on GitHub with my other email address how can I fine out? I'm not real smart with this stuff the only reason I even know about this website is because I found it in my phone with multiple profiles in my name with different emails some of which are the ones im trying to get back into. I'm really sorry to ask for help with this but this person has invaded my entire life

Make sure your URLs are correct when uploading. Since it works locally and not remotely, guessing the problem is in your setup.

You mean the CDN links?
If yes then I have checked the CDNs thrice in my code and also in the rendered page. The CSS and JS files are connected.

@KrishAgarwal2811 your markup is broken and the JS file isn't loaded.

@alpadev I think I have impoted the js file the right way but even why isn't it loading. And my markdown is broken... How?

@alpadev I think I have impoted the js file the right way but even why isn't it loading. And my markdown is broken... How?

The  markup, the HTML. Didn't you recognize, that half of your page isn't interpreted/rendered properly including the script tag? That's why the JS isn't loaded.
You need to replace the angle brackets (<, >) - see https://www.w3schools.com/html/html_entities.asp. Validate your HTML code with https://validator.w3.org/ and fix the errors and you should be fine.

@alpadev Thanks a lot 🙏🙏
The main issue was with dots used in ids that was because I am using ejs and didn't realise those are using dots lol


Add WordPress health check

Can we take a look at the failing integration test before merging? I don't think it's related to this change, but it'd be good to confirm what it is.

Can we take a look at the failing integration test before merging? I don't think it's related to this change, but it'd be good to confirm what it is.

It seems like one of the integration tests is using wait_for_idle but without the status parameter. So when the charm was performance database initialization in the maintenance status, it took more than 15 seconds, the default idle interval, and causes the wait to exit early.
Usually, database initialization only takes a few seconds, that's why this never happens before. But it is taking more time this time, probably due to the database performance issue.


feat: atomic studio specific packages

like the theme itself, some lowlatency settings, and RTKernel, cli utilities, and everything else :>

duplicate!


NullReferenceException in DacInterface.CallableCOMWrapper.Release()

I'm using CLRMD 1.0 and since recently I'm seeing this exception (not for all crash dumps):
INFO: created runtime with version v2.0.50727.8789
ERROR: Exception creating CLR Runtime
ERROR: Object reference not set to an instance of an object.
   at Microsoft.Diagnostics.Runtime.DacInterface.CallableCOMWrapper..ctor(RefCountedFreeLibrary library, Guid& desiredInterface, IntPtr pUnknown)
   at Microsoft.Diagnostics.Runtime.Desktop.DesktopModule..ctor(DesktopRuntimeBase runtime, UInt64 address, IModuleData data, String name, String assemblyName)
   at Microsoft.Diagnostics.Runtime.Desktop.DesktopRuntimeBase.GetModule(UInt64 module)
   at Microsoft.Diagnostics.Runtime.Desktop.LegacyGCHeap.GetTypeByMethodTable(UInt64 mt, UInt64 cmt, UInt64 obj)
   at Microsoft.Diagnostics.Runtime.Desktop.DesktopGCHeap..ctor(DesktopRuntimeBase runtime)
   at Microsoft.Diagnostics.Runtime.Desktop.DesktopRuntimeBase.CreateHeap()
   at System.Lazy`1.CreateValue()
   at System.Lazy`1.LazyInitValue()
   at SuperDump.Program.SetupCLRRuntime() in C:\workspaces\priv\superdump-internal.git\src\SuperDump\Program.cs:line 176

Cannot share the dump file for privacy reasons.
Here is the code calling CLRMD: https://github.com/Dynatrace/superdump/blob/master/src/SuperDump/Program.cs#L164

Thanks for the report.  Looks like another v2 issue.  I'll do some better testing with that runtime and see what we find.


Temporary fix for auth issue

This is a temporary fix for the couple of auth issues I've seen where stale auth tokens don't result in a redirection to the login page.. and new users navigating to / were receiving an infinite route.

LGTM

I'm not sure what happened but I can open multiple browsers and incognito windows and i get automatically logged in.  Reverted.


[DROOLS-1175][DROOLS-1242] infer numeric type for sum expression in an accumulate pattern + make accumulate functions null safe

+1 to merge. Running benchmarks now to get an idea how much perf this gives us.


Add new Page with all verified information in mijn.eduid

This issue is imported from pivotal
Link from drop-down verified attribute in the personal-info in mijn app. See attachments for new link and new page. See design: https://www.figma.com/design/04nA3kUctBZEAXfslxIeJc/eduID-2024?node-id=535-2870&t=25vbZwlQhpqNVvN1-0

(Okke Harsta - May 21, 2024)


Add a require_data() method

Please confirm that this PR has done the following:

[x] Tests Added
[x] Documentation Added
~Name of contributors Added to AUTHORS.rst~
[x] Description in RELEASE_NOTES.md Added

Description of PR
This PR adds a require_data() method as a generalized approach to require_variable(). The new method returns none if all scenarios have all (combinations) of required values on the dimensions, or it returns a DataFrame of model-scenarios where not all required values are present.
The PR also adds a (data) "coordinates" attribute to quickly access the data columns that are not in the index.
Question
The existing validation methods like require_variable() are very verbose. Here, I have not added any logging output. Any preferences?

I think the return values should contain all identifiers to missing data points, not just model and scenario as it could otherwise lead to ambiguities.
As an example these data:

Model
Scenario
Region
Variable
Unit
2020
2025

model_a
scenario_a
region_a
variable_a
unit_a
1

model_a
scenario_a
region_b
variable_a
unit_a
1
2

with a required data specification:
region: [region_a, region_b]
variable: variable_a
year: [2020, 2025]

would currently return model_a and scenario_a. That does not tell you the whole story though as for the first line in the data a value for 2025 is missing while for the second line, which is also model_a and scenario_a, everything is in order.

I think the return values should contain all identifiers to missing data points, not just model and scenario as it could otherwise lead to ambiguities.

It's not quite straightforward to develop a useful interface (or object) for this "complete" return-object.
Riffing off the example above: Should the returned dataframe contain a column "unit"? If yes, the value should probably be None for all columns... If no, the columns of the returned object depend on the arguments, making automated processing difficult.
Second, I see a problem that computing the missing index will be quite a lot of processing, only to be thrown away later anyway.
Suggestion: we leave as is for now (or even simplify just return bool) and add an argument "verbose" later?

Suggestion: we leave as is for now (or even simplify just return bool) and add an argument "verbose" later?

My preference would be the latter. Just keeping it as a kind of validator of, "is everything that we require there?". The question of "what is missing?" could almost be a separate one.

I had an idea of a different, maybe more simple, approach that might be worth exploring. Would it be an option to simply construct a list of all the combinations of required data input and then loop over them one by one checking if there is data there. During that you would simply save what's missing.
Something like:
def require_data(self, region=None, variable=None, unit=None, year=None, exclude_on_fail=False):
    missing_datapoints = []
    # combine "everything with everything"
    for datapoint in itertools.product([region, variable, unit, year]):
        # obviously this check is a bit more involved but just to illustrate my idea
        if datapoint not in self:
            missing_datapoints.append(datapoint)
    if missing_datapoints:
        return missing_datapoints

I had an idea of a different, maybe more simple, approach that might be worth exploring.

Yes, that's the (only) way to go if we want to have a complete list of all missing (combinations of) required items.
But if the use case (for now) is just to know whether all required items exist and (optionally) exclude those scenarios that do meet the requirement from further processing, checking the length of an existing index is much more efficient than creating a second index and comparing the two indices line-by-line.

Yes, true. I was already thinking towards providing user feedback to point exactly what data points are missing but that’s probably better handled in a different function if we really need that level of precision.


Getter for patch mutation on the frontend

Description
Getter for patch mutation on the frontend, and some minor fix

/deploy-staging

/rebase


SentinelOneAPISentinelConn.zip modification caused existing Function Apps to stop working

Describe the bug
https://raw.githubusercontent.com/Azure/Azure-Sentinel/refs/heads/master/Solutions/SentinelOne/Data Connectors/SentinelOneAPISentinelConn.zip modification from yesterday (2024-10-23) caused existing SentinelOneSentinelConnector function in the Function App to fail with the following error:
Result: Failure Exception: ImportError: libffi-9c61262e.so.8.1.0: cannot open shared object file: No such file or directory. Cannot find module. Please check the requirements.txt file for the missing module. For more info, please refer the troubleshooting guide: https://aka.ms/functions-modulenotfound. Current sys.path: ['/tmp/functions\standby\wwwroot', '/home/site/wwwroot/.python_packages/lib/site-packages', '/azure-functions-host/workers/python/3.8/LINUX/X64', '/usr/local/lib/python38.zip', '/usr/local/lib/python3.8', '/usr/local/lib/python3.8/lib-dynload', '/usr/local/lib/python3.8/site-packages'] Stack: File "/azure-functions-host/workers/python/3.8/LINUX/X64/azure_functions_worker/dispatcher.py", line 535, in _handle__function_load_request func = loader.load_function( File "/azure-functions-host/workers/python/3.8/LINUX/X64/azure_functions_worker/utils/wrappers.py", line 49, in call raise extend_exception_message(e, message) File "/azure-functions-host/workers/python/3.8/LINUX/X64/azure_functions_worker/utils/wrappers.py", line 44, in call return func(*args, **kwargs) File "/azure-functions-host/workers/python/3.8/LINUX/X64/azure_functions_worker/loader.py", line 220, in load_function mod = importlib.import_module(fullmodname) File "/usr/local/lib/python3.8/importlib/init.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1014, in _gcd_import File "", line 991, in _find_and_load File "", line 975, in _find_and_load_unlocked File "", line 671, in _load_unlocked File "", line 843, in exec_module File "", line 219, in _call_with_frames_removed File "/home/site/wwwroot/SentinelOneSentinelConnector/init.py", line 11, in  from .state_manager import StateManager File "/home/site/wwwroot/SentinelOneSentinelConnector/state_manager.py", line 1, in  from azure.storage.fileshare import ShareClient File "/home/site/wwwroot/.python_packages/lib/site-packages/azure/storage/fileshare/init.py", line 8, in  from ._file_client import ShareFileClient File "/home/site/wwwroot/.python_packages/lib/site-packages/azure/storage/fileshare/_file_client.py", line 28, in  from ._shared.uploads import IterStreamer, FileChunkUploader, upload_data_chunks File "/home/site/wwwroot/.python_packages/lib/site-packages/azure/storage/fileshare/_shared/uploads.py", line 21, in  from .encryption import get_blob_encryptor_and_padder File "/home/site/wwwroot/.python_packages/lib/site-packages/azure/storage/fileshare/_shared/encryption.py", line 19, in  from cryptography.hazmat.primitives.padding import PKCS7 File "/home/site/wwwroot/.python_packages/lib/site-packages/cryptography/hazmat/primitives/padding.py", line 11, in  from cryptography.hazmat.bindings._padding import lib
We have two Function Apps, deployed from the SentinelOne Data Connector via the ARM Template option more than 6 months ago, that stopped working since yesterday, both of them with the same error.
In the current SentinelOneAPISentinelConn.zip file there is a .python_packages\lib\site-packages\cffi.libs\libffi-806b1a9d.so.6.0.4 file but the filename is different than the one from the error: libffi-9c61262e.so.8.1.0.
The https://aka.ms/sentinel-SentinelOneAPI-functionapp URL in the Function App WEBSITE_RUN_FROM_PACKAGE environment variable redirects to this URL:
https://raw.githubusercontent.com/Azure/Azure-Sentinel/refs/heads/master/Solutions/SentinelOne/Data Connectors/SentinelOneAPISentinelConn.zip
The file SentinelOneAPISentinelConn.zip shows to have been modified yesterday (2024-10-23) at the same time our two Function Apps stopped working.

I have the same issue. Stopped working after the update..

Just fixed it. Make sure you have the SentinelOne Solution updated to the latest version. Create a new Function App from the "SentinelOne (using Azure Functions)" Data Connector using the same settings as the old one. The new one should work ok.

Glad it worked!

Hi @q0njg3m1, We have fixed this issue. Thanks!

Hi @v-sudkharat. Yeap, just checked and both the old function apps and the new ones are working ok now. We've stopped the old ones to prevent data duplication in the Sentinel workspace. Thanks!