PancakeSwap

PancakeSwap is a decentralized exchange for swapping BEP20 tokens on Binance Smart Chain. PancakeSwap uses an automated market maker (AMM) model where users trade against a liquidity pool. Such pools are filled with users’ funds. They deposit them into the pool, receiving liquidity provider (or LP) tokens in return. They can use those tokens to reclaim their share, plus a portion of the trading fees.
The LP tokens are called FLIP tokens. PancakeSwap also allows users to farm additional tokens – CAKE and SYRUP. On the farm, users can deposit LP tokens, locking them up in a process that rewards users with CAKE. Users can stake CAKE tokens to receive SYRUP, which will have further functionality as governance tokens (and as tickets in a lotteries).
Source: https://coinmarketcap.com/exchanges/pancakeswap/
Exchange URL : https://pancakeswap.finance/
API Documentation : https://github.com/pancakeswap/pancake-info-api/blob/develop/v1-documentation.md
Type of Exchange : DEX
┆Issue is synchronized with this Clickup task by Unito

connector added in Version 1.10.0 and available in latest development  / version 1.24.0
https://hummingbot.org/release-notes/1.10.0


<EMAIL_ADDRESS>decompress error

When attempting to install WingetUI I face the following:
With no other application does this happen.
PS C:\Users\lemag> scoop install wingetui
Installing 'wingetui' (3.1.1) [64bit] from 'extras' bucket
WingetUI.Installer.exe (51.2 MB) [============================================================================] 100%
Checking hash of WingetUI.Installer.exe ... ok.
Extracting WingetUI.Installer.exe ... ERROR Exit code was 1!
Failed to extract files from C:\Users\lemag\scoop\apps\wingetui\3.1.1\WingetUI.Installer.exe.
Log file:
~\scoop\apps\wingetui\3.1.1\innounp.log
Please try again or create a new issue by using the following link and paste your console output:
https://github.com/ScoopInstaller/Extras/issues/new?title=wingetui%403.1.1%3A+decompress+error
PS C:\Users\lemag>
Log shows
Signature detected: Inno Setup Setup Data (6.3.0)
This is not directly supported, but i'll try to unpack it as version 5602
; Version detected: 6300
Critical error: The setup files are corrupted. Please obtain a new copy of the program.
Removing download cache manually and also by running scoop cache rm -a  and scoop cleanup -a does not fix the issue.

Fixed.

scoop uninstall innounp
scoop bucket add versions
scoop install versions/innounp-unicode

Duplicates #13709.


Updating the "Getting Started Guide"

added new Processing video
added new workflow video

Merging this, but would welcome any further suggestions or additions to the getting started page!


USE KEYBOARD TO SEARCH A FOLDER

Describe the bug
HOLA!! DEBERIA PODER USARSE EL TECLADO PARA ENCONTRAR CARPETAS POR LETRAS, POR EJEMPLO SI PRESIONO LA TECLA"S" TENDRÍA QUE MOSTRAR TODAS LAS CARPETAS QUE COMIENZAN CON "S"
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS Version: [e.g. Windows 10 1903 18362.175]
App version: [v0.5.0]

Additional context
Add any other context about the problem here. Does this problem occur again after restarting the app?

HOLA!! DEBERIA PODER USARSE EL TECLADO PARA ENCONTRAR CARPETAS POR LETRAS, POR EJEMPLO SI PRESIONO LA TECLA"S" TENDRÍA QUE MOSTRAR TODAS LAS CARPETAS QUE COMIENZAN CON "S"

HELLO!!   If you don't see that behavior you might want to try updating to the latest version.

If you can still reproduce this issue with the latest release please feel free to reopen this issue.


Installation instructions via stack do not seem to work

I just cloned the repository, and ran (from the stack2nix folder). stack fails with the following output:

Error: While constructing the build plan, the following exceptions were encountered:

In the dependencies for hnix-0.3.4:
    data-fix-0.0.4 must match >=0.0.7 (latest applicable is 0.2.0)
needed due to stack2nix-<IP_ADDRESS> -> hnix-0.3.4

Plan construction failed.

Am I missing something?

@domenkozar any update on this fix?

stack install on this branch worked fine on my machine(TM)

could you try https://github.com/input-output-hk/stack2nix/pull/73

