godoc examples are not being compiled

See https://github.com/golang/go/issues/16773 for context.
Something in the tooling has changed and they are omitting to compile the examples if there is no output section. None of our examples are being built during go test.

IIUC, this is only going to affect 1.7? As long as it's fixed in 1.8 (or even better, 1.7.x) we should be fine since at least the examples are still being checked for correctness in 1.6.

It is currently a non-issue for me, closed the original bug as well. https://github.com/golang/go/issues/16773#issuecomment-241473447
Please update the bug if you experience an unexpected behavior.


LLM Response Added to Code Files

Describe the bug
In multiple files, the LLM response was added to the end of whatever file it starts working on first. See the screenshot for a representation, but this happened across almost every file in the repo.

Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-im584d
Steps to reproduce

Ask for a complicated app that will result in many files
Examine the end of each created file

Expected behavior
You will find the LLM Response at the bottom of the file. I had to delete them manually from each file.
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 129
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 67335897,
  "usedJSHeapSize": 52234557,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = dpmishler
Chat ID = 66ad2df9ed12

Additional context
No response

I’m familiar with React Flow, do you have details about the prompt resulting in this?

Hey @dpmishler ! :wave: Thanks for opening this issue!
We're aware of this and working on making sure this error does not happen. AFAIK, this is not related to the prompt provided to Bolt, it just happens from time to time.
We'll keep you posted!

This should be resolved, as we've upgraded to a new Sonnet 3.5 model under the hood and not seen any more reports of this. Going to close this for now, but feel free to comment below if you experience this again with the new model!

im getting the same issue with astro. should i open a new issue? 🤔


Browser's user agent is taken into consideration

Hi,
I noticed that browser's user agent is taken into consideration when someone gets denied by this module.
If someone makes a program that sends a huge amount of requests in a small amount of time with different user agent every time he will never get denied and all the requests will pass through.
Something like this (python code):
while True:
    opener = urllib2.build_opener()
    opener.addheaders = [('User-agent', 'Mozilla/5.0 ' + 'RANDOM_STRING_HERE')]
    response = opener.open('http://www.foo.bar')

On the other hand, if you ban someone based only on the public IP, whole local networks can be banned because one user got denied. My opinion is to leave it as an option for the developers to decide.

Similar issue is that this lib reads from X-Forwarded-For: https://github.com/rook2pawn/node-ddos/blob/1ad7a05cde671d65faf9f69712560ac9e61a993e/index.js#L53
req.ip in Express and this.ip in Koa will only read from X-Forwarded-For if you configure them to trust the proxy.
This library should do the same thing by exposing an option _params.trustProxy:
var host = _params.trustProxy
  ? (req.headers['x-forwarded-for'] || req.connection.remoteAddress)
  : req.connection.remoteAddress

@danneu @vipersec both issues have been addressed. Sorry for the delay, and thanks for the great suggestions.
https://github.com/rook2pawn/node-ddos/commit/c9bdbd9ece4d535129369da740d675143a8b1cc1


Hot reload fails with Error: Required named parameter '$creationLocationd_0dea112b090073317d4' must be provided.

Trying to hot reload with null safety enabled, throws the following error when trying to hot reload or hot restart after a change:
Error: Required named parameter '$creationLocationd_0dea112b090073317d4' must be provided.

Even though in reality, the constructor is empty.
Steps to Reproduce

Run flutter run --enable-experiment=non-nullable --no-sound-null-safety.
Hot reload
Or hot restart

Version
Flutter version is:
Channel master, 1.20.0-1.0.pre.208

Hi @creativecreatorormaybenot
I can't see the error when running the command with master, 1.20.0-1.0.pre.208.
Does it reproduce with any device? any app (with default counter)?
Could you provide your flutter doctor -v?

@VladyslavBondarenko It happens for me every time I change code and the error is printed for many constructors.
Note that I am using ({Key? key}) constructors for widgets to support null safety.

@creativecreatorormaybenot

I tried with this code sample
import 'package:flutter/material.dart';
void main() => runApp(MyApp());
class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}
class MyHomePage extends StatefulWidget {
  MyHomePage({Key? key, this.title = 'title'}) : super(key: key);
  final String title;
  @override
  _MyHomePageState createState() => _MyHomePageState();
}
class _MyHomePageState extends State<MyHomePage> {
  int _counter = 0;
  void _incrementCounter() {
    setState(() {
      _counter++;
    });
  }
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            Text(
              'You have pushed the button this many times:',
            ),
            Text(
              '$_counter',
              style: Theme.of(context).textTheme.headline4,
            ),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: Icon(Icons.add),
      ),
    );
  }
}

With master 1.20.0-1.0.pre.208 and with current master 1.20.0-1.0.pre.222, but I can't see the error (tried with --verbose as well).
Could you edit the code to reproduce it? or can you see the error with this code?

@VladyslavBondarenko It happens in a large proprietary, so it is hard to find a reproducible example.
I finally accomplished to create a reproducible example ❤ Really hope this can be addressed now. I am not sure what is required, but after making example apps for a while, I finally encounter the bug.
OK, here are the full steps to reproduce for me:
Flutter channel master, 1.20.0-1.0.pre.217, on Microsoft Windows
Dart version 2.9.0 (build 2.9.0-19.0.dev a9bef090e8)

Steps

Android Studio → New Flutter Project → Flutter Application
Project name: flutter_app
Create analysis_options.yaml:

analyzer:
  enable-experiment:
    - non-nullable

Add sdk constraint:

environment:
  sdk: ">=2.9.0-19.0.dev <3.0.0"

Pub get
Rerun Dart analysis → make sure that key and title in the constructor are reported as errors (non-nullable)
Replace the content of main.dart with the following:

import 'package:flutter/material.dart';
import 'package:flutterapp/widgets/one.dart';
import 'package:flutterapp/widgets/two.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatefulWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  _MyAppState createState() => _MyAppState();
}

class _MyAppState extends State<MyApp> {
  late bool _enabled;

  @override
  void initState() {
    super.initState();

    _enabled = false;
  }

  Future<void> _handleChange(bool value) async {
    setState(() {
      _enabled = value;
    });
  }

  Widget buildContent() {
    return InkWell(
      onTap: () => _handleChange(!_enabled),
      child: Padding(
        padding: const EdgeInsets.symmetric(
          vertical: 8,
          horizontal: 16,
        ),
        child: Row(
          children: [
            Text('Some'),
            Text('Text'),
          ],
        ),
      ),
    );
  }

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: Column(
          crossAxisAlignment: CrossAxisAlignment.start,
          children: [
            buildContent(),
            const Divider(
              thickness: 1,
              height: 1,
            ),
            Expanded(
              child: _enabled ? const One() : const Two(),
            ),
          ],
        ),
      ),
    );
  }
}

Create three files in lib/widgets: one.dart, two.dart, and three.dart → fill them with the following three snippets:

One
import 'package:flutter/material.dart';

class One extends StatelessWidget {
  const One({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return DropdownButtonHideUnderline(
      child: DropdownButton<String>(
        value: '1',
        onChanged: (value) {
          Null;
        },
        items: [
          for (var i = 0; i < 7; i++)
            DropdownMenuItem(
              value: '$i',
              child: Text(
                i.toString().toUpperCase(),
                style: Theme.of(context).textTheme.bodyText1.copyWith(
                      color: Theme.of(context).toggleableActiveColor,
                      fontWeight: FontWeight.bold,
                    ),
              ),
            ),
        ],
      ),
    );
  }
}

Two
import 'package:flutter/material.dart';
import 'package:flutterapp/widgets/one.dart';
import 'package:flutterapp/widgets/three.dart';

class Two extends StatelessWidget {
  const Two({Key? key}) : super(key: key);

  Future<void> _addDialog(BuildContext context) async {
    final String? result = await showDialog<String?>(
      context: context,
      useRootNavigator: false,
      builder: (context) {
        return SimpleDialog(
          children: [
            Padding(
                padding: const EdgeInsets.symmetric(
                  vertical: 8,
                  horizontal: 16,
                ),
                child: IconButton(
                  onPressed: Navigator.of(context).pop,
                  icon: const Icon(Icons.notifications_none),
                )),
          ],
        );
      },
    );

    if (result == null) return;
  }

  @override
  Widget build(BuildContext context) {
    return DragTarget<int>(
      onWillAccept: (data) {
        return true;
      },
      onAccept: (data) {
        return;
      },
      builder: (context, candidateData, rejectedData) {
        return InkWell(
          onTap: () => _addDialog(context),
          child: Stack(
            children: [
              const Three(),
              const ColoredBox(
                color: Colors.blueAccent,
              ),
              const One(),
            ],
          ),
        );
      },
    );
  }
}

Three
import 'package:flutter/material.dart';

class Three extends StatefulWidget {
  const Three({
    Key? key,
    this.delay = const Duration(),
  }) : super(key: key);
  final Duration delay;

  @override
  State createState() => _ThreeState();
}

class _ThreeState extends State<Three> {
  late bool _entered = false;

  void _onEnter(_) {
    setState(() {
      _entered = true;
    });

    Future.delayed(widget.delay, () {
      setState(() {
        _entered = false;
      });
    });
  }

  void _onExit(_) {
    setState(() {
      _entered = false;
    });
  }

  @override
  Widget build(BuildContext context) {
    return MouseRegion(
      onEnter: _onEnter,
      onExit: _onExit,
      child: Text('... what is this widget tree $_entered'),
    );
  }
}

Run the following command: flutter run --enable-experiment=non-nullable --no-sound-null-safety -d chrome
Change the following lines with the ones following that (main.dart 42):

