Do not count directories

Fixes #1097.
Signed-off-by: Joe Grund<EMAIL_ADDRESS>

Codecov Report

Merging #1125 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1125   +/-   ##
=======================================
  Coverage   95.42%   95.42%
=======================================
  Files           2        2
  Lines         153      153
=======================================
  Hits          146      146
  Misses          7        7

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 429faa3...0275b8c. Read the comment docs.


Set $HOME in container

Currently the docker runtime always sets $HOME to /. We could offer conveniences to detect a more relevant value based on the current user.
One way is to parse /etc/passwd and look for the home directory corresponding to the current user. We already parse it when a user is configured with run -u, so why not?
Another way is to extend the WORKDIR build directive (which specifies which directory to execute the process in), and have it set $HOME to that value. We could rename that directive to "HOME" to make that more obvious.

Just want to note that this now works beautifully.
RUN umask 0077; mkdir $HOME/.ssh
ADD id_rsa-github_readonly_user $HOME/.ssh/id_rsa

Where before you had to...
RUN umask 0077; mkdir $HOME/.ssh
ADD id_rsa-github_readonly_user /id_rsa
RUN mv /id_rsa $HOME/.ssh/

...because the meaning of $HOME was different for the ADD command and the RUN command. I really appreciate this, @tianon.
NOTE: If you use ~ instead of $HOME, it will work in the RUN command, but the ADD command will create a $PWD/\~/ directory. (Not complaining. Just making it known.)


Update functions.php

actually, the upload function don't take any options from deploy.php, but documentation mentions option for rsync.
This commit correct that.

Q
A

Bug fix?
Yes

New feature?
No

BC breaks?
No

Deprecations?
No

Fixed tickets
N/A

What is this for?

@antonmedv
I just ran into this issue myseld and found this issue. The problem is that if you want to add your own options to rsync, in my case "--inplace", it will not be added because the 'options' config is always overwritten if there are SSH arguments.

actually, the upload function don't take any options from deploy.php, but documentation mentions option for rsync.
This commit correct that.

@antonmedv & @nicodmf
Unfortunately this change now causes a PHP notice:
PHP Notice:  Undefined index: options in src/functions.php on line 426
PHP Notice:  Undefined index: options in src/functions.php on line 452

@nicodmf please, fix

@antonmedv I've created a fix: #1264


TypeError json.encoder in default instead of real error, using sentry-sdk python

