Fallback for when WebAssembly is not available

WebAssembly is not available when browsers disable JIT compilation:

Edge's enhanced security mode
The Tor Browser's "safer" security level
iOS Lockdown mode
Vanadium and Bromite are hardened Android browsers that support per-site JIT toggles.

I'm sure more examples exist. Some of these, such as iOS Lockdown and Edge's Enhanced Security, are relatively recent developments, so it's not unreasonable to assume that the popularity of JIT-toggling will increase with time.
A good approach would be to have an asm.js-based fallback. That's the approach used by CryptPad, and it has good results. Some polyfills allow transpiling WebAssembly to asm.js with usable performance.

This is a good idea, and the concept of transpiling the WebAssembly is especially great as it reduces any maintenance burden in having both implementations. I haven't experimented with any transpilers, but Pagefind's WebAssembly is intentionally simple and small, so if anything would work through that process it would be this.
I'm unlikely to have the time to tackle this in the medium-term, but I'm open to someone contributing this as a feature. Ping me in this thread if anybody wants to spitball what might be needed for them to implement this 🙂

polywasm works fine with pagefind.
tl;dr
self.WebAssembly = self.WebAssembly || (await import("https://unpkg.com/polywasm@0.1.4/index.min.js")).WebAssembly

I just ran into this issue with chromite and vanadium.  I posted about it here but will remove it now.

polywasm works fine with pagefind.

Impressive! Thanks for the pointer. I'll take it for a spin and then look at adding this as an official fallback.


Statement is timeout when use oceanbase as meta engine.

What happened:
https://github.com/juicedata/juicefs/runs/6619573475?check_suite_focus=true
2022/05/27 10:46:11.769364 juicefs[1125156] <INFO>: Syncing from file:///root/actions-runner/_work/juicefs/juicefs/data/ to s3://myjfs/data/ [sync.go:619]
2022/05/27 10:46:11.772530 juicefs[1125157] <INFO>: Syncing from file:///root/actions-runner/_work/juicefs/juicefs/data/ to s3://myjfs/data/ [sync.go:619]
2022/05/27 10:46:11.777670 juicefs[1125158] <INFO>: Syncing from file:///root/actions-runner/_work/juicefs/juicefs/data/ to s3://myjfs/data/ [sync.go:619]
2022/05/27 10:46:33.681259 juicefs[1125124] <ERROR>: error: Error 4012: Statement is timeout
goroutine 865 [running]:
runtime/debug.Stack()
	/usr/local/go/src/runtime/debug/stack.go:24 +0x65
github.com/juicedata/juicefs/pkg/meta.errno({0x306bd20, 0xc002dd9158})
	/root/actions-runner/_work/juicefs/juicefs/pkg/meta/utils.go:92 +0xc5
github.com/juicedata/juicefs/pkg/meta.(*dbMeta).doUnlink(0xc00007af00, {0x3098b98, 0xc0018c3d40}, 0x1e, {0xc002dd75f0, 0x2})
	/root/actions-runner/_work/juicefs/juicefs/pkg/meta/sql.go:1320 +0x21e
github.com/juicedata/juicefs/pkg/meta.(*baseMeta).Unlink(0xc00007af00, {0x3098b98, 0xc0018c3d40}, 0x1e, {0xc002dd75f0, 0x2})
	/root/actions-runner/_work/juicefs/juicefs/pkg/meta/base.go:714 +0x1b8
github.com/juicedata/juicefs/pkg/meta.emptyDir({0x30a5e70, 0xc00007af00}, {0x3098b98?, 0xc0018c3d40}, 0x1e, 0xc0019ab080)
	/root/actions-runner/_work/juicefs/juicefs/pkg/meta/utils.go:256 +0x45c
github.com/juicedata/juicefs/pkg/meta.emptyEntry({0x30a5e70, 0xc00007af00}, {0x3098b98, 0xc0018c3d40}, 0xc0077fcdce?, {0xc0077fcdce, 0x24}, 0xc00214fef0?, 0xc0077fcdc0?)
	/root/actions-runner/_work/juicefs/juicefs/pkg/meta/utils.go:266 +0x5c
github.com/juicedata/juicefs/pkg/meta.Remove({0x30a5e70, 0xc00007af00}, {0x3098b98, 0xc0018c3d40}, 0xd?, {0xc0077fcdce, 0x24})
	/root/actions-runner/_work/juicefs/juicefs/pkg/meta/utils.go:289 +0x174
github.com/juicedata/juicefs/pkg/fs.(*FileSystem).Rmr(0xc0007fc660, {0x3098b98?, 0xc0018c3d40}, {0xc0077fcdc0, 0x32})
	/root/actions-runner/_work/juicefs/juicefs/pkg/fs/fs.go:441 +0x2aa
github.com/juicedata/juicefs/pkg/gateway.(*jfsObjects).CompleteMultipartUpload(_, {_, _}, {_, _}, {_, _}, {_, _}, {0xc000281400, ...}, ...)
	/root/actions-runner/_work/juicefs/juicefs/pkg/gateway/gateway.go:892 +0x792
github.com/minio/minio/cmd.objectAPIHandlers.CompleteMultipartUploadHandler({0x2b76860?, 0x2b76850?}, {0x30801d8?, 0xc007e95040}, 0xc007012500)

What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?
Environment:

JuiceFS version (use juicefs --version) or Hadoop Java SDK version:
Cloud provider or hardware configuration running JuiceFS:
OS (e.g cat /etc/os-release):
Kernel (e.g. uname -a):
Object storage (cloud provider and region, or self maintained):
Metadata engine info (version, cloud provider managed or self maintained):
Network connectivity (JuiceFS to metadata engine, JuiceFS to object storage):
Others:

This is a problem of oceanbase.


Clarification questions (ffmpeg build, dropped openv)

Hello,
1- is there a reason that ffmpeg is build based on arch and not ubuntu/debian based?
2- compared to an older Dockerfile the opencv part is now dropped, what is the reason for it?
Thanks for clarifications!

1- is there a reason that ffmpeg is build based on arch and not ubuntu/debian based?

I want to ensure that I build my ffmpeg as new as I reasonably can. I tried to be deb based, but I then had a too old nasm and couldn't compile it myself from scratch for example. Older versions may result in worse performance, so it was easier to get everything working with arch. I was thinking of trying to go away from arch, but that would mean to figure out how to compile certain things which also would increase docker build time or use outdated software.

2- compared to an older Dockerfile the opencv part is now dropped, what is the reason for it?

I wanted to remove OpenCV since a while now, but I had a color fix which used it as a depdendency.
https://github.com/styler00dollar/VSGAN-tensorrt-docker/blob/13f1210df76d33c120ceb04f67335b3eff760341/color_transfer.py#L4
This color script can be considered replaced with pifroggi/vs_colorfix, which is better. I added it when I removed OpenCV.
The second reason is that OpenCV had an absurd amount of dependencies. I don't want to maintain this or have this bloat my final docker size.
https://github.com/styler00dollar/VSGAN-tensorrt-docker/blob/ac47012b9313fe76f37914601dafea82df0e94e6/Dockerfile#L840-L873


Yandex Music is broken

Checklist

[x] I'm reporting a broken site support
[x] I've verified that I'm running youtube-dl version 2<IP_ADDRESS>
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar issues including closed ones

Verbose log

youtube-dl --rm-cache-dir --extract-audio https://music.yandex.ru/album/10130567/track/63591534

Removing cache dir ~/.cache/youtube-dl ..
[yandexmusic:track] 63591534: Downloading track JSON
[yandexmusic:track] 63591534: Downloading track location url JSON
[yandexmusic:track] 63591534: Downloading track location JSON
ERROR: An extractor error has occurred. (caused by KeyError('storageDir')); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

I, too, have a likely related issue with yandex music. I tried downloading an entire album, and while it appeared to complete successfully, it only downloads the first 30 seconds of each track.
$ youtube-dl https://music.yandex.ru/album/417333
[yandexmusic:album] 417333: Downloading album JSON
[download] Downloading playlist: Гости из будущего - Best (2001)
[yandexmusic:album] playlist Гости из будущего - Best (2001): Collected 14 video ids (downloading 14 of them)
[download] Downloading video 1 of 14
[yandexmusic:track] 30390995: Downloading track JSON
[yandexmusic:track] 30390995: Downloading track location url JSON
[yandexmusic:track] 30390995: Downloading track location JSON
[download] Destination: Гости из будущего - Люби меня по-французски-30390995.mp3
[download] 100% of 469.84KiB in 00:00
[download] Downloading video 2 of 14
[yandexmusic:track] 30390998: Downloading track JSON
[yandexmusic:track] 30390998: Downloading track location url JSON
[yandexmusic:track] 30390998: Downloading track location JSON
[download] Destination: Гости из будущего - Так отважно-30390998.mp3
[download] 100% of 469.84KiB in 00:00
[download] Downloading video 3 of 14
[yandexmusic:track] 30391000: Downloading track JSON
[yandexmusic:track] 30391000: Downloading track location url JSON
[yandexmusic:track] 30391000: Downloading track location JSON
[download] Destination: Гости из будущего - Это сильнее меня-30391000.mp3
[download] 100% of 469.84KiB in 00:00
[download] Downloading video 4 of 14
...
[download] 100% of 469.84KiB in 00:00
[download] Finished downloading playlist: Гости из будущего - Best (2001)

(notice the file sizes)
I'm running youtube-dl 2<IP_ADDRESS>.

How can I close issue?

Doesn't make a difference to me. Or do I need to dump the related cookies from my browser?

@grishka
It doesn't matter

Well, for me, this
$ youtube-dl --cookies ~/cookies.txt https://music.yandex.ru/album/417333

still downloads 30-second fragments.

Read the documentation carefully
https://github.com/ytdl-org/youtube-dl#how-do-i-pass-cookies-to-youtube-dl

I downloaded this
https://send.firefox.com/download/c9c48756ad19f6c2/#gKXFFLK5jHA_COlvWDlSsQ

Yeah it does download complete tracks with that file filled with yandex cookies dumped from a logged in browser. That's what I meant initially and you said "it doesn't matter" so I assumed it just needed cookies to persist between requests.

How can I close issue?
Because it's not a bug.

I downloaded this https://send.firefox.com/download/c9c48756ad19f6c2/#gKXFFLK5jHA_COlvWDlSsQ

hi, your file's dead, can you upload it anywhere else? having the same problem here

@akimdi do the quotes even ping people????? not sure so i'm gonna do this

@toimine  I don't quite understand what you want me to upload

@akimdi the cookie file, mine didn't work

@toimine
This is confidential information. You can create your own cookies-file.
Here is the instruction how to do it
https://github.com/ytdl-org/youtube-dl#how-do-i-pass-cookies-to-youtube-dl


