Still use old view() function ?

I have followed installation steps, but not work. Someone help pls?
(1/1) ErrorExceptionstrpos() expects parameter 1 to be string, array given

@nguyenanhthai What version are you using?

Same problem here. Using 3.4 with Laravel 5.4

Never mind, I forgot to add the ViewServiceProvider to my config/app.php -.-


Restyle GraphViz output

I found it hard to read the GraphViz output, for example this demo graph.
The node labels are very long.  The part that changes is hard to see.
It is difficult to see namespace boundaries if there is more than one namespace.
Here is an example that wraps the K8s namespace in a GraphViz subgraph, and uses bold text for the Deployment name:
esnible-demo-connectivity-2.dot.txt (Note that this file should be renamed with .dot; extension, Github didn't let me upload except as text).

It might also be worthwhile to use GraphViz table-style labels for complex edges, to avoid very wide edge labels.  A simple edge might be UDP :53 or :8081, but a complex edge might be

TCP (layer 7)

paths: /a{4}(/[\\--9A-Z_a-z]*)?

dst_ports :3000

hosts ooo.y.z

(It might also be valuable to include several example .pngs in /docs directory of this repo, or in the Markdown of the NP-Guard-Demo repo.)

Done. Thanks @haim-kermany


URL to provision Microsoft New Employee Onboarding sites

I am reading this article @ provision-neo-hub on how to provision NEO hub sites, but when i click on this link :-

I will be redirected to a page to provision the "MICROSOFT 365 LEARNING PATHWAYS" and not the NEO sites.. any advice please? what is the URL to provision the NEO sites?

Hi, Thanks for your feedback. We're working on fixing the wrong link. The correct one is: https://docs.microsoft.com/it-it/sharepoint/provision-neo-hub
Thanks.


cannot use Mouse Buttons 3-5

Current Behavior:
When reassigning a hotbar key, mouse buttons 3,4,5,.. wont be assigned, and their default action triggers
Expected Behavior:

when reassigning keys in keybindings, please allow to capture additional mouse buttons. (refer to https://developer.mozilla.org/en-US/docs/Web/API/MouseEvent/button for vendor-specific mouse events )
default event for those mouse events have to be prevented

This slipped through and probably wasn't considered at all yet.


Removing some dead code and refactoring Rules file

it also fixes #967 erb issue

I'm merging here to deploy the site using this code


fixed npm main

Fixes #690
Fixes #1192
Fixes #1208
Fixes #1310
Well, really I'm hoping this is the root of the problem; could use help validating this. Unfortunately it won't be easily testable until we put out a new npm release with this fix, so I'll plan to do that fairly soon. I believe the problem is that main is supposed to point to a umd version of the library, instead of the es6 module version it was pointing at.

@elalish You can test npm packages locally before publishing them. Also, if you do need to cut a release to "test it out in the wild" maybe you could do so with an -alpha tag appended to it.

@corysimmons I'm still learning the ins and outs of npm, so if you know how to test this, please chime in with some instructions! :)
I'm not going to bother with an -alpha tag this time as I'm pretty confident it will be no more broken than before, and hopefully less so. If you'd like to review this PR or others, your input would be most welcome.


more opportunistic stereo assignment for polymers

See https://github.com/cdk/depict/issues/48#issuecomment-1257567395
The following example shows that the polymer version of the monomer could have stereochemistry, under reasonable assumptions. Actually, I think the missing R/S annotation on the left can actually be resolved without knowing the * (not?):

Fixed in release 1.2 (and 1.2.1). Not sure if live on SiMolecule/cdkdepict yet though.


ruff-check is not provider aware

Current Behavior
https://github.com/lucasvieirasilva/nx-plugins/blob/98ee074b55bde085619d29812580a59a1a488a99/packages/nx-python/src/executors/ruff-check/executor.ts#L23
Currently does not reference provider, so is not aware of uv
Expected Behavior
ruff-check should be running
uvx ruff check

Steps to Reproduce

generate a poetry project
change it to a uv project
cleanup and remove poetry venvs
notice that ruff fails because the python venv it wants to depend on no longer exists

Nx Report
n/a

Failure Logs
❯ pnpm nx run lambda-aurora-user-rotation:lint

> nx run lambda-aurora-user-rotation:lint

Running ruff check on project  lambda-aurora-user-rotation ...

dyld[38950]: Library not loaded: /Users/andrewhammond/.pyenv/versions/3.13.0/lib/libpython3.13.dylib
  Referenced from: <F20756FD-8531-3CBA-B4E2-DF2B56F7324F> /Users/andrewhammond/Library/Application Support/pypoetry/venv/bin/python
  Reason: tried: '/Users/andrewhammond/.pyenv/versions/3.13.0/lib/libpython3.13.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/Users/andrewhammond/.pyenv/versions/3.13.0/lib/libpython3.13.dylib' (no such file), '/Users/andrewhammond/.pyenv/versions/3.13.0/lib/libpython3.13.dylib' (no such file)

   ERROR  poetry run ruff check src test command failed with exit code null

Additional Information
No response

Want to provide additional context. @ahammond and I work together and so, I checked out his branch to test changes.
It seems to expect poetry even when we want to use uv. I even tried generating a new project from scratch and the error logs you see below are from that blank project.
$ npx nx run lambda-aurora-user-rotation:lint

> nx run lambda-aurora-user-rotation:lint

Running ruff check on project  lambda-aurora-user-rotation ...

[tool.poetry] section not found in /Users/ajonnavithula/Dev/clickup/apps/lambda-aurora-user-rotation/pyproject.toml

   ERROR  poetry run ruff check lambda_aurora_user_rotation tests command failed with exit code 1

———————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

 NX   Ran target lint for project lambda-aurora-user-rotation (827ms)

   ✖  1/1 failed
   ✔  0/1 succeeded [0 read from cache]

$ npx nx run lambda-aurora-user-rotation:build

> nx run lambda-aurora-user-rotation:build

  Building project  lambda-aurora-user-rotation ...

  Copying project files to a temporary folder
  Resolving dependencies...

   ERROR  Cannot read properties of undefined (reading 'extras')

———————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

 NX   Ran target build for project lambda-aurora-user-rotation (555ms)

   ✖  1/1 failed
   ✔  0/1 succeeded [0 read from cache]

It seems like the provider expected is defaulting to poetry?

Hey guys, thanks for raising this issue, I'm gonna fix it today!

@ahammond and @avadhanij I've checked the issue, and apparently, that only happens if you delete the root pyproject.toml and root uv.lock files.
did you guys figure out a way to ignore all the node projects (ref: https://github.com/lucasvieirasilva/nx-plugins/issues/258#issuecomment-2547304154) so you can keep the root pyproject.toml and root uv.lock files?

Trying with the root pyproject.toml as follows:
[project]
name = "nx-workspace"
version = "1.0.0"
dependencies = [
  "lambda-aurora-user-rotation",
]

[dependency-groups]
dev = [
  "ruff>=0.8.2",
  "autopep8>=2.3.1",
  "pytest>=8.3.4",
  "pytest-sugar>=1.0.0",
  "pytest-cov>=6.0.0",
  "pytest-html>=4.1.1"
]

[tool.uv.sources.lambda-aurora-user-rotation]
workspace = true

[tool.uv.workspace]
members = [
  "apps/lambda-aurora-user-rotation/",
  "apps/lambda-demo-pkg/",
]

And it's generating a uv.lock file. Tried linting and... huzzah! It worked!!!


Fix rebase mistake

I wanted to duplicate if ! ${ERROR}; logic where we only run
make ci if the setup worked.. Instead, make ci
only runs when the setup errors.
Changes proposed in this pull request

Fixes a false positive introduced from #348

ACK


Make sure chart viewer height gets set correctly

Fixes #1497 where chart viewer options could get cut off because the height of the panel was 100% but it got pushed down by the toolbar above it, meaning that some content got put out of view.

@MattIrv I've noticed the CI builds have been failing more frequently lately from apparently unrelated reasons.  Any ideas?  Or just general infra flakiness?

@kburtram they seem to be failing a lot lately but most of them that I've seen, including this one, seem to be infra problems with Travis


Create Skills, Skills Category relationship table

Resolves #4691
Notes:

Requires #4772 to be merged first.

Code coverage test fails arbitrary coverage drop allowed for success value, 2.5%, by 0.06% (2.56%).


Warning about set-env command deprecated

Hi, recently I started getting this warning on my build step that uses this action (no other step in my workflow reports this warning)
Warning: The `set-env` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

Ok, I suppose this PR is supposed to fix that, right?
https://github.com/r0adkll/sign-android-release/pull/21

@lukas1 Yes! This should be resolved now

@r0adkll Just hit this warning on my run a few mins ago. This will be disabled on November 16th.

Hmmm, interesting. I was pretty sure I updated the dependency to resolve this, let me check again


Nuke OpenSearch domains

Depends on https://github.com/gruntwork-io/cloud-nuke/pull/234 (for aws-sdk-go upgrade)
Fixes https://github.com/gruntwork-io/cloud-nuke/issues/235

Thanks for review! Since https://github.com/gruntwork-io/cloud-nuke/pull/234 was also approved, I'm going to go ahead and merge this one and close the other.


[Meta] Add the ability to split an application into multiple pages & conditionally direct a user to specific pages

Is your feature request related to an existing functionality? Please describe.
As part of the SimSec research on the application experience, we believe that it would be beneficial to be able to split the application into multiple pages and provide navigation to the user.
Closely linked to pagination is the ability to direct an applicant to different pages based on their answers to particular questions.
We're discussing both these functionalities in this meta issue as they are closely linked.
Terminology
There are many terms to describe conditional logic - the terms conditional logic, skip logic, and branching are interchangeable.
We'll try to use only skip-logic.
Pagination
Pagination allows the form creator to break show the the application form is displayed to the applicant over multiple pages.
Minimum viable product
Form creators (i.e. programme managers) need a way to:

indicate where another page begins (this could be create page breaks in an application, similar to creating a section header)
"move" questions from one page to another

When the applicant views this application:

they navigate between sections
the data they create needs to be stored (in the browser session or something along those lines) to make sure that the users doesn't lose data in the event of an Internet issue (e.g. low bandwidth situation or outage)

Prior examples of pagination functionality
Most form creation software support pagination.
Survey Monkey
Here's their documentation to adding pages
CrowdSignal
Here's how Crowdsignal does pagination and moving questions between pages.
Google Forms
Here's how Google Forms does it
Nextcloud Forms
Here's a similar discussion for implentation of pagination.
Skip-logic
Skip-logic allows the form creator to create branches where the applicant can be sent to different pages based on their answer to a question.
Minimum viable product
When the Hypha form creator user creates the application form, they need a way to:

choose which question is selected for skip-logic
they could create a rule to direct an applicant to question located on a different page, based on how they interact with previous question

When the applicant views this application:

depending on how they interact with the question they are directed to the next question, or to a specific question on a different page
they are able to navigate forward and backward through the pages

Example of skip-logic form:

Prior examples of skip-logic
wagtail-advanced-form-builder
There is a Wagtail module called "wagtail-advanced-form-builder". It contains skip-logic functionality. This module may be able to be reused. @frjo is investigating this.
CrowdSignal
Here's how Crowdsignal does skip-logic:

Google Forms
Here's how Google forms does skip-logic

SurveyMonkey
Their help documentation describes how skip-logic works.
Sub issues
These issues are for technical dscussion of implementation.

Add pagination to application forms #2378
Add conditional logic to application form creation [to be opened]

Describe alternatives you've considered
This is a new idea, feedback/critique/comments/alternative ideas welcome!
wagtail-advanced-form-builder
There is a Wagtail module called "wagtail-advanced-form-builder". This module may be able to be reused. @frjo is investigating this.
Additional context
Example from the wireframe:

Affected roles

Staff
Applicants

My suggestion would be to implement this in JavaScript.
The form would then in reality be one page as now but behave like a multipage form for the user.
A bit like the submission detail pages work today with the three tabs, "SUBMISSION DETAILS"
"COMMUNICATIONS" and "ACTIVITY FEED". That is really one page but it feels like three for the user.

Could we create a streamfield that would indicate the split?

A "split/break form" stream form would be needed so the staff can specify where the form should break.
@Parbhat What do you think would be the best solution?

JavaScript to handle the multi-step form in Frontend + A multi-step field in application forms streamfield to add step title and defines a break, looks like a good solution. It will help to not change anything in backend for the form submissions code and its side effects. And helps to retain the current standard form submission.
Wagtail docs also list one customization to create multi-step forms from standard Wagtail forms. It divides the form in the backend into steps with the help of paginator.
This issue is slightly related to the improve the file upload widget issue https://github.com/OpenTechFund/hypha/issues/1440. As it may change how the form submission works currently (standard way) or submitted via Ajax.

Flagging that we'd love to have pagination for the review form as well!

The first part now has an issue #2378.
The second part about redirecting I do not know how to implement. The admin UI for it can easily become a UX mess.

@katiewilson21 thank you for sharing your designs with us. I'm adding @frjo in case there are any questions.
Later this week I will share some example or potential application questions and forms we might create in the future based on pagination and skip logic. However, I think your design are great and don't want to delay the development of this github issue further.

Related to #2378


No 'delete' button to allow removal of terms from a codeset

Investigate issue removing terms from a CodeSet

Terminology deleted so issue moved.
Still waiting for #438 to be fixed to complete the Wiki page.


Fixes issue #12945 - Validation checks for content, yaml and redirect keys in parseRedirectsFile

This PR will fix issue #12945, I have added checks for content, yaml and redirect keys.
Please have a look and let me know if anything else you would like me to do.

[x] There's a clear use-case for this code change
[x] Commit message has a short title & references relevant issues
[x] The build will pass (run yarn test and yarn lint)

Hey @hey24sheep I'm so sorry I totally missed this PR 🙈
These changes look good, only the file has since moved from frontend -> server:
https://github.com/TryGhost/Ghost/blob/main/core/server/services/redirects/settings.js
Would you be up for rebasing this PR? If you do drop a comment and I'll keep a close eye out for it.


FIrst opening of a new wallet opening shows 'API error ...' message

Bug

your phone model and OS version
OnePlus Nord

BoltCardWallet app version (settings->about->scroll down)
Bolt Card Wallet ver 0.1.2 (build 167874118 master)

self-test passes? Open settings->about->scroll down, tap "Run self-test"
could not find this

unique ID for our crash reporting service (settings->about->scroll down, tap "copy")
4a7690eba203d194

After a new wallet is created, opening the wallet screen for the first time gives:
API error: Something went wrong. Please try again later (code 6)
Everything seems to work fine after that.

error traced to the hub
"error getting balance:","cannot get transactions: no onchain address assigned to user"
unsure why this is faulting on the first request

looks like the error is coming from this code:
error getting balance
cannot get transactions: no onchain address assigned to user


UnableToWriteImageData error/jxl.c/WriteJXLImage/641

Writing JXL files seems to be broken in the current version.
With the following Dockerfile:
FROM php:7.4-cli
RUN apt-get update \
 && apt-get install -y wget libmagickwand-dev --no-install-recommends \
 && curl https://raw.githubusercontent.com/SoftCreatR/imei/main/imei.sh | bash

Converting an image to JXL inside the docker image:
convert test.png test.jxl

Results in the following error:
convert: UnableToWriteImageData `jxl-test.jxl' @ error/jxl.c/WriteJXLImage/641.

Fixed via 11b42ca8f7b3bcb30ea41d369f42c3fa58e90596

Works great, thank you very much!


fix: Deposit and withdraw window does not close after singing the tra…

…nsaction
What is the purpose of the change

Add a description of the overall background and high level changes that this PR introduces

Bug fixes following Multiple Wallets QA. These issues are resolved in this PR:

[x] deposit window does not close automatically
[x] transfer status not updated until page is refreshed
[x] get Network Error when  depositing KI
[x] no transfer history shows up on the osmosis front-end when withdrawing ETH(Axelar) tokens
[x] unable to edit amount input when depositing native ETH(Axelar) tokens
[x] unable switch the toggle to wrap token when trying to deposit

ClickUp Task
ClickUp Task URL
Key Workflows to test

[ ] IBC deposit window does not close automatically
[ ] IBC transfer status not updated until page is refreshed
[ ] 404 when depositing CW tokens
[ ] Network Error when  depositing KI
[ ] No transfer history shows up on the osmosis front-end when withdrawing ETH(Axelar) tokens
[ ] Deposit status of native ETH(Axelar) tokens get stuck at  pending
[ ] Unable to edit amount input when depositing native ETH(Axelar) tokens
[ ] Unable switch the toggle to wrap token when trying to deposit

Documentation and Release Note

Does this pull request introduce a new feature or user-facing behavior changes? yes
How is the feature or change documented? not applicable

why do we need an API endpoint? Please add a comment to explain it's necessity

@jonator added a comment in my latest commit. To summarize, we need it to avoid CORS errors since there are several nodes that do not provide the necessary headers.


fix: check arguments size before calling get

Resolves: #398

@metacosm: does this fix your issue?


Having trouble gettting it to work

Having trouble gettting it to work, ive followed the detailed tut on https://derflounder.wordpress.com/2015/11/19/downloading-installer-packages-from-the-mac-app-store-with-appstoreextract/ with no success, need some help to get it to work please

Hi @skarzzzz
Thanks for your interest in my script, I'm happy to try to bring you up and running with it:
The write-up from Rich is a bit old and will only work partly on newer OS versions. To make it run (with less problems) starting on Catalina, you need another CLI tool, called "mas": https://github.com/mas-cli/mas, If you attempt to download the packages manually from the AppStore itself it will fail, as Apple has changed some background processes.
Easiest is to install it through home brew (https://brew.sh), then do these steps (tested under macOS Big Sur 11.2.1):

prepare the MacAppStore-Extractor-Script and start in in a Terminal Window:
---> /PATH/TO/MacAppStoreExtract.sh -m (use the -m for Munki compatibility)

---> Importan, let it run while you with to another window and run the mas-cli:
run mas-cli to install the desired package (for example the Safe Exam Browser from ETH Zurich):
---> /opt/homebrew/bin/mas install 411684841
When it has finished, go back to the MacAppStore Extractor script and press any key, then Y(es) to finish up the DMG.
You should now find it in "/Users/Shared/AppStore_Packages".
Hope that works for you, if now, please find me on the Mac Admins and send me a PM.

Try using v3.1
https://github.com/blakeusblade/MacAdminHelpers/tree/master/AppStoreExtract


Changing language on instance level doesn't work.

Describe the bug
Changing an instances language after from scratch installation doesn't work. The console instead prints an error about missing SMTP settings.
To Reproduce
Steps to reproduce the behavior:

Install ZITADEL from scratch
Go to instance general settings
Change language
Refresh

Expected behavior
Language is changed.
Screenshots

I tried this on my ZITADEL cloud instance. And I can't reproduce it. @eliobischof can you see what requests are done?
The setting is changed correctly. Only problem the loading icon doesn't disappear after.

The instance language is new users default language. The users language defines how the console is displayed. Therefore works as expected, apart from the spinner (PR is linked).

spinner is fixed with #4676


Directories not being shortened under Windows 10 GitBash

Here's my config:
{
    "segments": [
        "time",
        "git",
        "set_term_title",
        "cwd",
        "newline",
        "virtual_env",
        "exit_code",
        "username",
        "root"
    ],
    "hostname": {"colorize":"true"},
    "cwd": {
        "mode": "plain",
        "max_depth": 4,
        "full_cwd": "true",
        "max_dir_size": -1
    },
    "theme": "solarized_light",
    "mode":"patched"
}

Python version is 3.6.4, just pulled powerline-shell from PyPI.

The cwd directory options are currently ignored when plain mode is used. I plan to fix that, but currently that's "expected" behavior.

The directories still aren't being shortened after I remove the "mode":"plain" line from the config.

Could you post a screenshot of what it looks like without that option?

No change.

Without any cwd config: it looks the same as well.

I think the code might thing your directory separator is \ instead of /. What's the output of python -c 'import os; print(os.sep)'

The result is \.

Is python -c 'import os; print(os.path.sep)' any different?

I don't think it will be. It looks like os.sep is just a copy of os.path.sep.
What is the output of echo "$shell"

/usr/bin/bash which is just C:\Program Files\Git\usr\bin\bash.exe, but aliased. $OS is Windows_NT.

I think I have a solution. What's the output of python -c 'import os; print(os.getcwd())' ?

C:\Users\at8183jk\Desktop\Drive\Dropsync\School\Winona\ResearchProject\code

Excellent. I will have a change that I believe will fix your issue. Just gimme a little bit.

I'll work with a local version for a bit to see if this changes things.

By local version, you mean the PR I just opened? If so that would be great to confirm it resolves the issue.

Yeah, I just pulled it down and locally installed it. I had to remove 'max_dir_size':-1 to get it to work (otherwise neither the ... nor the full name of any directories appeared, which is weird!). Otherwise it seems to be working!

Another Weird thing: The git branch segment doesn't have the "arrow" appearance like the other ones do. Is that intentional?

I did a little more digging, it seems if the set_term_title segment is empty, the segment before it will not have its arrow portion shown.

Ah interesting. Let's discuss in a separate issue.

Issue with arrows moved to Issue #341


"root" configuration is not used when resolving a benchmark's URL

When configuring a basic Tachometer benchmark, I created a directory structure like this:
project_root/
 ⮑ benchmarks/
     ⮑ tutorial.html
 ⮑ tachometer.json

And a configuration file for Tachometer that looked like this:
{
  "root": "./benchmarks",
  "benchmarks": [
    {
      "name": "Tutorial Benchmark",
      "url": "./tutorial.html"
    }
  ]
}

The result I got from doing this was initially surprising:
❯ tach --config ./tachometer.json
Error: File or directory is not accessible from server root: ./tutorial.html
    at Object.urlFromLocalPath (/Users/cdata/repositories/github.com/cdata/tach-test-repo/node_modules/tachometer/src/config.ts:179:11)
    at parseBenchmark (/Users/cdata/repositories/github.com/cdata/tach-test-repo/node_modules/tachometer/src/configfile.ts:385:24)
    at Object.parseConfigFile (/Users/cdata/repositories/github.com/cdata/tach-test-repo/node_modules/tachometer/src/configfile.ts:290:43)
    at Object.makeConfig (/Users/cdata/repositories/github.com/cdata/tach-test-repo/node_modules/tachometer/src/config.ts:90:38)
    at realMain (/Users/cdata/repositories/github.com/cdata/tach-test-repo/node_modules/tachometer/src/cli.ts:113:18)
    at Object.main (/Users/cdata/repositories/github.com/cdata/tach-test-repo/node_modules/tachometer/src/cli.ts:40:15)

I had assumed that whatever "url" I used would be resolved from the configured "root". However, when I changed my configuration to look like this:
{
  "root": "./benchmarks",
  "benchmarks": [
    {
      "name": "Tutorial Benchmark",
      "url": "./benchmarks/tutorial.html"
    }
  ]
}

Everything suddenly worked. My conclusion was that either I used the "root" configuration incorrectly, or else it is being ignored and this is a bug.
This may be working as intended. If that is the case, the documentation could possibly be improved to better explain the meaning and correct use of the "root" configuration option.

I think I agree that it makes more sense for urls to be relative to the root, if there is one. Probably just an oversight.
A related question is what the root itself is relative to (and what a url without a root is relative to). I think it should be relative to the location of the config file, but I have a feeling it's currently relative to the cwd of the tachometer process? WDYT?

A related question is what the root itself is relative to (and what a url without a root is relative to). I think it should be relative to the location of the config file, but I have a feeling it's currently relative to the cwd of the tachometer process? WDYT?

@aomarks this might work fine if you intend the user to have multiple configuration files for the condition where there are multiple roots in a project. I usually expect a process to assume the current working directory is my intended basis for relative paths, and Tachometer doesn't require a configuration file to be used, so it might not be the most reliable signal.
Reflecting a little on my original issue, the thing that tripped me up the most was the error message: Error: File or directory is not accessible from server root: ./tutorial.html
"root" is being used with a possibly different definition there.


moment.js deprecation warning using date-io/moment

Environment

Tech
Version

@material-ui/pickers
3.2.10

material-ui
4.10.2 (core)

TypeScript

React
16.13.1

Browser
Google Chrome 83.0.4103.106 (Official Build) (64-bit)

Peer library
moment 2.26.0, date-io/moment 1.3.13

Steps to reproduce

Start with a null selectedDate
Open the date picker
Choose a date

Expected behavior
No warnings.
Actual behavior
The following warning:
Deprecation warning: value provided is not in a recognized RFC2822 or ISO format. moment construction falls back to js Date(), which is not reliable across all browsers and versions. Non RFC2822/ISO date formats are discouraged and will be removed in an upcoming major release. Please refer to http://momentjs.com/guides/#/warnings/js-date/ for more info.
Arguments:
[0] _isAMomentObject: true, _isUTC: false, _useUTC: false, _l: undefined, _i: 06/22/2020, _f: undefined, _strict: undefined, _locale: [object Object]

Live example
https://codesandbox.io/s/nifty-kare-4xeum?fontsize=14&hidenavigation=1&theme=dark

i am facing the same issue too

+1

We do no longer support v3, please provide a reproduction with v4.0.0-alpha.10

It is reproducing and we know it. Thats why we have disabled warning failure on CI for moment tests

I just updated my code base and the live example to use more current versions of dependencies:

Tech
Version

@material-ui/pickers
4.0.0-alpha.10

material-ui
4.10.2 (core)

TypeScript

React
16.13.1

Browser
Google Chrome 83.0.4103.106 (Official Build) (64-bit)

Peer library
moment 2.27.0, date-io/moment 1.3.13

Here's the link to a new live example with the updated dependencies:
https://codesandbox.io/s/weathered-feather-fhnhh?file=/src/App.jsx

@mjburtenshaw Any idea how we could solve this problem?

@oliviertassinari I'll take a look through the moment.js docs as I have time through this week to see what we can do. I'll provide an update on Friday at end-of-business with my findings if I don't think of any solutions sooner.

I took a deeper look at the warning details, and I think that the date string being passed to the MomentAdapter is in MM/DD/YYYY format, which is an unreliable format according to moment.js:

Changing the date string being passed to the MomentAdapter to one of the following may fix it:

moment("2014-04-25T01:32:21.196Z");  // iso string, utc timezone
moment("2014-04-25T01:32:21.196+0600");  // iso string with timezone
moment("2014 04 25", "YYYY MM DD"); // string with format

But, I'm not certain if that's something that needs to be tested in material-ui/pickers or if that's something that's managed by date-io/moment.


Edit Payment Proof Info

Make editions to the Payment Proof info:

remove doubled space (if possible, seen only on iPhone 7 with Zoomed mode on and Polish keyboard layout)

double space ziipped video.zip

Replace the comma with dot, to stay consistent with the desktop version.

OK on <IP_ADDRESS>, testnet


Feature Request: custom command for generating doxygen documents for ports

Would it be possible to add an option to generate doxygen documents for ports individually? A lot of the ports like opencv, pcl, tinyxml2 all has doxygen style comments, I am imagining something like vcpkg install --doc tinyxml and bind it to a custom target along the lines of
find_package(Doxygen)

if(DOXYGEN_FOUND AND NOT TARGET doc)
  configure_file(${CMAKE_CURRENT_SOURCE_DIR}/Doxyfile.in
    ${CMAKE_CURRENT_BINARY_DIR}/Doxyfile @ONLY)
  add_custom_target(doc
                    ${DOXYGEN_EXECUTABLE} ${CMAKE_CURRENT_BINARY_DIR}/Doxyfile
                    WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}
                    COMMENT "Generating API documentation with Doxygen"
                    VERBATIM)
endif()

I looked into doing this before, but I couldn't get doxygen to generate linked documentation (so, having #include <zlib.h> inside a boost header jump you to the generated zlib docs) in a reasonable timespan. It seemed like the performance was O(N^2) or worse as the number of lines processed increased. As long as each set of docs was generated completely independently, it was acceptable.
If someone could figure out how to do this reasonably, I'd love to have it!

Ah I wasn't even thinking about linked documentation. I agree it will be a lot harder to do it. I think we can start with unlinked documentation first at some point.

This issue hasn’t been updated in a year; if it is still an issue, please reopen this issue.


Non jquery version on iOS

It seams that the non-jquery version is not working in safari on iOS (9).
Is this a bug or a feature? The color chooser is opening and closing when I touch the image but the choosen color is not applied.

If I replace
_getColorCanvas(event.originalEvent.touches[0]);

with
_getColorCanvas(event.touches[0]);

it works on iOS.
I just cannot test it on other touch devices.

You are right. I added your fix in the latest version.


Write custom Gitlab URL to gitlab-domains composer option. Fixes #165.

When I add this, the GitLab sync does work.
See https://getcomposer.org/doc/06-config.md#gitlab-domains for what this option does.

Nice, thanks @nickygerritsen :+1:


Allow ![]const u8 to also be used as a reference

@stephenafamo Can you give an example use case for this ? One I can think of is e.g.:
{{foo(bar)}}

but then couldn't you use try ?
{{try foo(bar)}}

If you think the above PR solves your issue then I'm happy to merge. Seems like it could be convenient for other things too.

@stephenafamo zmpl.write now resolves optionals and error unions - I agree this is cleaner, thanks for the suggestion.


Refactor out Legion code shared between operators

There's a pretty substantial amount of rather opaque legion code in each of the operators. It seems unlikely to me that there isn't significant redundancy between them. We should reduce this redundancy
Originally posted by @lockshaw in https://github.com/flexflow/FlexFlow/pull/576#discussion_r1082161115

Closed by #622.


Update OLDEST_SUPPORTED_VERSION to 0.23.0+

Given the swap to using PyInfo in place of the legacy python provider (see: https://github.com/bazelbuild/bazel/issues/7298), this plugin no longer supports Bazel Versions < 0.23.
This updates the OLDEST_SUPPORTED_VERSION to 0.23.0

Thanks for the patch, I'll apply this upstream.


Different language highlighting examples

Can you point me on the right direction as to how to select a different language other than JS when highlighting using this decorator?
I can try putting something together so that this repo could have an example on the README on how to do that.

I have the same question! Thanks again:)

Yeah same, I would like for it to auto detect which language!

Here is how you are able to do that:

      {
        type: "code-block",
        text: 'var message = "This is awesome!";',
        data: {
          syntax: "javascript",
        },
      },
      {
        type: "code-block",
        text: "
I am superman
",
        data: {
          syntax: "html",
        },
      },

so, you just need to figure out how blocks are working and add a block with syntax you need


[Jenkinsfile] run pre-commit

Oh, I see, I have to work-around the
07:53:09  packit/cli/sourcegit_to_dist_git.py:47:10: F821 undefined name 'Transformator'
07:53:09  packit/cli/sourcegit_to_srpm.py:48:10: F821 undefined name 'Transformator'

Just comment all out: we'll scratch that soon TBH. When Franta finishes his source-git part and we'll implement the new job interface.

PTAL


Improve event tracing

We should be able to trace events further and possibly associate effects with the event that caused them.

@marc-casperlabs  is this for 1.4.0?

Yes! :)
On Tue, Aug 10, 2021 at 10:33 PM Amit Patnaik @.***>
wrote:

@marc-casperlabs https://github.com/marc-casperlabs is this for 1.4.0?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/casper-network/casper-node/issues/1849#issuecomment-896298574,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APGHDSYBVUMTHK2RIZL3LULT4GEKTANCNFSM5BTVTY6A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.


Enable syntax highlighting in README

Problem
README file lacks syntax highlighting
Solution
Enable syntax highlighting in code blocks

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Alarmo intergratie can not open it

Alarmo Version
V1.9.8
HA Version
2023.4.2
Bug description
The intergratie its working but we can not open it than is he always loaded

Steps to reproduce
We re install alarmo but its not working
Relevant log output
No response

Duplicate of #688


Returns error on invalid request line

Fixes #2655
We could be more strict and accept only GET methods for HTTP 0.9
Test case 42 had to be rewritten as it is not valid HTTP 0.9

I'm wondering if we should be more strict. I agree the warning should be raised, but in general we try to be liberal as we value getting something out of the stream more than being strictly correct in most cases. Experience shows that many clients and servers are also much more relax and forgiving than RFCs would allow.

we try to be liberal as we value getting something out of the stream more than being strictly correct in most cases

I totally agree and that is what I am trying to do here.
This patch is not meant to be RFC compliant, it is about acknowledging that we lost track.
But I surely do not see which are the implications for having HTPHandleRequestData return error.
I thought it would restart parsing from a fresh state on next packet.
By your response, I guess I thought wrong and parsing does not resume.
Can you tell ?
I guess that you mean that we should consider anything between the end of a request and the beginning of a new request to be http_client_body.
I will start to do that.
Best would be to have a new keyword http_client_junk but that can be done afterwards.
Anyways, that will just cover the case in the pcap and bypasses will remain.

I'm not entirely sure, but I think if we return error ultimately we go into an error state in Suricata and stop feeding the parser new data. But this should be easy enough to test with a unittest in Suricata.

we go into an error state in Suricata and stop feeding the parser new data

This is not what I intended indeed


Improve the clarity of the client-side introspection errors

Respect the DJANGO_REACT['DEBUG'] flag and pump in more explicit suggestions.
The obvious one is if a React global is missing.

Given the shift towards a more purely rendering functionality, this is no longer relevant.


Just implement infix:<%> and infix:<%%> already

I just looked over the examples, and it maybe it's me being obsessed with modulo-related code examples — probably — but it would seem that all three of euclid-gcd.007, fizzbuzz.007, and nicomachus.007 would benefit from having infix:<%> (and infix:<%%>) built into the language.
So,

[x] Let's implement those.
[x] Let's not implement infix:</> for now. I'm still bothered by the things described in this comment.
[x] There's the risk of a division by zero, even with infix:<%> and infix:<%%>. So we'll need a new 007-exception type, and we'll need tests that try catching it.
[x] After we have the operators, we should go back and make the examples prettier.

[x] There's the risk of a division by zero, even with infix:<%> and infix:<%%>. So we'll need a new 007-exception type, and we'll need tests that try catching it.

Actually, I ended up just using the Perl 6 exception (X::Numeric::DivideByZero) for now. We can save the custom-exceptions work for some later time, when we do it across the board.

actual commits: b19d939c17e97f1d02ed45319215a67ce31a45f3...8c0bb8ed52


how to use @Example。Why I use @Example no effect

i copy this code in https://github.com/swagger-api/swagger-core/blob/master/modules/swagger-jaxrs/src/test/java/io/swagger/resources/ClassWithExamplePost.java
but no effect

@rim-wood can you share the swagger.json you're getting?

@webron

this is part of my swagger.json

@webron
this is part of my swagger.json

"/surviveevent/external/info": {
"post": {
"tags": [
"surviveevent"
],
"summary": "test",
"description": "",
"operationId": "postTest",
"consumes": [
"application/json"
],
"produces": [
"application/json"
],
"parameters": [
{
"in": "body",
"name": "test",
"description": "test",
"required": false,
"schema": {
"type": "array",
"items": {
"type": "string"
}
},
"x-examples": {
"application/json": "["a","b"]"
}
}
],
"responses": {
"default": {
"description": "successful operation"
}
}
}
},

Right. The current version of swagger-ui doesn't support the x-example/s extensions.  It should work if you provide the example through the model itself.

@webron
yes,if i provide the example through the model,this is work.
but you know,
The add and modified is different，add method may be need more param.
if i use @ApiModelProperty , That means add and modified show the some param in swagger-ui.
for example，
the model hava 4 param in add method,and is required in addition to facilityCode.

but in edit method, facilityCode is required,the other is not.

I do not know whether you understand what I mean，if you hava solution，please tell me

Yeah, I understand. However, when it comes to Swagger, there's no simple solution to it because of how JSON Schema works. Effectively you'd need to create two different classes where in one the field is required and in the other it is not. Those classes can of course inherit from each other.

@webron  ok，i see， thank you very much

@webron I meet the same issue. I don't want to show the model schema because of to large. I try to use @example annotation but not work.
swagger-jersey2-jaxrs:1.5.16
swaggerUI:3.3.2
swagger.json generated by annotation:

code:
public Response registerApp(@HeaderParam("X-Auth-Token")String token, @PathParam("registeredSystem") RegisteredSystem registeredSystem,                                  @ApiParam(value = "request",                                         examples = @Example(value = {                                                 @ExampleProperty(mediaType="application/json", value="[\"a\",\"b\"]")                                         })) ApplicationRegistrationCreateRequest request) {...}


The documentation page for the SeDelegateSessionUserImpersonatePrivilege privilege is missing

In the page User Rights Assignment, the group policy setting Obtain an impersonation token for another user in the same session links to this page (https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/impersonate-a-client-after-authentication) which corresponds to another setting, Impersonate a client after authentication. Is this the correct behavior?

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

ID: 7de1fb45-91eb-f37f-8106-81bf82a5602e
Version Independent ID: 1c765989-4c50-4b89-83fe-a8625f0f9fd5
Content: User Rights Assignment (Windows 10) - Windows security
Content Source: windows/security/threat-protection/security-policy-settings/user-rights-assignment.md
Product: m365-security
Technology: windows-sec
GitHub Login: @Dansimp
Microsoft Alias: dansimp

Thanks @michaelAngeloEgypt for the edit...but that article you linked doesn't include anything about SeDelegateSessionUserImpersonatePrivilege or Obtain an impersonation token for another user in the same session either as @LorenzoDePasquale asked. It looks like it's come up in the past before with similar feedback: https://github.com/MicrosoftDocs/windows-itpro-docs/issues/8551. (Also reference https://github.com/MicrosoftDocs/windows-itpro-docs/pull/8902 for the original edit.)
I wonder if the feedback here is really that we need a new article for that user right. Unless I'm missing something?

@LorenzoDePasquale Thank you for your feedback. You are correct, Obtain an impersonation token for another user in the same session link points to Impersonating a client after authentication as this policy setting determines which programs are allowed to impersonate a user or another specified account in the same session.
Hope this helps!
Thanks
Sri

Thanks, now it's clear


Update readme file

In our readme file, our contributions sections look weird. It would be better if we updated it.

Hey @gouri-panda
I am Vishwas Tyagi. I would like to work on this.

@vishwast03 Thanks! Go ahead!

@gouri-panda  Thanks for your reply. I will get back soon with updated readme file.

Is this issue still need to be addressed? If yes, you can assign it to me.
I would like to work on this task!

@iamansoni Thank you! Go ahead!


Add a method to expose unknown flags back to the user

Currently it is possible to ignore unknown flags (with
FlagSet.ParseErrorsWhitelist.UnknownFlags) but there is no way to find out
what they were after the fact.
Add a method which registers a slice into which all unknown arguments will be
accumulated.
Note that unknown short arguments which appear in a group (e.g. -uuu) will be
exploded (e.g. into -u -u -u) in this slice. Also any following value is
associated with the final option, e.g. ["-uuu", "foo"] is interpreted as
["-u", "-u", "-u", "foo"]. This is consistent with the statement:
Single dashes signify a series of shorthand letters for flags. All but the
last shorthand letter must be boolean flags.

This is the reason why the call to stripUnknownFlagValue in
parseSingleShortArg becomes conditional on this being the last short arg in
the batch.
Add code to the existing TestIgnoreUnknownFlags (which already has
comprehensive set of the varities of possible unknown flags) to check this.
Also fixed a small cut-and-paste-o in the failure message of the test (use of
f.ParseAll).
Signed-off-by: Ian Campbell<EMAIL_ADDRESS>For my use I'm actually only interested in the first unknown argument but this seemed like a more flexible approach which might be more widely usable. (I could probably get away with a flag "there were unknown args", although that wouldn't be so nice).

My immediate need for this became obsolete with https://github.com/docker/cli/pull/1722 so feel free to close if there is no interest in this.

@ijc I have some interesting in this still, since the request was approved by @seemethere already can we merge this?

I've moved onto other employment but I have no objections. I don't have merge privileges myself.

@spf13 bump, can we get this merged or some review on what changes are needed?

@eparis is there any way to get more reviewers on this repo? There are so many outstanding PRs and issues, and the attention this repo gets seems to be extremely preferential and haphazard.

Would still be great for Cobra
/cc @eparis

As pointed out in my review, I'm pretty sure the state and intent of this PR is broken by the splitting of concatenated shortflags.
@jpmcb Just a reminder that I said PRs don't get reviews here, or require social capital outside of github to get attention. But my fork is still available if you decide not to wait any more :)

@underrun Your concern is covered by the whitelisting option
@ijc As pointed out in my review, I think this PR breaks expected behavior
cc; @marckhouzam @jpmcb

@ijc As pointed out in my review, I think this PR breaks expected behavior

@cornfeedhobo Thanks but please see https://github.com/spf13/pflag/pull/199#discussion_r475735582: I'm not planning to do anything further with this PR at this point (maybe I should just close it?). If it isn't going to be merged as is then someone else will have to take it over and address the review.

@ijc My apologies, I totally forgot about that comment. Thanks for the prompt reply. Cheers!

@cornfeedhobo my full concern as laid out in the related cobra issue combined with my commend a month ago is not covered by whitelisting - or I don't think it is. Maybe you could explain how?
@ijc - i'm willing to take this over if there are changes that could get it merged

@underrun I modified this PR a little before merging it into my fork, so maybe you're right, but I'm pretty sure this is covered in this PR. Either way, you can look at my commit history and pull out the relevant changes if you are holding out hope that this will be reviewed by the repo maintainers.

The description says that -uuu foo is somehow treated specially. I'd have to look at things more closely. But if the intention of the user was the flag -u and the value uu, with a separate unrelated argument foo, all of that context would be lost by anything trying to look at unparsed flags right. So it would be impossible for the code handling these unknown flags to correctly handle things.
Instead of using the arbitrary example above let's assume what the user typed was -cblue draw. And this was supposed to mean to something handling unknown flags that the color is supposed to be blue and we're supposed to draw that color. Breaking this into a slice with six different entries seems problematic. You have no idea if the user typed -c -b -l -u -e draw, or what was actually typed. Does this ambiguity not seem problematic?

Instead of using the arbitrary example above let's assume what the user typed was -cblue draw. And this was supposed to mean to something handling unknown flags that the color is supposed to be blue and we're supposed to draw that color. Breaking this into a slice with six different entries seems problematic. You have no idea if the user typed -c -b -l -u -e draw, or what was actually typed. Does this ambiguity not seem problematic?

personally i think it's reasonable that if we are combing unknown argument parsing with allowance for concatenated short flags to disallow concatenating the argument of the last short flag with the list of short flags.
but i think it'd also be possible to stop treating data as unknown short flags after hitting a short flag that is non-boolean?

It would be great if someone was willing to write out a lot of specific test cases to hammer against.

This just got a little more interesting. I decided to write out some test cases, and the first one I wrote seems to uncover a bug, if someone would like to verify:
	testCases := []struct {
		args         []string
		wantFlags    []string
		wantArgs     []string
		wantUnknowns []string
	}{
		// Known flags
		//   StringP("name", "n", ...)
		//   BoolP("enabled", "E", ...)
		// Unknown flags
		//   StringP("group", "g", ...)
		//   BoolP("hidden", "H", ...)
		{
			args:         []string{"--name", "foo", "arg1", "--group", "bar", "arg2", "--enabled", "arg3", "--hidden", "arg4"},
			wantFlags:    []string{"--name", "foo", "--enabled", "true"},
			wantUnknowns: []string{"--group", "bar", "--hidden"},
			wantArgs:     []string{"arg1", "arg2", "arg3", "arg4"},
		},
	}

is that a bug or is that like ... impossible to differentiate with unknown flags where unknown flags can be either boolean or non-boolean?
would this be fixed by disallowing both boolean and non-boolean unknown flags to be handled at the same time and giving users the choice to parse boolean unknown flags or non-boolean unknown flags? I don't like this option but maybe?
another option would be to disallow boolean unknown flags except for the final flag (which mirrors short flag handling).

would this be fixed by disallowing both boolean and non-boolean unknown flags to be handled at the same time and giving users the choice to parse boolean unknown flags or non-boolean unknown flags? I don't like this option but maybe?

@underrun Exactly. That is where this breaks down - do we assume preserve values when no = is used, or do we assume they are arguments, or do we leave that to the developer to toggle through a setting(s)?


Incorporate Huff Review

Looking good.
The only critical one is the acknowledgements (I'm not funded by those things anymore. Best to acknowledge that the department is funding @munkm , but please do not list anything regarding my funding.)
Other edits in the pdf.
main.pdf

These comments were addressed in arfc/2021-bachmann-epjn#1 so I believe we can close out this issue now.


The properties in the GroupMember struct are not in-sync with the API response

Looks like GitLab has updated the API response. Source: https://docs.gitlab.com/ce/api/members.html. The email and created_at fields are no longer available and instead avatar_url and web_url are now returned in the response to listing a group's members.

There's not a real schedule, so mainly when people ask or when I think enough has been changed/added.
So since you asked... v0.11.7 is just released :wink:


One tab does not update

Hi!
I have updated the CV tab on my academic pages multiple times and it does not change in the website. This only happens with this tab, while the others work well. I don't understand why, the website's tab got stuck in an old version of it.

Hello!
the same for me! I updated the config file but changes are not visible on the website!


Smaller flash extent density for lower resolution

I checked the histogram of flash_extent_density with different target resolutions: 2km and 20km (#83 ).
2 km
ds_glm_test = xr.open_dataset('../data/GOES-16/GLM_L2_Grid/2km/OR_GLM-L2-GLMC-M3_G16_s20201530000000_e20201530005000_c20211480438470.nc')

ds_glm_test['flash_extent_density'].plot.hist(bins=np.arange(0, 15, 1))

ds_glm_test['flash_extent_density'].plot(xlim=(0.0175, 0.0230), ylim=(0.078, 0.084), vmin=0, vmax=35)

20 km
ds_glm_test = xr.open_dataset('../data/GOES-16/GLM_L2_Grid/20km/OR_GLM-L2-GLMC-M3_G16_s20201530000000_e20201530005000_c20211882045450.nc')

ds_glm_test['flash_extent_density'].plot.hist(bins=np.arange(0, 15, 1))

ds_glm_test['flash_extent_density'].plot(xlim=(0.0175, 0.0230), ylim=(0.078, 0.084), vmin=0, vmax=35)

Problems

As the pixel is larger for the 20 km option, the FED (flash count in each pixel during 5min) should be larger. But, it's smaller.
Many FED values are smaller than 1. What does this indicate?

Oh, I see. It seems the FED is normalized by the area: Count per nominal  313599 microradian^2 pixel per 5.0 min.
Could you cite the lines of codes calculating these variables here? It's like a black box for us now ;)

Here's the illustration (Fig.4 of @deeplycloudy 's paper):

FED is the summation of flashcount * grid_fraction.
So, if the grid is large like 10 km, the grid_fraction is smaller and the flashcount may be not change. Then, it leads to the smaller FED.


PR for the new version.

1.0.1 -> 1.1.0
[Changes]

Print current version when starting program.
Improve exit routines.

Thank you for your PR.


AlpineRepo doesn't work for some repositories

Should add more details soon. This is here just to keep track of an issue.

Okay, it works with {branch: "", and repo: "", url: http://full-url}. So this issue may be closed.


fix: firefox compatibility

When copying from the static class methods to the jsep function, don't rely on the ordering of keys. Instead, check for properties that are allowed to be set (![prototype, name, length]), by checking if they already exist on jsep. This fixes the "length" is readonly error in firefox (but works in Chrome/Node)
Fixes #178

@EricSmekens - would you like to try the CI build (#177 ) for this?

I'm quite busy until after this weekend, so you have my permission to try this out of you want to.
If you need some help on the permission side, let me know, otherwise I can pick this up and try it out after next weekend.


Racing condition with parquet writer

Hi
After debugging a lot secor when writing Parquet from Avro message. I come to the conclusion that a possible racing condition can occurs.

So Iv'e a topic with 300 Partitions
Start 10 Pods - 7 Core per pod
7 Thread per pod

Result not enough parquet writer to handle every partition. So start a IndexOutOfBoundsException
This occurs into the parquet writer no code related to secor. As you know the parquet writer is not thread safe. Is there a possibility one Parquet writer is used by more that 1 thread ?
My investigations show me that assumption is correct because the only workaround I found at this moment is to have a much higher number of secor.consumer.threads to be sure that Parquet writer is not reused by mistake
Can you confirm ?
Thanks

You can turn on secor debug and check the following log line to see how
many writers are created:
LOG.debug("created writer for path {}", path.getLogFilePath());
From the code, we are going to create a new writer for each path.
You can also use jmap to count how many Parquet Writer objects in the heap
On Sun, Jan 3, 2021 at 6:27 AM Richard Grossman<EMAIL_ADDRESS>wrote:

Hi
After debugging a lot secor when writing Parquet from Avro message. I come
to the conclusion that a possible racing condition can occurs.

So Iv'e a topic with 300 Partitions
Start 10 Pods - 7 Core per pod
7 Thread per pod

Result not enough parquet writer to handle every partition. So start a
IndexOutOfBoundsException
This occurs into the parquet writer no code related to secor. As you
know the parquet writer is not thread safe. Is there a possibility one
Parquet writer is used by more that 1 thread ?
My investigations show me that assumption is correct because the only
workaround I found at this moment is to have a much higher number of
secor.consumer.threads to be sure that Parquet writer is not reused by
mistake
Can you confirm ?
Thanks
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pinterest/secor/issues/1792, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABYJP7YVNGI3MOLCADWURJDSYB5FXANCNFSM4VR5DMXA
.

You can turn on secor debug and check the following log line to see how
many writers are created:
LOG.debug("created writer for path {}", path.getLogFilePath());
From the code, we are going to create a new writer for each path.
You can also use jmap to count how many Parquet Writer objects in the heap
On Sun, Jan 3, 2021 at 6:27 AM Richard Grossman<EMAIL_ADDRESS>wrote:

Hi
After debugging a lot secor when writing Parquet from Avro message. I come
to the conclusion that a possible racing condition can occurs.

So Iv'e a topic with 300 Partitions
Start 10 Pods - 7 Core per pod
7 Thread per pod

Result not enough parquet writer to handle every partition. So start a
IndexOutOfBoundsException
This occurs into the parquet writer no code related to secor. As you
know the parquet writer is not thread safe. Is there a possibility one
Parquet writer is used by more that 1 thread ?
My investigations show me that assumption is correct because the only
workaround I found at this moment is to have a much higher number of
secor.consumer.threads to be sure that Parquet writer is not reused by
mistake
Can you confirm ?
Thanks
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pinterest/secor/issues/1792, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABYJP7YVNGI3MOLCADWURJDSYB5FXANCNFSM4VR5DMXA
.

Hi
My question was if my assumption are valid ?
yes we can debug with many tools but As I read the code I see there is 1 parquet writer by file because it's stored in a hashset<path,writer> but is there by any chance a problem a race condition trying to use the same parquet writer by 2 threads ?

Hi
My question was if my assumption are valid ?
yes we can debug with many tools but As I read the code I see there is 1 parquet writer by file because it's stored in a hashset<path,writer> but is there by any chance a problem a race condition trying to use the same parquet writer by 2 threads ?

From the code, it doesn't look like writers are going to be shared between
threads.  The edge case I can think of is when the consumer group
rebalances, some of the work and related file paths being shifted from
thread 1 to thread 2, but in that case the thread 1 should already
relinquish the work on the given path.  If you do see the problem happens
after consumer rebalance (I think there are some logging categories
indicating consumer rebalances), you can add some code to clear the
hashset<path,writer> and writers on consumer rebalance (there is a callback
when the consumer rebalance happens).
On Mon, Jan 4, 2021 at 4:16 AM Richard Grossman<EMAIL_ADDRESS>wrote:

Hi
My question was if my assumption are valid ?
yes we can debug with many tools but As I read the code I see there is 1
parquet writer by file because it's stored in a hashset<path,writer> but is
there by any chance a problem a race condition trying to use the same
parquet writer by 2 threads ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pinterest/secor/issues/1792#issuecomment-753942714,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABYJP74DHYAOM62ADA3DBD3SYGWQJANCNFSM4VR5DMXA
.

From the code, it doesn't look like writers are going to be shared between
threads.  The edge case I can think of is when the consumer group
rebalances, some of the work and related file paths being shifted from
thread 1 to thread 2, but in that case the thread 1 should already
relinquish the work on the given path.  If you do see the problem happens
after consumer rebalance (I think there are some logging categories
indicating consumer rebalances), you can add some code to clear the
hashset<path,writer> and writers on consumer rebalance (there is a callback
when the consumer rebalance happens).
On Mon, Jan 4, 2021 at 4:16 AM Richard Grossman<EMAIL_ADDRESS>wrote:

Hi
My question was if my assumption are valid ?
yes we can debug with many tools but As I read the code I see there is 1
parquet writer by file because it's stored in a hashset<path,writer> but is
there by any chance a problem a race condition trying to use the same
parquet writer by 2 threads ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pinterest/secor/issues/1792#issuecomment-753942714,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABYJP74DHYAOM62ADA3DBD3SYGWQJANCNFSM4VR5DMXA
.


Bigtable: Decouple TableAdminClient from BigtableTableAdminSettings.

This is in preparation for renaming the auto generated GAPIC clients &
settings to be prefixed with 'Base'. This will make it easier to
understand the layout of the code: the GAPIC generated client/settings
will be called BaseBigtableTableAdmin{Client,Settings}, while the
handwritten overlay will be called BigtableTableAdmin{Client,Settings}.

oops, sorry about that. Should be fixed now


fix broken github pages builds

fixed https://github.com/feranto/Lab_APIM/commit/cef4abcadeaf218cb8007e5c951a30d3fc50a873


Fix importing CJS, RESM, and ESM

This aligns ses/package.json such that SES can be imported with a CommonJS
loader, with the esm package using node -r esm, as well as Node.js ESM
support, all using the same "ses" name.
node main.js
const { lockdown } = require('ses');

node main.mjs and node -r esm main.js
import { lockdown } = import('ses');

This change includes a regression test that verifies each of these cases.
Fixes #214

You might be accidentally importing a different version of SES in your integration tests.  Maybe manage the integration test with lerna to hoist the dependencies and ensure you're actually getting the SES you mean?

You might be accidentally importing a different version of SES in your integration tests. Maybe manage the integration test with lerna to hoist the dependencies and ensure you're actually getting the SES you mean?

The failing lint seems to indicate that this is necessary. Stay tuned. 📻


release notes should include browser link to online copy

VS Code release notes open in webview, which is annoying for people wanting a normal browse experience. Every release note edition in the future should include a link to online copy we can open in a full featured browser.
(I'd prefer the web view didn't open at all, it only ticks me because of it's limitations, but that's asking for too much)

VSCode Version: 1.12
OS Version: only 10.12.4

Steps to Reproduce:

upgrade VS Code

@gregvanl that makes sense to me. We should add a link as proposed.

Adding @seanmcbreen for visibility.
From doc feedback and Google Analytics data, we still see plenty of people reading the release notes online.

Fixed with vscode-docs https://github.com/Microsoft/vscode-docs/commit/14a9f98c0164a45a810a8ab27ecbdd73f939e202


Home page could be better

please assign me this work under hacktoberfest
thank you

i want to make home page should be more attractive by using shadcn or antd libraries
please assign me this work under hacktoberfest
thank you

The navbar is not aligned properly I can fix that.


[Question] How to get navigation bar back after hide?

Describe the Question
I hide the top navigation bar in UTM, there is a notice alert message box shows to me, But I close the message box uncareful, So I did not see the message clearly. So, How can I get the navigation bar back?

3 fingers swipe down

swipe down with 3 fingers

swipe down with 3 fingers

Thanks!


A dot (.) in Regex Causes Errors

The following is a simple example of a regular expression as "[0-9]+.[0-9]".
Issue number #1:  Once the dot is typed, nothing can be updated to the left of the dot.
Issue number #2:  Using the backspace does not remove characters left of the dot, but just repeatedly copies the character over proceeding characters.
It appears the dot is treated differently than other characters.  Is there a flag or setting to remove this special functionality?

You can use
\\\.

it works well!

@barofusa ,
Works in the current


mode() indicates current mode is Operator-pending in operatorfunc

Describe the bug
In an operatorfunc, mode(1) indicates the current mode is Operator-pending; it returns no, nov, noV or noCTRL-V. But it seems a bit strange because the text to be operated on has already been determined at that moment. I think it makes more sense if it returns a Normal mode that the operator was used in, i.e. n, niI, niR or niV.
To Reproduce

Run vim -Nu NONE.

:source this script:
nnoremap <expr> ,o SetOperatorFunc() .. 'g@'
function SetOperatorFunc()
  set operatorfunc=OperatorFunc
  return ''
endfunction
function OperatorFunc(_)
  echo mode(1)
endfunction
let outputs = ''
let outputs ..= execute("normal ,ol")
let outputs ..= execute("normal ,ovl")
let outputs ..= execute("normal i\<C-o>,ol")
let outputs ..= execute("normal i\<C-o>,ovl")
echo outputs[1 :]

This is echo'ed:
no
nov
no
nov

Expected behavior
This is echo'ed:
n
n
niI
niI

Environment

Vim 8.2.3469
macOS 10.15.7
iTerm2

Additional context
Making this change not only makes sense, but also brings some benefits I believe; we can use it to change the operator behavior depending on the kind of the Normal mode, like this:
nnoremap <expr> ,p SetOperatorFunc() .. 'g@l'
function SetOperatorFunc()
  set operatorfunc=PutWithHighlight
  return ''
endfunction
function PutWithHighlight(_)
  normal! p
  if mode(1)[: 1] ==# 'ni' && getregtype('"') ==# 'v' && len(getreg('"', 1, 1)) == 1
    " Adjust the cursor position.
    normal! l
  endif
  call Highlight(getpos("'["), getpos("']"))
endfunction

Fixed by https://github.com/vim/vim/commit/75c30e96cf280a8cc01ac01c41a9252db3e503cc.


Link to List of shortnames for regions should be attached.

This documentation shows that some resources needs {region}.resourcetype.windows.net
However it's not clear what the shortnames for the regions are.
Could a link/reference in the documentation point to the file:
https://download.microsoft.com/download/1/2/6/126a410b-0e06-45ed-b2df-84f353034fa1/AzureRegionCodesList.docx
Would make it easier for whoever is reading the docs.

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

ID: a88af182-32aa-a8f3-359d-b92ae1cfb8c7
Version Independent ID: 01ce07fc-4bc2-def5-9ecd-a80330ad9488
Content: Azure Private Endpoint DNS configuration
Content Source: articles/private-link/private-endpoint-dns.md
Service: private-link
GitHub Login: @mblanco77
Microsoft Alias: allensu

@SebastianClaesson, Thanks for reaching out. We will investigate and update this thread.

Sorry but it seems that is not correct either, because some resources use "westeurope" and not "we" as the prefix for region.
Such as "westeurope.azmk8s.io" while for backup resourcetype it is "we.backup.windows.azure.com"

@SebastianClaesson, Appreciate your patience. We are working towards updating the document accordingly.
We are closing this issue for now. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.


Don't include .gitignore into npm module

The .gitignore file causes an npm "UNMET DEPENDENCY" on async when we git clone our web project. This means the async module for us doesn't get checked in to our code. Do you recommend installing async module at the root of our web project?

You shouldn't be checking in npm modules into your code. They don't belong there, as they are external dependencies.
You should create a package.json in the root directory of your project, and specify all the npm modules you need there (including connect-less). Then, when you check out the code, you run npm install -d and npm takes care of installing all the modules, including their dependencies.
Every major npm module I checked does the same thing, so I believe this is the accepted "best practice".
Let me know if you don't agree for some specific reason!

Thanks for the feedback. I'm pretty new to node. Sorry for the rookie comment.

No problem at all! You're welcome


Transformers : Error while fitting TFBertForSequenceClassification model

Hi,
First of all thanks a lot making directML compatible with TensorFlow > 2 !
As the Transformers lib needs TensorFlow >= 2.3 i had got hope my TFBertForSequenceClassification model was working with my AMD GPU card (Rx 6800)
Unfortuntly, this is not the case. (important detail : it takes a crazy long time but works on CPU with standard Tensorflow lib)
My env:
windows 11 PRO 64bit : 21H2
python 3.8.13
tensorflow-cpu 2.9.1
tensorflow-directml-plugin 0.0.1.dev220621
CPU : Ryzen 5600X,
GPU : Rx 6800
The GPU is rightly recognized:
tf.config.list_physical_devices('GPU')
[PhysicalDevice(name='/physical_device:GPU:0', device_type='GPU')]

My code :
bert_model = TFBertForSequenceClassification.from_pretrained('bert-base-uncased', num_labels=2)

callbacks = [tf.keras.callbacks.ModelCheckpoint(filepath=model_save_path,
                                                save_weights_only=True,
                                                monitor='val_loss',
                                                mode='min',
                                                save_best_only=True),
             keras.callbacks.TensorBoard(log_dir=log_dir)]

print('\nBert Model', bert_model.summary())

loss = tf.keras.losses.SparseCategoricalCrossentropy(from_logits=True)
metric = [tf.keras.metrics.SparseCategoricalAccuracy('accuracy')]
optimizer = tf.keras.optimizers.Adam(learning_rate=2e-5,epsilon=1e-08)

bert_model.compile(loss=loss, optimizer=optimizer, metrics=metric)

#OUTPUT :
Model: "tf_bert_for_sequence_classification_3"
_________________________________________________________________
 Layer (type)                Output Shape              Param #
=================================================================
 bert (TFBertMainLayer)      multiple                  109482240

 dropout_151 (Dropout)       multiple                  0

 classifier (Dense)          multiple                  1538

=================================================================
Total params: 109,483,778
Trainable params: 109,483,778
Non-trainable params: 0
_________________________________________________________________

Above code works well but when reaching the fit :
history=bert_model.fit([X_train, Mask_Train],
                       y_train,
                       batch_size=32,
                       epochs=EPOCHS,
                       validation_data=([X_test, Mask_test], y_test),
                       callbacks=callbacks)

The GPU VRAM begins to receive data (i'm monitoring it via Radeon Adrenalin Software) and suddenly an error message (see below) appears !
The Error Message :
Epoch 1/3
---------------------------------------------------------------------------
InvalidArgumentError                      Traceback (most recent call last)
File <timed exec>:2, in <module>

File ~\anaconda3\envs\P7_Bert_TF29_PYT38\lib\site-packages\keras\utils\traceback_utils.py:67,
 in filter_traceback.<locals>.error_handler(*args, **kwargs)
     65 except Exception as e:  # pylint: disable=broad-except
     66   filtered_tb = _process_traceback_frames(e.__traceback__)
---> 67   raise e.with_traceback(filtered_tb) from None
     68 finally:
     69   del filtered_tb

File ~\anaconda3\envs\P7_Bert_TF29_PYT38\lib\site-packages\tensorflow\python\eager\execute.py:54,
 in quick_execute(op_name, num_outputs, inputs, attrs, ctx, name)
     52 try:
     53   ctx.ensure_initialized()
---> 54   tensors = pywrap_tfe.TFE_Py_Execute(ctx._handle, device_name, op_name,
     55                                       inputs, attrs, num_outputs)
     56 except core._NotOkStatusException as e:
     57   if name is not None:

InvalidArgumentError: Cannot assign a device for operation tf_bert_for_sequence_classification_3/bert/embeddings/Gather:
Could not satisfy explicit device specification ''
because the node {{colocation_node tf_bert_for_sequence_classification_3/bert/embeddings/Gather}} was colocated
with a group of nodes that required incompatible device '/job:localhost/replica:0/task:0/device:GPU:0'.
All available devices [/job:localhost/replica:0/task:0/device:CPU:0, /job:localhost/replica:0/task:0/device:GPU:0].
Colocation Debug Info:
Colocation group had the following types and supported devices:
Root Member(assigned_device_name_index_=2 requested_device_name_='/job:localhost/replica:0/task:0/device:GPU:0'
assigned_device_name_='/job:localhost/replica:0/task:0/device:GPU:0'
resource_device_name_='/job:localhost/replica:0/task:0/device:GPU:0' supported_device_types_=[CPU] possible_devices_=[]

StridedSlice: CPU
Unique: GPU CPU
Shape: GPU CPU
_Arg: GPU CPU
ResourceGather: GPU CPU
Const: GPU CPU
UnsortedSegmentSum: CPU
Mul: GPU CPU
ReadVariableOp: GPU CPU
AssignVariableOp: GPU CPU
ResourceScatterAdd: GPU CPU
Sqrt: GPU CPU
AddV2: GPU CPU
RealDiv: GPU CPU
AssignSubVariableOp: GPU CPU
NoOp: GPU CPU

Colocation members, user-requested devices, and framework assigned devices, if any:
  tf_bert_for_sequence_classification_3_bert_embeddings_gather_resource (_Arg)
       framework assigned device=/job:localhost/replica:0/task:0/device:GPU:0
  adam_adam_update_readvariableop_resource (_Arg)
       framework assigned device=/job:localhost/replica:0/task:0/device:GPU:0
  adam_adam_update_readvariableop_2_resource (_Arg)
       framework assigned device=/job:localhost/replica:0/task:0/device:GPU:0
  tf_bert_for_sequence_classification_3/bert/embeddings/Gather (ResourceGather)
  Adam/Adam/update/Unique (Unique) /job:localhost/replica:0/task:0/device:GPU:0
  Adam/Adam/update/Shape (Shape) /job:localhost/replica:0/task:0/device:GPU:0
  Adam/Adam/update/strided_slice/stack (Const) /job:localhost/replica:0/task:0/device:GPU:0
  Adam/Adam/update/strided_slice/stack_1 (Const) /job:localhost/replica:0/task:0/device:GPU:0
  Adam/Adam/update/strided_slice/stack_2 (Const) /job:localhost/replica:0/task:0/device:GPU:0
  Adam/Adam/update/strided_slice (StridedSlice) /job:localhost/replica:0/task:0/device:GPU:0
  Adam/Adam/update/UnsortedSegmentSum (UnsortedSegmentSum) /job:localhost/replica:0/task:0/device:GPU:0
  Adam/Adam/update/mul (Mul) /job:localhost/replica:0/task:0/device:GPU:0
  Adam/Adam/update/ReadVariableOp (ReadVariableOp)
  Adam/Adam/update/mul_1 (Mul) /job:localhost/replica:0/task:0/device:GPU:0
  Adam/Adam/update/AssignVariableOp (AssignVariableOp) /job:localhost/replica:0/task:0/device:GPU:0
  Adam/Adam/update/ResourceScatterAdd (ResourceScatterAdd) /job:localhost/replica:0/task:0/device:GPU:0
  Adam/Adam/update/ReadVariableOp_1 (ReadVariableOp)
  Adam/Adam/update/mul_2 (Mul) /job:localhost/replica:0/task:0/device:GPU:0
  Adam/Adam/update/mul_3 (Mul) /job:localhost/replica:0/task:0/device:GPU:0
  Adam/Adam/update/ReadVariableOp_2 (ReadVariableOp)
  Adam/Adam/update/mul_4 (Mul) /job:localhost/replica:0/task:0/device:GPU:0
  Adam/Adam/update/AssignVariableOp_1 (AssignVariableOp) /job:localhost/replica:0/task:0/device:GPU:0
  Adam/Adam/update/ResourceScatterAdd_1 (ResourceScatterAdd) /job:localhost/replica:0/task:0/device:GPU:0
  Adam/Adam/update/ReadVariableOp_3 (ReadVariableOp)
  Adam/Adam/update/Sqrt (Sqrt) /job:localhost/replica:0/task:0/device:GPU:0
  Adam/Adam/update/mul_5 (Mul) /job:localhost/replica:0/task:0/device:GPU:0
  Adam/Adam/update/add (AddV2) /job:localhost/replica:0/task:0/device:GPU:0
  Adam/Adam/update/truediv (RealDiv) /job:localhost/replica:0/task:0/device:GPU:0
  Adam/Adam/update/AssignSubVariableOp (AssignSubVariableOp) /job:localhost/replica:0/task:0/device:GPU:0
  Adam/Adam/update/group_deps/NoOp (NoOp) /job:localhost/replica:0/task:0/device:GPU:0
  Adam/Adam/update/group_deps/NoOp_1 (NoOp) /job:localhost/replica:0/task:0/device:GPU:0
  Adam/Adam/update/group_deps (NoOp) /job:localhost/replica:0/task:0/device:GPU:0

      [[{{node tf_bert_for_sequence_classification_3/bert/embeddings/Gather}}]]
      [Op:__inference_train_function_57566]

Thanks in advance for any Help !
Have a good day.

Hey @ImRobot777, I can't be 100% sure without having a full repro, but from the log above it looks like all that's missing is the int32 data type support for StridedSlice and UnsortedSegmentSum. We already have implementations for those ops, so all that's missing should be to add support for int32. We are currently planning to release a new version of the plugin shortly after the upcoming TensorFlow 2.10 release, so you shouldn't have to wait too long.
If I provide you with a development wheel after the change has been merged in, would you be willing to try it out and let me know if it fixes your issue? Or if you're comfortable with building from source that should also work.

Hi,
Thanks a lot for your help @PatriceVignola
Of course i wanna try with a development wheel, i'll be so relieved and happy that I finally got my code to work !
You just cannot imagine how many different test i've done (all possible combinations with Tensorflow 1.15 with tensorflow-directml to TS 2.9(all possible variant std, -cpu, -gpu)  with tensorflow-directml-plugin and different compatible versions of python... tried to se soft_placement=true in the head of my jupyter notebook too...), the code and env from this issue form are the "best" results i've had.
Unfortunatly, the last time i've compiled sources was 20 years before for C++ student project :-P
That means that i do not know how to build package from source but if you have in mind a simple tutorial to build from source, i'll do it !
If it fix my issue, you'll be the first to know it :-)
Have a good day.
Guillaume

We have a the first nightly build that should contain the fixes: https://github.com/microsoft/tensorflow-directml-plugin/actions/runs/2887210312
Please try it out and let me know how it works for you! Note that we haven't been focusing on Transformer models performance thus far so we don't know how well we perform on them, but this is something we'll be focusing on in the next few months. Our main concern right now is making sure that they run to completion without crashing :)

Hi Patrice,
I'm so sorry haven't seen your answer this morning.
I was so late on my project that i've had to replace my AMD GPU (that i love so much) by a Nvidia one, 2 times less powerfull but run well my code at least...
I do not know when i'll have the time to do another GPU Switch (+drivers, cuda and so on) but when i'll do it, i'll test the built immediatly even if i'm not really sure what i'm supposed to do with the link in your previous response.
It looks like a docker file and i've never tried docker yet, will it work on windows 11 ?
Best Regards, have a good day.
Guillaume

No problem! tensorflow-directml-plugin is also compatible with Nvidia. The link I posted is just a page where you can download the package wheels. For example, if you want to test the Windows package for python 3.10, you would download this zip file, unzip it and call pip install tensorflow_directml_plugin-0.0.1-cp310-cp310-win_amd64.whl.

My bad, thank you for the explanations Patrice !
I've got just 2 points to add, a note and a question:
1/ I've only installed package nammed tensorflow and note tensorflow-gpu, cause since tensorflow 2.5, the standart package manage both CPU and GPU and it works well with the RTX 3060
2/ I've forgotten that but as you mention it, i remember now that directml-plugin can work with nvidia GPU.
Is that mean that without switching again my GPUs, i could reproduce the issue on the Nvidia card with the current directML-plugin and then see if it work with the nightly version of your link ???
Best Regards,
Guillaume

Yes! You don't need to switch GPUs to try it out. The only difference is that you'll need the tensorflow-cpu package instead of tensorflow alongside the plugin and you don't have to install or configure CUDA or cuDNN.

Great !
But,  indeed, i needed installing CUDA and cuDNN for the first try of my new Nvidia GPU, so they are already installed on my OS ?
So, will i still be able to reproduce the issue ??? (i mean in a new conda virtual env of course with tensorflow-directml-plugin)

You will be able to reproduce the issue. What I meant is that you don't need CUDA or cuDNN to make tensorflow-directml-plugin work with your Nvidia card :)

OK, thanks a lot,
I'll try to test it as soon as possible !
And come back to you

Well,
I've test it and the installation worked well !
But unfortunatly lot of fatal errors appeared when importing the package :
one of them
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
Input In [4], in <cell line: 28>()
     24 import tensorflow as tf
     25 #tf.config.set_soft_device_placement(True)
     26 #tf.compat.v1.config.set_soft_device_placement(True)
---> 28 import tensorflow_hub as hub
     30 import tensorflow.keras as keras
     32 from keras.callbacks import ModelCheckpoint

File ~\anaconda3\envs\P7_DirectML_38\lib\site-packages\tensorflow_hub\__init__.py:85, in <module>
     74   if (distutils.version.LooseVersion(tf.__version__) <
     75       distutils.version.LooseVersion(required_tensorflow_version)):
     76     raise ImportError(
     77         "\n\nThis version of tensorflow_hub requires tensorflow "
     78         "version >= {required}; Detected an installation of version {present}. "
   (...)
     82             required=required_tensorflow_version,
     83             present=tf.__version__))
---> 85 _ensure_tf_install()
     88 from tensorflow_hub.estimator import LatestModuleExporter
     89 from tensorflow_hub.estimator import register_module_for_export

File ~\anaconda3\envs\P7_DirectML_38\lib\site-packages\tensorflow_hub\__init__.py:74, in _ensure_tf_install()
     63 #
     64 # Update this whenever we need to depend on a newer TensorFlow release.
     65 #
   (...)
     71 # and character class transitions.
     72 #
     73 required_tensorflow_version = "1.15.0"
---> 74 if (distutils.version.LooseVersion(tf.__version__) <
     75     distutils.version.LooseVersion(required_tensorflow_version)):
     76   raise ImportError(
     77       "\n\nThis version of tensorflow_hub requires tensorflow "
     78       "version >= {required}; Detected an installation of version {present}. "
   (...)
     82           required=required_tensorflow_version,
     83           present=tf.__version__))

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

Then another try gives me a another error that said There is no Keras attribute in tensorflow module.
And finally, another one that shows incompatibility with transformers package
i do not manage to reproduce the 2 last errors after having re-installed the virtual env, but they could appear again if your team fix the first issue.
Wait and see, hope it will be fixed soon.
Have a goo WE

It looks like some of your installed packages were conflicting with each other (e.g. required_tensorflow_version  = "1.15.0" in tensorflow_hub). I'm not sure how this package made it into your virtual environment but tensorflow-directml-plugin only depends on tensorflow-cpu>=2.10, so it couldn't have been the cause.

See the content of my environment and search for tensorflow, you'll see that 2.10 has been installed :
name: P7_DirectML_38
channels:
  - defaults
dependencies:
  - argon2-cffi=21.3.0=pyhd3eb1b0_0
  - argon2-cffi-bindings=21.2.0=py38h2bbff1b_0
  - asttokens=2.0.5=pyhd3eb1b0_0
  - attrs=21.4.0=pyhd3eb1b0_0
  - backcall=0.2.0=pyhd3eb1b0_0
  - beautifulsoup4=4.11.1=py38haa95532_0
  - bleach=4.1.0=pyhd3eb1b0_0
  - ca-certificates=2022.07.19=haa95532_0
  - certifi=2022.6.15=py38haa95532_0
  - cffi=1.15.1=py38h2bbff1b_0
  - colorama=0.4.5=py38haa95532_0
  - console_shortcut=0.1.1=4
  - debugpy=1.5.1=py38hd77b12b_0
  - decorator=5.1.1=pyhd3eb1b0_0
  - defusedxml=0.7.1=pyhd3eb1b0_0
  - entrypoints=0.4=py38haa95532_0
  - executing=0.8.3=pyhd3eb1b0_0
  - importlib_resources=5.2.0=pyhd3eb1b0_1
  - ipykernel=6.9.1=py38haa95532_0
  - ipython=8.4.0=py38haa95532_0
  - ipython_genutils=0.2.0=pyhd3eb1b0_1
  - jedi=0.18.1=py38haa95532_1
  - jinja2=3.0.3=pyhd3eb1b0_0
  - jsonschema=4.4.0=py38haa95532_0
  - jupyter_client=7.2.2=py38haa95532_0
  - jupyter_core=4.10.0=py38haa95532_0
  - jupyterlab_pygments=0.1.2=py_0
  - libsodium=1.0.18=h62dcd97_0
  - markupsafe=2.1.1=py38h2bbff1b_0
  - matplotlib-inline=0.1.2=pyhd3eb1b0_2
  - mistune=0.8.4=py38he774522_1000
  - nbclient=0.5.13=py38haa95532_0
  - nbconvert=6.4.4=py38haa95532_0
  - nbformat=5.3.0=py38haa95532_0
  - nest-asyncio=1.5.5=py38haa95532_0
  - notebook=6.4.12=py38haa95532_0
  - openssl=1.1.1q=h2bbff1b_0
  - packaging=21.3=pyhd3eb1b0_0
  - pandocfilters=1.5.0=pyhd3eb1b0_0
  - parso=0.8.3=pyhd3eb1b0_0
  - pickleshare=0.7.5=pyhd3eb1b0_1003
  - prometheus_client=0.14.1=py38haa95532_0
  - prompt-toolkit=3.0.20=pyhd3eb1b0_0
  - pure_eval=0.2.2=pyhd3eb1b0_0
  - pycparser=2.21=pyhd3eb1b0_0
  - pygments=2.11.2=pyhd3eb1b0_0
  - pyparsing=3.0.4=pyhd3eb1b0_0
  - pyrsistent=0.18.0=py38h196d8e1_0
  - python=3.8.13=h6244533_0
  - python-dateutil=2.8.2=pyhd3eb1b0_0
  - python-fastjsonschema=2.15.1=pyhd3eb1b0_0
  - pywin32=302=py38h2bbff1b_2
  - pywinpty=2.0.2=py38h5da7b33_0
  - pyzmq=23.2.0=py38hd77b12b_0
  - send2trash=1.8.0=pyhd3eb1b0_1
  - setuptools=61.2.0=py38haa95532_0
  - six=1.16.0=pyhd3eb1b0_1
  - soupsieve=2.3.1=pyhd3eb1b0_0
  - sqlite=3.39.2=h2bbff1b_0
  - stack_data=0.2.0=pyhd3eb1b0_0
  - terminado=0.13.1=py38haa95532_0
  - testpath=0.6.0=py38haa95532_0
  - tornado=6.1=py38h2bbff1b_0
  - traitlets=5.1.1=pyhd3eb1b0_0
  - typing-extensions=4.3.0=py38haa95532_0
  - typing_extensions=4.3.0=py38haa95532_0
  - vc=14.2=h21ff451_1
  - vs2015_runtime=14.27.29016=h5e58377_2
  - wcwidth=0.2.5=pyhd3eb1b0_0
  - webencodings=0.5.1=py38_1
  - wheel=0.37.1=pyhd3eb1b0_0
  - wincertstore=0.2=py38haa95532_2
  - winpty=0.4.3=4
  - zeromq=4.3.4=hd77b12b_0
  - zipp=3.8.0=py38haa95532_0
  - pip:
    - absl-py==1.2.0
    - astunparse==1.6.3
    - cachetools==5.2.0
    - charset-normalizer==2.1.1
    - cycler==0.11.0
    - filelock==3.8.0
    - flatbuffers==2.0
    - fonttools==4.36.0
    - gast==0.4.0
    - google-auth==2.11.0
    - google-auth-oauthlib==0.4.6
    - google-pasta==0.2.0
    - grpcio==1.47.0
    - h5py==3.7.0
    - huggingface-hub==0.8.1
    - idna==3.3
    - importlib-metadata==4.12.0
    - joblib==1.1.0
    - keras==2.10.0rc1
    - keras-preprocessing==1.1.2
    - kiwisolver==1.4.4
    - libclang==14.0.6
    - markdown==3.4.1
    - matplotlib==3.5.3
    - numpy==1.23.2
    - oauthlib==3.2.0
    - opt-einsum==3.3.0
    - pandas==1.4.3
    - pillow==9.2.0
    - pip==22.2.2
    - protobuf==3.19.4
    - pyasn1==0.4.8
    - pyasn1-modules==0.2.8
    - pytz==2022.2.1
    - pyyaml==6.0
    - regex==2022.8.17
    - requests==2.28.1
    - requests-oauthlib==1.3.1
    - rsa==4.9
    - scikit-learn==1.1.2
    - scipy==1.9.0
    - sklearn==0.0
    - tensorboard==2.9.1
    - tensorboard-data-server==0.6.1
    - tensorboard-plugin-wit==1.8.1
    - tensorflow-cpu==2.10.0rc1
    - tensorflow-directml-plugin==0.0.1
    - tensorflow-estimator==2.10.0rc0
    - tensorflow-hub==0.12.0
    - tensorflow-intel==2.10.0rc1
    - tensorflow-io-gcs-filesystem==0.26.0
    - termcolor==1.1.0
    - threadpoolctl==3.1.0
    - tokenizers==0.12.1
    - tqdm==4.64.0
    - transformers==4.21.1
    - urllib3==1.26.11
    - werkzeug==2.2.2
    - wrapt==1.14.1

May be, i should not run python -m pip install --upgrade pip  first ???

PS : I just forgot to mention that with current stable tensorflow-directml-plugin, i've managed to reproduce with the Nvidia card the exact same error that with my AMD card

Well,
By uninstalling tensorflow-hub package and removing it from my packages import, i manage to get the 1st error message i saw with this directml nightly package :
---------------------------------------------------------------------------
ModuleNotFoundError                       Traceback (most recent call last)
Input In [2], in <cell line: 28>()
     24 import tensorflow as tf
     25 #tf.config.set_soft_device_placement(True)
     26 #tf.compat.v1.config.set_soft_device_placement(True)
---> 28 import tensorflow_hub as hub
     30 import tensorflow.keras as keras
     32 from keras.callbacks import ModelCheckpoint

ModuleNotFoundError: No module named 'tensorflow_hub'

I think the version check that tensorflow-hub does for the version of TensorFlow unfortunately just doesn't work with rc1 versions or development versions, which explains the error message above.

Yeah, i thought about something like that, that's why i've uninstalled it and got the first error message (about Keras) i talked about before, see above ;-)

I think the version check that tensorflow-hub does for the version of TensorFlow unfortunately just doesn't work with rc1 versions or development versions, which explains the error message above.

Yeah, i thought about something like that, that's why i've uninstalled it and got the first error message (about Keras) i talked about before, see above ;-)

I think the version check that tensorflow-hub does for the version of TensorFlow unfortunately just doesn't work with rc1 versions or development versions, which explains the error message above.

Yeah, i thought about something like that, that's why i've uninstalled it and got the first error message (about Keras) i talked about before, see above ;-)

Ho sorry, as i was coming for news, by reading my above answear, i saw that it has probably posted the wrong screen shot, or there is another issue as i've removed tensorflow_hub package.
I must go deeper in my tests and analysis, but i'm not having access to my working PC right now.
I'll came back with news as soon as possible !

Hi, i'm back for tests.
Do i have to get a nightly package of directML-plugin again or the stable published one ?

So with the new nightly, i got this error :
'''python
ModuleNotFoundError                       Traceback (most recent call last)
Input In [3], in <cell line: 30>()
24 import tensorflow as tf
25 #tf.config.set_soft_device_placement(True)
26 #tf.compat.v1.config.set_soft_device_placement(True)
27
28 #import tensorflow_hub as hub
---> 30 import tensorflow.keras as keras
32 from keras.callbacks import ModelCheckpoint
34 #BERT
ModuleNotFoundError: No module named 'tensorflow.keras'
'''

tensorflow-directml-plugin has nothing to do with keras, so I think there's some problems in your environment. At this point, I think it's better to wait for the release of tensorflow-cpu 2.10.0 (which should release any day now) and create a clean environment when it's out.

I agree but my virtual env is completly new and the command lines i've used to install the different package of my project are the same than the package of my stable env that make tensorflow(standart not directML) works with my RTX 3060.
The only difference between these 2 virtual env is the tensorflow_directml_plugin-0.0.1-cp38-cp38-win_amd64.whl that is replacing the standar tensorflow package.
For reminding, when i use the official directML-plugin (so not the nightly) i can import my package without any problems.
The only issye is the first one for which i've created this ticket.

Hi,
Well, so, i've just tested with tensorflow-cpu and even before reaching the .fit(...) code i've got a Jupyter kernel crash, see below

It seems that the crash is occuring when trying to execute this line:
tf.keras.metrics.SparseCategoricalAccuracy('accuracy')

@ImRobot777 we just released version 0.1.0.dev220928 which adds the missing UnsortedSegmentSum and StridedSlice operators. From our internal transformers testing, we were able to run some of the example transformer models. If you're still having problems after installing this package and tensorflow-cpu==2.10.0 in a brand new environment, please let us know.

Hi,
Well, so, i've just tested with tensorflow-cpu 2.10 and the last directML pluging and this time the .fit(...) has been reached and even started, but unfortunatly stopped by a Jupyter kernel crash (again...) , see below

Below last command lines executed before the crash:

Hope you'll find the reason of that crash.
Have a good day,
Best Regards
Guillaume


Context for meetings

Hi all,
We've built out a few sites that seem somewhat similar to the aims of this project

http://capsure.opencityapps.org/
https://chicago.councilmatic.org/events/

We have found that these have not been widely used.
We suspect that the main barrier to participation is not knowing when and where meetings occur, but an understanding of

what takes place in the meeting
why a person might go to the meeting
how to engage in the meeting (as either as speaker or just an observer)
does going to this meeting feel safe

A comprehensive source for the time and place of public meetings can be useful, but I'm wondering if you all are thinking of addressing any of the other barriers?

Yes, the platform is being created for use with our Documenters program,
which addresses all 3 of your points, i.e. Documenters assignments contain
info on what takes place at a meeting, Documenters assignments provide a
reason for being there and City Bureau trains Documenters to produce
various content at the meeting for public consumption:
http://www.citybureau.org/documenters
On Wed, Aug 2, 2017 at 3:05 PM, Forest Gregg<EMAIL_ADDRESS>wrote:

Hi all,
We've built out a few sites that seem somewhat similar to the aims of this
project

http://capsure.opencityapps.org/
https://chicago.councilmatic.org/events/

We have found that these have not been widely used.
We suspect that the main barrier to participation is not knowing when and
where meetings occur, but an understanding of

what takes place in the meeting
why a person might go to the meeting
how to engage in the meeting (as either as speaker or just an
observer)

A comprehensive source for the time and place of public meetings can be
useful, but I'm wondering if you all are thinking of addressing any of the
other barriers?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/City-Bureau/documenters-aggregator/issues/19, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AD1NKpRqopU5m3kqGyk7U7U46VDck_sdks5sUNaJgaJpZM4Orlo8
.

--
773-819-5188
Diaholliday.com http://diaholliday.com/
https://twitter.com/d_holli https://www.facebook.com/dIa.holliday
https://instagram.com/dia_holliday/

To echo what @diaholliday says, I don't think this needs to be used widely to be effective, since Documenters and ProPublica both get a direct benefit out of what we're building. There's almost certainly a broader audience for it, but broader in this case is still initially going to be a pretty small circle of people and organizations.
The primary use-case, which is to facilitate the Documenters program, means there's a way to learn and memorialize better context about what happens at these meetings.

Great! Thanks for the context!
On Sun, Aug 6, 2017 at 5:33 PM, David Eads<EMAIL_ADDRESS>wrote:

To echo what @diaholliday https://github.com/diaholliday says, I don't
think this needs to be used widely to be effective, since Documenters and
ProPublica both get a direct benefit out of what we're building. There's
almost certainly a broader audience for it, but broader in this case is
still initially going to be a pretty small circle of people and
organizations.
The primary use-case, which is to facilitate the Documenters program,
means there's a way to learn and memorialize better context about what
happens at these meetings.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/City-Bureau/documenters-aggregator/issues/19#issuecomment-320534259,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAgxbQAjDSFeshOnJQ7ez9_o4WoJhNq8ks5sVjEogaJpZM4Orlo8
.

--
773.888.2718

I think we can close this one 👯♂


Bugfix/missing params in swagger definition 3.1

merge 3.0.10 into 3.1.x and apply additional adjustments for https://github.com/gravitee-io/issues/issues/4394

Hi @Andy2003
Seems you have some conflicts here :)

@aelamrani you need to build https://github.com/gravitee-io/gravitee-repository/pull/177

@Andy2003 I mean, we cannot merge your pull request. Can you rebase your branch with the 3.1?

This is b/c of the merge of tag 3.0.10 into 3.1.x. when I rebase my branch you will double history

@Andy2003
First of all, 3.1.x is not under support anymore.
So I would suggest to start your changes from the 3.2.x branch and then ask for a pull request on the 3.2.x. That way, you will not have this commits in double...

@aelamrani and who is responsible for merging the 3.0.x / 3.1.x commits which are currently not part of the 3.2.x branch into 3.2.x? I want to do the final adjustments for 501ad077a77a1c0136ea7d212081ae1a002a0d25 in 3.2.x as pointed out in (https://github.com/gravitee-io/gravitee-management-rest-api/pull/1196#issuecomment-704250287 and https://github.com/gravitee-io/issues/issues/4394#issuecomment-714509514)

We will manage it don't worry.
We are merging everything (bugfixes / enhancements) until the master branch.

@aelamrani I thought I can support here with this PR, but as it seems I have to wait until I can apply my adjustments regarding gravitee-io/issues#4394


Mandate change

@remyb2canada I made the changes and pushed to the PR.
Please review and if OK with the change merge as is.
Thanks!