Huggyllama 7b Model Fails to Speak Turkish Despite Training with Alpaca Subset

I encountered an issue while training the Huggyllama 7b model using the Alpaca subset of 1500 instructions translated into Turkish. Despite training the model for 3 epochs with a context size of 2048, the trained model is unable to generate coherent responses in Turkish. Even simple instructions directly from the training set cannot be followed by the trained model. I have performed tests both before and after merging, and the issue persists.
To troubleshoot this problem, I conducted three training runs using Qlora with different settings and diverse datasets, varying the examples and formats. However, the model's inability to speak Turkish persisted across all training runs.
I suspect that the low number of epochs may be a contributing factor to this issue. However, I am unsure if there might be any other underlying bugs or challenges that I am facing. I kindly request assistance in understanding why the trained model is unable to generate coherent responses in Turkish and any recommendations for resolving this issue.
Steps to Reproduce:

Train the Huggyllama 7b model using the Alpaca subset of 1500 instructions translated into Turkish.
Utilize a context size of 2048 during the training process.
Train the model for 3 epochs.
Test the trained model by providing simple instructions from the training set.
Observe that the trained model fails to follow the instructions and generate coherent responses in Turkish.

Expected Behavior:
The Huggyllama 7b model should be able to understand and generate coherent responses in Turkish, specificly when provided with instructions directly from the training set.
Additional Information:

Environment: Colab, Qlora, Python 3.10, cu118, a100 40gb
Training Runs: 5 Epochs: 3
Dataset Examples and Formats: Varied across training runs
Issue Occurrence: Consistently observed across all training runs and testing phases.

Please let me know if any additional information or details are required to diagnose and resolve this issue.

7b is too small for translation
You need 33b or 65b
On Sat, Jun 17, 2023, 6:30 PM kostum123 @.***> wrote:

Closed #223
https://github.com/OpenAccess-AI-Collective/axolotl/issues/223 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/OpenAccess-AI-Collective/axolotl/issues/223#event-9559923079,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIQ4BIVSUA4PDL7YUFH2DLXLZK2JANCNFSM6AAAAAAZKMKYI4
.
You are receiving this because you are subscribed to this thread.Message
ID: <OpenAccess-AI-Collective/axolotl/issue/223/issue_event/9559923079@
github.com>

Additionally, qlora doesn't train enough parameters for more advanced instructions

Using the 13b model and another model as a base, I was able to make my model speak Turkish(bad) with 1500 instruction data. I think this is due to the fact that the model did not see much or almost no Turkish content while being trained by Facebook. I couldn't decide whether to continue training on text first and teach it to follow instructions after or to increase the instruction dataset to 15 thousand.

Feel free to join discord since this is a more involved question. My experience on language fine-tuning is that you need to pass a lot of data for fine-tuning.
A larger model would definitely help as said by others. I'm currently using with lora to some decent results, however, qlora is not so good for me. Fullweights would ideally be best.

Thanks for your advice. I have joined the Discord. Now, I will try the Qlora method one last time, but this time with more instruction answer examples. I will report results on discord.


VIDEO-6636: Update TwilioVideo dependency to 4.6.0

4.6.0 (September 17, 2021)
This release adds support for Apple Silicon arm64 Macs, updates WebRTC and modernizes our use of several WebRTC APIs. Thank you for your feedback on 4.6.0-beta1 and for your interest in Apple Silicon development.
Features

TwilioVideo.xcframework now supports the simulator on Apple Silicon arm64 Macs. #144

This results in a size increase for the SDK during development.
App store download size is not affected.

Enhancements

This release is based on WebRTC M88.
The SDK uses Unified Plan SDP semantics instead of Plan-B. This brings several important benefits:

Improved interoperability with Firefox, Safari and Chrome in Peer-to-Peer and Go Rooms
Track level operations like publishing and unpublishing are more reliable

Improved performance of Room.getStats() by adopting the W3C standardized RTC stats API
Unused codecs for a track are removed from the local SDP offer in order to reduce the SDP size, once codecs for the track have been negotiated. [VIDEO-3532]

API Changes

The ordering of RemoteParticipantDelegate.onAudioTrackSubscribed() and RemoteParticipantDelegate.onVideoTrackSubscribed() is not strictly guaranteed. In this release the ordering of these callbacks may be different when compared to previous releases.
The value of LocalVideoTrackStats.framesEncoded now reflects the total number of frames encoded for a simulcast track.

Bug Fixes

Fixed performance problems with Room.getStats() where block callbacks could sometimes be significantly delayed. [CSDK-3475]
Fixed an interoperability issue with twilio-video.js when publishing media in Peer-to-Peer or WebRTC Go Rooms. #931

Known Issues

Audio playback fails when running a simulator on a Mac Mini. #182
Carthage is not currently a supported distribution mechanism for Twilio Video. Carthage does not currently work with .xcframeworks as documented here. Once Carthage supports binary .xcframeworks, Carthage distribution will be re-added.
Unpublishing and republishing a LocalAudioTrack or LocalVideoTrack might not be seen by Participants. #34
H.264 video might become corrupted after a network handoff. #147
iOS devices do not support more than three H.264 encoders. Refer to #17 for suggested work arounds.
Publishing H.264 video at greater than 1280x720 @ 30fps is not supported. If a failure occurs then no error is raised to the developer. [ISDK-1590]

Contributing to Twilio

All third-party contributors acknowledge that any contributions they provide will be made under the same open-source license that the open-source project is provided under.

[x] I acknowledge that all my contributions will be made under the project's license.

Leaving this PR in draft since I wanted to investigate https://github.com/twilio/twilio-video-app-ios/issues/170 on my M1 Mac. This app is building locally on my Intel MacBook Pro.

Building locally on an Apple Silicon (arm64) machine fails because App Center is pre-compiled and does not have an arm64 simulator slice.

ld: in /Users/ceagleston/Development/twilio-video-app-ios/Pods/AppCenter/AppCenter-SDK-Apple/iOS/AppCenter.framework/AppCenter(MSAppCenter.o), building for iOS Simulator, but linking in object file built for iOS, file '/Users/ceagleston/Development/twilio-video-app-ios/Pods/AppCenter/AppCenter-SDK-Apple/iOS/AppCenter.framework/AppCenter' for architecture arm64

The 4.0 major version of App Center is delivered as an XCFramework with arm64. Looking good, but now Firebase:

ld: in /Users/ceagleston/Development/twilio-video-app-ios/Pods/FirebaseAnalytics/Frameworks/FIRAnalyticsConnector.framework/FIRAnalyticsConnector(FIRAnalyticsConnector_a8eeba373b74508311b8b22b8d3202a6.o), building for iOS Simulator, but linking in object file built for iOS, file '/Users/ceagleston/Development/twilio-video-app-ios/Pods/FirebaseAnalytics/Frameworks/FIRAnalyticsConnector.framework/FIRAnalyticsConnector' for architecture arm64

I completed the dependency updates that did not require code changes (AppCenter/Distribute and Firebase). Unfortunately the last hold out is GoogleSignIn.framework which can only be fixed by updating FirebaseUI to major version 12. This requires code changes since GIDSignInDelegate no longer exists in GoogleSignIn v6.

I updated GoogleSignIn and tested on Intel Mac but not M1 Mac.


Move CircleCI docker image to main repo (close #454)

@sinedied I think this is obsolete now that you moved to AzureCI ?

Definitely, no need for this anymore 😄


First very basic bias correction functions

Please check if the PR fulfills these requirements

[x] This PR addresses an already opened issue (for bug fixes / features)
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[ ] HISTORY.rst has been updated
[ ] bumpversion (minor / major / patch) has been called
[ ] Tags have been pushed

What kind of change does this PR introduce? (Bug fix, feature, docs update, etc.)
Basic quantile mapping bias correction functions.

Does this PR introduce a breaking change? (Has there been an API change?)
No

Other information:

When merging, please put fixes #{issue number} in your comment to auto-close the issue that your PR addresses. Thanks!

Ideally Pat would also review so we start in the right direction.

Pull Request Test Coverage Report for Build 981

87 of 97 (89.69%)  changed or added relevant lines in 5 files are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.4%) to 91.839%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

xclim/indices/_multivariate.py
25
27
92.59%

xclim/bc/qm.py
55
63
87.3%

Files with Coverage Reduction
New Missed Lines
%

xclim/testing/common.py
4
82.61%

Totals

Change from base Build 944:
-0.4%

Covered Lines:
1373

Relevant Lines:
1495

💛  - Coveralls

I've no problem if the bias correction code stays in a branch for a while. Let's get comments from Pat. There is no rush in merging this.

I'd say that if all is missing is detrending and moving window, it should be merged and tagged as experimental in the docs and function help (?). This way, users would at least test the core functionality of q-q mapping.

Interpolation over the monthly correction factor is already in there (interp=True).

Review expected by Sept. 17.

Moved to xsd.


