Fails on to open pdf (Invalid PDF structure)

Link to PDF file (or attach file here): https://ora.ox.ac.uk/objects/uuid:dd8473bd-2d70-424d-881b-86d9c9c66b51/datastreams/bine2aea0d2-0f9c-43a5-b551-c9570284d9f0
Configuration:

Web browser and its version: Version 61.0.3144.0 (Official Build) canary (64-bit)
Operating system and its version: Win 10 64b <IP_ADDRESS>3 Build 14393
PDF.js version: 1.6.293
Is an extension: Yes

Steps to reproduce the problem:

Open link

What is the expected behavior? (add screenshot)
File should open
What went wrong? (add screenshot)
Invalid or corrupted PDF file.
PDF.js v1.6.293 (build: 9295114)
Message: Invalid PDF structure
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

Works for me, using the latest version of PDF.js (which as of this writing is 1.8.503).

PDF.js version: 1.6.293

This version is outdated, and I'd recommend updating to a newer release; see https://github.com/mozilla/pdf.js/releases.
Closing, since nothing appears to be broken here.

Problem is I'm using the Chrome extension from Google Store and the version there is stuck at 1.6.293.
Is there anywhere a fresher version?


Phantom - Add "zig-zag" toggle

Minor issue - when using Phantom in combination with the "Switch Like Home" add-on, the zig-zag behind the icons on the home screen doesn't center vertically under the icons the same way as normal.  Still looks fine, but I would request that a toggle be added to turn optionally off the zig-zag pattern for users who don't care for it.
Image with Phantom + Centered Home
Image with Phantom + Switch Like Home
Thanks for your support!

Done!

Thank you!


Issues are not enabled in the GitHub repository.

in result.md, I can see this:
Issues are not enabled in the GitHub repository. So users cannot report bugs. Please enable issues in your repo.
In my case all issues is reported in my own forum

maybe you can bypass it with noGitHubIssues: true, in package.json (new value)
maybe use

"bugs": {
 "urls" :"https://....."
},

maybe this rule:
If "Issues are not enabled in the GitHub repository." and "noGitHubIssues" and bugs.urls --> bypassed
else display your actual message

Okay, we can do something about that. I'll try to adapt it soon.
The field is originally called "url" and not "urls", right?

Ready for testing with https://github.com/bugsounet/EXT-Detector/pull/92

I fixed it :smiley:


add: segmentation guide.

Closes #5181
I have opened a PR on Hub (https://huggingface.co/datasets/huggingface/documentation-images/discussions/5) to include the images in our central Hub repository. Once the PR is merged I will edit the image links.
I have also prepared a Colab Notebook in case anyone wants to play.

[x] Replace the image links

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Thanks @osanseviero. Am I good to merge?

I would wait for a second approval just in case :)

Sure :)

Merging since the images have been pushed as LFS files (PR).


Stop vim adding a new line

Unclear what unit test to do.
Would help Online_authentication_API/issues/85#issuecomment-2417556.
Instructions: Replace the template text and remove irrelevant text (including this line)
Is your feature request about something that is currently impossible or hard to do? Please describe the problem.
A clear and concise description of what is hard to do. Ex. It is difficult to [...] when [...]
(If it is related to runtime files, please check their header for where to discuss enhancements.)
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

It seems to only add a line when :w, hopefully.

It seems that a unit test can be modify and save a file without new line (wc -l returning 0), as it adds a new line (wc -l returns 1).
DuckDuckGo search Stop vim adding a new line.

The Stack Overflow answer 729795 reminds the importance of ending a file with a newline.

set nofixendofline (source: the Stack Overflow answer 16114535) keeps newline if there is already one. However, it does not add one.


[enhancement]: AzureFunctionApp task should validate appType against the existing function and enforce WEBSITE_RUN_FROM_PACKAGE settings accordingly

Task name
AzureFunctionApp@2
Describe your feature request here
Issue Description
The current implementation of the AzureFunctionApp task does not validate the appType (Linux or Windows) against the existing function, leading to potential silent issues when deploying functions with WEBSITE_RUN_FROM_PACKAGE settings. This can result in unexpected behavior, particularly when the WEBSITE_RUN_FROM_PACKAGE value is set to a URL.
Issue Context

When WEBSITE_RUN_FROM_PACKAGE is set to a URL and the function app is on Windows, it may lead to trigger issues, causing the function to be unresponsive to requests without raising any exceptions.
On Windows, the correct setting for WEBSITE_RUN_FROM_PACKAGE should be 1. However, if the appType is mistakenly selected as functionAppLinux, it can result in a frozen state without triggering, even when there are incoming requests.

Documentation Reference
WEBSITE_RUN_FROM_PACKAGE Documentation
Expected Behavior
The expected behavior is that if the task is used with appType: 'functionAppLinux' for a function on Windows, the task should fail and not proceed. This validation ensures that the deployment settings align with the platform requirements, preventing potential silent issues.

Hello, thanks for the issue. Let me investigate and see if we can add additional information.

@FinVamp1 was it adressed?


Strangely not working at all

This is not working on the latest builds on Sponge. I don't have time the next two days but Friday afternoon I will look into this and make some other slight updates as well.

Fixed in b98c7d965353556366c235065d60fafe194547a8


persist chain registry data

Rework defiant infra to give a persistent disk that can be used to hold chain-registry data.
Update the python code logic so If the data is less then X hours old, it should not need to be re-fetched.

fyi @clemensgg  I dded a 1GB persistent storage available at /cr.  Still need to rework the code to choose where to save the cr data. I gave this a stab this morning, but was not working, ill try again later this weeknd, or if you want feel free.

oh yeah, we could do a REPO_LOCATION env var (defaults to ./ where it is currently extracted to).
it works great locally.


MODE-2418 Fixed potential ConcurrentModificationException

This PR contains 2 commits:

one which adds a small optimization & a better exception message for the JcrVersionManager
one which fixes a potentially much more critical issue: when using local transactions (i.e. started & committed by ModeShape during session.save) there was a potential leakage of nodes that were being changed/edited in that transaction into the shared workspace cache (used by everyone else incl. readers), before the transaction was committed The solution was to make sure that a TransactionalWorkspaceCache is used always, regardless whether a user or a local transaction in active.

Looks good.


js files in subfolders are ignored

Hmm, I'll need to take a look, but just to make sure, what you mean is, the file GridColunaSubTabela.js should be included in the bundle as well, but currently it is not?

thanks for the reply blutorange, exactly, the content of the file is not included in the minified

So yesterday was a national holiday here in Germany, but today I've got some time to take a look at this.
I tried to reproduce what you described, but as far as I can tell, everything is working as intended. However, please note:

The docs for bundleConfiguration say If not an absolute path, it must be relative to the project base directory.. But in your screenshot, you specify /minify.json. This is an absolute path in Linux, but not in Windows, so I'm assuming you are running on a Windows system (otherwise the build should fail). Nonetheless, I would recommend you omit the slash for cross-platform builds.
The base directory for the files specified in the bundle is taken from the baseSourceDir property. Since you did not specify that property in the plugin configuration, it defaults to ${basedir}/src/main/webapp.

Here's a minimal Maven project based on the screenshot you posted that works: https://filebin.net/1ls51dx1vsc5kb48
PS: The JSON bundle feature still exists because I took it from the project from which this one was forked, but tbh, I don't quite see the point of JSON bundle files. Is there any particular reason you prefer a JSON file with the files to include instead of just configuring everything in the pom.xml (using multiple executions if you need multiple bundles)?

Good evening, sorry for the delay in responding.
First I would like to apologize because it was my mistake,
as the problem was in the name of the folder "subTable" in the capital letter "T".
I changed the name correctly and it solved my problem.
Anyway, I'd like to thank you for the feedback.


Creates system alert in webpages, expected browser style

Alerts and confirm dialogs display as the native style. This could lead to phishing scams, as there is no permission guarding alert and confirm.

To Reproduce

Go to Alert POC Hyperdrive
Click through the alerts.

Expected Behavior

I expected a normal alert box.
Screenshots

Not possible.
Environment

OS:
Windows 10, updated yesterday. WSL disabled.
Beaker Version:
Latest as of yesterday, clean install

Additional Context

This happens on any page. Please note that prompts work as expected.
Please host the POC for me, as I have limited bandwidth.

This is mostly a duplicate of an issue I raised in 2020, which is still open: #1823


any release notes available

hello
any release notes available  ?

https://github.com/IdentityModel/oidc-client-js/releases

i see now that the latest is 1.3 beta .. whats new ?
thanks

No official release notes as far as I can tell yet but you can check out the issue tracker for 1.3.0 and the commits since 1.2.2 on DEV to get an idea of what was done so far

Yep, @superjulius is correct.


show column content on hover

Can you add a title field or anything similar?
Some time my columns are too small and don't show their whole content, I would like that in that case (and in any case) when I hover it will show a tooltip/popup with the column content. For now I'm adding in cell renderer a span wrapper with the attribute title equals to the cell content.
Thanks in advance and Thanks for this awesome grid!

hmmmmm, not sure i like this . . . . having the content as a tooltip sounds great, but is not for everyone, so having to customize it yourself in the colDef makes sense to me.
let me think about it. maybe I put in a colDef.tooltip which would work like valueGetter  . . . . . .

When the column is too narrow to show the full content, showing the tooltip on hover is nice.  I would like to have this feature as well.

the colDef already supports tooltips. sorry, i should of closed this issue when this was done, i didn't realise the issue was here.
eg
colDef.headerTooltip = 'this is my tooltip';

@ceolter but that's for the header only right?  or is it for the content as well?  The content is dynamic...

sorry, my fault, i read it as column header. will reopen.

Yes. Below column should have tooltip to see the full contents.

Is there any possible workaround where I can show tooltip?

nope. unless you take a fork and implement it yourself.

+1
Should be a per column option IMO.
 columnDefinitions =
[
    {
        headerName: 'Column Header',
        field: 'column',
        enableTooltip : true
    }
]

+1
On Mon, Mar 7, 2016 at 1:32 PM Ronan Quillevere<EMAIL_ADDRESS>wrote:

+1
Should be a per column option IMO.
columnDefinitions =
[
{
headerName: 'Column Header',
field: 'column',
enableTooltip : true
}
]
—
Reply to this email directly or view it on GitHub
https://github.com/ceolter/ag-grid/issues/415#issuecomment-193214395.

+1

just implemented. next release will have it.
new property is colDef.tooltipField, where you provide the field where the tooltip can be found

Thanks!

I was able to render custom tooltip with HTML markup on column headers through "headerCellRenderer" and by setting "angularCompileHeaders" true,
Is there any way I can apply custom tooltip (not just HTML title) on content?

