White Plus / Minus Icon are not white on dark background color

Describe the bug
Some white Icons appeal differently on some font sizes on dark background colour. It looks more light blue or grey.
I noticed it on the plus and minus icon.
Steps to Reproduce
Reproduction Link: https://stackblitz.com/edit/vitejs-vite-kvithz?file=src%2FApp.tsx,src%2FApp.css,src%2Findex.css&terminal=dev
Zoom in and out and have a look at the plus and minus.
Expected behaviour
Plus and Minus icon should be white no matter which zoom / dpi / size level.
Screenshots

Context

OS: Windows 10
Browser/Environment [Chrome, safari, node]
Library  @phosphor-icons/react (I also had the issue with Angular)
Version 2.1.4

Additional notes
This might also affect other icons.

Unfortunately, this is caused by subpixel rendering native to your platform, and is a side-effect of the fact that we do not pixel-snap our icons. This is prohibitive for a general-purpose icon set that is meant to be used at many sizes, and not something we will change.
YMMV, but the best outcome is either to use the icons at 16px of multiples of it, or to with great care apply the shape-rendering: crispedges; CSS property (this can cause a lot of ugliness in shapes with curves and diagonals).


Need to optimize combine_unbinned_data method

This method is using more memory than needed. Needs to be optimized.

@krishnatejavedula I wanted to try to provide a bit of guidance on this issue.
You'll see that the method reads in one dictionary at a time, and concatenates them to the final combined dictionary. In order to concatenate a given dictionary, it needs to be read into memory. However, it should be immediately removed from memory after being concatenated. I'm not sure that this was actually happening, b/c when we were testing it we saw that the RAM was multiplying with the number of combined files (beyond what we expect for just the new combined dictionary). So that's one thing to check. Although this may have already been resolved since opening the issue -- I'm not quite sure.
At most, I think the RAM will need to hold the data for all combined dictionaries, plus the current dictionary that is being concatenated. One possible option to reduce this might be to try a memory map: https://numpy.org/doc/stable/reference/generated/numpy.memmap.html.

@ckarwin Thanks for the guidance. It does seem like the RAM usage is higher than expected and I have encountered this issue while working with Data IO during DC2. I’ll check on this and see if using NumPy's memmap can help reduce memory consumption.
I appreciate your input and will keep you updated.


[help] How to create a second chatgpt_telegram_bot container on the same host？

I want to create a second chatgpt_telegram_bot container on the same host to use a different OpenAI API key. I created a new folder, tried to modify the container_name of the three containers in the docker-compose.yml file, and the MONGODB_PORT and MONGO_EXPRESS_PORT in the ./config/config.env file.Then I executed docker compose --env-file config/config.env up --build again, but the containers failed to start properly. I am not very proficient in Docker. Can anyone tell me what I need to modify in order to create a second chatgpt_telegram_bot container?

I modified the docker-compose.yml file according to the changes shown at https://github.com/karfly/chatgpt_telegram_bot/pull/161, and now I can set up multiple chatgpt_telegram_bot containers on a single host simultaneously. However, when I run two chatgpt_telegram_bot containers at the same time (including two mongo-express and two mongo instances), I find that after a while, my host becomes unable to connect, loses network connection, and the gpt_bot becomes inactive. It requires a restart to return to normal. If I only run one chatgpt_telegram_bot container, there is no such issue. I'm guessing if there is a conflict when multiple mongo and mongo-express containers are running simultaneously, causing the system to freeze? Or is there some other issue?
So, what is a reasonable method to run multiple chatgpt_telegram_bot containers on a single host at the same time?


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/39478

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/89917


[core] Fix possibility to passNoneType objects in prepare

What does this PR do?
Fixes https://github.com/lvwerra/trl/issues/413 and the current CI in TRL :D https://github.com/lvwerra/trl/actions/runs/5204023029/jobs/9387749684?pr=412
Before https://github.com/huggingface/accelerate/pull/1555 it was possible to pass NoneType objects into prepare and that function would do nothing with it and return it.
Adding a simple check if item is not None:  before setting the _is_accelerate_prepare attribute circumvents the bug
cc @sgugger @muellerzr

Can you also add a test where None is passed to Accelerator.prepare? If you rely on this behavior, we need to make sure it's tested so there is no future regression.

sure, adding it now


Client respecting layers of mix nodes

Codecov Report

Merging #38 into develop will decrease coverage by 0.93%.
The diff coverage is 18.18%.

@@             Coverage Diff             @@
##           develop      #38      +/-   ##
===========================================
- Coverage    27.39%   26.45%   -0.94%
===========================================
  Files           15       15
  Lines         1537     1546       +9
===========================================
- Hits           421      409      -12
- Misses        1042     1064      +22
+ Partials        74       73       -1

Impacted Files
Coverage Δ

helpers/pki.go
0% <0%> (ø)
:arrow_up:

helpers/crypto.go
31.57% <0%> (-27.8%)
:arrow_down:

client/client.go
0% <0%> (ø)
:arrow_up:

clientcore/mixClient.go
57.14% <50%> (-3.8%)
:arrow_down:

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 cbd1290...8f0caab. Read the comment docs.


Use SVUnit for unit level testing

We should be able to use the SVUnit for unit level testing. This will help to develop, test and deploy our code with ease and will help to maintain our code base better.
Refer the below project for more info:
https://github.com/svunit/svunit
Tasks to be done:

[x] #25
[x] #20
[x] #21
[x] #22
[ ] #23
[x] #24
[ ] #26
[ ] #27
[x] #28

We have been able to learn as how to use SVUnit and now we are ready to use unit testing for our projects.


DPT program Icon

The DPT should have the new IPOCSMR logotype as program icon

No longer valid since this repo is now deprecated. Solved with the new version in the new repo


~FREE! PUBG Mobile UC Generator Free 2024 New Updated

FREE PUBG Mobile UC Generator 2024 How to Get Unlimited Free Mobile UC Generator FREE
➤🔴 CLICK HERE TO GET GENERATOR NOW📺📱
➤🔴 CLICK HERE TO GET GENERATOR NOW📺📱
I have done working on the new update of the Free Pubg Uc Generator Free Pubg Uc Free ONLINE-NopASswOrd/ unlimited, some cool features were added, also improved performance and stability. Now there are more safety features to protect you from the ban. We received the letter from [Free Pubg Uc Generator limited to close the matter. However, we blocked their IPs so they could not see our generator in their frameworks.
PUBG Mobile, the leading smartphone game, has an in-game currency called UC, which you can use to purchase an exclusive set of outfits and weapon skins.
UC is generally very expensive, and you need to spend a lot of money if you want some extra in-game currency. If you don't want to spend money, however, you can participate in events and complete rare missions to grab some UC in the game.

Repo.


2 games running without fonts - any ideas?

2 games - "Next Stop 2" and "Next Stop 3" - run without fonts which makes them unplayable.
API traces don't seem to work for these 2 games, IDK why. I did it following the instructions and yet no file was created. So all I can provide are the d3d11 and dxgi logs. There are some warnings inside these logs but I'm not a programmer and I don't understand what do these warnings mean.
Software information
Next Stop 2
Next Stop 3
default settings the games were installed with.
System information

GPU: GTX 1050 Ti 4GB
Driver: 455.38
Wine version: 5.20
DXVK version: 1.7.2

Apitrace file(s)

Put a link here

Log files
NextStop3_d3d11.log
NextStop3_dxgi.log

Do the fonts work with WineD3D?

Do the fonts work with WineD3D?

I have no idea how to use WineD3D outside of Steam Proton. I only know library override in winecfg.

I found a way to fix the problem. It turned out I had to run "winetrucks corefonts".


Updates Vagrant Documentation

Previously, the Vagrant documentation was missing a few minor
steps. This patch adds verbosity to the Vagrant documentation that
should improve developer onboarding.

take out menion of 636 and I will merge. Then we get 636 fixed quickly   :)

@eparis I removed the reference to 636 but kept the instructions to update the default source_type in vagrant/README.md. I also updated 636 making a note to remove this step in the instructions before closing the issue.


Upgrade to new version goes back to 3.0.0

Environment

Operating System: Darwin
Node Version:     v16.19.0
Nuxt Version:     3.0.0
Nitro Version:    1.0.0
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      app, modules, ssr, css, unocss, build, runtimeConfig, sourcemap
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
Just typing in the terminal
npx nuxi upgrade
of
npx nuxi upgrade -f
Describe the bug
I wanted to use vue 3.3 now, and I've tried to upgrade by using nuxi upgrade. Instead of upgrading the inner packages and vue to 3.3, still loading the older version of vue (3.2.47).
When I running the npx nuxi upgrade, this action returns my nuxt project to version 3.0.0.
To fix this, I just typing pnpm up --latest, to rollback the package.json.
Additional context
No response
Logs
No response

Under the hood nuxi runs pnpm -D nuxt. Do you mean that your package.json was updated to 3.0.0, or that the version actually installed in node_modules was 3.0.0?

Hello
My version is nuxt 3.4.3. I wanted to use vue 3.3, but only returns to old version. Here the prompt:
npx nuxi upgrade -f
npm WARN ignoring workspace config at /Users/mateus/Documents/projects/afiliapay/apps/apps/platform/.npmrc
Nuxi 3.0.0                                                            14:00:47
14:00:47
ℹ Package Manager: pnpm 8.5.0                                         14:00:47
ℹ Current nuxt version: 3.0.0                                         14:00:47
ℹ Removing lock-file and node_modules...                              14:00:47
ℹ Installing latest Nuxt 3 release...                                 14:00:47
../..                                    | Progress: resolved 0, reused 1, downl../..                                    | Progress: resolved 69, reused 69, dow../..                                    | Progress: resolved 71, reused 71, dow../..                                    | Progress: resolved 162, reused 162, d../..                                    | Progress: resolved 273, reused 272, d../..                                    | Progress: resolved 426, reused 425, d../..                                    | Progress: resolved 625, reused 624, d../..                                    | Progress: resolved 776, reused 776, d../members                               |  WARN  deprecated<EMAIL_ADDRESS>../..                                    | Progress: resolved 776, reused 776, d../members                               |  WARN  deprecated<EMAIL_ADDRESS>../..                                    | Progress: resolved 776, reused 776, d../..                                    | Progress: resolved 889, reused 889, d../..                                    | Progress: resolved 1024, reused 1002,../..                                    | Progress: resolved 1184, reused 1118,../..                                    | Progress: resolved 1377, reused 1314,../members                               |  WARN  deprecated<EMAIL_ADDRESS>../..                                    | Progress: resolved 1377, reused 1314,../..                                    | Progress: resolved 1526, reused 1463,../..                                    | Progress: resolved 1526, reused 1464,../..                                    | Progress: resolved 1535, reused 1472,../..                                    | Progress: resolved 1537, reused 1474,../..                                    | Progress: resolved 1550, reused 1487,../..                                    | Progress: resolved 1562, reused 1499,../..                                    | Progress: resolved 1570, reused 1507,../..                                    | Progress: resolved 1573, reused 1510,../..                                    | Progress: resolved 1575, reused 1511,../..                                    | Progress: resolved 1575, reused 1512,../..                                    |  +12   -8 +-
../..                                    | Progress: resolved 1575, reused 1512,../..                                    | Progress: resolved 1575, reused 1512, downloaded 0, added 0, done
../members postinstall$ nuxt prepare
│ Nuxi 3.0.0
│ ✔ Types generated in .nuxt
└─ Done in 2s
dependencies:

@afiliapay/unocss-rules 1.0.0 <- ../../packages/unocss-rules
@afiliapay/use-afiliapay 1.0.0 <- ../../packages/use-afiliapay
@ckeditor/ckeditor5-build-classic 37.1.0
@ckeditor/ckeditor5-image 37.1.0
@ckeditor/ckeditor5-vue 5.1.0
@nuxt/cli 2.16.3
@pinia/nuxt 0.4.10
@vorms/core 1.1.0
@vorms/resolvers 1.1.0
@vuepic/vue-datepicker 5.0.1
@vueup/vue-quill 1.1.1
@vueuse/components 10.1.2
@vueuse/nuxt 10.1.2
add 2.0.6
c8 7.13.0
chart.js 4.3.0
date-fns 2.30.0
design 1.0.0 <- ../../packages/design
maska 2.1.9
normalize.css 8.0.1
quill-blot-formatter 1.0.5
vue-chartjs 5.2.0
zod 3.21.4

devDependencies:

@histoire/plugin-nuxt 0.16.1
@histoire/plugin-vue 0.16.1
@nuxt/test-utils 3.4.3
@types/pell 1.0.1
@unocss/nuxt 0.51.12
@unocss/preset-attributify 0.51.12
@vitest/coverage-c8 0.31.0
@vue/test-utils 2.3.2

histoire

histoire 0.16.1
jsdom 22.0.0

nuxt

nuxt 3.4.3
sass 1.62.1
vitest 0.31.0

WARN  Issues with peer dependencies found
apps/platform
└─┬ @nuxt/test-utils 3.4.3
└── ✕ unmet peer<EMAIL_ADDRESS>found 0.31.0
Done in 9.7s
ℹ Cleaning up generated nuxt files and caches...                      14:00:57
ℹ Upgraded nuxt version: 3.0.0                                        14:00:57
✔ You're already using the latest version of nuxt.                    14:00:57
mateus@MacBook-Air-de-Mateus platform %

It looks like the issue is that npm has cached an old version of nuxi - try running npx nuxi@latest instead.

Well, it's worked to upgrade to nuxt 3.4.3, but remains vue 3.2.47. I wanted to upgrade now to vue 3.3

You can try npx nuxi@latest upgrade --force


The Code 128 encoder was improved to perform automatic encoding of extended ASCII data using FNC4.

Barcode Writer in Pure PostScript » postscriptbarcode #25 SUCCESS
This pull request looks good
(what's this?)


Test 5.11.0/5.12.0 Sync client

Describe the issue:
Need to test sync client for 5.11.0 migration, which includes migration for symmetric key encryption

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Junit5 Unit test not detected on GitHub actions but pass locally

Description
Description
My All JUnit5 test cases are not detected  on Github action but when I run the tests locally, all tests pass.
Repo. Details
Workflow Result:
https://github.com/TheReprator/Wipro/runs/3397355056?check_suite_focus=true
Repo: https://github.com/TheReprator/Wipro
Branch: Master
Looking forward for a solution.
Regards,
Vikram Singh
Virtual environments affected

[ ] Ubuntu 16.04
[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11
[ ] Windows Server 2016
[ ] Windows Server 2019

Image version and build link
https://github.com/TheReprator/Wipro/runs/3397355056?check_suite_focus=true
Is it regression?
no
Expected behavior
All Unit test case should be detected & pass
Actual behavior
No test case detected
Repro steps
https://github.com/TheReprator/Wipro
Branch: Master

Hello @TheReprator,
According to the information provided, I'm not completely sure that the issue is related to our images and should be resolved on your side. Most probably the issue is somehow related to project dependencies(according to the error messages) and it's better to ask your question or post this issue in the Support Community.
We're looking forward to your reply.

Issue is caused by the version of mvn that is used by the image, which in turn causes an older version of maven-surefire-plugin to be used.
This can be fixed by explicitly setting the maven-surefire-plugin version, rather than using the default version.


feat(kong): allow customizing chart version and proxy readiness probe

Codecov Report
Patch coverage: 10.00% and project coverage change: -50.00% :warning:

Comparison is base (d6d384b) 59.70% compared to head (23454ad) 9.70%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #774       +/-   ##
==========================================
- Coverage   59.70%   9.70%   -50.00%
==========================================
  Files          48      48
  Lines        3886    3896       +10
==========================================
- Hits         2320     378     -1942
- Misses       1271    3451     +2180
+ Partials      295      67      -228

Flag
Coverage Δ

integration-test
9.70% <10.00%> (-50.00%)
:arrow_down:

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

Files Changed
Coverage Δ

pkg/clusters/addons/kong/addon.go
12.61% <0.00%> (-45.82%)
:arrow_down:

pkg/clusters/addons/kong/builder.go
42.71% <14.28%> (-44.79%)
:arrow_down:

... and 42 files with indirect coverage changes

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


Generic packet handling

This pull request contains an implementation of 1) publishing generic radio packets received from crazyflies to topics which are hosted on a per crazyflie basis and 2) a service which can be called to transmit arbitrary packets to a crazyflie, where the services are provided on a per crazyflie basis. Please see issue #60 for a discussion of the motivation for implementing this feature.

Thanks a lot for your contribution and sorry for the long merging delay (I was on vacation).

I'm happy to have been able to contribute, and I appreciate your feedback as well!


Update to latest

perhaps a pretty basic code style writeup is in order, just to manage the weird, idiosyncratic syntaxes present in the language.


Need to write end-to-end tests

The old server/client has a whole series of E2E tests that cover both client and a test server.

Write the equivalent E2E server (so that old clients can test against new server)
Write the E2E tests - with either local server (TestServer) or remote server (by setting a test param)
Ensure all the E2E tests pass in situ
File bugs for any test that doesn't pass from the old client.

Complete.


Change Data Capture

Looking through the code it looks like that Change Data Capture events (/data/ are not supported?
def subscribe(self, channel, callback, replay=True, autocreate=True):
    type = None
    if channel.startswith('/u/'):
        type = 'generic'
    elif channel.startswith('/topic/'):
        type = 'push_topic'
    elif channel.startswith('/event/'):
        type = 'event'
    else:
        raise BadSubscriptionException(
            '{0} is not a valid subscription channel.'.format(
                channel
            )
        )

@Vanderstok fix in progress

@Vanderstok fixed in https://github.com/SalesforceFoundation/salesforce-streaming-client/commit/c1e0b85e7e7d18d046cdd94422564b36abb65369 and released to pypi as version 0.1.13
Please let me know if it doesn't work for you!


Added phone number field to user

r @thomaslee1911 @kongsally

Now all phone number formats are accepted. The non-digit characters are stripped out.
Look good now @kongsally @thomaslee1911 ?

Ok, just waiting for a :+1: from @thomaslee1911


add volumes in pod if images contains volumes configuration

such as /var/cache/nginx in official nginx image

LGTM


Tailwind components

As we know Oruga is beautiful project, both have super handy components. I'm also Buefy user and love that.
The only great feature request after using these two lib for about 4 years now is styling. I mean, I love the no CSS dependency and the fact that both also provide some styling (Buefy provides it all)
But Oruga, can we do something about Tailwind ? Like refactor the components to be tailwind compatible, and mostly configurable?
.o-notification {
    @apply gel-default-bg rounded-3xl p-10 dark:text-gel-brown relative;

    .o-notification__close {
        @apply absolute w-7 h-7 right-3 top-2;

        .o-icon {
            &:before {
                content: 'x';
                @apply text-gray-900 font-normal text-2xl;
            }
        }
    }
}

.o-btn {
    @apply bg-gel-red-dark px-5 py-3 rounded-3xl text-white;
}

Something that would look like 👆
Thanks!

Thanks 🙏
There is a old sample project that integrates Oruga with tailwind.
Btw you can use it as you prefer.. overriding the default classes (Oruga minimal CSS) or creating new classes to apply to each components removing the default or in append.


feat(compaction): control memory of compactor

Signed-off-by: Little-Wallace<EMAIL_ADDRESS>What's changed and what's your intention?
close https://github.com/singularity-data/risingwave/issues/3921

Add memory control for compactor
fix in-correct charge for cache

Checklist

[ ] I have written necessary docs and comments
[ ] I have added necessary unit tests and integration tests
[ ] All checks passed in ./risedev check (or alias, ./risedev c)

Refer to a related PR or issue link (optional)

I limit memory with 5GB and we can see that the memory of process does not exceed very much.
But the compact speed seems to reduce much

failpoint test fails. You need to enable failpoints feature locally to fix the tests.
Also, let's prioritize merging this PR to unblock nexmark benchmark.


Put Cloudfront for new docs in infrastructure-as-a-code

This is a part of a separate issue, closing.


cannot set color with string

Odd issue here where every time I try to set the color "red" with strings, my lights revert to the color blue.
Here is a flow that injects "color":"red" or "color":"f80d0d".
When I try to set the color with the string version, my light always turns blue. At first I thought it was reverting to the previous hex value, but if I change the light to any other color, with any method (string, hex), injecting "color":"red" always makes it revert to blue! Super strange!  Using huemagic 1.9.0.
If I enable "colornaming" I can see in the output that hitting the inject with "color":"red" will report:
"hex: "3b3cff"
color: "blue"
I added a bunch of other nodes to inject based on string, like "color":"green", "color":"white", etc and...they all will turn blue!  So basically.... injecting colors by string works only for the color blue.
[{"id":"ad2a5fce.a9d08","type":"hue-light","z":"54122aa2.7eec94","name":"color light","bridge":"6ae38e2e.c19bd","lightid":"5","colornamer":false,"x":472,"y":1232,"wires":[["2fdc9a05.4b57e6"]]},{"id":"e90d87c9.80f948","type":"inject","z":"54122aa2.7eec94","name":"","topic":"","payload":"{"color":"red"}","payloadType":"json","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":282.5,"y":1214,"wires":[["ad2a5fce.a9d08"]]},{"id":"722e6a95.828274","type":"inject","z":"54122aa2.7eec94","name":"","topic":"","payload":"{"hex":"f80d0d"}","payloadType":"json","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":281.5,"y":1261,"wires":[["ad2a5fce.a9d08"]]},{"id":"2fdc9a05.4b57e6","type":"debug","z":"54122aa2.7eec94","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","x":643,"y":1231,"wires":[]},{"id":"6ae38e2e.c19bd","type":"hue-bridge","z":"","name":"Philips hue","bridge":"<IP_ADDRESS>","key":"TTvODGlag9k1rF4ZWey-TjvJmlq0FmyH3pdeeM7O","interval":"3000"}]

Also having this issue.  Anyone find a workaround?  Setting via rgb works but is more tedious. :)

@mbillau I believe I've found a fix: https://github.com/Foddy/node-red-contrib-huemagic/pull/84

Hi @geekdave, thanks for the comment and fix!


workspace/didChangeConfiguration doesn't update diagnostics

