macOS: problems with Java AWT::Robot and AWT::Event-Queue (window not displayed, hangs waiting for events to finish)

This might be related to https://github.com/jpype-project/jpype/issues/906
My findings are when trying to use SikuliX through JPype on macOS.
On Windows and Linux it seems to work as reported by other users.
Find the issue doc here: https://github.com/RaiMan/SikuliX1/issues/400
For my plans Python-to-SikuliX I will ignore JPype, until this problem area is fixed in Java.

Thanks.  This is definitively something in the path towards fixing it.
So the path forward on this is I need to go to the travel department and pickup a loner OSX laptop and set up a development.  Unfortunately, there few logistical problems with that plan.   First I am not allowed on site to get to travel to due to COVID 19.  Next I suspect travel is currently closed down due to COVID 19.  Second being December finding someone who knows how to resolve those issues means the soonest I will be able to work on this will be in January.

@Thrameos
If you have something that could be tested/evaluated in macOS meanwhile, feel free to come back and contact me directly.
Happy Christmas. I wish you all the best for 2021.

Unfortunately this is the sort of problem that I would need to do a fair amount of exploring.   It is only obvious in retrospect after you find a series of cases that succeed or fail that you can find the documentation that points to the source of the problem.

@Thrameos
I feel with you ;-)

Okay I vaguely recall seeing some information on this.  The problem is that Java and AppKit have two separate requirements.  Java wants to handle events on a separate event handler thread, but AppKit wants to handle all events on the Appkit main thread.  When you start Python, you are almost always running on the main thread (of Python) which may be the AppKit main thread.  Thus only that thread can handle events.
This runs into a serious problem.   You want to keep running on the Python thread, but then you can't service events.  To handle this broken situation you would need to transfer control and start running Python on a different thread and tell the main thread to service the events.
Even if the Python main is not the Appkit main, the appkit main thread is most certainly already started by Python when Java starts.  So now Java is going to start its event thread in a different thread than the current AppKit thread and well we are headed for another deadlock.
They gave some code to "help" with this issue, but if the Python main is already the Appkit main there is no real way to tell Python to continue execution starting from this line in the code for things like interactive programming, this is always going to be a weak point.  It is not clear that the Python main thread has to be the Appkit thread, but I don't know enough about the API to determine that.
https://wiki.openjdk.java.net/display/MacOSXPort/Java+vs.+AppKit+Threading+Manifesto
Unfortunately not having a Mac there isn't a lot a can do to develop a better solution and this weakness is likely to cause issues for the future.    We really need and expert to guide us on how to get this to work.

Not sure it this information helps.  It seems to be indicating that we need to add an enter and exit section to our JNI calls to work with AppKit.
http://<IP_ADDRESS>/downloads/MacOSX10.8.sdk/System/Library/Frameworks/JavaVM.framework/Frameworks/JavaNativeFoundation.framework/Versions/A/Headers/JNFJNI.h
There are only a handful of JNI incoming calls from Java.  The most notable being JProxy call back hook.  There are others on the factory hooks, but those are not very likely to be able to stall unless the user plugs something horrible into the class creation routines.  If someone wants to contribute by adding some of these blocks and seeing if it helps with the deadlock it would be appreciated.  I am not sure it is the right path, but perhaps it will help.

http://mirror.informatimago.com/next/developer.apple.com/technotes/tn2005/tn2147.html

It is important to understand that the JVM cannot be started from the native application's main thread if your Java code uses an AWT/Swing-based GUI; in such applications the main thread must be kept free for use by Cocoa's event loop. Both of the above examples abide by this rule: Listing 16 starts a CFRunLoop in main, which is used by the NSApplication instance that the AWT creates. Listing 17 responds to NSApplication's applicationWillFinishLaunching: delegate method, indicating that an NSApplication is already in place on the main thread. Starting an AWT application from the native launcher's main thread significantly affects performance and may produce unrecoverable errors. Listing 18 shows a paraphrased example of the most common error thrown...

Again not sure if this applies to our Python/Java model.   Assuming it does we would need to start Java in a different thread than main then attach the Pythons main thread as a daemon thread.  This is likely to cause issues with our shutdown model, though perhaps there is a way to handle it because if Python is a daemon thread it won't count toward the shutdown.

Very good findings.
I guess you hit the problem cause.
But this means IMHO, that the approach of JPype in macOS only works with Java stuff, that does not use any AWT/Event-Loop features. Hence JPype -> SikuliX will not work on macOS, until someone finds a solution based on the above mentioned evaluations (sorry, but I am not one of those someone's).
I will continue to watch the further development in this problem area of JPype.

Assuming this is actually is the issue, there are two approaches.

Structural requirements for OSX using JPype modules.   This is what is happening in the existing jpype/gui module.     But the downside is unless someone wants osx, they won't code it with the required style and after it is written making a switch would be costly.  The result is most JPype using projects that exercise AWT won't work.

Structural changes to JPype.  In this case rather that starting the JVM in the main thread, we have startJVM and shutdownJVM work with a C++ spawned thread (yes that means we need to create a thread using the OS specific commands as we need the thread to be able to live and arbitrary scope regardless of the state of Java or Python).   The startJVM would create the thread which calls the real start method, and waits for the start to complete to initialize resources.  It would then attach the thread as a daemon so that Python actions can continue even if the Java is terminated.  The jmain thread would just sleep until it receives a message to proceed to terminate.  Shutdown would then become much softer as it is just a message to jmain thread to start with the shutdown rather than a hard cut point.  In the OSX case, we would also try to create a second appmain thread so that there is no deadlocks between jmain and pymain threads.  This may cause weird side effects between qt/java on osx so a lot of testing is required.

I am going to assume that option 1 is a poor one and examine the changes that result from option 2.
The user visible changes required for the second option is

startJVM would have a keyword argument headless which would be false be default.   If headless is true then the osx would not try to spawn the appmain thread.
shutdownJVM would have a keyword argument block defaulting to true which tells whether the shutdown requires the action to complete before Python proceeds.   There is one danger at this point as it you proceed and the Python machine completes its shutdown sequence before Java completes its then we will segfault on any existing proxy objects.  The "atexit" for Python would need to wait for Java one to complete so we avoid the danger point.   Likely we require an additional internal "waitJVMshutdown" command so we ensure we checkpoint.

The other change is jpype/gui would need to be deprecated.  It was not documented and I am not aware of any users, but once we make this structure change it may interfere or confuse.
The consequences for existing JPype using projects would be minimal.  Some would require adding headless to continue operating on osx as before.  Others may have minor changes in the shutdown behavior to deal with the softer shutdown.   Though there are still projects having issue with our current shutdown so from that prospective it may make things better.  (I suspect projects that are still having issues have "attachToJVM" calls buried in them that is causing the JVM to stall on exit.)
I can likely make these structural changes without actually having access to an OSX machine, but there is little way can actually debug it enough to know if it fixes the osx issues until I gain access, so unless someone volunteers to be a guinea pig I should likely place this on the wishlist for now and start work once I can access an osx machine.
@marscher The proposed changes are structural in nature and likely have at least some consequences from the user prospective even if I keep it minimal.   If you have some direction on the path to take, it would be appreciated.   We have had a lot of traffic on OSX users here so I am guessing interest is relatively high.  But if you think I have overlooked something on the  user prospective, then I should adjust the plans.

@Thrameos
I could do tests with a dev version and even some debugging in the Python and Java area (I am using PyCharm and IDEA).
... but I am not familiar with the area C++/Apple native.
All the best.

Sure thing.   Right now I am just debating the priorities for this particular task relative to others.  My main large tasks appear to be

Implementation of the reverse bridge allowing Java to call Python
Extension of Java classes from within Python
Dealing with OSX issues

The order that I complete these tasks will have a large influence on the final product.   If I have the reverse bridge then how I accomplish the other tasks may be very different than if I proceed in the opposite order not to mention the potential time that a solution may be available.   The reverse bridge is the largest of the tasks in terms of scope, but it also simplifies all other tasks which complicates the decision process.   I will think this over and get back to you when I have defined a path.

@Thrameos
I agree and wish you all the best on the way to your targets.
Feel free, to delete this remark:
I know that using the alternative Python-Java bridge py4j works on macOS (I have a sleeping project that implements the SikuliX features in C-Python this way). I guess that the performance with JPype should be slightly better, but py4j can also be used over the net (different target machine).

Py4j is intended for a different audience than JPype.  It exists to for creating an RPC like connection between Python and Java.  I often encourage projects that require a transient transactional type connection rather than a highly integrated one to use Py4j.  Both approaches have their strong points and weak points.

Since I am one of the JPype users that would be interested in a solution for this macOS issue, I would like to let you know that in the last five years I was using SikuliX with Robot Framework with the single available solution of Remote Server and XML-RPC protocol. Since this method is slow, I had to start the server once before any test run, and close it after, although on web testing this is not the most important thing to do. The ideal solution is that all tests are independent of each others and there should be no need to start e.g. a remote server just to be able to use a certain library when needed.
For that reason I was lately proposing a new Python library (robotframework-sikulixlibrary) that is working great on Windows (also tested on Linux), much more advanced than with XML-RPC protocol so I am very happy to use it also in the future, and to suggest it also to other Robot Framework SikuliX users. For us, the other alternative would be e.g. image libraries built on top of pyautogui, but it seems these libraries are quite limited when compared with SikuliX :)

@adrian-evo
Looking into your JPype based implementation of robotframework-sikulixlibrary IMHO it would be no problem, to also implement the py4j bridge as an option for those who want to use it for whatever reason.
I will check, wether I am right with a fork of your project. It is a good possibility, to evaluate the differences between the two approaches with respect to performance and implementation aspects.
Wish you all the best and a healthy 2021.

@RaiMan
I agree that having the possibility to choose one of the options would be the best solution, since the two approaches could have different usage reasons, as mentioned also by @Thrameos, and as long as the implementation of the keywords library can be kept as simple as possible. So let's see what the final findings will be.
Have a safe and happy holiday season!

This one is still waiting for access to an OSX machine.   I believe the solution would be to spawn JVM in a separate thread and then use a message to kill it on shutdown rather than keeping the main JVM thread and main Python thread the same.   This may have interactions with the shutdown sequence.  For symmetry we would want to use this same path for windows, osx, and linux otherwise we may end up with different shutdown behavior on different systems.
This fix would require porting enough os specific threading libraries so that we can create a thread, signal it to terminate, and join it after.  We also may need to add a "gui" option which informs JPype that it should also launch an appkit thread.   Unfortunately, I can't really complete this work until I am able to replicate it locally.

This one is still waiting for access to an OSX machine.   I believe the solution would be to spawn JVM in a separate thread and then use a message to kill it on shutdown rather than keeping the main JVM thread and main Python thread the same.   This may have interactions with the shutdown sequence.  For symmetry we would want to use this same path for windows, osx, and linux otherwise we may end up with different shutdown behavior on different systems.
This fix would require porting enough os specific threading libraries so that we can create a thread, signal it to terminate, and join it after.  We also may need to add a "gui" option which informs JPype that it should also launch an appkit thread.   Unfortunately, I can't really complete this work until I am able to replicate it locally.


