Rewrite Import Management API to Rust

Summary
Rewrite APIs to list/add/remove import statements in the Luna module.
Value
Part of double representation API, allows managing used dependencies without editing the text manually.
Specification
Port the original implementation from branch https://github.com/luna/enso/tree/wip/mwu/graph-syntax.
Acceptance Criteria & Test Cases
Test cases are to be rewritten to Rust, as part of this task.

Doble representation has been moved to IDE repository


Clean Dockerfile and bump NodeBB to v0.6.1

I just clean the apt install to avoid many created container.
I define the working dir earlier for next commands simply
And bump version of NodeBB to the latest (v0.6.1)

Thanks! I will take a look at this ASAP.

@bourvill this repo is no longer maintained in favor of https://github.com/NodeBB/docker-builds
For support/updates please go there instead.


check message for aiohttp import error

Can one of the admins verify this patch?

I suppose this narrower exception is technically more correct but just checking for ImportError seems fairly standard. Is there a specific rationale driving this change?


word after "alias ssc='sudo systemctl'; ssc " displayed as error

I have an alias ssc='sudo systemctl', and zsh-syntax-highlighting will display stop in red with ssc stop.
ssc ls will not display an error, and alias ssc=systemctl (without sudo) is also fine.
Bisected to https://github.com/zsh-users/zsh-syntax-highlighting/commit/f3410c5862fc6d89ee3661f7d140e570d6740e8c.

Currently only the first word of the alias's expansion is used.  Fixing this in full generality is probably non-trivial, because alias foo='sudo systemctl &&' is also valid (and furthermore, the expansion of an alias can contain global aliases).  I suppose we could at least hotfix this by allowing the :regular: state for the word after an alias, in order to prevent the false positive you're seeing...  Thoughts?
@blueyed Feel free to join IRC too.

I understand that it uses sudo and then the second word is meant to be a command, from/via sudo's completion?  Is that correctCould the completion system be used to get the type (after using the whole alias expansion)? Foralias foo='sudo systemctl &&'` it would be a command then.
(Sorry, I do nothing about the internals here)

