Unsupported URL Type "link:": link:../node_modules/bootstrap

Describe the bug
I failed to run "npm install" into the vite playground directory.
Reproduction

clone the vite project.

cd into the vite project. and run " npm install"

cd into the playground project.and run " npm install"

I get error as follows:

         src-import            tsconfig.json
➜  playground git:(master) ✗ npm install
npm ERR! code EUNSUPPORTEDPROTOCOL
npm ERR! Unsupported URL Type "link:": link:../node_modules/bootstrap

npm ERR!      /Users/snowdream/.npm/_logs/2020-10-25T14_15_17_399Z-debug.log

The log file "/Users/snowdream/.npm/_logs/2020-10-25T14_15_17_399Z-debug.log":
playground git:(master) ✗ cat /Users/snowdream/.npm/_logs/2020-10-25T14_15_17_399Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/Users/snowdream/.nvm/versions/node/v12.8.1/bin/node',
1 verbose cli   '/Users/snowdream/.nvm/versions/node/v12.8.1/bin/npm',
1 verbose cli   'install'
1 verbose cli ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose npm-session 046c51ef0a28ff33
5 silly install runPreinstallTopLevelLifecycles
6 silly preinstall playground
7 info lifecycle @~preinstall: @
8 silly install loadCurrentTree
9 silly install readLocalPackageData
10 timing stage:loadCurrentTree Completed in 7ms
11 silly install loadIdealTree
12 silly install cloneCurrentTreeToIdealTree
13 timing stage:loadIdealTree:cloneCurrentTree Completed in 0ms
14 silly install loadShrinkwrap
15 timing stage:loadIdealTree:loadShrinkwrap Completed in 2ms
16 silly install loadAllDepsIntoIdealTree
17 timing stage:rollbackFailedOptional Completed in 0ms
18 timing stage:runTopLevelLifecycles Completed in 33ms
19 silly saveTree playground
20 verbose stack Error: Unsupported URL Type "link:": link:../node_modules/bootstrap
20 verbose stack     at unsupportedURLType (/Users/snowdream/.nvm/versions/node/v12.8.1/lib/node_modules/npm/node_modules/npm-package-arg/npa.js:200:15)
20 verbose stack     at fromURL (/Users/snowdream/.nvm/versions/node/v12.8.1/lib/node_modules/npm/node_modules/npm-package-arg/npa.js:258:13)
20 verbose stack     at Function.resolve (/Users/snowdream/.nvm/versions/node/v12.8.1/lib/node_modules/npm/node_modules/npm-package-arg/npa.js:77:12)
20 verbose stack     at /Users/snowdream/.nvm/versions/node/v12.8.1/lib/node_modules/npm/lib/install/deps.js:484:20
20 verbose stack     at Array.map (<anonymous>)
20 verbose stack     at /Users/snowdream/.nvm/versions/node/v12.8.1/lib/node_modules/npm/lib/install/deps.js:483:47
20 verbose stack     at tryCatcher (/Users/snowdream/.nvm/versions/node/v12.8.1/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)
20 verbose stack     at Promise._settlePromiseFromHandler (/Users/snowdream/.nvm/versions/node/v12.8.1/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:517:31)
20 verbose stack     at Promise._settlePromise (/Users/snowdream/.nvm/versions/node/v12.8.1/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:574:18)
20 verbose stack     at Promise._settlePromiseCtx (/Users/snowdream/.nvm/versions/node/v12.8.1/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:611:10)
20 verbose stack     at _drainQueueStep (/Users/snowdream/.nvm/versions/node/v12.8.1/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:142:12)
20 verbose stack     at _drainQueue (/Users/snowdream/.nvm/versions/node/v12.8.1/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:131:9)
20 verbose stack     at Async._drainQueues (/Users/snowdream/.nvm/versions/node/v12.8.1/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:147:5)
20 verbose stack     at Immediate.Async.drainQueues [as _onImmediate] (/Users/snowdream/.nvm/versions/node/v12.8.1/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:17:14)
20 verbose stack     at processImmediate (internal/timers.js:439:21)
21 verbose cwd /Users/snowdream/workspace/vue/vite/playground
22 verbose Darwin 19.6.0
23 verbose argv "/Users/snowdream/.nvm/versions/node/v12.8.1/bin/node" "/Users/snowdream/.nvm/versions/node/v12.8.1/bin/npm" "install"
24 verbose node v12.8.1
25 verbose npm  v6.12.0
26 error code EUNSUPPORTEDPROTOCOL
27 error Unsupported URL Type "link:": link:../node_modules/bootstrap
28 verbose exit [ 1, true ]

System Info

required vite version: 1.0.0-rc.6

required Operating System: macOS 10.15.7

required Node version:
v12.8.1

Optional:

npm/yarn version
npm -v
6.12.0
Installed vue version (from yarn.lock or package-lock.json)
"vue": "^3.0.0-rc.10",
Installed @vue/compiler-sfc version
"@vue/compiler-sfc": "^3.0.0-rc.10",

Logs (Optional if provided reproduction)

Run vite or vite build with the --debug flag.
Provide the error log here.

Vite requires using Yarn for its own development.

Can you support npm for Vite's own development?

@snowdream
In your single-file-component simply add this
<style>
@import 'bootstrap/dist/css/bootstrap.min.css';
</style>

In vue-cli you had to prefix it with ~ but not in vite

@snowdream
In your single-file-component simply add this
<style>
@import 'bootstrap/dist/css/bootstrap.min.css';
</style>

In vue-cli you had to prefix it with ~ but not in vite


Webcomponents/Polymer

Note: for support questions, please use one of these channels: Chat: AngularClass.slack or Twitter: @AngularClass

I'm submitting a ...
[x ] bug report
[ ] feature request
[ ] question about the decisions made in the repository

Do you want to request a feature or report a bug?
I´m not sure if it is a bug or a feature reqquest.

What is the current behavior?
The current behavior is, that webcomponents on browsers where the polyfills kick in are not working.
Can you give me a advise how to change the configuration of the project to load the main module just after the Webcomponentsready Event?

What is the expected behavior?
I can bundle my application with webcomponents/polymer for development and for production. Even with aot enabled.

What is the motivation / use case for changing the behavior?
Webcomponents/polymer are just so much nicer components to build a state of the art web application and don´t have to to the boilerplet again and again.

Please tell us about your environment:

Angular version: 2.4.3
Browser: [all browsers that do not natively support webcomponents ]

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

@ITServicesAM Have not tested that yet, could you provide some code? So, could your share a repo?

Here is my repo: Repo
the webpack.common.js is changed to load a new main.ts if not aot
the main.ts loads the main.browser.ts when the event "webcomponentsready" occurs.
This is just a try to get it working. If you have a better idea to get this working, I would love to here it.
In the app.module.ts, index.html and home.component.html are the changes for polymer
(Polymer Docs)
In the quick start section of the readme of the repo you can find instructions how to install this project

Hi,
I do have Polymer elements working fine.

create a main-polymer.ts that contains: document.addEventListener('WebComponentsReady', () => {require('./main.browser.ts')});

your webpack.config.ts or webpack.common.ts may then contain:    entry: {
'polyfills': './src/polyfills.browser.ts',
'vendor':    './src/vendor.browser.ts',
'main':      './src/main-polymer.ts'
},

That's it.
Then you're sure that your polymer elements are loaded and working before your app get loaded.
I hop that's what you where looking for.

@otiteca We don't have a vendor file anymore.
@ITServicesAM You are setting up the polyfil in https://github.com/ITServicesAM/angular_2_polymer/blob/master/src/main.browser.aot.ts which is for AOT only.
You should also set it here: https://github.com/ITServicesAM/angular_2_polymer/blob/master/src/main.browser.ts
Using require might lead to unexpected AOT compilation result, its not 100% but it's not a good practice anyway.
If my suggestion isn't working it means that the main file can init before polymer is ready, even if  bootstrap not initialized...
lets see

do you have a code example for me? I set the polyfil for the main.browser.ts not directly, I set it in the webpack.common.ts there I have a entry point for non aot builds which requires the main.browser.ts but this is not working.


ModuleNotFoundError: No module named 'xdg.BaseDirectory'

Archlinux installed using pip

i face this error

then i installed "xdg" then it shows like this

Did you run pip install pyxdg? It seems that I overlooked this dependency when uploaded to pypi

i installed pip install pyxdg

The program needs a command line argument to work like lastfm-mpris2-scrobbler -c PATH_TO_YOUR_CONFIG/config.yaml, for more information on how to use it, you may refer to the Usage section of README, also on how to write the config file at Configurations section

thanks ❤

Any reason pyxdg isn't in requirements.txt or setup.py? I ran into the same issue after cloning and installing into a virtualenv and luckily found this issue because the top results for xdg on pypi didn't seem to fix the issue...

Any reason pyxdg isn't in requirements.txt or setup.py? I ran into the same issue after cloning and installing into a virtualenv and luckily found this issue because the top results for xdg on pypi didn't seem to fix the issue...

Sorry for the confusion, it's my mistake when packing it. I'm now busy working on other stuff and haven't got time to update it


Unable to deploy to Heroku

In case app/assets/stylesheets/application.tailwind.css is added to .gitignore, Heroku is unable to build applications because file is missing, I think we should prepare application.tailwind.css before compilation when running assets:precompile

In case app/assets/stylesheets/application.tailwind.css is added to .gitignore, Heroku is unable to build applications because file is missing, I think we should prepare application.tailwind.css before compilation when running assets:precompile

now it is resolved in version 0.2.1 👌


e.g. fairseq-train-script.py install during "pip install --editable ." suggestion please

I have no problem running
pip install --editable .

However, this leads to non-working e.g. fairseq-train.exe
Running fairseq-train.exe leads to calling the local source code faireq\fairseq-cli\train.py
Which then looks for ..\train.py of the fairseq root directory
Using pip install fairseq
only the fairseq-train.exe are installed without the fairseq-train-script.py
Any suggestion?

Can't you run your local source code?

@wiany11 Yes, I can do python (local) fairseq-generate.py
But I hope to get feedback what I did wrong by doing
pip install --editable .
Where can I change to get the right  e.g. fairseq-generate.exe  install. Thanks.


Not able to provision API keys after removal

Description:
I have successfully deployed API keys previously, however after I have deleted them from Api Gateway console, now I am not able to provision them anymore, the deployment goes smoothly, no error, but when I go and check them through the aws console the screen does't show them
Steps to reproduce the issue:
This is my SAM template
Resources:
  #API GATEWAY ========================================
  myAPI:
    Type: AWS::Serverless::Api
    Properties:
      StageName: !Ref Environment
      DefinitionBody:
        swagger: "2.0"
        info:
          title:
            Ref: AWS::StackName
        x-amazon-apigateway-api-key-source: HEADER
        securityDefinitions:
          myAPIKey:
            type: "apiKey"
            name: "x-api-key"
            in: "header"
        paths:
          /path/invocation:
            post:
              responses: {}
              x-amazon-apigateway-integration:
                uri: !Sub arn:aws:apigateway:${AWS::Region}:lambda:path/2015-03-31/functions/${myFunction.Arn}/invocations
                httpMethod: "POST"
                type: "aws_proxy"
              security:
                - myAPIKey: []

  myAPIKey:
    Type: AWS::ApiGateway::ApiKey
    Properties:
      Enabled: true

  myUsagePlan:
    Type: AWS::ApiGateway::UsagePlan
    Properties:
      ApiStages:
        - ApiId: !Ref myAPI
          Stage: !Ref Environment

  myUsagePlankey:
    Type: AWS::ApiGateway::UsagePlanKey
    Properties:
      KeyId: !Ref myAPIKey
      KeyType: API_KEY
      UsagePlanId: !Ref myUsagePlan