[eas-cli] Only configure updates in generic projects

Checklist

[ ] I've added an entry to CHANGELOG.md if necessary. You can comment this pull request with /changelog-entry [breaking-change|new-feature|bug-fix|chore] [message] and CHANGELOG.md will be updated automatically.

Why
In #888 we refactored the build:configure command and as a result of that change we ended up attempting to configure native iOS and Android projects for expo-updates even if they don't exist because the project is managed. It's possible to repro this with:
expo init project # blank app
cd project && expo install expo-updates
eas build:configure
# Error: Android project folder is missing in project ...
# Same sort of thing for iOS

How
I used the same logic that we use in syncProjectConfiguration to detect if we are in a generic project or not, then skip running updates configuration in managed projects:
https://github.com/expo/eas-cli/blob/dd2303dbb2b01dcd941591b5ccba01bbd04b29a7/packages/eas-cli/src/build/ios/syncProjectConfiguration.ts#L26-L29
Test Plan

Run easd build:configure in managed app with expo-updates installed, it should just create eas.json and nothing else
Run easd build:configure in bare app with expo-updates installed, it should sync config from app.json to native projects

/changelog-entry bug-fix Fix build:configure expo-updates configuration to only run on generic projects


"Warning: Failed propType:Invalid prop 'source' supplied to 'Image'

I'm going through the React Native tutorial with Expo on iOS and whenever I import an image I get the warning, ""Warning: Failed propType:Invalid prop 'source' supplied to 'Image'" and the image doesn't appear on the screen.
For example from https://reactnative.dev/docs/intro-react
import React from 'react';
import { Text, View, Image } from 'react-native';

export default function CatApp() {
  return (
    <View>
      <Image
        source="https://reactnative.dev/docs/assets/p_cat1.png"
        style={{width: 200, height: 200}}
      />
      <Text>Hello, I am your cat!</Text>
    </View>
  );
}

I was able to get the image to appear by adding a uri property as suggested in the accepted answer here: https://stackoverflow.com/questions/36460827/react-native-failed-proptype-on-image-component/36460928
export default function CatApp() {
  return (
    <View>
      <Image
        source={{uri: "https://reactnative.dev/docs/assets/p_cat1.png"}}
        style={{width: 200, height: 200}}
      />
      <Text>Hello, I am your cat!</Text>
    </View>
  );
}

Is there something I'm missing? If not, I'd be glad to make the PR to fix it.

Hi @MattGoldwater, thank you for reporting this! The solution you have posted is correct, feel free to make it into a PR. I would be nice if you can edit also 0.62 versioned page beside current/next one, because 0.62 docs are the default selected version (when user enters the website).


Page load slow, plus images flicker before transition

Some of the styling on the page takes a while to load now we have added the nivo slider to our wordpress site.
Also, the current image flickers before the next image transitions in.
Please offer support in how to fix.
Thanks so much!

I'm having this issue as well. Images flicker before the transition. Any word on what this is or how to fix it?

We ended up re-sizing all the images to the exact size of the player and reducing their quality so load time was quicker. This seems to have fixed it!


Project License

Hi,
I am interested in using this plugin in one of my project. I have searched for license info in the repo but I can't find it in the usual locations.
Adding the license the project is published under would help me to know if using this plugin is an option.
Could you add license info into the repo?
Thanks!

I believe that @riderx has the sole power to decide on the license.
Thank you for bringing this issue to our attention


Roadmap?

What's the expected ETA for supporting activatable WinRT components and XAML?

Sometime in the future, but not next month. They are features we are working on.


Homematic operation mode automation

Hi there,
currently i'm trying to set the operation mode of a homematic thermostat to manual in my automation config. This is working over the ui but not in the automation script:
  action:
  - data:
      entity_id: climate.int0000001
      operation_mode: manual
      temperature: 15
    service: climate.set_temperature

This will correctly set the temperature to 15° but the operation mode is still auto (which was before).
Am I miss something?

@tschechniker
You need to call climate.set_operation_mode
    - service: climate.set_operation_mode
      data:
        operation_mode: boost
        entity_id: climate.int0000001

The service climate.set_temperature changes not the operation mode. It can just set the temperature.


Persistence stopped working (not Redis, file-storage)

Verify latest release

[X] I verified that the issue exists in the latest chatgpt release

Verify webapp is working

[X] I verify that the ChatGPT webapp is working properly for this account.

Environment details
Running in Docker for Linux
Describe the Bug
Hi!
Before upgrading to the latest release, i was still running on version 4.4.0
My solution for persistence was storing the response received from the chatgpt api on the hard drive via JSON.stringyfy(response).
It worked fine, i was able to use parentmessageId to continue the last conversation, even after restarting the app, just by deserializing the file from the hard drive.
Now, it looks like the parentMessageId is loosing its context, i am unable to understand if this is a local problem or one with the package, but i figured i ask here just in case, since the issue did not exist in the previous version.
Even mid-conversation, the api seems to loose the conversation context, is this a problem with gpt-turbo?
Regards

I had a similar issue but realised I was instantiating a new instance of the ChatGPTAPI each time I made a new request, which was causing the issue
Just wondering if you are instantiating it more than once?

Hi Richard! Thanks for the reply.
I di create a new instance after every docker-restart, which happens sometimes, but that shouldn't be an issue since the parenrmessageid should work cross-instance, e.g. the CLI also has a continue option and continueing in a new instance worked on the older version of the package.
In short, it was possible to continue the conversation after an update/restart/downtime, based on the parenrmessageid.

@yavuzitconsulting That's interesting 🤔. Just to clarify, does ChatGPT lose the context of the conversation after an update/restart/downtime? Or does it lose the context after every request?

The default stores messages in memory, so if you want to persist conversation state across update/restart/downtime, you need to use a persistent message store. The readme has examples of this as well as demos/demo-persistence.ts.
You can use any keyv database adaptor or fully take control and override the getMessageById and upsertMessage options to store them however you want.

just to note, since this bug was closed without comment.
i do persist the state, as described in my bug description, you just commented that i have to persist the state and then closed the issue which makes no sense at all all.
i also described how i persist the state, and that this way of persisting worked in 4.4.0 but does not in the current version.


✏📘 [PUML Documentation] - Update PUML Documentation

Documentation Types

[X] New
[ ] Expansion
[ ] Correction

Requested Documentation
As an AaC Developer, I want to update the gen-puml documentation, so that it accurately captures and explains the gen-puml plugin for end users.

[x] Update gen-puml plugin page to utilize core plugin documentation layout so consistent information is provided.
[x] Include screen shots of executing commands.
[x] Include screen shots of example output diagrams.
[x] Include reference sections on the four diagram types produced.
[ ] Ensure publication to repository pages.

Reference Issues
#1
#4
#5
#6
#8
#9
#10

Publication will not happen until the pypi posting is valid, because a local build is not useable for documentation builds it seems. So, will have a small follow-on task that corrects/removes all of the local builds in the pipeline and swaps to a pypi pip install of the package after this PR merges in and pypi deployment should then be properly enabled.


Clean up display API on GameChip

Need to clean up API on GameChip and IGameChip

