Feat: Add fbtftp to packages

Fbtftp contains official fbtftp files
Fbtftp_server contains server file and service file

I cab merge in a single rpm. However, since the spec file for python libs is auto-generated on the fly, I will need to insert the required files inside it. Also, it means that if I wish to update the server part, I will no more comply with original libs versions since I will need to increment version on my side.
This is why I preferred to keep 2 rpms, to be able to version and update freely the server side, while keeping versions sync with the fbtftp gitlab for the libs.

Added the requires in the spec and solved conflicts.


APEXMALHAR-2278 Implement KuduNonTransactional Output Operator

@tweise  / @PramodSSImmaneni  : Could you please review or suggest the right person who can complete this review for me?

Great to see this addition!
Package for this should probably be: org.apache.apex.malhar.contrib.kudu
I would suggest to send a separate email to dev@ summarizing the contribution and asking for reviewers.

@tweise - I shall refactor to the above package structure, test it with the latest release and then send a mail to dev for feedback and subsequently review

@tushargosavi @bhupeshchawda can you help reviewing this PR?

@tweise  : Apologies I got side tracked due to other commitments.
Regarding the movement of the code to contrib/org/apache/apex package structure instead of the original contrib/com/datatorrrent/....., I see that this will be the only package sitting in that structure. I was wondering if org/apache/apex is the package structure going forward for all new additions ?
@tushargosavi / @bhupeshchawda  : I will send a summary and description of the implementation of this PR today to the dev mailing list.

@ananthc yes, that is the correct package structure. All new code needs to be added under org.apache.apex packages.

@tushargosavi / @bhupeshchawda : sent a description to the dev mailing list regarding the design. Please let me know if any changes are required for the design and I will resubmit the PR based on the inputs.

@ananthc I will start reviewing it.

@tushargosavi / @bhupeshchawda  - Worked on the review comments and addressed them accordingly.

LGTM , I will wait for @bhupeshchawda review before merge.

Can it be moved out of contrib to a separate module similar to kafka?

@vrozov : sure . @tweise suggested we have a different package structure under contrib (under the org/apache path).. Why was Kafka taken out of contrib and made separate ? ( My understanding was that we had multiple versions of the Kafka drivers that need to be colocated and hence moved out of contrib..) .. I can refactor if you think it should be out of contrib  as the dependencies do not seem to be that big at all to impact other modules...

@vrozov I would like such restructuring discussed and taken up separately. This PR has been open for a long time and it appears the original reviewers are quite happy with it.
I have my own thoughts on what should be a separate module, and there maturity of the operator, tests and documentation play in. That discussion goes beyond the Kudu operator.

@tweise I'd suggest that you initiate a discussion on dev@apex on the policy for new operators in the malhar main and contrib libraries. For this particular PR my concern is introducing a brand new operator with "org.apache.apex.malhar.contrib.kudu" package name. Having contrib in the name means that once an operator matures and is moved into a separate module, it's name will change affecting applications. Why not to mature an operator in a separate module?

@bhupeshchawda  : Are there any further code review comments that you would like to see in this operator ?

@ananthc Sorry for the delay. Will have a look today..

@bhupeshchawda : addressed the second set of review comments as well. Let me know if you think there is any more review comments that you think might need to be addressed.

@tweise : Could you please merge if you think it is ok ?

@ananthc Will wait for a couple of days before merging, to allow any other feedback from the community.

Wondering if this can be merged now since it has been 7 days since approved ?

@ananthc yes, please rebase and I will merge it.


Catch errors in callback functions

I'm not too sure how to best handle this issue, but a relatively simple solution is to change Callback to throw a Violation in case an error occurs while executing the callback.
Let me know!

Other possibility is to re throw other errors in both check functions so it bubbles up.

Hi @marcandre,
I just saw this PR today O_o.
This is a good idea, especially with the related Parsley issue. Thanks a lot!
Best

Cool. Let me know when you make a release for validator


