Evaluating the uncertainty of sdf-based NeRFs

Hi!
Thank you for the work. Could you please tell me if this work can be migrated to sdfstudio to evaluate the mesh of sdf-based NeRFs(such as neus,volsdf...)? I skimmed the paper and the code, and here is my understanding: construct an implicit uncertainty field using multiple viewpoints, and then input a 3D point to determine the uncertainty at the point. If I understand correctly, discretizing the mesh or sdf as the points cloud would similarly query their uncertainty. Is this feasible?
Thank you.

Hi, did installation go successfully for you? I'm facing some issues with running ns-uncertinity.

@Anonymous772066235
Hi,
the work has not been tested on sdf-based representations but it should be able to generalize to for example neus. However, you should adopt the code to work in sdf studio, as the uncertainty extraction code in this repository is not completely independent of nerfstudio code. As an example you can look at the uncertainty.py file to see how the same uncertainty extraction has been added to the three different nerf codes (ingp, nerfacto and mipnerf).
Once you have it on your sdf-based representation you will have a 3D field you can query anywhere in space for the uncertainty measure.

@Anonymous772066235 Hi,
the work has not been tested on sdf-based representations but it should be able to generalize to representations like neus. However, you should adopt the code to work in sdf studio, as the uncertainty extraction code in this repository is not completely independent of nerfstudio code. As an example you can look at the uncertainty.py file to see how the same uncertainty extraction has been added to the three different nerf codes (ingp, nerfacto and mipnerf). Once you have it on your sdf-based representation you will have a 3D field you can query anywhere in space for the uncertainty measure.

Ok, thank you！I will try.

Hi, did installation go successfully for you? I'm facing some issues with running ns-uncertinity.

Not successful. I am going to create a docker container based on nerfstudio’s docker image.

what issue did you run into for installation?

@lilygoli
Hi,
I have recently successfully installed BayesRays and completed the evaluation of nerfacto results. That's awsome! Referring to your implementation of get_unc_mipnerf, I successfully implemented uncertainty evaluation and visualization for vanilla-nerf. However, I encountered an issue when migrating to the sdf-based method. I tried both bakedsdf and neus-facto under sdfstudio, as well as neus under nerfstudio, but they all presented the same problem: in the find_uncertainty method, defform_points.grad is None. Could you provide some guidance on this?

Screenshots of successful implementation of  vanilla-nerf .

Screenshot of the error encountered while running the  sdf-based experiment.
This is the code uesed for uncertainty evaluation of  neus:
from nerfstudio.models.neus import NeuSModel
from typing import  Dict, List, cast
from torch.nn import Parameter
......
    def get_unc_neus(self, ray_bundle,model) :
        if model.collider is not None:
            ray_bundle = model.collider(ray_bundle)

        assert (
            ray_bundle.metadata is not None and "directions_norm" in ray_bundle.metadata
        ), "directions_norm is required in ray_bundle.metadata"

        samples_and_field_outputs = model.sample_and_forward_field(ray_bundle=ray_bundle)

        # shortcuts
        field_outputs: Dict[FieldHeadNames, torch.Tensor] = cast(
            Dict[FieldHeadNames, torch.Tensor], samples_and_field_outputs["field_outputs"]
        )
        ray_samples = samples_and_field_outputs["ray_samples"]
        weights = samples_and_field_outputs["weights"]
        bg_transmittance = samples_and_field_outputs["bg_transmittance"]

        points = ray_samples.frustums.get_positions()                                               # add
        pos, _ = normalize_point_coords(points, self.aabb, model.field.spatial_distortion)          # add
        offsets = self.deform_field(pos).clone().detach()                                           # add
        offsets.requires_grad = True                                                                # add
        ray_samples.frustums.set_offsets(offsets)                                                   # add

        rgb = model.renderer_rgb(rgb=field_outputs[FieldHeadNames.RGB], weights=weights)
        depth = model.renderer_depth(weights=weights, ray_samples=ray_samples)
        # the rendered depth is point-to-point distance and we should convert to depth
        depth = depth / ray_bundle.metadata["directions_norm"]

        normal = model.renderer_normal(semantics=field_outputs[FieldHeadNames.NORMALS], weights=weights)
        accumulation = model.renderer_accumulation(weights=weights)

        # background model
        if model.config.background_model != "none":
            assert isinstance(model.field_background, torch.nn.Module), "field_background should be a module"
            assert ray_bundle.fars is not None, "fars is required in ray_bundle"
            # sample inversely from far to 1000 and points and forward the bg model
            ray_bundle.nears = ray_bundle.fars
            assert ray_bundle.fars is not None
            ray_bundle.fars = torch.ones_like(ray_bundle.fars) * model.config.far_plane_bg

            ray_samples_bg = model.sampler_bg(ray_bundle)
            # use the same background model for both density field and occupancy field
            assert not isinstance(model.field_background, Parameter)
            field_outputs_bg = model.field_background(ray_samples_bg)
            weights_bg = ray_samples_bg.get_weights(field_outputs_bg[FieldHeadNames.DENSITY])

            rgb_bg = model.renderer_rgb(rgb=field_outputs_bg[FieldHeadNames.RGB], weights=weights_bg)
            depth_bg = model.renderer_depth(weights=weights_bg, ray_samples=ray_samples_bg)
            accumulation_bg = model.renderer_accumulation(weights=weights_bg)

            # merge background color to forgound color
            rgb = rgb + bg_transmittance * rgb_bg

            bg_outputs = {
                "bg_rgb": rgb_bg,
                "bg_accumulation": accumulation_bg,
                "bg_depth": depth_bg,
                "bg_weights": weights_bg,
            }
        else:
            bg_outputs = {}

        outputs = {
            "rgb": rgb,
            "accumulation": accumulation,
            "depth": depth,
            "normal": normal,
            "weights": weights,
            # used to scale z_vals for free space and sdf loss
            "directions_norm": ray_bundle.metadata["directions_norm"],
        }
        outputs.update(bg_outputs)

        if model.training:
            grad_points = field_outputs[FieldHeadNames.GRADIENT]
            outputs.update({"eik_grad": grad_points})
            outputs.update(samples_and_field_outputs)

        if "weights_list" in samples_and_field_outputs:
            weights_list = cast(List[torch.Tensor], samples_and_field_outputs["weights_list"])
            ray_samples_list = cast(List[torch.Tensor], samples_and_field_outputs["ray_samples_list"])

            for i in range(len(weights_list) - 1):
                outputs[f"prop_depth_{i}"] = model.renderer_depth(
                    weights=weights_list[i], ray_samples=ray_samples_list[i]
                )
        # this is used only in viewer
        outputs["normal_vis"] = (outputs["normal"] + 1.0) / 2.0
        return outputs, points, offsets

The  code contains added statements related to points and offsets  based  on get_output method in base_surface_model.py. From my observation, the get_unc_model method is built upon the get_output method of relevant models. Moreover, I've successfully performed evaluations for vanilla-nerf using this approach. However, the transition to sdf-based methods hasn't been successful. I'd greatly appreciate your guidance on this matter.

Hi @Anonymous772066235,
What is the type of normal you are computing in the line:
normal = model.renderer_normal(semantics=field_outputs[FieldHeadNames.NORMALS], weights=weights)
Numerical normal by itself doesn't compute gradients for the normals. But analytical normal compute gradients wrt to inputs. So, you might want to enable gradient propagation through your input coordinates and then compute backward to input coordinates...

@Anonymous772066235
Hey,
Happy you were able to test on vanilla nerf. I would make sure that you have the gradients wrt to the positions (even when deformation is not added, and in the original pipeline) available. This depends on how the accelaration backend (tinycudnn or nerfacc) is handled and if its allowing gradient flow all the way back to the point coordinates. Also make sure that the second-order derivatives that might show up because of NeUS formulation are precise enough or you might need to increase precision (for when you fix the gradient flow and stop getting NaNs). Let me know if this works out!
BTW you mentioned you might make a docker container for the repo, if you ended up doing that, would you mind sharing the image?
Thanks!

@Shrisudhan @lilygoli
Thanks for your replies. I'll try more.  Actually the docker environment creation failed, and I'm currently testing it in my local conda environment.

@lilygoli
Hi,
Due to a lack of theoretical knowledge, some of my attempts haven't been successful yet. Now I can confirm that in   find_uncertainty,  variable defom_points is all zeros and its gradient  is None before the line colors[0].backward(retain_graph=True) . After that line, defom_points remains zero, but its gradient is no longer None. However, with the SDF-based NeRF, after that line, defom_points remains zero, and its gradient remains 'None'. This is very puzzling for me. I noticed that nerfstudio includes methods like neus and neus-facto. Could you  implement their uncertainty evaluation?

Hi,
sorry for the late reply. I think your observation is consistent with the fact that the backend is not using gradient propagation to the input point positions for your case. I will try to take a look and see if I can set up an example with NeUS in nerfstudio this weekend and let you know.

@lilygoli
Hi,
Is there any good news? Looking forward to it working on NeUS.


productivty feature

Description of the new feature / enhancement
I mostly use the 'alt+space' option because it's the most productive one. However, when I consider using other options, it's really hard to remember all the shortcuts or find ones related to the right-click sections.
But I have an idea: what if we have a '/' right on the alt+tab search bar, and other options open up for selection, similar to Notion or other apps?
It can be really useful to see all PowerToys features at once like that, and we can use them easily as well.
Also we can use like the
I have written "/" then I'll see all app features
or I have written "/fanc" fore example I mean I'm trying to open fancy zones and I'll saw the results filtered as well.
Scenario when this would be used?
Also we can use like the
I have written "/" then I'll see all app features
or I have written "/fanc" fore example I mean I'm trying to open fancy zones and I'll saw the results filtered as well.
Supporting information
No response

In v0.76 there is a list of enabled plugins to PT Run, are you looking for more than that? Or are you looking for a way to search for the Plugins? /needinfo

You can check here
https://www.notion.so/help/keyboard-shortcuts#slash-commands
Joseph Finney @.***>, 5 Ara 2023 Sal, 16:35 tarihinde
şunu yazdı:

In v0.76 there is a list of enabled plugins to PT Run, are you looking for
more than that? Or are you looking for a way to search for the Plugins?
/needinfo
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/30170#issuecomment-1840806311,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJKEOJNRDADGUF2LH3JUZZTYH4PI7AVCNFSM6AAAAABAHEAQC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBQHAYDMMZRGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

yeah I am familiar with Notion's slash commands. They are a way to quickly search for different text formatting options. The challenge here is that PowerToys Run is a search box, so you are proposing tapping the / key would invoke a different kind of search? What would you be searching for? PT Run Commands? Windows Commands? /needinfo


Test: Keeping the undo history when the file changes on disk

Test plan item for #2908 (PR #29655)
Complexity: 3

[x] any OS @aeschli
[ ] any OS @isidorn

TODO@Alex: fill this in

Tested on Linux:

open a file in VSCode, make several change, test undo and redo
modify the file in an other editor, see that changes are applied to editor in VSCode, test that undo works, also redo
test with git viewlet


