EWS is not working with  On-premise exchange url in the cloud .

Hi,
Below is our requirement -  We are implementing cloud services (Proxies ) which are wrapper to EWS JAVA API’s – We are supporting both EWS on premise and O365.
O355 will work in any cloud solution but EWS on-premise does not work because cloud does not recognize  On-premise host and port.
To solve this problem we implement concept called Destination API  in our cloud – we will configure something like  https://Virtual host: Virtual Port :EWS/Exchange.asmx
Our cloud destination object returns httpClientFromDestination =destination.createHttpClient();
Either We need support from EWS JAVA API Custom httpclient support like
assign httpClient to EWSService
ExchangeService service = new ExchangeService(ExchangeVersion.Exchange2010_SP2);

HttpClient httpClientFromDestination =destination.createHttpClient();//our destination returns httpclient
Service.SethttpClient= httpClientFromDestination;

I saw we have support something like  .net EWS  but will this resolve our httpClient  handler problem?Do we’ve to rely on HttpClient only which is provided by Apache.
ExchangeService service = null;
service = new ExchangeService(RequestedExchangeVersion.Value);
if (SpecifyProxySettings == true)
            {
                WebProxy oWebProxy  = null;
                oWebProxy = new WebProxy(ProxyServerName, ProxyServerPort);
                oWebProxy.BypassProxyOnLocal = BypassProxyForLocalAddress;
                 ……..
             }
service.WebProxy = oWebProxy;

Thanks,
Showkath.

Why not edit your own API so that it returns the proper Exchange server URL, instead of a HttpClient object?

Hi ,
We can not edit our API , So Can you make changes in EWS Java API , one general question I have is Can other team (Non EWS Java team ) contribute to EWS Java API to fix any issues or implementing enhancements ?

@nshowkath ews-java-api is an open source software and anyone can provide fixes via pull requests. Once reviewed every contribution has the chance to get merged. If you want more information on how to provide Contributions here see:

github help
ews-java-api guidelines

Exposing the HttpClient is not desired, as explained in #100. To be honest, this sounds like incorrect API design on your side. But if you insist on providing the HttpClient instance yourself, you could create your own fork of this library.
However, I'd think that the right long term solution would be to fix your API. Your 'virtual URL' should be resolved to a real URL before passing it to the EWS Java API.


Mac customer_testing is trying to build the flutter tool from a different commit?

See https://github.com/flutter/flutter/pull/104431#issuecomment-1135001826
This is the CI build: https://ci.chromium.org/ui/p/flutter/builders/try/Mac customer_testing/31608/overview
Here are the relevant logs:
From https://github.com/flutter/flutter
 * [new branch]            master     -> master
 * [new branch]            master     -> origin/master
Warning: you are leaving 1 commit behind, not connected to
any of your branches:

  19204c238e Roll engine to d882b2d12375a4ae54baeccd2f7b0aafef422831

Switched to branch 'master'
+ dart __deprecated_pub get
Downloading Darwin x64 Dart SDK from Flutter engine 1bfe551d6b5adec64bb677cbb31ffd56c5acff49...
Building flutter tool...
Exhausted heap space, trying to allocate 32 bytes.

Note the engine version is from upstream HEAD, not the PR
This means that if upstream master Flutter SDK is broken, this CI test will have to be broken, even if run on a PR that would have fixed it

Based on https://flutter-review.googlesource.com/c/recipes/+/25820/2/recipe_modules/adhoc_validation/resources/customer_testing.sh#11, @godofredoc is this intended to run against HEAD?

oh, this looks like on line 18 it re-checks out the original branch?

oh, this looks like on line 18 it re-checks out the original branch?

Yeah, it intended to checkout the original branch, but all presubmit builds are with GIT_BRANCH: master, so it always checks out the HEAD. Looking to see if we can check out the commit instead.

https://flutter-review.googlesource.com/c/recipes/+/30840 to check out the commit.

Builders are not checking out correct commit to cover changes. Closing.


Eloquent way to query /api/graphql

Hey @Flux159! Thank you for this awesome starter example!
I have successfully implemented Postgraphile in the most recent nextjs version in my repo here.
Since you did not have a specific example of how to query /api/graphql, I used Vercel's example here which uses their SWR fetch tool.
My postgresdb has a table agile_teams with this:

With the graphiql tool I created a query from the generated postgraphile:
query MyQuery {
  allAgileTeams {
    edges {
      node {
        id
        name
        domain
        art
      }
    }
  }
}

In my nextjs page I created a type for the SWR fetch tool to use for typing:
type Data = {
  allAgileTeams: {
    edges: {
      node: {
        id: number
        name: string
        art: string
        domain: string
      }
    }[]
  }
}

Now in order to use the data I have to iterate over the edges under the data type:

  {allAgileTeams.edges.map((team, index) => (

      ID: {team.node.id}

      Name: {team.node.name}

      ART: {team.node.art}

      Domain: {team.node.domain}

  ))}

Which looks like this in my app:

My question is: do you have a better/more eloquent way to do this? With or without having to declare a type? A different query/fetch middleware/tool? Any suggestions are appreciated!

Hi, I'm using Apollo (@apollo/client in npm) in my app built using the same stack as this repo. You can read the docs here: https://www.apollographql.com/docs/react/api/react/hooks/
Essentially, in pages/_app.tsx, create a client that points to your endpoint (use a config/environment variable that determines between prod vs local). Something similar to this:
const client = new ApolloClient({
  cache: new InMemoryCache(),
  uri: "http://localhost:3000/api/graphql"
});

export default class App extends NextApp<AppInitialProps> {
  render(): JSX.Element {
    const { Component, pageProps } = this.props;
    return (
      // @ts-ignore
      <ApolloProvider client={client}>
        <Component {...pageProps} />
      </ApolloProvider>
    );
  }
}

Then in any React component, you should be able to useClient to run queries and mutations:
import { gql, useQuery } from '@apollo/client';

const GET_GREETING = gql`
  query GetGreeting($language: String!) {
    greeting(language: $language) {
      message
    }
  }
`;

function Hello() {
  const { loading, error, data } = useQuery(GET_GREETING, {
    variables: { language: 'english' },
  });
  if (loading) return
Loading ...
;
  return
Hello {data.greeting.message}!
;
}

Note that by default useQuery will be any typed, you still need to write the types of your responses if you want typescript to properly type check. If you want autogeneration of types, you would probably want to look at something like prisma, but that's an entirely different ORM system than using postgraphile (I'm using prisma these days in a larger project since it also handles migrations & works very well for managing conflicts between developers).
Also, this repo is a bit old & hasn't been updated, next 13 allows functional components for _app.tsx. I would recommend starting from a new create-next-app if making a new project.

Awesome, thank you for your incredible insight! I'll definitely research prisma vs postgraphile now that you mentioned the differences. Cool stuff!


Support optional dependencies from Conda-Forge

Blocked by #4848, #4919, #4920.
This is a fix related to #4850 to get Conda-Forge supported.
I expect to generate cupy/.data/_wheel.json in the Conda recipe, with a top-level entry packaging set to conda, so it's not touched in this PR.
TODO:

[x] Update installation guide.

cc: @jakirkham

cc @pentschev

Flake8 error will be fixed in #4888.

LGTM :+1:

pfnCI, test this please.

Ready for review?

Yes, thank you @kmaehashi 🙂

pfnCI, test this please.

@kmaehashi The AMD CI has passed long ago, but the status is not updated here, so automerge does not kick in.

Thanks Leo and everyone for the reviews! 😄


feat(nsconfig): read app resources path from nsconfig or default

Create a meaningful title

Read App Resources path from nsconfig.
Description
Part of implementation for https://github.com/NativeScript/nativescript-cli/issues/3257
Related Pull Requests

https://github.com/NativeScript/nativescript-cli/pull/3329
https://github.com/NativeScript/nativescript-cli/pull/3356

run ci

run ci


[JAX] Add TE examples

Add following examples:

examples/jax/test_single_gpu_mnist.py
examples/jax/test_single_gpu_encoder.py
examples/jax/test_multigpu_encoder.py
examples/jax/test_model_parallel_encoder.py

Align default values to google/flax

transformer_engine/jax/module.py
transformer_engine/jax/transformer.py

@timmoon10 and @nouiz ,
I think all conversation are resolved.
And I saw internal pipeline 7708362 is good.

@timmoon10 and @nouiz , I think all conversation are resolved. And I see internal pipeline 7708362 is good.

For me it is good except for one thing. GH doesn't allow me to make the comment at the right place, so trying here.
For the requirement, we still need to add flax as we don't always build and install in the same env.
It happens frequently that people use what is on pypi or build and one env and reuse in another one (We do this frequently in Dockerfile).
So we also need to add flax, even if in some cases it won't be useful.

For me it is good except for one thing. GH doesn't allow me to make the comment at the right place, so trying here.
For the requirement, we still need to add flax as we don't always build and install in the same env. It happens frequently that people use what is on pypi or build and one env and reuse in another one (We do this frequently in Dockerfile).
So we also need to add flax, even if in some cases it won't be useful.

Done

/te-ci

/te-ci

What is the result of the CI?
What is blocking this PR from being merged?

@timmoon10 and @nouiz ,
Thanks for help


Nested RepeaterView with efcore sqlite db

Hi @DottorPagliaccius,
The nested repeater totally works fine when I use dummy data that is not from database
but when I use database to get the list of feeds the nested repeater is not working on inner repeater (which is "Items" in my example). The parent repeater (which is "Feeds") works fine and showing data on my app.
This is my model
public class Feed
{
	public string FeedId { get; set; }
	public string Text { get; set; }
	public ICollection<Item> Items { get; set; }
}

public class Item
{
	public string ItemId { get; set; }
	public string ItemText { get; set; }
	public Feed Feeds { get; set; }
}

This is how I do to fetch the list of Feeds in db
var feeds = dbcontext.Feeds.Include(i=>i.Items).ToList();

foreach(var feed in feeds)
{
     Feeds.Add(feed);  //bind in ItemsSource="{Binding Feeds}"
}

