Print config error warning on startup

This change adds an error message at the bottom of the screen which will
be displayed when the config file contains any errors.
Currently deprecation warnings are unchanged but it would be possible to
add these too (maybe in yellow?) if it is desired.
The method for rendering text has been changed to always render at the
bottom of the terminal, this seems like a more reliable way of doing
this and it shouldn't cause any issues because under normal use, nothing
should be displayed.
I'd say this is still a bit rough around the edges so feedback is
welcome, maybe some things could be streamlined?
Currently if the terminal is not wide enough, nothing will be displayed,
maybe we should display the message but cut off? Not sure how important
this is because it would probably be fine to not display anything in
small terminals.
All errors are written to /tmp/alacritty.log, nothing is written to
stderr anymore, we could do both but I think it should not be necessary
to write anything to stderr anymore.
This fixes #1143.

What is the reason for not printing to stderr? That would be the first place i would look if something was wrong with Alacritty

It would be a simple fix to print both to stderr and a log file, however when starting alacritty you usually don't have access to stderr (without having to attach to the process).
So unless you start alacritty from another instance of alacritty, you will not be able to see the errors. Having a log file will allow you to always see the errors even when alacritty doesn't launch anymore and you don't have another terminal for checking the stderr.

Yeah but I wouldn't go look for a log file in /tmp. First I would run alacrity with another terminal and look at stderr. Then i would look for a .alacritty-log (like how the xserver does) in my home folder.

Have you tested this PR? It will show an error message to the user which states that errors have been written to /tmp/alacritty.log, so I think it should be fine.
I really don't like the idea of writing error logs in the home folder because it might create unnecessary files that could clutter the home directory of a user even long after alacritty is removed.

No I didn't test this PR. I think it is great that you will print the error in the Alacritty window. But, what if Alacritty exits for some reason. Will you still see the message that there is a logfile somewhere? Maybe you can print where the logfile is to stderr. I do still think that printing to stderr should be the default, what if /tmp isn't writeable, is there a fallback to stderr?

I'm now writing the errors to both the log file and stderr. However alacritty should never instantly crash when config errors are present, so when such an error appears it will never be logged but rather cause a panic that is untracked.

Ok! I misunderstood and thought this PR was all errors. If it is only config errors that are logged to file I don't have that strong opinion. But I still think it is good to be consistent and log everything to the same place. Which I guess is stderr in this case.

It would also be nice to use the printing facility that is implemented in this PR to print for example the new font size when pressing ctrl +/-.

I'm actually not a huge fan of the current shape of this PR, I think it's a bit awkward and doesn't really allow any other event to hook into the file logging and error/warning printing.
I think logging things like the font size change would be a great idea, at least if the required logging verbosity is specified.

I've decided to reimplement the complete PR rather than trying to resolve some remaining issues I've had with it.
I think the way this works should be a lot better now. There's no more globals being accessed across the complete codebase and generally things have been simplified a lot.
All warn! and error! logs are now printed to a log file and stdout by default. If any error or warning is created, it is displayed in the UI with a notice about the location of the log file. This allowed removing all calls to print!, eprint!, println! and eprintln!.
There were two slight complications with getting rid of printing to the command line directly. The --print-events flag has been changed so it will automatically set the log level to info (like -v). Then all messages are just printed using info!. It's still checked that --print-events is present though, so the events are not always printed when the info level is set.
The other problem was with warnings about escape sequences which are currently still emitted on a regular basis. This would cause a ton of warnings for most users. Since there has been some confusion about these messages anyways, the log level has been reduced to debug. This might make debugging harder in some cases, but I think it's a good solution now that Alacritty has support for most basic escapes.

It seems to me that env::temp_dir() is the global temporary folder and not the users temporary folder. Does this mean that the second user opening alacritty can't log to file? I would prefer that we use a user-local log directory such as $XDG_CACHE_HOME or $XDG_DATA_HOME.
I'm sure this will not be a very common problem, but I've had problems with running software using sudo and then not being able to start the software as my own user because the logfile now was owned by uid 0.

Another idea is to add the process id to the logfilename and keep storing it in the global tmp.

@NickeZ Those are some good points. Right now the global log file is used by all Alacritty instances. That means that all write to it at the same time, it's not locked to one specific process.
I've actually put it onto my todo list to test what happens when the user isn't allowed to write to the file, it should just prevent file logging from working, but I haven't tested that yet.
I've thought about multiple different ways to create logfiles with some kind of hash/time/id in the name, but I decided to go with a global log file for now. I think using the PID of Alacritty is probably the best of the choices I've evaluated, so I think using that would be fine. Note though that with 13 open Alacritty windows, this will spawn 13 files if you change your config and there's an error. This could also override previous files without restart because a PID can be reassigned, but I'd say that's irrelevant.
I think putting it in the user home directory is a bigger problem. There is no standard temporary user directory which gets automatically cleared, so Alacritty runs the risk of just dumping a ton of log files which will never be read or deleted. I think /tmp is a great place for discoverability and adding a PID should help with access problems, however it would still be possible to run into an issue if the PID is reused.
An alternative for a global temp directory would be a user-based temporary directory provided by systemd. It's located at /run/user/$UID and is automatically cleared at startup. However this will cause problems with Windows, macOS, BSD and every Linux distro not running systemd. Unless you have a good solution for that, I think using env::temp_dir is our best bet for making things work everywhere.

Ok, sounds like you thought about it. Another thing that is not immediately obvious to me after reading the code. Will it always log to file or only when -v is given?

@NickeZ Warnings and Errors are always logged to the file. Other stuff is only logged when -v(vv) is present.

The proposal from @NickeZ has now been incorporated into the latest commit.
I still need to do another full code review to make sure the code quality is okay, but I think the functionality should be pretty much there now. If there's any remaining problems or ideas for improvements, please let me know.

Instead of always keeping all logfiles, I've made the decision to delete logs by default once Alacritty is closed. If the CLI parameter --persistent-logging or the configuration option persistent_logging are set, the log file will not be deleted after closing Alacritty.
As always, feedback would be appreciated. I don't think there's any further issues I have with this PR, but I'm unsure if the additional configuration option plus CLI flag are absolutely necessary.


Modules are not getting loaded

I ran 'Install-Module -Name Microsoft.Online.SharePoint.PowerShell' command and successfully installed "Microsoft.Online.SharePoint.PowerShell" module. When I ran "Get-Module -Name Microsoft.Online.SharePoint.PowerShell -ListAvailable | Select Name,Version" command I can see the module is available and gives me below result.
Name                                   Version

Microsoft.Online.SharePoint.PowerShell 16.0.8924.1200
But when I try to execute "Connect-SPOService" command got below error
Connect-SPOService : The term 'Connect-SPOService' is not recognized as the name of a cmdlet, function, script file,
or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and
try again.
At line:1 char:1

Connect-SPOService

  + CategoryInfo          : ObjectNotFound: (Connect-SPOService:String) [], CommandNotFoundException
  + FullyQualifiedErrorId : CommandNotFoundException

When I try to load the module manually with 'Import-Module Microsoft.Online.SharePoint.PowerShell' command got below error
Import-Module : Could not load type 'Microsoft.SharePoint.Administration.DesignPackageType' from assembly
'Microsoft.SharePoint.Client, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=71e9bce111e9429c'.
At line:1 char:1

Import-Module Microsoft.Online.SharePoint.PowerShell

  + CategoryInfo          : NotSpecified: (:) [Import-Module], TypeLoadException
  + FullyQualifiedErrorId : System.TypeLoadException,Microsoft.PowerShell.Commands.ImportModuleCommand

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

ID: 05b23d72-33ed-a6a1-a442-a5e5cf039f9f
Version Independent ID: 4247cf37-3667-2007-7251-46ed80f58ef5
Content: Getting started with SharePoint Online Management Shell
Content Source: sharepoint/docs-conceptual/sharepoint-online/connect-sharepoint-online.md
GitHub Login: @Techwriter40
Microsoft Alias: kirks

@officedocsbot assign @yogkumgit

Hello @ravick4u
Thanks for your feedback.
I followed the steps in the article and it works

Also, Connect-SPOService is recognized without needing to import-module (but you could also run it)
As the documentation works I do not see that it needs to be modified, as this issue resource is specifically to address issues in documentation, I kindly suggest you to either remove the module and reinstall, or contact support at https://support.microsoft.com
Thank you

@get-itips Thank you very much for the contribution and sharing this explanation. @ravick4u
Hope this comment is helpful for you. Considering the nature of the issue, as advised that please open a service ticket in your tenant and follow with them for the resolution.
We will be very happy if you can share the outcome or resolution with us. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also

@officedocsbot close

This isn't resolved. I've uninstalled and re-installed the module and still it cannot find the cmdlet Connect-SPOService.