FLUME-3149 reduce cpu cost for taildir file source while still maintaining reliability by using posFile in memory channel

File channel tracks transferred events and use transnational mechanism to make transfer recoverable. However, it increases CPU cost due to frequent system calls like write, read, etc. The Cpu cost could be very high if the transfer rate is high.
In contrast, Memory channel has no such issue which requires only about 10% of CPU cost in the same environment but it's not recovered if the system is down accidentally.
For sources like taildir, I propose we could write position file in memory channel to achieve reliability and reduce CPU cost.
After testing on my own production environment, CPU usage dropped from 13% to 3% and still maintain reliability.  （Transfer rate: 1Mb/s ,  kafka sink, file channel -> memory channel with pos file)

I think this change is essentially reaching reliability in MemoryChannel when using taildirSource. So the performance diff is essentially the diff of MemoryChannel  and FileChannel. In my tests it saves more than 90% percent of CPU but it's no easy way of comparing it by a simple command.
Perhaps I should add some tests to verify the reliability when using tailDirSource and MemoryChannel?

Can one of the admins verify this patch?


A detail contributing guide

The only thing about this website that I like is the.com ending; otherwise, the user interface needs to be updated, and there isn't a comprehensive tutorial for contributing, which is a problem because I want to include my project here. I was given no instructions for doing the same. I will try to work on this issue. Can you please assign me that?

Hi @Sajiyah-Salat, the website does not work by including projects. It works by searching for issues/projects tagged with "Good First Issue" on Github using its API. There isn't a list of projects that are included by default.


Don't need search-index-full.json and search-index-head.json, so don't generate them.

Depends on Microsoft/TypeSearch#13
The files would also have to be manually deleted from Azure.

I'd prefer we keep the -full copy around just for debugging purposes. We can get rid of the other two, though

You mean get rid of just -head? -full is 11kb bigger than -min (see table in #86) so we probably want -min to be what TypeSearch accesses. Unless you think the difference isn't worth the complexity.

What I meant to say is that I want a file (maybe not a complete file) that has unminified field names in it. We don't have to upload it, just have it be an available artifact for someone to look at.

Maybe we could have a "--full" flag? Sounds like this is just for a command line users' testing?

Sure

OK, I've redone the entire PR. We now output -full as well when the user requests it. Also remembered to document this time.

:+1:


Allow editing other fields when transitioning an issue in TUI

Is your feature request related to a problem? Please describe.
Yes. We have a workflow that requires setting a resolution when moving to Done stage. In the TUI, this is not currently possible.
Describe the solution you'd like
Allow setting the same fields that are capable of being set from the cli in the tui:
resolution
comment
assignee
Describe alternatives you've considered
I suppose I could not use the TUI and only use the CLI.
Additional context

Another alternative I just thought of that would work in my case would be allowing to set a default resolution in the config. In 99% of cases, the resolution I would set would be "Done".
jira issue move PLAT-2872 Done -RDone

This does work, btw.

Same issue. +1 :)


[MEG] reword docstrings and docs

Hi @glevv
I mostly modified the wording of the user guide and the docstrings. I also changed the formulas based of what I interpreted from the slide deck you shared. Please double check the formulas to make sure I did not mess up.
Thank you!
Ready from my side.


[SEQ-1684] [SEQ-1731] Hashtags on comments

Use case, tag a comment with #QA or #Legal or #TempVFX in order to filter on them in the future.
From SyncLinear.com | SEQ-1684

Should do the Twitter thing where certain hashtags like #color #sound have cool icons that get auto attached.


Add Reducer.onChange