[#15] PostgreSQL database and CI environment

[#15]

[x] Updates docs in all READMEs for how to run tests and lints for a particular service
[x] Adds a CI docker-compose to simplify running tests and lints
[x] Sets up a Docker network for ability to resolve hostnames across Docker containers
[x] Sets up a Docker volume for database persistence when Docker containers are teared down
[x] Creates a PostgreSQL database as a service provided by a container
[x] Develops a proof-of-concept for running queries against the database from the backend service while both are running in separate containers using docker-compose.

Will do. I'll start Prod configuration soon. I'll propose something, but I'll also speak with everyone on the team to determine the needs for the db for all services. It will give me a better idea of what is required.


Use a chunked byte buffer to hold page versions in in-memory layer.

Change the way the page versions are stored in an in-memory layer.
Instead of storing the original PageVersion structs, serialize them
into an expandable buffer. That has a couple of advantages: first, the
serialized form is more compact, which greatly reduces the memory
usage. Secondly, we can track the memory used more accurately.
This moves the serialization work from the checkpointer to the WAL
receiver. It also means that if a page in an in-memory layer is
accessed, it needs to be deserialized on the GetPage call. That's adds
a bit of latency, but it's not significant compared to the overhead of
replaying WAL records. The simpler memory accounting is worth it.
Per Konstantin's idea a long time ago.

This also paves the way to start using a buffer cache to hold the data in the in-memory layers, if we want to go down that route in the future. If we had a buffer cache, we could implement ChunkedBuffer so that it reserves pages from the buffer cache instead of allocating new chunks effectively with mallloc. We still couldn't evict individual pages from the buffer cache that are reserved for holding data that belongs to the in-memory layers, as you need to write out the whole layer at a time. But it might make it easier to track where the memory is spent, and perhaps share the cache with reading pages from on-disk layers.
We could also replace the ChunkedBuffer with a temporary file. That would allow the OS to swap out parts of the in-memory layers.
I don't think those follow-up ideas are worth pursuing right now. But serializing the page versions earlier like in this patch seems like a good idea.

That's adds a bit of latency, but it's not significant compared to the overhead of
replaying WAL records. The simpler memory accounting is worth it.

It seems to be not exactly true.
I did just simple readonly test:
\timing
create table t (i integer);
insert into t values (generate_series(1,100000));
do
$do$
begin
  for i in 1..1000 loop
    perform count(*) from t;
  end loop;
end
$do$;

Results:
main:                                78525,430 ms (01:18,525)
inmemory-layer-chunks: 100501,193 ms (01:40,501)
buffered_repository:          15880,336 ms (00:15,880)

Fair enough, the derialization overhead certainly shows up in that test. We should add a test like that to our performance test suite.
I'm surprised the buffered repository is doing so much better on that test. Looks like it's materializing the page versions more eagerly, but I thought it relied on a lazy checkpointer thread to do that, with a similar policy as 'main'. Can you comment on that?

As you can see on flamegraph, large percent of time is really spent in deserialization
chunked.zip

Yes, buffered repo is ~10 times faster. Mostly because of checkpoint policy: checkpointer thread materializes the recent versions of the pages. Please notice that checkpoint distance for chunked repository means different thing that for layered repo.  There is no need for chunked repo to delay materialization of recently updated records. Another criteria is used: size of deltas. If number of page updates is small, then there may be no sense to force materialization of the page, because its reconstruction (applying deltas) should not take a lot of time. So in layered repo "checkpoint distance" means minimal total size of wal records which should be applied. And by default it is zero. So materialization is not delayed.
Each second (checkpoint interval), checkpointer is activated, traverse whole repository and if there some not yet materialized pages, then them are reconstructed. As a result, get_page_at_lsn in this test doesn't need to perform page reconstruction itself and this is why result is ~10 times faster.
But I do not consider it is "unfair"competition. It is actually one of the key features of buffered repository:  it doesn't somehow restrict materialization speed. We can do checkpoints as frequent as we want, trying to choose right balance between extra storage on the disk and time get_page_at_lsn time.

Frankly speaking I a little bit confused by this PR.
One of the main problems of layered repo is that in-memory layers cannot be swapped to the disk. Original OOM problem was cause by too slow checkpointer which is not able to catch up with wal receviers and flush reconstructed pages to disk at the same speed.
So my first attempt to solve this problem was to split flushing layer to the disk from materialization. I have done several experiments:

When checkpointer just save in-mem layer as delta layer and GC thread does materialization.
When layer is flushed by main threads and checkointer does materialization.
Both approaches eliminates OOM (even without back pressure), show similar performance which is comparable with
original layered repo performance (which is faster at the beginning but then degrading). But looks like my assumption that writing to the disk under lock is acceptable was not correct.

But there is general problem: if we force flushing in-mem layers as delta layers, than number of layers (files) will be increased and we will spent time for recreation of in-mem layers on subsequent updates.
So the solution of the problem can be some buffered (chunked) storage for in-mem layers pages. Actually it eliminates difference between in-mem/on-disk layers. We have hybrid layer, some pages of which are in-memory, some on disk.
This is why when I see this PR, I suspect that it is something like this. But then I looked through the code and realized that it is completely not true.
We are not able to load chunks from the disk. We just move some work (serialization) from checkpointer to the main thread with obvious (negative)  impact on GetPage speed.
I do not understand how serialization of WAL records can significantly reduce size. The largest part of WALRecord is Bytes with wal record data. We receive wal record data from safekeeper, wrap it into WALRecord, then WALRecord inside PageVersion. Then we serialize it and write to chunk. It seems to be just useless job requiring copy of large amount of data (especially for FPI). It will be much more efficient and straightforward  to copy received WAL records (as byte array) directly to chunk bypassing all this intermediate Rust structures. But it requires signficant code rewriting...
As a result, we do not safe much space, we can not swap this chunks to the disk... We really get some better control on memory usage and may be slightly simplify work of checkpointer (but slowdown receiver and GetPage). Is that the goal we what to address with this PR?

Yes, buffered repo is ~10 times faster. Mostly because of checkpoint policy: checkpointer thread materializes the recent versions of the pages. Please notice that checkpoint distance for chunked repository means different thing than for layered repo. There is no need for chunked repo to delay materialization of recently updated records. Another criteria is used: size of deltas. If number of page updates is small, then there may be no sense to force materialization of the page, because its reconstruction (applying deltas) should not take a lot of time. So in buffered repo "checkpoint distance" means minimal total size of wal records which should be applied. And by default it is zero. So materialization is not delayed. Each second (checkpoint interval), checkpointer is activated, traverse whole repository and if there are some not yet materialized pages, then them are reconstructed. As a result, get_page_at_lsn in this test doesn't need to perform page reconstruction itself and this is why performance is ~10 times better.

Gotcha.

But I do not consider it as "unfair"competition. It is actually one of the key features of buffered repository: it doesn't somehow restrict materialization speed. We can do checkpoints as frequent as we want, trying to choose the right balance between extra storage on the disk and time of get_page_at_lsn time.

Yeah, it's not a bad bet to eagerly materialize the latest page version. Unless a new full-page image comes along later, you will need to apply the WAL record anyway.

Frankly speaking I a little bit confused by this PR. One of the main problems of layered repo is that in-memory layers cannot be swapped to the disk.

Debatable :-). I don't think that's a problem as such. But I agree that swapping in-memory layers to disk could help in some scenarios.

Original OOM problem was cause by too slow checkpointer which is not able to catch up with wal receviers and flush reconstructed pages to disk at the same speed.

Right. The OOM aspect of that has mostly been fixed now. The checkpointer is still slow, and materialization is still expensive, but it shouldn't lead to an OOM anymore.

But there is general problem: if we force flushing in-mem layers as delta layers, than number of layers (files) will be increased and we will spent time for recreation of in-mem layers on subsequent updates.

Agreed.

So the solution of the problem can be some buffered (chunked) storage for in-mem layers pages. Actually it eliminates difference between in-mem/on-disk layers. We have hybrid layer, some pages of which are in-memory, some on disk. This is why when I see this PR, I suspect that it is something like this. But then I looked through the code and realized that it is completely not true.

Right, no, this PR doesn't do anything like that. This just changes the in-memory format of the PageVersions in the in-memory layers.

We are not able to load chunks from the disk. We just move some work (serialization) from checkpointer to the main thread with obvious (negative) impact on GetPage speed.

Correct.

I do not understand how serialization of WAL records can significantly reduce size. The largest part of WALRecord is Bytes with wal record data. We receive wal record data from safekeeper, wrap it into WALRecord, then WALRecord inside PageVersion. Then we serialize it and write to chunk. It seems to be just useless job requiring copy of large amount of data (especially for FPI).

The in-memory PageVersion struct is pretty complicated and has a lot of overhead. Firstly, you have the malloc() overhead of each individual PageVersion. Depending the malloc() implementation, it will contain a length field at a minimum, and might waste some memory for padding or rounding up the allocation size to fit into a slightly larger "bin". Then there's the Bytes to hold the actual WAL record. It contains a 'len' field, a pointer to the actual data, and another pointer for "vtable". Those pointers and length fields add up, and are pretty significant if the record itself is small.

It will be much more efficient and straightforward to copy received WAL records (as byte array) directly to chunk bypassing all this intermediate Rust structures. But it requires signficant code rewriting...

Well, you need to decode the records to figure out what to do with them. Hard to avoid having intermediate Rust structures for that. But sure, I'm all ears for optimizing that.
I suspect we could make the serialization/deserialization faster by writing the serialization routines by hand, instead of relying on serde. Serde is handy and nice, but I suspect the compiler cannot fully eliminate the overhead of its generic approach.

As a result, we do not safe much space, we can not swap this chunks to the disk... We really get some better control on memory usage and may be slightly simplify work of checkpointer (but slowdown receiver and GetPage). Is that the goal we what to address with this PR?

The goal is to reduce the memory usage, and make the accounting of how much memory is used more accurate.

Yeah, it's not a bad bet to eagerly materialize the latest page version. Unless a new full-page image comes along later, you will need to apply the WAL record anyway.

Yes, but please notice that we do not update pages in-place. So when we materialize page, then we need to append it to the storage. If we materialize page after each updated, then N 50-bytes updates, cause storing N*8k data on the disk. We loose disk space and consume IO throughput. It will be nice if we can keep materialized page in memory without saving it to the disk. But neither layered repo, neither buffered repo currently allows it.

On 3 November 2021 15:44:51 EET, Konstantin Knizhnik @.***> wrote:

Yeah, it's not a bad bet to eagerly materialize the latest page version. Unless a new full-page image comes along later, you will need to apply the WAL record anyway.

Yes, but please notice that we do not update pages in-place. So when we materialize page, then we need to append it to the storage. If we materialize page after each updated, then N 50-bytes updates, cause storing N*8k data on the disk. We loose disk space and consume IO throughput. It will be nice if we can keep materialized page in memory without saving it to the disk. But neither layered repo, neither buffered repo currently allows it.

Yeah. We could implement a page cache of materialized page versions. I'm thinking of a simple fixed size area with lru or clock replacement algorithm. That could be implemented as a separate component and glued on top of the layered (or buffered) repo implementation.
I'm not sure how useful that is if we implement a bigger cache in the compute node. But it would be pretty straightforward to do and pretty isolated from the rest of the system, so we could just implement it and see how it works, and drop it later if it becomes obsolete.

On 03/11/2021 15:56, Konstantin Knizhnik wrote:

Those pointers and length fields add up, and are pretty significant
if the record itself is small.

As I can see from the pg_waldump, on pgbench workload most frequent
record size is 83 bytes for insert, 82 for hot update and 34 for COMMIT.
So extra pointers and malloc overhead adds not such much to it. At least
it will not help reduce memory footprint let's say twice.

Hmm. 2 extra pointers would be 16 extra bytes, which is 20% of 83 bytes.
Plus other overhead. I could easily imagine it being up to 50% overhead.
But maybe there is more to this than just the pointer and malloc
overhead. Bytes uses reference-counting to allow multiple Bytes pointing
at the same backing store, so maybe the WAL record  Bytes points to the
original buffer that held the incoming WAL, and prevents it from being
removed? Or something like that.

Also, as you can check, malloc is still at one of the top places in
profile with inmemory-layer-chunks branch.
No? I don't see malloc being significant anymore. Can you share the
profile you're seeing?

And why chunk size is so small? Why don't you want to use Mb or even
larger chunks?
It should reduce malloc overhead and improve access locality.

Yeah, 1 kB was just a guess. Maybe it should be 4 kB or 8 kB or 1 MB, I
don't know. The obvious downside of a larger chunk size is that if you
only have one record in that 1 MB chunk, you waste a lot of memory. You
could use different-sized chunks too, but that makes the code a bit more
complicated.

Heikki

Hmm. 2 extra pointers would be 16 extra bytes, which is 20% of 83 bytes. Plus other overhead. I could easily imagine it being up to 50% overhead. But maybe there is more to this than just the pointer and malloc overhead. Bytes uses reference-counting to allow multiple Bytes pointing at the same backing store, so maybe the WAL record Bytes points to the original buffer that held the incoming WAL, and prevents it from being removed? Or something like that.

On latest CI run on 'main':
test_bulk_insert.peak_mem: 427 MB

On this PR:
test_bulk_insert.peak_mem: 315 MB

So about 28% reduction in memory usage. That seems like a plausible gain just from reducing the pointer and malloc overhead, actually.

This was superseded by #864, closing.


dns-overview.css color theme fixes for Cicada/Vicuna

by the way......for the dns-unbound reporting html basic structure the color "white" was written hardcoded. the color is defined differently in each theme and is already defined in the main.css. I would ask you to remove this hardcoded part so that the colors of the themes can be used again. the part I mentioned is here. see the screenshot

@opnsenseuser The color value prevents a weird looking border at the top of the context box, I'll move it to the main dns-overview.css file if this suits your need.
Thanks for the great work :)

@swhite2 thx for yout support. maybe this is a problem you can also fix?
if you call up the unbound dns reporting, the height or distances in the sidebar menu entries will change
when unbound reporting is not opened

when unbound reporting is opened

@opnsenseuser Nice catch, both points should be fixed with https://github.com/opnsense/core/commit/75807588ed28316f8c77a5e3c8ef3e4550e7e500

really great work. thx very much!! :-) 👍

@AdSchellevis can you approve the update for me? Are just color adjustments for the unbound DNS reporting anyway. Hope the .css also automatically overwrites the original dns-overview.css. That would be important for the color adjustment of the themes. Thank you

@opnsenseuser this file should be "theme sensitive" indeed. pulling it in for the next release. Thanks!

@swhite2
Hello
I noticed that you stored the wrong class name in the HTML structure. It is correct in the dns-overview.css, but it is not displayed correctly because the class in the HTML code is incorrect. see screenshot
Regards René

@swhite2 i think "danger" is also the wrong class. it doesn´t match with the css file

@opnsenseuser
Hi René, apologies for the late reply.
This has actually been done intentionally to map to bootstrap default colors, as is the case for status mappings in the bootgrid plugin: http://www.jquery-bootgrid.com/Documentation#statusmappings.
This happens here: https://github.com/opnsense/core/blob/master/src/opnsense/mvc/app/views/OPNsense/Unbound/overview.volt#L666-L669
We can of course just override this, no problem. I'll insert the original hardcoded Bootstrap color values in the css file.
Thanks!


Export project dialog initial path is now set correctly

Fixes #31427. (I think)

Due to just saving specifically the export path as relative, we must convert it back to an absolute path before calling set_current_path on the export_project variable, otherwise it'll be set to the res:// path.

I don't really like the amount of code this is adding, especially to String.
This issue is starting to get too complex for the simple purpose of saving one single path as relative, I'll see if I can figure out a cleaner way to do it (not saying that this isn't the right solution, but it doesn't feel right, so I want to investigate before merging).

Superseded by #34348.


PI extension with PyMoDAQ4

We are using a PID extensions with pymodaq 4. The model is intialized properly, but when intializing the PID we get the following errors
Traceback (most recent call last):
File "C:\Users\manip-lumi\Documents\GitHub\PyMoDAQ2\src\pymodaq\extensions\pid\pid_controller.py", line 161, in process_output
self.output_viewer.show_data([[dat] for dat in datas['output']])
File "C:\Users\manip-lumi\Documents\GitHub\PyMoDAQ2\src\pymodaq\utils\plotting\data_viewers\viewer.py", line 318, in show_data
if len(data.shape) > 4:
AttributeError: 'list' object has no attribute 'shape'
It is related to the modification of the dat structures in pymodaq 4.