Observed result:
No error, the deployment is successful, but the api key are not showing and the usage plan is not connected to any key
Expected result:
It should provision the key

Ok, I have managed to provision my key again. I had to deploy a new version of my app without APIkey, UsagePlan and UsagePlanKey.
After that I had re-deployed my original app including again those resources.
Just wondering, why is that happening? Thanks

I think this is an expected behaviour because of CloudFormation only deploys changes of you stack, it didn't know anything about external changes. CF only applies the changes of your template, so there was only a change for CF as you removed it from your template and a change as you added them again.

@timoschilling Thank you for the response. Closing this as it is an expected CloudFormation behavior


using numpy

this change lower the data usage about 5x
if we would used compressed pandas ot would be 20x

(1) First of all, when I test it locally, I got this:

charsplit.Splitter().split_compound("Autobahnstrecke")
[[nan, 'Aut', 'Obahnstrecke'], [0.85609055, 'Auto', 'Bahnstrecke'], [nan, 'Autob', 'Ahnstrecke'], [nan, 'Autoba', 'Hnstrecke'], [nan, 'Autobah', 'Nstrecke'], [0.94372, 'Autobahn', 'Strecke'], [nan, 'Autobahns', 'Trecke'], [nan, 'Autobahnst', 'Recke'], [nan, 'Autobahnstr', 'Ecke'], [nan, 'Autobahnstre', 'Cke']]

which is not the expected behavior.
(2) After looking at data_io for a while, I think I kind of understand how you create and load the numpy array, but only after some time (which is my inexperience, ok) -- so my main problem, is disc space really an issue here worth replacing a simple json.dump({"a": "b"}) by such complex a code? Somehow I couldn't get rid of a feeling that it's not the most natural use of numpy..
(3)  Probably ok, I just got some warnings regarding the automatic test (if I understand the >>> thing correctly).  DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
import imp
(and another one, less understandable, when running data_io from terminal)


jet-dev/rets_reply_codes

@zacronos
Attached is some structure for adding rets reply code handling, similar to how http codes are sometimes handled with meaningful constants.

Cool ok - added a commit for coffescript version

LGTM, thanks for the contribution!


EffectPass introduces facing problems with InstancedGeometry

Hello!
I premise that I have not yet been able to reproduce the bug on a codesandbox because the model I am using is in a special format and I have to ask the client I am working for to export a gltf one.
As soon as I can I'll do that, in the meantime I'll expose the problem I'm experiencing, maybe we don't even need the demo.
I am using a simple pipeline with RenderPass + EffectPass[BloomEffect], to render a lowpoly model as shown in the attached image.
Basically it is a model of a rock made up of several pieces, to which I will then have to apply an animation for the explosion (I think this info is not very relevant)
This model must be reproduced several times, so I am using an InstancedBufferGeometry.
The bug consists of a strange rendering of the mesh faces, in particular these strange artefacts increase as the distance from the camera increases. as shown in the figure.
In particular the problem only occurs when I use the EffectPass, even when it has no effect and is therefore "empty".
If I only use RenderPass instead, there is no problem whatsoever
I am already aware of the possible problems with InstancedBufferGeometry and the use of the OverrideMaterialManager, but using only the BloomEffect should not be the case, right? (in any case the bug exists even with workaroundEnabled)
I don't seem to be doing strange things at the code level
OverrideMaterialManager.workaroundEnabled = true;
...
const renderer = new THREE.WebGLRenderer({ canvas: this.canvas, context: this.gl, powerPreference: 'high-performance', antialias: false, stencil: false, depth: false });
...
this.composer = new EffectComposer(this.renderer, {
	frameBufferType: THREE.HalfFloatType,
	multisampling: 8,
});

this.renderPass = new RenderPass(this.scene, this.camera);
this.composer.addPass(this.renderPass);

this.bloomEfx = new BloomEffect({
	mipmapBlur: true,
});
this.effectPass = new EffectPass(this.camera, this.bloomEfx);
this.composer.addPass(this.effectPass);

The doubt came to me that this is a model-related problem. But then I cannot explain the different behaviour with and without EffectPass.
Library versions used

Three: ^0.143.0
Post Processing: ^6.28.5

Thank you!

Thanks for the report!
Does this also happen when you disable multisampling?

Hey super quick!
Yes, just tried with this code and I'm having the same behaviour
		this.composer = new EffectComposer(this.renderer, {
			frameBufferType: THREE.HalfFloatType,
			multisampling: 0,
		});

oh! I am looking at the code for OverrideMaterialManager.js
is it possible that the problem stems from the fact that I am not using InstancedMesh but InstancedBufferGeometry?
In particular I'm referring to this line of code

I don't think this is related to the OverrideMaterialManager, and the model is probably fine too. The steplike artifacts make me think it's somehow related to depth precision :thinking:
If you only use a RenderPass, the scene is rendered directly to screen and when you add a fullscreen pass, the scene is rendered to an internal buffer instead. But rendering to the canvas should cause other depth issues if you create the renderer correctly, because the canvas wouldn't have a depth buffer.
This means that the following code is wrong, because the gl parameters are ignored when you provide a canvas or a context:
const renderer = new THREE.WebGLRenderer({ canvas: this.canvas, context: this.gl, powerPreference: 'high-performance', antialias: false, stencil: false, depth: false });

It should be this instead:
// https://www.khronos.org/webgl/public-mailing-list/public_webgl/1703/msg00022.php
canvas.addEventListener("webglcontextrestored", () => {});
canvas.addEventListener("webglcontextlost", (event) => {

	event.preventDefault();
	window.location.reload();

}, false);

const renderer = new THREE.WebGLRenderer({
	powerPreference: "high-performance",
	antialias: false,
	stencil: false,
	depth: false,
	canvas
});

Maybe the device you're testing on doesn't support UnsignedIntType depth. Please try enabling stencilBuffer to check if that fixes the issue:
const composer = new EffectComposer(renderer, { stencilBuffer: true });

Maybe the device you're testing on doesn't support UnsignedIntType depth. Please try enabling stencilBuffer to check if that fixes the issue:
const composer = new EffectComposer(renderer, { stencilBuffer: true });

It works!
just to understand, is this a workaround that affects my performance in some way or can we call it a solution to the problem?

That's a solution, but it means that your device is not WebGL compliant and claims that it supports UnsignedIntType, but uses a low precision fallback instead :cry:

With stencilBuffer set to true, the EffectComposer uses UnsignedInt248Type instead for the depth texture which absolutely has to be supported by all devices. I'm considering using that as the new default now that there's actually a reported case of UnsignedIntType failing.

your device is not WebGL compliant

Actually it is compliant, the spec just says that devices may chose to use lower precision like 16 bits which kind of makes sense since UnsignedIntType doesn't specify the size.

thanks for the explanation, everything is clearer now
thank you so much!

I had to change the default depth texture type back to UnsignedIntType in<EMAIL_ADDRESS>because the previous switch to UnsignedInt248Type caused another issue with multisampling due to a missing stencil buffer.
I recommend enabling stencilBuffer explicitly if you require at least 24 bits of depth precision on any device. Otherwise try to tune your camera near/far plane settings to still produce satisfactory results with lower precision if possible.


favicon

How to add favicon.ico in a right way? I have put it into assets/ folder and added link in index.html
<link rel="shortcut icon" href="/app/assets/favicon.ico" type="image/x-icon" />

But it will not work for production.

Added join(APP_SRC, '**/*.ico') in tools/tasks/build.img.dev.ts and changed link to
<link rel="shortcut icon" href="assets/favicon.ico" type="image/x-icon" />

Just like you mentioned, you need to keep the path relative (i.e. ./assets/favicon.ico).


chore(main): release 1.6.1

:robot: I have created a release beep boop
1.6.1 (2022-12-09)
update

update files (aa5120d)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/School-of-Website-Engineering/Rosy-DR-Code-Ling/releases/tag/v1.6.1 :sunflower:


Heads up -- Apple just rejected our app due to the custom status bar

Received this email today:
We found your app uses system-provided items in a non-standard manner, which is not in compliance with the App Store Review Guidelines.
Specifically, we found your app animates the status bar. Please see the attached screenshot for reference to the issue [screen shot shows the custom status bar saying "Up To Date"].
Learn more about system-provided items in the iOS Human Interface Guidelines, sections: "System-Provided Buttons and Icons" and "iOS UI Element Usage Guidelines."

I am planning on using this nice status bar. Is the app store still an issue or do they approve this control now? Thank you.

I don't think many apps get rejected for this @oyalhi, but because of the subjective nature of the app review process, it is a risk.  Here are the current guidelines on the status bar.
You could always go for it, and just take it out if it gets rejected.


example using fast android networking

can you add example using fast android networking ?

will try right now am busy with some other stuff will add once am free


Add ruby feature to neovim-flake (WIP)

Description
A clear and concise description of the aim of your Pull Request.
If your pull request aims to fix an open issue or a present bug, please link the relevant issue below. If not, please remove this section
Fixes #(issue)
Type of change

New feature (non-breaking change which adds functionality)
Docs

Checklist
Please try to check at least a majority of the checklist before opening your pull request. PRs
Exceptions to this will be reviewed on a case by case basis.

[x] My code follows the style and contributing guidelines of this project.
[x] I ran Alejandra to format my code.
[x] I have performed a self-review of my own code and tested it.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generate no new warnings.
[x] This change requires a documentation update.
[x] I have updated the documentation accordingly.

Screenshots & Logs
Incoming when it works

Side note, I would appreciate it if you could add a debugger configuration for the Ruby language.

Closing, as per the discussion with @Vagahbond.


link: Set prefixLen for loopback address

The prefixLen for a loopback address is well-defined (/32),
and as such the variable is set accordingly.
Previously, loopback interfaces kept prefixLen set to None,
which was troublesome.

I think it should be 8?

My bad, I got confused with the v6 loopback which defaults to the full /128. I fixed the patch accordingly ...


Want to fill the 'like' button with red color when we are clicking.

Hey, I want to add this feature to the website.Please assign me this issue under GSSOC'23.

another candidate already working on this same issue.


user_groups: Migrate to @typed_endpoint.

migrate the following endpoints from @has_request_variables to @typed_endpoint:

get_user_group()
delete_user_group()
update_user_group_backend()
update_subgroups_of_user_group()
get_is_user_group_member()
get_user_group_members()
get_subgroups_of_user_group()

LGTM, @zulipbot add "maintainer review"

@timabbott are you reviewing this next?

Yeah, this migration only has like 3 files left, it makes sense for me to review.
Pushed a cleanup to how the thunks are managed to avoid polluting helpers with the | None type that don't need to be called at all, and marked to merge once CI passes. We'll likely want to use the same technique for the update_subscriptions_backend function; it should clean that up too.

I guess the response format for channel changes expects all the thunks to be called, so dropped that extra commit.


New release 0.16.1 request for kube 1.19 fixes

Type of question
Release request to help support and test with kube 1.19.
Question
Trying to run OLM on kube 1.19, need the https://github.com/operator-framework/operator-lifecycle-manager/pull/1562 and https://github.com/operator-framework/operator-lifecycle-manager/pull/1680
for that to work well.
What did you expect to see?
0.15.2 release
What did you see instead? Under which circumstances?
No new release after that kube 1.19 PR was merged.
Environment

Kubernetes version information:

1.19

Kubernetes cluster kind:

Additional context
cc @ecordell

@ecordell Any ideas on new release to pick these up?

@ecordell @awgreene @njhale Bump on this?

We should be cutting a new release shortly. We had cut a 0.16.0 on 1.19 but ran into some issues.

@exdx Thx for the update.

Testing on 1.1.9 now...

Closing, appears to work on 1.19 now.


Update default value for volume mounts' default mode based on usage

Description
This PR updates the default value for the Zeebe chart's StatefulSet configuration volume mount defaultMode. The defaultMode was previously 0744, which means it was not executable anyone but the owner. For OpenShift deployment, it's simpler to adjust it to be executable by the group as well, which doesn't have that much impact on other deployments, so it will simplify things.
For all others, the defaultMode remains 0744. Additionally, it was not specified for the curator cronjob, and it's now hardcoded to 0744 (since it's only meant to be read).
Related issues
closes #345

Shoo, go away, enjoy your holidays.


Chore/config handler spies test helpers

Description:
I introduced a helper function in https://github.com/ReactiveX/rxjs/pull/6169/files#diff-9e451a38948f76e3294d51d3a213e0e9d0170c3d327a871e1435a457a8268125R28 to more easily test the global config handlers.
With this PR I want to extract it into a general helper function in helpers/test-helper and convert existing config tests (or other tests involving the global config handlers) to use the helper. This also makes the config tests more readable imho, because the code order now matches the execution order.
I also removed a duplicated test in Observable-spec.ts which had the same test code as one of the config-spec tests.
BREAKING CHANGE:
While implementing the helper and converting the config-spec tests, I noticed a small discrepancy between how onUnhandledError and onStoppedNotification are handled. In the last commit, I adjusted onUnhandledError handling to match that of onStoppedNotification and added appropriate tests. this might be considered a BC break in the following case:
// current behavior
config.onUnhandledError = () => console.log('I am not called.');

new Observable((subscriber) => {
  subscriber.error('bad');
}).subscribe();

config.onUnhandledError = () => console.log('But I am!');

// behavior after the change
config.onUnhandledError = () => console.log('I am called!');

new Observable((subscriber) => {
  subscriber.error('bad');
}).subscribe();

config.onUnhandledError = () => console.log('But I am not.');

added one more test case for the execution order of onUnhandledError & onStoppedNotification

Thank you for this pr @backbone87. I'm going to add this to the Core Team agenda so we can decide which behavior is appropriate. While it might be a breaking change for someone, I think I personally see this as a bug fix, and it might be worth introducing in a patch. These features aren't very broadly used yet, to my knowledge. Particularly in this edge case.

rebased against master

Core Team meeting again: Punting. Not enough for quorum

Core Team: This is a bug fix and not a breaking change. We don't want people to "know" that the error is being handling asynchronously if it was synchronously thrown, the change to the handler shouldn't be honored. This may also help set us up for reportError usage. Related: #6795

I'm so sorry, @backbone87 ... but this PR has a lot going on in it, and it's been so long since I looked at it, that I'm going to close it for now, in favor handling the identified bug in another PR.


Add a wiki: Genfanad Wiki

An anonymous user has submitted a new wiki via our submission form.
Link to origin wiki: https://genfanad.fandom.com/wiki/Genfanad_Wiki
Link to destination (independent) wiki: https://genfanad.info/

The Wikis are very similar to each other in layout, content and quantity of pages (1,769 vs. 1792). While both seem to have activity, the destination wiki does have more. A quick skim of a few pages does show that some content is more up-to-date than the origin wiki as well.

Added in commit https://github.com/KevinPayravi/indie-wiki-buddy/commit/aaefcbd4688d252d5f5b7ae5e4285c95e85f6354

Now available in version 2.3.0


Fix: Helper Height

Summary
Height defined in getHelperDimensions() was not applied to the helper. This is fixed here.
*please ignore wrong reference getHelperStyle() in commit message, this meant to be getHelperDimensions().

@clauderic Hi, thanks for the work so far. I really like the component a lot. 👍 🎉
Would be nice if you could take a quick look at this PR in the coming days 😊

Hey @SMenigat, thanks for the kind words 😄
This looks good, let's get it merged 🚢


DJI mavic 3T

Hi,
does it work with DJI mavic 3T model thermal images?
I get this error, any advice on how to solve this:
(thermal_env) D:\Downloads\thermal_conversion_demo-main\thermal_conversion_demo-main>python tir_convert.py
Traceback (most recent call last):
File "tir_convert.py", line 24, in
temperature = thermal.parse_dirp2(image_filename=i)
File "D:\Downloads\thermal_conversion_demo-main\thermal_conversion_demo-main\thermal.py", line 789, in parse_dirp2
assert return_status == Thermal.DIRP_SUCCESS, 'dirp_set_measurement_params error {}:{}'.format(image_filename, return_status)
AssertionError: dirp_set_measurement_params error images\DJI_20230825215003_0007_T.JPG:-3
(thermal_env) D:\Downloads\thermal_conversion_demo-main\thermal_conversion_demo-main>

Hi,
thank you for the code. For me it seems to be working with the provided demo image, but with DJI Mavic 3T images I get a similar error as described above. Error pasted below:
Traceback (most recent call last):
File "C:\thermal_conversion\tir_convert.py", line 24, in
temperature = thermal.parse_dirp2(image_filename=i)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\thermal_conversion\thermal.py", line 789, in parse_dirp2
assert return_status == Thermal.DIRP_SUCCESS, 'dirp_set_measurement_params error {}:{}'.format(image_filename, return_status)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: dirp_set_measurement_params error images\DJI_20230921173941_0001_T.JPG:-3

Okay it seems that there is some differences in the image exif-data (ZH20T - M3T). K1 - KK parameters are missing completely below Thermal data. Would it be possible to get this working with M3T as well?
Exampleimage-exif.txt
M3T-exif.txt


feature: add tor support by using arti-hyper with new feature async-arti-hyper

What
As mentioned and discussed at https://github.com/bitcoindevkit/bdk/issues/66 adding Tor support to both rust-esplora-client or rust-electrum-client is really useful as an alternative to the current SOCKS proxy support, and adds another layer of privacy and anonymity for BDK, and other crates that rely on rust-esplora-client.
That said, why the new releases of Arti it became somewhat easy to add support for Tor, even more so for HTTP-based requests such as this crate, arti-client can be used in a way to have Tor support as async streams requiring some work with it's APIs and streams.
The Arti team already added support to HTTP requests by using hyper, keeping its usage APIs and usage, through arti-hyper.
As rust-esplora-client has support for both blocking/async/TLS/SOCKS based on its feature flags, I think that adding Tor support by using arti-hyper, and exposing it as a new feature flag, such as: async-arti-hyper would be a good approach.

NOTE: For the long-run I think that adding a different approach, as a new feature or refactor that is based on usage of different data streams, selected or built by the user, would make it easier to add support for different transport layers using the same API, something similar to what have been done on electrum_client::client::ClientType

How
It can be done by adding a new feature and adding support for all HTTP calls with arti-hyper, I think it's somewhat straightforward, and I can get it started working if it seems like a good approach.
If you are curious about arti-hyper and hyper usage, you can check both docs/examples:

https://gitlab.torproject.org/tpo/core/arti/-/blob/main/crates/arti-hyper/examples/hyper.rs
https://github.com/hyperium/hyper/tree/master/examples

@notmandatory @vladimirfomene Do you have any thoughts on this approach?

As posted on discord: I'm not aware of any localhost tor testing frameworks , how do you currently do manual testing? for now it's probably enough to have detailed  testing instructions and/or script that can be run manually for others working on that feature until we can come up with something automated in CI

As posted on discord: I'm not aware of any localhost tor testing frameworks , how do you currently do manual testing? for now it's probably enough to have detailed testing instructions and/or script that can be run manually for others working on that feature until we can come up with something automated in CI

I'm currently manually testing with the testnet endpoints on https://blockstream.info/ and trying to manually test with their OnionV3 service too.
Sure, the testing instructions and a script with a different CI step is feasible, I'll follow this strategy then.

update:
I've been working and using the https://blockstream.info/api for building the tests, but it seems flaky when connecting to it over Tor, some exit nodes work, and some receive a 403 Forbidden.
I'll check how arti-hyper, and arti handle the connection to hidden services, as another option in such scenarios, although it's not very stable on their side/implementation yet.


I am not sure if this is a problem in sphinx or in confluencebuilder the objects.inv file is not required

When I publish to confluence I get the following:
publishing assets... [100%] objects.inv
sphinxcontrib.confluencebuilder error:

Unsupported Confluence API call
An unsupported Confluence API call has been made. See the following
details for more information:
REQ: POST
RSP: 500
URL: redacted
API: content/252944754/child/attachment
DATA: {
"actionErrors": [
"This file type is not allowed."
]
}
make[1]: *** [confluence] Error 2
make: *** [confluence] Error 2
I see in my _build folder the objects.inv file is created, however I do not believe it is actually required and I see no way to stop it being produced. This error was not present in earlier iterations of my docs. The other objects do publish I believe this is the last object it attempts.
Sorry it is so vague.

Interesting. Curious to know why the file type is restricted, but I assume it is either an administrator setting for the instance, or maybe some addon which restricts certain file types.
Fortunately, there is a configuration option to disable the publication of the Intersphinx database. Adding the following should prevent this error from happening:
confluence_publish_intersphinx = False

Also, thanks for reporting this. Maybe we should tweak the implementation to generate a warning in the use case when publishing this file and this error message is generated.

Interesting. Curious to know why the file type is restricted, but I assume it is either an administrator setting for the instance, or maybe some addon which restricts certain file types.
Fortunately, there is a configuration option to disable the publication of the Intersphinx database. Adding the following should prevent this error from happening:
confluence_publish_intersphinx = False

Also, thanks for reporting this. Maybe we should tweak the implementation to generate a warning in the use case when publishing this file and this error message is generated.