tooltip was introduced in a recent release.
see tooltip here
https://www.ag-grid.com/javascript-grid-column-definitions/index.php

Thanks

Good work.

tooltipField covers only the most simple scenarios.
I'd rather have something like tooltipValueGetter(params)

It works great.
Is there any way to make it fast. as of now, upon hover overing it, you have to wait for 2-3 seconds until it appears. Thats a lot of time waste. Is there any way i can avoid it?
Thanks a lot.

@harshitgupta I believe it has some delay, because otherwise tooltips would be jumping out on every mouse swipe above the table.
Probably it would be nice to have a  cellTooltipDelay: float; property to change the delay if required

can we style this tooltip?

@ceolter Was tooltipField removed at some point? I don't see it documented on https://www.ag-grid.com/javascript-grid-column-definitions/index.php.

i cant find the tooltip field in documentation.
https://www.ag-grid.com/javascript-grid-column-definitions/index.php.

Take a @Piccirello @anandSep90 look https://www.ag-grid.com/javascript-grid-column-properties/ for the latest docs

Yeah the tooltip properties is available in the above link.
{ headerName: "User Role", field: "userRole", width: 70, editable: true, tooltipField: "userRole", headerTooltip: "User Role"},

By default tooltips should be turned on automatically with the cell value when the column width is smaller than what the cell value need to display completely

While a few have suggested tooltip styling, or maybe cellTooltipRenderer, there has been no response.  is there a way to style the tooltips?

cellTooltipRenderer would be nicer to have.
I add a tooltip in cellRenderer but the problem is the tooltip must be  "display: overflow" to show.
but if setting the cell as overflow, the columns would be affected too.

if i want ellipsis just when i can't see all the sell content,how can i do it?
i want to enable another tool tip sometimes,all time.

Am using Ag grid with vue+typescript
am getting this error when i use tooltip feature. any help

It's not working at all, and I am using your latest release.
  getColumnDefs = (fieldsArray) => {
    let columnDefs = [];
    this.tableData = this.data.map((record) => {
      let obj = {};
      fieldsArray.forEach((field) => {
        obj[field] = record[field];
      });
      return obj;
    });

    Object.keys(this.tableData[0]).forEach((key) => {
      let obj = {
        headerName: this.labels[key],
        field: key ,
        sortable: true,
        tooltipField: key
      };
      obj.valueFormatter = (params) => this.formatCells(params.data[key], key);

      columnDefs.push(obj);
    });

    return columnDefs;
  };

I'm trying to use tooltipField on cellrenderer but its not working
const columns = [
{
field: "productName",
lockPosition: true,
tooltipField: 'productName',  --> working as expected
},
{
field: "history",
lockPosition: true,
width:50,
cellRenderer: 'historyRenderer',
tooltipField:'history' ---> not showing the tooltip in this case when I add cellRenderer for column data
},
]
Can you please explain where it could have gone wrong?


clam_trace_gen

It is a good start.  The function access3addr is a good place to return ref id with the data address.  You'll also need a pass to assign a unique ID for each AryRef.


Fix x86-16 Windows cspec for stdcall ambiguity

x86-64-win.cspec deals with __fastcall and __thiscall by simply (somewhat misleadingly) specifying extrapop="8" and letting the resolution occur in the decompiler.  Really it should be "8 + args"
x86win.cspec deals with __stdcall, __thiscall and __fastcall by specifying extrapop="unknown" which although true fails to make an expectation that "unknown" means "4 + args" and it would be a stretch to say it could be inferred from pentry stack addresses.  It deals with this using a resolveprototype construct and an eval_current_prototype to allow selection instead of the default.
I propose either we do the same for x86-16.cspec or change "unknown" to "4" and use the 64-bit strategy.
This is likely a key part of the source of 4 reported issues although the decompiler should really handle prototype identification better and this is hardly the end of the story.  Problem a new XML attribute is needed - something like the now obsolete "stackshift" which would be an excellent hint!
Currently even with the selector - which all x86-16 bit files generally require - most use a mixture of far and near calling almost never one or the other exclusive.
But this change is a correct start towards fixing this entire area.

I also added the first fixup to the file which handles the following MSC v6.0/v7.0 & MSVC v1.0/v1.5 windows runtime routine which attempts to prevent stack overflow but also adjusts the stack pointer unlike its misleading name would suggest:
__chkstk        proc near
pop     bx
inc     ax
and     al, 0FEh
sub     ax, sp
jnb     short prepare_exit
neg     ax
cmp     ss:0Ah, ax
ja      short prepare_exit
cmp     ss:0Ch, ax
jbe     short success
mov     ss:0Ch, ax
success:
mov     sp, ax
jmp     bx
prepare_exit:
mov     ax, 0
jmp     __amsg_exit


Render to specific mip level of a texture

Ran into an issue where the mid level api was not flexible enough to accommodate the rendering to a specific mipmap level of a texture rather than the standard 0 level.
Added a tiny tweak to open up this feature..

@GoodBoyDigital is there anyway to add a unit-test for this?

@GoodBoyDigital is there anyway to add a unit-test for this?

yessir! added a test 👍


Just now i added  new  registry keys

On Windows 10 1809 64bit, I added new registry according to your article.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\policy\APTCA\aptcagac]
"APTCA_FLAG"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\Windows Presentation Foundation\Features]
"XBAPDisallow"=dword:00000000
"LooseXamlDisallow"=dword:00000000
"WebBrowserDisallow"=dword:00000000
"MediaAudioDisallow"=dword:00000000
"MediaImageDisallow"=dword:00000000
"MediaVideoDisallow"=dword:00000000
"ScriptInteropDisallow"=dword:00000000
Should i keep these keys or else delete them, Do i get any security problems while browsing on IE11  and on EDGE  browser keeping this setting.
Thanks for your article

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

ID: cc421c44-f66c-6e10-3413-00d6fee7ce81
Version Independent ID: 6c375715-042f-f4e9-a0db-580b3df37320
Content: Security (WPF)
Content Source: docs/framework/wpf/security-wpf.md
Product: dotnet-framework
GitHub Login: @dotnet-bot
Microsoft Alias: dotnetcontent

@RAJU2529 Apologies for the late response.  This issue is now a year old -- did you find an answer somewhere else or are you still looking for an answer?

@tdykstra. No sir I didn't got answer. I need clarification , if I add above registry keys on Windows 10 1909 64bit enterprise , do I get any secure issues  and while browsing on edge and internet explorer

@GrabYourPitchforks can you answer this security-related question or direct it to someone who can?

Closing as duplicate of #8874


Fix br_fifo_flops_push_credit_tb

This got broken when I removed the credit_available signals.

Close this since we are putting back the credit_available signal for convenience anyway


[WIP]add test case for [linkis-scheduler] #1914

What is the purpose of the change
Added tests for  linkis-scheduler package

Thanks, I will review this

Hello, the username in your commit may be inconsistent with GitHub, so that it will not be counted as contributor, and you need to reset it.

me in your commit may be inconsistent with GitHub, so that it will not be counted as contributor, and

OK I will correct it soon.


Vendor needs ability to label items "Out of Stock" or "Inactive"

Right now you can either display an item or delete an item, with nothing in between, but that's going to be a major problem for someone who runs out of stock temporarily.
@morebrownies suggests:

Listings need some type of status field so that vendors can set them to active out of stock or inactive

They’ll need this for adding new items to their store too. They may want to preload listings and activate all of them on the same day when they’re ready.

[If someone lists as out of stock ] we could hide the buy buttton and display out of stock instead

It would be helpful if we could start adding screenshots of people asking for certain features so that when we take on the work we have a good idea of how important it is and what they're trying to accomplish.

Similar to #1133, but an enhancement to build upon once we can count and reduce available stock after purchase.

Is it possible to attach a JSON variable to the listing (out_of_stock), and keep the client from buying it? If they buy it anyways (old version of the OB client), then refund the client and tell them to upgrade their version of OpenBazaar? Maybe withhold the public key for the wallet if they try to buy it instead of shafting the buyer with transaction fees.


Unit tests are failing in CI builds

In our CI builds, the following four tests recently started failing for x86 (x64 is fine):

ValidateExpressionRegExMatch
ValidatePasteExpressionErrorStates
ValidateScientificPasteExpressionTest
ValidateStandardPasteExpressionTest

This started happening after #687 was merged. We didn't catch it before the PR merged because we only validate x64 for PR builds.

This is your friendly Microsoft Issue Bot. I've seen this issue come in and have gone to tell a human about it.

Looking closer, this isn't an architecture-specific issue. Actually, the x64 test runs just haven't been discovering or running any tests.

Fix by #743

Keeping this issue open until we resolve the test discovery issue for x64.

Repros in a blank unit test app. Reported to the vstest project: https://github.com/microsoft/vstest/issues/2233

A fix for this should be available in a forthcoming update to VS2019 (16.6).

This is now fixed because VS 16.6 has been deployed to the Azure Pipelines agents which build our app.


how to run openfl code

hwdy,
this may be simple. but is there a way this can run openfl code at all from within atom?
not seen anything too much on this, except people saying to just do it in console
thanks

The way it works is that this package (the haxe package) provides support for and services for haxe specific features ionly, and framework specific support (like openfl with lime tools, or flow) are separate packages.
There is no and will be no openfl support in this plugin, that's not an option. An atom-openfl package must be made that will handle it's own details. For an example while we are unifying the package code for sublime/atom - see https://github.com/snowkit/atom-flow


Create StateMachineAula1e2Godot

It could be a nice addition, but I don't want to confuse the beginners who follow this tutorial with a script that hasn't been covered.
Nevertheless, I appreciate your contribution!


Option to call macro on completion

Hello, I think an option to call a macro upon completion would open this module up to automating a lot of the results of training, crafting, and other long term activities.
With a macro call (ideally one that accepts inputs) the sky is the limit, obviously I have no idea if it’s even possible but I thought I’d throw it out there as an idea for a future feature.

Hey thanks for the request! Good news - there's already a feature built in that can let users accomplish the same thing, with just a little more getting their hands dirty.
Stuff like this is what you'd use the Macro progression type for on an activity (and is exactly why it exists). The only difference to what you're proposing is that the macro you use here would also include the logic for "rolling" and updating the downtime activity, and a check for completion afterwards. Basically - you tell the module what to do to increase progress, update the progress value, check to see if it's done, and then conditionally do your "on complete" actions. If you've got the know-how to create a macro to run on completion in the first place, you should have the tools you need to do the extra steps too.
Here's an example of a Medicine Skill Check with a DC 15, that does whatever you specify once it completes:
// ======= CONFIG ========

let actorName = `Example Actor`; //The name of the actor who owns the activity to update.
let itemName = `Crafting Example`; // The name of the activity to update.
let checkDc = 15; // The DC of the check
let skillToRoll = `med`; // The abbreviation of the skill to roll.

