Fix focus after picking an emoji in edit mode

Details

This PR addresses an issue, where the input bar wasn't focused after selecting an emoji from the modal in the edit mode.
To make it work, I add a short delay before calling focus() on the input bar. A similar approach is used in the ReportActionCompose. They explain it in the comment:
// Keyboard is not opened after Emoji Picker is closed
// SetTimeout is used as a workaround
// https://github.com/react-native-modal/react-native-modal/issues/114
// We carefully choose a delay. 100ms is found enough for the keyboard to open.
setTimeout(() => this.textInput.focus(), 100);

This doesn't fix anything on the mWeb / Safari, because Safari blocks focusing here.
Fixed Issues

$ https://github.com/Expensify/App/issues/18001
$ PROPOSAL: https://github.com/Expensify/App/issues/18001#issuecomment-1642157870
Tests

[x] Verify that no errors appear in the JS console
[x] Select a report
[x] Type a short message in the input bar
[x] Press the emoji button
[x] Select a random emoji
[x] Check if the focus is back in the input bar
[x] Send the message
[x] Press the edit button on the message that was sent (on native/mWeb long-press the message, then press Edit).
[x] Make changes to the message (add/remove some characters)
[x] Press the emoji button and select an emoji.
[x] Verify that the focus is back in the edited box (on mWeb Chrome/native the keyboard should display).

Offline tests

This PR doesn't affect any offline behavior.
QA Steps

Note: On mWeb/Safari this PR doesn't do anything, because Safari doesn't let developers focus any input programmatically.

[ ] Verify that no errors appear in the JS console
[ ] Do the test from above
[ ] Check focus after selecting emoji in the edit mode several times

[ ] Select a message to edit
[ ] Modify it
[ ] Add emoji using the emoji button
[ ] Confirm, that the focus is back in the correct input bar

[ ] Check focus with multiple edit boxes

[ ] Open edit mode in several messages
[ ] Add emoji to one of the messages
[ ] Confirm that the emoji is added to the appropriate message, and everything works as expected

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
https://github.com/Expensify/App/assets/104823336/55bc3d60-b17b-43b5-b973-5398233c706e

Mobile Web - Chrome
https://github.com/Expensify/App/assets/104823336/8d11b706-49d3-40ec-a44c-0584c1bf4321

Mobile Web - Safari
https://github.com/Expensify/App/assets/104823336/7f2df0eb-472a-4f54-b054-1e19d7ab4ceb

Desktop
https://github.com/Expensify/App/assets/104823336/f59682d7-0fcf-4583-a565-de22ed46f6b5

iOS
https://github.com/Expensify/App/assets/104823336/a7004509-5661-4e10-93a9-2302aa2b1846

Android
https://github.com/Expensify/App/assets/104823336/83cd95f9-03cd-439c-977f-a57e8c6fb201

@situchan feel free to review please

Lint is failing

@situchan @kosmydel How is this looking

@kosmydel is this ready for another look?

@situchan good for another testing

Also, the branch conflicts

The reanimated version was bumped so lets make sure to retest this well

The reanimated version was bumped so lets make sure to retest this well

I merged into the main and quickly checked, and I haven't noticed any problems.

@situchan I think it is ready to review, just a friendly reminder :)

@situchan bumping this one

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
https://github.com/Expensify/App/assets/108292595/4212d628-6904-4884-8fe5-aaf082a6a27a

Mobile Web - Chrome
https://github.com/Expensify/App/assets/108292595/018c79ca-0ca6-424a-89ae-96288ccc6c4d

Mobile Web - Safari
https://github.com/Expensify/App/assets/108292595/d9ee94ed-3cd1-42fa-b615-f53218d60c9d

Desktop
https://github.com/Expensify/App/assets/108292595/95e239f1-974c-406e-82cc-4d1095cb5fce

iOS
https://github.com/Expensify/App/assets/108292595/b4dc9528-a991-4429-86b7-d0c58f64f960

Android
https://github.com/Expensify/App/assets/108292595/93f0a11b-ebea-4197-ab09-286140d4ae29

Hey @mountiny, I think this is ready for a second review. I'm not sure who I should ping.

Bumping @mountiny

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/mountiny in version: 1.3.54-0 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/mountiny in version: 1.3.54-0 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/yuwenmemon in version: 1.3.54-13 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


How to handle date?

I can't figure out how to handle time. I've been using "javascript-time-ago" to display messages based off a timestamp. Like "1h ago" or "in 2hours".
But I'm sure I can deprecate this module and only use next-intl right?

Hi @andrevenancio,
yes, there's useIntl().formatRelativeTime to achieve this.
Did you find something unclear or misleading in the docs?

Hey @amannn Somehow I've missed that. I think the way its organised you have to really read from beginning to end instead of just reading vertically trying to find something quick. Not necessarly your fault but mine :)
However, I have some questions on how to format it? so if I wanted to changee it to different languages "in 2hours" how can I configure the "in" from english to whatever language I'm targeting?
Also in regards to the now we're supposed to put in the Provider. How do you suggest we do this? since I have my Provider on the _app.ts ? Is it just a now={Date.now()} or does that Date.now() need to come from the server? You mention that with cache headers our chances of having a mismatch increase, what's your best practices that you recommend?
I really like this library. I guess my only suggestion is maybe some more examples. But again this might be me trying to solve things too quickly without properly absorving knowledge scattered on the docs :)

For example:
import {useNow} from 'next-intl';

function Component() {
  const now = useNow();

  const dateTime = parseISO('2020-11-20T10:36:01.516Z');
  intl.formatRelativeTime(dateTime, now);
}

Where is this intl coming from?

if I wanted to changee it to different languages "in 2hours" how can I configure the "in" from english to whatever language I'm targeting?

This is currently not possible. next-intl uses a built-in browser API for this feature which doesn't allow to customize this.

Is it just a now={Date.now()} or does that Date.now() need to come from the server? You mention that with cache headers our chances of having a mismatch increase, what's your best practices that you recommend?

From the docs of formatRelativeTime:
<NextIntlProvider
  // This value can be generated in data fetching functions of individual pages or `App.getInitialProps`.
  now={now}
  ...
>
  <App />
</NextIntlProvider>

This value will be used as the default for the formatRelativeTime function as well as for the initial render of useNow.
Important: When you use getStaticProps and no updateInterval, this value will be stale. Therefore either regenerate these pages regularly with revalidate, use getServerSideProps instead or configure an updateInterval.

Does that leave any questions open?

I guess my only suggestion is maybe some more examples.

What kind of examples are missing? Did you see or have a look at the example app in the repo?

Where is this intl coming from?

Good point, the import was missing here.
--
It seems like these are some issues with the docs. I've just created a new ticket look into these: https://github.com/amannn/next-intl/issues/72. I'm really grateful about feedback for the docs, so please leave any comments you have there!

thank you for working on it and your patience guiding me through this.


Update UI according to the new spec

Spec: https://app.zeplin.io/project/5cf7c3cecee3f113e909e492/screen/5cf7c4002eb4af5c6e929949
Demo: http://tectonic-explorer.concord.org/branch/166842460-ui-updates/index.html?preset=subduction
(the last version should be available in 10 minutes)

Look good! A couple of small changes - Cross-section should have lowercase s, and in the Key when Earthquakes are visible, change Magnitude and Depth to have lowercase and. Otherwise 👍

Hm, this is how CSS text-transform: capitalize works. So, I'll have to go through all the labels and do that by hand. :wink: But if it looks strange otherwise, I guess it makes sense, not a big thing. Thanks.

This change got pretty big, as I had to go through all the labels and fix them + update Cypress screenshots. But I guess it's better not to rely on automatic capitalize.


Braden's Swiftfall Project

I did a project and my mom is really proud!
Edit: Oops I didn't know I had to write an actual article, so I copied Marc's. Oh well, I'll get that done I guess.

I made changes.


0.3 release doesn't include some necessary folders

The unitypackage release is missing some folders in uREPL/Resources/Prefabs/ that make it crash on completing a command. I had to get it working by cloning master into my project.

I'll update the package after fixing #5.

v0.3.1 includes missing contents.
https://github.com/hecomi/uREPL/releases/tag/v0.3.1


Cannot build Android app on Windows "no such directory, lstat 'C:\c..."

