karpenter.k8s.aws/instance-family not working?

Is an existing page relevant?

What karpenter features are relevant?
So in this document https://karpenter.sh/v0.13.2/tasks/provisioning/ it indicate
   - key: karpenter.k8s.aws/instance-family
        operator: In
        values: [c5, m5, r5]

could limit the instance family. But after trying to add both in Provisioner or AWSNodeTemplate under spec -> requirements, both are not working. Checked the Customresourcedefinitions they are not defined as well.
How to make this working?
Same issue also happen to karpenter.k8s.aws/instance-size
How should the docs be improved?
Please indicate how to make it work
Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Can you provide your complete provisioner spec?
kubectl get provisioners -oyaml

So when I try to applied this on 0.13.2
apiVersion: karpenter.sh/v1alpha5 kind: Provisioner metadata:   name: default spec:   requirements:     - key: karpenter.sh/capacity-type       operator: In       values: ["spot", "on-demand"]   limits:     resources:       cpu: 100   provider:     requirements:       - key: karpenter.k8s.aws/instance-size         operator: NotIn         values: [nano, micro, small, large]     launchTemplate: xxxxxxxx     subnetSelector:       karpenter.sh/discovery: eks-shared   ttlSecondsAfterEmpty: 60
I got
Error from server (BadRequest): error when creating "provisioner_instance_size_not_working.yaml": admission webhook "validation.webhook.provisioners.karpenter.sh" denied the request: validation failed: strict decoder error for {"launchTemplate":"xxxxxxxxx","requirements":[{"key":"karpenter.k8s.aws/instance-size","operator":"NotIn","values":["nano","micro","small","large"]}],"subnetSelector":{"karpenter.sh/discovery":"eks-shared"}}: v1alpha1.AWS.ReadObject: found unknown field: requirements, error found in #10 byte of ...|uirements":[{"key":"|..., bigger context ...|xxxxxxxx","requirements":[{"key":"karpenter.k8s.aws/instance-size","operat|...:

apiVersion: karpenter.sh/v1alpha5
kind: Provisioner
metadata:
name: default
spec:
requirements:
- key: karpenter.sh/capacity-type
operator: In
values: ["spot", "on-demand"]
limits:
resources:
cpu: 100
provider:
requirements:
- key: karpenter.k8s.aws/instance-size
operator: NotIn
values: [nano, micro, small, large]
launchTemplate: xxxxxxxxxxxx
subnetSelector:
karpenter.sh/discovery: eks-shared
ttlSecondsAfterEmpty: 60

Since the document says the provider will be replaced soon, I tried
apiVersion: karpenter.k8s.aws/v1alpha1
kind: AWSNodeTemplate
metadata:
name: default
spec:
launchTemplate: xxxxxx
requirements:
- key: karpenter.k8s.aws/instance-size
operator: NotIn
values: [ nano, micro, small, large ]
subnetSelector:
karpenter.sh/discovery: eks-shared
also no luck

Those were applied
kubectl replace -f https://raw.githubusercontent.com/aws/karpenter/v0.13.2/charts/karpenter/crds/karpenter.sh_provisioners.yaml kubectl apply -f https://raw.githubusercontent.com/aws/karpenter/main/charts/karpenter/crds/karpenter.k8s.aws_awsnodetemplates.yaml

The requirements block is a list of requirements and is not duplicated in the Provider spec. You can include cloud-provider specific label requirements outside of the provider block like this:
apiVersion: karpenter.sh/v1alpha5
kind: Provisioner
metadata:
  name: default
spec:
  requirements:
  - key: karpenter.sh/capacity-type
    operator: In
    values: ["spot", "on-demand"]
  - key: karpenter.k8s.aws/instance-size
    operator: NotIn
    values: [nano, micro, small, large]
limits:
  resources:
    cpu: 100
provider:
  launchTemplate: xxxxxxxxxxxx
  subnetSelector:
    karpenter.sh/discovery: eks-shared
ttlSecondsAfterEmpty: 60

Feel free to reopen if the above is still not working for you! :)

It works! Thank you very much Brandon.
But does it means document under https://karpenter.sh/v0.13.2/tasks/provisioning/ is wrong?


Update About Lux:  History of Digital Collaboration

Problem Description:
The History of Digital Collaboration among Yale’s Libraries, Museums, and ITS
section of About LUX needs to be updated to include the 2024 work.
Expected Behavior/Solution:

Updated the History of Digital Collaboration among Yale’s Libraries, Museums, and ITS section with the 2024 work

Requirements:

the History of Digital Collaboration among Yale’s Libraries, Museums, and ITS section will include a new title "2024" and bullet points with its 2024 work.

Needed for promotion:
If an item on the list is not needed, it should be crossed off but not removed.

[ ] ~Wireframe/Mockup - Mike~
[ ] Committee discussions - Sarah
[ ] Feasibility/Team discussion - Sarah
[ ] Backend requirements - TBD
[ ] Frontend requirements- TBD
[ ] ~Are new regression tests required for QA - Amy~
[ ] Questions
List of questions for discussions. Answers should be documented within the issue.

UAT/LUX Examples:

https://lux-front-tst.collections.yale.edu/content/collaboration-history

Dependencies/Blocks:
N/A
Related Github Issues:
N/A
Related links:

Bugherd: https://www.bugherd.com/projects/284041/tasks/2117
Bugherd: https://www.bugherd.com/projects/284041/tasks/2550
Document:  https://drive.google.com/drive/u/0/folders/1VnZtvSkYUMRNlA9D7-sEWI_7VDmht4Jx

~Wireframe/Mockup:~
~Place wireframe/mockup for the proposed solution at end of ticket.~

@roamye - can you transfer the text to a google doc that we can co-edit?

@prowns - yeah I put it within the UX/BA folder: https://docs.google.com/document/d/1QmgjoHofAgzcQkjnYoxi8ujt64Zu-5jwp32saU7r7JE/edit?usp=drive_link

@prowns - pretty sure this can be closed? yes?


Dialog: add opened event

Closes #12798
Please make sure these boxes are checked before submitting your PR, thank you!

[ ] Make sure you follow Element's contributing guide (中文 | English | Español).
[ ] Make sure you are merging your commits to dev branch.
[ ] Add some descriptions and refer relative issues for you PR.

西班牙语文档没有更新。


Get microphone stream

Hello,
I have an issue when I would get my microphone audio. I need to get audio to send to a stream. But the audio tape is not correct. I have no sound or I have some noise..
In my example, I write in file and I use ffmpeg to create a wav file:
ffmpeg -f s16le -ar 16000 -ac 1 -i test.pcm file.wav
I needs pcm_s16le encoding only..
What is my misstake? There is not much documentation.. (I saw the example in readme.md, but it didn't help me much)
My code is here:
PortAudioSharp.Stream s;

PortAudioSharp.PortAudio.Initialize();

s = new PortAudioSharp.Stream(new StreamParameters()
    {
        device = PortAudioSharp.PortAudio.DefaultInputDevice,
        channelCount = 1,
        sampleFormat = SampleFormat.Int8,
        suggestedLatency = PortAudio.GetDeviceInfo(PortAudioSharp.PortAudio.DefaultInputDevice)
            .defaultLowInputLatency,
        hostApiSpecificStreamInfo = IntPtr.Zero
    },
    null,
    16000,//44100, //8000,
    (uint) 0,
    StreamFlags.ClipOff// | StreamFlags.DitherOff
    , Callback, IntPtr.Zero);

private StreamCallbackResult Callback(IntPtr input, IntPtr output, uint framecount, ref StreamCallbackTimeInfo timeinfo, StreamCallbackFlags statusflags, IntPtr userdataptr)
{
    int buffersize = (int) (framecount);

    byte[] samples = new byte[buffersize];

    Marshal.Copy(input, samples, 0, (Int32)buffersize);

    //Duration += (int) 0;//100;

    //dynamic audio = JsonConvert.DeserializeObject<object>(
    //    "{\n  \"object\": \"audio_chunk\",\n  \"payload\": \"ZXhhbXBsZQ==\",\n  \"stream_id\": \"flux_medecin\"\n}");

    var op =<EMAIL_ADDRESS>FileMode.Append);

    op.Write(samples);
    op.Flush();

    op.Close();

    //audio.payload = Convert.ToBase64String(samples);

    //client.SendAsync(new ArraySegment<byte>(Encoding.UTF8.GetBytes(JsonConvert.SerializeObject(audio))), WebSocketMessageType.Text, true, CancellationToken.None).Wait();

    return StreamCallbackResult.Continue;
}

Yes, it's my misstake.. I have to use int16 (short).
Thank you very much ;)
Have a nice day


Remove unnecessary commented code

https://github.com/Maxim280596/yo-smart-contracts/blob/ac6c8c8bbf57500db43845ee5771cfe2ab88496d/test/yo.test.ts#L711-L908

removed


Microsite is not available

I remember not that long time ago I used to send links to https://fs2-rabbit.profunktor.dev/ and it was working, but since the last week it is not loading. I wonder did something break the publishing to Github Pages or something else? Do you need a hand to fix it?

Weird... It works for me. Try cleaning up your cache?

Uh oh this is awkward! You are right. After I removed a file /etc/resolver/dev that was created by early versions of Docker for Mac (found a commit of its removal) the host started to resolve. Who knew .dev domain became available in 2019 and they all never loaded for me on this machine due to the early resolver docker left 😆
nameserver <IP_ADDRESS>

I am sorry!


Feature: Flashes: Moving flashes to Graphics; Slowing scrolling background during Air Force fight and Baren falls; add minimap high contrast option

Moving Remove Flashes from Misc to Graphics, so that they don't affect the seed. Converted all event flash changes from NOPS to Flash None (55 00).
Slowing scrolling background on Falling through clouds and Baren Falls backgrounds.
Video test of scrolling background changes:
https://www.youtube.com/watch?v=dw1HBKfxsw4 (note: this was an earlier change to Baren Falls with no palette swap changes)
https://www.youtube.com/watch?v=zDM8iaGub8w (this reflects the latest change to Baren Falls with the palette swap change)
Tested Misc->Graphics change by rolling seeds with 4 random characters but same -s. Ensured that the same random characters appeared regardless of having -frm, -frw, or neither of them.
-wmhc (World Minimap High Contrast):

