Why would the CSS rendering order differ between local and production builds?

Hello, my ui-components using styled components have begun to differ between local and production builds. See the screenshots below, given the same browser dimensions etc...
Notice how the css style ordering is different between local and production. This is not desired and causing components to break on production. What would cause this?
What would cause styled-components to output the CSS style ordering differently for a particular component? This is not happening for all components. After spending the day trying to debug this, I'm hoping for advice to point me in the right direction.
Thank you
Locally:

Production:

Environment
System:

OS: macOS High Sierra 10.13.4
CPU: x64 Intel(R) Core(TM) i5-6360U CPU @ 2.00GHz
Memory: 191.13 MB / 8.00 GB
Shell: 3.2.57 - /bin/bash

Binaries:

Node: 8.1.4 - ~/.nvm/versions/node/v8.1.4/bin/node
Yarn: yarn install v0.24.4
[1/4] Resolving packages...
success Already up-to-date.
Done in 1.13s. - /usr/local/bin/yarn
npm: 5.0.3 - ~/.nvm/versions/node/v8.1.4/bin/npm

npmPackages:

styled-components: 3.1.6 => 3.1.6

Expected Behavior
Components output renders the same locally and on production
Actual Behavior
Local and Production component rendering differs. This is not happening for all components, it's random.

Are you using SSR by any chance? Try setting up the babel-plugin maybe, if so. Can you maybe try to identify the affected component and extract it into a CodeSandbox or code snippet? Do you maybe have some custom CSS here as well? Maybe it's just the order of your external CSS and the SC CSS?

We are not using ssr. Sadly the effected component(s) seem to be occurring randomly every time we deploy.

It might be something to do with module concatenation. You can turn it off
via webpack config
On Thu, Jun 14, 2018 at 9:35 AM Brett<EMAIL_ADDRESS>wrote:

We are not using ssr. Sadly the effected component(s) seem to be occurring
randomly every time we deploy.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/styled-components/styled-components/issues/1809#issuecomment-397298156,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAiy1kGWp5jQDaAvKFVhtQvEhPSY45o8ks5t8margaJpZM4UnSu1
.

fyi, we're still working to debug the issue. So far we've learned the issue started occurring when we moved from npm to yarn.

Oh interesting. Could be an issue with library duplication.
Does yarn list styled-components show more than one installed version? You can also ensure deduplication by adding a webpack alias.

library duplication, 2 different versions of styled-components via yarn dependency handling  ended up being the issue... Thanks for your help


Supporting JUCE-level track info

Adding support for the track-info extension. The track info extension allows the host to provide more than what JUCE's TrackProperties supports, but for now I'm just passing through the JUCE-level information.
https://github.com/free-audio/clap-juce-extensions/assets/13724188/33c98906-063b-43cb-995f-f0fa9c3e6252

Looks great!


quic client fuzzer hang #2

After all the fixes for the various fuzzing issues including the tentative fix in #22425 - I'm seeing another hang in the quic client fuzzer (i.e. different to #22412).
Corpora file attached.
hang2.gz

Fixed by #22436


Please 'pub extern' to redis and r2d2

