Owner (org) not being set

Hi folks!
I came across your repos from this article: https://www.mineiros.io/blog/how-to-manage-your-github-organization-with-terraform which has given me a great headstart as a complete noob to Terraform. Thanks so much for the article and the resources! I have over 90 repos to manage in our open source project and I think this is going to be a very efficient way to work once I get my head around it all!
I'm stumbling upon a challenge though.
In your article you declare the organisation in the main.tf file however this doesn't seem to be working when I try to use the up-to-date example code from your repos.
I had to change a bunch of things by copying from your latest repos because I guess things have changed in the GitHub API since the article was written, so I expect maybe the way to declare the organisation has changed too.
I tried checking your repos for how to declare it with the updated templates but I can't seem to find it in any of your example files. I think that either it's set at the repository.tf or the main.tf level, so hedging my bets and making the request here for a snippet on how to get this working!
So far it's working perfectly, but creating everything in my personal account, not the org.
Thanks in advance for any help!

Hi @RCheesley ,
Thanks for reaching out and my apologies for the outdated article. We are currently working on a new set of articles that are based on the updated modules, provider and in which we will use GitHub Actions as the CI server since we abandoned Semaphore some time ago.
In the meantime, I kindly refer to the provider docs: https://registry.terraform.io/providers/integrations/github/latest/docs#owner
You can either set the organization through the organization attribute in the provider block or by configuring  the organization through the GITHUB_ORGANIZATION environment variable.

@RCheesley this is an example on how to configure the provider properly
terraform {
  required_providers {
    github = {
      source  = "integrations/github"
      version = "~> 4.0"
    }
  }
}

# Configure the GitHub Provider
provider "github" {
  organization = "my-org"
}

@RCheesley please let us know if the above mentioned hints helped you to solve your issue. Many thanks!

Hi @RCheesley, since I didn't hear back from you anymore, I am gonna close this issue for now. Please feel free to re-open it again in case I couldn't help you to resolve your issue. Thank You!


Enable npairs loss on windows

Fixes https://github.com/tensorflow/addons/issues/838
IIRC this should be fixed on TF2.2

Nice, thanks!


Fetching homebrew-php-ext failed

Hi,
thank you for the work you put into this repository/tap. 👍
After making the brew repo unshallow and try to run brew update I get the error from kabel/homebrew-php-ext:
fatal: couldn't find remote ref refs/heads/master
Error: Fetching /usr/local/Homebrew/Library/Taps/kabel/homebrew-php-ext failed!

https://github.com/kabel/homebrew-php-ext#troubleshooting

@kabel, even after running brew update-reset:
==> Fetching /usr/local/Homebrew/Library/Taps/kabel/homebrew-php-ext...
fatal: couldn't find remote ref refs/heads/master
error: Not a valid ref: refs/remotes/origin/main

==> Resetting /usr/local/Homebrew/Library/Taps/kabel/homebrew-php-ext...
Branch 'master' set up to track remote branch 'master' from 'origin'.
Reset branch 'master'
Your branch is up to date with 'origin/master'.

I'm still getting an error when I run brew update:
fatal: couldn't find remote ref refs/heads/master
Error: Fetching /usr/local/Homebrew/Library/Taps/kabel/homebrew-php-ext failed!

btw, I think the error happens normally because inside /usr/local/Homebrew/Library/Taps/kabel/homebrew-php-ext/.git/config you can see:
[core]
	repositoryformatversion = 0
	filemode = true
	bare = false
	logallrefupdates = true
	ignorecase = true
	precomposeunicode = true
	autocrlf = false
[remote "origin"]
	url = https://github.com/kabel/homebrew-php-ext
	fetch = +refs/heads/master:refs/remotes/origin/master
[branch "master"]
	remote = origin
	merge = refs/heads/master
[homebrew]
	private = false

It is looking for master branch, but the master branch in this repo has been renamed to main due to the new politically correct crap, I mean policies that GitHub introduced.

As @panosru mentioned running brew update-reset brings up the same error like he posted. brew doctor didn't help either.

@DevDavido, just follow my latest post and you will be good to go ;)

Sad to see the brew commands are a bit fragile. The other option is to untap and retap.

@kabel, I believe that in current situation, brew is not to blame, github decided to go a more PC way, which many, including me, don't like, but still, it is githubs' decision; thus, when it came into effect, brew broke because it was pointing to a reference that no longer exists. Untap and tap is the easier solution, which actually I believe is the best compared to the one I provided above.

I appreciate your feedback, but please keep the divisive language to a minimum. I made the conscious decision to change default branch names, fully knowing their would likely be some hiccups.

Thankfully github gave the option to us to decide how we like to proceed, otherwise I would've be moving :) Cheers


CAN support

Is it possible to access GPIO pins, specifically CAN, within a container?

Hi @lucasvandijck, I'm not entirely sure - if you search the NVIDIA Jetson forums for 'GPIO container', you will find some results.   However I think with CAN bus, you should be able to just mount the CAN device(s)

Yes i first tried to access the GPIO directly using various methods mentioned on the forum, but without any luck. Hadn't thought about passing through the interface though, thank you!


Scope fixture execution

Hey Patrick,
This is more a question than an actual issue at the moment.
Let me first describe the problem that I was trying to solve yesterday with @ChrisMissal:
We have two conventions for integration tests, FixturePerMethod and FixturePerClass, with the main distinction being when we reset state between the test runs.
public class FixturePerMethodConvention : IntegrationTestConvention
    {
        public FixturePerMethodConvention()
        {
            Classes
                .ConstructorDoesntHaveArguments();

            ClassExecution
                .CreateInstancePerCase();

             CaseExecution
                .Wrap<IntegrationTestExecutionWrapper>();
        }
}

public class FixturePerClassConvention : IntegrationTestConvention
{
    public FixturePerClassConvention()
    {
        Classes
            .ConstructorHasArguments();

        ClassExecution
            .CreateInstancePerClass()
            .Wrap<IntegrationTestExecutionWrapper>();
    }
}

The IntegrationTestConvention just filter the Classes to the Integration test namespace. It also defines an ParameterSource that uses AutoFixture to inject the method arguments.
This all works just fine. The part that we were not able to do is that we wanted to create a NestedContainer scoped to the Fixture, and we tried doing it like this:
public class IntegrationTestExecutionWrapper : CaseBehavior, ClassBehavior
{
    public void Execute(Class context, Action next)
    {
        ResetDataCheckpoint();
        TestContextFixture.Reset();
        next();
    }

    public void Execute(Case context, Action next)
    {
        this.ResetDataCheckpoint();
        TestContextFixture.Reset();
        next();
    }

    private void ResetDataCheckpoint()
    {
        // uses Respawn to reset the db state
    }
}

The TestContextFixture is a helper class that we can pass to the tests and use to save entities to the DB, send MediatR messages, on my tests, like this:
public void Should_update_customer_name(TestContextFixture fixture, Customer customer)
{
    customer.Name = "Tobias";

    // Saves customer entity to DB
    fixture.SaveAll(customer);

    // send MediatR message
    fixture.Send(new UpdateCustomer { Name = "Mrs. Featherbottom" });

    // Reload entity from DB
    fixture.Reload(ref customer);

    customer.Name.ShouldBe("Mrs. Featherbottom");
}

We added that Reset() method to the TestContextFixture to create a new scope, i.e to create the nested container.
public void Reset()
{
    this.scope.DisposeCurrentNestedContainer();
    this.scope.CreateNestedContainer();
}

With that, it was trivial to scope things like the EF DbContext to the NestedContainer. And this worked really well for the FixturePerClass tests. But in the FixturePerMethod scenario we have a problem that I'm not yet sure the best way to solve.
In our AutoFixture configuration for the Integration Tests, for some entities (usually lookup table entities), we configured AutoFixture to pull an instance from the DB instead of newing one up. For example, we have a "State" table that is just a lookup table for the US States, given that this table doesn't ever change, we configured Respawn to skip it when doing the Checkpoint Reset and have a custom AutoFixture builder that just pulls one random State entity from the DB whenever we need one.
When we added the Reset to the TestContextFixture, this became a problem for the FixturePerMethod as the method parameter instances were created before the CaseExecution wrapper method ran, essentially making the State entities to be tied to a different DbContext from the one that the TestContextFixture was going to use after the Reset call. And this makes EF freak out.
I initially tried a workaround by doing the Reset not at the CaseBehavior hook but in the ParameterSource. That didn't work because Fixie creates the parameter instances for all test methods within a class before executing each test method. Which, again, works fine for our FixturePerClass scenario but doesn't work for the FixturePerMethod scenario.
Going through this exercise yesterday it felt like I was trying to approach this the wrong way, as I felt I was having to "hack" fixie too much. I believe I'm probably using the wrong extension points to do this. Is there a way that I can reset the scope of the fixture execution, including the test method argument resolution?

@plioi ,
I was looking into implementing this change but I soon realized that this won't be trivial and will, probably, lead to API changes. So I want to discuss with you before proceeding.
The main reason why this is challenging is due to the fact that ParameterSource does the discovery of the case parameters as well as resolve their values at the same time. This means that for cases with method arguments, those arguments get resolved in the ClassRunner, when Fixie creates the Case instances.
To make this work, my idea is to change the ParameterSource api to allow the separaione of the parameter discovery from the parameter value resolution. I'm thinking something along the lines of:
public interface Parameter
{
   public IEnumerable<Func<object[]>> GetParameters(MethodInfo methos);
}

That way we can figure out the number of sets of paramenters for a given test method and create all the Case instances, but we can defer the Parameter value resolution to a later stage in the lifecycle, under a Fixture scope.

I think returning an IEnumerable<Func<object[]>> alone doesn't help, since we'd still have to change when the paramter source is used.  We may be able to fix where it is used without changing the interface.  I'll take a closer look at the main loop in ClassRunner to see what all would be involved in moving the retrieval of parameters to a more appropriate step of the process.

:+1:

If all of the sets of inputs for one test method were resolved right before that test method was called several times in a row, would that be sufficient?  Or, should each individual set of args be resolved right before the single call they belong to?  I bet the latter would be best.

the latter, yes.
Currently, when you have a CreateInstancePerCase lifecycle, and you have multiple sets of parameters, do you create a Fixture scope per each individual set of args?

https://github.com/fixie/fixie/blob/master/src/Fixie/Internal/Behaviors/CreateInstancePerCase.cs My "Fixture" class means "test class instance" (which I regret, as I think it causes confusion).  So, yes, when creating an instance per case, you get a whole new Fixture instance for each invocation of the test method.