Btw, on debug mode I've checked that "Feeds" and its child property "Items" has all the data I needed.
<repeater:RepeaterView x:Name="MainRepeater" ItemsSource="{Binding Feeds}">
	<repeater:RepeaterView.ItemTemplate>
		<DataTemplate>
			<ViewCell>
				<StackLayout Spacing="10">
					<Label Text="{Binding Text}" FontSize="16"  />

					<repeater:RepeaterView x:Name="MainRepeater2" ItemsSource="{Binding Items}">
						<repeater:RepeaterView.ItemTemplate>
							<DataTemplate>
								<ViewCell>
									<StackLayout>
										<Label Text="{Binding ItemText}" TextColor="Black" />
									</StackLayout>
								</ViewCell>
							</DataTemplate>
						</repeater:RepeaterView.ItemTemplate>
					</repeater:RepeaterView>
				</StackLayout>
			</ViewCell>
		</DataTemplate>
	</repeater:RepeaterView.ItemTemplate>
</repeater:RepeaterView>

hope you can help me on this :) thanks.

Uhm... if the control works with dummy data, I think the problem is... the data ;) I don't know efcore, but i suspect the problem is the lazy initialization of the child collection (that's why you're seeing it in debug mode, it evaluates itself when you observe it); since is not an observable one, once filled with data it doesn't refresh the control.
Try to make the "Items" Collection a ObservableCollection. Let me know.

it is now working fine! I just  change Items as ObservableCollection.
Thank you so much for the help and sharing your expertise @DottorPagliaccius  :)
keep on creating amazing control grazie :)

ahah "grazie" to you ;)


Socket timed out for Slurm adaptor

I've got the following error after submitting a couple of jobs to the queue. BTW the error occurs occasionally during builds on Travis CI.
slurm adaptor: Could not run command "scontrol" with stdin "null" arguments "[show, config]" at "nl.esciencecenter.xenon.adaptors.schedulers.JobQueueScheduler@142bb68f". Exit code = 1 Output:  Error output: slurm_load_ctl_conf error: Socket timed out on send/recv operation
Error submitting jobscript (exit code 1):
00:10:14.463 [main] DEBUG nl.esciencecenter.xenon.adaptors.schedulers.ScriptingScheduler - creating sub scheduler for slurm adaptor at local://
00:10:14.471 [main] DEBUG nl.esciencecenter.xenon.adaptors.schedulers.JobQueueScheduler - Creating JobQueueScheduler for Adaptor local with multiQThreads: 4 and pollingDelay: 1000
00:10:14.473 [main] DEBUG nl.esciencecenter.xenon.adaptors.schedulers.JobQueueScheduler - local: Submitting job
00:10:14.473 [main] DEBUG nl.esciencecenter.xenon.adaptors.schedulers.JobQueueScheduler - local: Created Job local-0
00:10:14.475 [main] DEBUG nl.esciencecenter.xenon.adaptors.schedulers.JobQueueScheduler - local: Submitting job to queue unlimited
00:10:14.475 [main] DEBUG nl.esciencecenter.xenon.adaptors.schedulers.JobQueueScheduler - local: Waiting for interactive job to start.
00:10:16.487 [main] DEBUG nl.esciencecenter.xenon.adaptors.schedulers.JobQueueScheduler - local: getJobStatus for job local-0
00:10:16.488 [main] DEBUG nl.esciencecenter.xenon.adaptors.schedulers.JobQueueScheduler - local: findJob for job local-0
00:10:16.488 [main] DEBUG nl.esciencecenter.xenon.adaptors.schedulers.JobQueueScheduler - local: findJob for job local-0
00:10:16.488 [main] DEBUG nl.esciencecenter.xenon.adaptors.schedulers.JobQueueScheduler - local: findJob for job local-0
00:10:16.488 [main] DEBUG nl.esciencecenter.xenon.adaptors.schedulers.JobQueueScheduler - local: findJob for job local-0
00:10:16.488 [main] DEBUG nl.esciencecenter.xenon.adaptors.schedulers.JobQueueScheduler - local: cleanupJob for job local-0
00:10:16.488 [main] DEBUG nl.esciencecenter.xenon.adaptors.schedulers.JobQueueScheduler - local: cleanupJob for job local-0
00:10:16.488 [main] DEBUG nl.esciencecenter.xenon.adaptors.schedulers.JobQueueScheduler - local: cleanupJob for job local-0
00:10:16.489 [main] DEBUG nl.esciencecenter.xenon.adaptors.schedulers.RemoteCommandRunner - CommandRunner took 2016 ms, executable = scontrol, arguments = [show, config], exitcode = 1, stdout:
stderr:
slurm_load_ctl_conf error: Socket timed out on send/recv operation

Interestingly, after restarting the Travis build this error disappeared.

The socket timeout is actually produced by slurm itself, Xenon just reports is back.
Apparently there is some race condition that occurs every now and then where a part slurm is not yet running? (or has already disappeared).


systemd patches for Plymouth

Motivation for this change
This is a mass-rebuildy part of #16763 and also a small cleanup. It needs patches to systemd https://github.com/NixOS/systemd/pull/5 and https://github.com/NixOS/systemd/pull/6 -- in this PR I use my own fork but this should not be merged as is.
Things done

[x] Tested using sandboxing
(nix.useChroot on NixOS,
or option build-use-chroot in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Ouch, I've posted it against master by mistake. Given that most likely this would be merged by one who would also merge systemd commits and update revision I expect this to be merged by hand, so let's leave it as is.

Whoever considers this for merging please also merge https://github.com/NixOS/nixpkgs/pull/16642 to reduce mass rebuilds -- I consider it ready.

Closed in favor of #16797


x/tools/godoc: hide app engine dependencies behind build tags

Failures like this occur because the builders don't fetch dependencies outside of the sub-repos. These files should be hidden behind build tags.

This has since been fixed.


Package the Ubuntu 16.04 with the snap format

Please package the Ubuntu 16.04 in the .snap format. snap packages work of many behind Linux and then have some kind of Linux universal package (they works on arch linux, Ubuntu, Red Hat, Fedora, Gentoo, Debian and others)

Would love to get this on Arch.

Also make is suitable for 17.04 to stay in line with LTS.

@rliessum In case you don't know, I'd like to remind that Ubuntu 17.04 is not a LTS version... But PowerShell currently supports non-LTS version of Ubuntu like 16.10.

@TravisEz13  Should we close the issue?

@SRGOM  @KexyBiscuit  the snap package is based on Ubuntu 16.04 (or 18.04 in the future.)  For non-LTS versions, this and the tar.gz is the only package we plan to supply.  For the latest stable release see https://snapcraft.io/powershell or for the latest preview release see https://snapcraft.io/powershell-preview


Everyone please join discussion group

@chris-hatton @cdjackson @presslab-us
The URL to the FAQ: https://groups.google.com/d/forum/zigbee4java

Joined.  FYI I’m slowly working on full Gradle support for zigbee4java (with equivalent to Maven profiles for Desktop/Android). With Gradle becoming the de-facto build system for Android, this will make zigbee4java useful to a wider audience.  I am new to Gradle so it’s taking a bit of time to get right (Maven seems a lot more straightforward at the moment…).
Thanks,
Chris

On 7 Mar 2015, at 20:57, Tommi S.E. Laukkanen<EMAIL_ADDRESS>wrote:
@chris-hatton https://github.com/chris-hatton @cdjackson https://github.com/cdjackson @presslab-us https://github.com/presslab-us
The URL to the FAQ: https://groups.google.com/d/forum/zigbee4java https://groups.google.com/d/forum/zigbee4java
—
Reply to this email directly or view it on GitHub https://github.com/tlaukkan/zigbee4java/issues/15.

Hi
Nice work Chris. There are lots of people and project appreciating gradle
support in server / desktop projects as well.
Cheers,
Tommi
2015-03-07 12:06 GMT+02:00 Chris Hatton<EMAIL_ADDRESS>
Joined. FYI I’m slowly working on full Gradle support for zigbee4java
(with equivalent to Maven profiles for Desktop/Android). With Gradle
becoming the de-facto build system for Android, this will make zigbee4java
useful to a wider audience. I am new to Gradle so it’s taking a bit of time
to get right (Maven seems a lot more straightforward at the moment…).
Thanks,
Chris

On 7 Mar 2015, at 20:57, Tommi S.E. Laukkanen<EMAIL_ADDRESS>wrote:
@chris-hatton https://github.com/chris-hatton @cdjackson <
https://github.com/cdjackson> @presslab-us <https://github.com/presslab-us
The URL to the FAQ: https://groups.google.com/d/forum/zigbee4java <
https://groups.google.com/d/forum/zigbee4java>
—
Reply to this email directly or view it on GitHub <
https://github.com/tlaukkan/zigbee4java/issues/15>.

—
Reply to this email directly or view it on GitHub
https://github.com/tlaukkan/zigbee4java/issues/15#issuecomment-77682427.

--
Best regards,
Tommi Laukkanen

By the way there is 2015 release thread at the google group. Contributors please check it out :).


Add Jira notifier.

Let's think how we can avoid duplicates

I'm leaving that to future improvements as it requires a bit more thought about ticket states and some way of associating tickets with alerts.


operator and namespace renaming

/cc @cooktheryan

@Gregory-Pereira I'd like to get this PR merged asap!


Missing Type.IsPrimitive

System.Type.IsPrimitive on docs.microsoft.com.
Thanks for this one!

Just realized I already submitted this one before :)
Duplicate of #2522. Closing.


Updating new way of creating review groups

🚀 Deployed on https://653846419743010b6b0fb4a9--cozy-fox-0defec.netlify.app


Add "merge" method into IntervalSet class. This method merges all ove…

This method merges all overlapping intervals.
For example, {(0,3), (3,6), (5,10]} => {(0,3), (3,10]}

Anybody reviews this?

You probably want to submit this upstream: https://github.com/intiocean/pyinter