Changed boss flash removal to only flash the monster sprite:
Boss Death: https://www.youtube.com/watch?v=Tl8HXJEFmQc&ab_channel=SilverThorn
Kefka death: https://www.youtube.com/watch?v=fYXLS3BXDcY&ab_channel=SilverThorn

Merged into ff6wc fork


Local Wakeword Detection not working

I'm running a Raspberry Pi 4 with openwakeword.
As soon as i add the options
      - "tcp://openwakeword:10400"
      - "--wake-word"
      - "ok_nabu"

to my docker container config the wakeword detection stops working.
If i remove it and use the remote one on the server, all is fine.
here's my docker config for these:
services:
  satellite:
    container_name: satellite
    depends_on:
      - openwakeword
    build:
      context: ./satellite/wyoming-satellite
      dockerfile: Dockerfile
    ports:
      - "10700:10700"
    devices:
      - /dev/snd:/dev/snd
    environment:
      - "PULSE_SERVER=tcp:<IP_ADDRESS>:4713"
    restart: unless-stopped
    command:
      - "--name"
      - "my satellite"
      - "--uri"
      - "tcp://<IP_ADDRESS>:10700"
      - "--mic-command"
      - "arecord -D plughw:CARD=OSM09,DEV=0 -r 16000 -c 1 -f S16_LE -t raw"
      - "--snd-command"
      - "paplay --device=alsa_output.platform-soc_sound.stereo-fallback --format=s16le --rate=22050 --channels=1 --raw"
      - "--awake-wav"
      - "./sounds/awake.wav"
      - "--detection-command"
      - "./get_loopback.sh module-loopback.c 0%"
      - "--tts-stop-command"
      - "./get_loopback.sh module-loopback.c 100%"
      - "--wake-uri"
      - "tcp://openwakeword:10400"
      - "--wake-word"
      - "ok_nabu"
      - "--debug"

openwakeword:
    container_name: openwakeword
    image: rhasspy/wyoming-openwakeword
    volumes:
      - ./wakeword/config:/data
      - ./wakeword/config:/custom
      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
    environment:
      - TZ=America/Los_Angeles
    command: --preload-model "ok_nabu" --debug
    restart: unless-stopped
    expose:
      - 10400/tcp

I think the flag is actually '--wake-word-name' - it hasn't been updated in the README yet.

README has been updated 👍

Unfortunately, it doesn't appear to be working even with the correct flag.
If i exclude the flag alltogether, and just include the wake-uri, then it seems to work - but the detection triggers over and over again until i physically mute the microphone.

Unfortunately, it doesn't appear to be working even with the correct flag.
If i exclude the flag alltogether, and just include the wake-uri, then it seems to work - but the detection triggers over and over again until i physically mute the microphone.

i am not using local wake word , and the problem you discribe is correct , it doesnt shutdown until muted here is the issue   - https://github.com/rhasspy/wyoming-satellite/issues/9

Remove just this from the command and see if it works --wake-word-name 'ok_nabu   ......., i had the same problem ,after removing the wake word command it will use the wake word from the wake uri , for now its a work arround until its fixed !!

I tried that, is it supposed to log that it detected the wake word, cause even with or without that flag, nothing gets put in the log for either applications, no matter how many times I say ok nabu

I tried it one more time and its still not working, this is without --wake-word-name
seion@rpvadownstairs:/opt/wyoming-satellite $ script/run --name 'downstairs satellite' --uri 'tcp://<IP_ADDRESS>:10700' --mic-command 'arecord -r 16000 -c 2 -f S16_LE -t raw' --snd-command 'aplay -r 22050 -c 2 -f S16_LE -t raw' --wake-uri 'tcp://<IP_ADDRESS>:10400' --debug
DEBUG:root:Namespace(mic_uri=None, mic_command='arecord -r 16000 -c 2 -f S16_LE -t raw', mic_command_rate=16000, mic_command_width=2, mic_command_channels=1, mic_command_samples_per_chunk=1024, mic_volume_multiplier=1.0, mic_noise_suppression=0, mic_auto_gain=0, snd_uri=None, snd_command='aplay -r 22050 -c 2 -f S16_LE -t raw', snd_command_rate=22050, snd_command_width=2, snd_command_channels=1, snd_volume_multiplier=1.0, wake_uri='tcp://<IP_ADDRESS>:10400', wake_word_name=[], wake_command=None, wake_command_rate=16000, wake_command_width=2, wake_command_channels=1, vad=False, vad_threshold=0.5, vad_trigger_level=1, vad_buffer_seconds=2, vad_wake_word_timeout=5.0, event_uri=None, startup_command=None, detect_command=None, detection_command=None, transcript_command=None, stt_start_command=None, stt_stop_command=None, synthesize_command=None, tts_start_command=None, tts_stop_command=None, streaming_start_command=None, streaming_stop_command=None, error_command=None, awake_wav=None, done_wav=None, uri='tcp://<IP_ADDRESS>:10700', name='downstairs satellite', area=None, no_zeroconf=False, zeroconf_name=None, zeroconf_host=None, debug=True)
INFO:root:Ready
DEBUG:root:Detected IP: <IP_ADDRESS>
DEBUG:root:Zeroconf discovery enabled (name=d83addb986fc, host=None)
DEBUG:root:Connecting to mic service: ['arecord', '-r', '16000', '-c', '2', '-f', 'S16_LE', '-t', 'raw']
DEBUG:root:Connecting to snd service: ['aplay', '-r', '22050', '-c', '2', '-f', 'S16_LE', '-t', 'raw']
DEBUG:root:Connecting to wake service: tcp://<IP_ADDRESS>:10400
INFO:root:Connected to services
Recording raw data 'stdin' : Signed 16 bit Little Endian, Rate 16000 Hz, Stereo
DEBUG:root:Connected to mic service
DEBUG:root:Connected to wake service

DEBUG:root:Server set:<PHONE_NUMBER>828
INFO:root:Waiting for wake word

^CAborted by signal Interrupt...

seion@rpvadownstairs:/opt/wyoming-openwakeword $ script/run   --uri 'tcp://<IP_ADDRESS>:10400'   --preload-model 'ok_nabu' --debug                                   DEBUG:root:Namespace(uri='tcp://<IP_ADDRESS>:10400', models_dir=PosixPath('/opt/wyoming-openwakeword/wyoming_openwakeword/models'), custom_model_dir=[], preload_model=['ok_nabu'], threshold=0.5, trigger_level=1, output_dir=None, debug=True, debug_probability=False, model=[])
DEBUG:root:Loading ok_nabu_v0.1 from /opt/wyoming-openwakeword/wyoming_openwakeword/models/ok_nabu_v0.1.tflite
DEBUG:wyoming_openwakeword.handler:Started thread for ok_nabu_v0.1
DEBUG:root:Loading /opt/wyoming-openwakeword/wyoming_openwakeword/models/melspectrogram.tflite
DEBUG:root:Loading /opt/wyoming-openwakeword/wyoming_openwakeword/models/embedding_model.tflite
INFO:root:Ready

DEBUG:wyoming_openwakeword.handler:Client connected:<PHONE_NUMBER>937
INFO: Created TensorFlow Lite XNNPACK delegate for CPU.
DEBUG:wyoming_openwakeword.handler:Client disconnected:<PHONE_NUMBER>937

Ok it works if I run both as root... even with --wake-word-name

Actually I think mine has something to do with the .asoundrc I created, root does not have it, so might be something to do with the device

Mine works if without root and removed my .asoundrc which I thought was defaulting my device to the WM8960_Audio_HAT I have.

Did some more testing, and local openwakeword works for me. But it is imperative that I specify the wake-word on the satellite with --wake-word-name for it to work properly. Otherwise, it will still detect the wake-word, but will repeatedly trigger the awake-wav sound and listen for a command until I kill the satellite connection to openwakeword. using that flag, it works without issue.
However, I guess we could say it is almost 'continuous conversation' in that the satellite immediately listens for commands again without a wake-word? :smile:

Did some more testing, and local openwakeword works for me. But it is imperative that I specify the wake-word on the satellite with --wake-word-name for it to work properly. Otherwise, it will still detect the wake-word, but will repeatedly trigger the awake-wav sound and listen for a command until I kill the satellite connection to openwakeword. using that flag, it works without issue.
However, I guess we could say it is almost 'continuous conversation' in that the satellite immediately listens for commands again without a wake-word? 😄

Unfortunately, as soon as i specify --wake-word-name i get no detection. Very strange. Can you post your whole command?

I am also running without Docker at the moment (containers not available when I set it up), but it works for me on Pi4 with a USB speakerphone.  After following the install instructions, for wyoming-openwakeword and wyoming-satellite;
start openwakeword with  script/run --uri 'tcp://<IP_ADDRESS>:10400'
start the satellite with
script/run \
  --debug \
  --name 'FR satellite' \
  --uri 'tcp://<IP_ADDRESS>:10700' \
  --mic-command 'arecord -D plughw:CARD=P20,DEV=0 -r 16000 -c 1 -f S16_LE -t raw' \
  --snd-command 'aplay -D plughw:CARD=P20,DEV=0 -r 22050 -c 1 -f S16_LE -t raw' \
  --wake-uri 'tcp://<IP_ADDRESS>:10400' \
  --wake-word-name 'ok_nabu' \
  --awake-wav sounds/awake.wav \
  --done-wav sounds/done.wav \
  --mic-auto-gain 5 \
  --mic-noise-suppression 2

Cheers.

@Fraddles Ok well that pointed me into a different and interesting direction!
running the openwakeword in docker locally appears to not work out right. If i run the openwakeword in script and the satellite in docker - all appears to work just fine!
something strange appears to be going on.

I've discovered that the newest version of the wyoming-openwakeword library is needed for this feature. I'm not sure what exactly the change is - but all is well after updating.
@synesthesiam i've submitted the MR above in wyoming addons that resolves this for me.
thanks for the help everyone!


Pipewalker depends on SDL 1.2

