text:
Ignore always failing tests

This either indicates a bug or a behavior change introduced in Gradle 7.3

@bot-gradle test and merge

OK, I've already triggered a build for you.

authors: bot-gradle ljacomet


text:
Introduce Task.doNotCacheConfigurationIf

For optimistic incremental adoption of the configuration cache.
The new API supports the scenario where one would like to use the configuration
cache whenever it just works via the configuration-cache-problems=warn setting
and have it automatically disabled whenever tasks for which configuration
caching has been proven problematic are scheduled.

@bot-gradle test ACC

Sorry some internal error occurs, please contact the administrator @blindpirate

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test ACC

Sorry some internal error occurs, please contact the administrator @blindpirate

@bot-gradle help

Currently, the following commands are supported:
@bot-gradle test <BuildTrigger1> <BuildTrigger2> ... <BuildTriggerN>

A trigger is a special build for this PR on TeamCity, common triggers are:

SanityCheck/CompileAll/QuickFeedbackLinux/QuickFeedback/PullRequestFeedback/ReadyForNightly/ReadyForRelease
Shortcuts: SC/CA/QFL/QF/PRF/RFN/RFR
Specific builds:

PT: PerformanceTest, all performance tests for Ready For Nightly stage.
APT: AllPerformanceTest, all performance tests, including slow performance tests.
AST: AllSmokeTestsPullRequestFeedback
AFT: AllFunctionalTestsPullRequestFeedback
ASB: AllSpecificBuildsPullRequestFeedback
ACC: AllConfigCacheTestsPullRequestFeedback
ACT: AllCrossVersionTestsReadyForNightly
AFTN: AllFunctionalTestsReadyForNightly
ACTR: AllCrossVersionTestsReadyForRelease
AFTR: AllFunctionalTestsReadyForRelease

@bot-gradle test and merge

queues this PR for testing and merges if all tests pass by:

Creating a merge commit from your PR branch HEAD and the target branch
Running a ReadyForNightly build against the merge commit
When it passes, fast-forward the target branch to this merge commit (i.e. merge the PR)

The merge commit is called a pre-tested commit, which means that it fully tests the integration
of your branch HEAD and latest master, instead of only testing your branch HEAD.
@bot-gradle cancel

cancel a running pre-tested commit build or remove it from queue

@bot-gradle clean

clear the conversation history

@bot-gradle help

display this message

To run a command, simply submit a comment.  For detailed instructions see here.

@bot-gradle test AllConfigCacheTestsPullRequestFeedback

@bot-gradle clean

@bot-gradle test ACC

Sorry some internal error occurs, please contact the administrator @blindpirate

Sorry some internal error occurs, please contact the administrator @blindpirate

We might consider this again in the future but it's more likely we introduce something at the project level.

@bot-gradle test ACC

OK, I've already triggered the following builds for you:

AllConfigCacheTestsPullRequestFeedback build

source: gharchive/pull-request

authors: bamboo bot-gradle

repo: gradle/gradle

license_type: permissive

license_source: github-api


text:
Merge daemon defaults with user-supplied jvmargs

Fixes #19750
Context
Previously, setting any value for org.gradle.jvmargs caused all default settings to be lost.
This often resulted in important defaults like -XXMaxMetaspaceSize being omitted when a user
attempted to provide more memory to a build process.
With this change, default jvmargs will be retained unless specifically overridden by a user-supplied argument.
One exception is that setting either -Xmx or -Xms will cause the default heap size settings to be omitted, preventing
user-supplied values from conflicting with default values (like having a min heap larger than max heap).
Contributor Checklist

[ ] Review Contribution Guidelines
[ ] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[ ] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[ ] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[ ] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[ ] Ensure that tests pass sanity check: ./gradlew sanityCheck
[ ] Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

@bot-gradle test this

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@octylFractal Thanks for the feedback. Unfortunately this PR is hitting some hard-to-understand test failures that will require further investigation before this change could be merged. I'm not sure if/when I'll find time to do that.
In the meantime, would it be helpful if I close this PR (or convert to draft?)

I'm looking at the test failures now, so don't worry about that.

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bigdaz I looked into the "hard-to-understand test failures", and the underlying issue is that we used to let anything that set org.gradle.jvmargs run with unlimited Metaspace if not specified, and now we limit it to 256m. After some research, @DPUkyle and I came to the conclusion that it would be a good idea to increase this to perhaps 1G by default, or remove it entirely. What do you think?

We should not remove the setting altogether. The entire reason for this PR is that users are setting org.gradle.jvmargs without specifying MaxMetaspaceSize, and the daemon process is consuming more and more memory until the process dies.
See #19750 for details.
Providing a higher default value might make sense. Or since these failures seem specific to the Kotlin compiler daemon (I think), perhaps the best fix is to ensure an appropriate MaxMetaspaceSize for this process.

@eskatos I see you assigned this back to me, but I'm not sure what action can/should be taken.
The current behaviour is that if you don't set any jvm args, then we set MaxMetaspaceSize=256m. If a user sets a completely unrelated jvm arg, then we don't provide any default value for MaxMetaspaceSize.
Perhaps this makes sense: we provide a default set of jvm args and you can choose to override the entire set, but not one value in the set. But I've seen a number of users struggle with this: they give their build more memory (say -Xmx1024m), and their build starts to run out of memory! It's a slightly different out of memory error, but users don't really know how to fix this.
There are a few options to address this:

Do nothing, but perhaps improve the documentation so it's clear that setting -Xmx does more than just giving more memory.
When a user sets just one of the values that we provide a default for, we only change that value, and leave the others in place. (That's what my PR tries to do).
Provide a different (or higher) default value for MaxMetaspaceSize. We should probably document this.
Provide a better model for specifying the memory settings for a build, allowing users to set value independently.
???

I could help out with any of 1-3. I think 4 would require more work and should be tackled by the BT team.
WDYT?

I assigned it back to you while triaging unassigned PRs and adding assignees to all team members/authors.
I think this PR is a reasonable improvement and will address the current confusion. But as shown by the failing tests, this may break builds.
I'm not sure if raising the default metaspace size to 1g would be a good move. Loots of builds won't need that much.
@octylFractal, @big-guy, would the approaching 8.0 be a good time to address this? Can you take over making a decision on this?

@bot-gradle test ReadyForNightly

OK, I've already triggered the following builds for you:

ReadyForNightly build

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.

The performance test asserts there's only one daemon involved in multiple iterations. However, this PR seems to change something in daemon compatibility so there're multiple daemon started. The performance test failure is reproducbile.

We're not able to look at this until 2025

authors: big-guy bigdaz blindpirate bot-gradle eskatos jvandort octylFractal


text:
Publish 7.4.2-20220325135218+0000

Publish 7.4.2-20220325135218+0000

@bot-gradle test and merge


text:
Run native related builds on Intel macs only

Since 2024 there will be only 2 Intel Mac build agents. Because only native builds are architecture-dependent, this PR only executes native subprojects on Intel Macs.

I have squashed this PR as 1f49fed23a4ec031d66d628e833546019d84c605

Can't cherry-pick due to merge conflict. You have to cherry-pick by yourself.

Sorry some internal error occurs, please contact the administrator @blindpirate

authors: blindpirate bot-gradle


text:
Fix port name not in effect and nodePort changed failed when update

When grafana instance is created, the port name configured for the service does not take effect. is also not effective when changed grafana nodeport
Description

apiVersion: integreatly.org/v1alpha1
kind: Grafana
metadata:
  name: grafana
  namespace: monitoring
spec:
  client:
    preferService: true
  ingress:
    enabled: False
  config:
    log:
      mode: "console"
      level: "error"
    security:
      admin_user: "root"
      admin_password: "12345"
    log.frontend:
      enabled: true
    auth:
      disable_login_form: False
      disable_signout_menu: False
    auth.anonymous:
      enabled: True
  service:
    name: "grafana-service"
    labels:
      app: "grafana"
      type: "grafana-service"
    ports:
      - { nodePort: 30004, port: 3000, protocol: TCP, name: web }
    type: NodePort
  dashboardLabelSelector:
    - matchExpressions:
        - { key: app, operator: In, values: [grafana] }
  resources:
    # Optionally specify container resources
    limits:
      cpu: 800m
      memory: 800Mi
    requests:
      cpu: 100m
      memory: 100Mi

bug1：When spec.service.port name is web,but deploy name is grafana. It's restricted in the program.
bug2：If the first grafana deployment nodePort is 30001,when I changed cr nodePort to 30002，It didn't work
Relevant issues/tickets

Type of change

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

Checklist

[ ] This change requires a documentation update
[x] I have added tests that prove my fix is effective or that my feature works
[ ] I have added a test case that will be used to verify my changes
[ ] Verified independently on a cluster by reviewer

Verification steps

@gitgaoxiang can you please rebase?

rebase
Already done

@pb82 Done.

Don't know why the e2e failes. For some reason it has returned
[
    {
      "id": 1,
      "uid": "He5NIuAVk",
      "title": "grafana-operator-system",
      "uri": "db/grafana-operator-system",
      "url": "/dashboards/f/He5NIuAVk/grafana-operator-system",
      "slug": "",
      "type": "dash-folder",
      "tags": [],
      "isStarred": false,
      "sortMeta": 0
    },
    {
      "id": 3,
      "uid": "0ed390cdb20229700c1741b72138163ce2214445",
      "title": "Node' Exporter 'Full",
      "uri": "db/node-exporter-full",
      "url": "/d/0ed390cdb20229700c1741b72138163ce2214445/node-exporter-full",
      "slug": "",
      "type": "dash-db",
      "tags": [
        "linux"
      ],
      "isStarred": false,
      "folderId": 1,
      "folderUid": "He5NIuAVk",
      "folderTitle": "grafana-operator-system",
      "folderUrl": "/dashboards/f/He5NIuAVk/grafana-operator-system",
      "sortMeta": 0
    },
    {
      "id": 2,
      "uid": "2150edaf610ab34b8f1050e5bcd5d4ca5903e1c2",
      "title": "Simple' 'Dashboard",
      "uri": "db/simple-dashboard",
      "url": "/d/2150edaf610ab34b8f1050e5bcd5d4ca5903e1c2/simple-dashboard",
      "slug": "",
      "type": "dash-db",
      "tags": [],
      "isStarred": false,
      "folderId": 1,
      "folderUid": "He5NIuAVk",
      "folderTitle": "grafana-operator-system",
      "folderUrl": "/dashboards/f/He5NIuAVk/grafana-operator-system",
      "sortMeta": 0
    }
  ]

This haven't happend before and it didn't on another PR that I just ran so I think this should be okay.
I will merge the PR and if there is some issue after I will look in to it.

authors: NissesSenap gitgaoxiang pb82

repo: grafana-operator/grafana-operator


text:
Property Value Aggregate Query Has Double the Expected Number of Data Points

The following description was taken from 2 comments in https://github.com/grafana/iot-sitewise-datasource/issues/160

I tested the new version (1.9.2) with Grafana version 10.0.0.
With my current setup, I get the following response:

By downloading the data and looking at it, there are duplicates of most of the values. Without knowing, I suspect it is the paginated response that is duplicated.
Using Boto3 - get_asset_property_aggregates I get the expected value of 600 data points.
As the screenshot shows above, the expression fails when using the value aggregates (top right corner), only showing 1 data point. By simply taking the expression query away, the result would be the same as top left corner (as expected).
Similarly, the expression does not get all the values for value history either. Again, I suspect that this is something with pagination/next token, not being able to show all the result.
Please let me know if anything is unclear or you require more information.
Originally posted by @egheie in https://github.com/grafana/iot-sitewise-datasource/issues/160#issuecomment-1592591464

Hi @kevinwcyu, no problem.
Here are the screenshots, starting bottom left, going clockwise. Note: every quadrant will have the same query, just the panel is different. (Either Time series, or Stat with Calculation = Count).
When doing this, I saw that the bottom left Stat was set to Get property value aggregates and not Get property value history. See new screenshot at the bottom, sorry for that.
Screenshots of query editor:
Bottom left

Top left

Top right

Bottom right

Updated screenshot:

Originally posted by @egheie in https://github.com/grafana/iot-sitewise-datasource/issues/160#issuecomment-1594699586

Here's a python script to fetch a count of the data points to compare with the results from the dashboard.
import boto3
from datetime import datetime

client = boto3.client('iotsitewise')

# get asset property values history
# https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/iotsitewise/client/get_asset_property_value_history.html
# may need a paginator if there are more than 20000 data points
response = client.get_asset_property_value_history(
    assetId='1a2b3c4d-5e6f-1a2b-3c4d-5e6f1a2b3c4d', # <--- replace with actual asset id
    propertyId='1a2b3c4d-5e6f-1a2b-3c4d-5e6f1a2b3c4d', # <--- replace with actual property id
    startDate=datetime.fromisoformat('2023-06-13T07:00:00Z'), # <--- set to corresponding from time from the query
    endDate=datetime.fromisoformat('2023-06-21T06:59:59Z'), # <--- set to corresponding to time from the query
    timeOrdering='ASCENDING',
    maxResults=20000
)
print(len(response['assetPropertyValueHistory']))

# get asset property aggregates
# https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/iotsitewise/client/get_asset_property_aggregates.html
agg_paginator = client.get_paginator('get_asset_property_aggregates')
agg_iterator = agg_paginator.paginate(
    assetId='1a2b3c4d-5e6f-1a2b-3c4d-5e6f1a2b3c4d', # <--- replace with actual asset id
    propertyId='1a2b3c4d-5e6f-1a2b-3c4d-5e6f1a2b3c4d', # <--- replace with actual property id
    aggregateTypes=['AVERAGE'],
    resolution='1m',
    startDate=datetime.fromisoformat('2023-06-13T07:00:00Z'), # <--- set to corresponding from time from the query
    endDate=datetime.fromisoformat('2023-06-21T06:59:59Z'), # <--- set to corresponding to time from the query
    timeOrdering='ASCENDING',
    maxResults=250,
)
agg_count = 0
for p in agg_iterator:
  agg_count += len(p['aggregatedValues'])
print(agg_count)

source: gharchive/issue

repo: grafana/iot-sitewise-datasource


text:
Allow tuning of .Values.configValidator.pullPolicy

It would be really nice to be able to tune the pullPolicy of the configValidator pod. Just adding this to the values
{{- with .Values.configValidator.nodeSelector }}
and tweak the template validate-configuration.yaml

this feature will be going away in v2. So I'd say either turn it off with configValidator.enabled=false.
otherwise, if you want to put together a PR, I'd be happy to take a look and merge it in.

It does not worth if it's going away. Is there an ETA for V2?
Thanks

Aiming for a release probably near the end of November, but subject to change.

authors: josemrs petewall


text:
pprof panic on recent toolchains

This simple program panics on recent toolchains
use pyroscope::PyroscopeAgent;
use pyroscope_pprofrs::{pprof_backend, PprofConfig};

fn main() {
    let pprof_config = PprofConfig::new().sample_rate(100);
    let pprof_backend = pprof_backend(pprof_config);

    let pprof_agent =
        PyroscopeAgent::builder("https://asd.net", "qwe")
            .basic_auth("xxx", "xxxx")
            .backend(pprof_backend)
            .build().unwrap();

    let running_agent = pprof_agent.start().unwrap();

    let (add_tag, _) = running_agent.tag_wrapper();

    let _ = add_tag("connections".to_string(), 10.to_string());
    let _ = add_tag("watchers".to_string(), 10.to_string());

    running_agent.stop().unwrap().shutdown();
}

panic:
/home/korniltsev/.cargo/bin/cargo run --color=always --package pg --bin pg
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.06s
     Running `target/debug/pg`
thread 'main' panicked at library/core/src/panicking.rs:221:5:
unsafe precondition(s) violated: slice::from_raw_parts requires the pointer to be aligned and non-null, and the total size of the slice not to exceed `isize::MAX`
stack backtrace:
   0: rust_begin_unwind
             at /rustc/6292b2af620dbd771ebb687c3a93c69ba8f97268/library/std/src/panicking.rs:661:5
   1: core::panicking::panic_nounwind_fmt::runtime
             at /rustc/6292b2af620dbd771ebb687c3a93c69ba8f97268/library/core/src/panicking.rs:112:18
   2: core::panicking::panic_nounwind_fmt
             at /rustc/6292b2af620dbd771ebb687c3a93c69ba8f97268/library/core/src/panicking.rs:122:5
   3: core::panicking::panic_nounwind
             at /rustc/6292b2af620dbd771ebb687c3a93c69ba8f97268/library/core/src/panicking.rs:221:5
   4: core::slice::raw::from_raw_parts::precondition_check
             at /rustc/6292b2af620dbd771ebb687c3a93c69ba8f97268/library/core/src/ub_checks.rs:68:21
   5: core::slice::raw::from_raw_parts
             at /rustc/6292b2af620dbd771ebb687c3a93c69ba8f97268/library/core/src/ub_checks.rs:75:17
   6: <pprof::collector::TempFdArrayIterator<T> as core::iter::traits::iterator::Iterator>::next
             at /home/korniltsev/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pprof-0.12.1/src/collector.rs:225:26
   7: core::iter::traits::iterator::Iterator::fold
             at /rustc/6292b2af620dbd771ebb687c3a93c69ba8f97268/library/core/src/iter/traits/iterator.rs:2587:29
   8: <core::iter::adapters::chain::Chain<A,B> as core::iter::traits::iterator::Iterator>::fold
             at /rustc/6292b2af620dbd771ebb687c3a93c69ba8f97268/library/core/src/iter/adapters/chain.rs:126:19
   9: core::iter::traits::iterator::Iterator::for_each
             at /rustc/6292b2af620dbd771ebb687c3a93c69ba8f97268/library/core/src/iter/traits/iterator.rs:818:9
  10: pprof::report::ReportBuilder::build
             at /home/korniltsev/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pprof-0.12.1/src/report.rs:110:17
  11: pyroscope_pprofrs::Pprof::dump_report
             at /home/korniltsev/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyroscope_pprofrs-0.2.7/src/lib.rs:202:22
  12: <pyroscope_pprofrs::Pprof as pyroscope::backend::backend::Backend>::add_rule
             at /home/korniltsev/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyroscope_pprofrs-0.2.7/src/lib.rs:180:13
  13: pyroscope::pyroscope::PyroscopeAgent<pyroscope::pyroscope::PyroscopeAgentRunning>::tag_wrapper::{{closure}}
             at /home/korniltsev/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pyroscope-0.5.7/src/pyroscope.rs:776:17
  14: pg::main
             at ./src/main.rs:18:13
  15: core::ops::function::FnOnce::call_once
             at /rustc/6292b2af620dbd771ebb687c3a93c69ba8f97268/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread caused non-unwinding panic. aborting.

Process finished with exit code 134 (interrupted by signal 6:SIGABRT)

Looks like it's problem in pprof-rs crate, which won't be fixed any soon as it looks abandoned (last update was almost a year ago). As I understood from googling, the problem has always been there, but started panicking only recently (at rust 1.78.0). So, downgrading may be a workaround, maybe?

https://github.com/tikv/pprof-rs/issues/232

I receive the same error on M1 with pyroscope for Rust on Macos M1
thread '' panicked at library/core/src/panicking.rs:219:5: unsafe precondition(s) violated: slice::from_raw_parts requires the pointer to be aligned and non-null, and the total size of the slice not to exceedisize::MAXstack backtrace: 0: rust_begin_unwind at /rustc/3f5fd8dd41153bc5fdca9427e9e05be2c767ba23/library/std/src/panicking.rs:652:5 1: core::panicking::panic_nounwind_fmt::runtime at /rustc/3f5fd8dd41153bc5fdca9427e9e05be2c767ba23/library/core/src/panicking.rs:110:18 2: core::panicking::panic_nounwind_fmt at /rustc/3f5fd8dd41153bc5fdca9427e9e05be2c767ba23/library/core/src/panicking.rs:120:5 3: core::panicking::panic_nounwind at /rustc/3f5fd8dd41153bc5fdca9427e9e05be2c767ba23/library/core/src/panicking.rs:219:5 4: core::slice::raw::from_raw_parts::precondition_check at /rustc/3f5fd8dd41153bc5fdca9427e9e05be2c767ba23/library/core/src/ub_checks.rs:68:21 5: core::slice::raw::from_raw_parts at /rustc/3f5fd8dd41153bc5fdca9427e9e05be2c767ba23/library/core/src/ub_checks.rs:75:17 6: pprof::addr_validate::validate at /Users/deanhunter/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pprof-0.12.1/src/addr_validate.rs:93:28 7: <pprof::backtrace::frame_pointer::Trace as pprof::backtrace::Trace>::trace at /Users/deanhunter/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pprof-0.12.1/src/backtrace/frame_pointer.rs:114:17 8: perf_signal_handler at /Users/deanhunter/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pprof-0.12.1/src/profiler.rs:354:13 9: ___simple_bprintf note: Some details are omitted, run withRUST_BACKTRACE=fullfor a verbose backtrace. thread caused non-unwinding panic. aborting.

authors: DeanHnter Yerkwell korniltsev

repo: grafana/pyroscope-rs


text:
Error loading: myorgid-simple-panel

I read the grafana documentation and starting with this example and then working my way towards integrating the funnel part but I can't seem to get it working。I restarted the Server when I tried opening this Panel I got an error saying Error loading: myorgid-simple-panel.My grafana version is 6.4.4, node.js version is 12.13.1;How to solve this?

My development environment is Windows x64

Hello,Try npm install before yarn build

I have the same error.
This is what I found in the browser console:
backend.js:6 Error loading panel plugin: myorgid-simple-panel TypeError: r.PanelPlugin is not a constructor
    at Module.eval (module.js:1)
    at n (module.js:1)
    at eval (module.js:1)
    at eval (module.js:1)
    at i (system.js:4)
    at system.js:4
    at system.js:4
    at O (system.js:4)
    at k (system.js:4)
    at system.js:4

Ok, I think you have a problem because you don't have the latest version.
Therefore git pull and try again

Ok, I think you have a problem because you don't have the latest version.
Therefore git pull and try again

Hi Samuel,
I've pulled the latest version and it's still not working.
Still the same Grafana error, and the same console error.
Have you tried building and running it on Grafana?

Yes but I'm on Linux.
You have the same mistake here: https://github.com/grafana/grafana/issues/20338
And the last simple-react-panel pull repair that: https://github.com/grafana/simple-react-panel/commit/ca7f48c685aa94c40eeabf63efbdf5eebe6baa14 (in src/SimplePanel.tsx and src/SimpleEditor.tsx)
Did you install Grafana from the sources?

Yes but I'm on Linux.
You have the same mistake here: grafana/grafana#20338
And the last simple-react-panel pull repair that: ca7f48c (in src/SimplePanel.tsx and src/SimpleEditor.tsx)
Did you install Grafana from the sources?

I'm on the MacOS.
All my files look exactly like how it is in that repair. The "fixes" that the person in the thread you posted were already implemented by me in my files
I installed Grafana through homebrew.

I just got it working. PanelPlugin should be imported from @grafana/ui and not @grafana/data
My old module.ts looked like
import { PanelPlugin } from '@grafana/data';
import { SimpleOptions, defaults } from './types';
import { SimplePanel } from './SimplePanel';
import { SimpleEditor } from './SimpleEditor';

export const plugin = new PanelPlugin<SimpleOptions>(SimplePanel).setDefaults(defaults).setEditor(SimpleEditor);

My new module.ts looks the same, but with the first line replaced to
import { PanelPlugin } from '@grafana/ui'

I just got it working. PanelPlugin should be imported from @grafana/ui and not @grafana/data
My old module.ts looked like
import { PanelPlugin } from '@grafana/data';
import { SimpleOptions, defaults } from './types';
import { SimplePanel } from './SimplePanel';
import { SimpleEditor } from './SimpleEditor';

export const plugin = new PanelPlugin<SimpleOptions>(SimplePanel).setDefaults(defaults).setEditor(SimpleEditor);

My new module.ts looks the same, but with the first line replaced to
import { PanelPlugin } from '@grafana/ui'

I just got it working. PanelPlugin should be imported from @grafana/ui and not @grafana/data
My old module.ts looked like
import { PanelPlugin } from '@grafana/data';
import { SimpleOptions, defaults } from './types';
import { SimplePanel } from './SimplePanel';
import { SimpleEditor } from './SimpleEditor';

export const plugin = new PanelPlugin<SimpleOptions>(SimplePanel).setDefaults(defaults).setEditor(SimpleEditor);

My new module.ts looks the same, but with the first line replaced to
import { PanelPlugin } from '@grafana/ui'

Module '"../node_modules/@grafana/ui"' has no exported member 'PanelPlugin'.
??

I just got it working. PanelPlugin should be imported from @grafana/ui and not @grafana/data
My old module.ts looked like
import { PanelPlugin } from '@grafana/data';
import { SimpleOptions, defaults } from './types';
import { SimplePanel } from './SimplePanel';
import { SimpleEditor } from './SimpleEditor';

export const plugin = new PanelPlugin<SimpleOptions>(SimplePanel).setDefaults(defaults).setEditor(SimpleEditor);

My new module.ts looks the same, but with the first line replaced to
import { PanelPlugin } from '@grafana/ui'

I modified the mudule.ts according to your way,it still not working, I input 'yarn dev',got an error "/@grafana/ui"' has no exported member 'PanelPlugin'."

Sorry guys. I forgot to share my full module.ts file.
You need to add // @ts-ignore on the first line of your module.ts file.
So the final version looks like:
// @ts-ignore
import { PanelPlugin } from '@grafana/ui';
import { SimpleOptions, defaults } from './types';
import { SimplePanel } from './SimplePanel';
import { SimpleEditor } from './SimpleEditor';

export const plugin = new PanelPlugin<SimpleOptions>(SimplePanel).setDefaults(defaults).setEditor(SimpleEditor);

That should solve your problem.
Don't ask me why that works though.

I also can't get this to work.
The plugin shows up in the panel list by clicking on it gives the error loading: myorgid-simple-pane
the console complains:
keybindingSrv.ts:20 Error loading panel plugin: myorygid-simple-panel SyntaxError: Unexpected token '<'
    at eval (<anonymous>)
    at st (system.js:4)
    at system.js:4
    at system.js:4
    at O (system.js:4)
    at k (system.js:4)
    at system.js:4

i solved the problem by upgrading grafana to 6.5.x .

In any case, there is a lot of mismatches between alpha plugins (i.e. piechart alpha panel) in Grafana core and this template. I think it would be reviewed and to propose an unified usage of @grafana libraries.

if this still exists... post again -- my guess is the plugin was not built

authors: efvhi gretamosa karlie93 manu2194 ryantxu sbelondr speg

repo: grafana/simple-react-panel


text:
Add func (seg MediaSegment)String()

related #98

Coverage decreased (-5.05%) to 66.278% when pulling 178325b3c3cfb74ad192bc583db21a09792757f0 on keizo042:media_segment_string into d137fcd412b91fee5939a56a9d0d5a83c81d39d3 on grafov:master.

I'm concerned that we'd now have two different methods to write a segment.
Can we not move the following to an unexported function, which takes a *m3u8.MediaSegment and *bytes.Buffer and writes to the provided buffer?
https://github.com/grafov/m3u8/blob/master/writer.go#L483-L600
As long as performance isn't drastically affected.

Coverage decreased (-4.7%) to 66.589% when pulling 9177d906dd8eefa5c7852b4d3725e4091a93af94 on keizo042:media_segment_string into d137fcd412b91fee5939a56a9d0d5a83c81d39d3 on grafov:master.

Coverage decreased (-0.5%) to 70.83% when pulling dde4c977e438e088aad4f7f4c85d5c0623ef3e24 on keizo042:media_segment_string into d137fcd412b91fee5939a56a9d0d5a83c81d39d3 on grafov:master.

@bradleyfalzon
Thank you for your review.
I'd fix that the functions writing XXX use provided buffer and replace duplicated code to unexported function.

Thanks @keizo042 that change is better, but there's still some duplication of the if statements. We've created a few new unexported functions, which is good, but I'd think there should just be one function that both MediaSegment.String() and *MediaPlaylist.Encode() call.

@bradleyfalzon

I'd think there should just be one function that both MediaSegment.String() and *MediaPlaylist.Encode() call.
Unless there's a specific reason we can't do that?

I agree but there is two difference.
in (p *MediaPlaylist) String,  writing m3u8.Map and m3u8.Key  depends on previous  media segments.
but in the function I request, I think it is good to write buffer if they exist.
In addition, (p *MediaPlaylist) String() have previous durations cache.
but (seg MediaSegment) String() is stateless.
I'd like to remove caching procedure in (seg MediaSegment) String()`.
so it needs writeKey and writeMap.
if I shoud not break order of segments attribute, writeSCTE also.
I feel need to create unexported function as rest part of writing media segment in order to remove duplicated code.
I don't have good idea how it maanges caching yet.

depends on previous media segments.

Ah yes, I see. This is unfortunate.

have previous durations cache

Yeah, so this is so for very large playlists, we don't continue to call the intensive strconv.FormatFloat.
I then understand why you've chosen this method, but I do prefer if we could remove the duplication completely. I don't mind duplicate code, but there's a lot of logic here that's being duplicated and that's what concerns me.
What if there was a function like

// writeSegment writes a string representation of seg to buf.
//
// durationCache is required to reduce the number of calls to repetitive strconv formats.
// If playlist is non-nil, additional context is derived from the playlist.
func writeSegment(seg MediaSegment, buf bytes.Buffer, durationCache map[float]string, playlist *MediaPlaylist, buf bytes.Buffer)

Then the same if statements that used information from the playlist would first check if playlist is non-nil.
-if p.Map == nil && seg.Map != nil {
+if p != nil && p.Map == nil && seg.Map != nil {

Or similar? I'm not 100% for my suggestion, just asking your thoughts.

That's good idea.
I'd like to show all infomation when the context is not provided.
I think better like this.

func (seg MediaSegment) write(buf bytes.Buffer, p *MediaPlaylist, durationCache map[string]float
) {
...
      if p != nil {
                if p.Map == nil && seg.Map != nil {
                        writeMap(buf, seg.Map)
                }
        } else {
                writeMap(buf, seg.Map)
        }
...
        if p != nil {
                // original caching and conversion
        } else {
                buf.WriteString(strconv.FormatFloat(seg.Duration, 'f', 3, 32))
        }
...
}

Coverage increased (+0.3%) to 71.644% when pulling 625523432ce599f5375de7ca5912c44bd8c72db0 on keizo042:media_segment_string into d137fcd412b91fee5939a56a9d0d5a83c81d39d3 on grafov:master.

This is looking good to me I think.
Could you run the benchmarks before and after to check for performance regressions?

benchmark resutls
Env

CentOS 7.4
go version go1.8.3 linux/amd64

result
[m3u8]$ go test -bench=.
BenchmarkDecodeMasterPlaylist-12           50000             29740 ns/op
BenchmarkDecodeMediaPlaylist-12              100          21899250 ns/op
BenchmarkEncodeMasterPlaylist-12         1000000              1426 ns/op
BenchmarkEncodeMediaPlaylist-12              200           6463614 ns/op
PASS
ok      github.com/grafov/m3u8  7.455s

[m3u8]$ git checkout media_segment_string
Switched to branch 'media_segment_string'
[m3u8]$ go test -bench=.
BenchmarkDecodeMasterPlaylist-12           50000             29644 ns/op
BenchmarkDecodeMediaPlaylist-12              100          21823718 ns/op
BenchmarkEncodeMasterPlaylist-12         1000000              1420 ns/op
BenchmarkEncodeMediaPlaylist-12              200           6974774 ns/op
PASS
ok      github.com/grafov/m3u8  7.569s

only Encode MediaPlaylist benchmark
[m3u8]$ git checkout master
Already on 'master'
m3u8]$ go test -bench=BenchmarkEncodeMediaPlaylist
BenchmarkEncodeMediaPlaylist-12              200           6456721 ns/op
PASS
ok      github.com/grafov/m3u8  2.000s

[m3u8]$ git checkout media_segment_string
Switched to branch 'media_segment_string'

[m3u8]$ go test -bench=BenchmarkEncodeMediaPlaylist
BenchmarkEncodeMediaPlaylist-12              200           6951293 ns/op
PASS
ok      github.com/grafov/m3u8  2.131s
[m3u8]$

well... I think we prefer that peformance regression is under 0.1sec.
I take inlining writeSCTE and invesitage in detail.

authors: bradleyfalzon coveralls keizo042

license_source: bigquery


text:
Question: would it be possible to use extensions

Having annotation is quite small code change. But would it be possible to have extension which accepts an object and saves/load it from parcel.
At least current API could be improved with extension to avoid using util classes

What do you mean by extensions? The next feature I'm thinking of adding is a way for apps to customize how a type should be parceled. E.g. by default a date is added to a parcel via serialization, but a more efficient way would be to read/write a long value directly to the parcel. Would this cover what you are after?

I was thinking about better API. Instead of:
val example = Example(42)
val parcel = ExampleParcel.wrap(example)

// e.g. use in a bundle
someBundle.putParcelable("example", parcel)

something like:
val example = Example(42)
example.putToBundle(someBundle)

Oh extension methods. I'm not sure how you can do this since I'm generating java code. Do you know if it's possible?

I've posted a question on the Kotlin forums. https://discuss.kotlinlang.org/t/annotating-static-java-methods-so-kotlin-can-pick-them-up-as-extension-functions-of-a-type/1431

Unfortunately this is not supported by Kotlin yet (see linked thread)

Actually, I may have dismissed this too early. I'll investigate generating a kotlin class with the extension methods alongside the other generated classes. Not sure it's possible yet though.

Could also do this with a paperparcel-kotlin library that is just a thin shim on top of paperparcel that adds the extension methods.

That is a good idea. I wanted to try it again after this pull request is released and see if the problem is fixed first, because it sounds like it should fix what I was seeing.

:+1:

Closing due to new APIs replacing the need for extensions. The wrappers are more hidden to the library consumer now.

authors: edenman emartynov grandstaish

repo: grandstaish/DataParcel


text:
All get lost on updates

In every update all I had saved its lost.
Is there I way I can recover it all? or don't overwrite by updates,
its a nightmare!!!!!

Thanks @kikoseijo ! We did put a warning into the release notes about exactly this. Did this happen to you through auto update? You can install an older release (<1.5) and all the data should still be there!

Hey @timsuchanek,
Yes its the auto update app for Mac, been happening on the last 3-4 updates, yes.
Lets hope it will settle eventually... thanks for support,

authors: kikoseijo timsuchanek

repo: graphcool/graphql-playground

license: MIT


text:
custom scalar

Hi All
This is more of a question than an issue. How do I create a custom scalar with graphql-yoga? I have attempted to use GraphQLScalarType from 'graphql' along the following lines:
import { GraphQLScalarType } from 'graphql'
//...
const MyScalar = new GraphQLScalarType({
 //...
})
//...

const resolvers = {
  Query: {
    //...
  },
  MyScalar: MyScalar
}

But the scalar value returns as null in all queries.

I made it work with something along the lines of this:
const NLString = new GraphQLScalarType({
  name: 'NLString',
  description:
    'New line terminated string',
  //invoked to parse client input that was passed through variables.
  //takes a plain JS object.
  parseValue(varaible){
    return varaible.replace(/\n$/, "")
  },
  //invoked to parse client input that was passed inline in the query.
  //takes a value AST.
  parseLiteral(literal) {
    return literal.value.replace(/\n$/, "")
  },
  //invoked when serializing the result to send it back to a client.
  serialize: function(value){
    return value + "\n"
  }
})

//...

const resolvers = {
  Query: {
    //...
  },
  NLString
}

Also, for completeness, here's are some example graphql queries:
query {
  post(title:"example\n"){
    title
    body
  }
}

triggers parseLiteral(literal) with literal.value="example\n"
query Posts($title: NLString) {
  post(title:$title){
    title
    body
  }
}

with:
{
  "title": "example\n"
}

triggers parseValue(varaible) with varaible="example\n"

repo: graphcool/graphql-yoga


text:
carbon-cache memory leak when put under LB

Recently we put our  graphite service under Load Balance, then seeing lots of log as bellow, the IP address here are from LB connection, carbon-cache process memory increasing slowly and finally OOM,
suspect the LB short connection which making carbon-cache memory leak.
n.
09/09/2018 05:06:34 :: [listener] MetricLineReceiver connection with 192.117.87.3:41731 lost: Connection to the other side was lost in a non-clean fashio
n.
09/09/2018 05:06:34 :: [listener] MetricLineReceiver connection with 192.117.87.131:8879 lost: Connection to the other side was lost in a non-clean fashi
on.
09/09/2018 05:06:34 :: [listener] MetricLineReceiver connection with 192.97.72.130:42744 lost: Connection to the other side was lost in a non-clean fashi
on.

@rmrf : It can be non-related carbon memory can grow above the limit if not configured properly.
What's your metric flow?
How many carbon-caches are you running?
Could you please share carbon config?

Are you sure it is caused by the lost connections? Can you reproduce this on a carbon with LB without any actual metrics? Which Twisted and Python version are you using?

authors: deniszh piotr1212 rmrf

repo: graphite-project/carbon


text:
Remove /opt/graphite prefix and use setuptools

See https://github.com/graphite-project/carbon/pull/835 for reasoning

I'm not finished yet but made some changes to the docs which I would like to get some feedback for. I've tried to simplify the docs, IMO there were too much separate pages which you had to jump back and forward to.
I've changed the default install (settings.py) so that running collectstatic is not needed. The static files can be served directly from the app with whitenoise. Serving from whitenoise should be fast enough for most installations. this eliminates the need for configuring the static dir in the webserver (simplifies installation). From what I've read the whole purpose of collectstatic is for organisations which run multiple django apps and have separated their static files from code (in repo), so that they can update static files without having to deploy code and vice versa. As graphite's static files haven't changed in years and they are in the code repo I don't see a point to require collectstatic in the default install. Users can still run collectstatic if they want/need.
please ignore the GRAPHITE_ROOT commit, ill remove it later.

I think a rebase went a bit wrong, you ended up with a copy of the commit "fix dashboard graph metric list icon paths with URL_PREFIX" from the master branch
in master: 0a037db4b2d864734e14dd6302bc71194f53e8d3
in this branch: 1ba4da55c08035cccfcdaae2220f8d384dbd1929

I think a rebase went a bit wrong, you ended up with a copy of the commit "fix dashboard graph metric list icon paths with URL_PREFIX" from the master branch
in master: 0a037db
in this branch: 1ba4da5

I think I merged instead of rebased. Anyway, cleaned up now.

All looks good to me.
I had another thought about storage dirs ... I think the original idea behind using /opt/graphite is those storage and log dirs, which would be awkward in the python site-packages directory. Maybe the thing to do is divorce them from the graphite application root, and default to /opt/graphite/storage and /opt/graphite/log regardless of the install prefix? And not mention them in setup.py at all? I suppose the downside is they would not be created by install. Just an idea - I suppose I always customize these dirs anyway.

good point. I'll have a look. But busy at the moment with more higher prio stuff.

This is a big painful change, but I think it's still relatively important. Just sayin' to appease the stale bot :)

If this will fix the pip install, can we get it merged?

Unfortunately, it's not that easy. That would break backward compatibility,
and need more changes in carbon. Also, not sure if that fix issue too :/
ср, 19 июл. 2023 г., 18:36 Adam @.***>:

If this will fix the pip install, can we get it merged?
—
Reply to this email directly, view it on GitHub
https://github.com/graphite-project/graphite-web/pull/2409#issuecomment-1642409417,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJLTVRNEHAUAT6W7NWQH7LXRAEH3ANCNFSM4GOVTH5Q
.
You are receiving this because your review was requested.Message ID:
@.***>

authors: adamboutcher deniszh piotr1212 ploxiln

repo: graphite-project/graphite-web


text:
[Bug] where or operation error structure

Bug report
Structure  ... where: { or: { xxx_contains_nocase: "xxx", xxx_contains_nocase: "xxx"}} ... query is not work
... or: { xxx_contains_nocase: "xxx", xxx_contains_nocase: "xxx"} ... query work
Relevant log output
Invalid value provided for argument `where`: Object({\"or\": Object({\"name_contains_nocase\": String(\"xx\"), \"symbol_contains_nocase\": String(\"xx\")})})

IPFS hash
No response
Subgraph name or link to explorer
https://api.thegraph.com/subgraphs/name/uniswap/uniswap-v2/graphql?query=query+MyQuery+{
++tokens(where%3A+{or%3A+{name_contains_nocase%3A+"xx"%2C+symbol_contains_nocase%3A+"xx"}})+{
++++name
++++symbol
++}
}
Some information to help us out

[ ] Tick this box if this bug is caused by a regression found in the latest release.
[ ] Tick this box if this bug is specific to the hosted service.
[X] I have searched the issue tracker to make sure this issue is not a duplicate.

OS information
Windows

hi @huazhuangnan I think you need the following query:
query MyQuery {
  tokens(
    where: {or: [{name_contains_nocase: "xx"}, {symbol_contains_nocase: "xx"}]}
  ) {
    name
    symbol
  }
}

repo: graphprotocol/graph-node


text:
Not populated metrics for indexer service,  version 0.20.4

Some metrics are missing from indexer service (not populated) such as indexer_service_queries_ok  or indexer_service_queries_total
Version:
graphval@node023:~/indexer/packages/indexer-cli/bin$ graph-indexer-service --version
0.20.4
However, I'm not sure if MIP send queries excactly to my indexer.

the issue is solved when queries started to arrive to index-service

repo: graphprotocol/indexer


text:
Add a protocolNetwork column to Rules and Actions table

Depends on #650.

Create a migration with these steps:

Alter the tables: indexingRules and actions:

add protocol_network column, which defaults to null

Resolve every row protocol_network (There can be no nulls left behind!)

This step can be difficult because we need to consider edge cases, such as when an indexer has allocations in the same subgraph for both layers.
derive protocol_network for every rule and action (only need to do for status = queued or approved)

gather rules, active allocations (across protocol networks), and actions: matching rules to active allocations to identify the network

Alter the tables again to add a NOT NULL

Add the protocolNetwork field to Rules and Actions ORM models.

Also, add it to non-ORM types, like SubgraphDeployment.
At this point, the compiler will surface every usage of the new field, we might make some wild discoveries.

Update the indexer-cli sub-commands to require a protocol network identifier.

indexingRules

add the option to specify the protocol network (optional). If not specified, the value will resolve to the default rule
example: indexer rules set <DeploymentId> protocolNetwork homestead allocationAmount 10000

actions

update actions queue commands to require protocol network
example: indexer actions queue allocate QmYN4ofRb5CUg1WdpLhhNTVCuiiAt29hBKGjTnnxYh9zYt homestead 1000

allocations

update create command

indexer allocations create <deployment-id> <protocol-network> <amount> <index-node>
NOTE: validate that allocation ids are unique per-protocol network; if not, we may need to require protocol-network for allocations close and allocations reallocate and allocations get

Update get command

support filtering by protocol_network

disputes

Update get command

Support filtering by protocol_network

cost

OPEN QUESTION: do we continue to use just deployment_id as the primary key, or do we also update to include the network?

To state that another way: do we need cost models for each deployment to be different per network?
If we do: we’ll need to update the set, get, and delete commands also to require protocol_network arg

Fixed by #668


text:
Use lodash-es

Instead of using individual lodash packages using lodash-es would be a better "es module" player and work with browser playground environments like google's playground elements. Also being an es module package would allow any build tools/bundlers to treeshake as needed.

Using ramda instead since it supports both es and cjs modules. Tested with playground-elements and ramda is good to go. The original motivation behind this issue was to move toward a more compatible module that could support the "es-only" world without bundling, etc, and ramda does the trick.

repo: graphql-mocks/graphql-mocks


text:
migrate README docs to Sphinx/RTD

Following on from #1313, I'd like to continue migrating to Sphinx for documentation, turning next to the installation and configuration instructions in the README. The purpose is to give ourselves a more powerful documentation system than GitHub markdown files and wiki pages. Sphinx enables us to practice literate programming, pulling documentation from docstrings in our source code. I'm using Sphinx successfully on these other libraries: algorithm.py, dependency_injection.py,environment.py, filesystem_tree.py, and postgres.py. We're also moving to Sphinx for the Aspen docs.
There's a sphinx-autobuild package that looks promising in terms of streamlining the doc workflow (auto-rebuild and live-reload). There's some potential hiccups, though, around both Mac OS and VirtualBox (i.e., Vagrant). See https://github.com/GaretJax/sphinx-autobuild/issues/6. So we'll have to figure out the best workflow.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Closing in light of our decision to shut down Gratipay.
Thank you all for a great run, and I'm sorry it didn't work out! 😞  💃

license: mit


text:
chore: cci update

fix circleci config

:tada: This PR is included in version 1.2.0 :tada:
The release is available on:

1.2.0
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.2.0 :tada:
The release is available on:

1.2.0
GitHub release

Your semantic-release bot :package::rocket:

authors: graviteeio jhaeyaert

repo: gravitee-io/gravitee-policy-json-xml


text:
rustc: add manifest so we can install with cargo

Depends on #1149

Is this still part of the cargo plan? Do you still want it merged?

Yes, this is dead now.

authors: brson elly

repo: graydon/rust


text:
Spaces in keys break zabbix-sender

Here is an example. I'm simulating the parsing of the input from pm2-zabbix --monitor, which produces a key-value stream which is parsed by zabbix-sender and sent. I'm fetching just one row from this stream, and sending to zabbix:
echo "xxxxx-be-preprod01 pm2.processes[xxxxx Frontend-0,cpu] 90"  | zabbix_sender -vv --config /etc/zabbix/zabbix_agentd.conf -s hostname --input-file -
zabbix_sender [25699]: DEBUG: answer [{"response":"success","info":"processed: 0; failed: 1; total: 1; seconds spent: 0.000028"}]
info from server: "processed: 0; failed: 1; total: 1; seconds spent: 0.000028"
So, if there are spaces in pm2 process, the server fails to process the monitor part. The "discover" part is working, though, because if we enclose the key with double quotes, it goes through:
echo "xxxxxx-be-preprod01 "pm2.processes[xxxxx Frontend-0,cpu]" 90"  | zabbix_sender -vv --config /etc/zabbix/zabbix_agentd.conf -s hostname --input-file -
zabbix_sender [25131]: DEBUG: answer [{"response":"success","info":"processed: 1; failed: 0; total: 1; seconds spent: 0.000083"}]
info from server: "processed: 1; failed: 0; total: 1; seconds spent: 0.000083"

This is going to be addressed in PR #31.


text:
下载不了FREEBROWSER

HI.
我下载不了FREEBROWSER，下载失败。无论是https://raw.githubusercontent.com/greatfire/z/master/FreeBrowser-1.1.apk还是https://raw.githubusercontent.com/greatfire/z/master/FreeBrowser-1.0.apk都下载失败（我浏览器是翻墙状态的），怎么回事？
可否把FreeBrowser-1.1.apk上传到某个网盘，贴出下载地址供人下载呢？
我找不到其他地方提交问题，只好在此提交，请见谅。

@luckypoem，这位已经通过邮箱反馈了，此issue申请关闭

网盘下载地址
FreeBrowser-1.1.apk
https://mega.co.nz/#!vs0QAToA!4ZqFmlvaevtWj4NDoFZzy_cqCTtnBYU-sWHcOelFk8Q

authors: ghfdbk luckypoem percyalpha

repo: greatfire/website-mirror-by-proxy


text:
Improve test_project

See bak2 archive (requirements.txt, etc.)

Solved in commits:
commit 72be744a4c301f66c9c6c73ee6691b6ea60c491e
Author: Max Arnold arnold.maxim@gmail.com
Date:   Mon Dec 28 13:13:45 2015 +0700
Drop LazyProgressBar, the patch is accepted upstream as of version 3.5.2

commit 489dc0eb6c01436798778af347ce92c0bc371011
Author: Michael Gulev greenday2.gd@gmail.com
Date:   Fri Dec 25 18:39:52 2015 +0700
travis: remove obsolete vendor directory from pep8 ignore list.

test_project test.py: Remove obsolete in django 1.9 django.utils.unitest and use unittest.

commit c53eec572c5ef13dfb5298381703ea47aef2cf6e
Author: Max Arnold arnold.maxim@gmail.com
Date:   Thu Dec 10 20:56:55 2015 +0700
fix docs

commit 1632113183b98f1122c23032300044deec271dd7
Author: Max Arnold arnold.maxim@gmail.com
Date:   Thu Dec 10 20:56:32 2015 +0700
write proper docs/requirements.txt

commit 94394148b78b1fe5b94d197e5dc8ea21db17eef6
Author: Max Arnold arnold.maxim@gmail.com
Date:   Thu Dec 10 20:56:00 2015 +0700
update test_project to look like it was created using django 1.9

commit cbd2b0cad537216a8cae96ec21e9abdbfd74e808
Author: Max Arnold arnold.maxim@gmail.com
Date:   Thu Dec 10 20:20:43 2015 +0700
prettify test_project requirements.txt

commit 7b40098719832e41bc90da3804b17595ad0d7a70
Author: Michael Gulev greenday2.gd@gmail.com
Date:   Thu Dec 10 11:25:46 2015 +0700
Change order of dependecy and up django version to 1.9 in requirements.txt

commit 3db5243edab4a2e42ea00c95217b2109cc10e383
Author: Michael Gulev greenday2.gd@gmail.com
Date:   Thu Dec 10 11:23:30 2015 +0700
Remove pl, abbr translation and add ru translation. Make ready contrib to django 1.9

commit 7903dd202ee32d265f1932665a40a8a44cf94c0f
Author: Michael Gulev greenday2.gd@gmail.com
Date:   Tue Dec 1 22:35:01 2015 +0700
Replace vendor/progressbar with progressbar2

commit 47837033cb9301e5e248871394dc0ffc33db21d8
Author: Michael Gulev greenday2.gd@gmail.com
Date:   Sun Nov 22 02:23:00 2015 +0700
Add loggers to settings.py

commit 698ceb50d3c32ca30e95555e57a1b69254d6fe4f
Author: Michael Gulev greenday2.gd@gmail.com
Date:   Sun Nov 22 02:21:44 2015 +0700
Remove South migrations.

commit a7032c1a6dd036d66a6fa0c6199d9e11eaf87f3b
Author: Michael Gulev greenday2.gd@gmail.com
Date:   Sun Nov 22 01:18:50 2015 +0700
Upgrade requirements in test_project

commit 16e47de2cf8c3711dbc38ec6026e4c012b4e60f1
Author: Michael Gulev greenday2.gd@gmail.com
Date:   Mon Nov 9 03:50:25 2015 +0700
New test_project on Django 1.9

commit d2aee99926739ee0e1605dfdcb88b4c0b29bc3b6
Author: Michael Gulev greenday2.gd@gmail.com
Date:   Mon Nov 9 01:40:58 2015 +0700
Remove unnecessary files in test project. Add requirements.txt

Closing,

Closed in
https://github.com/greenday2/django-cities-light/commit/d2aee99926739ee0e1605dfdcb88b4c0b29bc3b6

Ну всю портянку то не обязательно :)


text:
question: documentation regarding API keys is a bit sparse

I added an API key from the auth portal settings page at /settings, but now what?
I passed it as a bearer token a la Authorization: Bearer API_KEY, but that does not seem to work.
The only doc page that mentions API keys is this one: https://authp.github.io/docs/authorize/basic_api_key_auth
I have added with api key auth portal myportal realm local to my policy.
Is there something obvious I'm missing here? Or am I just not understanding what purpose API keys are supposed to serve?
My goal is to make a never expiring API key that I can use to give external services access to my services behind the authorize directive.
Thanks in advance, this project is great @greenpau.

@jariz , please share your config.
it is not “authorization Bearer”. Rather, pass X-API-Token header with the value of the key you’d created

@jariz , let’s keep it open. Will address it next week

@jariz , please help promote this project … if you like of course 😃

authors: greenpau jariz

repo: greenpau/caddy-security


text:
ActiveAdmin::Comment doesn't pick up ActiveRecord::Base.table_name_prefix

(Rails 3.0.7, ActiveAdmin 0.2.2)
The table_name property of ActiveAdmin::Comment is set before the configuration in application.rb is read and before Activerecord::Base is able to deal out pre- and suffixes for table names. Because of the load order of gems and application configuration this patch does not work:
#comments/comment.rb
class Comment < ActiveRecord::Base
  #self.table_name = "active_admin_comments"
  self.table_name = ActiveRecord::Migrator.proper_table_name("active_admin_comments")
  # ... more code ...
end

A simple workaround is:
#config/initializers/some_initializer.rb ,
ActiveAdmin::Comment.table_name = ActiveRecord::Migrator.proper_table_name(ActiveAdmin::Comment.table_name)

Is it possible to load ActiveAdmin::Comment more lazily? Then the first solution would work.

+1

Just as a side note, is it possible to completely disable the comments when using rails g active_admin:install ?
Because some of the solution here works fine if you don't have code already, if you're adding activeadmin after you created your rails project you will be face with namespace collision (Comment)

authors: davidmathei pothibo


text:
Refresh methods hangs with WPF application but not with .Net Core.

Describe the bug
To Reproduce
Hi! Playing around with your library and cannot figure out why Refresh method hangs when called from WPF app and not from .NET Core app.
I have 3 projects in a soluction:

TrelloHelper.Library: A .NET Standard Library (2.0), referencing Manatee.Trello 3.2.1 and dependencies (Json and WebApi)
TrelloHelper.ConsoleApp: A .NET Core 2.0 Console, referencing TrelloHelper.Library
TrelloHelper.WinApp: A .NET Framework 4.6.1 WPF Application referencing TrelloHelper.Library

At the TrelloHelper.Library I have a simple method to connect to Trello, get a board and enumerate it's lists. Code bellow:
        public void TestTrelloConnection(string output)
        {
            string s;
            var stb = new StringBuilder();
            var factory = new TrelloFactory();
            var board = factory.Board(boardDEV);
             board.Lists.Refresh();

            s = $"Board: {board}";
            stb.AppendLine(s);
            Console.WriteLine(s);
            foreach (var list in board.Lists)
            {
                s = $"   {list}";
                stb.AppendLine(s);
                Console.WriteLine(s);
            }
            stb.AppendLine(s);
            Console.WriteLine();

            s="Connection OK!";
            stb.AppendLine(s);
            Console.WriteLine(s);

            output = s;
        }

At the TrelloHelper.ConsoleApp, I have the following code, that works perfectily:
        static void Main(string[] args)
        {
            string s = "" ;
            TrelloHelperLib.TrelloHelper  tr;
            tr = new TrelloHelperLib.TrelloHelper();
            Console.WriteLine("Connecting to trello...");
            tr.TestTrelloConnection(s);
            Console.WriteLine(s);
            Console.ReadLine();
        }

At  TrelloHelper.WinApp, I have a button that calls the following method. But it does not work, hanging at the line "board.Lists.Refresh();" inside the method TestTrelloConnection :
        private void btTestarConexao_Click(object sender, RoutedEventArgs e)
        {
            string s = "";
            tr.TestTrelloConnection(s);
            MessageBox.Show(s);
        }

I don't know if it is a bug or if I'm doing something wrong using async/await in WPF Application ...
Expected behavior
I expected that the behavior would be the same at the .net core console and the .net wpf app.
Desktop (please complete the following information):

OS: Windows 10 Pro
.Net Target 4.6.1, Core 2.0 e Standard 2.0
Version: Manatee.Trello 3.2.1, ManateeJson 2.3.0 and Manatee WebApi 2.0.3 (all using .net standard 2.0)
Visual Studio Community 2017 15.7.3

Additional Information.
Your project is awesome. Thanks!

Thanks for reporting this. I can see that one problem is the async/await usage, but surprised that the console app works.
I'm on my phone right now, though. I'll update later today after I can do some testing.

@rtrianiguerra does this help?  Are you still experiencing issues?

Yes, @gregsdennis! You put me on the track! I've gone back to the C#'s book to review tasks/await/async, strugglered a little, but got it working!
Thanks a lot!
Now I'll begin to make something useful to publish on GitHub!
These are the revised methods:
Library
  public static async Task<string> TestTrelloConnection()
       {
           string s;
           var stb = new StringBuilder();
           var factory = new TrelloFactory();
           var board = factory.Board(boardDEV);
           await board.Lists.Refresh();

           s = $"Board: {board}";
           stb.AppendLine(s);
           foreach (var list in board.Lists)
           {
               s = $"   {list}";
               stb.AppendLine(s);
           }
           stb.AppendLine(s);

           s = "Connection OK!";
           stb.AppendLine(s);

           return stb.ToString();
       }

ConsoleApp:
    class Program
    {
        static void Main(string[] args)
        {
            try
            {
                Test().Wait();
            }
            catch (Exception ex)
            {
                Console.WriteLine(ex.ToString());
            }
            Console.ReadLine();
        }

        static private async Task Test()
        {
            Console.WriteLine("Connecting Trello...");
            var s = await TrelloHelperLib.TrelloHelper.TestTrelloConnection();
            Console.WriteLine(s);
        }
  }

WPFApp :
        private async void btTestarConexao_Click(object sender, RoutedEventArgs e)
        {
            var s = await Task.Run(() =>
                TrelloHelperLib.TrelloHelper.TestTrelloConnection());
            MessageBox.Show(s);
        }

That's a lot better. Just remember that async void should only ever be used for event handlers. Outside of that, you should always return a task.

authors: gregsdennis rtrianiguerra


text:
Day 7 - Wrong variable name in List Pagination paragraph

Close to the end of the paragraph there is this text.
We added page in the URL path and defined default value, in case when page is not defined in the URL (ex: /category/design). Variable $path is added in arguments of the method. It will be injected automatically by name in path. Also we need parameter max_jobs_on_category and getParameter methods to access it. That’s why this controller extends now Symfony\Bundle\FrameworkBundle\Controller\Controller but not Symfony\Bundle\FrameworkBundle\Controller\AbstractController.
Shouldn't it be the $page variable?

@gracoes yes, you are right. Fixed in PR #40. Thank you for reporting :+1:

authors: gracoes gregurco

repo: gregurco/jobeet-tutorial


text:
Another Strange Problem

I'm not sure why, but the following line:
const defaultEntityMap = require('./default-entity-map');
doesn't work when compiling with Angular/Webpack.  The implicit .json extension isn't recognized, and  I'm not sure why, since it is using node.
Would it be possible to add the .json to your code base, by any chance? I'm trying to avoid having a separate copy of the code just to allow this to work.
Thanks very much for this module.

Hrm, using this project with WebPack has been working for me. Looking at my config, I have .json in my resolve.extensions:
extensions: ['.js', '.json', '.ts', '.tsx'],

Have you tried adding that?

authors: greim queejie

repo: greim/html-tokenizer


text:
Published to Rubygems.

I'm very impressed with this implementation and looking forward to using it my own project. I notice that you have contributed some great code clean up to the originally published gem.
Will these changes be contributed back to a new version of the published 'secretsharing' gem or will they remain on your fork? I'm just trying to figure out the best way to get your latest code into my project.
Thanks!
Andy

FYI, version 1.0.0 of the gem has been released to rubygems. Please let me know if you see any issues.
https://rubygems.org/gems/secretsharing
:-)