// ==========================

// Get our actor and item
let item = CrashTNT.getActivity(actorName, itemName);
let actor = game.actors.getName(actorName);

// Make necessary rolls
let skillRoll = await actor.rollSkill(skillToRoll);
let total = skillRoll.total;

// If total is high enough, increase progress by 1
if(total >= checkDc){
    let newProgress = item.progress + 1;
    CrashTNT.updateActivityProgress(actorName, itemName, newProgress);

    // Check for completion
    if(newProgress >= item.completionAt){
        // Do your things here
    }

}

Thank you for your response, it totally slipped my mind that the macro called for progress rolls could also just check to see if the activity has been completed.
Follow up question, does the macro field accept inputs to be passed to the macro?

It does not, no. I'd imagine pretty much anything you'd need you should be able to get programmatically from inside the macro, though. Depends on what you're trying to do, I suppose.


Mac OS issues - is psutil supported ?

I read you were able to run on Mac OS.
I was following the tutorial:
spot issue with psutil:
https://nilomr.github.io/pykanto/_build/html/contents/basic-workflow.html
File ~/Sites/miniconda3/lib/python3.9/site-packages/pykanto/utils/compute.py:138, in calc_chunks(len_iterable, factor, n_workers, verbose)
    129 """
    130 Calculate chunk size to optimise parallel computing.
    131 Adapted from https://stackoverflow.com/a/54032744.
   (...)
    135
    136 """
    137 if not n_workers:
--> 138     n_workers = len(psutil.Process().cpu_affinity())
    140 chunksize, extra = divmod(len_iterable, n_workers * factor)
    141 if extra:

AttributeError: 'Process' object has no attribute 'cpu_affinity'

My version is 5.9.4
Here it says psutil is not supported by Mac OS, and optionally, comment out the line.
https://github.com/astooke/rlpyt/issues/40
How did you get it to work ?
I am using Mac Os 11.6 (Big sur)
Using a conda environment
Don't know if related, but were able to use joblib
Can you please advise?

Found that cpu_affinity() is not supported for Mac OS.
https://github.com/giampaolo/psutil/issues/1826
Would it be possible to disable it in the API of pykanto, or let the user specify numbers of workers for multiprocessing ?
I mean, expose n in calc_chunks () - or please tell if you already thought about this!
chunk_info = calc_chunks(n, verbose=dataset.parameters.verbose)
    133 chunk_length, n_chunks = chunk_info[3], chunk_info[2]
    134 chunks = get_chunks(keys, chunk_length)

File ~/Sites/miniconda3/lib/python3.9/site-packages/pykanto/utils/compute.py:138, in calc_chunks(len_iterable, factor, n_workers, verbose)
    129 """
    130 Calculate chunk size to optimise parallel computing.
    131 Adapted from https://stackoverflow.com/a/54032744.
   (...)
    135
    136 """
    137 if not n_workers:
--> 138     n_workers = len(psutil.Process().cpu_affinity())
    140 chunksize, extra = divmod(len_iterable, n_workers * factor)
    141 if extra:

AttributeError: 'Process' object has no attribute 'cpu_affinity'

Meanwhile, is the only option to install from git in dev mode, and edit the code:
git clone https://github.com/nilomr/pykanto.git
cd pykanto
pip install -e '.[dev, test, doc]'


bug: Cant find Marttra in word ends with tone mark

Description
For module pythainlp.khavee
There are some bugs (logic error) when using function check_marttra with word that ending with tone mark (ไม้เอก, ไม้โท, ไม้ตรี, ไม้จัตวา; ่ ้ ๊ ๋)
Expected results
from pythainlp.khavee import KhaveeVerifier
kv = KhaveeVerifier()
# สี่ (four in Thai, ending with ไม้เอก ' ่')
print(kv.check_marttra('สี่'))

กา
Current results
Cant find Marttra in this word
Steps to reproduce
from pythainlp.khavee import KhaveeVerifier
kv = KhaveeVerifier()
# สี่ (four in Thai, ending with ไม้เอก ' ่')
print(kv.check_marttra('สี่'))
# any word that end with tone mark

PyThaiNLP version
4.0.0
Python version
3.9.16
Operating system and version
Ubuntu 20.04.5 LTS
More info
Running via Google Colab
Possible solution
use pythainlp.util.remove_tonemark to remove tone mark before input in check_marttra (as a workaround for now)
maybe add more statement in the function to deal with these cases
Files
No response

@kangkengkhadev @HRNPH I don't sure about this bug.

well I think remove tone mark should work but I'm also not sure yet
I'll take a look at this tmrw


Adding APIs for private link

Changes

Adding APIs for SignalR PrivateEndpointConnection
Adding new field upstream

For both changes, backward compatibilities are took into account. If they are null, whether it's from old SDK or newer version of SDK, we won't change anything. Only if it's not null, we read their children properties and handle it correspondingly.
Validations documented at Swagger Validation tools all passed.
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[x] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

Can one of the admins verify this patch?

@juniwang there is  4 validations failure to fix. you should fix avocado first then modal validation & others

/azp run automation - sdk

@akning-ms Thanks for following up. Validation errors fixed.

@juniwang - few comments

/azp run automation - sdk

/azp run automation - sdk

/azp run

Hi @ravbhatnagar Could you please review this PR again?

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

Thanks for review, we will have a internal discussion first about the api-version

@juniwang Suggest to refer to https://github.com/Azure/azure-rest-api-specs/pull/8935 and try to use types in the common folder. Thanks!

Close this PR since we have another one: https://github.com/Azure/azure-rest-api-specs/pull/9377


Better matching and time interpolation

This PR removes the use of dataframes as a temporary solution when interpolating and other improvements in the matching between observation and model results.

$ mypy modelskill/timeseries/_timeseries.py --strict
Success: no issues found in 1 source file


Is there any difference between using a Parameter layer and using normalize: true in InnerDistance layer?

Are they equivalent?

No. Using Parameter layer means to get a true gradient to the weights. Using normalize: true means to force normalizing the weight during forward.

@happynear Thanks! Then why the normalized_Euclidean_contrastive.prototxt doesn't use such a Parameter layer?

There is not too much difference. Either way is ok.


Need some help with apache2 error log format

I have one virtualhost with these 2 log files I'd like ot parse by goaccess ideally at the same time.
 ErrorLog /var/www/domain.tld/logs/error.log
 CustomLog /var/www/domain.tld/logs/access.log "combined"

goaccess access.log works fine but error.log can't be figured out by goaccess with any of the default options when the config dialogue pops up.
sample from error_log
[Wed May 17 10:18:36 2017] [error] [client <IP_ADDRESS>] File does not exist: /var/www/domain.tld/public_html/favicon.ico, referer: http://www.domain.tld/report.html

I am able and willing to change my vhost log formats if someone has a suggestions which makes this command work:
goaccess access.log error.log

Right now you can't parse two different formats, #213 will address that. If you would like to simply try parsing the error.log, you could try:
goaccess error.log --log-format='[%^ %d %t %^] [%^] [%^ %h] %^: %U, %^: %R' --time-format=%T --date-format='%b %d' --http-protocol=no --http-method=no

Thanks, that worked just fine!
Any idea how to modify my vhost logging settings to be able to parse those two separate access and error log files

If you are using Apache >= 2.4, then please take a look at ErrorLogFormat, you may need to introduce some empty fields such as user agent since it looks like there isn't a specifier for it.

Thanks!

It keeps on asking the log format

I have problem with log
any help Please
Oct  8 11:55:59 server2 server2-access <IP_ADDRESS> - - [08/Oct/2020:00:00:12 +0200] "GET /wikiTek/info/tests.php" 200 6953 "https://wikiTek.com" "Mozilla/5.0 (iPhone; CPU iPhone OS 11_2_5 like Mac OS X) AppleWebKit/604.5.6 (KHTML, like Gecko) Version/11.0 Mobile/15D60 Safari/604.1"

@Houssem99 This should do it:
goaccess access.log --log-format='%^ %^ %^ %^ %v %h %^[%d:%t %^] "%m %U" %s %b "$R" "%u"' --date-format=%d/%b/%Y --time-format=%T --http-protocol=no

Hey, I am trying to parse this
 [Thu Jun 09 06:07:04 2005] [notice] LDAP: Built with OpenLDAP LDAP SDK
but when I use a similar config to the previously suggested formats
 --log-format='[%^ %d %t %^] [%^] %M' --time-format=%T --date-format='%b %d' --http-protocol=no --http-method=no
I get

IPv4/6 is required.

Format Errors - Verify your log/date/time format

What am I missing?

@Pol52 As it says there, IPv4/6 is required.


Game doesn't register some custom scrap and disappear

I was getting 2 bear plush from Plushies plus mod, a bronze trophy, Oj gloves and that 2 handed bronze statue thing from all the scrap, when i start the ship to orbit the moons, the game result screen ignore these scrap value and only count other scrap that is not from these mods the value it shown is 182$, scanning them still saying they still there and worth over 400$. and when i leave and
rehost the save file, all the scrap that was not register by the game disappear and when i scan again the total value is now exactly 182$ just like the game show on the result screen. Kinda weird because all of these custom scrap required lethal expansion.

i was playing solo with this one

The module is not from me, all what i can do it add a lot of warnings in the SDK when an anomaly is found, but i can't fix the scraps of other peoples if they missed a component or put the wrong tag on the object

hmm gonna find what cause this issue else where


Navigate to previous and next sibling folder

A feature that allows navigating to the next sibling folder or file relative to the currently opened one would be great. For example, given the following situation (bold means currently opened)

manga/

title/

chapter 1/
chapter 2/
chapter 3/

When I now reach the end of chapter 1 and attempt to navigate to the next image once more, ideally ahoviewer would automatically navigate to the first image of chapter 2. The same in reverse of course goes for navigating backwards.
Making this action a configurable keybinding (for example up and down arrows as default) in addition to an option for the last and first image of opened folders and files would be great too. That way easy navigation through mangas and similar media would be possible.

I look into adding this as an optional feature

Thank you again.


Priority type and priority reasons

We would like to add a field to set up a priority for the complaints received in the system. Hawaii often receives priority 1 complaints that need more attention than other ones. We will also have this feature available for NOIPM, so they can also use it if needed.
In Scope

On the Intake Source field add a new value as  Priority Incident
When Priority Incident is selected we should display a new field for priority level, as a drop down with values [Priority One, Priority Two, Priority Three]
Add a new drop down for priority reasons with values below, in alphabetic order . This field is also only displayed when Priority Incident is selected as an intake source. This field should also allow you to write in text in case you need to add other values.

