react-native-webview error, supports only kotlin-android-extensions Gradle plugin version 1.6.20 and higher.

getting
Android gradle plugin: 7.3.1
Gradle: 7.5.1
WARNING:Software Components will not be created automatically for Maven publishing from Android Gradle Plugin 8.0. To opt-in to the future behavior, set the Gradle property android.disableAutomaticComponentCreation=true in the `gradle.properties` file or use the new publishing DSL.

FAILURE: Build failed with an exception.

* What went wrong:
The Android Gradle plugin supports only kotlin-android-extensions Gradle plugin version 1.6.20 and higher.
The following dependencies do not satisfy the required version:
project ':react-native-webview' -> org.jetbrains.kotlin:kotlin-gradle-plugin:1.6.0

when running project using
import { Camera } from 'react-native-camera-kit';
of course works great with ios but android will not build.
To Reproduce
Steps to reproduce the behavior:
using
"dependencies": {
"react-native": "0.71.6",
"react-native-reanimated": "3.5.2",
"react-native-webview": "^13.6.2",
"react-native-camera-kit": "^13.0.0",
"bootstrap": "^5.3.2",
}
calling like
import { Camera } from 'react-native-camera-kit';
<Camera
scanBarcode={true}
onReadCode={(event: any) => {
handleOnReadCode(event);
}}
showFrame={true}
laserColor="red"
frameColor="white"
/>
like stated works fine on ios but will not build on android
added from
https://github.com/teslamotors/react-native-camera-kit/blob/master/docs/kotlin.md
android>build.gradle
buildscript {
    ext {
        buildToolsVersion = "33.0.0"
        minSdkVersion = 23
        compileSdkVersion = 33
        targetSdkVersion = 33
        kotlin_version = "1.7.20"
    }
    repositories {
        google()
        mavenCentral()
    }
    dependencies {
        classpath("com.android.tools.build:gradle:7.3.1")
        classpath("com.facebook.react:react-native-gradle-plugin")
        classpath("com.google.gms:google-services:4.3.14")
        classpath("org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version")
    }
}

allprojects {
    repositories {
        google()
     }
}
and
android>app>build.gradle
apply plugin: "com.android.application"
apply plugin: "com.facebook.react"
apply plugin: "com.google.gms.google-services"
apply plugin: "kotlin-android"
apply plugin: "kotlin-android-extensions"

tried various numbers, all i could think of for   kotlin_version = "1.7.20", "1.7.10", and many others to no avail

macos ventura 13.2.1
TRYING DESPERTELY to add a qr scanner,
since react-native-camera  is decprecated, and react-native-vision-camera doesn't implement a qr scanner , thought this was best option any help on build process for android is greatly appreciated.

I came across a workaround which basically suggested applying a patch for react-native-webview. I'll share the contents of patch file below:
diff --git a/node_modules/react-native-webview/android/build.gradle b/node_modules/react-native-webview/android/build.gradle
index f68fa80..6e52d07 100644
--- a/node_modules/react-native-webview/android/build.gradle
+++ b/node_modules/react-native-webview/android/build.gradle
@@ -9,7 +9,7 @@ buildscript {
         gradlePluginPortal()
     }
     dependencies {
-        classpath("org.jetbrains.kotlin:kotlin-gradle-plugin:${safeExtGet('kotlinVersion')}")
+        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:1.6.20"
         classpath("com.android.tools.build:gradle:7.0.4")
     }
 }


chore: code format

fix code format issues

The tests are failing due to some http error. Any idea why?

Merging:

it is not this PR causing the issue
issue is being investigated


Scaffold without constraint names?

Is it possible to scaffold without emitting constraint names (e.g. foreign keys)? This seems unnecessary and the binding to a name ?may? cause a problem if someone renames the constraint in the database.
Might even make sense to turn this off by default unless people opt in. If we are scaffolding from an existing database, chances are we aren't going to use EF to create the database.

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

ID: e1601c3e-3f29-5d84-6350-2b38eeaf6adc
Version Independent ID: 92a856d6-c5da-e215-46ac-d67c411f3ff9
Content: Reverse Engineering - EF Core
Content Source: entity-framework/core/managing-schemas/scaffolding.md
Product: entity-framework
Technology: entity-framework-core
GitHub Login: @bricelam
Microsoft Alias: bricelam

Duplicate of #10890


Added Docker service type resolver

Brooklyn service type resolver https://github.com/apache/incubator-brooklyn/pull/587 is a pre-requisite for this PR to build.

Tested, ready to merge now that Brooklyn PR is prt of master


Is react router still working on build?

I just noticed that there is no full page reload (react-static-boilerplate) when clicking on links, although static pages are generated for each route, it seems that the react router still works on the front, and that the content of each other page is is the js script (ex: about page)
Is that by design? That would mean my js script grows on each page added?
Looks like other generated page are useless...
Is there a way I could have "real" links after build?
Thanks!

Yup! You're right, this is how it works and it is indeed by design. You're also right that your bundle size for every single page will grow with each page added. This is certainly not ideal, but it's also not generally an issue. Here's why:

The majority of your bundled code is probably going to be vendor code like React, React Router, etc, and this code would need to be included on every page no matter what. Your actual app code is mostly likely very small by comparison.
In relation to the first point, your bundle size doesn't grow in a 1:1 ratio to the number of pages you have. For example, going from 1 page to 2 pages will not double the size of your bundle, it will likely only increase by a very small amount.
If you really do need to split your code into separate bundles you can do this directly with webpack (see code splitting).

All that being said, supporting automatic bundle splitting is definitely an optimization I'd like to include in this plugin, it's just low priority for the above reasons.

More generally, the goal of this project was allow you to build a single page app (Linking pages with react router) and simply drop in this plugin to get static pages from each route. This means that the app would naturally still support instant navigation with RR, but you now have a fully rendered static page backing every route. So the benefits you get are:

Seamless initial render, since react just has to set up event listeners and doesn't need to construct DOM
Routes that are fully parseable by search engines

Going to close this out but feel free to keep the discussion going here. If you see any drawbacks to this approach that I may have missed I'd love to hear them. I want this project to be the best it can be.

Ok nice :)
I have a LazilyLoad higher lvl components that enables me to split route code in separate scripts, it works well in dev but breaks on build because of Cannot read property 'initial' of undefined from the extract-text-webpack-plugin, and this PR won't do :(
I use it this way
import About from 'bundle?lazy&name=[name]!./components/About';

class ZAbout extends LazilyLoad {
  constructor() {
    super(About);
  }
  waiting() {
    return
Loading about...
;
  }
}

And it breaks as soon as I import using the bundle-loader
That would bring the best of both worlds, if you manage lazy loading feel free to mention me ! :)

I have a question regarding the front end router and SEO.
Do I have to handle nginx rules to redirect crawlers to about.html when they follow the /about link? or does it work out of the box?
thanks!

That will depend on your configuration, so if you're managing your own server then yes it will depend on your Nginx (or Apache) config.
I know from my own use that everything works out of the box with Surge.sh and Netlify, but you might have to configure nginx yourself if it's your server. In Nginx that looks something like this:
 try_files $uri $uri.html $uri/index.html =404;

Check out the full configuration I used in the past in the boilerplate repository:
https://github.com/iansinnott/react-static-boilerplate/blob/master/scripts/generate-nginx-conf.js

Thanks!


git status throws exception

After a successful load i tried to run gitRepository.status which fails with:
Exception: Concurrent modification during iteration: Instance(length:1) of '_GrowableList'.

I think this should be fixed by now. If it isn't please re-open with the full backtrace.


Pings

For reliability it might be an idea to immplement our ping method. Simply call it every 15 seconds or so.
Helps keep the connection alive.

Fixed!


Templates should include Travis CI configuration

Using Testee to launch FireFox on Travis requires special configuration to prevent errors. A default configuration should be added to the plugin, and probably the app templates.
This is the required configureation, note the dbus installation:
language: node_js
node_js:
  - "6"
addons:
  firefox: "latest-esr"
  apt:
    packages:
      - dbus-x11
before_install:
  - "export DISPLAY=:99.0"
  - "sh -e /etc/init.d/xvfb start"

For more information about this issue, see https://github.com/bitovi/testee/issues/157.
cc: @phillipskevin, @matthewp

I opened a PR for this, although it may need to be updated: https://github.com/donejs/generator-donejs/pull/265

The plugin generator has a template already: https://github.com/donejs/generator-donejs/blob/33cdf07aeacd6303abdd91572466d6effeca35ce/plugin/templates/static/.travis.yml.

Shouldn't that be in the root instead of under the static folder?

I'm not sure why the static folder exists. The way the code works, those files cannot use template replacements (like <%= name %>) like the folders outside of static can. I'm not sure why it was done this way, but we definitely shouldn't have the file in two places.


minecraft:pink_petals is not blacklisted by default

This issue occurs when only Valkyrien Skies and addons are installed and no other mods

[X] I have tested this issue and it occurs when no other mods are installed

Minecraft Version
1.16
Mod Loader
Forge
Issue description
minecraft:pink_petals is not blacklisted by default
Issue reproduction
minecraft:pink_petals is not blacklisted by default
Logs
No response

duplicate of #229
also, Pink Petals was added in Minecraft 1.20.


Fixing missing null encoded fields when using indexNullAs (NullEncodingTwoWayFieldBridge)

Can one of the admins add this person to the trusted builders? (reply with: "add to whitelist" or "ok to test")

ok to test

Thanks @torkis , I've added a quick test to this as I was very surprised ;-)
The follow up PR#802 contains both your commit and mine; I've only changed your commit message to point to the JIRA issue I've created to track this: https://hibernate.atlassian.net/browse/HSEARCH-1825
Could you please sign the contributor agreement at cla.jboss.org for project Hibernate ?
It just needs you to read a very short paragraph to make sure you understand the basics of OSS collaboration, and then you sign with a checkbox.
Thanks!

Thanks Sanne!
I signed the CLA for the Hibernate project.


Separate application part from GUI

This pull request changed the welcome window (separated the gui from the app). The call from main works, the welcome window opens, files can be selected and the main window opens after the start button is clicked. However, when we wanted to generate labels, an error from bentoml occurred and needs to be addressed.
File ".../main_window.py", line 155, in _run_inference
    response = await self.client.async_segment_image(self.eval_data_path)

The error seems to stem from docker (when the server is run by docker compose up). No error when run via bentoml serve command