            Text('Some'),
            Text('Text'),

            Text('See'),
            Text('The'),
            Text('Bug'),

Hot reload
I see the following error:

lib/main.dart:64:42: Error: Required named parameter '$creationLocationd_0dea112b090073317d4' must be provided.
              child: _enabled ? const One() : const Two(),
                                         ^
lib/widgets/one.dart:4:9: Context: Found this candidate, but the arguments don't match.
  const One({Key? key}) : super(key: key);
        ^^^
lib/main.dart:64:56: Error: Required named parameter '$creationLocationd_0dea112b090073317d4' must be provided.
              child: _enabled ? const One() : const Two(),
                                                       ^
lib/widgets/two.dart:6:9: Context: Found this candidate, but the arguments don't match.
  const Two({Key? key}) : super(key: key);
        ^^^
Performing hot restart...                                           99ms
Try again after fixing the above error(s).

Cannot build the app until I run flutter clean.

@creativecreatorormaybenot
thanks for the reproducing steps!
I'm changing the title, because I'm experiencing this with Android 9 (API 28) and iOS 13.5 (simulator) as well. Tried with master 1.20.0-3.0.pre.78

/cc @jensjoha - potentially seems like another interaction between widget location transformer and internal CFE state? CFE should not be able to see artificial parameters introduced by the transformer, unless its internal state is restored from the Kernel binary (which does not seem like a correct thing to do?).

/cc @jensjoha - potentially seems like another interaction between widget location transformer and internal CFE state? CFE should not be able to see artificial parameters introduced by the transformer, unless its internal state is restored from the Kernel binary (which does not seem like a correct thing to do?).

I haven't looked into this (yet), but

internal state is restored from kernel binary, and it is the right thing to do. Other transformations for instance removes fields and replaces them with something else. If CFEs internal state doesn't reflect this we cannot produce correct code.
even if we didn't do the above, we can initialize from a previous compiles dill file.

As I said, I haven't looked into the specifics here yet though.
/cc @johnniwinther who might also have input.

If CFEs internal state doesn't reflect this we cannot produce correct code.

Imagine:
class A {
  const A();
}

gets transformed into
class A {
  final someArtificialField;
  A(this.someArtificialField);
}

this is a fine transformation as long as transformer also globally inserts a value into each constructor call.
However if you restore CFE state from the dill which contains transformed code then users will starts seeing errors asking them to add missing value - which is not something they can, because someArtificialField was created by the transformer.
I guess things can be made to work if you use named parameters and make sure that you use nullable types for those parameters (and don't make them required) - I guess you could say that the actual bug is in the widget transformer not respecting this requirement.
In some sense this just high-lights inherent leakiness of transformer abstraction.

For this case it should be enough to change the type of the synthesized location parameter to Location? instead of Location - actually this is even necessary to make the transformed code valid since non-nullable named parameters must either have a default value (which is doesn't) or be required (which it isn't).
I'll update the transformer accordingly.

@johnniwinther So you know why this happens? Is it a trivial fix or will it take some time?

I have a fix in the pipeline: https://dart-review.googlesource.com/c/sdk/+/153085

@johnniwinther Is there anything blocking the fix? I am just curious, no pressure 😄

Waiting for a review from something knowledge of the widget transformer design. Summer time reviews are a bit slower than usual due to vacations.

Just noticed that flutter widget tests break in a similar fashion, does this PR also fix this?

Another note (sorry for extreme lack of detail, I'm trying to work to a deadline as well). The following causes the same errors:
class JteIcon extends StatelessWidget {
  const JteIcon({required this.path, this.size = 30, this.color});

While this doesn't:
class JteIcon extends StatelessWidget {
  JteIcon({required this.path, this.size = 30, this.color});

This is nested in another group of widgets.

Hmm. I get the same error (prior to the fix) for both const and non-const constructors.

Sorry about the lack of detail or any way to generate a repeatable case. I was trying to zip through a few things to get a build happen at that seemed to be one of the blockers - I didn't in any way test thoroughly.
Is there an easy way for me to get flutter using the dart master so I can check my cases a bit better with the fix?

Is there an easy way for me to get flutter using the dart master so I can check my cases a bit better with the fix?

I actually don't know how to do that. @jonahwilliams do you how/if this can be done?

It looks like the last change rolled into the engine as https://github.com/flutter/engine/pull/19838 . I would expect this to roll into the framework some time today - you can always get to the latest flutter with flutter channel master and flutter upgrade.
If you want to build flutter with an arbitrary dart commit, you would need to follow the engine development guide in contributing.md. This is a bit more involved, so it might be easier to wait for it to roll in.

Very cool, got the update now and it looks like all the issues I had were solved nicely :heart:

@creativecreatorormaybenot if you would confirm too I will mark this issue as fixed. Thanks for the fix @johnniwinther

@jonahwilliams Yess, it works 🎉
This is such a time save; thanks @johnniwinther.


test

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

requirements: run: intake>=0.3 must contain a space between the name and the pin, i.e. intake >=0.3
noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >=3.6 in both host and run but you should check upstream for the package's Python compatibility.


Combobox styling in Safari browser

Detailed description

Describe in detail the issue you're having.

Combobox styling in Safari is wrong. Maybe -webkit-appearance: none; missing.

Is this a feature request (new component, new icon), a bug, or a general issue?

Bug

Is this issue related to a specific component?

Combobox

What browser are you working in?

Safari 14.0

What version of the Carbon Design System are you using?

"@carbon/elements": "^10.18.0",
"@carbon/icons-angular": "^11.0.1",
"@carbon/motion": "^10.7.0",
"@carbon/themes": "^10.11.2",
"carbon-components": "^10.19.0",
"carbon-components-angular": "^4.15.1",
Additional information

I can't reproduce the issue in the storybook ... Ensure that you're using the latest version of carbon-components, and that your autoprefixer is configured correctly (Carbon doesn't manually add any vendor specific prefixes).

Since you haven't responded at all in roughly a month, and I can't reproduce this, I'm going to close this.


Update README.md

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hello, thank you for participating in our open-source community. However, I don't think this pull request should be merged with master because it doesn't seem to add any value to this repository.


Create generic decorators and functions for logging

Currently when adding logging we instantiate the ILogger interface, which is fine. However, in some cases performing the instantiation is totally unnecessary and gets in the way of writing tests.
I.e. if we wanted to add logging, then we'd need to modify the tests to account for this new injected class.
Ideally we should have simple functions that we could invoke without having to instantiate anything. I.e. we shouldn't have to modify any code, let alone any tests just to add any cross cutting concerns such as logging.
Summary:

Create decorator for logging
Create a function for logging purposes

Technical details:

The decorator and functions should internally use DI container to instantiate the concrete classes
During testing, these functions should be noops

Benefit:

Cleaner code

Already done


Fix chat completion and docs

What does this PR do?
This PR introduces three improvements to the LoRAX project:

Tokenization API: Inspired by HF TGI, this addition allows users to get tokenization results via a new /tokenize route in the API.

Chat Completion Stream API Fix: The existing implementation had a discrepancy with the official OpenAI API, where the final chunk in a stream erroneously contained null "role" and "content", leading to potential unexpected errors in some OpenAI API clients. This fix ensures that, while the last chunk (is_stop is True) still recognizes "role" and "content" as null, they are not serialized, allowing the final chunk's delta to correctly return as an empty object.

How the last chunk looks like (Before)

{
  "id":"null",
  "object":"chat.completion.chunk",
  "created":0,
  "model":"null",
  "choices":[{
    "index":0,
    "delta":{
      "role":null,
      "content":null
    },
    "finish_reason":"stop"
  }]
}

How the last chunk looks like (After, Equivalent with OpenAI API's behavior)

{
  "id":"null",
  "object":"chat.completion.chunk",
  "created":0,
  "model":"null",
  "choices":[{
    "index":0,
    "delta":{},
    "finish_reason":"stop"
  }]
}

Swagger Docs Improvement: Enhancements were made to the OpenAPI (Swagger) Docs for better usability. The changes include making the OpenAI compatible API visible, tagging the LoRAX standalone APIs, OpenAI compatible APIs, and the newly added Tokenizer for easier differentiation, and adding missing schemas to eliminate errors related to schema unavailability. Before/after screenshots are provided for a clearer comparison.

Before this PR

After

These enhancements not only improve the project's functionality but also its usability and compatibility with existing OpenAI API clients.
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[x] Was this discussed/approved via a Github issue or the discord / slack channel? Please add a link
to it if that's the case.

This PR will fix #356 and also fix #357

[ ] Did you write any new necessary tests?

Who can review?
@tgaddair
I have conducted several tests to ensure the proper functioning of these improvements and applied linting to adhere to coding style and conventions. Despite these precautions, there could still be issues within the code. Please feel free to review and suggest any changes you think might be necessary.
cc. @soeque1

Actually we have found some issues during handling non-ascii unicode characters such as Korean or Japanese text.
Some characters are splitted into several tokens by BPE tokenizer, and the returned text for each tokens are not equal to the token corresponding to the ID.
For example, a single character ⑴ can be usually seen in Japanese corpus, and it is splitted by NFKC normalizer like (, 1, ).
You can see this example and how we fixed it below:

encode API

curl -X 'POST' \
  'http://localhost:8080/tokenize' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
  "inputs": "⑴　抵当権、質権、先取特権及び賃借権、または所有権留保、等の乙の完全なる所有権の行使を妨げる事情がないこと"
}'

[
  { "id": 325, "text": "⑴", "start": 0, "stop": 1 },
  { "id": 28740, "text": "⑴", "start": 0, "stop": 1 },
  { "id": 28731, "text": "⑴", "start": 0, "stop": 1 },
  { "id": 28705, "text": "　", "start": 1, "stop": 2 },
  { "id": 233, "text": "抵", "start": 2, "stop": 3 },
  { "id": 141, "text": "抵", "start": 2, "stop": 3 },
  { "id": 184, "text": "抵", "start": 2, "stop": 3 },
  { "id": 29162, "text": "当", "start": 3, "stop": 4 },
  { "id": 233, "text": "権", "start": 4, "stop": 5 },
  { "id": 171, "text": "権", "start": 4, "stop": 5 },
  { "id": 172, "text": "権", "start": 4, "stop": 5 },
...

Issue cause and workaround

The text used in the old SimpleToken was sliced by the index on the original text for each token returned by tokenizer.encode_char_offsets.
When each token has NFKC normalization applied and the text area is different from the original (e.g., ⑴ -> (1)), the same character is repeated because the index of the original string is referenced.
Instead of slicing text of a SimpleToken from the original text to idx, we use tokenizer.id_to_token(id) to get its token directly from vocab

Existing
let text: String = input.chars().skip(start).take(stop - start).collect();

After the change
let text: String = tokenizer.id_to_token(id).unwrap();

API response changes after change
curl -X 'POST' \
  'http://localhost:8080/tokenize' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
  "inputs": "⑴　抵当権、質権、先取特権及び賃借権、または所有権留保、等の乙の完全なる所有権の行使を妨げる事情がないこと"
}'

[
  { "id": 325, "text": "▁(", "start": 0, "stop": 1 },
  { "id": 28740, "text": "1", "start": 0, "stop": 1 },
  { "id": 28731, "text": ")", "start": 0, "stop": 1 },
  { "id": 28705, "text": "▁", "start": 1, "stop": 2 },
  { "id": 233, "text": "<0xE6>", "start": 2, "stop": 3 },
  { "id": 141, "text": "<0x8A>", "start": 2, "stop": 3 },
  { "id": 184, "text": "<0xB5>", "start": 2, "stop": 3 },
  { "id": 29162, "text": "当", "start": 3, "stop": 4 },
  { "id": 233, "text": "<0xE6>", "start": 4, "stop": 5 },
  { "id": 171, "text": "<0xA8>", "start": 4, "stop": 5 },
  { "id": 172, "text": "<0xA9>", "start": 4, "stop": 5 },
  { "id": 29041, "text": "、", "start": 5, "stop": 6 },
  { "id": 235, "text": "<0xE8>", "start": 6, "stop": 7 },
  { "id": 182, "text": "<0xB3>", "start": 6, "stop": 7 },
  { "id": 173, "text": "<0xAA>", "start": 6, "stop": 7 },
  { "id": 233, "text": "<0xE6>", "start": 7, "stop": 8 },
  { "id": 171, "text": "<0xA8>", "start": 7, "stop": 8 },
  { "id": 172, "text": "<0xA9>", "start": 7, "stop": 8 },
  { "id": 29041, "text": "、", "start": 8, "stop": 9 },
  { "id": 29596, "text": "先", "start": 9, "stop": 10 },
  { "id": 29012, "text": "取", "start": 10, "stop": 11 },
  { "id": 29631, "text": "特", "start": 11, "stop": 12 },
  { "id": 233, "text": "<0xE6>", "start": 12, "stop": 13 },
  { "id": 171, "text": "<0xA8>", "start": 12, "stop": 13 },
  { "id": 172, "text": "<0xA9>", "start": 12, "stop": 13 },
  { "id": 29965, "text": "及", "start": 13, "stop": 14 },
  { "id": 31050, "text": "び", "start": 14, "stop": 15 },
  { "id": 235, "text": "<0xE8>", "start": 15, "stop": 16 },
  { "id": 182, "text": "<0xB3>", "start": 15, "stop": 16 },
  { "id": 134, "text": "<0x83>", "start": 15, "stop": 16 },
  { "id": 31626, "text": "借", "start": 16, "stop": 17 },
  { "id": 233, "text": "<0xE6>", "start": 17, "stop": 18 },
  { "id": 171, "text": "<0xA8>", "start": 17, "stop": 18 },
  { "id": 172, "text": "<0xA9>", "start": 17, "stop": 18 },
  { "id": 29041, "text": "、", "start": 18, "stop": 19 },
  { "id": 29241, "text": "ま", "start": 19, "stop": 20 },
  { "id": 29227, "text": "た", "start": 20, "stop": 21 },
  { "id": 29277, "text": "は", "start": 21, "stop": 22 },
  { "id": 29163, "text": "所", "start": 22, "stop": 23 },
  { "id": 28998, "text": "有", "start": 23, "stop": 24 },
  { "id": 233, "text": "<0xE6>", "start": 24, "stop": 25 },
  { "id": 171, "text": "<0xA8>", "start": 24, "stop": 25 },
  { "id": 172, "text": "<0xA9>", "start": 24, "stop": 25 },
  { "id": 30210, "text": "留", "start": 25, "stop": 26 },
  { "id": 29321, "text": "保", "start": 26, "stop": 27 },
  { "id": 29041, "text": "、", "start": 27, "stop": 28 },
  { "id": 29414, "text": "等", "start": 28, "stop": 29 },
  { "id": 28993, "text": "の", "start": 29, "stop": 30 },
  { "id": 231, "text": "<0xE4>", "start": 30, "stop": 31 },
  { "id": 188, "text": "<0xB9>", "start": 30, "stop": 31 },
  { "id": 156, "text": "<0x99>", "start": 30, "stop": 31 },
  { "id": 28993, "text": "の", "start": 31, "stop": 32 },
  { "id": 29474, "text": "完", "start": 32, "stop": 33 },
  { "id": 29374, "text": "全", "start": 33, "stop": 34 },
  { "id": 29270, "text": "な", "start": 34, "stop": 35 },
  { "id": 29116, "text": "る", "start": 35, "stop": 36 },
  { "id": 29163, "text": "所", "start": 36, "stop": 37 },
  { "id": 28998, "text": "有", "start": 37, "stop": 38 },
  { "id": 233, "text": "<0xE6>", "start": 38, "stop": 39 },
  { "id": 171, "text": "<0xA8>", "start": 38, "stop": 39 },
  { "id": 172, "text": "<0xA9>", "start": 38, "stop": 39 },
  { "id": 28993, "text": "の", "start": 39, "stop": 40 },
  { "id": 29037, "text": "行", "start": 40, "stop": 41 },
  { "id": 29154, "text": "使", "start": 41, "stop": 42 },
  { "id": 29078, "text": "を", "start": 42, "stop": 43 },
  { "id": 232, "text": "<0xE5>", "start": 43, "stop": 44 },
  { "id": 169, "text": "<0xA6>", "start": 43, "stop": 44 },
  { "id": 171, "text": "<0xA8>", "start": 43, "stop": 44 },
  { "id": 31967, "text": "げ", "start": 44, "stop": 45 },
  { "id": 29116, "text": "る", "start": 45, "stop": 46 },
  { "id": 29339, "text": "事", "start": 46, "stop": 47 },
  { "id": 29418, "text": "情", "start": 47, "stop": 48 },
  { "id": 29309, "text": "が", "start": 48, "stop": 49 },
  { "id": 29270, "text": "な", "start": 49, "stop": 50 },
  { "id": 29132, "text": "い", "start": 50, "stop": 51 },
  { "id": 29543, "text": "こ", "start": 51, "stop": 52 },
  { "id": 29316, "text": "と", "start": 52, "stop": 53 }
]

And we can now truncate text to desired token length based on Tokenize result.

After the change, text correctly returns the value of the token itself, but it is sometimes broken into bytes, which is cumbersome to combine with a simple concat.
This can be solved by using the start, stop indexes spit out by the tokenize API without a separate detokenize process.
For example, if you want to slice the original text to within 100 tokens, you can slice it before the start index of the 101st token

# Truncate the original text to 10 tokens or less
text = "⑴　抵当権、質権、先取特権及び賃借権、または所有権留保、等の乙の完全なる所有権の行使を妨げる事情がないこと"
tokens = [{"id":325,"text":"▁(","start":0,"stop":1},{"id":28740,"text":"1","start":0,"stop":1},{"id":28731,"text":")","start":0,"stop":1},{"id":28705,"text":"▁","start":1,"stop":2},{"id":233,"text":"<0xE6>","start":2,"stop":3},{"id":141,"text":"<0x8A>","start":2,"stop":3},{"id":184,"text":"<0xB5>","start":2,"stop":3},{"id":29162,"text":"当","start":3,"stop":4},{"id":233,"text":"<0xE6>","start":4,"stop":5},{"id":171,"text":"<0xA8>","start":4,"stop":5},{"id":172,"text":"<0xA9>","start":4,"stop":5},{"id":29041,"text":"、","start":5,"stop":6},{"id":235,"text":"<0xE8>","start":6,"stop":7},{"id":182,"text":"<0xB3>","start":6,"stop":7},{"id":173,"text":"<0xAA>","start":6,"stop":7},{"id":233,"text":"<0xE6>","start":7,"stop":8},{"id":171,"text":"<0xA8>","start":7,"stop":8},{"id":172,"text":"<0xA9>","start":7,"stop":8},{"id":29041,"text":"、","start":8,"stop":9},{"id":29596,"text":"先","start":9,"stop":10},{"id":29012,"text":"取","start":10,"stop":11},{"id":29631,"text":"特","start":11,"stop":12},{"id":233,"text":"<0xE6>","start":12,"stop":13},{"id":171,"text":"<0xA8>","start":12,"stop":13},{"id":172,"text":"<0xA9>","start":12,"stop":13},{"id":29965,"text":"及","start":13,"stop":14},{"id":31050,"text":"び","start":14,"stop":15},{"id":235,"text":"<0xE8>","start":15,"stop":16},{"id":182,"text":"<0xB3>","start":15,"stop":16},{"id":134,"text":"<0x83>","start":15,"stop":16},{"id":31626,"text":"借","start":16,"stop":17},{"id":233,"text":"<0xE6>","start":17,"stop":18},{"id":171,"text":"<0xA8>","start":17,"stop":18},{"id":172,"text":"<0xA9>","start":17,"stop":18},{"id":29041,"text":"、","start":18,"stop":19},{"id":29241,"text":"ま","start":19,"stop":20},{"id":29227,"text":"た","start":20,"stop":21},{"id":29277,"text":"は","start":21,"stop":22},{"id":29163,"text":"所","start":22,"stop":23},{"id":28998,"text":"有","start":23,"stop":24},{"id":233,"text":"<0xE6>","start":24,"stop":25},{"id":171,"text":"<0xA8>","start":24,"stop":25},{"id":172,"text":"<0xA9>","start":24,"stop":25},{"id":30210,"text":"留","start":25,"stop":26},{"id":29321,"text":"保","start":26,"stop":27},{"id":29041,"text":"、","start":27,"stop":28},{"id":29414,"text":"等","start":28,"stop":29},{"id":28993,"text":"の","start":29,"stop":30},{"id":231,"text":"<0xE4>","start":30,"stop":31},{"id":188,"text":"<0xB9>","start":30,"stop":31},{"id":156,"text":"<0x99>","start":30,"stop":31},{"id":28993,"text":"の","start":31,"stop":32},{"id":29474,"text":"完","start":32,"stop":33},{"id":29374,"text":"全","start":33,"stop":34},{"id":29270,"text":"な","start":34,"stop":35},{"id":29116,"text":"る","start":35,"stop":36},{"id":29163,"text":"所","start":36,"stop":37},{"id":28998,"text":"有","start":37,"stop":38},{"id":233,"text":"<0xE6>","start":38,"stop":39},{"id":171,"text":"<0xA8>","start":38,"stop":39},{"id":172,"text":"<0xA9>","start":38,"stop":39},{"id":28993,"text":"の","start":39,"stop":40},{"id":29037,"text":"行","start":40,"stop":41},{"id":29154,"text":"使","start":41,"stop":42},{"id":29078,"text":"を","start":42,"stop":43},{"id":232,"text":"<0xE5>","start":43,"stop":44},{"id":169,"text":"<0xA6>","start":43,"stop":44},{"id":171,"text":"<0xA8>","start":43,"stop":44},{"id":31967,"text":"げ","start":44,"stop":45},{"id":29116,"text":"る","start":45,"stop":46},{"id":29339,"text":"事","start":46,"stop":47},{"id":29418,"text":"情","start":47,"stop":48},{"id":29309,"text":"が","start":48,"stop":49},{"id":29270,"text":"な","start":49,"stop":50},{"id":29132,"text":"い","start":50,"stop":51},{"id":29543,"text":"こ","start":51,"stop":52},{"id":29316,"text":"と","start":52,"stop":53}]

# truncate to start of 10+1 tokens in case of byte-level splitting
# if 10th and 11th tokens are combined into a single character, discard 10th token
sliced_tokens = tokens[:10+1]
end_idx = sliced_tokens[-1]["start"]
sliced_text = text[:end_idx]

print(text)
# ⑴　抵当権、質権、先取特権及び賃借権、または所有権留保、等の乙の完全なる所有権の行使を妨げる事情がないこと

print(sliced_text)
# ⑴　抵当

Truncated text tokenize result

curl -X 'POST' \
  'http://localhost:8080/tokenize' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
  "inputs": "⑴　抵当"
}'

The 9th, 10th, and 11th tokens, <0xE6> <0xA8> <0xA9>, make up one character "権", so leaving only 8 tokens worth of text

[
  { "id": 325, "text": "▁(", "start": 0, "stop": 1 },
  { "id": 28740, "text": "1", "start": 0, "stop": 1 },
  { "id": 28731, "text": ")", "start": 0, "stop": 1 },
  { "id": 28705, "text": "▁", "start": 1, "stop": 2 },
  { "id": 233, "text": "<0xE6>", "start": 2, "stop": 3 },
  { "id": 141, "text": "<0x8A>", "start": 2, "stop": 3 },
  { "id": 184, "text": "<0xB5>", "start": 2, "stop": 3 },
  { "id": 29162, "text": "当", "start": 3, "stop": 4 }
]

As you mentioned as https://github.com/predibase/lorax/pull/358#discussion_r1538599514, When we receive the result of our tokenization, it's natural that the tokenizer is based on the default plus the special token.
However, some people may want to see the result with add_special_tokens set to false, and we've added this as a parameter to the request.
The default value of add_special_tokens is true(when if it was set to null), and of course you can set it to false and get tokenized result without adding special tokens.

The changed request may look like:
curl -X 'POST' \
  'https://localhost:8080/tokenize' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
  "add_special_tokens": true,
  "inputs": "My name is Olivier and I"
}'

@tgaddair We have found some issues related to this PR and made some commits for it.


[Question]: why fetch the nodes is return None by ResponseMode.NO_TEXT

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
Why does llama return None when response_mode is no_text?
      service_context = create_service_context()         index = self.embedding.load_index_simple(game_id, service_context)         retriever = index.as_retriever(similarity_top_k=15)         engine = RetrieverQueryEngine.from_args(retriever, service_context,                                                 response_mode=ResponseMode.NO_TEXT)
i saw the nodes was print, but it not return

the nodes are in the response object
response = index.as_query_engine(response_mode="no_text").query("query")
print(response.source_nodes)

thank you very much! the document need update ^.^


ERR_TOO_MANY_REDIRECTS. State parameter not saved in database when oauth2 authorization server issues an authorization code to a client

Bug description
I'm not redirected to the client server homepage after I'm successfully authenticated and authorized by the authorization server. More details at Projects behaviour.
To Reproduce
I have implemented an authorization server very similar to the one provided by Spring Documentation, with the following variations:

Maven instead of gradle, as project builder

JRE: jdk1.8.0_xxx

Spring Boot 2.7.12 , Spring Security 5.7.8 , Spring Security oauth2 authorization server 0.4.2 ,

a sql server database to store user's credentials. Here I also implemented the 3 oauth2 tables that, in the Spring demo, are located in an embedded h2 database,

a custom UserDetailsService instead of an InMemoryUserDetailsManager:
@Service
public class CustomUserDetailsService implements UserDetailsService {

    @Autowired
    UserRepository userRepository;

    @Override
    @Transactional
    public UserDetails loadUserByUsername(String email) throws UsernameNotFoundException {
    	Optional<User> user = userRepository.findByEmail(email);

    	User u = user.orElseThrow(() ->
        new UsernameNotFoundException("User not found with email : " + email));

        return SecurityUser.create(u);
    }

}

Here the SecurityUser class:
public class SecurityUser implements OAuth2User, UserDetails {

	@Id
	@GeneratedValue(strategy = GenerationType.IDENTITY)
	private Long id;
	private String username;
	private String password;
	private Collection<? extends GrantedAuthority> authorities;
	private Map<String, Object> attributes;

	public SecurityUser() {}

    public SecurityUser(Long id, String email, String password, Collection<? extends GrantedAuthority> authorities) {
        this.id = id;
        this.username = email;
        this.password = password;
        this.authorities = authorities;
    }

    public static SecurityUser create(User user) {
      List<GrantedAuthority> authorities = Collections.
      singletonList(new SimpleGrantedAuthority("ROLE_USER"));
        return new SecurityUser(
                user.getUser_id(),
                user.getEmail(),
                user.getPwd(),
                authorities
        );
    }

    public static SecurityUser create(User user, Map<String, Object> attributes) {
        SecurityUser userPrincipal = SecurityUser.create(user);
        userPrincipal.setAttributes(attributes);

        return userPrincipal;
    }

// getters and setters

    @Override
    public String toString() {
      return new StringJoiner(", ", SecurityUser.class.getSimpleName() + "[", "]")
          .add("id='" + id + "'")
          .add("username='" + username + "'")
          .add("authorities='" + authorities + "'")
          .add("attributes='" + attributes + "'")
          .toString();
    }
}

Here the SecurityUserMixin class (needed at point n. 7):
@JsonTypeInfo(use = JsonTypeInfo.Id.CLASS)
@JsonDeserialize
@JsonAutoDetect(
        fieldVisibility = JsonAutoDetect.Visibility.ANY,
        getterVisibility = JsonAutoDetect.Visibility.NONE,
        isGetterVisibility = JsonAutoDetect.Visibility.NONE)
@JsonIgnoreProperties(ignoreUnknown = true)
public class SecurityUserMixin {

	@JsonProperty
	private Long id;
  	@JsonProperty
	private String username;
  	@JsonIgnore
  	private String password;
  	@JsonIgnore
  	private String name;
	@JsonProperty
	private Collection<? extends GrantedAuthority> authorities;
  	@JsonProperty
	private Map<String, Object> attributes;

  	 @JsonCreator
  	 public SecurityUserMixin(@JsonProperty("id") Long id,
  			@JsonProperty("username") String username,
  			@JsonProperty("authorities") Collection<? extends GrantedAuthority> authorities,
  			@JsonProperty("attributes") Map<String, Object> attributes) {}

// getters and setters

}

I removed the device flow authentication's logic (as I downgraded the authorization server's version to 0.4.2) from the AuthorizationServerConfig class:
@Bean
@Order(Ordered.HIGHEST_PRECEDENCE)
public SecurityFilterChain authorizationServerSecurityFilterChain(HttpSecurity http) throws Exception {

        OAuth2AuthorizationServerConfigurer authzServerConfigurer = new OAuth2AuthorizationServerConfigurer();

        RequestMatcher endpointsMatcher = authzServerConfigurer.getEndpointsMatcher();

		Function<OidcUserInfoAuthenticationContext, OidcUserInfo> userInfoMapper = (context) -> {
			OidcUserInfoAuthenticationToken authentication = context.getAuthentication();
			JwtAuthenticationToken principal = (JwtAuthenticationToken) authentication.getPrincipal();
			return new OidcUserInfo(principal.getToken().getClaims());
		};

        authzServerConfigurer
        	.authorizationEndpoint(authzEndpoint -> authzEndpoint
                .consentPage(CUSTOM_CONSENT_PAGE_URI))
        	.oidc(oidc -> oidc
        			.userInfoEndpoint(userInfo -> userInfo
        					.userInfoMapper(userInfoMapper)
						)
		);

		http
			.requestMatcher(endpointsMatcher)
			.authorizeHttpRequests((authorize) -> authorize
				.antMatchers(CUSTOM_LOGIN_PAGE_URI).permitAll()
				.anyRequest().authenticated()
			)
			.csrf(csrf -> csrf.ignoringRequestMatchers(endpointsMatcher))
			.exceptionHandling(exceptions -> exceptions
				.defaultAuthenticationEntryPointFor(
					new LoginUrlAuthenticationEntryPoint(CUSTOM_LOGIN_PAGE_URI),
					new MediaTypeRequestMatcher(MediaType.TEXT_HTML)
				)
			)
			.oauth2ResourceServer(resourceServer -> resourceServer
				.jwt(Customizer.withDefaults())
			)
		.apply(authzServerConfigurer);

		return http.build();
	}

As result (and since I applied my own OAuth2TokenCustomizer method), these classes are not included in my project anymore:

FederatedIdentityIdTokenCustomizer

UserRepositoryOauth2UserHandler

DeviceClientAuthenticationProvider

DeviceClientAuthenticationToken

DeviceController

DeviceClientAuthenticationConverter

I modified the Oauth2AuthorizationService method since I had to resolve the issue n. 397:
	@Bean
    public OAuth2AuthorizationService authorizationService(JdbcTemplate jdbcTemplate,
                                                           RegisteredClientRepository registeredClientRepository) {
        JdbcOAuth2AuthorizationService authorizationService =
                new JdbcOAuth2AuthorizationService(jdbcTemplate, registeredClientRepository);
        JdbcOAuth2AuthorizationService.OAuth2AuthorizationRowMapper rowMapper =
                new JdbcOAuth2AuthorizationService.OAuth2AuthorizationRowMapper(registeredClientRepository);
        JdbcOAuth2AuthorizationService.OAuth2AuthorizationParametersMapper oAuth2AuthorizationParametersMapper =
                new JdbcOAuth2AuthorizationService.OAuth2AuthorizationParametersMapper();

        ObjectMapper objectMapper = new ObjectMapper();
        ClassLoader classLoader = JdbcOAuth2AuthorizationService.class.getClassLoader();
        List<Module> securityModules = SecurityJackson2Modules.getModules(classLoader);
        objectMapper.registerModules(securityModules);
        objectMapper.registerModule(new OAuth2AuthorizationServerJackson2Module());
        objectMapper.addMixIn(SecurityUser.class, SecurityUserMixin.class);

        rowMapper.setObjectMapper(objectMapper);
        oAuth2AuthorizationParametersMapper.setObjectMapper(objectMapper);

        authorizationService.setAuthorizationRowMapper(rowMapper);
        authorizationService.setAuthorizationParametersMapper(oAuth2AuthorizationParametersMapper);

        return authorizationService;
        // replace:
//        return new JdbcOAuth2AuthorizationService(jdbcTemplate, registeredClientRepository);
    }

All other classes of the authorization not mentioned are left unchanged from Spring's ones.
Then I implemented a resource server (built with Maven) and a client server (built with Gradle). Both are very similar to those of Spring, but, in the client, I remove device flow authentication logic.
To implement the 3 oauth2 tables I used the default sql scripts for this  authorization server version, but I replaced every blob type column with varchar and every timestamp type column with datetime.
To build the authorization server and the resource server I used this maven build command: spring-boot:run.
Projects behaviour and error:
All 3 projects build up correctly, and the registered client configured in my authorization server is saved in the oauth2_registered_client table.
Via browser, I try to access the client server homepage and I'm (correctly) redirected to the authorization server. Here I authenticate with the credentials of a previously registered user, and I'm redirected to the consent page. If I check the database queries in the project logs I see an INSERT INTO oauth2_authorization table query, with a state value, but, if I check the table on the database, no records are available.
In the consent page, the only consent available is profile and after I select that and submit the form, the authorization server goes in a loop where it continues to issue new authorization codes, one every second, and on the browser I get the ERR_TOO_MANY_REDIRECTS error.
In the project's logs (logging.level.org.springframework.security: TRACE) I see no errors: after the GET and POST /oauth2/authorize, the POST oauth2/token, the GET /oauth2/jwks and the GET /userinfo requests, the projects starts again to secure the GET /oauth2/authorize with a different authorization code (and state value!) from the same previous GET.
On the network tab on DevTools, I see some redirects to ...login/code/messaging-client-oidc with different authorization codes and state values, I stop the loading of the page (as I know that would generate the error I mentioned), and if I check the oauth2_authorization table on my database I see a bunch of records with different authorization codes but everyone with a NULL state.
However, If I try to reach one of my resource server endpoints via Postman, the authentication and authorization flow works and I get an access_token after I select the consents required. But still, no state value is saved in the record on the oauth2_authorization table.
Apart from this, if I stopped my authorization server and I plug the Spring one, the authorization flow works perfectly and I'm redirect to the client homepage as expected.
Expected behavior
After I select the profile consent via browser, I should be redirected to the client server homepage, and I should only have one record on the oauth2_authorization table with a valid state value.

To sum up:

Can someone explain why, if I use the authorization server provided by Spring instead of my custom authorization server everything seems to work correctly, as I get redirect to the client after the login and the consent selection?
Did I miss something downgrading the authorization server project to a version of oauth2-authorization-server dependency without the device flow authentication? Beside this change and my own token customizer, I only used a sql server database instead of an embedded database, so I don't get why the authorization flow is not working just with my custom authorization server.
In which class does the authorization server provided by Spring explictly save the state parameter in the oauth2_authorization table? Could it be in the AuthorizationConsentController?
Could someone please explain how does it work the "state" and "nonce" checking in the oauth2 authorization code flow or suggest me where I can find understandable documentation ?

Please, note that citation of sources for each of the answers is very welcome.

Sorry, I saw n. 1314 issue comment you guys made about not cross post question between StackOverflow and GitHub.
If someone has already see that post, please feel free to close this issue and answer right there.
Sorry again but I'm still new to Github so I'm not familiar on what the terms of use are.

I have also created a dead cycle, but I have solved it, and I believe you should have the same problem as me.
In the demo-authorization-server, it defines a UserDetailService in the DefaultSecurityConfig. Therefore, if you redefine another UserDetailService in the AuthorizationServerConfig or elsewhere, you will encounter a life and death loop, infinite redirection problem, because there are two similar authentications, which actually makes the authentication unsuccessful Therefore, if you need to customize UserDetailService, please remove the DefaultSecurityConfig first

@zhangpan-soft In my case, the problem was different: the access token generated by my authorization server had a "sub" claim value different from the "sub" claim of the token id, as suggested by @sjohnr . For more details on my error I refer you to this comment on Stackoverflow.


Adding Brazilian Cities/States to presets.go

Description:
In this pull request, I have expanded the presets.go file to include additional cities and states from Brazil. The aim is to enhance the coverage of Brazilian locations.
Changes Made:

Added new Brazilian cities to the existing list in the presets.go file.

Why This Change:
Include more people's.
Checklist:

[x] New cities and states added.

Closing Notes:
Please let me know if there are any further improvements or changes needed. Thank you for your attention to this enhancement.

Thanks for the contribution, @isyuricunha!

The updated rankings have been pushed via 57ebf2c1dc39e48a52204b3a2e65b1aba3db7e69.


Specify gpu_id for cog predict jobs

It would be awesome if there was a simple flag to set the gpu_id to be used for cog (on a machine with multiple gpu's)
eg
cog predict -i prompt="text input" -i cuda_id=0
setting export CUDA_VISIBLE_DEVICES=1 first in the terminal does not work as docker ignores it.
There's this way to do it, but it's so cumbersome...

Agreed: https://github.com/replicate/cog/pull/1334

@aiXander This is now in a prerelease version! https://github.com/replicate/cog/releases/tag/v0.9.0-beta7


move_by freezer method

We currently have freezer.move_to. It would be nice if we could advance time by a relative increment.
Example:
freezer.move_by('2 hours')

I think you can already do that with tick(timedelta(hours=2)), see https://github.com/spulec/freezegun#manual-ticks.

Nice thanks!


Rename master branch name to main

I renamed the default branch to main from this repository's /settings/branches.
And this setting UI tells me to update your repository settings by these steps:
git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a

CI has been changed https://github.com/karen-irc/option-t/pull/1147

I tried to release https://github.com/karen-irc/option-t/releases/tag/v29.0.1
I seem there is no problem.


chore: change author name in Order/KrullDimesnion

Yeah, I spelled his name wrong, sorry about this. 😅


Refactor Clean and Init tasks, move linking jobs to run in the background

Description
This PR refactors some of the tasks. The goal is to reduce the number of jobs to be submitted, hence, computing and waiting time for the each cycle. Clean tasks are removed and the content is moved to their associated application tasks (e.g., CleanHofX content is moved to HofX.csh). InitVariationals.csh and InitEnKF.csh scripts for the YAML and model stage preparation stage are also removed and their content is moved to PrepJEDI.csh (only one preparation task is submitted). For RTPP, Clean and Init tasks and both removed and merged with RTPP.csh. Here, the LinkExternalAnalysis and LinkWarmStartBackgrounds tasks are set to run in the background instead of Casper. These tasks use very little memory and wall-time, then running them in the background should be fine (but let's monitor that).
Issue closed
None
Tests completed
Tier 1:

[ ] 3dvar_OIE120km_WarmStart
[ ] 3denvar_OIE120km_IAU_WarmStart
[x] 3dvar_OIE120km_ColdStart
[ ] 3dvar_O30kmIE60km_ColdStart
[x] 3denvar_O30kmIE60km_WarmStart
[x] eda_OIE120km_WarmStart
[x] getkf_OIE120km_WarmStart
[x] 4dhybrid_OIE120km_WarmStart
[ ] ForecastFromGFSAnalysesMPT

good job! @ibanos90

good job! @ibanos90

Thanks @mos3r3n!

Now it works for scenarios/3dhybrid-allsky_O30kmIE60km_SpecifiedEnsemble_VarBC.yaml. Many thanks @ibanos90 !

Thanks a lot for the thorough review @junmeiban!


Fixed typos fixed at multiple places.

Describe the changes you have made in this PR
Fixed typos fixed at multiple places in the app.
For eg see below it should be Entertainment and not Entertaiment.

Link this PR to an issue [optional]
Fixes #ISSUE-NUMBER
Type of change
(Remove other not matching type)

fix: Bug fix (non-breaking change which fixes an issue)
feat: New feature (non-breaking change which adds functionality)
feat!: Breaking change (fix or feature that would cause existing functionality to not work as expected)
docs: Documentation update

Screenshots of the changes [optional]
Add screenshots to make your changes easier to understand. You can also add a video here.
How has this been tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist

[x] My code follows the style guidelines of this project and performed a self-review of my own code
[x] New and existing tests pass locally with my changes
[x] I checked if I need to make corresponding changes to the documentation (and made those changes if needed)

Thank you @reneaaron have fixed all the files.


Support for nest v10

Hi,
Cool project!
Are there any plans in supporting nest v10?
Thanks

Hi, sure will be done soon!

Hi there, how soon??

On this weekend

Done #33

Thanks so much for your contributions to the community
El dom, 3 de sept de 2023, 08:47, Pavel Fedyukovich <
@.***> escribió:

Done #33
https://github.com/p-fedyukovich/nestjs-google-pubsub-microservice/pull/33
—
Reply to this email directly, view it on GitHub
https://github.com/p-fedyukovich/nestjs-google-pubsub-microservice/issues/31#issuecomment-1704311285,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHD4X5SY4MK3J4KLDPR75BTXYSC55ANCNFSM6AAAAAA3IGIMFM
.
You are receiving this because you commented.Message ID:
<p-fedyukovich/nestjs-google-pubsub-microservice/issues/31/1704311285@
github.com>


Fix google tag manager snippet in wrong position (#80).

Add possibility to render snippets in different positions.

Thanks a lot for your Pull Request. and sorry again that it took soooo long to look at this and get a new version out.
The PR was super valuable but we have changed the logic a bit and introduced a new method on the handler that allows the handler to directly manipulate the html response. This gives the handlers more flexibility for cases like the google tag manager requirements.
https://github.com/railslove/rack-tracker/pull/84
The google tag manager is updated for that.
What do you think about that? Hope that helps? Are you still using rack-tracker?


Support angle brackets

This should be a valid link:
[Some link](<path to file with spaces.md>)

(This example is directly from latest VS Code release notes.)

Sorry for quite a delay. This is fixed in 0.4.0.
Also note that I have no intentions to actively support this project, more information provided at the top of the readme.


fix: ColorTokenTable sticky content switcher

Closes #1302
Fixes the sticky content switcher on the Guidelines > Color > Usage page

Hey! Just a quick reminder to stick to the assigned codeowner reviewers for PRs 👀   Totally fair to add in additional reviewers but it's important that we keep the assigned codeowners in there as well, really just so the branch isn't blocked from merging because of the codeowners requirement 👍

Hey @joshblack thanks for the review. I removed some of the reviewers since this issue was assigned to Aux by Mike (which probably wasn't the best thing to do considering System squad works on the site) and requested review from the Aux devs. I also requested review from Jeannie and Anna so I figured that their approval would allow us to merge bc they're part of system squad. I think going forward, we're gonna be talking to Mike to no longer assign us carbon-website issues since System squad is owning that. It just gets confusing trying to figure out what team is taking care of what.

+1 to @jnm2377 Mike has still been assigning issues to aux specifically causing confusion since codeowners tags system not aux, moving forward Carbon website issues should be brought up and prioritized in system squad sprints.

@jnm2377 totally makes sense!


🚀 feat: links for chapter navigations

Merging this as it is a minor change, Feel free to let me know if you see anything wrong :)


Unable to install pyross - error: Unable to find vcvarsall.bat

Hello
I am encountering this error when attempting to install pyross: error: Unable to find vcvarsall.bat. I have cloned the repository from github but I cannot seem to run the last command: python setup.py install.
Thanks,
Aniruddha

@anisengupta  are you running it on Windows? We are aware that our compilation is having some issues with Windows. Please can I suggest to use binder () while we fix the problem specific to Windows?
Please click on the Binder link in the README.md. Please be patient while it loads but after that, there is no difference in running from your own computer.

Hi @rajeshrinet, yes I am running it on Windows, ive tried to relevant batchfile and install a separate c++ compiler but I have had no such luck yet. I will use binder in the meantime, thanks so much.

Thanks.

There is now a solution for the above problems at https://github.com/rajeshrinet/pyross/issues/14

Hi Rajesh
Thanks so much, I will try implementing this and performing my own analysis. I just wanted to say that your paper was fantastic and I thoroughly enjoyed reading it. I thought it was very informative and the illustrations were very clear in outlining the effect that the lockdown the Indian goverment is imposing.
Thanks,
Aniruddha

Hi Aniruddha
Thanks very much for your kind words. We very much appreciate it.
Best wishes,
Rajesh

Hi Rajesh
I am trying to run my own anlaysis on the UK using Pyross, I have selected all the contact matrices to include UK data as well as use UK population and age classes:

I also saw that you don't have case data for the UK, so I have imported a JSON file from the European Center for Disease Control instead. The forecast I get however is minuscule to the real number of covid-19 cases in the UK:

Do you know why this might be? What others factors do I need to change to simulate your analysis but on the UK?
Thanks,
Aniruddha

Hi Aniruddha
Thanks for the explanation. I think a larger value of beta is needed for the UK data. It is possible to find an optimal beta automatically as shown in this example.
To use this in your case, you will have to replace the lines which point to the Indian data and update it to point to the UK data. In principle, the simulation should fit the data when available and then forecast for the unseen scenario. Hope this helps.
Best,
Rajesh

Hi Rajesh
Hope that you are well.
I am currently trying to implement the age structured SIR model for the UK and there are a couple of problems I wanted to flag by you to get your thoughts. Firstly, I used the UK data to find the value of beta which turns out to smaller than the Indian one. This make sense since beta is the infection rate which should be much smaller for the UK since its less densely populated than India. However, you said that a larger value of beta is needed, why would this be the case?
I also noticed that for the contact matrices for the UK, the matrix of total contacts only has an index upto 14, so I have had to change the number of age classes (M) to 14. This however, gives me a reproduction rate that is suspiciously low:

When I then simulated the model for the UK, plotting it along with UK case data. I was seeing that the model was not at all capturing the number of cases so far seen in the UK. Closer inspection revealed that the model was predicting a reverse exponential of the number of cases in the UK, with the number of cases being much too low:

Do you know why this would be the case? Will I need to change the contact matrix data for the UK?
Appreciate your help on this matter again and hope that you and your family are safe during these uncertain times,
Aniruddha

Hi Aniruddha
Sorry for the tardy reply. This example maybe helpful. In particular, it shows how to get the 16x16 contact matrix for UK.
I also extend my best wishes to you,
Rajesh

Hi Rajesh
Hope that you are well.
I have done some work now on trying to utilise your SIR model onto UK data. The results can be found here: https://github.com/anisengupta/SIR-analysis-on-Covid-19. I stressed in the description that this work is entirely credited to yourself and R Adhikari and all I simply did was to point the model towards the UK data.
The results I found were similar to your findings for India; one lockdown is insufficient and a series of lockdowns looks to be most effective in order to take pressure off the NHS. I have only used March data and again I stress, this was something done just in my spare time and is in no way, a comprehensive analysis on trying to model the scale of the epidemic in the UK.
It would be interesting to get your thoughts on this and the models and predictions are only rough as I have used much of the same parameters you did for your Indian analysis.
Thanks and have a good weekend,
Aniruddha


Use recommended node layout

This does not appear to use the recommended node layout as stated in the README.
The recommended layout separates ingestion nodes from client/data nodes, and it does not separate client and data nodes -- the nodes receiving query traffic are the same nodes that have data.

Well, you are most probably right. This repo comes from a different time. I'm happy to review PRs.


Submission Group 139: 2212046_2211740_2310717_2320010_2213144

1. A brief description of your policy
Best Fit Decreasing
Sort the list of products in descending order based on their area (width × height). Iterate through the sorted list and place each product in the position within the current stock that leaves the least remaining space (best fit). Products may be rotated to optimize space utilization. After placing a product, update the available space in the stock to reflect the new placement, ensuring no overlap occurs.
Random
Randomly choose a product from the list of available products that still need to be placed. Select a random position within the current stock to attempt placing the chosen product. If the product does not fit at the selected position, retry with a different position or select another product. Attempt to place the product at the chosen position, considering possible rotations. If placement is successful, update the stock layout accordingly; otherwise, continue the process until all products are placed or no suitable positions remain.
2. Result

Policy
Avg Filled Ratio
Avg Trim Lost

Best Fit Decreasing
0.19
0.25

Random
0.45
0.65

Explaination:
Best Fit Decreasing (BFD) Algorithm: Achieves a low trim_lost ratio while maintaining excellent processing time. It is highly efficient and competitive, making it suitable for models with large quantities.
Random Algorithm: Results in a high trim_lost ratio but compensates with very short processing time. Its performance is subpar, making it only suitable for models with small quantities.
3. Contributions

Team Member
ID
Contribution

Lê Nhật Minh
2212046
Algorithm implementation

Lưu Chấn Kiến
2211740
Report

Võ Thanh Đạt
2310717
Find case study

Đỗ Quý
2320010
Find algorithm

Nguyễn Việt Thành
2213144
Report

1. A brief description of your policy
Best Fit Decreasing
Sort the list of products in descending order based on their area (width × height). Iterate through the sorted list and place each product in the position within the current stock that leaves the least remaining space (best fit). Products may be rotated to optimize space utilization. After placing a product, update the available space in the stock to reflect the new placement, ensuring no overlap occurs.
Random
Randomly choose a product from the list of available products that still need to be placed. Select a random position within the current stock to attempt placing the chosen product. If the product does not fit at the selected position, retry with a different position or select another product. Attempt to place the product at the chosen position, considering possible rotations. If placement is successful, update the stock layout accordingly; otherwise, continue the process until all products are placed or no suitable positions remain.
2. Result

Policy
Avg Filled Ratio
Avg Trim Lost

Best Fit Decreasing
0.19
0.25

Random
0.45
0.65

Explaination:
Best Fit Decreasing (BFD) Algorithm: Achieves a low trim_lost ratio while maintaining excellent processing time. It is highly efficient and competitive, making it suitable for models with large quantities.
Random Algorithm: Results in a high trim_lost ratio but compensates with very short processing time. Its performance is subpar, making it only suitable for models with small quantities.
3. Contributions

Team Member
ID
Contribution

Lê Nhật Minh
2212046
Algorithm implementation

Lưu Chấn Kiến
2211740
Report

Võ Thanh Đạt
2310717
Find case study

Đỗ Quý
2320010
Find algorithm

Nguyễn Việt Thành
2213144
Report

Please revise the PR in Dec 16. Otherwise, your group will get 0 score for code.

Last chance to revise the PR until the end of Dec 17.

Close PR as it does not comply with submission instructions.

I sincerely apologize, Mr. @martinakaduc, for not regularly checking the Pull Request conversations.
I have rearranged the location of the file requirements.txt to ensure it complies.
Over the past week, I was solely focused on final exams and did not pay attention to this issue. Today, when I checked, it was already past the deadline. Additionally, all the members of my group are studying Computer Engineering (CE) and do not have prior experience using GitHub, which led to this situation. Could you please extend the deadline so that my group can submit the Pull Request? My group fully accepts the possibility of being penalized for the late submission as long as we do not receive a score of zero for this part.


Kernel modules headers archive switch to gzip

Connects to #320

LGTM

Please rebase this today so we can merge it.
Thanks


Set the inlineSources tsconfig setting to true

Summary
This adds the inlineSources setting in tsconfig (see https://www.typescriptlang.org/tsconfig#inlineSources)
Details
Fixes #2039.
Types of changes

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

Checklist:

[ ] The change has been ported to Java.
[ ] The change has been ported to Ruby.
[x] The change has been ported to JavaScript.
[ ] The change has been ported to Go.
[ ] The change has been ported to .NET.
[ ] I've added tests for my code.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have updated the CHANGELOG accordingly.

@davidjgoss do you agree this is the right option vs the alternative suggested in #2039? I don't have enough context to have a strong opinion.
Should we be doing this across the board in our TypeScript codebases?

@mattwynne yep this is the best way IMO. It’s what we do in cucumber-js. Only time I’d recommend externalised source maps would be doing a browser bundle.

Thanks @EnoahNetzach!

@aurelien-reeves this will need to be ported to the new repo as part of #2029

Thanks to you all!


[Flaky test] Champion_BasicCheckpointing

Champion_BasicCheckpointing

Result Details
Failed 7h ago on 76d1bd8bc000000
Duration0:00:01.123
Ownernot available
Date started5/20/2021, 1:24:22 AM
Date completed5/20/2021, 1:24:23 AM
Failing since7h ago
Failing since build20210520.1

Debug

Work items

Attachments

History

Attachments*

Error message
Expected: 489
But was:  1001

Stack trace
   at Azure.Search.Documents.Tests.BatchingTests.<Champion_BasicCheckpointing>d__17.MoveNext() in D:\a\_work\1\s\sdk\search\Azure.Search.Documents\tests\Batching\BatchingTests.cs:line 394
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Azure.Search.Documents.Tests.BatchingTests.<Champion_BasicCheckpointing>d__17.MoveNext() in D:\a\_work\1\s\sdk\search\Azure.Search.Documents\tests\Batching\BatchingTests.cs:line 395
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Azure.Search.Documents.Tests.BatchingTests.<Champion_BasicCheckpointing>d__17.MoveNext() in D:\a\_work\1\s\sdk\search\Azure.Search.Documents\tests\Batching\BatchingTests.cs:line 395
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at NUnit.Framework.Internal.TaskAwaitAdapter.GenericAdapter`1.BlockUntilCompleted()

@pakrym - I don't see any failures of Champion_BasicCheckpointing either in the Core or Search CI pipeline. Where I can get the link to a run with a failure of this test?

I'll make sure to add it next time.

Closing for now. Will reopen if there are additional reports of this test failing.

https://dev.azure.com/azure-sdk/internal/_test/analytics?definitionId=1180&contextType=build

Thanks, I favorited the Core and Search pipelines. I see there are public and internal pipelines.
Based on your comments in #21515, I am reopening this.

https://dev.azure.com/azure-sdk/public/_build/results?buildId=945668&view=ms.vss-test-web.build-test-results-tab&runId=20253758&resultId=112091&paneView=debug
Champion_BasicCheckpointing

Result Details
Failed 26m ago on 55e25914c000003
Duration0:00:01.253
Ownernot available
Date started6/14/2021, 9:38:19 AM
Date completed6/14/2021, 9:38:21 AM
Failing since26m ago
Failing since build20210614.1

Debug

Work items

Attachments

History

Attachments*

Error message
Expected: 489
But was:  707

Stack trace
   at Azure.Search.Documents.Tests.BatchingTests.Champion_BasicCheckpointing() in D:\a\_work\1\s\sdk\search\Azure.Search.Documents\tests\Batching\BatchingTests.cs:line 392
   at Azure.Search.Documents.Tests.BatchingTests.Champion_BasicCheckpointing() in D:\a\_work\1\s\sdk\search\Azure.Search.Documents\tests\Batching\BatchingTests.cs:line 395
   at Azure.Search.Documents.Tests.BatchingTests.Champion_BasicCheckpointing() in D:\a\_work\1\s\sdk\search\Azure.Search.Documents\tests\Batching\BatchingTests.cs:line 395
   at NUnit.Framework.Internal.TaskAwaitAdapter.GenericAdapter`1.BlockUntilCompleted()
   at NUnit.Framework.Internal.MessagePumpStrategy.NoMessagePumpStrategy.WaitForCompletion(AwaitAdapter awaiter)
   at NUnit.Framework.Internal.AsyncToSyncAdapter.Await(Func`1 invoke)
   at NUnit.Framework.Internal.Commands.TestMethodCommand.RunTestMethod(TestExecutionContext context)
   at NUnit.Framework.Internal.Commands.TestMethodCommand.Execute(TestExecutionContext context)
   at NUnit.Framework.Internal.Commands.BeforeAndAfterTestCommand.<>c__DisplayClass1_0.<Execute>b__0()
   at NUnit.Framework.Internal.Commands.BeforeAndAfterTestCommand.RunTestMethodInThreadAbortSafeZone(TestExecutionContext context, Action action)


Metadata API request failed: read ECONNRESET

Summary
Running sfdx force:source:retrieve ended with "Error: read ECONNRESET"
Steps To Reproduce:

Execute - sfdx force:source:retrieve -x ./manifest/PACKAGE_FILES/Reports_package.xml

Expected result
All reports in the package.xml file retrieved from the sandbox.
Actual result
Error: read ECONNRESET
at TLSWrap.onStreamRead (internal/stream_base_commons.js:209:20) {
errno: -4077,
code: 'ECONNRESET',
syscall: 'read'
}
ERROR running force:source:retrieve:  Metadata API request failed: read ECONNRESET
System Information
{
"cliVersion": "sfdx-cli/7.116.2",
"architecture": "win32-x64",
"nodeVersion": "node-v14.17.5",
"pluginVersions": [
"@oclif/plugin-autocomplete 0.3.0 (core)",
"@oclif/plugin-commands 1.3.0 (core)",
"@oclif/plugin-help 3.2.2 (core)",
"@oclif/plugin-not-found 1.2.4 (core)",
"@oclif/plugin-plugins 1.10.1 (core)",
"@oclif/plugin-update 1.4.0-3 (core)",
"@oclif/plugin-warn-if-update-available 1.7.0 (core)",
"@oclif/plugin-which 1.0.3 (core)",
"@salesforce/sfdx-plugin-lwc-test 0.1.7 (core)",
"@salesforce/sfdx-trust 3.6.0 (core)",
"alias 1.1.10 (core)",
"apex 0.2.8 (core)",
"auth 1.7.1 (core)",
"config 1.2.24 (core)",
"custom-metadata 1.0.12 (core)",
"data 0.6.1 (core)",
"generator 1.1.7 (core)",
"limits 1.2.1 (core)",
"org 1.7.0 (core)",
"salesforce-alm 52.3.1 (core)",
"schema 1.0.8 (core)",
"sfdx-cli 7.116.2 (core)",
"source 1.0.12 (core)",
"telemetry 1.2.3 (core)",
"templates 52.1.0 (core)",
"user 1.4.0 (core)"
],
"osVersion": "Windows_NT 10.0.18363"
}
Additional information
sfdx plugins --core
@oclif/plugin-autocomplete 0.3.0 (core)
@oclif/plugin-commands 1.3.0 (core)
@oclif/plugin-help 3.2.2 (core)
@oclif/plugin-not-found 1.2.4 (core)
@oclif/plugin-plugins 1.10.1 (core)
@oclif/plugin-update 1.4.0-3 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-plugin-lwc-test 0.1.7 (core)
@salesforce/sfdx-trust 3.6.0 (core)
alias 1.1.10 (core)
apex 0.2.8 (core)
auth 1.7.1 (core)
config 1.2.24 (core)
custom-metadata 1.0.12 (core)
data 0.6.1 (core)
generator 1.1.7 (core)
limits 1.2.1 (core)
org 1.7.0 (core)
salesforce-alm 52.3.1 (core)
schema 1.0.8 (core)
sfdx-cli 7.116.2 (core)
source 1.0.12 (core)
telemetry 1.2.3 (core)
templates 52.1.0 (core)
user 1.4.0 (core)

I got the similar error today 3 times in a row.
C:\GIT_REPOS\ENERGY_SFDX>sfdx force:source:retrieve -x ./manifest/PACKAGE_FILES/Reports_package.xml
Error: socket hang up
at connResetException (internal/errors.js:628:14)
at TLSSocket.socketOnEnd (_http_client.js:499:23)
at TLSSocket.emit (events.js:412:35)
at endReadableNT (internal/streams/readable.js:1317:12)
at processTicksAndRejections (internal/process/task_queues.js:82:21) {
code: 'ECONNRESET'
}
ERROR running force:source:retrieve:  Metadata API request failed: socket hang up

I am encoutering similar issues here also using a package.xml. But I'm getting the issues for deployment.
Version info
@oclif/plugin-autocomplete 0.3.0 (core)
@oclif/plugin-commands 1.3.0 (core)
@oclif/plugin-help 3.2.4 (core)
@oclif/plugin-not-found 1.2.4 (core)
@oclif/plugin-plugins 1.10.1 (core)
@oclif/plugin-update 1.5.0 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-plugin-lwc-test 0.1.7 (core)
alias 1.1.22 (core)
apex 0.3.0 (core)
auth 1.7.5 (core)
config 1.2.41 (core)
custom-metadata 1.0.12 (core)
data 0.6.4 (core)
generator 1.2.1 (core)
limits 1.2.2 (core)
org 1.9.0 (core)
salesforce-alm 53.1.2 (core)
schema 1.0.10 (core)
sfdx-cli 7.125.0 (core)
sfdx-git-delta 4.9.1
source 1.3.1 (core)
telemetry 1.2.8 (core)
templates 52.4.0 (core)
trust 1.0.11 (core)
user 1.5.2 (core)
Additional Info
Error: socket hang up
at connResetException (internal/errors.js:628:14)
at TLSSocket.socketOnEnd (_http_client.js:499:23)
at TLSSocket.emit (events.js:412:35)
at endReadableNT (internal/streams/readable.js:1317:12)
at processTicksAndRejections (internal/process/task_queues.js:82:21) {
code: 'ECONNRESET'
}

This is the error you'll see with network connection interruptions server hangups and as long as the CLI returns an exit code of non-zero it is behaving as expected.
The only thing the CLI can do is introduce retry logic when this happens.  We have an item in our backlog to address this but it's not a simple feature and requires multiple low-level libraries being swapped out.

Hello, it would be nice if the retry functionality is included in the tool. In recent weeks I have seen this message appear more often in combination with sfdx force:source:deploy within our ci-cd environment.

We see this happening daily on our build environment on Azure Devops.

Same thing here, I can see this error multiple time a day

We are also seeing this in our CI/CD.

UPDATE:
Upon connection errors the most recent CLI (7.135.0) will retry for these commands:

force:source:deploy
force:source:deploy:report
force:source:retrieve
force:source:beta:push
force:source:beta:pull
force:mdapi:beta:deploy
force:mdapi:beta:deploy:report
force:mdapi:beta:retrieve
force:mdapi:beta:retrieve:report
force:org:beta:create (in the release candidate available later today, 1/27/2022)

Please try the beta commands as they will soon have the beta topic removed and the non-beta versions will have a legacy topic added.

Closing--this is resolved in the new versions of these commands.


4.03+flambda: foo.cmt is not a compiled interface

I keep getting this error when looking up in other files. The files definitely exist and I cleaned before rebuilding them.

Support for 4.03 is still experimental. I plan to release an update next week.

Can you try with current master? This should work as expected.

I'm getting installation problems with opam pin. Specifically, none of the share files appear where they should be.
Looking at the opam file, does the 'prefix' variable exist? Also, the rm command is trying to delete a non-existent directory, with the result that I still have my old .pyc files.

$ opam config var prefix
/home/def/.opam/4.03.0

You can try on your machine.

So looking at your recent commit, it wasn't my config but a file that got messed up?
I'm trying to pin master now and I get a compilation error.
Error: The implementation src/ocaml/lexer_raw.ml
[...]
mutable comment_start_loc : Location.t list;
mutable preprocessor : preprocessor option;
}
File "src/ocaml/preprocess/lexer_raw.mll", line 53, characters 0-197:
Actual declaration
The mutability of field buffer is different.

Can you start from a fresh clone?

My bad! I had a change to the opam file that persisted after pulling.
It works! Yay! So happy Merlin's back. Thank you so much for your tireless efforts.

You are welcome, situation is a bit shaky during transition to 4.03.


Build a House Price Predictor with SAP AI Core

Tutorials: https://developers.sap.com/tutorials/ai-core-code.html
In step 13, the command used to upload the image is
docker upload docker.io/<YOUR_DOCKER_USERNAME>/house-price:02

It should be
docker push docker.io/<YOUR_DOCKER_USERNAME>/house-price:02

@dhrubpaul , please respond to the user's feedback.  Thank you.

Hi @gianfranco-s , @jmmargo ,
Thanks for the feedback. The tutorial has been updated to incorporate the code changes, and is functional now.
Thanks.


Feature/1112 support variables in Generate Code

Description
Fixing the issue with the variables in the Generate code from query
Contribution Checklist:

[X] The pull request only addresses one issue or adds one feature.
[X] The pull request does not introduce any breaking changes
[X] I have added screenshots or gifs to help explain the change if applicable.
[X] I have read the contribution guidelines.
[X] Create an issue and link to the pull request.

Linked to this issue : https://github.com/usebruno/bruno/issues/1112
The header is there now, but we still got the issue that the variable are not replace by there value

now the content of the variable is replaced in the Headers

Now the variables in the query params are replaced and escaped

Is there any thought expanding this and making an equivalent to req.getBody() that populates the variables? This would incredible useful when attempting to generate HMAC-signatures or any other time that a complete body is required within a pre-request script

@GarlicPunk I'm not sure what you are talking about.  Can you give me more details please.  Also, can you try this branch please.  I added few changes there : https://github.com/survivant/bruno/tree/main

+1

@survivant can you up-to-date pull request?
@helloanoop @lohxt1 please review this PR :adore:


Adding doc

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/GetStarted.md
:white_check_mark:Succeeded

windows-iotcore/commercialize-your-device/GoToMarket.md
:white_check_mark:Succeeded

windows-iotcore/commercialize-your-device/OEMLicenseRequirements.md
:white_check_mark:Succeeded

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


Watchdog bites while debugging

Hello!
Is there a way to relax the watchdog while I'm debugging(line by line)? Of course, the watchdog thinks that nothing is happening(while I let execute the code line by line), so it gets angry. :dog:
[21:45:12] [Server Watchdog/FATAL]: A single server tick took 124,08 seconds (should be max 0,05) [21:45:12] [Server Watchdog/FATAL]: Considering it to be crashed, server will forcibly shutdown.

In server.properties there is a key max-tick-time, set it to a big number.

Thank you!

@randombyte-developer: You can also set it to 0, which disables the watchdog thread entirely.

Good to know. Thanks!
This should be written down somewhere in the docs.