Bump to typescript version to 1.8.10

Hi @k-maru, I love to use your grunt module, but I had now problems with the old version of typescript you still have set as a dependency. It would be great if you could merge this pull request soon.

@k-maru seconded!

@k-maru  is possible to accept this request?


make the tags invisible and show the total tag instead

I do not want to see the tags. Instead, it is better to see the total selected tags.

I would like to have an option for this as well.

I had to do an ugly hack with limit=0 and some custom JS for the limit-text so native support would be nice, its crazy how there are no multi select dropdowns that dont natively and cleanly support no tags,

Hi @VCodepp
Are you talking about feature like this?

Or like this?

I've 'solved' this by setting the amount of selected items to show at 0 and css hiding the message that appears when there is nothing showing.

This is now available in 2.1.2 thanks to @akki-jat PR! 🎉

Hi, thank you for the wonderful feature!
I have checked many sites to implement this feature, but i couldn't find out how to set it.
If possible, could you kindly share us how we could list no tags and list "2 options selected"?
(Please kindly tell us in what options or code we should list to implement this feature)
sorry for taking you time.
& thank you for your support.

hi @rashearth,
creted small demo for it so you can play around with it.
Demo Link:
https://jsfiddle.net/akki_jat/pdvLz5bs/6/

Hi, akki-jat, Thank you so much for the support!
i understood, but it seems a bit different for what i have imagined.
in the Vue.js multiselect homepage(https://vue-multiselect.js.org/) example, it writes in plain text of "3options selected" as the picture below.
is it possible to work like this in plain text? this feature would fit the design of any kind of sites.
i have checked the source of the HP, but i could find the exact code for working this out.
sorry for taking you time, but it would be great if you could show us how to work this out.

Hi, @rashearth ,
Styles were coming because I added the classes you can remove the classes or even add your custom classes to give look as you want.
Take a look at updated link.
https://jsfiddle.net/akki_jat/prLu7zqt/9/

thanks alot! I got it working!
it took me so long, since i have been using the old version of vue multiselect, and couldnt make it work. but now i got it:)

Are you talking about feature like this?

How implement 1st image option ?

Hi @VCodepp
Are you talking about feature like this?

Or like this?

How to implement 1st image option?
Thanks


Use flow-typed for builtin types instead of storing them in flow itself

Some of us are unfortunately stuck on old versions of flow because of the dramatic effort it would take to bring dozens of interrelated private packages in our orgs up-to-date and fix the resulting new flow errors.  (I've been working to try to automate that process but there are still difficulties, like the defs packaged with Immutable.js not quite working with the latest version of flow.)
It becomes a significant problem when the builtin node module defs in an old version of flow are out of date.
If the type defs for builtin node modules were stored in flow-typed instead, it would enable us to upgrade the defs without having to upgrade flow (we might have to PR upgrades to the defs for an old flow version to flow-typed, but that would be better than nothing).

You can download the latest file and throw it in flow-typed/node.js

@aikar that's true...but would it actually override that defined in flow itself?


Really bad mistake

[Enter feedback here]
In this section:
To unregister your SQL Server VM from the resource provider with Azure CLI, use the **_New-AzSqlVM_**command. This will remove the SQL Server VM resource but will not delete the virtual machine.
It appears that the command: New-AzSqlVM should actually be: Remove-AzSqlVM as shown in the example below that description. It is a pretty huge mess up as MS mentions that a mistake in this area could potentially delete the entire VM, which may not be a user's intention.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 6f2e47a4-1781-8c55-c269-1946adbb46db
Version Independent ID: ed091689-e342-2661-8b3a-5be2ad164b3a
Content: Register with the SQL VM resource provider - SQL Server on Azure VM
Content Source: articles/azure-sql/virtual-machines/windows/sql-vm-resource-provider-register.md
Service: virtual-machines-sql
GitHub Login: @MashaMSFT
Microsoft Alias: mathoma

@paulmasonjuvare Thanks for the Feedback. We have updated the document changes will go live soon.

Hi @paulmasonjuvare , thanks for contacting Microsoft! Actually, the command Remove-AzSqlVM is the correct command to remove the sql virtual machines resource thereby unregistering your SQL Server VM from the SQL VM resource provider. It will not delete the underlying SQL Server virtual machine.
The typo is actually in telling you to use the New-AzSqlVM, which is incorrect.  It should tell you to use Remove-AzSqlVM instead.

@VikasPullagura-MSFT , can you process that change?
Thanks!
Masha from the SQL Docs team

Oh, my apologies, @paulmasonjuvare , I totally misread your original post. You're right, that should definitely be fixed! However, neither command (New-AzSqlVM or Remove-AzSQLVM) have any risk to deleting the virtual machine, so from that standpoint, the docs are okay. But you're right in bringing this to our attention, and this will be updated later today thanks to @VikasPullagura-MSFT .
Thanks!
Masha from the SQL Docs team


cargo: outdated 'as-slice' dependency

I was looking into duplicate/stale dependencies in one of my embedded projects, and it looks like some of those are coming from the fact that this crate uses an old as-slice 0.1 dependency instead of the latest 0.2 (in turn bringing in more duplicate/stale transitive dependencies).
Would it be possible to bump as-slice in the cargo manifest here? Additionally, those traits implementations seem to be re-exported by this crate, so I think a semver bump may be required too.

0.4.0 depends on as-slice 0.2.x

@japaric thanks a lot for the prompt update! :green_heart:


Transactions: Add specific labelling for Self Transfer

What does it mean ? Special icon / title for self transfer ? Or just "handle" self transfer tx ?

Yes I guess just handling and use a special title for it. Not sure about what the icon should be

IMHO self-transfer is a kind of "deposit", because technically the wallet "receives" something. Deposit icon seems OK ?


Add env var as admin password

This adds an environment variable LNBITS_ADMIN_LOGIN_KEY. This key can be entered on the wallet creation screen to make your account an admin.

The button shown in the screenshot is only visible if LNBITS_ADMIN_LOGIN_KEY is set and not an empty string.

I like it a lot. We'll be working on an optional admin extension UI in the next few weeks, so will be transposing the .envs into a db. I'll make sure to add this feature


Connection refused: You are not the owner of some DLC you use.

Whenever I try to join a truckersmp server, I get this error

Here is a list of all of the DLC's I own and use:

My operating system is Ubuntu 22.04 LTS and I am using the 5.15.0-46-generic kernel.

Recheck your DLCs at https://truckersmp.com/profile/settings


Conflicting peer dependencies

Steps to Reproduce

npm i @sentry/vue @sentry/capacitor

Result
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@sentry/vue
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@sentry/capacitor
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/@sentry/vue
npm ERR!   peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@sentry/capacitor
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /root/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2022-07-[26](https://singular-code.de/futureself/future.self-app/-/jobs/15825#L26)T10_18_57_868Z-debug-0.log

does it work if you specify the version of sentry/vue to 7.6.0?

I have noticed that the problem does not occur with Node v16.x, but with the latest version.

should work with<EMAIL_ADDRESS><EMAIL_ADDRESS>is latest

Closing since the dependency got updated.


.pdf export does not complete (stuck on loading symbol)

TImeline in question (<50 events). The same behaviour applies to the .png export.
According to the documentation:

Be patient, it could take up to 30 seconds to generate as this is a server side opertion.

However, no output is generated even after 3 minutes.

I'm awaiting the PDF / PNG Export!


Can't install (at least) on RedHat

OS: Oracle Linux 7.3 (RedHat 7)
Modules installed: yum groupinstall "Development Tools", yum install kernel-devel (and npm i -g node-gyp@latest only as superuser)
ERROR LOG:
$ npm i enmap

<EMAIL_ADDRESS>install /home/opc/node/Ryan/node_modules/better-sqlite3
prebuild-install || npm run build-release
prebuild-install WARN install /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /home/opc/node/Ryan/node_modules/better-sqlite3/build/Release/better_sqlite3.node)
<EMAIL_ADDRESS>build-release /home/opc/node/Ryan/node_modules/better-sqlite3
node-gyp rebuild --release
make: Entering directory /home/opc/node/Ryan/node_modules/better-sqlite3/build'   TOUCH b857c92884e9598d609f6be182a2595df7a8e00f.intermediate   ACTION deps_sqlite3_gyp_locate_sqlite3_target_extract_sqlite3 b857c92884e9598d609f6be182a2595df7a8e00f.intermediate   TOUCH Release/obj.target/deps/locate_sqlite3.stamp   CC(target) Release/obj.target/sqlite3/gen/sqlite3/sqlite3.o   AR(target) Release/obj.target/deps/sqlite3.a   COPY Release/sqlite3.a   CXX(target) Release/obj.target/better_sqlite3/src/better_sqlite3.o g++: error: unrecognized command line option ‘-std=c++14’ make: *** [Release/obj.target/better_sqlite3/src/better_sqlite3.o] Error 1 rm b857c92884e9598d609f6be182a2595df7a8e00f.intermediate make: Leaving directory /home/opc/node/Ryan/node_modules/better-sqlite3/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (events.js:315:20)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)
gyp ERR! System Linux 5.4.17-2036.104.5.el7uek.x86_64
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--release"
gyp ERR! cwd /home/opc/node/Ryan/node_modules/better-sqlite3
gyp ERR! node -v v14.16.0
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build-release: node-gyp rebuild --release
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build-release script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/opc/.npm/_logs/2021-04-06T12_51_25_409Z-debug.log
npm ERR! code ELIFECYCLE

Duplicate of #586 I think

For now I just can install versions under 7.1.0 where modules don't specify a newer version to use

There's something blocking newer installs (probably what @Prinzhorn mentioned).
I'll keep this issue opened because I don't know if GLIBC version is the really problem for this. Closing when this will be confirmed and/or issue has been solved. Thanks!

This seems related to #586 and https://github.com/JoshuaWise/better-sqlite3/issues/403

Closing this as a duplicate of https://github.com/JoshuaWise/better-sqlite3/issues/586


Doesn't support AVIF format

Describe the bug
Next image loader doesn't support avif format due to the use of the package image-size which doesn't support avif
Your minimal, reproducible example
None
Steps to reproduce
Add an <Image src="mum.avif" /> in a component which has a story.
Run Storybook
Crash with this stack trace:
ModuleBuildError: Module build failed (from ./node_modules/storybook-addon-next/dist/images/next-image-loader-stub.js):
TypeError: unsupported file type: undefined (file: undefined)
    at lookup (/Users/johann/Dev/lab/template/node_modules/image-size/dist/index.js:42:11)
    at imageSize (/Users/johann/Dev/lab/template/node_modules/image-size/dist/index.js:98:16)
    at Object.nextImageLoaderStub (/Users/johann/Dev/lab/template/node_modules/storybook-addon-next/dist/images/next-image-loader-stub.js:12:56)
    at processResult (/Users/johann/Dev/lab/template/node_modules/@storybook/builder-webpack5/node_modules/webpack/lib/NormalModule.js:758:19)
    at /Users/johann/Dev/lab/template/node_modules/@storybook/builder-webpack5/node_modules/webpack/lib/NormalModule.js:860:5
    at /Users/johann/Dev/lab/template/node_modules/@storybook/builder-webpack5/node_modules/loader-runner/lib/LoaderRunner.js:400:11
    at /Users/johann/Dev/lab/template/node_modules/@storybook/builder-webpack5/node_modules/loader-runner/lib/LoaderRunner.js:252:18
    at runSyncOrAsync (/Users/johann/Dev/lab/template/node_modules/@storybook/builder-webpack5/node_modules/loader-runner/lib/LoaderRunner.js:156:3)
    at iterateNormalLoaders (/Users/johann/Dev/lab/template/node_modules/@storybook/builder-webpack5/node_modules/loader-runner/lib/LoaderRunner.js:251:2)
    at /Users/johann/Dev/lab/template/node_modules/@storybook/builder-webpack5/node_modules/loader-runner/lib/LoaderRunner.js:224:4
    at /Users/johann/Dev/lab/template/node_modules/@storybook/builder-webpack5/node_modules/webpack/lib/NormalModule.js:834:15
    at Array.eval (eval at create (/Users/johann/Dev/lab/template/node_modules/@storybook/builder-webpack5/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:12:1)
    at runCallbacks (/Users/johann/Dev/lab/template/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:27:15)
    at /Users/johann/Dev/lab/template/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:200:4
    at /Users/johann/Dev/lab/template/node_modules/graceful-fs/graceful-fs.js:123:16
    at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read_file_context:68:3)

WARN Broken build, fix the error above.

Expected behavior
Support avif format
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform

OS: MacOS Monterey 12.6, M1 pro chip
Chrome

storybook-addon-next version
1.6.9
Additional context
Could be solved by using a package that supports avif format to get dimensions of images (e.g probe-image-size)

Regarding the upcoming release of storybook v7 and the accompanying framework api that replaces this addon. I'm switching this package into "keep the lights on" mode and directing everyone using this addon to switch to storybook's framework api.
Please report any issues you have with migrating though :)


