[BUG] Volumes are not cleaned up when VM provisioning fails

Describe the bug
When creating a RKE2 cluster with Harvester driver and for some reason (e.g. an invalid config) the VM provisioning fails (and is then automatically retried by the provisioner all over again) there will be eventually hundreds of volumes on Harvester occupying all storage space.
Volumes should be cleaned up if a VM was not successfully provisioned.

seems to be a known issue fixed by node driver v0.3.1 at the https://github.com/rancher/rancher/pull/34765, can u possibly check what is the node driver version have been used?

We're using node driver v0.3.0. Unexpected side effect of this, is that it exhausted storage on the integrated longhorn and prevented new pvc's to fail. And this doesn't result in an error because of this issue: https://github.com/harvester/harvester/issues/1242

v0.3.0 no pvc clean up logic.
v0.3.1 fix pvc clean up but still has some timing issue, harvester/docker-machine-driver-harvester#26 will fix it.
need v0.3.2

I don't know if it's deliberate, but when deleting the volumes in Harvester, they're still lingering in Longhorn. It also still shows that the pv's are attached, but that bogus, since they weren't attached in Harvester and the vm's were already removed hours ago.

since they weren't attached in Harvester and the vm's were already removed hours ago.

can u please help upload a support bundle file so that we can dig into the error logs properly, thanks

Gathering logs doesn't work. It's stuk at 0%. I'll give it some time.

@alexdepalex v0.3.2  released
URL: https://releases.rancher.com/harvester-node-driver/v0.3.2/docker-machine-driver-harvester-amd64.tar.gz
Checksum: f113d826b8bee79abf60f1026b4076befdf735c6675889240c75da6b30f09971

Verified using the Rancher v2.6-head and Harvester node driver with v0.3.2:

spin up a guest k8s cluster with total of 3 nodes using the RKE2 node driver (e.g 1 control plane + 2worker)
check the VM and volumes that exist on the Harvester cluster

delete 2 worker nodes and make sure the volumes are gone

close as verified per https://github.com/harvester/harvester/issues/1246#issuecomment-927234690 .


Service fasthue.set_update_interval missing

I've installed fasthue using HACS as described in the README.MD. When creating the automation using the automation example the service fasthue.set_update_interval is not known within Home Assistant. Also when calling this service via Developer Tools->Services, a warning is shown that the service cannot be found.
I'm running Hass.io on a raspberry pi 4. System info is as follows:
rch | armv7l
chassis | embedded
dev | false
docker | true
docker_version | 19.03.12
hassio | true
host_os | HassOS 4.16
installation_type | Home Assistant OS
os_name | Linux
os_version | 4.19.127-v7l
python_version | 3.8.6
supervisor | 2020.11.0
timezone | Europe/Amsterdam
version | 0.117.6
virtualenv | false
My log only shows the following:
2020-11-14 03:08:19 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for fasthue which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
Please let me know if you need more information.

I had the same problem and probably we missed the same thing: After installing the integration via HACS Store and updating your configuration you also have to add that integration in the GUI. So you have log in to your Home Assistant, go to Settings, click on Integration and then click on the plus icon to add another integration. In the search field, type "hue fast" and you will see the integration to add. Add it and after that the service will be available. It fixed the problem for me :-).

It doesn't appear under Configuration>Integrations. Hit the + button and it's not there. Installed from HACS and appears under HACS>Integrations but that's it. Can't find an answer as to why or what file to check.

Thanks! That did the trick. I was new to HACS and thought that adding fasthue to HACS via HACS->Integrations was enough to get it working. But you also need to add fasthue via Configuration->Integrations .
I've modified the README.MD so that this knowlegde is known for all mankind.

Hi, just jumping in on this. I have installed it on HACS, restarted HA but when I go to search for it in the Integrations as per the previous response it is only coming up with the official Hue integration. I totally can't work out where I am going wrong with this so if someone was able to give me a hint it would be greatly appreciated

Hi, just jumping in on this. I have installed it on HACS, restarted HA but when I go to search for it in the Integrations as per the previous response it is only coming up with the official Hue integration. I totally can't work out where I am going wrong with this so if someone was able to give me a hint it would be greatly appreciated

Hi, just jumping in on this. I have installed it on HACS, restarted HA but when I go to search for it in the Integrations as per the previous response it is only coming up with the official Hue integration. I totally can't work out where I am going wrong with this so if someone was able to give me a hint it would be greatly appreciated

I have the same problem. Have no Idea what to change. Any hints or tipps are much appreciate.

Hi, just jumping in on this. I have installed it on HACS, restarted HA but when I go to search for it in the Integrations as per the previous response it is only coming up with the official Hue integration. I totally can't work out where I am going wrong with this so if someone was able to give me a hint it would be greatly appreciated

I have the same problem. Have no Idea what to change. Any hints or tipps are much appreciate.


Autograph error in LSTMCell when using dropout

System information

Have I written custom code: no
OS Platform and Distribution: Manjaro linux testing
TensorFlow installed from: pip binary
TensorFlow version: v2.0.0-rc2-26-g64c3d38 2.0.0
Python version: 3.7.4
CUDA/cuDNN version: N/A
GPU model and memory: N/A

Describe the current behavior
TensorFlow returns an error when decorating functions calling LSTMCell.call with @tf.function if dropout is non-zero (most common scenario).
TypeError: An op outside of the function building code is being passed
a "Graph" tensor. It is possible to have Graph tensors
leak out of the function building context by including a
tf.init_scope in your function building code.
For example, the following function will fail:
  @tf.function
  def has_init_scope():
    my_constant = tf.constant(1.)
    with tf.init_scope():
      added = my_constant * 2
The graph tensor has name: lstm_cell_1/ones_like:0

Describe the expected behavior
Compile the LSTMCell code correctly
Code to reproduce the issue
import tensorflow as tf

good_cell = tf.keras.layers.LSTMCell(units=2, dropout=0.0, implementation=1)
bad_cell = tf.keras.layers.LSTMCell(units=2, dropout=0.1, implementation=1)
inputs = tf.ones((1, 2))

state = good_cell.get_initial_state(inputs)

@tf.function
def no_dropout():
    output = good_cell(inputs, state)
    return output

@tf.function
def dropout():
    output = bad_cell(inputs, state)
    return output

print('='*50)
print(no_dropout())
print('='*50)
print(dropout())

Other info / logs
I did a quick investigation and found out that setting self._dropout_mask = None at the top of the call method makes the code work again. This forces the reset of the cached dropout mask used at the previous/first call of LSTMCell.

Issue replicating for both  TF 2.0 and nightly version.Kindly find the gist of colab.Thanks!

So the story is bit complicated.
If you debug the bad cell call with debugger, you will see the the bad_cell.call() is invoked twice. This means the second time when its invoked, its using the cached dropout mask created in the second trace.
To walkaround this issue, you can update your code as below. This is mimic what a normal cell will behave to process the inputs 10 times. The LSTM/RNN layer is resetting mask for every batch. User will have to do the same if they want to direct play with the cell.
@tf.function
def dropout(inputs):
  time_step = 10
  bad_cell.reset_dropout_mask()
  bad_cell.reset_recurrent_dropout_mask()
  state = bad_cell.get_initial_state(inputs)
  for i in range(time_step):
    inputs, state = bad_cell(inputs, state)
  return inputs, state

Hi @qlzh727
Just wanted to thank you for your great response. This is an interesting behaviour of tf.function that I was not aware of, so I learnt something new :)

This means the second time when its invoked, its using the cached dropout mask created in the second trace.

Would you be able to help me with a high-level technical explanation ? I don't fully understand this yet, although it seems related to the specific implementation of tf.function.

Ah sorry, I made a typo in the original message:

This means the second time when its invoked, its using the cached dropout mask created in the FIRST trace.

So, in high level, tf.function will convert a python function into a tf graph, which will be used to execution. The conversion process is called "trace". During tracing, tf.function will check if there is any variable gets created. If that is the case, tf.function will trace the second time and make sure no other variable is created, as a verification. When the verification failed, it will raise an error.
In your case, the function body will create following items in the first trace:

cached masks
variables for bad_cell when it is called with inputs. The build() function is first invoked when cell is not build.

Since tf.function detect the variable creation, it will try to trace the second time. During the second trace, the code will try to use the cached mask in a different graph (created in the first trace). Since it can't access those tensors across the graph, it raises an error to you.
As a verification, you can try build your cell first outside the tf.function for your existing code, and it should make it work too.

import tensorflow as tf

good_cell = tf.keras.layers.LSTMCell(units=2, dropout=0.0, implementation=1)
bad_cell = tf.keras.layers.LSTMCell(units=2, dropout=0.1, implementation=1)
inputs = tf.ones((1, 2))
good_cell.build(inputs.shape)
bad_cell.build(inputs.shape)

state = good_cell.get_initial_state(inputs)

@tf.function
def no_dropout():
  output = good_cell(inputs, state)
  return output

@tf.function
def dropout():
  output = bad_cell(inputs, state)
  return output

print('='*50)
print(no_dropout())
print('='*50)
print(dropout())

So, is there any roadmap for this?
Or, all we got is a workaround.


Regarding your notice

Hi,
you recently started recommending "gulp-htmlmin" and a custom gulpfile.js for minifying Laravel's compiled views, but it's not working well...
[21:44:22] Starting 'compress'...

events.js:85
	  throw er; // Unhandled 'error' event
			^
Error: Parse Error: <li<?php echo Request::is("ucp") || Request::is("/") ? ' class="active"' : ''; ?>>

I just wanted to tell you and other people that htmlmin is not always a solution, at least not in my case where I have Blade tags inside the HTML, like
<li{{ Request::is("/") ? ' class="active"' : ""}}>

I'm disappointed. Minification really doesn't work with php into html attributes

Hello,
It isn't a suitable solution in most of the cases, when you work in your project and later you upload it to a git repository, the storage folder isn't uploaded, and usually you run the javascript task on the deployment process, not later to visit your page to generate the cache views.
It will be a bad practice to upload the content of your storage folder, and also can happen that not all the view of your site are cached, or maybe the cache get updated with a new file.

@xavadu I have a command I wrote that recompiles all the blade templates without having to visit/load the page. It uses Blade::compile($file); and you can just write a loop that passes in all your templates files (File::allFiles(base_path().'/resources/views/')).
IMO, the Gulp task is a much better approach than using the PHP package. I've been using it for the past 6 months or so.

What about first comment of @dhardtke? I have a lot of parse errors too so anybody have a solution?


Procedural request

