feat(checkbox)!: migrate checkbox component to core tokens (CSS-99)

Description

This PR migrates the Checkbox component and styles to use core-tokens and includes:

Create spectrum and express theme styles
Moving skin.css styles to index.css
Updating the HTML examples and component description
Update Windows high contrast mode styles
Add locale-specific styles

How and where has this been tested?

How this was tested:

Tested locally referencing the Components batch XD file
Tested with VoiceOver on Safari
Tested  WHCM with forced colors Chrome Emulation
Tested locale-specific styles by manually adding a locale attribute

Browser(s) and OS(s) this was tested with:

Chrome on macOS
Safari on macOS

Screenshots

To-do list

- [ ] If my change impacts other components, I have tested to make sure they don't break.

[x] If my change impacts documentation, I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.

[ ] Windows high contrast mode styles make sense.
[ ] Spectrum theme-specific styles match design
[ ] Express theme-specific styles match design
[ ] --spectrum-checkbox-CJK-line-height is applied correctly.
Test by adding lang attribute to a .spectrom-Checkbox-label element or the html element e.g. lang="ko".
[ ] This pull request is ready to merge.

Visual regression tests after running them locally.
We're already asking about the invalid text color change. The only other change is that the default checkbox border color has changed slightly, which is why we see those failures called out in the actual checkbox page as well as in a few other components. All of these changes may be expected and ok, but let's wait on the word from design.

Released beta:
-<EMAIL_ADDRESS>

Released another beta version due to a faulty build:
-<EMAIL_ADDRESS>

@yosevu - sorry to resurrect this PR, but we found a bug when we tried to integrate the beta with the Spectrum Web Components team.
The issue is with the t-shirt sized versions of the indeterminate state. You can reproduce locally by adding t-shirt size examples for the indeterminate state and noticing that the dash's position is incorrect at (at least) the small and medium sizes.

It looks like we just may have missed the tokens for these. They're in the Xd file:

Hopefully, that will fix this issue!

@pfulton Oops, I didn't think of testing indeterminate t-shirt sizes checkboxes since there weren't examples in the YAML file.  I'll add some examples and work on fixing this. The tokens are added correctly, but I think the spacing needs to be calculated differently for the t-shirt sizes.

VRT test is
2022-08-10 -- 1465 - checkbox.zip

@pfulton Oops, I didn't think of testing indeterminate t-shirt sizes checkboxes since there weren't examples in the YAML file. I'll add some examples and work on fixing this. The tokens are added correctly, but I think the spacing needs to be calculated differently for the t-shirt sizes.
Updated. Switched to centering the icons with flexbox rather than position and margin.

Awesome. Thanks for taking care of this!

Released:
4.0.0-beta.3


upgrade level from 6.0.1 to 8.0.0 for m1 mac compatibility

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
This is a fix for compatibility with m1 mac

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

<EMAIL_ADDRESS>compile failed. it is dependency of<EMAIL_ADDRESS>

What is the new behavior (if this is a feature change)?
The library compile successfully with m1 mac.

Other information:
<EMAIL_ADDRESS>upgrade guide: https://github.com/Level/level/blob/v8.0.0/UPGRADING.md
Support of Node.js 10 has been dropped

This change is

added in<EMAIL_ADDRESS>


Split text chapter files into biographies

For https://github.com/usaybia/srophe-eXist-app/issues/57

Done experimentally for ch. 12 at https://github.com/usaybia/usaybia-data/tree/nathangibson/issue116/data/texts/tei


fix link to those in master branch

since there is no master, those links are broken

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


Persistency in cookies

