Comment to keep API preview headers around

What type of PR is this?
documentation
What this PR does / why we need it:
API preview headers (media types) are used to enable new features in GitHub API.
These media types will be added to the API request as headers and used to enable particular features on GitHub API that are still in preview.
After some time, specific media types will be promoted (to a "stable" state).
From then on, the preview headers are not required anymore to activate the additional feature on GitHub.com's API. However, this API header might still be needed for users to run a GitHub Enterprise Server on-premise.
It's not uncommon for GitHub Enterprise Server customers to run older versions which would probably rely on the preview headers for some time.
While the header promotion is going out for GitHub.com, it may be some time before it even arrives in GitHub Enterprise Server.
We keep those preview headers around to avoid breaking older GitHub Enterprise Server versions. Additionally, an non-functional (preview) header doesn't create any side effects on GitHub Cloud version.
See https://github.com/google/go-github/pull/2125 for full context.
Special notes for your reviewer:
This Pull Request was triggered out of a discussion from https://github.com/google/go-github/pull/2125
Explicit comment
Personally, I prefer and see value in extensive comments that tell the story and the full context next to the code (like in this PR).
I can understand when this interrupts the code reading flow for others.
I do think that the added advantage (by the additional context) is bigger.
Please let me know what you think about it and if any change is required.
Additional documentation, usage docs, etc.:

https://github.com/google/go-github/pull/2125

Thanks for the quick review @gmlewis.
I added your changes.


webui: add read/write for all editors

1. Tell us something about your changes.
as the title said .. add read/write for all editors in webui.
Now you we can write all values (except log and webui - I decided that are 'nerd' settings and they can only be set in config manually)
when trying out, please backup your config before!!! (just some precautions ... )
2. If this changes affect the .conf file. Please provide the changed section
no
3. Reference an issue (optional)
Note: For further discussions use our forum: forum.hyperion-project.org

... a side note layout and beautiful eye candy wasn't the goal of this PR - just the basics of loading and writing the config

Nice! But how about a "nerd"-Mode on webui?

of course, but  the json editor needs some extension.
I want something like "settings level". Then we can add a settings level in json schema and set the level on editor ....

and a title catcher(compare) for translations? the only idea i have how we could integrate them?


Babel and csscomb

Please add  icons for the extension '.babelrc' and '.csscomb.json'.

I'll see to it. There might be some time before the next version is released though

It’s all good :eyes:
Thank you for quick response!


CLOUD-53287 fixed start services

@keyki

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/2165/


Integrate FUSE based open source cloud drive software.

What feature or improvement do you think would benefit Files?
Add a semi-package manager to install open source FUSE clients for cloud (mainly), network, etc drives without having to install the official manufacturers program, which will start to slow down the computer. Additionally, it will include GUI for the setup process. The external FUSE mount software should not run in the background unless the user is actively using a cloud drive. rClone should be the first and foremost one. All FUSE clients should be prebuilt as an EXE and portable, and only run when the specific cloud drive is in use.
Issues of official cloud clients:

Usually always run in the background, slowing the system down, especially on lower-end systems
Have unnecessary "automatic file backup" features, which is usually unwanted due to storage limitations and privacy reasons
Most of the time, these tools do not support multiple users (ex: home and work/school )
Many people do not want to take the extra length to install the software required.
Unwanted integrations between the cloud service and operating system and/or software can cause errors or problems in the future

Requirements
see above
Files Version
N/A
Windows Version
N/A
Comments
No response

Thanks for the feedback. Are you asking to have a cloud provider called FUSE added? If so can you link to the client install.
If you are asking for Files to integrate the cloud drive clients into the app? If so that properly isn't going to happen as Files doesn't have the dev team to add and maintain all the APIs for them.

Thank you for your feedback, as Josh mentioned above, we don't currently have the capacity to implement support for cloud services but if you can link us to the client, we'll be happy to add support for detecting the client.

No, I want support for mounting FUSE-based cloud storage. FUSE is a drive
mounting tool.
On Sun, Jul 2, 2023 at 5:02 AM Josh65-2201 @.***> wrote:

Thanks for the feedback. Are you asking to have a cloud provider called
FUSE added? If so can you link to the client install.
If you are asking for Files to integrate the cloud drive clients into the
app? If so that properly isn't going to happen as Files doesn't have the
dev team to add and maintain all the APIs for them.
—
Reply to this email directly, view it on GitHub
https://github.com/files-community/Files/issues/12811#issuecomment-1616620710,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKNKRXDHSUF332XHZIGD5VDXOFPMBANCNFSM6AAAAAAZ2NB6PU
.
You are receiving this because you authored the thread.Message ID:
@.***>


Added WSN x-kaazing-idle-timeout k3po test scenarios

@irina-mitrea-luxoft I would recommend pulling in the latest changes from upstream/develop, your branch is quite far behind now

@cmebarrow I have performed the gateway fixes on the x-kaazing-idle-timeout WSN acceptor scenarios.
I have had a sporadic failure issue with one of the WSN Acceptor test cases, the failure was very difficult to encounter (I think one failed attempt of maybe 30-50 successful attempts). I am attaching the k3po debug log.
201510121905_standardPongFramesSentByServerNoClientTimeout.log | uploaded via ZenHub


Remove unused features (socket activation and KSM)

Note that this cannot realistically land until we a stand-alone daemon to handle KSM, hence the dnm label.
See:

#168
https://github.com/clearcontainers/runtime/issues/795

The tests are failing due to https://github.com/clearcontainers/tests/blob/master/.ci/install_proxy.sh#L34..L35 which is trying to modify the proxy's service file (which has been removed by this PR).
Once we have a KSM daemon, we can then:

Raise a tests PR to tweak install_proxy.sh.
Re-run the CI tests for this PR.

Blocked on https://github.com/clearcontainers/tests/issues/913.
We cannot remove the KSM functionality from the proxy until the issue above is resolved since the tests currently install the proxy "manually" using:

https://github.com/clearcontainers/tests/blob/master/.ci/install_proxy.sh

(Note that user systems would not be affected by removing the functionality since they have the cc-ksm-throttler package installed already).

Hi @chavafg, @grahamwhaley - now that https://github.com/clearcontainers/tests/pull/920 has landed, could you both confirm that I can continue with removing these features from the proxy?

Let me check some stuff. afaict when we landed https://github.com/clearcontainers/tests/pull/911 then the metrics CI got to do the right thing, but it then appears when we landed https://github.com/clearcontainers/tests/pull/920 it might be back to being nobbled again (that is, KSM seems to be in effect even when we try to turn it off).
I'll have to go debug - which is made a fraction harder as the scripts don't generate any ack/nack/logs about what they are doing, so I have to go poke around the actual system... pls wait!
(oh, and apparently you need a rebase I think any how ;-) )

yep - I'll hold off rebasing until I get two confirmations :)


updating fbcs to 0.0.2

Can confirm all SHAs are correct here, we just need to discover why our redis and rekor-search-ui-rhel9 are not built
/cc @osmman @petrpinkas @ppecka @lance
Relates to: https://redhat-internal.slack.com/archives/C05M2GGKU7Q/p1707450833732149?thread_ts=1707449931.383969&cid=C05M2GGKU7Q

/hold until we can get registry redis and rekor-search-ui images

Adding the rest of the 0.0.2 images now

The images with their respective shas exist on registry now.
Going to see if there is a successful build on konflux and then merge.

/ok-to-test

/retest


Add Gentoo packages list, rework on Build section

The list is in alphabetical order, even Ubuntu is way more popular, but considering the list might grow, the order could be a better choice.
The packages are in literal text (for better looking), as space-separated list, it's for user's convenience, they can just copy and paste the list to use with package managers.

Sorry, I've been very busy recently. So didn't have chance to respond to this. Feel free to re-open if you still want it merged.


Fix issue: AltGr handled as Ctrl

This fixes issue #475 about AltGr handling.

Thanks.
LGTM
I will check.
For reference:  https://github.com/AmokHuginnsson/replxx/blob/master/src/terminal.cxx#L374-L387

Validated


Fixed #24826 -- Accounted for filesystem-dependent filename max length

Thanks Raphaël Hertzog for the report and help on the patch.

Do you imagine this as a public or private API? Someone browsing the source code might be a bit confused about its purpose (since it has no affect besides in a test). If we could keep the code limited to the test, we could more easily backport a fix to 1.8, I'd think. Would you be opposed to trying that?

We could easily move the code in the test files. However it might be a valuable information that could be use in the future when checking file name validity, for example. I'll try to update the patch anyway.

Superseded by #4697


How to use ipv4 in guzzlehttp/guzzle": "^6.2

exception 'GuzzleHttp\Exception\ConnectException' with message 'cURL error 7: Failed to connect to -----ipv6-------- Network is unreachable (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)
How do I use ipv4 guzzle 6.2?
How is the default for all connections ipv4?

what is the context of the error?

exception 'GuzzleHttp\Exception\ConnectException' with message 'cURL error 7: Failed to connect to -----ipv6-------- Network is unreachable (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)

Yes but when does it happen? How can I recreate it?

What Operating System are you on btw


feat: add algebra of sets

Define the notion of algebra of sets and prove basic properties.
Define the algebra of set generated by a family and prove basic properties.
Prove that the algebra of sets generated by a countable family is countable.

This is the first PR involving a whole new file that I do on my own, with new definitions and the use of namespaces. I tried to inspire from the similar files PiSystem and SetSemiring.

bors r+
Thanks!


Sankey Chart visualization option for response time (duration, VC, etc)

Currently, Sankey charts show flows between user actions. The thicker the line, the more requests that flowed between those actions. Allow for an option to size the "flows" based on average duration, vc, etc.

This might be better covered with a color mode for duration, visually complete and speed index. The goal is to see where choke points exit. Apdex could do this, but Apdex calculation could have errors factored in. So a breakout based on response times would make sense.


Fix: 10x summon (continue) misclick

The old location for continueSummonClick didn't even register on my phone, so I moved it slightly up:

Before and after video comparison. I'm not sure if JP's layout is different. D:

You're right, it's even below the point where it clicks continuously. I'm wondering why it even works on my phone. 🤣

JP layout is pretty much the same, so there won't be any problems.


Adding Default Message Option to the Whatsapp Button

Added a default message prop to the floating whatsapp button.
What is now different?
The users can now add a default message which will be populated in the chat by default.
Reasons for changes
This can be really helpful for e-commerce stores (like ours) wherein we want to prefill the chat with the URL and a few details so that users need not enter them and we save time.
Anything to watch out for?
I don't think so, I have tested it with example app and it is working fine.
Screenshots.
Here is a screenshot of the button with the default message prefilled

Note
I would love to update the README with the details of this update once you merge it.

@saiteja13427 Thank you for contribution.

@awran5 Shall i edit the README.md including this new feature to it?

@saiteja13427 Sure, you are welcome.


Unable to select arbitrary array fields

I've got some arbitrary array fields in my schema like so:
let Schema = new mongoose.Schema({
  name: String,
  other_names: [String],
});

