Indexing Morphisms

Heyya!
It'd be really neat to set Cayley up to index on a Morphism, so that expensive queries can be done while loading, rather than taking that hit every time a query is done.
I know this is a massive feature request and quite nebulous, but I figure I'll put it on the issue tracker.

We can continue this discussion on the feature request forum: https://discourse.cayley.io/t/indexing-morphisms/232


Create an analyzer for Endpoint Routing + UseMVC

In 3.0 we won't support this combo anymore, since we expect this to impact lots of folks updating to 3.0 this definitely deserves an analyzers so users can know.
The conditions I would expect to check for is:

Is MvcOptions.EndableEndpointRouting == false not found?
Is UseMvc() present

https://github.com/aspnet/AspNetCore/tree/rynowak/startup-analyzer

Questions:

Does CompatibilityVersion.Version_2_1 still disable endpoint routing? From what I can tell it does not.
How funky do we want to get with detecting the correct Startup.cs? For example, someone may have renamed it. Would require parsing Program.Main (which, if we want to be really thorough would require us to look in the csproj file to see if the entry point had changed).
I'll remove the other analysis logic that is in your branch. Can look at in the future. Cool?

We don't need to handle that. These analyzers are 3.0+ and 3.0 doesn't support that setting.

Not funky at all. We should do something really simple.

Yes please, we should do something reasonable to try and make the migration experience have better feedback.

Help file article - https://github.com/aspnet/AspNetCore/issues/8898


BUG: timeout when connecting to kernel on slow machine

Applies To

[X] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
My newish computer broke last week, using that worked fine. But, until my new machine arrives, I'm borrowing my dad's computer with a wimpy little i3. I believe this slowness is causing a timeout error. I'm not sure if you will be able to repro this without a slow computer, but here are my repro steps:

Reboot the machine

make a new .ipynb

run the first cell.

I get the message Failed to connect raw kernel session: Error: Unable to start Kernel '.venv (Python 3.11.6)' due to a timeout waiting for the ports to get used.  View Jupyter [log](command:jupyter.viewOutput) for further details.  Full log output below.

Repeat step 3 as many times as I like and I get outcome 4 every time.

OK, so I read the logs, and in a new terminal I try python -m ipykernel_launcher. This takes like 10 seconds, but it succeeds. Now, if ctrl-c that process and go back to the notebook, now the kernel starts up fine! Perhaps there is some caching or something that happens, so on subsequent runs that command is fast enough to avoid the timeout. If I restart vscode, the notebook kernel continues to work. So it seems like it requires a machine reboot for the cache to get cleared.

I'm not sure how you can repro this. Perhaps go into the ipykernel_launcher script and monkeypatch in a time.sleep(10) to emulate a slow computer?
VS Code Version
Version: 1.83.1 (Universal) Commit: f1b07bd25dfad64b0167beb15359ae573aecd2cc Date: 2023-10-10T23:46:55.789Z Electron: 25.8.4 ElectronBuildId: 24154031 Chromium: 114.0.5735.289 Node.js: 18.15.0 V8: <IP_ADDRESS>-electron.0 OS: Darwin x64 23.0.0
Jupyter Extension Version
v2023.9.1102792234
Jupyter logs
09:18:23.233 [error] waitUntilUsed timed out Error: timeout
    at Timeout.<anonymous> (~/.vscode/extensions/ms-toolsai.jupyter-2023.9.1102792234-darwin-x64/out/151.node.js:1:17194)
    at listOnTimeout (node:internal/timers:569:17)
    at processTimers (node:internal/timers:512:7)
09:18:23.234 [error] Disposing kernel process due to an error Error: Unable to start Kernel '.venv (Python 3.11.6)' due to a timeout waiting for the ports to get used.
View Jupyter [log](command:jupyter.viewOutput) for further details.
    > Kernel Id = .jvsc74a57bd0b727918fd311c44844600ae430f1976f0f8dc47d07c96db9dab81b44f2e17c1c.~/code/mismo/.venv/python.~/code/mismo/.venv/python.-m#ipykernel_launcher
    > Interpreter Id = ~/code/mismo/.venv/bin/python
    > at ~/.vscode/extensions/ms-toolsai.jupyter-2023.9.1102792234-darwin-x64/out/extension.node.js:24:87612
09:18:23.234 [error]
09:18:23.234 [info] Dispose Kernel process 2233.
09:18:23.260 [error] Kernel Launcher. launch, Class name = ty, completed in 6063ms, has a falsy return value, Arg 1: "~/code/mismo/.venv/python.~/code/mismo/.venv/python.-m#ipykernel_launcher", Arg 2: 6000, Arg 3: "~/code/mismo/docs/examples/patent_deduplication.ipynb", Arg 4: "~/code/mismo/docs/examples", Arg 5: "" Error: Unable to start Kernel '.venv (Python 3.11.6)' due to a timeout waiting for the ports to get used.
View Jupyter [log](command:jupyter.viewOutput) for further details.
    > Kernel Id = .jvsc74a57bd0b727918fd311c44844600ae430f1976f0f8dc47d07c96db9dab81b44f2e17c1c.~/code/mismo/.venv/python.~/code/mismo/.venv/python.-m#ipykernel_launcher
    > Interpreter Id = ~/code/mismo/.venv/bin/python
    > at ~/.vscode/extensions/ms-toolsai.jupyter-2023.9.1102792234-darwin-x64/out/extension.node.js:24:87612
09:18:23.261 [error] Failed to connect raw kernel session: Error: Unable to start Kernel '.venv (Python 3.11.6)' due to a timeout waiting for the ports to get used.
View Jupyter [log](command:jupyter.viewOutput) for further details.
09:18:23.261 [error] Failed to connect raw kernel session: Error: Unable to start Kernel '.venv (Python 3.11.6)' due to a timeout waiting for the ports to get used.
View Jupyter [log](command:jupyter.viewOutput) for further details.
09:18:23.261 [warn] Error occurred while trying to start the kernel, options.disableUI=false Error: Unable to start Kernel '.venv (Python 3.11.6)' due to a timeout waiting for the ports to get used.
View Jupyter [log](command:jupyter.viewOutput) for further details.
    > Kernel Id = .jvsc74a57bd0b727918fd311c44844600ae430f1976f0f8dc47d07c96db9dab81b44f2e17c1c.~/code/mismo/.venv/python.~/code/mismo/.venv/python.-m#ipykernel_launcher
    > Interpreter Id = ~/code/mismo/.venv/bin/python
    > at ~/.vscode/extensions/ms-toolsai.jupyter-2023.9.1102792234-darwin-x64/out/extension.node.js:24:87612
09:18:23.261 [warn] Kernel Error, context = start Error: Unable to start Kernel '.venv (Python 3.11.6)' due to a timeout waiting for the ports to get used.
View Jupyter [log](command:jupyter.viewOutput) for further details.
    > Kernel Id = .jvsc74a57bd0b727918fd311c44844600ae430f1976f0f8dc47d07c96db9dab81b44f2e17c1c.~/code/mismo/.venv/python.~/code/mismo/.venv/python.-m#ipykernel_launcher
    > Interpreter Id = ~/code/mismo/.venv/bin/python
    > at ~/.vscode/extensions/ms-toolsai.jupyter-2023.9.1102792234-darwin-x64/out/extension.node.js:24:87612
09:18:23.265 [info] Process Execution: ~/code/mismo/.venv/bin/python -c "import ipykernel;print('6af208d0-cb9c-427f-b937-ff563e17efdf')"
09:18:23.491 [info] Dispose Kernel '~/code/mismo/docs/examples/patent_deduplication.ipynb' associated with '~/code/mismo/docs/examples/patent_deduplication.ipynb'
09:18:23.502 [error] Error in execution Error: Unable to start Kernel '.venv (Python 3.11.6)' due to a timeout waiting for the ports to get used.
View Jupyter [log](command:jupyter.viewOutput) for further details.
    > Kernel Id = .jvsc74a57bd0b727918fd311c44844600ae430f1976f0f8dc47d07c96db9dab81b44f2e17c1c.~/code/mismo/.venv/python.~/code/mismo/.venv/python.-m#ipykernel_launcher
    > Interpreter Id = ~/code/mismo/.venv/bin/python
    > at ~/.vscode/extensions/ms-toolsai.jupyter-2023.9.1102792234-darwin-x64/out/extension.node.js:24:87612
09:18:23.502 [error] Error in execution (get message for cell) Error: Unable to start Kernel '.venv (Python 3.11.6)' due to a timeout waiting for the ports to get used.
View Jupyter [log](command:jupyter.viewOutput) for further details.
    > Kernel Id = .jvsc74a57bd0b727918fd311c44844600ae430f1976f0f8dc47d07c96db9dab81b44f2e17c1c.~/code/mismo/.venv/python.~/code/mismo/.venv/python.-m#ipykernel_launcher
    > Interpreter Id = ~/code/mismo/.venv/bin/python
    > at ~/.vscode/extensions/ms-toolsai.jupyter-2023.9.1102792234-darwin-x64/out/extension.node.js:24:87612
09:18:23.542 [info] End cell 0 execution @ undefined, started @ undefined, elapsed time = 0s

Coding Language and Runtime Version
python 3.11.6
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
NA
Running Jupyter locally or remotely?
Local

Thanks for filing this issue and sorry you are running into this
I have seen other users run into similar issues, and its caused by some other software blocking these ports,
Do you have some suck software on your mac?
Optionally, please can you launch Jupyter Lab/Notebook in your terminal, and let me know if that works.
python -m jupyter notebook
Once done, open a notebook in the notebook UI and try running a cell.

This takes like 10 seconds, but it succeeds. Now, if ctrl-c that process and go back to the notebook, now the kernel starts up fine! Perhaps there is some caching or something that happens, so on subsequent runs that command is fast enough to avoid the timeout

Looks like an issue with the Python package itself, hence the reques+ to try and start Jupyter Notebook outside vscode in the terminal

Thanks for the help!

The OS-installed stuff like photoanalysisd that I don't realy have control over, but it only takes 25% of a CPU at max (out of 4 cores). This might just run at startup of my machine, I could wait 30 minutes after boot and maybe that daemon will calmn down by then and I could retry if you think that's useful?

python -m jupyter notebook

That works, it takes like 10 seconds. Then I can open the given URL in chrome and it works. If I paste that as an "existing server" in the vscode jupyter UI, then when I run the first cell, it takes like 15 seconds to actually connect, but it does successfully.
Let me know what else I can do.

@NickCrews
I think i may have a solution for this.
Please can you try the solution posted here https://github.com/microsoft/vscode-jupyter/issues/14519#issuecomment-1778289425
Basically its a custom VSIX (custom build of the Jupyter extension with a potential fix)
Let me know how that goes
Lets continue the discussion in that issue https://github.com/microsoft/vscode-jupyter/issues/14519#issuecomment-1778289425


adding regex matching capability

@kcwinner how about now, didn't notice the issue was unresolved

LGTM! Merge it in


[ENG-1486] Updated WalletConnect & Web3 providers to support optional metadata param & different sign methods

the changes seems fine, but we need tests please.

We need to configure tests for these packages first, I will create a separate ticket for that.


[SERVICES-PTRUN] Update the details and Action Buttons if "Clear the previous search Queries-->Unchecked"

Description of the new feature / enhancement
Lets take scenario if the service was running & Clear the previous search Queries-->Unchecked

Run PTRUN
Search the service.
the details of service would be running, and an action button would be to stop.
Press enter to stop the service.
now bring the PTRUN again.
The details and button would still show -- running & Stop Button. Which it should not as i changed the service to Stop in last ptrun.

The query should update the details and Action Buttons.
The screenshot shows that in Services the service is running but in PTrun shows it is stopped and shows a button to start. (Also the action is performed correctly even if the details and button are displayed wrong)
This is a UI bug , the functionality works.

Scenario when this would be used?
The information & action would be displayed correctly.
Also Maybe this can be extended into other parts of PTRUN too , if its same there , as i just observed it in Services section. Devs will know better.
Supporting information
No response

/dup #15964


