Can't log in to spotify

So maybe I'm missing something here, but when I run the example program and it gives me a link to visit, I get to a log in screen, but when I try to click log in, nothing happens. I can click the log in through facebook link and this logs me in but when I paste it as the redirected link in spotipy, it raises an exception:
    raise SpotifyOauthError(response.reason)
spotipy.oauth2.SpotifyOauthError: Bad Request

Am I doing something wrong? I have my credentials set as environment variables and I'm using http://example.com/callback/ as my redirect uri

I found out that its actually logging me in, but not redirecting anywhere. If I put in a bad password it tells me such. but when I put my real password in and click log in, not a thing happens. If I open up the web player in another tab I'm logged in.

The same happens to me. Unlike you, if I open the web player in another tab I am not logged in. If I try to enter the redirect URI set for my application from https://developer.spotify.com/my-applications/, I get the same Bad Request. Any idea?

OK. I solved the problem, at least partially. I specified the redirect URI in line 13 of the example program:
token = util.prompt_for_user_token(username, scope, redirect_uri = 'https://www.google.com')
Theoretically, it was not necessary because I already did it when setting the environment variables. Anyway, now I can log in. Hooray. But don't count the chickens yet. When entering the URL (my original redirect URI plus a bunch of letters/numbers), I got another bad request, for a change:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/spotipy/util.py", line 86, in prompt_for_user_token
token_info = sp_oauth.get_access_token(code)
  File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/spotipy/oauth2.py", line 217, in get_access_token
    raise SpotifyOauthError(response.reason)
spotipy.oauth2.SpotifyOauthError: Bad Request

It seems that the origin of the problem is in the script 'oauth2.py' (line 217) within the Spotipy library. You can take a look at that script here. And you can do same with utils.py. Unfortunately, these scripts are beyond my grasp. Any clue? Thanks.

Solved it. In order to run the Authorization Code Flow example code provided in the Spotipy's documentation correctly, I specified the redirect URI in line 13 of the example script when calling util.prompt_for_user_token, even when I have done this previously when setting environment variables:
token = util.prompt_for_user_token(username, scope, redirect_uri = 'https://example.com/callback/')
Likewise, do not use https://www.google.com or similar web address as your redirect URI. Instead, try 'https://example.com/callback/' or 'http://localhost/' as suggested here. Do not forget that the redirected URL once you are logged in must have the word code included.
Cheers,
Antonio

I've tried what you said, but when I use any of the redirect URIs you suggest the webpage I am brought to has the following message: "INVALID_CLIENT: Invalid redirect URI"
Needless to say, when I past the redirected url in the terminal window I get the same traceback as before.

Hey @AlexEshoo, I don't know if you ever figured this out, but I just solved the same problem.
I found that you have to add your redirect URI that you either include in your bash profile or specify directly in the token prompt to your list of redirect URIs directly in the settings for your Spotify Dev App.

@nplevitt So I have specified it within my bash , Spotify Dev App, and within my python file. I still get the invalid error, is it due to the fact that I'm using 'https://example.com/callback/' as my redirect uri?


Added checkVowels code

Checks if a given string contains all vowels
Issue: https://github.com/jatinkumar027/Nourishing-Skills/issues/9
Signed-off-by: Kunal Garg<EMAIL_ADDRESS>

I think by mistake you have added the .ipynb file. Please add the python file with .py extension

I added ipynb file as I did it in jupyter which is a good IDE for python beginners. It can be opened in VS Code. I can change it to .py file if you still want that.

I request you to add simple python code here. You can take the reference of the sample code already present in repository

Updated as required. Please check

Great. Merging


feat(XEC price): Adding endpoint to retrieve XEC price

:tada: This PR is included in version 1.10.0 :tada:
Your semantic-release bot :package::rocket:


Link to contributor ladder template

Add links to our new contributor ladder template and update any existing links that pointed to the old draft (which has been removed).

/lgtm
/approve.


Get orders by incomplete asset pair