In pymodaq.extensions.pid.pid_controller
we have replaced the line 160:
self.output_viewer.show_data([[dat] for dat in datas['output']])
by
data=DataRaw(name='pid output'
data=datas['output'])
self.output_viewer.show_data(data)
We got the following errors:
Traceback (most recent call last):
File "C:\Users\manip-lumi\Documents\GitHub\PyMoDAQ2\src\pymodaq\extensions\pid\pid_controller.py", line 162, in process_output
data=DataRaw(name='pid output',data=datas['output'])
File "C:\Users\manip-lumi\Documents\GitHub\PyMoDAQ2\src\pymodaq\utils\data.py", line 1484, in init
super().init(*args, source=DataSource['raw'], **kwargs)
File "C:\Users\manip-lumi\Documents\GitHub\PyMoDAQ2\src\pymodaq\utils\data.py", line 1179, in init
super().init(*args, **kwargs)
File "C:\Users\manip-lumi\Documents\GitHub\PyMoDAQ2\src\pymodaq\utils\data.py", line 490, in init
self.data = data  # dim consistency is actually checked within the setter method
File "C:\Users\manip-lumi\Documents\GitHub\PyMoDAQ2\src\pymodaq\utils\data.py", line 748, in data
data = self._check_data_type(data)
File "C:\Users\manip-lumi\Documents\GitHub\PyMoDAQ2\src\pymodaq\utils\data.py", line 702, in _check_data_type
raise TypeError(f'Data should be an non-empty list of non-empty numpy arrays')
TypeError: Data should be an non-empty list of non-empty numpy arrays

Hi Jérémie,
For now the PID extension in not compatible with the v4.
I would recommand that you keep the v3 for now.
It is planned to make it compatible but difficult to fix the date of the release.
I will keep you updated!

the new pull request #148 should solve this issue!

Could either Jérémie or Quantuum try this and let us know if it is working properly now?

PID extension is working well!


Add: WIPM-DT1

Channel Name
WIPM-DT1
Alternative Names (optional)
No response
Network (optional)
PBS
Owners (optional)
Puerto Rico Public Broadcasting Corporation
Country
PR
Subdivision (optional)
No response
City (optional)
Mayaguez
Broadcast Area
c/PR
Languages
spa
Categories (optional)
education
NSFW
FALSE
Launched (optional)
1961-01-01
Closed (optional)
No response
Replaced By (optional)
No response
Website (optional)
https://publicfiles.fcc.gov/tv-profile/WIPM-TV
Logo
https://i.imgur.com/GnKg53z.png
Notes
No response

Please update your request:

the logo link is geoblocked

https://github.com/iptv-org/database/blob/master/CONTRIBUTING.md#channels

Image changed.


Fix: Godot 4.0.1+ Plugin loading

This is a fix for #12
Godot plugin loading seems to fail on addon directories that are case sensitive.

It might be worth opening an issue on the Godot repo since case-sensitive names seemed to work in the past. What platform are you on by the way? I feel like Windows should definitely support case-sensitive names, but I'm not too sure about Linux.


ExecuteCommandAsync method is not getting invoked.

I updated my Visual Studio 2022 copy to the latest Preview 2.

I have pasted the Copy Info output at the end. Pls scroll down.
Earlier in Preview 1, I raised this bug
That bug now in Preview 2 seems to got resolved. I no longer get that exception.
Now when I run application and invoke the command, as per my understanding, the following method must be executed.
But its not happening. So I dont see any prompt or message box to show that this method is executed.
public override async Task ExecuteCommandAsync(IClientContext context, CancellationToken cancellationToken)
{
    await context.ShowPromptAsync("Hello from an extension!", PromptOptions.OK, cancellationToken);
}

What am I missing?
If I place a break point in InitializeAsync() method, I see that this is executed. But nothing happens there after.
public override Task InitializeAsync(CancellationToken cancellationToken)
{
    // Use InitializeAsync for any one-time setup or initialization.
    return base.InitializeAsync(cancellationToken);
}

The full details of the Visual Studio I obtained by clicking the Copy Info button in the Help About is as follows.

Microsoft Visual Studio Professional 2022
Version 17.8.0 Preview 2.0
VisualStudio.17.Preview/17.8.0-pre.2.0+34112.27
Microsoft .NET Framework
Version 4.8.04084
Installed Version: Professional
ASP.NET and Web Tools   <IP_ADDRESS>92
ASP.NET and Web Tools
Azure App Service Tools v3.0.0   <IP_ADDRESS>92
Azure App Service Tools v3.0.0
C# Tools   4.8.0-2.23429.7+44555193fd1135b5d53a2099f76fec91e0d1ebde
C# components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.
Microsoft JVM Debugger   1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines
NuGet Package Manager   6.8.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit https://docs.nuget.org/
Syntax Visualizer   1.0
An extension for visualizing Roslyn SyntaxTrees.
TypeScript Tools   17.0.20830.2001
TypeScript Tools for Microsoft Visual Studio
Visual Basic Tools   4.8.0-2.23429.7+44555193fd1135b5d53a2099f76fec91e0d1ebde
Visual Basic components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.
Visual F# Tools   17.8.0-beta.23425.10+0d3549fa5b8b6387ade191d76768405cefed8229
Microsoft Visual F# Tools
Visual Studio IntelliCode   2.2
AI-assisted development for Visual Studio.

I did a quick test with VS 2022 17.8 Preview 2 and I was able to run a command as well as hit breakpoints during command executions.
Please update the PackageReference version for the Microsoft.VisualStudio.Extensibility.* packages to 17.8.1024-preview-2 (the version that matches VS 2022 17.8 Preview 2).
Also, update the extension https://marketplace.visualstudio.com/items?itemName=vsext.gladstone to the latest version.


Add logging through Monolog package

Add support for logging through Monolog.
Currently the debugging only supports echoing (for CLI). If this uses Monolog, then it could log to a file, Discord, or anything really.

Closing to archive this repository.


Merging year in review 2016 theme

Coverage decreased (-0.5%) to 64.74% when pulling 235961a1b306c672a10998494e77271d74e09ed7 on master into b99620a130ed03b591e8723e7186050ce918cd47 on production.


port changes back to 19132 regardless of set values

If I change the port in the docker compose file and in server.properties, it gets changed back to 19132 when the server starts. Is this by design? My ISP has 19132 locked so I need to use a different one.

Please provide compose file that you tried. Also, keep in mind that the port mapping is what matters more where the left hand value of the mapping, "host_port", can be whatever value you want
host_port:19132/udp


DotNetNuke.Abstractions.Prompt.ICommand Naming Conflict with System Library

Description of bug
The DotNetNuke.Abstractions.Prompt.ICommand interface in the abstractions project creates a naming conflict with a system library in .NET. System.Windows.Input.ICommand is in the dotnet/runtime and has been for a long time since .NET Framework. It is commonly used in MVVM applications. It is something that may be useful in MVC or future Razor Pages, etc style projects that want to implement MVVM architecture. This naming conflict will require using aliases as a workaround.
This may not be a common scenario in DNN extensions, but I wanted to call it to attention.
Steps to reproduce
N/A
Current behavior
Naming conflict with system interface
Expected behavior
Use a different name other than ICommand
Screenshots
N/A
Error information
N/A
Additional context
This very well could be marked 'as designed' and 'wont fix'. I don't think we should have specialized classes have the exact same name as a system class. It will generate confusion amongst developers that are contributing to the platform or building extensions.
Affected version
latest
Affected browser
N/A

Great catch.

This should probably be pinned as it creates a conflict with the BCL

Done
You have any example of Alias usage, I am curious how that works ?

Aliasing in C# allows you to use multiple objects in the same file with the same name. For example if you wanted to use the DNN ICommand and the BCL ICommand in the same file you would need to do something like this
// This is the namespace where ICommand exists in the BCL
using System.Windows.Input;

// Since there is a name conflict this alias statement allows this code file
// to use `IDnnICommand which maps to DotNetNuke.Abstractions.Prompt.ICommand
using IDnnICommand = DotNetNuke.Abstractions.Prompt.ICommand;

namespace MyProject
{
    public class CommandExample
    {
        // This is the standard System.Windows.Input.ICommand
        public ICommand Command { get; }

        // This is the DNN ICommand using the alias
        public IDnnCommand DnnCommand { get; }
    }
}

Oh got it :) Thanks for the example


Inner/outer join of DataFrame.

It is impossible to inner/outer-join DataFrames (like this: Set logic on the other axes).

I'm sorry, I figured out how to perform join 😅 .


Attempting to remove symlink eval

After doing some more reading and experimenting it look like the symlink sorting and verification that was added to clear CodeQL was not necessary and I can still clear CodeQL without any of that additional work. This also puts us extremely close to our original relatively flexible behavior.
Resolves #161
Checklist

[x] I have viewed, signed, and submitted the Contributor License Agreement.
[x] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[x] I have added an integration test, if necessary.
[x] I have reviewed the styleguide for guidance on my code quality.
[x] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

@ryanmoran @sophiewigmore I now have it in a failing state that I believe should succeed based on my understanding the vulnerability. If you could advise on what change I made that re-introduced the symlink zip slip I would very much appreciate.

@ForestEckhardt in relation to @arjun024 comment on https://github.com/paketo-buildpacks/packit/issues/161, could you work with him to repro the issue he mentioned and verify that these changes fix that issue?

@sophiewigmore I think that I will only be able to get a meaningful fix out once I understand what is required to pass the scanning for zip slipping. Until then there is not anything super meaningful that can be done.

The more I read about the symbolic zip slip check the more it sounds like it wants all file that are written and linked to, to be part of the destination directory. If this turns out to be the case I believe that case is unworkable as there are some archives that make symlinks to files on the operating system (see php-dist). I would love to be proved wrong about this but I am cynical. If this is not a workable idea how should we proceed forward?

My reading of the zipslip vulnerability description is also that mitigation requires a check to ensure all files, symlinks, and symlink targets a within the destination when unarchiving. This would mean that the current implementation should also be doing a check after evaluating the symlink to ensure that the target is within the destination directory.
For the case of php-dist, I believe that the current archive file is incorrectly, and therefore unsafely, packaged. We should be using the --dereference flag to be creating truly portable archives, but it appears that we are not.

The inclination seems to be to close so I will close for now but leave the branch up for a while


 But you'll losse all the infos.
or, like some chat mods do, display the death once and add a little counter to it (like on the picture where I spammed "t" 4 times)
Sadly I haven't found one of these mods working with your mod.

Can you say the chat mods that do this text compression so I can take a look?

Yep, there is Chat Patches (but turned out the compression thing doesn't work at all for me in 1.20.1, I haven't tested in .4 or else that seems to have got an update for this matter.
Compat chat also didin't work for you mod's messages, but after I opened this issue I came around Chatutils wich does compact the death messages :)
Still think it could be a cool feature directly from your mod :)
Main benefit beiing that you don't get randomly a big list of stupid squids covering half the screen :p

Oh, so it does compact. I thought I wouldn't "stack" for the same reason as beehives, since while the text is the same, they have that hover event with the entity UUID.
I'm now making a mod for Modfest, so I'll only look at it later


Moving cognitiveservices (1) resource to v1beta1 version

Moving 1 resource to v1beta1 version

[ ] azurerm_cognitive_account_customer_managed_key