Death in Custody
Death of On-Duty Staff
Escape
Major Property Damage
Assault to Employee
Assault to PiC
Assault to Civilian
Significant Discovery of Contraband
Arrest of Staff
Arrest of Civilian
Disturbance/Riot
Discharge of Firearm
Hostage/Barricade
Suicide Attempt
Successful Suicide
High Risk Motor Vehicle Pursuit
Bomb Threat
PREA
Other
Out of Scope

The case details page should also display the Priority Level and Priority Reason for that case.

Mockups
https://www.figma.com/file/3XcaCKS0xC3U0mo98B8eTV/Features-Complaint-Manager?type=design&node-id=253-1284&mode=design&t=ixtXcasWcyqTUyqw-4
ACs
Given I have accessed the complaint manager for Hawaii
When I create a new case
Then I can select Intake Source = Priority Incident, I can select a Priority Level and a Priority Reasons for that case.
Given I have created a new Priority Incident
When I do not see a Priority Reason that matches the incident that I have in hand
Then I can add a new value by writing in the reason that suits my case

I created a mock up "New Case form" to added a field to set up a priority for the complaints. See mock up for review
https://www.figma.com/file/3XcaCKS0xC3U0mo98B8eTV/Features-Complaint-Manager?type=design&node-id=188-1567&mode=design

@kjonesthoughtworks
Christin's feedback:
Instead of checkboxes, can we add, “Priority Incident” as a category under “Intake Source”
Once Priority Incident is chosen, can the next two dropdown boxes change?
Select a Complaint Type à Priority Level
Person in Custody à Incident Type
Priority Level should be a drop box with the following categories:
Priority One
Priority Two
Priority Three
Incident Type will be a drop box of the same list I gave you (that is listed on the screenshot).
Please note that the list of incidents that I gave you is specifically for Priority One’s. We are not currently receiving Priority Two or Three’s (at least not yet due to capacity). I imagine some of the categories will change for the lower priority levels, but I could get you that list so we can add in Priority Two’s and Priority Three’s at a later time? Let me know if it makes more sense to give it to you sooner.

Open Questions
-> Mockups for displaying these fields on the case details page  @kjonesthoughtworks

For the priority reasons dropdown, it should also allow you to write in text in case you need to add other values.

Hawaii Staging
https://github.com/PublicDataWorks/complaint-manager/assets/134408135/487540d9-5695-451a-bcdd-73d89a175477

NO Staging
https://github.com/PublicDataWorks/complaint-manager/assets/134408135/f9671141-7b84-44df-abb2-4145f8a1a725


peer dependencies

isn't better to put trpc and uwebsockets as peer dependencies and allow ranges of versions?

Yes indeed. I'm not that super familiar with all these ecosystem specific features, kind of afraid to break things.
But there was a "major" change in uWebsocketsjs quite recently. It allowed to store data on per-socket basis inside the uwebsockets itself. The subscription code now depends on it.
What are the steps to properly indicate that, with peer dependencies?

storing data on per-socket basis was always here but not fully typed and documented, there is no breaking changes for that.
for peer dependencies we can't put logical OR operator like this for example:
"the-dependency": "^0.1.0 || ^1.0.0-next.1"


Abt LLM inference

Hello thnx for the great work! ı am really excited to use it. I wanted to ask is there a way to make inference with a private llm server. I m using vLLM openai compatible server.
Thnx in advance

@emreekmekcioglu1  You can use openai as provider, it should work
graph_config = {     "llm": {         "api_key": "some dummy key",         "model": "openai/your_model_name",         "base_url": "your server IP"     },    ... }


Customize klusterlet namespace from klusterletConfig

/lgtm
/hold
/cc @elgnay @zhiweiyin318

/lgtm

before we merge this, do we also need to update mce installer with updated CRD at first @elgnay

before we merge this, do we also need to update mce installer with updated CRD at first @elgnay

Yes, we cannot merge this PR until the KlusterletConfig API is updated in the backplane-operator repo.

/unhold


Add Helix editing mode

Hi folks :wave:
I'm opening up a draft PR even though it's not anywhere near done to get some early feedback as it's quite a big change. If this eventually lands it should fix #639 . Very open to feedback from others, but currenly my plan of action is broadly:

[x] duplicate vi mode and rename it to hx mode
[ ] flip grammar structure
[ ] adjust keybindings to use what helix has
[ ] implement selection highlighting (optional)
[ ] cleanup/polish

I'm putting the selection highlighting as optional even though it's actually quite a core component of the helix model (it's actually why the grammar got flipped, so you can see what you're making adjustments on) mostly because I have no idea how attanable it is, and small steps and all that.
Looking forward to you feedback!

I know there have been quite a few people ask about helix mode, but this is quite ambitious. You might want to start with the founding principle of helix which is selection and just create a PR that allows one to do selection with keybindings. e.g. switch into selection mode, use left, right arrow keys to start and stop selection, switch out of selection mode, or something like that.
Once we have a selection mode, it seems like this PR is possible, but not really until that. Just my opinion though.

I think that is a good point actually. I'm barely a hop, skip and a jump into the implementation and it's already becoming quite clear that it makes very little sense to work on this without having some kind of selection mechanism in place. The one thing I'm not quite sure of yet, is how these selections may or may not interact with Vi and/or emacs mode.

I think that is a good point actually. I'm barely a hop, skip and a jump into the implementation and it's already becoming quite clear that it makes very little sense to work on this without having some kind of selection mechanism in place. The one thing I'm not quite sure of yet, is how these selections may or may not interact with Vi and/or emacs mode.

Thank you for immediately giving this a shot and laying out a strategy to approach that. I really appreciate that.
I want to be honest, why I have some concerns about landing this feature right now and why I think there should be a pretty high bar for an additional edit mode.
While our "emacs"-like mode is pretty flexible and open for configuration the existing "vi"-mode is pretty hacky through reusing the same operations internally.
It has thus not only missing features (e.g. glaringly no visual mode, missing text objects) but also major deviations from expected behavior (read bugs). Some of them could be overcome in the existing framework by tweaking those EditCommands but for others the complexity cost would be lower if we rework some of those things in terms of ranges/spans/selections.
A good example for the former is #631 (where I owe @alsuren a test/review cycle). When we make those changes for/from the established edit modes this will either cost you some rebases in this branch or all other contributors new things to watch out for in the helix mode as soon as it lands.
In the context that we currently both have some severe deficit in end to end UI tests that can reliably catch complex regressions and are understaffed in terms of technical maintainers steeped in reedline I don't want to disappoint expectations/ambitions.
The primary goal for reedline in the context of Nushell aiming for 1.0 will be to become reliable in behavior and settled in terms of existing configuration points. Under those constraints, giving more attention to the modes that have orders of magnitude more users or contributors familiar with them is obvious.
Nevertheless if this effort gets us incrementally closer to a simpler more maintainable and reliable core I don't want to rule this out (despite my bias of having no experience with the kakoune or helix flavored bindings)

So to make sure I've understood you correctly i'm going to try and summeraise your main points (feel free to point out any missunderstandings)

editing modes like vi-mode have deficiencies that need attention
vim has orders of magitude more users, therfore it makes sense to tempt them over by improving vi mode
the UI side is understaffed both in terms of infra and maintainers so we don't want to add more complexities

The conclusion you didn't mention explicity but I deduce from this is "we should not be doing this right now".
(this is the jist of what I understand)
Assuming I understood correctly some responses below, but tl;dr is: that's valid, I agree and if not now, then when?
So firstly, you say "landing this feature right now" (no sarcasm intended) but this feature is not, nor do I expect it to be any time soon, anywhere near ready. I definitely agree that the bar for entry should be high. A crappy implementation would hurt both Nu and Helix (imo). So I did not expect to land this anytime soon, or without any discussion, I kinda just jumped in head first. As an extention of that, discussions like these are exactly why I opened a PR before doing any significant work, so I'm glad we're having this discussion.
Secondly, as @fdncred mentioned and I recently found out, it really doesn't make sense to try and implement any of the helix bindings without having a mechanism for selections.  This is something you mentioned could also benifit emacs and/or vi mode so working on that first would be good for everyone.
Lastly, as to the fate of this PR. I think we all seem to be in agreement that it doesn't make sense to continue this at this moment, but I do have hope for a helix mode some day. I can leave it open as I do still think the approach is valid, even if it is currently blocked. I can see arguments both for leaving it open, or closing it and opening a new one when the time is right. I'm happy to defer to others on that front. Though I will also say, that if we're going to close this, I hope we can come to at least some agreed criteria for when it makes sense to open it back up, but stuff is hard so I fully accept the answer to that might be ¯_(ツ)_/¯
Thoughts?

I think what I would gather as a reasonable point where it makes sense to go ahead with helix mode without impacting the effort to getting the rest of the modes nice would be:

We have maybe reduced the number of EditCommand implementations that do essentially the same in slight variations: Move/Cut/Delete: https://github.com/nushell/reedline/blob/b1344f6a653b7c37154a1dd79b3c4e34afe6cfc9/src/core_editor/editor.rs#L43-L98
We have a selection implementation in at least one of the existing modes (be it visual mode for vim or Shift-Arrow for the non modal emacs-like mode)
We are happy with how you configure movements that can affect both the buffer and the general UI (e.g. up/down for history, completion or other menus) We currently have this UntilFound logic that has some implicit rules in how you need to order things and has some edge cases (multiplier motions in vi, left and right movements while in the history scrollback). This is not super critical for the helix implementation concerns itself but I think it makes sense that we have some clarity in how things should be configured on the nushell side so we can drop helix mode in when it is ready (potentially after we stabilize a config format for 1.0)

Sounds like a good conclusion to me, and it seem like we're on the same page. Given that you didn't express a preference for either closing the PR or keeping it I think I'll be closing it to avoid having to do rebase work down the line. Once the time is there it makes more sense to revaluate if the approach even makes sense. Thanks for the good discussion!

Thank you for being proactive here!


Check location service on Android

Resolves https://github.com/cds-snc/covid-alert-app/issues/891
How to test

Open the app, pass onboarding flow and enable EN.
Verify CovidAlert is active.
Go to device settings, disable location.
Back to the app, verify CovidAlert is inactive.
Turn on EN in the app, verify that location is enabled.
Turn off bluetooth.
Back to the app, verify CovidAlert is inactive.
Turn on EN in the app, verify that bluetooth is enabled.
Keep the app in foreground, toggle Location off in notification bar (not system settings), verify that the app change status properly.

Checking now

Ready for reviewing

I followed the testing steps on my Android device and it all looks good to me. Successfully logged out the system status as location_off. I couldn't test turning off location from the top menu though since I don't have it - maybe it was introduced after Android 7.1?
I am seeing the fall through "Something went wrong" screen now when location is off (as expected since we are not handling this state yet):

