Windows Add-Remove Programs should show full release level

Currently shows "Deployment Framework for BizTalk 5.0".  Shouldn't it show 5.0.16Beta for instance?  If not, how does a person easily know what release he is on.
This work item was migrated from CodePlex
CodePlex work item ID: '6688'
Vote count: '1'

[tfabraham@5/20/2010]
In general, most applications do not show a full version number in the title in Add/Remove Programs.  The full version number is available by selecting the Deployment Framework for BizTalk item, then clicking the Support Information link on XP, or on Vista/7/2008 by adding the Version column to the Programs list.

[UnknownUser@5/21/2010]

[UnknownUser@2/21/2013]

[UnknownUser@5/16/2013]

Issue closed by tfabraham with comment
See previous comment


Deprecate scale-generator

See https://forum.exercism.org/t/scale-generator-tests/8236/1

@BNAndras I'm not sure what to do with this yet.  I can see that it can be a hard toy problem for some students, and it isn't in the best shape, but I also think that to deprecate means invalidating a lot of solutions that have been done for this problem.

As shown in the forum and described in the documentation, there is no invalidation of solutions (if that means they are lost for the students or students loose reputation earned). The exercise will be hidden for new students only.
If there is no other reason not to deprecate this exercise, I suggest: Let's get that merged!

@BNAndras I can't rebase this branch to fix the formatting issues. Do you want to rebase your branch or should I close this and deprecate the exercise in a new PR?


ListStore missing functions, such as the remove

ListStore missing functions,such as the remove

http://gtk-rs.org/docs/gtk/struct.ListStore.html#method.remove
https://github.com/gtk-rs/gtk/blob/master/src/auto/list_store.rs#L99
May be you using old package?

I am using  the 0.1.2 version. i know, lastest version  hasn't push.

Then it have remove.
Can you show code and error it produced?

There is no error, I'm going to use the remove function.
Thank you!


Date.FormatStyle does not autoupdate when 12-24 hour preferences changes when using autoupdating locale

We cache the generated date format per Date.FormatStyle. Normally Date.FormatStyle's locale change would result in a cache miss because the hash has changed. However, using .autoupdating is an edge case where this does not apply -- Locale.autoupdating always compares equal to itself even when the locale identifier or preferences are different. Therefore we end up fetching the stale value when the locale is .autoupdating.
Fix this by using the locale identifier instead of the locale instance as the hash key.
Follow up: encapsulate hour preferences in the locale identifier instead of setting it as a special override. We should use this pattern wherever possible.

@swift-ci please test


Module not found: Error: Cannot resolve module 'babel-loader'

I'm using webpack in directory /users/path/a/(it holds the webpack.config.js) and compile files in directlry /another/path/b/. I run gulp webpack task in path a, and it will compile all the files in path b using absolute path.
Then I got Cannot resolve module 'babel-loader' error.
After looking at https://github.com/webpack/webpack/issues/784, I tried resolve.fallback, resolve.root, but neither works. Thanks for all kinds of help.

Finally I tried resolveLoader and it works.
My configuration is as follows:
resolveLoader: {
      modulesDirectories: [
          '/users/path/a/node_modules'
      ]
},

better use resolveLoader.root for absolute paths. see documentation hint.

Changed to resolveLoader.root
BTW, it's hard to find resolveLoader.root in the documentation. the IMPORTANT is not so outstanding

Thanks for the thread guys! Agree with @camsong it's better to highlight the IMPORTANT section there.

Thks @camsong , I also packed as webpack config in a node cli package

For those looking to have some copy pasta:
resolveLoader: {
  root: path.join(__dirname, 'node_modules')
}

From the image posted by @camsong as pulled from the docs

For those looking to have some copy pasta:
resolveLoader: {
  root: path.join(__dirname, 'node_modules')
}

Pulled from the docs and the image as posted by @camsong. Thanks for figuring it out.

And, why do I need to add resolveLoader? Shouldn't it work without? Why doesn't it?

I am having this same problem but it seems like resolveLoader.root is now deprecated. Can anyone point me in the right direction? There's a lot of conflicting information around!

Kevinreilly - I tried the suggestion you gave. I can see where you found it in the docs, but it produces this error for me:  Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.

configuration.resolveLoader has an unknown property 'root'. These properties are valid:
object { alias?, aliasFields?, cachePredicate?, descriptionFiles?, enforceExtension?, enforceModuleExtension?, extensions?, fileSystem?, mainFields?, mainFiles?, moduleExtensions?, modules?, plugins?, resolver?, symlinks?, unsafeCache?, useSyncFileSystemCalls? }

@MincePie after researching your error it seems like the solution above is for Webpack v1 and that it may have changed for v2. I've not used v2 so this is just a guess from the migration guide:
  resolve: {
   modules: [
     path.join(__dirname, "src"),
     "node_modules"
   ]
  }

For more information, see Migrating from v1 to v2

In my case my node_modules folder is in a different location, and only modifying resolve.modules didn't work well with webpack-dev-server.
This worked for me:
resolveLoader: {
    modules: ['/path/to/node_modules'],
},
resolve: {
    modules: ['/path/to/node_modules'],
}

I am using webpack 4.
I solved my "module not found" error finally! by using the loader option "includePaths":
    module: {      rules: [   {                 test: /\.(scss)$/,                 use: [                     {                         loader: 'sass-loader',                         options: {                             includePaths: ['./node_modules'] }                     }                 ]             }         ]     },
All "resolve" and "resolveLoader" and other solutions offered in this thread did not work.
Hope this helps anyone :)
My folder structure:
--node_modules
--src
webpack.config.js
package.json

FTW:
yarn add --dev babel-loader
npm i --save-dev babel-loader


In basic auth check for tokens before call UserSignIn (#5725)

Backport #5725

@techknowlogick really need this one to get out asap... drone is unusable with AD server with user locking on unsuccessful auths as on every build it blocks users :(

@lafriks ok, as we haven’t published blog post yet I think we can get this one in to 1.7.2


Added check if the delete-icon should appear.

Description
Please describe your pull request:

Why is it necessary?

Without this it would be possible to delete the last price-entry of an article.

What does it improve?

Adds a check if the delete-icon should appear.

Does it have side effects?

No.

Questions
Answers

BC breaks?
no

Tests pass?
pending

Related tickets?
No

How to test?
Open article in backend. Click into the "to"-field in the price-table. Click away. Without this fix, there should now be a delete-icon next to the only price-entry. If that does not appear, this works.

In the prices-table you could delete the last remaining price if you clicked on the "to"-field and then clicked away without entering anything. This commit fixes that.

Thanks @jkrzefski
We decided to close this PR because the change is incomplete and does not fix the underlying issue. If this change is still important to you, feel free to create a new pull request or create an issue on https://issues.shopware.com.

@janbuecker Could you tell me what is needed to fix this issue? Maybe then I can do some more work on this PR soon.


Error 2000 After running ofx_create_new_usaa_bank_custom_profile.py

I've re-ran this 3 times. High confidence that I did everything correct. Cannot interpret the console messages beyond knowing I'm getting Error 2000 and Error 15500. I've double and triple checked the information from the USAA Quicken access page. I don't type anything, I copy/paste everything and ensure I don't have leading or trailing characters. Not sure what to do next. I'm hoping you have some bandwidth to devote to this and help me.
I don't have a VPN running and while I use cookie blocker extensions in the browser I use (Brave), I don't have any other form of web blocking going on that I'm aware of. Windows 10 OS. I don't believe it's possible for the web browser extensions to work outside of the web browser, but I'll be testing that to see if uninstalling all extensions helps. Low confidence it will help, but I'm trying anything at this point.
Internet Options are configured to accept session, first and third party cookies.
I can provide the console output outside of this forum if needed.

Where are we at with this now..? About 60+ other people have usaa working. Is yours?

It’s working by using hleOFXQuotes, but NOT from within Moneydance.
I’ve tried everything I can think of and have spent a bunch of time redoing the script, trying with a different data file with only USAA. Still keep getting the Error 2000.
At this point I’ve spent an unreasonable amount of time trying to get it to work, so I’m done. hleOFXQuotes will be what I use moving forward, until it doesn’t work any longer.
Thanks for the help and following up, but I’m done trying to get it to work.
Thank you,
RJ
From: yogi1967 @.>
Sent: Monday, June 14, 2021 10:09 PM
To: yogi1967/MoneydancePythonScripts @.>
Cc: rjbarber @.>; Author @.>
Subject: Re: [yogi1967/MoneydancePythonScripts] Error 2000 After running ofx_create_new_usaa_bank_custom_profile.py (#16)
Where are we at with this now..? About 60+ other people have usaa working. Is yours?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/yogi1967/MoneydancePythonScripts/issues/16#issuecomment-861173923 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ACPVPI2WQBHGNBPPAIHFABLTS3N77ANCNFSM435POHVQ .  https://github.com/notifications/beacon/ACPVPI3X2XVVWPDUSRBBODTTS3N77A5CNFSM435POHV2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGNKHRIY.gif

Glad you have it working somehow. That’s the main concern.


General Stamp Deployment Fixes

This represents a collection of fixes to enable seamless bootstrap of the OXA Stamp.

Thanks


Run through test drive

If it doesn't work, don't do the blog post yet
Any failures are P0 blocking bugs

FWIW, it worked for me!

Closing as this works now.


Inventory Demo

Hi Ryan,
I am very happy to see new ScriptableObjects stuff. There are limited source when its come to architecture in unity. In your presentation demo I saw inventory in project root. Sadly, you had not enough time to show on unite event. I would like to see what you were to present about inventory.
Thank you

+1

https://github.com/roboryantron/Unite2017/commit/4894cb1e8a471793e424a17b6ca845321c6df71d

thank you! :D


Cleanup cranelift-frontend

This PR eliminates most of the per-block state tracked by the frontend module in cranelift-frontend. I think I can eliminate the last bits of state while preserving all the debug-assertions, but I want to think about that more.
I tried to keep the individual commits well-separated so it may be worth reviewing them individually.
This saves a tiny bit of memory allocations and traffic, according to DHAT, but has basically no impact on performance.

Thanks, @abrown!
I had verified that nothing in-tree called is_pristine or is_filled, but you've reminded me that I should check cg-clif, and... it also doesn't use those. So I think the answer to that question in particular is that it should be fine to remove pub.
Parts of this involved some reasoning that I found a little tricky, so I'd definitely appreciate more thorough review.


HDDS-4486. Feature Config : Make proper enableFSPaths and OFS optimized flag combinations

What changes were proposed in this pull request?
This jira proposal is to simplify the ofs optimization cases. OM can support FS optimization only if both are TRUE(ofsOptimized=true && enableFSPaths=true)
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4486
How was this patch tested?
Through existing test cases

@mukul1987  FYI, test case TestOzoneFileSystem#testTrash failure is unrelated to this PR, raised HDDS-4751 issue to address it.

@mukul1987  FYI, test case TestOzoneFileSystem#testTrash failure is unrelated to this PR, raised HDDS-4751 issue to address it.

@rakeshadr , I'm fine for this change, but one concern that does this change will break some logic in below 3 cases? I remember we considered and support these 3 cases when implemented ozone fs feature tasks before.

ofsOptimized=true && enableFSPaths=false
ofsOptimized=false && enableFSPaths=true
ofsOptimized=false && enableFSPaths=false

Thanks a lot @linyiqun for the reviews. Yes, we won't support all these three cases and support only if both the flags are TRUE. As we are exposing this feature freshly in the upcoming Ozone release, we can make it simple now and based on high user demands/usecases we can extend supporting complex modes. Now, this makes it clear to the users that OM supports either 100% FS mode(true) or 100% S3 mode(false). Like I mentioned in this patch, OM will expose this as a bucket level property. I will work on few more follow up tasks to ensure completeness (For ex: HDDS-4727).
Hope this makes sense to you.

@rakeshadr , I'm fine for this change, but one concern that does this change will break some logic in below 3 cases? I remember we considered and support these 3 cases when implemented ozone fs feature tasks before.

ofsOptimized=true && enableFSPaths=false
ofsOptimized=false && enableFSPaths=true
ofsOptimized=false && enableFSPaths=false

Thanks a lot @linyiqun for the reviews. Yes, we won't support all these three cases and support only if both the flags are TRUE. As we are exposing this feature freshly in the upcoming Ozone release, we can make it simple now and based on high user demands/usecases we can extend supporting complex modes. Now, this makes it clear to the users that OM supports either 100% FS mode(true) or 100% S3 mode(false). Like I mentioned in this patch, OM will expose this as a bucket level property. I will work on few more follow up tasks to ensure completeness (For ex: HDDS-4727).
Hope this makes sense to you.

Makes sense to me, : ).

Makes sense to me, : ).

Makes sense to me, : ).