authors: a-bash grempe

repo: grempe/secretsharing


text:
Bug fix where isnan  template specifier causes compilation errors

Bug fix where isnan  template specifier causes compilation errors, fixed it by removing the template specifier.

Thanks for spotting! I didn't get an error compiling on clang v12.0 on MacOS.

authors: grepthat victorjarlow

repo: grepthat/libOpenDRIVE


text:
Give the ability to bid on EOS premium names (Name Action)

It would be fantastic to let your userbase bid on premium names. It would give much value to EOS to give the oportunity to MORE users to bid on names. I am sure many that would not vote will do if they find it easy from a allready installed wallet.

Tentatively slating this for the 0.6.x milestone, couple versions out still. There's been an incredible demand for account creation and account permissions, which will be the two builds between now and then.

authors: aaroncox liondani

repo: greymass/eos-voter


text:
Timestamp issue on ERCOT SPP data pull?

When I run the example "Retrieving data in local time", I still seeing the timestamp in UTC... It also looks like it isn't lining up with the ERCOT data that I am finding on the website.

Or the data are 4 hours off?

it looks like the time zone conversion isn't happening correctly and the date is staying in utc.
what version of the grid status client library are you using?
>>> import gridstatusio
>>> import pandas
>>> gridstatusio.__version__
'0.4.0'
>>> pandas.__version__
'2.0.1'