Pipewalker depends on SDL version 1.2, which is unmaintained upstream. Some Linux distributions, such as Debian, will likely drop support for SDL 1.2 in the near future^1.
If possible, please consider porting it to SDL 2. There is a migration guide written by the SDL maintainers about the process^2. As the package maintainer for pipewalker in Debian, I will test it against libsdl1.2-compat-shim anyway, to check if it would work on SDL 2 through this shim.

Hi, @yselkowitz! Thanks a lot for the heads up! This is good news, especially if migration to SDL 2 isn't feasible. I will try to test it on Debian asap and hope to report the same to the Debian SDL packages maintainers.

I've ported a game from SDL1 to SDL2 before, so I can take a look at this. No promises regarding the timeline, though.

@artemsen What's the status of the next branch, though? Commit 852b64bad2acf30c11670a82cb7abe18c5fb3667 on said branch seems to include porting the game to SDL2.

status of the next branch

It was a failed attempt at code refactoring.
I was done with the game logic, but UI and SDL made me give up.

so I can take a look at this

I'd appreciate it!
But I am not sure it is possible without refactoring the project's architecture.


Can't enter anything through keyboard. Mouse works

Version: 1.0.128   Version: 1.0.129  and Version: 1.0.130
Platform: win32 10.0.14393
Plugins: none
I rollback to Version: 1.0.127 which works fine.

Same for me. I'm attaching the console output. Every time I type a key, it throws the following error:
`Uncaught Error: This socket has been ended by the other party
at Socket.writeAfterFIN [as write] (net.js:456)
at WindowsTerminal._doWrite (C:\Program Files\Terminus\resources\app.asar\node_modules@terminus-term\node-pty\lib\windowsTerminal.js:114)
at WindowsTerminal._defer (C:\Program Files\Terminus\resources\app.asar\node_modules@terminus-term\node-pty\lib\windowsTerminal.js:156)
at WindowsTerminal._write (C:\Program Files\Terminus\resources\app.asar\node_modules@terminus-term\node-pty\lib\windowsTerminal.js:111)
at WindowsTerminal.Terminal.write (C:\Program Files\Terminus\resources\app.asar\node_modules@terminus-term\node-pty\lib\terminal.js:81)
at Session.write (C:\Program Files\Terminus\resources\builtin-plugins\terminus-terminal\dist\index.js:12988)
at TerminalTabComponent.sendInput (C:\Program Files\Terminus\resources\builtin-plugins\terminus-terminal\dist\index.js:8736)
at SafeSubscriber._next (C:\Program Files\Terminus\resources\builtin-plugins\terminus-terminal\dist\index.js:8964)
at SafeSubscriber.__tryOrUnsub (C:\Program Files\Terminus\resources\app.asar\node_modules\rxjs\internal\Subscriber.js:205)
at SafeSubscriber.next (C:\Program Files\Terminus\resources\app.asar\node_modules\rxjs\internal\Subscriber.js:143)
`
TerminusFailure.log

Duplicate of #3397


The source field for Diagnostics shouldn't be relative Uri

It should be a human readable string
https://github.com/TypeFox/ls-api/blob/e83d3dde2d5bd5e2bb261779d5bfc3df1f7a0366/io.typefox.lsapi/src/main/java/io/typefox/lsapi/Diagnostic.xtend

We should just use the default groovyc all the time.


python3Packages.nltk: 3.4.4 -> 3.4.5 (security)

Motivation for this change
https://www.nltk.org/news.html
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Notify maintainers
cc @

:+1:  Built and tested locally. Thanks for the PR.

release-19.03 has 3.2.5.
From http://www.nltk.org/news.html it looks like it should be safe to upgrade to 3.4.5 (only api additions). Unless you have a reason not to backport it, I’ll do it shortly.


Deprecate tempdir

tempfile 3.0 supports the functionality of tempdir, switch to it.
https://github.com/rust-lang-nursery/tempdir#deprecation-note
https://github.com/Stebalien/tempfile/blob/master/NEWS

The code now uses tempfile, I'm guessing this issue can be closed?


ERROR: 404

Hello, when I want to download black clover (all episodes) it gives me this error
Thanks in advance

use a different provider (animekisa is no longer supported)

Which one can I use?

Uhh
twist.moe I guess

I would like to see the episodes in vostfr but I have tried several links but they don't work

I just used vostfree it works thanks for the help, I have a question how I can change the download location?

I just used vostfree it works thanks for the help, I have a question how I can change the download location?

anime config then go to dl, then download_dir


Pidp-1056 Back to top misalignment

were we able to test this on iOS successfully?

We didn't tested with PR-number url in ios. We faced issues while using the PR-number url in mobile device.
Discussed to test css fix in the dev environment in ios.


Kotlin Random Number should discuss Secure Random

https://www.baeldung.com/kotlin-random-number
This writeup doesn't discuss Secure Random or the impacts of not using a Secure Random number generator when non-predictable randomness is needed.
Related:
https://github.com/Kotlin/KEEP/issues/184

@JLLeitschuh We have logged an internal ticket to update the article. I'll keep this ticket updated with our progress.

Thanks! Given the risks of using an insecure RNG in a security critical location, I recommend highlighting it first.

Before 1.3, on the JVM we use Random or even ThreadLocalRandom if we're on JDK > 1.6.
fun IntRange.random() =
Random().nextInt((endInclusive + 1) - start) + start
Used like this:
// will return an Int between 0 and 10 (incl.)
(0..10).random()

@JLLeitschuh We added a new 'Pseudo vs Secure Random Number Generators' section to the article. Thanks for bringing this to our attention.

Molkki Drama Serial All Episodes, Colors Tv Voot Drama Molkki Watch Online at Mx Player Latest Episodes, Molkki Apne Tv Desi Serial indian Drama HD ...

Molkki Drama Serial All Episodes, Colors Tv Voot Drama Molkki Watch Online at Mx Player Latest Episodes, Molkki Apne Tv Desi Serial indian Drama HD ...


fix: Back out "Combine low selectivity vectors generated by the hash join filter"

The PR introduced memory leak in Velox system. Reverting it to unblock.
Summary:
Original commit changeset: e8e54e7be1b5
Original Phabricator Diff: D65949331
Differential Revision: D66484385

Hello @tanjialiang ,
May I know the reason to revert this commit, is there any issue you observed?
Thanks.

Got it. If you could provide some reproducible cases through unit tests, I'd be happy to take a closer look also.


Building pip pkg for different architectures (OSX vs Ubu)

Is there any documentation on using bazel to build pip pkgs for different architectures? The compiled custom-op.so contains different ELF headers.

Glad you got it working.
This sounds like a bazel question :). I think you can use the --platforms flag https://docs.bazel.build/versions/master/platforms.html#specifying-a-platform-for-a-build


langchain 0.3.12

Destination channel: defaults
Links

PKG-6020
Upstream repository
Upstream changelog/diff

Explanation of changes:

Update version
Remove Snowflake abs.yaml

@bwingconda I've updated the dependences. I feel it's better to keep the continuity between the defaults version and the snowflake version. They aren't enabling tests, so we shouldn't either.


Should we set all uID attributes to use="required"?

For example in the wing componentSegment branch, the definition of the uID attribute is not consistent. Sometimes the attribute uID is set to required sometimes optional.
As uIDs are used for referencing throughout the CPACS structure, shouldn't it be mandatory to define a uID for all elements that can be referenced?
The current state requires going back and forth between the defined elements always setting the uID once a reference to this element is required, since one probably forgets setting it when creating the element. Currently it requires the user to have in mind all the elements that might have an uID attribute in order to distinguish those from the elements that do not have an uID attribute.
In my opinion it would be much more straight forward when creating a new CPACS file based on the schema that all uID attributes are required and have to be filled in during creation of the respective element.

Thank you for that comment. I totally agree.
All the uID attributes should be mandatory. I appointed this task to the next release. I guess it should be straight forward to change that.

DLR-BT agrees to finally set all uID definitions to required. This may cause some uID atrtributes in the schema to be deleted, when they are not really required


Set up a "Hello world" project with two apps

I did the following on this Feature Branch:
RAILS-BACKEND

Create a new Rails API app called 'hello-rails-back-end'.
Initialize your project with Git.
Make sure that your project has a Postgres database set up.
Create a table for storing your messages and create 5 different greetings.
Create an API endpoint that selects a random greeting from your table (you will need a controller with an action and rails route).

REACT-FRONTEND

Create a new React app called 'hello-react-front-end'
Initialize your project with Git.
Create the App component with react-router.
Create the Greeting component that will display a greeting. Set it up as a route in your App component.
Create a store, an action and a reducer that will connect to you API endpont to get the random greeting.
Display the random greeting in your Greeting component.
PROJECT LINK: HELLO-REACT-FRONT-END
PULL REQUEST LINK: HELLO-REACT-FRONT-END

Hi @Osoro254Alex
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
Kindly remove live demo and video demo sections from the readme file since it does not apply to this project.
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


Crashing, bad settings.

So both my style and target pic are 3000x2000 pixels.
My preset_xml is set to ...
  <sprite_w>1000</sprite_w>
  <sprite_n>6</sprite_n>

and yet it always crashes like this,
[3000 x 2000]x4
[3000 x 2000]x3
libc++abi.dylib: terminating with uncaught exception of type cv::Exception: OpenCV(4.5.0) /tmp/opencv-20201123-26930-m95s1u/opencv-4.5.0/modules/core/src/matrix.cpp:473: error: (-215:Assertion failed) 0 <= roi.x && 0 <= roi.width && roi.x + roi.width <= m.cols && 0 <= roi.y && 0 <= roi.height && roi.y + roi.height <= m.rows in function 'Mat'

Abort trap: 6

I am attempting to create images that are made of recognisable fragments, so I want my sprite width to be quite big, and for the target image to be recognisable, but part style image... a bit like this picture of David Cameron UK MP.
https://www.inprnt.com/gallery/everythingability/pigs-ears-3/
It's the halfwayness I like...

Which is correct isn't it?

width = 3000
height = 2000
u = 1000
(width/u)*(height/u)
6.0

Hi @everythingability,
Thanks for reporting this issue!
From the looks of it, I think it is because the sprite height is >= half of the canvas height, so one of the computed regions gets a height of zero, causing openCV to be unhappy.
Maybe try with canvas dimensions 3001 x 2001 ?
I will try to reproduce the issue when I get some time