I'm currently watching compile_commands.json for any changes within ide-cquery, and sending a workspace/didChangeConfiguration to cquery whenever the file gets modified. The idea is to force cquery
to rescan the compile_commands.json as things change. What I'm doing to test that everything is working correctly is to modify the include paths, but I don't see symbols getting complained about that no longer exist in the world of cquery. cquery seems to respond to the didChangeConfiguration correctly - I see  the log messages that compile_commands.json is getting loaded and correctly don't see the include directories that I removed.
2018-03-15 17:15:34.958 (  87.837s) [querydb      ]        project.cc:405      0| Trying to load compile_commands.json
2018-03-15 17:15:34.958 (  87.838s) [querydb      ]          timer.cc:35       0| compile_commands.json clang time took 0.59ms
2018-03-15 17:15:34.958 (  87.838s) [querydb      ]          timer.cc:35       0| compile_commands.json our time took 0.158ms
2018-03-15 17:15:34.959 (  87.838s) [querydb      ]        project.cc:537      0| quote_include_dir: C:/Users/Elliot/dev/driver-demo/include/
2018-03-15 17:15:34.959 (  87.838s) [querydb      ]        project.cc:537      0| quote_include_dir: C:/Users/Elliot/dev/driver-demo/include/
2018-03-15 17:15:34.959 (  87.838s) [querydb      ]          timer.cc:35       0| [perf] Loaded compilation entries (4 files) took 0.965ms

However, the diagnostics still report everything is OK. The only hint I get that something might be wrong is that clang_complete shows the arguments passed to clang, which still includes the options I removed
(notice the -Ic:\toolchain... paths - those are the ones I removed):
2018-03-15 17:15:42.914 (  95.793s) [completeparse] clang_complete.cc:380      0| Creating completion session with arguments clang -working-directory=C:\Users\Elliot\dev\driver-demo --target=armv7a-xilinx-none-eabi --fshort-enums -Ic:\toolchain\usr\bin\../lib/gcc/arm-none-eabi/7.2.1/include -Ic:\toolchain\usr\bin\../lib/gcc/arm-none-eabi/7.2.1/include-fixed -Ic:\toolchain\usr\bin\../lib/gcc/arm-none-eabi/7.2.1/../../../../arm-none-eabi/include -iquote./include -iquote./include/./ -march=armv7-a -mfpu=neon-fp16 -mfloat-abi=softfp -D_POSIX_THREADS -D_UNIX98_THREAD_MUTEX_ATTRIBUTES -Os -Wall -ffunction-sections -fdata-sections -fdiagnostics-color --std=gnu11 C:/Users/Elliot/dev/driver-demo/src/opcontrol.c -resource-dir=C:/cquery/build/release/lib/LLVM-6.0.0-win64/lib/clang/6.0.0 -Wno-unknown-warning-option -fparse-all-comments -fspell-checking

Do you know some way to set a breakpoint early and attach the bin/cquery process with a debugger on Windows?  The wiki page https://github.com/cquery-project/cquery/wiki/Debugging#stopping-at-the-start-to-debug-early-issues is for *NIX but the approach should be as valuable if someone can make it available on Windows.

Damn... was hoping you would have an idea right off the bat and I wouldn't have to debug it! 😄
I will play around with it and report back.

@MaskRay You don't happen to have any idea how to run waf configure msvs? https://github.com/waf-project/waf/blob/master/waflib/extras/msvs.py I'm not familiar with waf, and following the simple instructions for how to integrate it into a build system fails because it's having trouble with bld.env['use_clang_cxx'] when trying to generate the MS VS solution files.

That was a fun debugging experience... I got MSVS working by doing some awful hard coding in the wscript. But it works and I can debug with Visual Studio. I think the problem boils down to this commit, where it was decided that diagnostics should not be emitted for interactive sessions. Since then, the is_interactive check now looks like this. I commented out the condition, and everything started working like a charm.
I'm not sure what we can do about this now - is it safe to remove the conditional? I don't think so, but it would appear that this blocks use cases. Users could be creating their build process concurrently with cquery running. They may have forgotten to include some important library headers or whatever (or perhaps they are adding a new library with a new include search path). Or perhaps they're using the wrong compiler flags or they want to start using -Wpedantic.
I'm not sure if there's an appropriate workaround to force clients to ask that diagnostics to be re-emitted, but I think that all clients would want to do this.

On second thought, could it be that clang completion manager never gets the news that those CompletionSessions have become invalidated?

Closed by #540


Xib file conversion failed

Failed to convert a project that is using interface builder (XIB) for rendering views. Please let me know the whether the WinObjC is supporting iOS projects having Xib files.

See #27

WinObjC SDK does support iOS projects with XIB files. This is done using the Xib2Nib tool. This is still under development so it may not support all types. If you encounter any problems, please send the error details.


[BUG]Unrecognized VM option 'UseFastAccessorMethods'

Describe the bug
When do sh create-dolphinscheduler.sh in openjdk 11.0.7, Program will exit.
[dolphinscheduler@root script]$ sh create-dolphinscheduler.sh
OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.

Unrecognized VM option 'UseFastAccessorMethods'

Error: Could not create the Java Virtual Machine.

Error: A fatal exception has occurred. Program will exit.

To Reproduce
Steps to reproduce the behavior, for example:
run sh script/create-dolphinscheduler.sh
Which version of Dolphin Scheduler:
1.2.1

openjdk没有相关参数

+1 on 1.3.1, does DS going to fix this in the future?

+1 on 2.0.5. On 3.0.0 beta, there is no problem, but api-server, master-server, worker-server cannot connect zookeeper lead to sprintboot start fail. I don't know if it related with openjdk and oracle jdk. Deployment is really a hard obstacle

Will be fixed by https://github.com/apache/dolphinscheduler/pull/10789


shared hosting

It would be good to test, use this gallery to a shared hosting

Could you explain a bit ?

I would use on a shared server, but before installed on a server other quelquonc I would have liked to test your photo gallery to see eventual bugs, customization etc.
and after the installation section, it must be installed from the command line, so when shared servers this is not possible
can you make a version set by FTP

The aim of sigal is to generate the files and then send it to the server, so there is no need to install it on the server.

ok


Allow using /etc/hosts for RabbitMQ name resolution

Allow using /etc/hosts for rmq name resolution
Add support for network spaces

Pending functional testing.

Pull-request updated, HEAD is now 60b061155235e113884922e7437c32d16b754c1a

Pull-request updated, HEAD is now 9a29c00c63a4863fee7f3e99c1afe4a12884a158

it would be good to split these commits in two different PR (and maybe fix typo in separate also).
rabbitmq issue is a hack that can be reverted later and it can be reviewed faster.
supporting of network spaces is more complicated and I need more time for this.

Pull-request updated, HEAD is now 580dd537baebd04a2bee1eb29d91ce3711241717

Fixing /etc/hosts is not so good solution. Anyone else may re-write it or current code can break changes of someone else.
This solution may lead to inability to resolve some names that were stored in /etc/hosts and were removed due to current implementation.

Pull-request updated, HEAD is now bef9c96844914aecc3aed89134941d93d9a850f1

