Meet  an ValueError when I replace RingNetwork with HighwayNetwork for network in the tutorial03

In the tutorial03, I replace RingNetwork with HighwayNetwork for network ,but I meet an  ValueError:
Traceback (most recent call last):
  File "/home/vcdc/anaconda3/envs/flow/lib/python3.7/site-packages/ray/tune/trial_runner.py", line 426, in _process_trial
    result = self.trial_executor.fetch_result(trial)
  File "/home/vcdc/anaconda3/envs/flow/lib/python3.7/site-packages/ray/tune/ray_trial_executor.py", line 378, in fetch_result
    result = ray.get(trial_future[0], DEFAULT_GET_TIMEOUT)
  File "/home/vcdc/anaconda3/envs/flow/lib/python3.7/site-packages/ray/worker.py", line 1457, in get
    raise value.as_instanceof_cause()
ray.exceptions.RayTaskError(ValueError): ray::PPO.train() (pid=10954, ip=<IP_ADDRESS>)
  File "python/ray/_raylet.pyx", line 636, in ray._raylet.execute_task
  File "python/ray/_raylet.pyx", line 619, in ray._raylet.execute_task.function_executor
  File "/home/vcdc/anaconda3/envs/flow/lib/python3.7/site-packages/ray/rllib/agents/trainer.py", line 444, in train
    raise e
  File "/home/vcdc/anaconda3/envs/flow/lib/python3.7/site-packages/ray/rllib/agents/trainer.py", line 433, in train
    result = Trainable.train(self)
  File "/home/vcdc/anaconda3/envs/flow/lib/python3.7/site-packages/ray/tune/trainable.py", line 176, in train
    result = self._train()
  File "/home/vcdc/anaconda3/envs/flow/lib/python3.7/site-packages/ray/rllib/agents/trainer_template.py", line 129, in _train
    fetches = self.optimizer.step()
  File "/home/vcdc/anaconda3/envs/flow/lib/python3.7/site-packages/ray/rllib/optimizers/multi_gpu_optimizer.py", line 140, in step
    self.num_envs_per_worker, self.train_batch_size)
  File "/home/vcdc/anaconda3/envs/flow/lib/python3.7/site-packages/ray/rllib/optimizers/rollout.py", line 29, in collect_samples
    next_sample = ray_get_and_free(fut_sample)
  File "/home/vcdc/anaconda3/envs/flow/lib/python3.7/site-packages/ray/rllib/utils/memory.py", line 33, in ray_get_and_free
    result = ray.get(object_ids)
ray.exceptions.RayTaskError(ValueError): ray::RolloutWorker.sample() (pid=11030, ip=<IP_ADDRESS>)
  File "/home/vcdc/anaconda3/envs/flow/lib/python3.7/site-packages/ray/rllib/utils/tf_run_builder.py", line 94, in run_timeline
    fetches = sess.run(ops, feed_dict=feed_dict)
  File "/home/vcdc/anaconda3/envs/flow/lib/python3.7/site-packages/tensorflow_core/python/client/session.py", line 956, in run
    run_metadata_ptr)
  File "/home/vcdc/anaconda3/envs/flow/lib/python3.7/site-packages/tensorflow_core/python/client/session.py", line 1156, in _run
    (np_val.shape, subfeed_t.name, str(subfeed_t.get_shape())))
ValueError: Cannot feed value of shape (1, 42) for Tensor 'default_policy/observation:0', which has shape '(?, 44)'

During handling of the above exception, another exception occurred:

ray::RolloutWorker.sample() (pid=11030, ip=<IP_ADDRESS>)
  File "python/ray/_raylet.pyx", line 633, in ray._raylet.execute_task
  File "python/ray/_raylet.pyx", line 634, in ray._raylet.execute_task
  File "python/ray/_raylet.pyx", line 636, in ray._raylet.execute_task
  File "python/ray/_raylet.pyx", line 619, in ray._raylet.execute_task.function_executor
  File "/home/vcdc/anaconda3/envs/flow/lib/python3.7/site-packages/ray/rllib/evaluation/rollout_worker.py", line 471, in sample
    batches = [self.input_reader.next()]
  File "/home/vcdc/anaconda3/envs/flow/lib/python3.7/site-packages/ray/rllib/evaluation/sampler.py", line 56, in next
    batches = [self.get_data()]
  File "/home/vcdc/anaconda3/envs/flow/lib/python3.7/site-packages/ray/rllib/evaluation/sampler.py", line 99, in get_data
    item = next(self.rollout_provider)
  File "/home/vcdc/anaconda3/envs/flow/lib/python3.7/site-packages/ray/rllib/evaluation/sampler.py", line 327, in _env_runner
    active_episodes)
  File "/home/vcdc/anaconda3/envs/flow/lib/python3.7/site-packages/ray/rllib/evaluation/sampler.py", line 551, in _do_policy_eval
    eval_results[k] = builder.get(v)
  File "/home/vcdc/anaconda3/envs/flow/lib/python3.7/site-packages/ray/rllib/utils/tf_run_builder.py", line 53, in get
    self.fetches, self.feed_dict))
ValueError: Error fetching: [<tf.Tensor 'default_policy/add:0' shape=(?, 1) dtype=float32>, {'action_prob': <tf.Tensor 'default_policy/Exp_1:0' shape=(?,) dtype=float32>, 'action_logp': <tf.Tensor 'default_policy/sub_2:0' shape=(?,) dtype=float32>, 'vf_preds': <tf.Tensor 'default_policy/Reshape:0' shape=(?,) dtype=float32>, 'behaviour_logits': <tf.Tensor 'default_policy/model/fc_out/BiasAdd:0' shape=(?, 2) dtype=float32>}], feed_dict={<tf.Tensor 'default_policy/observation:0' shape=(?, 44) dtype=float32>: [array([0.44409109, 0.44405716, 0.44405939, 0.44408473, 0.44404423,
       0.44407543, 0.44402707, 0.44407156, 0.44409773, 0.44407641,
       0.44411795, 0.44408998, 0.4440337 , 0.44362106, 0.44408406,
       0.44404458, 0.44409067, 0.3988301 , 0.44532913, 0.44532913,
       0.01731031, 0.09245801, 0.09184036, 0.09243479, 0.09184368,
       0.27578934, 0.27271432, 0.27350743, 0.27468785, 0.45574352,
       0.45488228, 0.45227   , 0.45656885, 0.63957073, 0.63730218,
       0.63756669, 0.63982425, 0.81881247, 0.81595532, 0.81928188,
       0.81876308, 0.91137627])], <tf.Tensor 'default_policy/action:0' shape=(?, 1) dtype=float32>: [array([0.7231164], dtype=float32)], <tf.Tensor 'default_policy/prev_reward:0' shape=(?,) dtype=float32>: [0.41458751306631525], <tf.Tensor 'default_policy/PlaceholderWithDefault:0' shape=() dtype=bool>: False}

When I set the horizon to a low value(eg. 110),It is correct,but it produce the error above when I set the horizon to a high value(eg.200)
Why?

I also got this error and I see no one currently supports the use of this tool. This team hasn't commented for almost a year now


[Fix] webviewTag: true

You now need to explicitly enable webviewTag in your webPreferences object.
https://github.com/electron/electron/issues/18145

Thanks.


Main flow already simplified - what else to do?

So, we've already stripped out the initial subsampling approach, and the 'adaptive' workflow is the already default.  So the two solution routes are 1) adaptive and 2) use one of the scipy minimizers, either with gradient or gradient-and-hessian type solvers.
I probably could simplify the solver code a bit; for example, currently there's a complicated solver_protocol object (tuple of dicts) that we really aren't using now, since it's now single phase (and we probably will leave it single phase).
But methodologically, it's pretty straightforward already.
Thoughts on what additional simplification could/should be done?

Actually, one todo - make the warning errors clearer so people know what to check in their data input .

Should we create a new issue for the warnings clarification?

Should we create a new issue for the warnings clarification?

OK, I did that #358.


Landing Page Migration

Description:

Migrate currently  CLARISA landing page to new CLARISA standalone

As discussed with @JuankCadavid, we request @yecksin help to know how to proceed with this issue


Disconnect/Reconnect Fails with Error code 22, "Authentication required"

After locally resolving the issue reported in issue #35 I found there is a further issue preventing successful Disconnect/Reconnect calls (or any IPP call that requires the OAuth headers).
When using PlatformService, the service context is overridden to IPP to ensure the correct endpoint is called:
        // Set the service type to IPP by calling a method
        $this->serviceContext->UsePlatformServices();

Issue here is that in SyncRestHandler, the sendRequest() function does not set the required headers for these IPP context calls (only the user agent is set), hence the OAuth credentials being discarded from the request and the resulting Error code 22 "Authentication required":
if (CoreConstants::IntuitServicesTypeQBO ==$this->context->serviceType) {
            // IDS call
            $httpHeaders = array(
                'Authorization' => $AuthorizationHeader,
                'host'          => parse_url($requestUri, PHP_URL_HOST),
                'user-agent'    => CoreConstants::USERAGENT,
                'accept'        => $this->getAcceptContentType($requestParameters->ContentType),
                'connection'    => 'close',
                'content-type'  => $requestParameters->ContentType,
                'content-length'=> strlen($requestBody)
            );

            // Log Request Body to a file
            $this->RequestLogging->LogPlatformRequests($requestBody, $requestUri, $httpHeaders, true);

            if ($requestBody && $this->RequestCompressor) {
                $this->RequestCompressor->Compress($httpHeaders, $requestBody);
            }

            if ($this->ResponseCompressor) {
                $this->ResponseCompressor->PrepareDecompress($httpHeaders);
            }
        } else {
            // IPP call
            $httpHeaders = array('user-agent' => CoreConstants::USERAGENT);
        }

Regards,
Mark

@markwoods241
Fixed on v3.2.6


[Request] Scroll behaviour

Sometimes, mostly when writing code blocks, it overflows the terminal/screen vertical viewport. I would be awesome the ability to “scroll down” to a slide content, if it is even possible.
For now the solution is to break the code block into smaller ones to fit the screen size, on different sldies.

