docker looks for certificates in a wrong place, and do not uses certificates on pull/push

I was trying to login to my private registry using self-signed user certificates, but always received error:
~$ docker login -u test -p test -e<EMAIL_ADDRESS>https://localhost:5000
Error response from daemon: invalid registry endpoint https://localhost:5000/v0/: unable to ping registry endpoint https://localhost:5000/v0/
v2 ping attempt failed with error: Get https://localhost:5000/v2/: dial tcp <IP_ADDRESS>:5000: connection refused
 v1 ping attempt failed with error: Get https://localhost:5000/v1/_ping: dial tcp <IP_ADDRESS>:5000: connection refused. If this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add `--insecure-registry localhost:5000` to the daemon's arguments. In the case of HTTPS, if you have access to the registry's CA certificate, no need for the flag; simply place the CA certificate at /etc/docker/certs.d/localhost:5000/ca.crt

in this time, docker daemon was trying to search certificates in /etc/docker/certs.d/https:/localhost:5000 directory, i think this wrong path, and in docs has no information about "http:" prefix in certificates path
DEBU[0071] hostDir: /etc/docker/certs.d/https:/localhost:5000
DEBU[0071] crt: /etc/docker/certs.d/https:/localhost:5000/ca.crt
DEBU[0071] cert: /etc/docker/certs.d/https:/localhost:5000/client.cert
DEBU[0071] key: /etc/docker/certs.d/https:/localhost:5000/client.key

This fix allows me to login correctly without setting https prefix in index name, and allow to pull/push images.
Signed-off-by: Vladimir Bulyga<EMAIL_ADDRESS>

ping @docker/distribution-maintainers plz review

re ping @dmcgowan @dmp42

Hi @13W
I'm not sure I understand.
There is no reason to specify https://
Just docker login localhost:5000.
Can you clarify what problem you face doing that?

I agree with @dmp42, looks like a bug with login that is being poorly handled.

Tentatively closing this.
@13W Feel free to clarify your problem, and maybe file an issue before submitting a PR so we can discuss the appropriate response! Thanks.


Add "take ownership" context menu

This is not working, and I don't have enough experience to troubleshoot, so I would like some help

Made use of reg command for it to work. I would appreciate if anyone could explain so I can avoid the same issue in the future

This should have been done with a Powershell command via Set-Property instead of invoke script using reg add, even then this is a bit of an obscure tweak that I'd prefer people to use Shell program to add it instead of a direct edit like this.


IT-3924: Setup sso admin group

Sets up the sso admin group for Synapse LLM dev account.
Depends on #1227 .

Closing this PR and replacing by same on prod account.


Module 1 exercises [SHEILA ABLA NYANYONU HUMPHREY-ACKUMEY]

Please "drag & drop" exercise 1 file below.

WS2_M1E1_Submission .docx
2. Please UPDATE THE TITLE of this "Issue" in the title bar above with your name.

If you haven't done so, please go back to Module 1 and make sure to take
the post-training survey.

Thank you for your successful submission to the practice exercise! Please be sure to fill out the post-Module survey.


Having the flags always visible

Hi,
it would be great if, when browsing streams, to have flags always visible not only after a mouse hover.
Much easier on the mouse travel.
Thanks

Hi...
Well, I don't think this is a great idea. This would cause too much distraction in a stream list. There is a reason why the flags are hidden without hovering the element. It's the same with the game being played. Showing too much at the same time renders a single information pretty much useless.

If you're looking for a stream in a specific language, then I would agree that it's not ideal, since you'd have to hover all the streams. But what's actually missing in this situation is a language search feature (the twitch API doesn't provide this functionality, though) or a filtering system.

It feels like a matter of preferences then. I don't feel it is cluttered at all but extremely useful for me.
I'm OK with hidden game being played as I usually browse by game rather than just random streams.
It would be nice to have as a toggle non-default option.though.
Thanks


Tests failing after removal of package root

The following tests are failing, and need to be fixed, after the removal of the package root directory, and its replacement with /.packages:
dart2js/library_resolution_test and dart2js/analyze_test_test running on -r vm -c none ( dart2js unit tests in tests/compiler/dart2js)
none-vm-checked debug_simmips co19/LibTest/isolate/Isolate/spawnUri_A01_t07
FAILED: none-vm release_simmips co19/LibTest/isolate/Isolate/spawnUri_A01_t07
FAILED: none-vm-checked debug_simarm co19/LibTest/isolate/Isolate/spawnUri_A01_t07
FAILED: none-vm-checked debug_simarm co19/LibTest/isolate/Isolate/spawnUri_A01_t07
FAILED: none-vm-checked debug_simarm co19/LibTest/isolate/Isolate/spawnUri_A01_t06
FAILED: none-vm debug_simarm co19/LibTest/isolate/Isolate/spawnUri_A01_t07
FAILED: none-vm debug_simarm co19/LibTest/isolate/Isolate/spawnUri_A01_t07
FAILED: none-vm-checked release_simarm co19/LibTest/isolate/Isolate/spawnUri_A01_t07

The dart2js tests have already been fixed, before the issue was filed.


Verbose debug mode

It would be useful to have a better logging mechanism in PDI that supports verbose logging

closed

@ksiero this is now supported with the introduction of spdlog, am I wrong?


Change repo ACL

Repo to change access:

https://github.com/hyperledger/aries-endorser-service

GitHub ID to add:

[x] Gavinok
[x] esune

One of:

https://github.com/orgs/hyperledger/teams/aries-endorser-service-committers
Role:

Manage / Maintain

Done! I will point out since neither of these people were outside the org, you could have done this directly.

I know, I just did not want to overstep.  If it's not an issue, I'll process similar requests directly.


Phalcon 3 & 4 support

Hello, just see the composer.json it implicit to phalcon 5 and php 8, can we support phalcon 3 & 4 also php >=7?

Unfortunately no. Due legacy code of Zephir and a lot of its changes it is near impossible to build it nowadays. Also there were a lot of memory leak fixes in Phalcon v5 which is much more stable with Swoole. Here is the blog post about my journey of memory management - https://blog.phalcon.io/post/high-load-micro-service
If you need any help you migrate your apps into latest PHP and Phalcon versions, feel free to join our discord server and ask for any help.


Release 1.10.0: Staging camel-k-runtime 1.14.0 and kamelet-catalog 0.9.0 tag

Related to #3560

Rebased


Handling cover art *.jpg

Heya guys,
Not a bug or anything but I'm occasionally getting multiple cover art files.
I'm thinking it's when I previously had the incorrect musicbrainz ID for the album, thus the existing cover.jpg isn't valid.
an example: http://pastebin.com/mz13gBZ9
I'm cover.2.jpg is the correct art for the release of that album I have.
I'm kind of anal here and would much rather have any existing cover*.jpg files deleted if it's going to get new art.
I already have *.jpg configured under clutter:, perhaps incorrectly thinking it would remove any jpgs when it checked for new artwork.
I suspect I'm just not groking something in the beets decision tree
fyi: fetchart is enabled and runs with these settings:
fetchart:                                   # get album art
    auto:               yes                 # default: yes
    cautious:           yes                 # require cover_names
    cover_names:        cover folder front picard  # be paranoid
    sources:            coverart itunes *   # prefer coverart itunes
    maxwidth:           2500                # max of 2500px wide please
    remote_priority:    no                  # prefer local

Hello, and thanks for reporting! Can you please try to reproduce this from the beginning so we can see exactly what might be going on? For example, steps to reproduce might look like:

Import this album (attached as zip file) with this config (also attached)
Run fetchart
Type ls /path/to/album to see the two files

Without knowing what you did to lead up to this situation, it's difficult to tell how things got into a bad state.

I already have *.jpg configured under clutter:, perhaps incorrectly thinking it would remove any jpgs when it checked for new artwork.

Yes, clutter is unrelated.

This happens to me when I import an album multiple times.
Steps to reproduce:

Import an album
Make sure it has a cover file
Import the album again
There should now be a cover.N.jpg file (N increments each time you re-import the album)

Here's my fetchart config:
fetchart:
  cautious: true
  remote_priority: true

That's exactly what I've experienced.  Thanks @djl

I think I've tracked this down to a bug in Album.set_art(). Rather than deleting the old file (as the docstring implies) a new file with a unique suffix is created instead.
Looking at this, it seems like a simple fix but now I'm not sure if this was done intentionally (possibly to prevent accidental data loss?) and the docstring is just incorrect.
In any case, pull request coming shortly. We can discuss it there :)

Hi there, @djl—thanks for doing some investigation. The story is much clearer now: re-importing albums with fetchart enabled creates double album art files. It's related to #314.
That does seem like a problem in set_art, but I actually don't think that's the only cause here. When re-importing, we currently don't do anything smart at all about album art. The normal workflow would pick up the file that already exists, but you have remote_priority enabled so it downloads another image. Re-importing creates a new Album in the database and replaces the old one.
A full solution here, and probably to #314, would need to bring over the old Album's art to the new one, and then make sure it gets deleted if it's replaced. Does that make sense?
Also, if you do tackle this, can I ask you the favor of creating a separate delete_art helper method? That will be helpful for, e.g., #733.

but you have remote_priority enabled so it downloads another image

I'm a little confused now.
If remote_priority is the trigger for this bug, how did @k-f- end up with multiple cover files? I tested fetchart without remote_priority and it didn't create any duplicate files.
What am I misunderstanding?

Good question—I don't exactly know how @k-f- ended up with this behavior. If you can cook up reproduction steps with your config, @k-f-, do let us know.

