fix: update gce-vpc to use random suffix

Re: change in 9af2904:
  on .terraform/modules/dynamic-python-webapp.gce-vpc/modules/subnets/main.tf line 29, in resource "google_compute_subnetwork" "subnetwork":
  29:   for_each                   = local.subnets
    ├────────────────
    │ local.subnets will be known only after apply

The "for_each" map includes keys derived from resource attributes that cannot
be determined until apply, and so Terraform cannot determine the full set of
keys that will identify the instances of this resource.

This is coming from the module itself. I added dynamic variables to the network, subnet, and instance because I thought that would be appropriate, but if subnets only need to be unique within the network, then making the subnet static should still allow for multiple deployments (in this scope).


Add pre-commit hooks and fix lint on all required files to pass the tests

First PR for adding CI on Kube-burner
On this PR, Im adding the pre-commit hooks and I have needed to fix all the lints to pass the test.
We can disable any of them, I have just removed the line length for the markdown files.

As we also have some YAMl files in the repo, do we want to consider a hook for yaml linting as well : https://github.com/adrienverge/yamllint ?

As we also have some YAMl files in the repo, do we want to consider a hook for yaml linting as well : https://github.com/adrienverge/yamllint ?

I have tried to add a yaml linter but most of the files we have in the repo are yaml templates named as yaml files, containing variables.
yaml lint fails on this kind of files when it finds a var. changing this files to yaml.template should resolve the issue, but it will requires changes on the code, which is out of scope on this PR.
If we want to lint yaml files, first we need to move yaml template files to the correct extension

looks good to me too!


Settings icon in gene description

Selecting the settings just enables choosing the gene source (refseq or gencode). Is it worth having the settings icon, or just leaving the source dropdown in view at all times?

I see your point.  I was trying to minimize the visual clutter in this panel, but perhaps this is overkill.

Fixed.


Support bearer token authentication

Cloudflare API now supports a normal bearer token authentication method instead of one using an email + API key pair.
https://blog.cloudflare.com/api-tokens-general-availability/
https://api.cloudflare.com/#getting-started-requests

LGTM, as this breaks public API I'll do a major version bump.

@ioquatix Does it?  I think I just added a new keyword argument.

Ah, did you mean authenticated()?  I wasn't considering it was a public API because it didn't have a spec.  I couldn't manage to make rspec pass anyway, though. 😜

I will think about it. I can check some existing code but I don't think many use that method... if I'm confident that it's generally not used, then it can just be minor version bump.
Regarding testing, I could give several colourful words to describe it. Cloudflare have been less than helpful even thought I was assigned someone to try and sort it out, we never made any progress. I just asked for a sandbox account, but even that was "too hard". I don't know how anyone at Cloudflare tests anything.

Thank you for the new release!


Sponsor and Speaker Updates

Sponsor updates:
Add SecurityInnovation to "Security Analyst" tier next to Contrast Security - https://www.securityinnovation.com/

Add NJCCIC linked logo to "CISO" tier next to SpecterOps - https://www.cyber.nj.gov/

Add NJCCIC linked logo next to SpecterOps under "Powered by" at the top
Speaker updates:
As the first card, add this speaker:

Michael Geraghty
CISO, State of New Jersey & Director, NJCCIC
Don't include "Speaker Topic:", just write "Keynote Speaker"
https://www.linkedin.com/in/michael-geraghty-13139820/

Added everything


rca

I've done a first pass design at rca. It will involve a lot of sql generation. As for query syntax, I'm thinking something like rca=dim_lvl_1,dim_lvl_2,mea, and where all of those names would have to already be selected in drilldowns and measures, and where cuts= would further limit the scope of calculation.
For example, for the rca calc above, it would be something like
?rca=Product.Shade,Geography.MSA,Quantity&drilldowns[]=Product.Shade&drilldowns[]=Geography.MSA&cuts[]=Date.Year&measures[]=Quantity

To make this more ergonomic, I can make additional cuts/drills/measures additive to the rca specific names, instead of duplicating names. I think this should be fine, but let me know if you think it might interfere with other features.
?rca=Product.Shade,Geography.MSA,Quantity&cuts[]=Date.Year

Here, Product.Shade and Geography.MSA would automatically be drilldowns.
I think it might be easier for me if Quantity was also exposed, but it wouldn't have to be. Let me know what a better default would be.
(Also, I think only one rca at a time is possible; and even if more were possible, it would probably too complicated to be worthwhile).

Basic rca works.
rca works with external cut.
rca works with external drilldowns.
Now need to check:

[ ] rca works with internal cuts
[ ] rca works with parents

Check if it's possible to calculate b, c, d from early sub-aggregations (probably won't be if there's an internal rca cut)

Need to make sure to test rca internal/external cuts, it's a little tricky and need to document the exact behavior.
For now, I'm allowing all external cuts, and internal cuts on drill_1.

closed by
https://github.com/hwchen/tesseract/commit/4b12092445de45dda943617b37894441a3cf79de
https://github.com/hwchen/tesseract/commit/8d19e6b8eff908fc9187b607fa9714743ede9662
https://github.com/hwchen/tesseract/commit/8bb584e421b1d4d69809497ce09d89af6b941649
https://github.com/hwchen/tesseract/commit/0fb5096bebf9d9c5848cc1e32a9ef6b160b97552
https://github.com/hwchen/tesseract/commit/1c0f8aea5d59df6e6c3f003af47459524271633d
https://github.com/hwchen/tesseract/commit/afa11d59dd605f4e3718ab316b526886e049bb05
https://github.com/hwchen/tesseract/commit/50384090e8dc250cfaeccf015a3b12e0d1ff5857
https://github.com/hwchen/tesseract/commit/604c4812227d7c4b8e2cc89438fc58196af05b78
https://github.com/hwchen/tesseract/commit/3676c07a8c5362ada7a970c751bd1d8de6bc4e42