What I had in mind was for Fixture to be the scope boundary for my tests, according to the lifecycle I have specified, and to be guaranteed that all parameter resolution, both ctor or test method, to happen within this scope boundary.
 The fixture scope starts right before a Test class is instantiated and is disposed right after the test class is disposed. All arguments, constructor arguments for test class instances and test method arguments for test cases are instantiated within the Fixture scope.
Fixture Life-cycles
Instance Per Class
When executing under an Instance per Class lifecycle, all cases defined in a test class are scoped to a single class instance.
This life-cycle will enable a Test Class Per Fixture pattern, where the Setup (and usually the Execution as well) is done at the test class constructor and each test case is a different assertions around that same setup and execution.
In a pseudo-code, the scoping would look like:
var fixture = startFixtureScope();
var testClassInstance = instantiateTestClass();
foreach(var case in testClass.Cases)
{
    var caseArgs = ResolveCaseArguments(case);
    InvokeCase(testClassInstance, caseArgs);
}
testClassInstance.Dispose();
fixture.Dispose();

Instance Per Case
In an instance per case lifecycle, each case defined in a test class will run under their own test class instance, completely isolated from each other.
This is usually the scenario where each test is completely isolated from the other tests defined in the same test class and usually the setup, execution and assertion parts of the test are defined in the test method body.
In pseudo-code, the scoping would look like:
foreach(var case in testClass)
{
      var fixture = startFixtureScope();
      var testClassInstance = instantiateTestClass();
      var caseArgs = ResolveCaseArguments(case);
      InvokeCase(testClassInstance, caseArgs)
      testClassInstance.Dispose();
      fixture.Dispose();
}

Conclusion
That way, regardless of the test class instance lifecycle, one could always create a FixtureBehavior to define the tasks that need to be performed to guarantee the isolated fixture boundary. In the example below, it clears the test database (checkpoint.Reset()) and creates a new nested container (container.CreateNestedContainer) before proceeding with create the test class instance, resolving case arguments and executing the cases:
FixtureExecution.Wrap((fixture, next) =>
{
    checkpoint.Reset();
    container.CreateNestedContainer();
    next();
});

Thanks for that analysis.  I've been thinking it's time to revisit the test class lifecycle in light of our real-world usages.  If it can be resolved without a breaking change, I'll include it in the 1.x branch.  If not, I have started up a dev branch for breaking changes (so far the only breaking changes have been for people making 3rd party runners, but I anticipate a few convention API changes where needed).
If this falls under the "breaking, 2.x" category of changes, that may make it a longer wait.  How much is this hurting in your current project?

I have my workarounds. (I currently don't allow Test parameters on integration tests, only ctor arguments).
So, don't feel pressured by my project is what I'm trying to say :wink:

It's been a while but did you get to work on that issue since it was reported?

@pedroreys With the big change in the customizatoin API in the now-released version 3.0, I believe I finally give enough control over the test project lifecycle, and in such a way where you can handle such things using plain old C# rather than these older complex-and-insufficient 'wrapping behaviors'. I'm closing this issue due to age and the fact that I think the new model gives everyone the control and context they need. Your pain points here definitely influenced the v3 design, so thank you for raising them and for your patience :)

blast from the past :)


Add gas price estimate in forge script summary

Component
Forge
Describe the feature you would like
I would like to be able to view the estimated gas price here after running forge script:

Happy to take on this! For the formatting, should we show the amount in Gwei, or do something akin to what etherscan does (that is, show the amount in ether and then in gwei)?

@outdoteth Is this issue asking to show the gas price that was used to convert the amount of gas used into an ETH estimate?
If so, how does this formatting look for @Evalir to implement? (I also changed the text on the bottom line a bit)
Estimated total gas used for script: 500123

Estimated total cost: 0.234 ETH (at 10 gwei)

Hm I think it would be better to have it on it's own separate line. The precision in the screenshot is nice and does not abstract anything away. It becomes a bit hard to read like this imo:
Estimated total gas used for script: 500123

Estimated total cost: 0.234234234234234  ETH (at 10 gwei)

vs:
Estimated total gas used for script: 500123

Estimated gas price: 10 gwei

Estimated total cost: 0.234234234234234  ETH

That sounds good to me—I personally like having everything on 3 lines as it seems pretty clear. wdyt @mds1? once we're aligned I can get started on this.


Explore running /onion bootstrappers

OpenBazaar have built an /onion transport: https://github.com/openbazaar/go-onion-transport

Not gonna run an /onion bootstrapper until go-onion-transport has been audited.


EnvoyFleet customization improvements

This PR...
Changes