Conflicting Intel Driver & Support Assistant packages

There are two manifests in this repository for the Intel Driver & Support Assistant, that differ only by the capitalisation of "a" in the "and". This seems unnecessary and makes installing one or the other unnecessarily difficult, as you need to (a) spot that the distinction is the capitalisation and (b) go hunting to remind yourself what the syntax is for the case-sensitive selection. One or the other should probably be deleted, or possibly they should be merged.
As best I can tell, this is entirely accidental. One was added in #1165 by @NathanBnm, the other in #1214 by @Reset12138.
I've no particular preference about which is preserved and which is maintained; the one from #1214 (IntelDriverandSupportAssistant, i.e. without the capital "A") specifies a more recent version, but as best I can tell they're both downloading the same installer. One has the argument /silent, the other /S /NORESTART, but that, the version and the installer hash seem to be the only substantive differences between the manifests.

I was the first to submit a PR, the second PR shouldn't have been merged. I even created a PR to add a notice about duplicates in the README to avoid this case.
Every word should be capitalized in the identifier so the correct identifier is the one with "And".
Moreover using /silent as silent argument does not work (I tried myself). The required silent arguments are /S /NORESTART.
I partially based my PR on the chocolately package to use the same identifier and app moniker.

@NathanBnm or @me-and  feel free to put a PR in to delete the second one if you feel the original from your PR #1165 is correct.

This should now be resolved.

This should now be resolved.


Stick to c_vec 1.0 and remove feature(unique)

@GuillaumeGomez did you miss this one? =)

I totally did... Thanks !


Compiling errors

I'm having problems when compiling the slave board.
I to go to config.h and define slave, and the errors i get are related to some identifiers being undefined because only being defined if master.
Or,
Are we supposed to use master in both boards?

I use the same code in both boards.
I didn't think I still had and MASTER/SLAVE defines in there.  I guess I need to check, and eliminate them.
So.. leave MASTER defined and load up both modules with the same code.

I use the same code in both boards.
I didn't think I still had and MASTER/SLAVE defines in there.  I guess I need to check, and eliminate them.
So.. leave MASTER defined and load up both modules with the same code.

Thanks for the reply, then it makes a lot more sense.
Btw, since you use the same firmware on both, I assume it doesn't matter in which board you connect the Bluetooth module.
Or is it advised to be used on one of the boards in specific?

Thanks for the reply, then it makes a lot more sense.
Btw, since you use the same firmware on both, I assume it doesn't matter in which board you connect the Bluetooth module.
Or is it advised to be used on one of the boards in specific?

Since the code that receives a drive command will use the first speed for its motor and send the second speed to the other side.   One of these will be negated so if you put the Bluetooth on the slave, the speeds will be assigned to the wrong sides, so the board will run in the opposite direction.

Since the code that receives a drive command will use the first speed for its motor and send the second speed to the other side.   One of these will be negated so if you put the Bluetooth on the slave, the speeds will be assigned to the wrong sides, so the board will run in the opposite direction.


Allow separators to be omitted from lists.

Enables newlines to be used in place of separators in some lists.

@swift-ci please test source compatibility

@swift-ci please test source compatibility

@swift-ci please test source compatibility

@swift-ci please test source compatibility

@swift-ci please test source compatibility

@nate-chandler I wrote some tests for the IDE side; it looks like everything I've thought about is already working, which is great.  I pushed a omit-comma-ide-tests branch to my swift fork: https://github.com/benlangmuir/swift/tree/omit-comma-ide-tests . You could probably just cherry-pick the two test commits at the top of that branch into this PR.

@benlangmuir Fantastic! Will do.

@benlangmuir Okay, the commits are cherry-picked to
https://github.com/apple/swift/pull/22714/commits/cf8c2f6ea9252ae139fb048942467e2e9ec6b874 and
https://github.com/apple/swift/pull/22714/commits/97cfe0eb01f8118717a7794e41d92fabfd17e94a .

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 28f1b7ce018ca5bffa6943ca78c1c5bafa800b78

Build failed
Swift Test OS X Platform
Git Sha - 28f1b7ce018ca5bffa6943ca78c1c5bafa800b78

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 97cfe0eb01f8118717a7794e41d92fabfd17e94a

Build failed
Swift Test OS X Platform
Git Sha - 97cfe0eb01f8118717a7794e41d92fabfd17e94a

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 8566d447e3545586c1aeb20a4ea8e9375ec87cb7

Build failed
Swift Test OS X Platform
Git Sha - 8566d447e3545586c1aeb20a4ea8e9375ec87cb7

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 11ffe3138759dbaadc802de834218ce7a0f236ca

Build failed
Swift Test OS X Platform
Git Sha - 11ffe3138759dbaadc802de834218ce7a0f236ca

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - efe3a379f89dabd3287b9fbfbfa5f012435522c4

Build failed
Swift Test OS X Platform
Git Sha - efe3a379f89dabd3287b9fbfbfa5f012435522c4

@swift-ci please test source compatibility

@swift-ci please test source compatibility

@swift-ci please test source compatibility

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 6b393ae39a496a37da9891817e0073cba20cfdc4

Build failed
Swift Test OS X Platform
Git Sha - 6b393ae39a496a37da9891817e0073cba20cfdc4

@swift-ci Please test Linux platform

Build failed
Swift Test Linux Platform
Git Sha - da4873b8b13b29aa2673dd818fa2a3784b0296ae

@swift-ci Please clean test Linux platform

@swift-ci please test

@swift-ci please test source compatibility

Build failed
Swift Test Linux Platform
Git Sha - da4873b8b13b29aa2673dd818fa2a3784b0296ae

Build failed
Swift Test OS X Platform
Git Sha - acdd16f7d16d1d2223758b09f5327175f1c3f8d6

@swift-ci Please clean test Linux platform

Build failed
Swift Test Linux Platform
Git Sha - acdd16f7d16d1d2223758b09f5327175f1c3f8d6

@swift-ci please clean test

Build failed
Swift Test Linux Platform
Git Sha - acdd16f7d16d1d2223758b09f5327175f1c3f8d6

Build failed
Swift Test OS X Platform
Git Sha - acdd16f7d16d1d2223758b09f5327175f1c3f8d6

@swift-ci please clean test

Build failed
Swift Test Linux Platform
Git Sha - faecb8d5f15a3421f661bd606158d0394dbb19be

Build failed
Swift Test OS X Platform
Git Sha - faecb8d5f15a3421f661bd606158d0394dbb19be

@swift-ci please test source compatibility

@swift-ci build toolchain

@swift-ci clean build toolchain

@swift-ci clean build

Toolchains:
macOS: https://ci.swift.org/job/swift-PR-toolchain-osx/272/artifact/branch-master/swift-PR-22714-272-osx.tar.gz
https://ci.swift.org/job/swift-PR-toolchain-Linux/211/artifact/branch-master/swift-PR-22714-211-ubuntu16.04.tar.gz

I tried the toolchain and it doesn't seem to allow me eliding commas in parameter lists

I tried the toolchain and it doesn't seem to allow me eliding commas in parameter lists

Hi @hartbit,
Thanks for the report!  What you're seeing is intentional behavior.  The proposed change allows comma elision only in expression lists.
func foo(
    _ a: Int, // required here
    _ b: Int
)
    -> Int
{
    return a + b
}

let s = foo(
    1 // optional here
    2
)

@swift-ci please build toolcahin

Trying to build a toolchain with this feature and static subscripts.


Plugin: cross-service document population