Would there be interest in implementing a solution, which would allow for the persistent store to save to cookies instead of local or session storage? I need this functionality in my own codebase (and would imagine I'm not the only) and I'm considering whether I should write some local code or write a PR for this project instead
Edit: Obviously, this would require a little more complexity, as we can just use the standard storage interface, but I think it should be doable by writing a custom interface to cover both storage and cookies

Hi @bertmad3400,
Yes, it is something I am considering.
I built a prototype: https://github.com/joshnuss/sk-cookie-store-experiment
The questions up in the air are:

Should it all be part of the same package?
Should it support SvelteKit too? (my experiment covers that)
Should there be separate "adapters" or factor functions for create a cookie, session storage and local storage store.  Great to se you already have a prototype working. To hopefully come a little closer to some answers, here is my thoughts on the concept:

From the perspective of an app developer, I absolutely think it makes the most sense for it to be part of the same package. As a developer not working on the library, but on my svelte application, I don't care that the underlying API's (storage and cookie API) are different, I just care about that the store has a persistency mechanism. This would also allow to use the same interfaces for things like serialization
With that said, to keep code complexity minimal, I think we should create a different object factory for cookies. Not only does it need other options as you mention, but I would imagine the usecase to be quite different (I often initiate localStorage stores from static application code, but would probably initiate a cookie store from load functions to ensure it can read the cookie server-side to enable SSR with the information)
I'm not a 100% sure what you mean when you ask whether it should support sveltekit? I assume you hint to the fact that the code you have written in the prototype uses AsyncLocalStorage to also work server-side, in which case I would argue that, no, this doesn't actually make sense. If I would want to use this cookie server-side, it would be to allow for data in the store to be used for SSR, in which case the implementation in the prototype doesn't solve this, as it can't read the cookies from the incoming request. What I would propose would be to implement a clientside only cookie store, and then initialize it from the load functions using the sveltekit cookie object to fetch initial value if one wants to use it for SSR.

Thanks, that makes sense.
To clarify on your last point:

If I would want to use this cookie server-side, it would be to allow for data in the store to be used for SSR, in which case the implementation in the prototype doesn't solve this, as it can't read the cookies from the incoming request

The proposed change would support reading cookies from the incoming request. It accomplishes this by using a server-side hook to extract the cookies from the incoming request.
See: https://github.com/joshnuss/sk-cookie-store-experiment/blob/main/src/hooks.server.js

Oh damn, that's smart! I missed that part of your prototype. On the one hand, I usually don't like this, as it "hides" the event flow from the user and adds a few more moving parts, but on the other hand, it feels like a very svelty way of doing things, and I DX wise, this seems to me as the right move. The only concern I have are the following:

Is there a possibility of the store getting initiated, and the server then reading the response, leaving the cookie without the cookie value as the server-side storage isn't re-actively linked to the store?
This would make this library a SvelteKit only project. Personally I think this is a reasonable compromise, as most people build Svelte projects with Kit, but if you disagree, it would of course be possible to integrate a cookie store that only works client side or from load functions into the project, and then built an extension that works natively with SvelteKit.

Do you want to have a go at this, or should I write a PR?

Is there a possibility of the store getting initiated, and the server then reading the response, leaving the cookie without the cookie value as the server-side storage isn't re-actively linked to the store?

Not sure, but it's a good point about consistency between the store and request. Would have to test it.
Also, what happens if a handler writes a new cookie value, will the store be updated?

This would make this library a SvelteKit only project.

I think it could be built in a way that it doesn't depend on SvelteKit. The hooks part would be optional. People not using SvelteKit wouldn't import it and it would be tree-shaken.

Do you want to have a go at this, or should I write a PR?

If you have time, feel free to open a PR!

I ended up never finishing this, see https://github.com/joshnuss/svelte-persisted-store/pull/213 for explanation.


cask-repair: fix download file path is not retrieved correctly

Fixes https://github.com/vitorgalvao/tiny-scripts/issues/196
brew cask fetch returns color output which causes sed not to strip the redundant text correctly in certain environment (specifically, in my case, GitHub Actions). This fixes the bug by simply setting brew cask fetch to return the plain text output (Ref: https://github.com/Homebrew/brew/pull/3090/files).

Thank you.


YNAB Now Supports Apple Card

Just in the nick of time! YNAB finally allows syncing of the Apple card. I've really appreciated the effort that went into making ynam @snowskeleton. Glad to see your project held us over until YNAB and Apple allowed syncing rather than just Mint...or now Credit Karma.
https://www.ynab.com/blog/ynab-apple-wallet

This is great news! Good to see Apple is finally playing nice with people. Thanks for sharing! Now I'm off to install the update :D


fileHandle.remove is not a function

Can't delete file.

The remove() method is supported in Chromium 110. Please upgrade your browser to this version. Since OPFS Explorer is a bleeding edge extension and the missing method is shipping anyway, the team decided to not offer a workaround for older versions.


bug in Responsiveness of user input page

bug in Responsiveness of user input page

@ankitapuri please assign me this issue


Oscars data?

Any chance you could upload the oscars data you've used in the past? or the script that was used to generate it?

@nickresnick do you know what the columns are in this dataset ?

@cristianounix no idea. I just haven't come across a good oscars dataset and given 538's predictions in the past, thought maybe they'd have something stored away.

There is a similar data set from Iain Pardoe available here:
https://github.com/tjmahr/GelmanHill/blob/master/datasets/academy.awards/
Data is available up to 2006.
There is a related article:
Applying discrete choice models to predict Academy
Award winners
Hope this helps.


Added links to manage Collections with PowerShell

#MMS2019Docathon

@ChrisKibble : Thanks for your contribution! The author, @aczechowski, has been notified to review your proposed change.

Thanks @ChrisKibble for the contribution! I'll review after the end of the contest.
#hold-off
(reviewers, please don't edit - I'll take care of it.)

@ChrisKibble : Thanks for your contribution! The author, @aczechowski, has been notified to review your proposed change.

Remove locale (en-us/) from all of the URLs

Hi @aczechowski - all set.

#sign-off
Once merged, this should be live with the next daily publishing process. Right now that should be tomorrow (Wednesday, 15 May) around 11:00 Pacific time. No further action needed from you.


improved unused temp files deletion

The idea is to delete cache files, that are currently not used by the running processes.
psutil lib was added to the requirements.txt in order to look at the running processes ids.
Special integration test was created and it can be found at here.

Нужно додумать тест, чтобы он входил в ситуации из соответствующего issue

Под виндой получил такую ошибку на примере api_classification:


product version logging and error handling

What does this PR do?
Add additional logging and error handling
Motivation
https://datadoghq.atlassian.net/browse/WINA-674
better logging/error message for when  MsiGetProductInfo fails, e.g. in rare case when two products are stuck/installed simultaneously
Error of MsiGetProductInfo was ignored so GetVersionString was returning an uninitialized buffer string, which Version.Version of course failed to parse.
Describe how to test/QA your changes
E2E tests cover happy paths, details unknown for rare case mentioned above
Possible Drawbacks / Trade-offs
Additional Notes

Example error when MsiGetProductInfo fails
CA: 17:53:00: ReadInstallState. Error reading install state: System.Exception: Failed to get version string for product {5071E877-08D6-4B59-8A3E-E9E87B451111} ---> System.ComponentModel.Win32Exception: Unknown property

/merge


feat(tapd): add proxy to forward api to tapd

Summary
Requests with path/plugins/tapd/connections/:connectionId/proxy/*path would route to api.Proxy handler
for example:
Request to http://your_devlake_host/plugins/tapd/connections/1/proxy/rest/story_categories?workspace=1
would forward to
https://api.tapd.cn/story_categories?workspace=1

Does this close any open issues?
closes #3194
Screenshots
Include any relevant screenshots here.
Other Information
Any other information that is important to this PR.

Can you provide some screenshots? thanks

Can you provide some screenshots? thanks

I used a screenshot of api response, please have a check

Please update the swagger document as well, thanks

Please update the swagger document as well, thanks

Hmm, the body of response and request will be different according to different tapd api, so if anyone want to use this api, they have to check https://www.tapd.cn/help/show#1120003271001000057 for detail


config: Use toml to store repo info. Bug fixes.

Fixes #6. Part fix for #2 (provides the data for client to use the hex in css)

Done @harshavardhana. Incorporated all the feedback.


generator-superset plugin uses deprecated and out of sync packages with the rest of Superset

Bug description
The generator-superset plugin for creating custom data visualization plugins utilizes the superset-ui version of chart-controls and core, but these are now 3 years out of date with main. Are there current versions of these packages that can be swapped out in place of them? Otherwise we would need some to be made available in order to be able to continue making custom visualizations that don't fall out of sync with the rest of Superset.
https://github.com/apache/superset/blob/master/superset-frontend/packages/generator-superset/generators/plugin-chart/templates/package.erb#L32-L33
  "peerDependencies": {
    "@airbnb/config-babel": "^2.0.1",
    "@superset-ui/chart-controls": "*",
    "@superset-ui/core": "*",
    "react": "^16.13.1"
  },

How to reproduce the bug

Run the generator-superset plugin
View the versions of @superset-ui/chart-controls and @superset-ui/core that are installed
Both are derived from the archived superset-ui repo

Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist

[x] I have searched Superset docs and Slack and didn't find a solution to my problem.
[x] I have searched the GitHub issue tracker and didn't find a similar bug report.
[x] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

Hi @wsoeltz. Were you able to find a fix for this issue?

Hi @wsoeltz. Were you able to find a fix for this issue?

No, we ended up having to fork Superset and build our chart package inside the monorepo


RevComp on Slice

Is there a reason there's no RevComp on alphabet.Slice?

An alphabet can be any set of letters. Not all letters have complementarity, e.g. amino acids.

That makes sense (I'm a software engineer, new to bio). Sorry I didn't see a mailing list or other place to ask for help.
Here's what I'm trying to do, maybe you can point me in a good direction–
I have a number of DNA Seq's for which I need to pull out slices based on a pattern. I need to match that pattern in both directions and then emit them all in the forward direction.
I was trying to do this with Slice, but then I end up not being able to RevComp them. Is building my own RevComp for alphabet.Letters the best way to do this?

Use linear.Seq or linear.QSeq depending on whether they have quality information. Use segio/fasta or seqio/fastq to read them in.


componentWillReceiveProps is deprecating

Describe the bug
componentWillReceiveProps is deprecating.
Screenshots

Thanks for reporting it.
Just published version 1.0.23. Should have fixed it there.


Updated IntersectionObserver Firefox information

According to https://developer.mozilla.org/en-US/docs/Web/API/IntersectionObserver
the flag is dropped with version 55.

Thanks!

Thank you for providing this service. The least i can do is contributing if i find an error :)


Spin: Update documentation to indicate to update the templates upon spin upgrade

Please see:
https://github.com/fermyon/spin/issues/615#issuecomment-1376073184
https://github.com/fermyon/spin/issues/615#issuecomment-1376125638
related to: https://github.com/fermyon/spin/issues/990

(Moved to fermyon/developer where Spin docs are currently tracked.)


Native read timeout

Perform timeouts via native handlers.

@violetagg or @smaldini thoughts?

@tony-clarke-amdocs This had been attempted previously but it introduced some bugs.  It seems like those no longer exist.
I had hoped that this would help with some of the memory leaks we are seeing but that does not appear to be the case.
When load testing this previously, one of the performance hotspots was the timeout in the routing filter.  This change seems to confirm that as I am getting higher throughput in my load testing.


Add support for PubKey into PubKeyHash conversion on-chain

Describe the feature you'd like
Tx signatures only can be checked using PubKeyHash.
But datum signatures only can be checked using PubKey.
So naturally we would use PubKey to check both of them, but we cannot find a way to convert it to PubKeyHash on-chain.
Describe alternatives you've considered
For now we including the pair of PubKey and its hash, and rely on off-chain code to check that they do match.
This hack is described in our spec:
https://github.com/mlabs-haskell/hydra-auction/blob/staging/doc/on_chain_spec.md#parameters-and-state

@michaelpj could you please take a look at this one?

Unfortunately, Michael is going to be on leave for a while. I've been jumping around asking people if there's a way to convert a PubKey to a PubKeyHash on-chain, but nobody seems to have an answer to this question. I've asked the question in one more internal channel, let's see if we can get an answer.
I need to triage the issue somehow, so I'm going to triage it with "Low priority" as I'm not sure what else I can do about it right now...

The Plutus Tools team pointed me to how a PubKey gets converted to a PubKeyHash. That conversion function uses Blake2b_224, but we only have Blake2b_256 on-chain, so it doesn't seem possible to me to convert a PubKey to a a PubKeyHash without adding a new builtin.
Does this make sense to you?
Adding new builtins is generally low-priority, hence I'm going to keep this issue as is for now, but we'll need to discuss with the team if adding Blake2b_224 to the set of builtins is cost-effective (it probably is, but it's not me who decides).

Looking on previous such issues (byte operations or something like that), I think this is up for CIP, cuz changes user primops list. Is that right?

Yeah, that's what I think too, and if you or somebody else created a CIP we'd highly appreciate that.

There is no "sensible" workaround, AFAIK. Leaving it to off-chain as we do have different security guaranties, same as any other oracle implementation.

I see, thank you, I agree with your assessment.

@GeorgeFlerovsky

@effectfully
Could you please explain how you arrived at the "Low Priority" status for this issue?

I already did:

Adding new builtins is generally low-priority

but let me elaborate.
Firstly, "low-priority" doesn't mean that we don't care or are not going to do it, it only means that we don't need to track it closely in the nearest future possible (unlike bugs or serious but easily fixable inefficiencies for example).
Secondly, any extension to the language needs to go through an approval of multiple people, often from different teams, and is generally a non-trivial process, particularly for crypto primitives that members of the Plutus team aren't familiar with (and we don't have any crypto experts among us). What this means is that in order to add any crypto primitive we need to reach out to a crypto expert and ask them to scrutinize it carefully, as well as review the implementation by a member of the Plutus team, plus a change to the specification. It's a lot of work, so before we commit to that, it is ideal for us to make sure that this is indeed something that we want, so that we don't end up spending a lot of time on something that isn't very helpful. And the way we ensure that is by having a CIP that we can read and ask other people to read, including various stakeholders who make the final decision.
Basically, it's a complicated and time consuming process, which is why having a CIP is a prerequisite for starting it. Sometimes we feel confident and not overloaded already, so we create a CIP ourselves. Other times we wait for the community to demonstrate us the need for a builtin by submitting a CIP. And even in this case it can take a while, e.g. the bitwise operations CIP that was approved long ago is still not done despite there being a PR. We're a fairly small team responsible for lots of different things working in a setting with an extremely high cost of failure, so some things just don't move as fast as everyone would like to.
Hope this explains why I labeled the ticket as "low-priority".
@GeorgeFlerovsky and @uhbif19 thanks a lot for the examples, those are going to be very helpful once we start discussing the possibility of adding the builtin.

@effectfully Thank you so much for the detailed reply. Indeed, a thorough discussion via CIP seems warranted here — adding crypto primitive is important to get right. 🙂
We'll go ahead and start that process. Incidentally, we may have some crypto experts on our end who may be able to advise on this.

We'll go ahead and start that process. Incidentally, we may have some crypto experts available on our end who may be able to advise on this.

@GeorgeFlerovsky thank you a ton for considering this, it would be invaluable for us. Any kind of help from the community is always highly appreciated and I personally insist that in the Plutus team we need to prioritize things that folks helped us with, because at that point it's very clear that the community does care about the specific functionality.

@effectfully Am I understanding correctly, that with this PR, this issue can be done with new primops?

@effectfully Am I understanding correctly, that with this PR, this issue can be done with new primops?

I don't know, sorry.
@kwxm do you happen to know? If not, any idea who might?

@effectfully Am I understanding correctly, that with this PR, this issue can be done with new primops?

I believe so, but only with Plutus V3, which won't be on mainnet until Conway.

@effectfully @GeorgeFlerovsky Are there any reference for Plutus/blockchain versions compability?

@uhbif19 does this help?

Am I understanding correctly, that with this PR, this issue can be done with new primops?

I believe so, but only with Plutus V3, which won't be on mainnet until Conway.

The Conway era is here, hence I'm going to claim that this issue is resolved. If that claim is wrong, please do let us know and feel free to reopen the issue.

@effectfully Correct. This issue is resolved because Plutus V3 added the Blake2b_224 hashing builtin:
https://github.com/IntersectMBO/plutus/blob/6d5e14ce7457f8317892343dca83fd7619cb7102/plutus-ledger-api%2Fsrc%2FPlutusLedgerApi%2FCommon%2FVersions.hs#L112


Sending message timed outexit status 1

Today I got this error
error sending message: sending message timed outexit status 1
anyone with the same problem ?
I just can response 1 message and the app crash.
I give me 3 times this message.
HandleJsonMessage ["Stream","asleep"]
HandleJsonMessage ["Conn",{"protoVersion":[0,17],"binVersion":11,"phone":{"wa_version":"<IP_ADDRESS>","mcc":"370","mnc":"004","os_version":"5.1.1","device_manufacturer":"unknown","device_model":"Z91","os_build_number":"V1.1.1_B180628"},"features":{"URL":true,"FLAGS":"EAEYASgBOAFAAUgBWAFgAWgBeAGYAQGgAQGwAQK4AQHIAQHYAQHgAQPoAQLwAQP4AQOAAgOIAgGgAgOoAgPAAgHQAgPYAgPgAgPwAgE="},"pushname":"Registro y Consulta"}]
HandleJsonMessage ["Props",{"stickers":1,"productCatalogOpenDeeplink":1,"productCatalogDeeplink":1,"catalogPdpNewDesign":1,"catalogMessage":1,"suspiciousLinks":1,"webBizProfileV3M2":false,"webBizProfileV3":false,"webProductListMessageFallback":true,"webProductListMessage":true,"webYouTubePlayerEnhancements":false,"webMediaCustomCroppingEnabled":true,"webCatalogProductsOnOff":true,"pttPlaybackSpeedHideDelay":1500,"pttPlaybackSpeedEnabled":true,"pttDraftEnabled":false,"webBizProfileEdit":true,"bizProfileEdit":false,"mmsCatV1ForwardHotOverrideEnabled":true,"webSendDocumentThumbInMessageDisabled":false,"webDownloadLinkThumbMmsEnabled":false,"webUploadLinkThumbMmsEnabled":false,"webDownloadDocumentThumbMmsEnabled":false,"webUploadDocumentThumbMmsEnabled":false,"mmsHotContentTimespan":86400,"mmsVCacheAggregationEnabled":true,"webSMBUpsellInBizProfile":true,"greenAlertBannerDuration":86400000,"webCatalogApiREH":true,"webButtonsMessage":true,"webCatalogManagement":true,"webCartV11OrderMessageChanges":true,"webCart":true,"webCatalogCart":false,"webGroupV2Enabled":1,"stickerSearchEnabled":false,"webVoipWindowsOsMinVersion":"10.0.18362","webVoipMacOsMinVersion":"17.0.0","webVoip":false,"webListMessage":true,"ctwaContextCompose":true,"aliteContactUsEnabled":true,"camelotWeb":true,"preloadStickers":true,"webBizProfileOptions":116,"wsCanCacheRequests":true,"bucket":"","gifSearch":"tenor","maxFileSize":100,"media":64,"maxSubject":25,"maxParticipants":257,"imageMaxKBytes":1024,"imageMaxEdge":1280,"statusVideoMaxDuration":30,"frequentlyForwardedMessages":1,"webShopsChatHeaderButtonEnabled":1,"ephemeralMessages":1,"newCommerceEntryPointEnabled":1,"shopsProfileDrawerEntrypoint":1,"viewOnceWrite":0,"ephemeralMessagesSetting":1,"upgradeToMDModal":1,"shopsHeaderDropdownMenuItem":1,"mmsVcardAutodownloadSizeKb":64,"multicastLimitGlobal":5,"wallpapersV2":1,"vcardAsDocumentSizeKb":64,"quickMessageSearch":1,"ctwaContextRender":1,"frequentlyForwardedMax":1,"vcardMaxSizeKb":5000,"hfmStringChanges":1,"muteAlways":1,"shopsHideCatalogAttachmentEntrypoint":1,"viewOnceRead":0,"groupDescLength":512}]
HandleJsonMessage ["Stream","asleep"]
I am using this version
Server has version 2.2126.14
Versions are equal
thanks
victor

Sorry , my mistake.


Need a way for applications to display help messages

Currently there's not a good way for application to display help messages if the user passes a --help argument. There are a few issues:

The --help argument gets swallowed when Wallaroo parses the Wallaroo-specific arguments, so it is never propagated down to the application_setup function. How should we notify the application that the user has requested help?
We would need to figure out how to merge the Wallaroo-specific help and the application-specific help messages. Would we display one first, then the other, and if so, which one is first and which one is last? Should we do something "smarter", like letting the application insert things into specific parts of the help, or rewrite the application-specific help?
Should the application decide what to do after printing help? For example, should it be able to print help and then run the application, or should help always print a message and terminate?

There are probably other things we need to think about.

Also, this is related to, but not a duplicate of #2217.


Latex package missing

I needed to install the standalone package on Ubuntu 18.04 after installing pdflatex. It might be useful to add this requirement to the documentation as currently, latex step crashes without any errors

Good point!
I updated the Readme d15ee1e267221a78d2cd45fbd97a3ba8ecc852a7


"MANGALIA" is listed in the drop-down menu

Description:
When user writes "Mangalia" the location appears in the drop-down menu next to the comune and the county witch is a part according to the law
Precondition:
The website is up an running.

Step 1
Write in the search bar "Mangalia"

Expected results
The location appears in the drop-down menu as "Municipiul Mangalia, CONSTANȚA"


neofetch incorrectly report the WM to be kwm instead of chunkwm

While this might be a bug of neofetch, I think you should take a look

See https://github.com/dylanaraps/neofetch/pull/785 – I noticed this a while back and fixed it, submitted a PR and it got merged, but there has not been a new release yet. It should work just fine if you install from master.

@dominiklohmann That's great, thanks for your timely response!


[ChargePrices] ChargePricesUpdated

@MadsBloendAndersen the ChargePricesUpdated event is not in scope for team volt to implement within the current PI so we can't start the work on this issue in the next coming sprint and I would thereby not put too much energy into refining the issue.
The "only" event from charges we can implement is ChargeCreated


fix(cheatcodes): Make serializeString always serialize values into a string, add serializeJson cheatcode

Motivation
Closes https://github.com/foundry-rs/foundry/issues/4601
don't rely on from_str when using serializeString
this fails a test test_serializeNotSimpleJson that uses a serialized string a serializes it again.
not sure what to make of this. wdyt @odyslam ?
I think serialize string was rather serialize object, so unsure if this change breaks some assumptions.

Solution

IMHO, this is a huge footgun actually. I believe serializeString should explicitly, always serialize objects to string, and have some other cheatcode like serializeJson that always expects serializable objects for composability.

This seems like a good solution to me, would be curious to confirm with @sakulstra also

@mds1 & @mattsse updated this PR with the new scope:

serializeString will now always serialize values as a string. It CANNOT be used to serialize json values, as they will be parsed as a string. This might be a breaking change for some I understand.
A new cheatcode, serializeJson, now performs the other function serializeString had, which is, it takes a valid JSON string and serializes it to a json object. It will revert if it fails to do so.

sgtm!

This might be a breaking change for some I understand.

Yea, given this we probably should merge this into the v1 branch and hold off on releasing it, since it might break user scripts

lgtm, agree with the gist of the discussion here.

Regarding v1 or main i don't have a strong opinion.
It wouldn't have been the first breaking change on foundry <1, but it's also not so urgent to change the behavior :shrug:
Imo both paths are fine.


Change WORMHOLE_B0 to WORMHOLE

Since we don't really have any Wormhole A0 cards for any part of the stack, we can rename WORMHOLE_B0 to WORMHOLE.
This is a simple change in tt-umd, but it needs more attention when uplifting, so this can be done by someone who is in charge of repo organization, since it probably requires a lot of code reviews in tt-metal

This will likely need many changes across many repos.
Still not clear on the benefits vs hassle.


Treat contextually typed functions in JS files as typed

fixes https://github.com/microsoft/TypeScript/issues/56900

@typescript-bot test top200
@typescript-bot user test this
@typescript-bot run dt
@typescript-bot perf test this
@typescript-bot pack this

@Andarist can you merge this from main and then I'll run typescript-bot test it before merging it.

@sandersn done


Fix parser

@grosu please review. Addressed was your previous comments.

Just to make sure, did your tests fail without this change?

Yes, the tests failed with just "\n".  That's why I changed the code.

The newline characters put by the multiline string don't depend on the platform but on the text editor.

Aren't the text editors consistent with the platform's conventions?

I can still put \r\n even in mac, where you can still put \n in windows, depending on the setting of your text editor.

Are you sure this is not too fragile?  I would say that if my change does not break the tests on your platform, then we should go with it.
It would be nice to have a clean solution here.  Working explicitly with "\n" and "\r" seems fragile to me.

@grosu more tests are added. Now every line is covered except ones with the explicit comment.

thanks, @daejunpark.
i found a bug, when  is encountered before the entire definition is parsed.  I added a test for it, parseTestFailUnfinishedModule, but will let you fix the code.
also, i found that some of error messages were not precise wrt that follows next, so I added a couple more tests with the desired error message.
in the process, i also thought that it would be a good idea to add a strip function that does all we need with these multistrings.  the code is a bit more compact now.  sorry i didn't put that in a separate commit.

for the sake of completeness, i think we should also have tests where <EOF> can occur in the middle of parsing everything.

First see my previous two comments.
Regarding the error messages, it is not simple to generate such error messages that you suggested. Yes, I can add an ad-hoc support for that cases, but you will always find another case. In general, providing a high-quality parsing error message is a challenging problem, for which ones still write paper. The general support for more kind error messages should be a separate project, which I'll not implement in this pull request.
Also, this pull request became already very long, and now it is hard to keep track of the changes properly. You should merge this pull request when it is in a reasonable shape and request another pull request for remaining issues. Otherwise, it will never be merged, and grow too bigger to be able to keep track of.

We are very close to a perfect solution here, aren't we?  I am OK to merge this PR asap if you think it is getting too long.  But at least we should have only passing tests.  Are you going to catch the EOF exception and generate a ParseError in this PR, or you want to do it in the next one?

I'm working on the EOF exceptions. I'll disable or comment out the enhanced parsing error messages. Also, I'll enhance the strip function to support the cross-platform editing environment.

Looks good.


Strip carriage-returns from textfile input

This PR removes all carriage return characters (\r) from input files in the textfile collector when they are read by the expfmt parser, since it does not support them.
Fixes #199

Nice job! LGTM


[custom channels]: Use new tapchannelrpc RPC methods

Depends on https://github.com/lightninglabs/taproot-assets/pull/1048.
~Depends on https://github.com/lightningnetwork/lnd/pull/8947.~
Uses the new tapchannelrpc RPC methods SendPayment and AddInvoice that do the RFQ part inline, so we don't have to keep that logic in the litcli code.

I tested all commands manually, everything seems to work as expected. Ready for full review now.


[iOS] identify is always sent to bridge root endpoint, instead of bridged device endpoint

Reproduction steps

commission a bridge which contains one or multiple bridged devices (e.g. the bridge-app example)
during commissioning, Home.app UI walks though all bridged devices and offers a "identify" device button.
pressing "identify" always sends the Identify command (0 in cluster 3) to endpoint 0 (the root node) instead of to the bridged device itself.

As the purpose of "identify" is to associate offered accessories (in the current implementation: anonymous because unnamed, see #22734) with actual hardware, this is clearly wrong. "identify" commands should be issued to the actual bridged device's endpoint so the corresponding hardware can make itself visible/audible and allow users to recognize them.
Note that sending "identify" to endpoint 0 is wrong even in the case of identifying the bridge itself, which is NOT represented by endpoint 0, but by a separate endpoint (1 in the bridge-app example).
Platform
darwin
Platform Version(s)
16.1 release
Type
Manually tested with SDK
(Optional) If manually tested please explain why this is only manually tested
No response
Anything else?
No response

@plan44 Please file an issue via our feedback assistant and we should get this resolved for you.  Please find the instructions below. Please let me know if you need any help with filing one and I would be happy to help.
Thanks,
Nivi.
Feedback assistant ticket:
File a feedback assistant ticket.
https://developer.apple.com/bug-reporting/#feedback-assistant
Click on the link below using your account:
https://feedbackassistant.apple.com/new-form-response
Choose iOS/iPadOS to file an issue
Choose the area as Home App and fill in the details of the type of issue and the description
Technical Information
Please provide the following
a) Sysdiagnose logs for iPhone / iPad with the timestamp / timeframe of the issue
b) Sysdiagnose logs for all the Home Hubs (HomePod mini / HomePod / Apple TV) with the timestamp / timeframe of the issue
c) Accessory logs with the timestamp / timeframe of the issue
d) mDNS network logs with timestamp / timeframe of the issue
e) Video or screenshot describing the issue (optional but beneficial)
Please make sure you download and install the profiles for iOS and tvOS as provided here. The instructions are also in these links.
iOS:
https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=ios&name=homekit
https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=ios&name=network
https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=ios&name=mdns
tvOS:
https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=tvos&name=homekit
https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=tvos&name=network
https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=tvos&name=mdns
For installation instructions, refer to https://developer.apple.com/bug-reporting/profiles-and-logs.
Note: Once you have the profile on the iPhone, it will ask you if you want to install it on other devices. Follow the prompts to install on the HomePod, Apple TV, etc., where you have the described issue and reproduce it.
Apple DeveloperApple Developer
Bug Reporting - Apple Developer
Now with Feedback Assistant available on iPhone, iPad, Mac, and the web, it’s easier to submit effective bug reports and request enhancements to APIs and tools. (71 kB)
https://developer.apple.com/bug-reporting/#feedback-assistant
developer.apple.comdeveloper.apple.com
Profiles and Logs - Bug Reporting - Apple Developer
Get details on providing logs, reproducible test cases, and other information that will help us investigate and diagnose your reported issues.
developer.apple.comdeveloper.apple.com
Profiles and Logs - Bug Reporting - Apple Developer
Get details on providing logs, reproducible test cases, and other information that will help us investigate and diagnose your reported issues.
developer.apple.comdeveloper.apple.com
Profiles and Logs - Bug Reporting - Apple Developer
Get details on providing logs, reproducible test cases, and other information that will help us investigate and diagnose your reported issues.

Recent testing with iOS 16.2 beta shows that this issue is already fixed. So closing this issue.
@nivi-apple Thanks for the instructions for feedback assistant. I will post future non-SDK iOS issues there, and hope it will be less of a black hole experience when reporting matter/home related things than it used to be for other topics (I've been developing iOS apps since 2009...) 😉 😁


Weather Fix

pls dad

Location might be a bit... borked since I wasn't able to find more parameters for the link to give shorter stuff, and the  equally worse
Example if you wanna see the json
http://wxdata.weather.com/wxdata/weather/local/USVA0944?cc=*&unit=f&dayf=6&locale=en_US

I just realized the current WeatherLocation variable will always return error because you need to specify a Location Code and not your city name, will get to fix it once I'm not bored

Honestly, I'd just guide the user to find their weather code themselves. Otherwise you'd have to search for it every time Rainmeter starts.

Rainmeter stops halfway downloading the weather data and to fix that and also make it automatic like the original I added the abundance of updates
I think I detalied in earlier edits that you can find the other locations by just going to wxdata's link and replace the last part with their city and blah blah, just make them find the exact name of the city, not the locid cause that's boring for me.
Good thing I haven't done anything with ip geolocations hehe

This has worked wonderfully for me. Literally changed a couple lines by hand in the way @Drgabi18 did and it is fully functioning. It fixes the Yahoo Weather problem!

Sadly, the weather API used here is not working anymore.
The API returns "This service is deprecated as of 01/15/2020" when you try to access it directly.


Add junit to try parsing of simple XML file with pool...

... to detect/prevent regression to parsing exceptions caused by whitespace that happened in gemfire 9.0 -9.0.1.

will create another pull request, canceling this one.


[SuperEditorMarkdown] & changes to & when serialized to markdown

When data is serialized using serializeDocumentToMarkdown, & changes to &

Also seen that. And the < and > symbols also become "<" and ">" respectively.

Can you please provide reproduction steps?
I just wrote the following test and it passes:
      test('paragraph with special characters', () {
        final doc = MutableDocument(nodes: [
          ParagraphNode(
            id: '1',
            text: AttributedText('This is a <paragraph> & specials symbols.'),
          ),
        ]);

        expect(serializeDocumentToMarkdown(doc), 'This is a <paragraph> & specials symbols.');
      });

Sorry I realised that unlike the OP, I am getting this error with:
MutableDocument deserializeMarkdownToDocument(
String markdown, {
MarkdownSyntax syntax = MarkdownSyntax.superEditor,
List<md.BlockSyntax> customBlockSyntax = const [],
List customElementToNodeConverters = const [],
})
Although, having tested it again now, the error is still occurring.

@Mijawel can you please provide reproduction steps? What exactly are you calling that method with? What error is being reported?

String markdownText = "Please note that the user prefers the use of ampersands (&) instead of the full word 'and'.";
    print(markdownText);
    var markdownDocument = deserializeMarkdownToDocument(markdownText);
    // print out the document
    for (DocumentNode node in markdownDocument.nodes) {
      print(node);
    }

Output:
Please note that the user prefers the use of ampersands (&) instead of the full word 'and'.
[TextNode] - text: [AttributedText] - "Please note that the user prefers the use of ampersands (&) instead of the full word 'and'."
[AttributedSpans] (0 spans):, metadata: {textAlign: null, blockType: [NamedAttribution]: paragraph}

This issue has been solved by this PR: https://github.com/superlistapp/super_editor/pull/1674


Supports sort with comments

This PR adds support for sorting with comments - comments will be kept before a string node.
Before:

After:

Sorry, confirmation was delayed.

I  mistook. I fixed commented code after merge.
Thank you awesome PR 👍
I will release version 1.0.4.


Add quote from @adinancr to website

I think it would be a good idea to add Adina's quote from the TLP press release to the website.  I am not sure where to put it ATM.  Is this ok with you @adinancr?

Sure Keith, feel free to use the quite wherever you see fit.
Adina
On Thu, Jul 27, 2017 at 10:33 AM, Keith Turner<EMAIL_ADDRESS>wrote:

I think it would be a good idea to add Adina's quote from the TLP press
release
https://blogs.apache.org/foundation/entry/the-apache-software-foundation-announces5
to the website. I am not sure where to put it ATM. Is this ok with you
@adinancr https://github.com/adinancr?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-fluo-website/issues/75, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ADR5beX-KM5AVg6EvkwOINuKlB74_5kPks5sSJ-kgaJpZM4OlXt7
.

--
Dr. Adina Crainiceanu
Associate Professor, Computer Science Department
United States Naval Academy
410-293-6822
<EMAIL_ADDRESS>http://www.usna.edu/Users/cs/adina/

Make a testimony sections. Could put it on the front page below the main features section.


Environment ID should be part of the URL so that bookmarks work better

v0.18.2
Steps:

Create a project
Switch to that project
Go to Services page
Create Environment
Copy Url that goes to that environment (example http://<IP_ADDRESS>:8080/static/environments/1e1)
Paste that Url into new browser window

Results:
404 page

Expected:
Should go to that service page
Additional info:
This is because the projectID is not in the URL and since it doesn't exist in Default project it can't find it.

Any URL can cause this, the current environment ID is not part of the URL so if the rest of it is to a resource that isn't in the active project it will be 404.

+1

Version - master 2/18
Verified fixed


Dedupe AppSync Functions appears to disregard (or runs before) overridden vtl resolvers

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
npm install -g @aws-amplify/cli
If applicable, what version of Node.js are you using?
16.15.0
Amplify CLI Version
10.5.0 (but this has been the case since 8.1.0 which introduced the dedupe feature)
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Amplify Categories
api
Amplify Commands
codegen
Describe the bug
Amplify v8.1.0 introduced the following change https://github.com/aws-amplify/amplify-cli/pull/10289 in order to limit the # of resources created in AppSync. It means that 2 or more GraphQL APIs can share the same underlying AppSync Function if their needs are the same. This is determined internally by Amplify by generating a hash over the VTL - which makes perfect sense and generally works as you'd expect...
...until you override one of the generated VTL's for one (or more) of those functions. Rather than the functions having their own separate AppSync Function they continue to use the same one even though the VTL is not the same. My guess is that this happens because the hash is run on the VTL before the overridden VTL is introduced but it could be something else entirely.
Expected behavior
Given the example reproduction steps below, the expectation is that the getUser API uses it's own QueryGetUserAuthFN rather than the shared MutationSaveSomeDataAuthFN once we introduce the /api/<api-name>/resolvers/Query.getUser.auth.req.vtl override.
Reproduction steps

Within the schema.graphql create two (or more) APIs with the same authentication, e.g.

type Mutation {
  saveSomeData(args: SaveSomeDataInput!): Boolean
    @function(name: "my-lambda-${env}")
    @aws_iam
    @aws_cognito_user_pools
    @auth(rules: [
      {allow: public, provider: iam},
      {allow: groups, groups: ["User", "Admin"]}
    ])
}

type Query {
  getUser(args: GetUserInput): User
    @function(name: "another-lambda-${env}")
    @aws_iam
    @aws_cognito_user_pools
    @auth(rules: [
      {allow: public, provider: iam},
      {allow: groups, groups: ["User", "Admin"]}
    ])
}

After running amplify api gql-compile && amplify codegen, as of Amplify v8.1.0 both the saveSomeData and getUser API's will share a single AppSync Function for the authentication (as the base configuration is the same) and because deleteSomeData is "first", the AppSync Function will be MutationSaveSomeDataAuthFN. This is expected and working correctly.

Override the getUser auth by creating your own custom VTL in /api/<api-name>/resolvers/Query.getUser.auth.req.vtl. For simplicity, let's set the contents as such (i.e. no authentication):

## [Start] Field Authorization Steps. **
#set( $isAuthorized = false )
#if( $util.authType() == "IAM Authorization" )
  #set( $isAuthorized = true )
#end
#if( $util.authType() == "User Pool Authorization" )
  #set( $isAuthorized = true )
#end
#if( !$isAuthorized )
$util.unauthorized()
#end
$util.toJson({"version":"2018-05-29","payload":{}})
## [End] Field Authorization Steps. **

Re-run amplify api gql-compile && amplify codegen and note that nothing has changed, both saveSomeData and getUser still share the MutationSaveSomeDataAuthFN function even though their hashes should no longer be the same and therefore getUser should have its own QueryGetUserAuthFN function.

If you change the authentication for getUser e.g.

type Query {
  getUser(args: GetUserInput): User
    @function(name: "another-lambda-${env}")
    @aws_iam
    @aws_cognito_user_pools
    @auth(rules: [
      {allow: public, provider: iam},
      {allow: groups, groups: ["User", "Admin", "FakeGroupJustToCreateADifferentHash"]}
    ])
}

and re-run amplify api gql-compile && amplify codegen then getUser correctly has it's own QueryGetUserAuthFN function generated.
GraphQL schema(s)

# Put schemas below this line
type Mutation {
  saveSomeData(args: SaveSomeDataInput!): Boolean
    @function(name: "my-lambda-${env}")
    @aws_iam
    @aws_cognito_user_pools
    @auth(rules: [
      {allow: public, provider: iam},
      {allow: groups, groups: ["User", "Admin"]}
    ])
}

type Query {
  getUser(args: GetUserInput): User
    @function(name: "another-lambda-${env}")
    @aws_iam
    @aws_cognito_user_pools
    @auth(rules: [
      {allow: public, provider: iam},
      {allow: groups, groups: ["User", "Admin"]}
    ])
}

Project Identifier
n/a
Log output
No response
Additional information
Workaround

Do something to change the hash, e.g. as shown above by adding a unique group name and whilst that works, it's a hack rather than a workaround.

This issue is being triaged and tracked here. Please follow that thread for updates.


Crawlable anchors

I would like Google to index all those nice remodals individually by their anchor.
According to https://support.google.com/webmasters/answer/174992?hl=en, the starting point seems to get a "hashbang" into the URL. mysite.com/#!myanchor. I've tried simply adding that to the code, like <a href="#!myanchor"> and data-remodal-id="!myanchor", but that wouldn't work out of the box. Neither using %21 instead of !.
Not sure if the entire operation makes sense though! What's your opinion on this?

It is absolutely easy to fix.

 Thank you very much!


Urban Dictionary plugin

.ud what's up should return the first definition and a permalink to the definitions page.

Closed by PR #37


Feature/esckan-65 - Generate PDF from the summary view

Issue Link  - ESCKAN-65
Task description:

Add a pdf generating service - generatePDFService -  generates a pdf as the below format.
file (12).pdf

alternative is also to add the text KnowledgeStatement before writing the knowledge statement for that CS. As below:
file (11).pdf

Edit the header to download PDF instead of csv.

Let me know @ddelpiano if this font works, still working on to get the Asap Font to work with the library. thanks!

Example of the connectivity matrix:

Demo file
file - 2024-09-18T154259.598.pdf


CI failing to complete tests

As reported on Slack 2019-12-23T15:55Z the documentation, gitlint, identity/emails, and Kconfig tests are failing to complete on multiple PRs.  Resubmitting does not seem to have any effect.  See https://github.com/zephyrproject-rtos/zephyr/pulls and note all the orange dots where there should be a :heavy_multiplication_x: or a :heavy_check_mark:.

This still doesn't seem to be resolved and in practice means that nothing can be merged at the moment.

Need to revert the following commit and keep using the docker image v0.9.1 until we figure out why the CI is not happy with the new CI image (probably Python 3.6-related issue ...):
https://github.com/zephyrproject-rtos/ci-pipelines/commit/6bf203c057475d5993b12f523e6b10b41bce0231

should be resolved now.


withJob from "react-jobs" runs on SSR

the following code:
import {withJob as withJobBrowser} from 'react-jobs';

@withJobBrowser(() => console.log('i should be in the browser') || Math.random())
class MyTest extends PureComponent {

    render () {
        const {job} = this.props

        return (
            <div>
                test: {job.result}
            </div>
        );
    }

}

prints i should be in the browser in node when server side rendering is enabled.
My understanding was that react-jobs and react-jobs/ssr were mutually exclusive (i.e. the former should only run on the client and the latter only the server/client)
this is using the latest version - 0.6.2

Hey @smirea with the latest release and API overhaul this is no longer applicable.
Closing 😀


undefined method 'name' for ROM::Yesql::Relation

I'm trying to use a rom-yesql relation with a rom repository. However, I get an error when I try to call .to_a on the relation from within the repository.
The error is thrown from within rom-repository where it is expecting the relation to have a method name. The Materialized instance that I get out of rom-yesql does not have that method.
Is rom-yesql supposed to be compatible with rom-repository, or can it only be used as a relation?

@mrship I haven't made it work with repos yet, but we can do it in next release. I want all adapters to work with repos, FWIW :)

This seems outdated, closing


[Macro] Incorrect displaying of monomer attachment point number

Steps to Reproduce

Add monomer "DAPhe" on canvas

Actual behavior
R1 attachment point displayed on canvas but R2 in preview.

Expected behavior
Attachment point number should be the same as in library.

this issue is tested


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 704

Questions ?
Please refer to the Backport tool documentation


style: bring back our changes from https://github.com/mitodl/bootcamps-zendesk-theme

Related Ticket
https://github.com/mitodl/hq/issues/3643
Description
This PR picks our cloned changes from https://github.com/mitodl/bootcamps-zendesk-theme.
We didn't have a forked repo for our bootcamps theme, And the cloned one also didn't have the commit history unlike https://github.com/mitodl/mitxonline-zendesk-theme. So, We have to fork a new one and get our changes from clone to this repo as part of PR. If our cloned repo had the commit history it would have been easier for us to keep them in sync.
Here is the test instance for this theme https://arbi377.zendesk.com/hc/en-us
Screenshots
Screenshot from this PR:

Mobile

I'm going to merge this as a single commit. It will be easier for us to rebase off of the upstream master later on.


cannot use compressed ibl texture for ios

I found that all the compressed formats (etc, astc, dxt, pvrtc2) of ibl texture are not supported by metal. Does this mean I cannot use compressed ibl file for iOS?
But dxt, astc are supported formats of OpenGL.

Metal supports ETC2, ASTC and PVRTC (and others too).

Will it be fixed in the next version of filament?
Or I need to fix it by myself if I need to use compressed texture?

@beibei1998 Which compressed format are you trying to use?

Thank you very much!
I have done the update and rebuilt. I used the cmgen to generate compressed ibl of etc2. But when I run the hello-gltf and change the ibl, it says:
validateReplaceRegion:183: failed assertion `rowBytes(0) must be >= (1024).'
and then crashed?
Are there any tips about generating compressed ibl?
below are the options I used:
--format=ktx --size=512 --extract-blur=0.1 --compression=etc_srgb8_alpha_rgba_100

That sounds like a problem with the Metal backend, I'll take a closer look.

I have temporarily solved the problem by setting bytesPerPixel and faceWidth in the MetalTexture::loadCubeImage to change rowBytes to apply texture of etc2 (etc2_eac_rgba8).

@bejado is this issue still valid?

This should be fixed—the Metal backend now supports ETC compression.


[Snyk] Security upgrade cryptography from 41.0.4 to 41.0.5

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

requirements.txt

⚠ Warning
celery 5.3.0 requires kombu, which is not installed.

Vulnerabilities that will be fixed
By pinning:

Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity

551/1000  Why? Recently disclosed, Has a fix available, CVSS 5.3
Missing Cryptographic Step SNYK-PYTHON-CRYPTOGRAPHY-6036192
cryptography:  41.0.4 -> 41.0.5
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Checkmarx One – Scan Summary & Details – d3ab5c86-350b-49f1-9d6c-1f072293b664
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

CVE-2023-44270
Npm-postcss-7.0.35
Vulnerable Package

CVE-2023-45803
Python-urllib3-1.26.17
Vulnerable Package

Log_Forging
/dojo/models.py: 1521
Attack Vector

Log_Forging
/dojo/models.py: 1524
Attack Vector

Log_Forging
/dojo/models.py: 1518
Attack Vector


[WIP] generate: support conversion webhooks

Description of the change:

internal/generate/clusterserviceversion: add CRD names that have conversion webhook configs matching a validating/mutating webhook config's service.

Motivation for the change: OLM supports conversion webhooks
/cc @varshaprasad96
Checklist
If the pull request includes user-facing changes, extra documentation is required:

[ ] Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
[ ] Add or update relevant sections of the docs website in website/content/en/docs

Blocked by #3761

Closing this since the spec for a CSV's conversion webhooks has changed.


don't copy over bzlib.h permissions in build.rs

TL;DR:
I had a failure building bzip2-rs (through the zip crate) on an external unix drive/mount, due to chmod not working on it. This patch uses std::io::copy instead of std::fs::copy to prevent copying over old file metadata/permissions/etc, and instead just copies over the file's contents, using the default destination's permissions.
rationale/how I found this:
Specifically, this EPERM error was caused due to me not being the owner of the drive/mount I'm working on (owned by root, but I am within a group that can read/write/exe all the files). This allows me to create/modify/etc all the files themselves, but not change the permissions (also NTFS, so it wouldn't make sense to anyway).
The error isn't really clear from the build.rs error output either (viewing the backtrace didn't help):
running: "ar" "s" "/media/ext_drive/my_crate/target/debug/build/bzip2-sys-60b04b335573cd8e/out/lib/libbz2.a"
  exit code: 0
  cargo:rustc-link-lib=static=bz2
  cargo:rustc-link-search=native=/media/ext_drive/my_crate/target/debug/build/bzip2-sys-60b04b335573cd8e/out/lib

  --- stderr
  thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 1, kind: PermissionDenied, message: "Operation not permitted" }', /home/$USER/.cargo/registry/src/github.com-1ecc6299db9ec823/bzip2-sys-0.1.9+1.0.8/build.rs:43:64
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: build failed

I had to strace it, and eventually traced it back to this line in the stdlib:
19144 openat(AT_FDCWD, "/media/ext_drive/my_crate/target/debug/build/bzip2-sys-60b04b335573cd8e/out/include/bzlib.h", O_WRONLY|O_CREAT|O_TRUNC|O_CLOEXEC, 0100664) = 8
19144 statx(8, "", AT_STATX_SYNC_AS_STAT|AT_EMPTY_PATH, STATX_ALL, {stx_mask=STATX_BASIC_STATS, stx_attributes=0, stx_mode=S_IFREG|0770, stx_size=0, ...}) = 0
19144 fchmod(8, 0100664)                = -1 EPERM (Operation not permitted)
19144 close(8)                          = 0

Thanks for the PR! This seems fine to me but it feels sort of weird, is this the only reason something doesn't build on your mount? Not supporting fchmod seems like it'd cause a lot of things to not build?

I'm not sure what other crates have this sort of problem (I guess generic to using fs::copy inside build.rs), but I run into this building my tarsum crate on an external NTFS drive. Building off my home folder (regular, ext4/etc permissions) works just fine.
As the machine is essentially a NAS, I have it setup so root owns all the files, and r/w/x access is controlled via a group, storage. Here's the drive's fstab line:
UUID=XXXXXXXXXXXXXXXX /media/2tb ntfs-3g   defaults,nls=utf8,umask=0000,dmask=0007,fmask=0007,uid=root,gid=storage,windows_names 0 0

This results in all files having permissions like the following:
-rwxrwx--- 1 root storage 1121 Dec 14 15:44 Cargo.lock
-rwxrwx--- 1 root storage  307 Dec 14 15:44 Cargo.toml
drwxrwx--- 1 root storage    0 Dec 14 15:43 src
drwxrwx--- 1 root storage  376 Dec 14 15:44 target

Since all the files are owned by root (but rwx by everyone in the storage group), chmod fails. I imagine this can be easily tested with an NTFS ramdisk (or probably something less extreme), if necessary.
Creating a new cargo project with just a dependency of bzip2 = "0.4.1" doesn't build due to fchmod, but bzip2 = { git = "https://github.com/csm123199/bzip2-rs" } does.
You're right - not supporting chmod breaks more things, like git. I looked more into how I can handle this, and it turns out ntfs-3g should have a silent option to hide chmod errors like these (and even mount has a quiet option for this), but I couldn't get those mount options to work.
Since even git chokes on this shared filesystem setup, I'd understand if this is out of scope or something; I personally just switched drives to fix it for me :)

Ok thanks for the info! In that case I think I'd prefer to go ahead and close this because I'd prefer to not have a specific workaround like this in the build script. If this becomes too problematic for you, though, this can also be added.


Assignment 04

Rubric For Mini Project 0: JQ
Submission
Canvas
1: The link submitted on Canvas is for the pull request containing the
assignment submission.
0: The link submitted on Canvas is not for the pull request containing the
assignment submission.
Git Branch
1: The branch includes only changes for this assignment.
0: The branch includes commits or changes outside this assignment.
Git Commit Message
1: All commit messages for the branch are reasonably clear.
0: One or more commit messages for the branch are reasonably clear.
GitHub Pull Request
1: The pull request is made to the main branch of the student's fork of the
course repository.
0: The pull request is made to a branch other than main or to a repo that is
not the student's fork of the course repository.
Points
Submission Score: 4/4
Features
Command Line Interface
For each of the required CLI arguments filter-string, path-to-json, color-output, monochrome-output, sort-keys, indent, and compact-output
0.5: The argument can be correctly parsed and consumed by the rest of the package.
0: The argument is not correctly parsed and propagated to the rest of the package.
Additionally, the command line parsing correctly raises errors to the user when conflicting arguments are inputted.
1.5: Errors are properly determined and bubbled up to the user.
0: Errors are not propagated back to the user.
Comments
(-1.5) Comments are not correctly bubbled up
Supported Filters
For each of the required filters identity, object-identifier index, array index, array slice, pipe, and array iterator
2: The filter is correctly implemented and properly parses all possible JSON inputs.
1: Minor errors exist in the implement of the filter.
0: Major errors exist in the implementation, or the filter was omitted from the package.
Additionally, comprehensive unit tests are required for each feature:
2: Full unit test coverage is provided (with passing implementations) to exercise a wide varity of use-cases and edge-cases of the filter, ensuring that the output is correct and that errors are properly outputted.
1: Unit tests are present, but lack a significant breadth of cases to fully exercise the filter.
0: Tests are missing, or lack significant assessment of the filter's performance.
Comments
Identity: Correct implementation and unit test
Object-Identifier: Correct implementation and unit test
Array Index: Correct implementation and unit test
Array Slice: Correct implementation and unit test
(-1) Pipe: Correct implementation, unit test exists for detecting a pipe, but would have been good to explicitly check that the filter chains work as expected
Array Iterator: Correct implementation and unit tests
(-2) Not taking points off everywhere, but as a whole, you test the positive cases for your filters quite well, but don't test for when invalid inputs are given.
Built-In Functions
For each of the required built-in functions add, length, del
2: The built-in function is correctly implemented and properly processes all possible JSON inputs.
1: Minor errors exist in the implementation of the operator.
0: Major errors exist in the implementation, or the function was omitted from the package.
Additionally, comprehensive unit tests are required for each function:
2: Full unit test coverage is provided (with passing implementations) to exercise a wide varity of use-cases and edge-cases of the function, ensuring that the output is correct and that errors are properly outputted.
1: Unit tests are present, but lack a significant breadth of cases to fully exercise the function.
0: Tests are missing, or lack significant assessment of the function's performance.
Comments
Add: Correct implementation and unit test
Length: Correct implementation and unit test
Del: Correct implementation and unit test
(-2) Similar to above, would have been good to have a slighty wider array of tests. This is especially important in this section for stuff like add since it can be defined differently for different datatypes.
Formatted Printing
For each of the required formats, colored printing, monochrome printing, sorted keys, indents, and compact output
2: The formatter is correctly implemented and properly displays any JSON object..
1: Minor errors exist in the implementation of the formatter.
0: Major errors exist in the implementation, or the formatter was omitted from the package.
Additionally, unit tests are required for each function:
2: Full unit test coverage is provided (with passing implementations) to ensure that the formatter can correctly handle all expected inputs.
1: Unit tests are present, but lack significant breadth of cases to fully exercise the formatter.
0: Tests are missing, or lack significant assessment of the formatter.
Comments
(-1) Color Printing: Color printing is implemented, but the JQ_COLORS env var is not read for the user to customize these formats.
Monochrome Printing: Correctly implemented and unit tests
Sorted Keys: Correctly implemented and unit tests
Indents: Correctly implemented and unit tests
Compact Output: Correctly implemented and unit tests
(-2) Effort was made for testing the output formats, but more explicit assertions would make them more effective tests (could be accomplished by faking out what you are writing to in order to consume the desired output)
Points
Features Score: 53/61
Code Quality
Design
File/Module organization
2: The program is appropriately split into reasonable files/modules
1: The program is somewhat organized, but there's room for improvement (splits aren't idiomatic, or some modules are still too large, etc.)
0: The program is not split at all
Scalability
5: The code is architected with scalability in mind. If more features needed to be added to the filtering/printing/CLI, they could easily be integrated.
3: The code was architected with some scalaibility in mind. However, significant refactoring would be needed in order to expand the feature set of this tool. (Possible symptoms include not modularizing enough/not effectively using traits + generics).
0: The code is not scalable. The entire package would need to be refactored in order to expand its features.
General Cleanliness
4: The code is effectively documented, especially for sources of user-facing errors. Additionally, function signatures are clear and the code is overall very readable.
2: Attempts at verbose documentation were made, but certain sources of error are unclear OR poor function signatures are used and readers would have slight difficulties while scanning the code.
0: Documentation is severely lacking in several palces and the code is not written in a readable way.
Lint/Format
RustFmt
2: RustFmt produces no warnings when run on the changed files
1: RustFmt produces a few minor warnings when run on the changed files
0: RustFmt produces many warnings when run on the changed files
Clippy
2: Clippy produces no warnings when run on the changed files
1: Clippy produces a few minor warnings when run on the changed files
0: Clippy produces many warnings when run on the changed files
Points
Code Quality Score: 12/15
Comments
Scalability: 5/5 - Overall, the scalability of your application was very strong, nice work.
General Cleanliness: 2/4 - taking some points off her for the dead code throughout the assignment. Could have also benefitted from some slightly more verbose commenting
-1 for clippy errors
Summary
Add up the point totals here
Total Score: 69/80


Ale linter

elm-vim supports Syntastic out of the box but you might want to divert that effort to Ale instead. Ale is the new hotness for linting in Vim. It takes advantage of Vim 8's async tasks. Ale's UX and speed leave Syntastic in the dust. Syntastic's architecture may not recover.
Ale collects all language linters in its repo. So this isn't a request for elm-vim's repo. Rather it's for interested people here, those familiar with Elm tooling, to contribute to Ale's repo.

Turns out this wasn't too difficult. The only problem is that to use elm-make properly the directory needs to be set to the project root. This is done in elm-vim by calling s:ExecuteInRoot, which calls the command after changing the directory to path returned from s:FindRootDirectory. This can be solved in ale by using the path from s:FindRootDirectory when creating the command string, and changing the directory to it before calling the elm-make command.
Knowing this, I made a fork that handles Elm linting; the linter file can be found here.
@ajhager - Since I'm copying that s:FindRootDirectory wholesale, should there be any additional attributions in the source for this project? (I'm not that familiar with the BSD-3 License)

This looks great. I hereby give you permission to use that function for whatever purpose you need. :)

Thanks! XD

Created https://github.com/w0rp/ale/pull/213

Nice! Thank you! I gave it a whirl and it works as well as I remember Syntastic used to! (Syntastic being currently out of commission. See #91)
There is one other thing missing. It doesn't lint as I type. That's the main advantage of Ale. Instead, I have to save the file first.
elm-make doesn't natively support compiling from stdin, but I think Ale has wrappers for that sort of thing.

Ah, thanks for pointing that out! That should probably be updated. I'll work on that tonight.

@john-kurkowski: the updates have been made to use stdin.  You should now see the lint occur as you type.

This PR was merged, feel free to close this issue and post any further issues in the Ale project.

It works great. Thanks again!

Trying it out, seems great.  I know the PR is closed, but I had two questions more related to Elm errors than Ale:

Is there a way to get the ElmErrorDetail text?  I couldn't find out how to do so.
Errors in an imported file show up in the file that imports it.  Is there any way to fix that?

Other than that, awesome work, thank you for contributing this!

@jschomay

To my understanding, the current elm#ErrorDetail logic is tied to the results of the elm#Build process. The first step might be making that more generic, which you may want to make a separate issue for if you think that's the right process.
Even then It would still be hard to do in combination with the Ale linter. The linters are tied to the Ale project, and would require weird cross-project interaction.

You should add this issue to the ale project. I overlooked those errors when I implemented it.


how to set auto scroll with duration

Hi, this is awesome library, amazing experience to use this library, but can i set auto scroll with duration? thanks

Hi, would you tell me with an example so that I'll try to provide you a more accurate answer?

like swipe automatically every 3 seconds, you know, like recommending 3 popular movies today and you see the banner moves automatically every 3 seconds for example


fix: do not use \v in character classes

\v expands to multiple code points and is, therefore, illegal in PCRE2 when it starts a range. In PCRE, the range token (-) following any such escape code would simply be treated as a literal (depending on compile time configuration).

Note that this commit branches of v2.0.0 and will need to be released as v2.1.0.

@theseion is this still a draft?


Web Viewer: Add support for drag-and-drop of materials with image references

Issue
If you drag-drop a MTLX file with image dependencies the image dependencies cannot be found to be bound.
Seems to be the case for

Image files in same folder as MTLX file
Image files in sub-folders of MTLX file
Image files in sibling or parent folders

Perhaps this is due to the usage of relative file paths, though would think that 1 would work.
Diagnosis
Found while loading and examining the console log in a browser.

Can I pick this issue for the dev day 2024 ?

Absolutely, and welcome!

As an FYI, AFAIK this could just not be feasible to do as you can't access local file paths due to security. Thus drag-and-drop supports zip files load. If there is a way @Avgilles, I'd be very interested in how to set this up :).

Hello, is there is a way to have resolve path in material X ?
I see here that the path is get in local when it's drag and drop, but the buffer store the blob url, maybe I can get the blob url and resolve it ? @kwokcb
https://github.com/AcademySoftwareFoundation/MaterialX/blob/e6b96502e965392c8851bab9de847d3135a48396/javascript/MaterialXView/source/helper.js#L117

When all the files are dropped togehter (or the folder containing them), then the references can indeed be resolved with a custom loader. (this is, for example, how all glTF viewers work when dropping .gltf + .bin + some textures).
I'll see if I find time to fix this :)

Hi @hybridherbst,
Thanks for you comments on this.
Actually @Avgilles was trying to do this for ASWF dev days but if Gilles is still interested maybe just some pointers would appreciate.
Also, the case I don't think is possible is drag-and-drop only the MaterialX file (not the folder or other with images files) and have the file references inside the MaterialX file parsed to load in associated images.


Async bug fixes

This PR contains fixes for all outstanding bugs related to async/iterator blocks pending for VS2015.
Some of them are actually affects VS2013 and previous versions as well.
Fixing this will unblocks us from releasing VS2015 support.
Would really appreciated for the review!

Thanks for doing this! It looks great.


show errorModal on trading failures

no ticket associated with this effort. Did @Chwy5 or @joeykrug say to do this?

@bthaile
@pgebheim requested some feedback in the order form - since we show none currently.  Maybe just temporary,  until we are more stable?


OCPBUGS-15595: Fix precaching job view cleanup

Updated the kuttl tests for the change from #475 and also fixed the bug introduced by the same PR

/assign @sudomakeinstall2 @irinamihai

/lgtm

/lgtm

/approve

/cherrypick release-4.13

/cherrypick release-4.13


Link checker should support relative paths to video files

Part of https://github.com/Qiskit/documentation/issues/1043
https://github.com/Qiskit/documentation/blob/bdf5b4d86602c647ec88dd374efe85a860db827d/docs/guides/sessions.mdx?plain=1#L40
We can change that link to ../videos and the link still will load correctly. We need to make that change to support PR previews in GitHub Pages because of how the basepath works (https://github.com/Qiskit/documentation/pull/1691).
However, the link checker doesn't like the relative link. It expects the folder ./public/videos, not ./videos.
Imo we should only special-case videos, not  /public/images. We can fix images with basepath through the app itself, whereas we can't easily with videos. For images, I think it's most clear to use the absolute link /images because it's resilient to whether the file is in a subfolder or not.
Bonus credit: ban /videos and require ../videos.

Eh, I don't think this is that important. It's only so that PR previews work with videos. We barely use those and local previews still work. We can reopen this if it's confusing to people.


Missing "log" command for the alternative to collect logs

File: docker-for-mac/troubleshoot.md
In the check the logs section the alternative way to collect the logs command is missing is missing the log command
Right now it's:
show --debug --info --style syslog --last 1d --predicate "$pred" >/tmp/logs.txt

While it should be:
log show --debug --info --style syslog --last 1d --predicate "$pred" >/tmp/logs.txt

Closing this ticket due to its age, and the impending refactor. If you think this is in error, feel free to reopen. Thanks!


What else do we need to do to build out our ecosystem?

Proposed topic for ASHG
What else do we need to do to build out our ecosystem?

Closing


hi, Is there anyway to let points to be customize widgets?

const FlDotData({
this.show = true,
this.dotColor = Colors.blue,
this.dotSize = 4.0,
this.checkToShowDot = showAllDots,
});
this is simple and can not to be customizable.but sometimes we need more comflex and customizable.

Hi, currently there isn't, but stay tuned.
Thanks!

ok, I will. Nice man, God Bless U.

Hi there, I'm about to post an issue, but this one is kinda similar, which is about customizing dots. It seems until the date that I can't make visual to only show the last dot in a line chart (I couldn't make  the custom function, even it's the same like default function showAllDots).
Looking forward to it^^

@imaNNeoFighT any news on this?

It will be in the next version,
I will notify you here.

0.9.0 ->

Added strokeWidth, getStrokeColor, getDotColor in the FlDotData, also removed dotColor from it (you should use getDotColor instead, it gives you more customizability), now we have more customizability on FlDotData, check line_chart_sample3, and line_chart_sample5


Minor fix in interp_nd_binning

Minor fix of interp_nd_binning that was failing when containing a pd.Interval vector with NaNs in a certain order.

Added a better type checking of the binning variable vector
Added a test that failed without the above fix

@adehecq @erikmannerfelt Merging this PR without review as it's only a couple line fix


chore: deprecate jest-runner-tsd

I think it is time to deprecate jest-runner-tsd and encourage people to migrate.

TSTyche has different API and that might complicate the migration. But it is worth extra effort, because TSTyche can do more:

it has more matchers;
test() and describe() helpers;
can test on different versions of TypeScript;
easier to setup;
less to install (only one package, which is only 200kb),
and more.

tsd-lite is deprecated and I do not plan coming back to it. Reasons are mentioned above (;
An alternative could be to wait for necessary APIs exposed directly from tsd. They were planing to do so in https://github.com/tsdjs/tsd/issues/196. That plan is nearly one year old. So far nothing related with code changes have been done. Also note that in the future they plan to publish tsd as ESM only package. That might cause another trouble with integration.

Another problem is @tsd/typescript. Sounds like something goes wrong with it. The install size of current<EMAIL_ADDRESS>is 20.8MB, but<EMAIL_ADDRESS>is 34.7MB. That’s almost double!

It can stay as is. All versions of tsd-lite are deprecated for some time. So users see the message anyways.


GovUK-Migr-Trello-16: Fix CNAMES for monitoring

alert and alert.cluster CNAMES should point to
alert.blue..govuk-internal.digital
But due to the way the code is setup alert will point correctly but
alert.cluster will end up pointing to alert.cluster..govuk-internal.digital
which does not go anywhere.
This fix will get both recards pointing into the correct destination.
Solo: @ronocg

Ok, correct if I am wrong but my understanding of this is that we want alert.cluster.blue.blah to point to the same location as alert.blue.blah. They should both resolve to the same host. This is what the current PR does.


feat(docker-compose): docker-compose version upgraded from 1.27.4 to 1.29.1

Signed-off-by: Batuhan Apaydın<EMAIL_ADDRESS>
Description
docker-compose version upgraded from 1.27.4 to 1.29.1
Motivation and Context

It fixes #374

[x] I have raised an issue to propose this change (required)

How Has This Been Tested?

$ docker container run --rm -ti -v $(pwd):/workspace golang:1.16-alpine sh $ go build -o ark $ ./ark get docker-compose

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I've read the CONTRIBUTION guide
[x] I have signed-off my commits with git commit -s
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

[ ] I have tested this on arm, or have added code to prevent deployment

Thank you


Print URL to find video after playing.

Print the video URL to the terminal so that a user can look up the video afterwards. If they want to.

the windows standalone package won't open a terminal window so therefore when you do print command the program would crash even if it builds. I was also thinking about printing the URL and considered writing the URL to some log file with the timestamp. Let me know if that would be a better option.

Maybe a history file will do (with a max of 20 entries or so)
something like
cheermeup.history
And that the file would look like this:
https://redditvideo1.com
https://redditvideo2.com

And that the file is viewable from the commandline like this:
$ cheermeup --history
Videos shown by cheermeup

https://redditvideo1.com
https://redditvideo2.com
$

Yeah that would work I think, I'll do that.


Feature request: Add description to firewall rule when creating from the app

Azure Data Studio Version:

Steps to Reproduce:
When you use the Azure Resource Explorer to find and connect to a database/instance, you get an option to add a firewall rule automagically if your IP address is not currently whitelisted.
This creates firewall rule in Azure that doesn't have a great description :-(
It would be nice to be able to add a description to the rule, like 'PASS Summit Hotel', 'Home internet' so that it's easier to tidy up firewall rules in Azure - don't really want to leave an IP in there for a network I'm only going to use once or twice...

+1 on this request to make it easier to audit who added the rules if there are multiple users.
Alternatively would also be reasonable if the auto-generated firewall rule had a name that included the signed in Azure account name.
For example the current rules are named
ClientIPAddress_2022-01-19_02:32:03

it could be the name and email of the user, with the timestamp
Doe, John - john.doe@email.com_2022-01-19_02:32:03


I can't download NVM on Ubuntu Using Curl

Operating system and version:
WSL 2
nvm debug output:

nvm ls output:

How did you install nvm?
I copied the installation command from the README.md file
and when I ran it in my Terminal, I got this timeout error:
mitchyugan@DESKTOP-A0GLKL9:~$ curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/master/install.sh | bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:05:00 --:--:--     0
curl: (28) SSL connection timeout

What steps did you perform?
What happened?
What did you expect to happen?
Is there anything in any of your profile files that modifies the PATH?

If you are having installation issues, or getting "N/A", what does curl -I --compressed -v https://nodejs.org/dist/ print out?

mitchyugan@DESKTOP-A0GLKL9:~$ curl -I --compressed -v https://nodejs.org/dist/
*   Trying <IP_ADDRESS>:443...
* Connected to nodejs.org (<IP_ADDRESS>) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=*.nodejs.org
*  start date: Feb  3 00:00:00 2023 GMT
*  expire date: Mar  5 23:59:59 2024 GMT
*  subjectAltName: host "nodejs.org" matched cert's "nodejs.org"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
*  SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* Using Stream ID: 1 (easy handle 0x55a92ef6f340)
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
> HEAD /dist/ HTTP/2
> Host: nodejs.org
> user-agent: curl/7.81.0
> accept: */*
> accept-encoding: deflate, gzip, br, zstd
>
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
< HTTP/2 200
HTTP/2 200
< date: Tue, 31 Oct 2023 21:05:59 GMT
date: Tue, 31 Oct 2023 21:05:59 GMT
< content-type: text/html
content-type: text/html
< cache-control: public, max-age=3600, s-maxage=14400
cache-control: public, max-age=3600, s-maxage=14400
< last-modified: Tue, 31 Oct 2023 19:05:25 GMT
last-modified: Tue, 31 Oct 2023 19:05:25 GMT
< cf-cache-status: HIT
cf-cache-status: HIT
< age: 368
age: 368
< vary: Accept-Encoding
vary: Accept-Encoding
< strict-transport-security: max-age=31536000; includeSubDomains; preload
strict-transport-security: max-age=31536000; includeSubDomains; preload
< x-content-type-options: nosniff
x-content-type-options: nosniff
< server: cloudflare
server: cloudflare
< cf-ray: 81eedbf7bcaddcc7-LHR
cf-ray: 81eedbf7bcaddcc7-LHR
< content-encoding: br
content-encoding: br

<
* Connection #0 to host nodejs.org left intact
mitchyugan@DESKTOP-A0GLKL9:~$

Seems like you're unable to make a secure connection to raw.githubusercontent.com - github needs to be completely unblocked for the nvm installation to work.

Seems like you're unable to make a secure connection to raw.githubusercontent.com - github needs to be completely unblocked for the nvm installation to work.

Pls what can I do about this?

The problem may be due to your employer, school, or government - in which case, short of moving to a different location with uncensored internet, you may need to use a VPN.
I can't advise you further than that.


Create ng-device-detector.d.ts

Added type definitions for ng-device-detector found here: https://github.com/srfrnk/ng-device-detector

I did not use branches, I'll create another PR


fix(Notification): Fixed Notification not centered in IOS, fixed #173

Description
Fixed Notification not centered in IOS, fixes #137 .
Type of change
Please select the relevant option.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

#173

Codecov Report

Merging #176 (f9903b1) into main (e7bb378) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #176   +/-   ##
=======================================
  Coverage   90.77%   90.78%
=======================================
  Files         155      155
  Lines        7386     7387    +1
  Branches     2031     2032    +1
=======================================
+ Hits         6705     6706    +1
  Misses        560      560
  Partials      121      121

Impacted Files
Coverage Δ

...uya-panel-kit/src/components/notification/index.js
98.07% <100.00%> (ø)

...ya-panel-kit/src/components/notification/styled.js
100.00% <100.00%> (ø)

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 e7bb378...f9903b1. Read the comment docs.


Filter (This Week) is not working on analytics page.

Expected Behavior
The filter should work similar to other filter, and should render the Click information.
Current Behavior
Now, the page turns out to be blank, and dropdown also get Stuck.
Steps to Reproduce

Shrink an URL.
Open it's analytics link.
Select (This Week) from the dropdown filter on top right.

Cannot be reproduced.


Update committers lists to point to apache website

https://github.com/apache/parquet-mr/pull/355#issuecomment-235637473
Reporter: Alex Levenson / @isnotinvain
Assignee: Alex Levenson / @isnotinvain
Note: This issue was originally created as PARQUET-667. Please see the migration documentation for further details.

Alex Levenson / @isnotinvain:
Issue resolved by pull request 355
https://github.com/apache/parquet-mr/pull/355


[CARBONDATA-3409] Fix Concurrent dataloading Issue with mv

Problem:
While performing concurrent dataloading to MV datamap, if any of the loads was not able to get TableStatusLock, then because newLoadName and segmentMap was empty, it was doing full rebuild.
Solution:
If load was not able to take tablestatuslock, then disable the datamap and return

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[ ] Document update required?

[ ] Testing done
manually tested

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/3421/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3626/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/11689/

@Indhumathi27 , please carify me one doubt, when concurrnet load are happening for main table adn no lazy datamaps are present, then each load will will trigger load to datamap. So since  the load to datamap happens after main table status update, so  there will be chance that both the loads to datamaps get duplicate main table segments, how this scenario is handled?

@akashrn5 for every new load to datamap, we will take TableStatusLock and write new LoadMetadataEntry with new load name and set segmentInfo to ExtraInfo and segmentStatus to Insert_In_Progress. so, when next dataload comes for datamap, we will consider both "SUCCESS & INSERT_IN_PROGRESS" segments and get specified segments to load for that corresponding datamap load.

LGTM


Perhaps tfaction-root.yaml overwrites tfaction.yaml in working directory

Hi, I found kind of like a bug.
ACTUAL
https://suzuki-shunsuke.github.io/tfaction/docs/config/tfaction-yaml
In above document, It seems that tfaction.yaml in working directory overwrites tfaction-root.yaml.
You can override the configuration of tfaction-root.yaml by tfaction.yaml.

On the other hand, in the action get-target-config it seems that tfaction-root.yaml overwrites tfaction.yaml in working directory.
https://github.com/suzuki-shunsuke/tfaction/blob/4f6e115706b6060fa0d56e7674d32ff7098d62f4/get-target-config/src/index.ts#L41-L52
As far as I read the codes, each variables mean like following.

jobConfig: terraform_(plan|apply)_config in tfaction.yaml
wdConfig: tfaction.yaml
rootJobConfig: terraform_(plan|apply)_config in matched target in tfaction-root.yaml
targetConfig: matched target in tfaction-root.yaml
config: tfaction-root.yaml

So the order of list in arguments to setOutputs seems incorrect.
EXPECTED
The order like following is correct?
    lib.setOutputs([
      's3_bucket_name_plan_file',
      's3_bucket_name_tfmigrate_history',
      'gcs_bucket_name_plan_file',
      'providers_lock_opts',
    ], [config, targetConfig, wdConfig]);
    lib.setOutputs([
      'aws_region',
      'aws_assume_role_arn',
      'gcp_service_account',
      'gcp_workload_identity_provider',
    ], [config, targetConfig, rootJobConfig, wdConfig, jobConfig]);

If it's correct I send the PR! Thank you for reading in advance.

Thank you for your reply.
I missed break; keyword. I apologize I bothered you, I close this issue.


Tile indicators plugin: Show intermediate path tiles

Currently, it is possible to use the tile indicators plugin to show you your current tile and target tile. I think that for players learning positioning based activities (fight cave, hallowed sepulchre etc) it could be helpful if the plugin could also highlight all the intermediate tiles you are going to step onto before arriving (assuming run on/off is not toggled in the process).

i believe this is a plugin hub plugin now

https://github.com/Milo-Piazza/pathfinder adds this functionality only for the hovered tile. As I understood this issue, it was asking for that behavior for the destination tile? It's possible we may want to add the functionality from that hub plugin to the main client for both destination and hovered tiles.

Hmm, did not know the pathfinder plugin. It is only a very partial solution to this request. As noted, it does not show the path to the destination and I see two other major issues with it: 1) It assumes walking, never running. 2) It ignores the existence of obstacles.