Glad to see your reply, please let me know your feedback. Appreciate, if you could approve the PR. Thanks!

Makes sense to me, : ).

Glad to see your reply, please let me know your feedback. Appreciate, if you could approve the PR. Thanks!

Sorry, I've used wrong branch name 4658-01, instead of 4486-01, with some other jira issue number. Once all the review comments are fixed, then I will create fresh PR which can be used for merging. Hope that makes sense to everyone.

Sorry, I've used wrong branch name 4658-01, instead of 4486-01, with some other jira issue number. Once all the review comments are fixed, then I will create fresh PR which can be used for merging. Hope that makes sense to everyone.

Closing this PR as the branch name is wrong. Created new PR for commiting to the branch.
Thanks a lot @linyiqun and @mukul1987 for the useful review comments.

Closing this PR as the branch name is wrong. Created new PR for commiting to the branch.
Thanks a lot @linyiqun and @mukul1987 for the useful review comments.


added session 0

Hey Tharun! :partying_face:
Great work on both assignments - did you ever work in ruby before? You seem to know many of the ruby idioms

Hey Tharun! :partying_face:
Great work on both assignments - did you ever work in ruby before? You seem to know many of the ruby idioms


Provide Form.IconList and Form.Icon to display image

Provide Form.IconList and Form.Icon in Form to display image, as shown in the code below.
<Form.IconList title={"Form.IconList"}>
        <Form.IconList.Icon source={icon1} />
        <Form.IconList.Icon source={icon2} />
        <Form.IconList.Icon source={icon3} />
</Form.IconList>

Describe the feature and the current behavior/state.

Will this change the current API? How?
Yes. A new component api will be added to the Form
Who will benefit from this feature?
People who show and browse pictures in Form
Any Other info.

It's not really clear to me what this item will be used for.
Is it a file picker? Or is it a simple non-clickable item where you want to display an image?
Do we have something like that somehwere else in Raycast?


"[event.target.name] : event.target.value" name undefined

Hi,
i would like to handle changes on a Suneditor component using a state with "[event.target.name] : event.target.value" in my NextJS project but an error is shown saying "TypeError: Cannot read property 'name' of undefined". Suneditor component is inside a form tag with other inputs, and the only component that shows error is that one
If i shouldn't use "[event.target.name] : event.target.value", please let me know which is the best way to handle changes when Sunedit component is not the only input component, I dont mind at all if i must to change my syntax
I appreciate your help, i love Suneditor and i dont want to use another one, its an excellent Rich Text Editor component

@chuchunesumis Where did you use "[event.target.name]: event.target.value"?
Show me the function that used the code.

@chuchunesumis Where did you use "[event.target.name]: event.target.value"?
Show me the function that used the code.

thanks for the reply
i created a state like this:

Thanks for the reply, let me try to explain what i did:
This is my imports:
import SunEditor from 'suneditor-react';
import 'suneditor/dist/css/suneditor.min.css';
i made a useState like this:
const [datos, setDatos] = useState({
titulo: '',
urlimagen: {},
descripcion
});
To handle changes, this is the function:
const onChangeFormulario = e => {
setDatos({
...datos,
[e.target.name] : e.target.value
});
}
This is the SunEditor component:
<SunEditor
lang="es"
id="descripcion"
placeholder="Descripción del producto"
name="descripcion"
value={descripcion}
onChange={onChangeFormulario}
// onBlur={handleBlur}
setOptions={
{buttonList: [
['bold', 'italic'], []
]}}
/>
SunEditor component is inside a  tag along with an  named "titulo". If i replace SunEditor component for a  everything works fine, that's why i would like to know your opinion
Note: i temporarily fix this situation making another useState for SunEditor component's values and another function to handle changes for that component only, but i maybe thats not the best way to handle changes when a SunEditor component and some input tags are together in the same render

onChange doesn't have an event object.
http://suneditor.com/sample/html/out/document-user.html#onChange
If you need editor element, you can use "context".
editorInstance.core.context
http://suneditor.com/sample/html/out/document-editor.html#context


Patch: node is null error when events from other frameworks creep into famous

Firefox 40.0 is generating "node is null" errors when events from other frameworks bubble into Famous (for example, from D3).
The attached patch to Famous#DOMRenderer._getPath() fixes it. It's a patch against the built famous.js but it should be clear where the required change is and its purpose should make sense just from looking at the code.
Grab me on slack if you need more info.
Index: WarRoom/lib/famous-20150801-622461886b5162f8dc42f91483b04d758b507d72.js
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
--- WarRoom/lib/famous-20150801-622461886b5162f8dc42f91483b04d758b507d72.js	(revision 2ff2a6e3c886e5aca9b200d93c3d3159dd1f7430)
+++ WarRoom/lib/famous-20150801-622461886b5162f8dc42f91483b04d758b507d72.js	(revision )
@@ -8993,7 +8993,7 @@
     // TODO move into _triggerEvent, avoid object allocation
     var path = [];
     var node = ev.target;
-    while (node !== document.body) {
+    while (node && node !== document.body) {
         path.push(node);
         node = node.parentNode;
     }

Thanks. Do you want to submit a PR for this? Otherwise I'm going to fix this.

Sorry I missed your note. Just fix it directly, its a one line change.


Latest version of nr types causing module not found error

The latest version of nr.types doesn't have the nr.enum module, on which the program is dependent. It causes an error and the program can't be started.

Hey @ahmedsadman, please check out the current version in the develop branch.
I switched the code to using enum34 instead (or the standard enum module in Python 3.4+) but I couldn't test it yet (time + can't find my Myo atm).
(Probably should have added unit tests for these things at some point)

develop that no longer depends on the nr module was merged into master a while ago (tagged v1.0.4)


proxy is in cluster , but controller is for cluster Kubernetes

The New Feature
Istio 1.6.9 add this feature will check ClusterID. Now don't set, will print error
failed to get service proxy service instances: 1 error occurred:
	* proxy is in cluster , but controller is for cluster Kubernetes

Your scenes
Describe your use scenes (why need this feature).
Your advice
Describe the advice or solution of this new feature.
Environment

MOSN Version

It looks like a Istio prob with this issues


Quotes in JSX output are not properly escaped

Example test case:
console.log(typescript.transpileModule('var x = "hello"; <h1>"{x}"</h1>;', {
  compilerOptions: {
    jsx: 2, // React
  },
  fileName: 'test.tsx'
}));

Output:
'var x = "hello";\nReact.createElement("h1", null, """, x, """);\n'

The triple quotes in the generated output is wrong, it needs a backslash before the middle quote.