Environment
SaaS (https://sentry.io/)
Version
No response
Steps to Reproduce

have an URL triggering an error that contains special chars, for example an "!"
in sentry, I'll get a strange TypeError json.encoder in default
with an epic long stacktrace, that goes through all my django middlewares and more
using gunicorn. not sure if on my side something is configured wrong? as far as I can see, I use a very basic default configuration

python sentry-sdk: 1.4.2
    sentry_sdk.init(
        dsn=SENTRY_DSN,
        release=VERSION,
        integrations=[DjangoIntegration()],
    )

Expected Result
Report AttributeError 'NoneType' object has no attribute 'url_name' as is the orginal error in this case.
Actual Result
TypeError json.encoder in default
the (probably) payload, that is wanted to be json serialized:
{
environment: 'production',
public_key: 'blbalbalbablaFOOOOO,
release: b'0.0.1-178-g889a3c7',
trace_id: 'the-trace-id',
transaction: '/medien/Pressedossier_PENG!_PALAST.pdf'
}

keep getting more of these. could it be that this came in with newer sdk version?

probably the same: https://github.com/getsentry/sentry-python/issues/1222

pinning the sdk to sentry-sdk<1.4 has normal/expected behaviour.

@benzkji, I had the same issue, with this same apparent cause. Your release argument to init() is of type bytes. You should add decode() after it to convert it to a string. That resolved the issue for me. Though it is interesting that this only happened as of v1.4.0


Automatable Docs tasks

We need a script that checks for the following on all open PRs and prevents submission until these tests come back clean:
Sub issues:

[ ] #732
[ ] #731
[ ] #733
[ ] #734
[ ] #735
[ ] #736
[ ] #737
[ ] #738
[ ] #739

@bgrant0607 @pwittrock @janetkuo

and auto assign reviewers

Thanks!
Auto assign reviewer
Submit queue

K8s YAML validation

Previous issue: #102

Link checking

We've also discussed adding date last reviewed (as well as owners) to every doc, so we could enforce periodic reviews.

Regarding labels: It would help if they were identical to the corresponding labels in the main (kubernetes) repo.

cc @kubernetes/contributor-experience

Move mungedocs: https://github.com/kubernetes/kubernetes/issues/29314

One idea @johndmulhausen had was to automatically generate a PR containing necessary reformatting against the PR author's fork.

We're taking a different path towards automation issues.  Also, we should break up any general automation bug into specific tasks that can be completed.


Fix: Array Index Out of bound

there's a index out of bound on table_translator.cc:506
the error occurred when I try to input over about 20 characters.
Then I found when trying to add blank to preedit then increase pos, might leads input[pos - 1] out of bound.
I thought the pos should not be increased, instead using other varibles.

as the photo shows, pos 20 is greater than input,length // = 18, causing array  index out of bound

Commited as https://github.com/rime/librime/commit/ff7acdc36b30582f8720e445cd01505fbcc51624

Commited as https://github.com/rime/librime/commit/ff7acdc36b30582f8720e445cd01505fbcc51624

Commited as ff7acdc

Thx for response

Commited as ff7acdc

Thx for response


Scenario missing result

What's the result of https://docs.microsoft.com/en-us/azure/devops/pipelines/process/conditions?view=azure-devops&tabs=yaml#use-a-template-parameter-as-part-of-a-condition?

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

ID: 21e5cee4-eaae-3a96-db91-540ac759e83a
Version Independent ID: 9bdc837c-ffe0-d999-f922-f3a5debc7f92
Content: Conditions - Azure Pipelines
Content Source: docs/pipelines/process/conditions.md
Product: devops
Technology: devops-cicd-process
GitHub Login: @juliakm
Microsoft Alias: jukullam

@serge-portima Thanks for your question. While we look into any changes for the article, consider these resources:

Azure DevOps Services
Azure DevOps on Stack Overflow

@serge-portima Thanks for your feedback. I'm adding the result now.


return in finally can swallow exceptions

In https://github.com/gunthercox/ChatterBot/blob/4ff8af28567ed446ae796d37c246bb6a14032fe7/chatterbot/logic/unit_conversion.py#L164 there is a return statement in a finally block, which would swallow any in-flight exception.
This means that if a BaseException (such as KeyboardInterrupt) is raised from the try body, or any exception is raised from one of the except: clauses, it will not propagate on as expected.
See also https://docs.python.org/3/tutorial/errors.html#defining-clean-up-actions.

邮件已收到，谢谢您！


Added the text "The domain of y=e^x..."

Added how to find perimeter of a square.
"To find the perimeter of a square you have to add up all sides."

[x ] I have read freeCodeCamp's contribution guidelines.
[x ] My pull request has a descriptive title (not a vague title like Update index.md)
[x ] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thanks for the pr. Congrats on your first, if you see anything else you'd like to help with feel free to make another.


Polish TemplateParser and Template

We need to evaluate the API surface exposed by the classes used to parse and express templates

Considering this done once we get a chance to review it.

We reviewed it. It's done 👍


Create 2 lessc tasks to create 2 differente css files

I need to create a desktop and a mobile css files based on 2 differente less files
lessc {
sourceDir = 'src/main/less'
include "desktop.less"
destinationDir = 'build/server/css'
encoding = "utf-8"
}
what I need to do to create the additional task to create the mobile css version ?
I tryed this, but gradle return an error
task lessmobile(type: lessc) {
sourceDir = 'src/main/less'
include "mobile.less"
destinationDir = 'build/server/css'
encoding = "utf-8"
}
Error:
A problem occurred evaluating root project 'gsa-augsburger-allgemeine'.

com.github.houbie.gradle.lesscss.LesscTask_Decorated cannot be cast to java.lang.Class

I found this on the documentation, using it solved the problem.
You can define additional tasks with type com.github.houbie.gradle.lesscss.LesscTask


Invitation manager controller

[ ] Validate code, get org and confirm to join GET /join/{code} [user]
[ ] Confirm join POST /join/{code} [user]
[ ] Create an invitation link POST /invite/{org} [admin]
[ ] Remove an invitation link DELETE /invite/{code} [admin]

waiting on #109 ...


brew livecheck fails to install bundler gems

I suppose this is kind of expected, since normally brew installs its own dependencies when running some development commands for the first time, but is not allowed to modify the nix store:
$ brew livecheck --debug kde-mac/kde/kdeconnect
Error: Permission denied @ rb_sysopen - /nix/store/v19ip7y08262kadi01g4wnrr8cxd9qbx-brew-4.3.5-patched/Library/Homebrew/vendor/bundle/ruby/3.3.0/.homebrew_vendor_version
Warning: Removed Sorbet lines from backtrace!
Rerun with `--verbose` to see the original backtrace
/nix/store/v19ip7y08262kadi01g4wnrr8cxd9qbx-brew-4.3.5-patched/Library/Homebrew/utils/gems.rb:296:in `write'
/nix/store/v19ip7y08262kadi01g4wnrr8cxd9qbx-brew-4.3.5-patched/Library/Homebrew/utils/gems.rb:296:in `write'
/nix/store/v19ip7y08262kadi01g4wnrr8cxd9qbx-brew-4.3.5-patched/Library/Homebrew/utils/gems.rb:296:in `install_bundler_gems!'
/nix/store/v19ip7y08262kadi01g4wnrr8cxd9qbx-brew-4.3.5-patched/Library/Homebrew/dev-cmd/livecheck.rb:52:in `run'
/opt/homebrew/Library/Homebrew/brew.rb:92:in `<main>'

Is there some workaround I can use to either

preinstall the necessary dependencies in the patched brew (maybe a new nix-homebrew.setupCommands or something that can run some commands to install gems?)
tell brew to install in some other location, or give it a mutable directory to install stuff to?

Well, this is tricky... I think the second way sounds nicer, but I don't have a strong opinion on this.
For reference, we patch Brew to use the bundled gems from upstream with a Nix-managed Ruby interpreter here: https://github.com/zhaofengli/nix-homebrew/commit/e88b940e4ca15127991eb8095c56db40a55e457f


implement automatic refresh

like every minute or hour

FYI - if you mention in your PR something like "Resolves #48" then you will get an auto-closed issue upon merge.


Feature/animals table

Vet clinic database: create animals table
Summary
I added the "animals" table to the vet clinic database. Includes columns for ID, name, date of birth, escape attempts, neutered status, and weight. Populated with sample data. Milestone 1 is complete.
Results of the queries:

Hi @ShadyShawkat ! thanks much for your review. Have a great day!


Update GitVersion.yml

add " - 3e92b24568c98de5f3124g587ffd04e7af80f9c" to the file.

@Ravitejavelamuri can you please help me understand why this change is necessary?  NOTE: Failure to respond to this question will result in this PR being marked as invalid

@Ravitejavelamuri can you please help me understand why this change is necessary? NOTE: Failure to respond to this question will result in this PR being marked as invalid

i tried to make this change to the file for its further extension,but sorry that later i realized i gave you a wrong one,sorry for my mistake.My sincere apologies,im just a beginner.

@Ravitejavelamuri based on your response, I am going to close out this PR.


Refactor/css to bootstrap grid layout

Deleted old css layout files
Moved to Bootstrap grid layout
Added mobile support, so website should be usable on phones

 Task 10: Refactor some components so they would use Bootstrap Grid Layout instead of custom css layout.

There seems to be a bug where the layout does not switch back from mobile layout even though it has enough space.
Repro steps:

Open groups page.
Shrink window until layout changes to mobile layout.
Enlarge window.
Result: Phone layout stays indefinitely.
Expected: Should switch back to desktop layout once there is enough space.


A sketch of DAS integration

This is a very sketchy and possibly not a canonical (in future) way to integrate DAS into MeTTa, but it might be valuable to have, because there are some potential issues on both sides.

Further work on DAS integration requires some steps on the DAS side, so I'd prefer to merge it for now as a sandbox example


commonMessageHandler returning null

Hi there,
My luck that this is not maintained anymore.... :/
If anyone would be able to assist it would be great:
//subscribing to this endpoint:
subscription Subscription {
  organizationsChanged {
    id
  }
}

results in organizationsChanged to be null:
// Response received at 23:24:00
{
  "data": {
    "organizationsChanged": null
  }
}

// Response received at 23:23:59
{
  "data": {
    "organizationsChanged": null
  }
}

// Response received at 23:23:58
{
  "data": {
    "organizationsChanged": null
  }
}

Project setup is as follows:
//schema.ts
  type Subscription {
    organizationsChanged: testObject
  }

  type testObject {
    id: String
  }

//resolver
Subscription: {
    // get all tracks, will be used to populate the homepage grid of our web client
    organizationsChanged: {
      subscribe: () => pubsub.asyncIterator(["ORGANISATION_CHANGED2"]),
    },
  },

//init
import { GooglePubSub } from '@axelspringer/graphql-google-pubsub';
// SETUP subscriptions
function commonMessageHandler (payload:any) {
  console.log(payload.id); /// get the correct data from publish here - whohoo!
  return {
    id: payload.id
  }
}

const pubsub = new GooglePubSub({
    projectId: 'PROJECT_ID',
    credentials:{
      client_email: 'SERV_ACC_EMAIL,
      private_key: "THE_KEY"
    }
  }, topicName => `ORGANISATION_CHANGED2`, commonMessageHandler)
}

//package.json
"dependencies": {
    "@axelspringer/graphql-google-pubsub": "^2.1.0",
    "apollo-datasource-rest": "^0.14.0",
    "apollo-server": "2.19.1",
    "dataloader": "^2.0.0",
    "graphql": "15.4.0"
  },

Hi @thespacedeck -- You may have already found it, but check out the discussion in https://github.com/axelspringer/graphql-google-pubsub/issues/14.
I ran into this as well and fixed it with the suggestion of adding this to the schema:
...
			resolve: (payload) => {
				const utf8 = Buffer.from(payload.data, "base64").toString("utf-8");
				return JSON.parse(utf8);
			  },
			subscribe: withFilter(
....

Hi @kacy, thanks for that - adding the resolve did it for me! Rgds.

Hi @thespacedeck -- You may have already found it, but check out the discussion in #14.
I ran into this as well and fixed it with the suggestion of adding this to the schema:
...
			resolve: (payload) => {
				const utf8 = Buffer.from(payload.data, "base64").toString("utf-8");
				return JSON.parse(utf8);
			  },
			subscribe: withFilter(
....

Life changing.. After 3 days of scratching my head and trying all possible tricks to figure out why "null" was returned.. This was the answer and now it is working as expected.


Texture can be added twice to project but SHADERed crashes when loading that project later

Version 1.4.2, Internal version 19.
Platform: Windows 10.
Log from the crash on load:
[13:17:40] Creating a texture img/slime_wide_003_lowres.png ...
[13:17:40] Creating a render texture LumaRT ...
[13:17:40] Creating a texture img/slime_wide_003_lowres.png ...
[13:17:40] (ERROR) Cannot create a texture img/slime_wide_003_lowres.png because that texture is already added to the project
[13:17:40] Opening an ObjectManager item in the PropertyUI

For context, the second copy of the texture was added to be able to use different min and mag filters.

How were you able to add the second texture? SHADERed prohibits adding the same texture more than once to the project since it internally uses texture's path as an ID. I guess by editing the .sprj file?
I think the solution to this would be adding sampler objects to SHADERed. Though, I am not yet sure what they should look like UI-wise.

How were you able to add the second texture? SHADERed prohibits adding the same texture more than once to the project since it internally uses texture's path as an ID. I guess by editing the .sprj file?

In the GUI via the Objects tab.
I am able to create a second copy of the texture like that but not a third. See log when adding the texture to a file which already contains it:
[16:27:02] Creating a texture img\slime_wide_003_lowres.png ...
[16:27:19] Creating a texture img\slime_wide_003_lowres.png ...
[16:27:19] (ERROR) Cannot create a texture img\slime_wide_003_lowres.png because that texture is already added to the project

I think the solution to this would be adding sampler objects to SHADERed. Though, I am not yet sure what they should look like UI-wise.

Sounds right. It would be good to have a shortcut though: specify sampler state at the texture level as now rather than forcing people who use one sampler per texture to add a sampler object to their projects for every texture.

Tried to repro with an empty project in same directory, adding same png that could be added to the original project. I could only add it once. Conclusion: my original project is corrupt in some way that allows this as a side effect.


Fixing vulnerability issues on the apache-any23-encoding dependency.

Update pom.xml

Thanks for the PR! I applied it locally and all tests are still passing.
We will incorporate this patch in our development branch. Thanks!

Merged in development, will close the PR here. Fix will be available in next release, thanks!


v1.0.0

This PR creates the first major release of BaSiCPy.

Shall we also change the doc version?
https://github.com/peng-lab/BaSiCPy/blob/8c9e527a3ccfb411806507bd7715208aa085df3c/docs/conf.py#L27


separate gunicorn deps

The Python agent team is going to use vulnpy to test gunicorn for our supported max and min version. For that I've separated the gunicorn requirements out. I"ve tested this change doesn't break the agent pipeline, see PYT-1644-gunicorn in that repo - nothing there will be merged.

oh hold on I'm missing some code!


Failed to query data (context canceled error)

Describe the bug
Hello
We upgrade from zabbix 5.2 to 6.0.2 with grafana 7.3 and plugin 4.1.1.
At the moment of updating everything, we obtained no data in all the queries.
lvl=eror msg="Query data error" error="failed to query data: Failed to query data: rpc error: code = Canceled desc = context canceled"
Screenshots

Software versions

Grafana
Zabbix
Grafana-Zabbix Plugin

8.4.3 o 8.2.7
6.0.2
4.2.5

Could you confirm that you can get data in plugin 4.1.1 and cannot in 4.2.5?

@alexanderzobnin Of course. It happens because the variables $1 $2 $3 etc are no longer supported. It is worth clarifying and the incident can now be closed. Alternatively, direct database connection solves if they can't make such a change

I have this problem in 4.2.10 but dont have in  4.1.1


Deserializing String with Backslashes :(

Hi all, as a personal project, I am trying to develop a tool for a game that I've been playing called Path of Exile. The tool is intended to scrape market data and display currency trade prices. I am a C++ developer by nature but I want to learn a new language and chose Rust for this project.
The first step is to scrape item information to build a list of available items. I've done it for the most part, with one exception. So here is an example of the json object that I want to deserialize:
{                     "id": "exa",                     "text": "Exalted Orb",                     "image": "\/image\/Art\/2DItems\/Currency\/CurrencyAddModToRare.png?v=1745ebafbd533b6f91bccf588ab5efc5" }
I am having trouble deserializing the image value. I am trying to store it into a &str.
It seems like serde is not able to handle escape characters. Can anyone help me with this issue?

The problem here is that due to the escape sequences, serde_json cannot simply hand out a reference to the original string, since the escape sequences need to be removed while deserializing. You can deserialize this into a String or a Cow<'_, str>. You can also apply #[serde(borrow)] to the latter to get zero copy deserialization when possible.
If it has to be zero copy deserialization you can look into in situ parsing for `serde_json. There is an issue and a pull request for it.


[Tools] [Enhancement] Extend dotnet ef scripting

Hi,
I would like to see some extension to the scripting via command line (or PMC for that matter)
dotnet ef migrations revert

Update the database to the previous migrations and apply it dotnet ef database update Migrations-1
Remove the last not applied migrations dotnet ef migrations remove

File extension for additional data
In many of my web projects the DbContext is definied in an assembly different from where the app is hosted, so I tend to write dotnet ef migrations add MyMigration -c MyContext -p ... -o ... very frequently. This is now a custom script, which works fine. I can just dotnetef migrations add MyMigration.
For new people this is something that they would need to learn and get acustom to, and I want it to be as simple as possible to get started and just do "the normal way": dotnet ef migrations add MyMigration.
Perhaps this can be fixed by a file with configurations that can be read (if exists). For example
.ef.config
MyContext: -p ... -o ...
MyOtherContext: -p ... -o ...

dotnet ef migrations squash
If working on a feature branch this would be very useful to creata a single migration from many experimental. Currently I do the "revert" step over and over again.
A lot of stuff here and I will gladly help submitting a PR if someone could point me in the direction where to start; if this is something that the community would like to see.
Otherwise point me in the right direction anyway so that perhaps I can build it as an extension :)
Good work with EF

Some thoughts:
#1972 is about adding a --revert option (or similar) to dotnet ef migrations remove
I think we support response files (or can easily enable it):
dotnet ef migrations add @MyContext.ef.config

#2174 is tracking a squash command.

@joacar Thanks for the suggestions. As @bricelam says above, two of these issues are already being tracked, and I just filed #10409 for ensuring the response files can be used. We would be happy to help you get started if you would like to work on a PR for any of these issues.