Hey guys,
Sorry been fighting a failing raid array all day, and haven't had a chance to get back to you.  :neckbeard:
I do indeed have `remote_prority:   no' set.
I've been meaning to make a config I can use for dev/testing without nuking my personal stuff, so I'll do that and see if I can't replicate this for you.


Minor Tweaks: Expand to bracket or quote // joining lines removes list markers

two minor additions, basically closing #7 and #21 (coincidentally created by me 😝 ).
However, I did have trouble building the plugin on my end. After building, no command works – even the ones I did not modify. However, the changes are pretty straightforward, and yarn.test passed all tests, so I assume that everything should be fine? 😅
For reference what happened on my end: ⬇

When running a command, I get the following error in the console, probably referring to .cm.operation here, but I have no idea what's missing here. In my main vault, where I use the last public release of Code Editor Shortcuts, all commands work fine though. :confused:
app.js:1 TypeError: cm.operation is not a function
    at withMultipleSelections (eval at <anonymous> (app.js:1:1444405), <anonymous>:111:8)
    at Object.editorCallback (eval at <anonymous> (app.js:1:1444405), <anonymous>:619:35)
    at Object.e.mobileOnly.kb.isMobile.e.checkCallback (app.js:1:1566335)
    at rz (app.js:1:1565804)
    at e.executeCommandById (app.js:1:1567080)
    at e.onTrigger (app.js:1:1098107)
    at e.handleKey (app.js:1:864568)
    at t.e.handleKey (app.js:1:864681)
    at t.handleKey (app.js:1:864890)
    at e.onKeyEvent (app.js:1:865683)

I assume I did something wrong while building? For reference, since I have no prior experience with nvm and/or yarn, this is the code I ran, where I never got an error during one of these.
# install yarn + nvm
brew install yarn
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.1/install.sh | bash

# build
nvm use # prompts to install the missing version
nvm install 12.22.4
nvm use
yarn install
yarn start
# Cancel with ^C
yarn test # all test passed

# git
git add -A
git commit -m "..."
git push # to my fork

Nice one! Would you mind adding some unit tests as well please? 🙏
As for the build error – not too sure what's going on, it works fine on my end and the commands you listed appear to be correct. Are you on the latest Obsidian version? What happens when you console.log(cm)?

Nice one! Would you mind adding some unit tests as well please? 🙏

Ugh, tbh, I have never done something like tests before, and wouldn't really know where/how to that 😨 🙈 So I guess it'd be easier if you added it, and I can look what you committed to understand what needs to be added for a test? That way I might at least be able to do it myself next time 😅

As for the build error – not too sure what's going on, it works fine on my end and the commands you listed appear to be correct. Are you on the latest Obsidian version? What happens when you console.log(cm)?

I am on macOS 12.2.1, Obsidian 0.14.2. And the latest release works fine in my regular vault, where I am obviously use the same version. 🤔
Where should I run the console.log(cm)? In the console itself?
console.log(cm)
VM165:1 Uncaught ReferenceError: cm is not defined
    at <anonymous>:1:13

I guess it'd be easier if you added it, and I can look what you committed to understand what needs to be added for a test?

Sure, check out ead9d91 and 3c7cccc 🙂
While writing them for expandSelectionToQuotesOrBrackets however, I noticed that this command doesn't work as expected for certain multi-cursor scenarios such as:
"(aaa| bbb) c|cc"
("aaa| bbb" c|cc)

(Cursor positions denoted by |)
Could you see if there's a way to rework the logic so its behaviour is more predictable?

Sure, check out https://github.com/timhor/obsidian-editor-shortcuts/commit/ead9d913d3d62a629f24a46204e98f1d72997549 and https://github.com/timhor/obsidian-editor-shortcuts/commit/3c7cccc8dcfbce205e03a48e50fbd9feee53e70a 🙂

great, thanks! 👍

While writing them for expandSelectionToQuotesOrBrackets however, I noticed that this command doesn't work as expected for certain multi-cursor scenarios such as:

ugh, yeah, that sounds like a lot of edge cases one can in theory consider. Should also affect Expand to Brackets/Quotes, if you have brackets in brackets or something. Can look into it some time, but I don't think I got the time for now. 😕
Maybe disable multiple cursors for that one command for now to be able to release it?

And the latest release works fine in my regular vault, where I am obviously use the same version.

I'd expect this to be the case if your regular vault is pulling in the published, pre-built version. Sounds like something's going wrong in the build process somewhere for you so it's breaking in your test vault. If you want to investigate further, we can discuss it through Discord DM.

Where should I run the console.log(cm)? In the console itself?

In src/utils.ts right after
const { cm } = editor;

Then once you reload the app and use a command, it should log out the value in the console.

Maybe disable multiple cursors for that one command for now to be able to release it?

Yeah, that's what I'm thinking too. It's probably less common to nest brackets and quotes of the same type inside one another, so it's not as obvious with Expand to Brackets/Quotes.


Added department GUI

Pull Request Test Coverage Report for Build 93

2 of 2 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.009%) to 79.79%

Totals

Change from base Build 92:
0.009%

Covered Lines:
1820

Relevant Lines:
2281

💛  - Coveralls


upgraded to pydantic v2.

library upgraded to pydantic v2. See https://docs.pydantic.dev/latest/blog/pydantic-v2-final/#pydantic-v2-is-here

Codecov Report

Merging #73 (f0e73c8) into dev (a6d40e6) will decrease coverage by 0.89%.
The diff coverage is 93.48%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##              dev      #73      +/-   ##
==========================================
- Coverage   93.11%   92.22%   -0.89%
==========================================
  Files          23       22       -1
  Lines        1089     1145      +56
==========================================
+ Hits         1014     1056      +42
- Misses         75       89      +14

Flag
Coverage Δ

unittests
92.22% <93.48%> (-0.89%)
:arrow_down:

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

Impacted Files
Coverage Δ

pydantic_xml/element/native/lxml.py
0.00% <ø> (ø)

...ydantic_xml/serializers/factories/typed_mapping.py
73.91% <73.91%> (ø)

pydantic_xml/element/element.py
98.80% <86.66%> (-0.59%)
:arrow_down:

pydantic_xml/serializers/factories/union.py
87.95% <87.17%> (+0.14%)
:arrow_up:

pydantic_xml/serializers/factories/mapping.py
88.75% <89.33%> (-1.88%)
:arrow_down:

...ydantic_xml/serializers/factories/heterogeneous.py
89.58% <90.90%> (-1.49%)
:arrow_down:

pydantic_xml/serializers/factories/homogeneous.py
92.00% <91.48%> (+0.62%)
:arrow_up:

pydantic_xml/serializers/factories/model.py
94.38% <94.73%> (-0.91%)
:arrow_down:

pydantic_xml/serializers/factories/primitive.py
95.55% <95.29%> (+1.52%)
:arrow_up:

pydantic_xml/serializers/factories/wrapper.py
95.12% <97.36%> (+2.43%)
:arrow_up:

... and 7 more


Refactor team controller update action

Notion card
Summary
port team_controller#update action code to a new service. This service updates the user name and role.
###file changes

team_controller.rb - remove fatty update action code and move it to a new service
team_policy.rb - remove email from permitted params [only first_name, last_name, and role can be updated from team page]
team/update_service.rb - Team::UpdateService the new service file to update the team member name and role.
added spec for service

Preview
Type of change
Please delete options that are not relevant.

[x] Refactor (non-breaking and retains the same functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to
not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Checklist:

[x] I have manually tested all workflows
[x] I have performed a self-review of my own code
[x] I have annotated changes in the PR that are relevant to the reviewer
[ ] I have added automated tests for my code

Merging the PR as CI test Suite passed

Rebased with develop as following cypress was failing frequently.


Readme Usage is not clear

The example usage on the Readme file is as follows:
`
import draftToHtml from 'draftjs-to-html';
const rawContentState = convertToRaw(editorState.getCurrentContent());
const markup = draftToHtml(contentState, directional, customEntityTransform);
`
Its not clear what the arguments contentState, directional, and customEntityTransform should be ? And how is the rawContentState supposed to be used to get the markup ?
Thank you,
Akhilesh

Thanks for feedback @heaplabs, I will improve it soon. For now you can refer this: https://github.com/jpuri/react-draft-wysiwyg/blob/master/docs/src/components/Demo/index.js#L66

@heaplabs: I have added more details to readme today. Plz share ur feedbacks. PR also welcome 😄

Additional to that: What is convertToRaw?

I add some more clarity to readme, hope it helps.


⚠ Bofrost.es has degraded performance

In b4bc419, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1740 ms

Resolved: Bofrost.es performance has improved in 4bc3dcd after 6 minutes.


ListView reorder item triggers ObservableCollection Remove and Add instead of Move

Describe the bug
It seems to be a history problem but it still confusing me that reorder item doesn't trigger ObservableCollection.Move method. I want to detect if some item is reordered, however I can not find any solution. Default ListView reordering behavior is remove item from the ObservableCollection and then add item to the ObservableCollection. Hence I can not determine whether item is reorder or add/remove. It's so weird. Is there any solution to detect reordering?
Steps to reproduce the bug

Place a ListView with a ObservableCollection ItemSource  and enable ListView reorder ability
Add event handler to the ObservableCollection's CollectionChanged
Reorder item in ListView and CollectionChanged was triggered twice. One is remove event and the other is add event.

Expected behavior
ObservableCollection's CollectionChanged should be triggered only once with NotifyCollectionChangedAction=Move
Screenshots
No response
NuGet package version
None
Windows version
No response
Additional context
No response

I can confirm this issue, that, IMHO, is a bug and not a feature request.
Which developer would think that a reordering gesture triggers a couple of add-remove notifications instead of a Move one?

I cannot agree it more


Gave option for trailing icon color to change and make it unclickable

Gave the option for devs to leave the trailing icon in the original tint or not and gave the option on whether the trailing icons should be clickable or not.

@omarsanchezv  Can you take a look at this? Thanks.


jQuery version issue for App-Inspect warnings

The app built with an Add-on builder has an issue/warning on the App-inspect for the jQuery version compatibility issue. (I'm posting here because I know UCC is what powers the Add-on builder.)

Reference - https://dev.splunk.com/enterprise/docs/developapps/visualizedata/updatejquery/
The issue is in common.js. I tried using the latest Add-on builder and has still the same warnings.
I think the issue could be specific to the Add-on builder and UCC has already resolved this issue. Let me know if this is the case. I can try using the latest version of UCC and see the common.js.

Hi @VatsalJagani, this is already accounted for in UCC>=5 and AOB v4. Can you please check with the latest version and let us know if you still face this warning?

@harshpatel-crest - Thanks for responding on this issue. I've replaced common.js shipped with AOB 4.0.0 and below are the warnings with that.

@VatsalJagani closing this issue because it seems to be resolved.


Loading indicator determinate

Summary of the bug
The circular determinate loading indicator's blue progress line isn't rounded like the others.
🧐 Expected behaviour
The edges should be rounded
📸 Screenshots or code
Looks like this currently:

Should match indeterminate, which looks like:

The loading indeterminate works with the rounded edges as we add a round border before and after. This is set to not display for determinate. If we remove that code, the determinate example looks like this:


The usage of "ptools" seems to break the "build" function of middleman on Windows

My ruby skill is not good enough so I came here to look for help.
I'm now using middleman-deploy (0.2.3) with middleman (3.3.2) & ptools (1.2.4-x86-mingw32).
When trying to build the console throws:
E:/usr/local/Ruby/lib/ruby/2.0.0/pathname.rb:47:in `[]': no implicit conversion from nil to integer (TypeError)
        from E:/usr/local/Ruby/lib/ruby/2.0.0/pathname.rb:47:in `chop_basename'
        from E:/usr/local/Ruby/lib/ruby/2.0.0/pathname.rb:102:in `cleanpath_aggressive'
        from E:/usr/local/Ruby/lib/ruby/2.0.0/pathname.rb:90:in `cleanpath'
        from E:/usr/local/Ruby/lib/ruby/2.0.0/pathname.rb:486:in `relative_path_from'
        from E:/usr/local/Ruby/lib/ruby/gems/2.0.0/gems/middleman-core-3.3.2/lib/middleman-core/cli/build.rb:193:in `execute!'
        from E:/usr/local/Ruby/lib/ruby/gems/2.0.0/gems/middleman-core-3.3.2/lib/middleman-core/cli/build.rb:128:in `invoke!'
        from E:/usr/local/Ruby/lib/ruby/gems/2.0.0/gems/thor-0.19.1/lib/thor/actions.rb:94:in `action'
        from E:/usr/local/Ruby/lib/ruby/gems/2.0.0/gems/middleman-core-3.3.2/lib/middleman-core/cli/build.rb:70:in `build'
        from E:/usr/local/Ruby/lib/ruby/gems/2.0.0/gems/thor-0.19.1/lib/thor/command.rb:27:in `run'
        from E:/usr/local/Ruby/lib/ruby/gems/2.0.0/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'
        from E:/usr/local/Ruby/lib/ruby/gems/2.0.0/gems/thor-0.19.1/lib/thor.rb:359:in `dispatch'
        from E:/usr/local/Ruby/lib/ruby/gems/2.0.0/gems/thor-0.19.1/lib/thor/base.rb:440:in `start'
        from E:/usr/local/Ruby/lib/ruby/gems/2.0.0/gems/middleman-core-3.3.2/lib/middleman-core/cli.rb:76:in `method_missing'
        from E:/usr/local/Ruby/lib/ruby/gems/2.0.0/gems/thor-0.19.1/lib/thor/command.rb:29:in `run'
        from E:/usr/local/Ruby/lib/ruby/gems/2.0.0/gems/thor-0.19.1/lib/thor/command.rb:126:in `run'
        from E:/usr/local/Ruby/lib/ruby/gems/2.0.0/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'
        from E:/usr/local/Ruby/lib/ruby/gems/2.0.0/gems/thor-0.19.1/lib/thor.rb:359:in `dispatch'
        from E:/usr/local/Ruby/lib/ruby/gems/2.0.0/gems/thor-0.19.1/lib/thor/base.rb:440:in `start'
        from E:/usr/local/Ruby/lib/ruby/gems/2.0.0/gems/middleman-core-3.3.2/lib/middleman-core/cli.rb:22:in `start'
        from E:/usr/local/Ruby/lib/ruby/gems/2.0.0/gems/middleman-core-3.3.2/bin/middleman:18:in `<top (required)>'
        from E:/usr/local/Ruby/bin/middleman:23:in `load'
        from E:/usr/local/Ruby/bin/middleman:23:in `<main>'