We've had this reducer in isowords for a very long time, before the Dependencies library, reducer protocol, and builders, and while handy, it didn't feel right to include in the library at the time due to lack of clarity in the API itself (we had several overloads to provide various permutations of old value and new, inout and non-inout state, action, the environment, etc. But revisiting things with our more modern tools, a single signature stands out as "right":
.onChange(of: \.childState) { oldValue, newValue in
  Reduce { state, action in
    // ...
  }
}

So here's a PR that adds just that!
The main concern of this reducer is the potential performance cost, a caveat we've attempted to document. Basically this reducer should be preferred at leaf nodes (like BindingReducer) where the cost to equate the given value is low.
@krzysztofzablocki I know you've observed some issues with onChange in the past. Given our caveats do you have any thoughts you'd like to share?

The biggest performance cost I observed wasn't the diffing at all, it was due to protocols and higher order wrapping of reducers this lead to, the same exact code as a single onChange instead of N smaller onChange has been significantly (40%+) faster in my testing.
The other issue I saw with onChange was the fact that if we place it at wrong level of reducer it will never fire, where mutations happen vs where onChange is established is very important distinction that lots of folks didn't realize

The biggest performance cost I observed wasn't the diffing at all, it was due to protocols and higher order wrapping of reducers this lead to, the same exact code as a single onChange instead of N smaller onChange has been significantly (40%+) faster in my testing.

Did you have multiple onChanges being applied to the same sub-state? It seems like we could take care to fuse them together, but it also seems like the user could compose the onChange logic together into a single operator as it sounds like you did.
I also wonder if the version in this PR would perform differently than the version you used? Or does it look the same?

The other issue I saw with onChange was the fact that if we place it at wrong level of reducer it will never fire, where mutations happen vs where onChange is established is very important distinction that lots of folks didn't realize

Ha yeah this is a gotcha, but we can document that it only observes changes in the reducer it's applied to.

Looks the same, we had many different elements we were reacting to, simply having one reducer replace onChange and doing individual if with substate comparison was the 40% gain and it was gain on all of TCA action processing so huge difference for us

@krzysztofzablocki I did a little bit of benchmarking and found that if all else is the same, inlining the work in Reduce vs. chaining the operators doesn't seem to incur that much of a slowdown, maybe 10% slower total with 10 chained operators:
name             time        std        iterations
--------------------------------------------------
Without onChange 3584.000 ns ±  15.92 %     358459
With onChange    3917.000 ns ±  10.23 %     354548

The biggest cost of using this operator (or any operator that combines reducers) is the Effect.merge that happens under the hood, so if you can avoid that by inlining the work, you'll see a much bigger difference. We do have plans to improve the performance of merging reducers much more in the future, so we think this is safe and useful enough to add to the library.

Expand for benchmark
```swift
struct R1: ReducerProtocol {
  struct State {
    var count = 0
  }
  enum Action {
    case incrementButtonTapped
  }
  var body: some ReducerProtocolOf {
    Reduce { state, action in
      let oldCount = state.count
      var effect = EffectTask.none
      switch action {
      case .incrementButtonTapped:
        state.count += 1
      }
      var newCount = state.count
      if oldCount != newCount {
        state.count = newCount
        effect = .merge(effect, .none)
      }
      newCount = state.count
      if oldCount != newCount {
        state.count = newCount
        effect = .merge(effect, .none)
      }
      newCount = state.count
      if oldCount != newCount {
        state.count = newCount
        effect = .merge(effect, .none)
      }
      newCount = state.count
      if oldCount != newCount {
        state.count = newCount
        effect = .merge(effect, .none)
      }
      newCount = state.count
      if oldCount != newCount {
        state.count = newCount
        effect = .merge(effect, .none)
      }
      newCount = state.count
      if oldCount != newCount {
        state.count = newCount
        effect = .merge(effect, .none)
      }
      newCount = state.count
      if oldCount != newCount {
        state.count = newCount
        effect = .merge(effect, .none)
      }
      newCount = state.count
      if oldCount != newCount {
        state.count = newCount
        effect = .merge(effect, .none)
      }
      newCount = state.count
      if oldCount != newCount {
        state.count = newCount
        effect = .merge(effect, .none)
      }
      newCount = state.count
      if oldCount != newCount {
        state.count = newCount
        effect = .merge(effect, .none)
      }
      return effect
    }
  }
}
struct R2: ReducerProtocol {
struct State {
var count = 0
}
enum Action {
case incrementButtonTapped
}
var body: some ReducerProtocolOf {
Reduce { state, action in
switch action {
case .incrementButtonTapped:
state.count += 1
}
return .none
}
.onChange(of: .count) { oldValue, newValue in
Reduce { state, _ in
state.count = newValue + 1
return .none
}
}
.onChange(of: .count) { oldValue, newValue in
Reduce { state, _ in
state.count = newValue + 1
return .none
}
}
.onChange(of: .count) { oldValue, newValue in
Reduce { state, _ in
state.count = newValue + 1
return .none
}
}
.onChange(of: .count) { oldValue, newValue in
Reduce { state, _ in
state.count = newValue + 1
return .none
}
}
.onChange(of: .count) { oldValue, newValue in
Reduce { state, _ in
state.count = newValue + 1
return .none
}
}
.onChange(of: .count) { oldValue, newValue in
Reduce { state, _ in
state.count = newValue + 1
return .none
}
}
.onChange(of: .count) { oldValue, newValue in
Reduce { state, _ in
state.count = newValue + 1
return .none
}
}
.onChange(of: .count) { oldValue, newValue in
Reduce { state, _ in
state.count = newValue + 1
return .none
}
}
.onChange(of: .count) { oldValue, newValue in
Reduce { state, _ in
state.count = newValue + 1
return .none
}
}
.onChange(of: .count) { oldValue, newValue in
Reduce { state, _ in
state.count = newValue + 1
return .none
}
}
}
}
benchmark("Without onChange") {
var state = R1.State()
_ = R1().reduce(into: &state, action: .incrementButtonTapped)
}
benchmark("With onChange") {
var state = R2.State()
_ = R2().reduce(into: &state, action: .incrementButtonTapped)
}
</details>


Update cats-effect, cats-effect-laws to 3.2.3

Updates

org.typelevel:cats-effect
org.typelevel:cats-effect-laws

from 3.2.1 to 3.2.3.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

labels: library-update, semver-patch

Superseded by #172.


Previously PinLayout was setting the view's frame. This was breaking the view's tranform

By setting the view's center and bounds we set the frame of the non-transformed view, and this keeps the view's transform.
So view's transforms won't be affected/altered anymore by PinLayout.
For people not using transforms, this should be a non-breaking change. If someone is using transforms with PinLayout, this may change the behavior, although I think this will produce the expected results (ie, transforms not being affected/altered by layout).

Codecov Report

Merging #107 into master will increase coverage by 1%.
The diff coverage is 98.3%.

@@            Coverage Diff            @@
##           master     #107     +/-   ##
=========================================
+ Coverage   89.36%   90.37%     +1%
=========================================
  Files          33       34      +1
  Lines        7554     6232   -1322
  Branches      440        0    -440
=========================================
- Hits         6751     5632   -1119
+ Misses        796      600    -196
+ Partials        7        0      -7

Impacted Files
Coverage Δ

Sources/Impl/PinLayoutImpl+Layouting.swift
88.88% <100%> (-0.81%)
:arrow_down:

Tests/TransformSpec.swift
100% <100%> (ø)

Sources/Impl/Coordinates.swift
100% <100%> (ø)
:arrow_up:

Tests/BasicView.swift
80.64% <50%> (+3.5%)
:arrow_up:

Tests/RectNimbleMatcher.swift
50% <0%> (-10%)
:arrow_down:

Sources/Impl/PinLayoutImpl.swift
82.87% <0%> (-0.57%)
:arrow_down:

Sources/ObjectiveC/PinLayoutObjCImpl.swift
3.25% <0%> (-0.13%)
:arrow_down:

Tests/PinPointCoordinatesSpec.swift
100% <0%> (ø)
:arrow_up:

Tests/RelativePositionSpec.swift
100% <0%> (ø)
:arrow_up:

... and 27 more

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 8d428be...9de5363. Read the comment docs.


DAC8574 support?

Hi!  I've been using your ADS1X15 and MCP23S17 libraries for a while now (many thanks!), and I have just started getting some DAC8574s ready on breadboard to expand my project.
I've forked this repo (https://github.com/doctea/DAC8574), and very quickly and roughly hacked in quad-channel support, since I can't find an already-existent implementation for the DAC8574 anywhere.
It basically works, although the output is very jittery compared to code that manually writes the values out to the DAC.
But before I get too far into modifying things myself, I wondered if you had any plans to make a library for the DAC8574, or any tips on the best way to modify one of your existing libraries to do the job please?

Thanks for the question
I have to check the datasheet and find time to work on it. Do you need it on short term?

Thanks for your swift reply!  I am in no urgent hurry, and can make do with my current bodges for a while :).  I am also planning to make a small sponsorship donation since I have had so much good use from your libraries so far.

Thanks, appreciated.
Had a quick look at your updated fork of the repo and it looks good (at least no very strange things).
Will setup a repository this week, and publish at platformIO and in the library manager.

created placeholder - https://github.com/RobTillaart/DAC8574

@doctea
Created a develop branch with first version, build is running.

get all examples compiling with channel 0 only
review all code against the datasheet
test with hardware, that's where I need your help
extend and stabilize
documentation
etc

@doctea
A first review of the code with datasheet is done.
Can you give the develop branch a try with your hardware?
Please test the examples with channel 0, and if that works try to use channel 1,2, and 3
Thanks!

@doctea
documentation is updated to remove references of DAC8571 and better match the DAC8574.

@doctea
Updated the error handling, if build succeeds I will merge the develop branch,
Please open new issues under the DAC8574 branch, or just to let me know your test results.

@doctea
published library on platformIO and in the library manager, should be available within 24 hrs.

@doctea
Thanks for the donation!


Fail to run HPOReID

When I tried to run
python3 projects/HPOReID/train_hpo.py --config-file projects/HPOReID/configs/baseline.yml --srch-algo "bohb"
errors occur： Do you know why?
2020-10-19 14:33:31,868     ERROR function_runner.py:233 -- Runner Thread raised error.
(pid=68853) Traceback (most recent call last):
(pid=68853)   File "/home//.local/lib/python3.7/site-packages/ray/tune/function_runner.py", line 227, in run
(pid=68853)     self._entrypoint()
(pid=68853)   File "/home//.local/lib/python3.7/site-packages/ray/tune/function_runner.py", line 290, in entrypoint
(pid=68853)     self._status_reporter.get_checkpoint())
(pid=68853)   File "/home//.local/lib/python3.7/site-packages/ray/tune/function_runner.py", line 499, in _trainable_func
(pid=68853)     output = train_func(config, checkpoint_dir=checkpoint_dir)
(pid=68853)   File "projects/HPOReID/train_hpo.py", line 132, in train_reid_tune
(pid=68853)     trainer.train()
(pid=68853)   File "fastreid/engine/defaults.py", line 365, in train
(pid=68853)     ), "No evaluation results obtained during training!"
(pid=68853) AssertionError: No evaluation results obtained during training!
(pid=68853) Exception in thread Thread-2:
(pid=68853) Traceback (most recent call last):
(pid=68853)   File "/home/anaconda3/lib/python3.7/threading.py", line 917, in _bootstrap_inner
(pid=68853)     self.run()
(pid=68853)   File "/home/.local/lib/python3.7/site-packages/ray/tune/function_runner.py", line 246, in run
(pid=68853)     raise e
(pid=68853)   File "/home//.local/lib/python3.7/site-packages/ray/tune/function_runner.py", line 227, in run
(pid=68853)     self._entrypoint()
(pid=68853)   File "/home/ligck/.local/lib/python3.7/site-packages/ray/tune/function_runner.py", line 290, in entrypoint
(pid=68853)     self._status_reporter.get_checkpoint())
(pid=68853)   File "/home//.local/lib/python3.7/site-packages/ray/tune/function_runner.py", line 499, in _trainable_func
(pid=68853)     output = train_func(config, checkpoint_dir=checkpoint_dir)
(pid=68853)   File "projects/HPOReID/train_hpo.py", line 132, in train_reid_tune
(pid=68853)     trainer.train()
(pid=68853)   File "/fastreid/engine/defaults.py", line 365, in train
(pid=68853)     ), "No evaluation results obtained during training!"
(pid=68853) AssertionError: No evaluation results obtained during training!
(pid=68853)
(pid=68853) ERROR [10/19 14:33:31 fastreid.engine.train_loop]: Exception during training:

Before run hpo experiments, make sure that you can train reid models normally.
Could you load the train set and test set?

@KRYSTALLJY There is no really wrong key message here.
You may need to post what follows this line..((pid=68853) ERROR [10/19 14:33:31 fastreid.engine.train_loop]: Exception during training:)


Disable violations from CLI

Why
We find ourselves experimenting with turning on and off violation types. It would be convenient if pks had this functionality built in.
What
Adding the following CLI args:
--disable-enforce-privacy
--disable-enforce-folder-privacy
--disable-enforce-dependency
--disable-enforce-layers
--disable-enforce-visibility

looks like some failing tests but ping me when everything is green!

looks like some failing tests but ping me when everything is green!

Yep, I had to fmt. It's ready now. Thanks!


[4907] Add HESA Cyprus codes

Context
Trello: https://trello.com/c/edXQJ5f4/4907-itt-register-portal-data-check-for-c22053
Cypriot nationality did not map for some HESA trainees because we did not hold these codes in Register. I have had a look at Apply and also found this PR where the Cyprus codes were added: https://github.com/DFE-Digital/apply-for-teacher-training/pull/6584
On the basis that these have been added to Apply, I have added to Register as well. I'm not 100% sure if we needed to add these nationalities elsewhere too to avoid issues with the PersonalDetailsForm when we try to save the nationalities. I had a look at the code and couldn't quite work it out.
I've added these codes to the Apply mapping as this is what we use for nationalities in trainees/create_from_hesa.rb
Changes proposed in this pull request

Add HESA Cyprus codes

Guidance to review

Not sure if I need to add these nationalities elsewhere to avoid issues with the PersonalDetailsForm saving the nationality correctly.

Important business

[ ] Does this PR introduce any PII fields that need to be overwritten or deleted in db/scripts/sanitise.sql?
[ ] Does this PR change the database schema? If so, have you updated the config/analytics.yml file and considered whether you need to send 'import_entity' events?

NB: Please notify the #twd_data_insights team and ask for a review if new fields are being added to analytics.yml

 ITT Register Portal Data Check for C22053

@HettieS there's two "inactive" mappings in that file which I believe you just move into MAPPING
app/lib/dttp/code_sets/nationalities.rb:277
app/lib/dttp/code_sets/nationalities.rb:278


[Bug]: Cannot connect to Google Sheets because authorization fails Internal server error while processing request

Is there an existing issue for this?

[X] I have searched the existing issues

Description
The attempt to create a new data source from Google Sheets fails when trying to authorize access this happens only in the self-hosted version
Performance Logs
https://user-images.githubusercontent.com/114161539/202267282-15bb7c7a-2f7e-4d2e-9c40-5b3e7f2a432d.mp4
Steps To Reproduce
To reproduce the Google sheets error, follow these steps

If you previously had an instance of appsmith, cleared its cache, you have to create a new instance

Warning everything you have in your self-hosted will be deleted.
docker ps -a
docker stop <<AppsmithContainerID>>
docker rm <<AppsmithContainerID>>
ls
sudo rm -rf stacks
docker-compose up -d

https://user-images.githubusercontent.com/114161539/204024361-ae33b098-7bc1-440d-9db5-c0f55c15bca9.mp4

Once you have re-run self-hosted create a new application.
Try adding a Google Sheets data source.
Try to authenticate the Google sheets data source, and you will see the error.

Public Sample App
No response
Issue video log
No response
Version
Self hosted: Appsmith Community v1.8.8
Self hosted: Appsmith Community v1.8.6
 Front conversations

Update the steps to follow to reproduce this issue

Investigated this issue and found that the issue occurred because the self hosted instance was not able to register itself with the cloud services. This issue has been already addressed by this PR raised by @nidhi-nair . Moving this issue to QA for verification.
Steps shared by @felix-appsmith and tested by me to reproduce the issue on my local setup:

docker system prune -a
docker rmi $(docker images | grep 'appsmith')
curl -L https://bit.ly/3AQzII6 -o $PWD/docker-compose.yml
docker-compose up -d

Closing the issue after testing it on the release as I was unable to repro the issue


allow_unknown in schema dict broken

The cerberus documentation gives an example of setting allow_unknown in your schema dictionary.  However, even when following the example verbatim, cerberus chokes
https://cerberus.readthedocs.org/en/latest/#allowing-the-unknown
from cerberus import Validator
v = Validator()
schema = {
  'name': {'type': 'string'},
  'a_dict': {
    'type': 'dict',
    'allow_unknown': True,
    'schema': {
      'address': {'type': 'string'}
    }
  }
}
v.validate({'name': 'john', 'a_dict':{'an_unknown_field': 'is allowed'}}, schema)

produces
cerberus.cerberus.SchemaError: unknown rule 'allow_unknown' for field 'a_dict'

Hello, on which Cerberus version are you?

$ pip show cerberus
Name: Cerberus
Version: 0.8.1

This is fixed in 0.8.2-dev, see https://github.com/nicolaiarocci/cerberus/issues/75. Can you please try to pull from that and see if it works for you? I just tried with your example and it seems to be working fine. Thanks.


Make Exceptions Serializable

Description
Currently AssertFailedException, AssertInconclusiveException, InternalTestFailureException, and UnitTestException are not marked serializable.
This presents a problem when executing tests in an different AppDomain. Since the exceptions are not serializable the runtime can't move them between app domains and throws SerializationException.
AB#1575813

I've since been working on other projects. @cltshivash and @jayaranigarg would be good contacts to help get traction on this.

We need a bit of investigation but maybe we will have to wait for the v3 as SerializableAttribute isn't available in portable class libs.


[DEVOPS-850] use fully static linking for cardano on darwin

Description

Linked issue
https://iohk.myjetbrains.com/youtrack/issue/DEVOPS-850
Type of change

[ ] 🐞 Bug fix (non-breaking change which fixes an issue)
[ ] 🛠 New feature (non-breaking change which adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🏭 Refactoring that does not change existing functionality but does improve things like code readability, structure etc
[ ] 🔨 New or improved tests for existing code
[ ] ⛑ git-flow chore (backport, hotfix, etc)

Developer checklist

[ ] I have read the style guide document, and my code follows the code style of this project.
[ ] If my code deals with exceptions, it follows the guidelines.
[ ] I have updated any documentation accordingly, if needed. Documentation changes can be reflected in opening a PR on cardanodocs.com, amending the inline Haddock comments, any relevant README file or one of the document listed in the docs directory.

Testing checklist

[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

QA Steps

Screenshots (if available)

after a 2 day bisect of nixpkgs, i tracked down why the binary went from 90mb to 140mb
https://github.com/NixOS/nixpkgs/commit/970f2b5063ba59aed2583a9741e79658a92d7656 Revert "justStaticExecutables: enable -dead_strip on mac to shrink closure


Updating to new faker library

Updating dep.
Fixing issue #18

Ahh still had a working version of faker-factory in my path... Hoping into a virtual env to fix this.

Had to update the init.py to pass flake8. Also it looks like the new Faker may have issues on python 2.6 so I backed out the upgrade and pinned to the old version of faker-factory. Figured this way maintainers can decide when to upgrade and when not to.

Looks like it might not matter and you may want to just drop python 2.6 support anyway. I'll leave for maintainer to comment

i'm okay with dropping 2.6 support. 2.7 has been out for an extremely long time.

Implemented. I also dropped the 2.6 check from travis to get the green build. We probably should have dropped the 2.6 from the setup.py as well.

nice! if you could just drop the 2.6 from setup.py i'll be happy to merge this and create a new release :)

actually, there are a few more 2.6-specific workarounds in the travis config file that could probably be removed/fixed as well. i can fix them myself after merge though.

Done

thanks!


First TODO on old buffer is not deleted on carryover

When I have a TODO entry on the previous day as the first node of a tree, like this:
* Saturday, 02/22/2020
** TODO FOO
** 16:47 Working on something
    blablabla

When I call org-journal-new-entry, which in turns calls org-journal-carryover-items, it adds the **TODO FOO before the new entry (as expected), BUT it does not deletes the ** TODO FOO from the old file.
Therefore, if I call org-journal-new-entry again, the TODO is added once again, as the gif below shows.

Git bisect lead me to this:
fb989163c60ea0c931e9d317c364af7a511d08fe is the first bad commit
commit fb989163c60ea0c931e9d317c364af7a511d08fe
Author: Christian Schwarzgruber<EMAIL_ADDRESS>Date:   Sun Feb 16 09:20:14 2020 +0100
    Add option to delete empty entry/file after carryover operation (Default never)
 org-journal.el | 90 +++++++++++++++++++++++++++++++++++++++++++++++-----------
 1 file changed, 73 insertions(+), 17 deletions(-)

Looking at the code I wonder why the org-journal-carryover is taking the cdr of entries:
    ;; Delete carryover items
    (with-current-buffer prev-buffer
      (mapc (lambda (x)
              (kill-region (car x) (cadr x)))
            (reverse (cdr entries)))

Maybe this should be (reverse entries) instead of (reverse (cdr entries))?
GNU Emacs 27.0.60 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.13, cairo version 1.17.3) of 2020-02-02

That won't work for:
** Parent heading
*** TODO adsasdf

There is a little bit more broken. Carryover functionality needs to be redesign a little.

Thanks for the report @vitorqb. Should work now 0761967


[feature] Apple Pencil Support on iPad

Woe to you, oh earth and sea
For the Devil sends the feature with wrath
Because he knows the time is short
Let him who hath understanding reckon the number of the feature
For it is a human number
Its number is six hundred and sixty-six

While it's technically feasible to use the Apple Pencil to draw on the canvas things like palm rejection and pressure sensitivity aren't present, this makes it hard to use the new pressure sensitivity tools from this tweet on iPad.
https://twitter.com/steveruizok/status/1521493624508276737?s=20&t=-nImuXfXAsYgWX3befrUKw
This post would suggest there is a means to get the 'force' of a touch within Safari that should allow for this pressure to be read with the pencil. https://developer.apple.com/forums/thread/31124

what's this new repo tldraw-v1, is this repo on route to being archived? I see a separate repo now named as tldraw: https://github.com/tldraw/tldraw/ - wondering if it's some change which has happened recently? @TodePond (atleast i don't personally remember seeing this tldraw-v1 repo earlier, though I might be wrong)

thanks for the info, look forward to the blog post! @TodePond


Update code for Character Names

The CharacterName class should be updated to handle the following.

Recognizing element order for handling structures that include nicknames.
Better class structure for non-titled roles like 'self' or 'narrator'.
Add test POC tool to display actor roles
Provide ways to present both full name, and formal expression of full name ("Bob Aliceton" vs "Professor Bob Aliceton")

Code updated.
Multiple classes now available to improve code management and readability.
Proof of concept tool added to display character roles for every movie in a library.
Also found a suitable workaround against the pylint warning "too-many-branches" and "too-many-instance-attributes".
https://github.com/cjcodeproj/medialibrary/commit/2fcbba387ef8bf5eb4012b54bb7a693b3ffd86b5


Lottie Slot Feature Support

Internal model & parser changes to parse "sid" and obtain their data into the LottieComposition.
It will support dynamic-change following lottie objects:

LottieSolidStroke
LottieSolidFill
LottieGradientStroke
LottieGradientFill
LottieTextDoc

Related: #1808

@tinyjin thanks for your update, please check my comments.

Imagine one another scenario, if the user intends to cancel the override of the slot by using:
animation->override(nullptr);

Imagine one another scenario, if the user intends to cancel the override of the slot by using:
animation->override(nullptr);

@hermet Sounds good.
And wondering:

We discussed this overriding features shouldn't take a memory to record what's overrided.
Do we have efficient way to clear overridden status without saving changes?

Please check this: https://github.com/thorvg/thorvg/pull/1998
LottieSlot
{
  LottieProperty::Type type;
  char* sid;
  LottieProperty* property  //we can backup the origin here:
};

Probably you can make the slot rewind the sequence with the original property in LottiSlot.

@tinyjin Please check more comments. thanks!

+please rebase the branch as well.

https://github.com/thorvg/thorvg/pull/2003


Split metadata parsing into a module

In preparation to vendoring Metadata23 from https://github.com/PyO3/python-pkginfo-rs/blob/main/src/metadata.rs for https://github.com/astral-sh/uv/pull/7475#pullrequestreview-2323104398 .
The logic itself stayed the same, I split the code into modules and renamed Metadata23 to MetadataResolver to free Metadata23 for the full core metadata 2.3 we use for uploading.

Since this is blocking the whole stack, I'll merge this now and follow up if needed.


Publishing an sqlproj creates database unpromptedly

Azure Data Studio Version: 1.33.1
OS Version: inwdows 10

Steps to Reproduce:

Create a new sqlproject
Right click on root of project, click on "Publish"
The dialog that appears contains the name of the project as the target database before any target server is selected
if the user quickly enough selects the server to which to deploy the database, the name of the sql project stays in selection and is used as the basis for the creation of an entirely new database in azure, generating cost without prompting user

@adriennn the current behavior is by design and the same behavior as SSDT. If the selected connection is to a specific database on the server, then the default database name gets replaced with that instead of the project name.
Is there an alternative behavior that you would prefer?

hello @kisantia

Is there an alternative behavior that you would prefer

if the user interface allows for deploying a new resource by inadvertence then definitely an alternative behavior is needed, in this case, perhaps like so:

Publish button is disabled
User selects a server
UI waits for database list from server
if there are no database on servers, enable Publish button with label "Publish to New Database"
if there is a database on the server, enable publish button to with label "Publish"


Fix to call the duplicator's child stream subscriber methods by the correct executor

Motivation:
Subscriber methods must be called by the executor that is specified when subscribing to a StreamMessage. However, the methods of the duplicator's child stream subscriber are currently being called from the duplicator's executor, which is incorrect.
Modifications:

Updated the implementation to ensure that the duplicator's child stream subscriber methods are called by the correct executor as specified during subscription.

Result:

The duplicator's child stream subscriber methods are now called by the correct executor.

Static analysis was not easy because two executors were used together in StreamMessageProcessor. How about refactoring the implementation later to delegate the logic to DownstreamSubscription if DownstreamSubscription.executor is needed?

That's a good suggestion. 👍 Addressed it from this PR. :wink:

Thanks for the quick review. 🙇
I'll test it with the snapshot version to ensure the problem is fixed.


一人血书添加设置device的功能

You can select the device by setting the CUDA_VISIBLE_DEVICES environment variable before running the code, such as CUDA_VISIBLE_DEVICES=1 python your_code.py to use the second GPU. I will add the option to specify the device when adding the DistributedDataParallel in the future (I am not considering it now because I mainly only have GPU).


Doc: make the Readme great again

Fix wrong mapping between rule ID and rule definition
Add missing rule
Correct numbering in various sections

@guillaumeVilar fixed various spelling mistakes in your fork and noticed we made a typo on one of our rules, delemeter vs. delimiter.
PR #39 should be merged before we merge this one!

@guillaumeVilar fixed various spelling mistakes in your fork and noticed we made a typo on one of our rules, delemeter vs. delimiter.
PR #39 should be merged before we merge this one!
@carlbuchmann - thanks!
It is being fixed in the pylint PR already

and wrong Guillaume ;) I am @gmuloc


weapons to add

I have a list of things I want to add as weapons from suggestions and my own notes.

[ ] tim: snark, superior, pretentious
[ ] adelie: toboggan, POTATO, circadian
[ ] with alligators: shock, dangerous, inconvenient
[ ] ghosts: haunt, ???, ???
[ ] Python: interpret, ???, ???
[ ] python: constrict, ???, ???
[ ] compact view: ???, ???, ???
[ ] k: ???, ???, ???
[ ] k-node: ???, ???, ???
[ ] n: ???, ???, ???
[ ] n-node: break, elusive, undefined
[ ] holes: ???, ???, ???
[ ] peter: ???, ???, ???
[ ] joel: ???, ???, ???
[ ] spider: ???, ???, ???
[ ] monkey: ???, ???, ???
[ ] Spider: ???, ???, ???
[ ] Monkey: ???, ???, ???
[ ] Meta: ???, ???, ???
[ ] meta: ???, ???, ???
[ ] Objects: ???, ???, ???
[ ] suggestions: ???, ???, ???
[ ] california: ???, ???, ???
[ ] golf: ???, ???, ???
[ ] the ocean: ???, ???, ???
[ ] Bard: ???, ???, ??? ***
[ ] bard: ???, ???, ???
[ ] sleep: ???, ???, ???
[ ] time: ???, ???, ???
[ ] laziness: ???, ???, ???
[ ] Kevin Bacon: ???, ???, ???
[ ] penguins: ???, ???, ???
[ ] cryptocurrency: ???, ???, ???
[ ] GPT: ???, ???, ???
[ ] chat j'ai pété: fart, ???, ???
[ ] income: ???, ???, ???
[ ] tea: ???, ???, ???
[ ] landlord: ???, ???, ???
[ ] property: ???, ???, ???
[ ] capital: ???, ???, ???
[ ] opportunity: ???, ???, ???
[ ] foundation: ???, ???, ???
[ ] user: ???, ???, ???
[ ] news: ???, ???, ???
[ ] conclusion: ???, ???, ???
[ ] imagination: ???, ???, ???
[ ] population: ???, ???, ???
[ ] health: ???, ???, ???
[ ] ear: ???, ???, ???
[ ] problem: ???, ???, ???
[ ] impression: ???, ???, ???
[ ] impressionism: ???, ???, ???
[ ] personality: ???, ???, ???
[ ] soup: ???, ???, ???
[ ] people: ???, ???, ???
[ ] location: ???, ???, ???
[ ] attention: ???, ???, ???
[ ] boyfriend: ???, ???, ???
[ ] exam: ???, ???, ???
[ ] winner: ???, ???, ???
[ ] clothes: ???, ???, ???
[ ] proposal: ???, ???, ???
[ ] growth: ???, ???, ???
[ ] sympathy: ???, ???, ???
[ ] empathy: ???, ???, ???
[ ] reality: ???, ???, ???
[ ] orange: ???, ???, ???
[ ] ability: ???, ???, ???
[ ] psychology: ???, ???, ???
[ ] series: ???, ???, ???
[ ] patience: ???, ???, ???
[ ] art: ???, ???, ???
[ ] accident: ???, ???, ???
[ ] promotion: ???, ???, ???
[ ] library: ???, ???, ???
[ ] chocolate: ???, ???, ???
[ ] fishing: ???, ???, ???
[ ] fish: ???, ???, ???
[ ] catfish: ???, ???, ???
[ ] relationship: ???, ???, ???
[ ] effort: ???, ???, ???
[ ] recipe: ???, ???, ???
[ ] device: ???, ???, ???
[ ] success: ???, ???, ???
[ ] gene: ???, ???, ???
[ ] replacement: ???, ???, ???
[ ] combination: ???, ???, ???
[ ] combinatorics: ???, ???, ???
[ ] number theory: ???, ???, ???
[ ] number theorist: ???, ???, ???
[ ] attitude: ???, ???, ???
[ ] night: ???, ???, ???
[ ] marriage: ???, ???, ???
[ ] agency: ???, ???, ???
[ ] dirt: ???, ???, ???
[ ] permission: ???, ???, ???
[ ] reception: ???, ???, ???
[ ] gate: ???, ???, ???
[ ] gatekeep: ???, ???, ???
[ ] goat: ???, ???, ???
[ ] GOAT: ???, ???, ???
[ ] concept: ???, ???, ???
[ ] fortune: ???, ???, ???
[ ] hat: ???, ???, ???
[ ] requirement: ???, ???, ???
[ ] negotiation: ???, ???, ???
[ ] digraph: ???, ???, ???
[ ] person: ???, ???, ???
[ ] republic: ???, ???, ???
[ ] outcome: ???, ???, ???
[ ] collection: ???, ???, ???
[ ] presence: ???, ???, ???
[ ] flight: ???, ???, ???
[ ] tradition: ???, ???, ???
[ ] volume: ???, ???, ???
[ ] actor: ???, ???, ???
[ ] magazine: ???, ???, ???
[ ] zine: ???, ???, ???
[ ] union: ???, ???, ???
[ ] employee: ???, ???, ???
[ ] reflection: ???, ???, ???
[ ] delivery: ???, ???, ???
[ ] selection: ???, ???, ???
[ ] wedding: ???, ???, ???
[ ] government: ???, ???, ???
[ ] writing: ???, ???, ???
[ ] laser: ???, ???, ???
[ ] dinosaur: ???, ???, ???
[ ] laser dinosaur: ???, ???, ???

Weapon suggestions: The Mace of Obviousness and the Spear of Opinion


Compact terminal without blank lines

Is it possible to remove the blank lines when displaying terminal sessions? For example, it looks like this:
julia> using DualNumbers

julia> a = Dual(3,1);

julia> b = Dual(2,0);

julia> log(a*b + max(a,2))
2.1972245773362196 + 0.3333333333333333ɛ

but I'd like something like this:
julia> using DualNumbers
julia> a = Dual(3,1);
julia> b = Dual(2,0);
julia> log(a*b + max(a,2))
2.1972245773362196 + 0.3333333333333333ɛ

I think this can be done by changing line 207 of run.jl to use rstrip:
result = ChunkOutput(str_expr, rstrip(out), report.cur_result, report.rich_output, figures)

though this is probably not what we want as the default behavior.

You could add this as a chunk option, but the default should look like Julia terminal. If you need this urgently I suggest you'll make a pull request.


IPFS Desktop - Folders not uploading

OS: macOS, Catalina 10.15.6
Version of IPFS Desktop 0.12.2

Describe the bug
The desktop downloads and installs. Importing individual files one at a time seems to work fine. I was also able to upload a couple of folders but then I continually get the message "Failed to add files to IPFS. Please try Again.

I have tried dragging and dropping folders. When I drag my folders I get the green "+" sign and it looks like I am good but then it fails. I use the upload button with the same effect.
Also, I have tried with small folders and large folders. Same result.
To Reproduce
Steps to reproduce the behavior:

In the Files tab click the Import button
Select Folder
Select the desired folder and click Open
Depending on the folder size there is a wait time and then the error message "Failed to add files to IPFS. Please try again."

Additional context
I use a VPN, could that be affecting anything? Also, I have tried this with locally saved folders on my hard drive as well as folders saved in the cloud. Same result.

<!--
ATTACH LOGS

Hi @gohub12 - thanks for flagging this. A few quick questions:

Are you able to add files/directories successfully via the command line?
Are you trying to add particularly large files/directories? There's a known issue in Desktop with items over 2GB, but a fix is very near.

Hi Jessica,
The size of the folders I have been trying to move are 750 MB and 2.2 GB. I just tried a small folder (750 KB) and it copied no problem.
I have not tried the command line but I will and let you know if that works for larger folders.
Thanks.
Rob Harper (gohub12)
Tel:<PHONE_NUMBER>
Email<EMAIL_ADDRESS>On Sep 3, 2020, at 12:00, Jessica Schilling<EMAIL_ADDRESS>wrote:

Hi @gohub12 - thanks for flagging this. A few quick questions:
Are you able to add files/directories successfully via the command line?
Are you trying to add particularly large files/directories? There's a known issue in Desktop with items over 2GB, but a fix is very near.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@gohub12 -- thanks for the info. I'm ccing @lidel and @rafaelramalho19 for more context, but we may be running into the large-file issue here. Let us know how you get by with the command line, and apologies for the inconvenience; it'll be temporary!

This was fixed in https://github.com/ipfs-shipyard/ipfs-webui/pull/1534 and  is scheduled to be fixed in v2.11


Please change the description

I'd like to have all in this repository in English. Could you plese change the description of this repository to:
Python library converting CityGML to printable STL

Thanks.

+1

OK, closing.

Well, I still see Skupina F (akademický rok 2014/2015)

fixed

Could it please be
Python library converting CityGML to printable STL

as stated in the issue description?

bump?

done

Thank You


imp: add proper nix patching

It is very likely that some digga functionality requires patches to nix
Create a place for patches that mimicks the way how they could be
applied once inputs.<name>.patches of the
UFR (Unofficial Flakes Roadmap) is implemented.
Also showcase how nixConfig can add extra feature flags (without
overriding the patched-in ones).

Im against adding a patched nix as the default for digga. Nix takes a while to compile for me and im certain for others. I don't want to wait almost an hour just to switch configurstions. I think the proper solution is to just not rely on the follows fix until its actually merged into upstream.
And since nixlib and deploys overlay the extra dependency isnt that big of an issue.

Nix takes a while to compile for me and im certain for others

Oh yeah, this is really, really annoying. I was hoping that maybe we could take a pinned nix inputs and then ask @nrdxp to provide a proper cached binary...
I guess we will be in need of some flexibility w.r.t. nix in the weeks to come. I don't possess proof, it's just a sentiment I have judging by the amount of people actually trying to fix things and the current upstream review capacity.

I guess we will be in need of some flexibility

Except for running lock --update-input, there is no reason to add it as default.
So, how about the patched-nix in commands of devshell.
 [[commands]]
   2 name = "patchedNix"
   1 command = "nix run github:<repo>#patchedNixUnstable -- $@"
   4 help = "Run Patched Nix"

Except for running lock --update-input, there is no reason to add it as default.

This is a good point, but I think you would still run into an issue with nix complaining about an input following another non-existent one during other calls of nix, because nix reads the lock file on every call.

input following another non-existent one during other calls of nix, because nix reads the lock file on every call.

As far as my experiemtns got me during the last couple of days, a well-crafted flake.lock file can be consumed by a non-compliant nix as well. That is: the file is correctly read. The only issue is while updating.

bors try

bors try

Note this only exposes what's already used for the devshell. It's up to the consumer to use it.


syz-ci: add kernel_src_suffix field to config

This is used to add a suffix to the kernel_src config field. This is used in Android where kernel source is under .../kernel/aosp/.

Addressed comments.


bundle: nice UX around disconnected setup

Feature Request
Describe the problem you need a feature to resolve.
A bundle's CSV supports "related image" configuration at the catalog level, which effectively establishes a pointer from some static image label to a resolved (i.e. contains the image's remote digest) image tag. Such config is crucial for disconnected clusters due to image proxying.
Related image config can be done via .spec.relatedImages (see #https://github.com/operator-framework/operator-sdk/issues/4884) or setting a RELATED_IMAGE_{name} environment variable. The latter is recommended, since OSBS will populate .spec.relatedImages from env vars matching the aforementioned pattern.
Describe the solution you'd like.
A kustomize configuration can "teach" filters to apply transformers to particular field sets. The following setup will substitute images set with kustomize edit set image key=value into .spec.relatedImages and RELATED_IMAGE_* env vars with the right key:
# config/manifests/relatedimages_config.yaml
images:
# For .spec.relatedImages
- path: spec/relatedImages[]/image
  create: true
# For env vars
- path: spec/install/spec/deployments[]/spec/template/spec/containers[]/env[]/value
  create: true

# config/manifests/kustomization.yaml
...
configurations:
- relatedimages_config.yaml

# This transformer makes sure the deployment name is set with the right prefix.
# The resulting value will be important for CSV parsing by 'operator-sdk generate bundle'.
transformers:
- |-
  apiVersion: builtin
  kind: PrefixSuffixTransformer
  metadata:
    name: notImportantHere
  prefix: memcached-operator-
  fieldSpecs:
  - path: spec/install/spec/deployments[]/name
    create: false
    kind: ClusterServiceVersion
    group: operators.coreos.com
    version: v1alpha1

Note: You would not actually want both .spec.relatedImages and RELATED_IMAGE_* configuration options present because the latter will not overwrite the former. I put forth both in the same issue because discussion is needed on which to support.
Given the below base CSV, you can run kustomize edit set image controller=foo.com/bar@sha256:1234 to create a kustomization.yaml image transformer that maps reference controller to foo.com/bar@sha256:1234. When you run kustomize build config/manifests, you will see a CSV with the expected image reference updates.
config/manifests/bases/memcached-operator.csv.yaml contents
apiVersion: operators.coreos.com/v1alpha1
kind: ClusterServiceVersion
metadata:
  annotations:
    alm-examples: '[]'
    capabilities: Basic Install
  name: memcached-operator.v0.0.0
  namespace: placeholder
spec:
  apiservicedefinitions: {}
  customresourcedefinitions:
    owned:
    - description: Memcached is the Schema for the memcacheds API
      displayName: Memcached
      kind: Memcached
      name: memcacheds.cache.example.com
      version: v1alpha1
  description: Memcached Operator description. TODO.
  displayName: Memcached Operator
  icon:
  - base64data: ""
    mediatype: ""
  install:
    spec:
      deployments:
      - name: controller-manager
        spec:
          template:
            spec:
              containers:
              - name: manager
                env:
                - name: RELATED_IMAGE_FOO_BAR
                  value: controller
                - name: SOME_ENV
                  value: foo
    strategy: deployment
  installModes:
  - supported: false
    type: OwnNamespace
  - supported: false
    type: SingleNamespace
  - supported: false
    type: MultiNamespace
  - supported: true
    type: AllNamespaces
  keywords:
  - memcached-operator
  links:
  - name: Memcached Operator
    url: https://memcached-operator.domain
  maintainers:
  - email<EMAIL_ADDRESS>    name: Maintainer Name
  maturity: alpha
  provider:
    name: Provider Name
    url: https://your.domain
  version: 0.0.0
  relatedImages:
  - image: controller
    name: foo_bar

@@ -23,17 +23,17 @@
   install:
     spec:
       deployments:
-      - name: controller-manager
+      - name: memcached-operator-controller-manager
         spec:
           template:
             spec:
               containers:
               - name: manager
                 env:
                 - name: RELATED_IMAGE_FOO_BAR
-                  value: controller
+                  value: foo.com/bar@sha256:1234
                 - name: SOME_ENV
                   value: foo
     strategy: deployment
   installModes:
   - supported: false
@@ -56,7 +56,7 @@
   provider:
     name: Provider Name
     url: https://your.domain
   version: 0.0.0
   relatedImages:
-  - image: controller
+  - image: foo.com/bar@sha256:1234
     name: foo_bar

To support env vars, some changes are needed in operator-sdk generate bundle, namely the ability to merge RELATED_IMAGE_* variables into the correct Deployment. This should not be difficult given Deployments and their containers have unique names in this context.

Important: I have created this issue here and not upstream because these are OCP-specific changes; afaik, OSBS is not available in vanilla k8s clusters, and related images usage outside of OCP is not documented.
Furthermore, changes to OLM may obviate or create better alternatives to the above suggestions.

/kind feature

Using the described setup, you can run
kustomize edit set controller=foo.com/bar:v1.0.0
make bundle

to update referenced images that can be resolved at runtime, or
kustomize edit set controller=$(docker inspect --format '{{index .RepoDigests 0}}' foo.com/bar:v1.0.0)
make bundle

to resolve and pin images yourself.


File not found: main.js

I just updated to the latest version of action-release and am receiving the following error. I'm not sure whether this is due to a problem in action-release, or because I did not specify the file argument (I don't want to attach any files to this release):
Run<EMAIL_ADDRESS>  with:
    changelog: changelog/CHANGELOG.md
  env:
    GITHUB_TOKEN: ***
##[error]File not found: '/home/runner/work/_actions/yakuhzi/action-release/v1.2.2/dist/main.js'

Downgrading to<EMAIL_ADDRESS>fixed my issue.
However then I received this warning:

Unexpected input 'changelog', valid inputs are ['file', 'changelogs']

Despite this warning, my changelog did appear in the release description.

Could you check if the issue is also present, if you use yakuhzi/action-release@v1?
It should also point to the latest release, but this one is working for me.
Regarding the warning: Back in v1.2.0 there was a typo in the action.yml file, where it says changelogs instead of changelog, but in code it was always changelog. This was fixed in 2ecf7e0d40ccb4cc77631dbca8c56f64f2731ac4.

I 'downgraded' to yakuhzi/action-release@v1 and everything is now working perfectly. There are no errors or warnings, and the changelog appears in the release.

I just found out the issue: The tag v1.2.2 was pointing to the master branch instead of the releases/v1 branch where the dist files are available.


[Feature Request] autocomplete=false for python runtime

Issue Transfer
This issue has been transferred from the Azure SDK for .NET repository, #27975.
Please be aware that @zargaryanlilit  is the author of the original issue and include them for any questions or replies.
Details
As described in the documentation here we don't have the ability to set autocomplete false for servicebus triggered functions (python runtime). Furthermore, there is no way to manage the lifetime of the message (deadletter or abandon the message) as the received message object is of type ServiceBusMessage. Having this feature will give as more flexibility while continuing to rely on servicebus binding.

Depends on: #37818.

@jsquire Can you please confirm the status of the request? This is very critical for our business applications running on Service bus trigger Python SDK.Thanks

@sudharsan2020 :  I have no insight into the status or plans.   You'd need to ask the assigned engineer, @YunchuWang.

@YunchuWang Do you've any plans to release this feature shortly? Please let me know.


babel: command not found

When I try to install the hapi-serve-s3, the npm returns: sh: babel: command not found.
➜  ryu git:(master) ✗ npm install hapi-serve-s3 --save

><EMAIL_ADDRESS>postinstall /Users/forma/Dev/node/ryu/node_modules/hapi-serve-s3
> npm run build

><EMAIL_ADDRESS>build /Users/forma/Dev/node/ryu/node_modules/hapi-serve-s3
> rm -rf ./dist && babel -d ./dist ./src -s

sh: babel: command not found

npm ERR! Darwin 15.3.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
npm ERR! node v4.2.2
npm ERR! npm  v3.8.6
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR<EMAIL_ADDRESS>build: `rm -rf ./dist && babel -d ./dist ./src -s`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script 'rm -rf ./dist && babel -d ./dist ./src -s'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the hapi-serve-s3 package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     rm -rf ./dist && babel -d ./dist ./src -s
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs hapi-serve-s3
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls hapi-serve-s3
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/forma/Dev/node/ryu/node_modules/hapi-serve-s3/npm-debug.log
npm WARN<EMAIL_ADDRESS>No repository field.
npm ERR! Darwin 15.3.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "hapi-serve-s3" "--save"
npm ERR! node v4.2.2
npm ERR! npm  v3.8.6
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>postinstall: `npm run build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'npm run build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the hapi-serve-s3 package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs hapi-serve-s3
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls hapi-serve-s3
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/forma/Dev/node/ryu/npm-debug.log

Is babel dependency of project? Can we add this in package.json?

Hey thanks for that, it's fixed in v1.0.1 and should hopefully be published to npm soon :smile:

Sorry! Forgot to publish v1.0.1 to npm yesterday. Should be up now.

+1


Move everything under project accounts (heroku, firebase)

Please make the installs in project heroku and firebase accounts.

OK!


fix: fix invalid style of log messages and exclude underscores

Summary
This PR fixes the following invalid style:

Error messages should start with lowercase, do not use UPPERCASE.
Do not declare variable and function names with underscores.

Test Plan

[ ] acceptance tests

@mnagaa thank you for your contribution!


added the xWindowsUpdateAgent resource with tests and readme updates

@HemantMahawar should review before merged

This change is

DscResources/MSFT_xWindowsUpdateAgent/MSFT_xWindowsUpdateAgent.schema.mof, line 3 [r2] (raw file):
@HemantMahawar should review before merging

Comments from the review on Reviewable.io

Review status: 0 of 6 files reviewed at latest revision, 6 unresolved discussions.

README.md, line 27 [r3] (raw file):

* **UpdateNow**: Indicates if the resource should trigger an update now.
* **Category**: Indicates the categories of updates the resource should update for.  'Security', 'Important', 'Optional' (please note that security is not mutually exclusive with Important and Optional, so selecting Important may install some security updates, etc.)
* **Notifications**: Sets the windows update agent notification setting.  Support options are 'disabled' and 'ScheduledInstallation'.  [Documentation from Windows Update](https://msdn.microsoft.com/en-us/library/windows/desktop/aa385806%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396)

Typo Support should be "Supported"
Categories should add (one or more)

README.md, line 121 [r3] (raw file):

Set Windows Update Agent to use Microsoft Update.
Disables notification of future updates.
Install all Security and Important updates from Microsoft Update.

Call out UpdateNow = $true in the comments

README.md, line 126 [r3] (raw file):

Configuration MuSecurityImportant
{
    import-dscresource -ModuleName xWindowsUpdate

Fix the casing of import-dscresource
Aligning = in each resource block will be appreciated

DscResources/MSFT_xWindowsUpdateAgent/MSFT_xWindowsUpdateAgent.schema.mof, line 12 [r3] (raw file):

        Values{"Disabled","ScheduledInstallation"}] String Notifications;
    [Write, Description("Indicates which service Windows update agent should use.  Note: WSUS is not implemented in this resource."), ValueMap{"WindowsUpdate","MicrosoftUpdate","WSUS"},
        Values{"WindowsUpdate","MicrosoftUpdate","WSUS"}] String Service;

Make it required
Call it Source

DscResources/MSFT_xWindowsUpdateAgent/MSFT_xWindowsUpdateAgent.schema.mof, line 13 [r3] (raw file):

    [Write, Description("Indicates which service Windows update agent should use.  Note: WSUS is not implemented in this resource."), ValueMap{"WindowsUpdate","MicrosoftUpdate","WSUS"},
        Values{"WindowsUpdate","MicrosoftUpdate","WSUS"}] String Service;
    [Required, Description("update now")] boolean UpdateNow;

Change it to write with default as $false

Comments from Reviewable

Review status: 0 of 6 files reviewed at latest revision, 7 unresolved discussions.

README.md, line 25 [r3] (raw file):

### xWindowsUpdateAgent

* **UpdateNow**: Indicates if the resource should trigger an update now.

Don't have a suggestion, but  should think of better name for this property.
Currently, it doesn't clearly specify that it will sync/trigger a check with the source each time this resource runs

README.md, line 27 [r3] (raw file):
Previously, HemantMahawar (Hemant Mahawar) wrote…
> Typo Support should be "Supported"
> Categories should add (one or more)
Default for Category should be 'Security'

Comments from Reviewable

Review status: 0 of 6 files reviewed at latest revision, 7 unresolved discussions.

README.md, line 27 [r3] (raw file):
Previously, HemantMahawar (Hemant Mahawar) wrote…
> Default for Category should be 'Security'
Done.

README.md, line 121 [r3] (raw file):
Previously, HemantMahawar (Hemant Mahawar) wrote…
> Call out UpdateNow = $true in the comments
Done

README.md, line 126 [r3] (raw file):
Previously, HemantMahawar (Hemant Mahawar) wrote…
> Fix the casing of import-dscresource
> Aligning = in each resource block will be appreciated
Done

DscResources/MSFT_xWindowsUpdateAgent/MSFT_xWindowsUpdateAgent.schema.mof, line 12 [r3] (raw file):
Previously, HemantMahawar (Hemant Mahawar) wrote…
> Make it required
> Call it Source
Done

DscResources/MSFT_xWindowsUpdateAgent/MSFT_xWindowsUpdateAgent.schema.mof, line 13 [r3] (raw file):
Previously, HemantMahawar (Hemant Mahawar) wrote…
> Change it to write with default as $false
Done

Comments from Reviewable

Review status: 0 of 6 files reviewed at latest revision, 6 unresolved discussions.

README.md, line 25 [r3] (raw file):
Previously, HemantMahawar (Hemant Mahawar) wrote…
> Don't have a suggestion, but  should think of better name for this property.
> Currently, it doesn't clearly specify that it will sync/trigger a check with the source each time this resource runs
Reviewed with @brucepay

DscResources/MSFT_xWindowsUpdateAgent/MSFT_xWindowsUpdateAgent.schema.mof, line 3 [r2] (raw file):
Previously, TravisEz13 (Travis Plunk) wrote…
> @HemantMahawar should review before merging
Done.

Comments from Reviewable


Allow input blur when using keyboard for suggestion or term

Hi, first I just want to say thanks for creating and maintaining react-autosuggest. I appreciate all the effort that goes into maintaining an OSS project, 👍
We have a prop focusInputOnSuggestionClick that determines whether the input receives focus when a suggestion is clicked. I am however finding it difficult to blur the input when the user hits ENTER on a suggestion or when wrapping the Autosuggest component in a <form> and handling the onSubmit event.
Is there already a recommended way of doing this or is this issue a feature request?
Thanks for any pointers and thanks again for your time and effort on this project.

Interesting. This is the first time someone asks to blur on Enter. Could you explain the rationale behind this? If you could create a Codepen that demonstrates the issue, that would be great.

The use case is that a user types a search query into a suggest-enabled box and hits enter (or keys down to an item and hits enter). The search is then loaded (this is an single-page-app) and because the search input still has focus, the suggestions show up.
We'd like to blur the input and stop the suggestions showing at that point because they offer little value to a customer who's already seeing search results. Perhaps this is a niche case? I could create a fork and implement this and PR if you're interested in the feature.

@JamieDixon Which version of react-autosuggest are you using? When you hit Enter, suggestions should be hidden like in this Codepen. Could you create a Codepen that demonstrates the issue?

Hi @moroshko Apologies in the delay in replying. I got married on Sunday so things have been quite busy!
The issue I'm having is when the autocomplete is wrapped in a form and we preventDefault on submit. At this point we load our search results (single-page-app) and we need the suggestions to disappear.
Here's an amended version of the pen to illustrate the issue: http://codepen.io/JamieDixon/pen/XdGrZa
Cheers!

@JamieDixon Congrats man!!
I just checked your pen and I see that the suggestions are hidden when you hit Enter. I thought that the issue is that they stay open. What am I missing?

Hey @moroshko Thanks for the congratulations.
In my pen, the suggestions are only hidden if you choose one of the suggested items but not when you just hit enter from the input itself. Perhaps you're seeing different behavior? I'm using Chrome 50.0.2661.94 m.

@JamieDixon Oh, I see!
What you can do, is to grab the input element and blur it yourself when form is submitted. Example

Thanks @moroshko  We also came up with another solution because we're using redux that allowed us to utilise the searchSuggestionsVisible. Additionally, someone on our team is planning to send a PR to contribute back to this project that will allow this functionality. I expect it'll be sent today or tomorrow. Thanks for all your time helping on this. Very much appreciated.

Hi, Thank you for merging this PR so fast..
And @JamieDixon awesome work on this 👍 .
@moroshko Could you cut a release for this please ? :)

@ganarajpr Enjoy!


[FLUME-3423]:Taildir source will throw unnecessay exception when rest…

…art agent

related issue https://issues.apache.org/jira/browse/FLUME-3423

There are 12 open PRs against taildir source. Before applying this I really need to know if this causes any of the other PRs to be moot. Or looking at it from the other perspective, if those PRs are applied what impact will they have on this one.


Fix Signup

fixes #80
This PR fixes the errors within the signup routes in the applications and successfully displays a toast message for successful signup confirmation.

add some video for reference

resolve the conflicts @haseebzaki-07

@gupta-ritik resolved the conflicts

@haseebzaki-07 upadate ??


Create 2 new blog notifications prototypes based on team feedback

Based on #387

This is repeat. Will move to hallway testing next sprint.


[AutoDiff] Add VJP for 'Array.init(repeating:count:)'.

Add a VJP for Array.init(repeating:count:) so that it can be differentiated. The VJP is merely a transpose since init(repeating:count:) is linear w.r.t. the repeated value. Its tranpose is a linear map that takes an Array.TangentVector and returns the sum of all of its elements.
Resolves TF-802.

@swift-ci please test tensorflow


[e2e]: container-based tag main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/v35.0.311
Run: https://github.com/slsa-framework/example-package/actions/runs/7706092746
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.container-based.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.container-based.tag.main.default.slsa3.yml
Trigger: push
Branch: v35.0.311
Date: Tue Jan 30 04:04:59 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v35.0.312
Run: https://github.com/slsa-framework/example-package/actions/runs/7721014870
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.container-based.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.container-based.tag.main.default.slsa3.yml
Trigger: push
Branch: v35.0.312
Date: Wed Jan 31 04:05:22 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v35.0.313
Run: https://github.com/slsa-framework/example-package/actions/runs/7736070572
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.container-based.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.container-based.tag.main.default.slsa3.yml
Trigger: push
Branch: v35.0.313
Date: Thu Feb  1 04:18:52 UTC 2024
Tests are passing now. Closing this issue.


sd image build ends without creating the image

hello,
when running the make command in the sdbuild folder of PYNQ cloned repository with the board path after downloaded the bsp to the folder of this cloned repo the make start to check the environment but after check all the dependencies it ends without any error.
I've done the setup_env.sh previously as the pynq documentation  describe without problem.
also the settings for vivado and petalinux was previously run in the same terminal and the webtalk off.
The thing is the make command works and start to generate the image for the boards in the board folder but I don't want to go in this direction since it takes a lot of time and I'm not sure if I put the zcu208 folder inside it will generate.
any thoughts?
thanks

Hey, is this still an issue? You've provided me with rather little to go on, so is there anything else you could share? Log files for example? Which commands did you invoke? What exactly are you observing, and what did you expect to see?

hi @Yamakaja, thanks for reply.
Since pynq 3.0 officially support the zcu208 this is not needed for me so I didn't try to solve it. but my guess is some package is missing in my setup or something like that and exit without error.
Thanks anyway.


Could not resolve host: api.razorpay.com

An uncaught Exception was encountered
Type: Requests_Exception
Message: cURL error 6: Could not resolve host: api.razorpay.com
Filename: /home/a2zroomz/public_html/testing/rppayment/libs/Requests-1.6.1/library/Requests/Transport/cURL.php
Please help to resolve error

Enable Curl Extension!
If enabled make sure you have configured it to make SSL connections!

This is a connectivity issue, not related to the PHP package itself. Looks like you're unable to make requests to any URL, not just Razorpay (or perhaps you have some whitelisting configured on your end?). Closing this for now, but please re-open if you see reason to believe that the plugin itself is misbehaving.


[share_plus_web] fix various issues

Description

generated missing example runner for web
share_plus_web was not endorsed in share_plus
SharePlugin.registerWith() was creating an instance of the platform interface SharePlatform instead of SharePlugin for web
the workaround for pure Dart desktop plugins had the kIsWeb guard in the wrong place

Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

LGTM thanks!

Thanks for the review! :+1:


Update build.gradle files

Each task requires reconfiguring a build, after Android Gradle plugin update. Is it possible to align all build files for the new Gradle plugin?

That's not a big deal of course, but, it's not a part of the exercises.


Failed to load on 4.17.1

Is that because of my version ?

Have you tried recompiling the plugin?
I ran tests on 4.17 and didn't get any issues.

Haven't heard back from you, so closing the issue for now.


Space before ruleSet name in comma delimited string will ignore ruleSet

If I call Validate with a space after the a comma in the ruleSet string, the subsequent ruleSet is never executed:
ValidationResult = Validator.Validate(entity, ruleSet: "default, Update"); // Update never invoked
if I remove the space it works as expected:
ValidationResult = Validator.Validate(entity, ruleSet: "default,Update"); // Update invoked

Technically you can have a rule whose ruleSet name is " Update" with a leading space, which this would match, so I don't think there's a good argument for changing this except perhaps to output some sort of warning somewhere (but the current library has no policy of where and how to issue run-time warnings based on usage). Personally I wouldn't use a function that accepted a delimited-list in a single string parameter like this unless the list was coming from an external (serialized) source. It would be nice to have a version of Validate( ) that accepted IEnumerable<string> ruleSet instead.

@shuep I've committed a change that trims the ruleset names and this will be in the next release.
@wizofaus You can always use the overload of validate that takes a ValidationContext and pass in a RulesetValidatorSelector directly - it's constructor takes an IEnumerable<string>.


Does Response class of Flask work with this ?

How to change server signature and returning object of Flask.Response will work ?

It uses a custom response class inheriting flask.Flask.response_class. You can change the base class by changing flask.Flask.response_class, default is flask.Resposne.


How create multiple view type with realm

Hello,
I have multiple realm items but how to bind it with adapter.

You have to use the GenericItemAdapter with the Function interface. https://github.com/mikepenz/FastAdapter/blob/develop/library-core/src/main/java/com/mikepenz/fastadapter/adapters/GenericItemAdapter.java#L32


execute sql appears error in document

SYSTEM RESTART MERGES helloworld.my_first_table;Cannot execute
SYSTEM RESTART GC helloworld.my_first_table;Cannot execute
It appears in the document SYSTEM START CONSUMER helloworld.cnch_kafka_consume;Cannot execute，SYSTEM START CONSUME helloworld.cnch_kafka_consume;Can execute
system.cnch_kafka_tables doesn't exist
Cnchkafka table execute select * from table error，Code: 48. DB::Exception: Received from localhost:9000. DB::Exception: Method read is not supported by storage CnchKafka SQLSTATE: HY000. (NOT_IMPLEMENTED)

thanks @zhbdesign , SYSTEM RESTART MERGES|GC should not be supported. this is document bug.
system.cnch_kafka_tables has not been merged to byconity, we'll add it soon


DCK poc transforms

What changes were proposed in this pull request?
Adding some transforms:

ChangeCaseStringTransform: change case of string column
ConcatenateStringColumns: concatenate multiple string columns into one
StringListToCountsNDArrayTransform: string column to dense BOW NDArray
StringListToIndicesNDArrayTransform: string column to sparse BOW NDArray (i.e., list of indices)

and one Spark function:

WritablesToNDArrayFunction: convert a list of writables to an NDArray

How was this patch tested?
Added unit tests ChangeCaseStringTransform and ConcatenateStringColumns to TestTransforms unit test class. Haven't added unit tests for StringList... transforms.
Please review
https://github.com/deeplearning4j/deeplearning4j/blob/master/CONTRIBUTING.md before opening a pull request.

@huitseeker Nope. Link? But several of these are NDArray specific, and the rest are so simple, I'm not sure it's worth introducing the external dependency...? @AlexDBlack requested I add these, so I'd be interested in hearing his take as well.

Replaced by https://github.com/deeplearning4j/DataVec/pull/340.


/ja/docs/Glossary/Public-key_cryptography

Request type

[ ] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[x] Correction or update

Details

https://developer.mozilla.org/ja/docs/Glossary/Public-key_cryptography
"懸賞" in the second paragraph should be updated to "検証".

Yes, thanks — fixed


Removing the preset keys

Hi! Love your theme. I've got a question though: the suggested way of installing the theme is using git submodules. How would one go about removing the preset keys in theme's config.toml? I don't have twitter/instagram/ello and want to remove them for my site. But hugo insists on merging the two configs, even if I specify just my config. So I end with my links intermixed with links specified in theme's config.toml as an example. Is there a way to remove them without changing the theme files?

Hi there, how is your root config.toml?
I am using this theme at https://hello.bryanalbuquerque.dev/ and Hugo does not merge the "defaults" keys from the theme config.
I am using it as as git submodule at themes/vncnt-hugo and here it is my config.toml at my hugo root directory:
baseURL = "https://hello.bryanalbuquerque.dev/"
buildDrafts = false
buildFuture = false
buildExpired = false
relativeURLs = true
disableRSS = true
enableRobotsTXT = true
languageCode = "pt"
language = "pt"
theme = "vncnt-hugo"
title = "Hello World · Bryan Albuquerque"
_merge = "none"
[permalinks]
  fixed = ":title/"
  posts = "posts/:slug/"
[params]
  author = "Bryan Albuquerque"
  description = "Landing Page"
  bio = "Open Source Technomancer.  \n  DevOps Engineer."
  avatar = "img/avatar.png"
  favicon = "img/favicon.ico"
  error404 = "ERR_404"
  [params.contact]
    github = "https://github.com/bryanasdev000"
    gitlab = "https://gitlab.com/bryanasdev000"
    linkedin = "https://www.linkedin.com/in/bryanasdev000/"
    [params.contact.1]
      name = "blog"
      icon = "globe"
      style = "fas"
      link = "https://blog.bryanalbuquerque.dev"
    [params.contact.2]
      name = "wiki"
      icon = "book"
      style = "fas"
      link = "https://wiki.bryanalbuquerque.dev"

Hi there, how is your root config.toml?

Here's mine: https://github.com/graynk/space/blob/master/config.toml

Hey :) First of all, I appreciate you guys using my theme!
The important line in @bryanasdev000's config is _merge = "none".
@graynk, if you include this line in your config, it should work. A couple of versions ago, Hugo started merging configs by default.
Your config looks like it was copied from an older version of my example config.toml. The current example includes this line.
Also, adding the hardLineBreak extension shouldn't be necessary anymore. If I'm not mistaken a double-space followed by \n should suffice for hard line breaks.
Let me know if this helped.

