New Term - "caste" for eusocial organisms

New term

Submitter: @wcornwell
Efficacy Justification (why is this term necessary?): Eusocial organisms not well captured by existing terms: lifestage and sex
Demand Justification (name at least two organizations that independently need this term): All museums with bee, ant, termite, or mole rat collections
Stability Justification (what concerns are there that this might affect existing implementations?):  Should not affect exiting implementations
Implications for dwciri: namespace (does this change affect a dwciri term version)?:

Proposed attributes of the new term:

Term name (in lowerCamelCase for properties, UpperCamelCase for classes): caste
Organized in Class (e.g., Occurrence, Event, Location, Taxon): occurrence
Definition of the term (normative): Categorisation of individuals for eusocial species (including some mammals and arthropods)
Usage comments (recommendations regarding content, etc., not normative): values could include worker, soldier, and reproductive
Examples (not normative):
Refines (identifier of the broader term this term refines; normative): this refines "sex" and "lifestage" for a particular set of organisms
Replaces (identifier of the existing term that would be deprecated and replaced by this term; normative):
ABCD 2.06 (XPATH of the equivalent term in ABCD or EFG; not normative):

Thanks @wcornwell for this submission and for using the new term template. It makes things super easy to assess. I would put the values you suggest in the Examples section. I have added the label "Process - need evidence for demand", because what is needed is not a general statement of who might be able to use it, but rather specific independent organizations that are willing to state that they have the need to share this information.

thanks for this.  maybe @bwprice could comment if this would be useful for the NHM?  Paul Eggelton or other social insect experts would be also good to check with but I can't find any on github.

@wcornwell - I will ask colleagues and update asap.