I compared the Shopify branch and upstream and found they are different.
Shopify branch has several commits not included in upstream..
2016-05-16 11:48 GMT-04:00 Kevin Cox<EMAIL_ADDRESS>
You probably want to submit this upstream:
https://github.com/intiocean/pyinter
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/Shopify/pyinter/pull/8#issuecomment-219461311


how to move the preprocessing step out of model?

❓ How to do something using fastreid
We'd like to deploy a MGN model, I noticed that the SUB and DIV layer of data preprocessing caused the inconsistent outputs, so I tried to set the pixel mean to 0 and pixel std to 1. However this seem to be helpless, so how to modify the code so that the transferred ONNX file will not contain those two layers?

Comment out
line130


chore(cargo): update homepage to repository

Change homepage key to instead use the repository key for correctly labeling/pointing to the GitHub repo.
This makes location of the source code easier to see Crates.io. 🙂

Thank you!


Fix for #3957: impl LikeIsAllowedForType<Nullable>

Fixes #3957

@weiznich not sure why this one postgres check is failing... is there a way to retry that test?

I restarted the corresponding job.


A Level-db python client

I am thinking to written a client for leveldb in Python
anybody intersted? join me together!

I suggest you post this request on the leveldb group. I've seen at least one leveldb wrapper (i.e. still using the leveldb shared libary), but maybe you're thinking of a pure Python implementation. Good luck.


Bulk insert not as performant, any Tips to increase speed?

Hi,
I am trying to insert 100,000 records and reach under 5 seconds. As of now it takes around 20 seconds
I have turned off auto detect changes.
 _dbContext.DbContext.ChangeTracker.AutoDetectChangesEnabled = false;
This is my object:
 public int ID { get; set; }
  public string PartIdentifier { get; set; }
   public int CountBatch { get; set; }
  public IdentifierType Type { get; set; }
  public Guid InventoryID { get; set; }
This is my insert statement
await _dbContext.BulkInsertAsync(lookupsListBulkInsert, new BulkConfig { BatchSize = 20000 });
Any tips or help?
Thanks

When you say 'As of now' what did change before Insert become slower?
Did this table become really large, containing several millions records?
Also make a Test for your scenario so that it can be reproducible.


[DOC] document the nested_path parameter in agent search tools

What do you want to do?
Per customer request, in 2.16 we will support nested field in agent search tools (neural sparse tool, vectorDB tool, RAG Tool). We add a new parameter to these tools, and we need to document this change

[x] Request a change to existing documentation
[ ] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Tell us about your request. Provide a summary of the request.
*Version: List the OpenSearch version to which this issue applies, e.g. 2.14, 2.12--2.14, or all.
2.16
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
https://github.com/opensearch-project/skills/pull/350

Please assign this issue to me


Simple aggregation schemes on aggregator: geometric mean + median

It would be great to have not only Avg operator for tensor aggregation, but also few other simple operations like Geometric Mean, Median, etc.

@alexey-gruzdev, we do have some of this in place: I believe we interpret one of the flplan args as the aggregation function. If the name doesn't match our pre-defined strings, we assume it is a numpy function and invoke it.
I'd like the end-result to be the same as others: you can declare arbitrary python classes in the flplan that provide the functionality, along with init kwargs, the function to invoke, and kwargs for that function. Essentially, our same generic task declaration method we use for the collaborators. This is one of the reasons Patrick and I have been talking about making the aggregator essentially "just another task runner".

@msheller that's great, if we have it in place - could you provide a simple example for the reference?
Ideally, for better extendibility it would be great to have a python function to be passed to Python API entities & being used by OpenFL further.
def custom_aggregation(a: torch.Tensor, b: torch.Tensor) -> torch.Tensor:
    return (a + b)/2

fl_model = fx.run_experiment(collaborators, agg_function=custom_aggregation,
                                                override_config={'aggregator.settings.rounds_to_train':5})

you can declare arbitrary python classes in the flplan that provide the functionality, along with init kwargs, the function to invoke, and kwargs for that function

Maybe I am wrong, however from Python user's perspective - is it a right place to define such kind of functionalities in FLPlan (.yaml)?

@alexey-gruzdev This is a feature I added a few months ago. A limited set of custom aggregation types are supported at the task level. They can be called in the following way:
plan.yaml
...
tasks:
  aggregated_model_validation:
    aggregation_type: median
    function: validate
    kwargs:
      apply: global
      batch_size: 32
      metrics:
      - accuracy
...

and you can call it through the current Python API like this:
fl_model = fx.run_experiment(collaborators, agg_function=custom_aggregation,
                                                override_config={'aggregator.settings.rounds_to_train':5,
                                                                 'tasks.aggregated_model_validation.aggregation_type': 'median'})

These aggregation types are currently limited to simple numpy functions (see here). As both of you suggest, we should provide a way to define custom functions that can be applied to model weights and task metrics. There is likely a need to apply a specific aggregation function to certain task output, and possibly another for how to combine model weights. Because of this level of specificity my view is that the plan is the appropriate place to embed this information, but we could extend our existing python APIs so that the user has a cleaner way for expressing the function they want to use without modifying the plan directly.


CI: skip testing dependent projects when version changed

We use the version in charon/Cargo.toml to indicate changes that will break downstream projects (e.g. adding variants to the AST). So when a PR changes the version, we should not run the aeneas/eurydice/kyber CIs.

Actually, the file charon-ml/CharonVersion.ml also tracks the version and only contains that, so we should look at that file instead of Cargo.toml.

I no longer think this is a good idea: we regularly do changes that change the json format without breaking downstream projects.


Add an optional significant-newlines mode without hard-wrapping accommodation?

I really appreciate the thoughtful, principled design of djot! But when I showed it to the rest of the Zulip team as a potential foundation for replacing our (slow, buggy, not-quite-standard) Markdown implementation, the one main point of pushback was on the inability to interrupt a paragraph with a list. “Requiring people to put a blank line between text and a list works out very poorly—Zulip’s markup originally worked that way, because Markdown did, and it was a source of constant complaints.”
This is a tricky dilemma. I do understand djot’s decision, and I think it’s probably correct for most use cases. But it seems to be a sticking point for many potential users. Some previous discussions that hopefully don’t need to be rehashed here:

Blank lines before lists, revisited
Djot: A light markup language by @jgm
#137
Hacker News discussion today

I have one observation to maybe add. In practice, Markdown is typically used in two modes today:

A collapsed-newlines mode where text may be freely hard-wrapped in the source without affecting the output. Most useful for longer documents written in a real editor, checked into version control, and maintained over time, where source code readability is important.
Example: GitHub’s rendering of Markdown files in the file browser.

A significant-newlines mode where line breaks in the input are passed through to the output (via
 conversion or white-space: pre-wrap styling). Most useful for shorter comments and chat messages written in a dumb textbox, perhaps by users who don’t want to think as much about formatting, typically just written and rendered once.
Example: GitHub’s rendering of Markdown comments in issues.

The users who complain about blank lines before lists are more likely to be writing in the latter mode, which is also the mode where hard-wrapping doesn’t make sense. Therefore, perhaps a solution to the dilemma would be to standardize slightly different parsing rules for these two modes, and restrict the hard-wrapping accommodations to the former mode? A blank line before a list would be required in collapsed-newlines mode, and optional in significant-newlines mode.
I know it’s not ideal to have the parsing rules diverge like this. But maybe it’s a reasonable compromise given that both modes are likely to exist anyway? It does make some intuitive sense that a 1. following a newline should be treated as more “intentional” when the newline itself would be significant in the output.

I'm not the creator, just someone who has gone all-in on djot for my software documentation. This is my own opinion, not anyone else's.
I think you have a point. However, I'm not sure the world would be best served by having two modes of djot when Markdown serves well enough in the significant-newlines mode.
I personally think that djot is great for documentation checked into version control and that it should stay designed that way. On the other hand, I also think Markdown with significant newlines would be better for comment systems since Markdown is close to what people would write in plaintext anyway.
If people really want djot for comment systems, I think it would be better to make a new language specifically for that, with different design goals (such as removing goal 7). I'll refer to it as "tojd" (djot backwards) for now.
I think a tojd language could be useful for the simple fact that it could share most of a parser with djot, but it would also give those who hate goal 7 a way out. It would also be well-optimized for comment systems.
And I think it should be a separate language so that each language could serve best the use case it is useful for: djot for documentation and tojd for comment systems, especially since those use cases have incompatible design constraints. It would also be clearer to users of both when they are using one or the other.
That said, I can't say if @jgm would even be interested in helping define such a language, though I might be.

I think you have a point. However, I'm not sure the world would be best served by having two modes of djot when Markdown serves well enough in the significant-newlines mode.

I feel like that'd be a bad solution. Sure, you can always use Markdown and Commonmark instead, but djot is a better design in many ways that have been clearly articulated by @jgm, and it'd be great if most of the ecosystem of projects that currently use Markdown or CommonMark can migrate to djot in order to benefit from those improvements. Today, projects using original Markdown rather than CommonMark are essentially all those for whom legacy considerations make migration hard; I'd like it to be that way for djot as well, where projects should only be using CommonMark if legacy considerations / limited resources prevent them from migrating to djot.
As best I can tell, this detail about newlines is the main language design reason I've seen that would motivate someone to start a new project using CommonMark rather than djot, and I think @andersk has articulated clearly the crux of the issue -- that there's actually two different use cases for a Markdown-style processor here with slightly different requirements. I would much prefer for significant newlines functionality to be part of djot (or at least a specified extension/variant) rather than a "separate language", to avoid fracturing the ecosystem.
On the naming point -- obviously this is entirely up to @jgm, but I think "djot with significant newlines" name would work well; I could easily see a project saying "We use djot with significant newlines" in the same way that projects today might say "We use GitHub-flavored Markdown" or "We use CommonMark with a few extensions" to provide a clear, concise description of what markup language they're using.

I would much prefer for significant newlines functionality to be part of djot (or at least a specified extension/variant) rather than a "separate language", to avoid fracturing the ecosystem.

I can see your point here. Ultimately, it comes down to a judgment call, and only @jgm would be able to tell us what he wants.