This is the error when trying to Import-Module (which I understand isn't required, but might explain why the Connect cmdlet is missing)
System.TypeLoadException: Could not load type
'Microsoft.SharePoint.Administration.DesignPackageType' from assembly
'Microsoft.SharePoint.Client, Version=<IP_ADDRESS>, Culture=neutral,
PublicKeyToken=71e9bce111e9429c'.
at System.Reflection.RuntimeAssembly.GetExportedTypes(RuntimeAssembly assembly,
ObjectHandleOnStack retTypes)
at System.Reflection.RuntimeAssembly.GetExportedTypes()
at System.Management.Automation.Runspaces.PSSnapInHelpers.GetAssemblyTypes(Assembly
assembly, String name)
at System.Management.Automation.Runspaces.PSSnapInHelpers.AnalyzeModuleAssemblyWithReflectio
n(Assembly assembly, String name, PSSnapInInfo psSnapInInfo, PSModuleInfo moduleInfo, Boolean                                                                                isModuleLoad, Dictionary2& cmdlets, Dictionary2& aliases, Dictionary2& providers, String                                                                                helpFile, Type& randomCmdletToCheckLinkDemand, Type& randomProviderToCheckLinkDemand)                            at System.Management.Automation.Runspaces.PSSnapInHelpers.AnalyzePSSnapInAssembly(Assembly                                                                                assembly, String name, PSSnapInInfo psSnapInInfo, PSModuleInfo moduleInfo, Boolean                         isModuleLoad, Dictionary2& cmdlets, Dictionary2& aliases, Dictionary2& providers, String&                                                                                helpFile)
at
System.Management.Automation.Runspaces.InitialSessionState.ImportCmdletsFromAssembly(Assembly                                                                                assembly, PSModuleInfo module)
at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadBinaryModule(PSModuleInfo
parentModule, Boolean trySnapInName, String moduleName, String fileName, Assembly
assemblyToLoad, String moduleBase, SessionState ss, ImportModuleOptions options,
ManifestProcessingFlags manifestProcessingFlags, String prefix, Boolean loadTypes, Boolean                                                                                loadFormats, Boolean& found, String shortModuleName, Boolean disableFormatUpdates)
at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModule(PSModuleInfo parentModule,                                                                                String fileName, String moduleBase, String prefix, SessionState ss, Object privateData,
ImportModuleOptions& options, ManifestProcessingFlags manifestProcessingFlags, Boolean& found,                                                                                Boolean& moduleFileFound)
at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModuleNamedInManifest(PSModuleInfo                                                                                parentModule, ModuleSpecification moduleSpecification, String moduleBase, Boolean
searchModulePath, String prefix, SessionState ss, ImportModuleOptions options,
ManifestProcessingFlags manifestProcessingFlags, Boolean loadTypesFiles, Boolean
loadFormatFiles, Object privateData, Boolean& found, String shortModuleName, Nullable1                         manifestLanguageMode)                            at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModuleManifest(String                         moduleManifestPath, ExternalScriptInfo manifestScriptInfo, Hashtable data, Hashtable                         localizedData, ManifestProcessingFlags manifestProcessingFlags, Version minimumVersion,                         Version maximumVersion, Version requiredVersion, Nullable1 requiredModuleGuid,
ImportModuleOptions& options, Boolean& containedErrors)                                                                                at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModule(PSModuleInfo parentModule,                                                                                String fileName, String moduleBase, String prefix, SessionState ss, Object privateData,                                                                                ImportModuleOptions& options, ManifestProcessingFlags manifestProcessingFlags, Boolean& found,                                                                                Boolean& moduleFileFound)                                                                                at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadUsingExtensions(PSModuleInfo                                                                                parentModule, String moduleName, String fileBaseName, String extension, String moduleBase,                                                                                String prefix, SessionState ss, ImportModuleOptions options, ManifestProcessingFlags                                                                                manifestProcessingFlags, Boolean& found, Boolean& moduleFileFound)                                                                                at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadUsingMultiVersionModuleBase(String                                                                                moduleBase, ImportModuleOptions importModuleOptions, Boolean& found)                                                                                at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadUsingModulePath(PSModuleInfo                                                                                parentModule, Boolean found, IEnumerable`1 modulePath, String name, SessionState ss,                                                                                ImportModuleOptions options, ManifestProcessingFlags manifestProcessingFlags, PSModuleInfo&                                                                                module)                                                                                at Microsoft.PowerShell.Commands.ImportModuleCommand.ImportModule_LocallyViaName(ImportModul                                                                                eOptions importModuleOptions, String name)                                                                                at Microsoft.PowerShell.Commands.ImportModuleCommand.ProcessRecord()                                                                                at System.Management.Automation.CommandProcessor.ProcessRecord()

@get-itips This is actually a documentation issue. The Microsoft.Online.SharePoint.Module will not load in PowerShell if SharePoint Client Components are installed. The documentation describing how to install this module must identify this incompatibility, because this is the root cause of the error reported above.

@get-itips This is actually a documentation issue. The Microsoft.Online.SharePoint.Module will not load in PowerShell if SharePoint Client Components are installed. The documentation describing how to install this module must identify this incompatibility, because this is the root cause of the error reported above.

Hello @KirkMunro Kirk, how are you? 👍 Thanks for your feedback.
I installed the SharePoint Client Components on my lab and I can import, connect and run cmdlets of the Microsoft.Online.SharePoint.Module without issues


[question] Revert stack?

Is it possible to revert stack?
Like, the stack will be full and you just scroll down to see the next card? (in this case: 10, 9, 8...)

There is currently no such method. Mainly because the use case it was modeled after always starts with the showing first card.

ok. thanks for your quick answer :D


Fix the link to Gerrit Code Review in doc/realworld.html

The code.google.com link is deprecated. Also add that CodeMirror
is being used as Gerrit's inline editor.

Thank you. Merged as fa705ea


TensorFlowLite: failed to load native library: no tensorflowlite_jni in java.library.path

TensorFlowLite: failed to load native library: no tensorflowlite_jni in java.library.path

@majiali1995 Have you solved that problem? I met this in the unit test.


Makes possible to interpret comma as decimal point in editor

Fixes issue #6028 and #6104
After some tests, looks like everything works smoothly.
This is how it looks in action: https://i.imgur.com/j8FUoBp.gifv

@akien-mga thought about it initially, but was kinda scary to broke something up by modifying such common function.
Anyway, done, check.


"unreachable"

https://squoosh.app/
Open "device screen" image.
Activate resize.
Reduce size by 1px (many other values produce the same effect)
Error "mozjpeg unreachable".

This happens with other codecs too.

This was introduced in 68177b7590b08427868f077f4e12656e6d62894e

cc @RReverser - I'm digging into this, but since it's part of the Rust/wasm stuff it might be beyond me

Ok, the issue is in the "Linear RGB" codepath. If that's disabled, it'll work fine.

Bug reports of this (https://github.com/GoogleChromeLabs/squoosh/issues/711) mention that it only happens when importing PNG images, which suggests to me that it's caused by alpha values other than 255.

I'm no longer sure the bug was introduced by 68177b7, but that's when the wasm was built after the breakage.

The bug appears to be in |v| (LINEAR_TO_SRGB_LUT[v as usize] * 255.0) as u8

Oh, ok, the bug only happens with both Premultiply and Linear RGB, so the issue is that |v, a| (v as f32) * 255.0 / (a as f32).clamp(0.0, 255.0) is generating something that |v, a| (v * (a as f32) / 255.0) as u8 cannot handle. And the problem is when alpha is 0.

I'm still seeing this error on Android when I try to resize images taken with the camera.

@JNavas2 unreachable is a generic Wasm failure might have a lot of potential causes. It's best if you open a new issue with specific repro steps.

New Issue #988


Regression in integration tests by modified credential handling errors

What happened:
Integration Tests are failing after commit: 0362e29d97c5dfc5c21fbc3a06cd876535150988
Likely caused by: https://github.com/open-component-model/ocm/pull/611
Before this commit error message if credentials are missing from ocm was: '401 Unauthorized`
After this commit it was changed to: 'unable to add blob (OCI repository images/pause): failed to push: authorization failed: no basic auth credentials\n'
What you expected to happen:
I prefer the old message as it reflects the http status code and is much better scriptable.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:
I added a PR to to ocm-integrationtest. Depending on whether you want to fix this in the CLI or in the integration-test either merghe or close this PR
Environment:

As this problem was introduced by an update of a used library (ocm CLI does not control the error message) it was fixed in the test.


Directory: added BootstrapWithGuard method

Added BootstrapWithGuard method that allows
reusing existing TorGuard instance, instead of
creating and discarding it like in Bootstrap method

If it passes the CI, LGTM.

If it passes the CI, LGTM.

Use the GitHub UI to approve.

Added BootstrapWithGuard method that allows
reusing existing TorGuard instance, instead of
creating and discarding it like in Bootstrap method

And why is this? Reply here, don't change commit message (I'll change it for you to include the answer to this question, plus adding a final dot because the body of the commit message is composed of paragraphs).

And why is this?

I mean and why is a method that allows reusing existing TorGuard instance needed?

And why is this?
This is done so that in GWallet we can use the guard that we just created for timing for the rest of bootstraping. And get consistent time measurements.


Invisible special characters appended to sanity object strings

Version
module: 1.8.3
nuxt: 3.11.2
Nuxt configuration
export default defineNuxtConfig({
devtools: { enabled: true },
modules: ["@nuxtjs/sanity"],
sanity: {
projectId: process.env.NUXT_SANITY_PROJECT_ID,
dataset: process.env.NUXT_SANITY_DATASET,
useCdn: true, // false if you want to ensure fresh data
apiVersion: process.env.NUXT_SANITY_API_VERSION || '2024-03-15',
visualEditing: {
studioUrl: process.env.NUXT_SANITY_STUDIO_URL || 'http://localhost:3333',
token: process.env.NUXT_SANITY_API_READ_TOKEN,
stega: true,
},
},
})
Reproduction
Make a query to a text or string field in sanity.
Link:
[ ] https://stackblitz.com/edit/nuxt-sanity
[x] GitHub repository
https://github.com/FancyJeff/test-sanity-nuxt
What is expected?
Getting a basic string
What is actually happening?
A huge number of special characters is being appended to the end of the string
Additional information
This does not occur on package version 1.8.3, I tested it as early as 1.10.0 and it still was occurring.
I have created an empty package with no other packages and used the latest versions of everything and its still occurring.
Checklist

[x]  I have tested with the latest Nuxt version and the issue still occurs
[x]  I have tested with the latest module version and the issue still occurs
[x]  I have searched the issue tracker and this issue hasn't been reported yet

What is actually happening?
Screen shot of the chrome dev tools

These special characters are added by Sanity when using visual editing mode.  They allow Sanity to work out where it needs to go withing Sanity studio when clicking on the content. You can read more about is here.
If you need to remove these characters from the string you can import stegaClean from @sanity/client/stega.

I think there is a problem here though. It looks like the stega encoding is enabled all the time when using this module and having visual editing configured. But as far as I understand, stega and anything visual editing-related are only supposed to be enabled when preview mode is enabled? Tried to find more clear answers in the Sanity docs and they ever only mention stega in relation to preview mode.
Sorry for pinging @danielroe

Yea, if we could expose the sanityClient stega config, we would be able to turn it on/off globally

Thanks @jesperbjerke, I think that assumption is correct. I've added a fix in #1023.

@rdunk This is still happening for me, even when the /preview/enable route has not been hit, and I'm not in preview mode.

@notflip: 1.11.4 doesn't include the fix, but @danielroe has kindly released a new version (1.11.5) that does.

@rdunk I just saw it! Thanks a lot. Is the stegaclean method still needed for some cases then? I suppose only to clean the input when effectively using the preview mode?

Yes exactly, it's still useful for all sorts of things, like str length comparisons.
Going to close this one now, thanks for the report. Please reopen if the issue persists.

@rdunk One more question, because I'm using a lot of comparisons in my Vue code (for example block.imagePosition, block.verticalAlign), what if I set stega: false, which features will not work then? Does this break the live editing?

If you'd prefer not to use stega you can manually map content/create overlays using  createDataAttribute and encodeDataAttribute. Docs here.

@rdunk Thanks for this, is there an example when using nuxt/sanity? For example the docs of encodeDataAttribute show
import { QueryResponseInitial, useQuery } from "@sanity/react-loader";

Do we have an example of how to use this with nuxt in general, or nuxt/sanity?

@rdunk Thanks for this, do you know the nuxt/sanity equivalent to import { createDataAttribute } from "@sanity/visual-editing"?

@notflip Good point. I've added that as a separate issue and created a PR to add an auto-import for it.


gobject-introspection-native-1.54.1-r0 failure when trying to build resin-odroid

I'm trying to build the resin-odroid image as per the instructions on the git page, but I'm running into the following issue:
| checking for backtrace_symbols... yes
| /usr/bin/env: 'node': No such file or directory
| configure: error: Python interpreter /home/mclark/Code/Yocto/ResinOS/resin-odroid/build/tmp/work/x86_64-linux/gobject-introspection-native/1.54.1-r0/recipe-sysroot-native/usr/bin/python3-native/python3 does not exist
| NOTE: The following config.log files may provide further information.
| NOTE: /home/mclark/Code/Yocto/ResinOS/resin-odroid/build/tmp/work/x86_64-linux/gobject-introspection-native/1.54.1-r0/build/config.log
| ERROR: configure failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_configure (log file is located at /home/mclark/Code/Yocto/ResinOS/resin-odroid/build/tmp/work/x86_64-linux/gobject-introspection-native/1.54.1-r0/temp/log.do_configure.2100)
ERROR: Task (virtual:native:/home/mclark/Code/Yocto/ResinOS/resin-odroid/build/../layers/poky/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.54.1.bb:do_configure) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1133 tasks of which 1084 didn't need to be rerun and 1 failed.

This error also appears if I try to bitbake the meta-toolchain.
I've got node installed on the host system itself, and have gone so far as to bitbake nodejs and nodejs-native, but it's still stumbling over this complaint about node.  Can anyone explain what's happening?
Thanks,
Matt

Apparently tmp/work/hosttools had glommed onto a bad "which" based out of NVM instead of using /usr/bin/which.


feat: expo app

:tada: This PR is included in version 1.14.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Does the directory structure affect the discovery of Java Projects？

I found that if I had a Java Project in my subdirectory, VS Code couldn't find it。

It's by design because currently the Java extension will only be activated if your project root contains Java build files: https://github.com/redhat-developer/vscode-java/blob/master/package.json#L31-L33
Will you see your project if you open a Java file contained by your project?


'Fix' macOS build errors, explicit tuple members (Swift 4), TestXDG folder cleanup

'Fix' macOS build errors with swift compiler option -swift-version 3. Xcode seems to have a SWIFT_VERSION setting, but it doesn't have the same effect! Changes should be like those in https://github.com/apple/swift-corelibs-foundation/pull/956.
Quiet some warnings with -Wno-nullability-completeness-on-arrays and -Wno-format-security for CoreFoundation - please review if GCC_WARN_TYPECHECK_CALLS_TO_PRINTF Xcode setting has the same effect/is better than -Wno-format-security
Has mangling changed on Mac? I've have had issues with comparing CF/NS strings, and not sure if it /was just/ a mangling issue, but got warning and error with macOS build, so updating __CFSwiftGetBaseClass and __CFConstantStringClassReference.
@slavapestov  or @eeckstein - is there a way for a script to determine a mangled class/function name at build time?
The warning/error reported on macOS:

ld: warning: undefined base symbol '__TMC15SwiftFoundation19_NSCFConstantString' for alias '___CFConstantStringClassReference'
Undefined symbols for architecture x86_64:
  "__T015SwiftFoundation21__CFSwiftGetBaseClassyXlXpyF", referenced from:
      ___CFInitialize in libCoreFoundation.a(CFRuntime.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Refactored XDG helper, and created target in Xcode so tests pass on Mac (well 2 failures still in NSString):

TestNSString.test_FromContentsOfURLUsedEncodingUTF16BE : failed - URL for NSString-UTF16-BE-data.txt is nil
TestNSString.test_FromContentsOfURLUsedEncodingUTF16LE : failed - URL for NSString-UTF16-LE-data.txt is nil

Target depends on SwiftFoundation being at same level in build directory (added rpath in lieu of framework copy phase). Perhaps copy can be disabled for TestFoundation too?
@mamabusi Are these changes okay with you?
I am thinking, perhaps, xdgTestHelper can be renamed testHelper or similar and used for any other 'checks' needing another process in the future.

This fixed my recent macOS build failures. Thanks.

@e78l XDG Test executable changes look good to me. I second your opinion of renaming xdgTestHelper to a more generic name if it helps other tests needing another process.

I would really like to split up these fixes into a few different PRs; especially stuff about build settings vs warning fixes in CF.

Hello @parkera,
Thanks for the review - I split some changes that were easy to do into #1006 and can split further+undo warnings silence if decided (would be a bit time consuming).
Removed Swift 4 changes which I think were covered by @spevans. After those changes, may be able to forget about -swift-version 3; in that case, may also want to update build.py.
@mamabusi Thanks also!

@swift-ci test

For some reason status isn't being updated here after request (cc @shahmishal @erg) but the PR is testing here: https://ci.swift.org/job/swift-corelibs-foundation-PR-Linux/872/

Looks like it passed. Thanks!


TEST: include missing busco test files

test_busco_feature_data.py::TestBUSCOFeatureData::test_evaluate_busco_action and test_busco_sample_data.py::TestBUSCOSampleData::test_evaluate_busco_action failing because test data is missing. This PR includes such data by specifying it in the setup.py.

@misialq I made a fresh clone locally, checkout out the PR branch, and ran the tests. It seems all is good now.

Hey @Sann5, I don't think it works - this is not something you can easily test locally - see the failing Q2 CI run. When you want to test it again after your new pushes you can just invoke the Q2 CI by commenting /q2ci here.

Hey @Sann5, I don't think it works - this is not something you can easily test locally - see the failing Q2 CI run. When you want to test it again after your new pushes you can just invoke the Q2 CI by commenting /q2ci here. Edit: Running QIIME 2 CI...

The error in the Q2 CI is about the Python version no? Not the Busco tests. This is not the same error. But you are right I thought that these files would not be included in my fresh clone but I think they are.

I think you're looking at the wrong action output (our CI fails with Python version not the Q2 one). See here: https://github.com/bokulich-lab/q2-moshpit/actions/runs/9599409582/job/26473075711 (that's the one from my previous run)

/q2ci

So I found out that placeholders (*) only work with files, not directories. I find this weird becasue we have been using these placeholders for folders in other modules and all seems fine. Maybe it breaks here because there are instances of a folder with nothing but another folder inside (busco/busco_downloads and lineages/lineage_1). So I modified the setup.py to explicitly include these folders but I keep getting the error.
@misialq could it be that the CI is not running on the right commit? It's weird that I keep getting the error even though I explicitly include these files in the setup.py. Besides, look at the commit referenced in the action. It is the commit from the last PR.

Oh yeah, it certainly looks this way... Another thing to fix 🙄 I guess it looks good otherwise so let's merge this and 🤞


[1.10.2] Digital Miner not visible by all players

Here's the steps to reproduce
2 Players in 1 area.
Player A - place the digital miner. Player B - cannot see the digital miner
Player B - place the digital miner. Player A - cannot see the digital miner
A quit/rejoin OR place another block in the effect area (where the digital miner is) will show the digital miner for both players.
Also, when breaking digital miner, players do not always see the ground item it produces. The 2 seem related, but if not, I can open a separate issue.

that sounds like a client sync issue but i could be wrong.

Yeah, sounds like a client sync issue.  Did some testing and was unable to reproduce.


Allow setting default values for exposure

This will allow setting a default value for exposure.
The change is motivated because on a dry-web-roda project I'm working I have to pass errors to a form view to display them, but if I do not have errors I'm forced to pass them as an empty array from my routes.
r.get 'new' do
  r.view 'tils.new', errors: []
end

So having the ability to set default values in our views objects make it simplier.
module Tils
  class New < TilWeb::View::Controller
    configure do |config|
      config.template = "tils/new"
    end

    expose :errors, default: []
  end
end

What do you think @timriley

Thanks for thinking this up and submitting this PR, @GustavoCaso.
One thing I worry about this feature is that it's a little vague as to when the default for an exposure should actually apply. Right now with the code you have here, an exposure's default will apply if its returned value is nil. However, there are cases when we might actually want a nil value to be passed through?
Further, do you think there's much benefit to defaults being provided as config versus being provided as part of the exposure's block/method? For example:
expose :errors do |input|
  input.fetch(:errors) { [] }
end

This achieves the same thing as your proposed expose :errors, default: [] behaviour, but IMO it's probably a little clearer. What do you think?

@timriley thanks for reviewing it.
After looking at your example it is true that is more clear.
One thing that could happen is seeing this pattern repeated if we have multiple expose that might be part of the input arguments of the view object and we want to have default values for all of them, maybe in the future if we find this happening often we can revisit this idea.

@timriley I updated the PR 😄 hope id ready for new release 📦

Thanks, @GustavoCaso, this is good!


Facebook OAuth Token as HTML instead of JSON fails

Hello,
I've started to use this Library for our Website project. I've already implemented Google Sign-In to our website which works fine. Now I am trying to integrate the Facebook Login too.
But it seems like Facebook don't respond with JSON after creating the Token. That's mostly what my code looks like:
client = Signet::OAuth2::Client.new(
   :authorization_uri => "https://www.facebook.com/#{self::FACEBOOK_GRAPH_VERSION}/dialog/oauth",
   :token_credential_uri =>  "https://graph.facebook.com/#{self::FACEBOOK_GRAPH_VERSION}/oauth/access_token",
   :client_id => 'XXXXXX',
   :client_secret => 'XXXXXX',
   :scope => 'public_profile email',
   :redirect_uri => "#{API_URL}/oauth/v2/third_party/facebook",
   :state => state
)

client.code = params['code']
client.fetch_access_token! # here will be the error thrown

#<ArgumentError: Invalid content type 'text/plain; charset=UTF-8'>
["/usr/local/rvm/gems/ruby-2.3.3/gems/signet-0.7.3/lib/signet/oauth_2.rb:86:in `parse_credentials'",
 "/usr/local/rvm/gems/ruby-2.3.3/gems/signet-0.7.3/lib/signet/oauth_2/client.rb:975:in `fetch_access_token'",
 "/usr/local/rvm/gems/ruby-2.3.3/gems/signet-0.7.3/lib/signet/oauth_2/client.rb:998:in `fetch_access_token!'",
 "..............third_party_controller.rb:62:in `facebook'",

Is there any chance to set the Content-Type or Accept Header for this request? I think that should be the issues, don't know why Facebook responds by default with HTML.
Regards,
Alex

Hello,
using a newer Graph Version fixed it.


Correction for raw affiliation Information and Systems (MIS) Laboratory, University of Picardie Jules Verne, GRECO Institute, Amiens, Modeling, France

Correction needed for raw affiliation Information and Systems (MIS) Laboratory, University of Picardie Jules Verne, GRECO Institute, Amiens, Modeling, France
raw_affiliation_name: Information and Systems (MIS) Laboratory, University of Picardie Jules Verne, GRECO Institute, Amiens, Modeling, France
new_rors: 01gyxrk03
previous_rors: 00b4yme84;01gyxrk03
works_examples: W4388754831
contact: f9949144e1f28d87cacee5ee7da68ff5:768d6fbec88181f4b47fcb103e36f214 @ u-picardie.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-09. The new affiliations should be visible within the next 7 days.


Fix button for diffs without whitespace

Since the new code reviews functionality on GitHub there has been some interface changes. GitHub changed the diff options from a drop down to a button group so the feature initially implemented in #196 stopped working.
We should change the code putting the button to make checks and modifications against the updated DOM structure.

The key to fixing this is changing how we check for the current DOM here: https://github.com/sindresorhus/refined-github/blob/b12ad0b07d24602fe400d887004540734b742500/extension/content.js#L240 and how we insert the button here: https://github.com/sindresorhus/refined-github/blob/b12ad0b07d24602fe400d887004540734b742500/extension/content.js#L269-L275

@anselmh @steveoh or anyone else who wants to work on this?

I’ll fix that. Sorry, totally had forgotten about this.

And here you go with https://github.com/sindresorhus/refined-github/pull/425.


Drawer Open/Close callback

An application I'm working on requires being able to detect when a Drawer is opened and closed which currently is not possible. Is it possible to add a callback on this event?
My use case requires the underlying android app to know the status of the drawer and I've been unable to think up any work arounds so far. As far I can tell merge #20015 has already implemented most of the required code for this.

#20856 seems to address that

Looks like a dup of #14510

Closing as duplicate.

This should be resolved by #67249


Function generics matcher

Match generic names in signature functions.
Now ForbiddenMethod call allows to forbid kotlin.runCatching {} but allowing runCatching {}.
closes #4448

I would like to merge this one in 1.20 too if possible. This PR was waiting for #4459 to be merged because it depends on that code.

I'm fine adding this, but we need some follow-up docs for this to the website

🤔 I don't think we need to add new documentation here. The current documentation matchs what this matcher does. This one is more a "bug-fix" than a new feature. I mean, for sure it is a new feature but for a user it could seems like the same. The PR that introduced real changes was #4459 and I added the documentation directly in it. https://github.com/detekt/detekt/pull/4459/files#diff-76703cf8efe31f0c7e06926568e0d1e248eb82cb63bd40b0b37698dc35bed70fR52


Not authorized on custom resolvers

Going a bit crazy with the custom resolvers. Trying to do a simply query with an api key and it's failing. Tried adding the @aws_api_key on the types as well, but still failing. When using cognito user pool it works as expected
This happens on deployed version only
@maoosi would greatly appreciate it if you could point me in the right direction here
query MyQuery {
  healthcheck {
    db
    status
  }
}

This is the result
{
  "data": {
    "healthcheck": null
  },
  "errors": [
    {
      "path": [
        "healthcheck",
        "db"
      ],
      "data": null,
      "errorType": "Unauthorized",
      "errorInfo": null,
      "locations": [
        {
          "line": 3,
          "column": 5,
          "sourceName": null
        }
      ],
      "message": "Not Authorized to access db on type HealthcheckStatus"
    },
    {
      "path": [
        "healthcheck",
        "status"
      ],
      "data": null,
      "errorType": "Unauthorized",
      "errorInfo": null,
      "locations": [
        {
          "line": 4,
          "column": 5,
          "sourceName": null
        }
      ],
      "message": "Not Authorized to access status on type HealthcheckStatus"
    }
  ]
}

And the handler + shield:
return await client.resolve<
    | 'healthcheck'
  >({
    event,
    shield: ({}: QueryParams) => {
      return {
        '**': {
          rule: true,
          reason: ({ model }) =>
            `${model} access is restricted to logged-in users.`,
        },
      }
    },
    resolvers: {
      healthcheck: async ({ args: _, prismaClient }: QueryParamsCustom) => {
        try {
          await prismaClient.$queryRaw`SELECT 1`
          return {
            status: true,
            db: 'OK',
          }
        } catch (e) {
          return {
            status: false,
            db: (e as any).message,
          }
        }
      },
    },
  })

Custom schema
type HealthcheckStatus
  @aws_api_key
  @aws_cognito_user_pools(cognito_groups: ["admins", "superadmins"]) {
  status: Boolean!
  db: String!
}

extend type Query {
healthcheck: HealthcheckStatus
    @aws_api_key
    @aws_cognito_user_pools(cognito_groups: ["admins", "superadmins"])
}

Hey @cipriancaba, I can't see anything wrong with what you just shared. Any chance you'd have a reproduction repo handy with your entire schema and custom resolver files? Otherwise, I can try to replicate the issue on my end over the weekend.

I ended up removing the shield validation and that seemed to do the trick. Not ideal, since will need to add it back soon for user authorization
In general, it feels like working with custom resolvers is a bit cumbersome. For example, spent hours trying to figure out why my custom resolver wasn't returning the proper data, just to realise that I forgot to add it to the custom-resolvers.yaml file. It was obviously working fine locally.
I think the following areas could benefit some improvements:

More documentation around custom resolvers. I think that any real world use case would need to have custom resolvers
Clarify how the custom directives should work in custom-schema (eg, do you need to add @aws_api_key on custom type? )
Simplify the process of creating custom resolvers. It's just too easy to misconfigure them atm. Maybe we can potentially generate at least the custom-schema.yml ?
Improve the QueryParamsCustom interface to allow for generic type params (I actually have a PR for it) so it's easier to work with args

I understand that maybe this might not be the focus of the library, but this would definitely make it easier to use and become the swiss army knife of graphql backends


Cannot find pappl

I have configured, maked, and make installed pappl from git HEAD, but this still cannot find it:
checking for PAPPL... no
configure: error: Package requirements (pappl) were not met:

Package 'pappl', required by 'virtual:world', not found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables PAPPL_CFLAGS
and PAPPL_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

You need to add /usr/local/lib/pkgconfig to PKG_CONFIG_PATH


Added the google maps object export to main.js

This PR is about #39 . We wanted to use google.maps for our own code, but we had no way to do that.
I don't think that what I am doing here is good enough. Here is what I did:

The main.js file has the export components for us. I only added an object that will hold the google.maps object in it and exported it with everything else.

The main problem you will find here is that google.maps is not loaded directly, we need to wait for it to load (this is known as lazy load).

This variable starts at null and its been exported directly, so when you import it, it will be always null. There is no google.maps object yet at this point.

The makeGMapApiPromiseLazy loads the Google API but we need to wait for it to happen. When it is finished, our googleMapsObject variable is populated and now it can be used in your code.

So here is an example of what we would need to do to load the google.maps (as known as googleMapsObject variable). Notice that I had to make a setTimeout to wait for the googleMapsObject that was imported to have a value in it.

<script setup>
import { ref } from "vue";
import { googleMapsObject } from "vue-google-maps-community-fork";

const test = ref(googleMapsObject);

const center = ref({ lat: 51.093048, lng: 6.84212 });
const markers = ref([{ position: { lat: 51.093048, lng: 6.84212 } }]);

setTimeout(() => (test.value = googleMapsObject), 20);
</script>

<template>
   <GMapMap :zoom="5" :maxZoom="5" style="width: 500px; height: 300px">
      <GMapCluster>
         <GMapMarker
            :key="index"
            v-for="(m, index) in markers"
            :position="m.position"
            :clickable="true"
            :draggable="true"
            @click="center = m.position"
         />
      </GMapCluster>
   </GMapMap>

   {{ test }}
</template>

This code lead us to this result:

@andyslack can you please help us validate this?
Every other help to improve the code is welcome.
You guys can clone this PR and add in your package.json as:
"vue-google-maps-community-fork": "file:./path/to/vue-google-maps-community-fork/"
then run npm install again.

Hi @NathanAP
This seems to be working, however I noticed on reloading the page every now and then googleMapsObject is still null, I guess the setTimeout() is not long enough.
Putting it inside the watch function on the mapRef sorted that out.

Before:

After:

Nice work!

I will add an example in docs before merging this PR.

@andyslack I changed googleMapsObject variable name for GMapObject just to keep the var names we already have in the library. Can you confirm everything still fine for you?

This PR is closed due to the #39 conversation.


🐛 [HOSTED-RR] Generated Issue: ObjectNotFound

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
The API has returned an error:
Typesense\Exceptions\ObjectNotFound
Status code: 0
Message: Could not find a field named `popularity` in the schema for sorting.
Trace: /app/vendor/typesense/typesense-php/src/ApiCall.php on line 348
Expected Behavior
The API should have returned a successful response with data.
Steps To Reproduce
Http Request: `GET /v4/anime?q=pekora
Environment
- OS: Ubuntu 24.04.1 LTS
- Browser: Google Chrome Versión 129.0.6668.89
- Docker image: jikanme/jikan-rest:latest

Anything else?

fyi we have an issue for changing this error message: https://github.com/jikan-me/jikan-rest/issues/478

Related issue: https://github.com/jikan-me/jikan-rest/issues/477


Fix wrapper

The existing wrapper script does not work with the classic snap (and is not necessary) so let's just overwrite it.

Without more context or an explanation of what's being changed (and, perhaps, a test?) this is impossible for me to review :/

The context is that the existing wrapper script does not work with the classic snap because classic snaps don't have plugs and thus IS_CONNECTED will evaluate to false.


EB-390: Github contrbution guide

This PR drafts a Github contribution guide for users who would be willing to submit new species through pull requests.
I could be paired with an adequate pull request template.
I plan to add subsequent sections for undaunted users who would like to get started with their species content
using hugo new or add_new_species.py.
Finally, I used the AsciiDoc format that was praised at PyCon to give it a try. If you prefer sticking to Markdown, it will give me a nice opportunity to try Pandoc 🙂
All remarks welcome of course, this is an experiment!

@kwentine great initiative! I wonder if it would be good to have a "dev" branch to which user's PRs are first merged and tested, and then if everything looks good (pass our review), then the PR is merged to main?

I wonder if it would be good to have a "dev" branch to which user's PRs are first merged and tested

Thanks for bringing up that point.
Since we can deploy any branch for testing purposes on our development portal https://swedgene.scilifelab-2-dev.sys.kth.se/, I think both review and preview can occur directly on the PR branch. In other words, nothing additional could be tested by introducing a dev branch. But curious to hear what @RMCrean and @brinkdp think.

One thing that could be added is to encourage them to allow us to commit to their forked branch

Great suggestion, thanks. Mentioned it in cd07bb4

I agree that I don't think we need a dev branch for this case.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/436 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target.git

Docs Build status updates of commit 5d9c83b:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Release_Archive_master_2020-03-19-06-19-10 has been deleted or has been force pushed: fatal: couldn't find remote ref refs/heads/Release_Archive_master_2020-03-19-06-19-10

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


Keywords in strings detected as expressions

Example ('for' is part of the string, yet it's detected as an expression):

The new version fixed the problem and will be published when godot 3.2 RC release.

I'm closing this as the new version has fixed this issue.
You can try the new version of the plugin with godot 3.2 from the release page


New editor field for page children links

Some pages require you to specify another item from the tree (not at page level) in order to create a link of some type. For example, the decision tree page requires you to select a child of the page (another Q or a result step) to link to from each answer option. At the moment this is done by giving each child of the page an id & typing the id into the target box to create the link. The 360 image page will also contain something similar.
It would be much easier if there was an editor option where child nodes of the current page were listed in a drop down box. Something similar is done on connector pages but the drop down box contains a list of all pages within the project - this new option would contain only the child nodes of the page being edited.

I've added this functionality to editor but need to change xwds for pages where it would be useful


Link Rot: www.adafruit.com

As of July 29, 2017 (potentially earlier) www.adafruit.com is returning 503 Service Unavailable to all web requests. This ticket tracks the Link Rot.
If the issue isn't addressed in two weeks, I'll replace the links.

Closed by 6d6727d575538d9f8446eaccd09bb50f0cd997a3.


Blender throws keyframe error when exporting as gltf with animations - Key.path_resolve could not be resolved

Blender fails to export my 3d model with animations. This error is most probably my fault as I am inexperienced with blender and animations. Still can't find any way to fix the issue. The issue might also be related to the sample blender file that I am using.
Python: Traceback (most recent call last):   File "D:\Program Files\Blender Foundation\Blender 3.4\3.4\scripts\addons\io_scene_gltf2\__init__.py", line 693, in execute     return gltf2_blender_export.save(context, export_settings)   File "D:\Program Files\Blender Foundation\Blender 3.4\3.4\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_export.py", line 35, in save     json, buffer = __export(export_settings)   File "D:\Program Files\Blender Foundation\Blender 3.4\3.4\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_export.py", line 52, in __export     __gather_gltf(exporter, export_settings)   File "D:\Program Files\Blender Foundation\Blender 3.4\3.4\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_export.py", line 66, in __gather_gltf     active_scene_idx, scenes, animations = gltf2_blender_gather.gather_gltf2(export_settings)   File "D:\Program Files\Blender Foundation\Blender 3.4\3.4\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather.py", line 34, in gather_gltf2     animations += __gather_animations(blender_scene, export_settings)   File "D:\Program Files\Blender Foundation\Blender 3.4\3.4\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather.py", line 93, in __gather_animations     animations_, merged_tracks = gltf2_blender_gather_animations.gather_animations(obj_uuid, merged_tracks, len(animations), export_settings)   File "D:\Program Files\Blender Foundation\Blender 3.4\3.4\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather_animations.py", line 114, in gather_animations     animation = __gather_animation(obj_uuid, blender_action, export_settings)   File "D:\Program Files\Blender Foundation\Blender 3.4\3.4\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather_animations.py", line 164, in __gather_animation     channels=__gather_channels(obj_uuid, blender_action, export_settings),   File "D:\Program Files\Blender Foundation\Blender 3.4\3.4\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather_animations.py", line 201, in __gather_channels     return gltf2_blender_gather_animation_channels.gather_animation_channels(   File "D:\Program Files\Blender Foundation\Blender 3.4\3.4\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather_cache.py", line 38, in wrapper_cached     result = func(*args, **kwargs)   File "D:\Program Files\Blender Foundation\Blender 3.4\3.4\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather_animation_channels.py", line 160, in gather_animation_channels     channel = gather_animation_channel(   File "D:\Program Files\Blender Foundation\Blender 3.4\3.4\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather_animation_channels.py", line 300, in gather_animation_channel     sampler = __gather_sampler(channels, obj_uuid, export_settings, bake_bone, bake_channel, bake_range_start, bake_range_end, force_range, action_name, driver_obj_uuid, node_channel_is_animated)   File "D:\Program Files\Blender Foundation\Blender 3.4\3.4\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather_animation_channels.py", line 368, in __gather_sampler     return gltf2_blender_gather_animation_samplers.gather_animation_sampler(   File "D:\Program Files\Blender Foundation\Blender 3.4\3.4\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather_cache.py", line 38, in wrapper_cached     result = func(*args, **kwargs)   File "D:\Program Files\Blender Foundation\Blender 3.4\3.4\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather_animation_samplers.py", line 59, in gather_animation_sampler     input = __gather_input(channels, obj_uuid, is_armature, non_keyed_values,   File "D:\Program Files\Blender Foundation\Blender 3.4\3.4\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather_cache.py", line 38, in wrapper_cached     result = func(*args, **kwargs)   File "D:\Program Files\Blender Foundation\Blender 3.4\3.4\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather_animation_samplers.py", line 243, in __gather_input     keyframes, is_baked = gltf2_blender_gather_animation_sampler_keyframes.gather_keyframes(blender_obj_uuid,   File "D:\Program Files\Blender Foundation\Blender 3.4\3.4\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather_cache.py", line 38, in wrapper_cached     result = func(*args, **kwargs)   File "D:\Program Files\Blender Foundation\Blender 3.4\3.4\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather_animation_sampler_keyframes.py", line 357, in gather_keyframes     mat = get_object_matrix(blender_obj_uuid,   File "D:\Program Files\Blender Foundation\Blender 3.4\3.4\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_gather_cache.py", line 102, in wrapper_objectcache     return func.__objectcache[cache_key_args[0]][cache_key_args[1]][cache_key_args[4]] KeyError:<PHONE_NUMBER>9296875
To Reproduce
1.Steps to reproduce the behavior:
2.Open my model in Blender 3.4.0
Export as gltf with animation export turned on
.blend file/ .gltf
used this model]

Confirmed.
Linked to frame that are not integer.
Workaround for now : select all your keyframes in dopsheet, and Key > Snap > Snap Selection to nearest frame

Hello,
This is now fixed in current main branch, after animation refactor 64e3532f48ebdf878a1c9b81ade6d1a19c8ff890


Support decimals in amounts

Is your feature request related to a problem?
Currently the lib only supports integers as amounts.
So we can't send amounts with decimals.
Describe the solution you'd like
Support decimals in amounts fields
Additional context
No response
Epic
No response

after discussion, we will keep integers here


XLSB Read error

I'm trying to read a simple xlsb (Excel binary) file.
When I try to upload the file, I get the following error: Error: Unexpected record 3072.
I have attached the xlsb file and the SheetJs demo can be used to simulate the issue (http://oss.sheetjs.com/).
Book1.zip

@gustavosimil  Thank you very much !  Coincidentally we found this issue earlier today and are preparing for the next release.
The 0x0c00 record type is not specified in MS-XLSB but the best guess is that it represents the underspecified "BrtUid" record.  We already reported the spec error to Microsoft: https://social.msdn.microsoft.com/Forums/en-US/880eb3f3-395a-4097-ad01-8e0878d0b436/xlsb-brtuid-record-type-not-defined?forum=os_binaryfile .
We will release 0.12.6 soon with the fix.

After pushing out the update, this appears to work.  Thanks a lot!

Yes, it is working now. Thanks!


Mobile Heating Issue

Hi!
After installing the esteem mobile for iOS i am observing that mobile is heating much.
I used this app 15 minutes continuous and felt that my iPhone got heated much.

net info temporarily disabled because of this issue


Changing the default bank account doesn't work

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.62-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @danieldoglas
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1712731362765859
Action Performed:

You need to have 2 bank accounts in the app
Go to Settings > Wallet
Click on the context menu for the account that is not the default, and click on Make Default Payment method

Expected Result:
The new account should be the default one
Actual Result:
The new account appears to be the default one in the app, but if you look on old dot, the old account is still the default one
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/38435837/e8808051-3f93-4f8f-9014-6d69a1dd490c

View all open jobs on GitHub

Per this, dupe of https://github.com/Expensify/Expensify/issues/299712

Closing!


Update to 3.0.3

Update to 3.0.3
Upstream diff: https://github.com/alkaline-ml/pmdarima/compare/v1.8.5..v2.0.2
conda-forge diff: https://github.com/conda-forge/pmdarima-feedstock/compare/8b01fd8f52e075aad95f0d7bc736cca2b879ec36..f42fcffa99688454aa61511c86f3da9a2d4f5e2f

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_cbkcxinv_s/clone/recipe/meta.yaml:33: python_build_tool_in_run: The python build tool cython is in run depends
ERROR: /tmp/abs_cbkcxinv_s/clone/recipe/meta.yaml:33: cython_must_be_in_host: Cython should be in the host section
WARNING: /tmp/abs_cbkcxinv_s/clone/recipe/meta.yaml:40: python_build_tool_in_run: The python build tool setuptools is in run depends
WARNING: /tmp/abs_cbkcxinv_s/clone/recipe/meta.yaml:64: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_71bdlniiej/clone/recipe/meta.yaml:33: python_build_tool_in_run: The python build tool cython is in run depends
ERROR: /tmp/abs_71bdlniiej/clone/recipe/meta.yaml:33: cython_must_be_in_host: Cython should be in the host section
WARNING: /tmp/abs_71bdlniiej/clone/recipe/meta.yaml:40: python_build_tool_in_run: The python build tool setuptools is in run depends
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_12crl4e_yj/clone/recipe/meta.yaml:33: python_build_tool_in_run: The python build tool cython is in run depends
ERROR: /tmp/abs_12crl4e_yj/clone/recipe/meta.yaml:33: cython_must_be_in_host: Cython should be in the host section
WARNING: /tmp/abs_12crl4e_yj/clone/recipe/meta.yaml:40: python_build_tool_in_run: The python build tool setuptools is in run depends
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_61r_trs_fb/clone/recipe/meta.yaml:33: python_build_tool_in_run: The python build tool cython is in run depends
ERROR: /tmp/abs_61r_trs_fb/clone/recipe/meta.yaml:33: cython_must_be_in_host: Cython should be in the host section
WARNING: /tmp/abs_61r_trs_fb/clone/recipe/meta.yaml:40: python_build_tool_in_run: The python build tool setuptools is in run depends
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_ba569n7pjx/clone/recipe/meta.yaml:29: python_build_tool_in_run: The python build tool cython is in run depends
ERROR: /tmp/abs_ba569n7pjx/clone/recipe/meta.yaml:29: cython_must_be_in_host: Cython should be in the host section
WARNING: /tmp/abs_ba569n7pjx/clone/recipe/meta.yaml:36: python_build_tool_in_run: The python build tool setuptools is in run depends
Errors were found


Add backend.user_can_authenticate() to allow for additional checks

This is the same pattern used in django's auth backend - in fact, I just copied the method verbatim:
https://github.com/django/django/blob/master/django/contrib/auth/backends.py#L51-L57
NOTE: I can add a test if required.

This PR fixes the issue I face - e.g. being able to set a redirect URL but as a result this code will never get hit:
https://github.com/peppelinux/djangosaml2/pull/253/files#diff-14e9a5c86c429d4f469f5e22f7c2c4b239e52569a920f15c58513f2d2a216332R438-R439
Is it important to log that RelayState was not provided?
Either I could remove the check/logging statement (lines 438/439) or restructure it so that it is correctly aware if the incoming request has no relay state.

I really like this feature, thank you.
Please take also a look to uniAuth project, I think that we could do something more together

Please rebase to PR to the Dev branch, I'll merge It asap


Gluon hybridize fails to detect an input

Here is a minimal example of hybridize failing to detect an input: https://gist.github.com/altosaar/6c29d8ac505ae1cea03ca65f193e7832
Without hybridize, this code runs fine.
However, hybridize thinks one of the inputs is not used. Stack trace:
/usr/local/anaconda3/lib/python3.6/site-packages/h5py/__init__.py:36: FutureWarning: Conversion of the second argument of issubdtype from `float` to `np.floating` is deprecated. In future, it will be treated as `np.float64 == np.dtype(float).type`.
  from ._conv import register_converters as _register_converters
/usr/local/anaconda3/lib/python3.6/site-packages/mxnet/gluon/block.py:414: UserWarning: The 2-th input to HybridBlock is not used by any computation. Is this intended?
  return self.forward(*args)
Traceback (most recent call last):
  File "gluon-hybridize-error.py", line 70, in <module>
    model(users, items, item_counts, set_sizes)
  File "/usr/local/anaconda3/lib/python3.6/site-packages/mxnet/gluon/block.py", line 414, in __call__
    return self.forward(*args)
  File "/usr/local/anaconda3/lib/python3.6/site-packages/mxnet/gluon/block.py", line 620, in forward
    return self._call_cached_op(x, *args)
  File "/usr/local/anaconda3/lib/python3.6/site-packages/mxnet/gluon/block.py", line 525, in _call_cached_op
    self._build_cache(*args)
  File "/usr/local/anaconda3/lib/python3.6/site-packages/mxnet/gluon/block.py", line 513, in _build_cache
    self._cached_op = ndarray.CachedOp(out, self._flags, input_names, param_dict)
  File "/usr/local/anaconda3/lib/python3.6/site-packages/mxnet/_ctypes/ndarray.py", line 130, in __init__
    ctypes.byref(self.handle)))
  File "/usr/local/anaconda3/lib/python3.6/site-packages/mxnet/base.py", line 210, in check_call
    raise MXNetError(py_str(_LIB.MXGetLastError()))
mxnet.base.MXNetError: [16:11:21] src/imperative/cached_op.cc:91: Check failed: arg_name_to_id.size() == arg_names.size() (3 vs. 4) CachedOp expects 3 inputs, given 4

Stack trace returned 6 entries:
[bt] (0) 0   libmxnet.so                         0x0000000111e58bb4 libmxnet.so + 19380
[bt] (1) 1   libmxnet.so                         0x0000000111e5896f libmxnet.so + 18799
[bt] (2) 2   libmxnet.so                         0x0000000112f0906f MXNDListFree + 353135
[bt] (3) 3   libmxnet.so                         0x0000000112e8cead MXCreateCachedOpEx + 845
[bt] (4) 4   libffi.6.dylib                      0x000000011063b884 ffi_call_unix64 + 76
[bt] (5) 5   ???                                 0x00007ffee0120790 0x0 +<PHONE_NUMBER>98704

Yup this is with the latest nightly build.

@sandeep-krishnamurthy Could you please tag this as question and gluon

The problem is in the following line:
https://gist.github.com/altosaar/6c29d8ac505ae1cea03ca65f193e7832#file-gluon-hybridize-error-py-L17
split_item_emb = F.split(item_emb, axis=0, num_outputs=len(set_sizes))
__len__ behaves differently between symbol and ndarray.
In general, hybrid_forward doesn't support having shape-specific logic.

    # split into set lists. each list is of length max_set_size
    split_item_emb = F.split(item_emb, axis=0, num_outputs=len(set_sizes))

    # stack the lists to get a set dimension. need to sum each set separately
    if len(split_item_emb) > 1:
      batch_item_emb = F.concat(*split_item_emb, dim=0)
    else:
      batch_item_emb = split_item_emb

seems to be equivalent to
batch_item_emb = item_emb

@piiswrong it would be great if we could have a way to explicitly warn about this though

This usage is not supported by hybridize. I can't think of a way to fix or warn about this without breaking API though.
Closing as unsupported


Few CWE root causes are mapped from the CVE database into OSV

I'm working on a vulnerability detection benchmark using OSV as the main data source. Having as many CWE root causes as possible would be useful for the project. Yet I notice that few CWEs seem to make it into OSV.
There are many CWEs included in e.g. cvelistV5:
$ cd /tmp
$ git clone https://github.com/CVEProject/cvelistV5.git
$ cd cvelistV5
$ fd '.json$' . | wc -l
252803
$ rg '"CWE-' . | wc -l
126266

Yet few in OSV:
$ cd /tmp
$ mkdir osv && cd osv
$ wget https://osv-vulnerabilities.storage.googleapis.com/GIT/all.zip
$ unzip all.zip
$ fd '.json$' . | wc -l
31413
$ rg '"CWE-' . | wc -l
135

For one random example of an entry that has a CWE in the CVE data but not in OSV:
$ rg -C4 '"CWE-' cvelistV5/cves/2023/4xxx/CVE-2023-4696.json
69-                    "descriptions": [
70-                        {
71-                            "type": "CWE",
72-                            "lang": "en",
73:                            "description": "CWE-284 Improper Access Control",
74:                            "cweId": "CWE-284"
75-                        }
76-                    ]
77-                }
78-            ],
$ rg 'CWE' osv/CVE-2023-4696.json
# no match

The only OSV items in the GIT ecosystem that have a CWE are CURL-CVE-* items, and a few PSF-* items.
Is there a reason for this?
For now, it seems that the best way for me to get the CWEs is to also clone the cvelistV5 repository in parallel and get them from there.
Might they be included in OSV at some point in the future?

Hi @timothee-chauvin your benchmark sounds really cool!
There's a couple of different angles here:
CWE representation in the OSV Schema
I'm unclear on what fd and rg are in your examples, but to your point about CWEs on OSV records, the OSV Schema today does not define this as a field. Any CWE IDs you're seeing from your examination of OSV.dev's exported data are appearing in the details of the record, or in the database_specific field:

PSF-2023-3
CVE-2023-39375

Today, the OSV Schema does not have a formal CWE field. If this is something you feel it would benefit from having, I would encourage you to have that conversation via an issue in https://github.com/ossf/osv-schema
It's also important to remember that OSV.dev is an aggregator of disparate data sources publishing vulnerability information in the OSV format. Ultimately, these data sources would need to be supplying CWEs with the records they publish.
CWE representation in OSV records we're generating from NVD CVEs
We are converting CVEs from the NVD, and these may have CWE information included in them in a structured way, e.g. CVE-2023-4696
For these records, if you're asking for any available CWE information to be included in a database_specific field, similar to how it appears on PSF-2023-3 for example, then we can clarify this issue down to being a feature request for that, since we are in direct control of that data source...

Thanks for the reply! Sorry, I quickly copy-pasted the commands I used, but fd refers to https://github.com/sharkdp/fd (an alternative to find) and rg to https://github.com/BurntSushi/ripgrep (an alternative to grep).
A formal CWE field would certainly be nice, but less important (and also more work?) than simply having the CWE information mapped from the NVD CVEs into the database_specific.cwe_ids field of the OSV schema.
So yes, we can consider this issue as a feature request for mapping the CWEs included in NVD CVEs into the database_specific.cwe_ids field.
That being said, this isn't currently a major blocker for me (since as I mentioned, there's the workaround of cloning the cvelistV5 repo and getting the information from there). So I'll let you decide on which priority this should have!
And thanks for your work on OSV, which helped me get started with the benchmark!

Thanks for clarifying. I think this can be treated as a feature request for our CVE conversion process to include the underlying CVE's CWE in the database_specific field, ala
  "database_specific": {
    "cwe_ids": [
      "CWE-416"
    ]
  }

Notes to (future) self:

in the NVD CVE record, this is .cve.weaknesses[].description[].value
in the CVE 5.x record, this is .containers.cna.problemTypes[].descriptions[].cweId


Question: While trying to add dialogue to a little Kade Engine mod I am doing for myself, I decided to not add dialogue, and now this error pops up.


Move backend issues to frontend repo

Overview
We need to move backend issues over to the frontend repo so we have one centralized location where the entire team can easily locate issues.
Action Items

[x] transfer all the issues that have been created on the backend repo, to the front end repo.
[ ] add all the missing labels
[x] discuss with devs potential complications that may occur with this move.

Resources/Instructions
Back end repo issues: https://github.com/civictechindex/CTI-website-backend/issues

Discussed with Bruce and Fang, there should be no complications. I went and moved all the issues from backend to frontend. Now just need proper labeling.
Issues moved to frontend repo:
#1049
#1050
#1051
#1052
#1053
#1054
#1055
#1056
#1057


Problem receiving message, an example would help

An end-to-end example of 1) create queue, 2) send message, 3) receive message and 4) delete queue would be a really helpful little piece of documentation.
As it is, I can accomplish 1 & 2, but not 3.  I am a scala noob, for sure, so chances are high that I'm just missing something obvious.  The symptom that I see is that my onComplete never seems to get called.  When executed at the command-line the program will run for about a minute and then exit.
Here is some really basic code of mine that does not do 3:
package com.learnAWSScala

import com.amazonaws.regions.Regions
import scala.concurrent._
import ExecutionContext.Implicits.global
import scala.concurrent.duration
import scala.util.{Success, Failure}

import com.kifi.franz.SimpleSQSClient

object Hello {

  def main(args : Array[String]) = {
    println("Hello World")

    val sqs = SimpleSQSClient("MY ID HERE", "MY SECRET HERE", Regions.US_EAST_1)

    val q = sqs.simple(com.kifi.franz.QueueName("testScalaQueue"), true)

    q.send("Hello AWS!")

    val msg = q.next(scala.concurrent.ExecutionContext.global)

    msg onComplete {
	  case Success(message) => println("got a message")
	  case Failure(t) => println("An error has occured")
	}

    println("More stuff")
  }
}

@JediMindtrick what library are you using for SQS support in Scala?

@ilanbiala Sorry, that was a learning project and it looks like I scrapped it.


Computed signals not working in dead-simple React component

I have simplified the scenario in this code playground: https://playcode.io/2199837
Basically - I have a count, which increments when I click a button ... but the computed signal never gets updated ... neither in the JSX template nor in the JS code.
Any idea if this is supposed to behave like this?

@JoviDeCroock  - OK, I will try to stick to the templates for the issues.
However - even if I use the two hooks - useSignal and useComputed - then I get the same result: https://playcode.io/2200161.

You have to use 'useSignals' note the s at the end. Or the babel plugin


Unable to securely authenticate Azure Function with SPA

Public clients or SPA cannot store Function keys securely. We need a way for SPAs to securely call the Azure functions. We have OpenID connect code workflow, why is access_token based authorization not supported ? This seems critical !
For example:
The SPA can use OpenID connect and authorization code workflow to authenticate a user and then generate access token. Based on the user roles and permission the access token can be used to authorize the call to the Azure function but how do I pass an access_token from a client to an Azure function ?

Specifically I want to call Azure Functions securely from standalone Blazor Web Assembly (SPA).

@fabiocav , I did a quick prototype by making the Azure functions access level Anonymous and then using AAD to verify the signed JWT access_token passed with the authorization header.
public async Task<HttpResponseData> RunCreate([HttpTrigger(AuthorizationLevel.Anonymous, "post", Route = "microsoftsaas/b2btenants")] HttpRequestData req)
Sample code inside Azure function
// Sample code to check the access_token issued by MSAL for multi-tenant Azure AD.
string accessToken = await req.GetAccessTokenAsync();
await accessTokenChecker.CheckAsync(accessToken, model.LoginTenantId, model.LoginObjectId, "tenants");

I can now call Azure functions from SPA and authorize the call via access_token.
Do you see any issues with this approach? I don't see any other way to achieve this right now?

@ameyasubhedar that's a reasonable approach.
This is more of a host/service requirement, as opposed to the worker, but what you have above is absolutely fine.

Closing as resolved, but let us know if you need any additional information.


Missing quotes around defaults with MySQL

Describe the bug
migrations set default values for string every time.
(The db diffing is incorrect because it treats the default value for varchar columns without quotes)
To Reproduce
Steps to reproduce the behavior:

Create an entity with a default string

@Entity()
export class MyEntity {

    @PrimaryKey()
    id!: number

    @Property({ default: "NEW" })
    stringDefault!: string
}

disable snapshots in the config (the problem occurs when the source is the db)

create a migration and run it
(or just run the following query : create table `MyEntity` (`id` int unsigned not null auto_increment primary key, `stringDefault` varchar(255) not null default 'NEW') default character set utf8mb4 engine = InnoDB`)

create the migration again.

Expected behavior
The 2nd migration should be empty but it contains
alter table `MyEntity` modify  `stringDefault` varchar(255) not null default \'NEW\'

Additional context
It seems that the problem occurs because in MySqlSchemaHelper.getColumns(), the default value has no quotes.
As a result, the schema comparator compares default:''NEW'' with default:'NEW' and think it must correct it every time.
Proposed fix
in  MySqlSchemaHelper.getColumns()
replace
default:  col.column_default

by
default:  mappedType instanceof StringType ? `'${col.column_default}'` : col.column_default

Or something like that.
But maybe there is a reason why the defaults are handled this way.
Versions

Dependency
Version

node
v14.16.1

typescript
4.4.4

mikro-orm
5.0.0-dev.434

your-driver
@mikro-orm/mysql

Thanks for the report, got it reproduced and I can confirm it behaves this way.


Does not support strings with placeholders

Support is currently disabled for template strings that use any placeholder values:
import styled from 'styled-components'

const color = '#f0f'
styled.button`
    color: ${color};
`

Initial support should be in 0.0.5:

Please open new issues for any errors or edge cases you find around placeholders


[question] How open SQLite database in shared folder?

I'm currently using react-native-sqlite-storage to open a database in shared mode, with several native modules running in the background on iOS. This setup leverages an App Group's Shared Container, allowing access to the same database instance across native modules and the main application, storing the files in the following directory:
.//Shared/AppGroup/4045CAC7-5BC7-4A1C-8D40-EE98C46CFCC0/app.db
I noticed in the code at line 54-55 that you're reading the appGroupID from the OPSQLite_AppGroup key.

However, after checking in the Xcode debugger, it seems this code is never reached. Instead, the database files are always created under a different directory:
.//Data/Application/7BEE9A09-790D-4F6E-BA20-6DE1431CC045/Library/app.db
Could you please clarify how to configure OP-SQLITE to work with a shared folder?

Did you set the value in the info.plist?

Yes, of course

Did you set it with the key OPSQlite_AppGroup? Or did you take the comment literally?

This is also described in the docs
https://ospfranco.notion.site/Configuration-6b8b9564afcc4ac6b6b377fe34475090?pvs=4
Closing this

I figured out the issue. There's no need to pass the location parameter in shared mode:
let db;

if (Platform.OS === 'ios') {
  db = open({ name: 'myDB' });
} else {
  db = open({ name: 'myDB', location: ANDROID_DATABASE_PATH });
}

I'm using version 3.0.7, and it always attempts to create/open the database in the IOS_LIBRARY_PATH folder. I'm not sure if this has been addressed in the latest release.
Thank you for your time, @ospfranco.

location will always override any value set by the C++ code, this is expected. Glad you solved it!


Fix typo & delete unnecessary spaces

typo: github -> GitHub
delete unnecessary spaces: As Markdown syntax, there was a large amount of half-width spaces that did not affect the display, so I deleted it

@changeworld : Thanks for your contribution! The author, @stevestein, has been notified to review your proposed change.

Verified editorial fix and layout in GitHub.


PubSub not working with remote subscriber

I have a pub+sub implemented in ZeroMQ.
The publisher is on machine A, the subscriber on machine B.
In the publisher I use this address: tcp://*:44557
In the subscriber I use:  tcp://remote-hostname:44557
Machine B receives messages from machine A.
I tried to do the same with mangos.
In the publisher, an address with a * doesn't work. I tried these instead: tcp://<IP_ADDRESS>:44557 and tcp://localhost:44557
In the subsciber I use the same address as in the ZeroMQ version.
I can subscribe locally, from machine A, but not from machine B.
On machine B, I get no errors, but no messages either.
Am I doing something wrong?

you can use <IP_ADDRESS> or omit the hostname. Using only local host on the publisher means that only subscribers on the same host will work.
Sent from my iPhone

On Jun 17, 2016, at 8:13 AM, Peter Kleiweg<EMAIL_ADDRESS>wrote:
I have a pub+sub implemented in ZeroMQ.
The publisher is on machine A, the subscriber on machine B.
In the publisher I use this address: tcp://*:44557
In the subscriber I use: tcp://remote-hostname:44557
Machine B receives messages from machine A.
I tried to do the same with mangos.
In the publisher, an address with a * doesn't work. I tried these instead: tcp://<IP_ADDRESS>:44557 and tcp://localhost:44557
In the subsciber I use the same address as in the ZeroMQ version.
I can subscribe locally, from machine A, but not from machine B.
On machine B, I get no errors, but no messages either.
Am I doing something wrong?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

OK, that works, mostly. But sometimes, when there is no subscriber, the publisher blocks. That is not desirable. I think I'll stick with ZeroMQ for the moment, and give mangos another try in a year or so.

It would be useful to have a test case demonstrating that the publisher blocks.  That should not occur.

Ok, I've got a repro for this; stay tuned.

I've fixed the blocking issue and added a test for it.  Thanks for reporting that problem.

With #222 I've added support for the wild card, and your other problems are now fixed.  Closing this report.


Fix address truncation if IPv6 address in HTTP_HOST

If HTTP_HOST contains an IPv6 address (eg [2001:db8::1]), the current implementation of Request::getHost() truncates this address after the first colon, yielding [2001 as the host instead of [2001:db8::1] (see #1325).
This PR fixes the Request::getHost() behaviour to check if an IPv6 address is given in HTTP_HOST and to split only on the colon after the IPv6 address.

Do we need the equivalent for Slim 3?

I'll check that...

Yes, but it's in \Slim\Http\Uri in Slim 3.
Will take care of it and create another PR.

I've merged this incase anyone needs this functionality in Slim 2. We probably won't do another release though unless a security fix is required.

I am inclined to consider this a critical bug and think there should be a patch release for it.

Fine with me. If we're going to do a new Slim2 patch release, we should probably review the other slim2 PRs and see if any of those are worth adding in too.

@akrabat I agree.

@akrabat @silentworks any news about this path release ?


Rebase onto Sui

We think the Sui storage model will be easier to implement on Solana than the mainline Move storage model. Let's attempt to rebase onto their tree.
@jcivlin Do you want to try this or should I?

I'm deep in dwarf riddle, plz go ahead. Let me know if you need help.

We think the Sui storage model will be easier to implement on Solana than the mainline Move storage model.  Let me know if you need help.

The state of sui move is discouraging.
Their Move codebase is part of the sui tree, and the Move subdirs only slightly resemble the upstream Move code organization:
https://github.com/MystenLabs/sui/tree/main/external-crates/move
The sui-move branch of the Move repo hasn't been updated for 9 months, and I'm guessing won't be updated again:
https://github.com/move-language/move/tree/sui-move
Mysten doesn't even have a fork of the move repo under their org, so it seems like they are just maintaining their fork in tree.

One way to tackle this would be to rebase onto the sui-move branch of the the move repo, to get mostly up to date with sui, then manually copy all our changes into the appropriate place in the sui tree.

Well, good news as that rebasing onto the sui-move branch of the move repo is not too hard. Here is a first try:
https://github.com/brson/move/tree/solana-sui-base
The tests run, but not all tests pass.

The IR test failures appear to mostly be because the compiler is emitting IR function definitions in a different order than on the main branch.

The sui compiler had a curious change that caused move-build to seemingly not work with bytecode dependencies. Applying this patch made those tests pass again:
+++ b/language/move-compiler/src/command_line/compiler.rs
@@ -598,6 +598,8 @@ fn generate_interface_files_for_deps(
     let interface_files_paths =
         generate_interface_files(deps, interface_files_dir_opt, module_to_named_address, true)?;
     deps.extend(interface_files_paths);
+    // Remove bytecode files
+    deps.retain(|p| !p.path.as_str().ends_with(MOVE_COMPILED_EXTENSION));
     Ok(())
 }

The sui compiler had a curious change that caused move-build to seemingly not work with bytecode dependencies. Applying this patch made those tests pass again:
+++ b/language/move-compiler/src/command_line/compiler.rs
@@ -598,6 +598,8 @@ fn generate_interface_files_for_deps(
     let interface_files_paths =
         generate_interface_files(deps, interface_files_dir_opt, module_to_named_address, true)?;
     deps.extend(interface_files_paths);
+    // Remove bytecode files
+    deps.retain(|p| !p.path.as_str().ends_with(MOVE_COMPILED_EXTENSION));
     Ok(())
 }

Can it be bc we are processing modules in a reverse order. I found this to be problematic for DI building and restoring the order returned by move compiler, see #397.

Can it be bc we are processing modules in a reverse order. I found this to be problematic for DI building and restoring the order returned by move compiler, see #397.

Doesn't seem to be related. I applied the patch here but didn't see any change in how move-build responded to bytecode dependencies.

Ok, this branch that is rebased onto the move/sui-move branch appears to pass all the tests it passed previously:
https://github.com/brson/move/tree/solana-sui-base
I have filed several new issues revealed during the rebase:

https://github.com/solana-labs/move/issues/399
https://github.com/solana-labs/move/issues/400
https://github.com/solana-labs/move/issues/398

Next step is to attempt to transplant all our changes on to the sui repo's copy of move, which has a completely different layout than the move repo.

Can it be bc we are processing modules in a reverse order. I found this to be problematic for DI building and restoring the order returned by move compiler, see #397.

Doesn't seem to be related. I applied the patch here but didn't see any change in how move-build responded to bytecode dependencies.

The patch controls the order of modules in the same file, so if you observe it in compilation of multiple files it may not help.

Update:
My previous attempt to rebase attempt failed, where I was trying to rebase onto the latest (but old) sui branch of move, then apply diffs to the sui codebase. The sui codebase has changed so much that the diffs were just unappliable.
I started a new attempt that just moves our files into the sui codebase one at a times, and it has been more successful.
My branch is here: https://github.com/brson/sui/tree/solana
Most of the tests pass now. The major outstanding problem is that sui removed from move-cli all support for alternative architectures, so none of our patches can be applied directly. I have started re-introducing multi-architecture support to move-cli, and once that works almost all tests should pass again.


Button hover state

Closes #139
This PR gives hover states to all buttons. Visually, hover states should be the same as focus states and they should not occur when a button is disabled.

Sorry is the hover state an underline at the moment or just the focus box?

Right now it's just the focus outline. I'm suggesting in my review that Will use the PlainButton we've already built with the underline styles, but I need to publish it to enable that to happen.

Good call, should probably add an underline. Thanks!

Cool. Looks like this is good to go for now. I'll open an issue to import PlainButton when that is available. Maybe it can be added when we do another audit of the site after alpha/beta testing.


add ACH's token LOGO

In MetaMask, the token ACH cannot add tokens directly through search, nor directly display the ACH logo. Please approve my application. thank you very much!

Does the code and content I submit meet the standards?
If the merge is successful, is it possible to add the ACH token by searching for ACH in MetaMask.

Can it be merged? Please tell me, thank you!

thinkbankcoin:master

Please use address in EIP-55 format
Regular SVG logo should be <5kB uploaded one have 200kB could you please upload smaller one?

Please use address in EIP-55 format
Regular SVG logo should be <5kB uploaded one have 200kB could you please upload smaller one?

thank you for your reply!
Can you give me a reference case for EIP-55?
I'm trying to make a logo smaller than 5KB.

Please use address in EIP-55 format
Regular SVG logo should be <5kB uploaded one have 200kB could you please upload smaller one?

The change of logo has been completed


consider adding an API for aegis sentinel to list secrets

viewing the values of a secret is a riskier operation than simply setting a secret to a workload.
And that would require stricter audit requirements.
Before starting working on it, it would be useful to add an option to restrict access to Aegis Sentinel API via an OIDC provider. -- that will also be useful when/if we want to move Sentinel out of Kubernetes too. (will create a task for that too)

requirements:

It should be secure and only reachable from Aegis sentinel
The user will need to provide a valid OIDC token that can be validated against the public key of an authorization server.
The well-known url of the authorization server should be preconfigured in Aegis Safe's deploymnet yaml.
the operation should be audit-logged (including the OIDC token details)
could either view per-workload, or all secrets of all workloads.

Update:
No need for an OIDC mandate; although it would be nice for auditing purposes, it does not provide any real security benefit.
So if the user has OIDC enabled, then they can use that; and if not, they can still view the secret value.
The operation can be done only from Aegis Sentinel, and in case of lack of an OIDC provider integration, Aegis Sentinel’s SVID is the identity.
OIDC and ability to view secrets are two separate concern; no need to mangle them.

update: maybe encrypt the values for added security, but then we will have to expose the encryption key to anyone who wants to list secrets; will cause more harm than good.
returning a base64 encoded version of the secrets will provide some obfuscation, but it’s impractical as well.
maybe a GET /sentinel/v1/secrets?reveal=true can be implemented
so, by default secret values will not be listed, and if the user knows what they are doing
they can add the reveal flag to list the secrets.
--
Adding the option to reveal secrets is less secure, but the convenience it provides is worth it.
we can make this feature disabled by default and make it configurable behind an environment variable. -- so for those who need the convenience, the option would be there.

update:

secrets will never be displayed to the operator as plaintext.
if someone want the secrets listed, they will have to provide a key public key to encrypt them first.

This is relatively involved.
Punting to v15.


InlineCompletions API bracket completion - range is not updated when brackets are added/removed

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.69
OS Version: Windows_NT x64 10.0.22000

Steps to Reproduce:
When the completion contains incomplete bracketPairs, the VS Code API corrects them, but the range is not updated so the tabbing behavior doesn't work as expected. Additionally, the grey text shown is also not shown accurately.
Example 1:
The code context is
React.useEffect(() => {
fetch("/api")
.then((res) => res.json())
})

In this GIF, the insertText provided is res.json()). When the completion is accepted using Tab, the () don't get accepted.
If the code on the line is .then((res) => res.|), the insertText is res.json()) and the cursor is marked by |, then the completion shows up as

Example 2:
A simpler case is when code on the line is React.useE, the completion shown is React.useEffect(() => {}). When the user hits Tab to accept, their cursor is taken between {}. If the insertText is { at this point, it will be closed by the API. But the range is not updated to match the already existing } and so it shows up as grey text.

cc @hediet

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.69.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Thanks for the issue and the PR! I'll get it in in the next release, as we already have feature-freeze and focus on fixing bugs in new features.

@hediet hmm should this be assigned to the July milestone since i see it is merged to main? And thus it will be part of the upcoming stable release in 10 days? Thanks

https://user-images.githubusercontent.com/29464607/181618429-5cdc87c0-a639-4db7-b90e-db7895f38b55.mov

The autocomplete text no longer has the parentheses, but the description does. Is it expected that they don't get completed @hediet ?

You have to try this with the intellicode extension. I suggest to get this validated by @juihanamshet1

@meganrogge Were you able to repro the bug you found with the Intellicode-Completions extension installed? I cannot repro it on my end.


Investigate node outputs (offloading outputs to reduce node status).

Summary
Support larger inputs and outputs.
Motivation
Because we use annotation to pass in inputs and out outputs, we are limited by the size of annotations and manifest (i.e. 1Mb). By storing these elsewhere, we circumvent this.
Proposal
How do you think this should be implemented?

Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

https://docs.google.com/document/d/1Y1I4CUmb2-OQMtsfYXGpY42GhnNyr9lBcUPnITwAXgw/edit#

Investigate complete.

https://docs.google.com/document/u/1/d/18hg6PTejp1knp5QTaCwP4j4gUTsRu4KDeKHs-4l9shs/edit?usp=drive_web&ouid=114615447895142998339


Queues should be sorted by their names in queues page

To get a consistent view of queues layout, it is better to have them sorted by queue names.

this is fixed by #11


PHP expansion is incorrect.

According to the wikipedia article, PHP was originally released as 'Personal Home Page Tools' and now stands for 'PHP: Hypertext Processor'.

cf. #6

Didn't see that, thanks!

np! thanks for contributing
On Sat, Jun 13, 2015 at 04:16 Vaibhav Sagar<EMAIL_ADDRESS>wrote:

Didn't see that, thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/BloombergMedia/whatiscode/issues/49#issuecomment-111686287
.


ShinyProxy Helm Chart

I wrote an Helm Chart that deploy Shinyproxy on Kubernetes. It's on early stage but works great (all contributions welcome).
https://github.com/remche/zero-to-shinyproxy
If it makes sens, it could be linked from here or documentation.

I wrote one too but haven't shared it yet.
Maybe there is getting to be enough users now that helm should be supported upstream?

Any update on the topic ?

I switched to remche's chart.

@rgarrigue the chart is still community maintained with the help of few users (including @kfox1111). Happy to see new contributors there ;)
OpenAnalytics supports a Kubernetes Operator for K8s deployment.

I've forked remche's chart and made some changes/additions, including improved secret handling and using an up-to-date image.
https://gitlab.com/devxy/helm/shinyproxy
Thank @remche for the initial work 👍

I've forked remche's chart and made some changes/additions, including improved secret handling and using an up-to-date image.
https://gitlab.com/devxy/helm/shinyproxy
Thank @remche for the initial work 👍

I do not have the time to work on this chart anymore, happy to see a new maintainer !
I will add a pointer and archive my repo. Thanks @pat-s !