Combine nested components in TTF-Fonts

Older MacOS versions (10.6.8) have a problem with nested components in TTF-Fonts. E.g. Fira Fonts have some accents misplaced, cause they are built from nested components (see this issue).
This was fixed in Fira 4.1.6 but returned in later versions. I currently work around this issue (I still have clients using 10.6) by fixing this manually in the ttx-output (e.g. replacing uni0308.case by uni0308 and adjusting offsets). Could this be automated via a fonttools snippet or maybe a pyftsubset option? Any hints welcome.

So this is how far I got after some hours of trial and error:
font = TTFont('fontfile.ttf')
glyphTable = font["glyf"]
glyphNames = font.getGlyphNames()
for glyphname in glyphNames:
	glyph = glyphTable[glyphname]
	if glyph.isComposite():
		for compo in glyph.components:
			cname = compo.glyphName
			# only needed if component is moved
			if compo.x == 0 and compo.y == 0:
				continue
			cglyph = glyphTable[cname]
			if cglyph.isComposite() and len(cglyph.components) == 1:
				# replace with nested component and adjust x/y position
				compo.glyphName = cglyph.components[0].glyphName
				compo.x += cglyph.components[0].x
				compo.y += cglyph.components[0].y
				compo.flags = cglyph.components[0].flags

glyphTable.compile(font)
font.save('fontfile-fixed.ttf')

This works fine so far, the accents appear at the correct place on MacOS 10.6. However I don't know if it's correct to just copy the compo.flags attribute from the nested component and moreover if and how the instructions present in the components should be handled. E.g. Adieresis is originally composed with a uni0308.case component, which is itself composed of a uni0308 component, both of them including instructions:
    <TTGlyph name="Adieresis" xMin="8" yMin="0" xMax="563" yMax="888">
      <component glyphName="A" x="0" y="0" flags="0x0"/>
      <component glyphName="uni0308.case" x="471" y="0" flags="0x0"/>
    </TTGlyph>

    <TTGlyph name="uni0308.case" xMin="-342" yMin="782" xMax="-30" yMax="888">
      <component glyphName="uni0308" x="0" y="126" flags="0x4"/>
      <instructions>
        <assembly>
          PUSHB[ ]	/* 2 values pushed */
          0 2
          PUSHB[ ]	/* 1 value pushed */
          126
          PUSHB[ ]	/* 1 value pushed */
          53
          CALL[ ]	/* CallFunction */
        </assembly>
      </instructions>
    </TTGlyph>

    <TTGlyph name="uni0308" xMin="-342" yMin="656" xMax="-30" yMax="762">
      <contour>
        ...
      </contour>
      <contour>
        ...
      </contour>
      <instructions>
        <assembly>
          PUSHB[ ]	/* 2 values pushed */
          6 100
          WCVTP[ ]	/* WriteCVTInPixels */
          NPUSHB[ ]	/* 41 values pushed */
          5 3 4 3 1 0 0 1 89 5 3 4 3 1 1 0 97 2 1 0 1 0 81 12 12
          0 0 12 23 12 22 18 16 0 11 0 10 36 6 11 23
          CALL[ ]	/* CallFunction */
          PUSHB[ ]	/* 2 values pushed */
          6 0
          WCVTP[ ]	/* WriteCVTInPixels */
        </assembly>
      </instructions>
    </TTGlyph>

Do I have to care about the instructions? What would be the correct way to handle this? Could anyone with more insights in the TT Spec and fonttools point me to the right direction? Thanks in advance for any hints.

So after some more hours of trial and error, here is my final script, which deals with components consisting of more than one nested component like tildemacroncomb.case. Feel free to include it into Snippets if you think somone could find it useful.
The question of how to deal with instructions in the original component remains however.
Closing here due to lack of response.
#! /usr/bin/env python
"""Script to combine multi-level components with component offsets. While this is allowed by the spec, fonts using this (e.g. Fira Sans) hit a bug in pre-10.9 Apple font engines, so this script makes them work on older MacOS versions."""

from __future__ import print_function, division, absolute_import
from fontTools.misc.py23 import *
from fontTools.ttLib import TTFont
from fontTools.ttLib.tables._g_l_y_f import GlyphComponent

def combineNestedComponents(font):
	changed = False
	if not 'glyf' in font:
		return changed
	glyphTable = font["glyf"]
	glyphNames = font.getGlyphNames()
	# loop over all glyphs
	for glyphname in glyphNames:
		glyph = glyphTable[glyphname]
		if glyph.isComposite():
			for compo in glyph.components:
				cname = compo.glyphName
				dx = compo.x
				dy = compo.y
				# if component is not shifted, everything works fine
				if dx == 0 and dy == 0:
					continue
				cglyph = glyphTable[cname]
				if cglyph.isComposite():
					# add all multi-level components directly to the glyph and delete original component
					for i in range(len(cglyph.components)):
						glyph.components.append(GlyphComponent())
						nc = glyph.components[-1]
						nc.glyphName = cglyph.components[i].glyphName
						nc.x = cglyph.components[i].x + dx
						nc.y = cglyph.components[i].y + dy
						nc.flags = cglyph.components[i].flags

					glyph.components.remove(compo)
					changed = True

	glyphTable.compile(font)
	return changed

def usage():
	prog = os.path.basename(sys.argv[0])
	print("usage: ", prog, " font.ttf [...]")
	sys.exit(1)

def main():
	ttfonts = []
	if len(sys.argv) > 1:
		for arg in sys.argv[1:]:
			base, ext = os.path.splitext(arg)
			if ext == '.ttf':
				ttfonts.append(arg)
			else:
				print("Not ttf: " + arg)
				usage()
	else:
		usage()

	for filename in ttfonts:
		base, ext = os.path.splitext(filename)
		font = TTFont(filename)
		if combineNestedComponents(font):
			font.save(base + "-fixed" + ext)
		else:
			print("nothing to do for " + filename)

if __name__ == "__main__":
	import sys, os
	sys.exit(main())

Does this have a chance to work on variable fonts? Returned "nothing to do" for mine.

This was a fix to make static TTFs with nested components work on MacOS 10.6 to 10.8. These Systems don't support variable fonts, so you don't need it.

Will the static fonts be fine?

Looking at the script, the output you're getting seems to say your font does not contain any nested components to begin with. That message should be as valid for a VF as for a static font. That said, the script probably doesn't do the right thing for a VF if it does contain nested components.

Thanks for taking the time trying to help me @justvanrossum and @artcs!
I ran the script for the VF writing to the same file and I must've ran it twice which is why it told me "nothing to do". It is able to flatten the components for VFs but doesn't handle marks above the flattened components well (they lose their alignment with variation I think).
Luckily there's a solution printed right there in fontbakery: https://github.com/googlefonts/fontbakery/issues/2961
I missed it because I ran fontbakery with the --succinct parameter 🤦 And yes, GF requires VFs without nested components too.
In case anyone bumps into this again: I'm adding the ufo2ft filter like this:
#fixMaster.py
import sys
from plistlib import load, dump

path = sys.argv[-1]

def fixLib(path):
    with open(path, 'rb') as fp:
        pl = load(fp)
    pl['com.github.googlei18n.ufo2ft.filters'] = [{ 'name': 'flattenComponents', 'pre': 1 }]
    with open(path, 'wb') as fp:
        dump(pl, fp)

fixLib(path + 'lib.plist')

ran like this python3 fixMaster.py "./UFO/masters/FontFamily.ufo/"

@hyvyys FYI, simon added a --flatten-components option to fontmake's command line

The original script does only combine components, that have an offset defined, so it does not flatten all the components. For that you should better use fontmake as suggested by anthrotype above or use the decompose pen snippet.


Scoll on overflow