Yes, Heavily restricted environmnet, Thank you for the info I will try it.

I would wonder why it is published by default.

The purpose of publishing the Intersphinx database file is to provide flexibility for other documentation sets using Intersphinx to have a place to reference/fetch external references to properly link documentation sets together. There is an outline of the intent (and current limitations) in https://github.com/sphinx-contrib/confluencebuilder/pull/690.
It will most likely be the case that this database attachment will remain as on by default, since the use of Akeles Consulting's "Attachment Checker for Confluence" (assumed to be the addon in question, based on the provided output message) is most likely only a small percentage of all Confluence instances. That being said, a tweak (https://github.com/sphinx-contrib/confluencebuilder/pull/783) has been introduced to help generate a warning in the case that this addon restricts an attachment type. This should make things easier for environments with this addon installed. And to avoid such a warning, the use of utilizing the confluence_publish_intersphinx option will be the best way forward to avoid publishing the Intersphinx  database.

With https://github.com/sphinx-contrib/confluencebuilder/pull/783 merged in and workarounds available for instances using the attachment checker addon, I will go ahead and close this issue. Thanks again for reporting this use case.


broken link

In What is XR? page, The following URL links on this page are broken.
https://ashy-plant-023e6671e.1.azurestaticapps.net/quiz/0

In What is XR? page, The following URL links on this page are broken. https://ashy-plant-023e6671e.1.azurestaticapps.net/quiz/0

Yes. Was this resolved? the link is still broken.

☹


docs(contributors): add @travi

Thanks for the bug report!
Are you ok with this @travi?

Current coverage is 100% (diff: 100%)

Merging #64 into master will not change coverage

@@           master   #64   diff @@
===================================
  Files           3     3
  Lines          94    94
  Methods         0     0
  Messages        0     0
  Branches        0     0
===================================
  Hits           94    94
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update ea45ffd...602ee54


Log does not need to output to logfile

These params are ignored by the function. This change was made in #1323, but this still needs to be cleaned up.
https://github.com/spacemeshos/go-spacemesh/blob/61eafeeb2a9e3ec785113cf8284eec8bf8ef6ee9/log/log.go#L127-L129
In fact AFAICT all of the functionality for logging to a file is not used anywhere (except in the log tests).

Is this just a matter of removing the function params then cleaning up the instances where it's called? If so, I can clean this up.


Version 2.0.0 (master) does not build with sleef / no_std features enabled

@arduano did an overhaul of the SIMD traits. That was a big undertaking and has many nice improvements like operator overloading.
I am trying to port my stuff over to use the v2.0.0-dev3 (current master) branch and I noticed that there 3 problems:

it does not build with no_std (cargo build --features "no_std")

it does not build with no_std (cargo build --features "sleef")

it seems that only scalar is exposed. A simple test program with sse2, sse41 or avx2 will fi lead to failed to resolve: could not find 'avx2'in 'simdeez' ...^^^^^ could not find 'avx2' in 'simdeez'`.

Here is a simple test program (src/main.rs):
use simdeez::prelude::*;

use simdeez::avx2::*;
use simdeez::scalar::*;
use simdeez::sse2::*;
use simdeez::sse41::*;

// If you want your SIMD function to use use runtime feature detection to call
// the fastest available version, use the simd_runtime_generate macro:

fn main() {
    simd_runtime_generate!(
        fn distance(x1: &[f32], y1: &[f32], x2: &[f32], y2: &[f32]) -> Vec<f32> {
            let mut result: Vec<f32> = Vec::with_capacity(x1.len());
            result.set_len(x1.len()); // for efficiency

            // Set each slice to the same length for iteration efficiency
            let mut x1 = &x1[..x1.len()];
            let mut y1 = &y1[..x1.len()];
            let mut x2 = &x2[..x1.len()];
            let mut y2 = &y2[..x1.len()];
            let mut res = &mut result[..x1.len()];

            // Operations have to be done in terms of the vector width
            // so that it will work with any size vector.
            // the width of a vector type is provided as a constant
            // so the compiler is free to optimize it more.
            // S::Simd::Vf32::WIDTH is a constant, 4 when using SSE, 8 when using AVX2, etc
            while x1.len() >= S::Vf32::WIDTH {
                //load data from your vec into an SIMD value
                let xv1 = S::Vf32::load_from_slice(x1);
                let yv1 = S::Vf32::load_from_slice(y1);
                let xv2 = S::Vf32::load_from_slice(x2);
                let yv2 = S::Vf32::load_from_slice(y2);

                let mut xdiff = xv1 - xv2;
                let mut ydiff = yv1 - yv2;
                xdiff *= xdiff;
                ydiff *= ydiff;
                let distance = (xdiff + ydiff).sqrt();
                // Store the SIMD value into the result vec
                distance.copy_to_slice(&mut res);

                // Move each slice to the next position
                x1 = &x1[S::Vf32::WIDTH..];
                y1 = &y1[S::Vf32::WIDTH..];
                x2 = &x2[S::Vf32::WIDTH..];
                y2 = &y2[S::Vf32::WIDTH..];
                res = &mut res[S::Vf32::WIDTH..];
            }

            // (Optional) Compute the remaining elements. Not necessary if you are sure the length
            // of your data is always a multiple of the maximum S::Simd::Vf32::WIDTH you compile for (4 for SSE, 8 for AVX2, etc).
            // This can be asserted by putting `assert_eq!(x1.len(), 0);` here
            for i in 0..x1.len() {
                let mut xdiff = x1[i] - x2[i];
                let mut ydiff = y1[i] - y2[i];
                xdiff *= xdiff;
                ydiff *= ydiff;
                let distance = (xdiff + ydiff).sqrt();
                res[i] = distance;
            }

            result
        }
    );

    let x1 = vec![0.0, 1.30, 2.3, 4.0];
    let y1 = vec![0.0, 1.30, 2.3, 4.0];
    let x2 = vec![0.0, 1.30, 2.3, 4.0];
    let y2 = vec![0.0, 1.30, 2.3, 4.0];

    //distance_scalar
    //distance<S:Simd>` the generic version of your function
    let got = distance_scalar(x1.as_slice(), y1.as_slice(), x2.as_slice(), y2.as_slice());
    //distance_runtime_select
    //distance_sse2
    //distance_sse41
    //distance_avx
    //distance_avx2
    //distance_runtime_select`  picks the fastest of the above at runtime
}

Please advice on how to assist with these problems

Hi, You mention some valid concerns, along with some things that were intentional design decisions.

Not compiling with no_std is an oversight, I will attempt to fix it soon.
I haven't gotten around to porting sleef, it is a fairly weird library to include, but I know it needs to be done to maintain feature parity with the previous simdeez versions.
That was an intentional design decision. One of the main complaints I see for simdeez is that it's all unsafe, which is obviously caused by the fact that simdeez has no way of knowing whether individual operations are valid or not at runtime. My approach was to hide away any simd instruction set specific calls, and just allow:

Scalar (as it is always supported)
An general function that always picks the best instruction set, guaranteeing that the calls will be safe
Using simd_unsafe_generate_all to generate a list of unsafe functions for each instruction set

I made the structs associated with the instruction sets private, as I can't make using them directly safe, but at the same time I want to keep the API as safe as possible (without needing unsafe blocks literally everywhere).
Does simd_unsafe_generate_all fix the problem for you?

Oh also, the README example is outdated, please look at the examples folder for a functioning example. The sum function there just does basic SIMD addition from one vector into another, although modern CPUs can optimize that at runtime via pipelining just fine, so I also added a function there called simd_get_sum which does SIMD-based string parsing to parse all the numbers in the lists of characters and get the sum of them. Naturally, all of this needs more documentation, I just paused for a bit. I will look at it again soon though (today or next few days).

Ok I'm just looking at the no_std compile error, would you be familiar with how to do neon detection in no_std? It seems like it's possible to do x86 feature detection with no_std, but ARM doesn't seem to support it.

related to the feature detection, rust doc mentions:

Sorry, did you sent the above reply correctly? The code block seems empty

@arduano , I missed your comment about the missing code block.
I edited the codeblock now.

Yeah the main issue with sleef is that it's an external C library that's more difficult to integrate. I am open to PRs though, if you have the capacity

I took a look at SIMD feature detection and it seems that in theory the std_detect crate could be used in no_std environments - it's the same implementation that's behind std::arch. They state:

We intend to make std_detect more flexible and configurable in this regard to better serve the needs of #[no_std] targets.

But currently it's not there yet: it requires a nightly rustc, a Git dependency (current 1.5.0 release doesn't build with recent rustc) and the stdarch_internal feature has to be enabled in simdeez, which is "strongly discouraged".
Looking at the issue from another perspective: does it really make sense to support runtime SIMD feature detection in no_std environments? I think no_std projects are well aware of their actual target architectures, so they can just use compile time code generation. So I would rather disable runtime detection on no_std by default, and maybe make it available under a dedicated feature (implemented with std_detect).
If you agree, I'm happy to pursue this path and prepare a PR - and also take a look at the situation with sleef.

I believe no_std is mainly used in things like wasm, so it's probably ok to manually work around that (e.g. "no_std_wasm" feature flag)
Also there's zero reason to use nightly for simdeez, because simdeez purely exists to allow using simd features in stable. If you're using nightly, you might as well use the portable_simd feature, which does everything simdeez does but better


TLS between Ingress and activator

testing...

Codecov Report

Merging #29 (0256011) into main (ad15a85) will decrease coverage by 0.10%.
The diff coverage is 68.88%.

@@            Coverage Diff             @@
##             main      #29      +/-   ##
==========================================
- Coverage   87.51%   87.41%   -0.11%
==========================================
  Files         196      196
  Lines        9782     9811      +29
==========================================
+ Hits         8561     8576      +15
- Misses        933      945      +12
- Partials      288      290       +2

Impacted Files
Coverage Δ

cmd/activator/main.go
0.00% <0.00%> (ø)

pkg/reconciler/route/resources/ingress.go
91.20% <73.33%> (-1.94%)
:arrow_down:

...reconciler/serverlessservice/resources/services.go
97.97% <90.90%> (-2.03%)
:arrow_down:

pkg/autoscaler/statserver/server.go
77.66% <0.00%> (-1.95%)
:arrow_down:

pkg/reconciler/revision/background.go
91.81% <0.00%> (+1.81%)
:arrow_up:

Continue to review full report at Codecov.

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


python311Packages.ansible-compat: 4.1.11 -> 24.6.1

Description of changes
This update is needed for molecule and probably will be needed for ansible-lint soon.
https://github.com/ansible/ansible-compat/compare/v4.1.11...v24.6.1

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 317507 run on x86_64-linux 1

16 packages built:

ansible-lint
ansible-lint.dist
ansible-navigator (python311Packages.ansible-navigator)
ansible-navigator.dist (python311Packages.ansible-navigator.dist)
molecule (python311Packages.molecule)
molecule.dist (python311Packages.molecule.dist)
python311Packages.ansible-compat
python311Packages.ansible-compat.dist
python311Packages.pytest-ansible
python311Packages.pytest-ansible.dist
python312Packages.ansible-compat
python312Packages.ansible-compat.dist
python312Packages.molecule
python312Packages.molecule.dist
python312Packages.pytest-ansible
python312Packages.pytest-ansible.dist


annotating new videos

Thanks for posting a great demo!
Do you have any recommendations for annotation tools? I'm looking for a tool for annotating some of my videos.

Vatic is one example. But this is quite old, Im sure there are much better ones now.
https://github.com/cvondrick/vatic

Thanks, @oulutan!
I looked around the web, and found VoTT https://github.com/microsoft/VoTT#labeling-a-video looks useful for my application. VoTT only supports frame-by-frame annotations for videos, but it's works okay because actions that I'm interested have similar temporal length. I hope they can support temporal segment annotation properly though.


Example in README.md not compiling

Hi, thanks for putting together this library. I've tried the example below from the README.md
module Link = %styled.a(
  (~color="#4299E1") => `
  font-size: 1.875rem;
  line-height: 1.5;
  text-decoration: none;
  margin: 0px;
  padding: 10px 0px;
  color: $(color);
`)

and get the following compiler error:
This has type: string
  Somewhere wanted:
    [<
  | #currentColor
  | #hex(string)
  | #hsl(
      Css_AtomicTypes.Angle.t,
      Css_AtomicTypes.Percentage.t,
      Css_AtomicTypes.Percentage.t,
    )
  | #hsla(
      Css_AtomicTypes.Angle.t,
      Css_AtomicTypes.Percentage.t,
      Css_AtomicTypes.Percentage.t,
      [#num(float) | #percent(float)],
    )
  | #rgb(int, int, int)
  | #rgba(int, int, int, [#num(float) | #percent(float)])
  | #transparent
  | #var(string)
  | #varDefault(string, string)
]

The above error show regardless of me mounting the Link component.
Thanks

Hi, thanks for opening the issue!
This example points to an old version (0.21). Currently, bigger than 0.23 would require changing this snippet a bit. Treat the ~color prop as a bs-css color instead of a string.
This will be the equivalent
module Link = %styled.a(
  (~color=Css.hex("4299E1")) => `
  font-size: 1.875rem;
  line-height: 1.5;
  text-decoration: none;
  margin: 0px;
  padding: 10px 0px;
  color: $(color);
`)

Pushed the fix into the README so fewer users will be confused by this!
https://github.com/davesnx/styled-ppx/commit/89915116f103a2ff9e952f61178118fbe40edb92
I will close this for now, but feel free to ask any question :D

Thanks, really appreciated the quick response!


How to observe in Swift 5.9 with swiftui

I can't set the delegate in Swiftui.
Can you share a example on how to do it (my experience with swift is limit but I managed to get the VPN connecting/disconnect, etc.).
Thank you!