This is closer, but still wrong.
diff --git a/highlighters/main/main-highlighter.zsh b/highlighters/main/main-highlighter.zsh
index 455c21f..ec0979c 100644
--- a/highlighters/main/main-highlighter.zsh
+++ b/highlighters/main/main-highlighter.zsh
@@ -69,6 +69,7 @@ _zsh_highlight_highlighter_main_predicate()

 # Helper to deal with tokens crossing line boundaries.
 _zsh_highlight_main_add_region_highlight() {
+  (( skip_words == 0 )) || return 0
   integer start=$1 end=$2
   shift 2

@@ -395,14 +396,19 @@ _zsh_highlight_main_highlighter_highlight_list()
   # Processing buffer
   local proc_buf="$buf"
   local -a args
+  # How many words to skip (these words are the result of alias expansion and are not added to region_highlight)
+  integer skip_words=0
   if [[ $zsyh_user_options[interactivecomments] == on ]]; then
     args=(${(zZ+c+)buf})
   else
     args=(${(z)buf})
   fi
-  for arg in $args; do
+  while (( ${+args[1]} )); do
+    arg=$args[1]
+    shift args
     # Save an unmunged copy of the current word.
     arg_raw="$arg"
+    (( skip_words <= 0 )) || (( --skip_words ))

     # Initialize this_word and next_word.
     if (( in_redirection == 0 )); then
@@ -428,6 +434,7 @@ _zsh_highlight_main_highlighter_highlight_list()
     fi

     # Compute the new $start_pos and $end_pos, skipping over whitespace in $buf.
+    if (( skip_words == 0 )); then
     start_pos=$end_pos
     if [[ $arg == ';' ]] ; then
       # We're looking for either a semicolon or a newline, whichever comes
@@ -462,6 +469,7 @@ _zsh_highlight_main_highlighter_highlight_list()
       ((start_pos+=offset))
       ((end_pos=$start_pos+${#arg}))
     fi
+    fi

     # Compute the new $proc_buf. We advance it
     # (chop off characters from the beginning)
@@ -516,6 +524,8 @@ _zsh_highlight_main_highlighter_highlight_list()
             # Avoid looping forever on alias a=b b=c c=b, but allow alias foo='foo bar'
             [[ $arg == $reply[1] ]] && break
             arg=$reply[1]
+            args[1,0]=( "${(@)reply[2,-1]}" )
+            (( skip_words += $#reply - 1 ))
             if (( $+seen_arg[$arg] )); then
               res=none
               break

This is happening for me as well -- seemed to have started very recently too (within the past week or so).

Fixed in cb8c736 #556.


aio_whois_domain() running infinitely

While using the library to perform mass WHOIS lookups, I found that the aio_whois_domain() function is not respecting the timeout parameter and running the query infinitely.
Example query performed:
loop = asyncio.get_event_loop()
result = loop.run_until_complete(asyncwhois.aio_whois_domain("1stchoicebankca.com"))

As per the source code, default timeout is set to 10 seconds, but surely its taking more than that.

Hi Prerak,
Thanks for posting. I briefly looked into this on my end and things seem to be good as far as respecting the timeout parameter:

With the domain you mentioned:

I will dig a little deeper though to be sure. In the meantime, here a few questions that can help me out:

Does the query still return; it just seems to be taking longer than the timeout value? or does it actually hang infinitely?
Are you using a proxy?

When you say "mass lookups", are you using anything special to run multiple Coroutines? e.g. asyncio.gather(*list_of_whois_lookups)

Hi pogzyb,
Please find the answers to your query below:

Does the query still return; it just seems to be taking longer than the timeout value? or does it actually hang infinitely?
No, the query does not return, it just hangs indefinitely. I waited more than 5 minutes for the query to return a value. Anyhow, it should respect the configured timeout.

Are you using a proxy?
Yes, a proxy is being used. Without it, I am also not facing any issues. But the environment in which this needs to be executed requires a proxy connection.

Yes, my internet connectivity is not a problem. Apart from a handful of these domains (as I mentioned before), all others are giving results in the expected time.

When you say "mass lookups", are you using anything special to run multiple Coroutines?
Yes, asyncio.gather() is being used.

@masquerad3r Thanks for the info!
I don't have a great answer right now, but if your query is hanging infinitely, then this issue may be related: #34. PR #35 was created and merged to address this for .tk domains, but hasn't yet been included in a release, so you'll need to pip install from the master branch.
It's possible there are other TLD parsers that are causing the same issue. If you run into this issue again please send me a domain that's causing the issue and I will look into it thoroughly.

@masquerad3r v1.0.1 is now available and contains the fix for .tk domains, which may have been the underlying issue. I'll keep this open in case the problem persists and/or other issues around "infinitely running" queries/parsing are identified.
Thanks!


test: [M3-7500] - Add tests for Parent/Child Users & Grants page enhancements

Description 📝
Add regression tests to check enhancements in users landing page.
Major Changes 🔄

Add new tests to check the Users & Grants page.
Move some existing test from user permission spec.

How to test 🧪
yarn cy:run -s "cypress/e2e/core/account/users-landing-page.spec.ts"

Can we merge in develop / rebase this PR with develop? I think the Notistack/Snackbar changes might affect these tests


fragment id assignment issue

There was a static framelayout id that was assigned repetitively. I need a fix for that.

Found the resource and it was fixed easily: http://stackoverflow.com/questions/8460680/how-can-i-assign-an-id-to-a-view-programmatically


Implement clean subcommand

Implement clean subcommand.
It should cleans standard workdir (target) at least.

This can be done by
commandunit --clean none


Generated site has localhost:1313 as the host for all static files

Perhaps I am doing something wrong, but the generated website seems to have a 'localhost:1313' prefix for all static files.
eg: <meta name="twitter:image" content="localhost:1313img/portfolio.jpg">
PS: Amazing theme; thanks! 🙂

Did you change the baseURL in config.toml?
Thank you!

Ah, 🤦♂
That was it. Thanks!


Column name: Registered container instances (not Registered containers)

Hi @keidarcy, Great tool!
When looking at clusters, column reads Registered containers, while it should read Registered container instances to (at least) match the AWS console.

Thank you!

@yriahi Hi, thank you for using. Please check the latest version

@keidarcy looks good! Thank you for making the change so quickly.
There can be more than one instance, if/when able; it'll be good as plural "Registered container instances".

Thank you. Will fix in next update.


cron::job doesn't support Ubuntu Xenial

Xenial switched to Systemd, so cron::job fails on Xenial
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Function Call, I cannot install Upstart backed crons on machines without Upstart

Heh. Yea I guess the equivalent would be "oneshot" ? https://www.freedesktop.org/software/systemd/man/systemd.service.html


How to use SAML 2.0 auth with this package?

Describe the feature request?
How to use SAML 2.0 auth with this package?
New or Affected Resource(s)
How to use SAML 2.0 auth with this package?
Provide a documentation link
No response
Additional Information?
No response

This SDK is built around OAuth2 + OIDC, and works exclusively with Bearer tokens. So it isn't compatible with SAML.

is there any Okta SDK that supports Okta SAML? or any example code to integrate SAML in Swift?

is there any Okta SDK that supports Okta SAML? or any example code to integrate SAML in Swift?

Unfortunately no, we don't have any code samples or other SDKs that support SAML use-cases.


Mixed output files result in very long play

Basically a .txt phrase file that results in 5m play, should also result in 5m play when mixed.

Have not observed in >=<IP_ADDRESS>...will close if not seen again.

Not in typer-cli branch either - closing.


Fix issue with order of column names.

Appears that order of dtypes.keys() is not guaranteed. Hard coded the
names array to resolve column mismatch.

Great point, that makes sense that dict keys are unordered. Merging pull request.


About the RadarScene dataset.

So there is no z coordinate for each point within the data set, right? or you just didn't use it?

According to the description of the dataset, https://radar-scenes.com/dataset/structure/, the z coordinates was not provided.

Got it, thanks for reply.


Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource

I did add middleware AccessControlTest and add config/middleware
class AccessControlTest implements MiddlewareInterface
{
    public function process(Request $request, callable $next) : Response
    {
        // 允许uri以 /api 开头的地址跨域访问
        if (strpos($request->path(), '/api') === 0) {
            // 如果是options请求，不处理业务
            if ($request->method() == 'OPTIONS') {
                $response = response('');
            } else {
                $response = $next($request);
            }
            $response->withHeaders([
                'Access-Control-Allow-Origin' => '*',
                'Access-Control-Allow-Headers' => '*',
                'Access-Control-Allow-Methods' => 'GET,POST,PUT,DELETE,OPTIONS',
                'Content-Length' => '0',
                // 'Access-Control-Allow-Headers' => 'Content-Type,Authorization,X-Requested-With,Accept,Origin',
            ]);
            var_dump($response);
        } else {
            $response = $next($request);
        }
        return $response;
    }
}

but still got error
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://admin.yhcmutiara24.my.id/api/siswa?page=1. (Reason: Multiple CORS header ‘Access-Control-Allow-Origin’ not allowed).

It works for me.

Reason: Multiple CORS header ‘Access-Control-Allow-Origin’ not allowed

It looks like your app returned two Access-Control-Allow-Origin headers .


Footer

Add in a footer to homepage along lines of powered by “Together We Listen” with links to the TWL splash page and this right here github.
For the NYPL instance, update the footer with the required privacy policy, etc.

Please add "Contact Us<EMAIL_ADDRESS>to the NYPL Project footer.
Please add "Together We Listen" to the defalt footer.


what should we canonically link to as documentation for this crate?

we have rustdoc and the book. this is really not a library that folks would use api docs for. should we make the canonical doc link (on cratesio) to the homepage?

I prefer to just "forget" the api docs on homepage, if it's really needed, how about add it into the contributing docs as [dev docs](https://docs.rs/...)

solved by the latest release


promu build -v . fails

promu build -v . fails.

cd %GOPATH%\github.com\martinlindhe\wmi_exporter
promu build -v .
Using config file: .promu.yml
Running command: build [-v .]
!! binary . not found in config
validation of given binary names for build command failed
github.com/prometheus/promu/cmd.runBuild
/src/github.com/prometheus/promu/cmd/build.go:137
github.com/prometheus/promu/cmd.Execute
/src/github.com/prometheus/promu/cmd/promu.go:125
main.main
/src/github.com/prometheus/promu/main.go:20
runtime.main
c:/go/src/runtime/proc.go:203
runtime.goexit
c:/go/src/runtime/asm_amd64.s:1357

Seems similar to https://github.com/martinlindhe/wmi_exporter/issues/119

Have you set GOOS=windows? Try omitting the local dir in the promu command.
E.G. GOOS=windows promu build -v


[Feature Request] Add a feature to export and import installed apps list

Say, I currently I've many apps installed via Chocolatey now if I migrate to new OS have to install them one by one, but if I could import the list of apps, I could just load it in the new OS and all will be installed at once.

@Cyberavater Thanks for reaching out!
it is already possible to export a list of packages from within Chocolatey GUI, this is documented here:
https://docs.chocolatey.org/en-us/chocolatey-gui/user-interface/main-window/actions/export
And there is already an open issue for allowing to import this file here:
https://github.com/chocolatey/ChocolateyGUI/issues/248
As such, I am going to go ahead and close out this issue as a duplicate.

Thanks, will be waiting for the import button.


set connectTimeout from Init

Could you add a change file in .changes directory?

Could you add a change file in .changes directory?

Yes.

OK


Add logging of slow events, track event processing (dispatching) time as metric

This PR introduces a (hopefully) low-overhead method of measuring event process time, albeit only on CPUs that support it (run grep tsc /proc/cpuinfo to find out).
It also tracks the time it takes to process events in a histogram. Events that take longer than 1ms will trigger a warn!ing.
If there are long running consensus events, this should root them out via the logs.

bors r+


add ORDO xref to cornea plana

this is a bit of an unusual case:

we obsoleted congenital corena plana but Gioconda asked that it be added back as an xref for cornea plana, so I added the ORDO xref and pointed to this term on the obsoleted term
close #7573

done
at some point we'll sync all of these definitions, right? so we won't have to add them manually?

I think there are still general discussions to sync definitions. Is the work in this ticket a good use case/example of this issue?

yes - this is a case where there was no definition and I added the ORDO def
If you would like examples of where I update the definition that comes from ORDO, I can make a note next time I come across one


Can't resolve fs / fs in normalize-file.js ?

This is such a cool project! But I can't get it to work. Cloned it once via gatsby cli & then tried a second time via git clone + repo link. Apart from lots of warnings during yarn, gatsby develop gives me:
 ERROR  Failed to compile with 2 errors                                                                                5:06:13 PM

This dependency was not found:

* fs in ./node_modules/<EMAIL_ADDRESS>./node_modules/remark-mdx/node_modules/@babel/core/lib/transformation/normal
ize-file.js

To install it, you can run: npm install --save fs

 ERROR #98123  WEBPACK

Generating development JavaScript bundle failed

Can't resolve 'fs' in '/Users/jester/projects/test_projects/gatsby-mdx-netlify-starter/node_modules/@mdx-js/mdx/node_modules/@babel/core/lib/transformation'

File: node_modules/<EMAIL_ADDRESS>

 ERROR #98123  WEBPACK

Generating development JavaScript bundle failed

Can't resolve 'fs' in '/Users/jester/projects/test_projects/gatsby-mdx-netlify-starter/node_modules/remark-mdx/node_modules/@babel/core/lib/transformation'

File<EMAIL_ADDRESS>
failed Building development bundle - 54.046s

Tried fixing it by yarn add fs, but didn't work. I'm not sure what to do. Any ideas?

Same issue here. Did you close the issue because you solved it? How? Could this be a solution?

Tried adding
// gatsby-node.js
exports.onCreateWebpackConfig = ({ actions }) => {
  actions.setWebpackConfig({
    node: {
      fs: 'empty'
    }
  })
}

No joy, any luck you guys @leafac @jesterbeaver or any advice from @renvrant ? Could we re-open this otherwise?
Cheers

Thanks for the quick response @mlynam !
This seems resolved with your addition plus the similar code for gatsby-node.js
Submitted PR #8 feel free to merge or close if I'm missing some valid reason this wasn't in the repo before @renvrant

@mysterybear you shouldn't need it in the root node config unless there is another unmentioned dependency running around.

@mysterybear: The progress I made on the issue is that I think I now understand why it occurs in the first place. In this starter there’s code like this that requires MDX. This code is being interpreted as if it were running on the browser. Of course, this is Gatsby we’re talking about, and Gatsby precompiles stuff during build time to generate a static site. But still, the code behaves as if it were interpreted in the browser. The problem is that MDX seems to use fs, child_process, and other things that you only find in Node.js, not on the browser.
The solution seems to be to tell webpack (which Gatsby is using under the hood) to provide an empty implementation of those libraries, only to get MDX going. (This isn’t just an issue with MDX; it also applies to other libraries that may be using things from Node.js.)

I can shed more light on the problem. Gatsby has 2 major build steps.
Step 1 runs entirely in node and is responsible for validating schema, running queries, loading data, performing SSR to generate the static elements and so on.
During step 2, Gatsby builds the site with a browser config because it expects there may be some elements that are intended to run in the browser (like dynamically loaded data at runtime, or maybe a netlify admin application!). This 2nd stage is what dies if you included a gatsby symbol inside some component that gatsby doesn't handle during Stage 1. In the case of this starter, any component you expose to your CMS like previews, mdx shortcodes and editors will complain if you don't stub those node modules inside your netlify plugin config.

@mysterybear you shouldn't need it in the root node config unless there is another unmentioned dependency running around.

Seems to be. If I remove it from gatsby-node.js, I get the same problem:
failed Building production JavaScript and CSS bundles - 116.667s
 ERROR #98123  WEBPACK

Generating JavaScript bundles failed

Can't resolve 'fs' in 'node_modules/@mdx-js/mdx/node_modules/@babel/core/lib/transformation'

File: node_modules/<EMAIL_ADDRESS>

Interesting. Thanks for the correction!


Fix CRD validation failure due to the null field(s)

User or ui may create or update CRs with null values rather than initialized values,
so it leads to the validation failure. To avoid the failures and avoid breaking the
backward compatibility , add +nullable to the CRD fields.
Signed-off-by: Derek Su<EMAIL_ADDRESS>

I'm fine with this approach.
However, we had a PR to upgrade the old CRs to initiate these fields.
Should we reconsider to use this approach and remove the upgrade code?

Probably we should keep both for 1.3.0. One is for the upgrade to make things right, but this PR is actually for the fresh install for backward compatibility at the moment. WDYT?

I'm fine. I just think that the mutating admission webhook could achieve this as well, i.e., initiate the default value if it's null.

I'm fine. I just think that the mutating admission webhook could achieve this as well, i.e., initiate the default value if it's null.

It seems reasonable for me by using mutation webhook. @derekbit WDYT?

Yes, it's reasonable. I'll use mutation webhook and to see if there is any prob.

Actually, I am confused about the recent CRD-related PRs, especially for the validation part.

Is the validation handled by k8s rather than the webhook we introduced?
Will there be similar issues for the old (v1beta1) CRs?
Jenting mentioned one similar issue in [#1189 (comment)]
(https://github.com/longhorn/longhorn-manager/pull/1189#issuecomment-1011542445). Can this PR fix the issue he mentioned?

Yes. The validation is handled by k8s instead of the webhook. Because v1beta1 CRs is still schema-less, we won't encounter this issue.
The APIs do not validate the parameters now. For example, the node.disks.tags should not be null, but ui or user may call the APIs with null values. Thus, the PR aims to the backward compatibility instead of fixing something.

Jenting mentioned one similar issue in [#1189 (comment)]
(https://github.com/longhorn/longhorn-manager/pull/1189#issuecomment-1011542445). Can this PR fix the issue he mentioned?

Right. nullable also fixes the the issue @jenting mentioned. I cannot make sure if null values is good, so I still keep the fixUpxxxx.

I am thinking if you can briefly summarize the materials/links/docs you referred for the CRD API version & webhook PRs. I am afraid of missing any conversions or principles for this part. If this is time consuming, you can ignore it.

main context: https://github.com/longhorn/longhorn/issues/3265.
Conversion webhook document: https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/
Backward compatibility concern: https://github.com/longhorn/longhorn/issues/3538

It seems reasonable for me by using mutation webhook. @derekbit WDYT?

@jenting @innobead
Looks we need another ticket for this, right?
It seems not in the scope of this issue and PR.

@derekbit actually I would prefer fixing in this PR or you still need to refactor it later when moving to the mutation webhooks. Right?

Sure. I can fix in this ticket. Just a little confused about the purpose of the PR's scope.

I'm okay to use this PR/issue.
From my perspective, I think the considering sequence to handles the CRs are:

Try to fix it in the CRD structural schema or fix it in the webhook server. Such as null field, we could add nullable in theCRD structural schema or use mutating admission webhook to initiate the field which is null.
If the above not possible, fix it in the longhorn manager.

@jenting @innobead
We still need the fixUpxxx in the upgrade path.
While upgrading the longhorn-manager, longhorn-manager calls UpdateStatus to update nodes' conditions.
The UpdateStatus complains
err=Node.longhorn.io \"rancher50-master\" is invalid: spec.disks.default-disk-745ff2be8d312b52.tags: Invalid value: \"null\": spec.disks.default-disk-745ff2be8d312b52.tags in body must be of type array: \"null\"",
because the mutating webhook does not handle UpdateStatus and only handle Update, Create, Delete and Connect.
The fixUpxxx in the update path can be simpler than before. Just List the old objects and  the Update, because the mutating webhook can help update the null values.

@jenting @innobead We still need the fixUpxxx in the upgrade path.
While upgrading the longhorn-manager, node-controller calls UpdateStatus to update nodes' conditions.
The UpdateStatus complains err=Node.longhorn.io \"rancher50-master\" is invalid: spec.disks.default-disk-745ff2be8d312b52.tags: Invalid value: \"null\": spec.disks.default-disk-745ff2be8d312b52.tags in body must be of type array: \"null\"", because the mutating webhook does not handle UpdateStatus and only handle Update, Create, Delete and Connect.
The fixUpxxx in the update path can be simpler than before. Just List the old objects and then call Update, because the mutating webhook can help fix the null values.

@derekbit will try to add subresources to the mutation config but update later.

I added the subresource node/status in the mutating webhook. Then, modified the node Spec in the node mutating logic while handling UpdateStatus, the error still happened.  The modify of the Spec is not accepted by Kubernetes.
curl -H "Authorization: Bearer  $<TOKEN>"  https://localhost:6443/apis/longhorn.io/v1beta2/namespaces/longhorn-system/nodes/rancher50-master/status -d '{"status": {"region": "Hello"}}' -H 'Content-Type: application/merge-patch+json' -X PATCH -k

{
  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {

  },
  "status": "Failure",
  "message": "Node.longhorn.io \"rancher50-master\" is invalid: spec.disks.default-disk-745ff2be8d312b52.tags: Invalid value: \"null\": spec.disks.default-disk-745ff2be8d312b52.tags in body must be of type array: \"null\"",
  "reason": "Invalid",
  "details": {
    "name": "rancher50-master",
    "group": "longhorn.io",
    "kind": "Node",
    "causes": [
      {
        "reason": "FieldValueInvalid",
        "message": "Invalid value: \"null\": spec.disks.default-disk-745ff2be8d312b52.tags in body must be of type array: \"null\"",
        "field": "spec.disks.default-disk-745ff2be8d312b52.tags"
      }
    ]
  },
  "code": 422

In summary, Spec and Status cannot be modified simultaneously.
Thus, we still need the fixUpxxx logic to fix the old CRs. The purpose of the mutating webhook is to fix the null values from different interfaces.

In this commit, the fixing up/mutating invalid values logics (fixUpxxx) are moved to the mutating webhook.
Thus, the //+nullable in CRD' Spec can be removed.
The fixUpxxx functions cannot be removed, because the node controller updates the CR.status.conditions after upgrading the longhorn-manager. The UpdateStatus fails if CR' Spec has invalid values.
But we can simplify the fixUpxxx functions. Just read the old CRs and update them. The mutating webhook will fix up the invalid values.
cc. @innobead, @jenting, @shuo-wu

I still prefer to retain the field checks in v1beta1 upgrade/fixup functions. Otherwise, if one manager pod fails at one CR update, the next manager pod needs to walk through all of the CRs one more time. e.g., there are 100 existing/old CRs in total, the 1st manager pod fails at updating the 99th CRs, then the pod will be restarted and re-update all of the 100 CRs blindly.

Yes, your concern is valid. I will add it back.

Actually, the checks in the v1beta1 upgrade/fixup functions are not mutexed with the checks in the mutation hooks. IMO, the checks in the mutation hooks are more like general steps that contain not only the v1beta1 related fields but also some other nullable fields.

Correct. The main purpose of the checks in the mutation hooks aims to fix the invalid values from different interfaces.

@derekbit Please also update longhorn/longhorn manfiests.


has_snapshot_children and has_one on model fails if nil

if you have in your has_snapshot_children
 something:          {
       record:        instance.something,
       delete_method: ->(item) { item.release! }
     },

and for your model
has_one :something
if fails if instance.something = nil
for for rails has_one is 0 or 1 item. so should not fail on nil

solved it this way for now
but not sure how the restore will react
record:        instance.something ? instance.something : {},

Yeah your totally right. Nil should be an accepted value. I can add this soon or will accept a PR if your willing

This is now fixed in 1aa90e6

v0.2.1 is now released which contains this fix.


Editing Light Level

Hey i'm looking for a way to edit light level (of Enlightened Fused Quartz/Glass,Powered Light and Light)  i've alreadry try few things so i decide to try to remove their recipe and i'm still unsuccess ...
Could you help me please to edit this ?

There is no configuration for the amount of light those blocks give off. Why would you want to reduce it?
For recipes, those are in the alloy smelter recipe config file (for quartz) and in the machine recipe file (for the lights). There are instructions on how to disable recipes in those files.

I work on a modpack and i 'm doing an overall of modded basics goal so my first goal is to create a progression in lightning device . I already remove/rework vanilla light source and some modded .

Ok, then I recommend you change the recipes for the "light" (LL15) to be more expensive, the "powered light" (LL15 + AOE) way more expensive or disabled or use a huge amount of power. The "wireless light" may either stay or go, it's recipe already is non-trivial.
The other light sources, Enlightened Quartz/Glass and Painted Glowstone, already take one Glowstone block for each and have the same LL. So by limiting the player's access to Glowstone, they should already be regulated. Nearly the same goes for Glowgas, but there you get a flowing liquid which you can stretch out over quite an area if you know what you're doing.
Fluid conduits give off the same light level as the liquid inside. But because you can fill less conduits than you could have liquid blocks if you let the liquid flow, I think that's ok. (Also, it can be disabled, "fluidConduitDynamicLighting".)
I'm a bit concerned about Conduit Facades. Those mimic the light level of the block they are painted with. So with a single glowing block and a good supply of sand, gravel and clay, you could light up the whole world.

Actually i can't change any light level on EnderIO that's why i'm asking ,p
I've already edit lava glowstone ect... light level so i think you can paint as many glowstone as you want it will not give you light ^^
For conduit lighting i've already ask for this config that's why this config appear in last version

bump ?


Settings are missing when app is removed from background

On Xamarin.Forms Android (5.1,6.0,7.0) When saving the information, it works great. However, if you close the app and clear the Android stack of apps running on background the settings values are missing.
Note: On iOS it works very good.
Plugin version 3.1.1
Any idea what the issue could be?
Regards,
Victor

All values are store immediately into shared preferences. Has worked perfect for 6 years with 1+ million installs here... can you share code at all that you are using?
Is it redeploy via debugging? Perhaps you have clear values on?

Hello @jamesmontemagno , that is also why it is really weird that is not working for me on Android only.
This is the code I'm using:
{
    public static class Settings
    {
        private const string RememberUserKey = "RU_Key_1";
        private const string UserPasswordKey = "UP_Key_1";
        private const string UserEmailKey = "UE_Key_1";

        private static readonly bool RememberUserDefault = false;
        private static readonly string UserPassworDefault = string.Empty;
        private static readonly string UserEmailDefault = string.Empty;

        private static ISettings AppSettings
        {
            get {  return CrossSettings.Current; }
        }

        public static bool RememberUser
        {
            get { return AppSettings.GetValueOrDefault(RememberUserKey, RememberUserDefault); }
            set { AppSettings.AddOrUpdateValue(RememberUserKey, value); }
        }

        public static string UserPassword
        {
            get { return AppSettings.GetValueOrDefault(UserPasswordKey, UserPassworDefault);}
            set { AppSettings.AddOrUpdateValue(UserPasswordKey, value);}
        }

        public static string UserEmail
        {
            get { return AppSettings.GetValueOrDefault(UserEmailKey, UserEmailDefault); }
            set { AppSettings.AddOrUpdateValue(UserEmailKey, value); }
        }

    }
}```

However, when I retrieve the values on the ViewModel RememberMe is always false:

ObjectUser.RememberUser = Settings.RememberUser;
ObjectUser.Email = RememberUser ? Settings.UserEmail : string.Empty;
ObjectUser.Password = RememberUser ? Settings.UserPassword : string.Empty;

App1.zip
This code works absolutely perfect. No issues at all.


how to use it in python

Hi thanks for the great work. Any suggestion on how I can use these .bin and .param files in python ncnn. I want to use it on jetson nano.  thanks

Please check the ncnn/python site.


TiCDC tests are run in groups, two tests per group

TiCDC tests are run in groups, two tests per group.

/hold
Never merge it

/unhold
Ready for review.


Bump jenkins lib version to 1.5.3 and set autoPublish to true

Signed-off-by: Sayali Gaikawad<EMAIL_ADDRESS>Description
The 1.5.3 version adds the missing JAVA_HOME args to docker container. Related PR: https://github.com/opensearch-project/opensearch-build-libraries/pull/105
Also setting autoPublish for maven to true since we tested this for last opensearch distribution release.
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] 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.

Hi @reta and @dblock The publishRelease option is set to false, right now. Do you want me to set it to true?
This will publish the generated draft release on GitHub so we do not have to manually do it. Lmk.
Thanks!

Hi @reta ,
I'll recreate the tag. Question: Should it be 0.1.0 or release-0.1.0?

Hi @reta ,
I'll recreate the tag. Question: Should it be 0.1.0 or release-0.1.0?

Thanks @gaiksaya , I would prefer 0.1.0, for some reasons previous build scripts triggered by release-x.y.x tag [1] :(, not sure why but @peterzhuamazon could spot some light here
[1] https://github.com/opensearch-project/opensearch-testcontainers/

Going ahead with 0.1.0. 🤞

Spring-data-opensearch is released: https://aws.oss.sonatype.org/content/repositories/releases/org/opensearch/client/
https://build.ci.opensearch.org/job/spring-data-opensearch-release/8/console

Hi @reta ,
Can you verify and fix the releases here: https://github.com/opensearch-project/spring-data-opensearch/releases?
You can convert the draft one to publish. I'll create another PR to add documentation and toggle the autoPublish release to true.
Thanks!


feat: serialization methods

Closes #95.
This ended up being a lot harder than I expected, mostly due to the nested structure of the preprocessor and its attributes, plus the mixture of basic data types and DataArrays. The only workable solution I could come up was to add xarray-datatree and zarr as optional dependencies, and build the whole structure as a tree. This was my first foray into DataTree which is super flexible and worked great for this task. I bailed on netcdf only because there are serious limitations with representing any sort of nested structures in attributes, i.e. dicts.

Hey, thanks Sam, that's really awesome! I've only skimmed through it, but it looks super clean. I'll try to get the CI up and running, and then I'll take a closer look at the code this evening. I haven't used `xarray-datatree before either, but it sounds like the perfect application.
Just as a side note, I'll change the target branch of the PR to develop so we can merge both this and #102 into main at the same time. Otherwise, we'd have two releases back-to-back.

Perfect, thanks, didn't notice the main/develop gitflow.

For reference, here's the DataTree for a serialized EOF model.
At most of the branches, we could probably get by with less deep nesting. But there were a few cases where I think the only safe route was to make each serialized attribute, or even individual values (usually coords) within a dict-like attribute, be isolated datasets/nodes.
The rotator classes are even heavier since we have to serialize the original model as well, but that was quite easy to add with DataTree.
DataTree('None', parent=None)
│   Dimensions:             (feature: 20, mode: 2, sample: 25)
│   Coordinates:
│     * feature             (feature) int64 0 1 2 3 4 5 6 7 ... 13 14 15 16 17 18 19
│     * mode                (mode) int64 1 2
│     * sample              (sample) datetime64[ns] 2001-01-01 ... 2025-01-01
│   Data variables:
│       input_data          float64 nan
│       components          (feature, mode) float64 0.1595 -0.02274 ... -0.1336
│       scores              (sample, mode) float64 -1.006 -5.303 ... -2.691 11.94
│       norms               (mode) float64 33.44 24.17
│       explained_variance  (mode) float64 46.58 24.35
│       total_variance      float64 195.8
│   Attributes:
│       params:   {'n_modes': 2, 'center': True, 'standardize': False, 'use_cosla...
└── DataTree('preprocessor')
    │   Dimensions:  ()
    │   Data variables:
    │       *empty*
    │   Attributes:
    │       params:   {'feature_name': 'feature', 'return_list': False, 'sample_name'...
    │       n_data:   1
    ├── DataTree('scaler')
    │   └── DataTree('0')
    │       │   Dimensions:  ()
    │       │   Data variables:
    │       │       *empty*
    │       │   Attributes:
    │       │       params:           {'with_center': True, 'with_coslat': False, 'with_std':...
    │       │       mean_:            _is_node
    │       │       std_:             _is_node
    │       │       coslat_weights_:  _is_node
    │       │       weights_:         _is_node
    │       ├── DataTree('mean_')
    │       │       Dimensions:  (lat: 5, lon: 4)
    │       │       Coordinates:
    │       │         * lat      (lat) float64 20.0 30.0 40.0 50.0 60.0
    │       │         * lon      (lon) float64 -10.0 0.0 10.0 20.0
    │       │       Data variables:
    │       │           t2m      (lat, lon) float64 4.711 4.587 5.164 4.597 ... 4.126 4.879 4.056
    │       │       Attributes:
    │       │           multiindexes:  {}
    │       │           name_map:      {'mean_': 't2m'}
    │       ├── DataTree('std_')
    │       │       Dimensions:  ()
    │       │       Data variables:
    │       │           std_     float64 nan
    │       │       Attributes:
    │       │           multiindexes:  {}
    │       │           name_map:      {'std_': 'std_'}
    │       ├── DataTree('coslat_weights_')
    │       │       Dimensions:          ()
    │       │       Data variables:
    │       │           coslat_weights_  float64 nan
    │       │       Attributes:
    │       │           multiindexes:  {}
    │       │           name_map:      {'coslat_weights_': 'coslat_weights_'}
    │       └── DataTree('weights_')
    │               Dimensions:   (lon: 4, lat: 5)
    │               Coordinates:
    │                 * lon       (lon) float64 -10.0 0.0 10.0 20.0
    │                 * lat       (lat) float64 20.0 30.0 40.0 50.0 60.0
    │               Data variables:
    │                   weights_  (lon, lat) float64 1.0 1.0 1.0 1.0 1.0 1.0 ... 1.0 1.0 1.0 1.0 1.0
    │               Attributes:
    │                   multiindexes:  {}
    │                   name_map:      {'weights_': 'weights_'}
    ├── DataTree('renamer')
    │   └── DataTree('0')
    │           Dimensions:  ()
    │           Data variables:
    │               *empty*
    │           Attributes:
    │               params:       {'base': 'dim', 'start': 0}
    │               dim_mapping:  {'time': 'dim0', 'lat': 'dim1', 'lon': 'dim2'}
    ├── DataTree('preconverter')
    │   └── DataTree('0')
    │           Dimensions:  ()
    │           Data variables:
    │               *empty*
    │           Attributes:
    │               params:                 {}
    │               modified_dimensions:    []
    │               coords_from_fit:        {}
    │               coords_from_transform:  {}
    ├── DataTree('stacker')
    │   └── DataTree('0')
    │       │   Dimensions:  ()
    │       │   Data variables:
    │       │       *empty*
    │       │   Attributes:
    │       │       params:        {'feature_name': 'feature', 'sample_name': 'sample'}
    │       │       dims_in:       ('dim0', 'dim1', 'dim2')
    │       │       dims_out:      ('sample', 'feature')
    │       │       dims_mapping:  {'sample': ('dim0',), 'feature': ('dim1', 'dim2')}
    │       │       coords_in:     _is_tree
    │       │       coords_out:    _is_tree
    │       ├── DataTree('coords_in')
    │       │   ├── DataTree('dim0')
    │       │   │       Dimensions:  (dim0: 25)
    │       │   │       Coordinates:
    │       │   │         * dim0     (dim0) datetime64[ns] 2001-01-01 2002-01-01 ... 2025-01-01
    │       │   │       Data variables:
    │       │   │           *empty*
    │       │   │       Attributes:
    │       │   │           multiindexes:  {}
    │       │   │           name_map:      {'dim0': 'dim0'}
    │       │   ├── DataTree('dim1')
    │       │   │       Dimensions:  (dim1: 5)
    │       │   │       Coordinates:
    │       │   │         * dim1     (dim1) float64 20.0 30.0 40.0 50.0 60.0
    │       │   │       Data variables:
    │       │   │           *empty*
    │       │   │       Attributes:
    │       │   │           multiindexes:  {}
    │       │   │           name_map:      {'dim1': 'dim1'}
    │       │   └── DataTree('dim2')
    │       │           Dimensions:  (dim2: 4)
    │       │           Coordinates:
    │       │             * dim2     (dim2) float64 -10.0 0.0 10.0 20.0
    │       │           Data variables:
    │       │               *empty*
    │       │           Attributes:
    │       │               multiindexes:  {}
    │       │               name_map:      {'dim2': 'dim2'}
    │       └── DataTree('coords_out')
    │           ├── DataTree('sample')
    │           │       Dimensions:  (sample: 25)
    │           │       Coordinates:
    │           │         * sample   (sample) datetime64[ns] 2001-01-01 2002-01-01 ... 2025-01-01
    │           │       Data variables:
    │           │           *empty*
    │           │       Attributes:
    │           │           multiindexes:  {}
    │           │           name_map:      {'sample': 'sample'}
    │           └── DataTree('feature')
    │                   Dimensions:  (feature: 20)
    │                   Coordinates:
    │                       dim1     (feature) float64 20.0 20.0 20.0 20.0 30.0 ... 60.0 60.0 60.0 60.0
    │                       dim2     (feature) float64 -10.0 0.0 10.0 20.0 -10.0 ... -10.0 0.0 10.0 20.0
    │                   Dimensions without coordinates: feature
    │                   Data variables:
    │                       *empty*
    │                   Attributes:
    │                       multiindexes:  {'feature': ['dim1', 'dim2']}
    │                       name_map:      {'feature': 'feature'}
    ├── DataTree('postconverter')
    │   └── DataTree('0')
    │       │   Dimensions:  ()
    │       │   Data variables:
    │       │       *empty*
    │       │   Attributes:
    │       │       params:                 {}
    │       │       modified_dimensions:    ['feature']
    │       │       coords_from_fit:        _is_tree
    │       │       coords_from_transform:  _is_tree
    │       ├── DataTree('coords_from_fit')
    │       │   └── DataTree('feature')
    │       │           Dimensions:  (feature: 20)
    │       │           Coordinates:
    │       │               dim1     (feature) float64 20.0 20.0 20.0 20.0 30.0 ... 60.0 60.0 60.0 60.0
    │       │               dim2     (feature) float64 -10.0 0.0 10.0 20.0 -10.0 ... -10.0 0.0 10.0 20.0
    │       │           Dimensions without coordinates: feature
    │       │           Data variables:
    │       │               *empty*
    │       │           Attributes:
    │       │               multiindexes:  {'feature': ['dim1', 'dim2']}
    │       │               name_map:      {'feature': 'feature'}
    │       └── DataTree('coords_from_transform')
    │           └── DataTree('feature')
    │                   Dimensions:  (feature: 20)
    │                   Coordinates:
    │                       dim1     (feature) float64 20.0 20.0 20.0 20.0 30.0 ... 60.0 60.0 60.0 60.0
    │                       dim2     (feature) float64 -10.0 0.0 10.0 20.0 -10.0 ... -10.0 0.0 10.0 20.0
    │                   Dimensions without coordinates: feature
    │                   Data variables:
    │                       *empty*
    │                   Attributes:
    │                       multiindexes:  {'feature': ['dim1', 'dim2']}
    │                       name_map:      {'feature': 'feature'}
    ├── DataTree('sanitizer')
    │   └── DataTree('0')
    │       │   Dimensions:  ()
    │       │   Data variables:
    │       │       *empty*
    │       │   Attributes:
    │       │       params:            {'feature_name': 'feature', 'sample_name': 'sample'}
    │       │       feature_coords:    _is_node
    │       │       sample_coords:     _is_node
    │       │       is_valid_feature:  _is_node
    │       ├── DataTree('feature_coords')
    │       │       Dimensions:  (feature: 20)
    │       │       Coordinates:
    │       │         * feature  (feature) int64 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
    │       │       Data variables:
    │       │           *empty*
    │       │       Attributes:
    │       │           multiindexes:  {}
    │       │           name_map:      {'feature_coords': 'feature'}
    │       ├── DataTree('sample_coords')
    │       │       Dimensions:  (sample: 25)
    │       │       Coordinates:
    │       │         * sample   (sample) datetime64[ns] 2001-01-01 2002-01-01 ... 2025-01-01
    │       │       Data variables:
    │       │           *empty*
    │       │       Attributes:
    │       │           multiindexes:  {}
    │       │           name_map:      {'sample_coords': 'sample'}
    │       └── DataTree('is_valid_feature')
    │               Dimensions:           (feature: 20)
    │               Coordinates:
    │                 * feature           (feature) int64 0 1 2 3 4 5 6 7 ... 13 14 15 16 17 18 19
    │               Data variables:
    │                   is_valid_feature  (feature) bool True True True True ... True True True True
    │               Attributes:
    │                   multiindexes:  {}
    │                   name_map:      {'is_valid_feature': 'is_valid_feature'}
    └── DataTree('concatenator')
        │   Dimensions:  ()
        │   Data variables:
        │       *empty*
        │   Attributes:
        │       params:      {'feature_name': 'feature', 'sample_name': 'sample'}
        │       n_data:      1
        │       n_features:  [20]
        │       coords_in:   _is_tree
        └── DataTree('coords_in')
            └── DataTree('0')
                    Dimensions:  (feature: 20)
                    Coordinates:
                      * feature  (feature) int64 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
                    Data variables:
                        *empty*
                    Attributes:
                        multiindexes:  {}
                        name_map:      {'0': 'feature'}

Codecov Report
Attention: 28 lines in your changes are missing coverage. Please review.

Comparison is base (8e199ef) 91.46% compared to head (3619f94) 94.14%.
Report is 168 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #103      +/-   ##
===========================================
+ Coverage    91.46%   94.14%   +2.68%
===========================================
  Files           39       71      +32
  Lines         2600     5821    +3221
===========================================
+ Hits          2378     5480    +3102
- Misses         222      341     +119

Files
Coverage Δ

tests/models/test_cca.py
100.00% <100.00%> (ø)

tests/models/test_complex_eof.py
100.00% <100.00%> (ø)

tests/models/test_complex_mca.py
100.00% <100.00%> (ø)

tests/models/test_eeof.py
100.00% <100.00%> (ø)

tests/models/test_eof.py
100.00% <100.00%> (ø)

tests/models/test_eof_rotator.py
100.00% <100.00%> (+2.05%)
:arrow_up:

tests/models/test_gwpca.py
100.00% <100.00%> (ø)

tests/models/test_mca.py
100.00% <ø> (ø)

tests/models/test_mca_rotator.py
100.00% <ø> (ø)

tests/models/test_opa.py
100.00% <ø> (ø)

... and 37 more

... and 25 files with indirect coverage changes

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

This _dummy_feature_coords was a little troublesome to serialize as dict[np.array], so I tried to instead recreate it in the inverse_transform pathway so we don't need to save it. This passes tests but I don't fully understand this class so let me know if this isn't right.

Everything looks good! With your approach, we indeed no longer need to save the dummy feature coordinate separately.
The sole purpose of the class is to concatenate a list of 2D DataArrays along the feature dimension. If the original feature dimension is only one-dimensional, the coordinates are preserved (the MultiIndexConverter ignores these). This can result in an attempt to concatenate multiple DataArrays with potentially incompatible coordinates at this point. In the case of already converted coordinates (which are always given by range(len(coords))), there's a risk of combining non-unique coordinates. Although xarray allows this in principle, we might run into trouble when performing mathematical operations along the coordinates. I can't remember exactly which mathematical operation causes the issue (it might even be .dot), but it seems to me that going into the individual models with streamlined coordinates is definitely the safer route.

I reduced these lines by defining a single source of truth for the order of transformer ops and then looping through them. Not sure if the copy is necessary in all these cases but didn't want to accidentally modify the original object if we don't want to. We could go a step further with this and try to use the transformer_types to instantiate the transformers as well, but we have to pass some unique kwargs to each there so I didn't bother.

That's beautiful!

Do you have a use case in mind where the user would require access to the model's serialize/deserialize methods? Or would providing just the save/load methods be sufficient?

Do you have a use case in mind where the user would require access to the model's serialize/deserialize methods? Or would providing just the save/load methods be sufficient?

Nope, nothing in mind, I only abstracted those out because it allowed me to reuse for the non-rotated model here. They could definitely be private methods if you prefer.

Do you have a use case in mind where the user would require access to the model's serialize/deserialize methods? Or would providing just the save/load methods be sufficient?

Nope, nothing in mind, I only abstracted those out because it allowed me to reuse code for the non-rotated model here. They could definitely be private methods if you prefer.

Alright, that makes sense; we can keep it then. I think we're ready to go once all the checks have passed. :)

Nope, nothing in mind, I only abstracted those out because it allowed me to reuse code for the non-rotated model here. They could definitely be private methods if you prefer.

Actually I take this back, already thought of a potential use case for myself.
Say you want to fit a separate set of EOFs for each month in a dataset (seasonally varying). You end up with 12 separate models, and for tidy storage we could, instead of calling save() on each one, call serialize(), then assemble the DataTree for each month into a node on a parent tree and save the whole thing with to_zarr(). Then to reassemble the models, load the DataTree manually, separate out each node, and call deserialize().
You could of course save 12 separate zarr stores too, but I can imagine applications where this might be preferred.


fix(support-bundle): test_support_bundle_purge

https://github.com/longhorn/longhorn/issues/6320

Test result.

@c3y1huang Do we still need this PR? Seems recently the test case doesn't fail anymore.

@c3y1huang Do we still need this PR? Seems recently the test case doesn't fail anymore.

I see no harm in asserting the status code. WDYT?

Agree. And checking the request's response before accessing the payload is more reasonable.


[HDInsight] Onboard new SDK

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

The SDK namespace board review is https://github.com/Azure/azure-sdk-pr/issues/1247

Hi @ArcturusZhang  could you please help review this?  Thanks

A few comments. I did not see the api file, please run the following commands to make sure everything in your PR is up-to-date:

dotnet build /t:GenerateCode
dotnet build /t:GenerateTests
<repoRoot>/eng/Export-API.ps1 hdinsight

Hi @ArcturusZhang , thanks for your review. Yes, I didn't run export-api.ps1, now I have added the api folder

Hi @ArcturusZhang  could you please help review it again? Thanks

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.HDInsight.Containers

Hi @ArthurMa1978 , I am sorry that you can not merge this commit https://github.com/Azure/azure-sdk-for-net/pull/38256/commits/758855f7bb8966417e35b7c311a1ef7a08c6d6e2
The reason is that our swagger spec requires it is string with format validation, if we change the string to Sytem.Uri, in http request it will end with "/", this request will fail, the SDK won't work.

Hi @ArthurMa1978 could you please help continue to review this PR?
I have addressed the comment with the suggestion from @ArcturusZhang .  Thanks


@conda-forge-admin, please add user @whophil

Additional comment:
No response

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added user @whophil in conda-forge/dash-extensions-feedstock#20.


Add ability to restart a pane/tab

Description of the new feature/enhancement
I'd like to see the ability to restart a pane/tab without altering the order or arrangement of tabs/panes.
See ConEmu's "recreate active console" feature.  This allows you to restart a console pane/tab without closing it.  The chosen console is closed, then a new console started with the same command line.
PowerShell occasionally needs to be restarted (unrelated to WT, this happens in its own console as well) but I don't want to lose the arrangement of panes.
Please make it available via customizable keyboard shortcut.

Thanks for the request! This looks like a /duplicate of #3726 (except it says tab instead of pane; it was likely filed before pane knowledge was widespread.)


Fixed Heat Index for Kelvin

Fixed
Issue related to #1263
Allows Current Weather module to display correct values for 'feels like' temperature in Kelvin

Warnings

:warning:

Please include an updated CHANGELOG.md file.This way we can keep track of all the contributions.

  Generated by :no_entry_sign: dangerJS


Upgrade dependencies

Direct:
golang.org/x/exp v0.0.0-20240823005443-9b4947da3948 golang.org/x/net v0.28.0
Indirect:
golang.org/x/crypto v0.26.0
golang.org/x/sys v0.24.0

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

Project coverage is 75.80%. Comparing base (46eab16) to head (f2d8ae7).

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #580      +/-   ##
==========================================
- Coverage   75.85%   75.80%   -0.06%
==========================================
  Files          73       73
  Lines        5990     5990
==========================================
- Hits         4544     4541       -3
- Misses       1055     1058       +3
  Partials      391      391

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


Random handshake failure

Hello, I've been trying to use this project to tunnel my OpenVPN connections. However, it appears that udp2raw-tunnel will randomly fail on the handshake stage: either the client or the server (or both) will be stuck at sending SYN packets to each other but never finishing that process. For example,

Without any changes to the network configurations, simply try to restart the server / client several times, and the client will connect without any problem.
At first I believed that this might be some sort of problem of time synchronization, thus I tried to synchronize the time on the server and client and made sure that the current timestamp on the server and client are as close as possible, but the problem remains. The RTT from my server to the client is ~80ms. What is strange is that if the connection is set up for one time, then reconnecting the client will not cause any further failures, but restarting the server might bring the problem back on.
I'm not sure if this is reproducible for others, therefore I am posting it here in case that someone may run into the same problem. I still think this is something about time but I can still not figure out where exactly the problem exists.

thus I tried to synchronize the time on the server and client and made sure that the current timestamp on the server and client are as close as possible, but the problem remains

udp2raw doesnt depend on synchronized time at all. No need to synchroize.
I still have no idea about this problem. I will reply as soon as i get an idea.

Sorry,I cant reproduce this.Have you tried to only restart client or only restart server? Could single side restaring solve the problem?
And what will happen if you let the client and server keep retrying for 5 minutes,will they eventually get a connection?
Could you plz give --raw-mode udp a try? udp mode doesnt have syn,so if i know the behavior under udp,it may help.

Could single side restaring solve the problem?

Yes. Sometimes it gets working by only restarting the server for several times

And what will happen if you let the client and server keep retrying for 5 minutes,will they eventually get a connection?

I tried to let them SYN for ~2min and nothing changes.

Could you plz give --raw-mode udp a try? udp mode doesnt have syn,so if i know the behavior under udp,it may help.

I have tried ICMP earlier but I don't have any screenshots now. I'll post them here later when I have a try with ICMP and UDP.

did you set your openvpn to automatically modify your route table? sometimes if this wasnt done correctly,there might be a route cirle.
could you try to stop openvpn client  and only test with udp2raw client and server?

No, the two screenshots posted above are not taken from when udp2raw is tunneling OpenVPN. I  have shut down OpenVPN on both sides in order to test whether udp2raw works on its own. It's definitely not something about the routing table.
I will do further tests tomorrow.

@wangyu- Yes it also happens with UDP mode. It might also get stuck in the handshake stage. (2 of 5 trials got stuck as the following picture shows)

ICMP mode has the same issue.
All these protocols have this problem randomly. I still cannot figure out in what case will this problem be exactly reproducible.

BTW, I am behind NAT provided by my home router and there is no ISP NAT (China Telecom, with public IP address for PPPoE endpoint), and the remote server is an Aliyun Singapore instance with a 1:1 NAT (1 public ip = 1 private ip, every packet is forwarded to the VPS). Might be usable if someone is trying to reproduce this issue.

I experienced the same problem, though less frequently. It randomly occurs on my configuration, and it seems a clean server (haven't been connect by any client yet) are less likely to have the problem than a server (session) that has previously been connected to.

I have done the following experiments on this issue:

Start the server, then start the client. The client gets stuck at the handshake stage. Tried to restart the client several times, but without luck, it cannot get connected to the server.

Start the server, then start the client. The handshake got stuck. I restarted the server and then restart the client, after which both sides handshaked and reached ready state. Tried to restart the client several times and the connections were all successful.

Start the server then start the client. Handshake succeeded. Restarted the server and then the handshake were stuck.

Following the same process of (2), I left the server alone for several minutes, and then tried to reconnect the client: the client got stuck on handshaking.

I left the server and the client alone to 'handshake' for several minutes, then the handshake process was still stuck. They are sending handshake packets to each other but none of them reached the ready state.

hi,@PeterCxy,thx for your feed back.that looks abnormal.
plz:
1.tell me the binary version you used at client/server side
2.and your client/server 's operating system
3.and the full arguments of your client/server
4.and the frequency of this problem
5.use --log-level 6 --log-position on both side. redirect the log to files(it could be very long,so redirect is necessary). and upload some of typical ones.
great thx.
if you can handle tcpdump,some tcpdump file will also be great.

looks like ,though udp-mode has similiar problem,it goes further than tcp-mode. i saw (re)send handshake2,which is the second step of udp-mode(client side). but in the tcp-mode screenshot,i only saw (re)send syn,thats only the first step of tcp-mode (client side)

@PeterCxy  i found a serious uninitialized variable problem after checking and experimenting. which causes packet loss randomly at server side,especially on a 32bit system.
In your case,re-booting the server solves the problem.This also looks like an  uninitialized variable problem,I suspect they are the same one.
Plz have a try with the lastest released version,check if the problem still exist.
Great thanks!

@wangyu- As far as I can test for now, the problem vanished after upgrading to the 20170813.1 tag. Thanks for your help. I am closing this issue for now.


[HelmDeploy 0.171.3]: Attempts to run Helm get manifest without specifying namespace

Type: Bug
Enter Task Name: HelmDeploy
Since 0.171.3 of the HelmDeploy task, the task tries to run the Helm get manifest  which fails because it does not include the --namespace option. Further to this I don't understand the purpose of running this command after deploying the release, as it may cause secrets to be available in the log.
Example task:

task: HelmDeploy@0
displayName: Deploy app to cluster
inputs:
connectionType: None   # KUBECONFIG environment variable is set in an earlier task
namespace: my-product-dev
command: upgrade
chartName: Deploy/helm/my-product
releaseName: my-product
valueFile: Deploy/environments/values-dev.yaml
arguments:  --atomic --timeout 250s

Task logs
2020-06-29T13:38:26.3548319Z Task         : Package and deploy Helm charts
2020-06-29T13:38:26.3549706Z Description  : Deploy, configure, update a Kubernetes cluster in Azure Container Service by running helm commands
2020-06-29T13:38:26.3550880Z Version      : 0.171.3
2020-06-29T13:38:26.3551753Z Author       : Microsoft Corporation
2020-06-29T13:38:26.3552688Z Help         : https://aka.ms/azpipes-helm-tsg
2020-06-29T13:38:26.3553781Z ==============================================================================
2020-06-29T13:38:26.6973457Z [command]/opt/hostedtoolcache/helm/3.2.1/x64/linux-amd64/helm upgrade --namespace my-product-dev --install --values /workspace/7/s/Deploy/environments/values-dev.yaml --wait --atomic --timeout 250s my-product Deploy/helm/my-product
2020-06-29T13:38:44.4882031Z Release "my-product" has been upgraded. Happy Helming!
2020-06-29T13:38:44.4883415Z NAME: my-product
2020-06-29T13:38:44.4884266Z LAST DEPLOYED: Mon Jun 29 13:38:28 2020
2020-06-29T13:38:44.4885415Z NAMESPACE: my-product-dev
2020-06-29T13:38:44.4886433Z STATUS: deployed
2020-06-29T13:38:44.4887586Z REVISION: 2
2020-06-29T13:38:44.4888389Z TEST SUITE: None
2020-06-29T13:38:44.4939514Z [command]/opt/hostedtoolcache/helm/3.2.1/x64/linux-amd64/helm get manifest my-product
2020-06-29T13:38:44.6334777Z Error: query: failed to query with labels: secrets is forbidden: User "system:serviceaccount:my-product-dev:my-product-dev-helm-sa" cannot list resource "secrets" in API group "" in the namespace "vsts-agent"
2020-06-29T13:38:44.6410641Z ##[section]Finishing: Deploy Review API

@adhodgson1 Could you please confirm whether it's a warning or a task failure, to help us understand the issue better?

The task still succeeds even with this error.

@shigupt202 it's probably not marked as an agent error.. it's just something being piped to the stdout maybe?

Yes, the error message is getting piped to stdout. Working on the fix.


optional force flag added

Optional force flag added. If force flag is on and patch fails, then resource will be deleted and re-created.
#24

Can you update the tests for the changes that you've made? The CI checks are failing.


[Snyk] Upgrade axios from 1.2.3 to 1.2.4

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade axios from 1.2.3 to 1.2.4.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 21 days ago, on 2023-01-24.

Release notes

Package name: axios

1.2.4 - 2023-01-24Release notes:
Bug Fixes

types: renamed RawAxiosRequestConfig back to AxiosRequestConfig; (#5486) (2a71f49)
types: fix AxiosRequestConfig generic; (#5478) (9bce81b)

Contributors to this release

 Dmitriy Mozgovoy
 Daniel Hillmann

1.2.3 - 2023-01-17Release notes:
Bug Fixes

types: fixed AxiosRequestConfig header interface by refactoring it to RawAxiosRequestConfig; (#5420) (0811963)

Contributors to this release

 Dmitriy Mozgovoy

    from axios GitHub release notes

Commit messages

Package name: axios

6600d51 [Release] v1.2.4 (#5487)
2a71f49 fix(types): renamed `RawAxiosRequestConfig` back to `AxiosRequestConfig`; (#5486)
6486929 Fix AxiosRequestHeaders & AxiosHeaders types; (#5482)
186ea06 fix AxiosRequestConfig generic (#5478)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 58.999%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1167

Relevant Lines:
1951

💛  - Coveralls


Description getting generated twice in the HTML

var x= {
/**
*
*

This flag set to true,
to work studio in offline mode.
@type Boolean */
offline: false
}

for the above code jsdoc generating below output in the html. please suggest a work around to avoid duplicate content
(static) offline :Boolean
This flag set to true,
to work studio in offline mode.
This flag set to true,
to work studio in offline mode.
Type:
Boolean

Found the Issue and corrected. Issue is with plugins added in config Json.


Clean up code around TaskPropertyUtils

Move single-use method to the only place it is called from
Add Javadoc to property walking methods

Build: https://builds.gradle.org/viewQueued.html?itemId=11734434


Fix catalog YAML

Square brackets within the yaml string meant it was interpreted as an array and broke the initial catalog load. This puts speach marks around so it's interpreted as a string.

Thanks for spotting and fixing! Merging now.


Add optimized read_parquet path for remote storage

Notes:

~This PR is blocked by #1081 (many of the apparent changes here actually belong to that PR)~
These changes are intended to address #1088
The optimizations added here are (mostly) copied from cudf#9225

The specific fsspec-based optimizations are described in a bit more detail in that PR
Once NVTabular is pinned to a new enough version of cudf (one where cudf#9225 is merged), the redundant code added here (in nvtabular/io/fsspec_utils.py) can be removed

Performance [UPDATED 9/20/2021]:

Initial tests on a local workstation (reading from GCS over the internet) are very promising: With this PR, I am able to read through a 23-file, 1TB Dataset (Criteo) on two GPUs in ~9 minutes.  Without this PR, I cannot even read in a single file from that dataset in the same amount of time.
I have confirmed that this PR leads to favorable performance on GCP (~15 min on an 8-GPU cluster when the input data is stored in GCS).  Without this PR, the benchmark takes hours (it is slow enough that I didn't bother with a full run). Note that the same benchmark is expected to finish in ~2-3 min when the input data is stored on a local SSD (however, my instance did not have a large-enough SSD to test this).  Command and output:

(rapids-21.08) rzamora@a100-nvtabular-gcs-testing-8g:~$ python NVTabular/bench/examples/dask-nvtabular-criteo-benchmark.py --part-mem-frac 0.125 --data-path gs://workshop-datasets/criteo-parque --out-path /h
ome/rzamora/scratch/ --out-files-per-proc 3 --device-limit-frac 0.75 --device-pool-frac 0.85 --cat-cache-high device -d 0,1,2,3,4,5,6,7 > bench.PR1119.out 2>&1

Dask-NVTabular DLRM/Criteo benchmark
--------------------------------------
partition size     |<PHONE_NUMBER>
protocol           | tcp
device(s)          | 0,1,2,3,4,5,6,7
rmm-pool-frac      | 0.85
out-files-per-proc | 3
num_io_threads     | 0
shuffle            | PER_PARTITION
cats-on-device     | False
======================================
Runtime[s]         |<PHONE_NUMBER>922211
======================================

GCP Instance Details:

Machine type: a2-highgpu-8g (96 vCPUs, 680 GB memory)
CPU platform: Intel Cascade Lake
GPUs: 8 x NVIDIA Tesla A100
Zone: us-central1-c
Disk: 1024GB SSD

I have confirmed that this PR is back to ~15 mins on the dask-criteo benchmark with 8 GPUs on GCP (and barely over 2 mins when reading from NVMe)
Reading from GCS on GCP:
Dask-NVTabular DLRM/Criteo benchmark
--------------------------------------
partition size     |<PHONE_NUMBER>
protocol           | tcp
device(s)          | 0,1,2,3,4,5,6,7
rmm-pool-frac      | 0.85
out-files-per-proc | 3
num_io_threads     | 0
shuffle            | PER_PARTITION
cats-on-device     | False
======================================
Runtime[s]         |<PHONE_NUMBER>167328
======================================

Reading from NVMe on a DGX-1:
Dask-NVTabular DLRM/Criteo benchmark
--------------------------------------
partition size     |<PHONE_NUMBER>
protocol           | tcp
device(s)          | 0,1,2,3,4,5,6,7
rmm-pool-frac      | 0.8
out-files-per-proc | 3
num_io_threads     | 0
shuffle            | PER_PARTITION
cats-on-device     | False
======================================
Runtime[s]         |<PHONE_NUMBER>4667053
======================================

This PR also fixes a small bug from #1127 that results in the reading of every partition in the dataset when infer_schema is called - See problematic task-stream screenshot below (where fit hasn't even started after >1 min):


Field defines a relation with the model 'auth.User', which has been swapped out.

https://github.com/maycuatroi/django-firebase-auth/blob/58c27292d2c29581674ce384660bac0533e3345b/abstract_auth/abstract_user_profile.py#L9
from django.conf import settings
user = models.OneToOneField(
        settings.AUTH_USER_MODEL, on_delete=models.CASCADE, related_name="auth_profile"
 )

https://github.com/iosifnicolae2/django-firebase-auth/commit/42c19f5b79cb737323e949a10de6143a16c3428b

iosifnicolae2@42c19f5
Use this in your requirements: git+https://github.com/iosifnicolae2/django-firebase-auth.git@42c19f5

@eracle @iosifnicolae2 some credits for this would be nice :)

Resolved in commit https://github.com/maycuatroi/django-firebase-auth/commit/9a5b2478f48a572dbf4da53f413efa8ec7c29e40


AutomaticBackgroundTask & ForceUpdateFromAnyVersion

ForceUpdateFromAnyVersion & AutomaticBackgroundTask can't be used in combination?
When using AutomaticBackgroundTask (and triggering it by running the Scheduled task taking care of it) it doesn't take lower versions into account. Only when a higher version was published, it downloads & installs the update...

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

ID: 0e69e20f-7cfc-aa28-85b8-f2deb8a69873
Version Independent ID: c3fffd4b-4405-c347-2db8-95c5c0928de5
Content: App Installer file update settings - MSIX
Content Source: msix-src/app-installer/update-settings.md
Product: msix
GitHub Login: @mcleanbyron
Microsoft Alias: mcleans

Thanks for reporting this. I followed up with the engineering team and confirmed that they have not seen this issue. Can you confirm that you have incremented the Version attribute of the AppInstaller element? The appinstaller version itself still needs to be incremented for the update to work – for example, appinstaller v1 containing app v5 installed, then replace appinstaller file with appinstaller v2 containing app v4.

In our example, we let the appinstaller be generated by Visual Studio (uses the same version number as the Package itself) - So no, we didn't. - Will try this and let you know - Thank you for the suggestion!

Thanks for the follow up. Since this does not appear to be related to a docs issue at this time, I'm going to close this issue for now. Please feel to reopen if you feel you are running into a docs issue after all.


Why mutation analysis is not supported on buggy program version?

I tried to execute mutation analysis in the following way:
defects4j checkout -p Time -v 9b -w Time_9b
cd Time_9b
defects4j mutation -r

But get the following error:

Mutation analysis on buggy program version not (yet) supported!

Can someone help me?
Thanks.

Hi @moar82,
The reason for this error is the following:
One or more triggering tests fail on the buggy program version, but mutation analysis usually assumes that all tests pass.
There are a number of options for how to handle such cases (e.g., exclude the triggering test(s) or properly define what it means for a failing test to kill a mutant).
Do you have a proposal for what the expected behavior of defects4j mutation on a buggy program version should be?
Thanks,
René

Hi @rjust ,
First of all, I'd like to clarify what is the internal process of the mutation command.
Does the mutation process executes the developer unit test into the checked out version?  According to the documentation this is the default behavior; then it makes sense that is not valid to run generate mutants, since the tests that reveal the bug will fail.  Then, I'd remove the (yet) from the error message, because it gives the impression that is not available now but is in the pending list.
What about unit tests generated with automated tools like evosuite (parameter -s) ?  This tests can/cannot reveal the bug.  It might be attractive to allow to generate mutants and evaluate them using external test suites for users at their own risk, warning them that if they failed the process won't finish.  Do you agree?
I'd appreciate your work and all the people that contributes to this framework. I hope my comments can help to make even better this framework.
Regards.
Rodrigo.

@moar82, thanks again for your suggestions. We changed Defects4J to allow a user to run mutation analysis on a buggy version; it will issue a warning if it fails with a possible resolution (i.e., removing/ignoring failing tests).

Hello @rjust and @moar82,
I am a bit confused about the discussion that why it doesn't make sense to compute mutation analysis for the buggy version for developer generated test cases or automated generated (failed) test cases?  Some mutation-based fault localization techniques use mutation coverage of failed and passed test cases to find the probability of a statement being buggy. So I believe whether a mutant is killed by a passed test case or by a failed test case, it is important to use this mutant in generating the mutation score.
Kindly correct me if I am misunderstanding the problem.


Where to put boilerplates

Hey, I have created a boilerplate for rails6 + graphql https://github.com/zauberware/rails-devise-graphql
Where can I include this here in the Readme?

Hi @simonfranzen, I was considering to have starters listed since there are some noteworthy examples like yours. You can add a section called "starters/boilerplates" before "other rails tools" and add yours by sending a pull request.

PR is open https://github.com/gramantin/awesome-rails/pulls

@simonfranzen merged, thanks so much!


Search Gets Stuck Loaading Images

Expected behavior
Searching for "MS SQL SERVER" or anything for that matter should filter to images that contain related words.
Actual behavior
Nothing loads and stuck on circle spinning.
Information about the Issue
Steps to reproduce the behavior

...
...

I get the same problem. I'm on MacOS Mojave - Docker Kitematic 0.17.5
Same as #4196

Same on MacOS too! :(


failed to download from Artifactory

I am getting Error: failed to download when using our internal Artifactory repo. I am able to publish charts and use helm install without issues. If I use the local path it works fine. Am I missing something?
repositories:
- name: stable
  url: https://kubernetes-charts.storage.googleapis.com
# To use official "incubator" charts a.k.a https://github.com/helm/charts/tree/master/incubator
- name: incubator
  url: https://storage.googleapis.com/kubernetes-charts-incubator
- name: mycompany-stable
  url: https://artifactory.ourdomain.com/artifactory/mycompany-stable
  username: {{ requiredEnv "MYCOMPANY_STABLE_USERNAME" }}
  password: {{ requiredEnv "MYCOMPANY_STABLE_PASSWORD" }}

releases:

- name: darktrace
  chart: mycompany-stable/darktrace-osagent
  wait: true
  namespace: default

Updating repo
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "mycompany-stable" chart repository
Update Complete. ⎈ Happy Helming!⎈

Comparing release=darktrace, chart= mycompany-stable/darktrace-osagent
in ./helmfile.yaml: helm exited with status 1:
  Error: Failed to render chart: exit status 1: Error: failed to download "mycompany-stable/darktrace-osagent" (hint: running `helm repo update` may help)

Artifactory Helm has the file
mycompany-stable/darktrace-osagent-3.0.0.tgz
- name: darktrace
  chart: ../../../helm-charts/darktrace-osagent
  wait: true
  namespace: default

helmfile diff
...
Building dependency release=darktrace, chart=../../../helm-charts/darktrace-osagent
Comparing release=darktrace, chart=../../../helm-charts/darktrace-osagent

@michaelpporter I don't know much about Artifactory, but anyways I have a few questions:

Do you have verify: true in your release? If so, would you mind disabling it? I thought you needed prove files to make verify work. https://helm.sh/docs/topics/provenance/
Does it work if you tried to use the chart with helm, like helm upgrade --install  mycompany-stable/darktrace-osagent?
Which versions of Helmfile and Helm do you use?

I do not have verify: true. I was using the default values and have added verify: false explicitly now.
helm upgrade --install mycompany-stable/darktrace-osagent does not work. Seems I need to troubleshoot our Artifactory.  It worked before, we migrated Artifactory recently, I will check with my team to see what changed. Any tips?
We are using helm v3.2.0 and helmfile v0.114.0

They enabled a redirect from http to https but Artifactory is not yet setup with https on the back end (AWS ALB) When the redirect was removed it worked fine. We know what we need to do going forward.
Thank you for the help.


Write pallet_evm README

I wanted to read pallet_evm source code but there was no README so I described pallet_evm README.
I put a link for the Rust documentation and wrote description according to this page.

Thank you for the review.
I also wrote readme into lib.rs.
Please confirm.

@sorpaas
Thank you for your review.
I updated README according to your review.
Please confirm.

@NoCtrlZ please fix the line width! Check the line-width job

@bkchr
I fixed the line length.
Please confirm.
Thank you!


ng serve sourcemaps are ineffective after angular 6 migration

Versions

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/

Angular CLI: 6.0.3
Node: 10.1.0
OS: darwin x64
Angular: 6.0.2
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.6.3
@angular-devkit/build-angular     0.6.3
@angular-devkit/build-optimizer   0.6.3
@angular-devkit/core              0.6.3
@angular-devkit/schematics        0.6.3
@angular/cli                      6.0.3
@ngtools/webpack                  6.0.3
@schematics/angular               0.6.3
@schematics/update                0.6.3
rxjs                              6.1.0
typescript                        2.7.2
webpack                           4.8.3

Repro steps

ng new test-app
cd test-app && npm start
Launch Chrome and try to find the sources

Observed behavior
In Angular 5, in Chrome DevTools sources were present in webpack:// > . > src, now I don't have them anymore (ng serve outputs .map files were created)
Desired behavior
Debugging sources

I deleted and recreated my Chrome Profile and now it works again !

Not sure why that was happening but glad to hear it's sorted.

The same thing happens to me, only when I try to serve the application with an environment ( ng serve --configuration user ). Regular ng server works as expected. Tried different browsers and also deleting my Chrome account, doesnt change anything. (identical version on everything with bioub )


Request to add "EnableFullScanOnBatteryPower" item

[Enter feedback here]
Hi Team,
The following features were added to the November 2020 platform version of MDAV.
It is not mentioned in the public information, so could you add it to this Leanr?
Features:
EnableFullScanOnBatteryPower
The following public information appears to contain:
https://learn.microsoft.com/en-us/powershell/module/defender/set-mppreference?view=windowsserver2022-ps
Best Regards.

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

ID: 67816e08-2639-ebac-5ffc-368cf9289301
Version Independent ID: cc8d93f2-8837-4169-0fc7-167d0ffca777
Content: Set-MpPreference (Defender)
Content Source: docset/winserver2016-ps/defender/Set-MpPreference.md
Product: w10
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.
As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.
If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.
With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.
Here's what the new experience looks like.
Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.
First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful
Article was unhelpful

Finally, select Submit and you're done!


Scan mode that ignores known TTL points

Can we get a scan mode that will ignore known TTL points? This way we can finally get all those spawn points that seem to elude the scan. For example I have over 250 unknowns after several weeks. Maybe in that mode, once all are found it then moves to regular scanning?

Could this help?
GIVE_UP_KNOWN = 0
GIVE_UP_UNKNOWN = 3300
SKIP_SPAWN = 3300

Hmm.. I have no idea. Have you tried it? Maybe Ill try it tomorrow. @Noctem would this work?

Ok Im giving it a try today, hopefully Ill see those unknowns go down! :) Thanks for the advice!

I tried it some time ago and I think (didn't pay much attention sorry) it helped. Hope it does the trick for you!
I'm going to test it too tonight.

It does look like my know are 70 more than previously, but my unknown hasn't changed. That could be a bug though... It might indeed be working :)

I'm afraid it didn't seem to work. After 9 hours running with ~100 accounts, my Known went from 6600 to 6690. Unknown stayed at 350. I've just restarted the scanner with the normal setting and have 6600 known again and still 350 unknown. I don't really get what's happening. To begin with, if I run web.py and look at the map, it seems I have less than 100 red spawn points.
Just in case I'm missing something, I have more: 1500.

Yeah I did this all day yesterday and I went from 4892 known to 5038 known, but my unknown is still 265, it didn't budge at all.. so Yay for the new known.. but hmm.. buggy for the unknown?

@manolomanila Hey looks like the new scan when I did no-pickle it updated my unknowns and sure enough.. they are a whole lot less! Im at 88 unknown now, so yeah there does seem to be some sort of bug.


Fix user feed fallback map

Use Leaflet for the fallback map.
It looks pretty much the same:

I'm controlling now as well whether it's a map with a tile url or not. On the latter case, we create a map using google maps.
This is blocked until we find a suitable api key / client id we can use, which we should include in all configs.

Acceptance :+1:


Fix build for iOS

Fixes #290. size_t is not uint32 or uint64 on iOS, so use explicit casts when calling WriteSize with a size_t

Thank you for this contribution.


No coverage data produced

The coverage.json, coverage.txt, and the JSON files in the coverage folder are either empty or only contain "{"coverage":{}}" when we run the command "timeout 20s ityfuzz evm -t './build/*'" with the following contract:
ragma solidity ^0.4.24;
/* User can add pay in and withdraw Ether.
The constructor is wrongly named, so anyone can become 'creator' and withdraw all funds.
*/
contract Wallet {
address creator;
mapping(address => uint256) balances;

function initWallet() public {
    creator = msg.sender;
}

function deposit() public payable {
	assert(balances[msg.sender] + msg.value > balances[msg.sender]);
    balances[msg.sender] += msg.value;
}

function withdraw(uint256 amount) public {
    require(amount <= balances[msg.sender]);
    msg.sender.transfer(amount);
    balances[msg.sender] -= amount;
}

}
How can i obtain the coverage data? Really lookforward to you help! thanks a lot!

There is a bug in the coverage calculation process.
An ad-hoc way to bypass this is by making it a foundry project and adding a setup script (check https://book.getfoundry.sh/forge/invariant-testing)
Example:
contract InvariantExample1 is Test {

    ExampleContract1 foo;

    function setUp() external {
        foo = new ExampleContract1();
    }

    function invariant_A() external {
        assertEq(foo.val1() + foo.val2(), foo.val3());
    }

    function invariant_B() external {
        assertGe(foo.val1() + foo.val2(), foo.val3());
    }

}

Then run:
ityfuzz evm -m test/Invariant.sol:InvariantExample1 -- forge test

@shouc Excuse me, has anyone been working on fixing this calculation bug?


Asking for username and password when trying to git clone

Hey Eric, you said to rebuild the docker image so when I try to git clone it tells me to put in an email and password. What do I put for that?

Here is the code:
pi@raspberrypi:~ $ git clone https://github.com/EricJMarti/inventory-hunter.
Cloning into 'inventory-hunter.'...
Username for 'https://github.com':

Do you have a trailing period in the link?

yes I do.

I even tried a git pull method and that did not work as you said in the previous 'issue'. btw thanks for making best buy work.

It's strange for git to be asking you for a password on a clone. Have you tried git cloning in a new directory (in other words, pulling a brand new copy of the code)?

Hello,
I am having the same issue with the user name and password.
I just pulled the clone not too long ago but it failed because my SD card didn't have enough storage, so I put Raspbian on a new SD card and tried again but now I'm being aske for a password.
Any suggestions?

Ok work around: fork the code and then use git with the link after forking to you account

Hello, Download the repo to your Raspberry Pi as a ZIP and then start terminal on downloaded directory.

Same issue here... I need a username and password to do git clone... I also noticed the '.' no longer has a space at the end which changed from yesterday.

Any ideas here. I have been trying to do this build the last 2 nights.  First tried SMTP and got to the end but then couldn't get emails to work, then tried Discord and never got notifications on Discord, so I am starting over now and now I am getting prompted for user id and password which this step has never caused an issue the last 2 days so something has changed.  Please help. Thank you!

I left out the period and it seems like it downloaded ok. Still need to verify though.
.
One thing that changed with the new setup is now emails are no longer going out (after I worked a long time to get them working in the previous version within hunter.py). :)

I left out the period as majorhavocgit suggested and it all worked for me.

Looks like I had a trailing period in the git clone command in README.md. This was not intentional. Sorry about that!


bug: manifest parser sees spaces in comments as multiple results

Consider the following manifest:
---
# +operator-builder:resource:collectionField=provider,value="aws",include
apiVersion: v1
kind: ConfigMap
metadata:
  name: contour-config-test-collection-field
  namespace: ingress-system  # +operator-builder:field:name=namespace,default=ingress-system,type=string
data:
  this: "serves no purpose other than to test resource markers on collection fields"
---
# +operator-builder:resource:collectionField=provider,value="aws",include
# Note: Comments with spaces can cause problems with parsing.  Leave this here
# for functional testing purposes.

# The space above is actually what causes the problem.
apiVersion: v1
kind: ConfigMap
metadata:
  name: contour-config-test-parse-comment
  namespace: ingress-system  # +operator-builder:field:name=namespace,default=ingress-system,type=string
data:
  this: "serves no purpose other than to test comment spaces for resource markers on collection fields"

With a space in the comment, this will actually return multiple marker results for the contour-config-test-parse-comment ConfigMap.  While this is not necessarily an issue if we handle the result properly, the marker package should only return one result as there is only one marker.
UPDATE: this is actually in the manifest parser, not the marker parser, as the static content while parsing looks like this:
(this is from a debug console)
"\n# +operator-builder:resource:collectionField=provider,value=\"aws\",include\napiVersion: v1\nkind: ConfigMap\nmetadata:\n    name: contour-config-test-collection-field\n    namespace: !!var parent.Spec.Namespace # controlled by field: namespace\ndata:\n    this: \"serves no purpose other than to test resource markers on collection fields\"\n\n# +operator-builder:resource:collectionField=provider,value=\"aws\",include\n# Note: Comments with spaces can cause problems with parsing.  Leave this here \n# for functional testing purposes."

This appears to be a bug in the upstream yaml.v3 package.  Given the above set of manifests, we get:
Manifest 0:
---
# +operator-builder:resource:collectionField=provider,value="aws",include
apiVersion: v1
kind: ConfigMap
metadata:
  name: contour-config-test-collection-field
  namespace: ingress-system  # +operator-builder:field:name=namespace,default=ingress-system,type=string
data:
  this: "serves no purpose other than to test resource markers on collection fields"
---
# +operator-builder:resource:collectionField=provider,value="aws",include
# Note: Comments with spaces can cause problems with parsing.  Leave this here
# for functional testing purposes.

Manifest 1:
# The space above is actually what causes the problem.
apiVersion: v1
kind: ConfigMap
metadata:
  name: contour-config-test-parse-comment
  namespace: ingress-system  # +operator-builder:field:name=namespace,default=ingress-system,type=string
data:
  this: "serves no purpose other than to test comment spaces for resource markers on collection fields"

The newline character causes the yaml marshaler to  see the resource marker as a foot comment to the first manifest and takes the newline as the start of a new manifest.


Video support for more file formats

Overview of feature request
Right now the Video media type only allows .mp4. Is it possible to allow other formats?
What kind of user is the feature intended for?
End users doing video storage/preservation
What inspired the request?
Documenting Video Derivatives #929  (which work great! But are only mp4-to-mp4.)
What existing behavior do you want changed?
Change the restriction on Video media type's file field to allow such types as:

.avi
.mov /.qt (Quicktime)
.mpg/.mpg2/.mpeg2 (uncompressed digititized video)
Other formats as suggested in "Video preservation" recommendations(?)

Any brand new behavior do you want to add to Islandora?
Along with being allowed to upload them, I'd like to be able to do derivatives. At the moment, conversion to .mp4 and extracting thumbnails/poster images would be great. There may be other preservation transformations that are eventually recommended.
What constraints does FFMPEG place on us in doing this? Are there extra codecs that need to be enabled? Are they protected by incompatible licenses therefore we can't ship with them enabled and could include documentation on doing this yourself? etc.
Any related open or closed issues to this feature request?

#929

I think this is just configuration at least for some of the above listed movie types. When testing video derivatives I just edit the file field of the video media type and add "mov" to the acceptable extensions. It works fine.

Probably! This ticket is partly here to do tests like that.
Smarter people than me would know better, but I suspect that it's not the extension (container format) that will affect whether ffmpeg can handle the file, as much as the audio/video(?) codecs. That true?

From the tech call: I think the way forwards is a 2 part approach.

Test to see what common formats are already useable when the dot extensions are added to Drupal.
Create a list of formats and using that list create PRs to add the necessary codecs/libraries to add to the buildkit.

Common formats:

.WEBM
.MPG, .MP2, .MPEG, .MPE, .MPV
.OGG
.MP4, .M4P, .M4V
.AVI, .WMV
.MOV, .QT
.FLV, .SWF
AVCHD

For a bigger list check Wikipedia
Most formats don't need to be web-accessible, the service file derivative on the other hand does.


quay image

We need to get an image onto quay so the helm chart can work with it out of the box. I was under the impression there was one, but I'm not seeing it yet.

Related to: https://github.com/prometheus-community/helm-charts/pull/2357

Imho it was available here: https://quay.io/organization/prometheus at least we should have had a successful GitHub action run with that image.
Or ist this the right repo?
https://hub.docker.com/r/prometheuscommunity/smartctl-exporter

the one here: https://hub.docker.com/r/prometheuscommunity/smartctl-exporter/tags still has the missing smartctl binary issue. :(
Can we get a new build please? would need to be tagged 0.7.1.

@SuperQ any chance we can see some effort on getting this fixed?
docker pull quay.io/prometheus/smartctl-exporter:v0.7.0

Error response from daemon: unauthorized: access to the requested resource is not authorized

+1
in the mean time, you can use: pnnlmiscscripts/smartctl-exporter:0.7-2

Prometheus Community exporters are under a different image repo.
docker pull quay.io/prometheuscommunity/smartctl-exporter:v0.7.0

@SuperQ
❯ docker pull quay.io/prometheuscommunity/smartctl-exporter:v0.7.0
Error response from daemon: unauthorized: access to the requested resource is not authorized


recipes-core: Drop packagegroup-arago-base

All packages are already part of meta-arago.
Hence, this bbappend is no longer needed.

Yep, LGTM

Applied with https://github.com/TexasInstruments/meta-tisdk/commit/f133aed69480ad5835830424570324ae7d52c402