I could be overlooking something totally obvious, but I can't seem to get an inner scrolling div working on a gridster item. I've tried setting the overflow on the div containing the content (what would be the "box-content" class in the dashboard example) and tried wrapping the content inside an inner div.  Either way I get no scrollbars and overflowing content.  If I set overflow to auto on the outer container (the "box" class) I get scrollbars but they appear within the resize handle zone (ok if I remove the south and east handles but I'd rather not.)  Ideally the scrollbars would be offset with padding on the left and bottom, but setting overflow on anything inside the box class just isn't working for me.  Do you have a working example I could follow?
Other than that I have had no issues and these are perfect for what I need, thanks for the awesome work!

The gridster items are position:absolute.  One way to make an inner element fill the gridster item is to use a style like this:
.gridster-item .inner-item {
  position: absolute;
  top: 0;
  left: 0;
  bottom: 0;
  right: 0;
  padding: 10px;
}

position:absolute is what I was missing.  Thank you!
From: Dan Blaisdell<EMAIL_ADDRESS>Sent: Tuesday, January 20, 2015 10:11 PM
To: ManifestWebDesign/angular-gridster
Cc: Abigail Ames
Subject: Re: [angular-gridster] Scoll on overflow (#222)
The gridster items are position:absolute. One way to make an inner element fill the gridster item is to use a style like this:
.gridster-item .inner-item {
position: absolute;
top: 0;
left: 0;
bottom: 0;
right: 0;
padding: 10px;
}
—
Reply to this email directly or view it on GitHubhttps://github.com/ManifestWebDesign/angular-gridster/issues/222#issuecomment-70777688.


Variable Transform in web.config inside system.web section.

Note
Issues in this repo are for tracking bugs, feature requests and questions for the tasks in this repo
For a list:
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
If you have an issue or request for the Azure Pipelines service, use developer community instead:
https://developercommunity.visualstudio.com/spaces/21/index.html )
Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: Variable transform inside system.web section is not working
list here (V# not needed):
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
Environment
Build Pipeline: https://microsoft.visualstudio.com/Universal Store/_build?definitionId=62210&_a=summary
Run: https://microsoft.visualstudio.com/Universal Store/_build/results?buildId=31510184&view=logs&j=fd490c07-0b22-5182-fac9-6d67fe1e939b&t=7f2915c2-c599-545f-479d-55f858cc2762
Issue Description
I want to variable substitute in my web.config. Variable is defined under configuraton->system.web -> machine key's decryptingkey and validationkey in my Azure build pipeline.
Please find Web.DevAzure.config https://microsoft.visualstudio.com/Universal Store/_git/SC.csBillingTools?path=%2Fprivate%2FBilling%2FAdmin.Service%2FWeb.DevAzure.config
I created a build pipeline using FIle Transform task. Please find a sample build pipeline (https://microsoft.visualstudio.com/Universal Store/_build?definitionId=62210&_a=summary)
and its latest run https://microsoft.visualstudio.com/Universal Store/_build/results?buildId=31510184&view=logs&j=fd490c07-0b22-5182-fac9-6d67fe1e939b&t=7f2915c2-c599-545f-479d-55f858cc2762
I have defined some variables in build pipeline : configuration.system.web.machinekey.decryptionKey and decryptionKey and machineKey.decryptionkey
It seems FIle transfrom is only look appsettings and configsections. It is not looking system.web
Task logs
[Enable debug logging and please provide the zip file containing all the logs for a speedy resolution]
Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Error logs
[Insert error from the logs here for a quick overview]

Currently only these sections are supported for variable substitution
"applicationSettings", "appSettings", "connectionStrings", "configSections"


MERN_MongoDB: 2.3 MongoDB installation and configuration - Linux

Description
Description
Installing MongoDB on Linux

Explain all the steps for installing and configuring MongoDB on Linux.

Project Directory
Branch MERN>MERN/Topic/Backend/MongoDB/
Name the file as 2.3_MongoDB_Installation_and_Configuration_Linux.md
Domain
MERN
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign

hey @priyanka001tech , what's the status of this issue?

hey @priyanka001tech , what's the status of this issue?

Ma'am I'm started to write installation process of mongodb community edition on ubuntu..

I'll do all the changes please view this

Please review this


Invalid signatures in tooltips

I would assume this is an issue in visualfsharp but just to be sure I first wanted to report this here.
The problem disappears when renaming the "exception" parameter to something else. In fact the signature was just copied from the ILogger tooltip.

For the errors we just feed editor with the errors provided by FCS, we have no impact on it.

Should we add the exception keyword to the grammar?

Yeah... I probably don’t add double backticks in the tooltips at all, I bet it’s broken for other cases too, not only exception keyword. The bug is in the signature or tooltip formatted in FSAC if anyone would want to work on it

So if paramName isKeyword then sprintf "`%s`" paramName else paramName

@7sharp9 it's probably not just keywords but also other doubleticked things are wrong. But yes, it's simple bug to fix ;-)

Actually, I think there a function in the compiler to get back a mangled name etc

PrettyNaming.QuoteIdentifierIfNeeded

@Krzysztof-Cieslak Can you assign this for me to do?

first part patched

This is now fixed.


resolve #1094 - switch build/program from objects/presets panel tab

allow objects/patches tab to switch build mode

lgtm


Range Value shows 0 intermittently after periodic (Non-Forced) updates

Please check Services, Known Bug / Issues and Troubleshooting over here first: https://github.com/fuatakgun/kia_uvo/blob/master/README.md
Region and Brand of car
EU / Kia eNiro
Version of the integration
HACS - 1.30.1
Kia Uvo / Hyundai Bluelink - v2.5.8
Describe the bug
A clear and concise description of what the bug is.
The Range Values intermittently update with 0 when the periodic "Non-Forced" update occurs. The "Force Update" always returns the range value. This intermittent issue has been there since I deployed the integration last September however since the Feb update it seems to be happening more frequently
Debug logs if an error occurred
Not an error, just a zero value
Outlined here: https://github.com/fuatakgun/kia_uvo/blob/master/README.md
To Reproduce
Intermittent issue and seems to be happening more frequently since the Feb release
Expected behavior
Range should always show a non-zero value regardless of whether the update is passive or forced
Screenshots
If applicable, add screenshots to help explain your problem.
Screenshot #1: Range entities showing 0 after passive update 2 hours ago
Screenshot #2: Range entities showing actual range after "Forced Update"
Additional context

These ones are always a tough one.   Most likely this is the data from the car showing that.  When in that state can you compare to the native mobile app? As well compare to the attributes in your data sensor.

Thanks. I will do that the next time it happens and post my findings.

You are correct cdnninja. The range has dropped off again and confirmed that it has also dropped from the Kia Connect App. See attached. The car is due a service soon so I will ask that the Uvo system is fully updated in the car and hopefully that will sort it. Many thanks for your help on this and for creating this integration.


Huhnitor on phone

I was wondering if huhnitor can be installed on phone or do you have a huhnitor version that supports android phones
This could be useful as some people does not have a laptop to work with.
Looking forward to your response.

Hi, this is an untested scenario; but you could potentially compile it yourself for Android although we don't have a tested binary and even if it does compile, I'm not sure it would work because I have no idea how serial connections are handled over USB on Android. Another possibility is (I think) you could use a different existing Android app to achieve similar functionality; the Huhnitor is just a serial terminal with some features that make life a bit easier, I'm not sure of existing apps that do this so I wont suggest any, but I'm sure you can find a serial monitor/ serial terminal app.
That said, the WiFi Deauther V2 (the latest version is v3, but core functionality is the same), has a web UI, and can be accessed on mobile devices. This doesn't require use of the Huhnitor or a different serial monitor program.
Hope this helps.


Add feature to color area between graph line and a certain y value

Attaching a sketch to visualize.
yellow line represent the y value in question

added in 0.0.3, check this sample:

here is the source code.


"TypeLoadExecption": It seems that this nuget no longer works with Asp.Net Core 6.0

The full exception is "TypeLoadException: Could not load type 'Microsoft.AspNetCore.Http.Features.IHttpSendFileFeature' from assembly 'Microsoft.AspNetCore.Http.Features, Version=<IP_ADDRESS>". I have checked and can confirm that the assembly is present.

I have the same problem

Really concerning that this package has been left behind even though official .net documentation reference it.


Hello, may I ask how to render depth images based on the environment of this project?

In this work, we utilize normalized depth maps for auxiliary supervision of 3D point prediction from a single view, which are computed using the following function:
def voxel_to_depth_map(voxel_data):
"""
Convert 3D voxel data into a depth map along the y-axis direction.
Parameters:
- voxel_data: 3D voxel data with shape (1, x, y, z), assumed to be mostly zeros
              with non-zero values representing structures.

Returns:
- depth_map: A depth map with shape (x,y) representing the structural depth
             when viewed from the negative to positive y-axis direction.
"""
# Assume voxel data has shape (1, D, H, W), remove batch dimension
voxel_data = voxel_data.squeeze(0)

# Initialize depth map with zeros, shape (H, W)
depth_map = torch.ones(voxel_data.shape[0], voxel_data.shape[2])

# Iterate through each position on the x-z plane
for x in range(voxel_data.shape[0]):
    for z in range(voxel_data.shape[2]):
        # Search for the first non-zero voxel along y-axis
        for y in range(voxel_data.shape[1]):
            if voxel_data[x, y, z] > 0:
                # Calculate distance from non-zero voxel to x0z plane (y value)
                depth_map[x, z] = y/voxel_data.shape[1]
                break  # Exit loop after finding first non-zero value

return depth_map

In this work, we utilize normalized depth maps for auxiliary supervision of 3D point prediction from a single view, which are computed using the following function: def voxel_to_depth_map(voxel_data): """ Convert 3D voxel data into a depth map along the y-axis direction.
Parameters:
- voxel_data: 3D voxel data with shape (1, x, y, z), assumed to be mostly zeros
              with non-zero values representing structures.

Returns:
- depth_map: A depth map with shape (x,y) representing the structural depth
             when viewed from the negative to positive y-axis direction.
"""
# Assume voxel data has shape (1, D, H, W), remove batch dimension
voxel_data = voxel_data.squeeze(0)

# Initialize depth map with zeros, shape (H, W)
depth_map = torch.ones(voxel_data.shape[0], voxel_data.shape[2])

# Iterate through each position on the x-z plane
for x in range(voxel_data.shape[0]):
    for z in range(voxel_data.shape[2]):
        # Search for the first non-zero voxel along y-axis
        for y in range(voxel_data.shape[1]):
            if voxel_data[x, y, z] > 0:
                # Calculate distance from non-zero voxel to x0z plane (y value)
                depth_map[x, z] = y/voxel_data.shape[1]
                break  # Exit loop after finding first non-zero value

return depth_map

Thank you for your quick reply. The code you provided works. However, I am not sure how to generate the depth map corresponding to "proj_data" in the "forward_project" function in the "ConeBeam3DProjector" class. Do you know the solution?

Sorry I wasn't at my desk when I saw the message. Because for us, we obtain the rotated depth map and corresponding projection image by first voxelizing the point cloud, then rotating the point cloud, and finally converting the rotated image back to voxels. You can refer to the code hint below:
`
Reference
save_dir = r"/path/to/dataset_save"
image_dir = r"/path/to/dataset"
for file in CASData_list[args.n1:args.n2]:
    print("filename: ", file)
    file_path = os.path.join(image_dir, str(file), 'img.nii.gz')
    label_path = os.path.join(image_dir, str(file), 'label.nii.gz')
    image = nib.load(file_path)
    labels = nib.load(label_path)
    image_mha = image.get_fdata() * (labels.get_fdata() == 1)
    image_mha[image_mha < 0] = 0

    image_mha = crop_to_standard_cas(image_mha, scale=480)  # ImageCAS
    labels_cor = crop_to_standard_cas(labels.get_fdata(), scale=480)  # ImageCAS
    image_mha = resample_valid_voxels_to_standard(image_mha, 128)
    labels_cor = resample_valid_voxels_to_standard(labels_cor , 128)

    mask = labels_cor == 0
    image_mha = torch.tensor(image_mha, dtype=torch.float32)[None, ...]
    mask = torch.tensor(mask, dtype=torch.float32)[None, ...]
    image_mha = F.interpolate(image_mha, size=(128, 128), mode='bilinear', align_corners=False)
    resampled_mask = F.interpolate(mask, size=(128, 128), mode='bilinear', align_corners=False)
    image_mha[resampled_mask.bool()] = 0

    image_mha = image_mha / torch.max(image_mha)  # [1, C, H, W]

    voxel_center = torch.tensor([64,64,64], dtype=torch.float32)

    #label
    points = torch.argwhere(1 - resampled_mask.squeeze(0))
    points_voxels = 1 - resampled_mask.squeeze(0)
    #centerline
    centerline_voxels = torch.tensor(skeletonize_3d(points_voxels)).long()
    centerline_points = np.argwhere(centerline_voxels).T
    number = 360
    bg_mask = torch.zeros(number , points.shape[0],3)
    depthes = torch.zeros(number , 128,128)
    cl_mask = torch.zeros(number , centerline_points.shape[0],3)
    projs_all = torch.zeros(number , 128, 128)
    points_centered = points - voxel_center
    centerline_points_centered = centerline_points - voxel_center
    #rotate resampled_mask
    points_image = volume2pointsplusplus(image_mha)
    points_image_center = points_image[:,:3] - voxel_center
    points_value = points_image[:, 3].unsqueeze(1)
    volume = torch.zeros(number , 1, 128, 128, 128, dtype=points_image.dtype, device=points_image.device)
    from multiprocessing import Pool
    def process(i):
        # Perform rotation operations on the point cloud
        bg_mask = (rotate_coordinate_system(points_centered, i) + voxel_center) / 128
        cl_mask = (rotate_coordinate_system(centerline_points_centered, i) + voxel_center) / 128
        # 将Convert the rotated point cloud back to voxels
        points_image_rotated = rotate_coordinate_system(points_image_center, i) + voxel_center
        points_image_rotated = torch.cat((points_image_rotated / 128, points_value), dim=1)
        rotated_image = pointsplusplus2volume(points_image_rotated, 128)
        projs = ct_projector.forward_project(rotated_image).cpu()
        projs_all = torch.flip(projs.squeeze(0)[0, :, :], [1]).T
        dep = voxel_to_depth_map(rotated_image)
        depthes = torch.flip(dep, [1]).T
        volume = rotated_image
        return projs_all, bg_mask, cl_mask, depthes, volume

`
You need to carefully verify the code and check whether the intermediate outputs match the expected results.

Sorry I wasn't at my desk when I saw the message. Because for us, we obtain the rotated depth map and corresponding projection image by first voxelizing the point cloud, then rotating the point cloud, and finally converting the rotated image back to voxels. You can refer to the code hint below: ` Reference
save_dir = r"/path/to/dataset_save"
image_dir = r"/path/to/dataset"
for file in CASData_list[args.n1:args.n2]:
    print("filename: ", file)
    file_path = os.path.join(image_dir, str(file), 'img.nii.gz')
    label_path = os.path.join(image_dir, str(file), 'label.nii.gz')
    image = nib.load(file_path)
    labels = nib.load(label_path)
    image_mha = image.get_fdata() * (labels.get_fdata() == 1)
    image_mha[image_mha < 0] = 0

    image_mha = crop_to_standard_cas(image_mha, scale=480)  # ImageCAS
    labels_cor = crop_to_standard_cas(labels.get_fdata(), scale=480)  # ImageCAS
    image_mha = resample_valid_voxels_to_standard(image_mha, 128)
    labels_cor = resample_valid_voxels_to_standard(labels_cor , 128)

    mask = labels_cor == 0
    image_mha = torch.tensor(image_mha, dtype=torch.float32)[None, ...]
    mask = torch.tensor(mask, dtype=torch.float32)[None, ...]
    image_mha = F.interpolate(image_mha, size=(128, 128), mode='bilinear', align_corners=False)
    resampled_mask = F.interpolate(mask, size=(128, 128), mode='bilinear', align_corners=False)
    image_mha[resampled_mask.bool()] = 0

    image_mha = image_mha / torch.max(image_mha)  # [1, C, H, W]

    voxel_center = torch.tensor([64,64,64], dtype=torch.float32)

    #label
    points = torch.argwhere(1 - resampled_mask.squeeze(0))
    points_voxels = 1 - resampled_mask.squeeze(0)
    #centerline
    centerline_voxels = torch.tensor(skeletonize_3d(points_voxels)).long()
    centerline_points = np.argwhere(centerline_voxels).T
    number = 360
    bg_mask = torch.zeros(number , points.shape[0],3)
    depthes = torch.zeros(number , 128,128)
    cl_mask = torch.zeros(number , centerline_points.shape[0],3)
    projs_all = torch.zeros(number , 128, 128)
    points_centered = points - voxel_center
    centerline_points_centered = centerline_points - voxel_center
    #rotate resampled_mask
    points_image = volume2pointsplusplus(image_mha)
    points_image_center = points_image[:,:3] - voxel_center
    points_value = points_image[:, 3].unsqueeze(1)
    volume = torch.zeros(number , 1, 128, 128, 128, dtype=points_image.dtype, device=points_image.device)
    from multiprocessing import Pool
    def process(i):
        # Perform rotation operations on the point cloud
        bg_mask = (rotate_coordinate_system(points_centered, i) + voxel_center) / 128
        cl_mask = (rotate_coordinate_system(centerline_points_centered, i) + voxel_center) / 128
        # 将Convert the rotated point cloud back to voxels
        points_image_rotated = rotate_coordinate_system(points_image_center, i) + voxel_center
        points_image_rotated = torch.cat((points_image_rotated / 128, points_value), dim=1)
        rotated_image = pointsplusplus2volume(points_image_rotated, 128)
        projs = ct_projector.forward_project(rotated_image).cpu()
        projs_all = torch.flip(projs.squeeze(0)[0, :, :], [1]).T
        dep = voxel_to_depth_map(rotated_image)
        depthes = torch.flip(dep, [1]).T
        volume = rotated_image
        return projs_all, bg_mask, cl_mask, depthes, volume

` You need to carefully verify the code and check whether the intermediate outputs match the expected results.

Thank you!


Add Firefox support

Adds support for Firefox Developer Edition

updates manifest_version to 2 since version 3 is not supported by Firefox
updates readme with installation instructions
adds .xpi binary file which is the extension itself

Proof this works in Firefox:

Proof this works in Chrome:

@totallyquiche I used the web-ext library to sign the extension using the Mozilla API


Several proxy request and cache fixes for the fonts and 3rd-parties examples

Filter the response headers for proxied requests.
Always specify a UA string when fetching font CSS.
Used the default cache (instead of a named cache).
Tell the worker runtime to wait for the cache puts.
Fixed a few (non-critical) missing semicolons.

@zackbloom - Hopefully the last PR for a while (sorry for the churn). Last tweaks were based on feedback from the Workers team.


correction + addition

removed valley worx modesto which is no longer valid, correct entry for modesto already exists.
added Nkongsamba

@cameldjoulako Your group will be added when this PR is merged.


packages are old,   meta: ^1.12.0

keep your packages updated

Hey there!
The dependency is indeed set to meta: ^1.3.0. Just a quick heads up: this syntax allows users to install any version equal to or above 1.3.0, including 1.12.0. The flexibility of the caret (^) symbol means users with older versions can still run the SDK, but those who choose to update will benefit from the latest features and improvements.
Let me know if you have any questions or concerns! Thanks for your attention to this matter.


Add string concatenation operator

Add an operator to concatenate strings – maybe a & b in keeping with MMM's extremely mixed linguistic heritage.

This one's for you, @phylll ;)

Already using it!


Repository in the tutorial was disabled

Hello.
I'm following the tutorial on how to use Azure DevOps to create a CI/CD pipeline for a Stream Analytics job.
But the repository in this document was disabled (https://dev.azure.com/ASA-CICD-sample/_git/azure-streamanalytics-cicd-demo). So could you check it, please?
Thanks

@SNAKE169
Thanks for your feedback! We will investigate and update as appropriate.
Since this channel is for driving improvements towards MS Docs, could you provide the URL of the specific documentation that your feedback is applicable to? That way, we are able to make sure your feedback is addressed by the right team

@SaibabaBalapur-MSFT
it is here.
https://learn.microsoft.com/en-us/azure/stream-analytics/set-up-cicd-pipeline

@SNAKE169
Thank you for reporting the issue. The product team is fully aware of the issue and is working to resolve it as quickly as possible.

@SNAKE169
Our product team is working on this issue, and once completed, it will be updated as needed.
Now We are going to close this thread, if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


Remove obsolete code from basicauth example

Fixes #1471 / #1485
Changes proposed in this pull request:

Remove obsolete code (see the beginning of #1485 for concrete reasoning)
Remove scopes completely except necessary arg in x-basicInfoFunc implementation

I sort of made 1 more logical step and made app.py-s and README.rst-s almost identical for both swagger and openapi3. Code duplication bothered me a bit, but they are examples after all.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.788%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2893

Relevant Lines:
2989

💛  - Coveralls

Cool, thanks a lot!


Provide request attributes during selection

Provide request attributes and 'allowNoMatchingVariants' to variant selector at time of selection.
Previously, these parameters were passed to the selector at time of construction.
By wiring these parameters through at time of selection, we can access them, most importantly the
request attributes, during other parts of the selection chain.
Accessing the request attributes is needed by the VariantResolvingArtifactSet so that it
can eventually perform proper variant selection during variant reselection

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test and merge

I've triggered a build for you. Click here to see all failures if there's any.

Pre-tested commit build failed. Click here to see all build failures.

Your PR is queued. See the queue page for details.

I've triggered a build for you. Click here to see all failures if there's any.

Pre-tested commit build failed. Click here to see all build failures.

@bot-gradle test apt

I've triggered the following builds for you. Click here to see all build failures.

AllPerformanceTestsReadyForRelease build

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

I've triggered a build for you. Click here to see all failures if there's any.


Handle blockchains that are assigned to subnets with 0 validators

Describe the bug
There are blockchains assigned to subnets with 0 validators. There is no way to make a call to a blockchain when no one is running it.
To Reproduce
Go to AVAX Explorer and look for subnet ASXXLbDQcW3jYyAvbJv1zH3bjb3eo64cH23PJKWe9wH2L8D6m
Expected behavior
P-chain should either auto delete these chains from its records (when the number of validators for the validating subnet is 0 or below a threshold), or auto-label them as "idle blockchain".
Screenshots

By submitting this issue I agree to the Terms and Conditions of the Developer Accelerator Program.

I'm not sure that the P-chain really has anything to handle here, as the subnet owner could add validators to that subnet at a later point. Is the suggestion to have the explorer note that this subnet has no validators additionally to displaying the number of validators?


SmallIcon

Will be cool to have small icon showing state.

awesome, please push that!

Closing due to iTunesRichPresence no longer being maintained.


Add spin animation. Rotate on the three axis.

Use an enum for Core Animation key path.

          1 Error

:no_entry_sign:
Any changes to library code need a summary in the Changelog.

          1 Warning

:warning:
Consider adding supporting documentation to this change. Documentation can be found in the docs directory.

SwiftLint found issues
Warnings

File
Line
Reason

Animatable.swift
653
Lines should not have trailing whitespace.

Animatable.swift
658
Lines should not have trailing whitespace.

Animatable.swift
663
Lines should not have trailing whitespace.

Animatable.swift
891
Files should have a single trailing newline.

Animatable.swift
651
The initializers declared in compiler protocols such as ExpressibleByArrayLiteral shouldn't be called directly.

Animatable.swift
656
The initializers declared in compiler protocols such as ExpressibleByArrayLiteral shouldn't be called directly.

Animatable.swift
661
The initializers declared in compiler protocols such as ExpressibleByArrayLiteral shouldn't be called directly.

  Generated by :no_entry_sign: Danger


Adds command spe containertype add

Closes #5767

Thank you @MathijsVerbeeck, we'll try to have a look at it ASAP.

Before this is merged, I suggest reviewing my comment here: https://github.com/pnp/cli-microsoft365/issues/5731#issuecomment-2009311690
Summary: I don't think it's wise to have container type as the command... rather I think these should be containerType. Having commands that talk about Containers & Container Types (which are two VERY DIFFERENT THINGS in SPE) should be clear they are different things.

Replace all instances of "Container Type" and "Container" with capitalized (sentence case) versions.

Awesome @andrewconnell, thanks for the additional check.
BTW do you think it's ok I would add you to all future reviews regarding SPE?

Fine by me

Thanks both for the remarks. I think that I have implemented all changes. Could you have another look @Adam-it ?

Thanks both for the remarks. I think that I have implemented all changes. Could you have another look @Adam-it ?

On it 👍

ready to merge with some small fixes I will do along the way 🚀

merged manually.
You Rock 🤩


Getting error while executing test on Vs Code by using Testcafe

What is your Scenario?
Running test on chrome browser
What is the Current behavior?
Failed to find a DNS-record for the resource at "http://localhost:4250/".
What is the Expected behavior?
After running test, TestCafe should be open up and  perform the given test Like login page
What is your public website URL? (or attach your complete example)
http://localhost:4250/
What is your TestCafe test code?
fixtureAssign/Validation of Assign Dialog
.page(config.baseUrl)
.beforeEach(async t => {
await t.maximizeWindow();
})
.afterEach(async t => {
await assignToDialog.cancelButton.click();
await header.logoutWithExpectCopyRight();
});
test
.meta('author', 'Volodymyr')
.meta('id', 'XRAY-1603')
.meta('priority', '5- High')
([XRAY-1603] Verify that Assign dialog gets displayed by clicking on Assign button, async t => {
// #region Arrange
await login.login('Axe', '');
await t.click(leftSidebar.libraryBrowserButton);
await leftSidebar.libraryBrowser.clickNodeByColumnValue(0, 'Unchecked');
await resultsGrid.getRow(['Filename', 'Assign_UI-Doc1.txt']).click();
await resultsGrid.getRow(['Filename', 'Assign_UI-Doc1.txt']).getCell('Owner').verify.value('');
// #endregion

// #region Act
await appToolbar.homeTab.assign.click();
// #endregion

// #region Assert
await assignToDialog.verify.visibility(true);
// #endregion

});
Your complete configuration file
Using locally installed version of TestCafe.
2.6.2
npm 9.7.1
Your complete test report
Running tests in:

Chrome <IP_ADDRESS> / Windows 10

× Assign/Validation of Assign Dialog - [XRAY-1603] Verify the default value in Assign To dropdown in Assign Dialog (screenshots:
C:\Git\Testing\TestCafe\report\screenshots\2023-06-13_21-51-11\test-1\Chrome_<IP_ADDRESS>_Windows_10\errors\1.png)

Error in fixture.beforeEach hook -
Failed to load the page at "http://localhost:4250/".
Increase the value of the "pageRequestTimeout" variable, enable the "retryTestPages" option, or use quarantine mode to perform
additional attempts to execute this test.
You can find troubleshooting information for this issue at "https://go.devexpress.com/TestCafe_FAQ_ARequestHasFailed.aspx".

Error details:
Failed to find a DNS-record for the resource at "http://localhost:4250/".
Browser: Chrome <IP_ADDRESS> / Windows 10
Screenshot: C:\Git\Testing\TestCafe\report\screenshots\2023-06-13_21-51-11\test-1\Chrome_<IP_ADDRESS>_Windows_10\errors\1.png
9 |import login from '../../../page-model/login';

10 |
11 |fixtureAssign/Validation of Assign Dialog
12 |  .page(config.baseUrl)
13 |  .beforeEach(async t => {

14 |    await t.maximizeWindow();
15 |  })
16 |  .afterEach(async t => {
17 |    await assignToDialog.cancelButton.click();
18 |    await header.logoutWithExpectCopyRight();
19 |  });

at  (C:\Git\Testing\TestCafe\Scripts\tests\qa\assign\assign-to-dialog.test.ts:14:13)
at  (C:\Git\Testing\TestCafe\Scripts\tests\qa\assign\assign-to-dialog.test.ts:8:71)
at __awaiter (C:\Git\Testing\TestCafe\Scripts\tests\qa\assign\assign-to-dialog.test.ts:4:12)
at  (C:\Git\Testing\TestCafe\Scripts\tests\qa\assign\assign-to-dialog.test.ts:13:25)

1/1 failed (2s)
Warnings (1):
The "src" option from the configuration file will be ignored.
Screenshots
No response
Steps to Reproduce

TestCafe version
2.6.2
Node.js version
v18.16.0
Command-line arguments
testcafe
Browser name(s) and version(s)
Chrome
Platform(s) and version(s)
Windows
Other
No response

Hi @Klaster1,
As much as I'd like to help you, unfortunately, there's not much I can do with the current information. You shared only a test - for proper research, I need a reproducible example that I can run without additional effort. Please share the app you are testing.


[FEATURE] enable handling synonyms in neural ingestion pipelines

Handling synonyms is like an ABC thing when it comes to semantic search, however the current neural search plugin does not handle synonyms.
I suggest a feature to enable that out of the box without really going through the expense of fine-tuning embedding model. One simple way to do it is by simply replacing a word with both the word and its synonyms before generate a vector for them. The source text remains the same but the embedding gets to reflect the synonyms. The option can also be disabled in case the embedding model already understands synonyms.
Example:
Src="OS is amazing"
dst="[[Open Search]]os is amazing"
vec= getEmbedding(dst)
POST test/_doc/1
{"content":src,
"Vec":vec
}

@asfoorial This is quite interesting! Do you happen to have any benchmark tests that demonstrate how handling synonyms improves search accuracy in semantic search?


Enum updated.

I think viability is correct. viablity was a misspelling in the code. Thanks for the PR though.


Fix DocumentOrShadowRoot.fullscreenElement

DocumentOrShadowRoot needs to be a mixin, not an interface,
to allow us to extend it without addedTypes.json overwriting it.
Fixes issue #551

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

Out of curiosity, do you know where the upstream Fullscreen webidl is? DOM.webidl defines DocumentOrShadowRoot as an interface mixin, but Fullscreen.webidl just uses partial interface. You mentioned it wasn't hand-written but I couldn't find any other source.

The IDL files are fetched from upstream web specifications. I just filed https://github.com/whatwg/fullscreen/pull/141 to fix it..

Ah, I didn't realize the IDL was embedded in the .bs file then :)

Quick ping to have this merged?


Update scalafmt-core to 3.1.2

Updates org.scalameta:scalafmt-core from 2.7.5 to 3.1.2.
GitHub Release Notes - Version Diff
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!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

labels: library-update, early-semver-major, semver-spec-major

Superseded by #97.


Changed import of fim to import it from spade_src

Fixed the import of fim in order to work also when elephant is installed with the setup.py

Coverage remained the same at 85.819% when pulling 69559e10c124097bd7b1e6bc3eb78eaee756db81 on INM-6:fix/fim_path into d12505694504e78465566866eb366203a74e5778 on NeuralEnsemble:master.

Coverage remained the same at 85.819% when pulling 69559e10c124097bd7b1e6bc3eb78eaee756db81 on INM-6:fix/fim_path into d12505694504e78465566866eb366203a74e5778 on NeuralEnsemble:master.


fix package security issues

What changed? Why?
Fix package security issues detected by security bot
How did you test the change?
Build and run

Wondering did you run make codegen to generate those proto go files? why the protoc version changed in those pb.go files


Implementing Library For Other Sensors

Hi @BjarneBitscrambler ,
First of all thanks for sharing such an awesome library and complete description in examples and header files, it's really helpful.
But with all these, implementing the library for another sensor is still confusing. I checked the whole library more than once and It looks like using this library for another sensors is a little bit impossible.
It's gonna be great if you help making a better and more understandable simple code :
Lets consider that I have my raw sensor data as ax,ay,az,gx,gy,gz,mx,my,mz variables which is in standard units and frequency for library.
1.Which header files have to be included in main script?
2.How should I feed these variables to sensor fusion?
3.How should I calibrate the whole IMU ACC,GYRO,MAG?(cause I couldn't find any calibration function for GYRO)
4.How should I get the Quaternion data as output?
also making a simple script like above looks like to be so challenging cause the main fusion header file is using build and board files and I couldn't find any possible way to pass the raw sensor data to filter.
anyways I hope there is an easier way.
Kind Regards,
Mason.

Yes, I agree it's a bit daunting to start modifying this library for other sensor hardware.  First off, you've probably read this library's Customizing and Modifying section (https://github.com/BjarneBitscrambler/OrientationSensorFusion-ESP#customizing-and-modifying), which gives an overview of the files involved, but I'll mention it for others who are browsing this topic.
To be more specific, here are the steps I would follow to adapt the library for other sensor hardware (which may not be the most efficient or 'proper' - I do not consider myself an expert programmer):

clone/copy the library code
compile it to ensure your development environment is setup correctly
rename the files driver_fxas21002.*, and driver_fxos8700.* to reflect the hardware that you are using, without actually editing the files themselves yet.  Edit the other source files to reference your new driver_* files instead of the old ones.  If all three orientation functions (gyro, magnetometer, accelerometer) are integrated in one IC (instead of 2 as with NXP), then you can probably simplify things by having just one set of driver_* files instead of two.
compile again to confirm that the filename changes haven't broken anything
rewrite the FXAS21002_Init(), FXAS21002_Read(), FXOS8700_Init(), and FXOS8700_Read() functions in the driver_* files to perform the setup and read functions for your new hardware. This will require diving into the specs for your hardware to see what particular I2C commands and registers are used. You'll have to also change the low-level command definitions that perform tasks like checking the accelerometer FIFO:

 (// Command definition to read the number of entries in the accel FIFO.
registerReadlist_t          FXOS8700_DATA_READ[] =
{
    { .readFrom = FXOS8700_OUT_X_MSB, .numBytes = 6 }, __END_READ_DATA__
};

update the driver_sensors.h file to reflect the new initialization and read functions that you have created. You can choose to rename the FXOS/FXAS functions here to reflect the actual hardware you are using, or (to minimize the number of changes percolating through the code) just live with the names as currently given.  If I were to re-write my code, I would choose generic names for these functions, like Accelerometer_Init(), and map them to hardware-specific functions like FXAS_Accel_Init() all in one place to provide a level of hardware abstraction.
compile to confirm that you are able to retrieve values from your particular hardware. It might, during this and the preceding 2 steps, be easier to just focus on getting one parameter (e.g. gyro) working at a time - the other parameters can be simulated by replacing the existing code with empty functions or ones that return known values.

Depending on how different the I2C comms of the new hardware are from the NXP sensors, you may have to adjust hal_i2c.cc.  For example, the I2C rate is set to 400kHz in I2CInitialize() - this may or may not be correct for other hardware.
Also depending on your hardware's definition of axes, you may have to remap one or more of the sensor's x,y,z outputs to match the coordinate system used by the fusion algorithm.  Check hal_axis_remap.c for details.
I hope that this is enough to get you on the road to successfully using the library with another sensor. If you have specific problems/questions, please let me know.  My time availability varies a lot, but if I am able to help I will.  Good luck!

Yes, I agree it's a bit daunting to start modifying this library for other sensor hardware. First off, you've probably read this library's Customizing and Modifying section (https://github.com/BjarneBitscrambler/OrientationSensorFusion-ESP#customizing-and-modifying), which gives an overview of the files involved, but I'll mention it for others who are browsing this topic.
To be more specific, here are the steps I would follow to adapt the library for other sensor hardware (which may not be the most efficient or 'proper' - I do not consider myself an expert programmer):
* clone/copy the library code

* compile it to ensure your development environment is setup correctly

* rename the files `driver_fxas21002.*`, and `driver_fxos8700.*` to reflect the hardware that you are using, without actually editing the files themselves yet.  Edit the other source files to reference your new `driver_*` files instead of the old ones.  If all three orientation functions (gyro, magnetometer, accelerometer) are integrated in one IC (instead of 2 as with NXP), then you can probably simplify things by having just one set of driver_* files instead of two.

* compile again to confirm that the filename changes haven't broken anything

* rewrite the `FXAS21002_Init()`, `FXAS21002_Read()`, `FXOS8700_Init()`, and `FXOS8700_Read()` functions in the `driver_*` files to perform the setup and read functions for your new hardware. This will require diving into the specs for your hardware to see what particular I2C commands and registers are used. You'll have to also change the low-level command definitions that perform tasks like checking the accelerometer FIFO:

 (// Command definition to read the number of entries in the accel FIFO.
registerReadlist_t          FXOS8700_DATA_READ[] =
{
    { .readFrom = FXOS8700_OUT_X_MSB, .numBytes = 6 }, __END_READ_DATA__
};

* update the `driver_sensors.h` file to reflect the new initialization and read functions that you have created. You can choose to rename the FXOS/FXAS functions here to reflect the actual hardware you are using, or (to minimize the number of changes percolating through the code) just live with the names as currently given.  If I were to re-write my code, I would choose generic names for these functions, like `Accelerometer_Init()`, and map them to hardware-specific functions like `FXAS_Accel_Init()` all in one place to provide a level of hardware abstraction.

* compile to confirm that you are able to retrieve values from your particular hardware. It might, during this and the preceding 2 steps, be easier to just focus on getting one parameter (e.g. gyro) working at a time - the other parameters can be simulated by replacing the existing code with empty functions or ones that return known values.

Depending on how different the I2C comms of the new hardware are from the NXP sensors, you may have to adjust hal_i2c.cc. For example, the I2C rate is set to 400kHz in I2CInitialize() - this may or may not be correct for other hardware.
Also depending on your hardware's definition of axes, you may have to remap one or more of the sensor's x,y,z outputs to match the coordinate system used by the fusion algorithm. Check hal_axis_remap.c for details.
I hope that this is enough to get you on the road to successfully using the library with another sensor. If you have specific problems/questions, please let me know. My time availability varies a lot, but if I am able to help I will. Good luck!

I apologize for the delay in my reply to your kind advice. The delay was due to the malfunctioning of the harware breakout I was using (many 9250 breakout boards are fake and sent with MPU 6250 that has only accel & gyro sensors, so I've to research for alternatives and learn about other orientation sensor families). I'll follow your suggestions but ther's a basic issue I'm thinkering a lot. My research drove me to understand that there are basically two types of orientation sensors families nowaday: a "raw" one (like te one used in your project) where the execution of the fusion algorithms (Kalman filter or others like Madgwick or Mahony) is in charge of the MCU ESP32 or similar (in this case the focus of the driver library is to have efficient acces to raw data produced by the sensors to feed the algorithm computations at best; by the way Adafruit did a good job unifying all this stuff in one library https://github.com/adafruit/Adafruit_AHRS ), and an "intelligent" or "smart" one where the sensor chip has integrated an MCU capable of executing direcly the fusion algorithms (in this case the driver library has access to computed fusion data by the sensor itself, like Euler vectors or quaternions), This second family is obviously capable to produce raw data as the "raw" one thus in principle it is possible to use smart sensor in dumb mode and consequently adapt the code following your hints. Bit it should be a pity, IMHO. I think that a reworking to your library should take into account this substantial difference of sensor approach and have a switch (or a separate version) for the different abstraction layer imposed by the different sensor families. Now I'm working with BNO055 Bosh smart sensor and the ICM-20948 of  TDK Invensense (I attach the pdf of both for your info).  Let me stop to bore you tellig where I'm now: starting with the Bosh unit what library use (the one from Bosh itself or the one from Adafruit referenced by platformio) and after to decide at what level of abstraction rework your code. I'll keep you informed of my progress if any in the next future. Regards. Daniele
bst-bno055-ds000.pdf
DS-000189-ICM-20948-v1.5.pdf


Cannot build Electron.net on Raspberry Pi 4

Electron.NET: <IP_ADDRESS>
Electron API: 11.5.1

Net 5
Node 15.12.0

Target: linux-arm

Steps to Reproduce:

Check out code on Raspberry Pi 4
Run command: electronize build /target linux-arm /PublishReadyToRun false
Build error appeared:

 ⨯ chmod /usr/lib/node_modules/electron-builder/node_modules/app-builder-lib/templates/icons/electron-linux/256x256.png: operation not permitted
github.com/develar/app-builder/pkg/icons.doConvertIcon
	/Volumes/data/Documents/app-builder/pkg/icons/icon-converter.go:208
github.com/develar/app-builder/pkg/icons.ConvertIcon
	/Volumes/data/Documents/app-builder/pkg/icons/icon-converter.go:66
github.com/develar/app-builder/pkg/icons.ConfigureCommand.func1
	/Volumes/data/Documents/app-builder/pkg/icons/icon-converter.go:33
github.com/alecthomas/kingpin.(*actionMixin).applyActions
	/Volumes/data/go/pkg/mod/github.com/alecthomas/kingpin@v2.2.6+incompatible/actions.go:28
github.com/alecthomas/kingpin.(*Application).applyActions
	/Volumes/data/go/pkg/mod/github.com/alecthomas/kingpin@v2.2.6+incompatible/app.go:557
github.com/alecthomas/kingpin.(*Application).execute
	/Volumes/data/go/pkg/mod/github.com/alecthomas/kingpin@v2.2.6+incompatible/app.go:390
github.com/alecthomas/kingpin.(*Application).Parse
	/Volumes/data/go/pkg/mod/github.com/alecthomas/kingpin@v2.2.6+incompatible/app.go:222
main.main
	/Volumes/data/Documents/app-builder/main.go:90
runtime.main
	/usr/local/Cellar/go/1.15.5/libexec/src/runtime/proc.go:204
runtime.goexit
	/usr/local/Cellar/go/1.15.5/libexec/src/runtime/asm_arm.s:857
  ⨯ Cannot cleanup:
Error #1 --------------------------------------------------------------------------------
Error: /usr/lib/node_modules/electron-builder/node_modules/app-builder-bin/linux/arm/app-builder exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE
    at ChildProcess.<anonymous> (/usr/lib/node_modules/electron-builder/node_modules/builder-util/src/util.ts:243:14)
    at Object.onceWrapper (node:events:476:26)
    at ChildProcess.emit (node:events:369:20)
    at maybeClose (node:internal/child_process:1067:16)
    at Socket.<anonymous> (node:internal/child_process:453:11)
    at Socket.emit (node:events:369:20)
    at Pipe.<anonymous> (node:net:665:12)
Error #2 --------------------------------------------------------------------------------
Error: /usr/lib/node_modules/electron-builder/node_modules/app-builder-bin/linux/arm/app-builder exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE
    at ChildProcess.<anonymous> (/usr/lib/node_modules/electron-builder/node_modules/builder-util/src/util.ts:243:14)
    at Object.onceWrapper (node:events:476:26)
    at ChildProcess.emit (node:events:369:20)
    at maybeClose (node:internal/child_process:1067:16)
    at Socket.<anonymous> (node:internal/child_process:453:11)
    at Socket.emit (node:events:369:20)
    at Pipe.<anonymous> (node:net:665:12)  stackTrace=

Seems to be it is about the access permission for folder /usr/lib/node_modules/electron-builder/node_modules/app-builder-lib/templates/icons
Suddenly, I have found this Github repository, in which they mentioned:

Note: Building on Linux may give some errors. Provided are some common errors and resolutions. After attempting each resolution, try the build again:

Error: ‘electron-builder update check failed’ Resolution: follow the instructions to ‘get access to the local update config store’
Error (if the exact path to directory /usr/lib/node_modules/electron-builder/node_modules/app-builder-lib/templates/icons differs in the error message, change it in the resolution command as well):
⨯ chmod /usr/lib/node_modules/electron-builder/node_modules/app-builder-lib/templates/icons/electron-linux/256x256.png: operation not permitted
 Resolution:

sudo find /usr/lib/node_modules/electron-builder/node_modules/app-builder-lib/templates/icons -type d -user root -exec sudo chown -R $USER: {} +

I tried their command sudo find /usr/lib/node_modules/electron-builder/node_modules/app-builder-lib/templates/icons -type d -user root -exec sudo chown -R $USER: {} + and build the application. It worked :)


Cannot Parse/Validate Any Yaml File

Trying to parse/validate any yaml file results in the same error every time:
SyntaxError: Unable to resolve $ref pointer "file:///C:/Users/atom0s/Desktop/test/swagger.yaml"(…)
The file can contain anything in it, or be empty, no matter what I get this error. I'm attempting to parse on Windows 8.1.
The code I am testing with looks like this:
    <script>
        SwaggerParser.validate('swagger.yaml').then(function(api) {
            console.log(api);
        }).catch(function(err) {
            console.error(err);
        });
    </script>

Here's an image of the error from the console:

Hi.  Sorry for the delayed response.  I've been away on holiday for a few weeks.
Try referencing the file as C:\Users\atom0s\Desktop\test\swagger.yaml or as C:/Users/atom0s/Desktop/test/swagger.yaml rather than using the file:/// protocol.  Swagger Parser doesn't currently support the file:// protocol.
However, I don't see any reason not to support this protocol, so I will add this functionality soon.  Or, if you want to submit a PR, I'll gladly review and merge it.  Pretty sure it'll just be a small change to this line of code (and a new unit test).


Improve the exception messages when a property name used in a predicate is not found

Can one of the admins verify this patch?

/cc @segiddins @jpsim @tgoyne

:+1:


Bump to Ruby 2.5.5 (DO NOT MERGE!)

This pull request is to trigger builds at Travis, it is not ready for merging yet. DO NOT MERGE.

Coverage remained the same at ?% when pulling 2177651c2dbd0c311355611b2e9e321ea742a0c4 on ruby-2.5.5 into 7be089dbd0695e25bb748c821157568545cc752c on development.


To fix bug to run in eclipse with *.launch files

To fix a bug to run in eclipse with *.launch files:

isis-core-webserver was added to dependencies of pom.xml file of webapp

in launch files org.apache.isis.WebServer renamed to org.apache.isis.core.webserver.WebServer

Thanks for taking the time doing this.
In fact, we generate the archetype from the simpleapp application (fyi as per [1])
So could you make the equivalent changes to simpleapp?  (I can apply this PR or we can discard it... either way it'll be overwritten at the next release).
[1] http://isis.apache.org/guides/cgcom.html#_cgcom_cutting-a-release_releasing-the-archetype_create-the-archetype).

I fixed it in the simpleapp folder and I created a new pull request for that:
https://github.com/apache/isis/pull/46

many thanks, I'll review and merge.
On 29 April 2016 at 16:01, Reza Rahimi<EMAIL_ADDRESS>wrote:

I fixed it in the simpleapp folder and I created a new pull request for
that:
#46 https://github.com/apache/isis/pull/46
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/apache/isis/pull/45#issuecomment-215745673


Line support dash line

Thank you so much for providing such a useful and beautiful open source library. The line drawn is much more beautiful than go-chart.
I used this lib to build alert lines. Show as following:

I want to let the "1day" line to dotted line and  I try to change the style, but it seems that doesn't take effect, the code is showing below.
charts.Series{
		Type: "line",
		Name: func() string {
			if isCurValue(lValue) {
				if len(lValue.Legend) > 0 {
					return lValue.Legend
				} else {
					return "Now"
				}
			} else {
				if len(lValue.Legend) > 0 {
					return lValue.Legend
				} else {
					return "Compare"
				}
			}
		}(),
		Min:  &min,
		Max:  &max,
		Data: charts.NewSeriesDataFromValues(yValues),
		Style: chart.Style{
			StrokeDashArray: []float64{5.0, 5.0},
		},
	}

Could you tell me how to get the dotted line, thanks a lot!

I am sorry, dash line is not supported.

It is difficult to support this feature. If it is not necessary to use golang, may be you can try using charts-rs , which is better performance and simplicity.
And you can try to use the web demo page,  https://charts.npmtrend.com/ .

Thanks for your reply! I will have a try.
And for your repo, this weekend I found we can add 3 line codes to support dash line for line chart,

You can check this, if you have time. (I try to make a branch, but it seems that I do not have permission)

Do you want to make a pull request, or wait until I support this feature later.

Well, I have created a pr,  you can check this
https://github.com/vicanso/go-charts/pull/67


Document how to build on macOS (stubbing out libostree support)

Fixes #380
(minimally; autodetection would be better)

How about
cd $GOPATH/src/github.com/projectatomic/skopeo && make binary-local  BUILTAGS=$([ $(uname) == "Linux1" ]  && echo containers_image_ostree_stub)

How about
cd $GOPATH/src/github.com/projectatomic/skopeo && make binary-local BUILTAGS=$([ $(uname) == "Linux1" ] && echo containers_image_ostree_stub)

Yes, such a condition should exist, but it should exist inside the Makefile’s binay-local target, not in the end-user instructions. Hoping for a tested PR… which is now in #382.

Closing, #382 is a better solution.


Add instructions for using ros1_bridge with Jammy

Address installing ros-core-dev from Jammy upstream packages and building the ros1_bridge against them.
Signed-off-by: Michael Carroll<EMAIL_ADDRESS>

@Mergifyio backport rolling galactic foxy


add get message method in Record interface

Motivation
Currently there is not way for users to the attributes of the underlying Message received.
This simple addition that allows users to do this for Function and WindowFunction
This is a cleaner and simpler approach IMO compared to
https://github.com/apache/pulsar/pull/4313

rerun java8 tests
rerun integration tests

rerun java8 tests

rerun java8 tests

rerun java8 tests


Validate parachain ID

We are not validating the ID of a parachain, just sending to that chain when we get a user request.
We need to verify if such id is correct, maybe by having a list or a configuration?

@Bullrich i think it'd be enough to test that it's a number >1000 && <9999 (or whaterver the max id)


refactor: move storefront routes translations interface from core to lib (GH-652)

The interface with names of all storefront routes provides intellisense in the app.module. Now this interface is moved from core to the lib.
Meawhile, the fetch option is moved out from routesConfig interface to the separate root option fetchRoutesConfig
fixes #652
fixes #1060

close without merging, as configurable routes will be replaced with cms-driven routes


Test fix Kafka Performance test batch

Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run Java KafkaIO Performance Test

Run Java KafkaIO Performance Test

Run Java KafkaIO Performance Test

Run Java KafkaIO Performance Test

Run Java KafkaIO Performance Test

Run Java KafkaIO Performance Test

There are three problems:

K8s instance used for testing running out of memory and causing kafka workload fail to initialize. Cleaned up in the backend.
testKafkaIOReadsAndWritesCorrectlyInBatch trying to write/read non-exist kafka topic. Fixed in config. Needs to run seed job to take effect.
Once the first two issues resolved, found that the test does not end in time. Bumped timeout.

Run Java KafkaIO Performance Test

Test now (correctly) time out. Running seed job should resolve.

R: @johnjcasey

run seed job

Run Java KafkaIO Performance Test

Run Java KafkaIO Performance Test

The test configuration change still does not take effect. From log it shows "--kafkaTopic=beam","--readTimeout=900" for batch read job. If it takes effect this should be "--kafkaTopic=beam-batch","--readTimeout=1800"

Merging this despite failing performance test. The test never worked, and we are merging these changes in to try and fix it

Pipeline now runs, though get assertion error: "Expected: "0f12c27c9a7672e14775594be66cad9a". but: was "966684bbc4d071c54466678005c86eec"


Improve Sort By controller

Please do work for this task in a branch called issue-188.
There are several improvements/bug fixes for the Sort-By controller:
1. Change controller from drop down to radio buttons
The sort by field is easy to miss in its current form as a drop-down:

To make it more obvious what the alternatives are, change this to three radio buttons.  Only one is selectable at any given time.
2. Clarify meaning of sort options
I understand what "posted" and "company" means for sort date. What does it mean to sort by "internship"?  Do you mean sort by "Title"?
3. Sorting does not work
Try sorting by Internship, then back to sorting by posting. What you'll discover is:

Many "Posted: N/A" internships appear at the front. All the unknown dates should sort to  the end.
Sorting by posting simply doesn't work. Just scroll down and you'll see mixed up ordering. Here's an example:

Buttons changed to radios, and the wording of each filter has been changed to more reflect what each filter does

The problem where the default filter isn't matching the posted listing occurred again. Will try to fix alongside sorting problems.


GridColumn line styling based on the tick value

I have a requirement to style the grid column line based on the tick value, for example Year line should be in red color or Quarter line in blue color. I would have done it easily if vx-grid supports render props mechanism as vx-axis
Do we have a way currently to style a particular line conditionally

hey @jithureddy 👋 , thanks for checking out vx. currently this is not possible to do in @vx/grid, but I agree it would be a great feature.
we do support something similar in @vx/axis, where you can specify tick label props per tick, so I imagine a similar function in GridColumns and GridRows would be straight forward.
happy to review a PR!


ODBC underlying techno ?

Why is your underlying techno is still ODBC  in 2022 ,please ? can you go to a more modern connector please?

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

ID: 38e8eb21-ce6a-dae6-8a93-a68659aedd30
Version Independent ID: 112cbadd-b770-66af-a3d8-7291c157e9c2
Content: Power Query Snowflake connector - Power Query
Content Source: powerquery-docs/Connectors/Snowflake.md
Service: powerquery
GitHub Login: @cpopell
Microsoft Alias: gepopell

Hi @bamakus
This seems to be product feedback or a request for product support. For information about product feedback or customer support for Power Query, go to Power Query feedback.


Statblocks Refactoring

Scope
An incoming major change to Obsidian Metadata will result in many of the code block and frontmatter issues that the plugin has experienced, to resolve. However, it requires some refactoring of the code base. Ideally, we'd address the multitude of trait issues at this time.
Discovery
Unknown at this Time.
Validate
No development yet.

I am going to close this issue.


This is a bug, you don't need to call the local setPaused(false), a…

This is a bug, , it would not pause the video on iOS.
You don't need to call the local setPaused(false), as it trigger to play the video again when paused from the native controllers. It always go to the else section of setPaused(), because _paused was never set to true
The video automatically Pause or continue to Play after it hit a stall and ready to play again

We will get this reviewed this week @nemothecapt

Closing in favor of #325


URL Handling Demo Does Not Work

The demo given here, for handling URLs, does not work in the current build of Edge, nor does it work in Edge Canary.
I have tried installing the app via both browsers and triggering a link; No links open in either PWA. I am trying to implement this for my own apps, but I am unable to do so as the documentation is incorrect.

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

ID: 9788272c-700b-9e60-d419-0f845a1ff644
Version Independent ID: 4e4fbf06-2d8e-bb66-ee1b-07f9d32a940e
Content: Handle URLs in Progressive Web Apps - Microsoft Edge Development
Content Source: microsoft-edge/progressive-web-apps-chromium/how-to/handle-urls.md
Product: microsoft-edge
Technology: pwa
GitHub Login: @MSEdgeTeam
Microsoft Alias: msedgedevrel

Thanks for reaching out and reporting this issue. Unfortunately the URL handling PWA feature is being phased out in favor of 3 other features. The design of the feature wasn't satisfactory, and so the teams have gone back to the drawing board.
The 3 new features that this will be replaced with are:

A new (and simpler) handle_links manifest member, for simple cases where same-context URLs need to be handled. https://github.com/WICG/pwa-url-handler/blob/main/handle_links/explainer.md
A new scope_extensions members to allow web apps to tell the OS which other contexts they own (like when an app has several domain names). https://github.com/WICG/manifest-incubations/blob/gh-pages/scope_extensions-explainer.md
A new launch handler mechanism to let apps decide if new instances need to be launched or if the existing one should be reused. https://github.com/WICG/sw-launch/blob/main/launch_handler.md

So we need to update this documentation page and sample, and we have this on our backlog already.
But, even before that happens, I think it makes sense for us to update the page by removing the demo, and adding a banner telling people that the API will change soon.

I tested again the demo app and it still worked for me though. Even if the feature is being phased out, it's still available in Edge (all versions, as far as I can tell), and is still in an origin trial.
@rigiddesign could you please test these 2 things:

make sure you enable the feature in edge://flags, as described in the docs
test the link handling outside of the browser. In-browser navigation isn't supported by this feature. For example, you can use the Windows Run app to launch a URL.

If it still doesn't work, please provide more information about your testing setup.
Overall though, I wouldn't spend too much time learning to use this feature as it's going away soon.
One related feature recently came out of origin trial, and you might interested in it: protocol handling. You can learn more about it here: https://docs.microsoft.com/en-us/microsoft-edge/progressive-web-apps-chromium/how-to/handle-protocols

Hello buddy,
Thank you for responding to this. The flag is definitely on:
[Graphical user interface, text  Description automatically generated]
Running this just opens it in the browser:
[Graphical user interface  Description automatically generated]
I installed this via Edge Canary and also the current build of Edge, so very strange it is not working. My own PWA was opening links previously, so when it stopped working, I stumbled across the demo and found to find it had the same issue.
I even tried switching which of the Edge versions was my default browser during testing. Could the issue relate ot having Canary & the current build installed?
I did find the Launch Handler stuff, as per the experimental flags but, after trying to get it to work for a bit, I then realised it’s only currently ready in Chrome OS.
Thank you for pointing out the protocol handling. I can try this. That flag isn’t in Canary though, so is it being dropped? I noticed the tabbed stuff is no longer in Canary which I am shocked about. It seems the tabbed interface is being removed too ☹
Regards,
Tim Maiden
Developer
0113 524 1791
07745 706666
From: Patrick Brosset @.>
Sent: 12 January 2022 08:51
To: MicrosoftDocs/edge-developer @.>
Cc: Tim Maiden @.>; Mention @.>
Subject: Re: [MicrosoftDocs/edge-developer] URL Handling Demo Does Not Work (Issue #1669)
I tested again the demo app and it still worked for me though. Even if the feature is being phased out, it's still available in Edge (all versions, as far as I can tell), and is still in an origin trial.
@rigiddesignhttps://github.com/rigiddesign could you please test these 2 things:

make sure you enable the feature in edge://flags, as described in the docs
test the link handling outside of the browser. In-browser navigation isn't supported by this feature. For example, you can use the Windows Run app to launch a URL.

If it still doesn't work, please provide more information about your testing setup.
Overall though, I wouldn't spend too much time learning to use this feature as it's going away soon.
One related feature recently came out of origin trial, and you might interested in it: protocol handling. You can learn more about it here: https://docs.microsoft.com/en-us/microsoft-edge/progressive-web-apps-chromium/how-to/handle-protocols
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/edge-developer/issues/1669#issuecomment-1010789078, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AF6BG55VJ3FXAZCNPZCHFMLUVU6HJANCNFSM5LVVXBRQ.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>[rigid.design] https://rigid.design
[https://www.rigiddesign.co.uk/images/email-signature/promo.jpg]
Swarcliffe Approach, Leeds, LS14 5JZ
Tel: 07745 706666
Web: https://rigid.design rigid.design
Company Registered in England & Wales: 11947167
The information contained in this email is for the addressees only. If you have received this e-mail by mistake, please notify the sender immediately and delete this e-mail and any attachments to it from your systems. The contents may not be copied or used by anyone other than the addressee and must not be further disclosed without our permission.
WARNING: Although Rigid Software Design Ltd has taken reasonable precautions to ensure no viruses are present in this e-mail, the company cannot accept responsibility for any loss or damage arising from the use of this e-mail or any attachments to it.

Unfortunately the screenshots didn't come through on github. If you get a chance, please try to attach them again here.
There may be a case where the feature only works if "stable" is your default browser, and you installed the PWA from that browser. But I'm not 100% sure.
@diekus might be able to help us get to the bottom of this.

Thank you for pointing out the protocol handling. I can try this. That flag isn’t in Canary though, so is it being dropped?

No it isn't being dropped, the feature is now on by default on all channels of Edge. No need to turn on any flags at all. I'm currently updating the docs to remove the section about the flag and origin trial.

Apologies, I have updated that above comment.

The tabbed interface of PWAs is missing from Edge and Chrome Canary, though. Has that been scrapped?

I am not very familiar with the tabbed interface. Are you talking about the feature behind flag #enable-desktop-pwas-tab-strip?
If so, it seems like this has been extended in Chrome: 3379602: Extend tabbed web app feature flag expiries -> https://chromium-review.googlesource.com/c/chromium/src/+/3379602
Edge will likely do the same thing.
That being said, here isn't the best place to discuss this. If the problem persists, could you please send feedback about this through the feedback button in Edge? (click the ... button in the toolbar, then help and feedback, and then Send feedback`.

Yes, I do that pretty frequently :-)
I see, after weeks, the [tabbed] flags are back in Chrome Canary so, like you say, they will likely appear in Edge Canary again, too.

Closing this issue as a PR was just merged with the following changes:

https://docs.microsoft.com/en-us/microsoft-edge/progressive-web-apps-chromium/how-to/handle-protocols now doesn't mention the flag/origin trial, since the feature is on by default.
https://docs.microsoft.com/en-us/microsoft-edge/progressive-web-apps-chromium/how-to/handle-urls a note about the feature being phased out and replaced by 3 other features was added.


Add ability to opt-out of data collection

What would you like to be added:
From Kontena's FAQ page:

We collect data that you submit via kontena account registration.
We collect data about events that are happening in Lens app: application started, application stopped, logged in, logged out, cluster settings page open, cluster view open, cluster feature X installed, cluster feature X uninstalled, cluster feature X upgraded, terminal opened and kubernetes resource applied. There is no metadata related to these collected.
We are not collecting any kind of telemetry data from Lens app: for example we don't know how many clusters you might have, how many nodes you have, what is actually running in your cluster etc.

As a user, I would like the ability to opt-out of this data collection.
Why is this needed:
In some environments and teams, there's a strict policy of not participating in any data collection.
Environment you are Lens application on:

Kubernetes distribution: vanilla on-prem
Desktop OS: Mac

At the moment this is not possible and we don't have plans to disable data collection. It's the only way for the company behind the product to see how many users are actively using it. As reminder: no private data is collected. However, we see issues with certain Enterprise environments.
A workaround for this might be to use a build that we are making available for big Enterprise IT departments. This build is primarily designed for big enterprise IT for easy software distribution, but among other things - it won't include any kind of tracking. Unfortunately, this build will require Enterprise license to work.

Fixed in 3.0.


Cannot find module 'vscode-uri'

I sometimes get this error if I make changes then npm run build. An npm install usually fixes things for a while, but then the error will eventually appear again.
src/LanguageServer/Uri.ts:1:21 - error TS2307: Cannot find module 'vscode-uri' or its corresponding type declarations.
1 import { URI } from 'vscode-uri';

Suspect this is related to npm link shenanigans - can you check with a straight install with no links - vscode-uri is present in dependencies so odd this could be inconsistent.

I think this was a build issue for development as indicated on my previous comment, and these modules/the build process have subsequently changed


runtime: PROCESS_ALL_ACCESS didn't check for 0XFFFF

Fixes #29176. PROCESS_ALL_ACCESS now checks for 0xFFFF.

I've signed the CLA :)


Make test pass within the context of the LS Core Defaults plugins test

For this plugin this means including the helpers in another way as using the standard rspec.configure is not working in the situation described in the title.
This is not standard rspec, although necessary because of:

The way we run LS default plugins tests.
The fact that this helper is not generic enough to be moved into devutils.

LGTM


Return stream id on auth, split store.SetActive

This commit makes the Auth function return the published streams id.
The reason behind this is simply that this is the only point, where its
possible to gather which stream is actually beeing published, because the
server reveals the publishers authkey at this point.
With this change its also possible to set the streams active flag by its
id. Deactivation on unpublishing can only be done by looking at the
streams Application/Name Pair and thus the SetActive function is split
into SetActive(id) which can is called by the streams id and
SetInactive(app, name) which sets all known streams for that app/name
pair as not active.

Closing. Clean pull request including this will follow.


Generating meaningless results

Hi! I tried to load the FlagAlpha/Llama2-Chinese-7b-Chat model using the llama2 chat sample code, the model is base on meta's meta-llama/Llama-2-7b-chat-hf and speed is excellent, but it generated meaningless results. Is it related to model support or did I overlook something?
from transformers import AutoTokenizer, TextStreamer
from intel_extension_for_transformers.transformers import AutoModelForCausalLM, WeightOnlyQuantConfig

# Please change to local path to model, llama2 does not support online conversion, currently.
model_name = "FlagAlpha/Llama2-Chinese-7b-Chat"
woq_config = WeightOnlyQuantConfig(compute_dtype="int8", weight_dtype="int4")
tokenizer = AutoTokenizer.from_pretrained(model_name, trust_remote_code=True)
streamer = TextStreamer(tokenizer)
model = AutoModelForCausalLM.from_pretrained(model_name, quantization_config=woq_config, trust_remote_code=True)

while True:
    prompt = input("> ").strip()
    if prompt == "quit":
        break
    b_prompt = "[INST]{}[/INST]".format(prompt)  # prompt template for llama2
    inputs = tokenizer(b_prompt, return_tensors="pt").input_ids
    outputs = model.generate(inputs, streamer=streamer, interactive=True, ignore_prompt=True, do_sample=True)

version:
intel-extension-for-transformers 1.2.2
transformers                     4.34.1
transformers-stream-generator    0.0.4

Thanks!

Thanks for you usage,

Could try newest branch and build from source  rather than 1.2.2 ?
And I would recommend you replace
while True:
prompt = input("> ").strip()
if prompt == "quit":
break
b_prompt = "[INST]{}[/INST]".format(prompt)  # prompt template for llama2
inputs = tokenizer(b_prompt, return_tensors="pt").input_ids
outputs = model.generate(inputs, streamer=streamer, interactive=True, ignore_prompt=True, do_sample=True)

To
prompt = "once upon a time, there is a girl"
inputs = tokenizer(prompt, return_tensors="pt").input_ids
outputs = model.generate(inputs, streamer=streamer, interactive=True, ignore_prompt=True, do_sample=True)
Because this template is mainly for llama 2 chat rather for Chinese version model.

Building from source(1.2.3.dev68+g43e30bcabd) worked fine, thanks

Thanks for your usage!


appflowy: <IP_ADDRESS> -> 0.0.8

Description of changes

Update appflowy to the latest version
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1516

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

1 package built:

appflowy

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/721


First commit of a polylog code, directly derived from mpmath. Not ready for prime time

hi, this is my first full-fledged hack at scipy, within github etc.... I aim at providing polylogarithm in scipy/special, heavily based on mpmath implementation. The polylog code is not ready at all yet (missing doc and UFunc implementation especially), but this pull request concerns the preliminary hack I needed to do, following a suggestion by Pauli Virtanen, in order to acces directly the zetac CEPHES C function in my cython code special/_polylog.cyx. In order to be able to link against it, I need to extract "special_raise_warning" function from _cephesmodule.c and put it in a separate raise_warning.c file, added to the sources in the sc_cephes.so build.
Just to give an idea, here is a timeit of the python exposed zetac call, compared to the polylog direct C call :
In [1]: from scipy.special import polylog
In [2]: from scipy.special import zetac
In [3]: %timeit polylog(7,1)
1000000 loops, best of 3: 551 ns per loop
In [4]: %timeit 1+zetac(7)
100000 loops, best of 3: 7.25 us per loop
I would like to have the green like on this preliminary modif to cephemodule.c : the files concerned thus are
new file:   scipy/special/raise_warnings.c
modified:   scipy/special/__init_.py
modified:   scipy/special/_cephesmodule.c
Johann

Did a polylog implementation end up anywhere? Or is there a recommended way to reduce this to an existing scipy.special routine?


How to use code-generator to generate clientset when using go 1.11 modules (GO111MODULE=on)

I successfully generated clientset, lister, informer by code-generator when I place my project into $GOPATH/src.
However, when I use go 1.11 modules and place my project anywhere outside $GOPATH, I find something go wrong in the output.
Is there any detailed solution for my problem? Thanks a lot!

Is there someone can help me ? 🤔

Is there someone can help me ? 🤔

After several trying, I figure it out.
https://github.com/kubernetes/sample-controller#when-using-go-111-modules provides helps.


Add generic pipeline publisher

The main feature added here is a publisher added that reads through the pipeline and exposes sort of what one might expect in terms of endpoints.
An auxillary / somewhat tangental feature also is the integration of a dynamic reconfigure server to allow for runtime adjustment of parameters. Right now it's just for stereo depth. I didn't want to go all out and add more until the feature direction itself was validated since this PR had already gotten away from me a little bit.
See https://github.com/jdavidberger/depthai-ros-examples/commit/42b6738c61e6d69ddcf809b887a5a568e3ae29c8 for use of the new publisher.

Is this still up for review? Haven't heard anything on it in a while

Is this still up for review? Haven't heard anything on it in a while

I think we discussed on slack that it doesn't really add much additional value by adding another generic publisher.

I was sorta under the impression it was going to get rolled in as support for a monolithic node from how the conversation ended there. The reason I ask is that the dynamic reconfigure stuff is important for one of our projects and if it's not in mainline I'll have to just commit to adding all of it to our internal tooling.

I'm up for the dynamic reconfigure part. Can't we add that as a converter to existing model and create a monolithic node/nodelet using the same ?
Note that we want to do that such a way we support both ros1 and ros2.

The dynamic reconfigure portion is mostly orthogonal and could be separated out. But to be honest, it's intractable to re-describe our pipelines all over again for the benefit of a creating a rosnode so it's sort of a moot point for me.


PySpark Code error: account, not account_name.

There is a mistake in the PySpark Code, it should be account instead of account_name in the fsspece argument.
https://filesystem-spec.readthedocs.io/en/latest/api.html#fsspec.open

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

ID: 91f1c299-9cf3-25c0-2ded-4a9d14a08938
Version Independent ID: b948ca8c-c162-a74f-c741-ab5d6dc32059
Content: Tutorial: Use FSSPEC to read/write ADLS data in serverless Apache Spark pool in Synapse Analytics - Azure Synapse Analytics
Content Source: articles/synapse-analytics/spark/tutorial-spark-pool-filesystem-spec.md
Service: synapse-analytics
Sub-service: spark
GitHub Login: @AjAgr
Microsoft Alias: ajagarw

@yang-jiayi  Thanks for the feedback! We are investigating and will update you shortly.

@yang-jiayi I had tested the PySpark code mentioned in the document and it works as excepted.

@CHEEKATLAPRADEEP-MSFT
Thanks for the reply.

This is a spark pool 3.1 and Managed VNet+DEP-Enabled environment.

Hi, @CHEEKATLAPRADEEP-MSFT
Could you please check again?

@yang-jiayi Looks like a known limitation with the spark pool 3.1 and Managed VNet+DEP-Enabled environment.
The document indented to work with different kind of spark version, I would request the product team to leave an important note to include while working with Spark 3.1 versions.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Improve README quality

As a user of MultiTouch, I would like to be able to learn everything I need to know from the README.
Update the README to improve its visual quality and content.

@all-contributors
please add @Russell-Newton for code, docs, infra, maintenance
please add @xorbit3024 for code, docs, infra, tests
please add @jrdike for code, docs, tests
please add @ocean-ift for code, docs, tests
please add @deborahsrcho for code, design, content

@all-contributors please add @Russell-Newton for code, docs, infra, maintenance

@all-contributors please add @xorbit3024 for code, docs, infra, tests

@all-contributors please add @jrdike for code, docs, tests

@all-contributors please add @ocean-ift for code, docs, tests

@all-contributors please add @deborahsrcho for code, design, content


Use http2bin instead of twitter for release test

Update the request adapter test to hit http2bin instead of twitter.
Test was failing with twitter as discussed in #94.

Hurrah! :cake: :sparkles: :cookie:

Thanks a bunch @jdecuyper!


[IOS] 'logger/react_native_log.h' file not found in CxxNativeModule.cpp Xcode

Description
Hello,
I wanted to update my project from react-native 0.64 to 0.67. I updated well I deleted my nodes modules folder my package.lock, the podfile.lock and the Pods folder.
I then did an npm install, cd ios pod install and npx react-native bundle --entry-file='index.js' --bundle-output='./ios/main.jsbundle' --dev=false --platform='ios' --assets-dest='./ios'
and when I try to build my project on an iphone 8 ios 15.3.1 it does not work and the error:
'logger/react_native_log.h' file not found from CxxNativeModule.cpp file
appears
Can you help me please
Version
0.67.3
Output of npx react-native info
System:
OS: macOS 12.2.1
CPU: (12) x64 Intel(R) Core(TM) i7-8700B CPU @ 3.20GHz
Memory: 25.86 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.14.0 - /usr/local/bin/node
Yarn: Not Found
npm: 8.3.1 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3
Android SDK: Not Found
IDEs:
Android Studio: 2021.1 AI-211.7628.21.2111.8193401
Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild
Languages:
Java: 17.0.1 - /usr/bin/javac
npmPackages:
@react-native-community/cli: ^7.0.1 => 7.0.3
react: 17.0.2 => 17.0.2
react-native: 0.67.3 => 0.67.3
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
Change version of React-native (0.64 to 0.67)
npm install
cd ios & pod install
npx react-native bundle --entry-file='index.js' --bundle-output='./ios/main.jsbundle' --dev=false --platform='ios' --assets-dest='./ios'
Build the project to xcode
Snack, code example, screenshot, or link to a repository
_No response

_

@Marinaarimany i also had a problem exactly same with.. did you solve this?

Has this been solved? I also have this issue.

@Marinaarimany do you mean you didn't see such issue after creating new project with same package and pod file?

it doesn't seem to me, I had to update some packages that I was using

Has this been solved?

Here is solution

Add pod 'React-logger', :path => '../node_modules/react-native/ReactCommon/logger'

Source: https://github.com/facebook/react-native/issues/33061#issuecomment-1033463246

A possible fix for this is to disintegrate pods from your project and reinstall pods
pod deintegrate
pod install


chore: resolve jQuery devDependency CVE

Description

Update the internal jQuery version (used for tests) to the latest version to resolve a CVE.
Motivation and Context
This PR resolved a jQuery common vulnerability affecting jQuery < 3.
As Foundation supports jQuery >=2.2.0, the jQuery peer dependency is not changed. PeerDependencies versions in package.json should only reflect the actual compatibility with the package, regardless of promotion or "potential" security issue. It's up to the end developer to choose the package version corresponding to its own needs and to the risks comming with its own usage.
Types of changes

[ ] Documentation
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing
functionality to change)

Checklist (all required):

[x] I have read and follow the CONTRIBUTING document.
[x] There are no other pull request similar to this one.
[x] The pull request title is descriptive.
[x] The template is fully and correctly filled.
[x] The pull request targets the right branch (develop or support/*).
[x] My commits are correctly titled and contain all relevant information.
[x] My code follows the code style of this project.
[ ] I have updated the documentation accordingly to my changes (if relevant).
[ ] I have added tests to cover my changes (if relevant).
[x] All new and existing tests passed.

Didn't we explicitely set it to 2+ to prevent issues with old setups? And to me it does not seem to be a peerDependency.

Foundation is compatible with jQuery 2.2.0+ so we rollbacked to >=2.2 for peerDependencies (and dependencies before). We also needed jQuery in devDependencies for development mode (and tests), as peerDependencies are not installed with npm install. However, as we only use this version for internal tests, we don't care about the "real compatibility range". It only matters for peerDependencies.
Anyway with >=2.0.0, npm and Yarn will install the latest compatible version 3.3.1. That's why there is no changes in the lockfiles, we're not changing the actual jQuery version used for test, just the range to prevent an unsecure jQuery version (< 3) to be installed and make dependency watchers happy.
Related to:

https://github.com/zurb/foundation-sites/issues/11290 jQuery and what-input should be peerDependencies
https://github.com/zurb/foundation-sites/pull/11294 chore: move jQuery & what-input to peerDependencies


Add back execution retry for query.

Issue:
We lacked tests for implicit usage of the execution strategy, so when the query pipeline was rewritten the lack of this feature wasn't detected.
Solution:
Add execution retry for query with a buffering data reader.
Move the retry scope for SaveChanges to properly reset the state before retrying.
Add tests for implicit usage of the execution strategy.
Fixes #18628

cc @Pilchie


Explore frontend performance measurement

Start Date
Project Lead
Actual Ship Date

2023-07-01
TBD
TBD

Description

On the frontend, we can improve the UX by improving performance. First, we would need to analyze the current state and find the bottlenecks that affect the performance the most. We would probably need to reduce JS bundle size.
For this project, we can reach out to external contributors who could do an audit for us.
Documents

[ ] Project Proposal
[ ] Implementation Plan

Issues

Prior Art

https://github.com/WordPress/openverse/issues/646
https://github.com/WordPress/openverse/issues/626
https://github.com/WordPress/openverse/issues/490

This project was not completed in 2023 and we are closing it in favor of prioritizing other work. Closing this issue.


D checker: Add src to default source paths

src and source are both default source paths in DUB.

That used to be the default in the past, and people had trouble with it.  Also, you can achieve the same thing without code changes, by setting g:syntastic_d_include_dirs in your vimrc.  Patches to the defaults are considered only when they solve serious problems.  Sorry, but no.
Please see here for a better solution.  I'll make a patch to that effect if (1) you can confirm this works, and (2) you tell me which was the first (released) version of dub that could do dub describe --import-paths.

No problem. I wasn't even sure it is the right way to do that. I added the function from the linked issue to my .vimrc. Will report next week if it works.

Please see cc6b92a.


Setup infrastructure that runs experiment on a remote machine and then collects results

In order to prepare for an evaluation on different machines we need to setup an infrastructure that allows running experiments on a remote machine and then collects the results together with some metadata about the machine.

Closing for now since it is irrelevant


The Obfuscated File cannot run.

I keep getting this error."This app cannot run on this PC..."

it's maybe malware