[#1082] Add automatic proficiency updates for items when the owning actor's proficiency list changes

[Potentially solves #1082]
Whenever _onUpdate is triggered on an Actor, update the proficiencies of any items related to the original update.
Note: There might be a better place to attach this than "_onUpdate", but I couldn't find a less frequent method that gets called every time the actor's proficiencies change. The current slowdown is small (checks if weaponProf, armorProf, or toolProf is included in every update), but there might be a more efficient location for this.
Note: When we get working tool proficiencies in 1.8.x (see #774), this section should be updated to handle non-binary tool proficiencies like expertise and half-proficiency.

This was like my original attempt to resolve this issue, but after discussion we decided to move in a different direction of automatically determining the proficiency in prepareData. Unfortunately some of that conversation got lost in the transition over from GitLab.
I have a branch that implements the automatic proficiency, but it is held up because we don't have a method for representing tool expertise on a character sheet.


What happens if we don't want to use default doctrine driver?

See https://github.com/ZF-Commons/ZfcUserDoctrineORM/blob/master/Module.php#L17
What happens if we don't want to use default connection?
Although, it is not normal, but, the goal of this module is to be very flexible.

PR welcome ;)


Bug: Backend Deployment Issues with @xmtp/node-sdk Due to GLIBC Compatibility in Docker

Description:
I'm encountering issues deploying the backend after switching to the new @xmtp/node-sdk package. The initial error I faced was:
Error: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.32 not found

This was caused by the debian:bullseye Docker image having an older GLIBC version. I then tried using debian:bookworm (with GLIBC 2.36), but the error changed to:
Error: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.38 not found

Additionally, I'm seeing this error:
Error: Cannot find module '@xmtp/node-bindings-linux-x64-gnu'

Steps Taken:

Switched Docker base image from debian:bullseye to debian:bookworm.
The errors persisted due to GLIBC compatibility issues.

Questions:

Which Debian or NPM packages need to be installed to resolve this compatibility issue in Docker?
Does the node SDK require such a recent version of GLIBC for specific reasons?
Would it be recommended to use an OS image like ubuntu:24.04 (with GLIBC 2.38+) in Docker as a workaround?

Additional Context:

The node bindings are built using Ubuntu 24.04 via GitHub runners (warp build).
Upgrading GLIBC in-place within a container is a complex process.

Current Workaround:
Switching to ubuntu:noble resolved the issue.

the fix is to use an ubuntu 24.04 image in Docker
if running on his ubuntu laptop directly , be sure that he has ubuntu 24.04 at least


Tidy up mess left behind

Hi, I'm working on a project which uses this as a base and noticed a bit of untidiness. Compare the below result from ubuntu:16.04 with phusion/baseimage:0.9.22
Step 2/2 : RUN dpkg -l | grep "rc  "
 ---> Running in d102cdbf6d34
ii  sysv-rc                  2.88dsf-59.3ubuntu2           all          System-V-like runlevel change mechanism

vs
Step 2/2 : RUN dpkg -l | grep "rc  "
 ---> Running in ba4b668c6991
rc  autoconf                    2.69-9                             all          automatic configure script builder
rc  bsdmainutils                9.0.6ubuntu3                       amd64        collection of more utilities from FreeBSD
rc  docbook-xml                 4.5-7.3                            all          standard XML documentation system for software and systems
rc  docbook-xsl                 1.79.1+dfsg-1                      all          stylesheets for processing DocBook XML to various output formats
rc  dpkg-dev                    1.18.4ubuntu1.2                    all          Debian package development tools
rc  groff-base                  1.22.3-7                           amd64        GNU troff text-formatting system (base system components)
rc  libgdbm3:amd64              1.8.3-13.1                         amd64        GNU dbm database routines (runtime version)
rc  libgpm2:amd64               1.20.4-6.1                         amd64        General Purpose Mouse - shared library
rc  libmpc3:amd64               1.0.3-1                            amd64        multiple precision complex floating-point library
rc  libperl5.22:amd64           5.22.1-9                           amd64        shared Perl library
rc  libsigsegv2:amd64           2.10-4                             amd64        Library for handling page faults in a portable way
rc  libunistring0:amd64         0.9.3-5.2ubuntu1                   amd64        Unicode string library for C
rc  man-db                      2.7.5-1                            amd64        on-line manual pager
rc  perl                        5.22.1-9                           amd64        Larry Wall's Practical Extraction and Report Language
rc  pkg-config                  0.29.1-0ubuntu1                    amd64        manage compile and link flags for libraries
rc  quilt                       0.63-3                             all          Tool to work with series of patches
rc  sgml-base                   1.26+nmu4ubuntu1                   all          SGML infrastructure and SGML catalog file support
rc  sgml-data                   2.0.10                             all          common SGML and XML data
ii  sysv-rc                     2.88dsf-59.3ubuntu2                all          System-V-like runlevel change mechanism
rc  w3m                         0.5.3-26ubuntu0.1                  amd64        WWW browsable pager with excellent tables/frames support
rc  xml-core                    0.13+nmu2                          all          XML infrastructure and XML catalog file support

I've had a look around the scripts and I don't immediately see the reason for this as there are no "apt-get remove" lines that I found. Maybe I missed something? They can be cleaned up with dpkg --purge --force-all  if desired. Otherwise I'm curious as to why they're there and any reason for not cleaning them up. Cheers.

I'm on mobile and cannot read the lines, but they are quite probably from
fix_pam_bug and they have been removed now.
On 2017. Aug 2., Wed at 23:57, Fred Cooke<EMAIL_ADDRESS>wrote:

Hi, I'm working on a project which uses this as a base and noticed a bit
of untidiness. Compare the below result from ubuntu:16.04 with
phusion/baseimage:0.9.22
Step 2/2 : RUN dpkg -l | grep "rc  "
---> Running in d102cdbf6d34
ii  sysv-rc                  2.88dsf-59.3ubuntu2           all          System-V-like runlevel change mechanism
vs
Step 2/2 : RUN dpkg -l | grep "rc  "
---> Running in ba4b668c6991
rc  autoconf                    2.69-9                             all          automatic configure script builder
rc  bsdmainutils                9.0.6ubuntu3                       amd64        collection of more utilities from FreeBSD
rc  docbook-xml                 4.5-7.3                            all          standard XML documentation system for software and systems
rc  docbook-xsl                 1.79.1+dfsg-1                      all          stylesheets for processing DocBook XML to various output formats
rc  dpkg-dev                    1.18.4ubuntu1.2                    all          Debian package development tools
rc  groff-base                  1.22.3-7                           amd64        GNU troff text-formatting system (base system components)
rc  libgdbm3:amd64              1.8.3-13.1                         amd64        GNU dbm database routines (runtime version)
rc  libgpm2:amd64               1.20.4-6.1                         amd64        General Purpose Mouse - shared library
rc  libmpc3:amd64               1.0.3-1                            amd64        multiple precision complex floating-point library
rc  libperl5.22:amd64           5.22.1-9                           amd64        shared Perl library
rc  libsigsegv2:amd64           2.10-4                             amd64        Library for handling page faults in a portable way
rc  libunistring0:amd64         0.9.3-5.2ubuntu1                   amd64        Unicode string library for C
rc  man-db                      2.7.5-1                            amd64        on-line manual pager
rc  perl                        5.22.1-9                           amd64        Larry Wall's Practical Extraction and Report Language
rc  pkg-config                  0.29.1-0ubuntu1                    amd64        manage compile and link flags for libraries
rc  quilt                       0.63-3                             all          Tool to work with series of patches
rc  sgml-base                   1.26+nmu4ubuntu1                   all          SGML infrastructure and SGML catalog file support
rc  sgml-data                   2.0.10                             all          common SGML and XML data
ii  sysv-rc                     2.88dsf-59.3ubuntu2                all          System-V-like runlevel change mechanism
rc  w3m                         0.5.3-26ubuntu0.1                  amd64        WWW browsable pager with excellent tables/frames support
rc  xml-core                    0.13+nmu2                          all          XML infrastructure and XML catalog file support
I've had a look around the scripts and I don't immediately see the reason
for this as there are no "apt-get remove" lines that I found. Maybe I
missed something? They can be cleaned up with dpkg --purge --force-all if
desired. Otherwise I'm curious as to why they're there and any reason for
not cleaning them up. Cheers.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/phusion/baseimage-docker/issues/433, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAeKj2LtxZO35TBgukhxKAOingab25Flks5sUPDZgaJpZM4Ortfh
.

OK. I tried to verify but there doesn't appear to be a nightly build and none of the automated builds appear to point at master branch in the official repo, some behind, and ahead, and so forth. I see a ticket asking for a "next" tag, even if it wasn't in the same public repository, that would be very handy to validate fixes on master without performing a from-scratch build which may/may not be the same as an official one for various reasons. I look forward to seeing 0.9.23 :-)

Ok that's quite an important topic, next should work.
On 2017. Aug 3., Thu at 4:44, Fred Cooke<EMAIL_ADDRESS>wrote:

OK. I tried to verify but there doesn't appear to be a nightly build and
none of the automated builds appear to point at master branch in the
official repo, some behind, and ahead, and so forth. I see a ticket asking
for a "next" tag, even if it wasn't in the same public repository, that
would be very handy to validate fixes on master without performing a
from-scratch build which may/may not be the same as an official one for
various reasons. I look forward to seeing 0.9.23 :-)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/phusion/baseimage-docker/issues/433#issuecomment-319852643,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAeKj4Zf8dvtYCxeyI2Sw6ctXH9aRkU8ks5sUTQKgaJpZM4Ortfh
.

This issue is fixed in 0.10.0

What is the PR that fixed this?

NVM I see it now, thanks @hyperknot 👍


fix a couple syntax errors

we override primeForRefresh, so we may be able to still use it?

Yeah, those seem important :)


Subquery optimization: Updates docs

There is an ongoing effort to improve subquery performance, which seems to introduce new Node types to the execution plan / explain output. The docs probably need an update when this is done.

SubqueryStart, SubqueryEnd
https://www.arangodb.com/docs/3.6/aql/execution-and-performance-optimizer.html#list-of-execution-nodes
splice-subqueries
https://www.arangodb.com/docs/3.6/aql/execution-and-performance-optimizer.html#list-of-optimizer-rules


dependent fields in collection

hey,
i could not find any information about this therefor i thought i would ask here.
is it possible to show and hide fields depending on some other field?
eg. this is my frontmatter
---
...
structure:
- type: productCircle
- type: divider
- type: copy
  content:
    text: >-
      Lorem ipsum dolor sit amet, consectetur adipisicing elit. Fugiat fugit enim quo consequuntur amet quasi ullam officia assumenda nihil. Corrupti delectus magnam excepturi nobis quae nihil explicabo provident repellat quaerat.
- type: infographic
  content:
    src: http://example.com/text.png
    overlay: http://example.com/text.png
- type: divider
- type: copy
  content:
    text: >-
      Lorem ipsum dolor sit amet, consectetur adipisicing elit. Animi nihil error repellendus perspiciatis ratione, dolores, cum dicta sapiente quod labore saepe, quam ab placeat veniam nobis culpa totam vitae nam.