/v2/orders/XCP/PEPECASH [works]
/v2/orders/XCP [doesn't work]

with /v2/orders/XCP
we should get orders with pair XCP/<asset>

This is just an alias, but it's worth doing IMO.


Broken Link

I posted this issue before but it was closed without resolution.  At the bottom of the page, under Related Links, there is a link called "Online Version."  I assume this link is supposed to point to the O365 version of Add-ADPermission but it doesn't--it just reloads this same page.
The response to my initial post was:
@Canis-Lupis, that link is used in command line help, i.e., 'Get-Help Add-AdPermission -Online` to take you to the topic. So, it's by design.
This is incorrect as it doesn't relate to the link (i.e. web link) I am referring to.  I don't know what you were looking at but it wasn't the "Online Version" link in the Related Links section of this page.

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

ID: 01a54a6b-1ef9-2809-c90f-a56defdba194
Version Independent ID: 8d822e69-212a-9c8d-d6db-4f7ba1e7707d
Content: Add-ADPermission (exchange)
Content Source: exchange/exchange-ps/exchange/active-directory/Add-ADPermission.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@officedocsbot assign @yogkumgit

@Canis-Lupis, the Related Links section in the Add-ADPermission topic looks like this:
RELATED LINKS
Online Version
That link points back to the Add-ADPermission topic itself, which is used by Get-Help Add-ADPermission -Online from the command line. All Exchange-related cmdlets have this link in the Related Links section, and 99% or more have only this type of circular link in the Related Links section.

Thanks for the explanation but this is really confusing for the reader.  I still don't fully understand it but I doubt MS is going to change anything given that 99% of the Related Links do this, as you mentioned.

From: Chris Davis<EMAIL_ADDRESS>Sent: Tuesday, September 3, 2019 12:34 PM
To: MicrosoftDocs/office-docs-powershell<EMAIL_ADDRESS>Cc: David Tessmann<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/office-docs-powershell] Broken Link (#3926)
@Canis-Lupishttps://github.com/Canis-Lupis, the Related Links section in the Add-ADPermission topic looks like this:
RELATED LINKS
Online Versionhttps://technet.microsoft.com/library/bef9f3db-84f6-4a40-81cb-c9cb9b9ee201.aspx
That link points back to the Add-ADPermission topic itself, which is used by Get-Help Add-ADPermission -Online from the command line. All Exchange-related cmdlets have this link in the Related Links section, and 99% or more have only this type of circular link in the Related Links section.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/office-docs-powershell/issues/3926?email_source=notifications&email_token=AMUD2TBEE2E45WCPGOGXQNTQH2N2RA5CNFSM4IS7O722YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5Y7A2A#issuecomment-527560808, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMUD2TCJOVG5CGVCZEXZXALQH2N2RANCNFSM4IS7O72Q.

@chrisda  Thank you very much for the contribution and digging deep into it. @Canis-Lupis
If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Please keep contributing with your suggestions to improve the documentation.

OK. I think I understand the confusion now.
Add-ADPermission is an EXCHANGE cmdlet. It's only available in the Exchange Management Shell, or if you use remote PowerShell to connect to an Exchange server.
I agree that it's confusing since the name of the cmdlet gives no indication that it be belongs to Exchange; it looks like a Windows Server or Active Directory cmdlet.
The Exchange product was so early in the PowerShell game that best practices like cmdlet naming conventions hadn't been established yet. Products that were later to PowerShell like SharePoint or Skype for Business Server follow the later-developed naming conventions for their cmdlets (*-SP* for SharePoint, *-SPO* for SharePoint Online, *-CS* (Communication Server) for Skype for Business, etc.).
Most Exchange cmdlets are easily identified because of their association with Exchange/email features (Get-Mailbox, New-TransportRule, etc.). But there are some Exchange cmdlets like this one that are hard to identify with Exchange just by their name (Get-User, Get-Contact, Get-Group, etc.).


Fatal error has been detected by the Java Runtime Environment

Question
is this issue already known?
--
A fatal error has been detected by the Java Runtime Environment:
SIGSEGV (0xb) at pc=0x00007f8e1fffb67c, pid=7, tid=12
JRE version: OpenJDK Runtime Environment Temurin-17.0.6+10 (17.0.6+10) (build 17.0.6+10)
Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.6+10 (17.0.6+10, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, shenandoah gc, linux-amd64)
Problematic frame:
V  [libjvm.so+0xd3a67c]  ShenandoahMark::count_liveness(unsigned short*, oopDesc*) [clone .isra.0]+0x28c
Core dump will be written. Default location: /usr/local/epa/core.7
An error report file with more information is saved as:
/usr/local/epa/hs_err_pid7.log
If you would like to submit a bug report, please visit:
https://github.com/adoptium/adoptium-support/issues
Aborted (core dumped)

Hi,
I have a similar error. See please the log below :
A fatal error has been detected by the Java Runtime Environment:

SIGSEGV (0xb) at pc=0x00007ff3e5937c78, pid=4140, tid=4141

JRE version: OpenJDK Runtime Environment Temurin-17.0.9+9 (17.0.9+9) (build 17.0.9+9)
Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.9+9 (17.0.9+9, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
Problematic frame:
C  [ld-linux-x86-64.so.2+0xcc78]

Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -- %E" (or dumping to /home/ps3/core.4140)
---------------  T H R E A D  ---------------
Current thread (0x00007ff3dc028eb0):  JavaThread "main" [_thread_in_native, id=4141, stack(0x00007ff3e5a19000,0x00007ff3e5b1a000)]
Stack: [0x00007ff3e5a19000,0x00007ff3e5b1a000],  sp=0x00007ff3e5b15560,  free space=1009k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [ld-linux-x86-64.so.2+0xcc78]
C  [ld-linux-x86-64.so.2+0x1525d]

You both need to upgrade to the latest Java 17.0.11 from adoptium.net

Hi thank you for your response.
I'm searching on your site adoptium.net but i didn't find the latest Java 17.0.11. The latest find is [17.0.10+7].
Could you please give me the direct link.
Thanks in adavance

@karianna there are just some beta versions! is there any release for 17.0.11 ?!
https://github.com/adoptium/temurin17-binaries/releases?q=17.0.11&expanded=true

Sorry I meant 17.0.10


I'm facing issues with CSS after I run build.

Describe the bug:
CSS Works fine in local but it ruins the css after i run build to run via the nginx in production.
I see the same css issues if i run with python server on my local computer.  So there's some issue in the way build is being created.
(Write your answer here.)
Did you try recovering your dependencies?
What is that ?

(Write your answer here.)
Which terms did you search for in User Guide?

(Write your answer here if relevant.)
Environment
Mac : high sierra .

(paste the output of the command here.)
Steps to reproduce

(Write your steps here:)

Expected behavior

(Write what you thought would happen.)
Actual behavior

(Write what happened. Please add screenshots!)
Reproducible demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

So im importing a css file inside the component like this :   import './Item.css';   Is it okay ?  whats the better option ?

I removed this file and still it fucks up when rendering from the server.


questions about quantification

Have you tried using int8? I noticed you mentioned float16. What is the reason behind your choice of float16? Also, regarding the command you mentioned: ct2-transformers-converter --model openai/whisper-large-v2 --output_dir faster-whisper-large-v2 --copy_files tokenizer.json --quantization float16, the converted model using float16 seems to perform worse than yours. I hope you could provide some assistance with this.

@phineas-pta speed，gpu，I am using some short audio clips.By the way, I would like to ask if you have any good suggestions for quantization to improve the inference speed. I would be extremely grateful if you could provide me with some answers.

consider provide a reproducible example of audio, show how much slower u get

if you have any good suggestions for quantization

u should ask in discussion, issue is to report bug


Failing to resolve dependencies that my custom server is returning ERROR 403 (Unauthorized)

I'm using coursier "1.0.0-RC12", I have added credentials for our own server and I'm getting the following error:
error Caught java.io.IOException: Server returned HTTP response code: 403 for URL: https://<server>/artifactory/libs-release/org/scalactic/scalactic_2.11/3.0.1/scalactic_2.11-3.0.1.jar (Server returned HTTP response code: 403 for URL: https://<server>/artifactory/libs-release/org/scalactic/scalactic_2.11/3.0.1/scalactic_2.11-3.0.1.jar)

My understanding is that coursier is thinking that our server can provide this library (scalactic) but we are not authorized to retrieve it and stopped looking for it in another server.
Maybe there is something that I'm missing.

I've done some research, for some reason coursier is getting that most artifacts should be retrieved from my custom server (here: https://github.com/coursier/coursier/blob/master/sbt-coursier/src/main/scala/coursier/Tasks.scala#L964), I thought that it tried to retrieve an artifact from different servers until its found or there are no more servers.

@AlexITC Once coursier finds the metadata (POMs for Maven repos), it "sticks" to that repo for JARs. So it doesn't try the other repos for now… This might change in the future, but that's how it works now.

I've hit this problem a couple of times already. Sometimes the solution is deleting the pom from cache ...

Closing for now. coursier only tries to get jars from the same repo it originally got metadata.


Updated pupil to use HTTPS

Thank you for the contribution. It was merged directly as 9ed5e109808c83e6937274644f1228114c43f6e9 to keep commit history cleaner. Your contribution is still credited to you.


Problem installing sonnet on a GPU machine

I have a CUDA supported CentOS 7 GPU machine with TF version 1.1.0 and tried to install sonnet
When I run
./configure
I get
ERROR: /home/xbbl35h/code/sonnet/tensorflow/WORKSPACE:3:1: //external:io_bazel_rules_closure: no such attribute 'urls' in 'http_archive' rule. ERROR: /home/xbbl35h/code/sonnet/tensorflow/WORKSPACE:3:1: //external:io_bazel_rules_closure: missing value for mandatory attribute 'url' in 'http_archive' rule. ERROR: com.google.devtools.build.lib.packages.BuildFileContainsErrorsException: error loading package '': Encountered error while reading extension file 'closure/defs.bzl': no such package '@io_bazel_rules_closure//closure': error loading package 'external': Could not load //external package.
I saw that someone had posted a change and I have the WORKSPACE file changed to
http_file(
  name = "weblas_weblas_js",
  url = "file:///local_path/weblas.js",
)

I suspect it is something simple

Hi there.
What version of bazel do you have?
bazel version will tell you that.

It looks like the latest version fixed this. Closing.


Add Code of Conduct preview endpoint support ✨

This PR adds support for the Code of Conduct GitHub API (in preview period) documented here: https://developer.github.com/v3/codes_of_conduct/
Tests and api docs generated. README updated for preview headers. npm requests that I commit the package-lock.json file, but please let me know if that is not the case.
cc/ @bkeepers @jbjonesjr

Awesome. Didn't know these new endpoints were a thing. 👍
The test suite is still not working. How can we ship these changes with confidence? Are you folks smoke-testing this stuff?

The test suite is still not working. How can we ship these changes with confidence? Are you folks smoke-testing this stuff?

I verified all the end points work by replacing the values in the testing suite with real ones and verifying those work. Since then I've been replacing the package in my node_modules with the code from my branch and had success hitting these endpoints.
I agree that this kind of testing doesn't give me great confidence in my changes. I'd be happy to update once we get some new testing infrastructure set up! :)

Thanks!

Hey @hiimbex!
@gr2m and I have started working on a fork in the octokit org. I tried to pull in the changes from this PR but things have already diverged enough to generate some conflicts.
Can you tell me which files you modified manually to make this change?

Yes! would it be easier for me to just open a PR there?
If not I edited the README to reflect the preview header and routes.json. Everything else was generated, but I think the index files are necessary while the test is ❓

would it be easier for me to just open a PR there?

Yes please 🙏


Heda Settings: System: New auto naming and format settings and help text need translated

Steps to duplicate:
*Assign the User's language to something other than English- I did Spanish.

Go to Heda Settings
Click the system tab.
For both the view and edit view the new settings/help text need translated.
See below screenshot of what is happening currently.

**lurch:add

Tracking W-022926

This has been fixed. Closing GH Issue.


Kepware v6  - BadNodeIdUnknown

Can Monitor a tag from a Kepware v5 server fine using the h-opc-cli.
Trying to do the same from a Kepware v6 server, the "Sub.ApplyChanges(), UaClient.Monitor method" raises a BadSubscriptionIdInvalidServiceResultException.

I'm reading from Kepware V6 right now. Need more info

Kepware v5, run h-opc-cli with connection params supplied as command line arguments, read [node] and value returned.
Exactly the same, but specifying a Kepware v6 server, read [node], "Invalid response from the server (Response Status : BadNodeIdUnknown)
Sorry, misleading information given. Exception is raised by UaClient.CheckReturnvalue
     private void CheckReturnValue(StatusCode status)     {       if (!StatusCode.IsGood(status))         **throw new OpcException(string.Format("Invalid response from the server. (Response Status: {0})",** status), status);     }
The status is BadNodeIdUnknown.

The Kepware v6 is running in a virtualised environment if this is relevant?

Is this a simulation server?

No, it's using Allen Bradley drivers with actual PLCs connected. It is running in Demo Mode though...

Let's continue this here: https://gitter.im/H-Opc/H-Opc-CLI

Actually, this is a false alarm - our client had assured us the Kepware server was actually out of its demonstration mode and activated (they couldn't see a countdown in the caption). It wasn't activated and the demo period had expired. Looks like Kepware 6 doesn't maintain the countdown in its caption...
Sorry, but thanks for your help!

No problem. Glad you got it fixed


Release 126.0.0

Explanation
This is the release candidate for 126.0.0. It exclusively releases the PermissionController to fix a type issue.

@SocketSecurity ignore<EMAIL_ADDRESS>New author looks fine.


add redmine api key to the correct headers

Thank you for your commit.
I will update software version to 0.7.4 today.


Hugging Face Down

Looks like the hugging face space is down. Are there plans to get it running again?

the space should be running again, sorry about that


Save Issue (BCS)

Pastor Sam and a couple others in BCS are facing an issue of save. When they edit text and click Save, possibly hit the button a couple of times which results in the error message shown below. The file does not get saved and text is lost.
From the call we saw these steps:

On a slow connection
edit text
Do NOT tab out of the field
Click the grey save button
Click the now enabled save button 2x
Repeat the process in quick succession

Vipin to share the Inspect element details to check for network issues. Not sure if issue can be recreated.

@ancientTexts-net can you look into this so we can define it better?

@klappy @ancientTexts-net
Is this log helpful? Tried it on a slow 3G Connection

I tested all the way down to 500kbps download, 5kbps upload, 20 seconds latency. Saving a tN change took ~4 minutes, but it was successful.


Ctrl+Arrow Key and Ctrl+Shift Selection no longer work on Windows

[x] I am on the latest Hyper.app version
[x] I have searched the issues of this repo and believe that this is not a duplicate

OS version and name: Windows 10 x64 1709
Hyper.app version: 2.0.0

Issue

Using Ctrl + Arrow Keys on windows used to control movement as expected. Now it outputs characters. Combining this with shift should select the text but now does nothing.

ctrl+shift+arrows should work, a Hyper keybinding might be intercepting it?

I don't know if this helps, but Ctrl+Left inserts b and Ctrl+Right inserts f.

@Tyriar, those commands (at least on my machine) control tab selection. I think @sbatten is referring to navigating through input text

@Xapphire13 yeah, my statement stands; Hyper is intercepting it so it's not being interpreted by the shell.

Same problem here.
Using Hyper 2.0.0 and Windows 10 1709.
If i use the key combination "ctrl+left arrow" then a "b" is written and if i use the combination "ctrl+right arrow" a "f" is written.
This behavior also occurs when I execute the function via the menu (Edit > Move to > Prevoius/Next Word).
Adjusting the keyboard shortcuts didn't help either:
"editor:movePreviousWord": "ctrl+left",
"editor:moveNextWord": "ctrl+right",

or;
"editor:movePreviousWord": "alt+left",
"editor:moveNextWord": "alt+right",

For me, using Hyper 2.0.0 (stable), and no plugins, on Windows 10 Professional (x64) Version 1803 (build 17134.228), the key combinations [ALT]+[Left Arrow], [ALT]+[Right Arrow] move backwards and forwards through the entered text. I would expect [CTRL]+[Left Arrow] and [CTRL]+[Right Arrow] to do this, but as others have mentioned above, [CTRL]+[Left Arrow] writes out a b and [CTRL]+[Right Arrow] writes out an f.

Experiencing the same issue on the most recent version for Windows. Ctrl <- outputs b and Ctrl -> outputs f. I'm guessing b stands for back and f for forward, and at some point not getting interpreted before it hits the shell.

Played around some more with this and have some more information for someone who might be able to look deeper into the issue. The pull request linked to in my previous comment attempts to "fix" the issue by breaking this function call (putting you into the catch block for the try-catch):
https://github.com/zeit/hyper/blob/6451ba7f85fe5b88268cf4e57da8a1a13f6046b7/app/config/import.js#L29
You can get the same effect by either:

Simply commenting out that line that breaks
Replace contents of app/keymaps/win32.json with an empty object {}
Replacing instances of ctrl with alt in that same file

Additionally in win32.json I tried playing around with a couple other commands and I don't see "editor:deletePreviousWord": "ctrl+backspace" or "editor:deleteNextWord": "ctrl+del" working at all, regardless if ctrl is replaced with alt. Windows keymaps are not reliable at all right now unfortunately.

Which shell do you use?

@chabou For me the work was done in the default Windows shell

I am also experiencing this when using Hyper with Cmder (following the instructions here)

So, here's something weird...
As we know, there are issues with Windows keymaps.
But, when I start a Windows CMD shell in Hyper (with this in the config: shell: '', shellArgs: ['--login']), and then SSH into a Linux box, then the CTRL+Left and CTRL+Right, etc. combinations work correctly. Exit the SSH session, drop back to the Windown CMD shell, and CTRL+Left and CTRL+Right are once again borked.
Well, it seemed weird to me. Maybe it's totally explainable?

I've had a quick look and I think this is what's happening:
In app/keymaps/win32.json, editor:movePreviousWord is mapped to ctrl+left. This means that whenever  ctrl+left is pressed, Hyper does not send the ctrl+left to the shell - instead it interprets it as the command editor:movePreviousWord. The way the editor:movePreviousWord is implemented is it sends \x1bb to the shell:
https://github.com/zeit/hyper/blob/0d82f983eb6b932ffd66563bd6e8153bf03e7398/app/commands.js#L77-L79
https://github.com/zeit/hyper/blob/0d82f983eb6b932ffd66563bd6e8153bf03e7398/lib/index.js#L70-L72
The problem is that PowerShell and CMD do not interpret this as "move to previous word" (but Bash does, hence why it works on Mac/Linux but not on Windows). If you use WSL Bash as your shell, this does work correctly and moves the cursor to the previous word.
Previous comments mentioned that replacing the windows key bindings JSON with {} fixes the issue. This is because it causes Hyper to stop recognising ctrl+left as a command, and instead passes it through directly to the shell - so PowerShell/CMD receives a ctrl+left and moves the cursor to the previous word as expected.
By removing the editor:movePreviousWord command I was able to see what the actual data for ctrl+left is: '\x1b\x5b\x31\x3b\x35\x44'. So changing:
store_.dispatch(sessionActions.sendSessionData(null, '\x1bb'));

to;
store_.dispatch(sessionActions.sendSessionData(null, '\x1b\x5b\x31\x3b\x35\x44'));

makes this work for PowerShell and CMD.
I think perhaps what is needed is some extra configuration files similar to the keymaps json that determines which control characters should be sent for each command, depending on the shell being used.
E.g. for bash:
{
  "editor:movePreviousWord": "\x1bb"
}

for PowerShell/CMD:
{
  "editor:movePreviousWord": "\x1b\x5b\x31\x3b\x35\x44"
}

However, an easy temporary fix for CMD/PowerShell users is to override the key bindings for the commands that don't work to ''. Edit -> Preferences - set keymaps to:
keymaps: {
  'editor:movePreviousWord': '',
  ...
},

This stops Hyper interpreting them as commands and instead sends them directly to the shell.

thanks @SamuelFisher savior!!!!

Adding this  code:
keymaps: {
    'editor:movePreviousWord': '',
    'editor:moveNextWord': '',
  },

fixed for me.

Note:
keymaps: {
    'editor:movePreviousWord': '',
    'editor:moveNextWord': '',
  },

Does not work on Hyper 3 Canary 8. I've filed https://github.com/zeit/hyper/issues/3484 as that issue seems to have a different cause.

Confirmed above works in Hyper 3 too.
note: Remove any default keymaps using Ctrl+arrows too
    // "tab:next": ["ctrl+right"],
    // "tab:prev": ["ctrl+left"],


[Linear] Menu bar icon stuck

Extension
https://www.raycast.com/linear/linear
Raycast Version
v1.81.2
macOS Version
14.6.1
Description
The icon doesn't go away even after viewing the notification.

The icons keep accumulating

Steps To Reproduce

Receive a notification
View it
The icon stays

Current Behaviour
No response
Expected Behaviour
No response

Thank you for reporting the issue. A recent Raycast release introduced a regression causing this bug in some menu bar commands. One of our engineers is working on it!

With the fixes in menu bar with recent version 1.82.0, this issue is fixed. Please reopen if that is not the case.

@raycastbot close this issue


Set Log2 Padded Height based on Table Height

Currently, it is set in consensus_program_prover_job.rs / prove_worker only taking into account the cycle count. In the general case, other table heights might exceed this number.

In case you have an AET at hand, you can use aet.padded_height(). Without the AET it is probably difficult to get the padded height.


Sorting by region

Due to there being a site that has everything dumped to it and being able to grab an Enctitlekey.bin file I would like to request a way to sort by region by clicking on region.

I'll work on it. Its tough doing stuff like this due to C# just sucking in general but it's doable.

Possible with fixed search bar in be9a76b3bd18a9c2dab57569bc94ab543a98a149


drivers: can: s32_canxl: ensure memcpy does not go over the frame size

Hi, fixing a warning that popped up with the switch to picolibc, guess that check was not there before for whatever reasons.
What do you think? Not in love with this solution myself to be honest, but adding a bunch of #pragma GCC diagnostic ignored "-Warray-bounds" around this does not sound great either.

Adds an extra validation to a memcpy from the HAL data structure to the
Zephyr can frame one. This is mainly to handle the build warning:
zephyr/drivers/can/can_nxp_s32_canxl.c:757:9: warning:
'__builtin___memcpy_chk' forming offset [16, 71] is out of the bounds
[0, 16] of object 'frame' with type 'struct can_frame' [-Warray-bounds]
757 | memcpy(frame->data, msg_data.data, can_dlc_to_bytes(frame->dlc));
where the compiler detects that frame->data is 8 bytes long but
can_dlc_to_bytes could return more than that.
Can be reproduced with:
west build -p -b s32z270dc2_rtu1_r52
-T samples/net/sockets/can/sample.net.sockets.can.one_socket

We can't do that, sorry. The utility function needs to do the correct calculation regardless if CAN-FD is enabled or not.

Fair enough, how about this instead? Just added a MIN against the size of the buffer. This one I'm actually not completely ashamed of.

This would be another solution the compiler is happy with:
static inline uint8_t can_dlc_to_bytes(uint8_t dlc)
{
	static const uint8_t dlc_table[] = {0, 1, 2, 3, 4, 5, 6, 7, 8, 12,
					    16, 20, 24, 32, 48, 64};

	return dlc_table[dlc > 0xF ? 16 : dlc];
}

This would be another solution the compiler is happy with:
static inline uint8_t can_dlc_to_bytes(uint8_t dlc)
{
	static const uint8_t dlc_table[] = {0, 1, 2, 3, 4, 5, 6, 7, 8, 12,
					    16, 20, 24, 32, 48, 64};

	return dlc_table[dlc > 0xF ? 16 : dlc];
}

Happy with either, I think @martinjaeger one is better though cause it would fix it on potentially any other driver doing a similar pattern. Can you open a PR with that? Happy to close this one for yours.

Happy with either, I think @martinjaeger one is better though cause it would fix it on potentially any other driver doing a similar pattern. Can you open a PR with that? Happy to close this one for yours.

Yes, it would be a more universal fix and maybe would save one additional comparison. Just take my suggestion and use it if you like. I don't mind.

Re-redone using @martinjaeger suggestion.
Compilers are magic.

At least the fact that I did not tag this as "Trivial" makes me feel a bit better.

@fabiobaltieri Please open an issue for this so the bug fix can be backported.

@fabiobaltieri Please open an issue for this so the bug fix can be backported.

Can we use https://github.com/zephyrproject-rtos/zephyr/issues/62612? It covers all three picolibc error I've found in the run.

Actually if you folks have any idea of what to do with the [2] in there... :-)

Got an idea. Will open a PR, but need to double-check first.

@henrikbrixandersen can we merge this? Trying to get this in before the next weekly run (tomorrow)

@henrikbrixandersen can we merge this? Trying to get this in before the next weekly run (tomorrow)

Yes, but please open a separate issue for this and link it, as it also fixes the bug in the implementation. A separate issue would help in backporting the fix.

@henrikbrixandersen can we merge this? Trying to get this in before the next weekly run (tomorrow)

Yes, but please open a separate issue for this and link it, as it also fixes the bug in the implementation. A separate issue would help in backporting the fix.

Cool with that: https://github.com/zephyrproject-rtos/zephyr/issues/62701


Increase max declarativenetrequest rule limits

Chromium defines some properties that limit the max number of static and dynamic rules(ets) when using DeclarativeNetRequest:

MAX_NUMBER_OF_ENABLED_STATIC_RULESETS
MAX_NUMBER_OF_DYNAMIC_AND_SESSION_RULES
MAX_NUMBER_OF_REGEX_RULES
MAX_NUMBER_OF_STATIC_RULESETS

These values should be user-configurable, or at least increased.

why

One thing that hexavalent expressed interest in was replacing addons like uBO with v3's DNR. Increasing these limits will allow more rulesets, and more rules might be necessary given that some advanced uBO rule syntax will need to be broken up into several smaller DNR filters.

eh sure then but this needs more investigation


(SMT) comment contract implementation

Adds comment contract, ability to set up post/comment reward pool.
Notes:

Primary key functionality added to facilitate quick lookups. Compounded Indexes added to provide efficient sorting given fixed parameters (e.g. reward pool ID in this case)
Trending score computation and curve computations for post exponents other than 1 or 2, and curation exponents other than 0.5 or 1 use double precision float computation.
Downvotes and upvotes use different pools, unlike hive's implementation where downvote power can bleed into the upvote power. It also uses the older voting power system (without mana) that requires powered up stake to charge before use.

Mostly looks good, I didn't check the math carefully will assume you've tested all that thoroughly, just have some questions about some of the DB queries (see comments). Also, you've got some lint errors to fix.
How has performance been in your test environment? Is your node able to keep up with blocks OK, processing all the votes & comments, without lagging behind at all?

Performance has been good, but I need to add more pools to my test to confirm.


Feature calander

Add an event using google calander .
Eg set up a meeting with Evan at 9pm tomorrow
Indent name calander
use sys.any,sys.date and sys.time

closed via #68


Click on 'OK' in production does not do anything

Hey! Click on 'OK' button works as expected locally but cannot be clicked on production in Chrome and Firefox. I am using Rails 5.1.0 without turbolinks

That's weird. Do you get any error in the console? I assume the assets are precompiled as they should be...

Yes, they are. I found a workaround by putting cookiesEu.init() in the end of application.js

Have you tried to put the requires in the order you really require them?

This is working for me


[Internal] Query: Fixes optimalPageSize logic for OFFSET LIMIT in ORDER BY queries

Description
This PR fixes the logic in CosmosQueryExecutionContextFactory where we determine optimal page size for ORDER BY queries that have an OFFSET/LIMIT clause.  Previously, the logic was only being applied to TOP and not OFFSET/LIMIT, resulting in suboptimal query execution (unnecessarily fetching more results than are likely to be needed by the query)
Consider an example query:
SELECT c.pk FROM c ORDER BY c.pk OFFSET 0 LIMIT 500
Without this change, we use a page size of 500 against each target range.  With this change, we will calculate an optimal page size based on the limit on the # of documents being requested (factoring in the number of target ranges) using the same formula that we already use for TOP queries:
                    // All partitions should initially fetch about 1/nth of the top value.
                    long pageSizeWithTop = (long)Math.Min(
                        Math.Ceiling(top / (double)targetRanges.Count) * CosmosQueryExecutionContextFactory.PageSizeFactorForTop,
                        top);

                    optimalPageSize = Math.Min(pageSizeWithTop, optimalPageSize);

Type of change

[] Bug fix (non-breaking change which fixes an issue)

Thanks for making this fix!


Repo sync for protected CLA branch

The pull request is created from main638025087408641572sync_temp to main to fix git push error for protected CLA branch

Learn Build status updates of commit f225954:
:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Orbi, HyperHDR, PiHole

I am having an issue when I use HyperHDR (RPi4, 4K Capture Card, Denon AVR) where it will interfere with my Orbi Router and knock the wifi offline. I know it is HyperHDR as I just did a new install on the same pi as my Pihole and the internet went down. I do not know where to start troubleshooting but the logs are attached.
Happy to share anything else but wanted to open this up to see what is happening.
HyperHDR Logs.txt
Additionally setting LED hardware instance to disabled restores wifi.

Hi
Unfortunately can't help with network related problems especially when network is especially pihole domain. Maybe you set some ports in pihole configurations that are used by HyperHDR on default: 8090 or 8092? BTW also your grabber doesn't work judging from  your logs but symptoms are typical for some video capture devices when no HDMI sources are available.

Hi Unfortunately can't help with network related problems especially when network is pihole domain. Maybe you set some ports in pihole configurations that are used by HyperHDR on default: 8090 or 8092? BTW also your grabber doesn't work judging from your logs but symptoms are typical for some video capture devices when no HDMI sources are available.

I have the grabber working but it only works on automatic and I can no longer set the dimensions on beta.

New logs_220106_210156.txt

The logs are cut off i don't like it. Anyway I see that when you connect the HDMI source the grabbed started to work: just as I wrote. Still can't see any problem with the network or the grabber in logs you provided.

Ok. Thanks. I have other issues however. Should I open a new issue or can I post here?

you can post it here and i can take a look.

I uploaded new logs after a restart (but have no run actual video).

Where is the option to calibrate RGB GRB? I no longer see it.
I have an issue where whites and sandy browns when solid on the frame show was red. I have messed with settings to see what is causing this but haven't found the issue.
For my Grabber  I have to select automatic as the two entries when selected do not work. This is since I upgraded to v<IP_ADDRESS> as well as v<IP_ADDRESS> Beta. Additionally, when I pick automatic I can no longer change the device resolution (which has helped in the past with issues. (1280 x 720).
I am using ws281x with GPIO pin 12 (GPIO 18). I am told using ground will help but does it matter if the ground is pin 5 or 14? does it matter if I use the left most or right most input on the led for ground? The middle goes to pin 12.

Fresh Start-up Logs.txt
HyperHDR-<IP_ADDRESS>beta-Backup-2022-01-08.txt

Hi

you can find it in one of sub-menus in the advanced tab

hard to say, the problem could be in the grabber itself, its configuration (hardware brightness/hue/saturation settings were changed), wronf calibration in the image processing tab etc..does the problem with colors appear in the live video window? probably it's best to start from fresh settings deleting old settings and restart the system.

that's what I see in the logs and it's not HyperHDR issue, probably other software use it or it's some kind of driver/device malfunction, again your grabber doesn't work at all:
2022-01-08T20:38:17.536Z [V4L2:AUTO] Found capture device: /dev/video14
2022-01-08T20:38:17.536Z [V4L2:AUTO] Found capture device: /dev/video15
2022-01-08T20:38:18.395Z [V4L2:AUTO] Throws error nr: Cannot open '/dev/video0' error code 16, Device or resource busy

driving ws281x led strip is not longer officially supported. Anyway in the logs the LED device is working. If there is not reaction from the LED strip there could be multiple reason: fried GPIO section, some kind of problem in the electrical installation, missing 3.3V to 5V level shifter,

It doesnt matter which ground pin you use but pin 5 is NOT the ground.

And just to be clear: ground from Rpi should be connected to 'minus' of the power supply that provides power for LED strip (absolutely NOT it's ground). Example: https://github.com/awawa-dev/HyperHDR/discussions/182#discussioncomment-1920409

It doesnt matter which ground pin you use but pin 5 is NOT the ground.

Sorry Pin 6 - https://cdn.sparkfun.com/assets/learn_tutorials/1/5/9/5/GPIO.png


Fingerprint background should be red (while error)

Fingerprint background should be red, also alert message is missing.
https://zpl.io/boZK6Zg

We should fasten a warning that the fingerprint is not recognized after 5 attempts.

Also, the fingerprint icon should be omitted below, and the text "Restore wallet or create new one" should be raised above,as in this screenshot.

Language of the wallet-English.
Local-Russian.

checked


Update workflow, setup workflow-test

Can trigger workflow from branch workflow-test
Make default multi-arch to single amd64
Remove specific ci targets; make shortlive builds more straightforward
Disambiguate makefile env vs workflow env
Remove unused targets
Remove now unused shortlived dockerfile

Testing worflows:

on PR: https://github.com/netobserv/netobserv-ebpf-agent/actions/runs/5065773179/jobs/9094733798
on merge: https://github.com/netobserv/netobserv-ebpf-agent/actions/runs/5065658695/jobs/9094488753
on release: https://github.com/netobserv/netobserv-ebpf-agent/actions/runs/5065711652/jobs/9094604107

They seem all good.
(Note: there's still an issue that all builds seem actually amd64 despite tagged as aarch/ppc - that's independent from this PR, still needs to be fixed)

/approve


test-branch/execute-job/wrong-commit-sha-on-pr/1986ca2d-e6ec-4ee8-9203-7e093b16ca33

PR for testing b9c91b56344dddbbf95de154a2a142a5066ac983

/canonical/self-hosted-runners/run-workflows 931ad21dd9ace68aaa0a7d341e94de96ad93fa6b


Angle bracket components error when resolving

With Ember Canary from a couple days ago (2.0.0-canary+f59d716e) something like this works.
test("curly bracket component", function(assert) {
  this.render(hbs`
    {{now-playing}}
  `);
});

Something like this fails.
test("angle bracket component", function(assert) {
  this.render(hbs`
    <now-playing />
  `);
});

The ember resolver throws an error because parsedName.fullNameWithoutType is undefined. The object for parsedName in the resolver looks pretty weird.

There are a lot of pieces in play here: new angle bracket syntax, new component integration tests, and ember-cli-htmlbars-inline-precompile. Hopefully I can find the right home for this bug.

This bug is not specific to ember-test-helpers. Closing in favor of https://github.com/ember-cli/ember-resolver/issues/101.


Bind SHA256/SHA1 Update/Finalize API

Issue #, if available:
Description of changes:

Binds support for SHA256/SHA1 update/finalize API

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Could we also include adding update() and finalize() to MD5 hashing?


Write a TypeScript program to convert hours to days

Description
Write a TypeScript program to convert hours to days
1 day = 24 hours
Input  : 120
Output : 5

How to contribute

Save the solution in program/ConvertHoursToDays.ts file
Add ConvertHoursToDays.ts file in convert-hours-to-days folder

I would like to work on this issue. Can you please assign to me?

@Frey0-0
Please, type !assign

!assign

I also had a request could you please add the label "hacktoberfest" to this issue. @victoriacheng15 @harshraj8843

I also had a request could you please add the label "hacktoberfest" to this issue. @victoriacheng15 @harshraj8843

The hacktoberfest will be added after your PR gets merge

I have made a PR against this issue.


Allow optional custom onFinish handler for Readable constructor.

Handle the issue raised in #490 in a disciplined way (by punting to the user). We simply allow an extra argument when wrapping a Readable that handles the onFinish logic for us..

I would like to suggest to take this one step further. Especially considering how common this issue is. Can't we simply check for  instanceof http.IncomingMessage and automatically apply onFinished?

That would cause the browserify build to pull in the http package, which I don't want to do, as it bumps up the size of our minified JS from 58.21 kB to 102.59 kB in exchange for just a bit of convenience.

@vqvu: I see. Isn't there other ways to check for http.IncomingMessage? e.g. if (stream.socket && stream.httpVersion).

That's certainly possible, but I think adding special handling for IncomingMessage is out of scope for the library.
Agreed that this is something of a gotcha. I'm happy to add something to the docs about this though (even though that's not as foolproof). I mention IncomingMessage specifically in the new docs for the stream constructor, and I'm open to suggestions for documentation improvements to make these kinds of issues more visible.
P.S. I'll leave this issue open for a few days so the other contributors can weight in if they so choose. Then I'll merge it and cut a release for you.

@vqvu: Could you merge into 3.0.0 branch? That is what I'm currently using.

Yeah, I can do that this weekend. I just tried and it's a bit complicated.


Better graphical distinction between native navigation.navigate and react-navigation

Description
I would like to propose that the page related to React Native navigation have a better distinction between usage of native navigation.navigate and react-navigation library.
What is the problem?
The issue is that currently the whole page for React Navigation (navigation.md) explains that one can use the react-navigation library and only at the very end and briefly does it state about the native navigation.navigate option. Is this intentional? Is the react-navigate a best practice and the navigation.navigate just a lesser option? Based on the documentation I think that both are just options for a person to choose from.
How can we address it?
If a bolded header was added after the sentence 'You can set options such as the screen title for each screen in the options...' titled 'Navigation.navigate usage' (for example) this will show that both options are valid. Basically have two section of the page which both have Usage.
Why is it important?
This will show that both navigation.navigate and react-navigation are viable options.
Who needs this?
Anyone learning how to do navigation in their apps can use and leverage both options according to their needs.
When should this happen (use version numbers if needed)?
Whenever. This is just an addition to the docs so no code will broken.

Nope, looks like it's just not important. Close it.


Support Arabic

Subject of the feature
Support Arabic language beside Chinese and English.
Problem
Not enough i18n for the admin panel.
Expected behaviour
Should support choosing arabic as a language for the admin panel. With RTL directions.
Alternatives
Me creating a repo based on this that is Arabic by default (or Arabic only).

document-i18n maybe help you better.


sample mongo db property loader

Hi,
I created a loader that pulls properties from mongodb.
Wasn't sure if you'd like to include it in the owner-extras module.
Thanks,
Dan

No test case has been provided. I won't merge any code that comes with no unit tests proving the code works.

Thanks.  Lots of great feedback.  Will take a look and resubmit.


Update to support latest level

Fixes some problems with missing { valueEncoding: 'binary' } in calls to db.get(). Without them, we get strings back which makes msgpack very unhappy.
Updated tests using latest level instead of levelup + memdown.
Closes https://github.com/moscajs/aedes-persistence-level/issues/21

Squash when happy.

Not running github actions on PRs?

Not running github actions on PRs?

Github bug? Cannot see nothing on actions tab :confused:

Oh totally missed that :fearful: You have to place github workflow in .github/workflows/ folder

@ralphtheninja I have made a pr to fix that #25

Let's wait for #25 and #26 to land then pull master and once ready this can be merged too

Oh totally missed that fearful You have to place github workflow in .github/workflows/ folder

Sorry. I knew this, but screwed up anyway :)

@mcollina last ping request (for today) :)