Adds the ability to customize EnvoyFleet deployment, including:
-- Scheduler hints (NodeSelector, Tollerations, Affinity/Antiaffinity)
-- CPU and Memory Resources (limits and requests)
-- setting custom public Envoy Image
-- Adding custom annotations (for e.g. Prometheus scrapping)
-- Service customization - the ability to set ports, type and annotations to fully support ingress Service in any environment
adds setting Status.State field for EnvoyFleet, allowing to hint the user if EnvoyFleet deployment succeeded (visible via kubectl describe envoyfleet default. Still requires more improvements since technically Service, Deployment and Config map statuses are not checked.

As part of the implementation, local development environment was reworked to support the same labels and resources names as in the Helm chart and subsequently
Updates

Controller-gen is updated to the currently used by Kubebuilder version 0.7.0.
Go-control-plane is updated to 0.10.1

Follow up items:
These tasks needs to be done just before we tag the new version:

the documentation for the EnvoyFleet CRD isn't changed since the site is deployed from main branch and it will be available immediately while must be visible only when we make the new tag and Helm chart.
Helm charts needs to be updated as well before we tag new version.

Follow up issue will be created.
Fixes

Moved EnvoyFleet handling from k8sutils package since it had leaked EnvoyFleet implemenation.
Reworked hardcoding of XDS service URL to the discovery mechanism based on labels. Needed for the situations when kusk-gateway is deployed to the different namespace.
Removed mangling of the Kustomization files during the debugging.

Checklist

[x] tested locally
[ ] added new dependencies
[ ] updated the docs
[ ] added a test

adds setting Status.State field for EnvoyFleet, allowing to hint the user if EnvoyFleet deployment succeeded (visible via kubectl describe envoyfleet default. Still requires more improvements since technically Service, Deployment and Config map statuses are not checked.

Perhaps we should open another issue for this @Tarick ?

local development environment was reworked to support the same labels and resources names as in the Helm chart

Will you update the docs?


Is it possible to add multiple  aws account in pacbot for monitoring

❔ Question

🔦 Context

💻 Code Sample

Yes. You can add any number of AWS accounts.
Please check the documentation under FAQ
https://github.com/tmobile/pacbot/wiki/Install#adding-new-aws-accounts-to-pacbot-to-monitor


Add PR template

I would like to add a pull request template for this repository. I believe that having a standardized template will help streamline the contribution process, ensuring that all necessary information is included and making it easier for maintainers to review and merge pull requests.
Could you please assign this issue to me under GSSOC'24.

//Duplicate issue

But I was the one who raised this issue first. Why would you label the original issue as duplicate???

All the other PR template related issues have been raised after this issue only.


Blade snippets not showing

I have a problem with blade snippets, when i'm in a blade view (*.blade.php) and i want to trigger some Blade snippets, they never appear

See #3

Thank you, that autocomplete config worked like charm


How to build localized UI

VSCode Version: master
OS Version: Windows 10

I'm trying to test a few modifications to Chinese Simplified translation, but can't get the built Code app localized.
I followed the instructions from:

Contributing to Code

My build env is:

Node JS v4.4.3
Python 2.7.11
Visual Studio Express 2013

Finally, I started Code successfully with:
.\scripts\code.bat

However, the localized UI just wouldn't show. I discovered that the nls files,
out\vs\workbench\workbench.main.nls.*.js

didn't get built.
How should I build them? Thanks!
I tried instruction from #2228, but couldn't clone the monacotools repository because I'm not authorized. And don't know if this is the right way to go.

@jackqq you need to run a full build. You can do that using the following command from a command prompt in the vscode directory:
gulp vscode-win32
This builds a full vscode version in ..\VSCode-Win32. After it is done change to that directory and start 'Code - OSS.exe'.


Question: Is it possible to use immediate transactions?

Ruby on Rails is making many changes to improve SQLite support. Apparently, one of the most noticeable is using BEGIN IMMEDIATE TRANSACTION. Quoting from this article from the author of such improvements for RoR (it is a highly recommended read for anyone using SQLite):

By default, SQLite uses a deferred transaction mode. This means that SQLite will not acquire the lock until a write operation is made inside the transaction.
In a context where you only have one connection or you have a large amount of transactions that only do read operations, this is great for performance, because it means that SQLite doesn’t have to acquire a lock on the database for every transaction, only for transactions that actually write to the database.

The he goes about how 99% of the time starting a transaction in Ruby on Rails means that there will be a database write. The conclusion is that immediate transactions should be the default for most cases.
This made me wonder a few things:

Is it possible to use immediate transactions with Ecto?
If not, would it be possible to add support for them? I could help if this feature seems interesting to have.
Would it be interesting to replicate the RoR behaviour in Ecto as well and make immediate transactions the default? I've been thinking about it and the fact that most transactions result in a database write seems true in my experience.

Great question, yes it is 100% now
https://github.com/elixir-sqlite/exqlite/blob/fec606ccc8a291526d1e3137099b6acf0f6f84fe/lib/exqlite/connection.ex#L263-L280
You need to set the transaction mode to :immediate
Check out the transaction documentation for Ecto in general https://github.com/elixir-sqlite/exqlite/blob/fec606ccc8a291526d1e3137099b6acf0f6f84fe/lib/exqlite/connection.ex#L263-L280

I wonder if it is possible to set the default transaction mode for ecto rather than being forced to pass it everytime. I will need to dig further.

@josevalim or @ruslandoga what is your opinion on setting the default transaction mode for this adapter to :immediate rather than :deferred. I don't really have a guide to look at for the SQL adapters because, well, those databases don't provide this level of control on transactions.

postgrex
myxql
tds

I am trying to set the :mode option but it doesn't seem to have any effect. I am not sure if I am using it correctly though.
iex(4)> Repo.insert(%Person{name: "Cristian"}, mode: :immediate)
# [debug] QUERY OK source="persons" db=0.8ms idle=936.3ms
# INSERT INTO "persons" ("name") VALUES (?) RETURNING "id" ["Cristian"]

iex(5)> Repo.transaction fn repo ->
...(5)>   repo.insert(%Person{name: "Cristian"}, mode: :immediate)
...(5)> end
# [debug] QUERY OK db=0.0ms idle=1807.7ms
# begin []
# ↳ :erl_eval.do_apply/7, at: erl_eval.erl:746
# [debug] QUERY OK source="persons" db=0.7ms
# INSERT INTO "persons" ("name") VALUES (?) RETURNING "id" ["Cristian"]
# ↳ anonymous fn/3 in Ecto.Adapters.SQL.checkout_or_transaction/4, at: # lib/ecto/adapters/sql.ex:1382
# [debug] QUERY OK db=0.2ms
# commit []

I don't know if the debug logs spit out the BEGIN TRANSACTION preamble

Oh that makes sense. I will dig further.

I do remember looking into this when I was first implementing this https://www.sqlite.org/lang_transaction.html
My goal was maximum read throughput. I opted for deferred because of the official documentation

IMMEDIATE causes the database connection to start a new write immediately, without waiting for a write statement. The BEGIN IMMEDIATE might fail with SQLITE_BUSY if another write transaction is already active on another database connection.

We'll just need to make sure that reads don't start explicit transactions, that might require some changes.

That would definitely have to happen.

Regarding the logging, DBConnection used to log begin for everything until I made this change:: https://github.com/elixir-ecto/db_connection/pull/297.
But it requires the adapter to changes its return value from handle_begin and I can't remember if I made a PR for that to exqlite.

to point out the pitfalls of using the different modes

FWIW I feel like it's enough for a library to document the option, say briefly what it controls and then link to the database docs to get more information. In my experience, documenting things like pitfalls tends to have the same issue as online tutorials where they can become out of date. People should ideally not rely on Ecto to teach them how to use their database. That should be knowledge they have before touching Ecto.
That's just my $0.02 though. It's obviously your call!

EDIT: I personally think it is wiser to leave that up to the caller to explicitly call out an exclusive or immediate lock is desired, but err on the side of deferred. I could document this better in the readme to point out the pitfalls of using the different modes and let the programmer decide when to use the mode.

I'd really love it if the default transaction mode could be a configurable option in the Ecto.Adapters.SQLite3 config (rather than having to specify immediate on every transaction invoke individually).
I use BEGIN IMMEDIATE for all my SQLite transactions across the board for this reason: https://kerkour.com/sqlite-for-servers#use-immediate-transactions

@dkulchenko 👋
Would something like this work instead of adding extra configuration options?
defmodule MyApp.Repo do
  use Ecto.Repo, adapter: Ecto.Adapters.SQLite3, otp_app: :my_app

  def immediate_transaction(fun_or_multi) do
    transaction(fun_or_multi, mode: :immediate)
  end
end

@dkulchenko 👋
Would something like this work instead of adding extra configuration options?
defmodule MyApp.Repo do
  use Ecto.Repo, adapter: Ecto.Adapters.SQLite3, otp_app: :my_app

  def immediate_transaction(fun_or_multi) do
    transaction(fun_or_multi, mode: :immediate)
  end
end

Good call! That definitely works too :)

@ruslandoga, that's actually a super simple solution... I wish I had thought of it.

Yeah that's a great idea. Should we close this issue then?

Yea.


UI Elements add/edit/delete added

@drurenia Merge conflict due to recently merged PR #97.

@chill117 Sorry, just saw your comment. Have you fixed the conflict or should I fix and send another PR?

Yes, the conflicts have already been resolved.


Cannot remove multi-digit country codes with delete key, with autoformat

As seen in this gif, i am actually trying to delete digits from country code when country code is multi digit, it does not seem to be able to remove them. But works fine with single digit country codes.
This issue only appears when auto-format is enabled, and i seem to be able to select the country code with double tap and can remove it than, but not normally.
I am testing on iOS simulator(iphone Xs max) as i am still in dev mode.
Version of library: 0.2.2
RN: 0.59.9

Same happening with RN 0.60.1. Removing "autoFormat" fixed the issue.

Hey guys. I know I am pretty late here but I recently started using this library and I also faced the same issue and I resolved this with a simple listener on onChangePhoneNumber, simply create a boolean state and check the length of your text and toggle auto formatting accordingly.
Refer below:

const [autoFormatPhoneNumber, setAutoFormatPhoneNumber] = useState(true);
<PhoneInput
textStyle={{color: 'black', fontSize: 17}}
ref={phoneNumber}
onChangePhoneNumber={text =>
text.length < 5
? setAutoFormatPhoneNumber(false)
: setAutoFormatPhoneNumber(true)}
autoFormat={autoFormatPhoneNumber}
/>

Hope this helps someone.


Revert "Create one NPM package for node/browsers/webpack (#732)"

This reverts commit e14b85a297448dd572744d4263d5b98c0ebe1569, since the Playground is broken.
I imagine it's a very small change, but reverting quickly as per https://github.com/prql/prql/blob/main/CONTRIBUTING.md.
@charlie-sanders do you know what we need to change? Is there any quick test we can have to ensure the playground works? As you know, JS is not my area...

Ugh this was a sloppy mistake on my part, this should not have changed any rust code, let me try again.

No prob @charlie-sanders ! "Better to have merged and reverted than never have merged at all"


Fixed up the Nelson ODE function

Checklist

[x] Appropriate tests were added
[x] Any code changes were done in a way that does not break public API
[x] All documentation related to code changes were updated
[x] The new code follows the
contributor guidelines, in particular the SciML Style Guide and
COLPRAC.
[x] Any new documentation only uses public API

Additional context
Hello! My name is Nina De La Torre, and I wrote this ODE function! It was such a pleasant surprise to see it on the Julia documentation website, but the version that was used was unfinished, and I wanted to fix it up a bit. Anyways, here is the same function but a bit nicer to look at, with helpful comments, parameters, and a cute name. I am planning to request updates the other nelson files as well. I hope this is helpful!
Kindly,
Nina

Hi! Stella showed me this example to turn it into a benchmark, but of course I don't know the model all that much so thank you for your contributions.
Note that this repo is the website output files, but it's generated by https://github.com/SciML/SciMLBenchmarks.jl. Thus the files here shouldn't be updated directly, instead https://github.com/SciML/SciMLBenchmarks.jl/blob/master/benchmarks/AstroChem/nelson.jmd should be updated and the CI will automatically generate the results from the script. Could you make a PR to the generator with these changes?

Hello! I’ll create a new pull request on the generator soon. No reason for
the high tolerances, I just thought it made a fun looking graph. HCO+ just
happens to have very small values, most of the other species don’t
experience visible solver issues. I think the Rosenbrock (Radaus4) methods
worked best for me even with high tolerances though.
On Thu, Oct 24, 2024 at 11:12 PM Christopher Rackauckas <
@.***> wrote:

@.**** commented on this pull request.
In markdown/AstroChem/nelson.md
https://github.com/SciML/SciMLBenchmarksOutput/pull/7#discussion_r1815969160
:

+sol2 = solve(prob, FBDF())
+sol3 = solve(prob, QNDF())
+sol4 = solve(prob, CVODE_BDF())

Is there a reason for using the high tolerances here? That's almost
certainly the reason why they are different from the reference.
—
Reply to this email directly, view it on GitHub
https://github.com/SciML/SciMLBenchmarksOutput/pull/7#pullrequestreview-2394126556,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BHYFG4J4IMKOMFB64QEZUJ3Z5HAJ7AVCNFSM6AAAAABQSLURVWVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDGOJUGEZDMNJVGY
.
You are receiving this because you authored the thread.Message ID:
@.***>


nydusify: abort oss blob upload if conversion failed

We have used PutObject to upload oss before, so if there is any failure during
conversion process, it will cause the uploaded blob to be left on oss, and these
blobs are hard to be GC-ed, so we need always to use the multipart upload, and should
call the AbortMultipartUpload method to prevent blob residue as much as possible
once any error happens during conversion process.

/retest

@bergwolf ping~


will there ever be inline comments?

hello, I was working on 1 project with my colleges and we consider to have possibility to add description directly to request fields, regular inline comment // comment, but blueprint of course reports errors, is it possible somehow?

Hi @andylaci,
This is a tracked feature in #139 about supporting comments. Would you be able perhaps elaborate on adding comments to the request fields in #139. Perhaps showing an example of what you are looking to comment would be great.
I'm going to close this issue as it's tracked in #139, thanks for reporting and sharing more insight into the type of comments you're looking for.


ebcli claim-type hotfix

[x] Targeted PR against correct branch
[ ] Linked to github-issue with discussion and accepted design OR link to spec that describes this work.
[ ] Wrote tests
[x] Updated relevant documentation (docs/)
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[x] Reviewed Files changed in the github PR explorer

For Admin Use:

Added appropriate labels to PR (eg. wip, ready-for-review, docs)
Reviewers Assigned
Squashed all commits, uses message "Merge PR #XYZ: [title]" (coding standards)

@denalimarsh The README change looks incorrect. You just burn cETH on Cosmos again now, instead of checking the functionality to burn the eATOM on ethereum and unlock the ATOM on cosmos.
code fix looks good.

@denalimarsh The README change looks incorrect.

Noted, will wind back the README change

@musnit pushed an updated README version for review: https://github.com/cosmos/peggy/pull/99


Support for presigned URLs

By default, all Amazon S3 objects are private, only the object owner has permission to access them. However, the object owner may share objects with others by creating a presigned URL (docs).
Currently Cloud Storage Extension doesn't support presigned URLs and requires a connection object with credentials.
Please consider implementing support for presigned URLs.

Hi @morazow , I'm trying to use the export that is mentioned here https://docs.exasol.com/db/latest/sql/export.htm with minio. Does this support it? And can we the presigned url here?
Thanks for help

Hi @ShadyD45.
Presigned AWS URLs are supported only for IMPORT command (see CHANGELOG: IMPORT allows accessing public files and presigned URLs from Amazon S3). IMPORT from presigned URLs for S3-compatible services could work, but this setup is not being actively tested.
The rest could be discussed in a Support ticket 😉

Closing this ticket, since this feature is not on the roadmap.


Add back MAX_PENDING_CONSENSUS_TRANSACTIONS

This seems like a quick way to avoid consensus getting overloaded.
Closes #7201

Yeah it is a bit high for now but I think it is a reasonable threshold based on the TPS goal. I don't want to forget about the limit and have to rise it later .. We can definitely decrease it or tune if it turns out to place too much burden on Narwhal in some circumstances.


NDArrayIter fails on large data (bug in tensor_blob.h)

print X_train.shape, Y_train.shape, X_train.nbytes
print X_val.shape, Y_val.shape, X_val.nbytes
print X_test.shape, Y_test.shape, X_test.nbytes
(212700, 6, 119, 119) (212700,)<PHONE_NUMBER>0
(70900, 6, 119, 119) (70900,)<PHONE_NUMBER>0
(70900, 6, 119, 119) (70900,)<PHONE_NUMBER>0

#
#
#
t0 = time.time()
batch_size = 100
train_iter = mx.io.NDArrayIter(data=X_train, label=Y_train, batch_size=batch_size)
val_iter = mx.io.NDArrayIter(data=X_val, label=Y_val, batch_size=batch_size)
test_iter = mx.io.NDArrayIter(data=X_test, label=Y_test, batch_size=batch_size)
print 'iterators configured', time.time()-t0, 'seconds'

---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-6-713633301713> in <module>()
      4 t0 = time.time()
      5 batch_size = 100
----> 6 train_iter = mx.io.NDArrayIter(data=X_train, label=Y_train, batch_size=batch_size)
      7 val_iter = mx.io.NDArrayIter(data=X_val, label=Y_val, batch_size=batch_size)
      8 test_iter = mx.io.NDArrayIter(data=X_test, label=Y_test, batch_size=batch_size)

/home/dhaehn/D1/lib/python2.7/site-packages/mxnet/io.pyc in __init__(self, data, label, batch_size, shuffle, last_batch_handle, data_name, label_name)
    577         super(NDArrayIter, self).__init__(batch_size)
    578
--> 579         self.data = _init_data(data, allow_empty=False, default_name=data_name)
    580         self.label = _init_data(label, allow_empty=True, default_name=label_name)
    581

/home/dhaehn/D1/lib/python2.7/site-packages/mxnet/io.pyc in _init_data(data, allow_empty, default_name)
    485             except:
    486                 raise TypeError(("Invalid type '%s' for %s, "  % (type(v), k)) + \
--> 487                     "should be NDArray or numpy.ndarray")
    488
    489     return list(data.items())

TypeError: Invalid type '<type 'numpy.ndarray'>' for data, should be NDArray or numpy.ndarray

but the error actually comes from tensor_blob.h
a = mx.nd.array(X_train[0:50000]) # no problem
a = mx.nd.array(X_train[0:60000]) # fails
MXNetError: [16:37:29] include/mxnet/././tensor_blob.h:247: Check failed: this->shape_.Size() == shape.Size()<PHONE_NUMBER> vs. 802992704) TBlob.get_with_shape: new and old shape do not match total elements