@ajcvickers I would be glad to contribute! Perhaps response files I a good starting point and after completion move to tackling the others. I'll move the discussion to the appropriate issue!

@bricelam this is a feature that i would find useful and so i have had a go with the changes and it works as you explained. do you have any guidance on unit testing?
For me I created a project and at the command line ran something like dotnet ./dotnet-ef.dll migrations list @BloggingContext.ef.config. Because the entry point is calling the command line, I am unsure on your preferred approach as to how to achieve this in an automated way (is there an expectation for automated testing at the command line level)? Or is it sufficient for the entry point to just test CommandLineApplication::ExpandResponseFiles().
If you do have any further thoughts and/or guidance on how to approach the unit testing that would be appreciated.


console.log("ky UMD !!!!") in dist code

There's this line in the dist/mailgun.node.js file:
console.log("ky UMD !!!!")
That is outputting "ky UMD !!!!" in the console whenever I send an email. It seems to have appeared in the latest release and I can't seem to find it in the non-dist source files.

I guess this is like this issue
Same as you I only found the code in dist and it appeared with the latest release

This is my bad I forgot to remove debug log before building.
I merged PR with the fix for that.
Please update to v 4.2.3

Thanks for resolving the issue!


mod_suexec 2.4.16 (El Capitan only)

I wonder if the instructions in the caveats can be done on El Cap given the SIP.

I should have checked the open PRs before writing this one. This duplicates #86.


CORS filter should throw when policy is not found

Use [EnableCors("foo")] without defining any policies.
System.ArgumentNullException: Value cannot be null.
Parameter name: policy
   at Microsoft.AspNetCore.Cors.Infrastructure.CorsService.EvaluatePolicy(HttpContext context, CorsPolicy policy)
   at Microsoft.AspNetCore.Mvc.Cors.CorsAuthorizationFilter.<OnAuthorizationAsync>d__9.MoveNext()

We just let it nullref, we should throw a better exception.

Fixed in https://github.com/aspnet/Mvc/commit/0f8542e4b27c1e6dc26f83a18b4bc7c7e050dd9b


fix: improve FetchResponse typing

here's an image explaining how it can provide better typings. Once u make sure there's no error, it'll allow u to safely access the data prop

Hi @brankoconjic , can u review this pr pls?


[org.bluez.Error.Failed] No notify session started

Thanks for the great work you did here!
idasen-controller --move-to 1180
Connected CE:41:99:2E:BA:4D
Height: 1000mm
Moving to height: 1180
Height: 1004mm Speed: 29mm/s
Height: 1016mm Speed: 33mm/s
Height: 1030mm Speed: 38mm/s
Height: 1044mm Speed: 38mm/s
Height: 1059mm Speed: 39mm/s
Height: 1073mm Speed: 39mm/s
Height: 1086mm Speed: 39mm/s
Height: 1100mm Speed: 39mm/s
Height: 1114mm Speed: 40mm/s
Height: 1127mm Speed: 39mm/s
Height: 1142mm Speed: 39mm/s
Height: 1156mm Speed: 41mm/s
Height: 1170mm Speed: 39mm/s
Height: 1180mm Speed:  0mm/s

Something unexpected went wrong:
[org.bluez.Error.Failed] No notify session started
Disconnected

Do you know why I get this error message?

What device are you using?

I'm using a Minix Neo z83-4  and the IKEA IDÅSEN Desk.

I think this is a duplicate issue to https://github.com/rhyst/idasen-controller/issues/46


TF_SelectV2Op gets legalized to TFL_SelectOp

1. System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 22.04
TensorFlow installation (pip package or built from source): pip package
TensorFlow library (version, if pip package or github SHA, if built from source): v2.17.0

2. Code
tf.where(condition, x, y)
3. Failure after conversion
The model cannot run on TFLite Micro, as it doesn't support the old SELECT op, only the new SELECT_V2 one.
5. (optional) Any other info / logs
The change was introduced 5 years ago by @abattery to improve compatibility with the older runtimes: https://github.com/tensorflow/tensorflow/commit/061d2e0a0d998623a2b0f191038c0aa918a08027
But now it breaks compatibility with TFLite Micro, which only supports the newer op.
Here's the legalization in question: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/compiler/mlir/lite/transforms/legalize_patterns.td#L302
UPD: I believe that https://github.com/google-ai-edge/ai-edge-torch/issues/93 is basically the same.

This issue originally reported by @tagunil has been moved to this dedicated repository for ai-edge-torch to enhance issue tracking and prioritization. To ensure continuity, we have created this new issue on your behalf.
We appreciate your understanding and look forward to your continued involvement.


fixed group by int16 and Date types on AMD EPYC 7401P machine