Here is what I have up and running in this environment
￼
Joshua Rhodes

On Aug 22, 2023, at 11:25 AM, Max Kanter @.***> wrote:
it looks like the time zone conversion isn't happening correctly and the date is staying in utc.
what version of the grid status client library are you using?

import gridstatusio
import pandas
gridstatusio.version
'0.4.0'
pandas.version
'2.0.1'
—
Reply to this email directly, view it on GitHub https://github.com/gridstatus/gridstatusio/issues/16#issuecomment-1688539078, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZQFTEPFBCBQESL64VFSVTXWTMO5ANCNFSM6AAAAAA3Y6XDD4.
You are receiving this because you authored the thread.

Here is what I have:

thanks! i was able to reproduce and fix the error when I downgraded to that version of pandas.
just  released version 0.5.0 of gridstatusio. if you upgrade to that, everything should work. let me know if you see any other problems

Hi Max
I seem to be getting a similar timestamp conversion error with the “ercot_fuel_mix” data after updating to the latest packages? I see solar production that appears to be indexed via UTC time even when asking for local?
Thanks!
Joshua Rhodes
￼￼
￼

On Aug 22, 2023, at 8:04 PM, Max Kanter @.***> wrote:
thanks! i was able to reproduce and fix the error when I downgraded to that version of pandas.
just released version 0.5.0 of gridstatusio. if you upgrade to that, everything should work. let me know if you see any other problems
—
Reply to this email directly, view it on GitHub https://github.com/gridstatus/gridstatusio/issues/16#issuecomment-1689113353, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZQFTHXGUYD2KJG3XDTWFTXWVJIBANCNFSM6AAAAAA3Y6XDD4.
You are receiving this because you authored the thread.

