flex becomes flex="flex" which breaks in Angular Material for Meteor

Hi,
I am working on an angular+meteor project using the package civilframe:angular-jade to enable ng.jade templates.
This package is using this Jade package for compiling.
Anyway, I noticed that when ng.jade is converted it tends to change the single attributes without value.
div(flex) Foo
becomes
Foo
It should just stay
Foo
because Angular Materials is tripping over this. It doesn't know flex="flex" and turns into class="flex-flex" :)
Is there an easy fix to not convert attributes that are without value?

@mattiLeBlanc yes, this is a known issue and the workaround is to do this div(flex="") Foo.
It is possible to implement a global change to this repo to support the what you're asking, but it would affect those people who depend on the current functionality.
The jade compiler itself has an option { doctype: 'html' }, which when combined with this line at the top of your code doctype html, results in what you're after. But, as I said, some people depend on the current functionality.
@civilframe what are your thoughts on this topic?
I'm thinking angular jade partials/templates never have doctype htmlat the top of the file. So, I could prepend that to each file and add the option { doctype: 'html' } to the compiler options. Then, I would need to remove the first line <!DOCTYPE html> from the generated HTML. It's certainly doable, I'm just not sure we should do it.

It wasn't and issue before angular Material 0.11.12, but I see angular is already at version 0.11.14 and they said they where going to support flex="flex".
So maybe you don't have to do anything?

So, are ok with my above suggestion to explicitly use the flex="" syntax?
If so, then can we close the issue?

The jade compiler does this by default, so I would just do flex="".

yes I concur.


son-package: retrieve external dependencies with son-access

addresses issues #133 and #132

test this please

test this please

test this please

test this please

test this please


Issue/remove redundant test case

Description
Remove test case test_override_inmanta_dev_dependencies_package because it hard codes a specific version of the inmanta-dev-dependencies package, which makes the test case fail. It can be removed because the test case doesn't add much value to the test suite.
Self Check:

[ ] Attached issue to pull request
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation

Processing this pull request

Merged into branches master in 88b5c9ceaa9d759c1bae89aa891f35fab7ba20f4

Processing #5195.


Edit in settings.json is not helpful

During settings sync user study - Everyone was confused when they clicked on “Edit in settings.json”, they expected to start editing the setting in the settings.json file

I also came to the same conclusion when I try it myself before they I saw participants do it. I thought we used to support this? @roblourens mentioned yesterday that auto save complicates this.

#67908

Also sort of related to https://github.com/microsoft/vscode/issues/89512
I still feel that giving the "edit in settings.json" button side effects will be bad because users will end up with lots of settings configured as their default values, which is confusing, but we could experiment.


Create a dummy backend instance so it's easier to test frontend locally

Having a dummy backend with a publicly available .env would lower the entry barrier to crowd-sourcing improvements to the frontend.

That would be great.

Closing as the new UI/backend has been developed after this issue was opened and this issue relates only to the old system.
In the new system, we are able to do entirely local development (-Twilio/Sendgrid) using Parse locally + Ngrok to route Twilio callbacks.


Error: Right-hand side of 'instanceof' is not callable

Versions:

VueJs: 2.8.2
Vee-Validate: 2.0.0-rc.8

Description:
Hi all,
I have this error, "Right-hand side of 'instanceof' is not callable at HTMLInputElement.fn", when i try to test the validation on the input field, in my Vue project done by Vue CLI. So it has the

Are you by any chance overwriting the Event global constructor in your app, if not there might be a plugin that does, I don't think overwriting native Objects/Functions is a good practice.

Hi @logaretm , I have gone through what you said and I realized that I have this code in my main.js.
Main.js
class Dispatcher {
  constructor () {
    this.vue = new Vue()
  }
  fire (event, data = null) {
    this.vue.$emit(event, data)
  }
  listen (event, callback) {
    this.vue.$on(event, callback)
  }
}

window.Event = new Dispatcher()

So after commenting it out, validation is able to work perfectly fine now.
Thank you for your help!

@maryheng Glad it worked 😄
I realize it was nifty to just call Event.fire. You might need either rename the module you are setting or take advantage of es6 modules and export the dispatcher, so you can import it and use whenever you want and you won't have to inject it globally.

Check in one of your props is not set right way , for example
props: {
  element: ['string']
}

This is wrong way
props: {
  element: [String]
}

This is the right way , i had this issue and fixed it this way ; i hope this will be helpful for someone


feat(filterprocessor): enable log filtering

This PR enables strict and regexp filtering of logs based on resource attributes using filterprocessor.
ref: https://github.com/pmalek-sumo/opentelemetry-collector-contrib/commit/6643765789daf85c51150b5de8bb64a82d9c52e0
related PR upstream that will introduce this when merged: https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/5237

If we plan to use this processor it will be to add it to documentation https://github.com/SumoLogic/sumologic-otel-collector/blob/main/docs/Configuration.md#processors, without link to proper docs it is difficult to find how to configure this processor.


catch all Exceptions, transmit traceback back from remote

before this changesets, most informations about exceptions/tracebacks
on the remote side were lost. now they are transmitted and displayed,
together with the remote attic version.

closing this pull request, seems unwanted.


belongs to relationship won't show without preloading, but preloading is not necessary