[ ] Display should be Display(visible) and return the full resolution and take into account the overscan
[ ] Remove overscan (it's just confusing)

Removing DisplaySize(), VisibleBounds() and OverscanBorder() from the GameChip.

This has been fixed.


/upload not working

server refuses to connect after i upload log file

It should be working - are you running it locally or using the hosted version?

I have the same problem, running locally


test(rpc): Add Rust tests for lightwalletd sync from Zebra

Motivation
We want to run full sync and quick sync integration tests for lightwalletd.
We want to merge PR #4068 first, to unblock some other work.
Depends-On: #4068
CI Commands
You'll need to update the cache paths to match the CI paths.
To test full sync:
export ZEBRA_CACHED_STATE_PATH="$HOME/.cache/zebra"
export RUST_LOG="info"

cargo test -- --ignored --nocapture  lightwalletd_full_sync

To test quick update sync:
export ZEBRA_CACHED_STATE_PATH="$HOME/.cache/zebra"
export LIGHTWALLETD_DATA_DIR="$HOME/.cache/lightwalletd"
export RUST_LOG="info"

cargo test -- --ignored --nocapture  lightwalletd_update_sync

Manual Testing
To manually test all the lightwalletd integration tests in series (which avoids state conflicts), use:
export ZEBRA_CACHED_STATE_PATH="$HOME/.cache/zebra"
export LIGHTWALLETD_DATA_DIR="$HOME/.cache/lightwalletd"
export RUST_LOG="info"

cargo test -- --ignored --nocapture  lightwalletd_test_suite

Solution

Create a lightwalletd full sync test
Create a lightwalletd cached state update test

Details:

Create a LightwalletdTestType enum
Make the lightwalletd integration test take a test type
Configure lightwalletd tests based on the test type
Add checks for each LightwalletdTestType
Create test functions that run each lightwalletd test type
Fail if the state doesn't match the test type

Related Cleanups:

Remove obsolete kill_on_error() in the lightwalletd test
Add a sub-directory for lightwalletd test state
Move failure messages into their own module

Closes #3511
Closes #4166
Review
@jvff is probably be the best person to review this PR.
@gustavovalverde this PR should work in CI if you use the commands above.
(It's draft because I haven't finished testing it yet.)
Reviewer Checklist

[ ] Code implements Specs and Designs
[ ] Tests for Expected Behaviour
[ ] Tests for Errors

Follow Up Work

#3926
#4165
#4167

@mergifyio update

When rebasing on main, I removed a bunch of duplicate code.
The LightwalletdTestType enum names are still a bit messy, but I'd like to fix that later.

Failed due to #4234:

Error: buildx failed with: error: failed to solve: failed to fetch oauth token: unexpected status: 401 Unauthorized


Use AngularJS to attach element to DOM (replaces plain JS code).

It's better to relay on AngularJS as there is no guarantee that changes made outside [AngularJS] will be digested.
Regards

Remove generated element on scope's $destroy (inspired by #783)

It doesn't really need to be digested.


Project internationalization

Translate project pages to different languages (e.g. ru, en). You can achieve this using following package: react-i18next.
https://react.i18next.com/guides/quick-start

Resolved at https://github.com/menkuichan/super-enigma-fe/pull/31


feat: add gaming sdk api

milestone 2
adds chainsafe gaming API call to plugin.
https://www.notion.so/chainsafe/Web3js-Marketplace-Plugin-e52134db8223409b9003323924cd1b3a

tests failing due to insufficient funds, might need to manually run contract tests.


Bug: Tabbing away from a Tooltip inside a Dialog moves focus to the Dialog root

Bug report
Current Behavior
When a tooltip is inside a dialog, tabbing away from the tooltip button moves focus back to the dialog root instead of the next focusable element in the dialog.
In this video made using the reproduction below you can see that, when I tab away from the Tooltip button, focus skips After tooltip entirely and goes straight to the dialog root.
At the end of the video, I press Escape before tabbing away from the tooltip. This closes the tooltip and then focus moves as expected.
https://github.com/user-attachments/assets/60f6d249-ca24-43f8-a612-7ec937326f43
Expected behavior
When you press tab while focused on a tooltip button, focus should move to the next focusable element.
Reproducible example
Reproduction in code sandbox
Suggested solution
I'm not familiar enough with the codebase to make a definite suggestion here. It might have something to do with react-focus-lock?
Additional context
When tabbing away from the tooltip button, the focusout event that fires does indeed have a relatedTarget set to the next element in the tab order. So something in the Dialog component is likely listening to that and manually changing the focus.
Your environment

Software
Name(s)
Version

Radix Package(s)
react-dialog, react-tooltip
1.1.2, 1.1.3

React
n/a
18.3

Browser
Arc
Version 1.65.0 (54911) -- Chromium Engine Version 130.0.6723.59

Assistive tech
n/a
n/a

Node
n/a
20.9

npm/yarn
bun
1.0.7

Operating System
MacOS
Sonoma 14.4.1

We have the same issue, instead of tabbing through the focusable elements it tabs through the first two elements (like in the video) and then tabs out to the dialog root.


Create Level 3 Collection Log

Hides all the log slots and categories that level 3's cannot complete.

Your plugin manifest should be placed in the plugins/ directory, and its filename should be all lowercase and with words separated by hyphens, not spaces. You can look at any of the existing plugin manifest files for reference

My bad, yesterday afternoon I had never used github or java so my brain was a bit fried from all the instructions I've followed everywhere haha. Should be in the right place now.

This has been failing to build for nearly 2 months with no follow-up.


run terraform plugin for all terraform state commands (not just `stat…

Overview
This PR makes sure the terraform plugin is run for all terraform state commands.
Type of change

[ ] Created a new plugin
[X] Improved an existing plugin
[ ] Fixed a bug in an existing plugin
[ ] Improved contributor utilities or experience

Related Issue(s)

Resolves: #
Relates: #

How To Test
Run terraform state show '<any terraform resource id in your state>' or terraform state pull|push`.
Changelog
The terraform plugin now kicks in on all terraform state subcommands, not just terraform state list.

Any chance we could get this merged in the near future?

Apologies for the delay on this @frans-otogone ! This will go out with the next 1Password CLI release.


use golang 1.7.5 for building man pages

- What I did
Updated man/Dockerfile to use golang 1.7.5 when building man pages. This is needed because builds of debian packages are failing during man page generation because the golang installed is version 1.6 which does not have context package:
docker run --rm \
-v /go/src/github.com/docker/docker:/go/src/github.com/docker/docker/ \
docker-manpage-dev
cli/command/plugin/upgrade.go:5:2: cannot find package "context" in any of:
	/go/src/github.com/docker/docker/vendor/context (vendor tree)
 	/usr/lib/go/src/context (from $GOROOT)
 	/go/src/context (from $GOPATH)
 	/manvendor/src/context

- How I did it
Using the official docker image of golang https://hub.docker.com/_/golang/
- How to verify it
$ make manpages

- Description for the changelog

N/A
- A picture of a cute animal (not mandatory but encouraged)
🐗

/cc @cpuguy83 @vieux

LGTM ping @thaJeztah

We need to fix https://github.com/docker/docker/issues/28205 so this doesnt break.

Aaaaaah go-imports strikes again.
We need to fix the code.

@cpuguy83 https://github.com/docker/swarmkit/pull/1926 for swarmkit, I'll do one for docker/docker too 👼

armhf, ppc64le, s390x, and most likely aarch64 are going to need a change as well. As not all of those have golang images, it might make more sense to just dl go like in the dockerfiles.

Tried to get the man/Dockerfile.armhf going but there are complications...the https://golang.org/dl/ download for linux-armv6l looks like go is compiled to be dynamically linked to /lib/ld-linux-armhf.so.3 which exists in armhf/debian:jessie docker image but not armhf/alpine:3.4 docker image, so updated to be FROM armhf/debian:jessie

@andrewhsu yes unfortunately all the Go downloads are linked to glibc. On amd64 you can use the compat libc in Alpine but I don't think that will work for other architectures.

@andrewhsu I'm not sure if you have access to p and z machines, but here are the changes for those Dockerfiles https://github.com/docker/docker/compare/master...tophj-ibm:fix-manpages-p-z

@tophj-ibm cool, thanks for that! can you create a separate PR for that? we need to roll on these changes for x86_64 and armhf first since they are needed quite soon.

@andrewhsu yeah sure

windows failures are unrelated


fix: prioritize important styles

When two selectors would set a property for an element, if one of those selectors is important then it should take precedence over non-important selector. If they are both important, or neither are important, then specificity is enough.
I observed this issue when comparing generated emails against the output of the node inline-css library. Here's a simple playground input/output that demonstrates the problem:

    Big Text

    Big Text

Note that if you reverse the order of the rule declarations, you get the correct behavior.

Hi @Stranger6667 — very glad you were able to release 0.14.2 on Monday!
Here's another patch for you — please let me know if this seems reasonable to you and whether there's anything I can do to make it better.

Hi @tborg
Thank you so much for fixing this :) Absolutely reasonable! I am going to make a new patch release soon


Minor documentation corrections

This is first PR to the project.  It consists of a minor documentation corrections.  I corrected some minor typos, spelling and English grammar.  I also updated image links to be consistent, as some of the links were not relative paths which causes issues with offline Markdown previews.

:white_check_mark: Build TheIdServer 1.0.0-roblthegreat-doc-cleanup1-0156 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/897c7cff9c by @roblthegreat)

@roblthegreat hey, thanks for the PR, can you please open a issue related to this PR please ?

Related Issue #160 has been created, per request.  Let me know if you need anything else.

:white_check_mark: Build TheIdServer 1.0.0-roblthegreat-doc-cleanup.1+156.build.503 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/897c7cff9c by @roblthegreat)

@roblthegreat Do you wanna be a member of the team ?


Aye.PullTime not working for me

I have Aye and Aye.PullTime and it's no longer displaying anything for me. I tested in LFR and I only managed to get the prepull to show up once after a dBm timer was set, but I also have ninja pulls enabled. I only noticed the issue this past Monday. Is it because of the new version? How do I debug and fix it, I've tried reinstalling both and nothing seems to work.

Edit: Apparently my WoW Cache was corrupted so deleting  WoW\Cache fixed the issue I was having.


BUG: periodically saving collection bloats db storage size

Description
This bug happens when saving a collection in a periodic manner like the example below.
# Create the DB and collection...
for _ in range(300):
    records = Record.many_random(dimension=512, len=100)
    collection.insert_many(records)
    db.save_collection("storage", collection)

This caused unflushed dirty IO buffers to bloats the database folder to an amount unimaginable 🤯
From 70MB database size to 10GB.
Read the discussion https://github.com/oasysai/oasysdb/discussions/77 for more context about what is happening.

The methods added in #84, Database.flush and Database.async_flush don't solve this issue. It seems that the correct approach to fix this issue is to store the collection in it's own file and only use Sled to store the reference to the file.


Bump

Notification
infrastructure
If you're reading this then Peacock has successfully read a message from a pr and sent it :)

testing testing

testing testing

testing testing

failed validate PR body: 3 team fields found in PR body, should be 2

failed validate PR body: 3 team fields found in PR body, should be 2

team name Team1 does not exist in feathers.yaml:
[devs product]

failed to parse email address hello for team devs: mail: missing '@' or angle-addr

failed to parse email address hello for team devs: mail: missing '@' or angle-addr

failed to parse email address "hello" for team "devs": mail: missing '@' or angle-addr

Sucessfully validated 2 messages.
2/2 teams to notify

Sucessfully validated 2 messages.
2/2 teams in config to notify

Sucessfully validated 2 messages
2/2 teams in config to notify

Sucessfully validated 2 messages
2/2 teams in config to notify

Message [0/2]
Teams:[devs]
Content:In this release blah blah blah
More blah blah blah

this is a list
second list

Testing Testing
Message [1/2]
Teams:[product]
Content:This message is for other people so is different

Sucessfully validated 2 messages
2/2 teams in config to notify

Message [1/2]
Teams: [devs]
Content:
In this release blah blah blah
More blah blah blah

this is a list
second list

Testing Testing
Message [2/2]
Teams: [product]
Content:
This message is for other people so is different

Sucessfully validated 2 messages
2/2 teams in config to notify
Message [1/2]
Teams: [devs]
Content:
In this release blah blah blah
More blah blah blah

this is a list
second list

Testing Testing
Message [2/2]
Teams: [product]
Content:
This message is for other people so is different

Sucessfully validated 2 messages
3/2 teams in config to notify
Message [1/2]
Teams: [devs product]
Content:
In this release blah blah blah
More blah blah blah

this is a list
second list

Testing Testing
Message [2/2]
Teams: [product]
Content:
This message is for other people so is different

Sucessfully validated 2 messages
2/2 teams in config to notify
Message [1/2]
Teams: [devs]
Content:
In this release blah blah blah
More blah blah blah

this is a list
second list

Testing Testing
Message [2/2]
Teams: [product]
Content:
This message is for other people so is different

Sucessfully validated 2 messages
2/2 teams in config to notify
Message [1/2]
Teams: [devs]
Content:
In this release blah blah blah
More blah blah blah

this is a list
second list

Testing Testing
Message [2/2]
Teams: [product]
Content:
This message is for other people so is different

Sucessfully validated 2 messages
2/2 teams in config to notify

Message [1/2]
Teams: [devs]
Content:
In this release blah blah blah
More blah blah blah

this is a list
second list

Testing Testing

Message [2/2]
Teams: [product]
Content:
This message is for other people so is different

Sucessfully validated 1 messages
1/1 teams in config to notify

Message [1/1]
Team: infrastructure
Content:
If you’re reading this then Peacock has successfully read a message from a pr and sent it :)

Validation
Sucessfully validated 1 messages
1/1 teams in config to notify

Message [1/1]
Team: infrastructure
Content:
If you’re reading this then Peacock has successfully read a message from a pr and sent it :)

Validation
Sucessfully validated 1 messages
1/1 teams in config to notify

Message [1/1]
Team: infrastructure
Content:
If you’re reading this then Peacock has successfully read a message from a pr and sent it :)

Validation
Sucessfully validated 1 messages
1/1 teams in config to notify

Message [1/1]
Team: infrastructure
Content:
If you’re reading this then Peacock has successfully read a message from a pr and sent it :)

Validation
Sucessfully validated 1 message(s)
1/1 teams in config to notify

