Document supported image formats for Image component

It isn't very clear from reading the documentation what image formats are supported by the Image component. We should be very explicit about it to avoid issues like https://github.com/react-community/create-react-native-app/issues/194

@brentvatne I upgrated React Native from 0.43 to 0.44 and images disappeared in my projects.
They have paths like this:
 <Image         source={require('../../../resources/logo-bookings.png')}    />
I checked Image component with http source and it works fine
source={{uri: 'https://facebook.github.io/react/img/logo_og.png'}}
What could happen?

@brentvatne not sure this was exactly the way to go but I opened #13807.
I was unsure about tiff and psd but used this as a reference.
Please let me know how I can help further. Thanks

@franciscofsales - can you test each of those on iOS and Android?

@brentvatne sure, will do 👍

@brentvatne done and documented on PR. thanks.

@brentvatne
ico format not support in android in own app
@franciscofsales
Could you add test about ico format

@fogmoon  I face the same problem!

@fogmoon and @zhuyifan2013, as seen here, ico is not handled as a picture, therefore should not be supported. Just in case I'm missing something, I gave it a try with a real device Android and iOS simulator and both failed.
@fogmoon I don't have my iOS device on me for the next week, please submit a PR if you have the chance to do so and think its relevant here, since its already tagged on the documentation PR.
Thanks

@franciscofsales
Thanks for your helpful information.
I also just used iOS simulator (iOS 10) which can render ico image correct. By your ref code, this is impossible.  So I am a little confused.
Whatever,  in my opinion, ico should be recognized as image format for the MIME type image/x-icon.  And now I had to think other method for my crawler-like app to show friendly favicon.ico of the websites.
@brentvatne
@franciscofsales
Could you please suggest a workaround to show favicon.ico ? Or it just can not to make it.
Thanks.

@fogmoon were you able to render the ico with react-native Image correctly on the iOS simulator?
I tried this setup and it just failed.
React-native version: 0.44.0
fresco version: 1.0.1

