I find I cannot load from fined LoRA checkpoint

import torch
from transformers import AutoModel, AutoTokenizer, AutoConfig

# Load the base model and tokenizer
model_path = "/home/yerong2/models/internlm-xcomposer2d5-7b"
model = AutoModel.from_pretrained(model_path, trust_remote_code=True).half().cuda()
tokenizer = AutoTokenizer.from_pretrained(model_path, trust_remote_code=True)

# Load the adapter/finetuned weights
checkpoint_path = "lorra_finetune/src/finetune/output/finetune_lora/checkpoint-2/"
adapter_weights = torch.load(f"{checkpoint_path}/adapter_model.bin")

# Merge the adapter weights with the base model
model.load_state_dict(adapter_weights, strict=True)

# Verify that the model has loaded the weights
print("Model successfully loaded with finetuned weights.")

model.tokenizer = tokenizer

query = 'Image1 <ImageHere>; Image2 <ImageHere>; Image3 <ImageHere>; I want to buy a car from the three given cars, analyze their advantages and weaknesses one by one'
image = ['../examples/cars1.jpg',
        '../examples/cars2.jpg',
        '../examples/cars3.jpg',]
with torch.autocast(device_type='cuda', dtype=torch.float16):
    response, his = model.chat(tokenizer, query, image, do_sample=False, num_beams=3, use_meta=True)
print(response)

This reports error:
[rank1]: Traceback (most recent call last):
[rank1]:   File "/home/yerong2/representation-engineering/lorra_finetune/src/mllm_lorra.py", line 580, in <module>
[rank1]:     train()
[rank1]:   File "/home/yerong2/representation-engineering/lorra_finetune/src/mllm_lorra.py", line 491, in train
[rank1]:     model.load_state_dict(adapter_weights, strict=True)
[rank1]:   File "/home/yerong2/local/miniconda3/envs/mllm/lib/python3.11/site-packages/torch/nn/modules/module.py", line 2189, in load_state_dict
[rank1]:     raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format(
[rank1]: RuntimeError: Error(s) in loading state_dict for InternLMXComposer2ForCausalLM:
[rank1]:        Missing key(s) in state_dict: "plora_glb_GN", "plora_sub_GN", "model.tok_embeddings.weight", "model.layers.0.attention.wqkv.weight", "model.layers.0.attention.wqkv.Plora_A.weight", "model.layers.0.attention.wqkv.Plora_B.weight", "model.layers.0.attention.wqkv.lora_sft_A.weight", "model.layers.0.attention.wqkv.lora_sft_B.weight", "model.layers.0.attention.wqkv.lora_dpo_A.weight", "model.layers.0.attention.wqkv.lora_dpo_B.weight", "model.layers.0.attention.wqkv.lora_web_A.weight", "model.layers.0.attention.wqkv.lora_web_B.weight", "model.layers.0.attention.wo.weight", "model.layers.0.attention.wo.Plora_A.weight", "model.layers.0.attention.wo.Plora_B.weight", "model.layers.0.attention.wo.lora_sft_A.weight", "model.layers.0.attention.wo.lora_sft_B.weight", "model.layers.0.attention.wo.lora_dpo_A.weight", "model.layers.0.attention.wo.lora_dpo_B.weight", "model.layers.0.attention.wo.lora_web_A.weight", "model.layers.0.attention.wo.lora_web_B.weight", "model.layers.0.feed_forward.w1.weight", "model.layers.0.feed_forward.w1.Plora_A.weight", "model.layers.0.feed_forward.w1.Plora_B.weight", "model.layers.0.feed_forward.w1.lora_sft_A.weight", "model.layers.0.feed_forward.w1.lora_sft_B.weight", "model.layers.0.feed_forward.w1.lora_dpo_A.weight", "model.layers.0.feed_forward.w1.lora_dpo_B.weight", "model.layers.0.feed_forward.w1.lora_web_A.weight", "model.layers.0.feed_forward.w1.lora_web_B.weight", "model.layers.0.feed_forward.w3.weight", "model.layers.0.feed_forward.w3.Plora_A.weight", "model.layers.0.feed_forward.w3.Plora_B.weight", "model.layers.0.feed_forward.w3.lora_sft_A.weight", "model.layers.0.feed_forward.w3.lora_sft_B.weight", "model.layers.0.feed_forward.w3.lora_dpo_A.weight", "model.layers.0.feed_forward.w3.lora_dpo_B.weight", "model.layers.0.feed_forward.w3.lora_web_A.weight", "model.layers.0.feed_forward.w3.lora_web_B.weight", "model.layers.0.feed_forward.w2.weight", "model.layers.0.feed_forward.w2.Plora_A.weight", "model.layers.0.feed_forward.w2.Plora_B.weight", "model.layers.0.feed_forward.w2.lora_sft_A.weight", "model.layers.0.feed_forward.w2.lora_sft_B.weight", "model.layers.0.feed_forward.w2.lora_dpo_A.weight", "model.layers.0.feed_forward.w2.lora_dpo_B.weight", "m

Use PeftModel from pretrained seems to work
import torch
from transformers import AutoModel, AutoTokenizer, AutoConfig
from peft import PeftModel

# Load the base model and tokenizer
model_path = "/home/yerong2/models/internlm-xcomposer2d5-7b"
model = AutoModel.from_pretrained(model_path, trust_remote_code=True).half().cuda()
tokenizer = AutoTokenizer.from_pretrained(model_path, trust_remote_code=True)

# Load the adapter/finetuned weights
checkpoint_path = "lorra_finetune/math/best"
# adapter_weights = torch.load(f"{checkpoint_path}/adapter_model.bin")
model = PeftModel.from_pretrained(model, checkpoint_path)
model = model.merge_and_unload()
# Verify that the model has loaded the weights
print("Model successfully loaded with finetuned weights.")

model.tokenizer = tokenizer

query = 'Image1 <ImageHere>; Image2 <ImageHere>; Image3 <ImageHere>; I want to buy a car from the three given cars, analyze their advantages and weaknesses one by one'
image = ['./examples/cars1.jpg',
        './examples/cars2.jpg',
        './examples/cars3.jpg',]
with torch.autocast(device_type='cuda', dtype=torch.float16):
    response, his = model.chat(tokenizer, query, image, do_sample=False, num_beams=3, use_meta=True)
print(response)

Use PeftModel from pretrained seems to work
import torch
from transformers import AutoModel, AutoTokenizer, AutoConfig
from peft import PeftModel

# Load the base model and tokenizer
model_path = "/home/yerong2/models/internlm-xcomposer2d5-7b"
model = AutoModel.from_pretrained(model_path, trust_remote_code=True).half().cuda()
tokenizer = AutoTokenizer.from_pretrained(model_path, trust_remote_code=True)

# Load the adapter/finetuned weights
checkpoint_path = "lorra_finetune/math/best"
# adapter_weights = torch.load(f"{checkpoint_path}/adapter_model.bin")
model = PeftModel.from_pretrained(model, checkpoint_path)
model = model.merge_and_unload()
# Verify that the model has loaded the weights
print("Model successfully loaded with finetuned weights.")

model.tokenizer = tokenizer

query = 'Image1 <ImageHere>; Image2 <ImageHere>; Image3 <ImageHere>; I want to buy a car from the three given cars, analyze their advantages and weaknesses one by one'
image = ['./examples/cars1.jpg',
        './examples/cars2.jpg',
        './examples/cars3.jpg',]
with torch.autocast(device_type='cuda', dtype=torch.float16):
    response, his = model.chat(tokenizer, query, image, do_sample=False, num_beams=3, use_meta=True)
print(response)

Actually this merge is not effective, I think it just loaded the original model from HF

You may read the document and use the merge_peft_adapter.py to merge the LoRA weight.

Here is a document for 2.0 https://github.com/InternLM/InternLM-XComposer/blob/0a33f58f3cbc7d20be4bae4a3d4a812289c63406/InternLM-XComposer-2.0/finetune/README.md

Also, I am curious whether there exists options letting deepspeed know not to save large global_step100 (42GB) when saving checkpoints.

#423 I found with multiple GPU, deepspeed+LoRA saves an invalid checkpoint for some reason.


Fix typo: "CMSI" -> "CMSIS"

Signed-off-by: David Reiss<EMAIL_ADDRESS>

@nashif , can you land this?

@dreiss sorry, but you need to fix your commit message. An empty body is not allowed and we require a subsystem/area. It has to look like this:
doc: Fix typo: "CMSI" -> "CMSIS"

A nonempty description of the change; yes, this is required even for trivial changes

Signed-off-by: Your Name <your.email@address>

@dreiss sorry, but you need to fix your commit message.

(this is why the compliance check in CI is failing)

Please fix the commit message as Marti mentioned above.
This can be merged after the feature freeze today since it is a documentation bug fix.

Done.


Fix Ecto repo config in README.md.eex

The info provided was not correct. That would only work after using mix release. With the config set in the config/config.exs it is working in all environments.

Hi @stefanluptak !
Can you provide a little more information about the error you ran into, or even better, provide a sample repo demonstrating the issue? Because I am very confident runtime config should be fine for this since it is only accessed at runtime, and I am and have been using runtime config for it since first writing it.

Hi @tfwright. Now I realized I put that config ... inside the if config_env() == :prod do ... end block and didn't notice that. 🤦🏻 Sorry. I am closing this PR as irrelevant.

No worries! Better wontfix bug reports than no bug reports


Use terminal cursor in date prompts

Is your feature request related to a problem? Please describe.
The selected date cursor in date prompts is entirely artificial, we explicitly add a background and foreground colors on where the cursor should be. Meanwhile, the actual cursor is hidden at the end of the prompt.
Ideally, we should position the cursor where it should actually reside. I'm not sure if this helps with accessibility, it would be even more worth it if it does.
We probably will continue to hide the cursor, as we can't highlight an entire 2-digit date with a cursor of width 1. But just having the cursor there is important.
Describe the solution you'd like
The backend should mark where the cursor should be and move it to the correct place after rendering the entire prompt.

Closed via https://github.com/mikaelmello/inquire/commit/cd7874a8f20517ad058af07402f78b6fffe21579


micro:bit deleted sprite still interferes with other display commands

Expected: The number should stay on the screen, as if we never created any sprite.
Actual: The number disappears after a short time, as if the sprite was still there. (Same for the real micro:bit and simulator.)
let item = game.createSprite(2, 2)
item.delete()
basic.showNumber(0)

Duplicate of https://github.com/Microsoft/pxt/issues/2467

To expand on this: After making some sprites, the game engine deliberately interrupts other display commands and re-displays the sprites after a short time. The point was that it shouldn't do this when all the sprites have been deleted.

Sorry I miss understood.

My first thought was to avoid plotting when there are no sprites. This does work.
https://github.com/HelenFoster/pxt-microbit/commit/384e8afec8c45d80fb5da178c8e74e595939402a
The remaining issue is that the game library sets the display to greyscale mode.
The game library initializes implicitly when the user creates the first sprite. So it makes sense to be able to "exit" the game library by deleting the last sprite. (And then it needs to work again if another sprite is created later.)
Would it be a good idea to save what mode the display was in when entering game state, and then restore it when the last sprite is deleted?

Would it be a good idea to save what mode the display was in when entering game state, and then restore it when the last sprite is deleted?

Would have to add a getDisplayMode function to do that.

Was fixed instead with manual pause and resume of game engine, in https://github.com/Microsoft/pxt-microbit/pull/476


Gk nov 7 2022

Hackathon branch from when @tnbernard visited PPPL. Includes a first pass at ionization, some build system changes, and a large refactoring of the Vlasov equation object to accommodate general geometry (which now works with neutrals!)
Corresponding G2 merge also needs to be completed. https://github.com/ammarhakim/gkyl/pull/113 will work though it won't have the option for general geometry. But that PR does have the necessary changes to the Vlasov updater to accommodate this G0 branch merge.

Strange Mac issues need to be debugged before merging


[UX]: Provide documentation of methods for testing

Description

refactor the code
document the code itself
generate documentation from the code
add the documentation to Berg GitHub repository

Affects
None
Subsystem
None

Is followed up by #25


Fix memory leak in MutableQuantiles

In some circumstances (high GC, high CPU usage, creating lots of
S3AFileSystem) it is possible for MutableQuantiles::scheduler to fall
behind processing tasks that are submitted to it; because tasks are
submitted on a regular schedule, the unbounded queue backing the
ExecutorService might grow to several gigs. By using
scheduleWithFixedDelay we ensure that under pressure this leak can't
happen.

Thanks for your interest in palantir/hadoop, @Alexis-D! Before we can accept your pull request, you need to sign our contributor license agreement - just visit https://cla.palantir.com/ and follow the instructions. Once you sign, I'll automatically update this pull request.


core: allow TS Gateway protocol violation

According to [MS-RDPBCGR <IP_ADDRESS>.1.1.1] the TS_EXTENDED_INFO_PACKET structure's cbClientAddress field must include the mandatory NULL terminator of the clientAddress field in its byte count.
However, connections proxied via Microsoft's TS Gateway set the cbClientDir value to 0.

@nfedera if it's mandatory maybe we should at least stick a warning (or debug message in) if it violates the written protocol.

Otherwise +1

@bmiklautz This is similar to the (maybe) protocol violation of the iOS/Android MS clients with the cbClientDir value. Since in [MS-RDPBCGR <IP_ADDRESS>.1.1.1] the null terminator is mandatory for for the clientDir and clientAddress strings, this also implies that the terminator is mandatory for empty strings. However, the spec does not explicitly mention null resp. not existent strings ... so there is a little room for interpretation.
And since this Microsoft software is already out there and cannot be changed I think we don't need a debug/warning message here.

+1 for no warning
LGTM

At MS they're really good to not follow their own specifications !


Simple keras model "predict" call fails inside py_function

Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes. Created a simple example for reproducibility.
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 18.04.3 LTS
TensorFlow installed from (source or binary): pip
TensorFlow version (use command below): v2.2.0-rc4-8-g2b96f3662b 2.2.0
Python version: Python 3.7.6
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version: CUDA 10.2 / cuDNN 7.6.5
GPU model and memory: GeForce GTX 980 Ti / 6GB

Describe the current behavior
Using the 'predict' api for a keras model inside a py_function throws the following error:
LookupError: No gradient defined for operation 'IteratorGetNext' (op type: IteratorGetNext)
Standalone code to reproduce the issue
import numpy as np
import tensorflow as tf

inp = tf.keras.Input(shape=(5,))
out = tf.keras.layers.Dense(1)(inp)
model = tf.keras.Model(inp, out)

def outer_func(arr):
    def _func(x):
        res = model.predict(x)
        return res

    out = tf.py_function(
        _func,
        (arr,),
        tf.float32
    )
    return out

outer_func(np.random.rand(10, 5))

I have tried in colab with TF version 2.2 ,nightly version(2.3.0-dev20200528) and was able to reproduce the issue.Please, find the gist here.Thanks!

model.predict contains a lot of state-management and input processing logic that is not designed for this usecase. Can you try instead just calling the model? Eg:
def _func(x):
        res = model(x)
        return res

I cannot unfortunately because I am using a third party library that wraps helper functions / class around the model.predict call. I'm using in a py_function because I'm including it in a tf.data.Dataset pipeline.

This is fixed with latest tf-nightly.
See gist
Output:
<tf.Tensor 'EagerPyFunc_1:0' shape=<unknown> dtype=float32>

@ymodak is still not fixed yet in 2.6.0 but worked at the nightly, do we have any estimation when this will be officially released?


If plugin creates an tag from an release branch on tagging it does not respect it

we had our v2.7.3 tagged on latest master and i manually had to delete and recreate the tag on the correct branch

https://ci.woodpecker-ci.org/repos/3780/pipeline/22344/4


support deployments using SDL

The official library does not support parsing the SDL file and getting Groups that are needed for creating a deployment.
Other AkashJS library developed by @spacepotahto does have support for it: https://github.com/spacepotahto/akashjs/blob/92f41c97fd876480440d46fadf120f7905ded65a/src/utils/deployment.ts#L132
I think for general purpose use of AkashJS to make composable projects, this is a basic requirement.

Can we have one example of create deployment using SDL file or SDL yaml string?


Feature: Broadcast disruption cron events

What does this PR do?
This PR introduces new events for the DisruptionCron resource to enhance observability and debugging capabilities. It also updates the Slack, Datadog, and HTTP notifiers to handle these new events, ensuring that notifications are sent out accordingly. This enhancement allows users to receive detailed notifications about the lifecycle and status changes of DisruptionCron resources, aiding in better management and monitoring of chaos experiments.

[x] Adds new functionality
[ ] Alters existing functionality
[ ] Fixes a bug
[ ] Improves documentation or testing

Please briefly describe your changes as well as the motivation behind them:

New Events for DisruptionCron:

DisruptionCronCreated: Emitted when a DisruptionCron is created.
DisruptionCronUpdated: Emitted when a DisruptionCron is updated.
DisruptionCronDeleted: Emitted when a DisruptionCron is deleted.

2 . Notifier Updates:

Slack Notifier: Enhanced to include custom messages for each new DisruptionCron event, providing users with immediate feedback on the status of their scheduled disruptions.
Datadog Notifier: Updated to track DisruptionCron events as metrics, allowing users to monitor and alert on these events within their Datadog dashboards.
HTTP Notifier: Modified to send HTTP requests for new DisruptionCron events, enabling integration with external systems for automated handling or notifications.

New configuration for the HTTP notifier:

eventnotifiers:
  http:
    enabled: true
    disruption:
      enabled: true
      url: "http://your-disruption-notification-endpoint"
    disruptionCron:
      enabled: true
      url: "http://your-disruptioncron-notification-endpoint"
    headers:
      - "Content-Type:application/json"
    authURL: "http://your-auth-service"
    authHeaders:
      - "Content-Type:application/json"
    authTokenPath: "/path/to/auth/token"

After configuring the HTTP notifier as shown above, the Chaos Controller will automatically use it to send notifications about Disruption and DisruptionCron events to the specified URLs. The notifications will include details about the event, such as the type of notification, the name of the disrupted resource, and a message describing the event.  For instance, when a Disruption event occurs, the Chaos Controller will send a POST request to http://your-disruption-notification-endpoint with a JSON payload containing information about the disruption. Similarly, DisruptionCron events will trigger POST requests to http://your-disruptioncron-notification-endpoint.

Create three webhooks

Validation webhook for DisruptionCron : Used to emit an event to the broadcasted during a CRUD operation.
Mutate webhook for DisruptionCron: Used to inject the UserInfo data as an annotation for DisruptionCron.

Code Quality Checklist

[ ] The documentation is up to date.
[x] My code is sufficiently commented and passes continuous integration checks.
[x] I have signed my commit (see Contributing Docs).

Testing

[x] I leveraged continuous integration testing

[x] by depending on existing unit tests or end-to-end tests.
[x] by adding new unit tests or end-to-end tests.

[x] I manually tested the following steps:

x
[x] locally.
[x] as a canary deployment to a cluster.

PR description reads:
eventnotifiers:
  http:
    enabled: true
    disruption:
      enabled: true
      url: "http://your-disruption-notification-endpoint"
    disruptionCron:
      enabled: true
      url: "http://your-disruptioncron-notification-endpoint"

But there is no http.enabled in the chart files. The description needs updated, yeah? (rather than the charts?)

In a lot of existing unit tests, we construct the logger with zaptest.NewLogger(GinkgoT()).Sugar() from the package "go.uber.org/zap/zaptest". In many of the new files added, you're using the NewZapLogger from our log package. I think we might prefer using zaptest?
Here's an example log from the make test output for notifiersink_test.go:
  {"level":"debug","ts":1721725161587.9463,"caller":"eventbroadcaster/notifiersink.go:45","message":"CREATE event received:","event":"&Event{ObjectMeta:{      0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[] map[] [] [] []},InvolvedObject:ObjectReference{Kind:Disruption,Namespace:,Name:,UID:,APIVersion:,ResourceVersion:,FieldPath:,},Reason:Finished,Message:,Source:EventSource{Component:disruption-controller,Host:,},FirstTimestamp:0001-01-01 00:00:00 +0000 UTC,LastTimestamp:0001-01-01 00:00:00 +0000 UTC,Count:0,Type:Normal,EventTime:0001-01-01 00:00:00 +0000 UTC,Series:nil,Action:,Related:nil,ReportingController:,ReportingInstance:,}"}

Here's a log from the zaptest package from make test output for the injector package:
2024-07-23T09:00:12.785Z      INFO    setting tx qlen for interface lo
The former is clearly preferable for ingestion into DD or another production log system, but for humans reading make test output, I think we want the zaptest logger.


Change the public API for Entity Models

Change the public API for Entity Models, could this be improved if it was to be moved to a public method / decorator in a Flask views file..?

duplicate


DXQ-38294 Update the preview component to accommodate in the versions comparison screen

DXQ-38294 Update the preview component to accommodate in the versions comparison screen
This PR covers the following changes:
1.) Added a versionComparison prop for the Preview component.
2.) Added a visual test for the Preview Component.