Message [1/1]
Team: infrastructure
Content:
If you’re reading this then Peacock has successfully read a message from a pr and sent it :)

Validation
Sucessfully parsed 1 message(s)
1/1 teams in config to notify

Message [1/1]
Team: infrastructure
Content:
If you’re reading this then Peacock has successfully read a message from a pr and sent it :)

Validation
Sucessfully parsed 1 message(s)
1/1 teams in config to notify

Message [1/1]
Team: infrastructure
Content:
If you’re reading this then Peacock has successfully read a message from a pr and sent it :)

failed to parse slack channel ID "C02BA9QHMD" for team "infrastructure"

Validation
Successfully parsed 1 message(s)
1/1 teams in config to notify

Message [1/1]
Team: infrastructure
Content:
If you’re reading this then Peacock has successfully read a message from a pr and sent it :)

Validation
Successfully parsed 1 message(s)
1/1 teams in config to notify

Message [1/1]
Team: infrastructure
Content:
If you’re reading this then Peacock has successfully read a message from a pr and sent it :)

Validation
Successfully parsed 3 message(s)
3/3 teams in config to notify

Message [1/3]
Team: infrastructure
Content:
If you’re reading this then Peacock has successfully read a message from a pr and sent it :)

Message [2/3]
Team: ml
Content:
If you’re reading this then Peacock has successfully read a message from a pr and sent it :)

Message [3/3]
Team: product
Content:
If you’re reading this then Peacock has successfully read a message from a pr and sent it :)

Validation
Successfully parsed 3 message(s)
3/3 teams in config to notify

Message [1/3]
Team: infrastructure
Contact Type: slack
Content:
If you’re reading this then Peacock has successfully read a message from a pr and sent it :)

Message [2/3]
Team: ml
Contact Type: slack
Content:
If you’re reading this then Peacock has successfully read a message from a pr and sent it :)

Message [3/3]
Team: product
Contact Type: slack
Content:
If you’re reading this then Peacock has successfully read a message from a pr and sent it :)

no messages found in markdown

Error: failed to parse messages from pull request: no messages found in markdown

Validation
Successfully parsed 3 message(s)
3/3 teams in config to notify

Message [1/3]
Team: infrastructure
Contact Type: slack
Content:
If you're reading this then Peacock has successfully read a message from a pr and sent it :)

Message [2/3]
Team: ml
Contact Type: slack
Content:
Here are the changes:

Fixes
Features
bugs
If you're reading this then Peacock has successfully read a message from a pr and sent it :)

Message [3/3]
Team: product
Contact Type: slack
Content:
If you're reading this then Peacock has successfully read a message from a pr and sent it :)

Error: failed to parse messages from pull request: no teams found in message 1

Error: failed to init handlers: contact type "t" found in config but no handler has been initialised, check required flags have been passed for this type

Error: failed to init handlers: contact type "slack" found in config but no handler has been initialised, check required flags have been passed for this type

Error: failed to parse messages from pull request: no messages found in markdown

Validation
Successfully parsed 3 message(s)
3/3 teams in config to notify

Message [1/3]
Team: infrastructure
Contact Type: slack
Content:
If you're reading this then Peacock has successfully read a message from a pr and sent it :)

Message [2/3]
Team: ml
Contact Type: slack
Content:
Here are the changes:

Fixes
Features
bugs

If you're reading this then Peacock has successfully read a message from a pr and sent it :)

Message [3/3]
Team: product
Contact Type: slack
Content:
If you're reading this then Peacock has successfully read a message from a pr and sent it :)

Validation
Successfully parsed 3 message(s)
3/3 teams in config to notify

Message [1/3]
Team: infrastructure
Contact Type: slack
Content:
If you're reading this then Peacock has successfully read a message from a pr and sent it :)

Message [2/3]
Team: ml
Contact Type: email
Content:
Here are the changes:

Fixes
Features
bugs

If you're reading this then Peacock has successfully read a message from a pr and sent it :)

Message [3/3]
Team: product
Contact Type: slack
Content:
If you're reading this then Peacock has successfully read a message from a pr and sent it :)


Tests: add tests for extension methods for CollectionBuilder{byte} structure

What I did

Add a testing method for CollectionBuilderExtensions.AppendLiteral(this CollectionBuilder<byte>, ReadOnlySpan<char>) method.
Fix a bug in CollectionBuilderExtensions.ToSystemString(this CollectionBuilder<byte>) method.

In this PR, all changes are made to CollectionBuilder<T> structure and CollectionBuilderExtensions class, and testing classes for those types.
Tests for those types were successful (with command below), so it is safe to merge this PR.
dotnet test --filter "CollectionBuilder"


How to modify the selected data of the table from the context menu?

I am trying to modify some selected data from the table. To do this, I have an option in the context menu (for example multiply x2). So what I want to do is retrieve the selected data (each cell with its x-axis, y-axis and value), be able to modify them and put the result in the same position(x,y). I have been looking at how to do that, but I have seen that it is quite complicated since I have not found a method that gives me that full data.

getjson (): gives me the data, but does not give me the x and y positions.
selectedCell: it returns me where my selection begins and where it ends, but it does not give me the structure, that is, I have no idea in what order the values are within that selection.

Is there any way to easily recover this data with its positions? Can someone help me on how to do that? Thanks a lot.

If you have x1, y1, x2, y2 you can do a loop to get all select cells. Another way is to use getData(true) - this will bring you the data of the selected cells only.

I have created the following method that uses various existing JExcel methods to gather the cell data. And what it does is return an array with the selected cells. In each of them comes the information of the X axis. Y axis, title of the column in which it is located and the value of the cell. Hope that helps others. To save the data again in the table you just have to use the method "setValueFromCoords (x, y, value)":
`    getCellData(obj) { //FIXME: seguir desde aquí. Este método no funciona
    let array = []
    class CellInfo {
        constructor(colHeader, xAxis, yAxis, value) {
            this.colHeader = colHeader;
            this.xAxis = xAxis;
            this.yAxis = yAxis;
            this.value = value;
        }
    }

    let json = obj.getJson(true); // devuelve un array de objetos con ejex y valor
    let selectedRows = obj.getSelectedRows();//devuelve array de filas. Dentro usamos la propiedad sectionRowIndex para el eje Y

    for (let i = 0; i < json.length; i++) {

        let y = selectedRows[i].sectionRowIndex; // aquí tenemos el eje y

        for (let [key, value] of Object.entries(json[i])) {

            let header = obj.getHeader(key);
            let c = new CellInfo(header, parseInt(key, 10), y, value)

            array.push(c);
        }
    }
    console.log('array :>> ', array);
    return array;
}`

it returns an array like this:


Wrong package name and Python module created

Describe the bug
The package names and @PythonModule annotations of the created stubs are wrong. For example, the stub for the Image class of Safe-DS starts with
@PythonModule("safeds.data.image.containers._image")
package safeds.data.image.containers.Image

It should instead be
@PythonModule("safeds.data.image.containers")
package safeds.data.image.containers

and since the package name and @PythonModule are then identical, it can be shortened to just
package safeds.data.image.containers

To Reproduce

Create stubs for Safe-DS (adjust the source path): safe-ds-stubgen -o "out" -nc -s "../library/src" --docstyle NUMPYDOC -v
Open out/safeds/data/image/containers/_image/image.sdsstub

Expected behavior

The class name should not be part of the package name.
For internal modules, no stubs should be created, i.e. the @PythonModule should never include parts that begin with an underscore. In this case, the class Image is reexported, so naturally stubs should still be created, but under a different package/Python module.

Screenshots (optional)
No response
Additional Context (optional)
No response

In data__api.json, all entries of reexported_by are also empty.

Works when using an absolute path for the -s argument, making this a duplicate of #125.


Fix block data transfer

Now correctly adds 12 when storing R15 (PC)
Inverts iteration order when using decrementing. From documentation:

The lowest register also gets transferred to/from the lowest memory address
So we should invert the order when decrementing otherwise we would store/save in inverse order.

Done! Should be ready @guerinoni


Error on Google Map Display

The map for the home page currently does not work. The following error is shown here:

So it looks like the map problem was fixed by running  heroku run rake geocode:all CLASS=Article --app blackopswiki from the development environment. The map now works

Now that the map is restored, the remaining tasks involve:

[ ] fixing the geocoder not adding an address to the case upon save
[ ] Adjusting the Google Maps implementation so that the lack of an address does not result in an overall error to the map

The map appears to be missing again...

Looks like it. Plus the geocoding rake task didn't fix the job this time.
On Sat, Apr 15, 2017 at 2:44 PM, campgurus<EMAIL_ADDRESS>wrote:

The map appears to be missing again...
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/BOWiki/BOW/issues/883#issuecomment-294311085, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAA0xeSJcMQOC2QtHQFfd_D8BFfVQ7Nzks5rwRAkgaJpZM4M6bDx
.

--
Mark<EMAIL_ADDRESS>blog.grandkru.com
github.com/trystant

It looks like the state model in full_address is causing the error. I wanted to replace #{state} with #{state.ansi_code}, and while the map works now, I'm having spec problems. I believe I'm going to push up the fix to get the map working and then figure out the spec problem.

We can close this, since the map is working.


ac-build-go-live

Docs Build status updates of commit 1e6a0b1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded

msteams-platform/concepts/bots/bots-test.md
:white_check_mark:Succeeded

msteams-platform/includes/landing-page.html
:white_check_mark:Succeeded

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit 0e7959a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded

msteams-platform/concepts/bots/bots-test.md
:white_check_mark:Succeeded

msteams-platform/concepts/tabs/tabs-context.md
:white_check_mark:Succeeded

msteams-platform/includes/landing-page.html
:white_check_mark:Succeeded

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit 2e63ef7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded

msteams-platform/concepts/bots/bots-test.md
:white_check_mark:Succeeded

msteams-platform/concepts/connectors/connectors-creating.md
:white_check_mark:Succeeded

msteams-platform/concepts/tabs/tabs-context.md
:white_check_mark:Succeeded

msteams-platform/includes/landing-page.html
:white_check_mark:Succeeded

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit 5488864:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded

msteams-platform/concepts/bots/bots-test.md
:white_check_mark:Succeeded

msteams-platform/concepts/connectors/connectors-creating.md
:white_check_mark:Succeeded

msteams-platform/concepts/messaging-extensions/create-extensions.md
:white_check_mark:Succeeded

msteams-platform/concepts/tabs/tabs-context.md
:white_check_mark:Succeeded

msteams-platform/includes/landing-page.html
:white_check_mark:Succeeded

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit 36ff546:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded

msteams-platform/assets/images/icebreaker.PNG
:white_check_mark:Succeeded

msteams-platform/assets/images/stickers.PNG
:white_check_mark:Succeeded

