text:
in (Deno or browsers) and (skypack or esm.sh), standalone compilation fails on recursive schemas

This report appears specific to using (either of) skypack or esm.sh to get a ES6 module version of ajv. I see the issue in both Deno v1.16.4 and Chrome 96.0.4664.110 (on OS X, though I doubt that matters).
Specifically, a call to safeStringify in the codegen step appears to find a circular structure, causing the generation to fail. On node.js environments, that doesn't happen.
The version of Ajv you are using
8.8.2
The environment you have the problem with
Deno or browser, using the library as packaged by skypack, esm.sh.
Your code (please make it as small as possible to reproduce the issue)
A minimal example is here. This works on node 17, fails on Deno 1.16
https://runkit.com/cscheid/ajv-non-issue
Results in node.js v8+
In node.js, the standalone source is generated without a problem.
Results and error messages in your platform
There is a runtime error:
> const moduleSrc = standalone(ajv, { "navigation-item": "navigation-item" })
    --> starting at object with constructor 'SchemaEnv'
    |     property 'refs' -> object with constructor 'Object'
    --- property 'navigation-item' closes the circle
    at JSON.stringify (<anonymous>)
    at safeStringify (https://cdn.skypack.dev/-/ajv@v8.8.2-oHh4dWmHmt5cH6zohUYk/dist=es2019,mode=imports/unoptimized/dist/compile/codegen/code.js:138:17)
    at interpolate (https://cdn.skypack.dev/-/ajv@v8.8.2-oHh4dWmHmt5cH6zohUYk/dist=es2019,mode=imports/unoptimized/dist/compile/codegen/code.js:131:78)
    at addCodeArg (https://cdn.skypack.dev/-/ajv@v8.8.2-oHh4dWmHmt5cH6zohUYk/dist=es2019,mode=imports/unoptimized/dist/compile/codegen/code.js:91:17)
    at Object._ (https://cdn.skypack.dev/-/ajv@v8.8.2-oHh4dWmHmt5cH6zohUYk/dist=es2019,mode=imports/unoptimized/dist/compile/codegen/code.js:66:7)
    at refValidateCode (https://cdn.skypack.dev/-/ajv@v8.8.2-oHh4dWmHmt5cH6zohUYk/dist=es2019,mode=imports/unoptimized/dist/standalone/index.js:63:35)
    at https://cdn.skypack.dev/-/ajv@v8.8.2-7PXBFgVwJaIVYRDIomxs/dist=es2019,mode=imports/optimized/ajv.js:287:76
    at Set.forEach (<anonymous>)
    at ValueScope._reduceValues (https://cdn.skypack.dev/-/ajv@v8.8.2-7PXBFgVwJaIVYRDIomxs/dist=es2019,mode=imports/optimized/ajv.js:279:12)
    at ValueScope.scopeCode (https://cdn.skypack.dev/-/ajv@v8.8.2-7PXBFgVwJaIVYRDIomxs/dist=es2019,mode=imports/optimized/ajv.js:266:19)

I suspect the answer here to be that there's a miscompilation somewhere in both esm.sh and skypack.dev. It is somewhat unfortunate, though, because ajv itself works excellently in skypack. It would be fantastic to be able to work around this issue if anyone knows how to do that.

Some progress: I see that in https://github.com/ajv-validator/ajv/blob/1b07663f3954b48892c7210196f7c6ba08000091/lib/compile/codegen/scope.ts, you have the declaration
export class ValueScopeName extends Name {
But in the browser, I can confirm that the line (which compiles from) https://github.com/ajv-validator/ajv/blob/master/lib/compile/codegen/code.ts#L101, in addCodeArg,
  else if (arg instanceof Name) code.push(arg)
the check for arg instanceof Name fails for a variable that's pretty clearly a ValueScopeName... So something is breaking that.

Ok, I'm pretty sure the issue is that both skypack and esm.sh give me slightly different files when importing through ajv/dist/standalone, compared to when importing through ajv. I'm documenting this in case other people are bit by the same problem, and I'll try to report this upstream. You can see that in the stack trace I offered above, by paying attention to the difference in the file paths: ...mode=imports/unoptimized... vs ...mode=imports/optimized...
    at interpolate (https://cdn.skypack.dev/-/ajv@v8.8.2-oHh4dWmHmt5cH6zohUYk/dist=es2019,mode=imports/unoptimized/dist/compile/codegen/code.js:131:78)
    at addCodeArg (https://cdn.skypack.dev/-/ajv@v8.8.2-oHh4dWmHmt5cH6zohUYk/dist=es2019,mode=imports/unoptimized/dist/compile/codegen/code.js:91:17)
    at Object._ (https://cdn.skypack.dev/-/ajv@v8.8.2-oHh4dWmHmt5cH6zohUYk/dist=es2019,mode=imports/unoptimized/dist/compile/codegen/code.js:66:7)
    at refValidateCode (https://cdn.skypack.dev/-/ajv@v8.8.2-oHh4dWmHmt5cH6zohUYk/dist=es2019,mode=imports/unoptimized/dist/standalone/index.js:63:35)
    at https://cdn.skypack.dev/-/ajv@v8.8.2-7PXBFgVwJaIVYRDIomxs/dist=es2019,mode=imports/optimized/ajv.js:287:76
    at Set.forEach (<anonymous>)
    at ValueScope._reduceValues (https://cdn.skypack.dev/-/ajv@v8.8.2-7PXBFgVwJaIVYRDIomxs/dist=es2019,mode=imports/optimized/ajv.js:279:12)
    at ValueScope.scopeCode (https://cdn.skypack.dev/-/ajv@v8.8.2-7PXBFgVwJaIVYRDIomxs/dist=es2019,mode=imports/optimized/ajv.js:266:19)

That's enough for there to be parallel class hierarchies, and then the instanceof check fails.
I imagine you folks didn't foresee this kind of thing happening, and I totally understand if you consider this to not be something worth addressing. But I imagine that using skypack or esm.sh will only become more common over time.
It's worth noting that the two CDN's fail for slightly different reasons. skypack is getting its optimized vs unoptimized build mixed up. But esm.sh is a little more blunt: it just uses esbuild on the package entrypoints, and then of course the classes we get from ajv/dist/standalone and ajv are different; the former carries its own class hierarchy with it almost by design.
Again, I would totally understand if you consider this a "misfeature" of esm.sh, but it would be very nice if the code just worked in these scenarios.

As I think about this some more, I belive the easiest fix (and I believe this would work for both CDN's) would be to expose standalone as an export in /lib/ajv.ts, which would avoid the double import statements and the multiple definitions.
I'd be happy to contribute a PR.

So, when you import from Ajv and from standalone they are somehow different, even though standalone imports from the same file, but because the path different it maps to another module I guess (and node.js understands it’s the same module because it uses absolute paths in module cash)…
I am note very supportive of exporting standalone from Ajv, as it is not needed by most users… What I think could be done in v9 is to stop using instanceof entirely, and use some other duck typing indication - instanceof is repeatedly biting users in different scenarios….
I will think a bit about it.

And thanks a lot for such detailed report!

I am note very supportive of exporting standalone from Ajv, as it is not needed by most users…

I totally understand - I just noticed a big number of exports there and thought I'd suggest. In this case, then, I'll wait for v9 to see if that fixes the skypack issues. In the meantime we can work around locally with a patched bundle on our end.
Thanks again for your work on this! (I'm ok with you folks closing this if you'd prefer to as well.)

Sorry for bumping this with no useful addition but, in regards to the Deno topic, is there any plan to have AJV published on such platform? It would be nice if you could. Thanks a lot.

I too would love to use AJV with Deno.
I've tried hacking support for it with Deno Deploy without success, as AJV generates code, and Deno Deploy does not support that, it seems.

It's not the only project where this has issues with skypack
https://github.com/codemirror/dev/issues/1059

authors: Kreijstal cscheid debo epoberezkin oles

repo: ajv-validator/ajv


text:
🛑 Danni O'Brien Shop is down

In e9a9144, Danni O'Brien Shop (https://shop.danniobrien.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Danni O'Brien Shop is back up in f3c24e9 after 47 minutes.

source: gharchive/issue

repo: ajwarnick/monitor

license: MIT

license_type: permissive

license_source: github-api


text:
visionOS Support

Hi,
Any chance to support visionOS (and its simulator / preview) via this project?
Some context on the state of the source firebase repo's progress/plans for it can be found in this issue. It's taking ... a while. (Both the process and ... building Firestore from source ha)
The changelog for today's version also mentions visionOS changes that seem like they should eventually bring at least the SPM binary distribution for Firestore back, but currently that is still hitting a warning during the actual build.
Thanks again for providing this mirror, it's so helpful to be able to speed up iterations via it.

+1 on this, would be great! 🙏

this would be awesome 🎉

authors: alexfringes arthurschiller oguzveozturk


text:
Tworzenie experta w panelu admina

Tworzenie experta odbywac sie bedzie przez panel admina, a tam musimy tworzyc dwa modoele - experta i usera. Dane do tego pierwszego sa juz predefiniowane w formularzu, natomiast dane do tego drugiego nalezy dopiero umiescic w tym formularzu: to znaczy chcemy tam miec rowniez mozliwosc nadania imienia, nazwiska, maila (moze to sie nawet odbywac w tym popupie co wyskakuje po kliknieciu plusa obok listy userów)

Od razu ogarnę cały ten panel admina by jakoś normalnie wyglądał

authors: Gumkle Szczepaniak-M

repo: akai-org/FakeCheck


text:
Replace Sirupsen with sirupsen in logrus package import URL

Fixes #13

👍
Thanks for the PR

source: gharchive/pull-request

authors: montanaflynn njuettner

repo: akamai-open/AkamaiOPEN-edgegrid-golang

license_source: bigquery


text:
Issue with Akask Provider: Misconfigured Worker Node

Problem
User quantomworks experienced an issue where cloudmos was not recognizing their node despite being active and running a test deployment. Further discussions with SGC | DCNorse identified a problematic configuration where the output indicated the intriguing number for the GPU count:
"gpu":18446744073709551615

This number, 18446744073709551615, was determined to be a representation of -1 when interpreted as a unsigned 64-bit integer ^1^. The user queried this unexpected interpretation and what might cause such an issue.
Diagnosis
SGC | DCNorse suggested that when a GPU goes offline while the provider/worker node is running, the reported number of GPUs might be incorrect. They proposed resolution methods such as shutting down some operations or rebooting the node.
Subsequent Findings

There seemed to be inconsistency between the available GPUs reported by Akash and the actual resources in Kubernetes.

The issue persisted even after updating the driver.

Misconfiguration was identified when moving GPU's between worker nodes. The labels for quantomworks Kubernetes/Akash worker node could be erroneous.

quantomworks detected that the node misunderstanding the number of GPUs available could be because of the node being in use but presenting -1. The nodes in question weren't labeled for GPU use.

Solution
The issue was resolved when correctly labeling the nodes. It seemed that since they weren't initally labeled, it assumed 0 GPU availability for consumption but also presented a -1 due to a workload using them.
{"name":"game-1","allocatable":{"cpu":11000,"gpu":1,"memory":67242971136,"storage_ephemeral":390585090631},"available":{"cpu":3000,"gpu":0,"memory":47008821248,"storage_ephemeral":390585090631}},{"name":"game-2","allocatable":{"cpu":11000,"gpu":1,"memory":67242594304,"storage_ephemeral":390586034349},"available":{"cpu":2285,"gpu":0,"memory":47172022272,"storage_ephemeral":390586034349}}

This correct labeling should allow cloudmos to correctly identify the node and compute resources.
Suggestions
Going forward, these insights would be useful to the community:

A provider troubleshooting page on cloudmos would be handy for issue identification and solutions.
Potential issues when mixing usage of GPUs locally and with Akash given the nature of passthrough in Akash.

Thanks for the suggestion @sfxworks - I'm moving this to the cloudmos repo for consideration towards enhancements there

Actually - looks like this could use improvements in both cloudmos and provider so I'll leave this here and create a separate one in cloudmos, referencing this

Not sure if related, but I am working on one provider now (the other issue where provider isn't releasing all of the GPU's it has),
So the gpu number briefly spiked up to 18446744073709552000 after I've bounced all the four nvdp-nvidia-device-plugin pods (using kubectl -n nvidia-device-plugin delete pods --all command)  (4 worker nodes, each has 8x A100 GPUs)

cc @chainzero @troian

authors: andy108369 anilmurty sfxworks

repo: akash-network/support


text:
Print estimated time remaining

This is not exactly an issue. It's probably me who don't know how the logging feature works.
I was reading the code and it apparently stores the estimated time for completion of a request. Is there anyway I can print that to the screen when making a multiple product query?

It's probably better to use tqdm to give a better estimate for a multiple item query.  Let me see how hard that's to implement.

Fixed in #57.  Install release keepa==0.19.3 to get the time indicator with the progress bar.

Thanks. That was super quick. Will test!

authors: akaszynski volcompt

repo: akaszynski/keepa


text:
Unable to connect to APDL server

Hey there!
I have a similar problem.
I'm trying to get pyansys working. Some weeks ago it works without problems. Yesterday I tried it again and it doesn't work anymore. By running this code for testing:
import os
import pyansys

path = os.getcwd()
ansys = pyansys.Mapdl(run_location=path, jobname='file', override=True)

ansys.prep7()
ansys.k(1, 0, 0, 0)
ansys.save()
ansys.exit()

The following error occurs:
2020-04-16 15:16:58,956 [INFO] pyansys.mapdl: Connecting to ANSYS via CORBA
Traceback (most recent call last):
  File "C:\Users\pi\AppData\Local\Continuum\anaconda3\envs\environment_pi\lib\site-packages\pyansys\mapdl.py", line 1150, in open_corba
    self.mapdl.getComponentName()
  File "C:\Users\pi\AppData\Local\Continuum\anaconda3\envs\environment_pi\lib\site-packages\ansys_corba\ICoMapdlUnit_idl.py", line 185, in getComponentName
    return self._obj.invoke("getComponentName", _0_AAS_CORBA.MAPDL.Solvers.ICoMapdlUnit._d_getComponentName, args)
omniORB.CORBA.TRANSIENT: CORBA.TRANSIENT(omniORB.TRANSIENT_ConnectFailed, CORBA.COMPLETED_NO)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:/Users/pi/Python/Projekt/fe_model.py", line 5, in <module>
    ansys = pyansys.Mapdl(run_location=path, jobname='file', override=True)
  File "C:\Users\pi\AppData\Local\Continuum\anaconda3\envs\environment_pi\lib\site-packages\pyansys\mapdl.py", line 480, in __init__
    self._open(additional_switches)
  File "C:\Users\pi\AppData\Local\Continuum\anaconda3\envs\environment_pi\lib\site-packages\pyansys\mapdl.py", line 494, in _open
    self.open_corba(self.nproc, self.start_timeout, additional_switches)
  File "C:\Users\pi\AppData\Local\Continuum\anaconda3\envs\environment_pi\lib\site-packages\pyansys\mapdl.py", line 1152, in open_corba
    raise Exception('Unable to connect to APDL server')
Exception: Unable to connect to APDL server
2020-04-16 15:17:04,087 [ERROR] pyansys.mapdl: exit: 'Popen' object has no attribute 'sendline'
2020-04-16 15:17:04,087 [ERROR] pyansys.mapdl: kill: 'Popen' object has no attribute 'isalive'

MAPDL opens in the background.
When I run MAPDL directly, there is no license problem.
I'm running: Windows 10 64-bit, ANSYS 19.1, Python 3.7 (and I tried Python 3.5) and pyansys 0.39.17.
Currently I'm working with VPN.
Can someone help?
Thanks
Originally posted by @pi314a in https://github.com/akaszynski/pyansys/issues/137#issuecomment-614656026

Hello @pi314a,

Some weeks ago it works without problems. Yesterday I tried it again and it doesn't work anymore

Did something change with your pyansys environment (e.g. updated pyansys, updated ANSYS, etc)?  Since you're using the latest version, is it possible I broke something with a release?

Hello @akaszynski,
thanks for your quick and sorry for my late reply!
Good question.. I started working with Python in March and I just understood the environment last week. After I ran pyansys without problems I tried to create a new environment and I guess I could have changed the environment where pyansys had been working. So I'm not sure if I updated pyansys with it by mistake and which version I used then. But the time pyansys worked it was the 12 March 2020, so with reference to your release history it only could be version 0.39.15 or lower.
Additionally during the time I was running pyansys without problems I was directly connected with the network and so I didn't have to use VPN.

Hello @akaszynski,
I found out a little more:
A colleague also works with pyansys via VPN but his program runs without problems. Today we both create an environment with Python 3.5 and pyansys 0.39.19. As I said, his program runs without problems but I get the same error as above.
Our systems have some differences:
He´s running: Windows 7, Cisco Systems VPN Client from 2010
I´m running: Windows 10, Cisco AnyConnect

@pi314a,
Thanks for the info.  Sadly, I have little experience running VPN coupled with pyansys, but if you can start MAPDL without pyansys, then it should also run.  Have you tried passing the -smp option to the additional_switches keyword arg?  Otherwise, see if you can investigate file.err at the location pyansys is attempting to start mapdl.  Set your run_location to a known directory (e.g. somewhere in your user directory).

@akaszynski
The -smp option generates the same error as above and the file.err just includes one line:
/COM,ANSYS RELEASE Release 19.1      BUILD 19.1      UP20180418       07:56:22

I'm honestly stumped about this issue.  It sounds like corba isn't connecting to the MAPDL instance.  Are there any other temporary files in the directory you're working in?  Perhaps try not setting your working directory as well.

Which temporary files do you mean? These which are created by running ANSYS?
If yes, there is: aaS_MapdlExceptionHolderServer.txt, aaS_Mapdlld.txt, file.bat, file.err, file.lock, file.page, instant_aaS_Mapdlld.txt, maple_broadcasts.txt and out.txt

Perhaps try not setting your working directory as well.

Sorry, I don't know what you mean. Can you explain?

Sorry for the delayed response.  By working directory I mean the run_location in:
ansys = pyansys.Mapdl(run_location=path, jobname='file', override=True)

I'm still quite unclear what's causing the issue on your end.  It seems like the CORBA server is indeed starting as aaS_Mapdlld.txt is being created, but for some reason it's not connecting.  It's possible that there's a port being blocked, though it's unlikely since you're not connecting to a remote instance.
Is there anything that changed between when it worked and right now?  If an older version of pyansys worked, could you try installing older versions?

Hi @akaszynski,
like you said, I tried not setting the run_location but I got the same error.
I create an environment with pyansys 0.39.15 which also creates the error.
Additionally I tried pyansys 0.39.4 because this version works for my colleagues. With this version the following error occurs:
2020-05-08 10:02:06,193 [INFO] pyansys.mapdl: Connecting to ANSYS via CORBA
Traceback (most recent call last):
  File "C:\Users\alle_pi\AppData\Local\Continuum\anaconda3\envs\env2\lib\site-packages\pyansys\mapdl.py", line 1111, in open_corba
    self.mapdl.getComponentName()
  File "C:\Users\alle_pi\AppData\Local\Continuum\anaconda3\envs\env2\lib\site-packages\ansys_corba\ICoMapdlUnit_idl.py", line 185, in getComponentName
    return self._obj.invoke("getComponentName", _0_AAS_CORBA.MAPDL.Solvers.ICoMapdlUnit._d_getComponentName, args)
omniORB.CORBA.TRANSIENT: CORBA.TRANSIENT(omniORB.TRANSIENT_ConnectFailed, CORBA.COMPLETED_NO)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:/Users/alle_pi/Python/alte_Pyansys/Test.py", line 5, in <module>
    ansys = pyansys.Mapdl(run_location=path, jobname='file', override=True)
  File "C:\Users\alle_pi\AppData\Local\Continuum\anaconda3\envs\env2\lib\site-packages\pyansys\mapdl.py", line 459, in __init__
    self._open(additional_switches)
  File "C:\Users\alle_pi\AppData\Local\Continuum\anaconda3\envs\env2\lib\site-packages\pyansys\mapdl.py", line 473, in _open
    self.open_corba(self.nproc, self.start_timeout, additional_switches)
  File "C:\Users\alle_pi\AppData\Local\Continuum\anaconda3\envs\env2\lib\site-packages\pyansys\mapdl.py", line 1113, in open_corba
    raise Exception('Unable to connect to APDL server')
Exception: Unable to connect to APDL server
Exception ignored in: <bound method Mapdl.__del__ of <pyansys.mapdl.Mapdl object at 0x00000198FF286B00>>
Traceback (most recent call last):
  File "C:\Users\alle_pi\AppData\Local\Continuum\anaconda3\envs\env2\lib\site-packages\pyansys\mapdl.py", line 973, in __del__
NameError: name 'exception' is not defined

Is there anything that changed between when it worked and right now?

Yeah, when it worked I was in office and didn't need VPN. Unfortunately I didn't try running it with VPN when it was working. At the moment I'm not able to go to office so that I could test it again without VPN...

Good news (sorta).  I've been able to reproduce this error on Windows.  I'll get working on this tomorrow.

Thanks @akaszynski  . I am seeing the same problem with VPN access needed to query the license server. Any resolution would be greatly appreciated. This is fantastic functionality you have developed, and it is a shame that VPN is causing trouble.

Hi @akaszynski,
I'm running: Windows 7 64-bit, ANSYS 18.1, Python 3.7 ,pyansys 0.40.0
and I also working with VPN.
When I try to connect to ANSYS with pyansys.Mapdl(),
I get : Unable to start ANSYS within 120 seconds
I tried a start_timeout=600 but It doesn't depend on time
I tried -smp or -aa_r for additional_switches and I get :
2020-05-20 16:50:27,012 [ERROR] pyansys.mapdl: exit: 'SubprocessPopen' object has no attribute 'sendline'
2020-05-20 16:50:27,012 [ERROR] pyansys.mapdl: kill: 'SubprocessPopen' object has no attribute 'isalive'
2020-05-20 16:51:27,024 [ERROR] pyansys.mapdl: Unable to start ANSYS within 120.0 seconds
I verified the exec_file path and it's the good one
I use os.getcwd() for the run_location path
Can someone help?
I don't know if it's related to your issues.
Thanks!

All the issues here are related to CORBA unable to work under VPN.  It's likely due to the way the CORBA server opens a port at a specific IP address and it likely tries to open it at the address of the VPN adapter and not at a general 0.0.0.0 address.
ANSYS will be releasing a newer interface in the following release or two, but I'll look into this a bit further.  I can't guarantee that I'll be make any progress on this as it's an older and unmaintained interface by ANSYS.

Hello @akaszynski,
Thank you for your quick reply! I will try to have access without VPN. Physical access to the computer should take place soon, before the newer interface releasing.
Thanks.

Please let me know if it works out.  If not, there might be a more fundamental problem and I'll have to look at that instead.

After wrestling with this for part of the day, I've concluded that the main issue here is having multiple adapters and the AAS (CORBA) service not knowing which adapter to connect to.  It appears that if there's more than one network adapter, the ANSYS AAS service will create a server on one adapter and CORBA from Python will attempt to talk with the other adapter.
This is quite frustrating, and there's no real workaround other than to disable all but one adapter, which isn't an option on VPN.
The good news is that ANSYS will be using a new interface for Windows for the next release, and with luck I'll be able to add the corresponding interface here at pyansys.

Another issue I've noticed occurs with MAPDL v20 (2020R1 +), and I've recently patched that in pyansys=0.40.2.  It's unlikely to fix this issue as well, but you might want to give the latest release a shot.

To those still on this thread, please try 0.41.0 and see if it works for you.  I've patched a variety of issues.  Please take a look at the updated docs as the API has changed.

I updated pyansys to 0.41.0 but it still does not work.
I tried running this code:
import os
import pyansys

path = os.getcwd()
ansys = pyansys.Mapdl(run_location=path, jobname='file', override=True)

ansys.prep7()
ansys.k(1, 0, 0, 0)
ansys.save()
ansys.exit()

First I thought it runs without problems because it tried to connect to ANSYS but nothing happened for a long time. I was looking in the Task Manager the whole time and ANSYS didn't start. After some minutes I got this error message:
2020-06-11 07:54:16,255 [INFO] pyansys.mapdl: Connecting to ANSYS via CORBA
2020-06-11 07:56:16,303 [ERROR] pyansys.mapdl: Unable to start ANSYS within 120.0 seconds
Traceback (most recent call last):
  File "C:/Users/pi/Python/Project/Test.py", line 7, in <module>
    ansys = pyansys.launch_mapdl(run_location=path, jobname='test',override=True)
  File "C:\Users\pi\AppData\Local\Continuum\anaconda3\envs\environment_pi\lib\site-packages\pyansys\mapdl.py", line 586, in launch_mapdl
    log_broadcast=log_broadcast)
  File "C:\Users\pi\AppData\Local\Continuum\anaconda3\envs\environment_pi\lib\site-packages\pyansys\mapdl_corba.py", line 85, in __init__
    log_apdl)
  File "C:\Users\pi\AppData\Local\Continuum\anaconda3\envs\environment_pi\lib\site-packages\pyansys\mapdl.py", line 879, in __init__
    self._launch()
  File "C:\Users\pi\AppData\Local\Continuum\anaconda3\envs\environment_pi\lib\site-packages\pyansys\mapdl_corba.py", line 152, in _launch
    raise TimeoutError(err_msg)
TimeoutError: Unable to start ANSYS within 120.0 seconds

I´m still working with ANSYS 19.1

Hi @akaszynski ,
Same here, I updated pyansys to 0.41.0 but it still doesn't work.
Same error code.
I use ANSYS 18.0 through a VPN with RDC in Windows 10.

Hi @Flalancette.  Sadly, I think that there won't be a way around the VPN issue.  0.41.1 and newer works without VPN, and I'd avoid using 0.41.0 as the CORBA interface had a few bugs that were patched in later versions.

Closing due to inactivity.  Anyone reading this issue in the future should note that the CORBA interface sadly defaults to a network adapter IP rather than simply using 0.0.0.0, which means that if the IP address isn't directly reachable (i.e. it's a virtual network adapter), then CORBA won't work.  This should be corrected in a future MAPDL API.

authors: Flalancette SairamPrabhakar akaszynski pi314a

repo: akaszynski/pyansys


text:
Gretty and Gradle 3.1

I am receiving an error from a gradle build file when gretty is added to the mix.
"> Cannot change strategy of configuration ':overlays' after it has been resolved."
I am able to run the build without error if gretty isn't added as a plugin.  I am including the build file in hopes that I can get some help with what the error possibly means or how to bypass it.
buildscript {
    repositories {
        jcenter()
    }
    dependencies {
        classpath 'org.akhikhl.gretty:gretty:1.4.0'
    }
}

apply plugin: 'java'
apply plugin: 'maven'
apply plugin: 'org.akhikhl.gretty'

version = '2'
archivesBaseName = 'service'

compileJava {
    sourceCompatibility = 1.8
    targetCompatibility = 1.8
}

configurations {
    overlays
}

repositories {
    mavenLocal()
    mavenCentral()
}

dependencies {
    overlays 'org.eclipse.jetty:jetty-distribution:9.3.9.v20160517@zip'
}

task overlayJetty(type: Copy) {
    def bundleRoot = 'build/bundle/project-' + project.version + '-bundle'
    def jettySrc = configurations.overlays.find {
        it.absolutePath.contains('jetty')
    }
    from zipTree(jettySrc)
    into bundleRoot
    includeEmptyDirs false
    exclude('**/README.TXT')
    exclude('**/VERSION.txt')
    exclude('**/license-eplv10-aslv20.html')
    exclude('**/notice.html')
    exclude('**/demo-base/**')
    exclude('**/webapps/**')
    exclude('**/start.ini')
    eachFile {
        def path = it.relativePath.pathString
        path = path.replaceFirst('jetty-distribution-9.3.9.v20160517/', '')
        it.setRelativePath(RelativePath.parse(it.relativePath.isFile(), path))
    }
}

task archiveBundle(type: Zip, dependsOn: overlayJetty) {
    from 'build/bundle'
    archiveName 'stream-service-' + project.version + '-bundle.zip'
}

task bundle(dependsOn: archiveBundle)

It was an issue with gradle.  I have fixed it.

repo: akhikhl/gretty

license: mit


text:
Iimage starts to be dragged in the browser

Hello. For me, the problem is that the image starts to be dragged in the browser, when I try to move it with the mouse. You can see this behavior in this video.
slick.mp4.zip
I did not find this problem in the original slick. You can fix it or suggest what to do?

I solved the problem with the help of -webkit-user-drag: none;

repo: akiran/react-slick


text:
Shared stahes

Hey there! Sorry for disturbing but can you please do shared stashes for co-op split screen in Outward DE like it was in default game. This mod that you did (MustStashes) is awesome but it can open stash everywhere and need a buttom to activate it. But can you do like it was in default game (2 players have same stash and open it only near stash) pretty please. Thank you!

Created a new mod "HostOnlyStash" that changes the default opening of the stashes to only open the world host's stash.  Tested in split screen but not online play.
Debugging the 'MustStash' mod for an issue but I am also adding a config option for host only (updating config descriptions since 'only in towns' was already an available option).

Thank You a lot!!!

repo: akiroth/Outward


text:
Highlighting does not put text in the primary buffer

Ordinarily in Linux, highlighting some text copies the text into the primary buffer which can be pasted with middle click. This does not seem to happen with Goneovim.
Though it might be argued that one should use vim bindings to copy and paste, sometimes it makes sense to do it the gui way.

Hi :)
I understand the opinion, but I believe there are users who do not like that behavior.
By putting the following settings in init.vim, you can copy the word under the cursor with a double-click and paste it with a right-click. I think it is the vim way that users get the behavior they expect from a setting like this.
be xterm
nnoremap <2-LeftMouse> bveyve
nnoremap <RightMouse> <Esc>p

@hgomersall
Sorry I haven't been able to reply.
It's not that I don't like the behavior, it's that I'm not comfortable defining such behavior by default. neovim can be configured to get the behavior you want, and your  expected behavior can be achieved t the configuration.
If the configuration I suggested above does not work, it may be in conflict with some other mapping. How about starting Goneovim as follows?
/path/to/goneovim -u NONE --cmd 'be xterm' --cmd 'nnoremap <2-LeftMouse> bveyve' --cmd 'nnoremap <RightMouse> <Esc>p'

By the way, I have fixed a bug related to this isssue in goneovim regarding triple clicks(c47a634a22a31c294196e4205877b37e41c997af).

Thanks for the pointers. If I can configure things appropriately, I'm happy.

authors: akiyosi hgomersall

repo: akiyosi/goneovim


text:
exclusively use the tst

So I am using an older config for tst by you and wanted to do so too in a new setup. There seems to be the need for css in the userchrome though and I dont really know what exactly I need

You'll need userchrome-hover or userchrome-static based on which kind of sidebar you want. These would style the sidebar(remove header, remove splitter, etc.). Both of them also use config.css to set some variables mainly sidebar width(s).

ok so I have to put css into the extension itself and import userchrome-hover and config into my main file if I want it to be in hover mode? will the config affect anything else?

Just realized I never removed tabline-removing code from userchrome-hover. Will fix that soon. Meanwhile, yeah include userchrome-hover and config.css in your userchrome. And remove line 51-62 from userchrome-hover. So these lines towards the end:
/* hide tabs */
.tabbrowser-tab {
    display: none;
}

#tabs-newtab-button {
    display: none;
}

.titlebar-spacer {
    display: none !important;
}

Thank you very much! I keep them if I want to remove tabline though?

Yep. Could also include hide-tabline.css but I'm pretty sure they do the same thing as those three rules.

okay, I have some final "issues". I would like to have the old icon behaviour, aka have the icon go right so its not visible when hovering tabs. Is the transform (i think it should be one?) in the extension or userchrome?
when hovering the sidebar it pops out but does so instantly. Where is that handeled?

Yes it's handled in TST's css. It'll be a lot of work in treestyletab/custom.css but if you're using treestyletab/custom-hover.css (which you should be since you want hover tabs?) you can achieve that by changing its line #188. Keep it as is except change the translateX(-20px) to something like translateX(30px). Notice the positive value, that will shift the icon right when hovered.
No its not exactly Nord. The palette is part of a color scheme I made few months ago for my neovim setup. You can find rest of the colors here.

Okay, this should resolve the other issues but now I am confused again. I want to change the width values. In config.css you handle these via variables but I cant find the variables

Its the --sidebar-width and --sidebar-collapsed-width variables around line 29.


text:
How disable swipe on drawer navigation

Version
Latest
Right now in my app if a user swipes to the left from the drawer navigation (when it's open) they are taken back to the login screen, I would like to disable this from happing

+1

Add this gesturesEnabled={false} into the Scene

@Mimicx, you mean drawer scene ?

I have this

And it does not work.
It does hide the navBar, but it still allow to see the drawer

authors: AlmogRnD Mimicx edoantonioco tonygriv

repo: aksonov/react-native-router-flux


text:
SQLi

40 added
40 x Injection attacks

47 x Injection attacks (SQLi)

repo: akto-api-security/tests-library


text:
Bad linking correction between label and input

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Bug fix, now if you click on the label email it will select the right input.

What is the current behavior? (You can also link to an open issue here)

If you click on email label the name input will be selected.

@geekow thanks for your PR.

authors: geekow lexzhukov


text:
how to upgrade from versio 4.0.1 to version 5.0

i have project work with ngx admin version 4.0.1, how i can update to latest version ?

You might want to add some information, this post might help https://github.com/akveo/ngx-admin/issues/5642. Also look at the pull request that merged the update to 5.0 and angular 9.

repo: akveo/ngx-admin


text:
Encoding configuration support

new optional Maven plugin parameter sourceEncoding (defaults to UTF-8)

Resolves #94

Coverage increased (+0.07%) to 89.467% when pulling 02b9a624101fb66a1d29385731b203ddfc83266c on feature/encoding-config-support into b6544e282c12e0305435609ba8e46e2c4f5d3063 on master.

authors: coveralls cstettler

repo: alainsahli/confluence-publisher


text:
Metric Hyperparameters investigation/sanity check

With the strange behaviour of PARC when evaluating ImageNet-1k we wish to evaluate the hyperparameters used to see these are the source of the issue. This method can be generalised away from PARC however, with sanity checks for the hyperparameters of the other metrics looking to be worthwhile.

37 should be done before this to recreate the method properly.

This should be independent from #37 I think (btw if you write #<issue_number> it links the issue for you) - we know the number of parameters will (almost definitely) correlate with fine-tuned performance, we want to tease out whether the base PARC metric adds anything independently of that.

Closed as duplicated by #20

Closed as duplicated by https://github.com/alan-turing-institute/ARC-LoCoMoSeT/issues/20

repo: alan-turing-institute/ARC-LoCoMoSeT


text:
Easier local deployment

Rather than having the manual developer doc instructions, can we wrap everything inside a docker container and single executable script?

Below is a simple script that I am using to deploy a local instance of the app. Also offers the option to restart the database. I don't think we should commit this to the repo:
#!/bin/bash

# REMEMBER TO ACTIVATE YOUR PYTHON VIRTUAL ENVIRONMENT BEFORE RUNNING THIS SCRIPT!
# THIS SCRIPT SHOULD BE RUN FROM THE ROOT LEVEL OF THE REPOSITORY

# Load the environment variables
source .secrets/dtenv_localdb.sh

# Take in an argument called 'restart-db' to optionally restart the database
if [ "$1" == "restart-db" ]; then
    echo "Restarting the database"
    # stop and delete server container
    docker stop $DT_SQL_DBNAME
    docker rm $DT_SQL_DBNAME

    # start the postgres docker container
    docker run --name $DT_SQL_DBNAME -e POSTGRES_PASSWORD=$DT_SQL_PASS -p 5432:5432 -d $DT_SQL_USER

    # create the database
    createdb --host $DT_SQL_HOST --username $DT_SQL_USER $DT_SQL_DBNAME -W
fi

# Run the backend. This will run the backend in the background to leave the terminal open for the frontend.
cd dtbase/backend
./run_localdb.sh &

# Run the frontend
cd ../webapp
./run.sh

# NOTE: THE BACKEND WILL CONTINUE TO RUN IN THE BACKGROUND AFTER THE TERMINAL IS CLOSED.
# TO FIND AND KILL THE BACKGORUND PROCESS, RUN ps TO SEE ALL RUNNING PROCESSES AND THEN KILL THE PROCESS WITH IT'S PID ID WITH KILL <PID>

repo: alan-turing-institute/DTBase


text:
Document and manage all TRESA processes

Goal Title
What will this work achieve?
Smooth running of Turing TRE deployments
Description

Work with projects to improve current documentation
Ensure all standard operating procedures are recorded

Definition of Done
When will this be considered as succesfully completed?
Ongoing
Details

RACI

Accountable team or person: TRESA
Responsible team or person: RAM, RPM
Informed and consulted people: project teams, PMU

Estimated effort

RAM: Can be incorporated under accountability for #32
RPM: time for support here can be included with #55

High effort
Story points (Above 10, sum of monthly issues effort)

Resourcing
August

REG: 0.1

Task and issue breakdown
Breakdown in specific tasks of maximum a month duration, tasks and issues may be added as necessary
Issues may span across repositories when necessary

issue alan-turing-institute/data-safe-haven-team#X
issue alan-turing-institute/data-safe-haven#X
issue alan-turing-institute/trusted-research
issue sa-tre/satre-specification#X
issue sa-tre/satre-team#X

Checklist

[x] This Story have been agreed with project members, it tackles prioritised work

[x] If not: Label as ForPrioritisation so it discussed in the next monthly meeting, do not set a status

[ ] I have included this Story in the agreed upon Milestone, set status as Planned

[ ] If not: set status as Backlog, to be Planned via weekly meetings/discussions

[x] The work to be done is likely to span over a month
[ ] I have broken down the work in monthly issues and added them above
[ ] I have labeled this issue according to its main project: SATRE, TRESA, CORE DSH (ELA) or other (please agree and create a new label if necessary)
[ ] I have stimated the total effort and added it in the body (under Details) but left the issue field blank

@JimMadge @harisood will this story cover what we plan to do in the new year? Probably needs to reflect processes improvement rather than only documenting them in the title.
We can complete the main comment together when we plan

Agree with @JimMadge, I would just drop the 'Document and'

I shall create a new story then

Jan planning
This is a focus of this month, to hand over this stuff to TRESA
Resourcing

REG

0.2 @JimMadge

RAM: 0.1
RPM: 0.2

authors: Davsarper harisood


text:
Add documentation

[x] Docstrings for modules, classes and major functions
[ ] Introductory page, with general description of the package and showing a basic example
[ ] Link to the tutorial (or: include notebooks in sphinx pages?)
[x] Add instructions to README for building the docs

Overview page is empty?
https://setvis.readthedocs.io/en/latest/overview.html

Thanks, added to the list!

repo: alan-turing-institute/setvis


text:
Refactor reducer

Reference Issues/PRs
#955

removed forecasting mixins and replaced with tags.
moved fit in _Reducer. there was one check in this fit that was moved to all the other _fit methods
added fh as parameter to all the _fit methods and adjusted docstring as such

Note that locally I checked only the tests for reduce, and those all passed. But who knows if other tests will fail... :/

@fkiraly Please review this

Just a comment: Having a _fit method in the _Reducer class which implements the check_window_length call and then delegates to another _internal_fit(or whatever you want to call it) would be an alternative but seems a bit overcomplicated.

I had similar thoughts, but also think it would have been overcomplicated

tests passed overnight - tests have re-started due to a PR that only fixed a broken link, so force-merging

authors: Lovkush-A fkiraly

repo: alan-turing-institute/sktime


text:
Typo in transformations.rst fixed

Reference Issues/PRs

What does this implement/fix? Explain your changes.

Does your contribution introduce a new dependency? If yes, which one?

What should a reviewer concentrate their feedback on?

Any other comments?

PR checklist

For all contributions

[ ] I've added myself to the list of contributors.
[ ] Optionally, I've updated sktime's CODEOWNERS to receive notifications about future changes to these files.
[ ] I've added unit tests and made sure they pass locally.

For new estimators

[ ] I've added the estimator to the online documentation.
[ ] I've updated the existing example notebooks or provided a new one to showcase how my estimator works.

Thanks @AreloTanoh - now merged! 🎉

authors: AreloTanoh mloning


text:
[ENH] Address deprecated references in datatypes modules

Reference Issues/PRs
Fixes #2049
Changes:
pd.Int64Index
To
pd.Index
Files:

_panel/_check.py
_series/_check.py
_hierarchical/_check.py

What does this implement/fix? Explain your changes.

Fixes future warnings in datatypes modules
PR checklist

For all contributions

[x] I've added myself to the list of contributors.
[ ] Optionally, I've updated sktime's CODEOWNERS to receive notifications about future changes to these files.
[x] I've added unit tests and made sure they pass locally.

Do you think this pd.Index(dtype='int64') will properly replace 'Int64Index'?

Perhaps - I don't know. Even if, it may be that consistent changes may be required throughout, e.g., in the ForecastingHorizon.

@SadmanSyfe
I don't think so. pd.Int64Index is a name of the class/type. When we call pd.Index(dtype='int64'), without any collection, it tries to create an object an fails, like so:
>>> pd.Index(dtype='int64')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/crocoder/anaconda3/lib/python3.8/site-packages/pandas/core/indexes/base.py", line 372, in __new__
    raise cls._scalar_data_error(data)
TypeError: Index(...) must be called with a collection of some kind, None was passed

@fkiraly I think that can work, but will involve several changes across the repository. A simple search leads to 26 entries of pd.Int64Index. And all the errors will have to go under if-else like strucutre.

@fkiraly
Most of the occurrences are type checking or tests in which instantiation is done.
One non-test case where it is instantiated is here.

I am working on the fix discussed above on this PR: #2082.

great! let's make sure we learn from each other here - it's fine to follow two different approaches, I also can't say which one will be the one solving the issue. Ultimately, it's going to be a joint contribution of everyone involved, I suppose.

This PR can be closed. The issue https://github.com/alan-turing-institute/sktime/issues/2332 is resolved. Sorry, @gchhablani, these warnings were too annoying.

@khrapovs No issues! Thanks a lot for fixing it.
I was not able to understand how to fix these errors. 😅

authors: SadmanSyfe fkiraly gchhablani khrapovs


text:
v1.0.4

Update fstream version to remove graceful-fs warning

P.S. Can you upload this module to NPM, because it is no use of changes if it is not pushed?
Thank you.

Coverage remained the same at 74.286% when pulling 2dc36271f77deab50d74dab6be582592cae812c3 on GermanBluefox:master into 39d82db457ca08e5486c58f5a02aa0ccbb5510ab on alanhoff:master.

The problem is, when the users installs tar.gz they get warning about graceful-fs is too old. And because the users are not so experienced, they struck immediately an alarm, that something goes wrong. I am tired of it and want fix it.
Could you please push version 1.0.4 to npm?

OK. I create a fork. :(

Sorry for the delay. LGTM.

authors: GermanBluefox alanhoff coveralls

license: isc


text:
Status always pending

Hi,
Really great service, seems like https://david-dm.org/char0n/ramda-adjunct is always in pending mode. Can you think of any reason why ?
Thank you

Hi, @char0n.
I don't see dependencies section in
https://github.com/char0n/ramda-adjunct/blob/master/package.json
It seems the reason of this status.

Hi @aivus,
Some time after I reported this issue It started to work on it's own. Then I removed all the dependacies from package.json so I did not need the badge anymore. Thanks anyway. I can close this issue as resolved for now.

This is a bug which I'm hoping has now been resolved by https://github.com/alanshaw/david-www/commit/6436f07bec18384d0d83a8e89b7fb40286da5bc8. If you don't have dependencies in your package.json your badge should be green and read "dependencies none", not pending.

authors: aivus alanshaw char0n

repo: alanshaw/david-www


text:
Not working with reanimated v3

hello, there is a bug with reanimated 3.

project detail:
"react": "18.2.0",
"react-native": "0.71.2",
"react-native-reanimated": "^3.0.2",
"react-native-reanimated-player": "^2.3.0",

hey @itsnyx , yeah, it's does not supprot Reanimated v3 yet, let me find some time to add support for it!

@alantoa thanks for the response.

Hi @alantoa, Our project requires to use Share Elements. So is there a workaround for using reanimated 3? Thank you so much

authors: alantoa itsnyx vdr-mm-quan

repo: alantoa/react-native-reanimated-player


text:
shaiport binary and nobody user privileges

Hi!
There is no sound with shairport binary and 'nobody' user privileges. But with shairportl.pl everything is ok. It seems that is the pulseaudio output.
$ sudo su -m nobody -c "/usr/local/bin/shairport -a ff"
LogLevel: 1
AirName: ff
HWID: ,nf;8
HWID_Hex(12): 002C6E663B38
********** RECV OPTIONS **********
********** RECV ANNOUNCE **********
********** RECV SETUP **********
********** RECV RECORD **********
********** RECV SET_PARAMETER **********
No protocol specified
xcb_connection_has_error() returned true
Home directory /root not ours.
waitpid(): No child processes
/root/.esd_auth: Permission denied
********** RECV OPTIONS **********
^C
$ sudo su -m nobody -c "/usr/local/bin/shairport.pl -v"
Listening...
New connection from 192.168.1.33
REQ: OPTIONS
REQ: ANNOUNCE
REQ: SETUP
launched decoder: 10561 on port: 6000
REQ: RECORD
No protocol specified
xcb_connection_has_error() returned true
Home directory /root not ours.
REQ: SET_PARAMETER
/root/.esd_auth: Permission denied
requesting resend on 6 packets (port 54044)
REQ: OPTIONS
REQ: OPTIONS
$ pulseaudio --version
pulseaudio 0.9.22
$ uname -a
FreeBSD incubus.bsd 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan  3 07:46:30 UTC 2012     root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64

As you say, it's a permissions issue. Looks like it's trying to read .esd_auth as $HOME is set to /root.

Yes, I see. But with shairportl.pl everything is ok. It works with this error without any problems.

Then it's probably using a different sound output?

authors: abrasive incubus

repo: albertz/shairport


text:
[Translation] 新孵化项目提案

原文：https://cwiki.apache.org/confluence/display/INCUBATOR/New+Podling+Proposal?desktop=true&macroName=markdown
翻译：https://hackmd.io/@tedliu1/Bkm5nKhmT/edit
微信公众号：https://mp.weixin.qq.com/s/2L5HSDxx2JkohjrYfkpiwQ

已将飞书文档内容改为 Markdown 格式，并可以协同编辑：https://hackmd.io/@tedliu1/Bkm5nKhmT/edit

文档已提交 https://alc-beijing.github.io/alc-site/post/apache-way/new-proposal-template-guide/

repo: alc-beijing/alc-site


text:
question: custom kubeconfig from cli argument

Hello,
for my setup I use multiple kubeconfig files a'la
kubectl --kubeconfig test-context.yaml get ns or kubectl --kubeconfig dev-context.yaml get ns, each defining own set of contexts. There might be aliases set a'la kubectltest or kubectldev to speed things up, as I use different contexts on regular basis. Reason for not putting them into single default kubeconfig is that clusters get regenerated sometimes and it is easier for me to download current config from Rancher in case of update rather then trying to merge them into single file (default homedir kubeconfig has configs for e.g. my local k8s context/cluster etc).
I am trying to use rbac-tool and cannot combine it with specific kubeconfig. There is --cluster-context cli switch, but it works inside current (default) contexts, and I want my specific config.
If I use kubectl --kubeconfig some.yaml rbac-tool viz it says flags cannot be placed before plugin name: --kubeconfig.
What am I doing wrong and how can I make it work?

Thanks @glebsts
Indeed  --cluster-context works against the default kubeconfig file.
Did you try to override kubeconfig file using KUBECONFIG env variable ?

Thanks, @gadinaor-r7 , will try later. That would be a workaround. Would you accept PR with new flag support?

Sure @glebsts

repo: alcideio/rbac-tool


text:
Revert "Always validate building docs in CI for PRs"

Reverts alcionai/corso#1423

I think it would be better to enable building cli docs instead https://github.com/alcionai/corso/pull/1435

authors: meain ntolia

repo: alcionai/corso


text:
⚡  Ability to use standalone binary without installing libraries (feature flags)

What problem does your feature request solve?
Currently, The program will immediately crash if libvip or ffmpeg is not installed, even if the user does not need the image/video capability
With this feature, The user can run the program without installing additional libraries
Describe the solution you are proposing.
A feature flag in the parameters of the program, if the user want to incluse image/video capabilities
Describe alternatives you have considered.
No response
Importance
Could Live Without
Additional Context

[ ] This missing feature presents as a bug.
[ ] This missing feature is forcing me to consider alternatives.

Good idea, will available on next release
currently still under development https://github.com/aldinokemal/go-whatsapp-web-multidevice/pull/136

authors: aldinokemal sayyidyofa

repo: aldinokemal/go-whatsapp-web-multidevice


text:
🛑 Teddit is down

In 37e686a, Teddit (https://teddit.alefvanoon.xyz) was down:

HTTP code: 502
Response time: 190 ms

Resolved: Teddit is back up in 5767acb.

repo: alefvanoon/Status


text:
Cannot find module '/app/index.js'

docker run --rm -v /root/www/app/index.js:/app/index.js alekzonder/puppeteer:latest
module.js:549
throw err;
^
Error: Cannot find module '/app/index.js'
at Function.Module._resolveFilename (module.js:547:15)
at Function.Module._load (module.js:474:25)
at Function.Module.runMain (module.js:693:10)
at startup (bootstrap_node.js:191:16)
at bootstrap_node.js:612:3

i'm wrong

repo: alekzonder/docker-puppeteer


text:
Substitution reference is not highlighted

Consider this part of a Makefile:
sources := $(objects:.o=.c)
sources := $(patsubst %.o,%.c,$(objects))

(from https://www.gnu.org/software/make/manual/html_node/Text-Functions.html)
and this screenshot of neovim with treesitter syntax highlighting:

:TSPlaygroundToggle reveals following syntax tree:
variable_assignment [0, 0] - [1, 0]
  name: word [0, 0] - [0, 7]
  value: text [0, 11] - [0, 27]
    substitution_reference [0, 11] - [0, 27]
      text: word [0, 13] - [0, 20]
      pattern: word [0, 21] - [0, 23]
      replacement: word [0, 24] - [0, 26]
variable_assignment [1, 0] - [2, 0]
  name: word [1, 0] - [1, 7]
  value: text [1, 11] - [1, 41]
    function_call [1, 11] - [1, 41]
      arguments [1, 22] - [1, 40]
        argument: text [1, 22] - [1, 40]
          variable_reference [1, 30] - [1, 40]
            word [1, 32] - [1, 39]

I would expect that the dollar sign with the parentheses are highlighted in the first line.

Sorry, this was a mix up on my side. I had installed nvim-treesitter with its own highlights.scm which is responsible for not highlighting dollar and its parentheses of substitution references.
https://github.com/nvim-treesitter/nvim-treesitter/blob/73cd1f189bf19e99af9b1349cdca590a40b985b0/queries/make/highlights.scm

repo: alemuller/tree-sitter-make


text:
how to auto close drawer

drawer open and we switch to an other screen when we come back the drawer remains opened in there any way to auto close drawer when we switch to any other page or screen

Close the drawer with controller on the button pressed inside the drawer
Sent from my iPhone

On 19 Jul 2022, at 7:58 PM, Bisharat Ali @.***> wrote:

drawer open and we switch to an other screen when we come back the drawer remains opened in there any way to auto close drawer when we switch to any other page or screen
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.


text:
Sample App stopped Working

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:
I don´t really understand why he problem occoured. I restarted the Raspberry and after that the AVS Sample App fails to start....there are Errors with the SSL-Certificat and the Port Audio Wrapper. I already testet the Mic. It is working and if i record with it all works fine
What is the expected behavior?
Sample App should Run
What behavior are you observing?
Sample App fails to build
Provide the steps to reproduce the issue, if applicable:

Tell us about your environment:
Rasbian on Raspberry Pi, with  USB Microphone
What version of the AVS Device SDK are you using?
  <x.y.z>

Tell us what hardware you're using:

[ ] Desktop / Laptop
[ X] Raspberry Pi
[ ] Other - tell us more:

Tell us about your OS (Type & version):

[ ] Linux
[ ] MacOS
[ X] Raspbian Stretch
[ ] Raspbian Jessy
[ ] Other - tell us more:

AVS-Log.txt

Hi @nox2213,
Which version of the SDK are you using, and how did you install it? The failure seems to be related to PortAudioMicrophoneWrapper failing to initialize:
2019-06-17 18:19:32.252 [  1] C PortAudioMicrophoneWrapper:Failed to open PortAudio default stream:errorCode=-9997
Did you make any changes to your microphone setup between restarts?

The SDK Version is 1.12.0. i didn´t changed any settings, thats why i´m some sort of clueless how to begin the troubleshooting

So. I reinstalled the whole Raspberry from the start. I now have SDK 1.13.0, but still the Problem with the Port Audio error -9997(Log attached)
AVS-Log2.txt

Hi nox2213,
Can you tell us a little more about your set-up:

What version of Raspberry PI?
When you say 'reinstalled whole Raspberry from the start', do you mean that you re-flashed the stretch image?
Can you show us the output of 'arecord -l' and the contents of /home/pi/.asoundrc ?

Thank you,
-SWH

I had this same problem after updating to the 4.19 kernel. All my microphone tests have passed. This issue has been reported several times with no real solution.
https://github.com/alexa/avs-device-sdk/issues/1359

I am facing the same issue . Please Help.

Not a full solution, but in my case I needed to kill the running pulseaudio daemon first, after which avs was able to open the PortAudio default stream.

I am closing this issue due to inactivity. Please feel free to re-open it if it has been closed in error.

authors: DMaiorino Vaishnavikumara kclchan kjkh nox2213 scotthea-amazon thardbarger

repo: alexa/avs-device-sdk


text:
https://api.pirateweather.net is down?

Not really an issue here per say, wondering if this is some AWS outage?
I'm located in the US.

Same issue here.
According to my HA logs, Pirate Weather was down for almost 6 hours coinciding withHukuma1's report, then came back online.
However, it is now down again, having gone down about 3 hours ago.

Came back here for this. Down for me again as well. :/

Bah humbug! Thanks for the reports here- logged in and fixed it, so we're back online now ☀


text:
🛑 Craftify is down

In a092dc2, Craftify (https://craftify.nl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Craftify is back up in 1f36d4b.

Resolved: Craftify is back up in 1f36d4b.

repo: alexandervantrijffel/upptimemonitoring


text:
add coerce options for Number, Date and ObjectID

Close #9

Coverage decreased (-0.6%) to 89.478% when pulling c409d2688f34c525ba585e334e9805afd465563e on ponury-kostek:master into d26aefb9392ea2f09e8a14e7f8f1ee48fcc7b4e7 on alexandrajs:master.

authors: coveralls ponury-kostek

repo: alexandrajs/sandstorm


text:
Is this bloom filter threadsafe?

That is, is calling .add and .mightContain concurrently from many different threads going to work?

I wrote a short program to try to find incorrect behavior in the presence of multiple threads, and it unfortunately appears to find some. I think that counts as a witness proof that the bloom filter is not thread-safe.
Looking at the implementation: the backing array would need to use atomic operations like getAndBitWiseOr or else do some locking, but it does neither. It looks like the Java 9 VarHandle API would make this all very possible and efficient using ByteBuffer's, but I've got no idea how to do that without dropping Java 8 support.
https://github.com/alexandrnikitin/bloom-filter-scala/blob/b2c41c02f694529acbb3d22237d4a192b845d197/bloom-filter/src/main/scala/bloomfilter/mutable/UnsafeBitArray.scala#L19-L26

Will there be a thread-safe implementation of this Bloom filter ?

authors: LeifW harpocrates rac021

repo: alexandrnikitin/bloom-filter-scala


text:
Update cats-effect, cats-effect-laws to 2.4.1

Updates

org.typelevel:cats-effect
org.typelevel:cats-effect-laws

from 2.2.0 to 2.4.1.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Applied Migrations

github:typelevel/cats-effect/v2_4_0?sha=v2.4.0

Documentation:

https://github.com/typelevel/cats-effect/blob/v2.4.0/scalafix/README.md

Files still referring to the old version number
The following files still refer to the old version number (2.2.0).
You might want to review and update them manually.
build.sbt
src/main/g8/build.sbt

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

labels: test-library-update, semver-minor, scalafix-migrations, old-version-remains

Superseded by #184.


text:
🛑 Hacker News is down

In 1bae4d8, Hacker News (https://news.ycombinator.com) was down:

HTTP code: 502
Response time: 221 ms

Resolved: Hacker News is back up in f1bc6c5 after 10 minutes.

repo: alexarnimueller/upptime


text:
🐛 [Mealie] Direct link to meals plan page redirects incorrectly

Description
Using the Mealie add-on on Home Assistant Yellow, within Mealie the meal plan opens fine, however when opening a new browser tab to http://x.x.x.x:9090/group/mealplan/planner/view the browser redirects to http://127.0.0.1:9000/group/mealplan/planner/view/
Reproduction steps
1. In the Mealie menu, click on "Meal Planner"
2. Copy the URL of the meal planner page (e.g. http://x.x.x.x:9090/group/mealplan/planner/ )
3. Open a new browser tab and paste the copied address
4. The Meal Planner page does not load. The URL in the navigation bar will change to http://127.0.0.1:9000/group/mealplan/planner/view/

Addon Logs
When loading the Meal Planner via the Mealie menu - 200 response:

127.0.0.1:39718 - "GET /api/groups/mealplans?page=1&perPage=-1&start_date=2024-01-28&end_date=2024-02-03 HTTP/1.1" 200
[28/Jan/2024:16:41:06 +1100] 200 -(192.168.1.221) GET /api/groups/mealplans?page=1&perPage=-1&start_date=2024-01-28&end_date=2024-02-03 HTTP/1.1 (Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0)

When loading the Meal Planner via the URL directly in any browser window - 307 response:

127.0.0.1:45846 - "GET /group/mealplan/planner/view HTTP/1.1" 307
[28/Jan/2024:16:41:33 +1100] 307 -(192.168.1.221) GET /group/mealplan/planner/view HTTP/1.1 (Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0)

Architecture
No response
OS
HAos

Easiest way would be for me to drop ssl and just propose a

Without SSL when i try refresh on user panel i still got redirect to http://localhost:9000/user/profile/

Currently this issue still occurs.

Can confirm, I see the same issue. So far I've given up trying to figure out why it redirects me when I try to open the meal planner using a direct link. Direct links to other areas (like a recipe) works fine.

Without SSL when i try refresh on user panel i still got redirect to http://localhost:9000/user/profile/

As per the bug report it was done using http. I've not tested https so not sure if there's any difference there, but yeah without ssl it definitely happens

As per the bug report it was done using http. I've not tested https so not sure if there's any difference there, but yeah without ssl it definitely happens

I use https, and also get redirected same as you.

I'm also having this problem. I first noticed this with the invite link, which is generated/emailed in this format:

https://mealie.mydomain.com/register?token={token}
When I go to that link, it immediately refreshes as:
http://localhost:9000/register/?token={token}
Note that it changes my domain to “localhost:9000” AND it adds a slash between “register” and the question mark. If I change the domain back (but leave the added slash), then it works:
https://mealie.mydomain.com/register/?token={token}
Likewise, when I navigate to Mealy locally (http://10.0.1.10:9091/ -- fyi, I use 9091 because another service uses 9090), the generated invitation link looks like http://10.0.1.10:9091/register?token={token} which then redirects to http://localhost:9000/register/?token={token}. And similarly to using the external link, if I adjust the registration link to include that extra slash (i.e. http://10.0.1.10:9091/register/?token={token} ), then the registration page loads and I can register a new user.

authors: AndrewDarlington alexbelgium nickj-git shirou93 thuesen

repo: alexbelgium/hassio-addons


text:
🛑 Web Busy Light Demo is down

In 3a9ad86, Web Busy Light Demo (https://workfromhome.capricehosting.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Web Busy Light Demo is back up in b428ab9.

repo: alexchapar/status-page


text:
Minimally support Visual Studio 2019.

This would be the bare minimum for fixing #385.
It'd need more fleshing out later, but should support the case when the environment variables are already set.

Thanks!

authors: TheGoddessInari alexcrichton

repo: alexcrichton/cc-rs


text:
Only set CMAKE_SYSTEM_NAME=Linux when cross-compiling to Linux

Previously, this would set SYSTEM_NAME unconditionally whenever targeting Linux.
Unfortunately, Cmake unsets some other variables when SYSTEM_NAME is set;
in particular CMAKE_SYSTEM_VERSION and CMAKE_SYSTEM_PROCESSOR.
To avoid regressing other builds, this only sets SYSTEM_NAME when cross-compiling,
which was already broken before SYSTEM_NAME was set.
Fixes https://github.com/alexcrichton/cmake-rs/issues/138 (I confirmed locally that this fixes the build for boring-sys).

Is there any confidence that this is the right fix? I don't know why cross-compiling would somehow be different than not. If there's not confidence that this is the right fix then I'd prefer that this would be reverted for now.

No, I'm fine with reverting, I was just trying to keep the churn low. I changed this PR to be a straight revert instead.

Thanks for the quick review!

repo: alexcrichton/cmake-rs


text:
Add environment variable to find GSSAPI

This change allows us to set the location for GSSAPI.
This would be useful on systems where the library is not found at the usual location /usr or if the client wants to set it manually.
I tried to make the behaviour similar to DEP_NGHTTP2_ROOT.

FWIW the DEP variables are not meant to be set by users, they're set by Cargo because dependencies of this crate are named nghttp2 and such (via the links key in the manifest). If this isn't going through Cargo for dependencies, could the env var be named differently?

Would GSSAPI_ROOT be okay?

Seems fine by me!

Updated the commits. Thank you for your time!.

authors: alexcrichton theawless

repo: alexcrichton/curl-rust


text:
Distinguish between functions belonging to different gateways

Expected Behavior
If there are multiple gateways in the same swarm, it should be possible to configure the gateways to pick up specific sets of functions, perhaps by labels. Otherwise, each gateway picks up all function services in the swarm.
Current Behavior
Function services are currently denoted by the presence of a function label on the service. Gateways automatically pick up all services with this label.
Possible Solution
As an example, Traefik can be configured with constraints for which Traefik configured services it handles. Only services that match the constraint (via tags on labels) will be handled by the Traefik instance. This enables multiple instances of Traefik to be deployed on a swarm, each handling a different set of services.
Context
I'm trying out FaaS in a project. The repo branches for this project are automatically built and deployed on a Docker swarm for review as part of a CI/CD process. The FaaS gateways from the deployments are picking up the functions from all the deployments, not just the specific branch. There doesn't seem to be a way to limit each gateway to the services for a specific deployment.
Your Environment

Docker version docker version (e.g. Docker 17.0.03 ): 17.0.04
Operating System and version (e.g. Linux, Windows, MacOS): Development on macOS. CI/CD deployments on RHEL 7.3.
Link to your project: Not available (internal).

Hi @kinghuang,
Thanks for opening this issue. I'd like to understand your use-case a little more.
In terms of two making FaaS gateways available - have you tried deploying individual stacks on separate networks? Can you share your YAML file with me?
# docker stack deploy pipeline1 -c ./stack1.yml
# docker stack deploy pipeline2 -c ./stack2.yml

I could reproduce the issue with the steps above. Both gateways saw the functions from either stack.
How would you propose injecting the unique network name / namespace into the gateway process/container?

You can use this test implementation - and provide a stack_namespace environmental variable to your gateways. This will filter your functions to only the gateway / stack they belong to.
https://github.com/alexellis/faas/compare/filter_networks?expand=1

@kinghuang please can you give feedback on above?

@alexellis Will do! I've added this to my task list.

@alexellis Sorry again to take so long. I'm finally ready to take a look at this, but it looks like the filter_networks branch is gone. Any chance you can push that back up and I'll review it right away? Thanks.

We're talking about an issue opened in April.. so I think I pruned it. The branch should be there again now thanks for looking 👍

Thanks. I don't see it on GitHub, yet. Mind double-checking the branch?

@alexellis I still don't see the branch. Considering how much development has happened since May, would it be better to just re-implement? If so, I will take that on.

Sure. Please join us on Slack to coordinate - message alex@openfaas.com

@kinghuang thanks for joining. Here is the branch - https://github.com/alexellis/faas/compare/filter_networks?expand=1

Derek add label: priority/low

authors: alexellis kinghuang

repo: alexellis/faas


text:
Cannot run registry-creds with OOTB manifest - fails with error initially creating leader election record

Describe the bug
K8s clusters tested on ARM from v1.18 thru v1.21, x86 vanilla with the same versions - and multiple Tanzu cluster versions, this failure is also described in the PR #31 in which is fails on IKS on IBM Cloud.
When applying the manifest.yaml via the following - the system will never start up with a failed leader election:
k apply -f https://raw.githubusercontent.com/alexellis/registry-creds/master/manifest.yaml

Error from the pod:
E1210 14:13:51.146061       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"

To Reproduce
Create KinD cluster:
$ kind create cluster --image=kindest/node:v1.19.11@sha256:07db187ae84b4b7de440a73886f008cf903fcf5764ba8106a9fd5243d6f32729

Creating cluster "kind" ...
 ✓ Ensuring node image (kindest/node:v1.19.11) 🖼
 ✓ Preparing nodes 📦
 ✓ Writing configuration 📜
 ✓ Starting control-plane 🕹
 ✓ Installing CNI 🔌
 ✓ Installing StorageClass 💾
Set kubectl context to "kind-kind"
You can now use your cluster with:

kubectl cluster-info --context kind-kind

Not sure what to do next? 😅  Check out https://kind.sigs.k8s.io/docs/user/quick-start/

$ kubectx kind-kind
Switched to context "kind-kind".

$ k get po -A
NAMESPACE            NAME                                         READY   STATUS    RESTARTS   AGE
kube-system          coredns-f9fd979d6-7zxdq                      1/1     Running   0          63s
kube-system          coredns-f9fd979d6-8z6xq                      1/1     Running   0          63s
kube-system          etcd-kind-control-plane                      1/1     Running   0          71s
kube-system          kindnet-bnjnl                                1/1     Running   0          63s
kube-system          kube-apiserver-kind-control-plane            1/1     Running   0          71s
kube-system          kube-controller-manager-kind-control-plane   1/1     Running   0          71s
kube-system          kube-proxy-vfd7l                             1/1     Running   0          63s
kube-system          kube-scheduler-kind-control-plane            1/1     Running   0          71s
local-path-storage   local-path-provisioner-547f784dff-mrcn8      1/1     Running   0          63s

Install reg-creds:
$ k apply -f https://raw.githubusercontent.com/alexellis/registry-creds/master/manifest.yaml
namespace/registry-creds-system created
customresourcedefinition.apiextensions.k8s.io/clusterpullsecrets.ops.alexellis.io created
role.rbac.authorization.k8s.io/registry-creds-leader-election-role created
clusterrole.rbac.authorization.k8s.io/registry-creds-registry-creds-role created
rolebinding.rbac.authorization.k8s.io/registry-creds-leader-election-rolebinding created
clusterrolebinding.rbac.authorization.k8s.io/registry-creds-registry-creds-rolebinding created
deployment.apps/registry-creds-registry-creds-controller created

$  kubens registry-creds-system
Context "kind-kind" modified.
Active namespace is "registry-creds-system".

$ k get po -w
NAME                                                        READY   STATUS              RESTARTS   AGE
registry-creds-registry-creds-controller-68468bd469-dtjxf   0/1     ContainerCreating   0          8s
registry-creds-registry-creds-controller-68468bd469-dtjxf   1/1     Running             0          12s

Check reg-creds pod logs:
$ k logs registry-creds-registry-creds-controller-68468bd469-dtjxf
2021-12-10T14:13:51.132Z	INFO	controller-runtime.metrics	metrics server is starting to listen	{"addr": ":8080"}
2021-12-10T14:13:51.133Z	INFO	setup	starting manager with the version %s and commit %s	{"0.3.0-rc4": "5883ef9ba8e72563b3c4ceee23647ed27c7713fb"}
I1210 14:13:51.133985       1 leaderelection.go:242] attempting to acquire leader lease  registry-creds-system/8bdecb1a.alexellis.io...
2021-12-10T14:13:51.134Z	INFO	controller-runtime.manager	starting metrics server	{"path": "/metrics"}
E1210 14:13:51.146061       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"
E1210 14:13:54.603970       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"
E1210 14:13:58.869250       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"
E1210 14:14:02.471738       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"
E1210 14:14:05.531691       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"
E1210 14:14:08.557895       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"
E1210 14:14:12.215142       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"
E1210 14:14:14.381499       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"
E1210 14:14:16.763812       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"
E1210 14:14:19.005162       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"

Expected behavior
The leader election to succeed and the system to run.
List all possible solutions, and your suggested option
Removing the lines:  https://github.com/alexellis/registry-creds/blob/873e47849c983d48e16f27c3e38947f941a3288d/manifest.yaml#L88-L89
Solves the issue instantly:
E1210 14:22:31.466596       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"
E1210 14:22:34.726013       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"
E1210 14:22:36.976019       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"
<!!!!! ------ kubectl edit role registry-creds-leader-election-role - executed here to remove the above lines ------- !!!!!>
I1210 14:22:39.356030       1 leaderelection.go:252] successfully acquired lease registry-creds-system/8bdecb1a.alexellis.io
2021-12-10T14:22:39.356Z	DEBUG	controller-runtime.manager.events	Normal	{"object": {"kind":"ConfigMap","namespace":"registry-creds-system","name":"8bdecb1a.alexellis.io","uid":"b1805b5f-0c0e-40a8-a555-fbc91916d2b7","apiVersion":"v1","resourceVersion":"2102"}, "reason": "LeaderElection", "message": "registry-creds-registry-creds-controller-68468bd469-dtjxf_13eadec4-12c6-44aa-8b2c-bf9107cf5df3 became leader"}
2021-12-10T14:22:39.357Z	INFO	controller-runtime.controller	Starting EventSource	{"controller": "serviceaccount", "source": "kind source: /, Kind="}
2021-12-10T14:22:39.358Z	INFO	controller-runtime.controller	Starting EventSource	{"controller": "clusterpullsecret", "source": "kind source: /, Kind="}

My comment here shows the same response as this being the fix for multiple users: https://github.com/alexellis/registry-creds/issues/16#issuecomment-778186442

Thanks for doing this. I was running the operator through go, so not seeing this error.
I've patched it a the source, instead of in the generated files at: 873e478
If you and @frundh want to use this software and see it maintained, may I suggest that you become sponsors on GitHub?
Alex

Closing as fixed

I appreciate you fixing it in the source - but the spirit of this issue was that the manifest.yaml is broken OOTB for anyone deploying it and i'm sure @frundh would agree here as this was also the spirit of his PR - so I would argue that this should be re-opened, even as an FYI for other people that will inevitably hit this issue if indeed there is an upstream issue that needs fixed.
Right now, I am just pointing people that use it to a manifest I have forked and removed the offending lines from to get them running.

It's fixed? What problem are you running into now?

The same one as before - repo info below:
❯ kind create cluster --image=kindest/node:v1.19.11@sha256:07db187ae84b4b7de440a73886f008cf903fcf5764ba8106a9fd5243d6f32729
Creating cluster "kind" ...
 ✓ Ensuring node image (kindest/node:v1.19.11) 🖼
 ✓ Preparing nodes 📦
 ✓ Writing configuration 📜
 ✓ Starting control-plane 🕹
 ✓ Installing CNI 🔌
 ✓ Installing StorageClass 💾
Set kubectl context to "kind-kind"
You can now use your cluster with:

kubectl cluster-info --context kind-kind

Have a nice day! 👋

❯ k apply -f https://raw.githubusercontent.com/alexellis/registry-creds/master/manifest.yaml
namespace/registry-creds-system created
customresourcedefinition.apiextensions.k8s.io/clusterpullsecrets.ops.alexellis.io created
role.rbac.authorization.k8s.io/registry-creds-leader-election-role created
clusterrole.rbac.authorization.k8s.io/registry-creds-registry-creds-role created
rolebinding.rbac.authorization.k8s.io/registry-creds-leader-election-rolebinding created
clusterrolebinding.rbac.authorization.k8s.io/registry-creds-registry-creds-rolebinding created
deployment.apps/registry-creds-registry-creds-controller created

❯ k get po -n registry-creds-system -w
NAME                                                        READY   STATUS              RESTARTS   AGE
registry-creds-registry-creds-controller-75d6696656-djskn   0/1     ContainerCreating   0          12s
registry-creds-registry-creds-controller-75d6696656-djskn   1/1     Running             0          13s
^C%

❯ k logs -n registry-creds-system registry-creds-registry-creds-controller-75d6696656-djskn -f
2021-12-13T13:56:08.943Z	INFO	controller-runtime.metrics	metrics server is starting to listen	{"addr": ":8080"}
2021-12-13T13:56:08.944Z	INFO	setup	starting manager with the version %s and commit %s	{"0.3.1": "9a617dafeb621c0dc09bb133b6163f68afc920cf"}
I1213 13:56:08.945026       1 leaderelection.go:242] attempting to acquire leader lease  registry-creds-system/8bdecb1a.alexellis.io...
2021-12-13T13:56:08.945Z	INFO	controller-runtime.manager	starting metrics server	{"path": "/metrics"}
E1213 13:56:08.976261       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"
E1213 13:56:12.437712       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"
E1213 13:56:16.707244       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"
E1213 13:56:20.311260       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"
E1213 13:56:23.368801       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"
E1213 13:56:26.402875       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"
E1213 13:56:30.060973       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"
E1213 13:56:32.232297       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"
E1213 13:56:34.618701       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"
E1213 13:56:36.865718       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"
E1213 13:56:39.596546       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"
E1213 13:56:42.841256       1 leaderelection.go:335] error initially creating leader election record: configmaps is forbidden: User "system:serviceaccount:registry-creds-system:default" cannot create resource "configmaps" in API group "" in the namespace "registry-creds-system"

authors: alexellis mylesagray

repo: alexellis/registry-creds


text:
Add support for tsconfig paths

If you use the paths compiler option in your tsconfig.json, it would be nice if this resolver used your config to resolve it for you.

Hey @bradzacher 👋
This feature forces people to use the baseUrl option in their tsconfig although it's not required by TypeScript. After upgrading to 1.1.0 I get these errors in every file:
Resolve error: Unable to find tsconfig in /my/project/path: Missing baseUrl in compilerOptions  import/no-unresolved

When I set...
"baseUrl": ".",

this plugin works fine. The problem is, however, that VSCode now generates paths on auto import that webpack and Node.js are not able to resolve:
// Instead of
import something from "../../shared/something";
// I get
import something from "src/shared/something";

I'm not sure if VSCode auto import is doing the right thing here, but I also think that baseUrl doesn't have to be set if I'm not using the paths option.
What do you think? :)

I get this issue, even when I add a baseUrl.
{
  "compilerOptions": {
    "strict": true,
    "strictNullChecks": false,
    "forceConsistentCasingInFileNames": true,
    "module": "commonjs",
    "esModuleInterop": true,
    "target": "es2017",
    "noImplicitAny": false,
    "lib": ["esnext"],
    "skipLibCheck": true,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "moduleResolution": "node",
    "allowJs": true,
    "sourceMap": true,
    "outDir": "dist",
    "baseUrl": ".",
    "typeRoots": ["src/types", "node_modules/@types"],
    "paths": {
      "~/*": ["src/*"],
      "~test/*": ["test/*"]
    }
  },
  "include": ["src", "test"]
}

module.exports = {
  env: {
    'jest/globals': true,
    browser: false,
    es6: true,
    node: true
  },
  extends: ['plugin:jest/recommended', 'airbnb-base', 'prettier'],
  globals: {
    Atomics: 'readonly',
    SharedArrayBuffer: 'readonly',
    window: true,
    document: true,
    localStorage: true,
    FormData: true,
    FileReader: true,
    Blob: true,
    navigator: true
  },
  settings: {
    'import/resolver': {
      node: {
        extensions: ['.js', '.jsx', '.ts', '.tsx']
      }
    }
  },
  parser: '@typescript-eslint/parser',
  plugins: ['jest', 'prettier'],
  rules: {
    'no-restricted-syntax': 0,
    'no-underscore-dangle': 0,
    'import/imports-first': ['error', 'absolute-first'],
    'import/newline-after-import': 'error',
    'no-unused-expressions': 0,
    'no-console': 0
  }
};

  settings: {
    'import/resolver': {
      node: {
        extensions: ['.js', '.jsx', '.ts', '.tsx']
      }
    }
  },

You're not using the node import resolver? Check the readme for how to configure this plugin.

Thanks!

Still not working.
module.exports = {
  env: {
    'jest/globals': true,
    browser: false,
    es6: true,
    node: true
  },
  extends: ['plugin:@typescript-eslint/recommended', 'plugin:jest/recommended', 'airbnb-base', 'prettier'],
  globals: {
    Atomics: 'readonly',
    SharedArrayBuffer: 'readonly',
    FormData: true,
    FileReader: true,
    Blob: true
  },
  settings: {
    'import/parsers': {
      "@typescript-eslint/parser": [".ts"]
    },
    'import/resolver': {
      typescript: {},
    }
  },
  parser: '@typescript-eslint/parser',
  plugins: ['import','@typescript-eslint', 'jest', 'prettier'],
  rules: {
    'import/no-extraneous-dependencies': 0,
    '@typescript-eslint/no-explicit-any': 0,
    '@typescript-eslint/explicit-function-return-type': 0,
    '@typescript-eslint/explicit-member-accessibility': 'off',
    '@typescript-eslint/indent': 0,
    '@typescript-eslint/no-unused-vars': [2, { args: 'none' }],
    'import/prefer-default-export': 0,
    'no-restricted-syntax': 0,
    'no-underscore-dangle': 0,
    'import/imports-first': ['error', 'absolute-first'],
    'import/newline-after-import': 'error',
    'no-unused-expressions': 0,
    'no-console': 0
  }
};

{
  "compilerOptions": {
    "strict": true,
    "strictNullChecks": false,
    "forceConsistentCasingInFileNames": true,
    "module": "commonjs",
    "esModuleInterop": true,
    "target": "es2017",
    "noImplicitAny": false,
    "lib": ["esnext"],
    "skipLibCheck": true,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "moduleResolution": "node",
    "allowJs": true,
    "sourceMap": true,
    "outDir": "build",
    "baseUrl": ".",
    "typeRoots": ["src/types", "node_modules/@types"],
    "paths": {
      "~/*": ["src/*"],
      "~test/*": ["test/*"]
    }
  },
  "include": ["src", "test"]
}

EDIT: seems like it wasnt installed on this branch, sorry. It's weird that eslint didnt warn me though that there's a missing plugin

authors: bradzacher cyrus-za jhnns

license: ISC


text:
Erreur 404 quand on essaie d'accéder à une sous-url manuellement

Probablement un souci avec Vercel.

Résolu avec https://github.com/alexislozano/salaires.dev/commit/0a74ace2d4c2d74b242a0cbf6900b02b5f6c6c1e


text:
Count API is Down

I reached out at count API through their email today and if I don't receive an email in the upcoming week, I will either remove the counter entirely, or surround it in a try/catch block.
Why is Count API Used?
Count API is used to collect data about the amount of times people use my program - I love statistics! It does not collect any user data whatsoever, and all requests are anonymous. I use Count API on my web portfolio too, so it's very sad to see that it has gone down over the past several days.

Looks like I will have to remove the counter :(

Count API was up for a few hours then went offline again. It's too unreliable for use in the extension so I removed it completely (it wasn't really useful anyway).

repo: alexlostorto/magic-notes