A get request to /api/endpoint?select=name other_names
returns the error:
{
  "status": 500,
  "name": "Internal Server Error",
  "message": "Cannot read property '0' of undefined (500).",
  "stack": "TypeError: Cannot read property '0' of undefined\n    at gatherPopulateParams (/home/archadmin/projects/maid-db/node_modules/baucis-decorator-deep-select/index.js:137:38)\n    at /home/archadmin/projects/maid-db/node_modules/baucis-decorator-deep-select/index.js:25:11\n    at Array.forEach (native)\n    at /home/archadmin/projects/maid-db/node_modules/baucis-decorator-deep-select/index.js:23:23\n    at Layer.handle [as handle_request] (/home/archadmin/projects/maid-db/node_modules/express/lib/router/layer.js:95:5)\n    at next (/home/archadmin/projects/maid-db/node_modules/express/lib/router/route.js:131:13)\n    at Route.dispatch (/home/archadmin/projects/maid-db/node_modules/express/lib/router/route.js:112:3)\n    at Layer.handle [as handle_request] (/home/archadmin/projects/maid-db/node_modules/express/lib/router/layer.js:95:5)\n    at /home/archadmin/projects/maid-db/node_modules/express/lib/router/index.js:277:22\n    at Function.process_params (/home/archadmin/projects/maid-db/node_modules/express/lib/router/index.js:330:12)\n    at next (/home/archadmin/projects/maid-db/node_modules/express/lib/router/index.js:271:10)\n    at next (/home/archadmin/projects/maid-db/node_modules/express/lib/router/route.js:121:14)\n    at /home/archadmin/projects/maid-db/node_modules/baucis/Controller/request/streams.js:42:5\n    at Layer.handle [as handle_request] (/home/archadmin/projects/maid-db/node_modules/express/lib/router/layer.js:95:5)\n    at next (/home/archadmin/projects/maid-db/node_modules/express/lib/router/route.js:131:13)\n    at Route.dispatch (/home/archadmin/projects/maid-db/node_modules/express/lib/router/route.js:112:3)"
}

Wow I somehow completely missed this issue.  😓  I am so so sorry.  I only just now noticed it when checking all of the open issues under https://github.com/loggur.  It's been... what... 6 months?  I'm betting this particular issue is unimportant now.  Did you ever figure it out?


Experiment with post

Codecov Report

Merging #2 into gatsby will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           gatsby       #2   +/-   ##
=======================================
  Coverage   95.71%   95.71%
=======================================
  Files          28       28
  Lines         140      140
  Branches        8        8
=======================================
  Hits          134      134
  Misses          6        6

Impacted Files
Coverage Δ

src/templates/post-template.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1b0db88...d740b1b. Read the comment docs.


Add the ability to differentiate between model loads from remote fetch v/s model loads from cache

Upstreamed from https://github.com/mlc-ai/relax/pull/265

@tqchen Hi, let me know if this looks okay as an upstream of https://github.com/mlc-ai/relax/pull/265

Thanks for upstreaming this change! CC: @tqchen

Not an expert here but this change looks pretty neat to me - giving an approval and anyone with more context please get it merged!


Support ES256 signatures

Right now only RS256 is supported. However it is known that some providers/intermediaries will use ES256, for example, AWS Load Balancer which is referenced in #smallrye/smallrye-jwt/issues/143, but also independently confirmed in #auth0/node-jsonwebtoken/issues/514 and possibly in others.
Even without those issues, supporting a well known alternative to RS256 (FYI, it has a higher Recommended+ status compared to RS256 in the JWA spec - which is only informative but indicates that the experts regard it quite highly) would let MP-JWT cover a wider user audience.
it will also sync it with the builder API PR.
My understanding is that no major changes will be needed to support both RS256 and ES256. The PR will recommend using only RS256 or ES256 but not both at the same time (it is considered to be a risky idea in JOSE for the token alg header alone dictating indirectly what key to load), which will let the implementations decide, when loading the keys, if they should be treated as RS or EC keys without any ambiguities.

I should mention a critical issue around the way some libraries were dealing with validating ES256 back in 2017, this post is informative. Note it was not really an algorithm flaw, and it has been fixed across the spectrum of libraries, including jose4j, nimbus, and others. As it is often the case the flaws in the libraries can be attributed to the specification itself :-). even more theoretically sound EC algorithms can be supported in the future if needed, but for now ES256 should be sufficient

For the record, I've removed the comment where I've wrongly assumed there was a ES256 vulnerability back in 2017 which in fact was related to the EC key based encryption and since was fixed across all the known libraries. (Which is quite embarrassing because I applied a relevant fix to my former project too at a time but it was awhile back :-)).
So all is good about ES256 and the trust a specific AWS project puts into it confirms it, obviously it was not chosen randomly


Scrape by Title instead of Hash?

I have a whole bunch of games that the scraper can't figure out because I ripped them myself. Because of this, the hashes don't match the online databases.
Is there a way I can get it to scrape by titles that match screenscraper.fr, instead of hashes?

Sorry for the delay. I probably won't ever add auto scraping my name. I have considered allowing a fallback to manual scraping by name but never really got around to implementing it.


Use absl::Status and co explicitly

MediaPipe exposes mediapipe::Status, mediapipe::StatusCode, mediapipe::StatusOr<> and mediapipe::OkStatus() which are aliases to their Abseil counterparts. Those aliases have been marked as deprecated, as shown here, for example: https://github.com/google/mediapipe/blob/c6c80c37452d0938b1577bd1ad44ad096ca918e0/mediapipe/framework/deps/status.h#L30
When building with warnings turned on, deprecation warnings end up spamming the build logs quite a lot, and play a part in being unable to treat warnings as errors in external code that includes some of MediaPipe's public headers.
This PR aims at removing all the uses I could find internally in the MediaPipe codebase.
Ideally I'd also like to remove the aliases themselves, but I realize this could break 3rd party code despite the deprecation flag because the warnings are silenced by default in .bazelrc, so I left them in.
I also left https://github.com/google/mediapipe/blob/master/mediapipe/framework/deps/status_test.cc mostly untouched, although 95% of it only tests Abseil's implementation. The test cases I did not touch could probably be safely deleted.

@jiuqiant @chuoling @sgowroji Would it be possible to merge this?


Issue with /docs/tutorials/kubernetes-basics/deploy-interactive/

This is a...

[ ] Feature Request
[X] Bug Report

Problem:
Proxy command is stuck and never completes:

kubectl proxy
Starting to serve on <IP_ADDRESS>:8001

Proposed Solution:
Page to Update:
http://kubernetes.io/...

Doesn't seem to be happening now, but I'm keeping an eye on the interactive tutorial since it's getting a lot of bugs.


QJson not working in VS 2019 with Qt 5.15

When trying to visualize a QJsonDocument, or any QJson* object really, I'm not getting what I was expecting.
When empty:

When not empty:

please let me know if you want me to provide any more information.
I have tried to add the .natvis in either Program Files or My Documents VS folders but it wouldn't change a thing.

Here is what I'm getting when displaying Error and Warning of Natvis files:
Natvis: C:\dev\QJson.natvis(4,4): Warning: Unable to load a visualized preview for type 'QJsonDocument' because the conditions of all <DisplayString> elements were false.
Natvis: C:\dev\QJson.natvis(55,6): Error: Side effects are not supported in this context.
    Error while evaluating '((Qt5Cored.dll!QtCbor::ByteData*)(tt()->data.data() + (int)(tt()->elements.at(n).value)))' in the context of type 'Qt5Cored.dll!QCborContainerPrivate'.
Natvis: C:\dev\QJson.natvis(46,57): Error: class "QCborContainerPrivate" has no member "byteDataAt"
    Error while evaluating 'container->byteDataAt(n)->str(),[container->byteDataAt(n)->len]na' in the context of type 'Qt5Cored.dll!QCborValue'.

hope this helps

Thank you for using my natvis files. I assume you used the latest version of Qt. As I know, there are a lot of changes in Qt QJson. I don't use Qt products at the moment, so I can't help you, sorry.

More detail:
Natvis: QJson.natvis(54,6): Error: Side effects are not supported in this context.
    Error while evaluating '((Qt5Cored.dll!QtCbor::ByteData*)(tt()->data.data() + (int)(tt()->elements.at(n).value)))'

@RichardTea do you have the .pdb files installed as well?  Without them I think it's impossible for natvis to resolve the internals...

@RichardTea do you have the .pdb files installed as well? Without them I think it's impossible for natvis to resolve the internals...

The nativs file provided by the visual studio qt plug-in works normally. QString can be visualized, but the added QJsonObject does not. Is this a problem with the pdb file?


Deleting a default key for helmrelease (setting to null)

Helm supports unsetting/deleting the default chart value: https://helm.sh/docs/chart_template_guide/values_files/#deleting-a-default-key
It works as expected when you set some value to null when HelmRelease is created the first time, for example you set cpu limit to null and the end result is:
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
[...]
spec:
  values:
    resources:
      limits:
        cpu: null
        memory: 128Mi

but if you update the HelmRelease and set some other value to null, for example memory limit, it ends up as:
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
[...]
spec:
  values:
    resources:
      limits:
        cpu: null

Thus, it doesn't propagate to helm and has no effect at all. I hope this bug is not inherent to the kubectl/k8s itself and can be fixed in kustomize-controller.

I guess this is what kustomize build does too, in Flux we don’t manipulate yaml directly, we use the kustomize/api package to build the yamls in the same way the kustomize CLI does it.

@stefanprodan I've just tested by running kustomize build locally - it produces the value with null correctly and as I've mentioned it works as expected when the resource is created the first time. The problem occurs only on update.
Actually, I've just tested this manually by executing kubectl apply in the same order (result is the same), so this is related to kubectl and how it applies the change...

so this is related to kubectl and how it applies the change

I don't see how we could do something about this, we exec to run kubectl apply and it's up to kubectl to do the 3-way-merge.

kubectl apply --server-side=true works correctly in my simple test, but it causes a conflict with helm-controller managed field.

Should this be moved to Helm Controller? I'm not sure it is a Kustomize Controller issue.

I think that this is indeed not a kustomize controller issue and not even a fluxcd issue, but if there are any ideas on the solution then can be moved to helm controller for sure.
In any case the good workaround is to just move the values to configmap and reference it via valuesFrom.

Does it mean that Flux does not handle this special null value as Helm describes in deleting-a-default-key?

I'm reproducing the same problem with https://github.com/crossplane/crossplane/blob/969b8ebdf2aedc1849302b687f2eebeba94b55f3/cluster/charts/crossplane/values.yaml.tmpl#L65-L69
whose value.yml has
securityContextCrossplane:
  runAsUser: 65532
  runAsGroup: 65532
  allowPrivilegeEscalation: false
  readOnlyRootFilesystem: true

A strategic patch with the following
spec:
  values:
    #see https://github.com/jeremycaine/crossplane-with-openshift/blob/main/1.%20Installing%20Crossplane%20on%20Openshift/README.md#install-crossplane
    securityContextCrossplane:
      runAsUser: null
      runAsGroup: null
    securityContextRBACManager:
      runAsUser: null
      runAsGroup: null

when trying to set a null runAsUser in the value gets ignored, and results into the HelmRelease value field as
    securityContextCrossplane: {}
    securityContextRBACManager: {}

As a result the default chart values are assigned by flux helm release
       securityContext:
          allowPrivilegeEscalation: false
          readOnlyRootFilesystem: true
          runAsGroup: 65532
          runAsUser: 65532