The 3001 x 2001 trick didn't do it... this exr got made.. but then still...

settings file loaded.
[3001 x 2001]x4
[3001 x 2001]x3
libc++abi.dylib: terminating with uncaught exception of type cv::Exception: OpenCV(4.5.0) /tmp/opencv-20201123-26930-m95s1u/opencv-4.5.0/modules/core/src/matrix.cpp:473: error: (-215:Assertion failed) 0 <= roi.x && 0 <= roi.width && roi.x + roi.width <= m.cols && 0 <= roi.y && 0 <= roi.height && roi.y + roi.height <= m.rows in function 'Mat'

Just as note, why should I have to define   <sprite_n>24</sprite_n> ?  Basically if I say it is 400 then the code could figure out how to fit that in, left to right, top to bottom, on whatever sized image(s)... and if I chose to have bits missing, that's down to me.

sprite_n is necessary because say you have 1021 sprites, you may want to do a grid of 3232=1024 and tell the program to omit the last 3 cells, instead of having a 11021 spritesheet.

Ah... yeah I get it...  Would it be possible to generate a mask file, like the one above, then edit it manually... to create more irregular shapes (like jigsaw pieces) or even a thresholded photo.. then pass that in as a param, rather than those regular ellipses?

Ah... yeah I get it...  Would it be possible to generate a mask file, like the one above, then edit it manually... to create more irregular shapes (like jigsaw pieces) or even a thresholded photo.. then pass that in as a param, rather than those regular ellipses?

Here are my project files, not that I expect you have time, just in case it sheads light on things...
https://www-users.york.ac.uk/~tas509/pmst-project.zip

Here are my project files, not that I expect you have time, just in case it sheads light on things...
https://www-users.york.ac.uk/~tas509/pmst-project.zip


componentDir not working with moduleResolution node

Hi,
Using a separate folder for front end components doesn't currently work with moduleResolution node. I tried to track down the bug and found my way to the resolve-specifier-node.ts file in polymer-analyzer where the resolve call always seems to fail because it's not looking in the correct location or componentInfo is undefined.

Rescuing from ‘stale’ with this message, please ignore.

Still experiencing this. Rescuing from ‘stale’ with this message, please ignore.


Fatal error, when collecting coverage on PHP 5.6

When I run PHPUnit 5.4.2 on PHP 5.6 using Paratest I'm getting following errors:
PHP Catchable fatal error:  Argument 1 passed to ParaTest\Coverage\CoverageMerger::addCoverage() must be an instance of PHP_CodeCoverage, instance of SebastianBergmann\CodeCoverage\CodeCoverage given, called in /home/travis/build/qa-tools/qa-tools/vendor/brianium/paratest/src/ParaTest/Runners/PHPUnit/BaseRunner.php on line 212 and defined in /home/travis/build/qa-tools/qa-tools/vendor/brianium/paratest/src/ParaTest/Coverage/CoverageMerger.php on line 12

See https://travis-ci.org/qa-tools/qa-tools/jobs/135858201
This seems to be a recent issue, because last week that build passed.

Did you try 0.13.2 or dev-master?
https://github.com/brianium/paratest/pull/207 is addressing this problem but currently wip

Did you try 0.13.2 or dev-master?

Nope. It's not that bad, because strangely test on all other PHP versions pass.

#207 is addressing this problem but currently wip

I'll just wait for it to be finished then. Or maybe lock to a specific PHPCov version.

Fixed in https://github.com/brianium/paratest/pull/208

At lest the Or maybe lock to a specific PHPCov version. is now done by paratest. For phpcc 4 support we have #211


Enable the ESLint no-var rule in the examples/ folder

Please refer to the individual commit messages for additional details.

Thank you for doing this!


fcft: 2.3.2 -> 2.3.3

Motivation for this change
https://codeberg.org/dnkl/fcft/releases/tag/2.3.3
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@ofborg build foot fuzzel

Result of nixpkgs-review pr 119431 at 70ab02ad run on x86_64-linux 1

5 packages built successfully:

fcft
foot
fuzzel
wbg
yambar


Plugged My S23 Into My Laptop and the App Keeps Crashing

Description
I plugged my S23 into my laptop to copy some videos I had made when I got a notification that Files ran into a problem that the developers didn't plan for yet. While my phones plugged in the app won't open. As soon as I unplug my phone the app opens just fine.

Steps To Reproduce

Open Files app like normal
Plug a USB cable into your laptop or PC
Plug the other end of the USB cable into your S23
App should encounter a problem

Requirements

e.g. Fix crash that occurs when...
My expected behavior was that the app would continue to work as intended. That my S23 would appear under Device's and Drives just like it does within Windows Files Manager and that I would be able to access the storage on my device to copy, move and delete files stored on my phone.

Files Version
<IP_ADDRESS>
Windows Version
Windows 11 22H2 22621.1
Log File
debug.log

Thanks for the report, I've added this to the project board.

This may be the same issue as #12370.
@MMZThumper could you try disabling some of the widgets to see if the crash can be avoided?

@MMZThumper this issue will be resolved in the upcoming v2.5.20 release.


Use ExceptionDescription in TypeScript client

Use response description as a custom message in error class (exceptionClass).

Thank you!


Add remaining sqllogictest test files

@bogensberger please review

Current coverage is 81.13% (diff: 100%)

Merging #4438 into master will increase coverage by 0.03%

@@             master      #4438   diff @@
==========================================
  Files          1304       1304
  Lines         44201      44201
  Methods           0          0
  Messages          0          0
  Branches       7040       7040
==========================================
+ Hits          35849      35863    +14
+ Misses         5664       5660     -4
+ Partials       2688       2678    -10

Powered by Codecov. Last update 5c7121c...13430e2


Do we have a plan to support ARTERY(雅特力) MCU?

Do we have a plan to support artery mcu， especially AT32F435/437 ？
想问下，接下来NUTTX有计划支持雅特力的MCU吗？特别是新出的 AT32F435/437

It depends on manufacture.

@TompsonTan you can ask the manufacturer to add support, this is the only way they know that there are users for it! If you have a company and want to create some product with it your chance to get attention will increase!

OK, thank you.


[83] Add support for RS256

Hi, I've added support for JWS RS256 algorithm. It's trivial and is needed for my project.
Let me know if you have any questions.
Changes:

Support for encoding/decoding JWS RS256
Tests
Updated Readme.md

Hi @turbulem 👋
Thanks, that's awesome! I'll have a look later today so we can merge this asap.

Thank you for fast release!


Float Capability

Similar to how position: absolute works in CSS it would be very useful if you could define a float boolean to have it ignore the parent's matrix when updating the transform.  This would give the ability to render on-screen with absolute positioning instead of being dependent on its parental hierarchy.

What is the use-case of having an object be a child of another object when you don't want the transforms shared? Just alpha?

@englercj No, it's useful for situations of encapsulation (component grouping) while still allowing something to be positioned absolutely.  In my specific use-case at the moment it's more about toggling between being fixed in the layout and floating apart from the layout.

I don't like the idea of adding a float property in v4, but I will try to consider this use-case in v5 as we refactor.

it shouldn't be a difficult addition since it would just ignore the parent's worldMatrix when updating the transform it's just impossible to accommodate without it being explicitly supported in Pixi.

It isn't that it is difficult, it just seems out of scope. The purpose of the scene-tree in pixi is to parent transforms. If you are grouping in a way that doesn't want those transforms grouped, that is an application-level concept.
Additionally, adding another branch to our already strained update loop is probably a no-go.

@englercj it's entirely a distinction of encapsulation vs transformation.  If I want to create a simple component that can be reused but has many parts to it, it's not unreasonable to want those parts to be contained in that component, but not to necessarily be positioned in the same hierarchical transformation.  I could create a simple PR that has like five lines of code to support this.

What about adding DisplayObject functions localToGlobal(pt) and globalToLocal(pt) so that at least it's easier to translate a global space coordinates to nested display objects?

@bigtimebuddy that wouldn't really solve my problem though would it?  I want my object to ignore the parent matrix entirely.

The globalToLocal approach would allow you to translate a position, but, yes, all the other parent transforms would apply.
I'm having a hard time imagining what types of components would need this for and you wouldn't just deal with a flat structure yourself. Could you please explain your use-case more? Maybe there's another approach.

I think the distinction I'm trying to convey is that your logical grouping and your rendering grouping are currently the same, and they shouldn't be.
If you have a logical grouping of like-minded components that you reuse; those things don't have to exist in the render tree in that same hierarchy. Group your objects in structures that make sense for you application, and group the visible rendering obnjects (pixi objects) in ways that make sense for rendering. Those two objects and concepts can (and should) be separate.

@bigtimebuddy imagine a toolbar at the top of a page, but you can switch it to "floating" to detach it from the rest of the layout.

This could be handled by re-parenting the toolbar to and from a tranformed/untransformed container.

@Patrick-Hammond you're right, I was simply wanting to avoid adding and removing it dynamically like that.  I'll do that if I have to, but was hoping for a more flexible option.  I assumed this would be a no-brainer since this is representative of a very common feature in HTML (absolute positioning) and is trivial to support in Pixi.

PIXI is not trying to be CSS, if you have better layout options with those tools, you might consider using CSS for your layout, and just having multiple PIXI renderers that are resizable.
While technically it's an easy change, it's certainly not trivial. It would allow users to opt-out of a core feature of PIXI's display trees. I would not consider this change because I do not see the utility beyond your limited circumstance, especially when there are alternative approaches available.
In v5 we are going to introduce a much more component-based system where you could make a custom renderer which includes only the features you want. You, ostensibly, could implement your own layout/positioning paradigm but still use all the guts of PIXI, like textures, loading, etc.

@bigtimebuddy I do believe this has far larger usefulness than just my narrow case, but I can work around it.  Any details on when 5 will be useable?

We are still months away from v5 beta. You should get on the PIXI Slack channel, we post some notices there when new stuff is about to come out. Ping @ivanpopelyshev if you want to join.