Also, I found this (issue)[https://github.com/facebook/fresco/issues/868] that is still open regarding fresco supporting ico.

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with Canny! Check out its new home: https://react-native.canny.io/feature-requests/p/document-supported-image-formats-for-image-component


(FACT-753) Update default external fact directories for unified agent layout

This commit updates the default search directories for external facts.
We now look in /opt/puppetlabs/agent/facts.d for both open source and
PE versions of Facter. When Facter 3 ships, we will default to only
searching in this directory, but to facilitate a smoother transition
Facter 2.4 will look in both old and new external fact search paths.
Note that this change only affects Unix agents, as Windows paths are
staying the same.
This change is part of the unified agent effort.

@whopper @haus do we actually need to change the windows location? If we do change it, we will need to update puppet_for_the_win so that the installer can apply the correct permissions to the directory, i.e. we don't want unprivileged users being able to drop external executable facts into the directory, and have LocalSystem execute it. /cc @Iristyle

Hopefully we can leave it alone for Windows - I don't think that we're manipulating the directory structure for Windows agents based on conversations I've had with @melissaanne, but please let me know if that understanding is incorrect @haus

nope, windows shouldn't be changing right now. all clear.

Thinking out loud here... is this a breaking change that requires a facter 3.0 release? Or will this go out in 2.4?

@joshcooper great question. I was thinking that this PR continues to honor the current directories (just adds another one) so it would not be a breaking change. (And then the complementary change in cfacter/facter3 is breaking but that will be released in a major.)
But I'd like that reasoning double checked so: thoughts?

@kylog :+1:

@joshcooper @kylog @haus so just to be totally sure before the merge - I opted to make the path /opt/puppetlabs/agent/facts.d, but we could also do /opt/puppetlabs/agent/facter/facts.d. Do you think leaving out the facter directory is a good idea, or should I put it back in?

I like /opt/puppetlabs/agent/facts.d - it's a shorter path, and I don't think specifying what sub-package uses the directory is all that useful. Anyone else with opinions?


Verify SHA-512 hashes after writing to SIP

Better be safe than sorry ..

Implemented already: https://github.com/KBNLresearch/omSipCreator/blob/master/omSipCreator/omSipCreator.py#L397


Javascript Error in app

Greetings!
Defenetely great extension, worked perfectly, but i've got this strange error today after aploading other set of data into app.
Are there any restrictions?
Error statement:

require.js:1 Error: Cannot add item: item with id 1145 already exists
at n._addItem (/extensions/bi-irregular-timeline/scripts/vis-fix2628.min.js?1509389618675:27)
at n.add (/extensions/bi-irregular-timeline/scripts/vis-fix2628.min.js?1509389618675:27)
at new n (/extensions/bi-irregular-timeline/scripts/vis-fix2628.min.js?1509389618675:27)
at DefaultView.paint (/extensions/bi-irregular-timeline/bi-irregular-timeline.js?1509389618675:644)
at /resources/assets/client/client.js?1509389618675:1
at a (require.js:1)
at require.js:1
at f.$eval (require.js:1)
at f.$digest (require.js:1)
at f.$apply (require.js:1)
(anonymous) @ require.js:1

I think the item id is not unique here..


react native upgrading Orientation issues

constructor OrientationPackage in class OrientationPackage cannot be applied to given types;  new OrientationPackage(),
we are upgrade RN to 0.31.
while installing the app the above exception is coming

I got this error too :(


Missing Formatting Options

The Action options are not available in the new format pane for icons or buttons.

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

ID: 99728831-9577-faee-e82a-8def045dadea
Version Independent ID: 99728831-9577-faee-e82a-8def045dadea
Content: The new Format pane in Power BI Desktop - Power BI
Content Source: powerbi-docs/fundamentals/desktop-format-pane.md
Service: powerbi
Sub-service: pbi-fundamentals
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Hi, @Joseph-Dodd -- good point! Those aren't currently available, but will be in the December release. I'm adding this to a Considerations and Limitations section of the article.


chore: add hardhat migration guide prerequisites

Description
To ensure a smooth migration and compatibility with your plugins, the following prerequisites must be met:
Node.js Version
Minimum: v18.x or later
Hardhat Version
Minimum: 2.16.0

Let's also add the plugin requirements to the hardhat-zksync plugin page. If all plugins have similar requirements, please create a reusable partial and include it in all plugin pages

Added. Please check it now.


Inconsistency: Are days 24 hours or not?

There seems to be some inconsistency in the treatment of days in spans. In particular, TryFrom<Span> for Duration assumes that days are 24 hours, whereas Timestamp::saturating_add rejects days as units that can't be resolved without a specific timezone.
Personaly I think the assumption that days are 24 hours is dangerous and shouldn't be made (because it is readily violated by DST), but more than that I think all functions should at least agree on whether days are assumed to always be 24 hours or not.

It is true that sometimes days are treated as always 24 hours and sometimes days are treated as more or less than 24 hours, depending on time zone transitions. In contexts where the meaning of a day is ambiguous, it's banned, as in the case of Timestamp::checked_add (and Timestamp::saturating_add). In cases where it could be either, like in the Span APIs, whether a day is 24 hours or not is determined by whether 1) a relative date is provided and 2) whether that relative date is a Zoned or not.
The shape of when days are allowed or not, and when they are 24 hours or otherwise, was taken straight from Temporal. For example, see its Instant.add API.
I think it would be better to be very concrete here. If you're working with a Zoned, for example, it is impossible to accidentally treat "1 day" as "always 24 hours." The APIs won't get it wrong precisely because a Zoned is involved. But when you're working with civil time, you want to be able to operate on days, yet civil time is unaware of time zones. So days are always 24 hours.
While I agree that this can all seem very inconsistent and arbitrary upon initial inspection, the thing I really care about is whether you're committing bugs in your code because of it. Do you have any code you've written where you got bit by days being 24 hours when you didn't want them to be?

Personaly I think the assumption that days are 24 hours is dangerous and shouldn't be made (because it is readily violated by DST)

You really can't blanket reject the assumption. Because sometimes you want it. And if you sometimes you want it, you really can't have all functions agree on whether days are uniform or not. Like, if all functions agreed that days were non-uniform, then what would adding 1 day to civil::DateTime do? It doesn't have a time zone, so it can't choose anything other than "1 day is 24 hours." So in that context, it is definitionally uniform. There is no other possible interpretation that I can see. And once you have that, it flows through to other APIs, like Span.

I guess I could have been clearer. I specifically have a problem with TryFrom<Span> for Duration making that assumption. I think the behavior of civil::DateTime is fine, because if you use it you more-or-less explicitly choose to ignore DST and other timezone oddities. However, the conversion to Duration is a general API and I think making the assumption that days are 24 hours there lends itself to misuse when combined with zoned datetimes.

I specifically have a problem with TryFrom<Span> for Duration making that assumption.

Ah I see. That follows from the behavior of Span::round, Span::total, Span::compare, Span::checked_add and Span::checked_sub. And that's all consistent with the corresponding Temporal.Duration APIs as well. Namely, days are always treated as 24 hours unless a relative time zone aware datetime is given.
An alternative design is that these APIs return an error when non-zero day units are given and no relative date is given. But if a relative date is given, then whether it is civil or time zone aware would determine the length of the day.
I think this Temporal issue sketches out the shape of why Temporal went with this design decision. There is even more background here and here, but it gets very dense very quickly.
I am not opposed to diverging from Temporal. I specifically did not set a goal that Jiff must match Temporal. Jiff is merely heavily inspired by Temporal. With that said, I've generally deferred to Temporal on these kinds of decisions, because they quite literally reflect the result of multiple experts investing person years of effort into the design. It doesn't mean they're always right, but there's got to be something compelling IMO to push me towards reversing one of their decisions.

and I think making the assumption that days are 24 hours there lends itself to misuse when combined with zoned datetimes.

Currently not near my computer, but will give an example when I get back (probably tomorrow).

But where did you get the input Span from? Getting a Span from two zoned datetimes will already return a Span with units no bigger than 1 hour. You'll only get bigger units if you explicitly ask for them.

The span comes from external data.

The other problem with your suggestion is that, as of today, all of the Span APIs can be used correctly, without a relative date, using any Span returned by subtracting two datetimes in the default configuration. Your suggestion would make that not the case for spans from the difference between two DateTimes or two Dates.

FWIW, I do find your suggestion compelling.

The other problem with your suggestion is that, as of today, all of the Span APIs can be used correctly, without a relative date, using any Span returned by subtracting two datetimes in the default configuration. Your suggestion would make that not the case for spans from the difference between two DateTimes or two Dates.

Based on my (admittedly relatively surface level) understanding, I would propose this:
The difference between two DateTimes should use hours as the largest unit, which would match Zoned.
The difference between two Dates could be made to work by adding a special case that allows adding or subtracting two spans as long as they both contain only one unit and it is the same unit.
This would almost certainly be an ergonomic hit in some cases that I haven't thought of, but my biased opinion is that the extra strictness and correctness is worth it.

Also the proposed special case for spans is problematic in that it breaks the invariant that you can always add absolute units to a span. That tradeoff may or may not be worth it.

Also the proposed special case for spans is problematic in that it breaks the invariant that you can always add absolute units to a span.

I believe this is not true today. If you're adding two spans and either of those spans have non-uniform units bigger than days, then you need a relative date. Because the lower units could add up and overflow into bigger units. I think the key thing today is that, under the default configuration for computing spans between any two datetimes, yes, you can always add absolute units to the span returned. But the change to avoiding implicitly assuming days are always 24 hours would indeed break that for DateTime and Date. The change to hours for DateTime would restore it there, but yes, I don't see a way to fix it for Date, which is unfortunate.

Honestly, I don't know. Like you said, the discussion gets very dense quite quickly and the tradeoffs are hard to evaluate. I would keep the issue open for now, in case someone else wants to weigh in with more practical experience or proposals.

@FeldrinH Can you say more about your higher level use case here? Like, what is the higher level problem you're trying to solve? This is what I understand so far:

You have some ISO 8601 durations in serialized form somewhere.
You want to parse them and convert them into durations with units no bigger than seconds. Or more generally, a duration with uniform units.
You want an error to appear if there is any ambiguity about what the units might mean.
You demonstrate the problem by comparing the duration before and after rounding with a time zone aware datetime.

I don't mean to ask for these details as a way to dismiss your concern, but I do think it's important to connect the threads a bit more here. In particular, I am wondering about the connection here between the time zone aware datetime after the fact instead of providing it to the rounding routine. Or perhaps that is part of the problem. I could see, for example, not realizing that you need to provide a relative datetime to round, trying it and then relying on it to produce an error if you're doing something wrong. Since it's silent about days, you assume it's okay and go on to do something with those durations and time zone aware datetimes. But had round given you an error, I think your remedy would have been to use a zoned relative datetime with round and thereby get correct spans. Is that right?
If so, yeah, I can see how the failure mode is effectively a way of pushing you towards using the APIs correctly and preventing misuse.

Basically I am parsing and processing some data dumps from some event logs. The documentation on the data format is limited, so I want to validate everything as strictly as possible. As part of that I want to enforce that there must be no ambiguity about the duration of spans. If there ever was ambiguity (e.g. if the event logs contained a span with days) then I would have to figure out what that actually means. The zoned datetimes only come into play because I later summarize the data in my local timezone (which has DST).

But had round given you an error, I think your remedy would have been to use a zoned relative datetime with round and thereby get correct spans. Is that right?

Not quite. If there is ambiguity about the duration of the spans then something is wrong with the input data and I will need to dig deeper into what that means. I am assuming that the durations will never contain ambiguous units like days or months, but I don't know for sure, so my goal with rounding without providing a zoned datetime was to enforce that if my assumption turns out to be wrong I will get an error.

I could see, for example, not realizing that you need to provide a relative datetime to round, trying it and then relying on it to produce an error if you're doing something wrong. Since it's silent about days, you assume it's okay and go on to do something with those durations and time zone aware datetimes.

That is definitely an issue that I could see happening, though my specific situation was a little different.

One suggestion I got from the Temporal folks is to provide a "marker" that makes it okay to assume days are always 24 hours. So, for example, there would be a new SpanDaysAre24Hours marker type (or similarly named) that would have trait impls like impl From<SpanDaysAre24Hours> for SpanRelativeTo. But if that marker isn't given, or a relative date isn't given, then using units of days would result in an error. So in your case, your round call would have errored.
The advantage of a marker is that it absolves users of Jiff from providing a "dummy" relative date in the case that all days are 24 hours.
I'm still going to noodle on this. And I think this is probably something that is a breaking change as well. In particular, this will result in an ergonomic hit when using some of the Span APIs. With that said, I think this is somewhat mitigate by the fact that all of datetime APIs that produce spans, like Zoned::until, also expose the rounding interface. And they set the relative datetime for you.

I really appreciate the API design of Jiff making the correct things easy to do.
On the other hand, I feel like implementing this proposal as the default may violate the principal of least surprise and make me hesitant to just "throw stuff" at Jiff and expect it to work.
While I appreciate Jiff's strong error-driven api, I actually don't want it to be the case that I'm getting random errors due to "valid" data. This isn't in opposition to an error driven api, but rather in favor of somewhat flexible input behavior by default.
As mentioned, this gets very dense very fast, and I'd be concerned for general usability if this is the default and somewhat realistic to hit.
On the other hand, I like the idea of "strict modes" where you can layer additional assertions on input data. This wouldn't require that the internal modeling or types change - instead you can harden the consistency of the data at the edge when you receive it, maybe with some parse_unambiguous method or something similar.

@johnpyp Sorry, I'm having a hard time following your comment. Could you say more concretely what you'd like? Are you saying the status quo is desirable? Because there are plenty of error cases in the status quo too. This issue is just talking about one of them for a few APIs on Span.
Also, does something like this help? Which basically lets you opt out of Span and lets you use something more like std::time::Duration.


Data directory should be located in APPDATA on Windows

What would you like to have changed?

On Windows, certmagic stores its data in %USERPROFILE%/.local/share by default at the moment, which should be located in %APPDATA% as Windows' convention.
Why is this feature a useful, necessary, and/or important addition to this project?

Following the operating system's convention gives users better understanding of the directory's function and eliminates unnecessary directory paths.
What alternatives are there, or what are you doing in the meantime to work around the lack of this feature?

Certmagic is used by Hysteria, which is considering

provide an option in "acme" for customizing the certificate storage directory.

Please link to any relevant issues, pull requests, or other discussions.

My issue in Hysteria repo

That's probably a good idea. I'm not a Windows user; does the data just go into %APPDATA%? Or is there a subfolder, or how does that work?

In Caddy, the default is %AppData%\Caddy 🤔
https://caddyserver.com/docs/conventions#data-directory

Forgot about that 😅  Thanks


Feat: Add support for Hi-DPI screens

@FarhadG can you squash some of those stale commits?

particularly the css ones that did not make it in?

@michaelobriena
That should do it! :+1:


changed session.jwt -> session.strategy

See https://next-auth.js.org/getting-started/upgrade-v4#session

"Created 1 year ago" really messes with my views, I guess it wont happen


Doing update instead of insert when Model::create()

When I used Model::create(), specifying _id uses the updateOne function in MongoDB driver, which leads to silent failure if the _id does not exist in the collection.
To me, this is kind of counter-intuitive. The method is named 'create'. It should mean inserting a new record. What if I want to use a specific type, e.g. incremental integer, as primary key? Seems there's no choice for users.
I'd suggest separating create and update action.

Model::create() method insert new record with passed fields.
MongoDB don't support autoincrement primaries like mysql


Provide a docker-compose.yml for running the complete stack

I'm using one like this:
version: '2'
services:
  lancache:
    image: 'steamcache/generic:latest'
    ports:
      - "80:80"
  lancache-dns:
    image: 'steamcache/steamcache-dns:latest'
    ports:
      - "53:53/udp"
    environment:
      - USE_GENERIC_CACHE=true
      - LANCACHE_IP=<IP_ADDRESS>

Created a new repository at steamcache/docker-compose, This has the full compose example for all services over at uklans, Please raise any issues with the compose file in that repository.


Reformat widget

Reformat widget into a table.

#82c3f209ab0330bf06e7e63e56c332c278ac0403
Initial commit of a widget reformatted with bootstrap's list group: http://getbootstrap.com/components/#list-group
mbbr_model now has a stats function that returns a simple SQL query. mbbr_controller returns the results of that stats function.


Island default

After getting 50 hours into a game, we found the edges of our island. Downloading the map, and then cheating around it confirmed that there was only an infinite expanse of ocean around us.
The map-settings.example.json seems to specify "elevation": "0_17-island", which induces this behaviour.
Is it possible to make the normal generation "elevation": "" the default?

We use the standard example .json files from the headless server archive you can download from factorio.com and I don't we should opinionate them.
You should probably write about this on https://forums.factorio.com if you care enough that the default for the headless server should be more like a vanilla map and no island.
What we can do is to write something in the already way to long readme to change that and generate a new save.
You can do that or I do it in a couple of days. While I am at it I probably restructure the entire readme and split it up into multiple files.

Fair enough. I'm happy to add a bit to the README to help other people who get caught by this.
As a side note, would you (or anyone else happening upon this thread) know of a way of changing the generation for non-loaded chunks?

Maybe this https://mods.factorio.com/mod/ChangeMapSettings works for that? Not sure right now.


Reworks the MetaTextBlockComponent

The component has a slightly different look.

I can pass a text and the component automatically let edit me that text.

The components personal-note.component and motion-comments.component are not used anymore.

There are added two more fonts: The default font with font-weight: 300 and a font for the developer-theme.

@GabrielInTheWorld @tsiegleauq Should we close this unfinished PR? Maybe we can start a new try for 4.x?


WARNING: The script cmark is installed in '/home/user/.local/bin' which is not on PATH.

This error msg showed when i ran the installation lines.
I am using Linux mint 20.3
There is another report of this anomaly but no response is there.

the terminal processes looks like this *

pip3 install gruvbox-factory
Collecting gruvbox-factory
Downloading gruvbox_factory-1.0.0-py3-none-any.whl (5.3 kB)
Collecting rich
Downloading rich-12.6.0-py3-none-any.whl (237 kB)
|████████████████████████████████| 237 kB 390 kB/s
Collecting image-go-nord
Downloading image_go_nord-0.1.5-py3-none-any.whl (11 kB)
Collecting commonmark<0.10.0,>=0.9.0
Downloading commonmark-0.9.1-py2.py3-none-any.whl (51 kB)
|████████████████████████████████| 51 kB 711 kB/s
Collecting pygments<3.0.0,>=2.6.0
Downloading Pygments-2.13.0-py3-none-any.whl (1.1 MB)
|████████████████████████████████| 1.1 MB 368 kB/s
Collecting typing-extensions<5.0,>=4.0.0; python_version < "3.9"
Downloading typing_extensions-4.4.0-py3-none-any.whl (26 kB)
Requirement already satisfied: Pillow in /usr/lib/python3/dist-packages (from image-go-nord->gruvbox-factory) (7.0.0)
Installing collected packages: commonmark, pygments, typing-extensions, rich, image-go-nord, gruvbox-factory
WARNING: The script cmark is installed in '/home/amlan/.local/bin' which is not on PATH.
Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
WARNING: The script pygmentize is installed in '/home/amlan/.local/bin' which is not on PATH.
Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
WARNING: The script gruvbox-factory is installed in '/home/amlan/.local/bin' which is not on PATH.
Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
Successfully installed commonmark-0.9.1 gruvbox-factory-1.0.0 image-go-nord-0.1.5 pygments-2.13.0 rich-12.6.0 typing-extensions-4.4.0

As what I experienced, just move the script in that file to /usr/local/bin and you are ready to go and use the script wherever you want

Alright, it seems it was fixed. Closing it


My second revup foo

Topic: foo2
Relative: foo

Reviews in this chain:
└https://github.com/josh-dewitt-skydio/revup/pull/1 My first revup foo
　└https://github.com/josh-dewitt-skydio/revup/pull/3 My second revup foo


I faced on the build-error of ndarray/Boost.Numpy in the Dockerfile based on Ubuntu18.04LTS

(1)Issue
I used the Dockerfile with bese of Ubuntu16.04 , CUDA10.1 and cuDNN7.
I changed host OS from Ubuntu 16.04LTS to Ubuntu18.04LTS.
Hence I changed the base of Dockerfile as below;
(Pervious)  FROM nvidia/cuda:10.1-cudnn7-devel-ubuntu16.04
(Current)   FROM nvidia/cuda:10.1-cudnn7-devel-ubuntu18.04
I only changed the base of Dockerfile, but I faced on the build Error of ndarry/Boost.Numpy.
Docker file is as below;
Dockerfile.txt
I did not face on build the error with previous Dockerfile which used Ubuntu16.04LTS base.
Build Error as below;

How do I delete this issue?
Why does the build error occur only with the changing of Base Ubuntu version of Dokcerfile?
I'd really appreciate it if anyone give me good advice!
2)Envirment
OS : Ubuntu18.04LTS
CUDA 10.2
Docker : 19.03.9
Regards,

This looks like a basic link error problem (as if your binary was not being linked to libboost_numpy.so at all).  I don't have any good guesses at how a tool chain could cause that, as is this is the kind of symptom that can have many cases.
But I'm afraid I'm not a Docker user myself, and this library is no longer being maintained.  You will be able to find more support if you can switch to the built-in NumPy bindings that have now been included directly in Boost.Python for a while.  Those have essentially the same interface, but are in namespace boost::python::numpy instead of boost::numpy.

Dear TalUimbo
Thank you for your reply and sorry for my delay.
I could not identify the underlying cause of this issue,but I found the way to resolve this issue.
When the Dockerfile,which uses the base of ubuntu16.04 ,Cmake detects the folder /usr/local/lib64 was installed libbost_numpy.so.
But  the Dockerfile,which uses the base of ubuntu18.04, Cmake can not detect the folder /usr/local/lib64 ,hence link error happens.
・The way of resolving this issue/
I added Path of /usr/local/lib64 to Makefile.config  for the building of CAFFE, the link error did not happened.
Regards,
Regards


Use ccache on osx

This PR reduces test time.

Is it really faster? Does it can cache compilation results in virtual environment?

I read this topics.
But, I checked travis result. Compile time is unstable. And I cannot find this PR effect.
I am going to try another way.


Allow switching/hybdrid between Semantic and Vector Index in Azure Cogntive Search

Currently, the TextSemanticMemory, uses only Vector Index for searching. But it has shown, in some cases semantic search or hybrid search outperforms Vector index search (src: https://techcommunity.microsoft.com/t5/azure-ai-services-blog/azure-cognitive-search-outperforming-vector-search-with-hybrid/ba-p/3929167)
Allow in Semantic Kernel memory to decide which search strategy to use on Azure Cognitive Search Index

@dluc, would this be a good scenario to use the new Semantic Memory service?

please see https://github.com/microsoft/semantic-kernel/issues/2544


Unable to Modfy Vital Parts on Equipped Weapons

"Modify Vital Parts during Raid" does not check compatibility with "Modify Equipped Weapons", so if you attempt to modify vital parts of an equipped weapon, this will fail as if you cannot modify vital parts, Probably not hard to fix but was confusing for me until i figured that out.

Intended, but I get that it's confusing. I'll look into updating the language in the settings to make it more clear.
The reason you can't modify equipped weapons in raid is the game has issues when you have an incomplete weapon equipped.


Setup Development Environment wiki

1.I had to install phantomjs to run "grunt test" it is not listed on the wiki.
I also had to update nodejs after installing it. I suggest to make a setup script to save some time.
I don't know if it contains all what is needed I’ve created it after installing everything manually.
http://pastebin.com/Hqum6HfF
2.I'm also missing API docs to the libs that are used.  I'm new to js and don't know where to look so maybe those two?
https://developer.mozilla.org/en-US/docs/Web/API/
https://nodejs.org/api/

These are good points. I don't necessarily want to maintain installation instruction for the different libraries we are using, but we could at least have a link to nodejs, phantomjs, casperjs and explain where each one is required (basically node & grunt are required to build, phantomjs is required to run unit tests, and casperjs required to run the integration tests in headless mode).
Regarding JS and libs, you are right we can point to MDN & Node documentation. We should also have links to the documentation of the libraries we use (jquery, spectrum, tinycolor, jszip).
And finally, need also to document a bit the current architecture. How to add a new JS, a new CSS, how the Controllers work etc ...

Assigning to myself as I am the only one who can edit the wiki ...

Phantom js is now installed via npm install. A developer should be able to run npm install and grunt unit-test without any extra step.

No extra setup steps required now, closing.


Remove error stack trace if error exists in a remote environment

Resubmission of #230 with a fix so that __ERROR__ is not set to {} when error is undefined in a remote environment
GUS: https://gus.lightning.force.com/lightning/r/ADM_Work__c/a07EE00000KAC67YAH/view
Description
Stack trace data and SSR options are visible on error pages when viewing page source. This change stops this data from being displayed in page source.
Types of Changes

[X] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Documentation update
[ ] Breaking change (could cause existing functionality to not work as expected)
[ ] Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

Removing a public function or component or prop
Adding a required argument to a function
Changing the data type of a function parameter or return value
Adding a new peer dependency to package.json

How to Test-Drive This PR

npm ci at root to rebuild sdk
Overwrite getProps method in app/components/_app.jsx inside to throw an error.

App.getProps = () => {
  throw new Error('this is an error')
}

Start Retail React App locally & verify you can see the error stack trace
Deploy the Retail React App to Managed Runtime and verify you cannot see the error stack trace

Checklists

General

[X] Changes are covered by test cases
[X] CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance
You must check off all items in one of the follow two lists:

[] There are no changes to UI

or...

[ ] Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
[ ] Changes comply with WCAG 2.0 guidelines levels A and AA
[ ] Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

[ ] Changes include a UI text update in the Retail React App (which requires translation)

Deployed here: https://scaffold-pwa-test-env-2.mobify-storefront.com/
work like a charm.


Cannot export a generic function

What version of Go are you using (go version)?

$ go version

go version go1.17 darwin/amd64

Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/pillar/Library/Caches/go-build"
GOENV="/Users/pillar/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/pillar/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/pillar/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GOVCS=""
GOVERSION="go1.17"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Applications/source/work/go-github/go-generic-learn/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/69/y88g1ft14_g35vl07y3dr6200000gn/T/go-build279161576=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

main.go:
package main

import "go-generic-learn/pkg"

func main() {
	pkg.Say([]string{"Hello, ", "world\n"})
}

pkg/pkg.go:
package pkg

import "fmt"

func Say[T any](s []T) {
	for _, v := range s {
	 fmt.Print(v)
	}
 }

go run -gcflags=all=-G=3 main.go

What did you expect to see?
print: Hello, world
What did you see instead?
# go-generic-learn/pkg
pkg/pkg.go:5:6: internal compiler error: Cannot export a generic function (yet): Say

Please file a bug report including a short program that triggers the error.
https://golang.org/issue/new

Looks like here is the answer Cannot export a generic function (yet).  yet generic are not released, support is limited.

@ymzuiku generic is not fully supported in go1.17, if you want to try, please use gotip.
See similar: https://github.com/golang/go/issues/43931#issuecomment-886046248

could visit this.  now  1.17 not yet support use generics at public function
https://preslav.me/2021/08/17/how-to-use-generics-in-golang-starting-from-go1-17/


Windows: Skip RunCidFileCleanupIfEmpty on RS1

Signed-off-by: John Howard<EMAIL_ADDRESS>Same deal as https://github.com/docker/docker/pull/24056 due to changes in the Windows base images on RS1. Needed for 1.12 if Windows CI is to continue passing when the CI servers imminently get rolled forward to post TP5 (aka RS1) builds. @tiborvass

added to the milestone and cherry-pick

LGTM

LGTM


Fixed profile config.

Codecov Report

Merging #283 into master will decrease coverage by 0.01%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master     #283      +/-   ##
==========================================
- Coverage   87.13%   87.12%   -0.02%
==========================================
  Files          19       19
  Lines        1780     1778       -2
  Branches      208      208
==========================================
- Hits         1551     1549       -2
  Misses        176      176
  Partials       53       53

Impacted Files
Coverage Δ

chalice/cli/__init__.py
75.95% <33.33%> (-0.14%)
:arrow_down:

chalice/cli/factory.py
88.63% <60%> (-0.13%)
:arrow_down:

Continue to review full report at Codecov.

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

The problem is that CLIFactory always use self.profile for botocore session which is set in cli/init.py :129 to argument given when invoking chalice command or None. Thus its always ignore profile setting given in config.json…

ping


You must add a reference to assembly Microsoft.UI.Composition

Describe the bug
I am trying to upgrade my WinAppSDK class library to the latest experimental version 1.1, using Visual Studio 2022.
However I cannot get the library to compile due to several errors (CS0012) saying I must add a reference to assembly Microsoft.UI.Composition.
I created a new project and compared it to the previous project, not having this issue, which used the version 1.0 of WinAppSDK.
I compared the working project to new project and do not see something obvious missing to lead to this error.
Below are the minimum steps required to recreate this issue.
Steps to reproduce the bug

In Visual Studio 2022, create a new project using the template [Experimental] Class Library (WinUI 3 in UWP)
Add the following lines of code:

4. The following error appears
5.

Expected behavior
This error should not happen.
Screenshots

NuGet package version
1.1.0-preview3
Packaging type
No response
Windows version
Windows 10 version 21H2 (19044, November 2021 Update)
IDE
Visual Studio 2022-preview
Additional context
No response

As an additional note, this is not an issue if I create a blank app project


check app is debugging now

if app is debugging now, then the assertionFailure will not excute

Thanks! However I wouldn't merge this code into master branch since it is not official way to check if app is in debbuging state.


formin-nucleated actin cable organization

a new term we could use, modeled on GO:0061572:
[Term]
id: GO:new
name: formin-nucleated actin cable organization
namespace: biological_process
def: "A process that results in the assembly, arrangement of constituent parts, or disassembly of a formin-nucleated actin cable." [GOC:mah]
is_a: GO:0061572 ! actin filament bundle organization
intersection_of: GO:0016043 ! cellular component organization
intersection_of: results_in_organization_of GO:0070648! formin-nucleated actin cable
and add link GO:0070649 ! formin-nucleated actin cable assembly is_a GO:new (manually or by reasoning)

Hi @mah11
Just to confirm, this is how the resulting term addition will look.  Is that correct?
GO:0061572 actin filament bundle organization
is_a GO:new formin-nucleated actin cable organization
is_a GO:0070649 formin-nucleated actin cable assembly
Thx.

yes, that looks fine
thanks :)


Performance improvement for most scenes

tl;dr: this is a significant performance improvement for many scenes. 1.7x - 2.6x improvement in animation it/s.
This is a small change to some of the hotest paths in rendering objects. The biggest win comes from not using np.allclose() to check if two points are close enough. In general, NumPy is awesome at operating on large arrays, but overkill for very tiny questions like this. Created a small function to determine if two points are close using the same algorithm, and limited it to 2D points since that's all we need in set_cairo_context_path().
A couple of other minor tweaks to reduce or eliminate other uses of NumPy in this path.
In general, it is better to avoid wrapping lists in np.array when a real NumPy array isn't actually needed.
Added a new file for performance test scenes, with a single scene from the end of a video I've been working on.
Data:
MacBook Pro (16-inch, 2019)
macOS Catalina 10.15.4
2.4 GHz 8-Core Intel Core i9
64 GB 2667 MHz DDR4
Python 3.7.3 (default, Mar  6 2020, 22:34:30)
Profiler: yappi under Pycharm.
Using the scene Perf1 from the included perf_scenes.py, averaged over 5 runs and rendered with:
manim.py perf_scenes.py Perf1 -pl --leave_progress_bars
Before:
Animation 0: FadeInTextMobject, etc.:               8.93it/s
Animation 1: ShowCreationParametricFunction, etc.: 84.66it/s
Profiler shows 48.5% of the run spent under Camera.set_cairo_context_path()
After
Animation 0: FadeInTextMobject, etc.:               23.45it/s  -- 2.63x improvement
Animation 1: ShowCreationParametricFunction, etc.: 149.62it/s  -- 1.77x improvement
Profiler shows 19.9% of the run spent under Camera.set_cairo_context_path()
Less improvement with production-quality renders, and percent improvement varies with scene of course. This appears to be a good win for every scene I'm working on though. I hope it will be for others, too.
NB: there are more perf improvements to be had, of course, but this is the best one I currently have.
Thanks for contributing to manim!
Please ensure that your pull request works with the latest version of manim.
You should also include:

The motivation for making this change (or link the relevant issues)
How you tested the new behavior (e.g. a minimal working example, before/after
screenshots, gifs, commands, etc.) This is rather informal at the moment, but
the goal is to show us how you know the pull request works as intended.

Alright, looks good!


Crashes after opening and attempting to change directory with tab completion

Onivim version 0.4.0 crashes after opening and attempting to change directory with tab completion. This issue may be related to #419.
Steps to reproduce

Double click on onivim from within finder
shift+: then cd type directory then tab
Wait as its loading/rendering

I welcome verbiage correction, what does the blue line moving mean?

Attempt to cd again with absolute path
Nothing....
Crash

Onivim Crash Log
Stack overflow:

MacOS Crash Report
Date/Time:        2020-04-21 19:34:17 -0400
End time:         2020-04-21 19:34:32 -0400
OS Version:       Mac OS X 10.15.4 (Build 19E287)
Architecture:     x86_64h
Report Version:   29

Data Source:      Stackshots
Shared Cache:     0x2eca000 E09A288B-531C-3953-A3AC-95EDE8DCF10D

Command:          Oni2_editor
Path:             /Applications/Onivim2.app/Contents/MacOS/Oni2_editor
Version:          ??? (???)
Parent:           launchd [1]
PID:              69227

Event:            hang
Duration:         14.79s
Duration Sampled: 9.59s (process was unresponsive for 5 seconds before sampling)
Steps:            96 (100ms sampling interval)

Hardware model:   MacBookPro14,3
Active cpus:      8

what does the blue line moving mean?

It's a progress bar. If it's anchored to the left side it shows actual progress, and if not it just indicates it's working.

I'm not able to reproduce this. Could you try running it from the terminal with OCAMLRUNPARAM=b <oni2 executable> -f --trace. That should give us lots of logging and a stack trace. The last 100 lines or so of the log should hopefully be enough.

Thanks for quick followup.
Files:
onivim2-macos-crash.log
onivim2-trace-stdout-n-stderr.log
The onivim2-trace-stdout-n-stderr.log file is the result of running the below command, and following the steps mentioned earlier. I did not see anything obvious in the output that points to a cause (last 100 lines). Also attached is the crash report from masOS.
OCAMLRUNPARAM=b /Applications/Onivim2.app/Contents/MacOS/Oni2 -f --trace 2>&1 | tee ~/onivim2-trace-stdout-n-stderr.log

The intended workflow was to click on the Onivim icon and cd to a working directory. I experience the crash if the initial working directory (when Onivim opens) is $HOME. As a work around, can I configure Onivim to open a different directory by default, from the dock?
My guess is that the searching of $HOME leads to an issue which causes the crash.

Seems like the trace didn't capture the stack trace. What's in onivim-crash.log now? You can also log directly to file using --log-file btw. That should capture the stack trace in the log too.
From the log it looks like it's crashing after filtering though 708957 files. Do you have 700k files in that folder?

As a work around, can I configure Onivim to open a different directory by default, from the dock?

You can give it another directory as a command line argument, though it doesn't seem like there's any convenient way of doing that on macOS. It's possible though: https://superuser.com/questions/271678/how-do-i-pass-command-line-arguments-to-dock-items

Should tab completion work when using :cd ~/somefolder/?
If I immediatly open and change directory its fine e.g. :cd ~/ws. However if I wait around in $HOME try to tab complete to another directory - it crashes.
The crash log file I have is empty and is "onivim2-crach.log" not sure if that matters. There are 149 files at the top level of my home directory. See image for file count estimates. At full depth there are over a million files within $HOME.

Nonetheless I will do a clean install of Onivim and open it from the command line.

Perhaps having an option to limit filter depth would help with performance when working in directories with a large number of files.

Should tab completion work when using :cd ~/somefolder/?

Yes, but only for the items in that folder. It certainly shouldn't recurse, which it seems like it does. Can you see completion items that aren't directly in that folder?

The crash log file I have is empty and is "onivim2-crach.log" not sure if that matters.

If it's crashed again after running without --trace it will overwrite the file with just the exception and no stack trace. Using --trace it should dump a stack trace to that file. You can also try using --log-file and --trace together to create a log file that should include the exception and stack trace at the end.


Create Complementary Dark Mode for the Mobile UI Kit

Moved to Sprint 53 as the Light mode in Figma & XD have discrepancies.


Enhancement request: MDTabs 2.0.1

Description of the Feature
I wish to do lazy loading of MDTabsPrimary tabs and tab content with KivyMD 2.X , because the data displayed comes from some server.
Of course I assume I must statically define at least one tab and its contents.
I would like

a method to append a new tab (and it's contents) at any time step.
a method to replace the content of any existing tab at any time step.

I was able implement lazy loading of tabs with KivyMD 1.X
Thanks for your time, I think version 2 is great.

Thank you. Do you have any problems implementing this or can we close this issue?

I can add tabs (but not their content), and I have a problem adding or changing Tab content.  I think the issue is a different time step to that in which the  MDTabsPrimary was instantiated.
I expect I can workaround by rebuilding the MDTabsPrimary as each tab contents arrives, but there will a (triangular) performance hit due to re-building tab contents on each new tab content.  8 tabs would be a total of 36 tab contents builds.
So I'd like an enhancement, the importance of dynamic loading of hidden tab contents in the context of your project as a whole is yours to prioritize.
Thanks for your time.

@HeaTTheatR
I tried my assumed workaround, dynamically rebuilding (in Python) both MDTabsPrimary, and also just its children. I ran into problems with tab event scheduling:
   File "C:\Users\Bobf\AppData\Local\Programs\Python\Python311\Lib\site-packages\kivymd\uix\tab\tab.py", line 1241, in <lambda>
     lambda x: self._tabs_carousel.current_slide.tab_item.dispatch(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 AttributeError: 'MDLabel' object has no attribute 'tab_item'

This MDLabel instance is the replaced tab content.
For the moment I'm out of ideas, so I would like to leave the issue open.

Okay, thanks for the analysis. I'll check it out...

Two Examples of changing Content at a later time step.
The first example is appending the second example is replacing

Adding more tabs and content at a later time step.
The tabs are added but the new content is the content of the previous last tab.

from kivy.lang import Builder
from kivy.clock import Clock

from kivymd.app import MDApp
from kivymd.uix.label import MDLabel
from kivymd.uix.tab import (
    MDTabsItemIcon,
    MDTabsItemText,
    MDTabsItem,
)

KV = '''
MDScreen:
    md_bg_color: self.theme_cls.backgroundColor

    MDTabsPrimary:
        id: tabs
        pos_hint: {"center_x": .5, "center_y": .5}
        size_hint_x: .6

        MDDivider:

        MDTabsCarousel:
            id: related_content_container
            size_hint_y: None
            height: dp(320)
'''

class Example(MDApp):
    def on_start(self):
        super().on_start()
        self.add_tabs(["Flights","Trips","Explore"])
        Clock.schedule_once(self.more_tabs, 2)

    def more_tabs(self,dt):
        #### These tabs are added, but not the contents
        self.add_tabs(["Dogs","Cats","Snakes"])

    def add_tabs(self, names):
        for tab_name in names:
            self.root.ids.tabs.add_widget(
                MDTabsItem(
                    MDTabsItemText(
                        text=tab_name,
                    ),
                )
            )
            self.root.ids.related_content_container.add_widget(
                MDLabel(
                    text=tab_name,
                    halign="center",
                )
            )
            self.root.ids.tabs.switch_tab(icon="airplane")

    def build(self):
        self.theme_cls.primary_palette = "Olive"
        return Builder.load_string(KV)

Example().run()

=====================================================================
2) Replacing the contents of existing tabs at a later time step.
Works, but crashes on subsequent tab change initiated by clicking tab:
   File "C:\Users\Bobf\AppData\Local\Programs\Python\Python311\Lib\site-packages\kivy\uix\carousel.py", line 295, in load_slide
     start, stop = slides.index(self.current_slide), slides.index(slide)

Or with swipe:
   File "C:\Users\Bobf\AppData\Local\Programs\Python\Python311\Lib\site-packages\kivymd\uix\tab\tab.py", line 1034, in android_animation
     a = instance.current_slide.tab_item
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 AttributeError: 'MDLabel' object has no attribute 'tab_item'

from kivy.lang import Builder
from kivy.clock import Clock

from kivymd.app import MDApp
from kivymd.uix.label import MDLabel
from kivymd.uix.tab import (
    MDTabsItemIcon,
    MDTabsItemText,
    MDTabsItem,
)

KV = '''
MDScreen:
    md_bg_color: self.theme_cls.backgroundColor

    MDTabsPrimary:
        id: tabs
        pos_hint: {"center_x": .5, "center_y": .5}
        size_hint_x: .6

        MDDivider:

        MDTabsCarousel:
            id: related_content_container
            size_hint_y: None
            height: dp(320)
'''

class Example(MDApp):
    def on_start(self):
        super().on_start()
        self.add_tabs(["Flights","Trips","Explore"])
        # Works, but crashes on tab change.
        Clock.schedule_once(self.replace_tab_content, 2)

    def replace_tab_content(self,dt):
        new_content = ["peace","love","understanding"]
        container = self.root.ids.related_content_container
        container.clear_widgets()
        for content in new_content:
            container.add_widget(
                MDLabel(
                    text=content,
                    halign="center",
                )
            )

    def add_tabs(self, names):
        for tab_name in names:
            self.root.ids.tabs.add_widget(
                MDTabsItem(
                    MDTabsItemText(
                        text=tab_name,
                    ),
                )
            )
            self.root.ids.related_content_container.add_widget(
                MDLabel(
                    text=tab_name,
                    halign="center",
                )
            )
            self.root.ids.tabs.switch_tab(icon="airplane")

    def build(self):
        self.theme_cls.primary_palette = "Olive"
        return Builder.load_string(KV)

Example().run()


autoheal container constantly restarts. "autoheal exited with code 7"

When trying to add autoheal to my container stack, it seems to fail and restart over and over. "autoheal exited with code 7" is emitted to the log each time. Google hasn't been particularly helpful; in particular, there are no results at all for this error message, which doesn't bode well for me.
This is how I have autoheal set up in my compose file:
  autoheal:
    image: willfarrell/autoheal:latest
    tty: true
    container_name: autoheal
    restart: always
    environment:
      - AUTOHEAL_CONTAINER_LABEL=all
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock

I've tried it on several stacks with the same result. The system is a Pi4 4GB on Bullseye. Docker version 20.10.19, build d85ef84.
I had it running without issue on an identical stack on this Pi once before, but after reimaging and starting over the issue began. It has never run successfully in the system's current incarnation.
Any ideas?

I have the same problem.

I don't have a Pi to test with, can one possibly build with set -exou pipefail in entrypoint?


[Question] Index "jrt-fs.jar"

Can you propose a way to index "jrt-fs.jar" please?
Or maybe have a JarFsIndexer?

@BoykoAlex sorry I didn't see this issue (I have been using JIRA to track issues), however considering switching to GitHub for everything.
Can you expand on this a bit more? You can generate an index of jrt-fs.jar, or do you mean indexing the content of module images?

I meant indexing the content of jrt-fs.jar, but think it's ok I got to the stuff (modules and .lcass files) inside of jrt-fs.jar and indexed with Jandex :-)


Add strax.Context documentation, fix #439

What does the code in this PR do / what does it improve?
Fix issue #439, add all the context functions on one place
Can you briefly describe how it works?
Now it's just a function that adds the strax.Context class with all the minianalyses added!
Can you give a minimal working example (or illustrate with a figure)?
I've now added it here:

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 87.637%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
6302

Relevant Lines:
7191

💛  - Coveralls


Error 500

Hi,
I discovered Atsumeru yesterday. What a great idea !
However, I'm not able to use it, I've an error 500.
I don't quite understand the reason.
From what I see, the process is well started:
root@0c04eb3f198e:/app# ps auxf
USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         176  3.0  0.0   7632  4104 pts/0    Ss   11:39   0:00 bash
root         184  0.0  0.0  10040  1536 pts/0    R+   11:40   0:00  \_ ps auxf
root           1  4.8  2.7 10021592 441804 ?     Ssl  11:32   0:23 java -Dserver.port=31337 -jar Atsumeru.jar

Here are the logs.
There is an error, but I don't know if it's due to that.
# docker logs scans

     _   _
    / \ | |_ ___ _   _ _ __ ___   ___ _ __ _   _
   / _ \| __/ __| | | | '_ ` _ \ / _ \ '__| | | |
  / ___ \ |_\__ \ |_| | | | | | |  __/ |  | |_| |
 /_/   \_\__|___/\__,_|_| |_| |_|\___|_|   \__,_|

Version:  (v1.0.2)

2023-08-29 11:32:07.374  INFO 1 --- [           main] com.atsumeru.web.AtsumeruApplication     : Starting AtsumeruApplication v1.0.2 using Java 11.0.20 on 0c04eb3f198e with PID 1 (/app/Atsumeru.jar started by root in /app)
2023-08-29 11:32:07.380  INFO 1 --- [           main] com.atsumeru.web.AtsumeruApplication     : The following 1 profile is active: "production"
2023-08-29 11:32:09.171  INFO 1 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 31337 (http)
2023-08-29 11:32:09.182  INFO 1 --- [           main] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
2023-08-29 11:32:09.183  INFO 1 --- [           main] org.apache.catalina.core.StandardEngine  : Starting Servlet engine: [Apache Tomcat/9.0.60]
2023-08-29 11:32:09.626  INFO 1 --- [           main] org.apache.jasper.servlet.TldScanner     : At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
2023-08-29 11:32:09.862  INFO 1 --- [           main] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded WebApplicationContext
2023-08-29 11:32:09.863  INFO 1 --- [           main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 2402 ms
2023-08-29 11:32:10.382  INFO 1 --- [           main] o.s.s.web.DefaultSecurityFilterChain     : Will not secure any request
2023-08-29 11:32:10.896  INFO 1 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat started on port(s): 31337 (http) with context path ''
2023-08-29 11:32:10.911  INFO 1 --- [           main] com.atsumeru.web.AtsumeruApplication     : Started AtsumeruApplication in 4.196 seconds (JVM running for 4.935)
2023-08-29 11:32:10.913  INFO 1 --- [           main] AtsumeruApplication                      : Application started with command-line arguments: []
2023-08-29 11:32:10.916 ERROR 1 --- [           main] Settings                                 : Unable to load atsumeru.properties
2023-08-29 11:32:10.916  INFO 1 --- [           main] MetadataUpdateService                    : Metadata service started
2023-08-29 11:32:10.918  INFO 1 --- [           main] FoldersProperties                        : Loading folder properties file...
2023-08-29 11:32:10.919  WARN 1 --- [           main] FoldersProperties                        : Unable to load folder properties...
2023-08-29 11:32:10.920  INFO 1 --- [           main] FileWatcherConfig                        : Starting Import Filesystem Watcher...
2023-08-29 11:32:10.922  INFO 1 --- [           main] CoversSaverService                       : Covers saver service started
2023-08-29 11:32:10.923  INFO 1 --- [           main] BonjourService                           : Starting Bonjour service with name Atsumeru (v1.0.2)...
2023-08-29 11:32:10.923  INFO 1 --- [       Thread-1] FileWatcherConfig                        : Import Filesystem Watcher started!
2023-08-29 11:32:10.931  INFO 1 --- [           main] BonjourService                           : Bonjour variables: {port=31337, remote.host_name=localhost, remote.address=<IP_ADDRESS>, version=1.0.2, local.address=<IP_ADDRESS>, local.host_name=0c04eb3f198e}
2023-08-29 11:32:10.972  INFO 1 --- [           main] BonjourService                           : Bonjour service started
2023-08-29 11:32:10.978  INFO 1 --- [           main] CategoryRepository                       : Categories loaded. Took 6ms
2023-08-29 11:32:10.981  INFO 1 --- [           main] MetacategoryRepository                   : Metacategories indexed. Took 3ms
2023-08-29 11:32:17.888  INFO 1 --- [io-31337-exec-1] o.apache.coyote.http11.Http11Processor   : Error parsing HTTP request header
 Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.

java.lang.IllegalArgumentException: Invalid character found in method name [0x160x030x010x020x000x010x000x010xfc0x030x030x8bGC0x980x84N0x040x160x020xf90xea0x899Y0xd90xd7:0xd80xc10xfe0x7f0x040xbfm0xe10x1e*0xf90xf00x1f0x0c0xc8 ]. HTTP method names must be tokens
        at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:419) ~[tomcat-embed-core-9.0.60.jar!/:na]
        at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:271) ~[tomcat-embed-core-9.0.60.jar!/:na]
        at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) ~[tomcat-embed-core-9.0.60.jar!/:na]
        at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:889) ~[tomcat-embed-core-9.0.60.jar!/:na]
        at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1743) ~[tomcat-embed-core-9.0.60.jar!/:na]
        at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) ~[tomcat-embed-core-9.0.60.jar!/:na]
        at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191) ~[tomcat-embed-core-9.0.60.jar!/:na]
        at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659) ~[tomcat-embed-core-9.0.60.jar!/:na]
        at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) ~[tomcat-embed-core-9.0.60.jar!/:na]
        at java.base/java.lang.Thread.run(Unknown Source) ~[na:na]

