Unable to Cross Compile ArmNN with the protobuf version 3.5.2 as it seems to be apparently missing

I am trying to cross-compile the ArmNN library in my machine(Ubuntu 18.04, Intel x86_64 CPU architecture) and am following the steps as mentioned in https://github.com/ARM-software/armnn/blob/branches/armnn_20_08/BuildGuideCrossCompilation.md.
However, when I try to download protobuf version 3.5.2 and install, protoc --version return 3.5.1. I have even tried to download the specific tag https://github.com/protocolbuffers/protobuf/releases/tag/v3.5.2 but to no avail. It still shows 3.5.1. I have ensured that there is no other libprotobuf in my machine except in the particular prefix as mentioned  in the Cross Compilation manual.
Following a protobuf version 3.5.1, when I try to build ArmNN library, make -j$(nproc) fails because of the following error, where it demands a newer version of protoc.
In file included from /home/sarthak/onnx/onnx/onnx.pb.cc:4:0:
/home/sarthak/onnx/onnx/onnx.pb.h:17:2: error: #error This file was generated by an older version of protoc which is
 #error This file was generated by an older version of protoc which is
  ^~~~~

/home/sarthak/onnx/onnx/onnx.pb.h:18:2: error: #error incompatible with your Protocol Buffer headers. Please
 #error incompatible with your Protocol Buffer headers.  Please
  ^~~~~

/home/sarthak/onnx/onnx/onnx.pb.h:19:2: error: #error regenerate this file with a newer version of protoc.
 #error regenerate this file with a newer version of protoc.

On the other hand, I have also tried as a sanity check to install protobuf version 3.6.0rc1 (https://github.com/protocolbuffers/protobuf/releases/tag/v3.6.0rc1, returns 3.6.0 on protoc --version) and faced the following error while building ArmNN:
In file included from /home/sarthak/onnx/onnx/onnx.pb.cc:4:0:
/home/sarthak/onnx/onnx/onnx.pb.h:17:2: error: #error This file was generated by an newer version of protoc which is
 #error This file was generated by an newer version of protoc which is
  ^~~~~

/home/sarthak/onnx/onnx/onnx.pb.h:18:2: error: #error incompatible with your Protocol Buffer headers. Please
 #error incompatible with your Protocol Buffer headers.  Please
  ^~~~~

/home/sarthak/onnx/onnx/onnx.pb.h:19:2: error: #error regenerate this file with a older version of protoc.
 #error regenerate this file with a older version of protoc.

How to solve this issue? Does protobuf version 3.5.2 not exist?
Is there any downgraded version of ArmNN that can work with protobuf version 3.5.1 and if there is, what are its corresponding dependencies?

Hi @sarthak-chakraborty
Is it possible that you have another version of protobuf installed somewhere on your build machine? What does which protoc return?
Internally we have begun to use v3.12.0 of protobuf could you try with that one?
Best regards,
Mike


README Incorporated

The contents of the GitHub README has been incorporated into the standard.  Potentially relevant text from the previous version has also been retained. More to come.

Hi Chuck,
lots of work done indeed, great! I am surprised to read that the core is
described as restricted to x/y subsetting, did we discuss this? We have been
discussing for a long time in the WCS.SWG, with strong push by MetOcean, that h

time are indispensable. Maybe if we subset a climate data set we don't want to
get all height levels and all time slices back, the resulting volume could be
overwhelming. As it stands, we'd be falling back to 2010 where coverages by some
were seen as limited to flat images.

-Peter
On 09.12.19 02:05, Chuck Heazel wrote:

The contents of the GitHub README has been incorporated into the standard.
Potentially relevant text from the previous version has also been retained.
More to come.

    You can view, comment on, or merge this pull request online at:

https://github.com/opengeospatial/ogc_api_coverages/pull/33
    Commit Summary

README Incorporated
File Changes

M standard/clause_7_core.adoc
https://github.com/opengeospatial/ogc_api_coverages/pull/33/files#diff-0
(212)

A standard/examples/examples.adoc
https://github.com/opengeospatial/ogc_api_coverages/pull/33/files#diff-1
(31)

A standard/figures/WCS_CoverageOfferings.png
https://github.com/opengeospatial/ogc_api_coverages/pull/33/files#diff-2
(0)

M standard/requirements/requirements_class_core.adoc
https://github.com/opengeospatial/ogc_api_coverages/pull/33/files#diff-3
(2)
Patch Links:

https://github.com/opengeospatial/ogc_api_coverages/pull/33.patch

https://github.com/opengeospatial/ogc_api_coverages/pull/33.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/opengeospatial/ogc_api_coverages/pull/33?email_source=notifications&email_token=ABOR5DUFSOBDBMRI3OSRKELQXWKWLA5CNFSM4JYBVGQ2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H655BAA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABOR5DTSVNNJBCCTZZ6XZ4LQXWKWLANCNFSM4JYBVGQQ.

--
Dr. Peter Baumann

Executive Director, rasdaman GmbH Bremen (HRB 26793)
www.rasdaman.com, mail<EMAIL_ADDRESS>tel: 0800-rasdaman, fax: 0800-rasdafax, mobile: +49-173-5837882
Professor of Computer Science, Jacobs University Bremen
www.faculty.jacobs-university.de/pbaumann
mail<EMAIL_ADDRESS>tel: +49-421-200-3178, fax: +49-421-200-493178
"A brilliant idea is a job halfdone."

@pebau Don't get upset yet. The content which is not from the README is left over from over six months ago. My next task is to identify what should be removed (since it is inherited from Common) and what needs to be updated.

got that, thanks for clarifying! Seems we'll have a busy meeting in January!
-Peter
On 09.12.19 04:29, Chuck Heazel wrote:

@pebau https://github.com/pebau Don't get upset yet. The content which is
not from the README is left over from over six months ago. My next task is to
identify what should be removed (since it is inherited from Common) and what
needs to be updated.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/opengeospatial/ogc_api_coverages/pull/33?email_source=notifications&email_token=ABOR5DV37GWGWK2GUWF7GIDQXW3QPA5CNFSM4JYBVGQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGHWYVA#issuecomment-563047508,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABOR5DVYYFJCL7K6ALBAH63QXW3QPANCNFSM4JYBVGQQ.

--
Dr. Peter Baumann

Executive Director, rasdaman GmbH Bremen (HRB 26793)
www.rasdaman.com, mail<EMAIL_ADDRESS>tel: 0800-rasdaman, fax: 0800-rasdafax, mobile: +49-173-5837882
Professor of Computer Science, Jacobs University Bremen
www.faculty.jacobs-university.de/pbaumann
mail<EMAIL_ADDRESS>tel: +49-421-200-3178, fax: +49-421-200-493178
"A brilliant idea is a job halfdone."


Add the next buses as an attr to the sensor

So it would be nice as we are fetching the data to make it available. This adds the buses data to the sensor as an attribute.
It enables the rendering of pages such as

Thank you for the addition!


Maybe move gravity decision to an ai component

Need to rethink about the PhysicsComponent and RigitComponent. If we move the gravity behavior to an AI component then the others might be merged :)

It should be an AI because now 2 components can decide what the actor does next. That gives unexpected behavior. By moving it to an AI an actor has only one decision maker

Done https://github.com/JordyMoos/elm-pixel-boulder-game/pull/36


Cant load dataset