^ Please update branch also


Crashing on startup (Windows Server 2022 with desktop experience and .NET 6 desktop runtime)

So i've downloaded this release: https://github.com/ErikEJ/SqlQueryStress/releases/tag/<IP_ADDRESS>
And it's crashing on startup. I am running it on a Windows Server 2022 host (it has .NET 6 desktop runtime installed and also the Desktop Experience [so it's not running Windows Server core]).
Is Windows Server not supported perhaps? I can't see a 'system requirements' list anywhere in this repo.
This is the first error that get's logged:
Application: SqlQueryStress.exe
CoreCLR Version: 6.0.3024.21525
.NET Version: 6.0.30
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException: Object reference not set to an instance of an object.
   at SQLQueryStress.SqlControl.SqlControl_OnLoaded(Object sender, RoutedEventArgs e)
   at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
   at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
   at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
   at System.Windows.UIElement.RaiseEvent(RoutedEventArgs e)
   at System.Windows.BroadcastEventHelper.BroadcastEvent(DependencyObject root, RoutedEvent routedEvent)
   at System.Windows.BroadcastEventHelper.BroadcastLoadedEvent(Object root)
   at System.Windows.Media.MediaContext.FireLoadedPendingCallbacks()
   at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks()
   at System.Windows.Media.MediaContext.RenderMessageHandlerCore(Object resizedCompositionTarget)
   at System.Windows.Media.MediaContext.RenderMessageHandler(Object resizedCompositionTarget)
   at System.Windows.Media.MediaContext.Resize(ICompositionTarget resizedCompositionTarget)
   at System.Windows.Interop.HwndTarget.OnResize()
   at System.Windows.Interop.HwndTarget.HandleMessage(WindowMessage msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)

This is the second event log:
Faulting application name: SqlQueryStress.exe, version: <IP_ADDRESS>, time stamp: 0x661e012c
Faulting module name: unknown, version: <IP_ADDRESS>, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ff5d1813e13
Faulting process id: 0x2530
Faulting application start time: 0x01dab7be4b1a2d69
Faulting application path: C:\Downloads\SqlQueryStress.exe
Faulting module path: unknown
Report Id: 345f6d83-22c0-4101-8dfa-1ae8645af7e4
Faulting package full name:
Faulting package-relative application ID:

Finally (and strangely a third one gets logged 5 minutes later):
Faulting application name: SqlQueryStress.exe, version: <IP_ADDRESS>, time stamp: 0x661e012c
Faulting module name: KERNELBASE.dll, version: 10.0.20348.2461, time stamp: 0x6008e061
Exception code: 0xc000041d
Fault offset: 0x000000000003f19c
Faulting process id: 0x2530
Faulting application start time: 0x01dab7be4b1a2d69
Faulting application path: C:\Downloads\SqlQueryStress.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: db8bfd26-e84e-4779-903b-653c5a0f1c54
Faulting package full name:
Faulting package-relative application ID:

@mamift Thanks for reporting, the latest release is broken, I am working on a fix


SIGSEGV when connecting to <IP_ADDRESS> with no running server

> gwhisper <IP_ADDRESS>
fish: Job 1, 'gwhisper <IP_ADDRESS>' terminated by signal SIGSEGV (Address boundary error)

false alarm, was caused by healthcheck issue (used old gwhisper version)


Add Animation::set_current_tag_frame

Hello! This is just a suggestion. Feel free to modify, use a different approach, or close the PR.
Proposal
It can be useful to be able to start at a frame that's not the initial tag frame. set_current_tag_frame() with a frame relative to the tag start frame can solve this.
Use case
You have a 8 directional character animation with 10 frames each. You would like when transitioning between e.g. North to North East movement to continue the animation at the step it was left of in the North animation.
This can now be done as:
let previous_frame_index = animation.current_tag_frame(info);
*animation = AsepriteAnimation::new(info, "North East");
animation.set_current_tag_frame(info, previous_frame_index);

Arguably, you should be able to create the animation while also specifying the tag. So maybe separately also add something like:
AsepriteAnimation::new_at_index(info, "North East", previous_frame_index)

That's a good idea ! Thanks for your contribution, I will release it later today.


The light/dark toggle button does not communicate its state

It communicates it visually but not through the accessibility tree

Not sure if we should also address https://github.com/pydata/pydata-sphinx-theme/discussions/1491

It communicates it visually but not through the accessibility tree

I'm not sure I completely understand, can you expand on what should be done here, or how that should affect the accessibility tree ?

We went over this is in the team sync yesterday.
Reiterating here, for reference, the issue is that when you cycle through the three states (light, dark, auto) of the light/dark button (which is in the top right of the PST docs), the current state of the button is reflected visually, but nowhere is this visual state communicated in a textual way in the DOM. For assistive tech, it's important that the current state of the button is reflected in the accessibility tree.

Thanks, I managed to see the accessibility tree in my dev console and will look into modifying it when the button switches.

I'm reading the various aria things, and I'm wondering if the theme switch button should be an option dropdown with 3 options (auto, light, & dark).
It seem like a 3 state button is a bit of a hack (and maybe less discoverable than an option?)
I think the UI could be almost identical, but making it an option would maybe solve most of our Accessibility concerns.
Thoughts ?

Also, I'm not sure we can do anything abut that, but the button tooltip on hover/focus seem to be added/removed by js (via bootstrap?), which removes and add a new aria-describedby attribute on every hover.
Should this aria-describedby (and tooltip element) always be present, but just visually hidden  to be properly supported by screen readers ?

be an option dropdown

And I suppose I mean a select

Speaking of, this is what MDN is doing, I'm trying to see if we can set aria-description anyway on the the body element, but that does not seem to work. There is no way to directly modify the accessibility tree.

Ok, so select won't work because we can't style it with icons. So we have a to do a custom dropdown which does not fix our accessibility issue. aria-desciption does no show up in the accessibility tree, and aria-label is already set to "light/dark" translatable string.
I guess we can change the aria label to a dynamic string like : "Switch theme. Current theme : %s". though it's unclear how to translate a dynamic js string. I also realize that "auto" is unclear. MDN uses "Os default" as a description.

Related:

https://github.com/pydata/pydata-sphinx-theme/discussions/1491#discussioncomment-9621593

Responding to some of your points:

I agree that the tri-state button is an unconventional pattern. A dropdown is probably preferred (that was the consensus in the discussion I linked in my previous comment). It's more work, though, and I think we could fix the specific accessibility issue here with much less effort. But I will leave it up to your judgment, whether to re-implement the theme switcher now or later.
As for the Bootstrap tooltips/popovers, I would check the docs to see if they have some option that might address our use case here, otherwise I would just leave them alone as a completely other thing.
As for translatable strings in JavaScript, it might be worth working on solving this problem once and for all, especially if it turns out their is an elegant, low-maintenance way to do so. I suspect it will come up again. However, I don't think you need it for this issue. We use Font Awesome icons in the theme-switcher.html Jinja template. I suspect that the Font Awesome accessibility docs provide a pathway to adding translatable strings in the Jinja template that then also show up in the accessibility tree.

Some thoughts from today's call:

Eventually we should probably get rid of the light/dark/auto mode toggle button and push that functionality back to the system (browser, OS).
Perhaps we imitate the search button and open a modal dialog with a deprecation notice and three buttons.
The deprecation notice could link the user to info on how to set light/dark mode on their system.


dump to alternative string type, as defined in basic_json template

An alternative string implementation can be defined in basic_json template. These changes allow json::dump to work with the alternative string type.

Thanks a lot!


Adding support for a custom proxy input

Related Issues

Closes #217

Why is this change being made?
WinGet has a feature where a user can specify a proxy string. Some users of winget download are interested in using the feature so they can use a proxy to bypass enterprise blocking of the service URL, and sfs client would need to support the proxy string in its network connection layer.
For the curl implementation inside the client, that means passing in a string to CURLOPT_PROXY setting.
This PR is implementing support for a new input parameter for a request to supply a custom proxy.
What is being changed?

A caller can now specify a std::optional<std::string> proxy argument on requestParams in the Client APIs. The correspondent request will use that proxy when connecting to the service to get product information.
The implementation happens in the Curl connection layer, where the proxy string is passed to CURLOPT_PROXY setting
For testing:

I've implemented a simple ProxyServer class reusing the model for the MockWebServer class and the cpp-httplib library. It just redirects GET and POST requests to the original server target URL.
I've added unit tests for validating that CURL accepts only valid proxy strings.
I've added functional tests using the new proxy server.

How was the change tested?
New tests are being added as mentioned above.

Merging directly to main? No develop branch? I see winget waiting for this fix.. will they validate your proxy support in winget before you make an official release?

Merging directly to main? No develop branch? I see winget waiting for this fix.. will they validate your proxy support in winget before you make an official release?

Yeah, our philosophy is that main is always building & working, but API users should be picking up from release-tagged commits. Thus, pushing to main should not affect a user immediately. They should run validation before integrating a new release.
The PM who's interested in the feature has already validated it internally using our PR and a modification they made to winget (https://github.com/microsoft/winget-cli/issues/5030) and said it's working fine.
WinGet should still do extra tests before committing the version change after we release.


Fix parsing from bytes if first character of string is multi-byte

In my environment, parsing the byte array of "£0.99" with spray-json incorrectly decodes the pound symbol as ASCII.  This fix modifies the advance function to advance 1 UTF-8 character rather than a single byte.

Thanks for the bug report and the patch, Mark!
I've create ticket #148 as a marker for the issue.
While the fix you propose does indeed solve the problem it is a bit too aggressive.
For performance reasons we should only call input.nextUtf8Char inside of JSON strings. Everywhere else multibyte characters are disallowed anyway.
The problem is the require in line 127 of the JsonParser.
If we replace it with
if (cursorChar == '"') cursorChar = input.nextUtf8Char() else fail(s"'$cursorChar'")

then the problem should be fixed as well as but performance should remain almost unaffected.
If you apply this small tweak to your PR and accept the Typesafe CLA then we'd be happy to merge your fix.
Thanks again!

One more thing: could you also change the commit message to
= Fix multibyte chars at ix 0 of JSON String not being parsed correctly, closes #148

? (to be inline with our git commit message policy

Thanks @sirthias, I've accepted the CLA and made the amendments you suggest.

Great! Thanks, Mark!


cannot access $- prefix vars provided from setup() except "$style"

Version
3.0.2
Steps to reproduce
given SFC:
<template>
<div>
{{ $a.bar }}
</div>
</template>

<script lang="ts">
import { defineComponent, useCssModule } from 'vue'

export default defineComponent({
	setup() {
		return {
			$a: { bar: 1 },
			$style: useCssModule(),
		}
	}
})
</script>

<style module>
.foo { color: #fff; }
</style>

What is expected?
shows value of $a.bar
What is actually happening?
Get error TypeError: Cannot read property 'bar' of undefined

$style in template can work properly.
But using any other $ prefixed variables, Vue throws error.
I'm using $ prefix because I'm going to inject some values like $globalStyle, $theme in setup(), but template always throws error with undefined except using $style as variable name.

You should avoid prefixing your variables with $ or _:
See https://v3.vuejs.org/guide/data-methods.html#data-properties
When defined in data, you get a warning about it but I'm not sure if the same should apply here

@posva good point!
With vue-loader, it allows css modules inject as custom name like $globalStyle and it works with old-style component definition.
But with setup()-style definition, we have to assign useCSSModule('custom-name') to some variable and export from setup(), thus, I cannot export custom names like $globalStyle.

If $- prefix is not allowed in exports from setup(), I think $style should also be banned and we may need to update the documents. 🤔
(Like what vue-router does: with composition API, we use router instead of this.$router)

There is already a warning in version 3.0.5, see https://codesandbox.io/s/adoring-khayyam-5qrr4?file=/src/index.ts

There is already a warning in version 3.0.5, see https://codesandbox.io/s/adoring-khayyam-5qrr4?file=/src/index.ts

wow thank you :)


bridge_with_slack: Do not use a stale Zulip client for send_message.

This is based on https://github.com/zulip/zulip/commit/ff647dff03f178c329240c0e938d3fff8fbc5ab0, from #761.

Seems reasonable, let's just make sure to come back to this when we fix #761.


Add Link APIs for better suspense control

Compatibility with current API is preserved.
This is based on the idea of curi router [1] that allows also passing
function as children in the Link component that gets the navigating
state as argument.
I've also passed navigating in getProps and if you're interested in this
approach I think the arguments of getProps and children function could
be the same.
This new functionality enables usages like the one below:
<Link to="">
  {navigating =>
Home {navigating && <Spinner />}
}
</Link>

[1] https://github.com/pshrmn/curi/blob/master/packages/react-dom/src/Link.tsx
NOTE: async/await demands further rollup/babel config so promises were
preferred here.

@ryanflorence not sure if you're interested in such an API. Feel free to close if not.
I just experimented in a suspense enabled app and this API enabled loading indicators in menu items as the next page loads.

This is interesting, going to leave open but not totally considering it right now (which I recognize is like a year later)


The 'responsive' prop on the Button component has no effect

The Button component has the following prop:
/**
* If true, button scales to 100% width on small form factors.
*/
responsive: PropTypes.bool,

https://github.com/salesforce/design-system-react/blob/master/components/button/index.jsx#L177
This prop does not appear to have any effect when set to true (or false naturally).
This issue is demonstrated on the storybook example:
http://design-system-react-components.herokuapp.com/iframe.html?id=sldsbutton--doc-site-base-neutral&args=&viewMode=story
Looks like at some point the code conditionally adding the class was accidentally left out.
It should probably add the class slds-max-small-size--1-of-1 or some conditional variant of slds-button_stretch. In the past it was slds-max-small-button--stretch - this was removed in this commit https://github.com/salesforce/design-system-react/commit/a796c5b1fe1a967f1427a4fbd3ec4c9710d7592d on 22 Jul 2016:
https://github.com/salesforce/design-system-react/commit/a796c5b1fe1a967f1427a4fbd3ec4c9710d7592d#diff-1beac10e4cb18d36a1e2e3de7103d0f359da4b9b5748c851ce1c8061f1a803aeL143

I would like to work on this Issue
Please assign to me and guide me once


redirect loop

Hi, I want to get users' events using the office 365 api after sign up. However, I can't seem to get logged in. I don't know if this is an error from my azureAd setup or some routing issue.

Hello @djluck,
I'm having the same problem.  Any progress at your end @pauldd91?

You possibly have your settings incorrect on the azure admin,
Tutorial Link on Medium.com
I wrote a brief tutorial, could you review your oauth/url  settings in azure?

Did anyone solve this?

Hello @jkd65 @AshBT @paulthealien @sbr464 ,
I'm also struggeling this issue. I don't get any error. How can I debug this.

SOLVED :)
#How to reproduce the issue
This only occures if you try to login with an account which is also a Windows Live, Hotmail or similar acount
How solve it
you need to create a user within Azure AD
Add verfied domain name

