[Question] Usage of padding

Thanks for providing an implementation for this architecture. I'm currently implementing a variant of it, and wondered why a padding is chosen in the conv layers although it is not mentioned in the LiLaNet paper (at least I couldn't find it):
https://github.com/TheCodez/pytorch-LiLaNet/blob/f68aae9d23a18c1d5b255fc0d4e7b421f2da44fd/lilanet/model/lilanet.py#L78-L81
I think it might make sense that a padding is applied along the axis where the kernel size is 7, so that the spatial dimensions decrease in the same way as for the side that has a kernel size of 3. But it isn't mentioned in the paper, or am I missing something?
Also, why is a padding of 1 applied in the 1x1 convolution?
Bonus question: So both spatial dimensions are decreased by one after each LiLaBlock. Why not use an (additional) padding of 1 so that the size is preserved through the network?
I'm just a beginner in deep learning so any help is appreciated.

Okay so I realized that the equal decreasing along both spatial dimensions is actually required so that all of the four parallel convolutions result in tensors of the same spatial dimensions, which is required for the LiLaNet because of the subsequent stacking.
I also realized that with the current choice of padding the spatial dimensions are indeed preserved through the network. However, this is caused by the 1-padding in the 1x1 convolution. This seems a bit strange to me, because on the edges the convolutions can only consider the zero-padding, because they are only 1x1.
What about removing this padding and instead increasing the padding for the previous conv layers, where the kernels are larger?


Q: deserializing/serializing complex XML documents?

The title is a bit odd, but I've read through the docs (and this library looks truly awesome) and I have a bit of a (possibly unique) use-case. Though I feel like this is pretty common with XML documents.
If I have a document that has this structure:
<top>
<element
    attributes for element (integer/boolean/single-line string)
>
<multi-line attribute>value</multi-line attribute>
...
</element>
...
</top>

Then I'd like to "move up" the (inner) elements of element into element itself when deserializing (since I don't have control over the actual structure of the document). The docs indicate that it's possible to "flatten" when serializing, but is it possible to go the other way? That is: flatten when deserializing but expand when serializing?
If the type-system constrains this and there isn't any way around it I don't mind using a custom processor with the reflection parts of the library only to handle it. If at all possible though I'd like to just define the attributes once given how many there are for the document I'm trying to parse.
Edit: I'd also like to rename the top-level element when serializing but that should be a lot easier (if I remember right that's just a template string literal when calling rfl::xml::write).

Hi @ethindp ,
I am not entirely sure I understand your requirement. Could you provide a somewhat more detailed example of what you are trying to do?
But if I do understand this correctly, I would do something like this:
struct MultiLine {
    rfl::Attribute<std::string> attribute;
    std::string xml_content; // magic field name, represents "value"
};

struct Element {
    rfl::Attribute<std::string> attribute1;
    rfl::Attribute<bool> attribute2;
    rfl::Attribute<int> attribute3;
    rfl::Rename<"multi-line", std::vector<MultiLine>> multi_line;
};

struct top {
    Element element;
};

The way I understand it, this should generate an XML that looks like what you have asked for.
Does that make sense?

And yes, you can just pass a string literal to rfl::xml::write to rename the top element.

@liuzicheng1987 Sorry, I'll clarify as to your first comment.
The actual XML document I'm working with is the MUSHclient XML format. It has this general structure:
<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE muclient>

<muclient>
<world
  ... world single-line attributes (eg. ip address) ...