I do not see this on latest<EMAIL_ADDRESS>this is what i get:
{ outputText: 'var x = "hello";\r\nReact.createElement("h1", null, "\\"", x, "\\"");\r\n',
  diagnostics: undefined,
  sourceMapText: undefined }

O, fancy, yea, sorry I should have specified a version number, I was on
1.6.2 which is the latest stable release I think?
On Thu, Oct 29, 2015 at 5:31 PM, Mohamed Hegazy<EMAIL_ADDRESS>wrote:

I do not see this on latest<EMAIL_ADDRESS>this is what i get:
{ outputText: 'var x = "hello";\r\nReact.createElement("h1", null, "\"", x, "\"");\r\n',
diagnostics: undefined,
sourceMapText: undefined }
—
Reply to this email directly or view it on GitHub
https://github.com/Microsoft/TypeScript/issues/5463#issuecomment-152365624
.

it should be fixed in next release 1.7.3, and it is already fixed in nightlies (typescript@next).

Cool, thanks.  When (roughly) is the next release?
On Thu, Oct 29, 2015 at 5:40 PM, Mohamed Hegazy<EMAIL_ADDRESS>wrote:

Closed #5463 https://github.com/Microsoft/TypeScript/issues/5463.
—
Reply to this email directly or view it on GitHub
https://github.com/Microsoft/TypeScript/issues/5463#event-449903038.

We try to have a major release every 6-8 weeks. no hard dates yet, but should be a couple of weeks or so.

For future finders: #5132


GH-510 Pass class type initialization to New Object nodes

Fixes #510

Applied to main (=2.1) and branch 2.0.


Update wachter.py

Fixed Decision_Thresh in the while loop and removed logging to line up with the rest of methods.

Hi, thanks for submitting your PR! I'm not sure if logging should be removed. I would argue that rather logging should be added to the other methods instead.
Adding the DECISION_THRESHOLD is good.


issue-1959: make sure e gets default values if e is null

New Pull Request
Change in dist/apexcharts.common.js  at  a.Matrix.
In Firefox the value of e can be null. And because t(null) === "object" , e doesn't get default values but keeps being null.
create: function(e) {
     var i = p([1, 0, 0, 1, 0, 0]);
     e = e === null ? i :   //<-- additional test
           e instanceof a.Element ?  e.matrixify() :
           "string" == typeof e ?   p(e.split(a.regex.delimiter).map(parseFloat)) :
           6 == arguments.length ?  p([].slice.call(arguments)) :
           Array.isArray(e) ? p(e) :
           "object" === t(e) ? e : i;
     for (var s = v.length - 1; s >= 0; --s) { this[v[s]] = null != e[v[s]] ? e[v[s]] : i[v[s]] }
}

Fixes #1959
Type of change
Please delete options that are not relevant.

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

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Thanks for the contribution, I have added a check as per your suggestion.


Implement Jest Tests for JSON GENERATOR

The JSON GENERATOR currently lacks Jest tests. We need to add tests to ensure its functionality and reliability.
Tasks:

Identify the key functionalities of JSON GENERATOR.
Write unit tests for:

Component rendering
User interactions
Props and state management

Write integration tests for:

Any significant workflows (if applicable)

Ensure all tests pass in the local environment and CI/CD pipeline.
Update the documentation to include instructions on running the tests.

Acceptance Criteria:

Jest tests for JSON GENERATOR are created and passing.

Additional Information:

Any known issues or specific areas of concern related to JSON GENERATOR can be added here.

Hi @Bashamega, I've created a PR for this. May I be assigned this ticket too? Sorry, I forgot to ask beforehand. 🙂


Added Compression Support in Always Encrypted

Pull Request Template
Description
This pull request adds compression support in Always Encrypted in Azure Cosmos DB. Compression is applied before encryption to reduce storage requirements. After decryption, the data is decompressed to restore its original form. This enhancement aims to optimize storage efficiency and improve performance.
Type of change
Please delete options that are not relevant.

[] New feature (non-breaking change which adds functionality)

Closing issues
To automatically close an issue: closes #IssueNumber

Auto closing due to lack of activity, please reopen if needed


ImportError: DLL load failed while importing _core: The specified procedure could not be found.

Hopefully I am in the right place. I am trying to build a python program with pyinstaller. When I run "python main.py" the program runs fine, but when I make an exe with pyinstaller I get the following error:
Traceback (most recent call last):
File "main.py", line 8, in
File "PyInstaller\loader\pyimod03_importers.py", line 546, in exec_module
File "scrcpy_init_.py", line 6, in
File "PyInstaller\loader\pyimod03_importers.py", line 546, in exec_module
File "scrcpy\core.py", line 12, in
File "PyInstaller\loader\pyimod03_importers.py", line 546, in exec_module
File "av_init_.py", line 9, in
ImportError: DLL load failed while importing _core: The specified procedure could not be found.
[9264] Failed to execute script 'main' due to unhandled exception!
*If this helps my ide is showing that it cannot find the declaration to go to on CodecContext:
from av.codec import CodecContext
From what I have read I needed to make sure the the ffmpeg bin was added to the path, but I am still getting the same error. Any help on this would be great! Thanks!

I'm sorry, this feels really out of scope for the project. Given our limited resources I'm going to have to close this.


Windows support

Comment:
Windows is supported on the pyg channel but the pyg channel has some binary incompat with conda-forge. Is that possible to add a windows package here?
Upstream relevant ticket: https://github.com/pyg-team/pytorch_geometric/issues/2790

xref https://github.com/conda-forge/pytorch_scatter-feedstock/issues/45


Detox supports AppleTV Simulator ?

Can some one confirm thats Detox supports Apple TV simulator ?
i tried but getting time out error .

We haven’t tested on tvOS and we have no plans to support it for the time being.
That said, tvOS and iOS are quite close, so Detox probably supports tvOS just fine, and your problem lies elsewhere.

Also, please don’t open duplicate issues to escape the Stack Overflow bot. It’s there for a reason. Final warning.

I tried to run it on tvOS, but unfortunately it didn't work, wrote more about it here https://github.com/wix/Detox/discussions/2853


nzBeforeUpload from nz-upload should have the file parameter of type File instance instead of UploadFile

Reproduction link
https://stackblitz.com/edit/ng-zorro-antd-start-ygithh?file=src/app/app.component.ts
Steps to reproduce
Use a nz-upload with a nzBeforeUpload attribute that returns false. Log the file parameter inside nzBeforeUpload.
What is expected?
I expect the argument type of the nzBeforeUpload function to be of type File instead of UploadFile as the function actually has inside Javascript
What is actually happening?
nzBeforeUpload has the wrong type definition for the file parameter of UploadFile instead of File.

Environment
Info

ng-zorro-antd
8.5.2

Browser
*

The type definition just needs to be changed to reflect what the function actually is called with:
Now is:
nzBeforeUpload: (file: UploadFile, fileList: UploadFile[]) => boolean | Observable<boolean>;

It should be:
nzBeforeUpload: (file: File, fileList: File[]) => boolean | Observable<boolean>;

PS. I am not sure if the fileList parameter should be File[].

the UploadFile already has the original file object as UploadFile.originFileObj

@radiumrasheed no. As seen in the demo, the nzBeforeUpload calls the method with a file of type File and the definition says it is of type UploadFile. There is an issue of definition on the nzBeforeUpload method inside nzUpload

actually yes, I agree to this. its really an issue. I noticed this after my comment

I agree to this.  In "beforeUpload", it is really a "File", not UploadFile.
When I want to preview "base64 thumbnail" in nzBeforeUpload callback, I read the File Blob from UploadFile.originFileObj, but got undefined error! Because after "nzBeforeUpload", the uploadFile.originFileObj is not exist.
" beforeFrontUpload = (file: File) =>  { ...  } "  will solve the problem! But when you turn on "strictTemplates": true.
Everything Goes Wrong!