Use JsonReader interop with JsonSerializer

Fix up some tests

Before:

Method
Input
HubProtocol
Mean
Error
StdDev
Op/s
Gen 0
Gen 1
Allocated

Read
FewArguments
Json
3,157.1 ns
65.910 ns
134.638 ns
316,749.1
0.0153
-
480 B

Read
LargeArguments
Json
44,724.6 ns
2,950.102 ns
8,605.586 ns
22,359.1
4.2114
0.1221
102800 B

Read
ManyArguments
Json
6,184.8 ns
123.451 ns
121.245 ns
161,687.4
0.0305
-
1056 B

Read
NoArguments
Json
1,441.7 ns
28.604 ns
25.356 ns
693,640.3
0.0057
-
176 B

After:

Method
Input
HubProtocol
Mean
Error
StdDev
Op/s
Gen 0
Gen 1
Allocated

Read
FewArguments
Json
2,147.6 ns
42.544 ns
114.293 ns
465,638.8
0.0038
-
224 B

Read
LargeArguments
Json
16,928.1 ns
706.900 ns
2,039.569 ns
59,073.3
1.0834
0.0153
30904 B

Read
ManyArguments
Json
4,251.8 ns
83.215 ns
102.196 ns
235,193.3
0.0153
-
424 B

Read
NoArguments
Json
750.6 ns
14.886 ns
30.071 ns
1,332,260.4
0.0029
-
96 B

Newtonsoft and MsgPack for comparison:

Method
Input
HubProtocol
Mean
Error
StdDev
Op/s
Gen 0
Gen 1
Allocated

Read
FewArguments
MsgPack
629.2 ns
12.395 ns
13.777 ns
1,589,257.0
0.0076
-
224 B

Read
FewArguments
NewtonsoftJson
2,281.4 ns
44.465 ns
76.699 ns
438,329.8
0.0267
-
960 B

Read
LargeArguments
MsgPack
7,936.3 ns
498.136 ns
1,460.948 ns
126,003.9
1.0910
0.0229
30904 B

Read
LargeArguments
NewtonsoftJson
68,549.2 ns
1,352.304 ns
3,291.694 ns
14,588.1
1.9531
-
58840 B

Read
ManyArguments
MsgPack
1,099.8 ns
22.493 ns
18.783 ns
909,275.0
0.0114
-
400 B

Read
ManyArguments
NewtonsoftJson
4,164.0 ns
82.231 ns
123.080 ns
240,151.6
0.0458
-
1504 B

Read
NoArguments
MsgPack
318.3 ns
6.272 ns
7.222 ns
3,141,842.9
0.0038
-
120 B

Read
NoArguments
NewtonsoftJson
1,016.5 ns
26.047 ns
32.941 ns
983,747.3
0.0191
-
584 B

cc @ahsonkhan

Very nice! MsgPack still crushing JSON though zomg.

🆙 📅

Ping @halter73 @mikaelm12 we might get QB approval for this so review/approval would be nice (read necessary)

Please do review ASAP. Submitted for QB Approval.

Approved by QB for preview 6. Please get review approval and passing build before merging.

@BrennanConroy are we blocked on anything other than dependencies flowing in now? Looks like no (builds are red because of that and we have review approval). Just want to confirm where we stand.

are we blocked on anything other than dependencies flowing in now? Looks like no

That's correct, I might change the test commented on above, but that isn't blocking

My feeling is that we should just cherry-pick this over to the dependency update PR when it arrives, but I'm not sure. The other option is to receive the dependencies and then rebase/update this PR when they arrive. That would mean another PR validation turn before we can merge it though. (Thoughts @aspnet/build)

@anurse my leaning is strongly toward pushing a commit or two on top of what the dependency bot comes up with. Just need to wait for aspnet/EntityFrameworkCore#15940 and the official build including that.
BTW why does this PR say it's about "Preview 6" but target 'master'?

I was always planning on cherry-picking

Spoke with @natemcmaster . Let's do this the "right" way and cherry-pick only the change needed to unblock the dependency PR there (there is a breaking change that we need to react to).
Then, we rebase this PR on top of the newly-arrived corefx dependencies (when they hit the release branch), retarget the PR and get our PR validation build green.

Dependency flow should be available soon. https://github.com/aspnet/AspNetCore-Tooling/pull/650 just merged.
Once this build is done and published to Maestro, I would recommend updating your PR to use latest deps by running darc update-dependencies --channel '.NET Core 3 Release' and pushing the changes to Version.props/xml to your PR branch. The bot is still going to open a separate PR to flow dependency versions, but this will help you get PR checks running with updated dependencies before we complete the bot dependency flow into AspNetCore (and spot any problems that might exist)

Note

Dependency flow should be available soon. aspnet/AspNetCore-Tooling#650 just merged.

That's the wrong repo to watch for important updates from Extensions or lower. We're flowing dependencies through EF Core again both here and in 'master'.
In any case, I believe aspnet/AspNetCore#10856 is the dependency update PR of interest.

@aspnet/build Someone merge please :)
Helix is hanging it looks like.

QB approved and good to go. Merging away!


Can I use "isDayBlocked" or similar prop?