There is sever performance degradation on AMD EPYC 7401P  based systems. Every query with grouping by int16 or Date type becomes very slow (see: https://github.com/yandex/ClickHouse/issues/3490).

Yes, really strange.
For this hash table, end() is just buf + 65536.
Also it's strange that it is calculated on every interation.
I have a testing server on AMD EPYC and I will try to reproduce.

I have successfully reproduced this issue.

I have no sudo on the server with AMD EPYC, will wait...

It would be great to find out the root cause

I have merged this PR, but we need to investigate further, this is TODO.


Hotfix/include favicons in bundle

Includes favicon icons in the main bundle.
Uses better favicon for Espoo.

[ ] There is a typo in the commit name.


CI prep & transfer ownership to pactflow org

[x] Setup CI Pipeline for testing
[x] Setup CI Pipeline for publishing
[x] Transfer ownership of repo to pact-foundation
[ ] Publish from npm pactflow org/scope
[x] rename to pact-msw-adapter

Tracking work via https://github.com/pactflow/roadmap/issues/63#issuecomment-1062353575

Now published as https://www.npmjs.com/package/@pactflow/pact-msw-adapter
msw-pact package marked as deprecated
https://www.npmjs.com/package/msw-pact


Update tutorial-two-python.md to use python f strings

@tatzati Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@pivotal-cla this is an obvious fix

@tatzati This Pull Request contains an obvious fix. Signing the Contributor License Agreement is not necessary.


Dscheck meets lockfree

As in the title; integrate lockfree with dscheck, which is now in opam.
Includes tests for:

spsc queue
mpsc queue
ws deque

Thanks for the PR !
I don't think it is alright to have an indirection for the  Atomic library for anything else than testing. Maybe you could wrap the Atomic library as a virtual library with the default implementation being the stdlib one ?

Thanks ! Great work !


PopOS/Ubuntu installation

I wa able to get this project working on an old PopOS machine that can barely run the Cuda work. Thought I would share the instructions on how I did it. Its a slight variation of the Linux install instructions:
sudo apt install nvidia-cuda-toolkit is the biggest change. Makes it easy to pull in for pop.
#install dependencies
sudo apt install espeak-ng ffmpeg nvidia-cuda-toolkit
#clone the repo
git clone https://github.com/aedocw/epub2tts
cd epub2tts
python3 -v venv venv
source venv/bin/activate
pip install .

Some distros like to default to py2 still. using the venv makes sure the install uses py3 and stays self contained. So I added:
(Optional)
python3 -v venv venv
source venv/bin/activate
pip install .

Im not sure if you want to add it to the repo or not, but just wanted to share! Thanks again for the library!

Thanks! I did mention the CUDA toolkit, but it was in a note regarding deepspeed. This was a good suggestion so I added it as an optional step in the linux install instructions.


[Microbatch] Update default make_temp_relation macro to incorporate a batch specific identifier if available

Desired Improvement
Microbatch batches have been improved in core such that they may be run concurrently. When a batch is executed, the necessary data is first moved into a temp_relation in the data warehouse. The path for this temp_relation is <resource_identifier>__dbt_tmp. As it currently stands, the <resource_identifier>__dbt_tmp will be the same for each batch of a given microbatch model. If the batches are run concurrently, they may end up clobbering the temp_relation destination, which may lead to some wonkiness. As such, we need a way to ensure that each batch for a microbatch model gets a unique temp_relation path.
Helpful Prior Art
Similar to dbt-postgres: https://github.com/dbt-labs/dbt-postgres/blob/ae48e67dae6c1b00cda37ee9bdc61d3330506638/dbt/include/postgres/macros/adapters.sql#L149-L152

Hello,
what a shame that I didn't find this issue before learning how the source code works, and found that my problem could be solved by https://github.com/dbt-labs/dbt-adapters/pull/361. I was currently starting the same PR.
At least, I've learned a lot and waiting to this release.
However, let me give you a little more context, because this solves my issue, but it's not related to microbatches. I'm currently implementing dbt with Airflow, and we are used to having multiples runs to ingest data in different partitions of BigQuery table.
Thus, having a dbt model model_A, materialized as incremental with insert_overwrite strategy, launching multiples runs, let's say D-2 and D-1, for different partitions, will create a conflict with model_A__dbt_tmp table. And the dbt-bigquery don't leverage this situation and relies on the make_temp_relation on dbt-adapters. So, it's the exact same situation as microbatch but on a less granular scope.
You'll probably know and understand better than me, but I wanted to share my situation.


refactor(diagnostics): configure miette properly and remove customization code

This is also an effort to remove 0.5s of terminal checking system calls across all threads.
To fully remove all system calls that check the terminal, these 2 PRs are required:

https://github.com/zkat/miette/pull/325
https://github.com/zkat/miette/pull/326

My customization changed the title color to yellow, this PR reverted that

https://github.com/oxc-project/oxc/blob/5b2696b71123c8ab289e7d9e95b619d5dc2c8333/crates/oxc_diagnostics/src/graphic_reporter.rs#L205-L207
Not achievable.


Add info when disk is too small

@jichenjc I think you want to update zthin-parts/zthin/bin/unpackdiskimage, which is guest deploy using

@jichenjc I think you want to update zthin-parts/zthin/bin/unpackdiskimage, which is guest deploy using

@bjhuangr I think I already updated the file you pointed out

@bjhuangr I think I already updated the file you pointed out


release: v3.15.6

[v3.15.6] (Oct 11th, 2024)
Features:

Exported useLocalization Hook:

Provided access to stringSet and dateLocale.
Note: Required SendbirdProvider to wrap your component for proper usage.
Import Path: "@sendbird/uikit-react/hooks/useLocalization"

Exported ThreadReplySelectType:

Import Paths:

"@sendbird/uikit-react/Channel/context"
"@sendbird/uikit-react/GroupChannel/context"

Fixes

Modified the MessageInput to scroll to the caret position when pasting text.
The maximum height of the MessageInput has been extended to '92px'
Fixed an error message on MenuItemAction when the children prop is undefined

/bot create ticket

[Creating Ticket] 🔖 Done https://sendbird.atlassian.net/browse/SDKRLSD-1433


Invert colors

Is it possible to invert the colors?

This is currentlt hard-coded inside the OnelinerKit Framework (https://github.com/kimar/OnelinerKit/blob/master/OnelinerKit/View/OnelinerView.swift#L53) but I think it would make sense to abstract this in the framework and implement Settings in the ScreenSaver.

I have implemented a way to alter colors in OnelinerKit, now the next step would be to properly implement this in DeveloperExcuses, here's an example with two different, hardcoded, colors: https://github.com/kimar/DeveloperExcuses/tree/colorsExample

Never did anything with Swift. How can I compile it?

I did those changes, hit Build and then replace current screen saver with compiled version in:
Library ▸ Developer ▸ Xcode ▸ DerivedData ▸ DeveloperExcuses-fxfzocpddjkyofbcqccparpelguv ▸ DeveloperExcuses.saver
Still no changes. I'm I doing something wrong?

Can you try uninstalling the currently installed one first? (Using Settings -> Screensaver). Might be cached. Usually the changes should show up, did you check everything looks correct using the build in Debug View?

I tried to uninstall it first but still no luck. No compile errors that I'm aware of.


[feature] Markup / Price equations for cryptocurrency listings

Sorry if this is a duplicate. Currently you can sell cryptocurrency only for its market value. I don't think this is motivating enough for merchants to do so
Merchants should be able to add fixed or percentage markup to be able to make profit and competition between merchants.
See how it works on localbitcoins.com: https://localbitcoins.com/guides/equation-howto/

The current cryptocurrency listing feature is very much a minimal implementation so we can experiment with it. We expect to iterate on it and add features like a markup once we have some feedback (like this issue).

I'm closing this issue, we are tracking the requirements for a markup feature in #1371


Duo icon request

Type
Icon request
Info
Duo icon request
Icon(s)

#313

All issues are temporarily on hold. Please refer to #316 for more info.

Hey, this icon has been added in the new-standards branch and will be merged once it is done!
https://github.com/walkxcode/dashboard-icons/blob/new-standards/png/duo.png
https://github.com/walkxcode/dashboard-icons/blob/new-standards/svg/duo.svg


[HACKTOBERFEST 2024] - Relational Databases Quiz

[!IMPORTANT]
This issue is part of our 2024 Hacktoberfest initiative. If you are interested in working on this issue, refer to our top-level tasks to see if this issue is claimed, or to claim it if it is not.

This issue is to create the Relational Databases quiz.
The file you should be working on is found in /curriculum/challenges/english/25-front-end-development/quiz-relational-databases.
All quiz questions need to relate to one of these topics:

What is a relational database
How does it differ from a non-relational database
One of the courses before this quiz is located here. Any commands or topics covered in that course can be used in the quiz. Here's a partial list: psql shortcut commands (\l, \c, \d), CREATE DATABASE, CREATE TABLE, ALTER TABLE, ADD COLUMN, INT, VARCHAR, DROP COLUMN, RENAME COLUMN, inserting data, basic select queries, deleting and updating data, primary and foreign keys, 1-1 1-m m-m relationships

[!CAUTION]
Questions which do not fall under these topics will be rejected.

You are welcome to include code blocks in your questions, but please keep them short (four lines or less).
Please do NOT open a pull request until you have completed all questions. Your quiz should have exactly 20 questions.

Thank you for your interest in contributing. This issue will be opened for contribution when Hacktoberfest starts on October 1st.

[!CAUTION]
Pull requests which are created before October 1st will not be eligible for Hacktoberfest. We appreciate enthusiasm, but encourage you to hold off on contributing to this issue until the event has begun.

If you wish to be notified when this issue is opened for contribution, subscribe to notifications:

This issue is now open
If you would like to work on this issue, please leave a comment so we can assign it to you.
Be sure to read our contributing guidelines.

@naomi-lgbt Can you assign this issue to me?

Hello,I would like to work on this issue.@naomi-lgbt

I would like to work on this

I would like to express my interest in taking on the responsibility for creating the Relational Databases quiz, as outlined. Please assign this task to me at your earliest convenience.

Hi, I wasn't aware that we needed to be assigned to an issue before working on it, so I went ahead and created a pull request. Could you please assign this issue to me?
Thanks!

This issue has been assigned a contributor. To prevent extraneous notifications, the issue is now locked. If you have any questions, please reach out to me in our Discord community.


How to set mask for input?

I wanna mask the input to set date or time. for example for date: ----/--/-- and for time: --:--

You can render an input with the ability to mask for your date picker:
https://codesandbox.io/s/gallant-butterfly-2mzlf?file=/src/App.js

You can render an input with the ability to mask for your date picker:
https://codesandbox.io/s/gallant-butterfly-2mzlf?file=/src/App.js

I am using Material ui Filled Input component and when i am using this third party library for masking input it destroys the filled variant styles of material ui FilledInput.

I forked this example from the Material UI documentation so that its input can be rendered in the DatePicker.
Please see it and let me know if you have any problems.
Material demo (forked):
https://codesandbox.io/s/material-demo-forked-k9xin?file=/demo.js

I forked this example from the Material UI documentation so that its input can be rendered in the DatePicker.
Please see it and let me know if you have any problems.
Material demo (forked):
https://codesandbox.io/s/material-demo-forked-k9xin?file=/demo.js

Thanks. it works great ✅

You're welcome.


[BCS classes] Restricting generics in BCS function arg classes to using entry function types only. Added helper factory methods and documentation too

Restricting generics in BCS function arg classes to using entry function types only..
Adding factory methods for MoveObjects and MoveVectors with unit tests & documentation.
Test Plan
pnpm jest

why do we do that?


doc: twister: ztest: Add test application diagram

Add a diagram to illustrate a test application's project components with relationships between Ztest and Twister objects.
To help resolve #74151 together with #74669
The proposed diagram - https://builds.zephyrproject.io/zephyr/pr/74834/docs/develop/test/twister.html#id1

It'd be nicer if the diagram cares dark mode as well.

It'd be nicer if the diagram cares dark mode as well.

hmm, Chrome dark theme shows the same on the page white background

This is what I got on my Chrome Version 126.0.6478.114 (Official Build) (64-bit) with the sun-moon toggle button at the top right corner of the page for the dark mode.

It'd be nicer if the diagram cares dark mode as well.

@yashi, the diagram adjusted.

some comments:

The test-identifier and test project group is not clear and conflicts with existing terminology
Do not use Test case for the test application, this is the source of all confusion and we shall not repeat this in the diagram.
Need to should 1..n possibility for scenarios, suites and test cases
Need to show that in twister, a test instance is a match between a scenario and a target platform, this is not immediately visible in the diagram right now. Matching a scenario to a platform in twister is the core functionality of twister, everything else and terminology used in there for suites and cases should be considered internal and should not be mixed up with how the actual test code and test structure.

@nashif, your comments should be addressed, please review again.

@nashif, do you any comments on the updated diagram ?

@nashif, do you any comments on the updated diagram ?

sorry, missed that.  lgtm.

@nashif General note: I think we added a new confusion to the picture :) TL;DR: Now we have a configuration keyword used in different contexts.
When we were talking about terminology we decided that test configuration (in docs) == test instance (in code) i.e. a combination of a scenario and a platform. With recent changes in docs, reflected in Dmitrii's diagram, configuration is used to refer to the testcase/sample.yaml. This can have more meaning, since those yamls describes how to configure your tests/builds but this is not how it was used. From quick scan of twister docs it seems the configuration is no longer used in the instance meaning there, that's good. However, the instance meaning is still used in the twister's summary, (e.g. 10 of 20 test configurations passed etc.) so this has to be addressed. And most likely this section https://docs.zephyrproject.org/latest/develop/test/twister.html#test-configuration will cause confusion now, since both configurations refers to yaml files (testcase.yaml and test_config.yaml). Maybe we should discuss the terminology again before further fixes, because it can end up in a whack-a-mole activity.

Need to show that in twister, a test instance is a match between a scenario and a target platform, this is not immediately visible in the diagram right now.

I think this was not addressed but I don't know how to show this on such diagram... maybe in next iteration we would figure this out


Scheduling

In the "Supported Labels", there is a line:
karpenter.k8s.aws/instance-cpu | 32 | [AWS Specific] Number of CPUs on the instance
It is unclear whether the "instance-cpu" is Hardware CPUs or vCPUs on HT enabled instances.  vCPUs is the more useful value and looking at the source in "instancetype.go", it does appear to be vCPUs.  Making this explicitly say "Number of vCPUs on the instance" would be clearer.

Hey @ksquaredkey ,
I'm interpreting "CPU" as a generic term to convey the default number of CPU cores visible to the OS (and then reported by Kubelet).  By using "CPU", it covers both virtual and bare metal instance types.  Although, the ec2 API seems to provide a vCPU count for bare metal instances too.
Is this something that is impacting your use of Karpenter?  Or just looking to make docs more accurate?

Just trying to make the docs more accurately reflect what AWS is calling at the API level of the the DescribeInstanceTypes in the vCpuInfo.  Specifically, I do NOT want Cores and by explicitly calling it vCPU it helps avoid the conflation of "CPU" with "Core" that happens, especially with folks used to non-HT processors (I know a lot of old CompSci farts because I am an old CompSci fart...)
In my particular case, I want to a minimum of "*.4xlarge" and my containers work on both Graviton2 and x86_64.  We can't use the "Gt" operator on "karpenter.k8s.aws/instance-size" and since I want to make sure I get the correct minimum vCPUs using "karpenter.k8s.aws/instance-cpu", I went to the source to confirm that "instance-cpu" was using the vCPU and not Core from the vCpuinfo that I am used to see in DescribeInstanceTypes.  By explicitly calling out vCPU in the doc, it eliminates the risk of the "assume" and saves other folks going "Hmm..." and digging in the source.
I'll admit, minor nit and debatable.  It's just that I went through the above exercise and that "Create documentation issue" link was right there conveniently on the page, so I thought I might save other folks the same trip.

I understand.  It does make sense to align the terminology with that of the EC2 API.  And it is a very quick change.


Swiper/vue RTL To LTR issue

LTR TO RTL BUG

[x] I confirm

Reproduction link
https://codesandbox.io/s/funny-water-ddz3lk?file=/src/App.vue
Bug description
when i change rtl to ltr slider not working properly.
Expected Behavior
Need to update slider as per direction or else give some method for reinit so we can reinit manually.
Actual Behavior
LTR to RTL swiper not updated.
Swiper version
8.1.4
Platform/Target and Browser Versions
chrome
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

I am also facing the same issue in next js

Have the same issue, any suggestion?

Have the same issue, any suggestion?
By simply removing the :dir="rtl ? 'rtl' : 'ltr'" line from swiper the code works correctly! but in my case, I had to add dir attr to make it work 🤦♂

There is a changeLanguageDirection method for this issue which helps, but still it doesn't calculate the positions correctly. Any news?

Issue is closed because of outdated/irrelevant/not actual/needed more information/inactivity.
If this issue is still actual and reproducible for latest version of Swiper, please create new issue and fill the issue template correctly:

Clearly describe the issue including steps to reproduce when it is a bug.
Make sure you fill in the earliest version that you know has the issue.
Provide live link or JSFiddle/Codepen or website with issue


Frontend (client-mall): Homepage Skeleton

Homepage

Product Card (Done and Responsive)
Product List (Done and Responsive
Sub-page for each product id: description and category (In progress)
Filter: Search by product name and search by product category (In progress)

Done


OSX workers

Currently, Strider seems to be coupled with Docker for adding separate worker machines.
The use case we have is - we need to be able to run iOS / Xcode jobs on separate workers,
decoupled from the webapp machine.
Use case
Running iOS jobs on workers
Docker
While being a great solution for containing apps, Docker doesn't run natively on OSX, because containers.
 Thus, ideally all the complex software should be managed by the master webapp. Maybe using SSH vs webapp/sockets would do the job.
We don't have problem deploying the webapp on a Linux box using Docker, as long as it's able to talk with non-docker workers.
At the end of the day, it should be as easy as possible to add and maintain the workers (no manual maintenance if possible)

@keyvanfatehi what about Windows?
I want to use strider in windows native app. I need a runner (strider-windows-runner), which can build & test windows native app. Something like buildbot slave do.

@zemug im not familiar with buildbot, but it sounds similar to strider in many ways (very modular, user-tailored cicd solution) but written in python. what makes you want to use strider rather than buildbot?
for the record I think that a solution such as this should not really be based on ssh, but rather needs a remote-slave concept to work best.

@keyvanfatehi I can't install buildbot,  due to sqlalchemy-migrate break with sqlalchemy which buildbot depend on.
I have to due with svn & git, and build in windows, I think I should try install buildbot.

@zemug hmm, sounds like something they would be able to address via their issue tracker more quickly than we would be able to address by adding the desired functionality to strider. That said, I think we'll have this feature eventually, someone just has to want it badly enough to make a runner plugin. @jaredly may have some suggestions (and code) in case you want to take this on. Currently the closest example I know of is https://github.com/Strider-CD/strider-docker-runner -- it would be cool to have a cross-platform "docker server" which would implement just the server portion yet be able to spawn and control processes via JSON ... essentially this is the basis of the build slave: supporting the subset of features the docker runner expects of the docker server, but without actually using docker

@keyvanfatehi docker isn't supported by OSX, so the closest you can get is a "vagrant server".
I think this shouldn't be coupled with anything than a SSH connection


disable "All day"  row

Hi,
thank you for this library !
i want disable the display of the line "all day", how can i do pls ?
And i have a problem with the view. I can't disable two view (day and aganda)...

you can pass views property to the BigCalendar component
<BigCalendar
                        events={events}
                        views={['week', 'day']}
                        defaultView={'week'}
...

Thank you but i want disable the row "All day", is that possible ?

its not currently possible to disable the all day view, in part because there would be no way of showing events that span multiple days (even if they aren't marked all day), as @mawek points out you can adjust the vies you want with the views prop

Is there a way of currently removing this line? Maybe with css?

Yes, I have sucessfully done it but not with css (it's not possible because that line have a dependency). You can fork this lib and just comment the code that does this. (And why not create a parameter for enable/disable that line). Good luck !

Yeah that's what I had in mind, thanks! (:

Did it with CSS! Boom!

.rbc-time-view .rbc-row {
    min-height: 0px;
}

.rbc-time-view .rbc-row div:nth-child(1) {
    height: 0px !important;
}

@mcmatan you the real mvp

For anyone else looking to use @mcmatan's solution, you can use that and set the allDay message to '': http://intljusticemission.github.io/react-big-calendar/examples/index.html#prop-messages

I went with
.rbc-row:nth-of-type(2) {
    display: none !important;
}

Anything wrong with that?

Using version 0.16.1, I found this worked:
.rbc-time-header > .rbc-row:nth-of-type(2) {
    display: none !important;
}

This got rid of the 'all day' row in week and day views. Anything wrong with this fix?

I used
.rbc-allday-cell {
  display: none;
}
.rbc-time-view .rbc-header {
  border-bottom: none;
}

anything wrong with this (as far as CSS hacks go)?
It would still be nice to disable the allday row altogether. I wonder if a PR that added an option for disabling the allday row, instead opting to display multi-day events with a note (i.e. "cont'd on next day) or an arrow pointing into the next/previous day, would be accepted? Maybe that's a more complex solution than most people need, but currently I have data that will just not be shown because the event would technically be an All Day event.

ya'll you can disable the allday row by setting http://intljusticemission.github.io/react-big-calendar/examples/index.html#prop-showMultiDayTimes

@jquense Hi Jason, I'm trying to disable the allday row using showMultiDayTimes and not getting it. Here's a basic example where specifying showMultiDayTimes is expected to make the allday row disappear. Can you let me know where I'm going wrong?
https://codesandbox.io/s/3q8mrk9l7q

Is there any new development? @jquense suggested solution does not work for me either.
It basically seems feasible, the first Basic example shows that.

I ended up doing it via CSS mentioned by @drewandrew.

I'm using  @drewandrew's CSS and noticed that when using the resourceGroupingLayout there was some extra space underneath the resource titles.
I've added this style to remove it:
.rbc-time-view .rbc-row {
    min-height: unset;
}

Default Min Height
Unset Min Height


Wrong import on generated file

I am interested in helping provide a fix!
Yes
Which generators are impacted?

[ ] All
[ ] Angular
[ ] HTML
[X] Qwik
[X] React
[ ] React-Native
[ ] Solid
[ ] Stencil
[ ] Svelte
[ ] Vue
[ ] Web components

Reproduction case
https://codesandbox.io/s/dazzling-panka-9d6jm2?file=/output/qwik/src/20221010-1/index.ts
Expected Behaviour
Importing a component file (.lite) on a non-component file, generates a file which contains a wrong extension (.jsx).
source index.ts
import ChildComponent from "./ChildComponent.lite";
import ParentComponent from "./ParentComponent.lite";

export { ChildComponent, ParentComponent };

What is supposed to be generated is an index.ts file like:
import ChildComponent from "./ChildComponent";
import ParentComponent from "./ParentComponent";

export { ChildComponent, ParentComponent };

Notes:
This won't happen inside a component file, where the import is as expected.
Prerequisite: Mitosis with TS output:
module.exports = {
  files: "src/**/*",
  options: {
    qwik: {
      typescript: true
    },
    react: {
      typescript: true
    }
  },
  targets: ["react", "qwik"]
};

Actual Behaviour
generated index.ts
import ChildComponent from "./ChildComponent.jsx";
import ParentComponent from "./ParentComponent.jsx";

export { ChildComponent, ParentComponent };

Additional Information
I believe the problem is genereted by the logic on extensions helper

Wrote a simple script as a stopgap for the time being.  I run it after every mitosis build.
// see: https://github.com/BuilderIO/mitosis/issues/809
import {readdir, readFile, writeFile} from "fs/promises"
import path from "path"

async function resolveExports(dir: string): Promise<any> {
  const files = await readdir(dir, {withFileTypes: true})
  return Promise.all(
    files.map(async (file) => {
      if (file.isDirectory()) {
        return resolveExports(path.join(dir, file.name))
      } else if (file.name === "index.ts") {
        const filePath = path.join(dir, file.name)
        const contents = await readFile(filePath, {
          encoding: "utf-8",
        })
        return writeFile(filePath, contents.replaceAll('.lite"', '"'), {
          encoding: "utf-8",
        })
      }
    }),
  )
}

resolveExports(path.resolve(__dirname, "../packages/react/src/generated/src"))

I don't see the bug when I go to https://codesandbox.io/s/dazzling-panka-9d6jm2?file=/output/qwik/src/20221010-1/index.ts
The output in Qwik's and React's index.ts is:
import ChildComponent from "./ChildComponent.jsx";
import ParentComponent from "./ParentComponent.jsx";

export { ChildComponent, ParentComponent };

Providing an explicit .jsx extension when the file is .tsx is valid, and in fact recommended for your code to be ESM compliant:

ESM spec requires explicit extensions: https://nodejs.org/api/esm.html#mandatory-file-extensions
TypeScript requires that you use .jsx when pointing to a .tsx file, and .js when pointing to a .ts file. TS does not accept .ts and .tsx extensions in paths by default.

https://www.typescriptlang.org/docs/handbook/esm-node.html#type-in-packagejson-and-new-extensions
https://bobbyhadz.com/blog/typescript-import-path-cannot-end-with-ts-extension

Combining the above two facts means that generating an import pointing to ChildComponent.jsx is the correct thing to do.


badssl docs in two places

there is now backends/badssl.md and backends/badssl/README.md, should be reduced to one.

Solved: ce90f08


DFS of Graph

❗Write Code in Only One Language ( CPP , C , Java , Python )
Give File Name :  DFSGraph  ✅ In respective language folder
📑 DESCRIPTION
DFS of Graph

You are given a connected undirected graph. Perform a Depth First Traversal of the graph.
Example 1:
Input: V = 5 , adj = [[2,3,1] , [0], [0,4], [0], [2]]
Output: 0 2 4 3 1
Explanation:
0 is connected to 2, 3, 1.
1 is connected to 0.
2 is connected to 0 and 4.
3 is connected to 0.
4 is connected to 2.
so starting from 0, it will go to 2 then 4,
and then 3 and 1.
Thus dfs will be 0 2 4 3 1.

Example 2:
Input: V = 4, adj = [[1,3], [2,0], [1], [0]]
Output: 0 1 2 3
Explanation:
0 is connected to 1 , 3.
1 is connected to 0, 2.
2 is connected to 1.
3 is connected to 0.
so starting from 0, it will go to 1 then 2
then back to 0 then 0 to 3
thus dfs will be 0 1 2 3.

Constraints:
1 ≤ V, E ≤ 104
- Only one valid answer exists.

Follow-up: Can you come up with an algorithm that is less than O(n^2) time complexity?

please assign this to me

Can you assign this to me

assigned to @SayaliMarathe-13


Update the project README

Description
The training and style guide links in the README are out of date.
These should be updated once the training and style guide are back online.

Won't fix because this repo will be deprecated.


Fix the tests on circleci

Increase babel-jest version that triggers the upgrade of babel to babel-core.
Upgrade of grunt dependencies
remove some useless grunt dependencies

No more vulnerabilities for the grunt packages
We now test the build of windows and mac on circle ci 2.0


add plan_id label in reconciliation_status metric

Implement task https://github.tools.sap/kyma/backlog/issues/2412  which needs to add global_accountid for distinguish the trial skr or real customer.

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

/retest

/retest

/retest

/retest

/retest

/ok-to-test

/retest

/test pre-main-reconciler-cli-integration-kyma-main-k3d

/test pre-main-reconciler-cli-integration-kyma-main-k3d

/retest

/retest

/retest

/retest

/test pre-main-reconciler-cli-integration-kyma-main-k3d

/test pre-main-reconciler-cli-integration-kyma-main-k3d

/ok-to-test

/test pre-main-reconciler-cli-integration-kyma-main-k3d

/retest

/ok-to-test

/retest

/retest

/retest

/restest

/retest

/retest

/retest

/cla-recheck

/retest

/retest

/retest


Add pilot config version

Add a gauge to track k8s resource version for Pilot CRDs. This is useful to track configuration changes overtime and roughly correlate them with other traffic metrics.
Example output of four changes to the details-default RouteRule.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: ayj
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS [ayj]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

cc @douglas-reid @gargnupur

@ayj: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
7ac0f6e35a1120462ae0d9a0036dce7362926a23
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Also: maybe an option would be to collect just the last resource version per config type - not one metric per object. My concern is that this can impact scalability and increase memory usage. But having a flag will allow A/B testing and disabling if we find it has any impact.

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
7ac0f6e35a1120462ae0d9a0036dce7362926a23
link
/test istio-unit-tests

prow/istio-presubmit.sh
7ac0f6e35a1120462ae0d9a0036dce7362926a23
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

I'm a bit concerned with the costs and scalability of this - can you at least add a flag, and add info about memory impact of this on a medium-size cluster ? How will prometheus memory use be affected ?

The number of gauges should roughly scale in proportion to the number of services (not endpoints). I tweaked the update/delete path to remote the old resource metric instance instead of setting the value to zero. Pilot only exports the most recent version of object instead of the full history. This should prevent unbounded memory growth in Pilot. The resulting graph is equally usable (see below).

I'm not that familiar with memory usage and scaling in Prometheus itself.I did find documention on selective deleting time series by labels / time ranges which might be applicable over time (see https://prometheus.io/docs/prometheus/latest/querying/api/#delete-series). cc @douglas-reid on additional guidance / best-practices w.r.t memory usage.
I also added the K8S_RESOURCE_VERSIONS_METRIC_DISABLED environment variable to disable the metric to enable A/B testing.

As implementation - I would rather not do it on each object update, but maybe before a push ? If you move this to be 'before a push' - please also add a small metric on the time it takes to update this metric :-)

Pilot doesn't retain previous resource versions in its config store. Therefore, we don't have sufficient information during a push to delete the previous resource version metric.

Note that we're planning to do some indexing and caching before the push - and likely to include the combined version in the envoy version we push - so having the code there would make sense for other reasons.

Including combined version info in envoy version_info would be really useful. Do you have any docs on your plans to handle this?

@ayj: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
cffa56126ed3c916fe7afbd56e1da5440dd124de
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
cffa56126ed3c916fe7afbd56e1da5440dd124de
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
cffa56126ed3c916fe7afbd56e1da5440dd124de
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
cffa56126ed3c916fe7afbd56e1da5440dd124de
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
cffa56126ed3c916fe7afbd56e1da5440dd124de
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
cffa56126ed3c916fe7afbd56e1da5440dd124de
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
cffa56126ed3c916fe7afbd56e1da5440dd124de
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
cffa56126ed3c916fe7afbd56e1da5440dd124de
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
cffa56126ed3c916fe7afbd56e1da5440dd124de
link
/test e2e-bookInfo

prow/e2e-bookInfoTests-v1alpha3.sh
cffa56126ed3c916fe7afbd56e1da5440dd124de
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
cffa56126ed3c916fe7afbd56e1da5440dd124de
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
cffa56126ed3c916fe7afbd56e1da5440dd124de
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
cffa56126ed3c916fe7afbd56e1da5440dd124de
link
/test e2e-bookInfo

prow/e2e-bookInfoTests-v1alpha3.sh
cffa56126ed3c916fe7afbd56e1da5440dd124de
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
cffa56126ed3c916fe7afbd56e1da5440dd124de
link
/test e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

I'm still quite uncomfortable with the risks of impacting scalability - we had enough troubles with this,
and it is not clear what kind of testing would allow us to have confidence this PR doesn't create more
problems than it solves. Prometheus is a time-series database - what is the use case for tracking the time  when each individual resource change in a graph ? Is it the appropriate system for this ?
How about doing this experiment in galley, since it would add less risk for 1.0 ?

what is the use case for tracking the time when each individual resource change in a graph ? Is it the appropriate system for this?

The use case was correlating user authored config changes with potentially affected traffic patterns.
I filtered out ServiceEntry from the metrics. Metrics should only be reported for user authored config.

Why don't you just enable this in galley - and after we test galley for
scalability we add it to pilot as well
(actually - it may not be needed at all in pilot, users who need this
metrics could use galley if it proven to work).
On Thu, Jun 7, 2018 at 12:13 PM, Jason Young<EMAIL_ADDRESS>wrote:

what is the use case for tracking the time when each individual resource
change in a graph ? Is it the appropriate system for this?
The use case was correlating user authored config changes with potentially
affected traffic patterns.
I filtered out ServiceEntry from the metrics. Metrics should only be
reported for user authored config.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/5893#issuecomment-395533198, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAFI6qOQxDLoI1HU6iygftT5xx1hFKZoks5t6XtggaJpZM4USLBh
.

To be clear: still not convinced Prometheus is the right system to use for
this feature.
On Thu, Jun 7, 2018 at 1:43 PM, Costin Manolache<EMAIL_ADDRESS>wrote:

Why don't you just enable this in galley - and after we test galley for
scalability we add it to pilot as well
(actually - it may not be needed at all in pilot, users who need this
metrics could use galley if it proven to work).
On Thu, Jun 7, 2018 at 12:13 PM, Jason Young<EMAIL_ADDRESS>wrote:

what is the use case for tracking the time when each individual resource
change in a graph ? Is it the appropriate system for this?
The use case was correlating user authored config changes with
potentially affected traffic patterns.
I filtered out ServiceEntry from the metrics. Metrics should only be
reported for user authored config.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/5893#issuecomment-395533198, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAFI6qOQxDLoI1HU6iygftT5xx1hFKZoks5t6XtggaJpZM4USLBh
.


[Proposal]: Data binding annotations for custom and actual names in Ballerina fields and resource/remote parameters

Updated with review : 2024/09/02
Summary
This proposal suggests adding annotation features to improve Ballerina’s usability and compatibility with modern web standards. Seamless JSON serialization and deserialization are crucial for its adoption in modern software development, especially for web APIs and services.
Goals

Add annotation features to Ballerina for better usability and compatibility with modern web standards, facilitating clear and maintainable code for web APIs and services.

Motivation
[1] Referring to the OAS sample, since this annotation is required to be part of this implementation https://github.com/ballerina-platform/ballerina-library/issues/6867
openapi: "3.0.0"
info:
  version: v3
  title: Karbon API 3.0
servers:
  - url: http://localhost:9090/v1
paths:
  /customer/groups:
    get:
      …
      parameters:
        - name: "customer-group" \\query param
          in: query
          schema:
            type: string
      responses:
        '200':
          description: successful
          content:
            "application/json":
              schema:
                $ref: "#/components/schemas/Person"
components:
  schemas:
   Person
      type: object
      required:
         - full-name
         - last-name
         - table
      properties:
        full-name:  \\property-name
          type: string
        last-name:  \\property-name
          type: string
        age:
          type: integer
        table:
          type: string

In the above OAS example, it has REST API  get with query parameter name, customer-group which is not aligned with Ballerina naming conventions. when we writing the ballerina code we were supposed to use escape for the query parameter name. ex: customer\-group
[2] Referring to the JSON sample
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "title": "Person",
  "type": "object",
  "properties": {
    "first-name": {
      "type": "string",
    },
    "last-name": {
      "type": "string",
    },
    "age": {
      "type": "integer"
    },
    "table": {
      "type": "string"
    }
  "required": ["first-name", "last-name", "table"]
}

Given JSON sample[2] has fields with names "full-name", "last-name" and "table", which are not aligned with Ballerina naming conventions. In addition to that some scenarios can have a ballerina reserved key as a field name like table.
Therefore if the user needs to use this JSON in the Ballerina record we have to escape special characters like the below way
type Person record {
    string full\-name;
    string last\-name;
    string 'table;
    int age?;
}

However, when using this generated record and the query parameters, users may face code readability issues. The escaped characters can make the code harder to read and understand, leading to confusion and potential mistakes during development.
Description
Through this proposal, we are suggesting having an annotation for users to override the record field name according to the preferred name.
Proposed designed
Annotation field for parameters
We propose introducing a new annotating field @http:Query parameters with metadata. The field will be specified using a syntax similar to the following:
public type HttpQuery record {|
   string name?;
|}

This HttpQuery annotation has one field for storing that parameter name.
Annotation for record fields
We propose introducing a new syntax for annotating record fields with JSON metadata. The annotations will be specified using a syntax similar to the following:
public type HttpRecordField record {|
   string name?;
|}

const annotation HttpRecordField Field on record field;

This RecordField annotation enriches name for the given record field name. The field format for the media for serialization which is optional can be added later.
This suggested approach will,

Improved Interoperability: Enhances the Ballerina's ability to work with external systems and APIs that use JSON.
Allow users to define custom names for fields when they are serialized to JSON

type Person record {
        @http:Field {| name: "age"|}
	int personAge;
}

Cleaner Code: Reduces the need for manual JSON manipulation, leading to more maintainable and readable code.
Handling Reserved Words and Unconventional Names
ex: Here table is a reserved word

type Person record {
       @http:Field {| name: "table" |}
       string tableName;
}

User experience with proposed annotations (@http:Query , @http:Field):
[3] User experience for HTTP service type
import ballerina/http;
type CustomerServiceType service object {
    *http:Service;
    # Annotation using the query parameter name
    resource function get customer/groups(@http:Query {name: "customer-group"} string customerGroup) returns Person|error;
   };

# Annotation using in-record field
type Person record {
   @http:Field {| name: "first-name"|}
   string firstName;
   int age;
}

[4] User experience for HTTP service implementation
import ballerina/http;

service /v1 on new http:Listener(9090) {

    # Annotation using the query parameter name
    resource isolated function get customer/groups(@http:Query { name: "customer-group"} customerGroup ) returns Person|error {
        //logic here    ...
    }
}

# Annotation using in-record field
type Person record {
   @http:Field {| name: "first-name"|}
   string firstName;
   int age;
}

[5] User experience for HTTP client
[5.1] HTTP client with resource function
Currently, there is no way to define the attachment point for function arguments. Therefore, we decided to have the user provide a record parameter included in the query parameters and enable @http:Query within the record fields to capture query parameter-related meta information.
 http:Client httpClient = check new ("https://www.example.com");

# Represents the Queries record for the operation: getCustomerDetials
public type GetCustomerGroupQueries record {
    @http:Query { name: "customer-group" }
    string? customerGroup?;
    //other remaining query parameters
};
GetCustomerGroupQueries queries = {
    customerGroup: "G11"
};
string response = check httpClient->/customer/group(params = queries);

[5.2] HTTP client with remote function
public client class Client {
    // The HTTP client to access the HTTP services.
    private final http:Client httpClient;

    function init(string url) returns error? {
        self.httpClient = check new (url);
    }

    remote function getCustomerGroups(GetCustomerGroupQueries customerGroup) returns Person|error {
        ...
        Person res = check httpClient->/customer/group(params = customerGroup);
       ...
    }
}
# annotation for query parameters in the client remote functions
public type GetCustomerGroupQueries record {
    @http:Query { name: "customer-group" }
    string? customerGroup?;
    //other remaining query parameters
};

Annotation usage for OpenAPI Tool generated client and service
The OpenAPI tool encountered an issue while generating Ballerina service and client code for a given OAS reference proposal.

Service code generation: the tool included the @http:Query and @http:Field annotations in the generated service, as described here[3].

Service contract type generation: the tool included the @http:Query and @http:Field annotations in the generated service contract type, as described here

import ballerina/http;
@http:ServiceConfig {basePath: "/v1"}
type OASServiceType service object {
    *http:ServiceContract;
    # Annotation using the query parameter name
    resource function get customer/groups(@http:Query {name: "customer-group"} string customerGroup) returns Person|error;
   };

# Annotation using in-record field
type Person record {
   @http:Field {| name: "first-name"|}
   string firstName;
   int age;
}

Client Generation
However, when generating the client, the tool observed an issue where the generated client treated the query parameters as included record parameters. Therefore we need to enable @http:Query annotation within those record fields.
The rest of the payload, and response data-binding used  @http:Field annotations for record fields.

User experience with generated code
import ballerina/http;

public client class Client {

    resource isolated function get customer/groups(map<string|string[]> headers = {}, *GetCustomerGroupQueries queries) returns Person|error {
        string resourcePath = string `/customer/groups`;
        // Need to support query generation here with openapi query annotation
        resourcePath = resourcePath + check getPathForQueryParam(queries);
        return self.clientEp->get(resourcePath, headers);
    }
}

# Represents the Queries record for the operation
public type GetCustomerGroupQueries record {
    #query annotation for the parameter
    @http:Query{ name: "customer-group" }
    string? customerGroup?;
    //other remaining query parameters
};

# Annotation using the in-record field for payload binding
type Person record {
   @http:Field {| name: "first-name"|}
   string firstName;
   int age;
}

Annotation usage for OpenAPI Tool generated OpenAPI Contracts for particular service
The given @http:Field and @http:Query annotation names are mapped under the x-ballerina-name extension in the particular sections.
Given ballerina service with annotations
import ballerina/http;

service /v1 on new http:Listener(9090) {

    # Annotation using the query parameter name
    resource isolated function get customer/groups(@http:Query { name: "customer-group"} customerGroup ) returns Person{
        //logic here    ...
    }
}

# Annotation using in-record field
type Person record {
   @http:Field {| name: "first-name"|}
   string firstName;
   int age;
}

Expected generated OpenAPI contract
openapi: "3.0.0"
info:
 ...
paths:
  /customer/groups:
    get:
      …
      parameters:
        - name: "customer-group"
          x-ballerina-name: “customerGroup”   <--- query name extension
          in: query
          schema:
            type: string
      responses:
        '200':
          description: successful
          content:
            "application/json":
              schema:
                $ref: "#/components/schemas/Person"
...
components:
 schemas:
   Person:
     type: object
     properties:
       first-name: //property name
         type: string
         x-ballerina-name: firstName          <--property name extension
       age:
         type: integer

How about introducing a single annotation to represent the mapping between OpenAPI and Ballerina?
Annotation definition:
public type MappingInfo record {|
   string name;
|};

public const annotation MappingInfo Mapping on record field, parameter;

Sample usage:
type Person record {|
    @openapi:Mapping { name: "full-name" }
    string fullName;
    @openapi:Mapping { name: "phone-number" }
    string phoneNumber;
|};

+1 for having a single annotation.
In xmldata, persist, we used theName annotation for both the record fields and parameters. Shall we use the same here
# Defines the schema name which matches the record field. The default value is the record field name.
public type NameConfig record {|
    # The schema  fields and parameters value
    string value;
|};

# The Annotation used to map schema fields and param to record and record fields
public annotation NameConfig Name on record field, record;

@daneshk, @TharmiganK  Following are some points to have two separate annotations for data binding

An optional  format field to the record field to capture whether the format is XML or JSON when performing data binding. This field requires discussion with the HTTP module regarding data binding (we can remove this field if the record fields always support JSON data binding).

Upon further observation, the parameter may have specific fields beyond the record fields, such as parameter serialization options. Refer to Swagger's serialization documentation for more details.
Currently, we have no way to represent these serialization details in query parameters. Therefore, introducing a specific annotation for parameters could allow room for future expansion of these details.

type ParamAnnotation {|
   string name;
   string explode;
   string style;
|}

We need to discuss whether this annotation should be included within the OpenAPI module or another module (HTTP or language level), as this proposal is based on general user requirements. If the user writes any client or service code then the user has no requirement to attach openapi module to their code.

Attendees Meeting: @shafreenAnfar , @daneshk , @lnash94 , @TharmiganK
Proposal Meeting Notes:

Provide two separate annotations for the data binding with the name since these two areas have the potential to expand with different area-specific attributes
Implementing this annotation within the HTTP module since this annotation engages with data binding within the HTTP module
Use already existing @http:Query annotation for query parameter details mapping

Attendees : @daneshk , @lnash94 , @TharmiganK
Annotation Name finalise

Provide @http:Field as the annotation name consistent with the query annotation
2.Provide @openapi:Query  as a separate annotation for handling the OpenAPI tool's client generation. Since we have designed the query parameters to be passed as included record parameters in the function, they will be represented as record fields to the client connector. We need this annotation solely to concatenate the name, and we've decided to implement it on the OpenAPI tool side.

2024/09/02 : @http:Query Annotations support for record fields
Attendees: @daneshk , @TharmiganK , @lnash94

When trying to support @http:Query for native HTTP client , we observed that we can not attach attachment points into functions arguments, therefore we specialized this client query parameter support via the record parameter included type.
Therefore we don't need to have separate openapi query parameter that discussed above comments

Implement HTTP client-related task :

Query annotation: https://github.com/ballerina-platform/module-ballerina-http/pull/2143
Data binding with toJson method https://github.com/ballerina-platform/module-ballerina-http/pull/2151
Annotation for record name to overwrite the JSON field implementation: https://github.com/ballerina-platform/module-ballerina-data.jsondata/pull/35

We can close this proposal since we  provided all fixes and tested the change against  the  depended ballerina packages[1]
[1]
https://github.com/ballerina-platform/module-ballerina-websub/pull/666
https://github.com/ballerina-platform/module-ballerina-websocket/pull/1462
https://github.com/ballerina-platform/module-ballerina-grpc/pull/1653
https://github.com/ballerina-platform/module-ballerina-websubhub/pull/1039
https://github.com/ballerina-platform/module-ballerina-graphql/pull/2088
https://github.com/ballerina-platform/module-ballerina-sql/pull/748
https://github.com/ballerina-platform/module-ballerinax-kafka/pull/1214
https://github.com/ballerina-platform/module-ballerinax-rabbitmq/pull/1001


Is the module "baron" used in Nuitka?

Hi,
There seems to be no code in the source code that uses the module "baron". But in “/requirements-devel.txt”, "baron == 0.9" is still listed.
The following commit removes " from baron.parser import ParsingError" in "nuitka/tools/quality/autoformat/Autoformat.py ".
Minor update
So is baron a unused dependency?

Redbaron uses baron, but it didn't expose the exception. When we started using black for formatting, only one task has remained is to update comments for pylint. They used to be arbitrary order, which is bad for searching them, and redbaron is used to sort them and to enforce their value names to be standardized.
We could rewrite this code to not use it, but I kind of like redbaron, and should it or something like it, become more mature, it could be a nice tool for source level patches to be done with Nuitka. Any pointers are welcome here.


.Wheel 1 glitch Windows 2.5.4

On a self hosted NadekoBot (Windows 2.5.4), you can do a .wheel 1, thus giving you a pretty big chunk of flowers

(First Nadekobot is Public, second is my Self Hosted)

.wheel 1 hardcoded as .wheel allin on 2.5.4

the multiplier seems broken tho, 1 * 0.2 isn't 17

well you probably have more than 1 flower on your self host


Add support for TileDB sparse arrays in vector ingestion

This add support for TileDB sparse arrays as input in vector ingestion.
It also:

Removes the attribute name values requirement for dense arrays. Instead we assume that the values are in the first attribute of the array schema.
Fixes a bug in random sampling where we used in_size instead of size to compute the sampling tasks.

The sparse array input functionality can be used facilitate the ingestion of single cell census embeddings (https://cellxgene.cziscience.com/census-models)

Nice catch on the size vs in_size fix as well - curious, did we run into an issue because of it? Or you just noticed it?

I had some issues with ingesting some test arrays with random sampling


Minor fixes and improvements to GH release workflow

Make release tag regex stricter (s/./\.)
Add missing build step
Handle RC releases

I tested this on my fork, here's examples of what it produces:
https://github.com/mprimi/natscli/releases


"Copy" is available even if there's no folder to copy to

1. Have you downloaded File Manager from caddyserver.com? If yes, when have you done that? If no, and you are running a custom build, which is the revision of File Manager's repository?
Caddy v0.10.10 (non-commercial)
http.filemanager v1.3.6
Used on Windows 7 x64.
2. What is your entire Caddyfile?
:2015 {
	root F:/caddy-filemanager-test
	filemanager /admin ./admin {
		no_auth
	}
}

3. What are you trying to do?
Copy a file to another folder. (without a folder to copy to being available)
4. What did you expect to see?
The "Copy" option being greyed out or unavailable.
5. What did you see instead (give full error messages and/or log)?
The "Copy" option being available.
6. How can someone who is starting from scratch reproduce this behaviour as minimally as possible?
Use the caddyfile above with at least one file that can be copied.
This issue could probably be labeled as an "enhancement" as it doesn't really hinder use.

Duplicate of #265: same cause.


[BUG] Compiler segmentation fault on input

Is there an existing issue for this?

[x] I have searched the existing issues

Current Behavior
The compiler correctly shows the syntax errors for this file but then gives segmentation fault.
crash.du
Expected Behavior
The compiler shows the errors and exits gracefully.
Steps To Reproduce
run dictu crash.du
Anything else?
gdb traces

Thanks for reporting the issue and providing reproducible steps!

This no longer segfaults on the latest develop version


Issue with k8s.io/docs/concepts/storage/volumes/

This is a...

[ ] Feature Request
[x ] Bug Report

Problem:
the example does not work.
apiVersion: v1
kind: PersistentVolume
metadata:
  name: example-pv
  annotations:
        "volume.alpha.kubernetes.io/node-affinity": '{
            "requiredDuringSchedulingIgnoredDuringExecution": {
                "nodeSelectorTerms": [
                    { "matchExpressions": [
                        { "key": "kubernetes.io/hostname",
                          "operator": "In",
                          "values": ["example-node"]
                        }
                    ]}
                 ]}
              }'
spec:
    capacity:
      storage: 100Gi
    accessModes:
    - ReadWriteOnce
    persistentVolumeReclaimPolicy: Delete
    storageClassName: local-storage
    local:
      path: /mnt/disks/ssd1

when i create it. my terminal show:
[root@controller:~/zxy]$ kubectl create -f example-local-pv.yml
The PersistentVolume "example-pv" is invalid:
* metadata.annotations: Forbidden: Storage node affinity is disabled by feature-gate
* spec.local: Forbidden: Local volumes are disabled by feature-gate

Proposed Solution:
fix the example.
Page to Update:
http://kubernetes.io/...

Maybe the solution is in https://github.com/kubernetes/kubernetes/issues/44339

xiangpengzhao commented on 17 Apr
In fact, setting nodeAffinity via annotations is still supported currently. (#41617) However, it's turned off by default. If you want it be turned on, you can add flag --feature-gates AffinityInAnnotations=true when starting kube-apiserver and kube-scheduler. But I think pod.spec.affinity is a more recommended way :)
cc @davidopp @timothysc

OK, thanks. Let me have a try ：）

I add "--feature-gates=PersistentLocalVolumes=true" for kubelet and kube-apiserver, it works.
Thanks @roffe

@zhangxiaoyu-zidif sorry forgot the PersistentLocalVolumes.
But good it solved your problems! 👍

You do not need --feature-gates AffinityInAnnotations=true for PV node affinity.  That flag is only for Pod NodeAffinity.
You also need to add the the PersistentLocalVolumes feature gate to to kube-scheduler.
@chenopis what's our policy on documenting which alpha feature gates need to be enabled and where?

@msau42 Thanks!

@msau42 It is a good question. With alpha features come and go in each release, it is hard to track and document each feature regarding where it should be enabled. Even there is such a table or matrix, I would suspect that no user will reference it. So I would suggest our users to enable a feature across all master components, as a realistic way to make sure it is fully applied.
With that said, I do see the value of such a matrix. If a feature is only targeting a kubelet, a user may have an optimization on rolling it out to all nodes. If another feature is only meaningful for the apiserver, applying it on the controller manager and then restart it doesn't sounds reasonable. This is for serious deployments. Maybe something like this?

Feature
Status
Since
Till
apiserver
kcm
scheduler
kubelet
proxy

APIListChunking
alpha
1.8
-
Y

Y

AffinityInAnnotations
alpha
1.6
1.7
Y
Y
Y
Y
N

There are heroes working on this now: kubernetes/kubernetes#55067

@msau42 Generally, we don't document Alpha features. However, if you strongly feel it is needed, you can add the information to the relevant page and tag it w/ the following code, which gives notice about what version it's tied to and what the Alpha state means:
{% assign for_k8s_version="v1.8" %}{% include feature-state-alpha.md %}

@chenopis maybe we need to update the release procedures then?  The release team has been pushing for documentation PRs to be created, even for alpha features.

@msau42 Sorry, my bad. I just double-checked, and it's fine to document alpha features for Kubernetes, since it's OSS. We just don't do it that for GKE.
We should still tag the feature states in the docs w/ that include code so that we know to update them for each release.

Ok thanks for the clarification!

the same issue here
when I add the --feature-gates=PersistentLocalVolumes=true,VolumeScheduling=true to the apiserver and scheduler, controller , my cluster died and I can't access it anymore, but when I only add the feature  to the kubelet as following :
Environment="KUBELET_EXTRA_ARGS=--fail-swap-on=false --serialize-image-pulls=false --feature-gates=PersistentLocalVolumes=true,VolumeScheduling=true"
I get this error :
The PersistentVolume "dev-voli" is invalid:

metadata.annotations: Forbidden: Storage node affinity is disabled by feature-gate
spec.local: Forbidden: Local volumes are disabled by feature-gate
when I check kubelet logs I see this :

Mar 18 08:21:01 hamza-master systemd[1]: Started kubelet: The Kubernetes Node Agent.
Mar 18 08:21:01 hamza-master systemd[1]: Starting kubelet: The Kubernetes Node Agent...
Mar 18 08:21:01 hamza-master kubelet[10661]: I0318 08:21:01.481481   10661 feature_gate.go:220] feature gates: &{{} map[PersistentLocalVolumes:true Volu                                  meScheduling:true]}
Mar 18 08:21:01 hamza-master kubelet[10661]: I0318 08:21:01.481696   10661 controller.go:114] kubelet config controller: starting controller
Mar 18 08:21:01 hamza-master kubelet[10661]: I0318 08:21:01.481701   10661 controller.go:118] kubelet config controller: validating combination of defau                                  lts and flags
Mar 18 08:21:01 hamza-master kubelet[10661]: I0318 08:21:01.498867   10661 server.go:182] Version: v1.9.2
Mar 18 08:21:01 hamza-master kubelet[10661]: I0318 08:21:01.498924   10661 feature_gate.go:220] feature gates: &{{} map[PersistentLocalVolumes:true Volu                                  meScheduling:true]}
Mar 18 08:21:01 hamza-master kubelet[10661]: I0318 08:21:01.499033   10661 plugins.go:101] No cloud provider specified.
Any help ?