Non-null host-address bits

Hey,
recently I started to get these errors:
Sep 25 18:51:04 ksol postfix/postscreen[83636]: warning: cidr map /usr/local/etc/postfix/postscreen_spf_whitelist.cidr,
 line 5: non-null host address bits in "2a01:111:f400:7c00::/48", perhaps you should use "2a01:111:f400::/48" instead:
skipping this rule

I have no idea as to what this could be, I run the list generation normally each day.

cidr map /etc/postfix/postscreen_spf_whitelist.cidr, line 941: non-null host address bits in "2607:13c0:0002:0000:0000:0000:0000:1000/115", perhaps you should use "2607:13c0:2::/115" instead: skipping this rule
is there a way to set IPv4 only CIDRs?

same here, returned yesterday.
seeing that the last commit in this repo is 6 years old (!) maybe someone ought to fork it.

seeing the network graph, @nabbi seems to be doing something that might fix this issue.

seeing the network graph, @nabbi seems to be doing something that might fix this issue.

I've added a "quick and dirty" fix to my local install in line 361 of /usr/local/bin/postwhite/postwhite
cat "${tmp5}" | grep -E '^[0-9]{3}[.][0-9]{3}[.][0-9]{3}[.].*' >> "${postfixpath}"/"${whitelist}"
Getting IPv6 addresses, just to remove than in the final result is of course a bit of waste of time.
I also noticed, quite a lot of IPs are not in the final cidr list.
e.g: amazon.de  -> amazon.com -> spf1.amazon.com -> 549	IN	TXT	"v=spf1 ip4:<IP_ADDRESS>/19 ip4:<IP_ADDRESS>/21 ip4:<IP_ADDRESS>/19 ip4:<IP_ADDRESS>/27 ip4:<IP_ADDRESS>/28 ip4:<IP_ADDRESS>/32 ip4:<IP_ADDRESS>/24 ip4:<IP_ADDRESS>/26 ip4:<IP_ADDRESS>/28 ip4:<IP_ADDRESS>/28 ip4:<IP_ADDRESS>/28 -all"
[missing]  <IP_ADDRESS>/2
[missing]  <IP_ADDRESS>/28

I patched my nabbi/postwhite fork to use an external script nabbi/route-summarization for the network summarization. It has been quick and accurate for my needs.


[Q] REMOTE_STORE_MERGE_RESULTS = True doesn't seem to work when schema changes

Hello all,
We're attempting to convert from a schema that has a 10s  default to  another that has a 60s default.      I performed the following steps:

Updated  storage-schemas.conf for our graphite-cache cluster so that   the default schema has    retentions = 60s:14d, with the understanding that pre-existing metrics would retain the old schema
Created a new graphite-cluster,  also with retentions = 60s:14d by default, with the expectation that all metrics will get the new retetion
Set up  graphite-web on our relay layer, which has REMOTE_STORE_MERGE_RESULTS = True,  to cluster with both the old and new cluster
Started marking query reuqests against the relay layer graphite-webs, and observed flapping where each time  grafana reloads, we randomly bounce between a long history of metrics, and  a much shorter visualization that is clearly just metrics from the new cluster.

Does REMOTE_STORE_MERGE_RESULTS = True work against  graphite-webs that have heterogenous clusters?     We have quite a bit of metrics and we're hoping that we can avoid shutting caches down  to rewrite them with whisper

Hi @jdblack ,
Theoretically, that's possible - but nobody implemented that. IIRC carbonapi has ability to merge different retentions - but maybe I'm wrong.

