Starting a conversation

Not sure if this is an appropriate place to post, but I really liked the ideas harpoon presents and wanted to explore where it can improve.
So, recently I have been working on a (slightly experimental) plugin that keeps the core idea of "file tagging", but improves upon some of the pitfalls I found when using harpoon. The plugin is called grapple.nvim.
Some of the core improvements that grapple has focused on are:

Persistence: grapple takes a different approach to how file tags are saved
Project scope: grapple adds numerous builtin and custom "project directory" resolution options for file tags

The README in the repo goes into more detail on these topics (and more), if you're interested in reading it.
My goal by posting here is not at all to promote grapple, but to start a (hopefully) healthy and meaningful conversation that can benefit both plugins in the long-term.
I'd be happy to discuss further. However, I'm way off-base here and this is wildly inappropriate please feel free to close this issue.

How does grapple handle scratch buffers?
Did you measure perf impacts of adding alot tag context and resolving logic?
How does grapple handle paths outside of the git dirs, for example relative as ../../someproject ? Are then absolute paths used?
Does global namespace mean always valid? If so, then you should explain the precedence of resolving tag bindings or how clashes are handled otherwise.
Does grapple support direct access to unordered keybindings via keybindings, ie <leader>j opening the first git tag file? I dont see anything like this in the README. Thats my main use case for harpoon.

I kinda like the idea to have both global and local scoped tags into project files, but I feel like git-local tags of a project should be user-controllable read from the git repo.
For each git repos itself, there should be however a way to reference it and I dont understand, why harpoon has no overview of all the repos to make things like telescope-project superfluous.
I dont want yet another plugin to only :cd into a dir and keeping things duplicated.

How does grapple handle scratch buffers?

Grapple handles scratch buffers as good as it can with its data model. That is, a scratch buffer is tagged as a file with an empty "" file path.
This could certainly be improved on with better identification when the file path is not available. In addition, any tags associated with a scratch buffer should not be persisted (grapple does not currently do this).

Did you measure perf impacts of adding alot tag context and resolving logic?

Measure explicitly? No. I have run a few empirical tests with 100+ tags and no slow down was observed. I have little experience benchmarking, but would be glad to try and run a few to get a measurable baseline.

How does grapple handle paths outside of the git dirs, for example relative as ../../someproject ? Are then absolute paths used?

Absolute paths are always used. There are pros and cons to that decision. The pros are that file tags don't have to know about what scope they're in, they just exist. The cons are that if the underlying directory that the tags are saved to move, they will all become invalid. But, how often are project directories moved around?

Does global namespace mean always valid? If so, then you should explain the precedence of resolving tag bindings or how clashes are handled otherwise.

The global scope is simply a special scope that is given the name __global__ where all tags would be saved to if the user chooses that scope.
I'm not entirely sure I understand your last comment here. Scopes are not (currently) chosen dynamically. The scope itself will resolve dynamically (e.g. git), but the user will only set the scope type once during startup. There is no precedence to be had between scopes types like global and git, they exist on their own. If the user chooses global during plugin setup, then Grapple will only show tags that have been saved globally.
The only precedence that exists is for scope types that could fail, i.e. git. In this case the fallback scope is stated for when the user is not in a git repo:

git: tags are scoped to the current git repository, fallback: static

I hope that answered your question! Apologies if I'm misunderstanding the question.

Does grapple support direct access to unordered keybindings via keybindings, ie j opening the first git tag file? I dont see anything like this in the README. Thats my main use case for harpoon.

Good question! I suppose this isn't mentioned explicitly in the docs. The API method grapple#cycle (you will have to expand the Usage section to access the link) will default to the first tag when invoked. So, if you don't have any files open or are in a file that is not tagged, the first tagged file would be selected.

I kinda like the idea to have both global and local scoped tags into project files, but I feel like git-local tags of a project should be user-controllable read from the git repo.

Do you mean that tags should be saved to the local git repo / directory, rather than to a known save path like vim.fn.stdpath("data") / "harpoon.json"? That could be an interesting avenue to explore. I kind of like that :)

For each git repos itself, there should be however a way to reference it and I dont understand, why harpoon has no overview of all the repos to make things like telescope-project superfluous.

This could be a good improvement. Some overview or good way to manage all your tags across repos would be fantastic. Grapple has some support for this, but needs improvement since Grapple now lazily loads scopes.

I will definitely be looking into this. I am off on a medical leave right now, but I will be back in the new year. I do plan on rewriting harpoon from the ground up. I just allowed a bunch of PR to get in so that people's wants could be met. But I do want to take it in a slightly different direction.
Effectively allow much more plug and play as opposed to trying to bring features in.

@ThePrimeagen Any details on when you might start a rewrite and or a more detailed plan of the direction you'd like to take it? Harpoon has become a core part of my workflow and would love to see where it's going and contribute if possible

@skdillon +1

i am planning on the rewrite next week.
I want to get 2 crucial plugins back up and running in my life.

harpoon getting fixed up and back to a fighting state
vim-apm -- think of something funny here

that is my next week goal

Rewrite it in Rust
🦀 💥 🚀

Effectively allow much more plug and play as opposed to trying to bring features in.

I would appreciate more direct control of things:
M.setCursorToBottom = function(harpoon_term_nr)
  local term_handle = harp_term.getBufferTerminalId(harpoon_term_nr)
  local buf_id = term_handle["buf_id"]
  local term_id = term_handle["term_id"]
  local windows = vim.fn.win_findbuf(buf_id)
  if #windows ~= 1 then
    return
  end
  local crowcount = vim.api.nvim_buf_line_count(0)
  vim.api.nvim_win_set_cursor(windows[1], { crowcount, 0 })
end


Don't panic on empty insert

Fixes #137

 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.


Instructions to use Ruff with other servers in Kate

Summary
Provide instructions to use Ruff together with other servers in the Kate editor.
Because Kate does not support running multiple servers for the same language, one needs to use the python-lsp-server (pylsp) tool.

Hi @dhruvmanila could you elaborate on the settings part?
As far as I can tell, you can provide a toml file via the pylsp-ruff "config" option. Do you mean that the ruff executable and the language server have different options, or did I misunderstand?
Otherwise, just let me tell you why I did it that way:

I don't think many people are knowledgeable about tools like ruff, jedi, or pylsp, so providing a config file they can simply copy-paste and have things work (well, almost, since they need to specify the path) is desirable
Quite frankly, I don't think anyone would want to use the current configuration instructions for Kate since they make it lose basic goto functionalities
It also took me quite a while to figure this out, so I thought I would just save others the trouble by providing everything 😉
using "details", it doesn't really take much space and I would not expect these instructions to be much of a maintenance burden

That being said, I understand if you do not want to risk that burden, or having people asking about how to use pylsp-ruff in your issue tracker.
In that case let me know if adding a disclaimer at the top of the details to tell people they should ask pylsp-ruff people if anything doesn't work would be enough, otherwise I'll just remove the details and paraphrase what you said, as requested.

As far as I can tell, you can provide a toml file via the pylsp-ruff "config" option. Do you mean that the ruff executable and the language server have different options, or did I misunderstand?

I mean the server settings as mentioned here: https://docs.astral.sh/ruff/editors/settings. Some of them controls the behavior of the server itself (ruff.lint.enable, etc.) while others overrides the config values (ruff.lint.select, etc.).
I think your reasoning makes sense but I'd rather prefer to re-use existing resources from other documentations. There have been some confusion in the past with how the server settings are suppose to work like https://github.com/astral-sh/ruff/issues/12778 and https://github.com/astral-sh/ruff/issues/12514 where the users were confused that the server settings weren't being considered when running the linter / formatter.
I think having a general guide on how to setup the python-lsp-server in Kate would be useful to more users while having it here would only benefit the Ruff users.
I think a general user of python-lsp-server would find it more useful to refer to a guide on setting it up in Kate rather than a Ruff user. It's not about maintenance burden but thinking on how much benefit does this provide to Ruff users. I hope this reasoning makes sense.
That said, I think it would be more useful to expand the note by informing the users that they could use python-lsp-server along with python-lsp-ruff to use Ruff with an existing language server along with relevant references like python-lsp-ruff configuration options.

I mean the server settings as mentioned here: https://docs.astral.sh/ruff/editors/settings. Some of them controls the behavior of the server itself (ruff.lint.enable, etc.) while others overrides the config values (ruff.lint.select, etc.).
I think your reasoning makes sense but I'd rather prefer to re-use existing resources from other documentations. There have been some confusion in the past with how the server settings are suppose to work like #12778 and #12514 where the users were confused that the server settings weren't being considered when running the linter / formatter.

OK, I think this should probably be mentioned in the note, then.
Since you have much more experience with this confusion issue, would you have an idea about how to phrase that?

I think having a general guide on how to setup the python-lsp-server in Kate would be useful to more users while having it here would only benefit the Ruff users. I think a general user of python-lsp-server would find it more useful to refer to a guide on setting it up in Kate rather than a Ruff user. It's not about maintenance burden but thinking on how much benefit does this provide to Ruff users. I hope this reasoning makes sense.

As I mentioned, I don't think people know much about these tools and would expect them to have heard (like me) that ruff is super fast and so they would want to use it and would just arrive on the ruff docs without prior knowledge.
However, I  completely understand your reasoning and definitely agree that it would be better to have the detailed doc where it belongs (somewhere in the pylsp ecosystem) and just link to it in the ruff documentation.

That said, I think it would be more useful to expand the note by informing the users that they could use python-lsp-server along with python-lsp-ruff to use Ruff with an existing language server along with relevant references like python-lsp-ruff configuration options.

I'll propose something along those lines, then, and maybe I'll make another PR once I have added the detailed configuration somewhere in the pylsp documentation.

OK, that seems reasonable! I'll try to propose something to python-lsp people, thanks!


Modal code and trigger button

I added modal code in the HTML and a little modification to the description part of the card and the link trigger code. there is also a portion adjusted on the CSS to accommodate the trigger button.

Book Title
                        **
                           click for description**

Where to purchase

Have taken provided code and integrated in branch im working on right now with a few additional features. Cheers!


Chief Scientist doesn't show in VARS X query

See attached. Not all chief scientists with dives loaded to VARS X are listed for query (example: Ken Smith)

