Difference between kafka and kafka2 images

What's the difference between the kafka and kafka2 docker images? The only difference I noticed is in the match directive of their conf/fluentd.conf files.

https://github.com/fluent/fluentd-kubernetes-daemonset/blob/master/docker-image/v1.14/debian-kafka/conf/fluent.conf
https://github.com/fluent/fluentd-kubernetes-daemonset/blob/master/docker-image/v1.14/debian-kafka2/conf/fluent.conf

What do these match differences do? Are there any other major differences? I'm trying to figure out which one to choose.

kafka2 is the recommended one.
kafka is for Fluentd's old v0.12 API, will be removed in the future.
https://github.com/fluent/fluent-plugin-kafka#buffered-output-plugin


No functionality to upload datasheets (pdf) to antibody records.

Current workflow is to upload a pdf datasheet (when available) to each curated antibody.
This functionality does not currently exist.

data on antibody_files. Only the curator can add them

need to also implement the import

@afonsobspinto please check this as you have your hands on the import


[type: refactor] Fix agent module failed to load opentracing dependency

// Describe your PR here; eg. Fixes #issueNo

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #2674 (e2c5379) into master (92ab2a6) will decrease coverage by 0.03%.
The diff coverage is n/a.

:exclamation: Current head e2c5379 differs from pull request most recent head fd9615a. Consider uploading reports for the commit fd9615a to get more accurate results

@@             Coverage Diff              @@
##             master    #2674      +/-   ##
============================================
- Coverage     59.95%   59.92%   -0.04%
- Complexity     4348     4353       +5
============================================
  Files           679      679
  Lines         19469    19469
  Branches       1727     1727
============================================
- Hits          11673    11667       -6
- Misses         6833     6838       +5
- Partials        963      964       +1

Impacted Files
Coverage Δ

...apache/shenyu/admin/utils/ShenyuDictH2Trigger.java
63.63% <0.00%> (-9.10%)
:arrow_down:

...henyu/plugin/grpc/resolver/ShenyuNameResolver.java
58.51% <0.00%> (-5.32%)
:arrow_down:

Continue to review full report at Codecov.

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


Katie Tigue's YAML file for HFOSS

Need to add First Flight posts onto this yaml files

added first flight, good to go!

updated pull request, fixed a typo

:one: :airplane:


Fix error with code output

Two commits, one to remove a linefeed from an error log to keep logs consistent. The second to fix the error output in the case of ErrWithExitCode so that the code is displayed if present.

I'd like to rework this, the output is not what I desired.


[FEAT] Add a dataprovider using KY

Is your feature request related to a problem? Please describe.
Most data providers use of Axios which is considered deprecated by (many/some). See adios-axios. Nowadays Native Fetch APIs are widely supported by all big browsers. A thin wrapper like KY provides an easy API to make use of functionalities like interceptors.
Describe alternatives you've considered
No response
Additional context
Axios was once a convenient library that utilized XMLHttpRequest in web browsers and the http module in Node environments. However, in today's modern development landscape, this approach has been surpassed by the native Fetch API, which offers consistent functionality across browsers, Node, and even other environments.
With the adoption of a unified API like Fetch, you can easily eliminate Axios as an additional dependency in your modern codebase, resulting in reduced bundle sizes. Moreover, the Fetch API has undergone full standardization, unlike Axios, which comes with its own set of nuances that often catch developers off-guard. This includes differences in how fetch and Axios handle promise rejection in various scenarios.
Furthermore, certain frameworks, like Next.js, have begun exposing additional features within the Fetch API that may not be readily accessible when using Axios.
Discussion was started here:
https://github.com/refinedev/refine/discussions/6375#discussioncomment-10799548
Issue was opened for better tracking.
Describe the thing to improve
Add ky support @refinedev/simple-rest/ky
Once the simple-rest-ky provider is implemented it might be used as a blueprint for upcoming providers e.g. Strapi 5

@capsloq thanks for the issue. About exposing it as @refinedev/simple-rest/ky, you can check our nextjs-router package. We have @refinedev/nextjs-router/app and also @refinedev/nextjs-router/pages exports separately.
https://github.com/refinedev/refine/blob/master/packages/nextjs-router/package.json

Hi, can I work on this?

hey @BatuhanW , I am working on adding the KY data provider to the @refinedev/simple-rest package. I’ve created a new provider-ky.ts file that mirrors the existing Axios provider, but uses the KY HTTP client for requests. will create a pull request soon. Let me know if you have any feedback or suggestions!

@OmkarBansod02 Nice! I can help with testing if you want

@kfern Yeah sure! i have open a PR. once go through it.


about disconnect

How can I detect a disconnected connection? I need to perform some business-level operations when the connection is lost, as well as attempt to reconnect.

You can check the status with ModbusClient::isConnected or ModbusClientTransport::isConnected.
The client will automatically reconnect, with some variation of behavior depending on the values of connectPersistent and reconnectLazy in the NettyClientTransportConfig.

What I do is to use the CompletableFuture returned by e.g. the sendRequest method...
CompletableFuture<> f = modbusMaster.<ReadHoldingRegistersResponse>sendRequest(new ReadHoldingRegistersRequest(…), …)

...and then to handle exceptions on the future, using
f.whenComplete((answer, t) -> {
  if (t != null && t.getCause() instanceof IOException) { … }
});

Looks a bit cumbersome, especially because the exception I'm interested in is a nested exception, but works ;)
The nested exception could also be a ModbusTimeoutException or ModbusResponseException which you could also be interested in.

My answer was concerning the current 2.0.0-RC3 version of the library.
It seems you're asking about the 1.2.x version? I'm not sure the answer changes much.

You can check the status with ModbusClient::isConnected or ModbusClientTransport::isConnected.
The client will automatically reconnect, with some variation of behavior depending on the values of connectPersistent and reconnectLazy in the NettyClientTransportConfig.

Understood. I have determined online status based on the isConnected() method and set the connectPersistent property to true, and reconnectLazy to false. Setting reconnectLazy to false means it will automatically reconnect if the connection is lost, right? Instead of relying on manual triggering; what is the purpose of the connectPersistent property?

My answer was concerning the current 2.0.0-RC3 version of the library.
It seems you're asking about the 1.2.x version? I'm not sure the answer changes much.
I can probably add a listener/callback to NettyTcpClientTransport in the 2.x version.