I think typically presentation tools don't allow scrolling and you need to adjust the content to fit on the slide. I'd even say if your code is so long if doesn't fit into a single slide then you probably should split it.
I'll look into this tho. The terminal does support scrolling so it would be a matter of hooking that into a hotkey and seeing what breaks.

I think your first point makes a lot of sense. However, there's something different about using these kind of tools of slides on the terminal. It's very hard to predict the amount of space required. I can increase/decrease the font at my wish, and also the screen size. So I have to prepare my slides with a specific screen size and font size/zoom in mind, and if something changes it can break visibility.
Thinking about this, I think it would make sense to scroll (and maybe hook that into J/K up/down?) the screen.
However, if some kind of PDF or image export in the future is on your mind, users who use it with scrolling in mind would make their content do not fit a PDF page. Maybe that's a tradeoff, in this case, that is okay. Don't know, just thinking out loud here, haha.

So I have to prepare my slides with a specific screen size and font size/zoom in mind, and if something changes it can break visibility.

Yeah, my thoughts on this is you should probably develop the slides in a specific terminal size and then use that same terminal size when displaying it. e.g. have an alias like alias presenterm-terminal=your-terminal-emulator --width x --height y. I'll see how this works, in theory it should be simple but I need to see how images look like with scrolling + the footer is probably by default going to be "scrollable" too so unless I do something about it, you will only see the footer once you scroll to the bottom.

However, if some kind of PDF or image export in the future is on your mind,
That is already implemented :).

in theory it should be simple

Famous last words. The scrolling API in the terminal just moves the visible text up/down so it won't show the text that's off-screen. This requires tracking whether the text overflowed and doing the translation ourselves which is a lot more involved.
As for API, any concerns with using a separate set of keys for this? hjkl are already used to move to the next/previous slides so I was thinking something else. Maybe C-d and C-u? Thoughts?

I just created #209 which sort of tackles this problem from another angle. Rather than letting you scroll, that change lets you detect that the presentation overflows the terminal screen. This lets you at least figure out whether there's overflows without having to scroll through every slide every time you make a change/start the app.

I'd also like to be able to scroll the command output pane(?).

As for API, any concerns with using a separate set of keys for this? hjkl are already used to move to the next/previous slides so I was thinking something else. Maybe C-d and C-u? Thoughts?

As for the API, ctrl u/d make sense for me but I wouldn't say they're as discoverable.
I think it would make sense for something like this as well:

h/l: prev/next slide
j/k: down/up on current slide, if at at the start/end => prev/next slide

So for most people j/k would work as usual still.

Some tools like reveal.js have bidirectional slides.
Perhaps an idea for this case would be to have overflowed text become a new vertical slide as well as having a <!-- break --> command to manually split a slide into vertical one.
Sounds a bit complicated to implement but it would fix an issue and create a cool feature in one go.
Issues I see currently would be the output pane and visualization of vertical slides (currently there is only a bar, and we don't have fancy animations :) ).


move topbar inside titlebar breaks drop down in queue

Environment

Spotify Version: <IP_ADDRESS>1.g0348b2ea
Spicetify Version: v2.28.0
Platform (WIN, MAC, LINUX): WIN

Theme Information

Installed via Marketplace Or CLI: Marketplace

Describe the bug
when having "move topbar inside titlebar" enabled it breaks the drop down in queue not allowing you to switch to recently played
Screenshots

this is actually a spotify issue, if you disable our theme and shrink your window size you'll see the dropdown does not render


Fix for interactive-pipeline Transformer and Trainer components.

These commits address two issues brought up in #9 related to the interactive pipeline notebook. First, the Transformer component errors out because the zip_code field in the current upstream dataset is inferred as INT and module.preprocessing_fn attempts to process it as a string. Second, the Trainer component errors out because the upstream dataset has the consumer_disputed field already converted to {0,1} but download_dataset.update_csv attempts to do that again, resulting in nans that the trainer chokes on.
I took a best guess at patches for both. I'm open for suggestions.

I have closed the PR, since #12 removes the entire update function. Thank you @dylan-stark for the PR!


Automatic update of fontconfig

Can fontist install be configured to automatically update fontconfig when a new font is installed?
Some software like LibreOffice rely on fontconfig to resolve fonts.
See my answer here.

@raffaem thank you for the suggestion! I believe Fontist could trigger fontconfig on font installs.
To do so perhaps we need to implement:

Detect whether fontconfig is installed
Install Fontist configuration for fontconfig, so that fontconfig reads the Fontist font directory
Fontist can trigger fc-cache/fc-match after a font is installed to make it available in fontconfig

Does this match your expectations?

Yes, thanks :+1:

Thanks @raffaem for the confirmation. We'll ping you once there is any update!


Include the volume name in the container name to prevent duplicates

First of all, thanks for creating this easy tool!
This already was exactly my work flow, creating docker containers for just the services like ElasticSearch, Redis etc. This makes maintaining them a lot easier! :D
I'd like to create a separate Elastic search and Redis container for each project.
However, if they both use the same version there is a name conflict.
This could be solved by including the volume name in the container name like: TO--redis--volume-name--buster
What are your thoughts on this?
Thanks!
ERR  docker: Error response from daemon: Conflict. The container name "/TO--redis--buster" is already in use by container "0d0d690f64328b59d4a2b60f54cd99ee2254ba48f63db302b1738ca927347410". You have to remove (or rename) that container to be able to reuse that name.
See 'docker run --help'.

I think this is a great idea! I'm trying to decide whether it's a breaking change or not. I.. sort of think it isn't? So.. we may be able to add this in a dot release.

Thanks for your answer! :)
I see that not all services have a volume, like: MsSql, Memcached, MailHog.
This means the container name can't always include the volume in its name.
In these cases it would still be nice to optionally be able to provide a name to make the containers unique.
I don't think it's a breaking change because all containers starting with TO-- are listed an all commands are done with its ID.
Please let me know if you would like me to work on a PR.
(Just curious, doesn't MsSql need a volume as well?)

@dducro MsSql could benefit from a volume, but the official image has trouble mounting docker volumes for some reason. In order to still have the service available in Takeout, we needed to disable volumes for that service.
I have seen some tricks to make volumes work with MsSql, but for now it's not available. So you can bring up the container, but as soon as you destroy it, the data will be removed.
We are looking into the option to bring down a container without destroying it though, so that will make working with MsSql a little better.

The only way I can think of so far is to add an additional prompt to the setup that's basically the "nickname" or something, which would default to the volume name, and the nickname would always be appended to the base name (e.g. TO--mysql--5.7--nicknamehere)

That would be perfect! This way the user could have an instance per project if he so desires.
I also use the docker desktop app to list the containers and turn them on/off, to see the project name in the container name would be a great improvement! :)

@dducro OK, it's a plan!

👋  Hey! I decided to take a stab at this in #89

Thanks for opening this issue @dducro and the potential fix @ozziexsh. I'm looking to set up two Postgres databases, one for local development and one for running tests against. Currently getting this naming conflict error when trying to create my second Postgres db.
Workaround for me is to rename one of the containers. You can do this from the CLI:
$ docker rename TO--postgresql--13.0 my-database-name

closed per reason in #89


handleItemSelect prop doesn't get called in Android

Working fine in iOS but the function I pass into the handleItemSelect prop doesn't get evoked
handleSelectItem={(item, id) => this._handleSelectItem(item, id)}

This is because of the animations happening that the buttons will not be clickable in android . better to use  by rn-gesture-handler in the dropDown item component. That will fix it

Is that a feature in this node package? Or what do you mean by "rn-gesture-handler"?

Go into the package in node_modules and change the <Button component (import from 'react-native') in the dropdownItem.js file into a <TouchableOpacity ( import from 'react-native-gesture-handler')


Upgrade npm dependencies

Codecov Report

Merging #401 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #401      +/-   ##
==========================================
- Coverage   96.43%   96.42%   -0.01%
==========================================
  Files         421      421
  Lines        3368     3361       -7
  Branches      371      371
==========================================
- Hits         3248     3241       -7
  Misses         98       98
  Partials       22       22

Impacted Files
Coverage Δ

.../components/form/field/HiddenField/HiddenField.tsx
100% <100%> (ø)
:arrow_up:

src/components/form/finalForm/Field/Field.tsx
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5b5fb7e...30558ee. Read the comment docs.


Remove the import of redirect_stderr

They are not used. And redirect_stderr is introduced in python 3.5. It prevents execution on old python.

Hmm I don't quite understand AppVeyor error. Is there anything actually depending on redirect_err? My search didn't show anything...

We don't support Python < 3.6 anymore, but still, that import indeed seems unused and unneeded.

The symbol was kept there because the module contained a backport with that name. I don't remember why it was originally added, but it I think it's safer to keep it there just in case it may be used elsewhere.
And yes, we don't support < 3.6 any more.

These symbols aren't listed in __all__, though. (But I don't mind if we keep them.)

true, but the intention in keeping the symbols was to avoid unintended breakages on python versions that we do support.

in a few months, we can get rid of the py23 module altogether.


When I import a dataset which was previously deleted, I see the "Are you sure you want to import this dataset?" dialog box

Bug description
When I import a dataset which was previously deleted, I see the "Are you sure you want to import this dataset?" dialog box. This is confusing to researchers & reviewers since the search or list views don't show the previously deleted dataset.
How to reproduce:

Import a dataset (e.g. with DOI 10.5281/zenodo.3613927).
Delete the dataset from the overview  list at /dataset.
Import the dataset again with the same DOI.
Notice how the duplicate dataset notification pops up.

Expected behavior
I don't see a duplicate dataset notification for previously deleted datasets (tombstones).
Additional information
Deleted datasets remain in the elastic index with the status "STATUS_DELETED" flag. This is the result of following immutability as a first  principle in our snapshot strategy. This shouldn't be changed. It's okay for tombstones to remain in the search index.
suggested solutions
When checking for existing datashots, tombstones should be omitted from the duplicate dataset check.

@netsensei i'll add a filter status=public


Borders don't have own friction values.