Hi @wcornwell,
Have you taken a look at the plant-pollinator vocabulary (
https://ppi.rebipp.org.br/)? It defines the term caste and it is supposed
to be used with dwc:measurementType.
Please, see:

Text Guide https://ppi.rebipp.org.br/text/
The paper describing how to share plant-pollinators interaction data, but
I'm sure you can adapt it to use only the caste term as you needed (
https://doi.org/10.1093/gigascience/giac043)

Let me know if I can help you in how to document the caste using this
approach.
thanks.
José Augusto Salim
Computer Engineer
Freelance Programmer
GitHub: https://github.com/zedomel
Freelancer Profile: https://www.freelancer.com/u/zedomel
On Tue, Jun 7, 2022 at 3:00 PM Ben Price @.***> wrote:

@wcornwell https://github.com/wcornwell - I will ask colleagues and
update asap.
—
Reply to this email directly, view it on GitHub
https://github.com/tdwg/dwc/issues/412#issuecomment-1148997316, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AB2UDVDIIRIMGLVE5UNXMW3VN6E3TANCNFSM5XXF62UA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hi @zedomel ,
Yes, I did have a glance at that when it popped up on google.  You have solved a very similar problem and solution here:

I think it's worth discussing with domain experts about whether the same vocabulary could work for all groups of eusocial organisms.  Termite castes are a bit more complex compared to bees: https://www.frontiersin.org/articles/10.3389/fphys.2014.00127/full
I'm curious what @bwprice colleagues suggest.

At the Danish GBIF node DanBIF, there is a need for a "caste" term in at least on sample based dataset on bees. E.g. see https://www.gbif.org/occurrence/1587094318 and the full dataset. I am investigating how caste is treated at the Natural History Museum of Denmark - in Specify. I will post this when known.

We endorse this addition from SiB Colombia, and we made an inquiry with some of our publishers to review this term, and Dimitri Forero from Instituto de Ciencias Naturales - Universidad Nacional de Colombia say this:

It is a good addition, however it can be more complex to establish controlled vocabularies from other groups.
At least for ants, I asked some colleagues that work with that group and they think of these examples for the vocabulary:

worker, mayor worker, minor worker, male alate, male dealate, queen alate, queen dealate, intercaste. Reference antWiki.

But it would be nice to ask experts in termites to see the possible vocabulary for that group.

So from SiB Colombia we think that maybe for this term we can put a wide variety of examples, to showcase that every group can use domain specific terms. It can be a sample from several groups, something like: Queen, male alate, intercaste, minor worker, soldier, ergatoid.
Also, in usage comments we can put that information explicitly, something like: Recommended best practice is to use a controlled vocabulary, those vocabularies can be domain specific for different eusocial insects.


Operator implementation (Xcode 8 beta issues)

Do you expect the current master (188fb11) to work with Xcode 8 beta?
Although Argo's master branch is mentioned to be compatible to Swift 3 there are some issues popping up in Xcode beta. E.g.:
Operator implementation without matching operator implementation (Decoded.swift)
public func >>- <T, U>(x: Decoded<T>, f: @noescape (T) -> Decoded<U>) -> Decoded<U> {}

public func -<< <T, U>(f: @noescape (T) -> Decoded<U>, x: Decoded<T>) -> Decoded<U> {

Operator is not a known binary (Decode.swift)
return flatReduce(keys, initial: json, combine: decodedJSON) >>- A.decode
```

Argo was added to my project via Cocoapods:
`pod 'Argo', :git => 'https://github.com/thoughtbot/Argo.git', :commit => '188fb11'`

@testzugang We did update Argo for Swift 3 and Xcode 8 beta. It appears to me that the problem you are seeing is because Runes was not installed properly as a dependency. This should happen automatically for you when using Carthage or Cocoapods. It is possible that the latest master commits aren't working with Cocoapods. I'll take a look and see if that is true.

@testzugang If you're going to manually specify the git location like that you also need to specify :submodules => true or else CocoaPods won't pull down the Runes source that it needs.
pod 'Argo', :git => 'https://github.com/thoughtbot/Argo.git', :commit => '188fb11', :submodules => true

I'm closing this as Swift 3.0 support (and a reworking of our Runes dependency) is currently under development.


Update clsid2.mpc-hc.installer.yaml

Update the installer URL for renewed x64 installer.
Checklist for Pull Requests

[ ] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

/azp run

@wingetbot run


[Mention The Feature]: add  faqs

Is your feature request related to a problem? Please describe.
add  faqs
Describe the solution you'd like.
add  faqs
Describe alternatives you've considered.
add  faqs
Additional context.
add  faqs
Show us the magic with screenshots
add  faqs
Checklist

[X] I have checked the Existing Issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

This issue was existing, please check it, i have kept it on hold.
So I am closing this issue.
Please understand.
And don't create multiple issues.


TensorFlow Custom loop gives different value of loss

I am using following versions:
tf version:  2.3.0
keras version:  2.4.0

my customized error is
def mse_fn(y_true, y_pred):
  error = y_true - y_pred
  mserror = tf.reduce_mean(tf.square(error))
  return mserror

data processing for my code is
(X_train, Y_train), (X_test, Y_test) = keras.datasets.mnist.load_data()
Y_train = np.array(Y_train).astype(np.float32)
Y_test = np.array(Y_test).astype(np.float32)
X_train = X_train/255.
X_test = X_test/255.

my customized DNN layer is
class MyDense(keras.layers.Layer):
  def __init__(self, units, activation=None, **kwargs):
    super().__init__(**kwargs)
    self.units = units
    self.activation = keras.activations.get(activation)

  def build(self, batch_input_shape):
    self.kernel = self.add_weight(name = "kernel", shape=[batch_input_shape[-1], self.units], initializer="glorot_normal")
    self.bias = self.add_weight(name = "bias", shape=[self.units], initializer = 'zeros')
    super().build(batch_input_shape)

  def call(self, X):
    return self.activation(X @ self.kernel + self.bias)

  def compute_output_shape(self, batch_input_shape):
    return tf.TensorShape(batch_input_shape.as_list()[:-1]+[self.units])

  def get_config(self):
    base_config = super().get_config()
    return {**base_config, "units":self.units, "activation": keras.activations.serialize(self.activation)}

the model is
class DNN_model(keras.Model):
  def __init__(self, output_dim, **kwargs):
    super().__init__(**kwargs)
    self.hidden1 = keras.layers.Flatten(input_shape = [28, 28])
    self.hidden2 = MyDense(32, activation='relu')
    self.hidden3 = MyDense(16, activation='relu')
    self.hidden4 = MyDense(8, activation='relu')
    self.hidden5 = MyDense(output_dim, activation='relu')

  def call(self, inputs):
    Z = self.hidden1(inputs)
    Z = self.hidden2(Z)
    Z = self.hidden3(Z)
    Z = self.hidden4(Z)
    Z = self.hidden5(Z)
    return Z

when I compile and fit using model.fit I get following loss
model_cust_loss = DNN_model(1)
model_cust_loss.compile(optimizer='adam', loss = mse_fn, metrics=['accuracy'])
model_cust_loss.fit(X_train, Y_train, epochs=20 , batch_size=32)

the output
1875/1875 [==============================] - 3s 1ms/step - loss: 2.5784 - accuracy: 0.1690
Epoch 2/20
1875/1875 [==============================] - 3s 1ms/step - loss: 1.0625 - accuracy: 0.1910
Epoch 3/20
1875/1875 [==============================] - 3s 1ms/step - loss: 0.8146 - accuracy: 0.1947
Epoch 4/20
1875/1875 [==============================] - 3s 1ms/step - loss: 0.7062 - accuracy: 0.1981
Epoch 5/20
1875/1875 [==============================] - 3s 1ms/step - loss: 0.6342 - accuracy: 0.1999
Epoch 6/20
1875/1875 [==============================] - 3s 1ms/step - loss: 0.5785 - accuracy: 0.2014
Epoch 7/20
1875/1875 [==============================] - 3s 1ms/step - loss: 0.5263 - accuracy: 0.2015
Epoch 8/20
1875/1875 [==============================] - 3s 1ms/step - loss: 0.4914 - accuracy: 0.2036
Epoch 9/20
1875/1875 [==============================] - 3s 1ms/step - loss: 0.4480 - accuracy: 0.2066
Epoch 10/20
...

and then I try customized loop
def random_batch(X, y, batch_size=32):
  idx = np.random.randint(len(X), size=batch_size)
  return X[idx], y[idx]

n_epochs = 5
batch_size = 32
n_steps = len(X_train)//batch_size
optimizer = keras.optimizers.Adam()
print("n_steps: ", n_steps)

epoch_losses = []
for epoch in range (1,n_epochs+1):
  print("Epoch {}/{}".format(epoch, n_epochs))
  batch_losses = []
  for step in range(1, n_steps+1):
    #print("step:",step)
    X_batch, Y_batch = random_batch(X_train, Y_train, batch_size = 32)
    with tf.GradientTape() as tape:
      Y_pred = model_cust_loss(X_batch, training=True)
      current_loss = mse_fn(Y_batch, Y_pred)
    batch_losses.append(current_loss)
    gradients = tape.gradient(current_loss, model_cust_loss.trainable_variables)
    optimizer.apply_gradients(zip(gradients,model_cust_loss.trainable_variables))
  epoch_losses.append(np.mean(batch_losses))
  print("loss per epoch:", np.mean(batch_losses))

The output gives a different value of loss than the model.fit method
Epoch 1/5
loss per epoch: 8.3357525
Epoch 2/5
loss per epoch: 8.387993
Epoch 3/5
loss per epoch: 8.356688
Epoch 4/5
loss per epoch: 8.362662
Epoch 5/5
loss per epoch: 8.374953

could you help?
Thanks, Debottam

Please, can you clean up a little bit your example so that we can quickly copy, paste, run your code.
Thanks

Hi @bhack , @amahendrakar
I have created an example in github you should be able to copy and run as it is https://github.com/Debottam/tensorFlowCustomized/blob/master/customizedTensorFlow.ipynb

Was able to reproduce the issue with TF v2.3 and TF-nightly. Please find the gist of it here. Thanks!

Hi @amahendrakar ,
Could you provide a solution to this issue?
Thanks,
Debottam.

Hi @jvishnuvardhan ,
Could you help me on this?
Thanks,
Debottam

Dear tensorflow developers,
I need help in this matter.
Thanks,
Debottam

@Debottam I've not seen your model and data in detail but it seems to me very similar to the working example at https://colab.research.google.com/github/tensorflow/docs/blob/master/site/en/tutorials/customization/custom_training_walkthrough.ipynb
Can you give a  run to that tutorial?

Hi @bhack
The loss of https://colab.research.google.com/github/keras-team/keras-io/blob/master/guides/ipynb/writing_a_training_loop_from_scratch.ipynb matches with the
model_cust_loss.fit(X_train, Y_train, epochs=20 , batch_size=32)

part of my code which is
1875/1875 [==============================] - 3s 1ms/step - loss: 2.5784 - accuracy: 0.1690
Epoch 2/20
1875/1875 [==============================] - 3s 1ms/step - loss: 1.0625 - accuracy: 0.1910
Epoch 3/20
1875/1875 [==============================] - 3s 1ms/step - loss: 0.8146 - accuracy: 0.1947
Epoch 4/20
1875/1875 [==============================] - 3s 1ms/step - loss: 0.7062 - accuracy: 0.1981
Epoch 5/20
1875/1875 [==============================] - 3s 1ms/step - loss: 0.6342 - accuracy: 0.1999

but the loss I get from my customized loop is way bigger. That is my question and would like to know why its happening?
Thanks,
Debottam.

It doesn't seems to me a bug. But if you want to have a specific support on your model/data generation I suggest you to post your question on our channel at:
https://stackoverflow.com/questions/tagged/tensorflow.
Tickets are  mainly for Bug reports and Feature requests.

@bhack ,
Did that too https://stackoverflow.com/questions/63941144/tensorflow-custom-loop-gives-different-value-of-loss didn't get any response.
Thanks,
Debottam.

@Debottam I quickly checked and looks like there was a shape mismatch between y_pred and y_true depending on whether y_pred is from model.fit or custom training. I added a reshape command as shown below and the error are similar from both the approaches.
Y_pred = tf.reshape(Y_pred,(1,batch_size))
Please take a look at the gist here. Thanks!
Ouput from the custom training
n_steps:  1875
Epoch 1/20
loss per epoch: 2.3010604
Epoch 2/20
loss per epoch: 1.0047752
Epoch 3/20
loss per epoch: 0.79963183
Epoch 4/20
loss per epoch: 0.68781537
Epoch 5/20
loss per epoch: 0.5867094
Epoch 6/20
loss per epoch: 0.527706
Epoch 7/20
loss per epoch: 0.4982657
Epoch 8/20
loss per epoch: 0.45960277
Epoch 9/20
loss per epoch: 0.43102258
Epoch 10/20
loss per epoch: 0.39782792
Epoch 11/20
loss per epoch: 0.3768253
Epoch 12/20
loss per epoch: 0.37661105
Epoch 13/20
loss per epoch: 0.34664243
Epoch 14/20
loss per epoch: 0.35457188
Epoch 15/20
loss per epoch: 0.3290785
Epoch 16/20
loss per epoch: 0.31267858
Epoch 17/20
loss per epoch: 0.30636093
Epoch 18/20
loss per epoch: 0.29752013
Epoch 19/20
loss per epoch: 0.27903932
Epoch 20/20
loss per epoch: 0.2706806

Hi @jvishnuvardhan ,
My apologies for the delayed reply. Thanks a lot for debugging it.
Thanks,
Debottam.


empty? is used against non-string arguments

NoMethodError: undefined method `empty?' for an instance of Integer (NoMethodError)

    cmd = cmd.reject { |a| a.nil? || a.empty? }.join(' ') if cmd.is_a?(Array)
                                      ^^^^^^^
/Users/yb/.rvm/gems/ruby-3.3.5/gems/qbash-0.2.0/lib/qbash.rb:60:in `block in qbash'
/Users/yb/.rvm/gems/ruby-3.3.5/gems/qbash-0.2.0/lib/qbash.rb:60:in `reject'
/Users/yb/.rvm/gems/ruby-3.3.5/gems/qbash-0.2.0/lib/qbash.rb:60:in `qbash'

@rultor release, tag is 0.2.1

@rultor release, tag is 0.2.1

@yegor256 OK, I will release it now. Please check the progress here.

@rultor release, tag is 0.2.1

@yegor256 Done! FYI, the full log is here (took me 2min).


gustatorially, brownly

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[b,g]

/trunk merge


UserPart Bindings for Dynamic Forms are missing

Hello,
In a completely new site created with Orchard 1.10 I cannot see UserPart Bindings from a Dynamic Form when it is used for inserting User content items.
I followed this post from IDeliverable http://www.ideliverable.com/blog/customizing-user-registration-and-login-with-dynamic-forms-and-workflows but I'm stucked at this part http://www.ideliverable.com/Media/Default/BlogPost/2014-11-24/firstname-bindings.png
because I don't see the UserPart bindings you can see in the image.
Dynamic Forms User Bindings Module is enabled,because in 1.10 it is a separate feature.
Root of the problem looks User ContentDefinition doesn't have UserPart as one of its parts. So BindingManager looks for bindings for parts within User type but that type doesn't have any part, so UserPart binding never is shown.
It is strange because I've looked previous versions and User type didn't have any part declared before. Furthermore BindingManager code haven't changed recently. So I don't get what can be causing the issue.

I answer to myself (if I would continue reading the post I would find the solution to my problem:

This is easily fixed by following these steps:

Go to Content Definition -> Content Parts and create a new part called UserPart. Make sure this part is Attachable. Although the Description field is optional, it is considered good practice to always provide a description to parts. I specified Turns your content type into a user." as its description.
Go to the User type edit screen and attach the UserPart.
Optional: go back to the UserPart edit screen and uncheck the "Attachable" checkbox. This step is not necessary, but since we won't be attaching this part to any other content type, I'd like to keep things tidy.


Merge kfm into rushd

The current KFM file layout is:
wells:
  - condition_name: A2-A5

Let's change it to use the rushd format, and also possibly let you pick metadata columns/combos of columns.

Allow multiple images per well, z stacks
Allow rushd to map images to wells that have been previously kfm'd using unmoved


The rigging data needed to apply flexes isn't exposed to GLua, so I'll need to write a model parser

Requires #81


Allowed ability for arguments to be passed via config.json

So far, this (should) allow better configuration for different markets (NA, EU, etc.) in the future through command line arguments.
Currently at the moment however, due to JSON imports for this to work you'd have to run npm run dev for it to run.
I didn't notice this branch until I planned to make a different pull request so I decided to just make one here because this would most likely get pushed to the master branch sometime soon.

Apologize for some of the bad explanations and grammar, I was typing it on half a brain cell at the time


Update learning.md

addressing yaml indentation issue.  correct should be something like this:
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
- role: control-plane
  extraMounts:
  - hostPath: /dev
    containerPath: /dev
  - hostPath: /var/run/docker.sock
    containerPath: /var/run/docker.sock```

Signed-off-by: Dan Papandrea<EMAIL_ADDRESS>
<!--  Thanks for sending a pull request!  Here are some tips for you:

1. If this is your first time, please read our contributor guidelines in the [CONTRIBUTING.md](https://github.com/falcosecurity/falco/blob/master/CONTRIBUTING.md) file in the Falco repository.
2. Please label this pull request according to what type of issue you are addressing.
3. Please add a release note!
4. If the PR is unfinished while opening it specify a wip in the title before the actual title, for example, "wip: my awesome feature"
-->

**What type of PR is this?**

> Uncomment one (or more) `/kind <>` lines:

> /kind bug

> /kind cleanup

> /kind design

> /kind user-interface

> /kind content

> /kind translation

**Any specific area of the project related to this PR?**

> Uncomment one (or more) `/area <>` lines:

> /area blog

> /area documentation

> /area videos

**What this PR does / why we need it**:

**Which issue(s) this PR fixes**:

<!--
Automatically closes linked issue when PR is merged.
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->

Fixes #

**Special notes for your reviewer**:

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

Needs approval from an approver in each of these files:

OWNERS

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

/kind bug
/area documentation

LGTM label has been added.  Git tree hash: fe4f62aaada3c755e3bd9aa1495aead473f7bfd6

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leogr]

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


MakeBootEntry: Windows Boot Manager not found.

What happens?
Installation fails with the reason "Windows Boot Manager not found." Now what's weird is that reading the HackBGRT log, I don't see any mention of my Windows installation on the main drive, C:. I don't see its GUID in there either. But if I run bcdedit in cmd, it does show my Windows installation. The only thing I can think of is if HackBGRT is trying to read from a different BCD than the one for my system...but I'm not sure why that would be
How this happens?
Explain exactly the steps you did:

HackBGRT didn't give me problems until today when  I messed up my bootloader and I had to reconfigure my boot files.
I just started with a fresh BCD and reconfigured from there

Log file
Before I put the log, I will put the output of bcdedit in a command prompt to compare it to:
C:\Windows\system32>bcdedit
Windows Boot Manager
identifier              {bootmgr}
device                  boot
description             Windows Boot Manager
locale                  es-ES
inherit                 {globalsettings}
isolatedcontext         Yes
default                 {current}
resumeobject            {1f8184a2-14de-11df-9734-f08c6d8c50b0}
displayorder            {8ecb1e79-e971-11ee-9338-2079188d02a6}
{8ecb1e78-e971-11ee-9338-2079188d02a6}
{8ecb1e76-e971-11ee-9338-2079188d02a6}
{8ecb1e77-e971-11ee-9338-2079188d02a6}
{current}
{c1c7020a-e972-11ee-9338-2079188d02a6}
{c1c7020c-e972-11ee-9338-2079188d02a6}
{c1c70208-e972-11ee-9338-2079188d02a6}
toolsdisplayorder       {memdiag}
timeout                 30
displaybootmenu         Yes
Firmware Application (101fffff)
identifier              {8ecb1e79-e971-11ee-9338-2079188d02a6}
description             Onboard NIC(IPV6)
isolatedcontext         Yes
Firmware Application (101fffff)
identifier              {8ecb1e78-e971-11ee-9338-2079188d02a6}
description             Onboard NIC(IPV4)
isolatedcontext         Yes
Windows Boot Loader
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.efi
description             Windows 7
locale                  ms-MY
isolatedcontext         Yes
osdevice                partition=C:
systemroot              \Windows
resumeobject            {453059b7-e973-11ee-9339-806e6f6e6963}
nx                      OptIn
bootmenupolicy          Legacy
Windows Boot Loader
identifier              {c1c7020a-e972-11ee-9338-2079188d02a6}
device                  ramdisk=[D:]\WIM\w11pe64.wim,{c1c70209-e972-11ee-9338-2079188d02a6}
path                    \Windows\System32\Boot\winload.efi
description             Anhdv 24 Windows 11 PE
locale                  en-US
isolatedcontext         Yes
osdevice                ramdisk=[D:]\WIM\w11pe64.wim,{c1c70209-e972-11ee-9338-2079188d02a6}
systemroot              \Windows
nx                      OptIn
detecthal               Yes
winpe                   Yes
Windows Boot Loader
identifier              {c1c7020c-e972-11ee-9338-2079188d02a6}
device                  ramdisk=[D:]\WIM\w10pe64_21.wim,{c1c7020b-e972-11ee-9338-2079188d02a6}
path                    \Windows\System32\Boot\winload.efi
description             Anhdv 21 Windows 10 PE
locale                  en-US
isolatedcontext         Yes
osdevice                ramdisk=[D:]\WIM\w10pe64_21.wim,{c1c7020b-e972-11ee-9338-2079188d02a6}
systemroot              \Windows
nx                      OptIn
detecthal               Yes
winpe                   Yes
Windows Boot Loader
identifier              {c1c70208-e972-11ee-9338-2079188d02a6}
device                  ramdisk=[E:]\Recovery\WindowsRE\winre.wim,{c1c70207-e972-11ee-9338-2079188d02a6}
path                    \Windows\System32\Boot\winload.efi
description             WinRE
locale                  es-MX
isolatedcontext         Yes
osdevice                ramdisk=[E:]\Recovery\WindowsRE\winre.wim,{c1c70207-e972-11ee-9338-2079188d02a6}
systemroot              \Windows
nx                      OptIn
detecthal               Yes
winpe                   Yes
The log:
2024-03-23 20:33:48.983 | pid 6512 | HackBGRT installer version: v2.4.0
2024-03-23 20:33:48.983 | pid 6512 | Args:
2024-03-23 20:33:48.999 | pid 6512 | Your OS uses arch=x64. This will be checked again during installation.
2024-03-23 20:33:48.999 | pid 6512 |
2024-03-23 20:33:48.999 | pid 6512 | Choose action (press a key):
2024-03-23 20:33:48.999 | pid 6512 |  I = install
2024-03-23 20:33:48.999 | pid 6512 |      - creates a new EFI boot entry for HackBGRT
2024-03-23 20:33:48.999 | pid 6512 |  J = install (alternative)
2024-03-23 20:33:48.999 | pid 6512 |      - creates a new EFI boot entry with an alternative method
2024-03-23 20:33:48.999 | pid 6512 |      - try this if the first option doesn't work
2024-03-23 20:33:48.999 | pid 6512 |  O = install (legacy)
2024-03-23 20:33:48.999 | pid 6512 |      - overwrites the MS boot loader; gets removed by Windows updates
2024-03-23 20:33:48.999 | pid 6512 |      - use as last resort; may brick your system if configured incorrectly
2024-03-23 20:33:48.999 | pid 6512 |  F = install files only
2024-03-23 20:33:48.999 | pid 6512 |      - ok for updating config, doesn't touch boot entries
2024-03-23 20:33:48.999 | pid 6512 |  D = disable
2024-03-23 20:33:48.999 | pid 6512 |      - removes created entries, restores MS boot loader
2024-03-23 20:33:48.999 | pid 6512 |  R = remove completely
2024-03-23 20:33:48.999 | pid 6512 |      - disables, then deletes all files and images
2024-03-23 20:33:48.999 | pid 6512 |  B = boot to UEFI setup
2024-03-23 20:33:48.999 | pid 6512 |      - lets you disable Secure Boot
2024-03-23 20:33:48.999 | pid 6512 |      - lets you move HackBGRT before Windows in boot order
2024-03-23 20:33:48.999 | pid 6512 |  L = show boot log (what HackBGRT did during boot)
2024-03-23 20:33:48.999 | pid 6512 |  C = cancel
2024-03-23 20:33:50.198 | pid 6512 | User input: J
2024-03-23 20:33:50.198 | pid 6512 |
2024-03-23 20:33:50.198 | pid 6512 | This setup program lets you edit just one image.
2024-03-23 20:33:50.198 | pid 6512 | Edit config.txt manually for advanced configuration.
2024-03-23 20:33:50.198 | pid 6512 | Draw or copy your preferred image to splash.bmp.
2024-03-23 20:33:50.198 | pid 6512 | StartProcess: mspaint splash.bmp
2024-03-23 20:33:51.539 | pid 6512 |
2024-03-23 20:33:51.550 | pid 6512 | RunPrivilegedActions: install disable enable-entry
2024-03-23 20:33:51.551 | pid 6512 | RunElevated: C:\Users\Alcatel\Desktop\HackBGRT-2.4.0\setup.exe is-elevated  install disable enable-entry
2024-03-23 20:33:53.505 | pid 1144 | HackBGRT installer version: v2.4.0
2024-03-23 20:33:53.505 | pid 1144 | Args: is-elevated install disable enable-entry
2024-03-23 20:33:53.505 | pid 1144 | Your OS uses arch=x64. This will be checked again during installation.
2024-03-23 20:33:53.520 | pid 1144 | RunPrivilegedActions: install disable enable-entry
2024-03-23 20:33:53.520 | pid 1144 | Esp.Find()
2024-03-23 20:33:53.520 | pid 1144 | Execute: mountvol
2024-03-23 20:33:53.708 | pid 1144 | Exit code: 0, output:
2024-03-23 20:33:53.708 | pid 1144 | Creates, deletes, or lists a volume mount point.
2024-03-23 20:33:53.708 | pid 1144 |
2024-03-23 20:33:53.708 | pid 1144 | MOUNTVOL [drive:]path VolumeName
2024-03-23 20:33:53.708 | pid 1144 | MOUNTVOL [drive:]path /D
2024-03-23 20:33:53.708 | pid 1144 | MOUNTVOL [drive:]path /L
2024-03-23 20:33:53.708 | pid 1144 | MOUNTVOL [drive:]path /P
2024-03-23 20:33:53.708 | pid 1144 | MOUNTVOL /R
2024-03-23 20:33:53.708 | pid 1144 | MOUNTVOL /N
2024-03-23 20:33:53.708 | pid 1144 | MOUNTVOL /E
2024-03-23 20:33:53.708 | pid 1144 | MOUNTVOL drive: /S
2024-03-23 20:33:53.708 | pid 1144 |
2024-03-23 20:33:53.708 | pid 1144 |     path        Specifies the existing NTFS directory where the mount
2024-03-23 20:33:53.708 | pid 1144 |                 point will reside.
2024-03-23 20:33:53.708 | pid 1144 |     VolumeName  Specifies the volume name that is the target of the mount
2024-03-23 20:33:53.708 | pid 1144 |                 point.
2024-03-23 20:33:53.708 | pid 1144 |     /D          Removes the volume mount point from the specified directory.
2024-03-23 20:33:53.708 | pid 1144 |     /L          Lists the mounted volume name for the specified directory.
2024-03-23 20:33:53.708 | pid 1144 |     /P          Removes the volume mount point from the specified directory,
2024-03-23 20:33:53.708 | pid 1144 |                 dismounts the volume, and makes the volume not mountable.
2024-03-23 20:33:53.708 | pid 1144 |                 You can make the volume mountable again by creating a volume
2024-03-23 20:33:53.708 | pid 1144 |                 mount point.
2024-03-23 20:33:53.708 | pid 1144 |     /R          Removes volume mount point directories and registry settings
2024-03-23 20:33:53.708 | pid 1144 |                 for volumes that are no longer in the system.
2024-03-23 20:33:53.708 | pid 1144 |     /N          Disables automatic mounting of new volumes.
2024-03-23 20:33:53.708 | pid 1144 |     /E          Re-enables automatic mounting of new volumes.
2024-03-23 20:33:53.708 | pid 1144 |     /S          Mount the EFI System Partition on the given drive.
2024-03-23 20:33:53.708 | pid 1144 |
2024-03-23 20:33:53.708 | pid 1144 | Possible values for VolumeName along with current mount points are:
2024-03-23 20:33:53.708 | pid 1144 |
2024-03-23 20:33:53.708 | pid 1144 |     \?\Volume{adcb3ea4-9ce8-4e9b-80f1-bc0bcb6cc116}
2024-03-23 20:33:53.708 | pid 1144 |         C:
2024-03-23 20:33:53.708 | pid 1144 |
2024-03-23 20:33:53.708 | pid 1144 |     \?\Volume{62a844e6-96e1-4079-aebe-f565465dc2d8}
2024-03-23 20:33:53.708 | pid 1144 |         D:
2024-03-23 20:33:53.708 | pid 1144 |
2024-03-23 20:33:53.708 | pid 1144 |     \?\Volume{3795b565-3504-48d4-b468-484e15e5def7}
2024-03-23 20:33:53.708 | pid 1144 |         E:
2024-03-23 20:33:53.708 | pid 1144 |
2024-03-23 20:33:53.708 | pid 1144 |     \?\Volume{ab1f7ab5-c3ca-4d1a-a1fd-a1720bf27d0c}
2024-03-23 20:33:53.708 | pid 1144 |         *** NO MOUNT POINTS ***
2024-03-23 20:33:53.708 | pid 1144 |
2024-03-23 20:33:53.708 | pid 1144 |     The EFI System Partition is mounted at A:
2024-03-23 20:33:53.708 | pid 1144 |
2024-03-23 20:33:53.708 | pid 1144 |
2024-03-23 20:33:53.708 | pid 1144 |
2024-03-23 20:33:53.708 | pid 1144 |
2024-03-23 20:33:53.708 | pid 1144 | Esp.TryPath: A:\ has MS boot loader
2024-03-23 20:33:53.708 | pid 1144 | EFI System Partition location is A:
2024-03-23 20:33:53.708 | pid 1144 | Detected arch=x64 from MS boot loader, the installer will use that.
2024-03-23 20:33:53.708 | pid 1144 |
2024-03-23 20:33:53.708 | pid 1144 | --- BOOT LOG START ---
2024-03-23 20:33:53.708 | pid 1144 | (null)
2024-03-23 20:33:53.708 | pid 1144 | --- BOOT LOG END ---
2024-03-23 20:33:53.708 | pid 1144 | LogBGRT: 56 bytes: 42 47 52 54 38 00 00 00 00 CD 00 00 00 00 00 00 00 00 00 00 00 00 00 00 09 20 07 01 41 4D 49 20 13 00 01 00 01 00 00 00 18 B0 C9 4F 00 00 00 00 E9 02 00 00 C4 00 00 00
2024-03-23 20:33:53.708 | pid 1144 | LogBootOrder: BootOrder Guid={8be4df61-93ca-11d2-aa0d-00e098032b8c} Attributes=7 Text='        ' Bytes='17 00 16 00 18 00 19 00'
2024-03-23 20:33:53.708 | pid 1144 | LogBootOrder: BootCurrent Guid={8be4df61-93ca-11d2-aa0d-00e098032b8c} Attributes=6 Text='  ' Bytes='19 00'
2024-03-23 20:33:53.723 | pid 1144 | LogBootOrder: Boot0017 Guid={8be4df61-93ca-11d2-aa0d-00e098032b8c} Attributes=7 Text='      O n b o a r d   N I C ( I P V 6 )        A              %   P                                <                                        @                     v  Gd- ; A  MQ  L P X E   I P 6   I n t e l ( R )   E t h e r n e t   C o n n e c t i o n   ( 7 )   I 2 1 9 - L M        BO' Bytes='00 00 00 00 F1 00 4F 00 6E 00 62 00 6F 00 61 00 72 00 64 00 20 00 4E 00 49 00 43 00 28 00 49 00 50 00 56 00 36 00 29 00 00 00 02 01 0C 00 D0 41 03 0A 00 00 00 00 01 01 06 00 06 1F 03 0B 25 00 C8 F7 50 0C A4 FC 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 03 0D 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 7F FF 04 00 01 04 76 00 EF 47 64 2D C9 3B A0 41 AC 19 4D 51 D0 1B 4C E6 50 00 58 00 45 00 20 00 49 00 50 00 36 00 20 00 49 00 6E 00 74 00 65 00 6C 00 28 00 52 00 29 00 20 00 45 00 74 00 68 00 65 00 72 00 6E 00 65 00 74 00 20 00 43 00 6F 00 6E 00 6E 00 65 00 63 00 74 00 69 00 6F 00 6E 00 20 00 28 00 37 00 29 00 20 00 49 00 32 00 31 00 39 00 2D 00 4C 00 4D 00 00 00 7F FF 04 00 00 00 42 4F'
2024-03-23 20:33:53.723 | pid 1144 | LogBootOrder: Boot0016 Guid={8be4df61-93ca-11d2-aa0d-00e098032b8c} Attributes=7 Text='      O n b o a r d   N I C ( I P V 4 )        A              %   P                                                              v  Gd- ; A  MQ  L P X E   I P 4   I n t e l ( R )   E t h e r n e t   C o n n e c t i o n   ( 7 )   I 2 1 9 - L M        BO' Bytes='00 00 00 00 D0 00 4F 00 6E 00 62 00 6F 00 61 00 72 00 64 00 20 00 4E 00 49 00 43 00 28 00 49 00 50 00 56 00 34 00 29 00 00 00 02 01 0C 00 D0 41 03 0A 00 00 00 00 01 01 06 00 06 1F 03 0B 25 00 C8 F7 50 0C A4 FC 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 03 0C 1B 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 7F FF 04 00 01 04 76 00 EF 47 64 2D C9 3B A0 41 AC 19 4D 51 D0 1B 4C E6 50 00 58 00 45 00 20 00 49 00 50 00 34 00 20 00 49 00 6E 00 74 00 65 00 6C 00 28 00 52 00 29 00 20 00 45 00 74 00 68 00 65 00 72 00 6E 00 65 00 74 00 20 00 43 00 6F 00 6E 00 6E 00 65 00 63 00 74 00 69 00 6F 00 6E 00 20 00 28 00 37 00 29 00 20 00 49 00 32 00 31 00 39 00 2D 00 4C 00 4D 00 00 00 7F FF 04 00 00 00 42 4F'
2024-03-23 20:33:53.723 | pid 1144 | LogBootOrder: Boot0018 Guid={8be4df61-93ca-11d2-aa0d-00e098032b8c} Attributes=7 Text='      U E F I :   P C 4 0 1   N V M e   S K   h y n i x   1 T B ,   P a r t i t i o n   4     *        v             D b  y@   eF]      0 \ E F I \ b o o t \ b o o t x 6 4 . e f i        8  Gd- ; A  MQ  L M N 8 B N 1 6 2 9 1 0 3 0 B L 2 R        BO' Bytes='00 00 00 00 9A 00 55 00 45 00 46 00 49 00 3A 00 20 00 50 00 43 00 34 00 30 00 31 00 20 00 4E 00 56 00 4D 00 65 00 20 00 53 00 4B 00 20 00 68 00 79 00 6E 00 69 00 78 00 20 00 31 00 54 00 42 00 2C 00 20 00 50 00 61 00 72 00 74 00 69 00 74 00 69 00 6F 00 6E 00 20 00 34 00 00 00 04 01 2A 00 04 00 00 00 00 B0 99 76 00 00 00 00 00 00 80 00 00 00 00 00 E6 44 A8 62 E1 96 79 40 AE BE F5 65 46 5D C2 D8 02 02 04 04 30 00 5C 00 45 00 46 00 49 00 5C 00 62 00 6F 00 6F 00 74 00 5C 00 62 00 6F 00 6F 00 74 00 78 00 36 00 34 00 2E 00 65 00 66 00 69 00 00 00 7F FF 04 00 01 04 38 00 EF 47 64 2D C9 3B A0 41 AC 19 4D 51 D0 1B 4C E6 4D 00 4E 00 38 00 42 00 4E 00 31 00 36 00 32 00 39 00 31 00 30 00 33 00 30 00 42 00 4C 00 32 00 52 00 00 00 7F FF 04 00 00 00 42 4F'
2024-03-23 20:33:53.723 | pid 1144 | LogBootOrder: Boot0019 Guid={8be4df61-93ca-11d2-aa0d-00e098032b8c} Attributes=7 Text='      U E F I :   P C 4 0 1   N V M e   S K   h y n i x   1 T B ,   P a r t i t i o n   6     *     d *w     E       z     M   r  }     F \ E F I \ M i c r o s o f t \ B o o t \ b o o t m g f w . e f i        8  Gd- ; A  MQ  L M N 8 B N 1 6 2 9 1 0 3 0 B L 2 R        BO' Bytes='01 00 00 00 B0 00 55 00 45 00 46 00 49 00 3A 00 20 00 50 00 43 00 34 00 30 00 31 00 20 00 4E 00 56 00 4D 00 65 00 20 00 53 00 4B 00 20 00 68 00 79 00 6E 00 69 00 78 00 20 00 31 00 54 00 42 00 2C 00 20 00 50 00 61 00 72 00 74 00 69 00 74 00 69 00 6F 00 6E 00 20 00 36 00 00 00 04 01 2A 00 06 00 00 00 64 FA 2A 77 00 00 00 00 9C 45 03 00 00 00 00 00 B5 7A 1F AB CA C3 1A 4D A1 FD A1 72 0B F2 7D 0C 02 02 04 04 46 00 5C 00 45 00 46 00 49 00 5C 00 4D 00 69 00 63 00 72 00 6F 00 73 00 6F 00 66 00 74 00 5C 00 42 00 6F 00 6F 00 74 00 5C 00 62 00 6F 00 6F 00 74 00 6D 00 67 00 66 00 77 00 2E 00 65 00 66 00 69 00 00 00 7F FF 04 00 01 04 38 00 EF 47 64 2D C9 3B A0 41 AC 19 4D 51 D0 1B 4C E6 4D 00 4E 00 38 00 42 00 4E 00 31 00 36 00 32 00 39 00 31 00 30 00 33 00 30 00 42 00 4C 00 32 00 52 00 00 00 7F FF 04 00 00 00 42 4F'
2024-03-23 20:33:53.880 | pid 1144 | Boot time = 23/03/2024 20:31:42, config.txt changed = 23/03/2024 19:45:38
2024-03-23 20:33:53.880 | pid 1144 | You may have to disable Fast Startup (Hiberboot) to reboot properly.
2024-03-23 20:33:53.880 | pid 1144 | Running action 'install'.
2024-03-23 20:33:53.918 | pid 1144 | Installed config.txt to A:\EFI\HackBGRT\config.txt.
2024-03-23 20:33:53.918 | pid 1144 | config.txt:
2024-03-23 20:33:53.918 | pid 1144 | # vim: set fileencoding=utf-8
2024-03-23 20:33:53.918 | pid 1144 | # The same options may be given also as command line parameters in the EFI Shell, which is useful for debugging.
2024-03-23 20:33:53.918 | pid 1144 |
2024-03-23 20:33:53.918 | pid 1144 | # Boot loader path. MS = either backup or original Windows boot loader.
2024-03-23 20:33:53.918 | pid 1144 | boot=MS
2024-03-23 20:33:53.918 | pid 1144 |
2024-03-23 20:33:53.918 | pid 1144 | # The image is specified with an image line.
2024-03-23 20:33:53.918 | pid 1144 | # Multiple image lines may be present, in which case one will be picked by random.
2024-03-23 20:33:53.918 | pid 1144 | # The image line may contain the following parts:
2024-03-23 20:33:53.918 | pid 1144 | # Any of the following:
2024-03-23 20:33:53.918 | pid 1144 | #  - "n=(number)", a weight for this image in the randomization process. Default: n=1.
2024-03-23 20:33:53.918 | pid 1144 | #  - "x=(number)" or "x=keep", the x offset from the center. Default: x=0.
2024-03-23 20:33:53.918 | pid 1144 | #  - "y=(number)" or "y=keep", the y offset from the center. Default: y=0.
2024-03-23 20:33:53.918 | pid 1144 | #  - "o=(0|90|180|270|keep)", the screen orientation, degrees anticlockwise. Default: o=keep.
2024-03-23 20:33:53.918 | pid 1144 | # One of the following:
2024-03-23 20:33:53.918 | pid 1144 | #  - "keep" to keep the firmware logo. Also keeps coordinates by default.
2024-03-23 20:33:53.918 | pid 1144 | #  - "remove" to remove the BGRT. Makes x and y meaningless.
2024-03-23 20:33:53.918 | pid 1144 | #  - "black" to use only a black image. Makes x and y meaningless.
2024-03-23 20:33:53.918 | pid 1144 | #  - "path=file.bmp" to read an image file.
2024-03-23 20:33:53.918 | pid 1144 | #    * NOTE: The installer can copy and convert BMP, PNG, JPEG, GIF.
2024-03-23 20:33:53.918 | pid 1144 | # Examples:
2024-03-23 20:33:53.918 | pid 1144 | #  - image=remove
2024-03-23 20:33:53.918 | pid 1144 | #  - image=black
2024-03-23 20:33:53.918 | pid 1144 | #  - image= x=0 y=-200 path=topimage.bmp
2024-03-23 20:33:53.918 | pid 1144 | #  - image= n=1 o=90 path=sideways.bmp
2024-03-23 20:33:53.918 | pid 1144 | #  - image= n=50 y=999999 o=keep path=probable.bmp
2024-03-23 20:33:53.918 | pid 1144 | # The above examples together would produce
2024-03-23 20:33:53.918 | pid 1144 | #  - 1/54 chance for the default OS logo
2024-03-23 20:33:53.918 | pid 1144 | #  - 1/54 chance for black screen
2024-03-23 20:33:53.918 | pid 1144 | #  - 1/54 chance for topimage.bmp, 200 px above the center of the screen
2024-03-23 20:33:53.918 | pid 1144 | #  - 1/54 chance for splash.bmp, centered, orientation set to 90 degrees
2024-03-23 20:33:53.918 | pid 1144 | #  - 50/54 chance for probable.bmp, at the bottom edge, explicitly default orientation
2024-03-23 20:33:53.918 | pid 1144 | # Default: just one image.
2024-03-23 20:33:53.918 | pid 1144 | image= y=-200 path=splash.bmp
2024-03-23 20:33:53.918 | pid 1144 |
2024-03-23 20:33:53.918 | pid 1144 | # Preferred resolution. Use 0x0 for maximum and -1x-1 for original.
2024-03-23 20:33:53.918 | pid 1144 | resolution=0x0
2024-03-23 20:33:53.918 | pid 1144 |
2024-03-23 20:33:53.918 | pid 1144 | # Logging (0 for disabled, 1 for enabled).
2024-03-23 20:33:53.918 | pid 1144 | # When logging is enabled, setup.exe can show debug information about the current boot.
2024-03-23 20:33:53.918 | pid 1144 | # The log might occupy a few kilobytes of RAM.
2024-03-23 20:33:53.918 | pid 1144 | log=1
2024-03-23 20:33:53.918 | pid 1144 |
2024-03-23 20:33:53.918 | pid 1144 | # Debug mode (0 for disabled, 1 for enabled).
2024-03-23 20:33:53.918 | pid 1144 | # Shows debug information and prompts for keypress before booting.
2024-03-23 20:33:53.918 | pid 1144 | debug=0
2024-03-23 20:33:53.933 | pid 1144 | InstallImageFile: splash.bmp
2024-03-23 20:33:53.949 | pid 1144 | Installed image splash.bmp to A:\EFI\HackBGRT\splash.bmp.
2024-03-23 20:33:53.949 | pid 1144 | Installed shim-signed\shimx64.efi to A:\EFI\HackBGRT\loader.efi.
2024-03-23 20:33:53.949 | pid 1144 | Installed shim-signed\mmx64.efi to A:\EFI\HackBGRT\mmx64.efi.
2024-03-23 20:33:53.949 | pid 1144 | Installed efi-signed\bootx64.efi to A:\EFI\HackBGRT\grubx64.efi.
2024-03-23 20:33:53.949 | pid 1144 | Installed efi-signed\bootx64.efi to A:\EFI\HackBGRT\䥗䑎坏SX.
2024-03-23 20:33:53.965 | pid 1144 | Installed certificate.cer to A:\EFI\HackBGRT\certificate.cer.
2024-03-23 20:33:53.965 | pid 1144 | HackBGRT has been copied to A:\EFI\HackBGRT.
2024-03-23 20:33:53.965 | pid 1144 | On first boot, select 'Enroll hash from disk' and enroll EFI\HackBGRT\grubx64.efi.
2024-03-23 20:33:53.965 | pid 1144 | Alternatively, select 'Enroll key from disk' and enroll EFI\HackBGRT\certificate.cer.
2024-03-23 20:33:53.965 | pid 1144 | Completed action 'install' successfully.
2024-03-23 20:33:53.965 | pid 1144 | Running action 'disable'.
2024-03-23 20:33:54.183 | pid 1144 | DetectLoader failed: A:\EFI\HackBGRT\bootmgfw-original.efi not found
2024-03-23 20:33:54.183 | pid 1144 | Execute: bcdedit /enum firmware
2024-03-23 20:33:54.554 | pid 1144 | Exit code: 0, output:
2024-03-23 20:33:54.554 | pid 1144 |
2024-03-23 20:33:54.554 | pid 1144 | Firmware Boot Manager
2024-03-23 20:33:54.554 | pid 1144 | ---------------------
2024-03-23 20:33:54.554 | pid 1144 | identifier              {fwbootmgr}
2024-03-23 20:33:54.554 | pid 1144 | displayorder            {8ecb1e79-e971-11ee-9338-2079188d02a6}
2024-03-23 20:33:54.554 | pid 1144 |                         {8ecb1e78-e971-11ee-9338-2079188d02a6}
2024-03-23 20:33:54.554 | pid 1144 |                         {fa6e64f8-e918-11ee-a402-806e6f6e6963}
2024-03-23 20:33:54.554 | pid 1144 |                         {fa6e64f9-e918-11ee-a402-806e6f6e6963}
2024-03-23 20:33:54.554 | pid 1144 | timeout                 0
2024-03-23 20:33:54.554 | pid 1144 |
2024-03-23 20:33:54.554 | pid 1144 | Windows Boot Manager
2024-03-23 20:33:54.554 | pid 1144 | --------------------
2024-03-23 20:33:54.554 | pid 1144 | identifier              {bootmgr}
2024-03-23 20:33:54.554 | pid 1144 | device                  boot
2024-03-23 20:33:54.554 | pid 1144 | description             Windows Boot Manager
2024-03-23 20:33:54.554 | pid 1144 | locale                  es-ES
2024-03-23 20:33:54.554 | pid 1144 | inherit                 {globalsettings}
2024-03-23 20:33:54.554 | pid 1144 | isolatedcontext         Yes
2024-03-23 20:33:54.554 | pid 1144 | default                 {current}
2024-03-23 20:33:54.554 | pid 1144 | resumeobject            {1f8184a2-14de-11df-9734-f08c6d8c50b0}
2024-03-23 20:33:54.554 | pid 1144 | displayorder            {8ecb1e79-e971-11ee-9338-2079188d02a6}
2024-03-23 20:33:54.554 | pid 1144 |                         {8ecb1e78-e971-11ee-9338-2079188d02a6}
2024-03-23 20:33:54.554 | pid 1144 |                         {8ecb1e76-e971-11ee-9338-2079188d02a6}
2024-03-23 20:33:54.554 | pid 1144 |                         {8ecb1e77-e971-11ee-9338-2079188d02a6}
2024-03-23 20:33:54.554 | pid 1144 |                         {current}
2024-03-23 20:33:54.554 | pid 1144 |                         {c1c7020a-e972-11ee-9338-2079188d02a6}
2024-03-23 20:33:54.554 | pid 1144 |                         {c1c7020c-e972-11ee-9338-2079188d02a6}
2024-03-23 20:33:54.554 | pid 1144 |                         {c1c70208-e972-11ee-9338-2079188d02a6}
2024-03-23 20:33:54.554 | pid 1144 | toolsdisplayorder       {memdiag}
2024-03-23 20:33:54.554 | pid 1144 | timeout                 30
2024-03-23 20:33:54.554 | pid 1144 | displaybootmenu         Yes
2024-03-23 20:33:54.554 | pid 1144 |
2024-03-23 20:33:54.554 | pid 1144 | Firmware Application (101fffff)
2024-03-23 20:33:54.554 | pid 1144 | -------------------------------
2024-03-23 20:33:54.554 | pid 1144 | identifier              {8ecb1e78-e971-11ee-9338-2079188d02a6}
2024-03-23 20:33:54.554 | pid 1144 | description             Onboard NIC(IPV4)
2024-03-23 20:33:54.554 | pid 1144 | isolatedcontext         Yes
2024-03-23 20:33:54.554 | pid 1144 |
2024-03-23 20:33:54.554 | pid 1144 | Firmware Application (101fffff)
2024-03-23 20:33:54.554 | pid 1144 | -------------------------------
2024-03-23 20:33:54.554 | pid 1144 | identifier              {8ecb1e79-e971-11ee-9338-2079188d02a6}
2024-03-23 20:33:54.554 | pid 1144 | description             Onboard NIC(IPV6)
2024-03-23 20:33:54.554 | pid 1144 | isolatedcontext         Yes
2024-03-23 20:33:54.554 | pid 1144 |
2024-03-23 20:33:54.554 | pid 1144 | Firmware Application (101fffff)
2024-03-23 20:33:54.554 | pid 1144 | -------------------------------
2024-03-23 20:33:54.554 | pid 1144 | identifier              {fa6e64f8-e918-11ee-a402-806e6f6e6963}
2024-03-23 20:33:54.554 | pid 1144 | device                  partition=D:
2024-03-23 20:33:54.554 | pid 1144 | path                    \EFI\boot\bootx64.efi
2024-03-23 20:33:54.554 | pid 1144 | description             UEFI: PC401 NVMe SK hynix 1TB, Partition 4
2024-03-23 20:33:54.554 | pid 1144 | isolatedcontext         Yes
2024-03-23 20:33:54.554 | pid 1144 |
2024-03-23 20:33:54.554 | pid 1144 | Firmware Application (101fffff)
2024-03-23 20:33:54.554 | pid 1144 | -------------------------------
2024-03-23 20:33:54.554 | pid 1144 | identifier              {fa6e64f9-e918-11ee-a402-806e6f6e6963}
2024-03-23 20:33:54.554 | pid 1144 | device                  partition=A:
2024-03-23 20:33:54.554 | pid 1144 | path                    \EFI\Microsoft\Boot\bootmgfw.efi
2024-03-23 20:33:54.554 | pid 1144 | description             UEFI: PC401 NVMe SK hynix 1TB, Partition 6
2024-03-23 20:33:54.554 | pid 1144 | isolatedcontext         Yes
2024-03-23 20:33:54.554 | pid 1144 |
2024-03-23 20:33:54.554 | pid 1144 |
2024-03-23 20:33:54.554 | pid 1144 |
2024-03-23 20:33:54.554 | pid 1144 | Execute: bcdedit /enum {8ecb1e79-e971-11ee-9338-2079188d02a6}
2024-03-23 20:33:54.815 | pid 1144 | Exit code: 0, output:
2024-03-23 20:33:54.815 | pid 1144 |
2024-03-23 20:33:54.815 | pid 1144 | Firmware Application (101fffff)
2024-03-23 20:33:54.815 | pid 1144 | -------------------------------
2024-03-23 20:33:54.815 | pid 1144 | identifier              {8ecb1e79-e971-11ee-9338-2079188d02a6}
2024-03-23 20:33:54.815 | pid 1144 | description             Onboard NIC(IPV6)
2024-03-23 20:33:54.815 | pid 1144 | isolatedcontext         Yes
2024-03-23 20:33:54.815 | pid 1144 |
2024-03-23 20:33:54.815 | pid 1144 |
2024-03-23 20:33:54.815 | pid 1144 |
2024-03-23 20:33:54.815 | pid 1144 | Execute: bcdedit /enum {8ecb1e78-e971-11ee-9338-2079188d02a6}
2024-03-23 20:33:55.081 | pid 1144 | Exit code: 0, output:
2024-03-23 20:33:55.081 | pid 1144 |
2024-03-23 20:33:55.081 | pid 1144 | Firmware Application (101fffff)
2024-03-23 20:33:55.081 | pid 1144 | -------------------------------
2024-03-23 20:33:55.081 | pid 1144 | identifier              {8ecb1e78-e971-11ee-9338-2079188d02a6}
2024-03-23 20:33:55.081 | pid 1144 | description             Onboard NIC(IPV4)
2024-03-23 20:33:55.081 | pid 1144 | isolatedcontext         Yes
2024-03-23 20:33:55.081 | pid 1144 |
2024-03-23 20:33:55.081 | pid 1144 |
2024-03-23 20:33:55.081 | pid 1144 |
2024-03-23 20:33:55.081 | pid 1144 | Execute: bcdedit /enum {fa6e64f8-e918-11ee-a402-806e6f6e6963}
2024-03-23 20:33:55.346 | pid 1144 | Exit code: 0, output:
2024-03-23 20:33:55.346 | pid 1144 |
2024-03-23 20:33:55.346 | pid 1144 | Firmware Application (101fffff)
2024-03-23 20:33:55.346 | pid 1144 | -------------------------------
2024-03-23 20:33:55.346 | pid 1144 | identifier              {fa6e64f8-e918-11ee-a402-806e6f6e6963}
2024-03-23 20:33:55.346 | pid 1144 | device                  partition=D:
2024-03-23 20:33:55.346 | pid 1144 | path                    \EFI\boot\bootx64.efi
2024-03-23 20:33:55.346 | pid 1144 | description             UEFI: PC401 NVMe SK hynix 1TB, Partition 4
2024-03-23 20:33:55.346 | pid 1144 | isolatedcontext         Yes
2024-03-23 20:33:55.346 | pid 1144 |
2024-03-23 20:33:55.346 | pid 1144 |
2024-03-23 20:33:55.346 | pid 1144 |
2024-03-23 20:33:55.346 | pid 1144 | Execute: bcdedit /enum {fa6e64f9-e918-11ee-a402-806e6f6e6963}
2024-03-23 20:33:55.618 | pid 1144 | Exit code: 0, output:
2024-03-23 20:33:55.618 | pid 1144 |
2024-03-23 20:33:55.618 | pid 1144 | Firmware Application (101fffff)
2024-03-23 20:33:55.618 | pid 1144 | -------------------------------
2024-03-23 20:33:55.618 | pid 1144 | identifier              {fa6e64f9-e918-11ee-a402-806e6f6e6963}
2024-03-23 20:33:55.618 | pid 1144 | device                  partition=A:
2024-03-23 20:33:55.618 | pid 1144 | path                    \EFI\Microsoft\Boot\bootmgfw.efi
2024-03-23 20:33:55.618 | pid 1144 | description             UEFI: PC401 NVMe SK hynix 1TB, Partition 6
2024-03-23 20:33:55.618 | pid 1144 | isolatedcontext         Yes
2024-03-23 20:33:55.618 | pid 1144 |
2024-03-23 20:33:55.618 | pid 1144 |
2024-03-23 20:33:55.618 | pid 1144 |
2024-03-23 20:33:55.618 | pid 1144 | Execute: bcdedit /enum {1f8184a2-14de-11df-9734-f08c6d8c50b0}
2024-03-23 20:33:55.884 | pid 1144 | Exit code: 0, output:
2024-03-23 20:33:55.884 | pid 1144 | There are no matching objects or the store is empty.
2024-03-23 20:33:55.884 | pid 1144 |
2024-03-23 20:33:55.884 | pid 1144 |
2024-03-23 20:33:55.884 | pid 1144 |
2024-03-23 20:33:55.884 | pid 1144 | Execute: bcdedit /enum {8ecb1e76-e971-11ee-9338-2079188d02a6}
2024-03-23 20:33:56.150 | pid 1144 | Exit code: 0, output:
2024-03-23 20:33:56.150 | pid 1144 | There are no matching objects or the store is empty.
2024-03-23 20:33:56.150 | pid 1144 |
2024-03-23 20:33:56.150 | pid 1144 |
2024-03-23 20:33:56.150 | pid 1144 |
2024-03-23 20:33:56.150 | pid 1144 | Execute: bcdedit /enum {8ecb1e77-e971-11ee-9338-2079188d02a6}
2024-03-23 20:33:56.416 | pid 1144 | Exit code: 0, output:
2024-03-23 20:33:56.416 | pid 1144 | There are no matching objects or the store is empty.
2024-03-23 20:33:56.416 | pid 1144 |
2024-03-23 20:33:56.416 | pid 1144 |
2024-03-23 20:33:56.416 | pid 1144 |
2024-03-23 20:33:56.416 | pid 1144 | Execute: bcdedit /enum {c1c7020a-e972-11ee-9338-2079188d02a6}
2024-03-23 20:33:56.697 | pid 1144 | Exit code: 0, output:
2024-03-23 20:33:56.697 | pid 1144 |
2024-03-23 20:33:56.697 | pid 1144 | Windows Boot Loader
2024-03-23 20:33:56.697 | pid 1144 | -------------------
2024-03-23 20:33:56.697 | pid 1144 | identifier              {c1c7020a-e972-11ee-9338-2079188d02a6}
2024-03-23 20:33:56.697 | pid 1144 | device                  ramdisk=[D:]\WIM\w11pe64.wim,{c1c70209-e972-11ee-9338-2079188d02a6}
2024-03-23 20:33:56.697 | pid 1144 | path                    \Windows\System32\Boot\winload.efi
2024-03-23 20:33:56.697 | pid 1144 | description             Anhdv 24 Windows 11 PE
2024-03-23 20:33:56.697 | pid 1144 | locale                  en-US
2024-03-23 20:33:56.697 | pid 1144 | isolatedcontext         Yes
2024-03-23 20:33:56.697 | pid 1144 | osdevice                ramdisk=[D:]\WIM\w11pe64.wim,{c1c70209-e972-11ee-9338-2079188d02a6}
2024-03-23 20:33:56.697 | pid 1144 | systemroot              \Windows
2024-03-23 20:33:56.697 | pid 1144 | nx                      OptIn
2024-03-23 20:33:56.697 | pid 1144 | detecthal               Yes
2024-03-23 20:33:56.697 | pid 1144 | winpe                   Yes
2024-03-23 20:33:56.697 | pid 1144 |
2024-03-23 20:33:56.697 | pid 1144 |
2024-03-23 20:33:56.697 | pid 1144 |
2024-03-23 20:33:56.697 | pid 1144 | Execute: bcdedit /enum {c1c7020c-e972-11ee-9338-2079188d02a6}
2024-03-23 20:33:56.962 | pid 1144 | Exit code: 0, output:
2024-03-23 20:33:56.962 | pid 1144 |
2024-03-23 20:33:56.962 | pid 1144 | Windows Boot Loader
2024-03-23 20:33:56.962 | pid 1144 | -------------------
2024-03-23 20:33:56.962 | pid 1144 | identifier              {c1c7020c-e972-11ee-9338-2079188d02a6}
2024-03-23 20:33:56.962 | pid 1144 | device                  ramdisk=[D:]\WIM\w10pe64_21.wim,{c1c7020b-e972-11ee-9338-2079188d02a6}
2024-03-23 20:33:56.962 | pid 1144 | path                    \Windows\System32\Boot\winload.efi
2024-03-23 20:33:56.962 | pid 1144 | description             Anhdv 21 Windows 10 PE
2024-03-23 20:33:56.962 | pid 1144 | locale                  en-US
2024-03-23 20:33:56.962 | pid 1144 | isolatedcontext         Yes
2024-03-23 20:33:56.962 | pid 1144 | osdevice                ramdisk=[D:]\WIM\w10pe64_21.wim,{c1c7020b-e972-11ee-9338-2079188d02a6}
2024-03-23 20:33:56.962 | pid 1144 | systemroot              \Windows
2024-03-23 20:33:56.962 | pid 1144 | nx                      OptIn
2024-03-23 20:33:56.962 | pid 1144 | detecthal               Yes
2024-03-23 20:33:56.962 | pid 1144 | winpe                   Yes
2024-03-23 20:33:56.962 | pid 1144 |
2024-03-23 20:33:56.962 | pid 1144 |
2024-03-23 20:33:56.962 | pid 1144 |
2024-03-23 20:33:56.962 | pid 1144 | Execute: bcdedit /enum {c1c70208-e972-11ee-9338-2079188d02a6}
2024-03-23 20:33:57.256 | pid 1144 | Exit code: 0, output:
2024-03-23 20:33:57.256 | pid 1144 |
2024-03-23 20:33:57.256 | pid 1144 | Windows Boot Loader
2024-03-23 20:33:57.256 | pid 1144 | -------------------
2024-03-23 20:33:57.256 | pid 1144 | identifier              {c1c70208-e972-11ee-9338-2079188d02a6}
2024-03-23 20:33:57.256 | pid 1144 | device                  ramdisk=[E:]\Recovery\WindowsRE\winre.wim,{c1c70207-e972-11ee-9338-2079188d02a6}
2024-03-23 20:33:57.256 | pid 1144 | path                    \Windows\System32\Boot\winload.efi
2024-03-23 20:33:57.256 | pid 1144 | description             WinRE
2024-03-23 20:33:57.256 | pid 1144 | locale                  es-MX
2024-03-23 20:33:57.256 | pid 1144 | isolatedcontext         Yes
2024-03-23 20:33:57.256 | pid 1144 | osdevice                ramdisk=[E:]\Recovery\WindowsRE\winre.wim,{c1c70207-e972-11ee-9338-2079188d02a6}
2024-03-23 20:33:57.256 | pid 1144 | systemroot              \Windows
2024-03-23 20:33:57.256 | pid 1144 | nx                      OptIn
2024-03-23 20:33:57.256 | pid 1144 | detecthal               Yes
2024-03-23 20:33:57.256 | pid 1144 | winpe                   Yes
2024-03-23 20:33:57.256 | pid 1144 |
2024-03-23 20:33:57.256 | pid 1144 |
2024-03-23 20:33:57.256 | pid 1144 |
2024-03-23 20:33:57.257 | pid 1144 | Read EFI variable: BootOrder Guid={8be4df61-93ca-11d2-aa0d-00e098032b8c} Attributes=7 Text='        ' Bytes='17 00 16 00 18 00 19 00'
2024-03-23 20:33:57.268 | pid 1144 | Disabled NVRAM entry for HackBGRT.
2024-03-23 20:33:57.269 | pid 1144 | HackBGRT has been disabled.
2024-03-23 20:33:57.270 | pid 1144 | Completed action 'disable' successfully.
2024-03-23 20:33:57.270 | pid 1144 | Running action 'enable-entry'.
2024-03-23 20:33:57.271 | pid 1144 | Execute: manage-bde -status
2024-03-23 20:33:57.574 | pid 1144 | Exit code: 0, output:
2024-03-23 20:33:57.574 | pid 1144 | BitLocker Drive Encryption: Configuration Tool version 10.0.19041
2024-03-23 20:33:57.574 | pid 1144 | Copyright (C) 2013 Microsoft Corporation. All rights reserved.
2024-03-23 20:33:57.574 | pid 1144 |
2024-03-23 20:33:57.574 | pid 1144 | Disk volumes that can be protected with
2024-03-23 20:33:57.574 | pid 1144 | BitLocker Drive Encryption:
2024-03-23 20:33:57.574 | pid 1144 | Volume C: []
2024-03-23 20:33:57.574 | pid 1144 | [OS Volume]
2024-03-23 20:33:57.574 | pid 1144 |
2024-03-23 20:33:57.574 | pid 1144 |     Size:                 948.20 GB
2024-03-23 20:33:57.574 | pid 1144 |     BitLocker Version:    2.0
2024-03-23 20:33:57.574 | pid 1144 |     Conversion Status:    Fully Encrypted
2024-03-23 20:33:57.574 | pid 1144 |     Percentage Encrypted: 100.0%
2024-03-23 20:33:57.574 | pid 1144 |     Encryption Method:    XTS-AES 128
2024-03-23 20:33:57.574 | pid 1144 |     Protection Status:    Protection On
2024-03-23 20:33:57.574 | pid 1144 |     Lock Status:          Unlocked
2024-03-23 20:33:57.574 | pid 1144 |     Identification Field: Unknown
2024-03-23 20:33:57.574 | pid 1144 |     Key Protectors:
2024-03-23 20:33:57.574 | pid 1144 |         Numerical Password
2024-03-23 20:33:57.574 | pid 1144 |         TPM And PIN
2024-03-23 20:33:57.574 | pid 1144 |
2024-03-23 20:33:57.574 | pid 1144 | Volume D: [Anhdv]
2024-03-23 20:33:57.574 | pid 1144 | [Data Volume]
2024-03-23 20:33:57.574 | pid 1144 |
2024-03-23 20:33:57.574 | pid 1144 |     Size:                 4.00 GB
2024-03-23 20:33:57.574 | pid 1144 |     BitLocker Version:    None
2024-03-23 20:33:57.574 | pid 1144 |     Conversion Status:    Fully Decrypted
2024-03-23 20:33:57.574 | pid 1144 |     Percentage Encrypted: 0.0%
2024-03-23 20:33:57.574 | pid 1144 |     Encryption Method:    None
2024-03-23 20:33:57.574 | pid 1144 |     Protection Status:    Protection Off
2024-03-23 20:33:57.574 | pid 1144 |     Lock Status:          Unlocked
2024-03-23 20:33:57.574 | pid 1144 |     Identification Field: None
2024-03-23 20:33:57.574 | pid 1144 |     Automatic Unlock:     Disabled
2024-03-23 20:33:57.574 | pid 1144 |     Key Protectors:       None Found
2024-03-23 20:33:57.574 | pid 1144 |
2024-03-23 20:33:57.574 | pid 1144 |
2024-03-23 20:33:57.574 | pid 1144 |
2024-03-23 20:33:57.574 | pid 1144 |
2024-03-23 20:33:57.574 | pid 1144 | BitLocker is enabled. Make sure you have your recovery key!
2024-03-23 20:33:57.574 | pid 1144 | Choose action (press a key):
2024-03-23 20:33:57.574 | pid 1144 |  I = Install anyway; THIS MAY BE DANGEROUS!
2024-03-23 20:33:57.574 | pid 1144 |  C = Cancel
2024-03-23 20:33:59.556 | pid 1144 | User input: I
2024-03-23 20:33:59.556 | pid 1144 |
2024-03-23 20:33:59.556 | pid 1144 | Continuing. THIS MAY BE DANGEROUS!
2024-03-23 20:33:59.556 | pid 1144 | Read EFI variable: BootOrder Guid={8be4df61-93ca-11d2-aa0d-00e098032b8c} Attributes=7 Text='        ' Bytes='17 00 16 00 18 00 19 00'
2024-03-23 20:33:59.556 | pid 1144 | Read EFI variable: BootCurrent Guid={8be4df61-93ca-11d2-aa0d-00e098032b8c} Attributes=6 Text='  ' Bytes='19 00'
2024-03-23 20:33:59.696 | pid 1144 |
2024-03-23 20:33:59.696 | pid 1144 | Unexpected error: MakeBootEntry: Windows Boot Manager not found.
2024-03-23 20:33:59.696 | pid 1144 | System.Exception: MakeBootEntry: Windows Boot Manager not found.
2024-03-23 20:33:59.696 | pid 1144 |    at Efi.MakeAndEnableBootEntry(String label, String fileName, Boolean alwaysCopyFromMS, Boolean dryRun)
2024-03-23 20:33:59.696 | pid 1144 |    at Setup.EnableEntry()
2024-03-23 20:33:59.696 | pid 1144 |    at Setup.<>c__DisplayClass45_0.b__2()
2024-03-23 20:33:59.696 | pid 1144 |    at Setup.<>c__DisplayClass45_0.b__1(Action enable, Action revert)
2024-03-23 20:33:59.696 | pid 1144 |    at Setup.RunPrivilegedActions(IEnumerable1 actions) 2024-03-23 20:33:59.696 | pid 1144 |    at Setup.Run(String[] args) 2024-03-23 20:33:59.712 | pid 1144 | If this is the most current release, please report this bug. 2024-03-23 20:33:59.712 | pid 1144 | If you need to report a bug, 2024-03-23 20:33:59.712 | pid 1144 |  - run this setup again with menu option L (show-boot-log) 2024-03-23 20:33:59.712 | pid 1144 |  - then include the setup.log file with your report. 2024-03-23 20:33:59.712 | pid 1144 | Press any key to quit. 2024-03-23 20:34:01.660 | pid 6512 |  2024-03-23 20:34:01.660 | pid 6512 | Error: Privileged action (install disable enable-entry) failed! 2024-03-23 20:34:01.660 | pid 6512 | Setup+SetupException: Privileged action (install disable enable-entry) failed! 2024-03-23 20:34:01.660 | pid 6512 |    at Setup.RunPrivilegedActions(IEnumerable1 actions)
2024-03-23 20:34:01.660 | pid 6512 |    at Setup.ShowMenu()
2024-03-23 20:34:01.660 | pid 6512 |    at Setup.Run(String[] args)
2024-03-23 20:34:01.660 | pid 6512 | If you need to report a bug,
2024-03-23 20:34:01.660 | pid 6512 |  - run this setup again with menu option L (show-boot-log)
2024-03-23 20:34:01.660 | pid 6512 |  - then include the setup.log file with your report.
2024-03-23 20:34:01.660 | pid 6512 | Press any key to quit.

Apparently you don't have a normal Windows boot entry, only some firmware-generated fallback entries.
Your log only shows the second install option (J). Did you try the first install option (I)?
It's better to attach the log and not copy-paste, it's very difficult to read this thread with such a long log attached.

I noticed now that Boot0019, which contains that bootmgfw.efi path, has some extra DevicePathNode components after the end-of-path marker. I will soon commit a patch to detect this somewhat unusual boot entry.


Fixed git import issues (MLDB-1487)

Commit is properly called, to avoid empty dataset issues
We accept messages with ISO-8859-1 encodings, and other encodings that are unknown simply cause the commit message to be skipped.
Note that the test is not enabled, since there is a separate error caused by problems with expression scope nesting.

+1


Form checkbox

Pull Request Template
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Config Change ( change to config or build process )
[x] I have read the CONTRIBUTING document.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.

[ ] I have updated the documentation accordingly.

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

1 / 4 of #46

Codecov Report

Merging #51 into master will decrease coverage by 0.63%.
The diff coverage is 76.92%.

@@            Coverage Diff             @@
##           master      #51      +/-   ##
==========================================
- Coverage    98.6%   97.96%   -0.64%
==========================================
  Files          49       50       +1
  Lines         430      443      +13
==========================================
+ Hits          424      434      +10
- Misses          6        9       +3

Impacted Files
Coverage Δ

src/Form/Checkbox.js
76.92% <76.92%> (ø)

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 2f455b9...6cb783f. Read the comment docs.


Side bar

Is it possible to have html in sidebar row data? I'm looking to have some a glyphicon / font awesome icon in the data rows.
Also, is it possible to have multiple right sidebar columns? I saw an older issue somewhat related but the answers seemed a bit vague.

Is it possible to have html in sidebar row data? I'm looking to have some a glyphicon / font awesome icon in the data rows.

You can use the groupRenderer prop to render whatever you'd like in the sidebar. Keep in mind that the sidebar items (and all rows) will not autoexpand their height based on their children's contents.  This is a result of us restricting the height of rows to the specified lineHeight prop to keep rows aligned.

Also, is it possible to have multiple right sidebar columns? I saw an older issue somewhat related but the answers seemed a bit vague.

It currently is not possible to have multiple right column sidebars.  There was a PR opened for this that I closed recently as there was no activity and I didn't think it was a feature that belonged in the core library.  You might be able to achieve the same using the groupRenderer prop above to render the multiple columns yourself

Yes it did. Thank you.


Cleanup: move user instantiation check inside else statement

We want the user instantiation to happen if user is None, and both _nick and _user_name have been given. Having this inside the else part of if user is not None: makes sense to me, because it contains other related code that runs only when the user is None.

This makes a lot of sense. Thank you.


Log aggregation for workloads

From Vince's idea:
You should be able to see all of the logs for a workload by selecting an action from the context menu for that workload.
Currently, if you want to see logs for a workload, you first need to go to the list of all the Pods within the workload and then get logs from individual Pods by clicking the action menu for each Pod. This is inconvenient, so there should also be a quick and easy way to aggregate all of a workload's logs from all of its Pods.

I can't remember where but this has been requested out in user land as well


Revert "[RC-1453] fx-ify the remote config service component"

Reverts DataDog/datadog-agent#22347
This change is causing unexpected crashes in case remote configuration is not initialized correctly.
As an example it will crash at startup if it's not initialized because of SSL verification being disabled globally but not disabled for remote configuration

force pushed to return the label pipeline that I couldn't rerun to get it pass

/merge


Can not build in Next.js 14

"dependencies": {
"@lifi/sdk": "^3.0.0-beta.0",
"@lifi/widget": "^3.0.0-beta.1",
"@mui/material": "5.15.19",
"@mui/material-nextjs": "5.15.11",
"next": "14.2.3",
"next-themes": "^0.3.0",
"react": "^18.3.1",
"react-cookie": "7.1.4",
"react-dom": "^18.3.1"
},
This is the dependencies and I got below error while building the project.

Please help me to fix this issue, Thanks

@codeninja0415 please upgrade to the latest versions of the Widget and SDK packages.

@chybisov what changed in lifi/sdk in latest version? I am getting an error that LiFi is not exported from lifi/sdk
import { LiFi } from "@lifi/sdk";

@codeninja0415 @haroon-schmrkow hey, sorry, I meant the latest beta versions of v3, since you are using them.

@chybisov yep, that's what I went for, 3.0.0-beta.1 of lifi/sdk, and I get that error

@haroon-schmrkow , @chybisov , I built the project successfully by changing the tsconfig.json file like below.
After updating the "target" from ES5 to ES2020, I could build the project successfully with the same version of @Lifi/SDK and @Lifi/Widget.
Thanks :)


added colab link

created a colab notebook for video inference using the pip package and added link with badge to repo.
Link = https://colab.research.google.com/drive/1XiC6vihCXzCeCpwk9vVi38l4cIIVdwCx?usp=sharing

bumping for vis, any remaining issues with the notebook or merge?
last feedback about getting the API key out of the notebook was performed.

Who has review for this? I'd like to add this notebook to the knowledge base along with a guide to using video inference


Running Firestore Emulator From Just Prevents Control C

I have the following in a Justfile.
start:
    gcloud emulators firestore start

If I run the command on it's own, I am able to CTRL+C to stop the emulator. If I run the command through just with just start, CTRL+C does nothing.

For a reproducible example of this here's a shell.nix which will set up an environment that demonstrates this.
{ pkgs ? import <nixpkgs> {} }:
let
    gcloud = pkgs.google-cloud-sdk.withExtraComponents([
        pkgs.google-cloud-sdk.components.cloud-firestore-emulator
    ]);
    shell = pkgs.mkShell {
        buildInputs = [
            pkgs.just
            pkgs.jdk11
            gcloud
        ];
    };
in
shell

If you run
nix-shell --pure
gcloud emulators firestore start
<C-c>
just start
<C-c>

You'll see the first control C does stop the program, but the second one does nothing (and the only way to exit is to start a new terminal and kill the java process).
Hopefully the nix environment is enough to reproduce the error (that's the whole point of nix after all)!

Checkout issue #302

To my knowledge that feature was never added. Sorry, I thought that was obvious from the other discussion. Maybe not as cut-and-dry as I thought though.

The issue was closed as completed and it looked to me as https://github.com/casey/just/pull/345 provided this functionality somehow? I may have misunderstood! So there is no way to have signals be forwarded to the program Just is running? and there's no scope planned for this to be implemented?

Ah, you're right. Looks like that was my mistake. Not sure how to activate it or anything. @casey ?

Closing in favor of #2473, where I've tried to collect everything related to signal handling in one place. Take a look and see if I've missed anything! A reproduction of this which doesn't depend on gcloud would be much appreciated.


Logic for split-year charge

closes #501
waiting for accountant approval

Split the non-current year into two, as we do on signle-year-of-relevance


feat(example): add blank slate rust provider

Feature or Problem
This PR adds a "blank slate" capability provider that's purpose made to inform deeply how to use the wasmcloud-provider-sdk, and where each piece fits into implementing a custom provider. I've included a test component as well in order to try out the provider, and a few workflows to get started quickly with writing and debugging a custom capability.
There will be two followups to this PR:

Mirroring this exact example with the provider-sdk-go, and a tinygo component, to give another comprehensive guide
Documentation on https://wasmcloud.com on the workflow that I have in mind, being 1. use wash new to generate this template, 2. update the WIT to fit a custom interface based on an idea, 3. implement the new logic, 4. run

Related Issues

Release Information

Consumer Impact

Testing

Unit Test(s)

Acceptance or Integration

Manual Verification
I ran through these READMEs and the application flow, but more testing is appreciated!

Hey @brooksmtownsend what do you think about the name? blank-state is OK but maybe... template or example might be nice?

@vados-cosmonic Honestly I'm not too dedicated to blank slate 😄 Template is good, I think just something that provides the message that this is a sample but meant to be used as a "base" for a custom provider is perfect

Oh also another thing I was thinking is that this is will be an input to wash new right? so a more generic name like that might be very useful/good for docs

Good point. Perhaps it could be custom-template, is that too generic?


chore(Dockerfile): add sbom-utility

Cyclonedx-cli is causing failures after updating syft version and it is not up to date. Sbom-utility does the same thing, with the same commands, it is also maintained by cyclonedx, but it is more up to date and written in Go.

This is associated pr that also updates the check sbom task https://github.com/redhat-appstudio/build-definitions/pull/503

Hmm, what's the proper Conventional Commits type here?

I would keep both utilities, at least for some time.

Hmm, what's the proper Conventional Commits type here?

It's according to this: https://www.conventionalcommits.org/en/v1.0.0/
So it should be something like chore: replace cyclonedx-cli with sbom-utility.

Hmm, what's the proper Conventional Commits type here?

Maybe chore? https://gist.github.com/joshbuchea/6f47e86d2510bce28f8e7f42ae84c716

I would keep both utilities, at least for some time.

Updated

commit & pr name shouldn't be 'chore'

commit & pr name shouldn't be 'chore'

I am not sure what you mean here?

I don't have the permissions to merge here, could you please merge this?


game_files

Added a file under game files to code for game space invaders

I'm not accepting this PR. It's not structured properly. And it should be in the bustle.py. The new components have not been added to requirements.txt.


 Looks at the really slow ones. Did some changes to make them faster or eliminate them because they're not really necessary. Found a flakey test during this and fixed that as well.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1582  👈
#1580
main

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

Join @bidetofevil and the rest of your teammates on  Graphite

Merge activity

Oct 24, 1:00 PM EDT: A user merged this pull request with Graphite.


[mainnet] seeds & persistent_peers need to be refreshed & extended

akash 0.16.4

all 3 seeds are offline;
RPC could not start with the current persistent_peers;
have successfully used Polkachu's live peers from https://www.polkachu.com/live_peers/akash - we should probably update our peers with those from their list;

we should probably make a periodic/cron gh action that syncs the list with polkachu

@sacreman maybe even worth having something that would alert us in the alert slack channel whenever some peers are offline for longer than 24 hours, WDYT?

resolved by https://github.com/ovrclk/net/pull/471
followed-up by https://github.com/ovrclk/engineering/issues/375


Add Github to known_hosts

What does this do / why do we need it?
This commit manually instructs Travis to add github.com to ~/.ssh/known_hosts. It looks like this was not added to the new build images.
What should your reviewer look out for in this PR?
Builds should pass on newer Travis builds.
Which issue(s) does this PR fix?
fixes #1428

omg. really? wow. 🤦♀

@arbourd You are the best! Thank you for jumping on this and making our problems go away. It is incredibly helpful! ✨ ❤ 🙇♀ 🍻


[analyzer][fix] Invocation list YAML config no longer break lines

The config file 'invocation-list.yml' may contain line breaks inside
list items. However, this is not properly supported by the analyzer YAML
parser. This fix sets the line width parameter to very high value.

Apart from fixing lint errors, I have a question:
Should the upgrade to pathlib be a separate patch (and that would then upgrade every use of os.path to pathlib.Path alternatives) or just do it here for only this test case (that would mean 1 patch, but 2 commits, one is where I upgrade this test file to pathlib, and another where I implement the new test case)?

Updated with the bare version.

Apart from fixing lint errors, I have a question:
Should the upgrade to pathlib be a separate patch (and that would then upgrade every use of os.path to pathlib.Path alternatives) or just do it here for only this test case (that would mean 1 patch, but 2 commits, one is where I upgrade this test file to pathlib, and another where I implement the new test case)?

I am okay to have all this in one PR.

Tests need to be fixed but apart from that it looks good.

Just fixed typos removed the unused YAML import line, and extended the documentation text a bit in the last few pushes.


tests: align pytest version across requirements

Description
Align pytest across pip requirements files

Is this file even needed? If there was a mismatch but CI & build pass, is it even used? One of the 2 is not required I presume

I was afraid.. now removed from dev-requirements, let's see CI passes

I don't think it'll pass because the tests don't install dev-requirements.txt. For all I care you can merge both into dev-requirements.txt and install it in test.sh.


TestCafe takes a blank white page screenshot when running Chrome

What is your Scenario?
I am running TestCafe v.2.5.1-rc.1 in a Dockerized environment. I have screenshots takeOnFails set to true, however, when I go to open up the screenshot .png TestCafe creates, it appears to just be a blank white page every time.
I have read a TestCafe thread about a similar issue here which suggested to disable the 'Use hardware acceleration when available' option. I have done so by passing in the --disable-gpu chrome flag, but alas, still no luck.
I initially was using TestCafe v1.18.6 but upgraded to the latest hoping this issue would resolve on its own, but I get the same exact behavior with both versions.
What is the Current behavior?
TestCafe takeOnFails screenshot will take a screenshot when a Test fails, but the image will be a blank white page.
What is the Expected behavior?
TestCafe takeOnFails screenshot takes a screenshot of the UI when a Test fails, and I can see it in the corresponding .png.
What is your public website URL? (or attach your complete example)
The application is private and I cannot share anything here. But I can reproduce with TestCafe's "Getting Started" example.
What is your TestCafe test code?
fixture('Getting Started')
.page('https://devexpress.github.io/testcafe/example');
test('My first test', async t => {
await t
.typeText('#developer-name', 'John Smith')
.click('#submit-button');
});
test('My second test', async t => {
await t
.typeText('#developer-name', 'John Smith')
.click('#submit-button');
});
test('My third test', async t => {
await t
.typeText('#developer-name', 'John Smith')
.click('#submit-button');
});
test('My fourth test', async t => {
await t
.typeText('#developer-name', 'John Smith')
.click('#submit-button');
});
test('My fifth test', async t => {
await t
.typeText('#developer-name', 'John Smith')
.click('#submit-button');
});
test('My sixth test', async t => {
await t
.typeText('#developer-name', 'John Smith')
.click('#submit-button');
});
test('My seventh test', async t => {
await t
.typeText('#developer-name', 'John Smith')
.click('#submit-button');
});
test('My eighth test', async t => {
await t
.typeText('#developer-name', 'John Smith')
.click('#submit-button');
});
test('My ninth test', async t => {
await t
.typeText('#developer-name', 'John Smith')
.click('#submit-button');
});
test('My tenth test', async t => {
await t
.typeText('#developer-name', 'John Smith')
.click('#submit-button');
});
Your complete configuration file
No response
Your complete test report
No response
Screenshots
No response
Steps to Reproduce

Run TestCafe 2.5.1-rc.1 in a Dockerized environment with screenshots takeOnFail set to True.
Have the test purposely fail to cause a screenshot to get created.
Inspect the screenshot

TestCafe version
2.5.1-rc.1
Node.js version
16.20.0
Command-line arguments
--disable-gpu --no-sandbox --disable-dev-shm-usage
Browser name(s) and version(s)
Chrome 105.0.5195.52
Platform(s) and version(s)
Ubuntu 18.04
Other
I was able to reproduce this issue using TestCafe's "Getting Started" example, to simplify the matters.
The screenshot functionality works in my experience when running TestCafe in a Linux VM, but when I try to run TestCafe in a Dockerized environment I get this issue (note, I am not using the TestCafe Docker image provided, instead I am using a custom Docker image).

Hello @collinharmon,
I was unable to reproduce the issue with a simple Docker image. All the screenshots are taken correctly. Here is my project example: https://github.com/Dmitry-Ostashev/testcafe-kubernetes-example/tree/take-screenshot.
Could you please share your image or modify my Dockerfile from the repo and branch mentioned above to reproduce the issue?

Hi i had the same problem.
The page is a huge react page (5MB) which loads a tons of js files, when the page is initialized.
Disabling the /dev/shm usage with the --disable-dev-shm-usage flag was not helping.
Taking a screenshot was always resulting in a white page. When i change the test url to another page, i got a screenshot with content from it.
So my guess was that the problem ist not K8s, it is the huge react page.
I enabled logging each request with:
const logger = RequestLogger({  }, {
  logResponseHeaders: true,
   logResponseBody:    true
});

and
fixture`Test`
        .page(url)
        .requestHooks(logger);

test.only("just some testing", async t => {
    console.log(await logger.requests);
})

Suddenly i could see all the requests and i got a screenshot with the content.
So i dig deeper into the problem, why adding a requesthook was solving my problem.
So starting the test with DEBUG=hammerhead:,testcafe:
I found this Problem:  net::ERR_INSUFFICIENT_RESOURCES
So in the net the solution for this is to increase the /dev/shm size. I was not sure why this happened because i had the --disable-dev-shm-usage set on my run.
So my wild guess is that the chromium or firefox are using /dev/shm when fetching js files from the net.
And adding the requesthook changes it from being called parallel in serial so /dev/shm is not so heavily used.
The /dev/shm device was 64mb big in my k8s pod.
Adding:
  volumes:
    - name: dshm
      emptyDir:
        medium: Memory
        sizeLimit: 1Gi

and
      volumeMounts:
        - mountPath: /dev/shm
          name: dshm

Fixed the problem so i don't need the requesthook anymore.


Wrong co-ordinates captured from PyVistaQt window in QStackedWidget

I would like to use a simple point picker by right clicking on a mesh.  The example here in issue 239 works well: https://github.com/pyvista/pyvista-support/issues/239
However, when this code is incorporated into PyQt5 where the plotter has been embedded as a QStackedWidget, the captured mouse co-ordinates are wrong.  I have added a line to the Issue 239 example above to plot the point of the mouse co-ordinates.
Using the existing function:  enable_point_picking, also has this effect of capturing the mouse co-ordinates incorrectly.
I would expect the enable_point_picking function or issue 239 example to work when the plotter is embedded as a QStackedWidget in Pyqt5.

To Reproduce
Please include a code snippet to reproduce the bug in the block below:
# Insert code here
import sys
import pyvista as pv
from pyvista import examples
import pyvistaqt as pvqt
import numpy as np
from PyQt5 import QtCore, QtGui, QtWidgets     # pip3 install pyqt5
from PyQt5.QtCore import * #QFile, QFileInfo, Qt, QSortFilterProxyModel, QAbstractTableModel
from PyQt5.QtGui import * # QPen, QStandardItem, QStandardItemModel, QPushButton
from PyQt5.QtWidgets import * #QStyledItemDelegate, QApplication, QHeaderView, QTableView, QWidget, QHBoxLayout, QVBoxLayout, QAbstractItemView, QListWidget, QPushButton, QMenu, QMessageBox,QDialog

class Picker:
    def __init__(self, plotter, mesh):
        self.plotter = plotter
        self.mesh = mesh
        self._points = []

    @property
    def points(self):
        """To access all th points when done."""
        return self._points

    def __call__(self, *args):
        picked_pt = np.array(self.plotter.pick_mouse_position())

        # Line below added to show where mouse position is...
        w.plotter.add_mesh(pv.Sphere(radius=3, center=picked_pt), color='pink')

        direction = picked_pt - self.plotter.camera_position[0]
        direction = direction / np.linalg.norm(direction)
        start = picked_pt - 1000 * direction
        end = picked_pt + 10000 * direction
        point, ix = self.mesh.ray_trace(start, end, first_point=True)
        if len(point) > 0:
            self._points.append(point)
            q = w.plotter.add_mesh(pv.Sphere(radius=3, center=point),
                           color='red')
        return

class OpNote(QDialog):
    def __init__(self):
        super().__init__()
        mesh = examples.load_airplane()
        self.tabs = QStackedWidget(self)
        self.tabs.setObjectName("tabs")
        self.tabs.setGeometry(QtCore.QRect(370, 210, 461, 441))

        self.tabs.setCursor(QCursor(QtCore.Qt.SizeAllCursor))

        self.plotter = pvqt.QtInteractor()
        self.plotter.add_mesh(mesh, show_edges=True, color='w')

        self.tabs.addWidget(self.plotter.interactor)

        picker = Picker(self.plotter, mesh)
        self.plotter.track_click_position(picker, side='right')
        self.plotter.add_text('Use right mouse click to pick points')

app=QtWidgets.QApplication(sys.argv)
w = OpNote()
w.show()
app.exec_()

Screenshots
If applicable, add screenshots to help explain your problem.

System Information:
Please run the following code wherever you are experiencing the bug and paste the output below. This report helps us track down bugs and it is critical to addressing your bug:
# Get system info
import pyvista as pv
print(pv.Report())

# Paste system info here
--------------------------------------------------------------------------------
  Date: Wed Jul 28 10:17:53 2021 BST

                OS : Darwin
            CPU(s) : 8
           Machine : x86_64
      Architecture : 64bit
       Environment : Python
        GPU Vendor : Apple
      GPU Renderer : Apple M1
       GPU Version : 4.1 Metal - 71.0.7

  Python 3.9.1 (v3.9.1:1e5d33e9b9, Dec  7 2020, 12:10:52)  [Clang 6.0
  (clang-600.0.57)]

           pyvista : 0.31.3
               vtk : 9.0.20210612
             numpy : 1.19.5
           imageio : 2.9.0
           appdirs : 1.4.4
            scooby : 0.5.7
            meshio : 4.4.6
        matplotlib : 3.3.3
         pyvistaqt : 0.5.0
             PyQt5 : 5.15.4
             scipy : 1.7.0
              tqdm : 4.61.1
--------------------------------------------------------------------------------

when this code is incorporated into PyQt5 where the plotter has been embedded as a QStackedWidget, the captured mouse co-ordinates are wrong

Strange indeed.  I'm not sure what magic is going inside Qt, but my guess is it's passing events from the widget to VTK and the coordinates aren't being transferred properly.  If you can figure out how they're being miss-translated, we could add a hook into pyvistaqt that could translate coordinates properly.

I have the same problem. Do you have a solution for this problem?
The problem is that the coordinates obtained by pick_click_position of pyvista are not accurate.

I am encountering the same issue for a DockedView.
I defined my own class, which inherits the QtInteractor class. It seems that the central widget needs to be the QtInteractor for the coordinates to work correctly(?).
I tried to remove the integration as a DockedWidget and simply called self.show() to display the plot in a new Window.
Here, the coordinates are still wrong. When closing the window, the same window reappears with a new title. Now, the interaction is much smoother and the picking works correctly.
Here is some code:
from pyvistaqt import QtInteractor
from pyvistaqt import BackgroundPlotter
import pyvista as pv
from PyQt6.QtGui import *
from PyQt6.QtWidgets import *
from PyQt6.QtCore import *
import numpy as np
import threading
from pyvista import examples

class Picker:
    def __init__(self, plotter, mesh):
        self.plotter = plotter
        self.mesh = mesh
        self._points = []

    @property
    def points(self):
        return self._points

    def __call__(self, *args):
        picked_pt = np.array(self.plotter.pick_click_position())
        direction = picked_pt - self.plotter.camera_position[0]
        direction = direction / np.linalg.norm(direction)
        start = picked_pt - 1000 * direction
        end = picked_pt + 1000 * direction
        self._points.append(picked_pt)
        w = self.plotter.add_mesh(pv.Sphere(radius=300, center=picked_pt), color="red")

class CustomInteractor(QtInteractor):
    def __init__(self, BasePlotter, root):

        self.actor = None
        self.mesh = None
        self.current_camera_pos = None
        self.scaler = 1.0

        super().__init__()

    def remesh(
        self, mesh=None):

        if mesh is not None:
            if self.current_camera_pos is not None:
                self.current_camera_pos = self.camera_position

            self.clear_actors()

            self.actor = self.add_mesh(
                mesh,
                smooth_shading=False,
                render_lines_as_tubes=True,
                show_scalar_bar=False,
                # pickable=True,
            )

            picker = Picker(self, self.mesh)
            self.track_click_position(picker, side="right")

        else:
            return

    def plot_preview(self):

        mesh = examples.load_airplane()

        # open new windows with the plot
        self.iren.reset_picker()
        if self.iren is not None:
            self.show()

It would be awesome to get to the second plot (after closing the first one) or simply wrapping the normal pyvista.plotter in a qtwindow, that can be closed without crashing the whole application.
When walking along the stack call I came to the same conclusion as @2umbrella, that pick_click_position() returns a wrong value. This happens in the vtk backend so there is not much we can really do. The coordinates of click_position are correct.
It would be awesome if someone with more insight could have a look at this problem.Being able to dock the plotting view and beaing able to use picking would be awesome for interacting in a complex ui.


Dev

Codecov Report

Merging #59 (d670f4c) into main (1358e8a) will decrease coverage by 0.15%.
The diff coverage is 44.44%.

@@            Coverage Diff             @@
##             main      #59      +/-   ##
==========================================
- Coverage   64.21%   64.05%   -0.16%
==========================================
  Files           2        2
  Lines        1425     1430       +5
  Branches      504      508       +4
==========================================
+ Hits          915      916       +1
  Misses         55       55
- Partials      455      459       +4

Impacted Files
Coverage Δ

include/hspp.h
72.50% <ø> (ø)

include/concurrent.h
47.74% <44.44%> (-0.29%)
:arrow_down:

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


Can this code be implemented on CLASSFICATION problem as well?

Hi and Thank you so much for your AMNet code.
I've been thinking that whether this code can be implemented on classification problem coz it seems that I can't attain a satisfactory result on my classification problem, compared with those regression problems.
To be specific, I've changed the MSE loss to CE loss.
Could you plz give me some advice?
Thx a lot and wish you a good day :)

Hi JingyuanYangXD,
Sorry for this very late reply. Indeed, turning the regression problem into classification is feasible, with some benefits and, of course, problems :-( In our new work we have been using similar idea, however simply treating the regression as classification does not improve the performance. Unfortunately I cannot tell you more at this time since we are just finalising our experiments for our new paper.
Kind Regards
Jiri

Dear Jiri,
Thank you so much for your kind reply, and I am looking forward for your new paper!
Wish you a nice day :)
Best Regards
Jingyuan
---------- Origin message ----------

From："Jiri Fajtl"<EMAIL_ADDRESS>To："ok1zjf/AMNet"<EMAIL_ADDRESS>Subject：Re: [ok1zjf/AMNet] Can this code be implemented on CLASSFICATION problem as well? (#2)
Date：2019-04-23 22:25:33

Hi JingyuanYangXD,
Sorry for this very late reply. Indeed, turning the regression problem into classification is feasible, with some benefits and, of course, problems :-( In our new work we have been using similar idea, however simply treating the regression as classification does not improve the performance. Unfortunately I cannot tell you more at this time since we are just finalising our experiments for our new paper.
Kind Regards
Jiri
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/ok1zjf/AMNet/issues/2#issuecomment-485825719


Wrong territory resolution for Switzerland

Territory.fromString("CHE-GR") result into MX-GRO territory where i would expect it result into CHE or throw UnknownTerritoryException.

The issue has been confirmed. We'll look into this.

OK. Here's what happened: the "state" GR does not exist in country CHE, so it is looked up in other other countries. Country MX has a state GRO, with alias GR. This is why MX-GR is matched instead.
We'll discuss this internally and see how we can improve the behavior of this API. Until then, we'll leave the issue open. Thanks for reporting.

Fixed in release 2.2.3.


Revert "[Autoplay policy] Add MediaStream section"

Reverts google/WebFundamentals#6120

Whoops!
There were 3 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2017/09/autoplay-policy-changes.md#L194 - '

:tada: This has been pushed live to https://developers.google.com/web/


Fixes 404 error

There seems to be an issue with either Github/Linguist or Github itself, the HEAD doesn't have the *.yml files anymore. Changed to master to make sure the files are still there. A better fix should be considered, for example with an immutable tag.

I just published my fork under "linguist-js-cw". It will not be maintained after this PR is merged.

I prefer fetching the resources so I don't have to issue releases every so often. This 404 issue should be a one-off. If there's more issues surrounding the fetching then yeah maybe I could have JSON files embedded to either fall back to or use instead of the HTTP reqs but for now this is the method I think is better.

I have added an offline option to v2.5 to alleviate this issue in the future. The metadata files are now packaged though I won't be releasing patch versions just to bump its contents.