Improve ellipsis support, for some value of improve

This PR changes two features of ellipsis support.

If the output has changed, mdx tries to preserve ellipsis lines - before, they would all be expanded. A test is included.
If an output line ends with an ellipsis, then only the rest of the line has to match - this allows very limited partial matching of lines (but useful for things like shell error messages where the prefix is portable but the precise text of the message is not)

The second change is obviously not wholly backwards compatible (an existing Press any key to continue... line of output will now match Press any key to continue...!, for example)

That looks like a good idea. Thanks for the patches!

Could you also add a few notes about this feature in README.md?

Ping :)

Getting there - though probably not until later in the week! @trefis - this won't be an immediate silver bullet for Merlin, since MDX needs back-ported support for OCaml 4.02-4.05 added before it can be used for the testsuite

(sorry - juggling OCaml 4.08 reviews and, unusually, providing a taxi service for my cat.......)

I'm happy to merge this PR now and add documentation later (see #70)


include: zephyr: sys: util: Add type check for macro DIV_ROUND_CLOSEST

Add type check to avoid comparing unsigned values with 0 which is always true or false and can cause coverity issue.
Fix #81936

@andyross I think the difference is the cast (__typeof__(n))-1) is evaluated differently depending on type of n, it does not tight to unsigned or signed value so that coverity will not complain.
But coverity is just a tool and it sometimes (if I don't want to say often) reports "fake" issues and we ignore them rather often :-). This is a medium priority issue so we can choose fix or does not fix it.
FYI, Linux does use typeof check for this same macro


Wasm: runtime failure for NotifyCollectionChangedEventArgs

The following code:
        var e = new NotifyCollectionChangedEventArgs(NotifyCollectionChangedAction.Add, new string[] { "1" });
        if (e.NewItems != null)
        {
            foreach (string newItems in e.NewItems)
            {
            }
        }

Causes the runtime exception
exception thrown: RuntimeError: function signature mismatch,RuntimeError: function signature mismatch
    at S_P_CoreLib_System_Runtime_CalliIntrinsics__Call<IntPtr> (wasm-function[801]:0x75e1b)
    at S_P_CoreLib_Internal_Runtime_EEType__GetArrayEEType (wasm-function[381]:0x2a027)
    at S_P_CoreLib_System_Runtime_DispatchResolve__FindInterfaceMethodImplementationTarget (wasm-function[373]:0x292eb)
    at System_ObjectModel_System_Collections_Specialized_ReadOnlyList__GetEnumerator (wasm-function[2668]:0x1af87d)
    at HelloWasm_Program__Main (wasm-function[496]:0x3e4f5)
    at HelloWasm__Module___MainMethodWrapper (wasm-function[479]:0x36aa9)
    at StartupCodeMain (wasm-function[469]:0x364dc)
    at __managed__Main (wasm-function[20456]:0xf91e44)
    at main (wasm-function[22390]:0x10d38c7)
    at E:\github\corert\tests\src\Simple\HelloWasm\bin\Debug\wasm\native\HelloWasm.js:1969:22

Not really sure how to fix this
        [RuntimeExport("GetSystemArrayEEType")]
        private static unsafe EEType* GetSystemArrayEEType()

The RuntimeExport function pointer is the one that ends up in main.cpp which does not get the wasm shadow stack arg:
static const pfn c_classlibFunctions[] = {
    &GetRuntimeException,
    &FailFast,
    nullptr, // &UnhandledExceptionHandler,
    &AppendExceptionStackFrame,
    nullptr, // &CheckStaticClassConstruction,
    &GetSystemArrayEEType,

But its called from managed IL through the CallIIntrinsic which wants to inject the shadow stack argument and hence there is a mismatch.

What I do see is some provision here in CalliIntrinsic
            if (target.Name == "StdCall")
                flags |= MethodSignatureFlags.UnmanagedCallingConventionStdCall;

But maybe that's for something else as that flag is not set for EEType.GetArrayEEType

What I do see is some provision here in CalliIntrinsic

Yes, that's for something else.

One way to fix this would be to inline GetSystemArrayEEType in EEType to avoid the problematic indirection.
internal EEType* GetArrayEEType()
{
#if INPLACE_RUNTIME
   return EETypePtr.EETypePtrOf<Array>().ToPointer();
#else
   ... existing impl...
#endif
}

Thanks!, that fixes it


[DEV-2666]&[DEV-2670] Integrate p2b, forward on pass

Release Checklist
Pre-Release

[ ] Check migrations

No database related infos (sqldb-xxx)
Impact on GS (new/removed columns)

[ ] Check for linter errors (in PR)
[ ] Test basic user operations (on DFX services)

Login/logout
Buy/sell payment request
KYC page

[ ] Add env parameter

Post-Release

Test basic user operations
Monitor application insights log

[ ] Add env parameter


Trusted publishing

I’m looking into using RubyGems’ trusted publishing to push a gem from a GitHub action (example). @rubocop/rubocop-rspec Do you see any downsides to this approach?

I think there doesn't seem to be any particular downsides.


Belarus (BY): add January, 2nd as a national holiday

Hurray!
From 2020 the second of January is the new national holiday in Belarus (New Year) according to the presidential decree #464:
"New Year - 1 and 2 of January"

Pull Request Test Coverage Report for Build 661

9 of 9 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 657:
0.0%

Covered Lines:
49602

Relevant Lines:
49602

💛  - Coveralls

Merged into beta.. Thank you very much!
Cheers
dr-p


Update swagger.yaml

This updates the swagger.yaml to have the new refresh by org endpoints and also the security definition and endpoint authorization.   This was generated using the generateYaml test.  Not sure why there's so many formatting changes.

Re-opening for testing

Coverage increased (+0.05%) to 70.921% when pulling dfed06d8db01039ff92ebb021e6c610e98b940b7 on feature/swaggerYamlUpdate into d9a17c10c5fc8e9b3954f1a5dfcdc018a7bcadf1 on develop.

Coverage increased (+0.05%) to 70.925% when pulling f54710f5f209c69279a10312efbd383c2b6a71da on feature/swaggerYamlUpdate into d9a17c10c5fc8e9b3954f1a5dfcdc018a7bcadf1 on develop.


Add a \nicefrac-like function (and ideally make the default / operator configurable)

I've been working on this function that makes something similar to LaTeX's \nicefrac:
#let over(a, b) = $#h(0pt)^(#scale(a, 140%)) #h(-1pt) slash #h(-2.5pt)_(#scale(b, 140%))$
$over(a, b)$ yields:

My function is very hacky and should instead be implemented properly. Following is an example of where it fails:
$a/(over(b, c))$ yields:

It would be even better if the behavior of the / operator was configurable in the template! i.e. the user could switch between the current default, a literal slash, or a nicefrac-like result.

I just wanna mention that a more modern version of nicefrac is https://ctan.org/pkg/xfrac?lang=en

This looks decentish. Obviously the parameters can be tweaked
$ a / (#move(dy:-0.3em, dx: 0.1em)[$#text(size:0.8em)[b]$] #h(0cm) slash #h(0cm) #move(dy: 0.1em, dx:-0.1em)[$#text(size:0.8em)[c]$]) $

Ooh, that's quite good, actually! I didn't know about the move function. Out of curiosity, is this how something like this would be implemented? Perhaps this isn't the place to ask, but how exactly does the typesetting/spacing happen?

Whilst this behaviour could probably be done by following what pkgs like xfrac, nicefrac, and faktor on CTAN do, the more robust solution I think is to make use of the so called "Skewed fractions" which are layouted using skewedFractionHorizontalGap and skewedFractionVerticalGap from the MathConstants table of the font.
LuaTeX has support for this through the \Uskewed primitive:
\[
  1 / 2
  { {1} \Uskewed / {2} }
  { {1} \Uskewed / exact {2} }
  { {1} \Uskewed / noaxis {2} }
  { {1} \Uskewed / exact noaxis {2} }
\]

\[
  a / b
  { {a} \Uskewed / {b} }
  { {a} \Uskewed / exact {b} }
  { {a} \Uskewed / noaxis {b} }
  { {a} \Uskewed / exact noaxis {b} }
\]

\[ { {\mathbb{R}[X]} \Uskewed / {X^2 + 1} } \]

\[ { {\sum_{i=1}^n k[X]} \Uskewed / {\sum_{i=1}^n k[X] \cdot \theta_i} } \]

We could perhaps consider scaling the fraction slash as well so that the last two examples above look nicer.
I think exposing this to the user would make the most sense through a field on math.frac, maybe style, which takes a string of either "skewed" or "display". (We could also add in "inline", which would display the slash verbatim, solving #3203.)

I think an argument for math.frac would be quite nice. We could also have a fourth option that automatically selects display or inline depending on whether the current math size is display or nine. Perhaps auto. Not sure whether it would be a suitable default or not.
Regarding inline, there was some problem with parentheses though in https://github.com/typst/typst/pull/4480.

Just had a quick read of that PR, is the issue to do with how $(a + b)/c$ should be displayed (with or without parentheses) when we have inline fractions?


Firefox: ReferenceError: customElements is not defined

Extension has stopped working after update to 1.5.6. Stopped at loading screen. There's reference error in console:

ReferenceError: customElements is not defined

Firefox 57, ubuntu

@Evgeny- Updated firefox extension to v1.5.7.

It works! Thank you!


Nextjs Contentful not showing all images

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
d2fqmcz003hgr1
Region
eu-west-2
Amplify Console feature
Redirects
Describe the bug
Some images do not load after the build and they are being fetched from contentful. Everything works fine locally
https://blog.daba.school/
I have tried adding the images rewrite/redirect rules, still no effect.
Expected behavior
All images should show
Reproduction steps
npm run build
npm run start
Build Settings
No response
Additional information
I have added this in the rewrite rules </^[^.]+$|\.(?!(css|gif|ico|jpg|js|png|txt|svg|woff|woff2|ttf|map|json)$)([^.]+$)/> to point to https://d2jw0ckg3954v4.cloudfront.net/<*>

But it works with the cloudfront url

hi @Onibenjo what version of Next.js are you using? and can you share any configurations you have in your next.config.js file. thanks

@Athena96
Next.js version 11.0.1
//next.config.js
module.exports = {
  images: {
    domains: ['images.ctfassets.net'],
  },
}

We're trying to reproduce this problem but it looks like everything is working ok, can you let us know if it's working as expected now?


easysnmp session.set problem

Hi,
I have the following code:
    session = Session(hostname=Hostname, community=Community, version=2)

.................................................
session.set('<IP_ADDRESS>.4.1.6<IP_ADDRESS>.<IP_ADDRESS>.67108864', '2','i')
For the last line I get the error:
session.set('.<IP_ADDRESS>.4.1.6<IP_ADDRESS>.<IP_ADDRESS>.67108864', '2','i')
File "/usr/lib64/python2.7/site-packages/easysnmp/session.py", line 351, in set
success = interface.set(self, varlist)
easysnmp.exceptions.EasySNMPUndeterminedTypeError: a type could not be determine for the object
Thank you for your help.

I think this is poor  documentation on our half, but can you try using "INTEGER" instead of 'i' for the type?
Thanks.

@fgimian: I've created a small patch in a separate branch to support snmpset(1) short types. Do you think this is something we should incorporate in the project? Secondly, should we do it in C or in the Python interface (before the interface.set is called)?

Hi,Thanks for the prompt response. It works with 'INTEGER'. I have a misunderstanding: how can I delete an object of type Session?
Best Regards,Octavian
 On Thursday, July 16, 2015 7:57 PM, Naveen Nathan<EMAIL_ADDRESS>wrote:

@fgimian: I've created a small patch in a separate branch to support snmpset(1) short types. Do you think this is something we should incorporate in the project? Secondly, should we do it in C or in the Python interface (before the interface.set is called)?—
Reply to this email directly or view it on GitHub.

@Dacicus there's no need to delete the Session, it doesn't retain a persistent connection since SNMP is using SNMP and Python will garbage collect it as soon as it's out of scope.
Would you like to point me to your branch to check out?  I can provide further advice from there :smile:
Thanks
fotis

I have no branch yet. I started learning python and test easysnmp library. So far I have worked in linux shell with NET-SNMP.

Thanks for the helpOctavian
 On Friday, July 17, 2015 10:10 AM, Fotis Gimian<EMAIL_ADDRESS>wrote:

@Dacicus there's no need to delete the Session, it doesn't retain a persistent connection since SNMP is using SNMP and Python will garbage collect it as soon as it's out of scope.Would you like to point me to your branch to check out? I can provide further advice from there  Thanks
fotis—
Reply to this email directly or view it on GitHub.

@Dacicus Apologies, I edited my message after I saved.  My question about the branch was actually meant towards @nnathan :smile:

@fgimian: I disguised it as a hyperlink in my last message, but here it is again: https://github.com/nnathan/easysnmp/commit/0e39b601a99fc47eaa06ad5685e69dbd6f2827e0

Thechanes look good @nnathan feel free to merge them in :smile:

Changes are now merged and now snmp_type can be specified using the snmpset(1) short types: https://github.com/fgimian/easysnmp/pull/29.

How can I install/upgrade the easysnmp library that supports the short types in snmpset ?
Thank you,
Octavian

Until a new minor version is released you can use the git version.
pip install git+http://github.com/fgimian/easysnmp


Use a WeakMap and fix memory leak

Pretty sure the current code has a memory leak in it since nothing is removing DOM elements from the elements array. Using a WeakMap instead of an array should properly deal with this leak.
Thanks!

Hi @mikeycgto ! Changes look awesome, I think its a good idea to use WeakMap.
Do you what happened in the dist file? it shows -1,157 changes. Happy to get it merged after we solve that :)

Sorry about that! My npm run build initially failed because I was missing the bower package, hence bad diff.
This should be good now. Thanks for the quick feedback!

@mikeycgto will you be interested of being part of the repository? I can add you as contributor and give you publish rights on npm as well.
I believe there are some things we can improve if you are motivated:

Remove /dist from Git.
Remove Bower
Introduce Webpack
Use new Javascript features

What do you think? :)

Yeah that would be great! We can introduce babel to and use es6 syntax. I'd also like write some simple tests as well.

Awesome! You are collaborator here and on npm now 🍾 .
I will create some issues now to track the stuff we want to do :)


Fix: action icon size

When the width of the vue-devtools is not large, the action icons disappear
Example of an error is shown in the screenshot.

1


RCTRenderingPerf does not expose ReactPerf.printExclusive()

Description
When calling RCTRenderingPerf.stop, we automatically get the output from ReactPerf.printInclusive() and ReactPerf.printWasted(), but have no way of getting ReactPerf.printExclusive(), as it is not exposed by the module.
Reproduction Steps and Sample Code
The following code will trigger the output from printInclusive and printWasted:
import PerfMonitor from 'react-native/Libraries/Performance/RCTRenderingPerf'

PerfMonitor.toggle()
PerfMonitor.start()
setTimeout(() => {
    PerfMonitor.stop()
}, 1000)

Solution
Expose the output functions to be called directly instead of automatically calling some inside stop.
import PerfMonitor from 'react-native/Libraries/Performance/RCTRenderingPerf'

PerfMonitor.toggle()
PerfMonitor.start()
setTimeout(() => {
    PerfMonitor.stop()
    PerfMonitor.printExclusive()
    PerfMonitor.printInclusive()
    PerfMonitor.printWasted()
}, 1000)

I am happy to do a merge request for this.
Additional Information

React Native version: 0.43.3

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with Canny! Check out its new home: https://react-native.canny.io/feature-requests/p/rctrenderingperf-does-not-expose-reactperfprintexclusive


Chinese fonts in iOS app set Locale in Japanese

I have an issue that the text in the iOS app display in Chinese font.
I tried three patterns. all patterns don't work.
In the iOS simulator, the text display in Japanese font, but it doesn't work in the build iOS app.
How can I reflect localization?

set locales in supportedLocales.

    return MaterialApp(
        　　localizationsDelegates: [
              GlobalCupertinoLocalizations.delegate,
              GlobalMaterialLocalizations.delegate,
              GlobalWidgetsLocalizations.delegate,
            ],
            supportedLocales: [
              const Locale('ja', 'JP'),
            ],
        .....
        );

set locale in TextStyle

　Text('', style: TextStyle(
　　　　fontWeight: FontWeight.bold,
　　　　locale: Locale('ja', 'JP'),
      )),

set CFBundleLocalizations in iOS/Runner/info.plist

  <key>CFBundleLocalizations</key>
   	<array>
   		<string>ja</string>
   	</array>

Expected results:

Actual results:
Chinese font

the screenshot in app setting in the iOS simulator

the screenshot in app setting in the iOS simulator

Logs

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 2.0.3, on macOS 11.2.3 20D91 darwin-x64, locale ja-JP)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
[✓] Xcode - develop for iOS and macOS
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.1)
[✓] VS Code (version 1.54.3)
[✓] Connected device (1 available)

