Cannot use Verson 3.0 because I cannot rebuild the library

Although the Installation APPEARED to work on Delphi 11 running on a Win 10 Machine, I needed to recompile a library that subclasses some Skia based components and when I did so and tried to install it I got an access violation in the BDS.
I then tried to open the FMX Package and rebuild/install it and I get an access violation again, in the BDS.exe
It builds fine, I just can't install it so until this can be resolved, I'm going to have to go back to the prior version.
(44C08E80){bds.exe     } [44C09E80]
[5006B652]{rtl280.bpl  } SysInit.@GetTls (Line 835, "SysInit.pas" + 23) + $0
[500614A1]{rtl280.bpl  } System.@RaiseExcept (Line 22127, "System.pas" + 51) + $0
[21CBF8D8]{delphicoreide280.bpl} PakList.TPackageListItem.LoadDesignPackage (Line 919, "PakList.pas" + 20) + $F
[500614A1]{rtl280.bpl  } System.@RaiseExcept (Line 22127, "System.pas" + 51) + $0
[103A4679]{fmx280.bpl  } FMX.BehaviorManager.{System.Generics.Collections}TDictionary<System.TGUID,System.IInterface>.GetItem (Line 7135, "System.Generics.Collections.pas" + 3) + $12
[106D849B]{fmx280.bpl  } FMX.Platform.TPlatformServices.GetPlatformService (Line 557, "FMX.Platform.pas" + 1) + $9
[5006177E]{rtl280.bpl  } System.InitUnits (Line 23842, "System.pas" + 21) + $0
[500617EE]{rtl280.bpl  } System.@PackageLoad (Line 23870, "System.pas" + 8) + $0
[500A3D07]{rtl280.bpl  } System.SysUtils.InitializePackage (Line 26512, "System.SysUtils.pas" + 4) + $0
[500A3E65]{rtl280.bpl  } System.SysUtils.LoadPackage (Line 26563, "System.SysUtils.pas" + 18) + $5
[21BCB5A9]{delphicoreide280.bpl} PasCppPakMgr.TIDEDesignPackage.ClearModules (Line 2189, "PasCppPakMgr.pas" + 14) + $10
[20430EAC]{coreide280.bpl} PakLoad.TPackage.DoLoadPackage (Line 146, "PakLoad.pas" + 0) + $8
[20431025]{coreide280.bpl} PakLoad.TPackage.Load (Line 220, "PakLoad.pas" + 7) + $7
[20433859]{coreide280.bpl} PakMgr.TDesignPackage.Load (Line 591, "PakMgr.pas" + 2) + $2
[21BCB8CF]{delphicoreide280.bpl} PasCppPakMgr.TIDEDesignPackage.Load (Line 2292, "PasCppPakMgr.pas" + 4) + $3
[210DAA6C]{vclide280.bpl} Collections.TCustomHashTable.Add (Line 1027, "Collections.pas" + 34) + $8
[500604D5]{rtl280.bpl  } System.@AfterConstruction (Line 19330, "System.pas" + 2) + $5
[21BCB6DF]{delphicoreide280.bpl} PasCppPakMgr.TIDEDesignPackage.DelayLoad (Line 2217, "PasCppPakMgr.pas" + 11) + $4
[21CBF938]{delphicoreide280.bpl} PakList.TPackageListItem.LoadWait (Line 939, "PakList.pas" + 3) + $4
[21CBF89F]{delphicoreide280.bpl} PakList.TPackageListItem.LoadDesignPackage (Line 914, "PakList.pas" + 15) + $5
[21CBE8AB]{delphicoreide280.bpl} PakList.TPackageListItem.SetIsInstalled (Line 582, "PakList.pas" + 7) + $3
[21CBE671]{delphicoreide280.bpl} PakList.TPackageList.AddPackage (Line 497, "PakList.pas" + 13) + $5
[21CDB4B2]{delphicoreide280.bpl} BasePasProjOpts.TProjOptsManager.InstallPackage (Line 1820, "BasePasProjOpts.pas" + 9) + $5
[21CDC73B]{delphicoreide280.bpl} BasePasProjOpts.TProjectOptions.InstallPackage (Line 2449, "BasePasProjOpts.pas" + 0) + $3
[21C9BA74]{delphicoreide280.bpl} PasMgr.TPascalPackageCodeUpdater.InstallPackage (Line 13131, "PasMgr.pas" + 18) + $19
[21BD6881]{delphicoreide280.bpl} PkgContainers.TStdPackageProjectContainer.CommandHandler (Line 178, "PkgContainers.pas" + 8) + $7
[20461C3F]{coreide280.bpl} ContainerIntf.TIDEProjectManagerMenuObject.Execute (Line 862, "ContainerIntf.pas" + 26) + $17
[2046386A]{coreide280.bpl} ContainerIntf.TProjectManagerMenuItem.Click (Line 1110, "ContainerIntf.pas" + 18) + $22
[50DF076B]{vcl280.bpl  } Vcl.Menus.TMenu.DispatchCommand (Line 3576, "Vcl.Menus.pas" + 5) + $2
[50DF19E6]{vcl280.bpl  } Vcl.Menus.TPopupList.WndProc (Line 4749, "Vcl.Menus.pas" + 4) + $E
[500606FC]{rtl280.bpl  } System.TMonitor.CheckOwningThread (Line 19536, "System.pas" + 2) + $0
[50060A22]{rtl280.bpl  } System.TMonitor.Exit (Line 19726, "System.pas" + 1) + $2
[50060A7E]{rtl280.bpl  } System.TMonitor.Exit (Line 19748, "System.pas" + 2) + $7
[50CA814D]{vcl280.bpl  } Vcl.Graphics.FreeMemoryContexts (Line 7288, "Vcl.Graphics.pas" + 12) + $8
[50CCC338]{vcl280.bpl  } Vcl.Controls.TWinControl.MainWndProc (Line 10267, "Vcl.Controls.pas" + 3) + $6
[50DF1935]{vcl280.bpl  } Vcl.Menus.TPopupList.MainWndProc (Line 4724, "Vcl.Menus.pas" + 2) + $5
[50174218]{rtl280.bpl  } System.Classes.StdWndProc (Line 18318, "System.Classes.pas" + 8) + $0
[211B4E9F]{vclide280.bpl} IDEVirtualTrees.TVirtualTreeHintWindow.IsHintMsg (Line 7103, "IDEVirtualTrees.pas" + 7) + $13
[50E0D743]{vcl280.bpl  } Vcl.Forms.TApplication.ProcessMessage (Line 11320, "Vcl.Forms.pas" + 23) + $1
[50E0D786]{vcl280.bpl  } Vcl.Forms.TApplication.HandleMessage (Line 11350, "Vcl.Forms.pas" + 1) + $4
[50E0DAC5]{vcl280.bpl  } Vcl.Forms.TApplication.Run (Line 11489, "Vcl.Forms.pas" + 27) + $3
[004F6F82]{bds.exe     } bds.bds (Line 227, "" + 16) + $2

Hi @TheOriginalBytePlayer, thank you so much for reporting the issue!
I've always had problems with the IDE to recompile packages without uninstalling them first and sometimes it's even necessary to reopen the IDE. To do this recompile without any problem, follow the steps:

Install Skia4Delphi using our Setup;
Open the library group project. In the case of alexandria: "Packages\RAD Studio 11.0 Alexandria\Skia4Delphi.groupproj"
Uninstall each "installable" package.
Close the IDE
If you want, you can delete the "Library" folder
Open the library group project. In the case of alexandria: "Packages\RAD Studio 11.0 Alexandria\Skia4Delphi.groupproj"
Compile all packages and install all "installable" packages. You can use "Show Build Groups pane" to build them all at once.
Reopen the IDE

@TheOriginalBytePlayer, do you have any news?

@TheOriginalBytePlayer Another way, perhaps even simpler, is to install InnoSetup and create/run your own installer:

Download the zip of our repository
Edit the files that you want
Install InnoSetup on your machine
Open and run the file Tools\Setup\Setup.iss

I'm sure both the methods I suggested here work 100%. I will close the issue for lack of response from you, but feel free to send any questions here or opening a new issue.

Okay, for some reason you're right I have to do that song and dance of uinstalling each library exiting Delphi.  Relaunching it and then rebuilding and reinstalling it.
Secondly, I'd had a component skLabel that I'd built and rather than refusing to install my library with the message that the component already existed in another one, it gave me an access violation, which is very weird.  Once I renamed it I was able to build and install my library which is vital to my project.

However, I needed to modify the tSkSVG to add a wrapMode property to the component itself (which then passes it along to its brush) and in order for me to do it, I had to go through the entire song and dance again, which is a bit of a pain.


Static code analysis _013 (The resource was not freed)

Short summary (details in file attached):
Event 17:  result has gone out of scope and no longer references the resource of interest.
There are no remaining references to the resource new () from linux_hal_common.hpp:382.

The resource was allocated at linux_hal_common.hpp:382.
The last reference was lost at linux_hal_common.hpp:383.
The resource was not freed.

gptp_013.txt

Fix was merged.


[identity] breaking change in 3.4.0?

Package Name:  azure/identiy
Package Version: 3.4.0

The application works fine with 3.3.2, if we upgrade to 3.4.0 we get the following error:
if we revert to 3.3.2, it works fine. if we upgrade to 4.0.0, it works fine too. something is broken in your 3.4.0
Error indexing files: Index creating "kbindex": Unknown server error: ChainedTokenCredential authentication failed.
CredentialUnavailableError: EnvironmentCredential is unavailable. No underlying credential could be used. To troubleshoot, visit
https://aka.ms/azsdk/js/identity/environmentcredential/troubleshoot.
CredentialUnavailableError: WorkloadIdentityCredential: is unavailable. tenantId, clientId, and federatedTokenFilePath are required parameters.
      In DefaultAzureCredential and ManagedIdentityCredential, these can be provided as environment variables -
      "AZURE_TENANT_ID",
      "AZURE_CLIENT_ID",
      "AZURE_FEDERATED_TOKEN_FILE". See the troubleshooting guide for more information:
https://aka.ms/azsdk/js/identity/workloadidentitycredential/troubleshoot

CredentialUnavailableError: ManagedIdentityCredential: Authentication failed. Message missing_tenant_id_error: A tenant id - not common, organizations, or consumers - must be specified when using the client_credentials flow.
CredentialUnavailableError: Azure CLI could not be found. Please visit
https://aka.ms/azure-cli
for installation instructions and then, once installed, authenticate to your Azure account using 'az login'.
CredentialUnavailableError: Error: Unable to execute PowerShell. Ensure that it is installed in your system. To troubleshoot, visit
https://aka.ms/azsdk/js/identity/powershellcredential/troubleshoot.
CredentialUnavailableError: Azure Developer CLI couldn't be found. To mitigate this issue, see the troubleshooting guidelines at
https://aka.ms/azsdk/js/identity/azdevclicredential/troubleshoot.

@sinedied

@KarishmaGhiya is this an MSAL issue?

@lgmorand Can you share the script I should run to reproduce this and the environment setting I should set? Are you running on local computer or on Managed identity resource? Let me know, I'll investigate

You can reproduce the issue easily from here: https://github.com/Azure-Samples/azure-openai-rag-workshop
After cloning the project:
npm install
cd src/indexer
npm install<EMAIL_ADDRESS>cd ../..
azd up

The post deployment script ./scripts/index-data.sh will fail with the error @lgmorand posted