2023-08-29 11:32:41.046  INFO 1 --- [io-31337-exec-5] o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring DispatcherServlet 'dispatcherServlet'
2023-08-29 11:32:41.046  INFO 1 --- [io-31337-exec-5] o.s.web.servlet.DispatcherServlet        : Initializing Servlet 'dispatcherServlet'
2023-08-29 11:32:41.047  INFO 1 --- [io-31337-exec-5] o.s.web.servlet.DispatcherServlet        : Completed initialization in 1 ms
2023-08-29 11:32:41.079  INFO 1 --- [io-31337-exec-5] RequestLogInterceptor                    : [Private@Unknown] Requested /

The atsumeru part of my docker-compose.yml (I've added the 31337 port to bypass my reverse-proxy (traefik)) :
scans:
    image: atsumerudev/atsumeru:latest
    container_name: scans
    ports:
      - 31337:31337
    volumes:
      - ./scans/data/library/:/library/:rw
      - ./scans/data/config/:/app/config/:rw
      - ./scans/data/db/:/app/database/:rw
      - ./scans/data/cache/:/app/cache/:rw
      - ./scans/data/logs/:/app/logs/:rw
    labels:
      - "traefik.enable=true"
      - "traefik.http.services.scans-http31337.loadbalancer.server.port=31337"
      - "traefik.http.middlewares.scans-redirect-https.redirectscheme.scheme=https"
      - "traefik.http.routers.scans-http.rule=Host(`scans.myfqdn.fr`)"
      - "traefik.http.routers.scans-http.entrypoints=http"
      - "traefik.http.routers.scans-http.middlewares=scans-redirect-https"
      - "traefik.http.routers.scans-https.rule=Host(`scans.myfqdn.fr`)"
      - "traefik.http.routers.scans-https.tls.certresolver=myresolver"
      - "traefik.http.routers.scans-https.entrypoints=https"
      - "traefik.http.routers.scans-https.service=scans-http31337"
      - "traefik.http.routers.scans-https.middlewares=secHeaders@file" # hsts and co
    networks:
      net_my-network:
    restart: unless-stopped

My folders architecture:
# tree -ugp ./scans
[drwxr-xr-x root     root    ]  .
└── [drwxr-xr-x root     root    ]  data
    ├── [drwxr-xr-x root     root    ]  cache
    ├── [drwxr-xr-x root     root    ]  config
    ├── [drwxr-xr-x root     root    ]  db
    │   ├── [-rw-r--r-- root     root    ]  library.db
    │   ├── [-rw-r--r-- root     root    ]  library.db-shm
    │   ├── [-rw-r--r-- root     root    ]  library.db-wal
    │   └── [-rw-r--r-- root     root    ]  users.db
    ├── [drwxr-xr-x root     root    ]  library
    └── [drwxr-xr-x root     root    ]  logs
        ├── [-rw-r--r-- root     root    ]  requests.log
        └── [-rw-r--r-- root     root    ]  requests.log.lck

7 directories, 6 files

If you have any idea...

@Rollbacke please, check this API url <host:port>/api/v1/books
It may be a little bit consfusing but (i hope, for now) there is no any of "web interface" for Atsumeru
Despite that you need to use AtsumeruManager for server managing (and reading) and/or AtsumeruAndroid if you want to read your books on Android
Also, you can build and use AtsumeruManager as WebApp

Oh damn. I didn't understand anything.
Indeed, everything works.
I was wondering why there were two github repositories for the same app, now I get it.
Sorry...

So I'll end on that, it would be cool to have a Docker image for AtsumeruManager :D
I will try to make a Dockerfile based on Atsumeru's, I could suggest it to you.

@Rollbacke preparing some new update for manager and will try to wrap WebApp version into Docker image. If you have any other questions about Atsumeru, fell free to ask them on https://t.me/atsumeru_talk


Unexpected message type: <class 'schema.schema.ChatMessage'>

When using the hosted app in the README this error is returned.

Needed a reboot, should be fixed now. Thanks for reporting!


Add Automated Network Provider Detection

Endpoint: /api/utils/network-provider
Method: GET
Description: Automatically identifies the network provider from submitted phone numbers and validates number format
Authorization Required: No
Parameters: Phone Number
Feedback:
Success: Returns network provider details
Failure: "Invalid phone number format" or "Unknown network provider"

Please assign me to this issue


Unhappy path network error injection test

What this PR does / why we need it:
Unhappy path network error injection test
TODO tasks : Enable Autofstrim, testrail link and coreanalysis
Which issue(s) this PR fixes (optional)
Closes #
Special notes for your reviewer:

@Santhoshairody please squash all commits before merging.


how to update version electron in mocha test

can somebody know how to update version of electron because when i run mycode in npm start is working but when i run my code in mocha test is have a lot of error

the left one is run with : npm start
the right one isrun with : test mocha
and the problem is i think the electron is different version
can somebody explained what happened :)