Build/Submit details page URL
No response
Summary
When trying to build an app for Android on Windows I get the error no such directory, lstat 'C:\c\... which obviously doesn't exist, since there is no 'c' folder inside C:\
EAS CLI is trying using the Linux path /c/... on Windows.
Managed or bare?
Managed
Environment
expo-env-info 1.0.5 environment info:
System:
OS: Windows 7 6.1.7601
Binaries:
Node: 14.16.1 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
npm: 6.14.12 - C:\Program Files\nodejs\npm.CMD
npmPackages:
@expo/webpack-config: ^0.17.0 => 0.17.0
expo: latest => 46.0.2
react: 18.0.0 => 18.0.0
react-dom: 18.0.0 => 18.0.0
react-native: ^0.69.4 => 0.69.4
react-native-web: latest => 0.18.7
Expo Workflow: managed
× Dependency tree validation for expo-modules-autolinking failed. This validation is only available on Node 16+ / npm 8.
× Dependency tree validation for @expo/config-plugins failed. This validation is only available on Node 16+ / npm 8.
× Dependency tree validation for @expo/prebuild-config failed. This validation is only available on Node 16+ / npm 8.
× Dependency tree validation for @unimodules/core failed. This validation is only available on Node 16+ / npm 8.
× Dependency tree validation for @unimodules/react-native-adapter failed. This validation is only available on Node 16+ / npm 8.
× Dependency tree validation for react-native-unimodules failed. This validation is only available on Node 16+ / npm 8.
🎉 Didn't find any issues with the project!
Error output
PS E:\ReactNative\app> eas build -p android
✔ Linked to project @ttfh/**** (https://expo.dev/accounts/ttfh/projects/****)
✔ Using remote Android credentials (Expo server)
✔ Using Keystore from configuration: Build Credentials **** (default)
Compressing project files and uploading to EAS Build. Learn more: https://expo.fyi/eas-build-archive
Error: ENOENT: no such file or directory, lstat 'E:\e\ReactNative\app'
Code: ENOENT
Reproducible demo or steps to reproduce from a blank project
Execute eas build -p android on Windows

It works on Linux, but I don't want to copy my project to a different computer every time I need to make a new build

It works for me on Windows:

Can you please tell me a little more about your setup? Can you share eas.json?

eas.json
{
	"cli": {
		"version": ">= 0.60.0"
	},
	"build": {
		"development": {
			"android": {
				"buildType": "apk"
			}
		},
		"preview": {},
		"production": {}
	},
	"submit": {
		"production": {}
	}
}

Build command:
eas build -p android --profile development
It works fine on Linux, but on Windows it's seems it's not detecting the operative system correctly and appending the drive letter at the beginning of the path.

@dsokal I found the problem.
I'm using eas version: eas-cli/0.60.0 win32-x64 node-v14.16.1
The program crash on build.js:110
const projectTarball = await (0, repository_1.makeProjectTarballAsync)();
It calls repository.js:80
await (0, vcs_1.getVcsClient)().makeShallowCopyAsync(shallowClonePath);
That calls local.js:73
async function makeShallowCopyAsync(src, dst) {
In this function src has the value:
src = "\e\ReactNative\app";
instead of:
src = "E:\ReactNative\app";
Not sure where the value comes from or why it's wrong


Add docs for stream processors

Signed-off-by: Michael Crosby<EMAIL_ADDRESS>

LGTM

Codecov Report

Merging #3518 into master will decrease coverage by 3.77%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3518      +/-   ##
==========================================
- Coverage   48.05%   44.27%   -3.78%
==========================================
  Files         113      124      +11
  Lines       10935    13682    +2747
==========================================
+ Hits         5255     6058     +803
- Misses       4746     6688    +1942
- Partials      934      936       +2

Flag
Coverage Δ

#linux
48.05% <ø> (ø)
:arrow_up:

#windows
39.76% <ø> (?)

Impacted Files
Coverage Δ

snapshots/native/native.go
43.04% <0%> (-9.99%)
:arrow_down:

metadata/snapshot.go
47.9% <0%> (-8.6%)
:arrow_down:

cio/io.go
46.47% <0%> (-8.53%)
:arrow_down:

pkg/encryption/keywrap/pkcs7/keywrapper_pkcs7.go
44.61% <0%> (-8.12%)
:arrow_down:

archive/tar.go
43.79% <0%> (-7.07%)
:arrow_down:

metadata/containers.go
47.97% <0%> (-6.62%)
:arrow_down:

pkg/encryption/keywrap/jwe/keywrapper_jwe.go
52.77% <0%> (-5.56%)
:arrow_down:

content/local/writer.go
58.65% <0%> (-5.55%)
:arrow_down:

pkg/encryption/encryption.go
50.69% <0%> (-5.35%)
:arrow_down:

content/local/store.go
49.52% <0%> (-5.29%)
:arrow_down:

... and 73 more

Continue to review full report at Codecov.

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


Stop Trail version popup

How do I stop trial version Pop up ? I have to give a demo for my clients, If popup comes in between, They may feel some think awkward .

@balarvs2002  Hi! You see popup only in free version. Paid component hasn't this alert.
Please send me email on<EMAIL_ADDRESS>- maybe i can send  discount to you.

I just need it for 3 weeks to show demo for stakeholders.  Once it is approved, Then I will indeed purchase it.  Can you please do some thing for 3 weeks ?

Hi!
Ok, i understand your problem. So let’s do this - i will send you dlls with
last version.
But after (if demo is success) you will send this 26$ to my paypal. For
Xamarin.Components i will send you promo code.
Ok?
Also i can sell source of this control for you with big discount.
And if you interested - please take a look on my UI Kit for Xamarin.Forms.
Demo : Android
https://appetize.io/embed/r0empkb48r755x01j6h345j0f4?device=nexus5&scale=75&orientation=portrait&osVersion=7.0
, iOS
https://appetize.io/embed/nbmf61eq18ub054ztd71058j00?device=iphone6&scale=75&autoplay=false&orientation=portrait&deviceColor=black&osVersion=9.3
.
Little doc:
https://www.dropbox.com/s/dds91hjigxej55r/UI Kit doc (ver 0.1).pdf?dl=0
APK file:
https://www.dropbox.com/s/d381sigw3i7kf54/com.alexandr.demo.apk?dl=0
If you need my help - you are welcome
Thanks, Alex
От 19 февраля 2017 г. в 18:13:17, balarvs2002<EMAIL_ADDRESS>написал:
I just need it for 3 weeks to show demo for stakeholders. Once it is
approved, Then I will indeed purchase it. Can you please do some thing for
3 weeks ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/AlexandrNikulin/AnimationNavigationPage/issues/16#issuecomment-280925225,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALQ-YBlU8dUpaAW8Yl5wnunMYmXWWehaks5reFwMgaJpZM4MDf_M
.


Support HashAlgorithm class

Sha3Digest class (namespace Org.BouncyCastle.Crypto.Digests) can provide the Hash function,
but it is not the C# programing style.
Most C# Hash classes inherit from class HashAlgorithm (namespace System.Security.Cryptography). By inheriting from HashAlgorithm, a large number of C# codes can be seamlessly switched.
https://docs.microsoft.com/en-us/dotnet/api/system.security.cryptography.hashalgorithm
This github class library has realized this function, through the simple conversion, bouncycastle can be integrated into all applications more easily.
https://github.com/dariogriffo/sha3.net/blob/master/src/SHA3.Net/Sha3.cs

Our API makes little to no attempt to integrate into System.Security.Cryptography API, and it wouldn't make much sense to do so on a case-by-case basis. I'm not saying it would be a terrible idea, but it's a much larger question than SHA3.
If you want to PR a HashAlgorithm adapter class that adapts any IDigest into a HashAlgorithm, that might be easy to include.


added updateModuleCommand and the appropriate test and parser, updated UserGuide as well as DeveloperGuide

Pull Request Test Coverage Report for Build 254

26 of 66 (39.39%)  changed or added relevant lines in 7 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 51.732%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/com/t13g2/forum/logic/parser/AddressBookParser.java
0
1
0.0%

src/main/java/com/t13g2/forum/logic/util/DisplayFormatter.java
0
2
0.0%

src/main/java/com/t13g2/forum/logic/parser/CreateModuleCommandParser.java
0
3
0.0%

src/main/java/com/t13g2/forum/logic/commands/UpdateModuleCommand.java
25
30
83.33%

src/main/java/com/t13g2/forum/logic/parser/ParserUtil.java
0
13
0.0%

src/main/java/com/t13g2/forum/logic/parser/UpdateModuleCommandParser.java
0
16
0.0%

Totals

Change from base Build 253:
0.2%

Covered Lines:
1568

Relevant Lines:
3031

💛  - Coveralls


how to training on new custom dataset?

Hello! Thank you for sharing code.
The FCDD you created before is working fine for me.
I'm trying to train EOE on my own dataset.
But it's a hard to do. how can i do?

Hello! I am trying to train EOE on my own dataset too. Did you do it ?

Hey.
I implemented this feature with commit e4dbb81.
I also added some lines on this to the readme.
Hope it helps! :)


JSONSchema required

When schema is embedded within an Array or an Object Field the required field is being added to the "items" or "properties" body. This should appear one level up at the same level as "type"
Reported by @smyrman
Example of incorrect output
        "items": {
          "properties": {
            "key": {
              "type": "string"
            },
            "score": {
              "type": "integer"
            },
            "required": [
              "score",
              "key",
              "value"
            ],
            "value": {
              "type": "string"
            }
          },
          "type": "object"
        },

Example of correct output
        "items": {
          "properties": {
            "key": {
              "type": "string"
            },
            "score": {
              "type": "integer"
            },

            "value": {
              "type": "string"
            }
          },
          "required": [
            "score",
            "key",
            "value"
          ],
          "type": "object"
        },

@rs I'll try and work up a patch, I have an idea of how to solve this.

@smyrman you might want to take a look now. I think it does the right thing. It's definitely generating valid JSON.

From what little testing I could do, it looks fine, at least inside an items clause.

@rs, @yanfali, I assume this issue should be closed.


BasicAuth middleware: headerField option doesn't seem to work

Do you want to request a feature or report a bug?

Bug

What did you do?
I tried to add basic auth (with TLS) to my portainer stack. As Portainer is also using the Authorization header to handle JWT, I wanted to change the portainer's header name used to handle basic authentication.

What did you expect to see?
Basic-Auth using the given headerField name header instead of Authorization to handle user authentication and allows other backend services to freely use Authorization (for JWT, ...)

My server is on Debian 9.x and I'm using dowker swarm.
$ docker version
Client: Docker Engine - Community
 Version:           19.03.10
 API version:       1.40
 Go version:        go1.13.10
 Git commit:        9424aeaee9
 Built:             Thu May 28 22:17:06 2020
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.10
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.10
  Git commit:       9424aeaee9
  Built:            Thu May 28 22:15:38 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.13
  GitCommit:        7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

My stack.yml
version: "3.3"

services:
  traefik:
    image: traefik:v2.2
    ports:
      - "80:80"
      - "443:443"
    command:
      - --global.checknewversion=true
      - --api.dashboard=true
      - --log.level=INFO
      - --metrics.prometheus=true
      - --metrics.prometheus.addEntryPointsLabels=true
      - --metrics.prometheus.addServicesLabels=true
      - --metrics.prometheus.entryPoint=traefik
      - --metrics.prometheus.manualrouting=true # because we create our own router

      - --providers.file.directory=/file_provider_d #we use the file provider for common definitions and outside-docker rules
      - --providers.file.watch=true

      - --providers.docker=true
      - --providers.docker.swarmMode=true
      - --providers.docker.exposedbydefault=false
      - --providers.docker.network=web
      - --providers.docker.swarmmoderefreshseconds=10 #default: 15s
      - --providers.docker.watch=true #default: true

      - --entrypoints.web.address=:80
      - --entryPoints.web.transport.respondingTimeouts.readTimeout=30s # default: 0s (no timeout)
      - --entryPoints.web.transport.respondingTimeouts.writeTimeout=30s # default: 0s (no timeout)
      - --entryPoints.web.transport.respondingTimeouts.idleTimeout=120s # default: 180s
      - --entrypoints.web.http.redirections.entryPoint.to=websecure
      - --entrypoints.web.http.redirections.entryPoint.scheme=https
      - --entrypoints.web.http.redirections.entrypoint.permanent=true
      - --entrypoints.web.http.middlewares=gzipResponseCompress@file # by default we'll compress the response

      - --entrypoints.websecure.address=:443
      - --entryPoints.websecure.transport.respondingTimeouts.readTimeout=30s # default: 0s (no timeout)
      - --entryPoints.websecure.transport.respondingTimeouts.writeTimeout=30s # default: 0s (no timeout)
      - --entryPoints.websecure.transport.respondingTimeouts.idleTimeout=120s # default: 180s
      - --entrypoints.websecure.http.tls.certResolver=my_resolver # let's encrypt
      - --entrypoints.websecure.http.middlewares=gzipResponseCompress@file # by default we'll compress the response

     # Uncomment the line to use Let's Encrypt's staging server, leave commented to go to prod.
     #- --certificatesresolvers.my_resolver.acme.caserver=https://acme-staging-v02.api.letsencrypt.org/directory
      -<EMAIL_ADDRESS>      - --certificatesresolvers.my_resolver.acme.storage=/letsencrypt/acme.json
     # Use a TLS-ALPN-01 challenge:
      - --certificatesresolvers.my_resolver.acme.tlschallenge=true
     # DNS-01 ACME challenge rather than HTTP-01 or TLS-ALPN-01 challenge. Mandatory for wildcard certificates
      - --certificatesresolvers.my_resolver.acme.dnschallenge=true
      - --certificatesresolvers.my_resolver.acme.dnschallenge.provider=gandiv5
      - --certificatesresolvers.my_resolver.acme.dnschallenge.resolvers=<IP_ADDRESS>:53,<IP_ADDRESS>:53

    environment:
      - "GANDIV5_API_KEY_FILE=/run/secrets/gandiv5-api-key"
    volumes:
      - letsencrypt:/letsencrypt
      - /home/itsmemario/workspace/traefik/file_provider_d:/file_provider_d
      - /var/run/docker.sock:/var/run/docker.sock:ro
    networks:
      - web
    secrets:
      - gandiv5-api-key
    deploy:
      placement:
        constraints:
          - node.role == manager
      labels:
        - "traefik.enable=true"

        - "traefik.http.routers.api.rule=Host(`traefik.website.com`)"
        - "traefik.http.routers.api.service=api@internal"
        - "traefik.http.routers.api.middlewares=proxyMonitoringAuth@file"
        - "traefik.http.routers.api.entryPoints=websecure"

        - "traefik.http.routers.prometheus_metrics.rule=Host(`traefik.website.com`) && PathPrefix(`/metrics`)"
        - "traefik.http.routers.prometheus_metrics.service=prometheus@internal"
        - "traefik.http.routers.prometheus_metrics.middlewares=proxyMonitoringAuth@file"
        - "traefik.http.routers.prometheus_metrics.entryPoints=websecure"

        - "traefik.http.services.dummy_api_service.loadbalancer.server.port=9999" # mandatory for docker swarm

networks:
  web:
    external: true

volumes:
  letsencrypt:

secrets:
  gandiv5-api-key:
    file: secrets/gandiv5_apikey

and my file_provider_d/common_definitions.yml
http:
  middlewares:

    #this auth is here to protect monitoring services by traefik before they're routing to.
    proxyMonitoringAuth:
      basicAuth:
        realm: "Monitoring"
        #        removeHeader: true
        headerField: "X-MonitorAuth-User"
        users:
          - 'test:$2y$05$o8JI3KtQhvYPMMIGGiPnpOiWikTAqwOlgrGx.xOiM.K5s1nT16hFK' # test:test

    #https://docs.traefik.io/middlewares/compress/
    gzipResponseCompress:
      compress: {}

[Edit] adding some info that I hope useful:
I talked about portainer as the intent behind, but it's the same with traefik's dashboard (see above dynamic config).
Here is the request details in my chrome inspector:
---------- General ----------
Request URL: https://traefik.website.com/dashboard/
Request Method: GET
Status Code: 200
Remote Address: xx.xx.xx.xx:443
Referrer Policy: no-referrer-when-downgrade

---------- Response Headers ----------
accept-ranges: bytes
content-encoding: gzip
content-length: 796
content-type: text/html; charset=utf-8
date: Wed, 03 Jun 2020 17:50:02 GMT
last-modified: Wed, 29 Apr 2020 18:00:36 GMT
status: 200
vary: Accept-Encoding

---------- Request Headers ----------
:authority: traefik.website.com
:method: GET
:path: /dashboard/
:scheme: https
accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9
accept-encoding: gzip, deflate, br
accept-language: fr-FR,fr;q=0.9,en-US;q=0.8,en;q=0.7,es-419;q=0.6,es;q=0.5
authorization: Basic YXRpcblablablabalaE=
cache-control: no-cache
dnt: 1
pragma: no-cache
sec-fetch-dest: document
sec-fetch-mode: navigate
sec-fetch-site: none
sec-fetch-user: ?1
upgrade-insecure-requests: 1
user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.61 Safari/537.36

Hello @toussa,
thanks for your interest in the project.
After reading your issue, I'm not too sure I did understood your use-case correctly. Do I understand it correctly, that you're basically asking to "read out" the basic auth information out of a different header field?
The field you're using is to tell Traefik, in which header it should store the information and not where to read it from.
Does it makes sense?

Hello :)
Oh... I think I misunderstood the "headerField" then...
Indeed I thought it allowed traefik to read and write the basic auth information to another header field in order to not interfere with backend service.
What's the main usage of storing it in another header ? I can't see any.
So if I understand well, it's not currently possible to use basic auth with a service (let's say, portainer) if this service uses JWT or other security mechanism that needs the Authorization header field.
If so, please feel free to close this issue. And thanks again for your work.

You're exactly right.
As you've suggested, I'll close that issue then. Thank you!


Unlock Intel Realsense D455 for Updates

Required Info

Camera Model
{ D455 }

Firmware Version
<IP_ADDRESS>

Operating System & Version
{Win 10}

Platform
PC

SDK Version
v2.39.0

Issue Description
After trying to update my Intel Realsense D455 to the newest update, I got the message that the device is locked for update.
Is there a way to unlock the camera?

Hi @pandurdo   Could you open the RealSense Viewer program please and use the 'Info' option to list the details of your camera to confirm which firmware version is currently installed.   It should not be the ' <IP_ADDRESS>' firmware listed in the Required Info details at the top of this case, as that was one of the first camera firmwares dating back to December 2017.  Cameras are shipped with at least the minimum firmware that supports them, and I believe for D455 that was a recent firmware from this year (2020).

What method are you using to update your camera firmware?

I tried to update it with the viewer as well as with the in SDK included tool 'rs-fw-update.exe' and the manually downloaded firmware '<IP_ADDRESS>' and got messages like:
"16/11 12:51:54,383 ERROR [18572] (types.h:313) hr returned: HResult 0x8007001f: "Ein an das System angeschlossenes Ger├ñt funktioniert nicht."
16/11 12:51:55,558 ERROR [19380] (handle-winusb.h:55) CreateFile failed, error: 5
16/11 12:51:55,560 ERROR [19380] (context.cpp:431) Exception thrown from user callback handler
failed to locate a device in FW update mode"
When I now try to update to this firmware, I get:
"firmware update started
firmware update progress: 8[%]RealSense error calling rs2_update_firmware_cpp(device:000001F8CF8BAF20, fw_image:000001F8D044F060):
Device: xxxxxxxxxxxx is locked for update.
Use firmware version higher than: <IP_ADDRESS>"

Okay, I see you have a D435.  The details at the top of this case said D455.  Thank you for the information.  So it would make sense why you might have an early firmware like <IP_ADDRESS> installed by default after purchasing the camera, as D435 was one of the original launch models of the 400 Series range.
It looks as though the English version of the HResult error logged above is A device attached to the system is not functioning.
Could you check the Windows privacy settings for cameras please to see whether Windows is set to allow applications to access the camera using the instructions in the link below?
https://github.com/IntelRealSense/librealsense/issues/3381#issuecomment-503424789

Actually it is a D455, I don't know why it is recognized as D435. I tried to update it on a different PC, where it was also detected as D435. After successfully updating it to the newest firmware, it is recognized as D455. But after switching back to my working PC, Windows downgrades the firmware back to '<IP_ADDRESS>'.
As I told you, I am no more able to update this camera (on any PC) due to the fact, that it is locked for updates (see error above).

How many times have you attempted to update the firmware of the camera, please?  RealSense cameras have a limit of 20 downgrades (installing a firmware version lower than the currently installed one).  After that point, you can only upgrade to a firmware version newer than the currently installed version.
So if the installed firmware was being recognised as <IP_ADDRESS> and the downgrade limit had been reached, I would expect to be told "Use firmware version higher than: <IP_ADDRESS>" each time that you tried to install <IP_ADDRESS> or older.
.Let's try to force a firmware update in the recovery mode of rs-fw-update.  First, please download the firmware .bin file for <IP_ADDRESS> if you have not done so already.
https://dev.intelrealsense.com/docs/firmware-releases

Place the firmware bin file in the same folder location as rs-fw-update and then launch rs-fw-update in recovery mode using the instruction below:
rs-fw-update -r -f Signed_Image_UVC_5_12_8_200.bin

Here the resulting message:
rs-fw-update.exe -r -f Signed_Image_UVC_5_12_8_200.bin
update to FW: Signed_Image_UVC_5_12_8_200.bin
recovering device:
Name: Intel RealSense D4xx Recovery, serial number: unknown, update serial number:<PHONE_NUMBER>87, firmware version: unknown, USB type: unknown
firmware update started
firmware update progress: 8[%]
failed to recover device

I notice that the USB type of your camera connection is not being displayed in the RealSense Viewer information.  It is usually beside the camera name and says '2.1' if it is a USB connection and '3.2' if a USB 3 connection.   The image below indicates where the USB type should be displayed on your connection:

And here is what my D435i camera's information looks like:

Can you confirm please whether your camera information remains the same if you go to the More option and select the Hardware Reset menu option.

Nothing happens by selecting Hardware Reset.

I have not seen a case before where the USB type is not detected / displayed at all.   I will consult within Intel about it.   I apologise for the delay in the meantime.

Having the device locked for updates is simply a function of too many downgrade-upgrade cycles.
5.8.15 on a D455 unit is not going to do anything good, since this firmware predates D455 hardware by 3 years...
I'm very concerned about this - "Windows downgrades the firmware back to '<IP_ADDRESS>'." Could you please provide more details, such as exact Windows version?

I did an successful upgrade to <IP_ADDRESS> one a Windows 10 PC, where such cameras were never used. When I plugged in the cam on my working PC with Windows 10 up-to-date (where I used Intel Realsenses such as D435 and D435i), the D455 was detected and again downgraded to <IP_ADDRESS>. And on this PC I was not able to upgrade neither via Viewer nor by the rs-fw-update.exe.

Hi @pandurdo   Do you require further assistance with this case, please?   Thanks!

Yes, Since my problem is not solved yet. I have a camera,which is not working and is not updatable.

@dorodnic   Do you have further advice about the problem of @pandurdo that you commented on earlier, please?  Thanks!

Hi again @pandurdo   Your previous problem was that your camera would only allow you to upgrade to a firmware newer than <IP_ADDRESS>.   As the new firmware <IP_ADDRESS> is now available, does your camera allow you to update to it?

Yes, upgraded it and it works now.

Great to hear that news @pandurdo

Hi @pandurdo  Do you require further assistance with this case, please?  Thanks!

No, thank you!

Excellent, thanks for the update!   :)


EnemyDeath prefix causing issues

Attacks don't finish, streetcleaners don't explode, NullReferenceExceptions get thrown

resolved with latest update


Add some missing PagerDuty fields to docs

These fields are all available on the PagerdutyConfig type:
https://github.com/prometheus/alertmanager/blob/59a96579cc9d117ae72cfb6ad45033ee746c6ba8/config/notifiers.go#L201..L203
I took the descriptions from the PagerDuty events-api-v2 docs:
https://developer.pagerduty.com/docs/events-api-v2/overview/

@simonpasquier this finally follows up on https://github.com/prometheus/docs/pull/1627


Tomcat 8 deployment issues with Latest artifacts on RHEL 7.4

There are some deployment issues with Tomcat 8 on RHEL7.4. It works good with tomcat 7.
error - WAR not getting deployed because of hibernate validation issues.
Thanks,
-Mayank Gangwal

This issue has been resolved.


Delete all data on submission

What is the context of this PR?
Fixes #276
Delete all user data from the database and clear users session on submission of data. This means once the thank you page has been displayed you are automatically logged out of EQ and all your questionnaire state is deleted.
Also changing to session cookies, so that when you close the browser your cookie is delete and your session is lost requiring you to log in again. Therefore if you are partially through a survey and close your browser you are required to log back in, though your data will be saved to the database.
How to review

Check out this branch
Run the application
Check save and resume works
Complete a survey
After the thank you page has been displayed hit the back button, a 401 response should appear
If you now return to the dev page you should be able complete the survey again

[x] Do all commits have sensible commit messages?
[x] Is all new code unit tested?
[x] Are there integration tests if needed?
[x] Is there sufficient logging?
[x] Is there documentation or is the code self-describing?

Who worked on the PR
@warrenbailey
…

Does this PR need a database backed environment to run in or can it be tested locally?

It'll use an SQLite database (the file is place in /tmp) if you don't set up postgres

LGTM 👍


paramiko 2.12.0

Recipe directory diff between current master and this update:
diff --git a/recipe/meta.yaml b/recipe/meta.yaml
index f24b973..634b07d 100644
--- a/recipe/meta.yaml
+++ b/recipe/meta.yaml
@@ -1,8 +1,8 @@
 {% set name = "paramiko" %}
-{% set version = "2.8.1" %}
+{% set version = "2.12.0" %}
 {% set bundle = "tar.gz" %}
 {% set hash_type = "sha256" %}
-{% set hash_val = "85b1245054e5d7592b9088cc6d08da22445417912d3a3e48138675c7a8616438" %}
+{% set hash_val = "376885c05c5d6aa6e1f4608aac2a6b5b0548b1add40274477324605903d9cd49" %}

 package:
   name: {{ name }}

Actions:
1.
Notes:

Jira ticket:  (-)
The upstream data:
Github releases:  https://github.com/paramiko/paramiko//releases
Diff between the latest and previous upstream releases
License: https://github.com/paramiko/paramiko//blob/master/LICENSE
Requirements:

setup.cfg:  https://github.com/paramiko/paramiko//blob/2.12.0/setup.cfg
setup.py:  https://github.com/paramiko/paramiko//blob/2.12.0/setup.py

Actions:

Notes:
*
Package's statistics

Priority D | effort: easy | Category: anaconda | subcategory:  | pkg_type: python
Outdated platfroms: 'linux-64', 'linux-aarch64', 'linux-ppc64le', 'osx-64', 'osx-arm64', 'win-64'
Latest version: 2.12.0
Release on PyPi:

version: 2.12.0
date: 2022-11-04T22:33:03

PyPi history
Popularity:

3 months downloads: 319731.0
All time:  2308411 downloads -  paramiko  2.12.0  SSH2 protocol library

**Anaconda Linter:**

The following problems have been found:
ERROR: /aggregate/paramiko-feedstock/recipe/meta.yaml:1: missing_pip_check: For pypi packages, pip check should be present in the test commands
WARNING: /aggregate/paramiko-feedstock/recipe/meta.yaml:19: avoid_noarch: noarch: python packages should be avoided
ERROR: /aggregate/paramiko-feedstock/recipe/meta.yaml:24: missing_wheel: For pypi packages, wheel should be present in the host section
WARNING: /aggregate/paramiko-feedstock/recipe/meta.yaml:42: missing_license_url: The recipe is missing a license_url
WARNING: /aggregate/paramiko-feedstock/recipe/meta.yaml:42: http_url: http://www.paramiko.org/ is not https
WARNING: /aggregate/paramiko-feedstock/recipe/meta.yaml:42: http_url: http://docs.paramiko.org/ is not https
WARNING: /aggregate/paramiko-feedstock/recipe/meta.yaml:42: missing_description: The recipe is missing a description
WARNING: /aggregate/paramiko-feedstock/recipe/meta.yaml:42: missing_doc_source_url: The recipe is missing a doc_source_url
Errors were found

Crender checks:

2.7.1:
- Missing wheel package in requirements
- Missing setuptools package in requirements
- Test section contains no 'commands'

Other checks:

[x] https://github.com/paramiko/paramiko//tree/2.12.0 exists

[ ] The upstream url error:
http://www.paramiko.org/
302
The home url must have HTTPS!

[ ] Check the pinnings

[ ] Changelog url error:
https://github.com/paramiko/paramiko//tree/2.12.0
200

[ ] Additional research
https://github.com/paramiko/paramiko//issues
200

[x] dev_url is present
https://github.com/paramiko/paramiko/

[ ] doc_url error:
http://docs.paramiko.org/
302
The doc_url must have HTTPS!

[ ] Verify that the build_number is correct

[ ] Verify if the package needs setuptools

[ ] Verify if the package needs wheel

[ ] NO pip in test

[ ] Verify the test section

[ ] Verify if the package is architecture specific or Noarch

[ ] Verify that private module are not mentioned on the recipe For example: (_private_module)

[x] license_file: LICENSE is present

[x] License: LGPL
[ ] License is spdx compliant

Check if the license identifier has correct name from the SPDX License List

Identifier

LGPL-2.0-only

LGPL-2.0-or-later

LGPL-2.1-only

LGPL-2.1-or-later

LGPL-3.0-only

LGPL-3.0-or-later

LGPLLR

[x] license_family LGPL is present

Checking the package CVEs:

../finder/temp/tmp.txt
Package CVEs:

Jira ticket:  (-)
The upstream data:
Github releases:  https://github.com/paramiko/paramiko//releases
Diff between the latest and previous upstream releases
License: https://github.com/paramiko/paramiko//blob/master/LICENSE
Requirements:

setup.cfg:  https://github.com/paramiko/paramiko//blob/2.12.0/setup.cfg
setup.py:  https://github.com/paramiko/paramiko//blob/2.12.0/setup.py

Actions:

Notes:
*
Package's statistics

Priority D | effort: easy | Category: anaconda | subcategory:  | pkg_type: python
Outdated platfroms: 'linux-64', 'linux-aarch64', 'linux-ppc64le', 'osx-64', 'osx-arm64', 'win-64'
Latest version: 2.12.0
Release on PyPi:

version: 2.12.0
date: 2022-11-04T22:33:03

PyPi history
Popularity:

3 months downloads: 319731.0
All time:  2308437 downloads -  paramiko  2.12.0  SSH2 protocol library

**Anaconda Linter:**

The following problems have been found:
ERROR: /aggregate/paramiko-feedstock/recipe/meta.yaml:1: missing_pip_check: For pypi packages, pip check should be present in the test commands
WARNING: /aggregate/paramiko-feedstock/recipe/meta.yaml:19: avoid_noarch: noarch: python packages should be avoided
ERROR: /aggregate/paramiko-feedstock/recipe/meta.yaml:24: missing_wheel: For pypi packages, wheel should be present in the host section
WARNING: /aggregate/paramiko-feedstock/recipe/meta.yaml:42: http_url: http://docs.paramiko.org/ is not https
WARNING: /aggregate/paramiko-feedstock/recipe/meta.yaml:42: missing_license_url: The recipe is missing a license_url
WARNING: /aggregate/paramiko-feedstock/recipe/meta.yaml:42: missing_description: The recipe is missing a description
WARNING: /aggregate/paramiko-feedstock/recipe/meta.yaml:42: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /aggregate/paramiko-feedstock/recipe/meta.yaml:42: http_url: http://www.paramiko.org/ is not https
Errors were found

Crender checks:

2.7.1:
- Missing wheel package in requirements
- Missing setuptools package in requirements
- Test section contains no 'commands'

Other checks:

[x] https://github.com/paramiko/paramiko//tree/2.12.0 exists

[ ] The upstream url error:
http://www.paramiko.org/
302
The home url must have HTTPS!

[ ] Check the pinnings

[ ] Changelog url error:
https://github.com/paramiko/paramiko//tree/2.12.0
200

[ ] Additional research
https://github.com/paramiko/paramiko//issues
200

[x] dev_url is present
https://github.com/paramiko/paramiko/

[ ] doc_url error:
http://docs.paramiko.org/
302
The doc_url must have HTTPS!

[ ] Verify that the build_number is correct

[ ] Verify if the package needs setuptools

[ ] Verify if the package needs wheel

[ ] NO pip in test

[ ] Verify the test section

[ ] Verify if the package is architecture specific or Noarch

[ ] Verify that private module are not mentioned on the recipe For example: (_private_module)

[x] license_file: LICENSE is present

[x] License: LGPL-2.1-or-later
[ ] License is spdx compliant

Check if the license identifier has correct name from the SPDX License List

Identifier

LGPL-2.1-or-later

[x] license_family LGPL is present

Checking the package CVEs:

../finder/temp/tmp.txt
Package CVEs:

Links:

Anaconda Recipes feedstock
Update branch
conda-forge recipe
PyPI
Diff between upstream and feature branch
Diff between origin and feature branch
The last merged PRs

Updating the recipe:
If the recipe needs additional modification the update branch can be modified. Note that the PR diffs are not updated with these changes.
git clone -b 2.12.0 git@github.com:AnacondaRecipes/paramiko-feedstock.git

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_8dvbc2bajx/clone/recipe/meta.yaml:1: missing_pip_check: For pypi packages, pip check should be present in the test commands
WARNING: /tmp/abs_8dvbc2bajx/clone/recipe/meta.yaml:19: avoid_noarch: noarch: python packages should be avoided
ERROR: /tmp/abs_8dvbc2bajx/clone/recipe/meta.yaml:24: missing_wheel: For pypi packages, wheel should be present in the host section
WARNING: /tmp/abs_8dvbc2bajx/clone/recipe/meta.yaml:42: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_8dvbc2bajx/clone/recipe/meta.yaml:42: http_url: http://www.paramiko.org/ is not https
WARNING: /tmp/abs_8dvbc2bajx/clone/recipe/meta.yaml:42: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_8dvbc2bajx/clone/recipe/meta.yaml:42: missing_description: The recipe is missing a description
Errors were found


N-Kannan Issue ID #8830

Issue ID #8830
In the docs\relational-databases\databases\revert-a-database-to-a-database-snapshot.md Updated the Invalid Colum Name
form SELECT dbid FROM sys.databases ...
to
SELECT database_id FROM sys.databases....
Please let me know if there anything i want to change.
It's my first Contribution to opensource so please let me know

Nice job, @N-Kannan. Thanks for taking the time to submit this PR! Your commit will be merged and this article update is in flight. After the updated article is published, GitHub will list you as an article contributor.
Thanks again for this feedback, your suggestions help improve our documentation.
#sign-off


Not accounting for different scrollbar widths in different browsers

There is a strange line around when using this component as seen in the screenshot.
After some investigation I noticed that these are the original browser scrollbars, that led me to the hardcoded -15px adjustment to hide the scrollbars in the code. And as you can see here the width of scrollbars is different between operating system https://codepen.io/sambible/post/browser-scrollbar-widths. So this plugin is only working for me on a Mac.

Should be fixed now


langchain-mongodb: Remove embedding retrieval from mongodb payload

Description
Returning the embedding is not necessary in the vector search functionality unless specified as a debugging step. This change defaults the behavior such that the server only returns the embedding key if explicitly requested, such as in the case of max_marginal_relevance_search.

[x] Add tests and docs: If you're adding a new integration, please include

Added test_from_documents_no_embedding_return

[x] Lint and test: Run make format, make lint and make test from the root of the package(s) you've modified. See contribution guidelines for more: https://python.langchain.com/docs/contributing/

cc: @shaneharvey, @blink1073 , @NoahStapp , @caseyclements


[itkwidgets / jupyterlite] Access to UI blocked by CORS policy

I will add this here even though I do not have a lot of information about it.
When I am running itkwidgets locally, I have no problems using this UI (other than the styling mentioned in #28). However, when trying to use the UI in JupyterLite (itkwidgets 1.0a6), I get an error:
Access to script at<EMAIL_ADDRESS>from origin 'https://kitware.github.io' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

the behavior for bootstrap UI:

Closing assuming this is the jsdelivr.com vs jsdeliver.net issue


VSCode 1.42.0: Activating extension fernandoescolar.vscode-solution-explorer failed due to an error

VS Code "about" info
Version: 1.42.0
Commit: ae08d5460b5a45169385ff3fd44208f431992451
Date: 2020-02-06T10:51:23.649Z
Electron: 6.1.6
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Linux x64 5.3.0-29-generic
Extension Host Log
[2020-02-07 20:54:35.082] [exthost] [error] Activating extension fernandoescolar.vscode-solution-explorer failed due to an error:
[2020-02-07 20:54:35.082] [exthost] [error] TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type undefined
	at validateString (internal/validators.js:107:11)
	at Object.join (path.js:1037:7)
	at new TemplateEngine (/home/ndotb/.vscode/extensions/fernandoescolar.vscode-solution-explorer-0.3.7/out/extension.js:2:29652)
	at new t.SolutionExplorerProvider (/home/ndotb/.vscode/extensions/fernandoescolar.vscode-solution-explorer-0.3.7/out/extension.js:1:102136)
	at t.activate (/home/ndotb/.vscode/extensions/fernandoescolar.vscode-solution-explorer-0.3.7/out/extension.js:1:99594)
	at Function._callActivateOptional (/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:710:141)
	at Function._callActivate (/usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:709:810)
	at /usr/share/code/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:708:960
	at async Promise.all (index 8)

When this started happening
It seemed to be working fine until code was updated to 1.42.

Workaround
If I save the open folder as a workspace and make code think it's a multi-root workspace, the path provided in the SolutionExplorerProvider constructor is populated and the extension works fine.
Source Reference
https://github.com/fernandoescolar/vscode-solution-explorer/blob/a8c1cdc87de28990136155712dc25a2f5d65823a/src/SolutionExplorerProvider.ts#L24


Added/Update new Enum and View required for Fortify Integration

Added/Update new Enum and View required for Fortify Integration

Please take a look at the PR for this branch, I think it addresses the final stuff for these changes.

Looks good!


Deprecation Warning (Carbon Component Manager) on OS X El Capitan

On OS X 10.10 El Capitan, the following warnings will show up when running soundmeter:
2016-01-09 22:21:11.616 python2.7[2268:35440] 22:21:11.614 WARNING:  140: This application, or a library it uses, is using the deprecated Carbon Component Manager for hosting Audio Units. Support for this will be removed in a future release. Also, this makes the host incompatible with version 3 audio units. Please transition to the API's in AudioComponent.h.

Just for record: spatialaudio/python-sounddevice/issues/10 indicates that:

I think we'll just have to wait for a new PortAudio version, until then you'll have to ignore this message.


Generate custom-icon-webfont on each provision or update-prod-static.

RFCR @pweaver. I have made sure that references in zproject/settings.py and elsewhere, checked via grep.

I have tested with doing a ./tools/build-release-tarball and gut out its innard:
(zulip-py3-venv) ~/rht_zulip/foo/zulip-server-webfont$ ls prod-static/serve/generated/icons/fonts
zulip-icons.01941e73afa6.eot  zulip-icons.b61502b7f02b.svg    zulip-icons.de770e4232f0.woff  zulip-icons.svg  zulip-icons.woff
zulip-icons.03d466915d50.ttf  zulip-icons.d36be9e1624b.woff2  zulip-icons.eot                zulip-icons.ttf  zulip-icons.woff2

Got this error when trying to upgrade-zulip-from-git to this PR:
Traceback (most recent call last):
  File "./tools/update-prod-static", line 53, in <module>
    stdout=fp, stderr=fp)
  File "/usr/lib/python3.4/subprocess.py", line 561, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['./tools/generate-custom-icon-webfont']' returned non-zero exit status 7
Traceback (most recent call last):
  File "/home/zulip/deployments/2017-11-16-11-31-29/scripts/lib/upgrade-zulip-stage-2", line 82, in <module>
    preexec_fn=su_to_zulip)
  File "/usr/lib/python3.4/subprocess.py", line 561, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['./tools/update-prod-static', '--authors-not-required', '--prev-deploy', '/home/zulip/deployments/current']' returned non-zero exit status 1
Traceback (most recent call last):
  File "/home/zulip/deployments/current/scripts/upgrade-zulip-from-git", line 67, in <module>
    deploy_path, "--from-git"] + deploy_options)
  File "/usr/lib/python3.4/subprocess.py", line 561, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['sudo', '/home/zulip/deployments/2017-11-16-11-31-29/scripts/lib/upgrade-zulip-stage-2', '/home/zulip/deployments/2017-11-16-11-31-29', '--from-git']' returned non-zero exit status 1

No logfile in /var/log/zulip/upgrade.log. I suspect this is due to permission problem.

One hypothesis of the error: upgrade-zulip-from-git uses the old version of package.json without the webfonts-generator in production dependencies, and so ./tools/generate-custom-icon-webfont fails to run.
I suppose the only way to fix it is to add webfonts-generator first and vendor it into release, then upgrade from that release into this one?

Probably not. upgrade-zulip-from-git definitely uses the new package.json. If there are permission errors creating the log file, the might itself be enough to crash the upgrade script.

This doesn't update yarn.lock; that's probably the issue with dependencies, right?

@timabbott I don't think so? I don't think yarn.lock cares if dependencies are in dependencies or dev dependencies. It should generate an identical file if they move from one to another.
@rht I think you can also remove the webfont-generator from devDependencies. devDependencies are additional dependencies on a dev install.

Also, it looks like yarn.lock hasn't been updated in a while and an update should probably be pushed to master.

@pweaver sounds good; remind me the procedure for that?

Run yarn install in the top level directory and it should update the yarn.lock which can be committed.

@rht I think you can also remove the webfont-generator from devDependencies. devDependencies are additional dependencies on a dev install.

Addressed.

Run yarn install in the top level directory and it should update the yarn.lock which can be committed.

Addressed as well.

Updating the yarn.lock via yarn install fixed the upgrade-zulip-from-git issue for me.
2017-11-17 00:09:18,374 upgrade-zulip-stage-2: Upgrade complete!
Cleaning unused deployments...
Deployments cleaned successfully...
Cleaning orphaned/unused caches...
Cleaning unused venv caches...
Cleaning unused node modules caches...
Cleaning unused emoji caches...
Done!

This looks good, but you'll need to rebase (I just merged some other changes to yarn.lock).

Rebased.

Merged, after updating PROVISION_VERSION for the merge conflict, thanks @rht!
@synicalsyntax FYI; I'd appreciate a post-commit review from you on this :).


Scrape committee membership

Although @dwillis did a lot of work on manually collecting committee membership, there is a lot of new data and some errors. We have a scraper, but now that the data has membership start dates and links to sources, the scraper needed to be updated to preserve existing data in the file.
I updated the scraper. The result was a lot of changes. So I ran it in stages (full committees first, then (missing) subcommittees we didn't have, then subcommittees we already had) so we have at least one commit with a readable diff.
I also added the House Select Committee on the Climate Crisis and the House Select Committee on the Modernization of Congress to the metadata since they are on the Clerk site and have members.

... I'm not sure how best to review this since one of the commits has a huge diff.
I think we also lost some ex officiio entries which are indicated in source data @dwillis used but isn't in the clerk committee data.

I can live with losing the Ex Officio members, tbh.

@JoshData I'm in the process of reviewing these commits. Thanks for doing this!

Here's a fun one: SSCM26, which has different information about the minority members in the Senate XML vs. the committee site.

@JoshData I've done some clean-up on these files. Lemme know if that helps.

Thanks. I'll take a look. I'm traveling this week and most of next so I'm not sure if I'll be able to look soon tho.

@JoshData Any issues with this?

Sorry, lost track, all good. Merging.


File "lynda-dl.py", line 8, in

Hi,
Downloaded new version of lynda-dl, and can't download any course:
$ python lynda-dl.py -u xxxxxx -p xxxxx -o xxxx.org https://www.lynda.com/FileMaker-Pro-tutorials/Learning-FileMaker/681078-2.html
Traceback (most recent call last):
File "lynda-dl.py", line 8, in
import lynda
File "/mnt/c/Users/uzver/lynda-dl/lynda/init.py", line 5, in
from ._extractor import LyndaInfoExtractor
File "/mnt/c/Users/uzver/lynda-dl/lynda/_extractor.py", line 25, in
from ._sanitize import (
File "/mnt/c/Users/uzver/lynda-dl/lynda/_sanitize.py", line 8, in
import six
ImportError: No module named six
Tried in Windows 10 cmd and in Ubuntu shell for Windows 10. The same error for any course.

@Mozenrat you need to install unidecode, six i will update the requirements soon.

pip install unidecode
pip install six


Update/clearfix

Mixin added 'clearfix' to resolve issues with elements containing float elements having no height.
Clearfix added on .nav-wrapper to resolve brand-logo position when centred and .nav-wrapper only containing float elements

Hey there 👋
We are happy to see, that you have created a pull request to fix a problem or add a feature or did something else.
Unfortunately does your PR include compiled files. Please do not edit materialize.css, materialize.js or any .html file directly! Those files are automatically generated. You should edit the source files in the locations below instead. Also make sure to check out our CONTRIBUTING GUIDE!
/materialize/sass/
/materialize/js/
/materialize/jade/page-contents/

We won't look into this, unless you modify your PR, so that it matches with our CONTRIBUTING guidelines and resolve the conflicts.


Which drupal oauth2 server module works with this?

Would this work for d8?
https://www.drupal.org/project/oauth2_server

Hey there,
This has been tested on the latest stable release for D7

I confirm this library also works with the Drupal 8 version of oauth2_server.


Unlock orientation when lightbox is open

Fixes https://github.com/bluesky-social/social-app/issues/624
Unlocks device rotation when lightbox is open
Details:

Screen orientation is locked to portrait normally. on iOS this is acheived via the config plugin, on Android we just have to call lockAsync as soon as it starts up
Locking/unlocked achieved via an effect in the lightbox component
Safe area for iOS/Android 15 was changed to not include the sides either - this was 0 anyway for portrait mode, and now allows it to be full-screen when rotated
Lightbox state (so zoom, position etc) is cleared via key whenever an orientation change happens to ensure that it doesn't get into a wonky state
There's some sort of double nav bar inset when sideways on Android <15. It's entirely outside of the app, not anything we're doing as far as I can tell. Not sure what's up with that, I just painted it black.

https://github.com/user-attachments/assets/f81f8fe9-d654-4eaf-bfb4-5be916d956fb
https://github.com/user-attachments/assets/05fe6a97-c85c-4fae-bc66-405eb5e7817e
Test plan
Test iOS, Android <=14, Android 15
Test rotating, test lightbox gesture behaviour while/after rotating
Try and test on device where possible

This transition feels very glitchy. Can we do something smarter here?
https://github.com/user-attachments/assets/6ef877ec-0124-49db-80a0-b7e5a75b5f7b
For example maybe we can always wait to update the lock state before starting the animated transition.

And about this — I understand why it happens but is there any way at all to make the rest of the app "keep the lock"? So that there's no "rotated feed" underneath it.
https://github.com/user-attachments/assets/47197a9f-614b-4e1b-996e-c167908d96aa

pushed a few fixes which should slightly help with cases above

Still a little bit glitchy but let's get this in and iterate.

@gaearon you could maybe use the rotation sensor data? that way you could handle the rotation yourselves just for the lightbox, but keep the app in locked portrait mode in the OS's perspective
ofc while respecting the user's current rotation lock

as for the extra inset on android, i'm not sure how this works in RN but double insets (natively) usually mean that they were not consumed higher up the tree
e.g. if a parent applies nav bar insets (for whatever sides), it shall also consume them, so if a child does that again, it gets no insets applied for the consumed sides.


Improve article 2210.00581

Exact location of issue
Article fails to convert
Problem details
According to the log, it appears the LaTeX 3 interpretation fails badly here, an unknown \ExplSyntaxOn being the first error.

Thanks for the report! I updated the issue description with the details.

After a fresh reconversion of ar5iv with latexml v0.8.8, this is now resolved - the article gets healthy HTML:
https://ar5iv.labs.arxiv.org/html/2210.00581


fix: classList.toString don't remove extra whitespace characters

👍  thx. Will merge and publish soon.


Increment global version number to 14.0.1

I think this mismatch is causing the build to fail at the moment for tagged build. Adding also test cases for NET 8.0 OpenAPI generation.

I think this PR fixes https://github.com/RicoSuter/NSwag/issues/4699

I doubt 14.0.1 is fixable at this point. It is much cleaner to just release 14.0.2.

Should be possible to recreate the tag and use same version number.


Included member of private channels

It would be great if one could get and send messages to the private channels that a bot is a member.

Private channels are apparently included by Slack in the API payload under groups.

This was actually really helpful.. README is a bit lacking in the explanation for this.. anyone think this is worth a PR ?


HTTP parser/serializer error

router.get("json") { req -> Future<Response> in
	let client = try req.make(Client.self)

	// Return the response from this URL
	return client.get("http://example.vapor.codes/json")
}

The above should be returning the HTTP response from example.vapor.codes to Vapor's client.
Instead a response with the following body appears:
Content-Length: 87

{"array":[0,1,2,3],"dict":{"lang":"Swift","name":"Vapor"},"number":123,"string":"test"}

This content-length header should be part of the headers section but is found as part of the body section instead.

Related?
https://github.com/vapor/vapor/issues/1481

I believe this was fixed with #220 (I remember seeing something about an extraneous /r/n which would explain this)


docs: README minified dist script in

#560 on which I've left a comment

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

https://cdn.minifyjs.xyz/blockstack/blockstack.min.js (I've created this service to automatically update based off master every hour at X:00 and to be served from many locations based on request origin location)

I've made a comment on the issue you create: https://github.com/blockstack/blockstack.js/issues/560#issuecomment-442922635

@JeremiGendron Thanks for getting this convo started and this initial PR work.
I'm closing this PR since we now have a CDN dist snippet being generated during our build process: https://github.com/blockstack/blockstack.js/blob/master/mdincludes/script-dist-file.md


assertion of style() for shallow()/render()

I think there is bug (or perhaps a mis-documentation) of the style() assertion, namely that it only works if you mount() the component.
describe("Chai-enzyme style test", function() {

    it("should do style test on shallow component", function() {
        const component = (

Hello, World

        );
        const wrapper = shallow(component);
        expect(wrapper).to.have.style("color", "red");
    });

    it("should do style test on rendered component", function() {
        const component = (

Hello, World

        );
        const wrapper = render(component);
        expect(wrapper).to.have.style("color", "red");
    });

    it("should do style test on mounted component", function() {
        const component = (

Hello, World

        );
        const wrapper = mount(component);
        expect(wrapper).to.have.style("color", "red");
    });
});

Result is
Chai-enzyme style test
    ✖ should do style test on shallow component
    ✖ should do style test on rendered component
    ✔ should do style test on mounted component

Finished in 0.025 secs / 0.017 secs

SUMMARY:
✔ 1 test completed
✖ 2 tests failed

FAILED TESTS:
  Chai-enzyme style test
    ✖ should do style test on shallow component
      PhantomJS 2.1.1 (Mac OS X 0.0.0)
    Window is not a constructor (evaluating '(0, _cheerio2.default)(this.wrapper.html())')
    get@/Users/.../test.spec.js:38342:44 <- webpack:///~/chai-enzyme/build/ShallowTestWrapper.js:127:0
    style@/Users/.../test.spec.js:38276:19 <- webpack:///~/chai-enzyme/build/ShallowTestWrapper.js:61:0
    /Users/.../test.spec.js:37455:37 <- webpack:///~/chai-enzyme/build/assertions/generic.js:17:0
    /Users/...test.spec.js:37907:24 <- webpack:///~/chai-enzyme/build/ChaiWrapper.js:199:0
    /Users/.../test.spec.js:32360:31 <- webpack:///~/chai/lib/chai/utils/addMethod.js:41:0
    /Users/.../test.spec.js:78:50 <- webpack:///test.spec.js:16:38

    ✖ should do style test on rendered component
      PhantomJS 2.1.1 (Mac OS X 0.0.0)
    undefined is not a constructor (evaluating '_cheerio2.default.load(html)')
    render@/Users/.../test.spec.js:19762:33 <- webpack:///~/enzyme/build/index.js:61:0
    /Users/.../test.spec.js:88:43 <- webpack:///test.spec.js:25:31

Actually according to our passing test suit we have style support for each render method.
  #style
    ✓ (shallow): chains
    ✓ (mount): chains
    ✓ (render): chains
    (name)
      ✓ (shallow): passes when the actual matches the expected
      ✓ (mount): passes when the actual matches the expected
      ✓ (render): passes when the actual matches the expected
      ✓ (shallow): passes negated when the actual does not match the expected
      ✓ (mount): passes negated when the actual does not match the expected
      ✓ (render): passes negated when the actual does not match the expected
      ✓ (shallow): fails when the actual does not match the expected
      ✓ (mount): fails when the actual does not match the expected
      ✓ (render): fails when the actual does not match the expected
      ✓ (shallow): fails when the actual is undefined
      ✓ (mount): fails when the actual is undefined
      ✓ (render): fails when the actual is undefined
    (name, value)
      ✓ (shallow): passes when the actual matches the expected
      ✓ (mount): passes when the actual matches the expected
      ✓ (render): passes when the actual matches the expected
      ✓ (shallow): passes negated when the actual does not match the expected
      ✓ (mount): passes negated when the actual does not match the expected
      ✓ (render): passes negated when the actual does not match the expected
      ✓ (shallow): fails when the actual does not match the expected
      ✓ (mount): fails when the actual does not match the expected
      ✓ (render): fails when the actual does not match the expected

Will have a closer look to your example.

Running your tests on master I get these results:
  Chai-enzyme style test
    ✓ (shallow): should do style test on shallow component
    ✓ (mount): should do style test on shallow component
    ✓ (render): should do style test on shallow component
    ✓ (shallow): should do style test on rendered component
    ✓ (mount): should do style test on rendered component
    ✓ (render): should do style test on rendered component
    ✓ (shallow): should do style test on mounted component
    ✓ (mount): should do style test on mounted component
    ✓ (render): should do style test on mounted component

What versions of chai, chai-enzyme, enzyme & cheerio are you running?

@ayrton I was running my tests with karma and PhantomJS. If I run these specific tests with jsdom, then all of the tests pass. Since I prefer to run all my tests with the same test runner, I want to stick with PhantomJS and karma if possible. So, I will dive further into this and let you know if anything pops.

@ItsCosmo which version of phantom? if 1.x, are you at least using es5-shim so that it has .bind etc? It might also be that phantom doesn't support strict mode, and cheerio might rely on that behavior.

@ayrton I modified my karma configuration, so that I am using jsdom now. I am using several of chai-enzyme assertions, but style() is only one hanging me up, even with jsdom. The error is different, though:
TypeError: (0 , _cheerio2.default) is not a function  (for shallow test)
TypeError: _cheerio2.default.load is not a function (for render test)

Its looking like karma may be the culprit. I am happy to provide my karma.config.js and a minimal test spec which exhibits the problem, and package.json if required.

Were you using Webpack to do module bundling for karma, by any chance? I encountered essentially the same issue when using the checked assertion on a shallow render.
Enzyme's documentation suggests configuring Webpack to treat Cheerio as an external module, which was the root cause of my problem. I was able to get it working by resolving Cheerio properly using Webpack's JsonLoader.
If you're not using Webpack, I don't know what the problem is, sorry! But maybe someone else will come across this issue for the same reason I did.

Thanks for a very helpful response. This solved my issue. Specifically, I removed the line:
cheerio': 'window',
from externals configuration, and added the line:
{ test: /\.json/, loader: "json"}
to the module.loaders configuration

It happened to me when I try to check the attribute src of an image tag. The solution provided by @dpoindexter and @ItsCosmo works like a charm.


Support connecting through an HTTP Proxy

We want to use the Java SDK on machines within our network, which is behind a firewall.  One that is quite restrictive.  In order to get out to external sites, we need to go through a proxy.
I have added the support to the core library, so that when it creates the Jersey client connection, it is possible to use a Proxy when opening the connection.  I have added support for two properties: http.proxyHost and http.proxyPort.  If these are defined, then support for proxied connections is added.  Otherwise, the original functionality is used.
This is how I am using this from my code.

Can one of the admins verify this patch?

Hi @hildo, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.azure.com.

TTYL, AZPRBOT;


OpenTTD build fail with Yosemite

The build process fails when trying to bundle the application :

==> make bundle
make: *** No rule to make target `bundle'.  Stop.

closing as stale


Install Desktop App: Wrong path in Windows File Explorer troubleshooting

In the troubleshooting guide for the desktop app, the windows paths are showing double backslashes \\
%APPDATA%\\Mattermost
Which is wrong - correct would be just one:
%APPDATA%\Mattermost
I found the issues on these two lines:
https://github.com/mattermost/docs/blob/70b50ccb6dbc7bb282034171a46f16077dba55d3/source/collaborate/install-desktop-app.rst?plain=1#L242
https://github.com/mattermost/docs/blob/70b50ccb6dbc7bb282034171a46f16077dba55d3/source/collaborate/install-desktop-app.rst?plain=1#L259

@cwarnermm Yeah they're should only be one backslash in those paths.

Perfect - thanks, @devinbinnie. @Movion - Are you open to creating a docs PR with the necessary changes?

@cwarnermm sure, but I just signed the "Mattermost Contributor Agreement", idk how fast I'm allowed to make a PR

@Movion - you're most welcome to get started any time (even if you hadn't signed the contributor agreement yet! It would be needed by the time we're ready to merge your changes into the docs code base).
Let us know here if you have any questions about the docs changes -- happy to help!

I hope I did everything right.. please check and let me know if I have to improve or change anything :s


Netflix Movies and TV Shows

Issue Title : #66

Info about the related issue (Aim of the project)

To understand what content is available in different countries ,Identify similar content by matching text-based features ,Network analysis of Actors / Directors and find interesting insights ,Does Netflix has more focus on TV Shows than movies in recent years?. Perform EDA.

[x] SWOC Participant

[ ] JWOC Participant

[ ] Contributor

Name: Sankalp Srivastava

GitHub ID: www.github.com/sankalp-srivastava

(Mention these details are must)
Closes: #66
Describe the add-ons or changes you've made
Give a clear description of what have you added or modifications made
Type of change
What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Ran the complete notebook file on kaggle.
Checklist:

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have added things that prove my fix is effective or that my feature works.
[x] Any dependent changes have been merged and published in downstream modules.

@sankalp-srivastava your PR is approved and merged.


Update to alpine 3.8 for arm support

Port #84 to v2.7.0 branch
Chrry-pick 6b2c05375d26958518b8915d2ee7ba28fd0df376

Addresses https://github.com/docker-library/official-images/pull/5141#discussion_r244415104


Tweak documentation and blog

Description
Closes #2843 #2847
Provided guidelines for tags and updated blog posts to match tags. Also updated documentation SEO.

Readiness checklist

[ ] I added/updated unit tests.
[ ] I added/updated integration/compatibility tests.
[ ] I added/updated comments and checked rendering.
[ ] I made spot refactorings.
[ ] I updated user documentation.
[ ] I ran task all, and it passed.
[x] I ensured that PR title is good enough for the changelog.
[x] (for maintainers only) I set Reviewers (@FerretDB/core), Labels, Project and project's Sprint fields.
[x] I marked all done items in this checklist.

Closes https://github.com/FerretDB/FerretDB/issues/2843 https://github.com/FerretDB/FerretDB/issues/2847

That will not work, it should be one "Closes #number" per line. "Conform PR" action will also fail.

@Fashander Please try now


fix(packed): Fix a couple of issues

Draft until I can actually test the map.
Unable to test anything because of the PR #29391 That broke forcemap.

About the PR

Removed 9 AME parts from the AME room. Reducing round start core count from four to one.
Relocated the shutter button in bar.
Why / Balance

Fixes #27225
Fixes #29409
Does not fix #27868 because it is not an actual issue.
Technical details

Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Before: https://map.spacestation14.com/?map=packed
After:

Breaking changes

Changelog

It works :D


Fixed typos

Changes

adds: ...

fixed: fixed typos in docs/CONTRIBUTING.md and goals/command.md

improvements: ...

Check off the following

[x] I have tested my changes with the current requirements
[x] My Code follows the pep8 code style.

Awesome thanks you, and sorry for my broken English, will try to improve


linux_testing: 6.6-rc3 -> 6.6-rc4 (plus some rt updates)

Description of changes
Hardened update script failed.  Didn't look into it.
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@OfBorg eval

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

8 packages built:

linux-rt (linuxKernel.kernels.linux_rt_5_4)
linux-rt.dev (linuxKernel.kernels.linux_rt_5_4.dev)
linuxKernel.kernels.linux_rt_5_10
linuxKernel.kernels.linux_rt_5_10.dev
linuxKernel.kernels.linux_rt_5_15
linuxKernel.kernels.linux_rt_5_15.dev
linux_testing (linuxKernel.kernels.linux_testing)
linux_testing.dev (linuxKernel.kernels.linux_testing.dev)

Ah, https://github.com/NixOS/nixpkgs/pull/257205 needs backporting first.


Support new RoleV2 for parent user invite flow

Describe the issue:
We have introduced a feature for inviting parent organization users to child organization.
swagger:
https://github.com/wso2/identity-api-server/blob/master/components/org.wso2.carbon.identity.api.server.organization.user.invitation.management/org.wso2.carbon.identity.api.server.organization.user.invitation.management.v1/src/main/resources/organization-user-invitation.yaml
This API has given the capability to assign roles while inviting users, but it's not implemented.
Need to support roles assignment for invitation based on the new role model

The improvement can be made here - https://github.com/wso2-extensions/identity-organization-management/blob/main/components/org.wso2.carbon.identity.organization.user.invitation.management/src/main/java/org/wso2/carbon/identity/organization/user/invitation/management/InvitationCoreServiceImpl.java#L190~L197

@Kanapriya can you create a separate issue to track the UI improvements?


removed RunspaceConfiguration support

For PSCore6, we are only supporting InitialSessionState.  The RunspaceConfiguration api was already made internal.  This PR removes all the code related to RunspaceConfiguration.  This also means that some public apis have changed.  Was deciding between leaving the RunspaceConfiguration parameters and throwing Unsupported, but thought it was better to have it a compile time error.  This should simplify the code base.

@SteveL-MSFT powershell.Invoke() (maybe some other part of the powershell class) goes through RunspaceConfiguration, for example the following script:
$ps = [powershell]::Create()
$ps.AddScript("gcm")
$ps.Invoke()

Did you change it to not depend on RunspaceConfiguration?

@daxian-dbw yes, I changed it to use InitialSessionState

@SteveL-MSFT Awesome! Can you please point me to the part of changes that related to powershell.invoke()?

@daxian-dbw after ripping out the RunspaceConfig code, to get it working (and those tests passing) I create a ISS instance with defaults.

@PowerShell/powershell-committee reviewed this and agreed on removal on RunspaceConfiguration code

            {"Get-PSSnapin",                      new SessionStateCmdletEntry("Get-PSSnapin", typeof(GetPSSnapinCommand), helpFile) },

You can delete this line.

Refers to: src/System.Management.Automation/engine/InitialSessionState.cs:5572 in 6121d89. [](commit_id = 6121d891d98cf4f813ac013ef8faa1bc8e68296d, deletion_comment = False)

            {"Get-PSSnapin",                      new SessionStateCmdletEntry("Get-PSSnapin", typeof(GetPSSnapinCommand), helpFile) },

And the *PSSnapin lines.

In reply to: 336302306 [](ancestors = 336302306)

Refers to: src/System.Management.Automation/engine/InitialSessionState.cs:5572 in 6121d89. [](commit_id = 6121d891d98cf4f813ac013ef8faa1bc8e68296d, deletion_comment = False)

I believe all feedback has been addressed

There is also a comment at https://github.com/PowerShell/PowerShell/pull/4942#discussion_r145203074.

New new Update-FormatData with invalid xml is causing a problem with PowerShellGet tests to fail.  I repro'd it with binaries built from master so it's not the result of these changes.  Created https://github.com/PowerShell/PowerShell/issues/5154 to track.


Continously Vulkan crashes

Godot version
v4.1.dev1.official.db1302637
System information
Windows 10, Vulkan, GPU AMD Radeon R7 M260
Issue description
Godot 4.1.dev1 version randomly get stuck, Console shows that Vulkan driver gets lost, and only option is force-close of the program.
It happens in different situations and with no clear patron: changing a texture, importing a resource, rotating an scene, navigating in project folders, asigning materials...
Tried in Forward and Mobile renderer. Same issue.
I took a couple of screenshots. Always same error:

Of course, drivers are updated:

I don't know a way to get any kind of trace or more information
Steps to reproduce
Not able to. It's random.
Minimal reproduction project
N/A

Thanks for the report! Consolidating this in https://github.com/godotengine/godot/issues/71929.


supported_dtypes np.half/float16

Is there any reason why np.half/float16 is not in the supported_dtypes -> https://github.com/scipy/scipy/blob/5f4c4d802e5a56708d86909af6e5685cd95e6e66/scipy/sparse/sputils.py#L13
it gets upcasted to float32 every time when convert my dok_matrix to csr, which in my case of 10000x10000 matrix is big difference in terms of memory?

I had the same problem and when i checked last time then another similar issue https://github.com/scipy/scipy/issues/2111 was addressed before. however i am providing a PR if maintainers feel to add this.

I had the same problem and when i checked last time then another similar issue https://github.com/scipy/scipy/issues/2111 was addressed before. however i am providing a PR if maintainers feel to add this.

most of the underlying Fortran libs don't support half precision. Hence there is little to be gained for allowing it since at some point they will be upcasted anyways.

most of the underlying Fortran libs don't support half precision. Hence there is little to be gained for allowing it since at some point they will be upcasted anyways.

with reference to this issue , similar issues have been raised before https://github.com/scipy/scipy/issues/2111.
considering the time factor it may been neglected in scipy community.
Look at this https://stackoverflow.com/questions/24587433/why-does-numpy-float16-break-the-openblas-atlas-functionalities fir the the reason of avoiding half precision.
I was able to reproduce this again

with reference to this issue , similar issues have been raised before https://github.com/scipy/scipy/issues/2111.
considering the time factor it may been neglected in scipy community.
Look at this https://stackoverflow.com/questions/24587433/why-does-numpy-float16-break-the-openblas-atlas-functionalities fir the the reason of avoiding half precision.
I was able to reproduce this again

Thank you for the explanation and info on the topic. I guess my only chance is to find a workaround and go on with float32 and higher unnecessary memory consumption. I am storing distances between points on a mercator map, so I would never go past 65504.0

Thank you for the explanation and info on the topic. I guess my only chance is to find a workaround and go on with float32 and higher unnecessary memory consumption. I am storing distances between points on a mercator map, so I would never go past 65504.0