@mcollina please add me as a collaborator of this in npm and/or move the package under the moscajs org in order to be able to publish a new major release
https://www.npmjs.com/package/aedes-persistence-level


Apply changes from running gofmt

What this PR does / why we need it:
This PR just applies changes resulting from running gofmt.
These changes were included in another branch I'm working on
but I thought it would be better to separate them into their own PR.
Release note:
None

Looks good to me; going to rerun tests though bc they failed. However, it was a great chance to actually hit that new debug logic. Still isn't perfect but we can see some more detail than we did before:
https://travis-ci.org/heptio/sonobuoy/builds/547752201?utm_source=github_status&utm_medium=notification
I can see the plugin is marked as complete on the status, the logs did get into the tarball, but not the junit.
I'll fixup that printing logic to pass so we can see the contents of the pod logs/test run.

Codecov Report

Merging #758 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #758   +/-   ##
=======================================
  Coverage   42.59%   42.59%
=======================================
  Files          70       70
  Lines        4029     4029
=======================================
  Hits         1716     1716
  Misses       2208     2208
  Partials      105      105

Impacted Files
Coverage Δ

cmd/sonobuoy/app/worker.go
10% <ø> (ø)
:arrow_up:

cmd/sonobuoy/app/gen.go
51.93% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6c522c8...988a5f7. Read the comment docs.