Hey :) First of all, I appreciate you guys using my theme!
The important line in @bryanasdev000's config is _merge = "none".

Thanks! That's exactly the setting that I was looking for, it works now, thank you


Do we have capability to ignore waiting for response from Pipeline?

In some situations, where the commands in a pipeline is only with 'Updates/Delete's, am actually not interested in the response unless there are any error's. In that case, do we have a way to instruct the pipeline to ignore waiting for response and proceed further?. Tried the 'CLIENT NO REPLY" option, but it still blocking.

Hi @fferozbasha I'm not sure I understand the situation.  When you issue commands in a pipeline they will be completed sequentially and the results added to the clients send buffer.  We do not wait for the result to be transmitted before moving to the next command.  However if we spend too long processing a client we may move on to another in order to ensure fairness (we will eventually get back and complete servicing of the pipeline).

@JohnSully Thanks for the response. Let me put an example. Consider I have created a pipeline with 100 hmset commands. Now with Python client, the code will be as ,
response = pipe.execute()
...next line of code
Now in this scenario, am not interested in the response at all. I understand the the client collects all request and send at once to the server. But post that it is going to get all response and send it back to the client. Only then the 'next line of code' gets executed. I do not want the code to wait for the response back from the server. Just like fire and forget approach. Do you think it is a reasonable ask?