There are different ways to address feedback provided in the course of handling merge request. One is to push incremental changes, another is to maintain single [or same amount of] commit[s] throughout lifetime of merge request by force-pushing. Maintaining single [or same amount of] commit[s] past point of first approval makes reviewer's life harder than necessary. Well, formally speaking it makes life harder even prior first approval. Because maintaining single commit leaves no easy way for reviewer to "see" that there were no other changes besides those discussed. But approval is a check-point where reviewer has to make an overall assessment in either case, so maintaining single commit prior first approval might be considered acceptable. "Might" in previous sentence refers to the fact that life is compromise, and just formulated suggestion is not universal. In this case compromise is mostly about changes' complexity and size. I mean for big enough changes it might be inappropriate to maintain single commit at any step. [And reverse it true, from small, trivial changes it might be perfectly appropriate to maintain single commit all along.]
To summarize. Suggestion is to ask contributors ~is~ to abstain from maintaining single [or same amount of] commit[s] at least past first approval, ~but~ and consider incremental changes even prior that point. This doesn't preclude possibility that contributor can be asked to squash changes. On the other hand even though it's not explicitly proclaimed, the project reserves some freedom of editorial right to squash commit upon commit to repository. For this reason commits tagged with say "[to be squashed]" should be welcomed.

I would further like to suggest that squashing all commits into one big upon final merge should be frowned upon.  The '[to be squashed]' commits should, of course, be squashed with the commit they refer to, but otherwise, squashing should at least be done with care.  The exception is, of course, if the overall change is small.
For example, I frown upon putting source style changes and other more substantial changes into a single commit in a PR, and I think they should be separate in the final merge as well.  Otherwise, looking back at history becomes just as hellish as a PR that holds everything in one commit.

For example, I frown upon putting source style changes and other more substantial changes into a single commit in a PR, and I think they should be separate in the final merge as well.

One probably can't disagree as long as we are talking about styling of existing code, existing at the moment of request(*). But I'd argue that styling fixes to code introduced in given request are better squashed. But let's not forget that suggestion is rather about specific point in the review process. I for one see no reason to be rigid about what happens prior that point, reviewer is free to ask for whatever action that is deemed appropriate, to split or squash, or insist on incremental squashables. It's rather about what happens past the point in question.
(*) At the same time if styling modification is just one and couple of lines away, it's probably ok.

I generally agree with @dot-asm 's sentiment here in terms of supporting the reviewer.  However, things become awkward when a pull request remains around long enough that merge conflicts with the target branch develop -- in such cases, the CI systems refuse to even attempt to build the pull request when changes are made.  Or do we want people to merge master into their pull request to resolve the conflicts and the committer to rebase prior to actually pushing to the main repo?

Sounds reasonable.

I also try to use a good commit message and sometimes getting smarter
after the fist review loop...