Go to AD
Domain Names
Add a Domain Name
Verify it at your domain register

Add a user

Go to Add
Users and Groups
All users
Add
Reset the password
Login on MS site and change password
Login on your app


[beta] backport doc fix for CARGO_PRIMARY_PACKAGE

Beta backport of #8891, since this is a new feature, I think it would be good to have the documentation correct from the start.

r? @alexcrichton
(rust-highfive has picked a reviewer for you, use r? to override)

:warning: Warning :warning:

Pull requests are usually filed against the master branch for this repo, but this one is against rust-1.49.0. Please double check that you specified the right target!

@bors: r+

:pushpin: Commit 56ca6c8cc58e49ae49ae5efe201e56d131373231 has been approved by alexcrichton

:hourglass: Testing commit 56ca6c8cc58e49ae49ae5efe201e56d131373231 with merge b9216831aac72cfa8167996e3a94d976461e3fd9...

:sunny: Test successful - checks-actions
Approved by: alexcrichton
Pushing b9216831aac72cfa8167996e3a94d976461e3fd9 to rust-1.49.0...


Horseshoe and Horseshoe+ Priors

From Andrew (via direct e-mail):
In implementing stan_lm and stan_glm, maybe we should have the horseshoe and horseshoe+ priors as precoded options:
http://andrewgelman.com/2015/02/17/bayesian-survival-analysis-horseshoe-priors/
That way the user can just use these prior routinely.  This could give a bit boost to Stan for the sort of many-predictors “machine learning” regression problems where people are now running lasso.
I also want hierarchical models, of course, but within the context of lm and glm this could be a very useful addition, no?

I agree (but I'm a little biased)!  What sort of implementation would this be?  For instance, would it be at the level of specification we used (i.e. the high-level Stan grammar), or a low-level C++ for--say--some conditional posteriors?
I haven't dug into the implementation details of Stan, or even HMC, so I don't really know what the possibilities are, but I imagine that some more solvery could really improve things.
Anyway, always glad to discuss further.

@jgabry this exists in rstanarm, no? Closing the issue.

Another good case study topic.  They never made it
into the manual.

On Mar 4, 2016, at 6:11 PM, Rob Trangucci<EMAIL_ADDRESS>wrote:
Closed #1303.
—
Reply to this email directly or view it on GitHub.

True; I have examples coded in an Rmd file for HS and HS+ priors; we can
add this as an issue in the example modes.
Rob
On Fri, Mar 4, 2016 at 6:16 PM, Bob Carpenter<EMAIL_ADDRESS>wrote:

Another good case study topic. They never made it
into the manual.

On Mar 4, 2016, at 6:11 PM, Rob Trangucci<EMAIL_ADDRESS>wrote:
Closed #1303.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
https://github.com/stan-dev/stan/issues/1303#issuecomment-192515980.

On Fri, Mar 4, 2016 at 6:11 PM, Rob Trangucci<EMAIL_ADDRESS>wrote:

@jgabry https://github.com/jgabry this exists in rstanarm, no? Closing
the issue.

Yeah already in rstanarm


fees: DA

Describe your changes
Add GasCost vectors for DA actions, addAction / ActionPlan skeletons, and make gas fee costs consistent with protobuf encodings (https://github.com/penumbra-zone/penumbra/issues/3940)
Issue ticket number and link
References #4212
Checklist before requesting a review

[x] If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason:

@erwanor @zbuc should we make the DA fees be counted towards the block_space instead of the execution?

@erwanor @zbuc should we make the DA fees be counted towards the block_space instead of the execution?

Do you mean the part multiplied by the step count? I think there is both a per-step block space and per-step execution time cost that should be accounted for. Doesn't each step incur a block space cost of storing liquidity positions?

@erwanor @zbuc should we make the DA fees be counted towards the block_space instead of the execution?

Do you mean the part multiplied by the step count? I think there is both a per-step block space and per-step execution time cost that should be accounted for. Doesn't each step incur a block space cost of storing liquidity positions?

yeah that's true, would the block_space therefore be something like proto encoding cost of action + (dutch_action_schedule.description.step_count * 8)?

proto encoding cost of action + (dutch_action_schedule.description.step_count * 8 bytes / step)

I am operating under the assumption (that I am not 100% sure of) that every step, a LP will be closed (and withdrawn?) and a new one opened.
So I think it should be something like proto encoding cost of action + dutch_action_schedule.description.step_count * (PositionOpen block space cost + PositionClose block space cost + PositionWithdraw block space cost)

I don't think I follow — how does the chain opening and closing positions on its own add data to a future block?

I don't think I follow — how does the chain opening and closing positions on its own add data to a future block?

I suppose it's not adding new Actions to the block and instead using only additional storage space in the JMT for the position data, and we don't account for JMT space usage in gas pricing.


Fix linting issues

@absidue :)

@ChunkyProgrammer seems like the linting issues arent gone yet #175 #174 #173 #172


[WIP] Support dynamic keypath member lookup

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


Code Schools API ping receives 500 error

Bug Report
What is the current behavior?
Fetching from the code_schools endpoint yields a 500 server error.
What is the expected behavior?
Fetching from the code_schools endpoint should yield a 200 success notice and operationcode.org/code_schools should render properly.
What steps did you take to get this behavior?
Open dev tools and go to operationcode.org/code_schools
Additional Info
Operating System
Linux Fedora 23 and MacOS latest
Browser
Chrome (59 and latest) and Firefox (latest)

I noticed that this got merged without passing CI build:
https://github.com/OperationCode/operationcode_backend/pull/164
I'm wondering if this could be the root of the problem. :thinking:

Fixed in #171
@sethbergman called it!


java.lang.IllegalArgumentException: Can not create a Path from a null string

Hi
I'm unable to insert data to HBase, because my job is failing with exception:
App > 16/07/06 12:16:58 task-result-getter-1 WARN TaskSetManager: Lost task 3.0 in stage 0.0 (TID 3, ip-172-31-19-56.eu-west-1.compute.internal): java.lang.IllegalArgumentException: Can not create a Path from a null string
App > at org.apache.hadoop.fs.Path.checkPathArg(Path.java:125)
App > at org.apache.hadoop.fs.Path.(Path.java:137)
App > at org.apache.spark.rdd.PairRDDFunctions$$anonfun$saveAsHadoopDataset$1$$anonfun$13.apply(PairRDDFunctions.scala:1197)
App > at org.apache.spark.rdd.PairRDDFunctions$$anonfun$saveAsHadoopDataset$1$$anonfun$13.apply(PairRDDFunctions.scala:1190)
App > at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:66)
App > at org.apache.spark.scheduler.Task.run(Task.scala:89)
App > at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:214)
App > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
App > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
App > at java.lang.Thread.run(Thread.java:745)

my hbase-site.xml is:
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<property>
    <name>hbase.cluster.distributed</name>
    <value>true</value>
</property>
<property>
    <name>zookeeper.recovery.retry</name>
    <value>3</value>
</property>
<property>
    <name>hbase.regionserver.info.port</name>
    <value>16030</value>
</property>
<property>
    <name>hbase.zookeeper.quorum</name>
    <value>remote_IP</value>
</property>
<property>
    <name>hbase.rootdir</name>
    <value>hdfs://remote_IP:9000/hbase</value>
</property>
<property>
    <name>hbase.fs.tmp.dir</name>
    <value>/user/${user.name}/hbase-staging</value>
</property>
<property>
    <name>hadoop.tmp.dir</name>
    <value>/tmp/hadoop-${user.name}</value>
</property>
    <!-- Put any other property here, it will be used -->
</configuration>

my Hbase version:
HBase Version   1.0.0, revision=984db9a1cae088b996e997db9ce83f6d4bd565ad
Any suggesions?

Could you share your code in the writing path?

I just upgraded our Spark implementation at Splice Machine and I hit the same issue.  It looks like the output committer tries to write to the outputPath.  I did not have
mapreduce.output.fileoutputformat.outputdir set which caused the issue.
    val committer = FileCommitProtocol.instantiate(
      className = classOf[HadoopMapReduceCommitProtocol].getName,
      jobId = stageId.toString,
      outputPath = conf.value.get("mapreduce.output.fileoutputformat.outputdir"),
      isAppend = false).asInstanceOf[HadoopMapReduceCommitProtocol]
    committer.setupJob(jobContext)

Hope this helps,
John

@zhzhan I just hit the same problem. @jleach4 were you able to resolve the issue?

@mavencode01 The issue is hitting https://issues.apache.org/jira/browse/SPARK-21549. For reference: https://issues.apache.org/jira/browse/SPARK-18191.
Workaround is to explicitly set the property to a dummy value.

@weiqingy thanks for the quick reply but I tried setting the property and the job still fails with same error.
--conf spark.hadoop.mapred.output.dir=/tmp --conf spark.hadoop.mapreduce.output.fileoutputformat.outputdir=/tmp