I traced to E:/usr/local/Ruby/lib/ruby/2.0.0/pathname.rb:43:
base = File.basename(path)

And at the final moment between crach, the result of File.basename became wired.
Before required ptools, File.basename 'E:/' returns "/" and everything was good.
After required ptools, File.basename 'E:/' returns "E:\\", then cause the cause the following codes crashed:
    if /\A#{SEPARATOR_PAT}?\z/o =~ base
      return nil
    else
      return path[0, path.rindex(base)], base
    end

I know nor whether this is a bug or a 'by design' for ptools, nor whether this is expected for middleman-deploy, nor whether there will be another solution to get it work.  Is there anybody can help?
Thanks

Is this still a problem since I've update pathname2?

@whitetrefoil Any luck?

@djberg96 oops... Sorry, I didn't see your previous message.  I haven't written ruby for years, and I can't remember details of this issue. I need some time to catch up.
I guess we can close this issue.  If there's still problem we can just reopen it.😄


🌅 Trim option for PDFs images

Ok, I have made this change a bit smaller based on feedback. The -trim call is now in the webp transform now as well, so they are consistent.
The image transforms certainly need some rework, but this is a worthwhile change to make for now!


Is it possible to add support to asm-lsp here?

Thank you for maintaining this extension, I came here after I opened https://github.com/zed-industries/zed/issues/19236, would be ok to add support for the LSP here?

Sorry to say, but I haven't really used Zed in months and don't have the drive to add this atm. If you want to submit a PR I would be happy to review it, though!


Killed

i am running the lm.extract('prompt', document) function and it seems to sometimes get hung up and then python will exit and return to bash terminal i have the single word message - Killed
I typed sudo dmesg and saw this message in my log:
[300974.215769] Out of memory: Killed process 336943 (python) total-vm:20061840kB, anon-rss:13408616kB, file-rss:128kB, shmem-rss:0kB, UID:1000 pgtables:27924kB oom_score_adj:0

I increased max_ram to 14gb and that seems to have solved it

I'm glad that you were able to get this resolved. It's possible to run out of memory during inference when using very long prompts, as memory requirements increase with prompt length. This currently results in your OS handling the out-of-memory condition as it normally would (often by killing the process hogging memory). I may explore adjusting this behavior in the future to either avoid this condition by limiting prompt length or by catching the OOM and providing a more helpful error message.

I was experienced another memory error while running a relatively short prompt and context.
[358590.438640] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-e01a3d63-8e8e-4ddf-81b6-ce6499a22afc.scope,task=python,pid=410852,uid=1000 [358590.438699] Out of memory: Killed process 410852 (python) total-vm:18305836kB, anon-rss:11485836kB, file-rss:128kB, shmem-rss:0kB, UID:1000 pgtables:24332kB oom_score_adj:0 [358591.189163] systemd[1]<EMAIL_ADDRESS>A process of this unit has been killed by the OOM killer. [358591.807792] systemd[1]: Started crash report submission. [358591.920102] systemd[1]: whoopsie.service: Deactivated successfully. [358592.046801] systemd[1]: Started crash report submission. [358592.047334] systemd[1]: systemd-journald.service: Main process exited, code=dumped, status=6/ABRT [358592.047442] systemd[1]: systemd-journald.service: Failed with result 'watchdog'. [358592.049111] systemd[1]: systemd-journald.service: Consumed 35.871s CPU time. [358592.049675] systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1. [358592.049785] systemd[1]: Stopped Journal Service. [358592.049809] systemd[1]: systemd-journald.service: Consumed 35.871s CPU time. [358592.053277] systemd[1]: Starting Journal Service... [358592.064364] systemd[1]: whoopsie.service: Deactivated successfully. [358592.097330] systemd-journald[422880]: File /var/log/journal/3bc42e77837046ff91ba2b6ab7df36b9/system.journal corrupted or uncleanly shut down, renaming and replacing. [358592.130826] systemd[1]: Started Journal Service. [358592.136700] systemd-journald[422880]: File /var/log/journal/3bc42e77837046ff91ba2b6ab7df36b9/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.


Add RTSP path via HTTP API add configuration can't working

Which version are you using?
v0.18.3
Which operating system are you using?

[x] Linux amd64 standard
[ ] Linux amd64 Docker
[x] Linux arm64 standard
[ ] Linux arm64 Docker
[ ] Linux arm7 standard
[ ] Linux arm7 Docker
[ ] Linux arm6 standard
[ ] Linux arm6 Docker
[ ] Windows amd64 standard
[ ] Windows amd64 Docker (WSL backend)
[ ] macOS amd64 standard
[ ] macOS amd64 Docker
[ ] Other (please describe)

Describe the issue
Hello,
I have an issue when i'm adding path config via HTTP API to server, when i'm post the config file for adding RTSP path to the server, The response from server is 200 and the server validate to created path, that seem OK but when listing path from server show the source path is "publisher" so i found the same problem at 0.17.8 version fixed at https://github.com/aler9/rtsp-simple-server/issues/664 https://github.com/aler9/rtsp-simple-server/issues/680, From this case i'm testing both linux amd64 and linux arm64 on this version.

If it's possible this version issue or the problem won't fixed completely at 0.17.8.

Describe how to replicate the issue

From the config yml, I config only one rtsp path from below.

paths:
  dinner:
        source<EMAIL_ADDRESS>        sourceOnDemand: no

Open rtsp server camera and the rtsp camera will adding on this process, I'm open with gstreamer. It's working correctly (but API edit configuration not tested).
After ensure the rtsp cameras can working, I adding another configuration file (the added file on below).

#fisheye.json
{
    "items": {
        "fisheye": {
            "confName": "1234",
            "conf": {
                "source"<EMAIL_ADDRESS>                "sourceProtocol": "automatic",
                "sourceAnyPortEnable": false,
                "sourceFingerprint": "",
                "sourceOnDemand": false,
                "sourceOnDemandStartTimeout": "10s",
                "sourceOnDemandCloseAfter": "10s",
                "sourceRedirect": "",
                "disablePublisherOverride": false,
                "fallback": "",
                "publishUser": "",
                "publishPass": "",
                "publishIPs": [],
                "readUser": "",
                "readPass": "",
                "readIPs": [],
                "runOnInit": "",
                "runOnInitRestart": false,
                "runOnDemand": "",
                "runOnDemandRestart": false,
                "runOnDemandStartTimeout": "10s",
                "runOnDemandCloseAfter": "10s",
                "runOnPublish": "",
                "runOnPublishRestart": false,
                "runOnRead": "",
                "runOnReadRestart": false
            },
            "source": {"type":"rtspSource"},
            "sourceReady": true,
            "readers": []
        }
    }
}

Checking active path on RTSP server. Found one from configure yml.

$ curl localhost:9997/v1/paths/list