- type: infographic
  content:
    src: http://example.com/text.png
    overlay: http://example.com/text.png
- type: copy
  content:
    text: >-
      Lorem ipsum dolor sit amet, consectetur adipisicing elit. Aspernatur vero, quos velit minima placeat alias, quibusdam at sed quia illum dolorum. A, rem aut quidem excepturi aliquam. Aliquid, ea, cumque.
- type: quote
  variant:
  - with-divider
  content:
    items:
      - image: http://example.com/text.png
        copy: Lorem ipsum dolor sit amet, consectetur adipisicing elit. Vitae sunt, earum? Perferendis ab blanditiis ut sequi consequuntur repudiandae ad ratione, amet eligendi laborum itaque labore, eius. Illo, quidem tempore quam!
        author: Mario and Luigi
        type: light
- type: divider
- type: copy
  content:
    text: >-
      Lorem ipsum dolor sit amet, consectetur adipisicing elit. Deleniti, illum qui. Adipisci fugit, obcaecati, vel nostrum cumque a dignissimos odit eveniet ab. Aut cum officiis nesciunt necessitatibus, provident, ullam delectus!
- type: image
  content:
    src: http://example.com/text.png
---

based on that type different configurations for this list item might be needed
eg.
if my type is image only a image field is necessary but if the type is infographicand additional overlay image can be added
my config.yml looks like this
- label: 'structure'
        name: structure
        widget: 'list'
        fields:
          - {label: "type", name: "type", widget: "select", options: ["copy", "divider", "image", "infographic", "productCircle", "quote"]}
          - label: content
            name: content
            widget: object
            fields:
              - {label: 'text', name: 'text', widget: 'markdown'}
              - {label: 'src', name: 'src', widget: 'image'}
              - {label: 'overlay', name: 'overlay', widget: 'image'}

this list has a lot of unused options and i am far from done adding all the fields
what would a good way to implement this kind of structure?
cms version 0.4.6

You could create a custom widget that provides a select input for selecting type, and the type definitions could be an array of objects defined in the widget config. Then you just swap in fields based on the selected type.

So I've been considering how this might look. We're now focusing heavily on the extensibility story around the CMS, and a big part of that is making widget authoring simpler, and the available API's more robust.
For this particular issue, we should have a widget as I mentioned in my last comment, but I want it to just be a button with configurable text. In the OP case you would configure the label to "Add content", and it's appearance would simply be that of a dropdown, which editors can use to add one of the widgets configured in the "fields" array. The UI around this could be further enhanced by passing control of labels (optionally) to widget authors (currently all widgets automatically receive a label in the UI direct through the CMS). This means an entry could consist of nothing more than this widget and be entirely dynamic, very similar to what ACF provides to WordPress users.
Furthermore, if the added widgets are themselves draggable, we'd have all that's needed for site building. Doing all of this in a widget is pretty compelling.
Thoughts?

@domtalbot can you open a "WIP" PR with a working implementation?

Started another issue similar to this. Wondering if you got anywhere @domtalbot and if you need any help? #1066

While considering #2405 I think I found a way to statically configure conditional fields right in the yaml while still providing flexibility. Using the original case from @kevinfoerster's OP:
- label: structure
  name: structure
  widget: list
  fields:
    - label: type
      name: type
      widget: select
      options:
        - copy
        - divider
        - image
        - infographic
        - productCircle
        - quote
    - label: content
      name: content
      widget: object
      fields:
        - label: text
          name: text
          widget: markdown
          condition: {type: fieldValue, field: type, oneOf: [copy, productCircle, quote]}
        - label: src
          name: src
          widget: image
          condition: {type: fieldValue, field: type, oneOf: [image, infographic, productCircle]}
        - label: overlay
          name: overlay
          widget: image
          condition: {type: fieldValue, field: type, equals: infographic}

fieldValue is just one potential type, and each type can accept different properties, here we use equals and oneOf.
condition could accept either an object or an array. The example above is shorthand for condition.oneOf, which accepts an object or array of objects, and can be used if condition itself can be configured with other properties for more control, or alternatives to condition.oneOf, such as condition.allOf, which would require all condition objects in an array to validate.

I love this idea of the condition property suggested above ☝ Do we have any forward progression on this? Just ran into a couple of scenarios where this would be very helpful. Thanks in advance.

Not yet, just a concept for now.
Sent with GitHawk

Looks great already @erquhart. Maybe add condition.not to the list of conditions

@erezrokah  Where is this on the roadmap? Would be great to get this feature added! I've got a situation that looks like this:

It's very confusing for content editors and hinders their productivity and the potential flexibility of NetlifyCMS.
Thanks to all for your hard work on this project !
Kyle

Hi @kylekirkby, see my comment https://github.com/netlify/netlify-cms/issues/565#issuecomment-576140240 and the most upvoted features here https://github.com/netlify/netlify-cms/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc.
I think one could implement this in a custom widget, and if that works well we can import it into the main repo.

Hi guys, I would love to see this feature added too. I have a requirement for a page builder. The way I would like to work would be that a collection's fields would be rendered out depending on which dropdown option you selected.

Hi guys, I would love to see this feature added too. I have a requirement for a page builder. The way I would like it to work would be that you create a new page based on the following in your config.yml:
collections:
  - name: 'pages'
    label: 'Pages'
    label_singular: 'Page'
    folder: 'src/_pages/pages'
    create: true
    identifier_field: name
    fields:
      - {
          label: 'Page Template',
          name: 'templateKey',
          widget: 'select',
          default: 'standardPage',
          options:
            [
              { label: 'Standard Layout', value: 'standardPage' },
              { label: 'Background Layout', value: 'backgroundPage' },
              { label: 'Carousel Layout', value: 'carouselPage' },
              { label: 'Gallery Layout', value: 'galleryPage' },
            ],
        }

The relevant fields for each type of Layout would be rendered out in the editor panel depending on which dropdown option you selected. Although, I'm not sure how I would associate each dropdown value with a unique set of fields (is this where the beta Variable Types widget comes in to play?) When I publish the page, the page's markdown would just include the frontmatter fields that correspond to the selected layout template (e.g a columns field) that was selected during page creation - all pre-populated of course:
---
templateKey: standardPage
title: Page Title
columns:
  columnOne: Column One Text
  columnTwo: Column Two Text
  columnThree: Column Three Text
---

Hi, any updates on this?

Hi, I need this feature for a client requirement, how is going on?

Hi @filipburian and @miguelt1, we had some work done in https://github.com/netlify/netlify-cms/pull/3891 if you'd like to pick it up.

6 years and multiple solutions proposed and still nothing🥲

In my case, I just needed a boolean widget that is attached to a list widget, and boolean widget can show/hide the list.
you can use a custom widget similar to this:
// custom widget
import React, { Component } from "react"
import CMS from "netlify-cms-app"
import _ from "lodash"
import { List } from "immutable"

const booleanWidget = CMS.getWidget("boolean")
const listWidget = CMS.getWidget("list")

export class ToggleListControl extends Component {
  constructor(props) {
    super(props)
    this.state = {
      show: !_.isNil(this.props.value),
    }
  }
  render() {
    const {
      value,
      forID,
      onChange,
      classNameWrapper,
      setActiveStyle,
      setInactiveStyle,
    } = this.props

    return (

          {React.createElement(booleanWidget.control, {
            value: !_.isNil(value),
            onChange: () => {
              if (!_.isNil(value)) {
                this.setState({ show: false })
                onChange(undefined)
              } else {
                this.setState({ show: true })
                onChange(List())
              }
            },
            forID: `${forID}-toggle`,
            classNameWrapper,
            setActiveStyle,
            setInactiveStyle,
          })}

          {!_.isNil(this.props.value) && (

              {React.createElement(listWidget.control, { ...this.props })}

          )}

    )
  }
}

export const ToggleListPreview = ({ value }) => {
  return

}

and the config would be the same as the one you use for list:
      - label: Toggle List
        name: fieldname
        widget: toggleList
        required: false
        field: { label: Text, name: text, widget: string }


Problem of putting into production

Q
A

Bug report?
[ ]

Feature request?
[ ]

Support request?
[ x ]

hi,
I have a problem when I want to put the project into production, yet when it is in mode dev everything is ok.
When he is in prod in the symfony logs I have:

Fatal error: Call to undefined function Doctrine\Common\Cache\apc_fetch()

and the page sends me a error 503 .
Yet "opcache" is installed when I type "php -m" , zend opcache is in the list.
here is my conf nginx:
server {
        listen 443 ssl;
        root /var/www/dev/Symfony/web;
        server_name dev.test.fr;
        ssl_certificate /etc/letsencrypt/live/dev.test.fr/fullchain.pem;
        ssl_certificate_key /etc/letsencrypt/live/dev.test.fr/privkey.pem;

        add_header Strict-Transport-Security "max-age=31536000; includeSubDomains";

        ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
        ssl_ciphers EECDH+AESGCM:EECDH+AES;
        ssl_prefer_server_ciphers on;
        ssl_session_timeout 1d;
        ssl_session_cache shared:SSL:50m;
        ssl_stapling on;
        ssl_stapling_verify on;

        # Autres directives ici

        satisfy any; allow all;

        location / {
        # try to serve file directly, fallback to app.php
          try_files $uri /app_dev.php$is_args$args;
          #try_files $uri /app.php$is_args$args;
        }
        # DEV
        # This rule should only be placed on your development environment
        # In production, don't include this and don't deploy app_dev.php or config.php
        location ~ ^/(app_dev|config)\.php(/|$) {
          include /etc/nginx/fastcgi_params;
          fastcgi_pass unix:/var/run/php-fpm.socket;
          fastcgi_split_path_info ^(.+\.php)(/.*)$;
        # When you are using symlinks to link the document root to the
        # current version of your application, you should pass the real
        # application path instead of the path to the symlink to PHP
        # FPM.
        # Otherwise, PHP's OPcache may not properly detect changes to
        # your PHP files (see https://github.com/zendtech/ZendOptimizerPlus/issues/126
        # for more information).
          fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
         }
         # PROD
        location ~ ^/app\.php(/|$) {
          fastcgi_pass unix:/var/run/php-fpm.socket;
          fastcgi_split_path_info ^(.+\.php)(/.*)$;
          include /etc/nginx/fastcgi_params;
         # When you are using symlinks to link the document root to the
         # current version of your application, you should pass the real
         # application path instead of the path to the symlink to PHP
         # FPM.
         # Otherwise, PHP's OPcache may not properly detect changes to
         # your PHP files (see https://github.com/zendtech/ZendOptimizerPlus/issues/126
         # for more information).
           fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;

         # Prevents URIs that include the front controller. This will 404:
         # http://domain.tld/app.php/some-path
         # Remove the internal directive to allow URIs like this

         #internal;
      }

         # return 404 for all other php files not matching the front controller
         # this prevents access to other php files you don't want to be accessible.
        location ~ \.php$ {
          return 404;
      }

      error_log /var/log/nginx/project_error.log;
      access_log /var/log/nginx/project_access.log;
}