Hi Joshua - im not able to reproduce. can you share the code you are using the versions of pandas and gridstatus that you are using?

Right, but it looks like that the solar doesn't start producing until late in the afternoon, well after the sun has come up and keeps on producing well into the night after the sun has gone down?

repo: gridstatus/gridstatusio


text:
Bun support

Hi.. Could you add bun.sh support? https://bun.sh

Hi.. Could you add bun.sh support? https://bun.sh

Hi! Sure! Will do it this weekend

authors: Kleywalker grigorii-zander


text:
Misspelling in AccordionPanel headings of the word "Third"

What does this PR do?
Where should the reviewer start?
What testing has been done on this PR?
How should this be manually tested?
Any background context you want to provide?
What are the relevant issues?
Screenshots (if appropriate)

thanks

authors: alansouzati tracybarmore

repo: grommet/grommet-docs


text:
Makes source no longer required

This should in theory make v0.18 backwards. compatible

I need to check in on the test runner's permissions before I can merge this in, but the branch is here to unblock internal work

Test runners are updated, should be good to go

The fact that source is optional is very unintuitive I think (and hard to determine why by reading the code). Is it possible to add a tag or annotation or something that explians its for compatibility between x version and y version and that in fact it will be returned in y version?

authors: brandon-groundlight tyler-romero