@maajja please note this is an issue tracker, not a help forum.
Searching the internet you will find documentation and tons of tutorials relating to electron.


Under Linux, check (in post-install script?) for availability of libgconf and ask to install if not found

Just upgraded Ubuntu from 17.10 to 18.04 and creating app stopped working. Was working perfectly in 17.10
I noticed that the progress bars when both inferring the app stops at 60%, and packaging the app stops ~68%. It appears to complete creating the app files but the executable does not launch. Not seeing any other indicators that there are issues.

Update- trying to launch from the terminal yielded this message: error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory
Installing that using  sudo apt-get install libgconf-2-4 fixes the issue. Hope that helps some other people out.

Thanks @skylundy ! Looks like https://github.com/electron/electron/issues/1518 , we'll probably have more of such reports, I guess Debian/Ubuntu are stopping installing libgconf by default due to dconf. Renaming the issue.

I tested recently-released 8.0.4 in a bare docker of Ubuntu 19.10, and I think this is no longer an issue. Closing, feel free to reopen if I'm missing anything.


bat is a less alternative

cat reads files to stdout, less and bat are for interactive viewing
I know bat claims to be a cat alternative, but... please... 🥺

not based.
bat is a cat clone with a lot more features: it can print to stdout, be a less replacement and more.
Please read the man before writing these things.