Thanks for the review.
I updated the PR (pending functional testing).
Previously used hostnames are now pushed to aliases (http://man7.org/linux/man-pages/man5/hosts.5.html) and are restored if the charm option to manage /etc/hosts is disabled (admittedly the previously used hostname will not be restored correctly if there are multiple aliases already as the previous hostname is appended to the list of aliases - I could fix that if this is important but it is an edge case). A persistent store (unitdata kv) is used to remember the managed ip: hostname pairs - this is used to disable the feature after the relevant config option is set to false.

Pull-request updated, HEAD is now a578f6d977306fe51fc88858fe8775cbdb5b2850

Pull-request updated, HEAD is now dc092ea3ed785d338cd4b4063b3f2f4966d493c9

@Andrey-mp Pinged you there.
Also fixed 2 additional issues (see the commit message) and added more logging to track down the problem where one unit had only 2/3 hostnames although all events (joined and changed) for all (2) peer units ran for that unit.
I am doing another redeployment to see if I can reproduce that and see what is wrong (with more Juju and charm logging).

Pull-request updated, HEAD is now e5ab1cb5286d64728630e9fddb000db4f8090e7b

With https://github.com/Juniper/contrail-charms/commit/e5ab1cb5286d64728630e9fddb000db4f8090e7b I got to a good state in a functional test where all units had their /etc/hosts filled with all cluster ip:hostname pairs without any duplicates.
Hostnames appear on all machines after all controller-cluster-changed events fire.

i don't have any requests in the skype...
about the change - right now it become rather big and not so simple. But from the other hand it's isolated. Therefore it can be treated as blackbox and if it works for you then I can merge it.
But in general I suppose that logic can be simplified with:

store hostname in relation always. without checking is it enable in config or not. flag in config can be used just for switch to fill /etc/hosts or not. storing can be done in the same manner as unit-address. at the any point in time this list can be obtained from relation without storing in kv.
because hostname is rather unique and predefined - then working with /etc/hosts can be simplified. in update_charm_status func - after reading we can remove all lines where this hostname is present (either as hostname or in aliases). and then code can read current state from relation and form new content for /etc/hosts. if new content is not equal to previous then new file can be renamed.

If this work is urgent and you confirm that it works for you - please let me know and i'll merge it. Later the change can be re-worked.

Pull-request updated, HEAD is now d5b280282a71e464a1fe482eeae9c9a23a1ce17d

Yes, from the perspective of the project I am working on it is quite critical as:

OAM network interface is used for Juju communication;
One of the secondary interfaces of a node is used for control plane & MX communication;
Doing /etc/hosts management in a separate charm or a script introduces race conditions.

I managed to get to a deployment where contrail-status was good yesterday:
https://gist.github.com/dshcherb/7828b0704cc41c7f88f59ff6c4c689d1
So I think having it under a feature flag and using it to move forward is a workable solution until the docker image is fixed to use FQDNs.


Cluster grenade refactor and contra markings

About the PR

Cluster grenades essentially have two categories.

Ones that shoot projectiles (projectile grenades)
Ones that scatter entities that may potentially trigger themselves (scattering grenades)

I split it into two distinct systems to better separate the logic and fixed a few bugs.
Why / Balance

Fixes https://github.com/space-wizards/space-station-14/issues/27571
Fixes cluster grenades and clusterbanana type grenades not triggering when exploded
Fixes stingers and incendiaries type grenades not triggering when exploded
Fixes stacking stingers into stingers into stingers into stingers into stingers

Technical details

Clustergrenades only trigger as a result of their on-use timer. This means that when they were destroyed, nothing happened. I gave both new categories of grenades a damage trigger so that they can be properly chained like regular explosives.
More than half of the variables in the system were unused by projectile-type grenades, so separating the two into two different systems enables easier alteration of logic or behavior.
None of the actual behavior regarding how they function has changed, it's just been separated.

Scattering grenades and projectile grenades now have an abstract parent to make contra marking sane
Clusterbang, cluster banana peel, slipocalypse clustersoap, and foam dart grenade migrated to Scattering Grenades and proper contra marking
Stingers, incendiaries, and shrapnel grenades migrated to Projectile Grenades and proper contra marking

Media

https://private-user-images.githubusercontent.com/58439124/335451517-58b0a78b-48cb-4861-9459-8317323cdf7e.mp4?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjM4NDg3NzcsIm5iZiI6MTcyMzg0ODQ3NywicGF0aCI6Ii81ODQzOTEyNC8zMzU0NTE1MTctNThiMGE3OGItNDhjYi00ODYxLTk0NTktODMxNzMyM2NkZjdlLm1wND9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MTYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODE2VDIyNDc1N1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWMzMGUyZDY3NmI0ZWY2NzE1NjJhYTRmMzQ2ZDU4ZjRlMGM0YTFiNmMzNDMzMmMxMTcyNDhhZDI4OWU2YzQxOWImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.Wxrn3HrQTz_lrkifmx16C2U0EvXrKxcKbWic1-V2Juo
https://private-user-images.githubusercontent.com/58439124/335451529-2f9f4d29-1cd1-4fcc-a970-7ae466054ab9.mp4?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjM4NDg3NzcsIm5iZiI6MTcyMzg0ODQ3NywicGF0aCI6Ii81ODQzOTEyNC8zMzU0NTE1MjktMmY5ZjRkMjktMWNkMS00ZmNjLWE5NzAtN2FlNDY2MDU0YWI5Lm1wND9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MTYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODE2VDIyNDc1N1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTA4NzE4MWQ0NDBjNTJmYWMyZWY2MTg3YjhjMTM5ODQ0MDZiNmNmMDA5MmQxY2I0YjNiMzI0NDhiODZhNzVjMGImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.sn0_bozS2UE79JWXZcrguA4Uulprqw7u9wWgdsncsZg
https://private-user-images.githubusercontent.com/58439124/341185234-783f1f67-89f2-43bb-9623-166a194ded20.mp4?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjM4NDg3NzgsIm5iZiI6MTcyMzg0ODQ3OCwicGF0aCI6Ii81ODQzOTEyNC8zNDExODUyMzQtNzgzZjFmNjctODlmMi00M2JiLTk2MjMtMTY2YTE5NGRlZDIwLm1wND9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MTYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODE2VDIyNDc1OFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTcyMDMzMmI1ZTVhZmM5YjhjZWEwOGYyMWRiOWE2OGYxNjQzYjgwZTEyZmVjZjg1MWY5ZDY0ZDVhNzRmN2RiNmMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.emCSM4pKjC04OB4GUdTZqN3VBLnMgZ-UPn-cI680J-A
Requirements

[x] I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

ClusterGrenadeComponent/System were removed, replaced by ProjectileGrenadeComponent/System and ScatteringGrenadeComponent/System.
Changelog

:cl:

fix: Bombs like stingers and clustergrenades now trigger when destroyed due to damage.

this is currently possible on live:
https://cdn.discordapp.com/attachments/1191299997489188916/1266110532729966703/Base_Profile_2024.07.25_-_<IP_ADDRESS>.mp4?ex=66c0f5d2&is=66bfa452&hm=7a27f8ae6053b5d3de74e74d110b48a7365c8f7a936c5f78586dce5d8b00fccd&

I think the stinger hit the nukies boss

900 stingers in a single stinger grenade is probably capable of crashing a server
https://cdn.discordapp.com/attachments/1295923728793866332/1301611809282719824/stinger_grenade.mp4?ex=67509d76&is=674f4bf6&hm=2a6c24eab300c7d9c6287c667a6924fb059d199c2cceb569efdbe4b6b38fc5eb&

Thanks for this! Just a few things from me
Also, during my tests I noted that when projectile grenades, like stingers, are triggered it causes a whole bunch of errors because the meta data component on the grenade can't be resolved. This is likely because it got deleted too early. So that needs to be addressed as well

because the bullet considers the grenade shooting it the "gun" and the grenade gets deleted so there is technically no gun, yeah

Thanks for this! Just a few things from me
Also, during my tests I noted that when projectile grenades, like stingers, are triggered it causes a whole bunch of errors because the meta data component on the grenade can't be resolved. This is likely because it got deleted too early. So that needs to be addressed as well

because the bullet considers the grenade shooting it the "gun" and the grenade gets deleted so there is technically no gun, yeah

Are you able to fix it? All those errors cause noticeable lag

I'm pretty sure this is the same as this bug already happening on master
#32642

I'm pretty sure this is the same as this bug already happening on master #32642

Yeah, it's the same issue

https://github.com/user-attachments/assets/bd42933c-84c8-47ca-8273-ce5698888ff0

looks pretty good

https://github.com/user-attachments/assets/5e0d6d74-e48b-42a3-b776-a458ae9f75c1

It doesn't look like the changes to RequireProjectileTargetSystem.cs have stopped the errors when projectile grenades detonate, unfortunately. I had a go at fixing it, but I couldn't make any progress either

It doesn't look like the changes to RequireProjectileTargetSystem.cs have stopped the errors when projectile grenades detonate, unfortunately. I had a go at fixing it, but I couldn't make any progress either

it stopped the client-side errors that normally caused me lag at the very least

to anyone who's wondering what the issue is for the future
SharedGunSystem's ShootProjectile() sets the shooter to either the gun's EntityUid, or a nullable user EntityUid using Projectiles.SetShooter(). This will get set to our projectile grenade's EntityUid. The projectile grenade is deleted once triggered.
ProjectileComponent has an EntityUid? Shooter field that is AutoNetworked. This field is set to the now deleted projectile grenade's EntityUid, and that will cause the engine's attempt to automatically network the EntityUid to fail since it can't load the MetadataComponent from the now deleted EntityUid

I got a question, I've been attempting to make a grenade launcher that fires timed grenades in another server. Think this will help me out?

I got a question, I've been attempting to make a grenade launcher that fires timed grenades in another server. Think this will help me out?

that's exactly why I made this

I got a question, I've been attempting to make a grenade launcher that fires timed grenades in another server. Think this will help me out?

that's exactly why I made this change, so I could make the china-lake fire different types of ammo like that lol

THANK YOU. I can now give Delta's secborgs teargas and stingers instead of a pack injector

So, I have gotten this PR of mine all working, except for 1 thing, the grenades launched by my launcher do not start the timer. How canI go abotu fixing that?
https://github.com/DeltaV-Station/Delta-v/pull/2059


Blank new line. Do not merge.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci Please smoke test macOS platform


[MERGE] Merge branch 1.7

The conflicts are resolved in the last commit.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18757/
Test FAILed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/18758/
Test PASSed.

Merged build finished. Test PASSed.


Inital PR

Functionality LGTM, but I have some styling nitpicks.
I would suggest improving the comments -- generally, I try have comments supplement the code / describe what the line/block means in the context of the whole (if needed), not restate what the immediate action of the code is. Note that these are my opinions on comments -- everyone has different styles.
@ramereth thoughts on using the new style of Chefspec tests? They are slower but I feel they read much nicer.

I respectfully disagree on this, I think I will prune some of the comments as I went overboard on purpose. In general I think that comments should be pretty verbose about what is going on in the code so that people who are not familiar with the code can easily understand what is going on. When I started with ruby the syntax was weird, and even now the loop structure can sometimes be hard to keep track of. In the case of chef I also think that cookbooks do wildly different things and it can be good to be verbose so people can pick up the new topic easily. Plus the comments are highlighted and easy to ignore for people who don't need them.
But that's also just my preference as well I can change it in either direction.
@ramereth what do you think

Functionality LGTM, but I have some styling nitpicks.
I would suggest improving the comments -- generally, I try have comments supplement the code / describe what the line/block means in the context of the whole (if needed), not restate what the immediate action of the code is. Note that these are my opinions on comments -- everyone has different styles.
@ramereth thoughts on using the new style of Chefspec tests? They are slower but I feel they read much nicer.

I respectfully disagree on this, I think I will prune some of the comments as I went overboard on purpose. In general I think that comments should be pretty verbose about what is going on in the code so that people who are not familiar with the code can easily understand what is going on. When I started with ruby the syntax was weird, and even now the loop structure can sometimes be hard to keep track of. In the case of chef I also think that cookbooks do wildly different things and it can be good to be verbose so people can pick up the new topic easily. Plus the comments are highlighted and easy to ignore for people who don't need them.
But that's also just my preference as well I can change it in either direction.
@ramereth what do you think

@ramereth thoughts on using the new style of Chefspec tests? They are slower but I feel they read much nicer.

I'm torn on this as it is slower but that might change if we fix chefspec itself to make it faster.
I'd say in general, we should do all new tests using the newer format.

@ramereth thoughts on using the new style of Chefspec tests? They are slower but I feel they read much nicer.

I'm torn on this as it is slower but that might change if we fix chefspec itself to make it faster.
I'd say in general, we should do all new tests using the newer format.

I would suggest improving the comments -- generally, I try have comments supplement the code / describe what the line/block means in the context of the whole (if needed), not restate what the immediate action of the code is. Note that these are my opinions on comments -- everyone has different styles.

I respectfully disagree on this, I think I will prune some of the comments as I went overboard on purpose. In general I think that comments should be pretty verbose about what is going on in the code so that people who are not familiar with the code can easily understand what is going on. When I started with ruby the syntax was weird, and even now the loop structure can sometimes be hard to keep track of. In the case of chef I also think that cookbooks do wildly different things and it can be good to be verbose so people can pick up the new topic easily. Plus the comments are highlighted and easy to ignore for people who don't need them.
But that's also just my preference as well I can change it in either direction.
@ramereth what do you think

I almost commented on the comments being a little excessive or the formatting was not quite what I was looking for. I think if you could trim down the use of ### and just focus on the comments themselves, that would be better. Also, if it's obvious what it's doing (such as the case statements are for versions of the OS), those aren't needed IMHO.
Go ahead and do a little trimming and I'll provide some feedback.

I would suggest improving the comments -- generally, I try have comments supplement the code / describe what the line/block means in the context of the whole (if needed), not restate what the immediate action of the code is. Note that these are my opinions on comments -- everyone has different styles.

I respectfully disagree on this, I think I will prune some of the comments as I went overboard on purpose. In general I think that comments should be pretty verbose about what is going on in the code so that people who are not familiar with the code can easily understand what is going on. When I started with ruby the syntax was weird, and even now the loop structure can sometimes be hard to keep track of. In the case of chef I also think that cookbooks do wildly different things and it can be good to be verbose so people can pick up the new topic easily. Plus the comments are highlighted and easy to ignore for people who don't need them.
But that's also just my preference as well I can change it in either direction.
@ramereth what do you think

I almost commented on the comments being a little excessive or the formatting was not quite what I was looking for. I think if you could trim down the use of ### and just focus on the comments themselves, that would be better. Also, if it's obvious what it's doing (such as the case statements are for versions of the OS), those aren't needed IMHO.
Go ahead and do a little trimming and I'll provide some feedback.

@ramereth how is this?

@ramereth how is this?

@TheREK3R next step is to do !bump major which will bump to a major 1.0.0 release but not try and create a PR in chef-repo. The reason is the fact that we don't have logic which can automatically add new cookbooks to chef-repo. It has to be done manually.
Once you bump this, please make a new PR manually in chef-repo which adds osl-repo to it and then you can work on updating all the other PRs.

@TheREK3R next step is to do !bump major which will bump to a major 1.0.0 release but not try and create a PR in chef-repo. The reason is the fact that we don't have logic which can automatically add new cookbooks to chef-repo. It has to be done manually.
Once you bump this, please make a new PR manually in chef-repo which adds osl-repo to it and then you can work on updating all the other PRs.

!bump major

!bump major

Jenkins has merged this PR into master and has automatically performed a major-level version bump to v1.0.0.  Have a nice day!

Jenkins has merged this PR into master and has automatically performed a major-level version bump to v1.0.0.  Have a nice day!


AST: Don't forget to check ProtocolCompositionType::hasExplicitAnyObject() in TypeMatcher

@swift-ci Please smoke test

This fixes a crash regression from https://github.com/apple/swift/issues/49200 but the diagnostic still isn't great.


Using mod() in line 50:  pylibs/Scripts/gen_hycom_3Dth.py

   Hi @wzhengui

I have a quick look at your pylibs repo. It  looks cool. Thanks for sharing it :)
It seems to me that we don't need to use mod on line 50:  sx=mod(array(C.variables['lon'][:])+360,360)-360 when the latitude is positive.  This is the case for Australia/NewZealand.
For example:
I have: sx  = array(C.variables['lon'][:])
sx =[143.04003906<PHONE_NUMBER>2<PHONE_NUMBER>7<PHONE_NUMBER><PHONE_NUMBER>5
143.43994141<PHONE_NUMBER>3<PHONE_NUMBER>9<PHONE_NUMBER>4<PHONE_NUMBER>7
143.83996582<PHONE_NUMBER>5<PHONE_NUMBER>5605<PHONE_NUMBER>8
144.23999023<PHONE_NUMBER>6<PHONE_NUMBER>1<PHONE_NUMBER>7<PHONE_NUMBER>9
144.64001465<PHONE_NUMBER><PHONE_NUMBER>3<PHONE_NUMBER>8<PHONE_NUMBER>4
145.04003906<PHONE_NUMBER>2<PHONE_NUMBER>7<PHONE_NUMBER><PHONE_NUMBER>5
145.43994141<PHONE_NUMBER>3<PHONE_NUMBER>9<PHONE_NUMBER>4<PHONE_NUMBER>7
145.83996582<PHONE_NUMBER>5<PHONE_NUMBER>5605<PHONE_NUMBER>8
146.23999023<PHONE_NUMBER>6<PHONE_NUMBER>1]
If I use: sx=mod(array(C.variables['lon'][:])+360,360)-360
sx = [-216.95996094 -216.88000488 -216.80004883 -216.7199707  -216.64001465
-216.56005859 -216.47998047 -216.40002441 -216.32006836 -216.23999023
-216.16003418 -216.07995605 -216.         -215.92004395 -215.83996582
-215.76000977 -215.67993164 -215.59997559 -215.52001953 -215.43994141
-215.35998535 -215.2800293  -215.19995117 -215.11999512 -215.04003906
-214.95996094 -214.88000488 -214.80004883 -214.7199707  -214.64001465
-214.56005859 -214.47998047 -214.40002441 -214.32006836 -214.23999023
-214.16003418 -214.07995605 -214.         -213.92004395 -213.83996582
-213.76000977 -213.67993164 -213.59997559]
Cheers,
Huy