msteams-platform/concepts/bots/bots-test.md
:white_check_mark:Succeeded

msteams-platform/concepts/connectors/connectors-creating.md
:white_check_mark:Succeeded

msteams-platform/concepts/messaging-extensions/create-extensions.md
:white_check_mark:Succeeded

msteams-platform/concepts/tabs/tabs-context.md
:white_check_mark:Succeeded

msteams-platform/includes/landing-page.html
:white_check_mark:Succeeded

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit 480e690:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/publishing/application-certification.md
:warning:Warning

Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded

msteams-platform/assets/icons/share-to-teams-icon.png
:white_check_mark:Succeeded

msteams-platform/assets/images/icebreaker.PNG
:white_check_mark:Succeeded

msteams-platform/assets/images/self-assessment.png
:white_check_mark:Succeeded

msteams-platform/assets/images/share-to-teams-icon.png
:white_check_mark:Succeeded

msteams-platform/assets/images/share-to-teams-popup-edu.png
:white_check_mark:Succeeded

msteams-platform/assets/images/share-to-teams-popup.png
:white_check_mark:Succeeded

msteams-platform/assets/images/stickers.PNG
:white_check_mark:Succeeded

msteams-platform/concepts/bots/bot-conversations/bots-conv-proactive.md
:white_check_mark:Succeeded

msteams-platform/concepts/bots/bots-test.md
:white_check_mark:Succeeded

msteams-platform/concepts/calls-and-meetings/call-notifications.md
:white_check_mark:Succeeded

msteams-platform/concepts/connectors/connectors-creating.md
:white_check_mark:Succeeded

msteams-platform/concepts/messaging-extensions/create-extensions.md
:white_check_mark:Succeeded

msteams-platform/concepts/tabs/tabs-context.md
:white_check_mark:Succeeded

msteams-platform/includes/landing-page.html
:white_check_mark:Succeeded

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded

msteams-platform/share-to-teams.md
:white_check_mark:Succeeded

msteams-platform/publishing/application-certification.md

Line 10: [Warning] Invalid file link:(~/platform/publishing/apps-publish.md).

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

Docs Build status updates of commit bea777a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded

msteams-platform/assets/icons/share-to-teams-icon.png
:white_check_mark:Succeeded

msteams-platform/assets/images/icebreaker.PNG
:white_check_mark:Succeeded

msteams-platform/assets/images/self-assessment.png
:white_check_mark:Succeeded

msteams-platform/assets/images/share-to-teams-icon.png
:white_check_mark:Succeeded

msteams-platform/assets/images/share-to-teams-popup-edu.png
:white_check_mark:Succeeded

msteams-platform/assets/images/share-to-teams-popup.png
:white_check_mark:Succeeded

msteams-platform/assets/images/stickers.PNG
:white_check_mark:Succeeded

msteams-platform/concepts/bots/bot-conversations/bots-conv-proactive.md
:white_check_mark:Succeeded

msteams-platform/concepts/bots/bots-test.md
:white_check_mark:Succeeded

msteams-platform/concepts/calls-and-meetings/call-notifications.md
:white_check_mark:Succeeded

msteams-platform/concepts/connectors/connectors-creating.md
:white_check_mark:Succeeded

msteams-platform/concepts/messaging-extensions/create-extensions.md
:white_check_mark:Succeeded

msteams-platform/concepts/tabs/tabs-context.md
:white_check_mark:Succeeded

msteams-platform/includes/landing-page.html
:white_check_mark:Succeeded

msteams-platform/publishing/application-certification.md
:white_check_mark:Succeeded

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded

msteams-platform/share-to-teams.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit 6ab7ecd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded

msteams-platform/assets/icons/share-to-teams-icon.png
:white_check_mark:Succeeded

msteams-platform/assets/images/icebreaker.PNG
:white_check_mark:Succeeded

msteams-platform/assets/images/self-assessment.png
:white_check_mark:Succeeded

msteams-platform/assets/images/share-to-teams-icon.png
:white_check_mark:Succeeded

msteams-platform/assets/images/share-to-teams-popup-edu.png
:white_check_mark:Succeeded

msteams-platform/assets/images/share-to-teams-popup.png
:white_check_mark:Succeeded

msteams-platform/assets/images/stickers.PNG
:white_check_mark:Succeeded

msteams-platform/concepts/bots/bot-conversations/bots-conv-proactive.md
:white_check_mark:Succeeded

msteams-platform/concepts/bots/bots-test.md
:white_check_mark:Succeeded

msteams-platform/concepts/calls-and-meetings/call-notifications.md
:white_check_mark:Succeeded

msteams-platform/concepts/connectors/connectors-creating.md
:white_check_mark:Succeeded

msteams-platform/concepts/messaging-extensions/create-extensions.md
:white_check_mark:Succeeded

msteams-platform/concepts/tabs/tabs-context.md
:white_check_mark:Succeeded

msteams-platform/includes/landing-page.html
:white_check_mark:Succeeded

msteams-platform/publishing/application-certification.md
:white_check_mark:Succeeded

msteams-platform/resources/design/components/color.md
:white_check_mark:Succeeded

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded

msteams-platform/share-to-teams.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit b583fbd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded

msteams-platform/assets/icons/share-to-teams-icon.png
:white_check_mark:Succeeded

msteams-platform/assets/images/icebreaker.PNG
:white_check_mark:Succeeded

msteams-platform/assets/images/self-assessment.png
:white_check_mark:Succeeded

msteams-platform/assets/images/share-to-teams-icon.png
:white_check_mark:Succeeded

msteams-platform/assets/images/share-to-teams-popup-edu.png
:white_check_mark:Succeeded

msteams-platform/assets/images/share-to-teams-popup.png
:white_check_mark:Succeeded

msteams-platform/assets/images/stickers.PNG
:white_check_mark:Succeeded

msteams-platform/concepts/bots/bot-conversations/bots-conv-proactive.md
:white_check_mark:Succeeded

msteams-platform/concepts/bots/bots-test.md
:white_check_mark:Succeeded

msteams-platform/concepts/calls-and-meetings/call-notifications.md
:white_check_mark:Succeeded

msteams-platform/concepts/connectors/connectors-creating.md
:white_check_mark:Succeeded

msteams-platform/concepts/messaging-extensions/create-extensions.md
:white_check_mark:Succeeded

msteams-platform/concepts/tabs/tabs-context.md
:white_check_mark:Succeeded

msteams-platform/includes/landing-page.html
:white_check_mark:Succeeded

msteams-platform/publishing/application-certification.md
:white_check_mark:Succeeded

msteams-platform/resources/design/components/color.md
:white_check_mark:Succeeded

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded

msteams-platform/share-to-teams.md
:white_check_mark:Succeeded

msteams-platform/whats-new.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit 161f774:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded

msteams-platform/assets/icons/share-to-teams-icon.png
:white_check_mark:Succeeded

msteams-platform/assets/images/icebreaker.PNG
:white_check_mark:Succeeded

msteams-platform/assets/images/self-assessment.png
:white_check_mark:Succeeded

msteams-platform/assets/images/share-to-teams-icon.png
:white_check_mark:Succeeded

msteams-platform/assets/images/share-to-teams-popup-edu.png
:white_check_mark:Succeeded

msteams-platform/assets/images/share-to-teams-popup.png
:white_check_mark:Succeeded

msteams-platform/assets/images/stickers.PNG
:white_check_mark:Succeeded

msteams-platform/concepts/bots/bot-conversations/bots-conv-proactive.md
:white_check_mark:Succeeded

msteams-platform/concepts/bots/bots-test.md
:white_check_mark:Succeeded

msteams-platform/concepts/calls-and-meetings/call-notifications.md
:white_check_mark:Succeeded

msteams-platform/concepts/connectors/connectors-creating.md
:white_check_mark:Succeeded

msteams-platform/concepts/messaging-extensions/create-extensions.md
:white_check_mark:Succeeded

msteams-platform/concepts/tabs/tabs-context.md
:white_check_mark:Succeeded

msteams-platform/includes/landing-page.html
:white_check_mark:Succeeded

msteams-platform/publishing/application-certification.md
:white_check_mark:Succeeded

msteams-platform/resources/design/components/color.md
:white_check_mark:Succeeded

msteams-platform/resources/dev-preview/developer-preview-features.md
:white_check_mark:Succeeded

msteams-platform/resources/dev-preview/developer-preview-intro.md
:white_check_mark:Succeeded

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded

msteams-platform/share-to-teams.md
:white_check_mark:Succeeded

msteams-platform/whats-new.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit 26f3751:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded

msteams-platform/assets/icons/share-to-teams-icon.png
:white_check_mark:Succeeded

msteams-platform/assets/images/icebreaker.PNG
:white_check_mark:Succeeded

msteams-platform/assets/images/self-assessment.png
:white_check_mark:Succeeded

msteams-platform/assets/images/share-to-teams-icon.png
:white_check_mark:Succeeded

msteams-platform/assets/images/share-to-teams-popup-edu.png
:white_check_mark:Succeeded

msteams-platform/assets/images/share-to-teams-popup.png
:white_check_mark:Succeeded

msteams-platform/assets/images/stickers.PNG
:white_check_mark:Succeeded

msteams-platform/concepts/bots/bot-conversations/bots-conv-proactive.md
:white_check_mark:Succeeded

msteams-platform/concepts/bots/bots-test.md
:white_check_mark:Succeeded

msteams-platform/concepts/calls-and-meetings/call-notifications.md
:white_check_mark:Succeeded

msteams-platform/concepts/connectors/connectors-creating.md
:white_check_mark:Succeeded

msteams-platform/concepts/messaging-extensions/create-extensions.md
:white_check_mark:Succeeded

msteams-platform/concepts/tabs/tabs-context.md
:white_check_mark:Succeeded

msteams-platform/includes/landing-page.html
:white_check_mark:Succeeded

msteams-platform/publishing/application-certification.md
:white_check_mark:Succeeded

msteams-platform/resources/design/components/color.md
:white_check_mark:Succeeded

msteams-platform/resources/dev-preview/developer-preview-features.md
:white_check_mark:Succeeded

msteams-platform/resources/dev-preview/developer-preview-intro.md
:white_check_mark:Succeeded

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded

msteams-platform/share-to-teams.md
:white_check_mark:Succeeded

msteams-platform/whats-new.md
:white_check_mark:Succeeded

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

Docs Build status updates of commit be4dae7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded

msteams-platform/assets/icons/share-to-teams-icon.png
:white_check_mark:Succeeded

msteams-platform/assets/images/icebreaker.PNG
:white_check_mark:Succeeded

msteams-platform/assets/images/self-assessment.png
:white_check_mark:Succeeded

