Scripts out of date and some not working as expected

The scripts used on "Azure Virtual Desktop | Custom image templates > Custom Scripts are great but pointing to an old repo.
Storage sense script does not work - I have my own script for this
Removing AppX works OK but leaves 3D and Mixed Reallity Appx on the machine, I cannot get rid of this when doing the image template
Bigged one: Languages - these 2 options on Custome script insert a packer restart which never happens on image creation process (I can see the restarts attempts on the logs) this will then break the image so I had to remove these 2 steps from my template - Does anyone know of a way to insert EN-GB and set as default for all in Regions?
Having said that, I really like this new integration since I am not a coding expert! Thanks everyone who worked really hard for this.
@dknappettmsft

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

ID: 15809d1b-0d5d-db24-aeed-17e112a44432
Version Independent ID: a8be3a55-b20f-51bd-e80f-56fc8a675298
Content: Custom image templates (preview) - Azure Virtual Desktop
Content Source: articles/virtual-desktop/custom-image-templates.md
Service: virtual-desktop
GitHub Login: @dknappettmsft
Microsoft Alias: daknappe

@ii-batman
Thanks for your feedback! We will investigate and update as appropriate.

@dknappettmsft
Can you add your inputs for the above query.

Closing this as per https://github.com/MicrosoftDocs/azure-docs/issues/111372.
#please-close


Deactivate SCIM by default

This PR deactivates SCIM on new realms by default and prevents that SCIM is automatically active on all realm after installing the extension.
This ensures that the administrator doesn't activate SCIM by accident, since it might be "invisible" when the admin theme is not changed.

argh, sorry, need to rebase :)

An additiional note in the README.MD would be great that mentions that the endpoints are disabled by default

added a note

Hi do you still plan to fix the integration-tests on this?

Jup, just got „delayed“ by the patch of good weather lately 😀


[Question]: How to make all documents return positions?

Describe your problem
When I checked the upload document interface, I found that only the PDF has returned location information? I want to highlight the original file when searching on an app? Or do I have a way to change the implementation

The files other than PDF do not support position extraction.


[automate-794] Teams: General UI Fixes

:nut_and_bolt: Description
Issue https://github.com/chef/automate/issues/794
We've brought the Teams (mostly) up to date with our current auth page styling.
:+1: Definition of Done

New empty list state

new heading and tabs on details page

name updates are now part of the details tab

new teams are now created in a modal, not on a different page like before

that long admin team description has been migrated to admins

:athletic_shoe: Demo Script / Repro Steps

log in to the UI
create a team with the modal
on the new team's details page, add users and update the team's name
play around the teams UI and make sure we didn't miss anything!

:chains: Related Resources

took care of this issue as part of this work

:white_check_mark: Checklist

[ ] Necessary tests added/updated?
[ ] Necessary docs added/updated?
[ ] Code actually executed?
[ ] Vetting performed (unit tests, lint, etc.)?

@bcmdarroch @blakestier y'all mind updating the docs team flow and screenshots?
https://automate.chef.io/docs/teams/
There is also mention of an Add Team button, which is now Create Team.


prop-types deprecation warning due to react-portal

prop-types deprecation warning is still there due to the react-portal package
https://cloudup.com/cGWN1K_TwPb
I am opening this issue for reference. react-portal should be updated once this PR is merged.
Thank you

Thanks - the reference isn't needed tho; that's a semver-patch update, so it will automatically upgrade when published.

@ljharb It looks like fix for this issue was a minor update v3.1.0. Can you bump up the version for react-portal please?
https://github.com/tajo/react-portal/releases/tag/v3.1.0

@feyzo no need, ^ automatically covers all non-major updates.

I researched how to upgrade a sub-dependency in yarn but couldn't find a decent solution. There are a few issues scattered around on web but none of them helped.
Can you tell me how i can use<EMAIL_ADDRESS>without installing it as a main dependency?

You'd have to check yarn's documentation; we use npm.


doesn't work with Node.js 4 LTS

Hi, we've moved to use latest JavaScript functionality (eg. await) and as such Node.js 4 is not supported anymore. However, there's an ES5 build in the repo that you can require() in a program that runs on Node.js 4. The ES5 build is also available when installed from npm.
Hope this works for your needs. Feel free to re-open the issue if it doesn't.


Fix bottom padding for alert dialogs when supress is null

Fix padding on MacosAlertDialog when supress field is null.
Fixes #188
Pre-launch Checklist

[x] I have run dartfmt on all changed files
[x] I have incremented the package version as appropriate and updated CHANGELOG.md with my changes
[x] I have added/updated relevant documentation
[x] I have run "optimize/organize imports" on all changed files
[x] I have addressed all analyzer warnings as best I could

Hi @Andrewngabriel, thanks for your PR! I just tried to test your changes and was met with some build errors. Are you seeing this as well?
error: Unable to load contents of file list: '/Target Support Files/Pods-Runner/Pods-Runner-frameworks-Debug-input-files.xcfilelist' (in target 'Runner' from project 'Runner')
error: Unable to load contents of file list: '/Target Support Files/Pods-Runner/Pods-Runner-frameworks-Debug-output-files.xcfilelist' (in target 'Runner' from project 'Runner')

@GroovinChip I ran into the same error but after running pod install from inside the macos directory, it fixed the build issue and was able to run ok.
I did notice however that Podfile.lock was updated. Should I commit that as well?

I did notice however that Podfile.lock was updated. Should I commit that as well?

Check the various .gitignore files and see if it is currently being tracked. If it is, commit it. If not, do not commit it.

@Andrewngabriel don't forget to run flutter pub get at the package level after update the package-level pubspec.yaml since the example's pubspec.lock is tracked; if you don't, the lock file won't update.

I just tried running after latest changes and it seems like there is no longer a Podfile.lock in the macos directory. Not sure if it was removed but the app is building and running fine. Let me know if you're still getting the same error

I just tried running after latest changes and it seems like there is no longer a Podfile.lock in the macos directory. Not sure if it was removed but the app is building and running fine. Let me know if you're still getting the same error

Nah mate, my error was resolved once I regenerated the macos runner.
Anyway, this all LGTM to me. Waiting on checks and then I'll merge.

Congratulations on your first merged PR to macos_ui, @Andrewngabriel!!! Thank you so much for contributing!

@GroovinChip Thank you! Expect many more to come 🙂

@Andrewngabriel hurray!!! Please let me know what else you'd like to work on by assigning yourself an issue and tagging me on it, and if you'd like to join the contributors Slack group please send me your email address and I'll invite you! I'll also add you as a collaborator to this repo so that you don't have to submit PR's from your fork - you'll be able to do it from this repo.

@GroovinChip That would be amazing! I just DMed you my email on Twitter


Hotkey not working

Hello,
Unfortunatelly in my case the hotkey WIN+ALT+V is not working, nothing happen when I press the hotkey.
I found an another global keypress catch method here: https://stackoverflow.com/questions/2450373/set-global-hotkeys-using-c-sharp
(Lumo -s answer)
This works well in debug mode.
Can I replace the hotkey to another hotkey? For example CTRL+Y ?
It would be very good when I can change the hotkey from the config (settings) file.
Thank you very much!

Are you sure you are using tray mode, i.e. restarted your PC? What version are you using; are both, the latest 4.* and 5.* affected? What Windows version do you have? Is there any other app using global hotkeys or even that same hotkey?
What do you mean with "this works well in debug mode"? The code I use is taken from the same stack overflow question (AaronLS answer), so it's the same thing.
The hotkey is hardcoded and currently not changeable. You can change it here and recompile.
If a config option should be added is debatable: The advantage is of course allowing users to easily use one of their preference. However this will probably not solve your issue if the hotkey is not recognised at all. On the other hand a global hotkey must be chosen wisely, because it must not conflict with hotkeys used by other programs (CTRL-Y is a bad choice as it is the "redo" action of windows explorer). In addition, it must be usable with and without the CTRL and SHIFT modifiers used to toggle automode and subdirectory mode. Under these constraints, there is not much left except the WIN-ALT-? option. What is your opinion on this?

Thank you for fast reply!
Yes, it is run in tray mode. After restart, the hotkey not working in my case.
I use version 5.0.2 and latest version of Windows 11 (hungarian).
Oh sorry, I not analyze your keypress solution deeply. I download the source code and insert the keypress code (Lumo) and that works in VS in debug mode.
About hotkey: My opinion is not problem if there a default hotkey (WIN+ALT+V) but the user can change in config when will. In my opinion pressing the WIN+ALT+V is not "comfortable".
Different languages have different keyboard layouts, for example in a hungarian keyboard CTRL+Í would be the best, because it is near to the "V" char (I think this is not used by another app). With the config hotkey option every user can find the best hotkey in his language and if it is not working (because it is used by another app) it can be changed easily again. In Lumo's answer the hotkey is a string, so it could be easily add to C# config file.
I changed the hotkey subscription in your code (as you linked above), but the hotkey is not catched. I not analyze why Lumo's answer works, and the build-in solution why not.
With this code I can catch the keypress (hotkey is an example only):
GlobalHotKey.RegisterHotKey("Control + Y", () =>
{
MessageBox.Show("Pressed");
});
My final goal is: press the hotkey in any folder and insert the image from clipboard to file without opening the form. Thank you!

I tested a little more with a Windows 10 virtual machine too:

In Windows 10 the hotkey works, but in some cases the hotkey opens the View menu of the file explorer. Another cases works well and saves the image.
Pressing the hotkey inside a folder from Total commander will not use the path.

What do you mean: it is possible to assign a shortcut for the context menu item in the registry? I not find solution for this yet, but that would be the perfect solution I think.

That is interesting, Lumo writes he took AaronLS code and only re-wrote it. Obviously, he did something more. Maybe you can quickly confirm that it is not in any way related to VS debugging, but also works for you in the usual tray mode after restart?
If that is positive, could you prepare a PR with the changes? Basically replacing the code in KeyboardHook.cs and update the calling function to use strings as you describe? For the moment, stick to the WIN+ALT+V and confirm that all combinations of the modifiers as mentioned above work on Win 11. Unfortunately, I can't do it because I don't have a Win11 machine to test with.
After you submit the PR with the fix for Win 11, we can add a config option in a second step to allow changing the key.


Autostop doesn't work for shared spaces sagemaker studio

Hello,
I use your autostop script in private spaces for sagemaker studio and it works fine. However, using the same script on shared space with the same custom image brings me an error in Cloudwatch after deploying LCC:

[W 240307 14:44:02 log:49] 404 GET /jupyterlab/default/api/sessions (<IP_ADDRESS>) 4.18ms referer=None
[W 240307 14:46:01 log:49] 404 GET /jupyterlab/default/api/terminals (<IP_ADDRESS>) 4.21ms referer=None
2024-03-07T14:46:01.743687z - [auto-stop-idle] - An error accurred while checking idle state. Exception: string indices must be integers

Does anyone know what is the matter and how to fix this? Thanks in advance😄

Hi @danliaudan , shared spaces are supported through SageMaker Studio Classic rather than the new Studio JupyterLab applications. You should refer to the Studio Classic auto-shutdown extension available here: https://github.com/aws-samples/sagemaker-studio-auto-shutdown-extension. Thank you.


ESP (NodeMCU) crashes when adding the 4th switch...

Hello!
First of all: thank you very much for sharing your code with us!!!
Unfortunately I'm facing a serious issue when adding my 4th swith to the code.
3x Switches are running very smooth, but after adding the 4th my ESP crashes with:
Exception (28):
epc1=0x40203bfb epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000
Is it possible that there is an issue with heap consumption?
I'm starting with:
Adding switch : eins index : 0  => loop heap size: 21248
Adding switch : zwei index : 1  => loop heap size: 21296
Adding switch : drei index : 2   =>loop heap size: 21216
and once I enter the loop (): =>  ... loop heap size: 6584
Any idea what could cause that crash after adding the 4th switch?
BR
Martin

For me work 4 switches just fine on NodeMCU 0.9. Just to make sure - did you change the listen port and introduced the methods at top of *.ino ?
`
lvngRmLEDStripe = new Switch("LED stripe in living room", 80, lvngRmLEDStripeOn, lvngRmLEDStripeOff);
lvngRmCornerLamp = new Switch("corner lamp in living room", 81, lvngRmCornerLampOn, lvngRmCornerLampOff);
lvngRmSubwoofer = new Switch("subwoofer in living room", 82, lvngRmSubwooferOn, lvngRmSubwooferOff);
lvngRmSocket4 = new Switch("socket 4 in living room", 83, lvngRmSocket4On, lvngRmSocket4Off);
`


AutoRef: format of result reporting

We are currently working on a service that displays the schedule and the results automatically. For this, we would like to easily extract the final result from the AutoRef logs. They could, for example, be in a format like:
 score[score]:score[score]