Hi Huy:
Thank you for reporting this bug to me. I just fixed it. I noticed this bug
some time ago, and got it fixed in gen_hycom_hotstart.py, but forgot this
script.
Thanks,
Zhengui
On Mon, Aug 23, 2021 at 6:55 PM Huy Quang Tran @.***>
wrote:

Hi @wzhengui
I have a quick look at your pylibs repo. It looks cool. Thanks for sharing
it :)
It seems to me that we don't need to use mod on line 50:
sx=mod(array(C.variables['lon'][:])+360,360)-360 when the latitude is
positive. This is the case for Australia/NewZealand.
For example:
I have: sx = array(C.variables['lon'][:])
sx =[143.04003906<PHONE_NUMBER>2<PHONE_NUMBER>7<PHONE_NUMBER><PHONE_NUMBER>5
143.43994141<PHONE_NUMBER>3<PHONE_NUMBER>9<PHONE_NUMBER>4<PHONE_NUMBER>7
143.83996582<PHONE_NUMBER>5<PHONE_NUMBER>5605<PHONE_NUMBER>8
144.23999023<PHONE_NUMBER>6<PHONE_NUMBER>1<PHONE_NUMBER>7<PHONE_NUMBER>9
144.64001465<PHONE_NUMBER><PHONE_NUMBER>3<PHONE_NUMBER>8<PHONE_NUMBER>4
145.04003906<PHONE_NUMBER>2<PHONE_NUMBER>7<PHONE_NUMBER><PHONE_NUMBER>5
145.43994141<PHONE_NUMBER>3<PHONE_NUMBER>9<PHONE_NUMBER>4<PHONE_NUMBER>7
145.83996582<PHONE_NUMBER>5<PHONE_NUMBER>5605<PHONE_NUMBER>8
146.23999023<PHONE_NUMBER>6<PHONE_NUMBER>1]
If I use: sx=mod(array(C.variables['lon'][:])+360,360)-360
sx = [-216.95996094 -216.88000488 -216.80004883 -216.7199707 -216.64001465
-216.56005859 -216.47998047 -216.40002441 -216.32006836 -216.23999023
-216.16003418 -216.07995605 -216. -215.92004395 -215.83996582
-215.76000977 -215.67993164 -215.59997559 -215.52001953 -215.43994141
-215.35998535 -215.2800293 -215.19995117 -215.11999512 -215.04003906
-214.95996094 -214.88000488 -214.80004883 -214.7199707 -214.64001465
-214.56005859 -214.47998047 -214.40002441 -214.32006836 -214.23999023
-214.16003418 -214.07995605 -214. -213.92004395 -213.83996582
-213.76000977 -213.67993164 -213.59997559]
Cheers,
Huy
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/wzhengui/pylibs/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFFROBKASVW5HDMVC7HJS7TT6LGXHANCNFSM5CVTG56A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

No worries @wzhengui
Have you also changed line 34:  sx=mod(array(C.variables['lon'][:])+360,360)-360   in Scripts/gen_hycom_hotstart.py?
Cheers,
Huy

It was changed before.  it should work as long as lxi and sx are
consistent. Zhengui
On Mon, Aug 23, 2021 at 8:00 PM Huy Quang Tran @.***>
wrote:

No worries @wzhengui https://github.com/wzhengui
Have you also changed line 34:
sx=mod(array(C.variables['lon'][:])+360,360)-360 in
Scripts/gen_hycom_hotstart.py?
Cheers,
Huy
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/wzhengui/pylibs/issues/1#issuecomment-904214562, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AFFROBMT2EZHMAA3K363IZLT6LOH7ANCNFSM5CVTG56A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

No worries mate.  Cheers, Huy.


chore: just consider crypto exists

I think we don't need to import anything.
$ node
Welcome to Node.js v18.19.0.
Type ".help" for more information.
> crypto.getRandomValues
[Function: getRandomValues]

And, it's in your window too:

Clicked around in the example dApp, everything (client- and server-side) seem to work.


Add wallet button content description shows "Add Token", it could be "Add Wallet"

Hi @seabornlee I see; thanks for the heads up, the 'add token' is indeed incorrect when viewing the full text.

let me try to fix this issue.


Screen Component colors

What's going on?
When using the Screen component, the default is white text on white background which makes it seem like the page is blank.
Steps to reproduce

ignite generate screen Example
Navigate to the Example screen

Results
Actual

Expected

or

Closed by latest master direct updates (accident as I thought that was disabled)


error：Library objects cannot exceed 65,536，win10 + TensorFlowGPU

System information:
· Have I written custom code (as opposed to using a stock example script provided in TensorFlow):  No
· OS Platform and Distribution (e.g., Linux Ubuntu 16.04):  Win10-x64
· TensorFlow installed from (source or binary): git clone https://github.com/tensorflow/tensorflow.git
· TensorFlow version (use command below):  r1.4, r1.5, r1.6  r1.7 and r1.8,  command :
v1.8's command : git checkout -b v1.8 -f origin/r1.8
v1.7's command : git checkout -b v1.7 -f origin/r1.7
v1.6's command : git checkout -b v1.6 -f origin/r1.6
and so on include v1.4 and v1.5
· Python version:  Anaconda3 - python3.6
· Bazel version (if compiling from source):  I used CMAKE 3.11.1
· GCC/Compiler version (if compiling from source):  Visual Studio 2015( VS15' MSBuild)
· CUDA/cuDNN version:  CUDA9.0,   cudnn-9.0-win10-7.1
· GPU model and memory: GTX-860m with 2Gb Memory
Exact command to reproduce:
"
D:\ProgramData\tensorflow\tensorflow\contrib\cmake\build> cmake .. -A x64 -DCMAKE_BUILD_TYPE=Debug -DSWIG_EXECUTABLE=D:/soft/TensorflowSoft/swigwin-3.0.12/swig.exe -DPYTHON_EXECUTABLE=D:/ProgramData/Anaconda3/python.exe -DPYTHON_LIBRARIES=D:/ProgramData/Anaconda3/libs/python36.lib -Dtensorflow_ENABLE_GPU=ON -DCUDNN_HOME="D:\soft\TensorflowSoft\cudnn" -G "Visual Studio 14 2015"
D:\ProgramData\tensorflow\tensorflow\contrib\cmake\build> set PreferredToolArchitecture=x64
D:\ProgramData\tensorflow\tensorflow\contrib\cmake\build> MSBuild /p:Configuration=Release ALL_BUILD.vcxproj
"
Describe the problem :
I build TensorFlow-CPU-r1.8 successfully (win10-x64 + Anaconda3-python3.6 + VS2017(not VS2015) +  tensorflow1.8 + cmake3.11.1 + SwigWin3.0.12).
But when I build tensorflow-GPU version(both tensorflow-r1.7 and r1.8), the only error has occurred: The library objects cannot exceed 65,536. (If I use VS2017, it shows error: " the compiler is not supported for CUDA 9.0" , so I switch Visual Studio version to VS2015, and CMAKE command is work successfully.)
After that, I switched to lower versions TensorFlow-r1.6 to TensorFlow-r1.5, but Link error occurred：
“libprotobufd.lib(text_format.obj) : error LNK2019: unresolved external symbol __std_reverse_trivially_swappable_8 referenced in function "void _
_cdecl std::_Reverse_unchecked1<class google::protobuf::Message const * *>(class google::protobuf::Message const * * const,class google::protobuf:
:Message const * * const,struct std::integral_constant<unsigned __int64,8>)" (??$_Reverse_unchecked1@PEAPEBVMessage@protobuf@google@@@std@@YAXQEAP
EBVMessage@protobuf@google@@0U?$integral_constant@_K$07@0@@Z) [D:\tf\tensorflowGPU\tensorflow\contrib\cmake\build\proto_text.vcxproj]
libprotobufd.lib(wire_format.obj) : error LNK2001: unresolved external symbol __std_reverse_trivially_swappable_8 [D:\tf\tensorflowGPU\tensorflo
w\contrib\cmake\build\proto_text.vcxproj]
D:\tf\tensorflowGPU\tensorflow\contrib\cmake\build\Debug\proto_text.exe : fatal error LNK1120: 1 unresolved externals [D:\tf\tensorflowGPU\tenso
rflow\contrib\cmake\build\proto_text.vcxproj]”
I don't know how to solve those errors...

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

I have updated my issue, @tensorflowbutler , and thank you very much for helping me !