less is a pager, bat isn't.  bat uses a pager when stdout is a tty, but has no pagination capabilities of its own.
There are Rust pager that could potentially replace less, such as streampager or rust-pager.


No PostgreSQL clusters exist; see "man pg_createcluster" ... (warning).

I am using Docker for Mac (Version 1.12.0-rc4-beta20 (build: 10404))
After creating a container, I couldn't connect to Postgres. Following is what I did to reproduce the issue, and get it working.
docker run --name postgres-1 -e POSTGRES_PASSWORD=postgres -d postgres:9.5.3
docker exec -it postgres-1 /bin/bash
root@ee38e70bca23:/# /etc/init.d/postgresql start
Above /etc/init.d/postgresql start command gave the following error.
No PostgreSQL clusters exist; see "man pg_createcluster" ... (warning).
After googling I found http://dba.stackexchange.com/questions/50906/why-wont-postgresql-9-3-start-on-ubuntu
Ran following commands, and after that Postgres was running.
root@ee38e70bca23:/# dpkg-reconfigure locales
root@ee38e70bca23:/# pg_createcluster 9.5 main --start
root@ee38e70bca23:/# /etc/init.d/postgresql start
Running dpkg-reconfigure locales prompted me to choose a locale, and I chose en_US.utf8. How can I extend this image, and use RUN commands in a Dockerfile to avoid prompting to choose the locale?
Is this something that can be fixed in postgres image?