I have exactly same case like @emondora. For now i use a small workaround:
In my beforeUpload function i accept file as UploadFile:
beforeUpload = (file: UploadFile): Observable<boolean> => {
but later i'm just casting types:
reader.readAsDataURL(file as unknown as File);

This is still an issue in version 9.3.0

I just encountered this as well.
https://stackblitz.com/edit/angular-y45bu7?file=src/app/app.component.ts
None of the NzUploadFile properties work and the type of the object [nzBeforeUpload] is called with is File
beforeUpload = (file: NzUploadFile, _fileList: NzUploadFile[]) => {
    console.log('Instance of: ' + file.constructor.name); // Instance of: File

    console.log(file.filename, file.originFileObj, file.error, file.linkProps, file.percent, file.thumbUrl, file.response, file.uid);
   // undefined undefined undefined undefined undefined undefined undefined e630sazjkzv
}

This is still an issue in version 10.0.0

@IonelLupu The type file is a primitive file type File Object, This is an error on the documentation.

@cipchk yes, but the nzBeforeUpload attribute expects a function which has the first parameter of type NzUploadFile and not File. So, the code needs to be updated as well. This is the definition of nzBeforeUpload:
nzBeforeUpload?: (file: NzUploadFile, fileList: NzUploadFile[]) => boolean | Observable<boolean>;

This is still an issue in v11.1.0.
Isn't this just a type correction? Though I guess this will be a breaking change for people using strictTemplates

This is still an issue in v11.1.0.
Isn't this just a type correction? Though I guess this will be a breaking change for people using strictTemplates

Hi,
I am using the version 10.2.2 for my current project.
Days ago, I had the issue I wanted to get the value as datatype File from a variable NzUploadFile in the event beforeUpload because I need convert the file to base 64. However, when I used the property "originFileObj" from this variable but I always got undefined.
Then, I found a solution which I put here:
beforeUpload = (file: NzUploadFile): boolean => {

    this.fileList = [file];
    const myReader = new FileReader();
    myReader.readAsDataURL(file as any);
    myReader.onloadend = (e) => {
      this.base64 = myReader.result;
    };
    return false;
  };

The trick is pass the NzUploadFile variable in the method "readAsDataURL" change the datatype using the keyword "as". I was surprised when I tested that code and it worked. Although, I have doubts because it works, but now that was the solution which I reach.

@Linzeur While this works, it is just a temporary solution. Using as any anywhere is problematic

Bumping this a bit. I encountered this again.

Still broken in version 13. 😮

still broken in 13.2.2

ahh..i thank it works. just receive a "File" type. and then use .arrayBuffer() to get a promise to process your data.
    beforeUpload = async (file: File): Promise<boolean> => {
        file.arrayBuffer().then(async (data) => {
          // use your stream do anything
        }).catch(
          (error) => {console.log(error);
        })

        console.log(this.fileList);
        return false;
    };

just cast NzUploadFile to File type , it will work
beforeUpload = (file: NzUploadFile): boolean => {
    const formData = new FormData();
    formData.set("image", file as unknown as File);
}

bump. still broken in v14

Actually, NzUploadFile should mention that it extends File. It would solve problems.

@Nosfistis as explained in https://github.com/NG-ZORRO/ng-zorro-antd/issues/4744#issuecomment-688710484 the parameter object (NzUploadFile) doesn't have any of the properties relevant to NzUploadFile set. They're all undefined.
So it's not just a matter of extending.

@snebjorn it seems the only property that NzUploadFile actually attaches in beforeUpload is uid. The rest are probably for the automatic upload.
Having them undefined is not an issue as they are actually marked as optional. The actual implementation though does use NzUploadFile as an extension of File.

Still broken in v16


Optional shortcut

Can we add an optional shortcut cmd+space to change language without popup on Sonoma?

Hello) This is an interesting idea, no promises yet, but I will consider implementing it in future versions.

@Nikeev Also, it would be great if the Caps Lock key is also supported as a switch like Fn.

@Nikeev Also, it would be great if the Caps Lock key is also supported as a switch like Fn.

ye, would like that one


House cleaning of configurations

This PR:

Gets rids of dysfunctional configurations (i.e., 360x210 and 360x320 resolutions).
Make use of WOA version 2018 (WOA18) as defaults, therefore no need to override via MOM_override.

The coupled tests are not happy. Do I need to change things at low res in my BCs set?

The coupled tests are not happy. Do I need to change things at low res in my BCs set?

Maybe because "woa18_decav_t01_04.nc" file is not present? It needs to be linked/copied in gcm_run.j.

The coupled tests are not happy. Do I need to change things at low res in my BCs set?

Maybe because "woa18_decav_t01_04.nc" file is not present? It needs to be linked/copied in gcm_run.j.

Ah. Okay. I'm on leave until next week, so I'll try and get things fixed up then. @zhaobin74 where is this file located on discover so I can include it in TinyBCs?

@mathomp4, @zhaobin74 and all,
Please do following in your gcm_run.j (for now, later, I'll coordinate with @biljanaorescanin to have these files populated in the BCs path .and. patch the App); see below(*)
set             FILE = linkbcs
/bin/rm -f     $FILE
cat << _EOF_ > $FILE
#!/bin/csh -f
...
...
...

cp /discover/nobackup/sakella/woa18/1-deg/WOA18_decav_TPOTS_monthly_fulldepth_01.nc INPUT

That gets a full_depth WOA18 T and S file into scratch/INPUT.
(*) Reason for not patching the App at this moment is so as to get @biljanaorescanin's help (as needed) in order to copy files from ⬆ path and purge whats not needed.
I can successfully run with my WOA18_decav_TPOTS_monthly_fulldepth_01.nc, so I expect you can as well.

@sanAkel I can't see the file (rw only for you), but... 900MB. Ouch.
Maybe once I can see inside it, I can work with you to prune it down for TinyBCs (i.e., if it's a daily file or something, we can pull out just a few days).

That (cut size) can be done. See in about an hour.

@mathomp4 I have undrafted this PR (again)! I don't want to hold off this clean up anymore (until I get a coarser WOA initial conditions. When we spoke last week, you said that the file size is ok.)
@zhaobin74 can you please review this PR.
Thanks!

Yay it's working!

Yay it worked! :)

Yay it worked! :)
@mathomp4, you mean it worked for c12x5 setup, right?

Yay it worked! :)
@mathomp4, you mean it worked for c12x5 setup, right?

Yes. Mainly that the CI didn't crash like before. The ocean could be boiling for all I know, but it ran for 6 hours! 😄

Yay it worked! :)
@mathomp4, you mean it worked for c12x5 setup, right?

Yes. Mainly that the CI didn't crash like before. The ocean could be boiling for all I know, but it ran for 6 hours! 😄

Thanks, @mathomp4. I am testing the other two configs, 1440x1080 and 540x458.
First, 1440x1080 didn't work out of the box.

cp /discover/nobackup/sakella/woa18/1-deg/WOA18_decav_TPOTS_monthly_fulldepth_01.nc INPUT

