STAR-361: Query all ranges at once for SAI distributed queries

Is this from a bdp/dse commit?

The changes came from DSP-20336 but that didn't apply in the original STAR-121 port because of changes made by CASSANDRA-16180. Originally the changes here went into StorageProxy but the range commands were moved out of StorageProxy and broken up into separate classes in the service.reads.range package.


Node.js Mentorship team Meeting 2018-04-20

Time
UTC Fri 20-April-2018 17:00 (05:00 PM):

Timezone
Date/Time

US / Pacific
Fri 06-April-2018 09:00 (09:00 AM)

US / Mountain
Fri 06-April-2018 10:00 (10:00 AM)

US / Central
Fri 06-April-2018 11:00 (11:00 AM)

US / Eastern
Fri 06-April-2018 12:00 (12:00 PM)

London
Fri 06-April-2018 17:00 (05:00 PM)

Amsterdam
Fri 06-April-2018 18:00 (06:00 PM)

Moscow
Fri 06-April-2018 20:00 (08:00 PM)

Chennai
Fri 06-April-2018 22:30 (10:30 PM)

Hangzhou
Sat 07-April-2018 01:00 (01:00 AM)

Tokyo
Sat 07-April-2018 02:00 (02:00 AM)

Sydney
Sat 07-April-2018 04:00 (04:00 AM)

Or in your local time:

https://www.timeanddate.com/worldclock/fixedtime.html?msg=Nodejs+Mentorship+Team+Meeting+2018-04-20&iso=20180406T17
or http://www.wolframalpha.com/input/?i=05PM+UTC,+April+20,+2018+in+local+time

Agenda
Extracted from mentorship-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

Mentorship Moderation #35
Peer support subgroup for mentors #33
Create a mentorship subgroup focused on to identify 6 month projects in Node.js #30

Invited
CommComm Members: @nodejs/community-committee

Dan Shaw (@dshaw - CommComm member, User Feedback champion)
Tierney Cyren (@bnb - CommComm Co-Chair)
Ahmad Bamieh (@Bamieh)
Conrad Hollomon (@hollomancer)
Erin Spiceland
Ryan Lewis
Forrest Norvell

Applied Mentors:

James M Snell (@jasnell)
Myles A Borins (@mylesborins)
Agiri Abraham Junior (@codeekage)
Samuel Omole (@samie820)
Brian Giggle (@BGiggle)
Benjamin Coe (@bcoe)
Carlos Santana (@csantanapr)
Kostas Kapetanakis (@kapekost)
Andrea Leone (@andrealeone)
Wassim Chegham (@manekinekko)
amine ben romdhane (@amineorion)
Avinash Chandra (@softwarecoder)
Miquel Ramon Ortega Tido (@wolmi)
Pramod Pathak (@pramod1792)
Dor Kleiman (@configurator)
Oleg Koval (@oleg-koval)
chen salomon (@csaloman)
Nguyen Truong Minh (@truongminh)
Zeeshan Memon (@zishon89us)
Opesanya Adebayo (@OpesanyaAdebayo)
Vinicius Mussak (@vmussak)
Manuel Romero (@mrm8488)
Sébastien D. (@demsking)
William Oliveira (@woliveiras)
Zoltan Debre (@zoltan-nz)
George Mandis (@georgemandis)
Tine Jozelj (@mentos1386)

Notes
The agenda comes from issues labelled with mentorship-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.
Joining the meeting
Zoom link: https://zoom.us/j/659137458
meeting notes: https://docs.google.com/document/d/1FAUuolJbkxG0oje8rBpqyH2XqgGPlHDX6WMIotSIyUk/edit

I missed the meeting today, where is the schedule so i can add to my personal calendar or is there a google calendar I can add?

