[BUG] missing spaces in response with mlx-lm 0.19.1 and 0.19.2

Describe the bug
I have fine-tuned the meta-llama/Meta-Llama-3.1-8B-Instruct model in different variants with mlx-lm and Lora to generate Dart-Unit-Tests. The tuning of the models was done with different versions of mlx-lm (0.19.0, 0.19.1 and 0.19.2). I also used mlx-lm to fuse the adapters to the LLM again. Now I have noticed that during inference/generation with 0.19.1 and 0.19.2 spaces are missing in the generated import-statements  when they are followed by a ', for example: import'package:flutter/material.dart'; vs import 'package:flutter/material.dart';. Regardless of which version the model was fine-tuned with, if I downgrade to 0.19.0 the generation works correctly. In the training data the import are ok. Maybe a problem with tokenising?
For example
Generation-Response with 0.19.0
Here are the widget tests for the `ListTile`:

```dart
import 'package:flutter/material.dart';
import 'package:flutter_bloc/flutter_bloc.dart';
import 'package:flutter_test/flutter_test.dart';

Generation-Response with 0.19.1
Here are the tests for the `ListTile` class:

```dart
import'package:flutter/material.dart';
import'package:flutter_bloc/flutter_bloc.dart';
import'package:flutter_test/flutter_test.dart';

Generation-Response with 0.19.1
body:'body',
timestamp: DateTime.now(),

To Reproduce
code snippet used to genrate code
model_path = "results/llama3_1_8B_instruct_lora/tuning_09/lora_fused_model"
model, tokenizer = load(model_path)

generation_config = GenerationConfig.from_pretrained("meta-llama/Meta-Llama-3.1-8B-Instruct")
generation_args = {
    "temp": generation_config.temperature,
    "top_p": generation_config.top_p,
}

prompt_template = "Generate {test_type}s in Dart for the following {code_type}.\n" \
                  "### Path: {code_file_path}\n" \
                  "### Code:\n" \
                  "{code}\n" \
                  "### Test:\n"

def build_prompt(
        code: str,
        code_file_path: str,
        test_type: str,
        code_type: str
) -> str:
    prompt = prompt_template.format(
        test_type=test_type,
        code_type=code_type,
        code_file_path=code_file_path,
        code=code
    )
    messages = [{"role": "user", "content": prompt}]
    return tokenizer.apply_chat_template(
        messages, tokenize=False, add_generation_prompt=True
    )

def generate_test(code, code_file_path, code_type, test_type) -> tuple[str, str]:
    logging.info(f"Generating test for {os.path.basename(code_file_path)}")
    prompt =  build_prompt(
        code=code,
        code_file_path=code_file_path,
        code_type=code_type,
        test_type=test_type
    )
    print(prompt)

Expected behavior
No missing spaces before '.
Desktop (please complete the following information):

OS Version: [MacOS 15.0.1]
mlx-lm [0.19.1 und 0.19.2]
mlx [0.19.1]

That's a bug in the detokenization. Fix here: https://github.com/ml-explore/mlx-examples/pull/1072

Many thanks for the fix. That was quick. :)


envoy/lds: add comments for specific filter chain match criteria

Description:
Add more speficic comments for each field in the filter chain
match. The existing comment is incorrect with regards to
how the SNI is configured.

Affected area:

New Functionality      [ ]
Documentation          [ ]
Install                [ ]
Control Plane          [ ]
CLI Tool               [ ]
Certificate Management [ ]
Networking             [ ]
Metrics                [ ]
SMI Policy             [ ]
Security               [ ]
Tests                  [ ]
CI System              [ ]
Performance            [ ]
Other                  [X]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? If so, did you notify the maintainers and provide attribution?
No

Codecov Report

Merging #2071 (a51f3cc) into main (d52ed3f) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main    #2071   +/-   ##
=======================================
  Coverage   57.80%   57.80%
=======================================
  Files         140      140
  Lines        5780     5780
=======================================
  Hits         3341     3341
  Misses       2437     2437
  Partials        2        2

Impacted Files
Coverage Δ

pkg/envoy/lds/inmesh.go
86.20% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d52ed3f...a51f3cc. Read the comment docs.


"video_player" does not support 'video/avc' format

PlatformException(VideoError, Video player had error com.google.android.exoplayer2.ExoPlaybackException: MediaCodecVideoRenderer error, index=0, format=Format(2, null, null, video/avc, avc1.6E000D, 1240800, null, [202, 360, -1.0], [-1, -1]), format_supported=NO_EXCEEDS_CAPABILITIES, null, null)
Forexample: https://video.591.com.tw/online/target/house/hls/2023-12-14/616865/master.m3u8

Please see https://pub.dev/packages/video_player#supported-formats
Closing as the plugin does not control the supported formats.


Fixing alter table multi partition

Fixes examples like this:
ALTER TABLE `database`.`table` ADD IF NOT EXISTS PARTITION (`hour` = '2020-12-24T17') PARTITION (`hour` = '2020-12-24T18') PARTITION (`hour` = '2020-12-24T19')

This includes the backtick commit by necessity but we can merge them all at once or the backtick commit separately, your choice.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

26 of 26 (100.0%)  changed or added relevant lines in 4 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.02%) to 85.652%

Files with Coverage Reduction
New Missed Lines
%

src/parser.rs
2
83.15%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
10286

Relevant Lines:
12009

💛  - Coveralls

Buhhhh forgot to cargo fmt again, force-pushed an amended commit for this.

@bitemyapp please add information about sources and references. Only putting the query there makes me search for 5 dialects at least before making sure that's valid

Removed #[must_use] from the peek helper I wrote and lifted the backtick acceptance out of the trait default to GenericDialect. Tests still passed.

I'll wait for the token parsing thing to merge and we can then merge this one

CI is failing so marking as draft

Closing this PR as it is more than 6 months old without activity. Please reopen or make another PR if you plan to keep working on this.


Add support for upptime/uptime-monitor#221

This PR is for adding support for upptime/uptime-monitor#221
As with the other PR do I have no real experience with svelte here... So if what I did is wrong let me know with the right solution. Thanks.

.

I give up....
The fact that even PRs get marked as stale is so BS to have.
I won't react to the next stale notice.
Hopefully there won't be any, but I doubt this in all honesty...

I'm sorry you feel this way, but I don't understand, this is a draft PR, right? So there's nothing actionable by me... or is it ready for review and it's on me?

I left it as a PR as I first wanted feedback on if this is a good aproach on adding what I suggested in https://github.com/upptime/upptime/discussions/569 and https://github.com/upptime/upptime/discussions/572
I can turn it into a normal PR. Tho, I can't tell if either this or https://github.com/upptime/uptime-monitor/pull/221 would need to be implemented first... Don't know the exact dependency relations between these two.


feat(modeling): rework math objects to conform with gl-matrix

WORK IN PROGRESS!  DO NOT MERGE!!!
BIG CHANGES!
These changes adjust the math objects to the same API as gl-matrix. This should have the following affects

improved performance as API signatures are now fixed (no more ...params)
improved performance in the use of math objects (less allocations)
improved interoperability with gl-matrix (no need to learn a different API)

All Submissions:

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Does your submission pass tests?

Here are the first set of performance statistics for these changes. Very nice!
For those following, take a look at intersection, subtract, and union performance.
JSCADPerformance20310427.pdf
There does seem to be a regression in measureVolume(). :(

There does seem to be a regression in measureVolume(). :(

Hmm... Why 10000 test is faster than 100000 test as well? Strangeness.
Relatively speaking in TIME, measureVolume() is still very fast.

Scanned through as best as I could. Changes look reasonable and well considered. Nice!

Yeah. It's a big set of changes. Thanks.
I'm still running performance tests as there were some issues with the extrusions. I should have some nice statistics at this end of this week.


[improvement](jdbc catalog) Added create jdbc catalog properties validation

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 46.96 seconds
stream load tsv:          538 seconds loaded<PHONE_NUMBER>9 Bytes, about 132 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          64 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
insert into select:          29.0 seconds inserted 10000000 Rows, about 344K ops/s
storage size:<PHONE_NUMBER>2 Bytes

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 47.89 seconds
stream load tsv:          536 seconds loaded<PHONE_NUMBER>9 Bytes, about 133 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          28.6 seconds inserted 10000000 Rows, about 349K ops/s
storage size:<PHONE_NUMBER>4 Bytes

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 48.02 seconds
stream load tsv:          530 seconds loaded<PHONE_NUMBER>9 Bytes, about 134 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          64 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          28.8 seconds inserted 10000000 Rows, about 347K ops/s
storage size:<PHONE_NUMBER>0 Bytes

run p1

run buildall

run buildall

run buildall

run buildall

run clickbench


doc: add the document to introduce the config-nacos

What type of PR is this?

doc
Check the PR title.

[x] This PR title match the format: <type>(optional scope): <description>
[x] The description of this PR title is user-oriented and clear enough for others to understand.

(Optional) Translate the PR title into Chinese.
(Optional) More detailed description for this PR(en: English/zh: Chinese).

en:
zh(optional):
(Optional) Which issue(s) this PR fixes:

cc @cqqqq777  @ViolaPioggia

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: whalecold:x: 郑力升郑力升 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


wip - implementing primary key support,

[x] Adding fetch_data to Store trait
[x] Expanding ast::IndexItem
[x] Execution layer - select
[x] Execution layer - insert
[ ] Query planner
[ ] Integration tests

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

101 of 135 (74.81%)  changed or added relevant lines in 10 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.07%) to 97.731%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

storages/sled-storage/src/store.rs
0
3
0.0%

core/src/executor/execute.rs
51
55
92.73%

storages/shared-memory-storage/src/lib.rs
0
5
0.0%

storages/memory-storage/src/lib.rs
0
8
0.0%

core/src/executor/fetch.rs
8
22
36.36%

Files with Coverage Reduction
New Missed Lines
%

core/src/executor/fetch.rs
1
84.25%

Totals

Change from base Build<PHONE_NUMBER>:
-0.07%

Covered Lines:
28947

Relevant Lines:
29619

💛  - Coveralls


Question about UIBindingObserver

Hello, I'm curious why are u use Dispatch.main in UIBindingObserver? Trying to implement something close to RxDataSources for internal usage, so maybe I should adopt your experience :)

Hi @haritowa ,
we had issues with UITableView animations and their state getting out of sync. I think there were some internal UI{Table, Collection}View issues. Collection view is by far the worst.
It was some time ago :)

Ok, thanks for explanation :)


Add Content Type, Content Modifiers, Ratings pages

CT, CM, Ratings pages added, closes #29
Other minor changes:

Updated sample code CSS for metadata fields on other pages
Reordered Territory columns for metadata
Table headers v-aligned top

@palemieux all comments should not be resolved, also updated the "code" color site wide in 916e9f3


Add silent conda upgrade to Dockerfile

It also needs to be added to the work/Makefile refresh target.  There's a conda call in the Makefile, but it requires user attention; temporary implementation until this ticket is solved.