Stack trace returned 10 entries:
[bt] (0) /home/dhaehn/D1/lib/python2.7/site-packages/mxnet/libmxnet.so(+0x18b0dc) [0x7f655a9510dc]
[bt] (1) /home/dhaehn/D1/lib/python2.7/site-packages/mxnet/libmxnet.so(+0x27d680) [0x7f655aa43680]
[bt] (2) /home/dhaehn/D1/lib/python2.7/site-packages/mxnet/libmxnet.so(+0x27db65) [0x7f655aa43b65]
[bt] (3) /home/dhaehn/D1/lib/python2.7/site-packages/mxnet/libmxnet.so(+0xc8047d) [0x7f655b44647d]
[bt] (4) /home/dhaehn/D1/lib/python2.7/site-packages/mxnet/libmxnet.so(+0xc5d29b) [0x7f655b42329b]
[bt] (5) /home/dhaehn/D1/lib/python2.7/site-packages/mxnet/libmxnet.so(MXNDArraySyncCopyFromCPU+0xa) [0x7f655b2f0a1a]
[bt] (6) /lib64/libffi.so.6(ffi_call_unix64+0x4c) [0x7f66065e3dcc]
[bt] (7) /lib64/libffi.so.6(ffi_call+0x1f5) [0x7f66065e36f5]
[bt] (8) /home/dhaehn/D1/lib64/python2.7/lib-dynload/_ctypes.so(_ctypes_callproc+0x30b) [0x7f66067f6c8b]
[bt] (9) /home/dhaehn/D1/lib64/python2.7/lib-dynload/_ctypes.so(+0xaa85) [0x7f66067f0a85]

# but..
a = mx.nd.array(X_train[50000:80000]) # no problem

This is related to #6195

as stated in #6195 we need 64bit indexing

I've posted a comment in #6195 that addresses this issue, maybe it could help you?

This issue is closed due to lack of activity in the last 90 days. Feel free to ping me to reopen if this is still an active issue. Thanks!
Also, do please check out our forum (and Chinese version) for general "how-to" questions.


Site Improve - User Feedback Feature  (from 2024)

Problem Description:
Site Improve has a user feedback feature available to use. This feature will allow us to create a survey, containing one question, which can then be displayed on a specific URL page of our choosing.
Expected Behavior/Solution:
The Feedback Survey shows on the desired URL, with our desired layout and rating system and we are able to track and receive this feedback from Site Improve/Email notifications.
Requirements:

Feedback Survey appears in all URL's which contain the snippet of https://lux-front-tst.collections.yale.edu/view/
Feedback Survey has the desired question displayed: How was your experience using LUX?
Feedback survey is displayed in the middle on the right hand side
Feedback Survey displays a smiling rating style.
Feedback survey requires a rating and has its comment box set to optional.
External link redirects user to the User Testing survey.
The submission of a survey or the selection of don't show this again will prompt the survey to disappear for the remainder of the user session.
Metrics will be added to the Heart Framework Dashboard.

Needed for promotion:
If an item on the list is not needed, it should be crossed off but not removed.
- [ ] Wireframe/Mockup - Heather

[x] Setting up Feedback Survey - Amy
[x] Testing survey in LUX-TST - Amy
[ ] Committee discussions - Sarah
[ ] Feasibility/Team discussion - Sarah
[ ] ~Backend requirements - TBD (might need depending on what Zach says)~
[ ] Frontend requirements- TBD
[ ] Questions
List of questions for discussions. Answers should be documented within the issue.

UAT/LUX Examples:

https://lux-front-tst.collections.yale.edu/view/results/objects?q={"AND"%3A[{"text"%3A"andy"%2C"_lang"%3A"en"}%2C{"text"%3A"warhol"%2C"_lang"%3A"en"}]}&sq=andy+warhol
Site Improve Dashboard: Heart Framework

Dependencies/Blocks:

~Blocked By: Sylvia's LUX Assessment plan (in development)~
Site Improve Support Ticket

Related Github Issues:
N/A
Related links:

Steps to creating a user feedback survey
Prioritizing feedback
https://my2.siteimprove.com/Settings/359298/AnalyticsFeedback/Index

Wireframe/Mockup:
Current:

Expected:

From UX/BA 9/25:
This was approved by the team in TST.
Sarah T will update the survey  link to keep the LUX checkbox hidden as this survey link will only be accessible to those coming from the LUX site.
Next steps: UAT reviewal

This was approved by UAT on sept 27. Closing as it is now in production and working fine.


chore: add "release" workflow

Adds a new "release" github workflow to automatically publish the addon to NPM every day.

You're the best @kettanaito <3


⚠ Samsung has degraded performance

In 6bbd360, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2486 ms

Resolved: Samsung performance has improved in 5b97e41.


Filter out unpublished content from REST API

Pre-Flight checklist

[x] Testing

[x] Code is tested
[x] Changes have been manually tested