Borders currently don't have their own coefficients of friction. During collision only the value of the object is considered.
When implementing two new sliders should be added under the  border Restitution slider for the friction coefficients.

also added a size option for the border.


Likely need help to use this crate.

I'm a bit confused on how to use this crate. I currently have this code but it doesn't work. I basically just took the esp_idf_sys template and added code that I think should work? It's pretty unclear to me where to find proper basic examples that just turn all neopixels red or somthing similiar.
use esp_idf_sys as _;
use log::*;
use smart_leds::{SmartLedsWrite, RGB8};
use ws2812_esp32_rmt_driver::Ws2812Esp32Rmt;

const NUM_LEDS: usize = 100;
const COLOR: (u8, u8, u8) = (32, 0, 0);
const GPIO_PIN: u32 = 18;

fn main() {
    esp_idf_sys::link_patches();
    esp_idf_svc::log::EspLogger::initialize_default();

    let mut ws2812 = match Ws2812Esp32Rmt::new(NUM_LEDS.try_into().unwrap(), GPIO_PIN) {
        Ok(ws2812) => ws2812,
        Err(error) => {
            info!("{error:?}");
            loop {}
        }
    };

    let data: [RGB8; NUM_LEDS] = [RGB8 {
        r: COLOR.0,
        g: COLOR.1,
        b: COLOR.2,
    }; NUM_LEDS];

    ws2812.write(data.iter().cloned()).unwrap();
}

This code errors with the following lines
E (453) rmt: rmt_set_gpio(523): RMT CHANNEL ERR
E (463) rmt: rmt_config(686): set gpio for RMT driver failed
I (463) test: Ws2812Esp32RmtDriverError(EspError(258))

The third line is the info macro invocation which just prints out the debug display of the error.

Looked at the examples and noticed that the first argument for Ws2812Esp32Rmt is the channel and not led count...


Issues with testing the classifier with testing dataset

Hi,
I followed the steps of classifying the training dataset using Minimum distance to mean, Tangent Space Logistic Regression, and CSP + logistic regression. However, I get errors when I want to test the model with the testing dataset(i.e. using the function score or predict)
Errors displayed are:
'MDM' object has no attribute 'covmeans_'
'TSclassifier' object has no attribute '_pipe'
'CSP' object has no attribute 'filters_'
Can someone help me with this?
Regards

A snippet of my code is below:
epochs_data_train = 1e6 * users_training_validation.get_data()
y_train= users_training_validation.events[:, -1]
epochs_data_test = 1e6 * users_testing.get_data()
y_test = users_testing.events[:, -1]

# compute covariance matrices
cov_data_train = Covariances(estimator="oas").transform(epochs_data_train)
cov_data_test = Covariances(estimator="oas").transform(epochs_data_test)

cv = KFold(n_splits=10, shuffle=True, random_state=42)

clf_mdm = MDM(metric=dict(mean='riemann', distance='riemann'))

# Use scikit-learn Pipeline with cross_val_score function
scores = cross_val_score(clf_mdm, cov_data_train, y_train, cv=cv, n_jobs=1)

# Printing the results
class_balance = np.mean(y_train == y_train[0])
class_balance = max(class_balance, 1. - class_balance)
print("MDM Classification accuracy: %f / Chance level: %f" % (np.mean(scores),
                                                              class_balance))

# Test with Minimum distance to mean
clf_mdm.score(cov_data_test, y_test)

I didn't fit the classifier

Hi @ibr2011
Thanks for taking the time to report your issue, even if you could solve it by yourself. Do not hesitate to open new issue if you get errors.


fix: override whereIn to work with FM

This will work for an independent "wherein", but if there are already existing wheres then the original where queries won't be applied to the wheres from the whereins which are being added, since they're being appended as an 'or'.
For example
Pet::where('flagged', true)->where('type', 'cat')->whereIn('fur_color', ['white', 'orange', 'black'])->get()
would make four find requests. The first would be 'flagged' and 'cat' and then there would be one additional find request per fur color. Instead, we should have three find requests with the flagged and type properties applied to each fur color.


Cross Azure samples and cross product samples like Eventgrid + functions, Storage + automation, Text analytics with Synapse, using metrics with storage etc.

Will revisit later if necessary


Revert PR 2993 for Opensearch Alert