repo: groundlight/python-sdk


text:
Selenium Grid Extras not restarting after N tests

Hi Dima,
I'm running the last Grid Extras (v1.7.1) in a windows vm and in the configuration I set the restart of the vm at 10 tests.
Despite this, the vm is not restarting. In the logs there's no tracking information and I accumulate like 100+ sessions without a restart.
It seems not to be a browser bug related, because it fails for ie/chrome/firefox.
Thanks in advance

@Ahskaniz Is this fixed for you in Selenium-Grid-Extras 1.10.0 ?

@smccarthy I just stopped using this feature for one handmade.

@Ahskaniz Ok thanks for the quick response!

Closing as we think this is working correctly. If anyone finds that this is still an issue, please open a new issue.

authors: Ahskaniz smccarthy

repo: groupon/Selenium-Grid-Extras


text:
Indian Flag Issue

Hi, Thank you for providing .svg flags for Vue. Though, I have an issue.
The flag you have deployed for India is invalid in vueflags/assets/flags/in.svg. It is not an Indian flag. I request you to please change the flag to the one that I have shared below from the source of wikipedia or as per your wished open source. Furthermore, the Indian flag has 'Ashok Chakra' in between and not the star. I thank you in advance for the same.
Your flag:

Link:

https://github.com/growthbunker/vueflags/blob/master/assets/flags/in.svg

Svg:

<?xml version="1.0" encoding="iso-8859-1"?> <svg   xmlns="http://www.w3.org/2000/svg"   xmlns:xlink="http://www.w3.org/1999/xlink" version="1.1" id="Capa_1" x="0px" y="0px" viewBox="0 0 512 512" style="enable-background:new 0 0 512 512;" xml:space="preserve">   <rect y="85.337" style="fill:#F0F0F0;" width="512" height="341.326"/>   <rect y="85.337" style="fill:#FF9811;" width="512" height="113.775"/>   <rect y="312.888" style="fill:#6DA544;" width="512" height="113.775"/>   <circle style="fill:#0052B4;" cx="256" cy="256" r="43.896"/>   <circle style="fill:#F0F0F0;" cx="256" cy="256" r="27.434"/>   <polygon style="fill:#0052B4;" points="256,222.146 264.464,241.341 285.319,239.073 272.927,256 285.319,272.927 264.464,270.659   256,289.854 247.536,270.659 226.681,272.927 239.073,256 226.681,239.073 247.536,241.341 "/> </svg>
Real Indian Flag:

Link:

https://en.wikipedia.org/wiki/File:Flag_of_India.svg#/media/File:Flag_of_India.svg

Svg:

<?xml version="1.0" encoding="UTF-8"?> <svg width="1350" height="900" viewBox="0 0 225 150" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"> <rect width="225" height="150" fill="#f93"/> <rect y="50" width="225" height="100" fill="#fff"/> <rect y="100" width="225" height="50" fill="#128807"/> <g transform="translate(112.5,75)"> <circle r="20" fill="#008"/> <circle r="17.5" fill="#fff"/> <circle r="3.5" fill="#008"/> <g id="e"> <g id="f"> <g id="g"> <g id="h"> <circle transform="rotate(7.5) translate(17.5)" r=".875" fill="#008"/> <path d="m0 17.5 0.6-10.5-0.6-5-0.6 5 0.6 10.5z" fill="#008"/> </g> <use transform="rotate(15)" xlink:href="#h"/> </g> <use transform="rotate(30)" xlink:href="#g"/> </g> <use transform="rotate(60)" xlink:href="#f"/> </g> <use transform="rotate(120)" xlink:href="#e"/> <use transform="rotate(240)" xlink:href="#e"/> </g> </svg>

Thank you @Ruchirr,  I have updated it with your flag. 👍
Update your package to 0.0.9.

Hi @LeCoupa
Thanks for a quick update. Though, the svg compilation does not match with other flags. This is how it is looking figure 1. Before with the wrong flag it was working just fine figure 2
Figure 1

Figure 2

Please use the following SVG code
`

`
Hope this helps your project @LeCoupa

Thank you so much @Ruchirr

authors: LeCoupa Ruchirr

repo: growthbunker/vueflags


text:
this dependency seems to be incompatible with new version 3.x of spring boot.

The context
upgrade my app to spring boot 3.X
The bug
"grpc-spring-boot-starter" seems to  not have a version compatible with spring boot 3.x as of now. And since their auto-configuration is still present in "spring.factories" file, some of the beans for these dependencies are not being autowired after migration to spring boot 3, resulting in application start up failures.

Could you please post the error mesaage along with the version you are using?

I'm having a similar problem. I'm following the Getting Started Guide, but Spring Boot 3 seems to ignore @GrpcService. Probably there is some kind of auto-detecting issue described in 3rd task of Implementing the Service.
And my pom.xml, downgrading spring-boot-starter-parent seemed to work for me.
i.e. from:
	<parent>
		<groupId>org.springframework.boot</groupId>
		<artifactId>spring-boot-starter-parent</artifactId>
		<version>3.2.2</version>
		<relativePath/> <!-- lookup parent from repository -->
	</parent>

to:
	<parent>
		<groupId>org.springframework.boot</groupId>
		<artifactId>spring-boot-starter-parent</artifactId>
		<version>2.5.7</version>
		<relativePath/> <!-- lookup parent from repository -->
	</parent>

You never said which version of grpc-spring you are using. Is it possibly not the latest?

You never said which version of grpc-spring you are using. Is it possibly not the latest?

You were right, I was using 2.15.0 and 3.0.0 is released and Beans are autowired there. What a simple mistake, thank you!

authors: ST-DDT codeGuru775 dsyer ocebenzer

repo: grpc-ecosystem/grpc-spring


text:
Metadata value; null-terminated vs. sized

There's a lack of consensus on the treatment of null-bytes in metadata values as far as I can tell. There should be documentation here clarifying how the metadata should be treated.
Note that GRPC appears to Do The Right Thing™ and respect the length for the metadata value when copying here (thus allowing null-bytes in the value). That such is not written anywhere as a guarantee isn't particularly comfortable.
And then there's what to do about metadata key suffixes. The purpose of this should be documented.

The HTTP2 spec forbids null as a value in header values which is why we require that arbitrary binary sequences (including ones with nulls) are encoded as base-64 on the wire and use the '-bin' suffix on the header name.
Feel free to suggest clarification to
https://github.com/grpc/grpc-common/blob/master/PROTOCOL-HTTP2.md

