Request for new models

Will support for new models be added like Auraflow and Flux be added ?
https://huggingface.co/fal/AuraFlow
https://huggingface.co/black-forest-labs/FLUX.1-dev

@karthik4579 there are plans to add Flux in the future

Can you comment on the expected timeline for adding flux? Would you be open to a PR that adds it (we haven't built it yet, but could work on it if you are open to such a PR)

@gabeweisz PRs are always welcomed :)
I am planning to start working on flux in beginning of 2025. There is already a JAX Flux repo that runs on both GPUs and TPUs, but it needs to be optimized. repo


feat: add role to force-bridge

Codecov Report

Merging #82 (e52ab66) into main (53d4ccc) will increase coverage by 8.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #82      +/-   ##
==========================================
+ Coverage   41.26%   49.29%   +8.03%
==========================================
  Files          23       23
  Lines        1958      499    -1459
  Branches       48       30      -18
==========================================
- Hits          808      246     -562
+ Misses       1150      253     -897

Impacted Files
Coverage Δ

...modules/ckb-contracts/types/src/generated/basic.rs

...tracts/types/src/generated/recipient_typescript.rs

...contracts/lib/recipient-typescript-lib/src/test.rs

...tracts/lib/recipient-typescript-lib/src/actions.rs

...-modules/ckb-contracts/types/src/recipient_cell.rs

...ules/ckb-contracts/tests/src/utils/case_builder.rs

...es/eth-contracts/contracts/libraries/SafeERC20.sol

offchain-modules/ckb-contracts/tests/src/lib.rs

...ffchain-modules/ckb-contracts/types/src/convert.rs

...in-modules/eth-contracts/contracts/ForceBridge.sol

... and 36 more

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 53d4ccc...e52ab66. Read the comment docs.


Support passing custom host for Index operations

Problem
We need support for supplying a custom host value for index operations.
Solution
pinecone.init() and Config already support the ability to supply a custom host. It didn't seem like it was being passed through to the ApiClient:

Update _get_api_instance() in manage.py to check for a Config.CONTROLLER_HOST value, and apply it to the client_config if so. This will then be used throughout the index operations.

Type of Change

[X] New feature (non-breaking change which adds functionality)

Test Plan
Pull this branch down and test locally. I validated myself by passing a bogus host in and looking over the errors, then passing the proper host via init to validate it works properly.
>>> poetry shell
>>> python3

>>> import pinecone
>>> pinecone.init(api_key="123-456-789", environment="my_environment", host: "https:custom-host-foo.com")

# Having passed a custom host that's inaccessible should fail
>>> pinecone.list_indexes()
# urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='fooblahblah.io', port=443): Max retries exceeded with
# url: /databases (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x107eb9dd0>:
# Failed to resolve 'fooblahblah.io' ([Errno 8] nodename nor servname provided, or not known)"))

# Re-Init - should work as expected
>>> pinecone.init(api_key="123-456-789", environment="my_environment")

pinecone.list_indexes()
# ['austin-3', 'austin-py-test', 'resin--test-index-1', 'test-create-1']

I know it's asking for a lot in this situation, but a test case would be great to see here.

I was thinking about that as well, definitely worth getting one added. I'll take a pass.

Looks great, thanks!


Allow notifications to have newlines

I would like to be able to use newlines in the notifications.
I know it has already been rejected here, but the VSCode native alerts are able to have multi-line comments, so why isn't this an option for the extensions? If "Notifications are imho not the right place to show structured text with formatting", then where else are we supposed to show complex notifications? Is there any other available location in VSCode?
Also I would argue that multi-line notifications are a pretty basic thing. I am not asking for the ability to add sixteen colors and a cursive font, I just need to be able to, say, make a confirmation message which shows the contents of an object in a structured way, for example.
And I am not the only one who still wants this.
Therefore opening this as a feature request again.

this can't be a good reason to strip out new lines
// Remove newlines from messages as we do not support that and it makes link parsing hard
		message = message.replace(/(\r\n|\n|\r)/gm, ' ').trim();

Please reopen.

well, good IDEs allow notification messages that contain paragraphs of text for more info.
not sure why this is such a big deal, or what that links parsing comment has to do with this change & such a simple request.

@bpasero Why is this out of scope? This has been asked for by the community many times, and imo feels like a very reasonable request. What is the main objection here?

I feel that notifications are not a good place to show a lot of information. The text should be short and concise. Allowing to use newlines and potentially other formatting only asks for larger notifications that consume even more space.
Does that make sense?

While I agree with the sentiment and don't want to have larger notifications, the ability of adding a newline or so can often improve readability and user-experience. The space is still constrained so packing too much content would still be highly discouraged. Also, we aren't talking about other formatting here.

I feel that notifications are not a good place to show a lot of information. The text should be short and concise. Allowing to use newlines and potentially other formatting only asks for larger notifications that consume even more space.
Does that make sense?

@bpasero Isn't that up to us? If we design our extensions badly and the alerts are obnoxiously big, then people just won't use our extension...

Let me bring this to the UX call and then report back the decision here. Depending on that call we may either close or leave the issue open.

@katelynienaber

@bpasero Isn't that up to us? If we design our extensions badly and the alerts are obnoxiously big, then people just won't use our extension...

That is not a good argument. Every extension author feels that their extension is the best and greatest and deserves notifications with lots of text to tell the user. The user may not agree but may also not have any alternative (e.g. imagine this was the one and only Python extension or C++). We would at least need https://github.com/microsoft/vscode/issues/41767 so that the user can stop an extension from spamming.

I'd be curious to know what the use cases are here. If all we're wanting to do is improve the readability of notifications, then I think we can look at how other systems structure their notifications:
Title
Detail
Message
[Actions]

I don't know if Slack and Windows notifications are good examples of UX for IDE notifications.
I would agree that in the short form that toast would display message type (info, warning, error), perhaps an ext. name it's coming from & the 1st line of text with ... in a collapsed state.
However, there are instances when we'd like to display a notification, like an error, where we would provide brief error description, & more information on the new line, if that makes sense.

@RandomFractals I don't know, you're comparing a single tool vs multiple platforms that use the same pattern. If you have other examples of better notifications please do share them.
Notifications are intended to be short and concise so that the user can act upon it. If they need more information, there should be an action to see that information. I don't believe we should try to cram too much information here.

I don't have a better example. I believe I described the typical use case & notifications in the current form don't support it.
It doesn't sound like you are willing to provide that option, or formatted messages in notifications. So, feel free to close it.
Thanks!

IMO a decent compromise would be to allow a title and a body, but disallowing newlines in the body. There are some use cases where a single uninterrupted line of text just isn't the best way to preset some information. I don't agree that bodies shouldn't be able to use newlines at all, but at least having 2 lines should cover a good chunk of use cases.

Two lines FTW.


Deployment

#User story
WHEN I visit the website using the URL,
THEN I can access my website from any browser
##Acceptance Criteria
Application deployed at live URL.
Application loads with no errors.
Application GitHub URL submitted.
GitHub repository that contains application code.

Completed


Week Seven Work updates

Updating Week 7 Details with links to ne project

This should NOT have come here. This was an error.


Home/end keyboard shortcuts

Both the WAI-ARIA tabs example and collapsible dropdown example recommend using Home/End to jump to the start/end of the list, but I did not implement this.
Where this would apply:

skintone dropdown (listbox)
search results (listbox)
tabs

Actually upon further inspection, for the combobox home/end should just go to the start/end of the input, not the end of the list. So we only need to do this for the skintone dropdown and tabs.


Fix missing image reference error message

This change updates the missing image reference error message to match
the triggering condition.

Oops, this is actually wrong.


errors on login from kodi/nflgamepass addon

Hi there!
I just installed the gamepass addon from the Kodi addon repository hoping to watch the superbowl next weekend on my new Kodi install, rather than on my phone :D
Unfortunately after I input my credentials I only get an error dialog that reads failed_login which led me to this repo.
I hacked the pigskin.py script to dump it's log file to disk and see the following (my username is redacted):
... request/response to v1/web/config omitted ...
[pigskin]: Debugging enabled.
[pigskin]: Python Version: 2.7.15 (default, Oct 15 2018, 15:24:06)
[GCC 8.1.1 20180712 (Red Hat 8.1.1-5)]
[pigskin]: Request URL: https://www.nflgamepass.com/api/user/oauth/token
[pigskin]: Method: post
[pigskin]: Payload: {'username': 'yyyyyy', 'password': 'xxxxxxxxxxxx', 'client_id': u'42cc360e-6fbb-4472-9437-2f088b8730de', 'grant_type': 'password'}
[pigskin]: Response code: 403
[pigskin]: Response:
<TITLE>Access Denied</TITLE>

Access Denied

You don't have permission to access "http://www.nflgamepass.com/api/user/oauth/token" on this server.

Reference #18.3ff90a17.1548284086.6ce5bc69

[pigskin]: Login Failed.
[pigskin]:
<TITLE>Access Denied</TITLE>

Access Denied

You don't have permission to access "http://www.nflgamepass.com/api/user/oauth/token" on this server.

Reference #18.3ff90a17.1548284086.6ce5bc69