Moved to vars-query repo


Fix parsing of segments with required but empty DEGs where all subfields are optional

Fixes #304
Not sure if a similar fix is necessary for the DEG parsing function, though probably not because DEG field delimiters need to be present even for empty subfields for the indices of subsequent fields to match. So probably the existing $allowEmpy logic in the DEG parsing function handles the same case there, and thus this fix is only necessary on the segment level.

to merge or not to merge for 3.0? :thinking:

Sure, why not. I think our tests are good enough to be reasonably sure that this doesn't break anything else. And if it does, we'll just have to push out 3.0.1 shortly after...


react-scripts says There was an error trying to load the config "relay"

I cloned this repository and just run issue-tracker app, then I got error message:
[react-scripts] There was an error trying to load the config "relay" for the macro imported from "babel-plugin-relay/macro. Please see the error thrown for more information.

App runs normally even with this message, so I think this is not big problem.
Whole log is below
❯ yarn -v
Now using node v12.13.0 (npm v6.12.0)
1.19.1

❯ yarn start
yarn run v1.19.1
$ yarn run relay; concurrently --kill-others --names "react-scripts,relay" "react-scripts start" "yarn run relay --watch"
$ yarn run relay-compiler --schema schema/schema.graphql --src ./src/ $@
$ /Users/adwd/ghq/github.com/relayjs/relay-examples/issue-tracker/node_modules/.bin/relay-compiler --schema schema/schema.graphql --src ./src/
HINT: pass --watch to keep watching for changes.

Writing js
Updated:
 - Issues_repository.graphql.js
 - IssueDetailComments_issue.graphql.js
 - IssueActions_issue.graphql.js
 - IssuesListItem_issue.graphql.js
Unchanged: 8 files
$ yarn run relay-compiler --schema schema/schema.graphql --src ./src/ $@ --watch
$ /Users/adwd/ghq/github.com/relayjs/relay-examples/issue-tracker/node_modules/.bin/relay-compiler --schema schema/schema.graphql --src ./src/ --watch
[relay]
[relay] Writing js
[relay] Unchanged: 12 files
[relay] Watching for changes to js/jsx...
[relay] Watching for changes to graphql...
[react-scripts] Starting the development server...
[react-scripts]
[react-scripts] There was an error trying to load the config "relay" for the macro imported from "babel-plugin-relay/macro. Please see the error thrown for more information.
[react-scripts] There was an error trying to load the config "relay" for the macro imported from "babel-plugin-relay/macro. Please see the error thrown for more information.
[react-scripts] There was an error trying to load the config "relay" for the macro imported from "babel-plugin-relay/macro. Please see the error thrown for more information.
[react-scripts] There was an error trying to load the config "relay" for the macro imported from "babel-plugin-relay/macro. Please see the error thrown for more information.
[react-scripts] There was an error trying to load the config "relay" for the macro imported from "babel-plugin-relay/macro. Please see the error thrown for more information.
[react-scripts] There was an error trying to load the config "relay" for the macro imported from "babel-plugin-relay/macro. Please see the error thrown for more information.
[react-scripts] There was an error trying to load the config "relay" for the macro imported from "babel-plugin-relay/macro. Please see the error thrown for more information.
[react-scripts] Compiled successfully!
[react-scripts]
[react-scripts] You can now view issue-tracker in the browser.
[react-scripts]
[react-scripts]   Local:            http://localhost:3000/
[react-scripts]   On Your Network:  http://<IP_ADDRESS>:3000/
[react-scripts]
[react-scripts] Note that the development build is not optimized.
[react-scripts] To create a production build, use yarn build.
[react-scripts]

Same issue here.

Its from babel macros, you can ignore or add a file .babel-plugin-macrosrc.yml with
relay: ~

with its contents in project directory.

Thanks ! 👍


Fixed #26973 -- Fixed views.static.serve() crash with show_indexes enabled.

https://code.djangoproject.com/ticket/26973

Or would it be possible to feed the libraries argument to engine()? Did you plan to write a test for that?

I didn't care to spend much time on this issue as I think this will be deprecated as described in https://groups.google.com/d/msg/django-developers/N0KbgDeLuUE/THUq64NjDwAJ.
If you want to try an alternate patch and write a test, I won't oppose it.

Wow nice, many thanks for taking care of this!


Unknown Error: The read operation timed out

Prerequisites

Yes
Yes
Yes

Description
when I tried using the "Download from bookmarked images" feature to download all my favorite works, it started importing bookmarks from my pixiv account to a certain page that I had pre-filled and suddenly it stopped working and gave an error like the image below, sorry I used Google translate because my English is not very good, thanks for reading!
Expected behavior: download all my favorite works
Actual behavior: it not worked
Log file::
pixivutil.log
Versions: v20230105

similar like #1229, most likely the server reject the connection for whatever reason


add allowDeclarationsAfterNestedRules option

updated README with new option
added type comment for postcss 8
added tests for the new option specifically

I don't see that we've dropped the support for PostCSS 7 as discussed. Is that meant to come later? Would you like me taking care of that? I think this will also simplify the testing moving forward.

This should be separate (imho) because one doesn't really have much to do with the other :)


[FEATURE] Create stackql-deploy init starter project for google

Sure! Here’s a detailed GitHub issue for creating a stackql-deploy starter template for Google Cloud Platform (GCP), starting with a project and including additional components for a complete "Hello IaC" project.

Feature Description
Create a starter template for stackql-deploy for the gcp provider, including the following components:

A GCP Project
A VPC Network
A Subnet
A Firewall Rule
An External IP Address
A Compute Instance

Example(s)
The starter template should be invoked using:
stackql-deploy init my-stack --provider google

Example Template YAML
provider: google
resources:
  project:
    project_id: my-project
    name: My Project
  vpc_network:
    name: my-vpc
    auto_create_subnetworks: false
  subnet:
    name: my-subnet
    ip_cidr_range: <IP_ADDRESS>/24
    region: us-central1
    network: my-vpc
  firewall_rule:
    name: allow-http-ssh
    network: my-vpc
    allowed:
      - protocol: tcp
        ports:
          - "22"
          - "80"
    source_ranges:
      - "<IP_ADDRESS>/0"
  external_ip_address:
    name: my-external-ip
  compute_instance:
    name: my-instance
    machine_type: e2-micro
    zone: us-central1-a
    subnetwork: my-subnet
    external_ip: my-external-ip
    image:
      family: debian-10
      project: debian-cloud
    boot_disk:
      initialize_params:
        size: 10
        type: pd-standard

completed use stackql-deploy init my-google-project --provider google


Add automatic version detection/switching

Overview
Would it be possible to support automatic version switching much like chruby's auto-switching?
Screenshots/Screencasts
The following captures the problem of having to manually switch Ruby versions when switching between projects:
https://user-images.githubusercontent.com/50245/126048754-17938534-9ac8-4e32-ae65-54ef068568aa.mp4
Steps to Recreate
Run the following:
frum --frum-dir "$HOME/.cache/frum" install 3.0.0
frum --frum-dir "$HOME/.cache/frum" install 3.0.2
printf "%s\n" "3.0.2" > $HOME/.ruby-version
mkdir zero
printf "%s\n" "3.0.0" > "zero/.ruby-version"
cd zero
cd ..
cd zero

Notice that Frum never detects the correct version (global versus local).
Desired Behavior
As shown in the screencast and steps above, Frum doesn't distinguish between the global, system-wide Ruby version of 3.0.2 versus the local project version of 3.0.0. You have to manually set the Ruby version you desire each time you switch a directory.
Environment

Operating System: macOS 11.4 (20F71)
Frum: 0.1.0

@bkuhlmann Thank you for opening the issue! You can set frum-dir as an environment variable like the following capture. And I think this way solve the problem. I'm sorry I forgot to mention this feature in README. I'm going to add a description to README.
https://user-images.githubusercontent.com/41065217/126057215-002fc8ee-5989-4a84-ac2e-f358891c2b81.mov

:bow: Takayuki, ah, this is excellent to learn -- yes, adding this information to the README would be most welcome. 😄 By the way, thanks for the work on this project. Looking forward to making more use of Frum in all of my projects.

@bkuhlmann
I'm glad to hear that :) I'll keep on making frum better. I've added this information to README in https://github.com/TaKO8Ki/frum/pull/86.

:information_source: I'm enjoying Frum and switched all systems to using it then decided to update my article on Ruby Version Managers to default to Frum instead of chruby. 😄


dragonfly is unstable with high latency

Ⅰ. Issue Description
I tested dragonfly in a kubernetes cluster of 300 nodes which were 2c4g vms.
The purpose of the test was to see the stability of dragonfly in distributing files across multiple nodes.
It turned out that dragonfly became unstable after running a while.
The testing procedure is as follows:

Supernode starts with arg "--max-bandwidth 10000000MB".
Every node has a downloader with dfget on it. Every downloader watches a key called "/new/file" in etcd.
A container uses "python3 -m http.server" to serve http requests. It also generates new random file which is 50MB and modifies the value of key "/new/file" in etcd every 30 seconds.
Downloaders get the etcd events simultaneously, then trigger the "dfget --url=<the_url> --notbs --locallimit=10G --totallimit=10G --node=<supernode_addr> -o <output_path>" command.

Ⅱ. Describe what happened
Everything seems fine at the beginning. But about 50 minutes later, the metrics became unstable. Dfget failures started to happen, and the download latency increased.

Ⅲ. Describe what you expected to happen
For the nodes in cluster were stable, the metrics should be stable too.
Ⅳ. How to reproduce it (as minimally and precisely as possible)
Ⅴ. Anything else we need to know?
I can provide the logs of supernode and dfclient if you need.
Ⅵ. Environment:

dragonfly version: 24c40b947859a04325a4f8883ad6efe3f71ebca2
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

Could you paste related logs of dfget? see FAQ to get logs.

Could you paste related logs of dfget? see FAQ to get logs.