You definitely shouldn't be running the init.d scripts in the container, since there is no init process in the container.  Postgres itself is PID 1 within the container.  Your first docker run command starts postgres and only postgres.  docker exec is a neat trick to get an interactive shell in the same namespaces as the container so that we can inspect things.
$ docker run --name postgres-1 -e POSTGRES_PASSWORD=postgres -d postgres:9.5.3992fd0e32d3e673f2c88c43a72b4ad43e5369d7974ae9d10dec789b6d4f45029
$ docker run -it --rm postgres psql -U postgres -h ip-of-postgres-container
Password for user postgres:
psql (9.5.3)
Type "help" for help.

postgres=#

As for changing the locale, that is in the docs under how-to-extend-this-image. This is the source for the docs on the Docker Hub.

@yosifkit Thanks a lot for the explanation. For some reason, the first few times I tried the container, I couldn't connect to it from localhost even with port mapping. That's why I tried getting it working as above. Now I can connect from localhost with a command like below.
docker run --name postgres953 -e POSTGRES_PASSWORD=postgres -p 5432:5432

Just in case it is useful for somebody, in my case I got that error because I was running the container with another process within it (because of a helper shell function that I didn't realize it was not right in this case). So, I was running something like:
docker run --name postgres-1 -e POSTGRES_PASSWORD=postgres -d postgres:9.5.3 tail -f /dev/null


warn and fall back to byte encoding, rather than fail, in the case of a mismatched field size

Real-world example in the file Bicicleta20201025061019.fit from https://github.com/GoldenCheetah/GoldenCheetah/issues/3645 (device is Coros Pace 2)
It appears to parse fine with this small change.

Looks good to me, would you be able to add that file to the repo and add a test for it? (the uploader gave permission in the linked thread)

Done in 951233d.
Is this repo not set up to run the tests automatically via Travis-CI or GitHub Actions? :thinking:

Here's the form of the offending messages:
1803. event [data]
 * event: timer
 * event_group: 0
 * event_type: start
 * timer_trigger: (0,)               # <- uint32, but only 1 byte, not 4 bytes
 * timestamp: 2020-10-25 11:41:39

Unfortunately no. I've had it in the back of my mind to modernize this repo a bit (drop support for python<3.6, use GitHub Actions to automatically run tests) but haven't gotten around to it.
The change looks good, I just made a small change to capture and test that the warning is being emitted.

Thanks!

Unfortunately no. I've had it in the back of my mind to modernize this repo a bit (drop support for python<3.6, use GitHub Actions to automatically run tests) but haven't gotten around to it.

I recently made some similar upgrades to a couple repos of mine. This one is pretty straightforward:
https://github.com/dlenski/gp-saml-gui/compare/f408593~..3b2bd3d (based on https://github.com/actions/starter-workflows/blob/main/ci/python-package.yml)
Happy to contribute something similar if you don't get around to it soon.

The change looks good, I just made a small change to capture and test that the warning is being emitted.

Good idea! :+1:


logging: Reflect recent ServiceAccount changes to the integration test

/area testing
/kind bug
/kind regression
This PR reflects the following changes to the integration test:

loki's ServiceAccount was removed with https://github.com/gardener/gardener/pull/5010
fluent-bit that is copied to the Shoot needs to have its ServiceAccount with .automountServiceAccountToken=true. By default it is copied with .automountServiceAccountToken=false but the fluent-bit Pods cannot have a projected ServiceAccount token magic done by default (fluent-bit is workload in the Shoot cluster, ref https://github.com/gardener/gardener/issues/4924).

Fixes #5249
Release note:

NONE

/invite @rfranzke @vlvasilev

/milestone v1.39


November commit

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contributing.html before opening a pull request.

What is the purpose of the pull request
(For example: This pull request adds quick-start document.)
Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

View detailed results in CodeScene

CodeScene PR Check

Recommended Review Level
Inspect the code that degrades in code health.

Warnings
Low Code Health for new/renamed ModulesAverageCodeHealth685.java has a low code health score with 7.23.

Review of New Files
1 new file(s) below the threshold for new code (8.1).0 new file(s) where the code health is above the threshold.hudi/AverageCodeHealth685.java Potentially Low Cohesion : Cohesion is a measure of how well the elements in a file belong together.  Bumpy Road : A Bumpy Road is a function that contains multiple chunks of nested conditional logic inside the same function. The deeper the nesting and the more bumps, the lower the code health. Detected Bumpy Roads: getPagedService, updatedHealthStatus, ServiceManager.ServiceReporter.run.  Deeply Nested Logic : Deeply nested logic in: getPagedService (depth = 5) Complex Method : Complex implementations in: getPagedService (cc = 18), ServiceManager.ServiceReporter.run (cc = 12), updateIpAddresses (cc = 9), updatedHealthStatus (cc = 9). A Complex Method has a high cyclomatic complexity. The recommended threshold for the Java language is  a cyclomatic complexity lower than 9. Excess function arguments : Excess arguments in: getInstance, getPagedService Functions with many arguments indicate either a) low cohesion where the function has too many responsibilities, or b) a missing abstraction that encapsulates those arguments. Primitive obsession : Code that uses a high degree of built-in, primitives such as integers, strings, floats, lacks a domain language that encapsulates the validation and semantics of function arguments. Primitive Obsession has several consequences: 1) In a statically typed language, the compiler will detect less erroneous assignments. 2) Security impact since the possible value range of a variable/argument isn't retricted. Heavy usage of string arguments : String is a generic type that often fail to capture the constraints of the domain object it represents. Consider introducing custom types instead.