Actually - this needs to be thought at a wider level.  We CANNOT assume that Conda/Anaconda is installed, because it doesn't exist in bare metal, only in the mini lab.  We need to find out all the dependencies for running the covidvu.predict module in a standard Python 3.7+ virtual environment, without Conda.  Assigned to @jaryaman

This is related to #348. Upon running covidvu.predict in the minilab, we get the warning
WARNING (theano.configdefaults): install mkl with `conda install mkl-service`: No module named 'mkl'

The purpose of mkl is for multi-threading of multiple MCMC chains. I presume it works when mkl isn't installed because it just defaults to 1 thread?
I was going to try and simply run conda install mkl-service in the mini-lab and add it to Dockerfile to resolve #348, but now I am not so sure.

@jaryaman - Thanks!  See if you can shake this bear and report, it's not an urgent matter.  The heavy lifting will happen when I go to the server and run mkl and theano on the metal.

Would you @pr3d4t0r know why Unbuntu is having GPG issues with their apt repo? I've tried apt-get clear and also moving the cache mv /var/lib/apt/lists /tmp and still getting:
W: GPG error: http://security.ubuntu.com/ubuntu bionic-security InRelease: At least one invalid signature was encountered. E: The repository 'http://security.ubuntu.com/ubuntu bionic-security InRelease' is not signed.

@dlwhitehurst - I'm not sure about what you're doing.  Try:
make image
From the top-level directory (NOT from ./work) and that should build the image.
I invited you to our Schlack channel a few minutes ago.

I'll try the above. Running apt-key update does a check and tells me that GPG might not be installed "in your lab image?" Not sure yet.
[~/Development/Python/covidvu-help]$ docker build --tag dlwhitehurst/covidvu:1.0 . Sending build context to Docker daemon  5.632kB [WARNING]: Empty continuation line found in:     RUN             apt-key update  && COPY            resources/_bash_profile /root/.bash_profile [WARNING]: Empty continuation lines will become errors in a future release. Step 1/8 : FROM            jupyter/datascience-notebook:latest  ---> ce97927bafa2 Step 2/8 : MAINTAINER<EMAIL_ADDRESS>---> Using cache  ---> b4f50694ec32 Step 3/8 : USER            root  ---> Using cache  ---> 0621eb3626a4 Step 4/8 : RUN             apt-key update  && COPY            resources/_bash_profile /root/.bash_profile  ---> Running in ec41cbb98396 E: gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them is required for this operation The command '/bin/sh -c apt-key update  && COPY            resources/_bash_profile /root/.bash_profile' returned a non-zero code: 255

Weird - not sure.

Let's continue this on Slack -- the issue that started this was Theona compatibility with the server (it's been deprecated) and we want to avoid Conda altogether.  We found other Jupyter issues.  Swing by Slack when you have a minute.  I'm very curious about why your environment doesn't build.

Added conda install of mkl only and upgrade of conda itself. Continued with pip installs. See PR https://github.com/VirusTrack/COVIDvu/pull/368


Profile's<EMAIL_ADDRESS>Squad" Links cause errors and disconnections on users without squads i.e razor / plt staff

Describe the bug
Using the<EMAIL_ADDRESS>Squad" links on a user's profile for users who do not have valid squads i.e platoon staff or razor causes an error and a database disconnection.
[2021-10-04T13:05:34.902Z] Error: There was an unhandled exception on the current circuit,
so this circuit will be terminated. For more details turn on detailed exceptions by setting
'DetailedErrors: true' in 'appSettings.Development.json' or set 'CircuitOptions.DetailedErrors'.

To Reproduce
Steps to reproduce the behavior:

Go to https://dc.501stlegion-a3.com/trooper/34554
Click on "Hobnob's Squad" / Platoon / Company
See error

Doesn't apply to just razor, also applies to platoon staff positions i.e Cyclone 3 Romeo:
https://dc.501stlegion-a3.com/trooper/29941
Expected behavior
Either the razor sections / flights / squadron should be displayed when selecting squad / platoon / company (cosmetic side note, a check here for the detachment to use the correct terms would be nice)
Or the links should only be displayed when they're valid.
Screenshots

Platform
Google Chrome

@jdoxley should be a simple fix to not display the squad/platoon/company pages if they do not have one so I'm assigning this to you. Also - displaying sections/flights for razor and mynock would be appreciated.


Escape quotation marks inside strings

Fix #26.

Very nice, thank you for the fix and the test case! Looks good to me.


Why discoveryClient.getInstance('service-with-kubernetes-service') returns empty ?

deployment.yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  namespace: default
  name: namespace-reader
rules:
  - apiGroups: ["", "extensions", "apps"]
    resources: ["configmaps", "pods", "services", "endpoints", "secrets"]
    verbs: ["get", "list", "watch"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: namespace-reader-binding
  namespace: default
subjects:
  - kind: ServiceAccount
    name: default
    apiGroup: ""
roleRef:
  kind: Role
  name: namespace-reader
  apiGroup: ""
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: service-with-kubernetes-config
data:
  math_max: "10"
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: provider-service-with-kubernetes-config
data:
  application.yml: |-
    math:
      max: 10000
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: service-with-kubernetes-deployment
spec:
  selector:
    matchLabels:
      name: service-with-kubernetes
  template:
    metadata:
      labels:
        name: service-with-kubernetes
    spec:
      containers:
        - name: service-with-kubernetes
          image: lionchi/service-with-kubernetes:latest
          ports:
            - containerPort: 8080
          env:
            - name: MATH_MAX
              valueFrom:
                configMapKeyRef:
                  name: service-with-kubernetes-config
                  key: math_max
          livenessProbe:
            httpGet:
              port: 8080
              path: /actuator/health/liveness
          readinessProbe:
            httpGet:
              port: 8080
              path: /actuator/health/readiness
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: discovery-service-with-kubernetes-deployment
spec:
  selector:
    matchLabels:
      name: discovery-service-with-kubernetes
  template:
    metadata:
      labels:
        name: discovery-service-with-kubernetes
    spec:
      containers:
        - name: discovery-service-with-kubernetes
          image: lionchi/discovery-service-with-kubernetes:latest
          ports:
            - containerPort: 9090
          livenessProbe:
            httpGet:
              port: 9090
              path: /actuator/health/liveness
          readinessProbe:
            httpGet:
              port: 9090
              path: /actuator/health/readiness
---
apiVersion: autoscaling/v2beta1
kind: HorizontalPodAutoscaler
metadata:
  name: service-with-kubernetes-autoscaling
spec:
  scaleTargetRef:
    apiVersion: apps/v2beta1v1
    kind: Deployment
    name: service-with-kubernetes-deployment
  minReplicas: 1
  maxReplicas: 2
  metrics:
    - type: Resource
      resource:
        name: cpu
        targetAverageUtilization: 70
    - type: Resource
      resource:
        name: memory
        targetAverageUtilization: 80
---
apiVersion: autoscaling/v2beta1
kind: HorizontalPodAutoscaler
metadata:
  name: discovery-service-with-kubernetes-deployment
spec:
  scaleTargetRef:
    apiVersion: apps/v2beta1v1
    kind: Deployment
    name: service-with-kubernetes-deployment
  minReplicas: 1
  maxReplicas: 2
  metrics:
    - type: Resource
      resource:
        name: cpu
        targetAverageUtilization: 70
    - type: Resource
      resource:
        name: memory
        targetAverageUtilization: 80
---
apiVersion: v1
kind: Service
metadata:
  name: service-with-kubernetes-service
spec:
  selector:
    project: service-with-kubernetes
  ports:
    - name: service-with-kubernetes-listener
      protocol: TCP
      port: 8080
      targetPort: 8080
  type: NodePort
---
apiVersion: v1
kind: Service
metadata:
  name: discovery-service-with-kubernetes-service
spec:
  selector:
    project: discovery-service-with-kubernetes
  ports:
    - name: discvovery-service-with-kubernetes-listener
      protocol: TCP
      port: 9090
      targetPort: 9090
  type: NodePort

code from service
@GetMapping(value = "/getInfo/{nameService}")
    public List<ServiceInstanceDto> getInfoInstances(@PathVariable String nameService) {
        return discoveryClient.getInstances(nameService).stream()
                .map(serviceInstance -> new ServiceInstanceDto(serviceInstance.getServiceId(), serviceInstance.getHost(), serviceInstance.getPort(), serviceInstance.getUri().toString()))
                .collect(Collectors.toList());
    }

pom.xml
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <parent>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-parent</artifactId>
        <version>2.6.3</version>
        <relativePath/> <!-- lookup parent from repository -->
    </parent>
    <groupId>ru.jpixel</groupId>
    <artifactId>discovery-service-with-kubernetes</artifactId>
    <version>0.0.1-SNAPSHOT</version>
    <name>discovery-service-with-kubernetes</name>
    <description>discovery-service-with-kubernetes</description>
    <properties>
        <java.version>17</java.version>
        <org.springframework.kubernetes>2.1.0</org.springframework.kubernetes>
    </properties>
    <dependencies>
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-web</artifactId>
        </dependency>

        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-devtools</artifactId>
            <scope>runtime</scope>
            <optional>true</optional>
        </dependency>
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-actuator</artifactId>
        </dependency>
        <dependency>
            <groupId>org.projectlombok</groupId>
            <artifactId>lombok</artifactId>
            <optional>true</optional>
        </dependency>
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-test</artifactId>
            <scope>test</scope>
        </dependency>

        <dependency>
            <groupId>org.springframework.cloud</groupId>
            <artifactId>spring-cloud-starter-kubernetes-client</artifactId>
            <version>${org.springframework.kubernetes}</version>
        </dependency>
    </dependencies>

    <build>
        <plugins>
            <plugin>
                <groupId>org.springframework.boot</groupId>
                <artifactId>spring-boot-maven-plugin</artifactId>
                <configuration>
                    <excludes>
                        <exclude>
                            <groupId>org.projectlombok</groupId>
                            <artifactId>lombok</artifactId>
                        </exclude>
                    </excludes>
                </configuration>
            </plugin>
        </plugins>
    </build>

</project>

Impossible to tell with the information provided

Impossible to tell with the information provided

What else do you need ? Here is the repository with the project https://github.com/lionchi/discovery-service-with-kubernetes

Where are you defining a service named service-with-kubernetes?

Where are you defining a kubernetes service named service-with-kubernetes?

I apologize for the incorrect name of the service kubernetes specified. Here on this service service-with-kubernetes-service I am trying to get information using discovery clietn

Where are you defining a kubernetes service named service-with-kubernetes?

also, when I try to reach the service by its name (the getUserAll method), then I have a connection timeout
@RestController
@RequestMapping("/api/v1/web/services")
@RequiredArgsConstructor
public class DiscoveryServiceController {

    private final RestTemplate restTemplate;
    private final DiscoveryClient discoveryClient;

    @GetMapping(value = "/getAll")
    public List<String> getAll() {
        return discoveryClient.getServices();
    }

    @GetMapping(value = "/getInfo/{nameService}")
    public List<ServiceInstanceDto> getInfoInstances(@PathVariable String nameService) {
        return discoveryClient.getInstances(nameService).stream()
                .map(serviceInstance -> new ServiceInstanceDto(serviceInstance.getServiceId(), serviceInstance.getHost(), serviceInstance.getPort(), serviceInstance.getUri().toString()))
                .collect(Collectors.toList());
    }

    @GetMapping(value = "/getUserAll/{nameService}")
    public List<UserDto> getUserAll(@PathVariable String nameService) {
        try {
            var restTemplateForObject = restTemplate.getForObject("http://" + nameService + "/api/v1/web/users/getAll", UserDto[].class);
            return Arrays.stream(restTemplateForObject != null ? restTemplateForObject : new UserDto[0]).toList();
        } catch (Exception e) {
            return Collections.emptyList();
        }
    }
}

Your selector in your services are wrong there are no pods with the labels project: discovery-service-with-kubernetes or name: service-with-kubernetes-service.

Your selector in your services are wrong there are no pods with the labels project: discovery-service-with-kubernetes or name: service-with-kubernetes-service.

Something I didn't quite understand what needs to be done. Can I have an example of some kind ?  I have for the service service-with-kubernetes-service which in the selector refers to project: service-with-kubernetes. And the discovery-service-with-kubernetes-service refers to project: discovery-service-with-kubernetes. And in my application, I'm trying to draw it by the names of the services in kubernetes service service-with-kubernetes-service and discovery-service-with-kubernetes-service. Both discoveryClient.getInstance(service-with-kubernetes-service) and discoveryClient.getInstance(discovery-service-with-kubernetes-service) return a void. Although if you request discoveryClient.GetServices() then it will output their name

Its not a problem with the service name its a problem with the service selector labels.  We can find the services, hence why getServices returns the correct list.  However your service selector label does not match any pods so we can't get any information about the pods associated with that service.  If you change your service definitions to this, everything should work
apiVersion: v1
kind: Service
metadata:
  name: service-with-kubernetes-service
spec:
  selector:
    name: service-with-kubernetes
  ports:
    - name: service-with-kubernetes-listener
      protocol: TCP
      port: 8080
      targetPort: 8080
  type: NodePort
---
apiVersion: v1
kind: Service
metadata:
  name: discovery-service-with-kubernetes-service
spec:
  selector:
    name: discovery-service-with-kubernetes
  ports:
    - name: discvovery-service-with-kubernetes-listener
      protocol: TCP
      port: 9090
      targetPort: 9090
  type: NodePort

Its not a problem with the service name its a problem with the service selector labels. We can find the services, hence why getServices returns the correct list. However your service selector label does not match any pods so we can't get any information about the pods associated with that service. If you change your service definitions to this, everything should work
apiVersion: v1
kind: Service
metadata:
  name: service-with-kubernetes-service
spec:
  selector:
    name: service-with-kubernetes
  ports:
    - name: service-with-kubernetes-listener
      protocol: TCP
      port: 8080
      targetPort: 8080
  type: NodePort
---
apiVersion: v1
kind: Service
metadata:
  name: discovery-service-with-kubernetes-service
spec:
  selector:
    name: discovery-service-with-kubernetes
  ports:
    - name: discvovery-service-with-kubernetes-listener
      protocol: TCP
      port: 9090
      targetPort: 9090
  type: NodePort

Yes, it really worked. It turns out it was the wrong selector for the pod. Thank you very much for your help


Fixed hamburger menu ,colour, search icon, greeting phrase

Related Issue
Issue : fix the hamburger menu
Fixes : #9
https://github.com/user-attachments/assets/92324e28-4263-4ffe-95cc-ab1613950b66
Description of Changes
Changed the colour of the menu button , enhanced the animation of the menu button.
Fixed the bottom of the hamburger menu , adjusted its size by blocking its overflow.
Positioned the greeting phrase in the center to look good.
Moved the search button to the right with some padding which looks good on different screen sizes.
No fixed the top because the search icon would have hidden due to that.
https://github.com/user-attachments/assets/35b7ea32-c05c-4464-aba4-4506e614cb21
Type of Pull Request

[* ] Performance Improvement

Checklist for Contributor
use'X' in [ ] to check it .

[* ] I have reviewed my code before submission.
[* ] I have read and followed the project's Contribution Guidelines.
[* ] I have tested the code thoroughly.
[* ] I have attached related issue numbers, screenshots, or videos (if applicable).
[* ] I have checked the existing code base and my changes do not introduce any breaking changes.
[ *] My PR addresses only one issue; I have created separate PRs for other issues.
[* ] I have ensured that the PR does not include unrelated files.
[* ] I am mindful of the project's coding standards and best practices.

Sorry forget to remove the previous overflow line , wait a minute

Perfect to go now @1-SubhamSingh good job

Thanks for the PR and also for updating the label to level 2 :))