Ask your Question
Hi! Tonight I tried 4 react native date picker libraries and only this is so cool! THANKS!
Is there a similar prop of "isDayBlocked" (as the airbnb picker https://github.com/airbnb/react-dates)?
I know that there are the "minimumDate" and the "maximumDate" prop but in my project I have a invalid date between the minimum and the maximum date
example:
minimumDate={new Date(2020, 1, 1)}
maximumDate={new Date(2020, 10, 10)}
if the date 5th April 2020 is invalid, how I can disable the 5th April?

👋 Short answer: you can't. React-native-modal-datetime-picker uses a native iOS/Android picker under the hood and, as far as I know, the native picker doesn't allow you to block specific dates.

👋 Short answer: you can't. React-native-modal-datetime-picker uses a native iOS/Android picker under the hood and, as far as I know, the native picker doesn't allow you to block specific dates.


Java/C++/C#: Provide path-node locations via hasLocationInfo, not getLocation.

As discussed, this is slightly more flexible and would make my life a little easier in reusing the shared library (though I could work around it in other ways if this change is considered too disruptive). It also eliminates the only uses of DataFlowLocation, but  I'm fine with keeping it around for potential future uses.
cc @hvitved, @jbj, @dave-bartolomeo

@hvitved: It turns out the C# library uses PathNode.getLocation() in at least one place. While that's easy to fix (see latest commit) it makes me wonder whether it's perhaps a more widely used predicate than I had thought...

@hvitved: It turns out the C# library uses PathNode.getLocation() in at least one place. While that's easy to fix (see latest commit) it makes me wonder whether it's perhaps a more widely used predicate than I had thought...

It appears that this is the only place where it was used, and I don't mind the change from your last commit.

@hvitved / @aschackmull, could you re-approve (or merge straight away)?


Wingman v2.0.8 , Local model is not supporting

Wingman v2.0.8 , Local model is not supporting. LM Studio, Koboldcpp URL are not working, please provide documentation or tutorial or video about enabling local models. Thank you

I'm unfamiliar with LM Studio, but I just downloaded it and started a local inference server running llama 2 chat 7B q4_0 ggml. Using the OpenAI provider in Wingman, I changed the URL to http://localhost:1234/v1/chat/completions and things seem to just work (with the exception of recognizing the end of the completion stream, which may just be unique to LM Studio, but a bug none-the-less).
Can you provide some more information regarding your setup?
KoboldCpp support is almost finished - still porting this functionality from the previous major version.


The type for various variadic functions (_printf) are inaccurate in macOS type libraries

bv.type_libraries
[<typelib '/usr/lib/libSystem.B.dylib.mac-aarch64.1292.100.5':aarch64>]
lib = bv.type_libraries[0]
bv.import_library_object('_printf', lib)
<type: immutable:FunctionTypeClass 'int32_t(char const*)'>

It should be int32_t _printf(char const*, ...). This also affects functions like _scanf, vsprintf, snprintf, and potentially other variadic functions as well.
This does not affect Linux type libraries -- they are correct

Confirmed, not only for MacOS type libraries, but also in all ARM type libraries

Seems Rel: #5828?

Don't think it's related. Lack of type libraries is totally independent from heuristic analysis being off.

Fixed in 4.2.6443


Improve wallet creation report screen with "Your wallet is ready" message

User feedback from @crwatkins has indicated that the current wallet report screen would benefit from a message along the lines of:
"Your wallet has been created and locked successfully. Click Finish to show the unlock screen."
This is to overcome the jarring nature of the unexpected appearance of the Unlock screen.

Agreed

I've added in text to make the segue less jarring at the end of the wallet create.
Rather than using 'unlock', which we only use on the button, I have refered to the password entry screen directly.
Screenshot:

The similar label for Trezor wallet creation has been changed to:
Your Trezor wallet is now ready to use. Press "Finish" to show the PIN entry screen

Looks good to me.

Good.

Closing.


AWS::ApiGateway::UsagePlan cannot use a stage from  AWS::Serverless::Api

I have a AWS::Serverless::Api defined as
     Type: AWS::Serverless::Api
     Properties:
        StageName: test
        DefinitionUri: swagger.json

and a AWS::ApiGateway::UsagePlan defined as
    Type: AWS::ApiGateway::UsagePlan
    Properties:
      ApiStages:
        -
          ApiId: !Ref MyApiResource
          Stage: test
      Throttle:
        BurstLimit: 500
        RateLimit: 50
      UsagePlanName:
        Fn::Join: [
            "_",
            [
              "UsagePlan",
              !Ref "AWS::Region",
              !Ref "AWS::StackName"
            ]
          ]

If I run the cloud formation script it fails to create the UsagePlan with an error saying the stage test does not exist on the API.
If I instead comment out the usage plan and run the script and then run it again with the API and the usage plan enabled it will create the usage plan and link it to the stage properly.

So what i had to do to fix this was add DependsOn to the AWS::ApiGateway::UsagePlan as DependsOn: MyApiResourcetestStage not sure if there is a better way to do this.

DependsOn is the right solution. Your UsagePlan was being created before the Stage resource.

Alas, that still feels a bit hacky, since we're relying on the implicit naming scheme for the stage resource (which gets created by the Api resource), as opposed to referring to it directly. I.e. if MyApi resource has a StageName: MyStageName, then the DependsOn for a UsagePlan resource must list MyApiMyStageNameStage literal, otherwise it won't work.

@sanathkr, we're seeing the same problem for AWS::ApiGateway::BasePathMapping as well. Either AWS::Serverless::Api should wait until its Stage resource is fully created (so other resources that depend on Api may use that stage), or we have to rely on that undocumented Stage resource naming scheme with DependsOn. Otherwise, AWS::Serverless::Api is useless for all but the trivial cases (when nothing else but AWS::Serverless::Functions depend on it).

The serverless approach is nice and clean but not much mature in the api keys/stages/usage plans area. It creates an extra "Stage" (named "Stage") even if we define our own stage, and the field is mandatory.
I couldn't find a permanent solution for the dirty stacks, and usage plans inside the cloudformation script, so I wrote a bash script that deleted the stage named "Stage" and creates api keys, usage plans then assigns keys to plans. Parsing JSON in the bash, clearing the stages, takes away the clean and neat solution of serverless in the Api gateway : (
Here is the script:
#!/usr/bin/env bash

echo "==============================="
echo "Get id of the api (set output param ApiId in CF)"
echo "==============================="
APIID=$(aws cloudformation describe-stacks \
--stack-name my-stack \
--query 'Stacks[0].Outputs[?OutputKey==`ApiId`].OutputValue' \
--output text)

echo "==============================="
echo "Delete the Stage env"
echo "API ID: ${APIID}"
echo "==============================="
aws apigateway delete-stage \
--rest-api-id ${APIID} \
--stage-name 'Stage'

echo "==============================="
echo "Create usage plan for stage name: v1"
echo "API ID: ${APIID}"
echo "==============================="
USAGEPLANJSON=$(aws apigateway create-usage-plan \
--name "my-usage-plan" \
--description "Usage plan for low usage of api" \
--api-stages apiId="${APIID}",stage='v1' \
--throttle burstLimit=2,rateLimit=1)
echo ${USAGEPLANJSON}

echo "==============================="
echo "Created usage plan for v1"
echo "API ID: ${APIID}"
echo "Getting Usage plan Id for:"
echo "==============================="
USAGEPLANID=$(echo ${USAGEPLANJSON} | python -c 'import sys, json
print(json.load(sys.stdin)["id"])')

echo "==============================="
echo "Creating api key for v1"
echo "==============================="
APIKEYJSON=`aws apigateway create-api-key \
--name 'my-api-key' \
--description 'Used for security of the admin api' \
--enabled`
echo ${APIKEYJSON}

echo "==============================="
echo "Created api key for v1"
echo "==============================="
APIKEYID=$(echo ${APIKEYJSON} | python -c 'import sys, json
print(json.load(sys.stdin)["id"])')

echo "==============================="
echo "Create usage plan key for v1"
echo "API ID: ${APIID}"
echo "USAGE PLAN ID: ${USAGEPLANID}"
echo "API KEY ID: ${APIKEYID}"
echo "==============================="
aws apigateway create-usage-plan-key \
--usage-plan-id ${USAGEPLANID} \
--key-type "API_KEY" \
--key-id ${APIKEYID}

@bargom DO NOT delete the Stage Stage outside of CloudFormation. You are creating more of a headache for yourself. When you go to deploy a change, CloudFormation will try and update the resource and fail since the resource does not exist. You should never be deleting resources that are controlled by CloudFormation outside of CloudFormation (console, script, etc).
Just leave Stage Stage alone. It isn't harming anything or anyone by being there. Yes, we know this happens. For more info, see #191.

I see your point. But for me it is a security breach. I setup all my keys and environment (usage plans) for the stage I know. So, if I leave the "Stage" there, a developer can guess the endpoint, and can reach it freely. I don't want to leave any open points that I don't have control.
I think also deploying changes is more confusing, I deploy the full stack with a version number and run it in parallel until everything is confirmed, then switch the new version and delete the old one. I believe if someone following this approach and using API keys, it is best to delete the uncontrolled "Stage".
Thanks for letting me know it causes problems in update.

@bargom if you are using Lambda proxies you could manage the invocation of the lambda function from your "allowed" stages using the AWS::Lambda::Permission resource.
This way you could leave the Stage stage and it cannot be used.
LogicalResourceName:
  Type: AWS::Lambda::Permission
  Properties:
    Action: lambda:InvokeFunction
    FunctionName: arn:aws:lambda:region:account-id:function:function-name:alias-name
    Principal: apigateway.amazonaws.com
    SourceArn: arn:aws:execute-api:region:account-id:api-id/stage-name

@Nr18 that is a great idea. Some of my endpoints are using proxies, but most of them are connecting to lambdas w/o proxy, and some calls are passing parameters (and jwt tokens) to 3rd party API's to create a gateway to external application from internal apps.


GVFS destination folder not works

I tried to make a backup by using a GVFS volume but it seems it not works. I don't have investigated yet.
Copying /run/media/themimitoof/disk/DCIM/100MSDCF/DSC04937.JPG - Remaining: 870/871
!!! Unable to copy '/run/media/themimitoof/disk/DCIM/100MSDCF/DSC04937.JPG' file. Cause:
        [Errno 95] Operation not supported: '/run/user/1000/gvfs/smb-share:server=xxxx.xxx.io,share=xxx/cambak/2020-03-07/A6400/Pictures/DSC04937.JPG'

Currently backing up pictures of smartphones via GVFS and it works with cambak v2!
λ izumo ~ → cambak cp -n xxx /run/user/1000/gvfs/mtp:host=XXX/Mémoire\ interne\ partagée/DCIM cambak-xxx-phone-backups
✅ 739 files collected (697 pictures, 0 RAWs, 42 movies). 0 files skipped.
 100% |██████████████████████████████████████████████████████████████████████████████████| (739/739, 1 it/s)
✨ All files have been copied!


Unbound Local Error While training

Hi, I tried training a model and I got the following error.
Training SOM... 0%
UnboundLocalError                         Traceback (most recent call last)
 in ()
----> 1 net.train(0.2, 1000)
~\Anaconda3\lib\site-packages\simpsom-1.3.3-py3.7.egg\SimpSOM_init_.py in train(self, startLearnRate, epochs)
213             inputVec = self.data[np.random.randint(0, self.data.shape[0]), :].reshape(np.array([self.data.shape[1]]))
214
--> 215             bmu=self.find_bmu(inputVec)
216
217             for node in self.nodeList:
~\Anaconda3\lib\site-packages\simpsom-1.3.3-py3.7.egg\SimpSOM_init_.py in find_bmu(self, vec)
173                 minVal=dist
174                 bmu=node
--> 175         return bmu
176
177
UnboundLocalError: local variable 'bmu' referenced before assignment

Hello @Inder95,
It seems that when checking for the closest node to your input datapoints no distance passes the following if condition.
        minVal=np.iinfo(np.int).max
        for node in self.nodeList:
            dist=node.get_distance(vec)
            if dist < minVal:
                minVal=dist
                bmu=node
        return bmu

Is your data range very wide? It may be that the initial distances surpass the limit of minVal.
I increased the reference value to the machine limits for float. This should do the trick.
Alternatively, you can normalize your data to reduce the variance.
Try installing and running the last version (1.3.4) form here on github and see if it works now.

Thanks it still showed the same error but normalizing did the job. Thanks!

happened also to me
import SimpSOM as sps
net = sps.somNet(20, 20, cleanDataSet, PBC=True)
net.train(0.01, 100000)
**/usr/local/lib/python3.6/dist-packages/SimpSOM/__init__.py in find_bmu(self, vec)
UnboundLocalError: local variable 'bmu' referenced before assignmen**

How can I solve it?

Found sorry, the issue was with nan in the data


Way to build Tesseract with custom neural net

Your Feature Request
Hi, how can I do that and where is the data when your research lab do the best eng model

Please use our forum for questions.


the camera is broken?

librealsense
2.33.1 RELEASE

OS
Windows

Please provide a description of the problem
Backend in rs2_create_device(info_list:0B2D3CA8, index:0):
MFCreateDeviceSource(_device_attrs, &_source) returned: HResult 0x80070005: "Access is denied."

If there is an access denial on Windows, please check the camera privacy settings in Windows to make sure that access to the camera hardware and to camera applications is set to "On".  Instructions for how to do this are in the link below.
https://github.com/IntelRealSense/librealsense/issues/3381#issuecomment-503424789

thanks it works

Great news!  I'm very pleased to hear it.


Added version Badge for npm.

Added version Badge for npm.

If it has to be hard-coded, maybe we need to add a build step when npm versioning that will auto update it - tagging the issue #118 to keep it aligned.


image file not found

There is no file named pic/RGB_OR_1200x1200_001.png

I'm sorry that I forgot to upload this image to our remote repository. I have now uploaded the image to the 'pic' directory and the program should be able to run normally. You can also replace this image and then change the 'img_path' in the config file to your own image path.

Ok, thank you


language selection

what is the technique to change the src file depending on the language ? I get the required localization while I load the file, the application has the feature to change languages. how do I switch leaflet-measure to the required localisation? I tried but could not get it to work.
setting the language in the options in the version before was a lot easier.

How does the application feature to change the language work? Does changing the language generate a page reload? How are you loading the control into your application?
On April 18, 2018 at 2:42:26 AM, unnic (notifications<EMAIL_ADDRESS>wrote:
what is the technique to change the src file depending on the language ? I get the required localization while I load the file, the application has the feature to change languages. how do I switch leaflet-measure to the required localisation? I triedhttps://stackoverflow.com/questions/13748269/dynamically-change-script-src-client-side but could not get it to work.
setting the language in the options in the version before was a lot easier.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/ljagis/leaflet-measure/issues/109, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABIL-pIUrg0be9Sr9upjwWVdRMVZV867ks5tpu5ggaJpZM4TZkm3.

It gets the country of interest as a URL parameter and loads the relevant localization.

Does changing the language generate a page reload
yes

How are you loading the control into your application?
<script src="./src/leaflet-measure.de.js"></script>

I recently updated to v3 and also have a problem with the new localization selection.
In my use case, I need to generate a compiled (single minified/uglified file) with no external dependencies at runtime. In this scenario, you can't switch between languages when user makes a choice.
I prefer the old way, like in my original fork where localization support was added.

Finally, I updated to v3.1.0, making a dynamic import after language selection.

@pedroetb Hello, I need to do a dynamic import depending on the language of the browser, but I don't understand how to do it, at the moment I have it importing "leaflet-measure/dist/leaflet-measure", I have it in v3, I try to put the "localization" option , but my code does not work, I only need to do it in case it is Spanish or English

Hi @MarceloDiazz, check README. First, you have to build and then you can import dinamically the right file for desired localization.


Merged Byran's Commit, and Exposed Courses to Session Object

See commit messages for details. Also removed Prisma since it's no longer maintained.

Merging because I'm a gigachad and I never write false code, period.


How to get position(x,y,z) of hand landmark?

Plugin Version or Commit ID
v.0.8.2
Unity Version
2020.3.29f1
Your Host OS
Windows 10
Target Platform
UnityEditor
Description
Hi, I'm a Korean college student and I'm preparing a graduation project.
Our team is trying to develop a finger counter to make an AR game(like this video = https://youtu.be/p5Z_GGRCI5s ).
But to do this, we need to get the x, y, z values for each landmark.
How can I access it?
Code to Reproduce the issue
No response
Additional Context
First, our team is studying by looking at the solution script under Handtracking, but I don't know how to do it.
Thank you for your cooperation!

our team is studying by looking at the solution script under Handtracking, but I don't know how to do it.

Can you list specifically (e.g. showing the code) which parts you don't understand?
If they say they don't understand everything, all I can do is ask them to look at the code.
Anyway, a little older code might give you a better idea of what is going on.
https://github.com/homuler/MediaPipeUnityPlugin/blob/a16d74c0a170f3bf271df7a09a7b63f46a55a5f1/Assets/Mediapipe/Samples/Scenes/Hand Tracking/HandTrackingSolution.cs


[Umbrella issue] Translate qiskit-terra versions to qiskit

To avoid confusion and to follow the migration of qiskit-terra to qiskit, translate all package versions on experiments ran on terra to the corresponding qiskit version. See version comparison table for reference.
This will only change the package name/version associated with experiment results (eg. CSV files, data summary info), legacy package names installed for historical experiment runs should remain the same.

@1ucian0 @AngeloDanducci Here's an update on this issue and my findings as I translate package versions for all current results:
qiskit and qiskit-terra packages did not bump versions at the same time. As a result, since we have been tracking only latest patch versions of terra, as we translate those versions to qiskit, below we can see minor version gaps missed in qiskit (eg. jumping from qiskit v0.19.x to 0.0.22.x). The top table represents what we currently follow to build historical benchmarks using qiskit-terra:

The bottom table shows the corrected version map, with double the amount of qiskit versions to run benchmark experiments. Since qiskit has more package releases than terra, this means now we may need to fill those gaps of missing data entries, in order to keep the pattern of benchmarking every latest patch of each minor qiskit version.
I will update the issue description with the necessary steps for a complete update in this repo and in Metriq.


Break up arguments section

Break up the arguments section into arguments and handling files.

Was not able to include full type hints because of issues with custom sphinx directive we use to run the code.


Alternative to Json.NET ResolvePropertyName

I was wondering if there is any alternative to Json.NET ResolvePropertyName to be able to get properly cased property name from formatter instance.

Thanks for the suggestion, but this will not work in my case. I'm working on porting NodaTime serialization library to UTF8Json. Some NodaTime types (e.g. Interval) must be serialized into custom objects, sample could be found here https://github.com/nodatime/nodatime.serialization/blob/master/src/NodaTime.Serialization.JsonNet/NodaDateIntervalConverter.cs#L41. Those objects should respect the global serialization rules which are configured for property name - ContractResolver in JsonNet case. Those rules should be set up by clients of the library and should NOT be hardcoded.
For UTF8Json, the closest to "global" rules is StandardResolver, but as far as I understand it will only affect IL generated formatters for custom types, and there is no good way of accessing this configuration at formatter level.
As of right now, I ended up creating a DTO to workaround this issue, but this is not ideal.
https://github.com/DSilence/NodaTime.Serialization.Utf8Json/blob/develop/src/NodaTime.Serialization.Utf8Json/DS.NodaTime.Serialization.Utf8Json/NodaDateIntervalFormatter.cs

Thank you for your explanation, I don't think I've seen the functionality you need either.


The batch bug fix of 4.6.16 to KYLIN5

https://opencicd.kyligence.com/blue/organizations/jenkins/OpenSource%2FKylin-CI/detail/Kylin-CI/95/pipeline/


Ensure base class is absrtact in polymorphism

Description
Regen PR in sdk repo: https://github.com/Azure/azure-sdk-for-net/pull/30235
Checklist
To ensure a quick review and merge, please ensure:

[ ] The PR has a understandable title and description explaining the why and what.
[ ] The PR is opened in draft if not ready for review yet.

If opened in draft, please allocate sufficient time (24 hours) after moving out of draft for review

[ ] The branch is recent enough to not have merge conflicts upon creation.

Ready to Land?

[ ] Build is completely green

Submissions with test failures require tracking issue and approval of a CODEOWNER

[ ] At least one +1 review by a CODEOWNER
[ ] All -1 reviews are confirmed resolved by the reviewer

Override/Marking reviews stale must be discussed with CODEOWNERS first

We might need to make exceptions for this  in GA'd types as its a breaking change.  Technically if someone is using that ctor today it wouldn't work so it might be an acceptable break I have asked @KrzysztofCwalina to weigh in before we move forward.


TODO

[ ] Improve INFO logging.
[ ] Look for places to WARN log. Probably most in db methods.
[x] Forms vs basic auth fixes.
[ ] Do sqlite3 queries correctly (no sprintf). Never mind, don't actually care.
[x] Move initialize.js code to Starr library.
[x] Fix Radarr icon in menu bar.
[x] Replace hard coded time out.
[x] Default Instance.
[ ] Selectable columns (block lists needs indexers, others?).
[ ] Need special method to unmarshall Starr api errors.
[x] Display images in block list popovers?
[ ] Add Links to block lists.
[ ] Config file encryption

Add CF bulk delete via API


some new file additions

added a weather prediction code , and how to use map and arrange its elements in ascending order both in c++

@prabhleenkaur1007  contribute to https://github.com/Ishaan28malik/Get-Dev-Resources instead


Add the filter categories for all Samsung, Shopify, and SlackHQ documentations

Research on each documentation in the Samsung, Shopify, and SlackHQ section to filter them into Company Owned Documentation and Community Owned Documentation
After getting your answer, add the category like this in the README.md file at the front of the documentation wrapped in backticks ``
e.g.

Amazon S3 Docs - Amazon Simple Storage Service (Amazon S3) is storage for the internet. You can use Amazon S3 to store and retrieve any amount of data at any time, from anywhere on the web. - Company Owned Documentation

assign me to this

I'm available

@nobledeveloper01 you can work on this

Solved #118


Fixed problem with region

When I try run deploy I see next error:

  Config Error -------------------------------------------

     Missing region in config

     For debugging logs, run again after setting SLS_DEBUG env var.

  Stack Trace --------------------------------------------

ConfigError: Missing region in config
  at Request.VALIDATE_REGION (/home/nas/projects/atb-custom.ecommerce.customer/node_modules/aws-sdk/lib/event_listeners.js:81:45)
  at Request.callListeners (/home/nas/projects/atb-custom.ecommerce.customer/node_modules/aws-sdk/lib/sequential_executor.js:105:20)
  at callNextListener (/home/nas/projects/atb-custom.ecommerce.customer/node_modules/aws-sdk/lib/sequential_executor.js:95:12)
  at /home/nas/projects/atb-custom.ecommerce.customer/node_modules/aws-sdk/lib/event_listeners.js:75:9
  at finish (/home/nas/projects/atb-custom.ecommerce.customer/node_modules/aws-sdk/lib/config.js:308:7)
  at /home/nas/projects/atb-custom.ecommerce.customer/node_modules/aws-sdk/lib/config.js:324:9
  at SharedIniFileCredentials.get (/home/nas/projects/atb-custom.ecommerce.customer/node_modules/aws-sdk/lib/credentials.js:126:7)
  at getAsyncCredentials (/home/nas/projects/atb-custom.ecommerce.customer/node_modules/aws-sdk/lib/config.js:318:24)
  at Config.getCredentials (/home/nas/projects/atb-custom.ecommerce.customer/node_modules/aws-sdk/lib/config.js:338:9)
  at Request.VALIDATE_CREDENTIALS (/home/nas/projects/atb-custom.ecommerce.customer/node_modules/aws-sdk/lib/event_listeners.js:70:26)
  at Request.callListeners (/home/nas/projects/atb-custom.ecommerce.customer/node_modules/aws-sdk/lib/sequential_executor.js:101:18)
  at Request.emit (/home/nas/projects/atb-custom.ecommerce.customer/node_modules/aws-sdk/lib/sequential_executor.js:77:10)
  at Request.emit (/home/nas/projects/atb-custom.ecommerce.customer/node_modules/aws-sdk/lib/request.js:668:14)
  at Request.transition (/home/nas/projects/atb-custom.ecommerce.customer/node_modules/aws-sdk/lib/request.js:22:10)
  at AcceptorStateMachine.runTo (/home/nas/projects/atb-custom.ecommerce.customer/node_modules/aws-sdk/lib/state_machine.js:14:12)
  at Request.runTo (/home/nas/projects/atb-custom.ecommerce.customer/node_modules/aws-sdk/lib/request.js:394:15)
  at Request.send (/home/nas/projects/atb-custom.ecommerce.customer/node_modules/aws-sdk/lib/request.js:358:10)
  at [object Object].makeRequest (/home/nas/projects/atb-custom.ecommerce.customer/node_modules/aws-sdk/lib/service.js:193:27)
  at [object Object].svc.(anonymous function) [as getFunction] (/home/nas/projects/atb-custom.ecommerce.customer/node_modules/aws-sdk/lib/service.js:451:23)
  at Promise.post (/home/nas/projects/atb-custom.ecommerce.customer/node_modules/q/q.js:1161:36)
  at Promise.promise.promiseDispatch (/home/nas/projects/atb-custom.ecommerce.customer/node_modules/q/q.js:788:41)
  at /home/nas/projects/atb-custom.ecommerce.customer/node_modules/q/q.js:1391:14
  at runSingle (/home/nas/projects/atb-custom.ecommerce.customer/node_modules/q/q.js:137:13)
  at flush (/home/nas/projects/atb-custom.ecommerce.customer/node_modules/q/q.js:125:13)
  at nextTickCallbackWith0Args (node.js:419:9)
  at process._tickDomainCallback (node.js:389:13)

It's problem will be resolved after my changes.
@jthomerson Please take my pull request.

Coverage remained the same at 22.222% when pulling c8e553bb4911fedb4bf7d5c07f48b72b75276fa4 on anasinnyk-atb:master into ecdd1752ab1217cfc8ced3861b44e6190a953014 on silvermine:master.

Coverage remained the same at 22.222% when pulling c8e553bb4911fedb4bf7d5c07f48b72b75276fa4 on anasinnyk-atb:master into ecdd1752ab1217cfc8ced3861b44e6190a953014 on silvermine:master.

I can't accept this change because it would explicitly override the region with something that comes from a "defaults" section of the configuration in Serverless. Many people use different methods for configuring the region, and this would override theirs.
The SDK is complaining because it doesn't know what region to connect to for the API. You can give it a region either through your credentials configuration or through the AWS_REGION environment variable.


AL Debugger Watch

1. Describe the bug
Whenever a field name contains a space, the debugger watch always displays "Out of Scope".
2. To Reproduce
Start the debugger and add some fields to watch

5. Versions:

AL Language: 7.4.496506
Visual Studio Code: 1.59.0

From your screenshot, it looks like it results from the field needing quoted, e.g. containing a space or a period as in No., or etc.

Compare with #5639.

The Add to Watch is bugged, the out of scope is a red herring.
It should add Rec."No." but instead adds just No.

Duplicate of #5639


Bulma seems not working

@jkuri I have installed daterangepicker as you said but I have a problem loading sass files from app.sass, so I have added bulma with yarn but I'm having the same problem still.
I don't know if you can guide me in order to get all the css files working? this is how I see it right now. And the console is not showing me any error.
https://user-images.githubusercontent.com/3856494/28010739-26df88cc-6560-11e7-984f-69763544d246.png

It seems that everything is working now, I had to change the route from app.sass to bulma cause the package wasn't pointing to the right folder.
@import '../../node_modules/bulma/bulma.sass'


Feature request: null SOLE_AUTHENTICATION_SERVICE in CoInitializeSecurity

Motivation
I'm trying to build a WMI client.
Currently the rust API does not allow passing the value "-1" in the "cAuthSvc" parameter of the CoInitializeSecurity function, instead, an array is passed and rust uses the length of the array as the "cAuthSvc" parameter.
#[link(name = "windows")]
extern "system" {
    fn CoInitializeSecurity(psecdesc: *const super::super::Security::SECURITY_DESCRIPTOR, cauthsvc: i32, asauthsvc: *const SOLE_AUTHENTICATION_SERVICE, preserved1: *const ::core::ffi::c_void, dwauthnlevel: RPC_C_AUTHN_LEVEL, dwimplevel: RPC_C_IMP_LEVEL, pauthlist: *const ::core::ffi::c_void, dwcapabilities: EOLE_AUTHENTICATION_CAPABILITIES, preserved3: *const ::core::ffi::c_void) -> ::windows::core::HRESULT;
}
CoInitializeSecurity(::core::mem::transmute(psecdesc), asauthsvc.len() as _, ::core::mem::transmute(::windows::core::as_ptr_or_null(asauthsvc)), ::core::mem::transmute(preserved1), ::core::mem::transmute(dwauthnlevel), ::core::mem::transmute(dwimplevel), ::core::mem::transmute(pauthlist), ::core::mem::transmute(dwcapabilities), ::core::mem::transmute(preserved3)).ok()

Drawbacks
No response
Rationale and alternatives
If the original "cauthsvc" parameter cannot be added, then some facility should be provided to generate the array of SOLE services.
Additional context
No response

This is currently blocked on a metadata bug: https://github.com/microsoft/win32metadata/issues/837
Duplicate of #1610


Is there a way to run AI locally?

Description of the feature request:
Hey! Could you please tell me if there's a way to run AI processing locally on the device in order to avoid library making API calls to https://generativelanguage.googleapis.com/v1beta/models/gemini-1.5-flash-latest:generateContent ?
What problem are you trying to solve with this feature?
No response
Any other information you'd like to share?
No response

@ilya-kuznetsov-tabby, Thank you reporting this issue.
This repository is for issues related to Dart SDK client bugs or improvements and the client doesn't control the service's responses. For issues related to Gemini API, we would suggest you to use "Send Feedback" option in Gemini docs. Ref: Screenshot below. You can also post this issue on Discourse forum.


Upgrade react and react native packages

This pull request upgraded android and ios folders for compatibility due to this package was generating conflicts when I was trying to install it on the latest react-native.
"react": "17.0.2",
"react-native": "0.66.4"

This is the result

Hi @jonra1993, did you test on IOS too?

Hi @jonra1993, did you test on IOS too?

Hello @hungvu193 yes, I tested on a simulator running a local rasa server with ngrok. it is working correctly.

@jonra1993 perfect.

@jonra1993 thanks for approving the pull requests. I have a question related to licensing I see it is using GPL v3 is there any plan to change it to Apache or MIT as react-native-gifted-chat uses? I am willing to help you add improvements to this library as PR. Currently, I am working on a client project connecting Rasa with a react native app, but GPL3 is not permitted for our client due to this https://youtu.be/sQIVclmxvdQ .

@jonra1993 no problem, I will change it to MIT at next release, will be next few days, I'm busy on another project, but I will release ASAP.


Add document for KEP Kubernetes Metrics Overhaul

/milestone 1.14
/hold
/sig instrumentation
/cc @brancz

/hold cancel

@brancz @jimangel does this look good ?

I'm not sure user facing documentation should have instructions on how to add a new metric to Kubernetes. I was more thinking to document the metric changes happening as a whole as part of the metrics overhaul KEP.

@brancz I don't know the best place to record our KEP implementation in website.
@jimangel @zacharysarah : can you give some advices?

Yeah I'd like to hear some advice as well, I'm also perfectly happy with documenting it in the KEP itself.

@danielqsj @brancz this does appear to be a developer centric doc that would be more suitable as a markdown doc in a sig-instrumentation repo. I don't think it should live in the KEP, since they aren't really designed to be doc repos. Who is the intended audience here?

I think generally what was started in this PR is not really what I imagined. What we need is cluster administrator facing docs informing them about the upcoming changes in metrics, as they are done as part of the metrics overhaul KEP. I guess my question is whether any actionable thing people need to do is fine to be in the KEP itself or whether we need docs on kubernetes.io for that?

Agreed. I think a release note theme is probably the best fit.

Thanks @brancz @jimangel . As conclusion is the release note is enough. I will close this PR.
/close


[volume.fsck] hotfix apply purging and add option verifyNeedle #3860

What problem are we solving?
fix error: findExtraChunksInVolumeServers: purging volume 2823: delete fileId monitoring-thanos:2823,2a7a380095160caa00000000: volume 0 not found on fast-volume-1:8080
option verifyNeedle: It is necessary to be able to verify the integrity of the dat files so that all blobs are recoverable.
To fix a blob in time from a replica or from a backup
How are we solving the problem?
How is the PR tested?
Checks

[ ] I have added unit tests if possible.
[ ] I will add related wiki document changes and link to this PR after merging.

@chrislusf Do not release without merge this PR (purging broken)


测试

please give me a star, then I will consider it.

please give me a star, then I will consider it.

please give me a star, then I will consider it.

please give me a star, then I will consider it.

thank you for giving me a star, I will consider it

thank you for giving me a star, I will consider it


HighlightTextArea x-scroll hide the text

Please sorry for my issues, but this time I really can't figure out what's going wrong with HighlightTextArea. Basically when you setText or paste a long text (so that x scroll happens), all the text that is not initial visibile will be always hidden and not rendered anymore. But if you start typing something then it appears correctly. I've tried multiple workarounds (disable culling area, force a keyTyped event, invalidate, and any other public method exposed) but nothing seems to work.
This is a GIF to better understand the situation:

Again, I cannot reproduce it with Test Application.. I've copied exactly the same example but in my enviroment produce this bug.. If you could give me an hint of why this bug may happens will be very helpful. Thanks!

No idea honestly. Is this only related to HighlightTextArea? Try with ScrollableTextArea, VisTextArea, TextArea. It could be issue with your layout, ScrollableTextArea#createCompatibleScrollPane has some requirements listed in the docs. Try to create as small as possible public project to reproduce this, otherwise there's no way to debug it.

Sorry for delay, but I've finally figured out a way to reproduce the bug! You can use Test Application as well. The problem happens when styleName parameter is provided to HighlightTextArea.
If you create new HighlightTextArea("", "textArea") the bug happens, while with new HighlightTextArea("") the bug disappear. So, I've thought that the problem might be here:
https://github.com/kotcrab/vis-ui/blob/ffc696a8341cdbff046dc1f4d318fbe248bcb510/ui/src/main/java/com/kotcrab/vis/ui/widget/HighlightTextArea.java#L54-L65
I didn't understand what is softwrap, but it is set to false only in the first constructor, maybe should be set false also for the others.. please let me know what do you thing about.

Yes, this is it. As per comment in ScrollableTextArea:
 * Warning: By default this can only support vertical scrolling. Scrolling in X direction MUST be disabled. It is NOT possible
 * to use vertical scrolling without child class properly implementing {@link #getPrefWidth()} and disabling soft wraps.
 * Example of such class is {@link HighlightTextArea}.

I'll add it.

Thanks for figuring it out!


10.0.10941.1741 not supported

My laptop with windows system can't support 10.0.10941.1741, could some guy help me resolve this issue?
And how can I generate the right rdpwap.ini file after windows updated?
thanks so much for any help!

Duplicate of https://github.com/stascorp/rdpwrap/issues/1881


zoom and scroll page

Hello
Is it possible to ensure that the modelviewer background don't receive the scroll, only 3D model?
Because I have a scroll page and if my mouse is inside modelviewer div it zoom instead of scrolling on the page.
I want to keep the zoom functionality but aslo scroll to my page.
Or perhaps another solution?
Thanks

Can I assume you're using the latest, v1.3? Perhaps you want to set the touch-action attribute to 'none'? I'm not entirely sure what behavior you're after. When you say mouse zoom, at you talking about a mouse wheel? And do you really want both zooming and scrolling to happen at once? You can also set up zoom to be triggered by scroll directly.

Can I assume you're using the latest, v1.3?
yes
Perhaps you want to set the touch-action attribute to 'none'?
I don't see any effect, perhaps it's only for mobile
When you say mouse zoom, at you talking about a mouse wheel?
yes
And do you really want both zooming and scrolling to happen at once? You can also set up zoom to be triggered by scroll
Not at once, I want my mouse wheel zoom only if my mouse cursor is over my 3d model, but scroll my page if I'm out.
Currently my mouse wheel zoom also if my mouse cursor is over the model-viewer background, but like my model-viewer background is transparent, the user don't really know if he over the model-viewer canvas to zoom or over the page background to scroll.
you can see my test page here : https://data.strategia.io/modelviewertest/index.html
I think it need a line trace hit between 3d model and mouse cursor to detect if i'm over the 3d model or not, I don't know if model-viewer can do that.

Ah, thank you for the details, I understand now. We don't support hit-testing to determine what interactions do for a couple of reasons. First, it's expensive to hit test, so putting that in a mouse handler would destroy page responsiveness. Second, some models (like fences or screens) have such finely detailed geometry that a user could have a hard time putting their mouse on/off the model reliably. Perhaps a subtle background highlight when the user is hovering over the model-viewer element?

What would I have to do to disable model-viewer zoom with scroll wheel and let it scroll the page instead?

At the moment all we have is not including the camera-controls attribute, but then you lose rotation as well.


feat: add support for Byte in FluentNumberField

🙋 Feature Request
Please add support for the Byte type in FluentNumberField.
🤔 Expected Behavior
Should accecpt Byte as underlying value.
😯 Current Behavior
Currently throws an error The type 'System.Byte' is not a supported numeric type.
🔦 Context
You are already supporting Short, Int, Long, etc.
Adding Byte to the list should be trivial.
Since my program uses Bytes extensively, all the way to the database level, it would be a massive pain to have to create new cloned classes for everything (eg. with Byte replaced for Short) just to data bind to FluentNumberField.
PS! Haven't checked, but are unsigned types supported? ushort, uint, ulong?
Better add support for those as well if they aren't currently supported.
💻 Examples
<FluentNumberField Label="Max employees:" @bind-Value=this.Entity.MaxEmployees Min="1" Max="10" />

@code
{
    private SomeClass Entity { get; set; }

    public class SomeClass
    {
         public byte MaxEmployees { get; set; }
    }
}

We will consider this for the next version. Currently the NumberField is too broken and I would advise you not to use it.


Dropdown should either wrap text or expand width to match

Overview
Noticed this in our sandbox environment - if the container is just the width of the text, the dropdown container is too small.
https://puu.sh/wpFpb/55cc9de222.png

This can be fixed by adding some right padding on the dropdown. Will submit a fix


Prepare to publish

Changelog entry and update pubspec
Make some of the utils/methods private
Document all public classes and methods
Move and rename some stuff

@jamescrosswell Version 1.3.0, which contains your raw file work, is live: https://pub.dev/packages/wav


The “singular matrix” problem of capon beamformer

Hi,
When I was using the dsp.aoa_capon() function for angle of arrival estimation, I met the “singular matrix” problem raised by the np.linalg.inv() function. Does any body know how to solve or prevent this problem? How did the “singular matrix” problem happen? May I use dsp.aoa_bartlett() to replace dsp.aoa_capon()? Are the two beamforming functions compatible?

I think this is because of the zero values in the data. You can just skip the frames or go to a lower frame rate.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-29-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 4667

Questions ?
Please refer to the Backport tool documentation


Replace current password if password generation is used in edit mode

Introduction
First of all I want to thank you for your work. As I was taking a look into this tool, I stumbeled upon a behaviour which felt a little odd to me. I'm not sure if anyone else shares my opinion, that's why I hope to start a discussion here.
Topic to Discuss
If an existing password file is edited with the internal editor, the file content is displayed in the textbox below (named ExtraContent, if I have done my research right). This also includes the password in the first line. If a new password is generated in edit mode and afterwards the "changes" should be saved, then I would expect, that the generated password replaces the old one. Otherwise I would need to replace the old password either by typing it or by copy+paste. If copy+paste is performed, the new password will be cached without deletion. In my opinion, this behaviour could be avoided.
My Thoughts
Forcing a cache deletion after editing a password seems a bad idea in my opinion, because this would not be expected by a user. This could even interrupt the users workflow.
My first idea to solve this "issue" was to force a replacement when using password generation in edit mode. On second thought, this might lead to another problem, because a user could first generate a password, then edit the password by hand and expect that his last changes will be saved.
Another solution I thought about, was to use the "Add Password" window in edit mode as well. This way any odd behaviour regarding password changes could be avoided. The negative aspect here may be, that the look and feel of editing does not match previous expectations that well...
The third solution I came up with, was an additional button in the edit window. Clicking this button replaces the first line of the textbox with the generated password. Even if the user changes anything in the textbox afterwards, these changes will be saved.
What do you think is the intended behaviour here?
Should this be changed? If yes, what would be the best way to do it? (I'm sure that my list of options is not complete)
Thank you and kind regards

Thanks for thinking about this! This particular feature is something I've thought about as well, and I'm not quite sure how to deal with it. I didn't want it to automatically replace the password in an existing file, because some of the behaviour resulting from that may be a bit unexpected, as you mentioned.
The third solution you mentioned seems reasonable to me though. Especially when combined with some additional help features (like tooltips on features to explain more clearly what they mean), I think it will be reasonable to implement it like that.

Implemented in v1.14.


tests: Initial connect test and docs

Adds an extremely basic initial test to ensure that we are able to connect to a YubiKey.
The test is marked #[ignore] in the hope that we can eventually start adding tests which run in CI, e.g. against a mock card.
This also includes a fix for calculating the APDU size, since the ones we were sending originally were overly long.

Note that this nukes all of the original C source code tests, but these are present both in the source history and in the original project, so I think we'll be OK.


Lp 235 create page template make reachable ac1

JIRA link
https://companieshouse.atlassian.net/browse/LP-235
Change description
Added page template, the partnership name has a placeholder for now.
Added routing to be able to test, again with placeholders, the previous and next pages still need to be added.
Work checklist

[x] Tests added where applicable
[ ] UI changes look good on mobile
[ ] UI changes meet accessibility criteria

Merge instructions
We are committed to keeping commit history clean, consistent and linear.  A BREAKING CHANGE can be part of commits of any type,
types other than fix: and feat: are allowed, for example build:, chore:, ci:, docs:, style:, refactor:, perf:, test:, and others,
footers other than BREAKING CHANGE: <description> may be provided.

CI: No security warnings found

CI: No security warnings found

CI: No security warnings found

CI: No security warnings found

LGTM

CI: No security warnings found


add metadata fields for nydusify filesystem check

@wraymo , a new test job has been submitted. Please wait in patience.

@wraymo , The CI test is completed, please check result:

Test CaseTest Result

merge-target-branch:white_check_mark:SUCCESS

build-docker-image:white_check_mark:SUCCESS

compile-nydus:white_check_mark:SUCCESS

compile-ctr-remote:white_check_mark:SUCCESS

compile-nydus-snapshotter:white_check_mark:SUCCESS

start-nydus-snapshotter-config-containerd:white_check_mark:SUCCESS

run-container-with-nydus-image:white_check_mark:SUCCESS

Congratulations, your test job passed!

@wraymo , your pull request has been updated. A new test job will be submitted. Please wait in patience.

@wraymo , your test job has passed, and no need to test again.

@wraymo , your pull request has been updated. A new test job will be submitted. Please wait in patience.

@wraymo , The CI test is completed, please check result:

Test CaseTest Result

merge-target-branch:white_check_mark:SUCCESS

build-docker-image:white_check_mark:SUCCESS

compile-nydus:white_check_mark:SUCCESS

compile-ctr-remote:white_check_mark:SUCCESS

compile-nydus-snapshotter:white_check_mark:SUCCESS

start-nydus-snapshotter-config-containerd:white_check_mark:SUCCESS

run-container-with-nydus-image:white_check_mark:SUCCESS

Congratulations, your test job passed!

@wraymo , your pull request has been updated. A new test job will be submitted. Please wait in patience.

@wraymo , your test job has passed, and no need to test again.

@wraymo , the test job has been submitted. Please wait in patience.

@wraymo , your pull request has been updated. A new test job will be submitted. Please wait in patience.

@wraymo , the test job has been submitted. Please wait in patience.

@wraymo , The CI test is completed, please check result:

Test CaseTest Result

merge-target-branch:white_check_mark:SUCCESS

build-docker-image:white_check_mark:SUCCESS

compile-nydus:white_check_mark:SUCCESS

compile-ctr-remote:white_check_mark:SUCCESS

compile-nydus-snapshotter:x:FAIL

Sorry, your test job failed. Please get the details in the link.

@wraymo , your pull request has been updated. A new test job will be submitted. Please wait in patience.

@wraymo , the test job has been submitted. Please wait in patience.

@wraymo , The CI test is completed, please check result:

Test CaseTest Result

merge-target-branch:white_check_mark:SUCCESS

build-docker-image:white_check_mark:SUCCESS

compile-nydus:white_check_mark:SUCCESS

compile-ctr-remote:white_check_mark:SUCCESS

compile-nydus-snapshotter:white_check_mark:SUCCESS

start-nydus-snapshotter-config-containerd:white_check_mark:SUCCESS

run-container-with-nydus-image:white_check_mark:SUCCESS

Congratulations, your test job passed!


S2U-21 <IP_ADDRESS> Support for Safe Exam Browser - MASTER

Jira S2U-21: SEB Support
Developed by: @stetsche
This is a port from Sakai 22 to 24
Related PRs: (https://github.com/sakaiproject/sakai/pull/11562) (https://github.com/sakaiproject/sakai/pull/11640) (https://github.com/sakaiproject/sakai/pull/11780) (https://github.com/sakaiproject/sakai/pull/11795)
(https://github.com/sakaiproject/sakai/pull/11804) (https://github.com/sakaiproject/sakai/pull/11988) (https://github.com/sakaiproject/sakai/pull/11833) (https://github.com/sakaiproject/sakai/pull/12056) (https://github.com/sakaiproject/sakai/pull/12067)

@V100X Could you add the conversion scripts in a reference PR?

Thanks for this tremendous contribution @stetsche and @V100X


Feat/telemetry

Adds telemetry features to the logic module, enabling tracking of predicate call counts and execution durations. Primarily intended for statistical data collection and limited to the node.
Ex:
# HELP logic_vm_predicate logic_vm_predicate
# TYPE logic_vm_predicate counter
logic_vm_predicate{predicate="chain_id/1"} 6
logic_vm_predicate{predicate="op/3"} 51
 HELP logic_vm_predicate_chain_id_1 logic_vm_predicate_chain_id_1
# TYPE logic_vm_predicate_chain_id_1 summary
logic_vm_predicate_chain_id_1{quantile="0.5"} 0.004000000189989805
logic_vm_predicate_chain_id_1{quantile="0.9"} 0.004999999888241291
logic_vm_predicate_chain_id_1{quantile="0.99"} 0.004999999888241291
logic_vm_predicate_chain_id_1_sum 0.06899999966844916
logic_vm_predicate_chain_id_1_count 6
# HELP logic_vm_predicate_op_3 logic_vm_predicate_op_3
# TYPE logic_vm_predicate_op_3 summary
logic_vm_predicate_op_3{quantile="0.5"} 0.004999999888241291
logic_vm_predicate_op_3{quantile="0.9"} 0.01600000075995922
logic_vm_predicate_op_3{quantile="0.99"} 0.210999995470047
logic_vm_predicate_op_3_sum 0.674000000115484
logic_vm_predicate_op_3_count 51

Summary by CodeRabbit

New Features

Introduced telemetry tracking for predicate calls, including counters and duration measurements.
Added new utility for converting operands to string representation for better predicate handling.

Bug Fixes

Improved logic for checking registered predicates, streamlining permission checks.

Refactor

Simplified predicate handling logic by replacing the previous interface with direct string conversion.

@coderabbitai resolve


Use .debug_aranges

Some compilers only emit the full ranges in .debug_aranges,
leaving only low/high attributes on the CU, which may overlap
with other CUs.  We already have workarounds for this, but it's
better to use the ranges if we have them.

Needs https://github.com/gimli-rs/gimli/pull/539


fix duplicated in LHN when deleted members was invited

Details

The workspace 1:1 DM between members becomes duplicated in LHN when deleted members was invited to the workspace again
Fixed Issues

$ https://github.com/Expensify/App/issues/33921
PROPOSAL: https://github.com/Expensify/App/issues/33921#issuecomment-1876188351
Tests

Invite any members to the workspace
Open LHN
Navigate to settings and remove the workspace members that were added
Open to LHN
Navigate to settings and add the previously removed members to the workspace again
Open to LHN
Verify that: Announce, Admins and 1:1 DM conversations with each member should be displayed in LHN

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

Invite any members to the workspace
Open LHN
Navigate to settings and remove the workspace members that were added
Open to LHN
Navigate to settings and add the previously removed members to the workspace again
Open to LHN
Verify that: Announce, Admins and 1:1 DM conversations with each member should be displayed in LHN

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/129500732/177e8634-97c8-43d5-ab6d-1036834aac06

Android: mWeb Chrome

https://github.com/Expensify/App/assets/129500732/83e395b7-cee8-48ff-961a-8ad224c0fdcd

iOS: Native

https://github.com/Expensify/App/assets/129500732/7bedfa38-6fca-4d94-b556-eacbfe928bab

iOS: mWeb Safari

https://github.com/Expensify/App/assets/129500732/7e7edc5d-8ec2-46e9-bf29-3de124a6c6ac

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/129500732/5af32ced-75dd-42c8-a5d4-30db38e2989d

MacOS: Desktop

https://github.com/Expensify/App/assets/129500732/60605177-b0e8-448e-a4eb-473c2bb23a85

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to production by https://github.com/marcaaron in version: 1.4.26-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


bug/null_string_display

The name can become nil if the user logs in on a fresh install without signing up.  We are looking into adding a name screen on log in for that case, but this helps mitigate the bug. So display blank string instead of .

Looks good


Create new instance of client info rather than stomping on shared instance.

While reviewing a new client @tseaver noticed a bit that may need revising.
Quoting from https://github.com/GoogleCloudPlatform/google-cloud-python/pull/5665/files/12676aaf08dc795f2216f9441896cfae54edd382#diff-198e257d2c267a0bc3e3d2f3e77ec561
https://github.com/GoogleCloudPlatform/google-cloud-python/blob/master/dlp/google/cloud/dlp_v2/gapic/dlp_service_client.py#L173
        if client_info is None:
            client_info = (
                google.api_core.gapic_v1.client_info.DEFAULT_CLIENT_INFO)
        client_info.gapic_version = _GAPIC_LIBRARY_VERSION

This bit is problematic -- the DEFAULT_CLIENT_INFO instance is going to be scribbled on by every library generated this way, which means that each time an app instantiates a generated client, they all use the last-instantiated one's gapic_version.
Rather than reuse the instance, we should be constructing a new one here, e.g.:
        if client_info is None:  # create a new instance
            client_info = (
                google.api_core.gapic_v1.client_info.ClientInfo(
                    gapic_version=_GAPIC_LIBRARY_VERSION)
        else:  # update caller-supplied instance
            client_info.gapic_version = _GAPIC_LIBRARY_VERSION

@crwilcox @lukesneeringer this has been quiet for awhile - is it still relevant?

@jbolinger The generator is still emitting code which has this flaw (@crwilcox re-genned several libraries over the weekend, ant their clients all have it).

https://github.com/googleapis/gapic-generator/blob/085018f461968ab38f1cb85565a9198c15684458/src/main/resources/com/google/api/codegen/py/main.snip#L140
https://github.com/googleapis/gapic-generator/blob/3bcf41a4de3f55bea470f6e72386406685ba77e7/src/test/java/com/google/api/codegen/testdata/py/python_multiple_services.baseline#L964
https://github.com/googleapis/gapic-generator/blob/3bcf41a4de3f55bea470f6e72386406685ba77e7/src/test/java/com/google/api/codegen/testdata/py/python_no_path_templates.baseline#L907
https://github.com/googleapis/gapic-generator/blob/a05cf23a4844f6ec16833d545fd69009fb939d25/src/test/java/com/google/api/codegen/testdata/py/python_library.baseline#L1213


Moving tests from old test system to new test system

On my local machine, the last code_39 test is presently failing on node, but working in browser.  This would appear to be evidence that there is something that doesn't translate properly between the two of them, probably some difference between how the browser-specific and node-specific files (*_node.js) operate.  This could be extremely difficult to track down.
We might file a bug on that, comment it out for now, and carry on.

I have noted this under https://github.com/ericblade/quagga2/issues/191 and will be commenting that test out of the new test system until we can fix it


Edge 15.15063.0 / Windows 10 0.0.0

Are you requesting a feature or reporting a bug?
Bug
What is the current behavior?
1) AssertionError: expected 30 to deeply equal 29

      Browser: Edge 15.15063.0 / Windows 10 0.0.0

         16 |    const gridRowPage = new GridRowPage();
         17 |
         18 |    await t.navigateTo(gridColPage.url)
         19 |        .expect(gridColPage.colums.count).eql(12)
         20 |        .resizeWindow(500, 500)
       > 21 |        .expect(gridColPage.colums.nth(0).clientWidth).eql(29)
         22 |        .navigateTo(gridRowPage.url)
         23 |        .expect(gridRowPage.rows.count).eql(12)
         24 |        .resizeWindow(500, 500)
         25 |        .expect(gridRowPage.rows.clientHeight).eql(25);
         26 |});

If you perform a manual inspection, then the width of the element is 29

What is the expected behavior?
test passed
How would you reproduce the current behavior (if this is a bug)?
$ git clone https://github.com/GitScrum/slims.git && cd slims
$ npm i && npm t

This should be done on the platform Windows 10

Provide the test code and the tested page URL (if applicable)
Tested page URL: https://github.com/GitScrum/slims/blob/master/tests/e2e/index-test.js#L14-L26
Specify your

operating system: Windows 10 0.0.0
testcafe version: 0.15.0
node.js version: v8.0.0

Hi Ivan,
I've checked your scenario and it works properly on my side.
I've added a debug command before the assertion:
await t.navigateTo(gridColPage.url)
        .expect(gridColPage.colums.count).eql(12)
        .resizeWindow(500, 500)
        .debug()
        .expect(gridColPage.colums.nth(0).clientWidth).eql(29)

Here is a screenshot how does it look on my side:

As you can see TestCafe run is stopped on the debug command. window.innerWidth equals 500 as expected and the clientWidth of the column is 29. I think it can be related to your MS Edge rendering specific or some extensions behavior. Could you please perform the same steps as I did to see what's wrong on your side?

@AlexanderMoskovkin Hi, I think the problem is resizeWindow. I changed the value to 600 but the window did not change

Hello @GitScrum, I reproduced the problem with resizeWindow and Edge 15. It's related to the OS-specific native module: https://github.com/DevExpress/testcafe-browser-tools/issues/117. Need some to investigate and fix it. I will inform you when the fix will be available in a next alpha/release.

@AndreyBelym Hi, thanks for the feedback. And also I have problems with:
MacOS 10.12.5
Firefox DE 54.0b14
Chrome 61.0.3122
Safari 10.1.1

Hello @GitScrum, we discovered that some apps can prevent TestCafe from accessing browser windows. In this case, relogin without session restore might be helpful.


Add missing Figma URL to footer

The footer of your documentation appears to be missing the Figma URL.

Hi,
Thanks for flagging this to us. We have updated the Figma URL for the docs.
Thanks


ImportError: cannot import name 'get_pyodbc_attrs_before' from 'dbt.adapters.fabric.fabric_connection_manager'

Hi all,
I've been using Github actions to schedule my dbt run for the past few months with no issues. However, over the weekend it failed with the following error:
ImportError: cannot import name 'get_pyodbc_attrs_before' from 'dbt.adapters.fabric.fabric_connection_manager' (/opt/hostedtoolcache/Python/3.9.20/x64/lib/python3.9/site-packages/dbt/adapters/fabric/fabric_connection_manager.py)
Any ideas what's caused this, or how best to fix it?
Thanks,
Jason

Fabric pushed an update yesterday that changed that function name. Will try to fix today, but you can pin the version <1.8.8 as a temp fix.