Likewise, I just realised the date on the top was different to the timezone
list .. :(
The list helps but maybe we should remove the day part and leave the time
only?
On Sat, 21 Apr 2018 at 01:11, Carlos Santana<EMAIL_ADDRESS>wrote:

I missed the meeting today, where is the schedule so i can add to my
personal calendar or is there a google calendar I can add?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nodejs/mentorship/issues/36#issuecomment-383251916,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AForrt_vL8YfuIRIhk5-YENluLgQP9LPks5tqnlJgaJpZM4Tdsik
.

--
Kostas Kapetanakis
Software Developer


Not a issue just a request. (Ace Permissions)

Hi there, would you be able to make this ace permission based? Thanks!!

That was on the roadmap but unfortunately at the moment I am not free enough to work on this


BUG REPORT: The custom eval metric get untransformed model input score.

On XGBoost python library (version 1.4.2, also in 1.4.0), custom eval metric get an untransformed model score, instead of the validation prediction probability.
Code to reproduce:
import numpy as np
import xgboost as xgb
from sklearn.metrics import accuracy_score

def custom_eval_metric(y_pred_proba, dtrain):
    y_true_label = dtrain.get_label()
    print(y_pred_proba.min(), y_pred_proba.max())

    acc_score = accuracy_score(
        y_true_label.reshape(-1, 1),
        (y_pred_proba > 0.5).astype(int).reshape(-1, 1))

    return 'custom_acc', -1 * acc_score

if __name__ == '__main__':
    # Generating random training data
    X_train = np.random.random(500)
    X_train = X_train.reshape((100, 5))
    y_train = (np.random.randint(0, 100, 100) > 50).astype(int)

    X_val = np.random.random(500)
    X_val = X_val.reshape((100, 5))
    y_val = (np.random.randint(0, 100, 100) > 50).astype(int)

    # training XGBoost classifier
    xgb_params = {
        "n_estimators": 20,
        "max_depth": 5,
        "learning_rate": 0.03,
        "verbosity": 0,
        "objective": "binary:logistic",
        "booster": "gbtree",
        "colsample_bytree": 0.98,
        "colsample_bylevel": 0.97,
        "subsample": 0.98,
        "disable_default_eval_metric": 1,
        "random_state": 2048}

    # Fit a xgboost model, you can see at each iteration, the eval metric
    # get the untransformed model output score
    model = xgb.XGBClassifier(**xgb_params)
    model.fit(
        X_train, y_train,
        eval_set=[(X_val, y_val)],
        early_stopping_rounds=15,
        verbose=True,
        eval_metric=custom_eval_metric)

Output:
-0.035172414 0.027272727
[0]	validation_0-custom_acc:-0.50000
-0.07448528 0.04746426
[1]	validation_0-custom_acc:-0.50000
-0.10820254 0.067466184
[2]	validation_0-custom_acc:-0.50000
-0.1436399 0.08694458
[3]	validation_0-custom_acc:-0.50000
-0.18393388 0.09330373
[4]	validation_0-custom_acc:-0.50000
-0.22471038 0.11267628
[5]	validation_0-custom_acc:-0.50000
-0.26337633 0.13032766
[6]	validation_0-custom_acc:-0.50000
-0.2959541 0.1534172
[7]	validation_0-custom_acc:-0.50000
-0.2985757 0.17225054
[8]	validation_0-custom_acc:-0.50000
-0.33194867 0.18320686
[9]	validation_0-custom_acc:-0.50000
-0.36432728 0.20864208
[10]	validation_0-custom_acc:-0.50000
-0.39650607 0.20381181
[11]	validation_0-custom_acc:-0.50000
-0.4287486 0.2129844
[12]	validation_0-custom_acc:-0.50000
-0.41276354 0.23032054
[13]	validation_0-custom_acc:-0.50000
-0.43424797 0.2607328
[14]	validation_0-custom_acc:-0.50000
-0.465707 0.28491184

Expected behaviour:
You can see negative score in each iteration. The expected output should range between 0 and 1.
Bug analysis:
See line 1643 in core.py, XGBoost version 1.4.2. This problem is caused by an unsuitable predict method parameter(output_margin=True).

This is actually an expected behavior. Quoted from the release note for 1.2.0:

Breaking: Custom evaluation metric now receives raw prediction (#5954)
Previously, the custom evaluation metric received a transformed prediction result when used with a classifier. Now the custom metric will receive a raw (untransformed) prediction and will need to transform the prediction itself. See demo/guide-python/custom_softmax.py for an example.
This change is to make the custom metric behave consistently with the custom objective, which already receives raw prediction (#5564).

The question remains: How can we transform the raw score of the prediction that custom_eval_metric received to the prediction  probability in the binary classification problem?
I have read the API codes and searched for answers for a half of a day, none of them gave an answer.
Thanks for your relying.

@MichaelYin1994 Take a look at https://github.com/dmlc/xgboost/blob/master/demo/guide-python/custom_objective.py. In particular:
preds = 1.0 / (1.0 + np.exp(-preds))  # transform raw leaf weight


Cargo.toml: structopt: Migrate to clap

According to https://github.com/TeXitoi/structopt/issues/525,
structopt has entered maintenance mode, and clap should be used
for new development.
* Migrate to clap so that nightly builds succeed as well.
This PR is dependent on https://github.com/parallaxsecond/parsec/pull/753

I triggered a nightly run in here: https://github.com/tgonzalezorlandoarm/parsec/actions/runs/8328515939

The failure in theCI - mismatch  checker, is expected, as a mirror PR is expected to be merged in parsec: https://github.com/parallaxsecond/parsec/pull/753


⚠ Bofrost.at has degraded performance

In 8938283, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1709 ms

Resolved: Bofrost.at performance has improved in 3d10e0b.


code128: Add minimal encodation algorithm (non-extended ASCII only)

Adapted from ZXing (props Alex Geller) - maybe 80% slower depending
on data & stack heavy but does improve some outcomes when FNC1s
present (GS1 or manual) although not much else it appears (the
previous algorithm was pretty good)
Prompted by tests added from PR #272, props lyngklip
This is the second of the alternative PRs (PR #275). You choose!

I'm wondering about the first Code 128 test case. I suspect a decoder might add 128 to those '9' digits because extended ASCII is active?

Yes you might think that but extended mode only applies to "the ISO/IEC 646 value", i.e. to Code Sets A and B ASCII values, not to Code Set C double digit values, which aren't ASCII, so C mode stuff can be freely intermixed with extended mode shifts and latches.

ChatGPT seems to agree with you once I helped it understand the question. That makes encoding a bit more complex, right - interesting. I was under the impression that FNC4 insertion was a "preprocessing" step. This would mean that sequences of extended ASCII that mapped to ASCII digits might be encoded in character set C, and that does seem a bit odd even though it would not a problem so long as encoder and decoder agrees. But that's what the encoder did before, right?

Well that was a bug, which PR #275 fixes. Extended ASCII should never be encoded as Code Set C digits.

No time to weigh in right now, but I'll likely take this PR (over the other) once I've had time to review.
@gitlost Did the basis for the algorithm get written up anywhere? If we're significantly deviate from informative routine provided in the symbology specs then we should have some reference to signpost users to. (I've had to expend a lot of effort over the years convincing developers of pathological decoders that they need to fix decoding bugs, even if the codeword sequence is not the result of a reference encoder.)

The only write up really is that it's a standard algorithm, e.g. https://en.wikipedia.org/wiki/Divide-and-conquer_algorithm.
I'm concerned about performance, both speed and stack usage, so I'd hesitate to use it without trying it out first in some real-life cases if that's possible.
The performance checking I did I wouldn't be confident in, being just loops using usertime for timings with garbage collection turned off (-2 vmreclaim).

Here's the very simplistic performance test I used (mode128 is the Divide-and-Conquer one, code128 is the current):
2 vmreclaim
-2 vmreclaim

/tot 0 def
/startt usertime def
1 1 100 {
(^031^031_^127^159^031^159^159^159^15912345``^255^000^127^255^224^224^159`) (dontdraw parse) /mode128 /uk.co.terryburton.bwipp findresource exec
} for
/endt usertime def
/tot tot endt startt sub add def
(mode128 tot ) print tot ==

2 vmreclaim
-2 vmreclaim

/tot 0 def
/startt usertime def
1 1 100 {
(^031^031_^127^159^031^159^159^159^15912345``^255^000^127^255^224^224^159`) (dontdraw parse) /code128 /uk.co.terryburton.bwipp findresource exec
} for
/endt usertime def
/tot tot endt startt sub add def
(code128 tot ) print tot ==

2 vmreclaim
-2 vmreclaim

/tot 0 def
/startt usertime def
1 1 100 {
(^031^031_^127^159^031^159^159^159^15912345``^255^000^127^255^224^224^159`) (dontdraw parse) /mode128 /uk.co.terryburton.bwipp findresource exec
} for
/endt usertime def
/tot tot endt startt sub add def
(mode128 tot ) print tot ==

2 vmreclaim
-2 vmreclaim

/tot 0 def
/startt usertime def
1 1 100 {
(^031^031_^127^159^031^159^159^159^15912345``^255^000^127^255^224^224^159`) (dontdraw parse) /code128 /uk.co.terryburton.bwipp findresource exec
} for
/endt usertime def
/tot tot endt startt sub add def
(code128 tot ) print tot ==

Something that I've been thinking about: should it be made explicit what the encoder does when faced with the possibility of encoding part of the message in two different ways with the same length:

prefer ASCII > Extended or vice versa
prefer A>B>C or B>A>C or C>A>B etc.
prefer range shift to range switch or...
prefer character set shift to character set switch or...
prefer dangling digit at the front of an odd digit span or at the end
switch from ASCII A to Extended B using 100 100 100 or 101 101 100 etc.

There are possibly more alternatives than the ones I have listed. The reason I ask is that I've been playing with a somewhat rewritten encoder and I have come up with something where I can sort of control the priority of these things, but I still can't match all the test cases. The test cases in some places seem to prefer range switching over shifting and in other places the other way around. Unfortunately I have no insight into specifications.

Closing in favour of PR #278


[stable/neo4j] - Plugin Installation Issue - initContainer hanging...

I'm having an issue with initContainer plugin installation? Followed example provided but container hangs. I double checked if container does job on its own, it does (downloads the file). Anyone installing plugins using method from values.yaml?
K8S: 1.10.6
CHART: neo4j-0.8.0

--- POD
NAME                          READY   STATUS                  RESTARTS   AGE
pod/prod-neo4j-neo4j-core-0   0/1     Init:CrashLoopBackOff   497        1d

--- PV
Reclaim policy: Delete
Access modes: ReadWriteOnce

--- from values.yaml
    storageClass: "gp2"
.
.
  initContainers:
    - name: init-plugins
      image: "appropriate/curl:latest"
      imagePullPolicy: "IfNotPresent"
      volumeMounts:
      - name: plugins
        mountPath: /plugins
        command:
          - "/bin/sh"
          - "-c"
          - |
            curl -L https://github.com/neo4j-graphql/neo4j-graphql/releases/download/<IP_ADDRESS>/neo4j-graphql-<IP_ADDRESS>.jar
            cp neo4j-graphql-<IP_ADDRESS>.jar /plugins/

DESCRIBE POD:
kubectl describe pod/prod-neo4j-neo4j-core-0 -n neo4j
Name:           prod-neo4j-neo4j-core-0
Namespace:      neo4j
Node:           ip-172-212-100-77.ec2.internal/<IP_ADDRESS>
Start Time:     Sun, 28 Oct 2018 20:30:01 +0000
Labels:         app=neo4j
                chart=neo4j-0.8.0
                component=core
                controller-revision-hash=prod-neo4j-neo4j-core-58c8db464f
                heritage=Tiller
                release=prod-neo4j
                statefulset.kubernetes.io/pod-name=prod-neo4j-neo4j-core-0
Annotations:    <none>
Status:         Pending
IP:             <IP_ADDRESS>
Controlled By:  StatefulSet/prod-neo4j-neo4j-core
Init Containers:
  init-plugins:
    Container ID:   docker://44b2115cc1473370a0e3aef9e338bb4dbde09317f864bb606f2c2a39fc585b3b
    Image:          appropriate/curl:latest
    Image ID:       docker-pullable://appropriate/curl@sha256:c8bf5bbec6397465a247c2bb3e589bb77e4f62ff88a027175ecb2d9e4f12c9d7
    Port:           <none>
    Host Port:      <none>
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    2
      Started:      Tue, 30 Oct 2018 14:33:15 +0000
      Finished:     Tue, 30 Oct 2018 14:33:15 +0000
    Ready:          False
    Restart Count:  498
    Environment:    <none>
    Mounts:
      /plugins from plugins (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-zkzf7 (ro)
Containers:
  prod-neo4j-neo4j:
    Container ID:
    Image:         neo4j:3.4.5-enterprise
    Image ID:
    Ports:         5000/TCP, 7000/TCP, 6000/TCP, 7474/TCP, 7687/TCP
    Host Ports:    0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP
    Command:
      /bin/bash
      -c
      export NEO4J_dbms_connectors_default__advertised__address=$(hostname -f)
      export NEO4J_causal__clustering_discovery__advertised__address=$(hostname -f):5000
      export NEO4J_causal__clustering_transaction__advertised__address=$(hostname -f):6000
      export NEO4J_causal__clustering_raft__advertised__address=$(hostname -f):7000

      if [ "${AUTH_ENABLED:-}" == "true" ]; then
        export NEO4J_AUTH="neo4j/${NEO4J_SECRETS_PASSWORD}"
      else
        export NEO4J_AUTH="none"
      fi

      exec /docker-entrypoint.sh "neo4j"

    State:          Waiting
      Reason:       PodInitializing
    Ready:          False
    Restart Count:  0
    Environment:
      NEO4J_ACCEPT_LICENSE_AGREEMENT:                        yes
      NEO4J_dbms_mode:                                       CORE
      NUMBER_OF_CORES:                                       1
      AUTH_ENABLED:                                          true
      NEO4J_causal__clustering_discovery__type:              DNS
      NEO4J_causal__clustering_initial__discovery__members:  prod-neo4j-neo4j.neo4j.svc.cluster.local:5000
      NEO4J_SECRETS_PASSWORD:                                <set to the key 'neo4j-password' in secret 'prod-neo4j-neo4j-secrets'>  Optional: false
    Mounts:
      /data from datadir (rw)
      /plugins from plugins (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-zkzf7 (ro)
Conditions:
  Type           Status
  Initialized    False
  Ready          False
  PodScheduled   True
Volumes:
  datadir:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  datadir-prod-neo4j-neo4j-core-0
    ReadOnly:   false
  plugins:
    Type:    EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
  default-token-zkzf7:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-zkzf7
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason   Age                      From                                     Message
  ----     ------   ----                     ----                                     -------
  Warning  BackOff  3m45s (x11379 over 42h)  kubelet, ip-172-212-100-77.ec2.internal  Back-off restarting failed container

Somewhat old but for others interested I ran into this issue when loading a plugin not supported by my neo4j according to this version table https://github.com/neo4j-contrib/neo4j-apoc-procedures#version-compatibility-matrix
#10573


Add expires attribute into Header HTTP

[OO-FEATURES] Add expires attribute into the header of HTTP request.

:+1:


Replace error with warning

I thought this would be a quick fix as I don't love that it makes forklift look like something broke. This is untested since I do not have a forklift environment and likely wrong. Setting the pallet to false with the message is going to give the same result isn't it?
I wonder if there needs to be a fake crate with self.WARNING added to it rather than setting the pallet status to false or we override get_report and set the result?
@stdavis or @jacobdadams what do you think the correct solution is?
closes #4

Setting the pallet to false with the message is going to give the same result isn't it?

Yes, I believe that this wouldn't change the report at all.
I don't believe that we have modeled a way for pallets to have warnings. They are only pass/fail. This may be a shortcoming of forklift. The fake crate sounds a little sticky since forklift expects crates to point at real data. Maybe you could add it to the pallet after forklift has processed crates?

If I remember correctly, the whole point of using Forklift was to take advantage of it's automation and reporting framework. It was always kind of a weird fit for the lift/ship process.
Now that we've got Supervisor, I wonder if it isn't worth pulling fleetshare out of Forklift and making it its own standalone process?

One of the other major advantages of forklift was to prevent conflicts between separately scheduled tasks. If this doesn't apply to this project, then perhaps it would be good to get it out of forklift.

This is the only process updating that data, so I agree with moving it out of forklift.
I really need to get that slack handler built for supervisor.


View editor does not let me go back to normal mode

Describe the bug
After clicking the "expression" button, it will no longer let me go back to the previous view
To Reproduce
Steps to reproduce the behavior:

Go to view editor
Drag element to view
Click on element properties
Click on blue Expression button
Try to go back to the previous state

Expected behavior
I would expect to undo the expression thing
Screenshots

Desktop (please complete the following information):

OS: macOS
Browser: Firefox
Version 77.0.1

Fixed in 4ccf905c1dd7566bdeae4ef6fa20abdef68785cc


i'd need some help running this library

I have teltonika .txt file that needs to be parsed. How could I reuse your code?

Hi @grmkris , do you still need help?

hi thanks for your response :) I managed to do everything I needed

I am very happy that everything is solved. Closing for now :+1:


feat: add metatag

Changes:

Add Basic Meta Tag
Add Open Graph Meta Tag
Add Twitter Meta Tag

Screenshots

Line

Telegram (forever loading zzz)

Instagram

Twitter

Discord

Resolves #5

lgtm, thx kak!


Remove package-lock.json

No need for the packge-lock probably created by mistake.

Why? The good practice is to have it pushed.

Why? The good practice is to have it pushed.

This is a python project, no need for npm dependencies, the file was created by mistake most probably.

👍 Cool


Some AT and metrics values being passed by the COS buckets submodule are being ignored

In https://github.com/terraform-ibm-modules/terraform-ibm-cos/blob/main/modules/buckets/variables.tf the bucket_configs variable has the following section:
activity_tracking = optional(object({
      read_data_events     = optional(bool, true)
      write_data_events    = optional(bool, true)
      activity_tracker_crn = optional(string, null)
    }))

However the root level module does not allow you to set the values for read_data_events or write_data_events - they are hard coded to true so whatever value is passed via the bucket_configs variable is actually ignored when bucket is getting created.
2 options:

Expose read_data_events and write_data_events in the root level module and allow the bucket submodule to set them
Remove them from the bucket_configs variable.

Same issue goes for metrics_monitoring:
metrics_monitoring = optional(object({
      usage_metrics_enabled   = optional(bool, true)
      request_metrics_enabled = optional(bool, true)
      metrics_monitoring_crn  = optional(string, null)
    }))

Draft PR (still waiting on 1.67.0 to be released): https://github.com/terraform-ibm-modules/terraform-ibm-cos/pull/660


Lyte2D's Lua module loader implementation does not handle folders with 'init.lua' files in them

Assume you have mylibrary with init.lua inside it. require "mylibrary" should load it (unless there's also a mylibrary.lua file.)
This is not implemented.
Workaround: require "mylibrary.init"

Fixed in main. to be released yet (with other changes.)


Add test functions to neon_test_utils to consume CPU, memory, or local disk.

This is handy for testing VM autoscaling.

Superseded by https://github.com/neondatabase/neon/pull/6747, closing


govendor fetch doesn't update packages correctly

I've been using govendor for dbxcli (https://github.com/dropbox/dbxcli) -- thanks! But everytime I try to update existing dependencies to their latest version, it doesn't work.
Specifically, running govendor fetch +v doesn't ever actually update dependencies -- all it does is update vendor.json thus:
index d9601df..170e13e 100644
--- vendor/vendor.json
+++ vendor/vendor.json
@@ -14,105 +14,129 @@
                },
                {
                        "checksumSHA1": "rhL7Byz/kUm7SwqG/cJsvcitWWA=",
+                       "origin": "github.com/dropbox/dbxcli/vendor/github.com/dropbox/dropbox-sdk-go-unofficial",
                        "path": "github.com/dropbox/dropbox-sdk-go-unofficial",
-                       "revision": "04e7072d0476c888b95bbad87858dad2416ef0d5",
-                       "revisionTime": "2016-04-27T04:32:50Z"
+                       "revision": "b23826e33adf9d33a45436ec5b3866d333608924",
+                       "revisionTime": "2016-07-17T23:26:49Z"
                },
                {
                        "checksumSHA1": "duzh0ljtcNs9gO/4sBTC7lY6WL0=",
+                       "origin": "github.com/dropbox/dbxcli/vendor/github.com/dropbox/dropbox-sdk-go-unofficial/apierror",
                        "path": "github.com/dropbox/dropbox-sdk-go-unofficial/apierror",
-                       "revision": "04e7072d0476c888b95bbad87858dad2416ef0d5",
-                       "revisionTime": "2016-04-27T04:32:50Z"
+                       "revision": "b23826e33adf9d33a45436ec5b3866d333608924",
+                       "revisionTime": "2016-07-17T23:26:49Z"
                },
                {
                        "checksumSHA1": "/9uzGxiG9Zg+cnXizYfdIzkUfS0=",
+                       "origin": "github.com/dropbox/dbxcli/vendor/github.com/dropbox/dropbox-sdk-go-unofficial/async",
                        "path": "github.com/dropbox/dropbox-sdk-go-unofficial/async",
-                       "revision": "04e7072d0476c888b95bbad87858dad2416ef0d5",
-                       "revisionTime": "2016-04-27T04:32:50Z"
+                       "revision": "b23826e33adf9d33a45436ec5b3866d333608924",
+                       "revisionTime": "2016-07-17T23:26:49Z"
                },
                {
                        "checksumSHA1": "30D0xboCEw38dYql2ufJk2oczPs=",
+                       "origin": "github.com/dropbox/dbxcli/vendor/github.com/dropbox/dropbox-sdk-go-unofficial/files",
                        "path": "github.com/dropbox/dropbox-sdk-go-unofficial/files",
-                       "revision": "04e7072d0476c888b95bbad87858dad2416ef0d5",
-                       "revisionTime": "2016-04-27T04:32:50Z"
+                       "revision": "b23826e33adf9d33a45436ec5b3866d333608924",
+                       "revisionTime": "2016-07-17T23:26:49Z"
                },
...

Note the new origin field.
Contrast this with the following (which, ideally, should be equivalent, unless I'm misunderstanding what/how govendor fetch is supposed to do): govendor fetch $(govendor list -no-status +v)
This actually updates the packages as expected:
        modified:   vendor/github.com/dropbox/dropbox-sdk-go-unofficial/files/interface.go
        modified:   vendor/github.com/dropbox/dropbox-sdk-go-unofficial/impl.go
        modified:   vendor/github.com/dropbox/dropbox-sdk-go-unofficial/sharing/interface.go
        modified:   vendor/github.com/dropbox/dropbox-sdk-go-unofficial/team/interface.go
        modified:   vendor/github.com/dropbox/dropbox-sdk-go-unofficial/users/interface.go
        modified:   vendor/github.com/spf13/cobra/command.go
        modified:   vendor/vendor.json

Am I missing something? Otherwise this seems very surprising and counter-intuitive.

This is indeed a bug.
I'll look into and add a regression test.


Replace --force flag with --dev-release?

--force feels like it's ignoring errors, or deleting things. Really maybe this flag should be --dev-release.
It would also rightly discourage people from using the --force flag "to just stop the errors" and instead make them recognize what they're doing is not creating a production ready release?

Replacing it would be backwards-incompatible, and I would strongly veto that.

As an alias and deprecate force?

Alias, maybe. Deprecate, definitely not.

@Benjamintf1, Aliasing --force by --dev-release does not seem to be a good idea since --force is not equivalent of building a dev release. It only deactivates the git dirty state check and --final and --force flags are not mutually exclusive.
Another possible approach could be to disable dirty git check by default when building a dev release (ie. flag --final not given). The idea behind this being:

when I want to build a final release: I'm glad that git dirty state is checked and I can deactivate it if needed
when I want to build a dev release: I just want my tarball, I don't care about git, generated files aren't even known to git

I guess I'm forgetting that dev-release is it's own concept and can be finalized too. Perhaps --dev-release is a poor overloaded term here.
I do worry the degree i've seen --force --final out in the field and I wonder if changing the flags that are used could discourage these sort of patterns.

I also agree that the change should be backwards compatible. Looking into the bosh create-release --help the --force flag explanation is quite clear Ignore Git dirty state check. The dirty state of the git repository could have an affect to the generated bosh-release that is why I think is a good idea to require explicit confirmation from the user that it is OK to ignore the dirty state. Even removing the check only for the dev releases is backwards-incompatible change and I'n not sure whether we should go that way. If yes, at least we should print a warning during the release generation.

It feels like this discussion has reached its natural conclusion and no further actions are needed.


Error-summary: Use link solid variant and matching black bullet points

Ref. slack: https://posten.slack.com/archives/C4U4PR0A2/p1730733569538909?thread_ts=1730382966.771939&cid=C4U4PR0A2

The red unline doesn't validate with the yellow background (2.64:1)

Before
After

trello.com/c/rMvu5zwL


Bug fix/back button behaviour

Description
Captures back button taps when FullscreenActivity is the current Activity and checks if the WebView has a back history item. If it does, the WebView performs the back navigation otherwise the back press is delegated to the Activity.
Issues Resolved
Fixes #6
Check List

[ ] New functionality includes testing. - Not included as we would only be testing the framework
[ ] New functionality has been documented in the README if applicable. N/A

This got implemented by @zoli in #27 and then converted to Kotlin by @berhram in #29, so I guess this PR is redundant and can be closed?


Update FASTA parser to be configurable, generic, track line numbers, and other changes

Apologies for the large diff! Much of it is comments and tests, though.
These changes make the FASTA parser more flexible, and will allow us to handle FASTA files the way we need for SecureDNA (SDNA employees, refer to the "Notes" section in [[Alpha API endpoint]] on the internal wiki).
Changes
Adds 2 new settings: allow_preceding_comment and concatenate_headers. These are described in the doc comments, but briefly:

allow_preceding_comment = true will ignore any content preceding the first header, like before. If false, it will emit that content as a headerless (header = "") record.
concatenate_headers = true will glue successive headers with no content together with newlines. If false, it will use the old behavior and emit content = "" records. See the doc comment for a doctest that explains this.

The return value of FastaParser is now a FastaRecord with header and contents fields, instead of a 2-tuple. It's also grown a line_range field which gives the line numbers of the record (including header, 1-indexed, [start, end)).
Removes DnaFastaParser and SimpleFastaParser in favor of a single FastaParser type which is generic over FromStr types. Since String has an (infalliable) FromStr impl, SimpleFastaParser is now FastaParser<String>, and DnaFastaParser is now FastaParser<DnaSequence>. We didn't have this type before, but a hypothetical ProteinFastaParser is now FastaParser<ProteinSequence>, and you could even have FastaParser<u64> if you wanted that.
FASTA parsing is now state-machine-driven, which should make a non-allocating API easier to add in the future if we want, and also simplified the parsing code since it was getting hairy handling the new special cases in the old loop. Luckily most of @mkysel 's parsing logic was relatively straightforward to port into the state machine without too many changes besides handling the new settings.
The old tests are all redone to use the new API (and to test all 4 settings combinations, where it makes sense), and a bunch of new tests are added.
Misc changes:
parse now explicitly asks for a BufRead instead of taking Read and wrapping it internally in BufReader. I checked the ecosystem using SourceGraph and that seemed to be the way most Rust stuff works, so this brings our API in line with that.
There's a new parse_str method that takes advantage of &[u8] having a BufRead impl. That's part of the reason for the other change, too, since before that would have needlessly allocated a BufReader buffer which would bother me :-)

There's a new parse_str method that takes advantage of &[u8] having a BufRead impl. That's part of the reason for the other change, too, since before that would have needlessly allocated a BufReader buffer which would bother me :-)

I suspect @hwchen will have opinions here :)

re bufreader:

if it's not in the hotloop, it probably doesn't matter if there's an extra allocation for &[u8] (looks like csv takes this approach), but I understand the principle of it :)
if it's in the hotloop, perhaps it's better to just read the whole file instead of using bufreader? I don't know how large the FASTAs we expect to parse are, though, and perhaps this doesn't really make a difference in perf.

Those are my opinions :) but I don't have a problem with this approach. There's definitely less hidden allocation and I appreciate that.

My one concern with reading the whole file at once is what happens if someone tries to shove a gigabyte down our throats.  OTOH, if something else will break upstream, maybe that's less of a concern.  We probably want an optional parameter somewhere (the first place we might otherwise allocate a user-controlled and indefinitely-large object) which is a maximum-size limit, so we/providers can supply that with something reasonable.  I'd guess quickdna is probably actually not a bad place to put that, because it's the first stop for untrusted data.  And then we set that to something reasonable at our end and give providers the ability to override it if for some reason they want to accept a Gn input or something and know they can handle it..  [I'm less concerned about giant allocs on a benchtop because you're only hurting yourself, but we still probably want to have the BT just reject gracefully and not have some C/Java-side thing inside it blow up instead, and their developers may want this limit anyway.]

The rocket server already rejects too large requests. But it only applies to users that use the REST API endpoint, rather than using it as a library.

We won't be using Rocket in production in general---we could be getting some giant thing uploaded by a customer to a provider's web page or non-web API and then handing it to us as a library.  And we probably want this available for, e.g., a benchtop into which someone plugs a flash drive. :)  In general we should be as as paranoid as possible about user-supplied inputs, and this is an easy one for users to supply.  (We also need to be paranoid about network inputs, but that's a different issue.)

@hwchen re: BufReader, my feeling is both a) I prefer to not silently allocate, but more b) depending on system you may want to tune your bufreader size to optimal for your disk / ram / etc., and by hiding our bufreader inside the other one we make it harder for people to do that without stacking bufreaders and wasting memory (which may be important on a benchtop that only has <4kb of RAM...). Glad you agree :-)