NC DataPalooza finale blog post

Goes live at 7am. Also sending to South West Raleigh
http://citycampnc.org/2017/11/03/nc-datapalooza-open-data-competition-concludes-at-hq-raleigh/


Don't send referrer to jsdelivr

Fixes #22

Coverage remained the same at 96.491% when pulling f7a5b3644aa290065c0bdb9ceac44e71d7f7acd5 on michaelgmiller:referrer into c116a04ca7860f11693e5f851194c1911df357d1 on graphql-python:master.


How will we deal with potential misuse of personal information

Subject of the issue
The site is filled with personal information including address, phone number etc. We need to seriously think about how we will prevent the misuse of these information. Right now it is accessible to anyone.
We can only hope that no one will misuse this, but that won't be the reality

Wouldn't that slow down the rescue operations?

@rasinansar We need to think it through. How to handle it without slowing down the rescue operation

elif we could make a form, of details of whoever wants to access data with email/sms-verification, and once verified , we could send them the password.

First and foremost, the data is already out there, so only action that can be taken now is to minimize the impact and ward of any future legal liabilities. You might already be doing most of them, but just for posterity:
Few standard recommendations:

Stop giving out real data as bulk extracts for testing. There are other ways to generate test data.
Restrict the PROD DB read access to a limited user group.
Don't implement any feature that allows bulk download of data as api/json/xml/csv/excel.
A legal declaimer displayed at the bottom of the data collection screen and/or a mandatory modal OK click waiving the right to privacy of the provided data.
Collect info about anyone who had access to data (logs/audits?) for future legal liabilities. (highly unlikely in our country)
Person search page or its result page should display header/footer warning legal action against misuse of data.

Any other actions that can be taken are intrusive and will affect the easy accessibility of data for rescue efforts.


[SPARK-43305] Add support for java 17 from spark 3.5.0

What changes were proposed in this pull request?

Create Java17 base images alongside Java11 images starting from spark 3.5.0
Change ubuntu version to 22.04 for scala2.12-java17-*

Why are the changes needed?
Spark supports multiple Java versions, but the images are currently built only with Java 11.
Does this PR introduce any user-facing change?
New images would be available in the repositories.
How was this patch tested?

It seems to me that the builds are failing due to insufficient storage on the runners.
[info]   java.lang.AssertionError: assertion failed: Failed to execute -- bash -c MINIKUBE_IN_STYLE=true minikube status  --
[info] minikube
[info] type: Control Plane
[info] host: InsufficientStorage
[info] kubelet: Running
[info] apiserver: Running
[info] kubeconfig: Configured
[info] docker-env: in-use

Maybe it's possible to try switching to larger runners?

I never hit this before, but if it is storage limit, you could try to remove some tmp file to save space, such as:

https://github.com/apache/spark-docker/blob/master/.github/workflows/main.yml#L249

sudo install minikube-linux-amd64 /usr/local/bin/minikube
rm -f ./minikube-linux-amd64

It's about to save 80MB

https://github.com/apache/spark-docker/blob/028efd4637fb2cf791d5bd9ea70b2fca472de4b7/.github/workflows/main.yml#L201

remove fetch-depth: 0, seems also save some space?

I never hit this before, but if it is storage limit, you could try to remove some tmp file to save space, such as:

https://github.com/apache/spark-docker/blob/master/.github/workflows/main.yml#L249

sudo install minikube-linux-amd64 /usr/local/bin/minikube
rm minikube-linux-amd64

It's about to save 80MB
(later upadte) I also noticed this change also apply on main repo: https://github.com/apache/spark/blob/master/.github/workflows/build_and_test.yml#L1045