We need to revert the change because there is an error when applying the change.
│ Error: elastic: Error 405 (Method Not Allowed)
│
│   with elasticsearch_opensearch_destination.cloud_platform_alerts,
│   on app-opensearch-alerts.tf line 1, in resource "elasticsearch_opensearch_destination" "cloud_platform_alerts":
│    1: resource "elasticsearch_opensearch_destination" "cloud_platform_alerts" {
│
╵

This maybe related to that destinations will be deprecated going forward in Opensearch from Opensearch Destinations Page.
Also we also need to use new resource block opensearch_channel_configuration for Opensearch and it involves the testing of new terraform opensearch provider.


Rotate the Screen

Hi,
I am wondering if there is a way to rotate the entire display "matrix" so it would be rotated 180 degrees.
I was able to do this with Python and Command line interactions with the OLED, but there doesn't seem to be an interaction offered. Everything else is working as expected (once I got items formated properly).

I'm also looking for the same problem. 5 years, still no solution.


styling added

Description
Aligned Save & toggle button, added shadows, hover effect, background colour and proper radius to other buttons like upload greyscale etc.
Checklist

[x] I am making a proper pull request, not spam.
[x] I've checked the issue list before deciding what to submit.

Related Issues or Pull Requests
#14
Add relevant screenshot or video (if any)

Remove transition hover from upload button instead added a simple hover which is working great

fixed the shadows of all Small buttons

@ZiaCodes Please Review my PR


Design a logo for website

We are seeking a designer to create a logo for our website.
Anyone interested?

hey, i know some designing i can try it using canva andd other resources

Yeah, you can try.  @Kallind
Share the photos of what u had done

hey i did make a logo but its not good i feel it can be done better ill try if i can

Could you please provide an update on your progress regarding the logo design, @Kallind?


Contacting attendees before / after a booking

Hi.  I often need to contact attendees before and/or after an appointment in Bookings.  I can't find a way to do this without manually copying and pasting all the email addresses from the calendar appointment.  Could you add how best to do this in the FAQ's page as a "Contact all attendees" button should be basic functionality.  Thanks.
[Enter feedback here]

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

ID: f7484dd4-5d94-dd6c-0dbe-551c852677c1
Version Independent ID: 257d60e2-9313-e08b-dccf-120cb4b30f5b
Content: Microsoft Bookings Frequently Asked Questions
Content Source: microsoft-365/bookings/bookings-faq.yml
Service: bookings
GitHub Login: @kwekuako
Microsoft Alias: kwekua

Thanks for replying Sri, I really appreciate it.  This seems like a massive gap in functionality so I've already added a feedback request: Contact attendees via email · Community (microsoft.com)https://feedbackportal.microsoft.com/feedback/idea/9393768f-2bf9-ec11-a81b-6045bd864d4f.
If you know anyone else who might like to upvote it then that would be appreciated!
Thanks again.
Oz Oscroft

From: Sriraman M S @.>
Sent: 01 July 2022 09:11
To: MicrosoftDocs/microsoft-365-docs @.>
Cc: OzmeisterO @.>; Mention @.>
Subject: Re: [MicrosoftDocs/microsoft-365-docs] Contacting attendees before / after a booking (Issue #9011)
@OzmeisterOhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOzmeisterO&data=05|01||af3b635420c34bf5c8f508da5b394cb4|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637922598920705154|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=YYDowoyEMyeZKxKl4UAFeNm5lEBeR%2Bk2YjYSOpVy9Co%3D&reserved=0 Thank you for your feedback. I tested and was not able to find another way to do it. I understand it gets difficult to track attendees when there are multiple bookings or attendees. I'd recommend you leave your feedback directly on our Bookings feedback portal so that the dev or product engineer can provide you with an update once this feature is available.
Here is the feedback portal link - https://feedbackportal.microsoft.com/feedback/forum/e9c7c7d1-011c-ec11-b6e7-0022481f8472https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffeedbackportal.microsoft.com%2Ffeedback%2Fforum%2Fe9c7c7d1-011c-ec11-b6e7-0022481f8472&data=05|01||af3b635420c34bf5c8f508da5b394cb4|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637922598920705154|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=pLjKz%2Fyw%2FNUlLeuiBjuGUcc5sZz%2FxX3WamyfM46UDjU%3D&reserved=0
Hope this helps!
Thanks
Sri
—
Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmicrosoft-365-docs%2Fissues%2F9011%23issuecomment-1172068013&data=05|01||af3b635420c34bf5c8f508da5b394cb4|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637922598920705154|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=52YqRN6I8VNrkBuTC0ebr6UZvldV9g2CSOXRik%2FSvGE%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMKNN6SX7CHDVTCB6PAW333VR2R27ANCNFSM5ZXBRYGQ&data=05|01||af3b635420c34bf5c8f508da5b394cb4|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637922598920705154|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=ldkYN9O7D6cKB8WVR5tjoyKHEZxbxP6cCYmWrSlbKc0%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>


pull request for e2e test at 11/27/2016 15:56:04

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Support dynamic enums for Case Status and Resolution

Is your feature request related to a problem? Please describe.
Case enums are currently hardcoded (as far as I can tell). When tracking different types of cases, the status and resolution may vary by the procedure path taken. For instance a Case created from an impossible travel scenario will differ in conclusion from the investigation into a supply chain incident (e.g. an account owner won't acknowledge it).
Describe the solution you'd like
It would be great if we can get these as configurable settings under the Case configuration of a project.
Describe alternatives you've considered
The alternative is to lock processes into the existing options or to compile a custom version of Dispatch containing all possible permutations of case type, status and resolution, which is an unfavorable overhead.
Additional context
N/A

I think this is a logical next step, we weren't sure what usage might look like but these should be relatively easy to add.

I think @whitdog47 will be taking this feature on.


Fix: No highlighted sidecar items when scrolling through long articles

Bit of a pet peeve issue here, but when scrolling through longer sections, the sidecar will sometimes lose focus on what article is currently active.
Screencast_20241230_102045.webm
This should keep at least something focused, which makes quickly scrolling through the docs less disorienting.
Screencast_20241230_102155.webm

Ty!


"Format" fields are no longer included into Excel when printing with "Microsoft Excel Document (Data only)" option

I use printing with "Microsoft Excel Document (Data only)" option to export test cases into Excel. Then I use that Excel as a data source to develop RDL reports in the Report Builder. Format columns are a must because their values are used to format other columns' values. Could you please add the "Format" fields back to that export option? That was a great help for me as a reports developer. Thanks!

Unfortunately, this repository is only for Business Central extensibility requests or code contributions towards the 1st party Business Central apps.
For suggestions to the Business Central product group, please create a BC Idea.
If you want to log a support case, please visit:
On premises - https://support.microsoft.com/en-us/supportforbusiness/productselection?sapId=93d37907-ad94-d591-22e9-593cfa09dd3f
Cloud – contact your partner, or if you are a partner open a support incident through Partner Center - https://partner.microsoft.com/en-us/pcv/dashboard/overview


[TODO] Add return types for functions

Description
Functions on project ocntroller do not have return  types. It should be refactored.
Expected Behavior
Function will return only expected type, or will throw
Assignees
@stbestichhh

Commit


Manual focus settings don't apply on startup or reboot

In the Webcam manual focus settings section, I showed how to add some values to start.sh to get them to apply when the webcam stream starts up:
sudo v4l2-ctl --set-ctrl=focus_auto=0
sudo v4l2-ctl --set-ctrl=focus_absolute=22
sudo v4l2-ctl --set-ctrl=exposure_auto=1
sudo v4l2-ctl --set-ctrl=exposure_absolute=180

The problem is it doesn't seem like these settings are applying after I reboot the Pi. So maybe I need to change the command, or figure out why the start.sh script isn't being called the way I thought it was...

This... is fixed now by running the commands using OctoPrint's built-in config (~/.octoprint/config.yaml); see https://github.com/geerlingguy/3d-printing?tab=readme-ov-file#webcam-manual-focus-and-exposure


How to localize the position of object by using tensorflow

The ILSVRC competition held by imagenet includes Object localization and Object detection and other tasks.
How did the convolutional neural network solve the localization problem?
I can only find tutorials on classification task.
I think it is proper to add an example of localization in tensorflow tutorial.

This question is better suited to stackoverflow since it is a usage question not a bug report.


TypeError                                 Traceback (most recent call last)
 in
----> 1 import zipline
~/miniconda3/lib/python3.9/site-packages/zipline/init.py in
19 # This is not a place to dump arbitrary classes/modules for convenience,
20 # it is a place to expose the public interfaces.
---> 21 from trading_calendars import get_calendar
22
23 from . import data
~/miniconda3/lib/python3.9/site-packages/trading_calendars/init.py in
14 # limitations under the License.
15
---> 16 from .trading_calendar import TradingCalendar
17 from .calendar_utils import (
18     clear_calendars,
~/miniconda3/lib/python3.9/site-packages/trading_calendars/trading_calendar.py in
31 import toolz
32
---> 33 from .calendar_helpers import (
34     NP_NAT,
35     compute_all_minutes,
~/miniconda3/lib/python3.9/site-packages/trading_calendars/calendar_helpers.py in
4 NANOSECONDS_PER_MINUTE = int(6e10)
5
----> 6 NP_NAT = np.array([pd.NaT], dtype=np.int64)[0]
7
8
TypeError: int() argument must be a string, a bytes-like object or a number, not 'NaTType'
Here is how you can reproduce this issue on your machine:
Reproduction Steps

create conda env
pip install zipline-reloaded
from jupyterlab import zipline
...

What steps have you taken to resolve this already?
...
Anything else?
...
Sincerely,
JCX

I can reproduce this error in Windows 10 and a clean Python 3.7 environment

Same problem on Ubuntu, Conda, Python 3.7

Well, as I can understand, the problem in https://github.com/quantopian/trading_calendars/blob/master/trading_calendars/calendar_helpers.py#L6
Numpy just can't cast NaT to int64, and that looks ok. If you patch your tradinc_calendar like that, it will work (in my case)
NP_NAT = np.array([pd.NaT])[0]

Plus this PR please https://github.com/quantopian/trading_calendars/pull/225
But maybe you will be faced with another problem:
ImportError: cannot import name 'gcd' from 'fractions' (/home/ms/miniconda3/envs/autotrade_env/lib/python3.9/fractions.py)
It's cause I use Python 3.9 and networkx too old. Update networkx to 2.5 and it will work.

For what it's worth, there's maintained fork here that, among other things, seems to fix that issue:
https://github.com/gerrymanoim/exchange_calendars

imposing a lower on pandas version <=1.2.5 should fix the error

Stefan, I think it's worth converting Zipline Reloaded to use @gerrymonoim 's exchange calendars.
(Note that Gerry was previous a Quantopian staffer, and now at Two Sigma)

@RichardDale
The issue is that exchange_calendars from gerrymanoim changed  the opening and closing times definitions (which zipline relies upon) from t+1min  to t. Someone would need to grab the baton there and look how hard it would be to convert zipline to to that change in opening/closing time definitions. I suspect the "easiest" would be to write some kind of wrapper to overwrite the calendar times, but maybe it would be more beneficial in the long term to change the logic there.

still there

A temporary workaround is to restrict to Pandas to v1.2.5 instead of v1.3+
I've documented a working environment here that we use as part of Norgate's Zipline integration showing the exact command lines used on a Conda environment on Windows:
https://pypi.org/project/zipline-norgatedata/

Temporarily addressed by https://github.com/stefan-jansen/zipline-reloaded/pull/47 that imposes pandas<1.3.0. We will work on the root cause and lift the pandas version constraint asap.


WIP: Add AzureStackHCI to WS2022

Docs Build status updates of commit 56e35cd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/azurestackhci/Clear-AzureStackHCIArcIntegration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Disable-AzureStackHCIArcIntegration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Enable-AzureStackHCIArcIntegration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Get-AzureStackHCI.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Get-AzureStackHCIArcIntegration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Get-AzureStackHCIBillingRecord.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Get-AzureStackHCIRegistrationCertificate.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Get-AzureStackHCISubscriptionStatus.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Initialize-AzureStackHCIArcIntegration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/New-AzureStackHCIRegistrationCertificate.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Remove-AzureStackHCIRegistration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Remove-AzureStackHCIRegistrationCertificate.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Set-AzureStackHCIRegistration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Set-AzureStackHCIRegistrationCertificate.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Sync-AzureStackHCI.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Update-AzureStackHCIRegistrationCertificate.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/azurestackhci.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit c8cfca1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/azurestackhci/Clear-AzureStackHCIArcIntegration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Disable-AzureStackHCIArcIntegration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Enable-AzureStackHCIArcIntegration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Get-AzureStackHCI.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Get-AzureStackHCIArcIntegration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Get-AzureStackHCIBillingRecord.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Get-AzureStackHCIRegistrationCertificate.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Get-AzureStackHCISubscriptionStatus.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Initialize-AzureStackHCIArcIntegration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/New-AzureStackHCIRegistrationCertificate.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Remove-AzureStackHCIRegistration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Remove-AzureStackHCIRegistrationCertificate.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Set-AzureStackHCIRegistration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Set-AzureStackHCIRegistrationCertificate.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Sync-AzureStackHCI.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Update-AzureStackHCIRegistrationCertificate.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/azurestackhci.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 5467e0e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/azurestackhci/Clear-AzureStackHCIArcIntegration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Disable-AzureStackHCIArcIntegration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Enable-AzureStackHCIArcIntegration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Get-AzureStackHCI.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Get-AzureStackHCIArcIntegration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Get-AzureStackHCIBillingRecord.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Get-AzureStackHCIRegistrationCertificate.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Get-AzureStackHCISubscriptionStatus.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Initialize-AzureStackHCIArcIntegration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/New-AzureStackHCIRegistrationCertificate.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Remove-AzureStackHCIRegistration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Remove-AzureStackHCIRegistrationCertificate.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Set-AzureStackHCIRegistration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Set-AzureStackHCIRegistrationCertificate.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Sync-AzureStackHCI.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Update-AzureStackHCIRegistrationCertificate.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/azurestackhci.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 4ccf5a1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2022-ps/azurestackhci/Clear-AzureStackHCIArcIntegration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Disable-AzureStackHCIArcIntegration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Enable-AzureStackHCIArcIntegration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Get-AzureStackHCI.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Get-AzureStackHCIArcIntegration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Get-AzureStackHCIBillingRecord.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Get-AzureStackHCIRegistrationCertificate.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Get-AzureStackHCISubscriptionStatus.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Initialize-AzureStackHCIArcIntegration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/New-AzureStackHCIRegistrationCertificate.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Remove-AzureStackHCIRegistration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Remove-AzureStackHCIRegistrationCertificate.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Set-AzureStackHCIRegistration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Set-AzureStackHCIRegistrationCertificate.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Sync-AzureStackHCI.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/Update-AzureStackHCIRegistrationCertificate.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/azurestackhci/azurestackhci.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Custom scalar not respected for array types

I have a custom scalar configured like this:
generateClientCodeConf {
  //…
  customScalars = [
    [
      graphQLTypeName: "Base64String",
      javaType: "java.lang.Byte[]",
      graphQLScalarTypeStaticField: "org.example.utils.Scalars.GraphQLBase64String"
    ]
  ]
}

However, when mutating an object with a Byte[] field, I get an exception:
graphql.schema.CoercingSerializeException: Expected type 'String' or 'Byte[]' but was 'Byte'
    at app//org.example.utils.Scalars$1.serialize(Scalars.java:31)
    at app//org.example.utils.Scalars$1.serialize(Scalars.java:23)
    at app//com.graphql_java_generator.client.request.InputParameter.getStringContentForGraphqlQuery(InputParameter.java:780)
    at app//com.graphql_java_generator.client.request.InputParameter.getStringContentForAListValue(InputParameter.java:839)
    at app//com.graphql_java_generator.client.request.InputParameter.getStringContentForGraphqlQuery(InputParameter.java:771)
    at app//com.graphql_java_generator.client.request.InputParameter.getStringContentForAnInputTypeValue(InputParameter.java:880)
    at app//com.graphql_java_generator.client.request.InputParameter.getStringContentForGraphqlQuery(InputParameter.java:791)
    at app//com.graphql_java_generator.client.request.InputParameter.getStringContentForGraphqlQuery(InputParameter.java:733)
    at app//com.graphql_java_generator.client.request.InputParameter.appendInputParametersToGraphQLRequests(InputParameter.java:936)
    at app//com.graphql_java_generator.client.request.QueryField.appendToGraphQLRequests(QueryField.java:346)
    at app//com.graphql_java_generator.client.request.QueryField.appendToGraphQLRequests(QueryField.java:376)
    at app//com.graphql_java_generator.client.request.AbstractGraphQLRequest.getPayload(AbstractGraphQLRequest.java:663)
    at app//com.graphql_java_generator.client.request.AbstractGraphQLRequest.buildRequestAsMap(AbstractGraphQLRequest.java:703)
    at app//com.graphql_java_generator.client.request.AbstractGraphQLRequest.buildRequestAsString(AbstractGraphQLRequest.java:686)
    at app//com.graphql_java_generator.client.RequestExecutionImpl.execute(RequestExecutionImpl.java:125)
    at app//org.example.client.util.MutationExecutor.updateObjectXWithBindValues(MutationExecutor.java:9739)
    at app//org.example.client.util.MutationExecutor.updateObjectX(MutationExecutor.java:9683)

It appears that this check:
https://github.com/graphql-java-generator/graphql-maven-plugin-project/blob/graphql-maven-plugin-project-1.18.9/graphql-java-client-runtime/src/main/java/com/graphql_java_generator/client/request/InputParameter.java#L768
is too early in the chain, and the custom scalar should take precedence. Naively changing the code like this:
diff --git a/graphql-java-client-runtime/src/main/java/com/graphql_java_generator/client/request/InputParameter.java b/graphql-java-client-runtime/src/main/java/com/graphql_java_generator/client/request/InputParameter.java
index f363bdb3c..2cc3346cd 100644
--- a/graphql-java-client-runtime/src/main/java/com/graphql_java_generator/client/request/InputParameter.java
+++ b/graphql-java-client-runtime/src/main/java/com/graphql_java_generator/client/request/InputParameter.java
@@ -765,6 +765,12 @@ public class InputParameter {
                } else if (writingGraphQLVariables && val.getClass().isEnum()) {
                        // When writing an enum value in the variables section, values should be between double quotes
                        return "\"" + val.toString() + "\"";
+               } else if (graphQLScalarTypeParam != null) {
+                       Object ret = graphQLScalarTypeParam.getCoercing().serialize(val);
+                       if (ret instanceof String) {
+                               return getStringValue((String) ret);
+                       } else
+                               return ret.toString();
                } else if (val.getClass().isArray()) {
                        // Doing just "Arrays.asList(val)" results in a StackOverflowError!
                        // We have to indicate that val is an array!
@@ -776,12 +782,6 @@ public class InputParameter {
                } else if (val instanceof RawGraphQLString) {
                        // The value is a part of the GraphQL request. Let's write it as is.
                        return ((RawGraphQLString) val).toString();
-               } else if (graphQLScalarTypeParam != null) {
-                       Object ret = graphQLScalarTypeParam.getCoercing().serialize(val);
-                       if (ret instanceof String) {
-                               return getStringValue((String) ret);
-                       } else
-                               return ret.toString();
                } else if (val instanceof String) {
                        // The value is a String. Let's limit it by double quotes
                        return getStringValue((String) val);

fixes my problem (but please note that graphQLScalarTypeParam will then always be null in the remainder of the if-then-else, so it probably needs a better fix).

Hello,
Thanks for the detailed analysis, and fix proposal.
If I undesrtand correctly, you're using the Base64String custom scalar as an input parameter of a query (or mutation), and the exception is thrown when you execute this query.
Is this correct ?
Etienne

Hello,
This one has lots of internal impacts. Now solved.
It will be available in the next release.
Would it be possible for you to test the correction before the release, by building the master branch ?
Etienne

Would it be possible for you to test the correction before the release, by building the master branch ?

I get test failures in graphql-java-client-runtime when trying to build latest master:
[ERROR] Failures:
[ERROR]   GraphQLReactiveWebSocketHandlerTest.testEncode:60 expected: <{"post":{"topicId":"22","input":{"authorId":"12","date":"2021-03-13","publiclyAvailable":true,"title":"a title","content":"some content"}},"aCustomScalar":[["2021-04-01","2021-04-02"],["2021-04-03","2021-04-04"]],"aDate":"2021-10-11","anEnum":"ADMIN","anIntParam":666}> but was: <{"post":{"topicId":"22","input":{"authorId":"12","date":"2021-03-13","publiclyAvailable":true,"title":"a title","content":"some content"}},"aCustomScalar":[[1617228000000,1617314400000],[1617400800000,1617487200000]],"aDate":1633903200000,"anEnum":"ADMIN","anIntParam":666}>
[INFO]
[ERROR] Tests run: 195, Failures: 1, Errors: 0, Skipped: 7

Grrr
It works for me. It's an issue with the date custom scalar serialization/deserialization. The date appear to not been
What OS and java version are you using ?
BTW: you've 195 unit tests executed and one failure, which means that the base64 unit test is Ok. It would be better to have the whole build to be ok to also execute the base 64 IT tests, that run latter. But it's a first passed test.

I'm building on Fedora 37, and get the same test failure on a clean build using either Java 17, 11, or 1.8 (to get that last one to build I needed to comment out the <release>8</release> on the main pom's maven-compiler-plugin, as JDK 1.8 doesn't recognise the --release 8 option).
I can do a mvn clean install -DskipTests of course, but I need a build of the graphql-gradle-plugin installed to my local Maven repo and using these artifacts; what would I need to do for that?

Ok,
I'll test with a Fedora 37. I'll need to setup an environment for that, so it will probably take some time.
About the 8, yes I know. It's written in the prerequisite described in the wiki. It's the better way I found to control the target release: if you know a better way, I'll be happy to use it... :)
And yes, the mvn clean install -DskipTests is not a good option: I'll test with the Fedora release and check that, before doing a new release.

I'm also using the packaged Maven, so:
$ mvn -v
Apache Maven 3.8.5 (Red Hat 3.8.5-3)

Thanks for taking the time to address this!

Hello,
I didn't install a Fedora box yet. But there may be an issue in the Date and DateTime custom scalar implementation provided by the plugin: it didn't force a Locale (as it seems useless for me here, but this remain IT... ;) ).
Is it possible for you to update your local git, and retry a build ?

As it happens I saw your commit and was already doing that. :wink:
Unfortunately, the error is still there:
[INFO] Running com.graphql_java_generator.client.GraphQLReactiveWebSocketHandlerTest
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.01 s <<< FAILURE! - in com.graphql_java_generator.client.GraphQLReactiveWebSocketHandlerTest
[ERROR] com.graphql_java_generator.client.GraphQLReactiveWebSocketHandlerTest.testEncode  Time elapsed: 0.007 s  <<< FAILURE!
org.opentest4j.AssertionFailedError: expected: <{"post":{"topicId":"22","input":{"authorId":"12","date":"2021-03-13","publiclyAvailable":true,"title":"a title","content":"some content"}},"aCustomScalar":[["2021-04-01","2021-04-02"],["2021-04-03","2021-04-04"]],"aDate":"2021-10-11","anEnum":"ADMIN","anIntParam":666}> but was: <{"post":{"topicId":"22","input":{"authorId":"12","date":"2021-03-13","publiclyAvailable":true,"title":"a title","content":"some content"}},"aCustomScalar":[[1617228000000,1617314400000],[1617400800000,1617487200000]],"aDate":1633903200000,"anEnum":"ADMIN","anIntParam":666}>
	at com.graphql_java_generator.client.GraphQLReactiveWebSocketHandlerTest.testEncode(GraphQLReactiveWebSocketHandlerTest.java:60)

Ok, thank you for your very quick test.
I'll try it with a fedora box.

I could repeat the building error.
So I still released the 1.18.10 version.

I can confirm that this issue is indeed solved with release 1.18.10; thanks @etienne-sf !


@AutoOpen does not open realm offline

How frequently does the bug occur?
All the time
Description
I have been trying to use the @AutoOpen property wrapper to open a realm with a flexible sync configuration during the app initialisation.
If the device is offline, the realm is blocked in .connecting state and is never opened.
It is working as intended if the device is online.
Stacktrace & log output
Configuration created
connecting
connecting
connecting

Can you reproduce the bug?
Yes, always
Reproduction Steps

If in memory, kill the app from the app switcher
Open the app

import SwiftUI
import RealmSwift

@main
struct MyApp: SwiftUI.App {
	var body: some Scene {

		WindowGroup {
			let app: RealmSwift.App? = App(id: Constants.APP_ID)
			if let app = app {
				SyncContentView()
					.environmentObject(app)
			}
		}
	}
}

struct SyncContentView: View {
	@EnvironmentObject var app: RealmSwift.App

	var body: some View {
		if let currentRealmUser = app.currentUser {
			let configuration = currentRealmUser.flexibleSyncConfiguration(initialSubscriptions: { subs in

				if subs.first(named: "report") == nil {
					print("Adding report subscription...")
					subs.append(QuerySubscription<Report>(name: "report") {
						$0.ownedBy == "ADMIN"
					})
				}
				// adding other subscriptions...
			})
			let _ = print("Configuration created")
			OpenSyncedRealmView()
				.environment(\.realmConfiguration, configuration)

		} else {
			AuthenticationView()
		}
	}
}

	struct OpenSyncedRealmView: View {
		@EnvironmentObject var app: RealmSwift.App

		@AutoOpen(appId: Constants.APP_ID) var autoOpen

		var body: some View {
			let user = app.currentUser
			let _ = print(autoOpen)

			switch autoOpen {
			case .open(let realm):
				let _ = print("--- REALM OPENED ---")
				let currentUser = realm.objects(User.self).where({try! $0._id == ObjectId(string: user!.id)}).first!
				let realmManager = RealmManager(app: app, realm: realm)
				TabView {
					LibraryView(currentUser: currentUser)
							.tabItem {
								Label("Library", systemImage: "books.vertical")
							}

					ChartsView()
							.tabItem {
								Label("Charts", systemImage: "chart.bar.xaxis")
							}
				}
				.environmentObject(realmManager)
				.environment(\.realm, realm)
			case .connecting:
				ProgressView("Logging in...")
			case .waitingForUser:
				ProgressView("Waiting for user to log in...")
			case .progress:
				ProgressView("Syncing your data...")
			case .error(let error):
				ErrorView(error: error)
			}
		}
}

Version
Realm 10.31.0
What SDK flavour are you using?
MongoDB Realm (i.e. Sync, auth, functions)
Are you using encryption?
No, not using encryption
Platform OS and version(s)
macOS 12.6
Build environment
Xcode version: 14.0
Dependency manager and version: ...

Hi @dianaafanador3 Are we sure this is fixed? I am using AutoOpen like so:
    @AutoOpen(
        appId: AtlasClient.shared.appId,
        timeout: 5000) var autoOpen

    @State var user: RealmSwift.User
    let onboardData: OnboardData?

    @Environment(\.realmConfiguration) private var config

    var body: some View {
        switch autoOpen {
        case .connecting:
            LoadingScreen()
        case .waitingForUser:
            LoadingScreen()
        case .open(let realm):
            RootContainer(shopper: {
                if realm.objects(Shopper.self).count == 0 {
                    try! realm.write {
                        let newShopper = Shopper()

//                        newShopper.firebaseUserId = FirebaseClient.shared.currentUserId()!
                        realm.add(newShopper)
                    }
                }
                return realm.objects(Shopper.self).first!
            }()).environment(\.realm, realm)

        case .progress(let progress):
            LoadingScreen()
        case .error(let error):
            ErrorScreenView()
                .onAppear {
                    ErrorLoggingService.shared.recordError(error)
                    print("Error", error)
                }
        }
    }
    ```

But when I go offline I get the error "Failed to connect to sync. Host not found (authoritative)"

I am also getting this error still did you ever find a work around??

Hi @dianaafanador3 Are we sure this is fixed? I am using AutoOpen like so:
    @AutoOpen(
        appId: AtlasClient.shared.appId,
        timeout: 5000) var autoOpen

    @State var user: RealmSwift.User
    let onboardData: OnboardData?

    @Environment(\.realmConfiguration) private var config

    var body: some View {
        switch autoOpen {
        case .connecting:
            LoadingScreen()
        case .waitingForUser:
            LoadingScreen()
        case .open(let realm):
            RootContainer(shopper: {
                if realm.objects(Shopper.self).count == 0 {
                    try! realm.write {
                        let newShopper = Shopper()

//                        newShopper.firebaseUserId = FirebaseClient.shared.currentUserId()!
                        realm.add(newShopper)
                    }
                }
                return realm.objects(Shopper.self).first!
            }()).environment(\.realm, realm)

        case .progress(let progress):
            LoadingScreen()
        case .error(let error):
            ErrorScreenView()
                .onAppear {
                    ErrorLoggingService.shared.recordError(error)
                    print("Error", error)
                }
        }
    }
    ```

But when I go offline I get the error "Failed to connect to sync. Host not found (authoritative)"


NIFI-13309 Lookup compatible bundles even if previous flow was empty

Summary
NIFI-13309
This change modifies the VersionedFlowSyncronizer to call mapCompatibleBundles even if the original flow was empty.
An additional null check was added to the proposed dataFlow instead to prevent exception during NiFi startup.
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[x] Apache NiFi Jira issue created

Pull Request Tracking

[x] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[x] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[x] Pull Request based on current revision of the main branch
[ ] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[x] Build completed using mvn clean install -P contrib-check

[x] JDK 21

UI Contributions

[ ] NiFi is modernizing its UI. Any contributions that update the current UI also need to be implemented in the new UI.

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

Thanks for submitting the change and incorporating the suggestions. +1 from my side


osm doesn't show in andorid 5.1

Hi, i'm developing an hybrid app with cordova using leafletjs and osm. The open street map is shown in android 4.1.1 but not in android 5 (it shows gray panel). How i can resolve it?

on Andorid 5.1 (CyanogenMod 12.1)

on Andorid 4.1.1

Hi, great to hear that you find Leaflet useful!
However, this issue tracker is used for reporting bugs and discussing new features. For questions on using Leaflet, please use gis.stackexchange.com or stackoverflow.


Make events generally much more common

About the PR

events are very non impactful rn which is bad. 25 mins as a max is simply far far far too much variance and too high of a max
Why / Balance

Technical details

Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

tweak: Random events should now occur much more frequently

3 to 10 minutes sounds freaky
I might be reading it wrong but survival has a 4 to 12 minute baseline (albeit with ramping)

woe be upon ye, every shift is survivial

woe be upon ye, every shift is survivial

imagine how bad survival is now

woe be upon ye, every shift is survivial

imagine how bad survival is now

Good you mean.


Remove preview suffix for Worker.Extensions.Tables package

Issue describing the changes in this PR
resolves #1118
Pull request checklist

[x] My changes do not require documentation changes

[ ] Otherwise: Documentation issue linked to PR

[ ] My changes should not be added to the release notes for the next release

[x] Otherwise: I've added my notes to release_notes.md

[x] My changes do not need to be backported to a previous version

[ ] Otherwise: Backport tracked by issue/PR #issue_or_pr

[ ] I have added all required tests (Unit tests, E2E tests)

/check-enforcer evaluate


Design the resource class

-Finished Resource Class and its style checking with PR Chore/resource class + init unit test for resource class #14 reviewed by Fiona Ruan


Minor version bump

Would you be amenable to releasing a version 5.0.2 to pick up the change in #174? It would help clean up some of our code.
Not sure if this is the correct repo to file this issue, but we're mostly concerned about usage in a Rails app, so ideally the bump would effect the official gem.

Done!


Replace tinyalsa API with audio_manager API

MediaPlayer doesn't use tinyalsa API directly

@Taejun-Kwon I moved them.


param: Param add a modified indicator to OSSL_PARAM.

Using the return_size field as a sentinel for change detection.

[x] documentation is added or updated
[x] tests are added or updated

I wonder if it would be better to not document how the modification detection works.

I'm wondering if you shouldn't mention what the value of OSSL_PARAM_UNMODIFIED is, and declare it "reserved".  If nothing else, those who worry that their particular huge buffer size might have the same value will feel informed.

I wonder if it would be better to not document how the modification detection works.

Why?

Why?

To give us some flexibility to change it without incurring breakage.  I can't guarantee that it will never need changing.  By not spelling it out, we can change it because the helper functions and macros hide the details.

Why?

To give us some flexibility to change it without incurring breakage. I can't guarantee that it will never need changing. By not spelling it out, we can change it because the helper functions and macros hide the details.

Would it be more future proof to have a separate flag variable to track the state of an OSSL_PARAM?

Would it be more future proof to have a separate flag variable to track the state of an OSSL_PARAM?

Yes, but it was shot down in the past.
Stealing a bit from the type field would be another possibility (although this would be far too invasive to consider now).
OSSL_PARAM is a public structure and we want to keep it plain and simple.  A version number and some flags wouldn't go astray but...

OSSL_PARAM is a public structure

... and that's exactly the reason to document the unmodified trick

Should this be also cleaning up where we already use the return_size in this fashion. There are quite a few of them.

We should clean them up.  I'd prefer to get this in and to then address the other uses.  I didn't release that such uses were widespread.

I didn't release that such uses were widespread.

They aren't yet.
: ; git grep 'return_size =.*not_set'
crypto/evp/p_lib.c:    params[0].return_size = not_set;
crypto/evp/p_lib.c:        if (params[0].return_size == not_set
crypto/evp/p_lib.c:    if (params[0].return_size == not_set)
crypto/evp/p_lib.c:    params[0].return_size = not_set;
crypto/evp/p_lib.c:    if (params[0].return_size == not_set)
crypto/evp/p_lib.c:    params[0].return_size = not_set;
crypto/evp/p_lib.c:    if (params[0].return_size == not_set)
crypto/evp/p_lib.c:    params[0].return_size = not_set;
crypto/evp/p_lib.c:    if (params[0].return_size == not_set)
crypto/evp/p_lib.c:    params[0].return_size = not_set;
crypto/evp/p_lib.c:    if (params[0].return_size == not_set)

Since the structure is public, and since the define's are public, and since openssl considers the contents of the header files, and not just the documentation of them, to be part of the API/ABI, might as well document what things currently do.

Merged to master, thanks.

since openssl considers the contents of the header files, and not just the documentation of them, to be part of the API/ABI

I thought I remembered the stance being a bit more subtle than that; do you have a pointer handy ("no" is a fine answer)?

Sorry, I don't.  Perhaps @t-j-h might reply here, since he was an advocate of that view.

Generally speaking, we consider the public headers to define the API. However, I would argue that some of those headers or APIs have become public by accident, so it's possible to justify that some of them should stop (see parts of the CONF API that was recently made unpublic).
OSSL_PARAM is intentionally a public structure, however, and very much part of the libcrypto<->provider interface, so it's safe to say that it should be considered part of the public API.

OSSL_PARAM is intentionally a public structure, however, and very much part of the libcrypto<->provider interface, so it's safe to say that it should be considered part of the public API.

It's not because it's used for the interface between libcrypto and
the providers, that it should also be used in the interface
between the application and the libcrypto.


make atlas annotations embedded instances of parcellationentityversion

This still needs to be resolved, @lzehl.

@UlrikeS91 thanks for the reminder. I'll have a look at it some time in the next days.

@UlrikeS91 I think this one is done. I'll just solve the conflicts and then it should be ready for merging


Fix shuffle_top_nams

We would not shuffle the NAMs if all found NAMs had the same score.
I found this a couple of weeks ago but noticed now I never sent this as a PR.

This doesn’t improve mapping accuracy, BTW.

Nice! Approved


Java Computer Vision to Detect Samples/Specimens

[x] Figure out global shutter camera 🟢
[x] Get example pictures of game elements with the shutter camera 🟢
[x] Write OpenCV script in Python 🟡
[x] Convert into Java 🔴

🟡 - Current Task in Progress
🔴 - Task is Not Started
🟢 - Task is Finished

Limelight introduced, work in progress


Project application commands

Closes: #64

Marking this as ready for review since I think it's a good stopping point for the first set of interactions.


Add .gitignore file

hey, its a simple html, css, js project... there is no room for adding gitignore file... if yes.. then it would just be blank file... please see to that...:)

No i means as many people use vs code and other software so some basic thing
So it adds .vscode and setting.jsonfile in repo
As for that would be fine cause if some one fork and open thenthat things will apply insted of his/her default settings
And many more stuff

oh my bad! can you assign it to me?

Yeah sure 🚀


[Feature Request] - "B.Tech Page" Branch Boxes Design Improvement

Is your feature request related to a problem ? Please describe. ✍
Enhancement

Describe breifly how would you implement the same.
The use of light color for boxes border rather than using a bright black which is taking user's whole focus on the border.

Additional context
Current Design

Expected Updated Design

Are you contributing for a program?
GSSoC2023
Code of Conduct

[X] I have read and agree to the CONTRIBUTING GUIDELINES of this project.

@anmode Please, Look into these...✌🏻

ok! You can go for it..

@iamRabia-N update me ?


Instant Search - Add Review Count slider

Feature Description
The number of reviews is helpful to indicate the popularity of a game and can indicate somewhat of how many owners it has, so having the ability to limit this can help fine tune our searches. Personally, I would use to it to find popular games. Top ingame player games list doesn't work as those are mostly multiplayer games and only work for a certain moment in time.

Bump. Would like to use this to find less played games


include vaccinations and virus variants in get_derivatives of vaccination model

Currently, vaccinations and virus variants are applied in secirv::Simulation::apply by modifying parameters or directly setting compartments. I think this is not ideal, as they could be included more elegantly in secirv::Model::get_derivatives.
In general we should limit the places in the code where compartments or parameters are modifed, otherwise the model becomes very hard to follow.
E.g., daily first vaccinations are the flow from compartment Susceptible to SusceptiblePartiallyImmune.

A base for this discussion could be what we had implemented in the parameter DynamicInfectionFromContact here:
https://github.com/DLR-SC/memilio/pull/233/files/cda84d1dd6db5bdc8a5b67354dcb65f443bc52d1#diff-ec5f30db7521beeba42314e5ef7c1e097edea1667dc21478f55ab0e6885a6cbbR152-R166


Add node 18 to the ci matrix

This PR adds node 18 to the ci testing matrix since it was released on 2022-04-19.

I wonder if we should update our eslint, prettier, and tsconfig repos to also allow the currently supported node versions.

I didn't realize that npm had started warning of engine incompatibility.  I think it's a good idea to bump those repos.  I'll make a PR for them.

All the warned repos have been updated to have node18 support and the dependency changes were merged in.  CI is no longer warning.


Ability to change keyswitch from the UI

Sforzando has it and it makes it easier to quickly test different articulations.

hello, in sfizz the red keys are used for that purpose, or do you mean something else?

exactly thank you


[website] don't line-wrap code

Wrapping code often makes it difficult to read. For example:

Cf. https://github.com/dart-lang/site-webdev/issues/643
cc @Sfshaza @filiph

How can one handle it on a small phone? We don't wrap in a browser.

How can one handle it on a small phone?

For site-www and -webdev we use scrolling. /cc @kwalrath

We don't wrap in a browser.

AFAICT we wrap in desktop browsers atm.

D'OH. Of course.

This issue was moved to flutter/website#1173


Seems like this conversation is resolved. I'm going to close and lock this thread.

"Seems like this conversation is resolved. I'm going to close and lock this thread.
Originally posted by @marstr in https://github.com/Azure/azure-notificationhubs-dotnet/issues/10#issuecomment-520015851"
No! Don't close it -- update the documentation! The documentation is currently a permutation of all versions you have ever produced, with absolutely no guidance on how to select a template when sending a message. Half of the APIs are deprecated and it absolutely is not obvious how to do it - I like most others were looking for where to provide the template name in SendTemplateNotificationAsync - and the fact you can provide it as a tag is completely arbitrary and should definitely be documented. Even better, it should be an argument to the method, as the API is currently a frankenstein of all the different experiments you've done with the API.
It is unacceptable that the only documentation on how this works ins in a closed GitHub ticket. Shouldn't it be #1 priority for you guys to update the documentation, instead of closing a ticket, when people have no information on how to use an essential feature?
Thanks.

Hello? Is this project maintained anymore or has it been killed off?

  We are making it a priority to fix our documentation in the coming months.

 We are making it a priority to fix our documentation in the coming months.

I appreciate it, thank you. Up to date documentation is vital so if at all possible please focus on it in the future. It doesn't matter how good the underlying technology is if it's not well documented as the barrier of entry becomes high and the trust goes down.
I appreciate your hard work on this!


Fix #1179 Add message_blocks property to Attachement class

This pull request resolves #1179
Category (place an x in each of the [ ])

[ ] bolt (Bolt for Java)
[ ] bolt-{sub modules} (Bolt for Java - optional modules)
[ ] slack-api-client (Slack API Clients)
[x] slack-api-model (Slack API Data Models)
[ ] slack-api-*-kotlin-extension (Kotlin Extensions for Slack API Clients)
[ ] slack-app-backend (The primitive layer of Bolt for Java)

Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you agree to those rules.

this change causes exception. message_blocks of type LayoutBlock cannot be read, because there is no type field in message_blocks.


UWP APPX Build fails for VS 2019 when VS 2017 is not installed

XRTK - Mixed Reality Toolkit Bug Report
Describe the bug

When a dev only has 2019 installed the build window fails
To Reproduce

Ensure only VS 2019 is installed
Build APPX for UWP
See error

Expected behavior

Devs should be able to build the appx with either 2017 or 2019 depending on what's availible.
Actual behavior

Can only build appx for VS 2017
Your Setup (please complete the following information)

Unity Version 2019.1.7f1
XRTK Version bea8cd15c072d8b398fafb533f3c7d1df243114e

Target Platform (please complete the following information)

UWP

Additional context

Might be related to how Unity creates the initial solution and project files. After being prompted to update the solution to a later version the appx build will succeed.  We might want to do something similar if only VS 2019 is found or a specific uwp sdk version is selected.

I also tested this with only installing the VS 2017 build tools only and I still get the following error:
C:\Dev\XRTK.Core\XRTK-Core\Builds\WSAPlayer\Il2CppOutputProject\Il2CppOutputProject.vcxproj(3786,3): error MSB4019: The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\Common7\IDE\VC\VCTargets\Microsoft.Cpp.Default.props" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.

More interesting still... I changed from x64 to arm and it built. Maybe it's my installation.

Odd, as my dev laptop I took to MRDevSummit ONLY has VS2019 and Unity 2019 installed and I had no issues.

Interesting 🤔


Q: Is this Audio CD dump correct?

Heya,
just got a new Audio CD and made a dump with DIC and a PLEXTOR PX-W4012A
Now I noticed these things in the DIC files:
_disc.txt:
========== Offset (Drive offset refers to http://www.accuraterip.com) ==========
	 Combined Offset(Byte)    392, (Samples)    98
	-   Drive Offset(Byte)    392, (Samples)    98
	----------------------------------------------
	       CD Offset(Byte)      0, (Samples)     0
	Overread sector: 1
	SubChannel Offset: 0

Overread sector? Is this a bad thing?
_subinfo.txt:
a message like this one is shown for each track (with different sector amounts):
P-channel pregap size (00:02:00) vs Q-channel pregap size (00:01:10) mismatch [65 sector(s)]

Just want to see, if anything could be wrong with the dump.
Logfiles:
DIC Logs.zip

Overread sector? Is this a bad thing?

No. To read 392 bytes, 1 sector is overreaded. Btw, if you search the CD Offset for audio cd, use /vrfy 1 (https://github.com/saramibreak/DiscImageCreator/wiki#dumping-guide-for-audio-cd)

_subinfo.txt:

Some discs don't match p vs q pregap size. It's no problem.

Thanks for the info. Case closed.


docs(VerticalNavigation): add slots examples

Added some examples of using slots, although these examples can also be implemented using ui prop
But at least we can now know which slots are available through the documentation

Thanks! 😊


Index from old article

Hi,
When I want to show old articles, it is easier to use index 0 for the oldest article.
I have to change the index number with the current setting.
Is it possible to change it or add an URL parameter?

do you find solution for you problem?


Instrument: Add OpNames to generated functions and variables

Add name annotations to the generated instrumentation code to
make it easier to understand. Example spirv-cross output:
vec4 _140;
if (0u < inst_bindless_direct_read_4(0u, 0u, 1u, uint(_19)))
{
    _140 = texture(textures[nonuniformEXT(_19)], inUV);
}
else
{
    inst_bindless_stream_write_4(50u, 1u, uint(_19), 0u);
    _140 = vec4(0.0);
}

@greg-lunarg would you prefer a different naming convention for the generated functions and global variables? Does naming introduce the possibility of conflicts in complex cases (possibly like https://github.com/KhronosGroup/SPIRV-Tools/issues/4892)?


Update deps

Updates clap, jsonrpsee, and applies cargo update afterwards.

@ljedrz does the short still work with these changes? I know clap is undergoing some major feature changes, but want to make sure these commands have not changed.

short without a right-hand value uses the first character (of the variant's name) and long  without one uses the full name, i.e.
#[clap(long = "addr", short = 'a')]
addr: SocketAddr,

is equivalent to:
#[clap(long, short)]
addr: SocketAddr,


How do I extend/customise ZSH after installing zimfw

I'm pretty happy with zimfw but I can't find some basic information on how to further customise ZSH after zimfw is installed: where do I put my personal exports or aliases, to avoid any update and upgrade conflicts? Would it be ~/.zshrc or ~/.zimrc? Any other place?

I put them into .zshrc and .pam_environment, e.g. https://github.com/lnicola/dotfiles/blob/master/.zshrc.

The files sourced by Zsh during the startup are documented here. The ~/.zimrc file is not sourced during startup. It should only be used to set the zimfw modules.


Put all the convert.py hooks into init.py?

I was trying to find out where the initial hooking of qutip-tensorflow and qutip happens and it turns out that its all done in convert.py when imported in the the init.py. I feel it would be a bit more verbose to see this happen inside the init as qutip-cupy does it. That makes it very clear to see and follow the magic of how qutip-tensorflow hooks on to the data layer.
@AGaliciaMartinez what do you think? I will follow this for qutip-jax.

That sounds good! I will update it to be consistent with the other packages. thanks for letting me know!


Roll engine eceb722b7111..a02a94e0182c (1 commits)

https://github.com/flutter/engine/compare/eceb722b7111...a02a94e0182c
git log eceb722b7111..a02a94e0182c --no-merges --oneline
a02a94e01 Roll src/third_party/skia 33f34556b5fc..a81c2be75adc (1 commits) (flutter/engine#6109)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

@rmistry @liyuqian : New roll has been created by https://autoroll.skia.org/r/flutter-engine-flutter-autoroll

Auto-roller completed checks. About to merge.


the Oxford Robotcar Dataset unavailable

Hi, thanks for your great work on multi modal fusion for place recognition.
However, the Oxford Robotcar Dataset is unavailable from 2022-11-08 and I'm a bit frustrated that there is no sign of re-opening the download. Could you please provide me with the centre RGB images by Google drive?
Thanks in advance.

Hi, I've uploaded pre-processed images from RobotCar dataset that are required to train and evaluate MinkLocMultimodal. In the below Google Drive link, you'll find compressed content of the folder containing downsampled RobotCar images from centre camera.
After downloading and unpacking, set image_path parameter in config_baseline_multimodal.txt to point to the folder with these images.
https://drive.google.com/file/d/1fnpBW57LVLZxOZU5-dSnuwfdwbfNyxGg/view?usp=sharing

Many thanks for your kind and warm help.


About polymer

Oh hi!
Is Polymer really necessary for this mod to work?
I tested the mod, but it seems to conflict with others with my modpack due to having Polymer embedded.

Dust will not function without Polymer, what is conflicting with Polymer?


Add runtime configuration of distributed database backend for RTS

Since a while back we build the RTS and have a compile time option (WITH_BACKEND) for the RTS to enable the use of the distributed database (DDB). The address and port to use is hard coded to localhost:32000.
We need to make it runtime configuration whether the RTS should use the distributed database backend or not as well as what host and port to connect to.
With this change, we can entirely remove the WITH_BACKEND flag and just have run time flags. It will greatly simplify experimentation with the database backend, in particular since the idea is that we will make binary releases of Acton available, so recompiling with an extra build flag would be a lot of work compared to downloading a readily available release.

Fixed through #46. Closing.


Pull Request: Merge develop into version v1.0.0

This pull request merges the develop branch into the version v1.0.0 branch, marking the official release of version 1.0.0.

Summary
This pull request merges the develop branch into the version v1.0.0 branch, marking the official release of version 1.0.0.
Changes

Completed migration from monolithic architecture to microservices architecture.
Implemented job-service, company-service, and review-service as standalone microservices.
Set up Eureka Server for dynamic service discovery and registration.
Added mappers for DTO and entity conversions using MapStruct.
Enhanced JobDTO to include reviews and updated job-service to handle this integration.
Updated the README file with project overview, setup instructions, and API documentation.

This merge signifies the release of version 1.0.0, featuring a fully functional microservices architecture for improved scalability and maintainability.


Ensure that all parsable arguments have corresponding coding keys

This PR add a validator to ensure each flag, option, argument of a ParsableCommand has the corresponding coding key.
For the following command:
struct Repeat: ParsableCommand {
    @Option(help: "The number of times to repeat 'phrase'.")
    var count: Int?

    @Flag(help: "Include a counter with each repetition.")
    var includeCounter: Bool

    @Argument(help: "The phrase to repeat.")
    var phrase: String

    enum CodingKeys: String, CodingKey {
        case includeCounter
        case phrase
        case count
    }

    func run() throws { /* ... */ }
}

Current behavior

If the command author forget to add the includeCounter to the CodingKeys. The command failed with fatal error:
Can't read a value from a parsable argument definition.

If the command author forget to add the count key and the user supplies a --count option. The command failed with message:
Error: Unknown option '--count'. Did you mean '--count'? 🤔

If the command author forget to add the phrase key. The command failed with message:
Error: Unexpected argument 'Hello'

Proposed behavior
None of the current behaviors seems appropriate. This PR proposed a validator to ensure all parsable arguments have corresponding coding keys. If the coding key of a parsable argument is missing the command parser reports fatal error: Can't find the coding key for a parsable argument.
Detail
It looks like there's no way to do the validation at compile time based on the current parser design. Create a runtime check is not straight forward too.
The ArgumentSet uses reflection to get the names of the arguments, however we can't get a list of CodingKeys so we can't see if the CodingKeys contains all of the arguments.
The solution proposed by this PR uses a special Decoder to get the type of CodingKey then try to create instances of CodingKey using given argument names. If CodingKey can be created from all the argument names we know that the command passes the validation.
Checklist

[ ] I've added at least one test that validates that my change is working, if appropriate
[x] I've followed the code style of the rest of the project
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary

@natecook1000 what do you think?

@YuAo This looks great! I'd like to pull it out into a separate validation step, since there are a variety of validations of the command declarations that we'll want to perform in debug mode but not in release. Could you move this into a separate method on ParsableArguments?
extension ParsableArguments {
    public static func _validate() throws { ... }
}

Also, the validation should throw on an error instead of trapping. Thanks!

@natecook1000 Thanks for the feedback!
I thought trapping would be better because this is an unrecoverable error and will cause unexpected behaviors. We don't want the program to continue when this happens.

we'll want to perform in debug mode but not in release.

If the validation is only performed in debug mode, then we are leaving the responsibility to the library users. It is not so important to trap, I agree that we should throw an error.
What do you think is the proper way to perform the validation only in debug mode? #if DEBUG or  assert({ do { try type._validate(); return true } catch { return false }}()) or anything better?
I prefer
#if DEBUG
do {
  try type._validate()
} catch {
  assertionFailure("\(error)")
}
#endif

public static func _validate() throws { ... }

Do we need making this public? There seems to be no need of running the check outside the library.

About other validations, did you mean this one: https://github.com/apple/swift-argument-parser/blob/9e77589d8532789635dc06e9ffce0280e2ca83d1/Sources/ArgumentParser/Parsing/ArgumentSet.swift#L44-L48
Then we can do something like this?
extension ParsableArguments {
  static func _validate() throws {
    // Use ArgumentSet(self).hasValidArguments or move the whole logic here.
    if !ArgumentSet(self).hasPositionalFollowingRepeated {
      throw Error.hasPositionalFollowingRepeated
    }
    try ParsableArgumentsCodingKeyValidator.validate(self)
  }
}

@natecook1000 Any thoughts?

Thanks for the feedback @natecook1000 !
I left a comment about the design of the validation layer. And added my propose
2316411.
I did not add any existing validations here, I think that would be a little off the topic and should be in a separate PR or something.
Let me know what do you think!

LGTM, @YuAo! I'll merge this now; would be great to add some more validators, as well. I think we may want to tweak the behavior once we have multiple validations happening, since it would be nice to see all the failed validations, rather than just the first one that doesn't pass.


WIP: Add duo pack (2FA)

Duo
Status

new pack, Work in progress

Description
A pack for to place 2FA authentication using the duo service (https://duo.com/) into workflows to add authentication / approval.
Checklist (tick everything that applies)

[X] Metadata: pack.yaml, icon, structure (required for new packs)
[X] Version bump (required for changed packs)
[ ] Code linting (required, can be done after the PR checks)
[ ] Tests (not required but really recommended)

This is mostly complete, just need to review the duo.auth action to ensure all the non-default options are covered.

Great, thanks.
Will have a look shortly.

The auth side of things is basically covered, the approach for handling output to the user when the action user is denied access by Duo needs to be consider further.
Options:

have action succeed on allow & deny and expect the workflow to parse the response to know if the auth was successful.
Only succeed if auth is allowed and return data and print message + raise an exception when auth is denied.

Personally I think the failure of the action on deny would be easier to understand instead having to put the following into the Mistral workflow:
on-successs:
   - run_action: <% $.status = "allow" %>
   - no_auth: <% $.status = "deny" %>

[The above is hidden in a comment on an out dated diff]

Awesome, I'll try with my Yubikey some time later.

@emedvedev Sorry, all my testing has been with factor set to auto so far, which translates to push or phone. Totally lacking the code in auth_auth.py to handle the other factors or pass in the passcode so far.
Before it gets to the merging stage I'll need to make that function, but there would need to be a action to pick up the passcode from another location and pass it to the duo.auth_auth action.

@emedvedev I've made it handle the different factors correctly now. it's worked for me with a passcode from the app so a Yubikey shoujld be fine now.

Latest commit has addressed the lack of lib use by @tonybaloney, so if this passes CI checks I think we are good to merge.

Thanks!
I added a couple of more comments.

Thanks to everyone for the comments and feedback, the pack covers the 3 useful actions for use of Duo within ST2. So I think we are good to merge, at a later date I expect I'll be able to start covering the admin API too.

Merged, thanks!


It only shows skiing now???

Oh,
if cavemaps=true, this sets a default filter: Caving
else it sets default filter: Skiing
...
and both override any selection in activity checkboxes.
The default filter and activity filter functionality needs an overhaul as well as related variable names.

Activity checkboxes are no longer shown, if cavemaps:true,
but the overhaul is still necessary.

Filtering is now (after fixing bug 344) bug free and less confusing.
Closing this issue.