• No issues found!

How can I reflect localization?

@ryomoro Can you try below solutions and see if they work for you ?
#14128 (comment)
#14128 (comment)

Thank you for providing me the information.
I was setting the Localizations in Runner.xcworkspace, but it doesn't work.
Where can I find Localized resources can be mixed?

@ryomoro
Check this and see if it helps.

@ryomoro
Check this and see if it helps.

I tried it, but it didn't work.

work.

flutter doctor -v
[✓] Flutter (Channel master, 2.1.0-13.0.pre.346, on Mac OS X 10.15.4 19E2269
    darwin-x64, locale en-GB)
    • Flutter version 2.1.0-13.0.pre.346 at
      /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision 8158b478d7 (2 hours ago), 2021-03-31 13:29:03 +0800
    • Engine revision dbcbf69a57
    • Dart version 2.13.0 (build 2.13.0-175.0.dev)

[!] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    ! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin
        code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see
      https://guides.cocoapods.org/using/getting-started.html#installation for
      instructions.

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

[✓] VS Code (version 1.54.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.20.0

[✓] Connected device (4 available)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 89.0.4389.114

! Doctor found issues in 1 category.

flutter doctor -v

Should I try to build an app with Channel master?

@ryomoro you may try that but I saw the issue on master, but you can always try that on latest and see if issue still persists or not.

@darshankawar I solve this issue, because of my using package.
https://github.com/DarshanGowda0/GeoFlutterFire/issues/151#issue-849118651

@HansMuller @gspencergoog @jason-simmons I'm not sure how the locale gets set in a way that would impact font sets, particularly on a physical iOS device but not the simulator.  Any hints about where to start looking?
(Tim passed this issue along from a customer.)

Some fonts provide locale-specific glyphs for a given Unicode value.  If a font supports this feature, then the locale can be selected using the TextStyle.locale API in Flutter.
To debug this further it would help to see the exact text/fonts/device where the issue is happening.
In order to get precise control over text rendering, the app may need to embed the desired fonts instead of relying on whatever fonts happen to be available in the host system.


Unable to compile on MacOS

I followed the installation directions, with minor exceptions for my OS version (13.3.1).  I have the latest Xcode installed and made sure my other software was setup per directions.
I changed "export MACOSX_DEPLOYMENT_TARGET=11.0" to use targets 13.0 and 13.3.
In short, I get Fortran runtime errors when I make the OpenBLAS:

At line 170 of file sblat2.f (unit = 6, file = 'stdout')
Fortran runtime error: Bad STATUS parameter in OPEN statement

then

At line 145 of file sblat3.f (unit = 6)
Fortran runtime error: Cannot open file '': No such file or directory

Make then gives up with a segmentation fault.
I need OpenBLAS to run wxmaxima, which has it as a dependency (but does not try to compile it properly).
The log is attached.
OpenBLASerror.txt

It's GNU Octave that requires OpenBLAS.

The warnings about stdio.h look a bit strange - what compiler version does cc point to, could this be some outdated version of gcc ?  (What does cc -v report ?)

Everything points to Clang, even though I also have GNU C suite.

Very strange, also the fortran warnings about a bad STATUS parameter - these should definitely not occur with any somewhat recent gfortran. Is it possible that you have multiple versions of gfortran installed, and your build is picking up parts (e.g. runtime libraries) of an incompatible earlier version (as was the case in #2303) ?

It turns out my gcc/gfortran configuration was a mess.  After cleaning it up and reinstalling gcc using Homebrew, I used Macports to install OpenBLAS, which it refused to do in the first place without raising an error message.  So, everything is working better now.  Thanks!


installation under MinGW/MSYS does not work

Hi!
I tried to let the script make an installation under MinGW/MSYS, but it did not work. The first crashes made clear that I should add wget and svn. After these had been installed, I re-ran the script, the runlog of which is attached to this message. Somehow, my gcc compiler was not approved of, with a reference to a file config.log with details. Unfortunately, this platform does not allow for uploading files of type .log, so I renamed it to config.txt. The config.log that I found in subdirectory gcc-trunk-build was renamed to config_2.txt and also attached. Please tell me how to proceed!
Regards,
Arjan
runlog.txt
config.txt
config_2.txt

Hi Arjan,
When I have seen this before, it's usually because the the CC variable didn't get set correctly by the script.  Are you able to set the CC  environment variables to a working C compiler of your choice and ensure that the environment variable gets passed to the install.sh script?  In a bash shell, for example, you might do so with the gcc compiler by invoking the script as follows:
CC=gcc ./install.sh
or, if the compiler is not in your path, then
CC=/absolute/path/goes/here/gcc ./install.sh
Here's a bit of explanation that might help.  install.sh works its way recursively down the following dependency stack looking to find or install each package and progressing to the next lower package when it cannot find a given package and will therefore need to install one or more prerequisites for building the missing package:
mpif90 wrapping gfortran 5.1.0 or later
gfortran 5.1.0 or later
flex
bison
From the 'runlog.txt' file, it appears that you probably restarted install.sh after a previous run (which is run), the install.sh script found the flex source tar ball that was a downloaded during the previous run, and you approved using it to build flex.  In order to reach the flex build, install.sh has to first complete its search for an mpif90 wrapping gfortran 5.1.0 or later.  If that isn't found, it searches for gfortran 5.1.0 or later itself (which might be present even if mpif90 doesn't wrap it).  If that isn't found, the script searches  for flex.  In your case it finds the flex source, at which point it prepares to build flex by setting the CC=gcc variable if CC is empty.  If CC is not empty, then it leaves the CC value untouched.  Therefore, if you're certain that you have gcc on your system, then hopefully you can fix this problem by setting CC and ensuring that the CC value get passed to the subshell that launches when the script launches.  The aforementioned syntax
CC=gcc ./install.sh
ensures that the environment variable passes to a subshell in bash.  You might need another way to ensure the passing if you're using a different shell.
Unfortunately, I am going to be extremely pressed for time over the next several days so it might take me a day or two to respond to issues this week.

Hi!
Thanks for the suggestions, but my agenda is pretty crammed either, so I will check what you wrote, but only in a few days.
Cheers,
Arjan

Op 7 dec. 2015 om 00:05 heeft sourceryinstitute<EMAIL_ADDRESS>het volgende geschreven:
Hi Arjan,
When I have seen this before, it's usually because the the CC variable didn't get set correctly by the script. Are you able to set the CC environment variables to a working C compiler of your choice and ensure that the environment variable gets passed to the install.sh script? In a bash shell, for example, you might do so with the gcc compiler by invoking the script as follows:
CC=gcc ./install.sh
or, if the compiler is not in your path, then
CC=/absolute/path/goes/here/gcc ./install.sh
Here's a bit of explanation that might help. install.sh works its way recursively down the following dependency stack looking to find or install each package and progressing to the next lower package when it cannot find a given package and will therefore need to install one or more prerequisites for building the missing package:
mpif90 wrapping gfortran 5.1.0 or later
gfortran 5.1.0 or later
flex
bison
From the 'runlog.txt' file, it appears that you probably restarted install.sh after a previous run (which is run), the install.sh script found the flex source tar ball that was a downloaded during the previous run, and you approved using it to build flex. In order to reach the flex build, install.sh has to first complete its search for an mpif90 wrapping gfortran 5.1.0 or later. If that isn't found, it searches for gfortran 5.1.0 or later itself (which might be present even if mpif90 doesn't wrap it). If that isn't found, the script searches for flex. In your case it finds the flex source, at which point it prepares to build flex by setting the CC=gcc variable if CC is empty. If CC is not empty, then it leaves the CC value untouched. Therefore, if you're certain that you have gcc on your system, then hopefully you can fix this problem by setting CC and ensuring that the CC value get passed to the subshell that launches when the script launches. The aforementioned syntax
CC=gcc ./install.sh
ensures that the environment variable passes to a subshell in bash. You might need another way to ensure the passing if you're using a different shell.
Unfortunately, I am going to be extremely pressed for time over the next several days so it might take me a day or two to respond to issues this week.
—
Reply to this email directly or view it on GitHub.