I can only find some logs like this.
2019-11-04 15:23:54.407 INFO sign:347-1572852234.407 : get cmd params:["dfget" "--url=http://<IP_ADDRESS>:12347/27.model" "--notbs" "--locallimit=10G" "--totallimit=10G" "--node=dfsupernode:8002" "-o" "/save/27.model"]
2019-11-04 15:23:54.407 INFO sign:347-1572852234.407 : get init config:{"url":"http://<IP_ADDRESS>:12347/27.model","output":"/save/27.model","pattern":"p2p","notbs":true,"nodes":["dfsupernode:8002"],"localLimit":"10GB","minRate":"64KB","totalLimit":"10GB","clientQueueSize":6}
2019-11-04 15:23:54.407 INFO sign:347-1572852234.407 : target file path:/save/27.model
2019-11-04 15:23:55.407 ERRO sign:347-1572852234.407 : Connect to node:dfsupernode:8002 error: dial tcp: i/o timeout
2019-11-04 15:23:55.414 INFO sign:347-1572852234.407 : runtimeVariable: {"MetaPath":"/root/.small-dragonfly/meta/host.meta","SystemDataDir":"/root/.small-dragonfly/data","DataDir":"/root/.small-dragonfly/data","RealTarget":"/save/27.model","TargetDir":"/save","TempTarget":"/save/dfget-347-1572852234.407.tmp-086707113","Cid":"<IP_ADDRESS>-347-1572852234.407","TaskURL":"http://<IP_ADDRESS>:12347/27.model","TaskFileName":"27.model-347-1572852234.407","LocalIP":"<IP_ADDRESS>","PeerPort":0,"FileLength":-1,"DataExpireTime":180000000000,"ServerAliveTime":300000000000}
2019-11-04 15:23:55.415 INFO sign:347-1572852234.407 : local http result:27.model-347-1572852234.407 err:<nil>, port:57838 path:/check/
2019-11-04 15:23:55.415 INFO sign:347-1572852234.407 : use peer server on port:57838
2019-11-04 15:23:55.415 INFO sign:347-1572852234.407 : do register to one of [dfsupernode:8002 dfsupernode:8002]
2019-11-04 15:24:00.415 INFO sign:347-1572852234.407 : do register to dfsupernode:8002, res:null error:timeout
2019-11-04 15:24:00.415 ERRO sign:347-1572852234.407 : register to node:dfsupernode:8002 error:timeout
2019-11-04 15:24:05.415 INFO sign:347-1572852234.407 : do register to dfsupernode:8002, res:null error:timeout
2019-11-04 15:24:05.415 ERRO sign:347-1572852234.407 : register to node:dfsupernode:8002 error:timeout
2019-11-04 15:24:05.415 ERRO sign:347-1572852234.407 : register fail:{"Code":-100,"Msg":"timeout"}
2019-11-04 15:24:05.415 WARN sign:347-1572852234.407 : register fail but try to download from source, reason:1({"Code":-100,"Msg":"timeout"})
2019-11-04 15:24:05.415 WARN sign:347-1572852234.407 : invalid download timeout(0.000s)
2019-11-04 15:24:05.415 INFO sign:347-1572852234.407 : download FAIL from supernode [] cost:11.008s length:-1 reason:1001

But what bothers me is the high latency which was about 30s.
Could you paste the log and the io/network details of supernode at that time.

grep the taskID 93fa39eff4af850e15eeaeab0c8ed8d147e8d9a69a7d024ef3bc1afd76c1e68e to get the related log.


Patch elyra kfp template with latest change for TensorFlow

Patch elyra kfp template with latest change for TensorFlow
Description

Inclusion of patch for successful use of Tensorflow image with pipelines
https://issues.redhat.com/browse/RHOAIENG-6853
Related-to: https://issues.redhat.com/browse/RHOAIENG-6486
How Has This Been Tested?

Run pipeline from the Tensorflow image.
Merge criteria:

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

tested on cluster:

Merging it.


Deprecation Warning 2024.7.0