release mgmt package: containerservice

The npm pack and npm run build success in my local environment, but failed in CI.


Integrate PCF and DSUBm into the workflows

Other #16 just added these in the most minimal way. This issue would address updating the Volume 1 flows and diagrams. Likely needing to create named options and have new diagrams.

PCF and DSUBm might be best added in named options. They will add significant complexity to the diagrams. Note similar is proposed for SeR to be added #15 and likely should be addressed at the same time .
Should PCF replace mentions of BPPC?

would be good to get done, but not resourced at this time. Would seem that the work would fit within a CP.


database sql file created

Created a SQL file in order to create tables and populate them. Team work was involved.

Once this is merged I will fix the 'IF EXISTS' at the top


Update 2.12 to 2.12.6 (and also sbt to 1.1.5)

Since we know people have run into issues on Java 9+ with 2.12.5.

Codecov Report

Merging #894 into master will increase coverage by 0.16%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #894      +/-   ##
==========================================
+ Coverage   85.56%   85.72%   +0.16%
==========================================
  Files          76       76
  Lines        2459     2459
  Branches      166      166
==========================================
+ Hits         2104     2108       +4
+ Misses        355      351       -4

Impacted Files
Coverage Δ

...rc/main/scala/io/circe/numbers/BiggerDecimal.scala
91.87% <0%> (+0.62%)
:arrow_up:

...d/src/main/scala/io/circe/NonEmptySeqDecoder.scala
100% <0%> (+8.33%)
:arrow_up:

...rc/main/scala/io/circe/shapes/SizedInstances.scala
92.85% <0%> (+14.28%)
:arrow_up:

Continue to review full report at Codecov.

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


Prometheus working for none-clusteradmin accounts

Proposal
Use case. Why is this important?
We are several departments, who run on a common openshift cluster, and we are not cluster-admins, which means we cannot query for Pods at ClusterScope f.ex. - and Prometheus does this - even if you direct it to only look at a few namespaces.
I would like for each department to be able to manage their own monitoring - as they are responsible for those services and handling ops for them - and prometheus + mtail would be very nice for that.
Currently Prometheus does not seem to able to work at all - when run in such a context.
I keep getting errors about it trying to access v1.Pods at ClusterScope: https://groups.google.com/forum/#!topic/prometheus-users/tsDEYeshn7k
I have tried disabling scraping of pods - as I'm okay with having to define pods to monitor manually if necessary (but it should be able to just list pods in the given namespaces - to discover.
I tried with just removing the rules from prometheus helm chart that I did not have access to - and improve helm chart to allow for RoleBindings in all namespaces instead of using ClusterRoleBindings - and then I got the admin to insert a common Role - that I could point at. This seems to work fine, and I'll gladly submit a PR for the improved chart to support it - once prometheus can actually work in this context.

cc @brancz

I opened #7470 about the error log - so this can be about making Prometheus support none-clusteradmin usage.. I don't know if thats not right or not.. but IMHO its a bug that it logs that error constantly - and its a missing feature that it does not have options to support none-clusteradmin usage (for openshift users who wants to run their own monitoring :)
Together with container-resource-exporter and this fix in openshift https://bugzilla.redhat.com/show_bug.cgi?id=1756123 - I seem to have solved how to get all the metrics I need - so its actually doable to run my own prometheus and get usage metrics as well.. Kube-state-metrics works in "namespaced" none-cluteradmin mode - so I get request and limit numbers for all my containers.. so it seems its just Prometheus thats hardcoded to expecting being cluster admin and having access to the v1.Pods at clusterscope.

Which version of Prometheus are you using? Because we are actively discovering Endpoints on individual namespaces and that only requires list/watch for those namespaces.

Using v2.18.1

Could you share your entire configuration instead of the snippet?

full configmap
apiVersion: v1
data:
  alerting_rules.yml: |
    {}
  alerts: |
    {}
  prometheus.yml: |
    global:
      evaluation_interval: 1m
      scrape_interval: 1m
      scrape_timeout: 10s
    rule_files:
    - /etc/config/recording_rules.yml
    - /etc/config/alerting_rules.yml
    scrape_configs:
    - job_name: prometheus
      static_configs:
      - targets:
        - localhost:9090
    - job_name: kube
      static_configs:
      - targets:
        - api-klavs2-prometheus-kube-state-metrics:8080
    - job_name: kubernetes-pods
      kubernetes_sd_configs:
      - namespaces:
          names:
          - api-klavs2-gateway-bank-d1
          - api-klavs2-gateway-web-d1
          - api-klavs2-manager-d1
          - api-klavs2-portal-d1
          - api-klavs2-tiller-d1
        role: pod
      relabel_configs:
      - action: keep
        regex: true
        source_labels:
        - __meta_kubernetes_pod_annotation_prometheus_io_scrape
      - action: replace
        regex: (.+)
        source_labels:
        - __meta_kubernetes_pod_annotation_prometheus_io_path
        target_label: __metrics_path__
      - action: replace
        regex: ([^:]+)(?::\d+)?;(\d+)
        replacement: $1:$2
        source_labels:
        - __address__
        - __meta_kubernetes_pod_annotation_prometheus_io_port
        target_label: __address__
      - action: labelmap
        regex: __meta_kubernetes_pod_label_(.+)
      - action: replace
        source_labels:
        - __meta_kubernetes_namespace
        target_label: kubernetes_namespace
      - action: replace
        source_labels:
        - __meta_kubernetes_pod_name
        target_label: kubernetes_pod_name
    alerting:
      alertmanagers:
      - kubernetes_sd_configs:
          - role: pod
        tls_config:
          ca_file: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
        bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token
        relabel_configs:
        - source_labels: [__meta_kubernetes_namespace]
          regex: api-klavs2-monitoring-d1
          action: keep
        - source_labels: [__meta_kubernetes_pod_label_app]
          regex: prometheus
          action: keep
        - source_labels: [__meta_kubernetes_pod_label_component]
          regex: alertmanager
          action: keep
        - source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_probe]
          regex: .*
          action: keep
        - source_labels: [__meta_kubernetes_pod_container_port_number]
          regex:
          action: drop
  recording_rules.yml: |
    {}
  rules: |
    {}
kind: ConfigMap
metadata:
  annotations:
    meta.helm.sh/release-name: api-klavs2-prometheus
    meta.helm.sh/release-namespace: api-klavs2-monitoring-d1
  creationTimestamp: 2020-06-26T10:24:33Z
  labels:
    app: prometheus
    app.kubernetes.io/managed-by: Helm
    chart: prometheus-11.5.0
    component: server
    heritage: Helm
    release: api-klavs2-prometheus
  name: api-klavs2-prometheus-server
  namespace: api-klavs2-monitoring-d1
  resourceVersion: "339235079"

