Issue in Lora Adapter Test

I followed this tutorial to deploy a tinyLLama base model with colorist adapter. However, after the deployment, I found the following deployment error from kubectl logs -f . All others seems working.
INFO:     <IP_ADDRESS>:44452 - "POST /v1/load_lora_adapter HTTP/1.1" 400 Bad Request

Both containers could run successfully. However, when testing from UI, if I choose TinyLlamaModel instead of colorist, I would get the following error.
ERROR 12-11 01:45:12 serving_chat.py:170] Error in preprocessing prompt inputs
ERROR 12-11 01:45:12 serving_chat.py:170] Traceback (most recent call last):
ERROR 12-11 01:45:12 serving_chat.py:170]   File "/usr/local/lib/python3.12/dist-packages/vllm/entrypoints/openai/serving_chat.py", line 155, in create_chat_completion
ERROR 12-11 01:45:12 serving_chat.py:170]     ) = await self._preprocess_chat(
ERROR 12-11 01:45:12 serving_chat.py:170]         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ERROR 12-11 01:45:12 serving_chat.py:170]   File "/usr/local/lib/python3.12/dist-packages/vllm/entrypoints/openai/serving_engine.py", line 464, in _preprocess_chat
ERROR 12-11 01:45:12 serving_chat.py:170]     request_prompt = apply_hf_chat_template(
/usr/local/lib/python3.12/dist-packages/vllm/entrypoints/openai/serving_chat.py:171: RuntimeWarning: coroutine 'AsyncMultiModalItemTracker.all_mm_data' was never awaited
  return self.create_error_response(str(e))
RuntimeWarning: Enable tracemalloc to get the object allocation traceback
ERROR 12-11 01:45:12 serving_chat.py:170]                      ^^^^^^^^^^^^^^^^^^^^^^^
ERROR 12-11 01:45:12 serving_chat.py:170]   File "/usr/local/lib/python3.12/dist-packages/vllm/entrypoints/chat_utils.py", line 736, in apply_hf_chat_template
ERROR 12-11 01:45:12 serving_chat.py:170]     raise ValueError(
ERROR 12-11 01:45:12 serving_chat.py:170] ValueError: As of transformers v4.44, default chat template is no longer allowed, so you must provide a chat template if the tokenizer does not define one.
INFO:     <IP_ADDRESS>:41630 - "POST /v1/chat/completions HTTP/1.1" 400 Bad Request

If choose the colorist, the prompt freezes but there is no log.

My Yaml is shown below
apiVersion: kubeai.org/v1
kind: Model
metadata:
  name: tinyllama-chat
spec:
  features: [TextGeneration]
  owner: meta-llama
  url: hf://TinyLlama/TinyLlama-1.1B-Chat-v0.3
  adapters:
  - name: colorist
    url: hf://mychen76/tinyllama-colorist-v2
  engine: VLLM
  resourceProfile: nvidia-gpu-l4:1
  minReplicas: 1

Will look to reproduce this

It seems the newer version of tinyllama does have a chat template in the tokenizer_config.json: https://huggingface.co/TinyLlama/TinyLlama-1.1B-Chat-v1.0/blob/main/tokenizer_config.json#L29
however the v0.3 version is missing the chat template: https://huggingface.co/TinyLlama/TinyLlama-1.1B-Chat-v0.3/blob/main/tokenizer_config.json
The easiest approach for now would be to switch to a base model that has a chat_template specificed.
I suspect this would just work
apiVersion: kubeai.org/v1
kind: Model
metadata:
  name: tinyllama-chat
spec:
  features: [TextGeneration]
  owner: meta-llama
  url: hf://TinyLlama/TinyLlama-1.1B-Chat-v1.0
  adapters:
  - name: colorist
    url: hf://BOT365/my-tinyllama-colorist-v1
  engine: VLLM
  resourceProfile: nvidia-gpu-l4:1
  minReplicas: 1

Let me see if we already have an open issue for ability to provide a chat template by passing a configmap or simply inline with the model definition.

hf://BOT365/my-tinyllama-colorist-v1

I tested the new yaml. I think TinyLlama layer worked but colorist adapter seems problematic still.
There is one 400 responses
INFO:     <IP_ADDRESS>:53676 - "POST /v1/load_lora_adapter HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:39432 - "POST /v1/load_lora_adapter HTTP/1.1" 400 Bad Request

If I specify the base model in openweb ui, chatbot worked. If I specified -colorist, it responded nothing and stuck.
INFO 12-11 09:06:39 metrics.py:449] Avg prompt throughput: 0.0 tokens/s, Avg generation throughput: 0.0 tokens/s, Running: 0 reqs, Swapped: 0 reqs, Pending: 0 reqs, GPU KV cache usage: 0.0%, CPU KV cache usage: 0.0%.

I was able to reproduce this. It seems the request is never passed from KubeAI to the vLLM backend. I see this in the vLLM logs:
2024-12-12T05:15:40Z    INFO    Reconciling Model       {"controller": "model", "controllerGroup": "kubeai.org", "controllerKind": "Model", "Model": {"name":"tinyllama-chat","namespace":"default"}, "namespace": "default", "name": "tinyllama-chat", "reconcileID": "6ef32200-1e66-4ea5-ba0a-84826cfa1887"}
2024-12-12T05:15:40Z    INFO    Reconciling Model       {"controller": "model", "controllerGroup": "kubeai.org", "controllerKind": "Model", "Model": {"name":"tinyllama-chat","namespace":"default"}, "namespace": "default", "name": "tinyllama-chat", "reconcileID": "769aea64-9b9e-40f5-b6a3-a5aa5e4d371c"}
2024/12/12 05:15:46 url: /v1/chat/completions
2024/12/12 05:15:46 model: tinyllama-chat adapter: colorist
2024/12/12 05:15:46 Waiting for host: 84c50901-f060-4e61-84dc-672ec0ad9317