Throwing redirect in beforeLoad still renders component

Which project does this relate to?
Router
Describe the bug
This could be similar to #2819, but the behaviour I am observing is slightly different:
export const Route = createFileRoute('/some-path')({
  beforeLoad: async () => {
    if (2 + 2 === 4) {
      console.log('throwing')
      throw redirect({
        to: '/some-other-path',
      })
    }
  },
  component: () => {
    console.log('component is running')

    return <Outlet />
  },
})

If I hit this URL, I see this in the console:
throwing
component is running

Apologies if I've misunderstood the purpose of beforeLoad, but isn't this as straightforward a bug as there could be?
EDIT: This is related to #2818. If I set TanStackRouterVite.autoCodeSplitting to false, the bug no longer occurs.
Your Example Website or App
http://example.com
Steps to Reproduce the Bug or Issue
export const Route = createFileRoute('/some-path')({
  beforeLoad: async () => {
    if (2 + 2 === 4) {
      console.log('throwing')
      throw redirect({
        to: '/some-other-path',
      })
    }
  },
  component: () => {
    console.log('component is running')

    return <Outlet />
  },
})

Expected behavior
Component should not be run.
Screenshots or Videos
No response
Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]

Additional context
No response

I've provided the minimal repro via a code snippet, and further follow-up investigation. I have isolated the problem for you.
I will gladly close this issue. You can deal with the next user to report it, and they can jump through your hoops.


difference between the trained model "contrastive" and "non-contrastive"

Hi, thanks for your outstanding work.
I found that there are two trained model, what is the difference between them?

Hello. "Contrastive" refers to the model trained using the mixed augmentation technique described in section 4.1 of the paper. This is the one you should use if you want to replicate our paper.


Add utility class SortBuffer

SortBuffer is a utility class to accumulate data inside and output the sorted result.
Spilling would be triggered if spilling is enabled and memory usage exceeds limit.

Reference PR: https://github.com/facebookincubator/velox/pull/2259

@xiaoxmeng thanks for the review, addressed some of the comments, haven't finished the test yet, want to confirm, the test regarding reclaim memory would be still in OrderBy test instead of SortBuffer test, is that correct?


Configure and use local NTP server

Since this cluster is meant to run standalone, and the Pi doesn't have an RTC, I've ordered an RTC that I can stick onto one of the Pis, then set up the Pi as an NTP server.
I'll need to configure all the other Pis to use the master Pi as the NTP server, then have the master Pi update it's time periodically if connected to the Internet.
Should hopefully not be too difficult to set up; I can probably do most of it with the geerlingguy.ntp role, and here's a guide to help as well: Use local NTP server with Raspberry Pi.

