Allow Usage.action to identify output types more flexibly.

Improvement Description
Allow Usage.action to identify output types more flexibly.
Current Behavior
Usage.action attempts to get an appropriate type string for outputs by searching for the output's name in action_f.signature. (ref)
Provenance replay has to monkeypatch this locally in order to support any archive version that doesn't track output-name in provenance, because it is impossible to give a variable a real output-name string to search with.
Proposed Behavior
If we support something like a snake-cased python type expression as a backup, we can still harvest correct UsageVariable type information.  E.g.
try:
    qiime_type = action_f.signature.outputs[param_name].qiime_type
except KeyError:
    # if param_name resembles a type expression, we can get the data we need from the param_spec
    for (p_name, p_spec) in action_f.signature.outputs.items():
        searchable_type_name = camel_to_snake(str(p_spec.qiime_type))
        if param_name == searchable_type_name:
            qiime_type = action_f.signature.outputs[p_name].qiime_type
            break

Comments
This change would probably only benefit automated tools like replay. I've pitched the idea here primarily because this is far enough up the chain of inheritance that it's not super easy for me to subclass around it without adding a bunch of superficial code to provenance_lib. I'm monkeypatching this locally just fine right now, so if it's not a good fit for Usage, that's AOK.

Hi @ChrisKeefe,
We do something like this for the Qiita QIIME 2 plugin to load all available QIIME 2 commands and match the qiime_types with the qiita_types.
Anyway, this caught my eye because I haven't seen a command where action_f.signature.outputs[param_name] will not work; do you have an example for this?
Thank you.

Two cases for you, @antgonza, but they only matter to me because my param_names are coming from captured provenance.

v0-v1 archive formats didn't capture an output-name in provenance, so provenance replay has to invent a param_name
the param_name has changed across plugin versions, so the user's QIIME 2 PluginManager expects a different param_name than was recorded in provenance.

Guaranteeing a match in the latter case is especially tricky, because one Result's provenance could have been captured across many different versions of QIIME 2, but the PluginManager only knows about one version of each plugin at a time.

Got it, so basically backward compatibility, right?
FWIW in Qiita we don't actually support backward compatibility; the reasoning is: to recreate exactly whatever analyses a user want, you have to have that plugin version installed (AKA you cannot exactly reproduce an analysis with an older or new version of that specific plugin); in other words a QIIME 2 2022.2 is different that any other version. However, I can see that this functionality might be different here.


[BACKLOG-36461] - Retaining the context of last opened file. Defaulting the user to user's home for new files in repository save

:warning: Build finished in 5m 50s
Build command:
mvn clean verify -B -e -Daudit -amd -pl \
plugins/file-open-save-new/core

:no_entry: Failed Tests
:cloud_with_lightning_and_rain: 3 test(s) failed:
org.pentaho.di.plugins.fileopensave.controllers.FileControllerTest.initializationError (click to expand)
org/hamcrest/SelfDescribing

org.pentaho.di.plugins.fileopensave.controllers.recent.RecentUtilsTest.initializationError (click to expand)
org/hamcrest/SelfDescribing

org.pentaho.di.plugins.fileopensave.providers.vfs.model.VFSFileTest.initializationError (click to expand)
org/hamcrest/SelfDescribing

Tests run: 3, Failures: 3, Skipped: 0    Test Results

:information_source:  This is an automatic message


feature: list datasets from data.gov.sg

This is hard because there is no dataset "search", only listing.

DGS Team replied, this feature should be live in a few months. So, till then.... need a fallback solution


Metadata isn't getting added to Letter

Summary
When making a LetterEditable object with a metadata field, and creating a new Letter, the metadata isn't attached.
const letterCreate = new LetterEditable({
  // Other necessary fields
  metadata: {
    internal_id: uuid
  }
});

await new LettersApi(config).create(letterCreate);

Expected Behavior
A new letter should be created in Lob with the same metadata that's specified.
Current Behavior
A new letter is created, but none of the metadata is present on it
Context (Environment)
I want to add our internal db ID for the document as metadata, so I can easily match webhook events to our internal document representation.

Typescript has officially been released on version 0.1.0 with this change. Thank you so much for bringing this issue to our attention. You can find the newest version on NPM.

Hi, I appreciate your quick fix. I'm having the same problem as I did in my previous request. When trying to download version 0.1.0 on either yarn or npm, I get the following error:
An unexpected error occurred<EMAIL_ADDRESS>Request failed \"404 Not Found\"".
404 Not Found - GET<EMAIL_ADDRESS>

@eeldar-attune  Apologies, we had a bad deployment release. Version 0.1.1 should be good to go now. You can find it here.

Works now, thank you


Fix the convert tools for mobilenetv2

Correct the converted keys for 'features.18' in the pretrained mobilenet_v2 from torchvision.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: xiaojieli0903:x: lixiaojielixiaojie seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


uzlib(trezor): fix compilation with clang

Btw, isn't it worth using -O3 for the whole lib/uzlib/tinflate.c file?
#pragma GCC optimize("O3")

That should work for all compilers (although this is ignored by Clang AFAIK).

I'm just trying to fix the build. @TychoVrahe have you tried this?^

yeah i tried optimizing the whole file - it increases the binary size by some 2kB, while most of the speed gains are from optimizing this one function, so it didn't seem like a good tradeoff.
We are in a bit better spot with flash space right now so maybe we can reconsider, but the conditional seems ok to me too.

Ok, let's use the proposed conditional then.


Update to Factorio 1.1.107

Updates the extractor to v1.1.104 (Current Stable)

Updates the extractor to v1.1.107 (Current Stable)

Didn't the graphics change as well?

I'll read back over the change log and make sure i didn't miss anything.  I just kinda updated the version and grabbed all the "exported" data from the extraction.  I didn't really think to check what changed between the versions.
For what it's worth, I haven't found any functionality issues while using the FBE

Usually I check the data.json just to be aware of any potentially problematic changes.

I'll update FBE to v2 soon.


Warning triangle text on ncRNA pages

Suggested text for a "warning triangle" associated with the ncRNA "genomic location" line of ncRNA features.
"As in most systems, fission yeast lncRNA most are cryptic, many may be non-functional. RNA-seq data have limitations for precise mapping of transcription start and termination site coordinates, hence features are currently approximate. Most lncRNAs in fission yeast are induced under perturbations or genetic conditions (most notably during late meiosis). Almost all lncRNAs are suppressed by 3 RNA-processing pathways: the nuclear exosome, cytoplasmic exonuclease, and RNAi. For more details on the relevance of  a specific RNA please follow the link to the source(s) (adjacent)."
Quite long
@bahler can you improve this so that we day the same with less text?