I set up the elastic search and all the containers are up & running.
But I'm facing an issue while loading the dataset to elastic search. I setup the mappings & trying to load dataset [
I'm following the Tutorial - https://www.elastic.co/guide/en/kibana/current/tutorial-load-dataset.html.]
On running the curl upload command -
curl -H 'Content-Type: application/x-ndjson' -XPOST 'localhost:9200/bank/account/_bulk?pretty' --data-binary @accounts.json,
I'm getting the error 'curl: (52) Empty reply from server'.
On listing the docker containers it shows the below containers are running successfully.
docker.elastic.co/kibana/kibana:6.3.0 "/usr/local/bin/kiba…" 2 hours ago Up 2 hours (healthy) <IP_ADDRESS>:5601->5601/tcp kibana
a3aa8556c225 docker.elastic.co/logstash/logstash:6.3.0 "/usr/local/bin/dock…" 2 hours ago Up 2 hours (healthy) 5044/tcp, 9600/tcp logstash
79c75ecde762 docker.elastic.co/elasticsearch/elasticsearch:6.3.0 "/usr/local/bin/dock…" 2 hours ago Up 2 hours (healthy) <IP_ADDRESS>:9200->9200/tcp, 9300/tcp elasticsearch
But when I checked for [http://localhost:9200/bank ] it is not up & running. Not sure what is wrong here.

@Rajashreegr soo it looks to me like stack-docker is functioning properly and as intended.
The bigger issue is getting your dataset into Elasticesarch.
So can you check a few things for me...
1: navigate to localhost:9200 in your browser and login with the username/password elastic/2. navigate tolocalhost:5600` and use the same username and password.
This is going to check that es and kibana are running and accessible via your host machine.
If both of those work, I'd suggest trying a few commands in the kibana console to try creating the index you wanna bulk index into delete the index.
if that works we well then we need to try doing a "bulk" load via kibana console (small subset of your data maybe 2-3 lines of your accounts.json file.
If that works then I'm going to say we need to look at the accounts.json and see if it's maybe too big for the size of the cluster..

Have you managed to turn off ssl? I have to use https.

I disabled the xpack ssl security in elasticsearch.yml file.
xpack.security.enabled: true
xpack.security.http.ssl.enabled: false
xpack.security.transport.ssl.enabled: false
Now the elastic search started properly but facing some other issue.  When I run the curl command on the Elastic search URL - http://localhost:9200, I'm getting the following output.
{
"name" : "xitm0Cn",
"cluster_name" : "docker-cluster",
"cluster_uuid" : "9N0lMgLVSWmipPgThJ_JoA",
"version" : {
"number" : "6.3.0",
"build_flavor" : "default",
"build_type" : "tar",
"build_hash" : "424e937",
"build_date" : "2018-06-11T23:38:03.357887Z",
"build_snapshot" : false,
"lucene_version" : "7.3.1",
"minimum_wire_compatibility_version" : "5.6.0",
"minimum_index_compatibility_version" : "5.0.0"
},
"tagline" : "You Know, for Search"
}
Now the Kibana & logstash are not able to reach elastic search and keep waiting for its connection.

@Rajashreegr
So lets go back and start at the beginning.
all you have to do to get the data set to load is run
curl -H 'Content-Type: application/x-ndjson' -u 'elastic:<your_elastic_password>' -k -XPOST 'https://localhost:9200/bank/account/_bulk?pretty' --data-binary @accounts.jso

Closing. @Rajashreegr if you're continue to having issues after using https in your curl to load the data please re-open the issue. Thanks


Added green hover effect

Fixes #
In the dashboard section
initially, on the hover mouse over the choose file button, the green effect was missing. So I added that by adding the CSS properties to the class of that button
Screenshots of the changes (If any) -

BEFORE:
https://user-images.githubusercontent.com/96808735/148106255-efeafc6a-3018-49f7-94a7-fbd77ccf1554.mp
Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

Coverage remained the same at 82.225% when pulling 37c1d7587c4273e9f473555059e804af0ae4536c on Snehagupta1907:users into d519756fd2e3adbeb251023d66ef1f0c5b79ba2e on CircuitVerse:master.

Fixed code climate issues...

Fix code climate issues...

ma'am I fixed it

Thanks for the contribution 🥇


[TA] CodeGen based on 3.1-preview.3

This PR focus on generating code for Text Analytics swagger 3.1-preview.3
https://github.com/Azure/azure-rest-api-specs/blob/master/specification/cognitiveservices/data-plane/TextAnalytics/preview/v3.1-preview.3/TextAnalytics.json

Create a feature branch to have all v3.1-preview.3 changes.
https://github.com/Azure/azure-sdk-for-java/pull/17182


Replace Microsoft.Azure.OperationalInsights dependency

Last month, the Azure SDK team shipped the Azure Monitor Query client library. This Azure.Monitor.Query package is intended to replace Microsoft.Azure.OperationalInsights. Please make plans to migrate. We're actively working toward deprecating the Microsoft.Azure.OperationalInsights package.

Hey @scottaddie ,
Thanks for the heads up about the deprecation.
Will take a look.
Thanks
Tobias

Solved in #46
FYI @scottaddie - version 6.1.0 onward is using Azure.Monitor.Query NuGet 🚀

@Zimmergren Thank you for migrating so quickly! Well done. 👏

You bet @scottaddie ,
Thanks for bringing this to my attention and being proactive.
Nobody likes deprecated libraries 😄
All the best,
Tobias.


[fix][cms] remains previous files under public dir on replacing file

Coverage decreased (-84.05%) to 0.0% when pulling 3ecb93ed3fdebcec78245e4b9ce28b4be493d10a on fix-remains-old-files-under-public-dir into 3fa21650b2e82e3601ad2423702800f5ea2d735d on master.


added temporary user settings page,

added shadcn avatar component, created profile page w display name, avatar and history setting

close #7


sharding: Support Tornado sharding by regexes

One should now be able to configure a regex by appending _regex to the port number:
[tornado_sharding]
9802_regex = ^[l-p].*\.zulipchat\.com$

(Not tested end-to-end yet.)

Preserving the ability to do hand overrides seems great; can be handy if we want to assign a dedicated shard to a problem realm for debugging or other reasons example.

Merged, thanks @andersk!


DOC: stream error in jupyter notebook langgraph_crag_local.ipynb

Issue with current documentation:
langgraph_crag_local.ipynb
in jupyter cell when is called app.stream(inputs):
triggers error for node "retriever" line 1125, in _prepare_next_tasks
val = proc.mapper(val)
TypeError: 'module' object is not callable
val variable in that moment is {}
python = "^3.11"
langchain-community = "^0.0.31"
tiktoken = "^0.6.0"
langchainhub = "^0.1.15"
chromadb = "^0.4.24"
langchain = "^0.1.12"
langgraph = "^0.0.31"
tavily-python = "^0.3.3"
langchain-mistralai = "^0.1.0"
Idea or request for content:
No response

Hm - do you run into this issue in versions after 0.0.40?

python = "^3.11"
langchain-community = "^0.0.38"
tiktoken = "^0.6.0"
langchainhub = "^0.1.15"
chromadb = "^0.4.24"
langchain = "^0.1.19"
langgraph = "^0.0.48"
tavily-python = "^0.3.3"
langchain-mistralai = "^0.1.6"
gpt4all = "^2.4.0"
docx2txt = "^0.8"


Object type spread

It would be nice to be able to spread an existing object type into another one:
type A = {
  foo: string,
  bar: number,
};
type B = {
  bar: boolean,
};
type C = {
  ...A,
  ...B,
};

In the above, C would resolve to { foo: string, bar: boolean }.
This is different from intersection types. With intersection types, A & B becomes something more like { foo: string, bar: number & boolean }, which the observant reader will notice is uninhabitable.

This would be incredibly useful to us, we extend types all the time just for arguments. This is really nice if a function has defaults, but then we want all functions called by that to actually have a proper object with all missing attributes filled in. A simple use case:
type OptionsInput = {
  a: number,
  b: ?string,
  c: Date
};

type FnOptions = {
  ...OptionsInput,
  b: string
};

function foo(opts: OptionsInput) {
  if (!opts.b) opts.b = 'some default';
  doSomethingWith(opts);
}

@STRML in this case intersection should probably work

@vkurchatkin It doesn't. For example, I'm intersecting such an optional property with a required property:
 16:   keys?: Array<string>,
              ^^^^^^^^^^^^^ undefined. This type is incompatible with
 22:   keys: Array<string>,
             ^^^^^^^^^^^^^ array type

Another thought: Even in cases where intersection would work, the spread syntax would enable an easier-to-read shorthand.
For example, to include common types in a disjoint union:
Currently, with intersections:
type Todo = {
  id: string,
  text: string,
};

type Action =
  | (
    {
      type: 'CREATE_TODO',
    } & Todo
  )
  | {
    type: 'DELETE_TODO',
    id: string,
  }
;

With spread:
type Todo = {
  id: string,
  text: string,
};

type Action =
  | {
    type: 'CREATE_TODO',
    ...Todo,
  }
  | {
    type: 'DELETE_TODO',
    id: string,
  }
;

Any status on this? This would be a huge help in defining so many types.

This would be useful to type database schemas.
Depending on how you perform queries, a field that represent a relationship with another table / document may return an id or an object (if you're asking for a join).
type Client = {
    id: string,
    name: string
};

type Campaign = {
    id: string,
    name: string,
    client: Client | string // <- this
};

This works, but forces you to check the type of the client field at run time. It feels awkward because you already know what this is going to be depending on what your query looks like.
I'd rather handle that sort of things on a case-by-case basis, something like that :
export type Campaign = {
    id: string,
    name: string,
    client: string
};

// somewhere else in the code, when querying Campaigns and populating the client field
import type { Client } from '.....';
import type { Campaign as CampaignBase } from '....';
type Campaign = {
    ...CampaignBase,
    client: Client
};

Would love to hear how you guys handle database / ORM stuff.

Any update on this? It would be very useful to handle the very common use case described by @STRML

👍

Another note on the usefulness of this feature: currently using intersection types the resultant errors can be rather indecipherable, displaying full lists of all the intersecting types. Simplified error messaging for spreads should be possible, given that a type mismatch will now be traceable to a single concrete property definition and never to something strange like an uninhabitable union, which is a problem that is fundamentally split between definitions in two locations.

I'm thinking of trying to tackle the code for this. Does anyone have thoughts about what the limitations of the spread operator should be?
How should it treat a spreaded object type that has an indexer or a callable?
Current thought: It should ignore callables and indexers.
Should it be able to spread unsealed object types? What should the behavior be?
Current thought: I have no idea. Example with intersections: https://flowtype.org/try/#0C4TwDgpgBAIhBmBDArgG2ABQE4HswGcoBeKAbygAtF84k1gAuKAIxx1QkQDsoBfAbgBQggMY4u+YFCwQAjsTKCBg0JCgBJLsAhYuiVNjyEStFOkMEoAMiiqIOeNLlDBM2QDoR+1M0QiA1grwyFwiwACW4gAUAJRkym7uSAAeCgBEAKxZALRZGbl5aS4AbohYthCSUAya2rr6FsaKUFBeqD5+-kzBoRHRcaS8ADSCAPSjLSlMAOTTIy1UNAhmjLZYyBBK-EA
Should it be able to spread intersection of object and/or union of object types?
Current thought: Being able to spread intersections of objects would help people who have been making do with intersections while waiting for the type spread operator. They are after all mostly identical operations if executed on objects with fully disjoint sets of properties. If the user wants the behavior that could ostensibly result for spreading a union, they should instead spread all the constituents of the union individually.

@conartist6, I think you can do something like {...?DefaultProps} today with
type DefaultProps = {callback: function};
type OptionalProps = $ObjMap<DefaultProps, <V>(v: V) => ?V>;

But you need to watch out for #2674.

That was one of the first things I looked at, but it is actually not correct! The problem is that it is creating optional values not optional keys.
https://flowtype.org/try/#0C4TwDgpgBACgTgezAZygXigbwFBSgMwQQC4oB+ZYOASwDsBzbAXwG5tsBjAGwENlUAwggC2YKBAAewCLQAmqAEoQeHYABIhohLRnAAPADcE1WQBpYiFOaMmAfFibtO2ylGmuMezWID0tlkA

This seems good to close!

This may need to be reopened,
I don't think the current implementation is what @samwgoldman proposed- see this example
The example above shows that
type A = {
  foo: string,
  bar: number,
};
type B = {
  bar: boolean,
};
type C = {
  ...A,
  ...B,
};

Does not resolve C to { foo: string, bar: boolean }.

@seveibar See https://github.com/facebook/flow/issues/3534. You can work around this by using exact types for now.

@STRML I get SyntaxError: Unexpected token when I try to use the spread notation. I found a suggestion to use flow comments to get around this issue, and it works, but I was wondering if you had a more elegant solution. Thanks!

Be sure your babel version is up to date for that.

Just tried 6.26.0 and got the same issue. As far as I can tell, that's the latest version of babel, right?

Oh right. I think it's only been merged into the 7.x branch.
Mark Siebert wrote:

Just tried 6.26.0 and got the same issue. As far as I can tell, that's
the latest version of babel, right?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/flow/issues/1326#issuecomment-338051875,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABJFPyrhAgaXo9k7JjwcMOYOvuBm5Lleks5st8hogaJpZM4HN5PG.

Cool. Thanks for your help. :+1: I'll just stick with the comment syntax for now.

@conartist6 you can do what you asked here using a combination of spreading and $Shape like follows:
type Result = {
  ...$Shape<OtherType>,
  // additional entries
};

Does object type spread work?
// @flow

type Foo = {bar: number}
type Foo2 = {...Foo}

function f(foo: Foo2) {
	const n: number = foo.bar // should be fine, right?
}

7: 	const n: number = o.foo                      ^ Cannot assign `o.foo` to `n` because undefined [1] is incompatible with number [2].
References:
3: type Foo = {foo: number}
                    ^ [1]
7: 	const n: number = o.foo
             ^ [2]

@jedwards1211 it works fine in master

all released versions I've tried don't work though, going back a long way.  So I'm not sure whether it's a bug or something I fundamentally misunderstand about how object type spread is intended to work

it's long standing bug

https://medium.com/flow-type/coming-soon-changes-to-object-spreads-73204aef84e1


Consider alternate storage mechanism for build command output

Currently, 75% of our database storage is build command output, if I had to guess, more than 95% of it is never seen. So, the majority of this data does not have a lot of value to us or users. We should explore alternative ways of reducing the storage requirements here, while also aiming to reduce our operational overhead. Discussions here will feed directly into how we upgrade (or avoid upgrading) our database server.
 This could be the case now, but eventually our database will outgrow our budget, and the bigger database servers are not cheap.
Option 2: more complex database usage
We could disregard usage patterns and instead turn to database sharding or partitioning, but these are heavy operational changes. Partitioning would at least be seamless from the aspect of the open source project, but would require special maintenance. We'd have the option of putting some of the data on cold storage.
Problems here are that rackspace's network disks are horribly unreliable and go belly up several times a year. I don't want to have to rescue our database.
Sharding could help, but I'm not sure what exactly we shard on. Database design would need to be reconsidered here, as it would likely be on project or user, but we still need to run join selects across shards.
Option 3: don't store build command output in database
This data could probably exist just fine in Cloudfiles/s3. When users view the build command output, we'll fetch the json blob from cold storage, cache, and serve the data to the user -- all through our API.
The downside would be that our build command update mechanism, and likewise the build command live updated, would need to be reworked to respect the fact that pulling down a json blob continuously probably won't work well. On viewing this data, a slight delay might be introduced as we proxy the JSON.
A strong benefit here is that this moves the operational load to rackspace/amazon, doesn't require us to continually revisit upgrading or breaking up our database.
Another benefit, build data would be served through a CDN if we didn't proxy it. We'd store the link to the build data in the build model object.
Yet another benefit: cost would be about $10/mo for storage of 100G of data
Option 4: rethink build data storage
Further reconsidering data, does having any more than the last 5 builds, or last 2 weeks, or 2 months even, of build data help anyone? Does historical build data really help anyone? We could just be storing failures, or otherwise deviating from the CI style tracking of all build data.
This won't work for use cases like integration with GitHub PRs though, we do need historical build data for display here, along with potentially storing build assets. So, this might be the wrong way to approach things.
Things we need to determine

[ ] What portion of build pages have pageviews
[ ] How many pageviews go to build output pages
[ ] What would flat file storage look like in terms of live updates -- is live update a requirement?
[ ] What would the update mechanism be for flat file storage? How do we disturb the modeling the least and avoid complicating local development?

I like keeping the data in cold storage. We could cache the last 2 weeks of data in the DB, and have a background task that syncs it to cold storage for old builds.

I think using cold storage here also paves the path for doing PR-based archiving of content as well. We could use a similar model where we keep the PR data on our web servers for 3 days, and then move it to cold storage in cloud files.

Good point on syncing. If we added a field to Build objects for the JSON blob URL, a celery scheduled task could exist to continually move this data into cold storage. This would leave local development untouched, and the syncing code could simply be an extension to RTD. Also leaves live updating in tact and would be entirely seamless.
If we kept the data structure of the API, the front end code just needs to be re-pointed to the JSON url.
I like this plan so far. 👍

Just had another thought on private repository support, we'll want authentication on the files. Not sure this is possible with cloudfiles, but is with s3. We can support either if we proxy through our API, but this doesn't leverage the CDN support. s3 is probably a better target here, as we can assign arbitrary authentication acls, i believe.

This is in production! Our database is not growing (as fast). 🎉


Visualisation layer under labels / lakes

We have disabled labels on the map as they were under the viz layer. We should find a way to insert the viz layer just under the viz layer, see https://deck.gl/docs/api-reference/mapbox/overview#inserting-a-2d-deck-layer-before-an-existing-mapbox-layer.

Labels over viz layer
Lakes over viz layer

This could be done via different layer styles.

Notes from Weekly Call (06.04.2022)

The shapes are stacked and you cannot see everything (e.g. in Tessin the shapes are over the lakes, whereas int he West of CH it is ok) - this is due to the lake layer being under the shapes.

Let's also check https://github.com/visualize-admin/visualization-tool/issues/479

Fixed by #514


hotfix - corrects release version

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Introductory Price parsing (#186)

Parsing SKProduct's introductoryPrice if available (on iOS 11.2+), returned as an object with all properties on the native object. Enum's parsed as strings.
Tested on iOS 9.3 and 11.4 devices, and iOS 12 emulators with products without introductoryPrice, free trials and pay as you go.
Readme updated

Maybe I should have used Dictionaries instead of switches. Will refactor later.

+1


Good file manager!

Thanks for a good file manager! I like it for the tags function because it's useful and help me managae files that are in multiple drives.
I'd like you to let me "move" files when dragging files through tabs. Copying files and deleting original files take time.
I'm using preview version <IP_ADDRESS> and there is a bit of lag when overflow context menu is shown. Also, I can't set this as the default file manager.

Try draghing while keeping Control or Shift key pressed. It should move the files.


Run TemplateHaskell with sandboxing

From Luite:

By the way, GHCJS runs Template Haskell with a JS engine now (it used to load native code) so it's not all that hard to build a variant that is safe enough for untrusted code. The standard implementation is a small server script that runs on node.js. GHCJS first sends the runtime system and the actual Template Haskell runner code, and then incrementally all compiled splices and their dependencies. You could for example modify the script to use a node.js sandbox, if you're more adventurous you could even send it to the user's browser.

This is of no value for the educational environment.  But it might be a good idea for Haskell mode, since it would make easier use of lens and similar libraries...


fix: query keys with context

What is the purpose of this pull request?

What problem is this solving?

Types of changes

[ ] Feat: (new functionality)
[ ] Bug fix: ([#ref number] non-breaking change which fixes an issue)
[ ] Chore: (improvements that will not reflect in production behaviour)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Requires change to documentation, which has been updated accordingly.

#153  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @keeganpotgieter and the rest of your teammates on  Graphite


Any possibility to train/finetune HuBert using custom data

This is really great job! I am wondering if textlesslib could also support training or finetuning HuBert with custom data.
For example not just in English but other language data.

Hello,
Thanks for your interest!
Training or fine-tuning of HuBERT in textlesslib is not planned at the moment. Please refer to fairseq's codebase to do so: https://github.com/pytorch/fairseq/tree/main/examples/hubert

Sure, thanks.


openai[minor],docs[minor]: Add parallel tool calls call option and docs

Also bumped openai to latest version

Thanks, will merge later!


Allow Response subclasses to set default_mimetype as None

This matches the type - see https://github.com/pallets/werkzeug/blob/92c6380248c7272ee668e1f8bbd80447027ccce2/src/werkzeug/sansio/response.py#L94.

The linked annotation should be fixed instead.

In case it changes your mind:
My use case is that I want to give responses without a Content-Type header.
In particular, I am making a mock of a service which does that, and I want to copy that service.

@davidism There's even this in the Werkzeug codebase:
    .. versionchanged:: 2.2
        Set the ``default_mimetype`` to None to prevent a mimetype being
        assumed if missing.

and:
    default_mimetype = None
    # Don't assume a mimetype, instead use whatever the response provides

That is exactly what I want to achieve here.


Get rid of EXT_HOST_CREATION_DELAY hacks in terminal

This could be avoided by more messages between ext host and main

I've added the label bug because this manifests as a bug from the point of view of extensions which fail to work...

I reverted this as our builds are failing (integration tests):

revert: https://github.com/microsoft/vscode/commit/33cc09da7a314ea0ee5677d1927739af60d16734
failures: https://monacotools.visualstudio.com/DefaultCollection/Monaco/_build/results?buildId=60622&view=logs&j=2d2b3007-3c5c-5840-9bb0-2b1ea49925f3&t=e5339641-12bd-5520-314f-0b8fa6bdcd9f&l=919

This was fixed some time ago


Update api to use jsonapi format

Coverage increased (+0.07%) to 99.37% when pulling 0a6c6d5d37cee3bd9a852d133234e6e618601f5c on jsonapi-format into d5af21a17f38fb83a41398461673d7cc30d1db79 on master.


Mettre en place le mock de datas

Analyser les technos utilisable et une fois la meilleure approche trouvée, réaliser des POCs
Quelques pistes:

Mongobee + profiles
mongodump et copie dans l'image docker (au moment du build)

@martinez-guillaume do you done this task pls?

Yes, I think it's good now. Wait for Fodil's approval

@martinez-guillaume I updated your PR with changes to do, here is the message:
Can you use the profiles, so that it's run only when we use a specific profile, like "dev"
You can do that by following this
You have to create the profile in pom.xml (see section 4.6) and basically just add @Profile("dev") in the class you created.
And if you want to do even better, try to have real names/information.
To do that, you have to use this
This is going to be fun !!

Done, you populate data by activating the profile 'populate'
Thanks @martinez-guillaume

I just saw your message now. I will take care of it right away.

I just saw your message now. I will take care of it right away.

Noo it works like that, no change needed !! 😋

Cool , it's OK.


Terminal crash with code 1

VSCode Version: Code 1.4.0 (6276dcb0ae497766056b4c09ea75be1d76a8b679, 2016-08-04T16:45:31.680Z)
OS Version: Windows_NT ia32 6.3.9600

Steps to Reproduce:

@Kran001 Can you please provide the steps needed to reproduce this crash?

Im just click Focus new terminal, and my VS code give me error with code 1.
I have been doing it with admin privileges, and none. Results was equals.
2016-08-25 13:39 GMT+03:00 Sandeep Somavarapu<EMAIL_ADDRESS>
@Kran001 https://github.com/Kran001 Can you please provide the steps
needed to reproduce this crash?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/10920#issuecomment-242345358,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHZzEK3GgSmFRZEmLuxzd9PuPu04rftsks5qjXDUgaJpZM4Jsidb
.

@Kran001 Can you let us know if you have any special terminal settings?

At begin, i have not special terminal settings, this error have been. I
restart my PC, and reinstall code editor, but don't be better. I change
terminal settings to Git-Bash terminal, VS Code have not reacting.
I have special settings just snippets.
2016-08-25 16:42 GMT+03:00 Sandeep Somavarapu<EMAIL_ADDRESS>
@Kran001 https://github.com/Kran001 Can you let us know if you have any
special terminal settings?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/10920#issuecomment-242390484,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHZzEIeKhRsJhGLX0EgShNDe9Efsat_Kks5qjZvUgaJpZM4Jsidb
.

Please, try to fix that. i very like this editor, and i want to use him
everyday, and when i was on linux i have been doing it. I can't to do this
now.
2016-08-25 23:09 GMT+03:00 Александр Кран<EMAIL_ADDRESS>
At begin, i have not special terminal settings, this error have been. I
restart my PC, and reinstall code editor, but don't be better. I change
terminal settings to Git-Bash terminal, VS Code have not reacting.
I have special settings just snippets.
2016-08-25 16:42 GMT+03:00 Sandeep Somavarapu<EMAIL_ADDRESS>
@Kran001 https://github.com/Kran001 Can you let us know if you have
any special terminal settings?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/10920#issuecomment-242390484,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHZzEIeKhRsJhGLX0EgShNDe9Efsat_Kks5qjZvUgaJpZM4Jsidb
.

@Tyriar Are you aware of any such terminal crashes?

This is common when the path is incorrect to your shell. Make sure the path to git bash is correct, there are some instructions here to help https://code.visualstudio.com/docs/editor/integrated-terminal#_configuration


Where is the models module?

The module models doesn't seem to be in the project, which causes posetrack18_helper.py to crash:
File "PoseWarper/tools/train.py", line 37, in <module>
    import models
ModuleNotFoundError: No module named 'models'

The "models" module is one of the directories provided with the repo. I believe that you might have missed one of the installation steps, and therefore your paths are not set properly. Please follow the instructions carefully, and I think this issue should be resolved.

You're right. I made a custom folder called models, and added it to .gitignore. This also affected the models folder in lib.


Refactor e2e testing

Description

moved current e2e tests-components to a new directory
add to angular config to e2e/e2e-app/mitosis.config.cjs with importMapper
add cpy-cli to e2e/e2e-angular/package.json
removed fast-glob and sync-directory from e2e/e2e-angular/package.json
update Angular version to 15 to work with newer typescript version

@samijaber, this is still open, would be great if you find some time to comment the PR 😅


The sent tokenizer deletes end of line characters

I am not sure whether this is a feature/bug, but the standard nltk.sent_tokenize() deletes characters from the text.
For instance:
s
'In the beginning, God created the heavens and the earth. And the earth was without form, and void; and darkness was upon the face of the deep. And the Spirit of God moved upon the face of the waters.'
from nltk import sent_tokenize
sents = sent_tokenize(s)
sents
['In the beginning, God created the heavens and the earth.',
 'And the earth was without form, and void; and darkness was upon the face of the deep.',
 'And the Spirit of God moved upon the face of the waters.']
len(''.join(sents))
197
len(s)
199

Is there a way to make sure the tokenizer does not delete characters?

As far as I know, all the tokenizers currently delete intervening
whitespace.
On 20 September 2016 at 19:56, J. de Joode<EMAIL_ADDRESS>wrote:

I am not sure whether this is a feature/bug, but the standard
nltk.sent_tokenize() deletes characters from the text.
For instance:
s
'In the beginning, God created the heavens and the earth. And the earth was without form, and void; and darkness was upon the face of the deep. And the Spirit of God moved upon the face of the waters.'
from nltk import sent_tokenize
sents = sent_tokenize(s)
sents
['In the beginning, God created the heavens and the earth.',
'And the earth was without form, and void; and darkness was upon the face of the deep.',
'And the Spirit of God moved upon the face of the waters.']
len(''.join(sents))
197
len(s)
199
Is there a way to make sure the tokenizer does not delete characters?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nltk/nltk/issues/1472, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEz6zzj1j4NIJZ798piwHsyUow7yDY1ks5qr63igaJpZM4KBb9v
.

Yes, that's the expected behaviour.


Rebase 1.18.0 beta.2

/hold
Things:

NewConfigObserver method of pkg/operator/configobservation/configobservercontroller/observe_config_controller.go is not used anywhere. Should we remove it or call it?

Feel free to remove NewConfigObserver. I think that is left over from when I was just starting to work on this and wasn't sure the direction to take. All we really use is the target config reconciler for now (I believe)

@ingvagabund is this still wip or ready to go soon?

@damemi ready!!!
$ oc logs -n openshift-kube-descheduler-operator cluster-597cfb8f6b-qmz2c
I0327 16:01:38.239925       1 reflector.go:153] Starting reflector *v1.Node (1h0m0s) from sigs.k8s.io/descheduler/pkg/descheduler/node/node.go:84
I0327 16:01:38.240081       1 reflector.go:188] Listing and watching *v1.Node from sigs.k8s.io/descheduler/pkg/descheduler/node/node.go:84
I0327 16:01:38.339624       1 duplicates.go:49] Processing node: "ip-10-0-157-41.us-east-2.compute.internal"
I0327 16:01:38.444505       1 duplicates.go:49] Processing node: "ip-10-0-161-52.us-east-2.compute.internal"
I0327 16:01:38.545213       1 duplicates.go:49] Processing node: "ip-10-0-174-170.us-east-2.compute.internal"
I0327 16:01:38.643233       1 duplicates.go:49] Processing node: "ip-10-0-131-83.us-east-2.compute.internal"
I0327 16:01:38.768217       1 duplicates.go:49] Processing node: "ip-10-0-140-224.us-east-2.compute.internal"
I0327 16:01:38.860924       1 duplicates.go:49] Processing node: "ip-10-0-146-132.us-east-2.compute.internal"
I0327 16:01:39.357569       1 lownodeutilization.go:145] Node "ip-10-0-140-224.us-east-2.compute.internal" is over utilized with usage: api.ResourceThresholds{"cpu":80.13333333333334, "memory":36.618721049786416, "pods":4.8}
I0327 16:01:39.357616       1 lownodeutilization.go:150] allPods:12, nonRemovablePods:12, bePods:0, bPods:0, gPods:0
I0327 16:01:39.357732       1 lownodeutilization.go:145] Node "ip-10-0-146-132.us-east-2.compute.internal" is over utilized with usage: api.ResourceThresholds{"cpu":85.46666666666667, "memory":44.05371887686421, "pods":7.6}
I0327 16:01:39.357761       1 lownodeutilization.go:150] allPods:19, nonRemovablePods:14, bePods:1, bPods:4, gPods:0
I0327 16:01:39.357932       1 lownodeutilization.go:145] Node "ip-10-0-157-41.us-east-2.compute.internal" is over utilized with usage: api.ResourceThresholds{"cpu":48.628571428571426, "memory":28.83790522680958, "pods":11.2}
I0327 16:01:39.357958       1 lownodeutilization.go:150] allPods:28, nonRemovablePods:27, bePods:0, bPods:1, gPods:0
I0327 16:01:39.358136       1 lownodeutilization.go:145] Node "ip-10-0-161-52.us-east-2.compute.internal" is over utilized with usage: api.ResourceThresholds{"cpu":52.05714285714286, "memory":33.10105217442801, "pods":14.8}
I0327 16:01:39.358159       1 lownodeutilization.go:150] allPods:37, nonRemovablePods:37, bePods:0, bPods:0, gPods:0
I0327 16:01:39.358232       1 lownodeutilization.go:145] Node "ip-10-0-174-170.us-east-2.compute.internal" is over utilized with usage: api.ResourceThresholds{"cpu":93.46666666666667, "memory":41.44871220046829, "pods":5.2}
I0327 16:01:39.358257       1 lownodeutilization.go:150] allPods:13, nonRemovablePods:13, bePods:0, bPods:0, gPods:0
I0327 16:01:39.358408       1 lownodeutilization.go:145] Node "ip-10-0-131-83.us-east-2.compute.internal" is over utilized with usage: api.ResourceThresholds{"cpu":51.48571428571429, "memory":28.837890629943065, "pods":12.8}
I0327 16:01:39.358431       1 lownodeutilization.go:150] allPods:32, nonRemovablePods:31, bePods:0, bPods:1, gPods:0
I0327 16:01:39.358441       1 lownodeutilization.go:66] Criteria for a node under utilization: CPU: 10, Mem: 20, Pods: 30
I0327 16:01:39.358452       1 lownodeutilization.go:70] No node is underutilized, nothing to do here, you might tune your thresholds further

$ oc get pods -n openshift-kube-descheduler-operator
NAME                                    READY   STATUS    RESTARTS   AGE
cluster-597cfb8f6b-qmz2c                1/1     Running   0          4m11s
descheduler-operator-77dfc57685-tt5lx   1/1     Running   0          4m24s

$ oc get pods -n openshift-kube-descheduler-operator descheduler-operator-77dfc57685-tt5lx -o yaml
apiVersion: v1
kind: Pod
metadata:
  annotations:
    k8s.v1.cni.cncf.io/networks-status: |-
      [{
          "name": "openshift-sdn",
          "interface": "eth0",
          "ips": [
              "<IP_ADDRESS>"
          ],
          "dns": {},
          "default-route": [
              "<IP_ADDRESS>"
          ]
      }]
    openshift.io/scc: restricted
  creationTimestamp: "2020-03-27T16:01:02Z"
  generateName: descheduler-operator-77dfc57685-
  labels:
    name: descheduler-operator
    pod-template-hash: 77dfc57685
  name: descheduler-operator-77dfc57685-tt5lx
  namespace: openshift-kube-descheduler-operator
  ownerReferences:
  - apiVersion: apps/v1
    blockOwnerDeletion: true
    controller: true
    kind: ReplicaSet
    name: descheduler-operator-77dfc57685
    uid: 14d1e72f-0cf3-46d9-a5fc-17bde8268375
  resourceVersion: "65874"
  selfLink: /api/v1/namespaces/openshift-kube-descheduler-operator/pods/descheduler-operator-77dfc57685-tt5lx
  uid: e96530f7-3e71-4226-81dc-73e025e89c96
spec:
  containers:
  - args:
    - operator
    command:
    - cluster-kube-descheduler-operator
    env:
    - name: WATCH_NAMESPACE
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: metadata.namespace
    - name: OPERATOR_NAME
      value: descheduler-operator
    image: quay.io/jchaloup/cluster-kube-descheduler-operator:20200327-fixgoroutine
    imagePullPolicy: Always
    name: descheduler-operator
    ports:
    - containerPort: 60000
      name: metrics
      protocol: TCP
    resources: {}
    securityContext:
      capabilities:
        drop:
        - KILL
        - MKNOD
        - SETGID
        - SETUID
      runAsUser:<PHONE_NUMBER>
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: openshift-descheduler-token-6t9xl
      readOnly: true
  dnsPolicy: ClusterFirst
  enableServiceLinks: true
  imagePullSecrets:
  - name: openshift-descheduler-dockercfg-8wznj
  nodeName: ip-10-0-146-132.us-east-2.compute.internal
  priority: 0
  restartPolicy: Always
  schedulerName: default-scheduler
  securityContext:
    fsGroup:<PHONE_NUMBER>
    seLinuxOptions:
      level: s0:c23,c22
  serviceAccount: openshift-descheduler
  serviceAccountName: openshift-descheduler
  terminationGracePeriodSeconds: 30
  tolerations:
  - effect: NoExecute
    key: node.kubernetes.io/not-ready
    operator: Exists
    tolerationSeconds: 300
  - effect: NoExecute
    key: node.kubernetes.io/unreachable
    operator: Exists
    tolerationSeconds: 300
  volumes:
  - name: openshift-descheduler-token-6t9xl
    secret:
      defaultMode: 420
      secretName: openshift-descheduler-token-6t9xl
status:
   ...

/hold cancel

/lgtm
Thanks @ingvagabund for getting this together. Do you want to follow up with a small bump to v0.18.0 GA tag?

/bugzilla refresh


Example Usage of PaymentTxn in "Your First Transaction" is Outdated

Describe the error
The constructor of the class algosdk.transaction.PaymentTxn now take transaction parameters directly rather than with a wrapper. So the line
unsigned_txn = PaymentTxn(my_address, params, receiver, 1000000, None, note)

is not working.
Link to the page or line
https://developer.algorand.org/docs/build-apps/hello_world/
Optional - The recommended fix if you have one
The line can be changed to
unsigned_txn = transaction.PaymentTxn(
    sender=my_address,
    fee=params.fee,
    first=params.first,
    last=params.last,
    gh=params.gh,
    receiver=receiver,
    amt=1000000,
    note=note)

These examples have been update to v2 now and this issue should now be resolved. Thank you!


Added deviceId parameter to the scene - it will set what camera to us…

…e based on its deviceId

What kind of change does this PR introduce?

This is a new feature - allows to define the deviceId to use for the camera.
** Can it be referenced to an Issue? If so what is the issue # ?**
Might be useful for this issue : #178
How can we test it?

You can use this feature by defining the deviceid as a parameter in the scene, like this :
 <a-scene embedded arjs="detectionMode: mono_and_matrix; matrixCodeType: 3x3; sourceType: webcam; trackingMethod: best; debugUIEnabled: false; deviceId: 10d9f755ccab290ef5dbd4a1bb27cca11e61677ab0b4356f302e098ef6144813;" antialias="true">
In order to get the deviceId, you can use getUserMedia.
Summary

Does this PR introduce a breaking change?
It doesn't. The previous behaviour to select what camera to pick up is the default one. The deviceId parameter is optional.
Other information

looks good to me. anybody can test it ?

I tested this.
It did not seem to work in either the Chrome browser or the Edge browser.
I added a GET variable to the URL with the name "deviceId". I set the value to the deviceId of a camera connected to the computer.
AR.js still opened with the default camera.
Perhaps more instructions should be added on how to use this feature.

I just noticed that the code sample on how to test it got hidden (forgot to put it between code markdown) ! You need to provide the deviceId in the scene tag, like this :
<a-scene embedded arjs="detectionMode: mono_and_matrix; matrixCodeType: 3x3; sourceType: webcam; trackingMethod: best; debugUIEnabled: false; deviceId: 10d9f755ccab290ef5dbd4a1bb27cca11e61677ab0b4356f302e098ef6144813;" antialias="true">

I tested this with the added instructions and I confirmed that this change works as described.


Project setup

What?
Pull request to set up the project's configuration.
Before merging
The following things are to be added before merging:

[x] Linters configuration
[x] Webpack configuration
[x] Jest configuration
[x] First README draft

Status: Approved :heavy_check_mark:
Hi, @notlfish
This Pull is complete! Great job and thank a lot you for cover me today, I just added the folder for tests, mocks, modules and fix the linters. There is nothing else to say other than... it's time to merge it :champagne:  :champagne:  :champagne:


isMobile always false, name is null

Device: iPhone 7 Plus
Flutter: 2.10.5
builder: (context, myWidget) {
        myWidget = DevicePreview.appBuilder(context, myWidget);
        myWidget = ResponsiveWrapper.builder(
          BouncingScrollWrapper.builder(context, myWidget),
          maxWidth: 1200,
          minWidth: 450,
          defaultScale: true,
          breakpoints: [
            const ResponsiveBreakpoint.resize(450, name: MOBILE),
            const ResponsiveBreakpoint.autoScale(800,
                name: MOBILE, scaleFactor: 1.1),
            const ResponsiveBreakpoint.autoScale(1000,
                name: TABLET, scaleFactor: 1.35),
            const ResponsiveBreakpoint.resize(1200, name: DESKTOP),
            // const ResponsiveBreakpoint.autoScale(2460, name: "4K"),
          ],
        );
        return myWidget;
      }

  I called "ResponsiveWrapper.of(context).activeBreakpoint"

returned

"

You might have caught an edge case here.
Looks like if a breakpoint is set to minWidth, then the minWidth overrides the breakpoint name?

I have no idea. How can i solve this problem and should how should I set it up?


Mac: Unable to launch the game

On Mac, the App cannot be launched. (v1.0.6) The permissions set for the executable inside the app are not correctly set.
I found this workaround: https://itch.io/post/5924204
The workaround, here as a snippet to copy - you can execute this inside the extracted archive in your terminal to make the game start.
$ chmod +x Geographical\ Adventures.app/Contents/MacOS/Geographical\ Adventures

this fixed my issue

Yeah I know it happens a lot with Unity games.

Where I have to manually fix them

Like I think superlininal just wouldn’t work but then I gave x attributes to it. And it worked!


Forms in v8 - seem to not honor col-x, block vs inline

Hi - thank you for what must have been an enormous amount of work on v8. I'm trying to upgrade.
In the previous docs, it mentioned using col-n to specify width of form fields, but in v8, this no longer seems to work.
<input type="email" name="emailAddress" class="col-4 email-octopus-email-address field rounded-left x-group-item" placeholder="Your Email Address">

Changing field to input works to get some formatting on the field, but, the col-4 no longer works, & the field just spreads out across the page.
In addition, even though I am loading the v7 optional ui-groups css, the x-group-item does not seem to actually group the components.
Is this expected? Do I need to set width simply using, say, inline styles. Also, should the x-group-item still work if I have those styles loaded, e.g:
/* Basscss UI Utility Groups */

.x-group-item { margin-left: -var(--border-width) }
.x-group-item:first-of-type { margin-left: 0 }

.y-group-item { margin-top: -var(--border-width) }
.y-group-item:first-of-type { margin-top: 0 }

.x-group-item:focus,
.y-group-item:focus {
  position: relative;
  z-index: 1;
}

Please advise, thanks!

Another thing I noticed about forms is, the default basscss-forms in vs has them styled as block elements. If I use my v7 markup as is, with v8, it leads to:
Label
[input text field]
[submit]

... but what I want is to have them inlined:
Label [input] [submit]

This worked by default before, but something changed. I tried a number of things like adding the utility classes inline, inline-block and so on, on the various parts of the form and its surrounding divs, but I cannot seem to get it to stop being in block mode. Appreciate any advice here. This is where I'm working on it:

		Footer links, Social icons, Copyright etc

				<form method="post" action="https://emailoctopus.com/lists/11111111-2222-3333-4444-5555555/members/external-add" class="email-octopus-form clearfix inline-block m1">
					Get Email Updates:
					<input type="email" name="emailAddress" class="email-octopus-email-address input bg-teal bg-lighten-1 rounded-left x-group-item" placeholder="Your Email Address">
					<button type="submit" class="btn btn-primary bg-lighten-2 rounded-right x-group-item">Subscribe</button>

						Protecting against bot signups - leave this field blank
						<input type="text" name="hp64dbf442-b268-11e5-b4ea-0a4287b2e8c5" autocomplete="off">

				</form>

Ok, I feel really dull. I aded that col-4 back after restarting my npm start, and it works again. No idea why that would have not been taking hold, but, adding the col-4 back where it was, definitely controls the width of the input text field.

I'm guessing that might've been a source order issue. Let me know if you're still having problems.

Thanks @jxnblk. The x-group-item definitely does not seem to work like it used to, though. Previously it kind of neatly pulled the form elements together, but now they stay separate. I am ignoring it for now, but it would be nice if this would work.


Background + offline incoherences

What
Assuming that I use the app offline and that I change a product 5 times in a row (changes A, B, C, D and E), there are 5 background processes pending, all on the same product.
When I go online, I may have problems.
Problem 1: if each process is executed atomically in a queue, after I run processes about A and B, I'll get the server product with changes A and B, but not yet C, D and E. The product is less complete than when I was offline with all my changes.
Solution 1: merge all changes about the same product into a single background process before executing it.
Problem 2: if I try to refresh the product before the background processes are executed, I'll get a fresh product from the server but without my local changes.
Solution 2: we should not be able to refresh a product when there are pending background processes. In addition to that, we could add an icon "local changes pending" and an error message "cannot refresh product while there are local changes pending".
Problem 3, related to problem 1 (spoiler alert: bad luck problem): if while the merged background processes are executed I change the product (change "F"), after the execution I get a fresh server product with all my initial changes (A-E), but change F will be ignored, until background process about F is executed.
Solution 3: each time we get product data from the server, we have to apply the pending changes before storing it locally.
The more I think about it, the more I believe that solution 3 would solve everything (we wouldn't need solutions 1 and 2).
@AshAman999 Do you share my views?

This sounds similar to performing commits on git.

Maybe, I don't understand that much about git - and I don't intend to.

what if we handle this like priority queue?
All local changes are prioritized over server retrieval.

Sounds correct, except that we need a decent UX for that - like the "cannot refresh product while there are local changes pending" message I was mentioning before.

if new change is submitted during execution of local changes, it will be added for execution before server retrieval.

How do you do that? For the moment, the background process execution is first the "upload changes" (async), and then the "download product" (which is async too).
And in the meanwhile - after the first execution and before the second one - how is the product?

if server retrieval is in execution, local changes will be executed afterwards and server will be re-fetched? (not sure about this)

That's more or less my "solution 3".

Problem 1: if each process is executed atomically in a queue, after I run processes about A and B, I'll get the server product with changes A and B, but not yet C, D and E. The product is less complete than when I was offline with all my changes.

Solution 1: merge all changes about the same product into a single background process before executing it.

There was something similar in my mind to do
I believe that a mix of sol 1 and sol 3 would work the best,

we check for the list of pending background processes, we merge the changes for a product, (would be better to have less API calls), and show an error snack bar too, if background task fails.
Something similar to what google keep having, show a sync icon in the product card, if the background sync process is in process of change, would be visually confirmation for the same
For product card, we should use a consumer i.e. provider so that the UI is rebuilt fully in case of changes in the product

How do you do that? For the moment, the background process execution is first the "upload changes" (async), and then the "download product" (which is async too).
And in the meanwhile - after the first execution and before the second one - how is the product?

upload changes => download product

when new local change is added, it's pushed to execute before 'download product'

upload changes => new_local_changes => download product
if download is in progress, we can either stop it and perform upload of new_local_changes first
or we can wait for download to complete then perform the flow of upload and download again?

We need to update the local changes instantly. Then queue a background process that uploads, then downloads, then stores locally.
Therefore I'm not sure what you suggest (upload then local changes) would work.

if download is in progress, we can either stop it

I don't think we can stop an async, can we?
Sharing views on that issue, I think we should just ignore whatever user data refresh (pull-to-refresh, search) from the server while there are pending tasks in general.
A possible nice-to-have would be to do that at the product level (user can't refresh a product while there are pending processes on that product), but that may be confusing for the user (if we refresh a whole search, most products will be fully refreshed while some "pending" products should not be).

I just want a solution that works - possibly bullet proof. Solution 1 so far looks like a "nice to have" and won't solve the main issue. Which means we can forget it. When all the major bugs are solved, then we can think about it again.
We won't show an error snack bar from a background process. Or with difficulties.
I don't think we need a provider, we just need a notifier. Like LocalDatabase.
I don't know google keep.

Therefore I'm not sure what you suggest (upload then local changes) would work

If somehow upload fails, then we'll need to revert back local changes?

I don't think we can stop an async, can we?

yeah, this can be used CancelableOperation

Sharing views on that issue, I think we should just ignore whatever user data refresh (pull-to-refresh, search) from the server while there are pending tasks in general.

Yeah, can add an indicator on top to let user know that they can't refresh due to background tasks

If somehow upload fails, then we'll need to revert back local changes?

That's a good point: I have no idea what we are supposed to do if upload fails.

yeah, this can be used CancelableOperation

Yes and no: the server will still process the data, it's just that the returned value on flutter will be irrelevant, right?

Yeah, can add an indicator on top to let user know that they can't refresh due to background tasks

Not that easy, as the retry process of background tasks sometimes waits 3 hours before launching again.

@teolemon @AshAman999 @anshpathania7 So if I had to sum up today's brainstorming, we are currently stuck with this question:
<< What are we supposed to do when a background "update product" process fails? >>

retry 5 times, first after 30 seconds, then after 5 mins, then 30 mins, then an hour, then 3 (current implementation)
=> that only delays the answer to the point when it failed 5 times (possibly because the server is down or the internet connection is poor) (and if the connection is poor it may mean that the server did process the change but was no able to return a success code)
try forever (how often?)
roll back locally the related changes (how do we warn the user?)

@monsieurtanuki

Yes and no: the server will still process the data, it's just that the returned value on flutter will be irrelevant, right?

Yes, it will only cancel async tasks on flutter side, irrespective of Api.
Instead of cancelling we can just let it execute, also are we storing state of these operations every second?
So in case of forced shut down of application we can refer the state saved locally?
This might also be helpful in knowing which tasks were failed so we can revert local changes for it

Not that easy, as the retry process of background tasks

if 5 retry methods fail,
how about adding a periodic upload at some fixed time daily (like 12 am)? To clear up pending tasks?
Or
we can stack up all tasks to execute in slots, like having 4 slots of 6 hours interval,
And at  each interval, we execute the current queue.
post execution queue is cleared, so it can be used in next time slot

We cannot use slots: we want the data to be uploaded to the server as soon as internet is available.
So that beyond the actual user changes, everyone (including the user) benefits from the impact of the changes (e.g. "ecoscore" computed on the server side after the user added a category to a product and uploaded the change) (and then downloaded its change + the new ecoscore).

what if slots are only used for failed upload tasks? (which were failed even after 5 retries)

In those cases I always ask myself: how do other apps do?
It looks like Evernote does it that way:

automatic upload of the note if online
explicit "not uploaded yet" icon
"sync" button
manual conflict management in some helpless cases

Which inspires me several things:

whatever we should do should be on the product level (for instance not a queue for all individual changes, but a queue of changed products)
we should make explicit that this product still needs to be sync'ed, and show a "sync/upload" button
every time we refresh a product (e.g. pull to refresh) we should upload it first (if relevant)

whatever we should do should be on the product level (for instance not a queue for all individual changes, but a queue of changed products)

Sounds good to me, so in queue of changed products, each product will have all changes to that specific product?
(Like queue of Product Object, where Object holds all changes to that product) ?

we should make explicit that this product still needs to be sync'ed, and show a "sync/upload" button

Yes, adding this globally would be better, like showing it on top of every screen

every time we refresh a product (e.g. pull to refresh) we should upload it first (if relevant)

Or we can explicitly mention to sync local changes first then refresh

@anshpathania7 I'm not sure exactly if we can do that currently, so let's check first!
@AshAman999 @g123k If I've understood well, for the moment there's a queue of background tasks, handled by the task manager. That sounds cool, we just add tasks and let the manager manage.
Unfortunately it looks like we need to be a bit intrusive with the task manager data, as we need to know from outside of the manager:

the list of related barcodes pending
the actual action of each task
with the option of merging all the tasks related to a barcode into a single task

Is that doable with the current task manager?

I think I've found a solution in order to merge all the tasks related to a product.
Today, when we add a task we say something like "for barcode 0123, change category to XXX".
Which means there's a new entry in the task queue, with a key like 0123_CATEGORY and a value like category: XXX.
If later the category is changed again, it will use the same task key 0123_CATEGORY. Or something like that.
What if instead of adding this task in the task manager, we created a dedicated sqflite table that would contain the same changes, and we just add to the task manager a simple task like 0123_CHANGE (no other parameter).
How would the task manager execute task 0123_CHANGE? We list all the changes recorded in our new table, merge them, execute them as one, and clean the new table about barcode 0123.
Et voilà.

Hello @monsieurtanuki,
The solution you are suggesting does looks promising,
About other things here, like what could be easily done, with the task_manager package
Ahh about the things related to the package task_manager,
We can request details about what was given to the Task object when we scheduled the task,
So at any instant, if a task is not running I can get a list of those tasks from the task manager,
Also, we can cancel those tasks with their unique id,
What we can do is,

Before queuing a task, look if, in pending tasks, there is a key that contains the same barcode as this one
if it is we gather the object from there,
We extract the product from that Taskobject
cancel that task,
merge the change we want now with the last one,
and then ask the task_manager to perform the new task

I am not sure about which way to go, perhaps I can work on the one I am suggesting, and see if works,
Though your approach seems faster and more efficient ...

@AshAman999 I guess your algorithm makes sense.
That said, the added value of the task manager is to queue tasks and run them when the internet connection is OK. It's supposed to be a black box that does that very well. As we have functional needs that go beyond the standard use of the task manager, we should keep the functional features in smoothie (including the task merge) and the task queuing in task manager. Of course we could do everything with task manager if our needs were simpler, like "for a barcode, execute only the latest task". To be discussed.
Anyway, it's not the priority now: I just mentioned our requirements to double-check that in the end, we'll have something that works in all cases.
The priority now is to get rid of Consumer<UpToDateProductProvider>, that prevents us from notifying the app. The only low level notifier we have is LocalDatabase, and that's where (or in DaoProduct) we should move UpToDateProductProvider's code to.
With that, we'll be able to notify the app every time a background task is finished, which we cannot do now.
Actually I've spent one hour on it so far. If you want to do it, tell me and I'll scrap my one-hour changes.

Actually I've spent one hour on it so far. If you want to do it, tell me and I'll scrap my one-hour changes.

I have done none for now, first I guess if we could refresh views after the background task is done, would be a good start
Then we could do about the consideration of merging changes into one.

@AshAman999 OK, I go on with my changes then. I'll keep you posted.

The priority now is to get rid of Consumer, that prevents us from notifying the app

@monsieurtanuki How is this preventing notifying the app? Like what's the expected behaviour?

@anshpathania7 In short, from the background tasks we have access only to LocalDatabase, and we need to notify somehow when a task is finished.

@monsieurtanuki This can be easily fixed with a global context I believe, as both LocalDatabase and UptoDateProduct Providers are defined on top level.

@anshpathania7 You may be right, but it's not at all the root of our problems. The whole thing is being rethought, with or without UpToDateProductProvider.

Given that #3059 is too complex to be reviewed with serenity, we have to do things differently here.
I'll keep committing to this PR in order to get a full single PR, but when I'm done with it I'll split it in smaller individual PRs, easier to review.
Meanwhile, I would like to explain what we're talking about:

some widgets are based on a product (e.g. the product page)
they need to be refreshed every time the product is downloaded or changed anywhere in the app
for that, we use the provider/notify feature
in addition to the initial product we used when we called the widget, we need to take into consideration the downloads and the changes that happened afterwards
the changes are done in two steps

we add the change to a stack, to be applied immediately via notification to all related widgets (when possible: we can do that for detail change, we cannot do that for image upload)
we create a background task, that will eventually be executed and followed by a download of the latest version of the product

for that, we'll need new features, like a sequential unique number generator, and a way to store transient product changes

Related issues:
P0:

#3100

P1:

#3048
#2968

P2:

#2978
#2961

P3:

#1398

Other

#3263
#3249
#3217
#3096
#3043
#2775
#2755
#2454
#2453
#2439
#1533

Thank you @M123-dev!
Aren't we supposed to say "Closes: #xxx" or "Fixes: #xxx"?
It looks like if in the PR comment we just mention an issue, it is going to be closed.

Yeah you are right, don't know why it closes, maybe because of your commit name

@M123-dev It looks like you're right: in #3308's title I didn't put the hash sign for issue 3018, which was not closed after the PR was merged.

Closed by #3329. Now the focus is on #3263.


sqlx macro property rename and rename_all priority

Bug Description
When I use macro like this
#[derive(Debug, FromRow)]
#[sqlx(rename_all = "PascalCase")]
pub struct TrainLogonLogRow {
    #[sqlx(rename = "ID")]
    pub id: Option<String>,
    pub user_id: Option<String>,
    pub user_name: Option<Vec<u8>>,
    pub mobile: Option<String>,
    pub user_type: Option<i32>,
    pub login_mode: Option<i32>,
    pub login_date: Option<NaiveDateTime>,
    pub login_ip: Option<String>,
    pub login_area: Option<String>,
    pub token: Option<String>,
    pub source: Option<String>,
    pub phone_model: Option<String>,
    pub device_model: Option<String>,
    pub phone_version: Option<String>,
    pub screen_pixels: Option<String>,
    pub product_version: Option<String>,
    pub online_status: Option<i32>,
}

expectation is to rename "id" to "ID," but in reality, it is being renamed to "Id." This does not align well with practical use cases. For example, if a table in a database predominantly uses PascalCase for field names, but the "ID" field does not conform to this naming convention, applying rename to a specific field under the global rename_all should take precedence. The priority of this individual field's modification should be higher than global.
the code in sqlx-macros-core\src\derives\row.rs
line 90
let id_s = attributes
                .rename
                .or_else(|| Some(id.to_string().trim_start_matches("r#").to_owned()))
                .map(|s| match container_attributes.rename_all {
                    Some(pattern) => rename_all(&s, pattern),
                    None => s,
                })
                .unwrap();

modify
let id_s = if let Some(s) = attributes.rename {
                s
            } else {
                let s = id.to_string().trim_start_matches("r#").to_owned();
                match container_attributes.rename_all {
                    Some(pattern) => rename_all(&s, pattern),
                    None => s
                }
            };

Hi, is there any update on this issue?

We'd gladly accept a PR. Looks like OP already found where the change needs to be made.


Prolog interpreted as Perl

.pl files containing prolog code are being classified as Perl.

Currently, the package is only able to match icons based on filename.
Once v2 drops, you'll be better able to customise icons on a per-language basis, rather than a per-filename basis. We're just waiting on Atom v1.11 before we can start testing publicly.


SRCH-5548 filtering by path

Summary

Goal here is to add ability to filter links we find by the url path.  I accomplished this by extending the built in offsite middleware which in addition to the domain checking adds this ability.  There are some examples in the JIRA story but simply if an allowed_domains value contains a path, e.g. quotes.toscrape.com/tag/ the the spider will only output links from that domain that contain the path tag.
Changes of Note:

New middleware to accomplish the filtering as well as enabling the middleware in settings.
Updates the helper methods to allow for creation of new argument to spider to contain domains with paths separate from just the domains.  This helped to ensure that we didnt mess with the exsting domain limiting functionality.
Moved parse_item back to the spiders to help with using built in scrapy CLI tools to test and debug.
Updated plist conversion script with filters and addition of paths where appropriate.
Removed three entries from crawl list and added path filters per Jim's instructions
Updated init schedule sql (will clean up during init automation story).
Updated tests and httpcache for tests
Added additional tests where needed.

Testing:

Try things for yourself.  For example, compare output of the following two scrape commands:

scrapy crawl domain_spider -a allowed_domains=quotes.toscrape.com -a start_urls=https://quotes.toscrape.com
scrapy crawl domain_spider -a allowed_domains=quotes.toscrape.com/tag/ -a start_urls=https://quotes.toscrape.com

Try with scrapyd

scrapyd-deploy local -p search_gov_spiders
curl http://localhost:6800/schedule.json -d project=search_gov_spiders -d spider=domain_spider -d allowed_domains=quotes.toscrape.com/tag/ -d start_urls=https://quotes.toscrape.com

Checklist
Please ensure you have addressed all concerns below before marking a PR "ready for review" or before requesting a re-review. If you cannot complete an item below, replace the checkbox with the ⚠ :warning: emoji and explain why the step was not completed.
Functionality Checks

[X] You have merged the latest changes from the target branch (usually main) into your branch.

[X] Your primary commit message is of the format SRCH-#### <description> matching the associated Jira ticket.

[X] PR title is either of the format SRCH-#### <description> matching the associated Jira ticket (i.e. "SRCH-123 implement feature X"), or Release - SRCH-####, SRCH-####, SRCH-#### matching the Jira ticket numbers in the release.

[X] Automated checks pass. If Code Climate checks do not pass, explain reason for failures:

Process Checks

[X] You have specified at least one "Reviewer".

I am able to test it correctly using scrapyd. When I try to just run the scrape commands though it's not writing the output to a csv file even though it says
{"asctime": "2024-10-07 14:12:46,476", "name": "scrapy.extensions.feedexport", "levelname": "INFO", "message": "Stored csv feed (120 items) in: scrapy_urls/domain_spider/domain_spider_2024-10-07T18-12-40+00-00.txt", "spider": "domain_spider"}
I can see based on the console messages though it's returning the right number of items (120 for /tag and 378 for the entire domain). Is the not writing to a file intended now?

intended now?

it should still write to the CSV... ill take a look.

I am able to test it correctly using scrapyd. When I try to just run the scrape commands though it's not writing the output to a csv file even though it says
{"asctime": "2024-10-07 14:12:46,476", "name": "scrapy.extensions.feedexport", "levelname": "INFO", "message": "Stored csv feed (120 items) in: scrapy_urls/domain_spider/domain_spider_2024-10-07T18-12-40+00-00.txt", "spider": "domain_spider"}
I can see based on the console messages though it's returning the right number of items (120 for /tag and 378 for the entire domain). Is the not writing to a file intended now?

Seems to work for me... is this what you are doing?
(.venv) ➜  search_gov_spiders git:(SRCH-5548_filtering_by_path) pwd
/Users/dself/Projects/searchgov-spider/search_gov_crawler/search_gov_spiders
(.venv) ➜  search_gov_spiders git:(SRCH-5548_filtering_by_path) ls -la ../output
total 8
drwxr-xr-x   3 dself  staff   96 Oct  7 15:17 ./
drwxr-xr-x  23 dself  staff  736 Oct  7 14:51 ../
-rw-r--r--   1 dself  staff   70 Aug 22 09:36 .gitignore
(.venv) ➜  search_gov_spiders git:(SRCH-5548_filtering_by_path) scrapy crawl domain_spider -a allowed_domains=quotes.toscrape.com/tag/ -a start_urls=https://quotes.toscrape.com
... output from run ...
(.venv) ➜  search_gov_spiders git:(SRCH-5548_filtering_by_path) ls -la ../output
total 24
drwxr-xr-x   5 dself  staff   160 Oct  7 15:17 ./
drwxr-xr-x  23 dself  staff   736 Oct  7 14:51 ../
-rw-r--r--   1 dself  staff    70 Aug 22 09:36 .gitignore
-rw-r--r--   1 dself  staff  1948 Oct  7 15:17 all-links.csv
-rw-r--r--   1 dself  staff  3897 Oct  7 15:17 all-links1.csv
(.venv) ➜  search_gov_spiders git:(SRCH-5548_filtering_by_path) wc -l ../output/all-links.csv
      40 ../output/all-links.csv
(.venv) ➜  search_gov_spiders git:(SRCH-5548_filtering_by_path) wc -l ../output/all-links1.csv
      80 ../output/all-links1.csv

Ah okay. I am getting them in the output/all-links{x}.csv but based on the message I was also looking for them in scrapy_urls/domain_spider. I remember we discussed removing them from there but I didn't expect to see that message in the logs.


Add APIs for tumbling window rerun trigger

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-sdk-for-js

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-python

Automation for azure-sdk-for-java

Automation for azure-sdk-for-node

Automation for azure-sdk-for-go

Can one of the admins verify this patch?

Automation for azure-sdk-for-go fails with error "fatal: git fetch-pack: expected ACK/NAK, got '?error: Access denied to IP <IP_ADDRESS>' ". How could I re-run this check?

@AutorestCI regenerate azure-sdk-for-go

@dsgouda it looks like it's a transient error.  I asked the bot to regenerate the PR but it seems to be running slow (I have several other PRs still waiting on Go SDK codegen from the bot).

Looks good. Signing off from ARM side.

@AutorestCI regenerate azure-sdk-for-go


Automation - Credentials re-encrypting

We're using Ansible to automate our Jenkins master, slaves on-demand.  We added credentials to a fresh master, then copied the secrets folder, all keys, the credentials.xml, config.xml files over for every fresh master.   However, when we fire up a new Jenkins node, and go into the credentials, any modification to an existing, or new credential results in all existing passwords, sans the one being modified or added, being re-encrypted, which is just encrypting a previous encryption.
I've compared file by file between a working, and a re-encrypted Jenkins node.  The only difference is the credentials.xml file, all other files (keys) are exactly alike.
What am I missing?

Hi, not really an answer, but how do you produce the password hash out of raw password? I'm about to write Ansible plugin to create credentials as a part of pipeline process, but I can't find the hash generation mechanism in sources...

@ror6ax  Hi,your problem is solved？

please use the Jenkins JIRA for issue tracking


Helm: Add value for deployment annotations

Is there an existing issue for this?

[X] I have searched the existing issues

Feature description
There should be an equivalent to podAnnotations for deployments in the helm chart like annotations or deploymentAnnotations
What would the ideal solution look like to you?
  values:
    annotations:
      sidecar.jaegertracing.io/inject: "XXX"

Anything else?
The k8s jaeger operator does not watch pod annotations only namespace and deployment annotations:
https://www.jaegertracing.io/docs/next-release/operator/#install-modes

This is included in release 0.23.1. We went with deployment.annotations as the value key for defining the annotations for the deployment.


ollama pull llama3 error

What is the issue?
ollama pull llama3
Error: pull model manifest: Get "https://ollama.com/token?nonce=EBGaz66AqKbJTscDMcl-ag&scope=repository%!A(MISSING)library%!F(MISSING)llama3%!A(MISSING)pull&service=ollama.com&ts=1714547177": read tcp <IP_ADDRESS>:49346-><IP_ADDRESS>:443: read: connection reset by peer
Can't I prioritize it? I can't use it locally
OS
macOS
GPU
Intel
CPU
Intel
Ollama version
llama2&llama3

Let's consolidate this as a dup of #3504
(We believe a proxy or firewall is altering the URLs during redirection and causing things not to work properly)


Cube filter fn

Far from ready for prime time, but want to show this as a POC and open discussion as to whether or not we think this is worth while (before we invest anymore time is what might turn out to be a hairy change). Please see toolbox branch of the same name.

Hey -- finally had a chance to look at this.
So I think for starters, we might just create a new Filter class called a "FunctionFilter" if our filter config is actually a filter.
BUT a larger concern I have, however, is with the id generation/parsing code.  It seems like we have a pretty strong understanding that the filters can always be regenerated from a serialized id.....
Do we need to do this?

Yes that concern ( id generation/parsing) is exactly why I decided not to go any further without this discussion. And no it doesn't seem we NEED it. I just thought it was a good idea before I even looked at the code. The motivating use case in the application has been dealt with in a satisfactory manner without this change


Fix windows regressions

Some windows apps broke with the recent .talon -> .py transition.

Thanks for fixing these!


tmux: when switching background color with select-pane -P, color is lost with new lines

Which operating system does the issue occur on?
macOS 10.13.3, with tmux 2.6
steps to reproduce:

open a tmux session
press the tmux prefix key, then :select-pane -P 'bg=red' (at this point the background of the tmux pane should be red)
run a command that has multiple lines of output (e.g. ls -la)

results:
the background color after the newline character of each line is not red but the original background color
expected:
the background color should be applied to the whitespace at the end of the line
This works as expected in iTerm 3.1.5.

I just pulled the latest from the scrollback branch and re-built, re-installed. But I still see the issue. When I first change the background color, the whole background is the new color. But once I start hitting enter or entering a command (e.g. ls -la) the background after the newline character is reset back to the default. In other words, the background of the characters printed are correct but not the remaining whitespace of the line.

Ok that's surprising. I'll look into it. Thanks for the report!

Was this a problem for you on master?

I have a similar problem. On (neo)vim, when scrolling (withing vim), the background color goes to black.

I just switched back to master, pulled, and rebuilt (doing cargo build --release). I still see the issue. Perhaps there is something I'm missing here re: building or perhaps there is something amiss in my configuration?

@mattsawyer77 After rebuilding, are you running the binary dropped into target/release/alacritty?

OK I see the problem now. I was coping the Alacrity.app to my /Applications folder and running it that way. When I invoke alacritty from iTerm via ./target/release/alacritty I do not see the problem in either the master or scrollback branches.


PersistentDateTimeAndZone saves incorrect timestamp if using PostgreSQL type timestamp with time zone

With the following field:
@Basic()
@Type(type = "org.jadira.usertype.dateandtime.joda.PersistentDateTimeAndZone")
@Columns(columns = { @Column(name = "creationtime", nullable = false),
		@Column(name = "creationtimezone", nullable = false) })
private DateTime creationTime = null;

and the column definitions:

creationtime timestamp with time zone, // note: with time zone
creationtime_zone varchar(255)

PersistentDateTimeAndZone saves the DateTime 2015-05-28 14:43:24.209+07:00 incorrectly as:

creationtime: 2015-05-28 12:43:24.209-00:00 (2015-05-28 17:43:24.209+07:00)
creationtime_zone: Asia/Jakarta

While PersistentDateTimeAndZone works fine with timestamp type, it's sometimes preferred to always use timestamp with timezone, therefore in which case PersistentDateTimeAndZone should save it as:

creationtime: 2015-05-28 07:43:24.209-00:00 (2015-05-28 14:43:24.209+07:00)
creationtime_zone: Asia/Jakarta

Tag @ceefour

I think it could be possible to support this via a new usertype. JDBC itself doesn't have built in support for this type, you would need to see if you can map it e.g. via PGObject. Have a look at this (resolved) issue which maps an enumerated type for Postgres in this way #14
If you are interested to work on this, I am happy to assist with integrating it into the library


Links only work once in nav-tabs dropdown menu

http://v4-alpha.getbootstrap.com/components/navs/#javascript-behavior
To reproduce problem:

click Dropdown > @fat

click Dropdown > @mdo

click Dropdown > @fat

Now both links are highlighted in primary color and neither are working.

Duplicate of #17371, and see #21223 as well.


Release new version for into-attr-derive

into-attr-derive is still using dot-generator v0.1.0 on creates.io. A new release will fix this
https://github.com/besok/graphviz-rust/blob/173c98f4e9d9d763c08c0a31abbc512ef56cb137/into-attr-derive/Cargo.toml
Likewise, all the dependent crates need to be updated.

 update ver


[Bug]: Mobile Navigation Bug

Discord Username
Zyruks
Severity Level
Low
Description of the Bug

Modal position need to be updated.
Operating System
Windows
Browser(s)
Firefox
Browser Version(s)
Latest
Relevant Log Output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Done!


Tabs - Changed the Cursor from default to pointer

The Cursor for the Tabs wasn't a pointer yet. So I changed it, like it is in the spectrum-css.
Line 69 has been changed according to this layout https://github.com/adobe/spectrum-css/blob/main/components/tabs/index.css#L79 and line 110 according to this https://github.com/adobe/spectrum-css/blob/main/components/tabs/index.css#L122
✅ Pull Request Checklist:

[ ] Included link to corresponding React Spectrum GitHub Issue.
[ ] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[ ] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

Spectrum CSS is actually incorrect here - may just not have been updated yet. The Spectrum cursor guidelines say that the pointer cursor should be reserved for links. The intent is to better match native browser behavior, the CSS spec, Microsoft interface guidelines and Apple interface guidelines.
See this series of blog posts for more details and history.


Include paas-admin costs in the PMO csv download

What

Include paas-admin costs in the PMO csv download

How to review

deploy to a dev env
go to admin, select 'Spend for PMO team in CSV format', open downloaded csv and check 'admin' is included in the file

Who can review
not @kr8n3r

🚨⚠ Please do not merge this pull request via the GitHub UI ⚠🚨

not required


XCode 'Contents.json' Not Update

When building icons for xcode, we actually also need to update the Contents.json file.
Suggest we:

Move the project to JavaScript as we now have a bit more work.
Add unit tests against an integration test folder.
Generate the Contents.json file programatically.

Resolved in v0.2.1


Change the look "Welcome to EmotiBit"

Description
Change how this  readme looks.
Type of correction

[ ] Documentation structure change
[ ] Documentation update
[ ] Permission Issue(Any page you do not have access to)
[ ] Inaccurate content
[ ] Inappropriate content
[ ] Outdated/Deprecated content

Link

Add Link to the page where the problem exits here

Screenshots

possible resolved when resolving #33


Issue#36 embedding visualisation Jupyter notebook

Adding exploration and visualization works of Louis-db embedding vector space.
embedding-vector-space-visualisation.ipynb : This notebook runs code that generates new 2d representation of embedding.
embedding-vector-space-exploration.ipynb : This notebook contains initial exploratory code used to understand Louis-db vector space and tables. Data folder (first markdown cell) contains details of the data used for this notebook. It also contains clustering, tfidf vectorizer, obtaining topic_depth from Atlas API and more.

@leejaeka
typically we don't merge changes that fail check, but the failing check is unrelated to your code:
https://github.com/ai-cfia/louis-db/issues/34
so you can merge this.


[WIP] Add additional diagnostics

This PR is to solve issue #30
Things to do for this PR:

[x] Fix the current frame diagnostics not updating properly.
[x] Add basic count of loaded shaders to diagnostics.
[ ]  Add basic count of loaded objects in the scene.

Previously the fps counter wasn't updating if the FPS doesn't change, so if you permanently hit the vsync cap it would never update the total frames rendered/avg
The first commit in this PR takes care of this problem by changing the location of the updateFpsCounter call.
The second commit adds a way to trace the amount of shaders loaded into the system.
It is implemented in a push from the RenderingService to the DebugService to make sure that if we load a shader halfway through the runtime it will still be reflected and updated and not force us to update the shaderload text every frame.
This should save some if not a minor amount of processing power but make it responsive and update on the frame the new shader is loaded.

PR is dead. Closing.


Remove Debug Commands

Pull Request
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

#106  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @JackPlowman and the rest of your teammates on  Graphite

Merge activity

Oct 1, 2:49 AM EDT: @JackPlowman merged this pull request with Graphite.


Update the DG: user stories, glossary, NFRs, use cases

Add the following to the DG:
1. Target user profile, value proposition, and user stories
2. Use cases
3. Non-functional requirements
4. Glossary

Close this issue? 🤔


Inplace editing of core text component broken after upgrading forms components to 3.0.x

We recently upgraded forms components from 2.0.90 to 3.0.50. After upgrade we noticed that upgrading forms components broke the inplace editing functionality of the core Text component. The post call also has the formatting stripped. This works fine on 2.0.90
Expected Behaviour
Inplace editing of Text component shows toolbar and doesn't remove formatting when inplace editing is active and the cursor is clicked outside the component.
Actual Behaviour
Inplace editing of Text component doesn't show toolbar and removes formatting when inplace editing is active and the cursor is clicked outside the component.
Reproduce Scenario (including but not limited to)
This can be observed on a new repo or any existing repo with forms by upgrading forms to 3.0.44 - 3.0.52 with core components 2.24.6 or above
Steps to Reproduce
Add core Text component to any page and author it using dialog normally with some formatting. Select the component and click on the edit icon for inplace editing. Click outside the component and all formatting present in the component is removed
Platform and Version
AEM cloud environments and AEM cloud SDK
AEM Version (mention the exact version in case of cloud SDK)
AEM Cloud SDK(tested on AEM SDK v2024.5.16461.20240524T172309Z-240400 and above) with core components 2.24.6 or above
AEM Forms Version
AEM Forms 3.0.48 and above(could occur in previous 3.0.x versions)
Sample Code that illustrates the problem
Happens on default generated core Text component
Logs taken while reproducing problem
No logs available attached HAR file of the post request
text component inplace editing issue.json

@samueljdel I attempted to reproduce the issue on my end but was unsuccessful. @im-shiv, could you please verify if the issue can be reproduced?

@samueljdel Could you please provide a video demonstrating the issue?

@rismehta
Attached video for your reference.
https://github.com/user-attachments/assets/8e2470c5-c2dd-4b7f-9e85-bf2845d2bd1a

@rismehta Looks like the root cause for this is the same as https://github.com/adobe/aem-core-forms-components/issues/1374
Commenting out the below code in /apps/core/fd/components/form/container/v2/container/clientlibs/editorhook/js/toolbaractionhook.js makes the toolbar load and the formatting issues are not present.
if(!(hasRichTextLabel || hasRichTextAttribute)){
                editable.config.editConfig.inplaceEditingConfig.editorType="plaintext";
            }

@samueljdel Thanks for identifying the issue. This should be resolved with the changes in this,  https://github.com/adobe/aem-core-forms-components/pull/1375

@samueljdel This issue has been resolved in the release available here: https://github.com/adobe/aem-core-forms-components/releases/tag/core-forms-components-reactor-3.0.54