Is your feature request related to a problem? Please describe.
There is a new deprecation warning  in HA 2024.7.0 appearing in the logs
Describe the solution you'd like
Update integration
Describe alternatives you've considered
N/A
Additional context
Log message below
Detected that custom integration 'dahua' calls async_forward_entry_setup for integration, dahua with title: NVR 6 and entry_id: 19c39c8e048176b3a713a86601569bd2, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead at custom_components/dahua/__init__.py, line 85: hass.async_create_task(, please create a bug report at https://github.com/rroller/dahua/issues
May be a HACS thing https://github.com/hacs/integration/issues/3850

I get almost the same error but it says it will be depreciated in 2025.1 instead of 2025.6.
Detected code that calls async_forward_entry_setup for integration dahua with title: CamVooraan and entry_id: 3f9ab753ea282e390ca028ff8353924b, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.

Hi, I am getting the same warning for it being depreciated in 2025.1
Core 2024.7.3
Supervisor 2024.06.2
Operating System 12.4
Frontend 20240710.0
Logger: homeassistant.helpers.frame
Source: helpers/frame.py:151
First occurred: 2:34:15 PM (5 occurrences)
Last logged: 2:34:15 PM
Detected code that calls async_forward_entry_setup for integration dahua with title: Front Porch and entry_id: 2f89fa81c70ceffa86d8452f86534b4d, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.

Detected that custom integration 'dahua' calls async_forward_entry_setup for integration, dahua with title: CameraOprit and entry_id: e1bc3dd8f74b4d16a8a547831xxxxxxx, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead at custom_components/dahua/init.py, line 85: hass.async_create_task(, please create a bug report at https://github.com/rroller/dahua/issues


Add Sportsbet, Sportsbet.io and Tois Bet as hard.

Run script/check_files_formatting.sh
npm WARN exec The following package was not found and will be installed<EMAIL_ADDRESS>import-im6.q16: unable to open X server ' @ error/import.c/ImportImageCommand/3[4](https://github.com/jdm-contrib/jdm/actions/runs/5212451545/jobs/9406062629?pr=1674#step:4:5)6. import-im6.q16: unable to open X server ' @ error/import.c/ImportImageCommand/346.
import-im6.q16: unable to open X server ' @ error/import.c/ImportImageCommand/346. import-im6.q16: unable to open X server ' @ error/import.c/ImportImageCommand/346.
import-im6.q16: unable to open X server ' @ error/import.c/ImportImageCommand/346. import-im6.q16: unable to open X server ' @ error/import.c/ImportImageCommand/346.
import-im6.q16: unable to open X server ' @ error/import.c/ImportImageCommand/346. import-im6.q16: unable to open X server ' @ error/import.c/ImportImageCommand/346.
/home/runner/.npm/_npx/6c526599faa30dd1/node_modules/.bin/editorconfig-cli: 1: -v: not found
/home/runner/.npm/_npx/6c526599faa30dd1/node_modules/.bin/editorconfig-cli: 1: --verbose: not found
/home/runner/.npm/_npx/6c526599faa30dd1/node_modules/.bin/editorconfig-cli: 11: const: not found
/home/runner/.npm/_npx/6c526599faa30dd1/node_modules/.bin/editorconfig-cli: 12: Syntax error: "(" unexpected
Error: Process completed with exit code 2.
What is that error?


Add support for non-empty volumes

We should support mounting non-empty volumes from the host environment. For example:
volumes:
    # Path on the host, relative to the Compose file
    - ./cache:/tmp/cache

Note: Do not try to support user-relative paths, e.g. ~/configs:/etc/configs/:ro. We should assume the data comes from a hosted git repository (e.g. GitHub).
Relevant context:
Since issue uffizzi_core#126, we are supporting "empty" named volumes, e.g.:
volumes:
    mydata:
    dbdata:

We should add support for both short and long syntax:
Short syntax
volumes:
    # Path on the host, relative to the Compose file
    - ./cache:/tmp/cache

Long syntax
From the long syntax we should support source, target and read-only.
services:
  web:
    image: nginx:alpine
    ports:
      - "80:80"
    volumes:
      - type: volume
        source: mydata
        target: /data
        volume:
          nocopy: true
      - type: bind
        source: ./static
        target: /opt/app/static

networks:
  webnet:

volumes:
  mydata:


Update 3.1-to-5.0 migration guide for ASP.NET Core 5.0 RC2

Update the following doc for RC2:
https://docs.microsoft.com/aspnet/core/migration/31-to-50
Incorporate details mentioned at https://devblogs.microsoft.com/aspnet/asp-net-core-updates-in-net-5-release-candidate-2/

@scottaddie @Rick-Anderson ... Confirm if you still want me to handle the Blazor section of the file. :ear: I'm almost done with the Blazor .NET 5 updates 😁. I'll be available perhaps tomorrow (Friday) morning to work on it.
WRT timing ... Given that I would be touching sections not touched by other PRs (and if I leave the date alone), I don't think that any merge conflict :boom: will crop up (or be difficult to resolve if it happens). If you prefer that I hold off and work on the doc ... say ... this weekend ... yeah, I can do that. Let me know if you think I should wait until existing PRs are merged into it before doing the work. :ear:

@guardrex Yes, please work on the Blazor section. I'll work on the rest of it.

btw --- I have 😈 one pesky Blazor WASM security scenario 😈 left to work out. I've asked Jean-Marc for a tip, but I also have a clue as to what might be wrong. Anyway ... my week is burned, so it will have to wait until Monday morning. I'll get to the Blazor updates for the migration topic for sure by EOD on Monday.


ref(), & unref() return value

We understand you have a problem and are in a hurry, but please provide us with some info to make it much more likely for your issue to be understood, worked on and resolved quickly.

Lolex version : 2.6.0
Environment   : NodeJS v8.11

What did you expect to happen?
According to NodeJS documentation the ref() and unref() return the timer.
https://nodejs.org/dist/latest-v8.x/docs/api/timers.html#timers_timeout_ref
What actually happens
But lolex returns undefined.
How to reproduce
const lolex = require("lolex");
const clock = lolex.install();

const timer = setTimeout(() => {}, 5000).unref();
console.log(timer);
// Prints: undefined

If you comment out the lolex.install() line, it prints the NodeJS Timeout object.
Thank you!

Grep the lolex code for unref and see what it does (or look at the code, it's just a couple of hundred lines in one file). I haven't encountered that before. Maybe we just define the function but no implementation. Wouldn't know, but I do know we accept PRs ;)

yes, I checked the code, only need to change ~2 lines. I'm making a PR.


guideguide.ZXPInstaller version 1.6.3

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

I'm not sure if zxpinstaller actually is for a neutral architecture, if someone can help find out for me i'd be glad.

@Touchcreator you could try the https://github.com/microsoft/winget-create tool to see what it detects.


Unresolved class CropImageActivity in Manifest

Hello!
Help me, please.
Error in Manifest file: Unresolved class CropImageActivity
<activity android:name="com.theartofdev.edmodo.cropper.CropImageActivity"
<EMAIL_ADDRESS>
and in MainActivity:
Cannot resolve symbol 'CropImage'
import com.theartofdev.edmodo.cropper.CropImage;
import com.theartofdev.edmodo.cropper.CropImageView;

Project.gradle
buildscript {
    repositories {
        jcenter()
        google()
        maven {
            url 'https://maven.fabric.io/public'
        }
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.0.1'
        classpath 'com.google.gms:google-services:3.1.2'
        classpath 'io.fabric.tools:gradle:1.24.4'
        classpath 'com.google.firebase:firebase-plugins:1.1.5'
        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

allprojects {
    repositories {
        jcenter()
        maven {
            url "https://maven.google.com" // Google's Maven repository
        }
        maven { url 'https://jitpack.io' }
        google()
    }
}

Module.gradle:
apply plugin: 'com.android.application'
apply plugin: 'io.fabric'
apply plugin: 'com.google.firebase.firebase-perf'

android {
    compileSdkVersion 27
    buildToolsVersion "27.0.3"

    defaultConfig {
        applicationId "com.kostasoft.help_signal_purchase"
        minSdkVersion 17 //Build.VERSION_CODES.JELLY_BEAN
        targetSdkVersion 27
        versionCode 67
        versionName "beta"
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
        resConfigs "auto"
        multiDexEnabled true
    }
   ...
}
dependencies {
   compile 'com.theartofdev.edmodo:android-image-cropper:2.6.0' //implementation
   ...
}

Android Studio 3.0.1

Manifest file:-

<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />

<application
    android:allowBackup="true"
    android:icon="@drawable/image_cropper"
    android:label="@string/app_name"
    android:roundIcon="@mipmap/ic_launcher_round"
    android:supportsRtl="true"
    android:theme="@style/AppTheme">
    <activity android:name=".MainActivity">
        <intent-filter>
            <action android:name="android.intent.action.MAIN" />

            <category android:name="android.intent.category.LAUNCHER" />
        </intent-filter>
    </activity>
    <activity
        android:name="com.theartofdev.edmodo.cropper.CropImageActivity"
<EMAIL_ADDRESS>/> <!-- optional (needed if default theme has no action bar) -->
    <activity android:name=".Main2Activity"></activity>
</application>

MainActivity:--
import com.theartofdev.edmodo.cropper.CropImage;
import com.theartofdev.edmodo.cropper.CropImageView;
Project.gradle:--
buildscript {
repositories {
    google()
    jcenter()
}
dependencies {
    classpath 'com.android.tools.build:gradle:3.0.1'

    // NOTE: Do not place your application dependencies here; they belong
    // in the individual module build.gradle files
}

}
allprojects {
repositories {
google()
jcenter()
}
}
task clean(type: Delete) {
delete rootProject.buildDir
}
Module.gradle:--
android {
compileSdkVersion 26
defaultConfig {
applicationId "com.example.algo.image_cropper"
minSdkVersion 15
targetSdkVersion 26
versionCode 1
versionName "1.0"
testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
}
buildTypes {
release {
minifyEnabled false
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
}
}
}
dependencies {
implementation fileTree(dir: 'libs', include: ['*.jar'])
implementation 'com.android.support:appcompat-v7:26.0.0-beta1'
implementation 'com.android.support.constraint:constraint-layout:1.0.2'
testImplementation 'junit:junit:4.12'
compile 'com.theartofdev.edmodo:android-image-cropper:2.6.+'
androidTestImplementation 'com.android.support.test:runner:1.0.1'
androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.1'
}
gradle wrapper properties:-
distributionUrl=https://services.gradle.org/distributions/gradle-4.1-all.zip
i think now ur eroor may be solved.
really this is awesome library.

2 Biplovkumar
So what did I do wrong?

congrats,u have done.

How to clean the project?

Hey! I am also facing same problem can someone resolve it?

How to clean the project? Cause i am facing the same issue @kostasoft Its showing "Class referenced in the manifest, com.theartofdev.edmodo.cropper.CropImageActivity, was not found in the project or the libraries Unresolved package 'cropper'"

Did you find out how??? Cause I'm facing the same problem now

How to clean the project? Cause i am facing the same issue @kostasoft Its showing "Class referenced in the manifest, com.theartofdev.edmodo.cropper.CropImageActivity, was not found in the project or the libraries Unresolved package 'cropper'"

Did you find out how??? Cause I'm facing the same problem now

ı have same error too. Did you fint out how to fix?

Uhhh yeah, kind of... You just keep invalidating the cache and restart Android Studio or restart your whole freaking computer, it will work someday...
Well atleast it did for me 😑 #AndroidStudioSucks

Uhhh yeah, kind of... You just keep invalidating the cache and restart Android Studio or restart your whole freaking computer, it will work someday... Well atleast it did for me 😑 #AndroidStudioSucks

Hey I'm trying to get it done it isn't working can you tell me if it worked for you or what exactly you did? thanks so much

Uhhh yeah, kind of... You just keep invalidating the cache and restart Android Studio or restart your whole freaking computer, it will work someday... Well atleast it did for me 😑 #AndroidStudioSucks

Hey I'm trying to get it done it isn't working can you tell me if it worked for you or what exactly you did? thanks so much

Uhhh yeah, kind of... You just keep invalidating the cache and restart Android Studio or restart your whole freaking computer, it will work someday... Well atleast it did for me 😑 #AndroidStudioSucks

Hey I'm trying to get it done it isn't working can you tell me if it worked for you or what exactly you did? thanks so much

I kept cleaning the project and restarting the Android Studio
and suddenly one day, it started working...
BTW have you checked if your repositories are correct???

hey, cleaning and restarting is not working so i changed mavenCentral() to jcenter() in settings.gradle now its working.

funny thing, mine was already in jcenter()
well whtever, maybe Android Studio knows what was the real problem.🫠

hey, cleaning and restarting is not working so i changed mavenCentral() to jcenter() in settings.gradle now its working.

thanks buddy


Validating user provided values

What I am looking for is a way to validate values provided by a user to my charts.
For example the user can set a password and supply it to a chart. I need to make sure that this passwords is greater than x characters and so I require programatically being able to validate it and fail upon non-compliance to the requirements.
Is this something that is supported? is there a way that you recommend that I can use to work around it if not?

This is a question if it is already supported or a feature request if it is not supported yet. I'll edit the description accordingly once I receive feedback

I am not sure if there is a native clean way to do this.
I was able to do it by using include and required
for example I needed a password to be at least 6 characters
I created a template function that returns an empty string if the password is less than 6 characters and pipe it's output to required which then errors achieving the required behavior.
Template:
{{- define validate -}}
{{ $length := len .Value.Password }}
{{- if ge $length 6 -}}
{{ .Values.Password }}
{{- end -}}
{{- end --}}

pipeline
{{ include validate .  | required "Password needs to be at least 6 characters" }}

feel free to close the issue If this is the only way to do that and may be include it somewhere in the templating tips and tricks


Bug: db connection on android doesn't support ForeignKey

As said in documentation, connection should enable foreign key support in runtime.
Please, add configuration for this or make this behavior enabled by default

According to SQLDelight docs, Foreign support should be enabled during driver creation
https://cashapp.github.io/sqldelight/2.0.1/multiplatform_sqlite/foreign_keys/

Added new flags and callbacks to KabinDatabaseConfiguration in db530a3
Here's how you control ForeignKey behaviour:
val configuration = KabinDatabaseConfiguration(
    context = this,
    name = "sample-database",
    foreignKeyConstraintsEnabled = false
)

foreignKeyConstraintsEnabled is true by default

Changes were published to 0.1.0-alpha03


edit: remove $HOMEBREW_BAT_CONFIG_PATH

Fix #11974
brew use bat's default config path not $HOMEBREW_BAT_CONFIG_PATH

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

I have changed the default value of $HOMEBREW_BAT_CONFIG_PATH
Thanks.


Fixing Json_pure dependency problems

The json_pure gem dropped ruby <2.0 compatibility in version 2.0.2.
Fixing the Gemfile to take that in account.

Damn, the tests fail due to a change in the apt module again...
     Failure/Error: it { should compile.with_all_deps }
       error during compilation: Undefined variable "::puppetversion"; Undefined variable "puppetversion" at /home/travis/build/tubemogul/puppet-maxscale/spec/fixtures/modules/apt/manifests/params.pp:9 on node testing-worker-linux-docker-048d0ffc-3451-linux-9.prod.travis-ci.org


Allow using AMIs built for architectures other than amd64

Right now kip can only use one AMI specified via bootImageSpec in provider.yaml.
However, AMIs are specific to the OS and CPU architecture. To support other architectures and OSes (ARM, mac1, etc) we need to be able to specify a boot image filter for each.

@ldx @jrroman @henryprecheur What you guys think of having something really generic, such as:
bootImageSpec:
    amis:
      - familyRegex: "mac.*"
        owners:<PHONE_NUMBER>01
        filters: name=elotl-kip-*
     - familyRegex: "*" # default
       owners:<PHONE_NUMBER>01
       filters: name=elotl-kip-*

@ldx @jrroman @henryprecheur What you guys think of having something really generic, such as:
bootImageSpec:
    amis:
      - familyRegex: "mac.*"
        owners:<PHONE_NUMBER>01
        filters: name=elotl-kip-*
     - familyRegex: "*" # default
       owners:<PHONE_NUMBER>01
       filters: name=elotl-kip-*

@hidalgopl so the issue i see with this is it will break reverse compatibility with previous releases of kip. We could potentially add this for additional ami fields while keeping the base of owner and filter.  This is the way i have been testing currently:
 16   bootImageSpec:
 17     owners:<PHONE_NUMBER>01
 18     filters: name=elotl-kip-*
 19     macfilters: name=elotl-kipmac-*
 20     armfilters: name=elotl-kiparm-*

@hidalgopl so the issue i see with this is it will break reverse compatibility with previous releases of kip. We could potentially add this for additional ami fields while keeping the base of owner and filter.  This is the way i have been testing currently:
 16   bootImageSpec:
 17     owners:<PHONE_NUMBER>01
 18     filters: name=elotl-kip-*
 19     macfilters: name=elotl-kipmac-*
 20     armfilters: name=elotl-kiparm-*

@jrroman You're right, I haven't thought about it. We can keep backwards compatibility by keeping what I proposed under new key:
bootImageSpec:
     owners:<PHONE_NUMBER>01
     filters: name=elotl-kip-*
     overrideAMI:
      - familyRegex: "mac.*"
        owners:<PHONE_NUMBER>01
        filters: name=elotl-kip-mac*
     - familyRegex: "*" # default
       owners:<PHONE_NUMBER>01
       filters: name=elotl-kip-*

Big question is how flexible this feature needs to be. And whether we want to have different AMI for different arch, or different AMI for different instance type familiy.
For our current needs keys you added are fully sufficient. However, if ever we want to be able to have different AMI for different instance type/family, introducing changes would be tricky if we already have feature that chooses AMI based on arch.

@jrroman You're right, I haven't thought about it. We can keep backwards compatibility by keeping what I proposed under new key:
bootImageSpec:
     owners:<PHONE_NUMBER>01
     filters: name=elotl-kip-*
     overrideAMI:
      - familyRegex: "mac.*"
        owners:<PHONE_NUMBER>01
        filters: name=elotl-kip-mac*
     - familyRegex: "*" # default
       owners:<PHONE_NUMBER>01
       filters: name=elotl-kip-*

Big question is how flexible this feature needs to be. And whether we want to have different AMI for different arch, or different AMI for different instance type familiy.
For our current needs keys you added are fully sufficient. However, if ever we want to be able to have different AMI for different instance type/family, introducing changes would be tricky if we already have feature that chooses AMI based on arch.

@jrroman You're right, I haven't thought about it. We can keep backwards compatibility by keeping what I proposed under new key:
bootImageSpec:
     owners:<PHONE_NUMBER>01
     filters: name=elotl-kip-*
     overrideAMI:
      - familyRegex: "mac.*"
        owners:<PHONE_NUMBER>01
        filters: name=elotl-kip-mac*
     - familyRegex: "*" # default
       owners:<PHONE_NUMBER>01
       filters: name=elotl-kip-*

Big question is how flexible this feature needs to be. And whether we want to have different AMI for different arch, or different AMI for different instance type familiy.
For our current needs keys you added are fully sufficient. However, if ever we want to be able to have different AMI for different instance type/family, introducing changes would be tricky if we already have feature that chooses AMI based on arch.

bootImageSpec is a map[string]string, so making some values in the map lists or other data structures would break compatibility. I think an architecture prefix to keys should be a good first shot without adding too much complexity. We should get a canonical list of architectures and use those (i.e. same ones AWS uses in describe-images, e.g. x86_64, x86_64_mac, etc). So an example bootImageSpec might look like:
bootImageSpec:
  owners: 123456789
  x86_64-filters: name=elotl-kip-*
  x86_64_mac-filters: name=elotl-kip-mac-*

We can keep the current keys (filters, owners, etc) for backward compatibility.
Another missing piece: an instance family -> architecture mapping, so we know which architecture we need when starting an instance.

@jrroman You're right, I haven't thought about it. We can keep backwards compatibility by keeping what I proposed under new key:
bootImageSpec:
     owners:<PHONE_NUMBER>01
     filters: name=elotl-kip-*
     overrideAMI:
      - familyRegex: "mac.*"
        owners:<PHONE_NUMBER>01
        filters: name=elotl-kip-mac*
     - familyRegex: "*" # default
       owners:<PHONE_NUMBER>01
       filters: name=elotl-kip-*

Big question is how flexible this feature needs to be. And whether we want to have different AMI for different arch, or different AMI for different instance type familiy.
For our current needs keys you added are fully sufficient. However, if ever we want to be able to have different AMI for different instance type/family, introducing changes would be tricky if we already have feature that chooses AMI based on arch.

bootImageSpec is a map[string]string, so making some values in the map lists or other data structures would break compatibility. I think an architecture prefix to keys should be a good first shot without adding too much complexity. We should get a canonical list of architectures and use those (i.e. same ones AWS uses in describe-images, e.g. x86_64, x86_64_mac, etc). So an example bootImageSpec might look like:
bootImageSpec:
  owners: 123456789
  x86_64-filters: name=elotl-kip-*
  x86_64_mac-filters: name=elotl-kip-mac-*

We can keep the current keys (filters, owners, etc) for backward compatibility.
Another missing piece: an instance family -> architecture mapping, so we know which architecture we need when starting an instance.


[2.3.5] Codesign grouping bug

It looks like there is a bug with the CodeSign grouping code recently introduced to fix exporting an archive in Xcode 9.
We're trying to sign an app using the app-store method with both a main target and a push notification extension. It seems like there's a bug in picking out the correct code signing group, but I'm not entirely sure what it's being caused by:
Log:
certificate: 446FE307C20B96B8 included in profiles:

- O2 Touch Notification App Store
- iOS Team Store Provisioning Profile: com.englandrugby.o2touch
- iOS Team Store Provisioning Profile: com.englandrugby.o2touch.EventNotification
- O2 Touch App Store
certificate: 1B184E542FC908A3 included in profiles:

- iOS Team Store Provisioning Profile: com.rugbyfootballunion.o2touch
- O2 Touch App Store
- O2 Touch Notification App Store
- iOS Team Store Provisioning Profile: com.rugbyfootballunion.o2touch.EventNotification

certificate: 249F9F17BCC3055E included in profiles:
- iOS Team Provisioning Profile: com.rugbyfootballunion.o2touch
- iOS Team Provisioning Profile: com.rugbyfootballunion.o2touch.EventNotification

certificate: 5DA2A94D5F7D931E included in profiles:
- BitriseBot-Wildcard

Creating CodeSignGroups
checking certificate (446FE307C20B96B8) group:
profile (O2 Touch Notification App Store) does not provision bundle id: com.englandrugby.o2touch.EventNotification
profile (iOS Team Store Provisioning Profile: com.englandrugby.o2touch.EventNotification) does not provision bundle id: com.englandrugby.o2touch.EventNotification
profile (iOS Team Store Provisioning Profile: com.englandrugby.o2touch) MATCHES for bundle id (com.englandrugby.o2touch) and export method (app-store)
profile (O2 Touch Notification App Store) MATCHES for bundle id (com.englandrugby.o2touch.EventNotification) and export method (app-store)
matching profiles: 2 should be: 2

The correct certificate to be used here should be the 446FE307C20B96B8 group. As you can see at the top, this is included in the O2 Touch Notification App Store profile (com.englandrugby.o2touch.EventNotification), and the O2 Touch App Store profile (com.englandrugby.o2touch). However when the Creating CodeSignGroups part of the process happens it seems to only have the O2 Touch Notification App Store profile, and so it falls back to the Xcode generated provisioning profile, which then fails because of:
Export TeamID specified: 25H7BM6YWK, filtering CodeSignInfo groups...
Both xcode managed and NON xcode managed profiles in code singing group

And then:
error: exportArchive: Provisioning profile "iOS Team Store Provisioning Profile: com.englandrugby.o2touch" is Xcode managed, but signing settings require a manually managed profile.
Error Domain=IDEProfileQualificationErrorDomain Code=12 "Provisioning profile "iOS Team Store Provisioning Profile: com.englandrugby.o2touch" is Xcode managed, but signing settings require a manually managed profile." UserInfo={IDEProfileQualificationError_Profile=<DTDKProvisioningProfile 0x7fc374b0b700: UUID: 9fd2e6fd-ad39-4ebb-9407-0f5d23a965a8, name: iOS Team Store Provisioning Profile: com.englandrugby.o2touch, team: 25H7BM6YWK (3 SIDED CUBE DESIGN LTD), platform: iOS>, NSLocalizedDescription=Provisioning profile "iOS Team Store Provisioning Profile: com.englandrugby.o2touch" is Xcode managed, but signing settings require a manually managed profile.}
** EXPORT FAILED **

Hi @simonmitchell ,
Thanks for the bug report! :)
Just to be sure: did you try it with the previous version, or can you try it? Did that work?

@viktorbenei I think the issue here is simply the break when it matches the first provisioning profile which matches both bundle identifier and export type. I don't think this works if you have Xcode managed and NON Xcode managed profiles uploaded.
The problem then becomes the fact that for our build configuration the provisioning profile export tool simply doesn't work in generating the correct provisioning profiles with the latest versions of the steps. I can give it a go with previous versions, for now though I'm going to try removing the Xcode team provisioning profiles and see if that fixes the issue!

@viktorbenei okay it turns out I was correct. I removed all the App Store Team provisioning profiles and now it works! Not sure if there's any way to get the provisioning export script working now at generating the correct provisioning profiles now that Xcode 9 seems to require manually generated ones for upload to App Store!
It could also obviously be the case that we're doing everything wrong here... but this is essentially how we've been building all of our apps for the last year and a half or so!

Hi @simonmitchell ,
thanks for the report! Could you please contact us on bitrise.io on-site chat and send us your failed build log url?

I'll close this issue, but if you need more info/help just let us know and we'll reopen it!


Suggestion: change terms "Whitelist"/"Blacklist" for "Allowlist"/"Blocklist"

Please consider changing the terms "Whitelist"/"Blacklist" for "Allowlist"/"Blocklist".
https://9to5google.com/2020/06/12/google-android-chrome-blacklist-blocklist-more-inclusive/

And change your "master" branch while you're at it :D

Also the White house

And rename your "master" branch while you're at it :D

Where do I find the branch


claim_list argument --claim_type can now be repeated to pass a list of claim_types

@eukreign can this be added to other calls too? https://github.com/lbryio/lbry-desktop/pull/3712 is blocked because it isn't supported.

Nevermind. Wasn't on the latest release.


Disabling all unnecessary fields in custom modules (Custom css, Visibility)

We're building custom modules for our websites, but we are running into a few issues. Because our theme will mainly be used by frontend webdevelopers, we want them to design the blocks in css alone.
To make sure that this works, we've build our own modules with as little options as possible. Some options I cant remove however. As seen in the attached screenshot, I still have options for 'Custom CSS', 'Visibility' and 'Transitions'. All of which I want to remove.
How do I remove these options in a supported and VB compatible way?
As a second part of this question: How do i make sure that the visual builder doesnt have more options that the backend editor? In the backend, I no longer have an option for margin and padding. But in the frontend I can still drag the module for padding.
And finally, like seen in the screenshot, Can I remove the design tab, as it's no longer used?

I've tried working with the get_advanced_fields_config() and have managed to get rid of a lot of these options, but not all.
`<?php
class [REDACTED] extends ET_Builder_Module {
public $slug       = '[REDACTED]';
public $vb_support = 'on';

protected $module_credits = array(
	'module_uri' => '[REDACTED]',
	'author'     => '[REDACTED]',
	'author_uri' => '[REDACTED]',
);

public function init() {
	$this->name = esc_html__( '[REDACTED]', '[REDACTED]-builder' );
}

public function get_fields() {
	return array(
		'content' => array(
			'label'           => esc_html__( 'Content', '[REDACTED]-builder' ),
			'type'            => 'tiny_mce',
			'option_category' => 'basic_option',
			'description'     => esc_html__( 'Content entered here will appear inside the module.', '[REDACTED]-builder' ),
			'toggle_slug'     => 'main_content',
		),
	);
}

public function get_custom_css_fields_config() {
    return false;
}

public function get_advanced_fields_config() {
    return array(
        'background' => array(
            'use_background_color_gradient' => false,
            'use_background_video' => false,
            'settings' => array(
                'disable_toggle' => false,
            ),
            'css' => array(
                'important' => false,
            ),
        ),
        'borders'           => false,
        'box_shadow'        => false,
        'text_shadow'       => false,
        'transform'       	=> false,
        'animation'       	=> false,
        'button'            => false,
        'filters'           => false,
        'fonts'             => false,
        'text'             	=> false,
        'text_alignment'   	=> false,
        'margin_padding'    => false,
        'max_width'         => false,
    );
}

public function render( $attrs, $content = null, $render_slug ) {
	return sprintf( '%1$s', $this->props['content'] );
}

}
new GNM_Text;
`

have you found how to remove the design tab?
thanks

I found how to:
	function get_settings_modal_tabs() 	{ 		$settings_modal_tabs = array(); 		$settings_modal_tabs['advanced'] = false; 		$settings_modal_tabs['css'] = false; 		return $settings_modal_tabs; 	}

Thank you for the information! I never got more information from elegantthemes. The project I needed this for is currently on hold.


Correction for raw affiliation UMR 6226 CNRS -University of Rennes; University of Tlemcen T. Roisnel

Correction needed for raw affiliation UMR 6226 CNRS -University of Rennes; University of Tlemcen T. Roisnel
raw_affiliation_name: UMR 6226 CNRS -University of Rennes; University of Tlemcen T. Roisnel
new_rors: 043vm9914;015m7wh34;00adwkx90
previous_rors: 043vm9914;015m7wh34
works_examples: W4387665734
contact: 7f5b52f4d29b1358aa92ddb327ec23fa:a4adaa765f74912253ac41eb90dc0f91 @ univ-rennes.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-10. The new affiliations should be visible within the next 7 days.


fix: lock_if_exist + aggressive locking

Locking commands skipped by lock_only_if_exists were mistakenly calculated as successfully locked for aggressive locking.

@cfzjywxk @sticnarf PTAL
cc @MyonKeminta

/merge


Make lemma-specs valid on both Java/Haskell backends

@virgil-serbanuta I'm closing this because I want to review the changes here, but I was the one who opened the PR. Please re-open a PR against master with the new set of changes you need now that #721 is merged.


Is the labeling correct?

The results in your paper are excellent, and I would like to reproduce them.
However, I have a question about Narcissus.ipynb.
Poi_warm_up_loader variable is received train_target, but the label of this dataset is still the label in CIFAR-10 ("2" for target class in the code).
However, during training of surrogate model, the CIFAR-10 and TinyImageNet data concatenated, and the label of the instances of the CIFAR-10 target class was assigned to "200".
Therefore, isn't it unintentional to train with train_target since the labels are different?
I have the same question about trigger_gen_loaders.
Please let me know if my interpretation is wrong.
Thank you.

It is fine to use any label in the surrogate model, the surrogate aims to make the model a feature extractor, and as the target class is included in the training dataset, the model will be able to distinguish from class to class.


Is it possible to reduce the size of ue4-source's final layer?

It turns out, AWS's ECR has a layer-size limit of<PHONE_NUMBER>0, and the final layer of ue4-source for 4.21.2 is 24.59GB.
I believe that's just
# Run post-clone setup steps
WORKDIR C:\UnrealEngine
RUN Setup.bat

Oddly enough, the final layer in ue4-build-prerequisites for ltsc2019 is 14.24GB, but I suspect that the 10GiB limit in AWS is for compressed data, and that 14GB layer compressed well. The 14GB reported by docker push might include empty space left after cleaning up, per the comment on the last two steps. I'm not totally sure how Docker works here...
# Install the rest of our build prerequisites and clean up afterwards to minimise image size
COPY buildtools-exitcode.py copy.py copy-pdbcopy.py install-prerequisites.bat C:\
RUN C:\install-prerequisites.bat

This is a low-value feature request, as long as no other layers grow. I don't need to push the ue4-source image at this time (I'm setting up for CI) so it was more about repeatability.
It might be worth mentioning in the documentation, but given other limitations on ECR (that 14GB layer in ue4-build-prerequisites is present in the other images, but the layer data is not shared across repositories, so I'm paying for that storage four times. >_<)

Unfortunately there isn't really anything I can do about the size of the Unreal Engine source code itself, or the size of the dependency files that are downloaded by Setup.bat. Due to its immense size, the documentation actually recommends removing the ue4-source image at the end of the build process to free up disk space. The unspoken expectation is that anyone running ue4-docker within a CI context will start from a fresh slate each time, either building or pulling the prebuilt version of the ue4-build-prerequisites image and building all subsequent images from source.
It's worth noting that Docker Hub's paid plans charge on a per-repository basis rather than a filesize basis, which is far better suited to massive container images like those produced by ue4-docker. I also know for a fact that Docker Hub shares layer data between repositories, and although I'm not sure about size limits on individual layers, I do know that there are no overall size limits for container images. I realise that storing images on Docker Hub isn't ideal from a performance perspective if you need to be pulling them from within an AWS availability zone, but from a purely storage standpoint it's definitely the most cost-effective option.

The Docker Hub suggestion is good, although I guess that means I'm paying traffic costs instead. I also haven't looked at what other cloud providers use (I just happened to have AWS at-hand), so at this experimentation/discovery stage, storage cost is not a driver.
Hopefully the person who does need to track costs isn't reading my Github activity log...
The main reasons I'm keen to push and keep things are:

I understood ue4-source was likely to change underneath me for auth-token reasons, and would invalidate caches on recreation.
The whole build-pipe took 18 hours, and I'd really like to avoid having to redo that. ^_^ This one might be on my selection of AWS instance, I probably made a poor choice (t3.xlarge to get 16GB of RAM, since the 8GB version kept Bugchecking during the build)

Depending on how we go, we may be pushing the ue4-source package from elsewhere, particularly if-and-when we have projects that're using project-specific UE4 branches, or even for builds from Unreal's own Perforce, e.g., for console targets. That's however for later stages, once I've proved this part workable for in-house development and playtest iteration.
I'll close this ticket off for now, as it's pretty-much what I expected. If it proves problematic, I might look at the python scripts that already hack Setup.bat, and see if I can do anything to auto-split it into multiple layers or something.

Just a quick follow-up for posterity in case anyone else reads this thread later:

Yes, the randomly-generated security token used by the credential endpoint will indeed result in unique layer hashes for each build of the ue4-source image, invalidating Docker's build cache. Unfortunately I've yet to find a satisfactory workaround for this, which is why I've done my best to isolate the effects to that one image.

18 hours is a startlingly long time for a full build of the container images produced by ue4-docker. I can see from the AWS documentation that a t3.xlarge instance has 4 vCPUs to accompany that 16GiB of RAM. I know from experience that a full build of the Windows versions of the images (which take longer to build than the Linux versions) on a physical machine with similar specs takes less than 10 hours (that's for the entire set of images, i.e. build prereqs, -source, -engine, -minimal, and -full.) The only relevant factors not stated are disk and network specs, but network can probably be ruled out since an AWS datacentre is pretty much guaranteed to have a better network connection than my residential 100Mbps NBN. Assuming an SSD was used for the instance's root volume and the instance wasn't a spot instance that got interrupted during the build, I'm at somewhat of a loss as to why the build would've taken so long.

My suspicion is that "t3" doesn't get all 4 vCPUs all the time due to the bursting behaviour. Next time I do this, I'll do it on an m5.large or m4.large, to rule that out. Most of that 18 hours was spent building ue4-minimal, as I recall, as I'd already gotten prereqs built, and ue4-source logged 44 minutes to complete.


⚠ Anthelion has degraded performance

In e3c1083, Anthelion ($ATH) experienced degraded performance:

HTTP code: 200
Response time: 2372 ms

Resolved: Anthelion performance has improved in 2003062 after 411 days, 2 hours, 42 minutes.


Release notes for hotfix 2308-2

Add release notes for hotfix of 2308-2, to include new CA certificates

@microsoft-github-policy-service agree company="Microsoft"


[Fix] Error raised when using "linear" policy

This fixes the "list out of bounds" exception raised when searching with "linear" policy. The error was raised due to a mismatch between the number of batches and the length of lr_multiplier_.
Note that this fix does not affect anything else.
For a detailed discussion, please refer to #6

Thank you for the fix !


CircularProgressIndicator draws outside the parent constraints

Steps to Reproduce

Execute flutter run on the code sample
Draw a CircularProgressIndicator inside a rect

Actual results:

Expected results:
Outerbound of the Circle to be inside the rect

Code sample
https://dartpad.dev/ff216dcfc7e84112b7e3267a2807d298

class MyWidget extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Container(
      height: 100,
      width: 100,
      color: Colors.yellow,
      child: CircularProgressIndicator(
        color: Colors.red,
        value: 1,
      ),
    );
  }
}

This also creates further complications when trying to draw customshaders since the rect doesnt completely cover the progressIndicator

Hi @Hari-07, Thanks for filing the issue. I am able to reproduce the issue on all platforms (Android/IOS/Web/Desktop), The circular indicator is painted slightly outside the container from all sides.

Android
IOS

This is reproducible on stable and the master channel.

code sample
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Navigation Basics',
      home: FirstRoute(),
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
    );
  }
}