Specifically the "you don't have permission" 403 error is the problem. I'm aware of the geolocated restriction of the service, and am physically located in Zurich, Switzerland. I generally have no problem using the web interfaces for game pass.
Any tips on how to debug this?

Closing this issue, as NFL has canceled the Gamepass service


NestedBlockDepth and functions like 'use'

Imagine the following code:
closeable1.use { closeable1 ->
    closeable2.use { closeable2 ->
        closeable3.use { closeable3 ->
            repeat(N) {
                // ...logic...
            }
        }
    }
}

NestedBlockDepth is naturally violated here, but there's no way to rewrite this code.
The only way to bypass it is suppression (and I don't like it) or setting threshold higher (it is equivalent to disabling the check).
I think this check needs something ComplexMethod has, like ignoreNestingFunctions.

Why not refactor this nested code into well-named functions to make it easier to understand? What's preventing you to do this?
By the way, the config option ComplexMethod:nestingFunctions actually counts the formalized McCabe complexity for scope functions. This is completely unrelated to the NestedBlcokDepth rule.
Do you know that you could write a custom detekt rule exactly for your scenario?

The code above is equivalent to
try (var r1 = SomeStream;
     var r2 = OtherStream;
     var r3 = AnotherStream) {
}

I don't think it needs to be rewritten, it's just a lack of such syntax in Kotlin that produces the nested use calls.

NestedBlockDepth is naturally violated here, but there's no way to rewrite this code.

I agree with @sanyarnd I had to write this code a couple of times (It was anyway never more than 4/5 nested blocks, so that would be a good threshold imho).
We could look into ignoring blocks where the receiver is a Closeable to handle those scenarios.

Are those so many cases? An @Suppress wouldn't it be enough? You can always add a new function to "reset" the indentation. For me it is a bit strange to make NestedBlockDepth more complex. This open the door to add even more exceptions to that rule.


dracula-theme: 1.3.0 -> 2.0 and rename ant-dracula to dracula-theme

Motivation for this change
Update package and rename it due to the upstream repo has been renamed.
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[X] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

cc: @alexarice
fixes: #97655

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/244


Fixed 186 other postags that were too long

Also changed some underscores to hyphens. The postags that were too long had an extra hyphen at the end. I removed the extra hyphen.

Thanks for all the work you've put into this PR!
It looks like there's a minor issue with line endings and encodings, making it difficult to review the changes. For example, the entire public/xml/eur-ba-23-169.xml file is marked as changed. Would you be able to update the PR to use the original line endings and only change the postags?

That is the only file of all the treebanks that uses that line ending. If you'd like it to conform to the others, you can accept the PR as it is. The line endings were the only thing changed in that file. There were no changes to any postags or anything else in eur-ba-23-169.xml. If you'd like, I can redo it and leave that file alone. But I've already got 4 more commits ahead of this and probably more in the future. And I'd rather not have to work around this one file every time.

It looks like there are two files with Windows line endings: eur-ba-23-169.xml and max-astrol-I-4-1-14.xml. I think you're correct that it would be a waste of time to have to work around the two files every time somebody wants to make a change. But at the same time, I don't like mixing formatting and content changes in a single commit (or a single PR). It makes the history hard to parse and is a vector for mistakes to get in the repo.
I've pushed a change to just update the formatting. Could you rebase your changes off of the base branch? Then, assuming it looks good to Anise, we can merge the changes.
Thanks again for all your work!

That sounds good. I'll do that.


[BUG] Bolt Cards and User Manager extensions 404 after upgrading from 0.9.4 to 0.10.4

Describe the bug
I upgraded from LNbits 0.10.0 to 0.10.4, two of my four installed extensions failed to download.
When starting up the log shows this:
Apr 23 16:27:54 NUC poetry[252134]: 2023-04-23 16:27:54.37 | INFO | Downloading extension Bolt Cards.
Apr 23 16:27:54 NUC poetry[252134]: 2023-04-23 16:27:54.60 | WARNING | HTTP Error 404: Not Found
Apr 23 16:27:54 NUC poetry[252134]: 2023-04-23 16:27:54.60 | WARNING |
Apr 23 16:27:54 NUC poetry[252134]: 2023-04-23 16:27:54.60 | WARNING | Failed to re-install extension: boltcards
Apr 23 16:27:54 NUC poetry[252134]: 2023-04-23 16:27:54.60 | INFO | Downloading extension User Manager.
Apr 23 16:27:54 NUC poetry[252134]: 2023-04-23 16:27:54.84 | WARNING | HTTP Error 404: Not Found
Apr 23 16:27:54 NUC poetry[252134]: 2023-04-23 16:27:54.84 | WARNING |
Apr 23 16:27:54 NUC poetry[252134]: 2023-04-23 16:27:54.84 | WARNING | Failed to re-install extension: usermanager
Apr 23 16:27:54 NUC poetry[252134]: 2023-04-23 16:27:54.84 | INFO | Downloading extension LndHub.
Apr 23 16:27:55 NUC poetry[252134]: 2023-04-23 16:27:55.28 | INFO | Extracting extension LndHub.
Apr 23 16:27:55 NUC poetry[252134]: 2023-04-23 16:27:55.29 | SUCCESS | Extension LndHub installed.
Apr 23 16:27:55 NUC poetry[252134]: 2023-04-23 16:27:55.33 | INFO | ✔ Successfully re-installed extension: lndhub
Apr 23 16:27:55 NUC poetry[252134]: 2023-04-23 16:27:55.33 | INFO | Downloading extension LNURLp.
Apr 23 16:27:55 NUC poetry[252134]: 2023-04-23 16:27:55.75 | INFO | Extracting extension LNURLp.
Apr 23 16:27:55 NUC poetry[252134]: 2023-04-23 16:27:55.76 | SUCCESS | Extension LNURLp installed.
Apr 23 16:27:56 NUC poetry[252134]: 2023-04-23 16:27:56.07 | INFO | ✔ Successfully re-installed extension: lnurlp
Apr 23 16:27:56 NUC poetry[252134]: 2023-04-23 16:27:56.08 | INFO | Application startup complete.

The two offending extensions were also missing from the GUI.
I was able to reinstall the extensions from the Manage Extensions GUI and the extension`s data (a bolt card, and a created user and their wallet) was still there.
Expected behavior
Upgrading LNbits does not break installed extensions.

One possible scenario for this issue:

user installs extension abc version 1.1 (works as expected)
devs launch release extension abc version 1.2
devs remove release files extension abc version 1.1
user upgrades lnbits (docker instance?)
lnbits tries to fetch extension abc version 1.1, but it is not found <-- therefore the above error
user installs manually extension abc version 1.2 (works as expected)

If downloading a newer version of an extension fails, I would prefer the older version not to be deleted yet so it can still be used.

@20a8vnf30 are you using docker?
I'm just curious why the extension was deleted in the first place.

@motorina0 My currenct LNbits instal was done through poetry, the previous version was installed with venv.


feat: Do deterministic inference

Switch default to do_sample=False to have deterministic outputs.
Add first AutoRA example to the data

Codecov Report
Attention: 5 lines in your changes are missing coverage. Please review.

Comparison is base (89899bb) 95.83% compared to head (6e7a101) 92.06%.

Files
Patch %
Lines

src/autora/doc/pipelines/main.py
28.57%
5 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #25      +/-   ##
==========================================
- Coverage   95.83%   92.06%   -3.77%
==========================================
  Files           3        3
  Lines         120      126       +6
==========================================
+ Hits          115      116       +1
- Misses          5       10       +5

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Ensure invariant that TimeWindow::start < end

Ignoring the check, because we're still on major version 0


chore(ci): build multiplatform next container image

Description
This updates the build process for the next image (build from main branch)
It adds the arm64 image build. arm64 and amd64 are built in parallel.
Platform specific images are tagged with next-{platform}. This is mainly to make the amd64 image available quickly (takes less than 40 min) for testing, as arm64 build can take 4 hours.
After both builds are done, the next multiplatform tag is pushed and can be used.

Which issue(s) does this PR fix

Fixes https://issues.redhat.com/browse/RHIDP-5027

Do we want PR builds on arm too, in case you're developing something locally on your arm64 mac?

Do we want PR builds on arm too, in case you're developing something locally on your arm64 mac?

I'm working on that as well. I'll do it in a separate PR. e2e tests depend on those images, so I want to make sure that they are not delayed by arm image builds


Important styles on icons overwrite other styles/packages with icons

I'm submitting a ...  (check one with "x")
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, post on Stackoverflow or Gitter

Current behavior

The following styles on icons.css overwrite other (packages') icons styles:
[data-icon]:before {   font-family: "data-table" !important; [class^="icon-"]:before, [class*=" icon-"]:before {   font-family: "data-table" !important;
Please don't use important, or specify the styles better.
I'm using this datepicker and the icons there are not readable because of the settings named above:
https://github.com/kekeh/mydatepicker
Expected behavior
The ngx-datatable should only overwrite their own icons' font-family.
Reproduction of the problem
Install both packages and open the datepicker. On examining the icon in the browser, you will find the datatable's rule: "font-family: "data-table" !important;" and the icons won't show properly. This problem is also expected to appear on all other packages using icons.
What is the motivation / use case for changing the behavior?
Modularization/ the SOLID principles/ interference with other packages using icons
Please tell us about your environment:
Angular2, AngularMaterial2

Table version: 8.0.0

Angular version: 4.0.2

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Language: [all | TypeScript X.X | ES6/7 | ES5]

This can easily be solved by using a prefix for all styling related class names. I would suggest using datatable-icon- to match the names used for the components.

Closed due to inactivity.


Sed Tank Module Function

@monroews The MathCad function for determining plate settler modules currently is written so each plant could have different number of plate settlers per module, starting with mod 8 and going up (apparently without end). Is it acceptable to rewrite the function so they are standardized to 10 plate settlers per module, and whatever number of P.S. remaining gets added onto a new module or added to the set of 10?

Yes! identical modules for all plants is best. leftovers can be a small
module.
On Sun, 11 Mar 2018 2:06 PM Cynthia<EMAIL_ADDRESS>wrote:

@monroews https://github.com/monroews The MathCad function for
determining plate settler modules currently is written so each plant could
have different number of plate settlers per module, starting with mod 8 and
going up (apparently without end). Is it acceptable to rewrite the function
so they are standardized to 10 plate settlers per module, and whatever
number of P.S. remaining gets added onto a new module or added to the set
of 10?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/AguaClara/aide_design/issues/36, or mute the thread
https://github.com/notifications/unsubscribe-auth/AbN_67MUDiCvOdYO1wJBRGYd6hIrBdFRks5tdWe9gaJpZM4SlyiC
.

Ok we will make modules of 10 plates and then one module which has the "leftover" plates at the end.


[Bug]: IBM Granite 3.1 tool parser fails

Your current environment

The output of `python collect_env.py`
Your output of `python collect_env.py` here

Not relevant - running with docker vllm/vllm-openai:v0.6.5

Model Input Dumps
No response
🐛 Describe the bug
The granite tool parser (--tool-call-parser granite) does not seem to be working for IBM Granite 3.1.
Note that this is not related to existing streaming-related bugs; note that stream is set to false; temperature=0 has also been set to maximize reproducability
vLLM Run configuration via docker-compose:

  vllm-9-granite31:
    image: vllm/vllm-openai:v0.6.5
    entrypoint: [
      "vllm", "serve", "ibm-granite/granite-3.1-8b-instruct",
      "--enable-auto-tool-choice", "--enable-chunked-prefill", "--enable-prefix-caching",
      "--gpu-memory-utilization", "0.98",
      "--max-model-len", "32768",
      "--tool-call-parser", "granite",
      #"--max-num-batched-tokens", "8096",
      #"--max-num-seqs", "256",
      "--num-scheduler-steps", "1"
    ]

Note --enable-auto-tool-choice and --tool-call-parser granite. This should work per the docs on IBM granite tool calling.
Example request and response:
{
  "model": "ibm-granite/granite-3.1-8b-instruct",
  "messages":[
    {
      "role": "user",
      "content": "What is the weather in Dallas Texas?"
    }
  ],
  "stream": false,
  "temperature": 0,
  "tools": [
    {
      "type": "function",
      "function": {
        "name": "get_current_weather",
        "description": "Get the current weather in a given location",
        "parameters": {
          "type": "object",
          "properties": {
            "city": {
              "type": "string",
              "description": "The city to find the weather for, e.g. 'San Francisco'"
            },
            "state": {
              "type": "string",
              "description": "the two-letter abbreviation for the state that the city is in, e.g. 'CA' which would mean 'California'"
            },
            "unit": {
              "type": "string",
              "description": "The unit to fetch the temperature in",
              "enum": [
                "celsius",
                "fahrenheit"
              ]
            }
          },
          "required": ["city", "state"]
        }
      }
    }
  ]
}

Output:
{
  "id": "chatcmpl-bea4219d4bf84b08b62c1bedd9de29a4",
  "created":<PHONE_NUMBER>,
  "model": "ibm-granite/granite-3.1-8b-instruct",
  "object": "chat.completion",
  "system_fingerprint": null,
  "choices": [
    {
      "finish_reason": "stop",
      "index": 0,
      "message": {
        "content": "<tool_call>[{\"arguments\": {\"city\": \"Dallas\", \"state\": \"TX\", \"unit\": \"celsius\"}, \"name\": \"get_current_weather\"}]",
        "role": "assistant",
        "tool_calls": null,
        "function_call": null
      }
    }
  ],
  "usage": {
    "completion_tokens": 41,
    "prompt_tokens": 343,
    "total_tokens": 384,
    "completion_tokens_details": null,
    "prompt_tokens_details": null
  },
  "service_tier": null,
  "prompt_logprobs": null
}

Expected output: a valid tool call completion, for example:
{
  "id": "chatcmpl-d4715468ea864d41ad79072727bc61aa",
  "created":<PHONE_NUMBER>,
  "model": "NousResearch/Hermes-3-Llama-3.1-8B",
  "object": "chat.completion",
  "system_fingerprint": null,
  "choices": [
    {
      "finish_reason": "tool_calls",
      "index": 0,
      "message": {
        "content": null,
        "role": "assistant",
        "tool_calls": [
          {
            "function": {
              "arguments": "{\"city\": \"Dallas\", \"state\": \"TX\", \"unit\": \"fahrenheit\"}",
              "name": "get_current_weather"
            },
            "id": "chatcmpl-tool-e33dff3a0d5445caac4ef3895f89ac24",
            "type": "function"
          }
        ],
        "function_call": null
      }
    }
  ],
  "usage": {
    "completion_tokens": 34,
    "prompt_tokens": 424,
    "total_tokens": 458,
    "completion_tokens_details": null,
    "prompt_tokens_details": null
  },
  "service_tier": null,
  "prompt_logprobs": null
}

Seems possibly related to #11039,  #11069, and #11307
cc @maxdebayser @tjohnson31415
Before submitting a new issue...

[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

+1，
i use model qwen2.5-32b-instruct,

+1，
i use model qwen2.5-32b-instruct

+1，i use model qwen2.5-32b-instruct,

@K-Mistele Thanks for trying out the new model and looking in to this!
The fix for parsing the <tool_call> token came in the https://github.com/vllm-project/vllm/pull/11307 PR that you linked to. This PR was merged the day after the v0.6.5 release of vLLM, so you would need to use the latest code. I just checked with your example request and it worked for me using latest.

    image: vllm/vllm-openai:v0.6.5

You will need to use the latest code
i.e. build from main? or is there a -post release?


rewrite this plugin as an imagemin-webp wrapper

We don't need to maintain almost the same two projects in the different ways. And currently imagemin-webp supports more cwebp options.
The only difference between this plugin and imagemin-webp is that gulp-webp should emit a gulp plugin error. So I introduced modify-error-event to update imagemin-webp's default error into the plugin error.

Ah, yeah, forgot about this one. I was planning to deprecate this, but might as well just keep it as a simple wrapper.

Thanks for the new release.

I was planning to deprecate this

This plugin is useful for me because gulp-load-plugins can load it by default, without changing pattern option.

:+1:


api service: Sort the returned images in ListImages

In the request:

Add an array that includes defined sortable fields, such as id, name, importtime.
Add a bool to tell whether to sort by ascending or desceding order.

Why should rkt be responsible for this?

It's nice to have, besides rkt image list also provides this

That's rather different, that part of rkt image list is essentially UX
glue. Can you convince me it's preferable for the server to provide this
instead of just doing it client-side?
On Tue, Dec 22, 2015 at 6:30 PM, Yifan Gu<EMAIL_ADDRESS>wrote:

It's nice to have, besides rkt image list also provides this
—
Reply to this email directly or view it on GitHub
https://github.com/coreos/rkt/issues/1911#issuecomment-166680716.

@jonboulle Doing on the client side means every user needs to implement the sort interface, a lot of duplicated codes. However, since we already have the functionality here https://github.com/coreos/rkt/blob/9ee8c238669a6cea23d7dff296996fbaa5ee71f8/store/aciinfo.go#L128 so I think it will be easier to do in the server side.
Of course this doesn't count the API maintaining cost. If you are concerned about this, we can hold.


Fix blocking test in test_syntax

Prevents an infinite loop if the test doesn't fail as expected. Might be worth making a PR to CPython for this one.

Yes, we should submit a bug and patch to CPython.


[REFACTOR/ENHANCEMENT] Refactor + Simplify Builder

Description
The builder scripts of our projects have always been a bit messy, especially the ones of this project. To make the generators more dynamic, readable and shorter, I've been working on a dependency-free, lightweight node markdown builder recently, exclusively for the 30-seconds projects, see it here.
I also fixed the isSimilar snippet that currently is a bit messed up because of inconsistent line breaks.
README's should basically be same except for indentation:
Main README: https://github.com/Chalarangelo/30-seconds-of-code/tree/refactor-builder
Archive README: https://github.com/Chalarangelo/30-seconds-of-code/tree/refactor-builder/snippets_archive
What does your PR belong to?

[ ] Website
[x] Snippets
[x] General / Things regarding the repository (like CI Integration)
[ ] Tests

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] Enhancement (non-breaking improvement of a snippet)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have checked that the changes are working properly
[x] I have checked that there isn't any PR doing the same
[x] I have read the CONTRIBUTING document.

yeah I now removed them all 😄

yep, to me aswell. Let's merge this!


Fix to the anime.js Footer

Hey, I noticed on the footer of the animejs.com site that "Staggering" had a misspelling in one of the items under the Documentation category.

Hey, let me take care of this issue.

can i work on this?


Known issues w/ CMPT12 code.

Some of the code is missing (due to some complications of exporting it from old lab computers)
No comments :< (I couldn't be bothered to comment the code way back when sadly)

Added the missing code through the last few days.


Meta Store , Time fields aren't Date types

Create Time, Status Time etc
e.g.
from "Meta Store"

eval Type=typeOf(${Create Time})
eval Dt=parseDate(formatDate(${Create Time}))

limit 10

select ${Create Time}, Type, Dt

The following changes will be made to the data source field types:
Annotations
Change CreadtedOn to Date
Change UpdatedOn to Date
Index Shards
Change Last Commit to Date
Meta
Change Status Time to Date
Change Create Time to Date
Change Effective Time to Date
Reference Date
Change Date to Date
Task Manager
Change Submit Time to Date
Change Age to Duration
Any Statistic data source
Change Date Time to Date

closed


Unable to link Sippet on Apple Silicon with LDFLAGS set

Hi,
It appears that because of the structure of the Makefile, having LDFLAGS set in the env makes the compilation of Sippet fail on Apple Silicon.
In our app, we're using Sippet as well as fast_tls. The issue is, fast_tls needs LDFLAGS to contain the path to the OpenSSL library (i.e. LDFLAGS=-L/opt/homebrew/opt/openssl/lib), and will not compile otherwise. When we try to compile everything at once, though, linking of Sippet fails because the Makefile uses conditional variable assignment ?= and does not overwrite/append to LDFLAGS if it is already set -- which is the case.
As far as I've tested, the only linker flag necessary for Sippet to compile successfully with this setup is -undefined suppress.
The most straightforward way of alleviating this issue I can think of is to always append the -undefined suppress flag, since it is necessary to link anyway. This is a simple fix, and doesn't change the general behaviour of the Makefile:
diff --git a/c_src/Makefile b/c_src/Makefile
index c20a402..a6dc5f1 100644
--- a/c_src/Makefile
+++ b/c_src/Makefile
@@ -73,7 +73,9 @@ endif
        CC ?= cc
        CFLAGS ?= -O3 -std=c11 $(ARCHFLAGS) -fstack-protector -Wall -Wmissing-prototypes
        CXXFLAGS ?= -O3 -std=c++11 $(ARCHFLAGS) -fstack-protector -Wall
-       LDFLAGS ?= $(ARCHFLAGS) -flat_namespace -undefined suppress
+       LDFLAGS ?= $(ARCHFLAGS) -flat_namespace
+       # Necessary to link successfully on Apple Silicon
+       LDFLAGS += -undefined suppress
 else ifeq ($(PLATFORM),freebsd)
        CC ?= cc
        CFLAGS ?= -O3 -std=c11 -finline-functions -fstack-protector -Wall -Wmissing-prototypes

Please let me know whether you're OK with this solution, and I'll be happy to make the relevant PR.
Logs from the failed linking for reference:
ld: Undefined symbols:
  _enif_alloc_binary, referenced from:
      (anonymous namespace)::ParseMultipleUriParams(enif_environment_t*, std::__1::__wrap_iter<char const*>, std::__1::__wrap_iter<char const*>) in parser.o
      ...
  _enif_get_list_cell, referenced from:
      parse_wrapper(enif_environment_t*, int, unsigned long const*) in parser.o
  _enif_get_map_value, referenced from:
      parse_wrapper(enif_environment_t*, int, unsigned long const*) in parser.o
  [...] etc.

Hi @balena, what do you think about @sgfn's proposition?

Could we open a PR with proposed changes @balena ?

Hi @Rados13 and @sgfn, sorry the delay to respond.
Definitely it seems a reasonable solution, if you have time, please open a PR so this change can be easily merged and a new version pushed to Hex.


Chore: merge main @0cf3633

⚠ This PR is a WIP

[x] https://github.com/twbs/bootstrap/commit/2a09f10676cd66aa435fb09c4bc5c19225f10dd9
[x] https://github.com/twbs/bootstrap/commit/48a7160cf4e05dc18dde9cf33fa38c12d1bd2e5e

See https://github.com/twbs/bootstrap/pull/35917
Not sure but we could have a CSS var for $pagination-focus-outline in Bootstrap
Not sure but we could use var(--#{$variable-prefix}pagination-border-width) for all occurrences of $pagination-border-width in Bootstrap

[x] https://github.com/twbs/bootstrap/commit/63f75bccd8d206bb59b0e8421258ce03d298b784
[x] https://github.com/twbs/bootstrap/commit/5565c64bde8a203560c596c67eebb7a6f2fed412
[x] https://github.com/twbs/bootstrap/commit/999bfaa036cb886389050db3645d74dfede0d2e8
[x] https://github.com/twbs/bootstrap/commit/d82602063ac48359a0f15f1033837b53f72bef3a
[x] https://github.com/twbs/bootstrap/commit/f7f450ec59fd4b7a2e73df5f0eba2dd496edf387
[x] https://github.com/twbs/bootstrap/commit/546e34cf85a31a5d553c15afbeef8591d0935efc
[x] https://github.com/twbs/bootstrap/commit/ccba6a3589ba33e25ab2919cb844b5bc870e2fef
[x] https://github.com/twbs/bootstrap/commit/a247fe9b27ec57152f07aaa5dfc79f633d2b6d10
[x] https://github.com/twbs/bootstrap/commit/d97125475b3a5cbbafe3100d5981fd456c92c722
[x] https://github.com/twbs/bootstrap/commit/928bdcadc56cef30b4483616c4b2eee7cfa34bd2
[x] https://github.com/twbs/bootstrap/commit/d52f6c9de144ac2bc3eba002d3db538183c52465
[x] https://github.com/twbs/bootstrap/commit/642d756eeaf107bed2baac931933c9350c33f5c1
[x] https://github.com/twbs/bootstrap/commit/407af8ac7f9296627aebc1e4c5d0ee948f8be1f3
[x] https://github.com/twbs/bootstrap/commit/ae12d645ef0225831e59248c45689042ebdb83d2
[x] https://github.com/twbs/bootstrap/commit/4b17868fb47abf6ed2e994b6c1d0961b34b912a9
[x] https://github.com/twbs/bootstrap/commit/353ad45b4b8dd3235a9e26dcc614baaa7fa1a840
[x] https://github.com/twbs/bootstrap/commit/cb8726d9e75b10c52c84753da171daacd78aee90
[x] https://github.com/twbs/bootstrap/commit/3a9b0b8b6f674a0d032682ef9062b1f1243053c1
[x] https://github.com/twbs/bootstrap/commit/9ac8e806602e9f6e3b6384116b176cf6ebf6991f
[x] https://github.com/twbs/bootstrap/commit/0804c0043f5bae586834a9b9ef1e2301e8452794

[ ] After having merged this PR Create some issues to check that those 2 workflows are working

[x] https://github.com/twbs/bootstrap/commit/37f3977e6d96e274cb73255d99e3e4ec60f03c0f
[x] https://github.com/twbs/bootstrap/commit/a381ee320b1e708651026fd85d4e7258e8c3ec08
https://github.com/twbs/bootstrap/commit/36765912c65ba859249776a6ec9eea7c2562e5d9: Do nothing because was already integrated in a previous PR
[x] https://github.com/twbs/bootstrap/commit/333d89e4980863db15d0f639051e3b239e77decc: None of those examples are actually visible so I've updated them to have the same content than in Bootstrap.
[x] https://github.com/twbs/bootstrap/commit/f1a89bf0d5d11ba4b2958f8caed098c6946342d1
[x] https://github.com/twbs/bootstrap/commit/3aaaa01ffa71e5a784451753d5bf9b86a1d5323c
[x] https://github.com/twbs/bootstrap/commit/db61cf3d6a907756aee2b0c4ee2cb6488c0ed459
[x] https://github.com/twbs/bootstrap/commit/1c5ec4c310ee630884fb75050ecd94e771031839
[x] https://github.com/twbs/bootstrap/commit/2c5a16ff8bdffe64361c4e2b8ad2a2dd57c6fa14
[x] https://github.com/twbs/bootstrap/commit/28d9aaf6708b4b84e7e70a62b78d8b22a51d990d
[x] https://github.com/twbs/bootstrap/commit/e4b62a920a5ed9c48c46865f987702fa67369ae0
[x] https://github.com/twbs/bootstrap/commit/d0b8114462a7fd10fd05d503280f1f06c3df4a42
https://github.com/twbs/bootstrap/commit/fd9db1758b17e6dc5c259f9efd486638af927777: Nothing to do in Boosted
[x] https://github.com/twbs/bootstrap/commit/d74870a749d694cb2859d300c24a0a49a0b52bce
[x] https://github.com/twbs/bootstrap/commit/4ee1465acfd14ab633364b5581d1e9213d946686: :warning: We need to be sure about this one before merging
https://github.com/twbs/bootstrap/commit/f98838136515ba2f9c6196b8476fd538e82371da: Nothing to do in Boosted
https://github.com/twbs/bootstrap/commit/0cf36335d66bf47e03587f798cf3fc5666eb7994: Nothing to do in Boosted

@Lausselloic I'd appreciate your feedback on https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/pull/1114/commits/ea5c8596c60f19ab1ab550f23bcec799af887b34 (based on https://github.com/twbs/bootstrap/commit/4ee1465acfd14ab633364b5581d1e9213d946686).


[BUG] Security test failure of action validation feature

What is the bug?
During 2.4 release testing, the security tests failures are related to action validation feature introduced in this release.
Test failures: https://github.com/opensearch-project/opensearch-build/issues/2649#issuecomment-1308257681
The bug in action validation feature breaks the existing ISM explain API when security enabled totally. If user calls explain API, a java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0 exception shows up.
How can one reproduce the bug?
Reproduce by starting up a security enabled docker cluster, and run security enabled test against it.
Fix PR: https://github.com/opensearch-project/index-management/pull/607

Close this as code fixes have been merged in main and 2.x branches.


Error running flake 8

Hi, without changing anything (intentionally at least) I have an error when opening Atom:
[Linter] Error running Flake8 Error: /Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/pep8.py:102: FutureWarning: Possible nested set at position 1
  EXTRANEOUS_WHITESPACE_REGEX = re.compile(r'[[({] | []}),;:]')
    at ChildProcess.<anonymous> (/Users/xxxxx/.atom/packages/linter-flake8/node_modules/sb-exec/lib/index.js:56:20)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:885:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)

Studying previous posts didn't help, so I'm posting my own issue.

This is error text coming from flake8's stderr stream, in this case it looks like the internal pep8 has an error, or maybe is throwing an error related to your code.
What happens if you run flake8 on the file manually?

I get something like this:
/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/pep8.py:102: FutureWarning: Possible nested set at position 1
EXTRANEOUS_WHITESPACE_REGEX = re.compile(r'[[({] | []}),;:]')
single_neuron.py:3:1: H306  imports not in alphabetical order (pandas, matplotlib.pyplot)
single_neuron.py:15:1: H404  multi line docstring should start without a leading new line
single_neuron.py:15:1: H405  multi line docstring summary not separated with an empty line
single_neuron.py:28:1: H404  multi line docstring should start without a leading new line
single_neuron.py:28:1: H405  multi line docstring summary not separated with an empty line

That's what I thought, you'll need to figure out why flake8 is giving you errors. It looks like https://github.com/PyCQA/pycodestyle/issues/728 is what you want to follow as that is where the error is coming from.
Note that this might just be an issue in Python 3.7 as I don't see this on Python 3.6.3.

Why is this issue closed?
Upgrading to production Python 3.7.0 on Mac OSX disables the current version of AtomLinter/linter-flake8 (with an error message every time I type a character) and I see no workaround in this issue?

@cclauss See my comment here for a temporary workaround.


VRP with Time Windows - More than 1 time window per location

Hey guys,
Amazing library!
I have a situation where a location (or "customer") has two or more available time windows (let's say it's open in the morning, closed for siesta, and then open again until the evening).
The following SetRange line of code: time_dimension.CumulVar(order).SetRange(start, end) gives one such constraint, how can I add two with "OR" logic between them?
Thanks,
Ilai

@ilaif I had the same problem and here is how I approached it:

First construct 2 lists of starts and ends of ranges that the CumulVar cannot take
Then use the NotMemberCt of constraint solver as follows (assuming routing is your RoutingModel:

solver = routing.solver()
solver.AddConstraint(
    solver.NotMemberCt(
        time_dimension.CumulVar(order),
        forbidden_time_frame_starts, forbidden_time_frame_ends
    )
)

Thanks @michaelarakel !

Just to make sure I understand: Your solution was to use De Morgan Rules: (A OR B) = NOT(NOT(A) AND NOT(B)) and chain a list of "AND" constraints on a variable?
The two lists (forbidden_time_frame_starts and ..._ends) are plain lists of numbers?

@ilaif

Yes you can think of it as using De Morgan's rule
Yes they are just lists of numbers. Let me give an example to make this clearer. Suppose forbidden_time_frame_starts  = [0, 34000] and forbidden_time_frame_starts = [26999, 57000]. This means that the CumulVar will not be allowed to take values in ranges [0, 26999] and [34000, 57000]
These 2 functions are not part of the routing, but belong to the constraint solver. I have been using the code as documentation :) You can have a look at the constraint_solver.h for other constraints (in c++). constraint_solver.i contains the python bindings

I confirm this is the proper way to model multiple time windows (and the
routing solver will take them into account actively in the local search).
On Mon, Aug 28, 2017 at 3:01 PM, michaelarakel<EMAIL_ADDRESS>wrote:

@ilaif https://github.com/ilaif

Yes you can think of it as using De Morgan's rule
Yes they are just lists of numbers. Let me give an example to make
this clearer. Suppose forbidden_time_frame_starts = [0, 34000] and forbidden_time_frame_starts
= [26999, 57000]. This means that the CumulVar will not be allowed to
take values in ranges [0, 26999] and [34000, 57000]
These 2 functions are not part of the routing, but belong to the
constraint solver. I have been using the code as documentation :) You can
have a look at the constraint_solver.h for other constraints (in c++).
constraint_solver.i contains the python bindings

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/456#issuecomment-325346894,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKjyUineD46iixYddKQPYFtM5i9nOt6Hks5scroygaJpZM4PDjqs
.

Hey, guys,
I think there might be a bug with this method.
I've used the instructions above to create forbidden time windows:
solver = routing.solver()
solver.AddConstraint(
    solver.NotMemberCt(
        time_dimension.CumulVar(order),
        forbidden_time_frame_starts, forbidden_time_frame_ends
    )
)

In the test I have 6 locations:

index: 0, forbidden time windows: None (Not inserted as a constraint)
index: 1, forbidden time windows: None (Not inserted as a constraint)
index: 2, forbidden time windows: [10801], [86400]
index: 3, forbidden time windows: [10801], [86400]
index: 4, forbidden time windows: [0, 46801], [20999, 86400]
index: 5, forbidden time windows: [0, 46801], [20999, 86400]

Where 86400 is the horizon, index 0 is the start location and index 1 is the end location.
The assignment is the following order:

index: 0, max_arrive_time: 0, min_arrive_time: 0
index: 3, max_arrive_time: 6482, min_arrive_time: 672
index: 4, max_arrive_time: 10800, min_arrive_time: 4990
index: 5, max_arrive_time: 41831, min_arrive_time: 21000
index: 2, max_arrive_time: 43317, min_arrive_time: 22486
index: 1, max_arrive_time: 46800, min_arrive_time: 25969

As you can see node index 4 is arriving during the forbidden time window.
The full source code:
https://gist.github.com/ilaif/a79dfd8c41b2924d4d74758e342c88f5
Command I've called (with the relevant input parameters):
python vrpsolver.py --data {\"locations\":[{\"time_windows\":[],\"service_time\":0},{\"time_windows\":[],\"service_time\":0},{\"time_windows\":[[0,10800]],\"service_time\":900},{\"time_windows\":[[0,10800]],\"service_time\":900},{\"time_windows\":[[21000,46800]],\"service_time\":900},{\"time_windows\":[[18000,46800]],\"service_time\":900}],\"distance_matrix\":[[0,0,2553,672,3561,2372],[0,0,2553,672,3561,2372],[2583,2583,0,2288,2063,741],[812,812,2410,0,3418,2229],[3585,3585,1906,3290,0,1756],[2452,2452,586,2157,1732,0]],\"start_location_index\":0,\"end_location_index\":1}

Appreciate the effort,
Thanks, Ilai

The issue with your code is that node and variable are mixed. In particular
when you set the time windows, it should be:
solver.Add(
solver.NotMemberCt(
time_dimension.CumulVar(routing.NodeToIndex(order)),   <--
note the conversion here
[tw[0] for tw in closed_time_windows], [tw[1] for tw in
closed_time_windows]
)
)
Also note that there's probably a typo in the forbidden time windows you
displayed; it's actually:
index: 4, forbidden time windows: [0, 20999], [46801, 86400]
index: 5, forbidden time windows: [0, 17999], [46801, 86400]
(at least from the command line you  specified).
On Sat, Sep 23, 2017 at 8:14 PM, Ilai Fallach<EMAIL_ADDRESS>wrote:

Hey, guys,
I think there might be a bug with this method.
I've used the instructions above to create forbidden time windows:
solver = routing.solver()
solver.AddConstraint(
solver.NotMemberCt(
time_dimension.CumulVar(order),
forbidden_time_frame_starts, forbidden_time_frame_ends
)
)
In the test I have 6 locations:

index: 0, forbidden time windows: None (Not inserted as a constraint)
index: 1, forbidden time windows: None (Not inserted as a constraint)
index: 2, forbidden time windows: [10801], [86400]
index: 3, forbidden time windows: [10801], [86400]
index: 4, forbidden time windows: [0, 46801], [20999, 86400]
index: 5, forbidden time windows: [0, 46801], [20999, 86400]

Where 86400 is the horizon, index 0 is the start location and index 1 is
the end location.
The assignment is the following order:

index: 0, max_arrive_time: 0, min_arrive_time: 0
index: 3, max_arrive_time: 6482, min_arrive_time: 672
index: 4, max_arrive_time: 10800, min_arrive_time: 4990
index: 5, max_arrive_time: 41831, min_arrive_time: 21000
index: 2, max_arrive_time: 43317, min_arrive_time: 22486
index: 1, max_arrive_time: 46800, min_arrive_time: 25969

As you can see node index 4 is arriving during the forbidden time window.
The full source code:
https://gist.github.com/ilaif/a79dfd8c41b2924d4d74758e342c88f5
Command I've called (with the relevant input parameters):
python vrpsolver.py --data {"locations":[{"time_windows":[],"service_time":0},{"time_windows":[],"service_time":0},{"time_windows":[[0,10800]],"service_time":900},{"time_windows":[[0,10800]],"service_time":900},{"time_windows":[[21000,46800]],"service_time":900},{"time_windows":[[18000,46800]],"service_time":900}],"distance_matrix":[[0,0,2553,672,3561,2372],[0,0,2553,672,3561,2372],[2583,2583,0,2288,2063,741],[812,812,2410,0,3418,2229],[3585,3585,1906,3290,0,1756],[2452,2452,586,2157,1732,0]],"start_location_index":0,"end_location_index":1}
Appreciate the effort,
Thanks, Ilai
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/456#issuecomment-331660275,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKjyUgD8yWPp5YigYJeHiAYBdD2vJzcPks5slUqNgaJpZM4PDjqs
.

@furnon thanks a lot! It solved the problem. The forbidden time windows are indeed a type :)

In this post - https://groups.google.com/forum/#!topic/or-tools-discuss/MBq1TcqSQTI they suggest a different approach.
Instead of using the 'solver.NotMemberCt()' function they simply remove the forbidden intervals using
' time_dimension.CumulVar(index).RemoveInterval(time_window_end, next_time_window_start)'
Here is a link to another implementation https://stackoverflow.com/questions/61456895/multiple-time-windows-vrp-or-tools
which approach is better or more correct?
The latter definitely looks easier...

see https://github.com/Mizux/tsp_multiple_days/blob/feature/morning_nodes/40_Locations_3_days.py

see https://github.com/Mizux/tsp_multiple_days/blob/feature/morning_nodes/40_Locations_3_days.py

Hey Mizux, Thanks for your contribution and I've learnt a lot.
Regarding the repo you mentioned, could you please answer these two questions at your earliest convenience? Thanks in advance.

Why all tasks tend to be scheduled at day 3 instead of day 1?
It seems that the output doesn't make sense since all location at last day share the exactly same time slots.

@ywang1110 Because the code is broken ^^;, here the fix:
https://github.com/Mizux/tsp_multiple_days/commit/a7810f969312c80fe4191e9d9faaf84a67615ad8
potential output:
./40_Locations_3_days.py
Objective: 483266
droped: [40, 41, 44, 45]
Route for vehicle 0:
0 [0d 8:0:0;0d 8:0:0] -> 43 [0d 8:21:37;0d 8:48:21] -> 39 [0d 9:35:34;0d 10:2:18] -> 18 [0d 10:49:57;0d 11:16:41] -> 19 [0d 11:12:48;0d 11:39:32] -> 14 [0d 11:35:1;0d 12:1:45] -> 16 [0d 11:53:47;0d 12:20:31] -> 15 [0d 12:13:21;0d 12:40:5] -> 17 [0d 12:33:30;0d 13:0:14] -> 27 [0d 12:55:2;0d 13:21:46] -> 13 [0d 13:43:1;0d 14:9:45] -> 34 [0d 14:7:40;0d 14:34:24] -> 35 [0d 14:49:38;0d 15:16:22] -> 1 [0d 16:0:0;0d 16:0:0] ->

2 [1d 6:0:0;1d 6:0:0] -> 12 [1d 6:43:21;1d 6:45:39] -> 28 [1d 7:7:23;1d 7:9:41] -> 33 [1d 7:41:52;1d 7:44:10] -> 31 [1d 8:22:31;1d 8:24:49] -> 36 [1d 8:57:7;1d 8:59:25] -> 37 [1d 9:35:36;1d 9:37:54] -> 38 [1d 10:9:34;1d 10:11:52] -> 42 [1d 10:43:35;1d 10:45:53] -> 30 [1d 11:52:18;1d 11:54:36] -> 22 [1d 12:26:39;1d 12:28:57] -> 23 [1d 13:3:52;1d 13:6:10] -> 29 [1d 13:41:11;1d 13:43:29] -> 9 [1d 14:26:17;1d 14:28:35] -> 24 [1d 15:1:41;1d 15:3:59] -> 25 [1d 15:38:28;1d 15:40:46] -> 32 [1d 16:31:1;1d 16:33:19] -> 3 [1d 18:0:0;1d 18:0:0] ->

4 [2d 10:0:0;2d 10:0:0] -> 26 [2d 10:13:18;2d 10:13:18] -> 11 [2d 10:58:3;2d 10:58:3] -> 7 [2d 11:24:28;2d 11:24:28] -> 6 [2d 11:48:56;2d 11:48:56] -> 8 [2d 12:14:4;2d 12:14:4] -> 10 [2d 12:49:2;2d 12:49:2] -> 21 [2d 13:11:31;2d 13:11:31] -> 20 [2d 13:52:9;2d 13:52:9] -> [2d 14:26:48;2d 14:26:48]

@ywang1110 Because the code is broken ^^;, here the fix: Mizux/tsp_multiple_days@a7810f9
potential output:
./40_Locations_3_days.py
Objective: 483266
droped: [40, 41, 44, 45]
Route for vehicle 0:
0 [0d 8:0:0;0d 8:0:0] -> 43 [0d 8:21:37;0d 8:48:21] -> 39 [0d 9:35:34;0d 10:2:18] -> 18 [0d 10:49:57;0d 11:16:41] -> 19 [0d 11:12:48;0d 11:39:32] -> 14 [0d 11:35:1;0d 12:1:45] -> 16 [0d 11:53:47;0d 12:20:31] -> 15 [0d 12:13:21;0d 12:40:5] -> 17 [0d 12:33:30;0d 13:0:14] -> 27 [0d 12:55:2;0d 13:21:46] -> 13 [0d 13:43:1;0d 14:9:45] -> 34 [0d 14:7:40;0d 14:34:24] -> 35 [0d 14:49:38;0d 15:16:22] -> 1 [0d 16:0:0;0d 16:0:0] ->

2 [1d 6:0:0;1d 6:0:0] -> 12 [1d 6:43:21;1d 6:45:39] -> 28 [1d 7:7:23;1d 7:9:41] -> 33 [1d 7:41:52;1d 7:44:10] -> 31 [1d 8:22:31;1d 8:24:49] -> 36 [1d 8:57:7;1d 8:59:25] -> 37 [1d 9:35:36;1d 9:37:54] -> 38 [1d 10:9:34;1d 10:11:52] -> 42 [1d 10:43:35;1d 10:45:53] -> 30 [1d 11:52:18;1d 11:54:36] -> 22 [1d 12:26:39;1d 12:28:57] -> 23 [1d 13:3:52;1d 13:6:10] -> 29 [1d 13:41:11;1d 13:43:29] -> 9 [1d 14:26:17;1d 14:28:35] -> 24 [1d 15:1:41;1d 15:3:59] -> 25 [1d 15:38:28;1d 15:40:46] -> 32 [1d 16:31:1;1d 16:33:19] -> 3 [1d 18:0:0;1d 18:0:0] ->

4 [2d 10:0:0;2d 10:0:0] -> 26 [2d 10:13:18;2d 10:13:18] -> 11 [2d 10:58:3;2d 10:58:3] -> 7 [2d 11:24:28;2d 11:24:28] -> 6 [2d 11:48:56;2d 11:48:56] -> 8 [2d 12:14:4;2d 12:14:4] -> 10 [2d 12:49:2;2d 12:49:2] -> 21 [2d 13:11:31;2d 13:11:31] -> 20 [2d 13:52:9;2d 13:52:9] -> [2d 14:26:48;2d 14:26:48]

EDIT: if running for 30s solver manage to add one more location ! note: on my machine the solver manage to add it after 8/9s since when I enable the log I can see the objective drop from 488k to 388k...
Objective: 388656
droped: [40, 41, 44]
Route for vehicle 0:
0 [0d 8:0:0;0d 8:0:0] -> 19 [0d 8:8:2;0d 8:19:10] -> 14 [0d 8:30:15;0d 8:41:23] -> 17 [0d 8:52:55;0d 9:4:3] -> 27 [0d 9:14:27;0d 9:25:35] -> 11 [0d 9:55:17;0d 10:6:25] -> 28 [0d 10:19:36;0d 10:30:44] -> 13 [0d 11:5:8;0d 11:16:16] -> 34 [0d 11:29:47;0d 11:40:55] -> 35 [0d 12:11:45;0d 12:22:53] -> 31 [0d 12:50:43;0d 13:1:51] -> 36 [0d 13:25:19;0d 13:36:27] -> 45 [0d 14:19:42;0d 14:30:50] -> 1 [0d 16:0:0;0d 16:0:0] ->

2 [1d 6:0:0;1d 6:0:0] -> 12 [1d 6:43:21;1d 6:45:24] -> 33 [1d 7:8:43;1d 7:10:46] -> 26 [1d 7:43:34;1d 7:45:37] -> 37 [1d 8:27:28;1d 8:29:31] -> 38 [1d 9:1:26;1d 9:3:29] -> 42 [1d 9:35:27;1d 9:37:30] -> 18 [1d 10:43:36;1d 10:45:39] -> 20 [1d 11:3:19;1d 11:5:22] -> 30 [1d 11:39:26;1d 11:41:29] -> 22 [1d 12:13:47;1d 12:15:50] -> 10 [1d 12:56:23;1d 12:58:26] -> 9 [1d 13:30:19;1d 13:32:22] -> 29 [1d 14:0:14;1d 14:2:17] -> 23 [1d 14:37:13;1d 14:39:16] -> 25 [1d 15:14:53;1d 15:16:56] -> 24 [1d 15:50:40;1d 15:52:43] -> 43 [1d 16:31:16;1d 16:33:19] -> 3 [1d 18:0:0;1d 18:0:0] ->

4 [2d 10:0:0;2d 10:0:0] -> 32 [2d 10:14:37;2d 10:14:37] -> 16 [2d 11:6:0;2d 11:6:0] -> 15 [2d 11:25:34;2d 11:25:34] -> 7 [2d 11:48:48;2d 11:48:48] -> 6 [2d 12:13:16;2d 12:13:16] -> 8 [2d 12:38:24;2d 12:38:24] -> 21 [2d 13:13:55;2d 13:13:55] -> 39 [2d 13:56:0;2d 13:56:0] -> [2d 15:6:14;2d 15:6:14]

Thank you so much. I appreciate your help.

Hey @Mizux, I have another question, is it possible to expand the scope a little bit. For example:

Expand to VRP instead of TSP
NUM_DAYS varies among different locations. e.g., #1 location should be visited between 8:00-12:00 at the first day (day 0). #2 location should be visited  between 8:00-12:00 within the first two days (day 0 or day 1).

Hey @Mizux, I have another question, is it possible to expand the scope a little bit. For example:

Expand to VRP instead of TSP
NUM_DAYS varies at different locations. e.g., The 1st location should be visited between 8:00-12:00 at the first day (day 0). The 2nd location should be visited  between 10:00-14:00 within the first two days (day 0 or day 1).

I tried these ideas based on your code. But the result doesn't seem correct. I'd appreciate it if you could provide any guidance. Thank you so much.

https://github.com/ywang1110/tsp_multiple_days/commit/c1e5c2b387e185b5dd6a0b1ac875acc022464a48


Fix bug in construction of atom indices à la PDBInput

Fixes a bug in the construction of atom indices à la PDBInput that could cause two (or more) separate ligands to be accidentally grouped together if they share the same residue index but not the same chain index, leading to e.g., distogram atom indices being out-of-bounds for the total number of atoms in a complex.
N.b., for what it's worth, this was one of the trickiest bugs to identify to date. On AMD cards, all you'd get is a generic HIPError to go debug, with no reference to an out-of-index error in the e.g., distogram modeling code. On NVIDIA cards, you'd actually get the expected out-of-index error to trigger further debugging.

@Kaihui-Cheng ^

That's great! I think it works! Thank Alex and Lucidrains!

It's all Alex

Thanks! By the way,  lucidrains, it might be helpful to add a device parameter in cli.py. Currently, all inference is running on the CPU.

@Kaihui-Cheng ok done! let me know if it works or not

We might also need to move the input data to the device:
https://github.com/lucidrains/alphafold3-pytorch/blob/3e1795ea03d4d3956940ef3cefdd566c5e36911b/alphafold3_pytorch/alphafold3.py#L6338

@Kaihui-Cheng good catch, should work now

Yeah! it works!


⚠ Bofrost.de has degraded performance

In 2140657, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1060 ms

Resolved: Bofrost.de performance has improved in 0e6cbc6.


Update to 1.20.6

Mixins for individual option screens have been removed since renderBackground is no longer overriden. Instead, we inject the DrawContext with offsets only after this.renderInGameBackground(context); in HandledScreen.renderBackground.
render injections have also been removed from HandledScreen since they're already called in Screen.

Thanks Man, really wanted it updated
Its working on 1.21 too

Could someone send a ready build for 1.21?

@seriousfreezing
smoothgui.zip


Bump DSE version to 6.8.31 and OSS C* 3.x to 3.11.14

What this PR does: Bump OSS C* 3.x version to 3.11.14 and DSE version to 6.8.31. There is a separate PR to update the main branch here at https://github.com/stargate/stargate/pull/2357.
Which issue(s) this PR fixes: n/a
Fixes #: n/a
Checklist

[ ] Changes manually tested
[ ] Automated Tests added/updated
[x] Documentation added/updated
[x] CLA Signed: DataStax CLA

/gcburn

@msmygit the command is /gcbrun and it has to be run by a core contributor.

/gcbrun

/gcbrun

/gcbrun

This is good to get in as DSE-6.8.31 has Netty upgrades which will resolve at least 2 Snyk alerts.

This is also missing changes to persistence-dse-6.8/pom.xml... I think


Added a Push template registration using Jobject

Fixes #41

@pragnagopa @mamaso  Code updated as per feedback


useStorage: window is not defined

Describe the bug
Since beautiful-react-hooks v0.26.0, NextJS throws this error while building:
error - ReferenceError: window is not defined
    at Object.useStorage [as default] .../node_modules/beautiful-react-hooks/dist/useStorage.js:15:17)
    at Object.<anonymous> (.../node_modules/beautiful-react-hooks/dist/useLocalStorage.js:8:41)

The build fails.
To Reproduce
Steps to reproduce the behavior:

Install<EMAIL_ADDRESS>(or 0.26.)0
Build using<EMAIL_ADDRESS>
Expected behavior
Expect to build without errors.

thanks @laurensnl I'll look into it

thanks @laurensnl I'll look into it

Thanks! Let me know if you need more information.

@laurensnl thanks, the truth is: I think I know what I did wrong :)
I introduced this bug few days ago, sorry about that... I'll check as soon as possibile

@laurensnl I think I fixed it, please install 0.27.1
Please let me know if you find any other issue

Thanks for the quick fix @antonioru! Works like a charm!


Relicense to dual MIT/Apache-2.0

This pull request was automatically generated because my scripts detected that
everyone in the relicensing issue agreed to
relicensing.
License headers in files were not updated, if they exist. I've reproduced an
example license header below if you want to copy-paste it in. If you don't
have license headers, don't feel compelled to add
them.
// Copyright 2016 pcap Developers
//
// Licensed under the Apache License, Version 2.0, <LICENSE-APACHE or
// http://apache.org/licenses/LICENSE-2.0> or the MIT license <LICENSE-MIT or
// http://opensource.org/licenses/MIT>, at your option. This file may not be
// copied, modified, or distributed except according to those terms.

I recommend publishing a new patch version (the z in x.y.z) so that the
metadata propagates to crates.io.
Please be sure to check the README.md for style. I've try to
review these PRs as they go out, but I might miss something.
Thanks for relicensing!
(For my bookkeeping: this is repository id pcap-e522de9d-b757-4c49-bc08-41ddf68f9e74)

The test failures are being travis is being wonky. Thank you for your work on this.


[Android] VirtualizedList: Encountered an error while measuring a list's offset from its containing VirtualizedList

Environment
System:
OS: Windows 10 10.0.19042
CPU: (12) x64 AMD Ryzen 5 3600 6-Core Processor
Memory: 6.69 GB / 15.95 GB
Binaries:
Node: 16.13.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
npm: 8.1.0 - C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK:
API Levels: 26, 29, 30
Build Tools: 28.0.3, 29.0.2, 30.0.3, 32.0.0
System Images: android-30 | Google APIs Intel x86 Atom, android-30 | Google Play Intel x86 Atom
Android NDK: Not Found
Windows SDK: Not Found
IDEs:
Android Studio: Version 2<IP_ADDRESS> AI-203.7717.56.2031.7784292
Visual Studio: Not Found
Languages:
Java: 1.8.0_312 - C:\Program Files\OpenJDK\openjdk-8u312-b07\bin\javac.EXE
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.1 => 17.0.1
react-native: 0.64.3 => 0.64.3
react-native-windows: Not Found
npmGlobalPackages:
react-native: Not Found
react-native-pager-view : 5.4.6
expo: 43.0.3
Description
My nested flatList is not showing using pager view.
I have a parent vertical flatlist with an horizontal tab view child, and each tab view has a vertical flatlist but they are not displayed and error "VirtualizedList: Encountered an error while measuring a list's offset from its containing VirtualizedList." is shown.
react-native 0.64.3, react-native-pager-view : 5.4.6

Reproducible Demo

Create parent vertical FlatList
Add horizontal ViewPagerAndroid
Each tab has a vertical FlatList

I'm getting this one too... with the same setup.
I have yet to find a work around.
Does anyone know how this can be resolved?

There error under the hood is:
Trying to measure a view using measureLayout/measureLayoutRelativeToParent relative to an ancestor that requires custom layout for it's children (RNCViewPager). Use measure instead.
It has something to do with RNCViewPager but I have no clue what the "requires custom layout" means.

same error, any resolutions?


Footer Spacing needed under

This is Suryadipta , a little space under the "2022 Clueless" footer text is needed

Assign this to me @Rajdip019 will work on it

Work on this @myGlitches

Thanks , on it!

Hey @Rajdip019 this is done and sent a pull request

This issue is solved so closing this issue.


feat: Page or Modal to change the password

Modal with the tailwind implemetation

I agree with @PedroChaparro, I also feel that using a library is overkill, when a modal can be done with tailwind directly.

I think that you need to agree whether to use MaterialUI or style the page "manually" with Tailwind. It's just to keep the styles consistent across the page.

@MiguelMRojas Your review is pending here.

Sidebar component responsive
https://github.com/hawks-atlanta/frontend-react/assets/131629166/873ba9b1-e86c-42af-84c9-b0da642f9dd6

File component with dropdown menu
https://github.com/hawks-atlanta/frontend-react/assets/131629166/a344ff67-15b3-4fb4-96aa-7d4bc608ec01

Shouldn't the sidebar and the component file be in the same view?

What do you think?

@PedroChaparro

What do you think?

What do you mean?

Homepage

Mobile view

Update password implemented

Update password modal

Min length

Pattern

Password match

Pagination (Bottom right)

The main navbar does not come out, I think that adding the navbar component on each screen is a bad practice.

https://github.com/hawks-atlanta/frontend-react/assets/131629166/6d54cc7a-e90f-4cf1-b0d9-12ebf0825fae

Try to keep future PRs consistent to it's original purpose so that it can be properly reviewed and merged into dev. For any new features you may create a new PR.

💯. Additionally, please remember to maintain the current tests, updating them as needed, and add new tests when introducing new features. That will help to keep a sufficient coverage metric and prevent the features from breaking during development.

[!IMPORTANT]
@shoriwe, what should we do with this pull request? Please consider the following:

It's not clear how many features are included in this single PR.
There are two different navbars.
No new tests were added, and the previous tests are broken since Miguel's navbar was removed.
Styles are inconsistent. For instance, the login form uses a rounded button while the modal to update the password uses a square one.

Important @shoriwe, what should we do with this pull request? Please consider the following:

It's not clear how many features are included in this single PR.
There are two different navbars.
No new tests were added, and the previous tests are broken since Miguel's navbar was removed.
Styles are inconsistent. For instance, the login form uses a rounded button while the modal to update the password uses a square one.

Why old navbar was removed?

My only points will be create a new branch based on the last commit were this PR was working properly, then merge that branch to dev finally to main

Why old navbar was removed?

It seems that they're trying to use a different navbar for the user icon instead of updating the navbar state according to the user's session.

Even the height and colors are different.

I'm closing this pull request due to the reasons mentioned above.
@DanielEJaimes, please follow @shoriwe's advice. I recommend that you start by creating a new PR specifically for the files page, including the sidebar and file cards, but excluding the navbar (#31). After that, you both can decide what to do with the navbar and modal in separated PRs.


[material-ui] sx properties have inconsistencies when using class/object notation

Steps to reproduce
Link to live example: https://codesandbox.io/p/sandbox/elated-bhaskara-h7lfkm?file=%2Fsrc%2FDemo.tsx
No steps to replicate.
Current behavior
Certain MUI React components have differences in styling when using the object-class notation such as "MuiButton-root" to try and style certain root and sub-components of the whole component.
The live example shows that MUI Button's sx works only with the exact syntax "& .", and stops applying the styles when using the syntax "&."
However, the Slider does the exact opposite.
Expected behavior
I would expect that both patterns should be support in ALL component styling.
Context
Style components, and specifically their sub-components.

  Output from `npx @mui/envinfo` goes here.

System:
OS: macOS 14.3
Binaries:
Node: 18.17.1 - ~/.nvm/versions/node/v18.17.1/bin/node
npm: 9.6.7 - ~/.nvm/versions/node/v18.17.1/bin/npm
pnpm: Not Found
Browsers:
Chrome: Not Found
Edge: Not Found
Safari: 17.3
Vivaldi: 6.6.3271.50
npmPackages:
@emotion/react: ^11.7.1 => 11.11.1
@emotion/styled: ^11.6.0 => 11.11.0
@mui/base:  5.0.0-beta.23
@mui/core-downloads-tracker:  5.14.17
@mui/icons-material: ^5.3.1 => 5.14.16
@mui/material: ^5.10.0 => 5.14.17
@mui/private-theming:  5.14.17
@mui/styled-engine: ^5.3.0 => 5.14.17
@mui/styles: ^5.3.0 => 5.14.17
@mui/system:  5.14.17
@mui/types:  7.2.8
@mui/utils:  5.14.17
@mui/x-data-grid:  6.18.7
@mui/x-data-grid-premium: ^6.16.2 => 6.18.7
@mui/x-data-grid-pro:  6.18.7
@mui/x-date-pickers: ^6.19.0 => 6.19.0
@mui/x-license-pro:  6.10.2
@types/react:  18.2.37
react: ^17.0.0 || ^18.0.0 => 18.2.0
react-dom: ^17.0.0 || ^18.0.0 => 18.2.0
styled-components: ^5.3.3 => 5.3.11
typescript: ^4.5.5 => 4.9.5

Search keywords: sx class "&." "& ."

& . targets nested components within the element having that classname, while &. targets the element itself having that classname.


Error refreshing token

I noticed there is an error in the token refreshing code.
You are using the "Authorization": "Bearer " + access_token header but spotify wants you to use the "Authorization": f"Basic {token.decode()}" like is used your HttpClient.get_bearer_info function.
I worked around the problem by overloading User._refreshing_token with this code:
    async def _refreshing_token(self, expires: int, token: str):
        while True:
            import asyncio
            await asyncio.sleep(expires-1)
            REFRESH_TOKEN_URL = "https://accounts.spotify.com/api/token?grant_type=refresh_token&refresh_token={refresh_token}"
            route = ("POST", REFRESH_TOKEN_URL.format(refresh_token=token))
            from base64 import b64encode
            auth = b64encode(":".join((os.environ['SPOTIFY_CLIENT_ID'], os.environ['SPOTIFY_CLIENT_SECRET'])).encode())
            try:
                data = await self.client.http.request(
                    route,
                    headers={"Content-Type": "application/x-www-form-urlencoded",
                             "Authorization": f"Basic {auth.decode()}"}
                )

                expires = data["expires_in"]
                self.http.token = data["access_token"]
                print('token refreshed', data["access_token"])
            except:
                import traceback
                traceback.print_exc()

Also in I believe you want to change:
"Content-Type": kwargs.get("content_type", "application/json"),
to
"Content-Type": kwargs.pop("content_type", "application/json"),
in HTTPClient.request otherwise it errors when the content_type kwd is passed on.
I could do a pull request if you'd like.  I really like your library, its very pythonic and much easier to use than the other spotify libraries I tried.

Damn nice catch, yeah if you can submit a pr I can merge it immediately.
I don't have access to my machine atm so I won't be able to fix this for a couple of hours

Keep in mind, If I merge the changes will still have to wait until I can release them to pypi

Great, I'll take a stab at a pull request.  I've never done one before.  It will probably take me a day or two.
I was also thinking about the way you are implementing this... If I had lots of users connect to my app then I believe this would keep refreshing all their tokens indefinitely.  Is there a way to stop the refreshing if I'm done with the user?  I was thinking another way this could be done is to detect when an api call fails and do the refreshing then.  I'm curious how other oauth applications handle this.

User objects have a refresh attribute that is a read only reference to the task handling the session refreshing, you can stop refreshing a user's token by cancelling the task with User.refresh.cancel()
Currently there is no mechanism in place to deal with a refresh task failing part way, I'd recommend just creating a new user oauth http session and discarding the old user object in this case.
I haven't looked into how other apps handle this situation but if you can find alternatives I'm happy to consider them :)

Oh awesome, I didn't realize user.refresh was an _asyncio.Task and I can call cancel on it.  In any case I think its a mistake for me to be holding onto the User objects for so long.  I'm gonna think about it more next weekend.


add disconnected environment support to operator

This commit adds disconnected environment annotation to CSV and adds images required by CSV to relatedImages spec.
Signed-off-by: Umanga Chapagain<EMAIL_ADDRESS>

/test integration-test

/lgtm

/cherrypick release-4.12

/cherry-pick release-4.12


Data collection and preliminary exploration

(- (temperature dependent, too) -> consideration for later

avrg. nr of laps each tyre lasts -> do that for every circuit to get an idea)