Trying to assign an empty map {} in the value, simply gets ignored by the strategic merge.
My workaround is to use helm post rendered to correct incorrect helm values in the resulting helm rendered templates, but this breaks the helm chart encapsulation.

I ran into the same issue as @gberche-orange, with a very similar usecase. I noticed that when using flux as intended via git and using a kustomization, it does indeed delete the null value, but when applying an hr directly using kubectl apply, the null values are not deleted and helm install works as intended with the deletion of the default keys.

I see this was fixed in Kustomize 5.x, but since Flux is still using the 4.x version the bug is still present.

The upgrade to Kustomize 5 includes permanent and final deprecation of patchesStrategicMerge and patchesJson6902 - there's a list of breaking changes in the release notes here, and a separate section for deprecations as well:
https://github.com/kubernetes-sigs/kustomize/releases/tag/kustomize%2Fv5.0.0
This should hopefully become normalized for the Flux 2.0.0 final release, I think it hasn't made it into any release candidate yet. It looks like these changes should harmonize to settle on patches that Flux has been promoting in our docs more for a while. I think many of those changes have already landed in Flux 2.0.0-rc.1, the API changes in particular deprecating other patch methods besides patches.
It's not clear from the release notes if Kustomize 5 is landing in 2.0.0, or if it may land yet in the next 2.0.0-rc.2. Let's stay tuned. I think it's good news, if Kustomize 5 fixes this 🎉 I think the breaking changes from upstream will likely come aligned with our own major bump, but I'm not the one doing the work so don't want to prognosticate too strongly about it.

Kustomize 5.x is planned before landing v2.0.0. Hopes this answers (part) of the question.

Is it already not upgraded in v1.0.0 according to the changelog https://github.com/fluxcd/kustomize-controller/blob/v1.0.0/CHANGELOG.md?

Yes, Kustomize v5 has been introduced to Flux since Flux 2.0.0 and Kustomize Controller 1.0.0, and we're up to Kustomize 5.2 as of Flux 2.2 (which comes with some more breaking fixes)
This issue should be resolved, if I understood the thread correctly reviewing it just now in summary? (Can anyone confirm to close it?)

@kingdonb, it doesn't seem fixed to me, I'm still experiencing this issue on HelmRelease upgrades with these versions:
› flux version
flux: v2.2.3
distribution: flux-v2.2.3
helm-controller: v0.37.4
kustomize-controller: v1.2.2
notification-controller: v1.2.4
source-controller: v1.2.4

same here


dropdown for choosing a type for reference

Codecov Report

Merging #18 (d06bba2) into main (5207ef3) will decrease coverage by 2.47%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main      #18      +/-   ##
==========================================
- Coverage   42.85%   40.38%   -2.48%
==========================================
  Files           2        2
  Lines          49       52       +3
  Branches        3        4       +1
==========================================
  Hits           21       21
- Misses         28       31       +3

Impacted Files
Coverage Δ

src/routes.py
0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Go to Start/End Keys for Paginator

This is just a simple feature request: I think it will be nice if we have "Go to Start" and "Go to End" key bindings for the paginator, mapped to the Home and End keys. I think the implementation should be simple, but I was a bit unsure of how to add the functionality myself, so I did not go ahead with a PR. I thought this might be something on your mind as well, so I opened up an an issue instead.
PS: Great work on this project btw 😁 ! Thanks to this I did not have to go to all the trouble to try and come up with a table widget myself. The speed at which you are implementing all these features is almost unreal 😮 ! I started using it when you implemented pagination, which was a feature I sorely needed (the data I wanted to display had more than 3000 entries!).

Hey there, glad you find it useful!
I'll add that in the near future, I just want to sort out #29 before coding anything as I think there will be some collisions.
Out of curiosity, how is the performance for you with 3000 entries?  Let me know if it's sluggish, I've prioritized correctness/simplicity over performance so far as I hadn't expected it to be used for that much!

Thanks for the quick reply 😁 ! I am seeing pretty good performance with 3000 entries so far. There were some lags before but they were because of how I was interacting with the SQL database, not because of the UI. Let me see if I can add some GIFs to my project's README. If you want to check it out yourself, the project is here.
PS: Excited to see how #29 unfolds.

This should now be implemented in 0.7.0, give it a try and let me know if this works for you!  If so feel free to close the issue.


Cannot set path for export in preferece

Debug log ID
CPY2JNWV-refs-euc/6.7.203-7
What happened?
Re-installed the plugin as it wasn't working and I have no place to set the export directory of the library.  No place to check the cache or re-gen the cache.  It's as if the entire section of the screen went missing.  On a MacBook.  The option was in the preferences, not its gone.

Did you try to change the path by hand in the database perhaps?

There isn't a place to modify the export directory of the library. There's something wrong with your database, I don't know what yet exactly or how it came about. If you have modified it manually I need to know.

I did not change anything manually.  I am not sure what happened.

Can you cmd-q zotero, go into your zotero directory, zip up zotero/better-bibtex.sqlite, and attach it here?

TypeError: Zotero.ItemPaneManager is undefined. So that is 2 mac systems with the issue

That Zotero-beta needs to be upgraded

To simplify, I blew away Zotero completely from the machine Reversed to the stable release of 6, and still the same issue.  Both machines have no way to set the path for auto-export.  The error above was not from beta, it was from version 6 stable.  The attached logs are from the initial machine.
better-bibtex.sqlite.zip
This one is the other machine where I installed a fresh copy of 6.  This is the machine with the error above:
better-bibtex.sqlite-v6-cleaninstall.zip

To simplify, I blew away Zotero completely from the machine Reversed to the stable release of 6, and still the same issue.

Can you send a new log from that install? If the regular error report doesn't work, the Help menu will have a "send debug log to file.io" entry that can be used as a fallback.
CPY2JNWV-refs-euc/6.7.203-7 shows errors I haven't seen before, and these seem specific to zotero 7.

Both machines have no way to set the path for auto-export.

I don't know what this means TBH. You can't set a path for auto-export anywhere. Auto-export works by exporting as you usually would, and checking the "keep updated" checkbox. If you mean that you can't select a path during regular exports, something is really wrong, because that's Zotero functionality, not BBT functionality.

The error above was not from beta,

Which error specifically?

This one is the other machine where I installed a fresh copy of 6. This is the machine with the error above:

What error specifically?

Can you try build 6427 and send a new debug log?

I'd love to fix this but since I cannot reproduce this on my end, I will have to get more information from your end.

Sorry for not replying sooner.  I ended up deleting the beta version off the machine and reinstalling the stable release and that seems to clear things up and it's working again.  It's something with the beta version.  and it did it on both machines.  But since I deleted it completely and reinstalled only stable, it works!

Alright. Glad it works.


When repeat is cloned setAllVals should only set the values in the new clone [3]

Now it sets the values of the whole form. Could be a significant performance issue.

this won't show up in performance monitor

works like a charm


Add Notes field to Inventory Items

Description
Closes https://github.com/maplethorpej/packstack/issues/25.
This PR adds a "Notes" field to the Inventory form. When adding a PackItem to a Pack, any notes on the Item are by default carried over to the "Notes" field of the PackItem.
Open questions for reviewers/community

In the issue https://github.com/maplethorpej/packstack/issues/25, the opener asked for a "Comments" field. I have implemented a "Notes" field, but can change to whatever folks prefer.
I have set it so the Notes are displayed after the Product Name for each lineitem in the Inventory list, but I was testing on a large screen so it may be too cluttered on a smaller one. Let me know.
Any thoughts on the placeholder text?

Note: I have not done a db migration before, the one I wrote worked fine for me but for all I know may be a disaster for someone else, please check. 😄
Demo
https://user-images.githubusercontent.com/8898786/104103708-8d5ca680-529b-11eb-9892-5c6c8d99c3da.mov

@Callisto13 One thing we may want to consider is adding a column to a row item that contains an icon indicator if the item has notes. For example, a blue dot if there are notes, otherwise light gray. This should help us save some space for the more critical fields in the table. Thoughts on this?
By the way, I really like that this copies the text to the packItem record. Nice work!

@Callisto13 One thing we may want to consider is adding a column to a row item that contains an icon indicator if the item has notes. For example, a blue dot if there are notes, otherwise light gray. This should help us save some space for the more critical fields in the table. Thoughts on this?
By the way, I really like that this copies the text to the packItem record. Nice work!

One thing we may want to consider is adding a column to a row item that contains an icon indicator if the item has notes. For example, a blue dot if there are notes, otherwise light gray.

Yeh I like that idea, will update. Maybe with a hover-over thing which explains what the dot means, otherwise I can see users being like "what is this mysterious thing?"

One thing we may want to consider is adding a column to a row item that contains an icon indicator if the item has notes. For example, a blue dot if there are notes, otherwise light gray.

Yeh I like that idea, will update. Maybe with a hover-over thing which explains what the dot means, otherwise I can see users being like "what is this mysterious thing?"

@maplethorpej I've update the UX following your suggestion: rather than having the Notes shown in the grid, there is a dot at the start of each line item which is blue when it has notes, grey if not. Also, when hovering over the dot the notes are shown in a Tooltip.
Currently I have put a "No notes on this item" message in the case that there aren't any, but I am going back and forth on whether I like that UX, what do you think?
Also I have set the Tooltip placement to the right here (unlike above as we have elsewhere) as when there is lots of text it looks better.
https://user-images.githubusercontent.com/8898786/105607257-a84c1200-5d95-11eb-8008-909bd633c717.mov

@maplethorpej I've update the UX following your suggestion: rather than having the Notes shown in the grid, there is a dot at the start of each line item which is blue when it has notes, grey if not. Also, when hovering over the dot the notes are shown in a Tooltip.
Currently I have put a "No notes on this item" message in the case that there aren't any, but I am going back and forth on whether I like that UX, what do you think?
Also I have set the Tooltip placement to the right here (unlike above as we have elsewhere) as when there is lots of text it looks better.
https://user-images.githubusercontent.com/8898786/105607257-a84c1200-5d95-11eb-8008-909bd633c717.mov

I think that looks great! Super clean. 👍

I think that looks great! Super clean. 👍

Perfect, this looks great! Merging!


The Extension is suggested by the current user Bug!