It does look like the issue is finding the C compiler, as Damian mentioned above. You may also run into #81 if get a little bit further, but of course we'd love to hear otherwise...

The compiler version (2.95, built in 1999) looks like it might be a little weak. Is there a minimumgcc version that is able to build gfortran?

I would recommend mingw-get-setup.exe from http://sourceforge.net/projects/mingw/files/ to get a more recent gcc build compiler and environment. Then, open up a bash shell and try the install again.

Today, I deleted all old attempts and directories and went to the suggested http://sourceforge.net/projects/mingw/files/ for a fresh basic gcc and performed the installation. Then I re-downloaded wget.exe, placed it in C:\MinGW\msys\1.0\bin, and started the install script for opencoarrays as suggested earlier as follows:
CC=gcc ./build.sh flex >& runlog_flex.txt
It crashed, see attachments (config.log was renamed to config.txt, since this site does not want to upload .log-files...).
New suggestions?
runlog_flex.txt
config.txt

It appears the problem is with the pre-installed C compiler.  config.txt contains
gcc.exe: installation problem, cannot exec `cc1': No such file or directory
Please let us know if this page helps.

I agree it looks like you have not properly installed the new compiler, it still is using the old one. Make sure you are using the msys shell that you recently downloaded, it has the paths set to the right compiler and tools. You want to see a compiler version that looks like 4.8 or 4.9, typing "gcc -v" will display the version.

I was sure that I had erased any old gcc stuff before I made my new attempt today, including the desktop icon to the MSYS shell. Therefore the old version number of gcc puzzled me. I typed "which gcc" and got /c/FPC/2.6.2/bin/i386-Win32/gcc.exe, so it appears that gcc is first found in my ancient FreePascal installation! Now I am re-trying my opencoarrays installation with explicit path specified for gcc. Keep fingers crossed!

The log now tells me that it does use gcc version 4.8.1, but installation still crashes, see attachments:
configure:2965: /c/MinGW/bin/gcc -V >&5
gcc.exe: error: unrecognized command line option '-V'
gcc.exe: fatal error: no input files
compilation terminated.
How to proceed?
config.txt
runlog_flex.txt

This might be an install script problem, it looks like runtime headers are not installed.
For a Windows build using Mingw, the Mingw runtime needs to be downloaded and the headers installed to a directory under the sysroot named "/mingw/include" before starting the configure. This library is largely a thin interface to the Microsoft C runtime DLL "msvcrt". After the compiler is built, but before it starts to build its language runtime libraries, the mingw runtime needs to be built and installed to a directory named "/mingw/lib". The Windows pthreads implementation is included with the mingw runtime, and headers and libraries should be built/installed like the main runtime.
Since the install uses svn, that makes getting the runtime easy at
svn://svn.code.sf.net/p/mingw-w64/code/trunk
It uses the normal "configure" style build.

@SourcerersApprentice, from what you've written above, I assume the "install script problem" you're referencing is not an OpenCoarrays installation script (i.e., not "install.sh" or "build").   If I'm incorrect and there is a problem with an OpenCoarrays installation script, please let me know.

If the OpenCoarrays install script is meant to support Mingw compiler builds, then there is a problem with the script. The extra runtime pieces described above should be considered as a prerequisite for the compiler, and are a substitution for libc. If the install script was only intended to support Cygwin environments (this sort of seems implied), then what we are trying is experimental. We know that we can't take the coarrays build all the way yet with mingw, but there are no high hurdles to jump getting the gfortran build part working. If you want to add this ability, I am willing to help out when you hit any sticky patches.

Ideally OpenCoarrays would support every common platform on which one expects users to write CAF programs.  That certainly includes Windows.  I have no strong opinion about whether it includes Cygwin, Mingw or any other Windows environment only because I haven't used any of them in years and I wrote the installation script.  If those who use Windows regularly suggest that Mingw should be supported, then I would gladly incorporate any edits to the script required to support it.  The biggest problem we face is simply access and expertise.  If someone would like to contribute to improving the script, I would be glad to walk anyone interested through the details of the script to help out.  Then it would be best if one of you forks the repository, creates a new branch for madden the edits, and submits a pull request.

My scripting skills aren't really strong, but I do know how to do the Windows build, so I am willing to give it a try. I won't be able to get to it until mid-next week, though.

For a Windows build using Mingw, the Mingw runtime needs to be downloaded
and the headers installed [...] svn://svn.code.sf.net/p/mingw-w64/code/trunk

I don't have the 64-bits version of Windows-7 installed, though that would have been possible on this box. Therefore, I fear that the svn link given above may not lead to something working on my 32-bit Windows-7 machine. Furthermore, my experience with svn is nil. Can I instead amend my MinGW/MSYS installation with the "MinGW Installation Manager"? That tool is rather cumbersome, so some assistance in which items to select is welcome. I will now proceed and activate all stuff under "Basic Setup" (I had most of it installed, but not yet everything) and then re-try the opencoarrays installation.
I do agree that it would be nice that if an OpenCoarray install were to support MinGW/MSYS, then this type of handlings would in the future preferably be caught and dealt with by the script and not by the user. I hope that someone capable of updating that script, and in the position to put some time in it ;-)) , will stand up and put this a step further. And there is no rush, I just want to use the new SUBMODULES feature, but otherwise my code runs fine, so mid-next week is okay for me!

My preference would be to work on this sometime after January 19.  Please feel free to book a time at http://rouson.youcanbook.me.  My bash scripting skills were non-existent before writing the install.sh.  I picked up everything I needed to know by the online search-copy-modify method.  Let's plan to talk through what is in the script and what needs to be done.

I have caf.c . You can compile coarrays. The method for compiling is : gcc -c -o caf.o caf.c. A fortran program is  compiled with : gfortran -cpp -gfortran=lib nameOfProgram.f90 cof.o.
I tested the OpenCoarrays porgrams: allocate_as_barrier.f90 Test passed. co_broadcast.f90 Test passed. hello_multiverse.f90 Test passed. syncall.f90 Test passed. syncimages.f90 Test passed. syncimages2.f90 Test passed. test1.caf Test passed. whole_get_array.f90m Test 5 fails.
If you run with a.exe the program uses NumberOfProcessor of Windows. else a.exe -n 2 the program uses 2 processors.

I am sorry. gfortran -cpp -fcoarray=lib nameOfProgram.f90 cof.o

@JulioBeneyto I'm glad to hear you were able to compile and run OpenCoarrays. However, could you please give us some additional details about your system and setup? Also, it appears that you may be leaving something out, since I see no linking happening with an MPI implementation.
Please include the following details:

OS and version
Linux emulation environment and version (i.e., Cygwin or MinGW/MSYS)
MPI implementation and version
All additional linking and compiling commands and their outputs

Thanks!

Hi Izaak
1.- Windows 7 64 bits
2.- Cygwin & MinGW/MSYS
3.- MPI implementation don't have.
4.- First gcc -c -o caf.o caf.c and their outputs is 'caf.o'
Finally you compile gfortran -cpp -fcoarray=lib NameOfProgram.f90
caf.o to run ./a or ./a -n (2,3,..,32)
Please see the file attached caf.zip
Thanks Julio
El 2016-02-06 16:51, Izaak Beekman escribió:

@JulioBeneyto [1] I'm glad to hear you were able to compile and run
OpenCoarrays. However, could you please give us some additional
details about your system and setup? Also, it appears that you may be
leaving something out, since I see no linking happening with an MPI
implementation.
Please include the following details:

OS and version
Linux emulation environment and version (i.e., Cygwin or
MinGW/MSYS)
MPI implementation and version
All additional linking and compiling commands and their outputs

Thanks!
--
Reply to this email directly or view it on GitHub [2].

Links:
[1] https://github.com/JulioBeneyto
[2]
https://github.com/sourceryinstitute/opencoarrays/issues/40#issuecomment-180796705

@JulioBeneyto I'm still confused, why would  you want to build OpenCoarrays without MPI? Also, what is the file caf.c you mentioned? The main OpenCoarrays implementation is in https://github.com/sourceryinstitute/opencoarrays/blob/master/src/mpi/mpi_caf.c
I'm guessing that what you're seeing is gfortran's single processor support for CAF? Maybe @rouson or @fanfa can weigh in here.
For example, what happens when you run this program on 4 processors:
      program main
        use iso_c_binding, only : c_int
        use iso_fortran_env, only : error_unit
        implicit none
        integer(c_int) :: tally
        tally = this_image() ! this image's contribution
        call co_sum(tally)
        verify: block
          integer(c_int) :: image
          if (tally/=sum([(image,image=1,num_images())])) then
             write(error_unit,'(a,i5)') "Incorrect tally on image ",this_image()
             error stop 2
          end if
        end block verify
        ! Wait for all images to pass the test
        sync all
        if (this_image()==1) write(*,*) "Test passed"
      end program

Hi Izaak
Because OpenMPI of Cygwin and MinGW don't support multi-process.($
ompi_info the answer is MPI_THREAD_MULTIPLE: NO)
caf.c is my mpi_caf.c, it uses CreateProcess (win32 API) to create
multi-process. The information,it's sent to other process via shared
memory.
You program main.f90 is 0K with:
integer(c_int) :: tally[*]
If you compile with
gfortran -cpp -fcoarray=lib main.f90 caf.o
./a
Test passed
./a -n 4
Test passed
Bye

Hi all, this thread has been dormant for quite some time. If you really want to use OpenCoarrays on Windows, your best bet is probably some sort of Linux virtualization. I highly recommend vagrant (www.vagrantup.com) with VirtualBox. It currently sounds as though the issues are on the mingw/cygwin side, and neither platform is officially supported at this time. If you have made any more attempts to get this working, we'd certainly love to hear about them, but for now I'm going to mark this issue as "won't fix" and close it due to inactivity and no official support or means for us to reproduce the issue.


Enable Xml values bigger than 250char

Remove the length limitation of Xml node value

Lovely. I will look into your code this week! Thanks, Gunnar!

Code does not compile. You are missing declaration of new field "Value Blob". Is that all that is missing, or were other parts left out? Please double check, before I proceed.


Rephrase the preserve static IPs warning message

Reference: https://issues.redhat.com/browse/MTV-1503
Based on Doc's review, rephrase the warning message for preserving static IPs while using Pod networking.
Change the PlanWarningCondition component to enable flexible formatting of the suggested section.
Screenshot

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 36.21%. Comparing base (13484d0) to head (eee3bc2).
Report is 146 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1405      +/-   ##
==========================================
- Coverage   36.81%   36.21%   -0.60%
==========================================
  Files         158      159       +1
  Lines        2548     2579      +31
  Branches      599      601       +2
==========================================
- Hits          938      934       -4
- Misses       1428     1630     +202
+ Partials      182       15     -167

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


use UniRx(UniRx.Async) with Entities(Unity ECS)

workaround.
set following code after RuntimeInitializeLoadType.BeforeSceneLoad.
// get ECS PlayerLoop
var playerLoop = ScriptBehaviourUpdateOrder.CurrentPlayerLoop;

// set to UniRx.Async PlayerLoop
PlayerLoopHelper.Initialize(ref playerLoop);

refer: http://notargs.hateblo.jp/entry/ecs_unirx

Shoudn't this be part of the Readme for now ?

solved in https://github.com/Cysharp/UniTask/issues/6


OPENAI_ENDPOINT support

#16

Thank you, this looks good! I'll test and merge tomorrow most likely.

Question, what if I add an OpenAI compatible endpoint like from a model provider like OpenRouter @ https://openrouter.ai/api/v1 and I want to modify or select an alternative/different model to carry out the ops? just adding the endpoint will not be suffice right? will this need to turn into an issue itself?

Question, what if I add an OpenAI compatible endpoint like from a model provider like OpenRouter @ https://openrouter.ai/api/v1 and I want to modify or select an alternative/different model to carry out the ops? just adding the endpoint will not be suffice right? will this need to turn into an issue itself?

@AxDSan Yes for this purpose I want to allow for adding dynamically configured models to supplement the default OpenAI models. These would then integrate with the plandex models and plandex set-model commands. Apart from the endpoint, I think they would also need to specify an associated environment variable to read the api key from.
But until that's done, I think the OPENAI_ENDPOINT in this PR is a good and simple stopgap measure.

Yup totally understandable, I'd also assume the OPENAI_API_KEY environment variable can be interchangeable with the OpenRouter key, but for sake of SOC it would be good to just do what you say instead, which is introducing a way of reading the env var to read the api key from. OPENROUTER_API_KEY or something.

I saw in #65 that the OPENAI_API_BASE was rejected in favor of this OPENAI_ENDPOINT.
However, OPENAI_API_BASE is the convention used by OpenAI's Python library etc. Ideally it should be the same here, to keep things consistent.

Thanks @ErikBjare, I didn't realize that. I'll add support for OPENAI_API_BASE in the next release for standardization, and make that the default in the readme/docs, but still keep support for OPENAI_ENDPOINT as well to avoid a breaking change for anyone who starts using it in the meantime.


[ERR] NANN: Unable to retrieve chan status for Channel(): edge not found

Background
bitcoind node and lnd node were offline for like 1 month.

I run lncli restorechanbackup.
Your environment
lnd-0.11.1-beta
Linux 5.9.8-gentoo
bitcoind (bicoin core) v<IP_ADDRESS>-gentoo
Expected behaviour
Sats from Remote Forced channel closes return to wallet.
Actual behaviour
Not all funds come back (some did).
I censor all hashes here with XXX and number them so you can refer to them, if you need them for debugging (just ask).
lnd gives repeatedly (but else functioning well, but my sats are still not all back):
[ERR] NANN: Unable to retrieve chan status for Channel(XXX:1): edge not found
I get three different categories of closed channels (existing resolution: CLAIMED, UNCLAIMED) and no resolution existing. Actually some funds got back and are now CLAIMED, but not all. So the problem is the UNCLAIMED and those without resolution.
How do I claimed those sats? What do I need to do?
The command lncli closedchannels for those two problematic categories, gives:
{
"channel_point": "XXX1",
"chan_id": "XXX2",
"chain_hash": "XXX3",
"closing_tx_hash": "XXX4",
"remote_pubkey": "XXX5",
"capacity": "XXX6",
"close_height": XXX7,
"settled_balance": "XXX8",
"time_locked_balance": "0",
"close_type": "REMOTE_FORCE_CLOSE",
"open_initiator": "INITIATOR_REMOTE",
"close_initiator": "INITIATOR_REMOTE",
"resolutions": [
{
"resolution_type": "COMMIT",
"outcome": "UNCLAIMED",
"outpoint": {
"txid_bytes": "XXX9",
"txid_str": "XXX10",
"output_index": 0
},
"amount_sat": "XXX11",
"sweep_txid": "XXX12"
}
]
},
{
"channel_point": "XXX13",
"chan_id": "XXX14",
"chain_hash": "XXX15",
"closing_tx_hash": "XXX16",
"remote_pubkey": "XXX17",
"capacity": "XXX18",
"close_height": XXX19,
"settled_balance": "0",
"time_locked_balance": "0",
"close_type": "COOPERATIVE_CLOSE",
"open_initiator": "INITIATOR_LOCAL",
"close_initiator": "INITIATOR_UNKNOWN",
"resolutions": [
]
},

Need additional information, @dsche-cyber contacted me on Slack and we're going to try to resolve it there.
My first suspicions are:

Offline peer
Outputs small enough to sweep at time

Will comment here what the final outcome was.

That error is also a sign that possibly they were running an earlier (possibly master version?) of thee latest logic used to enable/disable channels.

@dsche-cyber what's the status on this issue? Were you able to do a full wallet rescan to fix your UTXO set?

@guggero By your recommendation rescanning is better done with closed channels. As one channel was still open, but one peer not responding, I force closed, so it will take some time until it is settled. Then I will try to rescan...

After waiting some time, funds return, but my lnd node didn't saw it. As @guggero recommended, I rescanned by following the guide:
https://github.com/lightningnetwork/lnd/blob/987edc9d810f000d97bc9ac3ba1668e3bec77018/docs/recovery.md
Now everything is fine, the funds from forced channel are back AND the funds that I was missing, when I openend this issue.
Thanks to @guggero, funds are SAFU!


The vsix versions have to increase for every build

Today the version of the vsixes that we produce are <IP_ADDRESS>. This means that when I do a build-to-build upgrade in willow, I don't get any new project system bits because the vsixinstaller thinks the vsix is already installed. We should have the buildnumber as version component similar to what we do for the templates vsix.
@natidea assigning to you since you fixed up the versioning for the templates vsixes.

@mavasani has fixed this.

@srivatsn I think we also need to tweak the versions in the Editor swr files. This one is still hardcoded to <IP_ADDRESS>: https://github.com/dotnet/roslyn-project-system/blob/master/src/VsixV3/EditorsPackage/Microsoft.VisualStudio.Editors.swr

This is now really done. Editor vsix has also been fixed.


Use caret for composer/installers dependency

https://getcomposer.org/doc/articles/versions.md
Also use version 1.0.23 and upwards to fix API deprecation warning https://github.com/composer/installers/releases/tag/v1.0.23

Thanks! I didn't expect such a nice birthday present from you :gift:


Some Emojis Not Supported

It seems like the :sunglasses: emoji isn't being parsed correctly for me. Is this a known issue?

It's supposed to be supported (see https://github.com/vdurmont/emoji-java/blob/master/src/main/resources/emojis.json#L416)
What's the issue exactly?

I have a string that contains the code point of the sunglasses emoji. When  I call EmojiParser.parseToAliases the resultant string shows garbage values rather than :sunglasses:

Confirmed. Cause was alias "sunglasses" existing twice, once for "dark sunglasses" and once for "Smiling Face With Sunglasses."
I'll make a fix.

Awesome. Thanks

See #24


fix(e2e): delete component after it refreshes

Fixes
https://issues.redhat.com/browse/RHTAPBUGS-1010

/lgtm


Doc suggestion: Object Detection - Data Preparation - using JSON files - snippet

Hello!
First of all - a BIG thank you for the new Data Preparation guide inside the Object Detection section!
When I read the Object Detection guide some time ago and looked at your definition of the bounding box I thought it would be the best to store the data inside a JSON file:
[{'coordinates': {'height': 104, 'width': 110, 'x': 115, 'y': 216},
  'label': 'ball'},
 {'coordinates': {'height': 106, 'width': 110, 'x': 188, 'y': 254},
  'label': 'ball'},
 {'coordinates': {'height': 164, 'width': 131, 'x': 374, 'y': 169},
  'label': 'cup'}]

I found the issue #721  and built a similar data structure:
{
	"image1.jpg": [
		{
			"label": "label1",
			"coordinates": {
				"height": 243,
				"width": 216,
				"x": 174,
				"y": 276
			}
		},
		{
			"label": "label2",
			"coordinates": {
				"height": 104,
				"width": 217,
				"x": 174,
				"y": 450
			}
		}, ...
	],
	"image2.jpg": [
		{
			"label": "label1",
			"coordinates": {
				"height": 173,
				"width": 314,
				"x": 324,
				"y": 254
			}
		}, ...
	]
}

Whenever I tried to use one of your SFrame.read_json APIs I was not successful, because it was a nested JSON object with arrays.
Inside the mentioned issue @znation (thank you for that!) suggested a solution on how to load the json file with the default json package and how to prepare it.
What was left for me was a "cook-book-like" recipe on how to load the images and merge them with their corresponding annotation data. I am not a Python  #developer so those things took quite some time.
Anyway, I found a solution which I will post here and maybe you'll find it useful and also add such an example to your guide. My example is not perfect (non native speaker, variable names) but feel free to use it as an inspiration.
#First include necessary modules
import turicreate as tc
import json
import os

imagepath = "./images"

# read the JSON file into an in-memory object
# the JSON file contains data like this:
#
# {
#	"image1.jpg": [
#		{
#			"label": "label1",
#			"coordinates": {
#				"height": 243,
#				"width": 216,
#				"x": 174,
#				"y": 276
#			}
#		},
#		{
#			"label": "label2",
#			"coordinates": {
#				"height": 104,
#				"width": 217,
#				"x": 174,
#				"y": 450
#			}
#		}, ...
#   ],
#	"image2.jpg": [
#		{
#			"label": "label1",
#			"coordinates": {
#				"height": 173,
#				"width": 314,
#				"x": 324,
#				"y": 254
#			}
#		}, ...
#	]
# }

with open('turiimagedata.json') as f:
    data = json.load(f)

# get that JSON object into SFrame format (gives a single column of [key, value])
# note that `items` is what allows us to map this key/value structure into a table structure
imageframe = tc.SFrame(data.items())

# transform the SFrame into two columns, and rename them appropriately
imageframe = imageframe.unpack('X1')
imageframe = imageframe.rename({'X1.0': 'name', 'X1.1': 'annotations'})

images = tc.image_analysis.load_images(imagepath, with_path=True,
                                                  random_order=True,
                                                  recursive=True)

# get the file name from the image path
# ./path/image.jpg -> image.jpg
imagenames = images['path'].apply(lambda path: os.path.basename(path).split('/')[:1])
imagenames = imagenames.unpack().rename({'X.0': 'name'})

# add this column to the image sframe
images = images.add_columns(imagenames)

# delete the now unnecessary path
del images['path']

# join the images with the annotations, we have more images than annotations,
# so therefore we join the frame with the images
imagesannotations = imageframe.join(images)

imagesannotations['image_with_ground_truth'] = tc.object_detector.util.draw_bounding_boxes(imagesannotations['image'], imagesannotations['annotations'])

imagesannotations.explore()

BR, Denise

It might actually be nice to add some API for this, so that users don't have to (otherwise) manually ensure that their annotations column matches up with however they're loading the image column


micsthepick: Watch our7107islands

micsthepick requests the watch of the watch_keyword our7107islands. See the Metasmoke search here and the Stack Exchange search here.

our7107islands has been seen in 1 true positive, 0 false positives, and 0 NAAs.

!!/approve

Coverage remained the same at 65.238% when pulling 861194bd9117975f12381367158d6b55176ded9e on auto-blacklist-1520840665.4379954 into 762c04bdc8c6daea7de147df7d2e5c03ebefed40 on master.

Reminder to $self: we want to remove this after a while and perhaps check if the domain name is watched and/or blacklisted now.


Cypress/E2E: Replaced file upload input selector

Summary

#fileUploadInput does not show up anymore in the DOM for file input
Added global uiUploadFiles and used on all previous #fileUploadInput

Cypress Run: webapp-pr-7634
Ticket Link
NA

Looks like several tests failed related to the changes here - https://mm-cypress-report.s3.amazonaws.com/3635-webapp-pr-7634-mattermost-enterprise-edition:c806601/mochawesome.html

Closing PR. Looks like the change in file upload is more restricted to some feature. Will need to further investigate


Please add official hubot adapter for Rocket.Chat to the list of adapters in docs

Please add our hubot adapter for  Rocket.Chat  to the list of adapters in the docs.
Repo with quick-start guide is located at official Rocket.Chat adapter.
We have created a docker image that can get devs hacking Rocket.Chat bots in minutes with minimal setup.
Thanks in advance.

Hi Sing-Li,
This sounds great. Can you submit a pull request adding the adapter to adapters.md?

@bhuga  Thanks.


fix some text issues with grammar and style

fix most common markdownlint violations
I have two questions:

There are many inline HTML, which are not recommended. I would prefer to fix it before merging this pr.
There are badges mentions in footer, but no badges themselves. Is it a bug or feature?

Hey @nett00n thank you for these improvements. From a first look, all looks great .
So to answer your question:

Some HTML is there for the centering I was using.
The badges in the footer is a bug indeed and can be removed

I'm currently planning on merging #36 . Which changes the whole structure of the project
so woud you mind either:

Porting your changes ta branch based on the new-structure branch and wait for it to merge first
Or I can just review this and we can merge and I'll look into the conflicts myself.

Thank you again this is very helpful. But I figured I needed to do some very necessary cleanup first

@Zehina I ported changes to new-structure branch. Here is PR

HTML usage in README.md minified
More linters added
black formatter for *.py added for more style and readability
everything I found had been fixed


Possible updates to Readme

@flauc ,
With the upgrade to 2.0.  I think we need to upgrade the ReadMe to remove
You also need to declare the library in your system.js config.
var map = { 'angular2-easy-forms': 'node_modules/angular2-easy-forms' },
var packages = { 'angular2-easy-forms': {main: 'components.js', defaultExtension: 'js'} }

and then change
//...
import {EasyFormsModule} from '/angular2-easy-forms';

import
@NgModule({
    imports: [
        BrowserModule,
        FormsModule,
        EasyFormsModule
    ],
    providers: [],
    declarations: [AppComponent],
    bootstrap: [AppComponent]
})
export class AppModule {}

Am I missing anything?

Are you using webpack or system.js? If you're using system.js i think you still need to add the map and packages variables in to your config.

I'm using webpack now.

Yes that's why you don't need to map the library. I should add the For system.js subtitle before that line.


oauth/services: don't abuse log.exception

log.exception should not be used outside exception handlers

Because else is not for unhandled exceptions but for code that does not raise any exceptions:
>>> try:
...   raise ValueError
... except KeyError:
...   pass
... else:
...   print('am not here')
...
Traceback (most recent call last):
  File "<stdin>", line 2, in <module>
ValueError

Yeah, I got confused. Sorry about that.
So, we probably want to refactor that code since if the else is excecuted when any exception was risen, why we are logging an error? It doesn't make sense to me.

Because of   if resp.status_code == 201: and the likes in the try block.

I understand. I'd say that code needs to be rewritten with an easy to follow and clear flow, then :)

If you have time I'd do some audit of try-else usage in RTD, the next PR is fixing another misusage :)

Thanks!


refactor: Refactor the convertor params type of computed property

Refactor the convertor params type from Array to Object in computed property hook

@markduan review please


Issue #922 - Suppress TSAN false race in 3rd party lib OpenSSL

see https://github.com/skupperproject/skupper-router/issues/922

Codecov Report
Patch and project coverage have no change.

Comparison is base (62a753c) 27.19% compared to head (cb66405) 27.20%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #974   +/-   ##
=======================================
  Coverage   27.19%   27.20%
=======================================
  Files         136      136
  Lines       32959    32959
  Branches     5316     5316
=======================================
+ Hits         8963     8965    +2
  Misses      22844    22844
+ Partials     1152     1150    -2

Flag
Coverage Δ

unittests
27.20% <ø> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/router_core/route_tables.c
17.21% <0.00%> (+0.27%)
:arrow_up:

src/router_core/address_watch.c
89.65% <0.00%> (+1.14%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Teach Prestaging to pre-set level and colour temperature on compatible bulbs

With this change Virtual Prestage will prime Hue bulbs (with the appropriate driver) to know the desired level + colour temperature so it will "be correct" immediately as it turns on, even if it was issued ON outside of Hubitat (eg: via Zigbee bindings).
RGB is not done only because I'm focused on CT right now, so not spending the time testing RGB just yet.
Tested with Hue bulbs w/ the Hue driver and Ikea bulbs w/ the built-in (Advanced) driver.

The reason this code got commented out was because Hubitat has decided that adding the LevelPreset capability was a mistake and plans to "clean it up" (i.e. remove it) at some point in the future. It's not something supported by Zigbee itself, just a quirky behavior of some bulbs that can't be reliably detected from the hub side.

Interesting.  Didn't see in that thread what that opinion was based on, but I found some of the ZigBee spec files and browsed through them.  I believe I found the line that they're probably referring to:

If one of these commands is received while the device is in its off state, i.e., the OnOff attribute of the on/off cluster is equal to 0x00, the command SHALL be ignored.

So all our drivers are in violation - the built-in one is turning on the bulb which is bad (and incredibly annoying for me as a user) and the custom Hue driver is remembering that it happened.
I also learned a few other things:

setting the level without turning on the bulb (ie: presetLevel) is actually part of the spec (variants with vs without "with on/off").  So that should live on forever.
setEnhancedHue is part of the spec, not something specific to Hue bulbs, so apparently the wrong way to sniff out that driver.
scene 0:0 may be a spec-compliant way of pre-seeing a bulb (for those that support the scene cluster).  But I need to experiment with that before I know for sure.


Additional Bugfix for Representative Day 2-D & 3-D Surface Gridded Emissions Files

CMAQv5.3.1-i4
Date: 2020-03-09
Contact: David Wong<EMAIL_ADDRESS>Description: Using a 2-D and/or 3-D Gridded Emission File with representative day format specified via runscript with the environmental variable GR_EM_SYM_DATE_XXX set to T will cause a model crash when reading time-dependent initial conditions (ICs) due to a memory issue. This issue stems from the choice to psuedo-interpolate the ICs instead of extracting them directly, which is problematic if an emissions file is a 2-D or 3-D Emissions file of representative type. This is because to linearly interpolate temporally, two points are required stored as the head and tail. The head was stored correctly, but the tail was not being stored correctly and was picking up from whatever was in memory last, which usually is the 2-D/3-D Gridded Emissions file. This resulted in an error when trying to extract the data at the second point as the IC file only has data at the head.
If no emissions are present, the interpolation would pick the point from whatever file was read last whether that be a MET file, bioseason file, lightning file or IC file.
It should be noted, this issue would have not been seen if the IC file were time independent as IOAPI ignores the time input when trying to extract data from time independent files.
Scope and Impact: The model will terminate execution with a time retrieval error for the initial conditions. No model results will change.
Solution: Replace CCTM/src/cio/centralized_io_module.F file in repository with the version located in the folder DOCS/Known_Issues/CMAQv5.3.1-i2. Directions on how to replace this file in your repository can be found in Appendix F of the CMAQ User's Guide. This code fix will also be included with the next minor CMAQ release.

Resolved with release of v5.3.2.
See v5.3.2 Release Notes.


Replacement?

Since this project is no longer maintained, what project takes its place in the Serde stack?

Nevermind, apparently it's the serde-xml-rs project.


docs(safari mobile): fixes issue with overlapping text in api docs with safari mobile.

Test this fix with Safari, Chrome, and Firefox at 600px width or less using this link: https://api-doc-styling-1.firebaseapp.com/docs/ts/latest/api/common/AbstractControl-class.html
CLOSES:
https://github.com/angular/angular.io/issues/1099

LGTM

merged!


Add debug gradient function to bevy_core_pipeline

Objective
When debugging shaders, overwriting a fragment's color with any arbitrary value can be useful. Usually, this is done by using a grayscale gradient, by replacing each color channel with the given value.
However, distinguishing between different shades of grey can be strenuous.
Solution
A color map is often used to represent values with colors, color maps give much better contrast between even similar values.
I adopted the matplotlib "plasma" color map, and implemented it as a shader function that can be imported with #import bevy_core_pipeline::debug_gradient.

Changelog

Add the bevy_core_pipeline::debug_gradient shader to convert a value between [0, 1] into the "plasma" gradient.

This is just "nice to have". The one issue with implementing this as a 3rd party crate is… I can't use it so easily when developing on bevy.


Mounting hole diameters

I noticed a few holes in the assembly where two parts are joined by a screw have the same inner diameter for the portion the screw should pass through (the clearance portion) as well as the part the screw should be threaded in to. Is this actually how it's printed? I might expect the inner diameter of the part the screw should thread in to to be slightly smaller or something, either to tap the hole or so a screw can self-thread.  Or I might expect the holes-for-threads to be somewhat wider than the clearance holes to accept a heat set insert or something.
Two specific cases I'm looking at now:

between the 4 walls of the body and each of the plates that connects the pairs of walls together
between the two halves of the Jetson mount
...there might also be others I'm not seeing right now, but I assume the answer is the same everywhere.

What kinds of fasteners do you use in these cases? Just a screw (self-tapping?), some kind of thread insert, or something else?
Thanks!

Sometimes I take a 3mm drill to the one that should be larger. I'm using 2.9mm self tapping countersunk screws.

Sometimes I take a 3mm drill to the one that should be larger. I'm using 2.9mm self tapping countersunk screws.


Added knowledge for qiskit 0.X to qiskit 1.0 migration

Describe the contribution to the taxonomy

Knowledge of Qiskit, IBM's open-source quantum computing library.
Context on how syntax looked with Qiskit 0.X, and the corrections that need to be made for Qiskit 1.0.

Input given at the prompt
Can you upgrade my Qiskit 0.X code? "
from qiskit import *

#Superdense Coding-send 11
qreg_q = QuantumRegister(2, 'q')
creg_c = ClassicalRegister(2, 'c')
circuit = QuantumCircuit(qreg_q, creg_c)

circuit.h(qreg_q[0])
circuit.cnot(qreg_q[0], qreg_q[1])
circuit.barrier(qreg_q[0])
circuit.barrier(qreg_q[1])
circuit.x(qreg_q[0])
circuit.z(qreg_q[0])
circuit.barrier(qreg_q[0])
circuit.barrier(qreg_q[1])
circuit.cx(qreg_q[0], qreg_q[1])
circuit.h(qreg_q[0])
circuit.measure(qreg_q[0], creg_c[0])
circuit.measure(qreg_q[1], creg_c[1])
"

Response from the original model
"This code snippet demonstrates the use of Qiskit 1.0 to create a superdense coding circuit with two qubits and two   │
│ classical bits, similar to the original response. However, it has been updated to correct errors in the previous     │
│ version, as described in the original response.                                                                      │
│                                                                                │
│ The code first initializes the quantum circuit with the specified registers:                                         │
│ ```python                                                                                │
│ from qiskit import *                                                                                │
│                                                                                │
│ #Superdense Coding-send 11                                                                                │
│ qreg_q = QuantumRegister(2, 'q')                                                                                │
│ creg_c = ClassicalRegister(2, 'c')                                                                                │
│ circuit = QuantumCircuit(qreg_q, creg_c)                                                                             │
│ ```                                                                                │
│ Then, it defines the quantum operations on the qubits:                                                               │
│ ```python                                                                                │
│ circuit.h(qreg_q[0])                                                                                │
│ circuit.cnot(qreg_q[0], qreg_q[1])                                                                                │
│ circuit.barrier(qreg_q[0])                                                                                │
│ circuit.barrier(qreg_q[1])                                                                                │
│ circuit.x(qreg_q[0])                                                                                │
│ circuit.z(qreg_q[0])                                                                                │
│ circuit.barrier(qreg_q[0])                                                                                │
│ circuit.barrier(qreg_q[1])                                                                                │
│ circuit.cx(qreg_q[0], qreg_q[1])                                                                                │
│ circuit.h(qreg_q[0])                                                                                │
│ ```                                                                                │
│ Finally, it measures the qubits and stores their classical results in the corresponding bits:                        │
│ ```python                                                                                │
│ circuit.measure(qreg_q[0], creg_c[0])                                                                                │
│ circuit.measure(qreg_q[1], creg_c[1])                                                                                │
│ ```                                                                                │
│ This code snippet showcases how to create a superdense coding circuit with Qiskit 1.0 and use it for error           │
│ correction purposes, as demonstrated in the original response."

Response from the fine-tuned model
│ Here is the upgraded Qiskit 0.X code for your Superdense Coding implementation:                                                                                │
│                                                                                │
│ ```python                                                                                │
│ from qiskit import *                                                                                │
│                                                                                │
│ #Superdense Coding-send 11                                                                                │
│ qreg_q = QuantumRegister(2, 'q')                                                                                │
│ creg_c = ClassicalRegister(2, 'c')                                                                                │
│ circuit = QuantumCircuit(qreg_q, creg_c)                                                                                │
│                                                                                │
│ circuit.h(qreg_q[0])                 # Hadamard gate on q[0]                                                                                │
│ circuit.cx(qreg_q[0], qreg_q[1])      # Controlled-X gate between q[0] and q[1]                                                                                │
│ circuit.barrier()                      # Barrier operation for error correction                                                                                │
│ circuit.barrier()                      # Barrier operation for error correction                                                                                │
│ circuit.x(qreg_q[0])                   # X gate on q[0]                                                                                │
│ circuit.z(qreg_q[0])                   # Z gate on q[0]                                                                                │
│ circuit.barrier()                      # Barrier operation for error correction                                                                                │
│ circuit.barrier()                      # Barrier operation for error correction                                                                                │
│ circuit.cx(qreg_q[0], qreg_q[1])       # Controlled-X gate between q[0] and q[1]                                                                                │
│ circuit.h(qreg_q[0])                   # Hadamard gate on q[0]                                                                                │
│ circuit.measure(qreg_q[0], creg_c[0])  # Measure q[0] and store the result in c[0]                                                                                │
│ circuit.measure(qreg_q[1], creg_c[1])  # Measure q[1] and store the result in c[1]                                                                                │
│ ```                                                                                │
│                                                                                │
│ This improved code snippet incorporates more detailed comments, making it easier for you to understand and implement. The hadamard gate is applied before the cx gate to ensure that     │
│ both qubits are in a superposition state before the controlled-x operation. The barrier operations are added after each gate to facilitate error correction. The measurement of q[0] and │
│ q[1] is performed at the end of the circuit to extract the classical information.                                                                                │
│                                                                                │
│ Feel free to ask any further questions or request clarifications regarding this improved code snippet!

Contribution checklist

[x] The contribution was tested with ilab generate
[x] No errors or warnings were produced by ilab generate
[x] All commits are signed off (DCO)
[x] The qna.yaml file contains at least 5 seed_examples
[x] The qna.yaml file was linted and prettified (yaml-validator can do both)
[x] An attribution.txt file in the same folder as the qna.yaml file
[x] Content does not include PII or otherwise sensitive or confidential information
[x] Content does not include anything documented in the project's Avoid these Topics guidelines

I'm sorry, but we are only taking approved source submissions right now. Until we have clear direction from Red Hat legal when it comes to IBM documentation. Please take a look at this to find the approved location resources. https://github.com/instructlab/dev-docs/blob/main/docs/knowledge-submissions-past-wikipedia.md
This is the upstream Taxonomy repository, if this was specific to the Watsonx challenge please close this PR and submit it to the correct repository.

I'm sorry, but we are only taking approved source submissions right now. Until we have clear direction from Red Hat legal when it comes to IBM documentation. Please take a look at this to find the approved location resources. https://github.com/instructlab/dev-docs/blob/main/docs/knowledge-submissions-past-wikipedia.md This is the upstream Taxonomy repository, if this was specific to the Watsonx challenge please close this PR and submit it to the correct repository.

Yep this is for WatsonX, we weren't aware there was another repo. I'll close this and send it over there. Thanks!


Failure using Code Assistant and Claude 2

In a ChatInput cell configured to use Anthropic Claude 2 and the Code Assistant persona I entered

Create a table listing the first 9 layers of Pascal's triangle. Include Wolfram Language code to generate the output

Got this response

The code is incorrect.
Describe the issue in detail here. Attach any relevant screenshots or files. The section below was automatically generated. Remove any information that you do not wish to include in the report.

 Later I saw this


Refactor remapping

This PR:

Remaps weights less in the post processing script
Unifies create_weightfile with that used in the remap_pipeline.jl

I think the next step we may be able to make is to parallelize the remapping in the post processing scripts

bors r+


ios click not working

Thanks for this amazing slider. We are using this very frequently but we found that on ios whether or chrome or safari click events on image which are part of carousel is not working. This issue is pretty specific to ios on all iphones and not happening on desktop or android. This has happened in your 0.21 or 0.20 build because it was working fine till 0.19.

@virajs07
Did you figure out what was wrong?

@victsant I had by mistake closed this issue. But we shifted to the previous version to make it work. Haven't found the reason for that. I will reopen the issue

Hi! I have the same issue on version 0.23.1. The click event on image is not triggered. I have surrounding the image with  to navigate to some pages. It works fine on desktop; however, it does not work at all on ios.

Which version?@virajs07

@virajs07 I was running into a similar issue where I had an on click event on a slide, but on iOS if you clicked on an image within the slide it didn't work. I found a workaround where I wrapped the image in the slide within a div and added pointer-events: none to the image itself. I added cursor: pointer to the image wrapper because of this but not sure if that part was necessary.

I had the same issue, but my <img> tag was inside an <a> tag. As @arteagabriel said, adding pointer-events: none to the <img> tag did the trick, but then it broke in IE-11.
So in order to make it work in both places, I added a display: block to the <a> tag.

I've also faced the same situation in iphone6 ios10 recently @thuctonhuyen , but it's fixed when it navigate to iphone 8+ ios 13.


[Question] - InfoWindow touch propagate to childView ?

Hi,
For a project I need to handle touch inside InfoWindow at a specific children view.
I have a Custom GoogleMap.InfoWindowAdapter returning a listview when getInfoWindow() is called. Each row of this ListView represent a ClusterItem with a label and a left and right ImageButton. How can I handle the click specifically on the right OR left ImageButton ?
map.setOnInfoWindowClickListener(clusterManager);
this methods can't propage the touch to childsView :
clusterManager.setOnClusterItemClickListener()
clusterManager.setOnClusterItemInfoWindowClickListener()
Screenshots:

Device and Android version:
Android 6.0
android-maps-utils 0.4.4

It's actually not related to this particular library. Google Maps in Android simply render your view and show it as image. So your views can't react to the clicks (or touches). For example, 3 years old question on SO http://stackoverflow.com/questions/20283539/button-onclicklistener-on-infowindow-in-google-map
Probably, the simplest way to achieve required result is to simply show custom Dialog at the location of Marker.
You may also play with overlay layout to get map scroll working when info window is shown, but it would require additional work (time investment)

Thanks for your answer, very usefull ! I close the issue


option to only regenerate old certificates

That would be a neat option, (eg: key expiring in less that )

It would be neat, but I don't think it's really necessary. The nice thing about Let's Encrypt is that you don't have to care about maximizing a certificate's lifetime (since it doesn't cost you any money to just get a new one). I renew my certs roughly every two months, and if I need a cert inbetween for a new (sub-)domain, I just get one and renew it together with the other ones, even though the new certificate is (much) less than two months old at that point.
Anyway, if you want to implement this without adding a lot of new complexity, feel free to do so!

Do you agree @drzraf there's nothing more here to be done and we could close it?

I don't completely agree.
I keep having email notification for old certificate even if I renewed them. Thus renewing needlessly imply needless "expiration notification".
Unrelated, but adding to this that even certbot makes very hard, if not impossible, to change email address when certificates are generated without certbot, https://github.com/certbot/certbot/issues/3839

Well, feel free to add support for this to the ansible role. :)
For a hackish implementation, you can dump the certificate with openssl x509 -inform pem -text -in {{ filename }}, grep for Not After, and extract the date (cut off everything until :). If you stored the result of grep in expiry_date, you can check whether it expires with:
``

name: Check for expiry
local_action: command python -c "from datetime import datetime, timedelta; datetime.strptime('{{ expiry_date[expiry_date.index(':')+1:].strip() }}', '%b %d %H:%M:%S %Y %Z' > datetime.now() + timedelta(weeks=1))"
register: expiring_soon
run_once: true
``
the variable expiring_soon should now contain "True" if the certificate expires in the next seven days, or "False" if not.

If you found a good solution for this, feel free to open a PR. Until then, I'm closing this.


component not rendered when route is pushed from saga middleware

To push to different location this is what I used.
function forwardTo(location) {
  console.log("location", history, location);
  history.push(location);
}

yield call(forwardTo, "/");

This just changes the url but not renders the component for that route.
I saw the line "connected-react-router" is not needed so I am not aware how it can be done without it.

https://github.com/react-boilerplate/react-boilerplate-cra-template/issues/32#issuecomment-633643478


Update Dutch translations

The previous translations were a bit weird in the context they are used.

Thanks for merging!


Devtools not being excluded in production (v5/alpha)

Describe the bug
I'm using the alpha (v5) version of tanstack query on a side project and I have added the devtools. The dependency ("@tanstack/react-query-devtools": "^5.0.0-alpha.72",) is installed as a dev dependency (also tried as normal dependency). I'm using it on a NextJS v13 app generated with created-next-app.
The app is being deployed to Vercel.
The same setup but using react-query v4 was working and deploying to production without a problem.
Your minimal, reproducible example
https://github.com/kaumac/rank-tt
Steps to reproduce
Running npm run build should trigger the error
Expected behavior
As a user, I expect to not have the devtools as part of the production bundle, but its happening and breaking production builds.
How often does this bug happen?
Every time
Screenshots or Videos

Platform
Mac OS 12.6
Tanstack Query adapter
react-query
TanStack Query version
5.0.0-alpha.72
TypeScript version
5.1.5
Additional context
No response

seems to be the same error as in this issue:

https://github.com/TanStack/query/issues/5671

so let's track it there


new ARES logo

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

[done] Filename in the lowercase format
[done] Image format: png
[done] Image size: 256 by 256 px

@arescoinofficial Please add the file


Add Request-specific "jsonTable"

Depends on #246
Once 246 is complete we should add a more granular support for the property bag JSON table that relational databases can use. There should be the root-level default table and then also request-specific tables.

Closed by #360


Error: Missing adapter implementation for 'abstractRuntimeString'

Hi! We would like to build an simple Shopify App in nuxt3. After installation and configuration, we call the shopifyApi function.  Then the error occurs. Some issue report says, that we import first "@shopify/shopify-api/adapters/node" but that didn't help either.

@shopify/shopify-api version: 6.2.0
Node version: 18.14.0
Operating system: MacOs Venture 13.2.1

[nitro] [dev] [uncaughtException] Error: Missing adapter implementation for 'abstractRuntimeString' - make sure to import the appropriate adapter for your platform
    at abstractRuntimeString (/Users/florianbottmann/Documents/workspace/shopify-donation/node_modules/@shopify/shopify-api/runtime/platform/runtime-string.js:6:11)
    at shopifyApi (/Users/florianbottmann/Documents/workspace/shopify-donation/node_modules/@shopify/shopify-api/lib/index.js:50:117)
    at file:///Users/florianbottmann/Documents/workspace/shopify-donation/.nuxt/dev/index.mjs:676:1
    at ModuleJob.run (node:internal/modules/esm/module_job:193:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:530:24)
    at async loadESM (node:internal/process/esm_loader:91:5)
    at async handleMainPromise (node:internal/modules/run_main:65:12)

Having this exact issue as well. Been scouring the Shopify docs to see if I missed anything to no avail.

Still getting this error with @shopify/shopify-api": "7.5.1
ReferenceError: process is not defined
    at nodeRuntimeString (.../node_modules/@shopify/shopify-api/adapters/node/adapter.ts:92:18)
    at shopifyApi2 (.../node_modules/@shopify/shopify-api/lib/index.ts:77:62)
    at Object.fetch (.../server.ts:70:23)
    at ServiceWorkerGlobalScope.[kDispatchFetch] (.../node_modules/@miniflare/core/src/standards/event.ts:385:13)
    at /.../node_modules/@shopify/mini-oxygen/dist/mini-oxygen/server.js:146:24

I want to confirm that it will work if you import the library as with an await inside a nitro plugin
export default defineNitroPlugin(async (nitroApp) => {
await import('@shopify/shopify-api/adapters/node')
})
This way, the adapter is registered and work for Nuxt server functions with Nitro

I want to confirm that it will work if you import the library as with an await inside a nitro plugin
export default defineNitroPlugin(async (nitroApp) => { await import('@shopify/shopify-api/adapters/node') })
This way, the adapter is registered and work for Nuxt server functions with Nitro

@BYohann
I'm doing it the exact same way in a Nitro plugin and still getting the same error => "Error: Missing adapter implementation for 'abstractRuntimeString'"
Is this way what you are currently using?
Thanks.

Create a middleware server like server/middleware/shopifyAdapters.js with:
export default defineEventHandler((event) => {
import("@shopify/shopify-api/adapters/node");
});

This worked for me

Thank you!


I steel can't to download discordptb

I steel can't to download discordptb

Hi @Kadisa13,
Why can't you download Discord.Discord.PTB? What error do you get? Could you share the logs when you try?
A package problem is more likely than a CLI problem here, since issues with other packages weren't reported, so might need to be moved to the winget-pkgs repo, but I can't be sure without more data.

@Kadisa13 I'm not able to reproduce the failure. Can you share logs for when this is happening? You can append "--verbose-logs --logs" to the end of the command to enable verbose logs and open the folder containing the log.


Error: Invalid parameter object: need either .data, .range or .url

Before i have tested the directive with the sample file and it was working fine.
I am trying now to make it working with my own files, both in localhost and on the server.
It isn't working. In both cases i am getting the following error:
Error: Invalid parameter object: need either .data, .range or .url

The only thing i have done is the following:  change the link from
$scope.pdfUrl = 'https://s3-us-west-2.amazonaws.com/s.cdpn.io/149125/relativity.pdf';
to
$scope.pdfUrl = base_url + 'data/drawer/' + $scope.file.data_id + '/' + $scope.file.filename;
if i open the path of  $scope.file_url in the browser it will properly display the pdf file, both in locahost and online.
Why am i getting the error?
What am i doing wrong?
Thank you very much!

Can you post more of your code. Where do you have this expression – in a controller, directive, etc.? Is the file object loaded asynchronously?
How are you passing pdfUrl it to the directive? Can you add a your template too.
Also, can you try logging the pdfUrl inside pdf-ctrl.js
It seems like an issue where you are not passing the url correctly or it's not ready yet.
Thanks

Thanks @winkerVSbecks  for your time!
I am close to resolve this last thing and be able to use your very useful directive.
The file object is loaded asynchronously with a function initialize in the view through ng-init.
This is the function in the controller (the file path is currently hardcoded).
And in this way is not working.
This is the function in the controller:
$scope.get_file_detail = function()
{
var info_file = FileService.file_detail_get( $stateParams.file_id );
info_file.then( function( data ) {
		$scope.file = data;
	        $scope.file_url = base_url + 'data/locahost/drawer/' + $scope.file.data_id + '/' + $scope.file.filename;

	});

}

But if i hardcode the path directly into the controller then it is properly working:
$scope.file_url = 'http://localhost/sakura2/data/locahost/drawer/69/c649c4c8b5049486e66b0a52d01b00b1.PDF';
But i need to load the according to the id of the container and the file name.
Do you have any suggestion?
Thank you very much!
Definitely deserve a star

I have make a question on SO about this:
http://stackoverflow.com/questions/29005509/angular-ng-init-function-loaded-after-directive

@FrancescoMussi so, here's the issue. When the view loads $scope.file_url is null. The directive picks this up and since there is not binding it never gets the updated value.
$scope.get_file_detail runs later and updates the $scope.file_url value but, it's too late.
To get around this issue, wrap the directive in an ng-if. This way the directive will only load once the file_url is specified:
<div ng-if="file_url">
  <pdf-viewer
      delegate-handle="my-pdf-container"
      url="file_url"
      scale="1"
      show-toolbar="false">
</div>

Thank you very much for your help!
Now everything is working perfectly!


Rename from webrtc-rs-rtcp to rtcp

Rename library on cargo from webrtc-rs-rtcp to rtcp as name has not been taken https://crates.io/search?q=rtcp

I still prefer webrtc-rs-rtcp to rtcp, in order to keep consistent naming as other libraries.
you can do like this:
[dependencies]
util = { package = "webrtc-rs-util", version = "0.1.0" }
rtp = { package = "webrtc-rs-rtp", version = "0.1.0" }
rtcp = { package = "webrtc-rs-rtcp", version = "0.1.0" }


Main

Issue number #25
This pull request introduces an Automated Portfolio Management Tool to the NexTrade platform, allowing users to track, rebalance, and manage their investments more effectively. The key features include:
Portfolio Tracking: Users can monitor their stock holdings, current market value, and portfolio performance in real-time
.
Automated Rebalancing: Automatically rebalance the portfolio based on predefined criteria (risk tolerance, asset allocation)
.
Market Insights and Alerts: Get real-time insights and alerts for significant market changes.
Risk Assessment: Evaluate the risk level of the portfolio and suggest strategies to mitigate risk.
Educational Resources: Access resources and tutorials on portfolio management strategies.
Instructions to Run the Program-

Install Dependencies: Ensure you have Python 3.x, Flask, and Web3.py installed. Run command-
pip install Flask web3

2.Smart Contract Setup:
Compile and deploy the PortfolioManager.sol smart contract using Remix or Truffle.
Copy the contract ABI and address into app/web3_interface.py for interaction with Ethereum.

Configure Ethereum Provider: Set up your Ethereum provider in web3_interface.py. For Ganache, you can use:
w3=Web3(Web3.HTTPProvider('http://<IP_ADDRESS>:7545'))

For Infura, provide your API key:
w3=Web3(Web3.HTTPProvider('https://mainnet.infura.io/v3/YOUR_INFURA_PROJECT_ID'))

Connect MetaMask: Make sure MetaMask is set up and connected to the same network (Ganache/testnet/mainnet).

Run the Flask Application: Start the Flask server:
python app.py

I know you're already familiar with many of these instructions, but I wanted to ensure everything is clearly outlined so you can run the program smoothly. Let me know if you run into any issues or if any further adjustments are needed. Thankyou.

@Akshat111111 kindly have a look on this pr once.


Warning message in console

Hey! I use your package frequently because it's really cool 😎 🙌.
I have a warning message in my console concerning the _metamask method using in the MetaMaskProvider (l.25)
const isUnlocked = await ethereum._metamask.isUnlocked();

it is specified in the metamask doc that it is experimental:
https://docs.metamask.io/guide/ethereum-provider.html#experimental-api

Hey! Thanks a lot for the kind words and the issue! I'm happy to see that this package is useful to people 😁
This is indeed a bit of a problem, I will dig a bit if I may find a stable replacement, I have not for now :(
PS: I'm trying to generalize a bit the approach of this package with other wallets in https://github.com/VGLoic/ethpp. Don't hesitate to take a look if you want :)

Thank you for the answer. I have been looking for an alternative to "isUnlocked" method but I think it requires the use of web3 or ethers.js. It's not a big deal because it works very well 😜.

By taking a look at the code today, there is actually no need for this call to isUnlocked, I thought there was a locked status in order to justify this step but it does not exist 🤦 , and I don't think we should add it 🤔
So basically, I will just remove it 😅 and the warning should disappear at the same time 😁


Where is the setup.py

I was curious: how do you deploy data on pypi? I could not find the setup.py script, is it in another repository?

I'm keeping a separate folder on my computer for the upload to PyPi, wasn't aware this would be useful for sharing. I have Included the setup.py file now in this repo

Normal structure is to put the source code into src/loanpy/. If you check the structure we have in lingpy, you can just copy that. Or in pysem. It is recommendable, I think, as it is more transparent. Every (?) Python package maker will first look for a src directory in your main repository.

Now the structure should be fine I think

Yes, you can even move tests to the base level.

Yeah, I was thinking about this. Have implemented it now.

Nice.


Limit frequency of PQA API healthcheck

only carry out PQA API health check once every 15 mins (configurable)
fix bug in Healthcheck service
write tests for Healtcheck service and controller

@stephenrichards build failed. Please fix :)


Unify error logging

Internal refactoring to make all error logging go through an error logger. The default error logger logs to STDERR, but a custom error logger can be provided by passing a new error_logger option or by changing LogStashLogger.configuration.default_error_logger.

[Current coverage][cc-pull] is 89.91%

Merging [#82][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.23%

@@             master        #82   diff @@
==========================================
  Files            55         55
  Lines          1229       1240    +11
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           1108       1115     +7
- Misses          121        125     +4
  Partials          0          0

Powered by Codecov. Last updated by [fb86f42...0765f81][cc-compare]
[cc-base-branch]: https://codecov.io/gh/dwbutler/logstash-logger/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/dwbutler/logstash-logger/compare/fb86f4279c29beb8860e77332b317a695a1dde83...0765f81512bb0180532eabd3cc9d8ad9372b36fc?src=pr
[cc-pull]: https://codecov.io/gh/dwbutler/logstash-logger/pull/82?src=pr

Released in 0.16.0.


Invite members

Looks good, here's my suggestions:
• Should I be allowed to remove myself?
• On the send invite page, change the button label to say "Share Invite"
• On the members list table, instead of a blue edit link, I'd use our table buttons instead. Pattern match off the databases Scale button on the databases list table
• Q) Do we wanna add in the download members list functionality in this PR?
• I think we can move the Special search terms: verified and mfa. The inverse is also available: !verified and !mfa into the top Members page tooltip and say: Search members by name or status by typing verified, mfa, !verified, or !mfa


--ui attempts to load .vue files unrelated to test

Describe the bug
Attempting to open the use the UI with --ui causes Vitest to load .vue files unrelated to the tests (from the docs in particular).
The following errors are printed:
error: No loader is configured for ".vue" files: demo/components/App.vue

[
    {
      detail: undefined,
      location: {
        column: 16,
        file: 'demo/main.ts',
        length: 25,
        line: 1,
        lineText: "import App from 'demo/components/App.vue'",
        namespace: '',
        suggestion: ''
      },
      notes: [],
      pluginName: '',
      text: 'No loader is configured for ".vue" files: demo/components/App.vue'
    }
],

demo/main.ts is not referenced in the source code or any test.
Reproduction
Repository with reproduction: https://github.com/DerYeger/d3-graph-controller
Can be reproduced by running the test with yarn test:watch --ui.
System Info
System:
    OS: Windows 10 10.0.22000
    CPU: (24) x64 AMD Ryzen 9 3900X 12-Core Processor
    Memory: 16.04 GB / 31.92 GB
  Binaries:
    Node: 16.13.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.15 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 7.20.3 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22000.120.0), Chromium (96.0.1054.62)
    Internet Explorer: 11.0.22000.120
  npmPackages:
    @vitejs/plugin-vue: 2.0.1 => 2.0.1
    vite: 2.7.10 => 2.7.10
    vitest: 0.0.139 => 0.0.139

Used Package Manager
yarn
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Hi, is that issue still a problem?

Yes. Running yarn test:watch --ui in the repository linked above results in the same error.
I tried it with v0.2.3 without success.

Ok, I'll try to see what is going wrong.

Is it still happening?

Is it still happening?

Yes, just tested it with v0.4.2.

It's seemingly related to the file naming.
After renaming demo/main.ts the error no longer occurs.
However, the UI still doesn't work. I also renamed src/main.ts, but that didn't help.
There's no error, but the UI does open either.

I just noticed the v0.5.0 release.
After updating to that version, I do get the message that the UI was started, but the UI still is a 404.

So, this happens because:
By default, Vite will crawl all your .html files to detect dependencies that need to be pre-bundled (ignoring node_modules, build.outDir, tests and coverage). If build.rollupOptions.input is specified, Vite will crawl those entry points instead.

https://vitejs.dev/config/#optimizedeps-entries

We had it disabled, but removed some time ago - #641 🤔

We had it disabled, but removed some time ago - #641 🤔

Turns out optimizeDeps: undefined doesn't disable optimization, I guess thats why this patch was made. But optimizeDeps: { entries: [] } does disable it, opened a PR #1104


FindDefinitions commit for DragDropManager

pull request for this fix
https://github.com/brimdata/react-arborist/pull/129

@jameskerr Changed the prop name, thank you!