Turn the file format into fits table, which currently is tsv

The full form of FITS is Flexible Image Transport System.
Which is much more flexible and come with lots of convenient and fast api.
Better than the self-defined file format, tsv file.
The most of all, astronomical software usually deal with fits file.
In the future, maybe tat python need to adjust its system to fit another system, it would be easier.
spec

file format is fits.
datatype is table, defined by astropy.table

This task go on in branch develop_20170821.

This part is done in my opinion
because the most important part, star catalog have been convert into fits table.
I don't want to modify others program, because I rarely use them and the job is pretty time-consuming.


Event logging

Each event will contain the following fields:

timestamp
level - one of: "packet", "frame", "cc"

maybe add "stream" as well?

event - name of the event "send", "receive", etc., which are level-specific
rest of the fields are event-specific

We will initially log the events using JSON, but the internal API will be kept neutral to the output format.

mostly done with #23.
The leftovers are:

[ ] log address

at the moment, the addresses are bound to the connection rather than a "path". We need to change that as well, because probing on a separate "path"


Support xstate v5's initial

Right now initial can only be an identifier of one the child states, but starting from v5 initial can be { target, actions } too

Moved to #17


[AutoRelease] t2-cosmosdb-2024-03-04-82581(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/4979
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=984
BuildTargetingString
azure-mgmt-cosmosdb
Skip.CreateApiReview
true

issue link:https://github.com/Azure/sdk-release-request/issues/4979


Bug Report

Describe the bug
Bug happened OMG please fix it, thank you
Steps to reproduce

Start the app
connect exchange
It fails to connect
I'm sad

Release version
1.100
Type of installation
Source
Attach required files
I don't know where is the files :(((
Discord name
No response

Sorry missclick


Out of date instructions

The link to run a search points to protection.office.com, since this is getting phased out, a better link would be to https://compliance.microsoft.com/auditlogsearch

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

ID: 3494b782-92ad-e365-3398-bd2d760d10c6
Version Independent ID: fa4bca98-3975-23dd-dfac-f23049c71d01
Content: Search the audit log in the Security & Compliance Center - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/search-the-audit-log-in-security-and-compliance.md
Service: o365-seccomp
GitHub Login: @markjjo
Microsoft Alias: markjjo

@DeanGross Thanks for feedback. Eventually, audit log search in SCC will be redirected to MCC.

Also, I assume you have seen this banner as well, with the link to the MCC audit log search tool:

Yes, that is what inspired my comment, The docs send me to that page, which then redirects me to the new site. It would be nice to skip that middle step.


Maintainer wanted!

I am looking for a maintainer for statsd-influxdb-backend because I am currently not using statsd and influxdb at all. This makes it hard to test changes and decide on architecture topics.
Please let me know in the comments if you are using it and are willing to take over maintenance.
Thank you!

I'm using it right now but I did see other contributors for V0.9. You should ask them too since they are actively using it. If no one gonna do it, I can take over the maintenance

I've been using it too, i can help.

So what's up ? It woul'd be sad that this repo were abandonned since it is relatively popular (I followed http://www.symantec.com/connect/blogs/metrics-cocktail-statsdinfluxdbgrafana) and since influxDb has update (tags !).
Is there someone who coul'd merge tags support PR ?

Any word on this issue? I've been testing StatsD + InfluxD combo and seems to work quite well. This project needs to live on :)

Any word on this issue? I've been testing StatsD + InfluxD combo and seems to work quite well. This project needs to live on :)

@bernd I can fully understand you no longer wanting to steer this project. I would appreciate though if you can name a new maintainer that will step up to steer this project.
There's a number of forks out there (https://github.com/bernd/statsd-influxdb-backend/network) that added much needed features (InfluxDb v0.12 support, tags). I think @CodeKingdomsTeam fork looks pretty solid and there's been a couple of people that volunteered to take over in this thread as well.

Just wanted to add that @gillesdemey fork looks pretty complete as well!

My fork has been running on our production stats machine for a few months now so I dare say it works reliably.
I'll try to isolate the commits and merge them upstream so we can at least have support for Influx 0.12+ and tags.

I can confirm that @gillesdemey fork works nice also with v0.13

Thanks all for the feedback and sorry for the unresponsiveness from my side.
@gillesdemey Would you like to takeover maintainership of this project? Let me know and I will add you as a contributor to GitHub and npmjs.

@bernd if @gillesdemey isn't up for it, you can add me.


ReaperScans Issues

Steps to reproduce
Case 1 Browse:

Browse the source
Scroll

Case 2 Latest:

Click latest on the source
Scroll

Case 3 Missing free & paid chapters:

Browse a series

Expected behavior
Case 1 Browse:
Grabs all the series from https://reaperscans.com/all-series/novels/ and shows them.
Case 2 Latest:
Grabs all the series from https://reaperscans.com/all-series/novels/?m_orderby=latest and shows them
Case 3 Missing free & paid chapters:
Shows all the chapters for the series including the paid chapters where purchased ones can be accessed by logging in through webview.
Actual behavior
Case 1 Browse:
Its shows couple of series and then repeats them.
Case 2 Latest:
It still shows the same series as browse and they also repeat.
Case 3 Missing free & paid chapters:
It only shows chapters for one or two series which others are shown as 0 chapters. Paid chapters aren't shown at all.
LNReader version
1.1.12
Android version
Android 12
Device
Samsung Galaxy Tab S5e
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an source, I should be opening an issue in the sources repository.
[X] I have updated the app to version 1.1.12.
[X] I will fill out all of the requested information in this form.

If this is an issue with an source, I should be opening an issue in the sources repository.


[SHEL-1390] net: shell: Display TWT response details

[nrf fromlist] Show TWT response parameters details.
Upstream PR: https://github.com/zephyrproject-rtos/zephyr/pull/57116

@sachinthegreen @krish2718 @rado17


[stable/traefik] dashboard serviceType

What this PR does / why we need it:
This PR adds the ability to set the serviceType of the dashboard service. This is useful for when deploying to a managed k8s environment, e.g GKE.
Which issue this PR fixes

fixes #7912

Special notes for your reviewer:
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/assign @nmengin

Also, Is this error coming from GKE directly? I am unsure as to why it is expecting a nodeport service at all....We are not exposing anything via that nodeport...so it seems redundant....

Having the same issue. Deploying this chart creates a ClusterIP service, while it should be a NodePort.
Error:
Error during sync: error while evaluating the ingress spec: service "kube-system/jolly-jellyfish-traefik-dashboard" is type "ClusterIP", expected "NodePort" or "LoadBalancer"

I'm facing the same issue (also on GKE). How could we move forward with it? Can I help somehow?


Update html and styles.css and readme files

I have been updated the html and css files and fix some errors in the design.
I have been changed the title of the readme file for this mobile-first-project

I'm repeating my module .
I have been updated the html and css files and fix some errors in the design.
I have been changed the title of the readme file for this mobile-first-project


fix #5 Typescript support missing

See #5
To be merged if sachiel-ts doesn't exist.
To be closed if sachiel-ts actually exist and was private.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


ENH: make drawable types for rRNA and tRNA like CDS

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
57 unchanged lines in 17 files lost coverage.
Overall coverage decreased (-0.002%) to 91.538%

Files with Coverage Reduction
New Missed Lines
%

.nox/test-3-10/Lib/site-packages/cogent3/evolve/likelihood_function.py
1
96.3%

.nox/test-3-11/lib/python3.11/site-packages/cogent3/core/alignment.py
1
94.41%

.nox/test-3-11/Lib/site-packages/cogent3/evolve/likelihood_function.py
1
96.3%

.nox/test-3-8/Lib/site-packages/cogent3/core/alignment.py
1
94.37%

.nox/test-3-8/Lib/site-packages/cogent3/evolve/likelihood_function.py
1
96.3%

.nox/test-3-10/Lib/site-packages/cogent3/maths/scipy_optimize.py
3
84.92%

.nox/test-3-11/Lib/site-packages/cogent3/maths/scipy_optimize.py
3
84.92%

.nox/test-3-8/Lib/site-packages/cogent3/maths/scipy_optimize.py
3
84.87%

.nox/test-3-9/lib/python3.9/site-packages/cogent3/maths/scipy_optimize.py
3
83.88%

.nox/test-3-10/lib/python3.10/site-packages/cogent3/draw/drawable.py
5
83.73%

Totals

Change from base Build<PHONE_NUMBER>:
-0.002%

Covered Lines:
235585

Relevant Lines:
257364

💛  - Coveralls


Replace static image on the landing page with a carousel of images

Generate 2 images related to business, economy, monopoly in pixel art using bing.com Image Creator (https://www.bing.com/images/create). The prompt I used to generate the current image is "a modern version of city skyline, pixel art."
Instead of showing one static image, replace it with a carousel scrolling over these 3 images. It should look similar to the carousel on Google Meet.

Make sure the carousel is responsive and uses individual Fluent UI components. It should be accessible and compliant to theme. Refer to Fluent UI 9 documentation (https://react.fluentui.dev/)

IMP: Do comment your approach/library for building the carousel before starting to work on it.

@fliptrail i can work on this issue
The carousel will change images based on a simple counter or bool flag, since you are asking to generate 2 images only?

I'll assign it to you. Use a counter as it could have more than two images.
I asked to generate two more images as I have already generated one.

@fliptrail Can you please assign this issue to me next


Synchronize and controlled access to vnid map

Fix for bug# https://bugzilla.redhat.com/show_bug.cgi?id=1323279

LGTM

Extended networking tests (test/extended/networking.sh) passed and manually tested join-projects/make-projects-global.

@openshift/networking ready for review/merge

@openshift/networking Updated, ptal

LGTM

@danwinship Updated, PTAL

@pravisankar added some review comments on the patches.

Don't merge this yet please, we'll hold it for after 3.2.

@dcbw addressed your comments, thanks.

LGTM now

LGTM too... I'm not sure where we are with respect to freezes now though


Update MD file on new branch 2017-27-25_01-11-44

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Desktop App Automatic & Manual Updates

Documentation for: https://github.com/mattermost/desktop/pull/1714

Added automatic update and manual update steps for Linux, Mac, and Windows platforms to existing Desktop App installation documentation. Note that this content is a WIP that requires additional Engineering/PM input.
Streamlined content presentation on the page by organizing content in tabs
Updated the Sign In page to include links to desktop and mobile install pages
Updated the Windows GPO documentation as well to align it to our Style Guide. Additional updates may be needed following a technical review of this page.

/update-branch

/update-branch


OS X Yosemite

pkamb, awesome work on your app, love it! Just out of curiosity, have you looked into building this for OS X Yosemite? I have no idea how to go about doing this myself, and I understand that plenty of developers don't like building for beta releases, but I was just curious whether you were in the works on this or if it was one of those things where you planned on waiting for the final release first.
Thanks!

Closing this ticket now that El Capitan is out. Please open a new ticket if you see any issues in the new OS!


added support for ControlNodes aka non-system, non-patcher nodes

closes #70

one note @fde31
this doesn't dynamically update when you add a new jack client, you can test this by doing this:

start the web UI and target your pi
ssh to your pi
run jack_midi_dump

you may have to sudo apt-get install jack-tools before

you should see midi-monitor now in the graph but you don't until you reload the page

ok should be addressed now. Want to test it once more @x37v ?


"Unexpected modifier sealed" error when using sealed classes

we got a bug report at https://github.com/quarkusio/quarkus/issues/30639 for a user trying to do the Quarkus 3 migration steps that uses openrewrite.
It fails because openrewrite fails at parsing classes with "sealed" modifier.
The error we get is:
[WARNING] Failed to convert for the following cursor stack:--- BEGIN PATH ---
JCCompilationUnit(sourceFile = /Users/manderse/temp/quarkus-timed-producers/src/main/java/org/acme/GreetingResource.java)
JCClassDecl(name = GreetingResource, line = 10)
JCClassDecl(name = HelloService, line = 22)
--- END PATH ---

[WARNING] Failed to convert for the following cursor stack:--- BEGIN PATH ---
JCCompilationUnit(sourceFile = /Users/manderse/temp/quarkus-timed-producers/src/main/java/org/acme/GreetingResource.java)
JCClassDecl(name = GreetingResource, line = 10)
--- END PATH ---

[WARNING] Failed to convert for the following cursor stack:--- BEGIN PATH ---
JCCompilationUnit(sourceFile = /Users/manderse/temp/quarkus-timed-producers/src/main/java/org/acme/GreetingResource.java)
--- END PATH ---

[WARNING] Unexpected modifier sealed

Despite the failure to parse the maven plugin reports all went fine - but it did not :)
The code that "breaks" openrewrite is:
public static class HelloService {
        public static String HELLO = "hello ";
        record Msg(String msg) {}
        sealed interface Foo permits Bar,Baz{}
        static final class Bar implements Foo {}
        static final class Baz implements Foo {}
        public String hello() {
            return new Msg(HELLO).toString() + new Bar();
        }
    }

I run it with Java 17 which I assume has a javac/java parser that supports sealed thus I'm assuming its somehow openrewrite internal model that is failing to capture sealed classes/interfaces?

Hi @maxandersen ! What version of OpenRewrite are your running? We released 7.35.0 last week, which includes a fix for sealed classes.

doh, I should have checked with latest version. rewrite-maven-plugin:4.39.0 does not give this error.
still diff is not being generated but at least it seems it is no longer related to seal classes. I'll investigate further.


#1818 limit java optimization to improve compile perf in verification…

… builds on Azure pipelines
See #1818 for background
Should improve Java 11 build performance
Signed-off-by: Nigel Jones<EMAIL_ADDRESS>

Note I've just changed verify jobs at this point - the others are less time critical and taking a conservative approach in changing minimum possible.

There areThe only question is how it affects performance time, but generally +10% or so. No negative effects noted.  numerous projects using this, and it's referred to in articles at nvidia, redhat etc in this context. As such I will attempt the merge, monitor, and back off if we see any regression


Create a WYSIWYG Component

User Profile Subtask
What should your feature do?
Provide an editor for users to edit profile information.
https://www.froala.com/wysiwyg-editor/examples/textarea

I don't think we need this. We don't have a section for people to write the length of text in a profile that would require an in-browser editor.
Updating a profile would be as simple as a few inputs in a form.

Need thoughts on this from @team_frontend

Agree, let's close this.


Missing parts of cached chunks

This is a report on MeklanB's behalf before they commented here.
In HoldThatChunk v1.0.3 on Minecraft 1.19.2, there are visual artifacts and X-ray glitches in chunks that should be cached. These glitches are not present in a similar mod, Farsight and they appeared only when flying, not walking.

Getting visual artifacts and missing surfaces (resulting in x-ray) when flying in and out of chunks that should be in memory.

Screenshot album: https://imgur.com/a/p5ReFeD
Note that these tests were conducted in the modpack Fabulously Optimized versions 4.2.0-beta.1 (manually replaced Farsight with Hold That Chunk) and 4.2.0-beta.2 (contains Hold That Chunk without Farsight). Unfortunately it is currently unknown whether this is reproducible with just Hold That Chunk, without the other mods.

I'm not seeing these issues when testing Hold That Chunk in isolation in a vanilla MC instance. I'm going to start flipping through FO's mod list to see which may introduce issues.

Confirmed the issues did not arise with Sodium, Lithium, MemoryLeakFix, or Starlight.

The chunks are in the chunk cache, but the level renderer may sometimes skip drawing chunks that are outside the effective render distance. The effective render distance is calculated by taking the minimum between the client render distance and the server render distance. Farsight would have the same behavior if you configure its max distance option to be the same as the server render distance.

What if Hold That Chunk used client render distance + constant to workaround this bug?

Because it would still render by the client render distance, it shouldn't affect performance that much.

It will render by the effective render distance.
If you set ignoreServerRenderDistance to false, it follows vanilla behavior for calculating the effective render distance. The effective render distance is the lower value between client render distance and server render distance. If you set it true, it replaces the server render distance with the value of the client render distance, thereby making the effective render distance equal to client render distance.
The effective render distance is used for multiple things, including how far the level renderer will always draw chunks and where to place the fog.

Has this been fixed with 2.0.0?

It has not.

could a solution be to only render chunk if all chunk between are rendered starting from the chunk the player stand in ?
like if you have the 8x8 circle which is the server distance then a missing empty chunk then a chunk the client know, don't render the one the client know because there is an empty chunk in between

In my testing, this is not an issue anymore. It was probably fixed by Sodium 0.5.0.
To begin with, this was a rendering bug and Hold That Chunk does nothing to the renderer.


fix detect keepalived daemonset

Signed-off-by: renyunkang<EMAIL_ADDRESS>fix #264

@chaunceyjiang  @zheng1

/LGTM

/approve


install kafka cluster in istio ,the pod can not be created

We use GitHub issues to discuss Kafka operator bugs and new features.
For support requests please use the channels listed in SUPPORT.md
[root@node01 kafka_mesh]# kubectl get KafkaCluster --all-namespaces
NAMESPACE   NAME    CLUSTER STATE        CLUSTER ALERT COUNT   LAST SUCCESSFUL UPGRADE   UPGRADE ERROR COUNT   AGE
istio       kafka   ClusterReconciling   0                                               0                     2m39s
apiVersion: kafka.banzaicloud.io/v1beta1
kind: KafkaCluster
metadata:
  labels:
    controller-tools.k8s.io: "1.0"
  name: kafka
spec:
  headlessServiceEnabled: false
  ingressController: "istioingress"
  istioControlPlane:
    name: istiod
    namespace: istio-system
  istioIngressConfig:
    gatewayConfig:
      mode: ISTIO_MUTUAL
  zkAddresses:
    - "zookeeper-client.zookeeper:2181"
  oneBrokerPerNode: false
  clusterImage: "ghcr.io/banzaicloud/kafka:2.13-3.1.0"
  readOnlyConfig: |
    auto.create.topics.enable=false
    cruise.control.metrics.topic.auto.create=true
    cruise.control.metrics.topic.num.partitions=1
    cruise.control.metrics.topic.replication.factor=2
  brokerConfigGroups:
    default:
      brokerAnnotations:
        sidecar.istio.io/userVolumeMount: '[{"name":"exitfile", "mountPath":"/var/run/wait", "readonly":true}]'
      storageConfigs:
        - mountPath: "/kafka-logs"
          pvcSpec:
            accessModes:
              - ReadWriteOnce
            resources:
              requests:
                storage: 10Gi
  brokers:
    - id: 0
      brokerConfigGroup: "default"
    - id: 1
      brokerConfigGroup: "default"
    - id: 2
      brokerConfigGroup: "default"
  rollingUpgradeConfig:
    failureThreshold: 1
  listenersConfig:
    internalListeners:
      - type: "plaintext"
        name: "internal"
        containerPort: 29092
        usedForInnerBrokerCommunication: true
      - type: "plaintext"
        name: "controller"
        containerPort: 29093
        usedForInnerBrokerCommunication: false
        usedForControllerCommunication: true
    externalListeners:
      - type: "plaintext"
        name: "external"
        externalStartingPort: 19090
        containerPort: 9094
  cruiseControlConfig:
    topicConfig:
      partitions: 12
      replicationFactor: 3
    config: |
      # Copyright 2017 LinkedIn Corp. Licensed under the BSD 2-Clause License (the "License"). See License in the project root for license information.
      #
      # This is an example property file for Kafka Cruise Control. See KafkaCruiseControlConfig for more details.
      # Configuration for the metadata client.
      # =======================================
      # The maximum interval in milliseconds between two metadata refreshes.
      #metadata.max.age.ms=300000
      # Client id for the Cruise Control. It is used for the metadata client.
      #client.id=kafka-cruise-control
      # The size of TCP send buffer bytes for the metadata client.
      #send.buffer.bytes=131072
      # The size of TCP receive buffer size for the metadata client.
      #receive.buffer.bytes=131072
      # The time to wait before disconnect an idle TCP connection.
      #connections.max.idle.ms=540000
      # The time to wait before reconnect to a given host.
      #reconnect.backoff.ms=50
      # The time to wait for a response from a host after sending a request.
      #request.timeout.ms=30000
      # Configurations for the load monitor
      # =======================================
      # The number of metric fetcher thread to fetch metrics for the Kafka cluster
      num.metric.fetchers=1
      # The metric sampler class
      metric.sampler.class=com.linkedin.kafka.cruisecontrol.monitor.sampling.CruiseControlMetricsReporterSampler
      # Configurations for CruiseControlMetricsReporterSampler
      metric.reporter.topic.pattern=__CruiseControlMetrics
      # The sample store class name
      sample.store.class=com.linkedin.kafka.cruisecontrol.monitor.sampling.KafkaSampleStore
      # The config for the Kafka sample store to save the partition metric samples
      partition.metric.sample.store.topic=__KafkaCruiseControlPartitionMetricSamples
      # The config for the Kafka sample store to save the model training samples
      broker.metric.sample.store.topic=__KafkaCruiseControlModelTrainingSamples
      # The replication factor of Kafka metric sample store topic
      sample.store.topic.replication.factor=2
      # The config for the number of Kafka sample store consumer threads
      num.sample.loading.threads=8
      # The partition assignor class for the metric samplers
      metric.sampler.partition.assignor.class=com.linkedin.kafka.cruisecontrol.monitor.sampling.DefaultMetricSamplerPartitionAssignor
      # The metric sampling interval in milliseconds
      metric.sampling.interval.ms=120000
      metric.anomaly.detection.interval.ms=180000
      # The partition metrics window size in milliseconds
      partition.metrics.window.ms=300000
      # The number of partition metric windows to keep in memory
      num.partition.metrics.windows=1
      # The minimum partition metric samples required for a partition in each window
      min.samples.per.partition.metrics.window=1
      # The broker metrics window size in milliseconds
      broker.metrics.window.ms=300000
      # The number of broker metric windows to keep in memory
      num.broker.metrics.windows=20
      # The minimum broker metric samples required for a partition in each window
      min.samples.per.broker.metrics.window=1
      # The configuration for the BrokerCapacityConfigFileResolver (supports JBOD and non-JBOD broker capacities)
      capacity.config.file=config/capacity.json
      #capacity.config.file=config/capacityJBOD.json
      # Configurations for the analyzer
      # =======================================
      # The list of goals to optimize the Kafka cluster for with pre-computed proposals
      default.goals=com.linkedin.kafka.cruisecontrol.analyzer.goals.ReplicaCapacityGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.DiskCapacityGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.NetworkInboundCapacityGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.NetworkOutboundCapacityGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.CpuCapacityGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.ReplicaDistributionGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.PotentialNwOutGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.DiskUsageDistributionGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.NetworkInboundUsageDistributionGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.NetworkOutboundUsageDistributionGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.CpuUsageDistributionGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.TopicReplicaDistributionGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.LeaderBytesInDistributionGoal
      # The list of supported goals
      goals=com.linkedin.kafka.cruisecontrol.analyzer.goals.ReplicaCapacityGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.DiskCapacityGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.NetworkInboundCapacityGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.NetworkOutboundCapacityGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.CpuCapacityGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.ReplicaDistributionGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.PotentialNwOutGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.DiskUsageDistributionGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.NetworkInboundUsageDistributionGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.NetworkOutboundUsageDistributionGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.CpuUsageDistributionGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.TopicReplicaDistributionGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.LeaderBytesInDistributionGoal,com.linkedin.kafka.cruisecontrol.analyzer.kafkaassigner.KafkaAssignerDiskUsageDistributionGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.PreferredLeaderElectionGoal
      # The list of supported hard goals
      hard.goals=com.linkedin.kafka.cruisecontrol.analyzer.goals.ReplicaCapacityGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.DiskCapacityGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.NetworkInboundCapacityGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.NetworkOutboundCapacityGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.CpuCapacityGoal
      # The minimum percentage of well monitored partitions out of all the partitions
      min.monitored.partition.percentage=0.95
      # The balance threshold for CPU
      cpu.balance.threshold=1.1
      # The balance threshold for disk
      disk.balance.threshold=1.1
      # The balance threshold for network inbound utilization
      network.inbound.balance.threshold=1.1
      # The balance threshold for network outbound utilization
      network.outbound.balance.threshold=1.1
      # The balance threshold for the replica count
      replica.count.balance.threshold=1.1
      # The capacity threshold for CPU in percentage
      cpu.capacity.threshold=0.8
      # The capacity threshold for disk in percentage
      disk.capacity.threshold=0.8
      # The capacity threshold for network inbound utilization in percentage
      network.inbound.capacity.threshold=0.8
      # The capacity threshold for network outbound utilization in percentage
      network.outbound.capacity.threshold=0.8
      # The threshold to define the cluster to be in a low CPU utilization state
      cpu.low.utilization.threshold=0.0
      # The threshold to define the cluster to be in a low disk utilization state
      disk.low.utilization.threshold=0.0
      # The threshold to define the cluster to be in a low network inbound utilization state
      network.inbound.low.utilization.threshold=0.0
      # The threshold to define the cluster to be in a low disk utilization state
      network.outbound.low.utilization.threshold=0.0
      # The metric anomaly percentile upper threshold
      metric.anomaly.percentile.upper.threshold=90.0
      # The metric anomaly percentile lower threshold
      metric.anomaly.percentile.lower.threshold=10.0
      # How often should the cached proposal be expired and recalculated if necessary
      proposal.expiration.ms=60000
      # The maximum number of replicas that can reside on a broker at any given time.
      max.replicas.per.broker=10000
      # The number of threads to use for proposal candidate precomputing.
      num.proposal.precompute.threads=1
      # the topics that should be excluded from the partition movement.
      #topics.excluded.from.partition.movement
      # Configurations for the executor
      # =======================================
      # The max number of partitions to move in/out on a given broker at a given time.
      num.concurrent.partition.movements.per.broker=10
      # The interval between two execution progress checks.
      execution.progress.check.interval.ms=10000
      # Configurations for anomaly detector
      # =======================================
      # The goal violation notifier class
      anomaly.notifier.class=com.linkedin.kafka.cruisecontrol.detector.notifier.SelfHealingNotifier
      # The metric anomaly finder class
      metric.anomaly.finder.class=com.linkedin.kafka.cruisecontrol.detector.KafkaMetricAnomalyFinder
      # The anomaly detection interval
      anomaly.detection.interval.ms=10000
      # The goal violation to detect.
      anomaly.detection.goals=com.linkedin.kafka.cruisecontrol.analyzer.goals.ReplicaCapacityGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.DiskCapacityGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.NetworkInboundCapacityGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.NetworkOutboundCapacityGoal,com.linkedin.kafka.cruisecontrol.analyzer.goals.CpuCapacityGoal
      # The interested metrics for metric anomaly analyzer.
      metric.anomaly.analyzer.metrics=BROKER_PRODUCE_LOCAL_TIME_MS_MAX,BROKER_PRODUCE_LOCAL_TIME_MS_MEAN,BROKER_CONSUMER_FETCH_LOCAL_TIME_MS_MAX,BROKER_CONSUMER_FETCH_LOCAL_TIME_MS_MEAN,BROKER_FOLLOWER_FETCH_LOCAL_TIME_MS_MAX,BROKER_FOLLOWER_FETCH_LOCAL_TIME_MS_MEAN,BROKER_LOG_FLUSH_TIME_MS_MAX,BROKER_LOG_FLUSH_TIME_MS_MEAN
      ## Adjust accordingly if your metrics reporter is an older version and does not produce these metrics.
      #metric.anomaly.analyzer.metrics=BROKER_PRODUCE_LOCAL_TIME_MS_50TH,BROKER_PRODUCE_LOCAL_TIME_MS_999TH,BROKER_CONSUMER_FETCH_LOCAL_TIME_MS_50TH,BROKER_CONSUMER_FETCH_LOCAL_TIME_MS_999TH,BROKER_FOLLOWER_FETCH_LOCAL_TIME_MS_50TH,BROKER_FOLLOWER_FETCH_LOCAL_TIME_MS_999TH,BROKER_LOG_FLUSH_TIME_MS_50TH,BROKER_LOG_FLUSH_TIME_MS_999TH
      # The zk path to store failed broker information.
      failed.brokers.zk.path=/CruiseControlBrokerList
      # Topic config provider class
      topic.config.provider.class=com.linkedin.kafka.cruisecontrol.config.KafkaTopicConfigProvider
      # The cluster configurations for the KafkaTopicConfigProvider
      cluster.configs.file=config/clusterConfigs.json
      # The maximum time in milliseconds to store the response and access details of a completed user task.
      completed.user.task.retention.time.ms=21600000
      # The maximum time in milliseconds to retain the demotion history of brokers.
      demotion.history.retention.time.ms=86400000
      # The maximum number of completed user tasks for which the response and access details will be cached.
      max.cached.completed.user.tasks=100
      # The maximum number of user tasks for concurrently running in async endpoints across all users.
      max.active.user.tasks=25
      # Enable self healing for all anomaly detectors, unless the particular anomaly detector is explicitly disabled
      self.healing.enabled=true
      # Enable self healing for broker failure detector
      #self.healing.broker.failure.enabled=true
      # Enable self healing for goal violation detector
      #self.healing.goal.violation.enabled=true
      # Enable self healing for metric anomaly detector
      #self.healing.metric.anomaly.enabled=true
      # configurations for the webserver
      # ================================
      # HTTP listen port
      webserver.http.port=9090
      # HTTP listen address
      webserver.http.address=<IP_ADDRESS>
      # Whether CORS support is enabled for API or not
      webserver.http.cors.enabled=false
      # Value for Access-Control-Allow-Origin
      webserver.http.cors.origin=http://localhost:8080/
      # Value for Access-Control-Request-Method
      webserver.http.cors.allowmethods=OPTIONS,GET,POST
      # Headers that should be exposed to the Browser (Webapp)
      # This is a special header that is used by the
      # User Tasks subsystem and should be explicitly
      # Enabled when CORS mode is used as part of the
      # Admin Interface
      webserver.http.cors.exposeheaders=User-Task-ID
      # REST API default prefix
      # (dont forget the ending *)
      webserver.api.urlprefix=/kafkacruisecontrol/*
      # Location where the Cruise Control frontend is deployed
      webserver.ui.diskpath=./cruise-control-ui/dist/
      # URL path prefix for UI
      # (dont forget the ending *)
      webserver.ui.urlprefix=/*
      # Time After which request is converted to Async
      webserver.request.maxBlockTimeMs=10000
      # Default Session Expiry Period
      webserver.session.maxExpiryTimeMs=60000
      # Session cookie path
      webserver.session.path=/
      # Server Access Logs
      webserver.accesslog.enabled=true
      # Location of HTTP Request Logs
      webserver.accesslog.path=access.log
      # HTTP Request Log retention days
      webserver.accesslog.retention.days=14
    clusterConfig: |
      {
        "min.insync.replicas": 3
      }

Thanks!

Please attach your koperator logs

Hi, I've been having the same trouble, I followed the document to setup https://banzaicloud.com/docs/supertubes/kafka-operator/install-kafka-operator/ , everything runs well if i use this yaml file to run the kafka brokers https://github.com/banzaicloud/koperator/blob/master/config/samples/simplekafkacluster.yaml; However if i use this one https://github.com/banzaicloud/koperator/blob/master/config/samples/kafkacluster-with-istio.yaml there aren't any kafka brokers created and only this two pods are shown running without any errors.

The https://github.com/banzaicloud/koperator/blob/master/config/samples/kafkacluster-with-istio.yaml requires to have an  Istio mesh deployed into your Kubernetes cluster using https://github.com/banzaicloud/istio-operator/tree/v2.11.7
Can you confirm that you deployed Istio first and is up and running? If so please attach you koperator, istio-operator logs and also your IstioControlPlane custom resource.

Closing this ticket as did not receive the requested info which is needed to further investigate this issue and rule out that is not a user error.


[TECH DEBT] Need tests for existing modules

Description of the tech debt to be addressed, include links and screenshots
It seems these modules were created back in 2016 before there were stricter requirements for tests. The test framework is in place with some boilerplate, but we need to get some actual test code to cover the existing functionality.

Interested in things this on! I'll start with the utils/ folder

Would we want to use PyTest for this? I'm unsure what the wider Python community uses. I think it would be a good option since in seems to come with handy mocking features :)

Hello @vipermark7 ! Yes, the Salt Extensions expect to use nox to call pytest so the tests should be written in that fashion. You can look at some of the other Extensions which have tests for examples on how to structure them. If you have any additional questions, feel free to ask!

I got a new unit test to pass locally! I thinkk I'll need write access to push it to my new branch though

Great! Regarding contribution workflow, we use the Fork-and-Branch Workflow that is prevalent in OSS. So, you should be able to fork the repo, create a branch in your fork to hold and changes, and then open a PR to merge your branch into main back in this repository.

Oh, OK, thanks!
That occurred to me as soon as I posted my comment x(
On Wed, Feb 7, 2024, 3:07 PM Nicholas Hughes @.***>
wrote:

Great! Regarding contribution workflow, we use the Fork-and-Branch
Workflow
https://blog.scottlowe.org/2015/01/27/using-fork-branch-git-workflow/
that is prevalent in OSS. So, you should be able to fork the repo, create a
branch in your fork to hold and changes, and then open a PR to merge your
branch into main back in this repository.
—
Reply to this email directly, view it on GitHub
https://github.com/salt-extensions/saltext-github/issues/9#issuecomment-1932782992,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACKMZRFEX44UGIVXAG7AUBLYSPNJFAVCNFSM6AAAAABBZASVNWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZSG44DEOJZGI
.
You are receiving this because you were mentioned.Message ID:
@.***>


[Bug] Character encoding issues

Describe the bug A clear and concise description of what the bug is.
Some characters are not being encoded or parsed correctly in the API documentation
To Reproduce Steps to reproduce the behavior:

Go to https://developer.sailpoint.com/idn/api/beta/certification-campaigns
Scroll down to the section pictured

Expected behavior A clear and concise description of what you expected to
happen.
Actual behavior A clear and concise description of what actually happens.
Screenshots If applicable, add screenshots to help explain your problem.

Operating System (please complete the following information):
Browser: Vivaldi 5.4.2753.51 (Stable channel) (arm64)
OS: MacOS Monterey 12.6
CLI Environment NA
Additional context Add any other context about the problem here.

from what I can tell, It looks like this can be traced all the way here:
https://github.com/facebook/docusaurus/blob/6c8af03f513891c7ff6ab049480e274cc12d119a/packages/docusaurus/src/client/exports/Translate.tsx#L33
Path I followed is:

products/idn/api/beta/sidebar.js

import DocCardList from '@theme/DocCardList';
import {useCurrentSidebarCategory} from '@docusaurus/theme-common';

<DocCardList items={useCurrentSidebarCategory().items}/>

https://github.com/facebook/docusaurus/blob/main/packages/docusaurus-theme-classic/src/theme/DocCardList/index.tsx

<DocCard item={item} />

https://github.com/facebook/docusaurus/blob/main/packages/docusaurus-theme-classic/src/theme/DocCard/index.tsx

description={translate(
        {
          message: '{count} items',
          id: 'theme.docs.DocCard.categoryDescription',
          description:
            'The default description for a category card in the generated index about how many items this category includes',
        },

but I could have missed something in between.

Fixed in a previous pull request.


Best fix scan recommendations does not work with cpggen

As we do not pass any arguments in the workflow for cpggen, how do we work on the scan recommendations provided by 'Bestfix' ?
As an example, I used cpggen for the app 'Fineract' and then executed bestfix for this app. The scan recommendation were as below.
How do we work on those scan recommendations?

@nishfath Bestfix.ai currently doesn't recognize how the CPG gets generated. I will keep this as a requirement while working on an update.


Convert votingProceduresTxBodyL to a Map

Currently votingProceduresTxBodyL is defined as a sequence, which is problematic because it allows duplicate proposals.
Duplicate proposals don't make sense in general, but in the same transaction they will even cause issues when identifying a script with a ScriptPurpose.
For this reasons
  , ctbrVotingProcedures :: !(StrictSeq (VotingProcedure era))

must be switched to:
  , ctbrVotingProcedures :: !(Map (VotingProcedureId (EraCrypto era) (VotingProcedure era))
...

data VotingProcedureId c = VotingProcedureId
  { vpiGovActionId :: !(GovActionid c)
  , vpiVoter :: !(Voter c)
  }

This means that the VotingProcedure will loose the above two fields:
data VotingProcedure era = VotingProcedure
  { vProcVote :: !Vote
  , vProcAnchor :: !(StrictMaybe (Anchor (EraCrypto era)))
  }

I just realized  that it is actually much better to switch to a nested Map for representing VotingProcedures:
newtype VotingProcedures era = VotingProcedures
  { unVotingProcedures ::
      Map (Voter (EraCrypto era)) (Map (GovernanceActionId (EraCrypto era)) (VotingProcedure era))
  }

It does make decoding slightly more involved, namely we need to enforce that there are no nested empty maps, but it comes with very nice benefits:

The most common case where a DRep or CC votes on a lot of proposal in a same transaction becomes a lot more efficient, both:

with respect to CBOR serialization, because a single Credential is being encoded, instead of as many as there are votes
JSON serialization becomes possible, in case whet it is needed. Otherwise encoding a Voter+GovActionId as a key of a map is quite ugly, something like this: ScriptHash-0x12345678...-0xdeadbeef...#2

Better runtime performance

with respect to memory representation
with respect to rules. There is no need to filter out on DRep's credential anymore, it is a O(log n) lookup.

I like that change, but I probably wouldn't put it in the spec.
There is some room for tweaks still, since we don't know exactly what the most common pattern would be: it could also be the case that people vote for different roles, in which case splitting the Voter and putting a set of roles in VotingProcedure would be even more efficient. But what you have here is probably good enough for all cases and there's no need to make this more difficult.


dsp_geniee Bid Adapter : add dsp_geniee.md

🏷 Type of documentation

[x] new bid adapter
[ ] update bid adapter
[ ] new feature
[ ] text edit only (wording, typos)
[ ] bugfix (code examples)
[ ] new examples

📋 Checklist

[x] Related pull requests in prebid.js or server are linked -> Paste link in this list or reference it on the PR itself
[x] For new adapters check submitting your adapter docs

https://github.com/prebid/Prebid.js/pull/10834

@bretg
Thanks for the review.
We have just fixed it.


NaN during training

HI, I try to reproduce the training process, but get NaN D_loss after several training steps. I think that is because torch.sqrt in CriterionAdditionalGP  rerurns a NaN. I refer to https://github.com/pytorch/pytorch/issues/2534 and add 1e-8 to the grad_norm,

but can't help. Any suggestions?

@Jankyee
Hi, I got the same error!
Did you resolve this problem?
If so, could you help me?
Thanks.

can you sent your training log to me? I also got  worse result


Update README.md

Before contributing, please read our contributing guidelines and code of conduct.
Overview
Documentation typo fix. Sorry. My OCD kicked in.
Related Github Issue
N/A
Testing
The agent includes a suite of unit and functional tests which should be used to
verify your changes don't break existing functionality. These tests will run with
Github Actions when a pull request is made. More details on running the tests locally can be found
here for our unit tests,
and here for our functional tests.
For most contributions it is strongly recommended to add additional tests which
exercise your changes.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@nbolser, thank you for submitting this fix!  Happy to accept even the minor fixes.  If you could sign the CLA, we can then merge your PR and wipe out that typo.

@nbolser thanks for the updates.  We appreciate the contribution. Please note that we would appreciate it if you can sign the CLA for future code contributions.  It's a process step that we apply across all New Relic Open Source repositories.

@angelatan2 Hi. Sorry about that. I'm just catching up on this account now. Noted for future contributions. Happy to help, even if very minor.


#define ⇒ enum?

Would you like to replace more defines for constant values by enumerations to stress their relationships?

…_COLOR
TRACER_…

While its a nice to have, this is currently not on our priority list. Feel free to submit a PR.


InternalServerError in SearchAsync()

When trying to search for players InternalServerError error appears.
Could not find member 'debug' on object of type 'AuctionResponse'. Path 'debug', line 1, position 9.
Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject(Object newObject, JsonReader reader, JsonObjectContract contract, JsonProperty member, String id)    em Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateObject(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)    em Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateValueInternal(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)    em Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)    em Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)    em Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)    em Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings)    em UltimateTeam.Toolkit.Requests.FutRequestBase.<Deserialize>d__22`1.MoveNext()
My code:
var searchParameters = new PlayerSearchParameters
            {
                Page = 1,
                Level = Level.Gold,
                ChemistryStyle = ChemistryStyle.Sniper,
                League = League.BarclaysPremierLeague,
                Nation = Nation.Norway,
                Position = Position.Striker,
                Team = Team.ManchesterUnited
            };

            var searchResponse = await client.SearchAsync(searchParameters);

All other methods work normally , only that SearchAsync gives error .

Take a look at #143.  Also, the example in the README file is bad, since there are no norwegian strikers in manchester united anymore :smile:

I 'm trying to connect with the recently created account , to access the Transfers Market by WEB APP me on my browser displays this message ...

I think that's the problem ... Has anyone experienced this same problem ?

You must continue to play FUT on your console, then the market will unlock when they verify your account.

I was using a newly created account and had not played the required amount of matches to unlock access to tranferencia market, therefore the error was occurring.


[Enhancement] Allow deployment in non-SPA mode

Using Cognito client secret
And without SPA routing (the error document for 404 and default root object)

@ottokruse, this is something I'm looking at possibly tackling for the project. Would you be able to provide more detail around the "Using Cognito client secret"? In my testing so far the original validation still works with a non-SPA application, but I may be misunderstanding the requirement. Thank you!

Great to hear you're willing to work on this.
More info:
The Cognito User Pool client should be created with a client secret. Then when interacting with the Cognito endpoints from Lambda@Edge, the cleint secret must be provided using HTTP basic auth. Read more about this here:

https://docs.aws.amazon.com/cognito/latest/developerguide/user-pool-settings-client-apps.html
https://forums.aws.amazon.com/message.jspa?messageID=820844

TL;DR - adds a bit of extra security. Attackers also need the client secret to be able to sign-in programmatically.
Does that help?

Sure does @ottokruse. I'll see what I can come up with here. Thanks!

Hey @ottokruse. I started working through the branch and am currently at the step to pass in the ClientSecret to the configuration values. Ran into an issue however, it appears that this value is not obtainable except through Console or CLI invocation at this time. https://forums.aws.amazon.com/thread.jspa?messageID=800824

Curious if you have any preferences for how you would like to move forward with the implementation?

Ah, that's annoying!
We could extract the client secret with a custom resource. We can change an existing custom resource to this end: src/cfn-custom-resources/user-pool-client/index.ts
On line 47 in that file, the user pool client is updated. That call returns a.o. the client secret, that we could export in the Data on line 50.
Guess that would be the most pragmatic way to solve this. What do you think?

It seems like a great approach to me. I'll work on tackling that and let you know if I run into other issues. Thank you!

Hey @ottokruse, another question about the client secret. Wouldn't this be something that should be implemented in both cases (SPA/Non-SPA) if it's an extra level of security? It seems like if we have it for one we'd want it for both.
If that's the case should we make that a separate PR from the SPA/Non-SPA designation to keep things clean?

It is related actually. In SPA mode, we want to enable the SPA to make requests against Cognito (to e.g. sign-out or refresh tokens). Since the SPA is JavaScript running in the Browser, it can't use a client secret (technically it could, but it wouldn't be a secret would it, and just adds complexity).

Ahhh, yes that makes sense. Ok I'll keep it all as part of a single PR.

Almost ready to submit the PR, just have a couple of design questions for you @ottokruse:

I'm currently turning off the DefaultRootObject if we're in NonSPAMode, which results in an error when trying to poll the root. Should we add an option to specify the DefaultRootObject that the user would desire?

When in NonSPAMode I'm turning off the ReactApp and ReactAppHandler resources. Do we want to load a separate sample application in its place? Or just leave it up to the user to populate the empty bucket?

Thanks! Looking forward to getting this in place.

Great to hear it's nearly there!
Would be good I guess to in non-SPA mode prepopulate the bucket with an index.html file only that shows some banner content like "Welcome! Please replace me with your own files", and some explanation on what to do.
Then we can leave the default root object to index.html
Think that will actually be clearest to most users. The "error" you refer to (1) is not really an error it's just the result of the ListBucket operation, which CloudFront does if you go to "/" and no default root object defined (there is something to say for this too, but I think most users will think something is wrong).
Agreed?
You can steal from the ReactApp custom resource if you want, for the prepopulation of the S3 bucket.

Agreed. I think that makes a lot of sense. I'll make those updates and get the PR in asap. Thanks again.

Fixed by #42


Add all refs to subsets

I feel like we had this discussion of "what IDs should be considered verified" before, and we wanted to try and centralise the decision into the frontend because we wanted to be able to have app.name.Bla.Extension be a different app-ID and different vending settings / license to the main app. So should this little harcoded list not live in the frontend and the hooks check each one?

Yes, refs matching .Extension (and whatever else we came up with over the years) will need to be handled elsewhere to be tied to ownership.


doc/releases: v2.6.0: Update for SoCs and ARM boards

Add list of new SoCs and ARM boards added in this release.
Signed-off-by: Kumar Gala<EMAIL_ADDRESS>

@ioannisg can you take another look.


Error connecting Meshnet on arm64/kubernetes

Currently getting the following error running on Kubernetes arm64.
Can't really find the problem yet, NordVPN client logs on correctly but fails when trying to enable Meshnet.
Whoops! Connection failed. Please try again. If the problem persists, contact our customer support.

After some more troubleshooting I was able to dig up the following error from the NordVPN client logs:
[Error] setting mesh: enabling exit node: enabling filtering: iptables listing rules: exit status 3: iptables v1.8.4 (legacy): can't initialize iptables table filter': Table does not exist (do you need to insmod?)`
This seems to indicate that the Kubernetes node is missing some IPtables modules, I'm currently running Oracle Linux 8.7 OKE images on the Oracle Cloud OKE cluster.
Running on local Kubernetes based on Debian images seems to work fine. Will have a look at this later.

Running the following command on the host/node fixes the error.
sudo modprobe iptable_filter
Will have to see if there is a way to work with this from the docker-compose and Kubernetes deployment files instead of having to touch the host/node.

Will be adding this to the documentation instead, implications are too big.


V1.0: Migrate pages as a temporary MVP

What's happening
Case Studies
Contribute
FAQ and Contact (taking this out of the 'Help' drop down)

We have future plans for these pages, but reworking these is out of scope for V1.0

We no longer need this issue. Content has been migrated via remote MDX according to LHN proposal.

See above


Make the install test more platform agnostic

Enumerate and query the nodes in the test cluster to
a) Determine what IP address to use for the test registry
b) If there a nodes labelled for mayastor
c) Configure pools on suitable labelled nodes

bors merge


Remove admin/js/jquery.init.js from SortedCheckboxSelectMultiple

jquery.init.js seems to be used by Django's admin templates to remap $ into django.jQuery, and then remove $ from the global scope. Its contents are:
var django=django||{};django.jQuery=jQuery.noConflict(true);

(See https://api.jquery.com/jQuery.noConflict/.) This means that including a SortedCheckboxSelectMultiple widget on a page that expects jQuery to be accessible under $ breaks code on that page.
This commit removes the loading of jquery.init.js, which fixes this issue. The existing code does not appear to be relying on its behaviour, and it was introduced recently in 19a11c99d97f4f991d4d45ab4615d747dabd25fe (without explicit justification that I could find).

Just wanted to confirm that the removed JS does not seem to be necessary even on 2.2 (to which we have upgraded), and that the CI failure seem to be unrelated to this change.


Foreign key code not generated

In the case of mysql 5.7.17, PHP 7.1.1, Yii 2.0.10

This problem occurs after Yii version 2.0.7


Where is the model backbone.plan?

I run program like this, but I got an error.
./pointpillar ../data/ ./out

GPU has cuda devices: 1
----device id: 0 info----
  GPU : GeForce RTX 2070
  Capbility: 7.5
  Global memory: 7974MB
  Const memory: 64KB
  SM in a block: 48KB
  warp size: 32
  threads in a block: 1024
  block dim: (1024,1024,64)
  grid dim:<PHONE_NUMBER>,65535,65535)

Total 10
An empty file has been loaded. Please confirm your file path: ../model/backbone.plan
Failed to create lidar backbone & head.
Core has been failed.

I only find model backbone.onnx in folder model.

Still the same issue:
No backbone.plan in main.cpp:153
https://github.com/NVIDIA-AI-IOT/CUDA-PointPillars/blob/main/src/main.cpp

How to solve this problem?

@JunjieWang0528 , did you manage to solve this?

pointpillar.plan is generated by sh tool/build_trt_engine.sh using the trtexec, make sure the location of trtexec is correct.


Offline installation / prevent callout to dbt hub

Due to an enterprise setting I cannot cirectly load packages from dbt hub.
I have mirrored the dbt-codegen to my internal gitlab instance.
However,
- git<EMAIL_ADDRESS>    revision: 0.9.0

fails with:
External connection exception occurred: HTTPSConnectionPool(host='hub.getdbt.com', port=443): Max retries exceeded with url: /api/v1/index.json (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x00000232D005CA60>, 'Connection to [hub.getdbt.com](https://hub.getdbt.com/) timed out. (connect timeout=30)'))

due to firewalling.
Other packages like dbt-utils work just fine in this way. How can dbt-codegen support such an offline installation as well?
I did not find the place where the dbt installer is calling out to dbt hub.

I think https://github.com/dbt-labs/dbt-codegen/blob/main/packages.yml the references to the packages from DBT hub is the problem. DBT utils itself is already available but from the internal system. I would love to not have to fork/change the reference


Unparseable date: "%cI"

It works pretty well on my local Windows machine(with Git version 2.x). But when I ran it on my Linux server(with Git version 1.x), it failed.

Execution failed for task ':createVersionFile'.
java.text.ParseException: Unparseable date: "%cI"

My build.gradle
plugins {
    ...
    // For reading commit id
    id "com.peterabeles.gversion" version "1.5.0"
}
...
gversion {
    srcDir       = "src/main/java/"
    classPackage = "com.my.package.name"
    className    = "GitVersion"
    dateFormat   = "yyyy-MM-dd HH:mm:ss"
    timeZone     = "America/Los_Angeles"
    debug        = false
    language     = "java"
    explicitType = false
}
...
project.compileJava.dependsOn(createVersionFile)

Here's the stacktrace
It looks like it comes from here https://github.com/lessthanoptimal/gversion-plugin/blob/master/src/main/groovy/com/peterabeles/GVersion.groovy#L223.
java version "1.8.0_181"
git version <IP_ADDRESS>
CentOS Linux release 7.6.1810

thanks for the detailed bug report. I'll work on replicating it when I get back from vacation. That should be in about two weeks.

no worries. Enjoy your vacation!

May be problem at
static int[] parseGitVersion( String text )
because at my local repository
> git version
git version <IP_ADDRESS>

And version has 4 leksem

sorry for taking so long. You guys probably came up with another solution! I believe this to be fixed and should work with an almost arbitrary number of leksem.  Version 1.5.2

I still get this issue when running gradle build inside Bitbucket Pipelines.  Any insight?

@katelovescode I just noticed this comment from last year. If you're still willing, could you post the error message what what "git version" produces on Bitbucket?

@katelovescode I just noticed this comment from last year. If you're still willing, could you post the error message what what "git version" produces on Bitbucket?

Sorry, I don't have access to the project anymore, it was for a client :(  If I run into it again, I'll let you know!


Add support for serving Styled Map Package maps

Description
We want to be able to serve offline maps that follow the format described in https://github.com/digidem/styled-map-package/.
Ideally, I think this eventually replaces the "legacy" Mapeo approach that we currently support. For now, can probably build this functionality side-by-side.
Tasks

[ ] Expose functionality for importing and retrieving information about an SMP-based map.

importing = persisting the file path of the SMP file on the device to core.
based on app requirements, we'll need the following information about an SMP map:

date added
storage used
name

[ ] Implement a Fastify plugin for serving the SMP file based on the location from ^

Seems reasonable to me, at least at a high level.
We already have a Fastify plugin in the styled-map-package module, if helpful: https://github.com/digidem/styled-map-package/blob/0ede1b97bcdd0feb1df775025d0a7063dae6bf37/lib/server.js

Seems reasonable to me, at least at a high level.
We already have a Fastify plugin in the styled-map-package module, if helpful: https://github.com/digidem/styled-map-package/blob/0ede1b97bcdd0feb1df775025d0a7063dae6bf37/lib/server.js

Ah nice! Didn't see that - hopefully means less work then 👍


feat(language): updating arkscript documentation

Pull Request Type
Please specify the type of pull request (please only check one of these):

[ ] Sample Program Documentation
[x] Language Documentation
[ ] Other (explain in the Notes section)

This pull request must have a corresponding issue number. If you have
not already done so, please create a new issue.

I fixed #632

Notes
Feel free to share any details you feel are relevant.

Hi, sorry I went headfirst and forgot to check the contributing.md having seen arkscript.* files.
You can merge as is, I'm not participating in this year's Hacktoberfest!


To/FromJSON instance

It would be great if we could serialize unserialize via Aeson dimensionnal values.
for now we have this.
• No instance for (FromJSON
                     (dimensional-<IP_ADDRESS>:Numeric.Units.Dimensional.Internal.Dimensional
                        'Numeric.Units.Dimensional.Variants.DQuantity
                        Numeric.Units.Dimensional.Dimensions.TypeLevel.DLength
                        Double))
    arising from a use of ‘aeson-<IP_ADDRESS>:Data.Aeson.Types.FromJSON.$dmparseJSON’

thanks for considering

I have no objections but would appreciate a patch if you want it sooner rather than later (I guess it already is “later” – sorry). I'm thinking it will have to rely on Numeric.Units.Dimensional.Dynamic and should probably go in dimensional-dk-experimental or a package of its own.

If someone wants to work on this, this PR can be used as a template: https://github.com/bjornbm/dimensional/pull/224


Refactoring AWS Authentication across the plugins

Not using special environment variables like AWS_USE_IAM_ROLE to enable the IAM Role Access. Using the AWS SDK's AWSCredentialsProviderChain in the following order

Environment Variable Based
System Properties Based
Profile on the credentials file based
Instance Profile based
Basic Auth using the Keys from the configuration property explicitly
Anonymous access (if enabled)

@manojlds @brewkode Feedback please.

@haimizrael Looping you in, for your feedback.

Though other solutions may exist, we have an use case where this environment-variable trigger was necessary to override AWS access keys set at the system level and authenticate the s3 plug-ins via the instance profile.  Specifically, a pipeline task authenticates to aws via access key (giving it rights possibly in a different aws account), while the s3 plugin authenticates via the role.
The main issue is allowing the s3 plugins authenticate with one set of rights to aws while other tasks in the pipeline authenticate with different set of rights.  If AWS_USE_IAM_ROLE is removed, I think we'd need a different mechanism - perhaps a variable that holds an AWS role name to assume.  If present, the s3 plugin assumes that role to perform the work.  Otherwise, if using solely instance profile, you'd have to give all your instance profiles rights to access the s3 artifacts buckets plus other, application, rights, which compromises security by giving too much access rights to all roles.

@haimizrael Please help me with few clarifications just so I understand this better

Specifically, a pipeline task authenticates to aws via access key (giving it rights possibly in a different aws account), while the s3 plugin authenticates via the role.

Well according to AWSCredentialsProviderChain, it would pick up the first authentication mechanism that allows access to the required artifact bucket. Assuming access key has fewer permissions than InstanceProfile, we would naturally pick only the instance profile. If latter is true, we would only use aws keys available on the machine (GoCD Server and all agents for material plugin, and only the agents for fetch and publish plugin).

The main issue is allowing the s3 plugins authenticate with one set of rights to aws while other tasks in the pipeline authenticate with different set of rights.

I would really love to know how do you handle this scenario in your current setup? Is it like the AWS keys on the instance has more access permissions while the Instance profile has only GoCD specific access? And you use the AWS_USE_IAM_ROLE environment variable to force use IAM roles and not use AWS keys on ~/.aws/credentials? From the previous quote, I understand this is the case. Please correct me if my understanding is wrong. Assuming the above claim is right, I don't understand how is this approach better from the security standpoint? If someone has access to the machine they might as well use the ~/.aws/credentials to perform whatever actions they want and same holds true for Instance Profile as well isn't?

If AWS_USE_IAM_ROLE is removed, I think we'd need a different mechanism - perhaps a variable that holds an AWS role name to assume.

Is this related to #40 ?

@haimizrael @brewkode @manojlds If there are no more comments / concerns, can we merge this?

@ashwanthkumar : Apologies for not following up. I somehow missed your update and questions on my post.
My main issue is that, because environment variables (and thus - AWS authentication) can be controlled at the Go Job (and not Go Task) level, without ind s3 plugin-specific environment variables to control the AWS authentication (such as AWS_USE_IAM_ROLE), I cannot easily have in the same Go Job the Fetch S3 Artifacts task use one AWS auth, while the remaining tasks in that Job use different AWS auth.
Our specific situation is that we have different AWS accounts (prod, non-prod, etc.).  Go artifacts are stored in a bucket accessible by the owning account, and agents whose primary workload is in a different account need to access this bucket to fetch or push artifacts, while the remaining work is done in another AWS account.  While it is technically possible to provide cross-account access to the bucket, due to organizational constraints and the number of Go servers and teams that use them, that is not currently feasible for us.  A solution like you mention in #40 would definitely help, as then access can be controlled via a single role (and grant other aws creds to assume it), as opposed to granting resource access to multiple roles and accounts.
In regards to your specific question regarding having both secret/access key and role access via the machine: we apply access/secret keys via encrypted environment variables in Go (not ~/.aws/credentials) such that if one would gain access to the machine, they would only have access to the role associated with the instance profile.
Bottom line: while I do like the simplicity of AWSCredentialsProviderChain for authentication, without an assume-role solution as described in #40, if you merge this PR in we'd have to stay on our fork as we won't be able to function with it in our environment.

Bottom line: while I do like the simplicity of AWSCredentialsProviderChain for authentication, without an assume-role solution as described in #40, if you merge this PR in we'd have to stay on our fork as we won't be able to function with it in our environment.

@haimizrael I wanted to lay the foundations for implementing #40 with this PR. Rest assured, we should have #40 also baked in when we're going to make the first release with this PR. I hope that answers the above mentioned concerns?

Yes, with #40 in the release, we'd have a way of implementing this in our situation.
Thanks, @ashwanthkumar

So I finally got the time to work on #40.  Just curious what's the status of this PR?  Are you planning to merge any of this code into eventually or is it just a dead-end branch?

Closing this in favour of #53


add test coverage to json-forms

to support #12, I can add test coverage

Thanks @monte-hayward!
It would be great also including a simple test that serves as an example for the future ones.
Please send me a PR when you feel comfortable the changes

cool project you have here, @idelvall!

:) Thanks mate!

Hi, @monte-hayward.
I have noticed you referenced this issue in a commit.
Please send me a pull request if you consider I should include these new features
Cheers


Proxy Support

I know Node can sort of be a pain with adding proxy support, but it would be great if we could use the Netlify CLI behind a corporate proxy. Thanks!

Open to the idea. What are the requirements? Any suggestions on how to best support this?

My use case is sort of extreme, so I was initially thinking I'd put this out there to start keeping track of the feedback and then think about implementation when it hit critical mass.  If we didn't have this, we could probably just set up a Jenkins job on a server with a firewall rule.
Requirements:

Parse $http_proxy in the form of http://user:pass@host:port and do basic auth
Be able to support additional certificates like AWS_CA_BUNDLE since SSL intercepting proxy

I see you're using node-fetch.  If this was a normal package and not a CLI you could just allow someone to pass in an HTTP agent in the constructor config, which could still work for the js-client repo.
One sort of far-out idea for implementation was having a separate package with the proxy code as a peer dependency.  That way people would only have to install it if they needed it.  The CLI would inject it into the client if it existed (pseudocode below).  That way the vast majority of people could just use the normal package and you all wouldn't have to worry about testing the proxy code to make sure it didn't break things for everyone else.
const netlifyCliProxy = require('netlify-cli-proxy');
const agent = netlifyCliProxy ? netlifyCliProxy.agent : null;
const client = new NetlifyAPI('1234myAccessToken', {agent});

Its possible we could swap the agent in https://github.com/netlify/js-client.  Does Node have built in system proxy support we could leverage?  I've never looked into that before, I'll look around.

Unfortunately node doesn't have native support.  It uses http[s].Agent objects to do any proxy customization.  Here is a specific issue about that in node-fetch.
The proxy implementations are third party and have various levels of functionality.  I had used tunnel before, but it looks like https-proxy-agent supports proxy auth.  I will try it out.

How does this look?  The only additional dependency is https-proxy-agent.  fs and uri are core node modules, but with only including them just in the cli package we don't have to worry about browser compatibility.  The only change to the client-js package would be allowing an agent to be specified in the constructor opts.  If proxy environment variables are not set, then agent is undefined and there is no change to the behavior.
const fs = require('fs');
const url = require('url');
const fetch = require('node-fetch');
const HttpsProxyAgent = require('https-proxy-agent');

const demoRequestUrl = 'https://open-api.netlify.com';
const proxyUrl = process.env.https_proxy || process.env.http_proxy;
// follow the naming convention of REQUESTS_CA_BUNDLE and AWS_CA_BUNDLE
const caFilename = process.env.NETLIFY_CA_BUNDLE;
let agent; // only set if configured via env vars

if (proxyUrl) {
  const agentOpts = url.parse(proxyUrl);
  if (caFilename) {
    try {
      agentOpts.ca = fs.readFileSync(caFilename);
    } catch (error) {
      // this should be a real logger
      console.log('WARN: could not read CA file');
    }
  }
  agent = new HttpsProxyAgent(agentOpts);
}

// now we can inject agent into client-js opts and it can pass into fetch
fetch(demoRequestUrl, { agent })
  .then(res => res.text())
  .then(text => console.log(text));

@danieladams456 thank you for the thorough research!  Yeah, this sounds good to me.

Add an agent option to js-client
Add some flags / ENV var support for passing in / loading urls and certs via CLI.

This sounds like something that may be a good fit for the global config object.  Do you see yourself needing to toggle a proxy config depending on where you are running it?

Thanks!  I have setproxy and setoffnetwork functions in my bash profile that I use to toggle the 6 environment variables that work across all the languages/tools.  I find that more streamlined than having to pass flags to each command.
I could see the use for a global config object being helpful as more of these type of requests come in.  I know some packages for that, but they are more targeted at server side (env vars + layered config files.)  I'm sure there are some CLI config packages out there.  We use traefik at work for our internal stuff, and its config system flaeg seems really solid.  Go doesn't really help in this case though. 😄

also requested by netlify customer in this conversation:  https://app.intercom.io/a/apps/q245f50x/inbox/inbox/unassigned/conversations/20015116786

I'm hoping to refactor the code paths soon, and I can try to add this in then.

Wanted to jump in and see if this ever got implemented into the CLI tool. Our entire company is fully required to operate behind a corporate proxy, so I don't have many other options. Thanks guys!

yes, proxy support is really helpful in China
netlify login
Logging into your Netlify account...
    FetchError: request to https://api.netlify.com/api/v1/oauth/tickets?client_id=d6f37de6614df7ae58664cfca524744d73807a377f5ee71f1a254f78412e3750 failed,
    reason: connect ETIMEDOUT <IP_ADDRESS>:443
    Code: ETIMEDOUT

dig api.netlify.com +short
<IP_ADDRESS>

nali <IP_ADDRESS>
HTTP/1.1 200 OK
Date: Sun, 02 Aug 2020 13:31:09 GMT
Content-Type: application/json; charset=utf-8
Content-Length: 295
Access-Control-Allow-Origin: *
X-Ttl: 60
X-Rl: 44

{
    "status": "success",
    "country": "United States",
    "countryCode": "US",
    "region": "MO",
    "regionName": "Missouri",
    "city": "Kansas City",
    "zip": "",
    "lat": 39.0997,
    "lon": -94.5785,
    "timezone": "America/Chicago",
    "isp": "Google LLC",
    "org": "Google Cloud (asia-south1)",
    "as": "AS15169 Google LLC",
    "query": "<IP_ADDRESS>"
}

this ip is blocked in china...
and netlify cli does not read HTTP_PROXY env.
i use the latest version netlify.
netlify version
netlify-cli/2.58.0 darwin-x64 node-v14.6.0

Is there an update on this issue?
Thanks.

Opened a draft PR for this issue https://github.com/netlify/cli/pull/1215, if someone would like to try it out and provide some feedback.
You can follow the steps here https://github.com/netlify/cli#development to run locally (switch to the PR branch).

I git-cloned the repo, checkoute on the proxy support branch, cd to my web and run netlify deploy --prod,  I got the following error.PS. my internet is on the vpn service now.

 ›   Error: request to
 ›   https://api.netlify.com/api/v1/sites/ce7ab13d-f71e-432d-b263-eaf3a3236c8f
 ›   failed, reason: connect ETIMEDOUT <IP_ADDRESS>:443
/Users/lzhan/cli/node_modules/@oclif/errors/node_modules/fs-extra/lib/mkdirs/make-dir.js:85
      } catch {
              ^

SyntaxError: Unexpected token {
    at createScript (vm.js:80:10)
    at Object.runInThisContext (vm.js:139:10)
    at Module._compile (module.js:607:28)
    at Object.Module._extensions..js (module.js:654:10)
    at Module.load (module.js:556:32)
    at tryModuleLoad (module.js:499:12)
    at Function.Module._load (module.js:491:3)
    at Module.require (module.js:587:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/Users/lzhan/cli/node_modules/@oclif/errors/node_modules/fs-extra/lib/mkdirs/index.js:3:44)

I git-cloned the repo, checkoute on the proxy support branch, cd to my web and run netlify deploy --prod, I got the following error.PS. my internet is on the vpn service now.

Hi @likanzhan, there is a difference between a VPN and a proxy. When using a VPN you shouldn't need to configure a proxy with the CLI at all. I would first verify  curl -i https://api.netlify.com/api/v1/ returns a valid response (should return a 401 response).
To use the draft PR with the proxy feature you'll need to pass in the appropriate flags, e.g.
netlify deploy --prod --httpProxy=http://<proxy-host>:<proxy-port> --httpProxyCertificateFilename=<proxy-ca-file-path>

Thanks @erezrokah
when run
curl -i https://api.netlify.com/api/v1/,
I got a
curl: (35) ssl_handshake returned - mbedTLS: (-0x7280) SSL - The connection indicated an EOF

Seems like something is blocking that connection as the network level. You can try running traceroute api.netlify.com (or a similar tool for your OS) to get more insights.

@erezrokah
Here is the result

traceroute to api.netlify.com (<IP_ADDRESS>), 64 hops max, 52 byte packets
 1  localhost (<IP_ADDRESS>)  11.997 ms  1.970 ms  2.301 ms
 2  localhost (<IP_ADDRESS>)  2.170 ms  2.011 ms  2.242 ms
 3  localhost (<IP_ADDRESS>)  20.363 ms  24.229 ms  5.672 ms
 4  <IP_ADDRESS> (<IP_ADDRESS>)  14.289 ms  5.586 ms  8.063 ms
 5  <IP_ADDRESS> (<IP_ADDRESS>)  4.677 ms  7.605 ms  4.740 ms
 6  <IP_ADDRESS> (<IP_ADDRESS>)  5.126 ms
    <IP_ADDRESS> (<IP_ADDRESS>)  5.649 ms
    <IP_ADDRESS> (<IP_ADDRESS>)  10.561 ms
 7  <IP_ADDRESS> (<IP_ADDRESS>)  46.088 ms
    <IP_ADDRESS> (<IP_ADDRESS>)  37.462 ms
    <IP_ADDRESS> (<IP_ADDRESS>)  35.376 ms
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
31  * * *
32  * * *
33  * * *
34  * * *
35  * * *
36  * * *
37  * * *
38  * * *
39  * * *
40  * * *
41  * * *
42  * * *
43  * * *
44  * * *
45  * * *
46  * * *
47  * * *
48  * * *
49  * * *
50  * * *
51  * * *
52  * * *
53  * * *
54  * * *
55  * * *
56  * * *
57  * * *
58  * * *
59  * * *
60  * * *
61  * * *
62  * * *
63  * * *
64  * * *

Thanks @likanzhan, it seems the Netlify API IP address is blocked by the network you're using. Maybe other participants on this issue can help with this.

@erezrokah , Thanks. Is there a walkaround?

yes, proxy support is really helpful in China

Not sure about a workaround, but the main reason for this PR is to be able to proxy CLI requests in a way that will allow connecting to the Netlify API from a closed network (like an organisation internal network).
As for the proxy server itself that would have to be provided by users of the CLI per their networks configuration.

hi @erezrokah
yes it's blocked, and it should be easier to easy if cli can read HTTP_PROXY envs.
btw, why should i pass --httpProxyCertificateFilename flag when run netlify deploy?
λ curl -i https://api.netlify.com/api/v1/
curl: (28) Connection timed out after 60000 milliseconds

λ  proxy
HTTP Proxy on
no_proxy=localhost,<IP_ADDRESS>/0,<IP_ADDRESS>/16,<IP_ADDRESS>/0,kubernetes.docker.internal
GOS_UPSTREAM_ADDRESS=https://goproxy.cn
https_proxy=http://<IP_ADDRESS>:8118
NO_PROXY=localhost,<IP_ADDRESS>/0,<IP_ADDRESS>/16,<IP_ADDRESS>/0,kubernetes.docker.internal
HTTPS_PROXY=http://<IP_ADDRESS>:8118
HTTP_PROXY=http://<IP_ADDRESS>:8118
http_proxy=http://<IP_ADDRESS>:8118

λ  curl -i https://api.netlify.com/api/v1/
HTTP/1.1 200 Connection established

HTTP/2 401
cache-control: private, no-store
content-type: text/html
date: Thu, 10 Sep 2020 15:02:17 GMT
pragma: no-cache
strict-transport-security: max-age=31536000; includeSubDomains; preload
vary: Origin
www-authenticate: Bearer realm="user"
x-content-type-options: nosniff
x-frame-options: ALLOWALL
x-nf-srv-version: 3789f80
x-request-id: fdc1b8b4-28af-4041-a5af-2ece4e5cb7f0
x-runtime: 0.005766
content-length: 0
via: 1.1 google
alt-svc: clear

and it should be easier to easy if cli can read HTTP_PROXY envs.

It does - it falls back to env variables:
https://github.com/netlify/cli/blob/b06458fca975b7917fa607d237aec451243ecbfd/src/utils/command.js#L286
I tested with --httpProxyCertificateFilename=mitmproxy-ca-cert.pem which is the CA cert installed with mitmproxy

@erezrokah Lower case http_proxy and https_proxy support at the same time would be greater!

@erezrokah Lower case http_proxy and https_proxy support at the same time would be greater!

That would be inconsistent with the general casing of other flags. You could open a new issue to support different types of casing.


Simplify Eigen package config

I think we can avoid specifying the Eigen commit hash in multiple places by using the strip_prefix option to new_http_archive.
Here, I've declared the real Eigen includes without a prefix, while the includes in third_party can only be reached by including third_party/eigen3/... (to avoid an infinite inclusion loop).
I've used this setup to successfully build tensorflow.
This can probably still be improved by not declaring the real Eigen includes at the top level.
Maybe it's possible to access them under eigen_archive/..., although I'm not sure how to set that up.

Can one of the admins verify this patch?

Sorry, there's a conflict I just introduced from another update to eigen libraries -- can you rebase and we can try this again?

No problem, I've rebased the PR.

Sweet, let's give this a shot.  @tensorflow-jenkins test this please

hm, that's an interesting failure.  Have you successfully been able to compile with this?

I'm seeing the same problem now.
I'm pretty sure managed to compile it before the rebase, though :/

The cpu test failed with a more appropriate error -- maybe we can resolve the CPU ones first and then figure out what's going on with GPU?

I noticed that there's a new third_party Eigen header (at third_party/eigen3/unsupported/Eigen/SpecialFunctions) but adjusting it didn't help.

Okay, the CPU tests are failing because I haven't adjusted the code that creates the pip package (It still assumes that eigen is located in eigen_archive/eigen-eigen-\w+).
Not sure about the GPU tests, though.

I'm still not sure what's causing the problem with the GPU build.
Maybe the fact that Eigen is including the curand headers.
I'll have a closer look later.

Finally got around to this.
It turns out that that the problem is caused by a workaround in the GPU crosstool wrapper that's used to support CUDA <= 6.0. Does TensorFlow still support those versions? If not, I could remove it.
I've added some extra code that makes the build work with the workaround.
Both problems from before should be solved now, so we can have another go at the tests :)

I am fine dropping support for cuda 6.0, so go ahead!

Okay, I've removed that part of the crosstool script and pushed my changes.

Going to kick off a run just to see.  @tensorflow-jenkins test this please

I've pushed a new commit that isolates the eigen_version and eigen_sha256 in the bazel config and adds some code to the cmake and make builds to extract those values.
I've used built-in tools in cmake to make sure that the config stays portable.

Woohoo!  This is awesome.
@tensorflow-jenkins test this please
cc @rmlarsen  -- our hacky scripts for updating eigen just got easier.

Seems like an unrelated failure with cc_op_gen.cc, so merging.

Thanks!
If there should be an issue with the cmake build as a result of this PR, you can post it here and I'll fix it.


Is possible to copy and paste multiple tags

Hello, congratulations on your library.
I have the following query, is possible to copy and paste multiple tags into another field?
Thank you so much.

@DanielKimmich now it does :-)
https://github.com/lekoala/bootstrap5-tags/commit/2c1b03a7069171c5fe6864e883cc95f9349f5c77
you can give it a try on master, and i'll publish a new release when i got some time to review this better

Thanks for the quick reply.
I didn't understand how to use it, I copied the new code to my project.
I try to copy and paste but it does it as a single tag

copiar a:

are you using the master branch?

Hello, my separator is default
In my select I have:
<select
    class="{!!$clase!!}"
    id="{{ $name }}"
    name="{{ $name.'[]' }}"
    multiple
    data-full-width="true"
    data-allow-clear="true"
    data-allow-new="{!!$new!!}"
    data-badge-style="{!!$badge!!}"
    data-suggestions-threshold="0"
    data-selected="{!!$selected!!}"
    >

Yes i have this script "tags.js"
<script type="module">
        import Tags from "{{ asset('packages/bootstrap5-tags/tags.js') }}"
        Tags.init("#{!!$name!!}");

kind regards
D.K.

try with data-separator=" |,|  "

Excellent, adding that line in my code, it worked.
Thank you very much for your predisposition.

you are welcome
published here https://github.com/lekoala/bootstrap5-tags/releases/tag/1.6.9


wsl profile cannot have startingDirectory set to folder whose contents are unreadable

Windows Terminal version (or Windows build number)
1.11.2921.0
Other Software
No response
Steps to reproduce
Create a profile with
"commandline": "wsl -u root"
"startingDirectory": "\\\\wsl$\\Distro\\root"

Open a tab from that profile. Assumption is that /root is only readable by root in the Linux distribution.
Expected Behavior
A root prompt in Distro, with /root as the current directory.
Actual Behavior
No interactive prompt, and terminal tab has the text:
Access is denied.

[process exited with code<PHONE_NUMBER>]

More info:
This worked in earlier Windows Terminal versions.
If I set that startingDirectory for a powershell tab, it works fine.
If I set the startingDirectory to "\\\\wsl$\\Distro", it works fine

4294967295 is ERROR_UNHANDLED_ERROR, cool, that's useless.
Seems to work just fine from the commandline,

So this should work. huh.

This is an interesting outcome from promoting the starting directory to --cd, actually.
Terminal ends up calling wsl --cd \\wsl$\Distro\root, not wsl --cd /root. wsl.exe attempts to open \\wsl$\Distro\root, fails because the Plan9 server throws it an access error, and then just aborts.
The thing is... at this point, Terminal is fully out of the equation. It doesn't control whether wsl aborts when it encounters this issue.
My only question is ...

This worked in earlier Windows Terminal versions.

What did it do? Where did it put you? That directory is illegal to access :smile:

It did what I wanted, I had a root prompt and the working directory was /root. You may not be able to access anything in the directory, but apparently you can still set it as your current folder. If you set that path as startingDirectory for a powershell instance instead, it will happily give you a powershell prompt. Get-ChildItem will give access denied of course, but it has no objections to making it the current folder.

WSL Ubuntu has /root permission set to 700. Relaxing it a bit (like 755) it will allow /root access.
Here's sample output from pwsh prompt after changing permission:
PS C:\Users\tux> ls '\\wsl$\Ubuntu-20.04\root'

    Directory: \\wsl$\Ubuntu-20.04\root

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d----            5/3/2021  8:38 AM                .cache
-----           11/4/2021  6:26 PM            346 .bash_history
-----           12/5/2019  6:39 AM           3106 .bashrc
-----           11/4/2021  6:06 PM              0 .motd_shown
-----           12/5/2019  6:39 AM            161 .profile

PS C:\Users\tux>

Profile setting:
            {
                "colorScheme": "Campbell",
                "commandline": "C:\\Windows\\system32\\wsl.exe -d Ubuntu-20.04 -u root",
                "guid": "{ddd8505c-b727-4659-8496-a060f860cb7b}",
                "hidden": false,
                "icon": "ms-appx:///ProfileIcons/{9acb9455-ca41-5af7-950f-6bca1bc9722f}.png",
                "name": "Ubuntu-Test",
                "startingDirectory": "\\\\wsl$\\Ubuntu-20.04\\root"
            }

However, relaxing /root file permissions might become a security issue.

I have the same problems. l fixed it:
First, for terminal command
$ wsl
$ cd /
$ sudo chmod 755 root

Then, for terminal settings:
"commandline": "wsl.exe -d Ubuntu-16.04 -u root",
"startingDirectory": "\\\\wsl$\\Ubuntu-16.04/root",

Is this still happening? Nowadays, we're recommending linux style paths for these kinds of scenarios.


Do I need to manually update @angular packages when updating Angular-CLI?

When I simply follow the instructions to upgrade Angular-CLI, I sometimes end up with issues.
Most recently when I run ng init I get the error core_1.Version is not a constructor. In another issue I found that I need to lock my @angular packages to a specific version. So that means I need to manually update my @angular packages prior to running npm i and ng init?

What version of the CLI are you running and what versions of angular are currently installed?

I had @angular packages at "~2.1.0" and the latest Angular-CLI ("^1.0.0-beta.24"). Then it gave me that error.

After manually updating all @angular packages to "~2.4.0" it works, but this is not mentioned in the docs. So hence my question, is this the normal thing to do? If so, how do I know which version I should update my @angular packages to in order to make them work with the latest version of Angular-CLI?

Cli beta.24 should come with 2.3.1, having it on 2.1.0 is interesting.  Did you forget to bump when you upgraded?

When you update the CLI make sure that you are running an ng-init.  One of the files it lets you upgrade / gives you diff for, shows you the "blessed" combination for versions with that version of the cli.

Hmm that crossed my mind, but the doc section Updating Angular-CLI mentions that I need to run:
# Global package:
npm uninstall -g angular-cli
npm cache clean
npm install -g angular-cli@latest

# Local project package:
rm -rf node_modules dist tmp
npm install --save-dev angular-cli@latest
npm install
ng init

Which is exactly what I did.
But the error immediately occurred when I ran ng init, so it failed before it even got to the step where it shows the diffs between the auto generated files.

What version were you upgrading from?  I know there was a couple versions (forget which) that you had to step through the immediate next cli version to get ready for the subsequent versions.

I see, maybe that's the case then. I jumped from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>

Yeah I think it was related to the big jump as @zackarychapple mentioned. We do have a warning in case you have @angular/* at less that 2.3.1 but the jump in versions might have been so big that the ng commands couldn't even function. Sorry about that :/

No problem. Thanks for clarifying @filipesilva!

Why does angular-cli install 2.3.1 versions of @angular packages on ng-init instead of 2.4.x?

@leesaenz it doesn't. It installs ^2.3.1, which resolves to the latest minor e.g. 2.4.5.
2.3.1 is the minimum supported version for the CLI.


Fix DSO resolution when importing the NetworKit Python package

This PR fixes the last outstanding cmake bug: Currently, import network from Python is broken if it is not run from a directory containing the _NetworKit DSO or if that DSO has been moved.
We fix this by setting RPATH to $ORIGIN and by properly adding the libnetworkit.so to the Python distribution. Unfortunately, this patch involves a big of black magic (i.e. hacking around distutils and setuptools internals) so it needs a thorough review. @rbange and @manpen, could you take a look?
After this PR is merged, I will merge the cmake-pr branch into Dev. After That, MSVC support can be merged.

Seems that we really more options like include_dirs. For some reason that is not needed on my machine. Could you post the content of your distutils.cfg?

My (default) MacOS distutils.cfg looks like this:
[install]
prefix=/usr/local

[build_ext]
include_dirs=/usr/local/include:/usr/local/opt/openssl/include:/usr/local/opt/sqlite/include
library_dirs=/usr/local/lib:/usr/local/opt/openssl/lib:/usr/local/opt/sqlite/lib

I continue to recommend just inheriting from the distutils build_ext command (and just calling the initialize_options function from it)

Okay, I have added code to deal with --inplace, which fixes the pip3 install -e build. The second patch should fix the distutils.cfg on macOS. I did not inherit from distutils, as I want to avoid to accept non-supported options silently. If it turns out that we really need some functionality of distutils' or setuptools' build_ext that is hard to replicate, we might want to revisit this.
Let's see if that fixes the problems.

From a technical point of view this looks nice. I tried to reproduce the travis bug for clang4.0 but failed to reproduce it.
Im am still thinking about the best practice to design the install statements:
My problem is that make install fails at least on a mac because copying files to default(/usr/local) requires admin permission, which I perceive this as an odd behaviour. I think the CMake developer defaulted on that path, because binaries should be installed to ./bin and libraries to ./lib. (Like shown in various tutorials)
Therefore I would still like to change the install target to proposed here: https://github.com/kit-parco/networkit/pull/210#discussion_r207739253 or at least only specify it when NETWORKIT_PYTHON is provided. (so make install fails when just the lib is built)

I think the Travis issue is just a timeout.
Regarding the installation: Yes, I will fix the installation path for the non-Python installation.

The last patch fixes the timeout on Travis. IMHO this series is ready to be merged. I will fix the installation in a follow-up PR. I will keep this PR open another two days or so to wait if any comments come up.

-v is certainly not optimal. I will consider better solutions in the future. For now I merge the PR so that we can finally switch to CMake.


F-Droid is a few versions behind again

Do they not automatically pick up new versions?

Yes, all of that is automatic and on their end. It normally takes a week, but sometimes more. In the past I opened an issue after a week and a half and they just recommended waiting. I can look into opening an issue in a few days if it doesn't appear by then.

And I do see that they built version 5.7.1, just haven't updated the store page yet

Ah, okay. I had an update to a different app that came out after your 5.7.x series, so I thought there was something stuck.
But I see the build now. I suspect they have to do signing with human interaction, so the store update takes a bit after the build sometimes.

Ah, okay. I had an update to a different app that came out after your 5.7.x series, so I thought there was something stuck.
But I see the build now. I suspect they have to do signing with human interaction, so the store update takes a bit after the build sometimes.

Just wanted to let you know that the F-Droid 5.7.1 version is finally available (5.7.2 was just released yesterday, so probably won't be in F-Droid for a bit) - not sure why that took so long (or why version 5.7.0 was skipped). There's a lot of behind the scenes stuff in F-Droid that isn't visible to developers unfortunately.

Oh, yes. I noticed and updated it already. I have been itching to try the AR stuff. It looks fantastic!

Thanks!


Failing test to show that valid? duplicates messages

Reform 2.0.1
I haven't run into this case with normal usage, but I thought it makes sense to report it anyway.
What happens is that calling valid? after validate({}) will duplicate errors message. Given already validated form
{:title=>["can't be blank"], :"band.label.name"=>["can't be blank"]}

calling validate? will do
{:title=>["can't be blank", "can't be blank"], :"band.label.name"=>["can't be blank"]}

the more times you call valid?, the more duplicated messages you get.

Ah, this is already reported in #241

#valid? is not public API, please don't use it. Reform tries to be semi-functional which means you have to use #validate when you want to validate. #thisaintrails

This isn't rails for sure, but even Lotus has valid? which is and will always be confusing. Any way to make valid? private at least?

Yeah we should make it private (I thought it was, already). The thing is, both AM and Lotus validations are one level deeper, they validate state (and AM does a lot of messed up shit to achieve that), but Reform::Form allows to change application state before validating the object graph.
In case you didn't know, Reform::Contract gives you #validate without accepting params, exposing the exact same semantics as #valid?.
You're right, we should care to make it private.

I'll close this PR then.
Thank you for the great stuff you do!

Thank you! :wink: You can open a PR that makes #valid? private in Lotus::Validations and ActiveModel::Validations (both modules in Reform). :+1:


MSC2437: Store tagged events in Room Account Data

Rendered

relates to Riot issues https://github.com/vector-im/riot-web/issues/2938 and https://github.com/vector-im/riot-web/issues/5649

Maybe it would make sense to extend the mechanism a little to be able to solve Personal ('pet name') room name for chats by allowing to tag the room name state event with a custom name, or even the membership events of other users to be able to rename them? :thinking:

@florianjacob I would prefer to not consider this point here. This should be handled by another proposal.

This MSC has been implemented on mobile sdk level (ios, android)
I would like to get it merged, but I'm concerned by the recent @kevincox comments on it.
@turt2live, what is the right labels to assign to it in order to get a final review and/or be able to merge it?
This MSC would be useful to manage https://github.com/vector-im/roadmap/issues/34

@giomfo the implementations need to be linked in the PR description please. From there it's a message in the SCT office for us to consider it for FCP.