class FirstRoute extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
        appBar: AppBar(
          toolbarHeight: 30,
          title: Text('First Route'),
          elevation: 0,
        ),
        body: MyWidget());
  }
}

class MyWidget extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Center(
      child: Container(
        height: 100,
        width: 100,
        color: Colors.yellow,
        child: const CircularProgressIndicator(
          color: Colors.red,
          value: 1,
        ),
      ),
    );
  }
}

flutter doctor -v
[✓] Flutter (Channel stable, 2.10.1, on macOS 12.1 21C52 darwin-arm, locale en-GB)
    • Flutter version 2.10.1 at /Users/mahesh/Documents/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision db747aa133 (8 days ago), 2022-02-09 13:57:35 -0600
    • Engine revision ab46186b24
    • Dart version 2.16.1
    • DevTools version 2.9.2

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.10.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 61.2.4
    • Dart plugin version 212.5080.8

[✓] VS Code (version 1.63.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.34.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 12.1 21C52 darwin-arm
    • Chrome (web)    • chrome • web-javascript • Google Chrome 98.0.4758.102

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

[✓] Flutter (Channel master, 2.11.0-0.0.pre.582, on macOS 12.1 21C52 darwin-arm, locale en-GB)
    • Flutter version 2.11.0-0.0.pre.582 at /Users/mahesh/Documents/flutter_master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision<PHONE_NUMBER> (28 hours ago), 2022-02-16 00:00:11 -0500
    • Engine revision b09cf53269
    • Dart version 2.17.0 (build 2.17.0-105.0.dev)
    • DevTools version 2.10.0

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.10.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 61.2.4
    • Dart plugin version 212.5080.8

[✓] VS Code (version 1.63.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.34.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 12.1 21C52 darwin-arm
    • Chrome (web)    • chrome • web-javascript • Google Chrome 98.0.4758.102

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

duplicate of https://github.com/flutter/flutter/issues/3282


Undefined binding(s) detected on setup

Issue Summary
Unable to finish setup, after entering details, the following message is returned ...
All subsequent logins fail. Occurs after installing from source and using ghost-cli.
Clicking "Last Step: Invite your team" results in the following error message ...
"Undefined binding(s) detected when compiling SELECT query: select clients.* from clients where clients.slug = ? limit ?"
Steps to Reproduce

Setup run as normal, out of the box.

Any other info e.g. Why do you consider this to be a bug? What did you expect to happen instead?
Technical details:

Ghost Version: v1.17.0
Node Version: v6.12.0
Browser/OS: Windows 10 & Google Chrome
Database: MySQL 5.6

@sptdigital closing this as a duplicate of #8613. There is a fix for the server-side error going out in the next Ghost release. If you still see a problem after upgrading please reply and we can look into it further.

I am now seeing a different error. When it would normally take you to the 2nd part of the setup, it displays "Access Denied" before redirecting you to the login page. If you login it will start to load up "Your Stories" before redirecting back to the login page again.

@kevinansfield any idea?

Is there any session or cookie variables I could dump out to help with debugging?

I tried updating to 1.17.3 and I can now login successfully. I will test all other functionality today. Thank you for your help.


Weird changes in  schema after migration to 0.9.1

After migrating to new version 0.9.1, default values has changed in database
Current Behavior 😯
this is field definitions:
field.Time("created_at").
			Immutable().
			Default(time.Now),
field.Time("updated_at").
			Default(time.Now).
			UpdateDefault(time.Now),

This is how fields look now in database:
`created_at` timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp(),
  `updated_at` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',

Expected Behavior 🤔

First of all we aren't expected to any schema changes when just migration to new version, or at least should be some release notes
Second, this change look like a bug

Steps to Reproduce 🕹
Migrate to new version from 0.8 to 0.9.1
Your Environment 🌎

Tech
Version

Go
1.16.4

Ent
0.9.1

Database
mariadb

Driver
https://github.com/go-sql-driver/mysql

Hi @michaelkub and thanks for reporting this issue.
The fields above should not configure any DEFAULT on the database, and we didn't add any specific code for it in v0.9.*
What is your MariaDB version? I'll try to reproduce it now.

#1946 should address this issue (see attached screenshot). Would you mind ping me on Slack/Discord and discuss how we can avoid issues like this with MariaDB in the future?

expected
created_at TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP
updated_at TIMESTAMP on update CURRENT_TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP


Update build to version and package based on tag

@ctaggart any chance you can enlighten me on the Travis build failure?


updated files to deploy stellio under kubernetes

Proposed changes
new yaml files to deploy stellio under kubernetes,
Types of changes

Postgresql/Timescale is deployed as a StatefulSet, better than deployment for a database
added a way to deploy a json-ld context server, with @context files you need, through ConfigMap

Further comments
not tested on minikube,
but on several different kubernetes versions (1.20 to 1.24), with Rancher RKE, RKE2, or OVH managed clusters, so it shall be OK with minikube too !

it's never too late...


fix: divider colors

Description
When the category token was changed for popover border, the divider color was also changed from default-border to default border muted. However, this dependency didn't show up in my editor as a "usage" because the token is used inside a string. Since this change was unintentional and won't work for our platform, this PR creates two tokens for content-border, one for surface (which divider and menu divider uses), and one for container (which menu, select, popover, and date picker uses).
Depends on # (pr)
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Manual on storybook
Manual on main repo
Jest
Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

/generate-alpha

As mentioned in the description above, tested this PR for:

Divider:

Menu divider:

Menu (container):

Select (container):

Popover (container):

Date/Date range picker (container):

Looks good


fixes issues with links loosing anchors

Related to this issue
https://github.com/basemate/matestack-ui-core/issues/4

Hey @cameronnorman this looks good, but I couldn't get it working. Could you

add documentation
add tests
change the PR target to develop?

On closer inspection it seems like link tags are currently possible.
link(path: "/new#abc", text: "hello world")

One thing I did notice here https://github.com/basemate/matestack-ui-core/blob/master/app/concepts/matestack/ui/core/link/link.rb is that the link tag is not accepting a name attribute.
I can change this PR to include that silly change and remove my changes unless there is something I am missing
Note to future self. Do not code so late at night.

@cameronnorman
first of all:

thank you!
I think link component is broken since 0.7.0. I fixed it locally and will add the missing specs which would have pointed that out.

but anyway if the link component itself is working as currently designed, following is relevant:

linking to a path with an anchor is possible, as you said

link path: "some_link#someanchor", text: "link to page (full page reload) and display specific position"

the issue you referenced (#4) describes a different problem:

link path: "#someanchor", text: "go to anchor"

br times: 200

div id: "#someanchor" do
  plain "hello!"
end

Current:
If you click on the link "go to anchor", the page is reloaded and the anchor disappears from the url.
Desired:
If you click on the link "go to anchor", the page is not reloaded and only the scroll position is updated accordingly (default browser behaviour). The anchor link is visible in the url and works after full page reload (or link sharing etc)
--> I would recommend to discuss #4 within the comments of #4. I'm gonna add the details there.

adding the "name" attribute to the link might actually fix #4 but seems to be outdated: https://www.w3schools.com/tags/att_a_name.asp --> "The  name attribute is not supported in HTML5. Use the id attribute instead."

--> I would recommend not to support the name attribute and fix #4 instead
--> @cameronnorman If you agree, I would close this PR

I agree. You may close this PR


Unable to run server on localhost ...

This is my simple server :
import { Server } from 'boardgame.io/server';
import { Bridge } from './lib/bridge.js';
import cors from '@koa/cors';

const server = Server({
  games: [Bridge],
});

server.app.use(cors({ origin: '*' }));
server.run(3010);

when i try to connect to it it throws :
(node:47605) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'ctx' of undefined
    at CreateGameReducer (/Users/grzegorz/play-engine/gameServer/node_modules/boardgame.io/dist/server.js:1477:23)
    at Master.onSync (/Users/grzegorz/play-engine/gameServer/node_modules/boardgame.io/dist/server.js:2388:21)
    at Socket.<anonymous> (/Users/grzegorz/play-engine/gameServer/node_modules/boardgame.io/dist/server.js:2553:28)
    at Socket.emit (events.js:182:13)
    at /Users/grzegorz/play-engine/gameServer/node_modules/socket.io/lib/socket.js:528:12
    at process.internalTickCallback (internal/process/next_tick.js:70:11)

Same client running with multiplayer : Local works as should, what could be the source of problem?

My bad, different version of package on client and server


useSWRInfinite always make 2 calls for api (page 1 and page n)

Bug report
Description / Observed Behavior
What kind of issues did you encounter with SWR?
Always 2 requests sends to API:

with page number 1
with page number N

Expected Behavior
1 request should be created with page N
How did you expect SWR to behave here?
Repro Steps / Code Example
Install https://github.com/vercel/swr/tree/main/examples/infinite-scroll
Take a look in Network tab

Or share your code snippet or a CodeSandbox link is also appreciated!
Additional Context
SWR version.
Add any other context about the problem here.
It works as expected for very old version :) Example - https://swr.vercel.app/examples/infinite-loading

Duplicate of #1638, as I explained there:

Since SWR 1.1.0, there is a new option revalidateFirstPage that you can use to turn this off. Related docs: https://github.com/vercel/swr/releases/tag/1.1.0
If you are interested, here are the full discussions of why we built this feature in the first place: https://github.com/vercel/swr/issues/1401#issuecomment-907764278, and why we now provide this new option to customize it.
Let me know if it helps you!

@shuding thank you, got it


Standardize cross-links on component pages

Rethinking these cross-links at the bottom of each component page, are they valuable enough given our VOC conversation on 4/21? Do we need to standardize one or both of them? For example, could the right cross-link have a link to a contact page or future survey?

The link to github is convenient for us, but maybe not to all users. I'm going to look into some other options.

We talked about adding User Snap this AM. If we can do that and if people use it we'll have a good solution to this. I feel like the github link is useful as well.

I am working to standardize cross-links as I update each page.


What's up with Data_app?

I'm confused about Data_app:

We have a mk_data function that introduces Data_app annotations, but it's dead code.  Should it be used?

let mk_data l args =
  match args with
    | [] ->
      mk (Tm_meta(fvar l Delta_constant (Some Data_ctor), Meta_desugared Data_app)) None (range_of_lid l)
    | _ ->
      let e = mk_app (fvar l Delta_constant (Some Data_ctor)) args in
      mk (Tm_meta(e, Meta_desugared Data_app)) None e.pos

We don't seem to use Data_app anywhere except for resugaring, but there it'd be enough to just check for a capitalized name, right?

Can we just get rid of that annotation entirely? And is it bad that mk_data isn't used anywhere?

What's preventing the merge of your fix to this? I sometimes run into this and it's always annoying, so it'd be great to merge it.

Life is :) I was hoping to merge this last Friday, but with the CI down I couldn't. Now I'm back at work, so things are slower.

Cool, no rush! I was just wondering if anything was missing.

Ah, there is one thing preventing the merge. A circular dependency in F#.
tosyntax.vsproj depends on syntax,vsproj, and I need a dependency in the other direction.

Should I just move ToSyntax.Env into Syntax? Or move Syntax.Print to ToSyntax?

Can you say more about that circularity? I just merged 8edeba6 and it seems to have compiled OK (but I see a lot of Binder uu___ is not used).

I'm working on cpitclaudel_1293; I think you only merged part of that branch.

Indeed. Taking a look now ..

Moving ToSyntax.Env into syntax/ looks like the sanest solution.

I merged your cpitclaudel_1293 branch into a current F* and moved the desugaring environment into syntax/ to avoid the circular dep. The result is in guido_1303, and CI just gave a green for it.
If you have a couple of minutes could you check that it works as intended? The merge was non-trivial and I could have messed up. I do see prettier output but I haven't tried all of the bullets in #1293.
I stacked this over some tactics stuff which will get to master in a few days. I'll probably merge this with it unless you find I made some mistake or some bug appears.
Thanks a lot for working on this, the better resugaring and robustness is great.

Just had a quick look; it looks pretty good! I'll admit I didn't read the whole thing though :)
I left one quick question in https://github.com/FStarLang/FStar/commit/29b070c4fcec6165486f12fa1c79229899246823