where the first score is the score during the game and [score] the one including the penalty shoot-outs.

The version in 31ef09b always prints FINAL SCORE: 0 - 0 (at least in penalty shootouts)

In order to properly report the result in an easy to parse way, the result should also write one line with:
GAME RESULT: <teamTag> wins (<winComment>)
or
GAME RESULT: DRAW
with examples of winComment:

Regular time
Overtime 0-1
Penalty shootout 2-0
Extended penalty shootout: ball touched more often: 3-2


chore(osio): added workaround to install config map by pipeline

This snippet will get "injected" into the osio pipeline jenkins file to install the configmap before the app gets launched
part of https://github.com/fabric8-launcher/launcher-planning/issues/119

test this please

Thank you @edewit for this!
I take it the same thing should be done for the other boosters as well?

@geoand only the config map boosters I'll take care of it

Cool, thanks!

I guess @edewit would also like to have this on the redhat branch :-)

Done

Hmm, so Jenkinsfile is still being used?!? We really need to get better synchro on the different projects because we were about to delete all the Jenkinsfiles a couple of weeks ago…

@metacosm that is fine the jenkins file in the root is not used. On osio however a user selects a pipeline and then a prefixed jenkins file gets copied into this project.

@edewit so I'm confused as to why we need this change then?

This prefixed jenkins file (example) will not install the config map and there are no injection points to we've added // INJECT into that file and this "snippet" gets inserted there before it's added to the project. Thus the config map will be installed into the stage and prod namespaces before the project gets started. See fabric8-launcher/launcher-planning#119 for more on this

@edewit ok, my bad, I was mistaken on the file that was being modified. So I'm all good on this change after all :)


Ability to customize UI options