Marking this as community support, because we don't support debug builds on Windows.
/CC @gunan, who was looking at the symbol limit recently, and may have some suggestions.


migrate to aux window service for issue reporter

build here so you can download and test (due to services, stuff moving around, just in case ya know)
setting to control is issueReporter.experimental.auxWindow, enable by default for everything except stable

👋 I am back, are there any outstanding questions for me to comment on on this PR? I glanced over the changes and filed https://github.com/microsoft/vscode/issues/224051 as a follow up.


Wrong Caret Color

Bug, feature request, or proposal:
Caret color of input and textarea is not correct in all browsers and systems.
What is the expected behavior?
Caret color of input and textarea should behave the same in all browsers and systems.
What is the current behavior?
When one specifies the color of the mat-form-field and uses matInput directive, the placeholder and underline have the right color but the caret does not respect the color change in all browsers and systems.
Namely:

Microsoft Edge, Windows 10 - caret keeps the default color
Safari, Mac - caret keeps the default color
Safari, iPad - caret has some strange blue color
Safari, iPhone - caret has some strange blue color

What are the steps to reproduce?
Here is a Stackblitz with three inputs (in primary, accent, and warn colors) and three textareas (in primary, accent, and warn colors) . Click into the components and observe the caret color in above-mentioned browsers.
https://stackblitz.com/edit/angular-jmgqlb
What is the use-case or motivation for changing an existing behavior?
Caret should look the same on all browsers, devices, and operating systems.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
See above.
Is there anything else we should know?
No.

This is the expected behavior, because the caret-color property isn't supported by all browsers. We put it in since it's more of a progressive enhancement than an actual usability feature.


can not retweet

When I try to retweet, I get an error and cannot do it.
Error message
Failed: Retweet - An unknown error occurred. Please try again shortly.

same bro

Known issues:
Retweeting doesn't work
Deleting doesn't work
Replies don't show properly
Let's just sit tight and hope they fix the problem.

maybe twitter is down


net, net/http, net/http/httptest: HTTP GET on local HTTP server fails with "fetch failed" on js/wasm with Node.js 18

Some Go packages use a local HTTP server in examples. To make these work, the js/wasm port includes:
https://github.com/golang/go/blob/bae7d772e800207ed764b70a9e5963f0c1e8f0aa/src/net/net_fake.go#L5
It works okay with Node.js 14, but fails with Node.js 18. Without it working, tests/examples in packages like compress/gzip and various others fail. This is the tracking issue this problem.
Tested at tip (79cdecc8522e37d2eac5592c12459cd95ff92171) with local patches to work around #56860 and #57516. Those issues will need to resolved first; I'm just reporting this finding earlier since I came across it while looking briefly into what's needed to make all.bash pass with Node 18.
It can be reproduced with GOOS=js GOARCH=wasm ./all.bash, or GOOS=js GOARCH=wasm go test -run='Example_compressingReader' compress/gzip, or with this more standalone program:
package main

import (
	"flag"
	"fmt"
	"io"
	"log"
	"net/http"
	"net/http/httptest"
	"os"
)

func main() {
	flag.Parse()

	err := run()
	if err != nil {
		log.Fatalln(err)
	}
}

func run() error {
	ts := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, req *http.Request) {
		fmt.Fprintln(w, "ok from httptest")
	}))
	defer ts.Close()
	fmt.Println("started a test HTTP server at:", ts.URL)

	resp, err := http.Get(ts.URL)
	if err != nil {
		return err
	}
	defer resp.Body.Close()
	fmt.Println(resp.Status)
	_, err = io.Copy(os.Stdout, resp.Body)
	return err

	// Output with Node.js 14:
	// 200 OK
	// ok from httptest

	// Output with Node.js 18:
	// started a test HTTP server at: http://<IP_ADDRESS>:1
	// (node:52134) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
	// (Use `node --trace-warnings ...` to show where the warning was created)
	// 2023/01/04 16:40:18 Get "http://<IP_ADDRESS>:1": net/http: fetch() failed: fetch failed
	// exit status 1
}

CC @golang/js, @golang/wasm, @johanbrandhorst.

Also CC @Pryz, @evanphx who've recently joined as Wasm maintainers in #57968. (Thanks!)
Investigating and resolving this issue will help unblock progress on #57614.

This is probably related to the new "experimental" fetch functionality in Node 18: https://nodejs.org/de/blog/announcements/v18-release-announce/#fetch-experimental.

OK I've confirmed that this is due to the introduction of the fetch API in Node 18. In Node 14, fetch was not defined
https://github.com/golang/go/blob/1e12c63aacce3749c4fb649477f9b44f74ebf550/src/net/http/roundtrip_js.go#L45
so we would short circuit the Fetch API roundtripper
https://github.com/golang/go/blob/1e12c63aacce3749c4fb649477f9b44f74ebf550/src/net/http/roundtrip_js.go#L55-L57
This falls back to the fake network implementation in  net_fake.go.
However, with Node 18, all of a sudden fetch is defined, so while on the server side we set up a fake in-memory listener, on the client side we try to make a request to the real local address. I see a few ways forward:

Add a special case to disable the fetch API on NodeJS and reintroduce the roundtripper short circuit. We could use the new osinfo.Version() to determine the runtime environment (or just call to process directly).
Implement a real NodeJS based socket syscall interface so we can run proper networking tests for webassembly architectures (when run under NodeJS). This would probably be a lot of work. It's also not great because Go wasm on NodeJS is not supposed to be special, and we'd have to introduce runtime checks through the codebase to decide whether to lean on NodeJS APIs or return unimplemented errors. It's almost a js+node/wasm at that point.

I'm leaning towards option 1 for now as it means we can migrate to Node 18 with few changes and no net new functionality. At a later stage we could introduce a NodeJS based socket interface if we wanted to, and then reenable fetch for NodeJS. I will prepare a CL for option 1.
Would love @neelance's thoughts on a NodeJS based socket syscall interface, I assume the reason we didn't introduce one originally was because there was no fetch in NodeJS at the time.
Another note I want to quickly make here is that the NodeJS fetch implementation disallows the use of certain ports directly on the client (per the Fetch API spec). If we introduce fetch for NodeJS we have to ensure the server side tests don't use one of the blocked ports.

Thanks for investigating this and figuring out the problem.

Would love @neelance's thoughts on a NodeJS based socket syscall interface, I assume the reason we didn't introduce one originally was because there was no fetch in NodeJS at the time.

I asked Richard about that fairly recently, and he confirmed that the main reason the fake socket path was used is because that was the easiest path forward at the time. Back then, the NaCL port had the fake socket code implemented, and Node didn't support fetch. By now, with NaCL port being long gone and Node supporting fetch, it might be net simpler to start using fetch, but that is fine to investigate and consider later. I think starting with just disabling fetch with Node 18 as done in CL 463976 is good as the first step to resolve the immediate issue. Thanks.

I have this issue. Is there any work around for the issue for someone using the http package?


Some times can't add node in visualshader editor

Godot version
v4.2.beta2.official [f8818f85e]
System information
Windows 10, 64bit
Issue description
Some times can't add node in visualshader editor
Steps to reproduce

Open a VisualShader file for edit.
Click the Add Node... button, it will popup menu, it is OK.
Direct close the menu.
Clikd the Add Node... again, the menu can't popup.

Minimal reproduction project
/

I can't reproduce this on 4.2.beta f8818f85e (Linux). I've tried both single-window mode enabled and disabled.

Oh, I'm found it, the menu was in backgound.

How are you closing the Add Node window? Are you pressing Escape or clicking outside? Clicking outside doesn't close the window for me.

clicking outside

Happened to me too now, pretty confusing, if you started adding a node and then didn't add one, it would make sense to either automatically close the small window when you change the window back to Godot\another program, or to bring this window back to focus if you click add node and it's already open.

Oh, I'm found it, the menu was in backgound.

Same for me, my pr fixes the problem, you can help test :)

The same fate seems to have occurred for my graph editor, which uses a similar popup. What happened to the "click outside to close" behavior?
I can set my dialog to exclusive too I guess, just a bit more annoying to aim for the close button.
I also noticed in some circumstances that this popup can now get stuck unresponsive, eventually blocking the whole editor as a result (so far resolving with alt/tab). I haven't found the pattern to make it happen though, but had it occur a few times.


0.1.0 changes for ranger_adabelief

Hi @juntang-zhuang , super excited to try the new improvements.
I saw that you did not updated the ranger version. Do you plan to add the improvements there too?

Hi, thanks for asking. Currently don't have a plan for a big change with the ranger version, will fix some small errors. I don't have much experience with ranger version, also the decoupled weight decay and rectification is turned on by default in ranger (these two defaults are modified in adabelief-pytorch), except the eps is set as 1e-5 in ranger. Do you have a feeling what is a good default value for eps in ranger-adabelief? Or any other ideas on potential improvements?

Hi,
I would recommend  setting  the default value of  'weight decoupling' to true.
Adam originally had coupled weight decay, but after this paper,
https://arxiv.org/abs/1711.05101  e.g. Pytorch introduced AdamW.
But there is no supporting evidence for any case where coupled weight
decay outperforms decoupled one, so even the default pytorch
changed to decoupled. Actually, not just changed the default,
they completely removed the option for the old one, making it backward incompatible.
(So yes, now Adam and AdamW is almost the same in Pytorch,
but in Adam the default decay is 0.)
If you know any counterexamples where coupling helps, please, show a link,
but otherwise i strongly recommend the default to be set to True.
(And obviously, for comparison the same weight decay scheme should be used.)

@dvolgyes Thanks for feedback, actually for all latest implementations the default for weight_decouple is True. BTW, since you mentioned decoupled decay is enabled in Adam in PyTorch, I checked the source code it seems Adam does not have much change, am I missing something? Could you specify where in Adam of PyTorch is decoupled weight decay enabled? Thanks a lot

Hi,
It depend how you see it. Check out the documentation of Adam between version 1.5.1 and 1.6:
https://pytorch.org/docs/1.5.1/optim.html?highlight=adam#torch.optim.Adam
https://pytorch.org/docs/1.6.0/optim.html?highlight=adam#torch.optim.Adam
The old one was:
"Implements Adam algorithm.
It has been proposed in Adam: A Method for Stochastic Optimization."
The new one:
"Implements Adam algorithm.
It has been proposed in Adam: A Method for Stochastic Optimization. The implementation of the L2 penalty follows changes proposed in Decoupled Weight Decay Regularization."
I did not go into the details checking how they implemented it, but I should have.
Turned out, it is quite likely that the documentation is wrong, it suggests they updated it,
but they didn't, and they still use the old version without weight decoupling.
https://github.com/pytorch/pytorch/issues/42843
I still hold that I haven't seen any paper where the weight decoupling shows worse performance than the non-decoupled
version, but I take back my Pytorch suggestion, I was mislead by the documentation.
So my current view:

Adam uses coupled weight decay
the Adam documentation is wrong
weight decoupling seems  to be beneficial for all, I haven't seen counter-evidence