Hi @HamzaK8s, can you get the logs from your apiserver and scheduler to help see why they can't come up?  The feature gate needs to be enabled on all 3 components.


[kong] use migration commands directly in args

What this PR does / why we need it:
Call kong commands directly from migration pods. This allows them to take advantage of special entrypoint script features that require a kong command in args.
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)
Related to https://github.com/Kong/charts/issues/386#issuecomment-891859681
Note that the functionality in question doesn't yet exist in the entrypoint for the KONG_PASSWORD variable. This is preparation assuming that will be implemented.
Special notes for your reviewer:
Holding pending CI confirmation that Postgres tests complete successfully.
IIRC there may have been some reason we used the sh arg originally--typically we did that specifically to avoid the entrypoint script because of some incompatibility between its behavior and the chart (usually related to daemonization). Not sure if that ever actually existed though and/or if it's something that affected older versions of, but not the current entrypoint script.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] PR is based off the current tip of the next branch and targets next, not main
[x] New or modified sections of values.yaml are documented in the README.md
[x] Title of the PR and commit headers start with chart name (e.g. [kong])

Fine with CI. Tested with something ancient (Enterprise 1.5) and it doesn't appear this hits any incompatibility with older images, at least for the extent of older that I reasonably care about. Migrations completed and the main instance came online. :shipit:


Depreciating outdated IOC based detection queries

Required items, please complete
Change(s):

See guidance below

Reason for Change(s):

See guidance below

Version Updated:

Required only for Detections/Analytic Rule templates
See guidance below

Testing Completed:

See guidance below

Checked that the validations are passing and have addressed any issues that are present:

See guidance below

Guidance <- remove section before submitting

Before submitting this PR please ensure that you have read the following sections and filled out the changes, reason for change and testing complete sections:
Thank you for your contribution to the Microsoft Sentinel Github repo.

Details of the code changes in your submitted PR.  Providing descriptions for pull requests ensures there is context to changes being made and greatly enhances the code review process.  Providing associated Issues that this resolves also easily connects the reason.

Change(s):

Updated syntax for XYZ.yaml

Reason for Change(s):

New schema used for XYZ.yaml
Resolves ISSUE #1234

Version updated:

Yes
Detections/Analytic Rule templates are required to have the version updated

The code should have been tested in a Microsoft Sentinel environment that does not have any custom parsers, functions or tables, so that you validate no incorrect syntax and execution functions properly.  If your submission requires a custom parser or function, it must be submitted with the PR.

Testing Completed:

Yes

Note: If updating a detection, you must update the version field.

Before the submission has been made, please look at running the KQL and Yaml Validation Checks locally.
https://github.com/Azure/Azure-Sentinel#run-kql-validation-locally

Checked that the validations are passing and have addressed any issues that are present:

Yes

Note: Let us know if you have tried fixing the validation error and need help.

References:

Guidance for Detection checks
General contribution guidance
PR validation troubleshooting

Sorry my bad,Its my mistake, Its for the analytics folder only,

@v-atulyadav , Is it possibel for you to move this to Solutions/Legacy%20IOC%20based%20Threat%20Protection)/Analytic Rules folder or i need to close this and raise an new PR?

Hey @praveenthepro, as files already exist in that folder, you have to modify those files rather than adding new ones. Thanks


Do not fail clair-scan if docker containers cannot be killed

Recently some the clair-scan CI job has been failing because of an error
during cleanup. It seems that by the time we call "docker kill", at
least one of the containers (clair) may not exist any more. Maybe the
process is crashing, but the scan does complete successfully every time
regardless... To avoid job failures, we tolerate errors when calling
"docker kill" during the cleanup phase.

/skip-all