@mavencode01 You may want to set that property in mapred-site.xml, and restart hadoop cluster. Also, you can also use SHC branch-2.2 (https://github.com/hortonworks-spark/shc/tree/branch-2.2), which we make a fix for this issue.

@weiqingy sweet!!! Thanks for the quick reply. Appreciate


Exported PackedScene in C# script is not visible in the inspector

Godot version
v4.0.2.stable.mono.official [7a0977ce2]
System information
Windows 11
Issue description
Exported PackedScene variables do not appear in the editor. I've attempted restarting the whole editor, closing my code editor, closing and reopening all scenes, but PackedScenes do not appear in the editor.
{

   	[Export]
   	public PackedScene _Bullet;

https://i.imgur.com/gLiIADL.png
Steps to reproduce
-Export a packedscene variable
-packedscene variable does not appear
Minimal reproduction project
N/A

I can't reproduce this in GDScript in 4.1.dev d6dde819b (Linux), both with and without a leading underscore.
@export var bullet: PackedScene
@export var _underscore_bullet: PackedScene

Can't reproduce on v4.1.dev.mono.custom_build [8c729f0f3] on windows.
	[Export]
   	public PackedScene FirstBullet;

	[Export]
	public PackedScene SecondBullet;

	[Export]
	public PackedScene _ThiredBullet;

	[Export]
	public PackedScene fourth_bullet;

	[Export]
	public PackedScene _fifth_bullet;

@Woolton, Hope you did "Build Solution" after updating the source files, that is needed for C# scripts.

Can't reproduce on v4.1.dev.mono.custom_build [[8c729f0]

This appears to be a more recent build of Godot 4, would you recommend using this over the stable version? I can only consistently get Export variables to work by closing the editor after building.


The extension for video/quicktime should map to .mov, not .qt

.qt is a deprecated extension, and while this was once accurate it means that looking up the mime for .mov and then getting the extension for the returned video/quicktime results in mismatched extensions.

Finally got a chance to look into this.
The problem is that the qt extension is named first in both [mime-db](https://github.com/jshttp/mime-db/blob/master/db.json#L6746) and Apache mime types file.
This is where mime-db draws it's type info from, and it maintains the extension ordering.  Both this module and the mime-types module prefer the first extension when mapping type -> extension.   And I suspect neither I nor the mime-types authors are interested in special casing this in our code.  The solution really needs to be in either mime-db or Apache's types file.
So... I'd suggest you file an issue with mime-db to that affect.  You might also file a bug with the Apache project, but I don't know how willing they'll be to change there.


Package class structure refactor

Refactor wasm wrapper and plugin classes and add support for WrapPackage
IWrapper
This is an instance of a wrapper (plugin or wasm)
In the case of plugins it has state, this could be true of wasm in the future as well
interface IWrapper {
  package: WrapPackage;
  invoke(options: InvokeOptions<Uri>, client: Client): Promise<InvokeResult<unknown>>;
}

IWrapPackage
This is the representation of a Wrapper's Build Artifacts (wrap package)
All methods return promises, so the package does not need to live in memory for there to be in instance of it
It is responsible for knowing how to create an instance of a wrapper (IWrapper)
The createWrapper method takes a client and uris used in resolution (e.g. ["ens/test.eth", "ipfs/Qmsdas"])
because those two things are needed to get the appropriate environment variables for the wrapper.
interface IWrapPackage {
  getManifest(): Promise<WrapManifest>;
  getAbi(): Promise<WrapAbi>;
  createWrapper(client: Client, uris: Uri[]): Promise<IWrapper>;
}

IWasmPackage
This is the wasm version of IWrapPackage.
It has an additional method getWasmModule because wasm wrappers have a wasm module.
interface IWasmPackage extends IWrapPackage {
  getWasmModule(): Promise<ArrayBuffer>;
}

IPluginPackage
This is the plugin version of IWrapPackage.
interface IPluginPackage extends IWrapPackage {
}

IInterfacePackage
This is the interface version of IWrapPackage.
Not sure hot the createWrapper method would work for this package.
interface IInterfacePackage extends IWrapPackage {
}

WasmPackage
This is a base implementation of the IWasmPackage.
You only need to pass in a IWasmPackageReader in the constructor and it will create a IWasmPackage.
The methods are not implemented in this example, but in reality they would be. They all depend on this.reader
class WasmPackage implements IWasmPackage {
  constructor(public readonly reader: IWasmPackageReader) {
  }

  getManifest(): Promise<WrapManifest>;
  getAbi(): Promise<WrapAbi>;
  getWasmModule(): Promise<ArrayBuffer>;
  createWrapper(client: Client, uris: Uri[]): Promise<Wrapper>;
}

IWasmPackageReader
This is a service that can fetch files for a single wasm wrapper.
interface IWasmPackageReader {
  getFile(options: GetFileOptions): Promise<ArrayBuffer | undefined>;
}

Blocked by: #1102

Closed by: https://github.com/polywrap/toolchain/pull/1169


tcp provider: error code 0x2746

Client
PHP version

7.3

Microsoft ODBC Driver version

msodbcsql 17

OS

Tested with Docker image : php:7.3-fpm-alpine, php:7.3-fpm, Centos7

Openssl version

tested with 1.1.1d, 1.0.2k, 1.0.1e but still get the same error

Server
SQL Server version

SQL 2005 sp4 standard edition

OS

Windows server 2003

I'm trying connect my laravel application on linux to a sql 2005 but i've got this error

and i got to know it's a matter of ssl connection so i've tested with downgraded openssl but i still can't solve this problem
as far as i know the matter is that Client and Server's ssl version doesn't match
and sql 2005 does not support TLS1.2 so i downgraded openssl version on linux but still didn't work.
and on local (windows10) everything works fine but on linux i have been suffering with this error.
let me show you the connection packet (Microsoft Message Analyzer used)
laravel on windows 10 With SQL 2005 on windows server 2003

at first client tries to connect with TLS1.2 and then seems like it negotiates with the server and
agrees on using TLS1.0.
everyhintg works fine
laravel on linux(ubuntu 18.0.4 and centos7) With SQL 2005 on windows server 2003

although i downgraded the openssl version and configured it to use TLS1.0 only but
it still seems like it still using TSL1.2 and is not negotiable.
in addition i found something strange in packet between docker on windows10 and sql2005 on windows sever 2003

on records
indicates TLS1.0
but in the fragment - body
indicates TLS1.2
i'm confused which ssl version is actullay used and don't understand why the connection can't proceed.
and this is my docker file
FROM php:7.3-fpm

RUN apt-get update && apt-get install -y \
    build-essential \
    libpng-dev \
    libjpeg62-turbo-dev \
    libfreetype6-dev \
    locales \
    zip \
    libzip-dev \
    jpegoptim optipng pngquant gifsicle \
    vim \
    unzip \
    git \
    wget \
    curl

RUN apt-get update && apt-get install -my wget gnupg

RUN apt-get update \
    && curl https://packages.microsoft.com/keys/microsoft.asc | apt-key add - \
    && curl https://packages.microsoft.com/config/debian/9/prod.list \
        > /etc/apt/sources.list.d/mssql-release.list \
    && apt-get install -y --no-install-recommends \
        locales \
        apt-transport-https \
    && echo "en_US.UTF-8 UTF-8" > /etc/locale.gen \
    && locale-gen \
    && apt-get update \
    && apt-get -y --no-install-recommends install \
        unixodbc \
        unixodbc-dev \
        msodbcsql17

RUN apt-get clean && rm -rf /var/lib/apt/lists/*

RUN docker-php-ext-install pdo pdo_mysql mbstring exif pcntl
RUN docker-php-ext-configure gd --with-gd --with-freetype-dir=/usr/include/ --with-jpeg-dir=/usr/include/ --with-png-dir=/usr/include/
RUN docker-php-ext-install gd

RUN pecl install sqlsrv pdo_sqlsrv \
    && docker-php-ext-enable sqlsrv pdo_sqlsrv

WORKDIR /usr/local/src/
RUN wget https://www.openssl.org/source/old/1.0.2/openssl-1.0.2k.tar.gz \
    && tar -xvzf openssl-1.0.2k.tar.gz \
    && cd openssl-1.0.2k \
    && ./config --prefix=/usr/local/ssl --openssldir=/usr/local/ssl shared zlib \
    && make \
    && make install

RUN cd /etc/ld.so.conf.d/ \
    && echo /usr/local/ssl/lib > openssl-1.0.2k.conf \
    && echo PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/local/ssl/bin" > /etc/environment \
    && source /etc/environment

RUN curl -sS https://getcomposer.org/installer | php -- --install-dir=/usr/local/bin --filename=composer

EXPOSE 9000
CMD ["php-fpm"]

and in this case
Linux is the client
so i want to specify which SSL version it should use like windows
like following

i can enable SSL when windows is a client or a server
how can i do it on linux?

@dkrdj8989 for your information we no longer support Windows server 2003 and SQL 2005 sp4

#252
this solved my problem
and Thanks yitam :D

@dkrdj8989 I am having the same issue
Could I please request your updated Dockerfile after the fix so I can isolate what you changed?
My Dockerfile is similar to your initial one.
Thanks!


Can you release the package?

Your project is very good.Can you release the package?

There's a bunch of tagged releases; I don't know what you mean with "release the package"?

Publish package.

What does that mean?

Or let me put it this way: what problem are you facing?

I want to use your package, but the team requires a released package to use it.

 Beyond that a "releasing" or "publishing" a package doesn't really mean anything. Tagging a release is essentially "releasing a version".
You can see the tags in git, on GitHub, or on pkg.go.dev:
https://pkg.go.dev/zgo.at/zcache/v2
https://pkg.go.dev/zgo.at/zcache

Thank you.The released package is formal.The formal package is required by the development team.

The released package is formal. The formal package is required by the development team.

I have no idea what that means either.


Warnings related to string.h with newest versions of GCC

🐛 Bug Report
Recently, related to LLVM Loader, I've seen that there's some warnings with strlen and strncpy which were not present on my version of GCC ( https://github.com/metacall/core/pull/137#issuecomment-840881892 ). This warnings indicate that there can be an out of bounds error or similar, so it should be reviewed.
Expected Behavior
No warnings shown.
Current Behavior
Warnings shown.
Possible Solution
I have not investigated it yet, but we should check the bounds properly.
Steps to Reproduce
Using GCC 9 seems to trigger them.

hey i would like to work on this issue if it is still open?

Most of these have been solved, but I do not trust them.
I think we should add some way to safely handle strings, standardized in the whole project. Something like this:
https://github.com/metacall/core/commit/9586750fe1231c30c54b1d936751ee5df763aaee#diff-453f830a73f17cd076f14418fcf1313db6b1eea785b89108dd2536dcee5b5dccR38-R45


README: Add Model Number for LG UltraFine 4k 2nd Gen

Thanks for building this app. Here are my diagnostics for one LG 5k display (1st gen as I could find out now 😭) and 2 LG 4K displays (presumably 2nd gen, I just ordered them on Amazon last week?). Hope this helps. I got it hoping it would mitigate the auto-adjustment issue I'm seeing with my 5k display as previously described in #18:

my display occasionally seems to adjust the brightness when no discernible ambient light as changed.

[69734662: Optional({
    DisplayBacklight = 500;
    DisplayBluePointX = "0.1503906";
    DisplayBluePointY = "0.05371094";
    DisplayBrightReflection = 505;
    DisplayBundleURL = "/System/Library/Displays/";
    DisplayDarkReflection = "1.1";
    DisplayFixedPixelFormat = 1;
    DisplayGreenPointX = "0.2646484";
    DisplayGreenPointY = "0.6904297";
    DisplayHorizontalImageSize = 340;
    DisplayLeakage = "0.419";
    DisplayLowestLevel = 2;
    DisplayLowestMeasured = "0.4323";
    DisplayProductID = 41028;
    DisplayProductName =     {
        ar = "\U200fLCD \U0645\U0644\U0648\U0646\U0629";
        "ca_ES" = "LCD en color";
        "cs_CZ" = "Barevn\U00fd LCD";
        "da_DK" = "LCD-farvesk\U00e6rm";
        "de_DE" = "Farb-LCD";
        "el_GR" = "\U0388\U03b3\U03c7\U03c1\U03c9\U03bc\U03b7 \U03bf\U03b8\U03cc\U03bd\U03b7 LCD";
        "en_AU" = "Colour LCD";
        "en_GB" = "Colour LCD";
        "en_US" = "Color LCD";
        "es_ES" = "LCD color";
        "es_XL" = "LCD color";
        "fi_FI" = "V\U00e4ri-LCD";
        "fr_CA" = "ACL couleur";
        "fr_FR" = "LCD couleur";
        "he_IL" = "\U200fLCD \U05e6\U05d1\U05e2\U05d5\U05e0\U05d9";
        "hi_IN" = "\U0930\U0902\U0917\U0940\U0928 LCD";
        "hr_HR" = "LCD u boji";
        "hu_HU" = "Sz\U00ednes LCD";
        id = "LCD Warna";
        "it_IT" = "LCD colori";
        "ja_JP" = "\U30ab\U30e9\U30fcLCD";
        "ko_KR" = "\Uceec\Ub7ec LCD";
        ms = "Warna LCD";
        "nb_NO" = "Farge-LCD";
        "nl_NL" = "Kleuren-LCD";
        "pl_PL" = "Kolor LCD";
        "pt_BR" = "LCD Colorido";
        "pt_PT" = "LCD a Cores";
        "ro_RO" = "LCD color";
        "ru_RU" = "\U0426\U0432\U0435\U0442\U043d\U043e\U0439 \U0416\U041a-\U0434\U0438\U0441\U043f\U043b\U0435\U0439";
        "sk_SK" = "Farebn\U00fd LCD";
        "sv_SE" = "F\U00e4rg-LCD";
        "th_TH" = "LCD \U0e2a\U0e35";
        "tr_TR" = "Renkli LCD";
        "uk_UA" = "\U041a\U043e\U043b\U044c\U043e\U0440\U043e\U0432\U0438\U0439 LCD";
        "vi_VN" = "LCD M\U00e0u";
        "zh_CN" = "\U5f69\U8272LCD";
        "zh_TW" = "\U5f69\U8272LCD";
    };
    DisplayRedPointX = "0.6796875";
    DisplayRedPointY = "0.3203125";
    DisplaySubPixelLayout = 1;
    DisplayVendorID = 1552;
    DisplayVerticalImageSize = 220;
    DisplayViewAngleAffectsGamma = 1;
    DisplayWeekManufacture = 36;
    DisplayWhiteGamma = "2.2";
    DisplayWhitePointX = "0.3125";
    DisplayWhitePointY = "0.3291016";
    DisplayYearManufacture = 2019;
    IODisplayAttributes = {length = 40, bytes = 0x67617476 00000000 73676c66 04000000 ... 676c6664 00000000 };
    IODisplayConnectFlags = {length = 4, bytes = 0x00080000};
    IODisplayEDID = {length = 256, bytes = 0x00ffffff ffffff00 061044a0 00000000 ... 00000000 0000d090 };
    IODisplayEDIDOriginal = {length = 256, bytes = 0x00ffffff ffffff00 061044a0 00000000 ... 00000000 0000d090 };
    IODisplayHasBacklight = 1;
    IODisplayIsDigital = 1;
    IODisplayIsHDMISink = 0;
    IODisplayLocation = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPP/EGP0@0/IOPP/EGP1@0/IOPP/GFX0@0/AMDRadeonX6000_AmdRadeonControllerNavi14/ATY,Boa@0/display0/AppleBacklightDisplay";
    IODisplayMobileBLTable = {length = 36, bytes = 0x00110000 02900344 043d0592 076509e4 ... 583a7a96 aae1eeed };
    IODisplayPrefsKey = "Alias:0/AppleBacklightDisplay-610-a044";
    IOFBTransform = 0;
    IOGFlags = 4;
    "display-refresh-rate-policy" = {length = 8, bytes = 0x0000000000000001};
    "display-resolution-preview-icon" = "/System/Library/Displays/Contents/Resources/Overrides/DisplayVendorID-610/DisplayProductID-a044-9d9da0.tiff";
    "display-rotation-policy" = {length = 8, bytes = 0x0000000000000001};
    dspc =     (
        {length = 18, bytes = 0xd5910050c08038700820980859d71000001a},
        {length = 18, bytes = 0xe7910050c080c2710820980859d71000001a},
        {length = 18, bytes = 0xdc910050c08024720820980859d71000001a},
        {length = 18, bytes = 0xe4910050c08027720820980859d71000001a}
    );
    "edid-patches" =     (
                {
            data = {length = 36, bytes = 0x00000010 00000000 00000000 00000000 ... 00000000 00000000 };
            offset = 90;
        }
    );
    "resolution-preview-height" = 96;
    "resolution-preview-width" = 154;
    "resolution-preview-x" = 36;
    "resolution-preview-y" = 65;
    "scale-resolutions" =     (
        {length = 8, bytes = 0x0000100000000a00},
        {length = 8, bytes = 0x00000e00000008c0},
        {length = 8, bytes = 0x00000c0000000780},
        {length = 8, bytes = 0x00000a8000000690},
        {length = 8, bytes = 0x00000900000005a0},
        {length = 16, bytes = 0x00000a00000006400000000100200000},
        {length = 16, bytes = 0x00000a00000005a00000000100200000},
        {length = 16, bytes = 0x00000780000004b00000000100200000},
        {length = 16, bytes = 0x00000780000004380000000100200000},
        {length = 16, bytes = 0x00000500000002d00000000100200000},
        {length = 12, bytes = 0x000006720000041a00000001},
        {length = 12, bytes = 0x000005a00000038400000001},
        {length = 12, bytes = 0x000005000000032000000001},
        {length = 12, bytes = 0x00000480000002d000000001},
        {length = 12, bytes = 0x000004000000030000000001},
        {length = 12, bytes = 0x000003480000020d00000001},
        {length = 12, bytes = 0x000003200000025800000001},
        {length = 12, bytes = 0x00000280000001e000000001},
        {length = 16, bytes = 0x00000f00000009600000000900a00000},
        {length = 16, bytes = 0x00000d20000008340000000900a00000},
        {length = 16, bytes = 0x00000b40000007080000000900a00000},
        {length = 16, bytes = 0x00000a00000006400000000900a00000},
        {length = 16, bytes = 0x00000800000005000000000900a00000},
        {length = 16, bytes = 0x00000780000004b00000000900a00000},
        {length = 16, bytes = 0x00000780000004380000000900200000},
        {length = 16, bytes = 0x00000500000002d00000000900200000}
    );
    slopeLimitGamma = 0;
    "target-default-ppmm" = "10.39";
}), 458662313: Optional({
    ContainerID = "FF5E6AB6-8840-4BE5-A0C2-E56E1658B0B8";
    DisplayBluePointX = "0.1503906";
    DisplayBluePointY = "0.05957031";
    DisplayBrightnessAffectsGamma = 1;
    DisplayBundleURL = "/System/Library/Displays/";
    DisplayGreenPointX = "0.2646484";
    DisplayGreenPointY = "0.6904297";
    DisplayHasHardwareBrightnessSmoothing = 1;
    DisplayHorizontalImageSize = 600;
    DisplayPort =     {
        PowerValue = 5;
    };
    DisplayProductID = 23313;
    DisplayProductName =     {
        ar = "LG UltraFine";
        "ca_ES" = "LG UltraFine";
        "cs_CZ" = "LG UltraFine";
        "da_DK" = "LG UltraFine";
        "de_DE" = "LG UltraFine";
        "el_GR" = "LG UltraFine";
        "en_AU" = "LG UltraFine";
        "en_GB" = "LG UltraFine";
        "en_US" = "LG UltraFine";
        "es_ES" = "LG UltraFine";
        "es_XL" = "LG UltraFine";
        "fi_FI" = "LG UltraFine";
        "fr_CA" = "LG UltraFine";
        "fr_FR" = "LG UltraFine";
        "he_IL" = "LG UltraFine";
        "hi_IN" = "LG UltraFine";
        "hr_HR" = "LG UltraFine";
        "hu_HU" = "LG UltraFine";
        id = "LG UltraFine";
        "it_IT" = "LG UltraFine";
        "ja_JP" = "LG UltraFine";
        "ko_KR" = "LG UltraFine";
        ms = "LG UltraFine";
        "nb_NO" = "LG UltraFine";
        "nl_NL" = "LG UltraFine";
        "pl_PL" = "LG UltraFine";
        "pt_BR" = "LG UltraFine";
        "pt_PT" = "LG UltraFine";
        "ro_RO" = "LG UltraFine";
        "ru_RU" = "LG UltraFine";
        "sk_SK" = "LG UltraFine";
        "sv_SE" = "LG UltraFine";
        "th_TH" = "LG UltraFine";
        "tr_TR" = "LG UltraFine";
        "uk_UA" = "LG UltraFine";
        "vi_VN" = "LG UltraFine";
        "zh_CN" = "LG UltraFine";
        "zh_TW" = "LG UltraFine";
    };
    DisplayRedPointX = "0.6796875";
    DisplayRedPointY = "0.3203125";
    DisplaySerialNumber = 484832;
    DisplayVendorID = 7789;
    DisplayVerticalImageSize = 340;
    DisplayWeekManufacture = 12;
    DisplayWhiteGamma = "2.2";
    DisplayWhitePointX = "0.3125";
    DisplayWhitePointY = "0.3291016";
    DisplayYearManufacture = 2017;
    IODisplayAttributes = {length = 40, bytes = 0x67617476 00000000 73676c66 04000000 ... 676c6664 00000000 };
    IODisplayConnectFlags = {length = 4, bytes = 0x00000000};
    IODisplayEDID = {length = 256, bytes = 0x00ffffff ffffff00 9e6d115b e0650700 ... 00000000 00009290 };
    IODisplayEDIDOriginal = {length = 256, bytes = 0x00ffffff ffffff00 9e6d115b e0650700 ... 00000000 00009290 };
    IODisplayIsDigital = 1;
    IODisplayIsHDMISink = 0;
    IODisplayLocation = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPP/EGP0@0/IOPP/EGP1@0/IOPP/GFX0@0/AMDRadeonX6000_AmdRadeonControllerNavi14/ATY,Boa@3/display0/AppleDisplay";
    IODisplayPrefsKey = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPP/EGP0@0/IOPP/EGP1@0/IOPP/GFX0@0/AMDRadeonX6000_AmdRadeonControllerNavi14/ATY,Boa@3/display0/AppleDisplay-9e6d-5b11";
    IOFBTransform = 0;
    IOGFlags = 4;
    "display-icon" = "/System/Library/Displays/Contents/Resources/Overrides/DisplayVendorID-1e6d/DisplayProductID-5b11.icns";
    "display-resolution-preview-icon" = "/System/Library/Displays/Contents/Resources/Overrides/DisplayVendorID-1e6d/DisplayProductID-5b11.tiff";
    "resolution-preview-height" = 114;
    "resolution-preview-width" = 202;
    "resolution-preview-x" = 11;
    "resolution-preview-y" = 47;
    "scale-resolutions" =     (
        {length = 8, bytes = 0x0000190000000e10},
        {length = 8, bytes = 0x0000168000000ca8},
        {length = 8, bytes = 0x0000140000000b40},
        {length = 8, bytes = 0x0000100000000900},
        {length = 8, bytes = 0x00000c8000000708},
        {length = 16, bytes = 0x00001000000008700000000100200000},
        {length = 16, bytes = 0x00000f00000008700000000100200000},
        {length = 16, bytes = 0x00000a00000006400000000100200000},
        {length = 16, bytes = 0x00000780000004b00000000100200000},
        {length = 16, bytes = 0x000006900000041a0000000100200000},
        {length = 16, bytes = 0x00000500000003200000000100200000},
        {length = 12, bytes = 0x00000b400000065400000001},
        {length = 12, bytes = 0x00000a00000005a000000001},
        {length = 12, bytes = 0x000008000000048000000001},
        {length = 12, bytes = 0x000007800000043800000001},
        {length = 12, bytes = 0x00000640000004b000000001},
        {length = 12, bytes = 0x000006400000038400000001},
        {length = 12, bytes = 0x000005a00000032a00000001},
        {length = 12, bytes = 0x00000540000002f400000001},
        {length = 12, bytes = 0x000005000000040000000001},
        {length = 12, bytes = 0x00000500000002d000000001},
        {length = 12, bytes = 0x000004000000030000000001},
        {length = 12, bytes = 0x000004000000024000000001},
        {length = 12, bytes = 0x000003c00000025800000001},
        {length = 12, bytes = 0x000003c00000021c00000001},
        {length = 12, bytes = 0x000003480000020c00000001},
        {length = 12, bytes = 0x000003200000025800000001},
        {length = 12, bytes = 0x00000280000001e000000001},
        {length = 16, bytes = 0x0000190000000e100000000900a00000},
        {length = 16, bytes = 0x0000168000000ca80000000900a00000},
        {length = 16, bytes = 0x0000140000000b400000000900a00000},
        {length = 16, bytes = 0x00001000000009000000000900a00000},
        {length = 16, bytes = 0x00000c80000007080000000900a00000}
    );
    slopeLimitGamma = 0;
}), 458630020: Optional({
    ContainerID = "F1A71E54-3BA8-4BA6-A705-D55AE8E049B1";
    DisplayBluePointX = "0.1523438";
    DisplayBluePointY = "0.04980469";
    DisplayBrightnessAffectsGamma = 1;
    DisplayBundleURL = "/System/Library/Displays/";
    DisplayGreenPointX = "0.2802734";
    DisplayGreenPointY = "0.6738281";
    DisplayHasHardwareBrightnessSmoothing = 1;
    DisplayHorizontalImageSize = 530;
    DisplayPort =     {
        PowerValue = 5;
    };
    DisplayProductID = 23419;
    DisplayProductName =     {
        ar = "LG UltraFine";
        "ca_ES" = "LG UltraFine";
        "cs_CZ" = "LG UltraFine";
        "da_DK" = "LG UltraFine";
        "de_DE" = "LG UltraFine";
        "el_GR" = "LG UltraFine";
        "en_AU" = "LG UltraFine";
        "en_GB" = "LG UltraFine";
        "en_US" = "LG UltraFine";
        "es_ES" = "LG UltraFine";
        "es_XL" = "LG UltraFine";
        "fi_FI" = "LG UltraFine";
        "fr_CA" = "LG UltraFine";
        "fr_FR" = "LG UltraFine";
        "he_IL" = "LG UltraFine";
        "hi_IN" = "LG UltraFine";
        "hr_HR" = "LG UltraFine";
        "hu_HU" = "LG UltraFine";
        id = "LG UltraFine";
        "it_IT" = "LG UltraFine";
        "ja_JP" = "LG UltraFine";
        "ko_KR" = "LG UltraFine";
        ms = "LG UltraFine";
        "nb_NO" = "LG UltraFine";
        "nl_NL" = "LG UltraFine";
        "pl_PL" = "LG UltraFine";
        "pt_BR" = "LG UltraFine";
        "pt_PT" = "LG UltraFine";
        "ro_RO" = "LG UltraFine";
        "ru_RU" = "LG UltraFine";
        "sk_SK" = "LG UltraFine";
        "sv_SE" = "LG UltraFine";
        "th_TH" = "LG UltraFine";
        "tr_TR" = "LG UltraFine";
        "uk_UA" = "LG UltraFine";
        "vi_VN" = "LG UltraFine";
        "zh_CN" = "LG UltraFine";
        "zh_TW" = "LG UltraFine";
    };
    DisplayRedPointX = "0.6796875";
    DisplayRedPointY = "0.3154297";
    DisplaySerialNumber = 130493;
    DisplayVendorID = 7789;
    DisplayVerticalImageSize = 300;
    DisplayWeekManufacture = 5;
    DisplayWhiteGamma = "2.2";
    DisplayWhitePointX = "0.3125";
    DisplayWhitePointY = "0.3291016";
    DisplayYearManufacture = 2020;
    IODisplayAttributes = {length = 40, bytes = 0x67617476 00000000 73676c66 00000000 ... 676c6664 00000000 };
    IODisplayConnectFlags = {length = 4, bytes = 0x00000000};
    IODisplayEDID = {length = 384, bytes = 0x00ffffff ffffff00 1e6d7b5b bdfd0100 ... 00000000 00008f90 };
    IODisplayEDIDOriginal = {length = 384, bytes = 0x00ffffff ffffff00 1e6d7b5b bdfd0100 ... 00000000 00008f90 };
    IODisplayIsDigital = 1;
    IODisplayIsHDMISink = 0;
    IODisplayLocation = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPP/EGP0@0/IOPP/EGP1@0/IOPP/GFX0@0/AMDRadeonX6000_AmdRadeonControllerNavi14/ATY,Boa@2/display0/AppleDisplay";
    IODisplayPrefsKey = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPP/EGP0@0/IOPP/EGP1@0/IOPP/GFX0@0/AMDRadeonX6000_AmdRadeonControllerNavi14/ATY,Boa@2/display0/AppleDisplay-1e6d-5b7b";
    IOFBTransform = 0;
    "display-icon" = "/System/Library/Displays/Contents/Resources/Overrides/DisplayVendorID-1e6d/DisplayProductID-5b7b.icns";
    "display-resolution-preview-icon" = "/System/Library/Displays/Contents/Resources/Overrides/DisplayVendorID-1e6d/DisplayProductID-5b7b.tiff";
    drng = {length = 18, bytes = 0x000000fd00303c1e873c010a202020202020};
    "resolution-preview-height" = 90;
    "resolution-preview-width" = 160;
    "resolution-preview-x" = 33;
    "resolution-preview-y" = 47;
    slopeLimitGamma = 0;
    trng = {length = 312, bytes = 0x00000000 00000000 00000000 00000000 ... 00000000 00000000 };
}), 458629651: Optional({
    ContainerID = "DAF47A78-848B-4734-B26A-D82EB98C1192";
    DisplayBluePointX = "0.1523438";
    DisplayBluePointY = "0.04980469";
    DisplayBrightnessAffectsGamma = 1;
    DisplayBundleURL = "/System/Library/Displays/";
    DisplayGreenPointX = "0.2802734";
    DisplayGreenPointY = "0.6738281";
    DisplayHasHardwareBrightnessSmoothing = 1;
    DisplayHorizontalImageSize = 530;
    DisplayPort =     {
        PowerValue = 5;
    };
    DisplayProductID = 23419;
    DisplayProductName =     {
        ar = "LG UltraFine";
        "ca_ES" = "LG UltraFine";
        "cs_CZ" = "LG UltraFine";
        "da_DK" = "LG UltraFine";
        "de_DE" = "LG UltraFine";
        "el_GR" = "LG UltraFine";
        "en_AU" = "LG UltraFine";
        "en_GB" = "LG UltraFine";
        "en_US" = "LG UltraFine";
        "es_ES" = "LG UltraFine";
        "es_XL" = "LG UltraFine";
        "fi_FI" = "LG UltraFine";
        "fr_CA" = "LG UltraFine";
        "fr_FR" = "LG UltraFine";
        "he_IL" = "LG UltraFine";
        "hi_IN" = "LG UltraFine";
        "hr_HR" = "LG UltraFine";
        "hu_HU" = "LG UltraFine";
        id = "LG UltraFine";
        "it_IT" = "LG UltraFine";
        "ja_JP" = "LG UltraFine";
        "ko_KR" = "LG UltraFine";
        ms = "LG UltraFine";
        "nb_NO" = "LG UltraFine";
        "nl_NL" = "LG UltraFine";
        "pl_PL" = "LG UltraFine";
        "pt_BR" = "LG UltraFine";
        "pt_PT" = "LG UltraFine";
        "ro_RO" = "LG UltraFine";
        "ru_RU" = "LG UltraFine";
        "sk_SK" = "LG UltraFine";
        "sv_SE" = "LG UltraFine";
        "th_TH" = "LG UltraFine";
        "tr_TR" = "LG UltraFine";
        "uk_UA" = "LG UltraFine";
        "vi_VN" = "LG UltraFine";
        "zh_CN" = "LG UltraFine";
        "zh_TW" = "LG UltraFine";
    };
    DisplayRedPointX = "0.6796875";
    DisplayRedPointY = "0.3154297";
    DisplaySerialNumber = 130255;
    DisplayVendorID = 7789;
    DisplayVerticalImageSize = 300;
    DisplayWeekManufacture = 5;
    DisplayWhiteGamma = "2.2";
    DisplayWhitePointX = "0.3125";
    DisplayWhitePointY = "0.3291016";
    DisplayYearManufacture = 2020;
    IODisplayAttributes = {length = 40, bytes = 0x67617476 00000000 73676c66 00000000 ... 676c6664 00000000 };
    IODisplayConnectFlags = {length = 4, bytes = 0x00000000};
    IODisplayEDID = {length = 384, bytes = 0x00ffffff ffffff00 1e6d7b5b cffc0100 ... 00000000 00008f90 };
    IODisplayEDIDOriginal = {length = 384, bytes = 0x00ffffff ffffff00 1e6d7b5b cffc0100 ... 00000000 00008f90 };
    IODisplayIsDigital = 1;
    IODisplayIsHDMISink = 0;
    IODisplayLocation = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPP/EGP0@0/IOPP/EGP1@0/IOPP/GFX0@0/AMDRadeonX6000_AmdRadeonControllerNavi14/ATY,Boa@1/display0/AppleDisplay";
    IODisplayPrefsKey = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPP/EGP0@0/IOPP/EGP1@0/IOPP/GFX0@0/AMDRadeonX6000_AmdRadeonControllerNavi14/ATY,Boa@1/display0/AppleDisplay-1e6d-5b7b";
    IOFBTransform = 0;
    "display-icon" = "/System/Library/Displays/Contents/Resources/Overrides/DisplayVendorID-1e6d/DisplayProductID-5b7b.icns";
    "display-resolution-preview-icon" = "/System/Library/Displays/Contents/Resources/Overrides/DisplayVendorID-1e6d/DisplayProductID-5b7b.tiff";
    drng = {length = 18, bytes = 0x000000fd00303c1e873c010a202020202020};
    "resolution-preview-height" = 90;
    "resolution-preview-width" = 160;
    "resolution-preview-x" = 33;
    "resolution-preview-y" = 47;
    slopeLimitGamma = 0;
    trng = {length = 312, bytes = 0x00000000 00000000 00000000 00000000 ... 00000000 00000000 };
})]

Just to double check, for each display, do you see an option to enable automatic brightness?
This is what I see for my 1st gen 5k display:

As far as I know, for second gen UltraFines there should be an option to enable automatic brightness adjustments below the slider.

Nope, I do not have this option for my 5K display. Only for the 4K displays. So I presume it's in fact a 1st gen?

Yes, looks like it's a 1st gen, which is confirmed by the model number (thankfully).
Now with the model number of the 2nd gen 4k model you have provided, I have everything I need to distinguish 1st gen from 2nd gen. Thanks!
The next question is, how do I handle 2nd gen displays... I could either leave them alone and let them handle their own automatic brightness, or I could sync brightness to them anyway and treat them the same as 1st gen displays... I think the 2nd option is the best for most people.


radio button labels do not show up on arc dc create wizard on catalina

Azure Data Studio Version:
Version: 1.21.0-insider
Commit: f941f9910bd481220cb8d2e944d51163731e849d
Date: 2020-08-03T05:35:46.115Z
VS Code: 1.48.0
Electron: 9.1.0
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 19.5.0

Steps to Reproduce:

Fire up the 'Create New Controller' (+) button on the Azure Arc Controllers:
Accept the license terms and click next: (assuming right azdata and kubectl are already installed on the box).
In the wizard that shows up choose a cluster config and click next to go to 2nd page.
The second page is 'Choose the config profile'.
Actual:
On this page the labels corresponding to various profile options are missing:

Expected:
There should have been labels corresponding to each radio option for the config profile visible.

This was a regression from a recent check-in. Reverting that check-in fixed this. We will revisit a proper check-in for the one that was reverted later.


Doesn't work with ESM

Version
4.0.4
Reproduction link
https://github.com/openmod/OpenMod.WebServer/tree/master/OpenMod.Dashboard/web
Steps to reproduce

Copy files to a web server (e.g. nginx)
Open site

What is expected?
App should show and not generate an error
What is actually happening?
vue.esm-browser.prod.js?module:1 TypeError: Cannot read property 'parent' of null
    at warnDeprecatedUsage (vue-router.esm.js?module:2152)
    at setup (vue-router.esm.js?module:2071)
    at kt (vue.esm-browser.prod.js?module:1)
    at vue.esm-browser.prod.js?module:1
    at vue.esm-browser.prod.js?module:1
    at B (vue.esm-browser.prod.js?module:1)
    at O (vue.esm-browser.prod.js?module:1)
    at b (vue.esm-browser.prod.js?module:1)
    at E (vue.esm-browser.prod.js?module:1)
    at T (vue.esm-browser.prod.js?module:1)

Tested with es-module-shims and Chrome's own ESM implementation, both resulted in the same error

Not sure if you are referring to this: https://github.com/vuejs/vue-router-next/issues/694.
Otherwise, please read https://new-issue.vuejs.org/?repo=vuejs/vue#why-repro

This is a different issue and unrelated to #694. I will try to create an online repro, but you can also use the repo I have linked.

Here is the repro, please reopen the issue: https://plnkr.co/edit/0TYlxtktHJ1MszrL


Fixing bug with Appium set value for iOS

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 2

Complexity increasing per file
==============================
- Ginger/GingerCore/Drivers/Appium/SeleniumAppiumDriver.cs  2

See the complete overview on Codacy


mtail: 3.0.0-rc4 -> 3.0.0-rc34

Motivation for this change
3.0.0-rc4 is over 2 years old. no release yet...
Things done
This update has a tiny lie.
I saw from the manual that go2nix is normally used for goDeps but on the go2nix repo it says to use vgo2nix when there a go.mod file present.
The thing is that vgo2nix fails with 3.0.0-rc34 but not with master, so I generated the file with master. master only has tiny changes. It's mostly a deps update. (check https://github.com/google/mtail/compare/v3.0.0-rc34...0150dadbe24cbb3cc09cd5859ce8632541fb235a)
If it's not OK I could another way. I also wanted to switch the package to buildGoModule but I got some problem: https://github.com/NixOS/nixpkgs/issues/79355
Also, is gotools needed?

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

/nix/store/z0dk0mhfsni2lpaqpw2pnjgs0y9vzsyl-mtail-3.0.0-rc4-bin	  40.4M
/nix/store/cpdsp1m9v93jg4iz462rhrni2k08kimz-mtail-3.0.0-rc34	  41.3M

Another tiny thing is that mtail --version will print:
mtail version 3.0.0-rc34 git revision invalid:-use-make-to-build go version go1.13.7 go arch amd64 go os linux
since I only set Version. We could also set Branch and Revision.
https://github.com/google/mtail/blob/7b4270cb6e8b6ed1f2febe48e370cb68d38681f9/cmd/mtail/main.go#L77-L80

It seems my problem with buildGoModule doesn't happen anymore. I made the change to use buildGoModule now.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review-may-2019/3032/115

done, thanks @doronbehar

I done all the changes and updated to rc35. thanks

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


Now, examples page is down.

I couldn't access to https://visjs.github.io/vis-network/examples/ from https://visjs.org/.

Me neither

same here

Nor us :-(

Sorry about that, it should be back again soon.


API FR: GetSWSVersion()

Like native GetAppVersion().
Thanks.

ok, there is no need already, because I can get it from S&M.ini [General]

added in v2.10.0

CF_GetSWSVersion()


Quantify ability of SARS-CoV-2 embeddings to capture recombinant lineages relative to parental lineages

A clear gap in the current structure of the paper is some quantification of how well SARS-CoV-2 embeddings capture relationships between recombinant lineages and their parental lineages. We quantify the ability of flu embeddings to capture reassortment, so we should do the same for SARS-CoV-2.
Recombination is more complicated than reassortment, since the recombinant genomes are not distinct combinations of existing lineages but some continuous distribution of the parental lineages at different breakpoints.
One approach could be to quantify the pattern we observe by visually inspecting embeddings of two parental lineages and their recombinant offspring. In practice, we look for the recombinant samples to place "between" the two parental lineages in an embedding. We could quantify this placement by calculating the average distance between samples in the parental lineages A and B from each other and the average distances between samples from the recombinant lineage X and either parental lineage A or B. We expect lineages A and B to map farther apart from each other on average than A and X and B and X.

Resolved by 1639a47c790bddbcb0a1990a008a16b19ac9ba9e and 03c47e68fde3286fedacbf1fd400502078636f45.


ComponentTypeDependencyExtension - Add

Provides ability to get the job dependency on an arbitrary component or set of components.
@jkeon This may provide the opportunity to decouple task drivers from systems (if we want that)
Question:
Does making these extension methods of ComponentSystemBase and EntityManager make sense?
Alternatively (or additionally) we can have the extension methods work off of the ComponentType<T> instances themselves.
Examples:

ComponentType<MyComponent>.ReadOnly().GetDependency(EntityManager) (or system)
myComponentCollection.GetDependency(EntityManager) (or system)

EntityManager and ComponentSystemBase are the providers for the pointer to the underlying ComponentDependencyManager instance. That's why the current extension methods are setup as they are.
What is the current behaviour?
Currently, the only way to get the scheduling dependency of a collection of components is through an EntityQuery.
What is the new behaviour?
With a reference to EntityManager or ComponentSystemBase instance developers can calculate the scheduling dependency on an arbitrary collection of components.
What issues does this resolve?

None

What PRs does this depend on?

None

Does this introduce a breaking change?

[ ] Yes
[x] No

Ah... sorry. I just saw this in action here: https://github.com/decline-cookies/station-x/pull/430/
I think we should remove the ComponentSystemBase extensions and just have the EntityManager one.
This line:
dependsOn = JobHandle.CombineDependencies(dependsOn, this.GetDependency(ComponentType.ReadWrite<IsSelected>()));
Reads to me like we are getting this system's dependency for the component which is a bit confusing since my system may not interact with the component at all.
dependsOn = JobHandle.CombineDependencies(dependsOn, EntityManager.GetDependency(ComponentType.ReadWrite<IsSelected>()));
This reads better that we are trying to get whatever this component's global access dependency is.
This would also read well:
`dependsOn = JobHandle.CombineDependencies(dependsOn, ComponentType.ReadWrite().GetDepencency(ref EntityManager));


remove TSLint disable comments for store action message creator

Pull request checklist

[ ] Addresses an existing issue: Fixes #0000
[ ] Added relevant unit test for your changes. (npm run test)
[ ] Verified code coverage for the changes made. Check coverage report at: <rootDir>/test-results/unit/coverage
[x] Ran precheckin (npm run precheckin)
[ ] Added screenshots/GIFs for UI changes.

Description of changes
remove TSLint disable comments for store action message creator

I left a couple of comments about filenames?

Done.


Sprite.getBounds() does not take Sprite.scale into account before updateTransform is called

This may be more of an FYI to save other people the hour it took me to figure this out, but after changing the scale of a Sprite, you need to call updateTransform (or render) for getBounds to be correct.
Here's an example: https://jsfiddle.net/davidfig/mb1s6Lv4/1/

Fixed in v4 👍


Feature request: Use last modified files when log limit is hit.

Describe what happened:

I configured DD-Agent on an Atlassian Bamboo server which runs a few hundred builds per day. The log structure for build output is similar to: /bamboo_home/xml-data/builds/*/download-data/build_logs/*.log
I get a warning similar to 2018-12-06 19:48:26 UTC | WARN | (file_provider.go:98 in FilesToTail) | Reached the limit on the maximum number of files in use:  100
Confirming the issue, I got 50.000+ files in different subfolders. They need to be stored for archival reasons. Only a few hundred (or few thousands) are modified each day.

Describe what you expected:

I expected DD-Agent would be looking at the last modified files instead of opening every feel each time.

Suggestion:
Modify the method FilesToTail to order files by last modified instead of alphabetical.

@tmichelet is my understanding correct that the files are temporarily opened, tailed and then closed? Or will they be permanently kept open? I'm thinking I could make a shell script to symlink them to a log folder as a quick workaround.

@jannylund they are permanently kept open (only closed on logrotate or when stopping the tailer)

I made a workaround in the meanwhile.

Create a new folder that DD is watching.
Make a shellscript that uses find to fetch the latest logfiles into a list.
Symlink them into the new folder (and remove ones that are older).
Schedule from crontab every minute.

This causes the DD Agent to open up tails on the symlink added event and close them on delete event.

@jannylund this workaround should do the job indeed! On our end, we're queuing some work to properly tackle this issue. Thanks again for reporting

Hi @jannylund, do you have the name format of your files ? And do you have control on the name of those files ?
Getting the ordered list of files by last modified date for 50k+ files is quite resource intensive and might seriously increase the agent footprint on its host. we're investigating a more gentle way of doing it based on the filenames.


write a middleware to filter repeat request

I don't know much about ua architecture, what i use to do is define a set(), add the urls i request to it. It's surely a redundant thing but not much work in a spider

@misterpilou
I don't know @panhaoyu 's solution, but if I do, I will consider using Bloom Filter


Set overflow:auto for long lines

For long items I can't click remove item button (x)

After PR is merged it will looks like

Up


merge from arlac77/npm-package-template-esm-only

README.md

docs(README): update from template

:tada: This PR is included in version 10.0.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Support the format String Manipulation Processor

Is your feature request related to a problem? Please describe.
The format processor described in #697 was not yet implemented.
Describe the solution you'd like
Implement the format processor. It should be able to construct a string from a format string which includes both literal values and other keys.
The following is a conceptual example. The exact format may vary.
"messageString" : "${/http_method} ${/http_path} response: ${status_code}

With the following Event:
"http_method" : "POST",
"http_path" : "/hello",
"status_code" : 200

Will modify the Event to be:
"http_method" : "POST",
"http_path" : "/hello",
"status_code" : 200,
"messageString" : "POST /hello response: 200"

Implemented in #2424


Bugfix for race conditions

Hi @girishranganathan. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/assign @andraxylia

/lgtm

@girishranganathan: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
62b42806358d2037c28ded3053ac802cdd66d87c
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test all

@girishranganathan: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
62b42806358d2037c28ded3053ac802cdd66d87c
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/ok-to-test

@girishranganathan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
62b42806358d2037c28ded3053ac802cdd66d87c
link
/test istio-pilot-e2e

prow/istio-unit-tests.sh
62b42806358d2037c28ded3053ac802cdd66d87c
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-unit-rests

/test e2e-pilot

@girishranganathan is this PR still in development? Is there any way we can rebase ?

Hello @douglas-reid, technically no. I had finished the work almost a month back. @geeknoid had approved the code. I think e2e tests were failing and they were being fixed. When I checked a few weeks back, @xiaolanz had made some changes attempting to fix the issues. Now I am kind of confused/concerned that if I try to bring my changes in, it will overwrite @xiaolanz.
Please advise.


sasquatch: drop blanket -Werror (fix gcc-11 build)

Noticed build failure on gcc-11:
$ nix-build -E 'with import ./.{}; sasquatch.override { stdenv = gcc11Stdenv; }'
unsquashfs.c:1908:5:
  error: this 'if' clause does not guard... [-Werror=misleading-indentation]
 1908 |     if(swap)
      |     ^~

Let's defer warning squashing and code fixes to upstream.
Cc @Pamplemousse

Result of nixpkgs-review pr 139350 at 0322f7b6 run on x86_64-linux 1

6 packages built successfully:

binwalk (python39Packages.binwalk)
diffoscope
python38Packages.binwalk
python38Packages.binwalk-full
python39Packages.binwalk-full
sasquatch


Mostly minor cleanup and fixes, added two new features.

New:

can do juci . new_file.py for instance
added option to remove trailing whitespace characters and add trailing newline if missing on save. Off by default since it create annoying commits if a git-repository contains trailing whitespace characters already.

Tested and works on OS X, MSYS2, Debian stable/testing and Ubuntu 14


Set python version to 3.8.13 during image creation

Thanks for opening this! I made a similar PR here https://github.com/mhw32/data-centric-deep-learning/pull/15/files that also removes some double counting of requirements.txt

Closing this in favor of https://github.com/mhw32/data-centric-deep-learning/pull/15