fix(builder) set strip_path after defaults

https://github.com/Kong/kubernetes-ingress-controller/pull/2286 failed when trying to add v1.11.0 to KIC. Something appears to have happened after I tested with https://github.com/Kong/deck/pull/573.
Within ingresRoute, the value is false as expected after it's set to the result of getStripPathBasedOnProtocols(). It flips back to true after https://github.com/Kong/deck/blob/v1.11.0/file/builder.go#L786
I thought this maybe meant something didn't work as expected with https://github.com/Kong/deck/pull/580, but as these were already *bool any non-nil value is not zero, so I'm not sure why the default was merging over the original value.
The change here does fix the issue, but I'd like to better understand what's going on here if possible.

Codecov Report

Merging #596 (cec1ac2) into main (4235c73) will increase coverage by 0.07%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #596      +/-   ##
==========================================
+ Coverage   50.39%   50.46%   +0.07%
==========================================
  Files          74       74
  Lines        8277     8279       +2
==========================================
+ Hits         4171     4178       +7
+ Misses       3728     3725       -3
+ Partials      378      376       -2

Impacted Files
Coverage Δ

file/builder.go
56.62% <100.00%> (+0.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 4235c73...cec1ac2. Read the comment docs.


Spreadsheet: Refactor model to support nested rows

Currently, our presentation model is unaware of collection elements and other stuff. That's why we have complex value editors.
There's not a lot of information regarding this issue because it's about development.
This ticket is a part of #12148.


HIVE-25372: Advance write id for all the DDLs

What changes were proposed in this pull request?
Advance write ID during 12 DDLs
Why are the changes needed?
HMS cache relies on ValidWriteIdList to serve the data consistently.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Unit tests

Got a green build -> http://ci.hive.apache.org/blue/organizations/jenkins/hive-precommit/detail/PR-2524/3/tests/

@pvary @hsnusonic Please take a look now. Addressed all the comments and got a green run.


Reconfigure model-specific token limits

Some have relaxed token restrictions, while others have tightened them, depending on the latest model.
ref: https://platform.openai.com/docs/models/overview

https://github.com/3ru/gpt-translate/releases/tag/v1.1.10


Unable to install hi-ml, and pytorch and torchvision could not find a version that satisfies the requirement (torch==1.9.0 torchvision==0.10.0)

I am trying to use BioViL, but hugging face only has the text encoder. However, when I install the hi-ml package, hi-ml conflicts with many environment settings. Could you help me to fix it?

Hi @hxu105, can you say a bit more about

what exactly are you trying to do, how are you trying to install?
where do you get the error message?

Yes, please see the following images

Also, there is only text encoder on Hugging Face, will you consider releasing the image encoder on Hugging Face as well?

@fepegar @Shruthi42 for questions about the image encoder

Hi, @hxu105. We're not planning to release the image model on Hugging Face, but you can find it here. Please take a look at our Jupyter notebook.

Hi @fepegar, thank you, I do want to use the image model for extracting visual information, and I currently have issues in installing the hi-ml / hi-ml-multimodal packages, could you take a look at the above pictures and help me fix it？

Can you please try installing from this branch?
pip install git+https://github.com/microsoft/hi-ml.git@fperezgarcia/biovil-t-classifier-py310-compatible#subdirectory=hi-ml-multimodal

Things should work after this is merged:

https://github.com/microsoft/hi-ml/pull/928/

Thank, I can install the package now.


Typo in Migration

Namespace and package ID changes

All Microsoft.AspNetCore.* namespaces are renamed to Microsoft.AspNetCore.*.

Should be

All Microsoft.AspNet.* namespaces are renamed to Microsoft.AspNetCore.*.

Fixed.


HIVE-28282: Addendum: Merge-Insert with reserved keywords as column names

What changes were proposed in this pull request?

Merge-Insert with reserved keywords as column names
Why are the changes needed?

Fix
Does this PR introduce any user-facing change?

No
Is the change a dependency upgrade?

No
How was this patch tested?

Qtest

Please add the original commit message of HIVE-28282 too.

Please add the original commit message of HIVE-28282 too.

I am not sure where I should add it?


Add support for ElastiCache Redis

Redis List operations added here https://github.com/SneaksAndData/esd-services-sdk/pull/78


The 'scheduled publishing' feature needs documenting

After a couple of years of working with Wagtail, i'm still not entirely sure what page revisions are capable of, and what they aren't, and also where the publish_scheduled_pages management command comes into it. It would be great to have some docs to explain things better. Some major points of confusion for me have been:

Can you schedule publishing of a revision for a page that is already live, and keep the current revision active until the scheduled time comes? It would seem you can't, but as a developer, I would've thought that was one of the primary benefits of keeping multiple revisions., and should be possible. I'm okay with it not working that way, but it doesn't seem to be explained anywhere, and I'm struggling to guide clients in using the CMS because of that.
What happens to a scheduled revision when another revision is published to the page before the scheduled revision's go_live_at date is reached? I think the scheduled revision is considered redundant, and should no longer become live when the time comes. But again, the limitations just don't seem to be explained anywhere.
What code is responsible for publishing a scheduled revision when the time comes? I'm guessing the publish_schedued_pages command is responsible for this, but can't find any reference to this anywhere other than in the reference section of the docs. If the scheduled publishing fields are to be present by default, but require a 'recurring task' to be set up in order for them to work properly, I'd expect that to be outlined very clearly in the docs. In fact, I'd probably expect that feature to be disabled by default, and that I'd need to use a setting to turn it on, after setting everything up properly.

Hello @ababic, this is not proper documentation but taking a look at PR #205 should answer most of your questions about scheduled publishing!

Thanks @spapas, that does help a little with the things I was unsure about. We could still certainly do with some documentation, though. I would suggest as a minimum that a 'setting up a recurring task' part needs adding to the setup instructions (I would write it myself, but I don't see myself as technical enough to provide instructions on that - I have very little experience with celery/cron etc).
Secondary to that, would bean additional part in the Editor's guide, that would explain what editors can and can't do in simple terms (e.g. "If you schedule publishing for a live page, this will happen.")
And in addition, an a part in the Advanced topics, with more a more technical explanation of how it works (to better arm developers in explaining the feature to editors - if they neglect to read the part above, or want you to explain why certain limitations exist)

Docs via source-code 🤕 : https://github.com/wagtail/wagtail/blob/master/wagtail/core/models.py#L251

How about http://docs.wagtail.io/en/v2.4/reference/pages/theory.html#scheduled-publishing ?

@tomdyson I see no references to live, go_live_at, and expired_at properties among others.

@tomdyson Ooh, I wasn't aware of the additions to the Theory page. While that is certainly helpful, I would suggest moving that out into a separate page in the docs (at the same level as Theory), so that we can build on it. Since I raised this originally (and now have a fair bit more documentation-writing experience), I'm happy to take a stab at that :) Thanks @lacymorrow for bringing this to light again - It had completely dropped off my radar.

See #8901, which significantly reworks the UI of scheduled publishing, and would be a good occasion to also document how it works for end users as well as developers (we’ve had to research the implementation a lot to get there).


Change background image and remove blue header colour

@bia

Can I get a link to the image / is it safe to rip from Figma (I'm assuming it's in the dark mode tab)
Are we still expecting the header to be fixed as you scroll? May or may not look odd with how it blends into the background with the changes.

@joshri sorry this is a duplicate that github accidentally created of #2377
We are not expecting the header to be fixed as you scroll - unless we get a good idea about how to style it.


Updated docs for DELETE /portfolio with proper response

https://projects.engineering.redhat.com/browse/SSP-166
This PR fixes the openapi documentation for the DELETE /portfolios endpoint. Before it specified a 200 with the portfolio object being returned, now it shows that it returns nothing.

@gmcculloug - could you take a look?


init doesn't recognize an initialized store if using a different crypto provider

Summary
If you run the init command after a password store has already been initialized, but specify a different crypto provider than the one used in the initialized store, init will not recognize that the store is already initialized.
Steps To Reproduce

Make sure that the root password store is not initialized (e.g. set GOPASS_HOMEDIR to a new temp directory)
Run gopass init to initialize the root store with the default GPG encryption.
Run gopass init --crypto age to initialize the root store with Age encryption.

Expected behavior
When running the second gopass init command, it should report that the store is already initialized. If you run gopass init twice with the same crypto provider, it will report:
✗ Store is already initialized!

It appears that gopass is only checking for the recipient id file which corresponds to the crypto provider specified in the current init command. It does not check if the store directory already contains an id file for a different crypto provider.


Fix bug in utils.py occuring since python version 3.12.3

In python version 3.12.3 PEP 701 they changed how f strings get parsed. As a result "\.00" gives an error now instead of \\.00.
I tested that the bug fix also works with python version 3.11.9.

Thanks for the PR, indeed python 3.12 introduced a bug here.

 They even noted in the PEP that it should be backwards compatible.

It seems like that the change was introduced with this commit 3483299a24e4 and has nothing to do with PEP 701. So I'm not sure if it is an python bug, since I don't know pythons backward compatibility rules.

The issue has been fixed by another branch. Thanks for the pr but this is superseded, the bug should be fixed now on master.

a new version of wolframclient has been pushed to pypi, let me know if that works for you
https://pypi.org/project/wolframclient/1.4.0/


Add methods to deque

Adds copy, index, insert, __contains__, __add__ and __mul__ to deque.

Looks like there's a repr issue:
from collections import deque
d = deque([1, 2], 5)
assert list(d*2) == [1, 2, 1, 2]
assert repr(d*2) == "deque([1, 2, 1, 2], maxlen=5)"


build new schema

This PR is an enhancement for #12 to print schema. For now, there is no support for a few GraphQL Types like Date, Long etc.
Sample for running the project :
jdbc-url : jdbc:teiid:customer@mm://localhost:31000
driver name : org.teiid.jdbc.TeiidDriver

Amazing change!Really good work! I will see if I can write simple unit tests for it to verify it and add testing to build process tomorrow.
@ani-sha do you think we can architecture this code so we can have this engine independent from database - so we can mock the data layer easily and provide.
I was checking JDBC mocking libraries as well but wanted to ask you first what would you prefer personally.

Sample for running the project :
jdbc-url : jdbc:teiid:customer@mm://localhost:31000
driver name : org.teiid.jdbc.TeiidDriver

Trying to get this running with Postgress but getting strange errors.
Do you have some docker-compose?
How to run this? Assume that I'm 5 years old and can execute commands like:
java -jar target/graphqlcrud-java-1.0.0-SNAPSHOT-runner.jar

Do you think we can architecture this code so we can have this engine independent from database

This is great point, I mentioned this before to @ani-sha probably lost in translation. Maybe I can help with arranging the code a little bit for that to the separation of concerns. Can I merge and start on that if everyone is Ok?

Do you think we can architecture this code so we can have this engine independent from database

This is great point, I mentioned this before to @ani-sha probably lost in translation. Maybe I can help with arranging the code a little bit for that to the separation of concerns. Can I merge and start on that if everyone is Ok?

Okay with me.

Same for me. Thanks for merging.


Revert "Merge pull request #1352 from parkera/parkera/reduce_test_times"

Tests did not fail during local run/smoke test, but did in CI.
This reverts commit ce0122b9488d676802d9645ab7b7525ac4cccf90, reversing
changes made to 1b91087d37fa154119c59f622b34556fccb21876.

… The wrong patch got reverted. Please disregard.


NetworkManager: Update resource states to 'AVAILABLE' from 'PENDING' after create response

For NetworkManager: Update resource states to 'AVAILABLE' from 'PENDING' after create response to more accurately represent the mocked resource

Probably not necessary but I think you could use the Managed State model here if you wanted

That is true, @mattheidelbaugh, that would achieve the same result. For this scenario, with only one immediate transition, the current implementation is probably the simplest, so I'm happy with that.
Thanks for the PR @zkarpinski!


Sc 3262

Description

Added React Table Component  for Sauce Connect Download / Releases
Motivation and Context

Ensures SC Connect content/URLs are dynamically updated
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Documentation fix (typos, incorrect content, missing content, etc.)

Checklist

[x] I have read the contributing document.
[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

I'm adding the new endpoint here
Will review it with the team today and we'll try to deploy it next week


document or file

Icon Request

Icon name: document and file
Tags of this icon: file_tick or which you want
Use case: document and file
Screenshots of similar icons:

https://remixicon.com/icon/file-check-line

Can you add 3 line bottom of the file? like i sent pic

We hope that this icon can be part of a set with other icons and have the same standards, so there should not be three lines added.
If  you need this, I think I can separately provide you the SVG file.


Integrate with Gridsome

Hi @everyone,
I would like to integrate umami with Gridsome:
https://gridsome.org/
Just adding the tracking code in this format did not work:

Any help is welcome!

The app is built with Next.js which is React based. It's not a Vue app.

The app is built with Next.js which is React based. It's not a Vue app.

Sorry for the confusion.
I would like to know how to integrate the tracking code in Gridsome.
Tracking code:

Does anyone know how it works?

Sorry for the confusion.
I would like to know how to integrate the tracking code in Gridsome.
Tracking code:

Does anyone know how it works?

@buildingisfun you can just add script into the  of the index.html
or add with vue-meta in the main.js like so:
export default function (Vue, { head }) {
 head.script.push({
    src: 'https://xxx.com/umami.js',
    dataWebsiteId: 'xxx-xxx-xxx',
    defer: true,
    body: true,
  })
}

@buildingisfun you can just add script into the  of the index.html
or add with vue-meta in the main.js like so:
export default function (Vue, { head }) {
 head.script.push({
    src: 'https://xxx.com/umami.js',
    dataWebsiteId: 'xxx-xxx-xxx',
    defer: true,
    body: true,
  })
}

umami is installed and works fine.
umami analyzes sites where the script is added into the  of the index.html.
@jeferson-sb thank you for your response!
My gridsome project does not have an index.html.
Therefore I added the following in the main.js (as suggested):
export default function (Vue, { head }) {
head.script.push({
src: 'https://xxx.com/umami.js',
dataWebsiteId: 'xxx-xxx-xxx',
defer: true,
body: true,
})
}
Unfortunately, umami does NOT recognize the site built with Gridsome.
What am I missing? Any idea?

umami is installed and works fine.
umami analyzes sites where the script is added into the  of the index.html.
@jeferson-sb thank you for your response!
My gridsome project does not have an index.html.
Therefore I added the following in the main.js (as suggested):
export default function (Vue, { head }) {
head.script.push({
src: 'https://xxx.com/umami.js',
dataWebsiteId: 'xxx-xxx-xxx',
defer: true,
body: true,
})
}
Unfortunately, umami does NOT recognize the site built with Gridsome.
What am I missing? Any idea?

@buildingisfun hmm the script tag is being renderer with the correct id (data-website-id)?

@buildingisfun hmm the script tag is being renderer with the correct id (data-website-id)?

@jeferson-sb yes, the id is correct.
Maybe it is because of
data-website-id ... umami tracking code.
vs
dataWebsiteId ... your suggestion for Gridsome.
What do you think?
How could you implement 'data-website-id' in Gridsome?

@jeferson-sb yes, the id is correct.
Maybe it is because of
data-website-id ... umami tracking code.
vs
dataWebsiteId ... your suggestion for Gridsome.
What do you think?
How could you implement 'data-website-id' in Gridsome?

@buildingisfun I guess instead of using the head.script.push command you can create a new index.html in your src directory and paste the script tag directly
<!DOCTYPE html>
<html ${htmlAttrs}>
  <head>
    <script async defer data-website-id="YOUR_WEBSITEID_GENERATED_ON_UMAMI" src="UMAMI_URL/umami.js"> </script>
    ${head}
  </head>
  <body ${bodyAttrs}>
    ${app}
    ${scripts}
  </body>
</html>

If that didn't work, then it is most likely to be an error within your umami setup or project

@buildingisfun I guess instead of using the head.script.push command you can create a new index.html in your src directory and paste the script tag directly
<!DOCTYPE html>
<html ${htmlAttrs}>
  <head>
    <script async defer data-website-id="YOUR_WEBSITEID_GENERATED_ON_UMAMI" src="UMAMI_URL/umami.js"> </script>
    ${head}
  </head>
  <body ${bodyAttrs}>
    ${app}
    ${scripts}
  </body>
</html>

If that didn't work, then it is most likely to be an error within your umami setup or project

@jeferson-sb I created a new index.html and used the code provided in your last comment. This way it works! Thanks a lot!
Now, I am curious why it did not work in main.js with the code @jeferson-sb provided above. Does anyone know why?

@jeferson-sb I created a new index.html and used the code provided in your last comment. This way it works! Thanks a lot!
Now, I am curious why it did not work in main.js with the code @jeferson-sb provided above. Does anyone know why?


Allow to use UIToolkit

It seems that the current way is to inject IMGUIContainer, maybe it would be possible to allow us to use just UIToolkit? It would make styling consistent with the existing UI a lot easier

I have written a UIToolkit sample:
https://gist.github.com/SolarianZ/26a6bb7a8de62e5d5adf41cc9e34de69


No keycloak provider

Dear team,
I try to use this with my self-hosted keycloak. Unfortunately, the Provider class does not contain a value for Keycloak. How can I use this?
Thanks a lot!

Hi @cremfert,
Are you trying to implement social login using keycloak? If so, is there a reason why you cannot use Supabase's social login?

https://github.com/supabase-community/gotrue-dart/pull/74 should fix this!


Amount paid

functionality needed for #103

Current coverage is 94.65% (diff: 100%)

Merging #105 into master will increase coverage by 0.16%

@@             master       #105   diff @@
==========================================
  Files            23         23
  Lines           527        543    +16
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            498        514    +16
  Misses           29         29
  Partials          0          0

Powered by Codecov. Last update ca72dd0...92c0440


Update rootchain contract

@kasima Yep

FYI, just updated the branching strategy over in plasma-contracts to match OIP-4. The ABI hasn't changed at all, so no need to update here. New releases for MinimalVP will end up on the v0.0 branch (and tagged).


[WIP] Listen to all namespaces

@andraxylia are you working on this?

Yes.

this is likely very out of date. closing it for now, will revisit post-alpha.


updates filer design and spaces

This pull request fixes the following issues:

BEFORE
AFTER

:+1:

:+1:  :+1:


Version Skew Policy - In-place Kubelet minor version upgrades are not allowed

Can it really be true that doing in place upgrades of the kubelet for minor versions is not allowed? How can worker nodes be upgraded in place with this policy?
https://github.com/kubernetes/website/blob/d69be9799dd1f28d0c08bb5122974777f51f8004/content/en/releases/version-skew-policy.md?plain=1#L219-L220
I think that the intent of the original commit  is to communicate that a node must be drained before the kubelet is upgraded. I'd suggest that language like the below would be clearer.
In-place minor version `kubelet` upgrades, without node drain, are not supported

The fix seems perfect to me @avestuk .

/sig docs
/language en

/cc @liggitt

/remove-lifecycle rotten

To me, it means almost the same thing. Maybe the understanding of In-place is different?
/cc @liggitt

@mengjiao-liu The old language In-place minor version kubelet upgrades are not supported. isn't accurate. In-place minor version kubelet upgrades ARE supported, you just have to drain the node before you proceed.

I get it.

Ok glad we're on the same page. Perhaps I've misunderstood your comment - if it's important/something I can help to clarify then please let me know.

/remove-lifecycle stale


umd module compiler option doesn't have a fallback for global namespace.

Most umd patterns have a third fallback that allows exporting to the window.namesapace = export; As such the current umd module export is pretty broken when a huge number of users / library developers need to support all three.
(function(root, factory) {
  if (typeof define === 'function' && define.amd) {
    define(factory);
  } else if (typeof exports === 'object') {
    module.exports = factory(require, exports, module);
  } else {
    root.exceptionless = factory();
  }
}(this, function(require, exports, module) {}

There is no specification for UMD and any interfaces with the global/window object require some specific decisions, like you would have to determine a module name for each module.  What names on the global scope would you give these modules, all part of the same project?
src/index.ts
src/feature/index.ts
document.ts

If I'm outputting to a single file (like a library like jquery) it becomes very easy to say the export should be namespaced under the file name or module namespace.
https://github.com/umdjs/umd/blob/master/templates/commonjsStrictGlobal.js
We have to support a fallback to globals in our library and I've had to work around this like:
https://github.com/exceptionless/Exceptionless.JavaScript/blob/feature/heartbeats/dist/exceptionless.js#L1235-L1271

You can find a discussion on why UMD implementation does not support the global in https://github.com/Microsoft/TypeScript/pull/2605.
mainly, what is the variable name to use, and how to manage dependencies.
One possibility is to use the new export as namespace <id> syntax added in https://github.com/Microsoft/TypeScript/pull/7264

There is precedent [1] [2] for compilers that output UMD to take a separate parameter for the global name. But I guess since you already have export as namespace you might as well use it.

//cc: @RyanCavanaugh

As discussed in #9678, if we use export as namespace for setting the global name, then the export clause needs to be allowed in normal code other than declarations (.d.ts), otherwise library authors that are deriving their declarations from the --declaration flag have to add the clause at each recompile because it's overwritten.
So merging the two needs, my proposal is:
When --module is umd and there's an export as namespace in module code, TypeScript should:

emit declaration files .d.ts with the same clause export as namespace
provide a fallback for global namespace case.

Example: developer is writing a library "myreact" to be consumed in modules and in global:
myreact.ts:
export function createElement() { return 42; };
export as namespace React;

Typescript output
myreact.d.ts:
export declare function createElement() {};
export as namespace React;

myreact.js:
(function (root, factory) {
    if (typeof module === 'object' && typeof module.exports === 'object') {
        var v = factory(require, exports); if (v !== undefined) module.exports = v;
    }
    else if (typeof define === 'function' && define.amd) {
        define(["require", "exports"], factory);
    }
    else {
        root.React = factory(require, exports);
    }
})(this, function (require, exports) {
    "use strict";
    function createElement() {
        return 42;
    }
    exports.createElement = createElement;
});

@nippur72 something like that could work but you also have to consider that require and exports won't always exist when doing a fallback to browser global and is the exact reason I had to do a hack:
https://github.com/exceptionless/Exceptionless.JavaScript/blob/master/dist/exceptionless.js#L1236-L1264 (which we may not what to do.

@niemyjski yes the missing require is a problem. Also I don't think your hack covers all the cases, consider for example:
import _ from "lodash";

which translates into the now global code
var _ = require("lodash");

which is nothing else than
var _ = window["lodash"];

but which is also undefined because lodash is published globally as window._, not window.lodash.
So, we can fake require but still can't do nothing for modules whose global name is different than the respective module name. Is my understanding correct?

idk, it's something that has to be looked into...

I don't see why the require would be a problem:
https://github.com/umdjs/umd/blob/master/templates/returnExports.js

By the way, I did this two years ago, maybe it can be simplified and used in the compiler.

👍 it would be good if there was a tsConfig option for this. I ran into this today.

Any news on this issue?
At moment what is "bes tway" (or just an acceptanle one)  to implement an UMD module with TypeScript? I mean a module that falls back on globals i needed.
I need to implement a library composed of several modules that user may select accordint to its need. I would like each module be UMD, so user may decide how and if bundling the modules it needs.
It appears that my plan at moment is very difficult to implement in TypeScript. The only way I can think of is:

processing each .js produced by the TypeScript compiler with a bundler to transform it into an TRUE UMD (one that falls back on globals if needed)
After TypeScript compilation, process each d.ts ouput file to "add an export as namespace ..." statement.

The above appears to me the only way to get TRUE UMD modules from TypeScript.
Any thought about this?
Better proposals?

I ran into this issue today.
I need a else block like this ;-)
  } else {
    root.exceptionless = factory();
  }

@zixia,
Actually, extending to global namespace is not so simple. Popular global libraries have a one-level namespace, such as jQuery, ko, etc. However, propietary libraries usually have multi-level namespaces. Something like this: companyname.libraryname.librarymodule. So, in general, modules doesnt map easily and univocally to namespaces.
I wrote an article on how to author multi-platform (amd, commonjs, es6, global namespace) libraries with Typescript, and some simple software to process automatically all source files to get both .d.ts and compiled .js for all platforms. The article should appear in the upcoming May magazine of the DotNetCurry magazine

Hi @frankabbruzzese,
Thank you very much for replying me!
In order to make my UMD bundle work directly by <script src='...'>, I made a dirty fix yesterday:
Firstly, I had to switch to use rollup instead of tsc --module umd, because tsc does not compatible with Angular AOT compiler.(https://github.com/zixia/brolog/issues/52)
Secondly, I had to use global.ModuleName instead of global.namespace.ModuleName for my need, and remove other pollution such like add __esModule property.
The modification is like this one:
4c4
<             (factory((global.brolog = global.brolog || {})));
---
>             (factory(global));
227d226
<     Object.defineProperty(exports, '__esModule', { value: true });

My repo: https://github.com/zixia/brolog
I know it's not a good solution for all, but it really works very nice for my tiny module. ;-)
I'll keep trying to find a better solution to replace this method, and I'm looking forward to reading your article of compile .js for all platforms. Please post the link to this thread after it publishes, so I can read it at the first time.
Thanks!

I just found another hacky workaround for rollup at https://github.com/rollup/rollup/issues/494#issuecomment-268243574

@zixia ,
My article is out. It is in the May-June issue of DotNetCurry magazine. You may download it from the main page of the magazine . At the end of the aricle there is also the link to a GitHub repos containing the whole software.

@frankabbruzzese Awesome, thank you very much!

@zixia ,
Please notice that my proposal is a pre-processing of TypeScript sources. After having run my script you will get 3 different distributions: one for AMD+CommonJs, one for ES6, and one for globals, from an unique source. This way you may decide yourself the wrapper to put around the core code for each of the three platforms. I think this is the more general solution, sicne the library struture may be quite different in each of the three platforms.

Now my article on mult-platform support for TypeScript libraries has been published also here.

How about this solution:
Example input source/index.js
import stuff from './my-sub-module'
import _ from 'lodash'
export const theAnswer = 42

When following options are specified in tsconfig.json, it enables code generation for global object exports:
{
  "globalName": "MyModule", // global var for this module
  "globalMap": { // map of modules and their global names
    "lodash": "_"
  }
}

Generated compiled/index.js:
(function (root, factory) {
  // stuff that already works
  if (typeof module === "object" && typeof module.exports === "object") {
    module.exports = factory(require, exports)
  }
  else if (typeof define === "function" && define.amd) {
    define(["require", "exports", "./my-sub-module", "lodash"], factory)
  }
  // Use globals (interesting stuff starts here)
  else {

    // init exports object
    root.MyModule = {}
    // for sub-module it would be root.MyModule.MySubModule

    // insert globalMap from config here
    const globalMap = {…}

    function require(mod) {
      if (mod[0] == '.') { // if module is relative
        // insert logic for resolving relative module here
        // e.g. for ./foo-bar/thing it should return <current>.FooBar.Thing
        return …
      }
      else { // if module is not relative
        // do the mapping
        if (mod in globalMap) mod = globalMap[mod]
        // return name from global object
        return root[mod]
      }
    }

    factory(require, root.MyModule)

  }
})(this, function (require, exports) {

  const foo = require("./foo") // returns root.MyModule.Foo
  const _ = require("lodash") // returns root._
  exports.theAnswer = 42 // assigns root.MyModule.theAnswer

});

It does generate a lot of overhead code for every file, but it's completely optional

If you are defining a new module format, consider adding an __esModule property with a value of true to your output to support interop with SystemJS, Babel, and other tool chains.
TypeScript adds this when transpiling a module using import and export unless it contains an export assignment (export = value).

I also would like this. I'm currently achieving this by doing a similar method as @frankabbruzzese suggested, which was preprocessing the TS and generating files for global and UMD and then running tsc on those files. It works fine, but it's a really hacky way just to get around not having window.myNamespace = myNamespace.

This no clear reason why you'd need hacks or additional tools to accomplish such a small thing.
Why can't we have something like "moduleGlobal": "var_name", which would add a global variable fallback for module types like amd, commonjs and umd? That makes it opt-in and doesn't interfere with existing projects that might not want it.
I really don't want hacks (or big tools like webpack) for a simple small library 😐

One more example that uses multi-level namespace (twttr.txt): https://www.npmjs.com/packages/twitter-text

Is it not possible for the typescript compiler to incorporate a bundle process, either one that already exists - webpack/rollup or one that theoretically shouldn't be too difficult to implement? I mean there are solutions to this problem, namely export as CommonJS and have a bundler re-bundle as UMD. However that kind of defeats the purpose of having the UMD option in typescript.
You wouldn't really have to change anything for the current UMD process, just add an extra config option so previous code is still maintained in the same way.

If the umd module can not support global variable, why typescript call it umd? So I suggest remove this option if it can not support.

@njleonzhang, UMD is a convention, not a standard and global modification is not entirely consistent or common in implementations. It is also a bit too late to remove it.

global modification is not entirely consistent or common in implementations

Maybe we can accept some popular behavior, for example from rollup.js . https://github.com/twitter/twitter-text/blob/master/js/rollup.config.js#L36-L37

@saschanaz I am not saying that solving the problem isn't warranted.  I am just pointing out that there is no UMD "standard" to adhere to and it makes it non-sensical to suggest removing the feature as @njleonzhang suggested.
Of course once you start dealing with deep creation of the global var, you start making the emit pretty darn ugly and starts really encroaching on contravening non-goal:

Provide an end-to-end build pipeline. Instead, make the system extensible so that external tools can use the compiler for more complex build workflows.

If you need a bundler, use a bundler.

Of course once you start dealing with deep creation of the global var, you start making the emit pretty darn ugly

Why? TS is already doing that and it isn't too ugly.
namespace A.B {
    var x = 0;
}

// emits:

var A;
(function (A) {
    var B;
    (function (B) {
        var x = 0;
    })(B = A.B || (A.B = {}));
})(A || (A = {}));

If you need a bundler, use a bundler.

We don't need a bundler, instead we need a proper emission for export use namespace.

@kitsonk Although I have some words to refute you, I shut up at this time to avoid meaningless argument in this thread. I just want typescript to fix this, or if you really want to keep it, at least document it explicitly. The UMD, as a convention, usually supports global variable. current situation really makes users confused.

Proposal: export as namespace for UMD module output
Syntax:
NamespaceExportDeclaration:
   export as namespace IdentifierPath
Behavior:
export var x = 0;
export function y() {}
export default {};
export as namespace My.Custom.Namespace;

// emits:

(function (global, factory) {
  if (typeof module === "object" && typeof module.exports === "object") {
    var v = factory(require, exports);
    if (v !== undefined) module.exports = v;
  }
  else if (typeof define === "function" && define.amd) {
    define(["require", "exports"], factory);
  }
  else {
    global.My = global.My || {};
    global.My.Custom = global.My.Custom || {};
    global.My.Custom.Namespace = global.My.Custom.Namespace || {};
    var exports = global.My.Custom.Namespace;
    factory(exports);
  }
})(this, function (require, exports) {
  "use strict";
  exports.__esModule = true;
  exports.x = 0;
  function y() { }
  exports.y = y;
  exports["default"] = {};
});

Note:

This proposal basically follows Babel behavior.
Importing any module without a module loader will throw in this proposal. A further extension may use global namespaces as Babel does.
Babel overwrites on the existing namespace whereas this proposal extends the existing one, as TS namespace does.
Rollup has a special behavior where export default X works like CommonJS module.exports = X whereas this proposal does not.

Prior arts: Babel exactGlobals, Webpack multi part library, Rollup output.name option with namespace support

Hello, any news on this?
I am writing a module but i dont want a namespace. e.g.
export * from 'Person';
export * from 'Student';

export as no namespace;

that way when i reference using global i can just call
new Person();
new Student();

Hello, any news on this?
I am writing a module but i dont want a namespace. e.g.
export * from 'Person';
export * from 'Student';

export as no namespace;

that way when i reference using global i can just call
new Person();
new Student();

Wow, just ran into this today. It's 2021. This started in 2016. tsc is the easiest way to compile, but I can't use it. All I want is a simple application that runs in the browser without having to load something else. 😬

I was disappointed when I saw my UMD module did not work in browser. Standard or not, UMD means something to web developers and Typescript is just misleading when it says UMD but does not output proper UMD.

A core part of "Universal" is to include browser support if no other module loader is found - note that this means it's only doing this when there is no other option - not all of the time. That is - the library would only do it if:

The user expects the library to act like jquery does when you <script src="./path/to/jquery.js"></script> and make an appropriate namespace.
The developer intends their library to do that.

I'd say that's not ugly at all.

here is no UMD "standard" to adhere to

There is, actually a standard. It's been around since 2012. I see where you might have misunderstood, however. It was common practice for years to just copy code from their templates into your JavaScript file, and edit as needed, or just make code vaguely inspired off of the last time one saw a UMD module that does more-or-less the same thing - but perhaps not as good. Simply stated, there is no standard tooling but there is a standard - even if it isn't followed 100% of the time.

fallback will pollutes the global namespace. for example
// a.ts

export function foo() {
  console.log('foo a.ts')
}

// b.ts
export function foo() {
  console.log('foo b.ts')
}

These two files will fallback to the global namespace and conflict, This produces some unexpected behavior.
But sometimes a simple function is needed, without any module loader or bundler, it can be run directly from the

typically, UMD style fallbacks would be a global named after the library name. This global would be an object containing all of the exported functions. If the file needs a fallback and it's not supposed to be standalone, then it would be a sub-object underneath the globally exposed library name object. This recurses  down with imports.
My understanding is that this would still be using the export _ syntax in source.
Granted, misunderstandings aside, I'm not as convinced this needs to be a feature in typescript in 2023 anymore, seeing current progress in ESM. Progress halted by typescript - by not properly supporting ESM until very recently, ironically

Any status on this, guys? 🤐


Cannot start fe in Mac environment.

Mac env  exec start_fe.sh :
commond :
./bin/start_fe.sh

or

bash ./bin/start_fe.sh

or

sh ./bin/start_fe.sh

ERR msg :
bin/start_fe.sh: line 228: syntax error near unexpected token `>'
bin/start_fe.sh: line 228: `    exec &>> $LOG_FILE'

Steps to reproduce the behavior (Required)

CREATE TABLE '...'
INSERT INTO '....'
SELECT  '....'

Expected behavior (Required)
Real behavior (Required)
StarRocks version (Required)

You can get the StarRocks version by executing SQL select current_version()

Good catch. it is a bash4 feature, not portable on bash3.
B.t.w., starrocks frontend/backend is not tested to run on mac os natively, it may or may not fail.


ESP-DL tutorial/tvm_example No module named 'tvm.relay.op.contrib.esp' (IDFGH-12113) (AIV-678)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
5.0
Operating System used.
Linux
How did you build your project?
Command line with Make
If you are using Windows, please specify command line type.
None
What is the expected behavior?
successful build
What is the actual behavior?
esp-dl/tutorial/tvm_example$ . ./script.sh
Collecting tensor data and making histogram ...
Finding optimal threshold for each tensor using entropy algorithm ...
Number of tensors : 25
Number of histogram bins : 128 (The number may increase depends on the data it collects)
Number of quantized bins : 128
WARNING:root:Please use QuantFormat.QDQ for activation type QInt8 and weight type QInt8. Or it will lead to bad performance on x64.
Traceback (most recent call last):
File "../../tools/tvm/export_onnx_model.py", line 11, in
from tvm.relay.op.contrib.esp import preprocess_onnx_for_esp, evaluate_onnx_for_esp
ModuleNotFoundError: No module named 'tvm.relay.op.contrib.esp'
Steps to reproduce.
cd esp-dl/tutorial/tvm_example
. ./script.sh
Build or installation Logs.
esp-dl/tutorial/tvm_example$ . ./script.sh
Collecting tensor data and making histogram ...
Finding optimal threshold for each tensor using entropy algorithm ...
Number of tensors : 25
Number of histogram bins : 128 (The number may increase depends on the data it collects)
Number of quantized bins : 128
WARNING:root:Please use QuantFormat.QDQ for activation type QInt8 and weight type QInt8. Or it will lead to bad performance on x64.
Traceback (most recent call last):
  File "../../tools/tvm/export_onnx_model.py", line 11, in <module>
    from tvm.relay.op.contrib.esp import preprocess_onnx_for_esp, evaluate_onnx_for_esp
ModuleNotFoundError: No module named 'tvm.relay.op.contrib.esp'

More Information.
Also tried on Mac Intel, M1 and M2 and Windows 11

You can refer to the following link for details: https://docs.espressif.com/projects/esp-dl/en/latest/esp32s3/tutorials/deploying-models-through-tvm.html#set-tvm-package-path
Check if the PYTHONPATH environment variable is set to the correct value, ensuring that the path matches the local tvm/python folder path (export PYTHONPATH=$PYTHONPATH:/path-to-esp-dl/esp-dl/tools/tvm/python).

On Ubuntu, the following output is produced:
esp-dl/tutorial/tvm_example$ . ./script.sh
Collecting tensor data and making histogram ...
Finding optimal threshold for each tensor using entropy algorithm ...
Number of tensors : 25
Number of histogram bins : 128 (The number may increase depends on the data it collects)
Number of quantized bins : 128
WARNING:root:Please use QuantFormat.QDQ for activation type QInt8 and weight type QInt8. Or it will lead to bad performance on x64.
Model Information:
Input Name: input_1
Input Shape: (1, 32, 32, 3)
Input DType: float
Output Name: Identity
Output Shape: (1, 10)
Output DType: float
One or more operators have not been tuned. Please tune your model for better performance. Use DEBUG logging level to see more details.
esp_dl_library_path: /media/mpm/FiveTDrive/esp-dl
generated project in: ./new_project
The environment variable is set:
$ env | grep PY
PYTHONPATH=/media/mpm/FiveTDrive/esp-dl/tools/tvm/python
Also:
esp-dl/tools/tvm/python/tvm$ file *.so
libtvm_runtime.so: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked, BuildID[sha1]=b282dcf2103ca41ed42da59b5cab959277d8cac6, with debug_info, not stripped
libtvm.so:         ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked, BuildID[sha1]=c635d10c85e10f342ea6b2d48de8b8056125536b, with debug_info, not stripped
On the MAC:

Your previous error was: “ModuleNotFoundError: No module named 'tvm.relay.op.contrib.esp'.”
So, has your problem been resolved on the Ubuntu platform? Currently, it is not supported on macOS platform.


Configure max heap memory (Xmx) in start-tc-server.sh

Max heap space (-Xmx) should be configurable via an environment variable, defaulting to the current hardcoded value of 2049m.
https://github.com/Terracotta-OSS/terracotta-core/blob/master/terracotta-kit/src/assemble/server/bin/start-tc-server.sh#L50
We're currently having to edit the start script due to running out of heap space with the current hardcoded value.

If anyone finds this looking for a solution to increase the heap, here's one way:
docker run -d --entrypoint "" terracotta/terracotta-server-oss:5.6.4 \
  bash -c "sed -i 's/-Xmx2049m/-Xmx8g/' /terracotta/server/bin/start-tc-server.sh && /terracotta/entrypoint.sh"

You can modify Xmx by setting JAVA_OPTS environment variable before executing the script.  Any values there will be adopted by the JVM.

Wow, yes, I totally overlooked that JAVA_OPTS is specified after the defaults. So instead of the command above, one can increase the heap size like this:
docker run -d -e JAVA_OPTS="-Xmx8g" terracotta/terracotta-server-oss:5.6.4

You can see that the passed options are picked up in the JVM args (and come after the defaults, overriding them)
JVM arguments: [-XX:MaxDirectMemorySize=1048576g, -Xms256m, -Xmx2049m, -XX:+HeapDumpOnOutOfMemoryError, -Dtc.install-root=/terracotta/server, -Xmx8g]

and that the runtime memory is affected
2021-07-30 17:02:51.868  INFO   --- [           main] org.terracotta.console                  : Available Max Runtime Memory: 7282MB

Thanks!


Trying to render results for first time inside a modal

I have a button that when pressed will open a modal and then render the query results. As I don't want the query to run on page load only when someone opens the modal to see the results.

<button sprig id="myBtn">All</button>

    ×
    {% if sprig.request %}
     {% set users = craft.follow.following() %}
        {% for user in craft.users.id(users) %}

        {% set optimizedAuthorPic = user.getPhoto().authorPic %}

        {% endfor %}
        {% endif %}

If I click the button, it quickly renders the modal with the query results and then dissapears.
I think its because its re-rendering the HTML in the DOM when the button is pressed and the Javscript for the modal can't run properly and resets classes etc.
I don't get errors, but the Modal relies upon an onClick trigger to change the classes on the element but I think during the re-rendering it basically re-sets everything. I hope I make sense.
Is there any way around getting the two to play together nicely?

Thanks
Tom

You probably don't want to re-render the entire component, but just the contents of the modal. Using s-target like this might work:

<button sprig s-target="#myModal" id="myBtn">All</button>

@bencroker that seemed to do the trick, I had something similar previously but it wasn't working!
Cheers

Great!


Problem with "Collector" + "Identified by" field types in Scratchpads

Those fields correspond to the current "recordedBy" and "identifiedBy". See problem documentation at https://github.com/NaturalHistoryMuseum/scratchpads2/issues/6169
Issue opened here following the suggestion of Peter Desmet, during TDWG 2020 session "Capturing Ideas for the Future of BioCASe Provider Software and the GBIF Integrated Publishing Toolkit (IPT)".
Can edit further if necessary.

Thanks @Archilegt
If I understand correctly from the discussion on that thread this is a Scratchpad issue, where they aren't letting a curator enter recordedBy and identifiedBy fields but instead internally SP is tying it to another content model.
Is there a specific concern you have on the IPT, or are you raising this as an example to make sure the IPT doesn't impose incorrect limitations on data mapping?


parse build version on xcodeproj

Fixes: #105551
Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[x] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is [test-exempt].
[x] All existing and new tests are passing.

Rebase on master to resolve the stray command test failure.


fix: Fix usage of default @Provider methods in IdentityDidCoreExtension

What this PR changes/adds
Make some @Provider methods non-default in IdentityDidCoreExtension as this is causing non-deterministic dependency injection in IdentityHub project.
Why it does that
Default @Provider methods depending on injected services might be invoked while these services are not yet initialized.
Checklist

[ ] added appropriate tests?
[ ] performed checkstyle check locally?
[ ] added/updated copyright headers?
[ ] documented public classes/methods?
[ ] added/updated relevant documentation?
[ ] assigned appropriate label? (exclude from changelog with label no-changelog)
[ ] formatted title correctly? (take a look at the CONTRIBUTING and styleguide for details)

Codecov Report

Merging #1792 (8cc5914) into main (765983d) will decrease coverage by 0.01%.
The diff coverage is 80.00%.

@@            Coverage Diff             @@
##             main    #1792      +/-   ##
==========================================
- Coverage   67.82%   67.80%   -0.02%
==========================================
  Files         795      800       +5
  Lines       16899    16979      +80
  Branches     1078     1080       +2
==========================================
+ Hits        11461    11512      +51
- Misses       4969     4997      +28
- Partials      469      470       +1

Impacted Files
Coverage Δ

...aceconnector/iam/did/IdentityDidCoreExtension.java
66.66% <80.00%> (+8.60%)
:arrow_up:

...ypes/domain/contract/offer/ContractDefinition.java
77.77% <0.00%> (-3.00%)
:arrow_down:

...taspaceconnector/spi/types/domain/asset/Asset.java
88.57% <0.00%> (-2.06%)
:arrow_down:

...tor/spi/types/domain/transfer/TransferProcess.java
67.85% <0.00%> (-0.03%)
:arrow_down:

.../dataspaceconnector/spi/entity/StatefulEntity.java
0.00% <0.00%> (ø)

...clipse/dataspaceconnector/policy/model/Policy.java
81.15% <0.00%> (ø)

...onnector/policy/model/PolicyRegistrationTypes.java
0.00% <0.00%> (ø)

...nnector/sql/assetindex/schema/AssetStatements.java
100.00% <0.00%> (ø)

...iation/ConsumerContractNegotiationManagerImpl.java
87.38% <0.00%> (ø)

...main/contract/negotiation/ContractNegotiation.java
0.00% <0.00%> (ø)

... and 32 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


feat(server): automatically extract forwarded-for header

closes https://github.com/denoland/fresh/issues/1827
Or rather, the discussion that happens later in the issue.
This change modifies the call to Deno.serve to automatically extract the X-Forwarded-For header, if it exists. This is then available in HandlerContext, MiddlewareHandlerContext, and RouteContext.

@marvinhagemeister, based on https://github.com/denoland/fresh/issues/1827#issuecomment-1794435015 I guess I should close this. Before I do though: do you see any value in having the handler passed to Deno.serve configurable/overridable? If not, I'll close it. If yes, I can rework this.
Right now I don't see any way of controlling middleware execution order, so if someone absolutely needs something to run first, they're out of luck. Being able to override the Deno.serve handler and having the ability to order middleware (especially from plugins) seems like it would increase flexibility. I can open a separate issue for middleware ordering if desired.


Use consistent parameter order of (before, after) throughout update APIs

Currently most of the update APIs use the parameter order (before, after), but there are some that have the order (after, before). Since these parameters are the same type the compiler won't be able to catch it if we accidentally call them with (before, after) and we'll get runtime bugs where an update gets applied in the "wrong direction". We should make the update APIs consistent so that any APIs that take (before, after) or (old, new) parameters always take them in the same order.

Currently #1267 is still outstanding, so I'd like to wait until it's merged before tackling this. That way we'll minimize the chances of bugs being introduced by merge conflict resolutions.

Going to start working on this using #1295's branch as a base, then rebase to develop when #1295 is merged.


help: Fix minor bugs in keyboard shortcuts help.

First commit
This info was already in the Basics section, but was missing from the Navigation section.
Current:  https://zulip.com/help/keyboard-shortcuts#navigation and help modal

Updated

Second commit
The current sizing (12px) looks really bad at 16px font size:
It's also not necessary, as the modal is currently wide enough such that there's no line wrapping. It's not translated, so we can worry about line wrapping in other languages when we fix that (which may be after we redesign this modal).

Before (16px)

After (16px, 14px)

Merged, thanks @alya!


Update installation instructions (docker etc)

How do I install, step by step, prerequisites, and link from main readme.
(ref: https://github.com/microsoft/BotFramework-Composer/tree/stable/Composer)

@cwhitten - are we supporting docker?

Hi @scheyal
FYI. Our current installation doc with yarn is here. I have doubled checked with @boydc2014, he said "docker is not recommended and supported" at this point.
Thanks!
Yan

We are closing this issue at this point and will reopen when the "docker" installation is supported in Composer. Thanks!


issue: "recompile FFmpeg with openssl"

Checklist

[x] I'm asking a question
[x] I've looked through the README and FAQ for similar questions
[x] I've searched the bugtracker for similar questions including closed ones

Question

ok, "recompile FFmpeg with openssl", do you know a good HOWTO for dummies?
hints welcome!

Google it.

for those who are interested: "https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu"
add --enable-openssl to the compilation parameters
happy compiling...


data: array is shown as a single string...

Hello!
Wonderful plugin!
When I use a variable to pass an array, the input tag is parsing it is a single string. I have tried several splitting methods, etc. Here is the code...
`$(document).ready(function () {
var dispatchNames = [];

$('.square').each(function () {

    //convert each .square class div toString
    var square = $(this).html().toString();

    //grab availability value (if True, tech is available)
    var availability = $(this).find('tr:eq(4)').find('td').text();

    //grab IP (if exists, tech is online)
    online = $(this).find('tr:eq(3)').find('td').text()

    if ((availability === "True") && (online.indexOf("10.") === 0)) {

        //grab tech name
        dispatchNames.push([$(this).find('tr:eq(0)').find('td').text()]);

    }

})

var availableTechs = {

    data: [dispatchNames]

};

$("#dispatchTechs").easyAutocomplete(availableTechs);

//alert(dispatchNames);

})`
The variable 'dispatchNames' is an array that I can move through with an index, but when it is passed to 'dispatchNames' in 'availableTechs', it is a single string. This means the input control only has 1 selection instead of several.
Please advise,
Thank you!!

So, I got this working but removing the array wrapper from my 'dispatchNames' array, so that it was no longer a single object. I changed it to...
var availableTechs = { data: dispatchNames, };
However, now I cannot get the Match method to work. When adding it exactly as shown in the documentation, the autocomplete stops working. It does not find any names in the list.
Please advise.
`        var availableTechs = {
    data: dispatchNames,
    list: {
        match: {
            enabled: true
        }
    }`

I am getting the following error in console when match: is enabled....
jquery.easy-autocomplete.js:64 Uncaught TypeError: element.search is not a function
at Object.method (jquery.easy-autocomplete.js:64)
at match (jquery.easy-autocomplete.js:653)
at findMatch (jquery.easy-autocomplete.js:630)
at proccessData (jquery.easy-autocomplete.js:613)
at ListBuilderService.processData (jquery.easy-autocomplete.js:455)
at loadData (jquery.easy-autocomplete.js:1338)
at HTMLInputElement. (jquery.easy-autocomplete.js:1308)
at HTMLInputElement.dispatch (jquery-3.3.1.js:5183)
at HTMLInputElement.elemData.handle (jquery-3.3.1.js:4991)

Tambien tengo el mismo error, como lo solucionaste?


Foundry project was not able to initialize correctly: Error: Couldn't find forge binary.

Problem:
When attempting to open a Foundry project in VSCode using the Nomic Foundation Solidity extension, I encounter the following error:
Foundry project 'fund-me-foundry' was not able to initialize correctly: Error: Couldn't find forge binary. Performed lookup: ["forge","C:\\Users\\USERNAME\\.cargo\\bin\\forge"]

I installed Foundry on Windows using Git Bash with the command:
curl -L https://foundry.paradigm.xyz | bash.

And I ran foundryup  after installation.
When I run  where forge in terminal, I get this path:  "C:\Users\USERNAME.foundry\bin\forge.exe."
I investigated further and found this commit:
https://github.com/NomicFoundation/hardhat-vscode/pull/378/commits/90102debe1455a81551003aa716a6dd4ecedc521#diff-bb3d24c14df5446295dea3e272f667fcf3b9cd17ca7eb49863750e526c78ed67
In the file: server/src/frameworks/Foundry/FoundryProject.ts starting from line 223 there is this piece of code:
 if (runningOnWindows()) {
      potentialForgeCommands.push("%USERPROFILE%\\.cargo\\bin\\forge");
    } else {
      potentialForgeCommands.push("~/.foundry/bin/forge");
    }

So I figured out that this path is probably hardcoded everywhere and this might be why I am encountering this issue.
When I switch to the Juan Blanco Solidity extension, I don't have this problem, so that is why I think this is problem with extension and not with my installation. It is worth mentioning that all my commands (until now) work correctly, and I have no problem with that, it is just this annoying error that I get when I open Foundry project.

Same issue here, running on windows too. Everything works fine except this annoying error message when opening vscode.
The correct path is "%USERPROFILE%\\.foundry\\bin\\forge", instead of "%USERPROFILE%\\.cargo\\bin\\forge".
The problematic part is here: server/src/frameworks/Foundry/resolveForgeCommand.ts
export async function resolveForgeCommand() {
  if (resolvedForgeCommand) {
    return resolvedForgeCommand;
  }

  const potentialForgeCommands = ["forge"];

  if (runningOnWindows()) {
    potentialForgeCommands.push(
      `${process.env.USERPROFILE}\\.cargo\\bin\\forge`
    );
  } else {
    potentialForgeCommands.push(
      `${process.env.XDG_CONFIG_HOME || process.env.HOME}/.foundry/bin/forge`
    );
  }

There is a fix suggested in this PR: https://github.com/NomicFoundation/hardhat-vscode/pull/515

yes i am having same issue.What is the solution ?


fix: fixes build process on Windows

This PR replaces rm -rf with rimraf to ensure it works properly on Windows (in the same way it is done on vite and other packages).
Fixes #74

Neat 👍 .
One little thing: the user should still be able to follow the steps of https://github.com/brillout/vite-plugin-ssr/tree/master/examples/react. We should also add the rimraf dependency to each example.

We should also add the rimraf dependency to each example.

It was added to every instance of "rm -rf", including that one.

Thanks 👍

FYI https://github.com/brillout/vite-plugin-ssr/commit/d12ca50412a83f5011af545184ebf3ca52df9275 :-)

Thanks, I was unaware of the best way to add the dependency.


Track deployment changes via Dynatrace Deployment Events

Instead of going down to manually adjust CI/CD pipelines for every app and service I would like Dynatrace OneAgent to monitor deployment changes and notify Dynatrace accordingly.

👍


Improve scripts

Use pkgs.writeShellApplication instead of pkgs.writeShellScriptBin + PATH
writeShellApplication also integrates shellcheck into the build process, so the script was changed to follow the recommendations.
Turn generate-latest-release.nix into a flake package
Use https://downloads.openwrt.org/.versions.json to get all and latest versions

I wasn't able to find what populates this file or how it's created, but OpenWrt Firmware Selector and Attendedsysupgrade use it, so I assume it's safe and up-to-date. Having a JSON makes things much simpler and easier to work with.

Awesome. Thank you!


Add filters for Volume and Open Interest to Options cmd

Adds flags
-o to display only options whose open interest is > int
-v to display only options whose volume is > int

Nice, I will review and merge shortly.


Keyword search is not functional

Enter text into the search input.
Click the "check/finish" button or press Enter to close the keyboard.
Note that your entered text has now been cleared from the search input.

tested on android

tested on iPhone

tested on iPad

Verified - Test PASS


Feature/rwa 238 workflow message endpoint

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Close in favour of this one: https://github.com/hmcts/wa-case-event-handler/pull/29


feat(blocks): add Block data source

Summary
Closes https://github.com/PrefectHQ/terraform-provider-prefect/issues/175
To do

[ ] Consider adding fields to the schema that represent nested objects (see https://github.com/PrefectHQ/terraform-provider-prefect/pull/209#issuecomment-2159262200)
[ ] Consider getting block by name (see https://github.com/PrefectHQ/terraform-provider-prefect/pull/209#issuecomment-2159316724)
[ ] Consider adding tests (see https://github.com/PrefectHQ/terraform-provider-prefect/pull/209#issuecomment-2159332243)

Testing
First, start up the local instance:
docker compose up -d

Create a main.tf file with these contents:
terraform {
  required_providers {
    prefect = {
      source = "registry.terraform.io/prefecthq/prefect"
    }
  }
}

provider "prefect" {
  endpoint = "http://localhost:4200/api"
}

resource "prefect_block" "secret" {
  name      = "foo"
  type_slug = "secret"

  data = jsonencode({
    "value" : "bar"
  })
}

data "prefect_block" "my_existing_secret" {
  id = prefect_block.secret.id
}

output "block_info" {
  value     = data.prefect_block.my_existing_secret
  sensitive = true
}

Test it:

Click to expand
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create
 <= read (data resources)

Terraform will perform the following actions:

  # data.prefect_block.my_existing_secret will be read during apply
  # (config refers to values not yet known)
 <= data "prefect_block" "my_existing_secret" {
      + block_schema_id = (known after apply)
      + block_type_id   = (known after apply)
      + block_type_name = (known after apply)
      + created         = (known after apply)
      + data            = (sensitive value)
      + id              = (known after apply)
      + name            = (known after apply)
      + updated         = (known after apply)
    }

  # prefect_block.secret will be created
  + resource "prefect_block" "secret" {
      + created   = (known after apply)
      + data      = (sensitive value)
      + id        = (known after apply)
      + name      = "foo"
      + type_slug = "secret"
      + updated   = (known after apply)
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Changes to Outputs:
  + block_info = (sensitive value)

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

prefect_block.secret: Creating...
prefect_block.secret: Creation complete after 0s [id=b98844a2-39a5-4ba3-9562-0f104cc4c33f]
data.prefect_block.my_existing_secret: Reading...
data.prefect_block.my_existing_secret: Read complete after 0s [id=b98844a2-39a5-4ba3-9562-0f104cc4c33f]

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

Outputs:

block_info = <sensitive>

Get the specific value:
$ tf output -json block_info | jq .data
"{\"value\":\"bar\"}"

Currently, some of the fields in the schema are omitted because I'm not yet sure how to represent types other than string, UUID, or timestamp. Here's the full response from the API Read document by ID:

Click to expand
{
  "block_documents": {
    "operator": "and_",
    "id": {
      "any_": [
        "497f6eca-6276-4993-bfeb-53cbbbba6f08"
      ]
    },
    "is_anonymous": {
      "eq_": false
    },
    "block_type_id": {
      "any_": [
        "497f6eca-6276-4993-bfeb-53cbbbba6f08"
      ]
    },
    "name": {
      "any_": [
        "string"
      ],
      "like_": "my-block%"
    }
  },
  "block_types": {
    "name": {
      "like_": "marvin"
    },
    "slug": {
      "any_": [
        "string"
      ]
    }
  },
  "block_schemas": {
    "operator": "and_",
    "block_type_id": {
      "any_": [
        "497f6eca-6276-4993-bfeb-53cbbbba6f08"
      ]
    },
    "block_capabilities": {
      "all_": [
        "write-storage",
        "read-storage"
      ]
    },
    "id": {
      "any_": [
        "497f6eca-6276-4993-bfeb-53cbbbba6f08"
      ]
    },
    "version": {
      "any_": [
        "2.0.0",
        "2.1.0"
      ]
    }
  },
  "include_secrets": false,
  "sort": "NAME_ASC",
  "offset": 0,
  "limit": 0
}

So the current fields omitted are:

block_schema
block_type
block_document_references

I'm also omitting is_anonymous, but I don't think we need to expose that (yet?).

@parkedwards two quick questions:

Do you see a need to add these currently-omitted fields to the data source?
If yes, do you happen to know how to do it? I'm seeing some references to nested objects as a type but seems a little verbose.

Looking into querying by name:
In the Read Block Documents endpoint, we could allow a user to pass a name value and then interpolate it to fit into the block_documents.name.like or block_documents.name.any field:

This seems doable, but will require a more detailed implementation to do that translation. At the moment, I'm thinking that querying by ID should cover most use cases (especially since users would likely reference the object by the friendly data.prefect_block.my_block.id identifier).
What do you think @parkedwards?

I drafted a test, but looking at existing Datasource tests it seems like they read existing objects in Prefect. Wondering which project we create these in, since I can't read the encrypted variables in the GitHub project once they're written.
In this case I'd need to go create a block named my_block before committing the test (following the example from the variable_test.go).
package datasources_test

import (
	"fmt"
	"testing"

	"github.com/hashicorp/terraform-plugin-testing/helper/resource"
	"github.com/prefecthq/terraform-provider-prefect/internal/testutils"
)

func fixtureAccBlockByID(name string) string {
	return fmt.Sprintf(`
data "prefect_block" "test" {
	id = prefect_block.%s.id
}
`, name)
}

//nolint:paralleltest // we use the resource.ParallelTest helper instead
func TestAccDatasource_block(t *testing.T) {
	datasourceName := "data.prefect_block.test"
	blockName := "my_block"
	blockValue := "{\"value\":\"bar\"}"

	resource.ParallelTest(t, resource.TestCase{
		ProtoV6ProviderFactories: testutils.TestAccProtoV6ProviderFactories,
		PreCheck:                 func() { testutils.AccTestPreCheck(t) },
		Steps: []resource.TestStep{
			{
				Config: fixtureAccBlockByID(blockName),
				Check: resource.ComposeAggregateTestCheckFunc(
					resource.TestCheckResourceAttrSet(datasourceName, "id"),
					resource.TestCheckResourceAttr(datasourceName, "name", blockName),
					resource.TestCheckResourceAttr(datasourceName, "data", blockValue),
				),
			},
		},
	})
}

Do you see a need to add these currently-omitted fields to the data source?
If yes, do you happen to know how to do it? I'm seeing some references to nested objects as a type but seems a little verbose.

@mitchnielsen you're right, i think we can omit those, and i added a couple more in the comments above that we might think about skipping.  the nested object typing is a little nasty, and if we dont believe users to need to actually access those property values (which im not sure they do as of right now - that could change, at which point we can always take on the incremental work to support those), then we can omit

This seems doable, but will require a more detailed implementation to do that translation. At the moment, I'm thinking that querying by ID should cover most use cases (especially since users would likely reference the object by the friendly data.prefect_block.my_block.id identifier).

great idea, and totally do-able. i think we should do this (in this PR or a followup).  the general idea would be - allow the user to input either an id or a name, and based on the presence of either (you'd have to give precedence to one of those, so it'd probably be id) - you'd fire off a request to either the Get(id uuid.UUID) client method that we already have OR we can add a List(names []string) method to the client (similar to what you did with BlockSchema client)
check out the variable.go datasource, we do something similar there
https://github.com/PrefectHQ/terraform-provider-prefect/blob/main/internal/provider/datasources/variable.go#L121-L164

I drafted a test, but looking at existing Datasource tests it seems like they read existing objects in Prefect. Wondering which project we create these in, since I can't read the encrypted variables in the GitHub project once they're written.

@mitchnielsen yeah that was an approach i started with but dont love.  maybe we can create a new block resource in the same fixture string (right before your datasource) and then you can compare values against your input resource and the queried datasource

I drafted a test, but looking at existing Datasource tests it seems like they read existing objects in Prefect. Wondering which project we create these in, since I can't read the encrypted variables in the GitHub project once they're written.

@mitchnielsen yeah that was an approach i started with back then but dont love. maybe we can create a new block resource in the same fixture string (right before your datasource) and then you can compare values against your input resource and the queried datasource

Works for me. I was originally wondering if it should be cleaned up after the test run, but it's probably alright for now that it stays around since even concurrent tests won't try to modify it.


Remove hardcoding from jupyter notebooks

ROOT = 'c:/UCSC/Projects/PolyPhy/repo/PolyPhy/',  use relative paths.
Assume that we are starting from the main directory of the repo
https://github.com/PolyPhyHub/PolyPhy/blob/main/experiments/jupyter/PolyPhy_3D_mask_data.ipynb

Deprecated issue, development moved away from Jupyter notebooks


Add testing infra. and first unit-test for e-cash recovery

Follow-up to #1015
Add some basic infra to allow reasonable code to test recovery logic, and a first test to validate the approach.
Also, store unsigned notes in the backup and add code to handle them during recovery.

@elsirion Please let me know if this fundamentally looks good to you, so I can write bunch of other tests using similar approach.

Codecov Report
Base: 0.00% // Head: 65.81% // Increases project coverage by +65.81% :tada:

Coverage data is based on head (ad87948) compared to base (bebe4e1).
Patch coverage: 92.62% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff             @@
##           master    #1068       +/-   ##
===========================================
+ Coverage        0   65.81%   +65.81%
===========================================
  Files           0      116      +116
  Lines           0    18799    +18799
===========================================
+ Hits            0    12372    +12372
- Misses          0     6427     +6427

Impacted Files
Coverage Δ

client/client-lib/src/mint/backup.rs
59.66% <36.11%> (ø)

client/client-lib/src/lib.rs
78.45% <100.00%> (ø)

client/client-lib/src/mint/backup/tests.rs
100.00% <100.00%> (ø)

client/client-lib/src/mint/db.rs
58.33% <100.00%> (ø)

client/client-lib/src/mint/mod.rs
75.91% <100.00%> (ø)

modules/fedimint-mint/src/lib.rs
77.98% <100.00%> (ø)

crypto/tbs/src/serde_impl/scalar.rs
81.81% <0.00%> (ø)

gateway/ln-gateway/src/client.rs
23.23% <0.00%> (ø)

fedimint-api/src/module/audit.rs
97.56% <0.00%> (ø)

fedimint-api/src/macros.rs
13.07% <0.00%> (ø)

... and 112 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


runtime(vim): Update base-syntax, improve :menu{,translate} highlighting

Improve :menu and :menutranslate highlighting.

Match args to :menutranslation and :popup.
Only highlight special notation in {rhs} of :menu, like :map.
Allow line continuations in {rhs} of :menu and between {english} and
{mylang} of :menutranslation, matching common usage.
Highlight :popup {name}.
Bug fixes.

thanks!


feat: parallelize VisibilityTracker::from_crate

Small perf gains as there isn't much we can parallelize without more code massaging:
(92a9868) ❯ cargo criterion --bench indexed_crate --features rayon
IndexedCrate/new(aws-sdk-ec2)
                        time:   [574.13 ms 575.49 ms 576.92 ms]

(changes) ❯ cargo criterion --bench indexed_crate --features rayon
IndexedCrate/new(aws-sdk-ec2)
                        time:   [557.73 ms 559.38 ms 560.96 ms]
                        change: [-3.1709% -2.8003% -2.4380%] (p = 0.00 < 0.05)
                        Performance has improved.

Last part of #402

Resolves #401.


turbo-carto: category quantification method

New datasource quantification method for categories.
It depends on CartoDB/turbo-carto#15.

This was done at https://github.com/CartoDB/Windshaft-cartodb/pull/462.


Rebased 21Jan14

Sorry. Thought I was submitting the PR to my own fork. No matter I guess. I've had this fork around for a long time because I use the plugin in an old app. Just made an addition commit to get it working with JQuery 2


Error running in CodeSandbox

When I click to edit in CodeSandbox, this error shows:

Invariant Violation
Hooks can only be called inside the body of a function component.

I've fixed it. Haven't updated the dependencies for a while.


Trying to run AtlasMap standalone on local side

Hello, everyone.
I cloned the atlasmap project and ran the Java project on Windows 11's WSL today.
$ cd ${ATLASMAP}
$ ./mvnw clean install -DskipTests -Pitests
Encountered Non-parseable POM issues.

I hope someone will help me. Thanks.

Try deleting .m2 folder.

Hi,
I fixed the maven issue after modification of pom.xml in parent file.
The main issue is that the project is using the deprecated and unsupported repositories.
So I commented the unsupported repositories like that.

Thanks.


'HTML Source' button

Are there any plans to add this button?
Thank you for the nice control!

Are you just looking for a button to show the html that this wysiwyg is generating?

I need the functionality that the '<> Source' button provides on the CKEditor: http://ckeditor.com/demo

I used xeditable plugin to duplicate '<> Source'
Edit HTML:
{{data.text}}

You should be able to do this out side of the wysiwyg editor by displaying the content of the bound scope variable in a div or text area.  However I will add this as a future feature.


Get own cars data

Hello!
I would like to ONLY get my own car data such as speed, RPM etc, and not the other cars. How would I approach this?

every packet has a header object with PlayerCarIndex property you can use that to find your cars data in the array.

// approximate example
let myCar = data.carTelemetry[data.header.playerCarIndex]

console.log(myCar.rpm)


Create a test novel

Need to make a test visual novel that can be distributed and used to test the program. While unit testing covers a lot of the core engine, it can't exactly cover if things are being rendered/played correctly.
Any art assets that are used should be open source or have permission from the artist to be a part of this repository.

Being worked on here https://github.com/ajusa/VNDS-TEST


Update TerminationCodeDTO according with the last API spec

Some of the codes specified here https://docs.databricks.com/dev-tools/api/latest/clusters.html#clusterterminationreasonterminationcode are not reflected in the TerminationCodeDTO => error on deserialization (*) => the cluster API is not usable.
(*)
Example:
Cannot deserialize value of type com.edmunds.rest.databricks.DTO.clusters.TerminationCodeDTO from String "SPARK_ERROR": not one of the values accepted for Enum class: [CLOUD_PROVIDER_LAUNCH_FAILURE, INIT_SCRIPT_FAILURE, INTERNAL_ERROR, INSTANCE_UNREACHABLE, INSTANCE_POOL_CLUSTER_FAILURE, COMMUNICATION_LOST, REQUEST_REJECTED, INACTIVITY, CLOUD_PROVIDER_SHUTDOWN, USER_REQUEST, TRIAL_EXPIRED, INVALID_ARGUMENT, SPARK_STARTUP_FAILURE, UNEXPECTED_LAUNCH_FAILURE, JOB_FINISHED]
https://github.com/edmunds/databricks-rest-client/pull/77
@samshuster

merged


[Bug report] $withBase / alias not working as expected

Bug report
Description
I am referencing https://v2.vuepress.vuejs.org/guide/assets.html#base-helper to fix the prefixes in my internal markdown links and observing that the alias isn't working.
For example, the base in config.ts is...  base: "/testsite"
When I use [test] ($withBase/intro) the resulting url is http://<IP_ADDRESS>:8080/testsite/$withBase/intro
I attempted to bybasss $withBase and try a custom vite alias (https://vitejs.dev/config/#resolve-alias) but had the exact same type of result.
Steps to reproduce

Add a base url to the config
Use $withBase in a markdown link to reference another page in the internal site

Reproduction link / repo:

Expected behavior
I expected when using [test] ($withBase/intro) that the result url would be http://<IP_ADDRESS>:8080/testsite/intro
Screenshots
N/A
Environment info

Browser: Chrome
vuepress: 2.0.0-beta.35
Output of vuepress info: N/A

# Paste output of `vuepress info` here How is this obtained?

I noticed that doing [test] (. /intro) produces the intended result. Is this something I can count on going forward?

$withBase is a function, not a marker.


[KED-2309] Apply the 'meta' flag for requests to the nodes endpoint

Description
related ticket: https://jira.quantumblack.com/browse/KED-2309
this ticket is to hide the calls to the node API endpoint behind the meta flag so calls will only be fired when the meta flag is true.
Development notes
I had added an extra check for the meta field within the loadNodeData action, as well as updated the tests to check for this condition.
QA notes
Clicking the nodes will not trigger any calls to the nodes endpoint unless the meta flag is true.
Checklist

[x] Read the contributing guidelines
[ ] Opened this PR as a 'Draft Pull Request' if it is work-in-progress
[ ] Updated the documentation to reflect the code changes
[ ] Added new entries to the RELEASE.md file
[ ] Added tests to cover my changes

Legal notice

[x] I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":

I submit this contribution under the Apache 2.0 license and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.

I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorised to submit this contribution on behalf of the original creator(s) or their licensees.

I certify that the use of this contribution as authorised by the Apache 2.0 license does not violate the intellectual property rights of anyone else.

looks like the pylint tests are failing on the CI - @limdauto wondering if you know what this could be?

Lim has fixed the Python linter in #323 so if you merge main it should fix the broken CI on this PR


Switch to NetCorePublic-Pool

At this time it doesn't look like there's a perf advantage to doing this, so not bothering.


Allow customized batch size for embedding inference

Current batch size is fixed as 1024 for gnn embedding inference, which is too large for language models or large language models.

Solved


Caching: persist between runs

Right now we cache GitHub API responses between audits/workflows, but there are a lot of responses that also make sense to cache between zizmor runs (e.g. a commit that isn't an impostor isn't going to become an impostor).

Thinking about this more: I think almost all of the caching can be moved into HTTP middleware, since nothing else we do is really that expensive (or more precisely, so expensive that it makes sense to cache between runs).
For HTTP caching, this looks promising: https://github.com/06chaynes/http-cache/tree/main/http-cache-reqwest

#304 is an attempt at the above.


Update power-bi-integration-entity-store.md

Removed article content on the legacy Entity Store management experience ported from AX2012

:x: Organization membership check failed
Members of the MicrosoftDocs organization should use the private repo. Please move your changes to https://github.com/MicrosoftDocs/Dynamics-365-Operations, and close this pull request.


Fix SQL Query

The last query in the "Monitor compute resource utilization" section should be
SELECT timestamp,
Double(details :cluster_resources.num_executors) as current_executors,
Double(details :cluster_resources.latest_requested_num_executors) as latest_requested_num_executors,
Double(details :cluster_resources.optimal_num_executors) as optimal_num_executors,
Double(details :cluster_resources.state) as autoscaling_state
FROM
event_log_raw
WHERE
event_type = 'cluster_resources'
AND origin.update_id = '${latest_update.id}'

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

ID: 4cc208f0-6faa-ebc7-07d1-9572a0ec2fd6
Version Independent ID: 4cc208f0-6faa-ebc7-07d1-9572a0ec2fd6
Content: Monitor Delta Live Tables pipelines - Azure Databricks
Content Source: databricks/delta-live-tables/observability.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

@ThatOrJohn
Thanks for your feedback! We will investigate and update as appropriate.


Unable to install CLI on raspberry pi

Describe the bug
When attempting to install the CLI on a raspberry pi, it fails without any errors
To Reproduce

SSH into the raspberry pi
Execute /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/AssemblyAI/assemblyai-cli/main/install.sh)"

Expected behavior
Installs the CLI
Experienced behavior
Prints
Using the OSS distribution...
Downloading AssemblyAI CLI v1.17.4...

No errors or other information is printed.
Desktop (please complete the following information):
$ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian

Additional context
n.a.

Ah 💡 Looking at your releases, the armv7 releases are missing although the install script is looking for it.
$ uname -m
armv7l

Hey @japborst! Currently, we offer support for armv6, although I just created a PR for supporting armv7 and will let you know as soon as we can test and release it.

Running armv6 does also work. Just mapping that in the install script unfortunately results in other errors, but have been able to manually install it as a workaround.

Hey @japborst! Yes, the issue was that on the install script we did not have support for armv7l architecture. This issue is now addressed on release v1.17.5


Performance

Hi,
Firstly, resolved paths were not cached, so I added a fix for that (1ea7c1e). Although the performance win for this one is quite minuscule.
Secondly -- derequire. Now THAT's a serious bottleneck. I suggest to make it optional, which is what 37d434c implements. In my case the bundle performance went from 13-ish seconds to 2 seconds with derequire disabled. And I never had any issues in our huge code-base with derequire off.
Cheers,
M.

FWIW<EMAIL_ADDRESS>is super fast now (see https://github.com/calvinmetcalf/derequire/pull/26)


Opening settings app and "going back" freezes watch

When you open the settings and close it right after that the watch freezes. Sometimes the clock is displayed (and time moves on), but most of the time the display is just black and no buttons work until reboot.
When the clock is displayed the buttons don't work as well.

Try pressing and holding Button 3. If there are notifications waiting, there is a race condition that sometimes freezes the watch. Best to clear your iPhone notifications in the iPhone notification centre before starting. After that notifications are cleared when you press OK so it does not happen.

Deleting the notifications did help a bit, but only so that it works in 2 out of 3 tries...

I do not have any problems switching between clock and settings as long as I do not turn the ANCS widget on or off.
When ANCS is turned off, the iPhone tries to reconnect and seems to crash the bluetooth firmware when you switch out of settings. If you turn iPhone bluetooth off or forget the Bangle pairing it does not happen.

For me it's still crashing when I simply open the settings app and go back. Are there some kind of debug logs I can access?

Here are a few things to try:

I have put the exact version of the firmware that I have on my Bangle - ...bangle’js new.zip in the repository.
I have pretokenize set on all my uploads - so both servings. clocks and the widget are tokenised. The switch is in the app loader under other.
Does it crash when you switch off bluetooth in your phone before switching?

I've just flashed that version, no change at all
Seems to help (haven't had that on until now, still new to this watch)
Seems to help as well, but I think I'll stick to #2

If 2 helps it’s probably a low memory issue - remove some other widgets.
3 should not be necessary.


Validate incoming JWT tokens from the bot framework

Proposed changes:
This PR enables JSON Web Token validation for the JWTs coming in from the Azure botframework channel. This is achieved by periodically updating the keys that Microsoft uses to sign the tokens, saving those in memory, and then validating the tokens and verifying their signature for incoming requests from the bot framework.
For details on how the botframework does authentication, see here.
Status (please check what you already did):

[x] added some tests for the functionality
[ ] updated the documentation
[x] updated the changelog (please check changelog for instructions)
[x] reformat files using black (please check Readme for instructions)

@Maxinho96 thank you for pointing thejwt.PyJWKClient out, did not know about that one before and looks great! We'll consider refactoring this again to use that.


fix the prefer email issue

Critical Changes
Changes

If you have email fields that use the same label as a HEDA email field, we now choose the HEDA version of the field for a Contact's Preferred Email address. For example, if a user chooses Work Email as the preferred email address and your org has multiple fields on the Contact object labeled Work Email, we use the value from the HEDA Work Email field.

Issues Closed
Fixes #543
New Metadata
Deleted Metadata
Testing Notes
Steps to reproduce #543 :

Org needs HEDA and NPSP installed.
When user try to set the prefer email as Work Email on a Contact and click Save, system will display an error "The prefer email can not be empty".
If you enter the HEDA Work Email field and click Save, you will still see the error.
If you enter NPSP Work Email field then the error will disappear.

The issue here is that the system is confused with HEDA Work Email field and NPSP Work Email field. The correct behavior is that system should display/not display error based on HEDA Work Email but not NPSP Work Email since the logic is in HEDA package.

@weizsforg Looks unchanged from when I last reviewed. Good to go!

This looks good. Work email for a contact can be chosen and saved fine if someone just has HEDA only and if they have HEDA and NPSP. The contact saves fine. Merging pull request. Great work @weizsforg


Implicit Validation of Collection-Type Models

Got a report from Oisín Grehan and Nacer Dergal in Slack of a scenario where they weren't seeing the validator run.
Turns out they had an array arg where the inner type had the validator. e.g. [SomeInput]
Essentially this is "Implicit Validation of Collection-Type Models" as discussed in FluentValidation's docs here.
By default they don't handle it, but you can opt-in to handle it.
Context:
Slack thread

This overlaps a little bit with discussions on #61 with Jeremy and the concern is really it'd open a can of worms. Plan is just to document that explicitness is key.

[ ] Update readme


Implement smooth scrolling for X11

Right now scrolling for X11 is handled via Button4 / Button5 key presses, which is very rough.
https://github.com/glfw/glfw/blob/53c8c72c676ca97c10aedfe3d0eb4271c5b23dba/src/x11_window.c#L1395
The comment above is not true since 2011, when X11 implemented a smooth scrolling, which allows pixel-precise control. It really makes a huge difference, please support it too.
You might find interesting corresponding issues for Chromium and Firefox, both implemented this long time ago, I simply was using these browsers to compare the behavior to a glfw-based app until I figured out where the problem is.
Cross-linking the issues: https://github.com/kovidgoyal/kitty/issues/1123

Definitely want to support this.

Bump

Bump noted.
Still want this to happen but have no time for it right now, especially as XI2 has little documentation beyond Who-T's blog. Will try to do this while implementing XI2 touch input.


Group sidecar tests together

Is your feature request related to a problem? Please describe:
A clear and concise description of what the problem is.
This is a step in the same direction as https://github.com/kubevirt/kubevirt/pull/10320
The hook sidecars can be used for a variety of things and we test those in different places. Considering that the sidecar is featured gated and all tests rely on hooks sidecar, we should group this tests together as much as possible.
Describe the solution you'd like:
A clear and concise description of what you want to happen.
We should have a new tests/sidecar folder which splits the tests between core functionality of sidecars and whatever extra we have that is related.
I consider core functionality what tests HookSidecar struct and sidecar-shim image. Extra would be testing specific sidecars like networking bindings or storage/hotplug.go
Describe alternatives you've considered:
A clear and concise description of any alternative solutions or features you've considered.
Additional context:
Add any other context or screenshots about the feature request here.

/label good-first-issue

/assign

@victortoso do you want the test/sidecar to have tests only related to the core functionality?

@pat-glitch there is already an assignee to this issue

Hi @rootxrishabh, how is it going? Let us know if you have any problems with setup, testing or the issue itself.

Hey, @victortoso I am really sorry but I currently don't have the bandwidth to complete this. @pat-glitch would you like to take this up?

/assign

/assign

Hello @victortoso, I am completed code and test on my local. However, when i am pushing the code it showing i dont have permission to push. Btw, this is first issue which i am working.

Hello @victortoso , I can see that there is wrong with bazel version. When I am running it bazel 7.2 it is showing like this.
ERROR: no such package '@@bazel_tools//platforms': BUILD file not found in directory 'platforms' of external repository @@bazel_tools. Add a BUILD file to a directory to mark it as a package.
ERROR: C:/users/nagarjunan/_bazel_nagarjunan/laj3cetw/external/io_bazel_rules_docker/toolchains/docker/BUILD:60:10: no such package '@@bazel_tools//platforms': BUILD file not found in directory 'platforms' of external repository @@bazel_tools. Add a BUILD file to a directory to mark it as a package. and referenced by '@@io_bazel_rules_docker//toolchains/docker:default_osx_toolchain'
ERROR: C:/users/nagarjunan/desktop/myfirstproject/kubevirt/BUILD.bazel:91:8: Analysis failed
ERROR: Analysis of target '//:gazelle' failed; build aborted: Analysis failed
INFO: Elapsed time: 0.802s, Critical Path: 0.06s
INFO: 1 process: 1 internal.
ERROR: Build did NOT complete successfully
ERROR: Build failed. Not running target
can you please confirm me which version are we currently using? This is my first PR and if possible please try help me to push to code. TQ :)


Showing error on vercel

showing error on the moment of building..Attaching screenshot and also pay button is not working.

yup getting same issue