It's an interesting suggestion, and I remember we talked about something similar in the early discussions leading to commonmark.
I think losing a single uniform syntax is a heavy cost, so I'd be reluctant to go this way, but I will think about it some more.
I also wonder how much of the resistance to the current syntax is just based on familiarity.  Once you get used to adding a blank line before a list, it's not a big thing.  (And the source then more closely resembles what you find in printed books, which always set off lists from the main text.)  People complained when GitHub changed heading syntax (to conform to commonmark) so that a space was required after #, but I don't think too many people care about that now, since they've gotten used to it.
The objective in a lot of my work with markdown/commonmark was: "try to do what the writer intended in the vast majority of cases."  That's going to lead to a syntax with lots of quirks and rough edges (and one that, inevitably, still won't magically always do what the writer intended).  Djot has somewhat different aims.  It wants to be principled and uniform.
It would be good to write down exactly what would change in the envisioned special mode.  Is it this?

Lists, blockquotes, headings, and other block constructions can interrupt paragraphs.
Newlines within paragraphs create hard breaks.

Is that it?

Yeah, I think that’s it.
(A question occurred to me about whether blocks should still interrupt after backslash-newline in this mode:
paragraph\
- list item?

I guess they still should, for consistency with this existing behavior?
> blockquote\
- list item

But nobody’s likely to write this, so whatever makes the spec cleanest is fine.)

The users who complain about blank lines before lists are more likely to be writing in the latter mode, which is also the mode where hard-wrapping doesn’t make sense.

Personally, most of my use of commonmark is in the former mode, but the requirement for blank lines before lists still annoys me endlessly, even though I do hard-wrap my content. I'd much prefer that neither lists nor sublists require a preceding blank line, and that the "interrupted a paragraph with an unintended list" case be solved by escaping; editors' wrapping tooling could well be adapted to detect and automatically escape for this case.

OP, that people write in different modes is such a good point. Lightweight markup languages should be both readable and easily writeable, and sometimes these two points are in tension.
The problem though with creating two modes is that people then always have to put adjectives or disclaimers in or around the proper name.
In a perfect world with infinite resources (speaking from the peanut gallery here), it would be nice to have two distinct entities:

This language with its current name
Your proposed new “mode”

And for them to have different names.
Either that or something like djot/.
Of course you would have (see previous: infinite resources) utilities to convert between the two languages at any time. So then the only potential confusion would be if you are in a txt document and you forgot which variant you are currently in. ;)
Unfortunately though the hangup about the required blank line before a sublist would remain unless those who don’t like that rule also don’t like to hard-wrap (seems unlikely).

@LemmingAvalanche My point was that people are inevitably going to use Djot in these two modes anyway (even if only by feeding the output through a newline-to-
 postprocessor or a white-space: pre-line CSS rule). They already do this with Markdown—again, see the Markdown flavor in which we’re having this very discussion.
If we support both modes, we won’t need any additional resources to convert between them; that will automatically be possible by running the existing bidirectional Djot ↔ AST conversion, forwards in one mode and backwards in the other.

The concern of most users is that a blank line is needed before a sublist.
So, what about adding an escape mode only for lists, so that it enables to write
a sublist without a blank line.
For example:
*```
- top
  - inner
- top
  - inner
- top
  - inner
```

This is similar to the Math syntax used in djot.
$```
e=mc^2

x^n + y^n = z^n
```

(Instead of an asterisk, some other character can also be used.)