We need to show the user something more like the ExposureNotificationsDisabledView, with a button to turn on the framework. I think we can move the android location specific content there but I will check w/ @katewilhelm.
I think this is good to go but probably we should wait to merge until we have that new screen set up. What do you think @timarney?

Yes we'll hold until next week.

@timarney Did you do yarn to install the react-native-system-setting patch again?

Will check priority is https://github.com/cds-snc/covid-alert-app/pull/909 this A.M

@henrytao-me
yes
[1/4] 🔍  Resolving packages...
success Already up-to-date.
$ patch-package
patch-package 6.2.2
Applying patches...
<EMAIL_ADDRESS>✔
<EMAIL_ADDRESS>✔
✨  Done in 1.55s.

I just rebased master and gate location permission for Android only. The quick control for location works for me too. 🤔

@timarney @henrytao-me I've added the new screen: https://youtu.be/_g_Q-m8pXtY

This is on hold for now.

 More specific screen for "Your location is off"

@jeberhardt please give this a test.  Last time I tested it was working but ended up in out build back log.
Looking to confirm this is good to go when we're ready to include it.

Retested this
This should be rolled in with a release including
https://github.com/cds-snc/covid-alert-app/pull/934

@smcmurtry you might want to re-test this as well to confirm it landing on the right page.
Mostly around this part.
https://github.com/cds-snc/covid-alert-app/pull/892/files#diff-bb2a692e69dc457e8a5d5757bdaf9a3bR86

Will use the replacement branch https://github.com/cds-snc/covid-alert-app/pull/1045


NO-ISSUE: Add support for cachi2 based deps in Dockerfile.art

See https://github.com/openshift/etcd/pull/294 for Dockerfile.installer.art migration.
Konflux is replacing RH's internal build system OSBS. OSBS supported a build-time dependency injection system called "cachito". Konflux replaces this with "cachi2" which works differently. REMOTE_SOURCES no longer need to be copied into place and there is no need to source cachito's environment information (Konflux automatically rewrites the Dockerfile to source cachi2/cachi2.env before running the original RUN commands).
Additionally, cachito appears to have provided go.sum dependencies whereas cachi2 requires all build-time dependencies in go.mod. Missing dependencies are added to go.mod as // indirect in this change.

/retest

/cc @Elbehery

/test

/test ci/prow/e2e-aws-etcd-recovery

/test e2e-aws-etcd-recovery

/lgtm

/override ci/prow/configmap-scale


Appium server 0.0.5 - support Appium v2

What to do if the build fails?
At the moment contributors do not have access to the CI workflow triggered by StepLib PRs. In case of a failed build, we ask for your patience. Maintainers of Bitrise Steplib will sort it out for you or inform you if any further action is needed.
New Pull Request Checklist
Please mark the points which you did / accept.