I assumed this would be a no-brainer since this is representative of a very common feature in HTML (absolute positioning) and is trivial to support in Pixi.

To be clear HTML5/CSS does exactly what I suggested you do. Decouples the application layout (HTML/CSS) with the rendering layout (internal render objects). Changing a float values simply moves around internal render objects so they render differently. HTMLElement doesn't render anything in chromium, it just represents the application layers idea of what the document says to do, and a separate render thread holds render data that actually draws. Treat your application the same. You can have an object where setting float = true means it just moves some pixi objects under the hood.

@darkfrog26 what approach did you settle on?

@bigtimebuddy I wrote my own abstraction to make it so it adds and removes itself from the container if floating is enabled.

Sounds good! Glad you found something that works.
I'm going to close this since you have a solution and we are unlikely to consider the float API you suggested.


License

I noticed that there isn't a license specified in the repository, would you be able to clarify if the project is intended for open-source sharing and collaboration?
If so, would you consider adding a specific license? Thank you very much.

This project is intended for open-source sharing and collaboration. I will add a specific license.

Thanks!


Support ENUM types

We need to support an ENUM type and add it to all the major adapters as well as the waterline-adapter-tests

In my case, run with:
status: {
      type: 'STRING',
      isIn: ['pending', 'approved'],
      columnType: "enum('pending', 'approved')",
    },

mysql column:
`status` enum('pending','approved') DEFAULT NULL,


Forces Focus on the User, Should Start in the Background

Storage Explorer Version: 1.12.0
Build Number: 20200116.10
Platform/OS: macOS Catalina
Architecture: x64
Bug Description
When opening Storage Explorer it forces the user to focus on it even though it takes some time to initialize. This is frustrating behaviour because I want to start it so it can take its time loading and do something else in the mean time
Steps to Reproduce

Open Storage Explorer
Navigate to another application, even more apparent if you switch to another desktop
User is forced to focus back on Storage Explorer

Expected Experience
I expect Storage Explorer to work like 99% of other applications and start when I open it but not force me to pay attention to it
Actual Experience
When I am interacting with other applications Storage Explorer will get to a point in it's startup routine where it forces my focus back to itself
Additional Context
No restrictions

Unfortunately the API that I think would allow us to not steal focus is currently broken: https://github.com/electron/electron/issues/24703
Will need to revisit this at a later date.


Monitoring data factory pipeline runs using "az datafactory pipeline-run query-by-factory" not working as expected, and missing pipeline runs?

[The following command doesn't work correctly :
az datafactory pipeline-run query-by-factory --factory-name XXXXX --last-updated-after $last_updated_after --last-updated-before $last-updated-before --resource-group XXXXX
I encountered the following issues:
1/ I am not able to get pipeline runs that occured less than two hours ago
(Even though my pipelines are running every 10 minutes, everyday and I can see the pipeline runs on Azure data factory UX).
2/ No matter what date is defined for the option last-updated-before, only a fraction of the pipeline runs that started at or after last-updated-after are returned.
Example :  last-updated-after = "2022-06-05T20:36:45.859989" => I only get pipeline runs with run start from this time to "2022-06-01T22:58:17.115499+00:00", I don't get the runs that happened after that until the date/time defined by last-updated-before.
]

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

ID: bb16e30c-bfd2-e67d-5df7-6b83dc23f82d
Version Independent ID: 0bd3e41c-94df-d4bd-d0ed-f6fe9be37992
Content: az datafactory pipeline-run
Content Source: latest/docs-ref-autogen/datafactory/pipeline-run.yml
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

data factory


Confirmation of deleting a scenario

I think deleting scenarios, no matter of a kind, should be possible from a splash screen so there is no need going back to Editor menu.
I like the first idea of the dialog. It could be a simple thing:

I personally think the Delete button should stand out more and should be red-coloured. Moreover, all Back buttons in the app should have a neutral colour, i.e. be grey as the Delete is now or white. They don't do anything major/serious/dangerous to be red. But it's a topic for a different discussion.

Clicking the Delete button causes appearing of the confirmation text and two new buttons:

PSD: delete_confirmation.zip

The design is plain and simple. It'd could be an enhancement for another release.
PS. Grey vs White Back button:

Originally posted by @chrismaliszewski in https://github.com/NPBruce/valkyrie/issues/1077#issuecomment-465792756

I thought about this, and I really think that editor scenario should only be deletable from the editor.

Why do you think so? Is that because of the safety reasons?

Locally created scenarios are only accessible from Offline mode.
There would be the confirmation before deleting a scenario.

If you're still worried:

a new filter could be created to hide locally created scenarios and/or...
the delete button for the locally created scenarios could be a bit little different from the normal ones, i.e.

As I said before, I think deleting scenarios, no matter of a kind, should be possible from the same place (+from Editor if you still want to use it) so there is no need going back to Editor menu. But I think others should say what they think. @scrubbless @redwolf2?

Yes for me the risk of error is too high compare to the benefit of being able to delete Editor scenario in scenario explorer.
When you create a scenario in the editor, you can only delete it in the editor.
It makes sense to me.

Point taken. I am not a creator so if you think it's better that way, it's ok. In https://github.com/NPBruce/valkyrie/issues/1077#issuecomment-465809065 you said you've already deleted the possibility. And the only scenarios that will have Delete button will be downloaded ones.
But in both cases, deleting downloaded and created locally, it'd be good to have a confirmation. I know that deleting scenarios in Editor is a two-step process. But it's better to be sure you don't delete something you don't want to, right? Or think differently?

A delete confirmation wouldn't harm anyone and it protects the trigger-happy-clicker against him/her-self. :).
I agree that scenario in the editor should be only deleted from the scenario editor.
PS: I have to admit that for me clicking the yes/no for confirmation is more a reflex then a conscious action: are you sure 'yes'... are you really sure "YES" ... really really sure? Y E S !  ;)

I like the delete confirmation, great idea. But agree with BenRQ, local editor content should only be deletable from editor menu. In my eyes the two content types should be kept independent.

I see two options:

Have a message, that explains, that it should be deleted from the editor menu.
Avoid trigger happyness by having an additional text field, where the user is told, that this is an editor scenario and he has to type in a confirmation text to delete it. Much like the deletion of git repositories work.


fix bug which can cause incompatible docker images

Suppose you have an existing server without the commander image.
If you now follow the blog instructions and curl cyber-dojo and chmod+x it and then
$ cyber-dojo up
It will [docker pull commander] but it will not [docker pull] the other images (web/differ/etc).
So if you already had an old cyberdojo/differ image it will not get updated.
Basically, whenever cyberdojo/commander gets implicitly pulled (because cyber-dojo always delegates to it) then it should pull all the images (web/differ etc).

Should be very few people, if anyone, that old by now...


index.html

＜html＞
＜body＞
Since there's no index.html file in my repository, GitHub Pages displays the contents of the README by default. I've improve it
＜/body＞
＜/＞html

i tryed


Fatal Runtime Error

After following the fixes from #3 I get rust panic with following stacktrace:
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Error("invalid type: null, expected f64", line: 1, column: 9)', src/lib.rs:108:34
stack backtrace:
   0: backtrace::backtrace::libunwind::trace
             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.44/src/backtrace/libunwind.rs:86
   1: backtrace::backtrace::trace_unsynchronized
             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.44/src/backtrace/mod.rs:66
   2: std::sys_common::backtrace::_print_fmt
             at src/libstd/sys_common/backtrace.rs:78
   3: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
             at src/libstd/sys_common/backtrace.rs:59
   4: core::fmt::write
             at src/libcore/fmt/mod.rs:1063
   5: std::io::Write::write_fmt
             at src/libstd/io/mod.rs:1426
   6: std::sys_common::backtrace::_print
             at src/libstd/sys_common/backtrace.rs:62
   7: std::sys_common::backtrace::print
             at src/libstd/sys_common/backtrace.rs:49
   8: std::panicking::default_hook::{{closure}}
             at src/libstd/panicking.rs:204
   9: std::panicking::default_hook
             at src/libstd/panicking.rs:224
  10: std::panicking::rust_panic_with_hook
             at src/libstd/panicking.rs:470
  11: rust_begin_unwind
             at src/libstd/panicking.rs:378
  12: core::panicking::panic_fmt
             at src/libcore/panicking.rs:85
  13: core::option::expect_none_failed
             at src/libcore/option.rs:1211
  14: core::result::Result<T,E>::unwrap
             at /rustc/8d69840ab92ea7f4d323420088dd8c9775f180cd/src/libcore/result.rs:1003
  15: autopilot_deno::op_move_mouse
             at src/lib.rs:108
  16: <deno::ops::plugin::PluginInterface as deno_core::plugin_api::Interface>::register_op::{{closure}}
  17: deno_core::isolate::CoreIsolate::dispatch_op
  18: deno_core::bindings::send
  19: <extern "C" fn(A0) .> R as rusty_v8::support::CFnFrom<F>>::mapping::c_fn
  20: _ZN2v88internal25FunctionCallbackArguments4CallENS0_15CallHandlerInfoE
  21: _ZN2v88internal12_GLOBAL__N_119HandleApiCallHelperILb0EEENS0_11MaybeHandleINS0_6ObjectEEEPNS0_7IsolateENS0_6HandleINS0_10HeapObjectEEESA_NS8_INS0_20FunctionTemplateInfoEEENS8_IS4_EENS0_16BuiltinArgumentsE
  22: _ZN2v88internalL26Builtin_Impl_HandleApiCallENS0_16BuiltinArgumentsEPNS0_7IsolateE
  23: Builtins_CEntry_Return1_DontSaveFPRegs_ArgvOnStack_BuiltinExit
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
fatal runtime error: failed to initiate panic, error 5
Aborted (core dumped)

The Script that was used to produce the issue:
#!/usr/bin/env -S deno run --unstable --allow-net --allow-plugin --allow-env --allow-read --allow-write
import AutoPilot from 'https://raw.githubusercontent.com/divy-work/autopilot-deno/master/mod.ts';
var pilot = new AutoPilot();
var screenSize = pilot.screenSize();
var widthUnit: number = screenSize.heigth / 8;
setInterval(function () {
	var position = pilot.mousePosition();
	if (position.x > widthUnit * 2) {
		pilot.moveMouse(widthUnit,position.y)
	}else{
		pilot.moveMouse(widthUnit*3,position.y)
	}
}, 200);

