Don't support node v6.2.1

if i want to use it on node v6.2.1,wen i install it , well look some error info.like this:
><EMAIL_ADDRESS>install /home/nodeserver/xmltool/myapp/node_modules/node-expat
> node-gyp rebuild

make: Entering directory `/home/nodeserver/xmltool/myapp/node_modules/node-expat/build'
  CC(target) Release/obj.target/expat/deps/libexpat/lib/xmlparse.o
  CC(target) Release/obj.target/expat/deps/libexpat/lib/xmltok.o
  CC(target) Release/obj.target/expat/deps/libexpat/lib/xmlrole.o
  AR(target) Release/obj.target/deps/libexpat/libexpat.a
  COPY Release/libexpat.a
  CXX(target) Release/obj.target/node_expat/node-expat.o
In file included from ../node-expat.cc:1:
../../nan/nan.h:43:3: error: #error This version of node/NAN/v8 requires a C++11 compiler
In file included from /root/.node-gyp/6.2.1/include/node/node.h:42,
                 from ../../nan/nan.h:47,
                 from ../node-expat.cc:1:
/root/.node-gyp/6.2.1/include/node/v8.h:341: error: expected unqualified-id before 'using'
/root/.node-gyp/6.2.1/include/node/v8.h: In constructor 'v8::MaybeLocal<T>::MaybeLocal()':
/root/.node-gyp/6.2.1/include/node/v8.h:358: error: 'nullptr' was not declared in this scope
/root/.node-gyp/6.2.1/include/node/v8.h: In member function 'bool v8::MaybeLocal<T>::IsEmpty() const':
/root/.node-gyp/6.2.1/include/node/v8.h:365: error: 'nullptr' was not declared in this scope
/root/.node-gyp/6.2.1/include/node/v8.h: In member function 'bool v8::MaybeLocal<T>::ToLocal(v8::Local<S>*) const':
/root/.node-gyp/6.2.1/include/node/v8.h:369: error: 'nullptr' was not declared in this scope
/root/.node-gyp/6.2.1/include/node/v8.h: In member function 'bool v8::WeakCallbackInfo<T>::IsFirstPass() const':
/root/.node-gyp/6.2.1/include/node/v8.h:437: error: 'nullptr' was not declared in this scope
/root/.node-gyp/6.2.1/include/node/v8.h: At global scope:
/root/.node-gyp/6.2.1/include/node/v8.h:477: error: expected unqualified-id before 'using'
/root/.node-gyp/6.2.1/include/node/v8.h: In constructor 'v8::Global<T>::Global()':
/root/.node-gyp/6.2.1/include/node/v8.h:809: error: 'nullptr' was not declared in this scope
/root/.node-gyp/6.2.1/include/node/v8.h: In constructor 'v8::Global<T>::Global(v8::Global<T>&&)':
/root/.node-gyp/6.2.1/include/node/v8.h:834: error: 'nullptr' was not declared in this scope
/root/.node-gyp/6.2.1/include/node/v8.h: In member function 'v8::Global<T>& v8::Global<T>::operator=(v8::Global<S>&&)':
/root/.node-gyp/6.2.1/include/node/v8.h:846: error: 'nullptr' was not declared in this scope
/root/.node-gyp/6.2.1/include/node/v8.h: At global scope:
/root/.node-gyp/6.2.1/include/node/v8.h:871: error: expected unqualified-id before 'using'
/root/.node-gyp/6.2.1/include/node/v8.h:1108: error: 'nullptr' was not declared in this scope
/root/.node-gyp/6.2.1/include/node/v8.h:1114: error: 'nullptr' was not declared in this scope
/root/.node-gyp/6.2.1/include/node/v8.h: In member function 'v8::MaybeLocal<v8::Object> v8::Function::NewInstance(v8::Local<v8::Context>) const':
/root/.node-gyp/6.2.1/include/node/v8.h:3246: error: 'nullptr' was not declared in this scope
/root/.node-gyp/6.2.1/include/node/v8.h: At global scope:
/root/.node-gyp/6.2.1/include/node/v8.h:4463: error: 'nullptr' was not declared in this scope
/root/.node-gyp/6.2.1/include/node/v8.h:4479: error: 'nullptr' was not declared in this scope
/root/.node-gyp/6.2.1/include/node/v8.h: In member function 'v8::Local<T> v8::MaybeLocal<T>::ToLocalChecked()':
/root/.node-gyp/6.2.1/include/node/v8.h:7348: error: 'nullptr' was not declared in this scope
In file included from ../../nan/nan.h:190,
                 from ../node-expat.cc:1:
../../nan/nan_maybe_43_inl.h: At global scope:
../../nan/nan_maybe_43_inl.h:13: error: expected unqualified-id before 'using'
../../nan/nan_maybe_43_inl.h:16: error: expected unqualified-id before 'using'
../../nan/nan_maybe_43_inl.h:19: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:24: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:31: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:36: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:41: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:46: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:51: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:59: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:64: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:69: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:76: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:83: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:91: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:98: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:108: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:114: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:118: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:125: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:130: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:135: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:139: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:145: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:150: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:156: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:162: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:168: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:174: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:180: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:186: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:194: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:201: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:205: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:209: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:213: error: expected initializer before '<' token
../../nan/nan_maybe_43_inl.h:217: error: expected initializer before '<' token
../node-expat.cc:498: error: expected '}' at end of input
../../nan/nan_callbacks_12_inl.h:167: warning: 'void Nan::imp::FunctionCallbackWrapper(const v8::FunctionCallbackInfo<v8::Value>&)' defined but not used
../../nan/nan_callbacks_12_inl.h:181: warning: 'void Nan::imp::GetterCallbackWrapper(v8::Local<v8::Name>, const v8::PropertyCallbackInfo<v8::Value>&)' defined but not used
../../nan/nan_callbacks_12_inl.h:197: warning: 'void Nan::imp::SetterCallbackWrapper(v8::Local<v8::Name>, v8::Local<v8::Value>, const v8::PropertyCallbackInfo<void>&)' defined but not used
../../nan/nan_callbacks_12_inl.h:253: warning: 'void Nan::imp::PropertyGetterCallbackWrapper(v8::Local<v8::Name>, const v8::PropertyCallbackInfo<v8::Value>&)' defined but not used
../../nan/nan_callbacks_12_inl.h:270: warning: 'void Nan::imp::PropertySetterCallbackWrapper(v8::Local<v8::Name>, v8::Local<v8::Value>, const v8::PropertyCallbackInfo<v8::Value>&)' defined but not used
../../nan/nan_callbacks_12_inl.h:290: warning: 'void Nan::imp::PropertyEnumeratorCallbackWrapper(const v8::PropertyCallbackInfo<v8::Array>&)' defined but not used
../../nan/nan_callbacks_12_inl.h:306: warning: 'void Nan::imp::PropertyDeleterCallbackWrapper(v8::Local<v8::Name>, const v8::PropertyCallbackInfo<v8::Boolean>&)' defined but not used
../../nan/nan_callbacks_12_inl.h:323: warning: 'void Nan::imp::PropertyQueryCallbackWrapper(v8::Local<v8::Name>, const v8::PropertyCallbackInfo<v8::Integer>&)' defined but not used
../../nan/nan_callbacks_12_inl.h:428: warning: 'void Nan::imp::IndexGetterCallbackWrapper(uint32_t, const v8::PropertyCallbackInfo<v8::Value>&)' defined but not used
../../nan/nan_callbacks_12_inl.h:444: warning: 'void Nan::imp::IndexSetterCallbackWrapper(uint32_t, v8::Local<v8::Value>, const v8::PropertyCallbackInfo<v8::Value>&)' defined but not used
../../nan/nan_callbacks_12_inl.h:464: warning: 'void Nan::imp::IndexEnumeratorCallbackWrapper(const v8::PropertyCallbackInfo<v8::Array>&)' defined but not used
../../nan/nan_callbacks_12_inl.h:480: warning: 'void Nan::imp::IndexDeleterCallbackWrapper(uint32_t, const v8::PropertyCallbackInfo<v8::Boolean>&)' defined but not used
../../nan/nan_callbacks_12_inl.h:496: warning: 'void Nan::imp::IndexQueryCallbackWrapper(uint32_t, const v8::PropertyCallbackInfo<v8::Integer>&)' defined but not used
make: *** [Release/obj.target/node_expat/node-expat.o] Error 1
make: Leaving directory `/home/nodeserver/xmltool/myapp/node_modules/node-expat/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/home/soft/node/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:204:12)
gyp ERR! System Linux 2.6.32-573.22.1.el6.x86_64
gyp ERR! command "/home/soft/node/bin/node" "/home/soft/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/nodeserver/xmltool/myapp/node_modules/node-expat
gyp ERR! node -v v6.2.1
gyp ERR! node-gyp -v v3.3.1
gyp ERR! not ok
npm ERR! Linux 2.6.32-573.22.1.el6.x86_64
npm ERR! argv "/home/soft/node/bin/node" "/home/soft/node/bin/npm" "install"
npm ERR! node v6.2.1
npm ERR! npm  v3.9.3
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the node-expat package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs node-expat
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls node-expat
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/nodeserver/xmltool/myapp/npm-debug.log

I'm using Debian where this node version is not yet available.
Does bumping the nan dependency solve the problem?

https://github.com/nodejs/node-gyp/issues/809


Document need for Visual C++ Redistributable on clients

It should be documented that the Visual C++ Redistributable is needed to be installed on client beyond the Microsoft.WindowsAppRuntime.Redist.
https://docs.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist?view=msvc-170

Architecture
Link
Notes

ARM64
https://aka.ms/vs/17/release/vc_redist.arm64.exe
Permalink for latest supported ARM64 version

X86
https://aka.ms/vs/17/release/vc_redist.x86.exe
Permalink for latest supported x86 version

X64
https://aka.ms/vs/17/release/vc_redist.x64.exe
Permalink for latest supported x64 version.

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

ID: 80c85908-b97b-91a8-af9a-231785991bf7
Version Independent ID: a4838116-3cb0-b97e-5065-934f7e4aadbe
Content: Deployment architecture for the Windows App SDK - Windows apps
Content Source: hub/apps/windows-app-sdk/deployment-architecture.md
Product: reunion
Technology: deployment
GitHub Login: @zaryaf
Microsoft Alias: zafaraj

Thanks, @devlead, I'm investigating!
-Steve

Thanks again, @devlead, I've published an update to the topic.
-Steve


Type Error