>

  ... world multi-line tags (eg. <connect_text> ... </connect_text> ...

</world>

<triggers>

  ... individual triggers here ... (eg. <trigger> ... </trigger> )

</triggers>

<aliases>

  ... individual aliases here ... (eg. <alias> ... </alias> )

</aliases>
... Continues like this...

Essentially, the attributes on world itself can be boolean, numeric, color, or single-line strings (i.e. they're all just strings in the actual doc itself). But world can have sub-elements, like so:
<connect_text>Now connected to game</connect_text>

What I'm asking is: How do I represent things like connect_text as another field in the struct (but as a string), like I would for the single-line strings, without needing to create a new struct? Example of what I'm asking to achieve:
struct MCLFile {
// These can appear in any order and are all optional, theoretically
World world;
std::vector<Trigger> triggers;
std::vector<Alias> aliases;
// ...
};

struct World {
// Sample of some string attributes that might (but might not) appear in a document
std::string chat_file_save_directory;
std::string chat_name;
std::string chat_message_prefix;
// Example of some multi-line attributes, but they are child elements in the document itself
std::string connect_text;
std::string filter_aliases;
std::string filter_timers;
};

As XML this should, in theory, be then able to read a document like:
<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE muclient>

<muclient>
<world
  chat_name = "name"
  chat_message_prefix = "prefix"
>
  <filter_aliases>
This is a
multi-line string
</filter_aliases>
</world>
</muclient>

And it should be able to write a document like that too, if I do it right and it's possible.

@ethindp , you are pretty close.
In an XML context, std::vector is optional anyway, otherwise you can use std::optional. If you want something as an attribute, use rfl::Attribute.
The order of the fields does not matter, the parser goes my field names, not order.
struct MCLFile {
// These can appear in any order and are all optional, theoretically
std::optional<World> world;
std::vector<Trigger> triggers;
std::vector<Alias> aliases;
// ...
};

struct World {
// Sample of some string attributes that might (but might not) appear in a document
rfl::Attribute<std::optional<std::string>> chat_file_save_directory;
rfl::Attribute<std::optional<std::string>> chat_name;
rfl::Attribute<std::optional<std::string>> chat_message_prefix;
// Example of some multi-line attributes, but they are child elements in the document itself
std::string connect_text;
std::string filter_aliases;
std::string filter_timers;
};

@liuzicheng1987 Thanks so much! :) One last question: if I have an element like:
<element attr1 attr2>text</element>

What's the appropriate way of reading the text part? The format I'm parsing isn't documented anywhere so I'm just reading the code and trying to reimplement it using this lib and it's got some quirks.

Hi @ethindp,
you can use the magic field xml_content, like this:
struct element{
    rfl::Attribute<std::string> attr1;
    rfl::Attribute<std::string> attr2;
    std::string xml_content;
};


adding CRUD for tags

Current coverage is 37.55% (diff: 56.66%)

Merging #27 into master will increase coverage by 4.21%

@@             master        #27   diff @@
==========================================
  Files            16         17     +1
  Lines           219        245    +26
  Methods           0          0
  Messages          0          0
  Branches         20         24     +4
==========================================
+ Hits             73         92    +19
- Misses          134        141     +7
  Partials         12         12

Powered by Codecov. Last update 9de3f68...42838b1

ok to test

There you go, anything else?

This is going to need a big ol' rebase after #34 was merged - I don't mind doing it if you give me push karma to your repo.

@jimmidyson np, won't take me that long.

It'd be nice to get a review on this. It's been sitting here for a while now.

@KurtStam I could do a review later, but think @jimmidyson is probably better suited.

Sorry I haven't looked at this but I've had a lot of other things to do as you might have noticed. Right now I'm not too interested in adding functionality to the REST API while the model is still in flux, as we're discussing in the ipaas brain storming doc.
I would prefer to see stuff that we know we're going to have to do like authentication, authorization, logging, tracing, instrumentation, etc while we figure out what the model & finally the REST API should look like.
How does that sound?

It's something Rachel asked for specifically for he demo.

Thanks @KurtStam - I had asked around and Tags were still a model that would be necessary. Not sure about the priority though, @jimmidyson has a better idea of that.


lines-changed-only gets confused when lines only deleted from a file

From https://github.com/chocolate-doom/chocolate-doom/pull/1537
It complains about all issues in file src/hexen/p_enemy.c
The PR only deleted lines from this file and did not add any. This led to "lines": [] being passed to clang-format which was interpreted as "lint whole file".

@shenxianpeng To be clear, the desired behavior here is to skip the file entirely if there are now lines added. The solution you propose in #21 doesn't satisfy that behavior.


what the RGB images are used for?

from the paper KinectFusion, the only raw depth images are enough, so I don't know what the RGB images here are used for?

For color fusion on the output mesh.

For color fusion on the output mesh.

Excuse me, how do I fusion the colors?


Feedback as embedded google form or something else more useful?

I think we could find a way to attach a file, or include the data in some other way, but I'll have to look into it.

Update: we are going to try creating our own form instead of using a Google form. Then we will either use a tiny server to send the form data over email, or add it to a Google spreadsheet using Apps script.

Branch with development of form and request to send data to a google spreadsheet: https://github.com/ethanbb/cliff-effects/tree/feedback-form

Fixed with #465


fd.name some times contain bogus  part in "Write below root" event

Some times the events from sandbox rule "Write below root" contain a incomplete path, making it hard to know the location of the file in question.  This is an example message:
"14:27:16.402853438: Error File below / or /root opened for writing (file=<UNKNOWN>cf_lock.lmdb.lock evt_type=openat user=root user_uid=0 user_loginuid=-1 process=cf-agent proc_exepath=/usr/bin/cf-agent parent=cf-execd command=cf-agent terminal=0 exe_flags=O_RDWR container_id=host container_name=host)",
The process triggering the event is cfengine with its lock file, and in other similar events the fd.name value is "//cf_lock.lmdb.lock", so I suspect the real value of the <UNKNOWN> part should be "/".
This is running on a RHEL 9.3 machine using the "modern" ebpf probe, with a setup where all rule sets from https://github.com/falcosecurity/rules/ are enabled.  The machine uses cfengine to keep the setup correct and up to date.
I expected fd.name to contain a full path to the opened file, and suspect there is a bug somewhere causing the <UNKNOWN> part.

Falco version: 0.37.1

Tue Feb 27 14:35:54 2024: Falco version: 0.37.1 (x86_64)
Tue Feb 27 14:35:54 2024: Falco initialized with configuration file: /etc/falco/falco.yaml
Tue Feb 27 14:35:54 2024: System info: Linux version 5.14.0-284.11.1.el9_2.x86_64<EMAIL_ADDRESS>(gcc (GCC) 11.3.1 20221121 (Red Hat 11.3.1-4), GNU ld version 2.35.2-37.el9) falcosecurity/falco#1 SMP PREEMPT_DYNAMIC Wed Apr 12 10:45:03 EDT 2023
{"default_driver_version":"7.0.0+driver","driver_api_version":"8.0.0","driver_schema_version":"2.0.0","engine_version":"31","engine_version_semver":"0.31.0","falco_version":"0.37.1","libs_version":"0.14.3","plugin_api_version":"3.2.0"}

System info:

Tue Feb 27 14:36:59 2024: Falco version: 0.37.1 (x86_64)
Tue Feb 27 14:36:59 2024: Falco initialized with configuration file: /etc/falco/falco.yaml
Tue Feb 27 14:36:59 2024: System info: Linux version 5.14.0-284.11.1.el9_2.x86_64<EMAIL_ADDRESS>(gcc (GCC) 11.3.1 20221121 (Red Hat 11.3.1-4), GNU ld version 2.35.2-37.el9) falcosecurity/falco#1 SMP PREEMPT_DYNAMIC Wed Apr 12 10:45:03 EDT 2023
Tue Feb 27 14:36:59 2024: Loading rules from file /etc/falco/rules.d/01-falco-incubating_rules.yaml
Tue Feb 27 14:36:59 2024: Loading rules from file /etc/falco/rules.d/01-falco-sandbox_rules.yaml
Tue Feb 27 14:36:59 2024: Loading rules from file /etc/falco/rules.d/01-falco_rules.yaml
Tue Feb 27 14:36:59 2024: Loading rules from file /etc/falco/rules.d/60-nidhogg.yaml
Tue Feb 27 14:36:59 2024: /etc/falco/rules.d/60-nidhogg.yaml: Ok, with warnings
1 Warnings:
In rules content: (/etc/falco/rules.d/60-nidhogg.yaml:0:0)
    macro 'allowed_tmp_files': (/etc/falco/rules.d/60-nidhogg.yaml:41:2)
------
- macro: allowed_tmp_files
  ^
------
LOAD_UNUSED_MACRO (Unused macro): Macro not referred to by any other rule/macro

Tue Feb 27 14:36:59 2024: Loading rules from file /etc/falco/rules.d/99-settings.yaml
Tue Feb 27 14:36:59 2024: /etc/falco/rules.d/99-settings.yaml: Ok, with warnings
1 Warnings:
In rules content: (/etc/falco/rules.d/60-nidhogg.yaml:0:0)
    macro 'allowed_tmp_files': (/etc/falco/rules.d/60-nidhogg.yaml:41:2)
------
- macro: allowed_tmp_files
  ^
------
LOAD_UNUSED_MACRO (Unused macro): Macro not referred to by any other rule/macro

{
  "machine": "x86_64",
  "nodename": "soria.uio.no",
  "release": "5.14.0-284.11.1.el9_2.x86_64",
  "sysname": "Linux",
  "version": "#1 SMP PREEMPT_DYNAMIC Wed Apr 12 10:45:03 EDT 2023"
}

Cloud provider or hardware configuration:
OS: Red Hat Enterprise Linux 9.3
Kernel: Linux some-host 5.14.0-284.11.1.el9_2.x86_64 falcosecurity/falco#1 SMP PREEMPT_DYNAMIC Wed Apr 12 10:45:03 EDT 2023 x86_64 x86_64 x86_64 GNU/Linux
Installation method: RPM

cc @FedeDP @Andreagit97

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

I'm still waiting for a resolution.
--
Happy hacking
Petter Reinholdtsen

/remove-lifecycle stale
Sorry we had no time to look into this during this release cycle; setting next milestone:
/milestone 0.19.0

/milestone 0.20.0


Regression: DataFrameWriteOptions::with_single_file_output produces a directory

Describe the bug
Consider a snippet like this:
df.write_parquet(
  "dir/data",
  DataFrameWriteOptions::new().with_single_file_output(true),
  None
).await

Before v43 this would write a single file called data, but in v43 this is creating data as a directory with a randomly named file(s) in it.
This seems to be related to #13079 (cc @dhegberg) that added an extension-based heuristic.
I see this as a regression, as single file output is requested explicitly, and I don't want a heuristics to be applied.
We are using Parquet files with a content-addressable file system and our files don't have extensions.
To Reproduce
See above
Expected behavior
Considering the introduction of the extension-based heuristic I would suggest the following behavior:

with_single_file_output is not called (single_file_output == None) - apply the heuristic
with_single_file_output(true) - produce a single file at the exact path specified
with_single_file_output(false) - create directory under specified path if doesn't exist and write one or many files

Additional context

I agree this is a regression. Thank you for the callout @sergiimk
I think this is a pretty good first issue for someone as the description is clear and the need is well defined.

take

It seems hard to control the behavior of write_parquet by single_file_output(and I've noticed that It seems never used), what really controls whether to generate a single file output the suffix(in start_demuxer_task()), there are several methods I can think of to handle this issue:

We can add a suffix like .single to the paths that require generating a single file, and then recognize this suffix in start_demuxer_task().
Give up single_file_output in DataFrameWriteOptions, use FileSinkConfig instead to control single file behavior.
cc @alamb @sergiimk @dhegberg

Did some digging and found this old PR #9041 that seems to have removed single_file_output flag from FileSinkConfig - worth looking into it to understand the reasoning, not to undo the changes.
Looking at v42 code it does indeed seem that DataFrameWriteOptions::single_file_output is not read anywhere and the logic relies on just this condition in demux:
let single_file_output = !base_output_path.is_collection();

which in v43 became:
let single_file_output = !base_output_path.is_collection() && base_output_path.file_extension().is_some();

The DataFrameWriteOptions::new().with_single_file_output(true) is used in a bunch of tests though, so it's just a lucky coincidence that all tests give file a proper test.parquet name and not just test.
Personally I think that all kinds of extension-based heuristics don't belong in such low level code like start_demuxer_task and perhaps better left at the DataFrame level.
Whichever heuristic version (pre v36, pre v43, or post v43) is the right one - I don't really mind, but I think there should be a way to skip it and specify explicitly.

It seems that the previous PR intentionally removed the single_file_output option, but later introduced a heuristic.


Toggle search result (preserve toggle state)

Hi, some time ago this feature has been working fine. But now it's broken.

VSCode Version: 1.22.2
OS Version: osx 10.13.4

Steps to Reproduce:

Search some word through files.
Hide some search result.

Close editor.
Open editor.
Search the same word again.

Expected result: result we've toggled in step 2, should be hidden (toggle should be preserved)
Actual result: result we've toggled in step 2 is shown
The same situation with Open editors section

It can't preserve toggle state.
Thank you.

It's never worked that way, whether an item is expanded initially is always calculated again when the search happens, based on the number of results under that item.

@roblourens 'What do you mean "Same with open editors"?' state was preserving after close-open an editor for open editors, workspace... sections. It's very strange to hear that this feature never worked, I didn't come up with it. Maybe it worked as a part of some plugin.

Open VS Code
Open some file or files.
Open editors section is shown

Hide Open editors section

Close VS Code
Open VS Code
Actual result: Open editors section is shown

Expected result: Open editors section is hidden, because before VS Code was closed, I hided this section.

That part works for me in Insiders but not in Stable, so I think it's fixed in 1.23 which will be released tomorrow.

@roblourens Thank you!


Resolve relative imports in Protobufs compiled to JavaScript

Currently, Protobuf compiler generates JavaScript files with relative imports, e.g:
var spine_options_pb = require('../../spine/options_pb.js');

It means that all the files used as dependencies should be generated for every module and cannot be reused. The PR solves the issue and allows to replace relative imports by global, library-like imports.
So, the import above can be changed to:
var spine_options_pb = require('spine-web/spine/options_pb.js');

The adjustment of imports is done by Proto JS plugin by the ResolveImports task.
Imports of standard Protobuf types
The task also adjusts imports of standard Protobuf types like require('google-protobuf/google/protobuf/any_pb.js'). These imports are made non-relative by Protobuf compiler. But we want to use standard types, which are additionally processed by the Proto JS plugin. So, the imports are adjusted to refer spine-web module instead google-protobuf.
The set of imports that will be adjusted depends on the configuration of the Proto JS plugin. By default, the plugin will adjust only imports of files provided by Spine via NPM.
Custom configuration of imports resolving
You can also specify the custom modules and directories they provide. So, the plugin will replace relative imports by imports of module files.
An example:
protoJs {
      modules = [
           // The module provides `company/client` directory (not including subdirectories).
           // So, an import path like {@code ../company/client/file.js}
           // becomes {@code client/company/client/file.js}.
           'client' : ['company/client'],

           // The module provides `company/server` directory (including subdirectories).
           // So, an import path like {@code ../company/server/nested/file.js}
           // becomes {@code server/company/server/nested/file.js}.
           'server' : ['company/server/*'],

           // The module provides 'proto/company` directory.
           // So, an import pah like {@code ../company/file.js}
           // becomes {@code common-types/proto/company/file.js}.
           'common-types' : ['proto/company']
     ]
}

For a more comprehensive description of the feature configuration, see the wiki page.
Other changes
The PR also solves #306 by introducing a new abstract base for plugins — ProtoPlugin. This class provides FileSet including the types from the module known_types.desc and from the project runtime dependencies and ensures that these types are present in KnownTypes.
Under the hood, ProtoPlugin uses FileDescriptorSuperset. So, this and related classes were moved from model-compiler module to plugin-base.

@armiol PTAL.


Option for disabling HTML entity unescaping

Summary and context of the enhancement
This is a resurrection of the issue https://github.com/hyperdevs-team/poeditor-android-gradle-plugin/issues/49. In our project we use HTML tags combined with format strings. That means that tags should be escaped. It would be great to have that option.
Suggested implementation
Add an attribute unescapeHtmlTags to poEditor section with default value true, and enable/disable string escaping based on this value.
Additional documentation
https://developer.android.com/guide/topics/resources/string-resource.html#StylingWithHTML

In some cases, however, you may want to create a styled text resource that is also used as a format string. Normally, this doesn't work [...] The work-around to this is to write the HTML tags with escaped entities.

Hello @apoi!
Sorry for the long delay in answering to you, I've opened a PR with the added flag, hope it works with your use case 😁
Let me know if you run into any issues with it!


Add test job to ci config

This is nice in theory, but we don't have any real tests, nor is there any way to run Makepad apps within CI (yet).
Without that, what's the benefit of this CI pass? It'd just be wasted computational time & resources.

When I run the cargo test, it seems that there are test functions inside our project, for example in utils.rs. So do we delete the contents of utils.rs?

I mean, sure those are technically tests, but they're just there for the sake of my original development effort when writing that utility function. They're not actually providing any meaningful checks/tests that ensure things in Robrix are still working properly.
Until we have written tests that are actually useful and check some larger-scope correctness properties about Robrix, there's no real purpose in having a CI pass further slow down our PR procedure.
And no, don't delete them.

Got it. That's right. it doesn't mean much to our robrix at the moment.


Using sum of 2 losses

Hi, thank you for your works and share.
I found there are two outputs from EESPNet_Seg
output1 from level 4 (used in inference)
output2 from level 2 (only used in training stage)
I'm wondering why did you use sum of 2 losses
loss1 = criterion(output1, target)
loss2 = criterion(output2, target)
loss = loss1 + loss2

What if trying "loss = criterion(output1+output2, target)" and using "output1+output2" as a final segmentation output, which is similar to "skip layer" used in FCN-8s.

What if using one more (another) output from level 3.

If you have already tried those combination, can you inform the details you tried and explain the reason why you didn't use that?
If not, what do you think about that concept? what can we expect?

Sorry for the late response. I somehow missed this one.

We followed PSPNet kind of approach. However, you can use the one you are proposing. I don’t think it will make a huge difference.

give it a try.

@jongmokim7 This question is very interesting! But to some extend, there is no a proper explanation for that. In PSPNet, a weighted auxiliary  loss which is set to be 0.4 is added to the training procedure and in BiSeNet two more auxiliary losses(their weight are both set to 1) are added to optimize the whole model.  So you may see many excellent models use this training strategy while how do we understand it.
It should have some benefits at least:

Increase gradient. Gradient,in general,gradually guides our model to step into optimal.But in this case, if we add one more loss for training the model will get a gradient almost twice as large as the original one which seems to be more helpful for model to learn. After a long time for learning, performance of model will be stable and you will surprisingly find that loss here is also almost twice as large as the original one. Haha, that's may be or not be true but what you need to think is a better model will get better performance which comes mainly from the representation capacity not from more and more losses I think.
More context information or gather more information??   I'm not very clear about that.But I suggest that we need compare more cases about this issue. And here I list some experiment to help understand.

Firstly, train the model with only loss( we can view this as baseline)
Train the model with two or more losses jointly( Jointly train the model )
Pre-train model with part model and then add it to the whole model to train( to verify whether the
auxiliary loss help performance )
···( you can image any comparable experiment here )
So what I want to say is when you add one more loss to your model ,you may face a Collaborative Optimization question.

I'm also a learner of DL and focus on semantic segmentation. Here, I agree with @sacmehta you need give a try about your questions.


[cyclonedds] update to 0.10.4

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[x] The "supports" clause reflects platforms that may be fixed by this new version
[x] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

When testing locally, the following error occurs.
F:\cyclonedds\buildtrees\cyclonedds\src\0.10.4-13ac356444.clean\src\core\ddsi\include\dds/ddsi/ddsi_serdata.h(328): error C2375: 'ddsi_serdata_from_iox': redefinition; different linkage
F:\cyclonedds\buildtrees\cyclonedds\src\0.10.4-13ac356444.clean\src\core\ddsi\include\dds/ddsi/ddsi_serdata.h(326): note: see declaration of 'ddsi_serdata_from_iox'
F:\cyclonedds\buildtrees\cyclonedds\src\0.10.4-13ac356444.clean\src\core\ddsi\include\dds/ddsi/ddsi_serdata.h(335): error C2375: 'ddsi_serdata_from_loaned_sample': redefinition; different linkage
F:\cyclonedds\buildtrees\cyclonedds\src\0.10.4-13ac356444.clean\src\core\ddsi\include\dds/ddsi/ddsi_serdata.h(333): note: see declaration of 'ddsi_serdata_from_loaned_sample'

.\vcpkg.exe install cyclonedds[*] --allow-unsupported
install-x64-windows-dbg-out.log

.\vcpkg.exe install cyclonedds[*] --allow-unsupported

Any errors with supported features?

.\vcpkg.exe install cyclonedds[*] --allow-unsupported

Any errors with supported features?

The shm feature does not support the Windows platform. In order not to interrupt the installation, I added --allow-unsupported.

If you ask for unsupported features, the build is more and less expected to fail, i.e. to "interrupt the installation".
This is not how to do PR reviews.
If you don't want to manually remove unsupported features from the command line, I would recommend to build vcpkg with the test-features PR.

If you ask for unsupported features, the build is more and less expected to fail, i.e. to "interrupt the installation". This is not how to do PR reviews. If you don't want to manually remove unsupported features from the command line, I would recommend to build vcpkg with the test-features PR.

OK, I use the test command: .\vcpkg.exe install cyclonedds[ddsperf,deadline-missed,idlc,ipv6,lifespan,security,source-specific-multicast,ssl,topic-discovery,type-discovery]:x64-windows , re-tested, and this time the following error occurred.
FAILED: src/tools/ddsperf/ddsperf_types.c src/tools/ddsperf/ddsperf_types.h F:/cyclonedds/buildtrees/cyclonedds/x64-windows-dbg/src/tools/ddsperf/ddsperf_types.c F:/cyclonedds/buildtrees/cyclonedds/x64-windows-dbg/src/tools/ddsperf/ddsperf_types.h
cmd.exe /C "cd /D F:\cyclonedds\buildtrees\cyclonedds\x64-windows-dbg\src\tools\ddsperf && F:\cyclonedds\buildtrees\cyclonedds\x64-windows-dbg\bin\idlc.exe -Wno-implicit-extensibility -oF:/cyclonedds/buildtrees/cyclonedds/x64-windows-dbg/src/tools/ddsperf F:/cyclonedds/buildtrees/cyclonedds/src/0.10.4-13ac356444.clean/src/tools/ddsperf/ddsperf_types.idl"
ninja: build stopped: subcommand failed.

install-x64-windows-dbg-out.log

Thanks for your PR, Is work still being done for this PR?


Remove ClusterSet and ClusterSetBinding API version v1alpha1

We already have ClusterSet ClusterSetBinding v1beta1 version for 3 releases. It should be safe to remove the alpha version
/assign @elgnay
/assign @ldpliu

Duplicated with https://github.com/open-cluster-management-io/OCM/issues/67.


Markup error in Lung CT Segmenter

Slicer preview 4.13.0-2021-09-28
Error in Lung CT Segmenter concerning markup placement:
The green slice constantly switches back to the red slice after adding the 7th marker.

I've already fixed this (this is the problem I wrote about in the CIP pull request). Update your Slicer to the latest Slicer Preview Release.


SSO in non-browser context

My setup is single sign-on to an auth service under the same domain (eg sso.example.com) as the service I'm trying to authenticate to (eg portal.example.com).  Even though they share a domain, the auth & cookie headers get cleared because the domains do not match exactly.
Ideas on how I can do this the "right" way instead of a hack like the following?
https://github.com/erik-stephens/superagent/commit/b4fa2da5288638f08954023e0baa33d44288e03c

Unfortunately, we don't have a good solution here.
Do you know if the cookiejar library has support for matching cookies by domain? I'm not sure if we're using the library properly.

For my case, it's working as I expect: my diy/artisinal SSO service issues a Set-Cookie with a JWT for domain=example.com and the target service (foo.example.com) sees that cookie.
I assumed there would be some standard like CORS to help guide this, but not being in a browser changes the game considerably?  I've been out of the web dev game for a while and feel a bit out of touch - wondering if there's a best practice to follow.  My "let clients declare their level of trust" seems sound but I'm a bit biased, especially since I'm not worrying about browser clients.
Feel free to close if doesn't seem worth any more consideration.  I expect my use case to be outside the norm.

PR welcome


Extend reach for GUI

Currently when you try to open some inventories you get an issue of flashing off when you try to open it. This can be fixed by using Mixin in Ptdyeplus.
Right now vanilla containers can be reached; but this needs to be extended to all interfaces now.

 yarden.zamir on Discord says

Hm..

 yarden.zamir on Discord says

We dont have many guis lol, nothing else comes to mind

 yarden.zamir on Discord says

Thats a good sign

 engineersmith_4628 on Discord says

I'll just make sure all vanilla stuff work at least. Brewing stands, etc.

 yarden.zamir on Discord says

Yes, although a lot of them are removed or will be its probably better to have them all fixed

 engineersmith_4628 on Discord says

I tried to extend the reach to the stone cutter (as a block). and I just get crashes. So I'll leave it with what I've got so far and make a PR to ptdyeplus.

https://github.com/jasperalani/ptdye-plus/pull/6

 yarden.zamir on Discord says

thats ok i want to remove the stonecutter anyway.

 coolandonrs on Discord says

engineersmith_4628 is there a reason why you don't just mix into a shared parent?

(BaseContainerBlockEntity, WorldlyContainer, or Container for most, though you'd probably want one of the latter two)

 engineersmith_4628 on Discord says

because the ones that I did change override the functions within those

 engineersmith_4628 on Discord says

and don't call super

 coolandonrs on Discord says

oopsies

 engineersmith_4628 on Discord says

It's all good ^^ important to ask these questions for code review

 coolandonrs on Discord says

if you feel comfortable enough with more annoying mixins then try taking a look at #12. Feature request: Make it free to rename things in the anvil turns out to just be way easier in a mixin but it wasn't quite working as anticpated. I'm going to take another look tmrw but I have the idea down (I think) the execution just needs to be corrected

 coolandonrs on Discord says

Since while I understand mixin (mostly) I haven't done it alot, if you have more expierence it might be a better task for you.

 coolandonrs on Discord says

oh lol. No worries then since I plan on working on it later anyway

 engineersmith_4628 on Discord says

👀 not to nit pick, but could you move this line down one so it's still alphabetical
https://github.com/CoolandonRS/ptdye-plus/commit/9e08ec17847010666fc0276e8ee9c007420b4e84#diff-1a9720718d14c6295fc1134db3b40778a164277b2084cea9aa8835d55318e844R8

 coolandonrs on Discord says

Oh yeah. I did it that way to organize by purpose, but alphabetical might make more sense.

Implemented


Move system tests to a separate directory

Fixes #233
Instructions to reviewer on how to test:

Open the vscode test discovery tool
one-click run the tests that are CI-compatible
one-click run the s03 tests (which now are in a separate folder)

Checks for reviewer

[ ] Would the PR title make sense to a scientist on a set of release notes
[ ] If a new device has been added does it follow the standards
[ ] If changing the API for a pre-existing device, ensure that any beamlines using this device have updated their Bluesky plans accordingly
[ ] Have the connection tests for the relevant beamline(s) been run via dodal connect ${BEAMLINE}

https://github.com/DiamondLightSource/dodal/actions/runs/11239184669/job/31245653630?pr=597
it's the same as on another branch

Yeah, it's all typing stuff from the new bluesky release, I'll have a look in the morning, meanwhile this is fine


Random Game page returns Server Error (500) when there's no game in Plan to Play list.

https://remember.games/gamelist/random
This is a potential source of confusion: I initially thought it would return a random game from the entire catalog, not a random game from the PTP list.

Good catch! That is indeed a bug as well as something that could use some clarification. It was a feature carried over from the old really-rough site, so to me it seemed more obvious than it actually is.


[BugFix] deprecate CLASSES_DICT and _get_typed_output

closes #297
The fact that I had not to change tests means nor CLASSES_DICT nor _get_typed_output were directly tested.
Are there dedicated test for types? should we add some?

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.04 :tada:

Comparison is base (8ab67e4) 87.30% compared to head (0681e55) 87.35%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #299      +/-   ##
==========================================
+ Coverage   87.30%   87.35%   +0.04%
==========================================
  Files          30       30
  Lines       10678    10625      -53
==========================================
- Hits         9322     9281      -41
+ Misses       1356     1344      -12

Flag
Coverage Δ

linux-cpu
85.47% <100.00%> (+0.04%)
:arrow_up:

linux-gpu
86.84% <100.00%> (-0.43%)
:arrow_down:

linux-macos-cpu
85.49% <100.00%> (+0.04%)
:arrow_up:

linux-stable-cpu
85.52% <100.00%> (+0.04%)
:arrow_up:

linux-stable-gpu
86.84% <100.00%> (-0.43%)
:arrow_down:

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

Impacted Files
Coverage Δ

tensordict/prototype/tensorclass.py
95.37% <100.00%> (+2.85%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

This is very interesting, I just replaced _get_typed_output on main with the below (i.e. raise an error if we were ever going to call _from_tensordict) and the tests suites pass without issue. It seems that _get_typed_output is actually a no-op!
def _get_typed_output(out, expected_type: str | type):
    if isinstance(expected_type, str) and expected_type in CLASSES_DICT:
        if isinstance(out, CLASSES_DICT[expected_type]):
            return out
        raise RuntimeError
    elif (
        isinstance(expected_type, type)
        and not isinstance(out, expected_type)
        and isinstance(out, TensorDictBase)
    ):
        raise RuntimeError
    elif isinstance(out, TensorDictBase):
        dest_dtype = _check_td_out_type(expected_type)
        if dest_dtype is not None:
            raise RuntimeError

    return out

This is great! Much simpler. Is this possible now thanks to #249?

probably since #157 actually

I think we can probably consolidate test_tensorclass_nofuture.py and test_tensorclass.py now right?


Unable to view the complete VC Data

Scroll is disabled while viewing the VC data in user wallet. Due to this, user is not able to view the complete JSON-LD source of the VC

This has been fixed - https://github.com/trustbloc/edge-agent/commit/d99dd6783f2f3ff0a867cc15785a65ff9305b0f6.


Inconsistent 2206 upgrade instructions

There appear to be inconsistent requirements in the documentation.
This says to update from 1.2108.2.111 to 2206
"Hotfix prerequisites: before applying the 2206 update
The 2206 release of Azure Stack Hub must be applied on the 2108 release with the following hotfixes:
Azure Stack Hub hotfix 1.2108.2.111"
Source: https://docs.microsoft.com/en-us/azure-stack/operator/release-notes?view=azs-2206
But the 1.2206.1.24 hotfix docs say this:
"Hotfix information
To apply this hotfix, you must have version 1.2206.0.6 or later."
Source: https://docs.microsoft.com/en-us/azure-stack/operator/hotfix-1-2206-1-24?view=azs-2206
However, 1.2206.0.6 doesn't appear to exist.
Can you confirm that going from 1.2108.2.111 to 1.2206.1.24 is the correct sequence?

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

ID: c6e05517-6ffa-ad32-ec69-d3299492d880
Version Independent ID: 2d6ffb4c-9134-a390-3f90-2322c9182e76
Content: Azure Stack Hub release notes - Azure Stack Hub
Content Source: azure-stack/operator/release-notes.md
Service: azure-stack
Sub-service: azure-stack-hub
GitHub Login: @sethmanheim
Microsoft Alias: sethm

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

Please contact Microsoft Support, as on the documentation side, I have no visibility into versioning schemes. Thanks for reaching out! #please-close


console.log (JS) does not output to debug console, debug does not work either

VSCode Version: 1.49.2
OS Version: Windows 10 Pro

Steps to Reproduce:

Do a console.log("any string");
run the program

Does this issue occur when all extensions are disabled?: Yes
console.log does not output, and debugger does not work, breakpoints are completely ignored.
It all works find in the insiders version.

If it is fine in insiders version than there is nothing for us to do since it is fixed.
However first assigning to @connor4312 as he might have some ideas.
@danieltkach also we would need exact reproducavle steps

/jsDebugLogs

But yes if Insiders works fine (thank you for trying) then it's probably alright. The next release will ship next week.


[BUG] Meteoroids don't appear at all

Meteors don't seem to appear at all, regardless of how long one waits or how the meteor shower/shooting star chances are set.
found by littleodie (Discord)

I did various tests. They at least attempt to render, down to the part where the corners are chosen and used to draw a square. The square just doesn't appear in-game.


Fix intermittent start-up video desync

Occasionally, start-up will be desynced. Likely a race condition with a main memory access; need to deterministically time sync.

Per #63...
Relatively certain what's happening is that the worst-case scenario for the RX cog results in long count being loaded on Cog 0's side after the TX cog has started firing.
Likeliest solution is to pass constant(GFX_BUFFER_SIZE << 16) | @gfx_buff to the RX Cog and let it proceed to waitpeqing internally.

May have fixed w/ commit<PHONE_NUMBER>8d5a4839a7c6a34e8fc2a364d77e4e, pending verification...

Looks like it may actually be caused by the write on the TX side to the trans address too soon...

Next debug step is to hardcode some long waits in critical sections to try and force the behavior.

This is 100% happening when TX is running BEFORE RX is, 0% vice versa - narrowing down cause via scratchpad and deterministic timing.

Couldn't you do something simple like a start-up handshake and then use said line(s) for normal transfer?

That's actually what I'm already doing! I'm using the vertical sync (VS) and TX/RX (X) line as a two-way handshake which accounts for either Prop starting up first: the GPU's RX cog waits for VS to go high, while the CPU's RX cog drives VS high and then immediately waits for X to go high.
So if the CPU starts up first, it drives VS high and it waits for X to be driven high by the GPU. When the GPU eventually starts up, its waitpeq will immediately detect VS is high, and proceed to immediately drive X high, notifying the CPU to proceed as well.
If the GPU starts up first, it immediately starts waiting for VS to be high. When the CPU eventually starts up, it will drive VS high which causes the GPU to immediately drive X high, which notifies the CPU to proceed.
This paradigm works the majority of the time, with video starting and displaying seamlessly when both uCs are started at (ostensibly) the same time.
The problem is that, occasionally and without any apparent deterministic pattern, the transfer will be very slightly desynced at startup - colors and patterns flashing around in incorrect places, but the basic elements are definitely there.
What is almost certainly happening, and I have a test planned for this evening to verify, is that the transfer itself is desyncing - what the RX cog thinks is the "start" of the data stream is actually within the stream elsewhere, off by some yet-unknown number of bits, bytes, words, or longs.
What I've been able to determine for certain so far is that this behavior only happens when the CPU is running before the GPU (TX cog running before RX cog). Even with this startup order enforced to purposely trigger the desync, it still doesn't happen every time (maybe 1/3rd of the time).
So now I'm in a position of trying to determine if this is:

A hardware instead of software problem - the breadboarded nature of the circuit is causing errant behavior in the transfer (unlikely, as it would then happen regardless of which uC started up first) or maybe the individual clocks of the uCs are aligning or misaligning or mistiming in just the right way to cause an off-by-one-cycle error (again, if so then why wouldn't this happen regardess of which uC started up first)
An edge case, where a worst-case hub access timing is causing the desync somehow (my original thoughts, as the difference between 8 and 23 execution cycles would fit like a glove for an occasional symptom like this - but after plotting out the worst-case execution times down to the clock cycle in Excel, I don't see anywhere that this would be happening)
Something I haven't considered yet, which is where I'm sitting now

The fact that I've narrowed it down to only happening when TX precedes RX should be a big hint, but the random nature even then of the behavior is eating my chili. My most recent attempt at rooting out the cause was trying to force it to happen 100% of the time, adding delays between critical sections, but that didn't bare any fruit.
Here's the TX code with the handshake starting at line 86, and here's the RX code with the handshake starting at line 78
Somethign I may do tonight is remove the handshake code altogether, force TX to start before RX, and preclude that the handshake itself is the problem. If I can rule that out entirely, then that's another data point.
If you have any thoughts, they would be greatly appreciated. This issue has knocked me off of development for the past several months.

A new data point: forcing the RX cog to only accept a single transmission (followed by an infinite jmp $) shows me that the behavior is evident from the very first frame of data transmitted. I'm replacing one of the GPU rendering cogs with a serial transmission COG to sample the data that is in the video buffer to see whether the stored video data received from the CPU is errant.

Ok we're getting down to it now:
11111111_00001111_11000011_00000011 <--- GOOD GFX DATA
11111111_10001111_11100011_10000011 <--- BAD GFX DATA
11111111_00000111_11000001_00000001 <--- BAD GFX DATA
01111111_10001111_11000011_00000011 <--- BAD GFX DATA
These are all samples of the very first long of the GFX buffer on the GPU. All of these values and more are being seen, when only the first is stored in that memory during nominal operation. The only obvious pattern here is that the only bits that are being corrupted are those which are adjacent to a bit toggle (i.e. the preceding or following bit is different than the current one).
This therefore truly looks like the RX prop is somehow becoming de-synced despite the deterministic timing, and trying to read data off the wire at the instant the bits are changing; sometimes it gets the correct data, other times it gets the wrong next one.
Still digging for the cause.

Removing the handshake PASM entirely causes the problem to disappear. I'd like to say that this finally narrows the problem down to the ~10 lines of code which defines the handshake routine, but we'll see. Again, I've plotted out every instruction for the best and worst case timing scenarios down to the individual clock cycle and could not find anything that would cause this problem.

Finally narrowed down to the problem to, surprisingly enough, the TX side of the house. Only when the handshake code is present in the TX routine (with the RX-side handshake moved out to SPIN) does the problem occur. I'm sure there's a logical explanation regarding timings and whatnot, but for now the problem has been solved by moving all handshake code out to SPIN in the main functions. The next iteration will be to move the handshakes into the individual TX and RX module functions.
This issue has been (initially) satisfied by commit f8b7b4c3115bc056ab05216b7fd197fa726fc405


Fixed duplicate paragraph in use-advisor-teams-roll-out.md

Closes https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/5659.

@SerdarSoysal PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

Closing this PR because the proposed changes are already live.


DRAW THE APP UNDER THE STATUS BAR

Version
"react-native-router-flux": "4.0.0-beta.22",
"react-native": "0.50.1",
in ios 10   navbar starting from under the status bar but in ios 11  navbar starting from below the status bar .
i want to start nav bar from 0x 0y of screen  for all versions of ios.
like in android there is support like setTranslucent() but on ios i have not found support.

Lack of details


make download pages prettier

everything seems to be present.... but the pages  are not very pretty....

actually they are not that bad.
This one maybe needs a bit of space before annotation datasets?

http://pombase-dev.bioinformatics.nz/datasets
Gene names and Ids gets a bit lost.

We're gonna need something a little more specific than "prettier" to guide any changes ...

For the moment, I've tried adding some horizontal rules between the headed sections. See what you think when it's visible (on the dev site tomorrow?).

well, the lines are pretty faint, but they do add a little bit of vertical space, so I think it helps a bit


How to Debug, Profile

Hello!

Small Ruby fans want to known how catch errors.

mruby under microscope ?
Any debug-code guide

I found just this
http://www.slideshare.net/yamanekko/rubyconftw2014
http://www.slideshare.net/yamanekko/writing-mruby-debugger
https://github.com/miura1729/mruby-profiler

Have mruby team something newer?

for example https://github.com/hone/mruby-cli/wiki/StarteKit
could someone write Debug wiki post?

@toch startekit wiki is my shell command line by line draft

As it's the wiki of the project, I'd like to improve it that's why I'm asking. Is it like a tutorial of your first mruby-cli app?

yes - like tutorial but in draft now
I thought line by line is easy to understand, just try


Dns.java line 39

in okhttp3.Dns$1.lookup

Number of crashes: 1
Impacted devices: 1

There's a lot more information about this crash on crashlytics.com:
https://fabric.io/squanchy/android/apps/net.squanchy.london17/issues/59ef7cf761b02d480d21ab3b?utm_medium=service_hooks-github&utm_source=issue_impact

Not a crash


Added public justifications for CVE-2021-23463 and CVE-2022-23221

$subject

@thisaltennakoon Is this a duplicate of https://github.com/wso2/docs-security/pull/78


Fix typographical error.

Thanks for contributing to TVM!   Please refer to guideline https://tvm.apache.org/docs/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers by @ them in the pull request thread.

@adityaatluri

Thanks @cgyurgyik !


[improvement] Add more cardinal index metrics

issue: #716
/kind improvement

we don't have 2.4.7 Cardinal yet, do we?

/lgtm


Probably redesign menu burger for mobile as well?

I guess we can connect it with

#4125

May @exezbcz provide some ideas for mobile? Or do we have something on this in Figma already?
https://user-images.githubusercontent.com/5887929/198581961-d8ecc569-3ceb-4765-8c9c-4efdb26141ab.mov

yup, we already have in landing page handoff figma

components page
Can someone also change the search navbar on mobile? In current version of kodadot you dont have option to close it :D

also in components page
https://www.figma.com/file/3iOjW12ERFRDSVnpLuhQmf/landing-page-handoff?node-id=1305%3A5613

👋

Issue is still up for grab 👀

👋

@yangwao @roiLeo, can I remove buefy header component? It's hard to customize

can I remove buefy header component?

if it's hard and there are no helpers classes, I'm ok with that

seems meanwhile done
continue to #4441


style: Use members property

What type of pull request is this?

[x] Non-breaking code change
[ ] Breaking code change
[ ] Documentation change/addition

Description

better look
Changes

Checklist

[x] I've formatted my code with Black
[x] I've ensured my code works on Python 3.10.x
[x] I've tested my code

It may be a better look but it's less efficient. I'm closing this PR


[UG] Redo rephrase

Codecov Report

Merging #379 (29db3b3) into master (82d8c93) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #379   +/-   ##
=========================================
  Coverage     68.40%   68.40%
  Complexity     1131     1131
=========================================
  Files           135      135
  Lines          3865     3865
  Branches        521      521
=========================================
  Hits           2644     2644
  Misses          996      996
  Partials        225      225

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 82d8c93...29db3b3. Read the comment docs.


Make three blocks on homepage clickable

Make three blocks on homepage clickable. Now you can only add a link, but this is not intuitive.

Done


Strikethrough expands when zooming in or out

Windows Terminal version (or Windows build number)
1.4.3243.0
Other Software
should not matter
Steps to reproduce

Print strikethrough text (you can use python -c print('\x1B[9mstrikethrough\x1B[0m') or echo -e '\x1B[9mstrikethrough\x1B[0m' in bash)
Zoom in or out

Expected Behavior
The strikethrough shouldn't have expanded.
Actual Behavior

edit: this also seems to happen with underlines (\x1B[4m), double underlines (\x1B[21m), overlines (\x1B[53m), this that I don't know how to name (\x1B[7m) and hyperlinks (\x1B]8;;https://microsoft.com\x1B\\hyperlink\x1B]8;;\x1B\\)

Alas, this is one of the oldest issues in the console codebase!
/dup #32


Runtime error when decoding Json

I am getting Uncaught TypeError: Cannot read property 'tag' of undefined (https://github.com/elm-lang/core/blob/32b8fd9b3f2f1f6ef2c1d3a7914427e7a646770c/src/Native/Json.js#L313) when decoding Json.
Repo with minimum code required to replicate the issue with Json response hardcoded here
Main parts:
import Json.Decode as Json exposing ((:=))

type alias TweetModel =
    { id : Float
    , text : String
    , retweetedStatus : Maybe RetweetedStatus
    }

type RetweetedStatus = RetweetedStatus TweetModel

decodeTweets : Json.Decoder (List TweetModel)
decodeTweets =
    tweetDetails |> Json.list

tweetDetails : Json.Decoder TweetModel
tweetDetails =
    Json.object3 TweetModel
        ("id" := Json.float)
        ("text" := Json.string)
        (Json.maybe ("retweeted_status" := tweetDetails |> Json.map RetweetedStatus))

The issue seems to be related to the RetweetedStatus type and and its usage in decoder. Without it, everything works fine.
In twitter response, in each tweet record there may or may not be a retweeted_status key, hence the Json.Decode.maybe

The problem is the recursive dependency of tweetDetails on itself. This is currently not supported, the issue that needs to be fixed in order to support it is this: https://github.com/elm-lang/elm-compiler/issues/873. It's well known, so I'm closing this issue here.
To work around the issue currently, you should use lazy and force from http://package.elm-lang.org/packages/elm-lang/lazy. For more details, check out some of the issues mentioning "JSON" or "decode" listed over at https://github.com/elm-lang/elm-compiler/issues/873.

Something like this should work:
decodeTweets : Json.Decoder (List TweetModel)
decodeTweets =
    force tweetDetails |> Json.list

tweetDetails : Lazy (Json.Decoder TweetModel)
tweetDetails = lazy <| \_ ->
    Json.object3 TweetModel
        ("id" := Json.float)
        ("text" := Json.string)
        (Json.maybe ("retweeted_status" := force tweetDetails |> Json.map RetweetedStatus))

Thanks @jvoigtlaender 👍

I used this approach and now I am getting Maximum call stack size exceeded error. I will probably fix this by refactoring the code and use another decoder for retweet as there should not be any retweeted_status inside retweeted_status. I just wanted to reuse one decoder recursively as the rest of the structure is the same.
But what I am curious about, I got to this code by following this hint about recursive types/type aliases and if I would be expecting a response Json of shape used in example there (messages that can have response message and those can have response messages and so on), what would be the working approach there? I would need to use some kind of recursive decoder there like I was doing with the tweets and lazy approach just produces a different runtime error.
Thanks for pointing me to the right direction, still new to Elm :)

... what would be the working approach there? I would need to use some kind of recursive decoder there like I was doing with the tweets and lazy approach just produces a different runtime error.

The working approach should be the one using lazy and force. Other people, in some of the GitHub issues I mentioned earlier, the ones listed at https://github.com/elm-lang/elm-compiler/issues/873 that are about JSON decoding, have successfully used that approach to deal with decoding recursive structures, such as decoding JSON data that corresponds to types like this:
type Tree = Leaf Int | Node Tree Tree

So this approach is not unworking per se. Why it does not work in your specific case is difficult to diagnose without having an actual http://sscce.org/, including a call with a concrete JSON input that you expect to be able to decode but get the runtime error on.

Coming back to this since it was pointed out in https://github.com/elm-lang/elm-lang.org/issues/578 that lazy from elm-lang/lazy is overkill.

Thanks 👍

I found this via the same path as @patrik-piskay — via working through recursive type aliases advice and then hitting the runtime error.
For me using  lazy from the elm-community/json-extras package was super simple.
(I leave the note for the future. 🙂)

Yes, lazy from that package is like the lazy from my comment above. That package is not available at http://elm-lang.org/try, though, so when trying out stuff there (as above) an explicit definition of lazy is needed.


Unable to access external services/URLs

Bug description
Can't access any external website over HTTPs from my service container. I am getting this error
curl: (35) error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
Steps to reproduce the bug
I have created a service that uses port 8080. I created a gateway and virtual service like:
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: test-gateway
  namespace: tools
spec:
  selector:
    istio: ingressgateway
  servers:
    - port:
        number: 443
        name: https
        protocol: HTTPS
      tls:
        mode: SIMPLE
        serverCertificate: /etc/istio/ingressgateway-certs/tls.crt
        privateKey: /etc/istio/ingressgateway-certs/tls.key
      hosts:
        - "testurl.com"
    - port:
        number: 8080
        name: jenkins-http
        protocol: HTTP
      tls:
        httpsRedirect: true
      hosts:
        - "testurl.com"

apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: test-virtualservice
  namespace: tools
spec:
  hosts:
    - "testurl.com"
  gateways:
    - test-gateway
  http:
    - route:
        - destination:
            host: test

Now i want to allow the service test to be able to access any external URL (google, github anything) I don't want to restrict it.
Version (include the output of istioctl version --remote and kubectl version)
Kubectl:  Client v1.15.3, Server v1.15.5
How was Istio installed?
Deployed via helm chart (v1.1.0).
With the following values
apiVersion: helm.fluxcd.io/v1
kind: HelmRelease
metadata:
  name: istio
  namespace: istio-system
spec:
  releaseName: istio
  chart:
    repository: https://gcsweb.istio.io/gcs/istio-prerelease/prerelease/1.1.0/1.1.0/charts/
    name: istio
    version: 1.1.0
  values:
    global:
      enableTracing: true
    mixer:
      telemetry:
        resources:
          requests:
            cpu: 100m
            memory: 500m
    pilot:
      traceSampling: 100
    prometheus:
      enabled: false
    tracing:
      enabled: true

likely duplicate of https://github.com/istio/istio/issues/16458
Please do not install 1.1.0, it is no longer support and there are a number of clustsr-wide-outage inducing bugs that have been fixed since then
Please see the relevant issue and upgrade, and if you still have issues open a bug. Thanks


Fix build warnings when included in clang-based project

This fixes #2248

Is CI working properly? The change just removed the un-neccessary semicolon, it should not fail the build.

Thank you for the PR, @taste1981 !
@eponomar , can you please check CI?

Thank you for the PR, @taste1981 !
CI fails due to the following:
Copyright check FAILED!
api/include/mfxplugin++.h:
	Incorrect the copyright year, [YEAR-]2020 is needed:
	// Copyright (c) 2017 Intel Corporation
Correct format: Copyright (c) [YEAR-]2020 Intel Corporation. All Rights Reserved.

Can you please update the header?

done


Add E2E operator

What this PR does / why we need it:
Since we're at KubeCarrier feature complete stage, we require a simple e2e test operator for our e2e test suites.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #297
Special notes for your reviewer:
Documentation:

Does this PR introduce a user-facing change?:

NONE

/retest

/retest

/retest

/retest

/retest

/lgtm

/retest

/retest

/retest


Restore union-like behavior for inference to conditional types

Fixes #31766.

cc @rbuckton re: the node 8 failure on this PR. That failure looks like it's in an untranspiled optional catch clause in a library you happen to maintain: https://github.com/esfx/esfx/blob/master/internal/deprecate/src/index.ts

Should be fixed now. I restarted the node 8 build and it passed successfully.


Fix 03-create_entities example

Mirror of #545 which is a PR from a forked repository, hence cannot run the pipelines.

@kmahajan-cadfem FYI


Documentation now returning 404 for all UI components from Bing/likely Google

Current Behavior
Documentation now returning 404 for all UI components from Bing/likely Google
Expected Behavior
Documentation should not be returning 404 for all UI components from Bing/likely Google
Tamagui Version
n/a

Platform (Web, iOS, Android)
Bing

Reproduction
Bing/Google "Tamagui TextInput", click the link

System Info
No response

any https://tamagui.dev/docs/components/ link now returns 404

components are moved to /ui route
https://tamagui.dev/ui/intro/1.0.0
maybe take a day for google to index it ?


Spreadsheet: Add a person risk modeler tab

I'm intending to add a way to model person risk in the spreadsheet.
I wanted to open an issue for it so I can get feedback on it as I go.
Here's a (non-functional) mockup of what I'm envisioning:

How does this differ from having a tab for each person with their activities for a typical week?
Work - N people, 40 hours, masks, distance
Home - housemates, general risk categories for housemates
Social Contacts - people they see regularly undistanced. Likely marked as housemate/partner
Other activities - shopping, probably. Touring apartments, if they're me >.>
Replace the sumif(within 7 days) with just a sum.

I now have a working version of this that is pretty user friendly. Let me know if you'd like to take a look and implement it into the main spreadsheet. Happy to help make that happen if there is interest.

I'm not on the microcovid team, but I'm very interested in this - my current model of my own risk suggests that partner risk is by far the dominant contributor to my risk level, and I suspect that's the case for my partners as well, but we aren't in a closed pod.

Documenting here: @catherio gave this a thumbs up.


Is it possible to different route using service?

I was trying to navigate to element in different route using service, but i couldnt find information how to do it, is it possible?  are there any limitations to service api compared to directive?

No, that is not possible. The handling of the route change detection is only available to the directive.
You can trigger the scrolling via the scroll service from inside the onInit() method or similar on your new controller to get the desired behavior.


Authorization Logic :: Type Declarations

This implements type declarations for authorization logic. Type declarations are needed to support both:
https://b.corp.google.com/issues/219015959
and
https://b.corp.google.com/issues/219015796
for transparent release. The types supported are symbols, numbers, and principals. The syntax is directly borrowed from Souffle for now. An extra space is needed between type declarations and parameter names, but there is https://github.com/google-research/raksha/issues/375 to track fixing this eventually.

This implements type declarations for authorization logic. Type declarations are needed to support both: https://b.corp.google.com/issues/219015959 and https://b.corp.google.com/issues/219015796 for transparent release.

Links to internal bugs don't make sense in open source. When you get a chance add a brief description of what this PR is about. I have some context and will review it in any case.


[gitlab] allow runnning flakes finder manually on any branch

What does this PR do?

Enabling flakes finder on manual trigger to help detect potential flakes introduced by a change in e2e framework or its dependencies
Motivation

Helps preventing breaking e2e tests on bumps and changes
Additional Notes

Triggered this flakes finder pipeline after a bump of test-infra, realised we still run A6 tests, as discussed with @KSerrania it should be ok to remove them from the flakes finder pipelines
Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Fixing timeout issue for Wavenet

Issue #, if available: #774
Description of changes:
Changed the number of batches run per epoch to lower both training time and evaluation time.
This causes a speedup of the test by about 35%
To handle the potential difference in accuracy I performed some benchmarks of the test and adjusted the allowed accuracy to be below 1 since it fluctuated between ~0.67 - ~0.9.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

FYI the failing tests on jenkins are 1) some data loading throughput tests, which are probably affected by the machine the tests run on, and 2) some other flaky model tests :-)

Codecov Report

Merging #793 into master will decrease coverage by 0.91%.
The diff coverage is n/a.


Object-detection get "{'csrf_token': [u'CSRF token missing']}" error

Hi~
I got an ValueError: "Extension form validation failed with {'csrf_token': [u'CSRF token missing']}"  after select Test a single image. I use kitti dataset and DetectNet has been trained completed.
How to fix the problem? thanks~

Hello, this post might be relevant.

Thanks for your quick response, after I add "cloudfront.net" and "<IP_ADDRESS>:5000" into my Firefox white-list, this problem still happened. In addition, I found my terminal also show some message:

[WARNING] Infer Model unrecognized output: Couldn't import dot_parser, loading of dot files will not be possible.
"POST /models/images/generic/infer_one?job_id=20161025-205813-42f1 HTTP/1.1" 500 679 8.032371
Is this relevant to my problem?

Is this relevant to my problem?

No, that's just normal DIGITS output.

To debug, can you follow this guide to train LeNet on MNIST and try inference with that model? I suspect this is not related to object detection at all.

LeNet works fine on MNIST dataset.
It looks like my browser's problem, I'll check a again.
thanks,

I'm not sure whether it is a right way or not.
After I comment out " if not extension_form_valid and raise ValueERROR("......") " from in "DIGITS_ROOT/digits/model/image/generic/view.py", it is working.


upgrade pyright to 1.1.334

And remove two no longer required ignores

Not upgrading to 1.1.335 due to https://github.com/microsoft/pyright/issues/6387


Adjust the brightness of the external display black screen

Before opening the issue, have you...?

[X] Searched for existing issues

Question
When I open the app to adjust the brightness, the additional monitor goes black and then lights up again, and the brightness of the additional monitor does not change;
Is the VGA interface not supported?
Or the monitor is too old?

VGA is generally supported with the right dongle but the display itself might react badly to DDC commands (not all VGA monitors support DDC as this is the case with HDMI and DisplayPort monitors as well).


No way to add OAuth tokens thru the bot

There is no command to add the OAuth consumer/access tokens to the database via bot commands. Currently the only way to do this is via database edit.

Currently, the only way to add the OAuth tokens is with a database edit:
INSERT INTO auth VALUES ("token1", "token2", "token3", "token4");


Feature/apitest

lots of lines changed but I think it's because I formatted with prettier before submitting and Gene hadn't. I only added the youtube fetch and then tweaked the classes to be ids in the queryselectors.

cool

closes https://github.com/ggrove87/nu-project-1/issues/7

did you mean to close this without merging Joshua, or do I need to change something?

No. I’m sorry. I was trying to merge it but I don’t believe I have permissions because you requested only gene to review?
Sent from Yahoo Mail for iPhone
On Monday, April 11, 2022, 4:00 PM, jason @.***> wrote:
did you mean to close this without merging Joshua, or do I need to change something?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.Message ID: @.***>

Sorry I wasn't sure what that would do. I'll unrequest him.

Changes look good, will the storeMovieData function work without the input from the pullMovieInfo function?

I commented that out to debug something and forget to flip it back. I'll do it tomorrow in a new pr.


RFE: Add vendor_only data to vuln records

Is this a request for help?:
No
Is this a BUG REPORT or a FEATURE REQUEST? (choose one):
Feature Request
The GET /images/{imageDigest}/vuln/{vtype} call has a vendor_only flag today that controls if anchore will return vulnerability for an image that the vendor has marked as "won't fix". Today is only applies to vulnerabilities found in the Debian feeds that have been marked with no-dsa in the Debian bug tracker (see https://security-team.debian.org/security_tracker.html for details).
Anchore does not presently expose this fact in the record returned by the GET /images/{imageDigest}/vuln/{vtype} or the GET /query/vulnerabilities call. As a result if you want to know if a particular vulnerability matches this criteria you have to make a call to GET /images/{imageDigest}/vuln/{vtype} with the flag set and another call without the flag set and compare the results.
Anchore should provide an attribute in the response to both GET /images/{imageDigest}/vuln/{vtype} and GET /query/vulnerabilities that indicate if a specific vulnerability matches this vendor_only criteria or not. The field should always be present and probably be a boolean to align with how the flag to the API call works.

 vendor_only data in vuln query

@cburgess Thanks for bringing this RFE to our attention, this issue has been addressed in the new release of Engine v0.10.1.


metrics: set NIX_STORE_DIR

Mirror ca5ecbed4b5775f873fa15d7bf064b00d9e2862a to workaround NIX_STATE_DIR errors.
As with the other workaround, see:
https://github.com/NixOS/nix/issues/5495#issuecomment-963949707

Motivation for this change
Failure on metrics.nix is blocking unstable channel.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

@lovesegfault This is in-line with recent work you've done


tkdiff: 5.6 -> 5.7

Description of changes
https://sourceforge.net/projects/tkdiff/files/tkdiff/5.7/

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 310997 run on x86_64-linux 1

1 package built:

tkdiff


report errorbars from amsgrad

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

31 of 32 (96.88%)  changed or added relevant lines in 4 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.9%) to 73.734%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/amsgrad.jl
3
4
75.0%

Files with Coverage Reduction
New Missed Lines
%

src/kinetic-vqmc/state.jl
2
73.33%

Totals

Change from base Build<PHONE_NUMBER>1:
0.9%

Covered Lines:
466

Relevant Lines:
632

💛  - Coveralls


print-pit fails on Samsung Galaxy W (samsung-i8150): ERROR Protocol initialisation failed

Hey,
trying to use heimdall for an older Samsung device (samsung-i8150) somehow fails:
heimdall print-pit
Heimdall v1.4.2

Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...

Initialising protocol...
ERROR: Protocol initialisation failed!

Releasing device interface...

I'll look if I could find some workarounds :)
Best regards
Jonas

Are you running heimdall as root? (see https://github.com/Benjamin-Dobell/Heimdall/issues/403)
Stupid question but have to ask: have you tried reseting/restarting the phone? I know that an error like this happens if you try to run several heimdall commands in a row without reseting the phone in between

Hey thank you for the tipps. I tried with root and also as normal user. Restarting/resetting the phone several times did not help :(

Try capturing debug logs: heimdall print-pit --usb-log-level debug, and the libusb traffic with for example wireshark, and (if you have the possibility) the libusb traffic when flashing stock android with odin. Heimdall just mimics odin, so we need libusb traffic logs from odin to see how Heimdall is suppose to work with this device

Try capturing debug logs: heimdall print-pit --usb-log-level debug, and the libusb traffic with for example wireshark, and (if you have the possibility) the libusb traffic when flashing stock android with odin. Heimdall just mimics odin, so we need libusb traffic logs from odin to see how Heimdall is suppose to work with this device

Cool I'll try this! Unfortunately I didn't have luck with Odin on Windows 10 nor Windows 7. Installing the Samsung USB drivers is quite unstable and Odin is unable to establish an connection :/

I didn't have luck with Odin on Windows 10 nor Windows 7

When flashing stock android? In "proper" windows or a virtual box? (I have never gotten it to work in a virtual box)
If it does not work with odin on windows either, then maybe your usb cable is bad?

@Grimler91 I used your Heimdall fork and run it debugging option:
$ heimdall print-pit --usb-log-level debug
Heimdall v1.4.2

Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
https://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
https://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
[timestamp] [threadID] facility level [function call] <message>
--------------------------------------------------------------------------------
[ 6.788668] [00006436] libusb: debug [libusb_get_device_list]
[ 6.788690] [00006436] libusb: debug [discovered_devs_append] need to increase capacity
[ 6.788697] [00006436] libusb: debug [libusb_get_device_descriptor]
[ 6.788703] [00006436] libusb: debug [libusb_get_device_descriptor]
[ 6.788708] [00006436] libusb: debug [libusb_get_device_descriptor]
[ 6.788714] [00006436] libusb: debug [libusb_get_device_descriptor]
[ 6.788718] [00006436] libusb: debug [libusb_get_device_descriptor]
[ 6.788725] [00006436] libusb: debug [libusb_open] open 1.100
[ 6.788752] [00006436] libusb: debug [usbi_add_event_source] add fd 7 events 4
[ 6.788758] [00006436] libusb: debug [libusb_get_device_descriptor]
[ 6.788762] [00006436] libusb: debug [libusb_get_config_descriptor] index 0
Claiming interface...
[ 6.788775] [00006436] libusb: debug [libusb_claim_interface] interface 1
Setting up interface...
[ 6.788803] [00006436] libusb: debug [libusb_set_interface_alt_setting] interface 1 altsetting 0

Initialising protocol...
[ 6.791324] [00006436] libusb: debug [libusb_reset_device]
[ 6.943760] [00006436] libusb: debug [libusb_alloc_transfer] transfer 0x1d43b18
[ 6.943783] [00006436] libusb: debug [libusb_submit_transfer] transfer 0x1d43b18
[ 6.943789] [00006436] libusb: debug [add_to_flying_list] arm timer for timeout in 1000ms (first in line)
[ 6.943806] [00006436] libusb: debug [submit_bulk_transfer] need 1 urbs for new transfer with length 4
[ 6.943829] [00006436] libusb: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 6.943852] [00006436] libusb: debug [handle_events] event sources modified, reallocating event data
[ 6.943873] [00006436] libusb: debug [usbi_wait_for_events] poll() 3 fds with timeout in 60000ms
[ 6.943974] [00006436] libusb: debug [usbi_wait_for_events] poll() returned 1
[ 6.943992] [00006436] libusb: debug [reap_for_handle] urb type=3 status=0 transferred=4
[ 6.944007] [00006436] libusb: debug [handle_bulk_completion] handling completion status 0 of bulk urb 1/1
[ 6.944011] [00006436] libusb: debug [handle_bulk_completion] all URBs in transfer reaped --> complete!
[ 6.944018] [00006436] libusb: debug [arm_timer_for_next_timeout] no timeouts, disarming timer
[ 6.944035] [00006436] libusb: debug [usbi_handle_transfer_completion] transfer 0x1d43b18 has callback 0x7ff5bb601e20
[ 6.944047] [00006436] libusb: debug [sync_transfer_cb] actual_length=4
[ 6.944064] [00006436] libusb: debug [libusb_free_transfer] transfer 0x1d43b18
[ 6.944081] [00006436] libusb: debug [libusb_alloc_transfer] transfer 0x1d26c98
[ 6.944091] [00006436] libusb: debug [libusb_submit_transfer] transfer 0x1d26c98
[ 6.944102] [00006436] libusb: debug [add_to_flying_list] arm timer for timeout in 1000ms (first in line)
[ 6.944134] [00006436] libusb: debug [submit_bulk_transfer] need 1 urbs for new transfer with length 7
[ 6.944167] [00006436] libusb: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 6.944174] [00006436] libusb: debug [usbi_wait_for_events] poll() 3 fds with timeout in 60000ms
[ 7.944124] [00006436] libusb: debug [usbi_wait_for_events] poll() returned 1
[ 7.944158] [00006436] libusb: debug [libusb_cancel_transfer] transfer 0x1d26c98
[ 7.947251] [00006436] libusb: debug [arm_timer_for_next_timeout] no timeouts, disarming timer
[ 7.947265] [00006436] libusb: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 7.947279] [00006436] libusb: debug [usbi_wait_for_events] poll() 3 fds with timeout in 60000ms
[ 7.947286] [00006436] libusb: debug [usbi_wait_for_events] poll() returned 1
[ 7.947295] [00006436] libusb: debug [reap_for_handle] urb type=3 status=-2 transferred=0
[ 7.947303] [00006436] libusb: debug [handle_bulk_completion] handling completion status -2 of bulk urb 1/1
[ 7.947309] [00006436] libusb: debug [handle_bulk_completion] abnormal reap: urb status -2
[ 7.947314] [00006436] libusb: debug [handle_bulk_completion] abnormal reap: last URB handled, reporting
[ 7.947321] [00006436] libusb: debug [usbi_handle_transfer_cancellation] detected timeout cancellation
[ 7.947329] [00006436] libusb: debug [arm_timer_for_next_timeout] no timeouts, disarming timer
[ 7.947335] [00006436] libusb: debug [usbi_handle_transfer_completion] transfer 0x1d26c98 has callback 0x7ff5bb601e20
[ 7.947343] [00006436] libusb: debug [sync_transfer_cb] actual_length=0
[ 7.947350] [00006436] libusb: debug [libusb_free_transfer] transfer 0x1d26c98
ERROR: Protocol initialisation failed!

Releasing device interface...
[ 7.947389] [00006436] libusb: debug [libusb_release_interface] interface 1

[ 7.947428] [00006436] libusb: debug [libusb_close]
[ 7.947437] [00006436] libusb: debug [usbi_remove_event_source] remove fd 7
[ 7.947451] [00006436] libusb: debug [libusb_exit]
[ 7.947458] [00006436] libusb: debug [libusb_exit] destroying default context
[ 7.947464] [00006436] libusb: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 7.947470] [00006436] libusb: debug [handle_events] event sources modified, reallocating event data
[ 7.947479] [00006436] libusb: debug [usbi_wait_for_events] poll() 2 fds with timeout in 0ms
[ 7.947486] [00006436] libusb: debug [usbi_wait_for_events] poll() returned 0
[ 7.947492] [00006436] libusb: debug [libusb_unref_device] destroy device 2.3
[ 7.947498] [00006436] libusb: debug [libusb_unref_device] destroy device 2.2
[ 7.947505] [00006436] libusb: debug [libusb_unref_device] destroy device 2.1
[ 7.947511] [00006436] libusb: debug [libusb_unref_device] destroy device 1.7
[ 7.947518] [00006436] libusb: debug [libusb_unref_device] destroy device 1.100
[ 7.947524] [00006436] libusb: debug [libusb_unref_device] destroy device 1.2
[ 7.947530] [00006436] libusb: debug [libusb_unref_device] destroy device 1.1
[ 7.947536] [00006436] libusb: debug [libusb_unref_device] destroy device 4.1
[ 7.947543] [00006436] libusb: debug [libusb_unref_device] destroy device 3.1
[ 7.947549] [00006436] libusb: debug [usbi_remove_event_source] remove fd 6
[ 7.947562] [00006436] libusb: debug [usbi_remove_event_source] remove fd 5
[ 7.947585] [0000643a] libusb: debug [linux_udev_event_thread_main] udev event thread exiting

DRAFT:
Using the latest heimdall 1.4.2 of your fork:
heimdall flash --RECOVERY recovery.img

Here's the capture file.
Using Odin Multi Downloader 4.43 on Windows 7 (KVM):

Here's the capture file.
Files:

recovery.img
recovery.tar.md5
Ancora.ops

I really would like to look into the capture files but I haven't worked with them nor Heimdall yet so it might be a bit more complicated.

Seems something went wrong when you pasted the capture file link, could you send it again?

Your heimdall capture shows that the phone does not even respond to the first message sent, so will be interesting to see how different the "Odin Multi Downloader 4.43" protocol is

Hey thanks for the feedback. I have some issues capturing traffic on Windows but will try again tomorrow :)

Going through some of the old issues it seems some galaxy phones, like the Galaxy Y (and so perhaps the Galaxy W) use a different flashing protocol, see https://github.com/Benjamin-Dobell/Heimdall/issues/335#issuecomment-196208128.
Still interesting to see the differences in how it is flashed if you can capture the usb traffic, but adding support for it is probably quite a lot of work

I finally was able to capture the Win 7 usb traffic ;) Here's the Odin Multi Downlaoder flashing session capture: https://onny.project-insanity.org/files/samsungw/odin_flash_recovery.cap

Thanks! Some quick observations: the bootloader seem to be based on qcom's little kernel, and it claims that it is a MSM7230 device (not MSM8255T). I guess samsung did not bother s/7230/8225/..


Set correct "zero time" in SetAccessToken

Setting a custom token was broken since https://github.com/logpacker/PayPal-Go-SDK/pull/29.
Since time.Unix(0, 0) is NOT a "zero time" in go it caused the check at SendWithAuth function to never fail which lead to custom token always being replaced by a fresh token.
P.S. opened a new PR to use correct branch in my fork.

Thanks, it's good, merging!


Code-generating Attribute Macros fail to resolve outputs even with rust-analyzer.experimental.procAttrMacros

The crate aliri_braid seems to really confuse Rust-Analyzer due to its nature as a macro annotation, but the part that surprises me is that it seems like rust-analyzer.experimental.procAttrMacros has no effect on it.
To repro, import aliri and use this main.rs:
use aliri::jwt::JwtRef;

fn main() {
    let x = JwtRef::from_str("foo");
}

Hover over JwtRef or x and see that it has absolutely no clue what's going on- even when proc macro support is enabled. It just resolves as {unknown}, as it can't find the macro-generated types being exported by the crate.

JwtRef actually works fine in the aliri repo.

I was using it from another project which imported it; I didn't think to try it from within the repo. I can attempt to minimize my repro if it doesn't occur for you in a project which imports it?

No, I see it too. In another crate, Jwt appears to work, but I think that's only because there's a struct Jwt; in aliri, as if we're completely ignoring the proc macro attribute.

Yep, that's the behaviour I observed. Is it possible we're only expanding attribute macros in the current crate?

rust-analyzer doesn't really have a notion of a current crate, so that seems unlikely.

Seems related to #9782

This is working fine for me locally. Do you get a "proc macro not expanded" diagnostic on the #[braid] invocation? Restarting r-a should fix that.

Now I can't reproduce it either, even with the older versions.
I think we a race condition during load, so maybe I was unlucky that one time.

Odd- it worked, recognizing the type on mine for a moment while loading, then started showing the type as unresolved a moment later:

Now that errors and warnings are persisted after closing files, this leaves a permanent error after ever (purposefully or otherwise) looking at any file that exhibits this issue:

With the errors being from these lines, as above:

I attempted to reproduce the issue minimally and could not get it to occur reliably, only seeing it once during initial project creation and once while rearranging the project into a virtual workspace- but each time it resolved itself after trying the same again fresh. Is there any sort of trace or additional information I could gather from my large-project repro, being that this seems to be some sort of load-time race condition?

CC https://github.com/rust-analyzer/rust-analyzer/issues/9997

I'm no longer seeing this repro in my larger projects, and small repro scenarios appear to continue not presenting the issue.
The race condition may be fixed, or it may simply be reordered into being silent; @lnicola any idea of changes that may have reordered this or if it may actually be full-on resolved after changes to determinism?

@Dessix I don't know. I don't think it's solved, but just less likely to happen. And it didn't show up in the metrics lately:

#9997 has a possible repro, so we can close this issue in favor of it, if you want.

Let's do that. Refer to #9997 for further discussion.


Removing jalali from template

Is it possible to remove jalali from view?

Yes, as you can see in README, set multiple: false to remove Jalali from datePicker.
<adm-dtp ng-model='date' options='{multiple: false}'></adm-dtp>


Add stress_revision support

@mambocab and @EnigmaCurry review

No rush here. Was just wondering if you got the notification when written in the description. //cc @mambocab @EnigmaCurry

I can't think of any reason to use stress_path now that stress_revision exists, but I want to make sure we all agree on that.
I don't have an environment to test this in right now, but this looks correct. If you've run it locally, I'm +1 as long as we're all ok with stress_path going away.

You are correct for stress_path. Ryan and I already agreed to remove it with the addition of stress_revision. So we are all +1 on this.


add custom_field data source

👋 This adds an incident_custom_field data source.
It addresses issue #77.

These changes were merged as part of https://github.com/incident-io/terraform-provider-incident/pull/81


chore(main): release 1.1.25

:robot: I have created a release beep boop
1.1.25 (2023-05-31)
Features

ai/route.ts: add support for AIRBROKE_OPENAI_ORGANIZATION environment variable to be able to use OpenAI API with organization key (7543903)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/icoretech/airbroke/releases/tag/v1.1.25 :sunflower:


Feat :  Fetch all the values for dropdown using Axios

GET apis only

This PR has conflicts. We need to resolve those before merging.


Freetext value incorrectly set

The freetext component is returning incorrect text value when the user changes the text in the box. See example below.
Here the value of the instrument is set to the first value that user inputs i.e. 'd'
However the user continued to type additional text and the end result was 'Adler' marked with green. But the instrument returned 'd' (which was the first thing that they entered. )
In addition, the entity_type and kind field are not filled for the Freetext (marked with red)

Is this fixed, @madjens ? I believe the only existing issue is the multiple render events

yes it is fixed