Is your feature request related to a problem? Please describe.
Not all config options of ArgoCD server (argocd-cm) can be controlled by the operator (or I wasn't able to figure out how).
When running multiple ArgoCD instances I'd like to alter the UI with custom stylesheets in order to better distinguish them in the browser.
Describe the solution you'd like
Add a section in the ArgoCD operator resource schema where one can control custom styles as documented here:
https://argo-cd.readthedocs.io/en/stable/operator-manual/custom-styles/

Hi @thomascube , Thanks for reaching out.
We have understood the problem that we currently do not support all the config options available for argocd-cm and these config options will keep growing. To fix the problem we have introduced the support for extraConfig in Argo CD CR through which you can add entries to argocd-cm.
PR:
https://github.com/argoproj-labs/argocd-operator/pull/642
This fix is already merged to master and it will be out in the next release 0.4.0 which is planned with in a couple of weeks from now.

Please try this with the new release(once it is released) and feel free to re-open the issue. I am closing this as a duplicate of #641

Perfect. Thanks for the fast response!


Hover card changes

Design

anatomy

profile picture
follow button - has the same states as on the profile
offchain name, if no offchain name, display address
underneath the name, there is address, and 16px icon to copy, the address is copiable all over the address and the icon
divider
nfts created count
follower count
2 latest creations/latest buys - lets experiment with that

File

updated here: https://www.figma.com/design/JXNtryaNYhY0XJNArzvPQx/Handoff?node-id=1287-18959&t=7EV2FWXqowv0DK9U-11
darkmode

follows color pair rules

updated and up for grabs 🚀


Support page objects with Element subclasses

Given
class Page extends PageObject {
  checkbox = selector('.checkbox');
}
const page = new Page();

trying to do
assert.true(page.checkbox.element?.checked)

will give a type error because page.checkbox.element is an Element, not an HTMLInputElement. The user could cast or type-narrow, but it'd be really nice if the page object itself could encode the fact that page.checkbox matches an HTMLInputElement.

Would this be something like:

checking the resulting element of this line: https://github.com/bendemboski/fractal-page-object/blob/main/packages/fractal-page-object/src/page-object.ts#L98
based on the element.tagName return the element with a custom typeguard, i.e. element is HTMLInputElement?

There are a lot of HTMLElements...would this cover ALL of them or just ones with specific attributes like checked?
Also, I think a separate PR could just update the documentation on how to cast or type narrow...I see questions around this come up once in a while because not everyone using this package is familiar with type narrowing.

I don't think we could do it automatically as described -- the tagName of the matching element is a runtime thing that can't be statically known, so can't be used to type narrow. I was thinking that the page object author would optionally be able to tell us what types of elements a selector matches, e.g.
class Page extends PageObject {
  // elements/elements properties produce HTMLInputElements
  checkbox = selector<HTMLInputElement>('.checkbox');

  // elements/elements properties produce Elements
  otherThing = selector('.other-thing');
}


FileNotFoundError: [Errno 2] 01.KEGG_Regular_Module_Information.pickle

Dear MicrobeAnnotator developers,
I tried to annotate two bins with the light mode using blast as my search method, however, it returned a FIleNotFoundError with “01.KEGG_Regular_Module_Information.pickle” being the missing file. The software was used in a virtual python environment in a cluster instead of using Conda. I thought KEGG is not freely available, is it possible that the error was caused by the fact that I do not a KEGG subscription?
Could you help with this? Thank you!
Rui
2021-05-10 02:33:22,505 [INFO]:  ---- This is MicrobeAnnotator v2.0.4 ----
2021-05-10 02:33:22,505 [INFO]: Validating user inputs
2021-05-10 02:33:22,543 [INFO]: Passed
2021-05-10 02:33:22,544 [INFO]: Processing 2 files. I will run 2 files in parallel with 24 threads per file.
2021-05-10 02:33:22,544 [INFO]: Running in light mode. Searching only KOfam and Swissprot using blast.
2021-05-10 02:33:23,270 [INFO]: Searching proteins against KOfam profiles
2021-05-10 02:33:23,270 [INFO]: Parsing HMM profile metadata
2021-05-10 02:33:38,597 [INFO]: Filtering and saving results...
2021-05-10 02:33:38,697 [INFO]: Search against KOfam done!
2021-05-10 02:34:36,306 [INFO]: Filtering and saving results...
2021-05-10 02:34:36,475 [INFO]: Search against KOfam done!
2021-05-10 02:34:37,122 [INFO]: Searching proteins against Swissprot
2021-05-10 03:28:36,327 [INFO]: Extracting Swissprot annotation data
2021-05-10 03:28:49,720 [INFO]: MicrobeAnnotator annotation has finished succesfully!
2021-05-10 03:28:49,721 [INFO]: Summarizing results
2021-05-10 03:28:49,724 [INFO]: Extracting ko numbers and summarizing results
Importing data... Traceback (most recent call last):
File "/home/ruizhang/microbe_annotator/bin/microbeannotator", line 981, in
main()
File "/home/ruizhang/microbe_annotator/bin/microbeannotator", line 969, in main
module_information, metabolism_matrix, module_group_matrix = ko_mapper.module_information_importer(annotation_files)
File "/home/ruizhang/microbe_annotator/lib/python3.7/site-packages/microbeannotator/pipeline/ko_mapper.py", line 93, in module_information_importer
regular_modules = import_module_dict(data_folder / "01.KEGG_Regular_Module_Information.pickle")
File "/home/ruizhang/microbe_annotator/lib/python3.7/site-packages/microbeannotator/pipeline/ko_mapper.py", line 83, in import_module_dict
pickle_in = open(dictionary_location,"rb")
FileNotFoundError: [Errno 2] No such file or directory: '/home/ruizhang/microbe_annotator/lib/python3.7/site-packages/microbeannotator/data/01.KEGG_Regular_Module_Information.pickle'

Hi @Rui-Zzhang,
It seems we are having some issues with the associated data when MicrobeAnnotator is installed using pip. Can you confirm this is the case? If so, you could try installing it from Conda and it should work. Let me know if it does not.

@cruizperez, I have installed microbeannotator on conda but still getting the same error of '01.KEGG_Regular_Module_Information.pickle'. If anyone has solved it please share the debugging technique.

Hey, first, thank you for making MicrobeAnnotator.
I had the same problem and I solved by copying and pasting the files that are missing inside the anaconda environment.
git clone https://github.com/cruizperez/MicrobeAnnotator
then the missing files are going to be in /home/user/MicrobeAnnotator/microbeannotator/data/01.KEGG_Regular_Module_Information.pickle
then you just have to copy and paste the file
cd /home/cd/microbe_annotator/lib/python3.7/site-packages/microbeannotator/data/
cp /home/user/MicrobeAnnotator/microbeannotator/data/01.KEGG_Regular_Module_Information.pickle .


Add a new logo, as well as a basic outline for a TTS & speech recognition desktop interface

Add new logo to README and verbal conversation foundation

What does this add?
This PR just adds a possible logo which we could use, as well as a class for a GUI for verbal communication which will give the users a potentially more natural feeling experience when using the model.

Just in case the ui doesnt make it clear, the inner box is to show a transcription of the conversation


Write guide demonstrating how the build script can be customised

The ods-build-* tasks are quite opinionated. It would be great to have a guide that walks through an example of replacing the opinionated build logic with a script file from the repository.
FYI @adyachok based on our discussion recently

Closing as a consequence of https://github.com/opendevstack/ods-pipeline/pull/722. It is the responsibility of each task repository to maintain the documentation for build tasks.


Not seeing configuration UI page(s)

Describe the issue
I've installed HACS and the Pirate Weather Integrations, but I never see the configuration pages.
The instructions say, "The use to integration, click on the "Add Integration" button on the Integrations page in the Home Assistant Settings and search for Pirate Weather. This will open the add integration UI, shown below."
That UI never appears. I've removed Pirate Weather and HACS a couple of times and reinstalled each, but I never see that configuration UI.
What am I missing?
(I lied below when I said I tried the API in my browser. This issue prevents me from configuring my API key, so it's not the API. I hope...)
Home Assistant version
2024.7.1
Integration version
1.5.3
Troubleshooting steps

[X] I have updated my Home Assistant installation to the latest version.
[X] I have updated the Pirate Weather Integration to the latest version.
[X] I have gone through the documentation before opening this issue.
[X] I have searched this repository and API Repository to see if the issue has already been reported.
[X] I have restarted my Home Assistant installation.
[X] I have queried the API in my browser to confirm the issue is not with the API.
[X] I have written an informative title.

SOLVED. Complete removal of HACS and Pirate Weather, including the recommended restarts. Installed both again and it worked the third time.


Uses FXHash, rather than Rust's default hasher

Uses FxHash rather than Rust's default hasher, in an attempt to improve performance.
My tests have been a bit inconclusive, so would appreciate it if others compared these changes to the main branch in whatever way they think best. FxHash might even be a touch slower in some cases? I'm not sure.
There are definitely other hashers that may be worth exploring, like ahash. Maybe alternatives to try can be discussed in the comments here.

Hey Sam, I would be very surprised if the choice of hash map had an effect on overall performance. Most of the time should be spent looking for regex matches in files, since you're looking for a small number of needles in a very large haystack. If the code for determining whether a needle is actually a secret or not is running slow then I would guess that it's caused by the algorithm being slow (i.e something being accidentally exponential instead of linear). If that's the case, I think the algorithm would need to be fixed rather than the hash map implementation.
Given the built-in hash map has reasonably fast performance, I would prefer to stick with the built-in hash map and not add an additional dependency.
While benchmarks are useful for seeing whether an optimization worked or not, I think profiling is a good way to highlight which parts of the system are worth optimizing. However before even doing that, I would wait until there's a case where ripsecrets runs unreasonably slowly for some input (which I'm sure there are edge cases where it does) since that will likely be a case where optimization is helpful.

Ah, thanks for the explanation! Think I was a bit overeager to make more contributions.

No problem, your contributions have been greatly appreciated! I'm mostly waiting for more feedback for folks in terms of what improvements are needed, but there are still a few small improvements that I'm aware of. I filed them all in the issue tracker https://github.com/sirwart/ripsecrets/issues in case any of them peaked your interest.


Install typing only for old python

Closes #326
Install typing only in older python versions to solve installation problems on modern python

Thanks @GuillemGSubies , released as 0.10.1


Add missing Nepali translations

Add Nepali translations

I have tested that the translation displays fine. I have tested it with Konsole.
Issue https://github.com/php-earth/stats/issues/50

Thank you @samundra for the Nepali translation :+1:  Happy Hakctobeerfest


Limit Tchap to Android 5.0 Lollipop (API 21) and higher

On Android 4.4 and lower, the user is prompted to log out by exporting eventually his keys


Confidence level should be mandatory when validating TagPacks

The confidence level in a TagPack should be somehow mandatory. When validating a TagPack the tool should either fail validation if there isn't a confidence level, or assign the lowest level (e.g. default to Unknown == 0).

We opted for: assigning the lowest confidence level (=unknown) at insertion.


remove debug print from the test

I forgot to remove debug print from the Describe test.

Codecov Report
Patch and project coverage have no change.

Comparison is base (a0db8ac) 73.50% compared to head (b295692) 73.50%.

:exclamation: Current head b295692 differs from pull request most recent head 388b176. Consider uploading reports for the commit 388b176 to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##           master     #261   +/-   ##
=======================================
  Coverage   73.50%   73.50%
=======================================
  Files          43       43
  Lines        2291     2291
=======================================
  Hits         1684     1684
  Misses        377      377
  Partials      230      230

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


fix for "screen cheese with long error messages"

Since the parent element has been set to display: flex, it's children does not uses some of the css properties.
Those has been removed and subtsituted with the flex css property.
fixes #8357

@kisstkondoros Thanks for providing a quick and nice fix. Fix looks good to me. But, if you see the checks our builds are failing due to bad indentation. Can you please fix it and re-submit the request.
Thanks

@kisstkondoros Thanks for the fix. Merged it.


Add avx512f intrinsics

avx512f: add the following intrinsics:-
_mm512_broadcast_i32x4
_mm512_load_si512
_mm512_loadu_si512
_mm512_srli_epi64
_mm512_xor_si512

I tried to keep alphabetical order but I didn't rearrange those that were already disordered.
I found that I don't need explicit fallbacks for these intrinsics with simple pure C implementations.
However my compilers obviously don't efficiently vectorize "complicated" intrinsics like those I added to avx512bw.
I may not need some of the explicit SSE fallbacks I added to avx.h and avx2.h previously.
Do you want me to check and remove them if possible?

The failed check seems to be another APT timeout :-(

Thanks for the patches!
Travis and AppVeyor are failing, too, and not because of APT failures.  I restarted GH Actions and it looks like that succeeds, but there are problems on other compilers and architecutres.

I tried to keep alphabetical order but I didn't rearrange those that were already disordered.

Most of the functions in AVX-512 that are out of order need to come first because they're used to implement other functions.

I may not need some of the explicit SSE fallbacks I added to avx.h and avx2.h previously.
Do you want me to check and remove them if possible?

Unfortunately not all compilers behave the same, especially not for all versions.  It's generally best to have fallbacks in place when possible since it's not feasible to check all versions of all compilers on all architectures :(

Travis and AppVeyor are failing, too, and not because of APT failures. I restarted GH Actions and it looks like that succeeds, but there are problems on other compilers and architecutres.

Oops, sorry.

I may not need some of the explicit SSE fallbacks I added to avx.h and avx2.h previously.
Do you want me to check and remove them if possible?

Unfortunately not all compilers behave the same, especially not for all versions. It's generally best to have fallbacks in place when possible since it's not feasible to check all versions of all compilers on all architectures :(

I must have misunderstood you: I had the impression that you wanted to avoid fallbacks and let the compiler do the job of vectorizing. I have AVX and SSE fallbacks for virtually all the intrinsics that I sent. I carefully removed them before submitting. Do you want me to put them back in?

Travis and AppVeyor are failing, too, and not because of APT failures. I restarted GH Actions and it looks like that succeeds, but there are problems on other compilers and architecutres.

Oops, sorry.

I may not need some of the explicit SSE fallbacks I added to avx.h and avx2.h previously.
Do you want me to check and remove them if possible?

Unfortunately not all compilers behave the same, especially not for all versions. It's generally best to have fallbacks in place when possible since it's not feasible to check all versions of all compilers on all architectures :(

I must have misunderstood you: I had the impression that you wanted to avoid fallbacks and let the compiler do the job of vectorizing. I have AVX and SSE fallbacks for virtually all the intrinsics that I sent. I carefully removed them before submitting. Do you want me to put them back in?

No, it's my fault, I should have been much clearer.
Falling back on a half-length vector is probably a good idea more often than not.  For example, implementing __m512i functions using __m256i.  However, falling back on an __m128i implementation should only be done if __m256i isn't possible; the __m256i version will fall back on an __m128i implementation, so adding a __m128i implementation to an __m512i function is just repeating yourself unnecessarily (modulo compiler bugs, of course).  In other words, AVX fallbacks would usually be good, SSE fallbacks and AVX fallbacks are probably a bad idea.
In some situations the shorter-length fallbacks may make things worse, especially on non-x86 platforms.  In other situations, such as on x86, without -O3/`-fopenmp-simd, and/or on older compilers.  Overall it's probably a win, though.
What really needs to happen is for me to go through and make some changes in how the fallbacks work so we do a better job of choosing whether to use the fallback or rely on the compiler.  Just checking to see if we have a native implementation isn't a good test.  It's relatively high on my list; I was actually hoping to get to it last week.
For example, consider _mm_min_epi32 (sse4.1) when implementing _mm256_min_epi32 (avx2).  If we just test for #if defined(SIMDE_SSE4_1_NATIVE) we are never going to hit that anywhere except for x86.  However, all versions of NEON have vminq_s32 which should be used to implement _mm_min_epi32, so if we don't use it there is a good chance the result will be significantly slower.  Another (probably better) example is saturated math.  I've tried really hard to get compilers to generate something decent, and they just don't cooperate.  However, a lot of SIMD ISA extensions (including NEON and I think WASM) have saturated math functions.
Eventually we may start tweaking the priority of fallbacks; for example, it may make sense to prioritize GCC-style vector extension implementations, then use AVX.  However, this will be a lot easier if we have the code in place to reorganize.
Basically, the answer to the question of "are shorter-length fallbacks good or bad?" is "it's complicated."
I think the source of the misunderstanding is that I was trying to say that in the past I wasn't overly concerned with the shorter-length fallbacks for various reasons, which explains why a lot of the functions in AVX don't have them.  All I was really trying to say was that I didn't think it was quite as vital as you seemed to think; you're looking at relatively old compilers on x86, and there is more to it than that.

I may not need some of the explicit SSE fallbacks I added to avx.h and avx2.h previously.
Do you want me to check and remove them if possible?

Unfortunately not all compilers behave the same, especially not for all versions. It's generally best to have fallbacks in place when possible since it's not feasible to check all versions of all compilers on all architectures :(

I must have misunderstood you: I had the impression that you wanted to avoid fallbacks and let the compiler do the job of vectorizing. I have AVX and SSE fallbacks for virtually all the intrinsics that I sent. I carefully removed them before submitting. Do you want me to put them back in?

Falling back on a half-length vector is probably a good idea more often than not. For example, implementing __m512i functions using __m256i. However, falling back on an __m128i implementation should only be done if __m256i isn't possible; the __m256i version will fall back on an __m128i implementation, so adding a __m128i implementation to an __m512i function is just repeating yourself unnecessarily (modulo compiler bugs, of course). In other words, AVX fallbacks would usually be good, SSE fallbacks and AVX fallbacks are probably a bad idea.

I has hoped that it would work like this (AVX512 falling back to AVX which in turn falls back to SSE if necessary) but unfortunately it doesn't :-(
For me the killer intrinsic is _mm512_shuffle_epi8. Without the double fallback I get a 50x performance penalty running on SSE.
I think the reason is that on SSE, SIMDE_ARCH_X86_AVX2 isn't defined so it won't even try to fallback to AVX.

I think the reason is that on SSE, SIMDE_ARCH_X86_AVX2 isn't defined so it won't even try to fallback to AVX.

Yes, the changes I'm talking about would fix that.  Basically, instead of looking to see wether SIMDE_ARCH_X86_AVX2 (or SIMDE_AVX2_NATIVE) is set, it would fall back on the AVX2 function whenever the largest natively-supported vector size is < 512 bits.
FWIW, if you can use one of shuffle functions with an immediate-mode argument you should get good performance on pretty much any architecture with gcc or clang since we can use __builtin_shuffle/__builtin_shufflevector.

This commit should be applied after my previous one.
I hope that is OK, otherwise I'll combine them.
I hope I have addressed all of Evan's remarks.
I have limited the shift count values to 16 bits.

Excellent, the changes look good, thank you!  The MSVC errors were latent issues, cbc60dc3c195dcdb3352efd9389b14f7e3d3fd93 fixes them.
I made a few changes prior to merging.  It's all trivial stuff, normally I'd just silently "fix" it and thank you for the patch but since it seems like you're interested in contributing going forward I thought it would be a good idea to let you know what I changed and why.

For the preprocessor stuff, I changed the indentation to basically treat it just like the C code.  I know there isn't any consistency on this in SIMDe, but I've been trying to slowly move to this style; it makes it easier to generate code programmatically which is formatted correctly.
In the xor function, I switched the portable fallback to use the i32f member (int_fast32_t), which may be slightly faster than int64_t.
Removed the MODIF_CM checks for the fallbacks.  I'm guessing this is an artifact from some other changes.
Used *mem_addr instead of simde_memcpy in simde_mm512_load_si512.  This function is for aligned loads, so it's okay.  The simde_assert_aligned call theoretically makes this unnecessary since it uses the HEDLEY_ASSUME to tell the compiler that the data is aligned, but not all compilers support it.
Switched from C++ style comments to C style comments (/* ... */ instead of // ...).  Again, this shouldn't really matter since we already require C99 (or at least the subset MSVC supports) and C++ style comments are included in C99, but it does keep our C99 dependency weaker.

Anyways, thanks for all the work on this patch, and sorry again for not being clear about the fallbacks.


Is there a reason to have both lambda_c and impulse_c?

The title is quite expressive. Note that I refer to Pinocchio data.

Yes: impulse (contact impulses) is for impact dynamics and lambda (contact forces) if for contact dynamics. But in future, they won't be useful anymore.

Yes: impulse (contact impulses) is for impact dynamics and lambda (contact forces) if for contact dynamics. But in future, they won't be useful anymore

I know that, I was thinking that we could use one to store both results (for contact and impulse dynamics). However, this question is not important if they won't be useful in future.

In future, they won't be useful anymore.

Small note: even though they might not be necessary as an intermediate result to compute the joint acceleration and delta velocity, I suggest to keep these fields and retain a way of computing them. Somebody may need them per se


Fixes for inserting row or column breaks the formula.

Insert a row between row 5 and 9, breaks the formula.


Build out note section in single-level required schema

Currently, the notes section of the single_level_required.json is a placeholder.
We need to build out the schema to check for the scope and contents and conditions governing access notes.
See PR #40 for additional information.

I'm continuing to look into this, but wanted to note what is NOT working so far. Here's the relevant portion of the schema that I've tried to use anyOf with:
"notes": {
            "type": "array",
            "minItems": 2,
            "items": {
                "anyOf": [
                    {
                        "type": "object",
                        "required": ["type"],
                        "properties": {
                            "type": {
                                "type": "string",
                                "const": "accessrestrict"
                            }
                        }
                    }
                      ]
                }

I ran it against our valid fixture in https://jsonschemalint.com/#!/version/draft-07/markup/json , and the notes that are not required (but we can have anyway) caused validation to fail:

Figured it out. Instead of using items, we need to use contains. So something like:
"notes": {
            "type": "array",
            "minItems": 2,
            "contains": {
                "type": "object",
                "required": [
                    "type"
                ],
                "properties": {
                    "type": {
                        "type": "string",
                        "const": "accessrestrict"
                    }
                }
            },
            "contains": {
                "type": "object",
                "required": [
                    "type"
                ],
                "properties": {
                    "type": {
                        "type": "string",
                        "const": "scopecontent"
                    }
                }
            }
        }


Community - Added new blog SpinKube on KinD

Thanks for hosting my first blog on Fermyon site :smile:
The main changes done are:

Added a new [Community] section under the [News] in the blog menu.

Added a new blog post describing how to install SpinKube on KinD with Rancher Desktop and nerdctl.

Signed-off-by: Nuno do Carmo<EMAIL_ADDRESS>

Congratulations @nunix
Your blog is published.
I just dived in and added a blog image (and some very minor tweaks) for your convenience. Thank you, your article is fantastic. Please let me know if you want anything tweaked/changed/updated.


GUACAMOLE-1291: Add Korean language support

Add translation files for the webapp and the following extensions:
  - guacamole-auth-cas
  - guacamole-auth-duo
  - guacamole-auth-jdbc
  - guacamole-auth-openid
  - guacamole-auth-quickconnect
  - guacamole-auth-radius
  - guacamole-auth-saml
  - guacamole-auth-totp

Hello, I just squashed every commit.
Sorry for confusing commits. I try to make commit more meaningful, and reasonable.
If co-author things should be removed I will do it.

If co-author things should be removed I will do it.

I'm in favor of keeping co-authors as it gives credit to people who've worked on the code, so I don't think you need to remove that, so long as it doesn't interfere with meaningful commit messages :-)

I want to let them co-authors. They made an effort for this translations.

Added missing translation from extensions.

Update ko.json to 1.3.0.
I'm sorry if updating commit is annoying.
@necouchman  is there anything should I do?

@OctopusET: Force pushing the commit is fine, no issues with that. I'll try to review, soon, and make sure it looks okay.

Then should I remove every lines that reference another lines?

I believe so, yes. @mike-jumper can you confirm?

and should I remove lines like ("FIELD_OPTION_BACKSPACE_EMPTY" : "",)? Even these kind line should be empty?

Again, yes, I believe you can leave off empty lines.

@necouchman Okay I will remove all.

Removed unnecessary lines as @necouchman refers.

@necouchman commas removed. Sorry I didn't notice them.

Thank you for review.


Various build fixes

Motivation for this change
The wonderfully charismatic issue from @samueldr  https://github.com/NixOS/nixpkgs/issues/45960.
It was very compelling :smile:
Things done

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

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

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

@xeji
Hmm @GrahamcOfBorg didn't do the thing.

Yes, Ofborg seems a little down today. Maybe you can ask around on IRC, I'm on the road right now.

In the original comment there two spaces between the username and the buildcommand, which is apparently a bug in ofborg. However I deleted the extra space and it seems to be working:
https://logs.nix.ci/?attempt_id=3560f106-d074-4a29-85fa-8fcca91f6a4c&key=nixos%2Fnixpkgs.45967

Thanks! Let's try again, whit definitely only one space:
@GrahamcOfBorg build valadoc SkypeExport amule imgcat photoflow sayonara xfce4-13.xfce4-mixer

Failure on x86_64-darwin (full log)
Attempted: imgcat, photoflow, sayonara
The following builds were skipped because they don't evaluate on x86_64-darwin: valadoc, SkypeExport, amule, xfce4-13.xfce4-mixer
Partial log (click to expand)
        ^~~~~~~~~~~~~~~~~~~~~~~~~~
/nix/store/69j5d16l94pbnpjaf6ngk0m6a0i9bb7i-gstreamer-1.14.0-dev/include/gstreamer-1.0/gst/gstutils.h:1051:25: note: candidate function not viable: no known conversion from 'NanoSeconds *' (aka 'long long *') to 'gint64 *' (aka 'long *') for 3rd argument
gboolean                gst_element_query_position      (GstElement *element, GstFormat format, gint64 *cur);
                        ^
5 errors generated.
make[2]: *** [src/Components/Engine/CMakeFiles/say_comp_engine.dir/build.make:76: src/Components/Engine/CMakeFiles/say_comp_engine.dir/AbstractPipeline.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:3289: src/Components/Engine/CMakeFiles/say_comp_engine.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
builder for '/nix/store/n6w6b411v02jx5vjfvwzbpk0y3q0vgy1-sayonara-player-1.1.1-git1-20180828.drv' failed with exit code 2
error: build of '/nix/store/n6w6b411v02jx5vjfvwzbpk0y3q0vgy1-sayonara-player-1.1.1-git1-20180828.drv', '/nix/store/qsg0mmm0ggfcsjzpgfv0i8ybb4bm66lf-photoflow-unstable-2018-08-28.drv' failed

Failure on aarch64-linux (full log)
Attempted: valadoc, SkypeExport, amule, imgcat, photoflow, sayonara, xfce4-13.xfce4-mixer
Partial log (click to expand)
g++: error: unrecognized command line option '-mno-sse3'; did you mean '-fno-dse'?
[97/311] Building CXX object src/CMakeFiles/pfbase.dir/operations/scale.cc.o
FAILED: src/CMakeFiles/pfbase.dir/operations/scale.cc.o
/nix/store/pcrn3iq0i5s590mlp8v6m7jp1rn7h61r-gcc-wrapper-7.3.0/bin/g++   -I/nix/store/gmy1pcllxkp7fwpq98ld1bgrzx22gl6l-glib-2.56.0-dev/include/glib-2.0 -I/nix/store/8klbwrnv76g2fz8p8rbcg0qg3y5q3hhr-glib-2.56.0/lib/glib-2.0/include -I/nix/store/yb4kia0s0d1is3ia1lx1lb32cfbr1dhj-gtkmm-2.24.5-dev/include/gtkmm-2.4 -I/nix/store/siklys8wg531wbrbv9cjjx9zj0x1rjr7-gtkmm-2.24.5/lib/gtkmm-2.4/include -I/nix/store/yb4kia0s0d1is3ia1lx1lb32cfbr1dhj-gtkmm-2.24.5-dev/include/gdkmm-2.4 -I/nix/store/siklys8wg531wbrbv9cjjx9zj0x1rjr7-gtkmm-2.24.5/lib/gdkmm-2.4/include -I/nix/store/527xw24fzwq1hkd3yzffcr8g824cqfi5-glibmm-2.56.0-dev/include/giomm-2.4 -I/nix/store/55sj9nw451mbd9c704v3h0msc9fnbfyy-glibmm-2.56.0/lib/giomm-2.4/include -I/nix/store/527xw24fzwq1hkd3yzffcr8g824cqfi5-glibmm-2.56.0-dev/include/glibmm-2.4 -I/nix/store/55sj9nw451mbd9c704v3h0msc9fnbfyy-glibmm-2.56.0/lib/glibmm-2.4/include -I/nix/store/3zyhzhp70gc2y08cbcnqxnrp3wkn98gm-libsigc++-2.10.0/include/sigc++-2.0 -I/nix/store/3zyhzhp70gc2y08cbcnqxnrp3wkn98gm-libsigc++-2.10.0/lib/sigc++-2.0/include -I/nix/store/j8nwyym3x7k7ssa7a144b6rkm6m7jays-gtk+-2.24.32-dev/include/gtk-unix-print-2.0 -I/nix/store/j8nwyym3x7k7ssa7a144b6rkm6m7jays-gtk+-2.24.32-dev/include/gtk-2.0 -I/nix/store/qhi5ngxz13gqkk5x7g96nsh64rbhmvlq-gtk+-2.24.32/lib/gtk-2.0/include -I/nix/store/325s7f11pjgj4mp5ha4i94hxp7wr11zp-cairo-1.15.12-dev/include/cairo -I/nix/store/2nppjhfm4jiah3ib1vd6va06z5jmvnqs-freetype-2.9-dev/include/freetype2 -I/nix/store/2nppjhfm4jiah3ib1vd6va06z5jmvnqs-freetype-2.9-dev/include -I/nix/store/dkpp4c28cv9bdqzw6n1gkd8dnj364pdy-fontconfig-2.12.6-dev/include -I/nix/store/sj04c8mncaaczc0w50akgx1ygr9r835s-expat-2.2.6-dev/include -I/nix/store/rx3im9g1qhnijayx4kk1r4nkgdjm71hk-pango-1.42.1-dev/include/pango-1.0 -I/nix/store/d46jnjxzplb2b73clakwrvknh6npp3jq-fribidi-1.0.5/include/fribidi -I/nix/store/7rw34vjaip1pmnc6b7zq5vc35fq84f2a-gdk-pixbuf-2.36.12-dev/include/gdk-pixbuf-2.0 -I/nix/store/7lx9a1anpcg60wnvhx1y7z1a2pqs2l6n-atk-2.28.1-dev/include/atk-1.0 -I/nix/store/ffiw6i8r8kzz7r0ams9hhcl84xpbkcp8-atkmm-2.24.2-dev/include/atkmm-1.6 -I/nix/store/9jmw1k0r28pg0haxvxlqshb4sswr809w-cairomm-1.12.2-dev/include/cairomm-1.0 -I/nix/store/q44x3zjfym2640vgkf60mmw0vzwghvj0-cairomm-1.12.2/lib/cairomm-1.0/include -I/nix/store/y31lb097r3pyzhz607cs91ws04cpvass-pangomm-2.40.1-dev/include/pangomm-1.4 -I/nix/store/myb1a1wkxnaxlznr4mc32ljs6184xcyx-pangomm-2.40.1/lib/pangomm-1.4/include -I/nix/store/cvz2biq9800bpj3h2d8h2hj8xrr6v3qa-pixman-0.34.0/include/pixman-1 -I../src/external -I/nix/store/h9cv9ra3vxi9hi50ja9clcz3nrq0b0xn-libtiff-4.0.9-dev/include -I/nix/store/6d9vv8sn1mcaia2ahxbdq5mm8nn4q9rf-libpng-apng-1.6.34-dev/include -I/nix/store/3772gv6vcx142pchwhzycffagjcs15y8-zlib-1.2.11-dev/include -I/nix/store/mwixsclhx182f88ha9ra04il8svsr4kb-libxml2-2.9.8-dev/include/libxml2 -I/nix/store/63hpm4l1klfvf328xf3dkfcmm59imx1s-libexif-0.6.21/include -I/nix/store/9rxlim7fplmkk8ls4dz8pinf56z4b1n3-vips-8.6.5/include -I../src -I../src/external/rawspeed/src/librawspeed -I../src/external/rawspeed/src/external -Isrc/external/rawspeed/src -I/nix/store/vxjw3lxklgvkrlpvr67xfqmqy47ps9y1-exiv2-0.26.2018.06.09-dev/include -I/nix/store/wd37cgprshsdlkxm3w9hfkry8skf1z20-lensfun-0.3.95/include -I/nix/store/wd37cgprshsdlkxm3w9hfkry8skf1z20-lensfun-0.3.95/include/lensfun -DPF_HAS_LENSFUN     -O3 -ftree-vectorize -DNDEBUG  -std=gnu++11 -march=nocona -mno-sse3 -mtune=generic -Wno-error=narrowing -Dgmic_build -Dcimg_use_vt100 -Dgmic_is_parallel -Dcimg_use_fftw3 -Dcimg_use_tiff -Dcimg_use_zlib -Dcimg_display=0 -fno-ipa-sra -fpermissive -I/build/source/src/dt -DLIBRAW_NODLL -DINSTALL_PREFIX='"/nix/store/5ifrm6vrqsv4kj091izl6l0hcsm03q0b-photoflow-unstable-2018-08-28"'  -DLOCALEDIR="/nix/store/5ifrm6vrqsv4kj091izl6l0hcsm03q0b-photoflow-unstable-2018-08-28/share/locale" -DGTKMM_2  -Wno-unused-parameter -Wno-deprecated-declarations -fPIC -MD -MT src/CMakeFiles/pfbase.dir/operations/scale.cc.o -MF src/CMakeFiles/pfbase.dir/operations/scale.cc.o.d -o src/CMakeFiles/pfbase.dir/operations/scale.cc.o -c ../src/operations/scale.cc
g++: error: unrecognized command line option '-mno-sse3'; did you mean '-fno-dse'?
[98/311] Building C object src/CMakeFiles/pfbase.dir/vips/sinkscreen_pf.c.o
[99/311] Building C object src/CMakeFiles/pfbase.dir/rt/rtengine/cJSON.c.o
ninja: build stopped: subcommand failed.
builder for '/nix/store/4qf6ri62djjnjfgdgs6qhs6xmdqq5ca6-photoflow-unstable-2018-08-28.drv' failed with exit code 1
error: build of '/nix/store/4qf6ri62djjnjfgdgs6qhs6xmdqq5ca6-photoflow-unstable-2018-08-28.drv' failed

Failure on aarch64-linux (full log)
Attempted: valadoc, SkypeExport, amule, imgcat, photoflow, sayonara, xfce4-13.xfce4-mixer
Partial log (click to expand)
g++: error: unrecognized command line option '-mno-sse3'; did you mean '-fno-dse'?
[97/311] Building CXX object src/CMakeFiles/pfbase.dir/operations/scale.cc.o
FAILED: src/CMakeFiles/pfbase.dir/operations/scale.cc.o
/nix/store/pcrn3iq0i5s590mlp8v6m7jp1rn7h61r-gcc-wrapper-7.3.0/bin/g++   -I/nix/store/gmy1pcllxkp7fwpq98ld1bgrzx22gl6l-glib-2.56.0-dev/include/glib-2.0 -I/nix/store/8klbwrnv76g2fz8p8rbcg0qg3y5q3hhr-glib-2.56.0/lib/glib-2.0/include -I/nix/store/yb4kia0s0d1is3ia1lx1lb32cfbr1dhj-gtkmm-2.24.5-dev/include/gtkmm-2.4 -I/nix/store/siklys8wg531wbrbv9cjjx9zj0x1rjr7-gtkmm-2.24.5/lib/gtkmm-2.4/include -I/nix/store/yb4kia0s0d1is3ia1lx1lb32cfbr1dhj-gtkmm-2.24.5-dev/include/gdkmm-2.4 -I/nix/store/siklys8wg531wbrbv9cjjx9zj0x1rjr7-gtkmm-2.24.5/lib/gdkmm-2.4/include -I/nix/store/527xw24fzwq1hkd3yzffcr8g824cqfi5-glibmm-2.56.0-dev/include/giomm-2.4 -I/nix/store/55sj9nw451mbd9c704v3h0msc9fnbfyy-glibmm-2.56.0/lib/giomm-2.4/include -I/nix/store/527xw24fzwq1hkd3yzffcr8g824cqfi5-glibmm-2.56.0-dev/include/glibmm-2.4 -I/nix/store/55sj9nw451mbd9c704v3h0msc9fnbfyy-glibmm-2.56.0/lib/glibmm-2.4/include -I/nix/store/3zyhzhp70gc2y08cbcnqxnrp3wkn98gm-libsigc++-2.10.0/include/sigc++-2.0 -I/nix/store/3zyhzhp70gc2y08cbcnqxnrp3wkn98gm-libsigc++-2.10.0/lib/sigc++-2.0/include -I/nix/store/j8nwyym3x7k7ssa7a144b6rkm6m7jays-gtk+-2.24.32-dev/include/gtk-unix-print-2.0 -I/nix/store/j8nwyym3x7k7ssa7a144b6rkm6m7jays-gtk+-2.24.32-dev/include/gtk-2.0 -I/nix/store/qhi5ngxz13gqkk5x7g96nsh64rbhmvlq-gtk+-2.24.32/lib/gtk-2.0/include -I/nix/store/325s7f11pjgj4mp5ha4i94hxp7wr11zp-cairo-1.15.12-dev/include/cairo -I/nix/store/2nppjhfm4jiah3ib1vd6va06z5jmvnqs-freetype-2.9-dev/include/freetype2 -I/nix/store/2nppjhfm4jiah3ib1vd6va06z5jmvnqs-freetype-2.9-dev/include -I/nix/store/dkpp4c28cv9bdqzw6n1gkd8dnj364pdy-fontconfig-2.12.6-dev/include -I/nix/store/sj04c8mncaaczc0w50akgx1ygr9r835s-expat-2.2.6-dev/include -I/nix/store/rx3im9g1qhnijayx4kk1r4nkgdjm71hk-pango-1.42.1-dev/include/pango-1.0 -I/nix/store/d46jnjxzplb2b73clakwrvknh6npp3jq-fribidi-1.0.5/include/fribidi -I/nix/store/7rw34vjaip1pmnc6b7zq5vc35fq84f2a-gdk-pixbuf-2.36.12-dev/include/gdk-pixbuf-2.0 -I/nix/store/7lx9a1anpcg60wnvhx1y7z1a2pqs2l6n-atk-2.28.1-dev/include/atk-1.0 -I/nix/store/ffiw6i8r8kzz7r0ams9hhcl84xpbkcp8-atkmm-2.24.2-dev/include/atkmm-1.6 -I/nix/store/9jmw1k0r28pg0haxvxlqshb4sswr809w-cairomm-1.12.2-dev/include/cairomm-1.0 -I/nix/store/q44x3zjfym2640vgkf60mmw0vzwghvj0-cairomm-1.12.2/lib/cairomm-1.0/include -I/nix/store/y31lb097r3pyzhz607cs91ws04cpvass-pangomm-2.40.1-dev/include/pangomm-1.4 -I/nix/store/myb1a1wkxnaxlznr4mc32ljs6184xcyx-pangomm-2.40.1/lib/pangomm-1.4/include -I/nix/store/cvz2biq9800bpj3h2d8h2hj8xrr6v3qa-pixman-0.34.0/include/pixman-1 -I../src/external -I/nix/store/h9cv9ra3vxi9hi50ja9clcz3nrq0b0xn-libtiff-4.0.9-dev/include -I/nix/store/6d9vv8sn1mcaia2ahxbdq5mm8nn4q9rf-libpng-apng-1.6.34-dev/include -I/nix/store/3772gv6vcx142pchwhzycffagjcs15y8-zlib-1.2.11-dev/include -I/nix/store/mwixsclhx182f88ha9ra04il8svsr4kb-libxml2-2.9.8-dev/include/libxml2 -I/nix/store/63hpm4l1klfvf328xf3dkfcmm59imx1s-libexif-0.6.21/include -I/nix/store/9rxlim7fplmkk8ls4dz8pinf56z4b1n3-vips-8.6.5/include -I../src -I../src/external/rawspeed/src/librawspeed -I../src/external/rawspeed/src/external -Isrc/external/rawspeed/src -I/nix/store/vxjw3lxklgvkrlpvr67xfqmqy47ps9y1-exiv2-0.26.2018.06.09-dev/include -I/nix/store/wd37cgprshsdlkxm3w9hfkry8skf1z20-lensfun-0.3.95/include -I/nix/store/wd37cgprshsdlkxm3w9hfkry8skf1z20-lensfun-0.3.95/include/lensfun -DPF_HAS_LENSFUN     -O3 -ftree-vectorize -DNDEBUG  -std=gnu++11 -march=nocona -mno-sse3 -mtune=generic -Wno-error=narrowing -Dgmic_build -Dcimg_use_vt100 -Dgmic_is_parallel -Dcimg_use_fftw3 -Dcimg_use_tiff -Dcimg_use_zlib -Dcimg_display=0 -fno-ipa-sra -fpermissive -I/build/source/src/dt -DLIBRAW_NODLL -DINSTALL_PREFIX='"/nix/store/5ifrm6vrqsv4kj091izl6l0hcsm03q0b-photoflow-unstable-2018-08-28"'  -DLOCALEDIR="/nix/store/5ifrm6vrqsv4kj091izl6l0hcsm03q0b-photoflow-unstable-2018-08-28/share/locale" -DGTKMM_2  -Wno-unused-parameter -Wno-deprecated-declarations -fPIC -MD -MT src/CMakeFiles/pfbase.dir/operations/scale.cc.o -MF src/CMakeFiles/pfbase.dir/operations/scale.cc.o.d -o src/CMakeFiles/pfbase.dir/operations/scale.cc.o -c ../src/operations/scale.cc
g++: error: unrecognized command line option '-mno-sse3'; did you mean '-fno-dse'?
[98/311] Building C object src/CMakeFiles/pfbase.dir/vips/sinkscreen_pf.c.o
[99/311] Building C object src/CMakeFiles/pfbase.dir/rt/rtengine/cJSON.c.o
ninja: build stopped: subcommand failed.
builder for '/nix/store/4qf6ri62djjnjfgdgs6qhs6xmdqq5ca6-photoflow-unstable-2018-08-28.drv' failed with exit code 1
error: build of '/nix/store/4qf6ri62djjnjfgdgs6qhs6xmdqq5ca6-photoflow-unstable-2018-08-28.drv' failed

Failure on x86_64-darwin (full log)
Attempted: imgcat, photoflow, sayonara
The following builds were skipped because they don't evaluate on x86_64-darwin: valadoc, SkypeExport, amule, xfce4-13.xfce4-mixer
Partial log (click to expand)
        ^~~~~~~~~~~~~~~~~~~~~~~~~~
/nix/store/69j5d16l94pbnpjaf6ngk0m6a0i9bb7i-gstreamer-1.14.0-dev/include/gstreamer-1.0/gst/gstutils.h:1051:25: note: candidate function not viable: no known conversion from 'NanoSeconds *' (aka 'long long *') to 'gint64 *' (aka 'long *') for 3rd argument
gboolean                gst_element_query_position      (GstElement *element, GstFormat format, gint64 *cur);
                        ^
5 errors generated.
make[2]: *** [src/Components/Engine/CMakeFiles/say_comp_engine.dir/build.make:76: src/Components/Engine/CMakeFiles/say_comp_engine.dir/AbstractPipeline.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:3289: src/Components/Engine/CMakeFiles/say_comp_engine.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
builder for '/nix/store/n6w6b411v02jx5vjfvwzbpk0y3q0vgy1-sayonara-player-1.1.1-git1-20180828.drv' failed with exit code 2
error: build of '/nix/store/n6w6b411v02jx5vjfvwzbpk0y3q0vgy1-sayonara-player-1.1.1-git1-20180828.drv', '/nix/store/qsg0mmm0ggfcsjzpgfv0i8ybb4bm66lf-photoflow-unstable-2018-08-28.drv' failed

Timed out, unknown build status on x86_64-linux (full log)
Attempted: valadoc, SkypeExport, amule, imgcat, photoflow, sayonara, xfce4-13.xfce4-mixer
Partial log (click to expand)
[120/311] Building CXX object src/CMakeFiles/pfbase.dir/operations/gmic/emulate_film_negative_color.cc.o
[121/311] Building CXX object src/CMakeFiles/pfbase.dir/operations/gmic/emulate_film_colorslide.cc.o
[122/311] Building CXX object src/CMakeFiles/pfbase.dir/operations/gmic/emulate_film_instant_consumer.cc.o
[123/311] Building CXX object src/CMakeFiles/pfbase.dir/operations/gmic/emulate_film_instant_pro.cc.o
[124/311] Building CXX object src/CMakeFiles/pfbase.dir/operations/gmic/emulate_film_negative_old.cc.o
[125/311] Building CXX object src/CMakeFiles/pfbase.dir/operations/gmic/gmic_untiled_op.cc.o
[126/311] Building CXX object src/CMakeFiles/pfbase.dir/operations/gmic/emulate_film_print_films.cc.o
[127/311] Building CXX object src/CMakeFiles/pfbase.dir/operations/gmic/emulate_film_various.cc.o
building of '/nix/store/lc55v48m9g0zirwk0q5jysh3x1q7llcr-photoflow-unstable-2018-08-28.drv' timed out after 3600 seconds
error: build of '/nix/store/lc55v48m9g0zirwk0q5jysh3x1q7llcr-photoflow-unstable-2018-08-28.drv' failed

Success on x86_64-linux (full log)
Attempted: valadoc, SkypeExport, amule, imgcat, photoflow, sayonara, xfce4-13.xfce4-mixer
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/d34jwy7cp464cl569b4fls5pbf9gk2l3-xfce4-mixer-4.11.0
shrinking /nix/store/d34jwy7cp464cl569b4fls5pbf9gk2l3-xfce4-mixer-4.11.0/bin/xfce4-mixer
shrinking /nix/store/d34jwy7cp464cl569b4fls5pbf9gk2l3-xfce4-mixer-4.11.0/lib/xfce4/panel/plugins/libmixer.so
gzipping man pages under /nix/store/d34jwy7cp464cl569b4fls5pbf9gk2l3-xfce4-mixer-4.11.0/share/man/
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/d34jwy7cp464cl569b4fls5pbf9gk2l3-xfce4-mixer-4.11.0/lib  /nix/store/d34jwy7cp464cl569b4fls5pbf9gk2l3-xfce4-mixer-4.11.0/bin
patching script interpreter paths in /nix/store/d34jwy7cp464cl569b4fls5pbf9gk2l3-xfce4-mixer-4.11.0
checking for references to /build in /nix/store/d34jwy7cp464cl569b4fls5pbf9gk2l3-xfce4-mixer-4.11.0...
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip

I should probably restrict the platforms on the ones that failed on darwin right?

I should probably restrict the platforms on the ones that failed on darwin right?
Well, that depends on whether they built before.

imgcat built on darwin before this PR, so you can't just disable it: https://hydra.nixos.org/jobset/nixpkgs/trunk/jobs-tab?filter=imgcat.
sayonara never built on darwin in available hydra history: https://hydra.nixos.org/job/nixpkgs/trunk/sayonara.x86_64-darwin/all
same for photoflow.

So: please enable imgcat on darwin again, and we'll look at the logs in more detail (I can't open the ofborg logs above).

@GrahamcOfBorg build imgcat photoflow sayonara

Success on x86_64-darwin (full log)
Attempted: imgcat
The following builds were skipped because they don't evaluate on x86_64-darwin: photoflow, sayonara
Partial log (click to expand)
a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

/nix/store/8bdqdczyl2gd0imh4imda370rvxx9kci-imgcat-2.3.0

Success on x86_64-linux (full log)
Attempted: imgcat, photoflow, sayonara
Partial log (click to expand)
/nix/store/rdlplcj55sixysawbqv8pjyrrssx6nk0-imgcat-2.3.0
/nix/store/vnmdp3a3pzcziqwbgyxx3sb97mbpnrgh-photoflow-unstable-2018-08-28
/nix/store/k51iizqfp331vi5as883vcwahmhxl2kl-sayonara-player-1.1.1-git1-20180828

Failure on aarch64-linux (full log)
Attempted: imgcat, photoflow, sayonara
Partial log (click to expand)
g++: error: unrecognized command line option '-mno-sse3'; did you mean '-fno-dse'?
[97/311] Building CXX object src/CMakeFiles/pfbase.dir/operations/scale.cc.o
FAILED: src/CMakeFiles/pfbase.dir/operations/scale.cc.o
/nix/store/pcrn3iq0i5s590mlp8v6m7jp1rn7h61r-gcc-wrapper-7.3.0/bin/g++   -I/nix/store/gmy1pcllxkp7fwpq98ld1bgrzx22gl6l-glib-2.56.0-dev/include/glib-2.0 -I/nix/store/8klbwrnv76g2fz8p8rbcg0qg3y5q3hhr-glib-2.56.0/lib/glib-2.0/include -I/nix/store/yb4kia0s0d1is3ia1lx1lb32cfbr1dhj-gtkmm-2.24.5-dev/include/gtkmm-2.4 -I/nix/store/siklys8wg531wbrbv9cjjx9zj0x1rjr7-gtkmm-2.24.5/lib/gtkmm-2.4/include -I/nix/store/yb4kia0s0d1is3ia1lx1lb32cfbr1dhj-gtkmm-2.24.5-dev/include/gdkmm-2.4 -I/nix/store/siklys8wg531wbrbv9cjjx9zj0x1rjr7-gtkmm-2.24.5/lib/gdkmm-2.4/include -I/nix/store/527xw24fzwq1hkd3yzffcr8g824cqfi5-glibmm-2.56.0-dev/include/giomm-2.4 -I/nix/store/55sj9nw451mbd9c704v3h0msc9fnbfyy-glibmm-2.56.0/lib/giomm-2.4/include -I/nix/store/527xw24fzwq1hkd3yzffcr8g824cqfi5-glibmm-2.56.0-dev/include/glibmm-2.4 -I/nix/store/55sj9nw451mbd9c704v3h0msc9fnbfyy-glibmm-2.56.0/lib/glibmm-2.4/include -I/nix/store/3zyhzhp70gc2y08cbcnqxnrp3wkn98gm-libsigc++-2.10.0/include/sigc++-2.0 -I/nix/store/3zyhzhp70gc2y08cbcnqxnrp3wkn98gm-libsigc++-2.10.0/lib/sigc++-2.0/include -I/nix/store/j8nwyym3x7k7ssa7a144b6rkm6m7jays-gtk+-2.24.32-dev/include/gtk-unix-print-2.0 -I/nix/store/j8nwyym3x7k7ssa7a144b6rkm6m7jays-gtk+-2.24.32-dev/include/gtk-2.0 -I/nix/store/qhi5ngxz13gqkk5x7g96nsh64rbhmvlq-gtk+-2.24.32/lib/gtk-2.0/include -I/nix/store/325s7f11pjgj4mp5ha4i94hxp7wr11zp-cairo-1.15.12-dev/include/cairo -I/nix/store/2nppjhfm4jiah3ib1vd6va06z5jmvnqs-freetype-2.9-dev/include/freetype2 -I/nix/store/2nppjhfm4jiah3ib1vd6va06z5jmvnqs-freetype-2.9-dev/include -I/nix/store/dkpp4c28cv9bdqzw6n1gkd8dnj364pdy-fontconfig-2.12.6-dev/include -I/nix/store/sj04c8mncaaczc0w50akgx1ygr9r835s-expat-2.2.6-dev/include -I/nix/store/rx3im9g1qhnijayx4kk1r4nkgdjm71hk-pango-1.42.1-dev/include/pango-1.0 -I/nix/store/d46jnjxzplb2b73clakwrvknh6npp3jq-fribidi-1.0.5/include/fribidi -I/nix/store/7rw34vjaip1pmnc6b7zq5vc35fq84f2a-gdk-pixbuf-2.36.12-dev/include/gdk-pixbuf-2.0 -I/nix/store/7lx9a1anpcg60wnvhx1y7z1a2pqs2l6n-atk-2.28.1-dev/include/atk-1.0 -I/nix/store/ffiw6i8r8kzz7r0ams9hhcl84xpbkcp8-atkmm-2.24.2-dev/include/atkmm-1.6 -I/nix/store/9jmw1k0r28pg0haxvxlqshb4sswr809w-cairomm-1.12.2-dev/include/cairomm-1.0 -I/nix/store/q44x3zjfym2640vgkf60mmw0vzwghvj0-cairomm-1.12.2/lib/cairomm-1.0/include -I/nix/store/y31lb097r3pyzhz607cs91ws04cpvass-pangomm-2.40.1-dev/include/pangomm-1.4 -I/nix/store/myb1a1wkxnaxlznr4mc32ljs6184xcyx-pangomm-2.40.1/lib/pangomm-1.4/include -I/nix/store/cvz2biq9800bpj3h2d8h2hj8xrr6v3qa-pixman-0.34.0/include/pixman-1 -I../src/external -I/nix/store/h9cv9ra3vxi9hi50ja9clcz3nrq0b0xn-libtiff-4.0.9-dev/include -I/nix/store/6d9vv8sn1mcaia2ahxbdq5mm8nn4q9rf-libpng-apng-1.6.34-dev/include -I/nix/store/3772gv6vcx142pchwhzycffagjcs15y8-zlib-1.2.11-dev/include -I/nix/store/mwixsclhx182f88ha9ra04il8svsr4kb-libxml2-2.9.8-dev/include/libxml2 -I/nix/store/63hpm4l1klfvf328xf3dkfcmm59imx1s-libexif-0.6.21/include -I/nix/store/9rxlim7fplmkk8ls4dz8pinf56z4b1n3-vips-8.6.5/include -I../src -I../src/external/rawspeed/src/librawspeed -I../src/external/rawspeed/src/external -Isrc/external/rawspeed/src -I/nix/store/vxjw3lxklgvkrlpvr67xfqmqy47ps9y1-exiv2-0.26.2018.06.09-dev/include -I/nix/store/wd37cgprshsdlkxm3w9hfkry8skf1z20-lensfun-0.3.95/include -I/nix/store/wd37cgprshsdlkxm3w9hfkry8skf1z20-lensfun-0.3.95/include/lensfun -DPF_HAS_LENSFUN     -O3 -ftree-vectorize -DNDEBUG  -std=gnu++11 -march=nocona -mno-sse3 -mtune=generic -Wno-error=narrowing -Dgmic_build -Dcimg_use_vt100 -Dgmic_is_parallel -Dcimg_use_fftw3 -Dcimg_use_tiff -Dcimg_use_zlib -Dcimg_display=0 -fno-ipa-sra -fpermissive -I/build/source/src/dt -DLIBRAW_NODLL -DINSTALL_PREFIX='"/nix/store/5ifrm6vrqsv4kj091izl6l0hcsm03q0b-photoflow-unstable-2018-08-28"'  -DLOCALEDIR="/nix/store/5ifrm6vrqsv4kj091izl6l0hcsm03q0b-photoflow-unstable-2018-08-28/share/locale" -DGTKMM_2  -Wno-unused-parameter -Wno-deprecated-declarations -fPIC -MD -MT src/CMakeFiles/pfbase.dir/operations/scale.cc.o -MF src/CMakeFiles/pfbase.dir/operations/scale.cc.o.d -o src/CMakeFiles/pfbase.dir/operations/scale.cc.o -c ../src/operations/scale.cc
g++: error: unrecognized command line option '-mno-sse3'; did you mean '-fno-dse'?
[98/311] Building C object src/CMakeFiles/pfbase.dir/vips/sinkscreen_pf.c.o
[99/311] Building C object src/CMakeFiles/pfbase.dir/rt/rtengine/cJSON.c.o
ninja: build stopped: subcommand failed.
builder for '/nix/store/4qf6ri62djjnjfgdgs6qhs6xmdqq5ca6-photoflow-unstable-2018-08-28.drv' failed with exit code 1
error: build of '/nix/store/4qf6ri62djjnjfgdgs6qhs6xmdqq5ca6-photoflow-unstable-2018-08-28.drv' failed

Don't be confused :smile:  We built multiple packages in one job, and ofborg reports "failure" if at least one fails. You have to look at the logs to know which. So imgcat wasn't the problem after all.

Failure on aarch64-linux (full log)
Attempted: valadoc, SkypeExport, amule, imgcat, photoflow, sayonara, xfce4-13.xfce4-mixer
Partial log (click to expand)
g++: error: unrecognized command line option '-mno-sse3'; did you mean '-fno-dse'?
[97/311] Building CXX object src/CMakeFiles/pfbase.dir/operations/scale.cc.o
FAILED: src/CMakeFiles/pfbase.dir/operations/scale.cc.o
/nix/store/pcrn3iq0i5s590mlp8v6m7jp1rn7h61r-gcc-wrapper-7.3.0/bin/g++   -I/nix/store/gmy1pcllxkp7fwpq98ld1bgrzx22gl6l-glib-2.56.0-dev/include/glib-2.0 -I/nix/store/8klbwrnv76g2fz8p8rbcg0qg3y5q3hhr-glib-2.56.0/lib/glib-2.0/include -I/nix/store/yb4kia0s0d1is3ia1lx1lb32cfbr1dhj-gtkmm-2.24.5-dev/include/gtkmm-2.4 -I/nix/store/siklys8wg531wbrbv9cjjx9zj0x1rjr7-gtkmm-2.24.5/lib/gtkmm-2.4/include -I/nix/store/yb4kia0s0d1is3ia1lx1lb32cfbr1dhj-gtkmm-2.24.5-dev/include/gdkmm-2.4 -I/nix/store/siklys8wg531wbrbv9cjjx9zj0x1rjr7-gtkmm-2.24.5/lib/gdkmm-2.4/include -I/nix/store/527xw24fzwq1hkd3yzffcr8g824cqfi5-glibmm-2.56.0-dev/include/giomm-2.4 -I/nix/store/55sj9nw451mbd9c704v3h0msc9fnbfyy-glibmm-2.56.0/lib/giomm-2.4/include -I/nix/store/527xw24fzwq1hkd3yzffcr8g824cqfi5-glibmm-2.56.0-dev/include/glibmm-2.4 -I/nix/store/55sj9nw451mbd9c704v3h0msc9fnbfyy-glibmm-2.56.0/lib/glibmm-2.4/include -I/nix/store/3zyhzhp70gc2y08cbcnqxnrp3wkn98gm-libsigc++-2.10.0/include/sigc++-2.0 -I/nix/store/3zyhzhp70gc2y08cbcnqxnrp3wkn98gm-libsigc++-2.10.0/lib/sigc++-2.0/include -I/nix/store/j8nwyym3x7k7ssa7a144b6rkm6m7jays-gtk+-2.24.32-dev/include/gtk-unix-print-2.0 -I/nix/store/j8nwyym3x7k7ssa7a144b6rkm6m7jays-gtk+-2.24.32-dev/include/gtk-2.0 -I/nix/store/qhi5ngxz13gqkk5x7g96nsh64rbhmvlq-gtk+-2.24.32/lib/gtk-2.0/include -I/nix/store/325s7f11pjgj4mp5ha4i94hxp7wr11zp-cairo-1.15.12-dev/include/cairo -I/nix/store/2nppjhfm4jiah3ib1vd6va06z5jmvnqs-freetype-2.9-dev/include/freetype2 -I/nix/store/2nppjhfm4jiah3ib1vd6va06z5jmvnqs-freetype-2.9-dev/include -I/nix/store/dkpp4c28cv9bdqzw6n1gkd8dnj364pdy-fontconfig-2.12.6-dev/include -I/nix/store/sj04c8mncaaczc0w50akgx1ygr9r835s-expat-2.2.6-dev/include -I/nix/store/rx3im9g1qhnijayx4kk1r4nkgdjm71hk-pango-1.42.1-dev/include/pango-1.0 -I/nix/store/d46jnjxzplb2b73clakwrvknh6npp3jq-fribidi-1.0.5/include/fribidi -I/nix/store/7rw34vjaip1pmnc6b7zq5vc35fq84f2a-gdk-pixbuf-2.36.12-dev/include/gdk-pixbuf-2.0 -I/nix/store/7lx9a1anpcg60wnvhx1y7z1a2pqs2l6n-atk-2.28.1-dev/include/atk-1.0 -I/nix/store/ffiw6i8r8kzz7r0ams9hhcl84xpbkcp8-atkmm-2.24.2-dev/include/atkmm-1.6 -I/nix/store/9jmw1k0r28pg0haxvxlqshb4sswr809w-cairomm-1.12.2-dev/include/cairomm-1.0 -I/nix/store/q44x3zjfym2640vgkf60mmw0vzwghvj0-cairomm-1.12.2/lib/cairomm-1.0/include -I/nix/store/y31lb097r3pyzhz607cs91ws04cpvass-pangomm-2.40.1-dev/include/pangomm-1.4 -I/nix/store/myb1a1wkxnaxlznr4mc32ljs6184xcyx-pangomm-2.40.1/lib/pangomm-1.4/include -I/nix/store/cvz2biq9800bpj3h2d8h2hj8xrr6v3qa-pixman-0.34.0/include/pixman-1 -I../src/external -I/nix/store/h9cv9ra3vxi9hi50ja9clcz3nrq0b0xn-libtiff-4.0.9-dev/include -I/nix/store/6d9vv8sn1mcaia2ahxbdq5mm8nn4q9rf-libpng-apng-1.6.34-dev/include -I/nix/store/3772gv6vcx142pchwhzycffagjcs15y8-zlib-1.2.11-dev/include -I/nix/store/mwixsclhx182f88ha9ra04il8svsr4kb-libxml2-2.9.8-dev/include/libxml2 -I/nix/store/63hpm4l1klfvf328xf3dkfcmm59imx1s-libexif-0.6.21/include -I/nix/store/9rxlim7fplmkk8ls4dz8pinf56z4b1n3-vips-8.6.5/include -I../src -I../src/external/rawspeed/src/librawspeed -I../src/external/rawspeed/src/external -Isrc/external/rawspeed/src -I/nix/store/vxjw3lxklgvkrlpvr67xfqmqy47ps9y1-exiv2-0.26.2018.06.09-dev/include -I/nix/store/wd37cgprshsdlkxm3w9hfkry8skf1z20-lensfun-0.3.95/include -I/nix/store/wd37cgprshsdlkxm3w9hfkry8skf1z20-lensfun-0.3.95/include/lensfun -DPF_HAS_LENSFUN     -O3 -ftree-vectorize -DNDEBUG  -std=gnu++11 -march=nocona -mno-sse3 -mtune=generic -Wno-error=narrowing -Dgmic_build -Dcimg_use_vt100 -Dgmic_is_parallel -Dcimg_use_fftw3 -Dcimg_use_tiff -Dcimg_use_zlib -Dcimg_display=0 -fno-ipa-sra -fpermissive -I/build/source/src/dt -DLIBRAW_NODLL -DINSTALL_PREFIX='"/nix/store/5ifrm6vrqsv4kj091izl6l0hcsm03q0b-photoflow-unstable-2018-08-28"'  -DLOCALEDIR="/nix/store/5ifrm6vrqsv4kj091izl6l0hcsm03q0b-photoflow-unstable-2018-08-28/share/locale" -DGTKMM_2  -Wno-unused-parameter -Wno-deprecated-declarations -fPIC -MD -MT src/CMakeFiles/pfbase.dir/operations/scale.cc.o -MF src/CMakeFiles/pfbase.dir/operations/scale.cc.o.d -o src/CMakeFiles/pfbase.dir/operations/scale.cc.o -c ../src/operations/scale.cc
g++: error: unrecognized command line option '-mno-sse3'; did you mean '-fno-dse'?
[98/311] Building C object src/CMakeFiles/pfbase.dir/vips/sinkscreen_pf.c.o
[99/311] Building C object src/CMakeFiles/pfbase.dir/rt/rtengine/cJSON.c.o
ninja: build stopped: subcommand failed.
builder for '/nix/store/4qf6ri62djjnjfgdgs6qhs6xmdqq5ca6-photoflow-unstable-2018-08-28.drv' failed with exit code 1
error: build of '/nix/store/4qf6ri62djjnjfgdgs6qhs6xmdqq5ca6-photoflow-unstable-2018-08-28.drv' failed

That's ok, we had a successful build before.

backported in f3702544270..00a43c05d9a


jdk version in readme out of date

current build.sh appears to look for jdk 8, readme still has 7
Provisioning Method: default
A valid JDK distribution was not found at /Users/mnort/projects/docker-iot/dockerfile/common/provision/default/files folder. Expected: jdk-8u112-linux-x64.tar.gz
Cleaning...

Thanks for your interest in testing out the product. However, we are closing this issue now since it relates to an implementation before the re-architecturing of the repository which is no longer supported.


Routing not working

Routing tree gives the correct route, but when alerting it will go to the default receiver
v0.5.1 and v0.4.2

Can you share your config and the alert in question?

It looks like it's not the alertmanager, but prometheus.

Routing is working correctly, i will close this issue.


There is no way to hide the border in dark mode

Can you please add a feature that will allow users to hide the border in dark mode just adding &hide_border=true.

@Mo-Shakib
You can use border=0 to change the border width.
With border=0

Without border=0

Yep, I found that after opening this issue :3


Tooltip in Microsoft Edge browser goes to top of the page

Expected Behavior
Tooltip should be located relevant to origin button.
Steps to Reproduce (for bugs)

Browser: Microsoft Edge.
Enough content before the tooltip so that the page can be scrolled.
Scroll down a little bit
Hover on tooltip origin button.
The tooltip appears at the top of the page.

Please provide a codepen so we can reproduce this. You might need position: relative; on its parent element.

The same issue occurs in Safari Version 12.0 (13606.2.11)
https://codepen.io/iv-mexx/pen/yxZwYG

safari same

Any updates regarding this issue as it still seems to happen?

Any updates regarding this issue as it still seems to happen?

No, as you can see there was no progress.
Do you use Materialize v1.x?

Hi! Yep, I'm using the 1.0.5 startup theme which I bought from the website and is on 1.0.0 (if I remember correctly). Is there anything else you need for recreating the issue? Or is the issue known and reproducible with the devs?

Did you find a workaround for this?

I'm having the same problem in Chrome Version 78.0.3904.97

To fix Edge tooltip issue, search for method "_repositionWithinScreen".
In that method definition, change this
var edges = M.checkWithinContainer(document.body, bounding, offset);
to
var edges = M.checkWithinContainer(document.documentElement, bounding, offset);

The above fixed it for me in Edge, but then broke it in Chrome, so I had to keep both options:
if ((navigator.userAgent.indexOf("Edge") != -1 )){   var edges = M.checkWithinContainer(document.documentElement, bounding, offset); } else {   var edges = M.checkWithinContainer(document.body, bounding, offset); }


Style the documentation and improve layout

Style the documentation and improve layout

Possibly closed by #91 ?
Although I don't imagine this is anywhere near the final look


Add semantic release

Description
Adds semantic release bot to automate releases
Breaking Changes
None
JIRA Link
DA-438
Checklist

[X] Updated the Readme.md (if required) ? (adds some badges)

:tada: This PR is included in version 8.4.0-alpha.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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


spike: small model presets experiments

Model presets
LeapfrogAI currently has two primary models that are used on the backend, but more should be added/tested. By implementing certain small models and evaluating their efficacy from a human perspective, we can make better decisions as to what models to use and evaluate against.
Goal
To determine a list of models and model configs that work well in LFAI from a human-in-the-loop perspective (no automated evals).
Methodology

Determine a short list (up to 5) models to test in LFAI (from HuggingFace is the simplest way to do this)
Run LFAI in a local dev context, replacing the model backend with one of these choices
Change the config parameters to gauge performance
Record config

Limitations

Model licenses are very permissive (e.g MIT, Apache-2.0)
Must be compatible with vllm or llama-cpp-python (the two frameworks currently supported by LFAI)
Limited vRAM requirements (12-16Gb including model weights and context)

Delivery

A list of models, different config options, and a respective set of subjective scores gauging their performance within LFAI.
A report of the methodology used to evaluate these models (so the experiment can be replicated)
Potentially a repository that contains code used to run these evaluations (and what was evaluated on)

I can take this.
Here's an example from AWS on collecting HIL feedback for LM evals:
https://github.com/aws-samples/human-in-the-loop-llm-eval-blog
Is that example similar enough to the intent for this experiment?

Here's a list of additional models for consideration.

https://huggingface.co/meta-llama/Meta-Llama-3.1-8B
https://huggingface.co/nvidia/Llama-3.1-Minitron-4B-Width-Base # distilled Llama 3.1 model
https://huggingface.co/nvidia/Llama-3.1-Minitron-4B-Depth-Base # distilled Llama 3.1 model
https://huggingface.co/nvidia/Mistral-NeMo-Minitron-8B-Base
https://huggingface.co/nvidia/Minitron-8B-Base
https://huggingface.co/nvidia/Minitron-4B-Base
https://huggingface.co/RWKV/v6-Finch-7B-HF
https://huggingface.co/RWKV/v6-Finch-3B-HF

The above models would be used as is – without any quantization; unless it is preferred that I also quantize the models and provide feedback on 8-bit and 4-bit versions.
I can also provide feedback on the models listed in the docs.

https://huggingface.co/TheBloke/SynthIA-7B-v2.0-GGUF # CPU
https://huggingface.co/TheBloke/SynthIA-7B-v2.0-GPTQ # GPU
https://huggingface.co/defenseunicorns/Hermes-2-Pro-Mistral-7B-4bit-32g-GPTQ
https://huggingface.co/NousResearch/Nous-Hermes-2-Mixtral-8x7B-DPO-GGUF

I realize that not all of the models may be supported by llama-cpp-python or vLLM, and that I may need to add support for a custom model; especially for CPU only on macOS.
Here are two GGUF conversion examples for reference:

https://github.com/ggerganov/llama.cpp/discussions/2948
https://brev.dev/blog/convert-to-llamacpp

As for the models that have proprietary licenses – if anything, it will be beneficial to run these subjective evals and provide feedback for the community.
From a user perspective – I'd probably opt for these models on my own, foregoing the default selections – though I understand the need for the LFAI team to ship with a default model that is very permissive in terms of licensing.

For reference I've updated the issue description a little bit to help clarify a few things.
For the AWS HIL example, that framework looks like it makes sense for what we're asking for, so if you would like to use it as a basis, go for it!
I added these to the description, but we have a few limitations I didn't outline originally:

Model licenses are very permissive (e.g MIT, Apache-2.0)
Models must be compatible with vllm or llama-cpp-python (the two frameworks currently supported by LFAI)
Limited vRAM requirements (12-16Gb including model weights and context)

If you're on MacOS, we won't ask you to work outside of the deployment context available to you, so anything that can be run on llama-cpp-python is great. For simplicity, let's stick to model licenses that are as permissive as Apache-2.0 or greater.
The vRAM requirements are ideally less than 12Gb, but anything that would fit under 16Gb is worth checking for our purposes (i.e single-GPU laptop deployment scenarios). That likely means quantizations, so if you can find quantizations for models you want to test, great! We're also open to managing our own quantized models, so feel free to experiment with your own quantizations if you want to, but it's certainly not required.
It would be greatly helpful to compare any models you test with the current defaults from the docs (as you already listed). That would act as a fantastic point of comparison.

[!IMPORTANT]
RWKV is a recurrent model architecture (paper)

RWKV is a different architecture than transformers based models. The model arch is not available in llama-cpp, but can be made available for use in llama-cpp-python by using the gguf-my-repo HF Space.
With regard to the HF Space, a user must understand the quantization key provided in the How (Details) section of https://github.com/ggerganov/llama.cpp/pull/1684. The key applies only to the GGML quantization type, and not the imatrix quantization method (which requires a dataset).

[!NOTE]
Quantized models for this experiment will be made available in this HF collection.

I've successfully installed and deployed LFAI on my personal machine and can proceed by interacting with (1) the UI and/or (2) the API.
Using the UI may be more efficient to collect (fewer) results faster – given I won't have to learn the API to write any code. Additionally, using the UI will allow me to provide UX feedback on both the UI and deploying LFAI on macOS.
Using the API will be more effective to collect more results into a tabular dataset that can be shared with several people who can then provide subjective feedback. Given the objective is to select a model, and not provide UX feedback on the UI, it is probably best to learn to use the API so that I can provide the output to the team (for subjective feedback). Additionally, doing so would also allow me to pivot from providing feedback on UX to API DevX.
Which would you prefer for me to do @jalling97?

@jxtngx let's go with Option 2. There's lots of value in working with the API directly as, like you mention, it'll allow you to iterate faster. The LeapfrogAI team would also greatly benefit from your feedback using the API.
As for the models, those look like great choices! I'm curious to see the impacts of instruct vs. base vs. hermes 3. I would focus more on the 4-bit quantizations, as that tends to be a slightly better fit for single-GPU laptop deployment scenarios.

sounds good.
I'll create the 4 bit versions then share a new table with links.

4 bit models:

Model Family
Model Size
Quantization
Model
License

Llama 3.1
8B
4 bit
jxtngx/Meta-Llama-3.1-8B-Q4_0-GGUF
Llama 3.1 Community

Llama 3.1
8B
4 bit
jxtngx/Meta-Llama-3.1-8B-Instruct-Q4_0-GGUF
Llama 3.1 Community

Llama 3.1
8B
4 bit
jxtngx/Hermes-3-Llama-3.1-8B-Q4_0-GGUF
Llama 3.1 Community

Mistral
7B
4 bit
jxtngx/Hermes-2-Pro-Mistral-7B-Q4_0-GGUF
Apache 2.0

Phi 3 Mini
3.8B
4 bit
jxtngx/Phi-3-mini-128k-instruct-Q4_0-GGUF
MIT

please note that, for each of the 5 models, there are a few flavors of the 4 bit models in the HF collection. Those flavors being:

Q4_0
Q4_K_M
Q4_K_S

the tl;dr on the types is that K type quants are favored over the 0 type quants – as the later is considered a legacy quantization method.
please see below for more on quantization types found in GGUF:

https://huggingface.co/docs/hub/en/gguf#quantization-types
https://www.reddit.com/r/LocalLLaMA/comments/1ba55rj/overview_of_gguf_quantization_methods/

Meta released (leaked) Llama 3.2 on 25 Sep '24; and the new family of models includes 1B and 3B versions which ought to be evaluated against the Phi 3 mini and small versions. The weights have not yet been released to Hugging Face. Once they are available and I've been granted access, I'll quantize the models accordingly.

cc @jalling97

@jxtngx good callout!
Including these new models in the comparison would be great. To prevent from over-exploring in too many directions, feel free to take LLama3.1 8b base out of the comparison list, as the instruct finetune is usually what we'd lean towards anyways.

The current default models were selected in the Fall of 2023 based on finding a balance between model performance and GPU requirements. The defaults needed to be small enough to run on GPU-enabled edge deployments while maximizing performance on the standard evaluations at the time.
cc @justinthelaw @gphorvath if either of you want to add more context


Test-AzTemplate.sh does not recognize newer API versions in reference()

When running Test-AzTemplate.sh on a template with the following code:
 reference('loadbalancername', '2021-05-01')
the test complains that the ApiVersion does not exist, and prints an outdated list of versions:
    [-] apiVersions Should Be Recent In Reference Functions (1887 ms)                                                                                Microsoft.Network/loadBalancers is using an invalid apiVersion. Index:48310                                                                                ApiVersion not found for:  and version         Valid Api Versions found:                                                                                2020-08-01                                                                                2020-07-01                                                                                2020-06-01                                                                                2020-05-01                                                                                2020-04-01                                                                                2020-03-01
It does not complain about resources created in the template using the newer API versions.  It only complains when a newer version is specified in reference().

@lanceshelton - I'm not able to reproduce this on the latest version...  can you check to see you have the latest and if so, attach template we can use to repro?

Closing this out since we don't have a repro


Real-valued Fourier transform

It would be nice to have, for the internal Fourier transform code, specific paths for real input or output, which could mean a 2x increase in performance. When compiled with FFTW, such paths already exist.

This is (partially) implemented in ef536b709cc8be36baa289f7721ba38d04f7b21e
What this does is apply a normal transform to each line along the first transform dimension, then for the other transform dimensions it only processes the non-redundant lines. At the end it copies (with complex conjugation) the computed values to the other half of the image.
The 2x improvement in performance is not really there. For the 2D image sizes I tried, the performance is about equal. In 3D the difference becomes more significant.
Note that the real-to-complex transform that exists in FFTW doesn't seem any faster than the complex-to-complex transform for "normal" image sizes. In fact, it seems a little slower. In fact, the first implementation of dip::FourierTransform using FFTW, which simply prepared the image and called FFTW's nD R2C FFT or C2C FFT as appropriate, showed that the R2C FFT was significantly slower than than the C2C FFT for normal image sizes. With the new implementation (which always uses the 1D C2C FFT in FFTW), we're probably close to the optimal solution. (Note also that running the 1D C2C FFT from FFTW in parallel is more efficient than running the nD C2C FFT in FFTW using FFTW's multithreading. FFTW doesn't seem to get much benefit from multithreading, I think they might multithread each of the 1D FFTs, rather than running the many 1D FFTs in parallel.)


Errors hang Express when redis connectivity is lost with Redis client

Thanks for a great module.  The documentation indicates errors should just be emitted and pass through to the route... which seems true if node couldn't connect to Redis at all on startup.  But, if connectivity is lost after initial connection is made... the response is never returned.  Here is my code (I pass around the exported cache objects as middleware to the routes in server.js):
'use strict';

var redis = require('redis'),
  constants = require('../constants/constants'),
  logger = require('../utils/logger');

var redisClient;
redisClient = redis.createClient(constants.redisPort, constants.redisHost);
redisClient.auth(constants.redisAuth);

redisClient.on('connect', function () {
  logger.info('Connected to redis... ');
});
redisClient.on('error', function (err) {
  logger.error('Error connecting to redis: ' + err);
});

var _redisCache = require('express-redis-cache')({ prefix: constants.env, client: redisClient, expires: 15 });

_redisCache.on('connected', function () {
  logger.info('Cache is functional...');
});
_redisCache.on('error', function (err) {
  logger.error('Cache error: ' + err);
});

exports.tenSecondCache = _redisCache.route(10);
exports.oneMinuteCache = _redisCache.route(60);
exports.fifteenMinuteCache = _redisCache.route(60*15);

It seems that when using a Redis client, once it has problems the error that's emitted to the cache error doesn't allow it to pass through?  I can replicate this locally by cutting off network connectivity after the initial connection.  Is there a way I can let it fall through in this case?

Hey mate,
Thanks for the update! Indeed, there was a flaw in the code. I think I fixed it. Could you checkout master at commit e912f52 and let me know if it works for you. If so, I'll push the update to NPM repo. Thanks for reporting!

Thanks... I can catch the disconnected event when it happens now, but it still blocks.  It never passes through to the route after this is emitted?

Well, to understand  this part of the code, it's important to understand the role of the property connected.  In the file lib/ExpressRedisCache.js have a look at the constructor to see how the connected property is implemented:

first it is set to false
then when redis emits a 'connect' event, it is set to true
but when redis emits an ''end' event, it is set to false

Now to the file lib/ExpressRedisCache/route.js. There is this snippet:
if ( self.connected === false ) {
  return next();
}

So the express-redis-cache middleware checks for connected. If true, it assumes there is a connexion to Redis and proceed with caching mechanism. If false, it calls up next middleware.
I'm going to have another look at it this afternoon (I live in Barcelona).
Cheers

Thanks... This may be related more to how/when redis client emits - but I still experience blocking for requests in this use case.  When I connect to redis and call a cached route... I definitely see self.connected evaluate to true.  If I kill the connection to redis (making it unreachable on the network), and try to access the route again - self.connected still evaluates to true and blocks.  It's not until another subsequent route request causes redis to try reconnect that "end" is emitted (and the connection property gets set to false).

Thanks for the valuable input @benmcmeen! I'll investigate on redis client itself then. I'll let you know when I hit something!

Probably a far stretch, but I modified the code to this manner:
if ( self.connected === false || self.client.connected === false ) {
  return next();
}

Note that I have added a check directly to the client since the redis module also exposes a 'connected' boolean property. On my side, it looks like it's working. Do you want to give it a go also on your side? (commit is master 1386df3)
Cheers

I still experienced blocking... I think the crux of the problem is the redis client doesn't end until well after the cache thinks it's connected.  I created a pull request with a proposed change (not the nicest solution)... let me know what you think.  And thanks again for looking at this!

Hey mate, sorry for the delay! I was actually thinking about another way of fixing our problem. cache.route() calls cache.get(). cache.get() will throw if there is no connection. Then the error thrown is basically just emitted.
Instead, what about calling next() if cache.get throws any error at all? So if there is no live connection, the script rollbacks to use the dynamic page and skip cache altogether.
you can have a look at lib/ExpressRedisCache/routes.js line 132[master e9c2222] to see how error is now implemented.
What do you reckon? Would that fix your problem?
Cheers

btw thanks for spotting that disconnected emitted a "OK connected" evenet :+1:

I'm looking into using this module, has this issue been resolved?

I haven't had time to circle back on this after my pull request (which is
sort of an edge case) - but I am using this - only slightly modified as in
my pull request, and probably redundant to the author's recent changes - in
production for the past couple of months without issues.  I like it a lot.
I do use a hosted Redis solution, and I have a custom heartbeat that pings
my db every now and then (for reasons outside of this module).
Also, I have a custom piece of middleware, loosely based on the module's
documentation to avoid caching errors.  I do this because my responses are
service responses in JSON, and my client applications really need the error
status codes as well as any pertinent messages.  When an response is
cached, subsequent status codes are 200 - which is sort of correct in terms
of a successful cache response... but ultimately misleading since the
status code is often needed to make other choices in the client.
The module has been really useful to me, and I hope this information is
helpful to you.
On Thu, Apr 30, 2015 at 12:30 PM, Kelly Miyashiro<EMAIL_ADDRESS>wrote:

I'm looking into using this module, has this issue been resolved?
—
Reply to this email directly or view it on GitHub
https://github.com/co2-git/express-redis-cache/issues/24#issuecomment-97889228
.

Cool, thanks for the rundown. I'll give it a shot.

In my current usage of the module, my app does pick up the redis unavailability and the app continues to function, albeit without caching benefit.
My app sets up the express-redis-cache as such
var ERC = require('express-redis-cache')l
...
var cache_opts = {
    expire  : redis_opts.cache_expiry_seconds,
    host    : redis_opts.redis_host,
    port    : redis_opts.redis_port,
    prefix  : cache_prefix
};
var cache = new ERC(cache_opts);
cache.on('message', function(message){
    logger.info("cache", message);
});
cache.on('error', function(error){
    logger.error("cache", error);
});

I'm going to consider this issue resolved. Please let me know if you still see problems.


Naive integration with DETR

Hello,
Thank you for your excellent work.
I would like to do some benchmarks with the naive integration with DETR. Do you still have the code with this integration ?

Hello @Nastaszja, I meet the same issue as you mentioned above. Have you solved this problem?


[Issue 4422] Support pulsar scripts to work with bookkeeper

Motivation
Fixes #4422
Modifications
Add BOOKIE options in pulsar_env.sh.

run java8 tests

run java8 tests


Rename project to Hypersistence Utils

Since the project offers more than just Hibernate Types, it's time to rename it to Hypersistence Utils.
The base package and the Maven dependency will change as well.
Since this is a backward incompatible change, the change will happen in the 3.0 version of the project.

IMHO this is not an enchantment but a breaking change.

It is a backward incompatible change, just like the one that happened between Hibernate 2 and Hibernate 3.
For existing projects, they will have to:

change the dependency
update the package names

It's the same as Java EE to Jakarta EE.

Fixed.


Request For Trials

got an Error message while it was fetching paid subscription courses while I was on a trial
IndexError: list Index out of Range
'MainThread' (20720):
Traceback (most recent call last):

File "D:\ine-dl\ine.py", line 1074, in
main()
└ <function main at 0x000002C49DCD18A0>

File "D:\ine-dl\ine.py", line 1026, in main
user_subscriptions = fetch_user_subscriptions(all_course_contents, courses_with_access, all_courses_metadata)
│                        │                    │                    └ 'all_courses_metadata.json'
│                        │                    └ 'all_courses_with_access.json'
│                        └ [{'id': 'bfba41be-429a-11e4-a79f-22000b3582a3', 'tags': ['CCNA', 'Cisco', 'Security'], 'images': {'main_image_url': 'https://...
└ <function fetch_user_subscriptions at 0x000002C49DCD1120>
File "D:\ine-dl\ine.py", line 306, in fetch_user_subscriptions
subscriptions = json.loads(user_subs.text).get("data")[0].get("passes").get("data")
│    │     │         └ <property object at 0x000002C49DA0D490>
│    │     └ <Response [200]>
│    └ <function loads at 0x000002C49D366AC0>
└ <module 'json' from 'C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.12_3.12.496.0_x64__qbz5n2kfra8p0\Lib...
IndexError: list index out of range

If it's possible, pass me the account. I'll take a look.
Can you access courses just fine online?

I can access courses online Normally,
Unfortunately this is not possible Since it's Business Related Credintials

it appears after using the latest version of the @Jayapraveen code that I do not have the subscription/pass to Download the courses although I can browse freely, However, in the @Jayapraveen script I can list the all courses. believe if the listing was tied to subscription authorization it wouldn't have worked.

I am also receiving this error on Ubuntu 22.04.1 LTS.
Business credentials as well. Can I help debug somehow?

I am also receiving this error on Ubuntu 22.04.1 LTS.
Business credentials as well. Can I help debug somehow?
Yes, seems like line 297 doesn't work for us. https://subscriptions.ine.com/subscriptions/subscriptions returns: {"data":[],"meta":{"cursor":{"current":1,"prev":null,"next":null,"count":0}}}

Business APIs might differ a bit, happy to share creds?

@lotfyman95 this is now fixed. For any further comments or issues regarding the fix, use the issue #17.
https://github.com/Anon-Exploiter/ine-dl/issues/17#issuecomment-2093992591