Hi @fferozbasha
There's nothing in KeyDB that forces you to wait for a response before continuing. Unfortunately this is an issue with the library you are using and you'll need to get the modifications there.  If your client is waiting for data to be returned from KeyDB to continue then there isn't a way around it on the server side, e.g. if we didn't send a response at all then your client would just hang.


textarea resize not taking line-height into consideration

When a textarea has a line-height defined for it, the resizing of the textarea does not work properly.
Adding the line-height css attribute fixes this, just below "hiddenDiv.css('box-sizing'....":
            hiddenDiv.css('line-height', $textarea.css('line-height'));

Fixed in ad28884

Is the ad28884 change in materialize  v0.97.6 which is distributed presently ?


Danger and Primary style using the same color

Danger and Primary style are using the same color; Orange #ff7a59.
I think they should use different colors instead of using the same.
Also success and primary are using the same color for other classes 0091ae (--brand-primary and --brand-success)

Thank you for the notices, I've updated danger colors to: #ff5962 and success colors to: #00bda5

So much better now, thanks!
Something else that could be improved is the search bar as of now it blends with the background too much

Do you mean the main search in the upper right?
That bar should be darker like this:

Oh, it's because I am using it with the vertical Sidebar, sorry.

No worries, I will have a look and see if I can fix the vertical sidebar as well but I think we need to find a more suiting color since the vertical navbar is bigger so it may look wierd if it is as dark as the horizontal navbar.