libcudart.so.7.5: cannot open shared object file: No such file or directory

Hello,
I try to install tensorflow-gpu on my ubuntu machine.
i got this error here:
ImportError: libcudart.so.7.5: cannot open shared object file: No such file or directory
some one can help me ?
inside my ~/.bashrc
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/local/cuda/lib64:/usr/local/cuda/extras/CUPTI/lib64"
export CUDA_HOME=/usr/local/cuda
Installed:
Cuda 10.0
cuDNN 7.5.0

@007fred50  It looks like you haven't used a template to create this issue(tensorflow gpu  version used). Please resubmit your issue using a template from here. We ask users to use the template because it reduces overall time to resolve a new issue by avoiding extra communication to get to the root of the issue. We will close this issue in lieu of the new one you will create from the template. Thank you for your cooperation.

@007fred50 Request you to please follow the link1, link2.
Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


RuntimeError: derivative for aten::grid_sampler_2d_backward is not implemented

Hi Woctezuma,
thanks for your repo,
In the cell below, after running it with your custom datasets I get the error posted in the title of my Issue.
Also, do you really need to give it a resume file when you want to train a model for the first time?
!python stylegan2-ada-pytorch/train.py \
 --outdir={output_folder} \
 --snap={snap} \
 --metrics=none \
 --data={custom_dataset} \
 --cfg=auto_norp \
 --cifar_tune=1 \
 --gamma={gamma} \
 --kimg={kimg} \
 --batch={mini_batch} \
 --cfg_map=8 \
 --augpipe=bg \
 --freezed=10 \
 --resume=ffhq256