Simple as a package

Current environment.yml is the required dependencies/ conda environment for astrodbkit2, not simple. Do we want to add simple as a requirement to that environment or are we expecting people to operate in the cloned simple directory; i.e. in the same location as simple/schema.py and simple.db?

Astrodbkit2 is meant to work with lots of databases, not just SIMPLE. So Astrodbkit2 is a dependency of SIMPLE, but not the other way around.
Also, SIMPLE is at it's most fundamental, a collection of text (.json) files, not python code, so it's not quite right to "package" it. However, we might want to consider offering a binary version of the database as an easy to use, one click download thing which one could open with SQLite Browser, for example.


Add support for current() to refer to primary instance

currently being merged into javarosa by ODK from Commcare

done

ODK's implementation has a huge bug: https://groups.google.com/forum/#!topic/opendatakit-developers/nN8HTA5pUIM


Could you explain why are you using onViewCreated() life-cycle callback for injectDependencies() and ButterKnife.inject(this, view)?

Mostly because I use retaining Fragments.
Therefore, Fragment.onCreate() is only called the very first time. If for example you do dependency injection in Fragment.onCreate() and for instance access Fragement.getActivity() in your dagger module, you will run into memory leaks after screen orientation changes, because the injected components still may reference to the "old" activity (before screen orientation changes) and no new ones will be injected as Fragment.onCreate() will not be called again after screen orientation changes for retaining Fragments.
So one could discuss why not  doing all that in Fragment.onCreateView() ? Well, this is just a personal preference. You could also do it there, but Fragment.onViewCreated() feels more obvious to me and just inflate the xml layout in Fragment.onCreateView(). Again, that is just a personal preference...