As of now I am really liking the vertical navbar, maybe something that could be improved is the color when an entity is selected in the navbar

I see, maybe we can use the same color and make the buttons white like in the horizontal navbar and add some height to the navbar to give the search input a little more room?

Usually other themes gives a different background to the search box, I don't know if making the whole top navbar dark blue is the best design choice

Agreed, maybe this lighter one could work or do you have a suggestion? :)

This lighter one looks like it fits the style of the theme so well!

I will try to implement it this week so we can get the vertical navbar working :)

Thanks, can't wait! :)

Also something that I noticed,
The primary enum color is different than the primary button color, I think that the enum primary color would fit better for the buttons :) and maybe the current primary would be good for warning buttons/enums as their style was left unchanged.

Also just noticed that the various Espo.Ui banners have all the same color

@Kharg this is something I'm working on right no as well as the height of the notifications :)

@novastream Perfect! :)
Also, the navbar need some polishing regarding the icon selection background

I haven't updated my development enviroment yet but I would like the checkboxes to look something like this:

Yes, this design looks good! :)

@Kharg is there a new checkbox support for 7.3.1? Can't find it?

Closing this issue for now since the initial issue is solved.


How to rotate pawn while teleporting

Hi,
First I must say that great plugin! I do have a question which is how can i control the rotation of the pawn while teleporting? I'm not sure if this is already a built-in feature of the plugin but I am pretty new to this so if it is, can you please show me how to "turn it on". If not, can you maybe give some advice on how can i control the rotation of the pawn while teleporting?
Thanks!