A common feature for api gateways sitting in front of microservices, as kong is for us, is to handle aggregating data from multiple sources to return to the client in one API call.
I wonder if there's a generic way one could describe document populations so that kong can do so automatically.
For example, you might use the following json to describe a cross-service population for the orders service
{"product_id"<EMAIL_ADDRESS>
This would go through all product_id in the orders response if it's an array, or take the product_id key if it's a map, and send it to /products (copying all request headers so it looks like it's made by the same user), joining the two responses on orders.product_id=response.products.id
Obviously nuances need to be works out in the design like handling more edge cases, allowing custom manipulation of the response data, and handling different structures (like nested arrays or nested objects or arrays nested within objects) but it'd be quite valuable for us. For the time being we're just doing the joins at the service level but they should really be handled by the gateway to keep everything clean.

have you look at this one: https://github.com/Mashape/kong/issues/155

Closing since it duplicates an already opened issue.


fix Fix mem control in local exchanger (#38885)

Proposed changes
If a block (>128M) is dequeue by local exchange source operator and it is the last block, both of source operators and sink operators will be hang. This PR fixed it.
pick #38885

Proposed changes
Issue Number: close #xxx

run buildall


[UI] Closes #66: Handle orientation change by resizing the content

@timotiusnc

With this patch and the one before this, I will release v1.2.1


Looking for help with some issues

Leave comments

Hi! Which issues are you looking for help with? Or are you interested in helping with some issues?


operator deletes all running jobs whenever the relevant scaledjob object gets updated, and recreates them based on the new scaledjob spec.

Report
on version 2.2, whenever  a scaledjob object got updated, the operator used to create only new jobs with the latest changes -  leaving running jobs that were created by the older version of the scaledjob object to finish gracefully.
on version 2.4, the operator deletes all running jobs whenever the scaledjob objects gets updated.
this behaviour is very problematic since its causing termination of running jobs on each update.
Expected Behavior
rollout mechanism should be just like it was on version 2.2.
one of the main reasons to use scale jobs and not deployments is to avoid terminating long running operations in the middle of the run.
Actual Behavior
on version 2.4, the operator deletes all running jobs whenever the scaledjob objects gets updated.
Steps to Reproduce the Problem
reproduced on vanilla k8s cluster on on kind.

install kind

https://kind.sigs.k8s.io/docs/user/quick-start/#installation

create new cluster

kind create cluster --name test-keda

install keda on the new cluster

kubectl apply -f https://github.com/kedacore/keda/releases/download/v2.4.0/keda-2.4.0.yaml

deploy prometheus

helm --namespace keda install prom prometheus-community/prometheus

configure a scaled job to use the local prometheus

  triggers:
  - metadata:
      metricName: test
      query: vector(1)
      serverAddress: http://prom-prometheus-server
      threshold: "1"
    type: prometheus

update the image tag the scaledjob is using.
all jobs that were already running. will get terminated

Logs from KEDA operator
2021-09-12T14:41:55.057Z	INFO	controllers.ScaledJob	Reconciling ScaledJob	{"ScaledJob.Namespace": "default", "ScaledJob.Name": "sj-test"}
2021-09-12T14:41:55.057Z	INFO	controllers.ScaledJob	**Deleting jobs owned by the previous version of the scaledJob**	{"ScaledJob.Namespace": "default", "ScaledJob.Name": "sj-test", "Number of jobs to delete": 50461}
2021-09-12T14:41:55.262Z	INFO	controllers.ScaledJob	Initializing Scaling logic according to ScaledJob Specification	{"ScaledJob.Namespace": "default", "ScaledJob.Name": "sj-test"}

KEDA Version
2.4.0
Kubernetes Version
1.19
Platform
Any
Scaler Details
prometheus
Anything else?
this behaviour seems pretty similar to this issue from keda v1:
https://github.com/kedacore/keda/issues/1021

@zroubalik suggested that this pr might be relevant to this change 2.2-> 2.4
https://github.com/kedacore/keda/pull/1970
maybe you guys are familiar with this topic? @TsuyoshiUshio @tomkerkhove

worth mentioning that on v2.2 log looks the same "Deleting jobs owned by the previous version of the scaledJob"
but jobs are not being deleted

i did some debugging and found a few issues with this function:

over here controller is trying to fetch the number of jobs it needs to delete. it looks like Size doesn't work that way. i noticed that on version 2.2 it always returns 8 no matter how many jobs exists (line 171):

logger.Info("Deleting jobs owned by the previous version of the scaledJob", "Number of jobs to delete", jobs.Size())

on version 2.4, number seems to be weird(50363,21953,39908 - doesn't correlates with the number of running jobs in any way) but when there are no jobs, running jobs.Size returns 8. it means that on version 2.2 it is not deleting the jobs cause it Is not fetching them correctly.
on this line condition is always true since it is not really checking the number of jobs as expected (when 0 jobs running jobs.Size is 8).
might be related to this line but im totally not sure.
reference to the Size implementation
anyways, i think the main reason to use scaled job and not scaled object is to avoid terminating running pods in the middle of their work. therefore, im not really sure why we need this function at all - "Deleting jobs owned by the previous version of the scaledJob" but it is just my opinion :)
to enjoy both worlds,  making it configurable like @TsuyoshiUshio suggested will be great, or remove it if theres a consensus about it.
thanks a lot for helping with this one guys!

Thanks for the information @etamarw ! @TsuyoshiUshio I don't recall the context of that, it has been implemented way too loong ago and not by me :)
I agree with suggested approach, to make this configurable. @etamarw are you willing to give it a try? Since you have already started with the analysis?

ill try to dive it a try.
i hope its a good first issue ;)

Fixed in #2164


Problems Issue with Zabbix 7.0 beta 2

When querying Problems, we get an Invalid parameter error.

Log Line during the error:
logger=plugin.alexanderzobnin-zabbix-datasource t=2024-04-04T21:18:06.90846898+03:00 level=error msg="Zabbix API request error" error="Invalid params. Invalid parameter "/output/2": value must be one of "proxyid", "name", "operating_mode", "description", "allowed_addresses", "address", "port", "tls_connect", "tls_accept", "tls_issuer", "tls_subject", "custom_timeouts", "timeout_zabbix_agent", "timeout_simple_check", "timeout_snmp_agent", "timeout_external_check", "timeout_db_monitor", "timeout_http_agent", "timeout_ssh_agent", "timeout_telnet_agent", "timeout_script", "lastaccess", "version", "compatibility"."
Software versions

Grafana
Zabbix
Grafana-Zabbix Plugin

10.4.1
7.0.0 beta 2
4.4.6

Will try to check the Zabbix documentation for API changes of Problems on Zabbix v.7.0.0
Also note, this issue is happening from alpha versions of Zabbix v.7.0.0

Changes of Zabbix API for problems in v.7.0.0:
https://www.zabbix.com/documentation/devel/en/manual/api/changes#problem

Hey @christos-diamantis thanks for opening this issue. We didn't add support for version 7 yet. We are tracking that in this issue so I'm going to close this.

I have the same problem.
Grafana 9.3.6
Grafana Plugin 4.5.2
Zabbix 7.03


[Twig] CVA - Rework implementation + documentation

Q
A

Bug fix?
no

New feature?
no

Issues
..

License
MIT

Try another implementation + add some tests.
Updated/added a lot of documentation in the CVA class.
All tests are green but i'm not 100% sure this made no change at all :|
@WebMamba  I let you decide what you want to do with it (i needed a class to test some things :) ) .. really open to any choice :)
@kbond that does not include your modifications i think :|

Thanks Simon.


DeflateDecoder fails with "corrupt deflate stream"

I am trying to inflate git object (e.g. commit) files, but DeflateDecoder is giving an error. I am using version 1.0.16 of the crate, and have tried the crate with and without the zlib feature. Here is a sample program:
use std::io::Read;
use std::fs::File;
use flate2::read::DeflateDecoder;

fn main() {
  let file = File::open(".git/objects/28/431a4e1669823d25d81292f98c9e9717d7000d").unwrap();
  let mut inflate = DeflateDecoder::new(file);
  inflate.read(&mut [0]).unwrap(); // I've also tried inflate.read_to_string(), and the file is valid UTF-8
}

inflate.read() results in the following error, which causes a panic:
Custom { kind: InvalidInput, error: "corrupt deflate stream" }

I verified using Node.js that the file is a valid deflate stream:
const fs = require('fs')
const zlib = require('zlib')

fs.createReadStream('.git/objects/28/431a4e1669823d25d81292f98c9e9717d7000d')
  .pipe(zlib.createInflate())
  .pipe(process.stdout)

The contents of the object file are:
00000000: 78 01 9d 8e 51 6e 02 31 0c 05 f9 ce 29 7c 01 90  x...Qn.1....)|..
00000010: 43 e2 6c 2c 55 55 a5 1e a1 e2 00 de d8 81 15 84  C.l,UU..........
00000020: 5d 2d 41 5c bf 4b 8f d0 cf 79 d2 8c 5e 99 5b 9b  ]-A\.K...y..^.[.
00000030: 3a 1c 23 ed fa 6a 06 c2 9a 0b 79 31 53 1f 99 8c  :.#..j....y1S...
00000040: a8 7a 1e 51 22 ea 18 29 66 4b 35 73 21 76 8b ac  .z.Q"..)fK5s!v..
00000050: 76 ef c0 d5 52 d6 41 23 27 4d 55 31 04 f2 a9 e2  v...R.A#'MU1....
00000060: 18 0c cb 26 96 63 e0 2a 31 93 93 67 bf cc 2b 7c  ...&.c.*1..g..+|
00000070: cb cd 46 f8 91 bb da 0a 1f e5 4d 87 c7 1f 7d 9d  ..F.......M...}.
00000080: 9b 4c b7 43 99 db 27 78 62 1c 86 1c 38 c0 1e 23  .L.C..'xb...8..#
00000090: a2 db d6 ed 66 df 9c 7f 06 dc 69 51 e9 06 af e9  ....f.....iQ....
000000a0: 3a ed cf d2 0c 16 e9 97 87 fb 05 d2 11 4e 2f     :............N/

Am I using the crate incorrectly, or is there a possible issue with inflation?

I think you want to be using ZlibDecoder, it looks like the data has a zlib header. DeflateDecoder is for data without a zlib header.

Yup, that was it. I had been using inflateInit() from zlib in C, so I wasn't aware it was a separate format. I wonder if there's any way to infer that automatically like Node.js seems to?


The so called environment concept is redundant.

For example, instead this:

We can input expressions like that below:

With the power of auto-complete, this should be more intuitive and quicker.
What's more, the current predefined expressions in default_env.gd is tedious:

We can split these functions into several parts instead all huddled together.

well, how do you make this auto-complete?

Please avoid such design mistakes in the future.


Consider replacing KOS with Softspoken

If you read SoftSpokenOT: Communication--Computation Tradeoffs in OT Extension, we learn the KOS is deprecated. Softspoken OT is considered more secure and requires one less back and forth.

I don't see it deprecated but we had a task to add Softspoken OT as thats what the threshold BBS+ paper recommended.

The authors of DKLS "Note for DKLs19 + DKLs18 with Proactive Key Refresh (2019/1328): uses the KOS OT-extension protocol (2015/546), which we consider to be depricated (see 2022/192)."

I have looked in the 3 papers you mentioned and I don't find that statement. Can you please share the link you are reading from?

It's not a paper it's the authors website
http://dkls.info

Thanks.


packagegroup-wpewebkit-depends-video: Add libvpx dependency

... required for -DENABLE_VIDEO=ON.
Reference in the upstream Changelog:
    2018-04-05  Alejandro G. Castro<EMAIL_ADDRESS>
        [GTK] Add CMake package search for vpx and libevent libraries
        https://bugs.webkit.org/show_bug.cgi?id=184257

        Reviewed by Michael Catanzaro.

        Add new cmake search files for libevent, vpx and alsa-lib, this
        makes a cleaner detection of the libraries.

        * CMakeLists.txt: Use the new cmake find files to detect the
        package and add a better error message when the library is not
        there.
        * Source/cmake/FindAlsaLib.cmake: Added.
        * Source/cmake/FindLibEvent.cmake: Added.
        * Source/cmake/FindVpx.cmake: Added.

... required for -DENABLE_VIDEO=ON.

This is required for USE_LIBWEBRTC, not for ENABLE_VIDEO.
Check: https://trac.webkit.org/r230297

... it as activated by enable_video flag in any case.
On Sat, Jun 6, 2020, 13:55 Carlos Alberto Lopez Perez <
<EMAIL_ADDRESS>wrote:

... required for -DENABLE_VIDEO=ON.
This is required for USE_LIBWEBRTC, not for ENABLE_VIDEO.
Check: https://trac.webkit.org/r230297
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Igalia/meta-webkit/pull/187#issuecomment-640047808,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC4ABX3WPAC5VB2RGSIR43RVIVC3ANCNFSM4NVZ2QFQ
.

Carlos is right though. <video> it doesn't mandate specific codecs. WebRTC does.