Makes sense for me now. Thanks!


RUM-1330 Make sure we use try-locks in our NDK signal catcher

What does this PR do?
We recently had some reported issues in the flutter sdk regarding some ANRs caused by our signal catcher. Basically what was happening is that our code inside the signal catcher was trying to acquire a mutex lock which was already acquired by another thread (we could not really reproduce this). We chose to go with the safest mechanism here in order to avoid any other issues and use try locks instead of simple locks.
https://github.com/DataDog/dd-sdk-flutter/issues/487
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #1665 (e21c2a6) into develop (a5d678d) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop    #1665      +/-   ##
===========================================
- Coverage    83.73%   83.72%   -0.01%
===========================================
  Files          459      459
  Lines        15778    15778
  Branches      2354     2354
===========================================
- Hits         13211    13209       -2
- Misses        1938     1939       +1
- Partials       629      630       +1

see 16 files with indirect coverage changes

@xgouchet cannot reply on those comments for some reason so I will reply here, I've read the docs before adding this logic and actually we do not want to do anything in case we cannot acquire the lock, we just do not write the error log as there is no other action that we can take in that case. We could not find out who's acquiring that lock in the tests we performed (me and @fuzzybinary) and we do not want to block the process in the signal catcher in this case.

@mariusc83 in that case, then maybe add a comment explaining that 👍


There's no way to send messages to buses without coupling to implementation

The current implementation of WorkBench, deemed our service locator, does not contains a instance of IMessageBrokerWrapper.
Users are directly instantiating MessageBroker, just like this example (not included in this repo):

As one can see, the MessageBus is instantiated directly
I don't believe I need to elaborate. We need to address this as quickly as possible.

I'm marking this as a bug - this leads to very poor code. I also call it priority.


When branching, locales get new id's

Issue
I have a phraseapp.yml file that looks like this:
phraseapp:
...
  file_format: xml
  push:
    sources:
      - file: "./app/src/main/res/values/strings.xml"
        params:
          file_format: xml
          locale_id: 88df8852c829d975470f97feb607c8e8
  pull:
    targets:
      - file: "./app/src/main/res/values/strings.xml"
        params:
          locale_id: 88df8852c829d975470f97feb607c8e8
      - file: "./app/src/main/res/values-<locale_code>/strings.xml"

If I write phraseapp push --branch test , it will fail since the locale_ids will be different than that of the original branch. This does not seem to me as intended behavior, I have already specified the branch onto which I want to push, so why should I regenerate my .yml file for each branch?
I will fallback to the plain-text version ("en" in this case), but I'd guess this is a bug

Hi, this sounds indeed not like the intended behavior. I will check what is causing this and get back to you

I had a closer look and currently locale ids do not work as you've described above. For now the workaround with a locale code or locale name is required. I will keep you updated when there is any news

Sounds good, I fallback at using the locale name as you said. Looking forward to the fix 👍 Let me know if there is anything else I can assist with


Provide ability to manually specify expected types instead of annotated

I would like to use normal annotations in my project, while taking advantage of runtime checks with type-enforced.
Unfortunately, it has some false positive detection. Examples are: #29, #31.
I wanted the #26 to be implemented for these cases as a workaround.  But I now thought that it will not be either a good solution, because for disabled methods I will loose the advantage of checks.
Let's maybe introduce a way to override normal expected cases? I.e., to say type-enforced that when it sees some type, defined in the override_recognition dict, it should instead check against  the value for such key.
For example, I can have such config file:
override_recognition = {
    "Callable": type(lambda x: x)
    "TextIO": StringIO | TextIOWrapper
    "Developer": WithSubclasses(Developer)
}

This way I could easily disable/enable type-enforcer when needed, without editing the type hints (because when disabling, I need to remove WithSubclasses hack). I am using my own decorator over your type_enforced, called @conditional_type_enforced, with the approach taken from here.
If this is done, I could get rid of ugly type hints like this: -> list[Module | Union[*WithSubclasses(ModuleSet)]] and just use them like normal -> list[Module | ModuleSet]

This is an interesting suggestion. I think this might be achievable and make sense as part of a larger type_enforced construct to enable/disable it. Let me think about some of the larger implications around this and try some code variations. Also keep in mind that I need to keep backwards compatibility.

In 1.4.0: Callable support was added as was support for an enabled in Enforcer. This is still outstanding. This requires more time and thought.

Closing this issue.


Enhanced Lock Request Handling with TTL Consideration

TTL Consideration: Updated the lock request logic to consider the TTL (Time-To-Live) attribute when determining lock availability. Previously, TTL was ignored during lock requests, relying solely on DynamoDB's eventual purge, which can occur at any time, typically within a few days of expiration. Now, the lock request process checks the TTL to ensure that locks are not granted if the TTL has not yet expired.
Testing Enhancements: Added comprehensive tests to verify TTL expiration behavior and ensure locks are correctly released after TTL expiry. This includes simulating process crashes and verifying lock reacquisition.
Documentation Update: Updated README.md to reflect changes in TTL handling, clarifying that TTL is automatically managed and no manual configuration is needed for the TTL attribute.
Code Refactoring: Refactored code to improve readability and maintainability, including better logging and error handling.
Added go test wrapper script (run-tests.sh) for easier local testing

sorry, premature - opened against wrong target repo


IDA Pro plugin doesn't work when opening a subsequent idb

When using the IDA Pro plugin, close the workspace and open another sample, re-run the plugin. The results are inconsistent or empty.

I wonder if it has to do with the global state for the cache here:


Question: Accessing Current DbContext in Extension

Hi,
Sorry, not an issue, but a question: is there any way by which we can access the current context in an extension (IDbContextOptionsExtension)? There is only one method, ApplyServices, which takes a IServiceCollection. I tried building the IServiceProvider and asking for either DbContext or ICurrentDbContext, but no luck. Is this possible at all?
Thanks!
RP

@rjperes What is it that you need the context for? IDbContextOptionsExtension has a single responsibility (add services to the internal service collection) that is intended to be used before the context is initialized, so even if the context was available it would likely not be possible to use it for much.

Hi, Arthur! Imagine, for example, that you want to change the model at runtime.

@rjperes You can set the model in OnConfiguring or AddDbContext using the DbContextOptionsBuilder.


immediate render() after cancel()

Configuration:

Web browser and its version: Google Chrome 64, FireFox 58
Operating system and its version: Win7
PDF.js version: 2.0.334
Is a browser extension: No

Steps to reproduce the problem:
<!DOCTYPE html>
<html>
<head>
    <script type="text/javascript" src="//mozilla.github.io/pdf.js/build/pdf.js"></script>
</head>
<body>
    <canvas id="canvas" style="width:50em"></canvas>
    <script type="text/javascript">

var canvasContext = document.getElementById('canvas').getContext('2d');