msteams-platform/assets/images/share-to-teams-icon.png
:white_check_mark:Succeeded

msteams-platform/assets/images/share-to-teams-popup-edu.png
:white_check_mark:Succeeded

msteams-platform/assets/images/share-to-teams-popup.png
:white_check_mark:Succeeded

msteams-platform/assets/images/stickers.PNG
:white_check_mark:Succeeded

msteams-platform/concepts/bots/bot-conversations/bots-conv-proactive.md
:white_check_mark:Succeeded

msteams-platform/concepts/bots/bots-test.md
:white_check_mark:Succeeded

msteams-platform/concepts/calls-and-meetings/call-notifications.md
:white_check_mark:Succeeded

msteams-platform/concepts/connectors/connectors-creating.md
:white_check_mark:Succeeded

msteams-platform/concepts/messaging-extensions/create-extensions.md
:white_check_mark:Succeeded

msteams-platform/concepts/tabs/tabs-context.md
:white_check_mark:Succeeded

msteams-platform/includes/landing-page.html
:white_check_mark:Succeeded

msteams-platform/publishing/application-certification.md
:white_check_mark:Succeeded

msteams-platform/resources/design/components/color.md
:white_check_mark:Succeeded

msteams-platform/resources/dev-preview/developer-preview-features.md
:white_check_mark:Succeeded

msteams-platform/resources/dev-preview/developer-preview-intro.md
:white_check_mark:Succeeded

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded

msteams-platform/share-to-teams.md
:white_check_mark:Succeeded

msteams-platform/whats-new.md
:white_check_mark:Succeeded

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


Remove obsolete comment in join_all() docs.

After https://github.com/alexcrichton/futures-rs/pull/255, join_all() drives all of its futures concurrently.

Thanks!


Tabster causing costly recalculate styles when appending DOM elements to body

The origin for the issue is based on a lazy loaded component that adds an aria live region in the body of Teams.
To reproduce the issue you can start the latest version of Teams and start a performance trace.
Then run the following code in the console.
document.body.appendChild((() => { e = document.createElement("div"); e.innerText = "Hello world!"; return e; })())
Stop the performance trace, and you should see something like this:

The 111ms is done on a fairly new desktop computer, with 4x slowdown the time to compute is more than 500ms.
The reason for the recalculate style is tabster, and specifically within https://github.com/microsoft/tabster/blob/431e8d107eea021149ce4b68e48694b577962977/src/Utils.ts#L1148
When the body gets the new child appended, tabsters timeout will later run, and move the <i> element to the bottom of the body. This causes the recalculate style to happen.

@tejohans, why is it needed to append elements to  often enough for it to matter a lot?
I can imagine appending

@mshoho
For me there are two parts to this, one is the principle and the other is a real run-time issue.
The principle part is about the cost of adding a simple div to the body in the DOM should not be a several hundred millisecond task in an application. The exact same code in other applications uses 0-2ms on slowdown, compared to 500ms+ in Teams. When I discussed this internally I was asking if this was a tabster problem or an application problem, but I was encouraged to create the bug on tabster. At the moment, tabster is causing this to happen for any code that adds a div to the body - that is from my perspective not acceptable.
The second part is the run-time issue. When we lazy load our component and it is adding its aria live region, we get hit by this 100ms delay. However, its not the only recalculation outside of our control, there are several others as well. On my desktop PC, the totalt cost is 400ms+, on a slowdown we are seeing potentially seconds of recalculation. I need to get these issues solved one by one, else the first run experience for our component will not be good. And I think any other component that relies on similar logic will have a challenge with this.
If you think this behavior is something that cannot be improved, that is also an outcome that I can take into consideration when I continue my investigation.

The issue was caused by something else.

@mshoho can you explain what was causing this?

@ling1726 I cannot tell for sure. This particular issue is not reproducible anymore (Terje has confirmed that). Either Chromium has optimized something related (I tried to repro it in older public version and it's not reproducible) or some styling change in TMP.


faucet backward compat broken

logs from the faucet pod using tezos-k8s v6.2.0 on dailynet (which was activated with an older faucet version v5.x)
│                                                                                │
│ faucet-gen + CMD=faucet-gen                                                                                │
│ faucet-gen + shift                                                                                │
│ faucet-gen + exec /faucet-gen.py --seed redacted-TEZOS-DAILYNET-2022-02-09T00:00:00.000Z --number-of-accounts 1000 --write-secret-seeds-to /secret-seeds/secret-seeds │
│ .json                                                                                │
│ faucet-gen Seed is redacted-TEZOS-DAILYNET-2022-02-09T00:00:00.000Z                                                                                │
│ faucet-gen Searching for already used faucet keys                                                                                │
│ faucet-gen Assuming that if we see more than 10 empty accounts, we have reached the end of the faucet                                                                             │
│ faucet-gen Hopefully it's true. But if someone claims more than 10 faucets and do not use them, then our assumption is wrong                                                      │
│ faucet-gen Balance for tz1hm5GCEKSDd63BhkGy5JqNBRVFctFE8cwm is 0                                                                                │
│ faucet-gen Balance for tz1PLSbM2RSFSrXJyP5AUoFWTK3c1Taanbwk is 0                                                                                │
│ faucet-gen Balance for tz1YDMbeJQKYiAwRgtpmK42YzBWurqtFPKgG is 0                                                                                │
│ faucet-gen Balance for tz1MmniysjtVm2TX9AYmLxfUVC7uPJvBv6M6 is 0                                                                                │
│ faucet-gen Balance for tz1btCzDCZ1DS71nTthdbkVtE6d5JrVqK9g7 is 0                                                                                │
│ faucet-gen Balance for tz1MNv454PT5roby1epmhXg1EGADUbYcFYcK is 0                                                                                │
│ faucet-gen Balance for tz1Z2DsZUYU1dbp4NHXpV3KYX4VGPq8azStS is 0                                                                                │
│ faucet-gen Balance for tz1NzzY7ukXJrcK3h7FSgn7JyQqKAeiZKnBp is 0                                                                                │
│ faucet-gen Balance for tz1dUXeGMjgPgqUgw2RnbmAawN7RGCiUNTaP is 0                                                                                │
│ faucet-gen Balance for tz1cgcf51SgUVJTB6GMqjMh4zgNYTnowXFqK is 0                                                                                │
│ faucet-gen Balance for tz1YGjHnrVbnPrqgqnaTDZqQ385CWYghZ7fS is 0                                                                                │
│ faucet-gen Found the first empty faucet address: tz1hm5GCEKSDd63BhkGy5JqNBRVFctFE8cwm                                                                                │
│ faucet ><EMAIL_ADDRESS>start /                                                                                │
│ faucet > node app.js                                                                                │
│ faucet KEYS:  1000

When I try to activate the first account listed above, it fails. Reverting to 6.1.0:
│ + CMD=faucet-gen                                                                                │
│ + shift                                                                                │
│ + exec /faucet-gen.py --seed redacted-TEZOS-DAILYNET-2022-02-09T00:00:00.000Z --number-of-accounts 1000 --write-secret-seeds-to /secret-seeds/secret-seeds.json       │
│ Seed is redacted-TEZOS-DAILYNET-2022-02-09T00:00:00.000Z                                                                                │
│ numpy seed is<PHONE_NUMBER>                                                                                │
│ Searching for already used faucet keys                                                                                │
│ Assuming that if we see more than 10 empty accounts, we have reached the end of the faucet                                                                                │
│ Hopefully it's true. But if someone claims more than 10 faucets and do not use them, then our assumption is wrong                                                                 │
│ Balance for tz1ej5xErgyqRGBMNiFbqt6ApfAHbZ1axTDW is 0                                                                                │
│ Balance for tz1hrV3v5j6RDdvY831iZxZjjAwiWruWr728 is 0                                                                                │
│ Balance for tz1NwrDFQR9dWj9CB8SceAQbqfHzg1WWyXqa is 0                                                                                │
│ Balance for tz1RDNMMkPwxWUKDkJFd8c7GPUregTmPauV4 is 0                                                                                │
│ Balance for tz1bf5EqXaTMnFqb3tjj9cKVFhbebLk8FFJL is 0                                                                                │
│ Balance for tz1c6PGLSuMv8AqPvezx5KrLC6wBcFeMkUAh is 0                                                                                │
│ Balance for tz1MxEwJF2YHajLhuegpt44wxuozS3seExrv is 0                                                                                │
│ Balance for tz1Pd3W5XptyM8BcnoKoUzAXRDmMTYJo52Hj is 0                                                                                │
│ Balance for tz1aFmioTP82spKReu1hUK9HQB73UGmkqRrz is 0                                                                                │
│ Balance for tz1L85AV3fVNTWw14Wczov9RTWJ31uaGKu3J is 0                                                                                │
│ Balance for tz1TeKHpy3UgxzSMCU4jH6Rn9BrY2kkwb8qB is 0                                                                                │
│ Found the first empty faucet address: tz1ej5xErgyqRGBMNiFbqt6ApfAHbZ1axTDW

So, the 6.2.0 script gives me different addresses than 6.1.0.

Ah, yes. Something like this:
: chekalahk; git diff
diff --git a/utils/faucet-gen.py b/utils/faucet-gen.py
index 38d7729..d792cf1 100755
--- a/utils/faucet-gen.py
+++ b/utils/faucet-gen.py
@@ -77,6 +77,8 @@ def make_dummy_wallets(n, blind):
     amounts = [ i / sum(amounts) * 700e6 for i in amounts ]
     wallets = {}
     secrets = {}
+    # initialize random functions for determinism
+    random.seed(a=blind, version=2)
     for i in range(0, n):
         entropy = blake2b(str(i).encode('utf-8'), 20, key=blind).digest()
         mnemonic = m.to_mnemonic(entropy).split(' ')
@@ -103,8 +105,6 @@ args = parser.parse_args()
 if __name__ == '__main__':
     print(f"Seed is {args.seed}")
     blind = args.seed.encode('utf-8')
-    # initialize random functions for determinism
-    random.seed(a=blind, version=2)
     wallets, secrets = make_dummy_wallets(args.number_of_accounts, blind)

     commitments = genesis_commitments(wallets, blind)

should solve this.


Fix : Sample File Size Unit

Sample data had size label showing wrong memory units
13k instead of 13KB
2.8mb instead of 2.8MB
small b corresponds to bits and this would change entire meaning of file so fixed it

Closes #1192

@argyleink ready for review


Logo proposal

Hello @ziqiangxu, i am a graphic designer who loves open source projects. I would love to contribute a free logo to your project, that's if you allow.

It is my pleasure，just do it，thank you

Hi @ziqiangxu what do you think of this design...a mixture of opensource logo and dictionary

do you have any adjustments you would like me to make? if none, what logo sizes/types would you like me to export for you along with the editable SVG file?

What I want to know is that does logo equal to icon,I am not know about this.
2 .And the logo you designed is pretty, but I just want it can express more about dictionary, which can help user get the text and translation as easy as they can.
svg file is better, it will work well on diffrent resolution displays

ok how about these? their logo icons on the left

The first group is OK if adjust the color scheme like the previous one，

yellow and red are glare in my own opinion.

Sorry i have been unavailable. Was really ill, feeling better now. Will give you update on corrections soon.

Thanks, and best wish to you!

Thank you :). Here is the updated version plus another idea i had with the letter "F" being abstract in the second logo. What's your take?