I tried the azd up it's asking me to enter new environment name Please enter a new environment name:
Can you provide me more details on how to set up the environment, to repro the above issue?

Also, i am assuming that you were running DefaultAzureCredential. Can you provide more details on which credential in particular was expected to run and didn't run in this version? So that I can dive deeper into this. I know that we didn;t change anything on our side in terms of the API but we just upgraded msal versions to support both node 16 and node 20. Your feedback will really help me investigate in what actually broke.

I hit this yesterday, production broke between releases that were 20 minutes apart. How are there no tests for this most basic usage? Ridiculous.

I confirm the issue: with @azure/identity package 3.4.0, it is not possible to get credentials from a system identity on Azure.
To reproduce it, i created an azure function and an app configuration. I assigned a system identity to the azure function, an gave it rights to read app configuration keys.
I deployed the following code to my azure function:
  const { app } = require('@azure/functions');
  const { DefaultAzureCredential } = require('@azure/identity')
  const { AppConfigurationClient } = require('@azure/app-configuration')

  app.http('helloworld', {
      methods: ['GET'],
      authLevel: 'anonymous',
      handler: async (request, context) => {
          try {
              const appConfigClient = new AppConfigurationClient(
                  `https://${process.env.APPCONFIG_NAME}.azconfig.io`,
                  new DefaultAzureCredential()
              )
              const result = await appConfigClient.getConfigurationSetting({
                  key: 'MyKey'
              })
              context.log(`Http function processed request for url "${request.url}"`)
              const luxUrl = result.value
              context.log(`LUX URL is '${luxUrl}'`);
              return { body: `Hello World ! - LUX URL is '${luxUrl}'` }
          } catch (error) {
              context.log(error)
              return { body: JSON.stringify(error)}
          }
      }
  })

I tested with the following version of @azure/identity:

3.3.2: Works fine
3.4.0: Fails with the error reported by @lgmorand
4.0.0: Works fine

3.4.0 has been marked as deprecated to slow adoption while we work on getting 3.4.1 out

I figured out why managed identity was broken in 3.4.0 and pushed a fix to Matt's PR: https://github.com/Azure/azure-sdk-for-js/pull/27761/commits/a9974a7d8dde0f7102a6f29d0e7dafb318173505
Will see about getting this released assuming we've addressed all the constituent issues.

@lgmorand and @patrickdassier can you try out 3.4.1 which has just been released? I believe it addresses the issue you were seeing (at least it passes now in my Azure function app)
Thanks again for reporting and for your patience as we made sure we fixed things.

I confirm that release 3.4.1 solve the issue. Thanks

will get rollbacked to 3.4.1, you should fix that.

@sinedied Sorry for the bug.  It should be fixed now.


Fix broken UTF-8 symbols in r.js

Fix broken UTF-8 symbols in r.js

FYI @victor-homyakov ,
I submitted https://github.com/philix/jsx-requirejs-plugin/pull/41 which updates r.js to 2.1.16 - believe the UTF-8 symbols are fixed there?

Nope. They're still broken.

Weird because they show up fine on my machine?

Just compare https://raw.githubusercontent.com/tsjoberg/jsx-requirejs-plugin/master/r.js vs. https://raw.githubusercontent.com/jrburke/r.js/2.1.16/dist/r.js - they both are loaded in UTF-8 (have response header Content-Type:text/plain; charset=utf-8), and the first one has broken symbols. Seems that you're using some single-byte encoding locally, e.g. Cp1252.

Closed by #41.


Changes and corrections to support ROS 2 Galactic

This PR provides the fixes necessary to compile and run with ROS 2 Galactic.
This PR is backwards-compatible with ROS 2 Foxy. It can be merged without impacting support for ROS 2 Foxy.
Part of open-rmf/rmf#60.

LGTM!


"Token indices sequence length is longer than the specified maximum sequence length for this model"

Firstly, thanks so much for this code! I have been using it to make GPTQ 4bit 128g versions of several models, and it's been working very well.
On two recent models I have tried, I have got this error/warning:
When making GPTQ for model https://huggingface.co/AlekseyKorshuk/vicuna-7b:
Token indices sequence length is longer than the specified maximum sequence length for this model (3908 > 2048). Running this sequence through the model will result in indexing errors

When making GPTQ for model https://huggingface.co/GeorgiaTechResearchInstitute/galpaca-30b
Token indices sequence length is longer than the specified maximum sequence length for this model (1915 > 512). Running this sequence through the model will result in indexing errors

Example execution using Triton branch:
CUDA_VISIBLE_DEVICES=0 python3 llama.py /content/alek-vicuna-7b c4 --wbits 4 --true-sequential --act-order --groupsize 128 --save_safetensors /content/vicuna-AlekseyKorshuk-GPTQ-7B-4bit-128g.safetensors
I understand that this means that some input is exceeding the model's context length, but I am not sure what that input is, and what the impact is/might be for the final GPTQ file?
Thanks in advance.

I guess it's also possible that this has happened because of the new commits to GPTQ in the last day or so?   I am always running git clone https://github.com/qwopqwop200/GPTQ-for-LLaMa` before execution, so I am always running on the latest commit.
In a minute I will try re-running GPTQ on a model I did 24 hours ago, to see if I now get this message on that model.

This is normal and does not affect quantization in any way.


[Bug]: API Request Failed

Which API Provider are you using?
Anthropic
Which Model are you using?
Claude 3.5 Sonnet
What happened?
I do get this error quit frequently when running my tasks.
529 {"type":"error","error":{"type":"overloaded_error","message":"Overloaded"}}
Steps to reproduce

Creating a task in VS code for Claude 3.5 Sonnet
Running through some steps
This is the last prompt to the claude-dev

[write_to_file]
The content was successfully saved to src/components/EngineView.tsx.

<environment_details>
# VSCode Visible Files
src/components/EngineView.tsx

# VSCode Open Tabs
src/components/Hiber3D/Hiber3DApi.tsx
src/components/EngineView.tsx
src/utils/math/quaternionFromNormal.ts
src/components/Hiber3D/utils/rayCastFromScreen.ts
</environment_details>

...
Relevant API REQUEST output
529 {"type":"error","error":{"type":"overloaded_error","message":"Overloaded"}}

Additional context
No response
Before you submit

[X] I have checked existing issues
[X] I am using the latest version of Claude Dev and VSCode

+1 here for this one. My Claude Dev extension is stuck in this state and always returns this API response.
At console.anthropic.com under Logs, I can see these failing requests:

Interestingly, there it says "client error", suggesting that the problem might be on the client-side (meaning me or the Claude Dev extension, respectively), rather than Anthropic's API Endpoint.
Mentioning that in case it helps.

That is an issue with Anthropic.  You get that issue with any tool you use and it generally gets resolved after a few minutes.  There has been a degradation of response today as reported by Anthropic Status page.

529 means Anthropic servers down, I suggest using OpenRouter in the meantime–they have prompt caching now and better rate limits!


Add susl.txt

Changes needed for granting undergraduates of Sabaragamuwa University

@philipto Sorry for the delay in responding. Our university provides two email addresses for an undergraduate (one for Microsoft Dreamspark account and the official university email address). I recently found out that we are able to access your service via the official university email address and hence I am closing this PR as it is to obtain grant for the account created for MS dreamspark.


>= == !<

Description
x >= y == x !< y ∀𝑎∈ℕ
Technically this saves gas in some cases, but not in all. Not sure what you're thoughts are on this but figured I'd make in the PR in case you did want it. This saves gas usually because the compiler only must do iszero(gt(x,y)) rather than or(gt(x,y), eq(x,y)), but can very as its a pure function which will be inlined and optimized
Checklist
Ensure you completed all of the steps below before submitting your pull request:

[x] Ran forge fmt?
[x] Ran forge snapshot?
[x] Ran forge test?

Pull requests with an incomplete checklist will be thrown out.

@ControlCplusControlV Thanks for PR but solc optimizer already optimize this for us so for better readability we don't merge this.


Can CodeMap display in Explorer Activity

HI,
Can the CodeMap explorer have a setting to allow where its displayed.
Some screen shots show it in the Exporer activity.
However now its in its own activity on the activity bar.
A setting to control this would be great.
Thanks
Derek

Unfortunately it is not possible.
The placement of any plugin view  is hard-codded in the plugin's package.json.  Thus it's either its own view or in the main explorer.
And since

CodeMap can be relatively packed with the content
Main explorer is already crowded
VSCode introduced the mechanism and started encouraging authors to move their heavy plugin panels into the dedicated views

A few releases ago CodeMap has been moved in its own view.
Though thank you for letting me know. I have updated the readme.md to reflect the correct location of the plugin view:


branch-2.1 fix show create table consistency #37074

Proposed changes
Issue Number: close #xxx
pick https://github.com/apache/doris/pull/37074

run buildall


Update the Length of Malaysia PhoneNumber

As a Malaysian citizen and developer, I've made updates to the international phone field for Malaysia.
In Malaysia, phone numbers have the following format:
Phone Key: (+60)
phone number length of 9 digits following the phone key (+60 123456789).
I've adjusted the

MinLength from 11 to 9
MaxLength from 11 to 10.

This change aligns with the new phone number format provided by our updated phone number provider, which now includes numbers like +60<PHONE_NUMBER>.

@all-contributors please add @hanyi00i for code

Hey @hanyi00i, thanks for your contribution, but isn't the phone lower bound 8? According to this: https://en.wikipedia.org/wiki/Telephone_numbers_in_Malaysia
But, no worries, just confirm that it's 9 and I'll merge your PR

Hi @marcaureln, I appreciate your feedback and would like to provide further clarification on the phone number format for Malaysia.
The reason for the 8-digit lower bound mentioned in Wikipedia is due to its assumption of phone numbers starting with 01. But for the full international format used by the intl_phone_field, the phone numbers should start with +60XX-XXX XXXX, which results in either 9 or 10 digits.
Please let me know if you have any further questions or concerns. I'm open to any adjustments that would ensure the package's compatibility with Malaysian phone numbers.
Thank you for considering my contribution.

Great explanation, thank you!


flex-basis displaying %NaN when fenced blocks don't include span helper

basically
```html|
 <a href="javascript:;" class="pv3 ph4 br-pill bg-c-blue white bw1 link dim dib">Call to action</a>```

Doing this and not suppling the |span-X gives the CSS a %NaN in the flexBasis calc property

A quick fix for this was to add
if (span == undefined) {
  span = 6
}

inside the Span.prototype.render = function render() block
Any thoughts? Is the fix doable for now?

Thanks for reporting!
It is resolved in the latest version, the default value was never applied.


Limit the set of headers sent back

In the same way that we filter headers from the incoming message that we send to the dispatcher, we should limit headers on the way back (Content-Type seems like the only legitimate candidate for now)
This avoids exposing internal details (correlationId) and/or wrong values (eg http-gw replying with Served-By stating Express (node invoker))

Closing, in favor of handling at GW level: https://github.com/projectriff/http-gateway/issues/15


WFLY-18141 Several clustering-related modules should be private

https://issues.redhat.com/browse/WFLY-18141

Thanks @pferraro


update PPP

This merge is solely for PPP purpose, which is allowed by prof (asked in forum). No user guide, developer guide, functional codes or test cases code are changed.


Add Gitter Sidecar script

Added Gitter Sidecar script to embed the 24pullrequests/24pullrequests chatroom in the site.
Ref: #949

Nice work @tegon, thanks a lot! :christmas_tree:

Just deployed it, looking great!

Great! Thanks for looking into this so quickly. Never had a pull request merged so fast before! :smile:


Fix .golangci.yml

When we updated the .golangci.yml for 1.20 we should have used a string as 1.20 is not a valid number.
In doing so we need to restore the nolint markings within the pq driver.
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

merged following successful lint to avoid large queue.


Move Google Cloud Platform files over to "new" account

see #58

market-prediction-3fd2a is scheduled to be shutdown on 21st December 2021.


colorize output like jq

with colored_json and auto detection, if the output is an ansi terminal

@haraldh Thanks a ton for your contribution 👍.

Published https://crates.io/crates/jql/2.1.0 ⚡, thanks again!

Hmm, a lot of your README.md examples don't output valid json..
$ cargo run -q --  '"one".[2:0],"two","three"' <<EOF
> {
>   "one": [1, 2, 3],
>   "two": 2,
>   "three": 3
> }
> EOF
Invalid JSON file or content

@haraldh the latest release should address your issue https://crates.io/crates/jql/2.1.2 🤞.


NULL value handling

This is awesome, thank you for putting this out there! I just recently finished writing something similar for use at my company, but hit enough snags with the Parquet conversion bit that we punted on that portion. Perhaps we'll be switching to this soon.
One issue we had to deal with was proper round-trip representation of null values, as distinct from empty strings. Based on a quick glance it doesn't look like you're doing anything here to deal with that, but please let me know if I missed something!
Redshift UNLOADs provide the NULL AS option to allow specifying how nulls should be output, but there's a Redshift bug (which was actually acknowledged by an Amazon employee in an AWS forum posting somewhere, though I don't have the link handy) such that when you use both the NULL AS and ESCAPE options, the ESCAPE gets applied second. So, you can't get Redshift to unload a value that is guaranteed to uniquely represent nulls. A lot of systems out there seem to use the convention of representing nulls as \N in text files, but because of the bug you can only get Redshift unloads that use ESCAPE to write N (obviously problematic) or \\N (which would probably be okay most of the time but still isn't a solid guarantee).
We got around this by using an UNLOAD query formatted like so:
    UNLOAD ('{inner_unload_query}')
    TO '{unload_path}'
    IAM_ROLE '{iam_role_arn}'
    MAXFILESIZE 1 gb
    DELIMITER '|' NULL AS '\\N' MANIFEST GZIP

...where the inner_unload_query portion mostly just SELECTs all the table's columns by name, but uses a clause like this for columns of type character and character varying:
REPLACE(REPLACE(REPLACE(REPLACE("{column_name}", '\\', '\\\\'), '|', '\\|'), '\n', '\\\n'), '\r', '\\\r')

Which is admittedly pretty ugly, but the upshot is that this allows you to avoid needing the ESCAPE option, such that the NULL AS '\\N' part actually works to produce an output file where nulls are represented by \N. Once you have that in place, everything downstream can be configured to recognize that and the distinction between nulls empty strings can be maintained.
Just throwing that at you in case you find it valuable! Putting it all together the whole relevant chunk from my code (any or all of which you should feel free to use) looks like:
    cols = []
    escape_character_col_spec = r"""
        REPLACE(REPLACE(REPLACE(REPLACE("{}", '\\', '\\\\'), '|', '\\|'), '\n', '\\\n'), '\r', '\\\r')
    """
    for col in source_schema:
        if col['base_type'].startswith('character'):
            cols.append(escape_character_col_spec.format(col['name']))
        else:
            cols.append(r'"{}"'.format(col['name']))
    cols = r','.join(cols)
    inner_unload_query = r'SELECT {cols} FROM "{schema}"."{table}"'.format(**locals())
    inner_unload_query = inner_unload_query.replace('\\', '\\\\').replace("'", r"\'")
    unload_query = r"""
        UNLOAD ('{inner_unload_query}')
        TO '{unload_path}'
        IAM_ROLE '{iam_role_arn}'
        MAXFILESIZE 1 gb
        DELIMITER '|' NULL AS '\\N' MANIFEST GZIP
    """.format(**locals())
    logger.debug('Unloading with query:%s', unload_query)
    conn.execute(unload_query)

This is fantastic information! Thank you for sharing all this. One of my goals for this project is 100% data integrity so I'd love to have this as an option if not the default.

