QOL Improvements

Add:

Args for custom checkpoint, llm, outputs locations.
Args to pass HF token on startup.
Args for default llm/checkpoint on startup.
Selector for custom/default checkpoints, llms.
Seed randomization via -1
Save outputs to user-specified dir.
Load any checkpoint via from_single_file

C:\ProgramData\anaconda3\envs\omost\lib\site-packages\gradio\components\dropdown.py:181: UserWarning: The value passed into gr.Dropdown() is not in the list of choices. Please update the list of choices to include: ({'choices': [('omost-llama-3-8b-4bits', 'lllyasviel/omost-llama-3-8b-4bits'), ('omost-dolphin-2.9-llama3-8b-4bits', 'lllyasviel/omost-dolphin-2.9-llama3-8b-4bits'), ('omost-phi-3-mini-128k-8bits', 'lllyasviel/omost-phi-3-mini-128k-8bits'), ('omost-llama-3-8b', 'lllyasviel/omost-llama-3-8b'), ('omost-dolphin-2.9-llama3-8b', 'lllyasviel/omost-dolphin-2.9-llama3-8b'), ('omost-phi-3-mini-128k', 'lllyasviel/omost-phi-3-mini-128k')], 'value': 'lllyasviel/omost-llama-3-8b-4bits', '__type__': 'update'}, {'omost-llama-3-8b-4bits': 'lllyasviel/omost-llama-3-8b-4bits', 'omost-dolphin-2.9-llama3-8b-4bits': 'lllyasviel/omost-dolphin-2.9-llama3-8b-4bits', 'omost-phi-3-mini-128k-8bits': 'lllyasviel/omost-phi-3-mini-128k-8bits', 'omost-llama-3-8b': 'lllyasviel/omost-llama-3-8b', 'omost-dolphin-2.9-llama3-8b': 'lllyasviel/omost-dolphin-2.9-llama3-8b', 'omost-phi-3-mini-128k': 'lllyasviel/omost-phi-3-mini-128k'}) or set allow_custom_value=True.   warnings.warn( Loading LLM model from [{'choices': [['omost-llama-3-8b-4bits', 'lllyasviel/omost-llama-3-8b-4bits'], ['omost-dolphin-2.9-llama3-8b-4bits', 'lllyasviel/omost-dolphin-2.9-llama3-8b-4bits'], ['omost-phi-3-mini-128k-8bits', 'lllyasviel/omost-phi-3-mini-128k-8bits'], ['omost-llama-3-8b', 'lllyasviel/omost-llama-3-8b'], ['omost-dolphin-2.9-llama3-8b', 'lllyasviel/omost-dolphin-2.9-llama3-8b'], ['omost-phi-3-mini-128k', 'lllyasviel/omost-phi-3-mini-128k']], 'value': 'lllyasviel/omost-llama-3-8b-4bits', '__type__': 'update'}, {'omost-llama-3-8b-4bits': 'lllyasviel/omost-llama-3-8b-4bits', 'omost-dolphin-2.9-llama3-8b-4bits': 'lllyasviel/omost-dolphin-2.9-llama3-8b-4bits', 'omost-phi-3-mini-128k-8bits': 'lllyasviel/omost-phi-3-mini-128k-8bits', 'omost-llama-3-8b': 'lllyasviel/omost-llama-3-8b', 'omost-dolphin-2.9-llama3-8b': 'lllyasviel/omost-dolphin-2.9-llama3-8b', 'omost-phi-3-mini-128k': 'lllyasviel/omost-phi-3-mini-128k'}] Traceback (most recent call last):   File "C:\ProgramData\anaconda3\envs\omost\lib\site-packages\transformers\utils\hub.py", line 399, in cached_file     resolved_file = hf_hub_download(   File "C:\ProgramData\anaconda3\envs\omost\lib\site-packages\huggingface_hub\utils\_validators.py", line 106, in _inner_fn     validate_repo_id(arg_value)   File "C:\ProgramData\anaconda3\envs\omost\lib\site-packages\huggingface_hub\utils\_validators.py", line 154, in validate_repo_id     raise HFValidationError( huggingface_hub.errors.HFValidationError: Repo id must be in the form 'repo_name' or 'namespace/repo_name': '[{'choices': [['omost-llama-3-8b-4bits', 'lllyasviel/omost-llama-3-8b-4bits'], ['omost-dolphin-2.9-llama3-8b-4bits', 'lllyasviel/omost-dolphin-2.9-llama3-8b-4bits'], ['omost-phi-3-mini-128k-8bits', 'lllyasviel/omost-phi-3-mini-128k-8bits'], ['omost-llama-3-8b', 'lllyasviel/omost-llama-3-8b'], ['omost-dolphin-2.9-llama3-8b', 'lllyasviel/omost-dolphin-2.9-llama3-8b'], ['omost-phi-3-mini-128k', 'lllyasviel/omost-phi-3-mini-128k']], 'value': 'lllyasviel/omost-llama-3-8b-4bits', '__type__': 'update'}, {'omost-llama-3-8b-4bits': 'lllyasviel/omost-llama-3-8b-4bits', 'omost-dolphin-2.9-llama3-8b-4bits': 'lllyasviel/omost-dolphin-2.9-llama3-8b-4bits', 'omost-phi-3-mini-128k-8bits': 'lllyasviel/omost-phi-3-mini-128k-8bits', 'omost-llama-3-8b': 'lllyasviel/omost-llama-3-8b', 'omost-dolphin-2.9-llama3-8b': 'lllyasviel/omost-dolphin-2.9-llama3-8b', 'omost-phi-3-mini-128k': 'lllyasviel/omost-phi-3-mini-128k'}]'. Userepo_type` argument if needed.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\ProgramData\anaconda3\envs\omost\lib\site-packages\gradio\queueing.py", line 528, in process_events
response = await route_utils.call_process_api(
File "C:\ProgramData\anaconda3\envs\omost\lib\site-packages\gradio\route_utils.py", line 270, in call_process_api
output = await app.get_blocks().process_api(
File "C:\ProgramData\anaconda3\envs\omost\lib\site-packages\gradio\blocks.py", line 1908, in process_api
result = await self.call_function(
File "C:\ProgramData\anaconda3\envs\omost\lib\site-packages\gradio\blocks.py", line 1485, in call_function
prediction = await anyio.to_thread.run_sync(
File "C:\ProgramData\anaconda3\envs\omost\lib\site-packages\anyio\to_thread.py", line 56, in run_sync
return await get_async_backend().run_sync_in_worker_thread(
File "C:\ProgramData\anaconda3\envs\omost\lib\site-packages\anyio_backends_asyncio.py", line 2177, in run_sync_in_worker_thread
return await future
File "C:\ProgramData\anaconda3\envs\omost\lib\site-packages\anyio_backends_asyncio.py", line 859, in run
result = context.run(func, *args)
File "C:\ProgramData\anaconda3\envs\omost\lib\site-packages\gradio\utils.py", line 808, in wrapper
response = f(*args, **kwargs)
File "E:\AI\Omost\Omost\gradio_app.py", line 170, in load_llm_model
llm_model = AutoModelForCausalLM.from_pretrained(
File "C:\ProgramData\anaconda3\envs\omost\lib\site-packages\transformers\models\auto\auto_factory.py", line 484, in from_pretrained
resolved_config_file = cached_file(
File "C:\ProgramData\anaconda3\envs\omost\lib\site-packages\transformers\utils\hub.py", line 463, in cached_file
raise EnvironmentError(
OSError: Incorrect path_or_model_id: '[{'choices': [['omost-llama-3-8b-4bits', 'lllyasviel/omost-llama-3-8b-4bits'], ['omost-dolphin-2.9-llama3-8b-4bits', 'lllyasviel/omost-dolphin-2.9-llama3-8b-4bits'], ['omost-phi-3-mini-128k-8bits', 'lllyasviel/omost-phi-3-mini-128k-8bits'], ['omost-llama-3-8b', 'lllyasviel/omost-llama-3-8b'], ['omost-dolphin-2.9-llama3-8b', 'lllyasviel/omost-dolphin-2.9-llama3-8b'], ['omost-phi-3-mini-128k', 'lllyasviel/omost-phi-3-mini-128k']], 'value': 'lllyasviel/omost-llama-3-8b-4bits', 'type': 'update'}, {'omost-llama-3-8b-4bits': 'lllyasviel/omost-llama-3-8b-4bits', 'omost-dolphin-2.9-llama3-8b-4bits': 'lllyasviel/omost-dolphin-2.9-llama3-8b-4bits', 'omost-phi-3-mini-128k-8bits': 'lllyasviel/omost-phi-3-mini-128k-8bits', 'omost-llama-3-8b': 'lllyasviel/omost-llama-3-8b', 'omost-dolphin-2.9-llama3-8b': 'lllyasviel/omost-dolphin-2.9-llama3-8b', 'omost-phi-3-mini-128k': 'lllyasviel/omost-phi-3-mini-128k'}]'. Please provide either the path to a local folder or the repo_id of a model on the Hub.
`

@xhoxye seems like you have 32-bit version of numpy

The original version works fine @ginto-sakata

@xhoxye that's because @d8ahazard added a random seed generation, for which upper limit is 2**32 -1.
Your error indicates that you might have 32-bit version of numpy.
Check your if your numpy is 64-bit:

import numpy as np
print(np.int_)
<class 'numpy.int64'>

@ginto-sakata
How do I change it?

Try another pull, I think I fixed the precision issue.

I'm still having the same error here, unless I force seed = np.random.randint(0, 2 ** 31 - 1), and reading hf_download when rendering an image is also an error, and I can't read the model I copied to the Omost\models\checkpoints folder when refreshing

@ginto-sakata How do I change it?
Just make sure you have 64-bit python and install numpy again (you might want to do a clean install just in case)

Seed randomization via -1

Do we always want a random seed? a random seed button would give you more control

Seed randomization via -1

Do we always want a random seed? a random seed button would give you more control

Could be a good idea. I was just emulating how AUTO does it in that -1 == "randomized", otherwise, put in whatever you want.

I'm new to this but I'm loving how this works. it's honestly amazing imo. The only issue I seam to have is, I have no clue how to code or where/what to look for in the files to even change what model it is getting. Currently running this in a python env, but as someone who doesn't know code, well besides how to just setup a "simple" env, just wondering if there are any QOL improvements that would maybe include a dropdown for model selection to a folder that we can just put compatible models into?
I already use SD with comfyUI and other things, and would love to see how this works on some of my own SDXL merges I have worked on, but I'm at a loss for how to even do it.

ty Jtabox, I've never been good with git stuff, this helps a lot, I'll try this here shortly

Edit: as you might have read in my previous comment, some local models seem to take an extremely long time to load, making the process practically impossible. I haven't figured out what causes this yet. I have a 3080 so loading models and generating images isn't an issue generally, so it's probably not VRAM related. Not to mention that I can run those same models normally in A1111 & ComfyUI.

I see what you mean. Just tried 3 different models, cuz I"m trying not to use pony its good but i hate the "score" system, and the one called EchoAlpha didn't load, the new Compassmix, which is a SDXL lightning model, just hung, and then i tried Furry_XL, aka Seart's furry model that was used to make Compassmix, and it worked, but it was moving so slow, at like 90-110 seconds per iteration. However, when on SD WebUI's I usually get about 2-4 iterations per second on a 1024x1024 res and at lest 1.2 if I go to as high as 1440x1440, which is rare but sometimes i get lucky at that res with a good image. I'm gonna try it with pony but i've also noticed that its got different LLM's to select from as well. So, is the one selected by default when I load up this fork of the program the same one used in the main branch? Only asking cuz with the Main Branch it generates at normal speed.... but i guess i better try RealVision first cuz I haven't tried it at pure default yet, just went straight to putting in my own model.
I have an RTX 4070TI OC with 12GB of VRAM, the OC is Overclock and it was OC from factory according to the package, and no, i don't know how to OC, or what it is OC to, so whatever it's set to its staying at. I won't touch something I don't understand myself.

so, I followed your instructions, but idk if "I'm" doing something wrong or what at this point...
Load to GPU: LlamaForCausalLM
The attention mask and the pad token id were not set. As a consequence, you may observe unexpected behavior. Please pass your input's `attention_mask` to obtain reliable results.
Setting `pad_token_id` to `eos_token_id`:128001 for open-end generation.
G:\Omost\Omost 2\Omost\lib\site-packages\transformers\models\llama\modeling_llama.py:649: UserWarning: 1Torch was not compiled with flash attention. (Triggered internally at ..\aten\src\ATen\native\transformers\cuda\sdp_utils.cpp:455.)
  attn_output = torch.nn.functional.scaled_dot_product_attention(
You shouldn't move a model that is dispatched using accelerate hooks.
Unload to CPU: LlamaForCausalLM
Load to GPU: CLIPTextModel
Load to GPU: CLIPTextModel
Unload to CPU: CLIPTextModel
Unload to CPU: CLIPTextModel
Load to GPU: UNet2DConditionModel
  0%|                                                                                | 0/25 [00:00<?, ?it/s]K```

I sat here for about 15 Minutes and still couldn't get one iteration with BASE PonyDiffusionXL model... the ones that download from the program work fine, so... idk....

when it hangs like that idk what else to do so i just CTRL+C on the command window and it closes the running instance. I'm going to try downloading the models "fresh" from CivitAI and see if maybe its something to do with the models I have moved from my SD WebUI folder to this Programs folder.

if it doesn't work, then maybe i did something wrong or maybe theres some weird incompatability with my card... idk, and, if it does work with the same model "re-downloaded" straight from CivitAI into the Checkpoints folder of this program, them I'm just gonna be even more confused and wondering, If maybe I should delete and re-download all my models cuz somehow maybe "THEY" are the thing thats broken xD

@lllyasviel - I see you're on a tear doing updates to forge and focus. Maybe take a look at this PR, consider merging it?


Login cookie issue

I reinstalled it.
I logged in and replaced the cookie, but the same phrase came out.

Trying to log in with saved cookie
Error at doLogin(): (<class 'mechanize._response.get_seek_wrapper_class..httperror_seek_wrapper'>, <httperror_seek_wrapper (urllib.error.HTTPError instance) at 0x1e0f201f250 whose wrapped object = <HTTPError 403: 'Forbidden'>>, <traceback object at 0x000001E0F01B7800>)
Traceback (most recent call last):
File "PixivUtil2.py", line 1524, in doLogin
File "PixivBrowserFactory.py", line 347, in loginUsingCookie
File "PixivBrowserFactory.py", line 207, in open_with_retry
File "mechanize_mechanize.py", line 257, in open
File "mechanize_mechanize.py", line 313, in _mech_open
mechanize._response.get_seek_wrapper_class..httperror_seek_wrapper: HTTP Error 403: Forbidden
Cannot Login!
press enter to exit.

pixivutil.log
I'm having the same issue.  I attached my own log with my login censored.

The login request to https://www.pixiv.net/en/ is failing:
Trying to log in with saved cookie

send: b'CONNECT www.pixiv.net:443 HTTP/1.0\r\n'
send: b'\r\n'
send: b'GET /en HTTP/1.1\r\nAccept-Encoding: identity\r\nCookie: PHPSESSID=[REDACTED]\r\nUser-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.124 Safari/537.36\r\nHost: www.pixiv.net\r\nConnection: close\r\n\r\n'

reply: 'HTTP/1.1 302 Found\r\n'
header: Date: Tue, 28 Feb 2023 [REDACTED] GMT
header: Content-Type: text/html; charset=UTF-8
header: Content-Length: 0
header: Connection: close
header: vary: User-Agent
header: x-host-time: 109
header: x-xss-protection: 1; mode=block
header: set-cookie: first_visit_datetime_pc=[REDACTED]; expires=Thu, 27-Feb-2025 [REDACTED] GMT; Max-Age=63072000; path=/; secure
header: location: /en/
header: strict-transport-security: max-age=31536000
header: x-frame-options: SAMEORIGIN
header: CF-Cache-Status: DYNAMIC
header: Set-Cookie: __cf_bm=[REDACTED]; path=/; expires=Tue, 28-Feb-23 [REDACTED] GMT; domain=.pixiv.net; HttpOnly; Secure; SameSite=None
header: Server: cloudflare
header: CF-RAY: [REDACTED]
header: alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

send: b'CONNECT www.pixiv.net:443 HTTP/1.0\r\n'
send: b'\r\n'
send: b'GET /en/ HTTP/1.1\r\nAccept-Encoding: identity\r\nCookie: PHPSESSID=[REDACTED]; first_visit_datetime_pc=[REDACTED]; __cf_bm=[REDACTED]\r\nUser-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.124 Safari/537.36\r\nHost: www.pixiv.net\r\nConnection: close\r\n\r\n'

reply: 'HTTP/1.1 403 Forbidden\r\n'
header: Date: Tue, 28 Feb 2023 [REDACTED] GMT
header: Content-Type: text/html; charset=UTF-8
header: Transfer-Encoding: chunked
header: Connection: close
header: Permissions-Policy: accelerometer=(),autoplay=(),camera=(),clipboard-read=(),clipboard-write=(),fullscreen=(),geolocation=(),gyroscope=(),hid=(),interest-cohort=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=()
header: Referrer-Policy: same-origin
header: X-Frame-Options: SAMEORIGIN
header: Cache-Control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
header: Expires: Thu, 01 Jan 1970 00:00:01 GMT
header: Vary: Accept-Encoding
header: Server: cloudflare
header: CF-RAY: [REDACTED]
header: alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

A temporary workaround is to modify PixivBrowserFactory.py loginUsingCookie method to:

Load the cookie
Set self._myId
Set self._isPremium
Return true directly without sending the request.

Other functionalities (fanbox login, download) seems to be working atm.

Wow I was just using it moments ago, if you had the utility still running, it would work, but now it won't.

same getting HTTP Error 403: Forbidden

maybe related to #1209 as the solution i found that time seems to work now as well
change the useragent string to just "Mozilla/5.0" and it should work (try again if it fails)

maybe related to #1209 as the solution i found that time seems to work now as well change the useragent string to just "Mozilla/5.0" and it should work (try again if it fails)

Doesn't work for me

maybe related to #1209 as the solution i found that time seems to work now as well change the useragent string to just "Mozilla/5.0" and it should work (try again if it fails)

Best answer! Should be highlighted

maybe related to #1209 as the solution i found that time seems to work now as well change the useragent string to just "Mozilla/5.0" and it should work (try again if it fails)

I can also confirm it worked. I deleted the rest of the text and only kept Mozilla/5.0 and I logged in this time

Can confirm.  Worked perfectly.  I tested it prior to modifying the INI and it had the error.  With the change it had no issues.

Have a feeling Cloudflare is the problem, could be a coincidence that another thing I use also got issues at the same time.
The User-agent workaround does work.

[Network]
useProxy = False
proxyAddress =
useragent = Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.124 Safari/537.36
useRobots = True
timeout = 60
retry = 3
retryWait = 5
downloadDelay = 2
checkNewVersion = True
notifyBetaVersion = True
openNewVersion = True
enableSSLVerification = True
is what default settings is i guess ?

Setting user-agent to just Mozilla/5.0 works.

maybe related to #1209 as the solution i found that time seems to work now as well change the useragent string to just "Mozilla/5.0" and it should work (try again if it fails)

works

Changing user-agent doesn't work for me while running from source on linux. Still get the 403 error.

@na3i09 "useragent = Mozilla/5.0" did you use that? if so, idk other workaround

@na3i09 "useragent = Mozilla/5.0" did you use that? if so, idk other workaround

yeah, no dice when using the source version.

Changing user-agent doesn't work for me while running from source on linux. Still get the 403 error.

Try changing https://www.pixiv.net/en to https://www.pixiv.net in PixivBrowserFactory.py line 347:
https://github.com/Nandaka/PixivUtil2/blob/master/PixivBrowserFactory.py#L347

useragent = Mozilla / 5.0 is not work
useragent = Mozilla/5.0 is working

I still cannot log in using the session cookie and the proper user agent.

Created a pull request https://github.com/Nandaka/PixivUtil2/pull/1281 Hopefully fixes http:403 forbidden and people's confusion

MAN, this thread is making zero sense to me. I cant keep up

MAN, this thread is making zero sense to me. I cant keep up

Hi, please kindly stop posting non-constructive comments that disturbs everyone subscribed to this issue or repo.
Also, I would appreciate it if you can stop downvoting a solution that has expired for nearly a year ¯\(ツ)/¯.
I've already pointed out that you should use the solution by Nanoka, which worked very well. My automation script run twice a day and never fails since I switched to that solution.

I'm having this issue now, just pulled main down to try to fix it, but it is persisting. I've logged out and back in to re-aquire my cookie from firefox multiple times but it continues to give me this error.
I had the thought that I may be populating the cookie incorrectly, but if I change the last character to make it invalid I get a different error:
Error at doLogin(): (<class 'mechanize._response.get_seek_wrapper_class.<locals>.httperror_seek_wrapper'>, <httperror_seek_wrapper (urllib.error.HTTPError instance) at 0x7f5785b98d40 whose wrapped object = <HTTPError 302: 'The HTTP server returned a redirect error that would lead to an infinite loop.\nThe last 30x error message was:\nFound'>>, <traceback object at 0x7f5785b3a000>)
Traceback (most recent call last):
  File "/home/ahack/programming/PixivUtil2/PixivUtil2.py", line 1527, in doLogin
    result = __br__.loginUsingCookie()
  File "/home/ahack/programming/PixivUtil2/PixivBrowserFactory.py", line 354, in loginUsingCookie
    res = self.open_with_retry('https://www.pixiv.net')  # + self._locale)
  File "/home/ahack/programming/PixivUtil2/PixivBrowserFactory.py", line 208, in open_with_retry
    res = self.open(url, data, timeout)
  File "/home/ahack/programming/PixivUtil2/venv/lib/python3.10/site-packages/mechanize/_mechanize.py", line 257, in open
    return self._mech_open(url_or_request, data, timeout=timeout)
  File "/home/ahack/programming/PixivUtil2/venv/lib/python3.10/site-packages/mechanize/_mechanize.py", line 313, in _mech_open
    raise response
mechanize._response.get_seek_wrapper_class.<locals>.httperror_seek_wrapper: HTTP Error 302: The HTTP server returned a redirect error that would lead to an infinite loop.
The last 30x error message was:
Found

So it seems like my cookie is correct and then something else is causing it to fail.
I have tried both
useragent = Mozilla/5.0 (X11; Linux x86_64; rv:129.0) Gecko/20100101 Firefox/129.0
which was copied out of my browser and
useragent = Mozilla/5.0
to no avail

Nandaka, on pixiv fanbox i keep etting this
Configuration loaded.
Trying to log in FANBOX with saved cookie
Error getting FANBOX artist by id: 8594243 ==> Failed FANBOX Cloudflare CAPTCHA challenge, please check your cookie and user-agent settings.
i re appied
cf_clearance
cf_bm
cookieFanbox
the default pixiv worksfine just fanbox not and i have no clue what i do wrong
the view cookies i use this addon "cookie editor"
i have no clue what this cloudfare thing is

@Uraratan This is an issue for Pixiv logins, not Fanbox. Your issue is a duplicate of #1361 and #1371. I suggest searching through existing issues before simply posting under a pinned issue.

Sorry to bring back this http:403 forbidden issue but fixing useragent didn't fix the issue here:

I checked my cookies and cf multiple times: restarted a new session, restarted the browser, starting over the cookie maneuver. so it is not a cookie related issue
Changed useragent with: useragent = Mozilla/5.0 as suggested in every issues opened on this topic, tried again with correct cookies and it didn't fix the issue
tried switching multiple times useragent. I'm still stuck with the same Error
note that the issue appeared again since I updated all requirements using: pip install --upgrade --force-reinstall -r requirements.txt
I've looked a bit at all issues related on this error and didn't find another solution.
First time commenting on github, no idea how to use it properly so sorry if I missed something or did things wrong.

Sorry to bring back this http:403 forbidden issue but fixing useragent didn't fix the issue here:

I checked my cookies and cf multiple times: restarted a new session, restarted the browser, starting over the cookie maneuver. so it is not a cookie related issue
Changed useragent with: useragent = Mozilla/5.0 as suggested in every issues opened on this topic, tried again with correct cookies and it didn't fix the issue
tried switching multiple times useragent. I'm still stuck with the same Error
note that the issue appeared again since I updated all requirements using: pip install --upgrade --force-reinstall -r requirements.txt
I've looked a bit at all issues related on this error and didn't find another solution.
First time commenting on github, no idea how to use it properly so sorry if I missed something or did things wrong.

I will share my method and it work for me
first, change your pixiv language to japanese and logout
second, login back and get your "PHPSESSID"
I try change language back but it not work, you have to stay in japanese language to use it


Issue with Colloquial?

Am I misusing the colloquial method or is this a bug?
try! Date().colloquial(to: date).colloquial

date is a future Date : 2016-10-16 00:00:00 +0000

may be a fix
https://github.com/wsdwsd0829/SwiftDate/commit/8e5e6b120004d9464a86cc9cf18ce7f97336b3da

Yep it was actually fixed in 4.0.4 :)


In view function not called

Hi,
I am trying to get this to work angular 1.5.0-beta.1
HTML

 {{ category.name }}

Something here

CSS
#section {
	height: 500px;
}

Controller
(function() {
	angular.module("websiteApp")
		.controller("CvController", function(){

			this.categories = [
				{ name: "profile", id: "profile", content: "" },
				{ name: "education", id: "education", content: "" },
				{ name: "skills", id: "skills", content: "" },
				{ name: "work experience", id: "work", content: "" }
			];

			this.lineInView = function(index, inview, inviewpart, event) {
				console.log("called");
				return false;
			}

		});
})();

Can you please tell me where I'm going wrong?
Thanks.

I think it's because this.lineInView is not on the scope, it's the controller as syntax.
Try changing it to $scope.lineInView = function()....

It was to do with that, I needed to call cvCtrl.lineInView(...). Knew I was overlooking something!


GenerateDisplay: about additional view data

Additional view data will be merged using ObjectToDictionary.

Docs Build status updates of commit 445e8df:
:warning: Validation status: warnings

File
Status
Preview URL
Details

aspnet-core/xml/Microsoft.AspNetCore.Mvc.ViewFeatures/HtmlHelper.xml
:warning:Warning
View
Details

aspnet-core/xml/Microsoft.AspNetCore.Mvc.ViewFeatures/HtmlHelper.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.AspNetCore.Mvc.ViewFeatures.Internal.IViewBufferScope'.
Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'example' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

per the readme:
API PR's ( api/autoapi/... ) should not be made here. Changes to API documentation should be made in the source repository against the triple slash /// comments.


Remove dependency on mavenLocal() for functionalTests

Our tests should not depend on mavenLocal() at all.
The problem is that detekt-gradle-plugin is applying a dependency on detekt-cli using the version defined here:
https://github.com/detekt/detekt/blob/2eccd64bd8f8e71e688a222444356c945896c48f/build-logic/src/main/kotlin/Versions.kt#L5
So whenever that version gets bumped, test starts to fail unless you publishToMavenLocal as they'll try to find the next version on Maven Central, which won't be there.
That's also the reason why sometimes those PRs:

https://github.com/detekt/detekt/pull/6056

fail on CI as they can't find the newer artifact for detekt-cli on Maven Central yet.
This is blocking any automation of the release process essentially, and we should move away from it. See:

https://github.com/detekt/detekt/discussions/4696

In this PR I'm moving away from using the project version to apply the detekt-cli to use the latest published stable. This allows those tests to rely just on mavenCentral().
The dependency will be updated by Renovate bot as we release stable versions (we're doing the same thing for the formatting of the detekt-gradle-plugin itself).

Warnings

:warning:
It looks like this PR contains functional changes without a corresponding test.

  Generated by :no_entry_sign: dangerJS against a946487ecb9b9b34cf8baa00af8cb23143ff106c

Completely agree with the goal of removing mavenLocal usage, however this seems to make it more difficult to iterate on changes to CLI and the plugin and run functional tests.
When doing something like adding a new CLI flag and a complementary property in the Gradle plugin it seems like there's no way to run the functional tests with the updated CLI dependency?
Related (unmerged) PRs:

#4905
#5149

When doing something like adding a new CLI flag and a complementary property in the Gradle plugin it seems like there's no way to run the functional tests with the updated CLI dependency?

Yeah I agree, but I believe this is an improvement from the current status.
Even today, it's not possible to test the Gradle Plugin with the latest version of the CLI, unless you bump version and publishToMavenLocal.
If it helps, I can setup a separate CI job that bumps the version to 0.0.0 a local maven repo (I won't use mavenLocal() though) and runs functionalTest against it.
Still I would keep the current logic (i.e. relying on the latest release by default) as I want to be able to automate the release process, without having to publishToMavenLocal to merge the version bump.

That would help on CI but not local builds - unless that new task is attached to the functionalTest task as a dependency?
Maybe add that and then outline how one would update CLI & Gradle plugin together and run functional tests using that new task. As long as it's not necessary to update test code to get those tests working together when needed.

That would help on CI but not local builds - unless that new task is attached to the functionalTest task as a dependency?

I don't think we test this flow today with local build, though. As of today, local builds fetch detekt-cli from mavenCentral().
They will end up using mavenLocal() ONLY if you bump the version number here:
https://github.com/detekt/detekt/blob/2eccd64bd8f8e71e688a222444356c945896c48f/build-logic/src/main/kotlin/Versions.kt#L5

I recently found a Gradle feature that would fix that: https://docs.gradle.org/current/userguide/declaring_repositories.html#declaring_content_exclusively_found_in_one_repository
Using this means only Maven Local would be searched for the dependency. If the detekt CLI version is declared as a dynamic version then this would avoid the need to do any version bump as well. The only requirement then is pushing the required dependencies to Maven Local which can be easily setup with task dependencies.
Would this resolve your release issues as well?

I recently found a Gradle feature that would fix that: docs.gradle.org/current/userguide/declaring_repositories.html#declaring_content_exclusively_found_in_one_repository

Yup we could use this, yet still we will be forcing to depend on publishToMavenLocal() before we can run tests. Publishing to another maven local repo (being not ~/.m2) would probably be better but still suboptimal.

@3flex what's the best course of action for this? I'd really love to get rid of this setup as it's making the release process extremely complicated

This PR is stale because it has been open 90 days with no activity. Please comment or this will be closed in 7 days.

I vote to merge. If in the future we find better options we can revert this one and implement the better option but we have an issue with our release and this will improve that process.

I'd like to take another look at this - I'm not a fan of adding code to the plugin that's only there to support functional tests.
Also, the issue raised in the PR description:

whenever that version gets bumped, test starts to fail unless you publishToMavenLocal as they'll try to find the next version on Maven Central, which won't be there.

Should have been solved by #6424.
Agree with the goal of not using Maven local repo at all, but I don't think this should be merged.


Multiple validations  / disable form validation

I have a form with 2 submit buttons, if the user clicks on the second submit button, the validation should be disabled.
Is it possible to do?
** I can solve it  including a field where the user can select the form type, but there is requirement to do it using buttons.

@rafaelhz did you come up with a way to solve this based on your requirements?
I have the same situation.

I did not solve. For now I included a checkbox in the form where the user set the form type. Them I use this field in the validate function, to check what validation should be done.

I think warnings were added since you encountered this issue.
We were able to solve it by using a combination of warn and validate functions.

Depending on your situation, you might be able to get by only using Warn and not using Validate.
In our specific case, we want to enable SAVE_1 even if some required fields were left blank
But not if there are field-level errors. In that case we want to disable ALL form submissions.
SAVE_2 however, can only be enabled if all required fields are filled and valid, and the form itself is valid
So when we run Validate, we check if there's only a form-level error and no other errors (field-specific errors).
If that's the case, we return an empty object, the form is still valid and SAVE_1 remains enabled.
When we run Warn, we run the same validator function. But we need to change swwitch _error to _warning.
If this returns any warnings, this.props.warning is true and we use that prop to disable SAVE_2
Hope this helps you.
const validate = (values, props) => {
  let errors = myValidatorFunction(values, props);

  // if there is only a form-level error, delete it so that
  // form is considered valid and permits submission
  if (errors._error && Object.keys(errors).length === 1) {
    delete errors._error;
  }
  return errors;
};
const warn = (values, props) => {
  let warnings = {
    ...myValidatorFunction(values, props)
  };

  // convert _error to _warning
  if (warnings._error) {
    warnings._warning = warnings._error;
    delete warnings._error;
  }

  return warnings;
};

class myForm extends Component {
  render() {
    const {handleSave1, handleSave2, handleSubmit, invalid, warning} = this.props;

    return (

...form stuff in here

        <button disabled={invalid} onClick={handleSubmit(handleSave1)}>SAVE_1</button>

        // disable SAVE_2 if `this.props.warning` is true
        <button disabled={invalid || warning} onClick={handleSubmit(handleSave2)}>SAVE_2</button>

    );
  }
}

export default reduxForm({
  form: 'myForm',
  validate,
  warn
})(myForm);

thank you @dan-diaz. Using warnings is a good alternative. I will try it!

Because this issue saw almost no activity for more than a year, I'm closing it.

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain biomassiv.es has exceeded the max emails per hour (110/100 (110%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from o9.sgmail.github.com ([<IP_ADDRESS>]:27450)
by chi-server32.websitehostserver.net with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128)
(Exim 4.89)
(envelope-from<EMAIL_ADDRESS>id 1eMime-002ONe-Dp
for<EMAIL_ADDRESS>Wed, 06 Dec 2017 17:07:20 -0600
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;
h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe;
s=s20150108; bh=QAtIx0Myt624LDgEZ/322e+Uk5M=; b=xag2dvzCtL3ClFnP
Xd4mZ9h/wOa6xi3v5jsjXvVXduAmAOcZCaaqjEwje6jPNv+vJF2jjX8pZTCKRJMj
I7C4FdGM76y9gRbLNde41h61xhCDnSbufnzkGHY3XOTbd9dPrGIASMBUcSm36Ubn
JBSbemf3LCeZNtiy3NlbXsdMU/o=
Received: by filter0190p1iad2.sendgrid.net with SMTP id filter0190p1iad2-20050-5A287801-10
2017-12-06 23:06:41.250641813 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [<IP_ADDRESS>])
by ismtpd0001p1iad2.sendgrid.net (SG) with ESMTP id DGBz2ThdTfm4d0FQe1_ZDA
for<EMAIL_ADDRESS>Wed, 06 Dec 2017 23:06:41.064 +0000 (UTC)
Date: Wed, 06 Dec 2017 23:06:41 +0000 (UTC)
From: Gustavo Henke<EMAIL_ADDRESS>Reply-To: erikras/redux-form<EMAIL_ADDRESS>To: erikras/redux-form<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [erikras/redux-form] Multiple validations / disable form
validation (#2004)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_5a28780120e36_83243fd6cccc2f30285899";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: gustavohenke
X-GitHub-Recipient: biomassives
X-GitHub-Reason: subscribed
List-ID: erikras/redux-form <redux-form.erikras.github.com>
List-Archive: https://github.com/erikras/redux-form
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/AELU4uBfcEkDQapubEdxw6Kx9rVAVoRFks5s9x4BgaJpZM4KdK5P
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>X-SG-EID: ZlaDthyue/4HG+EgTb7JoZYs48JNb2iQtCcPV6oIs9XslawvPJ2OaPuRKlsKLurkb9uWZxSufEzw/V
F2p/C5UkH8ZhQar/rg7HsCvkcr0/x5JI4ux7OYeqeCuCuViRC5fy1RMoozcay1Qp3JZlGXJ2+hkNDZ
1czKZWthMfbt3E0j8YnRCqpe1YaYhQhy9f38hEHV6GEw4B6XbbBygts2mUdvSljb1/CQmPs1FZ8z51
c=
----==_mimepart_5a28780120e36_83243fd6cccc2f30285899
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Because this issue saw almost no activity for more than a year, I'm closing it.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/erikras/redux-form/issues/2004#issuecomment-349805035
----==_mimepart_5a28780120e36_83243fd6cccc2f30285899
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Because this issue saw almost no activity for more than a year, I'm closing it.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a28780120e36_83243fd6cccc2f30285899--

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain biomassiv.es has exceeded the max emails per hour (111/100 (111%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from github-smtp2-ext2.iad.github.net ([<IP_ADDRESS>]:60229 helo=github-smtp2b-ext-cp1-prd.iad.github.net)
by chi-server32.websitehostserver.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
(Exim 4.89)
(envelope-from<EMAIL_ADDRESS>id 1eMimf-002OOS-3A
for<EMAIL_ADDRESS>Wed, 06 Dec 2017 17:07:21 -0600
Date: Wed, 06 Dec 2017 15:06:41 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
s=pf2014; t=1512601601;
bh=Ite4F/C4Njay01q+PrMHAaospOaVHLUMytbEEpVh6pE=;
h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
List-Archive:List-Post:List-Unsubscribe:From;
b=YMW4j8ksaGVQY+WV+lc7sBOkM5XBPnP4Oy/KEcTR1Gij3XPt9Z4yimeVxSqykADgH
wIaBF+cgU56AJvXyvz9hKZWuK9jm0XFrcaBlLlu0/YoAaQeaS6HMGxbJHE2V0w38cR
cQkPOBrDD7PtGd4rKP5XqD4K3nwbwYn1AuZTNCFo=
From: Gustavo Henke<EMAIL_ADDRESS>Reply-To: erikras/redux-form<EMAIL_ADDRESS>To: erikras/redux-form<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [erikras/redux-form] Multiple validations / disable form
validation (#2004)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_5a287801c9146_4e3d3fc562e88f34137630";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: gustavohenke
X-GitHub-Recipient: biomassives
X-GitHub-Reason: subscribed
List-ID: erikras/redux-form <redux-form.erikras.github.com>
List-Archive: https://github.com/erikras/redux-form
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/AELU4uBfcEkDQapubEdxw6Kx9rVAVoRFks5s9x4BgaJpZM4KdK5P
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>----==_mimepart_5a287801c9146_4e3d3fc562e88f34137630
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #2004.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/erikras/redux-form/issues/2004#event-1375875527
----==_mimepart_5a287801c9146_4e3d3fc562e88f34137630
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #2004.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5a287801c9146_4e3d3fc562e88f34137630--


optimize the server's schedule tasks

Signed-off-by: slievrly<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
optimize the server's schedule tasks
Ⅱ. Does this pull request fix one issue?
pr before #1445
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #1446 into develop will increase coverage by 0.02%.
The diff coverage is 100%.

@@              Coverage Diff              @@
##             develop    #1446      +/-   ##
=============================================
+ Coverage      45.41%   45.43%   +0.02%
  Complexity      1664     1664
=============================================
  Files            345      345
  Lines          12708    12708
  Branches        1611     1611
=============================================
+ Hits            5771     5774       +3
+ Misses          6289     6287       -2
+ Partials         648      647       -1

Impacted Files
Coverage Δ
Complexity Δ

...ava/io/seata/core/constants/ConfigurationKeys.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...o/seata/server/coordinator/DefaultCoordinator.java
50% <100%> (ø)
25 <0> (ø)
:arrow_down:

...server/store/file/FileTransactionStoreManager.java
47.03% <0%> (+1.04%)
19% <0%> (ø)
: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 4472d9b...c84405c. Read the comment docs.


Correcting hip package dependencies

Hip package names have been changed because of the new rocm packaging standards. Hence the hip-hcc dependency needs to be changed to hip-devel hip-runtime-amd

Do we need the dependency to hip-devel?

We need it until we switch to hiprtc.

If it is needed not sure how we differentiate between hip-devel for rpm and hip-dev for debian.

You can set CPACK_DEBIAN_PACKAGE_DEPENDS and CPACK_RPM_PACKAGE_REQUIRES before calling create package.

Do we need the dependency to hip-devel?

We need it until we switch to hiprtc.

If it is needed not sure how we differentiate between hip-devel for rpm and hip-dev for debian.

You can set CPACK_DEBIAN_PACKAGE_DEPENDS and CPACK_RPM_PACKAGE_REQUIRES before calling create package.

So you mean for the hip-devel/dev we need to use CPACK_***** variables to differentiate between debian/RPM and for hip-runtime-amd current change is good with parameter to rocm_create_package() right?

There is this errors in the jenkins:
[2021-09-27T19:02:56.035Z] dpkg: migraphx: dependency problems, but configuring anyway as you requested:
[2021-09-27T19:02:56.035Z]  migraphx depends on hip-devel; however:
[2021-09-27T19:02:56.035Z]   Package hip-devel is not installed.
[2021-09-27T19:02:56.035Z]  migraphx depends on hip-runtime-amd; however:
[2021-09-27T19:02:56.035Z]   Package hip-runtime-amd is not installed.

It seems these packages are missing on rocm 4.2. Were they added in rocm 4.3?

There is this errors in the jenkins:
[2021-09-27T19:02:56.035Z] dpkg: migraphx: dependency problems, but configuring anyway as you requested:
[2021-09-27T19:02:56.035Z]  migraphx depends on hip-devel; however:
[2021-09-27T19:02:56.035Z]   Package hip-devel is not installed.
[2021-09-27T19:02:56.035Z]  migraphx depends on hip-runtime-amd; however:
[2021-09-27T19:02:56.035Z]   Package hip-runtime-amd is not installed.

It seems these packages are missing on rocm 4.2. Were they added in rocm 4.3?

4.2/4.3 had hip-base,hip-rocclr and for backward compatibility with --provides hip-hcc for hip-rocclr
starting 4.5 hip-base will be called as hip-devel/dev(with --provides as hip-base) and hip-rocclr will be renamed to hip-runtime-amd(--provides hip-rocclr). No more provides for hip-hcc which was deprecated long time back.

Since the changes were not compatible with ROCm4.3 / 4.4  closing this.
Opened a new PR #966 ( https://github.com/ROCmSoftwarePlatform/AMDMIGraphX/pull/966 )
After checking the changes with 4.3 / 4.4 / 4.5


[AutoRelease] t2-hybridcompute-2023-11-07-31553(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/4727
Live test fail, detailed info is in pipeline log(search keyword FAILED)!!!
https://dev.azure.com/azure-sdk/internal/_build?definitionId=1947

issue link:https://github.com/Azure/sdk-release-request/issues/4727

/check-enforcer evaluate

/check-enforcer override


Run as non-root user

It appears by running the unzip/cp CMDs the user that runs those commands becomes the owner of those dirs/files. At least that what appeared to be happening.


Implement Neon SIMD

This ports the WASM algorithm over to Aarch64 / ARM Neon. Rust itself isn't quite ready yet, but this should start compiling soon.
Blocked on: https://github.com/rust-lang/stdarch/pull/1230

Maybe you want to take a look at my adler32 SIMD implementation for NEON from way back then:
https://github.com/kaffeemonster/zlib/blob/adler32_vec/arm/adler32.c
It also contains some tricks which can be used in other SIMD (x86), mainly vector_chop, a modulo-approx. you can do on most SIMD instruction set. This way you can leave the data in the vector register and don't have to do a full reduction, copy to normal register set, do a modulo, and back to vector register. Also since you then have often 4 or more single sums, your inner loop count is not limited to NMAX (5552).

Is there any progress or status on this? I need adler32 to be fast on arm64. Is this PR not deemed ok? Any plans to finish the support for NEON?

Is there any progress or status on this? I need adler32 to be fast on arm64. Is this PR not deemed ok? Any plans to finish the support for NEON? I would love to contribute, but no SIMD experience.

I'll try running the build again when I have time.  Last a checked rust support for some of the operations we need was lacking although this was a while ago

bump

I'll quickly remove all the nightly conditions that shouldn't apply anymore to aarch64.

Seems like vdotq_u32 is not stable yet somehow.

Actually the error seems incorrect. The function is stable, but requires dotprod in addition to neon.

Actually the error seems incorrect. The function is stable, but requires dotprod in addition to neon.

It's been a bit since I looked at this code, but if I remember correct this would require adding an additional #cfg clause to allow compilation on non-dotprod,neon targets.

Mmh, turns out that the dotprod feature is indeed still unstable:

https://github.com/rust-lang/stdarch/blob/master/crates/stdarch-gen/src/main.rs#L1590

Would this dotprod be supported on Android ARM64 devices? Or is it a very obscure instruction? Would it impact performance much if a device doesn't have it? (cq can we still use NEON for the rest?)

Would this dotprod be supported on Android ARM64 devices? Or is it a very obscure instruction? Would it impact performance much if a device doesn't have it? (cq can we still use NEON for the rest?)

At a glance @CryZe comment indicates we could get it working when compiling with nightly.  The alternative is to port the c implementations mentioned above and hope that the intrinsics are stable.

I am willing to offer a bounty of 50 Euro to get this working on ARM64 Android.

I now resorted to using libdeflater-sys that wraps the libdeflate C++ library, and provides SIMD accelerated adler32 besides deflate and crc32. It has a dotproduct check and implementations for both with and without dot prod, while using NEON intrinsics. It did speed up my app on Android with 33%.

Would this dotprod be supported on Android ARM64 devices? Or is it a very obscure instruction?

It's supported on more modern chips. It is by no means universally present, though.


Feature Request: C500 support

Is your feature request related to a problem? Please describe.
C500 Tapo camera works like a charm, but no binary motion sensor is available.
Describe the solution you'd like
I have a C200 1.0 and a C200 2.0, and both work perfectly, but C500 1.0 is not showing a motion sensor on HA.
Additional context
Noise sensor is available, but seems not working on HA.

Is there any error in the logs? This is probably duplicate of https://github.com/home-assistant/core/issues/85902#issuecomment-1490120209 . Once it is fixed upstream it will be fixed also here.


Fix a race condition during the computation of uriToWorkspaceCache

See comment in workspaceForDocument that explains the race.

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test Windows


Issue with database and vrp_lscustoms

Hey, i was trying to move my fivem server to a dedicated vps, i managed to create a databse and everything went smooth-ish until i try to connect to my server , when i do, i get a identification error, and the console displays this message
query exception vRP/lscustoms_columns : System.AggregateException: One or more errors occurred. ---> MySql.Data.MySqlClient.MySqlException: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'IF NOT EXISTS veh_type varchar(255) NOT NULL DEFAU
I'm kind of new to this and im stuck here. i don't really know what to do,  thanks in advance

https://github.com/ImagicTheCat/vRP/tree/master/doc#issues--features--help


Creating a Deployment defaults to "Allow Privilege Escalation"

Internal reference: SURE-3663
Request description:
When users create Deployments in the Rancher Cluster Explorer UI, the setting under "Security Context" -> "Privilege Escalation" defaults to "Yes, container can gain more privileges than its parent process"
Users will fail to create deployments by default (at least when e.g. setting the "Run as User ID" field). The security context parameter is not added to the deployment unless one parameter is set, however when some parameter is set the Privilege Escalation option is set to yes by default.
This could be considered a more secure means of running Kubernetes, which would help with RKE2 strategy to align with other usage within the product.
Actual behavior:
Privilege Escalation in the security context tab is set to yes by default
Expected behavior:
Privilege Escalation in the security context tab is set to no by default
Additional notes:
Instead of choosing between one default or another, it would be helpful to have a way to select the default config options in the UI for each user.

Verified on v2.7-head Commit ID: c35f112
The Privilege Escalation field is now defaulted to the No option.


PackRecipeV2 leaves out last slot

Using the Menu Item "Save Selected Avatar(s) asset" saves an asset, but the Text Recipe is missing the last slot from the umaRecipe.slotDataList.
Must be because
int slotCount = umaRecipe.slotDataList.Length - umaRecipe.additionalSlotCount;
in PackRecipeV2 method of UMAPackedRecipebase.cs
If there is an additional slot, which is not the last slot in the slotDataList, instead of the additional slot being skipped when saving, another slot at the last index will get skipped.

It was meant as a feature but the more we learn about how people use additional recipes the more it becomes clear it's not a feature. :)
The idea was that Slots with Colliders, Locomotion, etc should be added through additional recipes and shouldn't be serialized. However it's clear that those slots should instead carry a flag that they're not to be serialized.

Fixed in branch unity53


chore(postcss): remove :hover styles when not supported in browser

General summary
By default browsers on touch screen device display the hover styles after the user clicks on an element.
We want to avoid this so this PR configures a PostCSS plugin that wraps all :hover in a CSS media query @media (hover: hover) so that we only active hover style on device that have a pointer that supports hover.
Screenshots
From left to right:

Device with mouse
Touch screen before this PR
Touch screen after this PR

https://user-images.githubusercontent.com/939567/154649992-b7963148-6be4-42f1-b844-d028f6e0093d.mp4
Before this PR: https://5fbfb1d508c0520021560f10-ctdadtqoew.chromatic.com/?path=/story/lumx-components-side-navigation-sidenavigation-demos--nested
After this PR: https://5fbfb1d508c0520021560f10-gcqqkmguvm.chromatic.com/?path=/story/lumx-components-side-navigation-sidenavigation-demos--nested

Seems ok for me, I only got a weird press state look with chrome touch device emulation:

Everything ok on ios 15 safari

@FlorentDinet Yes this blue overlay is added by chrome during touch screen emulation. It is present with or without this PR's code


xdpm searches for wrong folder

When I'm trying to run xdpm install, xdpm watch or xdpm ls with the Release version of Adobe XD (it works for the prerelease version with -w p) on Windows, I get the following error message:
ERROR: Could not locate C:\Users\pablo\AppData\Local\Packages\Adobe.CC.XD.adky2gkssdxte\LocalState. Do you have the release version of Adobe XD CC installed?
The problem here is that xdpm searches for an Adobe.CC.XD.adky2gkssdxte-folder, while only an Adobe.CC.XD_adky2gkssdxte-folder exists (_ instead of .).

I just opened a pull request fixing the issue: #6

I got the same error with XD <IP_ADDRESS> and xdpm 2.0.0 on macOS(10.14.4).
ERROR: Could not locate /Users/*****/Library/Application Support/Adobe/Adobe XD CC. Do you have the release version of Adobe XD CC installed?

There is an 'Adobe XD' folder exist in '/Users/*****/Library/Application Support/Adobe/'.

I’m on my phone at the moment so I can’t check yet, but this is likely due to the fact that XD has changed its name from “Adobe XD CC” to “Adobe XD”, and therefore the relevant /Library folder has also changed names.
If so, the cause of the issue is here:
https://github.com/AdobeXD/xdpm/blob/master/lib/constants.js.
Can you confirm the application name you have?
Note that this should only affect Mac I believe.

Thanks reply.
The application name is "Adobe XD".
It also worked correctly when I fixed from "Adobe XD CC" to "Adobe XD" in the lib/constants.js.
From:
"r": path.join(home, "Library", "Application Support", "Adobe", "Adobe XD CC"),
"p": path.join(home, "Library", "Application Support", "Adobe", "Adobe XD CC (Prerelease)"),
"d": path.join(home, "Library", "Application Support", "Adobe", "Adobe XD CC (Dev)")

To:
"r": path.join(home, "Library", "Application Support", "Adobe", "Adobe XD"),
"p": path.join(home, "Library", "Application Support", "Adobe", "Adobe XD (Prerelease)"),
"d": path.join(home, "Library", "Application Support", "Adobe", "Adobe XD (Dev)")

I have no environment to test on Windows.

Thanks for checking!
My understanding is that Windows remains unaffected because the equivalent folders don’t change names even if the app does. We need to verify that, in addition to patching the Mac version.
Reopening this issue.

And now I see Kerri has already put in a PR for this:
https://github.com/AdobeXD/xdpm/pull/17/files

Fixed by https://github.com/AdobeXD/xdpm/pull/17
cc @kerrishotts @dkstevekwak


a lint for 3.0.0-beta requires Dart 3.1

From a CI failure when trying out 3.0.0-beta:

warning - analysis_options.yaml:1:10 - Warning in the included options file /home/runner/.pub-cache/hosted/pub.dev/lints-3.0.0-beta/lib/core.yaml(723..747): 'no_wildcard_variable_uses' is not a recognized lint rule - included_file_warning

It looks like we need to rev the min sdk version of package:lints (to 3.1), or remove the no_wildcard_variable_uses from the package.
It's been quite a while since we last published, so I'd like to make the new version of the package more widely available. I think that means dropping no_wildcard_variable_uses for now, and re-adding it for our next version (and reving the min. sdk to 3.1 then).

It's been quite a while since we last published, so I'd like to make the new version of the package more widely available.

Agreed.


Update srdf, srdf4j, srdfjena to 0.1.54

Updates

es.weso:srdf
es.weso:srdf4j
es.weso:srdfjena

from 0.1.53 to 0.1.54.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "es.weso" } ]

labels: semver-patch

Codecov Report

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

@@           Coverage Diff           @@
##           master      #12   +/-   ##
=======================================
  Coverage   59.41%   59.41%
=======================================
  Files          97       97
  Lines        4223     4223
  Branches      179      179
=======================================
  Hits         2509     2509
  Misses       1714     1714

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 f0f23a3...6f176a4. Read the comment docs.


Correction for raw affiliation Radio Frequency Systems France

Correction needed for raw affiliation Radio Frequency Systems France
raw_affiliation_name: Radio Frequency Systems France
new_rors:
previous_rors: 033x0mt18
works_examples: W2795357019;W3127972016;W4298049083;W3184221410
contact: 4f55bd77ba3c922fe02cc94825b168b2:e05e334facc0a6815e51b21a593412b8e0c7 @ inrae.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-09. The new affiliations should be visible within the next 7 days.


Fix build by renaming ValidationState_t constructor argument.

The diag argument shadows the diag method, so the strict build fails.

We have shadowing warnings turned on, which turn into errors.
+2


Bug fix for "No file or variants found for asset: ..."

Bug fix for "No file or variants found for asset: packages/html_editor_enhanced/summernote.html"
Bug Fix for:
#341 #331

hello, why does'nt anyone merge this PR? many of us still facing the issue and cannot continue our project

@tneotia  Please merge the fix for assets and send out a new release.  Can't build my app at all with recent release of flutter 3.7.0

Sorry guys, been very busy with other projects. Only have time to look at critical issues or bug fixes for this package these days - if this is breaking I will merge and publish new version.

@tneotia Thanks, it works again.


Fix helpmergepullsubscription subscriber_db name

There is a typo in this doc. The correct name for the "subscription_db" parameter mentioned in this doc is "subscriber_db".

@willibrandon : Thanks for your contribution! The author(s) have been notified to review your proposed change.

The following users don't have valid GitHub IDs, or are not collaborators on this repo: microsoftdocs/public-repo-pr-review-team

#sign-off


[WIP] 🐛 re-run migration for sqlite/pg

closes #7192
With this PR people who were affected from non formatted sqlite/postgres dates, this PR will fix when they update to 0.11 (which we will release tomorrow)
Postgres: we have used ms format before (YYYY-MM-YY HH:mm:ss.ZZZ), but we need YYYY-MM-DD HH:mm:ss.

add 008 migration
added script to re-run 006/01

I decided against a hack to re-run the migration and instead i added a new migration script 008/01. The reasons:

the code is too complex for a hack
i don't wanne touch this logic again and move the hack into a migration file
migration of 006/01 can take very long, thats why we treat it as real migration file

TODO

[x] do one manual test (change tz to utc, build db 0.8, checkout 0.9, run migration, see it skips and verify sqlite format is still integer....then run db with this branch) - tested with #7322
[x] tested: 0.8 ghost, server is UTC, see that migration runs 2 times, but no offset is changed at all. all dates are still the same
[x] go over PR and check for tidy up
[x] update postgres from ghost 0.7.0 to 0.11.0 and see that date migration ran twice. no offset happend
[x] check format before executing 008

ready for review 👍


Some parallell execute Steps may be stucked on running phase when retry workflow manually

Pre-requisites

[X] I have double-checked my configuration
[X] I can confirm the issues exists when I tested with :latest
[ ] I'd like to contribute the fix myself (see contributing guide)

What happened/what you expected to happen?

As the picture shows, workflow has three parallell execute nodes: step-case(Failed), retry-step-case(Failed), retry-step-group-case(Succeeded).
If I retry this workflow manually, retry-step-group-case(0) will stucked on running phase even if workflow is completed.

Version
latest
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: workflow-fail-with-argument-
spec:
  entrypoint: main
  arguments:
    parameters:
      - name: code
        value: 1
  templates:
  - name: main
    steps:
    - - name: retry-step-group-case
        template: fail-step-group
      - name: retry-step-case
        template: fail-with-argument-with-retry
        arguments:
          parameters:
            - name: code
              value: '{{workflow.parameters.code}}'
      - name: step-case
        template: fail-with-argument
        arguments:
          parameters:
            - name: code
              value: '{{workflow.parameters.code}}'
  - name: fail-with-argument-with-retry
    inputs:
      parameters:
        - name: code
    container:
      image: python:alpine3.6
      command: [python, -c]
      args: ["import sys; sys.exit({{inputs.parameters.code}})"]
    retryStrategy:
      limit: "5"
      backoff:
        duration: "5"
        factor: "2"
        maxDuration: "1m"
  - name: fail-with-argument
    inputs:
      parameters:
        - name: code
    container:
      image: python:alpine3.6
      command: [python, -c]
      args: ["import sys; sys.exit({{inputs.parameters.code}})"]
  - name: fail-with-rate
    container:
      image: python:alpine3.6
      command: ["python", -c]
      args: ["import random; import sys; exit_code = random.choice([0, 0, 1]); sys.exit(exit_code); print(exit_code)"]
  - name: fail-step-group
    steps:
    - - name: step1
        template: fail-with-rate
    - - name: step2
        template: fail-with-rate
    - - name: step3
        template: fail-with-rate
    retryStrategy:
      limit: "5"
      backoff:
        duration: "5"
        factor: "2"
        maxDuration: "1m"

Logs from the workflow controller
kubectl logs -n argo deploy/workflow-controller | grep ${workflow}

Logs from in your workflow's wait container
kubectl logs -n argo -c wait -l workflows.argoproj.io/workflow=${workflow},workflow.argoproj.io/phase!=Succeeded

workflow_server.go RetryWorkflow() -> util.go FormulateRetryWorkflow()
case wfv1.NodeError, wfv1.NodeFailed, wfv1.NodeOmitted:
	if isGroupNode(node) {
                 // retry-step-group-case(0) is Steps type, which belong to group node, so it will be reset to running phase
                 // retry-step-group-case is succeeded phase, so its child node running phase will not affect the workflow execution
		newNode := node.DeepCopy()
		newWF.Status.Nodes.Set(newNode.ID, resetNode(*newNode))
		log.Debugf("Reset %s node %s since it's a group node", node.Name, string(node.Phase))
		continue
	} else {
		log.Debugf("Deleted %s node %s since it's not a group node", node.Name, string(node.Phase))
		deletedPods, podsToDelete = deletePodNodeDuringRetryWorkflow(wf, node, deletedPods, podsToDelete)
		log.Debugf("Deleted pod node: %s", node.Name)
		deletedNodes[node.ID] = true
	}


Name collision issue in Remote Redux DevTools is fixed

As we're using redux-devtools-instrument and there's no dependency to React anymore

Thanks!


Cherry pick PR #886

Change the mount, unmounts and nvme operations over to use spawn blocking.
Remove async_stream for grpc over uds for controller and node.

bors try

bors merge

bors merge


Deploy function doesn't work on Windows

Hi,
I've tested your tool on linux and it works perfectly, but when I'm trying to use it on Windows, deploy function doesn't work. Is there any chance, it would work on Windows? :)

Hey thanks for filing an issue, can you provide some more information. What version of kong are using and what version of windows are using?
This tool is intended for use for kong 1.3 EE.

I'm using:

kong-portal-cli v1.0.0
kong from image kong-enterprise-edition-amqp-enhanced:1.3-rc1-alpine
Windows 10
When I'm trying to deploy default developers portal (portal deploy default) on Windows I'm getting output: output.txt
Exit code of this operation is 0.

When I'm using WSL everything works correctly :)

@konwrz20
Thanks for the followup!  We will look into the issue and will link the PR fix to this ticket once submitted.

https://github.com/Kong/kong-portal-cli/pull/14

#14 PR merged, closing isssue.


Faking the ip <IP_ADDRESS> don't works on windows

I tried the steps of https://github.com/nagyesta/assumed-identity?tab=readme-ov-file#usage and works very well on linux.
The problem is with windows + docker desktop :

The container starts
It works with localhost

But the endpoint doesn't works with the IP

Any tip to solve it?
Thanks so much!!!

Hi @richard-leon-130524 ,
first of all, thank you for using Assumed Identity, and thank you for opening this issue!
I think the situation you have described might be because, AFAIK Docker Desktop is running a WSL instance in the background to be able to run the Docker Engine. I would assume, that there must be some kind of magic in it that is forwarding the ports to localhost, but as soon as you are running on a different IP, it will be harder to reach from the Windows host. I have never used Docker Desktop on Windows, so I am afraid I am not the best person to help resolve this network/routing part of the issue.
BUT, if you are only running the Assumed Identity image for the sake of Lowkey Vault, then you might be able to find a workaround by adding additional env variables or config parameters when you are running your application. Please see more details at the various example projects listed here: https://github.com/nagyesta/lowkey-vault/tree/main?tab=readme-ov-file#example-projects
Also, please note, that the latest Lowkey Vault contains the same Assumed Identity token endpoint now on port :8080 by default. You can configure this using the --app.token.port=80 Lowkey Vault startup argument. This way, if you can find a way to assign the <IP_ADDRESS> IP to your machine and run Lowkey Vault as a Jar, then you can leave out the whole layer of complexity coming from the Docker and WSL combination.
What do you think, would any of these options help you resolve the issue?
Thank you again!

Hi @richard-leon-130524 , first of all, thank you for using Assumed Identity, and thank you for opening this issue!
I think the situation you have described might be because, AFAIK Docker Desktop is running a WSL instance in the background to be able to run the Docker Engine. I would assume, that there must be some kind of magic in it that is forwarding the ports to localhost, but as soon as you are running on a different IP, it will be harder to reach from the Windows host. I have never used Docker Desktop on Windows, so I am afraid I am not the best person to help resolve this network/routing part of the issue.
BUT, if you are only running the Assumed Identity image for the sake of Lowkey Vault, then you might be able to find a workaround by adding additional env variables or config parameters when you are running your application. Please see more details at the various example projects listed here: https://github.com/nagyesta/lowkey-vault/tree/main?tab=readme-ov-file#example-projects
Also, please note, that the latest Lowkey Vault contains the same Assumed Identity token endpoint now on port :8080 by default. You can configure this using the --app.token.port=80 Lowkey Vault startup argument. This way, if you can find a way to assign the <IP_ADDRESS> IP to your machine and run Lowkey Vault as a Jar, then you can leave out the whole layer of complexity coming from the Docker and WSL combination.
What do you think, would any of these options help you resolve the issue?
Thank you again!

Summary
Faking the Azure Instance Metadata Service which default ip is <IP_ADDRESS> don't work on Windows.
Thank goodness linux exist for real ci environments.
Workaround on windows with nodejs
This variable helped me: AZURE_POD_IDENTITY_AUTHORITY_HOST=http://localhost
I achieved to write and read secrets with these steps:

docker run --rm -d  -p 8443:8443 nagyesta/lowkey-vault:2.4.13-ubi9-minimal
docker run -d  -p 80:80 --rm nagyesta/assumed-identity:1.2.16
These en variables in the nodejs client

KEYVAULT_URI=https://localhost:8443
NODE_TLS_REJECT_UNAUTHORIZED=0
AZURE_POD_IDENTITY_AUTHORITY_HOST=http://localhost

Write a secret:

const { DefaultAzureCredential } = require("@azure/identity");
const { SecretClient } = require("@azure/keyvault-secrets");
const credential = new DefaultAzureCredential();

let options = {
    serviceVersion: "7.4",
    disableChallengeResourceVerification: true, // ONLY ON CI, NEVER USE ON PROD!
};

const client = new SecretClient(process.env.KEYVAULT_URI, credential, options);

async function main(){
  const secretName = `secret-api-key`;
  const result = await client.setSecret(secretName, "changeme!!!");
  console.log("result: ", result);
}

main();

Read a secret

const { DefaultAzureCredential } = require("@azure/identity");
const { SecretClient } = require("@azure/keyvault-secrets");
const credential = new DefaultAzureCredential();

let options = {
    serviceVersion: "7.4",
    disableChallengeResourceVerification: true, // ONLY ON CI, NEVER USE ON PROD!
};

const client = new SecretClient(process.env.KEYVAULT_URI, credential, options);

async function main(){
  var response = await client.getSecret("secret-api-key");
  console.log(response);
}

main();

Thanks you for your help and your time to develop this tool!!!

Thank you for providing this detailed description! I am glad you were able to sort out the issue!


Python

python don't recognize inputs on Atom
i try to type this:
int = input("Type a number: ")
but not happening

Some text editors like Atom and Sublime really don't like user input.
Install atom-shell-commands .
Check out the Running in a new window sample in the linked page.
Then edit the config file to look just  like this:
"atom-shell-commands":
commands: [
{
name: "run with python 3"
command: "cmd"
arguments: [
"/C"
"start"
"$your_folder$/launch_python3.cmd"
"{FileName}"
]
options:
cwd: "{FileDir}"
keymap: 'ctrl-3'
}
]
I'd save the launch_python3.cmd in my user folder /.atom, but I think it's cool to save it elsewhere, shouldn't be a problem.
The contents of the cmd file should be:
@echo off
REM used by atom-shell-commands to launch python 3 in a new window
$your_python_path$\python.exe %1
pause
exit
Now, you should be able find  a 'Run with Python 3' under 'Packages > Atom Shell Commands'.
Change up the name and keyboard shortcut however you want after that.
Oh yeah, and when you click on the menu, a new command prompt window is show : it too supports the user input you desire.
If it doesn't work, accept Atom hates user input.


Update app dependencies (CBW-133)

Purpose
To keep the apps up to date, we must make sure dependencies are using the latest possible version and update any related code.
Changes
Updated all dependencies and migrates from Kotlin synthetics to Jetpack view binding.
Also updated manifest and gradle build script.

Please review the following
Please check if the app compiles and runs.
Test screens that you can think of in the. See that they contain content as normal.
Of course that must be no crashes.
Checklist

[x] My code follows the style of this project.
[x] The code compiles without warnings.
[x] I have performed a self-review of the changes.
[x] I have documented my code, in particular the intent of the
hard-to-understand areas.
[x] (If necessary) I have updated the CHANGELOG.

CLA acceptance
_Remove if not applicable.
By submitting the contribution I accept the terms and conditions of the
Contributor License Agreement v1.0

link: https://developers.concordium.com/CLAs/Contributor-License-Agreement-v1.0.pdf

[x] I accept the above linked CLA.

Compiles and works just as before, good job 👍


Document usage of Amalgam8 routing rules for load balancing in K8S

Document approaches and differences for doing k8s deployment of applications, leveraging a8 for finer grained load balancing (e.g,. percentage based, etc.).

P1 - Needed for demo

Shall be fixed once #514 is merged


Update linalg.py

This PR intentionally breaks some code to ensure that Travis CI reports build failure.

@ltiao do we still need to do this?

Don't need this particular PR, but at some point we should probably create another PR that intentionally breaks stuff to check that Travis still reports build failure now that I've totally overhauled it..


Flaky test: DockerSwarmSuite.TestApiSwarmServicesStateReporting

Seen on power, but looks like a general test issue.
10:55:32 FAIL: docker_api_swarm_test.go:374: DockerSwarmSuite.TestApiSwarmServicesStateReporting
10:55:32
10:55:32 [d68464000] waiting for daemon to start
10:55:32 [d68464000] daemon started
10:55:32 [d23430000] waiting for daemon to start
10:55:32 [d23430000] daemon started
10:55:32 docker_api_swarm_test.go:380:
10:55:32     d2 := s.AddDaemon(c, true, true)
10:55:32 check_test.go:221:
10:55:32     c.Assert(d.Join(swarm.JoinRequest{
10:55:32         RemoteAddrs: []string{s.daemons[0].listenAddr},
10:55:32         Manager:     manager}), check.IsNil)
10:55:32 ... value *errors.errorString = &errors.errorString{s:"joining swarm: invalid statuscode 406, \"{\\\"message\\\":\\\"This node is already part of a Swarm cluster. Use \\\\\\\"docker swarm leave\\\\\\\" to leave this cluster and join another one.\\\"}\\n\""} ("joining swarm: invalid statuscode 406, \"{\\\"message\\\":\\\"This node is already part of a Swarm cluster. Use \\\\\\\"docker swarm leave\\\\\\\" to leave this cluster and join another one.\\\"}\\n\"")
10:55:32
10:55:32 [d68464000] exiting daemon

thanks!

This is a known issue, affects other tests.
When I was writing swarmkit tests, I got this comment. I think there is an associate issue and PR in swarmkit but I can't remember how to find it right now.
https://github.com/docker/docker/pull/24563#issuecomment-232816142

/cc @tonistiigi ^^

@tophj-ibm Is this result from our ci. Do you have a link?

@tonistiigi https://jenkins.dockerproject.org/job/Docker Master (powerpc)/925/console

again I've only seen it on power, and I've only seen it happen once

I updated powrpc ci to store the daemon logs like other ci jobs. Without the logs it's hard to see what may be going on here. This error looks quite weird and I haven't seen it before.

Yeah I reread it the right way this time and it is new, not the same one. It just looked familiar at a glance.

thanks, I'll keep an eye out for it.
@dperny good info, that helps because I'm looking into #24590 which looks like it might be related to what you linked

@tonistiigi happened again, except this time on a different test. Also all the following swarm tests failed. A quick glance makes me think that everything isn't getting cleaned up after the tests https://jenkins.dockerproject.org/job/Docker Master (powerpc)/972/

@tophj-ibm Could it be something with UnixNano() method in powerpc? Daemon ID is taken from unixnano modulus(we should use rand.Read instead) and you can see that for powerpc these numbers are too round to be actual nanoseconds. I opened logs for TestApiSwarmServicesCreateGlobal and it clearly already has swarm files in daemon folder when daemon starts. Powerpc build does seem to do rm -rf bundles in the end that should clear the state between builds.

@tonistiigi nice catch! Looks like time.Now itself is actually wrong on power. I'll go ahead and submit and issue for it. Thanks for looking into it!

Turns out the time.Now precision difference has been a known "issue" for a long time. FYI: https://github.com/golang/go/issues/11222

Being fixed upstream https://go-review.googlesource.com/#/c/27710/

This is fixed for ppc64/ppc64le: https://github.com/golang/go/commit/0df5ab7e6569a8bf6bc87975e539706163bf664a


Add defaults for ContributionGraph (Fixes rendering crash)

Fixes #425

Thank you for your contribution 👍  this is now available in v6.12.0


Add cookie permissions

We should at least get consent for the Facebook share button.
If #34 is implemented, we don't need consent for Google Analytics, since we won't collect personal information in that case.

We don't anymore :D


INT-1045 better canonicalization

I still don't have a good repro of this bug, but I'm pretty sure that these were the two biggest issues (case sensitivity weirdness and IP addresses being used in the suffix).

LGTM

Review status: 0 of 4 files reviewed at latest revision, 3 unresolved discussions.

index.js, line 24 [r1] (raw file):
Don't want to call getId() here as that should happen higher in the stack (e.g. express middleware)

lib/canonicalize.js, line 9 [r1] (raw file):
Same as above.  Not a good idea to do on this level.

lib/probe.js, line 33 [r1] (raw file):
Again, not a good idea to instance.getId() here.

Comments from the review on Reviewable.io

@Machyne few same things you might want to check out.  Seems that isIP check will do the trick :)

Review status: 0 of 4 files reviewed at latest revision, 3 unresolved discussions.

Comments from the review on Reviewable.io

@imlucas - what's the logic for shying away from Instance.getId() here? I'm fine with changing though.
The reason I wanted it was for case normalization. Thoughts on using . toLowerCase()?

:shipit:

published in<EMAIL_ADDRESS>


Support Linux Consumption apps

This is the run-from-zip scenario where there will be no Kudu.
Any apps that are configured for Linux consumption should be published using run-from-zip, it's possible to detect the configuration.
The ARM app should look like
{
  ...
  "kind": "functionapp,linux",
  ...
  "properties": {
    ...
    "sku": "Dynamic",
    ...
  }
}

And the conditions to check for are:
app.kind.toLowerCase().indexOf('functionapp') !== -1 &&
  app.kind.toLowerCase().indexOf('linux') !== -1 &&
  app.properties.sku.toLowerCase() === 'dynamic'

Only thing left on this is to support this when creating function apps

Create will be tracked in this issue: https://github.com/Microsoft/vscode-azurefunctions/issues/587
Log stream will be tracked here: https://github.com/Microsoft/vscode-azurefunctions/issues/589
The other work was fixed in https://github.com/Microsoft/vscode-azurefunctions/pull/574 and https://github.com/Microsoft/vscode-azurefunctions/pull/577


ci: Change github UID from 3434 to 1001

CircleCI expected 3434; GitHub Actions expects 1001. This is the reason zulip-ci.yml currently needs to mess with the permissions in /__w.

Pushed the rebuilt images.


VAST/VPAID Waterfall on adserror

I've been researching it, but haven't found any concrete documentation on it.
How would I setup an IMA waterfall where I could put in X number of VAST/VPAID tags as pre-roll, and it would try each one until an ad is found. Or ping all of them and see which one returns an ad first - either would work.
TIA!

Currently this multiple-tag set-up isn't supported with the IMA SDK - the way we do this is with a single ad tag that returns multiple ads. We'll try to play the first, and if it fails move on to try to play the second, etc.

@shawnbuso so it's not possible to setup a waterfall with X number of different ad networks, even within a single ad tag?

@shawnbuso I tried what you suggested in the other issue, trying to use vast.xml and calling that single file with multiple networks within it. Maybe I formatted it incorrectly, but it wasn't firing anything, even 100% fill test tags from Google.
https://github.com/googleads/videojs-ima/issues/278
Appreciate any help you can provide to accomplish this kind of "waterfall" like approach.

@dingman that recommendation from #278 should still work - if you pass along the VAST response you created I can take a look and let you know if it looks ok.

Hi @shawnbuso thanks for the follow-up.
Here's what I have, which should provide 100% fill rates, but I'm not seeing any ads when I use this file as the adTagUrl

  | <?xml version="1.0" encoding="UTF-8"?>
-- | --
  | <vmap:VMAP xmlns:vmap="http://www.iab.net/videosuite/vmap" version="1.0">
  | <vmap:AdBreak timeOffset="start" breakType="linear" breakId="preroll">
  | <vmap:AdSource id="preroll-ad-1" allowMultipleAds="false" followRedirects="true">
  | <vmap:AdTagURI templateType="vast3"><![CDATA[https://pubads.g.doubleclick.net/gampad/ads?slotname=/124319096/external/ad_rule_samples&sz=640x480&ciu_szs=300x250&unviewed_position_start=1&output=xml_vast3&impl=s&env=vp&gdfp_req=1&ad_rule=0&vad_type=linear&vpos=preroll&pod=1&ppos=1&lip=true&min_ad_duration=0&max_ad_duration=30000&vrid=6496&cust_params=deployment%3Ddevsite%26sample_ar%3Dpremidpostpodbumper&url=https://github.com/videojs/videojs-contrib-ads/issues/117&video_doc_id=short_onecue&cmsid=496&kfa=0&tfcd=0]]></vmap:AdTagURI>
  | </vmap:AdSource>
  | </vmap:AdBreak>
  | <vmap:AdBreak timeOffset="start" breakType="linear" breakId="preroll">
  | <vmap:AdSource id="preroll-post-bumper" allowMultipleAds="false" followRedirects="true">
  | <vmap:AdTagURI templateType="vast3"><![CDATA[https://pubads.g.doubleclick.net/gampad/ads?slotname=/124319096/external/ad_rule_samples&sz=640x480&ciu_szs=300x250&unviewed_position_start=1&output=xml_vast3&impl=s&env=vp&gdfp_req=1&ad_rule=0&vad_type=linear&vpos=preroll&pod=1&bumper=after&min_ad_duration=0&max_ad_duration=10000&vrid=6496&cust_params=deployment%3Ddevsite%26sample_ar%3Dpremidpostpodbumper&url=https://github.com/videojs/videojs-contrib-ads/issues/117&video_doc_id=short_onecue&cmsid=496&kfa=0&tfcd=0]]></vmap:AdTagURI>
  | </vmap:AdSource>
  | </vmap:AdBreak>
  | </vmap:VMAP>
  |

Actually I think I got it, looks like a CORS restriction that I spotted on another site. I allowed CORS and it worked great.
Now the issue is, most of the tags I have, require macros to be replaced on runtime. Such as player-width, player-height, cachbuster, referrer, current page URL. Is it possible to pass those values to the XML file and process, without using some server-side logic? Wouldn't work for responsive either since that changes based on the screen size.
Thoughts?

Unfortunately that's not accessible :/ The IMA SDK doesn't provide access to the raw VAST response data, and doesn't have a window in which you can modify it before it makes the request.

I ended up rolling my own with some server-side processing to power the macros - https://www.jonathan.vc/tech/2017/08/setup-vastvpaid-waterfall-videojs
Thanks for all your help @shawnbuso!

@dingman I know you closed this issue but if you're interested we've developed a videojs plugin (for our Video Ad Analytics platform called Ad Tracer) that has a macro system that works client side.  Happy to discuss it more if you're still in need.

Hi @cameronchurch absolutely, I'm using a server-side solution right now, but something client side would be much more functional so it can be fully hosted on a CDN.
Are there any docs on the new feature?


ACCUMULO-4656

ACCUMULO-4656 new option for PrintInfo that provides index information

LGTM

I tried running this and though it was strange that the index was printed in the middle of the locality group info w/ no context.
Locality group           : <DEFAULT>
	Num   blocks           : 1
	Index level 0          : 29 bytes  1 blocks
	First key              : r1 f1:q1 []<PHONE_NUMBER>579 false
	Last key               : r1 f1:q5 []<PHONE_NUMBER>419 false
Key: r1 f1:q5 []<PHONE_NUMBER>419 false NumEntries: 4 Offset: 16 CompressedSize: 53 RawSize: 66
	Num entries            : 4
	Column families        : [f1]

Currently this only prints the lowest level of the index tree.  Could also print index entries for higher levels.  If interested, I could post a function that shows how this might be done.

It would be nice to see all levels, maybe indented appropriately.  Could go in a new section like the dump option does.

RE: Formatting comments
Agreed, the formatting is jarring as-is.  Does the below format look better to everyone?  I've added an "Index Entries" header, put the index of the IndexEntry on the left (double indented) and the IndexEntry information on the right, indented to line up with the other values in the print out.
I'd prefer to get consensus before changing the formatting so please let me know if you would like something other than what I've proposed below.  I'll try to make the code changes tomorrow.
Locality group           : <DEFAULT>
	Num   blocks           : 1
	Index level 0          : 29 bytes  1 blocks
	First key              : r1 f1:q1 []<PHONE_NUMBER>579 false
	Last key               : r1 f1:q5 []<PHONE_NUMBER>419 false
	Index Entries
		0              : Key: r1 f1:q5 []<PHONE_NUMBER>419 false NumEntries: 4 Offset: 16 CompressedSize: 53 RawSize: 66
		1              : Key: r2 f1:q5 []<PHONE_NUMBER>419 false NumEntries: 4 Offset: 16 CompressedSize: 53 RawSize: 66
	Num entries            : 4
	Column families        : [f1]I can add the indenting.

RE: printing multiple levels
I was interested in getting only the lowest level of the index for this ticket so that I could get some statistics on the rfile contents without reading the entire file.  Having multiple indexes might simplify certain types of analysis and complicate others.  It would be nice to be able to easily filter the lowest level.  Perhaps the level could be printed on the left hand side, like this:
	Index Entries
		L0,0              : Key: r1 f1:q5 []<PHONE_NUMBER>419 false NumEntries: 4 Offset: 16 CompressedSize: 53 RawSize: 66
		L0,1              : Key: r2 f1:q5 []<PHONE_NUMBER>419 false NumEntries: 4 Offset: 16 CompressedSize: 53 RawSize: 66

Overall it seems worthwhile though to provide more information.  I'd welcome Keith's offer of posting a function.  Feel free to adjust the PR with the suggested code if you'd like or I can modify it.
Thanks for the feedback.

@matthpeterson I tend to agree with other commenters. In my opinion you may want to add options to support showing all levels, lowest level, or an arbitrary level of the index tree. I've certainly needed the latter and it helps to print the information vice using a profiler to get it. The ticket's title is displaying index information, so that seems we should make it flexible to support more than just the lowest level.
I'm always supportive of @keith-turner writing functions...

I created matthpeterson/accumulo#1 which has a comment showing output

Thanks, Keith for the changes.  I think all comments are now addressed.

This is the check that failed in travis

[INFO] Format-string method java.io.PrintStream.printf(String, Object[]) called with format string "	%-22s :\n" wants 1 arguments but is given 2 in org.apache.accumulo.core.file.rfile.RFile$LocalityGroupMetadata.printInfo(boolean, boolean) [org.apache.accumulo.core.file.rfile.RFile$LocalityGroupMetadata] At RFile.java:[line 320] VA_FORMAT_STRING_EXTRA_ARGUMENTS_PASSED

I am fixing the issue noted above and will merge this now

@matthpeterson would you like to be added to the contributors list?  Either make a PR against https://github.com/apache/accumulo-website or let know what you listed


List of unrevised editings shows old stuff

see https://de.serlo.org/mathe/entity/unrevised

[ ] shows some old unrevised editings (2 years ago)
[ ] isn't sorted by timestamp

ping @inyono the old editings seem to be gone by now? Are you suggesting, only to show unrevised editings from a certain timespan?
Also might be related (or causing this): When there are multiple unrevised editings on the same entity, rejecting the newest one won't remove the entity from the list, since there are unrevised editings before that point. Annoyingly the link leads to the newest editing anyway, so it seems like it's already done when visited.
A solution might be to check only the newest version? Maybe this could also improve the load time of the page?

Might also be caused by #283, so showing the trash-bin instead of the unrevised edtitings?

@inyono Can we close this, assuming that the old entries weren't actually revisions, but from trash-bin (#283, which is fixed by now)?

Yes


Azure Application Gateway support / SSL termination

Hi,
I want to deploy Kubernetes on Azure and wanted SSL termination at load balancer level (typical as ingress object in Kubernetes).
As of now, only Azure Load Balancers (L4) are provisioned by acs. Is there a roadmap for supporting Application gateways ?
In the mean time, what is my best option to implement SSL offloading ? Eg. could I put an Application gateway in front of the loadbalancers ? or should I implement SSL termination myself by implementing an nginx container(s) specifically for this / or use something like 'dynamic SSL' plugin of Kong ?
Thx !

As a user, I'm hitting this exact need right now. I didn't try it yet, but my understanding is that I could/should be deploying nginx ingress-controller, with kube-lego to do the letsencrypt dance and get me certificates. The nginx ingress-controller would be exposed as a regular k8s service, through the Azure-LB.
If someone has more insight/workaround, or working yaml files, it would be great to share them! That is all ofc, till App-Gateway gets natively supported

+ @JargoonPard to comment on the status of azure-ingress-controller.

Sorry for the late response. I would suggest using the NGINX ingress controller at this point as @kim0 suggests.

This is out of scope for ACS-Engine.  Let's reconsider if you are able to create a patch and submit, or if there is more customer demand.

+1 as customer demand for have ALG as option for load balancing, mainly for SSL offloading and URL based routing.

+1. I need SSL offloading

+1 , some customers are not allowed to use kube-lego due to internal policies

+1 for SSL offloading


Error when generating widget

I'm using the Webstorm Javascript development environment, with my node / yeoman setup I get the following error when generating the widget, does anyone have an idea how to fix this?
  __  ____   __           _     _            _
 |  \/  \ \ / /          (_)   | |          | |
 | \  / |\ V /  __      ___  __| | __ _  ___| |_
 | |\/| | > <   \ \ /\ / / |/ _` |/ _` |/ _ \ __|
 | |  | |/ . \   \ V  V /| | (_| | (_| |  __/ |_
 |_|  |_/_/ \_\   \_/\_/ |_|\__,_|\__, |\___|\__|
                                   __/ |
                                  |___/
 Generator, version: 2.0.1
 Issues? Please report them at : https://github.com/mendix/generator-mendix/issues

events.js:160
      throw er; // Unhandled 'error' event
      ^

TypeError: this.env.adapter.prompt(...).then is not a function
    at constructor.Base.prompt (C:\Users\username\AppData\Roaming\npm\node_modules\generator-mendix\node_modules\yeoman-generator\lib\base.js:240:45)
    at constructor.prompting (C:\Users\username\AppData\Roaming\npm\node_modules\generator-mendix\generators\app\index.js:93:10)
    at Object.<anonymous> (C:\Users\username\AppData\Roaming\npm\node_modules\generator-mendix\node_modules\yeoman-generator\lib\base.js:439:23)
    at C:\Users\username\AppData\Roaming\npm\node_modules\generator-mendix\node_modules\run-async\index.js:26:25
    at C:\Users\username\AppData\Roaming\npm\node_modules\generator-mendix\node_modules\run-async\index.js:25:19
    at C:\Users\username\AppData\Roaming\npm\node_modules\generator-mendix\node_modules\yeoman-generator\lib\base.js:440:9
    at runCallback (timers.js:637:20)
    at tryOnImmediate (timers.js:610:5)
    at processImmediate [as _immediateCallback] (timers.js:582:5)

What is the version of Yeoman you are running? (yo version)
I'm running 1.8.5 and it works:
$ yo --version
1.8.5

Node version is v6.9.1
Yo version is 1.8.5.

You are running this from Webstorm or the command-line? It's weird. I have the same setup (node 6.9.1 and yo 1.8.5) and it works in my console.

I'm running it from the Webstorm start new project > Yeoman > Select the Mendix generator > click next and then it gives that error.

If i use it from the .cmd or terminal inside webstorm (which is .cmd) in an empty folder it works.

Can you please explain in steps how you use the 'yeoman generator selection'? Is this a plugin in WebStorm? If so, that might explain the problem, as in that it cannot answer any questions. Which would be a problem with Webstorm, instead of Yeoman.

Basically you select a project type, and then it allows for using installed generators.

I checked the issue and it seems that this is purely related to Webstorm and the way it interacts with the generator. Right now I can't fixed it, but I am investigating. Other generators also use the prompt and work in Webstorm, so there might be something I am missing right now.
The only thing I can see is that Webstorm doesn't accept adapter.prompt as a Promise. Other generators favor an callback style (which I don't). I'll see if I can rewrite this, using a callback (previous attempts failed)

This seems to be fixed in newer versions of WebStorm. Closing


how to connect via ssh to a localtunnel tunnel?

I'm trying to connect to a tunnel via ssh but it gives me access denied, any ideas?
Server
lt --port 22
https://chicken-12.loca.lt

client
ssh<EMAIL_ADDRESS><EMAIL_ADDRESS>password:
Permission denied, please try again.

Have the same issue.

Same issue here, I wish it gets fixed ASAP!!! The project is amazing and has a great potential!!!

Phew, I've spent so much time trying to figure out why I can't ssh into my MBP, but seems to be a localtunnel issue!

Ngrok?

Unfortunately, you can't ssh via localtunnel since localtunnel only tunnels HTTP/HTTPS traffic. Feel free to use something like ngrok (a general tcp tunnelling service)

Yes, I am facing the same issue. Hope, it gets fixed soon.

Unfortunately, you can't ssh via localtunnel since localtunnel only tunnels HTTP/HTTPS traffic. Feel free to use something like ngrok (a general tcp tunnelling service)

So Localtunnel doesnt support TCP like Ngrok does?


[5.6] Save empty array to database

PR as a bug reporting.

When I have the table with json_attribites column, then I should do attribute casting to the array.
But we have the problem with empty array saving to the database. It is saved as a [] instead of the {}

I have fixed this issue.
It is pretty the simular think as in https://github.com/laravel/framework/pull/24346 PR.

This would break my app. I have a JSON array field that I expect to be saved as an array even if it's empty.


[MdDatePicker] Validation gives no error state

Bug, feature request, or proposal:
Bug
What is the expected behavior?
When a minimum date is entered, the input should present an error state if the user enters a date before the minimum date in the input field.
What is the current behavior?
While the datepicker itself prevents the selection of a date before the minimum, the user can still manually enter a date before the minimum, which does not result in an error state.
What are the steps to reproduce?
In the following Plunk, enter a date before 01-01-2000. This Plunk comes directly from the Datepicker Docs page, only the mdError was added by me.
https://plnkr.co/edit/skksuwrpTwIMO0UYfrFd?p=preview
What is the use-case or motivation for changing an existing behavior?
The user should receive a visual cue when the input is incorrect.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
The issue is present in Material 2.0.0-beta.10

MdError shows based on whether the NgControl is valid. If you want to show error messages for invalid values, try hooking the control to a FormControl with a validator.

It seems an unrelated error and the wrong Google searches made me believe that the formControl property didn't work in conjunction with mdDatePicker. With that error resolved, the FormControl works. Closing since it's no longer a problem but simply user error on my part. Thank you for your time!