Hello Erwin1989!
You're right, this project is a bit outdated. But I'm not going to maintain this project now, maybe sometime in the future.
Sorry :(


[hotfix] Pin chart version to latest 2.4 release

Not sure if this is intended, but the release-2.x branches all install the latest version since the chart version is unpinned, which is a bit confusing imo. Pinning to a specific chart version fixes this, but introduces one more place to update. 🤷🏼 lmk

Huh. Somehow, I overlooked this PR completely. Sorry @austince ! I sure hope you will survive this betrayal of trust.

I will find it in my heart to forgive you @nicoweidner ❤


editable_test.dart not font-hermetic on web

This test is checking for specific size of the Chinese characters, but our ahem.ttf font doesn't have them (according to fontdrop.info). This causes the browser to fallback to a local font, which can be different from one computer to another.
This causes HHH to fail, for example:
https://logs.chromium.org/logs/dart/buildbucket/cr-buildbucket.appspot.com/8846622841805053712/+/u/flutter_test_web_tests/stdout
Somehow the C++ engine is immune to this problem. Perhaps it also falls back to some font, but that fallback font is stable across machines.

We should add ideographic sample glyphs to cough (https://github.com/flutter/engine/pull/13649) and change tests to depend on that instead of Ahem for ideographic scripts.

Not sure what fixed this, but I was able to turn the test marked with this bug in editable_test.dart with #87700. I will close this, if you feel it is still not properly addressed, please reopen.

Unfortunately this is still happening - the Dart/flutter HHH bot went red again once the test was reenabled in https://github.com/flutter/flutter/commit/225a43d941ddd1753765fec3682011e9ddffb11d
See https://ci.chromium.org/ui/p/dart/builders/ci.sandbox/flutter-engine-linux-web_tests/3108/overview
I believe this is hard to repro because many of our local setups have fallback fonts that would work OK.
Maybe there is a way we can force these processes to not look for an alternative font? Could we use an approach, like using FONTCONFIG_PATH or FONTCONFIG_FILE, to ensure we can repro more easily locally?

Somehow the C++ engine is immune to this problem.

Looks like font fallback is disabled in test mode so those characters are always tofu:
https://github.com/flutter/engine/blob/34794638c8b88ea9cabde44e587ece6d0dc56757/lib/ui/text/font_collection.cc#L143
https://github.com/flutter/engine/pull/4661
Looking at the original issue that for this test, it doesn't seem to have to do with the script or the baseline positions? It's just in those fonts the Chinese characters are generally taller than the 0x20 whitespace char we used to use to measure the line height? If that's the case using Ahem defeats the purpose of the test.

Ah nvm SkParagraph reports font metrics instead of glyph metrics for height. So it looks like the original issue is caused by different typefaces being used.


TypeError: headers.getSetCookie is not a function

Hi! I'm testing the new Single Fetch behaviour in Remix, but I'm having trouble with headers.getSetCookie which seemingly isn't present when running on Vercel for some reason.
As noted in the changelog, I've enabled nativeFetch in installGlobals but the TypeError is still present. The error I get is this:
TypeError: headers.getSetCookie is not a function or its return value is not iterable
    at proxyResponseToResponseStub (/var/task/node_modules/.pnpm/@remix-run+server-runtime@2.9.1_typescript@5.4.5/node_modules/@remix-run/server-runtime/dist/single-fetch.js:292:25)
    at /var/task/node_modules/.pnpm/@remix-run+server-runtime@2.9.1_typescript@5.4.5/node_modules/@remix-run/server-runtime/dist/single-fetch.js:61:9
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Promise.all (index 1)
    at async /var/task/node_modules/.pnpm/@remix-run+server-runtime@2.9.1_typescript@5.4.5/node_modules/@remix-run/server-runtime/dist/single-fetch.js:39:19
    at async callDataStrategyImpl (/var/task/node_modules/.pnpm/@remix-run+router@1.16.0/node_modules/@remix-run/router/dist/router.cjs.js:4169:17)
    at async callDataStrategy (/var/task/node_modules/.pnpm/@remix-run+router@1.16.0/node_modules/@remix-run/router/dist/router.cjs.js:3702:19)
    at async loadRouteData (/var/task/node_modules/.pnpm/@remix-run+router@1.16.0/node_modules/@remix-run/router/dist/router.cjs.js:3677:19)
    at async queryImpl (/var/task/node_modules/.pnpm/@remix-run+router@1.16.0/node_modules/@remix-run/router/dist/router.cjs.js:3522:20)
    at async Object.query (/var/task/node_modules/.pnpm/@remix-run+router@1.16.0/node_modules/@remix-run/router/dist/router.cjs.js:3416:18)

To reproduce, simply create a new Remix-project with npx create-remix@latest and put this in the _index.tsx-file:
export const loader = () => {
  return new Response(null, {
    headers: { "set-cookie": "_cookie_name=123; maxAge=1000000; SameSite=Lax" },
  });
};

export default function Index() {
  return
Welcome to Remix
;
}

`vite.config.ts`
import { vitePlugin as remix } from "@remix-run/dev";
import { installGlobals } from "@remix-run/node";
import { defineConfig } from "vite";
import tsconfigPaths from "vite-tsconfig-paths";
import { vercelPreset } from '@vercel/remix/vite';

installGlobals({ nativeFetch: true });

export default defineConfig({
  plugins: [
    remix({
      presets: [vercelPreset()],
      future: {
        unstable_singleFetch: true
      }
    }),
    tsconfigPaths(),
  ],
});

Then deploy to vercel.

Even without the new SingleFetch behaviour, using headers.getSetCookie still doesn't work. This can be reproduced by removing unstable_singleFetch from future in vite.config.ts, and changing the _index.tsx-file to this:
export const loader = () => {
  const res = new Response(null, {
    headers: { "set-cookie": "_cookie_name=123; maxAge=1000000; SameSite=Lax" },
  });
  console.log("getSetCookie", res.headers.getSetCookie); // -> getSetCookie  undefined
  console.log("getSetCookie values", res.headers.getSetCookie()); // -> TypeError: response.headers.getSetCookie is not a function
  return res;
};

export default function Index() {
  return
Welcome to Remix
;
}

Any help appreciated!

I am having the same problem. It also occurs with loaders that only return json({}).
It is also reported in the issue of remix-run
https://github.com/remix-run/remix/issues/9324
Perhaps I should try to use nativeFetch, but since it is vercelPreset and not a custom server, I don't know what to do.

I'm getting this error too. I tried to use node 20 if it solves the issue, but it's the same.
The server is not accessible (Just blank screen).
Mine is just a local dev environment.
I tried to dig deeper a little bit and there I see this line: https://github.com/remix-run/remix/blob/7b2fa032cd465c7f6e9c8d90471d6a544e0c08f6/packages/remix-server-runtime/single-fetch.ts#L350
Even the comments themselves acknowledge the presence of certain typing issues.
I want to contribute to solve this issue, but i'm not a yet great JS dev myself 😅 .

It would be nice to be able to control it externally somehow so that the following part called after invoking serverless functions becomes installGlobals({ nativeFetch: true }), but I wonder how to do that.
https://github.com/vercel/remix/blob/9a168473a813e42ab2dc8ae7f21a58a760b712da/packages/vercel-remix/globals.ts#L2

export const loader = () => {
  const res = new Response(null, {
    headers: { "set-cookie": "_cookie_name=123; maxAge=1000000; SameSite=Lax" },
  });
  console.log("getSetCookie", res.headers.getSetCookie); // -> getSetCookie  undefined
  console.log("getSetCookie values", res.headers.getSetCookie()); // -> TypeError: response.headers.getSetCookie is not a function
  return res;
};

export default function Index() {
  return
Welcome to Remix
;
}

I get the same error in development with remix vite:dev, unstable_singleFetch: true, "@remix-run/dev": "^2.9.1", Node 20.12.2. No custom server, only vite.

So I've solved this by using Object.defineProperty to set the globals and prevent changes to them, and by monkey-patching in an API that @ercel/remix relies on but isn't available in Headers when using nativeFetch.
Here's the gist https://gist.github.com/michalmo/d62e9a2e001183ec1df1bcac74980abb.
I call the installAndLockGlobals helper at the top level of app/entry.server.tsx (https://vercel.com/docs/frameworks/remix#using-a-custom-app/entry.server-file).
Hope this helps somebody :)

So I've found a workaround using Object.defineProperty to set the globals and prevent changes to them, and by monkey-patching in an API that @ercel/remix relies on but isn't available in Headers when using nativeFetch.
Here's the gist https://gist.github.com/michalmo/d62e9a2e001183ec1df1bcac74980abb.
I call the installAndLockGlobals helper at the top level of app/entry.server.tsx (https://vercel.com/docs/frameworks/remix#using-a-custom-app/entry.server-file).
Hope this helps somebody :)

Thank you sooo much!! You saved me a couple of headaches

@brophdawg11 Do you have an update regarding these or how can we help? Seems that this is an issue on the Vercel Side of things since locally is running ok

If Vercel needs a polyfill and doesn't have a fetch implementation, they will need to let you call installGlobals({ nativeFetch: true }) to get a single-fetch compatible polyfill (see https://github.com/vercel/remix/issues/109#issuecomment-2081349578).  I'm going to close this out on our end though since it's not a Remix issue.

Although the installGlobals({ nativeFetch: true }) fix solves this, I'm unable to use fetcher.submit from Remix, getting the error:
TypeError: RequestInit: duplex option is required when sending a body.
    at new Request (/var/task/website/node_modules/undici/lib/web/fetch/request.js:537:15)
    at createRemixRequest (file:///var/task/website/build/server/nodejs-eyJydW50aW1lIjoibm9kZWpzIn0/server-index.mjs:61:10)
    at Server.default (file:///var/task/website/build/server/nodejs-eyJydW50aW1lIjoibm9kZWpzIn0/server-index.mjs:80:19)


Expose the serializer on the localForage object/namespace

This is to gather the discussion that appeared in #412 & #432 (@tofumatt, @af7 )
My two suggestions:

localforage.serializer returning the actual serializer object
localforage.getSerializer() returning a promise

localforage.serializer returning the actual serializer object
Pros:

use es6 static imports

Cons:

load the serializer even in cases that it's not needed (eg: IndexedDB with unbundled RequireJS, do we even support it any more?)

This will make even more sense if we move the IndexedDB driver's blob serialization code into the main serializer.
Sample implementation:
// on the top of localforage.js, ouside the IIFE
import serializer from 'utils/serializer'

// near the end of localforage.js inside the IIFE
localForage.serializer = serializer;
export default localForage;

localforage.getSerializer() returning a promise
Pros:

We don't import anything if not really required/requested
That's the way the drivers are currently implemented and we could refactor them to use the exposed method, instead of doing a System.import in their own

Cons:

The developer will have to wait for a promise to resolve

// add a method to the LocalForage class
getSerializer() {
  return System.import('./utils/serializer');
}

I think waiting for the promise to resolve is okay, and is very much like the rest of our other APIs. I'm for that one. I'm not sure when we would need to load a serialiser async but it does let us do that as well.

tofumatt

On Tue, Sep 8, 2015 at 7:44 AM, Thodoris Greasidis
<EMAIL_ADDRESS>wrote:

This is to gather the discussion that appeared in #412 & #432 (@tofumatt, @af7 )
My two suggestions:

localforage.serializer returning the actual serializer object
localforage.getSerializer() returning a promise

localforage.serializer returning the actual serializer object
Pros:

use es6 static imports
Cons:
load the serializer even in cases that it's not needed (eg: IndexedDB with unbundled RequireJS, do we even support it any more?)
This will make even more sense if we move the IndexedDB driver's blob serialization code into the main serializer.
Sample implementation:

// on the top of localforage.js, ouside the IIFE
import serializer from 'utils/serializer'
// near the end of localforage.js inside the IIFE
localForage.serializer = serializer;
export default localForage;

localforage.getSerializer() returning a promise
Pros:

We don't import anything if not really required/requested
That's the way the drivers are currently implemented and we could refactor them to use the exposed method, instead of doing a System.import in their own
Cons:
The developer will have to wait for a promise to resolve

// add a method to the LocalForage class
getSerializer() {
  return System.import('./utils/serializer');
}

Reply to this email directly or view it on GitHub:
https://github.com/mozilla/localForage/issues/446

+1


Master

Added support for nesting helpers on embedded documents.
see tests for examples.

The nested properties are not attached to the prototype, wouldn't that be a problem?

Hey @stfnbrgh thanks for the pull request, I don't think I'll merge however for a couple of reasons.
I feel that collection-helpers power lies in its simplicity, whereas the features added in this PR are more suited to more complex projects, it just adds an unnecessary layer therefore I feel that adding further complexity to cover the 10% doesn't feel correct to me.

It doesn't seem like you will be able to get at the top-level fields from a nested collection helper.

@dburles - No problem, I will consider a package once it has matured a bit.
@rclai - Good point, will look into it!

@dburles Please reconsider merging the pull-rerquest (or perhaps asking for a simplified functionality), IMO having many similar packages on atmosphere would irritate the users...

@boustanihani my hesitation to merge is that I've never had a strong requirement for this feature in all of the apps that I have developed since I first created and began using collection-helpers, so I believe it's not the right decision.
However, it's not to say that there aren't projects out there that would benefit from nested helpers, so in that case it seems ideal to me if it could be provided as an "add-on" package for collection-helpers, it would be nice if nested-collection-helpers could depend on collection-helpers and simply add the extra functionality.
What are your thoughts on this @stfnbrgh?

@dburles I don't know. Because collection-helpers is so simple, wouldn't it be easier to develop it as a replacement for people who require the added complexity. Then they can use either collection-helpers or collection-nested-helpers.
I'm not sure how I would extend collection-helpers as-is in an efficient way? I no JavaScript guru though so maybe you have some ideas?
Maybe we could we add extension points to collection-helpers? I'm thinking a chain of key handlers on register that handles the different key's and a handler on attach that has access to the data from register step?
example:
"simple" -> add to prototype
"or.nested" -> handle nested
"or.$.array" -> handle nested with arrays
Other packages can the register their handler pairs with collection-helpers?
This will add to complexity to collection-helpers though.

I vote to keep the code simpler. Why don't think in some scheme of extensions? Like other plugins does.
So if someone need nested functionality he'll add the nested-collections-helpers extension to this one. etc..


Add support for fortanixvme target

#1 was already approved. This is basically the same PR. Changing a commit would have broken other crates, so I created a new branch and new PR to merge things.


Allow to call sync_schedule

I'd like to edit the schedule data, but I'm missing the SyncSchedule method in the library. Do you plan to implement it?
From my point of view, just JSON/YAML in the format the netatmo API accepts is flexible enough.

Currently I don't have that scheduled, but I'll happily review a PR.

I created a PR for modifying the temperatures of a schedule. It also includes a generic method to edit the schedule data.


Gzip encoded data

Ok so I was getting:
---deISzRSW---B--
GET /wp-content/uploads/2012/03/satan%E2%80%99s-malicious-agenda-300x200.jpg HTTP/1.1
Content-Length: 0
X-Forwarded-For: <IP_ADDRESS>
CF-IPCountry: FR
Host: www.danielsblog.org
CF-Origin-IP: <IP_ADDRESS>
Accept-Encoding: gzip
X-Forwarded-Proto: https
CF-Origin-Https: on
User-Agent: Toweya.com bot; report abuse to<EMAIL_ADDRESS>Connection: Keep-Alive
CF-RAY: 3734527bd93168f6-CDG
Accept: /
CF-Visitor: {"scheme":"https"}
(binary data here)
After reading through docs I find the directive I need:
SecDisableBackendCompression On
.....but it don't work....Nginx won't start with it in my modsecurity.conf file:
2017/06/23 03:52:08 [emerg] 5146#5146: "modsecurity_rules_file" directive Rules error. File: /etc/nginx/snippets/modsecurity.conf. Line: 9. Column: 32. Invalid input:  SecDisableBackendCompression On in /etc/nginx/conf.d/allcapa.org.conf:21

I disabled mod_deflate on my backend server and still getting binary data and header of
GET /wp-content/uploads/2012/03/satan%E2%80%99s-malicious-agenda-300x200.jpg HTTP/1.1
Content-Length: 0
X-Forwarded-For: <IP_ADDRESS>
CF-IPCountry: FR
Host: www.danielsblog.org
CF-Origin-IP: <IP_ADDRESS>
Accept-Encoding: gzip
X-Forwarded-Proto: https
CF-Origin-Https: on
User-Agent: Toweya.com bot; report abuse to<EMAIL_ADDRESS>Connection: Keep-Alive
CF-RAY: 3734a9cf5d7869be-CDG
Accept: /
CF-Visitor: {"scheme":"https"}
CF-WAN-ID: rg-72eb7a9df15c775786489ce7b862c78f.port2408.net:2408
CF-Connecting-IP: <IP_ADDRESS>
just cant figure out 1. where its getting zipped, and 2. why I cant turn it off with the directive.

Hi @nullmem,
I'm guessing you are using the nginx-connector with libModSecurity (aka v3), right?
If that's so, I'm afraid SecDisableBackendCompression is currently a missing feature for libModSecurity. I'll create an issue on ModSecurity Github for proper tracking of this missing feature.

Yes, and thank you. as a temporary workaround, I was able to disable gzip on both Nginx and my backend server. This isn't really a big deal because this server is behind CloudFlare and they gzip everything anyway.

Thanks for the feedback @nullmem, good to know you have a workaround :)
I've updated the reference manual to reflect the current missing feature and created an issue on ModSecurity's Github for proper tracking: https://github.com/SpiderLabs/ModSecurity/issues/1470
So I will close this one here.
Thanks!


[curl] x64 build fails with ninja error

When building [curl]:x64-windows-static, the build fails.  Building [curl]:x86-windows-static is OK.
Content of "C:\src\vcpkg\buildtrees\curl\install-x64-windows-static-dbg-err.log":
ninja: fatal: CreateProcess: The parameter is incorrect.
Screen output:
-- Configuring x64-windows-static done
-- Build x64-windows-static-dbg
CMake Error at scripts/cmake/vcpkg_build_cmake.cmake:136 (message):
Command failed: C:/Program Files/CMake/bin/cmake.exe;--build;.;--config;Debug;--target;install;--;-v;-j1
Working Directory: C:/src/vcpkg/buildtrees/curl/x64-windows-static-dbg
See logs for more information:
C:\src\vcpkg\buildtrees\curl\install-x64-windows-static-dbg-out.log
C:\src\vcpkg\buildtrees\curl\install-x64-windows-static-dbg-err.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_install_cmake.cmake:24 (vcpkg_build_cmake)
ports/curl/portfile.cmake:96 (vcpkg_install_cmake)
scripts/ports.cmake:72 (include)

Duplicated with #1797  ?

This seems to be fixed by CMake 3.11.1.


[TextField] OutlinedInput does not pass "style" props to NotchedOutline

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
I want to change the style of the "fieldset" of the NotchedOutline component but OutlinedInput does not pass that props:

Expected behavior 🤔
Be able to pass style props from OutlinedInput to NotchedOutline.
Steps to reproduce 🕹
No response
Context 🔦
No response
Your environment 🌎

`npx @mui/envinfo`
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

We too are running into this problem.
In order to apply the styles, we're having to target the generated classnames explicitly, rather than the object keys like we're doing for the rest of the styles.
We're currently using v4 and are looking to upgrade to v5 in the future, but an update to this (or a different workaround) would be fantastic.


Vulnerability roundup 102: jenkins-2.277.4: 2 advisories [4.3]

search, files

[ ] CVE-2021-21639 CVSSv3=4.3 (nixos-unstable)
[ ] CVE-2021-21640 CVSSv3=4.3 (nixos-unstable)

Scanned versions: nixos-unstable: ea7d4aa9b82.
Cc @coreyoconnor
Cc @earldouglas
Cc @fpletz
Cc @nequissimus

Already fixed in LTS 2.277.2+


fix, two alleles with the same name

I found this in the comments log file, but I don't thin it appears in the logs, check?
alp7-5A(S50A,S51A,T100A,T116A,T131A)	warning: same name as alp7-5A(K341,Y344,R346,K347,Y348)	PMID:29021344
alp7-5A(K341,Y344,R346,K347,Y348)	warning: same name as alp7-5A(S50A, S51A, T100A, T116A, T131A)	PMID:24790093

I can't see this in the logs, it isn't in the expected  file:
https://curation.pombase.org/dumps/latest_build/logs/log.2024-01-01-21-44-33.chado_checks.duplicated_allele_names
I won't fix it until the logs are reporting the error (no hurry)

alp7-5A(S50A,S51A,T100A,T116A,T131A) warning: same name as alp7-5A(K341,Y344,R346,K347,Y348) PMID:29021344
alp7-5A(K341,Y344,R346,K347,Y348) warning: same name as alp7-5A(S50A, S51A, T100A, T116A, T131A) PMID:24790093

Hi Val.  I can't see that message in the logs now.
The allele comments load log has this message which might be related:

can't find feature with name "alp7-5A(K341,Y344,R346,K347,Y348)" at line 81 - skipping

https://curation.pombase.org/dumps/builds/pombase-build-2024-01-02/logs/log.2024-01-01-21-44-33.allele-comments-from-supporting-data

I can't figure out why this wouldn't cause an error to appear in
https://curation.pombase.org/dumps/latest_build/logs/log.2024-01-01-21-44-33.chado_checks.duplicated_allele_names
though.
It's a duplicated allele name?

It's a duplicated allele name?

They have different names.  One is "alp7-5A(S50A,S51A,T100A,T116A,T131A)" and the other is "alp7-5A(K341,Y344,R346,K347,Y348)" in the allele_comments.txt file.  The first column is the allele name, not the allele name + description.
http://dev.pombase.kmr.nz/allele/SPAC890.02c:allele-24
http://dev.pombase.kmr.nz/allele/SPAC890.02c:allele-6

Val to fix


Lua.workspace.library path with username

Instead of: C://Users//Admin//AppData//Roaming//etc
I want to do:
%APPDATA%//etc
is there a way to do that for Lua.workspace.library?

$APPDATA/etc

thanks this works


Doesn't work at all for me

Hey! I didn't know where to ask, so I hope it's okay, that I reach out this way. I downloaded your plugin today to use it for my studies, but I can't get it to work. I tried all the commands in the documentation and wrote some myself with my own prompts but nothing seems to do what it's supposed to do. The Plugin is installed and enabled. Does it maybe have an issue with other languages?
This is what I did:

In Nachkriegszeit und 1950 wesentliche Beiträge zur Entstehung der Teildisziplin.
Begriff Organisationspsychologie erst 1960 etabliert.

style=2
[query.from-1950-to-1960]
start="1950"
end="1960"

Thank you in advance for your help.

Sorry for the inconvenience, I will improve it later.
This plugin by default works with only English. I will add functionality for switching between languages. However, I am unsure if this plugin in Deutsch can achieve the same usefulness. anyway I will try, thank you for the report

I know that probably is out of the scope for your plugin but for other languages, do you consider the possibilities to use inline tags?
I’m thinking about a list of tags that your plugin could identifies reporting to the “standard” English.
I’m not a English native speaker so if you want to use your plugin (that seems very nice) I should put an English sentence in my note just to enable it.

I know that probably is out of the scope for your plugin but for other languages, do you consider the possibilities to use inline tags?
I’m thinking about a list of tags that your plugin could identifies reporting to the “standard” English.
I’m not an English native speaker so if you want to use your plugin (that seems very nice) I should put an English sentence in my note just to enable it.

Thank you for giving me suggestions. Can you explain a bit clearer about what you want? Maybe give me examples. I still not understand what you mean about inline tag.

I was thinking about adding a #tag into the document to add a time context putting the same info but in a different way that clarifies it is not text. For instance #now, #twohoursago or a specific date #2023-02-31.
I don't know if it could be feasible.
As an example I could write a block of text and after putting a tag to clarifies when it happened.
La bomba non attesa di toccare terra per esplodere. #1945-08-06

@Azmoinal thank you, I will try to implement your idea.
This plugin will try to split the markdown content to sentences before doing extracting time. That is why in the example Martin era morto ma non era la brutta notizia. #1960-08-06_21:23. Which using 2 sentences, split by a dot, is not fit for the system now.
About your idea, I understand that you want to make the smallest atoms be a group of sentences (paragraphs) instead of just one sentence. And give the user a choice to explicitly choose the time to plot if there is none/multi-time in that group of sentences.
Maybe I will try to add some function that uses hidden HTML tags to define a group of sentences that account as paragraphs. For example:

<historica-block style={hidden:true} id=${block-id}>
${multi sentences go here}
</historica-block>

```historica
block_id=${block-id}
time_to_render=${time_here}

The idea of that plugin from the start is to make things simple and effortless as much as possible. Because there are some timeline plugins that use complicated ways to plot timelines before.

So many change in new versions that this issues become outdate. And I didn't receive any answer from this kute boy


[BUG]: tried to load a PDF book of size 383MB. It worked fine in an i7 Windows (16GB RAM), but it failed to embed the doc in Mac i7 (intel mac) 16GB RAM

How are you running AnythingLLM?
Docker (local)
What happened?
in the mac (16GB RAM, i7 processor with 4 core), I am able to load the pdf doc (383MB size), I moved it to the workspace. when I clicked embed and save, it takes 5 to 6 mins, then throws the message below:
[1 doc failed to load
cannot embed doc]
I think it has nothing to do with the embed model and the LLM. I chose nomic-1.5 as embedding model. Both these models are served by ollama server which was running.
I used LM Studio in windows, but there is no Intel Mac version of LM studio, hence chose ollama for Intel MAC
Are there known steps to reproduce?
adding a 383MB size PDF - for chatting with pdf locally - embed and save throwing error - in a i7 intel based MAC with 16GB RAM, using Nomic-1.5 embedding model served by ollama from the same mac instance.

In this particular circumstance I think that the ollama process is running out of memory processing all the document chunks at once - resulting in too many concurrent chunks. What do the ollama logs say? It should be exiting with some kind of OOM memory error.
Also, I have a similar setup (windows comp with GPU and Intel Mac) and all i do is run ngrok http 1234 after starting the windows LMStudio server, and then use that URL in my Intel Mac LMStudio integration in AnythingLLM and you get the best of both worlds.


Expose getOrientation api publically

Fixes issue #26

Great, thank for the help
This week end I will make a full review on the current issue and publish everything to npm


Add support for custom AgentExecutor

In more advanced agents use cases, you often want to have greater control of the loop that controls how agents act.
The langchain AgentExecutor class has a method _take_next_step which is encouraged to be overridden in order to "(...) take control of how the agent makes and acts on choices." (https://github.com/hwchase17/langchain/blob/master/langchain/agents/agent.py#L748)
Trying to do so in conjunction with the newly added agent streaming support raises:
"Error! Chain type 'CustomAgentExecutor' is not currently supported by 'AsyncStreamingResponseCallback'."
To reproduce the error you can run examples/app/zero_shot_agent.py and replace the zero_shot_agent_dependency with a modified version of the function. This function creates a dummy custom subclass of AgentExecutor and initializes it manually rather than using the initialize_agent helper function as it currently does not support custom agent executors.
def zero_shot_agent_dependency() -> Callable[[], AgentExecutor]:
    @lru_cache(maxsize=1)
    def dependency() -> AgentExecutor:
        llm = ChatOpenAI(
            temperature=0,
            streaming=True,
        )
        tools = load_tools(["llm-math"], llm=llm)
        # Additional imports
        from langchain.agents import AgentExecutor
        from langchain.agents.loading import AGENT_TO_CLASS
        # Create dummy custom agent executor
        class CustomAgentExecutor(AgentExecutor):
            pass
        # Initialize agent without initialize_agent helper function
        agent = AgentType.ZERO_SHOT_REACT_DESCRIPTION
        agent_cls = AGENT_TO_CLASS[agent]
        agent_obj = agent_cls.from_llm_and_tools(llm, tools)
        agent = CustomAgentExecutor.from_agent_and_tools(
            agent=agent_obj,
            tools=tools,
            )
        return agent

    return dependency

Acceptance Criteria

[ ] Running a subclass of AgentExecutor no longer raises an error

Hi! I need to update the error message here but you can already solve this by registering a custom callback handler. You can find the docs for it here: https://lanarky.readthedocs.io/en/latest/advanced/custom_callbacks.html

@ajndkr thanks this works if I import register_streaming_callback instead of register_callback as shown in the docs as that raises an error.
Keeping the ticket open in the meantime but feel free to close it when you want.

you're right! i will update the docs.


Create spelling workflow

I take care of your fat fingers and ESL mistakes.

This is essential for all projects involving text.

Yeah I make typos occasionally but to be honest it doesn't bother me enough to introduce a third party dependency that I need to maintain. I'm happy correcting them as they get spotted.


__hgt2 fix, env vars to individually disable fusion ops, MNIST testcase fix

PR Contents:
workaround for the issue where __hgt2 returns -1 (instead of 1) for true

ROCm Fusion Pass updates

change the pass to traverse the TF graph individually for each fusion

add env vars to disable fusions on an individual basis (to help with debug / perf measurements)
By default, ROCm FUSION is turned OFF

Setting the env var TF_ROCM_FUSION_ENABLE (to any value) turns ALL the fusion ops ON

When the env var TF_ROCM_FUSION_ENABLE is set

set TF_ROCM_FUSION_DISABLE_<type> to disable <type> fusion, where  can be

CBA : Conv+Bias+Actv
BNA : BatchNorm+Actv
ADDRELU : Add+Relu
ADDNRELUGRAD - AddN+ReluGrad

AddRelu Kernel implementation updates

added to check to error out when assumptions regarding the shape of the input tensors are not correct

added a simple "broadcast" version of the AddRelu Kernel to make the models/image/tutorial/mnist testcase work correctly
the mnist testcase was giving incorrect results because the "Add" operation requires broadcasting.
the "Add" operation in the resenet50 model is element-wise (i.e. does not require any broadcast) so this change does not affect it all.

@deven-amd , do I need to pick this PR to r1.11-rocm-fusion branch?

@deven-amd , do I need to pick this PR to r1.11-rocm-fusion branch?

You do not need to. No functional / performance changes that will affect resnet50.
On the flip side, one of the commits will allow you to disable individual fusions. It might help you with doing performance measurements with selective fusions turned on/off, in case you need to do something like that.


confirm UnicodeDecodeError

click.confirm() sometimes may raise UnicodeDecodeError on visible_prompt_func call
Several terminals control input stdin in different ways. Most of them are linux compatible and work fine, but some not.
E.G. PyCharm default integrated terminal with default terminal settings (inherited from user .*rc) may cause UnicodeDecodeError on several inputs.
Exact way to reproduce:

Run click app with click.confirm() or click.prompt() calls in PyCharm integrated terminal
Start typing
Backspace some symbols
Press enter

Stacktrace:
Continue? [y/N]: N
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.10/bin/app", line 8, in <module>
    sys.exit(cli())
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/click/core.py", line 1654, in invoke
    super().invoke(ctx)
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/click/decorators.py", line 26, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/click/decorators.py", line 84, in new_func
    return ctx.invoke(f, obj, *args, **kwargs)
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/app/app.py", line 45, in handle
    click.confirm(f'Continue?', abort=True)
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/click/termui.py", line 235, in confirm
    value = visible_prompt_func(" ").lower().strip()
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xd0 in position 0: invalid continuation byte

Expected behaviour:
UnicodeDecodeError is handled with user notification
Seems that except (KeyboardInterrupt, EOFError) is not enough for click.confirm func
Environment:

Python version: 3.10
Click version: 8.1.2
OS: macOS Monterey 12.6
PyCharm 2022.2 Pro
Shell: zsh 5.8.1

This sounds like a bug that should be reported to PyCharm.


test/e2e: add the template of the test for mirroring

We're currently working on mirroring feature. To develop this feature, we need multiple K8s clusters for testing.
This PR makes it easier to deploy multiple K8s clusters for testing purposes. Each K8s cluster has its own Rook/Ceph setup and is connected to the same network, allowing them to communicate with each other.
We've also added a new GHA workflow to test the multiple K8s clusters. At the moment, we don't have a comprehensive test suite that uses the multiple clusters. Instead, we deploy an Nginx server on one cluster and use curl from another cluster to query the server, ensuring that the clusters are functioning correctly.

First I left some comments about the title and the descriptions of this PR.

test/e2e: add tests using multiple k8s clusters #30

It's more appropriate to rename "test/e2e: add the template of  the test for mirroring"

We're currently working on mirroring MantleBackup and other objects from one K8s cluster to another.

"We're currently working on mirroring feature" is precise and simpler description. For instance, k8s resources in the primary k8s cluster are not mirrored to the secondary k8s cluster as is. Most annotations and labels will be removed.
I'll continue to review this PR since these comments doesn't correspond to the code diff. Please update the title, descriptions, and the commit logs at your convenience.

Thank you for your feedback. I updated this PR's title and description. I updated the commit message, too.

Thank you for merging this PR!


BUG - Incorrect LinkedIn Campaign Hierarchy

Are you a current Fivetran customer?
Andrew Woelfel, Analyst, Xometry
Describe the bug
Below should be the adjusted query for LinkedIn Campaigns query.  Campaign groups can have multiple campaigns, so to match the aggregation of across other platforms, this should be switched.  Below is documentation from LinkedIn noting this is the hierarchy.  In the current state when used for reporting this hierarchy doesn't make any sense when multiple platforms are shown and causes confusion.
https://docs.microsoft.com/en-us/linkedin/marketing/integrations/ads/account-structure/create-and-manage-campaign-groups?tabs=http
    select         'LinkedIn Ads' as platform,         cast(date_day as date) as date_day,         account_name,         account_id,         campaign_group_name as campaign_name,         cast(campaign_group_id as {{ dbt_utils.type_string() }}) as campaign_id,  ---Campaign Group can contain multiple campaigns         campaign_name as ad_group_name,         cast(campaign_id as {{ dbt_utils.type_string() }}) as ad_group_id,         base_url,         url_host,         url_path,         utm_source,         utm_medium,         utm_campaign,         utm_content,         utm_term,         coalesce(clicks, 0) as clicks,         coalesce(impressions, 0) as impressions,         coalesce(cost, 0) as spend     from base
Steps to reproduce
Adjust stg_linkedin_ads.sql fields CTE to the above query
Expected behavior
Switching campaign group and campaign will show correct hierarchy when comparing across every platform
Please indicate the level of urgency
Yes, this is blocking a release of a looker dashboard
Are you interested in contributing to this package?

[ X] Yes, I can do this and open a PR for your review.  YES

Hi @andrew-woelfel thanks so much for opening this issue!
Would you be able to let me know which other platforms you are using within the ad_reporting package? I am able to see based off the Microsoft documentation and in our own data that campaign groups may contain multiple campaigns. I have also checked a few of the other platforms and notice that the behavior of multiple campaigns may apply to a single group as well.
I wonder if the hierarchy is off for a different platform instead? I want to make sure we end up making the appropriate change to the relevant model. Especially since this proposed change flip the fields.

We use adwords, facebook, linkedIn and bing.  Typically in my experience this is the hierarchy tree: Campaign > Ad Group > Ad > Creative.

AdWords/Bing use this same naming for API columns
Facebook is Campaign > Ad Set > Ad > Creative
LinkedIn, using our internal data, it is Campaign Group > Campaign > Creative (not aware if there is something between campaign and creative)

I have confirmed with our data, AdWords/Bing/Facebook query setup is correct using this model.  I noticed this because we have internal naming conventions and these are only flipped for the LinkedIn data with this model, below is the output.
Campaign: PB:L|AN:|GN:|CN:
AdGroup: PB:L|AN:|GN:
It should be reserved from what I am seeing

@andrew-woelfel thank so much for this additional context. After diving into this within our own Bing, Adwords, and LinkedIn data I found exactly what you noted.

Bing: A single campaign will contain multiple ad groups
Adwords: A single campaign will contain multiple ad groups
LinkedIn: A single camapgain_group will contain multiple campaigns.

With this additional context I completely understand how this is causing confusion and should be addressed within the ad_reporting package. I want to do some additional testing to confirm the hierarchy for the other platforms we have not mentioned.
Since you noted that you would be open to contributing, and it looks like you have the code on hand, would you be interested in opening a PR with your proposed changes? Our team can then look further into the other platforms and integrate your changes along with any others that may need to be applied.
Thanks!

Great, I'd be glad to create a PR if I get access to do so

You can actually fork this repo, make changes, and then open a PR against this repo's master branch without having access. Once our team reviews/approves the PR it will be good to merge!

Great, PR created: https://github.com/fivetran/dbt_ad_reporting/pull/22

@andrew-woelfel I just release v0.4.0 of the ad_reporting package which incorporates your change. This should be live at the top of the hour. Thanks again for your contribution!!


Unicode text characters in math mode

#992 added support for e.g. é in both math and text mode, mapping to \acute{e} and \'e respectively.   This felt natural to me... but I haven't been able to reproduce this behavior (specifically, the math-mode behavior) in LaTeX.  I'm compiling the following with xelatex, and only the text line is rendering:
\documentclass{article}
\usepackage{amsmath}
\usepackage{unicode-math}
\setmathfont{xits-math.otf}
\usepackage{xeCJK}
\begin{document}
é私はバナナです。

$é私はバナナです。$
\end{document}

I may be missing some packages though.  If this is really the state of XeLaTeX, should we remove support in KaTeX?  Alternatively, we could try to add support via the mythical katex.sty.
Related, I am wondering whether to add support for CJK in math mode, but rendering as text symbols.  This is how \ae works in LaTeX (with a warning), but doesn't seem to be how it works with CJK...

https://tex.stackexchange.com/questions/270154/utf-8-characters-in-math-mode describes a way to allow unicode chars in math mode, but it's definitely non-standard.


”Cosoba” is listed in the drop-down menu

Description:
"Cosoba" is listed in the drop-down menu alongside its corresponding county and commune, according to the law.
Precondition:
The website is up an running.

Step 1
Type "Cosoba" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Cosoba, GIURGIU".


actions-mn/cli#6 add documentation for actions-mn

actions-mn/cli#6

@ronaldtse if there is no objections I propose to merge this one

@CAMOBAP Ronald likely already told you this, but he has not merged anything since November, because he has been working on refactoring it ever since. Therefore, no PRs here have been merged.
@ronaldtse swore to me 10 days ago that he would get this done some time this month.
Month is almost up.

@opoudjis who can I ask for review this, or it's ok to merge on my own?

@opoudjis who can I ask for review this, or it's ok to merge on my own?

It is emphatically not OK to merge on your own, because Ronald has an open refactor. (As he has had for the past 10 months.)
The reviewer on metanoma.org is only Ronald. Until anyone says otherwise, you must never merge metanorma.org updates on your own.
Yes. I know.

@CAMOBAP Given the continuing inaction from @ronaldtse I am unilaterally merging this pending PR into doc20230606, which has been my working PR since June.


Module Mismatch expected 14 got 46

Hey, I'm using robotjs on a Windows 2008 Server to automate something. It is working on the staging server but when I move it over to the production server I get this error.. I'm pretty sure I did everything else the same... please help!! Thanks!!
node 0.12.7
robotjs

@happilymarrieddad this usually means that you have to recompile RobotJS. You can do this by going into the robotjs directory inside node_modules and running node-gyp rebuild. It seems like the staging server and the production server might have different Node.js versions.

@happilymarrieddad were you able to get this resolved?

I'm going to close this, please let me know if you're still having issues.

This is fixed thanks!


Incorrect hover documentation for syntax "solve" : term

I have defined a custom notation for terms with the keyword solve.  When hovering over such term I'm getting documentation of already existing solve tactic and not the documentation for the solve term.
mwe
import Lean
open Lean Parser Elab Term

def solveFun (f : α → Prop) : α := sorry

/-- solve term -/
elab "solve" xs:funBinder* ", " b:term : term => do
  let e ← elabTerm (← `(solveFun fun $xs* => $b)) none
  return e

#check solve x, x = 10

Hovering over solve in the last command displays Similar to `first`, but succeeds only if one the given tactics solves the current goal. I'm expecting to see solve term
Tested on
leanprover/lean4:nightly-2023-08-18
and the behavior is the same in Emacs as in VS Code

Note that what you get here depends on where you hover. Highlighting the keyword (1) gives the tactic docs, but highlighting the middle of the term (2) gives the term docs
#check solve x, x = 10
   --    ^1    ^2
```

Odd, but still that is not expected behavior, right?

Was this fixed by #2586?

Yes!