Issue Type: Bug
When we click on The Extension is suggested by the current user Bug! Buttton then it type it down and when we remove the suggestion it duplicates and when we again click on The Extension is suggested by the current user Bug! it again add one more message but when we change the tab it clears and when come again on extension tab then its normal
VS Code version: Code 1.67.1 (da15b6fd3ef856477bf6f4fb29ba1b7af717770d, 2022-05-06T12:37:03.389Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz (4 x 2494)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: unavailable_offopengl: enabled_onrasterization: unavailable_offraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: unavailable_off

Load (avg)
undefined

Memory (System)
7.91GB (3.02GB free)

Process Argv
--crash-reporter-id 317d6e83-666e-47dc-a0c1-00261da7ea3a

Screen Reader
no

VM
0%

Extensions (34)

Extension
Author (truncated)
Version

vscode-color
ans
0.4.5

vscode-custom-css
be5
6.0.2

LinkCheckMD
bla
0.3.1

vscode-tailwindcss
bra
0.8.4

doxdocgen
csc
1.4.0

es7-react-js-snippets
dsz
4.4.3

vscode-html-css
ecm
1.12.2

vscode-npm-script
eg2
0.3.25

auto-close-tag
for
0.5.14

auto-complete-tag
for
0.1.0

auto-rename-tag
for
0.1.10

code-runner
for
0.11.7

copilot
Git
1.20.5902

better-cpp-syntax
jef
1.15.13

vscode-language-babel
mgm
0.0.36

code-beautifier
mic
2.3.3

vscode-docker
ms-
1.22.0

python
ms-
2022.6.2

jupyter
ms-
2022.4.1021342353

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.6

cmake-tools
ms-
1.10.5

sublime-keybindings
ms-
4.0.10

vscode-react-native
msj
1.9.2

vscode-css-peek
pra
4.2.0

open-php-html-js-in-browser
Pri
2.0.1

html-to-jsx
ria
0.0.1

LiveServer
rit
5.7.5

vscode-open
san
0.1.0

html-preview-vscode
tht
0.2.5

vscode-icons
vsc
11.11.0

vscode-simple-download
wk-
19.12.6

JavaScriptSnippets
xab
1.8.0

html-css-class-completion
Zig
1.20.0

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
pythonvsnew555:30457759
vscscmwlcmt:30465135
cppdebug:30475216
vsclangdf:30486550

/gifPlease

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette).
Happy coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


cleanup; fix ports and index

[ ] This patch includes any updated documentation of the proposed changes
[ ] This patch includes tests that verify the proposed changes work as expected

Codecov Report

Merging #984 into master will decrease coverage by 1.22%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #984      +/-   ##
==========================================
- Coverage   78.27%   77.04%   -1.23%
==========================================
  Files          52       52
  Lines        5606     5603       -3
==========================================
- Hits         4388     4317      -71
- Misses       1218     1286      +68

Impacted Files
Coverage Δ

vent/helpers/meta.py
73.73% <100%> (+1.83%)
:arrow_up:

vent/menus/ntap.py
24% <0%> (-33.6%)
:arrow_down:

vent/core/network_tap/ncontrol/rest/nlist.py
66.66% <0%> (-33.34%)
:arrow_down:

vent/api/actions.py
76.33% <0%> (-1.91%)
:arrow_down:

vent/menus/main.py
77.89% <0%> (-1.32%)
:arrow_down:

vent/api/plugins.py
77.54% <0%> (-0.87%)
:arrow_down:

vent/api/menu_helpers.py
92.71% <0%> (-0.41%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 587292d...bb99238. Read the comment docs.


Feat: Added Amazon EKS Resource Detector

Which problem is this PR solving?

Added AWS EKS Resource Detector
This is similar to the AWS EKS Resource Detector in Java

Short description of the changes

Added functionality of AWS EKS resource detector
Added corresponding unit tests for AWS EKS detector

If you can review @dyladan, @anuraaga, thanks a lot!

@dyladan  Hi Daniel, would really appreciate any comments or review of the code when possible thanks!

@obecny would really appreciate a review and merge if possible, thanks!

@KKelvinLo something wrong either with merge or rebase with latest master I suddenly see here changes which has nothing to do with yr PR.

@obecny Consistencies resolved and rebased master, cheers!


Rain in desert biomes

Mod Version:
DynamicSurroundings-1.12.2-<IP_ADDRESS>.jar
Forge Version:
2836
Description:
Dynamic Surroundings weather control, causes there to be rain in deserts, could you please add an option to disable rain in Desert biomes

Are/were you running Serene Seasons at the same time?  Reason is that there can be seasonal rain with that mod installed.

Closing due to inactivity.  If you feel this is in error feel free to open again with additional details.

I am also seeing rain in desert biomes on version <IP_ADDRESS>.  No other mods that mess with weather are installed.


load (load s0, s1), s2 causes an Internal Compiler Error in the parser

For this invalid program:
address 0
load (load s0, s1), s2

instead of outputting a sensible error message, the assembler outputs the following:
Internal compiler error: The assembly-lanaguage expression in line 2 doesn't end with a new-line token!

Given the way the parser is structured, there doesn't appear to be a simple solution.

I've opened a LangDev StackExchange question about this.


Internal: Add missing colors for graphical elements 5,6 and 7

Why?
Figma had colors that weren't in Core package
What?

Added colors for.

graphicalElements5
graphicalElements6
graphicalElements7

Update tests

Version Change

Minor

UI Changes

Where this is used?
I don't like much the whole graphical element X,
Since now we are having even more of these, we are losing the semantics. What's the difference of graphical element 1, 2, 3... 7?

I agree. Semantic colors are about what they mean semantically, and “graphical element 1, 2, , 4, 5, 6, 7” doesn't tell me anything about their semantic meaning.

It's used in the duration picker I've been meddling with, but yeah, let's do a 🥯  on it tomorrow.


method-level timeout config

While working on #2859 I noticed that some languages only take the timeout configuration from the RetryParams total_timeout_millis field instead of the MethodConfig timeout_millis. The comments on the latter indicate its only for methods not being retried and is unsupported in just half of the languages.
I think this conflates two configs:

The overall timeout of a method invocation (not individual RPCs but what a user would ultimately see as a DEADLINE_EXCEEDED for their method invocation)
How to retry an RPC (the RPC is the underlying invocation of the method, where multiple RPCs can be made by a single method invocation in the case of retries) in defined error modes

I don't think the retry and the method timeout configs should be combined the way they are in the RetryParams.
Furthermore, as we move towards using gRPC ServiceConfig RetryPolicy as the source of retry config, the RetryParams-defined timeout should be phased out. With gRPC ServiceConfig, the timeout is defined at the MethodConfig level, not the RetryPolicy level.
As it stands, this difference in configuration sources is blocking #2859. A few options are:

start using MethodConfig-level timeout_millis (instead of RetryParams timeout) as the source everywhere (the value is given by the gRPC ServiceConfig MethodConfig timeout)
Inject the gRPC ServiceConfig timeout (also a MethodConfig level param) into the RetryParams total_timeout_millis config

I don't like option 2 because it means even when there is no retry policy defined for a method, it will still have a retry config with mostly zeros/defaults and then a total_timeout_millis value of X, which I believe to be confusing.

After talking with the team, the easiest thing to do is option 2, setting the timeout in both the retry params and the method level configs. The "actual" value in a "no_retry_params" config for such a timeout is fine, it was said that we have examples of this elsewhere.


saving files

Saved files can be quite large - play around with @save filename.JLD2 {compress}  ??
Check why  files of a single subject with 128 channels can be 2gb large - seems too big

function save(file,uf::T;compress=false) where T<:UnfoldModel
	jldopen(file, "w"; compress = compress) do f
    	f["uf"] = T(uf.design,Unfold.DesignMatrix(designmatrix(uf).formulas,missing,designmatrix(uf).events),uf.modelfit)
	end
end
function load(file,::Type{<:UnfoldModel})
	f = jldopen(file, "r")
	uf = f["uf"]

	form = designmatrix(uf).formulas
	events = designmatrix(uf).events

	X = Unfold.modelcols(form.rhs, events)

	# reintegrate the designmatrix
	return typeof(uf)(uf.design,Unfold.DesignMatrix(form,X,events),uf.modelfit)

end

@jschepers can you try this out with an realistic UnfoldFile?
These tools might be helpful:
pretty_filesize(x) = Base.format_bytes(filesize(x))
pretty_summarysize(x) = Base.format_bytes(Base.summarysize(x))
	@time save(joinpath(tempdir(),"test3.jld2"),m;compress=true)
	@time save(joinpath(tempdir(),"test4.jld2"),m;compress=false)

begin
	sizex = x->pretty_filesize(joinpath(tempdir(),"test$x.jld2"))

	@show pretty_summarysize(m)
	for k = 1:4
		@show sizex(k)
	end
end

@time m2 = load(joinpath(tempdir(),"test4.jld2"),UnfoldModel)
m.designmatrix.Xs == m2.designmatrix.Xs


broke up css files - format js files - package-lock updated

Features:

Separated App.css into component level css files, all css files are in styles/
Formatted JS files with prettier, previous files were unformatted and difficult to read, formatting keeps code consistent
package-lock was updated with npm i, testing libraries for react were removed. Library depenencies for react might have changed, package-lock should reflect it

Goal:

A single css file used to store all styles, made it difficult to change anything and was big, we needed smaller units to make changes more precisely, also makes the codebase more welcoming for component libraries

I will make a backlog ticket for the prettier subject


no such file or directory textflag.h : delve doesn't build out of the box

tried to "go get" delve just now, but its build is broken:
jaten@c:~/go/src/github.com/derekparker/delve:master$ go get github.com/derekparker/delve/cmd/dlv
# golang.org/x/sys/unix
/home/jaten/go/src/golang.org/x/sys/unix/asm.s:6 6a: No such file or directory: textflag.h
jaten@c:~/go/src/github.com/derekparker/delve:master$ sudo locate textflag.h
/var/mailgun/cutlass/jaten/pkg/go1.2.1/go/src/cmd/ld/textflag.h
/var/mailgun/cutlass/jaten/pkg/go1.2.1with_http_improved/go/src/cmd/ld/textflag.h
/var/mailgun/cutlass/jaten/pkg/go1.3.1/go/src/cmd/ld/textflag.h
/var/mailgun/cutlass/jaten/pkg/go1.3.3/go/src/cmd/ld/textflag.h
/var/mailgun/cutlass/jaten/pkg/go1.4/go/pkg/linux_amd64/textflag.h
/var/mailgun/cutlass/jaten/pkg/go1.4/go/src/cmd/ld/textflag.h
jaten@c:~/go/src/github.com/derekparker/delve:master$

3.11.0-26-generic #45~precise1-Ubuntu SMP
linux/amd64

Hmm, that's a problem with the sys package, not Delve. What version of Go are you using? Also, maybe rm -rf $GOPATH/src/github.com/derekparker/delve first and do a fresh go get?

using go1.4.1, with a fresh (go get -u ) pull of delve.  I copied the textflag.h file over to fix sys package, but then I hit a 2nd build error:
jaten@c:~/go/src/github.com/derekparker/delve/cmd/dlv:master$ go build
# github.com/derekparker/delve/proctl
/home/jaten/go/src/github.com/derekparker/delve/proctl/variables.go:684: undefined: dwarf.UnspecifiedType

I commented out variables.go:684-5 to get a build.

 I think I mixed go1.3 with go1.4. I deleted everything, made sure I was on go1.4.1, and now install goes fine. Probably a local problem. Closing issue.


How do I bind my own interrupt handling

I tried to get wwdg to feed the dog during an early interruption,I follow the embassy-hal-internal/interrupt documentation and use bind_interrupts! Macro and implements the InterruptHandler triat, but it doesn't work.
the code:
`static mut WWDG_R: embassy_stm32::pac::wwdg::Wwdg = embassy_stm32::pac::WWDG;
struct InterruptHandler {
}
impl interrupt::typelevel::Handler<embassy_stm32::interrupt::typelevel::WWDG> for InterruptHandler {
unsafe fn on_interrupt() {
WWDG_R.cr().write(|w| {
w.set_t(0x7f);
});
}
}
bind_interrupts!(struct Irqs {
WWDG => InterruptHandler;
});
#[entry]
fn main() -> !{
let (p,mut delay) = sys::sys_init(); // Set the external clock
info!("Hello World!");
let rcc = embassy_stm32::pac::RCC;
rcc.apb1enr().write(|w|{w.set_wwdgen(true)});
let wwdg = embassy_stm32::pac::WWDG;
wwdg.cr().write(|w|{
w.set_t(0x7f);
w.set_wdga(true);
});
wwdg.cfr().write(|w|{
w.set_ewi(true);
w.set_w(0x7f);
w.set_wdgtb(Wdgtb::DIV8);
});
let mut beep = Output::new(p.PF8,Level::High,Speed::High);
let mut count = 0;
loop {
count += 1;
if count == 40 {
beep.set_low();
}
// wwdg.cr().write(|w|{w.set_t(0x7f)}) ; // It works properly when unwrapped
delay.delay_ms(40);
}
}`

Hello @cn-cq-doudou Do you have any update on this topic? I am trying to bind the TIM3 timer overflow interrupt to my own handling but dont know how to start. Thank you!


Scene graph as input to test in VM

@zachphillipps  can you please approve my pull request thanks

With scene graph code updated, propose merging of branches.


Crashes when downloading "secure"

I have been getting semi-frequent crashes that seem to be related to attempts to download a file called "secure".  I am downloading to an NFS share, in case that is relevant.  Here is a sample of the log from one of these.
2021-Jul-21 00:51:24 [Thread #3] Download complete: dying_light_tf_enemy_artworks.zip (@ 0.00kB/s)
2021-Jul-21 00:51:24 [Thread #3] Begin download: secure
2021-Jul-21 00:51:24 [Thread #0] Download complete: dying_light_tf_character_artworks.zip (@ 0.00kB/s)
2021-Jul-21 00:51:24 [Thread #0] Begin download: secure
2021-Jul-21 00:51:25 [Thread #2] Download complete: dying_light_collectors_artbook.zip (@ 0.00kB/s)
2021-Jul-21 00:51:25 [Thread #2] Begin download: secure
2021-Jul-21 00:51:25 [Thread #1] Download complete: dying_dight_3D_printer_models.zip (@ 0.00kB/s)
2021-Jul-21 00:51:25 [Thread #1] Begin download: secure
2021-Jul-21 00:51:25 [Thread #0] Retry 1/3: secure (HTTP response code said error)
2021-Jul-21 00:51:25 [Thread #0] Retry 2/3: secure (HTTP response code said error)
2021-Jul-21 00:51:25 [Thread #2] Retry 1/3: secure (HTTP response code said error)
2021-Jul-21 00:51:25 [Thread #3] Retry 1/3: secure (HTTP response code said error)
2021-Jul-21 00:51:25 [Thread #1] Retry 1/3: secure (HTTP response code said error)
2021-Jul-21 00:51:25 [Thread #0] Retry 3/3: secure (HTTP response code said error)
2021-Jul-21 00:51:25 [Thread #2] Retry 2/3: secure (HTTP response code said error)
2021-Jul-21 00:51:25 [Thread #3] Retry 2/3: secure (HTTP response code said error)
2021-Jul-21 00:51:26 [Thread #1] Retry 2/3: secure (HTTP response code said error)
2021-Jul-21 00:51:26 [Thread #3] Retry 3/3: secure (HTTP response code said error)
2021-Jul-21 00:51:26 [Thread #0] Download complete (HTTP response code said error (404)): secure
2021-Jul-21 00:51:26 [Thread #0] Begin download: secure
terminate called after throwing an instance of 'boost::filesystem::filesystem_error' ▕                          ▏ 0.00/0.00MB @ 0.00kB/s ETA: 0s
  what():  boost::filesystem::file_size: No such file or directory: "/mnt/nas/non_backed_up/gog/games/dying_light_the_following_enhanced_edition/extras/secure"
Aborted

It looks like lgogdownloader may think the file was somehow downloaded correctly (which it was not), then tries to access it?

Another similar instance, except failing after a different HTTP error when trying to download "secure".
2021-Jul-30 01:27:17 [Thread #3] Begin download: secure
2021-Jul-30 01:27:17 [Thread #1] Download complete: dying_dight_3D_printer_models.zip (@ 0.00kB/s)
2021-Jul-30 01:27:17 [Thread #1] Begin download: secure
2021-Jul-30 01:27:18 [Thread #1] Retry 1/3: secure (HTTP response code said error)
2021-Jul-30 01:27:18 [Thread #3] Retry 1/3: secure (HTTP response code said error)
2021-Jul-30 01:27:18 [Thread #1] Retry 2/3: secure (HTTP response code said error)
2021-Jul-30 01:27:19 [Thread #3] Retry 2/3: secure (HTTP response code said error)
2021-Jul-30 01:27:19 [Thread #1] Retry 3/3: secure (HTTP response code said error)
2021-Jul-30 01:27:19 [Thread #1] Download complete (HTTP response code said error (503)): secure
2021-Jul-30 01:27:19 [Thread #1] Begin download: secure
terminate called after throwing an instance of 'boost::filesystem::filesystem_error' ▕████████▌                 ▏ 1349.87/4096.00MB @ 4.43MB/s ETA: 10m 19s
  what():  boost::filesystem::file_size: No such file or directory: "/mnt/nas/non_backed_up/gog/games/dying_light_the_following_enhanced_edition/extras/secure"
Abort

I don't own Dying Light so I can't test this but I'm guessing that this is caused by downloader failing to get proper filename/path for multiple extras.
Then because multiple threads are trying to download a file with the same path it causes a race condition where the file exists when starting download but before the thread can get filesize using boost::filesystem::file_size it has been deleted already by another thread when it notices the download failed.
Does the crash happen with --threads 1 ?
It could be that GOG has a new url formatting scheme for some files that causes galaxyAPI::getPathFromDownlinkUrl to fail in getting proper filepath. I'd be interested in what the new scheme is so I can change galaxyAPI::getPathFromDownlinkUrl to account for it.
Change line 2767 in downloader.cpp from this
retry_msg += " (" + retry_reason + ")";

into this
retry_msg += " (" + retry_reason + ")" + " " + url;

and then try downloading Dying Light again using multiple threads and post the retry reason output with the urls.
Change or remove some parts of token and access_token from the urls so they are not valid.

Thanks for taking a look at this.    Both times failed, though I notice the second time included a (503) error for one thread, if that is relevant.
2021-Jul-31 17:59:51 [Thread #0] Begin download: dying_dight_3D_printer_models.zip
2021-Jul-31 17:59:51 [Thread #1] Download complete: dying_light_tf_enemy_artworks.zip (@ 0.00kB/s)
2021-Jul-31 17:59:51 [Thread #1] Begin download: secure
2021-Jul-31 17:59:51 [Thread #2] Download complete: dying_light_tf_character_artworks.zip (@ 0.00kB/s)
2021-Jul-31 17:59:51 [Thread #2] Begin download: secure
2021-Jul-31 17:59:52 [Thread #3] Download complete: dying_light_collectors_artbook.zip (@ 0.00kB/s)
2021-Jul-31 17:59:52 [Thread #3] Begin download: secure
2021-Jul-31 17:59:52 [Thread #0] Download complete: dying_dight_3D_printer_models.zip (@ 0.00kB/s)
2021-Jul-31 17:59:52 [Thread #0] Begin download: secure
2021-Jul-31 17:59:52 [Thread #2] Retry 1/3: secure (HTTP response code said error) https://content-system.gog.com/products/1448452156/users/46989135497749423/namespaces/website/download?path=%2Fsecure&token=XXX&access_token=XXX
2021-Jul-31 17:59:53 [Thread #0] Retry 1/3: secure (HTTP response code said error) https://content-system.gog.com/products/1448452156/users/46989135497749423/namespaces/website/download?path=%2Fsecure&token=XXX&access_token=XXX
2021-Jul-31 17:59:53 [Thread #1] Retry 1/3: secure (HTTP response code said error) https://content-system.gog.com/products/1448452156/users/46989135497749423/namespaces/website/download?path=%2Fsecure&token=XXX&access_token=XXX
2021-Jul-31 17:59:53 [Thread #3] Retry 1/3: secure (HTTP response code said error) https://content-system.gog.com/products/1448452156/users/46989135497749423/namespaces/website/download?path=%2Fsecure&token=XXX&access_token=XXX
2021-Jul-31 17:59:53 [Thread #2] Retry 2/3: secure (HTTP response code said error) https://content-system.gog.com/products/1448452156/users/46989135497749423/namespaces/website/download?path=%2Fsecure&token=XXX&access_token=XXX
2021-Jul-31 17:59:54 [Thread #3] Retry 2/3: secure (HTTP response code said error) https://content-system.gog.com/products/1448452156/users/46989135497749423/namespaces/website/download?path=%2Fsecure&token=XXX&access_token=XXX
2021-Jul-31 17:59:54 [Thread #0] Retry 2/3: secure (HTTP response code said error) https://content-system.gog.com/products/1448452156/users/46989135497749423/namespaces/website/download?path=%2Fsecure&token=XXX&access_token=XXX
2021-Jul-31 17:59:54 [Thread #1] Retry 2/3: secure (HTTP response code said error) https://content-system.gog.com/products/1448452156/users/46989135497749423/namespaces/website/download?path=%2Fsecure&token=XXX&access_token=XXX
2021-Jul-31 17:59:54 [Thread #0] Retry 3/3: secure (HTTP response code said error) https://content-system.gog.com/products/1448452156/users/46989135497749423/namespaces/website/download?path=%2Fsecure&token=XXX&access_token=XXX
2021-Jul-31 17:59:54 [Thread #2] Retry 3/3: secure (HTTP response code said error) https://content-system.gog.com/products/1448452156/users/46989135497749423/namespaces/website/download?path=%2Fsecure&token=XXX&access_token=XXX
2021-Jul-31 17:59:54 [Thread #3] Retry 3/3: secure (HTTP response code said error) https://content-system.gog.com/products/1448452156/users/46989135497749423/namespaces/website/download?path=%2Fsecure&token=XXX&access_token=XXX
terminate called after throwing an instance of 'boost::filesystem::filesystem_error' ▕                          ▏ 0.00/0.00MB @ 0.00kB/s ETA: 0s
  what():  boost::filesystem::file_size: No such file or directory: "/mnt/nas/non_backed_up/gog/games/dying_light_the_following_enhanced_edition/extras/secure"
Aborted

2021-Jul-31 18:05:05 [Thread #0] Begin download: dying_dight_3D_printer_models.zip
2021-Jul-31 18:05:05 [Thread #2] Download complete: dying_light_tf_posters.zip (@ 0.00kB/s)
2021-Jul-31 18:05:05 [Thread #2] Begin download: secure
2021-Jul-31 18:05:05 [Thread #3] Download complete: dying_light_tf_character_artworks.zip (@ 0.00kB/s)
2021-Jul-31 18:05:05 [Thread #3] Begin download: secure
2021-Jul-31 18:05:05 [Thread #1] Download complete: dying_light_collectors_artbook.zip (@ 0.00kB/s)
2021-Jul-31 18:05:05 [Thread #1] Begin download: secure
2021-Jul-31 18:05:05 [Thread #0] Download complete: dying_dight_3D_printer_models.zip (@ 0.00kB/s)
2021-Jul-31 18:05:05 [Thread #0] Begin download: secure
2021-Jul-31 18:05:06 [Thread #3] Retry 1/3: secure (HTTP response code said error) https://content-system.gog.com/products/1448452156/users/46989135497749423/namespaces/website/download?path=%2Fsecure&token=XXX&access_token=XXX
2021-Jul-31 18:05:06 [Thread #0] Retry 1/3: secure (HTTP response code said error) https://content-system.gog.com/products/1448452156/users/46989135497749423/namespaces/website/download?path=%2Fsecure&token=XXX&access_token=XXX
2021-Jul-31 18:05:07 [Thread #1] Retry 1/3: secure (HTTP response code said error) https://content-system.gog.com/products/1448452156/users/46989135497749423/namespaces/website/download?path=%2Fsecure&token=XXX&access_token=XXX
2021-Jul-31 18:05:07 [Thread #2] Retry 1/3: secure (HTTP response code said error) https://content-system.gog.com/products/1448452156/users/46989135497749423/namespaces/website/download?path=%2Fsecure&token=XXX&access_token=XXX
2021-Jul-31 18:05:07 [Thread #3] Retry 2/3: secure (HTTP response code said error) https://content-system.gog.com/products/1448452156/users/46989135497749423/namespaces/website/download?path=%2Fsecure&token=XXX&access_token=XXX
2021-Jul-31 18:05:07 [Thread #0] Retry 2/3: secure (HTTP response code said error) https://content-system.gog.com/products/1448452156/users/46989135497749423/namespaces/website/download?path=%2Fsecure&token=XXX&access_token=XXX
2021-Jul-31 18:05:07 [Thread #2] Retry 2/3: secure (HTTP response code said error) https://content-system.gog.com/products/1448452156/users/46989135497749423/namespaces/website/download?path=%2Fsecure&token=XXX&access_token=XXX
2021-Jul-31 18:05:07 [Thread #3] Retry 3/3: secure (HTTP response code said error) https://content-system.gog.com/products/1448452156/users/46989135497749423/namespaces/website/download?path=%2Fsecure&token=XXX&access_token=XXX
2021-Jul-31 18:05:07 [Thread #1] Retry 2/3: secure (HTTP response code said error) https://content-system.gog.com/products/1448452156/users/46989135497749423/namespaces/website/download?path=%2Fsecure&token=XXX&access_token=XXX
2021-Jul-31 18:05:07 [Thread #3] Download complete (HTTP response code said error (503)): secure
2021-Jul-31 18:05:07 [Thread #2] Retry 3/3: secure (HTTP response code said error) https://content-system.gog.com/products/1448452156/users/46989135497749423/namespaces/website/download?path=%2Fsecure&token=XXX&access_token=XXX
2021-Jul-31 18:05:07 [Thread #3] Begin download: secure
terminate called after throwing an instance of 'boost::filesystem::filesystem_error' ▕                          ▏ 0.00/0.00MB @ 0.00kB/s ETA: 0s
  what():  boost::filesystem::file_size: No such file or directory: "/mnt/nas/non_backed_up/gog/games/dying_light_the_following_enhanced_edition/extras/secure"
Aborted

584fef3 and d307d22 should help with this issue

Thanks for the update.  I pulled the new code, but I am still having the issue.    When I do the command exactly as you have it, I get
$ ./lgogdownloader --game dying_light_the_following_enhanced_edition --include extras,dlcs --list-details
Getting game names (7/7) 48 / 48
Getting game info 1 / 1
gamename: dying_light_the_following_enhanced_edition
product id:<PHONE_NUMBER>
title: Dying Light: The Following – Enhanced Edition
icon: https://images-2.gog-statics.com/04513166345a92e2cf17a72d1b2bf62ec285051bd5e5d12a31e90ba15ea5a68e.png
extras:
	id: 84598
	name: wallpapers
	path: /dying_light_the_following_enhanced_edition/dying_light_wallpaper_pack.zip
	size: 26214400

	id: 84601
	name: novella
	path: /dying_light_the_following_enhanced_edition/dying_light_novel.zip
	size: 4194304

	id: 84607
	name: soundtrack (MP3)
	path: /dying_light_the_following_enhanced_edition/dying_light_original_soundtrack.zip
	size: 165675008

	id: 65713
	name: posters
	path: /dying_light_the_following_enhanced_edition/dying_light_tf_posters.zip
	size: 56623104

	id: 65733
	name: monster artworks
	path: /dying_light_the_following_enhanced_edition/dying_light_tf_enemy_artworks.zip
	size: 65011712

	id: 65743
	name: character artworks
	path: /dying_light_the_following_enhanced_edition/dying_light_tf_character_artworks.zip
	size: 80740352

	id: 84604
	name: artbook
	path: /dying_light_the_following_enhanced_edition/dying_light_collectors_artbook.zip
	size: 14680064

	id: 84610
	name: 3D printer models
	path: /dying_light_the_following_enhanced_edition/dying_dight_3D_printer_models.zip
	size: 73400320

And of course, when I try downloading it without the --use-cache option (which I had used before), it works fine.  So, it looks like your updates fixed it after all!

I forgot to mention to run --update-cache if using --use-cache
It looks like the issue is caused by those dlcs that are listed as regular extras for some reason
API shows those to have "count" and "total_size" of 0
https://api.gog.com/products/1448452156?expand=downloads
{
    "id": 88891,
    "name": "Crash Test Skin Pack",
    "type": "game add-ons",
    "count": 0,
    "total_size": 0,
    "files": [
        {
            "id": 88891,
            "size": 0,
            "downlink": "https://api.gog.com/products/1448452156/downlink/product_bonus/88891"
        }
    ]
},
{
    "id": 88945,
    "name": "Dying Light: The Following DLC",
    "type": "game add-ons",
    "count": 0,
    "total_size": 0,
    "files": [
        {
            "id": 88945,
            "size": 0,
            "downlink": "https://api.gog.com/products/1448452156/downlink/product_bonus/88945"
        }
    ]
},
{
    "id": 88948,
    "name": "Dying Light: Bozak Horde DLC",
    "type": "game add-ons",
    "count": 0,
    "total_size": 0,
    "files": [
        {
            "id": 88948,
            "size": 0,
            "downlink": "https://api.gog.com/products/1448452156/downlink/product_bonus/88948"
        }
    ]
},
{
    "id": 88951,
    "name": "Cuisine & Cargo DLC",
    "type": "game add-ons",
    "count": 0,
    "total_size": 0,
    "files": [
        {
            "id": 88951,
            "size": 0,
            "downlink": "https://api.gog.com/products/1448452156/downlink/product_bonus/88951"
        }
    ]
},
{
    "id": 88954,
    "name": "Ultimate Survivor Bundle DLC",
    "type": "game add-ons",
    "count": 0,
    "total_size": 0,
    "files": [
        {
            "id": 88954,
            "size": 0,
            "downlink": "https://api.gog.com/products/1448452156/downlink/product_bonus/88954"
        }
    ]
}

Is it possible to download those from account page using the browser?

These DLCs show up under "Extras" on the account page, but they are not links and cannot be downloaded.  I'm guessing they did this just to show that these DLCs are included in this edition.
EXTRAS
wallpapers (9)25 MB
novella 4 MB
soundtrack (MP3) 158 MB
posters (5)54 MB
monster artworks (9)62 MB
character artworks (7)77 MB
artbook 14 MB
3D printer models (3)70 MB
Crash Test Skin Pack
Dying Light: The Following DLC
Dying Light: Bozak Horde DLC
Cuisine & Cargo DLC
Ultimate Survivor Bundle DLC

They do show up for download in the Galaxy client, but the download fails with a "server problem".

209d831 makes the downloader skip files with "count" and "total_size" of zero
I don't understand why GOG lists these separately but then again GOG has never been very logical with their API responses.
All games that I own which have DLC don't list the included DLCs as normal extras just to inform the user about them.
Apparently GOG Galaxy dev team doesn't know about this odd API usage because Galaxy fails with server problem on them.

I can confirm that this works and no longer tries to download the "secure" files.


fix: generated wire file to be compatible with workspaces

Fixes #403
Problem
After trying to run wire ./... on a module inside of a go workspace subsequent calls to go generate ./... fail
go: -mod may only be set to readonly or vendor when in workspace mode, but it is set to "mod"
        Remove the -mod flag to use the default readonly value,
        or set GOWORK=off to disable workspace mode.
internal/app/wire_gen.go:3: running "go": exit status 1

This is because the wire_gen.go files contain the following generate command (see #403 for more details)
// go:generate go run -mod=mod github.com/google/wire/cmd/wire

Solution
This fix adds a flag to the compiled binary to allow this flag to be either unset or overridden with a different value.
For example running this command:
wire gen -mod=readonly ./...

Would generate the following wire_gen.go file
// Code generated byWire. DO NOT EDIT.

//go:generate go run -mod=readonly github.com/google/wire/cmd/wire
//go:build !wireinject

// .. rest of the code ..

Calling wire gen -mod=unset ./... would remove the flag in the generated file all together and calling without the flag (i.e. wire gen ./...) will default to the current behavior of setting -mod=mod.

I'm realizing that this fix works until you run go generate ./... and then the issue comes back because the added flag needs to be present in the generate command in the file's header. So for this solution to work it'll need to play nice with the existing -tag flag.
For example:
// go:generate go run github.com/google/wire gen -mod=readonly


_yaml.pyx: disallow duplicate keys in yaml mappings

The current behaviour is to silently keep the latst one which is obviously wrong.
ruamel-yaml as used in the round-tripping code also raises an error (at least in the current version)

If I understand correctly, this will improve correctness by raising an error when bst loads redundant dict keys such as:
mydict:
  foo: Pony
  bar: Horsy
  foo: Zebry

And the update to the test case is required because we're otherwise using our yaml parsing to parse "variables" dictionaries of multiple elements which would cause this error to be raised.
If my understanding is correct, then this looks good to me @abderrahim please feel free to merge :)

Isn't this going to cause currently working but badly constructed projects to start failing to load?
Would that not make it a braking change?
Wouldn't this ether need to be a configurable failure or a bump to bst3?
Ps I agree this is obviously behaviour we want to call out to our users and generally fail on

This was supposed to be BuildStream 2 behaviour. BuildStream 1 warned about this and stated it's going to start failing.

At minimum bring the warnings back.

This was supposed to be BuildStream 2 behaviour. BuildStream 1 warned about this and stated it's going to start failing.

Except it wasn't :). Using buildstream 1, you could get either no warning, a warning or an error depending on the version of ruaml-yaml that you're using.
This is why I think it is reasonable to merge this even though it used to "work": depending on the version of a dependency it could work or not.


When Announcement received, it only response audio and doesn't have display card

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:

For test case 601, the expected result should show display card on GUI device but it doesn't show on Smart Screen SDK.
What is the expected behavior?

Show Announcement display card and response.
What behavior are you observing?

Only response annoucement
Provide the steps to reproduce the issue, if applicable:

Raspberry Pi / Alexa App / Echo Show use same account.
Raspberry Pi is online and announcement support.
Use Alexa App or other echo show to make an announcement.
(Raspberry Pi will receive announcement to response)

Tell us about your environment:

What version of the AVS Device SDK are you using?
  <1.21.0>

Tell us what hardware you're using:

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

Tell us about your OS (Type & version):

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

Have you tried the same use case with AVS Device SDK SampleApp?

[ ] The issue is not applicable to the AVS Device SDK SampleApp.
[x] The issue is not reproducible on the AVS Device SDK SampleApp.

Hi @oscar1372,
Announcements are currently supported as an audio-only experience on Alexa Smart Screen SDK. So the display card is not supported.
We have noted your interest for this functionality and are continuously working on improving the Smart Screen SDK, however we cannot comment on when a specific feature may be available.
Thanks a lot for reaching out and contributing to Alexa Smart Screen SDK.

Hi @oscar1372,
Announcements are currently supported as an audio-only experience on Alexa Smart Screen SDK. So the display card is not supported.
We have noted your interest for this functionality and are continuously working on improving the Smart Screen SDK, however we cannot comment on when a specific feature may be available.
Thanks a lot for reaching out and contributing to Alexa Smart Screen SDK.

@VaruPan Thanks your response. Yes, I am checking the test case of functional self-test checklist and found it needs to show display card on GUI device(TV).
Could I know whether certification will be impact when SDK only support audio-only experience?

@VaruPan Thanks your response. Yes, I am checking the test case of functional self-test checklist and found it needs to show display card on GUI device(TV).
Could I know whether certification will be impact when SDK only support audio-only experience?

You can reach out to the certification team to get more information on waivers for unavailable UX.

You can reach out to the certification team to get more information on waivers for unavailable UX.


Add fr-FR

I translate after

Will look into this when I'm home so I can properly merge the different PR's together. :)
Thank you so much so far for the help with translating the app! 😊

It has been added. Again thank you so much for translating the app! 😊

@FJduFou Hmmm, seems like the resource file for FR-fr still only contains the English strings.
Do you happen to have a file with the raw translations still with you? If so, can you send them to me, then I'll add them manually. ;)

I preferred to do it in 2 steps,
the 1st was the integration of Language Toolkit (refuse)
the 2nd was the translation (in progress)

All right, feel free to do a PR with all the changes in it when it's ready. :) That way the PR will include all changes you've made (as multiple seperate PR's make it crazy hard for me to see which ones have the most current changes. ;) )

I did not know how to put multiple files in one PR

If you work in your fork you can create commits to your own repo so you can still work incremental. Once you're done, you can click on "New Pull Request" on this repository. GitHub will then automatically select your main branch (you can also select a different one) that you want to merge with my repo.
If you do that the Pull Request will automatically include all changes you've made and synced with your fork on GutHub. 😊

oki, thx 😅


JS engine giveing me an error, and everytime i delete that said script, another shows up!

Describe your bug here. If you are modding, try testing your bug in a clean version of the engine instead. Also, if you're using an older version of JSE, please try the latest version/action build. Also, be sure to check the pinned 'JS Engine: Known Issues' issue, to check if your issue hasn't already been found!
it keeps giving me this on EVERY song
Command Prompt/Terminal/Crash logs (if existing)
No response
Have you identified any steps to reproduce the bug? If so, please describe them below in as much detail as possible. Use images if possible.
no
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
No
If you use 1.12.0 or earlier, did you have Optimized Chart Loading turned on?
No
Did you check for any similar issues to what you're reporting? Check, then come back here. If there is a similar issue, then do not report the issue, otherwise it will be marked as a duplicate.
No

and crashes

well
can you send the crash log?

Lua issue, either remove it or I'll fix it (not the haxe one)

dude
the log of the crash
the txt when the game crashes

something like that pops up

had to search up an fnf error example, not trying to make one right now

it doesnt do that. it just closes

look through every script of the song's data and look for "luaDebugMode = true;"
if that's there, get rid of that line
the txt from it is probably making the game crash


[Doc] Gluon Block/HybridBlock/SymbolBlock appears at the wrong place in the API doc

Description
Gluon Block, HybridBlock, SymbolBlock has an empty doc in the API doc. For example: https://mxnet.apache.org/api/python/docs/api/gluon/block.html
Their actual docs appear under gluon.nn domain, which IMO is a wrong place for them. For example: https://mxnet.apache.org/api/python/docs/api/gluon/nn/index.html#mxnet.gluon.nn.Block
@ys2843

Investigating, this PR #18412 import the website issue.

This should be due to missing use of __all__ specifier in the gluon.nn namespace.
https://github.com/apache/incubator-mxnet/blob/beafba76395e75c093f99d20ac62e38f48e91012/python/mxnet/gluon/nn/__init__.py#L22
imports the Block etc into the gluon.nn namespace and now it might be undefined behavior if Sphinx will show the Block doc as part of gluon.nn or gluon namespace.
Suggest to fix the all usage and improve the website broken link checker to avoid such bugs in the future
Please see https://stackoverflow.com/questions/44834/can-someone-explain-all-in-python

@leezu - Should we revert the PR ( https://github.com/apache/incubator-mxnet/pull/18413 ) if we are unable to fix the broken website issue quickly. Ideally this should have been caught before the PR was merged. We shall work on it as you suggested above to have broken link checker as part of the PR build. But, given currently Python APIs are broken, I prefer we revert and merge back with the fix.
What do you think?

I suggest we focus on ensuring our users see the stable API docs, given that most users don't use MXNet 2 at this point anyways. This PR has exposed some bugs in the Sphinx setup which need to be fixed before the release; but this is an issue with the website generation script and shouldn't delay the feature development. What do you think @sandeep-krishnamurthy

WARNING: autodoc: failed to import module 'executor' from module 'mxnet'; the following exception was raised:
No module named 'scipy'
from the log
https://github.com/apache/incubator-mxnet/commit/b4b8b805fe94a6df905c6eae7f6c1f83cfea9b73 introduces the scipy import


⚡ Add timestamp to webhook

What problem does your feature request solve?
It's useful to store timestamp of each message (i.e. the same timestamp that you would see in the WhatsApp web UI/mobile app on each message)
Describe the solution you are proposing.
Add the timestamp to the webhook payload
https://github.com/aldinokemal/go-whatsapp-web-multidevice/blob/b15afdc291a73f2f562ab999f8449218d6b6b8a9/src/pkg/whatsapp/whatsapp.go#L293-L312
Describe alternatives you have considered.
I could use the timestamp of when the webhook event is received as a proxy for the timestamp of the message itself, but this can be inaccurate especially with higher volume of events (or for example if webhooks are being handled in a task queue)
Importance
Nice to Have
Additional Context

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

https://github.com/aldinokemal/go-whatsapp-web-multidevice/pull/221


Maniacal-Moths

The Final App

No merge issues.
No flake8 linting errors.
Note for reviewer: This project was made as a solo effort by The Joker (hot9cups) after the other team members dropped out.

ok code quality. looks a bit short. did the team fall apart during the jam?

I made the project alone.

ok code quality. looks a bit short. did the team fall apart during the jam?

@eivl
I made the project alone.

No way. That is impressive.

ok code quality. looks a bit short. did the team fall apart during the jam?

@eivl
I made the project alone.

No way. That is impressive.

Hehe, thank you. That was indeed a very testing and challenging period of 10 days.


Firefox 121 is shipping text-indent values each-line & hanging

https://twitter.com/intenttoship/status/1715352912623194488
https://groups.google.com/a/mozilla.org/g/dev-platform/c/z6PaiICBCRg/m/w171E3_DAAAJ

As of Firefox 121, I intend to implement the hanging and each-line
keywords for the text-indent CSS property.

Also tried to find a support bug for Chromium, but couldn't find any :o

Thanks!


Advanced Particles Samples

The following legacy DirectX SDK samples were written for Direct3D 10 / FX10 and demonstrate various particle techniques. They should be ported to Direct3D 11, perhaps using FX11, for reference:

AdvancedParticles
DeferredParticles
GPUBoids
SoftParticles

The Direct3D 10 versions can be found on directx-sdk-legacy-samples.


Add missing AML CLI v2 release notes

Add missing AML CLI v2 release notes

@Blackmist
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


The info in the video appears to contradict the latency documentation below the video

Issue in ./help/ingestion/streaming-ingestion/overview.md
The video says that the identity stitching and RT customer profile is updated in less than a second. The documentation in the table below says that the latency for RT Customer Profile is < 15 minutes for P95.
The video says the max latency for ingestion into the data lake is 15 minutes but the table below the video says it could be up to 60 minutes.

Thank you for submitting this issue. We will review the documentation and make the necessary updates as quickly as possible. Tracking internally in PLAT-205497.


modelscope 执行lora失败

/mnt/workspace/facechain
Looking in indexes: https://mirrors.aliyun.com/pypi/simple
Generating train split: 1 examples [00:00, 278.06 examples/s]
02/28/2024 19:57:59 - INFO - main - ***** Running training *****
02/28/2024 19:57:59 - INFO - main -   Num examples = 1
02/28/2024 19:57:59 - INFO - main -   Num Epochs = 200
02/28/2024 19:57:59 - INFO - main -   Instantaneous batch size per device = 1
02/28/2024 19:57:59 - INFO - main -   Total train batch size (w. parallel, distributed & accumulation) = 1
02/28/2024 19:57:59 - INFO - main -   Gradient Accumulation steps = 1
02/28/2024 19:57:59 - INFO - main -   Total optimization steps = 200
2024-02-28 19:58:00,217 - modelscope - INFO - Use user-specified model revision: v1.0.0
Resuming from checkpoint /mnt/workspace/.cache/modelscope/damo/face_frombase_c4/face_frombase_c4.bin
Steps:   0%|                                            | 0/200 [00:00<?, ?it/s]/opt/conda/lib/python3.10/site-packages/diffusers/models/attention_processor.py:1871: FutureWarning: LoRAAttnProcessor is deprecated and will be removed in version 0.26.0. Make sure use AttnProcessor instead by settingLoRA layers to self.{to_q,to_k,to_v,to_out[0]}.lora_layer respectively. This will be done automatically when using LoraLoaderMixin.load_lora_weights
deprecate(
Traceback (most recent call last):
File "/mnt/workspace/facechain/facechain/train_text_to_image_lora.py", line 1224, in
main()
File "/mnt/workspace/facechain/facechain/train_text_to_image_lora.py", line 1036, in main
accelerator.backward(loss)
File "/opt/conda/lib/python3.10/site-packages/accelerate/accelerator.py", line 1964, in backward
loss.backward(**kwargs)
File "/opt/conda/lib/python3.10/site-packages/torch/_tensor.py", line 492, in backward
torch.autograd.backward(
File "/opt/conda/lib/python3.10/site-packages/torch/autograd/init.py", line 251, in backward
Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass
RuntimeError: element 0 of tensors does not require grad and does not have a grad_fn
Steps:   0%|                                            | 0/200 [00:00<?, ?it/s]
Traceback (most recent call last):
File "/opt/conda/bin/accelerate", line 8, in
sys.exit(main())
File "/opt/conda/lib/python3.10/site-packages/accelerate/commands/accelerate_cli.py", line 47, in main
args.func(args)
File "/opt/conda/lib/python3.10/site-packages/accelerate/commands/launch.py", line 1023, in launch_command
simple_launcher(args)
File "/opt/conda/lib/python3.10/site-packages/accelerate/commands/launch.py", line 643, in simple_launcher
raise subprocess.CalledProcessError(returncode=process.returncode, cmd=cmd)
subprocess.CalledProcessError: Command '['/opt/conda/bin/python', '/mnt/workspace/facechain/facechain/train_text_to_image_lora.py', '--pretrained_model_name_or_path=ly261666/cv_portrait_model', '--revision=v2.0', '--sub_path=film/film', '--output_dataset_name=/mnt/workspace/facechain/worker_data/qw/training_data/ly261666/cv_portrait_model/person1', '--caption_column=text', '--resolution=512', '--random_flip', '--train_batch_size=1', '--num_train_epochs=200', '--checkpointing_steps=5000', '--learning_rate=1.5e-04', '--lr_scheduler=cosine', '--lr_warmup_steps=0', '--seed=42', '--output_dir=/mnt/workspace/facechain/worker_data/qw/ly261666/cv_portrait_model/person1', '--lora_r=4', '--lora_alpha=32', '--lora_text_encoder_r=32', '--lora_text_encoder_alpha=32', '--resume_from_checkpoint=fromfacecommon']' returned non-zero exit status 1.
Traceback (most recent call last):
File "/opt/conda/lib/python3.10/site-packages/gradio/queueing.py", line 407, in call_prediction
output = await route_utils.call_process_api(
File "/opt/conda/lib/python3.10/site-packages/gradio/route_utils.py", line 226, in call_process_api
output = await app.get_blocks().process_api(
File "/opt/conda/lib/python3.10/site-packages/gradio/blocks.py", line 1550, in process_api
result = await self.call_function(
File "/opt/conda/lib/python3.10/site-packages/gradio/blocks.py", line 1185, in call_function
prediction = await anyio.to_thread.run_sync(
File "/opt/conda/lib/python3.10/site-packages/anyio/to_thread.py", line 56, in run_sync
return await get_async_backend().run_sync_in_worker_thread(
File "/opt/conda/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 2134, in run_sync_in_worker_thread
return await future
File "/opt/conda/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 851, in run
result = context.run(func, *args)
File "/opt/conda/lib/python3.10/site-packages/gradio/utils.py", line 661, in wrapper
response = f(*args, **kwargs)
File "/mnt/workspace/facechain/app.py", line 804, in run
train_lora_fn(base_model_path=base_model_path,
File "/mnt/workspace/facechain/app.py", line 207, in train_lora_fn
raise gr.Error("训练失败 (Training failed)")
gradio.exceptions.Error: '训练失败 (Training failed)'

Hi, did you figure this out: RuntimeError: element 0 of tensors does not require grad and does not have a grad_fn?

可以参考https://github.com/modelscope/facechain/issues/527
需要加一段代码

please try out the newest train-free, 10s inference version facechain-fact.


Status of Quaxtrip

Hi Damon,
What exactly is the status of Quaxtrip? Are you still working on it? I want to pickup up where I left off a few years ago, and begin integrating the essence of your work into my Telematic Theater project.
I am particularly interested in a VST or Max for Live version for routing audio in and out of Ableton Live, and perhaps an updated interface to make it super easy for performers who don't tend to be as technically savvy.
Look forward to hearing from you.
All the best, Randall

I do have one small update that’s just waiting on documentation to release (it adds recording capabilities), but other than that I don’t currently have any other plans for Quaxtrip
I don’t own Live, so I have no plans for a Max4Live device, but I imagine it would pretty simple for someone who wanted to do so. Probably mostly just a matter of refactoring the interface to fit it in the allotted space.
Miller has made a VST version of Quacktrip:
https://msp.ucsd.edu/tools/quacktrip/
I not sure what could be stripped away from the interface to make it easier to use, everything seems pretty necessary. I’m open to suggestions.


feat(core): [LW-9409] create Find Your Shared Wallet component

Checklist

[x] JIRA tickets: https://input-output.atlassian.net/browse/LW-9409 , https://input-output.atlassian.net/browse/LW-9521
[x] Screenshots added.

File upload component
Added a new UI component for file upload:
 <FileUpload
          label={[
            { text: 'Drag & drop or', highlight: false },
            { text: 'choose file', highlight: true },
            { text: 'to upload', highlight: false },
          ]}
          removeButtonLabel='Remove'
          supportedFormats='Supported formats: JSON'
          accept="application/json"
          onChange={handleFileChange}
          files={file ? [file.name] : undefined}
        />

Screenshots

Changes unknown
when pulling<PHONE_NUMBER>e701bef791441824fb42353b243f0f on lw-9409-find-your-wallet
into ** on LW-9408-all-set**.

cc @input-output-hk/lace-tech-leads


policy: Handle empty L7Rules in ToPorts

Consistently respect the API spec in handling an empty L7Rules
like a nil L7Rules.  Fix the merging and wildcarding of rules with
empty L7Rules.
Signed-off-by: Romain Lenglet<EMAIL_ADDRESS>

This change is

test-me-please

Alternatively, a simpler change would be to reject any rule with empty rules field. That would only require changing the validation and a bit of the API spec. That would be less surprising than the current behavior.
@tgraf what is your preference?

I assume you had a typo in your example as the "fromEndpoints: was using different labels.
I think I'm fine with the change after fully understanding it. Let me double check my understanding. Your change will cause the following:
                            "toPorts": [
                                {
                                    "ports": [
                                        {
                                            "port": "9092",
                                            "protocol": "TCP"
                                        }
                                    ],
                                    "rules": {}
                                }

to be handled identically to:
                            "toPorts": [
                                {
                                    "ports": [
                                        {
                                            "port": "9092",
                                            "protocol": "TCP"
                                        }
                                    ]
                                }

while the following will still have the old behavior:
                            "toPorts": [
                                {
                                    "ports": [
                                        {
                                            "port": "9092",
                                            "protocol": "TCP"
                                        }
                                    ],
                                    "rules": {
                                        "kafka": []
                                    }
                                }

Good point. My fix was breaking the old behavior with an empty Kafka list. I will fix that by changing the implementation of IsEmpty to:
func (rules *L7Rules) IsEmpty() bool {
	return rules == nil || (rules.HTTP == nil && rules.Kafka == nil)
}

test-me-please

Fixed L7Rules.IsEmpty to keep the semantics with empty non-nil HTTP or Kafka rule lists.

test-me-please


Make use of object initial values

71 lines removed in phase 0. A bunch of lines also removed in phase 1. Golang has such initial values baked into the language.

Internally debating this.
Do you plan to define initial values for each type somewhere?

Do you plan to define initial values for each type somewhere?

Yes, we can define initial values immediately after defining types. It's a one-liner: "Recursively initialize objects using 0 for "uintN", False for "bool", and [] for lists."

Close in favour of #963


DCR resource assignment and template content

In "step 4" under "Create a DCR for both Syslog and CEF logs" it says "use POST or PUT to deploy it". However, POST is not supported, PUT is the only method that can be used to deploy.
Under "Create a DCR for both Syslog and CEF logs" a "step 5" is necessary: assign the CEF/Syslog gateway as a resource to the DCR.
The request body template in "step 3" contains the following properties which are not required for the PUT method as they are set automatically:
properties/immutableId
id
name
etag
systemData
Leaving these out of the template makes the template less complex.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: c2b604a6-9b0d-ffb1-4d8b-cbf362cc9a01
Version Independent ID: b39a3da6-691c-b8da-17df-2db4fdfc1977
Content: Stream logs in both the CEF and Syslog format to Microsoft Sentinel
Content Source: articles/sentinel/connect-cef-syslog.md
Service: microsoft-sentinel
GitHub Login: @limwainstein
Microsoft Alias: lwainstein

@stephanwaelde
Thanks for your feedback! We will investigate and update as appropriate.

@stephanwaelde
Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can take a look at it accordingly

#reassign:yelevin

#label:"backlog-item-created"

@stephanwaelde,
Thanks for your feedback. This document has been updated and no longer contains any POST instructions or commands.
#please-close
cc: @ManoharLakkoju-MSFT @cwatson-cat @batamig


Image not being processed on /controlnet/txt2img endpoint

Until yesterday, our team was able to successfully send requests to the /controlnet/txt2img endpoint, including the image encoded in base64 format. However, today when we made the same request, the server is not taking the image into account and only the prompt is being processed. If we do the same via gradio ui it works ok.
We have ensured that we are sending the image in the correct format and have not made any changes to our request payload.
Please let us know if there have been any recent changes to the /controlnet/txt2img endpoint or if there is any additional information that we can provide to help diagnose the issue.

https://github.com/Mikubill/sd-webui-controlnet/issues/567


Update dimensions to be uint32_t in C++

What
Right now in C++ we have dimensions as size_t, uint64_t, and uint32_t in different places. In the metadata of created Python indexes I see dimensions is <class 'numpy.uint32'>, and that is also what the C++ metadata saves it as:
std::vector<metadata_arithmetic_check_type> metadata_arithmetic_checks{
      // name, member_variable, type, required
      {"dimensions", &dimensions_, TILEDB_UINT32, false},
      ...

So here we change all references of dimensions to be uint32_t in C++.
Alongside this we also change num_subspaces_ and sub_dimensions_ to uint32_t so that we can compute them using dimensions_ without casting. This is also a bug fix because previously we had them as:
src/include/index/ivf_pq_index.h
  uint64_t num_subspaces_{0};
  uint64_t sub_dimensions_{0};

But would store them as:
src/include/index/ivf_pq_group.h
  {"num_subspaces", &num_subspaces_, TILEDB_UINT32, true},
  {"sub_dimensions", &sub_dimensions_, TILEDB_UINT32, true},

In a follow-up we'll continue these updates with our variables that also have bugs, but we will split this up into separate PRs to be easier to review.
Testing
Existing tests pass.

Can we make this unit64_t consistently? The max uint32 value is ~4B which is close to our large scale datasets O(1B)

Done! One impact is that our old C++ metadata uses uint32, so we now fail to read it. So here we make this a breaking change (and delete the existing backwards compatibility indexes). This seems okay as I don't believe any customers use Vamana and we haven't made a public announcement about it. Another benefit is that it would let us delete the old Vamana backwards compatibility indexes which didn't have compression and so are quite big (~60MB instead of 100KB).
I also tested that we can still open up indexes generated in C++ in Python:
(TileDB-Vector-Search-2) ~/repo/TileDB-Vector-Search-2 python backwards-compatibility-data/generate_data.py 0.8.0
true
(TileDB-Vector-Search-2) ~/repo/TileDB-Vector-Search-2 pytest apis/python/test/test_backwards_compatibility.py -s

========================================== test session starts ==========================================
platform darwin -- Python 3.9.18, pytest-7.4.3, pluggy-1.3.0
rootdir: /Users/parismorgan/repo/TileDB-Vector-Search-2
plugins: nbmake-1.5.3, anyio-4.4.0
collected 1 item

apis/python/test/test_backwards_compatibility.py .

=========================================== 1 passed in 1.67s ===========================================


[DRAFT] Import script overhual

Overhauls the import script to account for changes from #223
Still pretty rough, needs a bit more work to get the edge cases dialed in

Moved to #225


Fix #85 Add trailing whitespace as plugin.

I remove the alias of s to remove whitespaces because this is not in README.md but if you want create at just put s to :FixWhitespace.
Sorry for the english but google translate help me in this adventure hehe

@hmleal nice. We can define another mapping for the :FixWhitespace command