Thanks for your help,
L.

Hello!

[!Warning]
First of all, know that training a model on Google Colab is painful, it is much more convenient to use paid platforms if you don't want to deal with sessions closing inadvertently, frequently resuming training, machines which are not powerful, etc.

[!Important]
Second, I did not have time to post the results which I had obtained. From what I can remember, they looked like the ones obtained in my other repository at woctezuma/steam-stylegan2. The illustration used in the current repository is a projection using a model pre-trained by Nvidia, without any banner of games.

In the cell below, after running it with your custom datasets I get the error posted in the title of my Issue.

I will have a look.

Also, do you really need to give it a resume file when you want to train a model for the first time?

This is done to perform transfer learning from FFHQ trained at 256x256. See the documentation by Nvidia at:

https://github.com/NVlabs/stylegan2-ada-pytorch/blob/d72cc7d041b42ec8e806021a205ed9349f87c6a4/docs/train-help.txt#L33

Transfer learning is not mandatory, but it may help reach a satisfying result without using too much computation time.
This is mostly  relevant if the original dataset (here, FFHQ, which contains faces) is similar to your own dataset (maybe, banners of Steam games which feature a prominent face). For the GIF illustration shown on the README, you can see projections obtained "with a network pre-trained by Nvidia on the LSUN DOG dataset", hence why I chose banners of games which featured a dog.