[x] I will not move an already shared step version's tag to another commit
[x] I read the Step Development Guideline
[x] I have a test for my Step, which can be run with bitrise run test (in the step's repository)
[x] I did run bitrise run audit-this-step (in the step's repository - note, if you don't have this workflow in your bitrise.yml, you can copy it from the step template.)
[x] I read and accept the Abandoned Step policy

The step icon needs to be located at , not in the Step source repo.


Tray icon not updating after resuming devise from hibernation

After exiting hibernation mode, the tray icon is not updated. The percentage, font and font size are not updated.

Yes. I have seen the same issue in the latest version 2.1.5 . Please see the below screenshot for reference.

I also have the same issue.
OS Name	Microsoft Windows 11 Home Single Language
Version	10.0.22631 Build 22631
System Model	Aspire A515-45
Processor	AMD Ryzen 5 5500U with Radeon Graphics, 2100 Mhz, 6 Core(s), 12 Logical Processor(s)
BIOS Mode	UEFI
Installed Physical Memory (RAM)	16.0 GB
Total Physical Memory	15.4 GB
Available Physical Memory	2.79 GB

same issue. resetting to default or restarting the app helps. maybe we can update the code to check if there was a resume from hibernation event

Hey guys, thank you for reporting the issue.
When this happens, can you go to the "About" page and see if there's a warning displayed there? If you do, please click the copy button and paste the full error details here for further investigation.
Thanks.


GitHub OAuth Login Failure - Too many Redirs

via ads paid here http://prntscr.com/batkz4

thanks for reporting this @NDuma  - currently this feature assumes that if you've logged into github that you should be allowed access to the demo ( this is not the case )
I'll be addressing this problem by automatically granting the correct github permissions for any user to login

Shifting work to the python version of the appserver, will re-implement authentication as described in this ticket as part of that project.
see updated project here: https://github.com/bitwrap/bitwrap-io


Fix docs typo

Thanks for working on sailfish!
This just fixes a small typo in the getting started docs.

Thank you, so obvious but I wasn't aware of that.


RecursionError in generated Python parser

The test corpus contained a case where  function is called with many (over 255) arguments, each just numbers. This used to be a syntax error in 3.6 and before -- but with more recent versions of the bytecode compiler it works for 10s of 1000s of arguments.
However, the generated parser in Python cannot handle it! It raises a RecursionError for A(0, 1, ..., k) if k is 221 or higher. The traceback seems to be an endless repetition of this fragment:
  File "/Users/guido/pegen/data/python_parser.py", line 5512, in _tmp_108
    if (literal := self.expect(",")) and (c := self.args()):
  File "/Users/guido/pegen/pegen/parser.py", line 65, in memoize_wrapper
    tree = method(self, *args)
  File "/Users/guido/pegen/data/python_parser.py", line 3041, in args
    if (a := self.named_expression()) and (b := self._tmp_108(),):
  File "/Users/guido/pegen/pegen/parser.py", line 65, in memoize_wrapper
    tree = method(self, *args)

I think this is actually about this rule:
args[expr_ty]:
    [...]
    | a=named_expression b=[',' c=args { c }] {
        [...] }

The part [',' c=args {c}] corresponds to _tmp_108. This is a straightforward recursion (not left-).
I can't actually fathom that the C parser doesn't segfault on this for me; it just slows down. (In the C code, it's _tmp_109, but the structure is the same.) The stack must automatically grow (on Mac, at least). But even there it would be nice if we could replace this by a simple loop.
E.g. maybe we could make this work?
args[expr_ty]:
    | a=starred_expression b=[',' c=args { c }] {
        _Py_Call(_PyPegen_dummy_name(p),
                 (b) ? CHECK(_PyPegen_seq_insert_in_front(p, a, ((expr_ty) b)->v.Call.args))
                     : CHECK(_PyPegen_singleton_seq(p, a)),
                 (b) ? ((expr_ty) b)->v.Call.keywords : NULL,
                 EXTRA) }
    | a=kwargs { _Py_Call(_PyPegen_dummy_name(p),
                          CHECK_NULL_ALLOWED(_PyPegen_seq_extract_starred_exprs(p, a)),
                          CHECK_NULL_ALLOWED(_PyPegen_seq_delete_starred_exprs(p, a)),
                          EXTRA) }
    | ','.(named_expression !'=')+ { XXX }

I haven't figured out what should go into XXX yet, but it's probably going to be more efficient, since we don't build up the array of arguments by prepending one at a time.

(Oh, I tried, and that doesn't actually work even for the Python parser. But why? @lysnikolaou any idea?)

I tried this and it works... Now for filling in XXX...
args[expr_ty]:
    | ','.(starred_expression | named_expression !'=')+ [',' kwargs] { XXX }
    | a=kwargs { _Py_Call(_PyPegen_dummy_name(p),
                          CHECK_NULL_ALLOWED(_PyPegen_seq_extract_starred_exprs(p, a)),
                          CHECK_NULL_ALLOWED(_PyPegen_seq_delete_starred_exprs(p, a)),
                          EXTRA) }

Here is a draft implementation:
https://github.com/python/cpython/pull/22053
For this script:
import ast

code = "f(" + ",".join(['a' for _ in range(100000)]) + ")"
print("Ready!")
ast.parse(code)

I get these results (release mode):
This patch:  0.17s +- 0.04

Python3.8:  0.27s +- 0.08

Master:
[1]    78689 segmentation fault (core dumped)  ./python lel.py


PyAV 8.1.0 wheel fails to open a x11grab device

Overview
In PyAV 8.1.0 wheel, av.open() fails when a x11grab device is opened.
Expected behavior
It should succeed.
Actual behavior
A ValueError saying "no container format 'x11grab'" is raised.
Traceback:
Traceback (most recent call last):
  File "t.py", line 4, in <module>
    con = av.open(os.environ['DISPLAY'] + '.0', mode = 'r', format = 'x11grab',
  File "av/container/core.pyx", line 354, in av.container.core.open
  File "av/container/core.pyx", line 132, in av.container.core.Container.__cinit__
  File "av/format.pyx", line 90, in av.format.ContainerFormat.__cinit__
ValueError: no container format 'x11grab'

Investigation
It worked at least on PyAV 8.0.2. I guess that ffmpeg libraries(libavformat, libavdevice, ...) included in the wheel was not compiled with x11grab support. I noticed that python3 -m av --version says explicitly --disable-libxcb. I wonder if that's an intentional one. If it is, IMHO it would be better to be mentioned on the installation instruction.
Reproduction
Run the following test code.
import os
import av

con = av.open(os.environ['DISPLAY'] + '.0', mode = 'r', format = 'x11grab',
	options = {'video_size': '640x480', 'framerate': '30'})

Versions

OS: Ubuntu 20.04
PyAV runtime:

PyAV v8.1.0
git origin: git@github.com:PyAV-Org/PyAV
git commit: v8.1.0
library configuration: --disable-doc --disable-libxcb --disable-static --enable-fontconfig --enable-gmp --enable-gnutls --enable-gpl --enable-libaom --enable-libass --enable-libbluray --enable-libdav1d --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libwavpack --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libxvid --enable-lzma --enable-shared --enable-version3 --enable-zlib --prefix=/tmp/vendor
library license: GPL version 3 or later
libavcodec     58. 91.100
libavdevice    58. 10.100
libavfilter     7. 85.100
libavformat    58. 45.100
libavutil      56. 51.100
libswresample   3.  7.100
libswscale      5.  7.100

PyAV build:

N/A(wheel binary)

FFmpeg:

N/A(wheel binary)

Research
N/A
Additional context
N/A

Wow I didn't know that you are also a PyAV developer. Thanks for your hard work.
Can you explain more on the situation? I want to know if I can help.
I have no experience on building a python wheel.
I found that av 8.0.3 wheel was built on manylinux2010 with xcb enabled and av 8.1.0 wheel was built on manylinux2014 with xcb disabled.
Is that mean, manylinux2010 provides libxcb binary but manylinux2014 does not?
I read manylinux2014 is based on CentOS 7. Then why the libxcb binary in the CentOS 7 repository cannot be used?


Do not write the default config schema into injectable configs

Since it's doing nothing.

Actually do write it, cos it makes component reading much easier.


Switch to contact:

Switched 3 field to contact: schema
this fix #3915 unless I've forgot others...

I do appreciate you wanting to improve the tag situation, but it would be irresponsible to deprecate the old contact tags that are in much wider use, just based on what the osm wiki says.
https://github.com/openstreetmap/iD/issues/3915#issuecomment-287945284


Burns cycles doing MD5 checksums on files I've never accessed

I lost my logs so I can't post them here but what I was seeing was a CPU core getting eaten up by gdfuse doing md5 checksums on cache entries for files I've never navigated to. Large video files.
Those files don't really need to be accessible nor cached so I added the stream large files option and I've moved my directory structure around and used the new root folder option to only include data I care about so this may not happen again. If it does, I'll post here. Is there a scheduled task to generate md5 sums and it was just taking a really long time?

Is there a scheduled task to generate md5 sums and it was just taking a really long time?

No, md5 checksum is recalculated only before downloading, to check if the cached copy is still synchronized. Maybe the Drive API was returning that those files have been modified (maybe just metadata) and that triggered downloading those files again.

Ok. So there's still problems. My curl log is 11G overnight gdfuse.log is 124M overnight. I'm going to turn off the curl logging. It also allocated 1.1GB of virt memory and filled my swap. I'm going to restart this and start logging the gdfuse.log growth to see if I can identify if it correlates with any access I'm doing.
Sorry for the running commentary. I'll try and catch it while it's being naughty and post some of the logs.

I solved this by using the setting the root folder as shown in the wiki: https://github.com/astrada/google-drive-ocamlfuse/wiki/Configuration


How to use Flask-CAS along with Flask-Appbuilder?

I want to add SSO to the Caravel witch is based on Flask-Appbuilder，How to combine them?

@Jackeriss I've implemented this you have to edit these three files:
/usr/local/lib/python2.7/dist-packagescaravel/config.py
/usr/local/lib/python2.7/dist-packages/caravel/init.py
/usr/local/lib/python2.7/dist-packages/flask_appbuilder/security/views.py
I can shoot you an email with the changes needed or you can wait until later and i'll create a repo and commit the files.

@jstevensfit Oh，thank you, you can email me at<EMAIL_ADDRESS>

@jstevensfit hi, i also need the code ,can you email me<EMAIL_ADDRESS>


best_practices: encourage use of pylint, six, and python-modernize

Add a section describing the Conservative Python 3 Porting Guide,
the python-futures Python 3 Compatibility Cheat Sheet, and the
python-modernize tool.
Recommend use of pylint --py3k.
Recommend use of six and python-modernize.
Add guidance for futurize and the python-future modules.
Signed-off-by: David Aguilar<EMAIL_ADDRESS>

Thanks for the review!  I added a note about pylint for projects that don't have tests and have adjusted the futurize links and recommendations as discussed.  Please see the latest pushed commit.

Regarding the usage of six, should we mention that DCCs might ship with an older version of six and that the DCC version will always be picked up? On the top of my mind there is Nuke and Houdini that both ship a quite old six version.
This has bitten RodeoFX quite a lot. RodeoFX contacted both vendors and their response was that they would fix it in their next major version. Though I don't know where they are at right now.

Regarding the usage of six, should we mention that DCCs might ship with an older version of six and that the DCC version will always be picked up? On the top of my mind there is Nuke and Houdini that both ship a quite old six version.
This has bitten RodeoFX quite a lot. RodeoFX contacted both vendors and their response was that they would fix it in their next major version. Though I don't know where they are at right now.

That's definitely been a problem for us as well. I think it's worth mentioning. Given the age of this pull request, I'm going to go ahead and merge this but I've made not of it as a point of discussion for the next meeting. Feel free to make a PR for this change ahead of time if you want.

That's definitely been a problem for us as well. I think it's worth mentioning. Given the age of this pull request, I'm going to go ahead and merge this but I've made not of it as a point of discussion for the next meeting. Feel free to make a PR for this change ahead of time if you want.

Perfect @AWhetter . I'll create a PR later today.

Perfect @AWhetter . I'll create a PR later today.


Add benchmarks for Sabre on large QFT and QV circuits

Summary
Sabre is capable of handling these large benchmarks now, and it's of interest for us to track our performance on large systems.  We don't anticipate running on them yet, but we will want to know in the future when further changes to routing and memory usage improve these benchmarks.

Details and comments
These could be in either mapping_passes.py or the files I've put them in.  It's not super clear where, but since I used the benchmark-internal constructors (to dodge issues with the Terra functions potentially changing in the future), it made some sense to put them in the structure-specific files.

Ah, I still have the output in the scrollback of my terminal (before I fixed the QFT generation):
ake@ninetales$ asv dev --python 3.10 -b 'LargeQ.*MappingBench.*time'
· Fetching recent changes
· Creating environments
· Discovering benchmarks
· Running 2 total benchmarks (1 commits * 1 environments * 2 benchmarks)
[  0.00%] · For qiskit-terra commit aab18fcd <main>:
[  0.00%] ·· Benchmarking virtualenv-py3.10
[ 25.00%] ··· Running (qft.LargeQFTMappingBench.time_sabre_swap--).
[ 50.00%] ··· Running (quantum_volume.LargeQuantumVolumeMappingBenchmark.time_sabre_swap--).
[ 75.00%] ··· qft.LargeQFTMappingBench.time_sabre_swap                                                                                2/6 failed
[ 75.00%] ··· ========== ============ ============
              --                 heuristic
              ---------- -------------------------
               n_qubits   lookahead      decay
              ========== ============ ============
                 115       404±40ms     380±9ms
                 409      6.59±0.08s   6.08±0.01s
                 1081       failed       failed
              ========== ============ ============

[100.00%] ··· quantum_volume.LargeQuantumVolumeMappingBenchmark.time_sabre_swap                                                                                ok
[100.00%] ··· ========== ================ ============ ================= =============
              --                               depth / heuristic
              ---------- -------------------------------------------------------------
               n_qubits   10 / lookahead   10 / decay   100 / lookahead   100 / decay
              ========== ================ ============ ================= =============
                 115        104±0.9ms      98.9±0.7ms       969±10ms        973±7ms
                 409        21.3±0.4s      7.09±0.03s         n/a             n/a
                 1081       59.1±0.2s       1.53±0m           n/a             n/a
              ========== ================ ============ ================= =============

I did a run locally, this adds ~30mins to local runtime (31:20.39 for my local asv run call without venv or build time) to the benchmarks for a commit. That's on the long side but considering we just reduced a lot of overhead from the assemble benchmarks and the importance of testing sabre at scale now I think that's ok. The results from my local run were:
[ 58.33%] ··· qft.LargeQFTMappingBench.time_sabre_swap                        ok
[ 58.33%] ··· ========== ============ ============
              --                 heuristic
              ---------- -------------------------
               n_qubits   lookahead      decay
              ========== ============ ============
                 115       307±1ms     296±0.9ms
                 409       4.93±0s     4.73±0.01s
                 1081     43.1±0.05s   40.6±0.05s
              ========== ============ ============

[ 66.67%] ··· qft.LargeQFTMappingBench.track_depth_sabre_swap                 ok
[ 66.67%] ··· ========== =========== ========
              --              heuristic
              ---------- --------------------
               n_qubits   lookahead   decay
              ========== =========== ========
                 115         3834      2980
                 409        26641     25214
                 1081       150404    120263
              ========== =========== ========

[ 75.00%] ··· qft.LargeQFTMappingBench.track_size_sabre_swap                  ok
[ 75.00%] ··· ========== =========== =========
              --               heuristic
              ---------- ---------------------
               n_qubits   lookahead    decay
              ========== =========== =========
                 115        19670      18634
                 409        269456     263765
                 1081      2043833    1959761
              ========== =========== =========

[ 83.33%] ··· ...uantumVolumeMappingBenchmark.time_sabre_swap                 ok
[ 83.33%] ··· ========== ======= ============ ============
              --                         heuristic
              ------------------ -------------------------
               n_qubits   depth   lookahead      decay
              ========== ======= ============ ============
                 115        10    83.5±0.9ms   80.7±0.8ms
                 115       100     816±20ms     799±3ms
                 409        10    18.1±0.02s   5.95±0.02s
                 409       100       n/a          n/a
                 1081       10    49.1±0.2s     1.28±0m
                 1081      100       n/a          n/a
              ========== ======= ============ ============

[ 91.67%] ··· ...olumeMappingBenchmark.track_depth_sabre_swap                 ok
[ 91.67%] ··· ========== ======= =========== =======
              --                      heuristic
              ------------------ -------------------
               n_qubits   depth   lookahead   decay
              ========== ======= =========== =======
                 115        10       563       506
                 115       100       5563      5274
                 409        10       4371      3676
                 409       100       n/a       n/a
                 1081       10      13996     12841
                 1081      100       n/a       n/a
              ========== ======= =========== =======

[100.00%] ··· ...VolumeMappingBenchmark.track_size_sabre_swap                 ok
[100.00%] ··· ========== ======= =========== ========
              --                      heuristic
              ------------------ --------------------
               n_qubits   depth   lookahead   decay
              ========== ======= =========== ========
                 115        10       4511      4286
                 115       100      44748     44298
                 409        10      72015     60308
                 409       100       n/a       n/a
                 1081       10      244513    296402
                 1081      100       n/a       n/a
              ========== ======= =========== ========

My hope is that Qiskit/qiskit-terra#9012 will (in fairly short order) knock off a good amount of that time again, and make the cost something more like 10-15 minutes on a run.


_workflow1.R runtime error

if i modify _workflow1.R to use pandabob.txt instead of the CondorFull.csv, then i get a runtime error:
[...]
	Processing move step 145 of 146
	Processing move step 146 of 146
	Maximum voxel density = 0
	Sum of voxel densities = 0
2D MKDE Computation: DONE
[1] "First raster"
Error in image.default(mkde.obj$x, mkde.obj$y, dens.dat, breaks = cont.vals$threshold,  :
  increasing 'x' and 'y' values expected

After some debugging, it appears that xmin <- min(data$xdata) throws a runtime error however ymin <- min(data$ydata) is fine!  From my debugging using pandabob.txt, data$xdata is numeric, while data$ydata is integer...not sure if that explains the problem and a check of min() function suggests that it should be able to handle both types...what's also weird is that if i test using CondorFull.csv, both data$xdata and data$ydata are numeric but "xmin <- min(data$xdata)" still throws an error!

This was a pretty easy fix. The cell size that I use for the condor data is way too large for the pandabob.txt data. So replace "cell.sz <- 3000" with "cell.sz <- 30" in line 12 when working with the panda data.
Btw, xmin <- min(data$xdata) does NOT throw an error for me with the condor data


Add clippy pedantic rules & update all dependencies.

Fix typos as wel.

I don't like pedantic rules since it increases visual noise.
Most of the changes are stylistic rather than critical.
Also, It would be better if changes were in neatly separated commits.
Dependencies are updated in #214, so rebase is needed.


raise numpy error

In numba 0.22.1,
raise np.linalg.LinAlgError

worked fine, but with 0.23 I get the following:
NotImplementedError: raise $61.3

Failed at nopython (nopython frontend)
raise $61.3

Full traceback: https://gist.github.com/zoeith/a9a4376a431dae50d4ea
I got a slightly different error while trying to put together an mwe...
NotImplementedError: raise $12.3

Failed at nopython (nopython frontend)
raise $12.3

Here's the original function and mwe attempt: https://gist.github.com/zoeith/0c1438486bfd031b39d0

This can be easily worked around using from numpy.linalg import LinAlgError and then (inside your function) raise LinAlgError.
I'd rather not fix this before the refactor in PR #1622 is merged, as that requires touching the same internal mechanism (constant inference).

OK, we'll address this bug in the Numba 0.24 release in February, but not put this into the bug fix 0.23.1 release happening this week.


visibility information missing from TypeInfo for structs & enums causing broken links in forc doc

I'm wondering if adding visibility to the TypeInfo for structs and enums would be acceptable. It would make determining if a type should get an anchored link possible since private items aren't documented by default. Ref #4017 running forc doc --open will produce broken links for fields with types that are private since the documenter won't produce the actual page the link goes to.

Another way I might be able to do this is to create blank pages in the documenter that say "This type is private" but this would mean there would be a page for every private item.

Also open to other options, maybe there's something better to use than TypeInfo here but the only thing I have at that point in the code is the TypeId. cc @mohammadfawaz @emilyaherbert if you have any tips

Closing since #3744 will add the DeclId to TypeInfo which will make the visibility available


Distance analyzer for detecting feature drift with PyDeequ

Is your feature request related to a problem? Please describe.
It looks like in PyDeequ 1.1.1 the Deequ distance analyzer is not available. It means that this type of analyzer cannot be run via PyDeequ.
Describe the solution you'd like
I'd like to run the distance analysis on my data, so that I can detect feature drift via the 2 methods currently available in Deequ (L-infinity and chi-squared). I'd like to be able to do this in the same way as with the other analyzers.
Are there any plans to add this analyzer in the future?
Describe alternatives you've considered
I've read the documentation, but couldn't find anything related to the distance analyzer.
As a hacky workaround, I experimented with invoking the numericalDistance() method directly with Py4J, but found that instantiating a Scala object of QuantileNonSample[Double] doesn't seem to be a straightforward thing to do in Python.

Mark as a feature request.

Also it shouldn't be too hard to add a new analyzer - see existing pattern here https://github.com/awslabs/python-deequ/blob/e74e974e739f24cccb827a6378cd50e97697a0e8/pydeequ/analyzers.py#L191

Maybe I can work on this to start contributing with the lib guys.
@thuber (or maybe even @chenliu0831) can you give me an usage example of the  Deequ Distance  Analyzer ?

Hi @peixeirodata, from what I can tell, usage of the distance analyzer isn't particularly well documented. The most useful reference I found is actually the unit tests for the class.
Some Pointers to Start with
If you want to look into it, I can provide some pointers of what I learned while looking into it.
As it turns out, the Distance.scala class doesn't follow the same pattern as the other analyzers, in that it just defines a regular Scala object that doesn't inherit any traits.
The method I would want to invoke for detecting feature drift of non-categorical features is numericalDistance(). This function has the following signature:
def numericalDistance(
    sample1: QuantileNonSample[Double],
    sample2: QuantileNonSample[Double],
    correctForLowNumberOfSamples: Boolean = false,
    alpha: Option[Double] = None
): Double

So in order to invoke this method, we would need to create two instances of QuantileNonSample[Double] in Python, one for the reference data set and one for the current data set. The signature of the constructor of the class is:
class QuantileNonSample[T](
    var sketchSize: Int,
    var shrinkingFactor: Double = 0.64)
    (implicit ordering: Ordering[T], ct: ClassTag[T]
) extends Serializable

Here is where I stopped looking into it, because the way I read it, we would have to somehow instantiate two instances of this Scala class in Python using a library called Py4j. The challenges I see are:

How to instantiate a Scala class that uses generics using Py4j
How to pass implicit parameters
How to obtain and pass the ordering and class tag of the type parameter

These questions may have obvious answers, but I am by no means an expert on how to do the above using Py4j and am hence not able to easily figure out the answers. Especially since it seems like Py4j wasn't really designed to support more advanced Scala concepts like class tags.

Hi @thuber,
Thank you for your observations! I started to create some implementation to the numericalDistance and categoricalDistance here (fell free to tell me your thoughts about it).
As this Distance class in Scala is quite different from the other analyzers, I'd be glad if someone could provide me an example of these methods just to try to use the same approach when testing the Python version.

@peixeirodata feel free to open a draft PR for discussion


Query & Update Tables

Added a column species of type string to the animals table. Modified the schema.sql file.
Inserted the given data to data.sql
Inside a transaction updated the animals table by setting the species column to unspecified. Verified that the change was made. Rolled back the change.
Inside a transaction:

Updated the animals table by setting the species column to digimon for all animals that have a name ending in mon.
Updated the animals table by setting the species column to pokemon for all animals that don't have species already set.
Verified that changes were made.
Committed the transaction.
Verified that changes persist after commit.

Inside a transaction:

Deleted all records in the animals table, then rolled back the transaction.
After the rollback verified all records in the animals table still exists.

Inside a transaction:

Deleted all animals born after Jan 1st, 2022.
Created a savepoint for the transaction.
Updated all animals' weight to be their weight multiplied by -1.
Rolled back to the savepoint
Updated all animals' weights that are negative to be their weight multiplied by -1.
Committed transaction

Wrote queries to answer the following questions:

How many animals are there?
How many animals have never tried to escape?
What is the average weight of animals?
Who escapes the most, neutered or not neutered animals?
What is the minimum and maximum weight of each type of animal?
What is the average number of escape attempts per animal type of those born between 1990 and 2000?


runtime: changing runtime features to be ABSL_FLAGs based

Risk Level: high
Testing: existing tests cover
Docs Changes: n/a
Release Notes:
Fixes https://github.com/envoyproxy/envoy/issues/19847
Part of https://github.com/envoyproxy/envoy-mobile/issues/2003

BTW: will it be possible to add the absl flags usage example into test/common/runtime/BUILD?

"BTW: will it be possible to add the absl flags usage example into test/common/runtime/BUILD?"
I don't think so.  we're not parsing command line flags, just using them for storage.

One line patch change
/lgtm deps

CI sorted, ptal!


Commit creation on pr error when using v0.24.0

Describe the bug
When use v0.24.0 to create commit to a pr, 404 error is occurred.
But when i downgrade it to 0.23.5, it's runnable.
Seems like it is related to the empty commit skipped mentioned in #1411, this url is double quoted: https://huggingface.co/api/datasets/narugo/sample_tars/revision/refs%252Fpr%252F2
Reproduction
import os

from huggingface_hub import HfApi, HfFileSystem, CommitOperationAdd

hf_client = HfApi(token=os.environ['HF_TOKEN'])
hf_fs = HfFileSystem(token=os.environ['HF_TOKEN'])

repo = 'my/dataset_repo'
pr_id = 2

ref = hf_client.get_discussion_details(
    repo_id=repo,
    repo_type='dataset',
    discussion_num=pr_id,
).git_reference

# runnable on 0.23.*
# 404 error on 0.24.0, error message
# No files have been modified since last commit. Skipping to prevent empty commit.
# huggingface_hub.utils._errors.RevisionNotFoundError: 404 Client Error. (Request ID: Root=1-669fba92-11c9368a00e7f82e01e5c86e;c4a76daa-bbf7-41e3-8e27-ae75792a0db8)
# Revision Not Found for url: https://huggingface.co/api/datasets/narugo/sample_tars/revision/refs%252Fpr%252F2.
# Invalid rev id: refs%2Fpr%2F2
hf_client.create_commit(
    repo_id=repo,
    repo_type='dataset',
    revision=ref,
    operations=[],
    commit_message='Test Message',
)

Logs
Traceback (most recent call last):
  File "/home/narugo/wtf-projects/hfutils/venv/lib/python3.8/site-packages/huggingface_hub/utils/_errors.py", line 304, in hf_raise_for_status
    response.raise_for_status()
  File "/home/narugo/wtf-projects/hfutils/venv/lib/python3.8/site-packages/requests/models.py", line 1024, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 404 Client Error: Not Found for url: https://huggingface.co/api/datasets/narugo/sample_tars/revision/refs%252Fpr%252F2

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "test_x.py", line 53, in <module>
    hf_client.create_commit(
  File "/home/narugo/wtf-projects/hfutils/venv/lib/python3.8/site-packages/huggingface_hub/utils/_validators.py", line 114, in _inner_fn
    return fn(*args, **kwargs)
  File "/home/narugo/wtf-projects/hfutils/venv/lib/python3.8/site-packages/huggingface_hub/hf_api.py", line 1398, in _inner
    return fn(self, *args, **kwargs)
  File "/home/narugo/wtf-projects/hfutils/venv/lib/python3.8/site-packages/huggingface_hub/hf_api.py", line 3804, in create_commit
    info = self.repo_info(repo_id=repo_id, repo_type=repo_type, revision=revision, token=token)
  File "/home/narugo/wtf-projects/hfutils/venv/lib/python3.8/site-packages/huggingface_hub/utils/_validators.py", line 114, in _inner_fn
    return fn(*args, **kwargs)
  File "/home/narugo/wtf-projects/hfutils/venv/lib/python3.8/site-packages/huggingface_hub/hf_api.py", line 2588, in repo_info
    return method(
  File "/home/narugo/wtf-projects/hfutils/venv/lib/python3.8/site-packages/huggingface_hub/utils/_validators.py", line 114, in _inner_fn
    return fn(*args, **kwargs)
  File "/home/narugo/wtf-projects/hfutils/venv/lib/python3.8/site-packages/huggingface_hub/hf_api.py", line 2446, in dataset_info
    hf_raise_for_status(r)
  File "/home/narugo/wtf-projects/hfutils/venv/lib/python3.8/site-packages/huggingface_hub/utils/_errors.py", line 311, in hf_raise_for_status
    raise RevisionNotFoundError(message, response) from e
huggingface_hub.utils._errors.RevisionNotFoundError: 404 Client Error. (Request ID: Root=1-669fba92-11c9368a00e7f82e01e5c86e;c4a76daa-bbf7-41e3-8e27-ae75792a0db8)

Revision Not Found for url: https://huggingface.co/api/datasets/narugo/sample_tars/revision/refs%252Fpr%252F2.
Invalid rev id: refs%2Fpr%2F2

System info
- huggingface_hub version: 0.23.5
- Platform: Linux-5.15.0-116-generic-x86_64-with-glibc2.2.5
- Python version: 3.8.1
- Running in iPython ?: No
- Running in notebook ?: No
- Running in Google Colab ?: No
- Token path ?: /home/narugo/.cache/huggingface/token
- Has saved token ?: True
- Who am I ?: narugo
- Configured git credential helpers:
- FastAI: N/A
- Tensorflow: N/A
- Torch: N/A
- Jinja2: 3.1.2
- Graphviz: N/A
- keras: N/A
- Pydot: N/A
- Pillow: N/A
- hf_transfer: N/A
- gradio: N/A
- tensorboard: N/A
- numpy: 1.24.4
- pydantic: N/A
- aiohttp: N/A
- ENDPOINT: https://huggingface.co
- HF_HUB_CACHE: /home/narugo/.cache/huggingface/hub
- HF_ASSETS_CACHE: /home/narugo/.cache/huggingface/assets
- HF_TOKEN_PATH: /home/narugo/.cache/huggingface/token
- HF_HUB_OFFLINE: False
- HF_HUB_DISABLE_TELEMETRY: False
- HF_HUB_DISABLE_PROGRESS_BARS: None
- HF_HUB_DISABLE_SYMLINKS_WARNING: False
- HF_HUB_DISABLE_EXPERIMENTAL_WARNING: False
- HF_HUB_DISABLE_IMPLICIT_TOKEN: False
- HF_HUB_ENABLE_HF_TRANSFER: False
- HF_HUB_ETAG_TIMEOUT: 10
- HF_HUB_DOWNLOAD_TIMEOUT: 10

Thanks for reporting @narugo1992, this is indeed a bug. I just opened https://github.com/huggingface/huggingface_hub/pull/2413 to fix it.

Regarding your script, no need to pass token=os.environ['HF_TOKEN'] since HF_TOKEN environment variable is read by default. This is just a nit, not related to the issue :)

Thanks for reporting @narugo1992, this is indeed a bug. I just opened #2413 to fix it.

ohh, i just open a pr for this lol

@Wauplin btw, will #2413 be in version 0.24.1 or some other version? my library hfutils has dependency on huggingface_hub and this operation. if so i will use huggingface>=0.23,!=0.24.0 in new version.

@narugo1992 I just merged the PR and shipped huggingface_hub==0.24.2 patch release: https://github.com/huggingface/huggingface_hub/releases/tag/v0.24.2. Both 0.24.0 and 0.24.1 contain the bug you've reported.


Is this project dead completely?

Its seems that there is little response to any support issues raised on this project.
Is there any intent to keep this project going?
Do you need help with supporting this?
My company needs to supports keyboard navigation and high levels of accessibility so we see the value in a framework helping to manage that aspect. We are currently evaluating whether to continue to use this component, but if we cant get P.Rs accepted to fix bugs, its makes us unlikely to want to continue using it.
Would appreciate some information on where this repo is heading. If the burden of supporting this is to much we may fork this and enhance it internally. Thanks.

Sorry for the lack of response!
I've literally just landed after a prolonged holiday so have not been
watching any of the activity here over the past month or so. I will be
responding over the next couple of days and getting prs merged.
As for further contribution I will not have time to work on the proposed v1
Roadmap (mainly just modernising and consolidatiny apis) and welcome anyone
who wants to jump on that.
On 20 Jul 2016 21:42, "Colm"<EMAIL_ADDRESS>wrote:

Its seems that there is little response to any support issues raised on
this project.
Is there any intent to keep this project going?
Do you need help with supporting this?
My company needs to supports keyboard navigation and high levels of
accessibility so we see the value in a framework helping to manage that
aspect. We are currently evaluating whether to continue to use this
component, but if we cant get P.Rs accepted to fix bugs, its makes us
unlikely to want to continue using it.
Would appreciate some information on where this repo is heading. If the
burden of supporting this is to much we may fork this and enhance it
internally. Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/chrisui/react-hotkeys/issues/37, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA_oAItKZsnQZiSyYsI7b-I_j2nlQ83oks5qXoglgaJpZM4JRL65
.

Thanks Chris. Good to hear.

Done a clean of issues and pull requests. v0.9.0 is now published to npm and UMD build available from repo.
Thanks for a nudge! :)


[9.x] Restores original table name guessing for Morph Pivot model

What?
When calling a many-to-many relations using morph pivot model, the table that Laravel guesses is snake singular from the pivot model name. For example, "Taggable" will point to taggable instead of taggables.
use Illuminate\Database\Eloquent\Model;
use Illuminate\Database\Eloquent\Relations\MorphPivot;

class Post extends Model
{
    public function tags()
    {
        return $this->morphToMany(Tag::class, 'taggable', Taggable::class);
    }
}

class Tag extends Model
{
    // ...
}

class Taggable extends MorphPivot
{
    // ...
}

Post::find(1)->tags()->dd();

// "select * from "tags"
//    inner join "taggable" on "tags"."id" = "taggable"."tag_id"
//    where
//        "taggable"."taggable_id" = ?
//    and
//        "taggable"."taggable_type" = ?

This patch adds back the plural table name guesser to MorphPivot, which will point to the plural name of the model rather than a the singular snake (which doesn't make sense). It will also avoid the developer to set the table manually when is the plural of the model name.

Note I decided against removing the method from the AsPivot trait because it would break something, but it could be done for 10.x I supposse.

This doesn't affect monomorphic Pivot, as is inferred the developer is using the convention {Bar}_{Foo}, which if not it should point the table name manually.

@DarkGhostHunter please do not link to a issue and provide a thorough explanation in your PR description (see the PR template).

More info? When was this bug introduced? Tests?

Added info. Dunno when was introduced, I just picked it up yesterday when I saw failing queries on staging. Added Tests.

@DarkGhostHunter please do not link to a issue and provide a thorough explanation in your PR description (see the PR template).

// @see above

I don't think I want to change this now since it could break applications.

One workaround for now, is to call BelongsToMany@using on the relation definition, and don't pass the $table name argument as a FQCN:
class Post extends Model
{
    public function tags()
    {
        return $this->morphToMany(Tag::class, 'taggable')->using(Taggable::class);
    }
}

The relation above will generate a SQL query using the taggables table name for the pivot table, and the results will be hydrated into a Taggable class instance.
Also the behavior of allowing a FQCN into the $tableName parameter to automatically guess the pivot table name and set the pivot model is not documented (I learned it from this PR)
https://laravel.com/docs/9.x/eloquent-relationships#defining-custom-intermediate-table-models
One last thing you can try, is to explicitly set the Taggable class' $table property

When was this bug introduced? Tests?

It seems this bug is present since the beginning.
From looking into git blames on BelongsTo Many class and AsPivot trait, it seems passing a MorphPivot instead of a Pivot as the $tableName parameter was overseen.
I couldn't find no tests related on using a MorphPivot FQCN as the third parameter to define a relation, nor a test generating a SQL directly from a MorphPivot instance.
As this is not documented behavior, I would send it to master and add a note on the upgrade guide. I agree changing a behavior that was always present on a patch release seems not to be a good idea.

When was this bug introduced? Tests?

It seems this bug is present since the beginning.
From looking into git blames on BelongsTo Many class and AsPivot trait, it seems passing a MorphPivot instead of a Pivot as the $tableName parameter was overseen.
I couldn't find no tests related on using a MorphPivot FQCN as the third parameter to define a relation, nor a test generating a SQL directly from a MorphPivot instance.
As this is not documented behavior, I would send it to master and add a note on the upgrade guide. I agree changing a behavior that was always present on a patch release seems not to be a good idea.

I agree. This should be documented for the next version because it was never clear.


Update exometer_core to 1.5 and adjust readme instructions

This updates exometer_core to 1.5 and updates the readme to point to the current repo for exometer_core.
Also, tangentially, are y'all planning on pushing a new build to hex sometime soon? If not, is there anything I can help with to get one out? Last time this was updated there was 2016.
Note: I can undo the formatting changes but it's just from mix format.
Update: It's failing CI on Elixir 1.3, I've updated it to be at least 1.4, any chance we could make that change? Elixir 1.3 is over two years old at this point.
Also this fixes #98

Unfortunately we also need to support 1.3 as we use that version with certain systems in production.

Closing in favor of #121


Is it possible to check if an adapter as already been registered?

Question
I am using Hive as local storage in my architecture template project and I am running into a problem where i try to register an adapter twice.
Code sample
hive.registerAdapter<PostH>(PostHAdapter());

Is it possible to check before registration?
if(!hive.isAdapterRegistered(PostHAdapter()){
    hive.registerAdapter<PostH>(PostHAdapter());
}

Currently I have to be safe and catch the double registration error
try {
    _hiveService.registerAdapter<PostH>(PostHAdapter());
} on HiveError {}

Version

Platform: iOS, Android
Flutter version: [1.12.13+hotfix.7]
Hive version: [1.3.0]

Fixed this by registering the adapters in the main function, which only registers once.


Clarify whether the “Other Endpoints” section is meant to include COVID + other diseases, or just other diseases

In the docs pages, are “Other Endpoints” meant to be COVID + other diseases or just other diseases? The description page seems to contradict what is noted in left side menu:

The "covidcast" endpoint provides some information relating to flu (and some other things that arent covid as well), and the other endpoints do provide some covid information too...  "covidcast" will get renamed/rebranded in the not-too-distant future, but for now, the title of "Epidata API (Other Diseases)" would best be changed to match the text in the sidebar.  The sentence you underlined can probably be removed unless you have an idea for changing it to be something more accurate.


last index of number in an array

Given an array of length N and an integer x, you need to find and return the last index of integer x present in the array. Return -1 if it is not present in the array.
Last index means - if x is present multiple times in the array, return the index at which x comes last in the array.
You should start traversing your array from 0, not from (N - 1).
Do this recursively. Indexing in the array starts from 0.
Programming language

[ ] C
[ ] C++
[ ] Java
[ ] Python

can I try this in c++

Can I try in python

Please assign me this issue under LGM-soc21. I will like to contribute the code in C.

can i try this in Java or c+?