Just an FYI; the `geerlingguy.ntp


ImportError: cannot import name 'field_validator' from 'pydantic'

Tested with the latest jetson-containers as of today (04-22) and ran into a Python import error with pydantic.
Error
oot@jao-gtc24-jp6dp:/data/RAG_based_on_Jetson# python3 main.py
Traceback (most recent call last):
  File "/data/RAG_based_on_Jetson/main.py", line 1, in <module>
    from mlc_chat import ChatModule
  File "/usr/local/lib/python3.10/dist-packages/mlc_chat/__init__.py", line 5, in <module>
    from . import protocol, serve
  File "/usr/local/lib/python3.10/dist-packages/mlc_chat/protocol/__init__.py", line 2, in <module>
    from . import openai_api_protocol
  File "/usr/local/lib/python3.10/dist-packages/mlc_chat/protocol/openai_api_protocol.py", line 11, in <module>
    from pydantic import BaseModel, Field, field_validator, model_validator
ImportError: cannot import name 'field_validator' from 'pydantic' (/usr/local/lib/python3.10/dist-packages/pydantic/__init__.py)
root@jao-gtc24-jp6dp:/data/RAG_based_on_Jetson#

Steps to reproduce
git clone --depth=1 https://github.com/dusty-nv/jetson-containers jetson-containers_ss
cd jetson-containers_ss
git checkout e8c3cb53b2c6c02c20903f68020d20a92f66cc4f

And follow the steps as is on the README.

I have update my mian.py now you can use it.


Dashboard updates

Update dashboards using registry.redhat.io/rhel8/grafana:7 and remove
any events or alarms from the panels.

I have a bit more work to do here, but opening this up for a quick conversation to make sure I don't spend too much time doing something dumb :)
Two main bits here:

remove reference to event stuff
export this from RHEL grafana 7 to try and get us more aligned to a supported workload artifact

As part of the re-export (which seems to have not been done in a really long time), one of the plugins (which provides the hex pattern layout of the virtual machines) is updated from a very old version. I was having some issues with it not loading, which seems to have been resolved by the version bump. Might not have been related issues, but getting to something more recent is probably a good thing.
I will re-test all of this to make sure it works with the default image as well (from docker in the grafana org), but the changes look to be so minor that a newer grafana should be able to support this as well.

I was initially confused by your comment about "a very old version" since I see all the version numbers going down from "8.0.6" to "7.5.15", but then I looked closer and found the "6.5.1" references. I thought this is ironic because IIRC, Perses is closer to compatibility with Grafana 6. in general this seems to be moving in the right direction, though, doesn't seem dumb.

oc get stf default -oyaml
apiVersion: infra.watch/v1beta1
kind: ServiceTelemetry
metadata:
  creationTimestamp: "2023-10-24T14:56:28Z"
  generation: 3
  name: default
  namespace: service-telemetry
  resourceVersion: "81961037"
  uid: 81945638-cd86-495b-ae69-585a2786a78f
spec:
  alerting:
    alertmanager:
      storage:
        persistent:
          pvcStorageRequest: 20G
        strategy: persistent
    enabled: true
  backends:
    metrics:
      prometheus:
        enabled: true
        scrapeInterval: 10s
        storage:
          persistent:
            pvcStorageRequest: 20G
          retention: 24h
          strategy: persistent
  clouds:
  - metrics:
      collectors:
      - bridge:
          ringBufferCount: 15000
          ringBufferSize: 16384
          verbose: false
        collectorType: collectd
        debugEnabled: false
        subscriptionAddress: collectd/cloud1-telemetry
      - bridge:
          ringBufferCount: 15000
          ringBufferSize: 16384
          verbose: false
        collectorType: ceilometer
        debugEnabled: false
        subscriptionAddress: anycast/ceilometer/cloud1-metering.sample
      - bridge:
          ringBufferCount: 15000
          ringBufferSize: 65535
          verbose: false
        collectorType: sensubility
        debugEnabled: false
        subscriptionAddress: sensubility/cloud1-telemetry
    name: cloud1
  graphing:
    enabled: true
    grafana:
      baseImage: registry.redhat.io/rhel8/grafana:7
      ingressEnabled: true
  observabilityStrategy: use_redhat
  transports:
    qdr:
      auth: none
      certificates:
        caCertDuration: 70080h
        endpointCertDuration: 70080h
      enabled: true
      web:
        enabled: false

oc get pods
NAME                                                        READY   STATUS    RESTARTS        AGE
alertmanager-default-0                                      3/3     Running   0               28h
cert-manager-operator-controller-manager-54f7679467-46pjj   2/2     Running   0               29h
default-cloud1-ceil-meter-smartgateway-7dfb95fcb6-bs6jl     3/3     Running   2 (4h22m ago)   28h
default-cloud1-coll-meter-smartgateway-674d88d8fc-858jk     3/3     Running   2 (4h22m ago)   28h
default-cloud1-sens-meter-smartgateway-9b869695d-xcssf      3/3     Running   1 (4h22m ago)   28h
default-interconnect-7cc45b86c5-lpljv                       1/1     Running   0               4h22m
grafana-deployment-54c54fddd7-grvx2                         2/2     Running   0               4h3m
grafana-operator-controller-manager-854d84f945-qz5tw        2/2     Running   0               6h27m
interconnect-operator-7bb99c5ff4-l6xc2                      1/1     Running   0               29h
prometheus-default-0                                        3/3     Running   0               28h
service-telemetry-operator-687b977879-ntfcn                 1/1     Running   0               20h
smart-gateway-operator-7d557cb7b7-9ppls                     1/1     Running   0               29h


Adding the [version]$osImageSkuVersion = (date -Format yyyy.MM.dd).ToString()

this parameter set´an OS Image SKU Version to be different from the hardcoded 1.0.0
it is included in Pull request https://github.com/Azure/AzureStack-Tools/pull/427
Please review the changes. ALso included latest os patch

The corresponding PR was merged, closing issue. Thanks.


replace relative paths to data dir in notebooks

currently in all of our ipython notebooks the data files are referenced by a simple ../../../data/<filename> relative path, like for example this:
shogun_feats_linear = RealFeatures(CSVFile('../../../data/toy/classifier_binary_2d_linear_features_train.dat'))

this is causing a lot of trouble if you copy the notebook somewhere else.
in this entrance task, one should replace all these relative paths with an environment variable called SHOGUN_DATA_DIR, which then would have a default value if it's not set.
the fix should be applied to almost every ipython notebook here: https://github.com/shogun-toolbox/shogun/tree/develop/doc/ipython-notebooks

Hi! Can I take up this issue?

No need to ask :)

so the ../../../data should be replaced by an os.getenv call right?

@vigsterkr Is this what you had in mind?
https://github.com/deveshnag1/shogun/blob/notebook_relative/doc/ipython-notebooks/classification/Classification.ipynb

@deveshnag1 mmm in a way yes but as you can see in the meanwhile this has been addressed by somebody else in the https://github.com/shogun-toolbox/shogun/pull/3753 pr

fixed in #3753


How do i use angular 2 in spring mvc

Note: for support questions, please use one of these channels: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#question. This repository's issues are reserved for feature requests and bug reports.
Do you want to request a feature or report a bug?
What is the current behavior?
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://plnkr.co or similar (template: http://plnkr.co/edit/tpl:yBpEi4).
What is the expected behavior?
What is the motivation / use case for changing the behavior?
Which versions of Angular, and which browser / OS are affected by this issue? Did this work in previous versions of Angular? Please also test with the latest stable and snapshot (https://code.angularjs.org/snapshot/) versions.
Other information (e.g. stacktraces, related issues, suggestions how to fix)

This repo is for angular 1. Angular 2 is at https://github.com/angular/angular.
But yours sounds like a support question, so you should try asking on one of ng2's support channels.


Internal error when entering ARAM

Hi guys, I just downloaded the app. I haven't been able to make it run at all.
Logs:
[Renderer] [log] [20:12:48] [ChampionSelectHandler] Entering
[Renderer] [log] [20:12:48] [ChampionSelectHandler] Entering into ARAM
[Renderer] [log] [20:12:49] [ChampionSelectHandler] Champion changed to: Cassiopeia
[Renderer] [log] [20:12:49] [ProviderHandler] Downloading data for Cassiopeia
[Renderer] [log] [20:12:49] [ProviderHandler] Using providers:  LoLFlavor
[Renderer] [log] [20:12:49] [ProviderHandler] Using LoLFlavor
[Renderer] [log] [20:12:49] [GameAssetsProxy] https://riot:MwuIJXFBi7ycHjDSD-A8iQ@<IP_ADDRESS>:62507/lol-game-data/assets/v1/champion-icons/69.png
[Renderer] [log] [20:12:50] [ProviderHandler] Couldn't aggregate data.
[Renderer] [error] [20:12:50]
TypeError: Cannot read property '2' of undefined
[Renderer] [error] [20:12:50]
The gathered data is empty. This is an error that shouldn't happen. Manaflux can't recover from it. You should restart the app.
[Renderer] [log] [20:13:02] Flu.x >> Upload error
[Renderer] [error] [20:13:02]
StatusCodeError: 503 - "<!DOCTYPE html>\n\t\n\t  \n\t\t<meta name=\"viewport\" content=\"width=device-width, initial-scale=1\">\n\t\t<meta charset=\"utf-8\">\n\t\t<title>Application Error</title>\n\t\t\n\t  \n\t  \n\t\t\n\t  \n\t"
[Renderer] [log] [20:13:02] [DataValidator] Copying required properties for Flu.x
[Renderer] [dir] [20:13:02]
{"roles":{"JUNGLE":{"perks":[{"suffixName":"(HW%)","selectedPerkIds":[8465,8463,8473,8453,8321,8347,5007,5003,5002],"primaryStyleId":8400,"subStyleId":8300,"provider":"championgg"},{"suffixName":"(MF)","selectedPerkIds":[8465,8463,8473,8453,8321,8347,5007,5003,5001],"primaryStyleId":8400,"subStyleId":8300,"provider":"championgg"},{"selectedPerkIds":[8214,8224,8210,8232,8321,8347,5008,5008,5001],"primaryStyleId":8200,"subStyleId":8300,"provider":"opgg"},{"selectedPerkIds":[8214,8224,8210,8232,8321,8347,5008,5008,5001],"primaryStyleId":8200,"subStyleId":8300,"provider":"opgg"}],"summonerspells":[],"itemsets":[{"title":"CGG1 Ivern > Jungle","type":"custom","map":"any","mode":"any","blocks":[{"type":"Starter (Most Frequent) | 51.65% WR","_type":{"i18n":"providers-cgg-blocks-starters-mf","arguments":["51.65%"]},"recMath":false,"items":[{"id":"1039","count":1},{"id":"2031","count":1}]},{"type":"Starter (HW%) | 52.31% WR","_type":{"i18n":"providers-cgg-blocks-starters-hw%","arguments":["52.31%"]},"recMath":false,"items":[{"id":"1039","count":1},{"id":"2003","count":1},{"id":"2055","count":1}]},{"type":"Trinkets","_type":{"i18n":"item-sets-block-trinkets"},"recMath":false,"items":[{"id":"2055","count":1},{"id":"3340","count":1},{"id":"3341","count":1},{"id":"3348","count":1},{"id":"3363","count":1}]},{"type":"Completed build (Most Frequent) | 45.38% WR","_type":{"i18n":"providers-cgg-blocks-completed-build-mf","arguments":["45.38%"]},"recMath":false,"items":[{"id":"3107","count":1},{"id":"3109","count":1},{"id":"3117","count":1},{"id":"3174","count":1},{"id":"3190","count":1},{"id":"3504","count":1}]},{"type":"Completed build (HW%) | 50.00% WR","_type":{"i18n":"providers-cgg-blocks-completed-build-hw%","arguments":["50.00%"]},"recMath":false,"items":[{"id":"3107","count":1},{"id":"3109","count":1},{"id":"3117","count":1},{"id":"3174","count":1},{"id":"3190","count":1},{"id":"3504","count":1}]},{"type":"Consumables | Skill Order: Q => W => E","_type":{"i18n":"item-sets-block-consumables-skill-order","arguments":["Q => W => E"]},"recMath":false,"items":[{"id":"2003","count":1},{"id":"2138","count":1},{"id":"2139","count":1},{"id":"2140","count":1}]}],"priority":true,"provider":"championgg"},{"title":"OPG1 Ivern > Jungle","type":"custom","map":"any","mode":"any","blocks":[{"type":"Starter 1 | Skill Order: E => Q => W","_type":{"i18n":"item-sets-block-starter-skill-order-numbered","arguments":[1,"E => Q => W"]},"recMath":false,"items":[{"id":"1039","count":1},{"id":"2031","count":1}]},{"type":"Starter 2 | Skill Order: E => Q => W","_type":{"i18n":"item-sets-block-starter-skill-order-numbered","arguments":[2,"E => Q => W"]},"recMath":false,"items":[{"id":"1039","count":1},{"id":"2003","count":1},{"id":"2055","count":1}]},{"type":"Trinkets","_type":{"i18n":"item-sets-block-trinkets"},"recMath":false,"items":[{"id":"2055","count":1},{"id":"3340","count":1},{"id":"3341","count":1},{"id":"3348","count":1},{"id":"3363","count":1}]},{"type":"Recommanded Items","_type":{"i18n":"item-sets-block-recommanded"},"recMath":false,"items":[{"id":"3107","count":1},{"id":"3174","count":1},{"id":"3504","count":1}]},{"type":"Boots (choose one)","_type":{"i18n":"item-sets-block-boots"},"recMath":false,"items":[{"id":"3111","count":1},{"id":"3117","count":1},{"id":"3158","count":1}]},{"type":"Consumables","_type":{"i18n":"item-sets-block-consumables"},"recMath":false,"items":[{"id":"2003","count":1},{"id":"2138","count":1},{"id":"2139","count":1},{"id":"2140","count":1}]}],"priority":true,"provider":"opgg"}],"gameMode":"CLASSIC"}},"championId":427,"gameVersion":"9.5","gameRegion":"la1","version":"2.4.2"}
[Renderer] [log] [20:13:02] Flu.x >> Upload

Hello, there seems to be an issue with the provider that Manaflux tried to use for you, LoLFlavor. Usually when it can't use a provider, it tries another one. Are you sure you have all of them enabled, and ordered in a way you like it?

You can disable LoLFlavor by just clicking on it in the settings.

I had disable some, since it was taking forever to Pre-download them all. But I'll try again with all enabled.

Try with LoLFlavor disabled. Don't worry, pre-download takes a lot of time, that's because it does one champion at a time. I'll resolve this issue later because I have to rework completely the foundations of Manaflux for that, but you don't have to pre-download before entering in champion select, that's just an optional feature for people who'd like a faster load when you're in champion select.

So I got it to work  by increasing the Maximum number of roles to download to 10 and running the pre-download again with LoLFlavor disabled.
I only play ARAM so I would need to download a champion every game or whenever I roll the dice.
I also found out that no ARAM runes are downloaded from any provider:(. The app does seem useful for any other mode though!

Manaflux takes care of that, every time your champion changes for any reason, it retrieves the data from your computer (if it was downloaded before) or downloads it. I haven't used LoLFlavor for a long time, but I'll see as soon as I have time if I can fix it.


New feature request

Is it possible and how easy to make a change that could change the view
sometime is nice open Slide-overs type modal and sometimes traditional??
   public function render(): View
    {
        return view('livewire-ui::modal');
    }

Thanks for the suggestion. I will take a look and see if this is possible 😄

+1


Workshop #3 Add more info for Metrics and Monitoring

Right now the metrics and monitoring shows what exists in openshift. But it does not show any valuable info as to why user benefits from these features.
Maybe we need to think about some way to bring meaning to this.
We could do something like:

We could switch order of this workshop to autoscale. So we can show the graph when usage went too high.
Run higher workload that adds some pressure of resource.
Change/Add a path to our application that has some random failure maybe.

I'm not sure this is still relevant. If it is, please reopen and we'll work to a resolution.


added us-gov-west-1 Govcloud regions for SNS and SQS

This PR is to address issue #1760

It looks like the linter is unhappy. If you can fix that, will be happy to merge!

This has already been added in #2657, so I'll close this PR.


Bundler fails to resolve JSON version

Reported by @dysinger against Chef 0.10.6:
https://gist.github.com/1480120

Fixed in 0.5.2.


api-server can not setup on centos 7.3

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
bug report

Environment:

Cloud provider or hardware configuration:

OS (printf "$(uname -srm)\n$(cat /etc/os-release)\n"):

Version of Ansible (ansible --version):

Kargo version (commit) (git rev-parse --short HEAD):
Network plugin used:
Copy of your inventory file:
[kube-master]
jdancer-master
[etcd]
jdancer-master
jdancer-worker
[kube-node]
jdancer-worker
[k8s-cluster:children]
kube-node
kube-master
Command used to invoke ansible:
Output of ansible run:

Anything else do we need to know:

fatal: [jdancer-master]: FAILED! => {
"attempts": 4,
"changed": false,
"cmd": [
"/usr/local/bin/kubectl",
"create",
"-f",
"/etc/kubernetes/kube-system-ns.yml"
],
"delta": "0:00:00.269913",
"end": "2017-03-31 14:28:56.763897",
"failed": true,
"invocation": {
"module_args": {
"_raw_params": "/usr/local/bin/kubectl create -f /etc/kubernetes/kube-system-ns.yml",
"_uses_shell": false,
"chdir": null,
"creates": null,
"executable": null,
"removes": null,
"warn": true
}
},
"rc": 1,
"start": "2017-03-31 14:28:56.493984",
"stderr": "The connection to the server localhost:8080 was refused - did you specify the right host or port?",
"stderr_lines": [
"The connection to the server localhost:8080 was refused - did you specify the right host or port?"
 Previously had working before pulling from master today.
first run of kargo: 30 times timeout waiting for apiserver
second run of kargo: 4 times FAILED - RETRYING: TASK: kubernetes/master : Create kube system namespace (4 retries left).
same error on namespace creation ""The connection to the server localhost:8080 was refused - did you specify the right host or port?""
I am using Ubuntu 16.04 servers for my nodes on a home network

Went back to earlier known-working version (based off commit  https://github.com/kubernetes-incubator/kargo/commit/f5af86c9d5e684eebdd6a70358cc21f6cce1a087 ) and my cluster was able to start up again.

Not for me... Just checkout on https://github.com/kubernetes-incubator/kargo/commit/f5af86c9d5e684eebdd6a70358cc21f6cce1a087 and still failing :/

Same issue here, the problem commit is ccc11e568092df89d8745ef3595ea8019f17db6d, found out with git bisect
It seems kargo doesn't work well with kubernetes 1.6.1 ATM, the latest working kubernetes version is 1.5.6

@torshie this is definitely not working for me on v2.1.1 tag with 1.5.6 k8s using calico on a centos7 image.

@leseb I'm using Flannel. Calico may need special setups in your switchs/routers, I'm not sure. Flannel should work in any network environment, since it's an overlay.

@torshie, thanks for the input. I'm actually trying with Calico since Flannel fails really quickly on the task "Wait for flannel subnet.env file presence". I've been so unlucky with this...

@leseb Did you changed etcd_data_dir or docker_daemon_graph in k8s-cluster.yml ? IIRC changing these two will cause problems.
BTW, I found the options in k8s-cluster.yml are quite fragile, avoid changing the default at all costs, if you want to move data around, bind mount a different directory instead.

@torshie I haven't changed anything, expect the number of VMs :(

My logs with verbose 6 using kube_version 1.5.6:
I0419 21:52:05.977958    2469 feature_gate.go:189] feature gates: map[]
I0419 21:52:05.978849    2469 loader.go:354] Config loaded from file /etc/kubernetes/node-kubeconfig.yaml
I0419 21:52:06.113987    2469 server.go:536] Using self-signed cert (/var/run/kubernetes/kubelet.crt, /var/run/kubernetes/kubelet.key)
I0419 21:52:06.114011    2469 docker.go:356] Connecting to docker on unix:///var/run/docker.sock
I0419 21:52:06.114023    2469 docker.go:376] Start docker client with request timeout=2m0s
E0419 21:52:06.116225    2469 cni.go:163] error updating cni config: No networks found in /etc/cni/net.d
I0419 21:52:06.175649    2469 manager.go:143] cAdvisor running in container: "/docker/e11e03a942ae0003209e4436b431a37b99a05acae0b6360972b8a623a72f540b"
W0419 21:52:06.182593    2469 manager.go:151] unable to connect to Rkt api service: rkt: cannot tcp Dial rkt api service: dial tcp <IP_ADDRESS>:15441: getsockopt: connection refused
I0419 21:52:06.189354    2469 fs.go:117] Filesystem partitions: map[/dev/mapper/VolGroup00-LogVol00:{mountpoint:/var/lib/docker/overlay major:253 minor:0 fsType:xfs blockSize:0}]
I0419 21:52:06.195364    2469 manager.go:198] Machine: {NumCores:1 CpuFrequency:4007988 MemoryCapacity:512323584 MachineID:8e025a21a4254e11b028584d9d8b12c4 SystemUUID:5BCF7458-2396-426A-A101-464E9E0CEE33 BootID:3e954e27-e4ce-46b5-bda4-bd8636aa44f2 Filesystems:[{Device:/dev/mapper/VolGroup00-LogVol00 Capacity:40212119552 Type:vfs Inodes:19644416 HasInodes:true} {Device:overlay Capacity:40212119552 Type:vfs Inodes:19644416 HasInodes:true}] DiskMap:map[253:0:{Name:dm-0 Major:253 Minor:0 Size:40231763968 Scheduler:none} 253:1:{Name:dm-1 Major:253 Minor:1 Size:1610612736 Scheduler:none} 252:0:{Name:vda Major:252 Minor:0 Size:44023414784 Scheduler:none}] NetworkDevices:[{Name:eth0 MacAddress:52:54:00:e3:a4:bd Speed:0 Mtu:1500} {Name:eth1 MacAddress:52:54:00:cb:d9:50 Speed:0 Mtu:1500}] Topology:[{Id:0 Memory:536322048 Cores:[{Id:0 Threads:[0] Caches:[{Size:32768 Type:Data Level:1} {Size:32768 Type:Instruction Level:1} {Size:4194304 Type:Unified Level:2}]}] Caches:[]}] CloudProvider:Unknown InstanceType:Unknown InstanceID:None}
I0419 21:52:06.197563    2469 manager.go:204] Version: {KernelVersion:3.10.0-514.6.1.el7.x86_64 ContainerOsVersion:Debian GNU/Linux 8 (jessie) DockerVersion:1.13.1 CadvisorVersion: CadvisorRevision:}
W0419 21:52:06.199594    2469 container_manager_linux.go:205] Running with swap on is not supported, please disable swap! This will be a fatal error by default starting in K8s v1.6! In the meantime, you can opt-in to making this a fatal error by enabling --experimental-fail-swap-on.
I0419 21:52:06.199626    2469 oom_linux.go:64] attempting to set "/proc/self/oom_score_adj" to "-999"
I0419 21:52:06.199676    2469 server.go:666] Sending events to api server.
I0419 21:52:06.199717    2469 server.go:700] Using root directory: /var/lib/kubelet
I0419 21:52:06.199737    2469 kubelet.go:242] Adding manifest file: /etc/kubernetes/manifests
I0419 21:52:06.199757    2469 file.go:47] Watching path "/etc/kubernetes/manifests"
I0419 21:52:06.199760    2469 kubelet.go:252] Watching apiserver
I0419 21:52:06.199779    2469 reflector.go:185] Starting reflector *api.Pod (0s) from pkg/kubelet/config/apiserver.go:44
I0419 21:52:06.199833    2469 reflector.go:185] Starting reflector *api.Service (0s) from pkg/kubelet/kubelet.go:378
I0419 21:52:06.199861    2469 reflector.go:185] Starting reflector *api.Node (0s) from pkg/kubelet/kubelet.go:386
I0419 21:52:06.200496    2469 reflector.go:234] Listing and watching *api.Node from pkg/kubelet/kubelet.go:386
I0419 21:52:06.201036    2469 file.go:156] Reading config file "/etc/kubernetes/manifests/flannel-pod.manifest"
I0419 21:52:06.204477    2469 common.go:53] Generated UID "515b303ebba3f35430b77eef4a0fe425" pod "flannel" from /etc/kubernetes/manifests/flannel-pod.manifest
I0419 21:52:06.204490    2469 common.go:57] Generated Name "flannel-k8s-01" for UID "515b303ebba3f35430b77eef4a0fe425" from URL /etc/kubernetes/manifests/flannel-pod.manifest
I0419 21:52:06.204493    2469 common.go:62] Using namespace "kube-system" for pod "flannel-k8s-01" from /etc/kubernetes/manifests/flannel-pod.manifest
I0419 21:52:06.204653    2469 file.go:156] Reading config file "/etc/kubernetes/manifests/kube-proxy.manifest"
I0419 21:52:06.205144    2469 common.go:53] Generated UID "9b146f076971df080c2298a6a8e84392" pod "kube-proxy" from /etc/kubernetes/manifests/kube-proxy.manifest
I0419 21:52:06.205152    2469 common.go:57] Generated Name "kube-proxy-k8s-01" for UID "9b146f076971df080c2298a6a8e84392" from URL /etc/kubernetes/manifests/kube-proxy.manifest
I0419 21:52:06.205156    2469 common.go:62] Using namespace "kube-system" for pod "kube-proxy-k8s-01" from /etc/kubernetes/manifests/kube-proxy.manifest
I0419 21:52:06.205220    2469 config.go:281] Setting pods for source file
I0419 21:52:06.205291    2469 config.go:397] Receiving a new pod "flannel-k8s-01_kube-system(515b303ebba3f35430b77eef4a0fe425)"
I0419 21:52:06.205299    2469 config.go:397] Receiving a new pod "kube-proxy-k8s-01_kube-system(9b146f076971df080c2298a6a8e84392)"
I0419 21:52:06.205348    2469 reflector.go:234] Listing and watching *api.Pod from pkg/kubelet/config/apiserver.go:44
I0419 21:52:06.205521    2469 reflector.go:234] Listing and watching *api.Service from pkg/kubelet/kubelet.go:378
I0419 21:52:06.205649    2469 round_trippers.go:318] GET http://<IP_ADDRESS>:8080/api/v1/nodes?fieldSelector=metadata.name%3Dk8s-01&resourceVersion=0  in 5 milliseconds
E0419 21:52:06.205711    2469 reflector.go:188] pkg/kubelet/kubelet.go:386: Failed to list *api.Node: Get http://<IP_ADDRESS>:8080/api/v1/nodes?fieldSelector=metadata.name%3Dk8s-01&resourceVersion=0: dial tcp <IP_ADDRESS>:8080: getsockopt: connection refused
I0419 21:52:06.205733    2469 round_trippers.go:318] GET http://<IP_ADDRESS>:8080/api/v1/services?resourceVersion=0  in 0 milliseconds
E0419 21:52:06.205769    2469 reflector.go:188] pkg/kubelet/kubelet.go:378: Failed to list *api.Service: Get http://<IP_ADDRESS>:8080/api/v1/services?resourceVersion=0: dial tcp <IP_ADDRESS>:8080: getsockopt: connection refused
I0419 21:52:06.205780    2469 round_trippers.go:318] GET http://<IP_ADDRESS>:8080/api/v1/pods?fieldSelector=spec.nodeName%3Dk8s-01&resourceVersion=0  in 0 milliseconds

@leseb  I tried f5af86c9d5e684eebdd6a70358cc21f6cce1a087 with centos 7.3 and its working fine for me.
encounter some issues thought.

If you are using proxy on your nodes, you have to systemctl daemon-reload   see this issue #1244
if you have firewalld up and running. I had to add some rules to allow access to the API serve

@simonlinj firewalld is not running, but I see a bunch of iptables rules from kube. I'm not using a proxy either.
Simply deploying with vagrant + libvirt using centos7 VM.

I also ran yum update for each node before install.
I suggest you to recreate yours nodes VM and make sure you recreate your
inventory after git checkout.
On Thu, Apr 20, 2017 at 12:50 Sébastien Han<EMAIL_ADDRESS>wrote:

@simonlinj https://github.com/simonlinj firewalld is not running, but I
see a bunch of iptables rules from kube. I'm not using a proxy either.
Simply deploying with vagrant + libvirt using centos7 VM.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/kargo/issues/1207#issuecomment-295810568,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABb-SgWs-J6kw5P9_9N-8tdWKacRP_i2ks5rx4zdgaJpZM4Mz3xF
.

using latest (https://github.com/kubernetes-incubator/kargo/commit/502f2f040db01f3e2237010359b0d26b058fd4cf) master I was able to deploy my kubernetes cluster using kargo again (up-to-date Ubuntu 16.04 nodes).  seems to have cleared up the issues I had been encountering with system namespace and kubernetes 1.6 referenced above/on this issue...

Thanks for the assistance @simonlinj, @idcrook and the others.
I'm not sure how you guys are managing to get this working.
I just changed the numbers of machines on my setup and tried different tag (2.2.0 and commits mentioned + master)/kube version combinations.
I'm not touching the VMs as they are provisioned by Vagrant+libvirt, then the playbook runs. Yet I get stuck on the task "Wait for flannel subnet.env file presence" because the api-server can not start.
Sorry to the maintainers but this project just doesn't work on Centos7, I'm not doing anything fancy here, I just changed the numbers of VMs and just fired vagrant up :/

@leseb I'm using VMs created manually, and setup ssh keys manually. Also, I'm using the ansible-playbook to run the playbook directly, instead of the the command line wrapper.

@leseb i also created my VMs manually.
On Mon, Apr 24, 2017 at 21:32 torshie<EMAIL_ADDRESS>wrote:

@leseb https://github.com/leseb I'm using VMs created manually, and
setup ssh keys manually. Also, I'm using the ansible-playbook to run the
playbook directly, instead of the the command line wrapper.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/kargo/issues/1207#issuecomment-296866442,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABb-SirxfoGeThN4I5mK3W0u9_olnpGnks5rzU0_gaJpZM4Mz3xF
.

@leseb Just now I run the "Wait for flannel subnet.env file presence" also. Sometimes flannel fails to contact etcd. You can get the flannel logs with command:
docker ps -a|grep flannel
docker logs
Check every node of your cluster, when flannel run into this problem, simply kill the flannel container with "docker kill ", then a new flannel container will spawn automatically. Keep doing this until you the host has a network interface named "flannel*", then delete all the manually killed containers. Finally rerun the playbook.

Thanks again @torshie and @simonlinj, creating the VMs manually or through Vagrant result in the same thing, you get VMs up and running :).
In my case, I'm hitting the error "Wait for flannel subnet.env file presence" because the api-server does not start. Since it can not start, there is no flannel containers running.
I still haven't been able to figure out why the api-server can not start though :(

Is there any work being done on getting these to work?
I'm experiencing exact same issue on multiple centos-based clusters with version 1.6.* of kubernetes. Only 1.5.* works, but nothing above that.

Hmm, I'm unsure of how to help you guys with this. I was able to deploy to 2 nodes (1 master/1 worker) on OpenStack with CentOS 7 just now. I chose flannel as the network plugin and deployed from the latest of the master branch. All seems to have completed as expected.
[centos@kube-1 ~]$ kubectl get nodes
NAME               STATUS                     AGE       VERSION
kube-1     Ready,SchedulingDisabled   4m        v1.6.1+coreos.0
kube-2    Ready                      4m        v1.6.1+coreos.0

@rsmitty I'm using vagrant + libvirt with the centos/7 image. So if you have a linux workstation you can easily reproduce.
I'm running master, 361a5eac7e74b143f7261f0d86d9c5cfe35ae5b7.
Here's my vagrant/config.rb:
$num_instances = 6
$box = "centos/7"
$kube_master_instances = $num_instances == 1 ? $num_instances : ($num_instances - 4)
$kube_node_instances = $num_instances

Thanks!

I don't have a linux workstation handy unfortunately, but I was able to run successfully using the virtualbox vagrant provider on my mac. Only thing I changed in the vagrantfile was the box variable to match yours, centos/7. It created a 3 node cluster which seems to work as expected.

@rsmitty alright, let me try on my OSX. Thanks.

@rsmitty - i keep on trying it on bare metal.
These nodes previously had docker swarm which i later upgrade to 1.5.1 to 1.5.3 to 1.5.6 to 1.5.7 version of kubernetes using kargo.
it is deployed with calico, i wasn't aware that I can choose which network driver to select, i can try switching to flannel, to be honest I don't really know much about these drivers to make an educated decision about which one is better or worse for us.
All nodes have 2 network interfaces, one for public (eth0) and one for internal communication (eth1). eth1 is completely open on firewalld, so that servers can interact within it's own LAN, while eth0 is restricted to publicly open ports only.
All internal communication goes to same hostname as the public hostnames, but each host contains /etc/hosts mappings from public hostname to local IP addresses.
So if server server1.domain.com has a public IP of <IP_ADDRESS> - /etc/hosts will contain an entry
<IP_ADDRESS> server1.domain.com server1
meaning that if the contianers try to communicate with each other by the hostnames, they will probably resolve to public IPs since the containers don't respect the /etc/hosts file of the host machine, which means that it's trying to access API server port on the public IP address, which blocks the PORT number on public network. I tried removing all iptables (firewalld) rules prior to attempting to reinstall kubernetes 1.6.x using kargo - but that didn't seem to have made any difference, and since previous versions of kubernetes (1.5.x) work correctly - I doubt that my scenario that is described above is affecting the proper communication between the containers and API server, etc.
Other than that - tried bare metal, where all servers connected on vlan, as well as nodes that are connected using the single hardware switch. Both with the same eth0 + eth1 setup.

I am using kubespray, commit 586d2a41ce474.
I have the same issue, but my master log is quit different.
Jun 21 02:27:38 node1 systemd: Started Kubernetes Kubelet Server.
Jun 21 02:27:38 node1 kubelet: I0621 02:27:38.418330   12472 feature_gate.go:144] feature gates: map[]
Jun 21 02:27:38 node1 kubelet: error: failed to run Kubelet: invalid kubeconfig: stat /etc/kubernetes/kubelet.conf: no such file or directory
Jun 21 02:27:38 node1 systemd: kubelet.service: main process exited, code=exited, status=1/FAILURE
Jun 21 02:27:38 node1 systemd: Unit kubelet.service entered failed state.
Jun 21 02:27:38 node1 systemd: kubelet.service failed.
Jun 21 02:27:38 node1 audispd: node=node1 type=SERVICE_STOP msg=audit(1498012058.428:179828): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=kubelet comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Jun 21 02:27:48 node1 audispd: node=node1 type=SERVICE_START msg=audit(1498012068.633:179829): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=kubelet comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 21 02:27:48 node1 systemd: kubelet.service holdoff time over, scheduling restart.
Jun 21 02:27:48 node1 audispd: node=node1 type=SERVICE_STOP msg=audit(1498012068.633:179830): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=kubelet comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 21 02:27:48 node1 systemd: Cannot add dependency job for unit docker.socket, ignoring: Unit not found.
Jun 21 02:27:48 node1 systemd: Cannot add dependency job for unit docker-storage-setup.service, ignoring: Unit not found.
Jun 21 02:27:48 node1 systemd: Starting Kubernetes Kubelet Server...
Jun 21 02:27:48 node1 docker: time="2017-06-21T02:27:48.662137641Z" level=error msg="Handler for DELETE /v1.26/containers/kubelet returned error: No such container: kubelet"
Jun 21 02:27:48 node1 docker: Error response from daemon: No such container: kubelet
Jun 21 02:27:48 node1 audispd: node=node1 type=SERVICE_START msg=audit(1498012068.665:179831): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=kubelet comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 21 02:27:48 node1 systemd: Started Kubernetes Kubelet Server.
Jun 21 02:27:48 node1 kubelet: I0621 02:27:48.928756   12500 feature_gate.go:144] feature gates: map[]
Jun 21 02:27:48 node1 kubelet: error: failed to run Kubelet: invalid kubeconfig: stat /etc/kubernetes/kubelet.conf: no such file or directory
Jun 21 02:27:48 node1 systemd: kubelet.service: main process exited, code=exited, status=1/FAILURE
Jun 21 02:27:48 node1 systemd: Unit kubelet.service entered failed state.
Jun 21 02:27:48 node1 systemd: kubelet.service failed.
Jun 21 02:27:48 node1 audispd: node=node1 type=SERVICE_STOP msg=audit(1498012068.935:179832): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=kubelet comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'

look like my kubelet cannot start expectedly?

 Workaround?

@4406arthur Your log are pointing a missing file /etc/kubernetes/kubelet.conf.
Did you check that before?

@leseb Did you finnaly get this working?

@simonlinj
Once I'm stuck to the task "wait for flannel..." I run a systemctl daemon-reload on my node like you said to pass this step. It worked.
But then, the api server still doesn't start.
The playbook fail at first on the task Create kube system namespace.
TASK [kubernetes/master : Create kube system namespace] ***************************************************************************************************************************************
Thursday 13 July 2017  10:00:25 +0200 (0:00:01.390)       0:06:24.795 *********
FAILED - RETRYING: Create kube system namespace (4 retries left).
FAILED - RETRYING: Create kube system namespace (3 retries left).
FAILED - RETRYING: Create kube system namespace (2 retries left).
FAILED - RETRYING: Create kube system namespace (1 retries left).
fatal: [node1]: FAILED! => {"attempts": 4, "changed": false, "cmd": ["/usr/local/bin/kubectl", "create", "-f", "/etc/kubernetes/kube-system-ns.yml"], "delta": "0:00:00.369560", "end": "2017-07-13 08:01:04.334275", "failed": true, "rc": 1, "start": "2017-07-13 08:01:03.964715", "stderr": "The connection to the server localhost:8080 was refused - did you specify the right host or port?", "stderr_lines": ["The connection to the server localhost:8080 was refused - did you specify the right host or port?"], "stdout": "", "stdout_lines": []}

Here, as we can see the task try to contact the api server. It should have checked that is one is available before, doesn't it?
I can see that the api-server masnifest file is copied with this line.
Then a notify is called to wait for the service, but between those two task I don't see the task that launch the api server.

Kubelet is not able to start the api server.

Any progress from your side guys? @leseb @rsmitty

Fixed from my side.
I had two error:

I use vsphere as cloud provider, kubelet try to get register the name of the VM so you need to have a valid FQDN name as a VM name when you use this backend.
Error with related to this issue. I've pushed a PR to fix it.

I can validate that the install is ok on Centos 7.3.

@Sispheor never fixed that issue on my side. I'll try again later.

Having a similar issue with CentOS 7 on Azure. api-server container/process not started/created. Appreciate any help!

I've spent a couple hours with the same problem today on CentOS 7.3.1611/4.12.10-1.el7.elrepo.x86_64/systemd 30.el7_3.9 and found the following:
In /etc/kubernetes/kubelet.env --cgroups-per-qos=True is passed to kubelet via the KUBELET_ARGS environment variable. Kubelet reports that the option has been elected to be used, but is missing the --cgroup-root  argument and elects a default:
I0831 13:44:12.071947   25451 server.go:509] --cgroups-per-qos enabled, but --cgroup-root was not specified.  defaulting to /
This breaks the Kubernetes Pod Lifecycle Event Generator (https://github.com/mironov/kubernetes/blob/master/docs/proposals/pod-lifecycle-event-generator.md) as it would appear the path to the correct cgroup is incorrect: I0831 13:44:12.183877   25451 kubelet.go:1752] skipping pod synchronization - [Failed to start ContainerManager failed to initialise top level QOS containers: root container /kubepods doesn't exist container runtime is down PLEG is not healthy: pleg was last seen active 2562047h47m16.854775807s ago; threshold is 3m0s]
As a work around I've set the argument --cgroups-per-qos=False which brings the Kubernetes pods up:
CONTAINER ID        IMAGE                                                                                COMMAND                  CREATED             STATUS              PORTS               NAMES 96133c4541f7        quay.io/coreos/hyperkube@sha256:e2fb6b5abd00083f356264b1a916e74565f6f1ffb4b6fa6cf0fcac1d0c0f7bf7   "/hyperkube proxy ..."   6 seconds ago       Up 6 seconds                            k8s_kube-proxy_kube-proxy-node1_kube-system_efb6c2a3faafeab4ae65844b085ad664_0 14d2e8af97db        quay.io/coreos/hyperkube@sha256:e2fb6b5abd00083f356264b1a916e74565f6f1ffb4b6fa6cf0fcac1d0c0f7bf7   "/hyperkube apiser..."   6 seconds ago       Up 6 seconds                            k8s_kube-apiserver_kube-apiserver-node1_kube-system_0049c4cbd047992d82708b430bfa2eaf_0 cf89afd02050        gcr.io/google_containers/pause-amd64:3.0                                                           "/pause"                 7 seconds ago       Up 6 seconds                            k8s_POD_kube-proxy-node1_kube-system_efb6c2a3faafeab4ae65844b085ad664_0 a7ab122fcba8        gcr.io/google_containers/pause-amd64:3.0                                                           "/pause"                 7 seconds ago       Up 6 seconds                            k8s_POD_kube-apiserver-node1_kube-system_0049c4cbd047992d82708b430bfa2eaf_0 fac725256e7d        quay.io/calico/node:v2.5.0                                                                         "start_runit"            51 minutes ago      Up 51 minutes                           calico-node
To properly fix this I believe we need to set --cgroup-root to the correct value. Via systemctl-cgls it looks this should be under the docker hierarchy? If someone confirms I'll create a PR to get the argument added.


Update OWNERS

I suggest to add Terry as the owner as well.

This change is

I signed it!

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.
What to do if you already signed the CLA
Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ Googlers: Go here for more info.

I signed it!

I signed it!

Thanks! /assign @richardsliu

Thanks!
/assign @richardsliu

/lgtm
/approve


Created file q203.cpp

Solved a problem that wasn't already in the repository.

[ ] Star ⭐ the repository. 🙂
Also give me a follow if you like😅


Special handling of the "C" package

When a package imports the C package, deplist complains like so:
2015/11/15 09:27:42 cannot find package "C" in any of:

This is a special package in the stdlib, and perhaps deplist should treat is specially. Thoughts?

Yeah, thanks. I'll fix this later today.


Document How to compile HIE with profiling enabled?

According to https://github.com/haskell/haskell-ide-engine/issues/556#issuecomment-430202467 I should be able to compile HIE with profiling enabled like this:
stack install --work-dir=.stack-work-profile --profile

I've tried it on a fresh clone of the repository on macOS and Linux and it fails on both systems with the same error:
    [34 of 34] Compiling Paths_HaRe       ( .stack-work-profile/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/autogen/Paths_HaRe.hs, .stack-work-profile/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/Paths_HaRe.p_o )
    Preprocessing executable 'ghc-hare' for HaRe-<IP_ADDRESS>..
    Building executable 'ghc-hare' for HaRe-<IP_ADDRESS>..

    <no location info>: warning: [-Wmissing-home-modules]
        These modules are needed for compilation but not listed in your .cabal file's other-modules:
            Paths_HaRe
    [1 of 2] Compiling Paths_HaRe       ( .stack-work-profile/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/ghc-hare/autogen/Paths_HaRe.hs, .stack-work-profile/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/ghc-hare/ghc-hare-tmp/Paths_HaRe.p_o )
    [2 of 2] Compiling Main             ( app/MainHaRe.hs, .stack-work-profile/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/ghc-hare/ghc-hare-tmp/Main.p_o )
    /Users/skress/work/src/haskell-ide-engine/submodules/HaRe/app/MainHaRe.hs:25:16: fatal:
        cannot find object file ‘.stack-work-profile/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/ghc-hare/ghc-hare-tmp/Paths_HaRe.dyn_o’
        while linking an interpreted expression

Any ideas how to avoid this problem? (In case the question arises: I'd like to further debug my problem in #1207 and my current approach to creating a build with profiling seems to be broken.)

Adding profiling: True to the cabal.project file and using cabal new-build worked fine for me when I tried it. I wonder if you might run into problems if you don't have a profiled version of GHC (you have to build this from source so it probably isn't worth the effort).
Any easier way to debug this issue might be to disable profiling in your project if it's enabled :) ?

Thanks, kind of worked. For future reference this is what worked for me:
cat << EOF > cabal.project.local
package *
  profiling: True
EOF

cabal new-install exe:hie --enable-profiling -w /Users/skress/.stack/programs/x86_64-osx/ghc-8.6.4/bin/ghc --write-ghc-environment-files=never --symlink-bindir=$HOME/.local/bin --overwrite-policy=always -j9 --reinstall

@alanz I can give it a try if the approach to build hie with profiling as I described it above is what would like to see in the documentation.
I would add a section to docs/Build.md#steps-to-build-hie.
I have tried my approach on macOS and Linux. It worked for a minimal project that I created via "stack new testproject", i.e. in VSCode I could see stacktraces when executing hie with +RTS -xc.
Using that profiling build of hie with a new project created via "stack new yesodtest yesod-sqlite" did not work. I had to rebuild that project itself with profiling support to see stacktraces. Is that expected behavior for projects like Yesod (probably due to it's use of Template Haskell)?

@skress that will be great. And getting it in as a preliminary doc of something that is known to work in at least one config is more important than having it in some sense "perfect".


Remove backup scanner

Using the provider without watch functionality will end up with an Error throw by scanner. This has to be handlede by top layers (UI, CLI)

Pull Request Test Coverage Report for Build 1209

2 of 3 (66.67%)  changed or added relevant lines in 1 file are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.2%) to 83.147%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Scanner/Scanner.ts
2
3
66.67%

Files with Coverage Reduction
New Missed Lines
%

src/Actions/Pending.ts
4
37.84%

Totals

Change from base Build 1203:
-0.2%

Covered Lines:
538

Relevant Lines:
624

💛  - Coveralls


Move CI to doctest instead of gtest

The issue on windows seems related to the infrastructure, let's merge and try to workaround it.


Question: security code review

Hi,
Did you guys ever did a security review on your code by an external party?
And if yes, are you willing to share these results or can we find it back in some specifc commits?
We are scheduling a code review by an external security company and if you want, we would like to share these results with you/the community as feedback to improve the product (if anything has been found) :)
Michiel

We have not performed an external security review on this project. If you're willing to foot the bill then that sounds great!


Add Container task

Adds support for ContainerTask: https://docs.flyte.org/projects/flytekit/en/latest/generated/flytekit.ContainerTask.html
Container tasks will allow to execute arbitrary container as Flyte task.
TL;DR
Adds ContainerTask allowing to execute arbitrary container as a Flyte task. Such functionality already exists in Python SDK: https://docs.flyte.org/projects/flytekit/en/latest/generated/flytekit.ContainerTask.html
Type

[ ] Bug Fix
[x] Feature
[ ] Plugin

Are all requirements met?

[x] Code completed
[x] Smoke tested
[x] Unit tests added
[x] Code documentation added
[x] Any pending items have an associated Issue

Complete description
ContainerTask functionality has been ported with minimal changes to the API. Container tasks will have its own registar therefore minimum changes were made to existing code for runnable tasks.
An example of a container task added here: https://github.com/evdokim/flytekit-java/blob/container-task/flytekit-examples/src/main/java/org/flyte/examples/HelloContainerTask.java
Tracking Issue
No issues has been created
Follow-up issue
No follow up issues

@narape thank you for the review, I addressed your comments, could you take a look again?

Snyk problem was fixed in https://github.com/flyteorg/flytekit-java/pull/113


[11.x] Adds without array helper

without removes a value from an array
Arr::without([10, 20, 30], 30);
// [10, 20]

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


Multiple entries of the same query parameter are encoded using ; (semicolon)

Description of the bug
In commit 1276c03cf5315658bc14c87c504b68d58ba03258 (PR #794), we fixed #792. However, the fix is still not optimal since query parameters where either part of the key=value part includes semicolon will be unable to be represented in the simulation JSON.
To be honest, my use case don't have a requirement to use semicolons at the moment. However, I see a risk with the current implementation in that it uses a separator which could potentially be a fully valid part of a query parameter for a "reserved" purpose like this. This could potentially be very confusing to our users.
Ideally, the values would be present multiple times in the JSON (i.e. no separator), but if this is considered too complex/time consuming, we should at the very least choose a separator which is more than a single character. ;;; would be an improvement (note, this is just a suggestion; feel free to come up with a better option if you like)
Steps to reproduce the issue
Make a query which includes the same query string multiple times.
Like this: http://localhost/some-api/some-resource?q=access:vod&q=order:latest&q=profile:vd
Observed result
"q": [
    {
        "matcher": "exact",
        "value": "access:vod;order:latest;profile:vd"
    }

Hoverfly error messages seen (If none, say none)
none

If possible, add screenshots to help explain your problem
Expected result
"q": [
    {
        "matcher": "exact",
        "value": "access:vod;;;order:latest;;;profile:vd"
    }

or (preferably):
"q": [
    {
        "matcher": "exact",
        "value": "access:vod"
    },
    {
        "matcher": "exact",
        "value": "order:latest"
    },
    {
        "matcher": "exact",
        "value": "profile:vd"
    }

or even this (I think this would be my personal favorite, in terms of readability of the JSON):
"q": [
    {
        "matcher": "exact",
        "value": [
            "access:vod",
            "order:latest",
            "profile:vd"
        ]
    }

Additional relevant information

Hoverfly version:

+----------+--------------+
| hoverctl | master-3141  |
| hoverfly | v1.0.0-rc.2  |
+----------+--------------+

Anything that might help us to diagnose the problem

Hi @perlun, joining multiple values using a symbol for a query is not a permanent solution, we prefer to implement what you suggest as well:
"q": [
    {
        "matcher": "exact",
        "value": [
            "access:vod",
            "order:latest",
            "profile:vd"
        ]
    }

We thought about this before, and the value field is an interface type in the data model, so that it can be an array.
There will be matcher types that are specific to array values, like contains, containsExactly or containsOnly.

@tommysitu Sounds great! As noted, it's not a huge problem for me at the moment but it was just something we discovered internally when we figured out how it's currently serialized to the JSON.
Btw, thanks for a great product! :+1:

Hi, is this fixed?
Or some way working with queries like: q=access:vod&q=order:latest&q=profile:vd](http://localhost/some-api/some-resource?q=access:vod&q=order:latest&q=profile:vd

@tommysitu  I can work on this issue and fix this in above mentioned way.

@kapishmalik that'll be awesome!

@tommysitu  Work is in progress. Can you mark this as WIP or assign this issue to me?

@tommysitu  Raised PR

Thanks @kapishmalik your PR looks good!

@tommysitu I feel I need to relook at contains and containsonly matcher. I am confused with existing implementation. I will raise PR to fix those.

@tommysitu  can you check this PR and review implementations and if they make more sense now.

Thanks @tommysitu with reviews. I believe we are good with this issue now.

@perlun this is done. You can use and let us know inase of any issues.


models - add internal notes

must be present in the Family, Child, and Social Worker models.
internal notes will be a supporting model which can be applied to a Family, Child, or Social Worker.
note that internal notes from the migration will be brought into a text field and all joined together.

Dates for internal notes need to be sorted reverse chronologically instead of chronologically.


utils/github: Provide a better error message when users don't have any GitHub credentials set

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[x] Have you successfully run brew tests with your changes locally?
[x] Have you successfully run brew man locally and committed any changes?

When running brew request-bottle, which uses GitHub.open_api() from here, users who don't have credentials in the macOS keychain (ie, Linux users) or HOMEBREW_GITHUB_API_TOKEN receive "Error: Not Found" from the GitHub API returning a 404.
This is cryptic and confusing for newcomers to Linux maintenance, and potentially confusing to other folks using open_api where credentials are expected yet unset.
This adds a new MissingAuthenticationError to handle the case where the GitHub API returns 404 and there are no creds yet API scopes are required.

Before:
issyl0@sky:/home/linuxbrew/.linuxbrew/Homebrew$ brew request-bottle hello
==> Dispatching request to Homebrew/linuxbrew-core for hello
Error: Not Found

After:
issyl0@sky:/home/linuxbrew/.linuxbrew/Homebrew$ brew request-bottle hello
==> Dispatching request to Homebrew/linuxbrew-core for hello
Error: No GitHub credentials found in Keychain or environment.
Create a GitHub personal access token:
    https://github.com/settings/tokens/new?scopes=gist,public_repo&description=Homebrew
  echo 'export HOMEBREW_GITHUB_API_TOKEN=your_token_here' >> ~/.profile

This is an alternative to https://github.com/Homebrew/homebrew-linux-dev/pull/192.
I'm not 100% sure of the behaviour when a user doesn't strictly need an API token (ie, finding related issues when builds fail locally), but I think checking for scopes not being empty before raising this error should cover it?

Review period will end on 2021-02-08 at 12:57:15 UTC.

Review period skipped due to critical label.


Formats: Fix OMotM link and Ban Archeops from LCotM

The OMotM link lead to last month's OM
http://www.smogon.com/forums/threads/monsjustmons-lcotm-august.3514696/page-3#post-6358892 Archeops is banned from MonsJustMons, the LCotM

k @TheImmortal I moved Archeops to it's correct alphabetical place like u asked


ImagePicker works with ImageAsset instead of ImageSource

Images and thumbs will be of type ImageAsset instead of ImageSource.
Thumb property of type ImageSource is deprecated, thumbAsset should be used instead.

Resolved with https://github.com/NativeScript/nativescript-imagepicker/pull/49 #49


Accents work strangely with synonyms

Describe the bug
I had some issues with some of the synonyms working and some not and it seems I managed to identify a bug.
It seems words with accents are not used from the synonym table (and/or the query is deaccentized before looking up synonyms (?))
To Reproduce
Steps to reproduce the behavior:
Add synonyms:
["case"]: ["holder"] --> works (searches for holder with queries both "case" and "cáse"!)
["cáse"]: ["holder"] --> does not work (for either)
Expected behavior
In a previous issue (#949) it was mentioned there is no typo tolerance with synonyms, however it now seems when considering synonyms, there is some sort of deaccenting the query before looking up in the synonyms table (?)

Hey @mzperix,
I just looked into the code base and it seems like we forgot to unidecode (standardize: remove accents and lowercase words) therefore words in the query doesn't match the non-standardized synonyms.
I advise you to do that by hand: remove accents and lowercase the words on both sides, until we fix that.
We will fix that in the next release, thank you for this bug report :)

Hi, I wanted to work on this as my first issue! I was planning on using this crate, however, I'm unsure of exactly where the search queries are parsed in the code base. Thanks!

Like what we did with facets (which are lowercased), we will need to store the synonyms in two different places. On one side the one we currently store need to be de-unicased, but we also need the original user input and keep the two lists in sync, so when the user request for the synonyms, the unicased versions are returned. I am currently on implementing this one.

In the end, this is not possible to do it in a straighforward manner without impacting user that use non-latin scripts. This involves work done on the tokenizer. In the meantime, I suggest that the synonyms are registered in a lowercase and de-unicoded format.
Re-opening this issue, and linking it to the tokenizer tracking issue

@MarinPostma What is the status of this issue?

Still an open issue @qdequele

I check with v0.28.1, searching for cáse is not finding documents with holder!
Closing this


STORM-1645: convert nimbus.thrift.port to int to avoid ClassCastException

Verified that it works

+1

@HeartSaVioR - can you merge this?


Show estimate for tx completion

With an endpoint to get the block time (https://github.com/blockstack/stacks-blockchain-sidecar/issues/171), we can indicate roughly how long one would have to wait before a transaction is completed

FYI, the PR on the API for this: https://github.com/blockstack/stacks-blockchain-api/pull/199

closing in favor of: https://github.com/blockstack/explorer/issues/261

closing in favor of: https://github.com/blockstack/explorer/issues/261


[Bug] cannot build custom llama2 model in docker successfully

🐛 Bug

To Reproduce
###follow the mlc-ai/llm-perf-bench repo and test successfully

###then failed to build custom model
Environment

Platform (e.g. WebGPU/Vulkan/IOS/Android/CUDA):cuda
Operating system (e.g. Ubuntu/Windows/MacOS/...):ubuntu 20.04
Device (e.g. iPhone 12 Pro, PC+RTX 3090, ...):RTX2060 6G
How you installed MLC-LLM (conda, source):docker
How you installed TVM-Unity (pip, source):docker
Python version (e.g. 3.10):
GPU driver version (if applicable):
CUDA/cuDNN version (if applicable):
TVM Unity Hash Tag (python -c "import tvm; print('\n'.join(f'{k}: {v}' for k, v in tvm.support.libinfo().items()))", applicable if you compile models):
Any other relevant information:

run conda install -c conda-forge git-lfs solved the issue


版本4.0.0  PipeLine 对一个Hash Key 进行 hincrBy 操作时，会导致pika直接崩溃！

Is this a regression?
Yes
Description
pika_version : 4.0.0
I encountered a situation where the Pika server crashed directly while using Pipeline to perform a hintrby operation on a hash data structure.
Firstly, I set a null value for a field in the hash  , Then I tried to hincrby  the field , And the Pika  server crashed!
Such as
pipeline.hset(key,field,"");
pipeline.hincrBy(key,field,1);
Please provide a link to a minimal reproduction of the bug
No response
Screenshots or videos
No response
Please provide the version you discovered this bug in (check about page for version information)
version: 4.0.0
pika build date: 2024-07-13 04:51:32
OS: Ubuntu 22.04.3 LTS

Anything else?
No response

@QlQlqiqi

尚未复现出来。