MR not needed. Dependency is already included in packagegroup-wpewebkit-depends-alternative.


All of my apps have disappeared from Amplify

Before opening, please confirm:

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

App Id
d280uf4ztky835 (and others)
Region
us-east-1
Amplify Console feature
Not applicable
Describe the bug
Literally all of my Amplify apps have disappeared from the console. When I create a new app, I get an error message that says App with id: <APP-ID> not found.
I have tried the following locally:
amplify status && amplify init && amplify pull && amplify push
It hasn't worked. I get differing errors each time I try to push, the latest being this:
UPDATE_FAILED      rOutputLambdaTriggerFunction AWS::CloudFormation::Stack Thu Jan 27 2022 13:37:45 GMT-0500 (Eastern Standard Time) Stack:arn:aws:cloudformation:us-east-1:767995013239:stack/amplify-sonxsplash-dev-212614-videosonxOnePagerVod-533E8D-rOutputLambdaTriggerFunction-D1S3IEAM8NG4/b3f9f3a0-4242-11ec-bcdb-0a7663231551 is in DELETE_COMPLETE state and can not be updated.
UPDATE_FAILED      rInputLambdaTriggerFunction  AWS::CloudFormation::Stack Thu Jan 27 2022 13:37:46 GMT-0500 (Eastern Standard Time) Resource update cancelled

The wierdest thing is that the apps are actually still there, and they still build when I push and merge changes to CodeCommit (I know this because I changed some copy in the repo, pushed to CodeCommit and merged to live, and it updated on my live site), but I just can't see or manage the apps in Amplify.
Expected behavior
Being able to see my apps
Reproduction steps

Go to Amplify in the AWS Console.
Cry.

Build Settings
Autodetected (React, Gatsby)

Additional information
No response

Just a quick update, I've managed to successfully run amplify push on one of my apps, after deleting the stack and associated resources and re-running amplify init, but the app is still not showing in my dashboard. I'm now absolutely stumped, it feels like the dashboard and my actual account state are not in sync.

Hi @lewisdonovan 👋🏽 thanks for raising this issue. Can you make sure that you're looking in the correct AWS region? If your console is set to a different region from where the apps are actually deployed then you won't be able to see them.

Hi @hloriana, yes I have double checked the region and have also changed and changed back to the correct region. The apps are still not displaying.

Okay thank you for checking we are investigating this internally and will get back to you with more information.

@lewisdonovan can you confirm that you're able to see your apps now?

@hloriana yes, thanks so much! Do we know what the issue was? Want to avoid this happening again in future, so would be good to know if it's anything our end. Thank you.

Hi @hloriana, I'm experiencing the same issue.
appid - d1u56ep7p49azn
aws amplify list-apps --region us-east-1 returns
{
"apps": []
}
The app is up, running, and connected to my CodeCommit repo, although, the app isn't displaying in the console. The app was created in the east-1 region and I've checked there and in all other regions and no dice.

@lewisdonovan this was not an issue on your end. @ElyYonce are you still running into this problem?


consider light theme?

Yeah will give an option in the next update to switch themes. Thanks for your input

Hey the update will be rolling out soon. Thanks a lot!


Syntax error for schema administrator

sf_create_obj schema commands generate the following grant for the schema ADM role:
GRANT CREATE TABLE IN SCHEMA MY_DB.MY_SCHEMA TO ROLE _SC_MY_DB_MY_SCHEMA_ADM_AR;
instead of
GRANT CREATE TABLE ON SCHEMA MY_DB.MY_SCHEMA TO ROLE _SC_MY_DB_MY_SCHEMA_ADM_AR;
same applies to all GRANT CREATE statements.

I've fixed the issue in main.


Allow JDBC based connector to define session properties

Allow JDBC based connector to define session properties

@kokosing this is already provided by https://github.com/prestosql/presto/pull/1148

@findepi it was also provided with https://github.com/prestosql/presto/pull/1105 (Allow JDBC based connector to define session properties)

@findepi it was also provided with #1105 (Allow JDBC based connector to define session properties)

oh, i missed that!

what's worse, i see now i've reviewed that code 😉

😆


production build fixes

refs https://github.com/Alfresco/alfresco-ng2-components/issues/1693

enable minification (UglifyJsPlugin), requires alfresco-js-api 1.2.1
to be released
add missing alfresco-js-api to the vendors
add missing 3D viewer related libs to the vendors (fixes issue with
app bundle having duplicates)

Codecov Report

Merging #73 into development will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           development      #73   +/-   ##
============================================
  Coverage        93.37%   93.37%
============================================
  Files                1        1
  Lines              151      151
  Branches            12       12
============================================
  Hits               141      141
  Misses              10       10

Continue to review full report at Codecov.

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


fix: push notification prompt on new onboarding

The type of this PR is: fix
Description
Prompt for push notification permissions after new onboarding.

Adds a new method in our native modules that uses the same logic as our old login push prompt
Renames the direct permission request used elsewhere

Screenshots
https://user-images.githubusercontent.com/49686530/137024982-4876d8cb-f1a0-40ae-bd8e-9ec92794d980.mp4
PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests/stories for my changes, or my changes don't require testing/stories, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a changelog entry below or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Prompt for push permissions after new onboarding - Brian

Android user-facing changes

Dev changes

#squahongreen


Feat/data avail

Feat: Common DA Trait
Issue #983
This PR aims to provide a common interface to integrate the following DA implementations:

Avail
Celestia
Ethereum

The goal is to have a generic Data Availability client (da_client) which can be Avail, Celestia or Ethereum.
The da_client implements the new trait DataAvailability and expose the following methods:
pub trait DataAvailability {
    fn new(args: &Vec<String>) -> Result<Self>
    fn validate_args(args: &Vec<String>) -> Result<DAArgs>
    fn format_state_diff(&self, state_diff: &[U256]) -> Result<DAInput>;
    async fn publish_data(&self, da_input: &DAInput) -> Result<DAOutput>;
    async fn verify_inclusion(&self, da_input: &DAInput, da_output: &DAOutput) -> Result<()>;
}

It also introduce some new types / enums:
enum DAType {
    Avail,
    Celestia,
    Ethereum,
}

pub enum DAArgs {
    Avail { ... },
    Celestia { ... },
    Ethereum { ... },
}

pub enum DAInput {
    Avail(BoundedVec<u8>),
    Celestia(Blob),
    Ethereum(Vec<U256>),
}

pub enum DAOutput {
    Avail { block_hash: H256 },
    Celestia { submitted_height: u64 },
    Ethereum,
}

There is then a common function to publish the state and verify inclusion.
Note: Ethereum is still ongoing.
To have more insight on the underlying process, you can take a look here:

PR #777
PR #967

Summary of Changes

Component
Change

CLI
New optional flags in ExtendedRunCommand: da-config-path for the DA config file

Service
state_diff notifications, push state_diff to the selected DA and verify that the state_diff output is included in the correct place.

Configuration file
When launching the node you can specify the path for the da-config-path, eg. --da-config ../da-config
An example is provided below for each type of DA.
Launch the node with DA
Launch with Avail
da-config local
da-type=Avail
ws_endpoint=ws://<IP_ADDRESS>:9945
app_id=0
avail_seed=//Alice

You can find instruction to launch the Avail node. TLDR:
git clone https://github.com/availproject/avail
cd avail
cargo run --release -- --dev --tmp --rpc-port 9934 --ws-port 9945 --port 30334

da-config testnet
da-type=Avail
ws_endpoint=wss://kate.avail.tools/ws
app_id=0
avail_seed=<SEED_OR_PK_WITH_AVAIL_TOKENS>

Launch with Celestia
Set up and run a Celestia light node
Requires the installation of the celestia CLI tool (available here). Once you have that set up, run the following:
celestia light start --core.ip consensus-full-arabica-9.celestia-arabica.com --gateway.deprecated-endpoints --gateway --gateway.addr <IP_ADDRESS> --gateway.port 26659 --p2p.network arabica-9

Next, we need to generate a JWT to access our light node:
celestia light auth admin --p2p.network arabica-9

da-config local
da-type=Celestia
http_endpoint=http://<IP_ADDRESS>:26659
ws_endpoint=ws://<IP_ADDRESS>:26659
auth_token=<GENERATED_JWT>
namespace=Madara

Launch with Ethereum
WIP
Launch Madara node
cargo run --release -- --dev --tmp --da-config-path ../da-config
Run Tests
Tests for Avail and Celestia are ignored by default since they require a running local node / light client of each DA Provider.
To run those tests, make sure you have one or both DA running in the background and use this command:
cargo test -- --ignored
Pull Request type
Please add the labels corresponding to the type of changes your PR introduces:

[X] Feature

What is the current behavior?
No concept of proving the state transition
Resolves: #693
Does this introduce a breaking change?
Yes
Users need to remove their local database as a new column is initialized.

logic stripped and used in #1021


upgrade controller tools to 0.14 to avoid nil ptr deref

I hit this issue on the dev machine. The controller tools panic when generating the files. Upgrading controller tools fix the issue.
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
        panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x0 pc=0x101050bc0]

> go version
go version go1.22.0 linux/amd64

Not sure if this would impact production environment / is it necessary to do this upgrade now? Anyways, I'm just testing it out in my own environment so it's fine if we decide not to upgrade.
And I'm new to k8s so not sure if all these yaml files should be included in this pull request or not. Thanks for reviews!

is it ok that controller-tools v0.14.0 depends on k8s 1.29 but autoscaling requires 1.25?
from controller-tool go.mod
	k8s.io/api v0.29.0
	k8s.io/apiextensions-apiserver v0.29.0
	k8s.io/apimachinery v0.29.0

maybe not..? and probably that's why i cannot spin up any VM for the past hour 🤣 maybe i'll set up a user-local go compiler on devserver instead.

In general, the issue we have is that the scheduler must have a version equal or -1 from the k8s API server, otherwise it'll just silently not work. And because everything has the same go.mod, every component will in practice use the same k8s version as the scheduler. Our local dev, staging, and prod clusters are all 1.25, so while in theory it's possible for us to use k8s 1.25 deps with code generated by controller-tools for 1.29, IMO it's likely to have hard-to-debug errors.

Let's keep this pull request on hold and don't merge. TL;DR, if anyone working on autoscaling will need to use go <= 1.21.

Blocked on k8s upgrade


Disable cache for matrix boxes

(Temporary)
The obs matrix box cache is not getting invalidated upon update of associated records, as pointed out by Joe in #1907. We will need to alter the caching strategy for these, implementing "Russian Doll" fragment caching for the nested records.

Name
Location
User
RssLog?

coverage: 94.523% (-0.01%) from 94.536%
when pulling 55ab4f30caa0ae118aeb52bb775599ace390ab7f on nimmo-russian-doll
into d61c187f2a39a8f46d304ce8595b36aff831246e on main.


suggestion demo

suggetsion demo filter contain insted of starts with

@oblomov-dev
not really sure what those errors are, i changed demo 2 and 60 only

Mhh it runs very Long, can't see on my phone what is wrong but will check it later

Mhh it runs very Long, can't see on my phone what is wrong but will check it later

method rtti_get_t_attri_by_struc not found .. and according paramerts in 3 demos..