I don't think people should need to jump across repositories to get an idea of the semantics of our code.

#554 should address this.

authors: ctiller louiscryan soltanmm

repo: grpc/grpc


text:
Issue with gRPC channel class missing request method

What version of gRPC and what language are you using?
What operating system (Linux, Windows,...) and version?
OSx Big Sur 11.5.2
What runtime / compiler are you using (e.g. python version or version of gcc)
Python 3.9
What did you do?
Generated a Python client using protoc-gen-grpclib_python, attempted to use the generated client:
import sys
import asyncio

sys.path.insert(0, '../clients/python')

import grpc

from proto.hot_storage_pb2 import SetRequest, GetRequest
from proto.hot_storage_grpc import HotStorageServiceStub

from google.protobuf import struct_pb2 as struct

async def main():
    with grpc.insecure_channel('0.0.0.0:9000') as channel:
        stub = HotStorageServiceStub(channel=channel)

        await stub.Set(SetRequest(key='key', values=struct.Struct(fields={'value': struct.Value(string_value='value')})))
        result = await stub.Get(GetRequest(key='key'))
        print(result)

if __name__ == '__main__':
    loop = asyncio.get_event_loop()
    loop.run_until_complete(main())

What did you expect to see?
I expected the code snippet to call my gRPC server, and return a result.
What did you see instead?
Instead, I got the following error:
Traceback (most recent call last):
  File "/Users/ewanvalentine/work/hot-storage-rollout/playground/test.py", line 24, in <module>
    loop.run_until_complete(main())
  File "/usr/local/Cellar/python@3.9/3.9.7/Frameworks/Python.framework/Versions/3.9/lib/python3.9/asyncio/base_events.py", line 642, in run_until_complete
    return future.result()
  File "/Users/ewanvalentine/work/hot-storage-rollout/playground/test.py", line 17, in main
    await stub.Set(SetRequest(key='key', values=struct.Struct(fields={'value': struct.Value(string_value='value')})))
  File "/Users/ewanvalentine/work/hot-storage-rollout/playground/venv/lib/python3.9/site-packages/grpclib/client.py", line 881, in __call__
    async with self.open(timeout=timeout, metadata=metadata) as stream:
  File "/Users/ewanvalentine/work/hot-storage-rollout/playground/venv/lib/python3.9/site-packages/grpclib/client.py", line 853, in open
    return self.channel.request(self.name, self._cardinality,
AttributeError: 'Channel' object has no attribute 'request'

Anything else we should know about your project / environment?
$ pip freeze . generates:
asyncio==3.4.3
cachetools==4.2.4
certifi==2021.10.8
charset-normalizer==2.0.7
coverage==6.0.2
Cython==0.29.24
google-api-core==2.1.1
google-api-python-client==2.27.0
google-auth==2.3.0
google-auth-httplib2==0.1.0
googleapis-common-protos==1.53.0
greenlet==1.1.1
grpcio==1.41.0
grpcio-tools==1.41.0
grpclib==0.4.2
h2==4.1.0
hpack==4.0.0
httplib2==0.20.1
hyperframe==6.0.1
idna==3.3
msgpack==1.0.2
multidict==5.2.0
mypy-extensions==0.4.3
protobuf==3.12.2
pyasn1==0.4.8
pyasn1-modules==0.2.8
pynvim==0.4.3
pyparsing==2.4.7
python-engineio==3.12.1
requests==2.26.0
rsa==4.7.2
ruamel.yaml==0.16.13
ruamel.yaml.clib==0.2.6
six==1.16.0
typed-argument-parser==1.7.1
typing-extensions==3.10.0.2
typing-inspect==0.7.1
uritemplate==4.1.1
urllib3==1.26.7

File "/Users/ewanvalentine/work/hot-storage-rollout/playground/venv/lib/python3.9/site-packages/grpclib/client.py", line 853, in open
return self.channel.request(self.name, self._cardinality,
AttributeError: 'Channel' object has no attribute 'request'

The error is in grpclib, which is a separate project: https://github.com/vmagamedov/grpclib.

Oh! My apologies @drfloob, silly me!

How did you solve it, I got the same problem

I am also having same issue.. How is that fixed?

Anyone have any contributions to the above issue?

authors: EwanValentine KiranHighNote atulsriv drfloob nflux-pyang


text:
grpc cpp 0_11_0 create stub error with msvc 2013 with preprocessor definition  _USE_32BIT_TIME_T

I build my grpc 0_11_0 with default settings under /vsprojects, and get all the cpp libs. When I used it in my project with very simple rpc server and client, I found that NewStub will be created without any error messages, but afterwards I called a rpc method, the program crashed. I tested again without the preprocesser definition _USE_32BIT_TIME_T in all /vsprojects, then everything is ok.
My environment is msvc 2013 in windows 10.

#4315

authors: Zerqkboo jtattermusch


text:
changes to allow VS solution/project generation and grpc.mak generation for c++ tests

this isn't fully polished but it gets OK coverage (about 10 c++ tests are not building because of posix includes, and a couple other random ones)
todo

switch back to using generate_projects.py (parallel version)
clean up c++ props and split into gtest/gflags props
Decide if building .proto files in-place with a manual script is the best solution, or if there's another way
add documentation for grpc.mak building and overall buildgen layout
get versions of zlib/openssl with pdb files (debug symbols) to get rid of most compile warnings

Can one of the admins verify this patch?

This is ok to test.

not building windows tests are below.  I am putting "platform" = posix into build.json for these for now

failed test
reason

async_streaming_ping_pong_test
posix (sys/time.h, sys/signal.h)

async_unary_ping_pong_test
posix (sys/time.h, sys/signal.h)

client_crash_test
unresolved external in grpc++_test_util (don't know why)

server_crash_test
unresolved external in grpc++_test_util (don't know why)

interop_client
posix (unistd.h)

interop_server
posix (unistd.h)

interop_test
posix (unistd.h)

qps_interarrival_test
posix (sys/time.h, sys/signal.h)

qps_openloop_test
posix (SIGPIPE, sys/time.h, sys/signal.h)

qps_test
posix (SIGPIPE, sys/time.h, sys/signal.h)

sync_streaming_ping_pong_test
posix (SIGPIPE, sys/time.h, sys/signal.h)

sync_unary_ping_pong_test
posix (SIGPIPE, sys/time.h, sys/signal.h)

C test failures/timeouts, over 3 runs:

failure count
fail/timeout
name

3
FAILED:
secure_endpoint_test

3
FAILED:
initial_settings_frame_bad_client_test

3
TIMEOUT:
chttp2_fullstack_compression_early_server_shutdown_finishes_inflight_calls_test

3
TIMEOUT:
chttp2_fullstack_disappearing_server_unsecure_test

3
TIMEOUT:
chttp2_simple_ssl_fullstack_request_with_flags_test

3
TIMEOUT:
chttp2_fullstack_compression_early_server_shutdown_finishes_inflight_calls_unsecure_test

2
TIMEOUT:
chttp2_fullstack_compression_cancel_after_invoke_unsecure_test

3
TIMEOUT:
chttp2_fullstack_graceful_server_shutdown_unsecure_test

3
TIMEOUT:
chttp2_fullstack_compression_disappearing_server_test

3
TIMEOUT:
chttp2_fullstack_early_server_shutdown_finishes_inflight_calls_test

3
TIMEOUT:
chttp2_fullstack_compression_graceful_server_shutdown_unsecure_test

2
TIMEOUT:
chttp2_fullstack_cancel_after_invoke_test

1
TIMEOUT:
chttp2_fullstack_cancel_after_invoke_unsecure_test

3
TIMEOUT:
chttp2_fullstack_compression_graceful_server_shutdown_test

3
TIMEOUT:
chttp2_fullstack_early_server_shutdown_finishes_inflight_calls_unsecure_test

3
TIMEOUT:
chttp2_fullstack_disappearing_server_test

3
TIMEOUT:
chttp2_fullstack_compression_disappearing_server_unsecure_test

3
TIMEOUT:
chttp2_fullstack_compression_cancel_after_invoke_test

3
TIMEOUT:
chttp2_simple_ssl_with_oauth2_fullstack_request_with_flags_test

3
TIMEOUT:
chttp2_fullstack_graceful_server_shutdown_test

C++ timeouts (no regular failures).  I think these are to do with opening a windows socket, see #2294
thread_stress_test
mock_test
cli_call_test
async_end2end_test
end2end_test

Alright, thank you for your hard work on this :)

authors: grpc-jenkins larsonmpdx nicolasnoble


text:
Build and run per-language containers for interop tests

-- introduce per-language docker images for interop tests
-- run_interop_tests.py now works in several steps: it first build all the language specific images, then spins up all the servers, runs all the interop tests (each in a separate container) and finally it kills the servers and cleans up the docker images it has build (it leaves the "base" images as those will rarely change).
-- added support java client/server (the scripts looks for java sources in ../grpc-java relatively to  grpc repo root)
-- added support for --alow_flakes flag (fixes #3581)

CC @ejona86


text:
Node package cleanup

This change removes several files that have become irrelevant, either because they now live in other repositories (like the contents of src/node/cli and src/node/bin) or because they were completely unused and untested (like src/node/examples/stock*). In addition, src/node/examples is now confusing in relation to the root examples directory, so it is split into more clear directories: src/node/performance for performance tests, and src/node/test/math, since the math service stuff is only used in tests.
It also removes some directories from package.json that are not essential to using the library.

LGTM, will merge once this is updated

It's updated


text:
Improve Node and libuv testing and test coverage

This makes a number of related changes:

The use of the libuv iomgr implementation can now be set at compile time when building Node (instead of hardcoded into the file). That setting currently defaults to false; we should set it back to true when we are more confident in that implementation.

The Node tests now run on Node 7 by default, instead of Node 4. Portability tests have been added to run the tests on Node 4 and Node 6, and with the libuv iomgr instead of the default iomgr.

When the debug config is specified, the Node tests actually use the debug build.

Some core tests have been modified or added to run with the libuv iomgr. A portability test has been added to run the core tests with libuv.

Note: The core test lb_policies_test currently fails with libuv. This test is being disabled in parallel in #9765

This also seems to fix #9668. That test is passing in this PR, at least. The test that was failing in #9726 also passes here.

TSAN failure: #9124. The interop failure is an infrastructure failure. The Mac failure appears to be a fluke: I have been unable to reproduce it in thousands of runs.


text:
Feature Request: Fail when number of warnings found exceeds certain threshhold

When trying to use CSSLint plugin on an already existing project, one issue that comes up often is that certain violations are not going to be fixed, therefore, one could not start from zero violations.
At such a situation the option to fail build only if the number of violations exceeds certain count (watermark) will be extremely useful.

I doubt this will ever be implemented.
You can make a PR and discuss the implementation there.

authors: XhmikosR serhiy-yevtushenko

repo: gruntjs/grunt-contrib-csslint


text:
Watch Error: FSEventStreamFlushSync(): failed assertion

I am getting the following error after Running "watch" task restarts
2015-03-02 11:19 grunt[7732] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

Happens with these versions:
$ node 0.11.6 - 0.12.0
$ npm 2.5.1

Related Grunt Config:
...
watch: {
  sass: {
    files: [
      '<%= configs.sassPaths.answ_sass + configs.minimatch %>',
      '<%= configs.sassPaths.sass_lib + configs.minimatch %>'
    ],
    options: {
      nospawn: true
    }
  }
}
...

Get exactly the same message when watch restarts. Happens on several projects with different configurations and on two different Macs.
Tested with those npm versions:
'''
$ node v0.12.0
$ npm 2.3.0, 2.5.0, 2.7.0, 2.7.1
'''

This happens for me too

+1 Ditto

Same here. Can't seem to find a solution...

+1 Yeah, same here. Watch task seems to actually work, but nonetheless the message is a bit annoying. I am on Yosemite 10.10.2

Same here, whats the problem?

Same problem. Upgraded to node.js v0.12.1, and it is still there.

Same problem.

Does anyone write an bugreport to the nodejs guys?

Same here
$ node v0.12.2
$ npm 2.7.4
OSX 10.10.2 (14C1514)

grunt[22532] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

If anyone wants to try this in io.js, should be fixed there.

Still happening for me as well
node v0.12.2
npm 2.7.5
grunt-contrib-watch 0.6.1
OS X 10.10.3
This seems to happen more when it has to run an uglify or concat task. But both are at the latest version.

Same here on
node v0.12.0
npm 2.5.1
grunt-contrib-watch 0.6.1
OS X 10.9.5
Happens only if I set the option spawn: false. The tasks don't run correctly, it's not just the message for me.

Same problem - Seems to be functioning fine, but always gives this error.
Node: v0.12.2,
NPM: 2.7.5,
grunt: ^0.4.5,
grunt-contrib-concat: ^0.5.1,
grunt-contrib-imagemin: ^0.9.4,
grunt-contrib-uglify: ^0.9.1,
grunt-contrib-watch: ^0.6.1,
grunt-sass: ^0.18.1
OS X 10.10.2

(FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

Can confirm.

same here
Node v0.12.2
grunt-cli v0.1.13
grunt v0.4.5
grunt-contrib-watch 0.6.1
OS X 10.10.3

I'm also experiencing this issue
Node v0.12.2
Npm v2.7.5
Packages:
├── grunt@0.4.5
├── grunt-contrib-connect@0.10.1
├── grunt-contrib-copy@0.8.0
├── grunt-contrib-less@1.0.1
├── grunt-contrib-uglify@0.9.1
├── grunt-contrib-watch@0.6.1
├── grunt-exec@0.4.6
└── grunt-express-server@0.5.1

Same here.
node: v0.12.0
Removing spawn from Watch > Scripts > Options:{ } stops the error. What is spawn anyway again?

Might this potentially be why?
https://github.com/bdkjones/fseventsbug/wiki/realpath()-And-FSEvents

@digitalcraftco solution worked with v0.12.7, removing all spawns from watch: {} task (even if they're false)

@juanbrujo Thanks for the follow up. Indeed this has fixed the issue for newer versions.

Interesting. Is 0.11.6 the earliest node version this manifests in? We've had the above linked io.js issue for this for a while but haven't really been able to debug it.

@digitalcraftco It defines whether a new task should be spawned or not. See https://github.com/gruntjs/grunt-contrib-watch#optionsspawn
Removing spawn from options does avoid but not fix the issue.

+1 getting this as well still.

Interesting to note, as soon as you remove the spawn = false property the compile time jumps up dramatically, in my case from 0.3sec to 4.3sec !!

I see similar messages in a C app using libuv and uv_fs_event* I wrote as well. Linked to https://github.com/nodejs/node/issues/854 which mentions this issue.

Absolutely nothing changed in my dependencies for the last month at least and I randomly just started seeing this

@maruf89 Did you change OS X versions?

No, I'm still on Yosemite 10.10.3 - The only thing that changed is I got a hard drive cable replaced but no software/npm deps changed

Never had this problem on Yosemite, upgraded to El Capitan and now it happens...

+1 having same issue

@maruf89, same by me, i had only changed the hard drive cable.

This is still an issue with Node.js 4.4.7 and 6.3.1. I'm on OS X 10.11.6. I'm NOT using chokidar, fsevents, gaze, or any other filesystem watching library. I'm only using the built-in fs.watch().

+1

What are the side-effects to this error? It started occurring in my project after I added imagemin

What are the side-effects to this error?

Unknown, probably nothing impactful? I think the OS just retries or something.

Strange that multiple people would see it after a harddrive cable, maybe it's an odd apple hardware issue?

Am sure it has nothing to do with hardware. As Fishrock123 said, no apparent(!) sideeffects, but still annoying. So a fix definetly would be nice, since also a lot of systems seem to be affected.

I'm having this issue with node v7.3.0 on OSX 10.11.6 (El Capitan) and grunt v0.4.5, grunt-cli v1.2.0

I can't make sense of why this worked, but I was having the exact same issue, and adding more specific selectors for the files I was watching resolved the issue. Here's a sample of my old Gruntfile:
watch: {
	css: {
		files: '**/*.scss',
		tasks: ['sass']
	},
	js: {
		files: '**/*.js',
		tasks: ['rollup']
	}
}

and here's my new Gruntfile
watch: {
	css: {
		files: './assets/**/*.scss',
		tasks: ['sass']
	},
	js: {
		files: './assets/**/*.js',
		tasks: ['rollup']
	}
}

What's more--my old grunt process was using a huge chunk of my CPU, and with my more specific file selection, I use only 2-3%.

authors: AlexChesters Fishrock123 JWGmeligMeyling Pedder SudoCat TheBox193 ThomasHoadley alphanull awenro cb1kenobi crimann cwklausing digitalcraftco ekkis flekschas greenchapter infinityplusone jlujan juanbrujo lancepadgett maruf89 mikehdt of6 ogmios2 ourcore paulhayes tannerlinsley tbremer tconroy teejayhh tuffz vemec vladikoff yumyo

repo: gruntjs/grunt-contrib-watch


text:
Fix template code for commander

If people uncomments the example it should actually compile :)

Thanks a lot!

authors: grych vic

repo: grych/drab


text:
🛑 volkstanz.st is down

In 21862af, volkstanz.st (https://volkstanz.st) was down:

HTTP code: 0
Response time: 0 ms

Resolved: volkstanz.st is back up in 94dc3d7.


text:
🛑 bretterhofer.at is down

In fc8ae49, bretterhofer.at (https://bretterhofer.at) was down:

HTTP code: 0
Response time: 0 ms

Resolved: bretterhofer.at is back up in f31004b.


text:
🛑 kinderundjugendtanz.at is down

In da1ca1c, kinderundjugendtanz.at (https://kinderundjugendtanz.at) was down:

HTTP code: 0
Response time: 0 ms

Resolved: kinderundjugendtanz.at is back up in 2986215.


text:
🛑 Wikipedia is down

In d312e65, Wikipedia (https://en.wikipedia.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wikipedia is back up in 05df3bf.


text:
🛑 volkstanz.st is down

In 8666018, volkstanz.st (https://volkstanz.st) was down:

HTTP code: 0
Response time: 0 ms

Resolved: volkstanz.st is back up in 7481ad0 after 7 minutes.


text:
Support for threaded messages

When being triggered inside a message thread, the plugin still posts within the main channel - without having looked into too much detail in the code, it would be great if the plugin could use the thread_ts/ts attributes as discussed in [1].
Thanks,
Johan
[1] https://api.slack.com/docs/message-threading

Thanks for the patch!

authors: gsingers johanlindquist

repo: gsingers/slack-jira-plugin


text:
Character count

Include a character count UI component which displays the length of the user's current message. If the CHARACTER_LIMIT defence mechanism is active, then this component should also inform the user when the message length is too long.

@PuneetLoona

repo: gsproston-scottlogic/prompt-injection


text:
Wrong variable referenced in Generating Google Slides from images Tutorial

Lines 61, 65, and 66 of imageSlides reference the presentation variable. At that point in the tutorial, the deck variable is still being used to reference the presentation, so the script throws an error if you're following the tutorial step by step.

Good catch, thanks!

authors: erickoledadevrel kacrouse

repo: gsuitedevs/apps-script-samples


text:
Error using topquadrant shacl

Hi Gabe, I'm getting an error running test cases using topquadrant shacl:
docker.errors.APIError: 500 Server Error for http+docker://localhost/v1.41/images/create?tag=1.4.2&fromImage=ghcr.io%2Ftopquadrant%2Fshacl: Internal Server Error ("Head "https://ghcr.io/v2/topquadrant/shacl/manifests/1.4.2": unauthorized")

Did you encounter this error?

I don't think I've run into this, but it might be an issue with docker configuration that we need to either document in the README or fix in a script. Have you run the build-topbraid-shacl.sh script?

That worked! I thought I had done it but it appears not. It may be a good idea to add to the readme.

Just added a note to the README!

authors: gtfierro lazlop

repo: gtfierro/shacl-issues


text:
Disable draw_value on Scale elements disables snapping to value

I'm not positive if this is a gtk bug or a gtk-rs bug, but if I create a Scale element with s couple of set values that the selector should snap to, it works fine. But then if I call set_draw_value(false), the scale no longer snaps to the appropriate values. I've included sample code:
extern crate gtk;

use gtk::prelude::*;

fn main() {

    gtk::init().expect("");

    let window = gtk::Window::new(gtk::WindowType::Toplevel);
    window.set_default_size(400, 300);

    let scale = gtk::Scale::new_with_range(gtk::Orientation::Horizontal, 1.0, 2.0, 1.0);
    scale.set_draw_value(false); // Comment out this line to see "proper" behavior
    scale.add_mark(1.0, gtk::PositionType::Bottom, Some("1"));
    scale.add_mark(2.0, gtk::PositionType::Bottom, Some("2"));

    let vbox = gtk::Box::new(gtk::Orientation::Vertical, 0);
    vbox.pack_start(&scale, false, false, 0);
    window.add(&vbox);
    window.show_all();
    gtk::main();
}

with Cargo.toml:

[dependencies.gtk]
version = "0.1"

Seems snapping unrelated to marks and controlled by https://developer.gnome.org/gtk3/stable/GtkScale.html#gtk-scale-set-digits (scale.set_digits(1); in your case) and works only when current value shown.
This can be seen if you set max to 5.0 and add 3.5 (or 4.0) marks.
If you need disable smooth scroll and don't show current value, you can use this
        scale.connect_format_value(|scale, value| {
            String::new()
        });

Thanks, yes I see what you're saying. So it seems like this is a GTK+ bug, either in their docs for not noting this limitation or in their code. I can't imagine why the behavior changes when changing appearance, however. I'll file a bug upstream and close this one once I do.

Moving this discussion to GNOME's bug tracker: https://bugzilla.gnome.org/show_bug.cgi?id=777858

authors: EPashkin Susurrus

repo: gtk-rs/gtk


text:
show currently logged in username in slideout action menu

https://github.com/filebrowser/filebrowser/issues/2692

Added in https://github.com/gtsteffaniak/filebrowser/pull/157

0.2.7 included

repo: gtsteffaniak/filebrowser


text:
SMS integration

let user enter phone number to link username with phone number?

philipp has something, that you culd send an sms with your username and your number was automatically registered. Afterwards it was possible to send messages.

I've used Nexmo in the past and it works well:
https://www.nexmo.com/
https://www.twilio.com/

twilio didn't give me a DE number, trying nexmo now

stuck with http://stackoverflow.com/q/29447706/1245190 now

Yay! First test worked!
Our number is +491771789420

works quite well now
todo: match phone number with user

continue with #9 and #11

authors: UserStefan guaka simison

repo: guaka/hitchticker


text:
Bug Fix GmSSL client cannot communicate with TaSSL server; https://gi…

Bug Fix : GmSSL client cannot communicate with TaSSL server.
Issue: https://github.com/guanzhi/GmSSL/issues/913

Are you still work on it?

repo: guanzhi/GmSSL


text:
Update livereload.js

Fix for Chrome bug: https://github.com/livereload/livereload-extensions/issues/26#issuecomment-54250594

I can merge this if it helps others - please ask people to add +1s here to confirm.

I've made it so you can change those values in the Guardfile: https://github.com/guard/guard-livereload/pull/147
If there are any issues there, please open a new PR.

repo: guard/guard-livereload