@tionis Thanks for opening the issue. It looks like there is some problem while passing arguments to the Rust OP. I'll push a new release to fix this. Will ping here.

@tionis The problem is with your script. The widthUnit is passed as NaN so it breaks(it should be a number). I'll add type checks for the same but this is a problem with your script.

@tionis I've added typechecks for the method arguments. If you try again with the same script, You will get a similar output to this:
https://shareit.video/1hvk1lnw6NGNShG0tjVP

I see, the error in the script was a Typo screenSize.heigth to screenSize.height.
Seems to be the error of the day for me.


Add getEventTypes to template API

Just as with getRequestTypes and getResponseTypes https://github.com/accordproject/cicero/blob/37f5d331d1c03a70558d2f8b34dfcf82d60dd33d/packages/cicero-core/lib/template.js#L1073, the Cicero template JS API should have a function which returns a list of the event types emitted by a clause.
@jeromesimeon does this imply that we also need an annotation in the compiled JS code to identify the event types?

There is now a corresponding getEventTypes() call.


Fix NPEs related to movable selections

Contains
Fix for two NPEs thrown by the LocalPlayerBlockSelectionByItemSystem:

When the cam target had no LocationComponent, for eg: when the player is looking up at the sky
When onLeftMouseButtonDown event was not triggered after a selection had been made, in which case the blockSelectionComponentEntity would be null

Hooray Jenkins reported success with all tests good!

Tests out, thanks 👍


Cannot read property login of undefined

Extension version: 2020.4.42661
VSCode Version: 1.45.0-insider@a0fe37870c42e0704a492cdc6b8550b4cf23f63c (2020-04-30T05:39:08.281Z)
OS: Windows_NT x64 10.0.18363

Unfortunately I'm not sure how I got into this state. I updated my settings (to add "githubIssues.ignoreMilestones"), then the Github view (both issues and PRs) blanked out and this error was logged:

I reloaded the window. I was prompted to sign in again. Doing so produced this error:

But seemed to work -- I could see the issues and extensions. On the third reload, everything was working again.

Hmm!  If you see this again, can you grab the log from the "GitHub Authentication" channel in the output panel?

will do

@connor4312 Have you seen this recently?

Nope, will close


complete logger

We need to finish the logger and add writing to the file for the logger.
(we can use the path in config).
log levels and other stuff should be tested.

Hi @kehiy , I would like to work on this issue.

@bansaltushar014 hi, okay its assigned to you now. You can work on this.


Repeat steps

This is actually intentional.  What's happening is that if 2 transactions are created by the UI at roughly the same time, they can be assigned identical nonces.  This will cause geth to silently drop one of them from the txpool.  ethrpc checks specifically for this (a seemingly normal tx becoming null without a geth error + matching nonces) and will re-submit the transaction in that case.
That said, it probably shouldn't repeat the message to the user, since that's confusing.  I'll remove the duplicate message.

Added a mutual exclusion lock to the ethrpc rawTxs object in AugurProject/augur.js@ae577f43b8f004a13695a93b226185d746ce1e2b, which should force nonces to always be unique.  Closing since I'm no longer able to reproduce this issue.


Doc - Proj Tech Information

Purpose: Anybody new onboarding can find the instructions to run this project.
Documentation

[x] Make a table of contents near the top of our README.md with links to various documentation in our project
https://github.com/bcgov/CONN-CCBC-portal/blob/main/docs/Tech_Stack.md

Project technical information

[x] Detail tech stack and why we chose it
[x] Link to Button Toolkit which could be helpful to future developers

Please add your planning poker estimate with Zenhub @rafasdc

can all the check boxes be checked off on this?  can I request that we get a link to this documentation in the ticket too for PO review and historical reasons?

@AntBush  poke (see question above) :)

Sorry! And yeah, I can link that in here. Missed the point about the button toolkit too I'll make a small PR for that.

ok great, I will place this ticket in the 'in progress column' for now

@AntBush I think that last ac can be checked off now?
And where would we document Material UI?  Do you think it belongs in this doc or some other?

Yeah it should probably be added in this doc, should be just under/over the toolkit link. Technically should be another ticket, but it's small enough I can just do it

OK thanks, I will place this in the in progress column so I know when it's ready for review again


fizmo 0.8.2

Version bump
Update homepage URLs
Remove explicit configuration for ncursesw (chrender/fizmo-ncursesw@79f2dd9432bfe082f3bfc48a8d3d4e40ead50221)
Remove version string check (each front-end may have different versions than libfizmo which no longer shown up in help message)

Thanks again!


Improvement: Analog Stick Toggle

Some other emulators have this; an on-screen toggle that swaps out the touch dpad for an analog stick while playing a game. Could be a nice feature to have - doesn't output anything different than the dpad, just looks and functions like an analog stick.

Not a bad idea, I'll have to see how it works in practice. The dpad basically already roughly approximates an analogue stick, breaking the square into 9 segments, though the match-up isn't perfect:

Rather than make it a separate on screen toggle, I'd probably just make it an option in the per-game settings menu, as I'd rather keep as few things on-screen as possible at once, and I assume you're probably not toggling between analogue and dpad frequently in one game.


What does<EMAIL_ADDRESS>look like?

@sandeepmistry and I are summiting at iotdevfest this weekend and are (at the very early stage) of pondering what a 2.0 looks like?
Bindings layers updates an obvious change:
OSX
Get rid of xpcids in darwin as these break every year or two. Though frankly these breaking is the only time anyone cares or returns to the project. Sadly being stable in open source is a death sentence (more below)
Deprecations and changes in 10.13 need to be looked at closely http://codeworkshop.net/objc-diff/sdkdiffs/macos/10.13/CoreBluetooth.html
Sandeeps been working on a lower level objc
https://github.com/sandeepmistry/node-core-bluetooth ffi but we found it was way too slow and leaks memory
https://github.com/sandeepmistry/node-core-bluetooth/tree/node-objective-c-runtime fast but leaks memory
https://github.com/sandeepmistry/noble/tree/core-bluetooth
Rewriting with proper memory management should clear that up and make that route viable
WINDOWS
The windows people did some good uwp that needs more help to make nobley. Could we get Microsoft involved? Maybe they could sponsor the 2.0 branch and we can bring this in proper with a big release?
https://github.com/sandeepmistry/noble/issues/550
LINUX
We've heard there might be problems on linux but what though? Which tickets? Or open new ones please. dbus/bluez instead hci has been pushed by those guys.
https://github.com/sandeepmistry/noble/issues/310
need more info though, is new enough dbus available on all platforms like rapsbian, etc???
Need some linux leaders, can we get the bluez people to get in here with actual code vs just issues?
Bindings abstraction and tests
(and low level errors bubbling up finally)
https://github.com/sandeepmistry/noble/pull/431
Streams (we get these for 'free' by dumping older node versions finally)
https://github.com/sandeepmistry/noble/pull/593
Promises
https://github.com/sandeepmistry/noble/pull/708
Other API changes? Whats your wishlist?
Support and attention
Were constantly used in commercial work and noble is, I would argue, incredibly stable so we sadly only hear from those people when xpcids break and they want to 'help', by asking when it will be fixed. We have an open collective like everyone else but that doesnt mean much without some explicit push and plan for use of those funds. How do we use the 2.0 release get more community and issue triage and yes, funding in order to reward such by say sending hardware and stickers and shirts to contribs, etc. Ive always wanted a mailbag section with new ble hardware and tutorials as well. Companies would gladly send toys to contribs to make and test noble support and to get their hardware seen...
@monteslu @noopkat @jrobeson @explicitcall and please @ anyone else who might have comment here.

Another out there idea, luis wants more web ble like scanning options. We want to be more promise async/await style which means api changes. What about dropping the noble api and mirroring the web ble as thats the standard now, adding to it where we have to but reacting to it as it adds features.

I think mirroring the Web Bluetooth API is a good idea. It would allow developers to port Web Bluetooth dependent applications to Node easily.
IE A developer could split out the bluetooth dependent part of their code into a separate library, and simply use navigator.bluetooth or require("noble") depending on the platform they're deploying to.
It looks like Chrome requires a user to choose which Bluetooth device to pair using a native popup, and node-web-bluetooth uses a command line prompt. I think we should avoid any sort of UI and allow developers to implement their own prompt IE define some sort of interface or function that receives a list of BLE devices and returns one to connect to. There are different Node UI libraries (Inquirer.js and blessed to name a few) and each use their own drawing algorithms, so allowing developers to use their own implementation would avoid a lot of headaches (we could still provide our own canonical implementation in a separate repository).

I would love to help with the macOS part.
All though noble is currently stable, i think moving away from xpcids would be beneficial in the long run.

@jacobrosenthal : I was planning on attempting the dbus apis again, but I really don't want to deal with node without promises.  I'll try to come back to it once you folks decide to require node 6.x at the least.

I just looked and debian buster (which includes versions of node > 4.x) isn't due to be released until mid 2019.  I guess i'm not sure how to proceed now.

Oh, i take that back. I thought promises appeared in node 6.x, but it's really 4.x

#839 I think this is a good feature to implement in noble 2.0
I've written an application that uses noble, and noble arbitrarily exiting instead of bubbling an error would prevent resources from being freed.


TypeError: Object # has no method 'render'

Hi, jwilm
I use koa-hbs(0.4.4) in koa(0.5.5)
app.use(middlewares.bodyparser());
app.use(middlewares.jsonp());
app.use(middlewares.router(app));
app.use(middlewares.compress());
app.use(hbs.middleware({
    viewPath: __dirname + '/views',
    partialsPath: __dirname + '/views/partials',
    layoutsPath: __dirname + '/views/layouts'
}));

// init routes
app.get('/', function*() {
     this.render('index', {title: 'test'});
});

//run app
app.listen(3000);
console.log('listening on port 3000');

when I vist localhost:3000,I found the error
TypeError: Object #<Object> has no method 'render'