This crate depends on redis and r2d2 cates but these are not public so we can't use that.
If there are some r2d2 protocol crates, those creates are depend on different version of r2d2 maybe.
In that case, we can't extern crate r2d2, we sould use 'extern crate r2d2_redis::redis`.

Could you create a PR?


Can't see the containers in storage explorer

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Storage Explorer Version
1.27.0
Regression From
No response
Architecture
x64
Storage Explorer Build Number
20221201.1
Platform
Windows
OS Version
Windows 10
Bug Description
Unable to retrieve child resources.
Details:
{
"name": "FetchError",
"message": "request to https://ziplinefiles.blob.core.windows.net/?comp=list&include=metadata failed, reason: unable to get local issuer certificate",
"stack": "FetchError: request to https://ziplinefiles.blob.core.windows.net/?comp=list&include=metadata failed, reason: unable to get local issuer certificate\n    at ClientRequest. (C:\Program Files (x86)\Microsoft Azure Storage Explorer\resources\app\node_modules\se-blob-extension\dist\src\index.js:2:2440800)\n    at ClientRequest.emit (node:events:527:28)\n    at TLSSocket.socketErrorListener (node:_http_client:454:9)\n    at TLSSocket.emit (node:events:527:28)\n    at emitErrorNT (node:internal/streams/destroy:157:8)\n    at emitErrorCloseNT (node:internal/streams/destroy:122:3)\n    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)",
"type": "system",
"errno": "UNABLE_TO_GET_ISSUER_CERT_LOCALLY",
"code": "UNABLE_TO_GET_ISSUER_CERT_LOCALLY"
}
Steps to Reproduce
Unable to retrieve child resources.
Details:
{
"name": "FetchError",
"message": "request to https://ziplinefiles.blob.core.windows.net/?comp=list&include=metadata failed, reason: unable to get local issuer certificate",
"stack": "FetchError: request to https://ziplinefiles.blob.core.windows.net/?comp=list&include=metadata failed, reason: unable to get local issuer certificate\n    at ClientRequest. (C:\Program Files (x86)\Microsoft Azure Storage Explorer\resources\app\node_modules\se-blob-extension\dist\src\index.js:2:2440800)\n    at ClientRequest.emit (node:events:527:28)\n    at TLSSocket.socketErrorListener (node:_http_client:454:9)\n    at TLSSocket.emit (node:events:527:28)\n    at emitErrorNT (node:internal/streams/destroy:157:8)\n    at emitErrorCloseNT (node:internal/streams/destroy:122:3)\n    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)",
"type": "system",
"errno": "UNABLE_TO_GET_ISSUER_CERT_LOCALLY",
"code": "UNABLE_TO_GET_ISSUER_CERT_LOCALLY"
}
Actual Experience
Cant connect to containers
Expected Experience
All containers should be viewable. I am not able to see any containers.
Additional Context
Unable to retrieve child resources.
Details:
{
"name": "FetchError",
"message": "request to https://ziplinefiles.blob.core.windows.net/?comp=list&include=metadata failed, reason: unable to get local issuer certificate",
"stack": "FetchError: request to https://ziplinefiles.blob.core.windows.net/?comp=list&include=metadata failed, reason: unable to get local issuer certificate\n    at ClientRequest. (C:\Program Files (x86)\Microsoft Azure Storage Explorer\resources\app\node_modules\se-blob-extension\dist\src\index.js:2:2440800)\n    at ClientRequest.emit (node:events:527:28)\n    at TLSSocket.socketErrorListener (node:_http_client:454:9)\n    at TLSSocket.emit (node:events:527:28)\n    at emitErrorNT (node:internal/streams/destroy:157:8)\n    at emitErrorCloseNT (node:internal/streams/destroy:122:3)\n    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)",
"type": "system",
"errno": "UNABLE_TO_GET_ISSUER_CERT_LOCALLY",
"code": ### "UNABLE_TO_GET_ISSUER_CERT_LOCALLY"
}

Can you try using System Proxy? You can read more about it here: https://learn.microsoft.com/en-us/azure/storage/common/storage-explorer-network#use-system-proxy-preview

Yes, it worked.
Thanks,
Chandra Rana
From: Matthew Rayermann @.>
Sent: Monday, January 30, 2023 12:48 PM
To: microsoft/AzureStorageExplorer @.>
Cc: Chandra Rana @.>; Author @.>
Subject: [EXTERNAL] Re: [microsoft/AzureStorageExplorer] Can't see the containers in storage explorer (Issue #6463)
Can you try using System Proxy? You can read more about it here: https://learn.microsoft.com/en-us/azure/storage/common/storage-explorer-network#use-system-proxy-previewhttps://learn.microsoft.com/en-us/azure/storage/common/storage-explorer-network#use-system-proxy-preview
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/AzureStorageExplorer/issues/6463#issuecomment-1409055495, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AX5FPYDCLZPNT3VABCC2HHDWU75FTANCNFSM6AAAAAAUHU6J6U.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>


Different style for finish

Hi, I have been through the whole documentation but i am unable to find the solution for my usecase:
I want to start with a style:
let bar = indicatif::ProgressBar::new(10)
    .with_message("Converting")
    .with_style(indicatif::ProgressStyle::default_bar()
        .template("{msg:>15.cyan} {bar:40.cyan} {prefix} {percent:>3}%  [{elapsed}]"));

But I want to finish it with a different template without a {bar}. I tried using finish_using_style but couldn't figure out how to make it work.
Thanks

I think finish_using_style() is specifically about the ProgressFinish stored in the ProgressStyle. I don't think there is a way to do what you want today. If you want to contribute something, feel free to submit a PR, or maybe start with a brief description of the design you have in mind to avoid work that turns out to not fit in with my goals.

Yes i would love to contribute. I will try to briefly explain my proposal:
Add a method called with_finish_style to work something like this:
let bar = indicatif::ProgressBar::new(10)
    .with_message("Converting")
    .with_style(indicatif::ProgressStyle::default_bar()
        .template("{msg:>15.cyan} {bar:40.cyan} {prefix} {percent:>3}%  [{elapsed}]"));
    .with_finish_style(indicatif::ProgressStyle::default_bar()
        .template("{msg:>15.cyan} {prefix} {percent:>3}%  [{elapsed}]"));

In the above example, we have two styles: one before finish and one after finish, this allows me for example to remove the bar just after finish, but keep other information as is, I can submit a PR, but i just require some help getting started.

What kind of help would you need? I think you'll find the code base reasonably straightforward to navigate.


Update akka-http to 10.1.12

Updates com.typesafe.akka:akka-http from 10.1.11 to 10.1.12.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.typesafe.akka", artifactId = "akka-http" } ]

labels: test-library-update, semver-patch

Coverage remained the same at 0.0% when pulling 0ea96b33359853bb611b362007f08f1c42abc304 on scala-steward:update/akka-http-10.1.12 into bd2fbba766f77c489ef650dfa84427230926a656 on andyglow:develop.


[ORA-1166] Migrate float64 type to CockroachDB APD Dec type

float64 are handled differently on different CPU architecture so we cannot use it for consensus when we expect different types of CPU machines to come to consensus e.g. x86 and ARM
Fortunately underlying cockroachDB that cosmos-sdk already relies on provides a complex arbitrary-precision decimal package for go called Dec.
This PR migrates us to use Dec in place of float64.

We can send the APD Decs through the CLI:
Help text
➜  allora-chain git:(APD-Dec) ✗ allorad tx emissions test-dec-message --help
test sending a dec message via the cli

Usage:
  allorad tx emissions test-dec-message [value] [flags]

Sending the transaction
➜  allora-chain git:(APD-Dec) ✗ allorad tx emissions test-dec-message "allo17e5ge56zvzcrw0pehv0y7hyuakwwv7ypyxk7j9" "0.
12345"
auth_info:
  fee:
    amount: []
    gas_limit: "200000"
    granter: ""
    payer: ""
  signer_infos: []
  tip: null
body:
  extension_options: []
  memo: ""
  messages:
  - '@type': /emissions.v1.DecMessage
    sender: allo17e5ge56zvzcrw0pehv0y7hyuakwwv7ypyxk7j9
    value: "0.12345"
  non_critical_extension_options: []
  timeout_height: "0"
signatures: []
confirm transaction before signing and broadcasting [y/N]: y
code: 0
codespace: ""
data: ""
events: []
gas_used: "0"
gas_wanted: "0"
height: "0"
info: ""
logs: []
raw_log: ""
timestamp: ""
tx: null
txhash: 8C66276C1DED0DA8BF9C595EC9982D4EF56BAA6B574BACCD84329D932E2EB889

In another tab where the CLI is running we have a simple printf statement in the msg_handler.go:
11:43AM INF committed state block_app_hash=A7D971D27E177737E28E8AB87B631E6DD45F0751120B4530DB19739C3BF1F954 height=38 module=state

 ---------------- Emissions BeginBlock -------------------
TestDecMessage
0.12345

 ---------------- Emissions EndBlock -------------------

From now on, we should use this Dec instead of float64, right?

From now on, we should use this Dec instead of float64, right?

yes

this is as good as this is going to get for now


Reordering of Discrete Math

Discrete Math requires Single Variable Calculus as a prerequisite.
I'd suggest the Calculus courses should come before Discrete Math in the curriculum.
Calculus > Discrete Math > Algorithms

I agree. The Discrete Mathematics course touches on some math that many people using this, those who want to self teach and are not in any way professional on the subject, have never used, me included. The Calculus course, as well as some Khan Academy cleared that up, but following the exact structure of the courses becomes confusing.

I was thinking along the lines of Calculus, Discrete Math, then Algorithms in order.

+1

This was discussed here.


Improve clarity of errors when writing to pin opened as input

The cdev and sysfs interfaces will throw errors (1: Operation not permitted or 22: Invalid argument for me) when attempting to write to a pin opened as an input. This PR improves clarity by catching attempts to write to a pin opened for input and raises a GPIOError with a clearer message. Similar checks also added to the poll and read_event methods.
Closes #43

Thanks, merged in 69bd36e. In addition to a few minor modifications, I decided to drop the checks in the sysfs implementation. I think it's a bit too much to open and read the direction file on every call to write() or poll() to check that it's the right direction. Ideally, that state would be cached, like it is in the character device implementation. But the sysfs implementation has avoided caching to be robust to external modifications (e.g. if another process modifies the GPIO in /sys).

I decided to drop the checks in the sysfs implementation. I think it's a bit too much to open and read the direction file on every call

Yeah that's quite the performance hit if you are doing a lot of writes in a short time, I did not see that the sysfs class was doing that.


chronos marathon addon

converts chronos to an addon that runs in marathon
Fixes #792
Fixes #1155
Obsoletes #1168

[ ] Installs cleanly on a fresh build of most recent master branch
[ ] Upgrades cleanly from the most recent release
[x] Updates documentation relevant to the changes
[ ] Rebases cleanly onto the latest master

How will people upgrade from Mantl 1.0?

good question. If you already have a 1.0 cluster with chronos installed, I don't know if there is really a great reason to switch. But, I can add a little bit to the documentation that explains how to turn off the existing chronos on control nodes and switch to the version running in marathon

ah but since we are using the same role name, it is likely that the addon will be installed anyway if someone has chronos in their mantl.yml and reprovisions. I'll have to add something to check for that.

@ryane We could move it to addons/roles/chronos (with the changes in #1224), and keep the old role (with a deprecation warning) for a release or two.
Other than that, this is looking awesome! I got a successful install with no Chronos dashboard in MantlUI for Chronos, and the UI appears and works after the Marathon deployment finishes.

Deleting the Marathon task also works as described.

@siddharthist I added a check to make sure it already isn't installed in the playbook and I added some docs. I didn't resurrect the old role b/c I wasn't sure how it would behave if we had a chronos role in both roles and addons/roles. we can move this to addons/roles in #1224 since that branch needs rebased anyway and it already includes the change to ansible.cfg

@ryane Sweet, I'll deploy this again later today to make sure it's working as expected with the new changes.

Successfully skips when Chronos is installed on a 1.0 cluster! Unfortunately, it doesn't reinstall Chronos, because mantl-api is the version that doesn't watch the Consul K/V to install packages.

If you just run sample.yml first, installing Chronos works after that. If we add that to the docs, I'll merge this.

This has now been tested on its own, as well as with a sucessful upgrade from 1.0. Merging

I didn't use fail b/c I was thinking of the scenario where you have a 1.0.3 cluster with chronos in your mantl.yml. Then, you pull 1.1, and re-provision with the same mantl.yml. I didn't want the provisioning to fail at that point.

When you upgrade from a 1.0.x cluster to 1.1, and you re-run your sample|mantl playbook, it should actually upgrade mantl-api.


New operator: moving_product

New EventSet.moving_product() operator.
See EventSet.moving_sum() for reference. Note that this issue will require C++ code.
See https://github.com/google/temporian/blob/main/CONTRIBUTING.md#developing-a-new-operator for guidance.
Questions or requests for additional guidance from possible contributors more than welcome!

Will be working on this as a part of #350

Hey @akshatvishu!
This involves modifying quite a bit of cpp code:

Creating a new Accumulator implementation (see MovingSumAccumulator in temporian/implementation/numpy_cc/operators/window.cc)
Creating new accumulate overloads for moving_product in the same file
Registering and creating bindings for the new accumulate cpp functions (see bottom of that same file)

Plus, there's some specifics to moving product that make it not as straightforward to implement as  moving sum, for example. We'd rather have the core dev team implement this (ETA: this/next week tops) and then have you do cumprod alone - unless you are perfectly comfortable with all of the above, in which case I can give more detail as to what these specifics are and let you take a shot at it :)
Let me know!

Sounds great 👍🏼 and great questions.

Zero or extreme values: zeros will result in the accumulator's result being 0. NaNs should be ignored (i.e., if we have a [2, NaN, 3] window, the result should still be 6, not NaN).
Accumulate overloads: you don't need to modify these, you'll just need to add the REGISTER_CC_FUNC and ADD_PY_DEF calls. See simple_moving_average's for reference.

Some extra notes:

You'll see that most accumulators work by adding/removing the new/old values from the window directly onto the accumulation result. This won't be possible here, since 0 would erase the accumulation, and precision loss would be high. Instead, we want the accumulator to store the left/right indexes, and compute the product on the whole window in Result().
No need to raise an error message on overflow (numpy doesn't in cumprod)
We'll only make this available for float types for now. This restriction should be in the C defs, the operator's accepted types, and the function's docstring.
Please do moving_product only for this task, leave cumprod for a follow up.

Issue and discord always open 💪🏼


Kubeflow installation on EKS fails - timed out while istio installation

Describe the bug
While installing using Helm charts from docker ubuntu machine, installation over AWS EKS fails with below error. It fails while setting up istio-system namespace
running command: kubectl wait --for=condition=ready pod -l 'app in (istio-ingressgateway, istiod)' --timeout=240s -n istio-system
timed out waiting for the condition on pods/istio-ingressgateway-67d6475549-7mjvj
timed out waiting for the condition on pods/istiod-c8965d9c5-m9nvm
Waiting for istio-1-14 pods to be ready ...
running command: kubectl wait --for=condition=ready pod -l 'app in (istio-ingressgateway, istiod)' --timeout=240s -n istio-system
timed out waiting for the condition on pods/istio-ingressgateway-67d6475549-7mjvj
timed out waiting for the condition on pods/istiod-c8965d9c5-m9nvm
Traceback (most recent call last):
File "utils/kubeflow_installation.py", line 278, in
install_kubeflow(
File "utils/kubeflow_installation.py", line 79, in install_kubeflow
install_component(
File "utils/kubeflow_installation.py", line 143, in install_component
validate_component_installation(installation_config, component_name)
File "/usr/local/lib/python3.8/dist-packages/retrying.py", line 49, in wrapped_f
return Retrying(*dargs, **dkw).call(f, *args, **kw)
File "/usr/local/lib/python3.8/dist-packages/retrying.py", line 212, in call
raise attempt.get()
File "/usr/local/lib/python3.8/dist-packages/retrying.py", line 247, in get
six.reraise(self.value[0], self.value[1], self.value[2])
File "/usr/local/lib/python3.8/dist-packages/six.py", line 719, in reraise
raise value
File "/usr/local/lib/python3.8/dist-packages/retrying.py", line 200, in call
attempt = Attempt(fn(*args, **kwargs), attempt_number, False)
File "utils/kubeflow_installation.py", line 155, in validate_component_installation
kubectl_wait_pods(value, namespace, key)
File "/kubeflow-manifests/tests/e2e/utils/utils.py", line 266, in kubectl_wait_pods
assert os.system(cmd) == 0
AssertionError
Makefile:102: recipe for target 'deploy-kubeflow' failed
Steps To Reproduce
Vanilla installation using manifests. Execute this command after prerequisites are completed
make delete-kubeflow INSTALLATION_OPTION=helm DEPLOYMENT_OPTION=vanilla
Expected behavior
A clear and concise description of what you expected to happen.
Environment

Kubernetes version
Using EKS (yes/no), if so version? Yes, 1.24
Kubeflow version - v1.6.1-aws-b1.0.1
AWS build number
AWS service targeted (S3, RDS, etc.)
None
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
while checking pod it shows CrashLoopBackOff
State:          Waiting
Reason:       CrashLoopBackOff
Last State:     Terminated
Reason:       Error
Exit Code:    1

What do the pod logs for istio say? Can you share the output of kubectl get pods -A

to add - we're using Graviton r6g processor (linux arm64 V8)

based on https://github.com/istio/istio/issues/22463, this looks like an intermittent issue and deleting the istiod pod might fix the issue.

Closing due to inactivity. Feel free to reopen if the issue is not resolved

@keenborder786 Please open a new issue and use the bug template to provide environment details amd steps to reproduce

I have the same problem. The oidc-authservice pod is not running. When I open the log, the following is displayed
| exec ./oidc-authservice: exec format error
It is said that this is because the architecture is different, but what should I do?


formData doesn't get updated  when I select an item from combobox

Describe the bug and the expected behavior
In my Remix application, I am passing a FieldMetadata to a Combobox.  When I select an item in the combobox, conform formData doesn't get updated with that value. It always remains null
With input type hidden or text, it also doesn't allow me to write string as value.
Check here,
https://stackblitz.com/edit/conform-combobox-issue?file=app%2Froutes%2Fresources.location.tsx%3AL133
Conform version
v1.1.5
Steps to Reproduce the Bug or Issue
Sandbox: https://stackblitz.com/edit/conform-combobox-issue?file=app%2Froutes%2F_index.tsx

I found a solution to this
instead of passing the value with getInputProps I need to pass it as an input element value
Previously, I was doing this
<input {...getInputProps(field, { type: 'hidden', value: cb.selectedItem?.id ?? ""  })}  />

What I had to do was
<input {...getInputProps(field, { type: 'hidden' })} value={cb.selectedItem?.id} />


Fix Find in Files Not Working Properly

When using the "Find in Files" option to search in non-script files (e.g. .tscn), the search does not work properly.
Closes: #20692

Thanks!


[DisplayServer] Add an option for GDExtension to extend DisplayServer window creation.

Allow early native window subclassing (immediately after creation) required by AccessKit.
See https://github.com/godotengine/godot/issues/58074#issuecomment-1356799871 and https://github.com/bruvzg/godot_accesskit_demo

Superseded by https://github.com/godotengine/godot/pull/76829


Make it possible to edit the product name in several languages

What

[ ] Make it possible to edit the product name in several languages

[ ]

Part of

#2422

Fixed by #3890.


dprint-plugins: init

The plan is to keep track of official dprint plugins here, utilising nixpkgs' update infra. see https://github.com/numtide/treefmt-nix/issues/278#issuecomment-2565265766
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

cc: @zimbatm @kachick

$ nix build -f default.nix dprint-plugins --print-out-paths --no-link
/nix/store/22d7q55wgkplk908fai0hdynijm7ld2a-dprint-plugin-biome-0.7.1
/nix/store/yv8vzdqa310klg8nym8wgjqi34jgfc4l-dprint-plugin-toml-0.6.3
/nix/store/yqzi3c7n9lx2yzclbxvvcf5z36yyf2wv-g-plane-malva-0.11.1
/nix/store/cri28vlvf3wrail2b7az44zh66s1cnqj-dprint-plugin-jupyter-0.1.5
/nix/store/vl90ad48hvh3m7403cvigvgw816pb24l-dprint-plugin-dockerfile-0.3.2
/nix/store/lm3l1frdin9282914bvi4n0jghkbqrdk-dprint-plugin-ruff-0.3.9
/nix/store/75gvzwxijl9xcabzss3w8ivn9iy2rcwf-dprint-plugin-json-0.19.4
/nix/store/dig6r6qyfpxnlsc2057l9lzaxxh43md0-g-plane-markup_fmt-0.18.0
/nix/store/kiyapbsgkf4jkh8gafcfapwplrblza1d-dprint-plugin-markdown-0.17.8
/nix/store/si9wh2pp3agklivpanf6rl9qc2kdp03n-dprint-plugin-typescript-0.93.3
/nix/store/5l0qqsisfq58p2kkixs82m1g6vpc04az-g-plane-pretty_yaml-0.5.0
/nix/store/yvyvyymgd1d1my23ahxm31915zkqmgbc-g-plane-pretty_graphql-0.2.1

nixpkgs-reviewd workflow finished
Status and logs: https://github.com/phanirithvij/nixpkgs-reviewd/actions/runs/12552400861
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 369415

x86_64-darwin

:white_check_mark: 12 packages built:

dprint-plugins.dprint-plugin-biome
dprint-plugins.dprint-plugin-dockerfile
dprint-plugins.dprint-plugin-json
dprint-plugins.dprint-plugin-jupyter
dprint-plugins.dprint-plugin-markdown
dprint-plugins.dprint-plugin-ruff
dprint-plugins.dprint-plugin-toml
dprint-plugins.dprint-plugin-typescript
dprint-plugins.g-plane-malva
dprint-plugins.g-plane-markup_fmt
dprint-plugins.g-plane-pretty_graphql
dprint-plugins.g-plane-pretty_yaml

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 369415

aarch64-darwin

:fast_forward: 1 package marked as broken and skipped:

homepage-dashboard

:white_check_mark: 12 packages built:

dprint-plugins.dprint-plugin-biome
dprint-plugins.dprint-plugin-dockerfile
dprint-plugins.dprint-plugin-json
dprint-plugins.dprint-plugin-jupyter
dprint-plugins.dprint-plugin-markdown
dprint-plugins.dprint-plugin-ruff
dprint-plugins.dprint-plugin-toml
dprint-plugins.dprint-plugin-typescript
dprint-plugins.g-plane-malva
dprint-plugins.g-plane-markup_fmt
dprint-plugins.g-plane-pretty_graphql
dprint-plugins.g-plane-pretty_yaml

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 369415

x86_64-linux

:white_check_mark: 12 packages built:

dprint-plugins.dprint-plugin-biome
dprint-plugins.dprint-plugin-dockerfile
dprint-plugins.dprint-plugin-json
dprint-plugins.dprint-plugin-jupyter
dprint-plugins.dprint-plugin-markdown
dprint-plugins.dprint-plugin-ruff
dprint-plugins.dprint-plugin-toml
dprint-plugins.dprint-plugin-typescript
dprint-plugins.g-plane-malva
dprint-plugins.g-plane-markup_fmt
dprint-plugins.g-plane-pretty_graphql
dprint-plugins.g-plane-pretty_yaml

In my understanding, dprint and the plugins have WASM schema versions. If there is a mismatch between them, dprint CLI does not run the plugin.
As far as I know, it occurs when dprint < 0.47 and the plugin uses the crate dprint-core >= 0.67.
For example, when using an old dprint CLI and several latest plugins.
Use https://github.com/dprint/dprint/releases/download/0.46.3/dprint-x86_64-unknown-linux-gnu.zip
With dprint.json as below
{
 "biome": {
 },
 "plugins": [
   "https://github.com/dprint/dprint-plugin-biome/releases/download/0.7.1/plugin.wasm"
 ]
}

Then
> ./dprint check
Error resolving plugin https://github.com/dprint/dprint-plugin-biome/releases/download/0.7.1/plugin.wasm: Invalid schema version: 4 -- Expected: 3. Upgrade your dprint CLI (/tmp/tmp.0KZQ0xdk2Y/dprint).

As far as I know, the latest dprint CLI version 0.48.0 supports old schema versions. However, I think it is not a guaranteed specification.
How to keep the compatibility
A version is listed at https://github.com/dprint/plugins/blob/cc8cd4c35bb0685b0a599b8d3c30923e8f41b0a0/info.json#L2-L3, but it does not mean the JSON result always points correct schema versions.
So I suggest it. Adding a test that includes all packaged plugins in the dprint.json enhances the stability of the dprint package in combination with dprint-plugins.
Ideal state is one where an update-script updates the dprint and the plugins together, but I don't know how to realize it in nixpkgs.

So I suggest it. Adding a test that includes all packaged plugins in the dprint.json enhances the stability of the dprint package in combination with dprint-plugins.

Or would injecting the dprint CLI package for each plugin package's checkPhase be more fluent?

@kachick I will look into adding compatibility tests


Whats the difference between gulp-styl and gulp-stylus?

Whats the difference between gulp-styl and gulp-stylus?

See the styl repo linked in the readme.


VEGA-2493 detect cp address anomaly

Checklist

[ ] I have updated the end-to-end tests to work with my changes
[ ] I have added styling for Dark Mode
[ ] I have checked that my UI changes meet accessibility standards

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

Project coverage is 71.82%. Comparing base (28b7eb2) to head (8fe90c2).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #592   +/-   ##
=======================================
  Coverage   71.82%   71.82%
=======================================
  Files         119      119
  Lines        5303     5303
=======================================
  Hits         3809     3809
  Misses       1156     1156
  Partials      338      338

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


view freezes with 2G 13 channel tiff images

I am using the latest 0.4.17 version on python 3.9.2 Mac OS. I opened naperi viewer and dropped a 2G tiff image. The window just freezes. Whatever I do, it says in terminal: 2023-04-04 15:32:44.402 napari[12345:33460107] Warning: Window move completed without beginning.

Can you provide the output of napari --info or copy paste the info from the Help menu item?
Also by 2G tiff image do you mean 2Gb, as in size? how was this tiff saved?

How long is freeze?
Such a size of tiff is expected to freeze napari during load time.

Sure! It is 2Gb as size, saved by python tifffile. the freeze was like 15min before I closed it.
napari: 0.4.17
Platform: macOS-13.2.1-x86_64-i386-64bit
System: MacOS 13.2.1
Python: 3.9.2 | packaged by conda-forge | (default, Feb 21 2021, 05:02:20)  [Clang 11.0.1 ]
Qt: 5.12.9
PyQt5: 5.12.3
NumPy: 1.24.2
SciPy: 1.9.1
Dask: 2021.04.1
VisPy: 0.11.0
magicgui: 0.7.2
superqt: unknown
in-n-out: 0.1.7
app-model: 0.1.2
npe2: 0.6.2

OpenGL:
  - GL version:  2.1 ATI-4.9.51
  - MAX_TEXTURE_SIZE: 16384

Screens:
  - screen 1: resolution 2560x1440, scale 2.0
  - screen 2: resolution 2560x1440, scale 2.0

Plugins:
  - napari: 0.4.17 (77 contributions)
  - napari-console: 0.0.7 (0 contributions)
  - napari-svg: 0.1.6 (2 contributions)

How did you install napari? your pyqt5 is awfully old...

Could you execute this script (with the proper path to the file)
import tifffile

total_size = 0

with open("/path/to/tiff/file.tif", 'rb') as f:
    tif = tifffile.TiffFile(f)
    for page in tif.pages:
        total_size += page.size * page.dtype.itemsize

print(f"Image requires {total_size} bytes ({total_size / 1024**3} GB)")

import psutil

print(f"Available memory {psutil.virtual_memory().available / 1024**3} GB")
print(f"Total memory {psutil.virtual_memory().total / 1024**3} GB")

How did you install napari? your pyqt5 is awfully old...

Thank you both for replying! I was installing on top of my napari several years ago. I just reinstalled it and all is good for now. It must be some old version package being slow. Thanks for the help.


Travis container support

Fixes #3

This change is

At first glance, it looks like you did not try to recreate the postinstall script provided in the RPM. How did you find/decide which changes to make?
I saw your issue about building the ruby bindings, and there's a comment here about LD_LIBRARY_PATH; what other issues did you run into when relocating the install?

I've just now found https://github.com/vschoettke/node-oracle-test/blob/master/oracle_db_setup.sh , which also does an install without using the rpm's postinstall , but still reliant on sudo and the default layout.
There were not many relocation problems -- Oracle has always kept its software distinct from the operating system, and able to have multiple versions installed concurrently, which makes it relocation friendly.  However, I suspect there is still some problems to be ironed out, as it should be possible to get the ruby bindings to build out of the box.  As ruby internals are mostly a mystery to me, I'm going to attempt to get python bindings working.  That way I can better debug what is happening, and should be able to find the clue I need that will hopefully also help with ruby.

(They are fetching the .deb from https://github.com/vschoettke/ci-xe-deb-enc )

Note there is something strange going on with dist: trusty for container mode.  When I add it https://github.com/jayvdb/travis-oracle/commit/24cbe14c42f6edece6d4e7a37d0d63c992ea3fe5 the result is https://travis-ci.org/jayvdb/travis-oracle/jobs/128745488 where the build information includes Build dist: trusty, but then everything else says precise.

The trusty 'sudo-less' problem is https://github.com/travis-ci/travis-ci/issues/6025 , and definitely doesn't halt this changeset .

Closing this as the container infrastructure is gone.
https://blog.travis-ci.com/2018-11-19-required-linux-infrastructure-migration


How to change minimum deposit, round timer, pot item max, and % cut?

Title says all, I would like to start this issue so that it is easy to reference all the major configuration needs for the beginner.

Please check closed issues before posting new ones. https://github.com/ztizzlegaming/CSGOWinBig/issues/42

@Laessen please check the open/ closed issues. This is asked before.

I have already seen that closed issue. @TheAnthonyNL @J0nafin
It doesn't address minimum deposit or round timer. Also, I feel like this should have been included in the readme because all this stuff is pretty necessary.

Check-items.php : @bottom => $minDeposit = $totalPrice >= 100 ? 1 : 0;
Where 100 = $1, 10 = $0.1, 1 = $0.01
Round timer is on deposit.php => $endTime = round(microtime(true) * 1000 + 120000.0);


Possible to add sparse elements?

Thanks for the very nice library!  I'm interested in using hora for doing nearest neighbor finding in single-cell genomics.  The data of interest consist of very high dimensional points (D = 30,000), but for most points, most dimensions have value 0.  Therefore, I'd like to avoid (it's not really feasible) to densify the elements before indexing them.  Is there some way to provide a custom implementation of the relevant distance metrics for the indexed type such that I don't have to actually insert a dense representation of the points into the index?

The project seems not to be maintained anymore, but since we're doing something similar at Qdrant (https://github.com/qdrant/qdrant), I think I may answer that question. Those tools are rather designed to support neural embeddings and they typically won't be sparse.


Tiles disappear after zoom 11

Describe the bug
Map data disappears as you zoom in past zoom level 11. We should be using overzoom so theoretically zoom levels 12 and above should still work, but for some reason this is not working. Overzoom should be enabled by default - maybe we are not implementing overzoom correctly.
To Reproduce
Steps to reproduce the behavior:

Open the map page in the app
Zoom in past zoom level 11.99 (you can see the zoom level in the URL)
Tiles disappear.

Expected behavior
At step 3 above, data should still be visible.
Screenshots

Desktop (please complete the following information):

OS: MacOS Mojave
Browser: Firefox
Version: 89

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

We should note that in our style file we are setting minzoom and maxzoom , but even if these are removed, or the source maxzoom is set to be less than the layer maxzoom, we're still seeing that the tiles disappear at these higher levels

Our current tippecanoe command is as follows:
docker run --rm -it -v ${PWD}:/data mikegiddens/tippecanoe tippecanoe --force -Z 5 -z 11 -l tl_2010_bg -o /data/tl_2010_bg/mbtiles/tl_2010_42_bg10.mbtiles -l blocks /data/tl_2010_bg/geojson/tl_2010_42_bg10.json
thus the stopping after 11 (the -z 11 arg above) - that said, with overzoom this shouldn't be a problem, so I suspect something is up in our mapbox style config

@NatHillardUSDS  try setting maxzoom on the source to the maxzoom in the layer style and see if that helps. overzoom should still happen beyond where tiles are available

Check this out here:
https://d2zjid6n5ja2pt.cloudfront.net/justice40-tool/be0256/en/cejst/?flags=mb

The overlay disappears at zoom level 22, but I don't think that's a problem as most people will not need to zoom in that far.
Looks great!


Fix file streaming

Closes #72

Codecov Report

Merging #73 (4fa5f04) into master (093b17f) will increase coverage by 0.07%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           master       #73      +/-   ##
===========================================
+ Coverage   99.92%   100.00%   +0.07%
===========================================
  Files          93        93
  Lines        1286      1284       -2
  Branches       71        71
===========================================
- Hits         1285      1284       -1
+ Misses          1         0       -1

Impacted Files
Coverage Δ

src/local-files/local-files.controller.ts
100.00% <100.00%> (+3.57%)
:arrow_up:

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


Contributor usability

rewrite testing system, make it easier to rewrite parts of the compiler and check for regression, know what parts are stable and what parts need some help.
Short term:

[ ] Rewrite testing system to use utest library (current testing library that Haxe uses)
[x] Follow Hxnodejs's example and add a settings.json to  Haxe Format on save for vscode.
[ ] Multithread tests.
[ ] Add a config file system to exclude certain tests if testing.
[ ] Run the tests on all supported Haxe targets.
[ ] Add the test runner to github actions to run on every commit and pull request.
[ ] Output data to be graphed to see progress on unit testing.

Medium term:

[ ] Document potential features that can be added independently such as, cgo, image support, runtime etc.
[ ] Explain in detail how certain source to source language features get translated such as pointers, interfaces, local types etc.
[ ] add an Issues test suite following Haxe's example and run Issues that have come up and been fixed in order to prevent regression.

Long term:

[ ] Allow a correctly formatted issues with a go code block to be run by a github action to check the compiler issue.
[ ] Add graphs for target generated code size.
[ ] Benchmark speed graphs.
[ ] Create a separate repo to run problematic go libraries and track their progress. A separate repo because it will probably be quite large and the errors should lead back to either the standard library or the language.
[ ] Bootstrap the compiler and have it have no dependencies except for testing.

I think no focus should be put to changing the code structure until the compiler gets bootstrapped, language feature spec compliance is almost done and most of the work work will be standard library tweaking.
Structure change ideas:
Typer.hx at the moment is about 5k lines, it should be broken up in the future by decls,statements,exprs,type system,analysis,general utils,features (example //#go2hx export system) etc
export.go will be merged with Typer.hx systems in the future and then broken up into the pieces listed above. the bootstrap will allow go ast analysis tools to be used for the code that comes into go2hx, cleaner calling of go methods, and no more need for socket transport of the data.

Most of the big tasks are done, ones I still want to implement:

speed benchmarks
document tasks to be done such as adding image support, cgo, bootstrapping etc.
Hold a list of 3rd party libs and have the compiler quickly check against what std libs it uses vs which ones pass at the moment and notify if a new library is passing.

These issues can be created as separate issues in the future.


Add IlpOverHttp and FX connection settings to ConnectorSettings

Fixes #453

@sappenin I added a bunch of javadocs and cleaned everything up!


ae.safetensors vs ae.sft

Fluxgym asks for ae.sft but I have only ae.safetensors. Do I have to keep manually modifying the text in the GUI everytime renaming "sft" to "safetensors"?

sft and safetensors have no difference. You can change model name as sft or change model path as "path/to/ae.safetensors" in code.

sft and safetensors have no difference. You can change model name as sft or change model path as "path/to/ae.safetensors" in code.

I already mentioned that I know I can change the code, but when I then make a change to a setting ,the code reverts back to sft file so I have to constantly keep renaming it if I make a change of setting...

I already mentioned that I know I can change the code

You're not talking about the code, you're talking about the GUI.
In the "app.py" folder on line 204, you can change it from .sft to .safetensors.

I already mentioned that I know I can change the code

You're not talking about the code, you're talking about the GUI. In the "app.py" file on line 204, you can change it from .sft to .safetensors.

ok that's good to know. Thank you!


Editor placeholder update

This PR...
Changes

Changed the image and the links in editor placeholder based on the design provided

Screenshots

Checklist

[x] tested locally
[ ] added new dependencies
[ ] updated the docs
[ ] added a test

Will make the necessary changes @topliceanurazvan

Hey @topliceanurazvan, I made the requested changes. Little heads up, I forgot to sync my fork with the latest changes before committing my changes so I pushed another commit with the synced changes.


Issue pulling from reMarkable to Zotero with Nextcloud as WebDAV

Apologies for my many issues - but I really really want to get this running.
Thx for the prior help. Figured, I'll open a new thread since it became a new issue :)
--
Here's the issue:
Successfully pushed a document from my Zotero which runs Nextcloud as WebDAV following these instructions (https://mlohr.com/sync-zotero-library-to-nextcloud/). All files are perfectly synched on the WebDAV, your app could perfectly pull it from the WebDAV and push it to ReMarkable, all great. Then I added some notes to the doc and moved it to my 'READ' folder, then I ran the "pull"-command and got this output:

From what I understand, it failed to download the file (which it successfully reached at my RM) to the folder in my "TEMP" folder - since the specified folder does not exist any more. So I went to my TEMP folder and confirmed. Now I am curious, why that is, if that is a WebDAV issue from nextcloud? Any ideas?

I don't think it has something to do with Nextcloud or WebDAV. Rather, it seems like my dirty implementation of temp files bites me here. Since this program was mainly put together for my own needs, it was only used and tested on Linux. And while Python's pathlib library seems to have helped a lot in making the program run with Windows style path conventions, I haven't chosen the most robust way of getting the tempfile location where the program tries to store files it gets from remarkable's cloud for further processing. I will tty to fix this, but it won't happen tonight.

Any chance you're getting at that problem within the next 1-2 months?

Turns out it was actually not an issue with the temp path, but with rmapi having changed how its get function works, breaking the processing of the pdf. This should be fixed with this commit 8e2dc5d.

Almost...I updated with your last commit, then pushed file to remarkable, pulled it into the "read" folder and ran the "pull" command - this is the output....

I encountered this issue as I was trying to fix the other bug and it seems to come down to how Windows handels some special characters in the file names that rmapi puts out. One way to fix this would be to sanitise file names to not use special characters beyond maybe a minimal set like dashes. Unfortunately, I can't do this programmatically right now since the file name is the source of truth for matching the downloaded files back with their Zotero entries. Now I'm sure there are ways to handle this better, but I fear those might be beyond my skills right now. Apart from that, it seems like the git bash shell does a whole lot of funny things to paths that I can't really account for.
Now, I think the best way to get over these issues would be to run the program in a true Linux environment. Don't worry, you don't need to switch to Linux or install it on your PC directly since Windows offers the Windows Subsystem for Linux which installs a minimal Ubuntu environment and gives you access to a "true" bash shell under Linux right inside Windows.
To install it, open a Windows PowerShell terminal and type
wsl --install

Once it finished downloading Ubuntu, it will prompt you for a restart. After the restart, you should see a terminal finishing the install. It will prompt you for a username and password and drop you into your Ubuntu bash shell. From here, I'd suggest updating Ubuntu's packages with
sudo apt update
sudo apt upgrade -y

Then just setup rmapi and zotero2remarkable following the respective Readmes. Note that git should already be installed, but you might need to install go by running
sudo apt install golang-go -y

Also note that there are ways to access the Windows file system from WSL and vice-versa, but that is not really needed for this program. You might just want to copy paste the content of your config file into a new file inside WSL. To do so, move to the zotero2remarkable folder and type nano config.yml to open the text editor. Copy your config and close it hitting CTRL+X and then y twice.
Ubuntu will also appear as an entry in your Windows start menu for future access.

Hey,
ok, I think I got it working - up to the point that it is a remarks-issue - I guess. Could you quickly confirm, that the following issue is a remarks issue and not a zotero2rm-bridge issue? Then I could head over there and annoy lucasrla with my wishes...

Oh I just saw that there might be a remarks fork that actually works with vm6:
https://github.com/lucasrla/remarks/issues/58#issuecomment-2156148243
is this a workeable branch?
https://github.com/Azeirah/remarks


J F: Watch anttravels.com

J F requests the watch of the watch_keyword anttravels\.com. See the Metasmoke search here and the Stack Exchange search here.

anttravels\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

!!/approve

Coverage remained the same at 65.763% when pulling 5cbb71b4db88991cec7dea683608abdf1a0a4533 on auto-blacklist-1527676907.5647418 into 588424fab1a247f386bf33ec368382d832343d5e on master.


Website update/reorganization

Reorganization/updating of website.
Some remaining TODOs without which this PR should not be merged:

Add Colab for MAE (@yaodongyu)
Add links to MAE code/segmentation visualization code (pending a repository reorganization)
Readme updates (acronym)

Some initial comments

assets/CRATE_segmentation.svg was deleted; deadlink on index.html
links to page anchors in tl;dr seem to not be set up
tl;dr text's associated div needs styles updated (e.g. match section div)
heading choices don't seem scaled optimally (we should maybe have h2 a bit more size-distinguished from h3, or each paper title should also be h1)
likely want to think about the organization ('overall' page title being the same as the page sub-titles for each paper may not have enough contrast)

Some style thoughts

We should restyle the title for the mobile pageview
We might want to think about making an 'aggregated' first figure that captures ideas across all the individual papers
padding before/after on narrow-figure vs. reg-figure
equation line-breaking at narrow page widths

Let's discuss these together and then assign TODOs

Thanks!

assets/CRATE_segmentation.svg was deleted; deadlink on index.html

Oops my bad, will fix.

links to page anchors in tl;dr seem to not be set up

This one I don't get, it seems to work for me at least locally.

padding before/after on narrow-figure vs. reg-figure

I think this is actually a property of the figures themselves, not the CSS...? I could be wrong.
Rest SGTM, let's set up a meeting offline

Changes incorporated -- @yaodongyu @DruvPai awaiting main branch TODOs in the original comment


Concurrent request ends up in runtime memory error

If i run any base image in docker it crashes when a concurrent request is made. In AWS environment it will create new instance to handle the request but here there will be only one instance so it will not handle the other request but it should return graceful error instead of runtime error and crashing the container.
Steps to reproduce. Just follow these steps to create a basic image and run it in docker container.
Make concurrent request to invoke your function then the container will crash with below runtime error.
(rapid) ReserveFailed: AlreadyReserved panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0x6af115] goroutine 62 [running]: go.amzn.com/lambda/rapidcore.(*Server).Invoke.func2()         /LambdaRuntimeLocal/lambda/rapidcore/server.go:666 +0xf5 created by go.amzn.com/lambda/rapidcore.(*Server).Invoke         /LambdaRuntimeLocal/lambda/rapidcore/server.go:649 +0x23d

This is really https://github.com/aws/aws-lambda-runtime-interface-emulator/issues/97.


refactor(web): deployment http api

Add deployment http api.
Remove deployment grpc api.

Codecov Report
Patch and project coverage have no change.

Comparison is base (79cf99b) 15.38% compared to head (e811bd7) 15.38%.

:exclamation: Current head e811bd7 differs from pull request most recent head eefdd11. Consider uploading reports for the commit eefdd11 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #519   +/-   ##
========================================
  Coverage    15.38%   15.38%
========================================
  Files           58       58
  Lines         5921     5921
========================================
  Hits           911      911
  Misses        4983     4983
  Partials        27       27

Impacted Files
Coverage Δ

golang/internal/grpc/grpc.go
0.00% <0.00%> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Inserting data with retention policy does not work with timestamp

Bug report
System info:

InfluxDB 1.1.1 (installed via Homebrew)
macOS Sierra 10.12.3 (16D32)

Steps to reproduce:
Open the influx CLI and run:
> CREATE DATABASE testing
> USE testing
> CREATE RETENTION POLICY hello ON testing DURATION 24h REPLICATION 1
> SHOW RETENTION POLICIES
name	duration	shardGroupDuration	replicaN	default
----	--------	------------------	--------	-------
autogen	0s		168h0m0s		1		true
hello	24h0m0s		1h0m0s			1		false
> INSERT INTO hello foo,foo_id=bar total=0.0<PHONE_NUMBER>835
Using retention policy hello
> SELECT * FROM hello.foo
> SELECT * FROM testing.hello.foo

It yields no results even though no error was raised.
Expected behavior:
I expected data to be inserted properly with the retention policy.
Actual behavior:
No data inserted.
  It's getting dropped because that time is actually 1970-01-01 00:24:48.740963835 +0000 UTC.  Since your hello retention policy is 24hr, you are writing too far into the past for that retention period.
Adding 6 zeros onto that timestamp<PHONE_NUMBER>835000000) creates a date at 2017-03-05 19:09:23.835 +0000 UTC which might be what you were trying to do.

@jwilder Oh, that makes some sense. I wish InfluxDB returned an error though. For instance, it does return an error if the retention policy does not exist.


output versioned function invokes

Description
@Zaid-Ajaj opening this up to help us use GitHub UI for review; the PR you had checked in providers/ changes which breaks the ability to use GitHub UI. We have some scripts to help check in that with "one provider per commit" and we use a stacked PR for now to workaround. Anyhow, I'll use this PR for now to comment. It's identical to yours just without providers/ and pr.yml change (might need to add that, I see why we need it).

Fixes # (issue)
Checklist

[ ] I have added tests that prove my fix is effective or that my feature works

[ ] I have updated the CHANGELOG-PENDING file with my change

[ ] Yes, there are changes in this PR that warrants bumping the Pulumi Service API version

@t0yv0 I believe this bullet point can be done in a separate task:

Hand-port runtime/mock tests for output-funcs. This may sound tedious but doing it mechanically for all languages has been worth the time for me in the past, every attempt found new bugs. https://github.com/pulumi/pulumi/tree/master/pkg/codegen/testing/test/testdata/output-funcs/dotnet-extras/Tests

Other than that, I will enable the tests and see if anything breaks + adding nested properties that are objects (which should be wrapped in output as well)
Will reach out if I get stuck

Going back to that PR.


Potential fix to very slow performance

This is partly a bug report, partly a user enhancement.
On my super slow, old laptop, simulations can run very slowly (1-to-1 real time to simulation time or worse, even on 3600x acceleration) on a large map like South Seattle with many active trips (especially once gridlock sets in). I have found that I can very dramatically improve the simulation speed if I zoom the view out enough to switch from detailed lane-specific view to the lower-resolution view where all travelers are represented by dots of different colors. To get the fastest performance, I zoom the map out just far enough to switch views but no farther and then uncheck all forms of travelers from the display. For me, this trick makes the difference between taking the simulation from midnight to 6 a.m. in several minutes versus several hours.
Now, the recommendation. 1) Let users know about this option via the tutorials or some other help resource, if it's not already in there. 2) Make a one-click "turbo time warp" mode that minimizes graphic processing to get the fastest-possible simulation on machines with limited resources. I can imagine that this could be a global option, i.e. a radio button in a settings menu selecting either "Pretty timewarps" or "Utilitarian timewaps".

Added a checkbox on the jump-to-time panel for the 2nd idea. Is this usually how you advance large steps? I could also expose it in the settings panel.

I hadn't been using the jump-to-time panel, but now that you mention it,
it's an easier method than what I've been using. I was using the button at
the bottom of the screen to continuously jump +1 hour and then had the game
speed set to 3600x to keep things moving fast when it drops from time warp
back into the regular game mode. The jump-to-time window is a much easier
way to achieve the same effect.
On Sat, Jul 4, 2020 at 1:41 PM Dustin Carlino<EMAIL_ADDRESS>wrote:

Added a checkbox on the jump-to-time panel for the 2nd idea. Is this
usually how you advance large steps? I could also expose it in the settings
panel.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dabreegster/abstreet/issues/125#issuecomment-653809859,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQEDTNEVZRJIYGAA5HYF3V3RZ6HZHANCNFSM4OQPPUUQ
.

That's very useful UX feedback. :D  Is there any reason why the jump control wasn't an obvious match? We've pondered variations of combining the time/speed panels before that could make jumping to a time easier, but so far not implemented them. On larger maps and slower computers, jumping back/forth through time is inevitably slow, so hiding the control behind a button seems justified.

I think the jump control wasn't an obvious match because I didn't see it
(or remember it) until you reminded me about it. It was probably included
in the tutorial, but I clearly didn't remember it. There is a lot going on
in the game, and it can be pretty overwhelming at first. It would probably
be good to retake the tutorial again after spending some time with the game
to remind me of things that I've missed. It's likely that there are other
ways that I'm not optimizing my use of the interface.
On Sat, Jul 4, 2020 at 4:26 PM Dustin Carlino<EMAIL_ADDRESS>wrote:

That's very useful UX feedback. :D Is there any reason why the jump
control wasn't an obvious match? We've pondered variations of combining the
time/speed panels before that could make jumping to a time easier, but so
far not implemented them. On larger maps and slower computers, jumping
back/forth through time is inevitably slow, so hiding the control behind a
button seems justified.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dabreegster/abstreet/issues/125#issuecomment-653822638,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQEDTNGJP7OWY3JSU32D353RZ63AZANCNFSM4OQPPUUQ
.


Spotify Connect scrobbling broken in Android N

Hi,
Since upgrading to Android N, scrobbling no longer works for casted audio.
In my case, I'm testing with Spotify Connect to a Chromecast Audio, but no tracks are detected anymore.
It might be related to this battery optimization: https://developer.android.com/about/versions/nougat/android-7.0-changes.html#bg-opt, but I don't have Android experience (although I might give it a go).

Nevermind, I couldn't enable "Device broadcast" when the app was casting, but you can change it when playing locally and then it's also valid when casting.


Acknowledge fairmat funding in docs

Update dev-requirements which were missed in last PR as well.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.03%) to 78.406%

Files with Coverage Reduction
New Missed Lines
%

tests/dataconverter/test_writer.py
1
96.67%

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
2814

Relevant Lines:
3589

💛  - Coveralls


Tightening Subscribe Response MID0061

The MID0061 object through MIDIncome will not update to new data. When I run more than one tightening the tightening information received in the onTighteningReceived function is always the same as the first tightening received. I have looked at the raw data coming in the logs and I can see they are different and the Tightening ID is increasing in the raw data string but the new data is not being parsed into the object.
I am using Mid0060 revision 6 because my controller reports that revision 7 is not available.

Sorry for the delay. I will check it out, I might figure out on my own, but can you exemplify the way you are using it?
About the revision, as far as I know, usually depends on controller's firmware, but there is no problem using the library with another revision.

I've checked, maybe there is a problem with MessagesTemplate possibly using the same instance of MID to parse.
If you could provide the way you're using it, it would be awesome. (if is different from the sample)

I could simulate exactly your problem, I'll be taking care of this and release a new version

Solution will be provided in version 3.X.X, please keep an eye here (or on NuGet)


Add release notes for the Project Explorer fixes

 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.İevgen Baida seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Allow different miterBoxes directions

Currently one problem that has appeared a few times is that miterBoxes overlap and then on the surgicalGuide after the difference boolean operations the structure of the slots is brittle, like on the second and third slots (from left to right of the fibula guide):

This should be easy to implement instead a line that sets the direction for all boxes, a point list with points created over the fibula surface will allow a different box direction per point

The combobox should allow a markups line or a fiducial list. If it's the later it should verify the number of points matches number of fibula planes


Picking a new MaxNALUSize

After more usage, it turns out that the newly raised (#30) MaxNALUSize is still not enough for 2160p60 streaming:
unable to decode AVCC: NALU size (4298040) is too big, maximum is 4194304

Before opening another pull request to raise the limit again, I would like to understand more about the effects of this value on memory usage. Would it be ok to just double it?

Hello, that variable doesn't influence memory usage, it's a limit on the maximum available memory in order to prevent people from creating specially-crafted packets that can crash software that depends on this library.
In case of RTSP / WebRTC / SRT / UDP, only one NALU at a time is routed from publisher to readers, therefore the maximum RAM occupied by a stream is MaxNALUSize * (maximum write queue size).
In case of HLS, a sequence of NALUs is kept into memory because HLS works by serving segments of NALUs, therefore the maximum RAM occupied by a stream is MaxNALUSize * segment duration * number of segments.

BTW i've renamed the variable into MaxAccessUnitSize in order to apply it to the entire access unit. An access unit is a sequence of NALUs referred to the same time instant.

Thanks for the detailed explanation. Do you plan to update the limit yourself? I'd be happy to test it afterwards.


Structure-Container /USI/CL_BAL_DC_STRUCTURE: Potential Loss of Data for deep structures

The data of deep structures might be lost, in some cases.
The following test report reproduces the issue.
TYPES: BEGIN OF ty_deep_structure,
         field_01 TYPE char10,
         field_02 TYPE string,
       END   OF  ty_deep_structure.

DATA(logger) = /usi/cl_bal_factory=>get_instance( )->create_new_logger( i_log_object = 'Z_MY_LOG_OBJECT'
                                                                        i_sub_object = 'Z_MY_SUB_OBJECT' ).
DATA(token) = logger->claim_ownership( ).

DATA(structure_container) = NEW /usi/cl_bal_dc_structure(
                                    i_structure = VALUE ty_deep_structure( field_01 = 'THIS DATA'
                                                                           field_02 = 'WILL BE LOST!' ) ).

logger->add_free_text( i_message_type = /usi/cl_bal_enum_message_type=>information
                       i_free_text    = 'Data of structure will be lost'
                       i_details      = structure_container ).

logger->save( token ).
logger->free( token ).

The debugger reveals, that the data is temporarily available inside the constructor.

Right after leaving the constructor, the data reference inside the data container will still be bound, but the dereferrenced structure will be initial!

The constructor of the class should be adjusted to avoid unexpected loss of data.
Replacing this
structure = REF #( i_structure ).

with that
CREATE DATA structure LIKE i_structure.
ASSIGN structure->* TO FIELD-SYMBOL(<structure>).
<structure> = i_structure.

fixes the issue.
This might not be ideal in terms of performance, so this might be changed again in the future, but for now I'd rather accept an insignificant hit to performance than an unexpected loss of data.

Adjusted the constructor. Data is now cloned into a newly created data reference, which avoids the issue.
The new test method lcl_unit_tests_serialization->test_keeps_deep_struc_values will prevent a regression in subsequent releases.


Docs search not working when looking at not-latest and not-stable version

Issue Summary

Search on the documentation site is not working when using a version other than "latest" or "stable".
Steps to Reproduce

Go the the docs site for the "stable" version: https://docs.wagtail.org/en/stable/search.html
Enter "test" into the search bar and hit enter.
See the search results.
Switch the version in the bottom right corner to something other than "latest" or "stable", e.g. "2.16.3": https://docs.wagtail.org/en/v2.16.3/
Enter "test" into the search bar and hit enter.
See there are no search results.

Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?

I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: (yes / no)

Technical details

Browser version: Independent of browser (Tried Safari and Firefox on macOS).

Pretty sure this already raised https://github.com/wagtail/wagtail/issues/8159

Closing as duplicate.


How to run the code?

Really great work.
I have great trouble realizing the TextStyleBrush as they don't open source the code.
I am wondering if your code could work and how to run the code.
Thanks.

me too

Hi
It's my trying to implementation for this paper, but my version it's not working.
But yoy can see examples for run my code:
https://github.com/asromahin/fline/blob/main/examples/gan/text_style_brush_train.py


QuackLib 2.2.2 RSWires 3.0.0 SpongeForge Crash

crash-2018-08-24_16.48.19-server.txt
This happened after a while, not instant. Public server. Did not happen on 2.1.1, no idea.
Could be a rare issue that's never happened before though, or a one time thing, Ill report back here if it happens again.

Redownload the latest version of RSWires. I know it's a bit confusing since there's 3 files with the version 3.0.0, sorry :P

Why not make it 3.0.1 or something, that really is confusing lmao

I didn't bump the version number because I didn't change any of the code

If it doesn't work properly and the newer 3.0.0 version fixes the issue, Id bump the version even with no code changes. But that's just me ;-;


added support for download counter on folders at Sourceforge

This pull requests allows to display the Sourceforge download count of a project folder.
On Sourceforge, projects are like organisations on Github. They may contain multiple repositories and download areas for individual software developed by the same group.
For example the Arianne Project consists of Stendhal and Marauroa. So in the Github readme file of Stendhal and Marauroa I like to display their individual counts. Not the download count of the complete Arianne project/organisation.
The attached pull requests allows to optionally specify a download folder. If it is omitted the project count is used. Thus, this change is fully compatible to existing badge uses.

:+1: neat! I'll try to put it live within 24h.


Setting UTIME_OMIT correctly for FreeBSD, Haiku and Illumos

I got EINVAL from set_file_mtime() on FreeBSD and fixed it by adding the correct definition for UTIME_OMIT.
Moreover I also tried to find the correct definitions for the other values of target_os.

Thanks!


Disable bundles for testing

I've got a jspm project which has bundles, however i don't want the bundles to be used for my tests, it would be nice to support disabling bundles in the same way that: https://github.com/Workiva/karma-jspm
plugin does.

Thanks for the PR!
I'll create a 0.16.0 tag and release tonight once I get home.

@rolaveric 👍  awesome! you bet me to asking for a publish. Thanks

Published v0.16.0