Same error :(
Progress: 23/26
--  While building package trifecta-<IP_ADDRESS> using:
      /home/damian/.stack/programs/x86_64-linux/ghc-nopie-8.0.2/bin/ghc --make -odir /tmp/stack3270/trifecta-<IP_ADDRESS>/.stack-work/dist/x86_64-linux-nopie/Cabal-<IP_ADDRESS>/setup -hidir /tmp/stack3270/trifecta-<IP_ADDRESS>/.stack-work/dist/x86_64-linux-nopie/Cabal-<IP_ADDRESS>/setup -i -i. -package=Cabal-<IP_ADDRESS> -clear-package-db -global-package-db -package-db=/home/damian/.stack/snapshots/x86_64-linux-nopie/lts-9.11/8.0.2/pkgdb /tmp/stack3270/trifecta-<IP_ADDRESS>/Setup.lhs /home/damian/.stack/setup-exe-src/setup-shim-mPHDZzAJ.hs -main-is StackSetupShim.mainOverride -o /tmp/stack3270/trifecta-<IP_ADDRESS>/.stack-work/dist/x86_64-linux-nopie/Cabal-<IP_ADDRESS>/setup/setup -threaded
    Process exited with code: ExitFailure 1
    Logs have been written to: /home/damian/Documents/github/stack2nix/.stack-work/logs/trifecta-<IP_ADDRESS>.log

    [1 of 2] Compiling Main             ( /tmp/stack3270/trifecta-<IP_ADDRESS>/Setup.lhs, /tmp/stack3270/trifecta-<IP_ADDRESS>/.stack-work/dist/x86_64-linux-nopie/Cabal-<IP_ADDRESS>/setup/Main.o )

    /tmp/stack3270/trifecta-<IP_ADDRESS>/Setup.lhs:7:31: error:
        Module
        ‘Distribution.Package’
        does not export
        ‘PackageName(PackageName)’

Same error as? This seems new to me, but I don't know how to reproduce it.

Sorry for not being clear. I meant the same error as when I fixed the dependency problems reported in above. I cloned #73 in a fresh repository to be sure. Could it be that some globally installed library is introducing some noise? (I doubt it, since I'm using stack...).

For what is worth I'm using Linux as host OS.


Improved Handling of Sparse Dictionaries

Is your feature request related to a problem or challenge? Please describe what you are trying to do.

Sparse dictionaries, where a large number of a dictionary's values are not referenced by a corresponding key, can occur fairly frequently:

Parquet dictionary preservation will output the same dictionary for all arrays in a row group
Selection kernels like take or filter will not recompute a smaller dictionary

Many of the kernels, however, proceed by evaluating against the values and then "materializing" this result in the context of a dictionary.
Describe the solution you'd like

The basic primitive needed is the ability to compute a selection vector for a dictionary's values, which can then be used as a selection vector (#4095) (#3620) for further operations
Describe alternatives you've considered

Additional context

https://github.com/apache/arrow-rs/issues/506 tracks adding the ability to recompute a dictionary, which may share similar primitives
https://github.com/apache/arrow-rs/issues/4095 and https://github.com/apache/arrow-rs/issues/3620 track adding selection vector support.

Closed by https://github.com/apache/arrow-rs/pull/3558


KAFKA-6290: Support casting from logical types in cast transform

This PR adds support for cast transforms to cast from logical types Date, Time, and Timestamp to
their internal int32 or int64 representations. Any valid cast on their internal representations
would also be applicable. For instance, Time has internal int32 representation, but can be cast to
int64 if desired.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Retest this, please.

Merged back to the 1.1 branch.


BackButton

Hi there,
thnaks for your excellent Plugin. I just noticed, that the "Backbutton" is not working anymore, once the App is in Immersive Mode. I know, that it once worked without any Issues, but since a while, it seems to stop working.
Are you aware of that and/or have a solution for this?
(android 6.0.1 on a nexus 6p with latest Cordova (5.4.1))
Thanks a lot!

It looks like there might be an issue with dispatchKeyEventnot being passed through correctly: should have a fix ready soon (ish)


Thread running at QOS_CLASS_USER_INTERACTIVE waiting on a lower QoS thread running at QOS_CLASS_DEFAULT. Investigate ways to avoid priority inversions

Which version of the Ably SDK are you using?
PODS:

Ably (1.2.1):

AblyDeltaCodec (= 1.2.0)
KSCrashAblyFork (= 1.15.20-ably-6)
msgpack (= 0.3.1)
SAMKeychain (= 1.5.3)
SocketRocketAblyFork (= 0.5.2-ably-7)
ULID (= 1.1.0)

AblyDeltaCodec (1.2.0)

On which platform does the issue happen?
iOS 13.1.3 to iOS 16.2
Are you using Carthage?
No
Are you using Cocoapods?
Yes, 1.11.3
Which version of Xcode are you using?
14.0.1 on M1 mac
What did you do?
I'm getting a Hang Risk warning on Xcode on one of the dependency pods for Ably regarding the usage of dispatch_group_wait primitive (https://developer.apple.com/documentation/xcode/diagnosing-performance-issues-early)

We've linked this to crashes that we've been experiencing since about 6 to 7 months ago with "C++ Exception: ARTException"
Does anyone have an idea of maybe what I might be doing wrong? or if this is a known issue?
I saw that the latest version of the SDK is 1.2.19 but I tried updating it to that and Cocoapods throws me an error saying that it can't be found

This was fixed in v1.2.18
Couldn't you post your Podfile here? (at least the line with the ably-cocoa) @lighthouse-beacon-01

@lighthouse-beacon-01 you need to run one of these: pod repo update or pod install --repo-update


Default signing algorithm should be SHA-256?

It looks like the default/recommended signatureAlgorithm in the documentation uses SHA-1, which is no longer considered secure.  Can this be changed to SHA-256?
        "signatureAlgorithm": "http://www.w3.org/2000/09/xmldsig#rsa-sha1",

I updated the doc and settings. The default value if the setting parameter is not provided still gonna be sha1 for backward compatibility.

OK -- I'd encourage you to change that default and just document the change in the release notes.  I don't think backward-compatibility is a good reason to default to a known insecure algorithm (which basically means all downstream projects, like python-social-auth which uses the default SECURITY settings, will be insecure).
If you're not able to change the default here, I guess I'll open an issue with python-social-auth for them to fix it.


Unit testing for relabeling rules

It would be great to have unit testing for relabeling configs. Relabeling configs can shift over time, and having unit tests would give confidence that we don't break them.
It is also not easy to test them without a cloud provider or k8s cluster on. I think we should not have that dependency.
We already have unit testing for rules, but I'd like to have something to test relabeling rules inside promtool.
Ideas welcome.

I think this could be pretty easily added to the existing test file by doing the following:

Adding a config_files field, where a user could specify the Prometheus config file their relabeling configs are in.
Adding an input_labels field, which holds further labels and their values, besides the ones that can already be gathered from input_series.
Then we could add a relabel_rule_test field, which accepts the name of the job that the relabeling configs belong to, and tests the configs for that job using the labels from input_series and input_labels.

Example:
# rule.yaml
config_files:
 - prometheus.yml

tests:
 - interval: 1m

   input_series:
    - series: 'up{job="prometheus", instance="localhost:9090"}'
      values: '0'

    - input_labels:
       - name: 'foo'
         value: 'bar'

    - relabel_rule_test:
     # Given the labels 'prometheus', 'instance' and 'foo'
     - name: prometheus
       exp_labels:
         - name: 'foo'
           value: 'car'

# prometheus.yml
...
scrape_configs:
 - job_name: 'prometheus'
   ...
   relabel_configs:
      # This is probably wrong
    - source_labels: ['foo']
      replacement: 'car'
      target_label: 'foo'

A possible thing to consider is if we should keep the changed label set and pass it to the alert and promql tests in the same test group.

cc @dgl you are better placed to comment on this

Something like this approach could work for metric relabels. Maybe that would be an interesting thing to prototype first...
However I think the real value is something that could test service discovery relabelling configs, as those are usually more complex. The tricky bit is it wouldn't necessarily be possible to infer the job as proposed, as that could be changed by relabelling.
In fact your example nicely shows how the unit tests currently get away without caring about the source of timeseries (internal vs user metrics), but per the docs on metric relabelling:
Metric relabeling does not apply to automatically generated timeseries such as `up`.

So we'd need to know which series those are, so as not to apply metric relabelling to them. This leads to a potential design: mark series as either processed by service discovery, or from a particular job.
- input_series:
    # Series has no labels, as those will be provided by service discovery (or
    # user can override them?)
    - series: 'up{}'
      values: '0x200'
      sd:
        source_job: "a-job-defined-in-config"
        labels:
          __meta_consul_node: node1
          instance: "..."

or for a metric_relabel_configs test:
- input_series:
    - series: 'something_total{job="a-job"}'
      values: '0+1x200'
      metric_relabel_source_job: "a-job-defined-in-config"

A possible thing to consider is if we should keep the changed label set and
pass it to the alert and promql tests in the same test group.

It definitely should, in the same way it would in the real system. I suspect actually making that happen may be challenging due to how the promtool unit tests currently pass the series straight to the promql testing code.
I think if that can be done then there's no need for relabel_config_test, just let the user match labels normally on their series, rather than making relabels special.

Something like this approach could work for metric relabels. Maybe that would be an interesting thing to prototype first...
However I think the real value is something that could test service discovery relabelling configs, as those are usually more complex.

I have been naive about the difference between these two in the past; I wrote that proposal quite a while ago and I assume that I had combined them in my mind. I definitely think that we should cover both methods.

So we'd need to know which series those are, so as not to apply metric relabelling to them. This leads to a potential design: mark series as either processed by service discovery, or from a particular job.

It took me a little bit to wrap my head around this, but my understanding is this is the distinction between target relabeling and metric relabeling. To that end, I think we should consider changing the sd field to job (and subsequently source_job to just source) to make it clear that this won't actually utilize any of the service discovery mechanisms (I think) and therefore has nothing to do with service discovery except that you might want to simulate a target garnered from it (or from static_configs, which is different)

I think if that can be done then there's no need for relabel_config_test, just let the user match labels normally on their series, rather than making relabels special.

This might cause some confusion/inconvenience. I do think it's fine for metric relabeling, as it's specifically for series, but target relabeling is somewhat separate. I could definitely see a user wanting to only test their target relabeling rules but have to specify series anyway and write tests for PromQL expressions, all to get access to those target labels. Actually, now that I'm thinking about it, that might be an annoyance for testing metric relabeling as well. Both are independent of PromQL and shouldn't have to be tested under its functionality.
A few more things we may want to think about:

Targets can be dropped during relabeling and we should support testing for that.

This is a whole other ordeal, but given that target relabeling is often used to filter out good targets from what is returned by service discoveries, the labels these mechanisms assign are necessary. Making users do the work themselves when testing is tedious but more importantly allows for inconstancies with the actual behavior of service discoveries. This means that relabeling rules can be written and tested mistakenly based on a different implementation than what Prometheus actually uses. But enabling service discoveries to be configured for offline testing would be tricky, and I don't think it's worth the effort.

Currently, we call this "unit testing for rules", and although I wasn't privy to its naming, testing PromQL expressions already falls out of its bounds in my opinion. Now adding relabeling will stray even further, so I think we should consider giving it a more general name.

Service discovery relabelling configs can be tested with #8970.
This would be to test metric relabeling.

Right, forgot that it had that. I think the service discovery capability in this still is needed given the nature of the check sd command, which outputs the result of relabeling but doesn't test it. Sure, you can go by sight, but this provides an automated and rigid system. In my opinion, both these features can live together.

Hello from the bug scrub.
@roidelapluie @LeviHarrison nothing has happened here in a while. What's the state of this? Is it still worth pursuing? Should we tag it with "help needed", or rather close?


Add Corretto 16.0.0 Docker images and tags

Description of changes:
This PR add containers with recently released Corretto 16, for AL2, alpine and debian, as both full JDK and slim images.
Tags have been also updated to have these images in repositories.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks @TianminShi for the quick review and merge!
I was wondering: how is it possible to have "slim" images pushed to docker hub repository? Thanks!


amp-pwa is outdated

apm-pwa is not the latest version of amp-pwa

@choumx - can you look at this?

/cc @cvializ

https://ampbench.appspot.com/validate_ua_desktop?url=https%3A%2F%2Fchoumx.github.io%2Famp-pwa%2F%23
You can see it fails the tests


Web interface option to re-analyze previous tasks (particularly failed)

There may be more than one instance of an administrator requiring a re-analysis of a previous task - e.g. mongodb wasn't running, virtualbox VM wasn't shut down properly, etc.  cuckoo.py process  can easily do this, so let's make a button "Retry Processing" or "Retry task" under web/analysis/views.py.

I like the idea.

duplicate of #483 ?
will take a look at this feature during the day or tomorrow.

There's a resubmit analysis button nowadays which I guess is most of what you suggested here.
We could add reprocessing in the sense that the analysis task status could be set to completed and then wait for one of the process.py instances to pick it up, but it's a little bit dirty (would also have to delete all data from the MongoDB database before hand etc).
So going to close this as resolved for now - please reopen or create a new issue if you think otherwise.


⚠ Bofrost.de has degraded performance

In cd51e17, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 895 ms

Resolved: Bofrost.de performance has improved in 5662ec4 after 50 minutes.


Fixed typo translation in ch.7

Thank you, @KRostyslav :)

@ivanzusko how can I  chat with You? I have some questions