Ah changed the name of the method today, did you pull the sample correctly? It's called rtti_get_t_attri_by_any now.

yes i pulled correctly and latest..

forget to merge my latest changes, now both PRs are merged and it should work


bug: Does not install on Node 21

Prerequisites

[X] I have read the Contributing Guidelines.
[X] I have searched for existing issues that already report this problem, without success.

Version
0.7.0
Current Behavior
pnpm add -D @ts-ast-parser/core
 ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)

This error happened while installing a direct dependency of /Users/jh/dev/a70/aui

Your Node version is incompatible with<EMAIL_ADDRESS>
Expected version: ^18.0.0 || ^20.0.0
Got: v21.6.1

This is happening because the package's manifest has an engines.node field specified.
To fix this issue, install the required Node version.

Expected Behavior
To install on node 21
Steps to Reproduce
Install node 21
Install ts-ast-parser
Code Reproduction URL
No response
Additional Information
No response

Hi!
Thanks for opening an issue.
I normally don't support non LTS versions of Node but I suppose it doesn't hurt to enable support for 21.x.
I have released a new version (0.8.0).


No maintenance/new features in Marzipano --> Community take over?

Hi,
I really love the Marzipano tool and its flexibility. Since support feels "kinda dead" I would like to propose that Marzipano will be maintained by other people in the community. Is that possible @tjgq ??
thanks in advance, can we please contact me at joostvanpoppel[at]gmail.com?
thanks,
Joost

I agree that this appears to be the case. Count me in on being a maintainer - we could fork it to another repo so we have control.

That would help. I also see @trevorparscal's PR hasn't been added yet.

I'm looking for a good 360 tour maker. so far marzipano has the best final user experience, but the actual limit of the "tool" that cannot save,load and edit past project is literally a blocking option for big tour.
If anyone want start over, I'll be very happy to see has first feature the ability to save a project, and edit without recreating from the scratch.


add even more useragents

I added a bunch of user agents (mostly crawlers) in this PR. I also added pacman, Pamac, libwww-perl, python-requests, and PackageKit.
Hope this gets merged!

No conflicts @allinurl! Does it look good to you?

Could you please submit another PR with only the added agents. It's confusing seeing those added and removed lines that were not relevant. Thanks

wdym, there's like 1 line that was removed. when you merge the PR, just squash it (I think that's the term) so it's only 1 commit.


Usage of Operators

Hi,
Thanks for this great gem. It has helped me save (and possibly many developers worldwide) weeks (possibly months) of coding time.
I would like to find records in FM server that have a date field greater than my value.
How can i achieve this?
It is stated in FM XML documentation that you send the "field.op" as query string. Here is a passage from docs:

For example, the following request searches for values greater than 100,000 in the “Salary” field
on the “Budget” layout. The resulting data is displayed using the “ExecList” layout, which does not
include the “Salary” field.

> http://<IP_ADDRESS>/fmi/xml/fmresultset.xml?-db=employees
> &-lay=Budget&Salary=100000&Salary.op=gt&-find&-lay.response=ExecList

In RFM i can only use ".find(:field => value)". How can i use comparison operators?
Thanks.

Actually i have experienced that one can send operators in the current rfm like this:
MyLayout.find({'my_field' => '1000', 'myfield.op' => 'gte'})

This would fetch all records that have "my_field" value greater then or equal to 1000.
Other operators can be found in FileMaker Custom Web Publishing documentation. You can also find not null, null, etc. other records. All of them are documented in FileMaker.
But again, it would be better to just write
MyLayout.find('my_field >= 1000')


Master

Added html , css , js for quiz_game
and a screenshot of my game
fixed #1753

Added

Thank you @manshasinghal ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

Hey @manshasinghal,
You can't work on a closed issue 👀!
Follow the proper guideline and make a new PR again 😀.
Happy Hacking 💗

Thank you  @manshasinghal , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


Include or exclude objects in export

Document how to manually filter objects during an export. This is helpful when a database contains  hundreds of tables and you don't want them all.
From @robert-s-lee:

Workaround: List all of the tables and run grep -v or similar.

This topic has come up in a long while. Closing for now.


fix not re-download when network is not stable

When internet is not stable, the file is downloading will be turned to success status. The DownloadManager will let the request to be success but actually it's not.
I have found this bug when testing in poor environment internet.
I use Charles to simulate with this setting

Thanks for your PR. I saw you change the condition with totalBytes, but totalBytes sometimes could not get from header, this will cause error downloading.

I think in that case, it should go to error


Box size!

I have chosen a planar rectangle as one of the 7 configurations, how would we expect to assign the values of a and b (a=length and b=width)? Are we allowed to choose randomly? Because there are no specific values for these terms in the paper?
I will appreciated your responses.

@tirthbha
review my task rectangular_nacl.ipynb


Change in input parsing from 10.1 to 10.3

We ran into a breaking change moving from 10.1. to 10.3 based on the new input parsing code.
Changing the code to
descriptor.Field(i => i.Value)
     .Type<NonNullType<EnumType<FileFormat>>>();

resolves the issue.
I don't think these are the best long term tests for this issue just how I came across it.

Updated with a better unit test.


[consolidated] Disable KafkaChannel dispatcher leader election

Fixes https://github.com/knative/eventing-contrib/issues/1659

Proposed Changes

Disable KafkaChannel dispatcher leader election

Release Note

- 🐛 The consolidated KafkaChannel dispatcher does not attempt anymore to acquire a lease

Docs

Must to be backported to 0.17

/lgtm
/approve

@lionelvillard can you port that the release-branches at https://github.com/knative/eventing-contrib  ?


Fix kubectl_build command

I had an issue with the kubectl_build extension: kubectl build <context> … made the CLI considere the <context> is the subcommand (as kubectl build has multiple commands: create, rm, ls…).
I fixed it by changing the kubectl build … command to kubectl build build ….

I'm sorry, it seems I had a wrong configuration using kubectl build as an alias to kubectl buildkit. I will fix it on my side.
Sorry for the useless PR.


emmet doesn't recognize some html elelements

after the upgrade to vscode 1.15 (and therefore emmet 2.0), some html5 elements are not in the abreviations list. I'm talking about  things like header, nav, footer, aside.
things like div, ul, li, img etc still work.

Thanks for reporting @guyvanbael
We are tracking this in https://github.com/Microsoft/vscode-emmet-helper/issues/5.


Add Android emulator test in GitHub actions

As developer, I would like to run integration test cases using an emulator on GitHub actions so that I can run test on a device
Acceptance Criteria

Unit tests are passing
Integraton tests are passing

Reference
https://www.atkinsondev.com/post/android-emulator-tests-github-actions/

Based on this open issue : https://github.com/ReactiveCircus/android-emulator-runner/issues/348 we do not have internet connection available on emulators, therefore I will close this ticket.


JWS- Verify failed with RSA public key but working with private key

I tried one of your example for JWS signing and verification.
I'm able to perform Sign with private key properly.
But I get below issue while Verify with RSA public key
Uncaught (in promise) TypeError: Cannot read property 'then' of undefined
at WebCryptographer.verify (jose-jwe-webcryptographer.js:316)
at jose-jws-verify.js:223
at Array.forEach ()
at JoseJWS.Verifier.verify (jose-jws-verify.js:183)
Code snippet -
var cryptographer = new Jose.WebCryptographer();
cryptographer.setContentSignAlgorithm("RS256");
var signer = new JoseJWS.Signer(cryptographer);
signer.addSigner(signer_rsa_key).then(function() {
        var message = document.getElementById("jws_text").value;
        var verifier = new JoseJWS.Verifier(cryptographer, message);
        verifier.addRecipient(rsa_key1).then(function () {
                verifier.verify().then(function (verified) {
                        document.getElementById("jws_text").value = 'Verified: ' + JSON.stringify(verified, null, 4);
                        }).catch(function (err) {
                            error.textContent = "verification failed: " + err;
                            }) });});

}
var rsa_key1 =
{
"n":   "00:c2:4b:af:0f:2d:2b:ad:36:72:a7:91:0f:ee:30:a0:95:d5:3a:46:82:86:96:7e:42:c6:fe:8f:20:97:af:49:f6:48:a3:91:53:ac:2e:e6:ec:9a:9a:e0:0a:fb:1c:db:44:40:5b:8c:fc:d5:1c:cb:b6:9b:60:c0:a8:ac:06:f1:6b:29:5e:2f:7b:09:d9:93:32:da:3f:db:53:9c:2e:ea:3b:41:7f:6b:c9:7b:88:9f:2e:c5:dd:42:1e:7f:8f:04:f6:60:3c:fe:43:6d:32:10:ce:8d:99:cb:76:f7:10:97:05:af:28:1e:39:0f:78:35:50:7b:8e:28:22:a4:7d:11:51:22:d1:0e:ab:6b:6f:96:cb:cf:7d:eb:c6:aa:a2:6a:2e:97:2a:93:af:a5:89:e6:c8:bc:9f:fd:85:2b:0f:b4:c0:e4:ca:b5:a7:9a:01:05:81:93:6b:f5:8d:1c:f7:f3:77:0e:6e:53:34:92:0f:48:21:34:33:44:14:5e:4a:00:41:3a:7d:cb:38:82:c1:65:e0:79:ea:a1:05:84:b2:6e:40:19:77:1a:0e:38:4b:28:1f:34:b5:cb:ac:c5:2f:58:51:d7:ec:a8:08:0e:7c:c0:20:c1:5e:a1:4d:b1:30:17:63:0e:e7:58:8e:7f:6e:9f:a4:77:8b:1e:a2:d2:2e:1b:e9",
"e":   65537
};
rsa_key as per  jose-jws-example.html but I have passed only n and e as I get these values only from RSA public key export.
Please guide me if I miss any to make it work.

I'm using browser but I have plan to test it in nodejs version as well.

Which browser? Version?

I tried it in chrome, firefox and edge as well.
chrome - Version 66.0.3359.139
firefox - 59.0.2 (64-bit)
edge - 38.14393.2068.0

I think I can guess what's going on. When you sign the message, the kid is computed using n and d. If you then verify with a key which doesn't have a d, you need to set the keyfinder argument (because the kid will mismatch).
An alternative would be to change Jose.WebCryptographer.keyId to only use n instead of n and d.

Thanks for your analysis.
Below the jsfiddle to replicate the issue. Maybe helpful for your further analysis.
https://jsfiddle.net/u0x2e2j8/5/
https://jsfiddle.net/grkz4akw/

https://jsfiddle.net/grkz4akw/1/ shows you a workaround. We should also return a better failure message when the kid isn't found.

Thanks for the workaround. But the patch works only if we perform both sign and verify operation.
patch works only with sign operation https://jsfiddle.net/grkz4akw/3/
patch fails with verify operation https://jsfiddle.net/grkz4akw/2/
Any help, how we can apply this workaround for verify also and any plans on bug fix.

https://jsfiddle.net/grkz4akw/2/ fails because of a trailing newline in message.
I was hoping to hear back from @rapropos or @rmhrisk, who wrote this part of the library. I'll give them a few more days and then roll out a fix.