The discovery config under the alerting section is the culprit. You are not scoping the namespace to discover from there, which is why it tries to discover the Alertmanager pods from all namespaces.

why aren't those logs in alertmanager pod then?.. I'll test it out :)

It's Prometheus discovering Alertmanager being the problem.

Thank you for the clarity. The default in chart Values.yaml - is:
alertmanagers: []
That threw me off :)
I'll see how to get my PR to the prometheus helm chart posted (fighting getting access to github push here unfortunately) - which enables support for using "common" clusterrole, with RoleBinding per-namespace instead - for those of us running on openshift cluster as none-cluster admins :)


[HUDI-7086] Scaling gcs event source

Change Logs
Scaling gcs event source to support consuming 1000 messages or more per round of ingestion to hudi.
Impact
Scaling gcs event source to support consuming 1000 messages or more per round of ingestion to hudi.
Risk level (write none, low medium or high below)
low.
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@vinishjail97 : Can you review this PR

hey @xushiyan : once vinish stamps the patch, can you take care of landing the patch.

testHoodieAsyncClusteringJobWithScheduleAndExecute{String, HoodieRecordType}[1]
is known to be flaky.

Approved

@hudi-bot run azure


#33: allow to specify multiple strategy paths

So passing array of paths in compose.yaml does not throw error anymore
But it seems that it kind of breaks behavior of stragegies :

Before:

After:

should be OK now, forgot to mention path to paths change, but i reverted it.

Tested ok :ok_hand:


Add failure capture DDB Table and Lambda Handler

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

is it possible to get the fail_time in athena-views-pipeline/athena_views_pipeline/lambda_handlers/handler.py from the json itself instead ?

yes - I pushed a fix for this just now


dep: update libxml to 2.11.5 and libxslt to 1.1.39 (v1.15.x)

What problem is this PR intended to solve?
update libxml to 2.11.5 and libxslt to 1.1.39

https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.11.6
https://gitlab.gnome.org/GNOME/libxslt/-/releases/v1.1.39

I'd like to rebase once https://github.com/sparklemotion/nokogiri/pull/3028 is merged and backported


Travis Rebuild on HERMIT changes

Figure out how to force travis to rebuild when the hermit repo changes. HERMIT changes may break the build.

I'll set up the hermit travis build to clone hermit-shell and build it...

I've got the hermit-shell building, and running the shell tests (finally!).

For now, I've added a .hermit file, that contains the md5 of the latest HERMIT checkin. Edit this file is a cheap, but not automated, way to force a travis rebuild.

If you want to avoid having to make a repo change to trigger a build, there are two other ways I know of doing it:

From the GitHub repo, go to Settings > Webhooks & Services > Travis CI, then click the "Test service" button in the top-right corner.
You can use the travis.rb CLI app to restart the last build with travis restart.


Update ups rb file with one tag added called total packages in shipment

Written a remote UPS test case to check of the time_in_transit request was valid. Since the test was using multiple packages, test would fail if < TotalPackagesInShipment > {number} tag is missing from the request.

This looks like a duplicate of https://github.com/Shopify/active_shipping/pull/477, closing.


Check whether google analytics results contain sampled data

Had a preview issue where the summary of returned results don't match the google analytics web portal results. This is probably why.
Need to look at the top level element for "containsSampledData".
https://developers.google.com/analytics/devguides/reporting/core/v3/reference#sampling
in pandas.io.ga.GDataReader.get_data, there’s the _read nested function which contains a call to execute the query object from google’s library. Pandas is looking for the results in the ‘rows’ attribute, I bet containsSampledData is also in there.

closing as deprecating ga in #11308


Plans for on disk dataloaders?

Hi there,
I have been finding the requirement to have your whole dataset in memory a severe limitation for larger models. I'm wondering if you have any plans to implement a version of your dataset and dataloader classes that load from the disk instead of keeping them in memory?
Thanks!
Matthew

Hi @mtvector. Yes, we totally agree, just haven't gotten around to implementing that yet. Currently there is only this untested experimental branch that you can play around with if you like: https://github.com/Genentech/gReLU/blob/hdf5dataset/src/grelu/data/dataset.py#L1018

Thanks for sharing! I was feeling inspired so I took a first pass at a HDF5-backed BigWig dataset. I'll make a pull request so you can take a look.

cc @ekageyama


fix: typos and grammar mistakes

@zeertzjq can you please include in your typo PR?

OK

@dpelle its now part of #12753 but I saw you force-pushed another commit afterwards. Can you please check you latest changes are there?


[Coastal area scenario] Add ability to load bathymetry from standard file format

The following describes the problem with the current implementation of the coastal area scenario and the associated bathymetry class, as well as a tentative solution to solve this problem. I would like to collect feedback on this proposal before implementing anything. Thanks!
Problem
The current implementation of the coastal area scenario requires that the user loads a text file with a grid of depth values defining the bathymetry to be used in the simulation.
While this in theory allows the user to use different bathymetries in simulations, it is not practical, since bathymetry data from standard sources / file formats cannot be used.
The main challenge in a user workflow thus seems to be loading standard bathymetry data and converting it to a format that can be consumed by simulators such as SWASH and XBeach.
The challenges of loading standard bathymetry data are:

There is no single standard source / file format. There are centralized repositories for this data, e.g. European Marine Observation and Data Network  (EMODnet), which follows an European policy and thus has some level of control over the format in which bathymetry data is stored.
Bathymetry data is usually collected at a sample of locations that are not necessarily a) uniformly distributed in space, b) labeled with cartesian coordinates instead of latitude, longitude pairs, etc., as required by SWASH.

Tentative solution
Ideally, we would be able to load bathymetries, inspect them and pre-process them before they can be passed to a simulator.
File format
I suggest we start by adding support to bathymetries provided in the ASCII XYZ format defined here. This is a format provided in many of the datasets in EMODnet, see e.g. this data from Algarve.
Bathymetry class
Due to the different definition of the bathymetry data in typical sources (scattered vs grid values, etc.), our Bathymetry class needs to be updated.
I suggest we allow loading a bathymetry with "no further questions asked", i.e.
bathymetry = inductiva.....Bathymetry.from_ascii_xyz_file(file_path)

The Bathymety class should:

Store information as read from the file, i.e. a list of coordinates and corresponding depths, and not arbitrarily crop it/interpolate it to a grid.
Contain a visualization method that allows inspecting the loaded bathymetry.
Contain a cropping method that allows selecting only sub-regions.
Contain a method to interpolate data to a grid. The scenario class CoastalArea should inspect that the provided bathymetry is indeed defined on a grid.

User workflow
A typical user workflow should thus be:

Load the bathymetry

> bathymetry = inductiva.....Bathymetry.from_ascii_xyz_file(file_path)

Plot the bathymetry

> bathymetry.plot()

This should return a plot of the raw bathymetry, e.g. for the Algarve data mentioned above this would be similar to

Crop the bathymetry

> bathymetry = bathymetry.crop(x_range=[562000, 563000], y_range=[4102600, 4103500])
> bathymetry.plot()

Interpolate the bathymetry to a grid

> bathymetry = bathymetry.interpolate_to_grid(x_num=200, y_num=200)
> bathymetry.plot_grid() # or other name?

Simulate

> scenario = inductiva.....CoastalArea(bathymetry=bathymetry, ...)
> task = scenario.simulate()

Render simulation outputs

> output = task.get_output()
> output.render()

https://github.com/inductiva/inductiva/assets/11545632/62f67e7c-2928-4fc4-9060-2fb393ba627c

Thanks @fabiocruz for the detailed description. I think that this makes a lot of sense! Just one comment:
Why have both the bathymetry.plot_grid() and bathymetry.plot() method? Why not have just the bathymetry.plot() plot the grid directly. This seems like the most intuitive visualization for me. Am I missing something?

Cool, thanks Fábio, this seems reasonable overall. Related with @cristianacarpinteiro question/suggestion, which makes sense: before doing the simulation does the user necessarily have to call the interpolate_to_grid method? What happens if the user does not do that and passes a bathymetry that is not a regular grid? Were you planning to throw some error, or doing some interpolation with default values "automagically"?

Thanks @fabiocruz for the detailed description. I think that this makes a lot of sense! Just one comment: Why have both the bathymetry.plot_grid() and bathymetry.plot() method? Why not have just the bathymetry.plot() plot the grid directly. This seems like the most intuitive visualization for me. Am I missing something?

You're right. We should provide a single method to visualize bathymetries, regardless of them representing data in a uniform grid or not. I'll test matplotlib.pyplot.pcolormesh instead.


fix: upgrade to version 3.1.334

from: https://github.com/jenkins-x/jx-cli

/test bbc

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign abayer
You can assign the PR to them by writing /assign @abayer in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

bbc
bb5a3efd9483427aeba9967a1e8ebabf94ffb482
link
/test bbc

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

/override bbc

@jstrachan: Overrode contexts on behalf of jstrachan: bbc

In response to this:

/override bbc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.

/retest


Firefox last scroll pos

Hi guys,
recently I noticed that the last scroll position is not saved when reloading the page in Firefox. I searched the net but only found posts almost as old as me hehe....
Does anyone know why this happens?

It seems that this has something to do with smooth-scroll https://github.com/bootscore/bootscore/issues/51. Without this script, Firefox saves the scroll position on reload correctly. Check here https://dev.bootscore.me/2013/01/10/markup-image-alignment/

We'll fix this here https://github.com/bootscore/bootscore/issues/51


Improve code quality

Hey there! :wave:
Thank you for your contribution to PDFMaker! :tada: Let's make this PR awesome together!
What has changed? :pencil:
In this commit, I have improved the code quality by refactoring some functions, adding comments and documentation.
I have also added a few algorithms that enhance the functionality of the program.
Why this change? :thinking:
The code is now more readable, maintainable, and efficient.
Testing :test_tube:

[ ] I have tested the changes.
[ ] I have updated the documentation accordingly.

Screenshots :camera:
If applicable, add screenshots to help explain your changes.
Additional Information :bookmark:
I am from VIT too :grin:
Mention me under hacktoberfest label :)
Thank you for being a part of the ACM-VIT community! :heart:

Thank you for your contribution!