I do not know where it may come from, thank you for your future help.
I have a second question about the registration form in the demo we see the choice of radio buttons "You are: a person a company" but in mine it is missing. see : http://i.imgur.com/8rduChO.png
Good job cocorico :)

Hello @gonzasylv,
Thanks for the compliment :)
To resolve your APC related issue you need to install PHP module APCu.
Concerning the person type in registration form for now it is available on Enterprise edition. It will be available in Community edition in a while.  In the meanwhile  you can add this field in the registration form.
Hope it helps

I have yet "apcu" when I do php -m, there is there a setting in particular to perform?
here is my mistake:

root@mx:/var/www/dev/Symfony# tail -f app/logs/prod-2018-04-09.log
[2018-04-09 21:29:29] request.CRITICAL: Uncaught PHP Exception Symfony\Component\Debug\Exception\FatalThrowableError: "Fatal error: Call to undefined function Doctrine\Common\Cache\apc_fetch()" at /var/www/dev/Symfony/vendor/doctrine/cache/lib/Doctrine/Common/Cache/ApcCache.php line 41 {"exception":"[object] (Symfony\Component\Debug\Exception\FatalThrowableError(code: 0): Fatal error: Call to undefined function Doctrine\Common\Cache\apc_fetch() at /var/www/dev/Symfony/vendor/doctrine/cache/lib/Doctrine/Common/Cache/ApcCache.php:41)"} []

[2018-04-09 21:29:29] request.CRITICAL: Exception thrown when handling an exception (Symfony\Component\DependencyInjection\Exception\ServiceCircularReferenceException: Circular reference detected for service "cocorico_user.user_manager", path: "sonata.admin.listing -> validator -> validator.builder -> cocorico_user.user_manager -> twig.controller.exception -> twig -> security.authorization_checker -> security.authentication.manager". at /var/www/dev/Symfony/app/bootstrap.php.cache line 2173) {"exception":"[object] (Symfony\Component\DependencyInjection\Exception\ServiceCircularReferenceException(code: 0): Circular reference detected for service "cocorico_user.user_manager", path: "sonata.admin.listing -> validator -> validator.builder -> cocorico_user.user_manager -> twig.controller.exception -> twig -> security.authorization_checker -> security.authentication.manager". at /var/www/dev/Symfony/app/bootstrap.php.cache:2173)"} []

It's ok thanks :)
The bundle for payment will be available soon? mangopay? it's really the only thing missing, you really do a good job!


[efr32] radio: asserts during data requests

Describe the bug A clear and concise description of what the bug is.
With very heavy traffic and very heavy MCU load, the following asserts trigger (lines 911, 919, 926):
https://github.com/openthread/openthread/blob/831406ce9055d622a3258a82a1a6ee556530fc49/examples/platforms/efr32mg12/radio.c#L902-L929
To Reproduce Information to reproduce the behavior, including:

Git commit id: 831406ce9055d622a3258a82a1a6ee556530fc49
IEEE 802.15.4 hardware platform: efr32mg12
Build steps: make -f examples/Makefile-efr32mg12 BOARD=BRD4161A
Network topology: 1 NCP + 10 SEDs. The bug occurs on the NCP/RCP.

For this to happen, the MCU has to be very heavily loaded, so that the RAIL interrupt fires late. These asserts are due to the RAIL_IEEE802154_GetAddress and RAIL_IEEE802154_SetFramePending returning RAIL_STATUS_INVALID_STATE because it is too late to modify the outgoing Immediate ACK.
I could submit a PR addressing this, but it's not clear to me if we should inform the upper layers that the frame was acked with FP or not, even if these calls failed.
Expected behavior A clear and concise description of what you expected to happen.
No asserts.
Console/log output If applicable, add console/log output to help explain your problem.
None.
Additional context Add any other context about the problem here.
None.

@dismirlian - thanks finding and reporting this.  You are exactly correct.  The asserts here are far too extreme.  One of our RAIL experts looked over the code and this is what they had to say, "[These RAIL_ functions] can return an error if it's called too late to modify the outgoing ACK due to interrupt latency. While unlikely we probably shouldn't assert because of it we should just make sure we tell the upper layer that we did not set frame pending on this ACK so it knows the end device won't be staying on to listen."  So if you don't mind submitting a PR that would be great.  Thanks again.

Hi @romacdon, thanks for your answer. I'll submit a PR shortly.


fix(tutorial): typing functions in tutorial

To fix #357
There are still two related files but wait for #355 being merged
src/webhook/handlePostback.js
src/webhook/handleInput.js

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

5 of 5 (100.0%)  changed or added relevant lines in 2 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.005%) to 91.054%

Files with Coverage Reduction
New Missed Lines
%

src/webhook/index.ts
2
50.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.005%

Covered Lines:
979

Relevant Lines:
1051

💛  - Coveralls


Test pose code

Hi,
Great work! Can you please share a script to do pose evaluation (similar to test_kitti_depth.py)? I tried loading the weights and creating the model with image sizes as [128, 416], [256, 832], [384, 1248], but all of them resulted in size mismatch errors.
Thanks,
Sai

Thanks for your interest. However, I am currently busy with CVPR submission. I do plan to add the pose evaluation code but I might not have time until the end of this year.

@Yuliang-Zou Thanks, I understand.
I'm currently working towards CVPR as well and as per the new reproducability standards, it'd be great if I can run inference on all the models in this area of work. Since DF-Net is one of the SOTA ones, can you let me know what the image sizes are? I can run the inference on my own.
Thanks for your help,
Sai

Hi @SaiK95 , sorry for the delay. The size is 320x1152, you can find it in the data preparation code here.

Hi @Yuliang-Zou, sorry to bother you again.
Couple of quick questions:

I think one of the reasons I was getting a size mismatch error was the sequence length was 2 in the DFLearner() class. After changing it to 5, that error was avoided. Can you clarify why you double the number of pose outputs in the pose network? Is it to get forward and backward poses?

As of now, by using a sequence length of 5, the number of output channels of the pose_pred layer is 24. But the saved weights has 48 channels. Can you clarify this please?

Hi @SaiK95 , since I am predicting both directions, the number will be doubled. (Actually, I should use the same pose but apply the inverse transform based on it. But at that time, I just chose to predict both directions)

Nevermind, I found the issue. I had to pass sequence length as 5 while calling the setup_inference() function. My bad :)
Thanks for the clarification on doubling the number of pose predictions.


[A11Y] [Web] Get Started Tab Template images not labeled

ENVIRONMENT:
Build number: 56.0.2924.87 beta (64-bit)
Form factor: Chromebook
Browser: Chrome
PRE-REQUISITE
chromevox is ON
STEPS TO REPRODUCE:

Open https://ampstart.com
Navigate to Get Started Tab
Using chromevox, Navigate Step 1: Pick a Template
Navigate to template images

ACTUAL RESULTS:
Images read out template one or template 2
EXPECTED RESULTS:
Template Image should be shown and properly labeled
ATTACHMENT:
https://drive.google.com/open?id=0BwUNSMCBrCB4Ul9kZlBUT0lWTlE

I have a working fix for this in my fork, can have it pulled in soon :)


Setup fails after upgrade to HA 2023.03

Version of the custom_component

4.02
Configuration
Describe the bug
After upgrading to HA 2023.03 I am getting the following error:
Setup failed for custom integration here_weather: Requirements for here_weather not found: ['aiohere==2.0.2'].
I see some (automated?) pull requests that seem to be around dependencies so maybe this is related?
The three full errors form the log are here:
Debug log

2023-03-02 15:47:52.381 ERROR (SyncWorker_18) [homeassistant.util.package] Unable to install package aiohere==2.0.2: ERROR: Cannot install aiohere==2.0.2 because these package versions have conflicting dependencies.
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

[notice] A new release of pip is available: 23.0 -> 23.0.1
[notice] To update, run: pip install --upgrade pip
2023-03-02 15:47:54.686 ERROR (SyncWorker_18) [homeassistant.util.package] Unable to install package aiohere==2.0.2: ERROR: Cannot install aiohere==2.0.2 because these package versions have conflicting dependencies.
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

[notice] A new release of pip is available: 23.0 -> 23.0.1
[notice] To update, run: pip install --upgrade pip
2023-03-02 15:47:57.063 ERROR (SyncWorker_18) [homeassistant.util.package] Unable to install package aiohere==2.0.2: ERROR: Cannot install aiohere==2.0.2 because these package versions have conflicting dependencies.
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

Got the same issue

Thank you for reporting this issue. I think dependency resolution failed because aiohere==2.0.2 was not compatible with the latest python version requirement of homeassistant core. The merged PR should fix the issue. A new version will be released in a few minutes.


Support for TXT records

Add support for the creation of TXT Records.
Example use case would include the creation of DV certificates which cannot be automated.
Note: proxied should not be set.

Done?


Add aarch64 cpu type for 64-bit ARM systems

Add support for ARM64 systems. It currently only works for nightly since no stable release is present.

I think this repo is abandoned since we are moving to rustup.rs. Closing.


Keyboard shortcuts for specific brushes

I'm loving this! Thank you a lot.
Is there any chance to add support for keyboard shortcuts? I'd love to be able to apply some of my common brushes without using the mouse.

Hey,
that is a good idea. Unfortunately I don't have a lot of time right now to implement new features. Are you interested in providing this as a pull request?

I can take a look at it, yes.

The truth is that after a while using this, I don't miss having shortcuts 🙂
So I think we can close this.


⚠ PrivateHD has degraded performance

In 97d6998, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 1997 ms

Resolved: PrivateHD performance has improved in b9915af.


NSP not reporting vulnerable package in tree

Maybe I'm misunderstanding what is going on here but I setup this example repo to showcase what I'm seeing.
Repo: https://github.com/walshie4/nsp-bug-example
I'm specifically targeting this advisory https://nodesecurity.io/advisories/566
In my tree I have hoek v2 which should be reported as vulnerable but when I run nsp check it passes no problem.
What packages in my tree are requesting:

npm ls hoek output

Is this incorrect behavior?

For some reason the hoek vuln isn't being reported with v3 of nsp. I notice older vulns like<EMAIL_ADDRESS>seem to get reported. Version v2.8 seems to report it

I'm getting the exact same problem on a current project.
yarn.lock says we're using an old version of Hoek, but nsp doesn't pick it up as a problem.
@michael-smith-tanium dropping down to 2.8 didn't work for me.

+1


Usage section is missing for quantity component