(if step 1 is ok, we don't need this step) https://github.com/apache/spark-docker/blob/028efd4637fb2cf791d5bd9ea70b2fca472de4b7/.github/workflows/main.yml#L201

remove fetch-depth: 0, seems also save some space?

added rm minikube-linux-amd64 and removed accidental changes in 3.3.0. Now only 3.5.0 will be built.
removing fetch-deph: 0 would help with space, but the default is fetch-deph: 1 which only fetches a single commit form the main/master branch. That would make the 3.3.0 build fail as it needs to cherry-pick commits from history.
I've tested this out on my own repo: https://github.com/vakarisbk/spark-docker/actions/runs/6545230049/job/17773271828

made fetch-depth: 0 applicable only for 3.3.0 (saves about 400MB for other builds)
borrowed CI runner cleanup scripts from the main spark repo free_disk_space_container free_disk_space and added an action step to execute them.
These scripts made the CI runner filesystem go from this:

Filesystem      Size  Used Avail Use% Mounted on
/dev/root        84G   66G   18G  80% /
tmpfs           3.4G  172K  3.4G   1% /dev/shm
tmpfs           1.4G  1.2M  1.4G   1% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/sdb15      105M  6.1M   99M   6% /boot/efi
/dev/sda1        14G  4.1G  9.0G  31% /mnt
tmpfs           693M   12K  693M   1% /run/user/1001

to this:
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        84G   29G   55G  35% /
tmpfs           3.4G  172K  3.4G   1% /dev/shm
tmpfs           1.4G  1.2M  1.4G   1% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/sdb15      105M  6.1M   99M   6% /boot/efi
/dev/sda1        14G  4.1G  9.0G  31% /mnt
tmpfs           693M   12K  693M   1% /run/user/1001

@Yikun could you trigger the builds one more time?

All tests have passed except the 3.3.2 build.
The 3.3.2 build fails due to an issue with the GPG key on keys.openpgp.org (key on keyserver.ubuntu.com works fine)
- gpg --keyserver hkps://keys.openpgp.org --recv-key "C56349D886F2B01F8CAE794C653C2301FEA493EE"

gpg: key 653C2301FEA493EE: no user ID
gpg: Total number processed: 1

- gpg --batch --verify spark.tgz.asc spark.tgz

gpg: Signature made Pn Vas 10 22:40:58 2023 EET
gpg:                using RSA key C56349D886F2B01F8CAE794C653C2301FEA493EE
gpg:                issuer<EMAIL_ADDRESS>gpg: Can't check signature: No public key

But that's probably not relevant to this PR?
Apart from that, the PR is ready for review.

@viirya Hi, Would you  mind taking a look on 3.3.2 release key issue. It might needs your help to upload the public key, see [1] as ref.
[1] https://github.com/apache/spark-docker/pull/55#issuecomment-1715173342

@Yikun Just uploaded to openpgp.

Please also make sure:

All dockerfiles and entrypoint.sh should be generated by add-dockerfiles.sh

All dockerfiles and entrypoints were generated using the add-dockerfiles.sh
To validate, I ran this diff:
mv 3.5.0 3.5.0_copy; \
./add-dockerfiles.sh 3.5.0; \
diff -r 3.5.0 3.5.0_copy;

It would be better if you can publish these images in your local repo to test (by appending a local change line in your local branch .github/workflows/publish.yml L50),  It's just a test but shouldn't be changed in this PR.

I've published the images in my forked repository.
Publish job logs can be found here.
Let me know if anything else is needed

cc @HyukjinKwon @zhengruifeng Would you mind also taking a look?

@Yikun maybe we can have this PR merged even without @HyukjinKwon and @zhengruifeng approval? This will not impact the existing images

Thanks for your efforts @vakarisbk , I'm going to merge this PR later today or tomorrow.

@vakarisbk Merged to master.
Thanks all!

Test publish on: https://github.com/apache/spark-docker/actions/runs/6820460339

Image published on GHCR @vakarisbk, would you mind doing a post validation:
https://github.com/apache/spark-docker/pkgs/container/spark-docker%2Fspark
Then you could feel free to open a PR on official image like:
https://github.com/docker-library/official-images/pull/15363
The content can be generated by tools/manifest.py manifest.


Update generic-host.md

Fixes #23196

You can use this if we merge it first ...
https://github.com/dotnet/AspNetCore.Docs/pull/23202


fade in fade out effect

Describe your problem here.
how to do fade in fade out effect like ..indie cross
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

doTweenAlpha

doTweenAlpha

function onCreatePost()
doTweenAlpha('1_alpha','1',0.2,2,'linear')
setProperty('gf.alpha', 0)
triggerEvent('Change Character', 'dad', 'die')
end
it works but i want to loop it

rks but i want to loop it

doTweenAlpha

how to loop that idk?


Attempt to fix merge conflicts for PR 69

@im-prakher I think if you merge this pull request, it will add the merge conflict commits from it to #69, and we'll then be able to merge that into the upstream master.

@im-prakher I think if you merge this pull request, it will add the merge conflict commits from it to #69, and we'll then be able to merge that into the upstream master.

Thanks a lot, it worked!!!

Thanks a lot, it worked!!!

Yay! Final PR is now merged.

Yay! Final PR is now merged.


Add -canary command-line flag

This PR introduces a new -canary boolean command-line flag.
When this flag is set, a -canary suffix is automatically added to the version.Version variable, which ends up in saved measurements and will help us identify data from canary releases. E.g.
{
  "GitShortCommit": "84608e1",
  "Version": "v0.20.6-4-g84608e1-canary",
  "ServerIP": "<IP_ADDRESS>",
  "ServerPort": 8080,
  "ClientIP": "<IP_ADDRESS>",
  "ClientPort": 43406,
  "StartTime": "2021-06-28T10:19:05.622318959Z",
  "EndTime": "2021-06-28T10:19:15.62552359Z",
  "Download": {
[...]

(Also, some formatting changes made by gofmt on unrelated code.)

This change is

Pull Request Test Coverage Report for Build 1448

5 of 14 (35.71%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.3%) to 81.673%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

ndt-server.go
5
14
35.71%

Files with Coverage Reduction
New Missed Lines
%

ndt-server.go
1
87.42%

Totals

Change from base Build 1446:
0.3%

Covered Lines:
1738

Relevant Lines:
2128

💛  - Coveralls


require file by platform

Test.ios.js   Test.web.js   Test.android.js
require('./Test')
in react-native, on android require is Test.android.js, on ios require is Test.ios.js
how to require Test.web.js in react-web?

If you use webpack, there is haste-resolver-webpack-plugin plugin for this

how to use it? can you give me a example please?

The plugin seems to be broken as of right now. Using it on the latest version causes a strange import issue yuanyan/haste-resolver-webpack-plugin#1

@fov42550564 , PR #165 resolved this issue
@brianneisler , the plugin issue https://github.com/yuanyan/haste-resolver-webpack-plugin/issues/1 seems fixed


[Bug]: shopify theme pull and ignore rule since 3.54.0

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
Theme
Expected behavior
The .shopifyignore file contains the following rule:
config/settings_data.json
templates/*.json

Since version 3.54.0, when I run the shopify theme pull command, the templates/*.json files are pulled even though they shouldn't be.
I have the same problem if I add templates/*.json rule in a shopify.theme.toml environment: the files are still pulled.
At first I thought it might be the * pattern, but shopify.theme.toml contains a rule to ignore locales and it still works fine:
[environments.xxx]
store = "xxx"
theme = xxx
ignore = ["locales/*"]

When testing the templates/collection.json rule, the templates/collection.json file is ignored.
It's definitely the templates/*.json rule that's causing the problem.
Expected behavior: The templates/*.json files should not be pulled because they are ignored by the .shopifyignore file or by an environment in the shopify.theme.toml file.
Please note that the shopify theme push command still works correctly: files are ignored during push.
Actual behavior
The files are pulled
Verbose output
2024-01-25T16:44:39.228Z: Reading the content of file at .shopifyignore...
2024-01-25T16:44:39.229Z: Ignoring theme file config/settings_data.json via .shopifyignore...
2024-01-25T16:44:39.229Z: Ignoring theme file locales/en.default.json via --ignore...
2024-01-25T16:44:39.229Z: Ignoring theme file locales/en.default.schema.json via --ignore...
2024-01-25T16:44:39.229Z: Ignoring theme file locales/fr.json via --ignore...
2024-01-25T16:44:39.229Z: Ignoring theme file locales/fr.schema.json via --ignore...

Reproduction steps

Add templates/*.json rule to .shopifyignore file or shopify.theme.toml environment
Run shopify theme pull command
templates/*.json files are pulled

Operating System
macOS 14.2.1
Shopify CLI version (check your project's package.json if you're not sure)
3.54.0
Shell
zsh
Node version (run node -v if you're not sure)
20.11.0
What language and version are you using in your application?
No response

--only flag is also broken...

This is a pretty critical bug that was introduced with 3.54.0.
Running shopify theme pull --store store-name --theme<PHONE_NUMBER>00 --path theme --only templates/*.json will result in no matches found: templates/*.json.
Or if I run shopify theme pull --store store-name --theme<PHONE_NUMBER>00 --path theme --only config/settings_data.json instead of pulling that one specific file locally I will see it occasionally delete some local templates/*.json files.
This change has broken our Github to Shopify integration with actions that rely on pulling down the latest changes someone might have made in the theme editor while also having the consequence of removing some files.
As a side effect, this change also breaks the .shopifyignore file in another way from what @msev outlined.  In my ignore file I have it set up to ignore markdown files:
...
*.md

With this in place the CLI will generate an error for these wildcard matches:
╭─ error ───────────────────────────────────╮
  Invalid regular expression: /*.md/: Nothing to repeat

  To investigate the issue, examine this stack trace:
    at match
    at (../../../.bun/install/global/node_modules/@shopify/theme/src/cli/uti-
       lities/asset-ignore.ts:25)
      const match = patterns.some((pattern) => key.match(pattern))
    at some
    at (../../../.bun/install/global/node_modules/@shopify/theme/src/cli/uti-
       lities/asset-ignore.ts:25)
      const match = patterns.some((pattern) => key.match(pattern))
    at filter
    at applyIgnoreFilters (../../../.bun/install/global/node_modules/@shopif-
       y/theme/src/cli/utilities/asset-ignore.ts:16)
      .filter(filterBy(shopifyIgnore, '.shopifyignore'))
    at async buildDownloadTasks (../../../.bun/install/global/node_modules/@-
       shopify/theme/src/cli/utilities/theme-downloader.ts:55)
      const checksums = await applyIgnoreFilters(remoteChecksums,
      themeFileSystem, options)
    at async downloadTheme (../../../.bun/install/global/node_modules/@shopi-
       fy/theme/src/cli/utilities/theme-downloader.ts:23)
      const downloadTasks = await buildDownloadTasks(remoteChecksums, theme,
       themeFileSystem, session, options)
    at async pull (../../../.bun/install/global/node_modules/@shopify/theme/-
       src/cli/services/pull.ts:43)
      await downloadTheme(theme, session, themeChecksums, themeFileSystem,
      options)
    at run (../../../.bun/install/global/node_modules/@shopify/theme/src/cli-
       /commands/theme/pull.ts:90)
      await pull(theme, adminSession, {path, nodelete, only, ignore, force})
╰───────────────────────────────────────╯

    SyntaxError: Invalid regular expression: /*.md/: Nothing to repeat

Looking at the PRs for 3.54.0, I noticed @karreiro's change that was included which removed the requirement for ruby for shopify theme pull, but clearly there is an issue with it.
As recommended in #3139 I added the --stable flag to use the legacy ruby implementation and now the all of the CLI commands related to shopify theme pull work as expected.

Thank you, everyone, for promptly reporting this issue with all the details!
As @jonathanmoore kindly suggested, please use the --stable option in the 3.54 version of Shopify CLI. In the next minor release, we're bringing back the legacy implementation (https://github.com/Shopify/cli/pull/3326) while the issues reported in this thread get fixed.
@anders-christiansen and @ChristiantangCC, could you please share the scenario you're facing (including the value you're passing for the --only/--ignore flags or the context of your .shopifyignore file)? With that information, we can make sure we support those use cases in upcoming releases.
Thanks again, everyone, for reporting the issues.


[BUG, DOC]  Written property, but it's FE property.

Steps to reproduce the behavior (Required)
in docs: https://github.com/StarRocks/starrocks/blob/main/docs/en/using_starrocks/Cost_based_optimizer.md#automatic-collection-1
When I try create analyze table tb_name(clmn) PROPERTIES ("statistic_collect_interval_sec" = "84600") i got invalid property statistic_collect_interval_sec error;
However, data changes in Hudi tables cannot be perceived and StarRocks periodically collects statistics based on the check interval and collection interval you specified. You can specify the following properties when you create an Analyze job:
statistic_collect_interval_sec

Expected behavior (Required)
However, data changes in Hudi tables cannot be perceived and StarRocks periodically collects statistics based on the check interval and collection interval you specified. You can specify the following FE properties when you create an Analyze job:
statistic_collect_interval_sec

Real behavior (Required)
However, data changes in Hudi tables cannot be perceived and StarRocks periodically collects statistics based on the check interval and collection interval you specified. You can specify the following properties when you create an Analyze job:
statistic_collect_interval_sec

StarRocks version (Required)

Latest 3.2

Thanks for reporting, we'll fix it


feat(projects): added anu in UI/UX & jd-solanki as contributor

[x] I followed the contributing guidelines: https://github.com/github/india/blob/main/CONTRIBUTING.md.

Which change are you proposing?

[x] Adding/updating open source project/s
[x] Adding/updating maintainer/s

Adding/updating open source project/s

[x] The project was built in or receives significant contributions from India
[x] The project has at least 100 stargazers

UnoCSS is emerging CSS framework (named Tailwind killer by some). However, CSS frameworks like Tailwind & UnoCSS don't provide any UI library to build UI rapidly. Anu helps with this 😇

Please replace this line with an explanation of why you think these changes should be made.

Adding/updating maintainer/s

[x] Maintainer's location on their GitHub profile indicates as India
[x] Maintainer has approved this PR to be included on the website

https://github.com/jd-solanki/anu

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

I think you made a typo in the projects yml file: it should be jd-solanki/anu, not jd-solanki-anu

Hi @tusharsadhwani
Thanks for the hint. Fixed ✅


Fixing misleading error message when trying to export

This patch fixes the misleading error message when users try to "Export all" into an invalid destination path.
It's not perfect, but I think that it will do the job. It's being a while since I wrote something in C++, but I would like to get back my skills, in this case, I'm all in for constructive reviews.
Also, I notice that we have too many places throwing errors, is that expected? Sometimes we have two messages, one for warning immediately followed by an error message.
Closes #26539

Something went real wrong with the rebase, probably it was done in the wrong direction?

Thanks!


Write a R program to find volume of a cuboid

Description
Write a R program to find volume of a cuboid
Volume of a cuboid = Length × Width × Height
Length : 2
Width  : 3
Height : 4

Volume : 24

How to contribute

Save the solution in find_volume_of_a_cuboid.r file
Add find_volume_of_a_cuboid.r file in find-volume-of-a-cuboid folder

!assign


[Feature]: Climate card : Icon Color based on temperature level

Is your feature request related to a problem?
I never turn off the thermostats, but lower them. And even with 15 degrees it will show them as heating/red.
Describe the solution you'd like
I really love this card. Could you please add icon colors based on temperature levels?
E.g. < 17 degrees blue, => 17 degrees red.
Describe alternatives you've considered
No response
Additional context
No response

Same here, only displaying a blue generic thermostat icon (the default from HA) and nothing changes from cold to heat, have you managed to come up with a solution ? The idea of mushroom is nice but lacks basic stuff


feat(scroll): 增加边界滚动配置, 解决横屏滚动会触发 mac 回退的问题

👀 PR includes

✨ Feature

[x] New feature

📝 Description
TODO:

[x] 文档
[x] Demo

之前滚动做了处理, 只有滚动到表格边缘时才会触发父容器滚动
但是 mac 上触摸板横向滚动时会触发浏览器默认的回退, 解决办法是通过 overscroll-behavior 解决
https://developer.mozilla.org/zh-CN/docs/Web/CSS/overscroll-behavior
同时增加虚拟滚动的 overscroll-behavior 实现, 当配置为 contain 和 none 时, 就算滚动到了边缘, 也不触发父容器滚动
🖼 Screenshot

Before
After

🔗 Related issue link

🔍 Self Check before Merge

[x] Add or update relevant Docs.
[x] Add or update relevant Demos.
[x] Add or update relevant TypeScript definitions.

:tada: This PR is included in version @antv/s2-v1.20.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version @antv/s2-react-v1.18.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[fix] dubbo monitor missing parameters

monitor interval can be override by outside setting

What is the purpose of the change

dubbo monitor collection missing the group version dubbo parameters
dubbo monitor interval default set to 60s and can't override by outside setting

Brief changelog

dubbo monitor parameters add group, version,dubbo parameters
monitor interval can be override by outside setting

Verifying this change
XXXX

Codecov Report

Merging #1407 into master will decrease coverage by 0.11%.
The diff coverage is 57.14%.

@@            Coverage Diff            @@
##           master   #1407      +/-   ##
=========================================
- Coverage   33.01%   32.9%   -0.12%
=========================================
  Files         691     691
  Lines       34624   34630       +6
  Branches     6850    6850
=========================================
- Hits        11431   11394      -37
- Misses      21247   21288      +41
- Partials     1946    1948       +2

Impacted Files
Coverage Δ

...n/java/com/alibaba/dubbo/config/MonitorConfig.java
0% <0%> (ø)
:arrow_up:

.../com/alibaba/dubbo/monitor/dubbo/DubboMonitor.java
73.39% <100%> (+0.24%)
:arrow_up:

...m/alibaba/dubbo/monitor/support/MonitorFilter.java
47.27% <100%> (+1.98%)
:arrow_up:

...ubbo/rpc/protocol/dubbo/ChannelWrappedInvoker.java
41.66% <0%> (-8.34%)
:arrow_down:

...mon/serialize/support/dubbo/GenericDataOutput.java
64.91% <0%> (-7.02%)
:arrow_down:

...om/alibaba/dubbo/rpc/filter/ActiveLimitFilter.java
77.77% <0%> (-5.56%)
:arrow_down:

...mmon/serialize/support/dubbo/GenericDataInput.java
57.91% <0%> (-3.87%)
:arrow_down:

...ba/dubbo/remoting/transport/netty/NettyServer.java
67.85% <0%> (-3.58%)
:arrow_down:

.../dubbo/rpc/protocol/dubbo/filter/FutureFilter.java
54.54% <0%> (-2.03%)
:arrow_down:

Continue to review full report at Codecov.

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


Site support request: instagram videos I liked

Is it possible to add list extractor for instagram videos I liked? Instagram API is able to return 300 last items I liked (need authentication).
(I found this related blog http://symmetricinfinity.com/2013/04/06/download-your-likes-from-instagram.html)

Here are my notes if anyone wants to get to it before me:
URL: https://www.instagram.com/x/saved/ where x is  username
Request always requires cookies.
https://www.instagram.com/graphql/query/?query_hash=8c86fed24fa03a8a2eea2a70a80c7b6b&variables=<encoded JSON>
variables must have:

id - User ID (see current extractor for how to get this)
first - integer, I think this is the limit
after - Unique ash for keeping track; it is on the page for the first request, next JSON returns it

Paths in the returned data:
data.user.edge_saved_media.count - int
data.user.edge_saved_media.edges - array
    [].node.is_video
           .shortcode = after /p/
data.user.edge_saved_media.page_info.end_cursor - goes in 'after' in variables in next request
                                    .has_next_page - boolean

The only way to do this without using the API (which will be deprecated, and the new Graph API does not provide this information) is to go through the entire feed with this path: /graphql/query/?query_hash=663d44f965069e3e859e829b6101903e&variables=%7B%7D
In the JSONthere's data.user.edge_web_feed_timeline.edges[].node.viewer_has_liked and to paginate there's the cursor string like in other requests already supported by the extractor.
Going through the entire feed (10 posts per request) will definitely take a while.

@dstftw This issue should be closed unless you want to pursue the above solution.


Update how the project is built locally and with actions

Update the MediaPipeUnityPlugin to v0.10.1 and add a build readme for how to download the packages for local builds.
Update the workflow scripts to download and unpack the libraries for mediapipe.
An issue has been posted on the MediaPipeUnityProject:
https://github.com/homuler/MediaPipeUnityPlugin/issues/779

I found a way to install the libraries inside the github action.
This issue should soon be done

Made sure macos 11 and 12 works with this update.
Still having problems with StandaloneFileBrowser

This has now been merged to develop. Added fallback option for systems were StandaloneFileBrowser does not work


[Question] It is possible a permanent ban?

I ran dev branch many hours until server turns down. Now (after 6 hours) I try to login from the smartphone and when i push login button it returns to the main screen (to register a new account). Tried many times, and it do the same: nothing. No warning messages, no error messages, only returns to the main screen. Tried with a google account and it works ok, just with PTC. It is possible a permanent ban or another limitation from the game?

Login is likely just down.
http://ispokemongodownornot.com/

Please don't create these issues here, this has nothing to do with the workings of the bot.

So far they have only issued soft bans from what I know. Next time google it, you'll find everything you need to know.


Remove needless OpcredsIssuer dependency

Problem

Dependency on ExampleOperationalCredentialsIssuer was in
many files where not needed, making other refactors more
difficult.

Change overview
Remove this dependency and make CHIPCommand own its ephemeral
operational credentials issuer.
Testing

Unit tests and integration tests still pass

Not sure why the member needs to move from private to protected.

To match other similarly scoped items just as storage

/rebase


[ESP32] Add matter IP events for Ethernet

Dnsserver Initialisation should be done whenever the IP address is changed for ethernet
This PR has changes to trigger the matter IP events and Initialise the Dnssd server

##TESTING

Tested commissioning and control

@PSONALl Cherrypick this to v1.1-branch?


TS-4265: Fix NUMA stack support.

The support for NUMA based stacks was lost in the #1997 PR due to the length of time of the work - it was added after work started and I didn't notice it until too late. This adds that back and also provides additional comments on the logic.

[approve ci autest]

[approve ci autest]

[approve ci autest]

Oh I see, it was deleted before.

I guess since Phil loves it, I'm ok too.


Migration failing on version slugs

Running migrations on #1396, I hit the following error:
Traceback (most recent call last):
  File "/home/docs/bin/django-admin.py", line 5, in <module>
    management.execute_from_command_line()
  File "/home/docs/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 399, in execute_from_command_li
ne
    utility.execute()
  File "/home/docs/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 392, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/home/docs/local/lib/python2.7/site-packages/django/core/management/base.py", line 242, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/home/docs/local/lib/python2.7/site-packages/django/core/management/base.py", line 285, in execute
    output = self.handle(*args, **options)
  File "/home/docs/local/lib/python2.7/site-packages/south/management/commands/migrate.py", line 111, in handle
    ignore_ghosts = ignore_ghosts,
  File "/home/docs/local/lib/python2.7/site-packages/south/migration/__init__.py", line 220, in migrate_app
    success = migrator.migrate_many(target, workplan, database)
  File "/home/docs/local/lib/python2.7/site-packages/south/migration/migrators.py", line 256, in migrate_many
    result = migrator.__class__.migrate_many(migrator, target, migrations, database)
  File "/home/docs/local/lib/python2.7/site-packages/south/migration/migrators.py", line 331, in migrate_many
    result = self.migrate(migration, database)
  File "/home/docs/local/lib/python2.7/site-packages/south/migration/migrators.py", line 133, in migrate
    result = self.run(migration, database)
  File "/home/docs/local/lib/python2.7/site-packages/south/migration/migrators.py", line 114, in run
    return self.run_migration(migration, database)
  File "/home/docs/local/lib/python2.7/site-packages/south/migration/migrators.py", line 84, in run_migration
    migration_function()
  File "/home/docs/local/lib/python2.7/site-packages/south/migration/migrators.py", line 60, in <lambda>
    return (lambda: direction(orm))
  File "/home/docs/checkouts/readthedocs.org/readthedocs/builds/migrations/0024_fix_slugs_with_leading_placeholders.py", line
21, in forwards
    version.slug = slug_field.create_slug(version)
  File "/home/docs/checkouts/readthedocs.org/readthedocs/builds/version_slug.py", line 145, in create_slug
    'Invalid generated slug: {slug}'.format(slug=slug))
AssertionError: Invalid generated slug: v

cc @gregmuellegger

Darn, sorry for the problems. I created #1407 as a fix.

Nice, I looked at the issue really quick and put together a PR at the same time. I'm closing mine out as your has more test coverage.


MCTS location data

./original - straight data from sqlserver from MCTS dump
./modified - cleaned up data, some by scripts, some by hand
./script - scripts used to massage the data

"Showing  142 changed files  with 549,969 additions and 0 deletions."
Are you just trying to increase your lines commited count?


Not sure if it's this mod causing server crash (Ticking World)

It was working fine for quite a while
crash-2021-05-07_15.46.48-server.txt
crash-2021-05-07_09.18.07-server.txt

Unrelated (was issue with Puddles mod, fixed in release 1.1.0)


Clean install from Docker gitea/gitea:latest ends with error 'open /data/gitea/LOG: is a directory'

Gitea version (or commit ref): sorry but no idea, this one - image: gitea/gitea:latest
Git version:
Operating system: WSL2 Docker
Database (use [x]):

[ ] PostgreSQL
[X] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[X] Not relevant

Log gist:

Description
Brand new instalation from Docker with gitea/gitea:latest (sorry, guys, no idea what current version is, but this one ) ends with error
version: "3.8"

services:
    gitea:
        image: gitea/gitea:latest # with 1.12.5 everything work - image: gitea/gitea:1.12.5
        environment:
            USER_UID: 1000
            USER_GID: 1000
            DB_TYPE: mysql
            DB_HOST: gitea-db:3306
            DB_NAME: gitea
            DB_PASSWD: 123 # please note these are not my real passwords
            SECRET_KEY: 456 # please note these are not my real secrets
            REQUIRE_SIGNIN_VIEW: "true"
#        restart: always # commented to better see the log after failing
        volumes:
            - ./gitea/data:/data
        depends_on:
            - gitea-db
        ports:
            - "3000:3000"
            - "222:22"

    gitea-db:
        image: mariadb:latest
        environment:
            MYSQL_DATABASE: gitea
            MYSQL_ROOT_PASSWORD: 123 # please note these are not my real passwords
            MYSQL_PASSWORD: 123 # please note these are not my real passwords
        restart: always
        volumes:
            - ./gitea/maria-db:/var/lib/mysql

Log (i formated it a little):
2020/10/03 10:29:02 ...eue/queue_wrapped.go:231:Run()
[F] Unable to set the internal queue for issue_indexer-wrapper
Error: Unable to create queue level for issue_indexer with cfg {"Addresses":"","BatchLength":20,"BlockTimeout":1000000000,"BoostTimeout":300000000000,"BoostWorkers":5,"ConnectionString":"/data/gitea","DBIndex":0,"DataDir":"/data/gitea/indexers/issues.queue","MaxWorkers":10,"Name":"issue_indexer","Network":"","Password":"","QueueLength":20,"QueueName":"issue_indexer_queue","SetName":"","Workers":1}
by max attempts:

error: open /data/gitea/LOG: is a directory

(looks like you guys are trying to open log directory as a file? IDK 😃 )
When i pull older version (image: gitea/gitea:1.12.5) everything works. Still, cant update to :latest with the same error message.

Can we see your app.ini ?

I think I've worked it out. Sorry about this.

Oh, sorry for delay, idk if it help you now (looks like you managed without it 😄 ), but there it is:
APP_NAME = Gitea: Git with a cup of tea
RUN_MODE = dev

[repository]
ROOT = /data/git/repositories

[repository.local]
LOCAL_COPY_PATH = /data/gitea/tmp/local-repo

[repository.upload]
TEMP_PATH = /data/gitea/uploads

[server]
APP_DATA_PATH    = /data/gitea
DOMAIN           = localhost
SSH_DOMAIN       = localhost
HTTP_PORT        = 3000
ROOT_URL         =
DISABLE_SSH      = false
SSH_PORT         = 22
SSH_LISTEN_PORT  = 22
LFS_START_SERVER = false
LFS_CONTENT_PATH = /data/git/lfs

[database]
PATH    = /data/gitea/gitea.db
DB_TYPE = mysql
HOST    = gitea-db:3306
NAME    = gitea
USER    = root
PASSWD  = 123

[indexer]
ISSUE_INDEXER_PATH = /data/gitea/indexers/issues.bleve

[session]
PROVIDER_CONFIG = /data/gitea/sessions

[picture]
AVATAR_UPLOAD_PATH            = /data/gitea/avatars
REPOSITORY_AVATAR_UPLOAD_PATH = /data/gitea/repo-avatars

[attachment]
PATH = /data/gitea/attachments

[log]
ROOT_PATH = /data/gitea/log

[security]
INSTALL_LOCK   = true
SECRET_KEY     = 456
INTERNAL_TOKEN = eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJuYmYiOjE2MDE3NDYxMjJ9.M-DDo3tvsyce80q914k4HlRB5P8Uszd23BHNJheYlSs

[service]
DISABLE_REGISTRATION = false
REQUIRE_SIGNIN_VIEW  = true

[oauth2]
JWT_SECRET = stx0JlLb-1LZZBz1rHzoiga5_Vtma_Kwxzgw-dAZCEs

Workaround for the moment is to set the CONN_STR for each of the queues individually - which is a bit crap - or have a common queue:
[queue]
CONN_STR=/data/gitea/queues

Hopefully we'll get the PR merged very soon though


improve logo display and fix alignment on webkit

Alignment differs on FF and Chrome, -webkit-padding-after helps fixing the line-height.

Should you not update the version number ?


Staff online status design related issues

Sir wants to see in normal text, small text (not bold)

Staff name
Working Company name
Service
Year & Periods

In current status bar on mouse over some details from above list are available,
User wants to see above details, without mouse over if possible.
Like this, just example

I think Title of Timesheet is more Important

I think Title of Timesheet is more Important

@vinpahilwani


"ZALĂU" is listed in the drop-down menu

Description:
"ZALĂU" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "ZALĂU" in the search bar.
Expected results
The location is listed in the drop-down menu as "Oras ZALĂU, SĂLAJ (ZALĂU)".


Error 404 on Webserver

Expected Behaviour
The transit map appears
Actual Behaviour
Error 404
Reproduction Steps
Steps to reproduce the behaviour:

Start the server with the mod
Open IP:8888/index.html

Screenshots

Environment

Minecraft Version: 1.19.2
Installed Mods: Modlist

Additional Information
The server is running on docker with this image and behind a VPN. TCP port 8888 is opened through the VPN, firewall and docker config.

http://localhost:8888/index.html

they already specified that they are going to this link

Reproducible on Quilt Loader 0.23.1, the online system map cannot be accessed and only works on Fabric and Forge.
[02:40:16] [Server thread/INFO]: Started m.l.o.e.j.s.ServletContextHandler@306c527a{/,null,AVAILABLE}

This should be fixed in 4.0.0. Please reopen this bug if you still encounter this issue with 4.0.0, thanks!


Image not loaded on modal

     Hello

I am trying to use this with bootstrap modal and image seems not loading on scroll.
Is there anyway to work around this matter?
Thanks :)

Would it be appropriate for a modal? That wouldn't react to a scroll.
I don't really understand the problem. Please publish an example page so I can see what you're trying to achieve.

Pls check this demo.
https://jsfiddle.net/quang_it/b1tufkrq/3/

It's not the modal or styles. The JS in your demo is preventing progressive-image.js from running. It's possibly cancelling the window load event and there's nothing I can add to prevent that.
If you got it running, you'd possibly have the problem that the window isn't actually scrolled when the modal is active - it's the modal that's scrolled. That could be addressed, though.

Closing: fault due to other conflicts.


Release version 0.7.0

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (c59f149) to head (67c3fdf).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #602   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           71        71
  Lines         1896      1896
  Branches       225       225
=========================================
  Hits          1896      1896

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Increment to 4.8.0-SNAPSHOT for next development cycle

Is this PR waiting on anything? I think this sort of commit is usually just pushed directly to master by the release manager. But @whikloj, if you need someone else to push the merge button, I'd be happy to oblige.

@acoburn no not waiting on anything, I asked that question in IRC @ 13:36 and it was suggested a PR. Perhaps I misunderstood @awoods. I have opened all those (8) PRs. I can close them and push them myself, if that is the process.

@whikloj from the IRC conversation, it looks like having PRs like this is fine. I'll merge them.


Remove uses of archaius2 config.getPrefixedView()

It currently has issues when combined with config interpolation

:thumbsup:

Can you elaborate on what the issues are? Why not fix the prefixed views in archaius2?

The issue is to do with config interpolation when using prefixedView, where if prefixedView is used, then the interpolator automatically expect the same prefix to be attached to the interpolated config.
e.g. if my.prefix.config=${ENV_VAR}, then using prefixed view with prefix=my.prefix, ENV_VAR will not be loaded as the interpolator will expect my.prefix.ENV_VAR instead.
We will fix archaius2, however as the fix is less clear right now we are doing this to be unblocked.


fix numbering of steps in quickstart

Signed-off-by: Joe Heck<EMAIL_ADDRESS>What this PR does / why we need it:

fixes broken/scattered numbering in the new quick-start tutorial

Release note:

/lgtm
/approve
/ok-to-test