Spring Boot applicaiton won't even start until "azure.storage" properties are correctly filled

I am having a problem developing multi-purpose multi-customer library code.
In order to support either multiple cloud platforms or just multiple-customers scenarios, I am implementing an abstraction of a File Repository over both Azure blob storage and local file system (for developers or on-prem customers).
The idea is that I want Azure configuration properties not to be mandatory. If there is an Azure blob configuration, and a BlobContainerClient and the blob container name (in the project's properties), then the file repository should be implemented by Azure.
On no-property startup (with H2 database) I have written my own logic to switch for a temporary directory that, just like an in-memory H2 database, gets cleared on shutdown.
Reference: https://github.com/Azure/azure-sdk-for-java/blob/26e7c0c89d7efb17499272bfc41e458225b7cf17/sdk/spring/azure-spring-boot/src/main/java/com/azure/spring/autoconfigure/storage/StorageAutoConfiguration.java
The problem is that I am unable to start my application if the Azure SDK jar is present in the dependencies without setting the blob account (which could still be a fake until I try to connect).
I would suggest the maintainers to amend the StorageAutoConfiguration class to adhere to Spring Boot's zero-configuration paradigm, thus not blocking the application from loading when configuration is blank. Instead, the BlobServiceClientBuilder should not be created by the Bean Factory and thus the bean unavailable.
Calling code can then use @ConditionalOnBean(BlobServiceClient.class) to determine whether Azure services are configured or not.
Thank you for your kind attention and please share your thoughts with me.

@djechelon we are working on our new design of project and will release the beta versions this month,
here is the repo branch and Reference wiki you can check.

close this issue, track in Release Spring Cloud for Azure 4.0.0-beta.1
the issue will be resolved after the  4.0.0-beta.1 libraries released.


Extend sx props to support a shorthand for container queries instead of only media queries.

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
Currently, there is no proper support for container queries (which admittedly is still fresh) in mui. There is a practical shorthand in the sxProps to define styles for each breakpoint, but this results in a @media query and there's no shorthand for @container queries.
Some ideas:

Extend createBreakpoints.js to have an optional query param in its functions:

const defaultQuery = 'media'; // with type QueryType = 'media' | 'container';
function up(key, query = defaultQuery) {
  const value = typeof values[key] === 'number' ? values[key] : key;
  return `@${query} (min-width:${value}${unit})`;
}
...

Extend breakpoints.js to understand a shorthand for container queries, i.e. containerXs or just cqxs, cqsm, cqmd...

Examples 🌈
{
  color: 'red',
  color: {
    cqsm: 'blue',
  },
}

would result in:
{
  color: 'red',
  '@container (min-width:600px)': {
    color: 'blue',
  },
}

Motivation 🔦
The newly introduced @container queries are a powerful tool that will solve lots of today's problems with responsiveness. The project I'm working on heavily uses mui and its theming capabilities and we're really looking forward to the usage of @component queries as they are already now quite broadly supported. We make use of the sx props quite a lot because often they are a nicer way to quickly adjust a component to our needs compared to styled components.
Therefore it would be nice to have a way to generate @container queries with a shorthand in sx.

This one seems a bit related: https://github.com/mui/material-ui/issues/25189

👍 It is currently ~83%, look promising.

I created a pull request for this feature: https://github.com/mui/material-ui/pull/36712

Proposal
Requirement

New opt-in API because browser support is still at ~87% and not everyone needs it by default.
Expose from MUI System so that Material UI and Joy UI can use it.
The API must work with sx prop and allow developers to customize the containment name.

Usage
Expose a function called containerQuery that will attach the utilities to theme.cq, a similar experience to the theme.breakpoints (I try to avoid theme.container because we have a Container component which is a different thing).
const { containerQuery, createTheme } from '@mui/material/styles';

const theme = containerQuery(createTheme());

const MyCard = styled('div')(({ theme }) => ({
  display: 'flex',
  flexDirection: 'column',
  [theme.cq.up(300)]: { // = @container (min-width: 300px)
    flexDirection: 'row',
  },
})

// https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_container_queries#naming_containment_contexts
const MyCard2 = styled('div')(({ theme }) => ({
  display: 'flex',
  flexDirection: 'column',
  [theme.cq.up(300, 'sidebar')]: { // = @container sidebar (min-width: 300px)
    flexDirection: 'row',
  },
})

sx prop:
import { createContainerQuery, createTheme, unstable_styleFunctionSx } from '@mui/material/styles';

const theme = containerQuery(createTheme());

<Box sx={{ containerType: 'inline-size' }}>
  <Card sx={{ display: 'flex',
     flexDirection: {
       cqxs: 'column',
       cqsm: 'row', // @container sidebar (min-width: 600px)
     }
   }}>

   <Card sx={{ display: 'flex',
     flexDirection: {
       cq0: 'column',
       cq300: 'row', // @container (min-width: 300px)
     }
   }}>

   // https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_container_queries#naming_containment_contexts
   <Card sx={{ display: 'flex',
     flexDirection: {
       'cq0-sidebar': 'column',
       'cq300-sidebar': 'row', // @container sidebar (min-width: 300px)
     }
   }}>
</Box>

@siriwatknp this looks great, even though the cq is a bit unintuitive it makes sense since using container can cause confusion with the Container component.
Thanks to @nate-summercook for initiating this conversation and to @siriwatknp for the proposal.

Huge 👏 to @nate-summercook for bringing this topic up and the POC.

So is this going anywhere from here? :)

I would also be interested in seeing this feature in MUI 👌

Has there been any progress made on this feature yet ?

I'd let @brijeshb42 review the proposal once more before marking this as good to take. @brijeshb42 Do you have any concern for the proposal to work with zero-runtime?

I'd let @brijeshb42 review the proposal once more before marking this as good to take. @brijeshb42 Do you have any concerns about the proposal to work with zero runtime?

regarding zero runtime: Shouldn't be similar to the already existing media queries. So it shouldn't generate additional problems ;)

Great job, but I have some questions and suggestions here:

When using container queries, I rarely use fixed breakpoints for different elements, unless it's just within a fixed page layout. But if the page layout is fixed, media queries can also do most of things which container query can do.
I think you should consider to keep the usage of container queries consistent with that of media queries in material-ui. For example: the usage of hooks like useMediaQuery.

the usage of hooks like useMediaQuery.

We need to see the use cases where CSS alone is not enough then we can consider the hook version.

Hate to be the annoying guy constantly nagging about this feature, but it's been nearly a year and pretty much nothing happened since my initial PR. What is blocking you still from marking this good to take? My project (and apparently several others) are eagerly waiting for this feature and it seems nothing is happening for months...
Also, browser support for container queries is now at 	91.47%.
If you need anything more from me, please let me know, I'm glad to help :)

Excited to see this land!

@nate-summercook @elyseholladay @beingflo @issam-seghir The PR is open. Here is the summary, I decided to use similar APIs as TailwindCSS (I don't see why we need a different one):
See demo here: https://deploy-preview-41674--material-ui.netlify.app/system/getting-started/usage/#responsive-values
<Box
  sx={{
    display: 'flex',
    flexDirection: { xs: 'column', '@350': 'row' },
    bgcolor: 'background.default',
    border: '1px solid',
    borderColor: 'divider',
    borderRadius: 2,
    overflow: 'clip',
  }}
>

Is there any chance this feature will be added to v5 as well?

Is there any chance this feature will be added to v5 as well?

Sorry to say this but I don't think we will add any new feature back to v5. We are now working on v6 alpha.


it cannot open multiples gt

when i open 2 gt it says one gt is running go play that one

This project is unfinished & has been abandoned


Introduce our code culture in contributing.md

What this PR does / why we need it:
This is a first outline of our code culture that mostly came out of retrospectives we had in the last 2 months.
This is for sure not a definitive list, let's add more points in next PRs though. Let's make this PR just about the points mentioned and if everyone is OK with them and with the wording.
Please let's keep this PR open longer so that everyone have chance to see it.

Looks good! Thank you!


Update syntax and readme content

Purpose

0.985.0 syntax updates and updated Readme as istio artifacts are now generated with the ballerinax/kubernetes extension.

Goals

Upto date syntax and readme.

Approach

Update bal files and readme.

Closing as reopened at https://github.com/ballerina-guides/ballerina-with-istio/pull/23


Only the first opened file gets linted when run as daemon

When activating the daemon, only the first opened file gets linted. When switching to another file nothing happens.

There are no errors from the extension itself in the output tab of this extension. I can see that the linter gets called for the file I just switched to, but no linting errors are shown in the output either.
Making changes to a file and saving it doesn't make a difference.
Apart from all of that, linting with the daemon (if it works at all) seems slower than directly invoking mypy.
Example Workspace
vscode-mypy.zip
My System
Version: 1.84.2 (user setup)
Commit: 1a5daa3a0231a0fbba4f14db7ec463cf99d7768e
Date: 2023-11-09T10:51:52.184Z
Electron: 25.9.2
ElectronBuildId: 24603566
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Mypy Type Checker: v2023.6.0
Python 3.10.11

That is an issue with dmypy, https://github.com/python/mypy/issues/15677 . We added the mypy-type-checker.preferDaemon setting to allow users to turn of daemon mode as it seems to have too many issues currently.


small typo

Description
Describe the changes made in your pull request here.
Checklist
Ensure you completed all of the steps below before submitting your pull request:

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

Pull requests with an incomplete checklist will be thrown out.

Big thanks!! 🫡


[DRAFT] Instruction tuning

This PR adds instruction tuning to openLM.
Currently a work in progress, but got some pretty good initial results with openLM 1B, doing a small amount of finetuning on the Tulu-V2 corpus, e.g.:
<|user|> Give me a very brief synopsis of the Donald Trump presidency.
<|assistant|>
I am not an expert on Donald Trump, but here is a brief overview of his presidency.

The inauguration of Donald Trump was historic for several reasons. First, it marked the first time that a sitting U.S. president was not re-elected in a single term. Second, it was the first time that a president was inaugurated using the "Old" or "Inaugural" Bible, which is believed to be more sacred than the "New" or "Holy" Bible. Third, it was the first time that a U.S. president was inaugurated using the "In God We Trust" motto.

In terms of policy, Donald Trump's presidency was largely focused on tax reform, regulatory rollbacks, and deregulation. In terms of foreign policy, it was largely focused on trade wars, military interventions, and military buildups.

This is in comparison to the garbage output of the original model without instruction tuning, so I think I'm doing something right!
<|user|> Give me a very brief synopsis of the Donald Trump presidency. <|assistant|> Ok, thanks.

# I am a little surprised that I did not get a better reception from the people, because I think I did a good job. I think I did a good job. I think I did a good job.

# OK, I want you to answer a question.

# OK, I think that I am going to take a question from the floor. If you have a question you can raise your hand. I think I am going to take a question from the floor. If you have a question you can raise your hand.

# How many people are in the United States?

# I think we have a question from the floor. How many people are in the United States?

# OK, I want you to answer a question. How many people are in the United States? <|student|> How many

Currently doing a larger run, and will do more careful evaluations to report performance improvements on downstream tasks.

Cool! Would be nice if it got the fact about presidents losing re-elections right (https://en.wikipedia.org/wiki/List_of_presidents_who_did_not_win_reelection) :-)  But still much better than the baseline without instruction tuning of course (as you said)!


Trig functions in equations

I require trig functions in some of the equations in my example:  sin, cos, tan, sec, csc, cot

These functions are now implemented.


Best way to sort a collection

I'm attempting to sort a collection using lodash _.sortBy method.
Problem is the collection methods get removed by lodash. I have also tried implementing a Collection method with no success.
What is the best practice for doing this?
Edit - related to https://github.com/platanus/angular-restmod/issues/169

Closing as solved.


Fix orgnization user watch repository

fix #2667

Codecov Report

Merging #2670 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master    #2670   +/-   ##
=======================================
  Coverage   27.13%   27.13%
=======================================
  Files          86       86
  Lines       17062    17062
=======================================
  Hits         4629     4629
  Misses      11755    11755
  Partials      678      678

Impacted Files
Coverage Δ

models/repo.go
13.14% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Does user creating repository for organization need to be added automatically as watcher?

@lafriks I think yes.

LGTM
Would it be worth changing watchRepo(..) to take a user argument, instead of a user-id, and check that the user is an individual? Right now, I think there is no way for the user-id to be an organization, but it might protect against future bugs. Just a thought.

@ethantkoenig Good idea. But for keeping the PR simple, I think that could be another PR.

@Morlinest fixed and rebased.

LGTM


feat(core): Skip schema post processor when previous post-processor r…

…emoved the current schema
Example: an avro schema is removed. Then the next post-processor (example generator) does not need to be called. Also, it avoids the error message due to unresolvable avro schemas

Relates to the second issue of https://github.com/springwolf/springwolf-core/pull/582


When using the host option the url does not include the bucket name

If the host option is passed into the Builder class the returned url does not include the bucket name. So I do not think this option is working as intended.
I was able to alter this spec to assert that the bucket name was in the url and it fails.
My altered spec:
    describe "custom host" do
      let(:host) { "my.example.com" }

      it "is correct" do
        expect(builder.public_url(object_key)).to eq("https://#{host}/#{object_key}")
        expect(builder.public_url(object_key)).to include(bucket_name) # new assertion
      end
    end

failure message:
  1) FasterS3Url#public_url custom host is correct
     Failure/Error: expect(builder.public_url(object_key)).to include(bucket_name)
       expected "https://my.example.com/some/directory/file.jpg" to include "my-bucket"
     # ./spec/builder_spec.rb:70:in `block (4 levels) in <top (required)>'

It is hard to say what the correct behavior should be since amazon has an endpoint option and not a host option. My guess is that we would want https://my-bucket.my.example.com/some/directory/file.jpg which is what amazon returns with an endpoint of https://my.example.com.

Hi, thanks for the clearly communicated issue, and for getting in touch!
OK, so host -- you are right that when I implemented/documented it I hadn't totally thought it ought and it didn't quite work in that way.
But I have ended up using it for when you have a CloudFront distribution (or any other CDN) on top of S3. For public unsigned urls, you just need to change the hostname to be your CDN hostname. And this is a convenient tool to do it, in a speedy way (much speedier than AWS SDK), applying appropriate (a bit idiosyncratic) S3 escaping rules for keys, etc.
So it is correct that it doesn't include the bucket name -- it is simply replacing the host name with your own custom specified hostname, that might be a CDN or other kind of proxy.  That's all it is, and I have had a use for it myself, so would like to leave it in!
When I wrote it, I think I didn't totally understand the use cases (that I ended up using it for), so it's possible there's some confusing docs that should be updated? Feel free to point out or PR! Closing this for now!


Detecting fixed points to reduce execution time

Description
Investigate whether using the dominators tree in a CFG and detecting a lack of change in a dominator basic block can profitably reduce unneeded searching.
Background
A dominator tree has the property that the basic block acts as a choke point for each of the basic blocks in its decendents. Therefrore if in tracing there is no change in a dominiator, there will be no change in the children and so they don't have to be scanned.
It could be that subsequently there's a change in one of a basic-block's ancestor dominators, and then the basic block would again be re
scanned.

We're spending a bit of time cleaning up old issues, which is why I was re-reading this issue again.
Not sure what my reasoning was, but I think I was wrong.
As I understand it (now) the following example could be optimized using this idea/technique:
function expensiveButUseless() {
    for (uint i=0; i<block.blocknumber % 10; i++) {
    }
}

function doIt() {
   expensiveButUseless()
   expensiveButUseless()
}

would be equivalent (in terms of safety properties) to:
function doIt{
  expensiveButUseless()
}

I'll therefore keep this issue in the backlog


Git index revision ids might have more that 7 characters.

In large repositories, commit ids in the index line for git patches can have more than 7 characters. This fixes it by making them variable length. To avoid making the expression too general, I also changed \w to accept only hex characters.

Great! Thanks so much. Could you add a test case to something that exercises this change?

Done.

Thank you :smile_cat:


Out Of Memory crashes

Any hints on how to investigate the cause of this?
Just had it happen twice after adding an extra project to my workspace (now 7 in total)...

This might help https://stackoverflow.com/questions/71614897/vscode-crashed-reason-oom-code-536870904

It looks like the OEUnit project I've recently added is causing the issues...
I'll exclude it from my workspace and use a pl file instead and see how that goes.

Started a rebuild of my project, and meanwhile attempted to open a markdown file...

I have disabled the "Markdown All in One" extension I was also using and I have the impression this is helping...
Closing this one again, will reopen if the issue reoccurs (without other extensions).


New dev profile that doesn't create the Hawkular archives.

$cd dist
$mvn clean install -DskipTests -Pdev
Total time: 41.865 s

$mvn clean install -DskipTests -PquickDev
Total time: 22.411 s

=> 19.5 seconds saved
Here is what you can do in 19 seconds:

https://www.youtube.com/watch?v=Yn9DpFY1X7o
http://www.dailymail.co.uk/sport/olympics/article-3044119/Usain-Bolt-want-run-200-metres-19-seconds-fully-fit-impossible-beat-me.html
https://www.youtube.com/watch?v=h2n9vPuzvj4

:smiley:

I like the idea per se, but not the addition of a new profile.
I think it should be the other way around. -Pdev should skip creating the archives and if you insist on having archives in dev-mode, then add the other profile or -Ddozip
A non-dev build always creates the archives, so we don't lose that functionality for releases etc.

I agree, but I don't know who depends on it. It's possible that someone builds it with -Pdev and do something with the zip, I could imagine QE is doing this in foreman. I wanted to be minimally invasive and don't break anything.

I think it should be the other way around. -Pdev should skip creating the archives

Done. Hopefully, it won't break anything, I can send it to the mailing list that people can use the dozip profile if they need the archive with jdoe

On 21 Jul 2015, at 11:29, Jirka Kremser wrote:

I agree, but I don't know who depends on it. It's possible that
someone builds it with -Pdev and do something with the zip, I could
imagine QE is doing this in foreman. I wanted to be minimally invasive
and don't break anything.

Then ask QE and warn them that this change may be coming.
We had too many profiles in the past, which was pretty confusing
to many members of the community.

travis fails during gulp build because of
unexpected status code: 403 on: https://api.github.com/repos/borisyankov/DefinitelyTyped/branches/master
we should consider using the oauth token because github has limits and travis infrastructure must be spamming them (website repo has similar issue)

I like this!
Too many profiles are a concern, but this is a real time savings.

Merged #342


Context variables extension

Describe the bug
Nothing prevents you from declaring a variable with a same name as the existing gitStream context variables have and one could accidentally do that, yet this isn't a supported thing.

Allow existing variables' extension,
Or make it explicitly prohibited.

To Reproduce
Steps to reproduce the behavior:

Use files context variable in your automation, e.g.{{ files | extensions | match(regex=r/^sql\s*$/) | some }}

Introduce a custom variable named source, e.g.source:
  isHotfix: {{ branch.name | includes(regex=r/^hotfix.+$/) }}

gitStream will fail with not that clear errorerror: TypeError: Cannot read properties of undefined (reading 'map')
    at Context.parseMatchDiffLines (/node_modules/@linearb/gitstream-rule-parser/dist/gitstream-rule-parser.cjs.development.js:1412:30)
    at eval (eval at _compile (/node_modules/nunjucks/src/environment.js:633:18), <anonymous>:26:101)
    at _callee3$ (/node_modules/@linearb/gitstream-rule-parser/dist/gitstream-rule-parser.cjs.development.js:1265:13)
    at tryCatch (/node_modules/@linearb/gitstream-rule-parser/dist/gitstream-rule-parser.cjs.development.js:97:17)
    at Generator._invoke (/node_modules/@linearb/gitstream-rule-parser/dist/gitstream-rule-parser.cjs.development.js:77:24)
    at Generator.next (/node_modules/@linearb/gitstream-rule-parser/dist/gitstream-rule-parser.cjs.development.js:128:21)
    at asyncGeneratorStep (/node_modules/@linearb/gitstream-rule-parser/dist/gitstream-rule-parser.cjs.development.js:361:24)
    at _next (/node_modules/@linearb/gitstream-rule-parser/dist/gitstream-rule-parser.cjs.development.js:383:9)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
/node_modules/@linearb/gitstream-rule-parser/dist/gitstream-rule-parser.cjs.development.js:1412
  return !regex ? [] : files.map(function (_ref3) {

Expected behavior

No errors, core source variable is extended with new members from your custom variable,
Or clear error message saying that one can't use a variable named source, as it's a reserved name.

@uladz-zubrycki welcome, and thanks for reporting this issue! We'll investigate it and let you know when we've implemented a solution for this. In the meantime, any other users who are affected by this bug can 👍  the original post or leave a comment to describe their situation.

Fixed