but app.use is well
app.use(hbs.middleware({
    viewPath: __dirname + '/views',
    partialsPath: __dirname + '/views/partials',
    layoutsPath: __dirname + '/views/layouts'
}));

//// init routes
//app.get('/', function*() {
//     this.render('index', {title: 'test'});
//});

app.use(function*(){
   yield this.render('index', {title: 'test'});
});

I also found the problem,thanks.
but why?

This is a dependency chain issue with koa-router and koa-compose. It's been around a while and is well-known. It isn't ideal, but the easy workaround is to app.use koa-hbs as soon in the stack as is possible. If someone knows how to hack around the limitations, we'd happily accept a PR.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_930b0446-5b60-4608-bc82-0db6d5eb4d2e/pull/1 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target_930b0446-5b60-4608-bc82-0db6d5eb4d2e.git

Docs Build status updates of commit c5853c9:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Release_Archive_master_2020-01-10-06-46-56 has been deleted or has been force pushed: fatal: couldn't find remote ref refs/heads/Release_Archive_master_2020-01-10-06-46-56

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


When image is printed in NB, add download link

https://chatgpt.com/share/0811e93e-dfc1-4279-b9a1-b3a40ba0bd89


vuetable-pagination component issue

Hey @ratiw
Thanks for the great plugin. When I set it up, there is issue with pagination component, I tried to pass through props too but it shows me the same error always
[Vue warn]: Failed to resolve component: vuetable-pagination (found in component: <vuetable>

any help would be highly appreciated

@vijaythecoder How do you install vuetable? Direct include in the


Upgrade git, dep and operator-sdk

/retest

force merging this patch as openshift/release build-root take the dockerfile.tools from the current master not from the patch
Pulling image centos:7 ...
--> FROM centos:7 as build-tools
--> LABEL maintainer="pipelines-dev<EMAIL_ADDRESS>
...

base image should be centos:8


[analyzer] add fix for default_list_constructor

With an old code of:
final list = List<String>();

With null-safely, the user currently sees:
The default 'List' constructor isn't available when null safety is enabled. (Documentation)
Try using a list literal, 'List.filled' or 'List.generate'.

It would be better to have a fix for replacement with the string list literal, at least when no initial size is specified.

99.9% was already done, thanks a lot.
https://dart-review.googlesource.com/c/sdk/+/238442


clustermesh-apiserver: extract kvstore client initialization and heartbeat logic in separate cells

This PR extracts the kvstore client initialization and heartbeat logic from the clustermesh-apiserver in two separate cells, to better integrate in the hive paradigm and allow them to be reused by other components. In this phase, the clustermesh-apiserver still relies on a global variable for the kvstore client, which is planned to be removed with subsequent refactoring (in particular, it involves much less changes once https://github.com/cilium/cilium/pull/25049 is in).

clustermesh-apiserver: extract kvstore client initialization and heartbeat logic in separate cells

/test

/test

Rebased onto main to include the changes introduced in https://github.com/cilium/cilium/pull/25643

/test

Rebased onto main to fix a conflict. I've additionally dropped a leftover kvstore initialization, which caused the spurious creation of an additional etcd client:
--- a/clustermesh-apiserver/main.go
+++ b/clustermesh-apiserver/main.go
@@ -576,21 +588,19 @@ func startServer(startCtx hive.HookContext, clientset k8sClient.Clientset, servi
 	}

 	var err error
-	if err = kvstore.Setup(context.Background(), "etcd", option.Config.KVStoreOpt, nil); err != nil {
-		log.WithError(err).Fatal("Unable to connect to etcd")
-	}

 	config := cmtypes.CiliumClusterConfig{
 		ID: cfg.clusterID,
 	}
@@ -602,6 +612,7 @@ func startServer(startCtx hive.HookContext, clientset k8sClient.Clientset, servi
 	}

 	ciliumNodeStore, err = store.JoinSharedStore(store.Configuration{
+		Backend:    backend,
 		Prefix:     nodeStore.NodeStorePrefix,
 		KeyCreator: nodeStore.KeyCreator,
 	})


⚠ Jenkins Plugins Artifactory has degraded performance

In f5de304, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1220 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 53e5677 after 47 minutes.


Fix various integration tests

This PR fixes various failing integration tests by adapting to the new Elasticsearch 5.x APIs.

Changes Unknown when pulling e7e992efcbb6db300b6f9824548e189d488aa6a7 on graylog-labs:fix-integration-tests into ** on searchbox-io:master**.

I realize that these are a lot of changes, but I tried to make each change very clear in its own commit. If you want to split up this pull request for better review, just let me know.

I'm not sure why Travis CI is still failing. The build succeeds locally:
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Jest Parent POM .................................... SUCCESS [  1.913 s]
[INFO] Jest Common Jar .................................... SUCCESS [ 12.161 s]
[INFO] Jest Apache HC Jar ................................. SUCCESS [09:20 min]
[INFO] Jest Android Jar ................................... SUCCESS [  2.798 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 09:37 min
[INFO] Finished at: 2017-04-12T13:23:17+02:00
[INFO] Final Memory: 43M/573M
[INFO] ------------------------------------------------------------------------


graph: backend: elyzor: use oneDNN's ISA traits to determine cpu features

Extract available CPU features using xbyak utils from oneDNN instead of internal graph compiler's functionality.
In order to detect CPU features, both (gc internal impl and xbyak utils) call cpuid() function to populate a bitmask consisting of 4 ints describing features (int info[4] in case of gc internal impl and int EAX, EBX, ECX, EDX in case of xbyak utils). Then individual bits are checked to determine supported features.
In the comments below I've specified which flag is extracted from which bit, in order to verify that both implementations are identical.

ping for review @AndreyPavlenko @kurapov-peter

I'd avoid using xbyak, but fine for a stopgap solution

I'd avoid using xbyak

What's wrong with it? It seems like a default way of getting CPU features in oneDNN


Dynamic changes

[Current coverage][cc-pull] is 23.34%

Merging [#44][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.96%

@@             master        #44   diff @@
==========================================
  Files             6          6
  Lines           218        227     +9
  Methods           0          0
  Messages          0          0
  Branches         28         27     -1
==========================================
  Hits             53         53
- Misses          162        171     +9
  Partials          3          3

Powered by Codecov. Last updated by [1cec7f4...4952de0][cc-compare]
[cc-base-branch]: https://codecov.io/gh/SxMShaDoW/embeddable-badges-plugin/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/SxMShaDoW/embeddable-badges-plugin/compare/1cec7f411c3f492658995a6aa173ad0714fe0472...4952de0fa4549128b93b1342695f70e299b049c7
[cc-pull]: https://codecov.io/gh/SxMShaDoW/embeddable-badges-plugin/pull/44?src=pr


[22.11] rustc: 1.64.0 -> 1.66.1

Description of changes
https://github.com/rust-lang/rust/releases/tag/1.65.0
https://github.com/rust-lang/rust/releases/tag/1.66.0
https://github.com/rust-lang/rust/releases/tag/1.66.1
Fixes CVE-2022-46176.
This is the path of least resistence, sadly; see the discussion in #210139.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin, nix-build -A fd -A synth -A sqlx-cli -A zee -A httplz

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Looking at the CVE it applies when cloning with cargo via SSH. We do not do this for our Nix builds and hence for that use case it is not relevant. Upgrading rustc often causes regressions.
Of course where the CVE does matter is for users using cargo outside of our Nixpkgs builds and outside of Nix builds.
I do not think this is the correct solution, and instead think the correct solution is to simply inform users that 1.64.0 should not be used doing ... because ... instead of forcing an update which can cause regressions both in Nixpkgs and outside.

These changes look good to me! I don't have an opinion on whether backporting is appropriate or not (depends on our position on security issues).

@FRidh I talked to @winterqt about this, and both of us think that the fix should be backported if we can make sure that no regressions happen within nixpkgs, since people do use cargo outside and might be affected by the CVE.
Another possibility I thought about was defaulting buildRustPackage and buildRustCrate (or just rustPlatform?) to 1.64.0, and make 1.66.1 the default rust. This way we can make sure that no regressions (no rebuilds as well) happen in nixpkgs if we change all uses of cargo and rustc to 1.64.0. Though, I am worried that it might be confusing and hard to debug for users since top-level rust and buildRustPackage would have different versions.
Do you have any suggestions how we might fix the vulnerability other than this and applying the patches? Or can you think of an easier way to apply the patches other than the method mentioned in https://github.com/NixOS/nixpkgs/pull/210139#issuecomment-1382658355? Perhaps it's better to apply the patches instead to avoid the potential regressions, even if the solution is ugly?

Fails to link on aarch64-linux. I think we encountered that on unstable as well.
rustc-aarch64-linux>    Compiling rustc_smir v0.0.0 (/build/rustc-1.66.1-src/compiler/rustc_smir)
rustc-aarch64-linux> error: linking with `/nix/store/08g2dvyx4i4zdc0s9i51029hlfm6q5ld-gcc-wrapper-9.5.0/bin/cc` failed: exit status: 1
rustc-aarch64-linux>   |
rustc-aarch64-linux>   = note: "/nix/store/08g2dvyx4i4zdc0s9i51029hlfm6q5ld-gcc-wrapper-9.5.0/bin/cc" "/build/rustcK9Xf7c/symbols.o" "/build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/rustc_main-95936b2b75bd5cef.rustc_main.eb2391a0-cgu.0.rcgu.o" "/build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/rustc_main-95936b2b75bd5cef.rustc_main.eb2391a0-cgu.1.rcgu.o" "/build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/rustc_main-95936b2b75bd5cef.rustc_main.eb2391a0-cgu.2.rcgu.o" "-Wl,--as-needed" "-L" "/build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps" "-L" "/build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/release/deps" "-L" "/build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/build/psm-725259a90952840f/out" "-L" "/build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/build/rustc_llvm-1fe81efb55ddb6da/out" "-L" "/nix/store/5133rd9ic81ybbf6myhwdrbhnikwpyaf-llvm-14.0.6-lib/lib" "-L" "/nix/store/2hzialg74cbmvqz17qnv9kzjglf8c8f9-gcc-9.5.0/lib/gcc/aarch64-unknown-linux-gnu/9.5.0/../../../../lib64" "-L" "/build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-sysroot/lib/rustlib/aarch64-unknown-linux-gnu/lib" "-L" "/build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps" "-lrustc_driver-c4bd77c3b6122f7a" "-L" "/build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-sysroot/lib/rustlib/aarch64-unknown-linux-gnu/lib" "-lstd-3c72abc60e605edb" "-Wl,-Bstatic" "/build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-sysroot/lib/rustlib/aarch64-unknown-linux-gnu/lib/libcompiler_builtins-a6b1f233b01990e9.rlib" "-Wl,-Bdynamic" "-lLLVM-14" "-ldl" "-lgcc_s" "-lutil" "-lrt" "-lpthread" "-lm" "-ldl" "-lc" "-Wl,--eh-frame-hdr" "-Wl,-znoexecstack" "-L" "/build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-sysroot/lib/rustlib/aarch64-unknown-linux-gnu/lib" "-o" "/build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/rustc_main-95936b2b75bd5cef" "-Wl,--gc-sections" "-pie" "-Wl,-zrelro,-znow" "-Wl,-O1" "-nodefaultlibs" "-Wl,-z,origin" "-Wl,-rpath,$ORIGIN/../lib"
rustc-aarch64-linux>   = note: /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_swp1_acq_rel'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-sysroot/lib/rustlib/aarch64-unknown-linux-gnu/lib/libstd-3c72abc60e605edb.so: undefined reference to `__aarch64_ldset8_relax'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_ldset1_acq_rel'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_ldclr1_relax'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_ldclr8_rel'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_swp8_acq_rel'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_swp4_rel'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_cas4_acq'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_cas8_rel'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_ldadd8_acq_rel'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-sysroot/lib/rustlib/aarch64-unknown-linux-gnu/lib/libstd-3c72abc60e605edb.so: undefined reference to `__aarch64_swp4_acq'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_ldset8_acq_rel'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_cas1_acq_rel'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_swp8_acq'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_ldset1_relax'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_ldadd4_acq_rel'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_ldadd8_rel'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_swp1_rel'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-sysroot/lib/rustlib/aarch64-unknown-linux-gnu/lib/libstd-3c72abc60e605edb.so: undefined reference to `__aarch64_cas4_relax'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_swp1_acq'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-sysroot/lib/rustlib/aarch64-unknown-linux-gnu/lib/libstd-3c72abc60e605edb.so: undefined reference to `__aarch64_ldadd4_acq'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_cas8_acq'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_ldclr8_relax'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_ldadd8_relax'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_cas1_rel'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_cas8_relax'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_ldset8_rel'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_cas8_acq_rel'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_ldadd4_rel'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-sysroot/lib/rustlib/aarch64-unknown-linux-gnu/lib/libstd-3c72abc60e605edb.so: undefined reference to `__aarch64_ldadd4_relax'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_cas1_relax'
rustc-aarch64-linux>           /nix/store/gnym1cd0q0aca7a1lidsdkq37jkkb69j-binutils-2.39/bin/ld: /build/rustc-1.66.1-src/build/aarch64-unknown-linux-gnu/stage0-rustc/aarch64-unknown-linux-gnu/release/deps/librustc_driver-c4bd77c3b6122f7a.so: undefined reference to `__aarch64_cas1_acq'
rustc-aarch64-linux>           collect2: error: ld returned 1 exit status
rustc-aarch64-linux>
rustc-aarch64-linux>   = help: some `extern` functions couldn't be found; some native libraries may need to be installed or have their path specified
rustc-aarch64-linux>   = note: use the `-l` flag to specify native libraries to link
rustc-aarch64-linux>   = note: use the `cargo:rustc-link-lib` directive to specify the native libraries to link with Cargo (see https://doc.rust-lang.org/cargo/reference/build-scripts.html#cargorustc-link-libkindname)
rustc-aarch64-linux>
rustc-aarch64-linux> error: could not compile `rustc-main` due to previous error
rustc-aarch64-linux> Build completed unsuccessfully in 0:04:04
rustc-aarch64-linux> make: *** [Makefile:12: all] Error 1

on x86_64-linux fd fails a test
fd> failures:
fd>
fd> ---- test_exec_invalid_utf8 stdout ----
fd> thread 'test_exec_invalid_utf8' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 84, kind: Uncategorized, message: "Invalid or incomplete multibyte or wide character" }', tests/tests.rs:2080:6
fd> note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fd>
fd> ---- test_invalid_utf8 stdout ----
fd> thread 'test_invalid_utf8' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 84, kind: Uncategorized, message: "Invalid or incomplete multibyte or wide character" }', tests/tests.rs:1756:6
fd>
fd>
fd> failures:
fd>     test_exec_invalid_utf8
fd>     test_invalid_utf8
fd>
fd> test result: FAILED. 79 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in 6.64s
fd>
fd> error: test failed, to rerun pass `--test tests`

aarch64-linux
/nix/store/9s3k2rci116pzvqmd184w6bdw5xkz9qh-fd-8.5.3
/nix/store/1d7a91ay3h2ypfp1d64zmxb87ypipiqw-synth-0.6.8
/nix/store/q420wcl3y8j2wsps270gjhzbdcxhlzd4-sqlx-cli-0.6.2
/nix/store/915f4g9hqvk6rr5xbyw9l2w0zz8pbixd-zee-0.3.2
/nix/store/691c21xzwp1d09y0hkngq7r89zmvgm8r-httplz-1.12.5

x86_64-linux
/nix/store/jm00bachpanypihhvdpqhw97ch5yd66q-fd-8.5.3
/nix/store/7hxamhhv0w5pkl1wqv2nc812smllh28g-synth-0.6.8
/nix/store/yn3mwf0r4zkvhn6w825lqfvz3zavfrsj-sqlx-cli-0.6.2
/nix/store/a6vn8xd90svbss0wfv9f6kirg59hzmj0-zee-0.3.2
/nix/store/8gb37dy0iji5rvxsvn3sqx5yxk390k45-httplz-1.12.5

The following fixes need to be picked as well

firefox-unwrapped: cdf02835ebf93dae3d38f665ce3530106f59b7db
spidermonkey: 77a214e764811aa5f4d3d4385439de4b28921171
rpm-ostree: https://github.com/NixOS/nixpkgs/pull/213287

only the NIX_LDDLAGS change, not the version bump

to be continued.

@mweinelt Should be good to go now, thank you for compiling that list/testing. (You need to retire that zpool, though.)

(Oh, and for posterity, I didn't cherrypick the rpm-ostree change because that was done alongside a version bump, and it felt weird cherrypicking only a part of a commit. If this isn't ideal, let me know.)

Do you have any suggestions how we might fix the vulnerability other than this and applying the patches? Or can you think of an easier way to apply the patches other than the method mentioned in https://github.com/NixOS/nixpkgs/pull/210139#issuecomment-1382658355? Perhaps it's better to apply the patches instead to avoid the potential regressions, even if the solution is ugly?

Maybe it is easier to break the ssh clone feature entirely and have a message there that users should use a newer rustc version if they want that version? Again, it really is only in a specific feature which is only applicable outside of Nix builds.
Or, from CVE:
If you can't upgrade to Rust 1.66.1 yet, we recommend configuring Cargo to use the git CLI instead of its built-in git support. That way, all git network operations will be performed by the git CLI, which is not affected by this vulnerability. You can do so by adding this snippet to your [Cargo configuration file](https://doc.rust-lang.org/cargo/reference/config.html):

[net]
git-fetch-with-cli = true

I don't think there is a right config file we can use, but we can wrap these older cargo versions with
cargo --config net.git-fetch-with-cli=true fetch

Well, upgrading (default) rustc also changes behavior, as you can see e.g. from all the patches needed across nixpkgs.

Yep, neither solutions are great. But, speaking as an end-user myself, I much rather be aware of the issue and have a choice, than be forced to potentially integrate a change in Rust version. We've had similar situations before, and it is problematic because it essentially means you cannot just upgrade your stable systems.

So, no conclusion for now?  I'm just asking because 22.11 rebuilds are likely to start soon.

This is obviously not going to happen. And at this point I'm just sorry about the time wasted.


Fix filters spacing with a new header

Fixes

Related to #1581 by @panchovm
Description

This PR is a companion to #1931. It adds the correct padding values for the filters sidebar on new_header layouts. It fixes the lack of padding on the desktop screens:

Also, the unnecessary padding and margins are removed. To make sure that 'Clear filters' button doesn't affect the layout when it is shown or hidden, the button uses absolute positioning.
Testing Instructions

Go to https://localhost:8443/preferences and make sure the New header flag is checked. Go to a search page and open the filters sidebar. It should have correct padding, and the layout should not change when 'Clear filters' button appears/disappears.
Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Rewrite after checking the right branch: Looks good!

I got an email notification with the video, then checked out the branch to check how that could have happened, and then realized that the single result is not supposed to have a filters sidebar :)


VS code puts \ see this issue for more info

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

VS Code Version: Version: 1.96.0-insider (user setup)
OS Version: Windows_NT x64 10.0.22631 Windows 11 Pro 23H2 build: 22631.4460

Steps to Reproduce:

Bug Report VS-code insiders
I want to specify a font file in a folder that is in .woff2 format. When i to press the Ctrl + Space Bar to specify the font file address in CSS it gives this folder that doesn't exist
Suggested path by vs code: ../IranSansX\(SemiPro\)/
Actual path that I want to put : ../IranSansX(SemiPro)/

Note that I didn't put url() before it

Out-of-the box, VS Code doesn't have any path completion in CSS.
Is this coming from an extension?

Out-of-the box, VS Code doesn't have any path completion in CSS. Is this coming from an extension?

yes this is work

Can you file the issue against the extension that provides the path completion for font paths?
You can use the Help: Start Extension Bisect too to find out which extension adds the completion.


Update blog “kawaki”

Automatically generated by Netlify CMS

👷 Deploy Preview for koyomiy processing.

Name
Link

🔨 Latest commit
d8c0df709fcde6eaa6bf02f2e5ccfb89abbb09ca

🔍 Latest deploy log
https://app.netlify.com/sites/koyomiy/deploys/62d299b7cdd006000a596117