The first one is ok :). .Thank you

Alright will make a pull request shortly. Is it OK i put the file in a folder named "Logo" at root directory?

Ok


Printing shortcuts

Description of the new feature / enhancement
having a function for printing all keyboard shortcuts at once
Scenario when this would be used?
at the beginning of using PowerToys, helping with the learning curve a bit
Supporting information
No response

/dup https://github.com/microsoft/PowerToys/issues/6751


Update drop down

Add component 'Item' https://github.com/ngsru/semantic-react/blob/5508a7a9ca970d45e214df764a020809c21c52d9/src/components/elements/item/index.js

Add OutsideClickHandle. https://github.com/ngsru/semantic-react/blob/5508a7a9ca970d45e214df764a020809c21c52d9/src/components/modules/outside-click-handler/index.js

Remove old 'dropdown' because it does not work, and add new only one type 'selection'.
Type  = http://semantic-ui.com/modules/dropdown.html#selection

I'll try to review this this weekend. Been out of the React space for a couple of months at work so haven't been able to do much here.

Can you rebase this against master?


Add support for Guzzle 7.x

I use AcmePHP Core in a Laravel project. Laravel 8.0 was released recently, and requires at least Guzzle 7. This library prevents the upgrade by demanding Guzzle 7.x.
I ran the test suite but didn't encounter any errors with this new version, so it should be safe to support both.