@c-nichols
I am glad that Spectrify is here.. helpful!   Just wondering when this fix will be available; (sorry, if I've overlooked). Currently, the UNLOAD uses plain dump.
@woodlee Should I change export_to_csv method in export.py?  with this snippet?  Currently, I see UNLOAD_QUERY is outside the method.  Will be helpful to re-use your code as I'm sure I'm going to hit the NULL/Timestamp issues.  Appreciate!
formatted_query = UNLOAD_QUERY.format(table_name)     with engine.connect() as cursor:         click.echo('Exporting table to CSV...')         cursor.execute(formatted_query, {             's3_path': s3_csv_path,             'credentials': creds_str,         })         click.echo('Done.')

@naveenarumugam I think something like that would be resonable; it's still working for us. Just keep in mind that my code snippet there is from an entirely different script I wrote, and not a modification to this library, so it'll certainly require some adjustment.
One thing that we have changed since I posted is to add a LEFT clause just inside the nasty series of REPLACEs like so:
REPLACE(REPLACE(REPLACE(REPLACE(LEFT("{}", 50000)...

...to help get around situations where the manual escaping causes the generated column's size to exceed Redshift's 64K max for varchars.
Good luck!

@woodlee  Thank you. Will test it. Meanwhile, should I consider the snippet as entirety or if possible can you pls share the full script?

@naveenarumugam Here you go!

I'll try to integrate this over the next few weeks, or at least make it easier to run the export with this query.
I'm also considering a rewrite of a lot of the core functionality to use classes instead of nested functions -- idea being classes are easy to extend/modify via inheritance.

Thanks @woodlee
@c-nichols  I just modified the code to add snappy compression (defaults to Gzip).
Do I have write permission to create branch and checkin to this project?

Hi @naveenarumugam, please use a fork to open a PR.  Following links provide some more info:
https://guides.github.com/activities/forking/
https://spectrify.readthedocs.io/en/stable/contributing.html#get-started

Sure, Thanks @c-nichols

Any progress on this?

@woodlee Is the issue of ESCAPE being applied after NULL AS is still present in AWS?

@Nihhaar sorry, I don't know. Haven't worked with it in a while.


Shells not hitting top of enemies (wont change probably); SMB2j mushroom bounce height; New custom enemy transform trigger: defeated by fireball

apparently i remembered these now hehe sowwy
list of things u need to check:

idk why but when you try to combo enemies with a shell coming from a ledge or smth, they dont actually hit the enemy but go above them as if they were solid from the top. thing is, these should hit enemies..
the smb2j mappack showcases a minor annoying thing, which is how high a item can go when bumped from below. just by playing 1-1 in it and trying to get the first mushroom is near impossible (cuz it bounces a bit lower and the brick collision pushes it to the left) unless you get inside that structure. a fix could be simply making the bounce value slightly higher.
maybe a property for defeating enemies that should transform when a fireball is used, unless that one exists already (example i can give is the custom enemy parakoopa, they should be defeated by a fireball but they transform into a normal koopa instead). idk how hard this maybe to implement but its ok if you dont. :p

There's the "shot" transformtrigger

I actually have a port of SMB2J, it fixes this completely, just that Luigi, title screen, and several things aren't done. All Power-Ups are textured like SMB2J, etc.


fix(integration): test_metric_longhorn_volume_file_system_read_only

Which issue(s) this PR fixes:

Issue longhorn/longhorn#9553
What this PR does / why we need it:

Fix metric gathered from the wrong node.
Replace the crashing engine by remounting volume RO, following the test steps outlined in the original issue.

Special notes for your reviewer:
None
Additional documentation or context
None

@coderabbitai review

Test results: https://ci.longhorn.io/job/private/job/longhorn-tests-regression/7773/


Unify the Node.js API for providers

Currently we have API methods that work under /api/bigcommerce/* that applies for all providers. The API used for the Node.js side of the commerce demo should be unified in a similar way of the agnostic provider we currently have for the UI hooks.

@lfades I support this but let's also think one step higher in abstraction: There are some API that go beyond providers and would be used for any back end. For example, isAllowedMethod.
ref: https://github.com/vercel/next.js/discussions/25599
As a side note, I find the higher-order hook implementation like swell/.../use-signup.tsx to be really hard to reason about. Just a note that 'unify the API' doesn't need to be done with a compositional approach. isAllowedMethod, for example, could simply be pasted in framework/utils and the other files could directly import it without composition.

@Vandivier isAllowedMethod was moved to be inside commerce so that's already the case, on the note about compositional approach that's a requirement because providers don't match each other's features, each provider adds what they can do


[Backport release-21.11] gitlab: 14.7.4 -> 14.8.2

Motivation for this change
Backport #162088 to release-21.11
(cherry picked from commit 09abb37955ca992608cc32732f9a837d87cbda20)
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Fails to build and need to fix gitaly. Marking as draft for now.


Signed OTA updates fail when debugger is attached (IDFGH-5089)

When the debugger is attached verification of signed OTA update images fails.
This is because the verification logic (in image_load()) skips the checksum check, but the checksum check also updates the image length attribute of esp_image_metadata_t.
When the signature of the images is then verified, the wrong position is used, as the image_len field is not updated. Furthermore, the corruption check (using a 'simple' hash) also fails due to the wrong end position being used.
The checksum check is skipped because when the debugger is attached software breakpoints might invalidate the checksum. This seems only relevant for running images, not for fresh images coming in via OTA.
I've attached a proposed fix, which extends the image loading enum with an IGNORE_JTAG option. This is then used in the OTA functions, knowing that a running debugger will not place software breakpoints in OTA images when they are checked after download.
ota_ignore_jtag.patch.txt

Hi @RJPoelstra!
Thank you for the issue report. I have done a refactor of image_load() and fix the image_len. The length of the image is calculated correctly even if some checks are needed.
12795.zip.
Could you help to check this patch to confirm that it helps?
Thanks.

Hi,
Thanks for the update, but I'm sorry, it doesn't fully work.
It reports that the image is valid, but the signature bad.
I've tried with espsecure.py verify_signature --version 1 --keyfile priv.pem build/S000030.bin, which reports that the signature is valid.
Output from the ESP32:
I (597594) esp_image: Verifying image signature...
E (599134) esp_image: Secure boot signature verification failed
I (599134) esp_image: Calculating simple hash to check for corruption...
W (599424) esp_image: image valid, signature bad

After applying your patch and recompiling, I re-flashed the bootloader, partition table and application.
Do you want me to dig into something?

Hi @RJPoelstra! Thanks for testing. Yes, there was an error. Please if you have time try this one. 12795 (1).zip
Thanks.

@KonstantinKondrashov Thanks for this patch. I can confirm that it works for me.


Add Unitxt Multimodality Support

@haileyschoelkopf @baberabb @lintangsutawika what is the recommended way to address the requirement of "pillow" package for loading doc-vqa dataset?

Hi @elronbandel. pillow is (or should be) one of the required dependencies of multimodal as that's what we use to manipulate images. But we should add unitxt as an optional dependency and add it there as well like: https://github.com/EleutherAI/lm-evaluation-harness/blob/15ffb0dafa9c869c7436ba9a3cf3067ac4c9d846/pyproject.toml#L59-L60

@baberabb Unitxt should work without any dependencies (including unitxt) the only issue is with the missing pillow. Is there any chance this GitHub action dont install it? it seems to install only pip install -e '.[dev,ifeval]'.
In the pyproject.toml there is no dependencies for multimodality and no mentions to pillow.  How would you like to address this?

@baberabb Unitxt should work without any dependencies (including unitxt) the only issue is with the missing pillow. Is there any chance this GitHub action dont install it? it seems to install only pip install -e '.[dev,ifeval]'. In the pyproject.toml there is no dependencies for multimodality and no mentions to pillow. How would you like to address this?

In that case, the unit tests are failing due to a recent tokenizers update. If you merge with the latest main, I think they should all pass now. Tasks Modified  will still fail, but thats ok as they haven't been updated for multimodal tasks yet.

Hi @baberabb, I updated it, still it fails on the missing pillow requirement.

LGTM! Will add pillow dependency in another PR!


How to solve this situation, it has been going on for three days

How to solve this situation, it has been going on for three days.

Same problem


Remove version: Jackett.Jackett version 0.21.662

404 - release deleted
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/Jackett/Jackett/releases/download/v0.21.662/Jackett.Installer.Windows.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 918)


Support other guest OSs that run VirtualBox

Eg. Windows and FreeBSD.

@herby it's a good suggestion to support more OS, however, virtualbox might not be the best candidate on every platform. We will adopt more hypervisors and support more OSes. And any contributions are welcome as well.

@gnawux Emm... I really don't know which hypervisor would be the best, and I was not suggesting VirtualBox's one is. My point was, you already have taken this path ("foreign" host OS, using hypervisor from VirtualBox) on OS X, so taking this tried path on Windows and FreeBSD should be possible a lot faster. And then when you can claim you can run on every major OS, it would be much stronger point to use hyper.
Optimizing the experience by choosing the most appropriate one for each OS can be done later.
Or?

Will runv be able to run windows inside created VM or it is limited to linux only. It might be mentioned somewhere but couldn't found it so asking to confirm.
Between really nice work and loooking forward to see it merged it with upstream k8s and may be other resource managers.

@gurvindersingh current it support linux only, because it launch vm with linux kernel and init

Ok. But is there plan to add support for Windows in near future as Windows
containers are also getting there.
On Dec 3, 2015 3:32 AM, "Xu Wang"<EMAIL_ADDRESS>wrote:

@gurvindersingh https://github.com/gurvindersingh current it support
linux only, because it launch vm with linux kernel and init
—
Reply to this email directly or view it on GitHub
https://github.com/hyperhq/runv/issues/64#issuecomment-161497900.

@gurvindersingh no plan yet, but we'd like to learn suggestions.

VirtualBox driver was disabled and partially removed


Move [data-turbo="false"] guard up to observers

Since the FormSubmitObserver and LinkClickObserver classes are
very interested in the page's HTML, extract the elementIsNavigable
checks from the Session into our utility module for re-use amongst the
observers.
This enables the Session to act with more confidence that any
interaction on the page is to be Turbo-enabled.

Modifying Link and Form observers is related to https://github.com/hotwired/turbo/pull/66, so I'm closing this in favor of #66 and combining the commits.

Modifying Link and Form observers is related to https://github.com/hotwired/turbo/pull/66, so I'm closing this in favor of #66 and combining the commits.


Popup does not appear

Hi!
I'm testing it with NeoVim on Ruby files and it does not seem to work. When I invoke completion using <C-X><C-O> it works fine but the completion popup (from asynccomplete-omni) does not automatically appear as I type.
Fragments from my init.vim file:
    " Completions {{{
      Plug 'prabirshrestha/asyncomplete.vim'
      Plug 'prabirshrestha/asyncomplete-buffer.vim'
      Plug 'prabirshrestha/asyncomplete-gocode.vim'
      Plug 'prabirshrestha/asyncomplete-tags.vim'
      Plug 'yami-beta/asyncomplete-omni.vim'
    " }}}

    call asyncomplete#register_source(asyncomplete#sources#omni#get_source_options({
      \ 'name': 'omni',
      \ 'whitelist': ['*'],
      \ 'completor': function('asyncomplete#sources#omni#completor')
      \  }))

Any idea what can be wrong?

If you add this imap <c-space> <Plug>(asyncomplete_force_refresh) and then type <c-space> does it show autocomplete popup?

@prabirshrestha thanks for quick reply. With ` it does not work correctly either. I've recorded screencast to show you how it behaves on my side:

At first try it asynccomplete shows error: No inserted text yet. Then I'm using normal omni-completion (<C-X><C-O>), then I try <C-Space> again (it works for include? method but put double ii at the beginning of the method), then when I try it once again it wipes the code before the cursor.

Seems to work perfectly fine with vim8 on windows that comes with inbuilt ruby onmifunc. For me both syntax and omni sources works.
Plug 'prabirshrestha/asyncomplete.vim'
Plug 'prabirshrestha/asyncomplete-necosyntax.vim'
Plug 'yami-beta/asyncomplete-omni.vim'

autocmd FileType ruby setlocal omnifunc=rubycomplete#Complete

imap <c-space> <Plug>(asyncomplete_force_refresh)
inoremap <expr> <Tab> pumvisible() ? "\<C-n>" : "\<Tab>"
inoremap <expr> <S-Tab> pumvisible() ? "\<C-p>" : "\<S-Tab>"
inoremap <expr> <cr> pumvisible() ? "\<C-y>\<cr>" : "\<cr>"
autocmd! CompleteDone * if pumvisible() == 0 | pclose | endif

au User asyncomplete_setup call asyncomplete#register_source(asyncomplete#sources#omni#get_source_options({
    \ 'name': 'omni',
    \ 'whitelist': ['*'],
    \ 'completor': function('asyncomplete#sources#omni#completor'),
    \ }))
au User asyncomplete_setup call asyncomplete#register_source(asyncomplete#sources#necosyntax#get_source_options({
    \ 'name': 'necosyntax',
    \ 'whitelist': ['*'],
    \ 'completor': function('asyncomplete#sources#necosyntax#completor'),
    \ }))

Do you have problems with other sources like gocode, buffer or is it just with ruby?
Are you using some other omnicomplete func? If so make sure that completefunc is sync.
Do you also other autocomplete plugins besides asyncomplete.vim. Since asyncomplete.vim is async it takes over our popup management. That means deoplete, ncm or neocomplete shouldn't be used. It is the same other way around. If you use those plugins use only one and not multiple autocomplete managers.
Since asyncomplete popup manages what to show in popup, do not use <c-x c-o> directly. Use  <Plug>(asyncomplete_force_refresh) instead.
Can you try disabling sign plugin. I do use ale personally but haven't seen this problem.
Please upload a minimal vimrc like this https://gist.githubusercontent.com/junegunn/6936bf79fedd3a079aeb1dd2f3c81ef5/raw so that I can exactly try to reproduce. also mention vim/nvim version as well as OS.
You can also try to see the log let g:asyncomplete_log = expand('~/asyncomplete.log').

Another option would be to also try vim-lsp with asyncomplete using asyncomplete-lsp.vim. This is better than omnicompletion since the actual lang server is started in different process and provides various other features such as go to definition, document formatting, find references and so on. This allow the actual completion to be purly async. A quick search let me to this https://github.com/mtsmfm/language_server-ruby and https://github.com/rubyide/vscode-ruby/issues/118#issuecomment-278221193

Thanks for detailed troubleshooting instructions!
I'm sorry but I map incorrectly map <c-space> to <Plug>(asyncomplete_force_refresh) - I used nnoremap instead of imap. After changing to imap I don't see any popup nor it does not autocomplete.
Here is the minimal vimrc that I've been using for testing. I'm using neovim (NVIM v0.2.1-782-gf465bf0).

Do you have problems with other sources like gocode, buffer or is it just with ruby?
It's only with Ruby. Autocompletion for gocode and buffers works fine.

Are you using some other omnicomplete func? If so make sure that completefunc is sync.
No I'm not

Do you also other autocomplete plugins besides asyncomplete.vim. Since asyncomplete.vim is async it takes over our popup management. That means deoplete, ncm or neocomplete shouldn't be used. It is the same other way around. If you use those plugins use only one and not multiple autocomplete managers.

No I don't

Can you try disabling sign plugin. I do use ale personally but haven't seen this problem.

I tried with the vimrc I posted above. Still no popup.

You can also try to see the log let g:asyncomplete_log = expand('~/asyncomplete.log')

I tried it but it didn't even created the log file for me.

@lowski Sorry for my late reply.
Please try fix-startcol branch.
I think this branch works correctly.
If this branch resolve this issue, I merge it into master.
@prabirshrestha Thank you for help to resolve !

@yami-beta I've switch to that branch but I don't see pop-up (neither when I type nor I hit <c-space>). I'm testing it with the following vimrc (using nvim -u path/to/file):
set nocompatible

call plug#begin('~/.vim/plugged')
  Plug 'prabirshrestha/asyncomplete.vim'
  Plug 'yami-beta/asyncomplete-omni.vim', { 'branch': 'fix-startcol' }
call plug#end()

autocmd FileType ruby setlocal omnifunc=rubycomplete#Complete
imap <c-space> <Plug>(asyncomplete_force_refresh)
inoremap <expr> <Tab> pumvisible() ? "\<C-n>" : "\<Tab>"
inoremap <expr> <S-Tab> pumvisible() ? "\<C-p>" : "\<S-Tab>"
inoremap <expr> <cr> pumvisible() ? "\<C-y>\<cr>" : "\<cr>"
autocmd! CompleteDone * if pumvisible() == 0 | pclose | endif
call asyncomplete#register_source(asyncomplete#sources#omni#get_source_options({
  \ 'name': 'omni',
  \ 'whitelist': ['*'],
  \ 'completor': function('asyncomplete#sources#omni#completor')
  \  }))

@lowski Sorry, I misspelled.
Wrong: fix-startcol
Correct: topic/fix-startcol

@yami-beta this works perfectly, thanks! Please merge to master.

Merged!


Table: Fix grouped table loading and no records missing text

A grouped table currently does not display the no records and loading render fragments. This pr fixes and tests the issue.

Yes it didn't display them, i agree.

All tests are passing on my end and no build errors. I can't seem to see the CI logs anymore and don't have access to rerun them...

All green

lol, co-authored by John Snow ;)

Thank you for your contribution!


If it possible to suport DB2 XML column type

I was playing with pyodbc and DB2 11 on windows
"DRIVER={IBM DB2 ODBC DRIVER};SEVER=localhost;PORT=50000;DATABASE=sample;UID=user1;PWD=password1"
..and if I do SELECT * from customer
it was giving me the error
pinfo->sql_type = -370, that's for ibm_db.SQL_XML DB2 XML column type value
RaiseErrorV("HY106", ProgrammingError, "ODBC SQL type %d is not yet supported. column-index=%zd  type=%d",
(int)pinfo->sql_type, iCol, (int)pinfo->sql_type)
so I went to the src\getdata.cpp in pyodbc source code and changed, line 780
case -370: //DB2.SQL_XML
return GetText(cur, iCol);
and 699
case -370://ibm_db.SQL_XML
and now my select works, but I am not sure if ODBC API has an XML data type and if that matches DB2 XML data type.

...that was quick....

Testing with python3 under mac I get
Python(59177,0x7ffff12d43c0) malloc: *** mach_vm_map(size=140733193392128) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
Exception   <class 'MemoryError'>
will keep investigating....

Hmmm...  That's 0x7FFF,0000,1000 which looks very suspicious.  If you know what the decimal value is, we can put it into the unit tests for some other DBs and see if we get the same thing.

I did a test with DB2 10.1 on mac, client pyodbc on mac...crashes
...did a test docker DB2 11.1 on mac , client pyodbc on mac ...crashes
the test is very simple...connect to SAMPLE database ( is like a demo DB2 database) and I do select * from customer, customer table has 2 DB2 XML fields...
will keep investigating...

I did not know you could be DB/2 for the Mac.  I'll have to download Express and test...

on windows works OK...let me keep investigating...with Db2 on a docker container, one can run DB2 almost everywhere you can run docker....

Last test works ok...will keep experimenting ....
pyodbc==4.0.17b4 works ok on mac using XML fields from SAMPLE database, table customer.
SELECT * from customer, loop through the cursor...print the fields.
Will do more complex tests, in the future.

So, I am assuming we can close this now that whatever is in 4.0.17b4 has been released in 4.0.19.  Please reopen if I misunderstood.

Yes, close it. The last test I did all was ok.


obsolete: signal transduction involved in regulation of aerobic respiration

obsolete: signal transduction involved in regulation of aerobic respiration
This was requested by PomBAse via term genie, but it is clearly
GO:0010619 | adenylate cyclase-activating glucose-activated G protein-coupled receptor signaling pathway
signal transduction involved in regulation of aerobic respiration
all EXP pombe except one mouse

GO:0007189 adenylate cyclase-activating G protein-coupled receptor signaling pathway
has 3 children:
GO:0010619 adenylate cyclase-activating glucose-activated G protein-coupled receptor signaling pathway
GO:0110034 negative regulation of adenylate cyclase-activating glucose-activated G protein-coupled receptor signaling pathway
GO:0110033 regulation of adenylate cyclase-activating glucose-activated G protein-coupled receptor signaling pathway

All  EXPannotations are pombase so I'll obsolete.

Don't we want to  keep this one
GO:0010619 | adenylate cyclase-activating glucose-activated G protein-coupled receptor signaling pathway
(I think this was the term name which came out of the signalling meeting wasn't it ?)
just to get rid of the
"involved in regulation of aerobic respiration" terms

SORRY I got confused by the ID

I didn't put the  title into the  requrest
"obsolete: signal transduction involved in regulation of aerobic respiration"
Possibly some weeding can be done in the cAMP signalling but it is pretty OK for now

Dear all,
The proposal has been made to obsolete
GO:1903759 signal transduction involved in regulation of aerobic respiration
The reason for obsoletion is that this represents a GO-CAM model.
There are 4 annotations to this term, one by UniProtKB and 3 by PomBase.
There are no mappings to those terms; those terms are not present in any subsets.
Thanks, Pascale


VSX version of vpx_quantize_fp

Implement a VSX version of :

[x] vpx_quantize_fp
[x] vpx_quantize_fp_32x32

Each function must:

[x] Pass the VP9QuantizeTest suite
[x] Include Speed Test to the VP9QuantizeTest suite (Disabled by default)
[x] Report performance in commit msg (compared to C version)

Must show significant speedup over C version

VSX Version of vp9_quantize_fp and

https://chromium.googlesource.com/webm/libvpx/+/b1434f31255c6857bb0f06abc942bbf07bb156d5
https://chromium.googlesource.com/webm/libvpx/+/74a0b04f5733f4b8c816225752417ef3ce146cd4

Low bit depth version only. Passes the VP9QuantizeTest test suite.
Performance gains for POWER8 Model 2.1, of VSX over C are :
4x4    C time = 86.3 ms (±0.7 ms), VSX time = 18.2 ms (±0.0 ms) [ 4.7x]
8x8    C time = 57.7 ms (±0.3 ms), VSX time =  7.6 ms (±0.0 ms) [ 7.6x]
16x16 C time = 50.7 ms (±0.1 ms), VSX time =  4.9 ms (±0.0 ms) [10.3x]
32x32 C time = 93.1 ms (±0.4 ms), VSX time = 6.5 ms (±0.2 ms) [14.4x]


Added String-To-Int64 option parsing

Add support for "map[string]int64" options.

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

hard to argue with that review.


Image building is very slow

Building the singularity image on each run is very slow. Even though the layers are cached, the image is still rebuilt for simulators that already exist.
We can remove the singularity pull command on each run. This will lead to the problem that images will not be updated if a change is made for a new tag. A simple API endpoint should be sufficient to provide an automated way to update images

I think this could be done by breaking down the pulling of the Docker image and building of the Singularity image into separate steps:

Use Docker to check if there's a new version and pull the version if needed. This will rely more directly on Docker's cache.
Inspect Docker's output to detect whether Docker pulled a new version.
Build a singularity image only if Docker pulled a new version.

IMAGE_UP_TO_DATE_MESSAGE="Image is up to date"
dockerLog=$(docker pull ghcr.io/biosimulators/{simulator-id})
if [[ "$dockerLog" != *"$IMAGE_UP_TO_DATE_MESSAGE"* ]]; then
    singularity build {simulator-id}.sif docker://ghcr.io/biosimulators/{simulator-id}
fi

I think this would work on my local machine. Would this work in UConn's HPC environment?

I think this could be done by breaking down the pulling of the Docker image and building of the Singularity image into separate steps:

Use Docker to check if there's a new version and pull the version if needed. This will rely more directly on Docker's cache.
Inspect Docker's output to detect whether Docker pulled a new version.
Build a singularity image only if Docker pulled a new version.

IMAGE_UP_TO_DATE_MESSAGE="Image is up to date"
dockerLog=$(docker pull ghcr.io/biosimulators/{simulator-id})
if [[ "$dockerLog" != *"$IMAGE_UP_TO_DATE_MESSAGE"* ]]; then
    singularity build {simulator-id}.sif docker://ghcr.io/biosimulators/{simulator-id}
fi

I think this would work on my local machine. Would this work in UConn's HPC environment?

No, we do not have the ability to use docker on the HPC
On Tue, Jan 12, 2021 at 1:04 PM Jonathan Karr<EMAIL_ADDRESS>wrote:

I think this could be done by breaking down the pulling of the Docker
image and building of the Singularity image into separate steps:

Use Docker to check if there's a new version and pull the version
if needed. This will rely more directly on Docker's cache.
Inspect Docker's output to detect whether Docker pulled a new
version.
Build a singularity image only if Docker pulled a new version.

IMAGE_UP_TO_DATE_MESSAGE="Image is up to date"
dockerLog=$(docker pull ghcr.io/biosimulators/{simulator-id} http://ghcr.io/biosimulators/{simulator-id})if [[ "$dockerLog" != "$IMAGE_UP_TO_DATE_MESSAGE" ]]; then
singularity build {simulator-id}.sif docker://ghcr.io/biosimulators/{simulator-id} http://ghcr.io/biosimulators/{simulator-id}fi
I think this would work on my local machine. Would this work in UConn's
HPC environment?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/biosimulations/Biosimulations/issues/1942#issuecomment-758837455,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHX4FIEXJILCFVDIMUC7MQDSZSFKRANCNFSM4V7SCLEA
.

No, we do not have the ability to use docker on the HPC
On Tue, Jan 12, 2021 at 1:04 PM Jonathan Karr<EMAIL_ADDRESS>wrote:

I think this could be done by breaking down the pulling of the Docker
image and building of the Singularity image into separate steps:

Use Docker to check if there's a new version and pull the version
if needed. This will rely more directly on Docker's cache.
Inspect Docker's output to detect whether Docker pulled a new
version.
Build a singularity image only if Docker pulled a new version.

IMAGE_UP_TO_DATE_MESSAGE="Image is up to date"
dockerLog=$(docker pull ghcr.io/biosimulators/{simulator-id} http://ghcr.io/biosimulators/{simulator-id})if [[ "$dockerLog" != "$IMAGE_UP_TO_DATE_MESSAGE" ]]; then
singularity build {simulator-id}.sif docker://ghcr.io/biosimulators/{simulator-id} http://ghcr.io/biosimulators/{simulator-id}fi
I think this would work on my local machine. Would this work in UConn's
HPC environment?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/biosimulations/Biosimulations/issues/1942#issuecomment-758837455,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHX4FIEXJILCFVDIMUC7MQDSZSFKRANCNFSM4V7SCLEA
.

I see. That removes one option.

I see. That removes one option.

The api endpoint would actually be rather simple. We already have all the code for making a ssh connection and running a command. I can get a PR up shortly

The api endpoint would actually be rather simple. We already have all the code for making a ssh connection and running a command. I can get a PR up shortly

I know that Docker can't be used to execute images in the HPC environment, but can Docker be used to pull images?

I know that Docker can't be used to execute images in the HPC environment, but can Docker be used to pull images?

No, docker is not present on the environment at all.
On Tue, Jan 12, 2021 at 1:07 PM Jonathan Karr<EMAIL_ADDRESS>wrote:

I know that Docker can't be used to execute images in the HPC environment,
but can Docker be used to pull images?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/biosimulations/Biosimulations/issues/1942#issuecomment-758839325,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHX4FIHX6LRBOTGE3KEHNDTSZSFW5ANCNFSM4V7SCLEA
.

No, docker is not present on the environment at all.
On Tue, Jan 12, 2021 at 1:07 PM Jonathan Karr<EMAIL_ADDRESS>wrote:

I know that Docker can't be used to execute images in the HPC environment,
but can Docker be used to pull images?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/biosimulations/Biosimulations/issues/1942#issuecomment-758839325,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHX4FIHX6LRBOTGE3KEHNDTSZSFW5ANCNFSM4V7SCLEA
.

I think you're right about needing to build a service for this. I can't see a way to do this with Singularity alone. I checked the Singularity API as well. I don't see anything that I think would help with this.

I think you're right about needing to build a service for this. I can't see a way to do this with Singularity alone. I checked the Singularity API as well. I don't see anything that I think would help with this.


docker pull always failed.

docker pull registry.cn-hangzhou.aliyuncs.com/modelscope-repo/modelscope:ubuntu20.04-cuda11.7.1-py38-torch2.0.1-tf1.15.5-1.8.1
It complains:
docker pull registry.cn-hangzhou.aliyuncs.com/modelscope-repo/modelscope:ubuntu20.04-cuda11.7.1-py38-torch2.0.1-tf1.15.5-1.8.1
Error response from daemon: Get "https://registry.cn-hangzhou.aliyuncs.com/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
it seems the address expired?

hi @You-Cun , Please take a look at this when you get a chance.

It may be a temporary issue with the server or network. Please try again after a while and check if there exists same problem.


Most currencies in the drop down menu aren't working

Description
In the 4.7.0 release candidate (tested on OSX) only the original currencies of NAV, BTC, EUR and USD populate correctly. The other currencies beginning from ARS all show 0.00000 amounts in Balances, Staking and Transactions.
Motivation
Having the above fields populated with the proper amounts gives users more confidence that the wallet is working correctly.

Acceptance Criteria
Add any additional acceptance criteria you think should be included to the list below.

[ ] Description is satisfied.
[ ] Changes display correctly on desktop / mobile.
[ ] Translations have been added or ammended as necessary.

@magpie17 this sometimes happens when a price query to the API does not successfully return the values.
It should fix itself once the prices are updated (Once every 5 minutes)

@mxaddict just for added detail, I have clicked on "Update exchange prices" and also quit the navcoin-core wallet and restarted and I still see the same issue with all currencies other than the first 5 in the drop down menu returning 0 values. This hasn't changed (for me) in the 2 days since logging this issue.

@mxaddict just for added detail, I have clicked on "Update exchange prices" and also quit the navcoin-core wallet and restarted and I still see the same issue with all currencies other than the first 5 in the drop down menu returning 0 values. This hasn't changed (for me) in the 2 days since logging this issue.

I see, are you running on OSX not windows? Cause we had a similar issue to this on windows, but worked fine on OSX and LINUX

If possible, can you copy the error log? You should be able to access it from: Help->Debug Window->Error Log

Yes I am running this on OSX (version 10.13.6 High Sierra on a Mac Mini Late 2012 just in case the hardware setup is a factor). The Error log is spitting out these error messages every 5 minutes: 2019-08-29 10:15:17 ERROR: Could not parse price data json 'boost::property_tree::json_parser::json_parser_error'
2019-08-29 10:20:22 ERROR: Could not parse price data json 'boost::property_tree::json_parser::json_parser_error'
2019-08-29 10:25:28 ERROR: Could not parse price data json 'boost::property_tree::json_parser::json_parser_error'
2019-08-29 10:30:15 ERROR: Could not parse price data json 'boost::property_tree::json_parser::json_parser_error'
2019-08-29 10:35:18 ERROR: Could not parse price data json 'boost::property_tree::json_parser::json_parser_error'
2019-08-29 10:40:15 ERROR: Could not parse price data json 'boost::property_tree::json_parser::json_parser_error'

Yes I am running this on OSX (version 10.13.6 High Sierra on a Mac Mini Late 2012 just in case the hardware setup is a factor). The Error log is spitting out these error messages every 5 minutes: 2019-08-29 10:15:17 ERROR: Could not parse price data json 'boost::property_tree::json_parser::json_parser_error'
2019-08-29 10:20:22 ERROR: Could not parse price data json 'boost::property_tree::json_parser::json_parser_error'
2019-08-29 10:25:28 ERROR: Could not parse price data json 'boost::property_tree::json_parser::json_parser_error'
2019-08-29 10:30:15 ERROR: Could not parse price data json 'boost::property_tree::json_parser::json_parser_error'
2019-08-29 10:35:18 ERROR: Could not parse price data json 'boost::property_tree::json_parser::json_parser_error'
2019-08-29 10:40:15 ERROR: Could not parse price data json 'boost::property_tree::json_parser::json_parser_error'

Thanks, they look like the same issue that the windows builds had.

@magpie17 could you please provide an address to receive a bounty for reporting this issue?

i can't see the issue on macos 14.14.4 devnet

error.log
2019-08-29 19:33:32 ERROR: Could not parse price data json 'boost::property_tree::json_parser::json_parser_error'
2019-08-29 19:33:42 ERROR: Read: Failed to open file /Users/alex/Library/Application Support/NavCoin4/devnet/peers.dat
2019-08-29 19:33:42 ERROR: Read: Failed to open file /Users/alex/Library/Application Support/NavCoin4/devnet/banlist.dat

@aguycalled Thanks, you can send it to NZB1D88gReSbVWp54JZEqCiQS78unCQTcz

Paid eaa557c6c929d47dd66c0152f9f4c0481cb412583ae8ef14b54789ade899a15c

@magpie17  @aguycalled  I was able to replicate this issue on OSX 10.14 as well as Windows 10 64 bit
And have created a patch for the issue in #601

tested the new build that @mxaddict created to fix this but I'm seeing the same behaviour and same error messages:

2019-09-08 08:49:02 ERROR: Could not parse price data json 'boost::property_tree::json_parser::json_parser_error'
2019-09-08 08:54:02 ERROR: Could not parse price data json 'boost::property_tree::json_parser::json_parser_error'
2019-09-08 08:59:02 ERROR: Could not parse price data json 'boost::property_tree::json_parser::json_parser_error'


async move in Box::pin produces an error

Using async move within Box::pin() as shown below will produce the corresponding error. This may not be the best example of this issue, but I would not expect the code to compile just fine and have lsp/rustic show an error within rustic.
fn main() {
    let a = Box::pin(async move { println!("Hello") });
}

error: expected one of `!`, `)`, `,`, `.`, `::`, `?`, `{`, or an operator, found keyword `move`
 --> /home/user/myproject/src/main.rs:2:28
  |
2 |     let a = Box::pin(async move { println!("Hello") });
  |                            ^^^^ expected one of 8 possible tokens

I believe this error came about due to a misconfiguration on my part. As of this writing, strictly following Robert Krahn's setup will avoid this error: https://robert.kra.hn/posts/rust-emacs-setup/


Improved/logistics examples

Resolves # .
Description
added examples in the logistic docs
Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x ] Read, understood, and followed the contributing guidelines.

@stdlib-js/reviewers

Closing this PR, as it contains the changes to the triangular namespace and updated the cdf README.md instead of the top-level one of the logistic namespace.


RandAugment magnitude:  10 in paper while 5 in code

Hi,
Thanks for your great work.
I noticed that the magnitude of RandAugment is 10 in the paper Appendix.H while 5 in the code:
https://github.com/deepmind/deepmind-research/blob/769bfdbeafbcb472cb8e2c6cfa746b53ac82efc2/perceiver/train/experiment.py#L192
I was wondering which value is correct?
Thanks in advance.

Hi, thanks for noticing and flagging this! We used RandAugment with a magnitude of 5 in all ImageNet experiments here. The value of 10 given in the paper is a typo: we'll fix it in the next draft we release.

Hi, @djaegle
Thanks for your clarification.
A similar question about learning rate here:
https://github.com/deepmind/deepmind-research/blob/769bfdbeafbcb472cb8e2c6cfa746b53ac82efc2/perceiver/train/experiment.py#L88
The paper said the 'a flat learning rate of 2e-3'.
I was also wondering which value is correct?


Need some help for i-cloud -find my iphone

hy thanks for your work, i need some help for do this..
-Activate device without albert
-turn off find my iphone
can u explain more about thanks in advace

Hi @genhack
Do you mean when you turn on your "find my iphone" this zxIpaServer will not work well?


[anchor-is-valid] Allow Object spread in href/specialLink values

We get this error Cannot read property 'expression' of undefined as eslint output when using
const a = {};
const foo = () => (
	<Link
		to={{
			pathname: '/bar',
			query: { ...a },
		}}
	/>
);

and .eslintrc:
{
	"extends": [
		"eslint:recommended",
	],
	"plugins": ["jsx-a11y"],
	"env": {
		"browser": true,
		"node": true
	},
	"parserOptions": {
		"ecmaVersion": 2018,
		"sourceType": "module",
		"experimentalObjectRestSpread": true,
		"ecmaFeatures": {
			"jsx": true
		}
	},
	"rules": {
		"no-unused-vars": "warn",
		"jsx-a11y/anchor-is-valid": ["warn", {
			"components": ["Link"],
			"specialLink": [ "to" ],
			"aspects": ["noHref", "invalidHref", "preferButton"]
		}]
	}
}

here's a passing test:
{
  code: '<Anchor hrefLeft={{ foo: { test: 1 } } }} />',
  options: componentsAndSpecialLinkAndNoHrefAspect,
},

and a failing test, when object spread is used (even with experimentalObjectRestSpread in parserOptions or babel-eslint as parser with the right .babelrc..):
{
  code: '<Anchor hrefLeft={{ foo: { ...{ test: 1 } } }} />',
  options: componentsAndSpecialLinkAndNoHrefAspect,
},

Message:
      A fatal parsing error occurred: Parsing error: Unexpected token ...

I reported the error in eslint originally: https://github.com/eslint/eslint/issues/9960#issuecomment-365179752
@AlmeroSteyn I can try to solve it, if you have any advices maybe?

I'm also experiencing this.

This is an interesting request; a url is a string, and that’s what this is meant to enforce.
I think if react-router’s Link is sufficiently different from an <a>, then it warrants its own react-router-specific rule.

@caub Wow sorry somehow missed the @ CC
Yes, as @ljharb mentions, it was not built to cater for objects in the link prop.
The React Router Link component renders to an accessible <a> tags and the to prop is guarded with a prop-type isRequired declaration and, when omitted, it will be reported on by React itself as can be seen on the following console capture:

I am not sure if this should be double checked by this linter as when the React error is dealt with, an accessible <a> will be rendered.
Thoughts?

I created a repo repo with this issue before I realized there was already any issue. Here's the link if it helps anyone:
https://github.com/justinanastos/eslint-plugin-jsx-a11y-anchor-is-valid-error

That being said, I'd like to throw my opinion into the ring: whether or not this rule should accurately  lint the to={[ Object ]} case, this lint plugin should not crash eslint. I think that would mean that using to={[Object ]} would make this rule incompatible with aspects: ['invalidHref'], which completely makes sense. One can chose to not include the invalidHref aspects in their configuration as long as this rule doesn't crash. Right now, if you include Link in components and then ever use an object in to=, this will crash eslint regardless of the other configuration options.
If the maintainers are interested in a workaround, I'd be happy to submit a PR; I just need some guidance on what would be acceptable.

I absolutely agree that it should not crash the plugin; a PR that prevents that (without silently allowing code that failed to pass before) would be great.

Any updates on this?

No, nobody’s submitted a PR yet.

Possibly related to https://github.com/evcohen/jsx-ast-utils/issues/69. Workaround involves extracting to into a variable and passing that variable to the component prop; e.g.:
const a = {};
const to = {
  pathname: '/bar',
  query: { ...a },
}
const foo = () => <Link to={to}/>;

Admittedly, not all that practical if you have a lot of spread objects in to props.

This one is really throwing me for a loop. I tried updating the parser config, but that doesn't solve the parser error. Updating eslint doesn't solve it either:
{
  extends: [
    "airbnb-base",
    "plugin:flowtype/recommended"
  ],
  parser: "babel-eslint",
  parserOptions: {
    ecmaVersion: 2018,
    ecmaFeatures: {
      experimentalObjectRestSpread: true,
    }
  },
}

Has anyone figured out the magical incantation to at least get the code to parse? Then I can fix the code error that occurs after that.

Alright, this should get the test runner to at least parse the failing case. Now to fix the failing case :)
#573

I think https://github.com/evcohen/jsx-ast-utils/pull/74 solves the Cannot read property 'expression' of undefined error that @caub notes in the OP.

Nice if it get fixed!
ps: I wonder if the spread error still happens with:
const a = {};
const foo = () => (
	<Link to={'/bar?' + new URLSearchParams({ ...a })} />
);

I guess it does

I've got a pull against jsx-ast-utils to resolve the error: https://github.com/evcohen/jsx-ast-utils/pull/75

@caub yes, that element pass as well with the fix:
./node_modules/.bin/jest ./__tests__/src/rules/anchor-is-valid-test.js
 PASS  __tests__/src/rules/anchor-is-valid-test.js
  anchor-is-valid
    valid
      ✓ <Link to={"/bar?" + new URLSearchParams({ ...a })} /> (59ms)

Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshots:   0 total
Time:        1.126s, estimated 2s


cjxl_ng: replace gflags

In the current cjxl, we also do our own flag parsing, but we basically write directly to a jxl::CompressParams. In cjxl we want to use JxlEncoderFrameSettingsSetOption to set most of the options. However we want to maintain a distingtion between setting a flag to true or fals and not setting it (implying default values, possibly depending on other settings).
Right now we do this by using jxl::Override and tracking if some arguments have been set by watching using variables with names opt_foo_id.


getting some NameError exceptions when my Rails app is first started up

Two days ago I updated my app.  I went from:

acts_as_taggable (master branch, which I was running since December 22nd in order to get Rails 7 support)
Ruby 3.0.1
Rails 7.0.0

to

acts_as_taggable 9.0.1
Ruby 3.1.0
Rails 7.0.1

Once I did that I started seeing errors like this in my exception tracker:
NameError: constant ActsAsTaggableOn::Core not defined
NameError: constant ActsAsTaggableOn::Cache not defined
NameError: constant ActsAsTaggableOn::Ownership not defined
They were very infrequent and I could not reproduce them when clicked the URLs that initially triggered them.  Today I manually restarted my Heroku web dyno and immediately saw a couple of these exceptions come through.  So it seems that something isn't getting loaded properly / fully/ quickly enough when the app starts up.
Here's one of the stack traces:

1
File "/app/vendor/bundle/ruby/3.1.0/gems/acts-as-taggable-on-9.0.1/lib/acts_as_taggable_on/taggable.rb" line 115 in taggable_on
2
File "/app/vendor/bundle/ruby/3.1.0/gems/acts-as-taggable-on-9.0.1/lib/acts_as_taggable_on/taggable.rb" line 41 in acts_as_taggable_on
3
File "/app/vendor/bundle/ruby/3.1.0/gems/acts-as-taggable-on-9.0.1/lib/acts_as_taggable_on/taggable.rb" line 17 in acts_as_taggable
4
File "/app/app/models/equity.rb" line 114 in class:Equity

And like 114 in equity.rb just has acts_as_taggable
I'm not sure if Rails or Ruby changed something to cause this but I'm not seeing any similar errors from any other gems I'm using. So I just thought I'd post to see if anyone else is having this issue.

I also have these problems sporadically. Not every time when starting a web dyno on Heroku so probably it depends on the random order in which classes / modules are loaded
constant ActsAsTaggableOn::Core not defined
and also undefined method `all_tags_list_on'

Does anyone has any idea of the source of this problem?


Add original position in onDragStart

When the onDragStart event is trigerred, the position of the sprite has
already changed if the lockCenter is activated. So it's impossible to
know the original position of the sprite.
The new parameter give the position in all the cases.
See http://www.html5gamedevs.com/topic/12025-get-original-position-when-dragging-with-lockcenter/

I'm going to do this slightly differently, but nice idea all the same, so consider it merged locally.


[FLINK-15522][runtime] JobResult takes ExecutionGraph failure cause as its failure cause only if job is FAILED

What is the purpose of the change
In JobResult#createFrom it sets the latest global failure cause of the ExecutionGraph to be the cause of the JobResult if the job is terminated but not FINISHED.
So if the job is CANCELED and any global failure had ever happened, the latest global failure cause would be shown as the root cause of the canceling. This results in a misleading root cause exception when a user cancels the job.
Brief change log

Changed JobResult to take ExecutionGraph failure cause as its failure cause only if the job is FAILED
also checked the failure cause to be not null if a job is FAILED

Verifying this change
This change added tests and can be verified as follows:

Fixed testCancelledJobThrowsJobCancellationException
Added testFailureResultRequiresFailureCause

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Thanks @tillrohrmann. Will try to backport the fix to release-1.9.
Merging.


Updated docs

Updated docs to reflect support for all external packages in miniconda environment. Removed prompt marker in code blocks.

Sorry @jmunroe I must have forgotten to actually issue a pull request. I'll merge this so Steve can see the updated docs


Sanity check on EBS volume attachment

The application checks to see if an ESB volume exists, but doesn't check if it's available. If the volume is attached to another instance already then the provisioning will fail.
We already have a reference to the boto.ec2.volume.Volume object. It should be easy enough to check AttachmentSet.status.

PR https://github.com/awslabs/cfncluster/pull/243


Merge column not working anymore

When I try to show "Merge" as additional column it crashes:

Error message:

Request Method:
GET

https://pmb.acdh.oeaw.ac.at/apis/entities/entity/place/list/?columns=lat&columns=merge&name=&kind=&related_entity_name=&related_relationtype_name=&lat=&lng=&Filter=Filter

2.2.11

Exception

Could not find field in entity: Place of column (probably defined in 'table_fields' settings): merge

/apis/apis-webpage-base/apis_core/apis_entities/tables.py in Meta, line 84

/usr/local/bin/python

3.8.8

['/apis/apis-webpage-base',  '/usr/local/bin',  '/usr/local/lib/python38.zip',  '/usr/local/lib/python3.8',  '/usr/local/lib/python3.8/lib-dynload',  '/usr/local/lib/python3.8/site-packages',  '/apis/apis-webpage-base/src/drf-spectacular',  '/apis/apis-webpage-base']

Do, 29 Apr 2021 11:28:06 +0000

It is not necessary to have this function as it tempts to merge entries that are only similar on the surface. So my solution would be to do it away here.


failed to run piqa test with sym_int4 precison by harness

(env_p311) C:\AIGC\llama\ipex-llm\python\llm\dev\benchmark\harness>python run_llb.py --model ipex-llm --pretrained "C:\AIGC\hf\Meta--Llama-3-8B-Instruct" --precision sym_int4 --device xpu --tasks piqa --batch 1 --no_cache
Could not import signal.SIGPIPE (this is expected on Windows machines)
C:\ProgramData\anaconda3\envs\env_p311\Lib\site-packages\torchvision\io\image.py:13: UserWarning: Failed to load image Python extension: 'Could not find module 'C:\ProgramData\anaconda3\envs\env_p311\Lib\site-packages\torchvision\image.pyd' (or one of its dependencies). Try using the full path with constructor syntax.'If you don't plan on using image functionality from torchvision.io, you can ignore this warning. Otherwise, there might be something wrong with your environment. Did you have libjpeg or libpng installed before building torchvision from source?
warn(
2024-05-08 13:50:54,841 - INFO - intel_extension_for_pytorch auto imported
Selected Tasks: ['piqa']
Special tokens have been added in the vocabulary, make sure the associated word embeddings are fine-tuned or trained.
Loading checkpoint shards: 100%|████████████████████████████████████| 4/4 [00:00<00:00,  8.79it/s]
2024-05-08 13:50:55,690 - INFO - Converting the current model to sym_int4 format......
Using the latest cached version of the dataset since piqa couldn't be found on the Hugging Face Hub
2024-05-08 13:51:38,088 - WARNING - Using the latest cached version of the dataset since piqa couldn't be found on the Hugging Face Hub
Found the latest cached dataset configuration 'plain_text' at C:\Users\Administrator.cache\huggingface\datasets\piqa\plain_text\1.1.0\2e8ac2dffd59bac8c3c6714948f4c551a0848bb0 (last modified on Tue Apr 23 15:09:12 2024).
2024-05-08 13:51:38,097 - WARNING - Found the latest cached dataset configuration 'plain_text' at C:\Users\Administrator.cache\huggingface\datasets\piqa\plain_text\1.1.0\2e8ac2dffd59bac8c3c6714948f4c551a0848bb0 (last modified on Tue Apr 23 15:09:12 2024).
Task: piqa; number of docs: 1838
Task: piqa; document 0; context prompt (starting on next line):
Question: Remove seeds from  strawberries
Answer:
(end of prompt on previous line)
Requests: [Req_loglikelihood('Question: Remove seeds from  strawberries\nAnswer:', ' Blend the strawberries, pour the mixture through a fine-mesh strainer with a bowl underneath to catch the pulps and strain out the seeds')[0]
, Req_loglikelihood('Question: Remove seeds from  strawberries\nAnswer:', ' Chop up the strawberries, pour the mixture through a fine-mesh strainer with a bowl underneath to catch the pulps and strain out the seeds')[0]
]
Running loglikelihood requests
9%|█████▎                                                    | 337/3676 [05:33<55:02,  1.01it/s]
Job config of task=piqa, precision=sym_int4 failed. Error Message: unsupported dtype, only fp32 and fp16 are supported
Here are results of all successful tasks:
Traceback (most recent call last):
File "C:\AIGC\llama\ipex-llm\python\llm\dev\benchmark\harness\run_llb.py", line 150, in
main()
File "C:\AIGC\llama\ipex-llm\python\llm\dev\benchmark\harness\run_llb.py", line 146, in main
raise RuntimeError('\n'.join(fail))
RuntimeError: Job config of task=piqa, precision=sym_int4 failed. Error Message: unsupported dtype, only fp32 and fp16 are supported

100%|██████████████████████████████████████████████████████████████████████████████████████| 3676/3676 [04:18<00:00, 14.
24it/s]
{
  "results": {
    "piqa": {
      "acc": 0.7665941240478781,
      "acc_stderr": 0.009869247889521012,
      "acc_norm": 0.7731229597388466,
      "acc_norm_stderr": 0.009771584259215168
    }
  },
  "versions": {
    "piqa": 0
  },
  "config": {
    "model": "ipex-llm",
    "model_args": "pretrained=/mnt/disk1/Meta-Llama-3-8B-Instruct,load_in_low_bit=sym_int4",
    "num_fewshot": 0,
    "batch_size": "1",
    "batch_sizes": [],
    "device": "xpu",
    "no_cache": true,
    "limit": null,
    "bootstrap_iters": 100000,
    "description_dict": {}
  }
}
Here are results of all successful tasks:
{'model': 'ipex-llm', 'model_args': 'pretrained=/mnt/disk1/Meta-Llama-3-8B-Instruct,load_in_low_bit=sym_int4', 'num_fewshot': 0, 'batch_size': '1', 'batch_sizes': [], 'device': 'xpu', 'no_cache': True, 'limit': None, 'bootstrap_iters': 100000, 'description_dict': {}}
|Task|Version| Metric |Value |   |Stderr|
|----|------:|--------|-----:|---|-----:|
|piqa|      0|acc     |0.7666|±  |0.0099|
|    |       |acc_norm|0.7731|±  |0.0098|

Hi, the above is my test result, I did not encounter the situation you said. Here is my env, please try checking you env and other settings.
-----------------------------------------------------------------
-e PYTHON_VERSION=3.11.9
-----------------------------------------------------------------
transformers=4.37.0
-----------------------------------------------------------------
torch=2.1.0a0+cxx11.abi
-----------------------------------------------------------------
ipex-llm Version: 2.1.0b20240509
-----------------------------------------------------------------
ipex=2.1.10+xpu

Device Name: Intel(R) Data Center GPU Max 1100

I used the MTL iGPU, not Data Center GPU. might you please have a try on MTL? if you need env, I can share my env to you.
thanks

BTW: today, when I tried to update the lib, it appears some error, please refer the capture for details.

I can't update transformers to 4.37.0, it remains to 4.31.0, which one I should use?
thanks a lot,

set BIGDL_QUANTIZE_KV_CACHE=0

The default setting for mtl is to enable the quantize kv cache. In the model, llama_attention_forward_4_36_quantized is used where key_states and value_states are updated with inputs that are in bf16 format, which leads to an issue with append_fp8_kv_cache. The method linear_q4_0.quantize_key_value(key, value) also receives bf16 inputs. However, MTL lacks native support for bf16, which is required by the new rms norm kernel, resulting in an error. Since fp16 is faster than bf16, there is no need to add bf16 support. This issue does not occur on arc. On mtl, setting IPEX_LLM_QUANTIZE_KV_CACHE=0 (previously BIGDL_QUANTIZE_KV_CACHE) can avoid this problem. Alternatively, converting key and value to fp16 before passing them to append_fp8_kv_cache linear_q4_0.quantize_key_value can also resolve the error.

In the llama3 model, the dtype for the key and value values passed into linear_q4_0.quantize_key_value defaults to bf16. However, MTL does not have native bf16 support, so this will cause an error.
On Arc, QUANTIZE_KV_CACHE is not enabled by default, whereas it is on MTL. Thus, this method does not produce an error on Arc.
When running the benchmark harness on MTL, setting IPEX_LLM_QUANTIZE_KV_CACHE=0 (previously BIGDL_QUANTIZE_KV_CACHE) can avoid this issue. Alternatively, converting key and value to fp16 before passing them to ‘linear_q4_0.quantize_key_value’ can also resolve the error.


Improve yaml parse error handling

I was unable to find an attribute on ScannerError for the name of the file being parsed.  I included "likely cumulusci.yml" in the error messaging, because we can't be sure which call to handle_exception() is being invoked.
Changes

CumulusCI displays more user friendly error message when encountering parsing errors in cumulusci.yml.

@davisagli @prescod - I removed the class to make things more pytest-like (also added a fixture to clean up cumulusci.yml file creation).  The outp has 12 spaces between \n and y: where as the value for rc has 10 spaces between \n and y:, but no code changed there.

@davisagli @prescod - I removed the class to make things more pytest-like (also added a fixture to clean up cumulusci.yml file creation).  The outp has 12 spaces between \n and y: where as the value for rc has 10 spaces between \n and y:, but no code changed there.

@Br4nd0R fwiw, I don't see organizing tests into classes as antithetical to pytest's approach -- but I don't feel strongly about whether we do so or not.
The failing test is because you changed the indentation inside the triple-quoted string.

@Br4nd0R fwiw, I don't see organizing tests into classes as antithetical to pytest's approach -- but I don't feel strongly about whether we do so or not.
The failing test is because you changed the indentation inside the triple-quoted string.

The failing test is because you changed the indentation inside the triple-quoted string.

The failing test is because you changed the indentation inside the triple-quoted string.


setup publishing to apache nexus

lgtm. Will also need to add the DISCLAIMER file using the sbt-apache-sonatype plugin similarly to how it was done with pekko-core but that can be done seperately.

That already seems to be working out of the box!?

lgtm. Will also need to add the DISCLAIMER file using the sbt-apache-sonatype plugin similarly to how it was done with pekko-core but that can be done seperately.

That already seems to be working out of the box!?

Its implemented manually in https://github.com/apache/incubator-pekko-http/blob/main/project/MetaInfLicenseNoticeCopy.scala#L16-L29 but sbt-apache-sonatype handles this for you as well, see https://github.com/apache/incubator-pekko/blob/main/project/AddMetaInfLicenseFiles.scala#L18-L42 (note that apacheSonatypeDisclaimerFile is optional)

Its implemented manually in main/project/MetaInfLicenseNoticeCopy.scala#L16-L29 but sbt-apache-sonatype handles this for you as well, see<EMAIL_ADDRESS>(note that apacheSonatypeDisclaimerFile is optional in the plugin which is why we need to specify it in Pekko projects).
As mentioned before, this makes sense to do in another PR since its not directly related.

Ah, I see, we could basically simplify. Let's do that later, indeed.

Test run at apache/incubator-pekko-http/actions/runs/4173990714

which seems to run in general but in this case errored out with a 502 from the Apache Nexus...


Develop create rule command & add modify_rule command

For the moment, a role is defined by the number of a given token the users own.
We want to add the possibility to define more complex rules with combination of tokens.
For instance, we would like to be able to add a rule that grant the status of knight if you own at least one NFT armor, one NFT sword and one NFT horse.
Moreover, we want to be able to modify some rules already created by adding a new command. This new command must be named /starkbot-modify-rule

@gaetbout is working on this issue
OnlyDust link : https://app.onlydust.xyz/contributions/0x007f


Fix issues with enumerators

Fixes issues mentioned in the discussion of #31.

[x] Restricts specialization
[x] Conforms to styleguide, part 1
[ ] Conforms to styleguide, part 2
[x] Adds block-based constructor

Once I've addressed the third issue, I'll add it to this PR.

LGTM


Automatically call "to tabs" after accepting diff depending on detected indentation of file

Validations

[X] I believe this is a way to improve. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that requests the same enhancement

Problem
Indentation type does not match user selection, which is a problem in python.
Solution
Process the AI generated code to replace indentation with the detected indentation of the file (provided by the IDE)

"to tabs" being the Jetbrains action

This is on our radar, thanks for the +1 here!


Disable hand rays by default in MRTK3 eye gaze examples

Describe the bug
Disable hand rays by default in MRTK3 eye gaze examples.  The hand rays get in the way, and prevent some of the demos from working correctly (like the EyeTrackingTargetPositioning example)

Fixed with

https://github.com/microsoft/MixedRealityToolkit-Unity/pull/11744


akalink table, UI, and shader

contribution includes a new pool table, a reorganized menu, and a special color menu and shader to allow players to customize the color of the pool table balls.
new pool table - overall lower poly and with more mirrored textures for less resolution loss when crunched to lower resolution.
new shader - a custom shader that uses masks to remove existing color and overlay a custom color. Includes a float within the shader to transition between using the texture and the color override.
new menu panel - a UI panel with preset colors and HSV sliders. Prefabed so it can be added to any existing menu.
unused UI for a 2 color vs multicolor balls switch. I tried to implement this, but was unsuccessful.
prefabs has been set up to fit the existing prefabs and how their nested prefabs work.
other notes:
The code on the pool state manager has been edited to include shader properties and related variables, a bool toggle, and a connection to the behaviors. The code is liberally commented, always started with "akalink added" or "akalink edited". The behavior will leave a message if the system is toggle on without connection to the color panel behaviors (color picker). A work around for a strange audio bug is also included. (I'll cover this later)
The code on the FSP Udon Activator has been edited to include support to triggering audio. This is used to add a sound to interactions on the menu.
The code on the pool menu has been edited to change various hard coded strings into public strings, this is to allow individual versions of the pool table to have differing text on the respective messages.
Bugs:
A bug revolving around the timer option has sprung up. Whenever the timer variable is incremented, or decremented, a version of the menu interact sound with excess reverb will play. It plays on the audio source attached the core table code. A work around has been implemented that turns off the audio source a line before the variable is either incremented or decremented. The audio source is turned back on before the game actually starts.

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

Nice addition, but you will have to sign the CLA before it can be merged.

I do like it myself, but is it possible to add in the UI to disable the Custom Color changes and render just as the regular 8-ball? Would be a nice addition with the new UI for those who want to do the "get real" 8-ball experience.


usage segmentation

Task/Issue URL: https://app.asana.com/0/392891325557410/1206955287217877/f
Tech Design URL: https://app.asana.com/0/392891325557410/1208090005627335/f
CC:
Description:
This PR ads usage segmentation calculations to the app so that we can monitor usage across segments in a private way, without having to send granular usage information to the server.
Deviation from tech design:

Added "Calculation" class / protocol in order to encapsulate the calculation logic exclusively and code it so that it's similar to the python implementation.

Steps to test this PR:
First run, new user:

Reset the simulator (so that the keychain is cleared)
Run the app
No m_retention_segments pixel should be fired

Subsequent run a few days later

Reset the simulator (so that the keychain is cleared)

Modify StatisticsLoader add the following line at the start of the load function:
     self.statisticsStore.atb = "445-1"

Run the app

An assertion failure should crash the app saying this is not a valid ATB.

Update the above line as follows and reset the simulator again:
     self.statisticsStore.atb = "v445-1"

Ensure that m_retention_segments pixel is fired. There will be various parameters but one should indicate "app_use" activity

Re-launch the app

No additional pixel should be fired

Perform a search

The pixel will be fired again and there should be a parameter indicating search activity.

Perform another search

No additional pixel should be fired

Return user test

Repeat the above test bit with the following atb.  The pixels sent should include reinstaller in the segments parameter.
     self.statisticsStore.atb = "v445-1ru"

Definition of Done (Internal Only):

[x] Does this PR satisfy our Definition of Done?

LGTM @brindy . Still a unit test failing - SyncManagementViewModelTests.testWhenSaveRecoveryPDFPressed_recoveryMethodShown(), which I assume is unrelated.


Reduce runtime

When checking for updates, particularly on large projects with many top-level dependencies, and several repositories, the majority of the runtime is spent querying remote servers for version information. By running these queries in parallel we make checking for updates a lot faster.
Caveats:

~I've not tested this with git dependencies, but I'm assuming those checks are also threadsafe~ Reading the code, it looks threadsafe to me. Also, testing on the test alias in the project gives the same results for olical/cljs-test-runner before and after the change.
~Since the code for --update uses a different and more complex looping mechanism, it does not receive any speed improvements from this change.~ Pushed commits expanding the speed up to the --update code as well.

Damn this is really cool, thank you very much! I've looked over the commits and am happy, will just give it a test locally before merging, great work! :clap:

Excellent, no difference other than much faster. Great work, thank you very much!


[Bug-RD][UI Next][V1.0.0-Alpha]query plugins result is null

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
query plugins result is null

What you expected to happen
Successfully acquire data and display
How to reproduce
1、Click  Security
2、Click  Alarm Instance Manage
3、Then it will show query plugins result is null
Anything else
No response
Version
dev
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

sorry, I can't reproduce at local.

@songjianet I found you had assigned yourself, so this is a bug of FE?

This error message from '/dolphinscheduler/ui-plugins/query-by-type?pluginType=ALERT', due to no plugin defined in table 't_ds_plugin_define'. I have copy one row from ds 204 env and this error won't show again. But cause alert instance creation problem and will check soon.

I have figured out this problem is due to no alert plugins data in table 't_ds_plugin_define'. You need to run the alert-server so that it will generate alert plugins and you move forward. I think this is not a bug.


fix 2417

related to issue https://github.com/containers/youki/issues/2417

@utam0k Sorry i think i linked the wrong issue. I changed it to the correct one just now.
also, a lot of explanation was done in the issue comments

@zahash Thanks for your update, but it's not enough information to start by reviewing it. Apparently, the title of the PR is wrong.

@zahash ping!

@utam0k @YJDoc2
i have changed the title.
the idea is, OwnedFd cannot be cloned. so before switching to OwnedFd, we have to make sure no cloning is done.
the next step would be to use OwnedFd inside sender and reciever instead of RawFd

💯

the idea is, OwnedFd cannot be cloned. so before switching to OwnedFd, we have to make sure no cloning is done.


cache Cargo artifacts

:pushpin: Commit a020866 has been approved by japaric

@homunkulus r+

:hourglass: Testing commit a020866 with merge a020866...

:broken_heart: Test failed - status-travis

@homunkulus r+

:pushpin: Commit 5b46164 has been approved by japaric

:hourglass: Testing commit 5b46164 with merge 5b46164...

:pushpin: Commit 2b7021a has been approved by japaric

@homunkulus r+

:hourglass: Testing commit 2b7021a with merge 2b7021a...

:broken_heart: Test failed - status-travis

@homunkulus r+

:pushpin: Commit 07f0b0d has been approved by japaric

:hourglass: Testing commit 07f0b0d with merge 07f0b0d...

:broken_heart: Test failed - status-travis

@homunkulus r+

:pushpin: Commit 1572c88 has been approved by japaric

:hourglass: Testing commit 1572c88 with merge 1572c88...

:sunny: Test successful - status-appveyor, status-travis
Approved by: japaric
Pushing 1572c88eb77ed3c2c19541c76d7b791d4e4e8fcb to master...