Hello all,
I am trying to implement JSON:API endpoints where I have belongs_to relationship so the ID is directly in the loaded table, but this library (probably because of https://github.com/jeregrine/jsonapi/pull/103) won't show these relationships unless they are explicitely loaded.
I think preloading the belongs_to relationship makes no sense as we only display the ID and type. For has_many relationship, the current behaviour is of course desirable.
Here is a workaround by setting the relationship by hand:
def show(conn, %{"id" => id}) do
    object = Document.get_document{(%{login_id: conn.assigns[:login_id], id: id})

    object = %{object | folder: %{id: object.folder_id}}
    render(conn, "show.json", data: object)
end

After this the folder relationship will be included and no other SQL queries (or joins) need to happen...
What do you think? Am I missing something?

I totally agree with you. I've been trying to come up with a resolution to this in #174 , but I'm a bit drained for time at the moment. The biggest challenge as I see it is changing how relationships work whilst providing a clean upgrade path.


chore: add example parsing script

Hello!
This adds an example parsing script similar to other tree-sitter repos. The script is used to checkout repos and execute the grammar on the files to ensure there's no issues parsing files in the community. Currently this is just parsing Breeze, but we can add other popular repos as needed/desired.
This actually revealed two bugs (I'll open an issue):

@js is parsed as a conditional
No support for casting @foreach((array) $messages as $message)

Thanks!

Note that you can ignore errors by adding them to the known-failures.txt file, so there's nothing keeping this pr from being merged

Hi @calebdw, that is amazing! Thank you so much for doing this. I have always wanted to sort out the CI to streamline, but since I have zero experience and have never done it before, it kept getting pushed back!
Are there any resources you can suggest for me to read and learn about CI, as I am fairly new to CIs? Does the GitHub docs do the job?

@calebdw amazing. This is actually very neat!
I am also definitely up to add more repos to cover as much as possible!
One question though. may I ask how do you handle your conflicts with the tree-sitter-php parsers 🤔? so far the only way I could get this working was removing the tree-sitter-php from the path that was pointed to at config.json for tree-sitter. That was the main reason for naming the playground example file example.blade .
I have actually already raised an issue for this a while ago, as it was bugging me during the dev

I'm not sure what conflicts you're talking about? I haven't really had any issues...

@calebdw ah, let me elaborate more.
So let us say you have a folder where all you tree-sitter-x parsers live, and your tree-sitter per user configuration is pointing there. The conflict happens if you have tree-sitter-blade and tree-sitter-php both in the same folder.
When you run tree-sitter parse which is the case in the bash script, conflict occurs because both tree-sitter-blade and tree-sitter-php both hit .php extension. see here. To be honest the .php extension makes no sense as it is an old artefact from the early dev phase, I was trying to make up .blade.php and that was not possible based on the issue in my previous comment. Ever since then I was mainly using the .blade for debug parsing etc.
The Parse Error Example

So when I first ran this, I was getting an error that no grammar.js is found or the file does not exists (confusion on which parser to use)
I can not reproduce that because I deleted the tree-sitter-php and now I do not get the error after reinstalling. 🤷♂
After cloning the tree-sitter-php again, and I am getting the stuff parsed in the example/. But the results are an illusion! It is using the tree-sitter-php instead of tree-sitter-blade

To reproduce

Have both parsers in the folder
remove the stuff in the known-failures.txt
then run the script
As shown in the image you will get 100% and no issues to report
Now delete the tree-sitter-php or move
Run the script again and you will get the correct parsing with the errors.

Fix?

All I can come up with to avoid confusion, is adding another for loop in the bash script that changes all the .blade.php into .blade ?

I am actually surprised that you managed to parse with no issues, considering that you are working with/on both parsers 🤔 Would be interesting to know how and why! :)

Hmm, I've never run into any issues, and I've never touched the default treesitter config so just running with the defaults. I install all of my repos at ~/sources and all of my treesitter repos go under ~/sources/treesitter, so I have:

~/sources/treesitter/tree-sitter-blade
~/sources/treesitter/tree-sitter-php
...

and I've never had any conflicts

Mmm that is so strange now! Your set up is pretty much like mine. So with this same set up if you:

Delete the content of the known-failures.txt
and then run the script.
you will correctly get the parse errors? 🤔

Can I ask your OS? Are you on Mac or Linux?

I tried that and still no issues. I'm on Linux (PopOS from System76)

@calebdw sorry my comments were sitting in the files as "pending", I thought it was "pending" awaiting your review!
What an awful UI/UX design by github!  However I went to the repo, when I was not logged in and realised it has not been submitted. Anyhow apologies for super delay getting back to you, this should have reached you a week ago maybe more! 😬

No worries!
I can try to add the --scope, but I'm not sure if that will work in the actual ci (the repo might not be in the ts path). If that's the case and there's a conflict, then the script should prefer ci use over local use for the time being

It should hopefully be fine in the CI 🤞, as it is based in the data in the package.json!
Of course if not we can revert etc as CI is more important. I will scramble an adjusted one maybe for my own local testing :)
I usually like to heavy stress test locally before I commit and this is a great tool to have in the toolbox!
It was nice to see new parsing issues arise after your first run using only one repo!

but I'm not sure if that will work in the actual ci
you were indeed right! I just revert it back to your original!


Please add reload schema support for HMR

it could be awesome if support something like:
  if (module.hot) {
    module.hot.accept('./schema') {
       server.replaceSchema(require('./schema'));
    }
  }

I am interested in this too. So far, I found it easy. Just have to do this: server.executableSchema = .... Subscriptions and middlewares may need some extra steps. Will see how it goes.


Trying to get Bitcoin Whitepaper by browing to the /bitcoin.pdf path.

Only getting "404 - PAGE NOT FOUND"

Same here. Bitcoin Whitepaper 1.0.2 is installed, /bitcoin.pdf is 404.

Same here .... latest version of BTCPayServer.

@Kukks ?

Fixed in latest version. Sorry for the delay

I just did an upgrade and it is still not working. Have you merged the fix already? @Kukks

Works for me in 1.0.3

Oh yes, it works now. had to go into "Manage Plugins" and update it from there. Thanks!


Unable to Import LIbrary

Hi.
I am using Python 3.9.12 with Anaconda.
I installed EntropyHub and then tried to import. I am not able to import the library. I am attaching the screenshot.
Please look into it.

This problem should be fixed with the new release of EntropyHub (v2.0) on PyPi
See here for more info


Feature Request:   Calculate workflow resource usage

For every workflow, many users want to know how many resource(cpu, memory) is used.   This info is very useful for user to compute costs.  We can use pod resource requests or limit to show every pod resource usage.
Maybe argo get <workflow> can show info like this.     Can someone accept this feature?  I can raise a PR to this.
Example:
➜  argo git:(release-2.2) argo get hello-world-gdpwz
Name:                hello-world-gdpwz
Namespace:           default
ServiceAccount:      default
Status:              Succeeded
Created:             Wed Oct 31 15:01:27 +0800 (4 minutes ago)
Started:             Wed Oct 31 15:01:27 +0800 (4 minutes ago)
Finished:            Wed Oct 31 15:01:50 +0800 (3 minutes ago)
Duration:            23 seconds
Total CPU:           0.00767    (core*hour)
Total Memory:        0.00639    (GB*hour)

STEP                  PODNAME            DURATION  MESSAGE  CPU(core*hour)  MEMORY(GB*hour)
 ✔ hello-world-gdpwz  hello-world-gdpwz  23s                0.00767         0.00639

Wonder if it would make most sense for resource utilization to simply be a step-level metric (https://github.com/argoproj/argo/issues/1539)

@xianlubird @ddseapy I have a whitespace day today I plan to work on this. At 5:30pm PST (8 hours away) I will down tools and what is done is done.
As I have limited time - I don't expect this can include $ cost.

@xianlubird @ddseapy I've created a POC PR that also capture pod metrics, conceptually allowing us to see how you resource you requested vs how much you actually used.

This is fixed in v2.7


Automated browser accessibility test suite in CircleCI

Depends on #7746. Addresses #4871 and #5271, by making Wagtail’s existing wagtail/tests suitable for UI integration tests. Compared to other approaches we’ve tried in the past, this has the immense advantage that the test suite is fully contained within the repository – so the tests can run in pull requests with little magic needed.
I chose Puppeteer for the browser automation, because it’s very popular and battle-tested, particularly on CircleCI and with Jest, which we use already.

Puppeteer has a Percy (from Browserstack) integration, if/when we want to do visual regression tests.
It also has good Axe integrations, which I’m making use of here.

This PR contains:

A baseline end-to-end browser integration test setup with Puppeteer & Jest
Enough configuration changes to the wagtail/tests suite to make it suitable for those browser tests in CI
CircleCI configuration to run the new test suite for all pull requests
Automated accessibility tests with Axe for a selection of Wagtail views
Basic documentation on how to get this test suite running.

Now updated with feedback from Fabien, and full documentation on how to run this locally.

@thibaudcolas  - #7746 is merged in, this will need to be rebased/conflicts resolved.

Thank you @lb-! All rebased and working.


feat: Adds support to IMF-fixdate format

References: IMF-fixdate Date/Time Formats

I would say rfc7231 would be a superset of IMF-fixdate as it should also support the obs-date format of the RFC.


There's not ValidateAll method

Envrioment
lang: go1.17
protoc-gen-validate: 0.6.1
protoc: 3.17.0
proto-gen-go: 1.3.2
Question
I generated xxx.pb.validate.to but there's no ValidateAll method in it. compile command is:
	protoc \
		-I. \
		-I ../../../thirdparty \
		--go_out=plugins=grpc:. \
		--validate_out=lang=go:. \
		api.proto

here is protobuffer file: https://github.com/yeqown/cassem/blob/main/internal/cassemdb/api/api.proto.
Is there any tip I missed?

As supplementary, third-party is a copy of validate/validate.proto and other google/protobuf/xxx.proto

I had the same issues with go1.17, to fix the issue I had to downgrade go to 1.16

@medgar-nitric Thanks for your reply,  I wonder you mean it works correctly with 1.16? And have you found the root cause of this issue?

Sorry, yes that is what i meant with Go version 1.16 the ValidateAll() functions are generated correctly, but are not present when using Go version 1.17.  I dont know what the root cause is for this.

This is fixed now with Go version 1.17.1  Not sure why.

This looks to not be working in Go 1.19.2


Is there table view paging support?

Is there table view paging support? Thanks.

Yeah, just noticed. Excitedly read too quickly through it looking for table view. Great, was looking for something like this.


Requirement for auto search option

I regularly use your Google extension for auto clicks, and I thought it was the best extension out there. Regarding this extension, I have one requirement.
No elemint finder exists. Currently, I'm doing search option manually, which takes time. If you could add these items, it would make everything very simple for me and completely automatic.
Requirement
When this page (https://myshopprime.com/manage-address)  opens, data can be copied from Excel and searched for using a website that I have already added in website. After clicking, you will move on to the next click. Take the second row of the Excel data for the following next entry, search, and click same repeat again
My Number:<PHONE_NUMBER>,<PHONE_NUMBER>
Please find the attached video which i need this auto setup.
https://github.com/Dhruv-Techapps/acf-docs/assets/144553043/03dcec1d-0f8b-4684-8f1a-0e2e3610fb4a

we have added option to fetch the element finder and value both from google sheets. checkout latest DEV version .


How to handle roads with curbs?

Discussed in https://github.com/spimort/TerraBrush/discussions/109

Originally posted by Flynsarmy May 29, 2024
One issue I've had with every terrain solution is difficulty in adding roads that cut into the terrain. Think a suburban neighbourhood that has roads with curbs. The road is cut about 10cm down into the terrain - it's the curb that's at roughly terrain height.

There are a few ways this can be handled:

Make the road at terrain height and slope the path beside the road up to give the illusion the road is cut into the terrain:

Disadvantage is that it doesn't look quite right.

Add the road splines above the terrain then manually paint the terrain height below the road to hide it. Disadvantage is that this process is manual and when you change terrain height, the road won't move with it.

Adding the road updates a splatmap that is sent to the terrain shader that automatically lowers the terrain. This is probably the correct solution but no idea how to do it.

Could we get some sort of road tool for this addon (or even a Roads addon that works alongside this tool) with this functionality? We've seen a million 'here is an empty field' terrains, but as it stands it's difficult to make any terrain set in the modern world.

Inspiration video form @raldor123 :
https://www.youtube.com/watch?v=jF6K3BkAa9M&t
Super interesting, I think it could work that way!


MRG: Fix minor bugs with Xdawn and create_ecg_epochs

Fixes:

bug with Xdawn where non-data-channels broke things
create_ecg_epochs where picks=None plus keep_ecg=False would not work.
minor PEP8 problem with mne/viz/misc.py
updates some tests to pytest (someday we will eliminate nose!)

update what's new?

done


PropTypes on Avatar saying imageUrl is required

While it's actually src as in docs :) But PropTypes helper in WebStorm is saying that imageUrl.
Also, adding all styled-system PropTypes to all components will be neat, so it will show up all shortcuts etc. Maybe a bit overkill, but it will save typing a lot. Also helping understand what props is possible to be passed.
So for Row which type is Flex it will be nice to get PropTypes of Flex too. Trying out props praying that they will work is kind of weird :)
Thanks.

I don't know anything about WebStorm but all the prop types should be defined for Rebass's hoc, grid-styled components, and any custom props on Rebass components. I suspect it's an issue with the tool you're using, since tracking prop types can be tricky. Feel free to reopen this issue if you notice React prop types warnings behaving incorrectly though


Update format and XML

I updated the format of the code to the latest rustfmt-nightly. I also upgraded the xml-rs dependency to 0.7 so that dependent crates can also update. This requires a minor version bump to 0.3.0 as per semver.

Coverage increased (+0.9%) to 81.304% when pulling 8e409dcbb102a2aefab747edc625dd4f81ac0a57 on Razican:update_fmt into a2b4fe269006a2414183a76a26cf12c3001a5a2a on gnieto:develop.


feat(compiler-core): avoid accidental side effects of event handlers

Close: #3651

If _ctx.fn can't be falsy, then remove the condition check will be fast;
If _ctx.fn could be falsy, then in the cacheHandlers: false edition, return fn(event, ...args); (in withModifiers) should change to return fn ? fn(event, ...args) : void 0; to support that. (Because compiled code is below:)
export function render(_ctx, _cache) {
  return (_openBlock(), _createBlock("div", {
    onClick: _withModifiers(_ctx.fn, ["self"])
  }, null, 8 /* PROPS */, ["onClick"]))
}

const withModifiers = (fn, modifiers) => {
      return (event, ...args) => {
          for (let i = 0; i < modifiers.length; i++) {
              const guard = modifierGuards[modifiers[i]];
              if (guard && guard(event, modifiers))
                  return;
          }
          return fn(event, ...args);
      };
  };

in the cacheHandlers: false edition, the falsy value means to remove the event handler, we cannot change this behavior, otherwise, it will be a breaking change. But we can easily make the code more robust, see the latest commit


gfa2rGFA.py caused KeyError: '1779060'

Hi
I failed to convert GFA (created by nf-core/pangenome) to rGFA with gfa2rGFA.py script from this project.
> cat panGraphViewer/panGraphViewerWeb/requirements.txt
Django==3.1.3
django-bootstrap4==22.1
requests==2.28.1
django-environ==0.9.0
djangorestframework==3.13.1
configparser==5.2.0
natsort==8.1.0
networkx==2.6.3
fontawesome-free==5.15.0
bokeh==2.2.3
dna_features_viewer==3.1.1
pysam==0.19.1
pandas==1.3.5
whitenoise==6.2.0
jinja2==3.0.0
numpy==1.21.6
biopython==1.79
matplotlib==3.5.2
sqlparse==0.4.2
tornado==6.2

> python panGraphViewer/panGraphViewerWeb/pangraphviewer/gfa2rGFA.py -in_gfa chnVSjapVSkorVSauVSusa.PanSN-1-19.fasta.gz.gfaffix.unchop.Ygs.view.gfa -out_rgfa chnVSjapVSkorVSauVSusa.PanSN-1-19.fasta.gz.gfaffix.unchop.Ygs.view.rgfa
2024-08-30 12:36:12,345 [INFO] The input file is in GFA1 format and we are converting it to rGFA. Please wait!
Traceback (most recent call last):
  File "/mnt/weka/scratch/waterhouse_team/gfa/panGraphViewer/panGraphViewerWeb/pangraphviewer/gfa2rGFA.py", line 241, in <module>
    run.convert()
  File "/mnt/weka/scratch/waterhouse_team/gfa/panGraphViewer/panGraphViewerWeb/pangraphviewer/gfa2rGFA.py", line 139, in convert
    S[newId] = {'seq':rev_comp(S[nodeId]['seq']),'len':S[nodeId]['len']}
KeyError: '1779060'

What did I miss?

Sorry for replying late. Based on the error messages, some nodeId used in path cannot be found. Please check if all nodeId can be found in "S-line".


Gstreamer package broken

[MIRROR] gstreamer1-1.12.2-2.gitdca812c.fc25.x86_64.rpm: Interrupted by header callback: Server reports Content-Length: 15667 but expected size is: 1265762
[FAILED] gstreamer1-1.12.2-2.gitdca812c.fc25.x86_64.rpm: No more mirrors to try - All mirrors were already tried without success

While trying to update my Fedora 25 install I ran into this error. Disabling UnitedRPMs solved my issue, so I assume that was the cause. I'm not sure what other information is useful here...

Hi; We need the next info...
rpm -q unitedrpms

dnf clean all && dnf -y update


Create prereqs.md

Creating an overall .NET Core pre-req native deps file to be able to point people to.
/cc @richlander @gkhanna79 @ellismg

@weshaggard PTAL as well.


luci-app-travelmate: generates wrong QR codes for WPA3 networks

Steps to reproduce:

go to: Network → Wireless
create a WPA3 SAE or WPA3 SAE / WPA2 PSK mixed network
go to: Services → Travelmate (luci-app-travelmate version git-22.232.72147-7971fe0)
Press the "AP QR-codes" button.
Generate a QR code for the newly created network
Scan it with an Android phone

Actual behavior:
"Check connection and try again" red message in the QR scanner (at least on a Poco X4 Pro 5G phone)
Expected behavior:
Phone should connect to the WiFi
Additional Information:
luci-app-travelmate inserts an invalid "T:" tag in the generated QR codes. It is set to "sae" or "sae-mixed", exactly as written in /etc/config/wireless, while the correct value is "WPA" according to the WPA3 specification (but this doesn't actually work) or "SAE" (the phone shares the WiFi credentials from another WPA3 network this way).
In other words, please map the "sae" or "sae-mixed" encryption types to "SAE" (in capital letters).

Not fixed. Even though "WPA" is the correct value per the spec, only "SAE" works with Poco X4 Pro 5G. The error is "Check connection and try again".
More precisely, WPA2 + WPA3 mixed mode works, but pure WPA3 doesn't.

Then your mobile phone seems to be ignoring official standards. I've tested this change successfully with my mobile phone (Android 12) and a 0815 china tablet (Android 10).

It's not only my phone. The same issue is present in the Google-provided AOSP sources. Here is a function that returns the string for the "T:" tag when one shares the network from the phone:
https://android.googlesource.com/platform/packages/apps/Settings/+/refs/heads/master/src/com/android/settings/wifi/dpp/WifiDppUtils.java#164
Copy-pasting:
    static String getSecurityString(WifiConfiguration config) {
        if (config.allowedKeyManagement.get(KeyMgmt.SAE)) {
            return WifiQrCode.SECURITY_SAE;
        }
        if (config.allowedKeyManagement.get(KeyMgmt.OWE)) {
            return WifiQrCode.SECURITY_NO_PASSWORD;
        }
        if (config.allowedKeyManagement.get(KeyMgmt.WPA_PSK) ||
                config.allowedKeyManagement.get(KeyMgmt.WPA2_PSK)) {
            return WifiQrCode.SECURITY_WPA_PSK;
        }
        return (config.wepKeys[0] == null) ?
                WifiQrCode.SECURITY_NO_PASSWORD : WifiQrCode.SECURITY_WEP;
    }

Where WifiQrCode.SECURITY_SAE is defined as "SAE" here: https://android.googlesource.com/platform/packages/apps/Settings/+/refs/heads/master/src/com/android/settings/wifi/dpp/WifiQrCode.java#70
My point is that the standard is worthless if it is not followed by Google itself.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/39691

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/76600

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/84469

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/94326

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/98037

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/98471

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/105756


Solve some sonar code smells

Pull Request Test Coverage Report for Build 2dbf47c4c59be439e3f704161f2f20b4acc2610f-PR-13

8 of 8 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.168%

Totals

Change from base Build fa0458e73f06f353e976f2f528bae73fa026c309:
0.0%

Covered Lines:
689

Relevant Lines:
775

💛  - Coveralls


product reviews

https://apps.shopify.com/product-reviews

The Shopify Product Reviews app does not have an API.
In this case we have two options, both of which will take a LOT of time.

Rewrite the entire site as a Shopify template.

Free!
Very time consuming.

Create our own review system.

Have to pay for a database, and server hosting.
Very time consuming.


Game crash.

Every time I try to open my world my game gets stuck in-between loading the spawn chunks and reading the world data, when I check the logs I see that my game crashed. I'm also using prism launcher
crash-2024-11-23_00.23.59-server.txt

hmm there is no hint of the cause in that log


Crash when run on IOS 10.3.3

It works well on iOS 11.3, but failed on 10.3.3 with logs:

Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'An instance 0x19be2e10 of class UIScrollViewPanGestureRecognizer was deallocated while key value observers were still registered with it. Current observation info: <NSKeyValueObservationInfo 0x19a8cef0> (
<NSKeyValueObservance 0x17f6c4d0: Observer: 0x17fa5550, Key path: state, Options: <New: NO, Old: NO, Prior: NO> Context: 0x0, Property: 0x17f60500>
<NSKeyValueObservance 0x19ab9180: Observer: 0x19a1d950, Key path: state, Options: <New: NO, Old: NO, Prior: NO> Context: 0x0, Property: 0x17f60500>
)'

I guess problem happen when you didn't remove observer in RefreshView.

@baohung02
Sorry for the late response, already fixed the issue in the latest version (v2.4.2), you can try again.
Thanks for your help.

Nice, thank you.

Hi, @WXGBridgeQ, I catch the same issue at ios 10.3.1 after update pod to 2.4.2.

@s-reshetnikov
Fixed in 2.4.3, please have a try with the new version.


HDDS-2182. Fix checkstyle violations introduced by HDDS-1738

/label ozone

@elek @adoroszlai Please review

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
80
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

-1
mvninstall
43
hadoop-hdds in trunk failed.

-1
mvninstall
29
hadoop-ozone in trunk failed.

-1
compile
18
hadoop-hdds in trunk failed.

-1
compile
13
hadoop-ozone in trunk failed.

+1
checkstyle
61
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
952
branch has no errors when building and testing our client artifacts.

-1
javadoc
18
hadoop-hdds in trunk failed.

-1
javadoc
16
hadoop-ozone in trunk failed.

0
spotbugs
1038
Used deprecated FindBugs config; considering switching to SpotBugs.

-1
findbugs
31
hadoop-hdds in trunk failed.

-1
findbugs
16
hadoop-ozone in trunk failed.

_ Patch Compile Tests _

-1
mvninstall
31
hadoop-hdds in the patch failed.

-1
mvninstall
26
hadoop-ozone in the patch failed.

-1
compile
21
hadoop-hdds in the patch failed.

-1
compile
15
hadoop-ozone in the patch failed.

-1
javac
21
hadoop-hdds in the patch failed.

-1
javac
15
hadoop-ozone in the patch failed.

+1
checkstyle
24
The patch passed checkstyle in hadoop-hdds

+1
checkstyle
26
hadoop-ozone: The patch generated 0 new + 0 unchanged - 6 fixed = 0 total (was 6)

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
793
patch has no errors when building and testing our client artifacts.

-1
javadoc
19
hadoop-hdds in the patch failed.

-1
javadoc
16
hadoop-ozone in the patch failed.

-1
findbugs
28
hadoop-hdds in the patch failed.

-1
findbugs
17
hadoop-ozone in the patch failed.

_ Other Tests _

-1
unit
25
hadoop-hdds in the patch failed.

-1
unit
20
hadoop-ozone in the patch failed.

+1
asflicense
31
The patch does not generate ASF License warnings.

2484

Subsystem
Report/Notes

Docker
Client=19.03.2 Server=19.03.2 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1529/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1529

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 7a86c91fa043 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 587a8ee

Default Java
1.8.0_222

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1529/1/artifact/out/branch-mvninstall-hadoop-hdds.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1529/1/artifact/out/branch-mvninstall-hadoop-ozone.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1529/1/artifact/out/branch-compile-hadoop-hdds.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1529/1/artifact/out/branch-compile-hadoop-ozone.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1529/1/artifact/out/branch-javadoc-hadoop-hdds.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1529/1/artifact/out/branch-javadoc-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1529/1/artifact/out/branch-findbugs-hadoop-hdds.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1529/1/artifact/out/branch-findbugs-hadoop-ozone.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1529/1/artifact/out/patch-mvninstall-hadoop-hdds.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1529/1/artifact/out/patch-mvninstall-hadoop-ozone.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1529/1/artifact/out/patch-compile-hadoop-hdds.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1529/1/artifact/out/patch-compile-hadoop-ozone.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1529/1/artifact/out/patch-compile-hadoop-hdds.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1529/1/artifact/out/patch-compile-hadoop-ozone.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1529/1/artifact/out/patch-javadoc-hadoop-hdds.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1529/1/artifact/out/patch-javadoc-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1529/1/artifact/out/patch-findbugs-hadoop-hdds.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1529/1/artifact/out/patch-findbugs-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1529/1/artifact/out/patch-unit-hadoop-hdds.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1529/1/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1529/1/testReport/

Max. process+thread count
305 (vs. ulimit of 5500)

modules
C: hadoop-ozone/ozone-manager U: hadoop-ozone/ozone-manager

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1529/1/console

versions
git=2.7.4 maven=3.3.9

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

/retest


How to check if block offsets have been calculated?

Sorry to keep on opening issues! Is there any way to check whether an IndexedBzip2File has had block offsets calculated yet or not? If it takes 8 hours to calculate them for my huge file, it's worth checking before running e.g. a seek(), and outputting a warning that this might take some time.

:) I'm glad someone uses it and cares enough to give feedback. Initially, this project only started to keep the required C++ bz2 code base for ratarmount separate from the python-only tar mount script. That's why the indexed_bzip2 interface is still fairly limited.
I see no harm in adding such a method. Will do.

Thanks. Incidentally, your code has sped up my workflow so that running my script (to parse Wikidata/Wikipedia files for https://www.onezoom.org) now takes under an hour with 64 processes, whereas it used to take 2 days. That's a huge difference, and makes my life so much easier. So I'm very grateful!

I added a size function. Note that it can throw an exception if the block offsets have not been completed yet.


add license and funding

Closes #7

Adding BSD-3-Clause License (in line with NEURON and CoreNEURON)
cc: @ASVG

cc: @alex4200


✨ Add support for find queries in locator fixture

[x] Add support for find* queries in locator fixture

[x] Rename SupportedQuery → SynchronousQuery
[x] Include find* queries in Queries type as (/* ... */) => Promise<Locator>
[x] Implement find queries per discussion starting here

[x] Use locator.first().waitFor()
[x] Throw proper error on timeout via get* query
[x] Wire up waitFor's to asyncUtilTimeout
[x] Incorporate waitFor's state option into our options and wire it up?

[x] Test coverage
[x] Does it make any sense to support hidden and detached just because waitFor supports them? https://playwright.dev/docs/api/class-locator#locator-wait-for

[x] Convert within to a fixture in order to pass asyncUtilTimeout properly — @sebinsua is this gonna be annoying/confusing?

~Refactors~ Merged in #489

Isolate 'standard' page (no timeout) in describe blocks
Use queries from Testing Library to enumerate queries (instead of internal hard-coded query name array, with the intention of removing all of the legacy ElementHandle implementation in a future major release)

This all looks good to me. I wrote some comments with my understanding of things!

I think this may be in a reasonable spot to release as another beta, assuming I can sort whatever's going on with Semantic Release. Worst case we switch to next 🙃 (or maybe alpha, heh)

Can you expose queriesFor when you publish a new version?


Depend on v0.1.0 of dfe-reference-data

Context
We were depending on main so potentially different environments could run different versions depending on when they pulled 🤪
Changes proposed in this pull request
Depend on freshly-tagged v0.1.0 — see https://github.com/DFE-Digital/dfe-reference-data/pull/11
Guidance to review
tbh I have no idea what the sha in the Gemfile.lock refers to. It's not in the repo either locally or in GitHub. The gem is still installed — bundle open works etc, and the local copy is at the same SHA as the tag. Probably of academic interest only... still, any ideas?
Things to check

[X] If the code removes any existing feature flags, a data migration has also been added to delete the entry from the database
[X] This code does not rely on migrations in the same Pull Request
[X] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[X] API release notes have been updated if necessary
[X] Required environment variables have been updated added to the Azure KeyVault

We were depending on main so potentially different environments could run different versions depending on when they pulled 🤪

I forgot about the revision hash in the lock file, so maybe currently it'd only get updated if you ran bundle update first? I'm not actually sure? 🤷♂

Nor am I @frankieroberto! Not intuitive to answer. This definitely better

cypress download failure, rerunning

I forgot about the revision hash in the lock file, so maybe currently it'd only get updated if you ran bundle update first? I'm not actually sure? 🤷♂
Yes exactly that.
Although I do agree that this is much better. 🚀


Uncatalogued sleep/1

I do not find sleep/1 here in the library(os) inventory listed:
http://tau-prolog.org/documentation#os
but a little URL engineering gives me:
http://tau-prolog.org/documentation/prolog/os/sleep/1

Maybe its uncatalogued because it doesn't work?
Can sleep/1 reliably be used in negation as failure?
I am asking because the JavaScript returns true.

Maybe its uncatalogued because it doesn't work?
Can sleep/1 reliably be used in negation as failure?
I am asking because the JavaScript returns true.
Ok so testing shows there is possibly no problem:
:- use_module(library(os)).
foo :- sleep(0).
bar :- fail.
baz :- \+ (foo, bar).

?- baz.
true.

Seems I am not used to the FFI protocol of Tau Prolog.

It is not listed because it previously belonged to a module that no longer exists. The predicate works fine, but you have to import the os module.

Yes, yes and yes...


Handle different environment cases for different builds

To handle cases where webpack produces a vendor, manifest etc. files which are required in
the production config but is not produced in the dev environment.
A primary example of this can be projects generated by Vue CLI.

@ranedk Raising this PR here since I feel this feature helps a lot.

I personally think such things should be put under an if clause inside the template. Pseudo code:
if is_production:
    load(manifest)
load(assets)

But if you really want the template tag, it could easily live in your django project. I don't think it's important enough to live in the core package. Closing but happy to hear your thoughts.


Update index.yml

correct prob of "?view=vs-2022" showing on card items, brought in from public

@jborsecnik : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@jborsecnik: I'm sorry - only the author of this article, @mikejo5000, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


Adds JavaDoc to stat methods in redis.clients.util.Pool (iss #1452)

LGTM too.

Done!., Thx for the contribution and sorry for taking too long to merge.


Custom prop-changed notifying event leaves host in un-flushed state

Separated from https://github.com/Polymer/polymer/issues/3912#issuecomment-246046934 as it's a different issue:
From @notwaldorf on August 2, 2016 21:43
me-ow.html
<link rel="import" href="../polymer/polymer.html">
<dom-module id="me-ow">
  <template>

value: [[value]]

  </template>

</dom-module>

index.html

  <link rel="import" href="me-ow.html">

<dom-bind>
  <template>
    <me-ow value="{{value}}" id="i"></me-ow>
    bind to value: {{value}}

    <button onclick="i.value='banana'">set value to "banana"</button>
  </template>
</dom-bind>

Resolved by https://github.com/Polymer/polymer/pull/3969


JuliaCon 2021: Symbolics.jl - fast and flexible symbolic programming

Video link: https://www.youtube.com/watch?v=Vkz4c-lDMU8
00:08 Introduction
00:21 Origin
00:48 Goals
01:23 Symbolics.jl tour
04:55 Expression trees
09:38 Rule-based rewriting
11:25 Symbolic Arrays
16:10 Symbolic Arrays: ArrayOp
23:33 Acknowledgements
23:50 More to see

Busy weekend! Appreciate the help here

Busy weekend! Appreciate the help here

Gotta take advantage of the free time when it comes around; not a common occurrence these days :)


cue imports within cue.mod pkg directory

What version of CUE are you using (cue version)?

cue version v0.6.0-alpha.2

go version go1.20.5
      -buildmode exe
       -compiler gc
     CGO_ENABLED 1
          GOARCH amd64
            GOOS darwin
         GOAMD64 v1

Does this issue reproduce with the latest stable release?
Yes
What did you do?

I have within the cue.mod/pkg/my.domain/x/... directories.
I have a mydef1 and mydef2 packages defined in there as parallel directories.
mydef2 imports mydef1 using import "my.domain/x/mydef1
when I cue vet from within the mydef2 directory, I get a 'cannot find package` error (same for cue def & export)
I also have a data directory outside of cue.mod
when i import mydef2, vet & cue commands works and mydef1 is correctly imported and works as expected

project_root
    cue.mod/pkg/my.domain/x/mydef1:
    cue.mod/pkg/my.domain/x/mydef2:
         import "my.domain/x/mydef1"
         > vet/def/export commands fail, cannot find mydef1
    data/myfile1:
        import "my.domain/x/mydef2"
        > vet/def/export commands work as expected

What did you expect to see?
vet/def/export working successfully within mydef2 directory for validating this schema.
What did you see instead?
import error, and still works successfully outside of cue.mod directory.

As it stands, the ability to vet within the packages is too important to me to give up, so even though it's working outside of here, I'm choosing to duplicate the def1 code in the packages over using the import until this is eventually resolved. Note that there a are dozens of small packages here, and this is just a trivial example to illustrate the concept.

I tried to write a reproducer for this and failed. This testscript succeeds, but by your description I think it should fail. Perhaps you could adapt it to show your issue?
exec cue export .
cmp stdout want-stdout.json
cd $WORK/cue.mod/pkg/my.domain/x/mydef1
exec cue vet .
cd $WORK/cue.mod/pkg/my.domain/x/mydef2
exec cue vet .

-- want-stdout.json --
{
    "z": 1
}
-- cue.mod/module.cue --
module: "example.com"
-- main.cue --
package main
import "my.domain/x/mydef2"
z: mydef2.y

-- cue.mod/pkg/my.domain/x/cue.mod/module.cue --
module: "my.domain/x"
-- cue.mod/pkg/my.domain/x/mydef1/d.cue --
package mydef1
x: 1
-- cue.mod/pkg/my.domain/x/mydef2/d.cue --
package mydef2

import "my.domain/x/mydef1"

y: mydef1.x

Also noting that cue vet my.domain/x/mydef1 and cue vet my.domain/x/mydef2 work from the root of that example. i.e. you do not need to change directories to vet those packages.

Grr hit Cmd+Enter instead of Enter:
exec cue export .
cmp stdout want-stdout.json
exec cue vet my.domain/x/mydef1
exec cue vet my.domain/x/mydef2

-- want-stdout.json --
{
    "z": 1
}
-- cue.mod/module.cue --
module: "example.com"
-- main.cue --
package main
import "my.domain/x/mydef2"
z: mydef2.y

-- cue.mod/pkg/my.domain/x/cue.mod/module.cue --
module: "my.domain/x"
-- cue.mod/pkg/my.domain/x/mydef1/d.cue --
package mydef1
x: 1
-- cue.mod/pkg/my.domain/x/mydef2/d.cue --
package mydef2

import "my.domain/x/mydef1"

y: mydef1.x

The above passes as expected.

Noting however the current bug with respect to /... wildcards show in https://github.com/cue-lang/cue/issues/2484.

This issue has been in a "cannot reproduce" state for eleven months now, so I think we should close it for the time being. I am more than happy to reopen it if @kghenderson responds to the questions above or with a specific reproducer, of course.


getSettings returns the wrong python interpreter when no interpreter is selected

#11084 added a call to the getSettings API to fetch the interpreter version for the resource. However, when no interpreter has been configured and the interpreter is auto-selected, this API appears to return the wrong interpreter. On @karthiknadig's machine, this is just the string "python" ends up using whatever's in PATH, but the interpreter selector has chosen something else entirely leading to problems like unresolved imports when the selected environment implies they exist.
cc @karrtikr

this API appears to return the wrong interpreter

What interpreter is it? It should be the auto-selected interpreter, which is what the extension will be using.
If no autoselected interpreter is present, we return the string 'python', when not in experiment.
If in experiment we return an empty string, meaning no interpreter is selected.

@karthiknadig can show you, but the bottom bar showed 3.8.0 in C:\Python38, while "python" in PATH was somewhere completely different, a different 3.8 install.

Showed it. It looks like on the master version it passes the correct path. Only in release branch it seems to path 'python'. For now I am going to assume this is not an issue anymore. Let us re-open this if we see it with insiders build.


Why is tls mandated for quic?

IMO there're use cases for non-tls situation, like in inner network ?

AFAIK "there is no way to use QUIC without TLS" (https://www.smashingmagazine.com/2021/08/http3-core-concepts-part1/)

There's a lot of value in having an ability to disable TLS, so that quic-go can work with other QUIC clients (e.g. msquic) supporting this feature.

No, there really is not. There's a lot of value in having an always-encrypted transport.
Also note that https://datatracker.ietf.org/doc/draft-banks-quic-disable-encryption/ never moved past a -00 version and has now been archived.

No, there really is not. There's a lot of value in having an always-encrypted transport.

One doesn't negate the other.  Having a Go QUIC client talking to a C QUIC client in an on-premices private network without encryption that has a stringent low-latency requirement is a valid use-case, and it's regretful not to be able to benchmark a Go QUIC application in that setting.

I disagree. Having an unencrypted code-path in an implementation that’s used over the public internet is a foot gun. This applies even more so since there isn’t even a standardized way to do so (just to be clear, quic-go wouldn’t implement such an extension, even if there was one, for the reasons outlined above). If you want to do local benchmarking, feel free to fork the library and implement an unencrypted mode.

There's no disagreement that using unencrypted mode on public internet is a strong no.  The feature I am after is to be able to use the quic-go in a fully private local network that contains latency-sensitive components written in C++ communicating through msquic.  We'd like to be able to use go.  Having to fork and maintain quic-go for that matter is a major inconvenience.


Random Error in Console

What is the output link of /viaversion dump?
https://gist.github.com/anonymous/12c2805faad6553afcebca36ee88884b
Are you using any additional software like BungeeCord? If so, what software and version? (Please list your plugins as well)
Plugins: http://prntscr.com/h060fk
How does this error happen? login? Using an item?
No idea if someone using an item, there is 170 players :/
Is there an error in the console? Use pastebin.com. Is there a kick message?
https://hastebin.com/afatetuqew.md

This error is caused by a client sending bad packets to the server, in the future we may offer to suppress pre-login packet errors but this may cause issues debugging login issues.


Add metrics tagging for vector functionality

Add tagging to the command_processor_process_seconds_count metrics to indicate whether calls include vector functionality (probably true/false makes the most sense).

There will be 2 tags added.

vector.enabled - This will suggest if vector storage is enabled for the collection.
search.type - This can have 3 values denoting what kind of document search was performed

VECTOR_SEARCH
VECTOR_SEARCH_WITH_FILTERS
OTHER


:req[headers] or :req[header] return "-"

morganFormat = ":date[iso] :remote-addr :remote-user :method :url :req[header] :http-version :referrer :user-agent"
app.use(morgan(morganFormat, {
immediate: true,
stream: logger
}))

Hi! Not dute what the question and/or issue is. Can you elaborate?

This is what I get in the log for this this format ":date[iso] :remote-addr :remote-user :method :url :req[header] :http-version :referrer :user-agent"
2017-11-07T21:50:57.010Z ::ffff:<IP_ADDRESS> - GET / - 1.0 https://www.domain.com/ Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36
Do you see req[header] return just dash "-"

Normally there is no property req.header so you get a dash. What does console.dir(req.header) print for that request?

Sorry, I'm on a phone and that didn't come out right. I mean normally there is no request header named header. What dkes console.dir(req.headers.header) print? Ade you sending the header "header" in your above request?

But in the doc: https://github.com/expressjs/morgan#reqheader

Right. It will shoe you the value of the header name you gave in the request. You put "header" as the name. If your request doesnt have the header named header, it will display a dash. Can you show all the request headers that are in your request?

I see. Doc is misleading I would say. Thanks

Doc improvements are definitely welcome! If you have a better way to word it, please feel free to make a pull request :+1:

Is there a way to display all the request headers? I suppose you would have to stringify them somehow or req.headers would just turn out like '[object Object]'

@jwerre adding your own token function like you did should do the trick! Then all you have to do is:
app.use(morgan(':request-headers'))


[language] introduce move-core-types and move Identifier into it

This crate will eventually contain all the types that are central to Move,
with the eventual goal being to release this on crates.io as a library for
others to consume.
Note that this library sits underneath libra-types (since the types here
are going to be independent of Libra).
Also start off the migration by moving the Identifier type over to this
crate.

LGTM. I'll give @dariorussi and others a bit more time to have a look, but will accept later this afternoon if no one does.

@bors-libra r=vgao1996

:pushpin: Commit 170f57f has been approved by vgao1996

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: vgao1996
Pushing a2bbf6d8bcdc650634b8ac99231ae1ce639fce0a to master...


Fix TODO directive out of bounds acccess

Summary
Fixes an out of bound access that I introduced https://github.com/astral-sh/ruff/pull/13640 where the old code was incorrect too, because it didn't handle joined comments correctly.
This PR fixes the out of bound access and adds a test for joined comments (# test # TODO: fixme).
Fixes https://github.com/astral-sh/ruff/issues/13755
Test Plan
See added tests

Hmm, what's up with our ecosystem checks. Let me re-run

Okay I don't know what's happening lol.

It's interesting that the number of additions in this PR is quite close to the number of removals in https://github.com/astral-sh/ruff/pull/13640#issuecomment-2395004667.

It's interesting that the number of additions in this PR is quite close to the number of removals in #13640 (comment).

Yes... the PR should not have removed any violations. I expect that it was panicking for all those repos, which is why there are so many changes. I ran the ecosystem check locally against the commit before I merged that PR and the result is:
zulip/zulip (+0 -7 violations, +0 -0 fixes)

ruff check --no-cache --exit-zero --ignore RUF9 --output-format concise --no-preview --select ALL

- zerver/actions/create_realm.py:239:11: FIX004 Line contains HACK, consider resolving the issue
- zerver/management/commands/list_realms.py:56:15: FIX004 Line contains HACK, consider resolving the issue
- zerver/tests/test_queue_worker.py:423:11: FIX004 Line contains HACK, consider resolving the issue
- zerver/tests/test_slack_importer.py:1244:15: FIX004 Line contains HACK, consider resolving the issue
- zerver/views/realm_icon.py:65:7: FIX004 Line contains HACK, consider resolving the issue
- zerver/views/realm_logo.py:68:7: FIX004 Line contains HACK, consider resolving the issue
- zilencer/management/commands/populate_db.py:109:7: FIX004 Line contains HACK, consider resolving the issue

Changes by rule (1 rules affected)

code
total
+ violation
- violation
+ fix
- fix

FIX004
7
0
7
0
0


Enabled option not respected for useInfiniteQuery

Describe the bug
The enabled option for useInfiniteQuery is not respected. When setting it to false the query still executes. This is necessary for dependent queries where the useInfiniteQuery instance must be called after another query resolves.
Your minimal, reproducible example
https://codesandbox.io/s/useinfinitequeryenabled-m576l?file=/pages/index.js
Steps to reproduce

Duplicated the codesandbox example for useInfiniteQuery
Added line 47 enabled: false,
Query still executes

Expected behavior
As the documentation says the "options for useInfiniteQuery are identical to the useQuery hook" which useQuery has the enabled option that should work for useInfiniteQuery as well.
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform

macOS 11.6.2
Chrome Version 97.0.4692.71 (Official Build) (x86_64)
Safari Version 15.2

react-query version
3.34.7
TypeScript version
No response
Additional context
No response

I seem to be running into this problem — did you find a fix? Was it fixed in a more recent version of react-query?

@ryb73 please provide a new sandbox, the one in this issue doesn't seem to work anymore. enabled generally works the same for infinite query and normal queries. They are both based on useBaseQuery, and the part that handles enabled is the same code for both ....

I can't be sure because I was only encountering the issue when in an intermediate development state and am not affected by it anymore, but I think my problem was that I was accidentally calling fetchNextPage, which seems to invoke the query even when enabled = false. So while it kind of doesn't make sense to ignore the enabled flag, it also doesn't really seem like a big issue to me, since developers shouldn't really be calling fetch if they don't want to immediately fetch.


Debug/test messages?

Wonder if someone could help me understand how I can test the transport by sending messages to rabbitMQ from the outside?
For example, if I have the following, what would I need in the payload to send a Seneca "cmd":
rabbitmqadmin publish exchange='seneca.topic' routing_key='role.demo' payload=?

@jofan This has been answered before. You can take a look at #28. Follow the thread: it has some advice on how to proceed to achieve what you want. If you need further assistance, write me back here.

@nfantone Thank you, I did see that message after my post. I haven't been able to send a message even with the output from inspecting seneca.act. I'll keep looking into it.

@jofan What exactly is it that you are struggling with? Maybe I can give you some pointers?


Ensure golangci-lint runs on all files

removed unused func params and imports
ignore revive dot-imports rule on ginkgo and gomega as dot import
there is the recommended practice
added missing error handling
various small style fixes found by the linter

I needed to rebase and fix a new lint failure from a recent commit on main.
pkg/octavia/images.go:245:2: unused-parameter: parameter 'log' seems to be unused, consider removing or renaming it as _ (revive)
	log *logr.Logger,
	^
level=info msg="File cache stats: 1 entries of total size 6.9KiB"


Support using credentials from multiple accounts against the LFS endpoint

Support credentials from multiple accounts when useHttpPath=true is set in the git config
Provide the URL path to 'git credential fill' for credential helpers that need the path to return the right credentials
Use the objects API URL for credentials so there is a stable path passed to the credential helper for caching

Ah, good call. I have a few questions though:
Will passing the path to the credential fill command (https://github.com/github/git-lfs/pull/554/files#diff-1eed123d34cdc2b60cc1a63521a9ca88R20) cause any problems for those of us without useHttpPath enabled? I don't think so, but I'll setup my laptop to use the osxkeychain helper instead of boxen's to see firsthand.
Do you by chance know what path git uses for pushes and pulls? We don't want end users to have to enter their password again for /{user}/{repo}.git/info/lfs/objects when they've already entered it for /{user}/{repo}.git.

I think this needs to strip the leading / from the path:
Downloading droidtocat.gif (24.65 KB)
trace git-lfs: run_command: 'git' config -l
trace git-lfs: run_command: 'git' config -l -f .git/config
Username for 'https://github.com//technoweenie/glowing-octo-lana.git/info/lfs/objects':

The Username prompt looks correct here:
echo "protocol=https\nhost=github.com\npath=technoweenie/glowing-octo-lana.git/info/lfs/objects" | git credential fill
Username for 'https://github.com/technoweenie/glowing-octo-lana.git/info/lfs/objects':

Added trimming the leading slash, so you get this now:
$ git clone https://github.com/technoweenie/glowing-octo-lana
Downloading droidtocat.gif (24.65 KB)
Username for 'https://github.com/technoweenie/glowing-octo-lana.git/info/lfs/objects'

Good idea on re-using the base remote URL, I'll work on that

Patch will now use the git remote's credentials if possible.
$ git clone https://github.com/technoweenie/glowing-octo-lana
Downloading droidtocat.gif (24.65 KB)
Password for<EMAIL_ADDRESS>
With this change, it seems to have started successfully picking up my credentials config for github.com from my gitconfig, which is great:
[credential "https://github.com"]
	username = clareliguori

This looks great. There are a couple more things:

The code to set the auth from the git remote is directly copied from earlier in the function. It could be extracted into a small, private helper function. I'll probably just make a small refactoring PR after merging this.
I'd really like new tests for this. Unfortunately, we don't have adequate credential tests at ALL. So I'll probably tackle this on my own.

This will likely make it into Git LFS v0.6.0, and a v0.5.5 if another bug fix release is necessary. Thanks for sending this patch!

Thanks again for the patch. I made a private helper and added some shell tests in #561.


Do you have plan to support for EntityFramework

Hi,
I have found a third party project MaikeBing.EntityFrameworkCore.LiteDB is a LiteDB provider for Entity Framework Core, it is on the development stage now, not for production yet.
I just want to ask, Do you have a roadmap for support EntityFramework?

Hi guys, at this moment I have no plans to support EntityFramework on LiteDB because there is no time for all. Maybe in future when has more people in this project :)

Hi, it is something that is planned? It would be very nice!

I think it would be very helpful if LiteDB gets support for the EntityFramework.

Any update on support for EntityFramework

Any update for this ?

Am also interested here it's been 3 years since this was first mentioned - any updates @mbdavid

any updates @mbdavid

Hi Team, Any updates on this?
Today I tried using 'OpenIddict' (https://documentation.openiddict.com/guides/index.html) which is an OpenID Connect & OAuth v2 provider like IdentityServer & Azure AD.
The issue is, It mainly only supports entity frameworks to store in a database.
And EF supports SQLServer, MySQL, etc...

I would like to use LiteDB there, But because we don't have a way I switched to SQLServer.
Is there any updates on this friends?

What do you think about that

Because of no support, I need to make unnecessary abstraction using Repository pattern, to let it work with LiteDB, PostgreSQL and mysql
Maybe any ideas of from what development can be started?

Pushing for support of this feature. My use case is that we use the EntityFramework provider for CosmoDB on production and wanted to use LiteDB as a provider on local development.


"Golang" Resources added

Closes #483
Description:
Golang Resources added.
Checklist:
Before submitting your pull request, ensure that you have completed the following tasks:

[ x ] I have carefully reviewed and adhered to the contributing guidelines before creating this pull request.
[ x ] I followed the prescribed PR title template. (Check this if you're adding a resource)

@jfmartinz The necessary changes have been done.

@jfmartinz Sorry for the misconception and kindly letting me correct my mistakes.Thank you for your co-operation.


Kernel smoothing and relative distribution for the power laws project

[x] Write the function for naive kernel density estimation
[x] Write the function for kernel estimation for nonnegative random variables using truncated normal density
[ ] Add comparison between relative density (referencing best-fit power distribution) and uniform distribution in the report

@FengshiNiu - can this issue be closed now?

Sure. All done! Pull request #199 has been merged


Examine transparency handling for hardware code generation

This issue has been logged for discussion purposes
Background

There is a code generation context setting on whether to consider "hardware transparency". By default this is set to false.
The user must explicitly determine when this should be set to be true.

As a convenience a "is transparent" heuristic utility traverses the shade tree at a given shader root and examines specific inputs and input values to determine if the shader is transparent.
There have be requests to enhance this to recognize more cases. (the inputs considered are currently fixed)

Depending on whether this option is set to true on not different code is generated.

Proposed Items To Examine:

Whether the code to support transparency should always be emitted to avoid re-generating code which can be costly.

If unique shaders are cached then 2 versions are required to support "transparent" and "opaque" variants, or the same shader may need to be regenerated + replaced on value changes.
A value change implies a shader regeneration requirement but there is no support for this mechanism of detection.

Whether the heuristic is too strict in checking for specific values to determine if a shade tree is (as opposed to could be transparent).
transmission is not included in the final color computation and instead relies on h/w alpha blending which is a "cheap" way to draw transparent objects.  This should be re-examined as this may not be a given.
Enhance heuristics to allow for additional inputs to be checked with custom logic. e.g. should transmission_color be checked for "unlit" shader.
do we still want to add support for a transparency "hint" attribute as proposed in the current 1.39 specification ? A suggestion from @niklasharrysson is that we move such a hint to <implementation>s as this has as it's main usage hardware rasterizers.
more?

Appendix:
Some examples of such as switch:

the PBR version of the surface constructor node here:
https://github.com/AcademySoftwareFoundation/MaterialX/blob/main/source/MaterialXGenGlsl/Nodes/SurfaceNodeGlsl.cpp#L201
when emitting the final alpha blending of the fragment result here:
https://github.com/AcademySoftwareFoundation/MaterialX/blob/main/source/MaterialXGenGlsl/GlslShaderGenerator.cpp#L643
for "unlit" shader support
https://github.com/AcademySoftwareFoundation/MaterialX/pull/860

Based on specification discussion, the h/w logic should be updated to follow this heuristic:
hint (string): A hint to help code generators understand how input may be used.  The following hints are currently defined:
"transparency": the input is indicating a level of shading transparency.
"opacity": the input is indicating a level of shading opacity (inverse of transparency)

which can be added to the nodedef as desired and parsed as part of the heuristic utility.
Adding a ping to @Gamache-autodesk for follow-up from previous discussion.

I like this. Can I dream about a hint named "isotropic" that would select between isotropic and anisotropic versions of dielectric/conductor/schlick nodes when roughness.x is detected to be equal to roughness.y? This would allow standard_surface to run without a tangent stream most of the time.

Think dreams should be sent to @dbsmythe  -- and best to raise this as a new "tangential" issue :)
The point about optimization based on "hint" is interesting but is counter to shader reuse as any value change means
a rebuild is required. This is a good point though as an value change for transparency could also require a rebuilt but this does
not currently occur.
So I would leave here an additional thought about adding an implementation level hint if a "value" change is a shader graph "topology" change.

Really good point! I am not currently integrating the isTransparent result into the shader hash used in the MayaUSD topologically-equivalent shader cache, which means a scene with a mix of transparent and opaque shaders is currently broken. Will open an issue.

Regarding @JGamache-autodesk 's thought about adding a hint for anisotropy, this is an interesting idea which I think the hint system might be able to accommodate, though not quite in the same way as transparency/opacity.  For transparency/opacity, the hint is placed on the  to say that this input actually indicates the level of transparency or opacity, as the interpretation of those inputs is (I think) pretty universal and uncontroversial.  For anisotropy, I think we could add a hint on whatever input is used to set the bitangent-direction roughness, but the hint's presence would merely indicate that there is a possibility for anisotropic reflections to occur, not necessarily that they are: this is because the input could either be specifying actual bitangential roughness, or it could be an anisotropic eccentricity amount depending on the implementation, and there isn't a standard interpretation of this value that I'm aware of.  But since the primary purpose of this hint would be simply to indicate whether or not separate tangent/bitangent streams must be maintained, I think we can leave the interpretation of the hint as basically just a boolean "there might be anisotropy here".  Not a perfect "there is anisotropy", but better than nothing.  And note that the polarity of the hint must be "anisotropic" and not "isotropic" at least on nodes with two roughness-like inputs, as I don't think you could give a hint of "isotropic" and know that there couldn't possibly be anisotropy: since the hint lives in the nodedef, it can't be added only in certain situations known to be isotropic.  For shader nodes with only a single roughness value, the absence of an "anisotropic" hint would be sufficient to indicate no anisotropy can occur.
One possible downside of this is that if an implementation now depends on the presence of this (new) hint to enable anisotropic reflections, then any legacy nodes without the hint in their nodedef would suddenly break.

Thanks for this original report, @kwokcb, and let's close this out in light of your work on shader generation hints in https://github.com/AcademySoftwareFoundation/MaterialX/pull/1954.


Running on Mac

After connecting to camera WIFI (QX10)
Korr:sony_camera_api Mac$ python src/example/pygameLiveView.py
Traceback (most recent call last):
File "src/example/pygameLiveView.py", line 90, in
cameras =  search.discover()
File "build/bdist.macosx-10.9-intel/egg/pysony.py", line 46, in discover
socket.error: [Errno 51] Network is unreachable

I have a similar issue, running on python 2.7.10, MacOS 10.11.6, direct WiFi connection to QX10:
python scan_for_cameras.py
Traceback (most recent call last):
File "scan_for_cameras.py", line 6, in
cameras =  search.discover(5)
File "/usr/local/lib/python2.7/site-packages/pysony.py", line 38, in discover
self.__udp_socket.sendto(msg, (SSDP_ADDR, SSDP_PORT))
socket.error: [Errno 51] Network is unreachable
The examples for sony_live and timer_photo work well. Any suggestions on how to fix this discovery issue on Mac?

@hblanken is right. I tested several times but SSDP discovery is not working well. so after connect the camera WIFI and run the sony_live or timer_photo. and if you success to connect to camera. you can skip the discover part on pygameLiveView example.


Highlighting missing from vi / nano etc

Hi - recently moved over to zsh, installed ohmyzsh and wanted to add the highlighting plugin.
Followed the install instructions and the plugin seems to be installed, recognised and listed in the omz plugin list. Highlighting works on the prompt but not inside any editors i have (vi, nano etc).

Any suggestions at to where to look would be great.
Thanks

z-sy-h only highlights input at zsh's prompt.  It does not interact with your $EDITOR in any way.  You'll want to look in your $EDITOR's documentation for how to enable syntax highlighting.  Good luck!


Script uses deprecated /usr/bin/wish on macOS instead of the one in PATH

On macOS an ancient, and now deprecated tcl-tk is supplied by the system. It is recommended to use the homebrew version.
Using #!/usr/bin/env wish fixes this.

Changed the script to use #!/usr/bin/env wish instead.


[stable/prometheus-operator] Add namespace information to the TargetDown alert

Is this a request for help?: no

Is this a BUG REPORT or FEATURE REQUEST? (choose one): FEATURE REQUEST

The TargetDown alert does not list the namespace and therefore:

the alert message does not provide the necessary context - one needs to guess the namespace
the alert cannot be further filtered out based on the namespace

https://github.com/helm/charts/blob/f6974d6307f964267df39cf1a77daf8e075082f5/stable/prometheus-operator/templates/prometheus/rules/general.rules.yaml#L23-L26
Version of Helm and Kubernetes:
helm-2.8.1
k8s-1.10.6
Which chart:
stable/prometheus-operator
What happened:
What you expected to happen:
If possible, more context of the alert should be provided in the alert.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:

Alerts are sourced from upstream repositories, originating with the kubernetes-mixin project. You're free to customize alerts in whatever way you wish, but if you would like to change the defaults, please ask in the source project


Permission error when installing assistant that has the same intents as a previously installed assistant

I previously installed a French assistant that has intents for weather. When trying to install a English assistant that has the same intents, I get the following error :
(env) pi@raspi:~ $ snipsmanager install
Running Snips Manager installer
❯ Fetching assistant
✔ Fetching assistant proj_YmY4rZ9k1AN from the Snips Console
✔ Using cached version: /home/pi/.snips/assistant_proj_YmY4rZ9k1AN.zip
❯ Loading assistant
✔ Loading assistant from file /home/pi/.snips/assistant.zip
⋯ Generating classes from assistant model
↯ [Errno 13] Permission denied: '/home/pi/.snips/intents/intents/search_weather_forecast_intent.py'
❯ Installing skills
⋯ Installing skill: /home/pi/snips-skill-owm
^C

Have you tried sudo snipsmanager install?

Closing this


Sort index releases by semver

Aims to get the right versions for e2e WIP and current builds, sorting by date doesn't get the more recent versions of each kind.

Updated to use the new IndexRelease sorter from versionbundle giantswarm/versionbundle#52 thx @tuommaki! Merging.


Hello teacher! After verifying that still missing items 1 and 2 in this iteration not solved it

Hello teacher!
After verifying that still missing items 1 and 2 in this iteration not solved it
Um! Teacher, your idea is great! Great! But I don’t know if your idea can solve this problem: [https://github.com//issues/134326], if it can be solved directly in the next milestone, then thank you very much, teacher, You are really very, very great, very, very awesome 👍👍👍😜!
It may be that what I described earlier is not clear enough or detailed enough. . . Here again, the detailed explanation is as follows: Hello, teacher! It is recommended that the font foreground color of the widget needs to be changed. I used red numbers and green arrows to make detailed marking instructions. I also used the green box to mark the range of the font foreground color that needs to be changed. Please see the picture below:

Hello, teacher!
If you confirm my needs, please reply, thank you very much!
https://github.com/microsoft/vscode/issues/134326

Doesn't https://github.com/microsoft/vscode/issues/134326#issuecomment-933315205 work for you?

Doesn't #134326 (comment) work for you?

Dear Teacher!
Hello!
https://github.com/microsoft/vscode/issues/134326
I just solved the foreground color of the area marked with number 3, but I did not solve the foreground color of the area marked with red numbers and yellow oval background color and the area marked with number 1 and number 2 with green boxes. Thank you very much for your help!😜

Hello, teacher!
The new year has come, I wish the teachers a happy new year! ! !
In the new year, I hope that the teacher can help solve this problem in time, thank you very much!👍👍👍👍👍👍😜😜

Hello, teacher!
VSCode is a great project that gives users the greatest autonomy from the very beginning, allowing users to personalize configurations according to their own habits, so it can fully surpass the long-born jetbrion series in just 5 years. The most important reason is that VSCode's open source thinking and allowing users to customize and configure VSCode development methods to the greatest extent can achieve today's achievements. I hope VSCode can continue to develop this way of thinking and development, focusing on every reasonable request of users and need. Thank you here!
vscode contributors
20220126

Doesn't #134326 (comment) work for you?

Hello, teacher!
VSCode is a great project that gives users the greatest autonomy from the very beginning, allowing users to personalize configurations according to their own habits, so it can fully surpass the long-born jetbrion series in just 5 years. The most important reason is that VSCode's open source thinking and allowing users to customize and configure VSCode development methods to the greatest extent can achieve today's achievements. I hope VSCode can continue to develop this way of thinking and development, focusing on every reasonable request of users and need. Thank you here!
vscode contributors
20220126


addOrderNote | Not possible to set iduser

There is no possibility to set the iduser of the notification. So it's getting self assigned to the first id right now.

It's not possible at the moment to change the user who added the note. Your observation is correct :) We don't have a fix for this planned at the moment.


How to forward UDP?

Thanks for your efforts.
Now I want to support forwarding UDP.
What time will you support UDP?
If you don't have time to support UDP soon, please guide me(documents or any relate technical) to support forwarding UDP.

Hi, I havent implemented a small part. All you would need to do is take the forwarded udp packets and send them to the socks5 server. I believe that the udp packets are already being captured.
I may come back to this project in a month or so and fix the bugs.

Thanks for your answer.
I'm trying to request UDP associate. But when I send VER CMD RSV ATYP DST.ADDR DST.PORT to establish a connection to send UDP packets, Socks server didn't send me a response and then I can't read BND.ADDR and BND.PORT to perform to connect DatagramSocket.
Here is my code
`           DatagramSocket clientSocket = new DatagramSocket();
byte[] response = new byte[256];
InetSocketAddress destination = new InetSocketAddress("<IP_ADDRESS>", 1080); //EDIT THIS WITH THE IP AND PORT OF THE PROXY
        Socket socketProxy = new Socket();
        socketProxy.bind(new InetSocketAddress(0));
        service.protect(socketProxy);
        socketProxy.setSoTimeout(5000);
        socketProxy.connect(destination, 5000);

        DataOutputStream writer = new DataOutputStream(new BufferedOutputStream(socketProxy.getOutputStream()));
        DataInputStream reader = new DataInputStream(new BufferedInputStream(socketProxy.getInputStream()));

        // connect/authorization request
        writer.writeByte(0x05); // VER
        writer.writeByte(0x01); // NMETHODS
        writer.writeByte(0x00); // METHODS
        writer.flush();

        // connect/authorization response
        reader.read(response); // RESPONSE IS: 5 0

        // udp associate request
        writer.writeByte(0x05); // VER
        writer.writeByte(0x03); // CMD - UDP ASSOCIATE
        writer.writeByte(0x00); // RSV
        writer.writeByte(0x01); // ATYP
        // is what I'm sending here as DST.ADDR & DST.PORT okay?
        writer.write(clientSocket.getLocalAddress().getAddress()); // DST.ADDR
        writer.writeShort(clientSocket.getLocalPort()); // DST.PORT
        writer.flush();

        // udp associate response
        Log.d(TAG, "udp associate response");
        reader.skipBytes(4); // skip VER, REP, RSV, ATYP bytes
        int relayAddress = reader.readInt();
        InetAddress relayInetAddress = InetAddress.getByAddress(ByteBuffer.allocate(4).putInt(relayAddress).array());
        int relayPort = reader.readUnsignedShort(); // server returns some random port

        // connect to relay server via datagramsocket
        clientSocket.connect(relayInetAddress, relayPort);`

Please help me, I spent a lot of time, but I can't find the cause.

Hey, sorry for the late reply, the last couple months have been busy. Have you resolved this issue?

Hey, sorry for the late reply, the last couple months have been busy. Have you resolved this issue?

Hi, I'm so sorry for the late response. I changed to use another solution for this and don't use your lib.


Storage and Auth headers incorrect?

Describe the bug
I have created a SupabaseCacheManager to use in CachedNetworkImage that is not working anymore with supabase_flutter 1.10.23
class SupabaseCacheManager extends CacheManager with ImageCacheManager {
  SupabaseCacheManager({
    required SupabaseClient supabaseClient,
  }) : super(
          Config(
            key,
            stalePeriod: const Duration(days: 7),
            repo: JsonCacheInfoRepository(databaseName: key),
            maxNrOfCacheObjects: 1000,
            fileService: SupabaseFileService(
              supabaseClient: supabaseClient,
            ),
          ),
        );

  static const key = 'supabaseCache';
}

class SupabaseFileService extends HttpFileService {
  SupabaseFileService({
    required SupabaseClient supabaseClient,
  }) : _supabaseClient = supabaseClient;
  final SupabaseClient _supabaseClient;

  @override
  Future<FileServiceResponse> get(
    String url, {
    Map<String, String>? headers,
  }) async {
    const renderPath = 'object';
    final storageUrl = _supabaseClient.storage.url;
    final fetchUrl = Uri.parse('$storageUrl/$renderPath/$url');
    final response = await super.get(
      fetchUrl.toString(),
      headers: _supabaseClient.storage.headers,
    );

    return response;
  }
}

And using it like this
CachedNetworkImage(
                imageUrl: state.avatarPath,
                width: radius * 2,
                height: radius * 2,
                fit: BoxFit.fill,
                placeholder: (context, url) {
                  return const SizedBox.square(
                    dimension: 16,
                    child: Center(
                      child: CircularProgressIndicator(
                        strokeWidth: 1,
                      ),
                    ),
                  );
                },
                errorWidget: (context, url, error) {
                  return const Icon(
                    Icons.error,
                    size: 24,
                  );
                },
                cacheManager: context.read<SupabaseCacheManager>(),
              ),

This worked fine in supabase_flutter 1.9.0
In 1.10.23 this doesn't work anymore.
By placing breakpoint right before final response = await super.get, I saw the first issue: supabaseClient.storage.headers now have a map with only one record which is the x-client-info, previously this had all the needed headers.
I tried using the supabase.auth.headers, but it turned out apikey and jwt token are the same, which is incorrect.
Eventually when I change it to use the token from supabaseClient.auth.currentSession?.accessToken and the key from supabaseClient.supabaseKey and it worked.
To Reproduce
Steps to reproduce the behavior:
Place breakpoints in any request you are making to Supabase and inspect the supabaseClient.storage and supabaseClient.auth headers
Expected behavior
I would expect
a. storage and auth headers to be the same
b. to have correct records in the map for the Authorization and apikey headers
c. apikey and jwt token are different things I'm not sure how this thing got messed up.
Version (please complete the following information):
On Windows
supabase_flutter 1.10.23
supabase 1.11.10
functions_client 1.3.2
gotrue 1.12.5
postgrest 1.5.2
realtime_client 1.4.0
storage_client 1.5.4
Additional information
By inspecting all of the SupabaseClient features,
functions headers are just these 2
"Content-Type" -> "application/json"
"X-Client-Info" -> "supabase-flutter/1.10.23"

rest has only "X-Client-Info" -> "supabase-flutter/1.10.23"
storage has only "X-Client-Info" -> "supabase-flutter/1.10.23"
realtime has only "X-Client-Info" -> "supabase-flutter/1.10.23", but it also has accessToken property which has a correct value

I hope this won't be closed due to inactivity. That's why I'm leaving this comment here - to prevent closure without resolving.

@talamaska
Supabase provides methods for retrieving URLs to retrieve URLs for the image, but is there a reason why you are not using them?
You shouldn't need to create your own CacheManager class at all, and you can just pass the image URL to CachedNetworkImage widget directly.
For public bucket: https://supabase.com/docs/reference/dart/storage-from-getpublicurl
For private bucket: https://supabase.com/docs/reference/dart/storage-from-createsignedurl

I don't think createSignedUrl cares about any policies I have set. I need the policies to be taken into account. Even if I start using it, I don't want to make the calls prematurely, so I will still need to implement custom url resolver in the cache manager. I have seen issues when these signed urls expire in the worst moment, in different projects, but still aws based. Plus having 2 cashing layers is a problem waiting to happen.

@talamaska

I don't think createSignedUrl cares about any policies I have set.

Just to make sure you understand how Supabase storage and RLS works, only those users that are allowed to select the files in a private bucket can create signed URLs and that is when the RLS takes effect. Once a signed URL is issued, the file will be accessible by anyone with the URL until the expiry time comes, and RLS does nothing there. So you have to design your system in a way that only those that should be able to access the file can obtain the signed URLs.
Knowing this behavior, a better caching strategy might be to use the image path as the cache key and call the createSignedUrl whenever the cache expires.

Eventually when I change it to use the token from supabaseClient.auth.currentSession?.accessToken and the key from supabaseClient.supabaseKey and it worked.

Also, it sounds like you did find a work around for this issue.
The current behavior was introduced to guarantee fresh auth tokens when making request to Supabase, and since there is a work around for it, I'm going to close this issue.

Once a signed URL is issued, the file will be accessible by anyone with the URL until the expiry time comes, and RLS does nothing there.

This is exactly my concern.

@talamaska
That's why typically for accessing files in private buckets, you set the token expiration time to something very short so that you can just download the file and be done with it.

Ok, you convinced me :)

Ok, well I researched how this can be done with CachedNetworkImage, with or without a CustomCacheManager. There is no way to for me pass the bucket and/or the expiration for a CustomCacheManager. A the fileService is initialized once, and the get method is called somewhere internally in the CachedNetworkImage. Without the cache manage I can only wrap the whole thing with a FutureProvider, which doesn't help at all, cause it will request a new signed url on every build, instead of just when the cache of the CacheManager.


ContainerExactly impls for Rc and Arc are unsound

In the ContainerExactly<T> impls for Rc<C> and Arc<C> (where C: ContainerExactly<T>), the write() and drop_before() functions create an exclusive &mut C::Uninit reference from a &mut Rc<impl ContainerExactly<T>> or &mut Arc<impl ContainerExactly<T>>, with the safety comment that "We're the only owners of the uninit data at this point". However, this is not necessarily true in the case of an adversarial C type, which can hold another reference to itself. To illustrate, this program produces an error in Miri:
/*
[dependencies]
chumsky = "=1.0.0-alpha.6"
*/

#![forbid(unsafe_op_in_unsafe_fn)]
use chumsky::container::ContainerExactly;
use std::{
    cell::UnsafeCell,
    rc::{Rc, Weak},
};

struct Evil(Weak<UnsafeCell<Self>>);

// SAFETY: `Evil` can be soundly reinterpreted as itself.
unsafe impl ContainerExactly<()> for Evil {
    const LEN: usize = 2;
    type Uninit = Evil;

    fn uninit() -> Self::Uninit {
        unimplemented!()
    }

    fn write(uninit: &mut Self::Uninit, i: usize, _: ()) {
        if i == 0 {
            let mut rc = uninit.0.upgrade().unwrap();
            Rc::<Self>::write(&mut rc, 1, ());
        }
    }

    unsafe fn drop_before(_uninit: &mut Self::Uninit, _i: usize) {}

    unsafe fn take(uninit: Self::Uninit) -> Self {
        uninit
    }
}

fn main() {
    let mut evil = Rc::new_cyclic(|weak| UnsafeCell::new(Evil(weak.clone())));
    Rc::<Evil>::write(&mut evil, 0, ());
}

error: Undefined Behavior: not granting access to tag <1942> because that would remove [Unique for <1836>] which is strongly protected because it is an argument of call 805
   --> /home/lm978/.cargo/registry/src/index.crates.io-6f17d22bba15001f/chumsky-1.0.0-alpha.6/src/container.rs:231:27
    |
231 |         C::write(unsafe { &mut *uninit.get() }, i, item)
    |                           ^^^^^^^^^^^^^^^^^^ not granting access to tag <1942> because that would remove [Unique for <1836>] which is strongly protected because it is an argument of call 805
    |
    = help: this indicates a potential bug in the program: it performed an invalid operation, but the Stacked Borrows rules it violated are still experimental
    = help: see https://github.com/rust-lang/unsafe-code-guidelines/blob/master/wip/stacked-borrows.md for further information
help: <1942> was created by a SharedReadWrite retag at offsets [0x10..0x18]
   --> src/main.rs:27:13
    |
27  |             Rc::<Self>::write(&mut rc, 1, ());
    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
help: <1836> is this argument
   --> src/main.rs:24:14
    |
24  |     fn write(uninit: &mut Self::Uninit, i: usize, _: ()) {
    |              ^^^^^^
    = note: BACKTRACE (of the first span):
    = note: inside `<std::rc::Rc<Evil> as chumsky::container::ContainerExactly<()>>::write` at /home/lm978/.cargo/registry/src/index.crates.io-6f17d22bba15001f/chumsky-1.0.0-alpha.6/src/container.rs:231:27: 231:45
note: inside `<Evil as chumsky::container::ContainerExactly<()>>::write`
   --> src/main.rs:27:13
    |
27  |             Rc::<Self>::write(&mut rc, 1, ());
    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    = note: inside `<std::rc::Rc<Evil> as chumsky::container::ContainerExactly<()>>::write` at /home/lm978/.cargo/registry/src/index.crates.io-6f17d22bba15001f/chumsky-1.0.0-alpha.6/src/container.rs:231:9: 231:57
note: inside `main`
   --> src/main.rs:40:5
    |
40  |     Rc::<Evil>::write(&mut evil, 0, ());
    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace

One fix would be to create a pub struct UniqueRc<T>(Rc<T>); wrapper type that can't be cloned, then set type Uninit = UniqueRc<UnsafeCell<C::Uninit>>; on the ContainerExactly<T> impl. (Ditto for Arc<T>.)

Argh, you're right. For the time being, I think the best approach is probably to remove the impls for Arc and Rc (I don't think they're frequently used anyway, thankfully). Thanks for pointing this out!

I've removed these impls in dce5918b. Thanks again.


Feature: ACD - switch back end to use web scraping instead of the API.

As the title says - how viable would it be to switch the ACD back end to use web scraping instead of the API interface?

I imagine it requires a lot of work, never mind the complications and errors that will it cause.

This might be possible, but I don't really want to do it as I'm sure it would end up with rclone being in trouble with Amazon again!

I'm going to close this ticket now as I don't think this is a good direction for rclone to go in.


Add tutorial for simple e-commerce dApp with confidential payment

I'm going to close this issue to clean up the tracker. Please reopen if needed.

I went through the PR and most of the diff are compiled contracts ABIs and React leftovers which probably shouldn't be in git anyway? Let's stick to smaller, confidential-specific examples, stress out important details you need to be aware of when building Sapphire dapps and provide boilerplate code, if needed.


Add eslint

✨ Wonderful Project! Thought i could lend a hand and add eslint for you. The configuration I'm using is based on one I'm using in my own TypeScript package development project: Matterhorn. Going to push a second commit that adds rules to fit the current project structure. Furthermore, I set the ecmaVersion based on what you have in the tsconfig.json file. Let me know if you have any questions!

Looks like there may be a conflict with prettier. I'll defer to your review on what modifications I should make. I believe there is a plugin to merge prettier with eslint I just haven't used it in a while

Do a reinstall with yarn for me.

and push

We've been a little lazy to move off of TSLint on our team. I guess we should bite the bullet and update palmerhq/typerscript.

This PR actually inspired me to dive head first and write up a detailed article on TypeScript + ESLint. You can check out the unpublished version here. It is nearly done just waiting on one more peer to review it. In the article I detail how to set it up with prettier too. I'm going to push some changes to this PR soon with an ESLint & Prettier integration (also outlined in the article).

Okay updated and fixed up some of the rules. Pretty close to passing. Here is the current output of yarn lint
👻 tsdx (add-eslint)▷ yarn lint
yarn run v1.15.2
$ eslint src/**/*.ts

/Users/ethanarrowood/Documents/GitHub/tsdx/src/createJestConfig.ts
  1:8  warning  'fs' is defined but never used    @typescript-eslint/no-unused-vars
  2:8  warning  'path' is defined but never used  @typescript-eslint/no-unused-vars

/Users/ethanarrowood/Documents/GitHub/tsdx/src/createRollupConfig.ts
  2:1  error  'ge' is not defined  no-undef

/Users/ethanarrowood/Documents/GitHub/tsdx/src/index.ts
   25:13  error    Require statement not part of import statement  @typescript-eslint/no-var-requires
   26:22  error    Require statement not part of import statement  @typescript-eslint/no-var-requires
   38:10  warning  Unexpected any. Specify a different type        @typescript-eslint/no-explicit-any
   42:13  warning  Empty block statement                           no-empty
   60:1   error    Expected indentation of 6 spaces but found 4    @typescript-eslint/indent
   61:1   error    Expected indentation of 6 spaces but found 4    @typescript-eslint/indent
   67:15  warning  Unexpected any. Specify a different type        @typescript-eslint/no-explicit-any
   68:13  warning  Unexpected any. Specify a different type        @typescript-eslint/no-explicit-any
   81:35  warning  Unexpected any. Specify a different type        @typescript-eslint/no-explicit-any
  105:15  warning  Empty block statement                           no-empty
  225:7   warning  Unexpected console statement                    no-console
  244:24  warning  Unexpected any. Specify a different type        @typescript-eslint/no-explicit-any
  257:1   error    Expected indentation of 4 spaces but found 10   @typescript-eslint/indent
  258:1   error    Expected indentation of 2 spaces but found 8    @typescript-eslint/indent
  261:1   error    Expected indentation of 4 spaces but found 10   @typescript-eslint/indent
  262:1   error    Expected indentation of 2 spaces but found 8    @typescript-eslint/indent
  291:9   warning  Unexpected console statement                    no-console
  296:26  warning  Empty block statement                           no-empty
  312:24  warning  Unexpected any. Specify a different type        @typescript-eslint/no-explicit-any
  327:1   error    Expected indentation of 4 spaces but found 10   @typescript-eslint/indent
  328:1   error    Expected indentation of 2 spaces but found 8    @typescript-eslint/indent
  331:1   error    Expected indentation of 4 spaces but found 10   @typescript-eslint/indent
  332:1   error    Expected indentation of 2 spaces but found 8    @typescript-eslint/indent
  353:20  warning  Unexpected any. Specify a different type        @typescript-eslint/no-explicit-any

/Users/ethanarrowood/Documents/GitHub/tsdx/src/logError.ts
  3:16  warning  Unexpected console statement              no-console
  5:39  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

/Users/ethanarrowood/Documents/GitHub/tsdx/src/output.ts
   7:3  warning  Unexpected console statement  no-console
  15:3  warning  Unexpected console statement  no-console
  19:3  warning  Unexpected console statement  no-console

✖ 32 problems (13 errors, 19 warnings)
  10 errors and 0 warnings potentially fixable with the `--fix` option.

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Configuring eslint with TypeScript isn't easy.  What if tsdx had a lint command as well? https://github.com/palmerhq/tsdx/pull/99
And it used tsdx lint to lint its own source code.

See #99