Duplicates ❌

[X] I have searched the existing issues

Which Figma library is concerned?
Not related to one Figma library
Current behavior 😯
When we go in quantity component page, we can see Overview, Web, Android and iOS sections but not "Usage" section which describe advanced common specification accros all platforms.
That can be cool to add this section and add some do/don't usage of this component.
@GerardPaligot
Expected behavior 🤔
No response
Context 🔦
No response
Screenshots / Videos 📸
No response

@GerardPaligot feel free to reopen if it's still needed.


⚠ Bofrost.at has degraded performance

In 0eed8c4, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1373 ms

Resolved: Bofrost.at performance has improved in 48aa287 after 15 minutes.


WIP: expose serializers

DO NOT MERGE
Exposes some of the serializers for use in https://github.com/informalsystems/ibc-rs/pull/52
Also uses a local version amino to support changes being made there ...

[ ] Referenced an issue explaining the need for the change
[ ] Updated all relevant documentation in docs
[ ] Updated all code comments where relevant
[ ] Wrote tests
[ ] Updated CHANGES.md

@ebuchman Is this something you need in the long run? During the serialization refactor I published all serializers (because of testing in a separate library), but we agreed with Ismail that it shouldn't be necessary. I've opened #263 to track this and make them private again when I was able to move the tests next to the serializers.
Please comment on that issue if you want any of them publiuc and we'll discuss there.

Note: the above mentioned issue was closed, so please open a new one if you decide you need serialization published.

Thanks - this was from an old attempt to get txs working for ibc, i think we can close for now


wiki page for windows problems with microbit etc. is lost

in the prod lab, select microbit. You see the note about windows problems. Beside the fact, that the text is not completely clear, it offers a link to solve the windows problem. But trhe page doesn't exist.
This page should be made visible as soon as possible.

btw: when I copy the hex file directly to the calliope (as in the past, using the Calliope as storage device), the process succeeds. This was not true some weeks before. Has Microsoft solved the problem?
Other Windows users: please test it, too.

Thank you very much! For the next issue in this area, please contact me directly because neither the wiki nor the notes are part of this repository. Btw, someone has deleted the page, which should never happen!!!


Issue with decoding  quotation mark

Which package is this bug report for? If unsure which one to select, leave blank
None
Issue description
I am working with some TripAdvisor API endpoint, which returns a bunch of places in JSON format, near some coordinates. One of the places returned, in my case, is called Restaurace "Otevreno", with the double quotes.
TripAdvisor encodes the string as such: Restaurace "Otevreno".
When i take the response's body from the Cheerio Crawlee context, " is automatically decoded to ", thus breaking the JSON and making JSON.parse raise an error.
This is the API
Code sample
No response
Package version
latest
Node.js version
latest
Operating system
No response
Apify platform

[ ] Tick me if you encountered this issue on the Apify platform

I have tested this on the next release
No response
Other context
Link to slack thread

So, a little investigation writeup:
To construct the context object for the request handler, HttpCrawler._runRequestHandler() calls this._parseResponse(), which, in turn, calls this._parseHTML().
_parseHTML() is overriden in CheerioCrawler, and returns
{
  get body() {
    return isXml ? "..." : $.html({decodeEntities: true})
  },
  // ...
}