failed with permission denied error.
I see there is another (smaller) file /discover/nobackup/sakella/woa18/1-deg/WOA18_decav_TPOTS_mon01_fulldepth_01.nc. Is this one supposed to be used? In that case, ```

Yay it worked! :)
@mathomp4, you mean it worked for c12x5 setup, right?

Yes. Mainly that the CI didn't crash like before. The ocean could be boiling for all I know, but it ran for 6 hours! 😄

Thanks, @mathomp4. I can test the other two configs, 1440x1080 and 540x458.

First, 1440x1080 didn't work out of the box.

cp /discover/nobackup/sakella/woa18/1-deg/WOA18_decav_TPOTS_monthly_fulldepth_01.nc INPUT

failed with permission denied error.
I see there is another (smaller) file /discover/nobackup/sakella/woa18/1-deg/WOA18_decav_TPOTS_mon01_fulldepth_01.nc. Is this one supposed to be used? In that case, 1440x1080/MOM_input should be updated to this new file.

540x458  config works out of the box with /discover/nobackup/sakella/MOM6-GFDL/MOM6-testing/Gustavo.Marques/datasets/woa18_04_initial_conditions.nc

/discover/nobackup/sakella/woa18/1-deg/WOA18_decav_TPOTS_monthly_fulldepth_01.nc

@zhaobin74 thanks for testing both configurations:

1440x1080 I fixed the file permission issue. Sorry, somehow I overlooked it! Whenever I scp files from local mac ➡ discover, this happens.

-rw-r--r-- 1 sakella s2640 908M Oct  4 18:24 /discover/nobackup/sakella/woa18/1-deg/WOA18_decav_TPOTS_monthly_fulldepth_01.nc

Reg:

I see there is another (smaller) file /discover/nobackup/sakella/woa18/1-deg/WOA18_decav_TPOTS_mon01_fulldepth_01.nc. Using this file worked.
Is this one supposed to be used?

NO. I want to use for this coarse- resolution tests only.

In that case, 1440x1080/MOM_input should be updated to this new file.

⬆  Not needed since I fixed the file permissions.

540x458

config works out of the box
👍  Thanks!

@zhaobin74 can You please retry 1440x1080?

@mathomp4 can you approve the PR since it seems to have worked for you.

@mathomp4 can you approve the PR since it seems to have worked for you.

Approved. Though without Yury, once @zhaobin74 approves I might have to use superpowers to get it in.

@zhaobin74 can You please retry 1440x1080?

After the permission fix, 1440x1080 config is working:smiley:

@mathomp4 can you approve the PR since it seems to have worked for you.

Approved. Though without Yury, once @zhaobin74 approves I might have to use superpowers to get it in.

Yes @mathomp4 please use them! 😄


Add multiple custom domains to FAQ

Add multiple custom domains question to FAQ

@feddovanede reviewed and ready. Shall I merge immediately?

Yes, I'm ok with that!


Move _WalkCoreSchema from pydantic into pydantic-core

https://github.com/pydantic/pydantic/blob/5049d115edaa4615c45b46ae9362855d0fbc890d/pydantic/_internal/_core_utils.py#L232
I think given the utility we are getting from this and the fact that it is really not specific to pydantic in any way, it makes sense to move to pydantic-core. Not urgent, just creating this as a tracking issue I can reference from a comment in the pydantic source.

Hopefully, might be faster as well.

I already tried this, it wasn't any faster because you have to make Python calls to manipulate dicts.

https://github.com/pydantic/pydantic-core/pull/1099

@adriangb, should we close this as not planned then?

Yes I’d say so
On Fri, Aug 16, 2024 at 8:56 PM Sydney Runkle @.***>
wrote:

@adriangb https://github.com/adriangb, should we close this as not
planned then?
—
Reply to this email directly, view it on GitHub
https://github.com/pydantic/pydantic-core/issues/615#issuecomment-2294530913,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANMPP3NCAKAUOIHTSCFHJTZR2UULAVCNFSM6AAAAABMUPQPJKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUGUZTAOJRGM
.
You are receiving this because you were mentioned.Message ID:
@.***>


Stop setting RestoreConfigFile environment variable

As part of nuget.config file mutations work (https://github.com/dotnet/installer/pull/18478) we've added a new env.var RestoreConfigFile to support various tool projects in aspnetcore, fsharp and source-build-externals. Those projects do not automatically get RestoreConfigFile MSBuild property.
Consider removing this env.var and fixing build infra in those repos, to properly pass the MSBuild property to all miscellaneous projects.
Without this variable, NuGet would restore packages from feeds in repo's root, instead of one that we supply with RestoreConfigFile property. Offline source-build is the perfect repro scenario.

We had a discussion with the NuGet team recently about https://github.com/dotnet/source-build/issues/3781. We discussed that NuGet (both the nuget sdk resolver and NuGet common code) would honor two new environment variables: NUGET_CONFIG and GLOBAL_JSON. We will implement this in the coming months.
Given that, we actually want to set an env var and won't need the properties then anymore. We need an env var over a property solution as sdk resolver don't have access to (global) msbuild properties.


[Request] Rename Inputs in the Input map?

All I want is to not have to delete and remake inputs if I want them to be called something different...please?

Uh, did this ever happen? XD

It was a very motivated "okay!" from @reduz, but indeed it's not implemented yet as of  bd736e5 :P


add separate softmax decoder layer type

that is pure readout and doesn't feed back -- see if it can do better than current output layer.

doing this now using a completely separate standalone softmax object, which can be used with any kind of model.  will not contaminate the network diagram with decoders..
and in the course of looking this up, I discovered that indeed my previous cemer impl of softmax was wrong, which I had suspected but hadn't quite gotten around to finding the right answer -- you do have to include the full jacobian of all cross-wise terms in the NxN matrix of output units!  I had only included the one diagonal term.  This is likely why my AlexNet didn't work!  Somehow my CU3D bp model did work though..


add international school of milan

International school of milan
official website: https://www.internationalschoolofmilan.it/en

@TeamSquidTempura I have to close this request without merging, because you requested to add a non-existent domain to this repository: Host myise.ism not found: 3(NXDOMAIN) Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with the correct information. Thank you for your understanding!

sorry the domain is @myise.cloud


CA URLs in connection profiles contain http even if TLS is enabled

It should be https

Hey @dzikowski  I dug into the issue and I believe I've found a way to address it. I would like to work on this.

Great, thanks! Feel free to start.

Great, thanks! Feel free to start.

Hi I have pushed the changes, can you check that out.


IInstallReferrerEvents cannot access in app

I'm trying to use IInstallReferrerEvents in InstallListener
but that callback message cannot be accessed outside of InstallListener
because it isn't public interface.
So, that interface cannot be used by any class!!

@krcho  can you please  provide  a little  bit more info on what you are trying to do?
IInstallReferrerEvents is for Branch Internal purpose to get notified when there Install referrer available.
IN case you want to add your own callback , can you please extend InstallListener class and add your own callback. Then yu can override the onReceive and call your callback method


Fixes to the CI document

Various fixes to the CI document.

@mairaw pls take a look. @enricosada will update the PR to add the new AppVeyor script that uses manual install of the newest bits.

also afaik (up to two days ago), travis doesnt yet support rc4, ref https://github.com/travis-ci/travis-ci/issues/7301
i'll check with travis.yml embedded in this repo

@blackdwarf added https://github.com/dotnet/docs/pull/1599 with cleanup appveyor/travis for rc4

@enricosada I've added support for RC* in Travis with travis-ci/travis-build#968 that was merged yesterday or on Wed.

@mairaw are you ok for this going in?

I've made some improvements @blackdwarf but I still don't think this is ready. Here are the my questions now:

we have images that are not being used. Delete them?
The section on Using a manual script seems to skip a few steps but I don't know how to fix that since I've never used VSTS. For example, how do I get to the Create new build definition page/dialog?
The topic still talks about VS 2015

@mairaw comments:

Sure, delete all of them.
You click on the "Build & Release" in the top row.
Hmmm, @enricosada I thought you added the YAML file for AppVeyor that uses the script and not the VS2015 image?

Hmmm, @enricosada I thought you added the YAML file for AppVeyor that uses the script and not the VS2015 image?

@blackdwarf i have do it, the appveyor.yml is
 install:
    - ps: $env:DOTNET_INSTALL_DIR = "$pwd\.dotnetsdk"
    - ps: mkdir $env:DOTNET_INSTALL_DIR -Force | Out-Null
    - ps: Invoke-WebRequest -Uri "https://raw.githubusercontent.com/dotnet/cli/rel/1.0.0/scripts/obtain/dotnet-install.ps1" -OutFile "$($env:DOTNET_INSTALL_DIR)/dotnet-install.ps1"
    - ps: '& "$($env:DOTNET_INSTALL_DIR)/dotnet-install.ps1" -Version $env:CLI_VERSION -InstallDir $env:DOTNET_INSTALL_DIR'
    - ps: $env:Path = "$env:DOTNET_INSTALL_DIR;$env:Path"

btw all that should be updated for 1.0 rtm i think.
@blackdwarf all that should be updated with .net core tools 1.0.1 , i'll send a PR asap, checking locally because the channel is changed (btw the descript of channel show dev/future/production, but production doesnt work and default is undocumented rel-1.0.0), i'll open an issue in dotnet/cli about that

@blackdwarf added some comment about dotnet-install script and docs in https://github.com/dotnet/cli/issues/5952

Replaced by https://github.com/dotnet/docs/pull/2161


Display labels in info panel

If the user clicks the card an info panel opens. Display all labels under the media title there.
Also, display labels right under the release date on the card, not next to status button.

Resolved. As part of the story all packages were updated


Task list check on every keypress

Windows 10
Kite isn't running

I'm seeing this on every keypress (with a delay), is this intentional/needed:
Error: Unable to find kited.exe process in the tasks list
index.js:61
	at WindowsSupport.isKiteRunning.utils.spawnPromise.then.stdout (C:\Users\jansorg\source\vscode-plugin\node_modules\kite-connector\lib\support\windows.js:211:15)
	at <anonymous>
rejected promise not handled within 1 second

intentional behavior.
In vscode, just like in atom, we have the Docs available at cursor hint in the status that requires to hit the hover endpoint on key strokes, then as kite is not running we’re enternig the health check, and it starts by checking if kite is running by using the task list


add a new school

file.zip

Please add the school :)

the school is ESADD. The official domain is esadd.fr

@kurakigo First stage of verification passed, official domain is esadd.fr as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.


delete the whole codeblock section

Thank you for your keyshots .
How could I do to delete or select whole codeblock with hot key?
Thank you.

Hello @trevim99, thank you for your issue post.
This is now not possible in Keyshots (at least with one command). But on computer it can be achieved by these steps:

Having cursor at the top or bottom of code block
Then move cursor in direction of codeblock with arrow keys ↑, ↓ while holding Shift key.
After reaching next bound of code block, to make sure, that everything is selected, use Keyshots: Expand line selection command (in default with Alt + E but it depends on what preset you have chosen)
Then press Backspace ← key or Delete key, to finally remove it

Command for removing code block is something, that you can make done in few steps, and I hope so, you don't type 100 code blocks on daily basis to actually have command for removing them.
I am sorry but I am closing this issue as not planned. Have a great day and thank you for helping Keyshots to become a better plugin. Feel free to leave other ideas in new issue post.


Support global-schema and api-schema in extractor

[x] #766

[x] #769

Closing the issue since both sub tasks are already merged


Add base config to allow users to specify files other than just .js files

Is your feature request related to a problem? Please describe.
It would be nice if the user could specify files other than .js files for the initial scrub of the project folder.
Describe the solution you'd like
Add an additional configuration for baseFileExtension (.txt or other). Then add to the parameters of the Watcher function with default value of 'js'

I would like to work on this if nobody is tackling it yet.


Sync slow since this week

I believe this is not an issue of govendor per se but I still want to double check I am not missing something obvious:
Since roughly the beginning of this week, our govendor sync step is very slow. Looking at govendor sync -v shows time is equally distributed between the dependencies. Did Github change something on their catching or CDN or git delivery strategy?
Most, almost all, dependencies come from github.com, a few from gopkg.in which I believe to understand is mostly a proxy for a specific revision also hosted on GitHub.

Maybe your cache got broken? Check files at $GOPATH/.cache

@kaey We run govendor sync -v in a docker container, so no caching by govendor but rather relying on Docker's image caches. And whenever we delete an image and need to start from scratch, the download times seem much slower than before the beginning of this week.

I just created a pull request that may help https://github.com/kardianos/govendor/pull/269


[Bug]: DaskExpr reduction to scalar can't be select-ed

Describe the bug
When selecting an expression which ends up in a reduction to a scalar, AttributeError is raised:

AttributeError: 'Scalar' object has no attribute 'name'

Steps or code to reproduce the bug
import dask.dataframe as dd
import pandas as pd

df = nw.from_native(
    dd.from_pandas(
        pd.DataFrame(data={"a": [1., 3, 2]})
    )
)

for attr in ("min", "max", "mean", "sum"):
    try:
        df.select(getattr(nw.col("a"), attr)())
    except:
        print(f"{attr=} run into exception")

Expected results
No error is thrown
Actual results
AttributeError get raised
Please run narwhals.show_version() and enter the output below.
main branch +

System:
    python: 3.10.12 (main, Mar 22 2024, 16:50:05) [GCC 11.4.0]
executable: /home/fbruzzesi/open-source/narwhals/.venv/bin/python
   machine: Linux-<IP_ADDRESS>-microsoft-standard-WSL2-x86_64-with-glibc2.35

Python dependencies:
     narwhals: 1.1.9
       pandas: 2.2.2
       polars: 1.2.1
         cudf:
        modin: 0.31.0
      pyarrow: 17.0.0
        numpy: 2.0.1

Relevant log output

Entire log
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
File ~/open-source/narwhals/.venv/lib/python3.10/site-packages/dask_expr/_core.py:467, in Expr.__getattr__(self, key)
    466 try:
--> 467     return object.__getattribute__(self, key)
    468 except AttributeError as err:
File ~/open-source/narwhals/.venv/lib/python3.10/site-packages/dask_expr/_expr.py:448, in Expr.name(self)
446 @property
447 def name(self):
--> 448     return self._meta.name
AttributeError: 'numpy.float64' object has no attribute 'name'
During handling of the above exception, another exception occurred:
AttributeError                            Traceback (most recent call last)
File ~/open-source/narwhals/.venv/lib/python3.10/site-packages/dask_expr/_collection.py:619, in FrameBase.getattr(self, key)
616 try:
617     # Fall back to expr API
618     # (Making sure to convert to/from Expr)
--> 619     val = getattr(self.expr, key)
620     if callable(val):
File ~/open-source/narwhals/.venv/lib/python3.10/site-packages/dask_expr/_core.py:488, in Expr.getattr(self, key)
487 link = "https://github.com/dask-contrib/dask-expr/blob/main/README.md#api-coverage"
--> 488 raise AttributeError(
489     f"{err}\n\n"
490     "This often means that you are attempting to use an unsupported "
491     f"API function. Current API coverage is documented here: {link}."
492 )
AttributeError: 'numpy.float64' object has no attribute 'name'
This often means that you are attempting to use an unsupported API function. Current API coverage is documented here: https://github.com/dask-contrib/dask-expr/blob/main/README.md#api-coverage.
During handling of the above exception, another exception occurred:
AttributeError                            Traceback (most recent call last)
Cell In[8], line 1
----> 1 df.select(getattr(nw.col("a"), attr)())
File ~/open-source/narwhals/narwhals/dataframe.py:2537, in LazyFrame.select(self, *exprs, **named_exprs)
2371 def select(
2372     self,
2373     *exprs: IntoExpr | Iterable[IntoExpr],
2374     **named_exprs: IntoExpr,
2375 ) -> Self:
2376     r"""
2377     Select columns from this LazyFrame.
2378
(...)
2535         └───────────┘
2536     """
-> 2537     return super().select(*exprs, **named_exprs)
File ~/open-source/narwhals/narwhals/dataframe.py:128, in BaseFrame.select(self, *exprs, **named_exprs)
121 def select(
122     self,
123     *exprs: IntoExpr | Iterable[IntoExpr],
124     **named_exprs: IntoExpr,
125 ) -> Self:
126     exprs, named_exprs = self._flatten_and_extract(*exprs, **named_exprs)
127     return self._from_compliant_dataframe(
--> 128         self._compliant_frame.select(*exprs, **named_exprs),
129     )
File ~/open-source/narwhals/narwhals/_dask/dataframe.py:87, in DaskLazyFrame.select(self, *exprs, **named_exprs)
83 if exprs and all(isinstance(x, str) for x in exprs) and not named_exprs:
84     # This is a simple slice => fastpath!
85     return self._from_native_dataframe(self._native_dataframe.loc[:, exprs])
---> 87 new_series = parse_exprs_and_named_exprs(self, *exprs, **named_exprs)
88 if not new_series:
89     # return empty dataframe, like Polars does
90     pd = get_pandas()
File ~/open-source/narwhals/narwhals/_dask/utils.py:53, in parse_exprs_and_named_exprs(df, *exprs, **named_exprs)
51         raise TypeError(msg)
52     for _result in _results:
---> 53         results[_result.name] = _result
54 for name, value in named_exprs.items():
55     _results = value._call(df)
File ~/open-source/narwhals/.venv/lib/python3.10/site-packages/dask_expr/_collection.py:625, in FrameBase.getattr(self, key)
622     return val
623 except AttributeError:
624     # Raise original error
--> 625     raise err
File ~/open-source/narwhals/.venv/lib/python3.10/site-packages/dask_expr/_collection.py:614, in FrameBase.getattr(self, key)
611 def getattr(self, key):
612     try:
613         # Prioritize FrameBase attributes
--> 614         return object.getattribute(self, key)
615     except AttributeError as err:
616         try:
617             # Fall back to expr API
618             # (Making sure to convert to/from Expr)
AttributeError: 'Scalar' object has no attribute 'name'

yup - not really sure what to do about this one unfortunately...maybe we need a special case for when everything passed to DaskLazyFrame.select is actually a Dask Scalar, so then we can safely call to_series on each one of them and concat them

Mmmh I somehow manage to make reduction work properly, yet now breaks when broadcasting (e.g. nw.col("a").min() + nw.col("b") )🥲
I will try to spend some time on this


Insert or Replace not working

I'm trying the following
if let insertID = table.insert(or: .replace, service <- serviceI, client <- clientI, client_type <- client_typeI, allowed <- allowedI).rowid

But I'm getting the error 'could not find memeber 'replace' '
Where is my error?
Is it smarted to use the following?
let stmt = db.prepare("INSERT OR REPLACE INTO access (service, client, client_type, allowed, prompt_count) VALUES (?,?,?,?,?)")
stmt.run([serviceI, clientI, client_typeI, allowedI, prompt_countI])

If that's an exact copy and paste, it looks like simply changing .replace to .Replace would fix the issue. Swift is telling you that the struct doesn't have a member named replace.

it is not solving the problem .Replace produces the same error

@Silve2611 Are you on the latest version of SQLite.swift?

@Silve2611 Going to close this due to inactivity. Please chime in if you're still having trouble and have a reproducible bug.


1

拉取/合并请求描述：(PR description)
[
这段方括号里的内容是您必须填写并替换掉的，否则PR不可能被合并。方括号外面的内容不需要修改，但请仔细阅读。
The content in this square bracket must be filled in and replaced, otherwise, PR can not be merged. The contents outside square brackets need not be changed, but please read them carefully.
请在这里填写您的PR描述，可以包括以下之一的内容：为什么提交这份PR；解决的问题是什么，你的解决方案是什么；
Please fill in your PR description here, which can include one of the following items: why to submit this PR; what is the problem solved and what is your solution;
并确认并列出已经在什么情况或板卡上进行了测试。
And confirm in which case or board has been tested.
]
以下的内容不应该在提交PR时的message修改，修改下述message，PR会被直接关闭。请在提交PR后，浏览器查看PR并对以下检查项逐项check，没问题后逐条在页面上打钩。
The following content must not be changed in the submitted PR message. Otherwise, the PR will be closed immediately. After submitted PR, please use a web browser to visit PR, and check items one by one, and ticked them if no problem.
当前拉取/合并请求的状态 Intent for your PR
必须选择一项 Choose one (Mandatory):

[ ] 本拉取/合并请求是一个草稿版本 This PR is for a code-review and is intended to get feedback
[ ] 本拉取/合并请求是一个成熟版本 This PR is mature, and ready to be integrated into the repo

代码质量 Code Quality：
我在这个拉取/合并请求中已经考虑了 As part of this pull request, I've considered the following:

[ ] 已经仔细查看过代码改动的对比 Already check the difference between PR and old code
[ ] 代码风格正确，包括缩进空格，命名及其他风格 Style guide is adhered to, including spacing, naming and other styles
[ ] 没有垃圾代码，代码尽量精简，不包含#if 0代码，不包含已经被注释了的代码 All redundant code is removed and cleaned up
[ ] 所有变更均有原因及合理的，并且不会影响到其他软件组件代码或BSP All modifications are justified and not affect other components or BSP
[ ] 对难懂代码均提供对应的注释 I've commented appropriately where code is tricky
[ ] 本拉取/合并请求代码是高质量的 Code in this PR is of high quality

1


add import to command tree

Codecov Report

Merging #49 (4652663) into main (d950839) will increase coverage by 0.06%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #49      +/-   ##
==========================================
+ Coverage   76.70%   76.77%   +0.06%
==========================================
  Files           8        8
  Lines         674      676       +2
==========================================
+ Hits          517      519       +2
  Misses        130      130
  Partials       27       27

Flag
Coverage Δ

Linux
76.77% <100.00%> (+0.06%)
:arrow_up:

macOS
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

cmd/import.go
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

closes #48


The data object "<LS_OBJECTS>" does not have a component called "UDATE".

I got an activation error
line 74036
error  The data object "<LS_OBJECTS>" does not have a component called "UDATE".
SAP_ABA 740 012
thanks

duplicate of https://github.com/larshp/abapGit/issues/3255 ?

@agiguere try again, latest version, PR is merged

thanks

asumming it works? closing

wait, I am testing it, I download the program from here is it ok
https://docs.abapgit.org/guide-install.html

I confirm the program compile without error, yes you can close this incident, thanks


Incorrect date ordering in Liquidations Chart

I observed a bug on the stats page - Liquidations on both monthly & yearly time frames.
The charts begin on July 4th 2021 and track backwards until May 12, 2021, before skipping over to Nov 5, 2020.

I was able to fix the issue with the date ordering; not sure if Nov-May is fixable


Provide a keyboard shortcut to get to the search box?

Not sure what the common shortcut would be (or if others do this). I know tab doesn't seem to move there because it's hidden by default anyway.

I suggest / or ? (Vim bindings) :)

Yeah maybe?/?
I know ? is used to show the keyboard shortcuts UI for many sites

I think we should also support a more common key: f or s for example.
In many cases / or ? are already used.

I can also add additional keys.
Will this be communicated in some way or another? It's potentially possible to open the search bar on any key and automatically start adding the typed key into the search input.

FWIW, Github uses s for search, I personally think that's a fine choice.

@raspo Thanks for reminding me of this contribution. :smile:
Yes, I updated my PR to include the s as a search button (extending the list of / and ?).


[Event Request] codeunit 312  "Cust-Check Cr. Limit" - OnSetCustCheckCreditLimitSalesLineCheck

Hello, would it be possible to add OnSetCustCheckCreditLimitSalesLineCheck,  event to codeunit 312  "Cust-Check Cr. Limit", like this:
    procedure SalesLineCheck(SalesLine: Record "Sales Line") CreditLimitExceeded: Boolean
...

         if GuiAllowed then
             OnNewCheckRemoveCustomerNotifications(SalesHeader.RecordId, false);

>         OnSetCustCheckCreditLimitSalesLineCheck(CustCheckCreditLimit);//New Event
         if not CustCheckCreditLimit.SalesLineShowWarningAndGetCause(SalesLine, AdditionalContextId) then
             SalesHeader.CustomerCreditLimitNotExceeded()
         else begin
             CreditLimitExceeded := true;

     [IntegrationEvent(false, false)]
     local procedure OnSetCustCheckCreditLimitSalesLineCheck(var CustCheckCreditLimit: Page "Check Credit Limit")
     begin
     end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 10644.


wac plug with registry support

This is depends/includes the changes in #103  and adds wac plug registry support (feature flag still but a default one). So if approved, would close #103 . Let me know if you like this approach or if it should be revised.
Existing behavior is unchanged:
wac plug my-component.wasm --plug helpful.wasm -o plugged.wasm
But you can also now mix in package names or local file paths that are fetched from a registry. In any combination. Kind of fun.
It determines whether to look in the registry or local path by trying to parse as valid namespace:package-name. If it is a valid package name, then it looks in the registry or otherwise tries local file paths. So path/some-file.wasm would be unambiguously a local file path.
wac plug macovedj:hashimap-service --plug macovedj:my-component -o plugged.wasm
(those are packages from @macovedj WasmIO demo and that command will work if Warg is configured)
or
wac plug hashimap-service.wasm --plug macovedj:my-component -o plugged.wasm
I debated adding another output option for publishing the output component. Also, it would be cool to parse and support the identifiers<EMAIL_ADDRESS>that have versions specified. I could also imagine an interactive dialogue approach to using wac CLI.

@macovedj thanks for the review. I definitely want the other maintainers to weigh in on this.


"Failed to allocate memory for image" error when reading Hamamatsu ndpi whole slide image

I'm trying to load a Hamamatsu formatted whole slide image (ndpi). It seems to be picking the TIFFImageIO correctly, but fails to load the image.
Is this actually a memory error, or is the ndpi format causing problems? The image is only 2.4 GB in size (possibly compressed) and I have 30 gb of available RAM and another 32 gb of swap memory.
This is in 64 bit Python3, SimpleElastix version 1.1.0.dev355+g665d6. Compiled for Python3, installed with pip3.
f = sitk.ReadImage(fixed)
TIFFReadDirectory: Warning, Unknown field with tag 65420 (0xff8c) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65421 (0xff8d) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65422 (0xff8e) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65423 (0xff8f) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65424 (0xff90) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65425 (0xff91) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65426 (0xff92) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65427 (0xff93) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65428 (0xff94) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65433 (0xff99) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65439 (0xff9f) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65440 (0xffa0) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65441 (0xffa1) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65442 (0xffa2) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65443 (0xffa3) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65444 (0xffa4) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65445 (0xffa5) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65446 (0xffa6) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65449 (0xffa9) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65455 (0xffaf) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65456 (0xffb0) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65457 (0xffb1) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65458 (0xffb2) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65459 (0xffb3) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65420 (0xff8c) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65421 (0xff8d) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65422 (0xff8e) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65423 (0xff8f) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65424 (0xff90) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65425 (0xff91) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65426 (0xff92) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65427 (0xff93) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65428 (0xff94) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65433 (0xff99) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65439 (0xff9f) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65440 (0xffa0) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65441 (0xffa1) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65442 (0xffa2) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65443 (0xffa3) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65444 (0xffa4) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65445 (0xffa5) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65446 (0xffa6) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65449 (0xffa9) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65455 (0xffaf) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65456 (0xffb0) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65457 (0xffb1) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65458 (0xffb2) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65459 (0xffb3) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65420 (0xff8c) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65421 (0xff8d) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65422 (0xff8e) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65423 (0xff8f) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65424 (0xff90) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65425 (0xff91) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65426 (0xff92) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65427 (0xff93) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65428 (0xff94) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65433 (0xff99) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65439 (0xff9f) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65440 (0xffa0) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65441 (0xffa1) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65442 (0xffa2) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65443 (0xffa3) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65444 (0xffa4) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65445 (0xffa5) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65446 (0xffa6) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65449 (0xffa9) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65455 (0xffaf) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65456 (0xffb0) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65457 (0xffb1) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65458 (0xffb2) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65459 (0xffb3) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65420 (0xff8c) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65421 (0xff8d) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65422 (0xff8e) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65423 (0xff8f) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65424 (0xff90) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65425 (0xff91) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65426 (0xff92) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65427 (0xff93) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65428 (0xff94) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65433 (0xff99) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65439 (0xff9f) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65440 (0xffa0) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65441 (0xffa1) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65442 (0xffa2) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65443 (0xffa3) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65444 (0xffa4) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65445 (0xffa5) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65446 (0xffa6) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65449 (0xffa9) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65455 (0xffaf) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65456 (0xffb0) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65457 (0xffb1) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65458 (0xffb2) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65459 (0xffb3) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65420 (0xff8c) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65421 (0xff8d) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65422 (0xff8e) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65423 (0xff8f) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65424 (0xff90) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65425 (0xff91) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65426 (0xff92) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65427 (0xff93) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65428 (0xff94) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65433 (0xff99) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65439 (0xff9f) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65440 (0xffa0) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65441 (0xffa1) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65442 (0xffa2) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65443 (0xffa3) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65444 (0xffa4) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65445 (0xffa5) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65446 (0xffa6) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65449 (0xffa9) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65455 (0xffaf) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65456 (0xffb0) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65457 (0xffb1) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65458 (0xffb2) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65459 (0xffb3) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65420 (0xff8c) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65421 (0xff8d) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65422 (0xff8e) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65423 (0xff8f) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65424 (0xff90) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65425 (0xff91) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65426 (0xff92) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65427 (0xff93) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65428 (0xff94) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65433 (0xff99) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65439 (0xff9f) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65440 (0xffa0) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65441 (0xffa1) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65442 (0xffa2) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65443 (0xffa3) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65444 (0xffa4) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65445 (0xffa5) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65446 (0xffa6) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65449 (0xffa9) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65455 (0xffaf) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65456 (0xffb0) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65457 (0xffb1) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65458 (0xffb2) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65459 (0xffb3) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65420 (0xff8c) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65421 (0xff8d) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65422 (0xff8e) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65423 (0xff8f) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65424 (0xff90) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65425 (0xff91) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65426 (0xff92) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65427 (0xff93) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65428 (0xff94) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65433 (0xff99) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65439 (0xff9f) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65440 (0xffa0) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65441 (0xffa1) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65442 (0xffa2) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65443 (0xffa3) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65444 (0xffa4) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65445 (0xffa5) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65446 (0xffa6) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65449 (0xffa9) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65455 (0xffaf) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65456 (0xffb0) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65457 (0xffb1) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65458 (0xffb2) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65459 (0xffb3) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65420 (0xff8c) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65421 (0xff8d) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65422 (0xff8e) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65423 (0xff8f) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65427 (0xff93) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65439 (0xff9f) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65440 (0xffa0) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65441 (0xffa1) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65442 (0xffa2) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65444 (0xffa4) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65445 (0xffa5) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65446 (0xffa6) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65449 (0xffa9) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65450 (0xffaa) encountered.
TIFFReadDirectoryCheckOrder: Warning, Invalid TIFF directory; tags are not sorted in ascending order.
TIFFReadDirectory: Warning, Unknown field with tag 65420 (0xff8c) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65421 (0xff8d) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65422 (0xff8e) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65423 (0xff8f) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65427 (0xff93) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65439 (0xff9f) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65440 (0xffa0) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65442 (0xffa2) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65445 (0xffa5) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65446 (0xffa6) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65449 (0xffa9) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65420 (0xff8c) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65421 (0xff8d) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65422 (0xff8e) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65423 (0xff8f) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65424 (0xff90) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65425 (0xff91) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65426 (0xff92) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65427 (0xff93) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65428 (0xff94) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65433 (0xff99) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65439 (0xff9f) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65440 (0xffa0) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65441 (0xffa1) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65442 (0xffa2) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65443 (0xffa3) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65444 (0xffa4) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65445 (0xffa5) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65446 (0xffa6) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65449 (0xffa9) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65455 (0xffaf) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65456 (0xffb0) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65457 (0xffb1) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65458 (0xffb2) encountered.
TIFFReadDirectory: Warning, Unknown field with tag 65459 (0xffb3) encountered.
Traceback (most recent call last):
  File "/usr/lib/python3.5/code.py", line 91, in runcode
    exec(code, self.locals)
  File "<input>", line 1, in <module>
  File "/home/markemus/.local/lib/python3.5/site-packages/SimpleITK/SimpleITK.py", line 8622, in ReadImage
    return _SimpleITK.ReadImage(*args)
RuntimeError: Exception thrown in SimpleITK ReadImage: /home/markemus/dev/SimpleElastix/build/ITK-prefix/include/ITK-4.13/itkImportImageContainer.hxx:199:
Failed to allocate memory for image.

The openslide specification mentions this:

NDPI uses a TIFF-like structure, but libtiff cannot read the headers of an NDPI file. This is because NDPI specifies the RowsPerStrip as the height of the file, and after doing out the multiplication, this typically overflows libtiff and it refuses to open the file. Also, the TIFF tags are not stored in sorted order.

This seems to match the errors- both the TIFFReadDirectoryCheckOrder: Warning, Invalid TIFF directory; tags are not sorted in ascending order.  error and the eventual overflow.

I take it this is an issue with the the ndpi format as you described. Feel free to reopen if this is not the case.


Broken Support for Python 3.10 due to backports.zoneinfo

On Fedora 35, there is Python 3.10.
There is an issue with backports.zoneinfo. It is not required anymore, because "zoneinfo is now in the standard library, so there's no reason to install backports.zoneinfo on Python >= 3.9" (see upstream issue: https://github.com/pganssle/zoneinfo/issues/111)
The bug is during pip install:
[00:05:40]   building 'backports.zoneinfo._czoneinfo' extension
[00:05:40]   creating build/temp.linux-x86_64-3.10
[00:05:40]   creating build/temp.linux-x86_64-3.10/lib
[00:05:40]   gcc -Wno-unused-result -Wsign-compare -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -D_GNU_SOURCE -fPIC -fwrapv -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -D_GNU_SOURCE -fPIC -fwrapv -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/home/django/basxconnect_demo/.venv/include -I/usr/include/python3.10 -c lib/zoneinfo_module.c -o build/temp.linux-x86_64-3.10/lib/zoneinfo_module.o -std=c99
[00:05:40]   lib/zoneinfo_module.c: In function 'zoneinfo_fromutc':
[00:05:40]   lib/zoneinfo_module.c:600:19: error: '_PyLong_One' undeclared (first use in this function); did you mean '_PyLong_New'?
[00:05:40]     600 |             one = _PyLong_One;
[00:05:40]         |                   ^~~~~~~~~~~
[00:05:40]         |                   _PyLong_New
[00:05:40]   lib/zoneinfo_module.c:600:19: note: each undeclared identifier is reported only once for each function it appears in
[00:05:40]   error: command '/usr/bin/gcc' failed with exit code 1
[00:05:40]   ----------------------------------------
[00:05:40]   ERROR: Failed building wheel for backports.zoneinfo

Not sure if we should just say: we don't support python 3.10 yet, or if we can make the requirement conditional in https://github.com/basxsoftwareassociation/bread/blob/main/setup.py#L51


Provide a built-in sampler to filter traces on request path

Is your feature request related to a problem? Please describe.
We want to use the opentelemetry-go-instrumentation to auto-instrument our Go microservices. To reduce storage costs and provide a better sampling strategy, we want something that allows us to exclude some traces when their request path (e.g. /health) matches a regular expression.
This could be very useful in environments like Kubernetes or similar where probes are regularly sent to the app.
Describe the solution you'd like
My first idea was to write a custom Go-specific sampler, RequestPathSampler, that takes a simple list of regular expressions as a parameter. For instance, when I configure my auto instrumentation, I would like to have :
export OTEL_TRACES_SAMPLER="request_path_sampler"
export OTEL_TRACES_SAMPLER_ARG="/(health|metrics)"

I would prefer to keep if possible OTEL_TRACES_SAMPLER and OTEL_TRACES_SAMPLER_ARG to ensure consistency with OpenTelemetry built-in samplers configuration.

When configured with the environment variables above, all traces matching the given pattern will be automatically dropped at the instrumentation level.
I dug a little into the code and saw that in instrumentation.go, we force the usage of the trace.AlwaysSample sampler. Maybe we can update a little this part of the code, in addition to adding the RequestPathSampler code to have something more modular for the sampler implementation, through a factory for instance.
I can make a PR for this proposal if needed.
Describe alternatives you've considered
Currently, I haven't found any viable workaround to drop some traces based on the path. I forked the repository into the company's GitLab to add this feature, but this is not ideal at all because I need to maintain my version of the project in addition to the feature. It would be better to have it included in the upstream repository.
Additional context
Related issues: https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/1060

I would rather see it as a configuration to HTTP/gRPC instrumentations.

Hi @pellared,
Seems better. In which repository is the code for HTTP/gRPC instrumentation? I'll move the issue to the right repository.

@thomasgouveia It is here. There is no need to change anything.

Ok perfect. I have a branch on my local fork with my changes to support the filter on the request path, I can submit a PR for this and we'll see how it should be organized in the PR review if you (or another reviewer) is ok.

Doing a PR always helps (even if it is not going to be merged it facilities the discussions) 👍
My preference for the env var name would be something like OTEL_GO_AUTO_HTTP_INSTRUMENTATION_FILTER_PATH

I'll do it ASAP.

My preference for the env var name would be something like OTEL_GO_AUTO_HTTP_INSTRUMENTATION_FILTER_PATH

Do you prefer to use only this variable? What I want to say is by default, we can keep the actual sampler and if OTEL_GO_AUTO_HTTP_INSTRUMENTATION_FILTER_PATH is not empty, we can use the custom sampler instead of the default, and we configure it with the value of the environment variable?

I think it's a great idea.

Hello,
We need this too on our side and this is a great idea to implement it in the base code.

I think it's a great idea. If we are going to support it via env variable, I think we should also add support through the instrumentation config option (similar to how it is currently with other configs). i.e something like WithPathFilter("/health")

Sure, I'll add this before opening the PR

I think it's a great idea. If we are going to support it via env variable, I think we should also add support through the instrumentation config option (similar to how it is currently with other configs). i.e something like WithPathFilter("/health")

Sure, I'll add this before opening the PR

Another point to consider is https://www.w3.org/TR/trace-context/#trace-flags

As stated by @MrAlias in https://github.com/open-telemetry/opentelemetry-go-instrumentation/pull/468, we will not add a custom sampler code directly in this repository, so that the base auto instrumentation remains generic.
Instead, I'll add a new option method WithSampler, that will allow the creation of custom auto instrumentation binaries by providing custom implementations of sampler (like already did with WithTraceExporter).
I'll update the issue title in consequence.


Feature Request: Separate files stored from files uploaded

In order to see which files have been uploaded into Qiita, users must go to the upload files page and infer that the text below the grey drag box shows which files have been uploaded into the study. At minimum these files should have a heading, and ideally they would be displayed on a separate page. The separate page should also show links to sample information and sample prep files that have been uploaded and converted so users can track what they have accomplished.

I'm not sure I follow this suggestion, could you give more background?
I'm getting confused cause once you add a prep info file, it will be shown below the main buttons (A), which you can click and then see which files you have linked to that prep and the resulting processing files/qiita-artifacts (B).

Sorry for the lack of details on the feature request. The core of the issue is that novice Qiita users are easily confused by Qiita's handling of files and make mistakes when first learning how to use the system.
Current observed issue:

User creates study
User clicks on Upload Files button
User drags and drops sample information, prep information, and fastq files
User clicks on Sample Information, selects their file from the dropdown and clicks Create button
User clicks Add New Preparation button, selects file assigns data type and clicks Create New Preparation button
User receives red banner telling them they have duplicated columns in their prep information and sample information sheets
User wonders what files they uploaded that have the problematic columns and observes there is no page indicating which files have been uploaded
User returns to Upload Files page hoping to learn which files did not work, but they are not listed, only the fastq files
User uploads sample information and prep information again
User repeats steps 4-7 and gets frustrated

Suggested behaviors:

Files do not "disappear" when they are processed; if the file must/should be removed, evidence of the original file name should be displayed somewhere to help users troubleshoot

If a separate page that shows which files the Qiita study knows about is not made, then at a minimum on the Upload Files page, there should be a heading stating what the files are below the grey dropbox (screenshot attached)

If there is opposition to the separate "Uploaded Files" page, then maybe just a page with a log of what was done before the prep information addition step would be helpful. This page could also log when sample information or prep information is updated

Thanks for the clarification and suggestions.
A few things to consider: (1) we decided to remove the "successfully" (warnings aren't consider failure) processed info file to avoid left over files that have been already added, (2) note that based on 1, we don't remove the files that failed, (3) we don't allow download of files that are not linked because we want to avoid users using the system as a simple Dropbox server, and (4) if the file was processed successfully it can be downloaded from the sample or prep info file, thus, recovering their original file.
Now, for your suggestions:
1-3. We could add the original name of the file uploaded to the DB and display it in the sample/prep, the problem is when you update the info. I guess we can only show the latest used or have the history of all of them. The latter option might become a GUI problem.
2. The heading is an easier solution, we can add without much problem.
What do you think?

@adswafford, what do you think?

It looks like 1-3 is somewhat addressed by the fix #2214 (#2327).
The concern about the dropbox-ing is valid, but can we make it so only admin accounts can download the uploaded files? The situation arises when I'm helping a user in a workshop, via email, or managing the help account where I wind up having to have them email or dropbox me files that I can already see but can't download to troubleshoot b/c they're invalid.
Let's add the header too.

Closed by https://github.com/biocore/qiita/pull/2403


Lab 8 PR

That's a lot of text to be seeding with but at least your PostText is easy to find! Don't forget to remove comments as well, figure id mention that too.  I only see two seeded posts rather three, dont forget to add that and keep in mind! But everything that is there is working. Well done.


feat: import from autoware_common/tmp

This PR is the re-submission of #1.
Based on https://github.com/autowarefoundation/autoware_lanelet2_extension/pull/1#issuecomment-2088133019, I modified it to use git subtree split to take over the commit tree.

This PR has Imported lanelet2_extention and lanelet2_extention_python packages from https://github.com/autowarefoundation/autoware_common
Note that autoware_ prefix change is not included here. I will do it on the next PR.
ref. https://github.com/orgs/autowarefoundation/discussions/4671

I would keep this PR to a minimal revision. So the fix for the clang-tidy error will be done in a separate PR.
https://github.com/autowarefoundation/autoware_lanelet2_extension/actions/runs/8914954856/job/24484113442
https://github.com/autowarefoundation/autoware_lanelet2_extension/pull/2/commits/839a72a362bc603fc5a83c139977965f70abe90e