PDFJS.getDocument('//cdn.mozilla.net/pdfjs/tracemonkey.pdf')
.then(function(pdf) {

    return pdf.getPage(1);
})
.then(function(page) {

    var renderTask = null;

    function renderPage() {

        if ( renderTask !== null ) {

            renderTask.cancel();
            return;
        }

        var viewport = page.getViewport(1, 0);

        renderTask = page.render({
            canvasContext: canvasContext,
            viewport: viewport,
        });

        renderTask.then(function () {

            renderTask = null;
        })
        .catch(function(err) {

            renderTask = null;
            if ( err.name === 'RenderingCancelledException' ) {

                renderPage();
                return;
            }

            console.log('Page render error', err);
        });
    }

    renderPage();
    renderPage();

})

    </script>
</body>
</html>

What went wrong?
The following error appear when the second renderPage() is called:
Cannot use the same canvas during multiple render() operations. Use different canvas or ensure previous operations were cancelled or completed.
In InternalRenderTask_cancel() function, canvasInRendering.delete(this._canvas) is called before RenderingCancelledException is send, then in initializeGraphics(),  canvasInRendering.has(this._canvas) should be false ??

As asked for in both https://github.com/mozilla/pdf.js/blob/master/.github/ISSUE_TEMPLATE.md and https://github.com/mozilla/pdf.js/blob/master/.github/CONTRIBUTING.md, can you please provide access to a complete (and runnable) example rather than just a code snippets?