Alright, I see the same error message as you saw.
Traceback (most recent call last):
  File "/content/stylegan2-ada-pytorch/train.py", line 556, in <module>
    main() # pylint: disable=no-value-for-parameter
  File "/usr/local/lib/python3.10/dist-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.10/dist-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.10/dist-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
  File "/usr/local/lib/python3.10/dist-packages/click/decorators.py", line 33, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/content/stylegan2-ada-pytorch/train.py", line 549, in main
    subprocess_fn(rank=0, args=args, temp_dir=temp_dir)
  File "/content/stylegan2-ada-pytorch/train.py", line 399, in subprocess_fn
    training_loop.training_loop(rank=rank, **args)
  File "/content/stylegan2-ada-pytorch/training/training_loop.py", line 299, in training_loop
    loss.accumulate_gradients(phase=phase.name, real_img=real_img, real_c=real_c, gen_z=gen_z, gen_c=gen_c, sync=sync, gain=gain)
  File "/content/stylegan2-ada-pytorch/training/loss.py", line 131, in accumulate_gradients
    (real_logits * 0 + loss_Dreal + loss_Dr1).mean().mul(gain).backward()
  File "/usr/local/lib/python3.10/dist-packages/torch/_tensor.py", line 492, in backward
    torch.autograd.backward(
  File "/usr/local/lib/python3.10/dist-packages/torch/autograd/__init__.py", line 251, in backward
    Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass
RuntimeError: derivative for aten::grid_sampler_2d_backward is not implemented

As well as a few warnings:
Creating output directory...
Launching processes...
Loading training set...

/usr/local/lib/python3.10/dist-packages/torch/utils/data/sampler.py:64: UserWarning: `data_source` argument is not used and will be removed in 2.2.0.You may still have custom implementation that utilizes it.
  warnings.warn("`data_source` argument is not used and will be removed in 2.2.0."

/usr/local/lib/python3.10/dist-packages/torch/utils/data/dataloader.py:557: UserWarning: This DataLoader will create 3 worker processes in total. Our suggested max number of worker in current system is 2, which is smaller than what this DataLoader is going to create. Please be aware that excessive worker creation might get DataLoader running slow or even freeze, lower the worker number to avoid potential slowness/freeze if necessary.
  warnings.warn(_create_warning_msg(

Num images:  2472
Image shape: [3, 256, 256]
Label shape: [0]

And many times:
/content/stylegan2-ada-pytorch/torch_utils/ops/conv2d_gradfix.py:55: UserWarning: conv2d_gradfix not supported on PyTorch 2.1.0+cu121. Falling back to torch.nn.functional.conv2d().
  warnings.warn(f'conv2d_gradfix not supported on PyTorch {torch.__version__}. Falling back to torch.nn.functional.conv2d().')

And a few times:
/content/stylegan2-ada-pytorch/torch_utils/ops/grid_sample_gradfix.py:39: UserWarning: grid_sample_gradfix not supported on PyTorch 2.1.0+cu121. Falling back to torch.nn.functional.grid_sample().
  warnings.warn(f'grid_sample_gradfix not supported on PyTorch {torch.__version__}. Falling back to torch.nn.functional.grid_sample().')

Hi Woctezuma,
Thanks a lot for your response. I saw Jeff Heaton training his GANs on Colab Pro. Do you mean this with a paid platform? If not wich would you recommend?
Thanks !
Leandre Sassi

I found the solution here https://github.com/dvschultz/stylegan2-ada-pytorch/issues/45#issuecomment-1671468176
Thanks again. Maybe this could be helpfull to update your colab!
Have a good day,
Leandre Sassi

Hello!

I saw Jeff Heaton training his GANs on Colab Pro. Do you mean this with a paid platform? If not wich would you recommend?

I have only had some experience with OVH AI Training, as I had a chance to try their platform for free when they were beta-testing their service near the official launch.
I don't have any experience with other platforms, so it is not sufficient knowledge to recommend one over another. 😅

I found the solution here dvschultz/stylegan2-ada-pytorch#45 (comment)
Thanks again. Maybe this could be helpfull to update your colab!

Thank you! I will have a look!
Have a nice day!

For info, the following commit:

https://github.com/NVlabs/stylegan3/commit/407db86e6fe432540a22515310188288687858fa

fixes this warning which appeared many times:
/content/stylegan2-ada-pytorch/torch_utils/ops/conv2d_gradfix.py:55: UserWarning: conv2d_gradfix not supported on PyTorch 2.1.0+cu121. Falling back to torch.nn.functional.conv2d().
  warnings.warn(f'conv2d_gradfix not supported on PyTorch {torch.__version__}. Falling back to torch.nn.functional.conv2d().')

Alright, I believe the notebook works now. I am not sure if one has to downgrade the PyTorch version.

No need to Downgrade Python or PyTorch ;) Just trained a model and it went all good.