@dvolgyes Thanks a lot. It seems weird that the "source code" page for Adam in PyTorch 1,6 is
       grad = grad.add(p, alpha=group['weight_decay'])```
Then it's not decoupled weight decay. Quite weird, I guess the document page is wrong

"Code never lies, comments sometimes do." -- Ron Jeffries
:)
Even worse, the bug was discovered before 1.7, but it might be that even 1.7.1 will be released without it.
Anyway, you code was always correct, but I am glad that I could convince you to change the default.


Exception: Could not find module! lsasrv.dll

INFO:root:Parsing file work.dmp
INFO:pypykatz:===== BASIC INFO. SUBMIT THIS IF THERE IS AN ISSUE =====
INFO:pypykatz:pypyKatz version: 0.4.9
INFO:pypykatz:CPU arch: X64
INFO:pypykatz:OS: Windows Server 2012 R2
INFO:pypykatz:BuildNumber: 9600
INFO:pypykatz:MajorVersion: 6
INFO:pypykatz:MSV timestamp: 0
INFO:pypykatz:===== BASIC INFO END =====
ERROR:root:Error while parsing file work.dmp
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pypykatz/pypykatz.py", line 261, in get_lsa
lsa_dec = LsaDecryptor.choose(self.reader, lsa_dec_template, self.sysinfo)
File "/usr/lib/python3/dist-packages/pypykatz/lsadecryptor/lsa_decryptor.py", line 20, in choose
return LsaDecryptor_NT6(reader, decryptor_template, sysinfo)
File "/usr/lib/python3/dist-packages/pypykatz/lsadecryptor/lsa_decryptor_nt6.py", line 22, in init
self.acquire_crypto_material()
File "/usr/lib/python3/dist-packages/pypykatz/lsadecryptor/lsa_decryptor_nt6.py", line 26, in acquire_crypto_material
sigpos = self.find_signature()
File "/usr/lib/python3/dist-packages/pypykatz/lsadecryptor/lsa_decryptor_nt6.py", line 44, in find_signature
fl = self.reader.find_in_module('lsasrv.dll', self.decryptor_template.key_pattern.signature, find_first = True)
File "/usr/lib/python3/dist-packages/minidump/minidumpreader.py", line 272, in find_in_module
t = self.reader.search_module(module_name, pattern, find_first = find_first, reverse_order = reverse_order, chunksize = self.segment_chunk_size)
File "/usr/lib/python3/dist-packages/minidump/minidumpreader.py", line 337, in search_module
raise Exception('Could not find module! %s' % module_name)
Exception: Could not find module! lsasrv.dll
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pypykatz/lsadecryptor/cmdhelper.py", line 230, in run
mimi = pypykatz.parse_minidump_file(args.memoryfile, packages=args.packages)
File "/usr/lib/python3/dist-packages/pypykatz/pypykatz.py", line 150, in parse_minidump_file
raise e
File "/usr/lib/python3/dist-packages/pypykatz/pypykatz.py", line 146, in parse_minidump_file
mimi.start(packages)
File "/usr/lib/python3/dist-packages/pypykatz/pypykatz.py", line 350, in start
self.lsa_decryptor = self.get_lsa()
File "/usr/lib/python3/dist-packages/pypykatz/pypykatz.py", line 267, in get_lsa
raise Exception('All detection methods failed.')
Exception: All detection methods failed.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pypykatz/pypykatz.py", line 261, in get_lsa
lsa_dec = LsaDecryptor.choose(self.reader, lsa_dec_template, self.sysinfo)
File "/usr/lib/python3/dist-packages/pypykatz/lsadecryptor/lsa_decryptor.py", line 20, in choose
return LsaDecryptor_NT6(reader, decryptor_template, sysinfo)
File "/usr/lib/python3/dist-packages/pypykatz/lsadecryptor/lsa_decryptor_nt6.py", line 22, in init
self.acquire_crypto_material()
File "/usr/lib/python3/dist-packages/pypykatz/lsadecryptor/lsa_decryptor_nt6.py", line 26, in acquire_crypto_material
sigpos = self.find_signature()
File "/usr/lib/python3/dist-packages/pypykatz/lsadecryptor/lsa_decryptor_nt6.py", line 44, in find_signature
fl = self.reader.find_in_module('lsasrv.dll', self.decryptor_template.key_pattern.signature, find_first = True)
File "/usr/lib/python3/dist-packages/minidump/minidumpreader.py", line 272, in find_in_module
t = self.reader.search_module(module_name, pattern, find_first = find_first, reverse_order = reverse_order, chunksize = self.segment_chunk_size)
File "/usr/lib/python3/dist-packages/minidump/minidumpreader.py", line 337, in search_module
raise Exception('Could not find module! %s' % module_name)
Exception: Could not find module! lsasrv.dll
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pypykatz/lsadecryptor/cmdhelper.py", line 230, in run
mimi = pypykatz.parse_minidump_file(args.memoryfile, packages=args.packages)
File "/usr/lib/python3/dist-packages/pypykatz/pypykatz.py", line 150, in parse_minidump_file
raise e
File "/usr/lib/python3/dist-packages/pypykatz/pypykatz.py", line 146, in parse_minidump_file
mimi.start(packages)
File "/usr/lib/python3/dist-packages/pypykatz/pypykatz.py", line 350, in start
self.lsa_decryptor = self.get_lsa()
File "/usr/lib/python3/dist-packages/pypykatz/pypykatz.py", line 267, in get_lsa
raise Exception('All detection methods failed.')
Exception: All detection methods failed.

Thanks for the bug report. The current version of pypykatz is 0.5.8 whilst yous is 0.4.9. A lot has happened since then :)
I believe this issue will go away if you use the latest version.

ahh okay thanks!

Did it solve your issue?

yeah, it did. also, a suggestion, could you make it possible to add, PPL bypass, to pypykatz, mainly for windows 2012?, The Userland exploit, doesn't work on windows 2012, Thanks =)

I'm glad it solved the issue.
PPL and other bypasses and exploits are not the main goal of this project at the moment, I'd recommend using other tools to perform the dumping.


Stuck in Creating server...

Stuck in Creating server...
python 3.11 and used the start.cmd

worked with python 3.9


Not updated to 1.16

While I know it's not really an issue, I'd still like a version for 1.16(.5). Pretty please?

https://github.com/Create-Fabric/Create-Refabricated/blob/b4e86ed1b4b4776f8e59b95d0da3990059053a4e/gradle.properties#L7

Oh.
Is there a release for it?

The port is currently incomplete and is lacking in functionality. If you want to test it or contribute yourself, compile it from source.

Cool. Sorry.
How I wish I could figure out how to compile.


Dark theme ?

Hi, is the dark mode options available ?

You should be able to use it as documented here: https://tailwindcss.com/docs/dark-mode


delete temp file on validation fail

Hi, is there a way to automatically delete the temp stored file if any of the other fields of the form fail validation ?
I understand there is the expiration setting and a cron can be set, but it puts friction to the process
Thanks

@clickanidea Unfortunately no. I intentionally wanted the files to exist to help me in testing or understanding my team’s intention. Also you can check for validation fails and call the delete method manually to clear up the files if any other field fails.

Thanks


Uncaught TypeError: undefined is not a function

[Enter steps to reproduce below:]

Select Upload Current File in context menu

Atom Version: 0.206.0
System: Mac OS X 10.10.3
Thrown From: SFTP-deployment package, v1.0.0
Stack Trace
Uncaught TypeError: undefined is not a function
At /Users/marcoslh/.atom/packages/SFTP-deployment/lib/observers/MessageObserver.js:47

TypeError: undefined is not a function
  at showLoader (/Users/marcoslh/.atom/packages/SFTP-deployment/lib/observers/MessageObserver.js:47:21)
  at MessageObserver.notify (/Users/marcoslh/.atom/packages/SFTP-deployment/lib/observers/MessageObserver.js:73:13)
  at /Users/marcoslh/.atom/packages/SFTP-deployment/lib/DeploymentManager.js:49:18
  at Array.forEach (native)
  at DeploymentManager.notifyObservers (/Users/marcoslh/.atom/packages/SFTP-deployment/lib/DeploymentManager.js:48:20)
  at atom-workspace.DeploymentManager.uploadCurrentFile (/Users/marcoslh/.atom/packages/SFTP-deployment/lib/DeploymentManager.js:215:10)
  at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app.asar/src/command-registry.js:238:29)
  at CommandRegistry.handleCommandEvent (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61)
  at CommandRegistry.module.exports.CommandRegistry.dispatch (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app.asar/src/command-registry.js:153:19)
  at [object Object].jQuery.fn.trigger (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app.asar/src/space-pen-extensions.js:64:23)
  at EventEmitter.<anonymous> (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:75:67)
  at emitTwo (events.js:87:13)
  at EventEmitter.emit (events.js:169:7)
  at EventEmitter.ipc.sendSync (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/atom.asar/renderer/api/lib/ipc.js:21:31)
  at BrowserWindow.RemoteMemberFunction [as emit] (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/atom.asar/renderer/api/lib/remote.js:110:29)
  at ContextMenuManager.module.exports.ContextMenuManager.showForEvent (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app.asar/src/context-menu-manager.js:170:31)
  at HTMLDocument.<anonymous> (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:148:33)
  at HTMLDocument.handler (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app.asar/src/space-pen-extensions.js:112:34)
  at HTMLDocument.jQuery.event.dispatch (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app.asar/node_modules/space-pen/vendor/jquery.js:4681:9)
  at HTMLDocument.elemData.handle (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app.asar/node_modules/space-pen/vendor/jquery.js:4359:46)

Commands
  2x -2:02.6.0 core:save (atom-text-editor.editor.is-focused)
     -1:40.5.0 core:close (atom-text-editor.editor.is-focused)
     -1:39.2.0 symbols-view:toggle-file-symbols (atom-workspace.workspace.scrollbars-visible-always.theme-base16-tomorrow-dark-theme.theme-isotope-ui)
     -1:38.5.0 fuzzy-finder:toggle-file-finder (atom-workspace.workspace.scrollbars-visible-always.theme-base16-tomorrow-dark-theme.theme-isotope-ui)
     -1:34.4.0 editor:move-to-first-character-of-line (atom-text-editor.editor.mini.is-focused)
     -1:32.2.0 core:confirm (atom-text-editor.editor.mini.is-focused)
  2x -1:29.7.0 core:save (atom-text-editor.editor.is-focused)
     -0:57.9.0 core:close (atom-text-editor.editor.is-focused)
     -0:54.9.0 core:save (atom-text-editor.editor.is-focused)
     -0:53.9.0 core:close (atom-text-editor.editor.is-focused)
     -0:49.8.0 settings-view:open (atom-workspace.workspace.scrollbars-visible-always.theme-base16-tomorrow-dark-theme.theme-isotope-ui)
     -0:17.9.0 fuzzy-finder:toggle-file-finder (ul.list-inline.tab-bar.inset-panel)
     -0:15.6.0 core:move-down (atom-text-editor.editor.mini.is-focused)
     -0:14.9.0 core:confirm (atom-text-editor.editor.mini.is-focused)
     -0:12.8.0 find-and-replace:show (atom-text-editor.editor.is-focused)
     -0:11.3.0 core:confirm (atom-text-editor.editor.mini.is-focused)

Config
{
  "core": {
    "themes": [
      "isotope-ui",
      "base16-tomorrow-dark-theme"
    ]
  },
  "SFTP-deployment": {}
}

Installed Packages
# User
SFTP-deployment, v1.0.0
atom-django, v0.3.0
color-picker, v2.0.4
django-templates, v0.5.0
editorconfig, v1.0.0
emmet, v2.3.10
git-log, v0.4.1
git-tab-status, v1.9.2
isotope-ui, v2.4.0
linter, v0.12.6
linter-flake8, v1.4.2
linter-jscs, v1.12.0
linter-jshint, v0.1.6
linter-python-pep8, v0.2.0
node-debugger, v1.0.5
pigments, v0.4.4

# Dev
No dev packages

Hi,
I use this plugins for 2 months without problem but since some  days i have the same problem than you: "Uncaught TypeError: undefined is not a function".
Atom version : 0.207.0
Thrown From: SFTP-deployment package, v1.0.0
Someone kown a solution at this probleme ?
Thanks in advance,
Charles

Hi,
I used this plugin fine for months as well.  Now this error occurs.

+1

I'm getting the same issue as you all.
I am running 0.208.0
Anyone have any idea how to correct this, or an alternative to an SFTP upload?

Now I'm using https://atom.io/packages/remote-sync Don't have the time to
fix and propose a PR right now and I'm way to comfy with atom to change
editor
Saludos…
Marcos Luis Hernández
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
1151, Fairlake Tr. #1716.
Weston, FL. 33326
[website]: http://xiryvella.com/ http://xiryvella.com/
[github]: https://github.com/marcoslhc https://github.com/marcoslhc
[twitter]: @marcoslhc http://twitter.com/marcoslhc
[mobile]: +1<PHONE_NUMBER>
[info]: https://www.google.com/profiles/marcoslhc
https://www.google.com/profiles/marcoslhc
On Wed, Jun 10, 2015 at 10:36 AM, kupoback<EMAIL_ADDRESS>wrote:

I'm getting the same issue as you all.
I am running 0.208.0
Anyone have any idea how to correct this, or an alternative to an SFTP
upload?
—
Reply to this email directly or view it on GitHub
https://github.com/amoussard/sftp-deployment/issues/62#issuecomment-110776920
.

+1

:+1:

+1

var atomModule = require('atom');
atomModule.$
undefined

Undefinied is atomModule.$

I fixed this, and send pull request to author

Hi guys,
This issue is fixed.
Thank you all and especially @tuberiumf :)


Ensure Meta data (EXIF) is preserved when resizing images.

I've just been bitten by this one and had put in a support request to Craft about it without thinking that this plugin was the problem. It would good to resolve this, as it's quite a big issue with no solution, as you can't rotate images after they have been uploaded.

So sorry for the delay in this, but looking into the issue, it seems like Craft's native $image->saveAs method strips out EXIF data. Image Resizer relies on this function pretty heavily, and its something I would expect to be handled by default - but thats how it goes.
In any case, I've come to a solution of my own using Craft already included PelJpeg library, which can handle this better.
Check out the latest master.


Discussion: Custom Proxy traps

🚀 Feature Proposal
Allow setting custom Proxy traps
Motivation
I've been working on a personal project which uses Immer under the hood. The idea was to be able to define custom schemas in the following way:
(speudo-code)
const User = new ObjectType({ userName: String, age: Number }).actions({
  updateUser(u, a) { // <<< createDraft (updateUser bound to this = draft)
    this.userName = u // <<< userName setter checks if `u` is typeof string
    this.age = a // <<< age setter checks if `a` is typeof number and if isFinite
  } // <<< after execution, inner state = finalizeDraft
})
const data1 = User.toJSON() // Current state { userName: '', age: null }
User.updateUser('Bob', 22)
const data2 = User.toJSON() // Current state { userName: 'Bob', age: 22 }
User.userName // Bob
User.userName = 'Something' // throws, disallowed outside of actions since it's not a draft

The current limitation on Immer is that it doesn't allow to set custom Proxy traps, so I ended up duplicating Immer functionality around drafts to disallow extra-properties and to check first the type of the value before setting on the draft. Something like:
SchemaCheckerProxy -> DraftProxy

If there was a way to set custom traps in a way that doesn't interfere with Immer's traps, it'd be easier to implement things such as disallowing certain properties from being set or throwing a custom error or warning (e.g: Warning: deprecated prop "name", use "userName" instead), or using a normalize function before a value is handled by Immer (e.g: value.toUpperCase())
Example
I haven't thought yet as to how this could be better implemented within Immer, maybe something like:
const produce = createProduce(customTraps)
where customTraps could be:
const customTraps = {
  set(prop, value) {
    // example 1
    if (prop === 'something') console.log('Warning: deprecated prop "something"')
    // example 2
    if (prop === 'age' && typeof age !== 'number') throw new Error('....')
    // example 3
    if (prop === 'userName' && typeof value === 'string') return value.toUpperCase()
    // example 4
    if (prop === 'something' && value === null) return nothing()
  }
}

This could be handled within Immer as something like:
function set(state, prop, rawValue) {
        const value = getCustomTrapsSomehow().set(prop, rawValue) || rawValue
        /// ....
}

Custom traps could have a signature closer to Proxy traps and not giving them access to the draft or the state itself but instead just act as a middleware around prop & value before they are treated by Immer.
If anyone has better ideas of how this could be implemented without adding a new feature to Immer, that'd also be great :)

I see how you would like to use immer as vehicle for this, but I think it goes pretty far beyond the scope of what Immer is designed to do. I'd suggest to build your own proxy around drafts proxies instead, or do the validation / normalization afterwards with one of the many libraries that are available for that :).


Add webhookUrl optional property to the GitServer spec

Is your feature request related to a problem? Please describe.
We need to have the possibility to redefine the webhook URL. For example, GCP uses HTTPRoute instead of Ingress, and our current approach(webhook URL is taken from hardcoded reference to Ingress) doesn't work.
Describe the solution you'd like

We need to extend the GitServer specification by adding a new field called webhookUrl. This field will be used to define the webhook URL.
The codebase-operator should first check this new field; if it is not defined, then it should try to use the current approach to get the URL from the ingress.
If both methods fail to retrieve the URL, then the codebase-operator should fail with an error message stating that it cannot set the webhook URL.

Additional context
Add any other context or screenshots about the feature request here.

Done. GitServer example:
kind: GitServer
apiVersion: v2.edp.epam.com/v1
metadata:
  name: gitlab
spec:
  gitHost: gitlab.com
  httpsPort: 443
  nameSshKeySecret: ssh-key
  sshPort: 22
  gitProvider: gitlab
  webhookUrl: https://test.com:8080/webhook


[Feature] download different dub in one click

My idea is that while the initial configuration I set is for Japanese audio with Spanish subtitles, the episode later appears in Spanish-dubbed audio. However, when I try to download it, I still get the version with Japanese audio and Spanish subtitles. I would like to download the version without subtitles in Spanish-dubbed audio without having to change the program settings every time I want to do this. Additionally, I would like to concatenate the language into the filename. For example, instead of just 'Quality Assurance in Another World - S01E08 [480p],' I would like it to be 'Quality Assurance in Another World - S01E08 [480p] [JA-JP]' or '[ES-MX],' etc.

Nice idea. I'd like to see an option to download multiple audio tracks, say: Japanese and English etc (if available)

Just set Spanish as a default DUB with Jap? Or am I misunderstanding something?

still can't download, it always says "hardsub not available", what's the correct configuration to download jap+subs and spanish dubs at the same time without changing settings? filename changed but still need change settings like 3 weeks ago

download the downloader a second time setup the settings how you like and you don't have to change anything if you want to switch between your 2 configurations

still can't hardsubs is mandatory i always download as mp4 and softsubs not working in mp4 format


Password Displayed after Generation

Password Displayed after Generation
User Story
AS AN employee with access to sensitive data
I WANT to randomly generate a password that meets certain criteria
SO THAT I can create a strong password that provides greater security
Acceptance Criteria
GIVEN I need a new, secure password
WHEN the password is generated
THEN the password is either displayed in an alert or written to the page

This functionality has been tested and verified.  The password is displayed within the text box of the Generate Password application.


mat1jaczyyy.ApolloStudio version 1.8.8

[ ] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?

[ ] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

oh yeah, It didn't pop up for me in testing since I already have it installed


values for frequency registers calculated wrongly

second and third value are always 0.
This is because si4432.cpp line 29 is an integer division and fractional part gets lost. Result is 0 for freqcarrier in line 33.
quick fix: change "10" to "10.0" in line 29

better: force compiler to use type double by a cast:
double fPart = ((double)baseFrequencyMhz / (10 * (highBand + 1))) - 24;

Thanks for the report.
Fixed.


Doctor details: Doctor details Page

In this pull request, I was able to:

create a doctor's detail page.
use useParams hooks to identify doctor's id.
ensure the code is from of linter errors.

Thanks @vickymarz, for the warm feedback

Good job @Qoosim 👏🏾


[stable/cluster-overprovisioner] Add PodDisruptionBudget

Description
This PR will close the issue #173 .
I added the PodDisruptionBudget in the Helm Chart for cluster-overprovisioner.

Checklist

[x] Title of the PR starts with chart name (e.g. [stable/mychartname])
[ ] Github actions are passing

Hi @SatoruItaya, thanks for the PR, please check the instructions for contributions here: https://github.com/deliveryhero/helm-charts#contributing
You will need to bump the version of the chart and regen the docs.

@SatoruItaya Github actions seem to be unstable today, might need to wait some time


ISPN-11930 Rocks db converted to new SPI

https://issues.redhat.com/browse/ISPN-11930
This relies upon https://github.com/infinispan/infinispan/pull/8400

@wburns Reviewing would be much easier without the formatting change :cry:

@wburns Reviewing would be much easier without the formatting change 😢

Sorry unfortunately I started a new class and copied over as needed :(

Updated per comments and also cleaned up the purgeExpired method a bit more.

Also I am not sure what the extra added commits are. You should be able to see the diff from checking the specific commit.

Unfortunately all the methods around key optimizations cannot be done with this store due to expiration. I have addressed the indentation one for iterator though.

Unfortunately all the methods around key optimizations cannot be done with this store due to expiration.

Eurgh, yeah I didn't consider that.

Also I am not sure what the extra added commits are.

They were just fixing the indentation quickly to make my life easier for the review. It was before you pushed your most recent changes. I guess you worked locally before seeing them.

Before, I repushed it wasn't like this. I had the extra commit in the middle before yours and then your latest ones appeared to undo it to allow the "entire" diff across all commits to look okay.

I don't think we should include 57ac6ba as it means we effictively lose the history of the file as diffs are no longer useful. This is why we don't apply our formatting rules across the entire repo to fix all of the formatting violations in one go.

I don't agree with this. If anyone changes this file in the future, they will end up changing the formatting. And since I am all but rewriting this file, I think this is the perfect time to fix the formatting since there are so many changes to begin with. And also the aforementioned SHA-1 is solely about the reformatting so other commits are not affected.

@wburns The DummyInMemoryStore failures are related:
org.infinispan.persistence.dummy.DummyInMemoryStoreTest.testWriteAndDeleteBatchIterable
org.infinispan.persistence.dummy.DummyInMemoryStoreTest.testWriteAndDeleteBatch
org.infinispan.persistence.dummy.DummyInMemoryStoreTest.Uncaught

Fixed, the test was passing the wrong value in a spot :)

Thanks @wburns