Revised text:
"Many lncRNAs are cryptic and the functions (if any) are mostly unknown. RNA-seq cannot precisely map transcription start and termination sites, hence features are currently approximate. Most lncRNAs in fission yeast are induced in certain conditions, like non-dividing cells and meiotic differentiation. In proliferating cells, most lncRNAs are suppressed by RNA-processing pathways. For more details on the relevance of a specific RNA please follow the link to the source(s) (adjacent)."
Best,
-Jürg
From: Val Wood @.>
Sent: 13 December 2022 11:57
To: pombase/website @.>
Cc: Bahler, Jurg @.>; Mention @.>
Subject: [pombase/website] waring triangle text on ncRNA pages (Issue #1978)
⚠ Caution: External sender
Suggested text for a "warning triangle" associated with the ncRNA "genomic location" line of ncRNA features.
"As in most systems, fission yeast lncRNA most are cryptic, many may be non-functional. RNA-seq data have limitations for precise mapping of transcription start and termination site coordinates, hence features are currently approximate. Most lncRNAs in fission yeast are induced under perturbations or genetic conditions (most notably during late meiosis). Almost all lncRNAs are suppressed by 3 RNA-processing pathways: the nuclear exosome, cytoplasmic exonuclease, and RNAi. For more details on the relevance of a specific RNA please follow the link to the source(s) (adjacent)."
Quite long
@bahlerhttps://github.com/bahler can you improve this so that we day the same with less text?
—
Reply to this email directly, view it on GitHubhttps://github.com/pombase/website/issues/1978, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADMTWVGHQQP5SADCHUOASWLWNBP75ANCNFSM6AAAAAAS5DXNYQ.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Perfect, thanks. Kim can you implement when you are back.
Thanks
Val

Hi Val.  Where should the warning icon be placed?  Before the "Source ..."?

The text only mentions lncRNAs so should the warning icon only appear on lncRNA gene pages?

Yes try that please..

on lncRNA and sncRNA (all currently ncRNA are lncRNA)

Sorry, I'm still a confused.  We have features of type sncRNA, lncRNA and ncRNA in Chado and on the website.  Should this warning appear on the ncRNA pages or just the sncRNA and lncRNA pages?

All sncRNA and lncRNA

How's this?  I'm mousing-over the icon but I couldn't capture the mouse pointer in the screenshot.

Looks good. I wonder if we should add to the final sentence.
"You can also inspect individual datasets in JBrowse."

This change is on the main site now.


Sheet: Propagate adapt context

Fixes https://github.com/tamagui/tamagui/issues/3024
Fixes https://github.com/tamagui/tamagui/issues/3071

Wrong target


Sharp crashes with invalid opcode in libvips-cpp.so.42

Sharp is a dependency of the Ghost CMS, used to resize image file uploads. But I am finding that sharp causes Ghost to crash when images are uploaded to the latest Ghost on Ubuntu and Debian.
I take a fresh Ubuntu focal installation and then follow the instructions at https://ghost.org/docs/install/ubuntu/ to install Ghost. That gives me Sharp version 0.29.3 running on NodeJS 16.13.2.
Ghost is up and running fine, but uploading an image to be resized causes Ghost to crash with the kernel trapping the following error:
ghost kernel: [248127.445076] traps: node[190951] trap invalid opcode ip:7f51fe938dfb sp:7ffcdffdfd60 error:0 in libvips-cpp.so.42[7f51fe62b000+aac000]
The problem occurs with any image upload, all calls to sharp to resize an image result in the invalid opcode error listed above.
What is the output of running npx envinfo --binaries --system?
System:
OS: Linux 5.4 Ubuntu 20.04.3 LTS (Focal Fossa)
CPU: (8) x64 AMD Opteron(tm) Processor 6128
Memory: 1.42 GB / 7.80 GB
Container: Yes
Shell: 5.0.17 - /bin/bash
Binaries:
Node: 16.13.2 - /usr/local/bin/node
npm: 8.1.2 - /usr/local/bin/npm
Here's the output from cat /proc/cpuinfo:
web101@ghost:~$ cat /proc/cpuinfo
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 16
model           : 9
model name      : AMD Opteron(tm) Processor 6128
stepping        : 1
microcode       : 0x10000d9
cpu MHz         : 2000.018
cache size      : 512 KB
physical id     : 0
siblings        : 1
core id         : 0
cpu cores       : 1
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 5
wp              : yes
flags           : fpu de tsc msr pae mce cx8 apic mca cmov pat clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow rep_good nopl cpuid extd_apicid pni cx16 popcnt hypervisor lahf_lm cmp_legacy abm sse4a misalignsse 3dnowprefetch vmmcall
bugs            : tlb_mmatch fxsave_leak null_seg amd_e400 spectre_v1 spectre_v2
bogomips        : 4000.03
TLB size        : 1024 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 48 bits physical, 48 bits virtual
power management:
There are 7 more vCPUs listed, but their specs are the same as above. Let me know if it would be useful to have the full output.

Please see #2723 (AMD Opteron 6128 CPUs were manufactured in or around 2010).

I hope this information helped. Please feel free to re-open with more details if further assistance is required.

Hi, yes it's clear to me now.
Running the system on a newer CPU has fixed the problem. Given that others seem to have had the same problem, I wonder if the CPU requirement should be listed somewhere on the project's README.md page.

Added via commit https://github.com/lovell/sharp/commit/24150eac897a31a18959580fbe3d441702661826

Excellent, cheers!


Adapt C compiler detection for VSI C on x86_64

VSI C on OpenVMS for x86_64 has a bit more information than on other
hardware.  This is no doubt because it's based on LLVM which leaves an
opening for cross compilation.
VSI C on Itanium:
$ CC/VERSION
VSI C V7.4-001 on OpenVMS IA64 V8.4-2L3

VSI C on x86_64:
$ CC/VERSION
VSI C x86-64 X7.4-843 (GEM 50XB9) on OpenVMS x86_64 V9.2-1

This pull request is ready to merge

Merged to master, 3.0, 3.1 and 3.2. Thank you.


Add has_no_root_node_jumps check

Check that the neurites have their first point not further than
radius_multiplier * soma radius from the soma center'''

This is required for the validator web service I've been asked to build


Story splash/intro special passage

A special passage that is shown to players before the normal starting passage and does not become part of the history.  Essentially, a splash or introduction screen.
My current idea on how it should work is that it would simply require any player interaction to move past—basically, the whole viewport would get the equivalent of an […].ariaClick() event handler.
Reasoning

To remove splash screens from the story history.
As a workaround for user activation requirements for media playback.

Others I'm likely forgetting at the moment.
Possible Names

StorySplash
StoryIntro

Other suggestions?

Closed in favor of the v3 issue: https://github.com/tmedwards/sugarcube-3-prealpha/issues/2
NOTE: The v3 repository is not yet public, so the above link probably will not work for you until it is.


build and dev error when trying to include includedRoutes from main.ts

Describe the bug
What i want to do
Use of environment variables managed by Vite following README#custom-routes-to-render
How i do it
Based on vitesse
// main.ts
import { ViteSSG } from 'vite-ssg'
import App from './App.vue'
...
export const createApp = ViteSSG(
  App,
  ...
)
export function includedRoutes(paths: string[]) {
  return paths
}

// vite.config.ts
import { defineConfig } from 'vite'
import { includedRoutes } from './src/main'
...
export default defineConfig({
  ...
  ssgOptions: {
    ...
    includedRoutes,
    ...
  },
})

Error encountered
// pnpm dev
No loader is configured for ".vue" files: src/App.vue
src/main.ts:5:16:
  5 │ import App from './App.vue'

// pnpm build
  let error = new Error(`${text}${summary}`);
              ^
Error: Build failed with 1 error:
src/main.ts:5:16: ERROR: No loader is configured for ".vue" files: src/App.vue

My question
I am maybe doing something wrong but i don't know what. This is a problem for me now because i need to use queries to get blog data => i need to have ~/ alias, import.meta.env ...
I hope someone has more information on this subject or can help me find a solution
Reproduction
based on vitesse adding previous code #how i do it
System Info
System:
    OS: macOS 13.2.1
    CPU: (8) arm64 Apple M2
    Memory: 1.43 GB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.8.0 - ~/.nvm/versions/node/v18.8.0/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 8.18.0 - ~/.nvm/versions/node/v18.8.0/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 112.0.5615.137
    Firefox: 108.0.1
    Safari: 16.3

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

could you offer a detail reproduction on codesandbox or stackblitz.com？

@justinzpc sure, you can clone https://github.com/jbaubree/vitesse and run pnpm build to see error

bro, i have found the problem ,you shouldn't export the "includedRoutes" fun from main.ts, move it to vite.config.ts plz,

i got a little busy last week, i just have time to check these code today

I want to use environment variables or ~ alias in my includedRoutes function and i can't do that from vite.config.ts. This is why i export includedRoutes from main.ts i'm following README 2nd part :
// main.ts

import { ViteSSG } from 'vite-ssg'
import App from './App.vue'

export const createApp = ViteSSG(
  App,
  { routes },
  ({ app, router, initialState }) => {
    // ...
  },
)
export async function includedRoutes(paths, routes) {
  // Sensitive key is managed by Vite - this would not be available inside
  // vite.config.js as it runs before the environment has been populated.
  const apiClient = new MyApiClient(import.meta.env.MY_API_KEY)

  return Promise.all(
    routes.flatMap(async (route) => {
      return route.name === 'Blog'
        ? (await apiClient.fetchBlogSlugs()).map(slug => `/blog/${slug}`)
        : route.path
    }),
  )
}

It's not working as expected

// Sensitive key is managed by Vite - this would not be available inside
// vite.config.js as it runs before the environment has been populated.
i thought these upon annotations means you needn't import "includedRoutes" to vite.config.ts and set it as property into the "ssgOptions"

@justinzpc i don't understand well what you mean, what should i do to use vite encironment in includedRoutes fonction?

Oh right ! Thank you @justinzpc ❤


Inherit standard configuration from parent package.json

Problem
standard currently does not check directories above cwd for package.json files containing standard configuration.
Example
Say I have A & A/B directories,  both with their own package.json files:
A
├── package.json
├── index.js
└── B
    ├── package.json
    └── index.js

Let's suppose B/index.js contains some syntax that requires the babel-eslint parser:
class A {
  // class properties are not supported by vanilla eslint
  static classProperty = 'ok'
}

console.log(A.classProperty)

standard will behave differently depending on what the current directory is:
> cd A
> standard B/index.js && echo 'ok'
ok
> cd B
> standard index.js && echo 'ok'
standard: Use JavaScript Standard Style (http://standardjs.com)
  /Users/timoxley/Projects/tests/standard-config/A/B/index.js:3:24: Parsing error: Unexpected token =

At first, not reading parent directories for configuration does seem like reasonable behaviour, though it differs from that of babel, which finds all the configs in all parents, then merges the results:
https://github.com/babel/babel/blob/210c3f7da92a7bd9b6da8fb57dac38996222fecd/packages/babel-core/src/transformation/file/options/build-config-chain.js#L26
While standard appears to just find the nearest package.json whether it has a "standard" config or not: https://github.com/Flet/standard-engine/blob/9ddbe6cce2dd43f3d888b64aede48ef3190d2e34/index.js#L136
Proposal
I suggest standard should follow the lead of babel here and inherit parent configs. I'd be happy if it just searched up until it found the first "standard" config, but I think perhaps a "standard" for config behaviour across all tools that read config from package.json/.rc files is better than minimalism. Ideally a reusable package could be used for keeping this consistent.

This sounds reasonable to me. We currently use find-root to find the nearest package.json. What does babel use?

Babel uses its own custom "config chain".
See https://github.com/babel/babel/blob/210c3f7da92a7bd9b6da8fb57dac38996222fecd/packages/babel-core/src/transformation/file/options/build-config-chain.js


en.json should map to file structure

organization of JSON object should be equivalent to the current fie structure.
Wrong:
"request_page": {
"greeting": "hello world"
}
Right:
"modules: {
containers: (
"NewRequestContainer": {
"greeting": "hello world"
}}}

ZenHub Information
This information is updated automatically. To modify it, please use ZenHub.

Not a real issue. Ths is an opinion about code structure .  It has been added to the CodingConventions doc


Group 5

Check this out

https://github.com/Counselllor/Counsellor-Web/pull/1347

My level 3 pr not getting merged


fix(es/minifier): Fix sequential inliner

Description:
cc @Austaras
I think we should fix this by improving infection analysis, as regression is way too much
Related issue:

Closes https://github.com/swc-project/swc/issues/6047.

Seems like many are caused by unresolved idents, maybe we could fix #6049 first?

I'll try

There are still lots of regressions

Oh, I mean we should stop at where callee is reassigned

Ah, thank you!
I did something wrong 🤣

It didn't work, and actually we were not skipping callee anyway

Well basically I thought it should be
// sequences.rs#1530
 Expr::Call(CallExpr {
                callee: Callee::Expr(b_callee),
                args: b_args,
                ..
            }) => {
                let is_this_undefined = b_callee.is_ident();
                trace_op!("seq: Try callee of call");

                if let Expr::Ident(i) = &**b_callee {
                    if let Some(usage) = self.data.vars.get(&i.to_id()) {
                        if usage.reassigned() {
                            return Ok(false);
                        }
                    }
                }

But that would cause lots of regressions too.


CORS issue with Pinata?

this doesnt seem to be an issue anymore (prob fixed by the fetchNFT thing)


Set Proxy-Authorization when needed

fixes #1145

Coverage remained the same at 87.457% when pulling 9fcb403970cdf42f3ccbf2e8fad162a8e2d80236 on timolehto:master into 94ee465682e90adb3f0b0edac99b4dc74d87cdc2 on node-red:master.

Coverage remained the same at 87.457% when pulling 9fcb403970cdf42f3ccbf2e8fad162a8e2d80236 on timolehto:master into 94ee465682e90adb3f0b0edac99b4dc74d87cdc2 on node-red:master.

Yes, parsing is done on line 74 by url module and it picks up the auth part just fine. I'm abusing this by reading the parsed auth property from the opts and converting it to basic auth Proxy-Authorization header which is what the http module expects for proxy authentication to work.

Is this going to get actually merged at some point?

Hi @timolehto - yes absolutely. In fact I can merge it now and it'll be in the imminent 0.17 release. Sorry for the delay!

👍

wow, that was a quick response :) 👍

apologies again for missing it... don't hesitate to kick us again if needed !


failed to determine the currently installed packages

Checks

[x] I have checked that this issue has not already been reported.

[x] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example
pixi run ...

Issue description
After a git pull with no modifications to pixi files:
❯ pixi run ...
  × failed to determine the currently installed packages for 'default'
  ├─▶ failed to parse '.../.pixi/envs/default/conda-meta/requests-2.31.0-pyhd8ed1ab_0.json'
  ╰─▶ Eof at character 0

I still have the broken .pixi folder around to help debugging.
Expected behavior
?

### Env broken for whatever reason?
❯ pixi run ...
...
    from scipy.ndimage import binary_dilation
E   ImportError: cannot import name 'binary_dilation' from 'scipy.ndimage' (unknown location)

### Attempt to reinstall
❯ rip .pixi/
❯ pixi run pytest -k 'Scan_3' -v
  × default: error installing/updating PyPI dependencies
  ├─▶ failed to determine the currently installed packages for .../.pixi/envs/default
  ├─▶ failed to parse '.../.pixi/envs/default/conda-meta/polars-1.12.0-py312h4b5da93_0.json'
  ╰─▶ Eof at character 0

### Next attempt
❯ rip .pixi/
❯ pixi run pytest -k 'Scan_3' -v
❯ echo $status
1

After another try it worked

In the original example, requests-2.31.0-pyhd8ed1ab_0.json is empty

Ooh I seem to be using an old version of pixi, something was messed up with Homebrew, I think this has been fixed


v0.4.0 Hangs when Collapsable side bar feature is enabled

Today when I open ynab it hangs and the screen is distorted. Then Chrome crashes. When I disable the extension, ynab works again.

So sorry about that! It seems the workaround is to disable the "Collapsable side bar" function. I'm right now working on a fix and 0.4.1 will be out very shortly.

I've just released 0.4.1 which I believe fixes the issue. Could you let me know if you still see this on 0.4.1?

Yes seems to work now.
On Wednesday, February 24, 2016, Kevin Brown<EMAIL_ADDRESS>wrote:

I've just released 0.4.1 which I believe fixes the issue. Could you let me
know if you still see this on 0.4.1?
—
Reply to this email directly or view it on GitHub
https://github.com/blargity/toolkit-for-ynab/issues/233#issuecomment-188222477
.

--
Alex

Great, thanks for confirming!


AD Recycle Bin

How do I actually enable the feature, specifically in Server 2019.  The section for how to enable AD Recycle Bin doesn't actually say how to do it, and has an article for Server 2008 in the link.  I looked in my roles and features on my server, and didn't see anything about AD Recycling Bin.

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

ID: fd5fd02e-6f34-8301-ac3d-023c8aa95fce
Version Independent ID: 8e12cb08-cd75-f52c-6e15-6b14a5adc3b3
Content: Azure AD Connect sync: Enable AD recycle bin
Content Source: articles/active-directory/hybrid/how-to-connect-sync-recycle-bin.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

@rconiv
Thanks for your feedback! We will investigate and update as appropriate.

Thanks for the feedback! I made a pull request to add the steps. https://github.com/MicrosoftDocs/azure-docs-pr/pull/169046
To enable the AD Recycling Bin, follow these steps:

Open the Server Manager.
Go to Tools and select the Active Directory Administrative Center.
Click on the local domain and select Enable Recycle Bin.

@billmath please review the pull request.


CNExT location: decode psuedo-FIPS codes for counties into their textual names

I.e NM 001 is Bernalillo. We have the last three digits, the first two are the state (NM==35).

99% datapoints addressed with a post-processing perl script - not posted in this repo yet.


Change extractZipArchive to optimistically save files to S3

extractZipArchive currently terminates on the first failure rather than uploading as many files as it can and then terminating with an error. The issue is due to using Promise.all without additional error handling.

Done in #4329


build: fix FromAsCasing warning from Dockerfile, for #6462 [skip ci]

The Issue

#6462
https://docs.docker.com/reference/build-checks/from-as-casing/

#1 WARN: FromAsCasing: 'as' and 'FROM' keywords' casing do not match (line 6)

How This PR Solves The Issue

uses the same casting for FROM ... AS ...
removes extra lines at the end of files
uses an indent of 4 spaces

Manual Testing Instructions
Automated Testing Overview

Release/Deployment Notes

Sure, I didn't start building anything here.


Test pr # 2

trying it out again

Can one of the admins verify this patch?

ok to test

test this please


Skipping tests if credentials don't exist

Why
Due to / Thanks to the way secrets are handled by Travis CI for open-source project like this, we cannot run the integration tests towards real Slack for pull requests. As that would cause the credentials to leak.
What
So we skip the tests when API credentials are unavailable.
And we continue to run these two tests if they are available - that is:

either it's a master run in Travis CI
or someone specifies the credentials manually in their local src/test/resources/application.conf

How
This is kind of lame with this one huge case/match. I haven't found a cleaner way in Scalatest. https://stackoverflow.com/q/32460295/118587 suggests it's doable, but:

I didn't try the Tags
the cancel or assume is not what we need here, as it causes a failure, not skipping of a test

Tested with and without the application.conf. Both pass. The former executes more tests.


Gradient checkpointing and ddp do not work together

Bug description
Am launching a script taht trains a model which works well when trained without ddp and using gradient checkpointing, or using ddp but no gradient checkpointing, using fabric too. However, when setting both ddp and gradient checkpointing, activate thorugh gradient_checkpointing_enable() function of huggingface, we get error
[rank0]:   File "/home/.../v2/lib/python3.10/site-packages/torch/autograd/graph.py", line 744, in _engine_run_backward
[rank0]:     return Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass
[rank0]: RuntimeError: expect_autograd_hooks_ INTERNAL ASSERT FAILED at "../torch/csrc/distributed/c10d/reducer.cpp":1591, please report a bug to PyTorch.

Scripts where launched with
fabric = Fabric(accelerator="gpu",
                    loggers=loggers,
                    precision=opt.precision,
                    strategy=DDPStrategy(process_group_backend="nccl", find_unused_parameters=False, static_graph=True)
                    )

When i launch with options strategy=DDPStrategy(process_group_backend="nccl", find_unused_parameters=True, static_graph=False), I get error instead:
[rank0]: Parameter at index 560 with name reader.decoder.transformer.h.11.mlp.c_proj.bias has been marked as ready twice. This means that multiple autograd engine  hooks have fired for this particular parameter during this iteration.

Thanks in advance for your help.
What version are you seeing the problem on?
v2.4
How to reproduce the bug
No response
Error messages and logs
# Error messages and logs here please

Environment

Current environment
#- PyTorch Lightning Version (e.g., 2.4.0):
#- PyTorch Version (e.g., 2.4):
#- Python version (e.g., 3.12):
#- OS (e.g., Linux):
#- CUDA/cuDNN version:
#- GPU models and configuration:
#- How you installed Lightning(`conda`, `pip`, source):

More info
No response

THank you @rubenweitzman, would you be able to provide a minimal reproduction? It will speed up finding a fix, thanks in advance!


Bug: UpdateMetadataByIndex

When there is an incorrect metadata file already in place, this function overwrites the file, occasionally leaving unwanted characters (which might result in an unparseable JSON file).
Fix: if file exists, it should be deleted in the beginning of this function, after the JSON data has been marshalled for saving later.

Issue fixed.


feat: add tracking widget

What is this
This PR adds a Tracking widget that takes in a simple list of DOM events (onClick, onSubmit, etc..) and calls the EventTracking track method with the provided data
How to use
Take event add_to_cart for example, we'd have something like the following:
/*
* product-template.liquid
* (I assume that every Shopify themes has this file)
*/

Checklist

[x] Implementation
[x] Unit test

The failing test is from overlay test, tried setting timeout to see if it can be resolved but no luck, maybe @zlatanpham can have another look.

I was initially skeptical that this should be a widget since it doesn't actually inject DOM and is just behaviour. However, habitat widgets give us an easy way to hand the customer transparent, declarative, configuration.

I've changed the tracking e2e test to a unit test because I feel like we're just really testing if the track method was called with the right event metadata.

I think Thanh's comment along with some Slack messages have revealed a fundamental misunderstanding about the API that we wish to design here. I'll need @JasonBerry to step in and help to clear up the best way of accomplishing what we want.
If a page has the following widget present:

Then what should happen is that click events fired on a DOM node matching the button#AddToCart selector should have an SearchIOAnalytics event add_to_cart fired on them. The hardest part of this is determining the correct queryId to submit the event with. We want to fire the add_to_cart event with the most recent queryId in which the user clicked on a this result item — a result item for the item which they are not adding to their cart.
@JasonBerry is the best way to do this, to simply call tracking.searchIOAnalytics.track(event, id, data)? My reading of the code at track is that it will look up the most recent result click for this item and use that queryId.
If this is the correct way to do this, I think we need two changes in sdk-js.

I note that it track only performs it's prevent event lookup for a small set of events, FUNNEL_ENTRY_TYPES which will need to be expanded for this PR to work.
I also note that the add-to-cart button will be clicked often for items which were navigated to via our search. Therefore firing a console.error when we can't find a queryId is probably the wrong move. I think I advocated the use of console.error previously. I believe we need an optional flag on track which will cause it to elicit a console.error when no queryId is found. We will use this flag internally when using track in a context where we expect a queryId to always exist.

I've spoken to Jason about this.
We shouldn't need a full context in order to submit tracking events.
This should work:
const tracking = new EventTracking(id);
tracking.track(event, id, data);

As you've noticed, this call can be a bit noisy (console.error). This noise was intentional, but we agree that it is overkill for this use-case.
When .track() is called, we use the unique id passed to look up previous interactions which have occurred using that same identifier. This is done in order to find the previously executed queryId which returned that result item. If one is found, that indicates that the user has previously interacted (clicked) on that item in a search result screen. Our use-cases for this lookup prior to this PR were all guaranteed. On a search result screen, not being able to find a queryId would be very strange and therefore merited a console.error. Now that we're using that same interface to perform ad-hoc event collection on items which may not have been navigated to via a search.io interface we need to quiet it down.
I'll make the change in sdk-js to only call console.error on event names we believe should be noisy.

I think the path forward is

I'll make changes in sdk-js and thread them through to sdk-react.
This PR will need to bump its sdk-react.
This PR needs to remove the context creation (instantiating a pipeline) and remove the use of useTracking. Instead, just instantiate the EventTracking interface directly.
Remove the arbitrary search query used to generate a queryId.

Some notes:

The tracking object needs to be passed to the Pipeline constructor so that the bootstrap method would be called which in turn properly set the searchIOAnalytics.
Running the tracking example in dev mode will fail due to the lack of queryId variable, this is known and is waiting for the update to propagate from sdk-js.


Finish PR 36 - Add Arbitrary-less law checks

Description of the change
Finishes #36 and fixes #35

Checklist:

[x] Added the change to the changelog's "Unreleased" section with a link to this PR and your username
[ ] Linked any existing issues or proposals that this pull request should close
[ ] Updated or added relevant documentation in the README and/or documentation directory
[ ] Added a test for the contribution (if applicable)

Can I get a :heavy_check_mark: ?


Get some Unit Tests and CI

I could use some help.  I have no idea how to test JS.

I use Mocha but there are several other popular unit test systems. What did you have in mind as far as priorities for developing tests?

Nothing too major.  In other code bases I try make some easy integration tests that emulate typical student interactions.  Then use code coverage reports to make sure I have hit 80-90% of the code.
This is a good example,
https://github.com/discreteoptimization/assignment/blob/master/test/submit_test.py
I no nothing about JS unit testing frameworks or how to do CI outside the browser, so your experience would be much appreciated!

Sure I can take a stab at it this weekend. Setting up the framework is fairly easy and Mocha is very straightforward.

I am using mocha.js for testing and blanketjs for code coverage. Do you have a preference as to how to include these in the project? Do you want to continue to load external libraries from a CDN or would you prefer to move these libraries into the project using Bower?

In light of modern web tools, I am a web-dev novice; so I'll trust your judgement on this one.
My feeling is that it is best to load the libraries via a CDN.  That way, it is one less tool that a would-be contributor would need to learn.
These are not mission critical tools so if the break due to an external library update that is not a huge deal.


Change two instances where we are using strcmp to use == as a follow …

…up to #26158.

@swift-ci smoke test

@swift-ci smoke test and merge

@swift-ci smoke test and merge

@swift-ci smoke test and merge

@swift-ci smoke test and merge

Seems that #26158 might have affected the Windows builds (https://ci-external.swift.org/job/oss-swift-windows-x86_64/709/). I'm going to check if this fixes them or we need something else.
/cc @compnerd
@swift-ci please test Windows platform

@drodriguez I think the problem is that MSVC is being MSVC and doing stupid things around constexpr. The getPrefixed thing can just remove the constexpr.


Add Naga dependency

By exposing Naga in gfx-hal we'll be able to have wgpu and gfx communicate the shaders without going through SPIR-V.
PR checklist:

[x] make succeeds (on *nix)
[ ] make reftests succeeds
[ ] tested examples with the following backends:

The controversial part here is that Naga is not optional. I tried to think of pros and cons.
Cons:

Naga needs more work anyway, it's not ready yet
Naga in gfx-hal isn't needed for any libraries that only depend on the gfx-hal, and do not care about Naga

Pros:

Naga will need to be ready at some point, replacing SPIRV-Cross. And it will need to be available for wgpu interop, so we might as well skip the stage where it's optional in the gfx-hal.
Naga by itself without features is super lightweight, it shouldn't affect the libraries too much. All the frontends and backends are gated by features.
The end user app will need to depend on gfx-hal backends, and probably not the Vulkan backend alone. So in the end those backends would require Naga anyway to do their translation (currently, only Metal backend supports this, optionally).
It's annoying in Cargo to say that naga dep is optional in a backend, in addition to requiring naga dep in the gfx-hal. This would require renaming the feature in the backend to be something else.

Unresolved question: how do we nicely specify Naga revision? It's needed everywhere: in gfx-hal, in each backend, in wgpu, etc, and all of them need to agree. We can't simply re-export Naga from gfx-hal, since every client will need to enable some of the features (i.e. Metal backend enables "mtl-out", wgpu enables "wgsl-in", etc).
One way to proceed is to just use the revisions. It's a bit clunky, since for the reader a revision is just a random set of symbols.
Another interesting way is to have tags in the Naga repo, and depend on those tags. E.g. it could be called gfx-1, gfx-2, etc, monotonically, as we update Naga dependency through the stack. I think that could work fine, at least better than with revisions only.

Using tags for now sounds good to me.
In the longer term, the Naga public API will stabilize which should allow us to release frequently anyway. This might allow us to switch off of the git dependency anyway, and still use patch to test fixes between Naga releases.

Discussed on the Matrix. Proceeding as is. Will keep in mind the option to 1) make it optional, and 2) to merge the entry points.
bors r=grovesNL


Is it possible to get Juniper and graphql-client working together?

I'm building a website that exposes a graphQL api but I would also like to use the graphQL api server-side. I assumed graphql-client would work with juniper since they are related projects but I can't seem to work out how to wire them up.
// I was hoping to do something like this

#[derive(GraphQLQuery)]
#[graphql(schema_path = "schema.graphql", query_path = "hello_query.graphql")]
struct HelloQuery;

let (res, _errors) = juniper::execute(
    "query { hello }",
     None,
     &schema,
     &juniper::Variables::new(),
     &ctx,
).unwrap();

let hello: hello_query::ResponseData = res

// This is the best I have so far converting to json and back again

#[derive(GraphQLQuery)]
#[graphql(schema_path = "schema.graphql", query_path = "hello_query.graphql")]
struct HelloQuery;

let (res, _errors) = juniper::execute(
    "query { hello }",
     None,
     &schema,
     &juniper::Variables::new(),
     &ctx,
).unwrap();

let hello: hello_query::ResponseData =
        serde_json::from_str(&serde_json::to_string(&res).unwrap()).unwrap();

Also, the Juniper Value does not work with serde_json::from_value(res)

When https://github.com/graphql-rust/juniper/pull/324 it lands should be easier in 2 passes. I'm not sure we can do it at compile time...juniper needs to build and know the schema before the client can be generated.


A single federated cluster can stop propagation of a type for all clusters if it does not have the specified resource version.

A single federated cluster can stop propagation of a type for all clusters if it does not have a particular resource version.
And a question - any good strategies for handling cluster estates that could have multiple versions of a resource in circulation (e.g. v1beta1 and v1 CRDs)
Editing the target type version in the federated type config to v1beta1 (lowest common denominator) appears to work around this ok (tbc), but it's still worrying a single cluster could stop all federation working - seems like this shouldn't be the expected behaviour.
What happened:
Run a federation control plane at kube version 1.16
Enabled federation of CRDs (v1)
Joined another 1.16 cluster - confirmed CRDs and CRs of that type are being propagated ok
Joined a 1.15 cluster - CRDs+CRs not propagated to the 1.15 cluster (CRDs at version v1beta1). All propagation of CRDs and CRs of the same type stopped working for the 1.16 cluster as well.
Logs for the controller manager show msgs like:
E0630 07:13:47.048845       1 reflector.go:153] pkg/mod/k8s.io/client-go@v0.17.3/tools/cache/reflector.go:105: Failed to list apiextensions.k8s.io/v1, Kind=CustomResourceDefinition: the server could not find the requested resource

What you expected to happen:
I expected v1 CRDs not to propagate to the 1.15 cluster, however I did not expect the propagation of all CRDs to all clusters to stop working.
How to reproduce it (as minimally and precisely as possible):
Run a federation control plane at kube version 1.16+
Enabled federation of v1 CRDs
Create a Federated CRD, and a CR of that type with placement that will match all clusters
Join another 1.16 cluster - confirmed CRD and CR are being propagated ok
Join a 1.15 cluster - expect the CRD and CR not to be propagated
Create a new federated CRD, or a CR of the original type - these should still be propagated to the 1.16 cluster but I have observed they are not.
Anything else we need to know?:
Environment:

Kubernetes version 1.16 for the fed control plane, 1.15- for one or more federated clusters
KubeFed version 0.3.0
Scope of installation Cluster
AWS/EKS

/kind bug

@dgorst Thanks for your feedback.
Let me reproduce it locally and then get back to you.

@dgorst
Cloud you please help confirm if this the minimum step for reproducing?
Prepare clusters:
[root@ecs-d8b6 kubefed]# kubectl -n kube-federation-system get kubefedclusters
NAME       AGE     READY
cluster1   9d      True // v1.17.4  (apiextensions.k8s.io/v1)  `this is the host cluster`
cluster2   9d      True // v1.17.4 (apiextensions.k8s.io/v1)
cluster3   3h10m   True // v1.15.0 (apiextensions.k8s.io/`v1beta1`)

Operation Steps:

create a CRD, such as crontabs.stable.example.com which apiVersion is apiextensions.k8s.io/v1beta1
enable CRD by command: kubefedctl enable customresourcedefinitions
federate CRD by command: kubefedctl federate crd crontabs.stable.example.com

Result:
[root@ecs-d8b6 kubefed]# kubectl get crds crontabs.stable.example.com --context cluster1
NAME                          CREATED AT
crontabs.stable.example.com   2020-07-01T12:50:31Z
[root@ecs-d8b6 kubefed]# kubectl get crds crontabs.stable.example.com --context cluster2
Error from server (NotFound): customresourcedefinitions.apiextensions.k8s.io "crontabs.stable.example.com" not found
[root@ecs-d8b6 kubefed]# kubectl get crds crontabs.stable.example.com --context cluster3
Error from server (NotFound): customresourcedefinitions.apiextensions.k8s.io "crontabs.stable.example.com" not found

You expected the CRD will be propagated to cluster2 and ignore the cluster3, right?

Yes exactly @RainbowMango 👍
It feels like the blast radius from a single (tbf misconfigured) cluster, should not impact propagation to the good clusters. So in your example, yes I don't expect a v1 CRD in cluster1 to be propagated to cluster3, but I would expect it to continue to be propagated to cluster2.
I mention a CR of the type of the CRD as that would also stop propagating at the point the 1.15 cluster is joined. But it's the same issue I guess (the CRD doesn't get propagated because it can't list v1/crds, so it also can't list that type either)

@dgorst
I did some investigation and found that the FederatedCustomResourceDefinition sync controller totally be blocked as one of the informers can't finish its sync process.
The following check keeps failing.
https://github.com/kubernetes-sigs/kubefed/blob/bf67d02369e9b2d93281f8224747b94afab3170e/pkg/controller/sync/controller.go#L235-L238
I agree with you that the propagation process should ignore bad clusters.
Let's see how to solve this.

Thanks @RainbowMango for recreating and confirming 👍
Happy to have a stab at resolving this if that'll help? (caveat: I'm new to the kubefed codebase so may need to reach on slack with some questions though!)

I've tried a workaround locally, but the community has discussed a better solution.
@hectorj2f @jimmidyson @irfanurrehman
Could you please take a look? If the solution that changes FederatedTypeConfigStatus OK for you?

@RainbowMango thanks for tracking this. IMO the solution proposed by pmorie as per the link you mentioned is completely legit and can be implemented. As far as I understand @font might not be available to complete it.

Given the implementation is a little bit complicated(API change, controller adopt, testing, etc...), I'd like to set up an umbrella issue and split this to several tasks and then run it by iteration. @dgorst you are welcome and feel free to pick any iterated items you interested in.
How do you say? @irfanurrehman , and If it's ok for you, can you help review the following PRs?

Awsome suggestion @RainbowMango. I can certainly review the same.
If time permits, I will take up some tasks too.

Thanks for taking care of this @RainbowMango. It sounds good to me too. Share the action items to see if we can help somehow.

Just sent a draft issue #1252. I have started some work locally, so I'll take the first task.
Thanks for your support @irfanurrehman @hectorj2f .

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale


AttributeError: module 'tensorflow' has no attribute 'compat'

AttributeError                            Traceback (most recent call last)
 in
1 get_ipython().run_line_magic('matplotlib', 'inline')
2 import matplotlib.pyplot as plt
----> 3 import tensorflow as tf
4 import numpy as np
5 import pandas as pd
~\miniconda3\envs\tensorflow\lib\site-packages\tensorflow_init_.py in
99
100 # We still need all the names that are toplevel on tensorflow_core
--> 101 from tensorflow_core import *
102
103 # These should not be visible in the main tf module.
~\miniconda3\envs\tensorflow\lib\site-packages\tensorflow_core_init_.py in
44 from . _api.v2 import autograph
45 from . _api.v2 import bitwise
---> 46 from . _api.v2 import compat
47 from . _api.v2 import config
48 from . _api.v2 import data
~\miniconda3\envs\tensorflow\lib\site-packages\tensorflow_core_api\v2\compat_init_.py in
37 import sys as _sys
38
---> 39 from . import v1
40 from . import v2
41 from tensorflow.python.compat.compat import forward_compatibility_horizon
~\miniconda3\envs\tensorflow\lib\site-packages\tensorflow_core_api\v2\compat\v1_init_.py in
30 from . import autograph
31 from . import bitwise
---> 32 from . import compat
33 from . import config
34 from . import data
~\miniconda3\envs\tensorflow\lib\site-packages\tensorflow_core_api\v2\compat\v1\compat_init_.py in
37 import sys as _sys
38
---> 39 from . import v1
40 from . import v2
41 from tensorflow.python.compat.compat import forward_compatibility_horizon
~\miniconda3\envs\tensorflow\lib\site-packages\tensorflow_core_api\v2\compat\v1\compat\v1_init_.py in
27
28 from . import compat
---> 29 from tensorflow._api.v2.compat.v1 import app
30 from tensorflow._api.v2.compat.v1 import audio
31 from tensorflow._api.v2.compat.v1 import autograph
~\miniconda3\envs\tensorflow\lib\site-packages\tensorflow_core_api\v2\compat_init_.py in
37 import sys as _sys
38
---> 39 from . import v1
40 from . import v2
41 from tensorflow.python.compat.compat import forward_compatibility_horizon
~\miniconda3\envs\tensorflow\lib\site-packages\tensorflow_core_api\v2\compat\v1_init_.py in
30 from . import autograph
31 from . import bitwise
---> 32 from . import compat
33 from . import config
34 from . import data
~\miniconda3\envs\tensorflow\lib\site-packages\tensorflow_core_api\v2\compat\v1\compat_init_.py in
37 import sys as _sys
38
---> 39 from . import v1
40 from . import v2
41 from tensorflow.python.compat.compat import forward_compatibility_horizon
~\miniconda3\envs\tensorflow\lib\site-packages\tensorflow_core_api\v2\compat\v1\compat\v1_init_.py in
665 _current_module = _sys.modules[name]
666 try:
--> 667   from tensorflow_estimator.python.estimator.api._v1 import estimator
668   _current_module.path = (
669       [_module_util.get_parent_dir(estimator)] + _current_module.path)
~\AppData\Roaming\Python\Python37\site-packages\tensorflow_estimator_init_.py in
8 import sys as _sys
9
---> 10 from tensorflow_estimator._api.v1 import estimator
11
12 del _print_function
~\AppData\Roaming\Python\Python37\site-packages\tensorflow_estimator_api\v1\estimator_init_.py in
8 import sys as _sys
9
---> 10 from tensorflow_estimator._api.v1.estimator import experimental
11 from tensorflow_estimator._api.v1.estimator import export
12 from tensorflow_estimator._api.v1.estimator import inputs
~\AppData\Roaming\Python\Python37\site-packages\tensorflow_estimator_api\v1\estimator\experimental_init_.py in
8 import sys as _sys
9
---> 10 from tensorflow_estimator.python.estimator.canned.dnn import dnn_logit_fn_builder
11 from tensorflow_estimator.python.estimator.canned.kmeans import KMeansClustering as KMeans
12 from tensorflow_estimator.python.estimator.canned.linear import LinearSDCA
~\AppData\Roaming\Python\Python37\site-packages\tensorflow_estimator\python\estimator\canned\dnn.py in
31 from tensorflow.python.keras.utils import losses_utils
32 from tensorflow.python.util.tf_export import estimator_export
---> 33 from tensorflow_estimator.python.estimator import estimator
34 from tensorflow_estimator.python.estimator.canned import head as head_lib
35 from tensorflow_estimator.python.estimator.canned import optimizers
~\AppData\Roaming\Python\Python37\site-packages\tensorflow_estimator\python\estimator\estimator.py in
51 from tensorflow_estimator.python.estimator import model_fn as model_fn_lib
52 from tensorflow_estimator.python.estimator import run_config
---> 53 from tensorflow_estimator.python.estimator import util as estimator_util
54 from tensorflow_estimator.python.estimator.export import export_lib
55 from tensorflow_estimator.python.estimator.mode_keys import ModeKeys
~\AppData\Roaming\Python\Python37\site-packages\tensorflow_estimator\python\estimator\util.py in
73
74
---> 75 class _DatasetInitializerHook(tf.compat.v1.train.SessionRunHook):
76   """Creates a SessionRunHook that initializes the passed iterator."""
77
AttributeError: module 'tensorflow' has no attribute 'compat'

Hi everyone
after a long attempt to install tensorflow gpu version by following this tutorial:
https://www.youtube.com/watch?v=qrkEYf-YDyI&t=295s
I always find myself facing the above error. Can someone please help me?

What is the TF version you are trying to install? Also what steps did you follow?

You can try uninstalling and re-installing TensorFlow. If that does not work, check this link https://www.tensorflow.org/guide/migrate

What is the TF version you are trying to install? Also what steps did you follow?

At first I uninstalled anaconda and all the NVIDIA programs I had before, to start over from scratch.
Then I followed every step of this tutorial in detail:
https://www.youtube.com/watch?v=qrkEYf-YDyI
Step 1: I have NVIDIA Geforce GTX 1050 Ti, I installed the GTX 1650 driver
Step 2: I downloaded the updated Setup Script provided in https://github.com/jeffheaton/t81_558_deep_learning
To search for compatible version of Tensorflow 2.1.0:  https://www.tensorflow.org/install/gpu?hl=fr
Step 3: I installed CUDA Toolkit 10.1
Step 4: I installed cuDNN  7.6.5 for Cuda 10.1
I've added  all the necessary paths in my path environment
Step 5: I installed TensorRT 6.0
Step 6: Once I installed miniconda,  i did the following setup commands using my command prompt:
-conda
-conda install jupyter
-Once jupyter installation is done, I run the installaton script downloaded in step 2 using this command dir *.yml.
Then, i run this command: conda env create -v -f tensorflow-gpu.yml, It took me a long time.
Later I used "conda env create -f tensorflow-gpu.yml". Again, several things have been installed.
Just after i run: python -m ipykernel install --user --name tensorflow --display-name "Python 3.7 (tensorflow)" . Then python
Once tensorflow activated using "conda activate tensorflow", I get the error on top when I try to import Tensorflow as tf

You can try uninstalling and re-installing TensorFlow. Also, check this link https://www.tensorflow.org/guide/migrate

I'm still getting the same error, even with the reinstallation of tensorflow using pip.

You can follow the steps mentioned in the article below and check if it works.
https://towardsdatascience.com/tensorflow-gpu-installation-made-easy-use-conda-instead-of-pip-52e5249374bc
If it does not work, try pip install tensorflow==2.1. Found this here: https://github.com/tensorflow/tensorflow/issues/37525.

You can try uninstalling and re-installing TensorFlow. Also, check this link https://www.tensorflow.org/guide/migrate

I'm still getting the same error, even with the reinstallation of tensorflow using pip.

You can follow the steps mentioned in the article below and check if it works.
https://towardsdatascience.com/tensorflow-gpu-installation-made-easy-use-conda-instead-of-pip-52e5249374bc
If it does not work, try pip install tensorflow==2.1. Found this here: #37525.

You can try uninstalling and re-installing TensorFlow. Also, check this link https://www.tensorflow.org/guide/migrate

I'm still getting the same error, even with the reinstallation of tensorflow using pip.

Same problem even with pip install tensorflow==2.1  ! Sorry, i already saw that issue

the steps mentioned in the article

Thank you for this article. I will follow these steps

Please properly fill in issue template and use the proper Markdown formatting around errors and code blocks.

I have the same exact issue Here is my post I cant find a working solution for this issue
https://stackoverflow.com/questions/62622704/attributeerror-module-tensorflow-has-no-attribute-compat-when-loading-tf-co
In google I see post to install MV C++ i already have VS 2019 installed

Same issue for us.
We have installed the same combo on another machine ,,, it works.
Here we have a notebook with internal graphics card and one additional GTX 1650
GTX driver: 442.70
CUDA 10.1
cuDNN <IP_ADDRESS>
TensorRT 6.0
system path changed like specified
We are using anaconda for test purpose.
packages installed all via conda install - no pip.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you.

Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!

After "conda install tensorflow-estimator==2.1.0", everything works fine for me too .

ISSUE FIXED for me
Indeed the command "conda install tensorflow-gpu==2.1.0" installed version 2.2.0 of tensorflow-estimator.
After "conda install tensorflow-estimator==2.1.0" everything works fine

Thanks for your solution! It works for me too.


Add token/rust: spl-token-api

Right now spl-token have cli and JS API. This proposal is about add a nice Rust API for tokens management which can be done through solana_client::rpc_client::RpcClient and solana_program_test::BanksClient. This API can especially be useful for writing tests with solana_program_test.
This is only a small prototype, if a package will be approved I'll finish PR.

Yes please, this would be great! Here's a direction I think would work nicely:

This becomes the spl-token-client crate (analogous to the solana-client crate)
Longer-term spl-token-cli gets ported to use spl-token-client

Hi @fanatid , I'd love to see this land. Are you available to help get it wrapped up?
I can also take it over, if you've moved on to other things.

@CriesofCarrots would happy to help with this PR :slightly_smiling_face:

Looks like something is wrong in solana-program-test:1.8.1.
I added println! locally and

request mint account info, supply is 1
mint amount 1 and client returned ok
request mint account info again, supply is 1

Looks like something is wrong in solana-program-test:1.8.1. I added println! locally and
1. request mint account info, supply is 1

2. mint amount 1 and client returned ok

3. request mint account info again, supply is 1

Hm, I'll take a look tomorrow

Also, it's very strange but I receive error only with an empty target directory, if I run already compiled test binary everything is ok.

Hey, @fanatid , so the set_authority test has a race in it that is not obvious.
Since the set_authority test attempts the same mint operation here and here, if those transactions get the same blockhash, they end up identical. It turns out that the BanksClient/Server doesn't return an error when asked to process the same transaction a 2nd time; it hands the duplicate transaction off to a Bank, but then finds the original successful status regardless of the fact that the duplicate was not committed.
The race is that if the Token client has happened to get a new blockhash for the second mint operation, the transactions are not identical, and all is well. If not (because BanksClient is still returning the original blockhash), the transactions are identical, and the test's assert!(is_err) will fail. ProgramTest seems to move somewhat slower on the CI machine or when running the tests in parallel, so this failure occurs more often.
Anyway, that's probably more detail than you wanted.
The short-term fix is to twiddle one of the mint operations so that they aren't the same. I'll make a suggest above.
This issue describes the more comprehensive fix to BanksServer that we are looking at: https://github.com/solana-labs/solana/issues/22029

Thank you for the explanation @CriesofCarrots! I thought about race conditions but did not understand why the test fails only with an empty target directory and is always ok with compiled binary.


Speech Demo

Created a demo using speech recognition and speech synthesis called "Adventure Blockly." Uses custom blocks to listen to user input, generate speech, and change images and text on the screen. Acts as a sandbox area to create new projects, and comes with several prebuilt demos. Uses the JS Interpreter to asynchronously block until a block is done executing (has listened for user input, generated speech, displayed an image, etc.). Currently only Chrome fully supports speech recognition and speech synthesis (Firefox coming soon).

This change is

+@vicng

Review status: 0 of 23 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Workload Details page UI issues

Rancher versions: 2.0 master 3/1
Results:

[x] Type: None floating in middle of page

[x] Expanding Service Log causes page to hang - Error in dev tools: Error in dev tools type.js:105 Uncaught Error: Unknown link

[x] Annotations, Scaling/Upgrade Policy & Volumes section missing

[x] Can we have order in details page be the same as the Add Workload page itself

[x] Add workload type and Namespace info

[x] All sections are not being filled out with their proper information

Version - 2.0 master 3/6
Verified fixed


Add handleFindOne method

to handle get requests with a specific id.
like
/api/v1/profiles/1

will return a record with id 1.

@Marthyn .. can you give me use case for the handleFindOne .. it's interesting because I think I used to have that method, but I took it out a long time ago because I thought people could do:
FactoryGuy.make('user');
store.find('user', user.id).then(function(user) { // blah });

for this case.

True, but for example a reload on that object will still trigger an api request. I found in our app that even though we created the object with factoryguy there were still requests occurring, which we used to catch with pretender but we want to switch.

Oh boy .. totally forgot about reload .. got it.

Are you using bower? If so you can get this code by updating since its now in master branch. If not (using gem) let me know and I will make new release version.

@Marthyn .. and thanks for updating the readme documentation ( almost no one does that )

We're using the gem :)

v0.9.4 gem  is now ready

Thanks! Another use case i found btw is this:
self.transitionToRoute('chapter', self.get('model.id'));
you transition to the id of an object, instead of to the object itself. So it forces a reload.

Interesting .. I have never done that in a transition .. only passed model .. good to know.


Where do we enforce UTF-8 JSON?

Spun off from #66, where “All configuration JSON MUST be encoded in UTF-8” is checked.  And it seems to be:
$ ./ocitools generate
$ iconv -f UTF-8 -t UTF-16 config.json -o config-16.json
$ mv config-16.json config.json
$ file config.json
config.json: Little-endian UTF-16 Unicode text
$ ./ocitools validate --path .
FATA[0000] invalid character 'ÿ' looking for beginning of value

But I can't find Go docs on what input encodings are supported or UTF references in ocitools:
$ git grep -i utf origin/master
Binary file origin/master:rootfs.tar.gz matches

The Go docs reference RFC 4627, and the RFC explains how to detect the encoding, but maybe Go doesn't support that yet?  Can someone with more Go+JSON experience explain how this works?

@wking my mistake, I just update #66, ocitools has not verify utf8 encoding yet.
I test it locally by using https://golang.org/pkg/unicode/utf8/#Valid. It works well.
In my test, I add a Chinese word  "/主目录" to CWD field in config.json and convert it to gb18030.
utf8.Valid returns false.


Prepare infrastructure for hand Mk5 documentation.

As per title.

All good except for the placeholder 😉
Thanks.

Would you mind removing it?
Done


Does it allow index.tsx as the entry point?

Hi! First, thanks for the awesome plugin, it's certainly what I was looking for.
I have a question: is the entry point pages/index.mdx or does it allow regular pages/index.tsx?
Right now I have a small website with a few non-doc pages and a doc-specific area (this is where I intend to use Smooth Doc). I'd like to know if it's possible to have the regular entry point/website with *.tsx and the docs with the *.mdx extension, or must I convert my *.tsx to *.mdx?
Thank you!

I don't know if TypeScript is supported or no actually, I would say no.


Compile issue for Android

ran into the below error when trying to compile Android. Does anyone know to fix that?
org.gradle.api.ProjectConfigurationException: A problem occurred configuring project ':react-native-month-year-picker'
Caused by: org.gradle.api.artifacts.UnknownConfigurationException: Configuration with name 'compile' not found.

I have same problem.

fixed on #140


Create upchiapas

they offer a software developer degree
http://www.upchiapas.edu.mx/media/40/Ingenieria_en_Desarrollo_de_Software.php
proof of mail being used for the students
http://www.upchiapas.edu.mx/media/62/Correo_Institucional.php

@mwleinad Thank you for the request which contains all the necessary information. Could you please rename the file path from lib/domains/mx/edu/upchiapas to lib/domains/mx/edu/upchiapas.txt to reflect this repository rules? Thank you!

Done, thanks!
From: Philip Torchinsky<EMAIL_ADDRESS>Sent: Friday, April 22, 2016 10:30 AM
To: JetBrains/swot<EMAIL_ADDRESS>Cc: mwleinad<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [JetBrains/swot] Create upchiapas (#1919)
@mwleinad https://github.com/mwleinad  Thank you for the request which contains all the necessary information. Could you please rename the file path from lib/domains/mx/edu/upchiapas to lib/domains/mx/edu/upchiapas.txt to reflect this repository rules? Thank you!
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub https://github.com/JetBrains/swot/pull/1919#issuecomment-213474830 https://github.com/notifications/beacon/AOccrn6G5YqjThGcv_W8cSaFD4fxTG3pks5p6OlngaJpZM4IL1q0.gif

@mwleinad Thank you! Pull request merged.


add nix flake install instructions to readme

Thought I'd share some experiences with how I got this library working in NixOS using nix flakes. This should work fine in other Linux distributions, but I don't have a way to test it in OS-X so minor changes may be needed for that. For example, LD_LIBRARY_PATH may need to change in that OS. Let me know what you think!

Hello @willbush ,
thanks a lot for taking the time to contribute and sharing your experience with others. I myself have never worked with this packet manager before, so I certainly could not have provided this information.
 I am also unable to maintain and update this information myself, because I am not competent with regards to NixOS. I wonder if this kind of information is better suited for a wiki?
I started one here: https://github.com/pacman82/odbc-api.wiki.git
Do not worry about how to organize the information in there, yet. I would suggest to start a new page about how to setup odbc and drivers with nix flake and link it top level. I would then link from the Readme into the wiki.
Cheers, Markus

@pacman82 Putting it in a wiki makes sense. I'm looking at https://github.com/pacman82/odbc-api/wiki and I don't see an edit or new page button that I usually see on other wikis. I think perhaps permissions have to be modified?

[...] and I don't see an edit or new page button that I usually see on other wikis. I think perhaps permissions have to be modified?

I am new to GitHub wikis as well I do not know how to change permissions for the web editor. Happy to learn about it if you should know more.
I copied your manual to the wiki at https://github.com/pacman82/odbc-api/wiki/Installing-unix-odbc-and-odbc-driver-in-NixOS-using-nix-flakes

edit: Just found an option in the settings. Could you edit the wiki now?

Yep! I can edit it now. Thanks! I'm going to make some edits soon. I've been playing around with this more and realized not including unixODBC as a build input was causing a link error for me:
= note: /nix/store/8qm6sjqa09a03glzmafprpp69k74l4lm-binutils-2.40/bin/ld: cannot find -lodbc: No such file or directory
          collect2: error: ld returned 1 exit status

Also, I'm finding it annoying putting odbcinst.ini in the target folder because cargo clean blows it away and the nix shell hook doesn't run in that case. I think putting it in ./ and adding it to .gitignore is better.

I made the edit. It's my first time using GitHub wiki also. I was expecting it to go into a pending approval state, but it seemed to update right away. I'll close this PR and make another with a single commit linking to the wiki.

Thank you for your time and effort!


sap.ui.table.Table: When scrolling, variable row heights alter table height

OpenUI5 version: latest
Browser/version (+device/version): All common browsers, latest versions
Any other tested browsers/devices(OK/FAIL):
URL (minimal example if possible): http://jsbin.com/zuzeye/6/edit?html,output
User/password (if required and possible - do not post any confidential information here):
Steps to reproduce the problem:
1.Use scrollbar to scroll down through the list.
2.Note that when rows with word-wrapped content in column 1 come into view, the row height is adjusted, and the table height is also adjusted.
3.Note that when those rows are scrolled out of view, the table height returns to the original size.
What is the expected result? Expected that the table height would remain consistent during the scroll.
What happens instead? The table height adjusts to accommodate the requested 5 visible rows, even though that alters the table height. This leads to an annoying user experience, especially on a page with much more content.
Any other information? (attach screenshot if possible)

Hello cmastandrea,
thanks for reporting this. I created an internal ticket for reference:<PHONE_NUMBER>
We will analyze this bug and get back to you as soon as possible.
Kind Regards,
Michael

Hi cmastandrea,
unfortunately we can't provide a fix here due to how the table is designed to work, let me try to give some details:
The tables of the sap.ui.table library aim for huge amount of data (i.e. lots of rows). Since it would break the performance to have own controls for each row, the table simply reuses the controls of the rows. It's just the context which is changed by scrolling. Since there is no real scroll area, the table can just only take the length of the binding, the number of visible rows of the table and the current height of the table (influenced by the controls of the row template and their current content) and calculate a scrollbar length which gets applied. This happens in a delayedCall of 250ms - therefore it can happen in unlucky circumstances that the scrollbar length is not set correctly. However, when the row height remains stable, this delayedCall gives a real performance boost. Maybe you've noticed that the table never clips a row, it always shows the complete control - this exactly due to the concept of reusing controls.
I understand that you dislike the current behavior of changing table height, scrollbar length and sometimes not reaching the last row of the table (caused by different row heights). Hence I'd propose to use the sap.m.Table for variable row heights. The sap.m.Table could be placed inside a scroll container with a fixed height. However, the sap.m.Table is not meant for mass-data since it would render the complete data as a table. You can reduce the margins of the controls inside the sap.m.Table by setting the style class sapUiSizeCompact to make the m.Table better fit on desktops.
Best regards
Sebastian

Hi cmastandrea,
with Sebastian's comment, I would like to close this issue. Please reopen if you don't agree.
Best Regards,
Martin


Error: You attempted to access "nodeType" on a factory manager created by container#factoryFor. "nodeType" is not a member of a factory manager.

Originally reported in https://github.com/emberjs/ember.js/issues/15033 and https://github.com/testem/testem/issues/1105.
This error is emitted from here when Testem tries to read value.nodeType.
Error: You attempted to access "nodeType" on a factory manager created by container#factoryFor. "nodeType" is not a member of a factory manager.
    at Object.get (index.js:27)
    at derez (testem.js:70)
    at derez (testem.js:108)
    at derez (testem.js:108)
    at derez (testem.js:108)
    at derez (testem.js:99)
    at derez (testem.js:108)
    at decycle (testem.js:116)
    at Object.serializeMessage (testem.js:906)
    at Object.sendMessageToIframe (testem.js:840)

Offending line in Testem: public/testem/decycle.js#L67.
I'm unable to create a minimal reproduction scenario, but here are some findings:
// component => a class instance with cyclic references
// component.serialize() => a flat POJO

console.log(comment); // Works. Logs a class instance with cyclic dependencies.
console.log(comment.serialize()); // Works. Logs a flat POJO.
console.log(JSON.stringify(comment.serialize())); // Works, logs a string.
console.log(comment, comment.serialize()); // Crashes with the above error
console.log(comment, JSON.stringify(comment.serialize())); // Also crashes

PS You can't even imagine how frustrating this has been. The issue was appearing out of nowhere and then, after hours of frustration, disappearing into the blue. Every time I attributed the issue and fix to an unrelated change in my code. Testem trolled me into becoming one of those superstitious pigeons: I was resolving it by changing store.createRecord to store.push, by cleaning tmp/ and dist/, etc.
I would never even consider that the console.log invocation itself was the reason. My developer instinct was telling me to ignore it, believing it has no side effects. The stack trace never linked to the offending line, even with the Async checkbox enabled.

If I had not read this, I would not have realized that the error was because of console.log!

Just ran into this in a new project on latest Ember CLI beta with Mocha. Luckily, this project is open source. I've pushed a reproduction here:

repo: bread-maker/bread-maker-ember-frontend
branch: ember-factory-for-polyfill-issue-9
run with: ember t -s --no-launch -f "should render all fields"
Travis: https://travis-ci.org/bread-maker/bread-maker-ember-frontend/builds/281614009#L965

@rwjblue This issue has got some upvotes, are you gonna have a look?

offending line: tests/acceptance/program-test.js#L98-L99

Previous message edited.

Sorry for taking so long reviewing this, I must have completely missed it :(
I'm going to close now though, as I work to archive some of these older polyfills...


Update kotlin-compile-testing to 1.4.4

Version bump of kotlin-compile-testing to 1.4.4, the latest as of now.

Thanks @weisers !


Apply black formatting

Fixes # (provide issue number if applicable)
Feature Summary and Justification
This feature provides ...
References

Thanks for the fix!


Huge performance difference with two nearly identical SGF files

Sabaki seems to perform a lot worse, when the SGF file contains many separate games in contrast to the same amount of variations of an empty board. Here is a zip containing two nearly identical "large" files. After opening large1.sgf, placing stones doesn't have any delay, with large2.sgf placing stones has a 1 second delay (at least on my machine).
I don't know if this is a bug or maybe can be designed better (or maybe the design doesn't allow this).

Interesting... Running a CPU profile yields that the perpetrator is Sprint, a jQuery-like DOM manipulator. I think this is because of the sheer amount of HTML elements that are generated for each game inside the SGF collection.

This fixes the delay when placing stones. I'm keeping this issue open for the delay when opening the 'Manage Games...' dialog. Maybe we can try generating the SVG preview images on the fly (when scrolling)?


Issue with Association Class

When I create an association class between to classes and I generate the Java code, the attributes of the other two classes are not added as an instance variable. Other UML tools do add these reference variables.

Not Solved till now

still not working

met  the same issue of Association Class.


PixiJS 5.0.0-alpha.3

Hello!
I've tried launching example, using PixiJS v5.0.0-alpha.3, but it doesn't work.
When will the after effect plugin support this version of pixi?

Hi !!
Supported v5 by https://github.com/knocknote/pixi-after-effects/pull/14 !
Thanks


feetech_ros2_driver: 0.1.0-1 in 'jazzy/distribution.yaml' [bloom]

Increasing version of package(s) in repository feetech_ros2_driver to 0.1.0-1:

upstream repository: https://github.com/JafarAbdi/feetech_ros2_driver.git
release repository: https://github.com/JafarAbdi/feetech_ros2_driver-release.git
distro file: jazzy/distribution.yaml
bloom version: 0.12.0
previous version for package: null

feetech_ros2_driver
* Add feetech ros2 driver
* Contributors: Jafar Uruç

See the comment in https://github.com/ros/rosdistro/pull/43490#pullrequestreview-2443491346 , which will probably necessitate changes here.

Holding for Jazzy sync

https://github.com/ros/rosdistro/pull/43995


Update website screenshot

Currently, it is the old colors, this should be fixed :)

Closed via 940cbf1c0f0a7babb64b8c998756e1dff3abaa81


add locks readme

🚀 Pull Request
Description

This PR adds a README.md to the requirements/locks directory to highlight that the contents of this directory is auto-generated and manual changes will be overwritten.

Consult Iris pull request check list

@bjlittle Awesome, thanks :beers:


[Fix #3365]: Changed regex to cover new line before action serious

Fix for: Changed regex to cover new line before action serious.
This PR fixes the issue where ValueError: Could not parse LLM output: was thrown on seems to be valid input.
Changed regex to cover new lines before action serious (after the keywords "Action:" and "Action Input:").
regex101: https://regex101.com/r/CXl1kB/1

thanks!

@hwchase17 no,  it is Thank you for this project :)
PS: I run Linter and I hope the build will pass now :)

Since this PR got merged I am getting ValueError: Could not parse LLM output: The forecast for Product X at location Y is 233.0 with trend and seasonality is present.. Even if there is no issue with the output

Since this PR got merged I am getting ValueError: Could not parse LLM output: The forecast for Product X at location Y is 233.0 with trend and seasonality is present.. Even if there is no issue with the output

@ananyatripathi is that all output you are getting? I mean there are no keywords like "Action", "Action Input" or others?
My change should allow having a new line after the keyword which was giving an error before... and to my understanding not having keywords is a ValueError... maybe your string/prompt is final and just missing the "Final Answer" keyword...
Probably you could create an issue and we could continue the discussion there. I might lack experience but I hope I will be able to find how my change could add to the braking change.


flutter run on Android ends up showing logs from previous debugging sessions on Android

This can be worked around by running adb logcat -c, but I don't remember this happening in the past.  I'm not sure when it was introduced, but it may be present on stable.
See https://github.com/flutter/flutter/issues/34876#issuecomment-568302267 for more context
/cc @jonahwilliams or @blasten who might know if something changed on the tooling side here.
It's also possible this is related to Android version, as I recently started using a Q device more regularly.

please mine is saying please review your gradle project
what do I do ??

@Horlahkay that's a different issue. Please file a new bug if there isn't an existing one covering that.

Okay thanks
Its solve already what am experiencing now is
FAILURE: Build failed with an exception.

Where:

Build file 'C:\flutter.pub-cache\hosted\pub.dartlang.org\shared_preferences_macos-0.0.1+2\android\build.gradle' line: 22

What went wrong:

A problem occurred evaluating root project 'shared_preferences_macos'.

Failed to apply plugin [id 'com.android.library']

Minimum supported Gradle version is 5.4.1. Current version is 4.10.2. If using the gradle wrapper, try editing the distributionUrl in C:\flutter.pub-cache\hosted\pub.dartlang.org\s

hared_preferences_macos-0.0.1+2\android\gradle\wrapper\gradle-wrapper.properties to gradle-5.4.1-all.zip

Try:

Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 14s
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Dan Field<EMAIL_ADDRESS>Sent: Monday, December 23, 2019 12:16:33 AM
To: flutter/flutter<EMAIL_ADDRESS>Cc: Horlahkay<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [flutter/flutter] flutter run on Android ends up showing logs from previous debugging sessions on Android (#47629)
@Horlahkayhttps://github.com/Horlahkay that's a different issue. Please file a new bug if there isn't an existing one covering that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/flutter/flutter/issues/47629?email_source=notifications&email_token=ANPVA3CUJKM2WW5EI6FWAM3QZ7YNDA5CNFSM4J6NQNA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHP34OY#issuecomment-568311355, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANPVA3CHPUISJSNTTQXCRCTQZ7YNDANCNFSM4J6NQNAQ.

@dnfield Is this a duplicate of https://github.com/flutter/flutter/issues/46815?  You commented on that one, too.

Yes, closing this one


Could this used for Healthcare?

Hello,
I am interested to build some healthcare modules onto Zulip for some healthcare providers to be able to communicate in their teams.
Is that cool?

If you're in the USA you'll need to make sure that you use it in HIPAA compliant way; I don't know exactly what's involved with that.  But I've heard HIPAA compliance is much more complicated for using a cloud product vs. using something on-premise.


feat: Add solid and dashed boarders

Add the option of solid or dashed boarder styles

@glouppe This is ready for review.

Thanks!


Intial Focus/Blur Rerenders entire form

Using v4 RC2. Seems like a bug.

Can you be more specific? How do you know it's rerendering? Are you using validation?

Considering that we have this in the v6 migration guide, @aldendaniels was probably right:

In v5, only the outer form component was connected to the Redux state, and the props for each field were passed in via the form component. The problem with this is that the entire form component had to rerender on every single keypress that changed a form value.

v6 doesn't have this problem anymore, so... will close here.


feat: Add invoke_mode input

Description
Adds suport for the recently-introduced invoke_mode argument on the aws_lambda_function_url resource:
https://github.com/hashicorp/terraform-provider-aws/pull/30547
Motivation and Context
Setting invoke_mode to RESPONSE_STREAM allows streaming responses via the lambda's Function URL.
More about the brand-new Lambda response streaming:
https://aws.amazon.com/blogs/compute/introducing-aws-lambda-response-streaming/
Breaking Changes
None.
How Has This Been Tested?

[x] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[x] I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed pre-commit run -a on my pull request

This PR is included in version 4.15.0 :tada:


Add StrictMetricsEvaluator

This will enable use to delete whole datafiles by evaluating the metrics, and not needing to open the Parquet files.

Thanks @HonahX for the review 👍


Pre-aggregation of events before Druid

Hi all,
This is not really an issue... but wanted to share here in case someone will find it useful.
We are using Druid to monitor the performance of our application, e.g. how much time the server spends on DB queries, how much time is spent on search engine queries etc. We have multiple dimensions, like the customer id, the API server host, the API action etc.
The number of events is quite large - around 10B a day, and it would probably take a significant number of middle managers to ingest it into Druid.
The solution we ended up with is to pre-aggregate the events before pushing them to Druid - we implemented an Nginx module that gets the events over UDP from our API servers, the events are aggregated based on a Druid-like schema, and then pushed to a Kafka topic. Druid then pulls the events from Kafka using Kafka ingestion service.
We have a single such Nginx server, it handles all the events with its CPU utilization averaging around 10%. In the current configuration we are using, the number of events drops by a factor of ~170 during this aggregation, and we can use a very small Druid cluster to handle it.
The Nginx module is open source, and available here - https://github.com/kaltura/nginx-aggr-module/
Thanks,
Eran

Great job. We also meet the same challenge.  We use Flink realtime pipeline to pre-aggregation ETL cleaned data, dramatically reduce input data volume for Druid.

Great job. We also meet the same challenge.  We use Flink realtime pipeline to pre-aggregation ETL cleaned data, dramatically reduce input data volume for Druid.


Fix invalid strict-mode syntax with hexadecimal

This resolves an issue where the module wasn't able to be parsed in strict mode.
See: ssbc/ssb-server#683

See my comment here: https://github.com/ssbc/ssb-server/issues/683#issuecomment-515697283

I'll be adding eslint to this repo, which will end up subsuming this PR, so I'll reopen and update the PR with those commits.

Thank you for the merge!


dnsproxy: 0.35.5 -> 0.36.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/AdguardTeam/dnsproxy/releases.
meta.description for dnsproxy is: "Simple DNS proxy with DoH, DoT, and DNSCrypt support"
meta.homepage for dnsproxy is: "https://github.com/AdguardTeam/dnsproxy"
meta.changelog for dnsproxy is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

directory tree listing: https://gist.github.com/cce9c13693383e08cdf066e883b7125f

du listing: https://gist.github.com/598d58821a3652aea89be14c4afb8b29

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
dnsproxy

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/854px845wh42i9v05chsxjicbr1hgsai-dnsproxy-0.36.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A dnsproxy https://github.com/r-ryantm/nixpkgs/archive/f8f128ca22469efb94b9e76b7dd696251e931492.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/854px845wh42i9v05chsxjicbr1hgsai-dnsproxy-0.36.0
ls -la /nix/store/854px845wh42i9v05chsxjicbr1hgsai-dnsproxy-0.36.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

dnsproxy

Maintainer pings
cc @contrun @kalbasit for testing.

Result of nixpkgs-review pr 116843 at f8f128ca run on aarch64-linux 1

1 package built successfully:

dnsproxy

1 suggestion:

warning: unclear-gpl
gpl3 is a deprecated license, check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/tools/networking/dnsproxy/default.nix:21:5:
   |
21 |     license = licenses.gpl3;
   |     ^


Unhandled choiceAdventure1341

`[1969] The Overgrown Lot
Encounter: A Pound of Cure
Manual control requested for choice #1341
choice 1: Transfuse the pygmy blood (cure patient)
Click here to continue in the relay browser.
Stack trace:
  at guzzlr_deliverLoop (guzzlr.ash:750)
  at guzzlr_deliver (guzzlr.ash:774)
  at guzzlr_aftercore (guzzlr.ash:791)
  at main (guzzlr.ash:842)
printStackOnAbort => false
afterAdventureScript => scripts\BestBetweenBattle.ash
breakableHandling => 1
choiceAdventureScript =>
currentMood => default
maximizerCombinationLimit => 200000
promptAboutCrafting => 1`

is it possible to encounter this if you do not have the cure item?

Might as well mark it as fixed.  In several weeks of running your script I haven't encountered this issue before.


Improve StyledComponent performance

#583

Add second BaseStyledComponent class to not repeat methods
Improve propsForElement and this.attrs creation
Stop creating this.attrs if attrs doesn't exist
Rewrite generateAlphabeticName to be iterative instead of recursive

Before
simple component (construction)     0.019±0.003ms
simple component (first render)     0.132±0.027ms
simple component (repeated render)  0.014±0.001ms
prop changes                        0.309±0.054ms
prop shorthands (first render)      0.175±0.071ms
prop shorthands with prop changes   0.377±0.093ms

After
simple component (construction)     0.013±0.002ms
simple component (first render)     0.121±0.026ms
simple component (repeated render)  0.015±0.004ms
prop changes                        0.311±0.101ms
prop shorthands (first render)      0.155±0.052ms
prop shorthands with prop changes   0.344±0.038ms

Edit:
After with preprocessing
simple component (construction)     0.011±0.002ms
simple component (first render)     0.090±0.018ms
simple component (repeated render)  0.014±0.001ms
prop changes                        0.195±0.030ms
prop shorthands (first render)      0.095±0.030ms
prop shorthands with prop changes   0.208±0.051ms

Side comment, there is a potential performance benefit from changing the implementation of https://github.com/styled-components/styled-components/blob/d096d6126b606a5c413e353d2d6cedf2309a912d/src/models/AbstractStyledComponent.js#L6 to use PureComponent instead

@evan-scott-zocdoc That is unfortunately not quite the right way. First of all, it will change the behaviour for the user, and unexpected that is. And also, it doesn't improve the performance of the library itself. It's the responsibility of the user to decide when to turn to reference equality checks for perf optimisations.
The more clever approach is to not trigger state changes, when it's not necessary, but that's not really the scope of this PR. Btw: https://twitter.com/dan_abramov/status/820668074223353858

@mxstbr possibly! Next I want to see if there are more obvious things, maybe even related to behaviour as I've said above

@philpl how are you generating those benchmark stats? would be awesome to just have an npm script we could run when making changes to the library to quickly evaluate perf differences

@evan-scott-zocdoc With https://github.com/styled-components/benchmark
I've split up some tests into more granular ones though. Once we do #588, it's going to live in the main repo.


Address security issue

See https://github.com/coverified/website/security/dependabot

Resolved in #42

Resolved in #42


Puzzle mode

Add puzzle mode (trying to predict the next move of prerecorded games).
This is on top of eval PR #498. Please only look at the latest commit. I will squash-submit the PRs sequentially.

I think this looks good but because of the overlap between this and #498 I'm going to wait for that PR to be finished and merged before merging this one.

I think this looks good but because of the overlap between this and #498 I'm going to wait for that PR to be finished and merged before merging this one.

Absolutely, I will rebase this PR and #523 once #498 is in.


wrangler installation raise error again on M1 Mac

🐛 Bug report
Describe the bug
Wrangler installation issue on M1 Mac seems to be fixed in #1685, however it raise an error again.
Reproduce the bug
sudo npm install -g @cloudflare/wrangler
Here is error log:
npm ERR! code 1
npm ERR! path /usr/local/share/node-17.2.0/lib/node_modules/@cloudflare/wrangler
npm ERR! command failed
npm ERR! command sh -c node ./install-wrangler.js
npm ERR! node:internal/fs/utils:344
npm ERR!     throw err;
npm ERR!     ^
npm ERR!
npm ERR! Error: EACCES: permission denied, mkdir '/Users/user1/.wrangler'
npm ERR!     at mkdirSync (node:fs:1334:3)
npm ERR!     at Binary._getInstallDirectory (/usr/local/share/node-17.2.0/lib/node_modules/@cloudflare/wrangler/binary-install.js:52:13)
npm ERR!     at Binary.install (/usr/local/share/node-17.2.0/lib/node_modules/@cloudflare/wrangler/binary-install.js:78:26)
npm ERR!     at install (/usr/local/share/node-17.2.0/lib/node_modules/@cloudflare/wrangler/binary.js:50:10)
npm ERR!     at Object.<anonymous> (/usr/local/share/node-17.2.0/lib/node_modules/@cloudflare/wrangler/install-wrangler.js:4:1)
npm ERR!     at Module._compile (node:internal/modules/cjs/loader:1097:14)
npm ERR!     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1149:10)
npm ERR!     at Module.load (node:internal/modules/cjs/loader:975:32)
npm ERR!     at Function.Module._load (node:internal/modules/cjs/loader:822:12)
npm ERR!     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) {
npm ERR!   errno: -13,
npm ERR!   syscall: 'mkdir',
npm ERR!   code: 'EACCES',
npm ERR!   path: '/Users/user1/.wrangler'
npm ERR! }
npm ERR!
npm ERR! Node.js v17.2.0

npm ERR!      /Users/user1/.npm/_logs/2022-04-19T15_58_14_475Z-debug-0.log

Expected behavior
Successfully installed
Environment and versions

operating system:  macOS Big Sur 11.6
output of wrangler -V: N/A
output of node -v: v17.2.0
content of wrangler.toml: N/A

I think the problem here isn't about the M1, but about using sudo, and npm's permission model.
A better solution is to use v2 of wrangler, available at npm install wrangler (note the lack of the @cloudflare scope). You can install it with -g, or locally to your project with -D. And it'll gracefully warn if it can't write to the location mentioned there.
Closing this issue since wrangler v2 is in GA.