azurerm_cognitive_account_customer_managed_key requires Azure Support Form request:


Resource Forecast - Work name replacing Project name

#1686

Display work name instead of project name in resource forecast report

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (develop@a7b9862). Click here to learn what that means.

Additional details and impacted files
@@            Coverage Diff             @@
##             develop    #1694   +/-   ##
==========================================
  Coverage           ?   62.97%
==========================================
  Files              ?      248
  Lines              ?     8265
  Branches           ?        0
==========================================
  Hits               ?     5205
  Misses             ?     3060
  Partials           ?        0

Flag
Coverage Δ

epictrack-api
62.97% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[Enhancement] Add notifyLast for PopLongPollingService

Before Creating the Enhancement Request

[X] I have confirmed that this should be classified as an enhancement rather than a bug/feature.

Summary
Add notifyLast for PopLongPollingService
Motivation
To notify a newer request to prevent notifying an invalidate request.
Describe the Solution You'd Like
Add notifyLast for PopLongPollingService
Describe Alternatives You've Considered
No
Additional Context
No response

/assign


Samsung Note3 5.0 cannot display image

view.setImage(ImageSource.resource(R.drawable.ic_map));
cannot display out on Samsung Note 3 android 5.0
other phone no problem

Also can't display on Infinix Zero 5 model X603 with android version 7.0

I need to set error and placeholder image for SubSamplingScaleImageView when loading an image from the server. There is no problem when load success, because set image via bitmap. For placeholder and error, I have to use image resource, so for a workaround, I have to use 1 more ImageView to set image resource.

With the issue template deleted, and the image, layout etc. not provided there is not enough information to reproduce this issue. Make sure the image is in drawable-nodpi or put it in assets instead.


pageserver: compaction racing with archival config can leave Timeline stuck in Stopping.

via INC-357.

Compaction races with modifying the timeline's archival config.
offload_timeline gets called for a timeline that was recently archived, errors out if the timeline isn't archived.  However, by that point it has already called DeleteTimelineFlow::prepare, which puts the timeline into Stopping state.
So that's how it's stuck right now: the Timeline exists but is in Stopping state.

I think that moving the timeline out from a Stopping state would not be good. I.e. Stopping should be an irreversible path to walk. Otherwise we'd have to implement a "initialization light" operation, and think about how all the different timeline components deal with initialization.
So more or less, what should happen is that once the timeline is in Stopping state, we should be completing the offload operation, and then unoffload it when the archival config request is retried. As the offload operation is triggered by the compaction task, we'll need some mechanism that continues the offload once that errors out: it's untenable to error on all archival config requests until compaction gets to the timeline again.
Actionable items:

We need some thread-safe switch that both timeline offloading and timeline need to flip to "their" direction so that there is no race going on. This would fix the bug at hand. For offloading, it could be a flag in the Stopping state maybe, as well as a new IsUnarchiving state, idk. Or we add it somewhere to the upload queue and have it live under its locks, idk.
We should also think about retries of offloading (issued by compaction). if it fails, it might leave the timeline in a stopping state, so waiting until the compaction loop gets to it again isn't good. Maybe we should spawn a task that retries indefinitely? Or have the compaction loop just have a sub-loop that retries offloading until completion? What if it errors each time?
We should also think about retries of archival config: say a timeline gets put into IsUnarchiving state: is there some running task that ensures this runs to completion? Or do we want to be dependent on users to retry unarchival, and not just giving up eventually? I think latter is where we want to move deletion eventually, so we can probably just demand this for unarchival as well: if an unarchive operation is started, we expect it to be retried until completion.

think about retries of offloading (issued by compaction)

as the compaction loop is per-tenant, it's probably not a good idea to block compactions of other timelines on this. however, compaction doesn't sleep if there is still work left to do. so maybe if there is an error during offloading, we could retry in the next iteration.


WeakMap + HostObject === Sadness