Hi! Thanks for the feedback. you can use the standard Blueprint node "Reset Orientation and Position" to do this.


Structs with mutable properties inside containers can't be mutated

type X =
    struct
    val mutable x : int
    val mutable y : int
    end

let t = ResizeArray([|X();X();X()|])

t.[0].x <- 5

The above example gives an error, though with plain arrays it works. Having the above work would be handy in ensuring data locality in games. I am working on one and am forced to use an oversized plain array with a separate counter as a mutable variable for length. It could be done with reference types, but I am worried they would fragment the memory. Of course, in the game, the struct used for NPC state is significantly larger than 8 bytes.
I've run into this problem before in a different context and there structs could not be mutated through Item set.
Would making the above example work be doable?

This is fundamental to the design of ResizeArray and in fact to the lack of byref returns in .NET IL.  The F# work for this to happen is covered by : https://fslang.uservoice.com/forums/245727-f-language/suggestions/11125137-expand-support-for-byref-to-match-c-7


Installation with pip

Hi Thomas,
I'm hoping to use Scoary2 but during pip installation I am getting the following error:
~ pip install scoary-2
ERROR: Ignored the following versions that require a different python version: 0.0.10 Requires-Python >=3.10,<3.11; 0.0.11 Requires-Python >=3.10,<3.11; 0.0.12 Requires-Python >=3.10,<3.11; 0.0.13 Requires-Python >=3.10,<3.11; 0.0.3 Requires-Python >=3.10,<3.11; 0.0.4 Requires-Python >=3.10,<3.11; 0.0.5 Requires-Python >=3.10,<3.11; 0.0.6 Requires-Python >=3.10,<3.11; 0.0.7 Requires-Python >=3.10,<3.11; 0.0.9 Requires-Python >=3.10,<3.11
ERROR: Could not find a version that satisfies the requirement scoary-2 (from versions: none)
ERROR: No matching distribution found for scoary-2