The result from curl check paths list.
{
"items":{
	"dinner":{
	"confName":"dinner",
	"conf":{
<EMAIL_ADDRESS>	"sourceProtocol":"automatic",
	"sourceAnyPortEnable":false,
	"sourceFingerprint":"",
	"sourceOnDemand":false,
	"sourceOnDemandStartTimeout":"10s",
	"sourceOnDemandCloseAfter":"10s",
	"sourceRedirect":"",
	"disablePublisherOverride":false,
	"fallback":"",
	"publishUser":"",
	"publishPass":"",
	"publishIPs":[],
	"readUser":"",
	"readPass":"",
	"readIPs":[],
	"runOnInit":"",
	"runOnInitRestart":false,
	"runOnDemand":"",
	"runOnDemandRestart":false,
	"runOnDemandStartTimeout":"10s",
	"runOnDemandCloseAfter":"10s",
	"runOnReady":"",
	"runOnReadyRestart":false,
	"runOnRead":"",
	"runOnReadRestart":false
		},
	"source":{"type":"rtspSource"},
	"sourceReady":true,
	"readers":[]
	}
}

Post the configuration file to server via HTTP API. Server status working correctly and the file sent to the server working correctly.

curl -X POST -d @fisheye.json -H "application/json" localhost:9997/v1/config/paths/add/fisheye

But when i'm list from API again, the added path isn't config correctly from setting path.

$ curl localhost:9997/v1/paths/list

The result from curl check paths list
{
"items":{
	"dinner":{
	"confName":"dinner",
	"conf":{
<EMAIL_ADDRESS>	"sourceProtocol":"automatic",
	"sourceAnyPortEnable":false,
	"sourceFingerprint":"",
	"sourceOnDemand":false,
	"sourceOnDemandStartTimeout":"10s",
	"sourceOnDemandCloseAfter":"10s",
	"sourceRedirect":"",
	"disablePublisherOverride":false,
	"fallback":"",
	"publishUser":"",
	"publishPass":"",
	"publishIPs":[],
	"readUser":"",
	"readPass":"",
	"readIPs":[],
	"runOnInit":"",
	"runOnInitRestart":false,
	"runOnDemand":"",
	"runOnDemandRestart":false,
	"runOnDemandStartTimeout":"10s",
	"runOnDemandCloseAfter":"10s",
	"runOnReady":"",
	"runOnReadyRestart":false,
	"runOnRead":"",
	"runOnReadRestart":false
		},
	"source":{"type":"rtspSource"},
	"sourceReady":true,
	"readers":[]
	},
	"fisheye":{
	"confName":"fisheye",
	"conf":{
        "source":"publisher",
	"sourceProtocol":"automatic",
	"sourceAnyPortEnable":false,
	"sourceFingerprint":"",
	"sourceOnDemand":false,
	"sourceOnDemandStartTimeout":"10s",
	"sourceOnDemandCloseAfter":"10s",
	"sourceRedirect":"",
	"disablePublisherOverride":false,
	"fallback":"",
	"publishUser":"",
	"publishPass":"",
	"publishIPs":[],
	"readUser":"",
	"readPass":"",
	"readIPs":[],
	"runOnInit":"",
	"runOnInitRestart":false,
	"runOnDemand":"",
	"runOnDemandRestart":false,
	"runOnDemandStartTimeout":"10s",
	"runOnDemandCloseAfter":"10s",
	"runOnReady":"",
	"runOnReadyRestart":false,
	"runOnRead":"",
	"runOnReadRestart":false
		},
	"source":null,
	"sourceReady":false,
	"readers":[]
	}
    }
}

Thank you for your reply or suggestion, Can i ask about HTTP API edit configuration "How to edit the source configuration, Can i send only source path?"

Add and Edit with HTTP API can work normally, I'm using struct from another issue. If you want to add or edit some thing with HTTP API to the server only send source path like
  {"source"<EMAIL_ADDRESS>
It's can work normally.


Testing

We've classically had the problem of not being comparable to the GNU toolchain because there are multiple ways to emit valid assembly for a given instruction.  So how about testing like this:
Use stoke search to randomly pick an instruction
Generate a random initial state for the CPU
Use stoke's sandbox to run the instruction on the initial state
Use stoke's sandbox again, but use hex emitted by gas for the instruction
Diff the resulting CpuStates
This might help uncover remaining bugs in the assembler/sandbox.

Sounds good to me. I'd bubble the testing up into stoke though so we don't
get a circular dependency between the repositories.
On Mon, Feb 2, 2015 at 2:29 PM, Berkeley Churchill<EMAIL_ADDRESS>
wrote:

We've classically had the problem of not being comparable to the GNU
toolchain because there are multiple ways to emit valid assembly for a
given instruction. So how about testing like this:
Use stoke search to randomly pick an instruction
Generate a random initial state for the CPU
Use stoke's sandbox to run the instruction on the initial state
Use stoke's sandbox again, but use hex emitted by gas for the instruction
Diff the resulting CpuStates
This might help uncover remaining bugs in the assembler/sandbox.
—
Reply to this email directly or view it on GitHub
https://github.com/eschkufz/x64asm/issues/140.

Yeah, for sure.  There are some x64asm tests already in stoke which we
could add to.
On 02/02/2015 02:35 PM, eric schkufza wrote:

Sounds good to me. I'd bubble the testing up into stoke though so we don't
get a circular dependency between the repositories.
On Mon, Feb 2, 2015 at 2:29 PM, Berkeley Churchill<EMAIL_ADDRESS>
wrote:
We've classically had the problem of not being comparable to the GNU
toolchain because there are multiple ways to emit valid assembly for a
given instruction. So how about testing like this:
Use stoke search to randomly pick an instruction
Generate a random initial state for the CPU
Use stoke's sandbox to run the instruction on the initial state
Use stoke's sandbox again, but use hex emitted by gas for the instruction
Diff the resulting CpuStates
This might help uncover remaining bugs in the assembler/sandbox.
—
Reply to this email directly or view it on GitHub
https://github.com/eschkufz/x64asm/issues/140.

Reply to this email directly or view it on GitHub:
https://github.com/eschkufz/x64asm/issues/140#issuecomment-72553260

Sounds good to me.
On Mon, Feb 2, 2015 at 2:36 PM, Berkeley Churchill<EMAIL_ADDRESS>
wrote:

Yeah, for sure. There are some x64asm tests already in stoke which we
could add to.
On 02/02/2015 02:35 PM, eric schkufza wrote:

Sounds good to me. I'd bubble the testing up into stoke though so we
don't
get a circular dependency between the repositories.
On Mon, Feb 2, 2015 at 2:29 PM, Berkeley Churchill <
<EMAIL_ADDRESS>
wrote:
We've classically had the problem of not being comparable to the GNU
toolchain because there are multiple ways to emit valid assembly for a
given instruction. So how about testing like this:
Use stoke search to randomly pick an instruction
Generate a random initial state for the CPU
Use stoke's sandbox to run the instruction on the initial state
Use stoke's sandbox again, but use hex emitted by gas for the
instruction
Diff the resulting CpuStates
This might help uncover remaining bugs in the assembler/sandbox.
—
Reply to this email directly or view it on GitHub
https://github.com/eschkufz/x64asm/issues/140.

Reply to this email directly or view it on GitHub:
https://github.com/eschkufz/x64asm/issues/140#issuecomment-72553260

—
Reply to this email directly or view it on GitHub
https://github.com/eschkufz/x64asm/issues/140#issuecomment-72553476.

Since not all the instructions are implemented, it would be nice for users like me to have a fuzz test that checks only a given set of instructions. The make test interface takes quite a while. That will allow users like me more comfortable with implementing new instructions and contributing to stoke

The current 'make test' is also buggy and produces nearly all
false-positives.  It's not recommended at all.  The only thing that's
good about it, is that if it says something is correct, then it's
actually correct (because it matches gnu's assembler).
On 02/08/2015 12:58 AM, Rajib Nath wrote:

Since not all the instructions are implemented, it would be nice for users like me to have a fuzz test that checks only a given set of instructions. The make test interface takes quite a while. That will allow users like me more comfortable with implementing new instructions and contributing to stoke

Reply to this email directly or view it on GitHub:
https://github.com/eschkufz/x64asm/issues/140#issuecomment-73402695

@bchurchill
do you have any current known list of instructions which have wrong entries in the spread sheet?

Nope.  We usually fix these pretty quickly -- this psllw we've postponed
since it requires touching more code and we've been busy.  Any that we
know about go on the tracker.  The instructions that we have circuits
for are very unlikely to be wrong because they go through the fuzz tester.
On 02/09/2015 02:42 PM, Rajib Nath wrote:

@bchurchill
do you have any current known list of instructions which have wrong entries in the spread sheet?

Reply to this email directly or view it on GitHub:
https://github.com/eschkufz/x64asm/issues/140#issuecomment-73606802

This issue seems closed to me. Reopen if I'm wrong.

We have no testing infrastructure for x64asm that's not replete with false positives.

I thought the consensus was that this issue was being moved to stoke.
On Feb 10, 2015 5:42 PM, "Berkeley Churchill"<EMAIL_ADDRESS>wrote:

We have no testing infrastructure for x64asm that's not replete with false
positives.
—
Reply to this email directly or view it on GitHub
https://github.com/eschkufz/x64asm/issues/140#issuecomment-73821364.

Well, the problem is in x64asm and the implementation will be in stoke
(if I implement it as described).  I just don't want to loose track of
it but don't care where the ticket is.  You can move it if you like.
On 02/10/2015 05:44 PM, eric schkufza wrote:

I thought the consensus was that this issue was being moved to stoke.
On Feb 10, 2015 5:42 PM, "Berkeley Churchill"<EMAIL_ADDRESS>wrote:

We have no testing infrastructure for x64asm that's not replete with false
positives.
—
Reply to this email directly or view it on GitHub
https://github.com/eschkufz/x64asm/issues/140#issuecomment-73821364.

Reply to this email directly or view it on GitHub:
https://github.com/eschkufz/x64asm/issues/140#issuecomment-73821484

Whatev. Here is fine.
On Tue, Feb 10, 2015 at 5:54 PM, Berkeley Churchill <
<EMAIL_ADDRESS>wrote:

Well, the problem is in x64asm and the implementation will be in stoke
(if I implement it as described). I just don't want to loose track of
it but don't care where the ticket is. You can move it if you like.
On 02/10/2015 05:44 PM, eric schkufza wrote:

I thought the consensus was that this issue was being moved to stoke.
On Feb 10, 2015 5:42 PM, "Berkeley Churchill"<EMAIL_ADDRESS>wrote:

We have no testing infrastructure for x64asm that's not replete with
false
positives.
—
Reply to this email directly or view it on GitHub
https://github.com/eschkufz/x64asm/issues/140#issuecomment-73821364.

Reply to this email directly or view it on GitHub:
https://github.com/eschkufz/x64asm/issues/140#issuecomment-73821484

—
Reply to this email directly or view it on GitHub
https://github.com/eschkufz/x64asm/issues/140#issuecomment-73822445.


Text edit not working on tablets/ipad

Hi I'm facing some issue related to edit text on tablets and iPad. I have installed this package which enable the touch support on grapesjs. Everything is working except text editing. I can select the text but keyboard not showing up. I try to check the Dom element during this testing. The Dom parameter "contenteditable" is not there.

Did you close this because you got it to work? While using a mobile device I cannot get the keyboard to display when trying to edit a text field. Even using the grapes touch plugin does not help. There is an example here:
http://jsfiddle.net/v9kecdpz/

No. After no response from anyone on this issue. I just used the workaround. Which is not good, but there is no other solution. I'll share the code which I found somewhere on the internet.
const textType = editor.DomComponents.getType('text'); editor.DomComponents.addType('text', {   model: textType.model,   view: textType.view.extend({     events: {       dblclick: function () {         this.onActive();       },       touchend: function () {         this.onActive();       }     }   }) });

Thank you for taking time to help. I will give that a shot.


All accelerate commands and imports fail in Singularity conversion of Docker container

System Info
- `Accelerate` version: 0.19.0
- Platform: Linux-3.10.0-1160.80.1.el7.x86_64-x86_64-with-glibc2.17
- Python version: 3.11.3
- Numpy version: 1.24.3
- PyTorch version (GPU?): 2.0.1 (True)
- System RAM: 187.36 GB
- GPU type: Tesla V100S-PCIE-32GB
- `Accelerate` default config:
        Not found

Information

[X] The official example scripts
[ ] My own modified scripts

Tasks

[ ] One of the scripts in the examples/ folder of Accelerate or an officially supported no_trainer script in the examples folder of the transformers repo (such as run_no_trainer_glue.py)
[ ] My own task or dataset (give details below)

Reproduction
I'm working on an HPC, so I can only use Singularity. To reproduce:
singularity pull docker://huggingface/accelerate-gpu
singularity shell accelerate-gpu.sif
conda init
source ~/.bashrc
conda activate accelerate

Then, when running any of the following snippets:
accelerate env

(The output of accelerate env that I pasted above is from outside of my Singularity container)
accelerate test

python3
>>> from transformers import pipeline

I get the same final error; the tracebacks are of course different, but they all end the same way:
Setting ds_accelerator to cuda (auto detect)
Traceback (most recent call last):
  File "/opt/conda/envs/accelerate/bin/accelerate", line 5, in <module>
    from accelerate.commands.accelerate_cli import main
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/accelerate/__init__.py", line 3, in <module>
    from .accelerator import Accelerator
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/accelerate/accelerator.py", line 33, in <module>
    from .checkpointing import load_accelerator_state, load_custom_state, save_accelerator_state, save_custom_state
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/accelerate/checkpointing.py", line 24, in <module>
    from .utils import (
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/accelerate/utils/__init__.py", line 119, in <module>
    from .megatron_lm import (
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/accelerate/utils/megatron_lm.py", line 32, in <module>
    from transformers.modeling_outputs import (
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/transformers/__init__.py", line 23, in <module>
    from .configuration_albert import ALBERT_PRETRAINED_CONFIG_ARCHIVE_MAP, AlbertConfig
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/transformers/configuration_albert.py", line 18, in <module>
    from .configuration_utils import PretrainedConfig
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/transformers/configuration_utils.py", line 25, in <module>
    from .file_utils import CONFIG_NAME, cached_path, hf_bucket_url, is_remote_url
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/transformers/file_utils.py", line 23, in <module>
    import requests
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/requests/__init__.py", line 44, in <module>
    import chardet
ModuleNotFoundError: No module named 'chardet'

Setting ds_accelerator to cuda (auto detect)
Traceback (most recent call last):
  File "/opt/conda/envs/accelerate/bin/accelerate", line 5, in <module>
    from accelerate.commands.accelerate_cli import main
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/accelerate/__init__.py", line 3, in <module>
    from .accelerator import Accelerator
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/accelerate/accelerator.py", line 33, in <module>
    from .checkpointing import load_accelerator_state, load_custom_state, save_accelerator_state, save_custom_state
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/accelerate/checkpointing.py", line 24, in <module>
    from .utils import (
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/accelerate/utils/__init__.py", line 119, in <module>
    from .megatron_lm import (
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/accelerate/utils/megatron_lm.py", line 32, in <module>
    from transformers.modeling_outputs import (
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/transformers/__init__.py", line 23, in <module>
    from .configuration_albert import ALBERT_PRETRAINED_CONFIG_ARCHIVE_MAP, AlbertConfig
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/transformers/configuration_albert.py", line 18, in <module>
    from .configuration_utils import PretrainedConfig
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/transformers/configuration_utils.py", line 25, in <module>
    from .file_utils import CONFIG_NAME, cached_path, hf_bucket_url, is_remote_url
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/transformers/file_utils.py", line 23, in <module>
    import requests
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/requests/__init__.py", line 44, in <module>
    import chardet
ModuleNotFoundError: No module named 'chardet'

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/transformers/__init__.py", line 23, in <module>
    from .configuration_albert import ALBERT_PRETRAINED_CONFIG_ARCHIVE_MAP, AlbertConfig
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/transformers/configuration_albert.py", line 18, in <module>
    from .configuration_utils import PretrainedConfig
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/transformers/configuration_utils.py", line 25, in <module>
    from .file_utils import CONFIG_NAME, cached_path, hf_bucket_url, is_remote_url
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/transformers/file_utils.py", line 23, in <module>
    import requests
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/requests/__init__.py", line 44, in <module>
    import chardet
ModuleNotFoundError: No module named 'chardet'

Installing chardet by conda install chardet fails because I don't have permission to write to the target environment:
Preparing transaction: done
Verifying transaction: failed

EnvironmentNotWritableError: The current user does not have write permissions to the target environment.
  environment location: /opt/conda/envs/accelerate
  uid: 1036009
  gid: 2022

Expected behavior
For chardet to be correctly installed upon container instantiation.

I think this is the same failure we're getting on our nightlies suddenly. Can you try via the 0.19.0 image? https://hub.docker.com/layers/huggingface/accelerate-gpu/0.19.0/images/sha256-32cdb06bc3e5c4fc64412b9cdac123dfc7870e4f00ede7bd89cc4419ac745070?context=explore

@muellerzr got the same chardet error when I ran accelerate env in the 0.19.0 image

@muellerzr just wanted to follow up on this!

Hi @serenalotreck, this looks like a transformers issue in the traceback, more than an accelerate issue, as I'm not sure what the cause would stem from this outside perhaps an outdated requests version? The sign of this is here in the traceback:
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/transformers/configuration_utils.py", line 25, in <module>
    from .file_utils import CONFIG_NAME, cached_path, hf_bucket_url, is_remote_url
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/transformers/file_utils.py", line 23, in <module>
    import requests
  File "/mnt/home/lotrecks/.local/lib/python3.8/site-packages/requests/__init__.py", line 44, in <module>
    import chardet
ModuleNotFoundError: No module named 'chardet'

Notice how its transformers t the end when the dependencies get used


Basic network request inspection

Original issue: https://github.com/node-inspector/node-inspector/issues/341
Based on bugger's network probe. The rest is basically one big copy&paste job of ConsoleAgent.
I kept this PR as small as possible because messing with the http module is prone to break people's code in edge cases. Tests against real-life code more than welcome.

@jkrems , great job!
After fast review I have one idea:
var request = require('http').request;

If this code was called before wrapping, we can't handle this requests, because user already has closure on original request func.
It may be reasonable to wrap something more private. Maybe http.ClientRequest

Well, request has a closure over ClientRequest. So if a user already has a closure over request, they also have one over ClientRequest (at least indirectly). It might be possible to change the code of request itself at runtime, but that would make me a bit nervous. ;)

Well, request has a closure over ClientRequest.

Ok, you are right here, but I don't stop to search an other place =)
So, I found _deferToConnect, it exists on all versions. (We shouldn't worry about compatibility with future versions here, only check that this function exists. I know what http module can be completely rewritten in nearest time.)
There are all that we need for data construction (correct me if I'm wrong), but making stack trace will be more difficult. In this case we need to wrap only one place:
function wrapHttpRequests() {
  var proto = require('http').ClientRequest.prototype;
  proto._deferToConnect = (function(fn) {
     var lastRequestId = 0;
     // ...
     return function handleHttpRequest() {
       debug.command('Network.requestWillBeSent', constructRequestData(this));
       this.once('response', handleHttpResponse);
       fn.apply(this, arguments);
     }
  } (proto._deferToConnect));
}

How about this?

Hehe, nice find. I didn't look too deeply into it but it doesn't look like options is stored anywhere on the instance of ClientRequest. So if we'd want to correctly reconstruct the original URL (and that's only one of the pieces of data) we'd need:

Find out the hostname. The client request doesn't store it. Host header is unreliable because it doesn't have to match the actual host (e.g. host-spoofing)
Find out the remote port. From reading the constructor I don't even know where to start to get that one, especially given that we'd only want to send requestWillBeSent if a dns lookup fails etc.. Failing requests are as or maybe even more interesting.

That last part also brings up the question - is there a guarantee that _deferToConnect is called? What if socket pooling is used and a hard timeout on the request to abort it if a socket can't be acquired after a few millis?
Sorry if I sound defensive here. I totally get that you'd love to get a more reliable/flexible http instrumentation working. It's just that the code in this PR (or at least variations of it) is something that I'm fairly confident works and is reliable to the point where I know of apps using it in production for outgoing http request logging. I could try to dig deeper into http core and research if there's an alternative that also handles the case where someone already has a reference to request. But unfortunately I won't get to around to that anytime soon. :( That being said - I'm happy to test and give feedback on other solutions!

I am excited to see this finally coming. This is great! So I tested the against one of our project, very glad to see the network requests showing up in the network tab!
I also noticed some potential bugs

network frontend stop working if header value is not a string (eg. content-length). network manager is calleing a split on header value here
when I restart node-inspector, the network request is doubled.
the options in the hijacking request seems not quite matching the one in http request api, which leads to hostname showing as the request url.

Hope this helps!

@GingerBear Thanks for giving it a spin! Will look into those issues!

Quick update: Pushed an update that adds the missing string cast for the headers. Also included a change to explicitly remove the instrumentation on disconnect, hoping that will fix the doubling issue. Unfortunately I wasn't able to reproduce it myself.
@GingerBear Do you have an example for the options object where the url is messed up? I'm assuming it's caused by the host/hostname weirdness in url.format. But I can't recall exactly how to trigger it.

@jkrems sure, here is an example. May not be the best one, but you can see only www.google.com show in the network tab when you go to http://localhost:4000/intl/en/about/ . Btw, it seems to be fine using request to send request.
I am still seeing the double logs. For the same example, refresh the inspector couple times and load the web page again, I was able to see the doubling in the network tab.
var http = require('http');

var server = http.createServer(function(req, res) {
  var request = http.request({
      host: 'www.google.com',
      method: 'GET',
      path: req.url
  }, function (response) {
      var body;
      response.on('data', function (data) {
          body += data;
      });
      response.on('end', function (data) {
          res.end(body);
      });
  });
  request.end();
});

server.listen(4000, function(){
    console.log("Server listening on: http://localhost:%s", 4000);
});

I am still seeing the double logs.

@jkrems , don't worry about this. This is out of scope of your pr.
Your .on('close') handling is reasonable.

@GingerBear Thanks! The code wasn't handling that protocol is optional. Pushed an update that should fix this.
Sorry for the slow reaction time. Busy week.

Closing in favor of #677


editing tags is broken — throws exception in console

Renderer
Both
Browser
Chrome
Operating System
MacOS
What happened?
Attempting to commit a change to a tag in the metadata panel has no effect, and throws an error in console.

bundle.js:76373 Uncaught TypeError: e.persist is not a function
    at ReactClassComponent.handleFieldChange (bundle.js:76373:7)
    at Object.onChange (bundle.js:76611:23)
    at ReactClassComponent.handleChange (bundle.js:76945:16)
    at ReactClassComponent.addValue (bundle.js:76952:10)
    at onClick (bundle.js:77095:16)
    at Object.ba (bundle.js:30337:84)
    at ja (bundle.js:30337:238)
    at ka (bundle.js:30337:292)
    at oa (bundle.js:30338:72)
    at lc (bundle.js:30375:170)

Source offender is here:
https://github.com/naturalcrit/homebrewery/blob/3e44d0ad130d936a5b90c1ab5d4e1a6dcb770a1d/client/homebrew/editor/metadataEditor/metadataEditor.jsx#L55-L57
event.persist() is a react thing, so I have no suggestions on what to do here. This might even not be the true source cause .. it might be some other change that caused the e.persist() to no longer be valid in this context. All I know it has something to do with synthetic (react) events in async functions. Good luck.
Code
No response

So we are using React 16.14.0  (correct me if i'm wrong).  From Reacts docs:

As of v17, e.persist() doesn’t do anything because the SyntheticEvent is no longer pooled.

Do we ever expect to move to React v17?  If so, it's probably not worth the time to make e.persist() work for tags, and we should just work around it entirely.  In fact, I think moving to v17 would just remove the necessity for it entirely and fix this issue.  My understanding (which doesn't mean much) is that React <16 doesn't really hold onto SyntheticEvents into nested functions.   Using persist() enables using the event in these deeper functions.   When doing the Field Validation PR, I felt that I needed it for this to work (from metadataEditor.jsx):
if(validationErr.length === 0){
	e.target.setCustomValidity('');   // without e.persist() this does not work, because 'e' is no longer linked to the original event
	this.props.onChange({
		...this.props.metadata,
		[name] : e.target.value
	});

The issue with the tags is happening because e isn't an event, so e.persist() isn't a function.  I'm not sure why e isn't an event, but I'm assuming it's because the <input> is inside an external component?
This might all be a bunch of nonsense, but regardless I'm not likely to figure it out quickly though I will try.  But if there was any chance we'd move to React v17, then maybe it's not worth the bother.  Alternatively, adapting my Combobox for the tags entry might be an easy fix, but that might be even messier.

We can update React at any time as long as we make any accompanying changes so we don't break stuff. I'm assuming most react versions are more or less backwards compatible.

Will do.  For my notes, here is the React post about React 17.  https://reactjs.org/blog/2020/10/20/react-v17.html
It starts off with a hopeful tone:

The React 17 release is unusual because it doesn’t add any new developer-facing features. Instead, this release is primarily focused on making it easier to upgrade React itself.
...
We’ve postponed other changes until after React 17. The goal of this release is to enable gradual upgrades. If upgrading to React 17 were too difficult, it would defeat its purpose.

I updated to React 17 and don't seem to have any issues....I haven't tried to implement any changes to fix this issue, though it wasn't solved by just the upgrade.  But i can navigate around the site fine and haven't had any issues yet.

Ok. Do you want to go ahead and make a PR to update react and we can move forward assuming we will have at least react 17?

Honestly it's probably a good idea to have someone else give it a shot, to be sure I didn't miss something when it was installing?  There were 'warn' messages as I installed it, which I mostly took to be "not important" and powered through.  So...

Ok I'll do that one and see how it goes.

@Gazook89 I updated react to v17. I had to do a little finagling in the background on a couple other things but it seems to be working now...

Fixed by #2547


{Packaging} Fix #23559: Disable build_id links

Fix #23559. This PR disables the generation of build_id links to prevent conflicting with azure-security package in RHEL 8.5 on Azure.

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

Packaging


node/ai-knowledge-assistant does not deploy properly

There is an error when trying to deploy node/ai-knowledge-assistant app:
Build failed with status: FAILURE and message: function.js does not exist.

Logs:
Step #2 - "build": failed to build: (error ID: 7485c5b6):
Step #2 - "build": function.js does not exist

Yeah, I ran into the same issue.
Can't get around it.

Thank you for trying our sample! I believe the issue may be that you are deploying the function to Google Cloud with a zip file, but you added the folder ai-knowledge-assistant to the zip file.
For the deployment to work, you must zip the contents of the folder (i.e., the files within the folder), not the folder itself. If you open the zip file, you should see package.json, index.js, and other files and subfolders in the root, not the folder ai-knowledge-assistant.
Please let us know if that resolves the issue.

Same issue which that did no resolve. There is no function.js file in the repo, nor mention of the functions in the https://developers.google.com/workspace/chat/tutorial-ai-knowledge-assistant.
no steps in the quickstart to create the functions.


[utils] remove stdint and stdbool wrappers

This PR removes the wrap_stdint.h and wrap_stdbool.h because OpenThread
enforces C99, which includes these headers in its standard library.

For background, these wrappers were introduced to address issues with Visual Studio (see #1476). Given that we have removed Windows support, I am fine with this PR unless someone else objects.


Prompt to accept incoming connections on Mac OS when running now dev

When activating the firewall on MacOS, I start getting these prompts each time running now dev (sorry for the french):

I would expect to accept it only once the first time I run now dev, or not at all because I'm not trying to access "internet" or expose a server to the outside world with now dev.
One possible root cause for this is that the now dev server is listening on <IP_ADDRESS> instead of localhost. Listening on localhost wouldn't prompt this message.
Also worth noting that I'm not getting these prompts when running other servers in dev mode (for example, yarn run next).

Re-opened so we can ship it after zero config: https://github.com/zeit/now-cli/pull/2720

To avoid the firewall prompt, you can now do now dev --listen <IP_ADDRESS>


rdmsr: Don't panic on user GPF.

I believe this fixes what David observed.
Signed-off-by: Dan Cross<EMAIL_ADDRESS>

Some testing would be nice.... :-D


style: activiy icon size is weird

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.84.1
OS Version: macOS Sonoma(14.0)

Steps to Reproduce:

change the color theme to high contrast theme
you will see the activity bar icon size and the border is weird

pinging @sandy081


Adds a Listview tile select example

This PR fixes https://github.com/flutter/flutter/issues/12882 and adds a listview tile example which shows a  List of ListTile

long press and select a listTile
switch between grid view and listView (while persisting state)
select all ListTiles of list
unselect all ListTiles of list

Pre-launch Checklist

[X] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[X] I read the Tree Hygiene wiki page, which explains my responsibilities.
[X] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[X] I signed the CLA.
[X] I listed at least one issue that this PR fixes in the description above.
[X] I updated/added relevant documentation (doc comments with ///).
[X] I added new tests to check the change I am making, or this PR is test-exempt.
[X] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Thanks for the review @Piinks I have renamed the file and linked the example in the comments here.
https://github.com/flutter/flutter/blob/9cb60c982863ec32018c078bf4dbe5fcd92c4245/packages/flutter/lib/src/widgets/scroll_view.dart#L1007-L1012
I thought this was the right place Since this section already talks about selecting ListItems. Let me know if you think this should be included somewhere else.
Thanks


Added client version code to test app

Codecov Report

Merging #140 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #140   +/-   ##
=========================================
  Coverage     72.44%   72.44%
  Complexity      483      483
=========================================
  Files            65       65
  Lines          2664     2664
  Branches        247      247
=========================================
  Hits           1930     1930
  Misses          663      663
  Partials         71       71

Continue to review full report at Codecov.

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


Update 3.x branch

Bring fork up to date with the parent repo, which moves it from v3.5.8 to v3.7.0.

DatabaseManager.php remains unchanged by the recent commits, so all being well the Portal should behave nicely with these changes :crossed_fingers:

Once this is merged a PR on the Portal repo will be created to allow testing of the newly updated v3.x branch alongside the Portal's own features


Update crd.md

I have updated crd.md with more readable format and added missing options from flinkcluster_types.go

Thanks @moonsub-kim


Dot marker size can be varied using a delegate 'sizeOnDayView' -> flo…

Eugene,
Added a delegate to control the size of dot marker to have flexible size according to screen. Have tested it and works fine. Hope it helps!
Sandeep

Hello @sandeepmenon,
Thank you for your contribution!
Please, update the changes to the current master branch, so the merge can be completed. :)
Regards,
Eugene

i have updated the branch :D .. timing of creating a request was bit off

Thank you once more! :+1:

Please, could you document the changes?

i have updated only the CV calendar under the project and not on the top level. Should i update both?
Sure i will update the documentation

Yes, both CVCalendar(s) should be updated. :]
Thank you!


[5.1 08-28-2019] [Constraint solver] Cope with circular inheritance.

This loop in the constraint solver won't terminate when given
ill-formed code involving circular inheritance. Make it
terminate. Fixes rdar://problem/54296278.

@swift-ci please test


Make "ago" optional for time-ago

What do you think about making "ago" optional for time-ago? It's often useful to get a human-readable time span and combine it with custom suffix, e.g.: 2 days since the last meeting, 10 years of experience. moment.js supports similar feature via a boolean argument to fromNow(true) method.

How often does <time-ago> refreshes? Because I see just now and then randomly later 36 seconds ago

Hey all! The direction we're planning to take here is to lean on the new Intl.RelativeTimeFormat API for internationalization https://github.com/github/time-elements/pull/104. Thanks!


If I am optimizing more than one model, do I need to write "with accelerator.accumulate(model1) and accelerator.accumulate(model2)"?

Duplicate of https://github.com/huggingface/accelerate/issues/1414

@muellerzr Thank you


(No. 9 A) Show/Hide Barrier Filter Layer [ Need More Info, Med. Hard? ]

Anne does not want all layers to show on load. Ryan doesn't either, since they won't all load when full data is in place.

Decide UI for WHEN to turn on barriers
Decide logic for WHEN to turn on barriers
Decide UI for WHERE to turn on barriers

Note for Jocelyn: where in the workflow do you see barriers, and where not? Question for Anne, and Ryan should be part of that convo.
Probably after location selection.
Tied to performance tuning,


Updates app version to v0.4.0

/assign @wallrj

/hold
Until we are ready to release

/retest

/hold cancel
/retest

/test


[DebugInfo][SILGen] Ensure "guard let" is lowered with a non-implicit…

… location
Prior to this patch, a "guard let" was being lowered with an implicit debug location, causing it to be dropped in later stages of the compiler, and making it impossible to set a breakpoint in that line.
This was tracked down to a piece of code in SILGenFunction::emitExprInto, which takes an optional Location parameter that was being ignored in one code path.
(cherry picked from commit 8baf9331140b3a9ce94835ee7f899e3846e90659)
rdar://116462520

@please test

@swift-ci please test


Benchmarks on different distributions

At the moments, I only benchmark on a (diagonal) multivariate normal. This is not great for the Python comparison because logpdf allocates a lot to compute $\Sigma^{-1}$. A comparison on univariate normals or categoricals would be much more in our favor.

Solved by benchmarking with LightDiagNormal


Refine README + docs

This PR refines the README and docs a bit as we prepare for an announcement, as well as updating URLs.
Let me know if I've bungled any of this!

Thank you for those improvements @isabelizimm! 🙌


Update persistent-volumes.md

/assign @sftim

I signed it

The sentence is referring to Persistent Volume Claims, so "claims" is correct.

As @msau42 and @rajeshdeshpande02 have pointed out, this change seems to be inaccurate.
/close


md-tab not showing any text

Bug, feature request, or proposal: Bug
What is the expected behavior?
Texts appear in a tab
What is the current behavior?
Texts do not appear in a tab
What are the steps to reproduce?
I really have no idea why it happens.
I just tried to use tabs regulary in my app.
I really have no idea why the display is not working, and not showing any texts, my app is too big for a plunker. I also have no idea how to reproduce it.
I have simply this:
<md-tab-group>
  <md-tab label="One">

One

        Test
    </md-tab>
</md-tab-group>

Outputs:

What is the use-case or motivation for changing an existing behavior?
Md tab bug fix
Which versions of Angular, Material, OS, browsers are affected?
Angular: 2.0.2,
"@angular/material": "^2.0.0-alpha.9-3",
OS: Windows
Browers: Chrome

That may not be the correct usage for 2.0.0-alpha.9-3
Do instead:
<md-tab-group>
  <md-tab>
     <template md-tab-label>One</template>
    <template md-tab-content>
      Test
    </template>
  </md-tab>
</md-tab-group>

Your code uses the simple API but I don't think that it's part of the alpha 9-3 release

Thanks @RoxKilly ! The documentation mislead me.

"Your code uses the simple API but I don't think that it's part of the alpha 9-3 release"
I don't think so. I think that the two approaches are valid but for some reason the simple API is not working in alpha.9-3.
I think it is really a bug.
Could someone from the core team ensure that the simple API was removed and we should use only the <template md-tab-label>One</template> ?
Thanks!

@vinagreti the Plunker you linked to does not use the released alpha 9-3. It uses the development version (look at systemjs.config.js)
I wasn't implying that the simple API has been removed from 9-3, but rather that it has not yet made its way to release (ie. it will be in a later version because right now it's just in the development channel)

Sure, because of that (Dev version) I thought that simple API was not removed from material but it was indeed removed from alpha-9.3.
Thanks for your quick reply!

@theunreal @vinagreti the code in the OP works on version  alpha 10

Hi, I solved changing the CSS the angular-material v1.0.0 by v1.1.0
This is the new CSS: https://ajax.googleapis.com/ajax/libs/angular_material/1.1.0/angular-material.min.css

@jacastellanosc man this bug was reported in 2016.

Sorry, until now I occurred me. And today it showed itself  the error in my
code.
____________________Jimmy Castellanos C
Celular: +57<PHONE_NUMBER>
Skype: jacastellanoscc
www.lyons-sas.com
2018-02-26 9:36 GMT-05:00 Ronildo dos Santos<EMAIL_ADDRESS>
@jacastellanosc https://github.com/jacastellanosc man this bug was
reported in 2016.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/angular/material2/issues/1651#issuecomment-368522742,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHQCLnNSqjy6ueNEx7hMVaYYPDLQm2rXks5tYsFugaJpZM4KkJKv
.


Unable to follow steps in the "How to Contribute" guide

Troubleshooting
Issue Description
I am attempting to follow the how to contribute guide, but when I run
npm install
npm run build

I get an error
I am running npm and node versions 5.5.1 (maybe I need to install an older version?)
>npm node -v && npm -v
5.5.1
5.5.1

Any idea what I'm doing wrong here?
Error logs
,,npm ERR! code ENOLOCAL
npm ERR! Could not install from "..\..\_build\Tasks\Common\codecoverage-tools" as it does not contain a package.json file.

npm ERR!      C:\Users\<username>\AppData\Roaming\npm-cache\_logs\2017-11-03T17_20_53_946Z-debug.log

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: `node make.js build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      C:\Users\<username>\AppData\Roaming\npm-cache\_logs\2017-11-03T17_20_53_996Z-debug.log```

does it work with node 6 LTS?  We can update docs ....

I honestly thought I installed the latest LTS from nodejs.org - but looking at the version above, that doesn't match up. I will reinstall and see if that changes anything.

I am also running into this issue! The master branch seems to work but i can not build the latest release branch (m126?)

Tests/L0.ts(3,22): error TS2307: Cannot find module 'vsts-task-lib/mock-test'.
Tests/L0.ts(4,21): error TS2307: Cannot find module 'vsts-task-lib'.
Tests/TestSetup.ts(1,21): error TS2307: Cannot find module 'vsts-task-lib/mock-answer'.
Tests/TestSetup.ts(2,23): error TS2307: Cannot find module 'vsts-task-lib/mock-run'.
container.ts(4,21): error TS2307: Cannot find module 'vsts-task-lib/task'.
containerbuild.ts(4,21): error TS2307: Cannot find module 'vsts-task-lib/task'.
containercommand.ts(3,21): error TS2307: Cannot find module 'vsts-task-lib/task'.
containerpush.ts(4,21): error TS2307: Cannot find module 'vsts-task-lib/task'.
containerrun.ts(4,21): error TS2307: Cannot find module 'vsts-task-lib/task'.
containertag.ts(4,21): error TS2307: Cannot find module 'vsts-task-lib/task'.
,
,,
[15:17:37] 'build' errored after 4.45 min
[15:17:37] Error: Missing error message
at new PluginError (E:\VSTSTasks\vsts-tasks-releases-m126\node_modules\gulp-util\lib\PluginError.js:73:28)
at make (E:\VSTSTasks\vsts-tasks-releases-m126\gulpfile.js:17:12)
at Gulp. (E:\VSTSTasks\vsts-tasks-releases-m126\gulpfile.js:25:5)
at module.exports (E:\VSTSTasks\vsts-tasks-releases-m126\node_modules\orchestrator\lib\runTask.js:34:7)
at Gulp.Orchestrator._runTask (E:\VSTSTasks\vsts-tasks-releases-m126\node_modules\orchestrator\index.js:273:3)
at Gulp.Orchestrator._runStep (E:\VSTSTasks\vsts-tasks-releases-m126\node_modules\orchestrator\index.js:214:10)
at Gulp.Orchestrator.start (E:\VSTSTasks\vsts-tasks-releases-m126\node_modules\orchestrator\index.js:134:8)
at C:\Users\hubertusg.ADOS\AppData\Roaming\npm\node_modules\gulp\bin\gulp.js:129:20
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickCallback (internal/process/next_tick.js:180:9)

E:\VSTSTasks\vsts-tasks-releases-m126>

The Node version I am using is the latest LTS version, I will try to downgrade to the LTS version 6 and check if it works then.

Any update on this issue, I'm facing the same!

@hubertusgr I just ran it with node 6.12.0 and npm 3.10.10 and it worked.
Let me know if it works when you try version 6 LTS.

@kuvinodms Can you try the same?

I could finally get it to work on my mac where I rolled back to node 6 LTS. (on my windows machine the tasks would not build, no matter which node and npm i tried)
But seriously you should probably upgrade the build mechanism to work with a node and npm version wich is still supported as the current LTS version is version 8 afaik.

npm install -g npm@4
This worked for me!

I can confirm that on Windows 10 I was able to build and run tests on master using node v4.8.6 and npm 3.10.10.

@hubertusgr I believe this is still supported as LTS according to the Node page.
Going to close this issue, please reopen if anyone has troubles. Thanks!

I would actually suggest that a min ver, max ver be added to the contribution guide, at least until the higher version npm's/nodes are supported.


SectionPost.Delete

Implement a Delete function within the SectionPost class to enable deleting posts.
Throw appropiate exceptions if the response returned by elitepvpers is indicating that the logged in user lacks permission in order to delete the specified post.

done in #b006039


Tops 815 add back missing measures

TOPS-815 adding back three missing measures (TAP data only)
workbasket 545 (and envelope ID 220185) had these measures in when sent to CDS, but were subsequently removed before committing to TAP. This update adds these back in so TMs can change them going forward.
Why

Adding back three measures, we need to make changes to
Aligning to what we have sent across to CDS and CI
Using a migration as this seems more controlled than hacking at console, plus its testable

What

Uses a migration to add back data to the database that was incorrectly removed historically

Checklist

Requires migrations? yes
Requires dependency updates? no
--->

Links to relevant material
See: Original workbasket ticket : https://uktrade.atlassian.net/browse/TOPS-707
See: Fix ticket : https://uktrade.atlassian.net/browse/TOPS-815

note: tested against production data and migrated correctly, also ran business rules on workbasket and no issues found


Changes in categorization page --> last modified

Describe the bug
Changes in categorization page is not reflected in the Last modified data on front page
To Reproduce
Steps to reproduce the behavior:

Check last modified for a process on the front page
Open a process
Go to categorisation page
Make a change
Go back to the front page and check last modified date

Expected behavior
Last modified to be updated upon changes in categories page

Deployed to Dev environment and available to test there now. @ntorsen

This is actually an issue for the To-be process #192 as well when tested in QA now.

This is working as expected in Dev environment 👍 @Magos


AnimationManager: onUpdate should fire after the cellIndex changes.

The onUpdate event should be fired after the cellIndex has been change. This will mean callbacks added to the onUpdate event will be able to get a more accurate cellIndex for that sprite.

Updated in 1.2 branch.


fix: SDA-1945: unregister global shortcuts for client switch on window blur

Description
Unregister global shortcuts for client switch on window blur
SDA-1945
Solution Approach
Unregister global shortcuts on window blur and register them again once the window is focused.
Related PRs
N/A

Build failure is because of https://github.com/actions/setup-node/issues/77, hence merging this with an override.


Definite assignment assertions

This PR introduces the ability for a variable or property declaration to include a definite assignment assertion in the form of a ! character following the variable or property identifier. A definite assignment assertion instructs the control flow analyzer to always consider the variable definitely assigned, even when the analyzer is unable to prove it.
// Compile with --strict
class C {
    data!: string;  // Suppress strict initialization check
    setData(value: string) {
        this.data = value;
    }
    getData(): string {
        return this.data;
    }
}

In the example above, if it is known that setData will always be called before getData, there is no need to initialize the data property upon construction. However, the control flow analyzer can't make that assumption, and in --strictPropertyInitialization mode (see #20075) it reports an error unless a definite assignment assertion ! is included.
function f() {
    let x!: number;  // Suppress definite assignment check
    doSomethingWithCallback(() => {
        x = 1;
    });
    console.log(x);
}

In the example above, if it is known that doSomethingWithCallback will always invoke the callback before returning, there is no need to initialize x in its declaration. However, the control flow analyzer conservatively assumes that x is used before being assigned in the console.log(x) call and reports an error. A definite assignment assertion can now be included in the declaration to suppress this error.
Definite assignment assertions are permitted only in the following cases:

On a property declaration in a class, provided the property has a type annotation and no initializer and isn't static or abstract.
On a let or var variable declaration, provided the variable has a type annotation and no initializer.

Related issues: #11463, #12855, #13811.

@ahejlsberg what's the best way to add suppression at call site, not globally for the variable?
See your second example, like this:
function f() {
    let x: number;  <---- reluctant to suppress checks for real code
    doSomethingWithCallback(() => {
        x = 1;
    });
    console.log( x as x! ); <----- prefer to suppress checks at diagnostic call site only
}

@mihailik I think you are looking for the pre-existing not-null assertion:
console.log( x! )

@gcnew great, but would that work in this case?

@mihailik I tested it before posting just to make sure and it worked.
Thinking about it for a second time, is your intention to mark properties as "assigned" in a class constructor under --strictPropertyInitialization? If that's the case, I'm afraid this will not assure the compiler that the property has been assigned. I haven't tried it yet, though.

@gcnew  I was referring to the second example in the original post. It's console.log used as one-off diagnostics, where in-place assert is preferable to the wide-scoped change.
Thanks for the syntax!!

Any chance this feature could expand a bit to solve ~A2 as well?

.ts(616,8): error TS1255: A definite assignment assertion '!' is not permitted in this context.
.ts(621,14): error TS2365: Operator '!==' cannot be applied to types '0' and '1'.
The terminal process terminated with exit code: 1

I know, I know... ~#9998?
Wish: Instead of the TS1255 error when variable declaration has an initial value, TypeScript treats it as a: don't overly-narrow type for later CFA assertion.


repository contains unwanted files

The repository contains files that should not be there.

/RSSDP/src/Main/.vs
/RSSDP/blob/master/src/Main/Rssdp.Net45/log.txt

Thanks for letting me know, I'll clean it up when I get a chance.

Should be fixed now, thanks.


Should we updated std to do DDOF correction?

We should actually be doing this for the .regress() method on Brain_Data objects otherwise we underestimate the SEs. The ddof correction is the number of columns of the design matrix (this makes the OLS results identical to what you'd get from R or statsmodels). I added that to a PR.

Fixed in #134


Multi language use problem

The introduction of multi language without effect, what will be the problem?

We cannot help you without looking at your code...


Remove references to Assert single-arg methods.

Single arg Asserts are deprecated for Spring 4.3.7; had been removed temporarily in 5.0 snapshots (are back now), and are object of removal for at least Spring 5.1.
see: SPR-15196

Duplicates #31.


Requests being denied a response from browsers

I'm facing a very strange issue with io.projectreactor.ipc:reactor-netty:0.5.0.M2.
To be honest, I'm not really sure if the issue is at reactor-netty or actually at Netty itself. It's just that I am supposing that, being the Netty version more stable (4.1.3.Final), it seems more possible that it is a reactor-netty thing. I'm terribly sorry if I'm wrong and this is a Netty thing… I just cannot understand enough what is happening to determine who to blame, and I have to start somewhere 😔
I have created a test project (Spring Boot-enabled, using the new experimental Reactive Web support), including a README with instructions, here: https://github.com/danielfernandez/test-spring-boot-reactive-netty
The idea is that, when I start this application using mvn spring-boot:run and try to access the only controller it's serving –a very, very simple one– using a browser (Chrome, Firefox or Safari) on Mac OS, after some refreshes (normally 2-3), the server starts sending an HTTP response only every two HTTP requests.
I've verified that the requests reach the server (by debugging), and also that there is no HTTP response at all in those cases (by sniffing the network). I've also verified that the HTTP requests look exactly the same when there is response and when there is not. Also, weirdly, I've not been able to reproduce this using curl, httpie or wget. Only from browsers.
I've also verified that this does not only happen to me (Mac OS El Capitan 10.11.6). I've seen this happening too on a Mac OS Yosemite machine.
Versions been used:

reactor.version: 3.0.0.RC1
spring.version: 5.0.0.M1

The issue still persists after updating the sample application (see above) to:

reactor.version: 3.0.3.BUILD-SNAPSHOT
spring.version: 5.0.0.BUILD-SNAPSHOT

Also, the issue seems not to be MacOS-only, as I've replicated this also in a Windows 10 machine. The environments this has been verified to happen are:

Chrome 52, Postman (Chrome-based), Firefox 49 and Safari 9.1.3 on Mac OS X 10.11 El Capitan (server + browsers, all local).
Chrome 52 and Firefox 49 on Windows 10 (server + browsers, all local).

But, important: in these same machines –actually, without even stopping the netty server–, the issue cannot be replicated if the server is accessed using the external IP address instead of localhost.
So with the same browser, same server instance, http://localhost:8080 shows the issue, while http://<IP_ADDRESS>:8080 does not.

An additional example application to check this behaviour is the Thymeleaf + Spring Reactive sandbox application (which I use as a sandbox for creating the Thymeleaf integrations with Spring Web Reactive).
It's here: https://github.com/thymeleaf/thymeleafsandbox-springreactive/tree/nettyissue (note there is a nettyissue branch).
It can be built with mvn -U clean compile spring-boot:run, and visited at localhost:8080.
The interesting part about this app is that the index pages for both Thymeleaf and FreeMarker (at URLs /, /thymeleaf and /freemarker) include a static resource that should be displayed (a logo in PNG). And this fact of including static resources in the returned HTML page seems to force even more the reproducibility of this issue.
Using this thymeleafsandbox-springreactive application, I've been able to replicate this even on an Ubuntu 16 machine with Firefox 48 and Chromium 52.
By the way, I've been reporting this here because, as explained above, I think it might be a reactor-ipc issue. If you prefer me to open a JIRA ticket for Spring Web Reactive instead, please just tell. Thanks!

@danielfernandez have you tried switching to one of the other supported servers? It should be a matter of changing the pom only. It would be interesting to see the result with RxNetty and also a different runtime like Tomcat/Jetty.

I've created new branches in https://github.com/thymeleaf/thymeleafsandbox-springreactive in order to test other servers. My results:

RxNetty works OK (branch rxnetty). But note bclozel/spring-boot-web-reactive#33.

Undertow works OK (branch undertow).

Tomcat has some kind of class loader issue (branch tomcat):

java.lang.ClassNotFoundException: org.thymeleaf.spring4.requestdata.RequestDataValueProcessor4Delegate
	at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1285) ~[tomcat-embed-core-8.5.5.jar!/:8.5.5]
	at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1119) ~[tomcat-embed-core-8.5.5.jar!/:8.5.5]
	at java.lang.Class.forName0(Native Method) ~[na:1.8.0_66]
	at java.lang.Class.forName(Class.java:348) ~[na:1.8.0_66]
	at org.thymeleaf.spring4.requestdata.RequestDataValueProcessorUtils.<clinit>(RequestDataValueProcessorUtils.java:70) ~[thymeleaf-spring4-3.0.1.RELEASE.jar!/:3.0.1.RELEASE]

Interestingly this exception only appears when I execute the app using the maven spring-boot:run target or directly using the java command, but not when I execute the Application class from IntelliJ. Anyway, I will investigate a bit more and report it at JIRA, as it seems some kind of strange interaction between Thymeleaf, the Reactor, Spring Web Reactive and Spring Boot…
Anyway, as I said, when I execute the app using Tomcat from IntelliJ and there are no class loader issues, it works OK.
So this does look like an issue in reactor-ipc/reactor-netty, I suppose.
Also, from bclozel/spring-boot-web-reactive#21 it seems I'm not the only one experiencing this issue…

I also confirm this issue that makes for example SSE example from https://github.com/sdeleuze/spring-reactive-playground unusable with Reactor Netty. Other engines are fine.

This bug has been fixed in Reactor Netty 0.5.2.RELEASE, since this version now closes HTTP connection after each request. Keep-alive support will be enable again when properly supported.
@smaldini I guess this bug should be moved to https://github.com/reactor/reactor-netty/ and marked as fixed in reactor-netty 0.5.2.RELEASE, isn't it ?

So reactor/reactor-netty#4 seems to be the cause for this...

I can confirm this seems fixed (or worked around ;)) for me now.


Interrupting transition starts at the next step of the interrupted transition

Problem statement
expected

Transition is running, evolving an attribute value
Compute a new attribute value and set it on the node and schedule a new transition
Verify that the attribute value is updated on next d3.timer tick
The interrupt event fires
The new transition starts with the new attribute value

2015-10-12 18:29:58.946 index.html:519 current x:<PHONE_NUMBER>3300786 new x: 80.5697041483292
2015-10-12 18:29:58.946 index.html:538 marker interrupted	80.5697041483292
2015-10-12 18:29:58.951 index.html:200 tick: current x: 80.5697041483292
2015-10-12 18:29:58.952 index.html:533 marker started 80.5697041483292
2015-10-12 18:29:58.962 index.html:200 tick: current x: 81.02723883894973
observed

Transition is running, evolving an attribute value
Compute a new attribute value and set it on the node and schedule a new transition
Verify that the attribute value is updated on next d3.timer tick
The old transition runs for one more tick and overwrites the attribute
The interrupt event fires
The new transition starts with the incorrect attribute value

2015-10-12 18:08:19.801 index.html:519 current x:<PHONE_NUMBER>1486485	new x:<PHONE_NUMBER>1057627
2015-10-12 18:08:19.810 index.html:200 tick: current x:<PHONE_NUMBER>1057627
2015-10-12 18:08:19.812 index.html:538 marker interrupted<PHONE_NUMBER>9917357
2015-10-12 18:08:19.812 index.html:533 marker started<PHONE_NUMBER>9917357
workarround
This can be fixed by calling selection.interrupt before setting the new transition on selection but (to me anyway) this is far from obvious.

This is the expected behavior. It might be non-obvious, but I don’t see a good way of changing it without something heavy-handed like an explicit run loop instead of native event handlers.
The issue is that your code runs first, such as in response to a setTimeout or event handler callback. Your code then schedules a transition. But since any transition is instantiated without concurrently specifying a delay (the delay is set by transition.delay after selection.transition returns) or likewise tweens, the transition cannot start immediately; it has to wait until the first tick, so that you have time to configure the transition before the transition starts.
Furthermore, if you schedule multiple transitions, we want the transition callbacks to run in the order they were specified while they are active, for simplicity’s sake. And thus since your new transition was scheduled after any active transition, its first tick occurs afters the active transition’s last tick, giving the active transition a chance to overwrite whatever else your code may have done before the new transition starts. If this transition is ending on this tick and a new transition is starting, we want the active transition to end normally and not be considered interrupted.
So, this is why you must call selection.interrupt: to make it clear that your code pre-empts any active transition that is running. You can’t just rely on your new transition pre-empting the active transition. Perhaps we could add a few more special cases to control the ordering of ticks, but I think minimizing the number of special cases will ultimately be easier to understand than a black box that tries to handle the common cases but is essentially inscrutable.

Yes, thank's for explaining, that makes perfect sense now: my "expected behaviour" is not altogether sane.
I tried to add a little more explanation around this in the wiki, hopefully, it's ok.

Thanks. I made some further changes… hope it helps.


I was wondering if it is possible to add domain_hint or login_hint for the OAuth2 authorize?

I am developing a SPA that use AAD for authentication and then call an Web API. I was wondering if it is possible to add domain_hint or login_hint for the OAuth2 authorize action to avoid Home Realm prompt? If yes, where do in the code I should include this? Thanks for your help.

This sample has been archived.
The newer one can be found at: https://github.com/Azure-Samples/active-directory-javascript-graphapi-v2