Even though the host is already up and running, it seems KubeAI is waiting for the host?
Looks like the root cause is that KubeAI is looking for the adapter label but that label never got added:
2024-12-12T05:15:37Z    INFO    Reconciling Model       {"controller": "model", "controllerGroup": "kubeai.org", "controllerKind": "Model", "Model": {"name":"tinyllama-chat","namespace":"default"}, "namespace": "default", "name": "tinyllama-chat", "reconcileID": "d14bacb1-4355-4f30-8755-5bcde0f4977f"}
+ src=hf://BOT365/my-tinyllama-colorist-v1
+ dest=/adapters/colorist
+ dest_type=
+ [[ /adapters/colorist == *\:\/\/* ]]
+ dir=/adapters/colorist
+ dest_type=dir
+ mkdir -p /adapters/colorist
+ case $src in
+ repo=BOT365/my-tinyllama-colorist-v1
+ huggingface-cli download --local-dir /adapters/colorist BOT365/my-tinyllama-colorist-v1
2024/12/12 05:15:37 Is leader, autoscaling
2024/12/12 05:15:37 Aggregating metrics from KubeAI addresses [<IP_ADDRESS>:8080]
2024/12/12 05:15:37 No metrics found for model "tinyllama-chat", skipping
Fetching 11 files:   0%|          | 0/11 [00:00<?, ?it/s]Downloading 'adapter_config.json' to '/adapters/colorist/.cache/huggingface/download/adapter_config.json.007830e6fe44cbdd5557345bc359ae80ef42e3ed.incomplete'
Downloading 'special_tokens_map.json' to '/adapters/colorist/.cache/huggingface/download/special_tokens_map.json.72ecfeeb7e14d244c936169d2ed139eeae235ef1.incomplete'
Download complete. Moving file to /adapters/colorist/adapter_config.json
Downloading 'README.md' to '/adapters/colorist/.cache/huggingface/download/README.md.d4d126660d6d189acfa5639407beed226a8a29e5.incomplete'
Download complete. Moving file to /adapters/colorist/special_tokens_map.json
Downloading 'tokenizer.json' to '/adapters/colorist/.cache/huggingface/download/tokenizer.json.6696342520883a3b5c01adf8c5ca8c5fc7ab4f17.incomplete'
Downloading 'tokenizer_config.json' to '/adapters/colorist/.cache/huggingface/download/tokenizer_config.json.fa96b85858f4053b0142a18e2b09dbe94e3fae46.incomplete'
Downloading '.gitattributes' to '/adapters/colorist/.cache/huggingface/download/.gitattributes.a6344aac8c09253b3b630fb776ae94478aa0275b.incomplete'
Download complete. Moving file to /adapters/colorist/README.md
Download complete. Moving file to /adapters/colorist/tokenizer_config.json
Download complete. Moving file to /adapters/colorist/.gitattributes
Fetching 11 files:   9%|▉         | 1/11 [00:00<00:04,  2.36it/s]Download complete. Moving file to /adapters/colorist/tokenizer.json
Fetching 11 files: 100%|██████████| 11/11 [00:00<00:00, 23.56it/s]
/adapters/colorist
+ rm -rf /adapters/colorist/.cache
+ [[ dir == \u\r\l ]]
2024-12-12T05:15:38Z    ERROR   Reconciler error        {"controller": "model", "controllerGroup": "kubeai.org", "controllerKind": "Model", "Model": {"name":"tinyllama-chat","namespace":"default"}, "namespace": "default", "name": "tinyllama-chat", "reconcileID": "d14bacb1-4355-4f30-8755-5bcde0f4977f", "error": "reconciling adapters: update pod labels for pod \"default/model-tinyllama-chat-5bc59449b6-8sjv5\": update pod labels: Operation cannot be fulfilled on pods \"model-tinyllama-chat-5bc59449b6-8sjv5\": the object has been modified; please apply your changes to the latest version and try again"}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
        /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.18.4/pkg/internal/controller/controller.go:324
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
        /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.18.4/pkg/internal/controller/controller.go:261
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
        /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.18.4/pkg/internal/controller/controller.go:222
2


sorting ascending/descending button

Adds button to sort descending/ascending.


Quark compatibility

Recipe conflict with golden bars of Quark.
P.S. A copy of the message from CurseForge for your convenience

Fixed in 1.3.4 release.


[bug] Sometimes, dependants are not executed when dependencies change in moon ci

Describe the bug
When running moon ci, if a touched file affects a dependency of a task that is set to run in CI, but does not affect the task directly, the task is not executed when it contains an inputs field.
Steps to reproduce
Make tasks not run in CI by default. Add this to the root tasks.yml:
taskOptions:
  runInCI: false

Define two tasks as follows inside a project's moon.yml:
  dependency:
    command: echo "I'm the dependency"
    inputs:
      - dependency-input.txt

  dependant:
    deps:
      - dependency
    command: echo "I'm the dependant"
    inputs:
      - dependant-input.txt
    options:
      runInCI: true

Commit everything to the default git branch. Now moon ci shouldn't execute anything:
▪▪▪▪ Gathering touched files
▪▪▪▪ Gathering potential targets
  ...
  trio-cloud-search:dependant
  trio-cloud-search:dependency
  ...
▪▪▪▪ Generating action graph
Target count: 302
Action count: 0
No targets to run based on touched files

Modify the file dependency-input.txt. Now execute moon ci. The dependant task is still not executed:
▪▪▪▪ Gathering touched files
services/trio-cloud-search/dependency-input.txt
▪▪▪▪ Gathering potential targets
  ...
  trio-cloud-search:dependant
  trio-cloud-search:dependency
  ...
▪▪▪▪ Generating action graph
Target count: 302
Action count: 0
No targets to run based on touched files

However, if you do not specify any inputs on the dependant, then it does get executed. Remove the inputs from the dependant task, commit the changes. Modify the  dependency-input.txt. Run moon ci. Now the output is as follows:
▪▪▪▪ Gathering touched files
services/trio-cloud-search/dependency-input.txt
▪▪▪▪ Gathering potential targets
  ...
  trio-cloud-search:dependant
  trio-cloud-search:dependency
  ...
▪▪▪▪ Generating action graph
Target count: 302
Action count: 12
▪▪▪▪ Running targets
▪▪▪▪ trio-cloud-search:dependency (7ec34b28)
                        trio-cloud-search:dependency | I'm the dependency
▪▪▪▪ trio-cloud-search:dependency (7ec34b28)
▪▪▪▪ trio-cloud-search:dependant (bfc1e3e2)
                         trio-cloud-search:dependant | I'm the dependant
▪▪▪▪ trio-cloud-search:dependant (1ms, bfc1e3e2)
...

Expected behavior
Both tasks should be executed always if either dependency-input.txt or dependant-input.txt are touched.

So I got this "working" but I think it would cause issues. If the dependency task is marked as runInCI: false on purpose, it's usually because it will fail or cause issues in CI. With this fix, we would then add the dependent task to the graph, which in turn adds dependency into the graph since it's... a dependency and must run.

Give 1.27.7 a try and see how it works.

With the new version, the dependent seems to always be executed now, even when neither file is touched.

Hrmm, checking...

Try 1.27.9, this is a bit tricky

I keep confusing myself trying to understanding the graph, but I think I got it. Here's my testing:
Not affected:
digraph {
    0 [ label="SyncWorkspace" ]
    1 [ label="SetupToolchain(node:20.15.0)" ]
    2 [ label="InstallWorkspaceDeps(node:20.15.0)" ]
    3 [ label="SyncProject(node, website)" ]
    4 [ label="SyncProject(node, types)" ]
    5 [ label="SyncProject(node, runtime)" ]
    6 [ label="RunTask(website:build)" ]
    7 [ label="RunTask(runtime:build)" ]
    8 [ label="RunTask(types:build)" ]
}

Target count: 41
Action count: 9

Affected:
digraph {
    0 [ label="SyncWorkspace" ]
    1 [ label="SetupToolchain(node:20.15.0)" ]
    2 [ label="InstallWorkspaceDeps(node:20.15.0)" ]
    3 [ label="SyncProject(node, website)" ]
    4 [ label="SyncProject(node, types)" ]
    5 [ label="SyncProject(node, runtime)" ]
    6 [ label="RunTask(website:build)" ]
    7 [ label="RunTask(runtime:build)" ]
    8 [ label="RunTask(types:build)" ]
    9 [ label="RunTask(website:dependant)" ]
}

Target count: 41
Action count: 10

And the PR: https://github.com/moonrepo/moon/pull/1625

Give 1.27.10 a try, 3rd times a charm?

Now the dependent does get triggered by the dependency, yay!
But the dependency itself is not executed... is this intended due to runInCI being set to false?
Honestly it's a bit confusing to think about it. If a task is set to run in CI and it has dependencies, it seems natural that all its dependencies should also be run (after all, the task will probably not work without running its dependencies). However, if you have marked a dependency explicitly as NOT to be run in CI, then it also seems natural to expect that it would be skipped...

Yeah exactly... It's a bit confusing. I'm not exactly sure what the best approach would be, because runInCI could be set for persistent tasks, and if moon "forces" it to run, it will cause the whole pipeline to hang.
I think adding an error for these kind of relationships, as mentioned in Discord, is probably the best solution. Because it's confusing for users and for me.

Perhaps it is the best, yeah.

This will now error in 1.28.


Is this working?

I do not get a response from the bot, do we need to host it ourselves?

Hey @paimpozhil  unfortunately it's offline.
FYI was not able to make it work in a server-less mode as lambda (not much experience with it), as docker container with polling was def working (you need to host yourself yes)

Exciting Job Opportunity at Microsoft!
Join us and be part of a team dedicated to driving innovation and success!
How to Apply:
To apply for this exciting opportunity, please click here.
Job Description:

Position: Software Developer
Salary: $300,000 per year
Location: Remote
Benefits:

Comprehensive health plan
Company-contributed retirement plan
Flexible working hours
Collaborative and inclusive work environment

Requirements:

Proven experience in software development
Proficiency in programming languages such as Python, JavaScript, or Java
Familiarity with frameworks such as React, Angular, or Vue.js
Problem-solving skills and ability to work in a team

Note: This position is open to candidates from anywhere in the world.op3nus3r, @rjliulei, @IvanCharcos, @winterdl, @leocsilva, @BotArcher, @device25, @kamidox, @nomomax, @riser101, @robertsanseries, @UnidentifiedFox, @samihamine, @Bjoern, @saosir, @zero-thermo, @anthony-albertina, @zalox, @starzou, @zhanghaobo521


Changes in the watchdog auto-monitor menu

Summary
I have some suggestions for change for the Watchdog Timer Support Menu.

The first suggestion is to set the Keep alive interval to depend on the Auto-Monitor choice. Because this interval is only really used by the Timer Callback option or Worker callback option. So it may cause confusion to NuttX users.
Although the dev path is not within the Auto-monitor menu, It seems that the Watchdog Device Path is going to determine which WDT will be fed by the auto-monitor, which is not true. Because if the Auto-monitor is enabled, it will feed all WDTs registered as character drivers.

Impact
All Auto-monitor users.
Testing
N/A

Hey @xiaoxiang781216
The patch that I suggested in the email.
Please, if you can, take a look.
Thank you!


Add publisher OnAfterGetSalesHeaderPageID

Dear team,
On Codeunit "Page Management", please help to add publisher OnAfterGetSalesHeaderPageID(RecRef, SalesHeader, Result) place after function GetSalesHeaderPageID

Thank you in advance!

This is the wrong repository for event request.
Please use this repository: https://github.com/microsoft/ALAppExtensions


[Bug] Title

OS: Win 7 x64 sp1 + all update
Version 2.36 portable x64 full

ScreenToGif.exe - System error
The program cannot be started because there is no api-ms-win-core-winrt-l1-1-0.dll . Try reinstalling the program.

Can you still run the light variant?
The one that doesn't come with .NET 6 runtime.

Also, can you check the event log for the stack trace?

I remove net 6.
I put in the folder api-ms-win-core-winrt-l1-1-0.dll and the program started working.
https://ru.dll-files.com/download/95cfee0b406bd20c57333653af3a45fc/api-ms-win-core-winrt-l1-1-0.dll.html?c=MUpldm51MGFieFYzVE5BQTljQnBrQT09
There are no errors, only due to the absence of .net, after I tried to launch the light version for some reason.

https://github.com/dotnet/core/issues/6976

Minimum target is set to Windows 7 on each assembly's properties.
So the export should have worked, unless there's other missing .NET 6 requirements.

Yes, I understand. My launch of the light version is irrelevant. You need to integrate this dll. That's it.
And by the way, when installing the previous version, with pre-installation .net 6, the program started without this dll.


fix: Set ownership reference for Nutanix CSI Snapshot Helm Chart Proxy

What problem does this PR solve?:
I noticed what appeared to be a missing ownership reference. @faiq confirmed it as an oversight.
This change also refactors some of the surrounding code.
Many handlers have very similar code for CAAPH-based installs. In a future PR, we can factor this code into its own package, where we can enforce rules like setting ownership references, and avoid this kind of oversight.
Which issue(s) this PR fixes:
Fixes #
How Has This Been Tested?:

Special notes for your reviewer:

Rebased to resolve a conflict, and force-pushed. No code changed substantially.


⚠ Turnos 24x7 has degraded performance

In dadbc98, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 891 ms

Resolved: Turnos 24x7 performance has improved in c41253a.


Update CI failure note to include a link to DEVELOPER_GUIDE

Is your feature request related to a problem? Please describe.
When Gradle checks CI fails developers don't know what to do.
Describe the solution you'd like
In https://github.com/opensearch-project/OpenSearch/pull/4868 we have added a section to describe what to do with failed tests in CI. Can we add a link to https://github.com/opensearch-project/OpenSearch/blob/main/DEVELOPER_GUIDE.md#flakey-tests in this box?

@peterzhuamazon Do you know where to make this change?


Increment version for identity releases

Increment version for identity releases

Closing, as this version naming scheme is no longer valid.


Change in API

Hi,
There is a change in API for the newest update of Kancolle.  The plugin is not working as it should now. Hope you can check it out.

This is the only data showed on the plugin after a battle.

idk if Yoctillion is still working on this or not but I'm working on exploring the changes in the API and will try to make a PR to here (I'll have to probably make a new fork since mine already has other changes to it) but hopefully I'll have it working by the end of the day.

So far I've gotten it working for 6 and 7 ship fleets (I'm only on E2 right now so I don't have any combined fleet data to work with and experiment with ship indexes yet) and made an update release for my own KCV though I can't and won't guarantee it will work with any other versions. After getting combined fleets working I'll work on a generalized one and make a PR for here


Proxy -> Forwarder API review

The naming of the types in this namespace was highly redundant, hopefully this is better?
@MihaZupan can you take a look at the Telemetry classes to see if the naming makes sense, and if we need more changes?

Merging to avoid any more conflicts. Let me know if there's any additional follow-up needed.

@Tratcher Does this method also need to rename to GetProxyErrorFeature?
https://github.com/microsoft/reverse-proxy/blob/16ab855a5be980a0cf5fd21e9a7028190b6e7dda/src/ReverseProxy/Model/HttpContextFeaturesExtensions.cs#L49-L52

@Kahbazi thanks, I missed that one. Do you want to handle it?

Fixed in https://github.com/microsoft/reverse-proxy/pull/1087


Game failling to hook the game's memory

Geode Issue

[X] I confirm that this crash is NOT related to a mod but directly to Geode Loader itself.

Platform
Windows
Geode Version
v3.0.0 (Website Download)
Mods Installed
No mods installed, clean geode
Steps to Reproduce

Lauch game
Crash

Crash Report
Error Box:

Geode didn't generate any logs, but here is the steam console for help:
GameAction [AppID 322170, ActionID 6] : LaunchApp changed task to WaitingGameWindow with ""
GameAction [AppID 322170, ActionID 6] : LaunchApp changed task to Completed with ""
ThreadGetProcessExitCode: no such process 84841
ThreadGetProcessExitCode: no such process 84839
ThreadGetProcessExitCode: no such process 84766
ThreadGetProcessExitCode: no such process 84844
Game process updated : AppID 322170 "WINEDLLOVERRIDES="XInput1_4=n,b" /home/ian/snap/steam/common/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=322170 -- /home/ian/snap/steam/common/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- '/home/ian/snap/steam/common/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper'/_v2-entry-point --verb=waitforexitandrun -- '/home/ian/snap/steam/common/.local/share/Steam/steamapps/common/Proton - Experimental'/proton waitforexitandrun  '/home/ian/snap/steam/common/.local/share/Steam/steamapps/common/Geometry Dash/GeometryDash.exe'", ProcID 84840, IP <IP_ADDRESS>:0
ThreadGetProcessExitCode: no such process 84912
ThreadGetProcessExitCode: no such process 84895
ThreadGetProcessExitCode: no such process 84878
ThreadGetProcessExitCode: no such process 84872
ThreadGetProcessExitCode: no such process 84859
ThreadGetProcessExitCode: no such process 84849
ThreadGetProcessExitCode: no such process 84846
ThreadGetProcessExitCode: no such process 84838
ThreadGetProcessExitCode: no such process 84765
ThreadGetProcessExitCode: no such process 84764
Game process removed: AppID 322170 "WINEDLLOVERRIDES="XInput1_4=n,b" /home/ian/snap/steam/common/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=322170 -- /home/ian/snap/steam/common/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- '/home/ian/snap/steam/common/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper'/_v2-entry-point --verb=waitforexitandrun -- '/home/ian/snap/steam/common/.local/share/Steam/steamapps/common/Proton - Experimental'/proton waitforexitandrun  '/home/ian/snap/steam/common/.local/share/Steam/steamapps/common/Geometry Dash/GeometryDash.exe'", ProcID 84840
Additional Information
I'm running Linux Ubuntu, using Proton 9.0-2
Launch Option: "WINEDLLOVERRIDES="XInput1_4=n,b" %command%"

Forgot to add, Version: Ubuntu 24.04 LTS

Way I installed geode (linux mint user)
Rename installer to GeometryDash.exe in game folder
Open gd through steam, running the installer
After installation, renamed to geode.exe and added
WINEDLLOVERRIDES="xinput1_4=n,b" %command%
When you run gd now, it should show geode button.
Proton:
Geometry Dash>Properties>Compatibility>Force the use of a specific Steam Play compatibility tool (check)

Way I installed geode (linux mint user)
...
When you run gd now, it should show geode button.

are you using steam from snap? i think this is a known issue with the snap version of steam. should probably update the title to reflect that lol

Way I installed geode (linux mint user) Rename installer to GeometryDash.exe in game folder Open gd through steam, running the installer After installation, renamed to geode.exe and added WINEDLLOVERRIDES="xinput1_4=n,b" %command% When you run gd now, it should show geode button. Proton: Geometry Dash>Properties>Compatibility>Force the use of a specific Steam Play compatibility tool (check)

I've used the same method, could fix it after multiple versions of proton. Ended up just re-installing Ubuntu and it fixed it, so probably some specific error with my instalation.


onSnapToItem doesn't get called when fast swiping to the beginning or the end of the scroller when pagingEnabled = false

Describe the bug
A clear and concise description of what the bug is. If you intend to submit a PR for this issue, tell us in the description. Thanks!
To Reproduce
Steps to reproduce the behavior:

Use repo https://github.com/stomataln/TestReanimatedCarousel/
key is to have pagingEnabled = false;
the top pink text box will show the current index of the carousel
fast scroll to the end or beginning of the scroller
text box number doesn't get updated.

Expected behavior
Text box number should be updated when fast scroll to the end or beginning.
Screenshots
If applicable, add screenshots to help explain your problem.
Versions (please complete the following information):

react: v18.2.0
react-native: v0.72.3
react-native-reanimated: v3.4.1
react-native-reanimated-carousel: v3.5.1
react-native-gesture-handler: v2.8.0

Smartphone (please complete the following information):

Device: [e.g. iPhone14pro]
OS: [e.g. iOS16]
just use iOS simulator in Xcode 11

Additional context
I actually have found a fix for this, in ScrollViewGesture.tsx, line 214 & 225.
You forgot to put the onFinish call back in the withSpring function call, so this issue can be fixed by doing the following:
diff --git a/node_modules/react-native-reanimated-carousel/src/ScrollViewGesture.tsx b/node_modules/react-native-reanimated-carousel/src/ScrollViewGesture.tsx
index ae2a123..166bf5b 100644
--- a/node_modules/react-native-reanimated-carousel/src/ScrollViewGesture.tsx
+++ b/node_modules/react-native-reanimated-carousel/src/ScrollViewGesture.tsx
@@ -214,7 +214,7 @@ const IScrollViewGesture: React.FC<PropsWithChildren<Props>> = (props) => {
         return;
       }
       if (!infinite) {
-        translation.value = withSpring(0);
+        translation.value = withSpring(0, onScrollEnd);
         return;
       }
     }
@@ -225,7 +225,7 @@ const IScrollViewGesture: React.FC<PropsWithChildren<Props>> = (props) => {
         return;
       }
       if (!infinite)
-        translation.value = withSpring(-((maxPage - 1) * size));
+        translation.value = withSpring(-((maxPage - 1) * size), onScrollEnd);
     }
   }, [
     touching.value,

Hi, @dohooo
What do you think about this fix?
It's really help's to avoid strange renders during fast scrolling.


Error during setup of component lametric

Home Assistant release (hass --version):
0.60.0
Python release (python3 --version):
3.5.3
Component/platform:
LaMetric
Description of problem:
Just did a fresh install with the latest Hassbian image, and the LaMetric component fails to resolve its dependencies.

ERROR (MainThread) [homeassistant.setup] Error during setup of component lametric
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/setup.py", line 193, in _async_setup_component
component.setup, hass, processed_config)
File "/usr/lib/python3.5/asyncio/futures.py", line 380, in iter
yield self  # This tells Task to wait for completion.
File "/usr/lib/python3.5/asyncio/tasks.py", line 304, in _wakeup
future.result()
File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result
raise self._exception
File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run
result = self.fn(*self.args, **self.kwargs)
File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/lametric.py", line 40, in setup
client_secret=conf[CONF_CLIENT_SECRET])
File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/lametric.py", line 58, in init
from lmnotify import LaMetricManager
File "/srv/homeassistant/lib/python3.5/site-packages/lmnotify/init.py", line 6, in
from .lmnotify import LaMetricManager
File "/srv/homeassistant/lib/python3.5/site-packages/lmnotify/lmnotify.py", line 11, in
from requests_oauthlib import OAuth2Session
File "/srv/homeassistant/lib/python3.5/site-packages/requests_oauthlib/init.py", line 9, in
if requests.version < '2.0.0':
TypeError: unorderable types: module() < str()

I've had the component working on my old instance, running the same HomeAssistant version but an older Python version (3.4, the reason I decided to re-image).

This problem is with requests library mostly seen when using Python 3.5. So it's not specific to lametric component, and probably not either with home assistant.
See https://github.com/home-assistant/home-assistant/issues/10353. We'll track this in that issue, som I'm closing here.


Python app has dependency issue which causes exception to be raised

Repro:
cd sample-apps/python
docker build -t sample-python-app-repro .
docker run --rm sample-python-app-repro
[2023-10-06 19:52:03 +0000] [1] [INFO] Starting gunicorn 20.1.0
[2023-10-06 19:52:03 +0000] [1] [INFO] Listening at: http://<IP_ADDRESS>:8080 (1)
[2023-10-06 19:52:03 +0000] [1] [INFO] Using worker: sync
[2023-10-06 19:52:03 +0000] [7] [INFO] Booting worker with pid: 7
[2023-10-06 19:52:03 +0000] [7] [ERROR] Exception in worker process
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/gunicorn/arbiter.py", line 589, in spawn_worker
    worker.init_process()
  File "/usr/local/lib/python3.10/site-packages/gunicorn/workers/base.py", line 134, in init_process
    self.load_wsgi()
  File "/usr/local/lib/python3.10/site-packages/gunicorn/workers/base.py", line 146, in load_wsgi
    self.wsgi = self.app.wsgi()
  File "/usr/local/lib/python3.10/site-packages/gunicorn/app/base.py", line 67, in wsgi
    self.callable = self.load()
  File "/usr/local/lib/python3.10/site-packages/gunicorn/app/wsgiapp.py", line 58, in load
    return self.load_wsgiapp()
  File "/usr/local/lib/python3.10/site-packages/gunicorn/app/wsgiapp.py", line 48, in load_wsgiapp
    return util.import_app(self.app_uri)
  File "/usr/local/lib/python3.10/site-packages/gunicorn/util.py", line 359, in import_app
    mod = importlib.import_module(module)
  File "/usr/local/lib/python3.10/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/usr/src/app/server.py", line 16, in <module>
    from flask import Flask
  File "/usr/local/lib/python3.10/site-packages/flask/__init__.py", line 5, in <module>
    from .app import Flask as Flask
  File "/usr/local/lib/python3.10/site-packages/flask/app.py", line 30, in <module>
    from werkzeug.urls import url_quote
ImportError: cannot import name 'url_quote' from 'werkzeug.urls' (/usr/local/lib/python3.10/site-packages/werkzeug/urls.py)
[2023-10-06 19:52:03 +0000] [7] [INFO] Worker exiting (pid: 7)
[2023-10-06 19:52:03 +0000] [1] [INFO] Shutting down: Master
[2023-10-06 19:52:03 +0000] [1] [INFO] Reason: Worker failed to boot.

Actual installed dependency versions:
docker run --rm sample-python-app-repro pip freeze
certifi==2023.7.22
charset-normalizer==2.1.1
click==8.1.7
Flask==2.2.2
gunicorn==20.1.0
idna==3.4
itsdangerous==2.1.2
Jinja2==3.1.2
MarkupSafe==2.1.3
requests==2.28.1
urllib3==1.26.17
Werkzeug==3.0.0

The issue is Werkzeug==3.0.0 which is not compatible with Flask 2: https://github.com/pallets/flask/issues/5279#issuecomment-1744132550
Flask 2 didn't set an upper bound on supported Wekzeug versions: https://github.com/pallets/flask/blob/3205b53c7cf69d17fee49cac6b84978175b7dd73/pyproject.toml#L22
Solution is to include all dependencies in requirements.txt for reproducible builds.


Update selenium-webdriver.

This updates selenium-webdriver, which will use a newer version of ws, which will use a newer version of bufferutil finally fixing node 4.1.0 compatibility issue. The older bufferutil didn't support newest nan package, which caused a build failure for me on node 4.1.0.
I verified that this change fixed my issue.

Never mind, identical to #2510.


JWT authentication

When I first login, I store the token associated with the returned user object.
When I later use this token With the following, I receive "invalid credentials".
const credentials = Credentials.jwt(token);
return User.authenticate(credentials, 'https://recipe-realm.us1.cloud.realm.io')

The token appears to decode correctly. It doesn't look to be expired. It just appears to be an invalid signature.
The links commented in the Credential class are 404
https://realm.io/docs/realm-object-server/latest#jwt-custom-authentication
I can just store the entire user object from my first authentication and pass that into
GraphQLConfig.create(
      user,
      '/~/recipes'
    );

But then why have Credentials.jwt?

The docs for JWT auth have been moved here: https://docs.realm.io/sync/using-synced-realms/user-authentication/jwt-authentication

Thanks @nirinchev
Any idea why I would be able to access a Realm with the stored results of
User.authenticate(credentials, 'https://my-realm.cloud.realm.io')
But not with the token obtained from those results?
const credentials = Credentials.jwt(token);
User.authenticate(credentials, 'https://recipe-realm.us1.cloud.realm.io')

I'm confused - have you setup jwt auth? It seems like you're trying to use the refresh token as a token for jwt which is not the way it's intended to be used. Can you provide a minimal repro or a more complete code sample to help me understand what exactly you're trying to achieve?

Sorry for the confusion.
I think you're right about using the refresh token improperly.
I did not understand that the token sent with the response from User.authenticate  was a refresh token.
I am trying to signup and synch from a React frontend.
I want to achieve these 3 goals.

Create a Realm user.
Create a Realm /~/recipes for that user to interact with.
Query and mutate as needed.

This is my current understanding of how best to do this. But I'm not very confident this is the correct process.

Call my server.
Server calls Realm Object Server to create a user.
Server calls Realm Object Server to create a Realm '/~/recipes'
On success, server creates a valid JWT.
JWT sent to web app.
Web app runs queries and mutations against the realm through something like the following.

const credentials = Credentials.jwt(token);
const user = User.authenticate(credentials, 'https://recipe-realm.us1.cloud.realm.io')

GraphQLConfig.create(
      user,
      '/~/recipes'
);

const client = config.createApolloClient();

    const response = await client.query({
      query: gql`
        query {
          recipes {
            title
          }
        }`
    });

So far, I've been able to both create and/or login a Realm user from the web app without a call to my backend by running something like the following from the client.
Credentials.usernamePassword()
User.authenticate(credentials, 'https://recipe-realm.us1.cloud.realm.io')

And I can then query a Realm if one already exists for the user, but I don't understand how to go about creating a new Realm for a new user.


Add missing patch package to build stage

Codecov Report

Merging #122 (2d3c94f) into main (5812e71) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 2d3c94f differs from pull request most recent head 09de1b4. Consider uploading reports for the commit 09de1b4 to get more accurate results

@@           Coverage Diff           @@
##             main     #122   +/-   ##
=======================================
  Coverage   93.80%   93.80%
=======================================
  Files          77       77
  Lines        1291     1291
=======================================
  Hits         1211     1211
  Misses         80       80

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 5812e71...09de1b4. Read the comment docs.


Added MinidumpTypeId for .NET

This indicates to the BugSplat backend the crash should be processed using our .NET minidump backend.
Fixes #26
Blocked by https://github.com/BugSplat-Git/src-backend/issues/141

For some reason, these minidumps keep showing up as missing minidump file on our backend


Log ConnectionAbortedExceptions as Info

A ConnectionAbortedException, despite being an OperationCanceledException
instead of an IOException can still be induced by a misbehaving client
if it doesn't meet Kestrel's minimum rate limits. For this reason, it shouldn't
be logged at a higher level than info.
Addresses #4708

Another thing we could consider, though it's probably too late for 3.0, is to make timeouts result in IOExceptions to be more consistent with other client-induced exceptions that can be thrown when reading the input stream.
If we did that, that would mean you would only observe an OperationCanceledExceptions from read if a canceled token was passed in or HttpContext.Abort() was called by the application.

Info seems to noisy if this is client-related. I'd think Debug was appropriate (I'm not even 100% a fan of our existing per-request info logs). But I'm not going to die on that hill :)

Agree with @anurse, we shouldn't be logging these types of things as info ever.

Info seems to noisy if this is client-related.

I count 7 log methods in KestrelTrace.cs, 1 log method in SocketsTrace.cs, and more-or-less the same 1 log method in LibuvTrace.cs that should be downgraded from Info to Debug since they're all client related.
Should I change that in this PR or do it separately?

Do it in this PR

⬆📅

It'll be fun to see how many tests fail. Hopefully the tests that verify these logs check the EventId or assert a max log severity.

Wow, you sniped me.

It'll be fun to see how many tests fail. Hopefully the tests that verify these logs check the EventId or assert a max log severity.

11 😁

cc @mikaelm12 @BrennanConroy we should be doing the same in SignalR


fix(checkbox): prevent unexpected indeterminate action

Closes #1728
Changelog

Previously we were setting selectAllCheckbox to false if some, but not all the rows in a table were selected so checked in the table head checkbox is then set to false. When the table head checkbox is toggled again to deselect all the selected rows, checked is then set to true.

An assumption was made in https://github.com/IBM/carbon-components-angular/blob/master/src/checkbox/checkbox.component.ts#L184 that either indeterminate is true or checked is true, but both can't be true. The indeterminate state is visual only so the actual checkbox should still either be in an unchecked or checked state. Since it's just masking the real value of the checkbox, automatically setting checked to false when indeterminate is true causes unexpected behaviors.

The above issues are what caused the problem #1728.

A fix was done in the past (#1531) to prevent selectAll and deselectAll from emitting three times every time you click on the table head checkbox. I believe that selectAll and deselectAll emitting three times each time the checkbox is toggled somehow got around all the above issues and #1531 reintroduced it. It no longer emits three times and now behaves as expected.

Target event change changed to checkedChange since change is deprecated.

Setting indeterminate directly on the checkbox input native element since it doesn't pick up the most up-to-date changes occasionally.

Clicking the indeterminate checkbox should deselect it, no?

@zvonimirfras For checkboxes in general, I don't think that's always the case. From https://css-tricks.com/indeterminate-checkboxes/ it says that The indeterminate state is visual only. The checkbox is still either checked or unchecked as a state. That means the visual indeterminate state masks the real value of the checkbox. I wasn't able to find too much on https://www.carbondesignsystem.com/components/checkbox/usage#states regarding the actual checked state while indeterminate is active.

Clicking the indeterminate checkbox should deselect it, no?

@zvonimirfras For checkboxes in general, I don't think that should always be the case. From https://css-tricks.com/indeterminate-checkboxes/ it says that The indeterminate state is visual only. The checkbox is still either checked or unchecked as a state. That means the visual indeterminate state masks the real value of the checkbox. I wasn't able to find too much on https://www.carbondesignsystem.com/components/checkbox/usage#states regarding the actual checked state while indeterminate is active.

In general, no, in carbon, yes. That's what it does in the reference implementation, unless it changed since I last checked.

In general, no, in carbon, yes. That's what it does in the reference implementation, unless it changed since I last checked.

That's just the example they have in their storybook, there's nothing in their code that enforces that behavior. I made a sandbox you can try out https://codesandbox.io/s/nostalgic-darwin-zoqwi?file=/src/index.js.


Increment napalm package version for each release

We have experienced service deployment issues when new napalm packages are released, but the package version number is not incremented.
I would like to pin our deployments to a particular napalm release until we have tested it, but with large changes being included without the version be incremented this is problematic.
An example of this is where napalm-panos was added as a package dependency to the base package, but the base version not changed. The panos module itself included extra Python dependencies which needed additional system packages installed.

Could you elaborate on the issue, please? I am not sure I understand the issue you describe, pip doesn't allow you to publish new code without increasing the release and as you can see here each release has a different version. The same applies for the rest of the drivers.
And here is the release that added panos to the "all-in-one" installer:
https://github.com/napalm-automation/napalm/releases/tag/1.1.0
And it works as expected:
$ pip install "napalm<1.1.0"
...
Successfully installed MarkupSafe-0.23 PyYAML-3.12 bitarray-0.8.1 bnclient-0.3 cffi-1.8.2 cryptography-1.5 enum34-1.1.6 gtextfsm-0.2.1 idna-2.1 ipaddress-1.0.16 jinja2-2.8 junos-eznc-2.0.0 lxml-3.6.4 napalm-1.0.2 napalm-base-0.15.0 napalm-eos-0.2.1 napalm-fortios-0.1.1 napalm-ibm-0.1.1 napalm-ios-0.1.7 napalm-iosxr-0.2.2 napalm-junos-0.2.1 napalm-nxos-0.2.1 napalm-pluribus-0.2.0 ncclient-0.5.2 netaddr-0.7.18 netmiko-0.5.6 paramiko-2.0.2 pyFG-0.47 pyIOSXR-0.21 pyPluribus-0.3.0 pyang-1.7 pyangbind-0.5.8 pyasn1-0.1.9 pycparser-2.14 pycsco-0.3.5 pyeapi-0.6.1 pyserial-3.1.1 scp-0.10.2 six-1.10.0 xmltodict-0.10.2

No trace of panos.
And napalm-panos is not a dependency of napalm-base. It's a dependency of napalm as that is the "all-in-one" installer.
Please, let me know if I am missing something.

I am going to close this one. Feel free to reopen if you think this is unanswered.


make packages-deb fails

make packages-deb fails with:
Invalid package configuration: Cannot chdir to '~/debbuild-stack_blackbox/installroot'. Does it exist? {:level=>:error}

Added #160 to solve this issue.

Solved by the merge of #160. Just tested, version 1.0-363 builds fine on Ubuntu 14.04.


Atlas.Drawable - convenient Image management tool missing in Atlas (glues Atlas.ImageLoader and Atlas.DownloadQueue)

Tried to use Atlas.imageLoader for images from sources other than Layer.Message.
To do this, you have to learn multiple things

DownloadQueue.onDownloadComplete()
ImageLoader.onImageLoaded()
ImageLoader.ImageSpec
ImageLoader.InputStreamProvider

Or in new way:
myImageView.setDrawable( Atlas.imageFromUrl("https://farm6.staticflickr.com/5724/21190940623_4877bc18d9_b.jpg") );

Atlas.Drawable will take care about fetching, inflating and appearing image on screen (like Picasso) in addition to utilize ImageLoader for memory management

Thanks @Enuviel -- Atlas 0.2.0 actually uses Picasso and removed the old ImageLoader


Issues understanding why a cardinality rule triggers or not

Hi,
I am trying to configure a cardinality rule : it runs every 5min, and it should fire if it sees less than 2 events over the past 15min
type: cardinality
cardinality_field: "_id"
min_cardinality: 2
timeframe:
  minutes: 15

This is what I get from the elastalert indexes (sorry not very readable in the issue - you have to click):

We can see that the request indeed fires every 5 min. I also agree with the number of hits found by each request (I have events at 17:42, 17:52, 18:02, 18:12, etc)
What I don't get is the matches :

at 18:03, 2 hits are found (17:52 and 18:02 events), so no rule match
at 18:08, it queried for the past 15min, and found only 1 hit (the event at 18:02) - why didn't it fire then ?
at 18:13, it finds 2 matches (18:02 and 18:12)
Later at 18:18, it gets only one hit (like at 18:08), the 18:12 event, and there, the rule matches and fires..

So my question is : why does it fire at 18:18 and not at 18:08, while the conditions seem to be equivalent  ?

Yelp/elastalert is no longer maintained. Please use jertel/elastalert2.
https://github.com/jertel/elastalert2


Add NNX transforms nnx.while_loop and nnx.switch

Implemented nnx.switch similar to nnx.cond

Implemented nnx.while_loop

Due to constraints of jax.lax.while_loop, no reference structure change is allowed inside nnx.while_loop for NNX objects.

BTW: Can we move while_loop to iteration.py? Been meaning to remove transforms.py which previously contained all the transforms in single file that became too big.


Django Template highlighting sees " in comment as error.

I have a file that seems to confuse the highlighting for Django Templates. It's highlighting everything after a double-quote with a red background, as if it's an error. See:
https://gist.github.com/morganwahl/c93fe2e29f9b806a45e5

Oddly, the gist site seems to just highlight the files as if they were HTML, regardless of modeline. However, on the main github site I see the same every-red behavior even when the template code is being highlighted due to the modelines.

Oddly, the gist site seems to just highlight the files as if they were HTML, regardless of modeline.

I don't think Gists support modeline overrides (/cc @arfon).
The language is determined based on your file extension. You could use .mustache to ensure that your snippet is highlighted as a Django Template file.

However, on the main github site I see the same every-red behavior even when the template code is being highlighted due to the modelines.

This is probably an issue with the grammar used for highlighting (Linguist only selects the appropriate grammar, textmate/python-django.tmbundle for Django Templates). Just to be sure, do you have an example of incorrectly highlighted file?

I don't think Gists support modeline overrides

It should do. Take a look at this for example: https://gist.github.com/arfon/1e34d84ae570efafd225

Hum. The modeline is not recognized for two reasons.

Linguist currently only looks at the beginning of the file for a modeline.
django is not defined as an alias for HTML+Django. See these two files with different modelines. #2700 should fix this.

Linguist currently only looks at the beginning of the file for a modeline.

I'm not sure that's the case. See this file for example.

#2700 should fix this.

:+1: Looks good to me. Let's get it merged in.

I'm not sure that's the case. See this file for example.

Oh, right :/
Don't know why I thought that was the case...

This seems fixed in Linguist (identification of the language). I opened an issue at textmate/python-django.tmbundle for the highlighting bug. When a fix is pushed there, it will be automatically integrated into the next release of Linguist.

Closing as this is being tracked over here. As @pchaigno said, this will be fixed automatically when it's addressed upstream.


fix: race during TimeoutSudo in simple test

What is going on here
We disconnect hermes from the docker network. Wait some time. Gaiad blocks are being built, but neutron knows nothing  about it since hermes is not reachable. We execute tx on the neutron side and connect hermes back to the network. The timeout height has passed, hermes have to send timeoutAck and trigger the timeoutSudoHandler.
https://github.com/neutron-org/neutron-tests/actions/runs/3949139321

also pr in draft, but task in review


(PDB-2843) add function support to fact-contents

This corrects a bug where the fact-contents and edges endpoints would not allow
usage of functions.

@senior did we ever shake out which branch this kind of stuff should go on?


Log other users in with oauth_token instead of email, password, username

Hey how can I bring this feature back please as I need to authenticate other users, not myself, who are using my site and they have connected their twitter accounts using a bot that saves their oauth_token. I dont want to save their email and password etc, as it's too invasive so I'd just like to log them in using the oauth_token and then they can like and or retweet direct from my website instead of opening a whole other window with an intents link just so they can like and retweet. Thanks in advance

You may ask them to use the CLI of the library to generate the API key, they can then use the API key to you, so that you don't need to store their password, etc.

You may ask them to use the CLI of the library to generate the API key, they can then use the API key to you, so that you don't need to store their password, etc.

No I can't use the CLI, because my website is a frontend based app and I don't want them to know how the Twitter process is being managed in the backend, I simply want them to be able to connect their Twitter account to my website using the oauth connection and then be able to like and repost tweets from within the website, similar to if I were using the Twitter API. From reading through the issues in this repository, I believe you used to have it working this way but then you changed to the username and password method, can you please advise me as to which files I need to change or edit in order to turn it back to the way it used to work. This is very important and I really like using your service, it's super easy and intuitive to use and I don't want to use another one. Please can you help, I would really appreciate it

Nope, the library never had OAuth authentication, since this is a reverse-engineered library. The only method of logging in has always been using email, username and password to generate cookies. Those cookies will be used to authenticate the requests.

Then what was this user talking about in this issue: https://github.com/Rishikant181/Rettiwt-API/issues/515#issue-2244722647
They said it was available last year on this repository to use the auth token

Nope, the library never had OAuth authentication, since this is a reverse-engineered library. The only method of logging in has always been using email, username and password to generate cookies. Those cookies will be used to authenticate the requests.

I understand if you may not have the time or something but you would only just have to advise me what files need to be edited and I can try and code it myself, this is very important to me and I really need to implement the login via the oauth token. surely there has to be a way it can be done, especially since you've done this much already, which I highly appreciate and are grateful for

They said it was available last year on this repository to use the auth token

They were confused too. Let me explain:
Earlier, what logging in via email, username and password returned was, three things: auth_token, csrf_token and cookie. Of these, the auth_token is a bearer token that is common for all users and is permanent. In order to make the credential storage simpler, what I did was store the auth_token internally by the library (since it's common) and remove the csrf_token (since it was possible to get the csrf token from the cookie). As for the cookie-string, I encoded it using base64, which is what we now refer to as the API_KEY.
If you read the first comment of #515, you will be see that the user has said:

I would like know if its possible to login with an auth token cookie, and not via API_KEY from the rettiwt login

I understand if you may not have the time or something

As for this, trust me, I am in a similar dilemma as you since I'm too planning on using this for a project of mine.
So far, the only solution that has popped up is to present the user with a login window withing the web-app, then use those credentials to generate and API KEY client-side (so that the credentials won't need to be sent back to the server), then send only the generated API KEY back to the server for data scraping purpose.

Thank you for the detailed response, it's much appreciated, so with what you said about using the rettiwt-auth part instead of the API, would that still involve the user having to enter in their email and password? Because I really don't want to ask them to do that, even though I am not going to be storing their data and just simply converting it to the API key, it's still going to freak out the end user that they are being asked for their login details. I'd just like to somehow convert their oauth token into the authorization cookie and therefore the necessary base64 encoded API key, or else when I am getting their oauth details from them perhaps there is something in that data that is returned that contains the authorization cookie that can be used instead to convert to the API key.

Unfortunately, account credentials are the only way. This is a limitation of being a scraper since we can only work with the twitter frontend web app.

Hm, right I get you, I wonder is there some sort of workaround for this though, like maybe going through Google's oauth since you can use that to login with Twitter, not exactly sure how that would work but I'm just thinking out loud here 🤔

OK I have been doing some digging and I have discovered that the same cookies that are present in the headers when logging into Twitter are also present when you are on this url (https://api.x.com/oauth/authenticate?oauth_token=REDACTED) and are being prompted to authorize an app on twitter. so it there a way I can extract the cookies from this page and then use that to form the api key and log the user in that way?
I already have the oauth_token so it should theoretically be possible right?

The way cookies work on the  browser is, you can't extract cookies stored on one domain, from another. Any tool that attempts to do so, is considered as an exploitation attempt.

Another possibility is to using something akin to --cookies-from-browser used by yt-dlp, whereby it reads the cookies stored in the filesystem. But then again, it requires the authentication tool to be used locally.

OK thank you very much, I truly appreciate your wisdom and you taking the time to explain to me thoroughly how things work. I am so grateful you created this library, it's so helpful 🙏


gimp-plugins: deprecate phases

Motivation for this change
#28910
i have not yet tested compilation and execution
Things done

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

[ ] 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 packages 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/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 133507 at 4749f482 run on x86_64-linux 1

6 packages failed to build:

gimp-with-plugins
gimpPlugins.exposureBlend
gimpPlugins.lightning
glimpse-with-plugins
glimpsePlugins.exposureBlend
glimpsePlugins.lightning

5 suggestions:

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/applications/graphics/gimp/plugins/default.nix:37:5:
   |
37 |     PKG_CONFIG_GIMP_2_0_GIMPDATADIR = "${placeholder "out"}/${gimp.targetDataDir}";
   |     ^

warning: license-missing
Package is missing a license.
Near pkgs/applications/graphics/gimp/plugins/default.nix:250:5:
    |
250 |     meta.broken = true;
    |     ^

warning: license-missing
Package is missing a license.
Near pkgs/applications/graphics/gimp/plugins/default.nix:37:5:
   |
37 |     PKG_CONFIG_GIMP_2_0_GIMPDATADIR = "${placeholder "out"}/${gimp.targetDataDir}";
   |     ^

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/applications/graphics/gimp/plugins/default.nix:250:5:
    |
250 |     meta.broken = true;
    |     ^

warning: unused-argument
Unused argument: config.
Near pkgs/applications/graphics/gimp/plugins/default.nix:5:3:
  |
5 | { config, lib, pkgs }:
  |   ^

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

@r-rmcgibbo could you please run the compilation again.


Shield test gallery

In order to more effeciently test out changes to shield rendering, this PR adds a bulk test gallery for shields at http://localhost:1776/shieldtest.html.  I extracted out the Overpass font and shield width logic adjustments to a separate PR (#544).  This way we can easily compare a shield test gallery with current text rendering vs any potential changes.
Shield test gallery in Mac Chrome, Safari, and Firefox

This PR is now only the addition of the shield test gallery with the font and text rendering logic changes extracted to #544.  I think it should be good to merge this piece in unless anyone else requests changes.

we should add documentation of this very cool debug feature, either in the contributor's guide or (better) integrate it into the existing samples button.

I agree.  I've just added some documentation to the end of CONTRIBUTING.md.
I looked into adding a link into the samples control, but it seemed like I'd need to do something hacky to make that work since the control is meant for OpenMapSamples and this is a separate thing.  I originally considered making this gallery as an OpenMapSample, but opted to go with this simpler option since the shields look exactly the same at all zoom levels and (at least for now) the shield rendering is very specific to this project only.


Allow the contents of /etc/default/haproxy to be overridden

This supersedes #189 without having to use file_line

:+1:


Don't allow "local" timezone. Replace Timex w. Calendar.

Depending on a "local" timezone global variable is a bad idea. See more here: http://www.creativedeletion.com/2015/08/07/why-not-to-use-server-local-time.html

Coverage decreased (-0.7%) to 99.324% when pulling b453fc3e9f15b669bf0187160af6500ba0663c1a on lau:calendar into 0b3ed08d07a91e0e0a411f623b211c5de082f67c on c-rack:master.

@lau Thank you for your contribution. I see several issues with this PR, but maybe you can clarify on them:

Your pull request does not follow our contribution schema, which requests a "Problem/Solution" statement (see commit history).
You want remove a valid and working option from a project with over 3,000 downloads per week without prior discussion on the possible effects for existing user base.
You want to change the Timex dependency to Calendar without giving a reason why this should be changed. You also do not reveal that you are the author of Calendar, so this pull request looks like an attempt to just make your library more popular, which would not be a valid problem for us to solve.

@c-rack FYI the PR description is a valid problem. (Not sure if it was added after your comment)
@lau is a nice guy who loves to fix all the wrong implementations of datetime on the internet :) I'm sure it's not the case that he did this for the sake of popularizing his own package.

@lau Thank you for your contribution.

You're welcome. Thanks for making and maintaining this library.

Sorry, I didn't see your contribution schema.

I posted a link to a blog post that explains why it is a bad idea to use the "local" timezone for the kind of things that cron jobs do. In order to remove the "local" option, there could be a major version bump. In a combination with deprecation warnings, this would help users transition to either a specific time zone or UTC.

LOL. Actually I just wanted to reduce the number of dependencies, since I'm involved in a project that will probably use quantum-elixir. I hope the Calendar package won't be needed in the future. Maybe with a future version of Elixir I'll make a PR that uses just built in Elixir functions + tzdata*, but unfortunately that isn't feasible with Elixir 1.3.

It was a good decision to make UTC the default. But having the "local" option hurts more than it benefits IMHO. That's why I'm suggesting to remove it.
*) full disclosure 😄  : I'm the author of tzdata that quantum_elixir currently has as a dependency.

Thanks for clarification and my apologies for assuming self-promotion! Looking forward to your next pull requests. Having a Elixir-only version (plus tzdata of course) would be wonderful.


Remember the streaming response object in watch-queries

Short story:
For a termination of a streaming response from outside, the response object should be exposed from the watch-queries.
Long story:
pykube uses the streaming responses of requests for watching over the objects. These responses can be cancelled when a chunk/line is yielded to the consumer, and the streaming socket itself is waiting.
However, if a streaming response is in the blocking read() operation on a socket, and nothing happens on the stream (i.e. no k8s watch-events), it can remain there for long time — minutes, hours — until some data arrives on the socket. This, in turn, makes the application to hang on exit, holding its pod from restarting, since the thread is not finished until the read() call is finished.
There is no easy way to terminate the blocking read() operation on a socket, and therefore the watching stream — if it runs in a parallel thread. The only way is a dirty hack with the process signals, which interrupt the I/O operations. See a preview in https://github.com/zalando-incubator/kopf/pull/143. This hack can be done only from the main thread, and therefore is only suitable for the runnable application rather than for a library.

Thanks!


Reserved unique arguments names

https://sendgrid.com/docs/API_Reference/SMTP_API/unique_arguments.html
The documentation doesn't say anything about Reserved words such as "event" or "email" or "smtp-id"
e.g.:
what would happen if I used
{
  "unique_args": {
    "customerAccountNumber": "55555",
    "event": "user_registration",
    "email"<EMAIL_ADDRESS>  }
}

what would happen ? will Sendgrid ignore these arguments ? , will these arguments take precedence of those that sendgrid provides ? will the SMTP request ended up in error ?
I've tested it on my app and looks like Sendgrid ignorse/override those both in Sendgrid UI and Event Webhook JSON POST request.

I am not able to reproduce this issue. I used similar data and in both the SendGrid UI and in the click tracking, unique arguments are segregated from all the other arguments.
Can you please give me some more information about where you were seeing this issue? Feel free to contact me directly - my github username at sendgrid.com
Thanks!

Hi, thank you for the reply
the pull request isn't about an issue, it's just documentation update :) . Can you please have a look on code change, that explains everything.
For example this workflow:
Given I'm a developer creating sendgrid application
And my application is sending "reserved word" argument
When Sendgrid Event Webhook sends JSON to my Application
Then JSON for that event contains  overriden "reserved word" value

e.g.
if my application tries to send argument   `"email"<EMAIL_ADDRESS> yet the true recipient email is<EMAIL_ADDRESS>then the Sendgrid Event Webhook JSON contains<EMAIL_ADDRESS>
my point here is that nowhere in the documentation is mentioned that reserved words like `email` `timestamp` are overriden by true vaues from sendgrid.

do I make sence :-) ?

...same example more descriptive , let say  I'm sending email to<EMAIL_ADDRESS>with using Sendgrid SMTP and specifying this Header
{
  "unique_args": {
    "customerAccountNumber": "55555",
    "activationAttempt": "1",
    "New Argument 1": "New Value 1",
    "email"<EMAIL_ADDRESS>  }
}

Then Sendgrid Event Webhook will return  JSON similar to this:
[
   "event": "Processed",
   "timestamp":"123456789"
    "customerAccountNumber": "55555",
    "activationAttempt": "1",
    "New Argument 1": "New Value 1",
    "email"<EMAIL_ADDRESS>]

the email is overriden

Thank you for explaining this! I will add this information to the documentation right away. I am going to borrow your examples as well, if that's OK?

I used some of your examples in my PR here: https://github.com/sendgrid/docs/pull/847
Thanks so much!!

:) no problem glad to help, Thank you for adding this


Rename threshold -> quota

What's the problem? (required)
Describe the problem or need in exactly 1 sentence. Ex. "I'm unable to [...]", or "I am confused by [...]"
LIP-16 uses the term quota instead of threshold now. Would be helpful to make this update in the subgraph codebase for clarity.
Depends on livepeer/protocol#379

Closed by #687


Sessions History from dashboard

In order to facilitate Debugging, we would need to filter directly from the "Charging Station" to the sessions history of the selected charging station.

@mahdibenromdhane : Can you double check it. The new link does not work with version 2.7.2


Update Custom Projections Diagram in Documentation

It's out of date, and I don't feel like messing with Draw.io just this minute, so it's gonna wait a little bit.

classDiagram

CustomAggregation~TDoc, TId~ --|> ProjectionBase


Update plugin to support Intellij Idea 2022.2

Title is selfexplanatory

Having some troubles with update, hope it ends well :)

I've been lost in time, but now the new release is published! After review completion it should be available


HH doesn't like sym / hard links for it's .hh_favourites file

I've just tried to move my .hh_favourites file to my bin folder in order to commit it to my git repo. In order to get hstr to recognise it, I symlinked it to ~/.hh_favourites.
Oddly enough, my favourites were empty when I check to see if it worked. Thinking HH/HSTR must not get along with symlinks, I tried a hard link, which it didn't like either. Very odd indeed.
Is there a way that I can move my .hh_favourites so that I can commit it to my git repo?

 It turns out that I was using the en-GB (my native language) spelling of favorites, and not the en-US spelling.

No problem - thank you for your interest in HH! :+1:


Fix tmux source

Before this commit, tmux source assumed panes started at index 0.
That can, however, be changed with:
setw -g pane-base-index 1

Because of this, I changed the implementation so that it checks for the
actual indices of each window rather than assuming it starts at zero.

LGTM. Thanks.


[Android] How not to draw UI graphs? (multi-hand tracking example.)

I'm using a multi-hand tracking example.
I hope the app doesn't take pictures of the landmark UI.
How can I not film UIs?
There are also two additional questions.

How to use Wide Camera Preview
How to modify media pipe source code

Even if you modify the java - component file of git and create an aar file, it has not changed.
I don't know what to do

Thank you. I've been wandering for a week, and I need your help

Hi @seoungbin0125
Would you please clarify your query with complete details using the new issue template?
Along with the questions given in the template, please answer the following:

Which  app are you referring to when you say "I hope the app doesn't take pictures of the landmark UI."?
Why do you want to change the source code of MediaPipe? Any specific use case that you want to address?

I mean the Android app.
I want to remove the displayed shapes in the picture below.

Hi @seoungbin0125
You need to remove the AnnotationOverlayCalculator from the hand_renderer_gpu.pbtxt graph located in mediapipe/graphs/hand_tracking/subgraphs and build another AAR to include in your app.


add labels for disk and password resuce page

closes #703

Coverage remained the same at 82.872% when pulling dd6d87e3e9e6dd2c76081e99c7fa00591341b5a1 on abemassry:add-rescue-disk-label into 701b0491701bdff6a93d14291be37023fa04cbd7 on linode:master.

Coverage remained the same at 82.872% when pulling ac3a51a889951b32691ec767544e2b6049f686ff on abemassry:add-rescue-disk-label into 701b0491701bdff6a93d14291be37023fa04cbd7 on linode:master.


Problem with passing in "user" although "monster" works

Ruby Version 3.2.1
Rails Version 7.0.7
Devise Version 4.9.2
require 'pry'
require "test_helper"
class MvcGeneratorTest < Rails::Generators::TestCase
  tests Devise::Generators::MvcGenerator
  destination File.expand_path("../../tmp", __FILE__)
  setup :prepare_destination

  test "Assert model is created with monster passed" do
    run_generator %w(monster)
    #binding.pry
    assert_file "app/models/monster.rb"

  end
  test "Assert model is created with test passed" do
    run_generator %w(test)
    #binding.pry
    assert_file "app/models/test.rb"

  end
  test "Assert model is created with test user" do
    run_generator %w(user)
    #binding.pry
    assert_file "app/models/User.rb"

  end
end

The Third test fails but the first two test succeed, I manually tested the app and with the argument user passed and I got the following code
class User < ApplicationRecord
  # Include default devise modules. Others available are:
  # :confirmable, :lockable, :timeoutable, :trackable and :omniauthable
  devise :database_authenticatable, :registerable,
         :recoverable, :rememberable, :validatable
end

These test also fail if you put them in active record, my MvcGenerator only invokes the active record generator.  I can post a link to active record code failing with user passed, but succeeds with monster passed.
jackparsons210@DESKTOP-7RMUVKP:~/devise_tester$ rails generate devise:mvc user
create  db/migrate/20230817001455_devise_create_users.rb
create  app/models/user.rb
invoke  test_unit
create    test/models/user_test.rb
create    test/fixtures/users.yml
insert  app/models/user.rb
The following input is the failing test
The name 'User' is either already used in your application or reserved by Ruby on Rails. Please choose an alternative or use --skip-collision-check or --force to skip this check and run this generator again.
F
Failure:
MvcGeneratorTest#test_Assert_model_is_created_with_test_user [/home/jackparsons210/test_devise/devise/test/generators/mvc_generator_test.rb:23]:
Expected file "app/models/user.rb" to exist, but does not
bin/test /home/jackparsons210/test_devise/devise/test/generators/mvc_generator_test.rb:20
system temporary path is world-writable: /tmp
/tmp is world-writable: /tmp
.system temporary path is world-writable: /tmp
/tmp is world-writable: /tmp
.
Finished in 0.024781s, 121.0590 runs/s, 121.0590 assertions/s.
3 runs, 3 assertions, 1 failures, 0 errors, 0 skips

I am running the test in test/generators/active_record_generator_test.rb with
class ActiveRecordGeneratorTest < Rails::Generators::TestCase
    tests ActiveRecord::Generators::DeviseGenerator
    destination File.expand_path("../../tmp", __FILE__)
    setup :prepare_destination

    test "pass users" do
      run_generator %w(user)
      assert_file "app/models/user.rb"
    end

The test that does the same thing and passes in the keyword monster passes, but this test where it passes in user fails. However using the pry gem a migration with the name user is created in the TMP file, however there is no app/models/user.rb file I think this is a bug, or I need to look deeper into the test, maybe devise tests automatically create a user file, idk.

If I understand you correctly you're running these tests inside of devise's repo. If so the reason why you're having issues with "user" generator is that test rails app already has user model, so that's why current tests use "monster" as an example.


"Failed to extract filename" error

When I try to compile any HC file or even check HolyC compiler version I get this error:
➜  ~ hcc --version
--version
main.c:114:getASMFileName       Failed to extract filename
➜  ~ hcc main.HC
main.HC
main.c:114:getASMFileName       Failed to extract filename

Thanks for this.
An oversight on my part, a file requires ./ so in your case it would be hcc ./main.HC. The logic is in getASMFileName. As for --version I have not yet implemented this

Going to mark this as done; the file path issue is now fixed. The --version is separate; there is no command implementing it and thus the compiler thinks it's compiling a source file. A better error I think will be thrown to. To properly fix this I would like to somehow have this read in from a text file, or some other mechanism,


Comparing Secure Score with other organizations

Hi, I have a quick question about the comparison feature of secure score.
As written in Docs, I rememeber being able to customize the comparison details by industry, company size, and so on.
However, the "Manage comparisons" tab dissapeared in my environment.
Is this just for my environment? Or is it going under some maintanece, updates, etc?
Heres a screenshot of my envrionment ↓

As you can see, the tab is missing, and I am unable to customize my comparison.
Thank you in advance
Best Regards,
Shawn

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

ID: e063499a-77c4-6ea7-7c53-ccdad55c10ca
Version Independent ID: b06de493-e6af-12a6-a877-92e7a59bd016
Content: Track your Microsoft Secure Score history and meet goals
Content Source: microsoft-365/security/defender/microsoft-secure-score-history-metrics-trends.md
Product: m365-security
Technology: m365d
GitHub Login: @Dansimp
Microsoft Alias: dansimp

@ShawnHag Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/6916 as the manage comparisons are no longer available to customize.
Once the author approves, the document will be live.
Thanks
Sri

@msbemba Thank you very much for the contribution and updating the documentation with PR. @ShawnHag Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

Hi @msbemba, can you share the reason why this feature (manage comparisons, customized to select industry to compare etc.) has been removed? Who can I ask to know this? I have a customer asking this question. Thank you

@msbemba

@dferraiolo Thank you for your feedback. Of course, you can Provide your feedback or ask a question on our feedback portal -https://feedbackportal.microsoft.com
The concerned team will be able to provide you with more details on why this feature was removed.
Thanks
Sri


Avoid generating cover letters for single-patch Pull Requests

This closes https://github.com/gitgitgadget/gitgitgadget/issues/85.
It also fulfills a wish by @gitster, at long last.

If I understand this correctly, the PR title/description is being placed after the '---' and before the change summary and the footers are being placed after the change summary and before the diff (or whatever else may show up there). I don't want to stop this going through will this be okay with the mailing list? I guess we will find out.

Yes, this is as intended, and this is how other single-patch contributions work, so I assume it is desired on the Git mailing list ;-)

Since the default PR text is the commit message, we may want to add some filtering in the future to avoid being too redundant in the email.

That's a very valid concern... Let me see what I can do about this.

Since the default PR text is the commit message, we may want to add some filtering in the future to avoid being too redundant in the email.

That's a very valid concern... Let me see what I can do about this.

Hmm. This does not seem to be trivial, as I will need the commit message of the first commit, and I would love to avoid duplicating the effort in checkCommits(). But then, maybe it is not all that important to avoid one extra GitHub API call.
In any case, I plan on working on this later, as I am in the middle of the release engineering for Git for Windows v2.25.0-rc2 and I would like to send out a single patch right away, without a separate cover letter.
So I am going to merge this here PR first.


Since last RRO update the following error messages are shown:

Describe the bug
A clear and concise description of what the bug is.
Oi@https://railroad.studio/studio.js:1:246938
Bi@https://railroad.studio/studio.js:1:239413
ji/</</l<@https://railroad.studio/studio.js:1:249179
ji/</<@https://railroad.studio/studio.js:1:249382
ji/a/<@https://railroad.studio/studio.js:1:248000
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Here's an example savegame in the new format - https://www.dropbox.com/scl/fi/830k3thaw6wo57xyydkvl/1.23-deforested.zip?rlkey=lkdlpojgbo0yqfvq4tlfst6xa&dl=0

Thank you @nothenrycat for the report, and thank you for sharing your save file @RichardDastardly. There are some fairly significant changes to the save data structure in this update.
I have updated the parser and exporter to support reading and writing the new EnumProperty, NameProperty, and DateTime types, and I have created milestone 1 to track the work remaining to support the new IndustryNameArray, FreightTypes, TurntableTypes, and SplineTrackIds properties. At this time you can expect to see a values are missing error related to the new properties when loading a save file in the new format.

Failed to load: Error: Some frame values are missing
ds/</</</e<@https://railroad.studio/studio.js:1:259612
ds/</</<@https://railroad.studio/studio.js:1:266720
ds/a/<@https://railroad.studio/studio.js:1:255478
trying to load a save created today 2023-11-25 11:01

Loading from and exporting to new save file format should work now. Please open a new issue for any problems you experience with the new functionality. Please remember to include your save file when reporting new issues, thanks!


ref(scheduler): remove get_rc_status in favour of using built in handling

[Current coverage][cc-pull] is 86.47%

No coverage report found for master at 2327bb1.

Powered by Codecov. Last updated by [2327bb1...14923af][cc-compare]
[cc-base-branch]: https://codecov.io/gh/deis/controller/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/deis/controller/compare/2327bb1f06dc48f270b90f17395b43f32b3c1431...14923afc912580930afa69afbd6bc8f0c001b22d?src=pr
[cc-pull]: https://codecov.io/gh/deis/controller/pull/869?src=pr


[Tyra2] Reorganize the file dates

That is a surprise!
Thank you for your contribution!

That is a surprise! Thank you for your contribution!
Please check out the ROADMAP.TXT file from tyrav2-develop branch We discussed about putting 2020-2022 everywhere, but it can be 2022 everywhere also.

It will maintained 2020-2022 however newer files should be only 2022

That is a surprise! Thank you for your contribution!
Please check out the ROADMAP.TXT file from tyrav2-develop branch We discussed about putting 2020-2022 everywhere, but it can be 2022 everywhere also.

It will maintained 2020-2022 however newer files should be only 2022

So how about putting 2022 everywhere? I like to be this simple and same in every place.

Due to inactivity - I fixed it by myself

Due to inactivity - I fixed it by myself

Yeah but i stopped becuase of the merge and patience


Use confirmed matches as training data

Overview
Attempts to make subsequent matching of replacements lists require less
intervention from the contributor by adding previously confirmed matches to the
training data.
This change does not appear to help. Adding it as a branch so it can be archived
and returned to if needed.
These are the testing steps:

Run ./scripts/resetdb
Log in as<EMAIL_ADDRESS>Confirm matches on http://localhost:6543/lists/8
Upload src/django/api/management/commands/facility_lists/geocoded/8.csv and
replace the previous list.
Fully process the uploaded list

./scripts/manage batch_process --list-id 16 --action parse
./scripts/manage batch_process --list-id 16 --action geocode
./scripts/manage batch_process --list-id 16 --action match

Browse the results http://localhost:6543/lists/16

Adding the manual matches as training data via markPairs does not boost the
match scores. The match score for row index 11 is 0.69 both times.
Connects #947

Closing because the purpose of this PR was just to create a historical record of a failed solution.


⚠ Bofrost.be has degraded performance

In fbd2879, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2762 ms

Resolved: Bofrost.be performance has improved in 1868f89.


latest MQ version is unable to create queues

We are using docker image and it has no issues with release, 0.15.7
here are some logs
localsqs_1       | 22:33:44.811 [main] INFO  org.elasticmq.server.Main$ - Starting ElasticMQ server (0.15.7) ...
localsqs_1       | 22:33:44.842 [elasticmq-akka.actor.default-dispatcher-6] INFO  akka.event.slf4j.Slf4jLogger - Slf4jLogger started
localsqs_1       | 22:33:44.844 [elasticmq-akka.actor.default-dispatcher-10] INFO  c.t.sslconfig.akka.AkkaSSLConfig - ssl-config.default is true, using the JDK's default SSLContext
localsqs_1       | 22:33:44.845 [elasticmq-akka.actor.default-dispatcher-10] WARN  c.t.sslconfig.akka.AkkaSSLConfig - You are using ssl-config.default=true and have a weak certificate in your default trust store! (You can modify akka.ssl-config.disabledKeyAlgorithms to remove this message.) WARNING arguments left: 1
localsqs_1       | 22:33:44.848 [elasticmq-akka.actor.default-dispatcher-9] WARN  c.t.sslconfig.akka.AkkaSSLConfig - You are using ssl-config.default=true and have a weak certificate in your default trust store! (You can modify akka.ssl-config.disabledKeyAlgorithms to remove this message.) WARNING arguments left: 1
localsqs_1       | 22:33:44.848 [elasticmq-akka.actor.default-dispatcher-9] WARN  c.t.sslconfig.akka.AkkaSSLConfig - You are using ssl-config.default=true and have a weak certificate in your default trust store! (You can modify akka.ssl-config.disabledKeyAlgorithms to remove this message.) WARNING arguments left: 1
localsqs_1       | 22:33:44.848 [elasticmq-akka.actor.default-dispatcher-9] WARN  c.t.sslconfig.akka.AkkaSSLConfig - You are using ssl-config.default=true and have a weak certificate in your default trust store! (You can modify akka.ssl-config.disabledKeyAlgorithms to remove this message.) WARNING arguments left: 1
localsqs_1       | 22:33:44.848 [elasticmq-akka.actor.default-dispatcher-8] WARN  c.t.sslconfig.akka.AkkaSSLConfig - You are using ssl-config.default=true and have a weak certificate in your default trust store! (You can modify akka.ssl-config.disabledKeyAlgorithms to remove this message.) WARNING arguments left: 1
localsqs_1       | 22:33:44.851 [elasticmq-akka.actor.default-dispatcher-11] INFO  o.elasticmq.actor.QueueManagerActor - Creating queue QueueData(dlq_omniarchive,MillisVisibilityTimeout(30000),PT0S,PT0S,2020-10-28T22:33:44.851Z,2020-10-28T22:33:44.851Z,None,false,false,None,None,Map())
localsqs_1       | 22:33:44.851 [elasticmq-akka.actor.default-dispatcher-13] INFO  o.e.rest.sqs.TheSQSRestServerBuilder - Started SQS rest server, bind address <IP_ADDRESS>:9324, visible server address * (depends on incoming request path)
localsqs_1       | 22:33:44.851 [elasticmq-akka.actor.default-dispatcher-13] INFO  o.elasticmq.actor.QueueManagerActor - Creating queue QueueData(cds_omniarchive_queue,MillisVisibilityTimeout(30000),PT0S,PT0S,2020-10-28T22:33:44.851Z,2020-10-28T22:33:44.851Z,Some(DeadLettersQueueData(dlq_omniarchive,4)),false,false,None,None,Map())
localsqs_1       | 22:33:44.851 [main] INFO  org.elasticmq.server.Main$ - === ElasticMQ server (0.15.7) started in 42 ms ===

But latest docker image has elastic mq changes and we are seeing issues with this build. It didn't create the required queue that we mentioned in the conf file.
conf file:
// this is mostly copy pasted from elasticMQ's README.md
// https://github.com/softwaremill/elasticmq

include classpath("application.conf")

// What is the outside visible address of this ElasticMQ node
// Used to create the queue URL (may be different from bind address!)
node-address {
    protocol = http
    host = "*"
    port = 9324
    context-path = ""
}

rest-sqs {
    enabled = true
    bind-port = 9324
    bind-hostname = "<IP_ADDRESS>"
    // Possible values: relaxed, strict
    sqs-limits = strict
}

// Should the node-address be generated from the bind port/hostname
// Set this to true e.g. when assigning port automatically by using port 0.
generate-node-address = false

queues {
  cds_omniarchive_queue {
     receiveMessageWait = 0 seconds
     deadLettersQueue {
         name = "dlq_omniarchive"
         maxReceiveCount = 4
     }
   }
   dlq_omniarchive { }
}

logs:
localsqs_1       | 18:07:46.392 [main] INFO  org.elasticmq.server.Main$ - Starting ElasticMQ server (0.15.8) ...
localsqs_1       | 18:07:46.451 [elasticmq-akka.actor.default-dispatcher-6] INFO  akka.event.slf4j.Slf4jLogger - Slf4jLogger started
localsqs_1       | 18:07:46.463 [elasticmq-akka.actor.default-dispatcher-9] INFO  o.e.rest.sqs.TheSQSRestServerBuilder - Started SQS rest server, bind address <IP_ADDRESS>:9324, visible server address http://localhost:9324
localsqs_1       | 18:07:46.463 [main] INFO  org.elasticmq.server.Main$ - === ElasticMQ server (0.15.8) started in 72 ms ===

Hi,
Thanks for the report.
Could You provide command via which You are starting elasticmq and specify whether You are using native elasticmq or "normal" one?

Judging on 72ms startup I would suspect native :)

In newest version (0.15.8) we have unified way of running native elasticmq and the "normal one".
In 0.15.7, to attach custom config to native elasticmq image was to mount it as path/custom.conf:/opt/docker/elasticmq.conf, in 0.15.8, the path has been changed to path/custom.conf:/opt/elasticmq.conf.

We're experiencing similar problems.
This works fine (old version):
    sqs:
        image: softwaremill/elasticmq-native:0.15.7
        container_name: insights_elasticmq
        volumes:
            - ./_dev/sqs/elasticmq.conf:/opt/docker/elasticmq.conf:ro
        ports:
            - "9324:9324"

However, this doesn't:
    sqs:
        image: softwaremill/elasticmq-native:0.15.8
        container_name: insights_elasticmq
        volumes:
            - ./_dev/sqs/elasticmq.conf:/opt/elasticmq.conf:ro
        ports:
            - "9324:9324"

When using the second config, our elixir (ex_aws) client fails with this message:
[error] Unable to fetch events from AWS. Reason: {:http_error, 400, %{code: "AWS.SimpleQueueService.NonExistentQueue", detail: nil, message: "AWS.SimpleQueueService.NonExistentQueue; see the SQS docs.", request_id: "00000000-0000-0000-0000-000000000000", type: "Sender"}}

With 0.15.7, it works.

I just tried this using 0.15.7 and i'm receiving the same error you posted above so i'm now thinking it may be a boto change?  Curious what version of boto are you using.  I'm actually using boto3 (latest version). just my two cents.

In newest version (0.15.8) we have unified way of running native elasticmq and the "normal one".
In 0.15.7, to attach custom config to native elasticmq image, You had to mount it as path/custom.conf:/opt/docker/elasticmq.conf, in 0.15.8, the path has been changed to path/custom.conf:/opt/elasticmq.conf.

I tried this option and it solved the issue.

Yep! @vk9551 I changed my docker-compose when using 0.15.7 to this and it worked perfectly
version: '3.7'

services:
  elasticmq:
    image: softwaremill/elasticmq-native:0.15.7
    container_name: elasticmq
    ports:
      - "9324:9324"
    volumes:
      - ./elasticmq/custom.conf:/opt/docker/elasticmq.conf

Still there's an issue with 0.15.8 and not sure what that is though....

version: '3.7'

services:
  elasticmq:
    image: softwaremill/elasticmq-native:0.15.8
    container_name: elasticmq
    ports:
      - "9324:9324"
    volumes:
      - ./elasticmq/custom.conf:/opt/elasticmq.conf

i tried this option and it worked for me.

Our queues are defined like this:
queues {
  bx_insights_asset_movements {
    defaultVisibilityTimeout = 10 seconds
    delay = 0 seconds
    receiveMessageWait = 0 seconds
    fifo = true
    contentBasedDeduplication = false
    deadLettersQueue {
        name = "bx_insights_asset_movements-dead-letters"
        maxReceiveCount = 3
    }
  }

  bx_insights_asset_movements-dead-letters { }
}

Starting 0.15.8 produces the following log:
insights_elasticmq | 21:15:00.910 [main] INFO  org.elasticmq.server.Main$ - Starting ElasticMQ server (0.15.8) ...
insights_elasticmq | 21:15:00.966 [elasticmq-akka.actor.default-dispatcher-8] INFO  akka.event.slf4j.Slf4jLogger - Slf4jLogger started
insights_elasticmq | 21:15:00.979 [elasticmq-akka.actor.default-dispatcher-9] INFO  o.e.rest.sqs.TheSQSRestServerBuilder - Started SQS rest server, bind address <IP_ADDRESS>:9324, visible server address http://localhost:9324
insights_elasticmq | 21:15:00.979 [elasticmq-akka.actor.default-dispatcher-9] INFO  o.elasticmq.actor.QueueManagerActor - Creating queue QueueData(bx_insights_asset_movements-dead-letters,MillisVisibilityTimeout(30000),PT0S,PT0S,2020-11-11T21:15:00.979Z,2020-11-11T21:15:00.979Z,None,false,false,None,None,Map())
insights_elasticmq | 21:15:00.982 [elasticmq-akka.actor.default-dispatcher-8] INFO  o.elasticmq.actor.QueueManagerActor - Creating queue QueueData(bx_insights_asset_movements.fifo,MillisVisibilityTimeout(10000),PT0S,PT0S,2020-11-11T21:15:00.982Z,2020-11-11T21:15:00.982Z,Some(DeadLettersQueueData(bx_insights_asset_movements-dead-letters,3)),true,false,None,None,Map())
insights_elasticmq | 21:15:00.983 [main] INFO  org.elasticmq.server.Main$ - === ElasticMQ server (0.15.8) started in 73 ms ===

It can be seen that a config gets loaded and two queues are created, but our client (and the AWS CLI) still returns the error 400 AWS.SimpleQueueService.NonExistentQueue.
So digging deeper, I used the official AWS CLI to discover that with 0.15.8, the queue naming seems to have changed to now include the .fifo suffix for FIFO queues:
aws --endpoint-url 'http://localhost:9324' sqs list-queues
{
    "QueueUrls": [
        "http://localhost:9324/queue/bx_insights_asset_movements.fifo",
        "http://localhost:9324/queue/bx_insights_asset_movements-dead-letters"
    ]
}

(if I had been more observant, this would have also been visible from the log...)
After adjusting the configured queue URL to include .fifo, retrieving messages is working again 👍

@iStefo I am happy to hear that everything is working fine for You :) The .fifo suffix is being added automatically while loading queues from config in order to align behaviour with real SQS which does not allow to create FIFO queue without the .fifo suffix.
@l0phius Could You provide more details what is not working? Maybe it is related to the FIFO queues that were described by iStefo?

As there are no new comments I am closing this issue


[Enhancement] Utility icons should show what they are

When hovering over one of the icons on the utility page, the user should be able to see what the hyperlink is

This has been implemented as of Other-1.0.2


Smart auto rerun task failures for framework tree

When a task fails with flakes, either test failure or infra failure, the framework tree depends the tree gardener to manual retry to reopen the tree. This largely reduces team development velocity.
Some flakes will be hidden as well when multiple commits merged around the same time and a task fails on an earlier commit but succeeds on the next.
A smart auto rerun logic is needed to improve the process:

Auto rerun TOT failures to open the tree faster
An after-hour job to rerun failed tasks to detect flakes

Related https://github.com/flutter/flutter/issues/84004

The work is complete.


C++20 compatibility for library users / std::result_of removed

As a library user, i would like to compile my code using the C++20 standard.
But in /3rd_party/include/opentracing/variant/variant.hpp' the std::result_of<>` template is used:
This template was removed in C++20: see https://en.cppreference.com/w/cpp/types/result_of
std::invoke_result<> can be used as an drop in replacement.
To make the code still compile in C++ versions below C++17 the code can use
__cpp_lib_is_invocable (https://en.cppreference.com/w/cpp/feature_test) to different
e. g.
            template <typename F, typename V, typename Enable = void>
            struct result_of_unary_visit
            {
#ifdef __cpp_lib_is_invocable
                using type = typename std::invoke_result<F, V&>::type;
#else
                using type = typename std::result_of<F(V&)>::type;
#endif
            };
            template <typename F, typename V, typename Enable = void>
            struct result_of_binary_visit
            {
#ifdef __cpp_lib_is_invocable
                using type = typename std::invoke_result<F, V&, V&>::type;
#else
                using type = typename std::result_of<F(V&, V&)>::type;
#endif
            };

I would also greatly appreciate this change.

Any progress???

@perseoGI This project is no longer maintained https://github.com/opentracing/specification/issues/163


Back ups for production DB

Ensure DB is backing up to S3 or other specified place. (dokku production db)

Doesn't look like S3 backups are enabled for mcweb-db:

DB has been backed up (11/16/23). Institute job to back up daily https://github.com/dokku/dokku-postgres#backups


[Tabular] Add TabPFN model

Add TabPFN model to Tabular.

Interesting, and it uses some FE as well in the model.

Do not preprocess inputs to TabPFN. TabPFN pre-processes inputs internally. It applies a z-score normalization (x-train_x.mean()/train_x.std()) per feature (fitted on the training set) and log-scales outliers heuristically.  Pre-processing is important for the TabPFN to make sure that the real-world dataset lies in the distribution of the synthetic datasets seen during training. So to get the best results, do not apply a PowerTransformation to the inputs.

TabPFN expects scalar values only (you need to encode categoricals as integers e.g. with OrdinalEncoder). It works best on data that does not contain any categorical or NaN data (see Appendix B.1).

TabPFN ensembles multiple input encodings per default. It feeds different index rotations of the features and labels to the model per ensemble member. You can control the ensembling with TabPFNClassifier(...,N_ensemble_configurations=?)

TabPFN does not use any statistics from the test set. That means predicting each test example one-by-one will yield the same result as feeding the whole test set together.

TabPFN is differentiable in principle, only the pre-processing is not and relies on numpy.

Resolved by #3270


Hello Adams!  Looking forward to …

…working with you more in the future!

ty homie