Apparently, this was added there to "save memory for highly parallel runs" (source)[https://github.com/apify/apify-ts/blob/c1ae0c6853b32423e22af88ba16ae425f594f5ef/src/crawlers/cheerio_crawler.ts#L649]. However, currently we don't get this effect anyways, since the result of _parseHtml() is immediately destructured here, so when requestHandler, context.body is already a string, and not the getter. (You can trivially verify this by putting a breakpoint/debugger;/console.log() into the getter, and checking at what moment (with what call stack) it is called.
Also, I don't think there's a way to have $.html() return what we want. When a website responds with ``, content-type: text/html:
/* consider a website that responds with
content-type: text/html
{"foo": "
bar < " baz
"}
*/
const crawler = new CheerioCrawler({
    requestHandler({ $ }) {
        console.log($.html({ decodeEntities: false }));
    },
});
// --> {"foo": "
bar < " baz
"}

const crawler = new CheerioCrawler({
    requestHandler({ $ }) {
        console.log($.html({ decodeEntities: false }));
    },
});
// --> {"foo": "
bar < " baz
"}

const crawler = new HttpCrawler({
    requestHandler({ body }) {
        console.log(body.toString("utf8"));
    },
});
// --> {"foo": "
bar < " baz
"}

First case is current behavior of ctx.body, and imo it's bad, because it breaks HTML. Also, it's really confusing that CheerioCrawlingContext.body and HttpCrawlingContext.body return different values (that's kind of what prompted the original report by @gullmar).
The second case is probably also unjustifiable, since it would change current behavior heavily (websites probably contain a lot of quotes, &s and idk what else cheerio decides to escape).

Therefore, I propose we remove body getter, and instead return the original body buffer .toString("utf8"), to have the same data like HttpCrawler, but also keep body as a string to avoid breaking Actors.
It is also ok with me to call this a won'tfix, since website returning JSON with content-type: text/html is just weird.


Add setuptools support

It would be nice if setuptools was supported so its features beyond distutils could be used, e.g. building eggs. I'd be willing to implement this, but I thought I might create an issue first to make sure there's interest in merging it.

Hi Kurt!
Thank you very much for the generous offer! I know it would have been better to use setuptools to package fluids. As you know, packaging can be very frustrating - and once I had distutils working, I moved on and haven't thought about it in almost three years. I already have two setuptools keywords: extras_require and install_requires which aren't doing anything right now.
I would absolutely welcome any help.
Congratulations on your new job as well!
Sincerely,
Caleb


Improve asyncPlaceholder handling

If Haxe function has some default parameters:

private function some(param: String = "asd") {}

then in JS and Python output Haxe adds something like:
if (param == null) {
  param = "asd";
}

and that added code is placed before asyncPlaceholder

In Python Haxe adds sometimes something like

_gthis = self

in the beginning of a function body, before async placeholder.
Probably both cases could be fixed with regexes. In the future would be good to get rid of regexes completely.

Fixed by https://github.com/botsman/hxasync/commit/91e4852e4bef3422c5829e7add931d78608aceff

Fixed by https://github.com/botsman/hxasync/commit/91e4852e4bef3422c5829e7add931d78608aceff


Fix unresponsive "Jump to unread"

Fixes https://github.com/vector-im/element-ios/issues/4071
I think we can remove this check altogether @ismailgulek.
It was introduced in an attempt to fix an issue with notifications not going to the message. But we no longer highlight messages from notifications.
In the codes current state, I don't think this check is having any effect(maybe it did in the past) other than causing a delay in the join.
At the moment it's just called for the "jump to unread" button and when joining a room with an initialEventId, in both cases we are starting the timeline at a point in the past.
When we start the timeline at an event in the past we load an in memory event store rather than the persisted session store.
So from my testing the initial check for the event in this in memory store always fails. We then wait for the next sync, but don't make any requests that would trigger the server to return. This means it hangs for an arbitrary amount of time(0-15 seconds for me), until the server pushes something on sync. During this time the join/jump to unread appear unresponsive.
Then we finalise the room and load the event using /context.

Just to clarify one point, the check failed as past events are stored in the in memory store and while new events go to the session store.


add raw file names next to link to PXD

Currently in the doc. we have this:
The files can be downloaded from the proteomeXchange repository PXD028735 (https://www.ebi.ac.uk/pride/archive/projects/PXD028735) or you can download them from the ProteoBench server here: https://proteobench.cubimed.rub.de/datasets/raw_files/DDA/

The link to proteomeXchange is not enough. We need to add the names of the raw files for users to find them.

The previous version of Proteobench had the download links to the raw files on the main page.
These links are missing at the moment.
The new one needs these links to get everyone started.
We should

what do you mean by "the main page"? We discussed in the past that it would be cleaner to have the download links with the complete explication of the module and how to use it: in the documentation. I think that it is good.
Specially because in the module page, in the tab Submit new data, there is this text:

What I meant when I created this issue was that in the documentation, the link to the PRIDE repo. is not enough. We need to link to individual files, or at least indicate their names.
Does this make sense?
We don't want to duplicate information and have these links in the module streamlit page and in the documentation.

I wasn't aware of this change. Makes sanse to have the information in one place.
However, the links "How to use" and "Data Set" are 'broken' in the DIANN module at the moment.

What are the correct links? I can try to update them.

Also, the link here:
https://proteobench.readthedocs.io/en/stable/available-modules/4-DIA-Quantification/
to the fasta is not working.

I just wanted to suggest something similar, when looking into it. I think it would be great, if there was a list of the actual direct links to the ftp servers for each raw file like so: https://ftp.pride.ebi.ac.uk/pride/data/archive/2022/02/PXD028735/LFQ_Orbitrap_AIF_Condition_A_Sample_Alpha_01.raw Then nobody needs to read any description of which files to download and which ones not.

Yes! Absolutely. Actually, it is the way it was in the past.


GestureEnabled property not working as expected

Using gestureEnabled property is not working as expected. However, when using gesturesEnabled, the navigation behaves as expected
READ ME PLEASE!
TL;DR: Make sure to add your changes to versioned docs
Thanks for opening a PR!
The docs cover several versions of react-navigation, and in some cases there are several files (for version 1, version 2 and etc.) that all describe a single page of the docs (eg. "Getting Started").
Please make sure that the edit you're making in docs/file-you-edited.md is also included in the file for the correct version, eg. /versioned_docs/version-3.x/file-you-edited.md for version 3. If such file doesn't exist, please create it. :+1:

You're using an old version, please refer to the documentation of the version you use or update to latest version.


Allow prefixes to URL

Currently, when an app gets started, we expect that users will access the app via a path like /app// .
We’re rewriting the index path to update the references for the JS & CSS resources (ie, everything that comes from /static in Qd) to point to /app//static, and we proxy that directory to Qd.  For the JS resources, we’re rewriting the websocket path from /_s to /app//ws.  We’re also translating the websocket messages to rewrite /app/ to the route the app is currently listening on.  We’re planning on adding a field to the toml file that allows developers to specify the route they’re using so we can do the correct proxy.  We also rewrite /_f references to /app//_f.
It’s not ideal for us, particularly since the string sub can translate innocent code that breaks the page (we're already seeing this in some situations).  We were wondering if it may be possible to have Qd know that it’s being loaded from a different path (using something like https://muffinman.io/react-router-subfolder-on-server/) that would allow us to avoid doing the translation.
Another option would be to serve apps from a subdomain, ie, .q8s.h2o.ai, and then it’s like it’s running from local.  The concern is that this makes deployment on prem and local testing more difficult (but not impossible)
What we'd like to be able to do:
Allow the browser to fetch /app/<uuid>, and have the app function, and all we need to do is proxy /app/<uuid> to the container without any rewrites.
The HTML base page for the react app has a hardcoded path for /static where it loads the JS resources from, and the JS resources contain a hardcoded path to the websocket (/_s).  Once the websocket connection is established, the browser sends its location to Qd.  We can pass this path ahead of time as an environment variable when we launch the container so that the Qd knows to expect it and allow the app to load on the different path.
Apps might need to know about the prefix as well (ie, if they create a link to somewhere else in the app, they may need to know), so an API may be needed for this purpose.
We're open to other suggestions as well

A few points that arose after discussion with @keznikl:

The auth paths (and their redirects) need to respect base URL as well, e.g. /base-url/auth. It currently returns 404.

Minor: Assume leading / if not specified by the user, otherwise results in a python error:

Minor: Consider renaming base-url to base-path as that's what it is actually.

cc @lo5 ^^

The auth paths (and their redirects) need to respect base URL as well

Thanks for catching - fixed. There were hard-coded paths in the auth backend/frontend that caused this.

Minor: Assume leading / if not specified by the user

Is this for the @app() / site[...] in Python or -base-url? I don't think we have any examples in the docs that omit the leading /, do we?

Minor: Consider renaming base-url to base-path as that's what it is actually.

I thought through this before coming up with -base-url. I agree that technically it's a path and not a URL, but "base path" has other connotations and it's not immediately obvious that it's a "path that is part of the URL". Base URLs sans paths are employed by other projects, e.g. Typescript, Jekyll.

Closing as HAC team confirmed this feature works as expected.

Except the logout handling (which does not seem to work?)

@keznikl The logout issue was fixed via https://github.com/h2oai/wave/commit/24d2a826db725b900044e5214c25078ad0a75ae6
Are you still facing issues?


pull request for e2e test at 11/12/2016 00:26:07

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


getting signature as binary (Help, it's my first attempt doing erlang)

trying to address #4

@ceolinrenato cool! Thanks for the PR. I think we could have a slightly different approach: we could pass the URL and the existing query params, and the function could return the signed query params. This would be similar to what sign_v4 does, but returning a list of query params that you can use in your URL. WDYT?

You didn't ask me, but I'm :+1: on that idea

Humm like a sign_v4 but instead of injecting the date header and the content hash headers we create those for the query string?
I think this would only work for GET method use cases. We'll need to return X-Amz-Algorithm, X-Amz-Credential, X-Amz-SignedHeaders (in this case will always be just host), X-Amz-Date and X-Amz-Signature
How should we call that function?

IMO it should be something like sign_v4_and_return_signed_params (open to shorter names of course lol)

I thought about returning the signature alone because of the multiple use cases that could exist in the AWS ecosystem. Like presign a S3 bucket object url for temporary download access, presign a url to upload a object (so the upload could go directly from client side to AWS s3). I'm sure there would be even more.
Right now sign_v4 always adds an authorization header and needs a request that has a body. But those 2 use cases I've mentioned earlier you need to use UNSIGNED-PAYLOAD as the body part in the canonical url. Also they don't use any headers, so the only signed header is "Host" which is mandatory by AWS specifications

@ceolinrenato I see. My concern is that the signature function is too "vague/open" for the end user. I would prefer to have specialized functions for each use case you mentioned.
 I will let you know. Thanks!

@mrallen1 I'm inclined to sign_v4_query_params. WDYT?

Sgtm


Update jsonschema to version 3.0.1 + switch from Draft 4 to Draft 7

Seems to works flawlessly in my project.

@danie1k  Why you need Draft7? OpenAPI 3 uses extended subset of JSON Schema Specification Wright Draft 00 (aka Draft5)

The Schema Object allows the definition of input and output data types. These types can be objects, but also primitives and arrays. This object is an extended subset of the JSON Schema Specification Wright Draft 00.

https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md#schema-object

@p1c2u

Why you need Draft7?

The idea started simply - because it's newest available JSON Schema specification version, and draft-05 is officially abandoned.
But it all started from connexion package: zalando/connexion#983 & zalando/connexion#996 which rely on jsonschema (which supports draft-07) + openapi-spec-validator + custom code.

OpenAPI 3 uses extended subset of JSON Schema Specification Wright Draft 00 (aka Draft5)

I haven't know that. It seems that I need to get know better specifications of both, OpenApi & JSON Schema. I've read a lot of documentation, but not much enough; thanks for the link.


Unknown entry types not remapped to @misc

The biblatex documentation states

All unknown entry types are generally exported as @misc.

and indeed earlier this year I posted https://tex.stackexchange.com/a/434285/35864 on TeX.SX where the MWE
\documentclass[british]{article}
\usepackage[T1]{fontenc}
\usepackage[utf8]{inputenc}
\usepackage{babel}
\usepackage{csquotes}

\usepackage[style=authoryear, backend=biber, dashed=false]{biblatex}

\usepackage{filecontents}
\begin{filecontents}{\jobname.bib}
@book{appleby1,
  author   = {Humphrey Appleby},
  title    = {On the Importance of the Civil Service},
  subtitle = {The Book},
  date     = {1981},
}
@software{appleby2,
  author   = {Humphrey Appleby},
  title    = {On the Importance of the Civil Service},
  subtitle = {The Software},
  date     = {1982},
}
@flobbel{appleby3,
  author   = {Humphrey Appleby},
  title    = {On the Importance of the Civil Service},
  subtitle = {The Nonsense},
  date     = {1983},
}
\end{filecontents}

\addbibresource{\jobname.bib}
\addbibresource{biblatex-examples.bib}

\DeclareFieldFormat{entrytype}{\texttt{@#1}}
\renewbibmacro*{begentry}{\printtext{Hello, I'm a \printfield{entrytype}}\newunit}

\begin{document}
\cite{appleby1,appleby2,appleby3}
\printbibliography
\end{document}

gave

Hello, I'm a @misc.

for the @flobbel entry.

But with a current Biber 2.12 the MWE passes the @flobbel right through, so I get

Have there been any changes to this area?
I though I'd check with 2.11 and 2.10 from Sourceforge to see where the behaviour went overboard and found that neither of the two shows

Hello, I'm a @misc.

as I expected. Instead both give

Hello, I'm a @flobbel.

So now I'm wondering if I went mad or if the behaviour changed at some point.

Hmm, I have a vague memory that this was changed because silently correcting data model errors was felt to be a mistake? What is your opinion?

Ok, I have removed that line from the doc. I can also add a biber warning about unrecognised types as I believe we do about unrecognised fields?

There is no Biber warning about unknown fields with the default settings at the moment (indeed, it is one of the features of BibTeX that unknown fields are discarded silently), so I think it is OK not to issue a warning for unknown types. A warning will be issued by biblatex if no driver is found, that should be enough for most users.

Ah, right, I think we took out the field warning for exactly that reason. Ok, then I think it's all ok.


Add CI build configuration

Adds configuration files for CI on self-hosted runners and the HPC.

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


Script in subfolders

Hi, thanks for your script: most useful!
I can't find a way to make it works when it's in subfolders.
I would like it in /administrator/showtable/showtable.php
"administrator" because it's already protected by a .htaccess/.htpasswd which is convenient.
"showtable" because I need to make several scripts and I want to collect them.
I've changed the root constant but it's not enough or I don't know how to do it properly.
Regards
Marc

Hi Christophe,
I've tried public const ROOT = '/administrator/showtable/'; with and without the ending slash.
The script says: The file /administrator/configuration.php can't be found, please review the ROOT constant to match your website root folder
I've tried to put the script in administrator (not in 'showtable' subdirectory)  public const ROOT = '/administrator/'; with and without the ending slash.
The script says: The file /administrator/configuration.php can't be found, please review the ROOT constant to match your website root folder
Any idea?

The full path Marc; not the relative one.
And ROOT should be the root of your Joomla site so, something like public const ROOT = '/var/www/mysite';.
That path is where you'll find the configuration.php file of Joomla.

Ok, got it.
My configuration.php is there:
/home/testsite/public_html/configuration.php
The script is there:
/home/testsite/public_html/administrator/showtable/showtable-test.php
So ROOT should be
public const ROOT = '/home/testsite/public_html/';
or
public const ROOT = __DIR__ . '/../../';
but the result is
`Warning: include_once(/home/testsite/public_html/administrator/showtable/includes/defines.php) [function.include-once]: Failed to open stream: No such file or directory in /home/testsite/public_html/administrator/showtable/showtable-test.php on line 453
Warning: include_once() [function.include]: Failed opening '/home/testsite/public_html/administrator/showtable/includes/defines.php' for inclusion (include_path='.:/usr/share/php') in /home/testsite/public_html/administrator/showtable/showtable-test.php on line 453
Warning: include_once(/home/testsite/public_html/administrator/showtable/includes/framework.php) [function.include-once]: Failed to open stream: No such file or directory in /home/testsite/public_html/administrator/showtable/showtable-test.php on line 456
Warning: include_once() [function.include]: Failed opening '/home/testsite/public_html/administrator/showtable/includes/framework.php' for inclusion (include_path='.:/usr/share/php') in /home/testsite/public_html/administrator/showtable/showtable-test.php on line 456
Fatal error: Uncaught Error: Class "Joomla\CMS\Factory" not found in /home/testsite/public_html/administrator/showtable/showtable-test.php:459 Stack trace: #0 /home/testsite/public_html/administrator/showtable/showtable-test.php(190): ShowTable->loadConfiguration() #1 /home/testsite/public_html/administrator/showtable/showtable-test.php(512): ShowTable->__construct() #2 {main} thrown in /home/testsite/public_html/administrator/showtable/showtable-test.php on line 459`

But if I change
/* Initialize Joomla framework */
        define('_JEXEC', 1);
        // Load system defines
        if (file_exists(__DIR__ . '/../../' . '/defines.php')) {
            include_once __DIR__ . '/../../' . '/defines.php';
        }

        if (!defined('_JDEFINES')) {
            define('JPATH_BASE', __DIR__ . '/../../');
            include_once JPATH_BASE . '/includes/defines.php';
        }

it works fine.

So, in your case, public const ROOT = '/home/testsite/public_html'; should do the trick.
I've quickly checked my code (in fact the last changes done a few weeks ago) and my code isn't correct; so it's my fault.
I've patched the file (https://github.com/cavo789/joomla_show_table/commit/1733a8be78dcff541df04b4603e5b156ffc67f2a).
Can you get the last version and check again; sorry.

But if I change
/* Initialize Joomla framework */
        define('_JEXEC', 1);
        // Load system defines
        if (file_exists(__DIR__ . '/../../' . '/defines.php')) {
            include_once __DIR__ . '/../../' . '/defines.php';
        }

        if (!defined('_JDEFINES')) {
            define('JPATH_BASE', __DIR__ . '/../../');
            include_once JPATH_BASE . '/includes/defines.php';
        }

it works fine.

I was on it on the exact same time ;)

Yes, thanks.
The updated script works fine now, with only the ROOT constant to adapt.
Thanks!
Since we're at it, it seems that line 262 is redundant?
"		'fixedHeader': false,\n" .
And a suggestion: since in your doc you give advice to copy/paste queries tested in Adminer/phpMyAdmin it is far more convenient to present your exemple query in Heredoc syntax.
Thanks again.
Marc

Oh, I'll remove the line 262; nice.
For Heredoc, you're right but I personally don't like this syntax.  It's just a question of taste and colors ;)
With some editor, Heredoc will break your layout like the ability to fold all the code or some formatting tools don't like them.
But you're right, it's more convenient since just copy/paste.


Unable to access application via Service locally following 'Using a Service to Expose Your App' tutorial

Using a service to expose your app tutorial not found:
in this part:
curl http://"$(minikube ip):$NODE_PORT"
i don`t have any answord.
I tried in remplace:
curl http://:
the ip and port, i got with:
kubectl describe

Page related to issue: https://kubernetes.io/docs/tutorials/kubernetes-basics/expose/expose-intro/
/language en

/retitle Unable to access application via Service locally following 'Using a Service to Expose Your App' tutorial

Similar (possibly duplicate) related issues we already have https://github.com/kubernetes/website/issues/41438 https://github.com/kubernetes/website/issues/40645

/triage duplicate

https://github.com/kubernetes/website/issues/40645 is now closed.
I believe it is sufficient to close this issue as well.

Looks like a fix has been delivered. Closing this issue in acknowledgment of the contributor's comment indicating the implementation of the fix.
/close


permission_target include_pattern duplicated

Terraform 0.13
Provider 2.2.4
Artifactory 6.23.1
If you import an artifactory_permission_target, the resource will have conflicting includes_pattern
resource "artifactory_permission_target" "conan-read" {
    name = "conan-read"
    repo {
        excludes_pattern = []
        repositories = [
            "conan-local",
            "conan-remote",
        ]
        actions {
            groups {
                name = "conan-read"
                permissions = [
                    "read"
                ]
            }
            users {
                name = "anonymous"
                permissions = [
                    "read"
                ]
            }
        }
    }
}
``

artifactory_permission_target.conan-read will be updated in-place
~ resource "artifactory_permission_target" "conan-read" {
id               = "conan-read"
+ includes_pattern = "**"                         <------------- note that it will automatically add includes pattern
name             = "conan-read"
  ~ repo {
        excludes_pattern = []
      ~ includes_pattern = [
          - "**",
        ]
        repositories     = [
            "conan-local",
            "conan-remote",
        ]

        actions {
            groups {
                name        = "conan-read"
                permissions = [
                    "read",
                ]
            }

            users {
                name        = "anonymous"
                permissions = [
                    "read",
                ]
            }
        }
    }
}

## Workaround 1

If you try and explicitly add the includes_pattern to the resource, it will throw an error

resource "artifactory_permission_target" "conan-read" {
name = "conan-read"
includes_pattern = "**" <---------------- Added this line here
repo {
excludes_pattern = []
repositories = [
"conan-local",
"conan-remote",
]
actions {
groups {
name = "conan-read"
permissions = [
"read"
]
}
users {
name = "anonymous"
permissions = [
"read"
]
}
}
}
}

Error: "includes_pattern": conflicts with repo
on permission:conan-read.tf line 1, in resource "artifactory_permission_target" "conan-read":
1: resource "artifactory_permission_target" "conan-read" {

## Workaround 2

resource "artifactory_permission_target" "conan-read" {
name = "conan-read"
repo {
excludes_pattern = []
includes_pattern = [
"**"                                     <------- added this line here
]
repositories = [
"conan-local",
"conan-remote",
]
actions {
groups {
name = "conan-read"
permissions = [
"read"
]
}
users {
name = "anonymous"
permissions = [
"read"
]
}
}
}
}

terraform apply will still show that it is trying to add the parameter `includes_pattern`

artifactory_permission_target.conan-read will be updated in-place
~ resource "artifactory_permission_target" "conan-read" {
id               = "conan-read"
+ includes_pattern = "**"        <------------ terraform is adding this line here
name             = "conan-read"
    repo {
        excludes_pattern = []
        includes_pattern = [
            "**",                                 <----- which is a duplicate of this line here
        ]
        repositories     = [
            "conan-local",
            "conan-remote",
        ]

        actions {
            groups {
                name        = "conan-read"
                permissions = [
                    "read",
                ]
            }

            users {
                name        = "anonymous"
                permissions = [
                    "read",
                ]
            }
        }
    }
}

I think removing this line should solve the problem:
https://github.com/jfrog/terraform-provider-artifactory/blob/65f21531883fca5674bff38edb835bf865285477/pkg/artifactory/resource_artifactory_permission_target.go#L140
Though I don't see why any of these lines are really needed:
https://github.com/jfrog/terraform-provider-artifactory/blob/65f21531883fca5674bff38edb835bf865285477/pkg/artifactory/resource_artifactory_permission_target.go#L136-L158

@jomast You're right, I've removed the default value. I left the legacy fields in just in case anyone's actually using them, but I can look into removing them at some point. For now though, they don't seem to get in the way (at least not anymore), so leaving them as-is should be fine.


#124 fixed more nullable Warnings when targeting net8.0

fixed LoggingEventTest for execution in CE(S)T or SAST
added missing nullable attributes from net6-8
added Log4NetAssert
fixed more nullable Warnings when targeting net8.0

for #124

@erikmav can you take a look?

LoggingEventTest wasn't successful in CEST
fixed more nullable Warnings when targeting net8.0 api

To aid understanding - are you considering adding net8.0 as a target for the 3.0 package? I kind of like it as there are perf optimizations that can be added like avoiding params object[] for up to 3 format params using https://learn.microsoft.com/en-us/dotnet/api/system.string.format?view=net-8.0#system-string-format-3(system-iformatprovider-system-text-compositeformat-0-1-2) .

@erikmav thanks for your feedback. I adjusted the files.
I'm definitely thinking about adding .net8 as target.
I had the same idea for interpolated strings (especially for the LogLog-class).


ModuleNotFoundError: No module named 'utils_box'

When I run the imports cell, this iimport error occurs:
CELL:
`import tensorflow as tf
import numpy as np
import concurrent.futures
from threading import Lock
import json, math, random, os, pprint
from matplotlib import pyplot as plt
import matplotlib as mpl
import utils_box as box
#import box_ops as box
AUTO = tf.data.AUTOTUNE
pp = pprint.PrettyPrinter()
print("TensorFlow version", tf.version)
from tensorflow_models.vision import box_ops as boxutils`
ERROR:
`ModuleNotFoundError                       Traceback (most recent call last)
 in ()
6 from matplotlib import pyplot as plt
7 import matplotlib as mpl
----> 8 import utils_box as box
9 #import box_ops as box
10 AUTO = tf.data.AUTOTUNE
ModuleNotFoundError: No module named 'utils_box'
Is there any other package able to replace this one?

Yeah, Same here. Can anyone tell me what to do?

I can't find utils_box library in PyPi.
But I replace the usage of utils_box for box.scale_rois with this function.
def scale_rois(boxes, image_size):
  return tf.concat([
      boxes[:, :2] * tf.expand_dims(image_size, axis=0),
      boxes[:, 2:] * tf.expand_dims(image_size, axis=0)
  ], axis=1)


Breaking change in SQL Server Database Retention Policies create_or_update APIs

SQL Server APIs to create or update Retention Policies recently had a breaking change not reflected in swagger.
Before: When called PUT, returned an object with the created\updated policy details.
Current: Returned an object with an operation status
It breaks tools using these APIs because SDK still behaves the old way and expects the BackupShortTermRetentionPolicy object

service team need update Swagger to align with service behavior. HI @logachev  could you pls share which version tag of API you're using?

@logachev since the last activity here is from end of September I am going ahead and close this issue. Please respond if you need more help.

@yungezz please close this issue.

@jeroenterheerdt Sorry for the late reponse.
It appeared an issue was on our side. Closing.


The value larger than 16 digits in response is rounded in UI display

Hi,
I want to return the value of Int64 or UInt64.
But wrong value has been displayed in Swagger UI.
Controller:
[HttpGet] public IActionResult GetValue() { return Ok(Int64.MaxValue); }
Int64.MaxValue =<PHONE_NUMBER>854775807
Response body (in Swagger UI):
9223372036854776000
Why is it rounded up?
Other tools (e.g.Postman) showed the correct value.
9223372036854775807

The UI is constrained by JavaScripts max int:
https://github.com/swagger-api/swagger-ui/issues/299

Thank you for answering.
Sorry, I did not know that it was a known matter.


Update renovatebot/github-action action to v41

This PR contains the following updates:

Package
Type
Update
Change

renovatebot/github-action
action
major
v40.3.5 -> v41.0.2

Release Notes

renovatebot/github-action (renovatebot/github-action)
v41.0.2
Compare Source
Build System

compile as esm (#888) (e8fc25c)

v41.0.1
Compare Source
Miscellaneous Chores

deps: update dependency eslint to v9 (#881) (d4f5ed0)
renovate: fix config (#884) (1eb9d9b)

Tests

e2e: test with default version (#886) (d16f12d)

Build System

use esbuild (#887) (4a407be)

Continuous Integration

deps: update renovate docker tag to v39 (#885) (f8106c1)
simplify (#883) (a060887)
use github-actions[bot] for merge commit (#882) (4c22a10)

v41.0.0
Compare Source
⚠ BREAKING CHANGES

Renovate is now pinned to v39.

Features

pin renovate major version (#880) (c31251b)

v40.3.6
Compare Source
Bug Fixes

refactor: use named imports (#879) (4d91b7f)

Documentation

Fix permissions for Renovate 39 (#873) (80524aa)
update references to ghcr.io/renovatebot/renovate to v39 (fa742b7)

Miscellaneous Chores

deps: update dependency @semantic-release/github to v11 (#876) (03986b7)
deps: update dependency @types/node to v20.17.2 (9b8168b)
deps: update dependency @types/node to v20.17.3 (62e9650)
deps: update dependency @types/node to v20.17.4 (b274faf)
deps: update dependency @types/node to v20.17.5 (de0fb82)
deps: update dependency eslint-plugin-json to v4 (#874) (205c9ef)
deps: update dependency npm-run-all2 to v7 (#877) (7b3e4ff)
deps: update typescript-eslint monorepo to v8 (major) (#878) (5343762)
husky migration (#875) (c884ed2)

Continuous Integration

deps: update renovate docker tag to v38.142.7 (5bf87b6)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This only pins renovate version. Should not cause problems.


Support large jars

Currently,
We are using akka messages to pass the jars, there maybe size limitation.
We need to find a robust way to distribute the jars.

If the client is not uploading the jar to the master (which could be done - the client wouldn't exit until the jar upload to master was complete), then the client could pass a URL reference which could be http, hdfs, etc. Assumption is this URL is available from the master.

If the client is not uploading the jar to the master (which could be done - the client wouldn't exit until the jar upload to master was complete), then the client could pass a URL reference which could be http, hdfs, etc. Assumption is this URL is available from the master.


CSRF token is missing Error

While integrating Superset with our webpage , we receive the following error:
Bad Request
The CSRF session token is missing.

You can disable CSRF protection by setting the config WTF_CSRF_ENABLED = False. This will disable all CSRF protection which has security implications.

Alternatively you can disable CSRF protection on certain routes with this config https://github.com/preset-io/incubator-superset/blob/master/superset/config.py#L173

If you upgraded lately to 0.37 this might have happen to you
Try to clean the cookie in Dev tools under application tab in chrome browser


Issue with consumer group example

Description
Context
From the example provided in this repository, a single consumer is created within the consumer group to process messages, and it gets assigned to all partitions of a Kafka topic. However, Kafka's design encourages leveraging partitioning to enable parallelism, which seems to favor multiple consumers within the same group for optimal resource utilization.
To align with Kafka's design and achieve partition-level parallelism, we are exploring a setup where N consumers are initialized within the same consumer group. This involves creating N clients and passing them to the NewConsumerGroupFromClient function with the same consumer group ID.
Questions

Is this model valid?

Can we create multiple consumers within the same group by initializing multiple clients and assigning them to the same consumer group ID?

Rebalancing and Partition Assignment:

How does the partition rebalancing handling work when using this model?
If the number of partitions increases or decreases, how are the changes reflected across the multiple consumers within the group?

Versions

Sarama
Kafka
Go

Configuration

Logs

logs: CLICK ME

Additional Context

Hi @dnwe / @puellanivis, been browsing the past issues and saw that you are active contributors to this repo, could you please help share some insights when you get a chance? TIA!


[Windows] Add trailing slash to NSTemporaryDirectory result

NSTemporaryDirectory on Darwin returns path with trailing slash, and almost every test in TestFileManager counts on it.
Without slash tests are generating temporary paths like C:\Users\user\AppData\Temptest_isReadableFile5004BFCF-4356-4000-8000-000000000000, which is, obviously, out of Temp directory.
Non-Darwin and non-Windows platforms have already implemented similar workaround, so I just adapted existing solution for Windows.

CC @compnerd

@swift-ci please test


Updates the charm metadata

Description
Includes website, source, and issues URLs.
Checklist:

[ ] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that validate the behaviour of the software
[ ] I validated that new and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I have bumped the version of the library

Tests failing due to #20

Now waiting on https://github.com/canonical/sdcore-nrf-operator/pull/42


Fix the bug for test_spdm_requester crashes with OpenSSL in Linux

Signed-off-by: Wenxing Hou<EMAIL_ADDRESS>Fix: #277

please add more comment:
time_t is 4 bytes for 32bit machine and 8 bytes for 64bit machine.

time_t is 4 bytes for 32bit machine and 8 bytes for 64bit machine.
time_t is migrating to 64 bits on all architectures due to https://en.wikipedia.org/wiki/Year_2038_problem
For example see https://musl.libc.org/time64.html

approved. We can see if there is need to change to int64 in the future.


Increment version for storage releases

Increment package version after release of azure-storage-blob

Will do this manually !


Not to send a discovery request at GrpcSubscriptionImpl destructor

Description:
This change tries to fix https://github.com/envoyproxy/envoy/issues/4352
The root cause with detail log is described at: https://github.com/envoyproxy/envoy/issues/4167
This PR is a re-open of closed PR: https://github.com/envoyproxy/envoy/pull/4178
Problem:
When GrpcSubscriptionImpl is deleted, it tries to send one more request update.  Newly added sds_api is using GrpcSubscriptionImpl which is owned by a ListenerImpl.  When server is killed, GoogleAsyncClientThreadLocal is removed before ListenerManager is deleted.   Hence the crash.
Ideal solution (suggested by htuch)
When GoogleAsyncClientThreadLocal is removed, somehow notify all its clients;
GoogleAsyncClientImpl, not to send any more requests.  The Google grpc code is fairly complicated.  It is not easy to achieve.  The change could be big and high risk.
Short-team solution:
When GrpcSubscriptionImpl is deleted, not to send last request update.  The change is simple and low-risk.
Risk Level:  Low
Testing:   tested with
bazel test --runs_per_test=1000 //test/integration:sds_dynamic_integration_test
Docs Changes: No
Release Notes: No
[Optional Fixes #Issue]
[Optional Deprecated:]

@htuch Please help to review this change.


Question: Set Easing via RN Animated API

Is it possible to create a linear based animation in After Effects and then set the easing curve or spring via Animated API?

Of course, easing is nothing more than manipulation of the frame rate. I say of course with one caveat - you must use the imperative animation methodology to control the animation and provide the easing function you would like used to interpolate the frames.

@cth0mas Oh nice, I didn’t think about doing that. Why would one need to use the imperative way? Just specify easing via Animated.timing?

Yes exactly. Imperative animation in the scope of Lottie is controlling the progress of the total animation cycle from 0 to 1 using an Animated.Value, along with the range you simply set the easing function like any other Animated.timing call. I prefer imperative due to the ability to hook into loop cycles and kick off another loop if the situation calls for it.
I don't know about the latest version of Lottie, but I had to specify linear for all animations that looped or they would stutter due to the default easing.
I'll copy in some sample code when I have a chance.

@cth0mas I’ll try this and report back. I’m interested to see if linear AE animation with easing set via Animated will behave how I expect it to.

In my experience, Bodymovin converts AE frames to Lottie json, somewhere in there it does specify AE easings and if you use the play functionality of Lottie you will get the easing you exported, however - if you use imperative you are controlling the frame transition ease via Animated API.

@zachgibson here is a common scenario for my use of Lottie that I think will help your cause:
...
import animation from "../../lottie/animation.json";
//linear frame transitioning is needed as Animation.timing defaults to ease with imperative use
const linearEasing = t => t;
//Calculated animation duration for imperative use
calcDuration(source) {
return source != null
? Math.round(source.op / source.fr * 1000)
: 60;
}
...
Play() {
// reset progess to 0 in case of looping function
this.state.animation.progress.setValue(0.0);
Animated.timing(this.state.animation.progress, {
to: 1.0,
easing: linearEasing,
duration: calcDuration(animation),
useNativeDriver: true
}).start(() => {
//place callback logic here to loop animation or do other stuff after each animation cycle...
if(shouldLoop)this.Play();
if(shouldExist)this.PlayExit();
});
}


Too much spacing between characters in mobile Edge

Issue Summary
I found the bug in this issue. In Edge for Android mobile, there are excess spacing between characters, but this does not occur in Edge for Windows.
Steps to Reproduce:
$$\mathit{xyz}\operatorname{sgn}\sin xyz$$

On Edge for Windows (expected):

On Edge for Android mobile (unexpected excess spacing):

Technical details:

MathJax Version: 3
Client OS: Android 10
Browser: Edge 101.0.1210.53

Supporting information:
If you view this webpage on mobile Edge, the math is not rendered the same as on desktop.

I'm not able to reproduce this on Android 11 with the same version of Edge on an actual device, nor in Android 10 on Saucelabs.com with their Samsung Galaxy S9 device. This was trying both your page linked above, and the MathJax.org live example.

On my device (Xiaomi Mi Max 3, MIUI 12 20.9.4 Beta), this problem can be reproduced. It seems weird that the same browser behaves differently on different Android devices. Cannot think of any reasons why this cannot be reproduced (or, why I have this issue).

Cannot think of any reasons why this cannot be reproduced (or, why I have this issue).

It does seem strange, and I don't have any answers for you.  But without being able to test it, I really don't know what to do to resolve the issue for you.  I'm sorry not to be able to help!

Reproduced in the embedded browser of Instagram.


Verify push to page design

https://github.com/Expensify/App/pull/21553#issuecomment-1609933984

When a push row has no value, the label should float vertically and have a font size of 15px which matches our default font size. Then when it does have a value, the label is at 13px and sits above the value:

In your screenshot, the labels with no value are too small.

Let's verify what we're using for the push to page font values. I believe we're using the same general component but those styles might have been updated somewhere
cc @shawnborton

Thanks!

@thienlnam @shawnborton I checked and this is not the standard in app anymore, maybe the code was removed -

https://github.com/Expensify/App/blob/c122266f96bab047cda55f0cebff8b3a61e97700/src/components/MenuItem.js#L89-L96
In line 93, we can see that if title (value) is populated then only margin is added. font-size is fixed in textLabelSupporting as 13px -
https://github.com/Expensify/App/blob/c122266f96bab047cda55f0cebff8b3a61e97700/src/styles/styles.js#L1042-L1046

@thienlnam @shawnborton I checked and this is not the standard in app anymore, I think the code was removed at some point -

What is the root cause of that problem?
https://github.com/Expensify/App/blob/c122266f96bab047cda55f0cebff8b3a61e97700/src/components/MenuItem.js#L89-L96
In line 93, we can see that if title (value) is populated then margin is added otherwise we don't change font-size to 15px. font-size is fixed in textLabelSupporting as 13px -
https://github.com/Expensify/App/blob/c122266f96bab047cda55f0cebff8b3a61e97700/src/styles/styles.js#L1042-L1046

Screenshots

What changes do you think we should make in order to solve the problem?
We just need to add it back like -
props.title ? descriptionVerticalMargin : StyleUtils.getFontSizeStyle(variables.fontSizeNormal),

Welp, let's fix it!

Hah - lovely. Let's just make it external!

@fedirjh Could you please review this proposal? https://github.com/Expensify/App/issues/21715#issuecomment-1610044723

https://www.upwork.com/nx/wm/offer/25415819 - @fedirjh
https://www.upwork.com/nx/wm/offer/25415841 - @Nikhil-Vats
Will pay on 10th!

Everyone's been paid!


Scala 2.13.7

This PR updates the .github/workflows/build.yml to Scala 2.13.7 and the default value of SCALA_VERSION args in the Dockerfiles.
Thank you very much for this project, I use it whenever I can :)

Thanks @valencik
Will merge once the build succeed


icono-frown mouth is misplaced

Hey @ksherlock , which browser did you screenshot?

Hello, that was from Safari Version 8.0.2 (10600.2.5) (OS X/Mavericks).  Firefox and chrome seem to display it fine.