Having read several discussions on this (this one, #137, #170), I have a question.
Is there a version of djot out there with all the goals except goal 7? More specifically with these answers to @jgm's questions above:

Lists, blockquotes, headings, and other block constructions can interrupt paragraphs. -- Yes
Newlines within paragraphs create hard breaks. -- No

I am not against hard wrapping. I am just saying that if a hard wrap results in one of those several well-recognized block-start sequences (- , 1. , > , a few others), well, I am interested in a compromise. It's like with hyphenation rules or orphaned paragraph lines: sometimes you just shouldn't break your text in a certain way, and it's a bit annoying, especially if your editor doesn't help you catch it, but it's OK. You break it earlier or later.
Here is my view of it: djot has so many good things going for it. But markdown turns out a great idea for representing rich text in all kinds of cases. In some cases, hard-wrapping is a non-issue, but blank lines are. In my case, I am looking for a representation of bits of text that would often be short. Think cells in a spreadsheet. Could be one line, could be many lines, and a "common" document may be a cell with 4 list items inside, and one of them having one sub-item. GFM/commonmark would look more natural, and more users would get it right on the first try. But again: djot is better in so many ways. After learning about it, choosing a traditional markdown format almost seems a step backwards.
I know there isn't a consensus on this. But is there a version that makes a different choice on this particular issue, that I could play with?

I don't know the answer here, but wanted to add: I think great values of djot are its simplicity and consistency. A change that would compromise either of those would have to offer significant value.

For what it's worth, I do think adding a significant newlines mode would add considerable value. The Zulip team continues to be really excited about the Djot AST architecture, but we remain unable to seriously consider migrating to Djot because of this issue. But more broadly, hard-wrapping is not a priority for text boxes on the web, and there's a lot of those that I'd like to see able to use Djot rather than flavors of Markdown.

Hello,
I'm a bit late to the party but what about this simple solution:

By default, a \n token represents an actual line-break in the output.
To "manually hard-wrap", the sequence "\n " (newline then space) has to be used at the end of a line which is otherwise non-empty.

Basically this reverse the current stance, where manually hard-wrapping is default and \ is used to actually line-break.
This allows:

to write djot both in collapsed and significant-newline modes @andersk is talking about,
maintain the principle of uniformity @jgm based djot on,
get rid of the rule "one blank line before any block element".

Examples (I write the space at the end of line as ␣ to highlight its presence):

## Short Header
Text content

and
## Short Header

Text content

render as

Short Header

Text content

## Long Header␣
That Continues Here
Text content

and
## Long Header␣
That Continues Here

Text content

render as

Short Header That Continues Here

Text content

- list item a
  - sublist item 1
  - sublist item 2
- list item b

renders as

		list item a

				sublist item 1

				sublist item 2

		list item b

- list item a␣
but I like them longer
  - sublist item 1,␣
  this one too
  - sublist item 2,␣
  and this one
- list item b

renders as

		list item a, but I like them longer

				sublist item 1, this one too

				sublist item 2, and this one

		list item b

I think he weighed 200 pounds, maybe even␣
220. But he was no more than five feet tall.

renders as

I think he weighed 200 pounds, maybe even 220. But he was no more than five feet tall.

Regarding this kind of example, to me it isn't good enough to mandate that lists should have one blank line before. It's just too rare and contrived, and if If I'm ever going to write sentences like this and I want to hard wrap, I'm not gonna hard-wrap with 220. at the beginning of the line, there are other ways.

I think he weighed 200 pounds, maybe even
220. But he was no more than five feet tall.

renders as

I think he weighed 200 pounds, maybe even

		But he was no more than five feet tall.

This generalizes to other blocks like block-quotes.
One can still put one blank line before them, but in environments like online messages, it's not mandatory.
Personally I do use both "manual-hard-wrapping" and "newline=line-break", depending on the need, and it makes quite sense when I manually hard-wrap to leave a blank space after the last word of the line so that if I change the wrapping by putting back some words on the previous lines, or change the wording (and delete some words in the process), there is one space waiting for me in the previous line.
This solution seems natural and elegant to me, on top of going back to sth similar to markdown's double spaces at end of line is a line break. Just the reverse. So in the end if the principle of uniformity is to be upheld, it's a choice between manual hard-wrapping as the default meaning of \n, and blank lines being optional before lists.


 contains a leading bullet on home and search pages

Very minor issue, the  node on the home and search pages has:  · Warehouse (PyPI)

This is because some templates (including index.html and search/results.html) are missing the title block.
@dstufft, @nlhkabu, which would be preferred: hiding the bullet if the block is empty, or ensuring that all templates have a title block? If the latter, is there a string which would be good to use as a default?

Technically a duplicate of #784.

Sort of a duplicate, though sort of not, the question of how do we handle a page that legitly doesn't have a title is a reasonable question I think. Options being:

Let the leading dot happen
Make the dot only show up if there is a title
Make sure all pages have a title and don't allow any to have an empty title

:+1: +1 for option 2.  Lets only show the dot if there is a title :D


Templating ERC721 & Handling some known failures in IPFS.cat

Hi All,
Kent from Graphrica.
Major changes in this branch:

Templating ERC721 - This indexes each contract seperately, and allows a bit more flexibility if other handlers need to be added. See Erc721.create(contractAddress). This should also speed up indexing/syncing.
IPFS is deprecated and is known to fail with timeouts.
I did make an attempt to parse some base64 json into json - this is a work in progress and I hope to solve this with some internal teams.
CozyCosmonauts cause IPFS to fail, I just save the URI and skip the reading of metadata. We can work on this.

@leonprou @mul53
fixes #3 :
See here for testing:
https://thegraph.com/hosted-service/subgraph/gundamdweeb/fuse-network-erc721?query=Account with Cozy

@mul53
Here is some of the tasks and known issues I was working with:
Fuse Network ERC721
Tasks:

[ ] Remove Account with 0 balance
[ ] Check for exceptions
[ ] FIGURE OUT HOW TO PARSE THAT BASE64
[x] Cover URI Update

https://github.com/fuseio/fuse-nft-subgraph/pull/4
13085303 - Last Block Failure -
14149632 - Last Block Failure - 0x876b6d93c27aee580ad492267200c6ce30228f8dbedbaddda0a064d2c92a27e8
14 149 632

https://explorer.fuse.io/tx/0x63be68eaf3607404a3ae900f4969ca0ad51838465c50976d877e7ca9627cb4ef/token-transfers
Current Issues:
https://thegraph.com/hosted-service/subgraph/gundamdweeb/fuse-network-erc721?query=IPFS Failures
IPFS Failures to check

[x] 0xaa8c1b2cf1005eb30f5d5c1cef2efc540ac49bbd

IPFS is broken

[ ] 0xa9c476274be91fcc920ab53436ed563f5723f2d1

Is JSON - we can perhaps parse it

I have removed the escape from readMetadata for Cozy Collection -
Let's see how it deals with the IPFS!

Here is a Pending version of Fix - https://thegraph.com/hosted-service/subgraph/gundamdweeb/fuse-network-erc721?version=pending

So by removing the Cozy Check -  it fails once again at the same block mentioned above on that tx. I am pushing a version that just skips that first ID in cozy. https://thegraph.com/hosted-service/subgraph/gundamdweeb/fuse-network-erc721?version=pending

Hey @GundamDweeb ,
Thanks for the PR 👍
About the Cozy issues, can you give more details? Cozy is a top project so we need it to be included

Hi @leonprou
This PR is being closed.


Feature AQI-7684 : Schedule Tolerance : Mobile : Expose Schedules

Seems like maybe this should be more than just a bugfix version change since we are adding functionality

I agree.  @williamwendt-aqi  - please bump the minor version, following https://semver.org/, as this is adding functionality and not fixing a bug.


Apply ts lint rules to HTML files?

I have a custom rule which disallows files starting with the empty line:
Object.defineProperty(exports, "__esModule", { value: true });
var tslib = require("../../../node_modules/tslib");
var Lint = require("../../../node_modules/tslint/lib/index");
var Rule = /** @class */ (function(_super) {
  tslib.__extends(Rule, _super);

  function Rule() {
    return _super !== null && _super.apply(this, arguments) || this;
  }
  Rule.prototype.apply = function(sourceFile) {
    var length = sourceFile.text.length;

    // TO DO: improve the first line empty check!
    if (length === 0 || (sourceFile.text[0] !== "\n" && sourceFile.text[0] !== "")) {
      return [];
    }

    return [new Lint.RuleFailure(sourceFile, 0, length, Rule.FAILURE_STRING, this.ruleName)];
  };
  /* tslint:disable:object-literal-sort-keys */
  Rule.metadata = {
    ruleName: "app-no-empty-bof-line",
    description: "Ensures the file does not begin with an empty line.",
    descriptionDetails: "Fix for single-line files is not supported.",
    optionsDescription: "Not configurable.",
    options: null,
    optionExamples: [true],
    type: "maintainability",
    typescriptOnly: false,
  };
  /* tslint:enable:object-literal-sort-keys */
  Rule.FAILURE_STRING = "File should not begin with an empty line.";
  return Rule;
}(Lint.Rules.AbstractRule));
exports.Rule = Rule;

Which works, but only for .ts files. How could I convince the linter to run this against HTML files?
(So src/app/components/foo/bar.component.html will be linted.)
Can someone explain to me what the typescriptOnly property is for? Looking at the source it allows linting of javascript files additionally to typescript, right?
I saw an implementation in codelyzer which runs against HTML files: https://github.com/mgechev/codelyzer/blob/af529127771a00e7a8b5a9e5557cbd96564f28fd/src/trackByFunctionRule.ts
Is there a simpler approach or I should follow this implementation to convince my custom rule to run on html files also?

@janez-svetin I don't think you need a linter to accomplish your goal, as there's really no need for an AST. You can just write a Node script to read source files and check that the opening character is not a newline.

@aervin hm, your response got me thinking, maybe I should leave the formatting of the code to the libs as the Prettier is.


fix doc wrong package name

Hi, thanks for the awesome library!
I just tried it out with next.js as a backend implementation. While I was reading the doc, I found that there is a wrong package name in the documentation. I realized it when I try to install it and it is not found. Turns out the right package name was the one in the sidebar. So, I want to contribute a little to fix the doc.
Thanks

Codecov Report

Merging #151 (86af803) into main (1153f4b) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main     #151   +/-   ##
=======================================
  Coverage   66.00%   66.00%
=======================================
  Files           9        9
  Lines         250      250
  Branches       61       61
=======================================
  Hits          165      165
  Misses         75       75
  Partials       10       10

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Awesome, thanks for your contribution!


client always times out

I figured out that the client side gets timeouted every time HERE. This affects even the example server.py and client.py scripts.
I do not know the protocol enough to decide if this is intentional. However, smuggling force=True into the coro requires monkey patching that seems unelegant to me.
By defaulting force=True or commenting out lines 447-455 entirely, the client.py exits immediately after receiving the hello message which should be the good way according my intention.

The server is expected to close the TCP connection right after sending the close frame as prescribed by the RFC.
If the example server.py doesn't, that's a bug and I should investigate it.
What OS / Python / asyncio (if applicable) / websockets versions are you using?

ARCH Linux 4.2.3-1 ARCH / Python 3.5.0 [GCC 5.2.0] on linux / 2.6 (installed by pip)

This may be a duplicate of #73. I don't know if the Python bug discussed there was reported to bugs.python.org and fixed in Python 3.5.0.

Yep, sorry for not looking the past issues first. As I see the lines I refered do block the client code. By ignoring it the client's connection_lost() callback gets called nicely, so the server do its part by closing the connection.
For some reason the code in line 447-455 blocks the client.

Yes, that's the bug (if I understand it correctly): while the server side has closed the TCP connection, asyncio doesn't dectect it on the client side and fire connection_lost callback.

I deebugged both client.py and server.py with the following code:
import sys
import logging
loghandler = logging.StreamHandler(sys.stdout)
logging.basicConfig(level=logging.DEBUG, handlers=[loghandler])
loop = asyncio.get_event_loop()
loop.set_debug(True)

The client receives the EOF:
< Hello Adam
DEBUG:asyncio:poll 9992.357 ms took 6.453 ms: 1 events
DEBUG:asyncio:<_SelectorSocketTransport fd=6 read=polling write=<idle, bufsize=0>> received EOF
INFO:asyncio:poll 9973.090 ms took 9979.426 ms: timeout

Digging into asyncio.code it seems that the transport is kept open HERE and its close() method is not called immediately.
To be continued...

Well, asyncio.streams.StreamReaderProtocol.eof_received() has been changed since Python 3.4.3 to return True instead of None (link).
According to this it means that since the change "closing the transport is up to the protocol".

As a quick fix, adding this method to protocl.WebSocketCommonProtocol solves the issue:
def eof_received(self):
    super().eof_received()
    return None

However, making the StreamReaderProtocol to return True was intentional according to this issue, so the final solution seems to be more sophisticated.

IIRC we have to be careful with SSL which handles connection termination differently. I'll review the changes in Python and try to understand how I'm supposed to adapt websockets.

One last question: if you close the repository and run make test with your Python version, do you get test failures?
----------------------------------------------------------------------
Ran 192 tests in 12.156s

OK
/usr/lib/python3.5/asyncio/sslproto.py:323: ResourceWarning: unclosed transport <asyncio.sslproto._SSLProtocolTransport object at 0x7fcf0c0aab70>
  warnings.warn("unclosed transport %r" % self, ResourceWarning)

Thanks for testing. I'll investigate further as soon as I get the opportunity.


Ability to revert class add and remove from Changes Browser (3.0.92)

With feature under issue #624. we can revert add, remove, and method modifications.
Alas this now creates the desire to revert adding and removing classes.

as of 3.2.12, it is not allowed to revert removing a class, this is an open issue.


Repositories: OCI: default values for 'exponentialBackOffValues' are not applied upon creation

Setup

Rancher version: 2.9-head
Rancher UI Extensions:
Browser type & version: Any

Describe the bug
Default values for 'exponentialBackOffValues' are not applied upon creation

To Reproduce

go to repos page (/manager/catalog.cattle.io.clusterrepo)
click create
input name
under Target select the second option (git repo) and then select the third option (OCI repo)
input index URL (oci://test.rancher.io/charts)
click create
notice error: MinWait should be at least 1 second

Result
Default values for 'exponentialBackOffValues' are not applied upon creation.
Expected Result
Default values for 'exponentialBackOffValues' are applied upon creation.

Screenshots
https://github.com/rancher/dashboard/assets/127343932/862fb18e-e248-4bef-8e72-ab2adb7c8f2d

Additional context
Note: you won't see the error if you select the third option (OCI repo) directly - step 4 of repro steps

The new e2e test looks sufficient to me. I also ran the existing repo e2e tests and all are passing. closing this out cc: @izaac


Release azure-cli-sql 0.1.1b3

Reviewers, please verify the following for this PR:

[ ] The PR title has format Release <component-name> <version>.
[ ] setup.py has been modified with the same version as in the PR title.
[ ] HISTORY.rst has been modified with appropriate release notes.
[ ] If releasing azure-cli or azure-cli-core, __version__ defined in __init__.py should also be modified to match.

Release of 'azure-cli-sql' with version '0.1.1b3' successful. View at https://pypi.python.org/pypi/azure-cli-sql/0.1.1b3.

GitHub release created. https://github.com/Azure/azure-cli/releases.


Design: Improve stdout for CLI

PoC for how CLI's stdout should look and description for follow-up issue.

[x] category title and scores should be included and clearly highlighted
[x] each plugin's audit results should be listed on a single line (title: result - no descriptions, no weights)
[x] should display status of each stage (spinner, then completed)

[x] parsing configuration (print if verbose?)
[x] executing plugin X - title, number of audits, duration once completed
[x] creating report file(s)
[x] uploading to portal

[x] TBD: should stdout really be a format? --verbose is more usual way of limiting stdout

Current version (for reference)

Update so far:

came up with a compact layout I like for audits and categories, PoC implemented with chalk, cliui and cli-table3 (see screenshot)
found @poppinss/cliui, which looks amazing I plan to try it out next

Submitted draft PR to demo stdout formatting: #189
Created follow-up issues to be refined:

#190
#191

Closing as the follow-up issues have been refined and prioritized.


Is Blue/green deployment (powered by AWS CodeDeploy) supported?

Is Blue/green deployment (powered by AWS CodeDeploy) supported?

If not supported, how can I make this a feature request?

Hi @monelgordillo , blue/green deployment is not supported yet. Please create a feature request on https://github.com/aws/containers-roadmap/issues. We'll track on the feature request and keep it updated.


Link ORCID account

Feature Request
Desired behaviour
Ala quay.io linking

┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Issue Number: DOCK-697

Ahead of even DOIs being ready, can link to ORCID profiles in stargazers and organization members

Implement as "more metadata" on an entry for its author's ORC-ID account
Add a sign-in as ORCID
Add Dockstore as a source of "Works" to the ORCID site

There are other potential integrations but I thought I might throw these out to give some idea of what our first feature should be. Being able to add a list of authors and their ORCIDs per entry would be a noted improvement and requires no interaction with the ORCID API (except creating a hyperlink).
Signing in as ORCID will be a bit more complicated but should follow the same patterns we are familiar with from gh and google.
Haven't done a feasability analysis on 3) but it seems like once we are publishing DOIs using zenodo works should be findable this way (DataCite is a listed "works" provider).


Synergize sometimes does not find Synergia VST instances via Bonjour/Zeroconf

During beta testing, we've noticed that Synergize sometimes does not discover a running Synergia instance via Bonjour/Zeroconf.  Often, toggling the VRAM button in Synergia is enough to get Synergize's attention. If that does not work, however, you can hardcode Synergia's network port (shown in green text under the VRAM button) via Synergize's Help->Preferences menu.

While the above "toggle VRAM" workaround seems to be reliable on MacOS, Synergize rarely is able to find Synergia instances on Windows.  The only reliable workaround on Windows is to hardcode the  port - very inconvenient.

Fixed in 2.3.0 -- we no longer use zeroconf for Synergia address/port discovery.


fix(core): throw error for invalid URL in config file

Pre-flight checklist

[x] I have read the Contributing Guidelines on pull requests.
[x] If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
[x] If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

Currently, a warning is displayed when the URL contains a sub-path but as mentioned at the end of #8159, it makes more sense to display an error. So, I updated the code to display an error instead of a warning.
Test Plan

Test links

I updated unit tests to verify my code.
Related issues/PRs

Related to https://github.com/facebook/docusaurus/pull/8159 and https://github.com/facebook/docusaurus/issues/8116

LGTM thanks 👍


Move nextstrain.py to paper repo?

There's a module nextstrain.py which isn't really used here. It probably belongs in the paper repo, if we're still using it for converting nextstrain formatted trees.
Do you remember how we were using this @hyanwong?
(I'm turning this into a "proper" software project here and trying to clear out unused code)

We were using this to plot the cophylogeny, I think. It should probably be moved to the paper repo, unless there is a more general use-case for people wanting to compare their own inferred sc2 ARGs to nextstrain trees.


OSX: shaders loaded from nonstandard location

tldr:  on OSX, _load_shader_str should look in .app/Contents/Resources/shaders instead of .app/Contents/MacOS/shaders
(or we need a sample setup.py / setup.cfg that copies the shaders to Contents/MacOS/shaders)
presently I'm using   'package_data_dirs': {'simplepbr': [('simplepbr/shaders*', '', {})]}, in my setup.py, and manually editing the generated app to put the shaders where simplepbr looks for them
seems like an easy enough fix -- let me see if I can figure out the workflow for a local fix + pull-request

https://github.com/Moguri/panda3d-simplepbr/pull/30

Fixed by b9129337fbdc37939f09ae4c0af2c662d9bf97ad


{BUG} findOrCreate creates a bug, it refuses to identify inputs.*anything

     inputs: {
      phone: { type: "string", required: true }
     // ....... //
      },
     exits :{
 phoneAlreadyInUse: {
      statusCode: 409,
      description: "The provided phonenumber  is already in use."
    }//....//}
     }
     fn: async (inputs, exits){
          var newUserRecord = await Owner.findOrCreate({
            phone: inputs.phone, // using `findOrCreate` creates a bug! but passes well using create
            phraseCode: inputs.phraseCode
        }).intercept("E_UNIQUE", "phoneAlreadyInUse");
     }

This throws this error
 UsageError: Invalid initial data for new record.
Details:
  Missing value for required attribute `phone`.  Expected a string, but instead, got: undefined

But when I use find, create or any other stuff, it works normally and just fine

I was looking at the upgrade documentation from something completely unrelated and stumbled on to this.

So maybe you need to set your type: 'json'

@navicstein looks like the usage is a bit off — findOrCreate expects two arguments:
https://sailsjs.com/documentation/reference/waterline-orm/models/find-or-create


[BAT]merge new ui code

Coverage increased (+0.8%) to 56.008% when pulling 98f9c2d16588992378c2eb5c5e8f95ef4ab597ad on sigsbee:drone3 into 551e679652ce71b819eb0f4d9052b02c1ff7c40d on vmware:drone.

Coverage decreased (-5.4%) to 49.827% when pulling 011524c2abac8c0021ecc46cb9c3621bb4f98093 on sigsbee:drone3 into 551e679652ce71b819eb0f4d9052b02c1ff7c40d on vmware:drone.


Starting collaboration session

Issue Type: Bug
Starting collaboration session: Could not connect to the server. HTTPS connection failed, verify there are no self-signed certificates or custom cert validation policies blocking Live Share.
Extension version: 1.0.1123
VS Code version: Code 1.39.2 (6ab598523be7a800d7f3eb4d92d7ab9a66069390, 2019-10-15T15:33:40.634Z)
OS version: Linux x64 5.3.0-19-generic

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-4310U CPU @ 2.00GHz (4 x 2751)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwareoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: disabled_softwareskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: unavailable_offviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
4, 2, 2

Memory (System)
7.66GB (0.13GB free)

Process Argv

Screen Reader
no

VM
0%

Thanks for reporting this, @taharqajr  Can you also share your logs? You can access them via the Live Share: Export Logs command from the command palette (ctrl + shift + p) and attach them to this issue.

Closing due to age. If you're still seeing a problem, please feel free to re-activate.


Feature querying now works when sequences renamed

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
597 unchanged lines in 16 files lost coverage.
Overall coverage increased (+0.006%) to 91.564%

Files with Coverage Reduction
New Missed Lines
%

.nox/test-3-10/Lib/site-packages/cogent3/core/alignment.py
32
93.91%

.nox/test-3-11/Lib/site-packages/cogent3/core/alignment.py
32
93.91%

.nox/test-3-12/lib/python3.12/site-packages/cogent3/core/alignment.py
32
93.91%

.nox/test-3-12/Lib/site-packages/cogent3/core/alignment.py
32
93.91%

.nox/test-3-9/Lib/site-packages/cogent3/core/alignment.py
32
93.87%

.nox/test-3-10/lib/python3.10/site-packages/cogent3/core/alignment.py
33
93.91%

.nox/test-3-11/lib/python3.11/site-packages/cogent3/core/alignment.py
33
93.91%

.nox/test-3-9/lib/python3.9/site-packages/cogent3/core/alignment.py
33
93.87%

.nox/test-3-10/lib/python3.10/site-packages/cogent3/core/sequence.py
42
94.66%

.nox/test-3-10/Lib/site-packages/cogent3/core/sequence.py
42
94.66%

Totals

Change from base Build<PHONE_NUMBER>:
0.006%

Covered Lines:
236582

Relevant Lines:
258378

💛  - Coveralls


can't include 'ng2-bootstrap' external dependency

Tried to include ng2-bootstrap, but during building I got this message:
d:/Development/angular2-seed/node_modules/ng2-bootstrap/components/datepicker/da
te-formatter.ts(1,25): error TS2307: Cannot find module 'moment'.

You need to install the type definitions for moment:
typings install moment --ambient --save

You may also need to install momentjs in case it is a peerDependency.

after installing momentjs & its type definition:
 moment.d.ts (9,21): Cannot find namespace 'moment'

Got it! Had to install without the flag --ambient.

Now you need to configure systemjs in config.ts. Just set path to the momentjs bundle.

Right, still using SystemJS for dev, sorry!

Failed to load resource: the server responded with a status of 404 (Not Found)
2016-02-24 20:40:40.955 localhost/:70 Error: XHR error (404 Not Found) loading http://localhost:5555/node_modules/moment.js(…) "Report this error at https://github.com/mgechev/angular2-seed/issues"(anonymous function) @ localhost/:70
I think this is the same issue.
npm install moment --save
typings install moment --save
(also tried with --ambient).
How do I configure systemjs in config.ts? DEV_NPM_DEPENDENCIES or PROD_NPM_DEPENDENCIES?
According to the wiki adding external packages should be a no-brainer, so is this a bug in angular2-seed/ng2-bootstrap or has it something to do with changes I made?

@raoel  you likely need this in tools/config.ts:  (in part, just add moment like so)
const SYSTEM_CONFIG_DEV = {
  defaultJSExtensions: true,
  paths: {
    [BOOTSTRAP_MODULE]: `${APP_BASE}${BOOTSTRAP_MODULE}`,
    'angular2/*': `${APP_BASE}angular2/*`,
    'rxjs/*': `${APP_BASE}rxjs/*`,
    '*': `${APP_BASE}node_modules/*`,
    'moment': `${APP_BASE}node_modules/moment/moment`
  },
  packages: {
    angular2: { defaultExtension: false },
    rxjs: { defaultExtension: false }
  }
};

// you also need to add to production setup like this:
export const SYSTEM_BUILDER_CONFIG = {
  defaultJSExtensions: true,
  paths: {
    [`${TMP_DIR}/*`]: `${TMP_DIR}/*`,
    '*': 'node_modules/*',
    'moment': `node_modules/moment/moment.js`
  }
};

In your system.js please tell system to look for moment.js as the default file. Moment is installed with some other js files as well.
https://github.com/valor-software/ng2-bootstrap/issues/663#issuecomment-230149877
There you go. Solved it for me.

@NathanWalker How does your solution map onto the new-look tools/config.ts which references tools/config/project.config.ts which extends tools/config/seed.config.ts?
In tools/config/project.config.ts I have:
this.NPM_DEPENDENCIES = [
       {src: 'ng2-bootstrap/*.js', inject: 'libs'},
       {src: 'moment/moment.js', inject: 'libs'},
    ];

but this still gives me:
Error on fetch for moment.js at file:///C:/[path shortened]/node_modules/moment.js
        Loading ng2-bootstrap/components/datepicker/date-formatter.js
        ...etc.

There doesn't seem to be any way to provide the 'map' solution that @raoel mentions....

Is it a possibility to work with SystemJS for you? There you can provide map paths.

Thanks @alfakappa - I was working with SystemJS in my dev environment and had ng2-bootstrap/moment working with the following in my systemjs.config.js:
(function(global) {
// map tells the System loader where to look for things
var map = {
'app':                        'app', // 'dist',
'@angular':                   'node_modules/@angular',
'angular2-in-memory-web-api': 'node_modules/angular2-in-memory-web-api',
'rxjs':                       'node_modules/rxjs',
'ng2-bootstrap':              'node_modules/ng2-bootstrap',
'moment':                     'node_modules/moment/moment.js'
};
// packages tells the System loader how to load when no filename and/or no extension
var packages = {
'app':                        { main: 'main.js',  defaultExtension: 'js' },
'rxjs':                       { defaultExtension: 'js' },
'ng2-bootstrap':              { defaultExtension: 'js' },
'angular2-in-memory-web-api': { main: 'index.js', defaultExtension: 'js' }
};
However I thought the angular2-seed looked as if it was going to give me the easiest route to building my project for deployment so have just spent all morning getting it working in this...and it doesn't seem to be using SystemJS?
Is there a 'map' equivalent in angular2-seed?

you should not use .js in your var map.
use it only in packages.
map is not correct when using a final path. packages just tells which file to start with (which is actually moment.js) but needs a reference path to include other files in moment.js. It will take it from map. if you make that a "moment.js" it will look for a folder moment.js (which does not exist)
take a look at the issue I referenced. It gives an exact systemjs config file which works fine.

Thanks @alfakappa - I've abandoned the SystemJS build now anyway, now that I have got it working and deployable in angular2-seed, but have edited my comment above for the benefit of those arriving here looking for solutions.

                                **>-------- Moment--------->**

Use these commands to add these dependencies to your package.json
npm install moment --save
Modify your System.config.js to the following code :
var map = {
'app':                        'app', // 'dist',
'@angular':                   'node_modules/@angular',
moment:              'node_modules/moment/moment.js',
};
Then, U are good to go for moment.


get machine object

What this PR does / why we need it:
print all node names after pressing  eg. gardenctl ssh .

Which issue(s) this PR fixes:
Fixes https://github.com/gardener/gardenctl-v2/issues/323
Special notes for your reviewer:
Release note:

from the issue #323 description:

There should be an option where gardenctl also considers the machine objects, but this requires access to the control-plane.

@tedteng I understand this PR is still in draft, but please consider the case where a regular end-user is not authorized to access the control plane

Hi, @petersutter can we process this PR? thanks.

Hi ted I thought you were working on https://github.com/gardener/gardenctl-v2/pull/347#discussion_r1377079306 for which you did not have any solution at the time you were writing the comment. See my comment there

/retest

Can we process this PR. Thanks.


Replacing hand instantiated clock gate cells

Code has hand-instantiated clock gating cells which are defined in below library.
swerv_el2/rtl/lib/beh_lib.sv
module `TEC_RV_ICG
Generally such clock gates are not synthesized, rather a specific specially design cells is picked up from tech library as we don't want any random unbalanced combo logic on clock path, and timing has to be carefully done.
I do see this particular module being different from the rest in library and using a define for module name. So I am guessing that there was an intent to handle this differently and perhaps allow it to be replaced without having to edit the  riscv core code.
But I am not able to see how to achieve that - could someone please clarify?

I recommend either:
a) Omit the module definition
or
b) ifdef synthesizable portion and leave intentional placeholder for per-integrator replacement.
a) Omit : force user substitution by TECH_SPECIFIC_EC_RV_ICG
751 ifndef TECH_SPECIFIC_EC_RV_ICG 752 module TEC_RV_ICG
...
775 endmodule
776 `endif
b) ifdef synthesizable portion and leave intentional placeholder for per-integrator replacement.
757 ifndef TECH_SPECIFIC_EC_RV_ICG 758    logic  en_ff; 759    logic  enable; ... 773    assign Q = CK & en_ff; 774 else  //TECH_SPECIFIC_EC_RV_ICG
775   user_tech_icg user_tech_icg_inst (.Q(Q), .SE(SE), .EN(EN), .CK(CK));  //user tech cell replacement
776 `endif //TECH_SPECIFIC_EC_RV_ICG

looks good to me, assuming module user_clock_gate sits in area outside of the core (which it does seem so).

just add +define+TECH_RV_ICG= to synthesis or compilation command
Or patch this define in generated  common_defines.h

@algrobman Adding the define is not enough as the module in question is defined inside beh_lib.sv: https://github.com/chipsalliance/Cores-VeeR-EL2/blob/ff9ad9bdbd88aa6d0314d2a1d921122c34c182b8/design/lib/beh_lib.sv#L752-L775
There will be name conflict with the custom one from the external tech library.

@rahuljainNV could you close if completed?

@nstewart-amd  - are you able to use this option as part of Caliptra codebase?
just checking if this is working end to end with caliptra flow as well.

@nstewart-amd - are you able to use this option as part of Caliptra codebase? just checking if this is working end to end with caliptra flow as well.

@rahuljainNV - I think this will work.  So far, it looks like we've been picking up the default inferred gaters since the code is written to default in that direction.  My preference is that the integrator should have a "force function", that requires them to define the cell (else FAIL to compile).  It's a bit of a silent failure at compile time here and will only get picked up by post compile design checks.
Also... please note that the same scenario exists the synchronizers.  Most integrators will have a foundry/technology specific synchronizer, likely exceeding 2 flop depth.


bug(python): error when adding to the database in v0.10

LanceDB version
v0.10.1 and v0.10.0
What happened?
I'm using lancedb as the vector database in our RAG app. We have populate functionality to ensure that the data in the database is up-to-date. Upon upgrading lancedb from v0.9.0 to v0.10.1 (also tested with v0.10.0), the population fails when adding data to the database.
What I'm using:

MacOS Sonoma 14.5
python 3.11.7
lancedb v0.10.1
lancedb.AsyncConnection
pydantic 2.8.0 (schema inheriting from lancedb.pydantic.LanceModel)
a custom lancedb.embeddings.TextEmbeddingFunction with the lancedb.embeddings.EmbeddingFunctionRegistry

table = await db_lance_client.create_table(  # the table gets created successfully
      name=collection_name,
      mode="overwrite",
      schema=get_schema_document().to_arrow_schema(),  # get_schema_document() returns the class inheriting from Lancemodel
)
await table.add(data=data)  # <----- This is where the error occurs
await table.optimize(cleanup_older_than=datetime.timedelta(seconds=1))
await table.create_index(column="processed_text", replace=True)

Executing the code with RUST_BACKTRACE=full yields this error:
[2024-07-19T10:11:37Z WARN  lance::dataset] No existing dataset at /path/to/db_folder/db/db_collection.lance, it will be created
thread 'tokio-runtime-worker' panicked at /Users/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/lance-encoding-0.14.1/src/encodings/physical/binary.rs:387:39:
Indices array is empty
stack backtrace:
thread 'tokio-runtime-worker' panicked at /Users/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/lance-encoding-0.14.1/src/encodings/physical/binary.rs:387:39:
Indices array is empty
   0:        0x116ed8068 - _PyInit_pyo3_asyncio
   1:        0x115a23d54 - _blake3_compress_in_place_portable
   2:        0x116eb0908 - _PyInit_pyo3_asyncio
   3:        0x116edbd58 - _PyInit_pyo3_asyncio
   4:        0x116edb4fc - _PyInit_pyo3_asyncio
   5:        0x116edd0d8 - _PyInit_pyo3_asyncio
   6:        0x116edc050 - _PyInit_pyo3_asyncio
   7:        0x116edbfb8 - _PyInit_pyo3_asyncio
   8:        0x116edbfac - _PyInit_pyo3_asyncio
   9:        0x116fe9254 - _PyInit_pyo3_asyncio
  10:        0x115a29790 - _blake3_compress_in_place_portable
  11:        0x116fe959c - _PyInit_pyo3_asyncio
  12:        0x1167f8ef0 - _blake3_compress_in_place_portable
  13:        0x1167fca4c - _blake3_compress_in_place_portable
  14:        0x1167fc064 - _blake3_compress_in_place_portable
  15:        0x116ef40b0 - _PyInit_pyo3_asyncio
  16:        0x116efc45c - _PyInit_pyo3_asyncio
  17:        0x116ee7088 - _PyInit_pyo3_asyncio
  18:        0x116ee6d78 - _PyInit_pyo3_asyncio
  19:        0x116edfabc - _PyInit_pyo3_asyncio
  20:        0x19122ef94 - __pthread_joiner_wake
stack backtrace:
   0:    thread 'tokio-runtime-worker' panicked at /Users/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/lance-encoding-0.14.1/src/encodings/logical/primitive.rs:421:32:
called `Result::unwrap()` on an `Err` value: JoinError::Panic(Id(43), ...)
    0x116ed8068 - _PyInit_pyo3_asyncio
   1:        0x115a23d54 - _blake3_compress_in_place_portable
   2:        0x116eb0908 - _PyInit_pyo3_asyncio
   3:        0x116edbd58 - _PyInit_pyo3_asyncio
   4:        0x116edb4fc - _PyInit_pyo3_asyncio
   5:        0x116edd0d8 - _PyInit_pyo3_asyncio
   6:        0x116edc050 - _PyInit_pyo3_asyncio
   7:        0x116edbfb8 - _PyInit_pyo3_asyncio
   8:        0x116edbfac - _PyInit_pyo3_asyncio
   9:        0x116fe9254 - _PyInit_pyo3_asyncio
  10:        0x115a29790 - _blake3_compress_in_place_portable
  11:        0x116fe959c - _PyInit_pyo3_asyncio
  12:        0x1167f8ef0 - _blake3_compress_in_place_portable
  13:        0x1167fca4c - _blake3_compress_in_place_portable
  14:        0x1167fc064 - _blake3_compress_in_place_portable
  15:        0x116ef40b0 - _PyInit_pyo3_asyncio
  16:        0x116efc188 - _PyInit_pyo3_asyncio
  17:        0x116ee7088 - _PyInit_pyo3_asyncio
  18:        0x116ee6d78 - _PyInit_pyo3_asyncio
  19:        0x116edfabc - _PyInit_pyo3_asyncio
  20:        0x19122ef94 - __pthread_joiner_wake
stack backtrace:
   0:        0x116ed8068 - _PyInit_pyo3_asyncio
   1:        0x115a23d54 - _blake3_compress_in_place_portable
   2:        0x116eb0908 - _PyInit_pyo3_asyncio
   3:        0x116edbd58 - _PyInit_pyo3_asyncio
   4:        0x116edb4fc - _PyInit_pyo3_asyncio
   5:        0x116edd0d8 - _PyInit_pyo3_asyncio
   6:        0x116edc050 - _PyInit_pyo3_asyncio
   7:        0x116edbfb8 - _PyInit_pyo3_asyncio
   8:        0x116edbfac - _PyInit_pyo3_asyncio
   9:        0x116fe9254 - _PyInit_pyo3_asyncio
  10:        0x116fe9564 - _PyInit_pyo3_asyncio
  11:        0x1167fbb48 - _blake3_compress_in_place_portable
  12:        0x116621780 - _blake3_compress_in_place_portable
  13:        0x11662613c - _blake3_compress_in_place_portable
  14:        0x1166251b0 - _blake3_compress_in_place_portable
  15:        0x116afc864 - _blake3_compress_in_place_portable
  16:        0x116afabf0 - _blake3_compress_in_place_portable
  17:        0x116b56bb4 - _blake3_compress_in_place_portable
  18:        0x116b4d8a0 - _blake3_compress_in_place_portable
  19:        0x116b4c7b4 - _blake3_compress_in_place_portable
  20:        0x11511f28c - <unknown>
  21:        0x1151e1614 - <unknown>
  22:        0x115189b9c - <unknown>
  23:        0x116ef4184 - _PyInit_pyo3_asyncio
  24:        0x116efc45c - _PyInit_pyo3_asyncio
  25:        0x116ee7088 - _PyInit_pyo3_asyncio
  26:        0x116ee6d78 - _PyInit_pyo3_asyncio
  27:        0x116edfabc - _PyInit_pyo3_asyncio
  28:        0x19122ef94 - __pthread_joiner_wake

I've tried to reproduce the failure with a fairly simple python script, but couldn't manage a successful reproduction in the simple script. I'll try figure out at what complexity it starts producing this error. Hopefully the provided backtrace is enough for you to find the root of the problem.
Please let me know if I should provide any additional information.
Are there known steps to reproduce?
No response

This error is coming from the new v2 reader which is still experimental.  We made a breaking change to it between version 0.9 and 0.10.  Is it possible you set use_legacy_format=False when you created the original dataset?
There's not a great fix.  If it's easy for you to recreate your dataset then that might be the best approach.  If not, I can investigate what it would take to add in backwards compatibility for that change.

Thanks for the reply. I tried it with use_legacy_format=False, but that produced the same error message. With use_legacy_format=True, however, it worked.
There are 2 points:
Point 1)
The code documentation for use_legacy_format states that the default value is True
        use_legacy_format: bool, optional, default True
            If True, use the legacy format for the table. If False, use the new format.
            The default is True while the new format is in beta.

but it's actually None
use_legacy_format: Optional[bool] = None,

The default behaviour seems to be the same as use_legacy_format=False, not use_legacy_format=True.
I suspect it's because the rust code only does something if a value exists (in lancedb/python/src/connection.rs:
    if let Some(use_legacy_format) = use_legacy_format {
            builder = builder.use_legacy_format(use_legacy_format);
        }

Point 2)
Could the documentation be updated to state that a breaking change was introduced? My first reaction, after discovering a new version was released, is to view the release information for new features and breaking changes. Nothing critical was mentioned in the v0.10.0 and v0.10.1 release notes.

You're right, this is a bug when creating tables without initial data, and a pretty serious one.  I've created https://github.com/lancedb/lancedb/pull/1469 with a fix and will get a release out today.

but it's actually None

The underlying behavior is True.

I suspect it's because the rust code only does something if a value exists

That part is ok (builder defaults to use_legacy_format=false).  Unfortunately, when creating a table with no data, we don't actually set the format of the table.  It gets set later, once data is first added, and that happens during the add call which is regrettably defaulting use_legacy_format to false.

Could the documentation be updated to state that a breaking change was introduced?

This was a major bug, not an intentional change.

Version 0.10.2 is publishing and contains the fix.  Creating an empty table will not use the v2 format unless specified.  Let me know if you are seeing otherwise.

Thank for you for the fix. Here's a summary of things I've noticed with v0.10.2:

creating a table without specifying use_legacy_format and then adding works as expected.
opening a table that was created with v0.9.0 raises an error. (luckily we refresh/overwrite the values often, so it doesn't affect my situation greatly.
creating a table while specifying use_legacy_format=False raises an error.

v0.10.2 fixes the bug sufficiently, so I'm going to close this issue. Maybe you find the abovementioned summary useful.
Thanks for quick response. Keep up the good work!


Update golang parser regex

:zap: Summary
I updated go to go 1.22 and noticed that CI was failing to upload test coverage to coveralls. I discovered that coveralls was detecting the file type as lcov when it should have been golang. This was because the regex in the golang parser expected three slashes in the file path for each file under test.
I updated the regex to only have one slash be required, while ensuring that existing tests didn't fail. I added two new fixture files and added two new tests to ensure the new behavior works correctly.
:ballot_box_with_check: Checklist

[X] Add specs

Thank you, @kjstouffer!
We aim to review and merge this week after a new planned release.

Hello @afinetooth! Any updates here?

@kjstouffer we have been working on that same release and have faced some challenges.
Therefore, I'm reviewing right now and will merge and cut a new release as soon as everything looks 👍 ...

Checks passed and changes merged.
Give me 30 min or so to cut the new release.

OK @kjstouffer, changes pushed to new release 0.6.14:
https://github.com/coverallsapp/coverage-reporter/releases


[WIP] Refactor quadicons 2nd phase

This is very much still a work in progress.
Purpose or Intent
The point of this refactoring is to make Quadicons more flexible, composable, and to over all Make Smaller Things
Thinking
New Quadicon classes coordinate the rendering of Quadrants (the corners), Badges (status like the compliance shield), a Label (text beneath), and the link when applicable. All this is configured by the Quadicon Context which is a sort of adapter between all the view state and the Quadicon. I hope this can evolve into a more explicit configuration object.
These changes allow for flexibility like changing the order and make up of the pieces of a Quadicon, or independent rendering of an element.
This code doesn't replace current functionality yet. New behavior can be seen in tests.
To Do

[ ] Reproduce existing functionality with composable classes

[x] VmOrTemplate
[x] Storage
[x] Configuration Manager Quadicon
[ ] Quadicon based on image from decorator (single/default)
[ ] EMS Cluster
[ ] EXT Management System
[ ] Host
[ ] Resource Pool
[ ] Service

[ ] Replace case statements with methods on decorator
[ ] Replace all images with CSS, SVGs, or Fonticons
[x] Combine label (text beneath) in full render
[ ] Confirm and remove unused logic
[ ] Speed up tests by checking less output (has_selector) and more config (includes)
[ ] Documentation

Don't let the + count scare you, about 2,100 lines are targeted for deletion.

Does this influence the decorators design&behavior?

@abonas It currently seems to me like the only function many of the decorator classes is to provide methods to interact with Quadicons. I'm not sure if they're really necessary, but I want to get feedback about it.

@hayesr decorators are a relatively new thing, and they provide the location of the icons for font, png and svg icons. cc @himdel @martinpovolny.
I just saw that in this PR some other places provide the icon location, so this is why I'm asking, to avoid (it happened multiple times lately) regressions in this area.

@hayesr We eventually want to get all the icon info into decorators, so if you can, please use them.. but it may take a few more steps to get there, I don't know :)

I definitely don't want to end up with duplicate places providing asset locations. They exist in the current code and right now I'm just moving code into classes and testing. (So far, just the render_vm_or_template_quadicon method) I expect it to evolve as I cover the different Quadicon types.
As for the decorator classes, what is the plan long term? Right now they seem like they could end up as just another "bag of methods" and then there's the extra Draper dependency. If we could make them unnecessary, wouldn't that be good?

@hayesr the plan is to have all the provider's UI config in a file owned by that provider, but separate from the model. (And same thing for the other models.) I don't think we can replace configuration with convention here, nor that we want to - it's better to make things explicit, but have them at a predictable place.
I actually want to add tests that would check all the decorators for consistency, as in, that all of them have/inherit a fonticon method, and that all the listicon_image methods include the directory and extension, but don't call image_path, etc.., which may address your bag of methods concern..?

Closing since this work is continuing in https://github.com/ManageIQ/manageiq-ui-classic/pull/59


Add config to allow jsx in classes

Our project has some utility classes which are not components but have some methods that return JSX. They don't need to be flagged by this lint rule, and all of our class-based components are already easily identified by the more narrow rules that look for classes extending React.Component.
This PR introduces a configuration option to allow disabling that "fuzzier" form of identification for component classes in projects that don't need it.

Awesome, thanks @noahm

I just realized I neglected to update the readme to document the new option. I can take care of that shortly if you'd like

I just realized I neglected to update the readme to document the new option. I can take care of that shortly if you'd like

Thanks, I tackled that in #12


Delta load support

At present we easily support direct loads, and with a little bespoke effort could support delta loads. However we will then land up with a wide range of brittle delta based implementations. We need to support delta loads as a first class load pattern and ensure all the good convention is in place there

Could we bring the existing delta work done in util.etl into maestro?
I think the existing delta implementation makes sense when the provided data has no structure, but I would hope that many data sets offer some sort of monotonic field which could be used to provide a better implementation.

Closing this since we support delta loads in util.etl.