let map = new WeakMap();
map.set(window.location, '1); // TypeError: WeakMap.prototype.set: 'key' is not an object

source: https://github.com/emberjs/ember.js/issues/15249
cc @jdalton / @nolanlawson

@stefanpenner Assuming your repro should have a string as the second param to set, I repro'd this issue.
let map = new WeakMap();
map.set(window.location, '1'); // TypeError: WeakMap.prototype.set: 'key' is not an object

However, this seems specific to window.location and thus is an Edge issue. Can you please reopen this as an Edge issue following the instructions here and post a link here to the issue you open so we can track it?

@tcare: @akroshg Believes this might be an issue that needs to be solved with a combined effort of Edge and Chakra.

@dilijev unfortunately I cannot file an issue, my microsoft account is in some strange state that wont let me log in :(.
I'll try to figure it out later this week...

No worries, I opened an issue on Edge: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/12112572/
FWIW you can also easily file an issue using #EdgeBug on Twitter: https://blogs.windows.com/msedgedev/2016/08/11/edgebug-twitter/

Thank you ❤ !


Fixed two typos in Azure Cli command.

Added missing dashes to command arguments.
MicrosoftDocs/azure-docs#77956

Thank you! #sign-off


Make Client Restoration ID Optional with Default Value

While this may cause problems in certain scenarios where our library is packaged with or used by another library, the most common intended case is that the client app is invoking the library for one type of client, in which case defaulting this value makes sense and reduces cognitive friction for the developer.

Addressed in #306


MRG, FIX: Fix labeling for broken raw

Why the data are nan is another issue, but at least raw.plot should not die with a cryptic message. We could perhaps also add a warning, this PR will make it so the user sees something like this, which pretty clearly indicates a problem (so maybe it's enough already):

Pushed a commit to deal with nan in autoscale, now we get:

Eventually we might want to add a check like this:
    if check_finite and not np.isfinite(x).all():
        warn('Non-finite (inf or NaN) found in data, these will spread '
             'when %s. Consider picking different channels, or Annotating '
             'segments as bad if working with raw data' % (kind,))

But it's non-trivial to do this in a way that is actually informative for the user. For example in #7576 we hit this during EDF channel resampling, and the user gets spammed with messages. So it should probably be a separate PR someday.

@agramfort this would be good to get into 0.20.1, too

backported


Response error with status code 503: Service Unavailable

Issue description
cant see my staking
Firefly version
1.3.0
OS details
os catalina
Can the issue be reliably reproduced?
No
Steps to reproduce the issue

...
Expected behaviour
a
Actual behaviour
a
Errors
No response

me too

Same here! No Connection to Tangle,Cafe, or Iota. Org Node possible!?!?!?

I have the same issue when I want to log in in my firefly wallet

seems its a network problem..................

same here!
error type Main unhandled promise rejection
clientError 'error sending request for url (https//chrysalis-nodes.iota.org/api/v1/info

i also cant re-add the Tangle node its thrown away by firefly.. "an error occured " -window occurs when i want to add the tangle node.

I'm also having the same problem to connect the firefly wallet...

is the staking still active even though I have this problem as well?

This is not a bug with firefly, the network is currently not issues new milestones. Please follow official IOTA channels to be notified when this issue is resolved. https://twitter.com/iota/status/1476126255506501632?s=20


internal/singleflight: delete, use golang.org/x/sync/singleflight

The singleflight package started life in internal/singleflight and then moved to golang.org/x/sync/singleflight, and the two have had slightly divergent development histories since. It's getting kinda messy. Their APIs have even somewhat diverged.
I just tried to re-unify them and delete internal/singleflight from std, but we can't use mod/vendor packages during bootstrap.
/cc @ianlancetaylor

Another step to re-unify them is:

Adding a new method to golang.org/x/sync/singleflight to report something like this https://github.com/golang/go/commit/6c877e5da7ab14f0d8a206c09f24cf51fbbc393a#diff-64cfc9b51215a4e84f98e7a67cfa800a

Change golang.org/x/sync/singleflight to behave the same as internal/singleflight.

I vote for 1st point, 2nd point will break current user of golang.org/x/sync/singleflight out there. How do you think @bradfitz ?

We can't break (change) the x/sync/singleflight public API.
We can add a new method, though.

If github.com/golang/sync another fork or is that just a clone of golang.org/x/sync? I've been unsure which should be imported.

@tarndt Use golang.org/x/sync, it's custom import path for github.com/golang/sync https://github.com/golang/sync/blob/master/singleflight/singleflight.go#L7

@cuonglm, rather than delete internal/singleflight, how about taking advantage of its private nature and give it generics like we did in our https://pkg.go.dev/tailscale.com/util/singleflight fork?
The std can use it with types instead of the any boxing.

@cuonglm, rather than delete internal/singleflight, how about taking advantage of its private nature and give it generics like we did in our https://pkg.go.dev/tailscale.com/util/singleflight fork?
The std can use it with types instead of the any boxing.
(Unless you want to wait for https://github.com/golang/go/issues/53427; but that could be a long time)

That sounds interesting, but I think we still need to wait until we bump the bootstrap version to 1.18 at least, for supporting generic?
The main motivation is that we should unify them, so we need to maintain one version only.

That sounds interesting, but I think we still need to wait until we bump the bootstrap version to 1.18 at least, for supporting generic?

Ah never mind, we don't have to, since when singleflight is only used in std, not during bootstrap tools.

@bradfitz See CL 425187 for adding generic to singleflight. We can keep it then, until #53427 accepted.


Vulnerability roundup 112: wolfssl-5.0.0: 2 advisories [7.5]

search, files

[ ] CVE-2022-25640 CVSSv3=7.5 (nixos-21.11)
[ ] CVE-2022-25638 CVSSv3=6.5 (nixos-21.11)

CVE details
CVE-2022-25640
In wolfSSL before 5.2.0, a TLS 1.3 server cannot properly enforce a requirement for mutual authentication. A client can simply omit the certificate_verify message from the handshake, and never present a certificate.
CVE-2022-25638
In wolfSSL before 5.2.0, certificate validation may be bypassed during attempted authentication by a TLS 1.3 client to a TLS 1.3 server. This occurs when the sig_algo field differs between the certificate_verify message and the certificate message.

Scanned versions: nixos-21.11: efea022d6fe.
Cc @fabaff

Fixed in #161897 n'est ce pas?


Fixed metrics service selector and metrics service port name

Hi,
there is bug in metrics scrapping configuration:

Servicemonitor has invalid app label selector value - there must be metrics service app label value;
In Servicemonitor expected port name is infinispan-met, but in service it named as infinispan.

Have a look on fixes.

Thanks @dimitriin


(SDK-44) REVIEW ONLY: in which jean has questions

Creating this PR just for leaving comments

Perfect, @DavidS , this is very helpful. I've integrated your comments and will PR. Thank you!


Enhancement of Sneakers Page: Filters Section and Additional Listings

I have been working on enhancing the Sneakers page to improve user experience and product discoverability. These enhancements focus on two main areas:
1. Addition of a Filters Section:
This new feature will allow users to refine their search based on various parameters, making it easier to find the products they want. The filters have been designed to be user-friendly and intuitive.
2. Expanded Sneaker Catalog:
I have also added several new sneakers to the page to ensure a broader selection of products for users to browse. These new listings include all relevant product details, ensuring a consistent and appealing look for the page.
I have already completed the development work on these improvements and would be happy to raise a pull request for review once the issue is assigned to me.
I am a gssoc-ext and hacktoberfest contributor

Proceed!

Proceed!

Hii @hars-21
I've completed the enhancements for the Sneakers page, including adding a filter section and additional sneaker options.
Also, I noticed that the level label  has not yet been added to my issue. Could you please add it?
Thank you!


stable/rabitmq Health checks fails when management ui deploy with path_prefix

Describe the bug
Health checks on wrong URL if RabbitMQ deployed with path_prefix setting for management UI.
I'm deploying rabbit mq with a management prefix.
rabbitmq:
    extraConfiguration: |-
      management.path_prefix = /RabbitMQ

And and then making it available with a ingress rule on /RabbitMQ.
Why I am doing this?
I want RabbitMQ management to be available on the same URL as the app (and same port).
Im not using a URL rewrite as the URL rewrite with NGINX will URL decode and that causes in issue upstream. So not using a URL rewrite solves this problem, but the prefix must be used.
But with this setup, using the path_prefix, the api and health checks fail. If I disable them (by changing to "exit 0") then everything works fine.
Version of Helm and Kubernetes:
Client: 1.15.5
Server: 1.15.7
Which chart:
stable/rabbitmq
What happened:
RabbitMQ health checks keep failing and pod get restarted
What you expected to happen:
RabbitMQ health checks to be successful
How to reproduce it (as minimally and precisely as possible):
See above
Anything else we need to know:
I've already investigate why this fails, this is because the health check URL is called like this:
"rabbitmq-api-check "http://user:$RABBITMQ_PASSWORD@<IP_ADDRESS>:15672/api/healthchecks/node\" '{"status":"ok"}'"
But in my case the URL should have contained":15672**/RabbitMQ**/api/"
I've also investigate the HELM template and found that the file statefulset.yaml contains the following:
- rabbitmq-api-check "http://{{ .Values.rabbitmq.username }}:$RABBITMQ_PASSWORD@<IP_ADDRESS>:{{ .Values.service.managerPort }}/api/healthchecks/node" '{"status":"ok"}'
So it seams there is not way to insert the require prefix.
The above case is for the api-check but the case is the same for the health-check.

Hi,
Given the stable deprecation timeline, the Bitnami maintained RabbitMQ Helm chart is now located at bitnami/charts. Please visit the bitnami/charts GitHub repository to create Issues or PRs.
This is the PR with the deprecation changes: https://github.com/helm/charts/pull/21310, in the description you can find a link to another issue explaining more carefully the reasons and motivations behind this transition.


Failed to login into FusionSolarAPI

Since a few days ago I get the error message "Failed to login into FusionSolarAPI" when I try  to connect with Fusion Solar API.
The same python program has been running correctly before.
The program reads data each 15minutes, and makes a log_out before to exit.
I would like to know if it is any limitation in the number/frequency for the API connections,
I have read something about the captcha connection option, but I have not been able to install it.

It seems i have resolved the issue. I have updated from version  14 to 17 and added the field " huawei_subdomain" in the call to FusionSolarClient.


Distorted Pixel Art with frame animation on window resize

Godot version
4rc5
System information
Windows 10, Vulkan, GTX1060 6GB
Issue description
Distorted pixel art - mostly visible on character eyes [with "keep-width" the eyes pop like 3 times the size, on simple "keep" they jump between what appears like 1.5 and .5 pixels] when window is resized to full screen. Viewport V and H are 640x360, Mode: Viewport, Aspect: Keep, Scale 1 int. Did not happen in Godot3, with pixel snap enabled. Both pixel snap options in Godot4 fail to fix it, AND add heavy jitter when moving diagonally. Clean project, with a tilemap, a sprite with animation frames and godot logo. Tried every option in project settings I could find.
Aspect: Keep / Keep height:

Aspect: Keep Width:

It looks like the scale would not stay at a full integer, and instead go into an f, or might be a problem on my end - please advise.
Steps to reproduce
Change the window size / maximize the minimal reproduction project
Minimal reproduction project
Minimal.zip

Duplicate of https://github.com/godotengine/godot-proposals/issues/1666.

This is due to uneven pixel scaling. The pixel snap project settings are not expected to fix this.


feat(bsky): update selectors for current version

light mode is mainly untested/untouched, not fully finished yet
may have some issues because i changed a couple things quite a bit
i also want to restructure some parts of the style, but i might do that in another PR
🔧 What does this fix? 🔧
fixes some selectors for the current bluesky web app as i haven't touched this style in like, 6 months oops lol
(mostly buttons, backgrounds, etc being broken, and a lot of selectors no longer matching anything at all)
also themes direct messages now as those didn't exist when i last touched this style
🗒 Checklist 🗒

[x] I have read and followed Catppuccin's contributing guidelines.
[x] I have updated the version appropriately in the ==UserStyle== header of the catppuccin.user.css file.

that was actually already implemented, i just forgot to update the selector ^^

maybe bit off-topic, but can you squash merge from the command line so i can retain my commit signatures?


RVS json logging for iet,gst,pebb and corrections

Cleanup and remove redundant info from json logs generated.
Enable changes for pebb reporting

General comment - please check and correct the code indentation.

It smells that this is a good opportunity to apply "visitor pattern" here. Have you thought of it?

Wil take it up in next iteration. This was more of removing redundant items from reported json and adding changes to pebb


Object Editor shows two ERD tabs

System information:

Operating system (distribution) and version Win10
DBeaver version 7.2.1 EA
DBeaver SVG Extension	<IP_ADDRESS>008302047

Still can reproduce (  DBeaver	<IP_ADDRESS>009181031).
Steps:

Install DBeaver
Install SVG Extension <IP_ADDRESS>008302047

verified


Cfg missing during build script build

Crate name: proc-macro2
Old working build: https://docs.rs/crate/proc-macro2/1.0.4/builds/186665
Build failure link: https://docs.rs/crate/proc-macro2/1.0.6/builds/192719
Additional details:
With the switch to rustwide, it seems that --cfg entries from our [package.metadata.docs.rs] are no longer seen by our build script (but still present when building the crate), which causes the build to fail.
Notice how in the working 1.0.4 build the rustc invocation that builds build.rs has --cfg procmacro2_semver_exempt. From tracing through the types in the failing 1.0.6 build, I believe that failure could only happen if --cfg procmacro2_semver_exempt is set for the lib.rs rustc invocation but not for the build.rs rustc invocation.
Relevant part of Cargo.toml: https://github.com/alexcrichton/proc-macro2/blob/1.0.6/Cargo.toml#L18-L20
Diff between working build current failing build: https://github.com/alexcrichton/proc-macro2/compare/1.0.4...1.0.6
(no relevant changes on our end).

FYI @pietroalbini -- this was causing the failure you saw in https://github.com/rust-lang/docs.rs/issues/23#issuecomment-540228220.

@dtolnay it looks like this error started occurring after the switch to rustwide (https://github.com/rust-lang/docs.rs/pull/407). It's probably due to https://github.com/rust-lang/cargo/issues/4423 - as you can see in the build logs --target is set in the latest (broken) build, but not in the old one.

@dtolnay I don't think this is an issue with docs.rs.
https://github.com/alexcrichton/proc-macro2/pull/207

This was fixed in https://github.com/rust-lang/docs.rs/pull/491, 1.0.7 is live: https://docs.rs/crate/proc-macro2/1.0.7


Support replace operations with value of null

When setting a json field to null, the patch produces a replace operation like this:
{"op":"replace","path":"/test_int_ptr"}

with no value field.
Is there perhaps a configuration option to produce an operation with null/nil instead?
{"op":"replace","path":"/test_int_ptr",value:null}

Thank you.

Thanks for the quick turnaround!

@kingtaj I just realised that there's one case where the current implementation will fail to met the expected output once an operation is marshaled to JSON; when the value (which has type interface{}) is not nil but a typed-nil value (nil vs (*int)(nil) for example).

thanks, good catch

@kingtaj Updated the PR with a new commit, if you want to check it out!
I'm using unsafe to avoid reflect. One could check is reflect.ValueOf(o.Value).IsNil() is true, but that would require to ensure that the underlying type of o.Value is nill-able (map, slice, pointer or func/chan -- event tho the last two can be excluded since not supported by encoding/json).

👍 Nice! Yeah I didn't think you'd want to use reflect if it could be avoided.

@kingtaj Release with v0.3.0. Thanks again for the issue reporting.


Retire docker.io/istionightly

This is no longer actually published nightly, since we are off of circleci. As such, it has not been updated in 2 months

How about publishing it from cloud builder or similar ? Including variants
for deb, bionic ?
The purpose was to speed the build and have a set of common tools for
debug. And a common base.
On Fri, Aug 9, 2019, 18:14 John Howard<EMAIL_ADDRESS>wrote:

This is no longer actually published nightly, since we are off of
circleci. As such, it has not been updated in 2 months
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/16182?email_source=notifications&email_token=AAAUR2VPZBW255O3FVEFYLTQDYI53A5CNFSM4IKYHD7KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HEQGYAQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAUR2WU5E5CV56YELYTDJLQDYI53ANCNFSM4IKYHD7A
.

How does it speed up the build? we do the same thing now just in gcr.io/istio-testing as far as I know.
If you are talking about the base image I don't mean getting rid of that, I mean the repo that it is in

@sdake is working on our base image and making it updated in each release

I dont really know what i meant by retire it. We already don't publish to it. We should just not push more stuff there in the future


Fix timing mismatch issue for vkGetQueryPoolResults

The problem
Some timing mismatch issue was observed when playing back a particular title's trace. vkGetQueryPoolResults returned VK_NOT_READY at playback time, while it returned VK_SUCCESS at the capture time.
The solution
The commit adds changes to handle the timing difference between capture time and playback time.
Result
Tested the target title with the build of the pull request, it fixed this issue.

CI gfxreconstruct build # 4996 running.

CI gfxreconstruct build # 4996 passed.

This looks like you'd lose the timeout implemented in 75bc5b3. In order to keep that functionality, should this be converted to a time-based timeout?

Hi @bradgrantham, in the case mentioned in [75bc5b3], an infinite loop occurred in several D3D11 games running with DXVK. It seems that the query always returns VK_NOT_READY, indicating that an error has occurred prior to this call. It's possible that every following query for the same pool would also return VK_NOT_READY. Therefore, the time-based timeout value needs to be very short because it affects the frame rate.
Another approach is similar to the current vkGetFenceStatus handling. It uses command options --skip-get-fence-status or --skip-get-fence-ranges to skip the query. So, if there's no issue with vkGetFenceStatus, there's no timeout. If there's an issue with vkGetFenceStatus, the user can set the option to skip the call. We can implement the same handling, such as using --skip-get-querypool-results or --skip-get-querypool-results-ranges to skip the query for the case that an infinite loop occurred in a specific title. What do you think of this approach?

The issue was addressed in PR#


MUMUP-1615 : Create servlet container, create configurable rest containers

Creates servlet for /api

Created a REST type end point with {key}.json where key is a preconfigured endpoint service

Uses basic auth or no authentication

Added an example properties file, must rename to have it work (will be in overlay)

Changed new stuff to point at servlet for an example of how we can utilize this new service.

Note this will break the build as we will need an overlay with the endpoint.properties

:+1: Let's do this


VG RDF shell script does not support all vg.JSON possibilities

The jq script depends on all types of nodes being present. e.g. it fails on some of the test data json files when a path element in the JSON tree is missing.

Do you have an example of this?

from the test directory cyclic/all.json, mises a path element in the JSON tree. This is not supported by the conversion script.

This will be fixed with pull requests #171 #170


clamav-scan taskrun marked as succeeded, but in fact fails and extracting the image

While the build pipeline succeeds in konflux-ci, I found out that the clamav-scan taskrun fails
STEP-EXTRACT-AND-SCAN-IMAGE

Extracting image(s).
Running "oc image extract" on image of arch amd64
error: unable to extract layer sha256:8694db102e5bd27fa30106f87d5a0f0c5ccccac0e5cc38ba56080d7559377096 from quay.io/psturc_org/user-ns2/konflux-ci-upstream/konflux-ci-upstream@sha256:537a34c6d8f37a05f142bb8f35b740f01a55c68d25812442fc2385f05f81bb53: operation not permitted
Unexpected error: Script errored at command: oc image extract --registry-config ~/.docker/config.json $arch_imageanddigest --path="/:${destination}" --filter-by-os="linux/${arch}".

When I tried to run the oc image extract command locally it worked just fine:
❯ mkdir tmp
❯ oc image extract quay.io/psturc_org/user-ns2/konflux-ci-upstream/konflux-ci-upstream@sha256:537a34c6d8f37a05f142bb8f35b740f01a55c68d25812442fc2385f05f81bb53 --path /:tmp --filter-by-os="linux/amd64"
❯ ls tmp
bin           entrypoint.sh lib           media         proc          sbin          tmp
boot          etc           lib64         mnt           root          srv           usr
dev           home          lost+found    opt           run           sys           var

It doesn't block the build->test->release flow, just wondering if it's something we should investigate and potentially fix

Good catch. Looks like something we need to figure out.


C# Android export doesn't open on some devices, or does but has null refs that don't happen on desktop

Tested versions
Godot v4.2.1.stable.mono
System information
Godot v4.2.1.stable.mono - GLES3 (Compatibility)
Issue description
I have 2 android devices:
1 - Alcatel 1S (2019) – Android 9 - gsmarena link
2 - Samsung Galaxy A03 - Android 13 - gsmarena link
On device 1, the game simply doesn't open. Device logs here:
device logcat.txt
On device 2, the game does open, but logs are spammed with nullrefs that do not appear on desktop, and I have no idea where to even start:
device logcat samsung.txt
On device 1, it seems like the render view can't be created?
On device 2, It seems like exported nodes lose their reference somehow?
I am unable to pinpoint the problem. The game works on desktop as-is. In truth, these may be two separate issues, but considering I'm sharing my whole project here, I figured I'd turn this into 1 issue.
Steps to reproduce
Export the attached project to an Android device.
Minimal reproduction project (MRP)
I spent 4 hours trying to make MRPs but couldn't pinpoint the problem. Empty projects or projects with minimal code don't generate the issues I'm seeing, and so I'm dropping the entire project here so you can try it for yourself. Again, really sorry that this complicates debugging for you.
td.zip

I have .NET 8.0 installed, but may have installed older versions in the past. Considering the .csproj defines the .NET versions, I assume it will use the latest?

I have .NET 8.0 installed, but may have installed older versions in the past. Considering the .csproj defines the .NET versions, I assume it will use the latest?

yes indeed it uses the one in the .csproj , I would recommend dotnet 7 for android.

Sorry, to be clear: Android targets .NET 7.0 and iOS targets .NET 8.0 in the .csproj. I assume that installing .NET 8.0 also 'includes' .NET 7.0?

I think these are 2 separate issues:

In the log for device 1 I'm seeing The vulkan hardware level does not meet the minimum requirement: 1, try using the compatibility renderer. This would be unrelated to C#.
In the log for device 2, you are getting a NullReferenceException in Player._PhysicsProcess.

I see. I'll close this issue treating it like a user error.


bot working differently in apiai site and node sdk

Hi i have developed some bot, when i am calling from api.ai site it is working fine. But if i call it from node SDK it is not working incase of intents having fulfillments. i am getting default response for the same request.

Hi. @kkorada  Thank you for quick response. I've never done this but I'm getting help from the api.ai site.

I'm new as well. I am still on the tutorial api.ai and its very interesting
with assisted guidance. good luck @kkorada
On Apr 6, 2017 11:01 AM, "LethiousFeribial"<EMAIL_ADDRESS>wrote:

Hi. @kkorada Thank you for quick response. I've never done this but I'm
getting help from the api.ai site.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

i can confirm, that i'm getting the same response every time without variations... Can anyone help?


Small refactor of the documentation organization for better URLs

Before this PR, the URL of an autogenerated reference file from the codebase docstrings looked like _autosummary/manim.container.html. This PR changes it to reference/manim.container.html.
Before this PR, the URL of the installation instructions documents looked like installation/installation_win.html. This PR changes it to installation/win.html.
Before this PR, the URL of the installation index looked like installation/installation_index.html. This PR changes it to installation.html. And the same for examples and tutorials indices.

cc. @kolibril13 since he designed the original organization.


fix: dep update

BREAKING CHANGE: min node version now 18

:tada: This PR is included in version 5.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update gotham and arial fonts note

Changes

Gotham and Arial have been replaced by Montserrat and Arimo.

https://devforum.roblox.com/t/introducing-builder-font-deprecating-gotham-and-arial/2868222/372
Checks
By submitting your pull request for review, you agree to the following:

[x] This contribution was created in whole or in part by me, and I have the right to submit it under the terms of this repository's open source licenses.
[x] I understand and agree that this contribution and a record of it are public, maintained indefinitely, and may be redistributed under the terms of this repository's open source licenses.
[x] To the best of my knowledge, all proposed changes are accurate.

Will I be able to create a Roblox game
On Tue, Jun 18, 2024 at 5:00 PM haan-roblox @.***>
wrote:

Merged #639 https://github.com/Roblox/creator-docs/pull/639 into main.
—
Reply to this email directly, view it on GitHub
https://github.com/Roblox/creator-docs/pull/639#event-13206513965, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BJEXSSHIWWOLNOLJ7EOZSSDZICNXXAVCNFSM6AAAAABJQWIK2WVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTGIYDMNJRGM4TMNI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Add a copy-to-clipboard button to the export viewconf URL dialog

Because highlighting text and ctrl+c is just so laborious... ;)
Also, the viewconf URLs can be longer than the dialog box and it's easy to miss a few characters at the end by not dragging the cursor far enough... I've also found it easy to accidentally click somewhere outside the modal, which closes it before I manage to copy (that's probably a bug).

At least the text should be highlighted by default so that you only need to hit CTRL+C

Actually, having to click on a button or hitting CTRL+C is already waaay too much work. As a lazy person, I want to be spoon fed and have the link already be copied to the clipboard for me.


Proper error logging

Description
Proper error logging
Type of change

New feature (non-breaking change which adds functionality)

Testing steps
Done on CI
Checklist

[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary

Shouldn't it be unable instead of enable?

up, nice catch. Fixed


Cleaning up linter complaints + addressing "name" parameter issue

Finally getting my hands dirty with Rubocop and cleaning up new errors
that appeared after the last PR. Complexity linters are hard to address
currently, so some have been incremented in Rubocop's TODO file.
/CC @erjohnso

updated instance naming logic, fixing #82

Awesome, lgtm @Temikus!


Conflict with vuetify-loader

Thank you for looking at my issue! Now that I’m using version 1.1 (relates to #9), there’s now a conflict with vuetify-loader:
 error  in ./src/App.vue

Module parse failed: Identifier 'installComponents' has already been declared (28:7)
File was processed with these loaders:
 * ./node_modules/vuetify-loader/lib/loader.js
 * ./node_modules/cache-loader/dist/cjs.js
 * ./node_modules/vue-cli-plugin-import-components/dist/loader.js
 * ./node_modules/vue-loader/lib/index.js
 * ./node_modules/eslint-loader/index.js
You may need an additional loader to handle the result of these loaders.
|
| /* vuetify-loader */
> import installComponents from "!../node_modules/vuetify-loader/lib/runtime/installComponents.js"
| import { VApp } from 'vuetify/lib/components/VApp';

I think you can easily replicate this environment in a Vue CLI app by doing vue add vuetify.

Hey thanks for that, version 1.1.1 should have it sorted.


[Bug] EditingActions like Define Lookup are not shown.

Describe the bug
Tested with the TestApp on develop branch and 2.7.1 tag, Define and Lookup are not shown, And if you click on the share, App will crash.

How to reproduce?
1.Clone the repo
2.cd TestApp
3.make spm
4.Import a book and long press the text
Readium version
2.7.1-3.0.0-alpha.1
OS version
iOS 17.4-17.5
Testing device
iPhone 13 Pro Max
Environment
macOS: 14.5
platform: arm64
Xcode 15.4
Build version 15F31d

Additional context
No response

Thank you for reporting this issue, I fixed it in #447. I will publish a new 2.7.2 version.


Show node approval status in CLI

Shows the node approval status when running the node list command. This will currently show as APPROVED for requester nodes, and PENDING for compute nodes, but as these values are not currently used in filtering this is okay.  Once we start filtering nodes based on their approval status being APPROVED then we will need to decide on how we auto-approve compute nodes.
Also contains a couple of Printf's not caught in previous PR.

@coderabbitai review


Adding an example showing how to work with indicators inside the strategy file on a different time frames

It would be great if you could add one simple python example to show how to integrate an indicator inside the strategy file and make a trading decision based on that? Something similar to the existing Coin Flip Trader, but, incorporating at least one indicator operating on a , for instance, 15 min time frame ticker.
Very much appreciated for being such helpful

I would love that inorder to use zeromq_connector to code my strategies which involve indicators available in MT4

Hi,
generally there are two ways. Either you could calulate it in python from the price data you stored, for example using the resample function  on a pandas data frame.
Or you could do it in mql and pass the information via the socket connection similar to how it is done for example for DWX_GetOpenOrders().
However, this would be quite a lot of work. If a strategy is based mostly on technical indicators, I would highly recommend just to code it in mql4 and execute it directly in MT4.


The coverage directory is included in 0.17.1

The coverage directory is included in 0.17.1 https://registry.npmjs.org/http-proxy-middleware/-/http-proxy-middleware-0.17.1.tgz

Thanks for reporting it. I noticed this too.
It is already fixed in: https://github.com/chimurai/http-proxy-middleware/commit/f670d6e08a5ac378f96fa8ab755b11da8d490859
Haven't pushed a new version to make it effective.

I'd recommend to use the files option in package.json to whitelist what you want to include instead. This will probably happen again in the future when you add a new folder / change a folders name.

Thanks for the tip @SpaceK33z! Didn't know about files option.
Much nicer compared to .npmignore


As a user i wish to have colors help to indicate completed and overdue tasks

so that I can easily notice tasks that are done and overdue

Issue Completed


Feat: Gated SAEs, train SAEs on image patches only

🔥🔥🔥

Thank you! :)
Re jumprelu - @themachinefan has worked on the it, you should be seeing a PR for it sometime soon.


chore(main): release 0.9.2

:robot: I have created a release beep boop
0.9.2 (2024-09-07)
Bug Fixes

Revert "chore(main): release 0.9.1 (#23)" (#24) (331d505)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.9.2
:sunflower:


CCDB GE/002 - Section 1.4

Para 14
Comment:
This essentially repeats para 8.
Proposal:
Priority: 2

Duplicate of #16. This is the proper location for the information.


Misc Function fixes

Motivation
This pr does a couple of minor fixes

Collect input topics from the function details spec:- Currently source is referred before creating the context, while source creation itself needs the context. This circular dependency is removed by making context creation independent of source.
Catch all errors during source/sink close since its user code:- Sink/Source code is external/user code, thus any errors caught need to be caught.

Modifications
Describe the modifications you've done.
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change 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 deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API: (yes / no)
The schema: (yes / no / don't know)
The default values of configurations: (yes / no)
The wire protocol: (yes / no)
The rest endpoints: (yes / no)
The admin cli options: (yes / no)
Anything that affects deployment: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

run java8 tests

run java8 tests

Merged in 2.3.1 at
6e8320a


Proposal for Blockchain Explorer for Iroha

Signed-off-by: turuslan<EMAIL_ADDRESS>

Please update the labs short description; Think the first paragraph of the wiki page would be a good addition.
Please update the sponsor; Afaik "Hyperledger Internship project" does not qualify ;-)

On more general note and without knowing all the details it seems a shame (and wasted opportunity ?) to fork and make it incompatible... Isn't there a way to work with hyperledger/blockchain-explorer to at least have a path towards a common codebase ?

Like @trbs , I wonder why this is meant to be done as an incompatible change rather than an addition to Explorer. And I have to ask whether the Explorer team was contacted to see if this couldn't simply be done as part of Explorer rather than a lab.

I am not against forking HL-explorer to be an Iroha-explorer, if that is what you intended. However name, as well as sponsor needs to be changed also clear reference to previous repo. Maybe to satisfy the prior reviewers, you can also add rationale of why the Iroha-Explorer has to be labs .

FYI: HLExplorer was designed to support multiple blockchain platforms, you will need to add your implementation under the https://github.com/hyperledger/blockchain-explorer/tree/master/app/platform, define your DB models, create mapping between UI and DM model if some are not matching the DB endpoints, add starting scripts for your platform.

I haven't seen any response to @nfrunza 's comment which actually confirms my doubts about the approach. I would like this proposal to be abandoned and instead the effort to be redirected to contributing to the Explorer project.


cannot delete the comments

Hi i am Testing Portus Version: 2.1.0-dev i am unable to delete the comments . I am an Admin User . i am running with rack and rails env set to staging with compose setup.

Can you look into the rails logs and see if there's some exception being logged?

I see no Logs being Logged when i am clicking Delete

Which logs are you talking about: the one produced by the container or the Rails' logs?
We recently fixed the compose setup to ensure all the rails logs were sent to the stdout (and hence picked up by docker logs). Maybe you created your image before the fix was pushed to master...
The rails logs are under logs/development.log. You can try to get them via docker exec


[protocol] Deploy mainnet spoke connectors

Background
Deploy the wormhole connector for replacement.
Linked Issues & Documentation

#4538

Definition Of Done
Spoke and hub connectors are deployed and init'd/

deployed


Remove unused import in Button docs

Codecov Report

Merging #73 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #73   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          20     20
  Lines         232    232
  Branches       65     65
=====================================
  Hits          232    232

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 680bc6a...999a2d5. Read the comment docs.

Thank you, @wordofchristian.


Consistently use colons before code examples

We use colons directly before most code examples. This PR is being introduced in order use that format consistently across all code examples.

👍


Add babel-plugin-css-in-js

This is basically react-inline as a babel plugin. Now that v6 of babel supports plugin options, this can be directly integrated into babel's transformation pipeline.

Thank you very much @martinandert
I worked on a presentation about Inline Styles recently and I added react-inline as one of the best solutions: https://speakerdeck.com/michelebertoli/inline-styles?slide=24

@MicheleBertoli Thanks for accepting my PR.
Yeah, I already saw your slides and retweeted it back then.
With the advent of babel-plugin-css-in-js, react-inline is now kind of obsolete. I'm thinking about deprecating it in favor of the plugin.


add configurable toolbar fixes #1540

@bryon-czoch thanks, I'll check this soon 👍

👍

Released on v4.0.2, thanks again


⚠ ClamAV has degraded performance

In ab2ca87, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 84 ms

Resolved: ClamAV performance has improved in 512e603.


How can I make multiple sessions share a graph? Not found: Container localhost does not exist

How can I make multiple sessions share a graph by c_api?
My usage is as follows:
The first session is created using TF_LoadSessionFromSavedModel.
The second session is created using TF_NewSession.
It is normal to call the TF_SessionRun of the first session. However, when calling the TF_SessionRun of the second session from another thread, the following error is reported:
2021-08-19 14:56:00.772594: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at resource_variable_ops.cc:633 : Not found: Container localhost does not exist. (Could not find resource: localhost/embeddings/charactor_embeddings/weight)
{{function_node __inference__inference_5828_specialized_for_StatefulPartitionedCall_StatefulPartitionedCall_at_tf_graph}} {{function_node _inference__inference_5828_specialized_for_StatefulPartitionedCall_StatefulPartitionedCall_at_tf_graph}} Error while reading resource variable encoder/layer.0/attention/self/key/bias from Container: localhost. This could mean that the variable was uninitialized. Not found: Container localhost does not exist. (Could not find resource: localhost/encoder/layer.0/attention/self/key/bias)
[[{{node encoder/layer._0/attention/self/key/BiasAdd/ReadVariableOp}}]]
terminate called after throwing an instance of 'std::runtime_error'
what():  {{function_node __inference__inference_5828_specialized_for_StatefulPartitionedCall_StatefulPartitionedCall_at_tf_graph}} {{function_node _inference__inference_5828_specialized_for_StatefulPartitionedCall_StatefulPartitionedCall_at_tf_graph}} Error while reading resource variable encoder/layer.0/attention/self/key/bias from Container: localhost. This could mean that the variable was uninitialized. Not found: Container localhost does not exist. (Could not find resource: localhost/encoder/layer.0/attention/self/key/bias)
[[{{node encoder/layer._0/attention/self/key/BiasAdd/ReadVariableOp}}]]
[[StatefulPartitionedCall/StatefulPartitionedCall]]
[[StatefulPartitionedCall/StatefulPartitionedCall]]Aborted (core dumped)
Why? Usage problem or bug? We look forward to your reply.
System information
tensorflow version(2.3.0)
Linux Ubuntu 16.04
code snippet:
static pthread_mutex_t sSpeakerClassToGraphMutex = PTHREAD_MUTEX_INITIALIZER;
static std::map<const void*, const void*> sSpeakerClassToGraph;
Model::Model(const void* classID, const std::string& model_filename, const std::vector<uint8_t>& config_options) {
const char* v = TF_Version();
printf("Model********************************************************************** v(%s)\n", v);
    this->status = TF_NewStatus();
// Create the session.
TF_SessionOptions* sess_opts = TF_NewSessionOptions();

if (!config_options.empty())
{
	TF_SetConfig(sess_opts, static_cast<const void*>(config_options.data()), config_options.size(), this->status);
	this->status_check(true);
}

pthread_mutex_lock(&sSpeakerClassToGraphMutex);

 std::map<const void*, const void*>::const_iterator iter = sSpeakerClassToGraph.find(classID);
if (iter != sSpeakerClassToGraph.cend())
{
	this->graph = (TF_Graph* ) iter->second;
	printf("(%p, %p)\n", classID, this->graph);
	this->session =TF_NewSession(this->graph,sess_opts,status);
}
else
{
	this->graph = TF_NewGraph();
	TF_Buffer* RunOpts = NULL;
	const char* tags = "serve";
	int ntags = 1;
	this->session = TF_LoadSessionFromSavedModel(sess_opts, RunOpts, model_filename.c_str(), &tags, ntags, this->graph, NULL, this->status);
	sSpeakerClassToGraph[classID] = graph;
	printf("(%p, %p) create\n", classID, graph);
}
pthread_mutex_unlock(&sSpeakerClassToGraphMutex);
if (TF_GetCode(this->status) == TF_OK)
{
	printf("TF_LoadSessionFromSavedModel OK\n");
}
else
{
	printf("%s", TF_Message(this->status));
}
TF_DeleteSessionOptions(sess_opts);

// Check the status
this->status_check(true);

}

@hankewei ,
In order to expedite the trouble-shooting process, could you please provide the complete code and dataset to reproduce the issue reported here.Thanks!

Also please take a look at this issue with similiar error.It helps.Thanks


Trying to use this with Nuxt and have errors

There are number of errors I have in console:
e3-ace-editor.js:1109 Unable to infer path to ace from script src, use ace.config.set('basePath', 'path') to enable dynamic loading of modes and themes or with webpack use ace/webpack-resolver
r
caught SyntaxError: Unexpected token '<' (at VM3758 mode-html.js:1:1)
caught SyntaxError: Unexpected token '<' (at VM3759 theme-chrome.js:1:1)
caught Error: couldn't load module ace/theme/chrome or it didn't call define
t afterLoad (vue3-ace-editor.js:19101:1)
at vue3-ace-editor.js:1079:1
at Array.forEach ()
at vue3-ace-editor.js:1078:1
at vue3-ace-editor.js:1122:1
at _require (vue3-ace-editor.js:59:1)
at req (vue3-ace-editor.js:97:1)
at vue3-ace-editor.js:1121:1
at afterLoad (vue3-ace-editor.js:1074:1)
at s.onload.s.onreadystatechange (vue3-ace-editor.js:711:1)
Just followed basic instructions:
<template>
  <VAceEditor v-model="code" lang="html" :min-lines="10" />
</template>

<script lang="ts">
import { defineComponent } from 'vue'
import { VAceEditor } from 'vue3-ace-editor'

export default defineComponent({
  components: { VAceEditor },

  data: () => ({
    code: '',
  }),
})
</script>

You must import modes and themes yourself. See https://github.com/CarterLi/vue3-ace-editor#breaking-change

@CarterLi I see, that has to be in "How to use" section, otherwise people would assume that "How to use" instructions supposed to work as is.


Simplify Twitter Card Tags and Remove Unused Keywords Meta Tag

Enter your suggestions in details:
Issue Description
The current implementation of the metas.ts plugin in Lume includes unnecessary Twitter Card tags (twitter:*) even when OpenGraph tags (og:*) are present. Twitter provides fallback behavior for OpenGraph tags, which means that we don't need to duplicate our efforts by including both sets of tags.
Additionally, the keywords meta tag is no longer utilized by search engines for SEO purposes. Therefore, it can be safely removed to reduce output sizes and maintain consistent development practices.
Proposed Changes

Remove the twitter:title tag if og:title is present, optimizing the Twitter Card tags.
Simplify Twitter Card tags to include only twitter:site and twitter:card when og:* tags are present, eliminating redundant tags.
Consider removing the keywords meta tag as it is no longer effective for SEO, resulting in a cleaner codebase and reduced output size.

Additional Information

Twitter Card Markup Documentation provides details on Twitter's card markup requirements.
Getting Started with Twitter Cards offers guidance on implementing Twitter Cards effectively.
Social Media Meta Tags provides insights into best practices for social media meta tags.
Google's Statement on Keywords Meta Tag clarifies that Google does not use the keywords meta tag for ranking websites.
Twitter Confirmation on Keywords Meta Tag highlights that Twitter also does not use the keywords meta tag.

These changes will streamline the meta tag implementation, reduce redundancy, and ensure alignment with current SEO practices and social media card standards. 😄

I'm ok about removing redundant tags but not removing the keywords meta tag. This is not only about SEO, if users want to specify the keywords tag, they should be able to do.

So, going to create a PR!


[BUG] Scrolling issue in Media Details Page.

Summary:
Profile Page scrolling is not smooth.
Steps to reproduce:

Login to the app.
Open any courses and go to uploads section.
Try scrolling in the category section of the page.

Device and Android version:
Model No: Moto G5S+
Android version: 8.1.1
Would you like to work on the issue?
No

I would like to work on this issue

Sure, feel free to start working on it. send a PR once it's solved.
On Wed 2 Oct, 2019, 12:31 AM gconnect<EMAIL_ADDRESS>wrote:

I would like to work on this issue
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/WikiEducationFoundation/apps-android-wikiedudashboard/issues/57?email_source=notifications&email_token=AEVTAA7ASXDTNP4OQRMBY63QMONBJA5CNFSM4IYWYAVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEACL5SY#issuecomment-537181899,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEVTAA6QPXHC2AVNDY52PUTQMONBJANCNFSM4IYWYAVA
.

Please I sent you a mail to your personal mail<EMAIL_ADDRESS>I hope its correct?. I just got approval for the inital round of the Outreachy 2019. And I would like to contribute to the Wikimedia Education Dashoboard Project. I would need your mentorship guide. I followed you on twitter wanted to reach out to you but your private messaging is not accessible.
Here is my email<EMAIL_ADDRESS>Twitter : @agatevureglory
I would like to have the link to Wikimedia slack channel so I can join. Thanks.

Sure, feel free to start working on it. send a PR once it's solved.
…
On Wed 2 Oct, 2019, 12:31 AM gconnect, @.***> wrote: I would like to work on this issue — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#57?email_source=notifications&email_token=AEVTAA7ASXDTNP4OQRMBY63QMONBJA5CNFSM4IYWYAVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEACL5SY#issuecomment-537181899>, or mute the thread https://github.com/notifications/unsubscribe-auth/AEVTAA6QPXHC2AVNDY52PUTQMONBJANCNFSM4IYWYAVA .

I have asked Sage to send you an invite for Slack. Also, I am assigning this issue to you.

Okay thanks.
On Wed, Oct 2, 2019 at 11:47 AM Ujjwal Agrawal<EMAIL_ADDRESS>wrote:

Assigned #57
https://github.com/WikiEducationFoundation/apps-android-wikiedudashboard/issues/57
to @gconnect https://github.com/gconnect.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/WikiEducationFoundation/apps-android-wikiedudashboard/issues/57?email_source=notifications&email_token=AFPXA4BLEPVLFRS44UNBICTQMR337A5CNFSM4IYWYAVKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOT67ZVTI#event-2680134349,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFPXA4GNCWGOXY3DMJBGPDTQMR337ANCNFSM4IYWYAVA
.

I just made a pull request now.

Thanks @gconnect , I will review the PR soon.


FPGA: Add sample for max_reinvocation_delay attribute

Adding a New Sample(s)
Description
New sample demonstrates how and when to use the max_reinvocation_delay loop attribute.
Checklist
Administrative

[ ] Review sample design with the appropriate Domain Expert:
[ ] If you have any new dependencies/binaries, inform the oneAPI Code Samples Project Manager

Code Development

[ ] Implement coding guidelines and ensure code quality. see wiki for details
[ ] Adhere to readme template
[ ] Enforce format via clang-format config file
[ ] Adhere to sample.json specification. https://github.com/oneapi-src/oneAPI-samples/wiki/sample-json-specification
[ ] Ensure/create CI test configurations for sample (ciTests field) https://github.com/oneapi-src/oneAPI-samples/wiki/sample-json-ci-test-object
[ ] Run jsonlint on sample.json to verify json syntax. www.jsonlint.com

Security and Legal

[ ] OSPDT Approval (see Project Manager for assistance)
[ ] Compile using the following compiler flags and fix any warnings, the falgs are: "/Wall -Wformat-security -Werror=format-security"
[ ] Bandit Scans (Python only)
[ ] Virus scan

Review

[ ] Review DPC++ code with Paul Peterseon. (GitHub User: pmpeter1)
[ ] Review readme with Tom Lenth(@tomlenth) and/or Project Manager
[ ] Tested using Dev Cloud when applicable

@tomlenth and @pmpeter1 would be appreciated if you find the time to review this new FPGA code sample


Runtime Bug

Excellent project Leon!  While running the demos using existing images, computational flow seems to stop 2-3 layers before end.  I am running Firefox 49 on Mac OSX.
If you cannot replicate this, I can send you debug info from the console.
Great job again!

Thanks for the report. Firefox 49 in Ubuntu 14.04 and 16.04 work fine, but I just checked with Firefox 49 in OS X and am running into issues as well. Strange, will investigate.

Firefox on certain platforms (macOS in particular, possibly others) still has texture size limits hard-coded. Even on modern GPUs, this limit may be too low. This is a known issue. While Keras.js will gracefully downgrade to use the CPU in this case, computational performance will be degraded. One way to get around this is to go to about:config and change gfx.work-around-driver-bugs to false, and restart the browser. This should increase the max texture size back to normal.


Feature/external toolchain

#patch#

Changes Unknown when pulling d86abf9b107012092eb17412a37915617e447c8b on feature/external-toolchain into ** on master**.


Broken link on page about switching from GOV

Bug Report
The link with this link text: download the kit using the zip file or Github
on this page: https://prototype-kit.service-manual.nhs.uk/how-tos/switching-from-govuk-prototype-kit
I'm not sure what the fix should be.
Should it be 2 links? It says "or".
Thanks
Sara

Whoops good catch! I'll make this link to the advanced page on our guidance as I kinda want this page to be a reference to other things.


Dropdown menus should not be droppable

Expected Behavior
I think the menu should not be droppable (right, @carljbowman?)
Actual Behavior
Current 3.0 behaviour when combining unexpected inputs/ blocks - @ericrosenbaum & I were trying out the speech & wedo extensions and noticed that currently we can drop the reporter "speech"  into the dropdown menu of "set voice to" and that we could drop "tilt angle [up]" into the "tilt angle [up]" block (this yielded "undefined").
Steps to Reproduce
Add the WeDo 2.0 & Speech extensions, then drag "tilt angle [up]" into itself, and put that in the speak block. It should say "undefined".

Operating System and Browser
Mac, Chrome 59

@paulkaplan similar to the variable dropdown issue you just fixed.

Some dropdowns can accept blocks, and some can't.

The first block in this screenshot can accept a block, but the second one can't.
A dropdown that can be overridden by a dragged block should be implemented as an input with a shadow block (in the toolbox).
A dropdown that cannot be overridden by a dragged block should be implemented as a field.

Yup, those probably shouldn't be droppable. @ericrosenbaum I can help you fix this on your extensions branch, but I'm going to close this issue here because it can't be fixed on scratch-blocks repo right now.


Should prefetchCount part of rabbitmq.eventing.knative.dev/prefetchCount be changed to another name ?

Problem
rabbitmq.eventing.knative.dev/prefetchCount could be confusing as it conflates prefetchCount in the RMQ Bounded Context - https://www.rabbitmq.com/consumer-prefetch.html with prefetchCount in the Eventing Rabbitmq context.
Persona:
Which persona is this feature for?

Event Consumer
Event producer

Exit Criteria

Determine if this needs to be changed ?

Time Estimate (optional):
n/a
Additional context (optional)
Add any other context about the feature request here.

I guess this can be closed since https://github.com/knative-sandbox/eventing-rabbitmq/pull/676 landed