Thanks. I will wait for the fix.
Just to know, I could not understand "trailing newline in message" which means I can fix this jsfiddle
https://jsfiddle.net/grkz4akw/2/ (I don't see any trailing newline in this example) or it is part of issue in library?

I plan to write a fix for this issue next week. Sorry it's taken this long, other things have been keeping me busy.


Negative number loss on model training, low confidence in strongly accurate evaluation

Discussed this with several of your engineers last week at WWDC, who asked me to post this here.
General problem domain: Trying to detect lego pieces within an image frame. This would be used in AR to be able to pinpoint where a particular piece is out of an assortment of parts that are spread out. Initially, I am trying to get just a single piece working, though ultimately a couple of hundred different pieces are a more real world scenario.
The model I've trained for a single part exhibits two peculiar characteristics that the engineers I spoke with wanted to explore:

When the model trained, it showed negative loss numbers for much of the training session.
With the trained model, the IMG_1081.JPG test image in the archive is able to be accurately detected but exhibits a confidence value of just 0.2%, while an evaluate() call against the trained data set shows average precisions of 1.0.

An archive with an sframe, model and test images is available here

Hi @kvaughan-ct , thanks for posting here, it was really nice talking to you at WWDC! Hope you're doing well! :-)

The negative loss numbers were very bizarre and unexpected -- I was puzzled to see them as well. I tried to train an Object Detector Model using the SFrame you shared, but I'm not able to repro the negative loss numbers. I'm using Turi Create version 5.0b1 on macOS 10.14 with Python 2.7.10. Could you share what version of macOS, Python, and TC you're using so I can do an exact repro?
Furthermore, do you do anything apart from model = tc.object_detector.create(sf, 'annotations', 'image') that I may be missing? Any train/test split?

Looking forward to hearing from you!

Hi @kvaughan-ct , just wanted to check in on this!

I've not been able to reproduce this either. I'm glad you all saw it in person at least so that I know I wasn't going crazy. My only guess at this point is that I had built cuda on 10.13 and then after upgrading to the beta, didn't get all of it removed before rebuilding on 10.14. Perhaps some mismatched linking caused the issue. I had already cleaned every remnant of cuda that I could find and rebuilt it by the time I was looking at reproduction, and since then have also upgraded to the more recent model MBP. The model is still not very confident, but when I have spare cycles I will continue trying to figure out what sort of data set might help solve this problem, if its solvable at all with current tech.

Thanks for letting us know! Feel free to post if you run into any issues!
Closing this issue since none of us on this thread can repro.


Add option support for filter helper

Is there any way to support option on filter helper? I could not find any way to using image command with variable.
Example:
{{ some_var | image : [resize:50x50] }}

I'll take a look over a weekend.

Was there any progress on this? I've tried all kindsa things to pass a variable to image resize and output the path.
This is the closest I've got, but it just outputs the original image.
---
banner: test.jpg
---
{{ page.banner image [resize:30x20] | asset_path }}

Sorry. I forgot about this issue. I would say go with solution I have proposed here:
https://github.com/jekyll-assets/jekyll-assets/issues/162#issuecomment-115704782
---
banner: test.jpg
---
{{ page.banner | append:' [resize:30x20]' | image }}

That worked a treat, thank you very much!


Local cache for helm charts

I'm trying to use flux-build for not a big gitops repo, but it downloads ~30 helm charts 4000 times! This overloads our registry and slows down rendering a lot.
I've seen that there are commented out attempts to add cache, also there are different caching in helm packages. I could contribute, but would appreciate some hints how to do it better.
Thanks!

This part is mostly from upstream and was disabled in this initial version. I do agree that we need a caching layer here thats why it was left commented in the code.
Happy to merge a pr regarding this! Likely to be extended in https://github.com/DoodleScheduling/flux-build/blob/master/internal/build/helm.go#L464
You might also check upstream flux source-controller base regarding that bit.


Support void type body

Migrate https://github.com/Azure/autorest.csharp/pull/4809

API change check
API changes are not detected in this pull request.


Improve attention benchmarking and add more attention sweeps

Added batch sweeps for llm + unet shapes + bert shapes

Thanks for pushing on this!


Path Manager Restructure

Here is the new architecture for path manager.
Will need to verify with simulation before merging.

@sahil-kale

Can this be made draft before simulation changes are done?


Validation:  Resource property cannot set readOnly properties

Currently, if set a value for a readOnlyProperties, this will be silently ignored.  We should have validation to enforce this validation.

catching some of these because readOnlyProperties should never overlap with writeOnlyProperties or createOnlyProperties or required:
https://github.com/aws-cloudformation/cloudformation-cli/pull/663
https://github.com/aws-cloudformation/cloudformation-cli/pull/668


Failure upon building project on Windows

I'm attempting to build a new project using this template and Clang.
I followed the instructions to install the apps via choco, expect I already had Visual Studio Enterprise installed, so I skipped that bit.  I added everything to the Path.  I also added CC and CCX environment variables.  I selected "Visual Studio 16 2019" as the generator, ClangCl as the Optional toolset, and checked "use default native compilers" Upon configuring in cmake-gui, I get the following output.
Selecting Windows SDK version 10.0.18362.0 to target Windows 10.0.18363.
The CXX compiler identification is Clang 10.0.0 with MSVC-like command-line
Detecting CXX compiler ABI info
Detecting CXX compiler ABI info - done
Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Enterprise/VC/Tools/Llvm/x64/bin/clang-cl.exe - skipped
Detecting CXX compile features
Detecting CXX compile features - done
ccache found and enabled
Conan: checking conan executable
Conan: Found program C:/Program Files/Conan/conan/conan.exe
Conan: Version found Conan version 1.32.0