it`s 2.0.0-RC3

When connectPersistent is true it means that even if the initial call to connect() fails it will keep retrying automatically. Otherwise if that initial call fails it will just remain disconnected.
reconnectLazy means the reconnect happens the next time the connection is actually needed, instead of happening eagerly/immediately.

When connectPersistent is true it means that even if the initial call to connect() fails it will keep retrying automatically. Otherwise if that initial call fails it will just remain disconnected. Only influences the behavior of the initial call to connect().
reconnectLazy means the reconnect happens the next time the connection is actually needed, instead of happening eagerly/immediately.

okay,thanks

I will soon add a connection listener callback as well: https://github.com/digitalpetri/modbus/pull/78

the issue has been solved


AASX Download not working

With the newest container for the aas-environment on DockerHub the AASX-download is not working properly. The downloaded file can not be opened with the newest AASX package explorer. Also renaming the file from *.aasx to *.zip does not work in that sense that the zipped document cannot be accessed in windows file explorer.

This issue resulted from a bug in the AAS Web UI not fetching the binary AASX content as a blob. This is fixed here: https://github.com/eclipse-basyx/basyx-applications/pull/39
Now AASX files can be renamed to {filename}.zip and examined and also imported back to BaSyx V2 without any errors.
Nonetheless, AASX serialisations from aas4j cannot be opened in the Package Explorer. This is an issue with the Package Explorer, not aas4j or BaSyx.

The AAS Web GUI was updated today, thus the blob issue should be fixed. For the general issues with AASX files with AAS4J and Package Explorer, cf. https://github.com/eclipse-aas4j/aas4j/issues/158


Why the training phase is quite slow with V100 GPU?

I have two V100 GPUs, however, the training phase is extremely slow with only 643 images? I wonder the reason.

I find the reason, I suggest the author to modify the code: nanodet/data/dataset/yolo.py, line 97, img = cv2.imread(img_name).
This function is extremely slow for images with high resolution, I change this into w, h = imagesize.get(img_name).

pip3 install imagesize

However, the code is stuck here:

Hi @ForeverPs,
Are u aware of how to save all the checkpoints of each epochs and what epochs does model.best.ckpt saves? Where to check those?

And also i think in Nanodet training script we can't control. Is that what you have also experienced?


bug(mat-dialog-content): mat-dialog-content style messed up

Is this a regression?

[X] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
14
Description
I am using a custom theme. I upgraded from 14 to 15. all of my dialog which use mat-dialog-conent looks really weird now.

previously, it looked like this:

there are some css added to mat-mdc-dialog-content:

I changed my custom theme to :
`// Custom Theming for Angular Material
// For more information: https://material.angular.io/guide/theming
@use '@angular/material' as mat;
// Plus imports for other components in your app.
// Include the common styles for Angular Material. We include this here so that you only
// have to load a single css file for Angular Material in your app.
// Be sure that you only ever include this mixin once!
@include mat.core();
// Define the palettes for your theme using the Material Design palettes available in palette.scss
// (imported above). For each palette, you can optionally specify a default, lighter, and darker
// hue. Available color palettes: https://material.io/design/color/
$lawyer-primary: mat.define-palette(mat.$indigo-palette, 800);
$lawyer-accent: mat.define-palette(mat.$green-palette, A700);
// The warn palette is optional (defaults to red).
$lawyer-warn: mat.define-palette(mat.$red-palette,A700);
$lawyer-typography: mat.define-typography-config();
@include mat.typography-hierarchy($lawyer-typography);
// Create the theme object. A theme consists of configurations for individual
// theming systems such as "color" or "typography".
$lawyer-theme: mat.define-light-theme((
color: (
primary: $lawyer-primary,
accent: $lawyer-accent,
warn: $lawyer-warn,
),
typography: $lawyer-typography,
/*  density: 0,*/
));
// Include theme styles for core and each component used in your app.
// Alternatively, you can import and @include the theme mixins for each component
// that you are using.
@include mat.all-component-themes($lawyer-theme);
@include mat.all-component-typographies($lawyer-typography);
@include mat.typography-hierarchy($lawyer-theme);`
but, the mat.typography-hierarchy does not help
Reproduction
Steps to reproduce:

use a custom theme
use mat-dialog-content

Expected Behavior
the style is same as before on angular material 14
Actual Behavior
style looks very wierd
Environment

Angular:  15.1.5
CDK/Material: 15.1.5
Browser(s): chrome
Operating System (e.g. Windows, macOS, Ubuntu): windows

Hi, your theme file seems to be set up correctly. If I had to guess, there is probably some custom css in your application trying to style the internals of the mat-dialog which are no longer being applied due to changes in the internal dom structure of the mat-dialog from v14 to v15. If it is possible to avoid depending on our internal dom structure for your custom css, I would recommend doing so to prevent your css from breaking in the future
I'll also mention that it is incorrect to expect that the v14 components look the same as v15 components. There were many changes in the appearance of our components and it is possible that the appearance will change in the future to continue to keep up with the material design specs


onWorldObjectStreamIn/Out undefined object

create a virtual entity group and add a virtual entity on the server, on the client make a onWorldObjectStreamIn/Out event and log the entity, it will be undefined

can't reproduce

@Yiin just so you know, typeof null is also 'object' and you can just pass object to alt/console.log, it will output you constructor name of it

fuck right I forgot

@notmatical please provide reproduction sample - i can't reproduce using the following:
###Server:
import * as alt from "@altv/server";

const virtualEntityGroup = alt.VirtualEntityGroup.create({
  maxEntitiesInStream: 128,
});

for (let i = 0; i < 10; ++i) {
  const VirtualEntity = alt.VirtualEntity.create({
    group: virtualEntityGroup,
    pos: { x: 0, y: 0, z: i * 0.5 },
    streamingDistance: 100,
  });

  VirtualEntity.streamSyncedMeta.customId = i;
}

alt.Events.onPlayerConnect(({ player }) => {
  player.model = "mp_m_freemode_01";
  player.spawn({ x: 0, y: 0, z: 71 });
});

###Client:
import * as alt from "@altv/client";

alt.Events.onWorldObjectStreamIn(({ object }) => {
  if (!(object instanceof alt.VirtualEntity)) return;

  const customId = object?.streamSyncedMeta?.customId;
  alt.log(
    `VirtualEntity with customId ${customId} streamed in - remoteid: ${object.remoteID}`
  );
});

alt.Events.onWorldObjectStreamOut(({ object }) => {
  if (!(object instanceof alt.VirtualEntity)) return;

  const customId = object?.streamSyncedMeta?.customId;
  alt.log(
    `VirtualEntity with customId ${customId} streamed out - remoteId: ${object.remoteID}`
  );
});

Feel free to re-open once reproduction has been provided.


The Big Bad - Part 2: Controlled Props

Controlled Tasks

[x] Overridables for every builder that should/could have them
[x] Change functions to go along with each overridable
[x] Initial documentation for controlled usage with BYOS (Bring Your Own Store) & change functions.
[x] Nested/children popovers - #80  #189
[x] Ensure essential controlled stores work out of the box (open for floating elements, etc.)
[x] Popover forceVisible

@huntabyte small addendum. Sometimes we apply actions (popper, portal, etc) during a specific event, instead of listening to the state of a store. This would probably mean controlled usage would not work very well. We should test if these use cases work with this PR

I was looking at the documentation deployed by this PR to understand the new controlled way...it seems the non main snippets (at least for the checkbox) are not updated to the new syntax, am i wrong?


aktualizr: drop unnecessary do_configure_prepend

fails with latest oe-core/master with:
https://git.openembedded.org/openembedded-core/commit/meta/classes/cmake.bbclass?id=0fb6280432a36985590d9a714a5f11164aaebb51
because this prepend does "cd ${S}" and doesn't go back to ${B} and
cmake_do_configure function doesn't cd to ${B} anymore, resulting in:
| CMake Error at CMakeLists.txt:42 (message):
|   Aktualizr does not support building in the source tree.  Please remove
|   CMakeCache.txt and the CMakeFiles/ directory, then create a subdirectory to
|   build in: mkdir build; cd build; cmake ..

drop this whole do_configure_prepend as git-native works fine:
aktualizr-native/1.0+gitAUTOINC+1255aa24fe-7/git$ grep Setting ../temp/log.do_configure
-- Setting version to 2020.10-0-g1255aa24f
aktualizr/1.0+gitAUTOINC+1255aa24fe-7/temp$ grep Setting ../temp/log.do_configure
-- Setting version to 2020.10-0-g1255aa24f
aktualizr/1.0+gitAUTOINC+1255aa24fe-7/build$ which git
/OE/build/oe-core/tmp-musl/hosttools/git
aktualizr/1.0+gitAUTOINC+1255aa24fe-7/build$ grep GIT CMakeCache.txt
GITCOMMAND:FILEPATH=/OE/build/oe-core/tmp-musl/hosttools/git
GIT_EXECUTABLE:FILEPATH=/OE/build/oe-core/tmp-musl/hosttools/git
//ADVANCED property for variable: GITCOMMAND
GITCOMMAND-ADVANCED:INTERNAL=1
//ADVANCED property for variable: GIT_EXECUTABLE
GIT_EXECUTABLE-ADVANCED:INTERNAL=1

Signed-off-by: Martin Jansa<EMAIL_ADDRESS>

@aodukha this would be great if we could drop this. Can you test and confirm?

The cmake.bbclass changes was backported to hardknott branch today:
https://git.openembedded.org/openembedded-core/commit/?h=hardknott&id=db6a315e5f6de02e226e582f878a83c427fd87cc
so aktualizr-native builds will now fail also with the stable hardknott branch.


When launching Debian 10.4 (Xfce) with console mode, UTM crashed

UTM 2.0.19
IOS 14.3
https://mac.getutm.app/gallery/debian-10-4-xfce

The macOS UTM Virtual machines gallery is for mac, and the VMs are configured for it to work with the macOS version of UTM only.

The macOS UTM Virtual machines gallery is for mac, and the VMs are configured for it to work with the macOS version of UTM only.

That’s literally not true.

That’s literally not true.

@osy Yes, same issue. Also when I enable the directory sharing of Debian 10.4 (Minimal) and turn it on, UTM crashed. Both 2.0.19 and 2.0.18

@osy Yes, same issue. Also when I enable the directory sharing of Debian 10.4 (Minimal) and turn it on, UTM crashed. Both 2.0.19 and 2.0.18

Can you post a crash log? If you don’t know how refer to the issue template you deleted when you created the issue.

Can you post a crash log? If you don’t know how refer to the issue template you deleted when you created the issue.

@osy It doesn't make a crash log, the latest one is three days ago
UTM.wakeups_resource-2021-01-28-142152.ips.synced.txt

@osy It doesn't make a crash log, the latest one is three days ago
UTM.wakeups_resource-2021-01-28-142152.ips.synced.txt

@osy I found that my utm.ipa is resigned by @js-john , so today I tried the github-released utm.ipa (both 2.0.19 and 18), it also crashed.  (js-john fixed an issue on cpu multicore and names it 2.0.20)

@osy I found that my utm.ipa is resigned by @js-john , so today I tried the github-released utm.ipa (both 2.0.19 and 18), it also crashed.  (js-john fixed an issue on cpu multicore and names it 2.0.20)

@osy And here's the debug log of the two issues. (Under 2.0.18)
debug_xfce_command_mode.log
debug_minimal_directory_sharing.log

@osy And here's the debug log of the two issues. (Under 2.0.18)
debug_xfce_command_mode.log
debug_minimal_directory_sharing.log

@osy I found that my utm.ipa is resigned by @js-john , so today I tried the github-released utm.ipa (both 2.0.19 and 18), it also crashed. (js-john fixed an issue on cpu multicore and names it 2.0.20)

I just pulled the latest code for and archived an ipa. I didn't fixed that bug, osy did.

@osy I found that my utm.ipa is resigned by @js-john , so today I tried the github-released utm.ipa (both 2.0.19 and 18), it also crashed. (js-john fixed an issue on cpu multicore and names it 2.0.20)

I just pulled the latest code for and archived an ipa. I didn't fixed that bug, osy did.


Auto minify SCPs

Is your feature request related to a problem? Please describe.
SCPs that are valid from the AWS console cannot be applied via the API.  This seems to be because the AWS console automatically minifies the JSON policy whereas the API applies it as-is.   SCPs are limited to 5120 bytes, but you can apply much larger SCPs from the console due to the automatic minification.
Describe the feature you'd like
I would be very helpful if this framework could automatically minify the SCPs before applying them.  That way we can maintain the pretty SCPs in our customization project.
Additional context
It is difficult to maintain and review changes to minified JSON documents in git.  I have many SCPs that push the limits of SCP size due to the limitations of SCP policies.
In IAM policies you can use multiple wildcards in an action statement, but in SCP policies it only supports one wildcard.  So I often have to expand 1 action pattern into many to achieve the same goal.  For example:

iam:*User* works in IAM policies but not in SCP which leads to a much longer policy in SCP.

@rjenks Thanks for bringing this to our attention. We have added this to our backlog.

Is there any update on this? Is there a public roadmap of accepted enhancements we can see? The repository isn't accepting contributions at the moment, so I believe we are fully reliant on the AWS team to make these enhancements?


Handle Translation of the  tag

Currently we can't really translate the <title> tag because our block doesn't allow a template to add a l20n ID to it.

Gonna drop this out of the Become PyPI, since we're not going to have any translations for launch we can figure this out later.


Support for M1

Added Support for M1 Macs
Compiler flag '-march=native'  and the maximal allowed version 1.5.11 of pyglet have prevented nes-py from being installed on M1 Macs.
Type of change
Please select all relevant options:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Local installation on M1 Mac
[x] Local installation on Intel based Mac

Test Configuration

Operating System: macOS 12.0.1 (M1), macOS 11.6 (Intel)
Python version: 3.8 & 3.9
C++ compiler version: C++17

I've also tested the change and it worked correctly.

Sorry for the delay, thanks for the contribution!


viewing Pandas Sparse matrix from variable explorer will crash

Issue Report Checklist

[ ] Searched the issues page for similar reports
[ ] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[ ] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[ ] Tried basic troubleshooting (if a bug/error)

[ ] Restarted Spyder
[ ] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[ ] Tried the other applicable steps from the Troubleshooting Guide

[ ] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
What steps reproduce the problem?

What is the expected output? What do you see instead?
Paste Traceback/Error Below (if applicable)

PASTE TRACEBACK HERE

Versions

Spyder version:
Python version:
Qt version:
PyQt version:
Operating System name/version:

Dependencies

PASTE DEPENDENCIES HERE

You don't mention an specific problem, but most probably this is fixed in our latest version. Please update by opening the Anaconda Prompt and running there
conda update spyder


Update Python versions

Python 3.6 was released on 2016-12-23, so add it.
Python 2.6 reached EOL on 2013-10-29, and no longer receives security updates.

https://en.wikipedia.org/wiki/CPython#Version_history
Also, whilst we're here, update some HTTP links to HTTPS.

Hello Hugo,
Thanks for the changes!
I would like to keep Python 2.6 enabled in the travis.yml since I do not for see any changes to this code base and if it works on Python 2.6 why not continue testing it as well.
More importantly, there is no overhead in maintaining the test: its all automatic anyway!
So could you get 2.6 back in travis.yml? I will then merge the changes in.
Regards,
Prasanth

Done!

Thanks Hugo!


Incorrect namespace for PackageGuidString

The line [Guid(FirstPackageGuids.PackageGuidString)] is incorrect. It should read [Guid(FirstPackage.PackageGuidString)] - Mitch

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

ID: f7aca15b-bfa6-33ac-8f45-78d5d6c4ffc0
Version Independent ID: c3dc31a4-cf7a-4b25-8e39-91cb19565203
Content
Content Source
Service: unspecified

Thanks for calling this out! Will be fixed shortly.


Defining a route (NuxtPage) does not permit component property though documentation uses it

Environment

Operating System: Linux
Node Version:     v18.15.0
Nuxt Version:     3.3.1
Nitro Version:    2.3.1
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      modules, quasar, vite, runtimeConfig, typescript, hooks
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
Occurrence in documentation: https://nuxt.com/docs/guide/going-further/custom-routing#using-the-pagesextend-hook
Corresponding type definition: https://github.com/nuxt/nuxt/blob/main/packages/schema/src/types/hooks.ts#L22-L30
Describe the bug
The documentation adds a route using a component. While this should work for directly adding it to the router (RouteRecordRaw[]), it does not work for adding routes within the pages:extend hook and in my testing lead to errors.
Additional context
No response
Logs
No response

Thanks for spotting! Updated the documentation.


The number following

Hi,  I am using your ‘jubmlr’ api to develop an app.  When I use the method (‘userFollowing’) to get the blogs what I am following, the number of the blogs isn't equal to my account’following. My account’s following is 228, but the number I got from the ‘jubmlr’ is 20. So is there any limitation to the api?

To get the amount of blog use
user.getFollowingCount();
It works for me properly (I have more than 20 blogs following)

@iwuvhugs Thank You. Your answer solved my problem.


Auto import not working

Type: Bug
for example, after typing Path and  Trigger Suggest(ctrl + space), there is no import pathlib suggestion but  only __path__ . using python 3.11.0, pre-release python  and pylance.
Extension version: 2022.10.41
VS Code version: Code 1.72.2 (d045a5eda657f4d7b676dedbfa7aab8207f8a075, 2022-10-12T22:16:26.920Z)
OS version: Linux x64 5.15.0-52-generic
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
AMD Ryzen 7 4700U with Radeon Graphics (8 x 2000)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
1, 1, 0

Memory (System)
30.72GB (20.23GB free)

Process Argv
--unity-launch --crash-reporter-id b0fe70dc-73b5-44f5-a8cc-3807703c7d9c

Screen Reader
no

VM
0%

DESKTOP_SESSION
plasma

XDG_CURRENT_DESKTOP
KDE

XDG_SESSION_DESKTOP
KDE

XDG_SESSION_TYPE
x11

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
pyindex848:30577860
nodejswelcome1:30587005
fc301958:30595537
2e4cg342:30596373

Auto-import is turned off by default starting in 2022.10.41. Set "python.analysis.autoImportCompletions": true to enable it.

well that's weird but alright.

Auto-import is turned off by default starting in 2022.10.41. Set "python.analysis.autoImportCompletions": true to enable it.

thats a descision which makes sense from a "want it to be correct" POV, but has absolutely awful UX. Most users would expect auto imports to just work when installing the python extension - and likely not consider they're a off-by-default setting.
I know that it took me a surprising amount of googling to even find the change and issue - since the extension auto updated in the background and suddenly my auto imports were gone.


ros2 topic echo /lowcmd NOT WORKING

unitree@unitree-h1-pc2:~$ ros2 topic echo /lowcmd
Traceback (most recent call last):
File "/opt/ros/foxy/bin/ros2", line 11, in
load_entry_point('ros2cli==0.9.13', 'console_scripts', 'ros2')()
File "/opt/ros/foxy/lib/python3.8/site-packages/ros2cli/cli.py", line 67, in main
rc = extension.main(parser=parser, args=args)
File "/opt/ros/foxy/lib/python3.8/site-packages/ros2topic/command/topic.py", line 41, in main
return extension.main(args=args)
File "/opt/ros/foxy/lib/python3.8/site-packages/ros2topic/verb/echo.py", line 71, in main
return main(args)
File "/opt/ros/foxy/lib/python3.8/site-packages/ros2topic/verb/echo.py", line 86, in main
message_type = get_msg_class(node, args.topic_name, include_hidden_topics=True)
File "/opt/ros/foxy/lib/python3.8/site-packages/ros2topic/api/init.py", line 99, in get_msg_class
msg_class = _get_msg_class(node, topic, include_hidden_topics)
File "/opt/ros/foxy/lib/python3.8/site-packages/ros2topic/api/init.py", line 144, in _get_msg_class
return get_message(message_type)
File "/opt/ros/foxy/lib/python3.8/site-packages/rosidl_runtime_py/utilities.py", line 28, in get_message
interface = import_message_from_namespaced_type(get_message_namespaced_type(identifier))
File "/opt/ros/foxy/lib/python3.8/site-packages/rosidl_runtime_py/import_message.py", line 30, in import_message_from_namespaced_type
module = importlib.import_module(
File "/usr/lib/python3.8/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1014, in _gcd_import
File "", line 991, in _find_and_load
File "", line 961, in _find_and_load_unlocked
File "", line 219, in _call_with_frames_removed
File "", line 1014, in _gcd_import
File "", line 991, in _find_and_load
File "", line 973, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'unitree_hg'
unitree@unitree-h1-pc2:~$

I have the same problem. Have you solved it?


Misalignment with parsing of Lookup Records

When parsing testdata/Roboto-BoldItalic.ttf, parsing of GSUB->Lookups gets misaligned.
Output of testing the current code:
--- FAIL: TestGSubLookupRecords (0.00s)
parse_test.go:34: [0] lookup record of type GSUB_Single
parse_test.go:34: [1] lookup record of type GSUB_Single
parse_test.go:34: [2] lookup record of type GSUB_ChainingContext
parse_test.go:34: [3] lookup record of type GSUB_Single
parse_test.go:34: [4] lookup record of type GSUB_Single
parse_test.go:34: [5] lookup record of type GSUB_Ligature
parse_test.go:34: [6] lookup record of type GSUB_Single
parse_test.go:34: [7] lookup record of type GSUB_Single
parse_test.go:34: [8] lookup record of type GSUB_Single
parse_test.go:34: [9] lookup record of type GSUB_Single
parse_test.go:34: [10] lookup record of type GSUB_ChainingContext
parse_test.go:34: [11] lookup record of type 8960
parse_test.go:34: [12] lookup record of type 2750
parse_test.go:34: [17] lookup record of type 2305
[…]
parse_test.go:34: [31] lookup record of type 2343
parse_test.go:34: [32] lookup record of type 10505
parse_test.go:34: [33] lookup record of type 2349
parse_test.go:34: [34] lookup record of type 12041
It finds 35 lookup records, which is correct, but really only just by chance (I think in total it re-aligns with sub-tables somehow, but nevertheless is off). GSUB lookup types like 2315 aren't valid.
The expected output should be:
parse_test.go:34: [0] lookup record of type GSUB_Single
parse_test.go:34: [1] lookup record of type GSUB_Single
parse_test.go:34: [2] lookup record of type GSUB_Single
parse_test.go:34: [3] lookup record of type GSUB_Ligature
parse_test.go:34: [4] lookup record of type GSUB_ChainingContext
parse_test.go:34: [5] lookup record of type GSUB_Single
parse_test.go:34: [6] lookup record of type GSUB_Ligature
parse_test.go:34: [7] lookup record of type GSUB_Ligature
parse_test.go:34: [8] lookup record of type GSUB_ChainingContext
parse_test.go:34: [9] lookup record of type GSUB_Single
parse_test.go:34: [10] lookup record of type GSUB_Single
parse_test.go:34: [11] lookup record of type GSUB_Single
parse_test.go:34: [12] lookup record of type GSUB_Ligature
parse_test.go:34: [13] lookup record of type GSUB_Single
parse_test.go:34: [14] lookup record of type GSUB_Single
parse_test.go:34: [15] lookup record of type GSUB_Single
parse_test.go:34: [16] lookup record of type GSUB_Ligature
parse_test.go:34: [17] lookup record of type GSUB_Ligature
parse_test.go:34: [18] lookup record of type GSUB_Ligature
parse_test.go:34: [19] lookup record of type GSUB_Single
parse_test.go:34: [20] lookup record of type GSUB_Single
parse_test.go:34: [21] lookup record of type GSUB_Single
parse_test.go:34: [22] lookup record of type GSUB_Single
parse_test.go:34: [23] lookup record of type GSUB_Single
parse_test.go:34: [24] lookup record of type GSUB_Single
parse_test.go:34: [25] lookup record of type GSUB_Single
parse_test.go:34: [26] lookup record of type GSUB_Single
parse_test.go:34: [27] lookup record of type GSUB_Single
parse_test.go:34: [28] lookup record of type GSUB_Single
parse_test.go:34: [29] lookup record of type GSUB_Single
parse_test.go:34: [30] lookup record of type GSUB_Single
parse_test.go:34: [31] lookup record of type GSUB_Single
parse_test.go:34: [32] lookup record of type GSUB_ChainingContext
parse_test.go:34: [33] lookup record of type GSUB_Single
parse_test.go:34: [34] lookup record of type GSUB_Single

I'll provide a fix, if this package is still maintained.

The Travis CI build obviously failes due to an illegal call to go vet in the pipeline (go tool vet instead of go vet).

This was fixed.
@npillmayer I've made you a collaborator on this repo, thank you for the high quality change! Feel free to push more fixes that you need (it's best if you use the PR mechanism, but if you don't hear back in a reasonable time, I trust your judgement).


ROX-16430: Add option in os-4 flavor to keep failed clusters

Requires https://github.com/stackrox/automation-flavors/pull/184.
Testing
Forcing the failure mode via https://github.com/stackrox/automation-flavors/pull/184/commits/10747416e14221e171dfc50fdaa8e60943397c2a:
❯ infractl -k -e localhost:8443 create openshift-4 bl-os4-keep --arg "keep-failed-cluster=true"
NOTE: infractl no longer requires a NAME parameter when creating a cluster.
      If ommitted a name will be generated using your infra user initials, a
      short date and a counter for uniqueness. e.g. jb-10-31-1
ID: bl-os4-keep
❯ infractl -k -e localhost:8443 create openshift-4 bl-os4-no-keep
NOTE: infractl no longer requires a NAME parameter when creating a cluster.
      If ommitted a name will be generated using your infra user initials, a
      short date and a counter for uniqueness. e.g. jb-10-31-1
ID: bl-os4-no-keep

# Some time passes...

❯ infractl -k -e localhost:8443 list
bl-os4-keep
  Flavor:      openshift-4
  Owner<EMAIL_ADDRESS>  Description:
  Status:      READY
  Created:     40m ago
  Lifespan:    2h19m remaining
bl-os4-no-keep
  Flavor:      openshift-4
  Owner<EMAIL_ADDRESS>  Description:
  Status:      FAILED
  Created:     41m ago
  Destroyed:   2m39s ago
  Lifespan:    2h18m remaining

# Some time passes...

One future improvement would be to indicate in the infra status of the cluster whether the cluster failed, but we're keeping it around. Right now, if we use the --arg "keep-failed-cluster=true", the cluster will almost certainly be marked as READY even though it's an unhealthy cluster (or perhaps no cluster exists at all).

Note to self: if we decide to go with the current implementation in the PR, it's probably worth adding the parameter to the openshift-4-demo flavor as well (likely wouldn't require any stackrox/automation-flavor changes, just an update to the workflow config)


ARROW-13110: [C++] Deadlock can happen when using BackgroundGenerator without transferring callbacks

@lidavidm Do you see any harm that could be caused by this transfer?

Related: ARROW-13109 should allow the producer to place restrictions on callbacks.

You mean the one in OneShotFragment? I think that's fine.
Should we add the thread pool as a parameter to MakeBackgroundGenerator? So that you can't forget. (I guess that'd create some churn once we have ARROW-13109 since it would become redundant again.)
This looks like it was a fun issue to debug…


Increment version for ai releases

Increment package version after release of Azure.AI.Projects

API change check
API changes are not detected in this pull request.


[move-only] Prepare for handling ref_element_addr/global_addr/escaping closure captured params

Specifically, I am going to be adding a new form of semantics where one is allowed to read from an address, assign into an address, but not consume an address. This works for ref_element_addr, global_addr, and no_escaping_closure.
Just slicing off parts of a larger patch.
This is part of rdar://102794400, rdar://104874497, and rdar://105294941

@swift-ci smoke test


In Android not able to get all devices, whereas in iOS its working perfectly fine.🐛

What were you trying to do?
I am trying to access ultra wide angle camera using getAvailableCameraDevices.
Reproduceable Code
No response
What happened instead?
I am only getting 2 cameras i.e. back and front in android, whereas in iOS its working fine.
Relevant log output
No response
Device
android all devices
VisionCamera Version
2.15.4
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

Hey! I've rewritten the entire Android codebase of VisionCamera from CameraX to Camera2 in the efforts of ✨ VisionCamera V3.
I just now completed the Camera2 rewrite and I believe the core structure is running, but there might be some edge cases to iron out. Can you try and test the PR #1674 for me to see if you can still reproduce this issue here?
Here's an instruction on how you can test that: https://github.com/mrousavy/react-native-vision-camera/pull/1674#issuecomment-1684104217
If the issue cannot be reproduced with that version/PR anymore, then hoorayy, I fixed it! 🎉
Otherwise please let me know and I'll keep this issue open to keep track of it.
Thank you!


Get this working everywhere

The goal of this crate is to have a quick-and-dirty way to throw pixels into a buffer and display them on a window without a significant number of dependencies. Potentially, we'll be able to use this in the Winit examples to clear the screen quickly and get windows showing up with Wayland, but that would require that this work on all the platforms Winit supports.
@vbogaevsky @murarth @vberger @ryanisaacg @mtak- @goddessfreya - would any of you be able to throw together an implementation for the platform you've worked on in Winit? It's totally fine if you're unable or uninterested in working on this, and I have no desire to thrust work onto any of you that you don't want to do. However, you're the people I know I can ping, which seems like a good place to start for getting movement on this crate.
Anyhow, assorted implementation details:

I have no idea if the current public API will work on all platforms. There's a good chance it won't, but figuring that out will be part of the design process.
This crate doesn't depend on Winit directly - instead, it depends on raw-window-handle. That works fine on Windows, but there may be some friction on other platforms - particularly X11, which uses a #[doc(hidden)] API to load up Winit's X11 bindings. We should be able to resolve that problem by moving the X11-bindings-loading code into a separate crate that creates a lazy_static bindings object, which both Winit and winit-blit can depend upon.

That X11 work will be necessary for decoupling Glutin from Winit, which we should do in the long term. Getting this crate working should help lay the groundwork for figuring out how to do that.

Ideally, this shouldn't be too complex to implement for the various platforms - the Windows implementation is about 250 lines, and the majority of that code is API boilerplate that can be copied to other platforms.

Let me know if there are any questions. Thanks!

Just looking at the API as it is, I anticipate a few complications wrt Wayland. The raw window handle as we manipulate it for wayland currently (as a (*mut wl_display, *mut wl_surface)) si not something that can be used "as-is", but requires some initialization work before being usable (binding the registry & retrieving the globals), implying a few round-trips with the compositor.
This is not an issue with glutin, which does this initialization work once at startup and then keeps the initialized state around to use it. Here however, the API as it is implies re-doing this initialization work every time a blit is made. Performance would be terrible & it'd cause object leak at the protocol level.
If this crate is only intended for quick, single-shot blit, that's fine to keep it like this, but it should be clearly expressed that it should not be used for regular cpu drawing.
If it should be usable for regular cpu drawing, then for it to play necely with wayland the API needs to be updated by creating some "initialized window handle" that is created from a H: HasRawWindowHandle, and then this initialized handle would be used for blitting pixel. This would make it possible to keep the initialized state around, and implement some double-buffering to avoid graphical glitches.

I should be able to get this running on web without too much pain, but it might be a bit of time before I'm available to.

Should be reasonably simple to implement for wayland too.
It only raises the question of double buffering. Generally wayland clients are expected to do it to avoid having the client modify the buffer while the server is still reading it (which could cause graphical glitches).
Not sure when I'll have the time to do it, but I'd be happy to mentor anyone willing to try it.

@vberger good to hear! The current API implementation is already double-buffered, so implementing that on Wayland shouldn't be too much of a problem.

A note that I forgot to mention in the main post: at some point I'd like to pull Winit's Size and Position types out into a separate crate so this crate and Winit master can use the same types, without this crate directly depending on Winit. We should aim to do that once the dpi overhaul has landed on master.

I imagine most people will have already noticed this, but, I just wanted to mention I'm currently working on decoupling glutin from winit via three new crates (that are still heavily WIP and unpublished): winit_types, glutin_interface and glutin_x11_sym.
The purpose of glutin_x11_sym is to provide a single crate that downstream crates can all depend on for their X11 symbol loading. We also provide a single X11 display for downstream crates to all share, and some error handling code ripped out of winit.
winit_types simply rips out winit's error handling and dpi module and places them in a separate crate that both glutin and winit can depend on. This has the wonderful consequence of unifying glutin and winit's error types. I should note that while modifying winit's codebase to utilize this crate, I got confused by the ~4 different error types in use by the X11 backend, so I took it on me to cleanup the backend to just use Error everywhere.
glutin_interface serves a similar purpose to raw-window-handle, acting as an interoperability library for crates that wish to be compatible with glutin. Unfortunately, as it currently stands, raw-window-handle does not expose enough things to be usable by glutin. To enumerate all the reasons off the top of my head:

It does not expose the components necessary for making an EGL/GLX display.
Similarly, for WGL it does not expose a dummy HWND for finding the target pixel format with.
It doesn't expose an interface for pixmaps.
It does not expose an interface for allowing glutin to pass certain parameters to the window builders before the windows are built. More precisely, on X11 glutin needs to decide the XVisual and screen.
Similarly, on iOS glutin needs to decide, for some reason, the window's "root view class" (I'm not familiar with UIKit so don't ask me what this means) before the window is built.
It doesn't expose the size and hidpi factor of the windows, the later needed by glutin for its iOS backend while the former for its Wayland backend.

With that said, I'd like to hear everybody's feedback on the work done so far.
I'd also like to hear if @Drakulix is interested in implementing glutin_interface on gbm.rs, or if I should go ahead with the task myself. Doing so would allow glutin's EGL backend to be used with their crate.

Window properties that you want are up to you as a consumer of a raw window handle to find out on your own via the appropriate OS calls.
As to window creation, I doubt there's a way to make that unified in a good way.

Window properties that you want are up to you as a consumer of a raw window handle to find out on your own via the appropriate OS calls.

On Wayland, as far as I and @Osspial could tell (as we were talking on discord), there appears no way to acquire the size that winit sets the window to via OS calls. Maybe @vberger is familiar way to do so? That would also allow us to automate calls to wegl::WlEglSurface::resize.

I'd also like to hear if @Drakulix is interested in implementing glutin_interface on gbm.rs, or if I should go ahead with the task myself. Doing so would allow glutin's EGL backend to be used with their crate.

I feel similar disappointment with raw-window-handle, as it is not really helping smithay's gbm use-case. (Although one could argue, that the gbm-interface is not really like any other window, but still...)
I would be glad to support viable alternatives in gbm.rs. I am currently a little busy, but I could likely work out support some time before the end of the year. If you could provide me with some hints, what needs to be done, that would be really helpful.

On Wayland, as far as I and @Osspial could tell (as we were talking on discord), there appears no way to acquire the size that winit sets the window to via OS calls. Maybe @vberger is familiar way to do so? That would also allow us to automate calls to wegl::WlEglSurface::resize.

Now that you mention it, it is indeed not possible to retrieve this information for only the two pointers *mut wl_display and *mut wl_surface. This is basically why WlEglSurface::resize exists: the OpenGL stack cannot retrieve the size from these pointers, as the size of the surface is defined by what is drawn on it. So it needs to know what size the application wants.

Similarly, for WGL it does not expose a dummy HWND for finding the target pixel format with.

Why is it necessary for raw-window-handle to expose that? It should be easy enough for Glutin to create its own dummy window for that purpose - it's already calling Windows API functions, so creating and destroying a temporary window doesn't seem like too much of a stretch. On a similar note, I don't think it's unreasonable to ask Glutin to call the native iOS size/DPI retrieval methods, although that still leaves the Wayland situation unresolved.
@vberger On Wayland, is it possible to attach functions to a surface after the surface's creation that intercepts events dispatched by the compositor (along the lines of the win32 subclassing API)? If that existed, we could have Glutin hook into Wayland's event queue to read the resize events directly, which would alleviate the context resizing problem.

Why is it necessary for raw-window-handle to expose that? It should be easy enough for Glutin to create its own dummy window for that purpose - it's already calling Windows API functions, so creating and destroying a temporary window doesn't seem like too much of a stretch.

Fair enough.

On a similar note, I don't think it's unreasonable to ask Glutin to call the native iOS size/DPI retrieval methods, although that still leaves the Wayland situation unresolved.

Honestly, I didn't look into this one too much. My reasoning being that if Wayland's going to require size, then we might as well have all the platforms provide it.

@vberger On Wayland, is it possible to attach functions to a surface after the surface's creation that intercepts events dispatched by the compositor (along the lines of the win32 subclassing API)? If that existed, we could have Glutin hook into Wayland's event queue to read the resize events directly, which would alleviate the context resizing problem.

Well, no, this is really not how Wayland is structured. How it works is that the server sends events suggesting a size, but these events do not go through the wl_surface, winit collects them through an other object (the wayland protocol splits things between a lot of objects). And in the end, it is winit that decides the new size of the window, and should forward this information to the part of the program in charge of drawing the contents.

softbuffer exists now and supports pretty much every platform. It's awesome.


Not support for TEL;TYPE=WhatsApp:

I use Xiamoi mi 8, Android 10.
Export from my mobile all contacts to vcf file.
Some contacts has TEL;TYPE=WhatsApp:
BEGIN:VCARD
VERSION:3.0
N:;zzMad Perla 45;;;
FN:zzMad Perla 45
TEL;TYPE=HOME:7yy-zzz-xxx
TEL;TYPE=WhatsApp:7yy-zzz-xxx
URL:https://www.xxxxxx
NOTE;CHARSET=UTF-8:PERLA\nmadrid
END:VCARD

More real samples in  http://unc.esy.es/jw/00001.vcf
TEL;TYPE=WhatsApp:

Hello Kiquenet,
thank you very much for posting this issue. I need some time to investigate and reproduce your issue and then I will answer detailed. Your posted example is very helpful, but please think of the data protection of your friends and remove their vCards (http://unc.esy.es/jw/00001.vcf) from the web.
Thank you very much.
Folker

Thanks a lot.
NOt my friends :-) Google search returns :'(

Hi Kiquenet,
unfortunately, during my research on the Internet, I could not find any RFC that defines
a WhatsApp-TYPE in a vCard file. Therefore there wasn't an easy fix for your issue like
a new enum value TelTypes.WhatsApp.
Although the WhatsApp-TYPE is a "Non-Standard-Thing", you have found a real issue, because the
library supports such "Non-Standard-Things",e.g., with the ParameterSection.NonStandardParameters
property. Up to version 2.0.0 of the library, there was a bug, that Non-Standard-Values of
standard parameters (like TYPE) were not recognized by the library.
Thanks to your post, the issue could be fixed now. I have published a
preview version (2.0.2-alpha) of the package on nuget, so you don't have to wait for the
next regular release to test it. (It's a preview, because the bug fix required some changes
at the heart of the library, which should be tested more thoroughly.)
Before showing you how the WhatsApp-TYPE can be handled with the preview version, I
would like to demonstrate, how a WhatsApp telephone number is embedded in a vCard using
the Standard-Way:
using System;
using FolkerKinzel.VCards;

using VC = FolkerKinzel.VCards.Models;

namespace Examples
{
    internal static class WhatsAppDemo1
    {
        public static void IntegrateWhatsAppNumberUsingIMPP()
        {
            const string mobilePhoneNumber = "tel:+1-234-567-89";

            // The IMPP-Extension (Instant Messaging [IM] and Presence Protocol [PP] applications)
            // is available in vCard 3.0 through RFC 4770:
            var whatsAppImpp = new VC::TextProperty(mobilePhoneNumber);
            whatsAppImpp.Parameters.InstantMessengerType = VC::Enums.ImppTypes.Personal
                                                         | VC::Enums.ImppTypes.Business
                                                         | VC::Enums.ImppTypes.Mobile;

            // The vCard 4.0 standard RFC 6350 recommends to add an additional TEL entry
            // if the instant messenging device supports voice and/or video.
            // I think, that's a good practice also in vCard 3.0.
            var xiamoiMobilePhone = new VC::TextProperty(mobilePhoneNumber.Substring(4));
            xiamoiMobilePhone.Parameters.PropertyClass = VC::Enums.PropertyClassTypes.Home
                                                       | VC::Enums.PropertyClassTypes.Work;
            xiamoiMobilePhone.Parameters.TelephoneType = VC::Enums.TelTypes.Voice
                                                       | VC::Enums.TelTypes.BBS
                                                       | VC::Enums.TelTypes.Cell
                                                       | VC::Enums.TelTypes.Msg
                                                       | VC::Enums.TelTypes.Text
                                                       | VC::Enums.TelTypes.Video;

            // Initialize the VCard:
            var vcard = new VCard
            {
                NameViews = new VC::NameProperty[]
                {
                    new VC::NameProperty(lastName: null, firstName: "zzMad Perla 45")
                },

                DisplayNames = new VC::TextProperty[]
                {
                    new VC::TextProperty("zzMad Perla 45")
                },

                // Add the WhatsApp-Handle:
                InstantMessengerHandles = new VC::TextProperty[]
                {
                    whatsAppImpp
                },

                // Add the mobile phone too:
                PhoneNumbers = new VC::TextProperty[]
                {
                    xiamoiMobilePhone
                }
            };

            Console.WriteLine(vcard.ToVcfString());
        }
    }
}
/*
Console Output:

BEGIN:VCARD
VERSION:3.0
FN:zzMad Perla 45
N:;zzMad Perla 45;;;
TEL;TYPE=HOME,WORK,VOICE,MSG,CELL,BBS,VIDEO:+1-234-567-89
IMPP;TYPE=BUSINESS,MOBILE,PERSONAL:tel:+1-234-567-89
END:VCARD
*/

The following example shows how to deal with the WhatsApp-TYPE. (Make shure to use at least Version 2.0.2-alpha
of the FolkerKinzel.VCards nuget package.):
using System;
using System.Collections.Generic;
using System.Linq;
using FolkerKinzel.VCards;

using VC = FolkerKinzel.VCards.Models;

namespace Examples
{
    internal static class WhatsAppDemo2
    {
        public static void UsingTheWhatsAppType()
        {
            var xiamoiMobilePhone = new VC::TextProperty("+1-234-567-89");
            xiamoiMobilePhone.Parameters.NonStandardParameters = new KeyValuePair<string, string>[]
            {
                new KeyValuePair<string, string>("TYPE", "WhatsApp")
            };

            // Initialize the VCard:
            var vcard = new VCard
            {
                NameViews = new VC::NameProperty[]
                {
                    new VC::NameProperty(lastName: null, firstName: "zzMad Perla 45")
                },

                DisplayNames = new VC::TextProperty[]
                {
                    new VC::TextProperty("zzMad Perla 45")
                },

                PhoneNumbers = new VC::TextProperty[]
                {
                    xiamoiMobilePhone
                }
            };

            // Don't forget to set VcfOptions.WriteNonStandardParameters when serializing the
            // VCard: The default ignores NonStandardParameters (and NonStandardProperties):
            string vcfString = vcard.ToVcfString(options: VcfOptions.Default | VcfOptions.WriteNonStandardParameters);

            Console.WriteLine(vcfString);

            // Parse the VCF string:
            vcard = VCard.Parse(vcfString)[0];

            // Find the WhatsApp number:
            string? whatsAppNumber = vcard.PhoneNumbers?
                .FirstOrDefault(x => x?.Parameters.NonStandardParameters?.Any(x => x.Key == "TYPE" && x.Value == "WhatsApp") ?? false)?
                .Value;

            Console.Write("The WhatsApp number is: ");
            Console.WriteLine(whatsAppNumber ?? "Don't know.");
        }
    }
}
/*
Console Output:

BEGIN:VCARD
VERSION:3.0
FN:zzMad Perla 45
N:;zzMad Perla 45;;;
TEL;TYPE=WhatsApp:+1-234-567-89
END:VCARD

The WhatsApp number is: +1-234-567-89
*/

If you agree, I would close the issue now.
Best regards
Folker

0908416071


Customer feedback | az stack sub validate | missing information | validate what, how, why?

Describe the bug
This GitHub issue is in response to MicrosoftDocs/azure-docs-cli customer feedback 4639.
Engineering request
Please add more information to the reference command description. What does this command validate? Why does a customer want to do this? Use the long-summary property if needed.
There is one conceptual article that uses the commands in this subgroup, Deployment stacks, but it doesn't address validation.
Customer feedback
Link:
https://learn.microsoft.com/en-us/cli/azure/stack/sub?view=azure-cli-latest#az-stack-sub-validate
Verbatim:
Here it says "Validate a deployment stack at subscription scope.", which sounds nice, but what are you validating? I don't understand what this command is doing at all.
If I change something in my bicep file or parameter file it just says "looks cool 👍" with a list of "validatedResources" (including resources that don't exist yet or that I modified)
I had hoped it would give me a list of what would change (but sadly, this doesn't seem to exist at all for deployment stacks?)...
Page URL
https://learn.microsoft.com/en-us/cli/azure/stack/sub?view=azure-cli-latest
Content source URL
https://github.com/MicrosoftDocs/azure-docs-cli/blob/main/latest/docs-ref-autogen/stack/sub.yml
Related command
az stack sub validate
Errors
n/a
Issue script & Debug output
n/a
Expected behavior
n/a
Environment Summary
Azure CLI 2.64.0
Additional context
No response

Thank you for opening this issue, we will look into it.

@yonzhan , Can you please assign this GitHub issue to the service team?

@sijuman, @sarathys, @bganapa, @rakku-ms, can you please comment on this customer feedback?


Support for 'IDEOGRAPHIC SPACE' (U+3000) in test data on IronPython

While using IronPython to execute robot framework, ideographic space (U+3000) in test data will be replaced by white space (U+0020).
( robot.parsing.datarow.DataRow._collapse_whitespace ).
BTW, ideographic space won't be replaced in CPython.
Example:
${v1} | Set Variable | 1 2
${v2} | Set Variable | 1　2
Should Be Equal | ${v1} | ${v2}
This case will:
PASS in IronPython
FAIL in CPython

Yeah, it seems that re.match(r'\s', u'\u3000') doesn't match with Python but matches with IronPython. That is a bug in IronPython and should be reported to its tracker. I don't think it makes sense for us to try adding a workaround.
Instead I could consider changing the behavior so that also ideographic space is always considered a normal space, similarly as non-breaking space is (#1264). That would make space handling more consistent, but would also potentially cause backwards incompatibility problems. I don't want to do that anymore in RF 2.9, but could be considered in RF 3.0 later this year.
A good workaround for the problem you encountered is using escape sequences, e.g. \u3000 in Robot data. Alternatively you could create more complicated variables in variable files.

Thanks! Seems using escape sequences is the best solution for now.

There's a good workaround for the problem. Changing the behavior when not using IronPython is probably not a good idea. Closing.


Reorganise functions in core.py

Group the functions better, mainly have the functions to set emission probabilities for the haploid case together and those for the diploid case together.

Also, do the following:

Set dtype to np.int8 when assigning haplotype/genotype values or number of distinct alleles.
Remove get_index_in_emission_matrix_diploid_genotypes.


Migrate styling from Bootstrap to MUI v5

#11 resolved. Replaced Bootstrap components with temporary equivalent MUI components. Removed Bootstrap completely including all related packages and imports. Also removed Nav.module.css file as no longer required.

Thanks @paulcretu for your comments. What I was thinking when working on this issue was to just remove bootstrap components with temp components which will ultimately be removed by the components according to the designs. So should I work on suggestions like creating a new reusable card component and creating a card for the missed one which I think is an unnecessary work ?

@DivyanshuParwal yeah that's a good point. I actually didn't mean to request changes for all the suggestions, just for removing @types/node. My mistake, I should have been more clear. All the other comments are feedback in case you find it helpful—they're not blocking. So go ahead and remove package.json/package-lock.json and I'll merge

@paulcretu I have removed @types/node

@DivyanshuParwal package-lock.json is still conflicting, you may want to rebase/merge changes from main into your branch

@paulcretu merge conflict resolved.


quarkus: 3.12.1 -> 3.13.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/quarkus-cli/versions.
meta.description for quarkus is: Quarkus is a Kubernetes-native Java framework tailored for GraalVM and HotSpot, crafted from best-of-breed Java libraries and standards
meta.homepage for quarkus is: https://quarkus.io
meta.changelog for quarkus is: https://github.com/quarkusio/quarkus/releases/tag/3.12.3
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.12.3 with grep in /nix/store/pphs4dfp2kh8fim5kczl3q9hlfgqks1w-quarkus-cli-3.12.3
found 3.12.3 in filename of file in /nix/store/pphs4dfp2kh8fim5kczl3q9hlfgqks1w-quarkus-cli-3.12.3

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

quarkus

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/2a2a8607614db5618f434f29156dd8f3c3108d10#quarkus

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

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

1 package built:

quarkus

Maintainer pings
cc @vinetos for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/quarkusio/quarkus/releases.
meta.description for quarkus is: Quarkus is a Kubernetes-native Java framework tailored for GraalVM and HotSpot, crafted from best-of-breed Java libraries and standards
meta.homepage for quarkus is: https://quarkus.io
meta.changelog for quarkus is: https://github.com/quarkusio/quarkus/releases/tag/3.13.0
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.13.0 with grep in /nix/store/c8n4sxxa5n77qdfb09x4m2j4rnv1j7ii-quarkus-cli-3.13.0
found 3.13.0 in filename of file in /nix/store/c8n4sxxa5n77qdfb09x4m2j4rnv1j7ii-quarkus-cli-3.13.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

quarkus

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/0e35c2f10f39327b9fde3afbe8bb57197fb13f1d#quarkus

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

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

1 package built:

quarkus

Maintainer pings
cc @vinetos for testing.


Inverse logic of nzShowExpand in nz-row-expand-icon

I'm submitting a...

[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Support request => Please do not submit support request here

Current behavior

When set [nzShowExpand]="true", there is no expand icon. It shows when [nzShowExpand]="false"
Expected behavior

The logic is inverse.
Minimal reproduction of the problem with instructions

In documentation website, there is an example about tree table:
<td nz-td>
                <nz-row-indent [nzIndentSize]="item.level"></nz-row-indent>
                <nz-row-expand-icon [(nzExpand)]="item.expand" (nzExpandChange)="collapse(expandDataCache[data.key],item,$event)" [nzShowExpand]="!item.children"></nz-row-expand-icon>
                {{item.name}}
</td>

Why it should show expand icon when the item has NOT children property?
What is the motivation / use case for changing the behavior?

Environment

Angular version: 4.4.4

ng-zorro-antd version: 0.5.2

Browser:
- [x] Chrome (desktop) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] IE version XX

For Tooling issues:
- Node version: XX
- Platform:

Others:

Thanks for your attention.
This bug associated the API changing, it will be fixed in the next major version (incompatible)

close by #439


sequential adaquant updating only one batch with quantized input?

https://github.com/itayhubara/CalibTIP/blob/69077c92611b079234706784c344e8c9156f3283/main.py#L481
[0] index into the first batch.
isn't sequential adaquant supposed to update the input cache of all batches to the quantized values?

In line 465 I set quantize to true thus all values are quantized. In line 481 I just replace the FP32 record I have with the results from the quantized model.

Hi itayhubara,
Thanks for replying. Yes the quantize is set to True. But in the record that you will be using for optimization, only the first batch is updated (the replacement action you mentioned).
This is because cached_input_output is organized as [layer1, layer2 ... ] and each layer is [batch1, batch2, ...]. So in line 481, only the first batch's FP32 record is replaced with the quantized values.
Could you let me know if this is true? Thanks!


Remove IsCdRom(), IsMo() etc. in disk.cpp

disk.cpp should not know about drive characteristics. The device specific subclasses should contain the repective functionality instead. These calls should be removed at least for the purpose of adding device specific mode pages.

This ticket is obsolete, because these calls have already been removed.


Add ability to delete multi-value records in Route 53

Ability to delete multi-value records in Route 53
Description
Currently any .delete() operation on multi-value records results in RecordDoesNotExistError. This PR handles record deletion correctly regardless of its type.
Status

done, ready for review

Checklist (tick everything that applies)

[ ] Code linting (required, can be done after the PR checks)
[ ] Documentation
[ ] Tests
[ ] ICLA (required for bigger changes)

please add a supporting test to validate this feature.
thanks for your contribution

@vaygr ping!

@pquentin sorry, it slipped again.
I added the test, but while doing this I discovered that current one (test_delete_record()) doesn't cover the corresponding operation fully: it doesn't catch the error for multi-value record deletion and I couldn't find a way to check whether the record was actually deleted or not afterwards.
Suggestions?

First thank your for your contribution.
This PR is very old and out of date now so I will go ahead and close it.
If it's still relevant, please sync your changes with the latest master / trunk and open a new PR. Thanks!


feature request: implement fd_pread, golang "archive/zip" fails because fd_pread returns -1

https://github.com/bjorn3/browser_wasi_shim/blob/f4d2382d9e61d6fda580b7a5afb37699a0015745/src/fd.ts#L38-L39
time="2023-10-11T10:49:24Z" level=fatal msg="impossible to open zip reader: read /language-platforms.zip: errno<PHONE_NUMBER>"

proxy for fd_pread !! 4 25784616 1 128772n 25784612
index.js:110 return_value for fd_pread is -1

-1 becomes positive<PHONE_NUMBER>  2^32-1 in javascript because of signed 2s complement being interpreted as unsigned javascript number

When I initially prototyped this project I returned -1 as error for unimplemented things rather than a real error. Some usages have been fixed since, but several still remain. fd_pread is one of those unimplemented syscalls.

When I initially prototyped this project I returned -1 as error for unimplemented things rather than a real error. Some usages have been fixed since, but several still remain. fd_pread is one of those unimplemented syscalls.

Right, is it feasible to implement it? It's required for basic stuff like expanding a zip archive. https://www.practical-go-lessons.com/post/how-to-unzip-a-file-or-directory-with-golang-ccb0328321as70o6ujjg

I think you could copy the fd_read impl except use the given file offset instead of reading and modifying this.file_pos.

@bjorn3 have implemented the fd_pread and now Golang "archive/zip" is working for expanding .zip archives.

Nice! Merged your PR.


chore: bump zio, zio-test, zio-test-sbt from 2.0.10 to 2.0.19

About this PR
📦 Updates

dev.zio:zio
dev.zio:zio-test
dev.zio:zio-test-sbt

from 2.0.10 to 2.0.19
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "dev.zio" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #282.


Import icon from URL Favicon

I'd love to be able to fetch an icon via issuer (or other) url.

Hello,
i had the same idea. Downloading the "http://berlin.de/favicon.ico" does not work.
I learned you have to parse the website for 'rel="shortcut icon"' string. This can be complicated.
But i also found a google link/tool which downloads the favicon. (I don´t want to use google ... but maybe this is an idea)
From here: https://superuser.com/questions/157925/how-to-download-favicon-from-website
You can do this using Google S2 converter.
Here is the syntax : http://www.google.com/s2/favicons?domain=DomainName
ex: http://www.google.com/s2/favicons?domain=https://superuser.com/

You can download in different sized when adding "size"
https://t3.gstatic.com/faviconV2?client=SOCIAL&type=FAVICON&fallback_opts=TYPE,SIZE,URL&url=https://smdv.de&size=64


[Feature] Add "Watch Later button on Preview" everywhere

Hi,
thanks for the great extension.
I have a FR:
As a user I would like to add a video to the Watch Later Playlist when I watch the preview by hoovering. This is more convenient than moving the mouse near the video desciption to the 3 dot menue.
This feature is present on the History page:

but not on ALWAYS on other pages:

Sometimes I see the clock symbol on the Subscription Page and the video next to it has none. This is strange.
I understand that this is a feature or a bug by youtube.
But: Can you add it to the extension to show a clock icon allways on the thumbnails on Subscription Page and the Home Page?
Thanks in advance & BR
Günther

Me:

This is more convenient than moving the mouse near the video desciption to the 3 dot menue.

You:

then when you hover over the thumbnail on the right next to the titile, a menu appears and you can add it to the watch list.

We are talking about the same dialog. :)

This is owesome. Thanks so much.


[Java] send app version with every request

 [Java] send app version with every request

some tests


SDK

i cannot make my project

Hi @Nasrallah1997 - from reading the error message, it looks like you need to start up Android Studio GUI at least once so that you can accept a license agreement inside of it. Have you tried that?


Incorrect run test after tranning within google colab

Hi
I trained model which is about hand poses on google colab, but it seems not work correctlly. What should I do now?

What is the error?

What is the error?

This is the input image that I made on https://cloud.annotations.ai/.

Moreover, I tried other poses but all predict result is letter K.

This is the input image that I made on https://cloud.annotations.ai/.

Moreover, I tried other poses but all predict result is letter K.

Maybe you need more training data? You have a lot of classes that probably all look very similar, so you’ll need more training data for it to be able to distinguish

Maybe you need more training data? You have a lot of classes that probably all look very similar, so you’ll need more training data for it to be able to distinguish

Sure, I wonder how many images for each class that I need to add?

Sure, I wonder how many images for each class that I need to add?

I can’t say for sure, but try to get to 250 each and see if the accuracy improves

I can’t say for sure, but try to get to 250 each and see if the accuracy improves

Ok, thanks, I will try. In fact, I used same model for yolov5 and it run correctly almost cases.

Ok, thanks, I will try. In fact, I used same model for yolov5 and it run correctly almost cases.

Good to know, you could try playing around with the hyperparameters or other models to see if you can improve accuracy. The colab training process is new so there could be an issue on my end, I will look into it

Good to know, you could try playing around with the hyperparameters or other models to see if you can improve accuracy. The colab training process is new so there could be an issue on my end, I will look into it


replace location with selections

This PR should be run in the climakitae branch mapview. That branch combines app.selections and app.location, such that it's just app.selections now, which contains both data and location information. I had to modify notebooks that worked directly with app.location to function with this new update.
Perhaps we can tag team the review of this PR since it requires looking over so many notebooks (i.e. one person looks over 1-2 notebooks each?)

Okay, I think (fingers crossed) that everything should be working now, provided it's run in the climakitae branch mapview

Update May 2: Beth reviewed localization.ipynb and confirmed it runs as expected.

Update:

INTRO works great now
Localization works great now
Warming levels works great now (there is a warning at the final figure, but I believe that is resolved with a newer image/switch in the code that I had done previously that we had to roll back for the older image)

Issues:
Station_8760s (in mapview branch):
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
/tmp/ipykernel_1197/2321414481.py in <module>
----> 1 median_year = data.squeeze().map(get_median_8760)

/srv/conda/envs/notebook/lib/python3.9/site-packages/xarray/core/common.py in __getattr__(self, name)
    237                 with suppress(KeyError):
    238                     return source[name]
--> 239         raise AttributeError(
    240             "{!r} object has no attribute {!r}".format(type(self).__name__, name)
    241         )

AttributeError: 'DataArray' object has no attribute 'map'


Expand contributing documentation

Forgot to tag you for a review on this, @jaclarke. If you have a chance, see if you notice any glaring omissions or inaccuracies.


List implementation partners on website

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2530
Originally created by @DouweM on 2021-01-25 20:50:39

Let's add a Partners page listing consultancies that can help set up Meltano and build custom Singer taps. We can rank them by the amount of contributions they've made to Meltano and/or the number of (discoverable) taps they maintain.

DataTeer
Mashey
Commencis
RFA (Applied Labs)
b.telligent
Wheelhouse DMG
Slalom

View 3 previous comments from the original issue on GitLab


Removed Policy Groups 22, 19, 18, and 12 andPolicy 15.2 from Gmail Baseline per Issue 137

Based on the comments in issue #137, the following policies have been removed from the baseline:

Policy Group 22
Policy Group 19
Policy Group 18
GMAIL.15.2v0.1
Policy Group 12

The remaining affected policies have been renumbered.
Fixes #137

Fixed the drift rules file. This PR Fixes #137

Fixed Table of Contents at beginning.

Marking as blocked until #132 is complete. When that is done I can make the needed code changes here.

@LaurenBassett, I've made the needed Rego changes in this branch. Could you review my code changes? Note that because of how I merged the latest from main into here, it's showing a ton of changes. To see just my changes, under the "Files changed" tab, you can select "Changes from all commits" and change it to just my commit, "Remove deleted controls from the rego" (cb6db95).


Man pages

I don't know if this's right repo for creating this issue, please lead me to right place if I'm wrong.
After installing elm through its installer/homebrew man elm doesn't work. What can I do about it? Man pages can be helpful not only for their information, but also for programs like fish shell that build autocompletions based on man pages.

I think the right repository for this issue would be https://github.com/elm-lang/elm-platform. That's where the Elm installers are made, and certainly creation/install of man pages would have to happen during the install phase of Elm.

@jvoigtlaender thanks, I'll create an issue there. Closed this one.


Amazfit GTS 4

Hello, I see that the GTS 4 Mini is currently supported but not the GTS 4, do you think it would be possible to add it? Thank you!

Hello!
I'll check it later.

I can't add it now. But maybe later.

Ok, thank you for your work @Keddnyo

Hi @Keddnyo, do you by chance had the time to look into the issue?

I did. But now I can't add it. Maybe later it will be possible.


Graphical abstract for PMID: 30773398

to do

[ ] finish session
[ ] write announcement

text
Set7, a histone methyltransferase for the uncharted histone H3 lysine 37 (H3K37) mark

This research spotlight can be activated
Val

The Spotlight is on the main site now: https://www.pombase.org/archive/spotlight
I'll tweet this during the week.

I've sent a tweet: https://twitter.com/PomBase/status/1123756262121005059

@pgaudet  @marcfeuermann  this one will be useful for PAINt, I think it's the first
histone H3-K37  example.
https://github.com/geneontology/go-ontology/issues/17061
https://www.pombase.org/reference/PMID:30773398
(set7)

I think everything here is done.


Design system: Promos and promo-ing

Notes: https://github.com/orgs/wellcometrust/teams/experience/discussions/6

Duplicate of #3014


laminas asks for permissions for core elements without explanation

The laminas configuration asks if I want to allow core elements but I can't find any reference or explanation for 'core elements' in the documentation or installation guide.

Do you have a screenshot perhaps for that? Need to try it again with a fresh checkout to see, if I get that message too

To be more precise: I am referring to the cooArchi:setup question cooArchi will allow core elements: as defined in src/App/src/Command/SetupCommand.php line 86

The concept of core elements was planned and the option is already there. Implementation is not really there, as frontend has no support for it, as far as I known. core elements could exist from start on, or get created later on, not sure about that right now. They should be "bigger", or have another "color" or something else to see a difference.
So this option is just to early there - not perfect, as it makes people feeling missing something without proper documentation. Perhaps we should remove it and build the changes into a PR to build on top.
If interested, you could add support for it into the frontend 😃


[WIP] feat: added ip-ratelimit middleware

Problem
We need a generic way to prevent DDoS of CLEAN / MOLLI / ChemScraper and future similar tools
Approach

feat: add ip-ratelimit Middleware to ingress rules in staging + prod

How to Test
TBD

Ratelimiting actually needs to happen on the API side, not the ui :pensive:
See https://github.com/moleculemaker/mmli-job-manager/pull/31


Fix design issues on social buttons

Note: Please transform - [ ] into - (NA) in the description when things are not applicable
Related issues

Issues seen when reviewing issue #1766 and PR #1778
Description
What has been seen by Franco:

global quality of social icons is not really good and some icons are not compliant with real ones
design issues:

hover color of Snapchat should be black and not white
Facebook icon is not correct
LinkedIn icon size should be 18x18 instead of 20x20

Franco proposed new icons, they have been optimized with svgo and cleaned up of unnecessary attributes, and result is obviously visually better but bundle size is really bigger. Note that some aliasing is still visible in zoom 100% but seems due to browser display (ok in 200%).
Icons look and size comparison, and proposition:

icon
old size
new size
Look enhancement
proposition

Facebook
141 bytes
257 bytes
really better
use new icon

Instagram
840 bytes
1 664 bytes
slightly better (visible only with zoom 200%)
keep old icon

WhatsApp
511 bytes
1 216 bytes
slightly better (visible only with zoom 200%)
keep old icon

LinkedIn
239 bytes
413 bytes
really better
use new icon

Youtube
414 bytes
411 bytes
slightly better (visible only with zoom 200%)
use new icon

Snapchat
206 bytes
1 532 bytes
really better
find other icon?

Pinterest
292 bytes
832 bytes
a bit better and bigger
keep old icon?

Email
502 bytes
380 bytes
a bit better and bigger
use new icon

Total
122 748 bytes
126 353 bytes

Comparison before (above) and after (below):

No changes on icons Twitter (for now) and TikTok (already new).
Technical changes in .btn-social class:

transform can now be specified on all icons if needed, not only LinkedIn (to make code more generic)
new possibility to change hover color if specified in $btn-social-networks in _variables.scss

Motivation & Context

Changes asked by Franco after a review on social icons.
Types of change

Bug fix (non-breaking which fixes an issue)

Live previews

https://deploy-preview-2073--boosted.netlify.app/docs/5.3/components/buttons/#social-buttons
https://deploy-preview-2073--boosted.netlify.app/docs/5.3/components/footer/#follow-us-bar
https://deploy-preview-2073--boosted.netlify.app/docs/5.3/examples/footers/

Checklist

Contribution

[x] I have read the contributing guidelines

Accessibility

[x] My change follows accessibility good practices; I have at least run axe

Design

[x] My change respects the design guidelines defined in Orange Design System
(NA) My change is compatible with responsive display

Development

[x] My change follows the developer guide
(NA) I have added JavaScript unit tests to cover my changes
(NA) I have added SCSS unit tests to cover my changes

Documentation

[x] My change introduces changes to the documentation and/or I have updated the documentation accordingly

Checklist (for Core Team only)

(NA) My change introduces changes to the migration guide
(NA) My new component is added in Storybook
(NA) My new component is compatible with RTL
(NA) Manually run BrowserStack tests
(NA) Manually test browser compatibility with BrowserStack (Chrome >= 60, Firefox >= 60 (+ ESR), Edge, Safari >= 12, iOS Safari, Chrome & Firefox on Android)
[ ] Code review
[ ] Design review
[ ] A11y review

After the merge

[ ] Manually launch Percy tests

Quick prototype can be done with the following idea:

  Facebook

diff --git a/scss/_buttons.scss b/scss/_buttons.scss
index 7e08d0d2d..d0590f11b 100644
--- a/scss/_buttons.scss
+++ b/scss/_buttons.scss
@@ -248,6 +248,10 @@
     --#{$prefix}btn-active-border-color: #{$white};
     --#{$prefix}btn-disabled-color: #{$gray-700};
   }
+
+  &::before {
+    mask-size: 32;
+  }
 }

 @each $name in map-keys($btn-social-networks) {

Then the doc could present the different icons and CSS variables to use as inline CSS, or explain that project can still create their .btn-network and just define the 2 CSS vars within this class definition.


in_app_purchase only retrieves google play purchase options after hot restart on a debug build

Running my app on release build, i am retrieving 0 items from the google play store.
If i run on debug, the first launch is also empty, however, after i hot restart, now my in app purchases are retrieved. I am getting no errors. Have not tested iOS

@AvatarDevs
Please provide flutter doctor -v and a minimal reproducible code sample that shows the issue.
Thanks.

`[✓] Flutter (Channel beta, 1.23.0-18.1.pre, on Mac OS X 10.15.7 19H2 x86_64, locale en-US)
• Flutter version 1.23.0-18.1.pre at /Users/colbymaloy/Developer/flutter
• Framework revision 198df796aa (2 weeks ago), 2020-10-15 12:04:33 -0700
• Engine revision 1d12d82d9c
• Dart version 2.11.0 (build 2.11.0-213.1.beta)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
• Android SDK at /Users/colbymaloy/Library/Android/sdk
• Platform android-30, build-tools 30.0.2
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 12.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 12.1, Build version 12A7403
• CocoaPods version 1.10.0
[✓] Android Studio (version 4.1)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
[✓] Connected device (3 available)
• No issues found!`
in main.dart
`void main() async {
WidgetsFlutterBinding.ensureInitialized();
InAppPurchaseConnection.enablePendingPurchases();
await Firebase.initializeApp();
setupLocator();
setupDialogUI();
runApp(MyApp());
}`
and the method i call to populate list of products
`
Set _productLists = Platform.isAndroid ? {'no_ads'} : {'remove_ads'};
Future<List> getProductsFromStore() async {
ProductDetailsResponse response = await InAppPurchaseConnection.instance
.queryProductDetails(_productLists);
print(response.productDetails);
return response.productDetails;
}
`
in my view model, populating using the above method
`getIAPItems() async {
availableItemsToPurchase = await _iapService.getProductsFromStore();
}
`

Hi!
I faced the same issue in production - some users reported issue with purchases. In our app in-app purchase flows are covered with error reports to crashlytics and after some investigation i found out that  the app does not receive products details on queryProductDetails request - the list is empty.
I could not reproduce it yet...
Code snippet above contains pretty the same steps that we have.
Please let me know if i can help you with any additional information.
[✓] Flutter (Channel unknown, 1.25.0-4.0.pre, on Mac OS X 10.15.7 19H15 darwin-x64, locale en-UA)
    • Flutter version 1.25.0-4.0.pre at /Users/andrii_vachasov/dev/flutter
    • Framework revision a7f5fd5360 (3 months ago), 2020-11-30 13:14:13 +0100
    • Engine revision 20caf54969
    • Dart version 2.12.0 (build 2.12.0-76.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/andrii_vachasov/Library/Android/sdk
    • Platform android-30, build-tools 29.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    • CocoaPods version 1.10.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] IntelliJ IDEA Ultimate Edition (version 2020.1)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin version 201.7223.43

[✓] IntelliJ IDEA Community Edition (version 2020.1.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin version 201.7223.43

[✓] VS Code (version 1.47.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (3 available)
    • Pixel 3 (mobile) • 8C1X1GZAS  • android-arm64  • Android 11 (API 30)
    • Web Server (web) • web-server • web-javascript • Flutter Tools
    • Chrome (web)     • chrome     • web-javascript • Google Chrome 88.0.4324.182

• No issues found!

Just chiming in to say that I experience the exact same bug.  In my experience it does not require a hot restart, so I have hacked around the issue just by calling it twice:
await InAppPurchaseConnection.instance.queryProductDetails(PRODUCT_IDS.toSet());
ProductDetailsResponse productDetailsResponse = await InAppPurchaseConnection.instance.queryProductDetails(PRODUCT_IDS.toSet());

Obviously not ideal, but for me it at least cures the symptoms.

[✓] Flutter (Channel stable, 2.0.4, on macOS 11.2.3 20D91 darwin-x64, locale en-US)
    • Flutter version 2.0.4 at /Users/jason.toms/Git/flutter
    • Framework revision b1395592de (2 weeks ago), 2021-04-01 14:25:01 -0700
    • Engine revision 2dce47073a
    • Dart version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/jason.toms/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • Java binary at: /Users/jason.toms/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-1/202.7231092/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Users/jason.toms/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-1/202.7231092/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] Android Studio (version 4.1)
    • Android Studio at /Users/jason.toms/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/201.7199119/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.55.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (2 available)
    • Pixel 2 XL (mobile) • 711KPNY0904399 • android-arm64  • Android 11 (API 30)
    • Chrome (web)        • chrome         • web-javascript • Google Chrome 89.0.4389.128

• No issues found!

@jasonctoms
can confirm on flutter v2.0.6 and in_app_purchase v0.6.0

This bug is also happening on Flutter 2.5.2 and in_app_purchase 1.0.9


Update fsnotify to v1.4.7

fsnotify v1.3.1 uses unix.InotifyInit() which is not available on mips64/mips64le. Updating to a newer version allows builds to succeed on these platforms.
Signed-off-by: Jeffery To<EMAIL_ADDRESS>

Related issues:

#5689
openwrt/packages#9494 (openwrt/packages#9543)

The actual change in fsnotify: fsnotify/fsnotify#178 (released in v1.4.2)

Could you uncomment the mips targets in .promu.yml too?

@simonpasquier Sure :smile: it's updated

Thanks!


Add product page components and hero

📝 Changed routes:

/authentication

(view full size)

Commit f66b152ac379f0d738130c193c9b63ad55bcb655 (https://thirdweb-mzy9dznng-thirdweb.vercel.app).

Having the first menu super polished and the second menu like this

feels a bit weird, can we unify the same style?

On mobile the "Products" and "Resources" have a bit more padding, a bit better styles would be good here


Unify Name: "ComposableArchitecture" vs "swift-composable-architecture"

Describe the bug
Currently, using Tuist and in some other situations, there are problems to build, as Xcode throws this error:
xcodebuild: error: Could not resolve package dependencies:
declared name 'ComposableArchitecture' for package dependency 'https://github.com/pointfreeco/swift-composable-architecture' does not match the actual package name 'swift-composable-architecture'
To resolve this, an SPM .package declaration must use the "name:" argument, which is not available yet in Tuist. Therefore, the project cannot taken under Tuist control, if it uses TCA.
Expected behavior
To avoid this: why not give the package the name "ComposableArchitecture", instead of "swift-composable-architecture"?

@innoreq Thanks for taking the time to file this. We definitely find this aspect of package management to be confusing. We try to follow Apple's conventions here, though. Most of their open source libraries, like NIO, use swift-\(package-name) for the overall name, and \(PackageName) for any primary module: https://github.com/apple/swift-nio/blob/main/Package.swift#L85-L87
Were you able to get things working by adding name: to the dependency? If you're having issues, please paste in any ComposableArchitecture-related lines and we'll try to help you debug!

@innoreq I'm doing some spring cleaning, so going to close this out. If you'd like to continue the discussion, though, let me know! Any chance Tuist has this on their roadmap to fix? SPM requires explicit name: arguments as of package tools version 5.3.


added dspData struct and appropriate get_dsp() -methods to work with it.

Let's try this again. :) Just the dspData struct addition, I added the metadata as a JSON as I don't know the exact properties (and I guess they are still on poll anyways?) but we can always add more specific data in in the future I guess.

Resolves #45.

Sigh! Somehow I thought that new pushes on this branch would not propagate to the pull request automatically... Little did I know. I will, once again, create a new pull request with just the dspStruct addition 🙃