@hwchen re: BufReader, my feeling is both a) I prefer to not silently allocate, but more b) depending on system you may want to tune your bufreader size to optimal for your disk / ram / etc., and by hiding our bufreader inside the other one we make it harder for people to do that without stacking bufreaders and wasting memory (which may be important on a benchtop that only has <4kb of RAM...). Glad you agree :-)
@Ravna re: DOS with large file, I agree but don't want to address that yet in this PR. I think the Vec-interface is working OK for alpha, and the state-machine-based parser will make implementing a streaming parser a lot easier in the future, and this PR is a bit big already...

Sure, re DoS, leave it the way it is, but can you make an issue so we don't forget?  (I may already have this in the testing zoo but should put it there if I don't.  Reading FASTA input is pretty much the only input we'll take where we don't know up front how big it's supposed to be anyway; I'm planning for the network protocol to give an up-front count anyway for everything where we control both ends.)


[consult]Is "ca" attribute not needed if cryptogen tool is used instead of CA

Context
Hello Caliper team:
My network has 2 orgs, and each org has 2 peers. And I didn't use CA server to create and publish certificates. Instead, I use the official script cryptogen to generate certificates.
So I want to confirm with you that in network configuration file, whether "ca" can be removed or not?

Thanks in advance.

@CoreyLin You are absolutely right, you don't need a CA if you don't use its services. Please run a test without the CAs, and let me know the result :)
(The new Fabric adapter #296 allows you to dynamically register and enroll users, so the CA could play a role in your tests, but it's optional, of course.)

Submitted #311 , so closing this related issue.


Remove Ethernet pairing with chip-tool in README

The chip-tool pairing ethernet subcommand has been removed in the latest chip-tool by this upgrades the Matter SDK to v<IP_ADDRESS>. This PR appropriately updates the affected command in README.

Superseded by https://github.com/canonical/matter-pi-gpio-commander/pull/20


Add ability to render components inside Notifications

Is your feature request related to a problem? Please describe.
Currently, we only allow rendering text as the content inside a Notification. Additionally to that, it should be possible to render advanced content aka Components inside them, for example Button, Actions and so one.
One Example can be the Run Success Notification which regards #1552.

Describe the solution you'd like
Add the ability to render components inside a Notification.
Describe alternatives you've considered
/
Additional context

Notification component

Found out it already works as intended:
const {
   displayNotification
}  = this.props;

 displayNotification({
      type: 'error',
      title: 'foo',
      content: (FooComponent(foo)),
      duration: 10000
 });

function FooComponent(foo) {
   return (<div>{ foo }</div>
}

I'll add a test case which verifies that.

Seems like the current test coverage covers this enough. So no work needs to be done.


Add mode-style setting for tmux 2.9

Changes highlight color from default yellow to cyan
Affects copy mode and windows (C-b w) list
Works for tmux 2.9+
Works with #34

Hi @nikita-y :wave:, thanks for your contribution :+1:
I'll review your PR right after #34. This ensures the theme doesn't break when using tmux version <=2.9.

Hi @arcticicestudio
Any chance this could be merged or integrated in some way?
I tested it and seems to work on tmux 3.3a (archlinux)


Animal database

In this pull request I implement SQL vet_clinic database following these steps:
Use this template to generate your repo.

[ ] Create a database named vet_clinic.
[ ] Create a table named animals with the following columns:

d: integer
name: string
date_of_birth: date
escape_attempts: integer
neutered: boolean
weight_kg: decimal

[ ] Copy the SQL you used in the previous point into the schema.sql file in the generated repository.

[ ] Insert the following data:

Animal: His name is Agumon. He was born on Feb 3rd, 2020, and currently weighs 10.23kg. He was neutered and he has -
never tried to escape.
Animal: Her name is Gabumon. She was born on Nov 15th, 2018, and currently weighs 8kg. She is neutered and she has tried to escape 2 times.
Animal: His name is Pikachu. He was born on Jan 7th, 2021, and currently weighs 15.04kg. He was not neutered and he has tried to escape once.
Animal: Her name is Devimon. She was born on May 12th, 2017, and currently weighs 11kg. She is neutered and she has tried to escape 5 times.

[ ] Copy the SQL you used in the previous point into the data.sql file in the generated repository.

[ ] Write queries for the following quests:

Find all animals whose name ends in "mon".
List the name of all animals born between 2016 and 2019.
List the name of all animals that are neutered and have less than 3 escape attempts.
List the date of birth of all animals named either "Agumon" or "Pikachu".
List name and escape attempts of animals that weigh more than 10.5kg
Find all animals that are neutered.
Find all animals not named Gabumon.
Find all animals with a weight between 10.4kg and 17.3kg (including the animals with the weights that equals precisely 10.4kg or 17.3kg)
-Take a screenshot of the results of your queries.

Thank you so much for the review. I have updated the screenshots of all the queries. Please check ..


xfce4-clipman-plugin is missing from the base image

xfce4-clipman-plugin is the clipboard manager for xfce and an xfce4-panel plugin. It handles both manual copies and selections and it saves copy history across sessions. It's an incredible quality-of-life tool.

xfce4-clipman-plugin added to the base image in 6ddb635. Thanks!


Fix some undefined classes in the host script

The script host_tools/python/gpu_cc_tool.py, which configures the CC mode of the GPU, has some undefined (but used) classes.
Two usages are modified:

NvSwitch. The deployment guide of EA of Nvidia Confidential Computing does not include introduction of NvSwitch, so I try skipping its configuration.
IntelRootPort. It might be feasible to treat IntelRootPort as PciBridge

Fixed in https://github.com/NVIDIA/nvtrust/commit/6296b7a8dce48a65202fcf7358453874d47ed6a0


Broken Link

Note: This form is for submitting issues about Volt MX documentation, not Volt MX itself. For Volt MX support, please visit the HCL Software Customer Support Portal at https://support.hcltechsw.com.
Description
In Java PreProcessor and PostProcessor on https://opensource.hcltechsw.com/volt-mx-docs/95/docs/documentation/Foundry/voltmx_foundry_user_guide/Content/Java_Preprocessor_Postprocessor_.html, first link to Volt MX App Services is broken. It's pointing to .md instead of .html
Observed

Desired
Link in line 36156 should be same as link in 36162, https://github.com/HCL-TECH-SOFTWARE/volt-mx-docs/blob/master/docs/95/docs/documentation/Foundry/voltmx_foundry_user_guide/Content/Java_Preprocessor_Postprocessor_.html#L36156
Topics
URLs of topics affected.
To Reproduce
In "Java PreProcessor and PostProcessor" section click on first link that says "Volt MX App Services API". Link doesn't work. Click on second link that says "Volt MX App Services API". Link works.

@paulswithers I have created a pull request for this problem please verify it and merge it

Hi @paulswithers, the fix is published to production. You may see it here: https://opensource.hcltechsw.com/volt-mx-docs/95/docs/documentation/Foundry/voltmx_foundry_user_guide/Content/Java_Preprocessor_Postprocessor_.html
(@davidsayer57

The issue is fixed.


权重下载时报错Bad Request

您好，在复现demo时遇到了一些问题，辛苦帮忙看一下～
运行命令
python cli_demo.py --from_pretrained cogvlm-chat-v1.1 --version chat --english --bf16

报错如下
/home/heyu/anaconda3/envs/cogvlm/lib/python3.9/site-packages/urllib3/connectionpool.py:1061: InsecureRequestWarning: Unverified HTTPS request is being made to host 'c8a00746a80e06c4632028e37de24d6e.r2.cloudflarestorage.com'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/1.26.x/advanced-usage.html#ssl-warnings
  warnings.warn(
Failed to download or check, if you already had the zip file, please unzip it manually as /home/heyu/.sat_models/cogvlm-chat-v1.1!
Traceback (most recent call last):
  File "/mnt/disk1/yuhe/codes/CogVLM/cli_demo.py", line 154, in <module>
    main()
  File "/mnt/disk1/yuhe/codes/CogVLM/cli_demo.py", line 34, in main
    model, model_args = CogVLMModel.from_pretrained(
  File "/home/heyu/anaconda3/envs/cogvlm/lib/python3.9/site-packages/sat/model/base_model.py", line 215, in from_pretrained
    return cls.from_pretrained_base(name, args=args, home_path=home_path, url=url, prefix=prefix, build_only=build_only, overwrite_args=overwrite_args, **kwargs)
  File "/home/heyu/anaconda3/envs/cogvlm/lib/python3.9/site-packages/sat/model/base_model.py", line 201, in from_pretrained_base
    model_path = auto_create(name, path=home_path, url=url)
  File "/home/heyu/anaconda3/envs/cogvlm/lib/python3.9/site-packages/sat/resources/download.py", line 68, in auto_create
    raise e
  File "/home/heyu/anaconda3/envs/cogvlm/lib/python3.9/site-packages/sat/resources/download.py", line 62, in auto_create
    download_s3(path, url[5:])
  File "/home/heyu/anaconda3/envs/cogvlm/lib/python3.9/site-packages/sat/resources/download.py", line 108, in download_s3
    bucket.download_file(remote_uri, os.path.join(local_dir, os.path.basename(remote_uri)),Callback=ProgressPercentage(client, SAT_BUCKET, remote_uri), Config=transfer_config)
  File "/home/heyu/anaconda3/envs/cogvlm/lib/python3.9/site-packages/sat/resources/download.py", line 134, in __init__
    self._size = client.head_object(Bucket=bucket, Key=filename)['ContentLength']
  File "/home/heyu/anaconda3/envs/cogvlm/lib/python3.9/site-packages/botocore/client.py", line 553, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/home/heyu/anaconda3/envs/cogvlm/lib/python3.9/site-packages/botocore/client.py", line 1009, in _make_api_call
    raise error_class(parsed_response, operation_name)
botocore.exceptions.ClientError: An error occurred (400) when calling the HeadObject operation: Bad Request

没有权限访问c8a00746a80e06c4632028e37de24d6e.r2.cloudflarestorage.com

可以手动在魔搭或者huggingface下载checkpoint，然后把from_pretrained的参数替换成checkpoint的本地路径


JME displays, E and arrays

This particular problem arises in writing an expressions such as {a}E[X]+{b}E[Y] where {a} and {b} are variables possibly taking  0, 1 or negative values. E[X] etc is the standard way of writing expectation of a random variable.
So for display purposes it is natural to use \simplify[std]{{a}E[X]+{b}E[Y]} - but E[X] is taken to be asking for a value of an array in jme and even if you relax notation and use E(X), E is taken to be e=2.71.... One could use 'E[X]', but then the display is at variance with the latex display.
What can be done?

Two problems:
1 - E is interpreted as a number. You can use an annotation to stop this happening.
2 - square brackets mean take a value from a list. I suppose this doesn't matter as long as it gets TeXed right, if you're just doing display.
I've added some bits to the display code to get round these problems, but I forgot to tag this issue in the commit message. It's commit 0a232f04def8
You now have two options - use the op: annotation to get the E displayed properly:
\simplify{ {a}*op:E[X] + {b}*op:E[Y] }
or use the new verbatim function to just write stuff out in TeX inside a simplified expression:
\simplify{ {a}*verbatim('\operatorname{E}[X]') + {b}*verbatim('\operatorname{E}[Y]') }
The first option is a lot more concise but I thought this kind of thing is bound to come up again, so the second option is there in case we ever really need it.

Thanks, I like the second option as it really expands the use of simplify


Add SR-IOV net support to images in EC2 compute driver

Add SR-IOV net support to images in EC2 compute driver
Description
This change adds a missing configuration option while registering images. More documentation about this option here: https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_RegisterImage.html
Status

done, ready for review

Checklist (tick everything that applies)

[x] Code linting (required, can be done after the PR checks)
[x] Documentation
[x] Tests
[ ] ICLA (required for bigger changes)

👍  thanks @amisstea
I'll resolve that conflict


Support admins channel on ms teams

Blocked by strongdm/errbot-backend-botframework#7
Closes #297

2 things to fix:

sdm admin resources update cassandra --id rs-xxxx --tags 'approvers-channel="#general"'
Elevate admins with general (and maybe other channels) in MS Teams


read_csv_arrow() does not support ".csv.gz"

Hi,
I tried to read some ".csv.gz" files by using read_csv_arrow() and it gave me such an error message "Error in url(file, open = "rb") : URL scheme unsupported by this method." However, I've never had such an issue by using readr::read_csv(). I am not sure if this is a bug or a feature that can be requested for the future releases.
Thanks!

This is probably ARROW-16619; #13625 should resolve this and a few related issues.


CS:GO server stuck on "starting", won't autostart

Bug Report
System Information

Operating System (Including distribution name and version number): Ubuntu 20.04 LTS
AMP version and build date (Always use the version number, 'latest' is not valid!): 2.3.3
Which AMP release stream you're using (Mainline, Nightly or FastTrack): MainLine

I confirm:

[x] that I have searched for an existing bug report for this issue.
[x] that I am using the latest available version of AMP.
[x] that my operating system is up-to-date.
[x] that my checkboxes above look exactly like the one on the left with no extra spaces. Remove this line to confirm you can follow instructions - if this line shows up in the bug report then the whole report will be ignored

Symptoms

What are you trying to do?
Starting CS:GO instance.

What are you expecting to happen?
The instance should start and show that it's up and running.

What is actually happening? ('Nothing' is not an acceptable answer!)
When AMP is restarted, it shows that the instance is running (autostart), however, the instance won't start until it is started manually. Once started, console won't display anything and application state would stay at "Application State: Starting", making it impossible to restart the instance as the only option shown is "abort" which would shut down the server.
The server is running just fine, but 0 information about it is being shown, it's always on 0 players and 0% CPU usage.

In main menu, it says the instance is running, but when in manage mode, it says it's still starting.
Reproduction

I installed AMP using "bash <(wget -qO- getamp.sh)" on Ubuntu 20.04 LTS.
For some odd reason, on first time setup, I couldn't log in with the password I set.
I cancelled the AMP setup and changed my password.
I logged in, completed first time setup and a started CS:GO instance.
I updated the instance, and once I started it the issue appeared.

Have you specified a GSLT token and IP address?

Closed due to inactivity, likely user-error.


Allow RGBA tiles for "*OnlyLabels" maps

Currently, downloaded tiles are implicitely converted to RGB images.
https://github.com/geopandas/contextily/blob/37ac810a6f159be64855585c6fcab63a6f681673/contextily/tile.py#L305
However, since leaflet-providers supports maps with decomposed map and overlay labels, the maps with only labels need to be opened as RGBA images. PIL is also complaining about RGB casting on palette images.
.../lib/python3.6/site-packages/PIL/Image.py:960: UserWarning: Palette images with Transparency expressed in bytes should be converted to RGBA images

Minimal working example to reproduce the behavior:
import geopandas
import matplotlib.pyplot as plt

df = geopandas.read_file(geopandas.datasets.get_path('nybb'))
df = df.to_crs(epsg=3857)
ax = df.plot(figsize=(10, 10), alpha=0.5, edgecolor='k')

provider = contextily.providers.CartoDB.DarkMatterNoLabels
contextily.add_basemap(
    ax=ax,
    source=provider,
)

provider = contextily.providers.CartoDB.DarkMatterOnlyLabels
contextily.add_basemap(
    ax=ax,
    source=provider,
    zorder=10,
    alpha=0.5  # this makes the background map and polygons visible
)

plt.show()

@razorx89 thanks for opening the issue!
There is currently an open PR that I think does exactly what you are suggesting: https://github.com/geopandas/contextily/pull/114

@razorx89 thanks for opening the issue!
There is currently an open PR that I think does exactly what you are suggesting: #114

Yep, #114 fixes this.  You also wouldn't need to have alpha=0.5 on the labels-only layer.


flutter/packages CI scripts need access to channel

The flutter/packages repository needs to test with both Flutter master and Flutter stable, and sometimes specific tests need to know which mode they are running under (e.g,. tests with golden files or that rely on auto-formatting need to be skipped on one of the two channels, because it's periodically impossible to pass on both).
With Cirrus, we put the channel into the environment, so scripts just check Platform.environment['CHANNEL']. Ideally we would have the LUCI recipe propagate the existing channel property from the CI config into the environment as CHANNEL so everything would keep working the same way, but I'm open to other options.

The channel is already a property: https://github.com/flutter/packages/blob/main/.ci.yaml#L122, this can be done by directly adding the channel to env.

@yusuf-goog Is this something you could take care of adding to the recipe?

Yes, I'll take care of it.

fix in https://flutter-review.googlesource.com/c/recipes/+/46900

@stuartmorgan please confirm the fix is working for you

It does indeed (https://github.com/flutter/packages/pull/4404), thanks for turning that around quickly!


docs: pdf files uploaded

Issue #, if available: GALI-1061
Description of changes: missing PDFs are uploaded
Checklist:

[ ] Have you successfully deployed to an AWS account with your changes?
[ ] Have you written new tests for your core changes, as applicable?
[ ] Have you successfully tested with your changes locally?
[ ] If new dependencies have been added, have they been pinned to specific versions?
[ ] Is this change also required on the AWS Solution version?
[ ] Have you updated openapi.yaml if you made updates to API definition (including add, delete or update parameter and request data schema)?
[ ] If you had to run manual tests, have you considered automating those tests by adding them to end-to-end tests?
[ ] If you are updating the changelog and vending out a new release, have you updated versionNumber and versionDate in .defaults.yml

AS review ticket id:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@shyogesh-sw Does this need to be merged in? This PR shows the 2 pdfs being deleted.

Looks like the relevant PR was already merged in
https://github.com/awslabs/service-workbench-on-aws/pull/842
Closing PR 841. Please reopen this PR if it's still needed.

@shyogesh-sw Does this need to be merged in? This PR shows the 2 pdfs being deleted.

Hi Tim, no, this is not required to be merged.


GitLeaks throwing "too many open files" error when running with the --no-git option

Describe the bug
When running the "gitleaks" command against a git repository that's locally checked out on Mac OS X, it throws a "too many open files" error:
gitleaks --path=. -v --no-git
ERRO[0000] open .git/objects/06/c465fef0df46ca67970792e4a3b31695bd6498: too many open files
INFO[0000] scan time: 485 milliseconds 934 microseconds
ERRO[0000] open .git/objects/06/c465fef0df46ca67970792e4a3b31695bd6498: too many open files

The reason for running with the "--no-git" option is that I would like to only scan the current revision of the repository (all the files, not just the ones referenced by the latest commit).
The error seems to be being thrown due to GitLeaks scanning the ".git" repo in particular, which has a lot of files.
Other things I've tried to work around the above with no success are:

Running with "threads=1" to try and reduce the number of files that the program opens "gitleaks --path=. -v --threads=1 --no-git"
Moving the ".git" directory out of the checked out repository temporarily

To Reproduce
On a machine running OS X 11.4, clone a large-ish Git repository.
Install gitleaks, change directory into the repository and run:
gitleaks --path=. -v --no-git

Expected behavior
I would expect that gitleaks scans the directory without throwing an error and identifies any secrets in files as per normal.
Screenshots
N/A
Basic Info (please complete the following information):

OS: Mac OS X 11.4
Gitleaks Version: 7.5.0

Additional context
The OS X system max open file limits are set to the following (after increasing):
$ launchctl limit maxfiles
	maxfiles    65536          1048576

cc @zricethezav

Could this PR -> https://github.com/zricethezav/gitleaks/pull/590 fix this issue?

@srkiNZ84

The error seems to be being thrown due to GitLeaks scanning the ".git" repo in particular, which has a lot of files.

Damn, true. Thanks for pointing that out. Gotta fix that

Damn, true. Thanks for pointing that out. Gotta fix that

Just note that I did try moving the ".git" directory and it's files out of the way and it was still throwing the error, though it did manage to get a bit further in terms of scanning. So, there might still be an issue even without scanning the .git repository.

Temporarily set ulimit to a larger value in linux, such as:
$ ulimit -n 524288

This worked for me.

Temporarily set ulimit to a larger value in linux...

Yeah, I tried this as well. Not sure why it doesn't work on OS X 🤷

I'm seeing something similar. I've tried various different regexes to exclude all node_modules directory and the .git directories but I can't get anything to work. Do you have any suggestions of what regex to use here?
MacOS 11.4
gitleaks 7.5.0
$ gitleaks -v --config-path=gitleaks.toml --no-git --path=./
ERRO[0000] open node_modules/.cache/babel-loader/6d8063beb61e7aeac6d81316036a7468.json: too many open files
INFO[0000] scan time: 59 milliseconds 48 microseconds
ERRO[0000] open node_modules/.cache/babel-loader/6d8063beb61e7aeac6d81316036a7468.json: too many open files

gitleaks.toml
title = "gitleaks config"

[[rules]]
description = "JSON Web Token"
regex = '''eyJ[A-Za-z0-9-_=]+\.[A-Za-z0-9-_=]+\.?[A-Za-z0-9-_.+/=]*?'''
tags = ["key", "jwt"]

[allowlist]
description = "Allowlisted files"
files = [
  '''.*node_modules.*''',
  '''\.git''',
]

Temporarily set ulimit to a larger value in linux, such as:
$ ulimit -n 524288

This worked for me.

If the code is working the way I intended it (limited number of concurrent files open), then you really shouldn't have to set ulimit. Something fishy is going on. One easy solution would be to scrap multi-processing of --no-git altogether. This would increase the scan time significantly but would ensure no more too many files opened errors get thrown.
Who's got opinions... lets hear em

i too face the same issue. Could you please provide high priority to fix this one .

@jboler @srkiNZ84 do either of you have example repos I can try reproducing this on? The concurrency pattern found in the nogit scanner is pretty straight forward and based off of https://www.oreilly.com/content/run-strikingly-fast-parallel-file-searches-in-go-with-sync-errgroup/

@jboler @srkiNZ84 found the issue, turns out I wasn't limiting the number of goroutines spinning up :/
Gonna throw a limiter on it like the other scans

Thanks!

found the issue, turns out I wasn't limiting the number of goroutines spinning up :/

Awesome! Thank you! Sorry I wasn't more helpful in identifying the issue

https://github.com/zricethezav/gitleaks/pull/619 going into next release

@jboler @srkiNZ84 should be fixed in 7.6.0, feel free to reopen if you find it still broken

should be fixed in 7.6.0, feel free to reopen if you find it still broken

have upgraded, ran the command with "--no-git" that was consistently failing before and it is working now! Thank you so much! 🙂


Example of Instruction-Tuning Training

Hello, thank you for open-sourcing this work. We are now interested in generating our own instructions to fine-tune the Llama model based on your documentation and approach. Could you please advise on any resources or references we can use? Also, are these codes available on Hugging Face?

Hi @BowieHsu
this repo contains the relevant code for generating instructions and check the README for how to run that

@Tiiiger Hi, thank you for your response.
Your documentation is excellent, and I now understand the instruction generation approach.
Now I want to reproduce the training task and I found this repository, https://github.com/nebuly-ai/nebullvm, which seems to have a similar instruction fine-tuning training approach as yours. Is it consistent with your training method, and are there any codes that can be referenced there?

hi @BowieHsu unfortunately we have no knowledge of this repo and cannot be more helpful.

Hi,
Quick update - We have released the training code, see https://github.com/tatsu-lab/stanford_alpaca#fine-tuning. Hope this is helpful.

@rtaori Thank you, my friend. I'll have all my GPUs running at full power to express my gratitude.


Performance issues

Running list of lagginess complaints, quotes:

If I try to unfollow notifications the UI reaction time is very very
slow. I thought the Unfollow button was doing nothing at all at first. Here is a screencast how it looks for me: https://upload.kikeriki.at/file_share/paWGzJXam_nWVVGZz61vf5P6/metaculus-follow.mp4 (user: t.b - reported at 6:17 PM Eastern Sep 9)
I also experienced extremely long UI delays when trying to change the
language. I think it was a full minute. It really feels like the
buttons are not working at all. (t.b - ditto)
The question details / resolution criteria / background info load async and can take quite a while, which degrades the experience a bit. I bet this is mostly because the beta server might be on limited resources. But I thought I'd note it here anyway: assuming a faster prod deploy, it still could be frustrating on mobile, on a poor network, etc. If those could load synchronously that'd be much nicer! [I think @lsabor said it's not a problem of async loading nor resources but this is what draaglom said - reported at 5:35 PM Eastern Sep 3]
Every new page load (question pages, tournament pages…) was slow for me. Also specific actions such as Following/Unfollowing a question took far longer than before. If before it was around a second per load/action, now it was even 3-5 seconds at times… roughly. (user: Zaldath - they had said 2 or 3 times slower - reported at 5:44 PM Eastern Sep 9) Note: at 11:30 AM Eastern Sep 10 they said they tested it again and everything seemed to work considerably faster :shrug:
"The site feels slower overall." (skmmcj at Sep 9 9:30 PM Eastern)

Here's t.b's screencast:
https://github.com/user-attachments/assets/6222b8c9-2577-40e9-8044-aff7241ad975

Current results:

Under stress testing the dev env performs well when resources == prod (i.e. the beta. domain)
We should make sure our database is large enough
Current issues look to be quite random and often have to do with data that's already loaded, so I think @ncarazon we should make sure there are no situations in which our next frontend might arbitrarily freeze


paint 3d

hey i could help you work on paint 3d in js
using threejs

You could fork this and add it.

haha ok


Concurrent executor failover to serial queue

There are two important changes, here:

The parallel executor will never use the last MIN_CAPACITY (currently 64) slots of a bounded executor queue.  That leave a fair amount of space for serial queues (2 slots per queue) and other application stuff.
When the parallel executor exhausts execution resources (availCapacity - MIN_CAPACITY <= 0) it fails over to using an unbounded serial queue.  This means that the failure mode for, e.g., conflict revolvers that permanently block all execution, will be an eventual OOM.  Before the OOM warnings will be logged to help identify the actual problem.  Unfortunately, though, because the queue is unbounded, there will be no helpful execution queue dump.
All tests passing on all platforms

This is a bit hard to follow given all the formatting changes that also took place, but I gave it a shot.

@borrrden  Yes.  Sorry about that.  It is, essentially, a rewrite.  I suggest reading the new code, and not the changes.

I believe that there are 3 bugs here:

Pasin described a condition in which, if the serial queue in non-empty, a task can be lost
Pasin and Jim both pointed out that if an task from the serial queue is rejected, the queue is hung forever.  The implementation of the SerialExecutor addresses this; the implementation needs to be pulled over.
I noticed that when the serial queue dispatches multiple items (because there is space available in the underlying executor), each (instead of only one) of them will reschedule from the queue.

I believe I have addressed all of the issues.  I have not yet run tests, and I think it is worth adding a couple more.  I would like to get your eyes on the new code, though ASAP.

All tests pass.  I still think I will add a couple more.  Esp for queue restart.

@bmeike Need help to understand the definition or functionality of the restartQueue(). From the code, the execute one task from the top of the pending queue and when it's done it will try to execute a lot of tasks in the pending queue until the space is not available. Is it by design to execute only one task from the pending queue first (why we don't try to execute all the tasks in the pending queue)?

RestartQueue does exactly what its name implies. It tries to schedule the head of pendingQueue on the executor.  In order to "restart" the queue, that task must call scheduleNext on completion.  If the method succeeds, it clears needsRestart, because the queue has been restarted.  If it fails it sets needsRestart because there is no running task that will schedule the next task.

Added a test for serial queue restart.  It even found a heinous bug in the logging routine!
It is proving much harder to write a test for restarting the concurrent executor.

Added a test for concurrent queue restart.

I am not delighted with this solution.  It does mitigate the biggest problem we have had so far: A serial executor getting an REE.  With that in mind, I am going to merge it to Mercury, with a note that the design needs to be revisited.


[Feature] support for multiple zendesk connectors

Is there an existing feature request for this?

[X] I have searched the existing issues

Describe the Feature
Feature to use this package for multuple Zendesk connectors simultaneously.
This feature is already implemented in dbt-xero packages: unioning-multiple-xero-connectors
Describe alternatives you've considered
No response
Are you interested in contributing this feature?

[ ] Yes.
[ ] Yes, but I will need assistance and will schedule time during your office hours for guidance.
[ ] No.

Anything else?
No response

Hi @mhadole-tc thanks so much for opening this Feature Request. I think this would be a great feature enhancement.
I am curious, what is the use case in your situation for multiple Zendesk connectors?

We have separate Zendesk instances for every line of business but the requirement is to have all the analytics in one dashboard/place. ideally, I am looking for combined  Zendesk models with individual Zendesk instance identier in models.

@mhadole-tc that makes sense to me and I can understand why you would want to have all the Zendesk models under one hood.
This is feature request is most likely something we will pick up in a future quarter. Our next quarterly planning initiative will likely take place after the holidays. I will be sure to post back here once we decide to pick this up and integrate into the Zendesk package!
However, if you are interested in opening a PR for the package to have this support, I would be happy to help with any questions you may have. Otherwise, we will pick this up following the holidays!

hey there, looks like this got lost for a bit -- there's a duplicate ticket that is open (and soon to be worked on) here, so please follow along there! will close this issue to defer to the more recent one


Implemented the show/hide password funtionality

Description
Implemented the show/hide password funtionality
Fixed #184
Type of change
Please check options that are relevant to your PR.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] This change requires a documentation update

Checklist:

[x] I have pulled the latest changes in the repository
[x] I have squashed my commits
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

@abhay27chauhan Add cursor: pointer on hover. Rest is fine.

Should I give inline style?
On Sun, 4 Apr, 2021, 6:19 PM Vaishali, @.***> wrote:

@abhay27chauhan https://github.com/abhay27chauhan Add cursor: pointer
on hover. Rest is fine.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Girl-Code-It/Opportunity-Calendar-Frontend/pull/186#issuecomment-813027510,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKG5GE6XISFX6WAKNR7ZCSLTHBN65ANCNFSM42LJMEEA
.

Should I give inline style?
…
On Sun, 4 Apr, 2021, 6:19 PM Vaishali, @.***> wrote: @abhay27chauhan https://github.com/abhay27chauhan Add cursor: pointer on hover. Rest is fine. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#186 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKG5GE6XISFX6WAKNR7ZCSLTHBN65ANCNFSM42LJMEEA .

No, make the changes in CSS file.

@vaishali614 is it ok ?


Le modèle « Console Application » ne peut pas être créé. Failed to create template. Details: Access to the path 'C:\Windows\system32\myApp' is denied..

Problem encountered on https://dotnet.microsoft.com/learn/dotnet/hello-world-tutorial/create
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

This part is on that same page:

This error message means you cannot create the app on that directory. Try for example going to a different directory, like going to the users directory, and trying again cd %USERPROFILE%
Let us know if this worked.


doc: minor fix Japanese README

URL fix
Correct your expressions more fluently

Thanks for the contribution @eltociear


iOS deployment hangs forever at XamarinDownloadArchives task

We are currently facing an issue when trying to locally deploy and debug our .NET MAUI app using the most recent version of the barcode scanning library. While deployment and debugging works smoothly on Android devices, the iOS build task seems to hang forever when attempting to extract the package "GAppM-10.24.0" as part of the XamarinDownloadArchives task. Has anyone faced a similar issue?
As far as I've figured out, downgrading the Xamarin.Build.Download package to version 0.8.0 (or even lower) might mitigate this issue, this is however not really an option, as AdamE.MLKit.iOS.BarcodeScanning package demands for version 0.11.0 or higher. Somehow I'm stuck at this point...
https://stackoverflow.com/questions/60453145/the-xamarindownloadarchives-task-could-not-be-initialized-with-its-input-param

I am experiencing the same issue.

I found the problem on my machine.  I am building on Windows 10 which has a maximum path length of 260 characters.  XamarindDownloadArchives cannot extract GAppM-10.24.0 because the path of some of the resulting files would be too long.

If you try and compile it from the CLI with maximum verbosity and manually terminate the 7z process you'll find it tells you what it was trying to do.
Unpacking failed. Please download 'https                    ://dl.google.com/firebase/ios/analytics/cc4d75392af34c62/GoogleAppMeasurement-10.24.0.tar.gz' and extract it to the '%userprofile%\AppData\Local\XamarinBuildDownloadCache                    \GAppM-10.24.0' directory and create an empty file called '%userprofile%\AppData\Local\XamarinBuildDownloadCache\GAppM-10.24.0.unpacked'.
Do that and recompile the app, and it will magically work. The issue is with either the GAppM package or the 7z extractor


Toast is not displayed in AfterViewInit method

I'm trying to pop a toast on a ngAfterViewInit method, without success.
The code
@Component({
  selector: 'app-team-member-menu',
  templateUrl: './team-member-menu.component.html',
  styleUrls: ['./team-member-menu.component.css']
})
export class TeamMemberMenuComponent implements AfterViewInit {

  defaultToasterConfig = defaultToasterConfig;

  constructor(private toasterService: ToasterService) {}

  ngAfterViewInit() {
    console.log('entering view init');
    const toast: Toast = {
      type: 'success',
      body: 'I am init toast'
    };
    this.toasterService.pop(toast);
  }

  toto() {
    console.log('toto button clicked');
    const toast: Toast = {
      type: 'success',
      body: 'I am toto toast'
    };
    this.toasterService.pop(toast);
  }

The behaviour
(Note: my toast lifetime is 5 seconds)

After entering the view, I can see in the console the message "entering view init" but no toast, which is not expected.
And then, for example, if I click on button that triggers toto() in my template 2 sec after entering the view, I'll see toto toast for 5 seconds, and init toast for 3 seconds.

This means the init toast bas been kind of triggered, but for some reason it was not displayed !?!
** Notes **
I'm running Angular 6.0.0 and rxjs-compat to ensure compatibility.
Any idea? Thanks.

This is most likely due to running Angular 6 against the library prior to upgrade.
I am in the middle of creating an Angular 6 target release and I'll test your scenario against it.

Please test this against the new 6.0.0 release and confirm if it is still an issue.  Thanks!

Hi,
After upgrading to 6.0.0, it still have the exact same problem.

Thanks for confirming. I’ll take a closer look.

I can't reproduce this in the angular-cli demo app.  AfterViewInit properly fires a toast and it display for the correct duration.
Do you have a conflict where your toaster-container is being loaded in a sibling component or even AFTER TeamMemberMenuComponent is loaded?  You should always render your toaster-container as far up the component tree as possible and as early as possible so that you can target the container earlier rather than later.
In either case, I'll need a more detailed reproduction in order to identify the issue.


In a prow job creating deployment doesn't check the status before continuing to next deployment.

see difference in the logs running from cli vs running in a prow job.
in local the deployment waits until it is ready before continuing to the next one where in prow it just continues.
This causes the same time shifting problem  in the metrics  between pr and the release deployments I tried to solve by adding the ready probe .
this log is missing in the prow jobs.
Request for 'applying deployment:prometheus-test-pr-4448' is in progress. Checking in 10s

Command to run
./prombench gke resource apply -a $AUTH_FILE \
	-v ZONE:europe-west3-a -v PROJECT_ID:macro-mile-203600 -v CLUSTER_NAME:prow \
	-v PR_NUMBER:4448 -v RELEASE:v2.3.2 \
	-f components/prombench/manifests/benchmark

From local cli.
2018/08/06 13:46:33 resource created - kind: Namespace, name: prombench-4448
2018/08/06 13:46:33 resource created - kind: ServiceAccount, name: loadgen-scaler
2018/08/06 13:46:33 resource created - kind: ServiceAccount, name: prometheus
2018/08/06 13:46:33 resource created - kind: ClusterRoleBinding, name: loadgen-scaler
2018/08/06 13:46:33 resource created - kind: ClusterRoleBinding, name: prometheus-4448
2018/08/06 13:46:34 resource created - kind: Deployment, name: fake-webserver
2018/08/06 13:46:34 Request for 'applying deployment:fake-webserver' is done!
2018/08/06 13:46:34 resource created - kind: Service, name: fake-webserver
2018/08/06 13:46:34 Request for 'applying service:fake-webserver' is done!
2018/08/06 13:46:34 resource created - kind: ConfigMap, name: prometheus-loadgen
2018/08/06 13:46:34 resource created - kind: Deployment, name: prometheus-loadgen-scaler
2018/08/06 13:46:34 Request for 'applying deployment:prometheus-loadgen-scaler' is in progress. Checking in 10s
2018/08/06 13:46:44 Request for 'applying deployment:prometheus-loadgen-scaler' is done!
2018/08/06 13:46:45 resource created - kind: Deployment, name: prometheus-loadgen-querier
2018/08/06 13:46:45 Request for 'applying deployment:prometheus-loadgen-querier' is in progress. Checking in 10s
2018/08/06 13:46:55 Request for 'applying deployment:prometheus-loadgen-querier' is done!
2018/08/06 13:46:55 resource created - kind: Service, name: prometheus-loadgen-querier
2018/08/06 13:46:55 Request for 'applying service:prometheus-loadgen-querier' is done!
2018/08/06 13:46:55 resource created - kind: ConfigMap, name: prometheus-test
2018/08/06 13:46:55 resource created - kind: Deployment, name: prometheus-test-pr-44482018/08/06 13:46:55 Request for 'applying deployment:prometheus-test-pr-4448' is in progress. Checking in 10s
2018/08/06 13:47:05 Request for 'applying deployment:prometheus-test-pr-4448' is in progress. Checking in 10s
2018/08/06 13:47:15 Request for 'applying deployment:prometheus-test-pr-4448' is in progress. Checking in 10s
2018/08/06 13:47:25 Request for 'applying deployment:prometheus-test-pr-4448' is in progress. Checking in 10s
2018/08/06 13:47:35 Request for 'applying deployment:prometheus-test-pr-4448' is in progress. Checking in 10s
2018/08/06 13:47:46 Request for 'applying deployment:prometheus-test-pr-4448' is done!
2018/08/06 13:47:46 resource created - kind: Service, name: prometheus-test-pr-4448
2018/08/06 13:47:46 Request for 'applying service:prometheus-test-pr-4448' is done!
2018/08/06 13:47:46 resource created - kind: Deployment, name: prometheus-test-v2-3-2
2018/08/06 13:47:46 Request for 'applying deployment:prometheus-test-v2-3-2' is in progress. Checking in 10s
2018/08/06 13:47:56 Request for 'applying deployment:prometheus-test-v2-3-2' is done!
2018/08/06 13:47:56 resource created - kind: Service, name: prometheus-test-v2-3-2
2018/08/06 13:47:57 Request for 'applying service:prometheus-test-v2-3-2' is done!
2018/08/06 13:47:57 resource created - kind: Deployment, name: node-exporter-prometheus-test-v2-3-2
2018/08/06 13:47:57 Request for 'applying deployment:node-exporter-prometheus-test-v2-3-2' is in progress. Checking in 10s
2018/08/06 13:48:07 Request for 'applying deployment:node-exporter-prometheus-test-v2-3-2' is done!
2018/08/06 13:48:07 resource created - kind: Deployment, name: node-exporter-prometheus-test-pr-4448
2018/08/06 13:48:07 Request for 'applying deployment:node-exporter-prometheus-test-pr-4448' is in progress. Checking in 10s
2018/08/06 13:48:17 Request for 'applying deployment:node-exporter-prometheus-test-pr-4448' is done!
2018/08/06 13:48:17 resource created - kind: DaemonSet, name: node-exporter-nodes
2018/08/06 13:48:17 resource created - kind: Service, name: node-exporter
2018/08/06 13:48:17 Request for 'applying service:node-exporter' is done!

From a prow job
2018/08/06 10:21:40 resource created - kind: Namespace, name: prombench-4448
2018/08/06 10:21:40 resource created - kind: ServiceAccount, name: loadgen-scaler
2018/08/06 10:21:40 resource created - kind: ServiceAccount, name: prometheus
2018/08/06 10:21:41 resource created - kind: ClusterRoleBinding, name: loadgen-scaler
2018/08/06 10:21:41 resource created - kind: ClusterRoleBinding, name: prometheus-4448
2018/08/06 10:21:41 resource created - kind: Deployment, name: fake-webserver
2018/08/06 10:21:41 Request for 'applying deployment:fake-webserver' is done!
2018/08/06 10:21:41 resource created - kind: Service, name: fake-webserver
2018/08/06 10:21:41 Request for 'applying service:fake-webserver' is done!
2018/08/06 10:21:41 resource created - kind: ConfigMap, name: prometheus-loadgen
2018/08/06 10:21:41 resource created - kind: Deployment, name: prometheus-loadgen-scaler
2018/08/06 10:21:41 Request for 'applying deployment:prometheus-loadgen-scaler' is done!
2018/08/06 10:21:41 resource created - kind: Deployment, name: prometheus-loadgen-querier
2018/08/06 10:21:41 Request for 'applying deployment:prometheus-loadgen-querier' is done!
2018/08/06 10:21:41 resource created - kind: Service, name: prometheus-loadgen-querier
2018/08/06 10:21:41 Request for 'applying service:prometheus-loadgen-querier' is done!
2018/08/06 10:21:42 resource created - kind: ConfigMap, name: prometheus-test
2018/08/06 10:21:42 resource created - kind: Deployment, name: prometheus-test-pr-4448
2018/08/06 10:21:42 Request for 'applying deployment:prometheus-test-pr-4448' is done!
2018/08/06 10:21:42 resource created - kind: Service, name: prometheus-test-pr-4448
2018/08/06 10:21:42 Request for 'applying service:prometheus-test-pr-4448' is done!
2018/08/06 10:21:42 resource created - kind: Deployment, name: prometheus-test-v2-3-2
2018/08/06 10:21:42 Request for 'applying deployment:prometheus-test-v2-3-2' is done!
2018/08/06 10:21:43 resource created - kind: Service, name: prometheus-test-v2-3-2
2018/08/06 10:21:43 Request for 'applying service:prometheus-test-v2-3-2' is done!
2018/08/06 10:21:43 resource created - kind: Deployment, name: node-exporter-prometheus-test-v2-3-2
2018/08/06 10:21:43 Request for 'applying deployment:node-exporter-prometheus-test-v2-3-2' is done!
2018/08/06 10:21:43 resource created - kind: Deployment, name: node-exporter-prometheus-test-pr-4448
2018/08/06 10:21:43 Request for 'applying deployment:node-exporter-prometheus-test-pr-4448' is done!
2018/08/06 10:21:43 resource created - kind: DaemonSet, name: node-exporter-nodes
2018/08/06 10:21:43 resource created - kind: Service, name: node-exporter
2018/08/06 10:21:43 Request for 'applying service:node-exporter' is done!

I think this can be closed by #130

thanks


RepositoryContentDescriptor should support include/exclude version ranges

Hi folks,
I was looking into the docs for RepositoryContentDescriptor excludeVersion  and I couldn't find anything related to version ranges.
For example:
repositories {
    maven {
        url = 'http://some-url'
        content {
             excludeVersion('com.google.guava', 'guava', '[19.0,)')
       }
    }
}

What I try to accomplish is to exclude  where the version is >= 19.0 on this case by using Maven Version Ranges
Also, I couldn't find tests related to this use case: https://github.com/gradle/gradle/blob/master/subprojects/dependency-management/src/integTest/groovy/org/gradle/integtests/resolve/RepositoryContentFilteringIntegrationTest.groovy
Use case
Given the following repos
ivyRepo
|-- mygroup
|    |-- my-library
|    |    |-- 1.0
|    |    |    +-- my-library-1.0.xml
|    |    |    +-- my-library-1.0.jar
|

mavenRepo
|-- mygroup
|    |-- my-library
|    |    |-- 2.0.0
|    |    |    +-- my-library-2.0.0.pom
|    |    |    +-- my-library-2.0.0.jar
|    |    +-- maven-metadata.xml
|

If I have the following declared repositories:
repositories {
     maven {
        url = 'mavenRepoUrl'
    }
    ivy {
        url = 'ivyRepoUrl'
        layout 'pattern' , {
            artifact '[module]/[revision]/[artifact](.[ext])'
            ivy '[module]/[revision]/ivy.xml'
        }
    }
}

I should be able to add excludeVersionRange (that's the API I think it should be created to avoid a breaking change to current excludeVersion behavior
so it would look like this:
     maven {
        url = 'mavenRepoUrl'
    }
    ivy {
        url = 'ivyRepoUrl'
        layout 'pattern' , {
            artifact '[module]/[revision]/[artifact](.[ext])'
            ivy '[module]/[revision]/ivy.xml'
        }
        content {
             excludeVersionRange('mygroup', 'my-library', '[2.0.0,)')
        }
    }
}

More context
I'm trying to apply these rules to thousands of groups and/or modules.
One option was to use excludeVersionByRegex and use something like ^([0-9]|[1-9][0-9]*)\\.([0-9]|[1-9][0-9]*)\\.([0-9]|[1-9][0-9]*)(?:-([0-9A-Za-z-]+(?:\\.[0-9A-Za-z-]+)*))?(?:\\+[0-9A-Za-z-]+)?\$ to make sire we exclude versions that don't have 3 digits. However, looking at the implementation, using ByRegex suggest that also the group and module name will be regex and the PatternSpecMatcher creates a Pattern for each part.
This could definitely work for us but a little hesitant to do it as we have a good amount of modules and this could be a performance impact, that's why having version range support seems like a better approach for this and also a nice addition to the current offering

Just clarify one thing around repository resolution. The content filtering in the example is useless because Gradle respects the order of repositories. And so any version 2.+ will be found in the first repo and thus the next repo will never be searched anyway.
I understand this was a sample for the issue and in reality, it might be beneficial to leverage content filtering. But I also wanted to make it clear that ordering can play a role in there for some use cases.
Example where it matters:
maven {
    url = 'mavenRepoUrl'
    content {
        excludeVersionRange('mygroup', 'my-library', '[,2.0.0)')
    }
}
ivy {
    url = 'ivyRepoUrl'
    layout 'pattern' , {
        artifact '[module]/[revision]/[artifact](.[ext])'
        ivy '[module]/[revision]/ivy.xml'
    }
}


[Create] VM and VMSS create should have image as a required param

Feedback from the AzLinux teams pointed out that having a default for this field biases Az against Linux VMs.  We should simply require the image to be selected (which is commonly overridden anyway) so all images have an equal opportunity to be selected.

@ahmetalpbalkan

Related to #586

Agreed.
The Image is the most important aspect for a VM, hence I never mind providing it explicitly.


[Bug]: Rules typo - Two's effect should read 'Scrap target Royal or Glasses Eight'

Bug Summary
Currently the two's second one-off effect reads 'Scrap target Royal', but does not mention that two's can scrap glasses eights.
Detailed Description
See pic

The Rules.vue page should be updated so that the second one-off effect for two's reads 'Scrap target Royal or Glasses Eight'.
This should be a matter of updating the description field of the object for that move preview, defined on line 384 of src/client/js/views/Rules.vue so that it reads
            description: 'Twos have two alternative one-off effects: Scrap target Royal or Glasses Eight',

Current Behavior
No response
Expected Behavior
No response
Steps to Reproduce

Navigate to the rules page on https://www.cuttle.cards/#/rules or locally at localhost:8080/#/rules
Look at the text for the second one-off effect of two's

Hey, I've just posted a PR that fixes the typo. Could you, please, check it when you have spare time?
https://github.com/cuttle-cards/cuttle/pull/137


Why I can't get the same result with example?

Hi, I followed the example instructions strictly, but nothing happened after I created the daemonset.
[xxx@xxx]$ kubectl get pods
NAME                READY     STATUS    RESTARTS   AGE
echoheaders-j0t2f   1/1       Running   0          20s
[xxx@xxx]$ kubectl get daemonset
NAME                  DESIRED   CURRENT   READY     NODE-SELECTOR   AGE
kube-keepalived-vip   0         0         0         type=worker     4m
And I didn't found any error in logs. Could you please help me know what's wrong with my try? Thanks!

Try to run kubectl describe daemonset kube-keepalived-vip to see what kube says about it.


Add general styles to Tailwind config file

Add our custom styles (colors, typography, breakpoints etc) to the Tailwind config file like below

https://tailwindcss.com/docs/adding-custom-styles

See https://github.com/NoroffFEU/edu-gate/pull/193

Resolved by running "npm run dev" in the terminal, moving to review again.


Detecting whether an attachment is media through attachment.content_type can sometimes fail

We have the following code for detecting whether an attachment in a Discord message is a song/video:
https://github.com/anoadragon453/busty/blob/15c4bb0d20a2160f75dbb390b8c10757c68bae67/main.py#L214-L217
However, on accidentally running !list on a fairly old channel with a lot of messages/attachment, I got the following stack trace:

Exception
 % python ./main.py
We have logged in as Busty Dev#3334.
Ignoring exception in on_message
Traceback (most recent call last):
  File "/home/user/code/busty/env/lib/python3.10/site-packages/discord/client.py", line 343, in _run_event
    await coro(*args, **kwargs)
  File "/home/user/code/busty/./main.py", line 57, in on_message
    await list(message)
  File "/home/user/code/busty/./main.py", line 197, in list
    channel_media_attachments = await scrape_channel_media(message.channel)
  File "/home/user/code/busty/./main.py", line 232, in scrape_channel_media
    not attachment.content_type.startswith("audio")
AttributeError: 'NoneType' object has no attribute 'startswith'

It turns out that Attachment.content_type can be None, according to discord.py's documentation. Since it's new in discord.py v1.7, my hunch is that Discord only started recording and returning the media type of attachments recently, and thus this field is None when querying older message attachments.
This doesn't really affect Busty's at all, as we're always dealing with newly uploaded media files, but it'd be good hygiene to handle, especially if my hunch is wrong.

I just found out by accident that the attachment type is also "None" if you send a file with no extension and this crash occurs. This seems much more likely to actually happen by accident, so we should definitely patch this.

@Cephian nice catch! Definitely worth fixing then.

Fixed by https://github.com/anoadragon453/busty/pull/28.


Convoy-gluster file changed as we read it

I have 3 hosts.installed gluster-fs and convoy-gluster from catalog.
I modified my_vol types, from reply to Distribute (/opt/rancher/replicated_volume_create.sh num 58: gluster volume create $ {VOLUME_NAME} transport tcp $ {CONTAINER_MNTS})
I created a volume from UI named pools_1 and mount it to a container(volumes is pools_1:/tmp1).
but docker-enter in container,cd /tmp1.When I run the command: tar zcvf openvpn-2.3.10.tar.gz ./openvpn-2.3.10, display an error: file changed as we read it
If my_vol mount the hard disk directory, without Convoy-gluster, there is no mistake

Ok, I hit the same bug!
(it is also mentionned in the forum here
Looks like the solution is:
upgrade to 3.7.12:
You have to have the following configuration:
1) gluster volume set <volname> cluster.consistent-metadata on
2) gluster volume set <volname> cluster.post-op-delay-secs 0

PS: you can find the origin of my discovery on this thread.


Proxmox Host on port 443 instead of 8006

Hi,
Is there a way to configure the exporter to query on port 443 via nginx instead of 8006?
I have to keep 8006 open for the remote query via /etc/default/pveproxy and cannot close it down.
Thanks.

Prometheus PVE Exporter uses https://github.com/proxmoxer/proxmoxer under the hood. It looks like there are two ways to specify a port in the HTTPS Backend:
class Backend(object):
    def __init__(self, host, user=None, password=None, otp=None, port=None,
                 verify_ssl=True, mode='json', timeout=5, auth_token=None,
                 csrf_token=None, token_name=None, token_value=None, service='PVE'):
        if ':' in host:
            host, host_port = host.split(':')
            port = host_port if host_port.isdigit() else port

Either specify port alongside user and password in pve.yml or supply host:port as the target param in prometheus scraper config.
Example for pve.yml:

default:
  user: prometheus@pve
  password: sEcr3T!
  port: 443

Example for prometheus config:
scrape_configs:
  - job_name: 'pve'
    static_configs:
      - targets:
        - <IP_ADDRESS>:443  # Proxmox VE node listening on HTTPS port.
        - <IP_ADDRESS>:443  # Proxmox VE node listening on HTTPS port.
    metrics_path: /pve
    params:
      module: [default]
    relabel_configs:
      - source_labels: [__address__]
        target_label: __param_target
      - source_labels: [__param_target]
        target_label: instance
      - target_label: __address__
        replacement: <IP_ADDRESS>:9221  # PVE exporter.

Nice! Thanks.
I used the method via pve.yml as that does not change the instance name in grafana.


Package appmetrics-dash into NodeRED

@knolleary Here's the code needed to put Appmetrics-dash into NodeRED. It can be enabled by setting the APPMETRICS environment variable. Appmetrics-dash will attach to NodeRED's web server instance, and the dashboard will be on hostname:port/appmetrics-dash. Happy to write docs!

@mattcolegate this isn't for the core project. As per discussion, this would only be for the Bluemix instances - so any PR for discussion should be against the Bluemix boilerplate here: https://github.com/ibmets/node-red-bluemix-starter

Coverage increased (+0.08%) to 86.132% when pulling 605859469f189d85c7d2cc54c4556a3f82eeac8b on mattcolegate:appmetrics into 096b3534d839369eceebfb9cf6f3fd56f4c1b4aa on node-red:master.

Thanks @knolleary, I'll close the PR here and look to make changes against the Bluemix sample then.


Test StableHash and implement it for stringlabels

We need a test that checks that StableHash is really stable. I think checking three hashes should be ok.
Also implemented this function for the stringlabels build tag.
Finally, added a CI piepline to ensure that this doesn't break anymore.

Okay, I guess I messed it up when I ran the tests with the tag (I ran them without).
It was too suspicious to see that the hash was valid (as I recalled that it shouldn't be).

Closing this in favor of #503, where I'll cherry pick the test and the CI job.


Can I delay an update?

In the "Can I delay an update?" section, it's mentioned that it's 3 months for 2 consecutive updates, whereas is 3 consecutive updates, not 2. It has been misleading for some customers referring to this page.
Thanks!

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

ID: 23fde63f-0f6f-b1a0-50c8-e1bf5f6a48c4
Version Independent ID: 59a1f734-87cb-f34c-afd5-9f14de877584
Content: One Version service updates FAQ - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/fin-ops-core/fin-ops/get-started/one-version.md
Service: dynamics-ax-applications
Product: ****
Technology: ****
GitHub Login: @meeramahabala
Microsoft Alias: meeram

@elenchule, thanks for posting this!
@meeramahabala, please review and update the content as necessary.

@ShellyBakke, can you please review and update the content, as needed.

Bug 386052 has been logged to track this issue.

Hi can the customer pause 3 or 2 consecutive service updates ? And when will the text be changed?

This content has been updated and will be published later today.