Conan: Adding bincrafters remote repository (https://api.bintray.com/conan/bincrafters/public-conan)
Conan: Using cmake-multi generator
Conan: Automatic detection of conan settings from cmake
clang-cl
: warning: unknown argument ignored in clang-cl: '-x' [-Wunknown-argument]

clang-cl
: warning: unknown argument ignored in clang-cl: '-dM' [-Wunknown-argument]

clang-cl
: error: no such file or directory: 'c++'

Conan: Settings= -s;build_type=Release;-s;compiler=clang;-s;compiler.version=10;-s;compiler.libcxx=libc++
Conan: checking conan executable
Conan: Found program C:/Program Files/Conan/conan/conan.exe
Conan: Version found Conan version 1.32.0

Conan executing: C:/Program Files/Conan/conan/conan.exe install . -s build_type=Release -s compiler=clang -s compiler.version=10 -s compiler.libcxx=libc++ -g=cmake_multi --build=missing
Configuration:

[settings]
arch=x86_64
arch_build=x86_64
build_type=Release
compiler=clang
compiler.libcxx=libc++
compiler.version=10
os=Windows
os_build=Windows
[options]
[build_requires]
[env]

conanfile.txt:
Installing package
Requirements
    catch2/2.11.0 from 'conan-center' - Cache
    docopt.cpp/0.6.2 from 'conan-center' - Cache
    fmt/6.2.0 from 'conan-center' - Cache
    spdlog/1.5.0 from 'conan-center' - Cache
Packages
    catch2/2.11.0:5ab84d6acfe1f23c4fae0ab88f26e3a396351ac9 - Cache
    docopt.cpp/0.6.2:96ea241aa3076f4628e6ccc36aec6371370a7e39 - Build
    fmt/6.2.0:96ea241aa3076f4628e6ccc36aec6371370a7e39 - Build
    spdlog/1.5.0:3a5fa269c7789182033bca003043705da37ce3d1 - Build

Installing (downloading, building) binaries...

catch2/2.11.0:
Already installed!

docopt.cpp/0.6.2:
Copying sources to build folder

docopt.cpp/0.6.2:
Building your package in C:\Users\gary\.conan\data\docopt.cpp\0.6.2\_\_\build\96ea241aa3076f4628e6ccc36aec6371370a7e39

docopt.cpp/0.6.2:
Generator cmake created conanbuildinfo.cmake

docopt.cpp/0.6.2:
Calling build()

CMake Error: CMake was unable to find a build program corresponding to "MinGW Makefiles".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.

CMake Error: CMake was unable to find a build program corresponding to "MinGW Makefiles".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.

CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage

-- Configuring incomplete, errors occurred!

docopt.cpp/0.6.2:

WARN: spdlog/1.5.0: requirement fmt/6.2.1 overridden by your conanfile to fmt/6.2.0
docopt.cpp/0.6.2: WARN: Package binary is corrupted, removing: 96ea241aa3076f4628e6ccc36aec6371370a7e39
docopt.cpp/0.6.2: WARN: Build folder is dirty, removing it: C:\Users\gary\.conan\data\docopt.cpp\0.6.2\_\_\build\96ea241aa3076f4628e6ccc36aec6371370a7e39
docopt.cpp/0.6.2: ERROR: Package '96ea241aa3076f4628e6ccc36aec6371370a7e39' build failed
docopt.cpp/0.6.2: WARN: Build folder C:\Users\gary\.conan\data\docopt.cpp\0.6.2\_\_\build\96ea241aa3076f4628e6ccc36aec6371370a7e39
ERROR: docopt.cpp/0.6.2: Error in build() method, line 58
	cmake = self._configure_cmake()
while calling '_configure_cmake', line 52
	self._cmake.configure(build_folder=self._build_subfolder)
	ConanException: Error 1 while executing cd C:\Users\gary\.conan\data\docopt.cpp\0.6.2\_\_\build\96ea241aa3076f4628e6ccc36aec6371370a7e39\build_subfolder && cmake -G "MinGW Makefiles" -DCMAKE_BUILD_TYPE="Release" -DCONAN_IN_LOCAL_CACHE="ON" -DCONAN_COMPILER="c
lang" -DCONAN_COMPILER_VERSION="10" -DCONAN_CXX_FLAGS="-m64" -DCONAN_SHARED_LINKER_FLAGS="-m64" -DCONAN_C_FLAGS="-m64" -DCONAN_LIBCXX="libc++" -DBUILD_SHARED_LIBS="OFF" -DCMAKE_INSTALL_PREFIX="C:\Users\gary\.conan\data\docopt.cpp\0.6.2\_\_\package\96ea241aa3076f4628e6ccc36aec6371370a7e39" -DCMAKE_INSTALL_BINDIR="bin" -DCMAKE_INSTALL_SBINDIR="bin" -DCMAKE_INSTALL_LIBEXECDIR="bin" -DCMAKE_INSTALL_LIBDIR="lib" -DCMAKE_INSTALL_INCLUDEDIR="include" -DCMAKE_INSTALL_OLDINCLUDEDIR="include" -DCMAKE_INSTALL_DATAROOTDIR="share" -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY="ON" -DCONAN_EXPORTED="1" -DUSE_BOOST_REGEX="False" -Wno-dev C:\Users\gary\.conan\data\docopt.cpp\0.6.2\_\_\build\96ea241aa3076f4628e6ccc36aec6371370a7e39

CMake Error at build/conan.cmake:402 (message):
  Conan install failed='1'
Call Stack (most recent call first):
  build/conan.cmake:492 (conan_cmake_install)
  cmake/Conan.cmake:16 (conan_cmake_run)
  CMakeLists.txt:76 (run_conan)

Configuring incomplete, errors occurred!
See also "C:/Dev/Code/TheCodeFiend/vulkan-cmake-clang-vs/build/CMakeFiles/CMakeOutput.log".

@gary-desroches this appears to be a bug specific to building docopt.cpp on MSVC/Clang configuration. Have you been able to resolve this problem since you reported it?

@gary-desroches this appears to be a bug specific to building docopt.cpp on MSVC/Clang configuration. Have you been able to resolve this problem since you reported it?

@lefticus I managed to get the build process working on my Windows setup using MSVC/Clang. Unfortunately I'm pretty new to C++ and CMAKE and I don't have a proper solution for this but maybe this info can help someone more knowledgeable address this.
From what I could tell it seems that CMAKE_COMPILER_ID, which is "Clang" under these conditions results in a misconfiguration in build/conan.cmake around lines 154 and 174 which looks to be expecting the CMAKE_COMPILER_ID to be MSVC. I don't know if this is Conan making an incorrect assumption or some issue in this setup.
I managed to get everything building fine by setting the CMAKE_CXX_COMPILER_ID to MSVC and CMAKE_CXX_GENERATOR_TOOLSET to ClangCL before Conan.cmake invokes conan.cmake/conan_cmake_run() and it results in conan generating a working batch of settings that look something like this:
[settings]
arch=x86_64
arch_build=x86_64
build_type=Debug
compiler=Visual Studio
compiler.runtime=MDd
compiler.toolset=ClangCL
compiler.version=16
os=Windows
os_build=Windows
[options]
[build_requires]
[env]

I do revert the CMAKE_COMPILER_ID and CMAKE_GENERATOR_TOOLSET after this call but because I'm pretty clueless about most of this I'm not sure what the repercussions would be. I'm not sure if any of this is useful but hopefully someone here has an idea how this should be fixed up correctly.

After looking into this a little bit more it seems that conan is not correctly checking for the Clang running with the the MSVC frontend. This post over here suggests that CMAKE defines some additional variables based on the the frontend being used with Clang that conan should probably be taking into account.
For my own purposes I have worked around this by checking against these variables and modifying the cmake/Conan.cmake file to look something like this:
`
set (PROJECT_IS_MSVC_CLANG (${CMAKE_CXX_COMPILER_ID} STREQUAL "Clang" AND ${CMAKE_CXX_COMPILER_FRONTEND_VARIANT} STREQUAL "MSVC"))
if (PROJECT_IS_MSVC_CLANG)
set(PREV_CMAKE_CXX_COMPILER_ID ${CMAKE_CXX_COMPILER_ID})
set(PREV_CMAKE_CXX_GENERATOR_TOOLSET ${CMAKE_CXX_GENERATOR_TOOLSET})
set(CMAKE_CXX_COMPILER_ID MSVC)
set(CMAKE_CXX_GENERATOR_TOOLSET ClangCL)
endif ()
conan_cmake_run(
REQUIRES
${CONAN_EXTRA_REQUIRES}
catch2/2.13.3
docopt.cpp/0.6.2
fmt/6.2.0
spdlog/1.5.0
OPTIONS
${CONAN_EXTRA_OPTIONS}
BASIC_SETUP
CMAKE_TARGETS # individual targets to link to
BUILD
missing)
if (PROJECT_IS_MSVC_CLANG)
set(CMAKE_CXX_COMPILER_ID ${PREV_CMAKE_CXX_COMPILER_ID})
set(CMAKE_CXX_GENERATOR_TOOLSET ${PREV_CMAKE_CXX_GENERATOR_TOOLSET})
endif ()
`
Probably a horrendous hack but it works for me until conan handles this correctly.

Has anyone tried the fix proposed in #122 for this problem? I don't know if it works, but it looks a little cleaner.

Has anyone tried the fix proposed in #122 for this problem? I don't know if it works, but it looks a little cleaner.
I'm not able to reproduce this problem myself, otherwise I would try the fix.

I tried it, and I got the following error upon configuring.
Conan executing: C:/Program Files/Conan/conan/conan.exe install . -s build_type=Release -s compiler=clang -s compiler.version=11 -s compiler.libcxx=libc++ -e=CC= -e=CXX=C:/Program Files/LLVM/bin/clang-cl.exe -e=catch2/2.13.3 -e=docopt.cpp/0.6.2 -e=fmt/6.2.0 -e=spdlog/1.5.0 -g=cmake_multi --build=missing
ERROR: Invalid input 'catch2/2.13.3', use 'name=value'

Also, is this just setting environment variables to Clang?  Setting them is a part of the instructions, so I already have them.

@gary-desroches this appears to be a bug specific to building docopt.cpp on MSVC/Clang configuration. Have you been able to resolve this problem since you reported it?

Not yet.

Has anyone tried using Conan profiles (https://docs.conan.io/en/latest/reference/profiles.html)? This is one of the approaches frequently suggested by people in the Conan community who are having trouble building with a specific toolchain. I think you can use a Conan profile to mimic what @BrendonSmuts was doing, without adding any compiler-specific code to Conan.cmake.
You would need to pass the path to your profile into cmake_conan_run:
conan_cmake_run(
    ...
    PROFILE ${PATH_TO_USER_CONAN_PROFILE}
    ...
)

I think you can use PROFILE default if the user doesn't have a Conan profile.
See https://github.com/conan-io/cmake-conan#profile and https://docs.conan.io/en/latest/using_packages/using_profiles.html for docs.

I think we can close this issue now, as cpp-boilerplate-project has builds for windows/llvm


This to remove the existing keys if it is not present in the keys

In the authorized_keys module used in this role is updated with exclusive attribute . It would be addressing the issue raised in the Removing ssh keys #56.

@davidpanofsky Please, can you review and merge this?

I can see the value of this change, but think it might be better to make this behavior something one can opt in/out of. Concerned that with this change, manually added entries would be cleaned up which could be confusing.
Also, note that I'm no longer actively a member of the team which owns this repo. I'll reach out to see if I can get someone to take it on for a faster response in the future.


fix syntax highlighting with new version of Jekyll

Reverts syntax highlighting behavior to state before #5239
CC @benesch

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/e2376cc14e157b3d90595cd8822e2e4539158dab/

Thanks, Sean!


Consider an Alpine dockerfile

The normal aspnet-buster is all good, for sure.  We've converted to using aspnet-alpine for our stuff, and it reduces the size of the docker image.

Thanks for tip, I will check it


platform view initialization error

What is the problem?
the widget can't initialize because of an error creating the PlatformView of the plugin
and this is the code I have:
`import 'package:flutter/material.dart';
import 'package:playx_3d_scene/controller/playx_3d_scene_controller.dart';
import 'package:playx_3d_scene/models/model/glb_model.dart';
import 'package:playx_3d_scene/models/scene/indirect_light/hdr_indirect_light.dart';
import 'package:playx_3d_scene/models/scene/scene.dart';
import 'package:playx_3d_scene/models/scene/skybox/hdr_skybox.dart';
import 'package:playx_3d_scene/models/state/model_state.dart';
import 'package:playx_3d_scene/view/playx_3d_scene.dart';
class HomePage extends StatefulWidget {
const HomePage({super.key});
@override
State createState() => _HomePageState();
}
class _HomePageState extends State {
bool loading = true;
jqsmflk() {
Scene();
}
@override
Widget build(BuildContext context) {
return Scaffold(
appBar: AppBar(
title: const Text('Ayoub 3D Test'),
),
body: Playx3dScene(
model: GlbModel.asset(
"assets/t_shirt.glb",
// animation: PlayxAnimation.byIndex(0, autoPlay: true),
),
scene: Scene(
skybox: HdrSkybox.asset("assets/studio_small_02_4k.hdr"),
// indirectLight:
//     HdrIndirectLight.asset("assets/envs/courtyard.hdr"),
),
onCreated: (Playx3dSceneController controller) async {
// await controller.changeAnimationByIndex(1);
print(controller);
},
onModelStateChanged: (state) {
setState(() {
loading = state == ModelState.loading;
});
},
),
);
}
}`
this is the logs:
Launching lib\main.dart on AOSP on IA Emulator in debug mode...
✓  Built build\app\outputs\flutter-apk\app-debug.apk.
Connecting to VM Service at ws://<IP_ADDRESS>:54487/BbCkuX9JCXo=/ws
D/eglCodecCommon(17485): setVertexArrayObject: set vao to 0 (0) 1 0
D/EGL_emulation(17485): eglMakeCurrent: 0xde770aa0: ver 2 0 (tinfo 0xc9a60fa0)
E/flutter (17485): [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: PlatformException(error, java.lang.IllegalStateException: Trying to create a platform view of unregistered type: io.sourcya.playx.3d.scene.channel_3d_scene
E/flutter (17485): 	at io.flutter.plugin.platform.PlatformViewsController.createPlatformView(PlatformViewsController.java:496)
E/flutter (17485): 	at io.flutter.plugin.platform.PlatformViewsController$1.createForTextureLayer(PlatformViewsController.java:191)
E/flutter (17485): 	at io.flutter.embedding.engine.systemchannels.PlatformViewsChannel$1.create(PlatformViewsChannel.java:128)
E/flutter (17485): 	at io.flutter.embedding.engine.systemchannels.PlatformViewsChannel$1.onMethodCall(PlatformViewsChannel.java:55)
E/flutter (17485): 	at io.flutter.plugin.common.MethodChannel$IncomingMethodCallHandler.onMessage(MethodChannel.java:258)
E/flutter (17485): 	at io.flutter.embedding.engine.dart.DartMessenger.invokeHandler(DartMessenger.java:295)
E/flutter (17485): 	at io.flutter.embedding.engine.dart.DartMessenger.lambda$dispatchMessageToQueue$0$io-flutter-embedding-engine-dart-DartMessenger(DartMessenger.java:322)
E/flutter (17485): 	at io.flutter.embedding.engine.dart.DartMessenger$$ExternalSyntheticLambda0.run(Unknown Source:12)
E/flutter (17485): 	at android.os.Handler.handleCallback(Handler.java:873)
E/flutter (17485): 	at android.os.Handler.dispatchMessage(Handler.java:99)
E/flutter (17485): 	at android.os.Looper.loop(Looper.java:193)
E/flutter (17485): 	at android.app.ActivityThread.main(ActivityThread.java:6669)
E/flutter (17485): 	at java.lang.reflect.Method.invoke(Native Method)
E/flutter (17485): 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
E/flutter (17485): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
E/flutter (17485): , null, null)
E/flutter (17485): #0      StandardMethodCodec.decodeEnvelope
E/flutter (17485): #1      MethodChannel._invokeMethod
E/flutter (17485):
E/flutter (17485): #2      TextureAndroidViewController._sendCreateMessage
E/flutter (17485):
E/flutter (17485): #3      AndroidViewController.create
E/flutter (17485):
E/flutter (17485): #4      AndroidViewController.setSize
E/flutter (17485):
E/flutter (17485): #5      RenderAndroidView._sizePlatformView
E/flutter (17485):
E/flutter (17485):

Hello,
I tested the code and couldn't reproduce the error as the plugin worked as expected.
Can You try running the following
1. flutter clean
2. flutter run

And make sure your minSdkVersion is greater than 23 and try again.