Yiu can get me via email<EMAIL_ADDRESS>Or Telegram: @ivanzusko
:(
Ср, 25 квіт. 2018 р., 16:53 користувач KRostyslav<EMAIL_ADDRESS>пише:

@ivanzusko https://github.com/ivanzusko how can I chat with You? I have
some questions
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ivanzusko/javascript/pull/8#issuecomment-384316453,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH-_ZmKGBpp_ycUiM9OlQUJtBokSBGlgks5tsI3zgaJpZM4ThJ-t
.


kubectl --insecure-skip-tls-verify doesn't seem to ignore TLS errors

Tectonic Version
1.5.5
Environment
bare metal
Expected Behavior
kubectl should talk to the API when using --insecure-skip-tls-verify even if the TLS certificate on the server is invalid:
Actual Behavior
kubectl complains about the TLS certificate:
$ kubectl --insecure-skip-tls-verify get nodes
error: error fetching provider config: Get https://tectonic.example.com/identity/.well-known/openid-configuration: x509: certificate signed by unknown authority
Reproduction Steps
Make the tectonic ingress have a certificate signed by an the Let's Encrypt Staging server.

Hey @abh thanks for filing this issue and apologies for the delayed followup - I've looped in @IvanCherepov, who will get back to you shortly.

@abh are you sure you're pointing kubectl at the correct host?

@abh  same problem here. Can't login now anymore because I deleted the ingress for kube-lego.
Can't login with kubectl and webinterface. Anyone knows how to get that fixed?

In the assets.zip that the installer generated, there is a kubeconfig that is "root" and can be used to bypass identity. Using this with kubectl should give you the ability to add the ingress rule back and correct any other misconfigurations.

@kersten @abh Can you attempt to modify the CA embedded in your kubeconfig to be the correct LE cert or with --root-ca-file=?

@robszumski I will try that. First attempt looked a bit better. Now I get error error: You must be logged in to the server (the server has asked for the client to provide credentials)

On Apr 26, 2017, at 14:21, Rob Szumski<EMAIL_ADDRESS>wrote:
@kersten @abh Can you attempt to modify the CA embedded in your kubeconfig to be the correct LE cert or with --root-ca-file=?

I am traveling this week. As far as I remember when I tried I struggled either to get the right chain or it blew up on accessing the controller URL. Anyway, that was what led me to in the end just wanting to ignore the TLS stuff for a moment to see if that's work. :-)

--insecure-skip-tls-verify=true


Lua colors not working

Describe your bug here.
so idk if its just me but the lua colors don't work for me for some reason there is no specific error for it but its happening on my side but tell me if theres a fix for it
i was trying function onCreatePost()
setProperty('timeBar.color', getColorFromHex('FF0000'))

end

and didn't work
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
no

i fixed it


naive-tab-completion

In absence of rls (#3) or rust-analyzer integration (#102), I think even a basic, naive tab completion is helpful.
let foo = "foobar";
dbg!(f<cursor>
         ^ with this PR pressing tab, cycles through foo and foobar

It's based on history.
And it only matches the longest prefix.

Thanks


Can't obtain a Stripe token with Apple Pay

I'm using Apple/Google Pay to generate a Stripe's charge, then I'm passing the token to our backend that takes care of the payment process.
Here's the GPay flow:
Inside the google_pay_config.json we've all infos about Stripe:
"allowedPaymentMethods": [
      {
        "type": "CARD",
        "tokenizationSpecification": {
          "type": "PAYMENT_GATEWAY",
          "parameters": {
               "gateway": "stripe",
	       "stripe:version": "2018-11-08",
	       "stripe:publishableKey": "stripe_key"
      }
   }
]

Then I'm creating all the PaymentItems, getting a PaymentResult and finally from PaymentResult I can get a token to pass to the backend to complete the payment.
final token = paymentResult['paymentMethodData']['tokenizationData']['token'];
final tokenJson = Map.castFrom(json.decode(token));
String tokenId = tokenJson['id'];

How can I obtain that token using Apple Pay since I couldn't find any way to specify the Stripe data inside apple_pay_config.json?

Hello @Alessandro-v, using the payment result to create orders is a process that varies by PSP.
Using client libraries
Some of them, like Stripe, offer SDKs and client libraries that simplify that step. In fact, Stripe recently released a plugin for Flutter too (see the comment below). The plugin from Stripe integrates seamlessly with the pay plugin, by offering convenience methods to complete the payment operation with the payment result returned by the showPaymentSeletor method. Take a look at the pay section in the README to see a practical example. For Apple Pay, the token can be found under paymentResult.token.paymentData.
Using backend APIs
Alternatively, you can perform the same operation calling the APIs directly from your backend (which is a common path supported by most PSPs). For Stripe, that means creating a payment method from a token, and using it to confirm the payment or create a payment intent:

Create a token resource, passing the result received with the pk_token param. Take a look at how this is done in the Stripe SDK for iOS and the parameters used.
Create a payment method with the token created previously. See an example of that same request in the Stripe SDK for iOS for reference.
Confirm the payment or create a [payment intent] with the new payment method. Take a look at the API docs for creating a new intent with a payment method.

//cc'ing @jamesblasco @thorsten-stripe for visibility and additional context.

Thank you!! We're still waiting for an answer on the Stripe repo to manage the Apple Pay flow.

Hi @Alessandro-v, the Stripe library for Flutter has added specific means to create a payment method directly from the Apple Pay token. See #85 for more info.

Thanks!!!!

Closing this issue.
Feel free to re-open if the issue stands.


Update geval to 2.2.0

Contains important fixes with listening and unlistening from within event handlers.

https://github.com/Raynos/geval/pull/5


internal: publish

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

Codecov Report

Merging #2324 (6706fb4) into master (0429273) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2324   +/-   ##
=======================================
  Coverage   98.22%   98.22%
=======================================
  Files         128      128
  Lines        2028     2028
  Branches      310      310
=======================================
  Hits         1992     1992
  Misses         19       19
  Partials       17       17

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Sync .github/workflows directory with azure-sdk-tools for PR 6280

Sync .github/workflows directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/6280  See eng/common workflow

I'm going to override check enforcer as there's no pipeline that will test these changes.
/check-enforcer override


Why is your model well generalized for different applications such as polyp/transparent segmentation?

First of all, thanks for your great work for camouflaged object detection(COD). I know segmentation task, but I am very new to COD.
I read your paper and am really surprised to your great result, but I have one question about polyp/transparent segmentation.
I understood a key feature of your model is to learn an object texture as well as an object shape. If this understanding is correct, I'm not sure why this  also improves the polyp/transparent segmentation accuracy because they don't seem to have a distinct texture.

Hi, @muraano
Thank you for putting forward such an excellent discussion here.
Yes. In our early experiments, we excitingly found that our model could perform well in some similar tasks, such as polyp/transparent/surface anomaly objects. Similar to COD, these task scenes contain camouflaged patterns in Figure 9.
Notably, the excellent generalization ability may be an open issue here. We provide a dual-branch framework comprising object texture and object semantic learners. The former could excavate the gradient-wise perspective's abundant texture cues of candidate object(s). The latter receives the texture cues and takes further aggregation via GIT. This could be viewed as the holistic semantic understanding of the current scene along with the texture (whether distinct or non-distinct).
Happy to receive your interesting idea or understanding.
Best.

Thanks for your answer!


Suggestion: donations page in a new tab / add some text before link

Current situation: when someone clicks "לתרומות", it leads to another page (and exits the open-bus site)
The problem is that it looks to the user like it leads to another page and is unexpected.
My suggestion is to add some text (something like "כדי לעזור לנו להמשיך לקיים את הסדנה לידע ציבורי, ניתן לתרום לנו באמצעות jgive")
Another option is to open the link in another tab (but I like option 1 best because it lets the user know exactly where it goes).
What do you guys think? (I always click there by mistake so I thought that might be the user experience)

I discussed this with @NoamGaash  last week, I will take care of it :)
Regarding the text that explains, I think it's too long for a menu, and setting up a dedicated page for that seems a bit unnecessary to me, doesn't it?

Great! :)
I agree it's too long for a menu, and I can see why it seems a little overkill to have a dedicated page (if no additional content). My thought was to have a unified structure of menu -> page, But having a new tab, or any idea that will make the flow more comfortable can work.

maybe JGive can be embedded somehow?
https://jgivesupport.zendesk.com/hc/he/articles/4408727702930-כיצד-מטמיעים-חלון-תרומה-חכם-באתר-העמותה-

Yes, this is an excellent option, this way the user does not exit the application.
@NoamGaash, I would appreciate it if you could check with whoever is responsible on behalf of the association, for producing the iframe tags.

i have two suggestions on this issue which i wish to put for a consideration:

we can move dontations link to the topbar (where is also github external link )
we can display a modal (on menu item click) with donations page of jgive embedded

see this widjet:
https://www.hasadna.org.il/
it's just an img with a link

we can use it this way for now

I think it is unnecessary to create a model/page to display a non-functional image and redirect to an off-site page.
For now, I think the solution is that it will remain in the menu, only that it will open in another tab.

@xoRmalka let us know where are you standing and if you need any help! If you're still on this issue, please let us know and you'll be re-assigned
Thanks!

@NoamGaash
I'm waiting for the IFRAME tag for the completion.
can you try to generate it according to this tutorial:
https://jgivesupport.zendesk.com/hc/he/articles/4408727702930-כיצד-מטמיעים-חלון-תרומה-חכם-באתר-העמותה

Hi @xoRmalka , we've asked JGive to enable this feature for us, but their pricing was too expensive for us so unfortunately we won't be able to use it

@xoRmalka Nice to meet you and work on the same project.

@xoRmalka nice to see you in this issue also :-)

Hi @NoamGaash, I just made a PR for this issue:
https://github.com/hasadna/open-bus-map-search/pull/833

Solved!


⚠ ClamAV has degraded performance

In 5df0674, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 55 ms

Resolved: ClamAV performance has improved in 67b8e03 after 5 minutes.


stats section countup added #72 done

stats section countup added #72 done
https://github.com/user-attachments/assets/c89b010b-463e-4aa8-bfea-b18c4f225e01

#72

@VinayLodhi1712  Raise pr for the develop branch


Supporting swedish keyboard layout?

Similar to this: https://github.com/suurjaak/InputScope/issues/11
I would like to be able to support the Swedish keyboard layout.
What changes would need to be made?
Inputscope already works for this layout for the most part, its just that keypresses dont seem
to be reported for swedish characters.
As can be seen here:

For swedish chars normally placed here

there is no data.

Are the keypresses visible in the detailed counts table below? They might be listed as Oem_somethingsomething.
If yes, then the solution would be similar as in the linked issue: providing a custom keyboard image, and overriding KeyPositions in configuration.

they show up like this:

So I will try the solution in the linked issue, tnx

If it's no trouble, could you also detail your solution here upon success? Looks like it would help to have such guidance in program documentation, and this would help.
If you don't mind, I will keep this issue open, as a reminder for myself.

@jave Any luck with configuring the custom layout?

@jave So, any luck with configuring the custom layout?

sorry, I'm having trouble running inputscope, so I havent tried doing anything in a while.


[Bug][RayJob] Avoid nil pointer dereference

Why are these changes needed?
Reproduce the error:

Step 1: Deploy a KubeRay operator without this PR. I recommend using the nightly image [1].
Step 2: Create a RayJob using this YAML. It is configured to sleep for 1000s, giving you ample time to terminate the head Pod while the job is running.
Step 3: Delete the head Pod after the job is submitted.
Step 4: If the submitter Pod reaches the backoffLimit before the new head Pod is ready, the KubeRay operator will fail after the head Pod is restored. This failure occurs because if the job is not found, both jobInfo and error will return as nil. Consequently, at L274, isJobPendingOrRunning(jobInfo.JobStatus) will attempt to dereference a nil pointer.

[1] To easily reproduce the issue, I recommend using the nightly image, as its backoffLimit is smaller than that of v1.0.0. Hence, "the submitter Pod reaches the backoffLimit before the new head Pod is ready" is more likely to happen.

Related issue number

Checks

[ ] I've made sure the tests are passing.
Testing Strategy

[ ] Unit tests
[ ] Manual tests
[ ] This PR is not tested :(

With this PR, the operator will throw an exception instead of crashing.

Update the PR description. Merge this PR.


Fix: restrict program refs to item hashes

Problem: some users specify nonsensical strings in the ref field of programs and program volumes.
Solution: enforce the use of item hashes with the ItemHash type.
Moved the ItemHash and ItemType definitions to their own module to avoid circular imports.

Good initiative. This may break some type checking in aleph-client, we will have to watch for that.


Includefile property

In some cases we only want to share one solution folder or even a single src file and hide all the rest, especially when we have a very big solution.   By default live share has a folder view, but we don't want guests to see any other project within the solution.
There do exist properties like excludeFiles and hideFiles , but it is hard to configure in this case where only want to share one file or folder. Is there any way to "includeFiles" that by default hide the rest? Or even simpler, right-click a solution folder or a file in VS to share?

For only sharing a single folder - you could open the folder you wish to share instead of the solution that contains it and just share that. Although I agree it would be nice if we provided a gesture to do that so you didn't have to close your solution and open up the folder you want to share.
For only sharing a single file - this is something we're working on and hope to release soon!
And it sounds like you have a final suggestion in there for Live Share's file security to have an "include" list rather than an "exclude list," which I think is also a good idea. I've opened a separate issue - 1933 to track this.

@daytonellwanger  Glad to hear that!
 But then I lose the ability to debug since I am in the folder view instead of a solution/project view.

Ah, that makes sense. I will keep this issue open then as a feature request for the ability to, within a solution, share only a single folder. This is technically possible today as per the discussion in 1933 (i.e. set up a .vsls.json file that only includes the folder you want shared),, but we could make it simpler (I'm thinking just right-click on the folder you want to share "Live Share This Folder"). Thanks for your suggestion!

Thanks! I tried the #1933 's solution. But it doesn't work for this purpose, it ignores all files. The concept of '.gitignore' is to "by default preserve, indicate the files you don't want", where in excludeFiles, the /* in the root folder overwrites all behaviors in child folders even with !.  As a result of this, you still have to manually exclude every folder under /.I can't do "ignore all folders except this".

@jasongin

1933 didn't work for me as well, see https://github.com/MicrosoftDocs/live-share/issues/1933#issuecomment-565706444

I'm going to close this for now since we haven't heard significant customer feedback for this. If this is something that folks would like to see us prioritize, please let us know by re-opening/commenting on this bug. Thanks!


[NodeJS] templating for src/index.js

Very often I have to manually edit src/index.js when new version of an API is being pulled in. I'd like that to be templated, however the index.js file for each API is different. Here is an example from Cloud Vision:
/**
 * @type {object}
 * @property {constructor} ImageAnnotatorClient
 *   Reference to {@link v1.ImageAnnotatorClient}
 */
module.exports.v1 = gapic.v1;

/**
 * @type {object}
 * @property {constructor} ImageAnnotatorClient
 *   Reference to {@link v1p1beta1.ImageAnnotatorClient}
 */
module.exports.v1p1beta1 = gapic.v1p1beta1;

/**
 * @type {object}
 * @property {constructor} ImageAnnotatorClient
 *   Reference to {@link v1p2beta1.ImageAnnotatorClient}
 */
module.exports.v1p2beta1 = gapic.v1p2beta1;

Here we have a reference to ImageAnnotatorClient in the jsdoc section of the code, and it is generated based on gapic configs (I think?).
The templating strategy could be:

generate src/index.js using artman for a single version
for each version, take the module.exports... line that correspond to the version (regex?), along with its jsdoc section
bring it all into the generated src/index.js

cc @crwilcox since we were just talking about this

Templating support is in. I made one for circle ci configs -> https://github.com/GoogleCloudPlatform/synthtool/blob/master/synthtool/gcp/templates/node_library/.circleci/config.yml.j2
we use jinja for templating. tags are like this {{ VARNAME }}
If you look at https://github.com/googleapis/nodejs-speech/blob/1511cba881c5f6da0a711965503a6e599dcdb345/synth.py you can see how you can use template groups.
In short though

create index.js.j2 under nodejs folder in templates
Add the following code to synth.py:

common_templates = gcp.CommonTemplates()
templates = common_templates.node_library(package_name="@google-cloud/speech", my_arg = 'foo', other_arg = 'bar')

node_library takes keyword arguments. So just add new args by the names you need in your template.

Closing in favor of #10


Download Reminder

Right next to the "Download Commit" button should be a "Download Reminder" where their calendar is synced with the beginning of the reveal phase. The reminder should be as follows:
Reveal [site.com] // adChain Registry
https://app.adchain.com/domains/site.com#! (this URL can be in the notes of the calendar reminder)

If possible, the calendar reminder can be simultaneously downloaded with the commit json file when the "Download Commit" button is pressed. For now, let's mandate the download of the json commit.

can use ics module for this https://github.com/adamgibbons/ics


Press Escape to Close Selected Transcription

Taken from #165
This PR closes the LineViewer (Selected transcription) modal when pressing the escape key. Tests are included.

@beckyrother
Should this be denoted anywhere? This PR lets "escape" close the selected transcription line modal, but there's no signage anywhere telling the volunteer about the quick key.

It could be included in the help documentation, but I don't think we necessarily need to signpost anywhere as it's a fairly common UX pattern.

Merging. This is a small PR needed for beta.


changes made in viewstate file

Fixes #.
Description of the changes:

How changes were validated:

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: amrit1207 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

As a maintainer, how should I handle spam PRs?

We don’t like seeing spam PRs just as much as you, so please give them an invalid label and close them. PRs with an invalid label won’t be counted toward Hacktoberfest.

https://hacktoberfest.digitalocean.com/faq#rules


Add the "/" at end of the swagger ui doc url cause issue

When I make API documentation UI request(default path) with these two types of url:

https://localhost:18134/swagger/ui/index/
https://localhost:18134/swagger/ui/index

The first one will return me this:
{"Message":"An error has occurred.","ExceptionMessage":"Mapping not found - index/","ExceptionType":"Swashbuckle.SwaggerUi.AssetNotFound","StackTrace":"   at Swashbuckle.SwaggerUi.EmbeddedAssetProvider.GetAsset(String rootUrl, String path)\r\n   at Swashbuckle.Application.SwaggerUiHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)"}
Second one works well and return me the swagger UI doc page.
Any one can help me? this is a minor issue but it will potentially confound if anyone ever make this mistake.

Yes minor issue indeed...

There might be ...
but it wont make it to Nuget for a while, there is a big queue of pending Pull Requests.
My recommendation save your self some time and just type:
http://swashbuckletest.azurewebsites.net/swagger
http://swashbuckletest.azurewebsites.net/swagger/
Those will redirect you to the correct version

Thanks a lot, I was having this issue, in the end I read this and just drop the / , it solves the issue.


Consider replacing period usage in command line parameters

I noticed we have periods in our cmd arguments, for example --ao.enable.  It's standard to use a hyphen to separate words, I've never seen periods used like this: --ao-enable.  Hyphens are standard enough that yargs automatically duplicated this to aoEnable on the parsed object to make it easily indexable from JavaScript without having string literals everywhere.

This is meant for gltf-pipeline, right?

Whoops, yes, sorry.


Compute /v1/sources endpoint statically during indexing

Elasticsearch aggregations are expensive. If we continue experiencing capacity issues, we should look into making the /v1/sources endpoint counted once during ingestion.

Closing this because we've managed to stabilize Elasticsearch by making some better hardware tradeoffs and smarter indexing


Request to add a github action

This is an awesome and an engaging repository , plus due to hacktoberfest'21 many open source enthusiasts ( preferably students who are first time contributors ) open issues and PRs which eventually help repo to grow
I think there should be a github action to welcome contributors on their each issue and PR so as to make repository more interactive
If you love the idea , please assign this to me

@vytas7 Should I move further with this  ?

No, the maintainer team needs to make a decision whether we want this behaviour. Let us get back to you once we've discussed this.

Hi again @Jassi10000,
We have now discussed this and decided not to proceed with such an action at this time, but thanks for bringing this up.
If anything, we will probably explore Github issue templates as a first step, which could potentially make the triage process more efficient.

Sure sir , no issues


Picture upload on progress hook is not effective

测试环境使用生效
使用webpack打包后on-progress失效
打包命令:npm run build:prod

+1

I fixed this bug by delete mockJs


Opening "." in ArchiveFS, when using Stream fails with invalid argument

What version of the package or command are you using?
github.com/mholt/archives v0.0.0-20241216060121-23e0af8fe73d
What are you trying to do?
I am trying to open an archiveFS (I don't think it matters that much which one, but it's .tar.gz) using the Stream I provide and then reading the special case ".".
What steps did you take?

Small reproduction
package main

import (
	"context"
	"errors"
	"fmt"
	"io"
	"os"
	"path/filepath"
)
import "github.com/mholt/archives"

func main() {
	f, err := os.Open("./test.tar.gz")

	if err != nil {
		fmt.Println(err)
		return
	}

	format, _, err := archives.Identify(context.TODO(), "test.tar.gz", f)

	if err != nil && !errors.Is(err, archives.NoMatch) {
		fmt.Println(err)
		_ = f.Close()
		return
	}

	if _, err := f.Seek(0, io.SeekStart); err != nil {
		fmt.Println(err)
		_ = f.Close()
		return
	}

	info, err := f.Stat()

	if err != nil {
		fmt.Println(err)
		_ = f.Close()
		return
	}

	fs := archives.ArchiveFS{Stream: io.NewSectionReader(f, 0, info.Size()), Format: format.(archives.Extraction), Context: context.TODO()}

	archiveDir, err := fs.Open(".") // Fails here with `invalid argument`

	if err != nil {
		fmt.Println(err)
		return
	}

	stat, err := archiveDir.Stat()
	if err != nil {
		fmt.Println(err)
		return
	}

	fmt.Println(stat.IsDir())

	_ = archiveDir.Close()

	_ = f.Close()
}

What did you expect to happen, and what actually happened instead?
I expected the Open(".") to return a directory file handle. What actually happened, is that it read everything internally correctly and then failed to close archiveFile, which is nil, as I am using a Stream.
How do you think this should be fixed?
Before closing handle https://github.com/mholt/archives/blob/23e0af8fe73df29b749ae01ab2de86845585aa44/fs.go#L401 check if the archiveFile exists, as currently it tries to close on nil.
Please link to any related issues, pull requests, and/or discussion
N/A or haven't found
Bonus: What do you use this package for, and do you have any other suggestions or feedback?
I use it to create/extract archives in docker containers. In this context, walking the archive to find if the extracted archive fits in the limited disk space of the containers. (In a downstream version of https://github.com/pterodactyl/wings)

Thanks, that's a good find. Appreciate the pointer. Fixed, I think!


Propagate dataflow errors that are added to a Vector.Builder using .append

Currently, attempting to add an uncaught dataflow error to a Vector.Builder results in nothing being added, and the error is not propagated. It should be detected and propagated by Builder.to_vector.
The same logic should be applied to .set and .append_vector_range.

With #9725 and while in Vector.build builder-> callback one could throw a Panic on Error being appended, catch it in the caller of the callback and turn it back to Error - e.g. we could interrupt the addition sequence immediately when we know the result is going to be an error.


Server closes before download is completed

I was trying to send some audios to my phone, on the first file, I got the behavior depicted in the image on the first try and on the second one the download finished successfully, when transferring the second audio I think I tried 3 times and got this behavior the 3 times, I don't know if this would be specific to my phone or something, but maybe an option to keep the server running or adding a delay to it could solve this(assuming I didn't do anything wrong).
Files were around 30mb of mp3. Using Ubuntu 16.04.

Hi, I think you are affected by this issue: https://github.com/claudiodangelis/qr-filetransfer/issues/13
Please check the last comment of that thread, the user has a working solution on their fork which needs testing, maybe you can have a look?
I will check It out myself in a few hours, thanks!

Hey @claudiodangelis, sry for the delay, I've tried @tssva's branch and seems it's fixed there :+1: My only comment is that my previous install was running on go 1.6.3, I then tried building it on 1.7 and finally on 1.10 for it to build. Thank you both.


🚀 Feature: TechDocs comment system

🔖 Feature description
Introduce a comment system for TechDocs. A URL-based per page comment support for docs.
🎤 Context
Interacting with software documentation would be a nice addition. Users are already inside backstage to view the documentation. Would be nice to discuss certain things about the docs without leaving backstage.
Leaving approvals, asking questions about the docs, recording decisions
✌ Possible Implementation
I was thinking for a first step a pretty basic might even say naive implementation.
Create a new backend plugin: techdocs-comments-backend. Create a table where we would store the comments for each techdocs URL.
Extend the techdocs addon framework to be able to add a footer component. Provide a techdocs-comments package with the frontend work with the input field and the display components of the comments.
I wouldn't consider adding replies I think a similar system like GitHub PR/Issue comments would work as a starter. Only top-level comments, no replies. One tricky part is we should probably flag comments if the underlying docs changed since the comment and I'm not sure if techdocs currently is versioned or not
👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

@alper98 and/or @efenner-cambia didn't you have a similar request before?
@kissmikijr, is it safe to assume that this is something Roadie would be building and contributing as open source? Are you looking for feedback on this?

I don't think I made a similar request, but I do agree that it would be useful. And it has been requested before: https://github.com/backstage/backstage/issues/21091

I've not requested it before, i have however seen a similar request.
I'm wondering though, how this seperates it self from the current techdocs reportissue addon

@awanlin Right now we won't have time to work on this in company time.
However I personally think it's a nice feature and might going to work on this in my spare time.
I wanted to raise this request to get a feel for it from you guys what do you think about it. Would it make sense to add something like this to techdocs. I think some changes will be needed in the core techdocs stuff for it to work properly (but might not be the case) most of it could be in their own plugins/extensions/techdocs addons etc.

No worries 😀

@alper98 Great question

I'm wondering though, how this seperates it self from the current techdocs reportissue addon

The current report issue addon uses scaffolder templates to interact with your current documentation if you would like to tweak/suggest something.
This addon aims to support comments in the way we do it currently. In the techdocs page somewhere probably under the docs imagine this thread where people can discuss stuff about the docs.

Any update here?

Hi there! After some discussion, we're not sure if this is the right type of feature we want to add to TechDocs at the moment, at least not in its proposed form. Following the ethos of "docs as code", we're not sure if introducing context about documentation into a separate backend plugin's database is the right model to follow. If there are comments on certain pieces of documentation, it seems like VCS issues may be the right place for these to continue to live, especially since commenting and comment history are first-class features of VCS issues that may confusingly compete for a techdoc user's attention if both were used.
However, it seems like there's a desired feature of "we want to view issues on this piece of documentation in context while we read it, much like Google Docs". Perhaps this could be structured as an addon to better display + raise awareness of issues within the page?
Happy to discuss this further. For full transparency, we as maintainers don't have immediate capacity to implement this idea soon, but would like to get this in a state where the community can come up with a solution.


Fix repeating set of tweets load #250

The issue was in:

User-Agent header
Params encoding
min_position mechanism change

Searching seems to be working fine, however --location flag causes error:

Request() missing 1 required positional argument: 'connector' [x] get.Tweet

My command:
python3 Twint.py -s "#dieselgate" --since "2015-09-18" -o dataset.csv --csv --hashtags --stats --location

@PiotrJZielinski It should be working now.

Thanks! Indeed it does. Minor issue: once in a while

'NoneType' object has no attribute 'find' [x] get.Tweet

pops in throughout tweets fetching.

This is probably related to empty twitter response issue. Should be fixed soon after I believe.

@Mehdzor bad news, I waited for my code to execute and it stopped fetching after sth like ~10k of tweets. No error message, just finished job. I've been using same command as in first post. Am I doing something wrong?

This is still about empty response. Sometimes twitter returns empty response and it is considered as an end of the data. It will be fixed soon but not in this PR.

It is being tested right now.

For some tweets I'm also getting
'NoneType' object has no attribute 'find' [x] get.Tweet
and using Profile() for a username doesn't get full history. I updated from pull request #271 thinking that might fix it, but no dice. Should I file a new bug report or is this the same issue?

@LaurenDahlin I merged #271 as patch for this kind of errors, please update your Twint package with pip3 install --upgrade -e git+https://github.com/twintproject/twint.git@origin/master#egg=twint and let us know if the error comes again, if so, please provide us your query and we will investigate


Duplicate followup questions

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Any log messages given by the failure

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

Closing as potentially irrelevant due to changes in #163. Let's reopen an issue if it persists.


Do not write vector graph if all ordinals are deleted

Changes two components:

We will no longer write out the index components for vector indexes if all of the ordinals are deleted.
We can now handle vector graphs that were written without any non-deleted ordinals. This code is likely unnecessary, but protects us in the event any more of these indexes exist (the index that caused the issue was already deleted via compaction).

Other SAI indexes do not have deleted ordinals because they do not implement the MemtableIndex method:
    default void update(DecoratedKey key, Clustering clustering, ByteBuffer oldValue, ByteBuffer newValue, Memtable memtable, OpOrder.Group opGroup)
    {
        throw new UnsupportedOperationException();
    }

But they can still end up with "nothing to index" if all the rows have null cells

However, this is consistent with this earlier part of the index writer where we have:
            if (!rowMapping.hasRows() || (memtableIndex == null) || memtableIndex.isEmpty())
            {
                logger.debug(indexContext.logMessage("No indexed rows to flush from SSTable {}."), indexDescriptor.descriptor);
                // Write a completion marker even though we haven't written anything to the index
                // so we won't try to build the index again for the SSTable
                indexDescriptor.createComponentOnDisk(IndexComponent.COLUMN_COMPLETION_MARKER, indexContext);
                return;
            }

Range/partition deletions are the only way that we can skip this code block for vector while still having all ordinals deleted.


lower bool literal value

Following up on #3805, this PR adds the literal value to ast::LiteralKind so when we lower we can use the actual value from the source code rather than the default value for the type. Ultimately I plan to use this for exhaustiveness checking in #3706.
I didn't include this in the previous PR because I wasn't sure if it made sense to add this information to ast::LiteralKind or provide some other mechanism to get this from ast::Literal.
For now I've only implemented this for boolean literals, but I think it could be easily extended to other types. A possible exception to this are string literals, since we may not want to clone around an owned string to hold onto in ast::LiteralKind, and it'd be nice to avoid adding a generic lifetime as well. Perhaps we won't ever care about the actual value of a string literal?

Hm! I wonder if we could use this for graying out paths that are known to not be taken or something (eg if true {} else {}).

I think we can. Going further, e.g. TypeScript uses literal or unit (meaning single-value) types to bring more type-safety and contextual typing. But, this should actually be the concern of rustc in the first place...


Wrong drag preview offset when dragSource is outside dragPreview box.

Hi, first of all — thanks for a great job done! It seems, however, that I found some corner-case issue which I'd like to report.
I'm currently trying to create a draggable component with its drag handle (connect via connect.dragSource()) being placed outside of the component's box (using absolute positioning). Everything works fine, but drag preview seems to receive wrong offset coordinates when dragging begins. After quick code review, I believe the issue to be inside react-dnd-html5-backend:OffsetUtils:getDragPreviewOffset function: you can see that coordinates of a node connected via connect.dragPreview() are being used to define ghost's position.
I'm not completely sure whether it's an actual bug that needs to be fixed or there just has to be some workaround to set ghost with a proper offset. I would appreciate any help, thanks in advance.

👍  I'm having the same issue, with a position:absolute and an overflow-x: hidden for scrolling

Did someone resolved this problem?


Sidebar Height Adjustment

Can you add an option for the sidebar height, please ^^. Is it possible to add bongocat without the compact mode, maybe next to the workplace name or icon ^^

Will see if I can do that


Build with uv instead of just pip

Description
Fixes #1323
Type of change

[ ] Documentation change (change only to the documentation, either a fix or a new content)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Infra/Build change
[ ] Code refractor

Changes
Please list the changes introduced in this PR:

build_tools picks uv or python -m pip depending on if pip exists or not
additional install_and_imports for uv's clean build environments

Checklist:

[x] I have read and followed the contributing guidelines
[x] The functionality is complete
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

@timmoon10 Thanks for looking into this! I've updated the PR to be just the uninstall_te_wheel_packages change.
I think it's easier for me to just maintain a fork than --no-build-isolation since (as far as I can tell) there's no way to tell rye to pass --no-build-isolation to uv.
Do you think we can (for the time being) support both build isolation and no build isolation? One way this might work is: if NVTE_FRAMEWORK contains frameworks that aren't in the current python environment, try installing them; otherwise use the existing package.


feat: proxy-robot-account in robot.tf

Requirements

Filling this template is required. Pull request without enough information to be reviewed may be closed

Description of the Change
platform/terraform/modules/registry_harbor/robot.tf with proxy-robot definition
Alternate Designs

Benefits

Possible Drawbacks

Verification Process

Applicable Issues

Need add kaniko cache project and adjust proxy robot permission


Issues building from quickstart instructions

I'm trying to build the bart binary from source but the prescribed make command fails, and it's unclear what is going wrong that I need to fix.
The docs state the following steps for building:
% git clone https://github.com/fermyon/bartholomew.git
% cd bartholomew
% make bartholomew

which results in
make: *** No rule to make target 'bartholomew'.  Stop.

I don't think `make bartholomew` is the right make command based off this previous [issue comment https://github.com/fermyon/bartholomew/issues/61#issuecomment-1092467847] by @radu-matei . I'm pretty sure it should be make bart. However the results there are still odd.

```zsh
% make bart
cargo build --release --manifest-path=bart/Cargo.toml
    Finished release [optimized] target(s) in 0.55s

Calling bart obviously results in the following:
zsh: command not found: bart

It strikes me as odd that the cargo commands from make bart build so quickly. Also, is the build target supposed to be a bin or a wasi file? I'd think it would be a bin since i need to execute that, but i cant find the bin in the target directory after calling make.
In case it helps with debugging here's a little information on the host I'm running this from
Linux version 5.19.2-arch1-2 (linux@archlinux) (gcc (GCC) 12.2.0, GNU ld (GNU Binutils) 2.39.0) #1 SMP PREEMPT_DYNAMIC Sat, 20 Aug 2022 16:11:19 +0000

And I do have spin installed from main.
% spin --version
spin 0.5.0 (c3bbfeb 2022-09-02)

make bart generates a binary you can find in target/release/bart — does that help?

yeah, that at least gets me the binary i need to install.
should the make command drop it in usr/bin/ though?

I opened a minor pr to make the make bart lifecycle clear in the docs. If y'all want this feel free to review and allow the CI to run.
https://github.com/fermyon/bartholomew/pull/122

The merged pr #122 resolves this.


small changes, mostly about pep8

Hi, thanks for this nice library.
I have made some changes if you wish to incorporate:

changed mixed usage of tabs and spaces to all spaces (reference).
added the import line in the usage part in readme.md.
deleted some unused imports
and changed has_key() to key in d which might even be a bit faster (reference)

@ofgulban for some reason I didn't get the notification for this, sorry!
I will review it during the weekend, thanks! :smile:

Haha, no problem :)


fix: correctly handle the default ::fetch style for statements

We've overridden the default value to our magic -123, which normally works, but if someone passes in PDO::FETCH_DEFAULT manually the method can't recognize it and throw an unimplemented error. This just makes sure the default is interpretted the same as -123, better matching the standard.
Added an appropriate test as well.

Thanks for fixing this!

Added in release https://github.com/vimeo/php-mysql-engine/releases/tag/0.7.3


Remember the last active tab and show it by default

From the HIG:

Restore the last viewed preference pane. If the user switches preference panes, your app should remember this change and show the same pane immediately the next time the user opens your preferences window.

We don't currently do that. I think we should do it when users call .show() without an argument, and mention in the docs that that should be the preferred way to show the preferences window, and refer to the HIG docs. This would be another benefit of having https://github.com/sindresorhus/Preferences/issues/14 and we could enforce it there.

I always disliked this in my apps, but it's the default behavior if I remember correctly: if you call NSWindowController.showWindow, it restores the pane before closing. In fact, it seems the window stays hidden all the time during the app's lifecycle and is not disposed when closed.

@issuehunt has funded $80.00 to this issue.

Submit pull request via IssueHunt to receive this reward.
Want to contribute? Chip in to this issue via IssueHunt.
Checkout the IssueHunt Issue Explorer to see more funded issues.
Need help from developers? Add your repository on IssueHunt to raise funds.

@sindresorhus has rewarded $56.00 to @divinedominion. See it on IssueHunt

:moneybag: Total deposit: $80.00
:tada: Repository reward(20%): $16.00
:wrench: Service fee(10%): $8.00


Submodules not completely removed

Performing a fresh clone and submodule update fails:
> git clone https://github.com/PowerShell/DscResources
> git submodule update --init
fatal: No url found for submodule path 'xDscResources/xAdcsDeployment' in .gitmodules

This occurs because several submodules were removed from .gitmodules but not removed from the cache. The following references need to be removed:

xDscResources/xAdcsDeployment
xDscResources/xCertificate
xDscResources/xComputerManagement
xDscResources/xDFS
xDscResources/xSharePoint

Thank you for reporting and fixing this!


Make sure Doxygen can write paths for cpp_long_names.

cpp_long_names was causing Doxygen to fail on Windows which then caused the tests to fail.  Doxygen could not write out the files if the repo was cloned to a moderately deep directory.
I use SHORT_NAMES = YES to prevent this but it can't be used for all projects since it causes the Pimpl tests to fail.  I'm not sure why.

Hmm ok interesting. Are you using Windows or something else like bash for Windows or whatever it's called now?
The test is only supposed to generate the file path that breaks if platform.system() != "Windows" (in CI the part of the test that breaks should get skipped). Can you share more information on the crash or error messages? Does it still break if you come the repo and run the tests from C:/exhale (much shorter path length)?

Hmm ok interesting. Are you using Windows or something else like bash for Windows or whatever it's called now?

Using GitBash, which is from the Git for Windows package.  platform.system() is 'Windows' when I check it in Python in the GitBash shell.  I don't think the shell is affecting this test.
Here's the relevant part:
-------------------------------------------------------------------------------------- Captured stderr setup ---------------------------------------------------------------------------------------
[~] error: Cannot open file C:/Users/4b796/Projects/_others_projects/exhale/testing/projects/cpp_long_names/docs_CPPLongNames_test_file_hierarchy/_doxygen/xml/classclass__that__is__longer__than__two__hundred__and__fifty__five__characters__long__which__is_b3ede03b695ca987c2d4a4e7f05f30e3.xml for writing!
[~] error: Cannot open file C:/Users/4b796/Projects/_others_projects/exhale/testing/projects/cpp_long_names/docs_CPPLongNames_test_file_hierarchy/_doxygen/xml/structstruct__that__is__longer__than__two__hundred__and__fifty__five__characters__long__which__i50119b87d5f473544b8165fa34a0cad2.xml for writing!
[~] error: Cannot open file C:/Users/4b796/Projects/_others_projects/exhale/testing/projects/cpp_long_names/docs_CPPLongNames_test_file_hierarchy/_doxygen/xml/unionunion__that__is__longer__than__two__hundred__and__fifty__five__characters__long__which__is_d964ced6248a839f08541098a5f8b500.xml for writing!
[~] error: Cannot open file C:/Users/4b796/Projects/_others_projects/exhale/testing/projects/cpp_long_names/docs_CPPLongNames_test_file_hierarchy/_doxygen/xml/namespacenamespace__that__is__longer__than__two__hundred__and__fifty__five__characters__long__whafbc602bde0658898d288d3ffbeb0b83.xml for writing!
(!) Did not locate file that defined define [namespace_that_is_longer_than_two_hundred_and_fifty_five_characters_long_which_is_an_absolutely_and_completely_ridiculous_thing_to_do_and_if_you_did_this_in_the_real_world_you_put_yourself_comfortably_in_a_position_to_be_downsized_and_outta_here_as_soul_position_would_explain_to_you::MAKE_IT_BIG]; no link generated.
(!) Did not locate file that defined define [namespace_that_is_longer_than_two_hundred_and_fifty_five_characters_long_which_is_an_absolutely_and_completely_ridiculous_thing_to_do_and_if_you_did_this_in_the_real_world_you_put_yourself_comfortably_in_a_position_to_be_downsized_and_outta_here_as_soul_position_would_explain_to_you::DEFINE_THAT_IS_LONGER_THAN_TWO_HUNDRED_AND_FIFTY_FIVE_CHARACTERS_LONG_WHICH_IS_AN_ABSOLUTELY_AND_COMPLETELY_RIDICULOUS_THING_TO_DO_AND_IF_YOU_DID_THIS_IN_THE_REAL_WORLD_YOU_PUT_YOURSELF_COMFORTABLY_IN_A_POSITION_TO_BE_DOWNSIZED_AND_OUTTA_HERE_AS_SOUL_POSITION_WOULD_EXPLAIN_TO_YOU]; no link generated.
(!) Did not locate file that defined enum [namespace_that_is_longer_than_two_hundred_and_fifty_five_characters_long_which_is_an_absolutely_and_completely_ridiculous_thing_to_do_and_if_you_did_this_in_the_real_world_you_put_yourself_comfortably_in_a_position_to_be_downsized_and_outta_here_as_soul_position_would_explain_to_you::enum_that_is_longer_than_two_hundred_and_fifty_five_characters_long_which_is_an_absolutely_and_completely_ridiculous_thing_to_do_and_if_you_did_this_in_the_real_world_you_put_yourself_comfortably_in_a_position_to_be_downsized_and_outta_here_as_soul_position_would_explain_to_you]; no link generated.
(!) Did not locate file that defined typedef [namespace_that_is_longer_than_two_hundred_and_fifty_five_characters_long_which_is_an_absolutely_and_completely_ridiculous_thing_to_do_and_if_you_did_this_in_the_real_world_you_put_yourself_comfortably_in_a_position_to_be_downsized_and_outta_here_as_soul_position_would_explain_to_you::typedef_that_is_longer_than_two_hundred_and_fifty_five_characters_long_which_is_an_absolutely_and_completely_ridiculous_thing_to_do_and_if_you_did_this_in_the_real_world_you_put_yourself_comfortably_in_a_position_to_be_downsized_and_outta_here_as_soul_position_would_explain_to_you]; no link generated.
(!) Did not locate file that defined variable [namespace_that_is_longer_than_two_hundred_and_fifty_five_characters_long_which_is_an_absolutely_and_completely_ridiculous_thing_to_do_and_if_you_did_this_in_the_real_world_you_put_yourself_comfortably_in_a_position_to_be_downsized_and_outta_here_as_soul_position_would_explain_to_you::variable_that_is_longer_than_two_hundred_and_fifty_five_characters_long_which_is_an_absolutely_and_completely_ridiculous_thing_to_do_and_if_you_did_this_in_the_real_world_you_put_yourself_comfortably_in_a_position_to_be_downsized_and_outta_here_as_soul_position_would_explain_to_you]; no link generated.
(!) Did not locate file that defined function [namespace_that_is_longer_than_two_hundred_and_fifty_five_characters_long_which_is_an_absolutely_and_completely_ridiculous_thing_to_do_and_if_you_did_this_in_the_real_world_you_put_yourself_comfortably_in_a_position_to_be_downsized_and_outta_here_as_soul_position_would_explain_to_you::function_that_is_longer_than_two_hundred_and_fifty_five_characters_long_which_is_an_absolutely_and_completely_ridiculous_thing_to_do_and_if_you_did_this_in_the_real_world_you_put_yourself_comfortably_in_a_position_to_be_downsized_and_outta_here_as_soul_position_would_explain_to_you]; no link generated.

The file names shown are 263 characters long.  I think the error is Doxygen being unable to open the files for writing.
The full log if you need it: tests.log

Thanks @HexDecimal for trying to fix this.  The PR went out of scope, and the solution of forcing in the short names changes the meaning of the test.  These tests run in CI because it gets cloned closer to C:/, I have added #192 and will need to think about the right way to deal with this.


Add rosdep key for xsltproc.

Context here is wanting to transform URDF at build time in ways that aren't possible for xacro. Some OSes bundle xsltproc in the libxslt package, but Ubuntu has it separate, hence a separate key for Ubuntu and Debian.
The other way to handle this could be just adding xsltproc to the existing libxslt key.

+1


google map API  How to do it?

The following html file

we can see google map in browse. the https://maps.googleapis.com/maps/api/js?key=AIzaSyDZYYGcH34dgWnYlcAPEz3ioWHyjDbEQz8&callback=initMap is google javascript API ,but in our project ，How to do the API ？
I am rea determine  my 2D map can see in the browse

I haven't heard any response here, and it seems to have been also answer in #847, so I'm going to close it. If you still are having issues, please feel free to reopen the issue and give more details.


Either unsound rules or a bug in egglog

Here's a set of rules that results in constants being merged.
Several people have looked at the rules, but we can't find the bug. It's potentially a bug in egglog

Actually this one is probably easier to work with


Fixed #435 One shot replicator sends STOPPING state immediately

In case of One Shot replication,  STOP_GRACEFUL is fired almost immediately. It makes replicator state STOPPING instead of RUNNING during replication.
Like continuous replication mode, use waitForPendingStates() to wait till all tasks are completed, then fire STOP_GRACEFULLY at end of waitForPendingState() if mode is OneShot

I couldn't follow all logics so I reviewed the code as much as I can do.

Applied all feedbacks from @pasin. Please review this PR again.


Docs - remove personal info reqs

Go through docs and make sure it is more privacy friendly for applicants
E.g. no hard requirements for addresses, phone numbers, etc.

[ ]


Script to autogenerate mirrored and rotated assets

My goals with this PR:

Automate the generation of alternate assets *
Prevent forgetting to create alternate assets (see #198)
Set a precedent, this script can be extended to generate the "Two Palettes" assets for #171

*Note that this could be made as part of a GitHub Action to ensure we don't forget to run the script, and that manual changes in generated assets are cleared up. You could even automatically apply changes on PR (like an autofixer) using https://pre-commit.ci/ .
I went with Python because:

Wanting to keep this project free of compilation (all scripts are runtime). Performance is not that critical (the script runs in about 8s on my Ryzen 5 2600).
My other options were powershell and node (JS), Python already has great, easy to use C-binding libraries for image manipulation. It ended up easier and faster than the alternatives I could come up with.

First of all, thank you for your work.
Python would also be my preferred language for this.
The "Two Palettes" are used by many games, I want to make a generic style out of it to support these games as well.

The "Two Palettes" are used by many games, I want to make a generic style out of it to support these games as well.

Would you like me to do it in this PR as well? Or maybe first come up with a canonical name and representation in the file-system?
I know Pitfall is split in "RG" and "BA", but are there games using a different split?

Is the script name and location good for you? Would you like a GitHub action and/or pre-commit.ci config that checks/autogenerates these? Or maybe later.

From Discord:

Avasam 💻🧙 — 12/26/2023 7:59 PM
This makes me notice that _Rotated assets are strangely lower rez than the original assets??
Venomalia — Today at 3:56 PM
If you mean the quality, it depends very much on the filter and the API that is used. but it's not a big difference.
Avasam 💻🧙 — Today at 10:18 PM
I mean the current existing _Rotated assets in the main branch are half the width and height than their non-rotated counterpart.

For instance:

Name and location are good, you don't have to make any changes to the PR, I'm happy as it is.
I have to admit I'm not super familiar with GitHub action when it comes to scripts, but I don't mind setting it up as an action.

I know Pitfall is split in "RG" and "BA", but are there games using a different split?

Yes, this is used in exactly the same way in several games.
My TextureExtraction Tool and Bigheads Custom Texture Tool PS can now also split and recombine these textures.

The "Two Palettes" are used by many games, I want to make a generic style out of it to support these games as well.

Would you like me to do it in this PR as well? Or maybe first come up with a canonical name and representation in the file-system?

I think Seperart would be better because we also need a new template for the creator tool. I wanted to think about the name but the way you did it in Pitfall is perfectly ok.

The current existing _Rotated assets in the main branch are half the width and height than their non-rotated counterpart.

That's only because they are rarely used to save unnecessary storage space.


RTCIceCandidate format

The spec for the candidate message is as follows:
{
   "type": "candidates",
   "session": b"bb938a583e67923c6e9f2185a6a03773",
   "sdp": [
       "...",
       "..."
   ]
}

That assumes that the candidates are sdp strings. In the WebRTC RTCIceCandidate structure, that is contained in the candidate string attribute. On the other hand, ORTC does not provide such an attribute: http://ortc.org/wp-content/uploads/2015/06/ortc.html#h-rtcicecandidate
Can we simply send the entire RTCIceCandidate structure instead? Or is that too implementation-specific? Maybe we can define a key mapping?

I agree. The RTCIceCandidate interface should be pretty fixed - I'm not expecting any changes to it for either WebRTC or ORTC. However, they should be treated as individual types.
Also, we want to be independent from the browser's implementations. Thus, the MessagePack serialisation must be crystal clear in the protocol spec.

ORTC:
dictionary RTCIceCandidate {
             DOMString              foundation;
             unsigned long          priority;
             DOMString              ip;
             RTCIceProtocol         protocol;
             unsigned short         port;
             RTCIceCandidateType    type;
             RTCIceTcpCandidateType tcpType;
             DOMString              relatedAddress = "";

WebRTC:
dictionary RTCIceCandidateInit {
    required DOMString      candidate;
             DOMString      sdpMid;
             unsigned short sdpMLineIndex;
};

[ Constructor (RTCIceCandidateInit candidateInitDict)]
interface RTCIceCandidate {
    readonly        attribute DOMString               candidate;
    readonly        attribute DOMString?              sdpMid;
    readonly        attribute unsigned short?         sdpMLineIndex;
    readonly        attribute DOMString               foundation;
    readonly        attribute unsigned long           priority;
    readonly        attribute DOMString               ip;
    readonly        attribute RTCIceProtocol          protocol;
    readonly        attribute unsigned short          port;
    readonly        attribute RTCIceCandidateType     type;
    readonly        attribute RTCIceTcpCandidateType? tcpType;
    readonly        attribute DOMString?              relatedAddress;
    readonly        attribute unsigned short?         relatedPort;
    serializer = {candidate, sdpMid, sdpMLineIndex};
};

It looks like WebRTC uses the candidate string together with sdpMid and/or sdpMLineIndex to create an RTCIceCandidate object. In ORTC you construct that object directly.
From the spec I did not really understand what the sdpMid and sdpMLineIndex do. But we could probably choose the same structure as ORTC and then construct the candidate string from that in WebRTC?

Let's just send the whole RTCIceCandidate instance as defined above as a generic JSON object (serialised to a MessagePack map on the wire and unserialised to a generic JSON object before it's being passed to an onCandidate event) and leave it up to the users which fields they want to use to reconstruct the RTCIceCandidate. The SDP-stuff is not really well explained because it's not meant to be modified and... I don't really understand it either. (Personally I think SDP is an unnecessary burden - that's why I like ORTC.)

Ok, so this would be the RTCIceCandidate?
interface RTCIceCandidate {
    foundation: string,
    priority: number, // unsigned long
    ip: string,
    protocol: 'tcp' | 'udp', // RTCIceProtocol
    port: number, // unsigned short
    type: 'host', 'srflx', 'prflx', 'relay', // RTCIceCandidateType
    tcpType?: 'active' | 'passive' | 'so', // RTCIceTcpCandidateType
    relatedAddress?: string,
    relatedPort?: number, // unsigned short
}

Nicht ganz. Wir senden auch die Felder candidate, sdpMid und sdpMLineIndex, falls WebRTC genutzt wird.

Well, but what if both candidate and the other fields are filled out with conflicting information? Which one is authoritative?
If it's easy to deduce the candidate from the fields above, I don't think we should include redundant information.

I'm with you - yes, the information is redundant. But you can't reconstruct an RTCIceCandidate instance without candidate, sdpMid and sdpMLineIndex (see the RTCIceCandidate interface constructor). At least not for WebRTC.
For us, another option would be to just send candidate, sdpMid and sdpMLineIndex for WebRTC and the well defined RTCIceCandidate interface for ORTC (which is also slightly different to the one that WebRTC defines).

That would probably be the best approach for now. The implementors know which library they want to use :)


create an ISSUE_TEMPLATE

See https://raw.githubusercontent.com/square/okhttp/master/.github/ISSUE_TEMPLATE.md
What kind of issue is this?

 - [ ] Question. This issue tracker is not the place for questions. If you want to ask how to do
       something, or to understand why something isn't working the way you expect it to, use Stack
       Overflow. https://stackoverflow.com/questions/tagged/spring-cloud

 - [ ] Bug report. If you’ve found a bug, spend the time to write a failing test. Bugs with tests
       get fixed. Here’s an example: <todo>

 - [ ] Feature Request. Start by telling us what problem you’re trying to solve. Often a solution
       already exists! Don’t send pull requests to implement new features without first getting our
       support. Sometimes we leave features out on purpose.

https://help.github.com/articles/creating-an-issue-template-for-your-repository/


iOS 12.1.3-12.2 Support

And 12.3, like the original unc0ver

Yes, but only 12.3 b1-b5
Watking01<EMAIL_ADDRESS>schrieb am Fr. 26. Juli 2019 um 16:21:

And 12.3, like the original unc0ver
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nqcshady/unc0ver-dark/issues/64?email_source=notifications&email_token=AK6KPAAEJDMSZYYVLEMZSBDQBMB6VA5CNFSM4IFIWGZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD24YBSQ#issuecomment-515473610,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AK6KPAA2WYU5OCRWKKQP6OTQBMB6VANCNFSM4IFIWGZA
.

It's getting worked on. No eta. Waiting patiently is your best bet. @neumaif02 @Watking01

Why does this take so long?
Syndrome(Buddy Pine<EMAIL_ADDRESS>schrieb am Sa. 27. Juli
2019 um 09:15:

It's getting worked on. No eta. Waiting patiently is your best bet.
@neumaif02 https://github.com/neumaif02 @Watking01
https://github.com/Watking01
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nqcshady/unc0ver-dark/issues/64?email_source=notifications&email_token=AK6KPAANH3RE7NDYHYQ75B3QBPYZZA5CNFSM4IFIWGZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD26FSAA#issuecomment-515660032,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AK6KPAFPWRREFHDJNQ6TMSLQBPYZZANCNFSM4IFIWGZA
.

@neumaif02 Stop acting entitled, you assume that it shouldn't take that long. How bout I just stop adding support because of you.

Sorry😢. But why does this take so long?
Syndrome(Buddy Pine<EMAIL_ADDRESS>schrieb am Di. 30. Juli
2019 um 03:17:

@neumaif02 https://github.com/neumaif02 Stop acting entitled, you
assume that it shouldn't take that long. How bout I just stop adding
support because of you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nqcshady/unc0ver-dark/issues/64?email_source=notifications&email_token=AK6KPAFJPY7WJ53ALG5NDILQB6JEPA5CNFSM4IFIWGZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3COMXA#issuecomment-516220508,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AK6KPAEAJOANAROJYXTW2LLQB6JEPANCNFSM4IFIWGZA
.

Any updates?


Can't save the default settings for subtitle

I'm submitting a ...

[x ] bug report
[ ] feature request
[ ] support request

General infomration
Raspberry Pi with the latest build of Kodi
Prerequisites

[x ] Are you running the latest version?
YES

Description
When I watch serie I have to select the subtitle (swedish) everytime I watch a episode.
Even if I say in the setting that swedish is going to be default.
Expected behavior: [What you expected to happen]
Show swedish subtitle as default.
Actual behavior: [What actually happened]
Disable the subtitle when it start a new episode
Installation

[ ] I installed the plugin via zip from the Releases page
[ x] I´m using the Netflix Repo
[ ] I´m using a different source (Please tell which)

Operating System

[x ] Linux (x86/x64)
[ ] OSX (x86/x64)
[ ] Windows (x86/x64)
[ ] Linux (ARM)
[ ] Android

Additional informatin on the environment
LibreElec latest update.

Got it to work.
I did have to select swedish in Kodi players too.


[$500] Thread - In offline, tapping 3 dots on top and selecting "Join", user unable to join the thread.

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.15-4
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:
Pre-condition: Turn off mobile data

Go to https://staging.new.expensify.com/
Tap on a report
Send a message
Long press the sent message and select reply in thread
Send a message
Tap 3 dots on top and select Leave the thread
Tap reply
Tap 3 dots on top and select Join the thread
Again tap 3 dots on top and note user can't join the thread

Expected Result:
In offline, when user taps three dots on top and select Join the thread, user must be able to join the thread. When user taps 3 dots again, "Leave" option must be displayed
Actual Result:
In offline, when user taps three dots on top and select Join the thread, user unable to join the thread. When user taps 3 dots again, same "join" option displayed instead of "Leave"
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/b2e1735c-4041-4093-aec9-3b162a589375
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01bdc70a567b7f40a2
Upwork Job ID:<PHONE_NUMBER>673898496
Last Price Increase: 2023-12-22

Proposal
Please re-state the problem that we are trying to solve in this issue.
In offline mode, user can't join/leave the chat room and 'Join' button keeps displaying after clicked.
What is the root cause of that problem?
Join button shows when notificationPreference is hidden:
https://github.com/Expensify/App/blob/659f509b7e1093252d7c2ea14d0082ee78dd6503/src/pages/home/HeaderView.js#L145
When user clicks on Join, it will update notification preference to always:
https://github.com/Expensify/App/blob/659f509b7e1093252d7c2ea14d0082ee78dd6503/src/pages/home/HeaderView.js#L150
The problem is, update failed because reportID for the chat is undefined.
What changes do you think we should make in order to solve the problem?
Get the correct reportID from route:
const currentReportIDValue = useCurrentReportID();
const reportID = props.report.reportID || currentReportIDValue?.currentReportID

and pass it to both join and leave actions:
Join:
onSelected: Session.checkIfActionIsAllowed(() =>
                    Report.updateNotificationPreference(reportID, props.report.notificationPreference, CONST.REPORT.NOTIFICATION_PREFERENCE.ALWAYS, false),
                ),

Leave:
onSelected: Session.checkIfActionIsAllowed(() => Report.leaveRoom(reportID, isWorkspaceMemberLeavingWorkspaceRoom)),

What alternative solutions did you explore? (Optional)
N/A

Proposal
Please re-state the problem that we are trying to solve in this issue.
In offline, Join room option isn't responsive after leaving the room
What is the root cause of that problem?
For the optimistic data of the LeaveRoom we are setting the reportID to null in this PR and notificationPreference set to hidden here
https://github.com/Expensify/App/pull/33053/files#diff-ce6bb391d0654bf99a360da7d25fd73b85bb120211c8b4c2432ef7c7d8c708f3R2068
https://github.com/Expensify/App/blob/659f509b7e1093252d7c2ea14d0082ee78dd6503/src/libs/actions/Report.ts#L2071-L2074
With that below condition turns to true and we are showing Join option without having reportID.
https://github.com/Expensify/App/blob/659f509b7e1093252d7c2ea14d0082ee78dd6503/src/pages/home/HeaderView.js#L144-L145
cc: @blazejkustra
What changes do you think we should make in order to solve the problem?
We don't need to show the Join or Leave option when the reportID is not available by adding that condition here.
https://github.com/Expensify/App/blob/659f509b7e1093252d7c2ea14d0082ee78dd6503/src/pages/home/HeaderView.js#L144

Once a PR is up please make sure that issues linked in this PR aren't reproducible

@eVoloshchak what are the next steps for this one?

@eVoloshchak bump

I think we should proceed with @tienifr's proposal
It is similar to @zukilover's proposal, but @tienifr's approach of using allReports is much cleaner
🎀👀🎀 C+ reviewed!

@miljakljajic, this has caused a regression in https://github.com/Expensify/App/issues/35076, the amount should be $250

Updated!

$250 approved for @eVoloshchak based on this summary.


Declare support for Python 3.13

  + /home/runner/work/flake8-pyi/flake8-pyi/pyi.py:1484: DeprecationWarning: Tuple.__init__ missing 1 required positional argument: 'ctx'. This will become an error in Python 3.15.

This will go away in the next beta. We could just add ctx=ast.Load() though to make things work now.

I think I'm inclined to keep our code how it is and wait for the next beta (scheduled to arrive in just over two weeks, and I think Thomas might be planning to expedite it even more due to some bugfixes that didn't quite make it into beta1). I'll just mark this as a draft for now.

Well, the latest update is that Python 3.13.0b2 is now available on setup-python, but the build they provide is apparently utterly broken:

https://github.com/actions/setup-python/issues/886

Tests all pass locally for me with 3.13.0b2, though, so I guess I'll mark as "ready for review"


Filter sensitive headers in debug logs with :sanitize_headers

Basically the same as Phoenix' config :phoenix, :filter_parameters, ["password", "secret"] but for Tesla debug logs and headers.
# your client
plug Tesla.Middleware.Logger, filter_headers: ["authorization"]

# >> REQUEST >>>
# authorization: [FILTERED]
# user-agent: Mozilla
# << RESPONSE <<
# ...

While you generally don't want to enable debug logs in production, it can be useful to do so once in a while.

Nice! 👏 👏 👏

Fantastic! Thanks for your time and support @teamon


Implement automatic registry credential fetching & auth status command

Fixes https://github.com/jetstack/jsctl/issues/9
We are building an improved installation flow where users are guided through installing the operator using in the Jetstack Secure UI. These changes are to make that easier by:

Not requiring users to have registry credentials downloaded to install the operator
Making flag names for registry credentials distinct from JSCP credential files
Allowing users to see who is logged in and what their current organisation is with jsctl auth status

Thanks Irbe, I have updated this now to allow users to optionally specify --auto-registry-credentials to enable this behaviour. If this is not set, and there are no other paths to credentials set, then the configuration will be generated without image pull secrets - the assumption being that they're installed via another means or the images are public.


Private links

Links that are visible only to users creating them, and CRUDable only by those users.

This was implemented already in #21 ahead of time so closing this now.


[TEST] Rancher v2.9.0 alpha integration test of Harvester charts for K8s v1.29

In order to test the K8s v1.29 support for Harvester-cloud-provider and Harvester-csi-driver of the following tickets:

https://github.com/rancher/rancher/issues/45470
https://github.com/rancher/rancher/issues/45471

We need to perform Rancher v2.9.0 integration test with Harvester v1.3.1
Test environment

Rancher 2.9.0-alpha2 (Prime)
Harvseter v1.3.1
K8s: v1.29
Type: RKE2, RKE1

Test plans

[ ] 1. RKE2: Necessary checks for cloud provider and csi driver working on cluster.
[ ] 2. Execute Rancher integration test backend automation test
[ ] 3. RKE1: Install, uninstall of cloud-provider and csi-driver
[ ] 4. RKE2: upgrade v1.28 to v1.29
[ ] 5. Create RKE2 guest cluster using terraform, custom cluster, import cluster
[ ] 6. Scale down and scale up of guest clusters
[ ] 7. Delete cluster
[ ] 8. Upgrade Rancher from v2.8.5 -> v2.9.0-alpha4 with RKE2 guest cluster

Verifying on Rancher v2.9.0-alpha4 with Harvester v1.3.1 for K8s v1.29.5
Result
$\color{blue}{\textsf{Ongoing}}$ RKE2: Necessary checks for cloud provider and csi driver working on cluster. $~~$

Can provision v1.29.5 RKE2 cluster well
$\color{green}{\textsf{PASS}}$: $~~$

Check the default cloud provider version:
$\color{red}{\textsf{FAILED}}$: default cloud provider version is 0.2.3 not 0.2.4 $~~$

Test Information

Test Environment: Single nodes harvester on baremetal machine
Harvester version: v1.3.1
Rancher version: v2.9.0-alpha4
K8s version: v1.29.5

Verify Steps
Necessary checks for cloud provider and csi driver

Original

Scale up

After complete the full Rancher integration on Rancher v2.9.0-alpha5 with Harvester v1.3.1
Most of the provision of RKE2, RKE1 cluster, bundle chart of Harvester cloud-provider and csi-driver are working as expected.
As the above test result stated:
https://github.com/harvester/tests/issues/1337#issuecomment-2192059083
We can pass the following test scenarios

RKE2: Necessary checks for cloud provider and csi driver working on cluster.
Delete RKE2 guest cluster on Rancher v2.9.0-alpha5
Execute Rancher integration test backend automation test
RKE1: Provision, install, uninstall of cloud-provider and csi-driver
Delete RKE1 guest cluster on Rancher v2.9.0-alpha5
Scale down and scale up of guest clusters
RKE2: upgrade RKE2 from v1.28.10 to v1.29.5
RKE2: Upgrade Rancher from v2.8.5 -> v2.9.0-alpha5 with RKE2 guest cluster

While we found the harvester-cloud-provider chart bundled with RKE2 v1.29.5+rke2r1 is not yet updated to the latest version v0.2.4
According to the investigation result in comment https://github.com/rancher/rancher/issues/45470#issuecomment-2190719068, we need to wait next release for v1.29.6+rke2r1 to have v0.2.4 cloud provider bundled on it.
And we encounter the following failure while executing the following cases

Create RKE2 guest cluster using terraform-provider-rancher2

Use both automation test or manually execution, both the RKE2 cluster stuck in "waiting for cluster agent to connect"
We have created Harvester issue https://github.com/harvester/harvester/issues/6098 to track the failure

Create v1.29.5 RKE2 guest cluster using import cluster

When we have RKE2 cluster imported to Rancher and try to install csi-driver and cloud-provider, the cloud-provider can't fully deployed which cause failed to create the load balancer service
We have create Harvester issue https://github.com/harvester/harvester/issues/6099 to track the failure

We also encounter issue when access the virtualization management in Rancher
Access Harvester in Rancher virtualization management, most of the UI text are displayed with the incorrect %variable-reference%

We also created the following issue for a track:
https://github.com/rancher/dashboard/issues/11349
https://github.com/rancher/dashboard/issues/11350

Close this since we have finished all task activities.