Formally speaking one can can probably take it one step further and even argue that squashing (again, past point of first review) is actually reviewers' responsibility. However, it doesn't actually mean that reviewer has to do the actual squashing, one can still turn to the contributor. But then in majority of such cases it would be more than appropriate for reviewer to pull a local copy prior asking contributor to do the squashing, so that outcome can be double-checked (as suggested by @kaduk in #3992). As failure to do so would formally require reviewer to restart review from scratch. But one way or another it's probably appropriate to say that squashing reviewers' responsibility and consequently choice of actual method [which automatically would mean that contributor is not free to take the initiative to squash].

When I compare the review process here with the review process for GCC patches,
there are some differences.
For instance every GCC patch is first prepared and sent to the gcc-patches mailing list.
It is always sent together with the proposed ChangeLog entry.
The reviewer either approves or requests changes on the patch itself or the ChangeLog entry.
Then the author updates his patch and sends it again to the gcc-patches ML.
In effect it is possible to find every version of each patch together with the review comments
and compare what was checked in to what was finally approved.
OTOH when I have a closed PR and want to compare the approved version with the
finally checked in version, all I can see is the review comments, because once the author
removes the branch on his repository, all history is gone.  And the author has less control
over the ChangeLog entry, because after the squashing the committer creates an completely
new ChangeLog entry out of the different commits.

Well, github is not really a review system, and my suggestion is admittedly just an attempt to make best of situation.

Hmm, yes, interesting, usually each commit, is recoded in the git reflog, and
the reflog gets garbage collected after 90 days, but I see squashed commits
much older than that. So It looks like github does not garbage collect unreachable
commits.  I wonder if we can rely on this "feature", and what happens if the author's
github account is deleted.  Why is the "View Changes" not working when the commit
is still in the github tree?

git reflog

Isn't reflog a local thing? I mean let's say you look at merge request page for first time and want to double-check outcome of squash operation. What do you pull to recover pre-squash hash? There is no reflog that can help you...

Yes, reflog is a local thing.
The only ways I know of to get a commit hash for subsequent examination is if someone made an inline comment on that commit, or maybe if github had generated an email when a new commit was added to the PR (which isn't helpful in the general case).  And I don't understand how github decides when/whether to send emails for new commits on pull requests...

This is the info I just received from github support:

Hey Bernd,
We normally wouldn't garbage collect a repository unless its requested by the repository owners.
This means that commits may hang around but we cannot guarantee that they'll always be there.
Any commit thats referenced in another branch or fork will remain though. Even if you delete it from one branch it will still be accessible via any other ref it's still a part of.
Cheers
Stacey
Hi,

could you chime in on openssl Issue #3963 ?
It looks like that reviewed changes are often available even after a force
push or author deleting the branch.
Just the "View Changes" button does not work, but it turns out
that old commits are often available quite long after they are usually
garbage collected.
I wonder if we can rely on that or if the commits will eventually be
deleted?

This sounds that mentioning pre-squash commit in conversation (so that there is an URL) is not guaranteed to work. It's likely to work, but not guaranteed, and hence should not be relied upon. So that explicit pre-squash pull would be preferred option? Anyway, all this is relevant only if we actually agree on the premise, namely that squashing [specifically past point of first approval] is reviewers' responsibility (and not contributor's initiative). [Once again, "responsibility" doesn't necessarily mean that reviewer is obliged to do the squashing, only to ensure that outcome is consistent, and doing it yourself is simply one way to achieve the goal.]
There also was question about how to handle re-bases. In the context of this discussion more specifically what if there is approved request, but which has conflicts, and question is if commiter is free to resolve conflicts upon merge to main repository. I'd be inclined to say that this is error-prone procedure that might be inappropriate for this project. Or in other words I for one would argue in favour of handling re-base exclusively within merge request irregardless its approval status. So that re-base would always be contributor's responsibility. I would even take it one step further and say that re-base effectively voids [all] approval[s]. As compromise corner case, one can probably argue that if re-base outcome is a squashable that involves for example some ordinals re-numbering[?], then it doesn't have to void the approval. But I have feeling that there already is kind of implicit consensus at least on the part that re-bases are to be handled at review time and never at merge time, i.e. merge to main repo has to be conflict-free.

Another procedural request. I'd like to suggest to make it request originators' responsibility to explicitly comment on red-crosses from CI. Effectively it means that request would be less likely to be reviewed if there is red cross from either CI and no note from contributor.


updates api-version reference

fixes MicrosoftDocs/azure-docs#5486

@mike-urnun-msft : Thanks for your contribution to the Azure documentation! The author, @vladvino, has been notified to review your proposed change.

Hi @steved0x  - Could you take a look at this PR request when you have a chance?
Thanks,
Mike

#sign-off

@mike-urnun-msft: I'm sorry - only the author of this article, @vladvino, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


Checking for CRON_BUILD

Is the purpose of checking for CRON_BUILD on line 36 of the circle.yml to prevent the build from happening prematurely? Can this check happen sooner to prevent the setup from happening at all?

Closing this out as we are now using native cron on CircleCI 2.0


All generatorDims must be equal to embeddingDim?

Hello,
Because of the architecture of the generator (shortcut connections), I think that all the hidden layers must have the same size of the input, right?
Thank you.

Yes, that is correct.
But now that I think of it, I could have tried not using the shortcut connection in the first layer (between the gaussian noise and the first hidden layer of the generator).
Then --noise_size and --generator_size[0] wouldn't have to match.
But for the current implementation, they need to match.
Thanks,
Ed


When setting an X11 icon fails, try halving the size

When setting an icon that is too large previously Godot would die with a
X Error of failed request:  BadLength error. To avoid this we install an
error handler right before we set an icon. If the error handler triggers
we halve the icon size until it works or until we've reached a 0 size on
either width or height.
We print a warning when this happens to alert developers.
This fixes #19716

Thanks!

Now that Godot 3.1 has been released, we only plan to cherry-pick critical bug fixes to the 3.0 branch, unless there is very strong support in favor of a specific non-critical issue. Removing cherrypick label for 3.0.


Channels with no new activity get marked as unread

Hello,
Over couple of days, I've noticed that from time to time, Riot will mark bunch of Discord channels as unread (name of the channel gets bold and channel jumps to the top of the list), despite the fact that there is no activity in this channel.
I think it happens when this log is printed into console, but I'm not sure (I don't know exact time when it happens since I check chat client periodically):
Apr-1 11:30:40.848 [DiscordPuppet:DiscordEventHandler] info: Received new message!

What could I do to diagnose this further?

That is a riot but, not an mx-puppet-discord bug. Soru believes there to be an open issue for that somewhere
It happens when there haven't been any m.room.message events in quite some time.

I don't think this is Riot issue or it is at least strongly related to Discord puppet.
For me it only happens with Discord channels and it always happens in bursts (bunch of Discord channels become unread).

It also happens in non-bridged channels like synapse announcements and riot announcements.
The key to this bug is to have a lot of other events (like m.room.member) which are not message events and then eventually you'll get it in a room.

What would be the best way to see the list of events that caused this? Are they in the database

just have tons of member events or thelike without a message events, and you'll get it
Am 1. April 2020 15:14:07 MESZ schrieb "Matej Drobnič"<EMAIL_ADDRESS>
What would be the best way to see the list of events that caused this?
Are they in the database
--
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub:
https://github.com/matrix-discord/mx-puppet-discord/issues/65#issuecomment-607241323

Riot-Web issue https://github.com/vector-im/riot-web/issues/10954 and the related one posted there

Thanks for the links.

I think I might have found a workaround for this. I added following to the config file:
presence:
  disableStatusState: true

From what I understand, this should disable status updates from Discord users and will prevent rooms from filling with status updates.
What are the main negative effects from this?

status messages won't be bridged, then.
Also, the bug will still happen eventually, so it isn't a proper fix
Am 9. April 2020 08:57:59 MESZ schrieb "Matej Drobnič"<EMAIL_ADDRESS>
I think I might have found a workaround for this. I added following to
the config file:
presence:
 disableStatusState: true

From what I understand, this should disable status updates from Discord
users and will prevent rooms from filling with status updates.
What are the main negative effects from this?
--
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub:
https://github.com/matrix-discord/mx-puppet-discord/issues/65#issuecomment-611364313

Yes I understand that, but what exactly does "status messages" mean?

the labs feature in riot for status messages. the discord thing "Playing xyz"
Am 9. April 2020 16:11:37 MESZ schrieb "Matej Drobnič"<EMAIL_ADDRESS>
Yes I understand that, but what exactly does "status messages" mean?
--
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub:
https://github.com/matrix-discord/mx-puppet-discord/issues/65#issuecomment-611549231

Oh there is a labs feature. Just wanted to know where this might get displayed. Thanks!


Vertical scroll position of modal saves between openings

I use a default modal like in a documentation: http://getbootstrap.com/javascript/#modals
I open a modal for a first time ('Launch demo model' button), scroll down and click 'Close'. Everything is ok.

Then I open it again and it is already scrolled down. Modal has the same position where it was closed.

Is it a normal behavior? And how could I open the modal for a second time in top scroll position?
P.S. I am sorry if I write it in wrong place, but I did find an answer on my question in the documentation.

i'm facing same this problem in firefox alone. I'm using the version 4.0.0-beta.  Is there any solution


Unlockable Simulator Skins

Context
@jwunderl shared some reskins of the simulator, which gave me an idea we apparently had before: Unlockable simulator skins!
This could be a great way to reward our users for participating in things like game jams and much more.
Achievement Ideas
None are set in stone obviously, just throwing ideas out there.

Participate in a game jam
Code and play a multiplayer game with 3 other players
Use arcade X number of hours
Make a contribution to our repos
etc.

Features

The skin would be displayed when sharing with others

Examples
Bubblegum Theme

Another example

For a later revision of this, we could have "textures" that are Arcade images. This can allow something like an ocean image for participating in the Ocean Game Jam. You could even have animated ones too.


Unit testing examples

Hi @nipafx,
A colleague and I have been working through your book about JPMS - we found it very helpful and informative.   However, we noticed that there is no material that covers unit testing.  Is it possible to add an example to this repository that demonstrates how this would work with modules, or is there a reference that you could recommend?
From a cursory reading, others have added a separate unit testing module that requires the module under test.  Testing internals requires adding additional exports from the source to the test module.
I would be grateful for your help / any resources that you can provide.
Thank you,
David

I've managed to find a solution that has been proposed elsewhere, and in fact corresponds to a section of the book (section 4.1 Organizing your project in a directory structure).  The solution I have adopted creates a separate tests module for every src module, and uses exports and requires to gain access to the internal packages.

Hi @davecromberge, sorry for taking a while to reply. Glad you found a solution.


Write a crash reporting RFD

While we'd like Hipcheck to be robust and minimize crashing, we should also be realistic and recognize that Hipcheck will sometimes crash and we ought to do our best to empower users to get those crashes solved.
There's some interesting prior art here:

Bun: https://bun.sh/blog/bun-report-is-buns-new-crash-reporter
Tailscale: (don't have the link right now)
Firefox: https://hacks.mozilla.org/2022/06/everything-is-broken-shipping-rust-minidump-at-mozilla/

Closing as no longer a priority.


Minimum Docker version requirement

In the Requirements section, can you add the minimum docker version? I tried testing a container job on an old build server and got this error:
Min required docker server version is '17.12', your docker ('/usr/local/bin/docker') server version is '17.9.1'

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

ID: 3339a2e0-be29-1363-f588-b231d4472c02
Version Independent ID: 72dd11a3-704d-d0fd-6dfa-cf49f3352de3
Content: Container Jobs in Azure Pipelines and TFS - Azure Pipelines
Content Source: docs/pipelines/process/container-phases.md
Product: devops
GitHub Login: @erickson-doug
Microsoft Alias: macoope

i have the same problem ?
tried the solution docker in docker, but had other problem....

Yes, please help. My docker server version used to be at 18.x.x and for whatever reason (nobody did anything) it's now at 3.x.x and builds are failing because of this.

I'm being hit by the same bug:

jobs:
  - job: 'Documentation'
    pool:
      vmImage: 'ubuntu-16.04'
    container:
      image: osgeo/proj-docs
      options: --privileged
...

Thank you for reporting this issue. I'm sorry for the long delay in response. I was out of the office for a long period of time earlier this year.


Add conditional for Ubuntu 22.04

Add conditional for Ubuntu 22.04 under scale_version_id() to prevent scaling to version 18.04.

@maximvelichko The Pullrequest #48 you did on Oct 7, 2022 was overwritten by this commit:
https://github.com/microsoft/mdatp-xplat/commit/22086479aa74b423b4598c4ee22460a44f230a06
This looks like a bad manual merge.
See issue: https://github.com/microsoft/mdatp-xplat/issues/47

Hi, @pmooo @quovide , please push the PR again for your suggested changes for issue #47. Sorry, for overwriting your changes


Load classpath in windows

Implemented loading the maven classpath for windows:

added the necessary windows command
added some handling for the partial error case : when we run the mvn command to get the classpaths, there's a case when some dependency fails to download, or some module fails to build, however, we get some of the classpath, I just assumed that we can load the succeful part, and log a wrning with the error, if you want this to behave differently feel free to let me know and I'll change it. here's a screenshot for this case :

changed behavior to throw in the case where there are errors in the mvn result.


Update FileInsight module

Added support for the base module parsed entities
Added a permission test at the beginning and exit when it fails (it is a bit different than the other modules permissions mgmt, but there were so many cases - some of which can fails for other reason and that's ok - that I figured I do a test upfront).
Fixes #193

Actually, I need to check it a last time on a sub where I do have an MDE.
Lately, the arm template deployement have been timing ut on my machine...

@piaudonn ok let me know when you're ready for me to merge it.  The overall deploy template is timing out on you? or just any arm template in general?  I just deployed the whole solution this morning without issue

Should bo good to go.


Forking in the Editorial Workflow

Netlify CMS backends currently only work if you have write access to a repository. If you don't have write access to a repository, contributing generally involves:

creating a fork
committing changes in a new branch
opening a pull/merge request in the source repo

Git hosts support forking via API, so Netlify CMS should be able to facilitate editing content through forking and pull requests.
Expected approach
The current editorial workflow functionality in the GitHub backend can be supplemented to utilize a fork. The following should occur when persisting a change:

Call the create fork endpoint, which will create a fork if it doesn't already exist and return info about the fork
Be ready to poll in case the fork is being created and git objects aren’t ready
Get the PR base branch SHA from the source repo
Create a new branch in the fork repo referencing the SHA from the source repo
Use this branch for standard editorial workflow procedure
Open PR against the source repo

Activation Developer/User Experience
Forking can be implemented in such a way that it automatically works for the GitHub backend, making it zero effort for implementing developers.
For editors, forking should be used if the editor does not have write access to the repository being edited.

Check for write access
If the user has write access, use the standard editorial workflow
If the user does not have write access, notify them that a fork will be created if it does not already exist, and a PR will be opened from the fork.
If the user does not confirm that forking is okay to do, do nothing.
If the user confirms forking is acceptable, proceed with PR from fork.

Here's a writeup I've done investigating the forking process in the CMS, step by step:

Netlify CMS GitHub forking workflow

Authenticate as the GitHub user
When logging into the CMS, the user will use their own GitHub account. Ideally, we could then tell if the user has permissions to access the repository using the /repos/:owner/:repo/collaborators/:username/permission endpoint, and automatically offer to fork the repo if the user does not have write permissions to the repo. However, that endpoint is currently in a "preview period" and the GitHub documentation indicates it should not be relied upon in production. We have two alternatives to using this API endpoint:

Use separate instances of the CMS, one which uses the forking workflow and does not allow publishing entry drafts, and one which uses a traditional Netlify CMS setup and allows entry drafts to be published.
Require a list of specific GitHub accounts which can access the repo directly be provided in the repo or in the CMS configuration. The CMS will access the repo in the traditional manner for these specified maintainers (who will thus be able to publish entries), but accounts outside of the specified list will use the forking workflow.(Q: Should maintainers also use the forking workflow for everything but publishing?)

Check for a fork
Once the user agrees to fork the repository to edit, we need to find out if the user has an existing fork. This can be done one of three ways:

Require that the user's fork be named the same as the original repository. This is almost always the case, but there are exceptions. Use that repo.
Using the /repos/:owner/:repo endpoint, we can check the repo of the same name as the original repo. If that is not a fork of the original repo, request the list of all the user's repos with the /user/repos endpoint. Iterate through these, requesting the repo info on each, until we find a fork of the original repository. This is expensive in the worst case, but should be able to be cached almost indefinitely.
The same approach as 2, but iterating through the list of forks of the original repo at the /repos/:owner/:repo/forks endpoint to find a fork by that user instead of iterating through the user's repos to find a repo which is a fork.

Create a fork if none exist
If no fork exists for the user, we can trigger its creation with the /repos/:owner/:repo/forks endpoint. Unfortunately, this endpoint is asynchronous, so we'll have to poll to determine when the repo has been created and is ready to edit. Once it is, we can complete the user's login process and begin pulling data from GitHub.

Creating a new entry
When creating a new entry, we will create the branch and commits on the user's GitHub account. When a repository on GitHub is a fork, it is able to create new branches using a SHA reference to an object in the repo it was forked from.

Making an entry ready to review
To avoid spamming maintainers with PRs of unfinished posts, we might want to implement a staged system where draft posts only exist on the forked repo, and moving them to "Ready to Review" actually creates the PR on the original repo. The "Publish" button should also be changed to "Submit for review", unless the user is a maintainer of the original repo. Once the entry is submitted, we should create a PR on the source repo using the SHA of the branch in the fork.

Concerns

Image display from display_url
We cannot depend on any new images being uploaded to the site specified by display_url until they have been published to the original repo and a build has completed. Additionally, our current approach of updating the master branch with images so that we can load them from the site will not work, since all new content will have to be contained in a single PR. The solution for this is to pull images through the API exclusively, which we already have code for (even though we don't use it everywhere in the UI). This won't necessarily be possible in all cases (consider build images that don't map 1:1 with source images, like multiple resized versions of a single image created at build time), but we should be able to cover the common ones.

No deploy previews until the PR on the source repo is created
If we don't create PRs immediately when saving a draft, as suggested above, deploy previews will be unavailable until the entry is submitted for review (which, in this approach, would create the PR on the source repo).

git-gateway as an alternative
As git-gateway does not currently have any role enforcement, we cannot authenticate non-maintainer accounts using it. We could limit their actions in the UI, but they would still have access to the JWT token that edits the original repo, with all the permissions that encompasses.
However, there are downsides to not using git-gateway. All editors must have GitHub accounts in order to use the forking workflow (it's fundamental to the approach), and a lack of an Identity login means we can't use Netlify features which require Identity. It might be possible to allow users to log in to both in order to authenticate with Identity without using git-gateway for API access, but that would be a messy user experience.
It would be possible to support OSS contributions in git-gateway, but it would entail adding a role system requiring gating and rewriting responses for all available API endpoints, which would be a significant time investment.

More thoughts on UX/DX:

User loads CMS
After login, if GitHub + EW active and they don't have write access, notify that fork will be created if it doesn't exist, and that edits will happen in the fork.
Use localstorage to remember that a fork was fetched/created and just use it in the future.
If they decline forking, they can't log in and view the admin at all
If they accept, the CMS is running entirely from their fork at that point, not the original repo.
When running from a fork, it needs to use a special branch that is owned by the CMS, some kind of CMS-BASE branch or something. That branch should be updated with the latest from upstream branch (whichever branch is configured).
Editorial workflow branches should be able to work exactly as they do now.
If possible to uncheck "allow maintainers to edit branch" option if that's still possible, we should to avoid breaking EW PR's with unexpected edits from maintainers.
When an entry is saved, drafts should not create a PR, only waiting for review/ready to publish should.
When moving from draft to Ready for Review, a notification should be provided that this will open a PR in the upstream repository.
The user should be able to (optionally) provide the title and message for the PR. Not sure where this should happen. We can tack this on at the end of development.


[SIG-scale] KubeVirt PProf Profiler tools

This PR enables PProf profiling aggregation across the KubeVirt control plane. Using the new cluster-profiler client tool, a developer can start, stop, and dump PProf profiling data for every component in the KubeVirt Control plane. This feature requires the ClusterProfiler feature gate to be enabled.
Example workflow
start CPU profiling across the KubeVirt control plane
$ cluster-profiler --cmd start
2021/08/09 14:49:18 SUCCESS: started cpu profiling KubeVirt control plane

stop CPU profiling across the KubeVirt control plane
$ cluster-profiler --cmd stop
2021/08/09 14:49:54 SUCCESS: stopped cpu profiling KubeVirt control plane

dump the pprof results for every KubeVirt control plane component locally
$ cluster-profiler --cmd dump
2021/08/09 14:50:28 SUCCESS: Dumped PProf results for KubeVirt control plane to [cluster-profiler-results]

introspect the pprof data dump
$ tree cluster-profiler-results/
cluster-profiler-results/
├── virt-api-9f5c6489-8xp5b
│   ├── allocs.pprof
│   ├── block.pprof
│   ├── cpu.pprof
│   ├── goroutine.pprof
│   ├── heap.pprof
│   ├── mutex.pprof
│   └── threadcreate.pprof
├── virt-api-9f5c6489-vnxwl
│   ├── allocs.pprof
│   ├── block.pprof
│   ├── cpu.pprof
│   ├── goroutine.pprof
│   ├── heap.pprof
│   ├── mutex.pprof
│   └── threadcreate.pprof
├── virt-controller-5658b7577c-q2mlq
│   ├── allocs.pprof
│   ├── block.pprof
│   ├── cpu.pprof
│   ├── goroutine.pprof
│   ├── heap.pprof
│   ├── mutex.pprof
│   └── threadcreate.pprof
├── virt-controller-5658b7577c-zt2n8
│   ├── allocs.pprof
│   ├── block.pprof
│   ├── cpu.pprof
│   ├── goroutine.pprof
│   ├── heap.pprof
│   ├── mutex.pprof
│   └── threadcreate.pprof
├── virt-handler-2dqtw
│   ├── allocs.pprof
│   ├── block.pprof
│   ├── cpu.pprof
│   ├── goroutine.pprof
│   ├── heap.pprof
│   ├── mutex.pprof
│   └── threadcreate.pprof
└── virt-handler-hvddz
    ├── allocs.pprof
    ├── block.pprof
    ├── cpu.pprof
    ├── goroutine.pprof
    ├── heap.pprof
    ├── mutex.pprof
    └── threadcreate.pprof

Enabling and Authorization
The cluster-profiler tool works by accessing a subresource in virt-api which calls out to every component to aggregate pprof data. This feature requires the ClusterProfiler feature gate to be enabled to work.
When the ClusterProfiler feature gate is enabled, the corresponding subresource endpoints become available for all authenticated users, similar to our version endpoint. So this feature should only be enabled in developer environments.
cluster-profiler pprof gathering tool and corresponding "ClusterProfiler" feature gate

/cc @marceloamaral @kwiesmueller @rthallisey @rmohr

I wonder if a near term step could be to also pull profile information from virt-launchers via virt-handler to analyze them when we get to it.

I wonder if a near term step could be to also pull profile information from virt-launchers via virt-handler to analyze them when we get to it.

if it's useful, we certainly can.
I'd consider this initial effort as an entry point. We can add more options/functionality/optimizations later on as needed.

@kwiesmueller @rthallisey I updated the PR with more unit testing and the addition of gather virt-operator pprof data as well.
I think this should be good to go for another review. Maybe we can push out some of the suggestions around adding more options or optimizations to follow up later on.

/approve

/retest

I think we need to add Documentation somewhere
/retest
/lgtm

@davidvossel the unit test is failing...

/hold until the unit test is fixed

/hold cancel
unit tests fixed. it wasn't a test case issue exactly. It was an issue with junit merger of my new test cases

/retest
/lgtm

/retest


Bugfix/110/aggressive ai bugs

Fixes #110
Testing Scenarios:

Aggressive Enemies Leash Correctly (when enemies reset/leash, they should return to their spawn area, not keep running)

Enter combat, run away, enemy should leash
Enter combat, hit enemy once or twice, run away, enemy should leash

Sheep Animations

After hitting sheep, they should flicker red, and return to normal, not get stuck red

Wander Glitching

Just watch the enemies (specifically the treetrunkguys) for awhile. You should notice that they glitch into walls much less frequently.

@ivoryfitz  can you rebase this one on the latest main?
Thx


Multipass: improve language

Context
Multipass project docs are in a reasonably good shape, but there are (as always) little things that could be improved to offer better user experience. One of them is the use of language that's largely superfluous and doesn't help the user.
The Multipass docs are maintained in and published from the Ubuntu Discourse forum. To suggest changes in a Discourse-hosted docs page, scroll all the way down to the bottom of the page and open the page to which the "Help improve this document in the forum" link points. On the Discourse page, scroll to the bottom of the article (if there are comments, then the bottom of the article is just where the comments start, i.e. not at the very bottom of the page) and click "Edit". (You need an account on Ubuntu Discourse.)
Task
Modify the language throughout the docs set to not use unnecessary verbiage, including:

"simply"
"please"
sentences starting with "You can" (where appropriate)
future tense (where not appropriate, which is almost everywhere)
...

Hi @geoffreynyaga. Thanks for your interest in this issue. The absence of the "Edit" button is caused by a Discourse setting that prevents anyone who has not done a certain amount of reading & commenting from modifying existing topics. It's a bit unfortunate, but that's the way it works.
What we've been doing with docs that are hosted in Discourse, is we'd take the Markdown sources, copy them over top this repo, and let contributors work on the files here until the content is ready. Then someone submits them back to Discourse.
What I didn't realize is that this particular issue makes this approach a bit complicated because the modifications would likely be occurring in many different places in the docs set -- so, copying everything to this repo would be cumbersome (especially considering that there might only be one or two small changes in each file).
We need to come up with a better way of handling changes to Discourse docs.

Hi @geoffreynyaga. Just wanted to let you know I've trying to come up with a sane way of dealing with the mechanics of how to allow you to work on this issue, but I don't have any satisfactory answers yet. I really should've considered this problem before defining this issue for the Academy :/

Hi @PitifulPete, thank you for your suggestion, breaking it down is actually a very good idea. I have reframed this issue to specifically target Multipass tutorials, let us know if that's something you'd like to contribute to!
I will look at Multipass docs closely and try to identify other areas of improvement. In the meantime, please let us know if you have something else in mind, such as application of the Canonical Documentation Style Guide, examples and instructions provided in the docs, etc.

Hi @giuliazanchi. Yes, I'd like to contribute. Thank you!

PitifulPete

Great! You can start by assigning this issue to yourself. Then, please check that you have permission to edit the relevant Discourse pages. To do so, go to , select a tutorial and click "Help improve this document in the forum" at the bottom of the page.
If you don't have the required permissions on Discourse, let me know and I'll set up a temporary copy that you can work on here on GitHub.
Thanks again for your help,
Giulia

@giuliazanchi, i still can't edit on the forum so i will need a temporary file

@PitifulPete I added three Markdown files to the Multipass folder, using short filenames for simplicity (Linux, macOS, Windows). Let me know if you need help!

Hi @PitifulPete , please refresh your copy of the Linux tutorial, I added in some punctuation fixes (see PR #83) that were suggested by another contributor. Thanks!

Hi @giuliazanchi, peep this

Hi @PitifulPete , I'll look at it properly tomorrow and let you know if you're on the right track, thanks so much for such a speedy contribution!

Done! Thanks again @PitifulPete


Fix name of test script in contributing guide

Coverage remained the same at 80.869% when pulling 3ba1057f5a83775f2a922aff3e150490025df071 on itajaja:patch-1 into 88c9516e20bbfd1f5fb9ec478cc9a1624f6eed33 on airbnb:master.


Strategy onPeriod out of Sequence

I'm working with the TALIB functions.  It seems that the execute and callback is being performed on its own thread.  It seems that if the calculation in the TALIB library takes too long, zenbot will move on.  It also appears that the TALIB function calls will queue up and then start to return their results sequentially in their callback functions outside of the main zenbot processing thread.
Here is a screenshot that shows an example:

If periods were being processed synchronously, then there should be no break between the regular zenbot out and the next number.  These numbers are the result of console.log(result.nbElement) being executed in the TALIB callback inside a function contained in the "lib" directory that is executed in the strategy's onPeriod method.
Also, without changing the code but simply rerunning, the output shown in the screenshot will not duplicate in the same spot every time.  It seems to be hit or miss where it will happen.
These callbacks seem to be processed asynchronously.  Is there a way to make these TALIB calls process synchronously or is this an illusion from console.log and the standard zenbot output processes?

@DeviaVir, I think this may be a larger problem than what I think is possible to correct with a pull request.  Basically, it would force anyone that utilizes "lib" functions to have to rewrite their utilization of it to now process the results of the "lib" call via a callback function.  Perhaps the talib functions can only be used in the "onPeriod" folder so that the "cb" callback can be used to trigger zenbot to move forward.
After doing some tests and reviewing the talib source, this appears to be a problem where the talib functions are executed asynchronously.  This means that the callback from talib may not be ready in time for zenbot's need to calculate it's return values.  I noticed that sometimes i would get sporadic undefined errors, which clued me into this in the first place.
It seems that there may need to be a callback setup from a library function found in the "lib" directory.  That way the talib function can callback to the originating procedure after the calculations are complete.  That way the talib dependency can be satisfied prior to the callback in the "onPeriod" function being executed.


Ighack

Bhai 1 type kr ke enter kr rha hu to nhi ho rha

Remove and run it again.
On Sat, 28 Sept 2024, 10:16 pm Zain1234jackie, @.***>
wrote:

Bhai 1 type kr ke enter kr rha hu to nhi ho rha
—
Reply to this email directly, view it on GitHub
https://github.com/dark-player/instabrute.github.io/issues/6#issuecomment-2380807600,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQG5LDKDF34QDV5NRZ7KAWTZY3MPDAVCNFSM6AAAAABPAYQCXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBQHAYDONRQGA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


[NFC] Please linter by reducing width to < 80 columns.

Seeing CI failure in https://github.com/apple/swift/pull/28479
./utils/swift_build_support/swift_build_support/cmake.py:245:80: E501 line too long (80 > 79 characters)

@swift-ci Python lint


perf: optimize move operation

Purpose
Improve the performance of file renaming/moving by using the api to do so on the backend.
What the code is doing
The default way is implemented in the base class using the essential methods which simplifies the requirement for implementing a filesystem. However, this means files will be downloaded and re-uploaded when calling blob_fs.move(src, dst). We override that by using the rename_file method in the azure sdk, which presumably does this in constant time.
Testing
Ran the test suite - pytest tests/test.py. To validate the perf improvement I just wrote a loop that creates and renames 10 files with a few MB of content each. The current way took 17sec vs about 1sec for the optimized version.
Time estimate
5 min

Could you remind me the original functionality of move? I presume what it does is moving a file in one directory into the other in the blob within one container.

Could you remind me the original functionality of move? I presume what it does is moving a file in one directory into the other in the blob within one container.

Sure thing. The implementation is here, for reference. And the behavior is similar to the mv command, except for both src and dst have to be files. So it would fail (via error handling, not input validation) if e.g. we called it with _fs.move("/dir1/foo.txt", "/dir2"). But can also use it to rename a file (in fact, that's the only way to rename a file directly).
Also just fyi, blobs are essentially files. I'm not sure what the difference is or why there is another name, but yeah.


MFA Enforced

It probably is helpful to share that $st.State = "Enabled" can be changed to $st.State = "Enforced" so that MFA is enforced, which is one notch higher than simply enabling MFA.

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

ID: 4cb129d2-9594-bf0c-5946-982f0ed0d888
Version Independent ID: 6522b038-6853-3552-55c8-f174cf56573d
Content: Enable per-user Multi-Factor Authentication - Azure Active Directory
Content Source: articles/active-directory/authentication/howto-mfa-userstates.md
Service: active-directory
Sub-service: authentication
GitHub Login: @Justinha
Microsoft Alias: justinha

@cuatrix-bensonlee Thanks for your comment! We will review and provide an update as appropriate.

@cuatrix-bensonlee Thanks for your comment! We will review and provide an update as appropriate.

@cuatrix-bensonlee We do not recommend moving the state directly to Enforced state because doing so causes disruptions during sign-in to applications which do not support modern authentication as stated in the change state using PowerShell section .

That is the reason the article provides the details of all three valid states and recommends users to start with enabled however if one is sure that their environment doesn't have any applications within their organization which use legacy authentication , they can choose to enforce it . We believe that the description in the document above clarifies this . Hope this helps. We will now close this issue.
Thank you.


⚠ Bofrost.de has degraded performance

In 97ad432, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 974 ms

Resolved: Bofrost.de performance has improved in 57ad7c8.


Update to 3.0.1 bring new issues

It looks like there is a a bad interaction between log4net 3.0.1 and log4net.Ext.Json <IP_ADDRESS>
With error:
log4net:ERROR Failed to find type [log4net.Layout.PatternLayout, log4net.Ext.Json]
System.TypeLoadException: Could not load type 'log4net.Layout.PatternLayout' from assembly 'log4net.Ext.Json, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.
   at System.Reflection.RuntimeAssembly.GetTypeCore(String typeName, ReadOnlySpan`1 nestedTypeNames, Boolean throwOnError, Boolean ignoreCase)
   at System.Reflection.TypeNameParser.GetType(String typeName, ReadOnlySpan`1 nestedTypeNames, String assemblyNameIfAny)
   at System.Reflection.TypeNameParser.Parse()
   at System.Reflection.TypeNameParser.GetType(String typeName, Func`2 assemblyResolver, Func`4 typeResolver, Assembly requestingAssembly, Boolean throwOnError, Boolean ignoreCase, Boolean extensibleParser)
   at System.Type.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase)
   at log4net.Util.SystemInfo.GetTypeFromString(Assembly relativeAssembly, String typeName, Boolean throwOnError, Boolean ignoreCase)
   at log4net.Util.SystemInfo.GetTypeFromString(String typeName, Boolean throwOnError, Boolean ignoreCase)
   at log4net.Repository.Hierarchy.XmlHierarchyConfigurator.CreateObjectFromXml(XmlElement element, Type defaultTargetType, Type typeConstraint)

Additionally, the issue with log4net.Util.PatternString using global properties to set dynamic log names,
For example:
<file type="log4net.Util.PatternString" value="C:\Development\TestProjects\Log4NetExample\Logs\DDLogs\dd-%property{LogName}.json" />
This is still not resolved with updates in 3.0.1, in this case, the log name is dd-null where global property "LogName" is set in the main project like so:
log4net.GlobalContext.Properties["LogName"] = "custom_log_" + DateTime.Now.ToString("yyyyMMdd_HHmmss");
Reference to duplicate issue:
#183, but now in version 3.0.1.
Please find a simple project implementation attached.
Log4NetExample.zip

Hi @NoahHabanero,
can you contact https://gitlab.com/gdziadkiewicz ?
It looks like log4net.Ext.Json needs to be adjusted for log4net 3.x
E.g. there are no more matching target frameworks:
log4net supports net462 & netstandard2.0
log4net.Ext.Json supports net452, net40, net35, net20, netstandard1.3

ok I have written to him,
What of the log4net.Util.PatternString issue?

Hi, I will take a look today. BTW, congrats on releasing version 3 of log4net

ok I have written to him,
What of the log4net.Util.PatternString issue?

@NoahHabanero I added a unit test for your problem (see https://github.com/apache/logging-log4net/commit/79b57e5eff0fb970a8d51ca35b5bf63e0b90a6df).
But I can't reproduce. Maybe you set GlobalContext.Properties too late?
It must be called before XmlConfigurator.Configure().
If the problem still persists, please create a separate issue.

Hi all, I reproduced the issue and will be working on getting it fixed.
Sent from Outlook for Androidhttps://aka.ms/AAb9ysg

From: Jan Friedrich @.>
Sent: Monday, October 14, 2024 5:56:33 PM
To: apache/logging-log4net @.>
Cc: Grzegorz Dziadkiewicz @.>; Comment @.>
Subject: Re: [apache/logging-log4net] Update to 3.0.1 bring new issues (Issue #193)
ok I have written to him,
What of the log4net.Util.PatternString issue?
@NoahHabanerohttps://github.com/NoahHabanero I added a unit test for your problem (see 79b57e5https://github.com/apache/logging-log4net/commit/79b57e5eff0fb970a8d51ca35b5bf63e0b90a6df).
But I can't reproduce. Maybe you set GlobalContext.Properties too late?
It must be called before XmlConfigurator.Configure().
If the problem still persists, please create a separate issue.
—
Reply to this email directly, view it on GitHubhttps://github.com/apache/logging-log4net/issues/193#issuecomment-2411660944, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACBG4D2QK64KN4RDRSEXSLTZ3PSTDAVCNFSM6AAAAABP43DQK6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJRGY3DAOJUGQ.
You are receiving this because you commented.Message ID: @.***>

Hi @NoahHabanero ,
I did the move to log4net 3.0.1 in log4net.Ext.Json. There is a pre-release version 3.0.1-develop1504356721 you can test.
The funny thing I found out while testing if it resolves your problems is that the config in the repro is invalid. Instead of
<layout type="log4net.Layout.PatternLayout, log4net.Ext.Json"> you probably meant <layout type="log4net.Layout.SerializedLayout , log4net.Ext.Json">  . Can you check if new version and the config change resolve your problem?
On my side the error with the config change and old log4net.Ext.Json version is:
log4net:ERROR XmlHierarchyConfigurator: Failed to construct object of type [log4net.Layout.SerializedLayout] Exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
 ---> System.TypeLoadException: Derived method 'Convert' in type 'log4net.Layout.Pattern.JsonPatternConverter' from assembly 'log4net.Ext.Json, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' cannot reduce access.
   at log4net.Layout.SerializedLayout.ActivateOptions()
   at log4net.Layout.PatternLayout..ctor(String pattern)
   at log4net.Layout.SerializedLayout..ctor()
   at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean wrapExceptions)
   --- End of inner exception stack trace ---
   at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean wrapExceptions)
   at log4net.Repository.Hierarchy.XmlHierarchyConfigurator.CreateObjectFromXml(XmlElement element, Type defaultTargetType, Type typeConstraint)
log4net:ERROR Failed to create object to set param: layout
logs should be logging.
Check the log file in the Logs folder.

which corresponds nicely to the code change (adjusting access modifier) I did during the move from 2 to 3.

Hi @gdziadkiewicz ,
I have updated to version log4net 3.0.2
And to your log4net.Ext.Json pre-release 3.0.1-develop1517163871
As Well as changed from log4net.Layout.PatternLayout --> log4net.Layout.SerializedLayout
The test project is working as expected!
@gdziadkiewicz once version 3.0.1 is released as a stable version. I will update my main project.
Thank you all for your work and support!
@FreeAndNil thank you for the configuration advice, you are correct, it is working.


create better method of handling different PVC sizes in polysite projects

In a polysite environment it can quite easily end up that each instance will not need the same PVC sizes, we need a way to define the size of a PVC per-polysite-instance

the better solutiion here would be to not polysite -and instead build two projects from the same giturl?


Build failing, likely due to sailbot_msg

Base path: /catkin_ws
Source space: /catkin_ws/src
Build space: /catkin_ws/build
Devel space: /catkin_ws/devel
Install space: /catkin_ws/install
####
#### Running command: "cmake /catkin_ws/src -DCATKIN_DEVEL_PREFIX=/catkin_ws/devel -DCMAKE_INSTALL_PREFIX=/catkin_ws/install -G Unix Makefiles" in "/catkin_ws/build"
####
-- Using CATKIN_DEVEL_PREFIX: /catkin_ws/devel
-- Using CMAKE_PREFIX_PATH: /opt/ros/melodic
-- This workspace overlays: /opt/ros/melodic
-- Found PythonInterp: /usr/bin/python2 (found suitable version "2.7.17", minimum required is "2")
-- Using PYTHON_EXECUTABLE: /usr/bin/python2
-- Using Debian Python package layout
-- Using empy: /usr/bin/empy
-- Using CATKIN_ENABLE_TESTING: ON
-- Call enable_testing()
-- Using CATKIN_TEST_RESULTS_DIR: /catkin_ws/build/test_results
-- Found gtest sources under '/usr/src/googletest': gtests will be built
-- Found gmock sources under '/usr/src/googletest': gmock will be built
-- Found PythonInterp: /usr/bin/python2 (found version "2.7.17")
-- Using Python nosetests: /usr/bin/nosetests-2.7
-- catkin 0.7.28
-- BUILD_SHARED_LIBS is on
-- BUILD_SHARED_LIBS is on
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- ~~  traversing 2 packages in topological order:
-- ~~  - local_pathfinding
-- ~~  - sailbot_msg
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- +++ processing catkin package: 'local_pathfinding'
-- ==> add_subdirectory(local_pathfinding)
-- Using these message generators: gencpp;geneus;genlisp;gennodejs;genpy
-- +++ processing catkin package: 'sailbot_msg'
-- ==> add_subdirectory(sailbot_msg)
-- Using these message generators: gencpp;geneus;genlisp;gennodejs;genpy
/opt/ros/melodic/share/genmsg/cmake/pkg-genmsg.cmake.em:56: error: <class 'genmsg.base.InvalidMsgSpec'>: /catkin_ws/src/sailbot_msg/msg/Sensors.msg: Invalid declaration: // For more information refer to:
Traceback (most recent call last):
  File "/usr/bin/empy", line 3302, in <module>
    if __name__ == '__main__': main()
  File "/usr/bin/empy", line 3300, in main
    invoke(sys.argv[1:])
  File "/usr/bin/empy", line 3283, in invoke
    interpreter.wrap(interpreter.file, (file, name))
  File "/usr/bin/empy", line 2295, in wrap
    self.fail(e)
  File "/usr/bin/empy", line 2284, in wrap
    callable(*args)
  File "/usr/bin/empy", line 2359, in file
    self.safe(scanner, done, locals)
  File "/usr/bin/empy", line 2401, in safe
    self.parse(scanner, locals)
  File "/usr/bin/empy", line 2421, in parse
    token.run(self, locals)
  File "/usr/bin/empy", line 1425, in run
    interpreter.execute(self.code, locals)
  File "/usr/bin/empy", line 2595, in execute
    _exec(statements, self.globals, locals)
  File "/usr/bin/empy", line 42, in _exec
    exec("""exec code in globals""")
  File "<string>", line 1, in <module>
  File "<string>", line 38, in <module>
  File "/opt/ros/melodic/lib/python2.7/dist-packages/genmsg/deps.py", line 45, in find_msg_dependencies_with_type
    spec = genmsg.msg_loader.load_msg_from_file(msg_context, msg_file, full_type_name)
  File "/opt/ros/melodic/lib/python2.7/dist-packages/genmsg/msg_loader.py", line 289, in load_msg_from_file
    raise InvalidMsgSpec('%s: %s'%(file_path, e))
genmsg.base.InvalidMsgSpec: /catkin_ws/src/sailbot_msg/msg/Sensors.msg: Invalid declaration: // For more information refer to:
CMake Error at /opt/ros/melodic/share/catkin/cmake/safe_execute_process.cmake:11 (message):
  execute_process(/catkin_ws/build/catkin_generated/env_cached.sh
  "/usr/bin/python2" "/usr/bin/empy" "--raw-errors" "-F"
  "/catkin_ws/build/sailbot_msg/cmake/sailbot_msg-genmsg-context.py" "-o"
  "/catkin_ws/build/sailbot_msg/cmake/sailbot_msg-genmsg.cmake"
  "/opt/ros/melodic/share/genmsg/cmake/pkg-genmsg.cmake.em") returned error
  code 1
Call Stack (most recent call first):
  /opt/ros/melodic/share/catkin/cmake/em_expand.cmake:25 (safe_execute_process)
  /opt/ros/melodic/share/genmsg/cmake/genmsg-extras.cmake:303 (em_expand)
  sailbot_msg/CMakeLists.txt:26 (generate_messages)

-- Configuring incomplete, errors occurred!
See also "/catkin_ws/build/CMakeFiles/CMakeOutput.log".
See also "/catkin_ws/build/CMakeFiles/CMakeError.log".
Invoking "cmake" failed

Exited with code exit status 1

Resolved in other repo. Issue with comment type.


[Suggestion] Susped global hotkeys (pause key pauses gemfarm)

I suggest suspending hotkeys because they don't really serve any purpose other than accidentally silently stopping your gemfarm or jimothy or whatever else you're doing if you press pause key, either on purpose for something else, or by accident.

Thanks for the suggestion. If we were to go back in time and do things over again, we probably would handle this differently. But pause functionality has existed in this state for so long that we feel changing it now may benefit fewer users than it would disrupt.

But it's so silent and global :/ I don't think anyone actually uses it, except on accident. You could poll people of #scripting to see, most won't even know it's a thing, until they have to use pause key for some reason (I used it inside another game) and then realise their gemfarm was no longer working.
At least add a setting in advanced or something, to make people aware and easily able to turn it off without having to modify the code.


Undefined local variable occurrence_counter

Upgrading to the email notifications and getting this currently:
ERROR -- : [ActiveJob] [ActionMailer::MailDeliveryJob] [65ec43aa-b13e-4a96-aa7b-67770a3e6d79]
Error performing ActionMailer::MailDeliveryJob (Job ID: 65ec43aa-b13e-4a96-aa7b-67770a3e6d79)
from Async(default) in 97.84ms: ActionView::Template::Error (undefined local variable or method `occurrence_counter' for #<ActionView::Base:0x00000000054dd0>):

This also has the unfortunate side effect of continually looping into error after error as I think solid_errors is catching the error from this and trying to report the error, which then raises an error...

Fixed by #28


Report errors with validation dataloader

Hi, I try to reproduce the results on ogb-lsc. It report errors at the 90% iteration of the first epoch. It seems there is something wrong with the validation dataloader. Could you give me some suggestions to fix it? Thanks!

Are your environment same as the requirement? Could you provide a minimal reproducible example with detailed package version information? In addition, could you try to set num_workers=1 to see the error message?

Thanks for your reply! Previously, my pytorch-lightning version is 1.4.2. After changing to 1.3.0, it works.
Thanks for your help!


Created CONTRIBUTION.md

Created a contribution.md file that can help the folks to know about how to contribution to search_with_ai and what rules they can follow.
This file is necessary for the contributors to get to know how to contribute to the search_with_ai repository.

Thank you for improving search_with_ai! it's very helpful.

Thanks man if you have anything else then please let me know as right now I am going through the code base and want to know more of it so if you got something for me then let me know.


[json] improve (or remove) warning when schema download is disabed

Type: Bug
I open any package.json and see a warning. I have disabled this feature in the past, it is still disabled in the settings but its somewhat turned back on. In fact the warning even mentions that the feature is disabled.
Please remove the warning if the feature is disabled.
At the moment the only way to 'hide' this warning is to enable the feature again.
Problems loading reference 'https://json.schemastore.org/package':
  Unable to load schema from 'https://json.schemastore.org/package':
    Downloading schemas is disabled through setting 'json.schemaDownload.enable'.

VS Code version: Code 1.74.0 (5235c6bb189b60b01b1f49062f4ffa42384f8c91, 2022-12-05T16:47:18.476Z)
OS version: Linux x64 6.0.6-76060006-generic
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 2800)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
1, 1, 1

Memory (System)
15.18GB (6.16GB free)

Process Argv
--unity-launch

Screen Reader
no

VM
0%

DESKTOP_SESSION
pop

XDG_CURRENT_DESKTOP
Unity

XDG_SESSION_DESKTOP
pop

XDG_SESSION_TYPE
x11

Extensions (7)

Extension
Author (truncated)
Version

esp-idf-extension
esp
1.5.1

todo-tree
Gru
0.0.220

better-cpp-syntax
jef
1.17.2

git-graph
mhu
1.30.0

cpptools
ms-
1.13.8

color-highlight
nau
2.5.0

rust-analyzer
rus
0.3.1325

(2 theme extensions excluded)

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.74.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

updated to:
Version: 1.74.2
Commit: e8a3071ea4344d9d48ef8a4df2c097372b0c5161
Date: 2022-12-20T10:27:19.253Z
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 6.0.6-76060006-generic
Sandboxed: No
the issue remains in 1.74.2

Is "json.schemaDownload.enable" disabled or enabled in the settings?
If you disabled it, then we won't load the schema, but show the warning so users understand why they don't get any schema support.
Are you suggesting to not show such a warning in that case?

it is set like this: "json.schemaDownload.enable": false but I do get the warning

me too, when settings.json set {"json.schemaDownload.enable":false}  when open package.json it's still show warning info

Disabling a feature should not produce a warning that it is disabled.

Yep, this is a very curious UX when I specifically choose to disable an unwanted feature, and then get a persistent warning stating I have disabled the feature.
As with all other settings, this shouldn't be a warning.

Imagine a warning is shown for every setting that is not on the default value. I would have over a thousand warnings, completely useless and drowning out actual relevant/useful warnings.
Please remove the warning if the feature is disabled. There are many closed issues with the same request for different schemas, why not spend 5 minutes and remove this 1 line of code?

or you know add another option so I can choose if I want to see this warning.


Please avoid Dune 3.13-3.15

Hi,
Unfortunately the releases of Dune 3.13.1, 3.14.2 and 3.15.1 all contain a serious bug where any changes in the output of coqdep will cause Dune to rebuild all .v files. This doesn't affect the main Coq build only projects that use Dune to build, such as HoTT/Coq-HoTT. The main build in the platform will be fine, but users with Dune projects based on the platform will be annoyed by the constant rebuilds.
I therefore recommend avoiding those versions. I've already submitted a fix for this issue upstream:

https://github.com/ocaml/dune/pull/10446

and most likely that will appear in a point release for 3.15. Probably 3.15.2. However this still means that previous versions 3.13 and 3.14 will have this bug. I will speak with the Dune team to ask for those to be back ported also.
Regarding the platform, I'm not exactly sure which Dune version you have chosen, but I wanted to give you a heads up that this issue was present. If by the time you cut a new release we have 3.15.2 then I would recommend using that for the platform, if not then I would recommend sticking with 3.12 if it is possible with the package constraints.

Triage note: we are currently only using dune 3.15.3 and 3.4.1, so closing.


Ts 3647

TS-3647 : CPP-API for  ....
TSHttpTxnConfigIntSet
TSHttpTxnConfigIntGet
TSHttpTxnConfigFloatSet
TSHttpTxnConfigFloatGet
TSHttpTxnConfigStringSet
TSHttpTxnConfigStringGet
TSHttpTxnConfigFind

I think you need to clean up this branch, removing commits that aren't intended for upstream. A more descriptive pull request message would also help us figure out what this change is intended to address.

To clarify James' comment, it looks like you have TS-3560 mixed in with this as well. You'll want to have multiple branches, one per ticket, and pull request from those. If there's a dependency it should be marked on the Jira tickets but the pull requests should still be distinct.


add Flowers notebook

@RatanRSur,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


LCO: Labware info in app

Adding the labware browser info to the run app

Closing this old ZenHub epic as stale. We've moved these things to Jira.


Is Azure SQL Managed Instance considered inside the Azure SQL Database?

Hi, I would like to know if Managed Instances are considered the same as Azure SQL Database or if they are considered as SQL Server instances On-premises.

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

ID: ea45d88b-212b-51ae-b902-6efd5873f6c5
Version Independent ID: 6f86e171-7553-3d01-00fa-e0865d8d817b
Content: Data sources supported in Azure Analysis Services
Content Source: articles/analysis-services/analysis-services-datasource.md
Service: azure-analysis-services
GitHub Login: @Minewiskan
Microsoft Alias: owend

@uvita
Thanks for the feedback! We are currently investigating and will update you shortly.

@uvita yes, Managed Instance is considered part of Azure SQL Database.


Create user showcase.

Fixes #2269.

WIP.

[ ] Add missing logos.
[ ] Add introductory paragraph.
[ ] Link from homepage and nav bar.

Current coverage is 89.23% (diff: 100%)

Merging #2369 into new-docs will not change coverage

@@           new-docs      #2369   diff @@
==========================================
  Files            39         39
  Lines          1486       1486
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1326       1326
  Misses          160        160
  Partials          0          0

Powered by Codecov. Last update 73424a9...e14319a

nice!

two teams at MS also use it, but I don't know if it makes sense to include them.

This is now ready for review. A small showcase is visible at the bottom of the homepage, and the full showcase is now linked to from the navbar.
Homepage:

Full showcase:

looks lovely. Thank you so much.


Design for Career/job page phase 2

Some content ideas for phase 2 of the careers/jobs page, see #39


feat: add transferable record verifier

:tada: This PR is included in version 1.0.0-alpha.7 :tada:
The release is available on:

npm package (@release-v1 dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Remove card handle tab background

Ideally during card scrolls the top 'padding' that houses the card handle should be blank, not white.
The handle can stay fixed to the top of the card, and should always be the highest z-index UI element in the card, so that it remains interactive.

The bottom sheet library we are using doesn't have a built-in solution for this. I tried a few hacks, but all caused the usability to suffer. Going to punt on this for now.

adjusted label and milestone accordingly


Base form submission panel to use get_submission_class

Fixes #3758
Additional tests written and pass locally, make lint run locally, no docs needed as this now aligns with expected behaviour when overriding the form_submission_class.

Duplicate PR


[Windows] Window cannot be dragged

The window cannot be dragged. It can currently only be moved by resizing.
Affects Windows only.

Experienced this also, very annoying to say the least lol


German localization

Hi,
the short strings for german (de) should look like this:
monthsShort : 'Jan_Feb_Mrz_Apr_Mai_Jun_Jul_Aug_Sep_Okt_Nov_Dez'
weekdaysShort : 'So_Mo_Di_Mi_Do_Fr_Sa'

The current version with dots looking very strange and are not required.
Almost same for Austria (de_at):
monthsShort : 'Jän_Feb_Mär_Apr_Mai_Jun_Jul_Aug_Sept_Okt_Nov_Dez'
weekdaysShort : 'So_Mo_Di_Mi_Do_Fr_Sa'

Many thanks in advance.

You are right. One PR would be good to fix this.

The German norm DIN 5008 recommends "Mär" instead of  "Mrz". But also recommends "Sept" instead of "Sep". Confusing!
Also, it allowes for months with only four characters to not be abreviated (eg. Juli instead of Jul.)
http://www.din-5008-richtlinien.de/datum.php
I'm not quite sure which option should be implemented :-(

@lothargrieb, would you submit a PR to get this fixed, please?

+1

Based on the discussion in #3803 and the fix in #3829 , I'm going to close this. If you think this merits more discussion, please re-open @lothargrieb


force_plot visualizing all predictions doesn't show the feature with highest shap values

Hi, I used this amazing force_plot to display all instances by sample ordering. As seen below, for instance with index 3 in my dataset the key features displayed are : MF_MATCH_RESIDENCE, MF_MATCH_CITY,MF_FUZZY_FULLNAME_MATCH,MF_MATCH_NATIONALITY AND MF_EXACT_FN_MATCH. These can be seen in this screenshot below:

Now, one would expect that these are probably the features with highest shap values in magnitude when I explain the index 3 right? But that's not the case. See screenshot below:

As you can see, the top 3 contributing features namely MF_MATCH_DOB, MF_MATCH_YOB and GNM_DoBScore were not even displayed in the force plot above! What is more surprising is that when I tried to toggle through all the instances in the above force_plot, these top 3 features were not part of most of the displaying features. However, they are the highest contributing in almost all my instances, as they are the variables of highest importance by my Random Forest. I am wondering if there is some issue with the way this wonderful dynamic force_plot is built? Please help.
If needed for you to address this issue, I will then send subset of my data, my random forest model object and my code as they are confidential information.  Thanks in advance!

Sorry for the slow reply! It looks to me like there is some mismatch between the column names. So either the names in the force_plot are not right or the ones you are checking in your dataframe are not right (which means one of them has the features mislabelled). Perhaps it has something to do with filtering the column names to only those of type int64?


how to enable #define VersionAboveV24? game is crashing.

#define GamePackageName "com.arcsystemworks.bbdw"
#define UnityVersion 2019.3.7f1
// 2018.3.0f2(v24.1) and up enable it
#define VersionAboveV24
my game.h
i looked at the similar issues and perfare said to enable #define VersionAboveV24 but i dont know what to change with it.
the game version is 2019.4.14f1

same problem here... unityversion 2018.4.31f1 .. how to solved this ??
is it change to compability version with #define VersionAboveV24 enable or how ?

same problem here... unityversion 2018.4.31f1 .. how to solved this ??
is it change to compability version with #define VersionAboveV24 enable or how ?

#define UnityVersion 2018.4.31f1


Fixes #10814.

This PR fixes #10814. It assumes that is possible read the Position from the Stream, which I think is true in all code paths the PR affects. If the original stream was not Seekable from the beginning, it will be converted to a ChunkedStream.
I think this fixes the issue with #10814 , but the same problem could be in other places as well.

Can one of the admins verify this patch?

Obselete.


Missing what DNS server configuration is on the vNets

Assuming that it is set to the Azure default resolver in the vNet DNS servers, but that needs to be documented for completeness.

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

ID: 67376353-3eff-47d3-3e52-13600075ebd4
Version Independent ID: 88cd7c90-2a27-a389-a751-99b5dc37120e
Content: Quickstart - Create an Azure DNS Private Resolver using the Azure portal
Content Source: articles/dns/dns-private-resolver-get-started-portal.md
Service: dns
GitHub Login: @greg-lindsay
Microsoft Alias: greglin

@Roblarson
Thank you for your feedback! We have assigned this issue to the author to review further and take the next course of action.

If the quickstart doesn't say to change a setting, the setting isn't changed.  I am not sure we need to call this out, but it can't hurt.
There are other documents that discuss scenarios where the DNS server setting is changed to "Custom DNS" for example: https://learn.microsoft.com/en-us/azure/dns/private-resolver-architecture#centralized-dns-architecture
I will look for a place to expressly say that we don't change the DNS setting, and perhaps also point to the use case where this setting might be changed. Thanks for the suggestion. #please-close


Remove underscore dependency from client

Similar to https://github.com/abecks/meteor-inject-data/pull/8, this removes the dependency on underscore from the client. There were several refactors to be done in the client code, but they were all doable with javascript ES6.
The dependency still exists for the server, though. I suppose I could do the same and refactor those, but the intent of these PRs were to help reduce bundle size on the client.

@abecks any news on this one?

@dr-dimitru thanks! Published as 3.1.0


Missing closing brace

When you force a mistake it pops up a missing closing brace

The last field should be "\\" and not "\".


RuntimeError: Error compiling objects for extension

I have followed the instructions to install the dependencies. But when I build FsDet, there was a RuntimeError: Error compiling objects for extension.
My environment：

CUDA 10.2
pytorch 1.5.0
python 3.7.7
GCC 7.5.0

Error:
Traceback (most recent call last):
File "setup.py", line 114, in
cmdclass={"build_ext": torch.utils.cpp_extension.BuildExtension},
File "/usr0/home/zhiqic/anaconda3/lib/python3.7/site-packages/setuptools/init.py", line 144, in setup
return distutils.core.setup(**attrs)
File "/usr0/home/zhiqic/anaconda3/lib/python3.7/distutils/core.py", line 148, in setup
dist.run_commands()
File "/usr0/home/zhiqic/anaconda3/lib/python3.7/distutils/dist.py", line 966, in run_commands
self.run_command(cmd)
File "/usr0/home/zhiqic/anaconda3/lib/python3.7/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/usr0/home/zhiqic/anaconda3/lib/python3.7/distutils/command/build.py", line 135, in run
self.run_command(cmd_name)
File "/usr0/home/zhiqic/anaconda3/lib/python3.7/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/usr0/home/zhiqic/anaconda3/lib/python3.7/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/usr0/home/zhiqic/anaconda3/lib/python3.7/site-packages/setuptools/command/build_ext.py", line 87, in run
_build_ext.run(self)
File "/usr0/home/zhiqic/anaconda3/lib/python3.7/site-packages/Cython/Distutils/old_build_ext.py", line 186, in run
_build_ext.build_ext.run(self)
File "/usr0/home/zhiqic/anaconda3/lib/python3.7/distutils/command/build_ext.py", line 340, in run
self.build_extensions()
File "/usr0/home/zhiqic/anaconda3/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 580, in build_extensions
build_ext.build_extensions(self)
File "/usr0/home/zhiqic/anaconda3/lib/python3.7/site-packages/Cython/Distutils/old_build_ext.py", line 195, in build_extensions
_build_ext.build_ext.build_extensions(self)
File "/usr0/home/zhiqic/anaconda3/lib/python3.7/distutils/command/build_ext.py", line 449, in build_extensions
self._build_extensions_serial()
File "/usr0/home/zhiqic/anaconda3/lib/python3.7/distutils/command/build_ext.py", line 474, in _build_extensions_serial
self.build_extension(ext)
File "/usr0/home/zhiqic/anaconda3/lib/python3.7/site-packages/setuptools/command/build_ext.py", line 208, in build_extension
_build_ext.build_extension(self, ext)
File "/usr0/home/zhiqic/anaconda3/lib/python3.7/distutils/command/build_ext.py", line 534, in build_extension
depends=ext.depends)
File "/usr0/home/zhiqic/anaconda3/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 423, in unix_wrap_ninja_compile
with_cuda=with_cuda)
File "/usr0/home/zhiqic/anaconda3/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 1140, in _write_ninja_file_and_compile_objects
error_prefix='Error compiling objects for extension')
File "/usr0/home/zhiqic/anaconda3/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 1413, in _run_ninja_build
raise RuntimeError(message)
RuntimeError: Error compiling objects for extension

Had a similar issue.  torch.cuda.is_available() returns true even if your pytorch version doesn't support an older gpu.  So, removing the code from line 32-41 in setup.py worked for me.

@thomasehuang : facing the same issue, any idea?

@bjditto1221 : lines 32-41? or 32 to 46?

Could you try to build the code with CUDA 10.0?  There might be some issues with CUDA 10.2.  We are working on upgrading the code and remove the detectron2 dependencies. Stay tuned.

I managed to fix it following some hint on the internet regarding cuBLAS. Nonetheless, an upgrade is more than welcome.

@bjditto1221 : lines 32-41? or 32 to 46?

@hjraad my bad it is 32-46.  I should also mention this is just a hack to get it to work with cpu only. if you need it to run on gpu you'll need to try the CUDA changes mentioned above.

The codebase has been upgraded. It should work for CUDA10.2 with Pytorch 1.6 now. The detectron2 version is now upgraded to v0.2.1.  Feel free to test the latest release and let us know if anything goes wrong. Thanks!

@bjditto1221 it work for me too, thanks!
cuda: 10.2
pytorch: 1.6.0
python: 3.7.9
gcc: 5.4.0

@bjditto1221 it work for me too, thanks!
cuda: 10.2
pytorch: 1.6.0
python: 3.7.9
gcc: 5.4.0


Distribution not populating as expected

Put this distribution in the CustomOreGenConfig experimental distribution section:
http://pastebin.com/r21wDNLF
Generate the world with seed<PHONE_NUMBER>70531 (enabling test distributions)
Teleport to 49 23 346
According to the distribution parameters there should be an ovoid approximately 10 blocks wide and 30 blocks tall at the destination.  Instead what I get is a mostly, but not completely, empty area.  Largely contiguous, but definitely not an empty ovoid as a "OreDensity = 1" setting should indicate.  There are dozens and dozens of blocks which should--to my eyes--have been replaced by air.
For example, there is a 1 block wide gap like so right in the middle:
https://s28.postimg.org/dipycthm5/2016_12_08_00_35_28.png
Or these three orange wool blocks (manually placed where stone was found):
https://s18.postimg.org/6s43r4549/2016_12_08_00_38_52.png
https://s18.postimg.org/4c2ad9n1l/2016_12_08_00_38_57.png
https://s18.postimg.org/vnxjelrs9/2016_12_08_00_39_06.png
https://s18.postimg.org/il1wvc1k9/2016_12_08_00_39_33.png
https://s18.postimg.org/agtsqlf55/2016_12_08_00_39_52.png
They appear to be 100% contained within the wireframe.

Clouds have their own internal noise field that would cause this. Please check with the OreVolumeNoiseCutoff setting at 0.

Facepalm
Oh god, I feel dumb.  That was it.  I blame it being 1:30 in the morning, but I certainly felt like I was trying everything and not seeing any changes.
Thanks.


Fix regexp filter query

Description
Fix #2796 .
Issues Resolved
#2796
Check List

[x] New functionality includes testing.

[x] All tests pass, including unit test, integration test and doctest

[x] New functionality has been documented.

[x] New functionality has javadoc added
[x] New functionality has user manual doc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

CI was blocked. Triggered its run now.


How to proxy only root?

I have two apps:
8080
8081

and example domain: www.mydomain.com
I would like to send all trafic located to my www.mydomain.com (TO ROOT) http://<IP_ADDRESS>:8080
And rest of trafic to http://<IP_ADDRESS>:8081.
How can I do it?
A tryied:
proxy.register("mydomain.com/", "http://<IP_ADDRESS>:8080");  // only for root "/"
proxy.register("mydomain.com", "http://<IP_ADDRESS>:8081");  // for rest of routes
But it is not working, probably / is rewrited by second register.
Example:
www.mydomain.com -> http://<IP_ADDRESS>:8080 = returns index.html
www.mydomain.com/login -> http://<IP_ADDRESS>:8081 = returns REACT APP
www.mydomain.com/register-> http://<IP_ADDRESS>:8081 = returns REACT APP
www.mydomain.com/list-> http://<IP_ADDRESS>:8081 = returns REACT APP

Thank you for any help.

Using custom resolvers:
require('redbird')(
	{
		port: 80,
		resolvers: [
			// uses the same priority as default resolver, so will be called after default resolver
			function (host, url, req) {
				if (url === '/') {
					return 'http://<IP_ADDRESS>:8081'
				}
				return 'http://<IP_ADDRESS>:8080'
			}
		]
	}
);


Update README.md

Changes include

[ ] Bugfix (non-breaking change that solves an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (change that is not backwards-compatible and/or changes current functionality)
[ ] Tests
[x] Documentation
[ ] Other (for changes that might not fit in any category)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 60.54%. Comparing base (8cfa715) to head (439a903).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #697   +/-   ##
=======================================
  Coverage   60.54%   60.54%
=======================================
  Files          12       12
  Lines        1726     1726
=======================================
  Hits         1045     1045
  Misses        681      681

Flag
Coverage Δ

unittests
60.54% <ø> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


update Debian structure

I would like to make a couple of suggestions.
I want to use the API. The issue here is that the URL is very inconvenient as the path needs to be urlencoded and is generated from the releaseCycle field. Example:
$ curl -sf https://endoflife.date/api/debian/Debian%209%20%22Stretch%22.json | jq

Something like this would be much easier to work with:
curl -sf https://endoflife.date/api/debian/9.json | jq

This means also that you can already understand how the API works, even if you dont know much details about your requesting product. At the moment you have to request the product, urlencode the releaseCycle and generate a new request.
My shorter path would be usable even if you don't know the current release tag. urlencoding is probbaly not a problem with JavaScript. But doing this on a shell is a nightmare. So I split the fields and introduced cycleShortHand for Debian.
Debian 9 is in LTS now. So I removed the 2nd Debian 9 block. But there is also something to discuss. Its not true that there is a non-LTS and a LTS version of a release at the same time. The LTS starts when the support for a release is dropped by the Debian Security Team. The Question is how to handle this? Just add a LTS flag at the end of the official support? Should be EOL date the point when official support is dropped? Or when the LTS is dropped?
An other way could be to add releases like 9-LTS. This is "released" when the official support is dropped.
Here is also another idea for this: https://github.com/endoflife-date/endoflife.date/issues/156
Here was this also a topic: https://github.com/endoflife-date/endoflife.date/pull/456 I have checked it and there is no need to change something on the system to get LTS support. The apt sources are the same as for the regular stable release.
I have added a some other changes: cat /etc/os-release contains more and better information than lsb_release. I have also added the latest version of 6 and 7. also some typos.
Some of my points also hit other products like Ubuntu.

For LTS, I think #156 is a clean and easy approach that works for most projects. (Not those with relative dates)
The "easier URLs" problem is real (one of the reasons I'm still hesitant to move the API from alpha, since any solutions involve a breaking change).

But the current solution has to drop the release names (buster/wheezy) from the text, which are important for Debian. Okay with merging in the intermediate, while we can look for solutions.
Suggestion: How about a nameTemplate field where we can provide a similar template as changeLogTemplate that can use all the release Parameters to label itself? This also works well for Ubuntu I think.
So for Debian, it could look like __RELEASE_CYCLE__ (__CYCLE_SHORTHAND__) __LTSLABEL__ (Where LTSLABEL is (LTS) or ``)

Will wait for a while before merging, in case there are other suggestions since this is a breaking change, but LGTM.
Thanks a lot for your contribution 💯!

The template would be a good solution here. :+1:

are we sure to remove code names ? if it is we also need to make it all ( ubuntu , android , .... ) and it will also lower our visitors from websites which generally people are searching their code names
If we plan to remove these from name it might be better to add a new column named codename that we will add those names so search engines wont effected
@captn3m0 @BiNZGi

See the template plan above, so we'll have it back quickly.

@captn3m0  LTSLABEL -> LTS_LABEL other than that it looks good

#891 is up with initial tempting support to fix these issues. It doesn't work for complicated cases, but the majority is easily covered.


Commit signoff

Would be nice to have a flag or option to enable the Signed-off-by line for the generated commit!

How do you imagine this working? Would you want the bot email to be in the signoff?

I think that would be fine. Or an option to overwrite it.


Load sensitive config credentials via secrets/env variable

The burrow configuration requires SASL credentials (username + password). I don't want to put any credentials into my Kubernetes configmap.
Thus I am wondering if it Is possible to load parts of the configuration (e. g. SASL profile passwords) from environment variables, so that I don't need to put credentials into the configuration? This way I could mount a kubernetes secret as environment variable which then will be loaded on startup by burrow.
    [tls.prd-tls-profile]
    certfile="certificate.crt"
    keyfile="keyfile.key"
    cafile="rootcerts.crt"
    noverify=false
    [sasl.prd-sasl-profile]
    username="myname"
    password="sekrit"
    handshake-first=false

Burrow relies on https://github.com/spf13/viper for config processing, and they fully support environment variables. Support for that already exists in Burrow as well, with the prefix burrow.
So if you want to configure that username and password using environment variables, you should be able to do that by naming them BURROW_SASL_PRD-SASL-PROFILE_USERNAME and BURROW_SASL_PRD-SASL-PROFILE_PASSWORD.
I think. The case rules for env variables in viper seem to say that (they they should be all upper case), and the replacer rules we use substitute '_' for '.'.


feat: add keepalive changes in java client library

This will enable to detect the dead peer tcp connection within (10+10) seconds and start a new one.
Fixes #408 408☕

@igorbernstein2  @kolea2 can you review? I do not think I can add you as reviewers.