Traceback (most recent call last):
File "text_predictor.py", line 114, in
rnn()
File "text_predictor.py", line 76, in rnn
sample_text(sess, data_provider, iteration)
File "text_predictor.py", line 93, in sample_text
output.write(text + "\n")
TypeError: can't concat str to bytes
Any clue?

I am not 100% sure what’s causing the issue, but please check if your datasest is utf-8 encoded.
Another thing that came to my mind - it might be python 2/3 compatibility issue. I have tested it only with python 2.

Yes @gsurma it is the compatibility. And @fonzai it works after the changes! Many thanks!!!


Registration page clarification

**

**
Currently the registration page asks for:

Username
Email
Github username
Password
Confirm password

This leaves some ambiguity... specifically whether this is asking for your Github password, or for you to create a new password that will be used with this service.
My recommendation is to change this to:

Github username  >>>check whether this already exists in the registration system, deny registration if so.
Email (to receive notifications)
Create your GitGud username
Create your GitGud password
Confirm your GitGud password

Does this look better @mattwojo ?

So much better! These updates make it clear what is being asked for and what is being created.

*The only thing I might consider adding is whether the GitGudIssues username needs to be different than your GitHub username. (And use "GitHub" capitalization, especially since you're using GitGud capitalization).


Add SNAX icon

Hey, sorry, we don't accept PR contributions for the icons as we need to ensure all entries are exactly the same and also have the source Sketch file updated with all entries in case we need to export them again in the future. Instead, open an issue and we'll make it soon: https://github.com/atomiclabs/cryptocurrency-icons/issues/new


Document Launch with NHLBI Buttons

Is your feature request related to a problem? Please describe.
Need to document the Launch with BD Catalyst buttons:

Language Support
Individual page(s) (although now that the number is growing, I'm wondering if we shouldn't have a single launch with page, rather than one for each platform.

┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Fix Versions: Dockstore 1.8.X
┆Sprint: Backlog
┆Issue Number: DOCK-1235

NHLBI funds BD Catalyst. I think I have access; Beth does if not, and I can work with her.


VS Code can't open workflow in designer

Describe the Bug with repro steps

switch workflow designer to preview
Same issue when i open workflow in VSC

Workflow JSON
No response
Screenshots or Videos

Browser

Chrome
Edge

Additional context
Same problem when i open this workflow in VSC
Version: 1.77.3 (user setup)
Commit: 704ed70d4fd1c6bd6342c436f1ede30d1cff4710
Date: 2023-04-12T09:16:02.548Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: Yes

duplicate of #1934


Support Dark Mode

add dark mode to dashboard, nav, profile, login, register, reset, forget, email, layout and build a x-splade-script to switch dark mode and RTL

Curious to know if this was ever done?


Only add the token-minter sidecar to the ingressoperator when on AWS

Only aws needs the token minter sidecar, don't add it on other
platforms.

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #
Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/retest-required

/test e2e-aws

/lgtm


Can not download file

Can not download file
https://github.com/MrS0m30n3/youtube-dl-gui/releases/download/0.4/youtube-dl-gui-0.4-win-portable.zip

There is no release yet available for version 0.4 you can download 0.3.8
https://github.com/MrS0m30n3/youtube-dl-gui/releases/download/0.3.8/youtube-dl-gui-0.3.8-win-portable.zip


why a sampler network to test images not the generator

i saw the sampler() and generator() network have the same architecture, why define a new sampler but not use the generator? what is the difference of them.

maybe,it's to tell u that your model is training. generator network was optimized，but sampler not


I'm getting wrong barcodes

Is ist working? I'm getting wrong barcodes.

I'm no barcode expert but I believe the last digit is a checksum of sorts: it is a 33 followed by a 6.

I'm no barcode expert but I believe the last digit is a checksum of sorts: it is a 33 followed by a 6.

It looks so. Code39 mod 43 (Wikipedia)


logic change to the check in ART

Reason for this change is that MMD will not automatically fail enrollment if Device Compliance policy is set to All Users. The Admin can choose to assign their own Device compliance policy to MMD users, as long as they are aware that MMD has its own Device compliance policy that will also be applied to MMD users upon MMD enrollment. Thus this check now only has 'Advisory' setting and not 'Not Ready'

@jaimeo to review wording

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks

@jaimeo Please merge this PR. Thanks

@JohanFreelancer9 if you're going to be doing copy editing, please get familiar with our style guide. We do not use "please" except in certain circumstances (which do not apply in this text). Also, we are starting to move away from "target."


docs: concepts updates for v0.9

What's Changed in this PR

Describe the change in this PR
Checklist

[ ] Please confirm that all corresponding versions of the documents have been revised.
[ ] Please ensure that the content in summary.yml matches the current document structure when you changed the document structure.
[ ] This change requires follow-up update in localized docs.

Summary by CodeRabbit

Documentation

Updated architecture documentation with refined descriptions of Metasrv, Frontend, and Datanodes roles and interactions.
Enhanced data model explanation, including detailed examples of Metric and Log tables.
Clarified key concepts like database functionality, time-series tables, indexes, views, and flows in the user guide.
Revised overview of GreptimeDB features and data model details.

I'll add the zh docs right now

Please don't merge it, I'll modify it tomorrow if I feel better.

@nicecui Already done. Please take a look. If everything is good, we can copy them into v0.9 folder too.


Run celery with the beat option in docker.

If the DB has no migrations (which usually hasn't by default) the celery container throws errors.
celery_1 | ProgrammingError: (1146, "Table 'mozillians.djcelery_periodictask' doesn't exist")

Coverage remained the same at 92.547% when pulling a978748d0faa435b03394af2a9d6084a03645824 on akatsoulas:add-celery-beat-docker into 59f428a9bcfaa725bb5193980dcdb09015884d42 on mozilla:master.

Coverage remained the same at 92.496% when pulling 836ee35160d72004f1e106d277d92a63d60d68a7 on akatsoulas:add-celery-beat-docker into 544be67b88b8caece29a0a545adf7906294774dd on mozilla:master.

@johngian / @glogiotatidis r?

Coverage remained the same at 92.496% when pulling 836ee35160d72004f1e106d277d92a63d60d68a7 on akatsoulas:add-celery-beat-docker into 544be67b88b8caece29a0a545adf7906294774dd on mozilla:master.

Coverage remained the same at 92.496% when pulling 7ac9696c263779471c40a78ebeaf25a59185a268 on akatsoulas:add-celery-beat-docker into 49db2539fe190cc67b977ba4d46a4bbd5c9b3c91 on mozilla:master.

Coverage remained the same at 92.496% when pulling 7ac9696c263779471c40a78ebeaf25a59185a268 on akatsoulas:add-celery-beat-docker into 49db2539fe190cc67b977ba4d46a4bbd5c9b3c91 on mozilla:master.

Coverage remained the same at 92.496% when pulling 7ac9696c263779471c40a78ebeaf25a59185a268 on akatsoulas:add-celery-beat-docker into 49db2539fe190cc67b977ba4d46a4bbd5c9b3c91 on mozilla:master.

Coverage remained the same at 92.496% when pulling 7ac9696c263779471c40a78ebeaf25a59185a268 on akatsoulas:add-celery-beat-docker into 49db2539fe190cc67b977ba4d46a4bbd5c9b3c91 on mozilla:master.

r+ :ship:


Improved Interpolation

[x] Add HSV interpolation
[ ] Add RGB <-> HSV conversion for HASS lights / Pillow image outputs
[x] Add customization for interpolation procedure (weights, local influence)
[ ] Add app options for custom HSV color profiles
[ ] Add tests for new functionality
[ ] Update Readme

Old interpolation

New RGB interpolation (higher local influence)

New HSV interpolation

New built-in profiles:


Update request a call page functionality to match Old Dot

Details

cc @puneetlath
Fixed Issues

$ https://github.com/Expensify/App/issues/7067
Tests

Test requesting a call without an extension

Open the concierge chat
Click the call button
Make sure text appears showing the current wait time
Click the call me button
Ensure the request a call page closes and you see an alert saying "Call requested"

Test requesting with a phone extension
Same as above but enter a phone extension number before submitting
Test an invalid phone extension

Enter any non-numeric symbols in the phone extension
Make sure an error message appears when clicking away.
Make sure you can't submit with an error message.

[ ] Verify that no errors appear in the JS console

QA Steps

Same as the test steps

[ ] Verify that no errors appear in the JS console

Tested On

[ ] Web
[ ] Mobile Web
[ ] Desktop
[ ] iOS
[ ] Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

I have read the CLA Document and I hereby sign the CLA

@neil-marcellini good job with this. There's two main things I left comments on:

The wait time message doesn't seem to work properly when it's less than 300 minutes.
Adding default props and prop types for inboxCallUserWaitTime

And then one other thing. On old dot, we have a specific message if the user requests a call on the weekend. Can we add that here as well? https://github.com/Expensify/Web-Expensify/blob/main/site/app/modals/InboxCall.jsx#L34

Thank you for your review. I made an update with these changes. I also made sure that 'Calculating wait time...' shows up by not initializing the wait time with its the stored value.

I merged in main to fix the merge conflicts.

@neil-marcellini, Great job getting your first Expensify/App pull request over the finish line! :tada:
I know there's a lot of information in our contributing guidelines, so here are some points to take note of :memo::

Now that your first PR has been merged, you can be hired for another issue. Once you've completed a few issues, you may be eligible to work on more than one job at a time.
Once your PR is deployed to our staging servers, it will undergo quality assurance (QA) testing. If we find that it doesn't work as expected or causes a regression, you'll be responsible for fixing it. Typically, we would revert this PR and give you another chance to create a similar PR without causing a regression.
Once your PR is deployed to production, we start a 7-day timer :alarm_clock:. After it has been on production for 7 days without causing any regressions, then we pay out the Upwork job. :moneybag:

So it might take a while before you're paid for your work, but we typically post multiple new jobs every day, so there's plenty of opportunity. I hope you've had a positive experience contributing to this repo! :blush:

: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 @puneetlath in version: 1.1.29-6 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by @roryabraham in version: 1.1.30-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


An additional reason why breakpoints might not be hit, for the documentation

Breakpoints might also  be skipped if you're debugging the wrong type of code (e.g. script code vs. .NET 4 vs. .NET Core), as set when attaching to a process.

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

ID: 95bc6d7e-2b58-4755-4411-c5f369011a6c
Version Independent ID: d5710161-bc97-6d33-6c6b-77fc9cfe9c62
Content: Troubleshoot breakpoints in the debugger - Visual Studio (Windows)
Content Source: docs/debugger/troubleshooting-breakpoints.md
Product: visual-studio-windows
Technology: vs-ide-debug
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

@ekolis Thanks! That is a good addition to the doc. I'll make an update.

Update should be live by end of day today.

PR: https://github.com/MicrosoftDocs/visualstudio-docs-pr/pull/10693


Make event section descriptions consistent in Readme.md

This is a non-code PR, but the documentation was bugging me a little.

Some descriptions were after the code, some were before. Now they are all before the code sample they pertain to.
field has no description, fileBegin had field's description, file had fileBegin and file's descrition. Now they are all in the proper section.

Yea... I'm always confused too. Closing this, I'll update the docs soon.


Disable caching of verifier cmake project for now

Signed-off-by: Alan Jowett<EMAIL_ADDRESS>Description
Test to see if disabling caching fixes the issue with san cov settings.
Testing
CI/CD
Documentation
No.

Closing to stop CI/CD


chore: update server api to prevent overwrite the root dialog

Description
Add preserveRoot to inform create project to not overwrite the root dialog

Task Item
#minor

Screenshots

Coverage increased (+0.003%) to 55.068% when pulling bcdb64ec95bbab2e25361223ed507c3a5098f041 on lei9444:pvaroot into 83c08046a8f6969da1ee70fad6d22c5f9961c51e on microsoft:main.

What is the reason for this change? I don't see a linked issue.

@a-b-r-o-w-n this is something I worked with Dong and Leilei on for a PVA requirement

This probably warrants some commenting in the code because our code base isn't directly using this parameter.

I'm going to implement the client-side of this and will be sure to include some comments.

We should also consider typing the request body on our controller actions like in https://github.com/microsoft/BotFramework-Composer/blob/main/Composer/packages/server/src/controllers/extensions.ts#L55
We can then add comments on the TS properties.


Run py stub

Read error parameters from file

Codecov Report

Merging #19 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #19   +/-   ##
=======================================
  Coverage   87.13%   87.13%
=======================================
  Files           9        9
  Lines         241      241
=======================================
  Hits          210      210
  Misses         31       31

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 64ac42a...d949d11. Read the comment docs.


Feedback on clickability in UI

We have many small targets for clicking and inconsistent UI on what can be clicked. @pmbrull, @vivekratnavel, and @harshach, please continue to provide feedback here:

[x] In Glossaries there are two types of click allowed. One for clicking the term to see the details and another to expand the children under a term by clicking the arrow. Let's combine them to make the click target bigger. When clicking a term or an arrow, let's expand the children and show the term details both.

[x] Instead of just making the checkbox a click target, let's also allow clicking the entire line:

[x] Some clickable text changes colors to purple with an underline when hovering over and others don't do this. Some examples are - Sorting with Last Updated, Owner field in the data asset details page. @parthp2107, can you please do a thorough review of this?

[x] No hover over response for What's New, Tour, Help, and Profile button like Explore and settings

[x] Inconsistent hover-over for follow and version count in data asset details page.

https://user-images.githubusercontent.com/83201188/157595786-6fefaf45-17f4-4b58-ac9e-fbafa5880f99.mov

[x] The count presentation should be consistent for activity feed.

[ ] adding glossary terms as a tag is really hard to do .

https://user-images.githubusercontent.com/38649/157581268-dc2d7056-926d-4b28-9e7c-d42e76958165.mov

The hover-over tooltip gives the same text as a checkbox innerHTML
https://user-images.githubusercontent.com/83201188/157592545-812098c7-74bd-4910-8c35-0c376c7e3a17.mov

The icon shown for a user changes depending on if we show the username or the name

Tag details UI changes after adding a new tag category

Misaligned icon:

The icon is not aligned with the left margin in service pages.

The hover-over tooltip gives the same text as a checkbox innerHTML
Screen.Recording.2022-03-10.at.10.24.41.AM.mov

@parthp2107 That is expected behaviour.

Closing this and moving out alignment related issues to #3115


Redirect on props update (#5003)

Fixes https://github.com/ReactTraining/react-router/issues/5003
Is it ok I've added is-equal dependency? It's used by expect already.
I needed it because checking if we are redirecting to the same route is not so trivial.
to can be a String or an Object, and the Object variant can have pathname, search and state, each of which could be a valid new route to redirect to.
e.g. I might want to redirect to my own route with a different search string or state data.
Other PR Questions:

I'd really like the warning to be better, telling the user where that last  originated or something that will help him realize where the issue is, any ideas?
How do I test if the usage of warning?
In this case if we try to redirect to the same route we call warning to notify the user.

pathname and search are simple strings, so that's easy to check. I don't even know if state is worth checking, since it's a hidden property anyways.
There is a warning test at the bottom of #5151

@timdorr Update:

Ditched is-equal and wrote a basic comparison without state (I've noticed to is not a required prop, does that make sense? What's the use case for a Redirect without to?)
The tests in #5151 are for the console, which is a global object, if we want to test warning, which is an imported module inside the Redirect module, we'll have to use proxyquire or alike to stub it.
Let me know if you'd like me to do that, for now I've added a test that works around that.

Two ideas:

Use value-equal, which is fairly lightweight.
Use history/LocationUtils -> locationsAreEqual. It requires that it's an object, but you can also use createLocation to coerce it into an object.

I don't know why to isn't required. We're not hardcore PropType-ers around here.
It's fine to test console. You don't need to stub the library, just the effects of that library. If we want to switch to a "better" library at some point, we can do so without breaking tests.

@timdorr value-equal worked, so did locationsAreEqual, so I picked it to not add a dependency. Spying on console.error` worked as well.
The warning itself has a stack trace, but you can't find the component that included the bad <Redirect>. This would be a different ticket though.
I think I'm done.

@timdorr Merge it while it's hot (and passing build) ;-)

LGTM. Needs a second, though. (Only @ryanflorence or @mjackson can do a solo merge)

I'm tempted to just put an invariant inside <Redirect>'s componentDidUpdate. It's not supposed to persist across multiple renders!

It's not that it's necessarily persisting the same exact <Redirect> usage in a user's code. It's that React is re-using an instance, as it does when the component tree shape does not change. So this is perfectly reasonable code to write:
render() {
  return (
    !loggedIn ? <Redirect to="/login"/> :
    !admin ? <Redirect to="/denied"/> :
    <Admin/>
  )
}

You've got two <Redirect>s from your perspective, but if you move between them, React re-uses the instance and it does nothing. No one is trying to re-use a <Redirect>, React is. It's a common problem to run into.

Fixed conflict, but the build was canceled, no apparent reason.
Can we rebuild it?

It auto-cancels if another build comes in on top of it. But you should rebase against master because @mjackson just fixed all the testing and building infra.

@timdorr Had some issues, but managed to do it eventually.
In Jest, we don't need to restore spies anymore?
Also, do I need to squash the commits or something? Got a ref for that?

@alexilyaev Squashing yourself isn't completely necessary since GitHub allows the maintainers to do it when merging, but I generally like to do so anyways (especially if something I do in one commit gets reverted in another). For reference, this article goes over the details very nicely: https://github.com/edx/edx-platform/wiki/How-to-Rebase-a-Pull-Request.

Guys, please merge this.

Needs another 👍  from someone.

@pshrmn Done with requested changes.
Now using createLocation and added a test for the query param use case.

In it goes. It'll be in the next minor release. Lots of goodies lined up, so hopefully that will be soon.


Game crash on interaction between Exchanging gadget and Occultism mod storage

Building Gadgets Version 1.0.6
Playing on All The Mods 9 Version 0.2.28
Using the Exchanging Gadget on Occultism's Storage Actuator will crash the game. From then on, loading into the world will continue to crash the game.
I've been playing on a server that offers a secondary world (Hosted separately) but with a shared inventory. Logging into this secondary server with the exchanging gadget still in the inventory continues to crash the game when loaded in.
Steps to reproduce the behavior:
-Use an exchanging gadget on Occultism's Storage Actuator.
(Note: Unsure if this was a right-click or a shift + right-click)
Expected behavior:
-Either have no interaction with the storage actuator,
-Or pick the storage actuator up.
Log Files: https://file.io/EN0QmSLBk5Zc
Rubidium Note:
ATM9 is using Embeddium rather than Rubidium, however the crash still persisted when Embeddium was removed.

Sorry I can't reproduce this, and the log file has expired. Please let me know if its still happening


refactor(cp): delete key for moreOp in component list

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Specified Reivewers:
/assign @your-reviewer

/approve


M2 Ultra and M3 Max benchmarks updated

@TristanBilot benchmarks updated, PR ready!

amazing! thanks @ivanfioravanti 🤗


Support multiple keys with safe gen

If there's a backwards-compatible way to support safe gen [len] path key1 key2 ... keyN, it would be great, so that we can make use of that similarly to safe set path key1 key2 ... keyN.

We can always just assume that if the first path is numeric (/^[0-9]$/), it's a length, otherwise it's the start of a set of paths to gen for?

Once #73 is merged, we can relegate length to an option, and if the path looks like an integer, fall back to the existing logic.  Then we will be able to do this:
safe gen -l 64 secret/path/to/wherever username password firstname lastname ssn phone email

I believe the fix for this was included in #75 . Can we verify and close this ticket?

Verified.
→  safe gen secret/stuff:{username,password,pin,token}
→  safe tree --keys secret
.
└── secret
    └── stuff
        ├── :password
        ├── :pin
        ├── :token
        └── :username

→  safe read secret/stuff
--- # secret/stuff
password: QjfrGk7tK6J6LtOA4hp7W9FVPs7iZpj3r5qyquupqE6SaV81fbQeZPguC2A2S8mG
pin:      LyJVKrGUMh4uZ8pWLv6vMl030sAmJtGgSdhcXrbyhRYHiDIYCFH4zj11UAHi0j6x
token:    Ynm4wwGmY7a44lj3GY06tR8edgO0jWc6rrLCt1dtzLc1gyv8SdfTLPtYpxyqPmrt
username: nHbWej7S44OD6NfaZ3qgRcgIHQ4gBFLlos3bEFWZ6XMLMhEqBH5kGcPabAGUsG0b


Plugin option to resend the email ?

Sometime for different reasons, the email can't be sent.
If you had fix the mail problem, how can you re-send the very mail ?

This issue has been closed automatically for inactivity after more than 1 year. Unfortunately, this project doesn't have enough resources to manage all these requests. Read the FAQ.


Panic during execution of Brainfuck code

Description:
While executing the provided Brainfuck code snippet, a panic occurs instead of generating the expected output. The panic indicates an unexpected error or invalid state during the execution.
Code:
code = `+[-->-[>>+>-----<<]<--<---]>-.>>>+.>>..+++[.>]<<<<.+++.------.<<-.>>>>+.`
output := Run(code, nil)
if string(output) != "Hello World!\n" {
 	t.FailNow()
}

Expected Output: "Hello World!\n"
Actual Behavior: Panic occurs during code execution
To Reproduce:

Use the provided code snippet in a test case.
Execute the test case.
Observe the panic message or error stack trace.

Environment:

Operating System: Mac OS
Go version: 1.20

The BF code shouldn't in fact execute successfully (you can try via the online interpreter here) as it is trying to move the pointer to negative values.

The issue has been closed based on the reason provided by Kalam132.


Refactor connectivity

Made a small refactor on connectivity.go
Created a new variadict argument in CurlFail
Added Netcat into wrappers.

test-me-please

test-me-please


DNS-U IP Address has changed!

The IP address for DNS-U used to be <IP_ADDRESS>. It has changed to <IP_ADDRESS>
Source: https://gbatemp.net/threads/dns-u-new-update-blocking-dns-server.436346/

Thanks, it's been updated.


Rationalize list of additional tutorials

From discussion in https://github.com/aspnet/EntityFramework.Docs/pull/1475, figure out what to do with list of additional ASP.NET Core tutorials at the bottom of some of ours:

Should it be the same at the bottom of all ASP.NET Core-related tutorials?
Should it be a single link?
Should it be moved to the ToC as external links?

Duplicate of #481


SPIKE: Create some files for gitops run bootstrapping

The bootstrapping process for gitops run hurts.  Let's create the files that we think will be outputted by the command in the following scenarios.  We will then use those files to drive the stories for making the command work as expected.
The files should contain

Flux bootstrap files
Gitops dashboard
Normal kustomization.yaml (not Flux Kustomization) that follows best practices.
Files or configuration to point to the path in gitops run

Acceptance Criteria
Scenario 1 - Root directory and current working directory are the same.
Root directory: /Users/myself/my-repo
Current working directory: /Users/myself/my-repo
Scenario 2 - Root directory and current working directory are different.
Root directory: /Users/myself/my-repo
Current working directory: /Users/myself/my-repo/manifests
Scenario 3 - Root directory and current working directory are different and the working directory is an application path.
Root directory: /Users/myself/my-repo
Current working directory: /Users/myself/my-repo/apps/podinfo
I run gitops run .
I run gitops run ./workload <- This is assumed not to exist
I run gitops run ./deploy/overlays/dev

I haven't created the exact full grid, but there's sufficiently many examples to get going.
General notes

The exact version of flux used isn't important
The flux files have to be generated using flux bootstrap, which limits what we can do with them
The exact version of gitops dashboard installed isn't important
I've not created the implied kustomization.yaml files (e.g. clusters/my-cluster doesn't have a kustomization.yaml). I decided not to, since the flux example repos do not, and I remember past bugs when files are generated but kustomization.yaml isn't updated. I could be convinced we should.
I've created a flux kustomization, not a k8s kustomization, to include the workload. This is a bit unusual, but demos our dashboard better since the workload is now its own thing you can look at. I've reused the flux-system source for this kustomization.

gitops run .
Scenario 1: https://github.com/ozamosi/scenario-1-gitops-run-dot
Scenario 2: https://github.com/ozamosi/scenario-2-gitops-run-dot
Note:

We do not create a workload level kustomization, because the path already exists.
Because the user is explicitly saying that the entrypoint for the workload is at the current top level, this will confuse flux and the resources defined in clusters/my-cluster/flux-system will flap between being owned by flux-system and workload. You don't want to do this.
I assume we create a root special case for the resource name.

gitops run ./workload
This is the "normal" getting started scenario.
Scenario 1: https://github.com/ozamosi/scenario-1-gitops-run-workload
Scenario 2, but assumed to be gitops run ../workload instead of ./workload (otherwise it'd just be the same as scenario 1 but in a directory): https://github.com/ozamosi/scenario-2-gitops-run-dotdot-workload
We create the directory workload and we create an empty (k8s) kustomization.yaml for the user to get started with.
gitops run ./deploy/overlays/dev
Someone has set up a bit of automations already, but the user still needs to bootstrap this cluster.
Scenario 1, using podinfo as the existing repo: https://github.com/ozamosi/scenario-1-gitops-run-deploy-overlays-dev
This is really the same as ./workload except we don't create any new files in the workload directory because the destination already exists.
Scenario 3
Using podinfo as a base, and for simplicity's sake I used deploy/webapp instead of apps/podinfo so it exists.
gitops run .: https://github.com/ozamosi/scenario-3-gitops-run-dot
gitops run deploy/overlays/dev: https://github.com/ozamosi/scenario-3-gitops-run-deploy-overlays-dev
This is probably not what I wanted - now the cluster definition lives under the webapp deploy instructions, and in the second scenario, the user typed a path that they meant to make relative to the root of the repository and we interpreted it as being relative to the root of where they currently are. Disappointing.
However, the user would have had to ignore e.g. tab completion to think that this would work.


0% JSON to CSV

When using twarc2 csv tweets.jsonl tweets.csv # convert to CSV
It loads the JSONL and runs the script at 0%:
0%|                                                                                | 0.00/2.72M [00:00<?, ?B/s]

How big is the tweets.jsonl file and what command generated this file?

The JSONL is 2783KBS and the command was:
twarc2 csv test.jsonl tweets.csv # convert to CSV.

oh, sorry, i meant - what was the command that wrote test.jsonl - was it twarc2 search? Can compress and attach this test.jsonl file here?

No worries! I hydrated the tweets using: twarc hydrate test.txt > test.jsonl. I'm hoping to use the Twarc cmd to hydrate a large JSONL of roughly 1M Tweets. The test files is a smaller file of 500 Tweets.
I think publicly publishing the JSON break Twitter's T&C for privacy, I can email it to you if that works?

Sure - igor.brigadir at gmail.com will work

I never found the tweets in case you sent them, but I released a new version, so try again after:
pip3 install --upgrade twarc-csv

Please reopen if it's still an issue.


[Snyk] Fix for 8 vulnerabilities

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

requirements.txt

⚠ Warning
graphql-core 3.2.3 requires typing-extensions, which is not installed.
dj-database-url 2.0.0 requires typing-extensions, which is not installed.
asgiref 3.7.2 requires typing-extensions, which is not installed.
arrow 1.2.3 requires typing-extensions, which is not installed.
ariadne 0.20.1 requires typing-extensions, which is not installed.
ariadne 0.20.1 requires starlette, which is not installed.

Vulnerabilities that will be fixed
By pinning:

Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity

691/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.4
Improper Certificate Validation SNYK-PYTHON-CRYPTOGRAPHY-5777683
cryptography:  41.0.1 -> 41.0.5
No
Proof of Concept

399/1000  Why? Has a fix available, CVSS 3.7
Insufficient Verification of Data Authenticity SNYK-PYTHON-CRYPTOGRAPHY-5813745
cryptography:  41.0.1 -> 41.0.5
No
No Known Exploit

479/1000  Why? Has a fix available, CVSS 5.3
Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-5813746
cryptography:  41.0.1 -> 41.0.5
No
No Known Exploit

399/1000  Why? Has a fix available, CVSS 3.7
Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-5813750
cryptography:  41.0.1 -> 41.0.5
No
No Known Exploit

539/1000  Why? Has a fix available, CVSS 6.5
Denial of Service (DoS) SNYK-PYTHON-CRYPTOGRAPHY-5914629
cryptography:  41.0.1 -> 41.0.5
No
No Known Exploit

551/1000  Why? Recently disclosed, Has a fix available, CVSS 5.3
Missing Cryptographic Step SNYK-PYTHON-CRYPTOGRAPHY-6036192
cryptography:  41.0.1 -> 41.0.5
No
No Known Exploit

/1000  Why?
Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-SETUPTOOLS-3180412
setuptools:  39.0.1 -> 65.5.1
No
No Known Exploit

424/1000  Why? Has a fix available, CVSS 4.2
Information Exposure Through Sent Data SNYK-PYTHON-URLLIB3-6002459
urllib3:  1.26.17 -> 1.26.18
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Denial of Service (DoS)

Codecov Report

Merging #419 (5b49a54) into develop (3b07e98) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #419   +/-   ##
========================================
  Coverage    81.67%   81.67%
========================================
  Files          150      150
  Lines         9164     9164
========================================
  Hits          7485     7485
  Misses        1679     1679

:mega: Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today!


Add error messages to assert conditions

Trying to resolve #1294 :)

It looks like auto-merge couldn't merge this because of codecov/patch, right?


Destructible delayed

🚀 Description
The SELFDESTRUCT opcode can have negative consequences when executed inappropriately. This was the case with the library the parity multisignature wallet was using. By introducing a delay in the destruction of a contract, you can make it safer that any party involved is aware that the contract will be self-destructed. This should allow anyone involved to securely adjust before the SELFDESTRUCT opcode is called.

[x] 📘 I've reviewed the OpenZeppelin Contributor Guidelines
[x] ✅ I've added tests where applicable to test my new functionality.
[x] 📖 I've made sure that my contracts are well-documented.
[x] 🎨 I've run the JS/Solidity linters and fixed any issues (npm run lint:all:fix).

Yikes, I merged master instead of rebase.

Hey @PhABC! Do you intend to keep working on this? If not, maybe we can have someone else finish this PR, since its so close to completion. Thanks!

Closing as stale. I think delaying destruction makes sense, but I'm unsure selfdestruct is something one should even want in the first place (and hence, if we should promote it from OZ).


Set From address to use in SMTP alert

Hi.
I am trying to use smtp fro frigate notifications. The configuration looks valid but any notification is dropped because I get this error message:  WRN Unable to send alert error="send failed: getting sender address: no FROM address set" event_id=xxx. How do you set the Frrom address?
Regards.

Hi @szafar, please provide the frigate-notify configuration you're using (do not forget to obscure sensitive things like credentials, etc).
The FROM field in a message will be populated from user configuration property of SMTP notifier: https://github.com/0x2142/frigate-notify/blob/main/notifier/smtp.go#L32
Potentially, an incorrect configuration can occur if your SMTP relay does not require authentication and you have not set both user and password properties in the configuration. In this case, the SMTP notifier will set FROM field in the message as empty string.

Hi,
I am still unable to configure as now I am getting this error when using
self signed certs:
WRN Unable to send alert error="dial failed: tls: failed to verify
certificate: x509: cannot validate certificate for 192.168.X.X because it
doesn't contain any IP SANs"
I normally use letsencrypt certs but that causes another error:
WRN Unable to send alert error="dial failed: 454 TLS currently
unavailable".
In this case the corresponding error in exim4 is:
TLS error on connection from notify ( ) [<IP_ADDRESS>] (cert/key
setup: cert=yes key=yes): Error while reading file.
Trying to figure out what it is causing this.
Regards,
On Mon, Aug 19, 2024 at 11:35 AM Matt Schmitz @.***>
wrote:

Hm, perhaps I should add a dedicated FROM field for cases like this.
Honestly I figured I was the only one who probably used SMTP 😅
—
Reply to this email directly, view it on GitHub
https://github.com/0x2142/frigate-notify/issues/123#issuecomment-2296869045,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2K2XY57YEBPM36PKSG2Z3ZSIGFLAVCNFSM6AAAAABMVXO3K2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJWHA3DSMBUGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi,
My SMTP config looks like this:
smtp:
enabled: true
server: 192.168.X.Y
port: 25
tls: True
user: notifier
password: XXXX
recipient: @.***
Regards,
On Sun, Aug 18, 2024 at 7:48 AM freefd @.***> wrote:

Hi @szafar https://github.com/szafar, please provide the frigate-notify
configuration you're using (do not forget to obscure sensitive things like
credentials, etc).
The FROM field in a message will be populated from user configuration
property of SMTP notifier
https://frigate-notify.0x2142.com/latest/config/file/#smtp:
https://github.com/0x2142/frigate-notify/blob/main/notifier/smtp.go#L32
Potentially, an incorrect configuration can occur if your SMTP relay does
not require authentication and you have not set both user and password
properties in the configuration. In this case, the SMTP notifier will set
FROM field in the message as empty string
https://github.com/0x2142/frigate-notify/blob/main/config/config.go.
—
Reply to this email directly, view it on GitHub
https://github.com/0x2142/frigate-notify/issues/123#issuecomment-2295232877,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2K2X4NCXBALE4XWJKLSZDZSCC2DAVCNFSM6AAAAABMVXO3K2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJVGIZTEOBXG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

BTW followed this to configure my exim4 ...
https://ubuntu.com/server/docs/install-and-configure-exim4
On Mon, Aug 19, 2024 at 11:46 AM Sohail Zafar @.***> wrote:

Hi,
I am still unable to configure as now I am getting this error when
using self signed certs:
WRN Unable to send alert error="dial failed: tls: failed to
verify certificate: x509: cannot validate certificate for 192.168.X.X
because it doesn't contain any IP SANs"
I normally use letsencrypt certs but that causes another error:
WRN Unable to send alert error="dial failed: 454 TLS currently
unavailable".
In this case the corresponding error in exim4 is:
TLS error on connection from notify ( ) [<IP_ADDRESS>] (cert/key
setup: cert=yes key=yes): Error while reading file.
Trying to figure out what it is causing this.
Regards,
On Mon, Aug 19, 2024 at 11:35 AM Matt Schmitz @.***>
wrote:

Hm, perhaps I should add a dedicated FROM field for cases like this.
Honestly I figured I was the only one who probably used SMTP 😅
—
Reply to this email directly, view it on GitHub
https://github.com/0x2142/frigate-notify/issues/123#issuecomment-2296869045,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2K2XY57YEBPM36PKSG2Z3ZSIGFLAVCNFSM6AAAAABMVXO3K2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJWHA3DSMBUGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

WRN Unable to send alert error="dial failed: tls: failed to verify certificate: x509: cannot validate certificate for 192.168.X.X because it doesn't contain any IP SANs"

It seems there should be ignoressl option like other notifier modules have.

Agreed. I can bundle that into the next release

This will be good, I too have a SMTP with no user, although I just created one as a workaround ;)

Oh, "dial failed: server does not support SMTP AUTH" not such a cleaver workaround!
Any idea when this might be released? Or at least merged into dev? Might be nice if a docker image was build for PRs to allow testing before merge?

Hi @bobemoe - I just merged the changes into dev so you can try pulling that down to test if you like. Please let me know if you see any issues!

@0x2142 Thanks. This is tested and working as expected :)

New options added to v0.3.5, see docs.


use query if it is present even with operation id

Stack:

#12
#10
#9
#7 ⬅

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

✓ Commit merged in pull request #12


Creating a Custom Authorizer

Issue on page:        https://github.com/opentelekomcloud-docs/api-gateway/blob/main/umn/source/api_opening/custom_authorizers/creating_a_custom_authorizer.rst
Please remove hint that FG is not yet launched. Thanks

This issue will be fixed with the next release of the document.


Aria2安装后启动报错

对不起，请求的目标未找到。
No page is registered at '/admin/services'. If this url belongs to an extension, make sure it is properly installed. If the extension was recently installed, try removing the /tmp/luci-indexcache file.
无法调度: /cgi-bin/luci/admin/services/aria2

应该是 Aria2 插件的兼容性问题，可能入口地址根本不是 OpenWRT 官方提供的入口地址。

对不起，请求的目标未找到。
No page is registered at '/admin/services'. If this url belongs to an extension, make sure it is properly installed. If the extension was recently installed, try removing the /tmp/luci-indexcache file.
无法调度: /cgi-bin/luci/admin/services/aria2

可能是因为没安装 luci-compat?


Fix qhull-static output

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Solve #20

Activate static lib build
Fix test to check if static libs exist
Export cmake in qhull-static to have all symbol inside (shared and static)

I have tested this package locally with hpp-fcl and it's working.


chore(main): release 0.12.2

:robot: I have created a release beep boop
0.12.2 (2024-12-05)
Bug Fixes

input: define an explicit height for small sized input (b25bedb)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.12.2
:sunflower:


Build error for Spring 2.4.1 with spring-cloud-starter-vault-config 2.2.4.RELEASE

I have upgraded spring boot dependencies from 2.3.5.RELEASE to 2.4.1. I have spring-cloud-starter-vault-config version at 2.2.4.RELEASE. I tried to upgrade it to 2.2.6.RELEASE. In both the cases I am getting below error.
java.lang.IllegalStateException: Failed to load ApplicationContext
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'configurationPropertiesBeans' defined in class path resource [org/springframework/cloud/autoconfigure/ConfigurationPropertiesRebinderAutoConfiguration.class]: Post-processing of merged bean definition failed; nested exception is java.lang.IllegalStateException: Failed to introspect Class [org.springframework.cloud.context.properties.ConfigurationPropertiesBeans] from ClassLoader [jdk.internal.loader.ClassLoaders$AppClassLoader@2aae9190]
Caused by: java.lang.IllegalStateException: Failed to introspect Class [org.springframework.cloud.context.properties.ConfigurationPropertiesBeans] from ClassLoader [jdk.internal.loader.ClassLoaders$AppClassLoader@2aae9190]
Caused by: java.lang.NoClassDefFoundError: org/springframework/boot/context/properties/ConfigurationBeanFactoryMetadata
Caused by: java.lang.ClassNotFoundException: org.springframework.boot.context.properties.ConfigurationBeanFactoryMetadata
Is there any compatible version of spring-cloud-starter-vault-config?
I tried spring-cloud-starter-vault-config version 3.0.0-RC1. It throws error as below. In my project I have bootstrap.yml with property spring.cloud.vault.token which is not empty.
Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.vault.authentication.VaultTokenSupplier]: Factory method 'vaultTokenSupplier' threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'clientAuthentication' defined in class path resource [org/springframework/cloud/vault/config/VaultAutoConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.vault.authentication.ClientAuthentication]: Factory method 'clientAuthentication' threw exception; nested exception is java.lang.IllegalArgumentException: Token (spring.cloud.vault.token) must not be empty

Version 2.x of Spring Cloud vault is not compatible with boot 2.4.x so only the later error is relevant

https://github.com/spring-cloud/spring-cloud-release/wiki/Spring-Cloud-2020.0-Release-Notes#breaking-changes

Version 2.x of Spring Cloud vault is not compatible with boot 2.4.x so only the later error is relevant

sorry, which error is relevant? I tried 2.4.1 with 3.0.0-RC1 spring-cloud-starter-vault-config. To fix bootstrap.yml issue. I added dependency. Is this approach right? or I should not use 2.4.1 springboot?

org.springframework.cloud
spring-cloud-starter-bootstrap

| which error is relevant?
The error with 3.0.0-RC1
There are two approaches, add the bootstrap start like you said or use the new spring.config.import

ok great. I have added bootstrap dependency. It is working. Thank you


rework index drop logic in parse:* scripts

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (35ebc9c) 95.06% compared to head (1c9792c) 95.06%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master     #192   +/-   ##
=======================================
  Coverage   95.06%   95.06%
=======================================
  Files          21       21
  Lines         162      162
  Branches       14       14
=======================================
  Hits          154      154
  Misses          8        8

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


remoteAddress MDC does not respect cas.audit.alternateClientAddrHeaderName property

The MDC variable for remoteAddress does not respect the cas.audit.alternateClientAddrHeaderName Audits property.
How to Replicate
The following properties in cas.properties are relevant to this issue:
cas.audit.alternateClientAddrHeaderName=X-FORWARDED-FOR

The above property works as expected to override the CLIENT IP ADDRESS with the OOB Audit logging. This works because there is a conditional check to see if the above configuration property is set.
=============================================================
WHO: <PRINCIPAL>
WHAT: TGT-**********************************************tdEX5OSvGN-cas6
ACTION: TICKET_GRANTING_TICKET_CREATED
APPLICATION: CAS
WHEN: Sat Oct 28 08:44:24 EDT 2017
CLIENT IP ADDRESS: <X-FORWARDED-FOR CLIENT IP>
SERVER IP ADDRESS: <SERVER IP>
=============================================================

However, when using MDC variables to create a custom logging format, the remoteAddress variable does not respect the alternative header specified in cas.audit.alternateClientAddrHeaderName. Instead, it uses the IP Address making the request which is not desired when this property is set to an alternative header value.
This can be replicated by adding the following simple example to log4j2.xml:
<Appenders>
       <Console name="mdc_dump" target="SYSTEM_OUT">
            <PatternLayout pattern="MDC remoteAddress: %X{remoteAddress}"/>
        </Console>

        <CasAppender name="mdc_dump_console">
            <AppenderRef ref="mdc_dump" />
        </CasAppender>
</Appenders>

<Loggers>
        <AsyncRoot level="warn">
            <AppenderRef ref="mdc_dump_console"/>
        </AsyncRoot>
</Loggers>

The above configuration outputs the following to console:
MDC remoteAddress: <REQUEST IP, NOT X-FORWARDED-FOR IP>

Expected Behavior
The remoteAddress MDC variable should return the header value mapped in the cas.audit.alternateClientAddrHeaderName property.
Version Information
CAS Version: 5.1.5
CAS Commit Id: dd67c8066700545fa6fe92fb681277fabded6115
CAS Build Date/Time: 2017-10-28T12:42:56Z
Spring Boot Version: 1.5.3.RELEASE
------------------------------------------------------------
System Date/Time: 2017-10-28T08:43:00.895
System Temp Directory: /tmp
------------------------------------------------------------
Java Home: /usr/lib/jvm/java-1.8.0-openjdk-<IP_ADDRESS>-2.b11.el7_3.x86_64/jre
Java Vendor: Oracle Corporation
Java Version: 1.8.0_131
JCE Installed: yes
------------------------------------------------------------
OS Architecture: amd64
OS Name: Linux
OS Version: 3.10.0-514.16.1.el7.x86_64
------------------------------------------------------------
Apache Tomcat Version: Apache Tomcat/8.5.20
------------------------------------------------------------

The MDC's remoteAddress would never consider a setting that deals with audit logs. However, if you wish you have MDC process alternative headers for remoteAddress, I think that's a sound idea. Please file a pull request to address the change at your earliest convenience.


kakoune: 2017-04-12 -> 2018-02-15

Motivation for this change
It has been a while since the last version bump. I also removed the now unnecessary dependency on boost.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build kakoune

Success on x86_64-darwin (full log)
Partial log (click to expand)
[ -e /nix/store/gmqzwdni9c12v075x2wsd2fi0acv8vwv-kakoune-unstable-2018-02-15/share/kak/autoload ] || ln -s rc /nix/store/gmqzwdni9c12v075x2wsd2fi0acv8vwv-kakoune-unstable-2018-02-15/share/kak/autoload
install -m 0644 ../colors/* /nix/store/gmqzwdni9c12v075x2wsd2fi0acv8vwv-kakoune-unstable-2018-02-15/share/kak/colors
install -m 0644 ../README.asciidoc /nix/store/gmqzwdni9c12v075x2wsd2fi0acv8vwv-kakoune-unstable-2018-02-15/share/doc/kak
install -m 0644 ../doc/kak.1.gz /nix/store/gmqzwdni9c12v075x2wsd2fi0acv8vwv-kakoune-unstable-2018-02-15/share/man/man1
post-installation fixup
gzipping man pages under /nix/store/gmqzwdni9c12v075x2wsd2fi0acv8vwv-kakoune-unstable-2018-02-15/share/man/
strip is /nix/store/v8ifq0hapblpr2z0hx4wvwg02w4aczqy-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/gmqzwdni9c12v075x2wsd2fi0acv8vwv-kakoune-unstable-2018-02-15/bin
patching script interpreter paths in /nix/store/gmqzwdni9c12v075x2wsd2fi0acv8vwv-kakoune-unstable-2018-02-15
/nix/store/gmqzwdni9c12v075x2wsd2fi0acv8vwv-kakoune-unstable-2018-02-15

Success on x86_64-linux (full log)
Partial log (click to expand)
install -m 0644 ../doc/kak.1.gz /nix/store/kyrbdzwx6cbf0azlg7cx30i3bslawsx4-kakoune-unstable-2018-02-15/share/man/man1
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/kyrbdzwx6cbf0azlg7cx30i3bslawsx4-kakoune-unstable-2018-02-15
shrinking /nix/store/kyrbdzwx6cbf0azlg7cx30i3bslawsx4-kakoune-unstable-2018-02-15/bin/kak
gzipping man pages under /nix/store/kyrbdzwx6cbf0azlg7cx30i3bslawsx4-kakoune-unstable-2018-02-15/share/man/
strip is /nix/store/adidfx4pa7vmvby0gjqqmiwg2x49yr27-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/kyrbdzwx6cbf0azlg7cx30i3bslawsx4-kakoune-unstable-2018-02-15/bin
patching script interpreter paths in /nix/store/kyrbdzwx6cbf0azlg7cx30i3bslawsx4-kakoune-unstable-2018-02-15
checking for references to /tmp/nix-build-kakoune-unstable-2018-02-15.drv-0 in /nix/store/kyrbdzwx6cbf0azlg7cx30i3bslawsx4-kakoune-unstable-2018-02-15...
/nix/store/kyrbdzwx6cbf0azlg7cx30i3bslawsx4-kakoune-unstable-2018-02-15

Success on aarch64-linux (full log)
Partial log (click to expand)
install -m 0644 ../doc/kak.1.gz /nix/store/d7y1r8f6pk71z0yf4np09h5h3kmki3r7-kakoune-unstable-2018-02-15/share/man/man1
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/d7y1r8f6pk71z0yf4np09h5h3kmki3r7-kakoune-unstable-2018-02-15
shrinking /nix/store/d7y1r8f6pk71z0yf4np09h5h3kmki3r7-kakoune-unstable-2018-02-15/bin/kak
gzipping man pages under /nix/store/d7y1r8f6pk71z0yf4np09h5h3kmki3r7-kakoune-unstable-2018-02-15/share/man/
strip is /nix/store/skd6ix5ipkyhxzq7naylj4digawakl4j-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/d7y1r8f6pk71z0yf4np09h5h3kmki3r7-kakoune-unstable-2018-02-15/bin
patching script interpreter paths in /nix/store/d7y1r8f6pk71z0yf4np09h5h3kmki3r7-kakoune-unstable-2018-02-15
checking for references to /build in /nix/store/d7y1r8f6pk71z0yf4np09h5h3kmki3r7-kakoune-unstable-2018-02-15...
/nix/store/d7y1r8f6pk71z0yf4np09h5h3kmki3r7-kakoune-unstable-2018-02-15


fix: 1053 - remove bars for telemetry

Fix:

#1053

Sample of the output:
-----------
Follow your logs with:
   tail -f  /app/logs/log_1673272819.log

-----------
- Sending installation telemetry
Download dependencies         ... 33.3% [#########...................] [1 in 700.264ms]
Download dependencies         ... done! [3 in 8.862s]
Create SSH keys               ... done! [1 in 8.874s]
Clone and Detokenize (GitOps) ... done! [1 in 10.085s]
- initialization step is done!
Process Parameters            ... done! [1 in 10.34s]
- Creating github resources with terraform
- Created gitops Repo in github.com/ABC
- pushing local detokenized gitops content to new remote github.com/ABC
Setup gitops on github        ... done! [3 in 1m5.548s]
- create initial argocd repository
- helm repo add argo https://argoproj.github.io/argo-helm and helm repo update
- helm install argo and wait
- ArgoCD is running, continuing
- Setting argocd username and password credentials
- argocd username and password credentials set successfully
- Getting an argocd auth token
- argocd admin auth token set
- applying the registry application to argocd
- waiting for Vault to be ready...
- configuring vault with terraform
- vault terraform executed successfully
- Vault secret created
- applying users terraform
Setup base cluster            ... done! [2 in 4m22.629s]
Install apps to cluster       ... done! [4 in 4m22.629s]
- executed users terraform successfully
- To use your cluster port-forward - argocd
- If not automatically injected, your kubeconfig is at:
- k3d kubeconfig get kubefirst
- Expose Argo-CD
- kubectl -n argocd port-forward svc/argocd-server 8080:80
- Argo User: admin
- Argo Password: ABC

Signed-off-by: 6za<EMAIL_ADDRESS>

init screen: (cloud)
-----------
Follow your logs with:
   tail -f  /home/developer/app/logs/log_1673280898.log

-----------
-----------

  ----------------------------------------------------------------------
  Info summary:
  ----------------------------------------------------------------------

  Operational System: linux
  Architecture: amd64
  Go Lang version: vgo1.18.6
  Kubefirst config file: /home/developer/.kubefirst
  Kubefirst config folder: /home/developer/.k1
  Kubectl path: /home/developer/.k1/tools/kubectl
  Terraform path: /home/developer/.k1/tools/terraform
  Kubeconfig path: /home/developer/.k1/gitops/terraform/base/kubeconfig
  Kubefirst Version: development

- Sending installation telemetry
Download dependencies         ... done! [3 in 6.765s]
Get Account Info              ... done! [1 in 7.514s]
Get DNS Info                  ... done! [1 in 8.437s]
Test Domain Liveness          ... done! [1 in 9.531s]
Create Buckets                ... done! [1 in 18.434s]
Create SSH keys               ... done! [1 in 18.594s]
Clone and Detokenize (GitOps) ... done! [1 in 23.214s]

aws-gitlab create:
-----------
Follow your logs with:
   tail -f  /home/developer/app/logs/log_1673280929.log

-----------
-----------

  ----------------------------------------------------------------------
  Info summary:
  ----------------------------------------------------------------------

  Operational System: linux
  Architecture: amd64
  Go Lang version: vgo1.18.6
  Kubefirst config file: /home/developer/.kubefirst
  Kubefirst config folder: /home/developer/.k1
  Kubectl path: /home/developer/.k1/tools/kubectl
  Terraform path: /home/developer/.k1/tools/terraform
  Kubeconfig path: /home/developer/.k1/gitops/terraform/base/kubeconfig
  Kubefirst Version: development

Process Parameters            ... done! [1 in 0s]
- Sending installation telemetry
- Creating K8S Cluster
- Created Softserve
- Waiting Softserve
Prepare Temporary Repo        ... done! [4 in 15m7.39s]
- Softserve Update
- Deploy ArgoCD
- ArgoCD Ready
- ArgoCD available at http://localhost:8080
- Setting argocd credentials
Deploy CI/CD                  ... done! [5 in 2m9.463s]
- Getting an argocd auth token
- Waiting vault to be ready
- Vault available at http://localhost:8200
- Waiting gitlab to be ready
- Gitlab available at http://localhost:8888
- Gitlab setup tokens
- Gitlab terraform
Setup Gitlab                  ... done! [6 in 6m8.193s]
- Gitlab ready
- waiting for vault unseal
- Vault configured
Configure Vault               ... done! [2 in 40.882s]
- Vault secret created
- Waiting for Gitlab dns to propagate before continuing
- Pushing gitops repo to origin gitlab
- Adding the registry application registered against gitlab
- deleting argocd-server pod
- waiting for argocd to be ready
- Port forwarding to new argocd-server pod
- Syncing the registry application
Finalize Gitlab updates       ... done! [3 in 3m37.304s]
- ArgoCD DNS is ready
Configure Vault Backend       ... done! [1 in 19.097s]
- Vault backend configured

-----------
Follow your logs with:
   tail -f  /home/developer/app/logs/log_1673289716.log

-----------
-----------

  ----------------------------------------------------------------------
  Info summary:
  ----------------------------------------------------------------------

  Operational System: linux
  Architecture: amd64
  Go Lang version: vgo1.18.6
  Kubefirst config file: /home/developer/.kubefirst
  Kubefirst config folder: /home/developer/.k1
  Kubectl path: /home/developer/.k1/tools/kubectl
  Terraform path: /home/developer/.k1/tools/terraform
  Kubeconfig path: /home/developer/.k1/gitops/terraform/base/kubeconfig
  Kubefirst Version: development

Process Parameters            ... done! [1 in 0s]
- Sending installation telemetry
- Creating gitops/metaphor repos
- Creating gitops repository with terraform in GitHub
Setup gitops on github        ... done! [3 in 50.117s]
- GitHub terraform applied
- Created GitOps Repo in github.com/org
- Creating K8S Cluster
- Attempt to recycle certs
- Install ArgoCD
- ArgoCD Ready
- ArgoCD available at http://localhost:8080
- Setting argocd credentials
- Getting an argocd auth token
- Syncing the registry application
- Setup ArgoCD
- Setup ArgoCD
- Waiting vault to be ready
- Vault available at http://localhost:8200
- Setup Vault
- waiting for vault unseal
- Vault configured
- Vault secret created
- Terraform Vault
- applying users terraform
Install apps to cluster       ... done! [6 in 22m16.232s]
Setup base cluster            ... done! [3 in 22m16.232s]
- Waiting chartmuseum


Remove the mirror-rolling-to-master workflow.

We no longer need to keep that compatibility, so just drop it.

https://github.com/Mergifyio backport jazzy humble


Add data lineage plug-in

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
将sql，脚本，spark，flink 等这些，添加血缘插件，支持血缘输出
https://github.com/melin/sqlflow
Use case
No response
Related issues
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

同时将血缘数据推送到apache atals

Project melin/sqlflow is not under the apache license. This feature would not be accepted.


Not in HACS anymore

Can't find the repo in HACS?
Have installed manually just pointing out it.

Nevermind was searching from my mobile, found it


TypeError: expect(...).toHaveMethod is not a function

I've been trying to add jasmine-matchers to my Karma tests for a while now, and apparently it refuses to load.
I have the following config (with the irrelevant items left out):
        frameworks: [
            'requirejs',
            'jasmine',
            'jasmine-matchers'
        ],

        // list of files / patterns to load in the browser
        files: [
            // ...
            'src/test/javascript/test-main.js'
        ],

        browsers: [
            'PhantomJS'
        ],

        plugins: [
            'karma-jasmine',
            'karma-jasmine-matchers',
            'karma-requirejs',
            'karma-junit-reporter',
            'karma-chrome-launcher',
            'karma-firefox-launcher',
            'karma-phantomjs-launcher'
        ]

The only thing I can think of that may collide is requirejs. The log shows that jasmine-matchers.js was indeed requested and loaded, also, looking at the browser running the karma tests, I can see jasmine-matchers.js in the resources tab.
Is it possible the karma-jasmine-matchers doesn't play nice with requirejs?

Which version of karma jasmine matchers are you on? I think that matcher landed in the most recent release.

Yes, it would appear that it was on the 2.0.0-beta1 branch, which npm did not install by default. It may be worth to mark those in README.MD so that it's clear what's currently available and what is not.

A README update would be helpful for this, I ran into the same issue.

Sorry about this @MadaraUchiha @Dianna, please find the README updated.


H2 font size is 20px when it should be 24px on pf-next.com

https://pf-next.com/components/Content/examples/
"Second level" should be 24px, currently showing as 20px.

this could be related to #610


Do not include symbols defined in driver/others/parameter.c in DYNAMI…

…C_ARCH
driver/others/parameter.c does not get build during DYNAMIC_ARCH, thus,
do not declare its symbols. This will make the build fail early and in
an obvious way if functions are trying to use these symbols.
This helps to catch issues like the one fixed in PR #3547 / PR #3580 earlier
as they become obvious when building the library already.
Signed-off-by: Egbert Eich<EMAIL_ADDRESS>

I like to think that that particular problem was a one-off (more related to the fairly recent addition of bfloat16 rather than a recurring problem with DYNAMIC_ARCH additions, but I guess it cannot hurt to have this guard. (And at some point we may want to add fp16 or other datatypes, creating a new opportunity to repeat the mistake)

@martin-frbg - thanks for accepting this! I believe the problem mentioned was introduced with the introduction of the Intel Cooperlake support - at least this is where I had bisected it to. Thus I was assuming that the introduction of further optimized kernels for other arches may potentially risk the same.


id is not always a field on models, use pk instead

If the primary key of a model is not auto, then it should be accessed by pk:
https://github.com/djangonauts/django-hstore/blob/master/django_hstore/fields.py#L251

thank you very much @stringfellow


Update MD file on new branch 2017-12-03_19-28-17

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef1.md
:white_check_mark:Succeeded

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


Unexpected value '[object Object]' imported by the module 'AppModule

I'm getting an error when I'm running the application. I followed the steps in your docs.
That's why I have something like this in my app.module.ts:
import {DndModule} from 'ng2-dnd';
@NgModule({
imports: [
DndModule.forRoot()
]
I installed ng2-dnd using this command jspm install npm:ng2-dnd. This is what my systemjs config looks like:
config.js
paths property:
"npm:*": "jspm_packages/npm/*",
map property:
"ng2-dnd"<EMAIL_ADDRESS>"@angular/common": "npm<EMAIL_ADDRESS>"@angular/compiler": "npm<EMAIL_ADDRESS>"@angular/core": "npm<EMAIL_ADDRESS>"@angular/forms": "npm<EMAIL_ADDRESS>"@angular/http": "npm<EMAIL_ADDRESS>"@angular/platform-browser": "npm<EMAIL_ADDRESS>"@angular/platform-browser-dynamic": "npm<EMAIL_ADDRESS>"@angular/router": "npm<EMAIL_ADDRESS>Whenever I load the application, I get this error:
Error: (SystemJS) Unexpected value '[object Object]' imported by the module 'AppModule'
Error: Unexpected value '[object Object]' imported by the module 'AppModule'
How do we fix this issue?

Any update?


Move sysext image creation to shared helper

The code to package the folder in filesystem image was shared. To ease maintenance and adding new features like systemd-repart for GPT images with dm-verity, move it to an own helper. While doing so we can also support the new properties that we added in systemd 252.
How to use
You can use the bake.sh script also standalone to make an image of a folder you prepared.
Testing done
Tested wasmtime, docker release, and torcx conversion sysext images for amd64 and arm64, checked on Alpha that the ARCHITECTURE field and OS=_any works.

Updated the README, too


fixed markdown formatting

in the release notes for v5.0.* it looks like someone missed 3 backticks which caused a section to become formatted as bash code.

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


Sound skips and rattles heavily from Windows to Linux (xrdp) or Windows Server (RDS)

Using the latest FreeRDP 2 builds (#648) and connecting from Windows to either Linux (xrdp 0.9.10) or Windows Server (RDS 2016) results in sound skipping and rattling frequently. This problem is present for some time now.
I’m using the following command for the connection with the Windows and Linux server:
wfreerdp.exe /v:hostname /cert-tofu /u:Administrator /p:password /sound:format:0x0001 /w:1000 /h:600
Several optimization tactics, like sound formats, quality, latency and network detection were used with very limited success, usually only delaying the sound skipping and rattling.
Also, using sound formats (e.g. WAVE_FORMAT_MPEGLAYER3 0x0055) other than PCM (0x0001) while connecting to Linux (xrdp 0.9.10) server will result in client immediately exiting when playing any kind of sound with [com.freerdp.client.common] - Network disconnect.  Debugging shows “rdpsnd_virtual_channel_client_thread reported an error. Error was 13”

@vscfreire

for some time now is how long? last commit there was ages back. (we´d appreciate some windows maintainer/tester for early feedback)
Could you describe your setup with a bit more detail? I sometimes use the windows client and did not have that particular problem (but most of the time just listen to some video in background)
Your 'optimization is not really one, better not do that (format` option that is). (most of the time that only leads to more issues, should really remove that option ;))
the xrdp mp3 abort is expected, you can´t use a codec that is not compiled into the client. (and it is part of the EXPERIMENTAL ones, so they are buggy anyway) (not really a bug as the only way you can force this is by forceful command line override)

@vscfreire just tried the current nightly build https://ci.freerdp.com/job/freerdp-nightly-windows/arch=win64,label=vs2013/lastSuccessfulBuild/artifact/build/Release/wfreerdp.exe against various servers (rds and direct connections) and did not experience rattling or similar.
Could you provide a short description of your test routine to allow reproducing this?

@vscfreire Ok, did finally manage to reproduce, it was the missing latency estimation.
This still has some small glitches when reconnecting to a e.g. browser running a youtube video but the problems occurring with 'rattles' seem to be fixed.

@akallabeth Connecting to either Windows or Linux server seems much better now (with PCM). In both cases, sometimes (~20%) the sound starts perfect but after a minute or more the skips and rattles come back. If I stop and start the clip/video again it appears to fix it.
There's another situation, if I omit the sound format parameter to force PCM, the connection to Windows Servers 2016 (from a Windows 10) the FreeRDP client states: Opening device with format WAVE_FORMAT_AAC_MS [backend WAVE_FORMAT_PCM]. In this case I get sound distortion/rattle from the beginning (but no skipping).
In terms of environment, fairly standard Windows 10 (1903) on the client side, and a low latency, high throughput WAN connection to the server side ( Linux xrdp 0.9.10 or Windows Server RDS 2016).  The WAN connection it's over IPSEC with 0% packet loss and 6 ms average rtt.

@vscfreire

hmm, how do you get AAC support compiled in? our windows builds do not link against any AAC decoder, in that case better check your buildconfig.
Could you check if the issues stop if you always wait until a packet is played (remove the while(winmm->diff == 0... check in channels/rdpsnd/client/winmm/rdpsnd_winmm.c)?

@akallabeth

I have compiled freerdp with ffmpeg in windows to test different codecs. That's also how I was testing MP3 with Linux XRDP server. I can test other codecs in the Windows client if you like.

I tried removing the cycle and it gets more prone to rattling. However I noticed that without it, the lip sync is better.

@vscfreire ok. some notes:

Never really got mp3 running with xrdp and have no windows 7 that announces it (therefore it is experimental)
Which AAC decoder backend are you using? Have had success with ffmpeg and faad under linux, but windows never tried.

@akallabeth
Was trying to find a way to help you reproduce the problems and introducing even a very small packet loss (1% or 0,5%) in the connection triggers it. There's a really simple utility to simulate several network conditions on Windows: https://jagt.github.io/clumsy/.
With Windows, I'm using the ffmpeg backend, but just tried using faad in Linux and the sound works great connecting to Windows Server, even with induced latency and drops. Also tried PCM in Linux and it's also really resilient to network conditions.

@vscfreire ok, so it is the winmm backend that is (still) not working well :/ (the rest of the path is the same on all os)

@vscfreire Ok, is the current nightly working?

Can not reproduce with nightly build https://ci.freerdp.com/job/freerdp-nightly-windows/656/

Sorry for the late reply.
I'm still getting problems, when using the latest nightly build (656) on Windows (x86_64).
Tried the latest nightly on Linux (connecting from the same network to the save Windows Server 2016 machine) and the sound is just perfect, spot-on.
Is there any additional info I can provide to help debug the issue?

Just to complement what I said regarding the latest nightly (running on Windows)...
Sometimes I connect and the sound is perfectly synced and with no skipping/rattling. But if I disconnect and reconnect to the same session, the sound is now skipping/rattling again. And it stays that way until I disconnect. Sometimes this reconnect makes things worse, sometimes it improves a bit (and sometimes it becomes perfect).

In the latest build (Nightly build 710, win32, vs2013) the sound is always skipping. The last time I tested, some times it worked but in the latest build, I can't get proper sound anytime. (windows 10 desktop to windows 2016 server)

Ok, #5818 should (finally) fix this one. please confirm


Variable initialisation

Variables (e.g. column_variables.jl) are initialised with zero. Is there any reason for doing so? If not why not using NaN for floats and typemax or typemin for ints?

Does it matter, it will be overwritten anyway? To initialise arrays as with NaNs we would need to do
julia> fill(convert(NF,NaN),2,3)
2×3 Matrix{Float16}:
 NaN  NaN  NaN
 NaN  NaN  NaN

for example, such that for ever NF<:AbstractFloat there needs to a conversion from NaN to whatever NaN corresponds to in NF.

No it's not a performance issue. In both cases memory is allocated and filled with bits. Doesn't matter what those are.
julia> using BenchmarkTools
julia> c = NaN
julia> @btime fill($c,1000,1000);
  1.160 ms (2 allocations: 7.63 MiB)

julia> c = 0.0
julia> @btime fill($c,1000,1000);
  1.163 ms (2 allocations: 7.63 MiB)

Note that in the dynamics we allocate with zeros, and I never had a debugging-related issue with this. Happy for you to convert the initialisation for ColumnVariables to init with NaN, if people prefer that. I would suggest to define
function nans(::Type{T},dims...) where T
     return fill(convert(T,NaN),dims...)
end

in utility_functions.jl such that zeros(NF,...) works as nans(NF,...)
julia> nans(Float16,2)
2-element Vector{Float16}:
 NaN
 NaN

julia> nans(Float32,2)
2-element Vector{Float32}:
 NaN
 NaN

nans has been added now ☝🏼


display multiple subtitles

I may just be missing some docs somewhere because I found what seems to be relevant code. So pardon in advance if this is already covered somewhere.
Anyway, Is it possible to display multiple subtitles at the same time?
like one on top, and the other on bottom?
Regards

no one ?

@rafa8626  is there any way to achieve this?

sad to hear that :(

is it possible to make like ...
make a video object or something which plays only subtitle floating above base video, while still syncing with the base video which have their own subtitle, so that multiple subtitle could be implemented in that way?

I would love to that, but it is possible to style the track element?


Add Vegan dinner event

Took close to 3min writing this on the phone using the GitHub code editor.

CI would validate the json, so that we don't merge a bad change.


Linked List Algorithm Implementations (Intermediate)

Here is a list of algorithmic implementations using a linked list,

Design Linked List -
Rotate List -
Insert Into a Sorted Circular Linked List -
Add Two Numbers -
Remove Nth Node From End of List -
Copy List with Random Pointer -
Remove Duplicates From The Sorted List (Second Version) -
Reorder List -
Linked List Cycle (Second Version) -
Reverse Linked List (Second Version) -
Linked List In Binary Tree -
Insertion Sort List -
Remove Zero-Sum Consecutive Nodes from Linked List -
Partition List -
Sort List -
Design Phone Directory -
Convert Sorted List to Binary Search Tree -
Swap Nodes in Pairs -
Split Linked List in Parts -
Add Two Numbers(Second Version) -
Flatten a Multilevel Doubly Linked List -
Odd-Even Linked List -
Linked List Components -
Next Greater Node in Linked List -
Plus One Linked List -
Convert Binary Search Tree to Sorted Doubly Linked List -

Work upon these algorithms are going on.

Hi there! I found this Project on FOSS United Foundation's FOSS HACK 2020 event website. I have the read the Documentation and I wanted to contribute to the Sorting Algorithms and its Visualization as mentioned on the Documentation under the section saying "Algorithms Yet to Publish".


zfs-replicate: 1.1.14 -> 1.2.0

This fixes the build failures when switching to NixOS 20.09 and needs to
be merged into that branch as well.  Let me know if that's another pull
request I need to submit.
I've verified this functions with: nix-build . -A pkgs.zfs-replicate
and I no longer get the errors I was getting when switching to 20.09
without this version change.

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

I'm not sure why the binary isn't finding the python modules any longer and when running result/bin/zfs-replicate I get an ModuleNotFoundError on the package itself.  Any assistance would be appreciated as Python isn't something I'm super familiar with any more.

Alright, I got it figured out (problems with setup.cfg and namespace packages).  Everything should be good to go now.  I'll ensure the fixes are landed on the zfs-replicate side as well.

This is identical to the referenced commit but must still be ported to stable.  How do we go about that?  Do I need to mark the other pull request as this one has been?

https://github.com/NixOS/nixpkgs/pull/101970 was merged in place of this PR. Thanks @alunduil!


PHOENIX-6693 Remove Hbase 2.1 and Hbase 2.2 support from Phoenix

@stoty - looks like a bunch of test failures around the refCount leak check in tearDown, particularly in DateTimeIT and SequenceIT, plus a couple misc. test failures.

@gjacoby126 The refCount tests have been randomly failing for a long time.
ConcurrentMutationsExtendedIT and PartialIndexRebuilderIT are respectively flakey and always fail even without this patch.
I've investigated ConcurrentMutationsExtendedIT and PartialIndexRebuilderIT, and those failures seem to be tied to Hbase 2.4. PartialIndexRebuilderIT always fails with HBase 2.4.11, while ConcurrentMutationsExtendedIT is flakey with 2.4.11.
I've run these two tests with HBase 2.3.7, and both passed 3 out of 3 times.
Opened PHOENIX-6702 for the test failures.
@elserj Yes, I've aimed to keep the behaviour exactly the same as before, just moving some code around classes.
Opened PHOENIX-6703 for the STREAM vs PREAD issue.


Defer File Highlight until the full DOM has loaded.

This allows the File Highlight plugin to work properly even when the script is loaded before the elements that should have a file loaded into them.

Thanks!

Thanks @chriswells0!
However, no browser we’re targeting doesn't support addEventListener. This is a pointless check that adds pointless extra code for everyone. Can we please remove it?

However, no browser we’re targeting doesn't support addEventListener. This is a pointless check that adds pointless extra code for everyone. Can we please remove it?

Good point. I've removed the check.

no browser we’re targeting doesn't support addEventListener.

I thought that was the case, but I'm old school and struggle with telling browsers "no."  ;)  I'll get used to it one day.


Change Vector, Quaternion, and Matrix Classes to use [ ] Operator for Accessing Elements

To eventually support using auto-generated code from SymPy, add [] operators to the matrix and vector (and quaternion?) classes.
As with std::array and std::vector, the [] operator will not have bounds checking (no throws, assert though?). Create a .at() accessor (or change the () accessor?) to perform bounds checking (and throw errors).
Vector<2> vec;
vec[1] = 123;  // no checks, but debug assert

Matrix<2,3> mat;
mat[1,1] = 456; // no checks, but debug assert

vec.at(0)  // check
mat.at(1,1) = 456;  // check

I learned you cannot overload operator[] for two arguments, just one. Therefore, I'll keep the operator() but change it to have no bounds checking, but create at() accessors that will include bounds checks (like std::array).


Add a shorter alias for the whereami command

Your proposal
Add an alias for whereami called w. Or something else short.
Additional context
Since the list command is stateful (continuing to print source code below if you run it multiple times), I find myself using whereami instead. But I wish it had a short alias (like list has l). I've already mistyped whereami as both wherami and once I even forgot the last bit and simply typed where, both of which crash with a NoMethodError.
Reading through https://github.com/ruby/debug/issues/639 it seems the idea of allowing users to alias @ whereami would be added but since it hasn't been done I think it would be better to just add it to the defaults.
@ would be similiar to pry so maybe that makes it easier for some people to switch?

👋  IRB has both whereami and the @ alias for it. You can use binding.irb as breakpoints and then activate the irb:rdbg integration to access debug commands, then you get features from both tools.


Windows: Context menu doesn't work in ARM64

I am going to merge this PR for insiders testing and follow-up on the arm64 issue.

Originally posted by @deepak1556 in https://github.com/microsoft/vscode/issues/151186#issuecomment-1287124875

Hi @joaomoreno @deepak1556 -- do you know what version of Windows you were testing against for the context menu not showing up on ARM64, and is this blocking bringing the context menu entry to the stable release?

Same issue. VSCode version VSCodeUserSetup-arm64-1.87.0.exe
System information
OS 名:                  Microsoft Windows 11 Pro
OS バージョン:          10.0.22631 N/A ビルド 22631
システム モデル:        Windows Dev Kit 2023
システムの種類:         ARM64-based PC

@luojunyuan Not sure if this is requested here, but have you been able to install with traces as described here: https://github.com/microsoft/vscode/issues/171911#issuecomment-1882892289?


[Feature] dbt_clone sf implementation

resolves #672

Description
adding the macros needed on adapter side for dbt_clone and trying to design adapter zone version of Clone tests from defer_state in https://github.com/dbt-labs/dbt-core/pull/7881

Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have signed the CLA
[ ] I have run this code in development and it appears to resolve the stated issue
[ ] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
[ ] I have run changie new to create a changelog entry

@McKnight-42 Separating the tests here from the boilerplate in defer_state makes sense, thanks for doing this.
I'll leave it up to you whether to test the messages or not, but we should test that we get 3 table materializations and 1 view materialization in Snowflake.

yeah figure once I get these tests working for snowflake I'll go remove the defer_state test in core and just create a dbt_clone adapter zone test we can pull into adapters to run.

flagging that only failing tests are for dynamic tables currently.