Hi @jdblack
Theoretically (I didn't test it but should work) you can use carbonapi only as "merger".
You can set up carbonapi which will have 2 backends with different retentions, like:
...
backendsv2:
        backends:
          -
            groupName: "graphite-web"
            protocol: "msgpack"
            lbMethod: "broadcast"
            maxTries: 3
            maxBatchSize: 0
            keepAliveInterval: "10s"
            concurrencyLimit: 0
            maxIdleConnsPerHost: 1000
            servers:
                - "http://<ip1>:<port1>?format=msgpack"
                - "http://<ip2>:<port2>?format=msgpack"

and then point another graphite-web to carbonapi as `CLUSTER_SERVERS=["<carbonapi_ip>:<carbonapi_port>"]


Updated the UCP GUI prompts

Updated the UCP GUI prompts for 'Grant Creation' to reflect the current version of UCP terminology

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Deploy preview for docsdocker ready!
Built with commit 757150ba546618306551d6ba431af260b908466e
https://deploy-preview-8423--docsdocker.netlify.com


feat(plugin): @robojs/cors

CLA Assistant Lite bot: 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 can sign the CLA by just posting a Pull Request Comment same as the below format.

I have read the CLA Document and I hereby sign the CLA

You can retrigger this bot by commenting recheck in this Pull Request

I have read the CLA Document and I hereby sign the CLA

Looks great! Thank you for this!


Fix aspect ratio on hmd projection matrix

This fixes #37582
Aspect ratio wasn't applied correctly in the hmd projection calculation resulting in a distorted image:

Applied it the wrong way around, after correcting we get:

Seeing VR hasn't been given love yet on 4.0 I did this fix on 3.2, but obviously applies to both. @akien-mga is that a problem or should I submit a separate PR for 4?

Seeing VR hasn't been given love yet on 4.0 I did this fix on 3.2, but obviously applies to both. @akien-mga is that a problem or should I submit a separate PR for 4?

The normal workflow would to make a PR against master, with the cherrypick:3.2 label so that I cherrypick it.

I'll merge and cherry-pick in master exceptionally.


Problem with addons after recent signature debacle and it's hotfixes: After update that's supposed to fix the issue = still not working

Hi,
after todays update the issue should be fixed, but not for me. Therefore I assume it has to be the user.js that breaks or prevents the hotfix from working. And that's the reason why I ask here. You know the user.js.
I tried changing these setting in the user.js in order make studies work, but to no avail:
app.normandy.enabled
app.normandy.run_interval_seconds
app.normandy.first_run
datareporting.healthreport.uploadEnabled
datareporting.policy.dataSubmissionEnabled
app.shield.optoutstudies.enabled
That seemed to at least make it receive the studies:
hotfix-update-xpi-signing-intermediate-bug-1548973•Active
hotfix-reset-xpi-verification-timestamp-1548973•Complete
So now I have the hotfixes AND the new update installed, but it still doesn't work.
Anything else I can try?

The only thing that this user.js does that could affect it, is that we had disabled normandy and telemetry - you need to enable telemetry in order to get studies. Sp I would assume you reset those as well?
If you received the studies then it should have worked. Did you restart Firefox? Do the studies show as completed in about:studies?
https://blog.mozilla.org/addons/2019/05/04/update-regarding-add-ons-in-firefox/

We’re aware that some users are reporting that their extensions remain disabled with both studies active. We’re tracking this issue on Bugzilla in bug 1549078

Firefox 66.0.4 is now officially out. Just update

FWIW, I manually applied the hotifx and it worked for me with all normandy and telemetry disabled. I didn't change any of my prefs - so the prefs don;t prevent the hotfix from being applied


Update audio-conferencing-common-questions.md

https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/6877
Updated dial-pad commands

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@tonysmit PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


⚠ Nebulance has degraded performance

In 84640e7, Nebulance ($NBL) experienced degraded performance:

HTTP code: 502
Response time: 1143 ms

Resolved: Nebulance performance has improved in aa37c8c after 10 minutes.


fix(service): allow setting translations in deep objects

This PR fixes the issue mentioned in #216 .
When we pass a key with nested properties, for example, profilePage.header.name, it will set the key as is instead of creating the necessary nested objects.

 Currently   After this PR

{
 "profilePage.header.name": "Test"
}

{
 "profilePage": {
     "header": {
         "name": "Test"
     }
  }
}

This change will check if the received key has ., creating the nested objects automatically if they do not exist in the appropriate translation object.

What is going on with this? Can anyone check it and merge it?

Integrated in upcoming V16
https://github.com/CodeAndWeb/ngx-translate/commit/02567229af93af6c915a73abd5b88ba41c4ed386

In your fork v16, please do not confuse people

Fixed in @ngx-translate/core@16


Progress tag position covers the toolbar dropdown after downloading a file

Operation System: Ubuntu 16.04
Beaker Version: v0.7.5 latest from master (4cedb3)
After downloading a file the <progress> tag covers part of the dropdown menu.

Only seeing this on my Linux machine.
PS: thanks for making Beaker it's :100:

Thanks for reporting. That's not right!

I'll take this one. I've been working on the downloads items in the dropdown menu so I can hit this at the same time.

Fixed in the 0.8 branch


Gazette build system & example application; revert ignored routes

Re: ignored routes, see PUB-4117.
This PR otherwise introduces a Docker-ized build system for Gazette, a word-count toy example, and initial Helm charts for standing up Gazette clusters.
build/README.rst provides instructions on building containers, and test/NOTES.rst is my current state of notes on bringing up a cluster with the word-count example for testing.

This change is

Publishing a partial review of first two commits.

Reviewed 6 of 6 files at r1, 14 of 14 files at r2.
Review status: 20 of 38 files reviewed at latest revision, 11 unresolved discussions.

build/Dockerfile.gazette-base, line 4 at r2 (raw file):

ENV ROCKSDB_VERSION 5.3.5
ENV PROTO_VERSION 3.4.0

Opinion: Consider moving ENV commands below the RUN apt-get.
Docker's docs prefer setting multiple variables in a single line since it will produce a single layer for caching. My own (weak) preference is to move each closer to it's first usage so after an update, fewer cache layers are invalidated.
Q: Do we care about having these env vars in the final container? If not, should we inline them so they don't appear there?

build/Dockerfile.gazette-base, line 18 at r2 (raw file):

      libzstd-dev \
      unzip \
      zlib1g-dev \

Q: Where does this list come from? It has some entries that use different versions from what we have used elsewhere (e.g., libgflags-dev vs libgflags2).

build/Dockerfile.gazette-build, line 59 at r2 (raw file):

    ; do \
      mockery -inpkg -name $(basename ${tgt}) -dir /go/src/$(dirname ${tgt}) ; \
    done ;

Thought: I have been thinking about trying a branch where mocks are placed in a mock package "under" the interface's import path and using go:generate directives. That would simplify the command here and keep mocks out of "production" packages.
The caveat is I think this is a worthwhile trade only if we can get away with default mockery options to keep directives minimal. E.g., go:generate mockery -name MyInterface.

build/Dockerfile.gazette-build, line 69 at r2 (raw file):

# TODO(johnny): Use a recursive go install gazette/pkg/...
RUN go install github.com/LiveRamp/gazette/cmd/gazette
RUN go install github.com/LiveRamp/gazette/cmd/run-consumer

Why not use go install github.com/LiveRamp/gazette/cmd/... even before we have gazette/pkg?

build/Dockerfile.gazette-build, line 73 at r2 (raw file):

# Test all packages.
# TODO(johnny): Use a recursive go test gazette/pkg/...
RUN go test github.com/LiveRamp/gazette/async

Why not use go test github.com/LiveRamp/gazette/... even before we have gazette/pkg?

build/README.rst, line 11 at r2 (raw file):

but still require the RocksDB runtime:

  ``docker build . -f build/Dockerfile.gazette-base --tag gazette-base``

FYI, this is how to do code blocks and literal blocks in rST: https://gist.github.com/rupertchen/9b6ca6f1c4fe42eeb05e759d32a31c72.
I've included a short-hand version of :: where it is placed at the end of a paragraph and renders as a single : as you may see it around. I tend to avoid it as thinking about an extra form and saving a couple new lines isn't worth it IMO.

cmd/run-consumer/main.go, line 91 at r2 (raw file):

		LocalDir:        *dir,
		ConsumerRoot:    *root,
		RecoveryLogRoot: filepath.Join(*root, "recovery-logs")[1:], // TODO(johnny): Fix me.

What needs to be fixed here?

consensus/route.go, line 23 at r1 (raw file):

// NewRoute initializes a new Route from the |response| and |node|.
func NewRoute(response *etcd.Response, node *etcd.Node) Route {
	rt := Route{

Should we keep the replacement of the short assignements? Perhaps we should add something about code styles to the project doc soon.

examples/word-count/topics.go, line 57 at r2 (raw file):

// Encode implements topic.Framing.
func (*sentenceFraming) Encode(msg topic.Message, b []byte) ([]byte, error) {

Nit: Value as receiver since sentenceFraming holds no state.
Sentences.Framing = new(sentenceFraming) would still work thought I'd be inclined to swap it to sentenceFraming{}.

examples/word-count/counter/counter.go, line 15 at r2 (raw file):

type counter struct{}

func (c *counter) Topics() []*topic.Description {

Same opinion as for sentenceFraming and shuffler.

examples/word-count/shuffler/shuffler.go, line 16 at r2 (raw file):

type shuffler struct{}

func (c *shuffler) Topics() []*topic.Description {

Same opinion as for sentenceFraming. Additionally could drop c.

Comments from Reviewable

Thanks, PTAL!

Review status: 12 of 38 files reviewed at latest revision, 11 unresolved discussions.

build/Dockerfile.gazette-base, line 4 at r2 (raw file):
Previously, rupertchen (Rupert Chen) wrote…
Opinion: Consider moving ENV commands below the RUN apt-get.
Docker's docs prefer setting multiple variables in a single line since it will produce a single layer for caching. My own (weak) preference is to move each closer to it's first usage so after an update, fewer cache layers are invalidated.
Q: Do we care about having these env vars in the final container? If not, should we inline them so they don't appear there?

Switched these to a single line. Leaving where they are, however: if we're ticking versions of these packages (a very infrequent change), I think we also want to be verifying compatibility with current debian packages. Otherwise there's a minor risk of weird caching affects / "works on my machine".
A: I think they should be available for inspection by downstream containers. Eg, Rocks is very actively developed and functionality / features changes with each release. I can definitely see wanting to be able to sanity check the version I'm running against.

build/Dockerfile.gazette-base, line 18 at r2 (raw file):
Previously, rupertchen (Rupert Chen) wrote…
Q: Where does this list come from? It has some entries that use different versions from what we have used elsewhere (e.g., libgflags-dev vs libgflags2).

since we're building rocks from source (rather than a pre-build deb package), we need the -dev versions of gflags. I also did an audit to ensure we're including dev packages for all compression modes that RocksDB supports so they're available at runtime (in particular, lz4 looks interesting).
In theory we could have a separate runtime container which had most of this, but swapped out libgflags-dev for libgflags2, but IMO that's not worth it (these packages are small, and compiling cgo bindings requires dev packages for most of them anyway).

build/Dockerfile.gazette-build, line 59 at r2 (raw file):
Previously, rupertchen (Rupert Chen) wrote…
Thought: I have been thinking about trying a branch where mocks are placed in a mock package "under" the interface's import path and using go:generate directives. That would simplify the command here and keep mocks out of "production" packages.
The caveat is I think this is a worthwhile trade only if we can get away with default mockery options to keep directives minimal. E.g., go:generate mockery -name MyInterface.

It won't work with un-exported mocks like httpClient. I'm not opposed in principle, but it'd take further refactoring to get there.
I'm not sure what practical value is bought by separating them into a different import path. I did go back and ensure mock_ and pb.go are part of the .dockerignore, to ensure any local copies aren't shipped into the build context.

build/Dockerfile.gazette-build, line 69 at r2 (raw file):
Previously, rupertchen (Rupert Chen) wrote…
Why not use go install github.com/LiveRamp/gazette/cmd/... even before we have gazette/pkg?

good call! done

build/Dockerfile.gazette-build, line 73 at r2 (raw file):
Previously, rupertchen (Rupert Chen) wrote…
Why not use go test github.com/LiveRamp/gazette/... even before we have gazette/pkg?

annoyingly that will also test the entire vendor directory.

build/README.rst, line 11 at r2 (raw file):
Previously, rupertchen (Rupert Chen) wrote…
FYI, this is how to do code blocks and literal blocks in rST: https://gist.github.com/rupertchen/9b6ca6f1c4fe42eeb05e759d32a31c72.
I've included a short-hand version of :: where it is placed at the end of a paragraph and renders as a single : as you may see it around. I tend to avoid it as thinking about an extra form and saving a couple new lines isn't worth it IMO.

thanks. updated.

cmd/run-consumer/main.go, line 91 at r2 (raw file):
Previously, rupertchen (Rupert Chen) wrote…
What needs to be fixed here?

fixed. want recover-logs as a top-level parallel hierarchy, but that requires figuring out how to bootstrap multiple minio buckets on minikube.

consensus/route.go, line 23 at r1 (raw file):
Previously, rupertchen (Rupert Chen) wrote…
Should we keep the replacement of the short assignements? Perhaps we should add something about code styles to the project doc soon.

yes, just because I'd like to leave this as a pure git revert of that commit.

examples/word-count/topics.go, line 57 at r2 (raw file):
Previously, rupertchen (Rupert Chen) wrote…
Nit: Value as receiver since sentenceFraming holds no state.
Sentences.Framing = new(sentenceFraming) would still work thought I'd be inclined to swap it to sentenceFraming{}.

it actually wouldn't still work, making it value recv requires sentenceFraming{}. Done

examples/word-count/counter/counter.go, line 15 at r2 (raw file):
Previously, rupertchen (Rupert Chen) wrote…
Same opinion as for sentenceFraming and shuffler.

Done.

examples/word-count/shuffler/shuffler.go, line 16 at r2 (raw file):
Previously, rupertchen (Rupert Chen) wrote…
Same opinion as for sentenceFraming. Additionally could drop c.

Done.

Comments from Reviewable

Reviewed 17 of 18 files at r3, 8 of 8 files at r4, 3 of 3 files at r5.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

examples/word-count/topics.go, line 57 at r2 (raw file):
Previously, jgraettinger (Johnny Graettinger) wrote…
it actually wouldn't still work, making it value recv requires sentenceFraming{}. Done

Both forms work on the Go Playground: https://play.golang.org/p/f-vTw9GnWb

Comments from Reviewable

Review status: :shipit: all files reviewed at latest revision, all discussions resolved, all commit checks successful.

examples/word-count/topics.go, line 57 at r2 (raw file):
Previously, rupertchen (Rupert Chen) wrote…
Both forms work on the Go Playground: https://play.golang.org/p/f-vTw9GnWb

whaaa, what is this sorcery!?
(you're right).

Comments from Reviewable


Updated go dependencies

Signed-off-by: Andy Tinkham<EMAIL_ADDRESS>Desired Outcome
Bring all our direct go dependencies to their latest versions to remove dependencies on yaml.v3 prior to v3.0.1
Implemented Changes

Updated github.com/gomarkdown/markdown to v0.0.0-20220607163217-45f7c050e2d1
Updated github.com/stretchr/testify to v1.7.2
Updated gopkg.in/yaml.v3 to v3.0.1
Ran go mod tidy

Definition of Done
At least 1 todo must be completed in the sections below for the PR to be
merged.
Changelog

[X] The CHANGELOG has been updated, or
[ ] This PR does not include user-facing changes and doesn't require a
CHANGELOG update

Test coverage

[ ] This PR includes new unit and integration tests to go with the code
changes, or
[X] The changes in this PR do not require tests

Documentation

[ ] Docs (e.g. READMEs) were updated in this PR
[ ] A follow-up issue to update official docs has been filed here: insert issue ID
[X] This PR does not require updating any documentation

Behavior

[ ] This PR changes product behavior and has been reviewed by a PO, or
[ ] These changes are part of a larger initiative that will be reviewed later, or
[X] No behavior was changed with this PR

Security

[X] Security architect has reviewed the changes in this PR,
[ ] These changes are part of a larger initiative with a separate security review, or
[ ] There are no security aspects to these changes

Something's borked with the go.sum. Need an eng to look at it?

Think I got it. The release-testing go.sum was the problematic one. Once I updated that go.mod and ran go mod tidy, everything seems to have worked.


Android - Taxes - Save button appears above the keyboard with huge spacing in Name page

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.67-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause Internal Team
Action Performed:

Launch the app.
Go to workspace settings > Taxes.
Tap Add rate.
Tap Name.

Expected Result:
Save button will not appear above the keyboard with huge spacing.
Actual Result:
Save button appears above the keyboard with huge spacing or overlap with keyboard.
Same happens in Report fields.
Seems issue is repro only with Samsung devices. Tester used  Samsung Galaxy Z Fold4 device
Workaround:
Unknown
Platforms:

[x] Android: Standalone
[x] Android: HybridApp
[ ] Android: mWeb Chrome
[ ] iOS: Standalone
[ ] iOS: HybridApp
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/294e3fef-9f3e-47ca-acb3-c16600dab3ad
https://github.com/user-attachments/assets/9fc9abc6-91e2-461a-a692-53f51de93bdb

View all open jobs on GitHub

Hello, I'm Kiryl from Margelo expert agency and I'd like to work on that problem (most likely this regression was introduced by my changes in edge-to-edge PR).

Fix CPed

Not overdue, payment on Dec 7.

Payment for this issue was handled here for all edge-to-edge mode PRs. No payment is due here.


i+=1 as a only code line in a for loop didn't work normally

What version of Go are you using (go version)?

$ go version
go version go1.13.5 linux/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN="/home/me/go/bin"
GOCACHE="/home/me/.cache/go-build"
GOENV="/home/me/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/me/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build161703294=/tmp/go-build -gno-record-gcc-switches"

What did you do?

1. origin question
run following go script and get different output with and without the comment line
package main

import (
        "fmt"
        "time"
)

func main() {
        var i = 0

        go func() {
                for {
                        i += 1
                //      time.Sleep(1*time.Nanosecond)     <- this comment line
                }
        }()

        for {
                fmt.Println("i is", i)
                time.Sleep(time.Second)
        }
}

with the comment line I get
$ go run main.go
i is 0
i is 3673005
i is 7360961
i is 11182533
i is 14892563
i is 18696280
i is 21821713
....

but strangely, without that comment line I get:
$ go run main.go
i is 0
i is 0
i is 0
i is 0
i is 0
i is 0
....

2. debug by checking assemble code
with and without the comment line I get different assemble code:
assemble code shown below include the anonymous function run by go routine only.
without that comment line:
....

TEXT main.main.func1(SB) /home/me/go/src/github.com/trainyao/test/main.go
		for {
  0x48d0c0		eb00			JMP 0x48d0c2
			i += 1
  0x48d0c2		eb00			JMP 0x48d0c4
  0x48d0c4		eb00			JMP 0x48d0c6
  0x48d0c6		ebfa			JMP 0x48d0c2

.....

with that comment line:
...

TEXT main.main.func1(SB) /home/me/go/src/github.com/trainyao/test/main.go
	go func() {
  0x48d0c0		64488b0c25f8ffffff	MOVQ FS:0xfffffff8, CX
  0x48d0c9		483b6110		CMPQ 0x10(CX), SP
  0x48d0cd		7636			JBE 0x48d105
  0x48d0cf		4883ec10		SUBQ $0x10, SP
  0x48d0d3		48896c2408		MOVQ BP, 0x8(SP)
  0x48d0d8		488d6c2408		LEAQ 0x8(SP), BP
		for {
  0x48d0dd		eb00			JMP 0x48d0df
			i += 1
  0x48d0df		eb00			JMP 0x48d0e1
  0x48d0e1		488b442418		MOVQ 0x18(SP), AX
  0x48d0e6		488b00			MOVQ 0(AX), AX
  0x48d0e9		488b4c2418		MOVQ 0x18(SP), CX
  0x48d0ee		48ffc0			INCQ AX
  0x48d0f1		488901			MOVQ AX, 0(CX)
			time.Sleep(1*time.Nanosecond)
  0x48d0f4		48c7042401000000	MOVQ $0x1, 0(SP)
  0x48d0fc		e8df71fbff		CALL time.Sleep(SB)
  0x48d101		eb00			JMP 0x48d103
			i += 1
  0x48d103		ebda			JMP 0x48d0df
	go func() {
  0x48d105		e8f646fcff		CALL runtime.morestack_noctxt(SB)
  0x48d10a		ebb4			JMP main.main.func1(SB)

...

it seems like go complier ignore that i+=1 when complie into assemble code, and make that i+=1 do nothing.
command I use to generate assemble code:
$ CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build --gcflags "-N -l" -o main main.go
$ go tool objdump -S main > main.S

What did you expect to see?
output of main.go is the same, with and without that comment line
What did you see instead?
different output

This problem also happens on go version go1.13.4 linux/amd64.
package main

import (
	"fmt"
	"time"
)

func main() {
	var i, j int

	noop := func() {}

	onlyAdd := func() {
		fmt.Println("onlyAdd runs")
		for {
			i += 1
		}
	}

	notOnlyAdd := func() {
		fmt.Println("notOnlyAdd runs")
		for {
			j += 1
			noop()
		}
	}

	go onlyAdd()
	go notOnlyAdd()

	for {
		fmt.Println("i is", i, " and j is", j)
		time.Sleep(time.Second)
	}
}

output:
i is 0  and j is 0
onlyAdd runs
notOnlyAdd runs
i is 0  and j is 715125111
i is 0  and j is<PHONE_NUMBER>
i is 0  and j is<PHONE_NUMBER>
i is 0  and j is<PHONE_NUMBER>
i is 0  and j is<PHONE_NUMBER>
i is 0  and j is<PHONE_NUMBER>
i is 0  and j is<PHONE_NUMBER>
i is 0  and j is<PHONE_NUMBER>
^C

Same issue on macos on go1.13.4 darwin/amd64.
i is 0  and j is 0
onlyAdd runs
notOnlyAdd runs
i is 0  and j is 800290823
i is 0  and j is<PHONE_NUMBER>
i is 0  and j is<PHONE_NUMBER>
i is 0  and j is<PHONE_NUMBER>
i is 0  and j is<PHONE_NUMBER>
i is 0  and j is<PHONE_NUMBER>
...

You have a data race. You can see it if you do go run -race main.go, or if you read https://golang.org/doc/articles/race_detector.html.
You should use https://golang.org/wiki/Questions for general questions about why your code doesn't work.

if use go run -race main.go,
it  output
i is 53406210
i is 106633590
i is 160145249
i is 213722371
i is 266922550

You have a data race. You can see it if you do go run -race main.go, or if you read https://golang.org/doc/articles/race_detector.html.
You should use https://golang.org/wiki/Questions for general questions about why your code doesn't work.

I know there is a data race in the code, but a data race would not make the for loop not adding i variable right?  and how to explain the assemble code generated....will data race effect code compile?

for {
i += 1
}

This is an infinite loop with no synchronization. No other thread is guaranteed to ever see the increment (because that would be a data race, and behavior under data races is undefined), so the compiler optimizes it away.


llm collections show collection_id command

I'm going with llm collections show xxx for consistency with llm templates show xxx.

Originally posted by @simonw in https://github.com/simonw/llm/issues/229#issuecomment-1712940173

Relevant conversation about the need to export embeddings to share with other people: https://discord.com/channels/823971286308356157/1128504153841336370/1152337623394824282
This command should have --format json/csv/etc options which cause it to be output in the same formats that work with llm embed-multi.


Failed to create .hdf5 files

Hi @sgrvinod
I got this error when i run the create_input_files.py
Traceback (most recent call last):
File "D:\PyTorch-Tutorial-to-Image-Captioning-master\create_input_files.py", line 5, in
create_input_files(dataset='coco',
File "D:\PyTorch-Tutorial-to-Image-Captioning-master\utils.py", line 158, in create_input_files
json.dump(caplens, j)
File "h5py_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
File "h5py_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
File "C:\Users\HORIO-LAB\AppData\Roaming\Python\Python39\site-packages\h5py_hl\files.py", line 544, in exit
self.close()
File "C:\Users\HORIO-LAB\AppData\Roaming\Python\Python39\site-packages\h5py_hl\files.py", line 526, in close
self.id._close_open_objects(h5f.OBJ_LOCAL | h5f.OBJ_FILE)
File "h5py_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
File "h5py_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
File "h5py\h5f.pyx", line 358, in h5py.h5f.FileID._close_open_objects
RuntimeError: Can't decrement id ref count (unable to extend file properly)

Do check this out  - https://github.com/sgrvinod/a-PyTorch-Tutorial-to-Image-Captioning/issues/7#issuecomment-410666483


Read profile and key from _FILE secrets

See https://docs.docker.com/engine/swarm/secrets/#advanced-example-use-secrets-with-a-wordpress-service
tests:
NEXTDNS_PROFILE=... NEXTDNS_API_KEY=... go test ./...
?       github.com/raylas/nextdns-exporter      [no test files]
ok      github.com/raylas/nextdns-exporter/internal/api (cached)
ok      github.com/raylas/nextdns-exporter/internal/util        0.150s

tested via:
NEXTDNS_PROFILE_FILE=../nextdns/profile NEXTDNS_API_KEY_FILE=../nextdns/api go run .

@raylas PTAL :)

@raylas yay, finally i can use it. somehow missed the update.


Scrollbar slider difficult to see in dark themes

VSCode Version: 1.3.1
OS Version: Windows 7

I'm colour blind (red/green, the most common type), and when using any dark theme I really struggle to see the scrollbar slider - there's just not enough contrast.
It would be helpful if themes were able to control the scrollbar colours. It would also be helpful if the scrollbar width could be increased (ideally themeable).

yes, make it themeable please, at least for colors and transparency,  it's really difficult to see scrollbar, also i don't really like to see code cross the slider. Let us choose the right setting.

This is supported with April release, the related colors to set are:
scrollbarShadow
scrollbarSliderActiveBackground
scrollbarSliderBackground
scrollbarSliderHoverBackground
(note that color names might still change!)


feat: Update references to new name 'TraceGateway' except for Kubernetes resources

Description

Since we're favoring the new name "TraceGateway" over "TraceCollector," this PR focuses on updating all references accordingly. The deployment and related resources still maintain the name trace-collector. Achieving this shift involves more than just renaming strings. It requires implementing migration logic in the controller.
Changes proposed in this pull request:

Rename the variables/comments/test cases
Rename the Grafana dashboard
Rename the status condition reasons and messages (for TracePipeline and Telemetry CRs)

Related Issues and Documents

Related issues:
https://github.com/kyma-project/kyma/issues/17158
Traceability

[x] The PR is linked to a GitHub Issue.
[x] New features have a milestone label set.
[x] New features have defined acceptance criteria in a corresponding GitHub Issue, and all criteria are satisfied with this PR.
[x] The corresponding GitHub Issue has a respective area label.
[ ] The follow-up issues (if any) are linked in the Related Issues section.

Testability
The feature is unit-tested:

[x] Yes.
[ ] No, because unit tests are not needed.
[ ] No, because of ...

The feature is e2e-tested:

[x] Yes.
[ ] No, because e2e-tests are not needed.
[ ] No, because of ...

Tests conducted for the PR:

Codebase

[x] My code follows the Effective Go style guidelines.
[x] The code was planned and designed following the defined architecture and the separation of concerns.
[x] The code has sufficient comments, particularly for all hard-to-understand areas.
[x] This PR adds value and shows no feature creep.
[x] I have augmented the test suite that proves my fix is effective or that my feature works.
[x] Adjusted the documentation if the change is user-facing.

/retest

/retest


bioconda

This application should be import in bioconda
https://bioconda.github.io/
unfortunnaly, there is another python package called sickle

It looks like it already is... it's called sickle-trim.

Nik.

On Thu, Feb 2, 2017 at 2:52 AM, sacha schutz<EMAIL_ADDRESS>wrote:

This application should be import in bioconda
https://bioconda.github.io/
unfortunnaly, there is another python package called sickle
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/najoshi/sickle/issues/50, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAlGodkh4bImdOmOsMLlLwt7MZZORbI-ks5rYbVigaJpZM4L09tJ
.

--
Nikhil Joshi
Bioinformatics Analyst/Programmer
UC Davis Bioinformatics Core
http://bioinformatics.ucdavis.edu/
najoshi -at- ucdavis -dot- edu
530.752.2698 (w)

Any chance of getting it on the osx-64 channels? I try and receive the following output:

Any chance of getting it on the osx-64 channels? I try and receive the following output:
$ conda install sickle-trim
Fetching package metadata ...............
PackageNotFoundError: Package missing in current osx-64 channels:

sickle-trim


Fix: Handle Craft Links with Custom Domains by Implementing getCraftSlug Function

The Craft application used for displaying notes has introduced a feature allowing users to share links with custom domains. Previously, links followed the pattern "https://www.craft.do/s/" with a 23-character slug, which was sliced to extract the necessary ID. However, this approach fails with the new custom domain links, causing issues in preview images and other functionalities. This affects new users configuring the Craft settings for the project as well.
To address this problem, I have implemented a getCraftSlug function in the lib directory. This function correctly extracts the slug from both the old and new link formats, ensuring the application functions correctly without errors. This change ensures that both legacy and new links are handled seamlessly, maintaining the integrity of the application for all users.

@izuolan , can you check it?


TableId compression on block level

Since the TableId is only used after decoding the block, we can store it in the block without changing the BlockMeta to ensure compatibility with the upper-level code.


Error

  App version: 0.1.4 (ad62b84)

Android version: 10 (29)
Device brand: Redmi
Device manufacturer: Xiaomi
Device model: M2003J15SC (merlinnfc)
MPV version: v0.38.0-743-gad7976c33e
ffmpeg version: 0b6d7cd9d9
libplacebo version: v7.349.0 (v7.349.0-9-gefb89342)
  Exception:
  androidx.startup.StartupException: lateinit property fileName has not been initialized
at live.mehiz.mpvkt.ui.player.PlayerActivity$event$3.invokeSuspend(SourceFile:116)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(Unknown Source:8)
at kotlinx.coroutines.DispatchedTask.run(Unknown Source:94)
at androidx.core.app.ActivityRecreator$1.run(SourceFile:15)
at kotlinx.coroutines.scheduling.TaskImpl.run(Unknown Source:2)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(SourceFile:92)
Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@f34a6b8, Dispatchers.IO]

  Logcat:

The crash error was caused by opening a link of this type:
https://vk146-2.vkuser.net/?expires=1726082214055&srcIp=<IP_ADDRESS>&pr=40&srcAg=UNKNOWN_ANDROID&ms=<IP_ADDRESS>&type=5&subId=7300623502032&sig=4p3w5KawGXo&ct=0&urls=<IP_ADDRESS>%3B<IP_ADDRESS>&clientType=13&appId=512000384397&zs=132&id=7300408347344

I'll look into it tomorrow, thanks for the report.

mpv.conf:
log-file=/storage/emulated/0/mpvlog.txt
file not created, i think because there is no permission to the file manager

The crash error was caused by opening a link of this type (link is not static):
https://vkvd206.mycdn.me/?expires=1726110057013&srcIp=<IP_ADDRESS>&pr=40&srcAg=UNKNOWN_ANDROID&ms=<IP_ADDRESS>&type=5&subId=6768006335101&sig=235ATKDS87Q&ct=0&urls=<IP_ADDRESS>&clientType=13&appId=512000384397&zs=132%3B11&id=6767891516029

Seems like it expired 😔

@abdallahmehiz
https://vkvd206.mycdn.me/?expires=1726114147251&srcIp=<IP_ADDRESS>&pr=40&srcAg=UNKNOWN_ANDROID&ms=<IP_ADDRESS>&type=5&subId=6768006335101&sig=dmaFvMb-hGU&ct=0&urls=<IP_ADDRESS>&clientType=13&appId=512000384397&zs=132%3B11&id=6767891516029

I tried adding it to the manifest:

it didn't work

You can select an mpvKt configuration directory and place the log file there...

@abdallahmehiz
log not created.

you're giving it permission to the root of shared storage? I don't know if android allows that...

@abdallahmehiz
yes I do and only the mpv.conf configuration file is created

I think that's cause I am creating it using Android's SAF, but mpv can't make SAF calls...

Also... you shouldn't do that (choosing the entirety of your shared storage as an mpv configuration). Cause what the app is doing, is copying every single file in there recursively to its application directory...
make sure to clear your mpv configuration from the settings.

@abdallahmehiz
I deleted the same from the settings the log was not created.

I think that's cause I am creating it using Android's SAF, but mpv can't make SAF calls...

Just like i said, mpv can't create log files on shared storage (at least without WRITE_EXTERNAL_STORAGE permission) even if you set the config dir.

@abdallahmehiz
yes the file was created only in
/data/data/live.mehiz.mpvkt/files

Btw, can you provide me a new, regenerated link so I can debug the crash?

@abdallahmehiz
https://vk146-1.vkuser.net/?srcIp=<IP_ADDRESS>&pr=40&expires=1726325826071&srcAg=UNKNOWN_ANDROID&fromCache=1&ms=<IP_ADDRESS>&type=5&subId=6768006335101&sig=fzGDEYPS2SE&ct=0&urls=<IP_ADDRESS>%3B<IP_ADDRESS>&clientType=13&appId=512000384397&zs=132&id=6767891516029

@abdallahmehiz
What did you do to make it work smoothly with gpu-next with the gpu-hq profile ? Goes smoothly )

Didn't do anything special...
Maybe it's because you have the YUV420P pixel format enabled in the settings (enabled by default), which from my testing, increases performance a lot.

well then I am not sure what's causing it, I have applied any kind of optimizations.

@abdallahmehiz
In mpv goes poorly there, but mpvkt does great.

Why is that :thinking:


Logging not working

Hi,
The logged messages aren't readable, the website seems offline. Can I move them to pastebin?

That did the trick, thanks!


plugin fails to work from different app path

I noticed that when my app is cloned by somebody else, whenever they try to run, it fails to create a bundle with a warning
> cordova run browser -- --livereload

Script file does't exist and will be skipped: <app path>/plugins/cordova-plugin-webpack/dist/webpackCompile.js

Script file does't exist and will be skipped: <app path>/plugins/cordova-plugin-webpack/dist/webpackServe.js

startPage = index.html

Static file server running @ http://localhost:8000/index.html

CTRL + C to shut down

304 /index.html

(node:7934) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated

304 /css/index.css

304 /cordova.js

404 /index.bundle.js

It looks like the problem is caused by _where attribute in plugins/cordova-plugin-webpack/package.json that holds absolute path to the app folder when this plugin was installed
As for now, the workaround is to
cordova plugins rm cordova-plugin-webpack
cordova plugins add cordova-plugin-webpack

After pulling other people commits

@romanlv Are you example repository to reproduce it?

@kotarella1110
Try this one https://github.com/romanlv/cordova-webpack-test
I experimented with it a bit more, it looks like npm i does not install everything and cordova plugins add cordova-plugin-webpack is required to fully install it (unless it's a required step, I'm new to cordova development)

@romanlv Thanks for providing the example 👍
I will look into this.

@romanlv Because the platforms and plugins depend on the individual, you should ignore them when managing your Cordova project with git.
# .gitignore
/platforms
/plugins

After cloning, perform the following steps.
npm i
cordova prepare

@kotarella1110 Thanks for the help, the problem is solved


[S3] This enables the use of IAM roles and fancy stuff with AWS creds

@mistercrunch
For review. I need to attach a testing plan, but this worked fine in a manual test script.

Merge it!


[zh] sync 2023-01-06-unhealthy-pod-eviction-policy-for-pdb.md

Add zh text to this blog:
content/zh-cn/blog/_posts/2023-01-06-unhealthy-pod-eviction-policy-for-pdb.md

Preview: https://deploy-preview-38899--kubernetes-io-main-staging.netlify.app/zh-cn/blog/2023/01/06/unhealthy-pod-eviction-policy-for-pdbs/

/approve


picker.on is not a function

How do you use the on event? I always get picker.on is not a function, the picker shows so it has worked up until the event.
<script type="module">
  import { createPicker } from "https://unpkg.com/picmo@latest/dist/index.js?module";
  const container = document.querySelector('.pickerContainer');
  const picker = createPicker({
    rootElement: container
  });
  picker.on('emoji:select', selection => {
    console.log('Selected emoji: ', selection.emoji);
  });
</script>

.on is now .addEventListener
But it is not documented.

Which documentation were you looking at? addEventListener is documented in the README as well as the API on picmojs.com

https://picmojs.com/docs/usage/emoji-selection
const picker = createPicker();

picker.on('emoji:select', selection => {
  console.log('Selected emoji: ', selection.emoji);
});```

Aha, thanks! Looks like I missed a spot. I’lol make sure it’s up to date, thanks!

Updated: https://picmojs.com/docs/usage/emoji-selection/
const picker = createPicker();

picker.addEventListener('emoji:select', selection => {
  console.log('Selected emoji: ', selection.emoji);
});


Add blob size limits. (#2705)

Motivation
Large blobs can make messages containing them exceed the gRPC message limit, and require a lot of storage and bandwidth.
In addition, we need to guard against small compressed bytecode that is excessively large when decompressed.
On testnet-boole, I successfully published a 6 MiB blob, but failed with 8 MiB.
Proposal
Backport https://github.com/linera-io/linera-protocol/pull/2705, but hard-code the limits to remain backwards-compatible.
Make the blob limit 3 MiB, so that two blobs (e.g. contract and service bytecode) fit in a block.
Make the bytecode limit 30 MiB.
Test Plan
The tests were backported, too.
Release Plan
This is the backport of https://github.com/linera-io/linera-protocol/pull/2705 to devnet_2024_10_21.
Links

main version: https://github.com/linera-io/linera-protocol/pull/2705
testnet_boole version: https://github.com/linera-io/linera-protocol/pull/2720
reviewer checklist

I'll also add https://github.com/linera-io/linera-protocol/pull/2726 to this…


add totalMemory to hl as other targets

System.totalMemory returns  0 for hash link so I've added the ability to HL to return a value.

Closing because merged #2561 instead.


Failed to install with external PostgreSQL

I have tried to install redmine with external PostgreSQL, but it doesn't work for me with the logs below.
Seems the problem is:

redmine     | bundler: failed to load command: rake (/usr/bin/rake)
redmine     | Bundler::Dsl::DSLError:

Can someone tell me how to make it work?
Logs

redmine     | Initializing logdir...
redmine     | Initializing datadir...
redmine     | Symlinking dotfiles...
redmine     | Installing configuration templates...
redmine     | Configuring redmine...
redmine     | Configuring redmine::database
redmine     | Configuring redmine::unicorn...
redmine     | Configuring redmine::secret_token...
redmine     | Configuring redmine::max_concurrent_ajax_uploads...
redmine     | Configuring redmine::sudo_mode...
redmine     | Configuring redmine::autologin_cookie...
redmine     | Configuring redmine::backups...
redmine     | Configuring nginx...
redmine     | Configuring nginx::redmine...
redmine     | New redmine version. Clearing cache
redmine     | Migrating database. Please be patient, this could take a while...
redmine     | bundler: failed to load command: rake (/usr/bin/rake)
redmine     | Bundler::Dsl::DSLError:
redmine     | [!] There was an error parsing Gemfile: Too many levels of symbolic links - /home/redmine/redmine/vendor/bundle/ruby/2.4.0/specifications. Bundler cannot continue.
redmine     |
redmine     |  #  from /home/redmine/redmine/Gemfile:45
redmine     |  #  -------------------------------------------
redmine     |  #  require 'erb'
redmine     |  >  require 'yaml'
redmine     |  #  database_file = File.join(File.dirname(FILE), "config/database.yml")
redmine     |  #  -------------------------------------------
redmine     |
redmine     |   /usr/lib/ruby/2.4.0/rubygems/specification.rb:752:in []' redmine     |   /usr/lib/ruby/2.4.0/rubygems/specification.rb:752:in gemspec_stubs_in'
redmine     |   /usr/lib/ruby/2.4.0/rubygems/specification.rb:777:in block in map_stubs' redmine     |   /usr/lib/ruby/2.4.0/rubygems/specification.rb:774:in each'
redmine     |   /usr/lib/ruby/2.4.0/rubygems/specification.rb:774:in flat_map' redmine     |   /usr/lib/ruby/2.4.0/rubygems/specification.rb:774:in map_stubs'
redmine     |   /usr/lib/ruby/2.4.0/rubygems/specification.rb:766:in installed_stubs' redmine     |   /usr/lib/ruby/2.4.0/rubygems/specification.rb:853:in stubs_for'
redmine     |   /usr/lib/ruby/2.4.0/rubygems/dependency.rb:279:in matching_specs' redmine     |   /usr/lib/ruby/2.4.0/rubygems/dependency.rb:300:in to_specs'
redmine     |   /usr/lib/ruby/2.4.0/rubygems/dependency.rb:320:in to_spec' redmine     |   /usr/lib/ruby/2.4.0/rubygems/core_ext/kernel_gem.rb:65:in gem'
redmine     |   /usr/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:47:in require' redmine     |   /usr/lib/ruby/2.4.0/yaml.rb:6:in <top (required)>'
redmine     |   /usr/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in require' redmine     |   /usr/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in require'
redmine     |   /home/redmine/redmine/Gemfile:45:in eval_gemfile' redmine     |   /var/lib/gems/2.4.0/gems/bundler-2.1.3/lib/bundler/dsl.rb:47:in instance_eval'
redmine     |   /var/lib/gems/2.4.0/gems/bundler-2.1.3/lib/bundler/dsl.rb:47:in eval_gemfile' redmine     |   /var/lib/gems/2.4.0/gems/bundler-2.1.3/lib/bundler/dsl.rb:12:in evaluate'
redmine     |   /var/lib/gems/2.4.0/gems/bundler-2.1.3/lib/bundler/definition.rb:34:in build' redmine     |   /var/lib/gems/2.4.0/gems/bundler-2.1.3/lib/bundler.rb:195:in definition'
redmine     |   /var/lib/gems/2.4.0/gems/bundler-2.1.3/lib/bundler.rb:143:in setup' redmine     |   /var/lib/gems/2.4.0/gems/bundler-2.1.3/lib/bundler/setup.rb:20:in block in <top (required)>'
redmine     |   /var/lib/gems/2.4.0/gems/bundler-2.1.3/lib/bundler/ui/shell.rb:136:in with_level' redmine     |   /var/lib/gems/2.4.0/gems/bundler-2.1.3/lib/bundler/ui/shell.rb:88:in silence'
redmine     |   /var/lib/gems/2.4.0/gems/bundler-2.1.3/lib/bundler/setup.rb:20:in `<top (required)>'

Here is my docker-compose file:

redmine:
container_name: redmine
image: sameersbn/redmine:4.1.0
environment:
- DB_ADAPTER=postgresql
- DB_ENCODING=utf8
- DB_HOST=<IP_ADDRESS>
- DB_PORT=5432
- DB_NAME=redmine
- DB_USER=redmine
- DB_PASS=redmine
- TZ=Asia/Shanghai
- REDMINE_PORT=10083
- REDMINE_HTTPS=false
- REDMINE_SECRET_TOKEN=000000000
restart: always
ports:
- "10083:10083"
volumes:
- type: bind
source: /opt/dockers/redmine/data
target: /home/redmine/data

Could you upload your compose file as a file?  I've just spent 10 minutes trying to fix all the syntax errors from copy pasting it.

redmine | bundler: failed to load command: rake (/usr/bin/rake)
redmine | Bundler::Dsl::DSLError:
redmine | [!] There was an error parsing Gemfile: Too many levels of symbolic links - /home/redmine/redmine/vendor/bundle/ruby/2.4.0/specifications. Bundler cannot continue.

I'm also not sure why having an external postgres would cause you issues running rake.  I'm wondering if something got corrupted in the container.  Make sure to run docker-compose down to delete the container.

Could you upload your compose file as a file? I've just spent 10 minutes trying to fix all the syntax errors from copy pasting it.

Here is my docker-compose file:
https://we.tl/t-vgGUTEbbOT
I use docker-compose ps -a to see containers,  seems docker doesn't create a container when it happened.

Running your example, I made some changes but redmine can't connect to the database.  It doesn't look like the mysql container creates a default database for redmine...
mysql       | 2020-02-17T16:03:36.969790Z 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.
mysql       | 2020-02-17T16:03:36.981413Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.19'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server - GPL.
mysql       | 2020-02-17T16:03:37.101279Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: '/var/run/mysqld/mysqlx.sock' bind-address: '::' port: 33060

redmine     | Configuring redmine::database...........................................................
redmine     | Could not connect to database server. Aborting...

The redmine container can contact the server but it doesn't have a redmine database.
 $ docker-compose exec redmine mysqlshow -h mysql -p
WARNING: Some services (redis) use the 'deploy' key, which will be ignored. Compose does not support 'deploy' configuration - use `docker stack deploy` to deploy to a swarm.
Enter password:
+--------------------+
|     Databases      |
+--------------------+
| information_schema |
| mysql              |
| performance_schema |
| sys                |
+--------------------+

Changes to docker-compose
 $ diff -u docker-compose.yml.orig docker-compose.yml
--- docker-compose.yml.orig	2020-02-17 10:57:19.204089312 -0500
+++ docker-compose.yml	2020-02-17 11:06:17.818574084 -0500
@@ -33,10 +33,10 @@
             - "3306:3306"
         volumes:
             - type: bind
-              source: /opt/usc/mysql/data
+              source: /srv/docker/redmine/mysql
               target: /var/lib/mysql
             - type: bind
-              source: /opt/usc/mysql/logs
+              source: /srv/docker/redmine/mysql-logs
               target: /var/log/mysql
     redmine:
         container_name: redmine
@@ -44,8 +44,8 @@
         environment:
             - DB_ADAPTER=postgresql
             - DB_ENCODING=utf8
-            - DB_HOST=<IP_ADDRESS>
-            - DB_PORT=5432
+            - DB_HOST=mysql
+            - DB_PORT=3306
             - DB_NAME=redmine
             - DB_USER=redmine
             - DB_PASS=password
@@ -58,5 +58,5 @@
             - "10083:10083"
         volumes:
             - type: bind
-              source: /opt/usc/redmine/data
+              source: /srv/docker/redmine/redmine/
               target: /home/redmine/data

I tried configuring the mysql container to create the database and user but i can't seem to connect using the redmine user.
     mysql:
         container_name: mysql
         image: mysql:8
         environment:
             - MYSQL_ROOT_PASSWORD=password
+            - MYSQL_DATABASE=redmine
+            - MYSQL_USER=redmine
+            - MYSQL_PASS=password
             - TZ=Asia/Shanghai

 $ docker-compose exec redmine mysqlshow -h mysql -p
Enter password:
+--------------------+
|     Databases      |
+--------------------+
| information_schema |
| mysql              |
| performance_schema |
| redmine            |
| sys                |
+--------------------+
$ docker-compose exec redmine mysqladmin -h mysql -u redmine -ppassword status
mysqladmin: [Warning] Using a password on the command line interface can be insecure.
mysqladmin: connect to server at 'mysql' failed
error: 'Access denied for user<EMAIL_ADDRESS>(using password: YES)'

Since you aren't using our standard mysql container and I'm struggling to get yours working, can you provide details on how to get it set up so I spend my time looking at your problem and not fighting with mysql?

Another problem is that you set your example db to postgres
-            - DB_ADAPTER=postgresql
+            - DB_ADAPTER=mysql2

I was able to reproduce your problem after switching back to the normal mysql container.  I then deleted the redmine data directory and tried to up the docker.  And I got stuck in a Gemfile Too many symlinks loop.
And looking in the data tmp directory, there is indeed a symlink loop.
 $ sudo rm -rf /srv/docker/redmine/redmine/*
 $ ls /srv/docker/redmine/redmine/
 $ docker-compose up
...
 $  $ ls -la /srv/docker/redmine/redmine/tmp/
total 8
drwxr-xr-x 1 cladmin jcormier 82 Feb 17 11:46 .
drwxr-xr-x 1 cladmin jcormier 72 Feb 17 11:46 ..
lrwxrwxrwx 1 cladmin jcormier 29 Feb 17 11:46 bundle -> /home/redmine/data/tmp/bundle
lrwxrwxrwx 1 cladmin jcormier 35 Feb 17 11:46 Gemfile.lock -> /home/redmine/data/tmp/Gemfile.lock
drwxr-xr-x 1 cladmin jcormier  0 Feb 17 11:46 plugin_assets
drwxr-xr-x 1 cladmin jcormier  0 Feb 17 11:46 thumbnails

Note this bug can be avoided by properly bring the container down after deleting the redmine directory. Although just deleting the tmp directory would have worked too.
 $ sudo rm -rf /srv/docker/redmine/redmine/*
 $ /usr/local/bin/docker-compose down
WARNING: Found orphan containers (rabbit, redis) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.
Removing issue412_redmine_run_b997a1070866 ... done
Removing redmine                           ... done
Removing mysql                             ... done
Removing network issue412_default
 $ /usr/local/bin/docker-compose up
...
redmine_1     | 2020-02-17 22:22:19,036 INFO success: unicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
redmine_1     | 2020-02-17 22:22:19,036 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
redmine_1     | 2020-02-17 22:22:19,036 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

My current version of your compose file.
docker-compose.zip
Although this can be reproduced using the example docker files.
 $ sudo rm -rf /srv/docker/redmine/redmine/*
 $ docker-compose up
...
redmine_1     | 2020-02-17 22:22:19,036 INFO success: unicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
redmine_1     | 2020-02-17 22:22:19,036 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
redmine_1     | 2020-02-17 22:22:19,036 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
^CGracefully stopping... (press Ctrl+C again to force)
Stopping docker-redmine_redmine_1    ... done
Stopping docker-redmine_postgresql_1 ... done

 $ sudo rm -rf /srv/docker/redmine/redmine/*
 $ docker-compose up
...
redmine_1     | [!] There was an error parsing `Gemfile`: Too many levels of symbolic links - /home/redmine/redmine/vendor/bundle/ruby/2.4.0/specifications. Bundler cannot continue.

Note that it is not expected for the data directory to be deleted and the container to not be deleted at the same time.  In general, this project was set up with the expectation that the container would be destroyed or brought "down" whenever it is stopped. Although as long as the data directory is left alone, you don't have to destroy the container.

At this point, I consider this to be a low priority bug.
To recover from this scenario, it should be sufficient to delete the tmp directory in the redmine data directory and bring down and up the docker.

Thanks for spending your time to figure this out.
Actually, there is a mysql container in the docker-compose file. But I do have a postgre db on another machine (<IP_ADDRESS>), which is different then redmine used.
Here is my infrastructure:

Machine A (<IP_ADDRESS>) - Redmine, MySql and other containers.
Machine B (<IP_ADDRESS>) - PostgreSQL

I see.  I hope the above fix works for you.
On Tue, Feb 18, 2020 at 10:38 PM hchungi<EMAIL_ADDRESS>wrote:

Thanks for spending your time to figure this out.
Actually, there is a mysql container in the docker-compose file. But I do
have a postgre db on another machine (<IP_ADDRESS>), which is different then
redmine used.
Here is my infrastructure:

Machine A (<IP_ADDRESS>) - Redmine, MySql and other containers.
Machine B (<IP_ADDRESS>) - PostgreSQL

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/sameersbn/docker-redmine/issues/412?email_source=notifications&email_token=ABK2RGIQ7WPJ6B5QA3WS4G3RDSSUPA5CNFSM4KUJJK6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMGHN4I#issuecomment-588019441,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABK2RGJFAV23W2MX7CGDDXTRDSSUPANCNFSM4KUJJK6A
.

--
Jonathan Cormier
Software Engineer
Voice:<PHONE_NUMBER> x222
http://www.CriticalLink.com http://www.criticallink.com/
6712 Brooklawn Parkway, Syracuse, NY 13211
https://www.linkedin.com/company/critical-link-llc
https://twitter.com/Critical_Link

Should I close this issue or leave it?

I see. I hope the above fix works for you.
…
On Tue, Feb 18, 2020 at 10:38 PM hchungi @.***> wrote: Thanks for spending your time to figure this out. Actually, there is a mysql container in the docker-compose file. But I do have a postgre db on another machine (<IP_ADDRESS>), which is different then redmine used. Here is my infrastructure: - Machine A (<IP_ADDRESS>) - Redmine, MySql and other containers. - Machine B (<IP_ADDRESS>) - PostgreSQL — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#412?email_source=notifications&email_token=ABK2RGIQ7WPJ6B5QA3WS4G3RDSSUPA5CNFSM4KUJJK6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMGHN4I#issuecomment-588019441>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABK2RGJFAV23W2MX7CGDDXTRDSSUPANCNFSM4KUJJK6A .
-- Jonathan Cormier Software Engineer Voice:<PHONE_NUMBER> x222 http://www.CriticalLink.com http://www.criticallink.com/ 6712 Brooklawn Parkway, Syracuse, NY 13211 https://www.linkedin.com/company/critical-link-llc https://twitter.com/Critical_Link

No, I think the bug does exist.  I just don't have the time to track it down and fix it.  And we have a workaround for now.

Have the same issue on windows 10.
After installation, it was OK, but after a reboot became broken. Any ideas about how to fix it without purging the database?

To recover from this scenario, it should be sufficient to delete the tmp directory in the redmine data directory and bring down and up the docker.

If you are consistently getting into this state after reboots.  Then we need to investigate further as this is not normal behavior.
I've not used this container on Windows but for my Linux service script, I call docker-compose down on shutdown and docker-compose up on startup.

Same problem, tmp directory removal doesn't help because  bundle -> /home/redmine/data/tmp/bundle symlink re-creates every start of container. Any ideas?

  WIth docker-compose this is done with
"docker-compose down"
On Sun, Aug 9, 2020 at 2:08 PM gmsalex<EMAIL_ADDRESS>wrote:

Same problem, tmp directory removal doesn't help because bundle ->
/home/redmine/data/tmp/bundle symlink re-creates every start of container.
Any ideas?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/sameersbn/docker-redmine/issues/412#issuecomment-671083433,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABK2RGMDL2OMFOPLQDI77CDR73QYDANCNFSM4KUJJK6A
.

--
Jonathan Cormier
Software Engineer
Voice:<PHONE_NUMBER> x222
http://www.CriticalLink.com http://www.criticallink.com/
6712 Brooklawn Parkway, Syracuse, NY 13211
https://www.linkedin.com/company/critical-link-llc
https://twitter.com/Critical_Link

If problem still persist, this solved for me docker system prune && docker system prune --volumes


Can not pull latest 1.7 (1.7.31) images from docker hub

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
docker pull traefik:1.7.31
What did you see instead?
docker pull traefik:1.7.31
> v1.7.31: Pulling from library/traefik
> no matching manifest for linux/amd64 in the manifest list entries

What version of Traefik are you using?
I want to use 1.7 with the latest update
What is your environment & configuration?
tried several machines, got the problem everywhere.
I can pull 1.7.30 and 2.5.3 without issues
If applicable, please paste the log output in DEBUG level
No response

Duplicate of #8490


Link to further explanation regarding the term "entity highlighting"

When reading an auto-generated manifest from top to bottom in order to understand their meaning, one will encounter the DisableEntityHighlighting property that is set to false as of today. The documentation page doesn't really clarify what's behind the term entity highlighting.
After doing a bit of googling, I suspect it has something to do with contextual add-ins and whether to highlight text fragments (entities?) that match the predefined regex, however I'm not too sure. If it indeed has something to do with contextual add-ins, then it shouldn't be part of the auto-generated manifest in my opinion, as the auto-generated manifest does not specify an ExtensionPoint with attribute DetectedEntity.

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

ID: 609bae71-6e55-153f-0ba4-1469272f9eca
Version Independent ID: 63b55e12-3d3e-41df-93d2-d3b81d33e440
Content: DisableEntityHighlighting element in the manifest file - Office Add-ins
Content Source: docs/reference/manifest/disableentityhighlighting.md
Product: non-product-specific
Technology: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

@adem Thanks for your query. Yes, that property is related to Outlook contextual add-ins. Can you share how the manifest was generated? That will help us to determine next steps.
Thanks.

@ElizabethSamuel-MSFT Hi, the manifest was generated via yo office with the options Office Add-in Task Pane project using React framework, TypeScript, and Outlook.
$ cat manifest.xml | grep Disable
<DisableEntityHighlighting>false</DisableEntityHighlighting>

Here are the versions:
$ npm list -g | grep "yo@"
└─┬<EMAIL_ADDRESS>$ npm list -g | grep "generator-office@"
├─┬<EMAIL_ADDRESS>
Thanks!

@adem Thanks for your response. We'll look into this.
@akrantz @TCourtneyOwen Can you take a look at this issue?
Thanks.

@adem @ElizabethSamuel-MSFT I will take a look at the Outlook manifest that yo-office uses

I think we can probably safely remove the DisableEntityHighlighting element from the Outlook manifest

@TCourtneyOwen Thanks for investigating. Can you update this issue once it is fixed?
Thanks.

@adem Can you confirm if this issue is now fixed for you?
Thanks.

@ElizabethSamuel-MSFT The element still seems to be part of the manifest - tested with<EMAIL_ADDRESS>However, I'm really not too bothered by it. It doesn't break anything and was just an initial point of confusion in our team. You can go ahead and close the issue.
Thanks!

@adem Thanks for letting us know. Closing now.


Set linear algbra library thread usage environment variables for all jobs

For any process that snakemake runs, avoid implicit parallelism beyond the requested number of threads for the respective rule. Default to 1 thread for implicit parallelism if the rule does not specify a number of threads.
When e.g. R is compiled with a parallelized linear algebra library, calling any linear algebra (like handling large matrices) can lead to implicit parallelism that will grab all cores/threads available on the host system. On large servers, this will lead to a degree of parallelization that does more harm than good, slowing everything down with cross-talk between threads.
For R parallel computing, there's a package that can control this variable within scripts: RhpcBLASctl. However, the same issue exists in other languages, e.g. for numpy in python or for Julia. Thus, I think setting all known environment variables for every created process to the number of threads that process has specified via its rule definition is the cleanest solution that is easiest to maintain and document.

It seems the error currently thrown is still related to yesterday's commits. But the failing tests also reveal, that the environment variables are added three times each, so the current way of adding them is somehow executed three times -- not sure what this is a side-effect of?

This took days to pinpoint...
Have a quick look, if that is how you meant your suggestions. Now, the variables are only added once, as intended, and should contain the right threads number applicable to the current process.
The failing test seems to be due to the new requirement to specify --cores...

Once #138 is accepted, you could add these lines to the part of excecutable where pipefail is set, that overrides the shell prefix when bash is the shell of choice. This might be a bit cleaner than adding them inside of the command context each time.


Include the various availability SLA percentages

This page currently only mentions 99.99% availability.
However, the various Azure SQL Database tiers fluctuate between 99.9% and 99.995%. Perhaps this can somehow be included in this page, as it's an important consideration for decision making around HA.
Source: https://azure.microsoft.com/en-ca/support/legal/sla/sql-database/v1_4/

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

ID: 15036ef6-9c0b-044e-d600-b9f90f039720
Version Independent ID: 6fe5cd14-a1ad-e183-a048-d72686abb969
Content: High availability - Azure SQL Database
Content Source: articles/sql-database/sql-database-high-availability.md
Service: sql-database
Sub-service: high-availability
GitHub Login: @Sashan
Microsoft Alias: sashan

@VitalyMCT We are checking this and will get back to you.

@VitalyMCT Thank you for the feedback.
This is being assigned to the content author to evaluate and update the documentation as appropriate.
@stevestein CXP cannot update the content on  https://azure.microsoft.com
Please route this feedback to the right team.

@VitalyMCT This Page defines the values and overview of the services that you are looking for.
Please refer this and let us know if you have any other question in this regard.

@NavtejSaini-MSFT, the issue is on the page for which the ticket is open:

The goal of the High Availability architecture in Azure SQL Database is to guarantee that your database is up and running 99.99% of time, without worrying about the impact of maintenance operations and outages.

That 99.99% figure is incorrect on its own. It's actually a range that depends on the specific tier and configuration. So the figure should either be removed, a range stated instead, a link be provided to the page with the correct figures, etc.

@VitalyMCT We have raised a request to add this information to the document. Once reviewed and approved by content author the changes will display.
Thanks for the feedback.


fix: esm import issues

When importing @knocklabs/react as esm, @knocklabs/react-core gets imported as common js where it should be esm. This updates the build to output .cjs files in the cjs build and .js in the esm build. Updates package.json to disambiguate the imports.

Fixed with #48


aiida-pseudo

Hello,
I have installed Quantum Mobile 21.06.04 on VirtualBox 6.1. I am working through: https://aiida-pseudo.readthedocs.io/en/latest/index.html
I get to here in the tutorial: https://aiida-pseudo.readthedocs.io/en/latest/howto.html
And cannot get past downloading aiida-pseudo install sssp:

I have checked the internet on the VirtualBox. It is working. I have downloaded new .tars of the pseudos from Materials Cloud and tried to manually install best I could gather from the aiida-pseudo howto doc above. I have even tried to point it to /usr/local/share, as I see them already installed on the installation Quantum Mobile 21.06.04.
I have read through the issues posted here, etc #59 and just general search online.
What am I not getting? Looks like this issue was solved some time ago, with no other posts, but I just can't figure it out. I have even tried to install an earlier version of Quantum Mobile, with no luck.
Any insight you can offer would be much appreciated.
Thank you.

Just an update to add that I have tried to install dojo and aiida-pseudo install pseudo-dojo worked.

What is the version of aiida-pseudo that is installed? You can figure it out with pip freeze | grep aiida-pseudo.

Hello,
It returns version 0.6.2.

How may I get the 'precision' SSSPs? (for now I am focued on using Quantum Mobile to make working with QE easier). I tried aiida-pseudo install -h to see if there was an identifier that I could for them but there was not. The default is 'efficiency'.

Try aiida-pseudo install sssp -p precision. Since it is an option of aiida-pseudo install sssp you need to call aiida-pseudo install sssp -h to see its specific options.

As well, it looks like aiida-pseudo install pseudo-dojo installed the psp8, although there are many other types and formats on materials cloud. Must I then download a tar of UPF format from Materials Cloud and try to install an 'archive' say aiida-pseudo install 'family' m  -f gztar?
For example: aiida-pseudo install family SSSP_1.1.2_PBE_precision.tar.gz SSSP/1.1/PBE/efficiency -f gztar

If you want them in another format, you can simply use the   -f, --pseudo-format [psp8|upf|psml|jthxml] option of aiida-pseudo install pseudo-dojo.

Where do these get installed? As I said, I already see a copy on in usr/lib/share. Am I duplicating things here or am I merely using aiida to point to those preinstalled pseudo libraries?

They are installed in AiiDA's storage (database and file repository). They are stored as UpfNodes (in the case of SSSP) in the provenance graph so you can use them as inputs for calculations such as PwCalculation. If families share pseudos they will automatically be deduplicated by aiida-pseudo based on the md5 checksum of their contents.

Thank you so much for all of your help! Have a great day.

Here is screenshot.

Note, when the help says -v, --version these are just the short and long form of the option, you only need to use one of them, e.g.:
aiida-pseudo install pseudo-dojo -v 1.1 -f upf

As for the error message, it is exactly as it says: 1.1 is not a supported version by aiida-pseudo, only 0.4 and 1.0 are. So you will have to select one of those.


Match Torch speed for sum reduction on M1

It looks the problem was with global/local dims being overloaded.

Changes made in tinygrad/:
------------------------------------------------------------
files                             insertions       deletions
------------------------------------------------------------
tinygrad/helpers.py                        1               0
tinygrad/lazy.py                          24               3
tinygrad/ops.py                            3               3
tinygrad/runtime/lib.py                    8               1
tinygrad/runtime/ops_cuda.py               5               2
tinygrad/runtime/ops_gpu.py                3               2
tinygrad/runtime/ops_metal.py              3               2
------------------------------------------------------------
total                                     47              13
------------------------------------------------------------
lines added in the tinygrad folder: 34

Can you post the speed results from test/test_speed_v_torch.py. Also a before/after of test/models/test_real_world.py

test_speed_v_torch:
add                                1x    1    0.44 ms (    0.00 GFLOPS     0.00 GB/s) in torch,    0.34 ms (    0.00 GFLOPS     0.00 GB/s) in tinygrad,    0.79x faster       0.00 MOPS     0.00 MB
add                             1024x 1024    0.56 ms (    1.88 GFLOPS    22.54 GB/s) in torch,    0.50 ms (    2.09 GFLOPS    25.11 GB/s) in tinygrad,    0.90x faster       1.05 MOPS    12.58 MB
add                             4096x 4096    1.73 ms (    9.72 GFLOPS   116.58 GB/s) in torch,    1.57 ms (   10.66 GFLOPS   127.87 GB/s) in tinygrad,    0.91x faster      16.78 MOPS   201.33 MB
add_constant                    4096x 4096    1.29 ms (   13.02 GFLOPS   104.20 GB/s) in torch,    1.18 ms (   14.23 GFLOPS   113.83 GB/s) in tinygrad,    0.92x faster      16.78 MOPS   134.22 MB
add_sq                          4096x 4096    3.26 ms (   15.46 GFLOPS    61.83 GB/s) in torch,    1.56 ms (   32.24 GFLOPS   128.97 GB/s) in tinygrad,    0.48x faster      50.33 MOPS   201.33 MB
array_packing                   2048x 2048    0.83 ms (    5.05 GFLOPS    40.36 GB/s) in torch,    0.62 ms (    6.75 GFLOPS    54.00 GB/s) in tinygrad,    0.75x faster       4.19 MOPS    33.55 MB
cat_0                            256x  256    0.46 ms (    0.29 GFLOPS     2.30 GB/s) in torch,    0.38 ms (    0.34 GFLOPS     2.74 GB/s) in tinygrad,    0.84x faster       0.13 MOPS     1.05 MB
cat_1                            256x  256    0.44 ms (    0.30 GFLOPS     2.38 GB/s) in torch,    0.40 ms (    0.33 GFLOPS     2.62 GB/s) in tinygrad,    0.91x faster       0.13 MOPS     1.05 MB
conv bs: 32 chans:  4 ->  32 k:3              0.75 ms (  100.64 GFLOPS     6.39 GB/s) in torch,    0.51 ms (  149.19 GFLOPS     9.47 GB/s) in tinygrad,    0.67x faster      75.50 MOPS     4.79 MB
conv bs: 32 chans: 16 ->  32 k:3              0.76 ms (  398.34 GFLOPS     8.68 GB/s) in torch,    0.87 ms (  345.53 GFLOPS     7.53 GB/s) in tinygrad,    1.15x slower     301.99 MOPS     6.58 MB
conv bs: 32 chans: 64 ->  32 k:3              1.30 ms (  929.11 GFLOPS    10.57 GB/s) in torch,    0.93 ms ( 1305.84 GFLOPS    14.85 GB/s) in tinygrad,    0.71x faster    1207.96 MOPS    13.74 MB
double_permute (64, 64, 64, 64)               2.92 ms (    5.75 GFLOPS    46.00 GB/s) in torch,    2.47 ms (    6.79 GFLOPS    54.35 GB/s) in tinygrad,    0.85x faster      16.78 MOPS   134.22 MB
exp                             2048x 2048    0.71 ms (   11.87 GFLOPS    47.46 GB/s) in torch,    0.63 ms (   13.29 GFLOPS    53.15 GB/s) in tinygrad,    0.89x faster       8.39 MOPS    33.55 MB
gemm                            1024x 1024    1.05 ms ( 2043.92 GFLOPS    11.98 GB/s) in torch,    0.94 ms ( 2273.77 GFLOPS    13.32 GB/s) in tinygrad,    0.90x faster    2147.48 MOPS    12.58 MB
gemm                             256x  256    0.46 ms (   72.27 GFLOPS     1.69 GB/s) in torch,    0.43 ms (   77.60 GFLOPS     1.82 GB/s) in tinygrad,    0.93x faster      33.55 MOPS     0.79 MB
gemm_unrolled                    512x  512    0.82 ms (  329.12 GFLOPS     3.86 GB/s) in torch,    0.74 ms (  364.31 GFLOPS     4.27 GB/s) in tinygrad,    0.90x faster     268.44 MOPS     3.15 MB
gemm_unrolled_permute_l          512x  512    0.59 ms (  453.12 GFLOPS     5.31 GB/s) in torch,    0.66 ms (  404.47 GFLOPS     4.74 GB/s) in tinygrad,    1.12x slower     268.44 MOPS     3.15 MB
gemm_unrolled_permute_lr         512x  512    0.55 ms (  488.14 GFLOPS     5.72 GB/s) in torch,    0.63 ms (  427.76 GFLOPS     5.01 GB/s) in tinygrad,    1.14x slower     268.44 MOPS     3.15 MB
gemm_unrolled_permute_r          512x  512    0.75 ms (  358.97 GFLOPS     4.21 GB/s) in torch,    0.45 ms (  596.30 GFLOPS     6.99 GB/s) in tinygrad,    0.60x faster     268.44 MOPS     3.15 MB
max                             4096x 4096    0.98 ms (   17.11 GFLOPS    68.72 GB/s) in torch,    0.88 ms (   19.14 GFLOPS    76.87 GB/s) in tinygrad,    0.89x faster      16.84 MOPS    67.63 MB
mul_sum                         4096x 4096    2.16 ms (   15.56 GFLOPS    62.37 GB/s) in torch,    1.26 ms (   26.78 GFLOPS   107.32 GB/s) in tinygrad,    0.58x faster      33.62 MOPS   134.74 MB
neg                             4096x 4096    1.29 ms (   13.04 GFLOPS   104.30 GB/s) in torch,    1.21 ms (   13.88 GFLOPS   111.05 GB/s) in tinygrad,    0.94x faster      16.78 MOPS   134.22 MB
conv bs:  1 chans: 12 ->  32 k:3              0.55 ms (  103.44 GFLOPS     2.66 GB/s) in torch,    0.87 ms (   65.35 GFLOPS     1.68 GB/s) in tinygrad,    1.58x slower      56.62 MOPS     1.46 MB
partial_sum                     4096x 4096    1.00 ms (   16.82 GFLOPS    67.54 GB/s) in torch,    0.94 ms (   17.96 GFLOPS    72.10 GB/s) in tinygrad,    0.94x faster      16.84 MOPS    67.63 MB
permute                         1024x 1024    0.47 ms (    2.25 GFLOPS    18.00 GB/s) in torch,    0.46 ms (    2.27 GFLOPS    18.18 GB/s) in tinygrad,    0.99x faster       1.05 MOPS     8.39 MB
permute                         4096x 4096    4.46 ms (    3.76 GFLOPS    30.08 GB/s) in torch,    1.20 ms (   13.93 GFLOPS   111.44 GB/s) in tinygrad,    0.27x faster      16.78 MOPS   134.22 MB
pow                             2048x 2048    0.88 ms (  261.56 GFLOPS   114.14 GB/s) in torch,    1.12 ms (  206.73 GFLOPS    90.21 GB/s) in tinygrad,    1.27x slower     230.69 MOPS   100.66 MB
relu                            4096x 4096    1.41 ms (   11.92 GFLOPS    95.38 GB/s) in torch,    1.19 ms (   14.13 GFLOPS   113.01 GB/s) in tinygrad,    0.84x faster      16.78 MOPS   134.22 MB
sub                             4096x 4096    1.68 ms (   10.01 GFLOPS   120.17 GB/s) in torch,    1.57 ms (   10.69 GFLOPS   128.30 GB/s) in tinygrad,    0.94x faster      16.78 MOPS   201.33 MB
sum                             2048x 2048    0.67 ms (    6.25 GFLOPS    25.10 GB/s) in torch,    0.58 ms (    7.30 GFLOPS    29.31 GB/s) in tinygrad,    0.86x faster       4.21 MOPS    16.91 MB
sum                             4096x 4096    0.99 ms (   16.93 GFLOPS    68.00 GB/s) in torch,    0.88 ms (   19.05 GFLOPS    76.51 GB/s) in tinygrad,    0.89x faster      16.84 MOPS    67.63 MB

As for test_real_world.py my m1pro might run out of memory for llama and sd, maybe better to retest them.
New:
METAL=1 python3 models/test_real_world.py
test_llama: used 13.49 GB and 486 kernels in 1601.10 ms
.test_sd: used 14.06 GB and 1016 kernels in 2290.58 ms
.train_cifar: used 7.85 GB and 274 kernels in 1812.34 ms

Old:
METAL=1 python3 models/test_real_world.py
test_llama: used 13.49 GB and 486 kernels in 1633.04 ms
.test_sd: used 14.05 GB and 924 kernels in 2424.88 ms
.train_cifar: used 7.55 GB and 236 kernels in 1841.71 ms

As for test_real_world.py my m1pro might run out of memory for llama and sd, maybe better to retest them.
If you run it with CI=1 it will test the tiny llama

As for test_real_world.py my m1pro might run out of memory for llama and sd, maybe better to retest them.

If you run it with CI=1 it will test the tiny llama

Thanks. But for llama count of kernels is the same, so the speed should be the same. Llama has reductions with global dims like (242, 64), so it's better not to apply the optimizations, since it just adds more to global/local dims (this amount of threads simply overload gpus, for some gpus performance is unchanged, for some it is worse).
I tested a smaller version of sd (with Tensor(1,4,64,64)->Tensor(1,4,48,48). Overall it's a bit better than original verison:
OLD
test_llama: used 13.49 GB and 486 kernels in 1563.78 ms
.test_sd: used 7.30 GB and 924 kernels in 499.63 ms
.train_cifar: used 7.55 GB and 236 kernels in 1830.16 ms

test_llama: used 13.49 GB and 486 kernels in 1617.32 ms
.test_sd: used 7.30 GB and 924 kernels in 501.72 ms
.train_cifar: used 7.55 GB and 236 kernels in 1831.49 ms

test_llama: used 13.49 GB and 486 kernels in 1595.49 ms
.test_sd: used 7.30 GB and 924 kernels in 503.38 ms
.train_cifar: used 7.55 GB and 236 kernels in 1826.27 ms

NEW
test_llama: used 13.49 GB and 486 kernels in 1545.04 ms
.test_sd: used 7.30 GB and 928 kernels in 497.91 ms
.train_cifar: used 7.85 GB and 274 kernels in 1786.99 ms

test_llama: used 13.49 GB and 486 kernels in 1537.53 ms
.test_sd: used 7.30 GB and 928 kernels in 498.68 ms
.train_cifar: used 7.85 GB and 274 kernels in 1812.01 ms

test_llama: used 13.49 GB and 486 kernels in 1599.92 ms
.test_sd: used 7.30 GB and 928 kernels in 496.24 ms
.train_cifar: used 7.85 GB and 274 kernels in 1781.60 ms

.train_cifar: used 7.85 GB and 274 kernels in 1781.60 ms

test_real_world should have reported a failure if the generated kernels is greater than 236, not sure why it is passing in CI

Just did a quick test on cifar using CL backend on 3090, working fine.

.train_cifar: used 7.85 GB and 274 kernels in 1781.60 ms

The kernel counts were introduced due to when #1187 was first merged, it halved computation speed for OpenCL backend on nvidia and amd GPUs. I assume that count should be device agnostic unless you change the way kernels are generated.

It should have the same speed on CUDA/CL as #1187. The difference is that this MR doesn't generate more threads than gpu can handle. If a gpu is loaded enough with threads, no need to use this 2 kernels approach. But since amount of parallel threads depends on the size of gpu (it's about 1024*sm_count), this optimisation is also depends on the gpu it's running.

Are you very confident in this? Last time we merged this, we had to revert.

No, no. Found what's wrong with SD. Need to fix it

I think this is gonna need a lot more testing before we can merge this.

Tested this PR on some models from examples/. On what I have tested (see full results for details) this PR is never worse. SD is now even a bit faster after #1429 + this PR.

Full results
stable_diffusion.py NEW: avg:  1075.24 GFLOPS    20.06 GB/s           total:  1193 kernels  4221.37 GOPS    78.76 GB  3925.99 ms
stable_diffusion.py OLD: avg:  1085.77 GFLOPS    18.94 GB/s           total:  1076 kernels  4372.68 GOPS    76.29 GB  4027.27 ms

train_resnet.py NEW: 8.04it/s
train_resnet.py OLD: 7.71it/s

efficientnet.py: same
hlb_cifar10.py: same
train_efficientnet.py: same
serious_mnist.py: same
transformer.py: same

test_real_world.py:
  OLD:
  test_sd: used 7.30 GB and 924 kernels in 499.92 ms
  train_cifar (smaller 48x48): used 7.55 GB and 236 kernels in 1834.85 ms
  NEW:
  test_sd: used 7.30 GB and 932 kernels in 495.85 ms
  train_cifar (smaller 48x48): used 7.85 GB and 274 kernels in 1807.73 ms
  test_llama: same

Hoping you got it with that bug fix. Will merge, if there's no revert in a day or two, $400 bounty is yours<EMAIL_ADDRESS>to claim


Add extra_sans config option

Ported from https://github.com/canonical/kafka-operator/pull/125

Just noticed that this PR fell through the cracks. There were no reviewers assigned and that's why I never noticed.
I have assigned myself and @marcoppenheimer now

@zmraul please update the PR title with the ticket and feel free to merge this!


Update links to Presto documentation

/lgtm
/approve

/ok-to-test

You'll be glad to know we are correctly using the new presto github for our docker images (forked in this org), though we're still lagging behind on versions.

Docs changes don't need these
/override ci/prow/e2e-aws-metering
/override ci/prow/integration-aws-metering


Please give an example on how to "filter"

Could you give an example on how to apply filter
In SublimeLinter.sublime-settings
I tried
"cpplint": {
"filter": "-build/c++11"
}
both in and out of "default"
I also tried
"linters": {
"cpplint": {
"filter": "-build/c++11"
}
}
both in and out of "default"
non of them worked. It still show error when I #include <chrono>

It works when I change the settings at "user" instead of "default"


Error when adding nuget in asp.net mvc

When adding nuget to asp.net mvc (4.5.2) I have error on web pages. Nothing clear error message. I tried use class library with nuget and add to project but still have error.

4.5.2 is the .NET framework version?
I was not able to reproducce the issue, however I tried .net fw 4.6.1, since it is the oldest one what I was able to create in my VS.

Yes .net 4.5.2
I have installed version seems 3.1002. And solved issue. But sometimes I can not connect proxy so use fiddlerCore

I think you should update your target framework is possible, since .net 4.5.2-4.6.1 is not supported by MS since more than 8 months ago.


Fix building associations

With the addition of ROM::Factory::UnknownFactoryAttributes, it has become apparent that attributes passed to structs are also passed into their many-to-one associations. This PR addresses the issue and tests that it does not cause errors for one-to-one, one-to-many, or many-to-one associations.
Here's an example:
factories.define(:task) do |f|
  f.title { 'Foo' }
  f.association(:user)
end

factories.define(:user) do |f|
  f.timestamps
end

Currently, attributes provided to the task struct are being passed into the user association:
factories.structs[:task, title: 'Bar']  #=> ROM::Factory::UnknownFactoryAttributes

This PR makes it possible to build such structs without exceptions:
factories.structs[:task, title: 'Bar'].title  #=> "Bar"

@ianks I just released 0.9.1, thanks for helping with this!