What are the relevant tickets?
Fixes #520
What's this PR do?
Adds a filter to the website content REST API so that unpublished content is not visible
How should this be manually tested?
TBD
View the website content list view REST (for example http://localhost:8043/api/websites/res-8-001-applied-geometric-algebra-spring-2009/content/) for a website you imported but never published. It should have no content. A website which is published should have some content in the REST API.

It looks like WebsiteContent which is created is automatically synced to main but not to the preview or release branches. So there isn't going to be an easy way to produce a case to show that the relation field correctly filters out unpublished content, without manually unpublishing it via the Django admin.
This also brings up another question. If it is published to main but not to preview or release, then it effectively still does not exist in the git repository for those two branches. I don't think we keep track of whether we published to a particular branch, just whether we published at all. I'm not sure how to proceed there


bug: Fix invalid package_name value

😢

Lint failed but let's merge first and will fix it later.

Lint failed but let's merge first and will fix it later.


Added Efficiency Improvements in the code. Including fast versions of…

This update adds efficiency improvements to the apply and gauge functions by minimising the amount of graph analysis that is done.
Additionally:

The apply function for a tn in the Vidal gauge places the site-index on the QR decomp relative to whether a gate is being applied.
A fast version of dag(tn::AbstractITensorNetwork) has been added
A function unflattened_norm_network(tn::AbstractITensorNetwork) has been added which is faster than using ⊗
An example has been added to demonstrate different gauging routines

Not really sure what is going on in test_apply here (which is why the tests are failing?). The changes to
function ITensors.apply(   o::Union{ITensor,NamedEdge},   ψ::AbstractITensorNetwork,   bond_tensors::DataGraph;   normalize=false,   apply_kwargs..., ) appear to have made the apply function extremely accurate for the simple update case and hence its accuracy is far higher than the belief propagation version (whereas they were identical before).
There must be a bug there as they should probably not be that accurate..

What if you switch back from qr(...) to factorize(...; cutoff=1e-16), do the tests pass? Otherwise it seems like the rest of the changes are either independent of those tests or just code reoarganization.

I'm confused by why you are saying SU gauging is now more accurate, it looks less accurate to me with the latest commit.

Okay those bugs should be fixed now and all tests should pass.

Codecov Report

Merging #94 (d7ca39d) into main (34fd5dc) will increase coverage by 0.05%.
The diff coverage is 90.90%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main      #94      +/-   ##
==========================================
+ Coverage   79.25%   79.30%   +0.05%
==========================================
  Files          61       61
  Lines        3442     3465      +23
==========================================
+ Hits         2728     2748      +20
- Misses        714      717       +3

Impacted Files
Coverage Δ

src/apply.jl
89.26% <73.68%> (-1.96%)
:arrow_down:

src/abstractitensornetwork.jl
82.66% <100.00%> (+0.77%)
:arrow_up:

src/gauging.jl
100.00% <100.00%> (ø)

Thanks!


Add Dev to Evidence: Start Server and Stop Server command titles

per comments in #32

[x] Update those command titles in package.json
[x] Update Commands section in 'README.md`
[ ] Update commands pic in docs/images

This is done. Commands image in docs will be updated when v1.1.0 is ready to be released.


[kb for admins: configuration options] add missing parameters

There is no description for parameters releated to:

rate limiting filter
proxy filter

implemented.


Fix regressions in buffer settings initialization

Fix regressions after ba98b55:

Unable to override filetype autodetection by setting a specific filetype for specific files, i.e. this doesn't work:
 "*.h": {
     "filetype": "c++"
 },

Unable to enable/disable syntax highlighting for specific files, i.e. this doesn't work:
 "*.c": {
     "syntax": false
 },

"readonly" setting doesn't work (neither global nor per-filetype).

Note that the behavior is still not ideal: cannot set syntax option per-filetype via "ft:" with autodetected filetype, e.g. this doesn't work:
    "ft:c": {
        "syntax": false
    },

To fix it, need to separate the filetype autodetection from the highlighter setup in UpdateRules.

I was not able to reproduce the issues you mentioned (for the filetype and syntax), but did experience the issue specifically for the readonly option so I have merged the fix. I can't reproduce the syntax issue which you say is still a problem after this PR. Could you elaborate on that?

Hmm, I'm not sure why you can't reproduce these issues. I've double-checked that I do reproduce them on a clean build with a clean config dir.
Could you double-check with these 3 tests?

Run e.g. micro internal/buffer/buffer.go with the following settings.json:

{
    "*.go": {
        "filetype": "c"
    }
}

Result:

before this PR: the statusline shows "ft:c" but the file is highlighted as a Go file, not a C file (the reason is that filetype was set to "c" only after UpdateRules).
after this PR: the file is hightlighted as a C file, as expected.

With the following settings.json:

{
    "*.go": {
        "syntax": false
    }
}

Result:

before this PR: the file is highlighted.
after this PR: the file is not highlighted, as expected.

With the following settings.json:

{
    "ft:go": {
        "syntax": false
    }
}

Result:

before this PR: the file is highlighted.
after this PR: the file is still highlighted.

BTW, how I noticed these issues in the first place: due to non-deterministic filetype detection for *.h files, sometimes they are highlighted as C and sometimes as Objective-C (I've created issue #2041 for it), so I force c++ filetype for *.h files to have the same highlighting each time. It stopped working after ba98b55, so I fixed it in this PR.


[Bug]-[22500]:The evaluated value is displayed as undefined in google sheets

Description
[What happened]The evaluated value is displayed as undefined
Steps to reproduce the behaviour:

Important Details

Version: [Cloud ]
OS: MacOS
Browser chrome,
Environment  release

Stats

Stat
Values

Reach
1800

Effort (months)
<>

This is not reproducible anymore since the Sheet Name input is now a dropdown with static values


CI and Semantic Release

Currently, better-commits process for deploying looks like this:

manually bump version number in package.json
manually build via npm run build
manually publish via npm publish

Utilizing Github Actions + Semantic Release, we could automate this process. Which would make accepting other user's PRs simpler.
This would be a good first time issue / help wanted -- as I won't be able to get to this for a while

This is probably something I could look into, but it won't be for a few weeks. If the issue is still on here then, I'll take it up.

I'll take this one. Should have something actionable in a few days


Dynamic paths with emhass config dict, some mlforcaster error suppression

Will do more checking tomorrow. Here early for progress and help.
Added Dictionary var containing EMHASS paths
emhass_config dictionary has been created (currently, containing data and config paths) to try and add directory structure consistency though the program.
Currently, if the data path is outside the root EMHASS directory, certain errors may occur from some hard coded paths.
emhass_config tried to change this by  passing in a dictionary to (I believe) all sub models.
MLForcaster error suppression
Added some more error suppression. (more testing should be done)
MLForcaster wise, I'm still not supper confident with how MLForcaster works. My assumption is, if there is missing data in the sensor, that days worth gets rejected, Causing the "ValueError: All arrays must be of the same length" error. (between forecast_dates and forecast_out.).
I have added  an if statement to notify the user of the issue, replacing the ValueError. This however doesn't fix the issue.

the pytests are failing with (I believe) test_main_publish_data. It's a weird issue, will look into tomorrow.

Looks like there are a fer few more issue then I first realized.

ValueError: The provided timedelta will relocalize on a nonexistent time: 0 days 00:30:00

This may be related to the current errors of DST change

I'm still trying to understand the changes proposed in this PR...

@GeoDerp hopefully you can help with a current issue that I have relating to paths.
I added two new database files for updated PV modules and inverters. The files are here: https://github.com/davidusb-geek/emhass/tree/master/src/emhass/data
But when testing using the docker standalone option I kept getting the file not found error. It seems that I'm not properly passing the files to the docker images build. Could you check the current Dockerfile? I think that it is correct but I still get the said error.

I'm still trying to understand the changes proposed in this PR...

Pretty much we want to make sure that our passed data_path and config_path parameters are used throughout EMHASS. Currently there are sections of EMHASS that have datapaths like root + /data/filename. However, this may not always be the case.

I'm still trying to understand the changes proposed in this PR...

Pretty much we want to make sure that our passed data_path and config_path parameters are used throughout EMHASS. Currently there are functions inside of EMHASS that have datapaths set to like: root + /data/filename. However, this may not always be the case if we set the datapath to something like /share.

Ok yes. I get it. It is a good idea to have a proper path management.

@GeoDerp Careful with those conflicts with forecast related files. I made some updates this week. You need to git rebase.

@GeoDerp Careful with those conflicts with forecast related files. I made some updates this week. You need to git rebase.

hahah, I just merged them

def test_main_publish_data(self):
opt_res = main()
self.assertFalse(opt_res.empty)

I just changed this so all tests passed. Feel free to revert. Will be away for a few days. Feel free to have a look/adjust/implement in the mean time. Will defiantly recommend some tests to confirm everything is functional.

I just changed this so all tests passed. Feel free to revert. Will be away for a few days. Feel free to have a look/adjust/implement in the mean time. Will defiantly recommend some tests to confirm everything is functional.

But this is not ready to merge right?

I just changed this so all tests passed. Feel free to revert. Will be away for a few days. Feel free to have a look/adjust/implement in the mean time. Will defiantly recommend some tests to confirm everything is functional.

But this is not ready to merge right?

I wouldn't be confident until I ran some more tests. But I also trust that you can do the same if you like to merge it sooner.

Having a look over the PR now, will likely be finished tomorrow night.

Will check over the latest changes tomorrow to confirm everything should be good to go.

@davidusb-geek , Alright I'm pretty happy with it, I may be missing some places where its still using the old path system, but I  believe everything is functional. Feel free to test yourself and see what you think.
The two things i'm unsure about is how well special_config_analysis.py and save_pvlib_module_inverter_database.py  works as I'm unable to test it.

@davidusb-geek , Alright I'm pretty happy with it, I may be missing some functions, the old path system is still used. But, from my testing, I believe everything is functional. Feel free to test yourself and see what you think.
The two things I'm unsure about is how well special_config_analysis.py and save_pvlib_module_inverter_database.py works as I'm unable to test it.

Ok it will be merged and tested, probably over the week-end. For those 2 files I can check them, but those are just auxiliary scripts files.


Python PreCommit finished with just dataflow worker image errors


Snow doesn't work in Firefox 8.0

Works fine in Chrome. Don't know if it's a firefox issue.
Details: Windows 7 x64 professional

I changed a variable name and obviously didn't double-check on Firefox. Fixed. (at least on FF 8 on the Mac).


Allow down and upSize for reshape

(related to #19)
Moreover having downsize and upsize for reshape makes sense to, otherwise
people will end up with something like this:
auto s = iota(4).sliced(2, 2);
assert(s[0..1,0..2] == [[0, 1]]);
assert(s[0..2,0..1] == [[0], [2]]);

Which works nicely if we just "cut" a slice, however once we don't we have to do such an ugly pattern:
auto s2 = iota(9).sliced(3, 3);
assert(s2.byElement.sliced!(Yes.replaceArrayWithPointer,
       Yes.allowDownsize)(4, 1) == [[0], [1], [2], [3]]);

can maybe be part of #77 - closing for now then.


Add in better native parquet footer implementation and remove the old one

This uses the new API to provide a good implementation that fixes the issues older parquet files (legacy ones).
This depends on https://github.com/NVIDIA/spark-rapids-jni/pull/362
I think this will fix https://github.com/NVIDIA/spark-rapids/issues/5493 because it does not reorder the columns like the old implementation did.

build

build

In addition to my left comments, I have no idea if we can have unit tests in this repo?

The problem with tests is that the only way to test it is with parquet files. We could do some round trip tests and see that it works properly, but I found it was much simpler to test it in the plugin itself. I know there are some big downsides to this and if we really want to be alerted earlier if there is a regression I can add tests here.

I know there are some big downsides to this and if we really want to be alerted earlier if there is a regression I can add tests here.

The critical thing for me is that it is tested regularly and hopefully in an automated way. If we don't know about a breakage until the spark level, I'm not that concerned as long as testing is done.

build

@hyperbolic2346 and @ttnghia could you take another look

build

@hyperbolic2346 can you please take a look at the latest changes?

@hyperbolic2346 thanks for the new review I think I have addressed all of your comments. Please take another look

build


[FEAT] Please add tabs layout

Hi all, please add tabs layout like facebook. Thanks

Hey @bangdragon ,
Thank you for contacting us! Could you please share some more details?

Hi Omer, i want my app to use tabs not sider.

Actually, what i want is when create refine app from npx, it allow to choose between sider and tabs layout. Thanks

hi @bangdragon, You can create your own tabs menu. can you check it topMenuLayout example does this work for you?

hi @bangdragon, You can create your own tabs menu. can you check it topMenuLayout example does this work for you?

hi @biskuvit, i still don't know to create tabs layout. I wish when create app with npx there is tabs layout to choose. Like ionicframework has this feature.


Add README.md to describe the exit demo

Create some description to show the mechanism of the exit demo.
In this demo, I use setup thread to indicate thread 0 at the beginning.
After it calls the counter() function, I use counter to describe the thread instead.

I think we can set the name of the initial thread to counter to seperate thread 0 and the other 2 threads.
Shall we work on this change?

It would be cool to add a page to docs/ that links to all the ones so far, to give a rough reading order. (the same order you're adding them)

Sounds great. I think I will add it with another PR.

I updated the commit. This commit includes the introduction of thread_start.

I think we can set the name of the initial thread (thread 0) to counter to seperate thread 0 and the other 2 threads.
Shall we work on this change?

Yeah do that and also remove the yield() call in setup, it's not adding anything.

OK, I have modified the demo and split it into 2 commits.

Took me a bit to wrap my head around why removing the yield() didn't change the demo output more but I eventually got there. Another sign it was a good all to remove it!

Btw, I've been thinking that having separate tests as well as the demos might be a good move. There's some things that are just randomly jammed into demos where they don't really fit.
If you see stuff like that please call it out.


System.err: a.a.a.a.a.ac

Hello,
I am using the cloudsdk and used gradle to import the dependency (io.particle:cloudsdk:0.3.4. What I'm trying to achieve is to login using the Particle cloud sdk, get a list of devices and communicate with them. When it is in debugging mode, everything works fine. In release, I added the oauth credentials inside the strings.xml file. I get the following message when I try to login:
W/System.err: a.a.a.a.a.ac
06-28 01:46:08.516 952-1030/? W/System.err: at a.a.a.a.a.y.a(Unknown Source)
06-28 01:46:08.516 952-1030/? W/System.err: at com.bmertech.activities.k.a(Unknown Source)
06-28 01:46:08.516 952-1030/? W/System.err: at com.bmertech.activities.k.doInBackground(Unknown Source)
06-28 01:46:08.516 952-1030/? W/System.err: at android.os.AsyncTask$2.call(AsyncTask.java:292)
06-28 01:46:08.516 952-1030/? W/System.err: at java.util.concurrent.FutureTask.run(FutureTask.java:237)
06-28 01:46:08.516 952-1030/? W/System.err: at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)
06-28 01:46:08.517 952-1030/? W/System.err: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
06-28 01:46:08.517 952-1030/? W/System.err: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
06-28 01:46:08.517 952-1030/? W/System.err: at java.lang.Thread.run(Thread.java:818)
Thank you for your on-going support,
Nirujan

Without a de-obfuscated stack trace, I'm afraid I can't help you.  You'll need to do something like this: http://simplyadvanced.net/blog/android-how-to-decode-proguards-obfuscated-code-from-stack-trace/

W/System.err: a.a.a.a.a.ac
at a.a.a.a.a.y.a(y.java)
06-28 01:46:08.516 952-1030/? W/System.err: at com.bmertech.activities.k.a(k.java)
06-28 01:46:08.516 952-1030/? W/System.err: at com.bmertech.activities.k.doInBackground(k.java)
06-28 01:46:08.516 952-1030/? W/System.err: at android.os.AsyncTask$2.call(AsyncTask.java:292)
06-28 01:46:08.516 952-1030/? W/System.err: at java.util.concurrent.FutureTask.run(FutureTask.java:237)
06-28 01:46:08.516 952-1030/? W/System.err: at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)
06-28 01:46:08.517 952-1030/? W/System.err: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
06-28 01:46:08.517 952-1030/? W/System.err: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
06-28 01:46:08.517 952-1030/? W/System.err: at java.lang.Thread.run(Thread.java:818)

Looks like that's the same stack trace as above.  Can you make a release build with proguard disabled and try reproducing this?

Looks like it worked without proguard? Thanks!

Cool, glad to hear it's working without Pro Guard at least.
Try adding rules to keep io.particle.** and let me know how that goes. If that works, I will add that to our documentation!

That worked for me!

Brilliant, thanks for the update!


WFLY-3095 Weld subsystem exposes way too much dependencies to user deployment

…ployment

Linux with security manager Build 1454 is now running using a merge of e1f66b39d8cfdaa313b1b72ed54d183eef934e5f

Windows Build 1626 is now running using a merge of e1f66b39d8cfdaa313b1b72ed54d183eef934e5f

Linux Build 6549 is now running using a merge of e1f66b39d8cfdaa313b1b72ed54d183eef934e5f

Linux with security manager Build 1454 outcome was SUCCESS using a merge of e1f66b39d8cfdaa313b1b72ed54d183eef934e5f
Summary: Tests passed: 823, ignored: 319 Build time: 0:05:58

Linux Build 6549 outcome was SUCCESS using a merge of e1f66b39d8cfdaa313b1b72ed54d183eef934e5f
Summary: Tests passed: 2873, ignored: 374 Build time: 0:47:47

Windows Build 1626 outcome was SUCCESS using a merge of e1f66b39d8cfdaa313b1b72ed54d183eef934e5f
Summary: Tests passed: 2873, ignored: 374 Build time: 0:48:55


Don't use panic-happy prometheus client With() function

Deals with part of #405, although it doesn't deal with the underlying
label error that is occuring.

@oldmantaiter The one-liner With() function is nice, but I'd rather use the one that won't panic in the case of an error. This change prevents the panic and logs an error.

@sparrc Absolutely, that makes a lot more sense. I should have looked for a solution like this in the beginning when I hit the issue, my apologies!

@oldmantaiter No problem :-), IMHO the With() function that panics shouldn't even exist in the prometheus library, looks like someone was trying to shim ruby/python syntax into Go


Improve many sprites example

Objective
My attempt at fixing #2075 .
This is my very first contribution to this repo. Also, I'm very new to both Rust and bevy, so any feedback is deeply appreciated.
Solution

Changed move_camera_system so it only targets the camera entity. My approach here differs from the one used in the cheatbook (in which a marker component is used to track the camera), so please, let me know which of them is more idiomatic.
move_camera_system does not require both Position and Transform anymore (I used rotate for rotating the Transform in place, but couldn't find an equivalent translate method).
Changed tick_system so it only targets the timer entity.
Sprites are now spawned via a single spawn_batch instead of multiple spawns.

I think we should merge this over #2075; be sure to credit @neosam in the appropriate places too however.

I disagree with the addition of the _system prefix, but other than that it looks good

bors r+

bors retry


Ignore empty keys in QueryStringValueProvider

Fixes #8484

Note that this is going in to master (3.0)


Pavilion Silently fails when quotes are not around some values in yaml files

With the current version of pavilion missing quotes around time_limit in the yaml files will cause it to fail without error. This has been fixed in 3790a3fb3e5141cc47f0d707094303585a018f8b but I am not sure that there are not other cases where this is also a problem.

Trying to catch this for every value will significantly increase the code base and the only place where it seems like it will be a large issue is for time which is now caught and documented in the default_test_config.yaml file.


Move FactCheck from REQUIRE to test/REQUIRE

since it's a test-only dependency

https://github.com/JuliaLang/JuliaParser.jl/commit/61ed9a5e6cb206179febd36a59d574e743877857


Bug: failed to get segment

What happened?
A bug happened!
Steps to reproduce
Transcription of a 40 minute file, ended with this bug
Continuation of this bug:
https://github.com/thewh1teagle/vibe/issues/35
What OS are you seeing the problem on?
No response
Relevant log output
"Error in desktop\\src-tauri\\src\\main.rs at line 60: failed to get segment\n\nCaused by:\n    Invalid UTF-8 detected in a string from Whisper. Index: 119, Length: 1."
options: ModelArgs { path: "C:\\Users\\user\\Downloads\\הקלטה בקו של הקהילה שלנו.wav", model: "C:\\Users\\user\\AppData\\Local\\github.com.thewh1teagle.vibe\\ivrit-ai--whisper-large-v2-tuned-ggml-model_2.bin", lang: Some("he"), verbose: false, n_threads: Some(4), init_prompt: Some(""), temperature: Some(0.4) }

App Version: 0.0.7
Arch: x86_64
Platform: windows
Kernel Version: 10.0.22631
OS: windows
OS Version: 10.0.22631
Models: ggml-large.bin, ivrit-ai--whisper-large-v2-tuned-ggml-model_2.bin
Default Mode: "C:\\Users\\user\\AppData\\Local\\github.com.thewh1teagle.vibe\\ivrit-ai--whisper-large-v2-tuned-ggml-model_2.bin"

Fixed in latest version (0.0.8).
You can update from the main window in vibe or download it from thewh1teagle.github.io/vibe
Also I tested it on 1 hour video, and it worked.
Feel free to reopen the issue,
and please let me know if it fixed :)


Added allowFullScreen prop to video content iframes

Fixes #2398
Changelog Entry
Added full screen capability to iframes in the YouTubeContent and VimeoContent components by @tdurnford in PR #2399
Description
See Changelog entry

[ ] Testing Added

Coverage remained the same at 65.201% when pulling d2397f0a3159d4e6bc396166668adf38c317efdf on tdurnford:2398 into 928217408c853e261cd3fcba69604228e72a3bdb on microsoft:master.


Implement http::Get and http::Post methods

Whew, it's a biggie!
This all looks pretty reasonable to me, although I haven't yet dug into how uv and curl work.
When you're ready for a full review, let us know. To keep the review size manageable I suggest that we first review just the Get() method, become happy with that, and then continue to review the Post() method. Could still be in one PR (with multiple back-and-forths), or if you want to split it into two PRs that's bonus points.


New version: Juniper v0.4.3

Registering package: Juniper
Repository: https://github.com/lanl-ansi/Juniper.jl
Created by: @Wikunia
Version: v0.4.3
Commit: 8d927926d2ccbab1f5e406bafb777f9dd6372ce3
Reviewed by: @Wikunia
Reference: https://github.com/lanl-ansi/Juniper.jl/issues/152#issuecomment-526926022

Can you also add
[compat]
julia = "1"

and retrigger?

Out of curiosity is that the same as "^1" @fredrikekre ?
Will do

Yes, see https://julialang.github.io/Pkg.jl/v1/compatibility/

@fredrikekre can we get this merged?


Storage Account Names are too Long

With the new implementation of the ${appEnvironment} parameter, storage account names are now too long. This could even get worse when a full region short name list is implemented.
I suggest using the uniqueString fucntion. For example:
Diagnostics Storage Account
var storageAccountName = replace('sa-diags-${uniqueString(resourceGroup().id)}', '-', '')

Modified to use the uniqueString funciton for the subscription ID.


FIX: Use as_json instead of to_json for chat DM message bus

Follow up to f1fb1d0b4843b6265a6f46d8b24c31930a69c015,
in this commit I accidentally changed as_json (which produces
a Hash) to to_json (which produces a JSON string) in the
ChatPublisher for the new DM channel. This makes the MessageBus
data unparseable, so in JS in the chat service it ends up creating
a public channel in the channel list with undefined data, leaving
a blank channel in the list with a blue unread indicator.
Before fix MessageBus data:

After fix MessageBus data:

UI error:

Thanks Martin. Your descriptions are the best.

@nattsw thank you! :bowing_man:


feat(pins): add support for custom storage options in board_s3

Introduce the ability to pass arbitrary storage options to the underlying fsspec S3FileSystem in board_s3.
This enhancement allows for greater flexibility when connecting to S3-compatible services by enabling the specification of custom credentials, endpoints, and other S3FileSystem parameters.
Added documentation and examples to illustrate how to use the new storage_options parameter, including an example for connecting to Backblaze B2.

This change enables users to more easily integrate with a variety of S3-compatible storage solutions, improving the library's versatility and user experience.
Address issue: #235
Tag @isabelizimm!

@isabelizimm @machow I think I'm running into an issue with the docs, but I'm not quite sure how to address the issue, as it uses quartodoc (which I'm happy to learn, but may need help getting up-to-speed on).
In case it's helpful, this is a direct link to the exact line that is failing.

Ah thank you so much for putting up this PR! Let me peek at the docs failures and run the tests on other backends to see if something jumps out  👀

One small nit, but everything else looks great! 😄

Woot! Looks like all of the non-skipped stuff passed :smile:.

Okie dokes, just pushed the requested change, @isabelizimm!


Main

Hey, did you resolve the issue? Or is there something that you think needs to be addressed?
Thanks.

My apologies for the confusion. The pull request was intended for my personal forked copy of your repository, not your master repo. Despite that, I do have a question regarding the implementation.
I was trying to generalize the implementation of DeformableRegistration.update_transform() to accommodate a vector-valued sigma2, which allows each gmm centroid to have a different covariance value.
In the step where eq.22 in the original paper is solved for, I changed
 A = np.dot(np.diag(self.P1), self.G) + self.alpha * self.sigma2 * np.eye(self.M)

to
A =  self.G @ np.diag(self.P1) + self.alpha * np.diag(self.sigma2)     derivation)

Do you think this is the correct generalization?

That looks like it would work great for that reason. The only comment is that it looks like you changed the order of the dot product (@) which would change that result.


[refactor] Abstracted isResponseEmpty conditional in a separate method

Motivation
I want to help with some Architecture clean up to help make RestHooks's codebase easier to read and to contribute from a large audience.
Some nit:

logic abstraction
fix some spacing
fix some style comments

I will help with more general nits before I get into the real problems, let me know @ntucker if you don't mind those changes.
Thank you for this great library.

Oh and let me know if you prefer different naming or coding changes.

Thanks for the PR, I'd love to accept these improvements with the small feedback mentioned. :)

@ntucker updated the PR 😄


opa version upgrade to latest

Description
To maintain compatibility with previous KE versions, we initially introduced the result. New feature to all Rego scripts on the server level. However, we encountered an error within StarBoard. This problem arises from the utilization of "dots in rule heads," which is not compatible with the current OPA version employed by StarBoard. As a resolution, updated the OPA version used within StarBoard to the most recent one. Reference: https://github.com/open-policy-agent/opa/issues/4653

 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.Kiran Bodipi seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


icons.svg loading problem with CDN

When using CDN, I got this error and can't load icons.svg
XMLHttpRequest cannot load https://cdnjs.cloudflare.com/ajax/libs/Trumbowyg/2.1.0/ui/icons.svg. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:3000' is therefore not allowed access.

You can reproduce with changing index.html.
<!DOCTYPE html>

        <meta charset="UTF-8">
        <title>Trumbowyg by Alex-D</title>
        <link rel="stylesheet" href="css/main.css">
        <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/Trumbowyg/2.1.0/ui/trumbowyg.min.css">

Default usage of Trumbowyg

                    No plugin, no options. Just naked Trumbowyg.

This editor is the default build of Trumbowyg.

                    Lorem ipsum dolor sit amet, consectetur adipisicing elit. Possimus, aliquam, minima fugiat placeat provident optio nam reiciendis eius beatae quibusdam!

                    The text is derived from Cicero's De Finibus Bonorum et Malorum (On the Ends of Goods and Evils, or alternatively [About] The Purposes of Good and Evil ). The original passage began: Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit (Translation: "Neither is there anyone who loves grief itself since it is grief and thus wants to obtain it").

The code

$('#editor').trumbowyg();

I am not the manager of this CDN version. See here: https://github.com/cdnjs/cdnjs

I see, but following code doesn't work either.
jQuery.trumbowyg.svgPath = 'https://cdnjs.cloudflare.com/ajax/libs/Trumbowyg/2.1.0/ui/icons.svg'

I got same CORS error.
How can I use remote svg file ? Any idea?
Anyway, thank you for this nice editor.

You can't via AJAX :/

Same problem, even with plain http and not https:
XMLHttpRequest cannot load . No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin '' is therefore not allowed access.
The script become unusable from CDN :/
Any idea for workarounds other than include the SVN directly in the source (in facts no CDN) or modify the http headers (too tricky and invasive for my case)? Even better solve this in the main source?

http://alex-d.github.io/Trumbowyg/documentation.html#svg-icons
Check the "Use SVG icons without XHR or via an another protocol that HTTP(S)" section


Formatting as a code Action?

Do you think it would be useful to have automatic code formatting for out .SQL files?
There is https://github.com/andialbrecht/sqlparse, which could be used to build a represented as well.

Absolutely! If there is a way to defer formatting choices to a tool which makes things consistent, I think that would be great.

I added an initial python script to format our SQL files: #16


Update scripts

Also snuck an update of the Sublime Text project file in there.

The Travis build is broken on Travis, due to cortex-m-rt's new minimum requirement. I'm going to leave this as is for now, as it's going to unbreak itself with the next stable release.


BungeeCord error during login (1.13.x only)

What is the output link of /viaversion dump?
https://dump.viaversion.com/4728ef752f0553befb9769d087f42fcfcd3768466d305512a3363139bccb7066
Are you using any additional software like BungeeCord? If so, what software and version? (Please list your plugins as well)
Yes, I'm using latest BungeeCord.
How does this error happen? login? Using an item?
Sometimes it happens when I login using 1.13.1 version to 1.12.2 server. At the time of login the player was in nether (world_nether).
Is there an error in the console? Use pastebin.com. Is there a kick message?
https://pastebin.com/AYYatNac

Could you repastebin etc? As it's not available.

Sorry, but I didn't save it. Now I'm using ViaVersion 1.3.0.

Need the above to fix this, otherwise possibly catch me on our Discord (if you have discord).


Specify tree sitter dependency version to continue use of deprecated method

Language.build_library() was removed in py-tree-sitter v22. Due to no versions being specified in setup.py, the latest version of each dependency is installed by default. I've changed setup.py to match the versions specified in requirements.txt. Also, I bumped the tree sitter dependency to the most recent usable version.
See this discussion for information related to the method deprecation.
Here's some context for where the method is used in the source:
https://github.com/cedricrupb/code_ast/blob/982940d04b1d721e5ac9a97d433f36d1fb47e8e0/code_ast/parsers.py#L188-L196

Hey!
Thanks a lot! I will merge it as soon as I get time for it.
In the meantime, if you want to use v22, there is already a version in the dev that supports it. However, there seem to be some major changes in the (Python) grammars which might break stuff.


About obtaining pose from point clouds

Hi Yan Di, I see the input of your network is P = points - points.mean(dim=1, keepdim=True)，where points  is obtained from the backprojection of the depth map.
In my shallow knowledge, two pieces of information are needed to obtain the pose(R only discussed), the points P=R @ P_ori  after the R transformation and the original points P_ori.
The input of network only has P=R @ P_ori, how does the network get rotationR without knowing the original points P_ori？

In the training of the network, we know the ground truth 9D pose and use it to supervise the network to learn how to transform the observed point cloud into the canonical space.
The canonical coordinate space is pre-defined as in the paper NOCS.
SO during inference, we don't need the P_ori in canonical space

Thank you very much for your reply. I think there may be a sentence to try to explain my confusion:

Understanding the Limitations of CNN-based Absolute Camera Pose Regression (CVPR 2019)

We have also shown that APR(e2e method) is more closely related to image retrieval approaches than to methods that accurately estimate camera poses via 3D geometry.


Skip failed unit tests for s390x

Let's skip the result server rotating unit test for now on s390x so that we get a successful build.

let's wait to see if https://github.com/ComplianceAsCode/compliance-operator/actions/runs/9460690156 has a success run


Change way in which SLURM accounts are exposed

Current status
Currently, there exists several different ways of choosing a specific SLURM account for job execution. From the more general to the more specific one:

The admin may set a default account in the SLURM/Fractal configuration file, which applies by default to all jobs (unless it is overridden). This looks like

{
    "default_slurm_config": {
        "partition": "main",
        "cpus_per_task": 1,
        "account": "somecommonaccount"
    }
}

The user may add this information to the WORKER_INIT variable, as in

WORKER_INIT = "#SBATCH --account=myaccount"

For a given task, a user can add a new meta property, with the key-value pair account->something.

Each one of these three options is then transformed in the same kind of line within the sbatch submission script.
Future changes
There are multiple possible extensions of this mechanism:

We may add a column to the user DB table, that lists all their available slurm accounts (similar to the slurm_user attribute).

Why this is useful: this information can be used to offer a pre-filled drop-down menu in fractal-web, at the job-run stage
Why this is not useful: At a difference from slurm_user, a Fractal user should be able to freely add/remove/modify their own accounts (since this does not require any sudo privilege). But modifying a user is currently restricted to superusers, and then this wouldn't immediately work. We can still make it work, but we need to rework the permissions of the user CRUD endpoints.

We may include a string query parameter for the apply endpoint, named slurm_account, and offer the corresponding input form in fractal-web. Inference of possible values would not be available from fractal-server, but we could in principle build it within fractal-web (based on the previous values that were used by a given user).
Independently on how the apply-workflow endpoint receives this information (be it one of a list of user's accounts or a free-field endpoint query parameter), further changes are needed:

The DB model for jobs must be modified, as it should also include a slurm_account optional column.
The attribute job.slurm_account should then be used in the backend runner component (or neglected, for the local runner), and it should be passed as an additional argument to the _slurm_submit_setup function, which (if not None) will take priority over any existing value of account (e.g. the ones included through methods 1 and 3 above).
There will always be a chance of conflicts, if the user sets an account both via approach 2 above and any other method (1, 3, or any other future method). Note that this is already an issue in the current status. We could add a check that makes the job execution fail in the presence of multiple values for account (or we may verify what is the SLURM behavior in this case, as I guess that this will already be an error).

A couple of general notes:

We will (likely) add some backend-specific information to DB model and API endpoints. This is not the first time, and it's acceptable because SLURM is our main target, and because these attributes are clearly optional. Let's keep it in mind that this approach won't scale forever, especially if we introduce a new runner.
Within SLURM, we may be moving towards four possible sources of the same information (actually five: task.meta, workflowtask.meta, job.worker_init, SLURM configuration file, and potentially one more). I'd be in favor of pruning some branch, since this situation could lead to unclear situations. Some options:

We start filtering some strings from worker-init (e.g. # SBATCH --account), and returning a 422 error from the workflow-apply endpoint in case they are present (together with a suggestion of where this should go).

Feedback is welcome.

If the account is not set, but the user's slurm_accounts list is non-empy, do something - cc @jluethi. What should we do here? Should we say e.g. that the first account in the list is always used by default?

Yes, that sounds good to me.
Is there another way that the slurm account can be set besides using the slurm_accounts afterwards?
What I'd expect on the web front-end:
The submit dialogue has a "slurm account" dropdown. By default, the top entry in the slurm_accounts list is selected.
What if there are no entries in that list? Then null is passed and no slurm account is provided?
What if it's not running on a slurm backend? Then that option isn't really relevant. But for just this, I don't think we need to make things too complex.
We could always put the slurm account & worker init parameters in an "advanced options" boxed that is not expanded by default

The part above seems reasonable to no or 1 account. Thinking through some more edge-cases in the scenario that a user has multiple accounts in slurm_accounts
Do we want to remember which one was used last and default to that?
Not sure if that is actually the main usage pattern.
Or default to no account to force the user to pick?
Would be very counter-intuitive if submission fails because no account was specified. But in general, accounts are optional (e.g. not currently required at UZH).
Or just also default to the top entry?
That should always work, but sometimes a user submits to the wrong account by mistake.
=> I'd probably still start with the option above, to be reevaluated for these edge-cases once we actually have actual users with multiple accounts

Expose optional selection of slurm account upon job submission (e.g. via query parameter? TBD)

While discussing with @ychiucco: let's rather proceed in the same way as for worker_init. We can add a new (nullable string) column to the ApplyWorkflow table, and include it also in the pydantic schemas. Then the apply-workflow endpoint will receive it directly from within the request body.

Summary of use cases, also based on @jluethi comments above (and open to improvements after some actual usage):

current_user.slurm_accounts = [], ApplyWorkflowCreate.slurm_account=None --> job.slurm_account=None
current_user.slurm_accounts = [], ApplyWorkflowCreate.slurm_account="a" --> 422 error
current_user.slurm_accounts = ["a", "b", "c"], ApplyWorkflowCreate.slurm_account=None --> job.slurm_account="a"
current_user.slurm_accounts = ["a", "b", "c"], ApplyWorkflowCreate.slurm_account="b" --> job.slurm_account="b"
current_user.slurm_accounts = ["a", "b", "c"], ApplyWorkflowCreate.slurm_account="d" --> 422 error


Enable tests package

Looks like error with Perf tests is related to

They arent using the correct rocm-cmake version.

So can we ignore this then?

@pfultz2  can you rebase , there are some conflicts ?


Student name/email in git history

Is your feature request related to a problem?

When I click on the Download Repo button and unzip the dowloaded folder, I can execute git commands on the student's repository, e.g.,
$ git logs
commit 0de45bf82d19a4e6fc64afb7bebe406501b2189e (HEAD -> diff)
Author: M... M<EMAIL_ADDRESS>Date:   Wed Mar 3 18:41:55 2021 +0100

    All student changes in one commit

What I really like about Artemis is that the assignments are anonymized, but through downloading the assignment, I can break this anonymity very easily. Now I am wondering: Is there a reason for this? Or is there a switch somewhere to activate an anonymization also for the git history?
Describe the solution you'd like
When clicking on export, Artemis is either

recreating the history with some placeholders for name and email, e.g., Max Mustermann and<EMAIL_ADDRESS>or
creating one single commit with the placeholders

You are right, this is one of the few places where the anonymity is not yet fully realized. We will consider this in the future.
What we cannot really fix is the "Go to repository" button. Tutors can navigate to Bitbucket and review the student repository over there. This is sometimes really helpful to help the students in case of issues, so I am not sure if we should prevent this in the future.


chore(i18n): add samoan locale

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Chore: This PR adds the Samoan locale file for ngLocale.
What is the current behavior? (You can also link to an open issue here)
There currently is not a locale file for Samoan in ngLocale.
https://github.com/angular/angular.js/issues/7246
What is the new behavior (if this is a feature change)?
This adds the ability to translate content to Samoan.
Does this PR introduce a breaking change?
No.
Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[ ] Fix/Feature: Docs have been added/updated
[ ] Fix/Feature: Tests have been added; existing tests pass
Other information:
No tests are available: See angular.js issue 7246: https://github.com/angular/angular.js/issues/7246
This was copied and then adapted from angular/bower-angular-i18n (originally committed by @spiffy2man: https://github.com/angular/bower-angular-i18n/pull/26).

I signed the cla.

Thanks for the PR. However since we are in Long Term Stability mode we are not going to add new locales to AngularJS.

Thanks for the PR. However since we are in Long Term Stability mode we are not going to add new locales to AngularJS.

@Narretz, I can understand that. How long will this have to wait until we can add the Samoan locale to angular.js? Can this be scheduled for when it will be an approvable PR?

Sorry if I wasn't clear, but feature development for AngularJS is completely over. We advise everyone to use the new Angular: https://angular.io/
However, with i18n you can simply take the Samoan ngLocale module you created and add it to your application without it being in an official release.

Sorry if I wasn't clear, but feature development for AngularJS is completely over. We advise everyone to use the new Angular: https://angular.io/
However, with i18n you can simply take the Samoan ngLocale module you created and add it to your application without it being in an official release.

Sounds good. Will do.


add group, hide user management in aad schema

Coverage increased (+0.01%) to 50.354% when pulling 2bbe541681e67c14a9aa17c951c34dc1aa3be1de on authendev into efe5ffd1159e534f50634d0f973664eb6df7c403 on authndev.

Coverage increased (+0.01%) to 50.354% when pulling 2bbe541681e67c14a9aa17c951c34dc1aa3be1de on authendev into efe5ffd1159e534f50634d0f973664eb6df7c403 on authndev.


Images not displaying on app  after uploading the photos but they are saving in the home directory folder

Once images are uploaded they will be stored in /temp folder of the current user then after processing they will move to /master and /preview folders.
that's the process...
so what's going wrong?

After uploading the photos nothing visible on homepage of app but when I
look at stats there are already number of photos I uploaded, hope u will
resolve this issue soon
On Tue, 21 May, 2024, 8:03 am Meet Patel, @.***> wrote:

Once images are uploaded they will be stored in /temp folder of the
current user then after processing they will move to /master and /preview
folders.
that's the process...
so what's going wrong?
—
Reply to this email directly, view it on GitHub
https://github.com/meet244/PicFolio/issues/5#issuecomment-2121595363,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUH2VJPOQ52P3PEOQBQIUPDZDKXA5AVCNFSM6AAAAABH7QR43KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRRGU4TKMZWGM
.
You are receiving this because you authored the thread.Message ID:
@.***>


Stathat from donate page not reporting

It's unclear if no one is donating, or if this is just not making it to stathat.

I added some logging on my local and [this line([https://github.com/DoSomething/dosomething/blob/2cf9e7db46bd066c0a51c0adc4b0aa222ce7abf7/lib/modules/dosomething/dosomething_payment/dosomething_payment.module#L215) is getting called, but it's not making it to stathat

Right, because the stathat library has to be added to the drupal-org.make file and in order to do that I think I have to give it a git url... or somehow have it locally.


This repository is outdated and superseded

The original author is now on github and his repository is more up to date (version f)
https://github.com/rcarmo/imapbackup

Thanks.  I added a note to the top of README pointing to that repo: https://github.com/mleonhard/imapbackup/commit/2927ce5b8ca0cc2ab47cf9568b80846bd7badb89


Icon request: Autodesk

URL of the site or app https://www.autodesk.com/
Logo resources for the icon https://brand.autodesk.com/brand-elements/autodesk-logo#sizes

Here you go:
https://github.com/krisu5/aegis-icons/blob/master/PNG/Autodesk.png


package fails to install on windows

> pip3 install pulumi-azure                                                                                Collecting pulumi-azure
  Using cached https://files.pythonhosted.org/packages/8f/76/1cf9e1e4e1e8d13222a34034d388fcb03d4d973f46cc1249e4caa9bb6bbf/pulumi_azure-1.0.0.tar.gz
    ERROR: Command errored out with exit status 1:
     command: 'c:\users\core\appdata\local\programs\python\python36-32\python.exe' -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\\Users\\core\\AppData\\Local\\Temp\\pip-install-n1bhdol8\\pulumi-azure\\setup.py'"'"'; __file__='"'"'C:\\Users\\core\\AppData\\Local\\Temp\\pip-install-n1bhdol8\\pulumi-azure\\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base pip-egg-info
         cwd: C:\Users\core\AppData\Local\Temp\pip-install-n1bhdol8\pulumi-azure\
    Complete output (9 lines):
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "C:\Users\core\AppData\Local\Temp\pip-install-n1bhdol8\pulumi-azure\setup.py", line 33, in <module>
        long_description=readme(),
      File "C:\Users\core\AppData\Local\Temp\pip-install-n1bhdol8\pulumi-azure\setup.py", line 28, in readme
        return f.read()
      File "c:\users\core\appdata\local\programs\python\python36-32\lib\encodings\cp1252.py", line 23, in decode
        return codecs.charmap_decode(input,self.errors,decoding_table)[0]
    UnicodeDecodeError: 'charmap' codec can't decode byte 0x9d in position 452: character maps to <undefined>
    ----------------------------------------
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.

windows 10, pulumi 1.0, python 3.6.8. venv\no venv doesnt make a difference. works fine on linux

Thanks!  I understand the issue here - we have smart quotes in our README.rst file and they are not being decoded correctly when trying to install the package (as it is not being opened as a UTF-8 file).  I'll have a quick fix for this shortly and then will be pushing out some larger changes to force us to always use UTF-8 encoding when opening the README.rst

@4c74356b41 Could you try installing pulumi-aws==1.0.1a1567796678 and see if this addresses the issue you're hitting?  If so, I will cut a 1.0.1 release of pulumi-aws.  Thanks!