Sorry, here is the runnable example: https://jsfiddle.net/b6wbh8q2/
I asynchronously wait for the end of the cancel operation using the render() promise rejection:
 .catch(function(err) {
            renderTask = null;
            if ( err.name === 'RenderingCancelledException' ) {
                renderPage();
                ...

Any updates on this?

Any updates here?

any update on this?


Sample scene empty almost

Sample scene has nothing really in it at all. Nothing runs, it has a pink block and a camera...

same bro
did you resolve it?

Nope 💀
Sent from my iPhone
On Oct 18, 2023, at 10:27 AM, Octavio Guerrero @.***> wrote:

same bro
did you resolve it?
—
Reply to this email directly, view it on GitHubhttps://github.com/PokemonUnity/PokemonUnity/issues/134#issuecomment-1768586469, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYX3CAKFNQSS7NCYEKJMHETX77RN5AVCNFSM6AAAAAA526V7SGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRYGU4DMNBWHE.
You are receiving this because you authored the thread.Message ID: @.***>


JSG Completion: update ActorState to use jsg::JsValue

The new jsg::JsValue and jsg::JsRef<...> are replacements for v8::Local<...> and jsg::V8Ref<...> ... this starts the transition over to using the new abstractions, starting with ActorState.

This feels like an improvement!

Awesome. That's definitely the hope!


Firefox: Using space to set a node in walkthrough triggers undo and JS errors

Weird things are happening when I try to use space for placing a node in the walkthrough (in either of the steps; Areas, Lines, Buildings). After a couple of presses it seems to trigger undo, and something like the below is thrown in the console for each (the number following 'n-' is decremented for each).
22:19:53.254 Error: entity n-9 not found 1 iD.js:38565:19
	entity http://preview.ideditor.com/master/iD.js:38565:19
	addChildVertices http://preview.ideditor.com/master/iD.js:49050:42
	siblingAndChildVertices/< http://preview.ideditor.com/master/iD.js:49073:17
	forEach self-hosted:251:13
	siblingAndChildVertices http://preview.ideditor.com/master/iD.js:49065:9
	drawVertices http://preview.ideditor.com/master/iD.js:49183:24
	selection_call http://preview.ideditor.com/master/iD.js:20572:3
	drawVector http://preview.ideditor.com/master/iD.js:55137:9
	redraw http://preview.ideditor.com/master/iD.js:55269:13
	immediateRedraw http://preview.ideditor.com/master/iD.js:55285:9
	call http://preview.ideditor.com/master/iD.js:20053:61
	change http://preview.ideditor.com/master/iD.js:71406:9
	_perform http://preview.ideditor.com/master/iD.js:71376:16
	perform http://preview.ideditor.com/master/iD.js:71468:24
	withDebouncedSave/< http://preview.ideditor.com/master/iD.js:72821:26
	behaviorDrawWay/drawWay.addNode http://preview.ideditor.com/master/iD.js:50456:9
	modeDrawArea/mode.enter/behavior.addNode http://preview.ideditor.com/master/iD.js:51577:17
	call http://preview.ideditor.com/master/iD.js:20053:61
	click http://preview.ideditor.com/master/iD.js:49609:13
	space http://preview.ideditor.com/master/iD.js:49638:9
	testBindings http://preview.ideditor.com/master/iD.js:39581:17
	bubble http://preview.ideditor.com/master/iD.js:39595:9
	contextListener/< http://preview.ideditor.com/master/iD.js:20196:7

This is on;
$ firefox -v
Mozilla Firefox 53.0

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.2 LTS
Release:	16.04
Codename:	xenial

Thanks!  will investigate...


Wrong scope for resolving variables when passing arguments to SSViewer#process

Affected Version
up to date Silverstripe, framework version 4.12.3
Description
In some circumstances passing arguments SSViewer#process results in inconsistent behaviour when resolving variables.
Steps to Reproduce

use SilverStripe\View\ArrayData;
use SilverStripe\View\SSViewer;

$viewer = SSViewer::fromString('
    \$Name: {$Name}

    loop \$Page

    <% loop $Page %>
        Page:\$Name: {$Name}

        Page:\$Name: {$Name}

    <% end_loop %>

    direct address page…

    \$Page.Name: {$Page.Name}

    loop \$Page…

    <% loop $Page %>
        Page:\$Name: {$Name}

        \$Top.Something: {$Top.Something}

        Page:\$Name: {$Name}

    <% end_loop %>

');
echo '
';
var_dump($viewer->process(new ArrayData([
    'Something' => 'asd',
    'Page' => new ArrayData([
        'Name' => 'page'
    ])
]), [
    'Name' => 'top',
]));

Results in:
    $Name: top

    loop $Page

        Page:$Name: page

        Page:$Name: page

    direct address page…

    $Page.Name: top  <<-- unexpected

    loop $Page…

        Page:$Name: page

        $Top.Something: asd  <<-- note this call

        Page:$Name: top  <<-- unexpected

Note: it does not happen, when customizing the ArrayData beeing rendered and not passing the customization as argument to process:
echo '
';
var_dump($viewer->process((new ArrayData([
    'Something' => 'asd',
    'Page' => new ArrayData([
        'Name' => 'page'
    ])
]))->customise([
    'Name' => 'top',
])));

Does the same happen when you rename Page to anything else, e.g. MyPage? I think for Page there's a method somewhere that could be affecting this. If it breaks in the same way with a different name then we can look into it.

Thanks for your fast response, yes this is independent of the variable/field names:
$viewer = SSViewer::fromString('
    \$Xasias: {$Xasias}

    loop \$Auwfb

    <% loop $Auwfb %>
        Auwfb:\$Xasias: {$Xasias}

        Auwfb:\$Xasias: {$Xasias}

    <% end_loop %>

    direct address Auwfb…

    \$Auwfb.Xasias: {$Auwfb.Xasias}

    loop \$Auwfb…

    <% loop $Auwfb %>
        Auwfb:\$Xasias: {$Xasias}

        \$Top.Sidjobf: {$Top.Sidjobf}

        Auwfb:\$Xasias: {$Xasias}

    <% end_loop %>

');
echo '
';
var_dump($viewer->process(new ArrayData([
    'Sidjobf' => 'asd',
    'Auwfb' => new ArrayData([
        'Xasias' => 'sub'
    ])
]), [
    'Xasias' => 'top',
]));

    $Xasias: top

    loop $Auwfb

        Auwfb:$Xasias: sub

        Auwfb:$Xasias: sub

    direct address Auwfb…

    $Auwfb.Xasias: top

    loop $Auwfb…

        Auwfb:$Xasias: sub

        $Top.Sidjobf: asd

        Auwfb:$Xasias: top


Remove jcenter and add mavenCentral for Android repositories

Remove jcenter android repo due to its shutdown
https://blog.gradle.org/jcenter-shutdown
https://github.com/flutter/flutter/issues/96633

thanks @dolpheen, I merged your code and created a release 2.0.1 containing it (cc @jWinterDay, @sla-000)


FSDP, AMP, and Accelerate together

Hi, I'm wondering how I should be thinking of the mixed precision policies of these three packages together. My plugin is below. It works, but I don't think we're doing things right with the mixed_precision_policy.
In particular, we're setting bf16 in the FSDP pluging, we'also setting --mixed_precision bf16 in the accelerate command, and we're setting self.model = model.to(torch.bfloat16) in our train.py.
I suspect that the last one is incorrect because it means that we'll lose out on the f32 precision. Is that right? Thanks!
FullyShardedDataParallelPlugin(
        activation_checkpointing=True,
        auto_wrap_policy=functools.partial(...),
        sharding_strategy=ShardingStrategy.FULL_SHARD,  # We can probably use a different strategy.
        backward_prefetch=BackwardPrefetch.BACKWARD_PRE,
        mixed_precision_policy=MixedPrecision(  # Doubt we need this.
            param_dtype=bfloat16,
            reduce_dtype=bfloat16,
            buffer_dtype=bfloat16,
        ),
        state_dict_type=StateDictType.SHARDED_STATE_DICT,
        cpu_offload=CPUOffload(offload_params=False),
        forward_prefetch=True,
        sync_module_states=True,
        use_orig_params=True,
    )

Yes that is correct. You should let accelerate/the FSDP plugin handle everything unless you want "pure" bf16 training (which is not what you want here)

Thanks! How should I think about explicit casts in the huggingface repo then? For example, these in modeling_gemma:
https://github.com/huggingface/transformers/blob/1bd604d11c405dfb8b78bda4062d88fc75c17de0/src/transformers/models/gemma/modeling_gemma.py#L62
https://github.com/huggingface/transformers/blob/main/src/transformers/models/gemma/modeling_gemma.py#L1087

Upcasts are generally fine, as they are just no-ops. Since everything is done under an autocast manager also (with how it all works), new tensors will be done in half/whatever precision just the original model weights won't be (notice how those were all done in the forward(), which happens under autocast)


AttributeError: 'Model' object has no attribute 'internal_input_shapes'

I am using Python 3.6 and install keras_adversarial with the master branch, it seems that Model has no attribute 'internal_input_shapes' BUT '_internal_input_shapes'. Also Model has no attribute 'internal_output_shapes' either.
Traceback (most recent call last):
File "example_gan.py", line 118, in
main()
File "example_gan.py", line 114, in main
latent_dim=latent_dim)
File "example_gan.py", line 71, in example_gan
loss=loss)
File "/Users/leo/Applications/anaconda3/lib/python3.6/site-packages/keras_adversarial-0.0.3-py3.6.egg/keras_adversarial/adversarial_model.py", line 91, in adversarial_compile
AttributeError: 'Model' object has no attribute 'internal_input_shapes'

I also have the same problems

I'm stuck in the same situation. Any update?

same with 2.1.4 only 2.1.2 works

This appears to have happened because of a change in Keras, internal_input_shapes and internal_output_shapes were changed to be private variables in the keras/engine/topology.py file, reference this commit
As far as a fix goes, I think keras_adversarial just needs to be updated to reflect the latest version.

my keras version was 2.1.6 and i was getting the same error.... downgrading solved the issue

do you have any suggestions about how to use the keras-adversarial examples without downgrading the keras, i.e. with newer versions?

with newer keras versions try K.int_shape(model.inputs[0])

with newer keras versions try K.int_shape(model.inputs[0])

Where to use this?


AAD 2.2 Automate validation of settings to notify administrator when high risk users are detected

Azure AD Secure Configuration Baseline Item 2.2, policy bullet 2 states: A notification SHOULD be sent to the administrator when high-risk users are detected.
Previous work shows that there is not currently an MS Graph API endpoint to validate the notification settings.  Additionally, the implementation guidance further clarifies that settings should "configure Azure AD Identity Protection to email the security operations team/administrator when a user account is determined to be high risk so that they can review and respond to threats."  As such, an automated implementation should include a way for an agency to indicate who the security operations team or administrator to be notified is in order to indicate compliance with the baseline.  Otherwise, even with notification configured it isn't clear that the recipients are valid and correct.
This item is blocked until either Microsoft Graph API and associated Graph Powershell SDK adds support to query these settings OR an alternative automated mechanism can be discovered or developed to retrieve these settings for automated evaluation.

Alternatively, could an AAD P2 license check be added? It's listed as required in the docs

Received a response from Microsoft that there is currently no API to retrieve the list of users that get the "Users at risk detected alerts" emails. Therefore we cannot code any updates to ScubaGear at this time.


allow cluster script to update worker code on nodes

To try this out, do the following.
mkdir ~/example_worker_code
cp ray/scripts/default_worker.py ~/example_worker_code/worker.py
cp ray/scripts/example_functions.py ~/example_worker_code/

Then start cluster.py with
python cluster.py --nodes ... --key-file ... --username ... --installation-directory ...

Then start workers using the local code with.
>>> start_ray("~/example_worker_code")

Try modifying ~/example_worker_code/example_functions.py and then restarting the workers with
>>> restart_workers("~/example_worker_code")

Note that if you ssh to any of the nodes in the cluster, you will find the worker code under $installation_directory/ray_worker_files/.

Need to replace
cp ray/scripts/default_worker.py ~/example_worker_code/

by
cp ray/scripts/default_worker.py ~/example_worker_code/worker.py

This enables us to load custom code on the workers, but it doesn't import them in the shell. So when we start python scripts/shell.py, we won't have access to the newly defined remote functions...

I think the only piece of information that the worker and the driver need for a given application is the path of the file(s) that define the remote functions. We could make these arguments to default_worker.py and shell.py.


On State Machines

State machines for animations are easy to handle: when the current animation is finished (reaches the last frame) it emits a signal or calls the next state choosing from the list of possible next states.
For command state machines it's not that obvious. How would we know if the current state is finished? If commands are triggered one after the other, we might need some kind of status controller (maybe the returned Status).
Another issue is how we store the actual behaviour of each state, the list of commands it should trigger. It's similar to a /def if not exactly the same, so we could just map each state to a /def. But how would we handle its variables? The current syntax is:
stateMachine[machine].addState("bla", "foo", "bar") # creates a new state "bla" with possible new states "foo" and "bar"

StateMachine currently uses a Dictionary to store states. Should we add another dictionary to hold the actual commands? See StateMachine.gd

A proto implementation for image sequences using state machines has been implemented in https://github.com/loopier/animatron/commit/eae6ceb66484d1d8d76d43f4daa5ab3eea1756d9 . I used the existing StateMachine.gd to keep it compatible with possibl future command state machines.
Animation state machines and command state machines may not have the same workflow. This needs further investiation.


Trendspotter azure pipelines

Purpose

Update trendspotter folder architecture according to Azure DevOps Pipeline

Does this introduce a breaking change?

[x] Yes
[ ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[x] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Test the code

No test yet

What to Check
Verify that the following are valid

pylint, pytest

Other Information

Update DevOps pipeline and preprocessing todo list, Update trendspotter folder architecture according to Azure DevOps Pipeline


plane by plane segmentation or full 3D?

I see 2D convolutions are used in the model, does the code do plane-by-plane segmentation?

Yes the prediction per se is done in 2D. We newly implemented TAP method, which facilitates quite accurate 3D prediction using 2D training datasets. Please see the paper on bioRxiv for details.

Thanks for the response. I am interested to use the tool for segmenting large 2D RGB images. Is it possible?

Thanks for considering using PHILOW.
This application does not currently support RGB images. Please wait a little longer, as we plan to support the segmentation of RGB images in the next update.


IPFS upload not loading modal but loading button state

We already discussed this with @hassnian and it would make more sense to have one consistent flow for both minting multiple and one

that means there wont be this loading modal

instead, it will have the same button state as when minting multiple nfts

looks like it shows quite randomly? tried minting the aeroloom again and it did not display this state

thanks to #10095 there is no more "uploading data to ipfs"
try canary , this hasn't been deployed to prod yet


Add Simple method to make deepcopies

Is your feature request related to a problem? Please describe.
It's quite common to use an existing object as a "template" for a new one. For instance, when discretizing a cell into smaller ones for zone depletions it would be helpful to make copies of the cell, its surfaces, and material.
Describe the solution you'd like
Add a clone method to all objects.
So you can do:
new_cell = cell.clone()

instead of:
import copy
new_cell = copy.deepcopy(cell)

Describe alternatives you've considered
Currently the recommended method is copy.deepcopy
Additional context
See openmc.Cell.clone

duplicate of #123.

This will be useful.
Some questions on the mechanics to consider:

How deep should the deepcopy clones go? For instance, cloning a Material should copy the material_components, and it shouldn't copy the _problem.
Should cloning automatically link to a Materials instance and to an MCNP_Problem?
Does the clone automatically get assigned a new number? Will it use append_renumber(), request_number(*args), etc.?

I think generally:

Everything but the _problem should be cloned.
MCNP_Object instances should automatically be linked to the same problem I think.
When copying MCNP_Problem all of its children should be linked to it.


Capturing named streams.

Implemented functionality which will be later needed for fuzzing.

we're getting close :clap:


Question: Local Development and Bootstrap4

If one need to modify/add components, How to test them locally on browser to see whats happening on the UI and for interaction? Currently it's on tests.
We are not pulling bootstrap css locally, then how can we verify the widgets look and feel
Do you plan to support Bootstrap4 or Bootstrap3. Plunker examples are shown for bootstrap3 however issue #1 is being tracked for Bootstrap4

So to see visually what are you doing, you have two options:
You can use a plunker (all plunkers in the README are bootstrap 4). Fork one of our plunker and you can play with them (I should update them to latest versions, that too).
There is a better option I use in every library project. Create a playground application inside the library that will be an application where you can load the library and play with it. You just add it to your global gitignore (if you don't have one, you can create one) and well, it is the best way to play with a library.
I personally use http://puu.sh/ljd03/b1868e9521.zip
Download that, extract the playground folder, copy it inside the root folder of this project, npm install and to run the server npm run dev.
Just require what you need in app.ts and use it.
And yes, everything is bootstrap 4.

@sirajc, just a note that this project is in pure development mode and the code base is incredibly volatile.  I would not rely on anything here being even remotely stable for a while.

@Foxandxss, Thanks for the details and Playground code, I was able to extend it and display all three components in one page.
One question, For rating we need glyphicons which are not part of Bootstrap 4, I used font-awesome locally, what are our goals which icons library are we planning to use?
@icfantv, Thanks for the note, I am not intending to use this as of now, in fact I am planning to do some contribution, so am just getting familiar with this ecosystem

Bootstrap is not even final. When it reaches beta or RC, I will see what their decisions are with the icons and act accordingly.


package request: moonscript

Issue description
In the process of trying to install pgmoon, I discovered than moonc wasn't available.  Indeed, I can't find any reference in nixpkgs to Moonscript except for an emacs mode.
I can probably package this up, but I'm shocked to find that it's not already available; it's fairly obscure, but Nix has pretty good coverage.  So I'll check to see if I'm just missing it (or if anyone has a nix expression for it handy) before spending the effort on it.
Steps to reproduce
cd nixpkgs; grep -Ri moonscript
Technical details
Please run nix-shell -p nix-info --run "nix-info -m" and paste the
results.
edanaher@kroen:~/nixpkgs$ nix-shell -p nix-info --run nix-info -m
error: undefined variable ‘nix-info’ at (string):1:66

Odd....
edanaher@kroen:~/nixpkgs$ nixos-version
17.09pre105622.f0fac3b578 (Hummingbird)
edanaher@kroen:~/nixpkgs$ nix-instantiate --eval '<nixpkgs>' -A lib.nixpkgsVersion
"18.03pre117327.3fe7cddc30"

edanaher@kroen:~/nixpkgs$ nix-shell -p nix-info --run nix-info -m
error: undefined variable ‘nix-info’ at (string):1:66

nix-info -m should be in double quotes, otherwise shell interprets it as multiple arguments.


Pin pygobject below 3.36

This PR pins pygobject below 3.36, see https://git.ligo.org/lscsoft/gstlal/-/issues/67.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

This is not required.


Theme setting lost after restart PowerShell/ConEmu

Hi,
could you please tell me how to config so that I don't have to set theme for PowerShell everytime I start ConEmu?

You could add a Set-Theme Paradox or whatever theme to your $PROFILE

Yup, what @nwykes said 🙂

Thanks guys. Problem fixed.


Cg/poc base case partial

Description
Restart of #65. The branch gives a full proof construction and verification (see tests StandardHonkComposer.*). This branch established a foundation for us to finish the proof of concept by working on the following major remaining work streams in parallel:

Adapt stdlib tests of StandardComposer to run for StandardHonkComposer.
Add Gemini parts of the verifier and reinstate in manifest and prover.
Fix the currently broken copy constraints (tests fail the computation relation, but this may only be due to how the tests are written).

Checklist:

[x] I have reviewed my diff in github, line by line.
[x] Every change is related to the PR description.
[ ] I have linked this pull request to the issue(s) that it resolves.
[x] There are no unexpected formatting changes, superfluous debug logs, or commented-out code.
[x] There are no circuit changes, OR specifications in /markdown/specs have been updated.
[x] There are no circuit changes, OR a cryptographer has been assigned for review.
[ ] I've updated any terraform that needs updating (e.g. environment variables) for deployment.
[x] The branch has been rebased against the head of its merge target.
[x] I'm happy for the PR to be merged at the reviewer's next convenience.
[x] New functions, classes, etc. have been documented according to the doxygen comment format. Classes and structs must have @brief describing the intended functionality.
[x] If existing code has been modified, such documentation has been added or updated.

@ledwards2225 and I spent most of a day debugging this work together. Luke agrees that this constitutes a sufficient review and is happy to have me merge the work to avoid blocking others.


Refactor: GGUF metadata tokenizer

This was my progress on a refactor, but I didn't communicate this effort well with maintainers.

A similar effort was recently made and merged with a slightly different approach. I thus haven't adapted the from_gguf() methods in model files that could have used the approach I proposed here (a simple TryFrom on a struct of metadata fields). I was considering a derive macro to simplify that further, but it might have been overkill for the project 😅
I did propose upstreaming this into Candle directly, but like my other issues/PRs raised upstream I don't know if I'll get a timely response (my PR to the HF API crate still has no activity).

The merged alternative was rather extensive in changes, I don't have the motivation to go through all that. Some structs were renamed, methods changed, the gguf tokenizer file moved along with other changes that'll bring conflicts for rebasing.

If this PR were updated, it would simplify the from_gguf() metadata parameter extraction:
https://github.com/EricLBuehler/mistral.rs/blob/89dea1b1fc80213550eed53fb0020e188f092643/mistralrs-core/src/models/quantized_llama.rs#L274-L287
But without the derive proc macro approach, due to all the usize and defaults, this PR may not be that worthwhile of an improvement.

The related tests changeset is probably still worth having. It fixes a bug with the encoder test case being misconfigured. It also removes the need for the dead_code annotations.
Each commit has a commit message for additional context.

Hi @polarathene thanks. If I roll back the changes s.t. #380 was effectively never merged, would that work for you?

Ok, I reverted and there is just 1 simple merge conflict now :)

If I roll back the changes such that #380 was effectively never merged, would that work for you?

Thanks! Much appreciated 🙏
Sorry about this, I'll try to better communicate when I'm working on a refactor in future 😓
I hope I didn't waste any of your time. You still had some nice changes I think, such as better restructuring of the files (something I've not given too much thought to).

No problem! In the future, f you let me know in Discord, I'll see it immediately so we can coordinate better.

You still had some nice changes I think, such as better restructuring of the files (something I've not given too much thought to).

Maybe you can do something similar? A key point is that each GGUF model has an md_get closure, which we can refactor with our own Content type? Perhaps you can find a better way to do this though :)

A key point is that each GGUF model has an md_get closure

That's no longer necessary if you take the approach I did here with PropsGGUF (not the best name) stuct, just impl a similar TryFrom that maps all the keys and it should look a little bit more terser.

which we can refactor with our own Content type?

I don't know if we need to beyond the MetadataContext (also not a great name choice) struct? Unless there are other parts that would benefit, I was just focused on a cleaner API for extracting the needed metadata fields :)

I'll take a look after some rest, past midnight here 😅
Failing test is for the last encode test case:
HF tokenizer has <s>  prepended, that's the only difference in content vs GGUF tokenizer. I'm not sure why that is. I know there was a bug in this particular test case, so this might have just surfaced what was already there, rather than something I've introduced?

This is a great thing to have. As far as my research, there isn't currently a crate that does this!
Not sure if it's an error in this quant, but it's listed as tokenizer.ggml.model: gpt2.
Given how prolific this hugging face user is I imagine people are going to try their quants and run into the same issue I had (only support for llama). Should I reach out to them or is it something that will be handled by this library?

@ShelbyJenkins thank you!

Not sure if it's an error in this quant, but it's listed as tokenizer.ggml.model: gpt2.

Given how prolific this hugging face user is I imagine people are going to try their quants and run into the same issue I had (only support for llama). Should I reach out to them or is it something that will be handled by this library?

We do the conversion in this codebase, so I can add support for the gpt2 tokenizer type. However, I don't think it is a mislabeling because the other fields for GPT2 are there. I'll try to add this soon.

@polarathene I took a look at it, and I think that the GGUF one is actually wrong here. It is not prepending a BOS token where one should not be. Regardless, GGUF tokenizers are documented to be less accurate than the HF ones and the GGML docs themselves recommend using the HF one.
I have not seen any effect of this error, as the chat template adds that anyway. This can, however, be an issue if you are not using a model with a chat template.
I also did a cursory search for an API through tokenizers to enable this prepending behavior but could not find any. Could you perhaps find what we are missing? A key difference is that we use a unigram tokenizer here (that is what the GGUF tokenzier provides for llama tokenizers), but the tokenizer.json which we are testing against uses a BPE tokenizer.

Could you perhaps find what we are missing?

I'm not quite sure how to? Is there no information in the GGUF to ensure the correct tokenizer is used?
Even with the improved tokenizer support after unigram, is the GGUF still lacking the information to use the appropriate tokenizer?

As another note, I plan on merging this before #397 (which #388 will need for testing) so I am excited to merge!

Sorry for the delay, I'll get onto applying the requested changes.
I'm still not sure how to proceed with the test case issue though.

One of the tests are failing. I assume it's temporary and may have been from a rate limit.
---- sampler::tests::test_gumbel_speculative stdout ----
thread 'sampler::tests::test_gumbel_speculative' panicked at mistralrs-core\src\sampler.rs:423:60:
called `Result::unwrap()` on an `Err` value: IoError(Os { code: 5, kind: PermissionDenied, message: "Access is denied." })

https://github.com/EricLBuehler/mistral.rs/blob/69f86268f70f83ddb99a77e01a8cab0c298faff7/mistralrs-core/src/sampler.rs#L445-L461
https://github.com/EricLBuehler/mistral.rs/blob/69f86268f70f83ddb99a77e01a8cab0c298faff7/mistralrs-core/src/sampler.rs#L415-L425
I'm not familiar with what the rate limit might be (total requests within a duration, total bandwidth within a duration, etc), I guess it'd be optimal to have any models pulled as very small ones that are able to meet the needs of the test, even if they're not suitable for real world usage (perhaps custom trained model with considerably less parameters to keep file size down?).
Provided the model doesn't change much, you could easily leverage actions/cache in the CI to restore it locally to avoid making an external request each CI run?

so if you could add it, that would be great.

Alright, will add that and push shortly 👍

I think we should always use u64 in PropsGGUF (we cast to usize anyway)

I'll leave as-is with this PR, I prefer those kind of changes to be a bit more isolated for git blame traceability without all the added noise from unrelated changes.
I could open a TODO issue for that if you'd like, since you're going to update this file next. Or leave with the TODO comment reminders I have in the PR 😅

Provided the model doesn't change much, you could easily leverage actions/cache in the CI to restore it locally to avoid making an external request each CI run?

Thanks, I'll look into using a cache. The Windows test is a bit flaky for this reason.

I could open a TODO issue for that if you'd like, since you're going to update this file next. Or leave with the TODO comment reminders I have in the PR 😅

Sounds good. I'll probably resolve it quickly, as I will bundle the changes in the next PR.

I am not sure about this new test failure.
It's with the decoder again, but since your calling a non-deterministic input from a REST API web request, it's a bit tricky to know when the test is actually passing correctly?
Perhaps my change to the workaround types has a flaw :(

UPDATE:
I can see that every space character is being replaced with _ (similar but not same, actually this: ▁) in the GGUF tokenizer (there is almost 16k of these), but it looks like there is other differences too.
After converting those to spaces, it looks to be a similar issue. The GGUF tokenizer was prepending ▁ to the string.

Can you please hardcode the test passage so that we have a consistent input?

Sure.
I haven't gone over the contents of this llama.cpp tokenizer test, but it's probably a good reference (lists some edge cases they encountered too where some models fail).
For now I'll just go with a single input based on some content from there.

@EricLBuehler your recent merge was based off your earlier PR work that you since reverted, you merged that and now there's a bunch of conflicts for changes unrelated to Phi3 vision 😓
I'm not even able to resolve those via the web UI this time apparently (not that I particularly would want to):

Potentially, revert the merge, and fix the history there?
That PR was 184 commits long though, it looks there were other changes like dropping some docs (Adding models, CLI docs), so I don't know what else was done that was/wasn't intentional 🤷♂

Ok, sounds good. Is this PR ready for merge?

Is this PR ready for merge?

Yes?
You asked for the test to be updated and I addressed that roughly 11 hours ago. But now there is the conflicts.

Ok, thanks for confirming. I'll undo the merge of that PR so that this can merge cleanly. Sorry for the inconvenience!

Thank you!

Just to confirm, was the removal of those mentioned doc pages intentional? Seemed like useful information, just a bit outdated?

Sorry, which docs pages were removed?

which docs pages were removed?

I referenced them at the end of the comment above. "Adding Models" / "CLI".
I then said if that was unintentional that there may have been other mishaps, but there was quite a bit of changes in the PR you merged.

Oh I see. I removed the "Adding models" in favor of a comment in the README contributing section because of the rate of development regarding that section, and the "CLI" document was prone to being outdated. If you know of a better way to autogenerate the CLI docs that would be great, I think we could do it in CI.

If you know of a better way to autogenerate the CLI docs that would be great, I think we could do it in CI.

Yeah, you could probably have a template file to produce the markdown content? Or switch to a docs generator that can import content from separate sources.
Then for the CI part, you would just get the output of the CLI help and if it doesn't match the importable snippet, it'd update that and generate the page again.
Another way with CI is to have that sort of behaviour triggered on an automated schedule rather than commit triggers. That can then create a PR with the update, I've not done that before myself but I'm aware of something like that 🤔

Ok, I'll look into that. But before starting work on this, do you see static CLI docs as a useful tool when users can simply download and run with --help? That was my rationale.

do you see static CLI docs as a useful tool when users can simply download and run with --help? That was my rationale.

It was useful as an insight when I first came across mistral.rs and was looking through the README. I think that was more of an issue with the README at the time being a bit confusing with instructions, and I knew I'd have to build the CLI.
If there's no additional context though, it's probably not that meaningful :)
I had a look over the deleted document, it doesn't appear to provide any value beyond an overview to reference without the CLI available. I wouldn't worry about restoring it 👍

Great. I did a refactor of the README yesterday, do you see any parts that are confusing or hard to find?


question: is there a way to trigger a Terraform object reconciliation with its source object via CLI? like flux reconcile kustomize

my current workaround is to push an empty commit and run a flux reconcile source command on the source object of the Terraform object

Yes, you can use tfctl to trigger a reconcile: tfctl reconcile <resource-name>.