Hello @HansAdema !
This is a read-only repository extracted from the main repository (https://github.com/acmephp/acmephp). Could you apply your PR there?
Thanks!


InteractionProtocol */0x31/0x3 unsupported path

InteractionProtocol Read from udp://fe80::1424:8341:502a:f033%wlan0:55462 on session secure/62366: */0x31/0x3 unsupported path
here are the logs
And here is the code running the device.

Fixed by https://github.com/project-chip/matter.js/pull/210


Can't resolve 'idx' in InnerList.js

Hi,
I am looking to try out this library. However, when i try to set it up, it shows me this warning.
./node_modules/react-kanban-dnd/lib/InnerList.js
Module not found: Can't resolve 'idx' in '/node_modules/react-kanban-dnd/lib'

After looking at the library package.json, I think the library idx should be inside dependencies instead of devDependencies ?

Fixed it on: https://github.com/lucasbesen/react-kanban-dnd/pull/18


wasmtime-X.0.0-py3-none-any.whl doesn't include linux-x86_64

Hi,
The version py3-none-any.whl doesn't include build for linux-x86_64.
Thank you,
BR,
Julien

Of the files published the intention is that wasmtime-17.0.0-py3-none-manylinux1_x86_64.whl is used by x86_64 linux. The none-any is there for MinGW Windows IIRC, although I also sort of forget.
I'm also no expert on Python packaging, however, so do you know why the tooling you're using ended up using the none-any whl? Or do you have another use case for this wheel?

The none-any is there for MinGW Windows IIRC, although I also sort of forget.

Yeah, there's no way to separately distribute packages for MinGW, and this is the workaround.


Remove beta releases from changelog

Alaska Airlines Pull Request
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Resolves: # (issue, if applicable)
Summary:
Please summarize the scope of the changes you have submitted, what the intent of the work is and anything that describes the before/after state of the project.
Type of change:
Please delete options that are not relevant.

[ ] New capability
[ ] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[x] Other (please elaborate)

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

Summary by Sourcery
Remove entries related to beta releases from the changelog to maintain a cleaner and more focused document.
Chores:

Remove beta release entries from the changelog to streamline the document.

:tada: This PR is included in version 3.1.0-beta.3 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


update new guid for host exerciser lpbk and mem

HE-LB 56e203e9-864f-49a7-b94b-12284c31e02b
HE-MEM 8568ab4e-6ba5-4616-bb65-2a578330a8eb
Signed-off-by: anandaravuri<EMAIL_ADDRESS>

Coverage decreased (-0.06%) to 75.332% when pulling 05ebd0f772dd023fbc91b61d703594cad1a5f3ca on aravuri/he_guid into 91b23fb0fd27870e2c9474bac7c9f03c7480db73 on master.

Coverage decreased (-0.06%) to 75.332% when pulling 05ebd0f772dd023fbc91b61d703594cad1a5f3ca on aravuri/he_guid into 91b23fb0fd27870e2c9474bac7c9f03c7480db73 on master.


pivot filter box position

Hi,
Awesome work!
Recently in my project, I found that pivot filter box will be out of view port. Line 214, inn the file PivotTableUI.js, I saw the position is the absolute distance. However, seems that react-draggable is using relative distance from parent dom (Not sure, though)

Glad you like it! Can you explain how to reproduce the behaviour you're seeing? OS, Browser, window size?

Hi,
I can reproduce this issue together with Bootstrap.css
simple layout:
`import React, { Component } from 'react';
import DataTable from './DataTable';
class App extends Component {
render() {
return (

);
}
}
export default App;`
DataTable.js
`import React, { Component } from 'react';
import PivotTableUI from 'react-pivottable/PivotTableUI';
import 'react-pivottable/pivottable.css';
import TableRenderers from 'react-pivottable/TableRenderers';
class DataTable extends Component {
constructor(props) {
super(props);
this.state = {
data: [
{
attr1: "1",
attr2: "2"
},
{
attr1: "3",
attr2: "4"
}
]
}
}
render() {
    return (
        <div style={{height: "450px", width: "100%", overflowY: "auto", overflowX: "auto"}}>
            <PivotTableUI
                data={this.state.data}
                renderers={Object.assign({}, TableRenderers)}
                onChange={s => this.setState(s)}
                {...this.state}
            />
        </div>
    )
}

}
export default DataTable;`
As you can see, I put two data tables on one page, if you click the filters on second table, you would see the filter box is positioned out of the viewport. (Browser: 63.0.3239.84 (Official Build) (64-bit), screen resolution: 1900*1200)

Hi,
I can reproduce this issue together with Bootstrap.css

DataTable.js:

As you can see, I put two data tables on one page, if you click the filters on second table, you would see the filter box is positioned out of the viewport. (Browser: 63.0.3239.84 (Official Build) (64-bit), screen resolution: 1900*1200)

Does the solution proposed in https://github.com/nicolaskruchten/pivottable/issues/865 work for this issue as well?

In our app, the pivot table is embedded in another layout and also the filter box position is off (it's too far down). The proposed solution does not change anything in our case.

I had the same issue (position too far down) and fixed it by removing the top- and left-attributes in PivotTableUI.jsx on line 58 and 59 (see here).

Working on moving from pivottable to react-pivottable, getting the same issue, removing top and left attributes fixes the filter position for me too!

hey, thanks for the follow up! I was able to reproduce the issue in a codesandbox: https://codesandbox.io/s/6w7x5q74nr
I reproduced something like what we have in our page, we have a left panel with some sort of list, then in the right panel we have some bootstrap tabs, a data table and then in another tab the pivottable, at first I only added the tabs and the issue wouldn't show, then, when I added the left and right panel thing the issue showed, so it is related to having the pivottable inside bootstrap columns.

hope this helps solving the issue!! :)

hi @nicolaskruchten , do you have any progress on this issue? I have the same problem and I can reproduce it using
@claudio-rodriguez 's example.
Thanks in advance!

Fixed in https://github.com/plotly/react-pivottable/releases/tag/v0.8.0


Migrate NewInformer to cache.ListerWatcher

Migrate informer.NewInformer to cache.ListerWatcher to:

provide compile-time validation of resources (e.g. typo in resource name will be detected in compilation time)
make it testable:

previous code uses on RESTClient which isn't implemented by kubernetes' fake.NewSimpleClientset()
this code uses a standard way of creating informers which is properly handled by fake.NewSimpleClientset()

I still let informer.NewInformer exists as it has convenient addEventHandler call.
/assign @wojtek-t

/lgtm
/approve

/retest


Raspberry Pi 4: Docker Build Fails on Debian Bullseye

user@domain:/home/dietpi/flare-bypasser# docker compose up -d
[+] Running 1/1
 ! flare-bypasser Warning pull access denied for flare-bypasser, repository does not exist or may require 'docker login': denied: requested acces...                         2.9s
[+] Building 45.3s (12/23)                                                                                docker:default
 => [flare-bypasser internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 3.77kB                                                                                0.0s
 => [flare-bypasser internal] load metadata for docker.io/library/python:3.11-slim-bullseye                                                                                1.7s
 => [flare-bypasser internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [flare-bypasser internal] load build context                                                                                0.2s
 => => transferring context: 81.04kB                                                                                0.2s
 => [flare-bypasser builder 1/8] FROM docker.io/library/python:3.11-slim-bullseye@sha256:08ef1d5c4e0c05244f0971150437c57f6c79863345e549dbaebaf1b61f56bdf5                    0.0s
 => CACHED [flare-bypasser builder 2/8] WORKDIR /app/                                                                                0.0s
 => CACHED [flare-bypasser builder 3/8] RUN mkdir -p "/packages"   && apt-get update   && apt-get install -y --no-install-recommends equivs   && equivs-control libgl1-mesa  0.0s
 => CACHED [flare-bypasser builder 4/8] RUN apt-get install -y --no-install-recommends curl  # gost-install.sh requirement                                                   0.0s
 => CACHED [flare-bypasser builder 5/8] COPY utils/gost-install.sh ./gost-install.sh                                                                                0.0s
 => CACHED [flare-bypasser builder 6/8] RUN ./gost-install.sh --install                                                                                0.0s
 => CACHED [flare-bypasser builder 7/8] COPY utils/linux_chrome_installer.py /opt/flare_bypasser/bin/linux_chrome_installer.py                                               0.0s
 => ERROR [flare-bypasser builder 8/8] RUN python3 /opt/flare_bypasser/bin/linux_chrome_installer.py   --version-prefix="130."   --install-root=/opt/flare_bypasser/instal  43.1s
------
 > [flare-bypasser builder 8/8] RUN python3 /opt/flare_bypasser/bin/linux_chrome_installer.py   --version-prefix="130."   --install-root=/opt/flare_bypasser/installed_chrome/   --arch=$(arch) ||   { echo "Can't install chrome (required version '130.')" >&2 ; exit 1 ; }:
3.018 Download chrome by url: https://storage.googleapis.com/chrome-for-testing-public/130.0.6669.0/mac-arm64/chrome-mac-arm64.zip
33.07 ERROR:root:Can't install chrome: [Errno 2] No such file or directory: '/opt/flare_bypasser/installed_chrome/chrome'
35.07 Can't install chrome (required version '130.')
------
failed to solve: process "/bin/sh -c python3 /opt/flare_bypasser/bin/linux_chrome_installer.py   --version-prefix=\"$CHROME_VERSION\"   --install-root=/opt/flare_bypasser/installed_chrome/   --arch=$(arch) ||   { echo \"Can't install chrome (required version '$CHROME_VERSION')\" >&2 ; exit 1 ; }" did not complete successfully: exit code: 1
user@domain:/home/dietpi/flare-bypasser# arch
aarch64

Hi, ARM supporting is now in progress, I plan to finish at 11 Nov

Please, try version after this fix

 => ERROR [flare-bypasser builder 9/9] RUN if [ "$(arch)" != "x86_64" ] ; then     echo "To install chrome from google repository (no archive versions for ARM)" ;     c  51.9s
------
 > [flare-bypasser builder 9/9] RUN if [ "$(arch)" != "x86_64" ] ; then     echo "To install chrome from google repository (no archive versions for ARM)" ;     chmod +x ./linux_chrome_repo_installer.sh ;     bash -c "./linux_chrome_repo_installer.sh /opt/flare_bypasser/installed_chrome/ '130.'" ||     { echo "Can't install chrome (required version '130.')" >&2 ; exit 1 ; } ;   else     echo "To install chrome from archive" ;     python3 ./linux_chrome_archive_installer.py       --version-prefix="130."       --install-root=/opt/flare_bypasser/installed_chrome/       --arch=$(arch) ||     { echo "Can't install chrome (required version '130.')" >&2 ; exit 1 ; } ;   fi:
0.618 To install chrome from google repository (no archive versions for ARM)
46.47 To install package: google-chrome-stable=130.0.6723.116-1
51.75 Chrome install failed:
51.76
51.76 WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
51.76
51.76 Reading package lists...
51.76 Building dependency tree...
51.76 Reading state information...
51.76 E: Unable to locate package google-chrome-stable
51.76 Available versions:
51.77 chromium/oldstable,oldstable-security 120.0.6099.224-1~deb11u1 arm64
51.77 google-chrome-beta/stable 131.0.6778.33-1 amd64
51.77 google-chrome-canary/stable 132.0.6832.0-1 amd64
51.77 google-chrome-stable/stable 130.0.6723.116-1 amd64
51.77 google-chrome-unstable/stable 132.0.6821.2-1 amd64
51.77 Can't install chrome (required version '130.')
------
failed to solve: process "/bin/sh -c if [ \"$(arch)\" != \"x86_64\" ] ; then     echo \"To install chrome from google repository (no archive versions for ARM)\" ;     chmod +x ./linux_chrome_repo_installer.sh ;     bash -c \"./linux_chrome_repo_installer.sh /opt/flare_bypasser/installed_chrome/ '$CHROME_VERSION'\" ||     { echo \"Can't install chrome (required version '$CHROME_VERSION')\" >&2 ; exit 1 ; } ;   else     echo \"To install chrome from archive\" ;     python3 ./linux_chrome_archive_installer.py       --version-prefix=\"$CHROME_VERSION\"       --install-root=/opt/flare_bypasser/installed_chrome/       --arch=$(arch) ||     { echo \"Can't install chrome (required version '$CHROME_VERSION')\" >&2 ; exit 1 ; } ;   fi" did not complete successfully: exit code: 1

Yes, reproduced - script try install any available version without checking that it is available for platform, will fix at morning

Please, try version after this fix
I tested on macbook m1, trust that should work for raspberry too


Resolve issue where gcloud installation fails when building Datalab image

Fixes #816

This looks good to me. I ran into the same issue after the latest version of gcloud was 108.0.0.

Closing as duplicate. The gcloud installation will no longer be locked to a specific version based on the changes from pull request #823.


Azure Pipelines/TFS repo branch policy navigation inconsistent with docs.

Doc title: Build multiple branches
Doc URL: https://docs.microsoft.com/en-us/azure/devops/pipelines/build/ci-build-git?view=azure-devops-2019&tabs=classic#azure-pipelines-or-tfs-repository
Doc section: Validate pull requests > Azure Pipelines or TFS repository section
The documented steps don't match up with the current UI in on-prem Azure DevOps Server 2019. I started to author a change but then realized that there are all those conditionals (monikers and such) that drive the docs based on the ADO/TFS version and don't know if there are differences between the UI based on those variations.
It's a minor correction:
Step 3: The ellipsis next to the branch name only has the Lock Branch option. This step should be changed to direct the user to the Branch Policies link under the Security for master branch in {repo name} title.

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

ID: a55e404e-010b-32e5-30e0-71a2663a4f89
Version Independent ID: e011575a-691c-af48-2268-1959c9f3020b
Content: Building multiple branches - Azure Pipelines
Content Source: docs/pipelines/build/ci-build-git.md
Product: devops
Technology: devops-cicd
GitHub Login: @steved0x
Microsoft Alias: sdanie

@steved0x -- Steve, please review the changes in the above-mentioned PR 79.

@peterlanoie Thank you for your feedback. On Azure Devops Server 2019, the Branch menu hasn't changed in the areas of branch policies, it looks like this. Does yours look different? Even if your user account doesn't have the permission to change the branch policies, you can typically still see the menu item for branch policies, click it, and view the policies.
Based on the screenshot I just took, it matches the steps for Step 3: You will implement a branch policy to protect the master branch. Select the ellipsis to the right of your branch name and Select Branch policies.
What does yours show?

I see what the confusion was. In Azure DevOps Server 2019, the Code hub is now Repos. When I couldn't find Code in the hubs list, I went to Project Settings > Code > Repositories and then the branches under a repo. That's where the ... menu for the branch only shows Lock Branch. The Project Settings > Code > Policies section has a note and screenshot directing us to the area you have in your screenshot, so that definitely aligns with the docs.
I do have what you have in the screenshot when in the Repos > Branches area. So the docs are mostly correct except for the Code vs. Repos labeling in step 1.

I've updated https://github.com/MicrosoftDocs/azure-devops-docs-pr/pull/79 to reflect only that change (Code is now Repos).


Document the docs writing and testing better

What we currently have in the docs writing section lacks detail (install, test) and causes contributors to spend, unnecessarily, time in setting up and updating their docs contributions.

PR #417 addressed this,
https://github.com/aws/aws-controllers-k8s/pull/417/files includes info for contributors


Use ActionView instead of Erubis to render outcome templates

In general this moves us closer to being a standard Rails app which is one of
our longer-term goals. More specifically:

By supplying the state in the locals Hash, we don't have to worry about the
view modifying the state via writer methods.
Strings marked as HTML-unsafe (e.g. user input) are automatically escaped.
I've added an integration test to demonstrate this.
We don't have to do mess about with a binding object.
Note that ActionView uses Erubis in its implementation which is what we
were using previously, so this reduces the scope of the change.
A different exception is raised if a non-existent state variable is accessed:
ActionView::Template::Error instead of NoMethodError.
It should now be much easier to introduce "partial" templates for sharing
content between outcome templates.

Closing to investigate an unexpected issue.

This has been superseded by #1689.


Addition of Concode Dataset

##Overview
Concode Dataset contains pairs of Nl Queries and the corresponding Code.(Contextual Code Generation)
Reference Links
Paper Link = https://arxiv.org/pdf/1904.09086.pdf
Github Link =https://github.com/microsoft/CodeXGLUE/tree/main/Text-Code/text-to-code

Testing command doesn't work
###trace
-- Docs: https://docs.pytest.org/en/stable/warnings.html
========================================================= short test summary info ==========================================================
ERROR tests/test_dataset_common.py - absl.testing.parameterized.NoTestsError: parameterized test decorators did not generate any tests. Ma...
====================================================== 2 warnings, 1 error in 54.23s =======================================================
ERROR: not found: G:\Work Related\hf\datasets\tests\test_dataset_common.py::LocalDatasetTest::test_load_real_dataset_concode
(no name 'G:\Work Related\hf\datasets\tests\test_dataset_common.py::LocalDatasetTest::test_load_real_dataset_concode' in any of [])

Hello @lhoestq Test checks are passing in my local, but the commit fails in ci. Any idea onto why?
Dummy Dataset Test
====================================================== 1 passed, 6 warnings in 7.14s =======================================================
Real Dataset Test
====================================================== 1 passed, 6 warnings in 25.54s ======================================================

Hello @lhoestq, Have a look, I've changed according to the reviews. Thanks!

@reshinthadithyan that's a great start! You will also need to add a Dataset card, following the instructions given here

@reshinthadithyan that's a great start! You will also need to add a Dataset card, following the instructions given here

Hello @yjernite I'm facing issues in using the datasets-tagger Refer #1 in datasets-tagger. Thanks

@reshinthadithyan that's a great start! You will also need to add a Dataset card, following the instructions given here

Hello @yjernite I'm facing issues in using the datasets-tagger Refer #1 in datasets-tagger. Thanks

Hi @reshinthadithyan ! Did you try with the latest version of the tagger? What issues are you facing?
We're also relaxed the dataset requirement for now, you'll only add to add the tags :)

Could you work on another branch when adding different datasets ?
The idea is to have one PR per dataset

Thanks ! The github diff looks all clean now :)
To fix the CI you just need to rebase from master
Don't forget to add the tags of the dataset card. It's the yaml part at the top of the dataset card
More infor here : https://github.com/huggingface/datasets/blob/master/ADD_NEW_DATASET.md#tag-the-dataset-and-write-the-dataset-card
The issue you had with the tagger should be fixed now by https://github.com/huggingface/datasets-tagging/pull/5


Update psycopg2 for newer version

Hi,
The version of psycopg2 in the requirement of prod is no more compatible with newer version of python. Could you modify the tuto to indicate to install new version of psycopg2. I am currently trying to work with the 9.5.5 version of psycopg2 and the install worked i'll see if it's keep running without issues in the future
Alexandre Martin

Hi !
Thanks for the useful info !
Don't hesitate to propose a PR for the tuto, it would be greatly appreciated :)
(To be honest it's a bit hard to find time to continue supporting this project, but I'm available if you need any help)
Eyap / Mael Lacour

OK,
I'll will send it !
pams95 / Alexandre MARTIN


make docker guide somewhat useable for new linux users

Things i've added:
.sh to the end, otherwise you just get told that chbisafe is a directory
chmod 775 to mark the sh file as executable

Fixed in 987078b