Any advice on how to proceed with python versions? Thanks for your time!

Hey @jrherr
Scoary2 requires Python 3.10. I just realized that's not very clear in the wiki!
Alternatively, you could use docker.
Best, MrTomRod

Fyi, I also added instructions on how to install the dependencies with conda: https://github.com/MrTomRod/scoary-2/wiki/Installation#conda


Add compartment quotas and usage against quotas

Is your feature request related to a problem? Please describe.
OCI allows to set compartment quotas for various resources.  Right now it is not easy to get a holistic picture of usage of resources against the quota limits.
Describe the solution you'd like
a module to report compartment quotas and usages
Describe alternatives you've considered
Manually checking quotas and usage in console
Additional context
Compartment quotas are used by organizations to control departments usage. Quotas helps to make sure individual departments (compartments) do not go over in budget.

@kbsantosh1 Appreciate using Steampipe!! 👍
That is an excellent suggestion; we see new go SDK support now available here
We have added a new issue in the OCI Plugin to work on the feasibility
Meanwhile, let us know how Steampipe is helping in your use case; this will help us.
We are looking forward to more collaboration on this.


⚠ Bofrost.lu has degraded performance

In 66f8627, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1481 ms

Resolved: Bofrost.lu performance has improved in 85d2a66 after 6 minutes.


Added functions to create commit and pr.

Some of my functions aren't completed, but I wanted to commit anyway since I haven't in a while.