Error installing MTGA Protracker

Hi,
When I try to install the lastest version of the soft, it fizzles and I can read this message:

thanks for your help!

I am having this issue too

Just released v.1.3.3 fixes that

It installs fine, but I do get that same error message when I install (1.3.3, 1.3.4 & 1.3.5).
I'm not installing to the default directory and I'm using Windows7.

You can click OK and go on with installation. Just ignore error

I am having the same issue. the first time I just clicked ok and I guess it was ok because the app worked but yesterday when I opened the app it said there was an update. I got the same error message and now the app won't work at all.

I am having the same issue. the first time I just clicked ok and I guess it was ok because the app worked but yesterday when I opened the app it said there was an update. I got the same error message and now the app won't work at all.

you should download latest app 1.5.1 and follow those steps: https://www.reddit.com/r/MTGArenaPro/comments/9z2ngf/tracker_update_v150_released_21112018_catchup_mode/

Won't do you mean by "won't work"? Do you see app interface? Is there error log in installation directory?

Not sure? the app itself seems to be working now. thanks for your help.
On Thu, Nov 22, 2018 at 9:29 PM Razviar<EMAIL_ADDRESS>wrote:

Won't do you mean by "won't work"? Do you see app interface? Is there
error log in installation directory?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Razviar/mtga-pro-tracker/issues/138#issuecomment-441158855,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AqI1zsSUaLFOc3SHhDxo3u5xQvH0uLQIks5ux4fTgaJpZM4YQTCj
.


Update README

I spent 2 days looking for solution then eventually found this is the solution, look like someone also face the same issues as well. Update solution here should help save time for more people

Thanks! I'll modify this a tiny bit, but LGTM.


update to new apis

This is a big one.
The VS Code notebook APIs have taken a large change that's mostly incompatible with the current Stable release.  Because of that a bunch of common code had to be moved into the stable/src and insiders/src directories and other helpers rearranged as necessary.
These changes aren't meant to be used in Stable currently, only in Insiders so we can unblock our users.  The differences between the two will be reconciled before the next Stable release which will then bring both back into close alignment.
There are some bugs yet to be filed against VS Code once this has been merged, specifically:

[x] Notebook controller webview not getting postMessage calls via onDidReceiveMessage().  Because of this bug, JavaScript cells don't behave as expected.
[ ] onDidChangeNotebookAssociation should fire even on initial notebook open.

microsoft/vscode#121895 was closed and latest insiders addressed the webview ipc issue


Highlight yourself

In crowded area's, where nearly every player looks identical, it would be useful if the player could highlight themselves:

This would work similar to the NPC indicators plugin.

Feature already implemented.
Player indicators -> highlight own player

Well, not a box, but a thing like this:

Just place a screenmarker around your player, you're always in the middle of your screen anyways so it will be correct no matter what.

I suppose that works too. Thanks for the workaround.


Dead links in README.md

I'm getting 404s for four links in https://github.com/RadeonOpenCompute/ROCm/blob/master/README.md, under 'The Latest ROCm Platform - ROCm 1.3". Tags: HCC compiler, LLVM-AMDGPU-Assembler-Extra, llvm, clang. Possibly permission issues.

Seems fixed now, I can access the links today.


"Search Cluster" should auto-expand matching children

Currently, the search has limited utility as it will only highlight what is visible. This means the user must manually expand every application type, then every application instance in order to search through all services.
For my team, that means 12 clicks before the search is useful.

Hi @tonjohn,
What do you think if we allow you to pin certain cluster tree nodes (for example the service node that you want to check) and then you can go to that node directly? Since we don't have user profile concept in SFX so this pinned nodes have to stick with browser local storage.
Thanks!

So then I would pin all my services to avoid having to expand the tree in the future? Sounds like that would solve the particular UX problem we have but I still think the search box UX doesn't map with what a normal search/filter experience is.


should fix middleware issue

I think expressive v2.2 requires zend-servicemanager v3

Thank you, it fixed the issue.


Remove @testing-library/react-hooks in favor of @testing-library/react

Noticed over in: https://github.com/primer/react/pull/3077 that later versions of @testing-library/react-hooks do not support React 18 🤔
When looking into this, it seems that the recommendation is to instead use renderHook from @testing-library/react directly: https://testing-library.com/docs/react-testing-library/api/#renderhook
This work would require removing call sites of @testing-library/react-hooks and replacing them with @testing-library/react. A previous exploration of this work was done over in: https://github.com/primer/react/pull/3129
This work will require React 18 support since this is not available in the previous major version of @testing-library/react.

Hello, may I work on this issue?

Hey there @roy9495! 👋 Thanks so much for reaching out about this!
Right now, it seems like this issue has a blocker since the project currently tests across React 17 and 18. One thing I found about the work over in #3129 is that this would not work in that React 17 case since @testing-library/react does not have renderHooks exported 😞 https://github.com/primer/react/pull/3129#issuecomment-1499350137
Just wanted to bring this up, if you have any suggestions or ideas for a workaround that would help us close this issue then it would be greatly appreciate and we would love if you picked up the work for this!

Blocked on React 18 support


Adding support for pixart-sigma model?

#88

@foreverpiano Thanks for your attention. Would like to help us work on this PR?


[NotCurrentlyABug] Cursor and rendering get out of sync with flexible row dimensions

Using the UTF8 example, this is what happens

There is a temporary fix that uses fixed lines, I think this is the right thing to do for a terminal.

This is just to track the issue while we decide what to do about the new rendering approach - I do not think it should be variable height, but if we do, then this bug tracks that issue.


added XO

Thanks a lot @hrocha16! So glad to see your contribution. You might be missing this tho.
JSX is supported by default but you need eslint-config-xo-react.

Added the eslint-config-xo-react, thanks a lot guys!

Nice work @hrocha16! Thanks so much 🎉 🌮
https://github.com/bukinoshita/open-source/issues/5


Contributions

Hey @DigitalFlow, this project looks exciting :) I'd love to work on it..  can you give any more suggestions for functions you would like to see added to the project? (I see you've mentioned RUI support already).

Hi @camelCaseDave,
awesome, I'm glad that you're interested in this project :)
Yes RUI support should be done quite soon. I guess this will be rather easy, as the Dynamics Level Up Chrome Extension already retrieves the context in RUI and UCI as well.
So we know that it's definetly possible.
Next up I'd like to handle Quick Create forms.
As this project targets to simulate process testing, so focus to business processes instead of simulating every user click, we need to find the correct IFrame after opening a quick create form, for being able to use its Xrm.Page object for issuing commands.
I already did a quick check and was able to find the correct IFrame in the debugger once a quick create form was opened. I imagined the openQuickCreate function to return a class instance, which allows interacting with it, just as the normal forms do.
I will also have to come up with some kind of namespaces for all functions that we provide, so that it's easier to work with. All functions directly in the top scope get messy really quick.
The nice thing is that easy tests are already working and we can build on that.
I'm really glad that you want to join in, as this will become quite a lot of work, but I think it will pay off.
Working with UI tests is so much less painful when using the Xrm.Page JS calls.
Kind Regards,
Florian

Awesome :) thanks for getting back to me.
Yeah agreed with your point on namespacing. The sooner the better for them being defined I think, less breaking changes moving forward and contributors will also have a clearer idea of how you want to structure the project.

Hi @camelCaseDave,
some progress already happened yesterday evening.
The latest commit on master now has a function for retrieving the Xrm object in UCI as well as in RUI and namespaces are split up.
We now have namespaces such as XrmTest.Attribute.get / set, XrmTest.Entity.Save and so on.
Pressing of ribbon buttons is now possible by id as well as by label.
Once the RUI tests work as expected and the docs are updated, I'll publish a new version on npm.
Kind Regards,
Florian

Hi @camelCaseDave,
are you still interested and want to give it a spin?
I have the feeling that we reached a pretty good state right now.
There is a demo repository for getting started quickly here: https://github.com/DigitalFlow/D365-UI-Test-Jest-Demo
Would be great to get some feedback and maybe you still want to contribute :)
Kind Regards,
Florian

Hey @DigitalFlow
I am indeed! I noticed you pushed some significant changes yesterday.
I also just included this project in a blog post (though I've not publicised the blog post yet).
I'll have a go with the demo repository. I'm sure it will then become obvious which methods I could look at implementing. If you have any other suggestions please do say.
Thanks
Dave

Hey @camelCaseDave,
that's great, thanks for the blog post, I like it very much :)
Maybe it would be useful to include the example repository in there already.
I did a few tests with O365 and also custom auth and fixed some issues in v0.0.18.
The latest version of the example repository already uses this version.
On my agenda I will now implement setting values in quick create, adding new records from subgrids and lookups and a helper function for setting multiple attributes at once.
Once you really use this lib and see need for more functions or easier access, I'm happy for every PR :)
Kind Regards,
Florian


Help me pls

Description
I'm an Xbox user,i'm unable to play normally due to updates from Valheim(Updated to 0.217.37),It keeps reporting errors when I enter the main menu.At the first I think it's a problem with the ’Jotunn‘ mod,But after testing, I found that J could be loaded alone, and it started reporting errors until I added the ’cheb‘ mod.
Attachments Checklist

[
LogOutput.log
] Log file
[
com.chebgonaz.ChebsNecromancy.zip
] Config file

Screenshots

Hello, I'll look into it later today and get back to you. Thanks for opening the issue and providing your log etc

I think your Valheim version is too new for the mod. Current is 0.217.31 (network version 18) and you're running 0.217.37 (network version 20)

Yes, that's right. Are you able to downgrade? I don't support PTB versions of Valheim - only the latest official releases.

Yes, that's right. Are you able to downgrade? I don't support PTB versions of Valheim - only the latest official releases.

Okay, I will be try. Thanks for your answer.


[BABEL] Error unknown: Preset

i am trying to add @tailwindcssinjs/macro to existing nextjs app with ant design and i got this error
./pages/index.js
MacroError: /home/darwis/dev/with-ant-design-app/pages/index.js: Error: @tailwindcssinjs/macro - [BABEL] unknown: Preset /* your preset */ requires a filename to be set when babel is called directly,

babel.transform(code, { filename: 'file.ts', presets: [/* your preset */] });

See https://babeljs.io/docs/en/options#filename for more information.

its working when using macro from tailwind.macro

my package.json:
{
  "name": "with-ant-design-less",
  "version": "1.0.0",
  "scripts": {
    "dev": "next",
    "build": "next build",
    "start": "next start",
    "build:base-css": "tailwindcss build ./styles/tailwind.base.css -o ./styles/base.css"
  },
  "dependencies": {
    "@emotion/cache": "11.0.0-next.12",
    "@emotion/css": "11.0.0-next.12",
    "@emotion/react": "11.0.0-next.12",
    "@emotion/styled": "11.0.0-next.12",
    "@zeit/next-css": "^1.0.1",
    "@zeit/next-less": "^1.0.1",
    "antd": "^4.2.3",
    "babel-plugin-import": "^1.13.0",
    "less": "3.11.1",
    "less-vars-to-js": "1.3.0",
    "next": "latest",
    "null-loader": "4.0.0",
    "react": "^16.13.1",
    "react-dom": "^16.13.1"
  },
  "devDependencies": {
    "@babel/core": "^7.9.6",
    "@emotion/babel-plugin": "^11.0.0-next.12",
    "@emotion/server": "11.0.0-next.12",
    "@tailwindcss/ui": "^0.3.0",
    "@tailwindcssinjs/macro": "^0.3.1",
    "tailwind.macro": "^1.0.0-alpha.2",
    "babel-plugin-macros": "^2.8.0",
    "postcss-preset-env": "^6.7.0",
    "tailwindcss": "^1.4.6"
  },
  "license": "ISC"
}

Hello @darwis059, it's not immediately clear what the problem is.
Please try:

Upgrading @tailwindcssinjs/macro to the latest version "@tailwindcssinjs/macro": "^0.3.1" => "@tailwindcssinjs/macro": "^0.7.0"
Deleting the .next folder in your repository this will make sure u don't use cached babel files.

Hopefully, this helps let me know if u still have the problem.

it still doesn't work. its working when build my app then serve it using next start. its error on dev mode
here my repository: https://github.com/darwis059/next-antd-tailwind-emotion.git

@darwis059 I was able to reproduce the issue and its an easy fix! Please try with v0.7.1.
Thanks a lot!

its working now, thank you


Volume control with Spotify Controls

Extension – Spotify Controls
Author:
@thomaspaulmann
Describe the feature and the current behavior/state.
I would like to be able to control Spotify's internal volume from the keyboard too.
This can be done with AppleScript too, for example:
tell application "Spotify"
	set sound volume to 50
end tell

or
tell application "Spotify"
	set sound volume to (sound volume - 10)
end tell

I would love five built-in presets available (the value goes from 0 to 100):

0 (mute)
50
100 (full)
volume up (in 10 increments)
volume down (in 10 decrements)

Who will benefit with this feature?
Any user wanting to control more of Spotify's feature set through the keyboard.
Any Other info.
Thanks in advance!

@sidbena how about adding it yourself? The source code is here.

@thomaspaulmann: I'm sorry, I but I'm not sure how. I've done some scripting before, but I've never coded anything for an already existing extension, let alone done much git stuff to ”real” repos. Is there a guide to this or a similar scenario?


Adds support for optional caliper dependencies to build system

If a user's caliper is built against adiak or gotcha, they can supply ADIAK_DIR and/or GOTCHA_DIR config variables to the make-based or cmake-based build systems.
Resolves #3361

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

Merged in next for testing...


ASB-2254 - Content audit

Describe your changes
https://pins-ds.atlassian.net/browse/ASB-2254?atlOrigin=eyJpIjoiYWZjM2U0ZWQxNzA2NDk5YjkwN2VmODk3YzRjNjk0ZTAiLCJwIjoiaiJ9
Type of change 🧩

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[ ] Other (please explain in the description section above)

Checklist before requesting a review

[ ] I have performed a self-review of my own code
[ ] I have double checked this work does not include any hardcoded secrets or passwords
[ ] I have made corresponding changes to the documentation
[ ] I have provided details on how I have tested my code
[ ] I have referenced the ticket number above
[ ] I have provided a description of the ticket
[ ] I have included unit tests to cover any testable code changes

:tada: This PR is included in version 1.9.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.19.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.24.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


MIDI message blast

Hi, when I run the code below, it repeats the MIDI message forever. I can't seem to find the correct way to send a single midi message under my control. The first port connected below is just the GMIDImonitor with JACK support, the second is a midi port on a Echo AF12 connected to a mixer. Both show the message repeated until I hit the keyboard which satisfies the input() at the end of the code.:
#!/usr/bin/env python3
import jack
import struct

client = jack.Client("MyGreatClient")
inport = client.midi_inports.register("input")
outport = client.midi_outports.register("output")

portlist = client.get_ports(is_midi=True, is_physical=True)

for port in portlist:
    print('port: {} is output: {}'.format(port.name, port.is_output))

@client.set_process_callback
def macsend(frames):
    print('frames: {}'.format(frames))
    outport.clear_buffer()
    outport.write_midi_event(0, (0xB2, 0x01, 0x40))

client.activate()
client.connect(outport,"MIDI monitor:midi_in")
client.connect(outport, portlist[1].name)
print("#" * 80)
print("press Return to quit")
print("#" * 80)
input()

it repeats the MIDI message forever

Yes, that's what you tell it to do.
Starting with client.activate(), the callback function macsend() is called once for each audio block, each time generating a MIDI event.
BTW, you should call client.deactivate() in the end (or use a with statement) to properly stop the audio callback.

I can't seem to find the correct way to send a single midi message under my control.

When do you want to send that message?
If you describe what you actually want to do, I can probably give you some kind of a hint.

Yes, I read that it will be called each process loop on the web site. So, I really wasn't surprised that this snippet is doing that. (I cobbled it from one of the examples, so it is lacking deactivate due to my lazy cobbling.) ;o
I read through the examples and they all use the callback to do the work. I'm missing the part that says "the work" is only one midi packet.
The simplest example of what I'm trying to do is: When the user clicks a button, my app must send, for example, a control change message to a specific midi channel. (So, for the event in the example, on my mixer, on midi channel 2 set the slider for channel 1, to -10db.)

I usually have a process callback which uses a Queue.
This is an example, taken from a custom program I use.
class JackThread(SomeThreadingClass):
    def __init__(self):
        [...]
        self.client.set_process_callback(self.process)
        self.client.activate()
        [...]

    def output_event(self, event):
        self.equeue.put(event)

    def process(self, frames):
        for port in self.client.midi_outports:
            port.clear_buffer()
        offset = 0
        while not self.equeue.empty():
            event = self.equeue.get()
            self.client.midi_outports[event[0]].write_midi_event(offset, event[1:])
            offset += 1

Then, from the main loop, I just call the output_event method with the midi event as argument; in your case it might be something like this.
    def button_clicked(self):
        self.jack_client.output_event(0, 0xB2, 0x01, 0x40)

I haven't tried to run this code, but I do use queues so I get what you're doing.
What does the offset variable and subsequent increment of offset do? Is this actually indexing the jack buffer so the next set of midi bytes are added rather than overwritten when there is more than one event in the queue?

I'm glad you sorted that out, even if my example wasn't complete.
About your question, I don't exactly know how it (jack midi) works, but as far as I understand, you can only have a certain number of events per audio block, and they have to be ordered, according to the timing in the current block.
As explained in the help, indeed, unordered events are ignored, but I don't actually know what happens if you write two events with the same order, I haven't tested that yet.

Multiple MIDI events can be generated for the same offset.
See my example midi_chords.py, where three notes are generated at the same offset.
@macdroid53 A few caveats regarding @MaurizioB's code above:

Depending on the exact requirements it may be the right thing to use threads, but I would first try to tackle the problem without (additional) threads. You should only create your own threads if you really need them.

Within the audio callback, you shouldn't use the blocking Queue.get() method. Use get_nowait() instead. This will throw an exception is the queue is empty (see below).

You shouldn't use Queue.empty(), since according to the official docs it's rather useless (since it doesn't guarantee anything): https://docs.python.org/3/library/queue.html#queue.Queue.empty. Just use a try/except block and check for the right exception (queue.Empty). This is more Pythonic anyway (EAFP).

See my example play_file.py for the (hopefully!) proper use of queue.Queue.

Thank you @mgeier for those tips!

I've looked at play_file.py extensively and I admit that I have not groked every detail. But, I've adjust my code somewhat based on what I think I understand.
At this point I have the following code in my process function
and I have a xrun callback as well:
   def process(self, frames):         self.print_error( 'frames={0}'.format(frames))         for port in self.client.midi_outports:             port.clear_buffer()         offset = 0         try:             midievent = self.MIDIsndrqueue.get_nowait()         # while not self.MIDIsndrqueue.empty():         #     event = self.MIDIsndrqueue.get()             print('In midi process: {0} || {1}'.format(midievent[0], midievent[1:]))             self.client.midi_outports[midievent[0]].write_midi_event(offset, midievent[1:])             sleep(0.100)             offset += 1         except queue.Empty:             self.print_error('JACK midi queue empty')
But, just siting there it gets xruns:
frames=1024
JACK midi queue empty
An xrun occured, increase JACK's period size?
An xrun occured, increase JACK's period size?
Jack: JackClient::ClientNotify ref = 11 name = jmidi_ShowMixer notify = 3
Jack: JackClient::kXRunCallback
frames=1024
JACK midi queue empty
frames=1024
JACK midi queue empty
An xrun occured, increase JACK's period size?
Jack: JackActivationCount::Signal value = 0 ref = 11
Jack: JackActivationCount::Signal value = 0 ref = 11
frames=1024
JACK midi queue empty
Jack: JackClient::ClientNotify ref = 11 name = jmidi_ShowMixer notify = 3
Jack: JackClient::kXRunCallback
frames=1024
An xrun occured, increase JACK's period size?
JACK midi queue empty
frames=1024
JACK midi queue empty
Jack: JackActivationCount::Signal value = 0 ref = 11
Jack: JackActivationCount::Signal value = 0 ref = 11
frames=1024
So, I don't get why it would xrun when nothing is being processed. And how does one increase JACK's period? Can that be done in code based on buffer size, etc.? Or do the settings have to be adjusted from a JACK controller like QJackctl?
It also gets an xrun every time I something is queued. I basically send 3 byte single midi commands, is the buffer in the client that small by default?

I don't get why it would xrun when nothing is being processed.

Well that's not quite true, you are doing plenty in your process callback.
Did you try it with an actually empty callback?
Strictly speaking, you shouldn't even print stuff in the process callback.
But I guess the real problem is this:
sleep(0.100)

I don't know which exact function this is (it might be time.sleep() from the standard library?), but are you really sleeping 0.1 seconds here?
Why are you doing that?
You should never sleep for any amount of time in the process callback, except if you want to deliberately cause xruns!
If it's really 0.1 seconds, you should think for a moment what that means: Assuming that you use a sampling rate of 48000 Hz and a block size of 1024 frames, playing back one frame takes 0.021333 seconds. Obviously, your process callback must not take longer than that. Now if you sleep 0.1 seconds, that's five times as long!
Apart from that, you still use offset += 1.
If you don't really need this, please remove it.

And how does one increase JACK's period? Can that be done in code based on buffer size, etc.?

This might work by assigning a new value to self.client.blocksize, see http://jackclient-python.readthedocs.io/#jack.Client.blocksize.
But it probably makes more sense to choose the block size when starting the JACK daemon.

Or do the settings have to be adjusted from a JACK controller like QJackctl?

Yes, that's typically where you would do that.
Or via command line options if you are starting jackd manually.

I basically send 3 byte single midi commands, is the buffer in the client that small by default?

I don't think so. I guess the problem is somewhere else.
You should provide a minimal but runnable code example, then I can also try it and help find the problem.

So, I removed the sleep (it was indeed a time.sleep() call). I had put it there attempting to debug what I thought was a timing issue with the moving faders on one of the mixers. The xruns have quieted down to occasionally. (I should have known better having written plenty of interrupt callbacks for micro-controllers.)  My bad... :(
I guess I don't get what the offset is, but, I removed the offset += 1 and it seems to work. does it offset into a ring buffer for large blocks of data when the buffer is not empty?

Good. You can probably tweak some JACK settings to completely get rid of xruns.
offset is much simpler than you probably think. In the docs it's called time: http://jackclient-python.readthedocs.io/#jack.OwnMidiPort.write_midi_event.
It's just the time when you want your MIDI event to be sent. And this time is given in samples relative to the beginning of the current audio block.
If you want to send your event as soon as possible, just use offset = 0.
Note that write_midi_event() might raise a JackError, you should check for that, just to be sure.
If you want to send multiple events at the same time anyway, it's probably easier to use reserve_midi_event(), which returns an empty buffer if anything goes wrong.
Unless you have more questions, can you please close this issue?


Information Security with HelmetJS - Understand BCrypt Hashes: challenge require('bcrypt') 'error'

Describe your problem and how to reproduce it:
Within the challenge within the title of this issue, the require method for bcrypt isn't working properly.  I have written const bcrypt = require('bcrypt'); in the top of myApp.js within Glitchand I get error below the submit button.  The dependency is being set correctly according to the tests, but the require portion is failing.
Add a Link to the page with the problem:
Link to freeCodeCamp Challenge
Link to glitch
Tell us about your browser and operating system:

Browser Name: Google Chrome
Browser Version: v70.0.3538.110
Operating System: Windows 10

If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):

I think there's a new glitch project to clone when you get to the bcrypt stuff

Hey there, thanks for the help.  You're correct, I just didn't see the link up top.  I wrongly assumed and that's on me.  Thanks for the prompt response, and loving all the trainings/challenges!


Canary rollout upgrade

This is a shell issue, that gathers the technical gaps, identified to implement Camel K operator canary rollout upgrade:

[x]  Support resources scoping, locking/handover: #1943

[x] Upgrade controller-runtime to version v0.9.0
[x] Use selectors support from controller-runtime: kubernetes-sigs/controller-runtime#1435

[x] Improve multiple operators topology: #2177
[x] Add support for Integration Deployment strategy: #2256
[ ] Report the Upgradable Condition to OLM
[ ] Complement existing upgrade e2e tests to cover canary rollout use cases

The implementation should work equally for both OLM and standalone (kamel install or kustomize) installation modes.

Relates to https://github.com/apache/camel-k/issues/3397#issuecomment-1735525398


Idea: Show name of entity in the list of integartions

Would be great to have the list of Dynamic Energy Cost integrations with a name such as "Boiler Dynamic Energy Cost" Instead of a long list of Dynamic Energy Cost:

Thank you for this idea. I have thining about it as well. I'll look into it


Update portfolio

Coverage remained the same at 91.923% when pulling 6190308d551dfc22fceed1b931f96bbd8e64f127 on jaivigneshvenugopal:Update_Portfolio into 92d02e7c222538352b98e0c41540d06680814ef4 on CS2103AUG2017-T17-B1:master.

Coverage decreased (-0.1%) to 91.821% when pulling 0908396b8469d072cb8111a6ab6efa8249d5be5d on jaivigneshvenugopal:Update_Portfolio into 92d02e7c222538352b98e0c41540d06680814ef4 on CS2103AUG2017-T17-B1:master.


In Result change Value column name to Final Heat

In Result change Value column name to "Final Heat"

Changed


Update README.md

Corrected a deadlink.

@Nox-MSFT , @shiyi-peng any recommendations for getting past the failed tests. The change is very small. Fixed the relative path for a doc.


ENH+BUG: Add first_step functionality to all solve_ivp methods and fix lsoda first_step for backwards case (fixes #9366)

This adds functionality to be able to specify first_step to any currently implemented solve_ivp solver.
This fixes #9366, which was uncovered in developing this functionality. If it is preferred to fix this independently, the changes to lsoda.py file are the only additions needed.  The test would have to be rewritten only slightly to just use LSODA method in this case
This also partially addresses #9198 as well.

Removed WIP and TODO.  Failed Travis-CI seems unrelated to these changes.

I am fully onboard with adding first_step to all the solvers that can support it. I would like @nmayorov to give his approval that this is still mathematically valid (none of the solvers are expecting their first steps to be a particular format).

I would add that the current method for choosing an initial step for all solvers is to use a numerical routine.  The reference for said numerical routine mentions that sometimes it is useful to choose an initial step size based on experience.  I would welcome thoughts on whether we should guide the user on whether to use this functionality in the docstring.
I suppose I did not consider the case of solvers that cannot support this.  I changed the solve_ivp docstring to imply that all solvers would support first_step.  I am not aware of any solvers that cannot support this, but I am not aware of a lot of things.  Assuming that non-support is only for rare, specific solvers, I suggest leaving it as it is in the current PR, and that exceptions are added to the docstring if those solvers are added.

I suppose I did not consider the case of solvers that cannot support this.

I was unclear. I should have said "I am fully onboard with adding first_step to all the solvers because they can all support it." In theory, any of the options to solve_ivp may not apply to some future solver (or user-defined solver). The current design of solve_ivp is to expose and document the options of the built-in solvers, document any options that are specific only to some solvers, and error if inappropriate options are supplied. Right now, all the built-in solvers can accept first_step, so the implementation and docstring you've provided is perfect.

The implementation is good and the feature itself is conventional. Consider my very minor suggestions and I will merge it.

Both reasonable and more tidy suggestions.


no_overlap method refactor

Re-factor this method:
  def no_overlap
    (@computer_board.computer_occupied_cells + @computer_submarine_position).uniq.length == (@computer_board.computer_occupied_cells + @computer_submarine_position).length
  end

this actually doesn't need to be re-factored; Did comment it though


Feature request: Download compressed.js directly

Currently click on Download will download jscompress-result.zip containing compressed.js .
I propose to download it directly as compressed.js, know that you can simply use HTML5 element attribute download="compressed.js" for it, examples in https://www.w3schools.com/tags/att_a_download.asp
Spec details https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a#Attributes

@finom did the fix already landed? It still keeps downloading zip file after compressed pasted single JS file code.

@laukstein not yet, I'm getting deployment issues. The new version is going to be landed soon.

Everything is good now.


Constraint coverage

Meet 100% coverage goal for:

find_constraint.py
create_array_hiearchy.py

Ready for review.

@kkunal1408 , what is the change in examples/switched_capacitor_filter/switched_capacitor_filter.sp?

@kkunal1408 , what is the change in examples/switched_capacitor_filter/switched_capacitor_filter.sp?

Nothing. I had deleted it by mistake then copy-pasted it from the master.


volar throw Request textDocument/foldingRange failed with message tips while in github.dev

example: https://github.dev/element-plus/element-plus
open a vue file after installed volar plugin. it happens.

Duplicate of #1479


Variable Build.SourceBranchName is empty with TFS-RestAPI

Agent Version and Platform
Agent version: 2.122.2
OS: Windows
VSTS Type and Version
On-premise TFS 2018 Update 1
What's not working?
If you queue a git build with the TFS-RestAPI via the build id, the variable $(Build.SourceBranchName) is empty. If you queue the build with web access, it works fine.

@anonymmynona i would suggest you to report this problem to Developer Community, since it sounds like a problem with the server. $(Build.SourceBranchName) is a variable provided by the VSTS Server.

Okay I'll try. Thanks you.


extract watchdog metric

Please provide a description of this PR:
fix: https://github.com/istio/istio/issues/52731

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

Before:
# TYPE envoy_server_main_thread_watchdog_mega_miss counter
envoy_server_main_thread_watchdog_mega_miss{} 0
# TYPE envoy_server_main_thread_watchdog_miss counter
envoy_server_main_thread_watchdog_miss{} 0
# TYPE envoy_server_worker_0_watchdog_mega_miss counter
envoy_server_worker_0_watchdog_mega_miss{} 0
# TYPE envoy_server_worker_0_watchdog_miss counter
envoy_server_worker_0_watchdog_miss{} 0
# TYPE envoy_server_worker_1_watchdog_mega_miss counter
envoy_server_worker_1_watchdog_mega_miss{} 0
# TYPE envoy_server_worker_1_watchdog_miss counter
envoy_server_worker_1_watchdog_miss{} 1

After:
# TYPE envoy_server_watchdog_mega_miss counter
envoy_server_watchdog_mega_miss{thread_name="main_thread"} 0
envoy_server_watchdog_mega_miss{thread_name="worker_0"} 0
envoy_server_watchdog_mega_miss{thread_name="worker_1"} 0
# TYPE envoy_server_watchdog_miss counter
envoy_server_watchdog_miss{thread_name="main_thread"} 0
envoy_server_watchdog_miss{thread_name="worker_0"} 0
envoy_server_watchdog_miss{thread_name="worker_1"} 0

@zirain: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
5b299bf45359ad7ac16b6285b249f2ed60363cb2
link
true
/test release-notes

gencheck_istio
5b299bf45359ad7ac16b6285b249f2ed60363cb2
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@zirain: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
5b299bf45359ad7ac16b6285b249f2ed60363cb2
link
true
/test release-notes

gencheck_istio
5b299bf45359ad7ac16b6285b249f2ed60363cb2
link
true
/test gencheck

unit-tests-arm64_istio
5b299bf45359ad7ac16b6285b249f2ed60363cb2
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.


Issue with Database Upgrade to v0.16.0 and Data Loss

Describe the bug
Hi there,
I have upgraded my instance to version v0.16.0 of the Memos instance and encountered some issues with my database. Unfortunately, my instance data seems to have disappeared after the upgrade, and I am also being prompted to sign up again.
Fortunately, I backed up my database before the upgrade, but I am unsure how to restore and resolve it. I would greatly appreciate any guidance or instructions you can provide to help me resolve this situation.
Thank you for your assistance in advance.
Steps to reproduce
Simply upgrade the docker container instance to v0.16.0
Screenshots or additional context
No response

I have upgraded my instance to version v0.16.0 of the Memos instance and encountered some issues with my database.

What's the error message of some issues?

Fortunately, I backed up my database before the upgrade, but I am unsure how to restore and resolve it. I would greatly appreciate any guidance or instructions you can provide to help me resolve this situation.

To restore your database, you can just directly replace the existing file with your backup database file.

I have successfully restored my instance after deploying again and overwriting database files. Thanks anyway.


Fails when no package.version

I'm running cargo-run-bin at the root of a workspace, where the version is not specified as package.version but as workspace.package.version. And I'm getting
run-bin failed: missing field `version` for key `package` at line 51 column 1

https://doc.rust-lang.org/cargo/reference/workspaces.html#the-package-table

Good call out, there's no proper support for workspaces. Are you defining binaries in your individual crates Cargo.toml, or the workspaces Cargo.toml?
I'd assume the workspace Cargo.toml is the correct spot.

I'm defining binaries in the workspace Cargo.toml.

Fixed in https://github.com/dustinblackman/cargo-run-bin/commit/208b000f47ee7666009a066a9f2a5124275ea381
Thanks!

Dustin, kudos on the response time. And thank you!


allow statements in shell .python command

I would tend to do this kind of thing in a python program that uses bql, rather than in the shell. I think we're prioritizing notebooks for most interaction, so I recommend wontfix.

I added a .pythexec command in commit 1d423d7276b681cff211dd80ce6c5505cb5925d1.  If someone else wants to figure out how to mix expressions and statements, gopher it.


Where is the easy version?

Those instructions did result in an application with a window, but I'd like to do it Visually, like VB6 or maybe C#. Looking around I see that there used to be a "CLR' package for this, but it has been removed.
What is the way to do this now?
Thanks,
John

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

ID: eda99bc7-483b-e53c-1035-886f4d0955f4
Version Independent ID: a6fdba4d-53e4-9f1a-2352-bc68ef491069
Content: Walkthrough: Create a traditional Windows Desktop application (C++)
Content Source: docs/windows/walkthrough-creating-windows-desktop-applications-cpp.md
Product: visual-cpp
Technology: cpp-windows
GitHub Login: @corob-msft
Microsoft Alias: corob

@anyonecan
There are several C++ framework libraries that have visual designers in Visual Studio, but I wouldn't call any of them easy. The oldest is MFC. It has visual designers to build apps that have the classic Windows look, but it's hard to take advantage of some of the newest Windows features in an MFC app. We used to support creation of C++/CLI apps, but dropped that in VS 2015. These apps were .NET Framework apps that used the C++/CLI dialect of C++ to emulate managed languages. There's the more recent C++/CX, which targets UWP apps, and like C++/CLI, modifies the C++ language to be closer to the managed .NET languages. It lets you use XAML visual designers just like C# or VB. Most C++ UWP project templates in Visual Studio generate C++/CX projects. C++/CX is loosely deprecated in favor of C++/WinRT, which doesn't modify the C++ language itself, but we don't have app templates that use C++/WinRT. While you can create an app with C++/WinRT, the templates are for creating components that you'd use in, say, a C# app.
Since your issue isn't one that suggests we need to change this particular doc, I'm closing it.

Hi Colin,
Thanks for the rundown on the options. I may have to look at C# for the
most straightforward path.
John
On Tue, Jun 29, 2021 at 4:40 PM Colin Robertson @.***>
wrote:

@anyonecan https://github.com/anyonecan
There are several C++ framework libraries that have visual designers in
Visual Studio, but I wouldn't call any of them easy. The oldest is MFC. It
has visual designers to build apps that have the classic Windows look, but
it's hard to take advantage of some of the newest Windows features in an
MFC app. We used to support creation of C++/CLI apps, but dropped that in
VS 2015. These apps were .NET Framework apps that used the C++/CLI dialect
of C++ to emulate managed languages. There's the more recent C++/CX, which
targets UWP apps, and like C++/CLI, modifies the C++ language to be closer
to the managed .NET languages. It lets you use XAML visual designers just
like C# or VB. Most C++ UWP project templates in Visual Studio generate
C++/CX projects. C++/CX is loosely deprecated in favor of C++/WinRT, which
doesn't modify the C++ language itself, but we don't have app templates
that use C++/WinRT. While you can create an app with C++/WinRT, the
templates are for creating components that you'd use in, say, a C# app.
Since your issue isn't one that suggests we need to change this particular
doc, I'm closing it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/cpp-docs/issues/3229#issuecomment-870937282,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACJWJP2SFF42SIFGVGGFJNDTVI4VRANCNFSM47Q7MMSQ
.


#618 implement basic delta function

Description
Implement delta function on one side of a domain
Fixes #618
Type of change

[x] New feature (non-breaking change which adds functionality)

Key checklist:

[ ] No style issues: $ flake8
[ ] All tests pass: $ python run-tests.py --unit
[ ] The documentation builds: $ cd docs and then $ make clean; make html

You can run all three at once, using $ python run-tests.py --quick.
Further checks:

[ ] Code is commented, particularly in hard-to-understand areas
[ ] Tests added that prove fix is effective or that feature works
[ ] Any dependent changes have been merged and published in downstream modules

hi @tinosulzer accidentally merged master into this branch. Hope that's ok


reth falls out of sync periodically

Describe the bug
Reth has been falling out of sync for a few minutes. This used to happen rarely, but has occurred twice in the last two days.

Steps to reproduce
run reth
Node logs
2023-11-05T19:01:17.616296Z  INFO reth::cli: Status connected_peers=9 latest_block=18507751
2023-11-05T19:01:25.196065Z  INFO reth::node::events: Block added to canonical chain number=18507752 hash=0x3efb28a82476c8ab5e920f67d0e49f6e10497b7f26ee00e1394b411b042ffea2
2023-11-05T19:01:25.678094Z  INFO reth::node::events: Canonical chain committed number=18507752 hash=0x3efb28a82476c8ab5e920f67d0e49f6e10497b7f26ee00e1394b411b042ffea2 elapsed=346.171537ms
2023-11-05T19:01:25.678135Z  INFO reth::node::events: Forkchoice updated head_block_hash=0x3efb28a82476c8ab5e920f67d0e49f6e10497b7f26ee00e1394b411b042ffea2 safe_block_hash=0x44d277c20a498fbc6df645df0a4e638dcb15cc61d08de5ff6ebbfaafaa56b6b5 finalized_block_hash=0x005a7165aa0cf9084d31b1a803ef3e6f4a56de552bdafa67dc7050adff23a8a0 status=Valid
2023-11-05T19:01:38.135717Z  INFO reth::node::events: Block added to canonical chain number=18507753 hash=0x33fce494ce2263b408506f429acd6af91be3b16cac1e329e05efa06a88e5a9b0
2023-11-05T19:01:38.648031Z  INFO reth::node::events: Canonical chain committed number=18507753 hash=0x33fce494ce2263b408506f429acd6af91be3b16cac1e329e05efa06a88e5a9b0 elapsed=359.930881ms
2023-11-05T19:01:38.648063Z  INFO reth::node::events: Forkchoice updated head_block_hash=0x33fce494ce2263b408506f429acd6af91be3b16cac1e329e05efa06a88e5a9b0 safe_block_hash=0x44d277c20a498fbc6df645df0a4e638dcb15cc61d08de5ff6ebbfaafaa56b6b5 finalized_block_hash=0x005a7165aa0cf9084d31b1a803ef3e6f4a56de552bdafa67dc7050adff23a8a0 status=Valid
2023-11-05T19:01:42.616099Z  INFO reth::cli: Status connected_peers=9 latest_block=18507753
2023-11-05T19:02:07.616310Z  INFO reth::cli: Status connected_peers=9 latest_block=18507753
2023-11-05T19:02:21.325311Z  INFO reth::node::events: Block added to canonical chain number=18507754 hash=0xf4767217592c51b52404ffc6729399d57b4b9e91e0e42231aef61b1bc1a6ba1f
2023-11-05T19:02:31.246021Z  INFO reth::node::events: Canonical chain committed number=18507754 hash=0xf4767217592c51b52404ffc6729399d57b4b9e91e0e42231aef61b1bc1a6ba1f elapsed=9.917251711s
2023-11-05T19:02:31.246097Z  INFO reth::node::events: Forkchoice updated head_block_hash=0xf4767217592c51b52404ffc6729399d57b4b9e91e0e42231aef61b1bc1a6ba1f safe_block_hash=0x44d277c20a498fbc6df645df0a4e638dcb15cc61d08de5ff6ebbfaafaa56b6b5 finalized_block_hash=0x005a7165aa0cf9084d31b1a803ef3e6f4a56de552bdafa67dc7050adff23a8a0 status=Valid
2023-11-05T19:02:32.615765Z  INFO reth::cli: Status connected_peers=9 latest_block=18507754
2023-11-05T19:02:57.616473Z  INFO reth::cli: Status connected_peers=9 latest_block=18507754
2023-11-05T19:03:22.615551Z  INFO reth::cli: Status connected_peers=9 latest_block=18507754
2023-11-05T19:03:47.615661Z  INFO reth::cli: Status connected_peers=9 latest_block=18507754
2023-11-05T19:04:12.616256Z  INFO reth::cli: Status connected_peers=9 latest_block=18507754
2023-11-05T19:04:23.002257Z  INFO reth::node::events: Block added to canonical chain number=18507755 hash=0x43aee42d1232af6e4fe72bae31609f7933096da98c8ecad1b9fca20336a33b58
2023-11-05T19:04:37.615934Z  INFO reth::cli: Status connected_peers=9 latest_block=18507754
2023-11-05T19:04:38.590066Z  INFO reth::node::events: Canonical chain committed number=18507755 hash=0x43aee42d1232af6e4fe72bae31609f7933096da98c8ecad1b9fca20336a33b58 elapsed=15.582301348s
2023-11-05T19:04:38.590091Z  INFO reth::node::events: Forkchoice updated head_block_hash=0x43aee42d1232af6e4fe72bae31609f7933096da98c8ecad1b9fca20336a33b58 safe_block_hash=0x44d277c20a498fbc6df645df0a4e638dcb15cc61d08de5ff6ebbfaafaa56b6b5 finalized_block_hash=0x005a7165aa0cf9084d31b1a803ef3e6f4a56de552bdafa67dc7050adff23a8a0 status=Valid
2023-11-05T19:05:02.616450Z  INFO reth::cli: Status connected_peers=9 latest_block=18507755
2023-11-05T19:05:27.269358Z  INFO reth::node::events: Block added to canonical chain number=18507756 hash=0xa5c3cc8fbb1501d7771500e37e84e61e26bbcdbe2e9675edb089db246d049f98
2023-11-05T19:05:27.615763Z  INFO reth::cli: Status connected_peers=9 latest_block=18507755
2023-11-05T19:05:51.976369Z  INFO reth::node::events: Block added to canonical chain number=18507757 hash=0xc6bc616e702375fcad9480304c0aa1cc8125a3b99925dcf1e8e303f13cdda54d
2023-11-05T19:05:52.615950Z  INFO reth::cli: Status connected_peers=9 latest_block=18507755
2023-11-05T19:05:55.159066Z  INFO reth::node::events: Canonical chain committed number=18507756 hash=0xa5c3cc8fbb1501d7771500e37e84e61e26bbcdbe2e9675edb089db246d049f98 elapsed=3.182623902s
2023-11-05T19:05:55.159105Z  INFO reth::node::events: Forkchoice updated head_block_hash=0xa5c3cc8fbb1501d7771500e37e84e61e26bbcdbe2e9675edb089db246d049f98 safe_block_hash=0x44d277c20a498fbc6df645df0a4e638dcb15cc61d08de5ff6ebbfaafaa56b6b5 finalized_block_hash=0x005a7165aa0cf9084d31b1a803ef3e6f4a56de552bdafa67dc7050adff23a8a0 status=Valid
2023-11-05T19:05:55.170204Z  INFO blockchain_tree: Block is already canonical, ignoring. block_hash=0xa5c3cc8fbb1501d7771500e37e84e61e26bbcdbe2e9675edb089db246d049f98
2023-11-05T19:05:55.174163Z  INFO reth::node::events: Forkchoice updated head_block_hash=0xa5c3cc8fbb1501d7771500e37e84e61e26bbcdbe2e9675edb089db246d049f98 safe_block_hash=0x7a1ad05d908a0934b389458f6e8502fd6400cafb70bf0456c31695bfd432e949 finalized_block_hash=0x44d277c20a498fbc6df645df0a4e638dcb15cc61d08de5ff6ebbfaafaa56b6b5 status=Valid
2023-11-05T19:05:56.628495Z  INFO reth::node::events: Block added to canonical chain number=18507758 hash=0x71f186e988f9c4967594e8abb9c317a8e5069efeb8018267573c83a05b504880
2023-11-05T19:05:59.925225Z  INFO reth::node::events: Canonical chain committed number=18507757 hash=0xc6bc616e702375fcad9480304c0aa1cc8125a3b99925dcf1e8e303f13cdda54d elapsed=3.291824644s
2023-11-05T19:05:59.925257Z  INFO reth::node::events: Forkchoice updated head_block_hash=0xc6bc616e702375fcad9480304c0aa1cc8125a3b99925dcf1e8e303f13cdda54d safe_block_hash=0x7a1ad05d908a0934b389458f6e8502fd6400cafb70bf0456c31695bfd432e949 finalized_block_hash=0x44d277c20a498fbc6df645df0a4e638dcb15cc61d08de5ff6ebbfaafaa56b6b5 status=Valid
2023-11-05T19:06:01.218941Z  INFO reth::node::events: Block added to canonical chain number=18507759 hash=0x81989bc025c7356f8a6d8edd5da8256350e71f3dea5568351383787877d82c85
2023-11-05T19:06:04.311716Z  INFO reth::node::events: Canonical chain committed number=18507758 hash=0x71f186e988f9c4967594e8abb9c317a8e5069efeb8018267573c83a05b504880 elapsed=3.092745735s
2023-11-05T19:06:04.311752Z  INFO reth::node::events: Forkchoice updated head_block_hash=0x71f186e988f9c4967594e8abb9c317a8e5069efeb8018267573c83a05b504880 safe_block_hash=0x7a1ad05d908a0934b389458f6e8502fd6400cafb70bf0456c31695bfd432e949 finalized_block_hash=0x44d277c20a498fbc6df645df0a4e638dcb15cc61d08de5ff6ebbfaafaa56b6b5 status=Valid
2023-11-05T19:06:06.671461Z  INFO reth::node::events: Canonical chain committed number=18507759 hash=0x81989bc025c7356f8a6d8edd5da8256350e71f3dea5568351383787877d82c85 elapsed=2.35641039s
2023-11-05T19:06:06.671483Z  INFO reth::node::events: Forkchoice updated head_block_hash=0x81989bc025c7356f8a6d8edd5da8256350e71f3dea5568351383787877d82c85 safe_block_hash=0x7a1ad05d908a0934b389458f6e8502fd6400cafb70bf0456c31695bfd432e949 finalized_block_hash=0x44d277c20a498fbc6df645df0a4e638dcb15cc61d08de5ff6ebbfaafaa56b6b5 status=Valid

Platform(s)
Linux (x86)
What version/commit are you on?
reth Version: 0.1.0-alpha.10 Commit SHA: 23c4828e
What database version are you on?
No response
What type of node are you running?
Archive (default)
What prune config do you use, if any?
No response
If you've built Reth from source, provide the full command you used
"RUSTFLAGS='-C target-cpu=native' cargo build --profile maxperf --features=jemalloc
Code of Conduct

[X] I agree to follow the Code of Conduct

UPDATE
The issue has become a lot worse, as now reth falls out of sync multiple times a day.
System setup: CPU AMD 3950x RAM, 64 GB, SSD Firecuda 530 4TB. The system runs lighthouse, Geth and Reth.
Geth & Reth are multiplexed to lighthouse with executionbackup (https://github.com/TennisBowling/executionbackup) and they both run on the firecuda.
I used to have the same problem with erigon, before I made the switch to reth.
Current version/commit: reth Version: 0.1.0-alpha.12 Commit SHA: 6b06382d0
A script that check every 3mins (with getBlockNumber rpc calls)and notifies me reported that reth was out of sync at:

03/12 22:42 - 23:03
03/12 23:48
04/12 01:03
04/12 04:33-04:42
04/12 12:45-12:51
04/12 13:48

Logs December 4th 04:29 - 04.47
reth.log

Hi can we confirm whether this is still a problem in alpha.13?

Hi can we confirm whether this is still a problem in alpha.13?

Sure! Already installed alpha 13, I will let you know as soon as I notice anything.

Can you re-share the same diagrams you had here? https://github.com/paradigmxyz/reth/issues/5319#issuecomment-1839240714
Also pls dm me on telegram @gakonst, we'll set up a channel to debug this more closely.

For 0.1.0-alpha.13 Commit SHA: 227e1b7ad here are some metrics and logs:

Logs 5:45 - 6:12 (reth out of sync 5:49 - 6:08)
reth.log

Turned out this was a disk issue.


Traceback (most recent call last):   File "E:\Seed-App-Mine-Seed-BOT-Telegram-main\bot\core\tapper.py", line 468, in run     if now < timestamp_naive: TypeError: can't compare offset-naive and offset-aware datetimes 2024-09-24 02:05:20 | ERROR    | 576 - test | Unknown error: can't compare offset-naive and offset-aware datetimes

why

use python 3.11.5


Add Vulture to CI and drop unused code

Proposed changes:

drop unused code
use vulture in CI to detected unused code (unfortunately we can't use it with min confidence 60% because it then has to many false positives - definitely worth going through these every now and then)

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

pushed a commit which triggers a vulture error. Also happy to skip adding vulture to the CI for now. It's not perfect but in my opinion a good start to have a least some check for it.

@wochinge it didn't fail because the lint for docstrings failed first :D
I don't think it's a good idea to not add it to the CI, because it will become dead code too (a bit ironic ahah)

I dropped vulture and now use flake8 instead @m-vdb Removed more unused imports - flake8 is a lot better than vulture for this. Dropped vulture since it has to many false positives.

but can flake8 detect dead code? unused import are a subset of dead code

not as good as vulture - but vulture has to many false positives so we can't really run it as part of the CI

@m-vdb Would be great if we could get this in before my vacation 👀 The review should be quick despite its size as it's just removing dead code.


Add RTD doc build, and move to after_success.

@dhermes what do you think of moving the documentation generation to after_success?
Fixes #2121

If you put it in after_success it won't fail the build if there's a problem

@dhermes switched them back around. If I understand correctly though, even if the unittests fail, the docs will still get deployed. I don't know if that's the best case.

I don't know if that's the best case.

It's not. Are you deploying on PRs or just merges?

You'll have to apply the **kwargs fix from #2071

Yup, thanks!

I assume / hope the Yup wasn't for "Are you deploying on PRs or just merges?"

Apparently it is! I'm fixing that right now.

Oy

How does tox -e docs deploy to RTD? Is that just from the READTHEDOCS envar?

It doesn't,  https://readthedocs.org/projects/gcloud-python/ looks for commits to master and triggers a build.
The relevant file was scripts/update_docs.sh before you implemented the new docs env

A while ago, I made a separate script for the JSON docs, update_json_docs.sh.  Travis is calling that now instead of tox -e json-docs directly.

Looking at https://github.com/GoogleCloudPlatform/gcloud-python/commits/master/.travis.yml it looks like tox already does this (#2016)

I guess I had more coffee in me back then.

It doesn't look like update_json_docs.sh checks if the docs build during a PR

That should run it every time, or were there some cases that you didn't want the docs to build? Also, should I have it build the RTD docs with tox -e docs?

tox -e docs has been changed by you (previously) to update_json_docs.sh, which now calls tox -e docs, thus creating an infinite recursion.
tox -e docs-rtd makes sure the docs actually build with Sphinx (which is the concern)

@dhermes updated! Looks like it worked.
https://travis-ci.org/GoogleCloudPlatform/gcloud-python/builds/153329212#L687

@daspecster This LGTM except for the tiny nit about using ${...}. Please squash and rename the PR to actually state what is happening

You can merge once you've fixed the nit and Travis goes green, no need to check with me


Redirect to requested_uri after login?

How do I make it redirect to the original requested page after login?

Try using:
<meta http-equiv="refresh" content="0; url=http://whereyouwant.com" />
Note: Place it in the head section.
Additionally for older browsers if you add a quick link in case it doesn't refresh correctly:

Redirect

This will still allow you to get to where you're going with an additional click.


Can I use it without react or vue?

Can I use it without react or vue? I just want to use it in a simple application with vite and html + js + css.
I have tried it, but got error:

vite.config.js is:
import { defineConfig } from 'vite';
import path from "path";
import mdPlugin, { Mode }  from "vite-plugin-markdown"

const { resolve } = path;

export default defineConfig({
  server: {
    port: 2023,
    host: "<IP_ADDRESS>",
  },
  resolve: {
  alias: [
    { find: "@", replacement: resolve(__dirname, "./src") },
  ],
  },
  plugins: [
    mdPlugin.plugin({ mode: [Mode.HTML, Mode.MARKDOWN, Mode.TOC] })
  ],
})

mypage.tsx:
import Hello, { attributes } from "./defining.md"

console.log(Hello, attributes, 11);

you need to import what you want like this:
import { html as DefiningText, toc as DefiningTOC } from "./defining.md"

thanks bro, another question：
defining.md code as following:
  # Markdown File

  ```jsx
  import { QuarkElement, customElement } from "quarkc";

  @customElement({ tag: "quark-count" })
  export default class Count extends QuarkElement {/***/}

![image](https://github.com/hmsk/vite-plugin-markdown/assets/14307551/7488cf17-bfe6-45a1-8a63-952f0a067ec2)

How to make the code highlight？


Incorrect reportUndefinedVariable for builtin qualname

Pylance mistakenly raises a reportUndefinedVariable warning for dundermethod__qualname__
Environment data

Language Server version: v2021.5.4
OS and version:

Windows 10 Version	10.0.18363 Build 18363
WSL Ubuntu 20.04.2 LTS (Linux VAU-NB-11514 4.4.0-18362-Microsoft #1049-Microsoft Thu Aug 14 12:01:00 PST 2020 x86_64 x86_64 x86_64 GNU/Linux )

Python version (& distribution if applicable, e.g. Anaconda): cPython 3.8.5

Expected behaviour
Pylance should recognise qualname as valid dundermethod in a class defintion and not raise any warning.
Example:
class Test:
    "Pylance bug"
    my_name = __qualname__

>>> t = Test()
>>> t.my_name
'Test'

Actual behaviour
Pylance raises reportUndefinedVariable  for the above code.
"__qualname__" is not defined

Logs
{
	"resource": "/mnt/c/Users/virtualraider/Documents/Code/GitLab/deleteme.py",
	"owner": "_generated_diagnostic_collection_name_#1",
	"code": {
		"value": "reportUndefinedVariable",
		"target": {
			"$mid": 1,
			"external": "https://github.com/microsoft/pylance-release/blob/main/DIAGNOSTIC_SEVERITY_RULES.md#diagnostic-severity-rules",
			"path": "/microsoft/pylance-release/blob/main/DIAGNOSTIC_SEVERITY_RULES.md",
			"scheme": "https",
			"authority": "github.com",
			"fragment": "diagnostic-severity-rules"
		}
	},
	"severity": 4,
	"message": "\"__qualname__\" is not defined",
	"source": "Pylance",
	"startLineNumber": 6,
	"startColumn": 15,
	"endLineNumber": 6,
	"endColumn": 27
}

The documentation for __qualname__ within a class does not suggest that it is accessible from within the class body itself. See PEP 3155 for the introduction of this attribute, and note that none of its examples show it being used within the class body. That said, I've confirmed that the Python interpreter does allow this. I wonder whether this was intentional or an oversight. It appears to be somewhat inconsistent because some dundered attributes like __doc__ and __module__ are accessible within the class body but others like __dict__ and __mro__ are not. Perhaps that's because the latter are still being constructed at the time the class body is executed.
The same PEP introduced __qualname__ for functions, and it is not accessible from within a function body (it generates a NameError at runtime).
Mypy (another popular type checker) also reports the use of __qualname__ and __module__ as errors.
So I wonder whether this is intended behavior or just an implementation detail that you should not be relying on.
Do you happen to know of any official Python documentation that explains that the use of __qualname__ within a class body is allowed?

Hi @erictraut , thanks for replying so quick!
I do not have any official documentation other than that PEP, sorry.
I have seen it in the dataclass implementation, which is where I found out about it
https://github.com/python/cpython/blob/a6a20658814e8668966fc86de0e80a4772864781/Lib/dataclasses.py#L582
I wanted to use it to build a qualified name hierarchy for logging so instead of:
class MyClass:
  log = module_logger.getChild("MyClass")

I can do
class MyClass:
  log = module_logger.getChild(__qualname__)

and this future-proofs any code refactoring of the module name.

I've updated the logic in pyright/pylance to handle this case consistently with the Python interpreter. I also filed a bug report for mypy, since it contains the same problem. After some experimentation, I found that __module__ needs to be handled in the same manner as __qualname__.
This will be fixed in the next release of pylance. Thanks for reporting the problem.

This issue has been fixed in version 2021.6.0, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/main/CHANGELOG.md#202160-2-june-2021

@erictraut, there is unfortunately a regression of this bug since v2021.8.1. Could we please reopen this issue?

__qualname__ is very strange. It doesn't show up in the __dict__ for a class. If you call dir() for the class, it isn't listed. When you call locals() within a class body, it is listed. So it appears to be a local variable injected into the scope at the time the class body is executed.
I'll note that mypy doesn't handle this correctly either. It's not surprising given that it appears to be a very strange special case.
I've added some logic that makes this work. This will be included in the next release.

This issue has been fixed in version 2021.12.1, which we've just released. You can find the changelog here:  CHANGELOG.md


Add AQI widget

Hello! I'm not sure if this repo is open to contributions, but I found the following widget I created to be useful based on your extension and wanted to share.
It's an AQI sensor  that changes the color of the widget based on the current numeric state. This works easily via Home Assistant's AirVisual Cloud API integration or other AQI states. The icon is from the repo you shared: https://github.com/encharm/Font-Awesome-SVG-PNG and the --text parameter can still be used. I also made sure to make the file executable with the same permissions as the other widgets. I find that using the icon alone looks nice as well as with the AQI:

I setup the widget in BTT as follows:
/usr/local/bin/python3 /Users/codes/clone/home-assistant-macbook-touch-bar/widgets/aqi.py --icon cloud.png --entity_id sensor.u_s_air_quality_index

Then added a URL action that goes to the AirVisual (redirects to IQair?) website, so I can easily see more info:

There isn't any error handling if the sensor passed in can't be cast to an int, but I did ensure that the correct AQI colors show based on the values which map to those colors (e.g. 50 is green, 51 is yellow)
Thanks again for making this great BTT Touch Bar extension! It's been making it easier than ever to get info and trigger things with the touch of a finger 👇🏼!

This is great, thanks a lot! :tada:


unable to determine direct routing device. Use --direct-routing-device to specify it (except that option is set)

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Attempting to setup cilium in direct routing mode (cluster shares a secondary, private L2 network).
I expected cilium to be able to route all cluster traffic over the private network.
Cilium Version
RKE2 included helm chart. Cilium version 1.15.6.
Kernel Version
Linux master1 6.8.12 #1-NixOS SMP PREEMPT_DYNAMIC Thu May 30 07:49:53 UTC 2024 x86_64 GNU/Linux
Kubernetes Version
v1.28.10+rke2r1
Regression
No response
Sysdump
cilium-sysdump-20240702-085709.zip
Relevant log output
level=fatal msg="failed to start: daemon creation failed: failed to detect devices: unable to determine direct routing device. Use --direct-routing-device to specify it" subsys=daemon

DEBUG: userDevices: [external,internal]
DEBUG: Initial DirectRoutingDevice: internal
DEBUG: filter: [internal]
DEBUG: devs: []
DEBUG: After match DirectRoutingDevice:
DEBUG: Final DirectRoutingDevice:

Anything else?
The error produced by cilium was not useful. I'm already providing --direct-routing-device.
I've added some debug logging to pkg/datapath/linux/devices.go to produce the above logging output.
You can see I've set both --devices and --direct-routing-device but then as cilium doesn't appear to be able to get my list of network interfaces for some reason it removes them as options.
Network interfaces (the bridges were added because I thought maybe it didn't like the @ in the vlan device name):
[wonko@master1:~]$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master external state UP group default qlen 1000
    link/ether 52:54:00:b2:4a:69 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::5054:ff:feb2:4a69/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever
3: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 52:54:00:4e:03:62 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::5054:ff:fe4e:362/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever
4: vlan4000@enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master internal state UP group default qlen 1000
    link/ether 52:54:00:4e:03:62 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::5054:ff:fe4e:362/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever
5: external: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 52:54:00:b2:4a:69 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global dynamic noprefixroute external
       valid_lft 2319sec preferred_lft 1718sec
    inet6 fe80::5054:ff:feb2:4a69/64 scope link
       valid_lft forever preferred_lft forever
6: internal: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 52:54:00:4e:03:62 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 scope global internal
       valid_lft forever preferred_lft forever
    inet6 fe80::5054:ff:fe4e:362/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever

Added logging:
diff --git a/pkg/datapath/linux/devices.go b/pkg/datapath/linux/devices.go
index 5807a71305..f1d60f99ca 100644
--- a/pkg/datapath/linux/devices.go
+++ b/pkg/datapath/linux/devices.go
@@ -31,6 +31,7 @@ type DeviceManager struct {
 func (dm *DeviceManager) Detect(k8sEnabled bool) ([]string, error) {
        hasWildcard := false
        userDevices := option.Config.GetDevices()
+       fmt.Printf("DEBUG: userDevices: %s\n", userDevices)
        for _, name := range userDevices {
                hasWildcard = hasWildcard || strings.HasSuffix(name, "+")
        }
@@ -40,8 +41,12 @@ func (dm *DeviceManager) Detect(k8sEnabled bool) ([]string, error) {
        }

        rxn := dm.params.DB.ReadTxn()
+       dt, _ := dm.params.DeviceTable.All(rxn)
+       fmt.Printf("DEBUG: dt: %+v\n", dt)
+
        devs, _ := tables.SelectedDevices(dm.params.DeviceTable, rxn)
        names := tables.DeviceNames(devs)
+       fmt.Printf("DEBUG: rxn: %+v devs: %+v names: %+v\n", rxn, devs, names)

        if len(names) == 0 && hasWildcard {
                // Fail if user provided a device wildcard which didn't match anything.
@@ -67,23 +72,29 @@ func (dm *DeviceManager) Detect(k8sEnabled bool) ([]string, error) {
        if option.Config.DirectRoutingDeviceRequired() {
                var filter deviceFilter
                if option.Config.DirectRoutingDevice != "" {
+                       fmt.Printf("DEBUG: Initial DirectRoutingDevice: %s\n", option.Config.DirectRoutingDevice)
                        filter = deviceFilter(strings.Split(option.Config.DirectRoutingDevice, ","))
+                       fmt.Printf("DEBUG: filter: %s\n", filter)
                }
                option.Config.DirectRoutingDevice = ""
                if filter.nonEmpty() {
                        // User has defined a direct-routing device. Try to find the first matching
                        // device.
+                       fmt.Printf("DEBUG: devs: %+v\n", devs)
                        for _, dev := range devs {
                                if filter.match(dev.Name) {
+                                       fmt.Printf("DEBUG: checking DRD:%s dev:%s\n", option.Config.DirectRoutingDevice, dev.Name)
                                        option.Config.DirectRoutingDevice = dev.Name
                                        break
                                }
                        }
+                       fmt.Printf("DEBUG: After match DirectRoutingDevice: %s\n", option.Config.DirectRoutingDevice)
                } else if len(devs) == 1 {
                        option.Config.DirectRoutingDevice = devs[0].Name
                } else if nodeDevice != nil {
                        option.Config.DirectRoutingDevice = nodeDevice.Name
                }
+               fmt.Printf("DEBUG: Final DirectRoutingDevice: %s\n", option.Config.DirectRoutingDevice)
                if option.Config.DirectRoutingDevice == "" {
                        return nil, fmt.Errorf("unable to determine direct routing device. Use --%s to specify it",
                                option.DirectRoutingDevice)

Cilium Users Document

[X] Are you a user of Cilium? Please add yourself to the Users doc

Code of Conduct

[X] I agree to follow this project's Code of Conduct

So after getting some advice on the Cilium/eBPF Slack I changed my devices list from a comma separated list to a space separated list. This solved the issue completely.
This appears to be a documentation error. Both on the part of the cilium agent (the docs aren't clear on the format of the devices list) and the section of the docs Kubernetes Without kube-proxy which states: To change the devices, set their names in the devices Helm option, e.g. devices='{eth0,eth1,eth2}' which is incorrect.


Incorrect command - Install the provider on Hyper-V Core Server

On code snipped:
cd  C:\Program Files\Microsoft Azure Site Recovery Provider\DRConfigurator.exe" /r /Friendlyname "FriendlyName of the Server" /Credentials "path to where the credential file is saved"
You should remove the "cd" instruction and add quotation marks at the beginner. So the command shall be:
"C:\Program Files\Microsoft Azure Site Recovery Provider\DRConfigurator.exe" /r /Friendlyname "FriendlyName of the Server" /Credentials "path to where the credential file is saved"
At least, once you run over Core Server, you should open CMD before run this instruction.

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

ID: f09250c3-f338-5ed0-9b83-fbf66e1ed48d
Version Independent ID: 159b7261-c371-4d3d-dfb2-4f43727d8211
Content: Set up disaster recovery for on-premises Hyper-V VMs (without VMM) to Azure with Site Recovery
Content Source: articles/site-recovery/hyper-v-azure-tutorial.md
Service: site-recovery
GitHub Login: @rayne-wiselman
Microsoft Alias: raynew

@jvinicius Thanks for the Comment. We are actively investigating and will get back to you soon.

@jvinicius  - fyi

this issue has been fixed and the update will be live shortly. Thanks again for catching this.


How do I update my hOn password?

The hOn password expires after one year and needs to be changed. How do I enter the updated password in HomeAssistant without adding the integration from scratch? (I wouldn't want to make new integration as I'm afraid it could break existing dashboards, automations etc)
Thanks!

Re-adding the integration won't break anything if you use the same name.

Yes, unfortunately it's the only option today, I didn't implement the password change yet


The assembly inside the latest package (https://www.nuget.org/packages/Serilog.Sinks.Loki/2.2.0)  does not contain the line ending and back-to-forward slashes fixes by #13

The assembly inside the latest package (https://www.nuget.org/packages/Serilog.Sinks.Loki/2.2.0)  does not contain the line ending and back-to-forward slashes fixes by #13

Originally posted by @REscobar in https://github.com/JosephWoodward/Serilog-Sinks-Loki/issues/21#issuecomment-712563792

It also not contains #18 if I pull the assembly over nuget. But if I use the source it is working.
There seem to be an wrong assembly.

Comparing the assembly in the NuGet you can see, that they are in Version 2.1 and 2.2 identical.

@kaflake @REscobar Yes, I must have missed this. I'm publishing an update that includes these now.

@kaflake @REscobar This is available as part of the latest 3.0.0 release.

Hi @JosephWoodward,

The same issue for 3.0.0. Nuget contains 2.1.0 build. Could you please check it?


icloudpd: init at 1.7.2

Description of changes
iCloud Photos Downloader

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] 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/)
22.05 Release Notes (or backporting 21.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.

Unfortunately seems to require iCloud account so cannot test it. Will use https://github.com/ghostops/ICloud-Shared-Album instead.


Disable LLVM JIT when cross-compiling for Android

To repro:
# Follow instruction in https://google.github.io/iree/GetStarted/AndroidCMake to build IREE
$ cd build-android
$ ctest -R iree/modules/check/test:check_llvm-ir_llvm_success.mlir_on_android_device

I will post the log later.
Tag @asaadaldien for visibility

I think we want to disable LLVM JIT for Android entirely and bring up LLVM AOT for it.

Yeah no JIT needed on Android!

On Jul 15, 2020 at 10:53,  <Lei Zhang (mailto:notifications@github.com)>  wrote:
I think we want to disable LLVM JIT for Android entirely and bring up LLVM AOT for it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly,   view it on GitHub (https://github.com/google/iree/issues/2528#issuecomment-658911470), or   unsubscribe (https://github.com/notifications/unsubscribe-auth/AAASMSK6URT3SAVDJ2K6ASLR3XUH3ANCNFSM4O2W4GKQ).

But still, thanks Hanhan for filing the issue! I retitled it to a task. :)

Sounds good, note that the tests under xla_ops for LLVM-IR should be disabled as well.

This is fixed, right? (also planning on removing LLVM JIT entirely soon)


Packaging is fast,Special slowly into the APP

Packaging is fast,Special slowly into the APP
I have used --prod
How can I solve?
ionic info
global packages:
@ionic/cli-utils : 1.4.0
Ionic CLI        : 3.4.0

local packages:
@ionic/app-scripts              : 1.3.0
@ionic/cli-plugin-ionic-angular : 1.3.1
Ionic Framework                 : ionic-angular 3.0.1

System:
Node       : v7.9.0
OS         : Windows 7
Xcode      : not installed
ios-deploy : not installed
ios-sim    : not installed
npm        : 4.2.0

Hello! Thanks for opening an issue with us! As this seems like more of a support question I will urge that you ask this question on our forum or on our slack channel. Thanks for using Ionic!

Thank you, I think I found the reason is I cordova version 6.0.0


Save branch name for each commit

To get the original branch name of a commit, I need to create a hook to add the current branch name in the commit message.
When GIT will do this natively?
prepare-commit-msg.txt

This issue tracker is dedicated to the git-scm.com website.
The question you have asked is related to the git program. Please see https://git-scm.com/community for information on how to ask questions regarding git.

As you remarked it, Git already supports this feature through the prepare-commit-message hook.


Sets value to empty when deleted

Description
The element sets the bound value to empty when it's deleted. Which is extremely undesired, when the dropdown is used to set a value, then dismissed as a modal or page navigated away in SPA.
Not to mention cases when the data is bound to a proxy, that instantly reacts to the changes with triggering actions on the server.
Live Demo
https://jsbin.com/zigijed/edit?html,output
Steps to Reproduce

Create and append vaadin-dropdown-menu bound to a value
Pick a value,
Remove vaadin-dropdown-menu

<dom-bind id="db">
  <template>
    Please pick a value from `vaadin-dropdown-menu`, then click on the button, observing how the value changes.

Picked value: {{model.selectedItem}}

    <vaadin-dropdown-menu id="dd" label="Label" placeholder="Placeholder" value="{{model.selectedItem}}" on-value-changed="{{remove}}">
      <template>
        <vaadin-list-box>
          <template is="dom-repeat" items="{{model.items}}">
            <vaadin-item value="{{item}}">{{item}}</vaadin-item>
          </template>

          <vaadin-item disabled>Option four</vaadin-item>
        </vaadin-list-box>
      </template>
    </vaadin-dropdown-menu>
    <button id="closeBtn">Click to close once done with selection</button>
  </template>
</dom-bind>

Expected Results
The value should remain as it was picked.
Actual Results
Value is always set to empty string"".
Browsers Affected

[x] Chrome
[x] Firefox
[x] Edge
[?] Safari 9
[?] Safari 8
[x] IE 11

Versions

vaadin-dropdown-menu: https://github.com/vaadin/vaadin-dropdown-menu/tree/62eca8957aea266514b180564d87e7285874bf84 (master)
webcomponents: https://github.com/webcomponents/webcomponentsjs/tree/a957286fa3cb157695cb82a1cdd9c822290f73d6(v1)

This seems to be a bad side-effect of the Vaadin.ListMixin’s observer for items and the way the value matching works in the <vaadin-dropdown-menu>.

During the removal, the items are removed before the dropdown menu, and removal of every item triggers the items observer. This notifies the dropdown-menu of the items array change.
Then, the <vaadin-dropdown-menu> tries to update the selected item based on the “new” items list.
At some point the item corresponding to the value gets removed. As the <vaadin-dropdown-menu> in that case cannot find the selected item, it sets the value to ''.

I don’t have a good quick fix idea for that. The <vaadin-dropdown-menu> value matching behaviour seems to mimic the one of the native <select>, which also changes the value if an item is removed, as I can see. But this is, of course, unexpected that the value change notification of any sort happens on removal (the native <select> does not notify the value change on removal too).
Maybe <vaadin-dropdown-menu> should detect its removal level before the items start to disappear, and disable the items change reaction. Hope, disconnectedCallback() can do that before it calls super.disconnectedCallback(), but not sure.


Updated schema-configurations.md to correct the last code example

Description
Updated schema-configurations.md to correct the following code example:
class CustomInfo(Info):
    @property
    def response_headers(self) -> Headers:
        return self.context["response"].headers

schema = strawberry.Schema(query=Query, info_class=CustomInfo)

to correctly use StrawberryConfig as follows:
class CustomInfo(Info):
    @property
    def response_headers(self) -> Headers:
        return self.context["response"].headers

schema = strawberry.Schema(query=Query, config=StrawberryConfig(info_class=CustomInfo))

Types of Changes

[ ] Core
[ ] Bugfix
[ ] New feature
[ ] Enhancement/optimization
[x] Documentation

Issues Fixed or Closed by This PR

#3650

Checklist

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] I have tested the changes and verified that they work and don't break anything (as well as I can manage).

Summary by Sourcery
Update the schema-configurations.md documentation to correct the code example by using StrawberryConfig for the info_class parameter.
Documentation:

Correct the code example in schema-configurations.md to use StrawberryConfig for specifying the info_class.

Thanks for contributing to Strawberry! 🎉 You've been invited to join
the Strawberry GraphQL organisation 😊
You can also request a free sticker by filling this form: https://forms.gle/dmnfQUPoY5gZbVT67
And don't forget to join our discord server: https://strawberry.rocks/discord 🔥


nixos/alist: init module

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[x] 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

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 309156 run on x86_64-linux 1

1 package built:

alist

@ofborg test alist

@ofborg test alist
@ofborg build alist

waiting for merged

waiting for merged

Please pay attention to #348717 first. This pr of the module will continue after the package. But the current problem is that the license of alist-web is not clear, and the upstream does not reply the issue. If it continues, I may package the alist with the unfree license.

new PR: #355716


Fix bug in OrbitCaptureGgpService/main.cpp

Fix name for the The log file created to match the name of the executable.

Thanks, merging this now.


[@azure/openai] Allow to specify a custom OpenAI URL

Is your feature request related to a problem? Please describe.
@azure/openai is compatible with the non-Azure OpenAI API. Nowadays, there are many local tools such as Ollama or LM Studio that allows to simulate an OpenAI API REST API to allow fully local testing.
Using the regular openai client it's possible to set a custom API URL (other than api.openai.com), allowing to use this local tools.
Currently it's not possible to do the same with the @azure/openai SDK, making it more difficult to perform local testing as we have to use another client in the codebase.
Describe the solution you'd like
When an OpenAPI key is used, I'd like to be able to also set a custom OpenAI API URL instead of the hardcoded one here: https://github.com/Azure/azure-sdk-for-js/blob/497d3edb3993260bfed7c68ab259fb377492b297/sdk/openai/openai/src/OpenAIClient.ts#L39
Describe alternatives you've considered
The alternative is to use another client entirely, which is not practical and make it more difficult to perform local tests.

@glharper Thanks for looking into it, PR looks good. For auth you're right, using the same as OpenAI path should work:

local OpenAI API providers such as Ollama or LM Studio doesn't have auth and ignore it anyways
hosted OpenAI API compatible providers use the same auth schema as the regular OpenAI API to maintain compatibility with their SDK (so Bearer token)

This will allow our samples to have broader compatibility way more easily than before, and make a lot of users happy 🙂

Hi @sinedied,  we strongly recommend that you migrate to use the AzureOpenAI client exported by the official OpenAI client library for JavaScript. Checkout the migration guide for how to do so. You can set custom URL by setting the baseURL input property.
Please let us know if you have any other questions!


404 Error Loading the .map File from NuGet Installation

When installing the bootstrap-select plug-in from NuGet via ASP.NET the script files are installed into a folder called Scripts in the root of the project.  In the bootstrap-select.min.js file there is a line of code:
//# sourceMappingURL=bootstrap-select.js.map
This line points to the map file.  However, for the NuGet installation the path should be:
//# sourceMappingURL=Scripts/bootstrap-select.js.map

Fixed in 1.7.2


Add Firewall Handling to Provisioners

If, for example, a cloud image has a strict firewall in place,
machine will not complete provisioning because it will not be
able to communicate with the Docker port (2376).
This patch adds a few firewallaction package, which is modeled
after the packageaction package. It also includes the Unbuntu
provisioner logic.
The decision to use different logic for each provisioner was
made after realizing that manipulating iptables would have to
be done slightly differently for each provisioner (since they
store their rules in different files) -- so there would already
have to be some provisioner awareness. Additionally, using the
provisioners' firewall manipulation packages (ufw, firewall-cmd,
etc.) will provide the extra benefit of persisting rules across
reboots more easily.
Signed-off-by: Christy Perez<EMAIL_ADDRESS>

This picks up where PR #1156 left off, but expands it a bit. @ehazlett, it turns out the pure iptables approach we discussed [I don't think] will work after all.
The CI build checks failed b/c I didn't add a test file yet -- but I can if we think this is a good way to go.
/cc @nathanleclaire

@ehazlett, @nathanleclaire Ping.

I'm pretty keen on this basic idea, but would be hesitant to move forward on it without supporting at least Debian and Red Hat as well.
@ibuildthecloud Do you have any comment or sentiments on this basic idea from a RancherOS perspective?
@davetucker @mrjana @mavenugo @nerdalert Do you have any opinions about how this sort of thing should be handled by Machine?  I think it's pretty relevant to your interests ;D

@nathanleclaire, thanks for the look! I've got the RH provisioner done (and tested) locally. With feedback from everyone you just pinged, I can add others as well.

I've got the RH provisioner done (and tested) locally.

Oh nice!

One thing to take a look at is that libnetwork has an iptables module, I'm not sure if it's relevant here but I would really prefer to re-use code if we can.

@nathanleclaire I think I looked at libnetwork's iptables module, but I'll look again. It has been a while since I started all this!

ah, @nathanleclaire, I didn't see a way to persist a rule there. I think that is fine for docker (IIUC), but we'd need this rule to always be there across reboots. Can someone from the libnetwork confirm? Maybe @mrjana?

@clnperez Thanks for all the good work on this one, however the scope of Machine is exploding as-is and I think we need to re-group and/or define the API barriers / roles of the tool better before moving forward with things like this.  However, would love to see some discussion going on how to resolve the various networking / port forwarding / firewall issues.


Dev-mode Suggestion

The option to run the jobs synchronously in development would be really nice.
Is this possible with the current state of the package?

Yup, it could be doable, same with https://github.com/RomainLanz/adonis-bull-queue/issues/20

For now I just made a BaseJob that all other jobs inherit from
import Application from '@ioc:Adonis/Core/Application'
import { JobHandlerContract, Queue, type Job } from '@ioc:Rlanz/Queue'

export default class BaseJob implements JobHandlerContract {
  // needs to be implemented in each job, imports cannot be inherited properly
  public static get $$filepath(): string {
    // must be implemented by subclass
    throw new Error('Must be implemented by subclass')
  }

  constructor(public job: Job) {
    this.job = job
  }

  public static async run(payload) {
    const job = new this(payload)

    if (Application.inDev) {
      job.handle(payload)
    } else {
      Queue.dispatch(this.$$filepath, payload)
    }
  }

  /**
   * Base Entry point
   */
  public async handle(payload: any) {}

  /**
   * This is an optional method that gets called if it exists when the retries has exceeded and is marked failed.
   */
  public async failed() {}
}

so I'll just call the class method of SomeJob.run() and that will either queue it up or run it synchronously.

What do you think of having a flag in the configuration?
defineConfig({
  instant: true
})

(I am not sure about the name)

I like that approach! Easily configurable per environment which would be great :)


A11y_Visual Studio Code Client_Extension_Rating_Screen Reader: Jaws is not announcing the tooltip information available on "rating" link.

[(Check out Accessibility Insights!)]- Identify accessibility bugs before check-in and make bug fixing faster and easier.
GitHubTags:
#A11yTCS; #A11ySev3; #DesktopApp; #Win32; #Visual Studio Code Client; #BM-VisualStudioCodeClient-Win32-Jan2024; #WCAG1.3.1; #ScreenReader; #JAWS; #NVDA; #A11yMAS;
Environment and OS details:
Visual Studio Code insider version 1.86.0
Microsoft Windows 11 Enterprise 22H2 Build 22621.3007
JAWS
NVDA Version: 2022.2.3
Repro Steps:

Open Visual Studio Code Insiders editor
Using "Ctrl+Shift+X" key navigate to the extension side view bar option.
Select an extension and using "Tab" and "Arrow" keys navigate through the extension details window on the RHS.
Tab till rating link.
Verify whether the Jaws is announcing the tooltip information available on "rating" link or not.

Actual Result:
Jaws is not announcing the tooltip information available on "rating" link when we are navigating using the tab key.
Note: Issue is not repro'ing using the NVDA
Expected Result:
Jaws should announce the tooltip information available on "rating" link.
User Impact:
Screen reader only users will not be able to get any information about the rating.
Attachment:
JAWS:
https://github.com/microsoft/vscode/assets/124244478/ce118b95-6edd-4c16-a903-432a42a5697d
NVDA: Issue is not repro'ing using the NVDA.

Since the issue is not reproducing when using NVDA, closing this as not actionable on our end. @isidorn pls reopen if you disagree


[USM] Fix issue in postgres table name extraction

What does this PR do?
When handling the issue of encountering the if exists string, we need to support it in a case-sensitive manner to address all possible variations."

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Does IRQL respect the ExecutionLevel of the queue?

This page should explicitly state whether the IRQL of this callback is adjusted by the ExecutionLevel parameter of the WDF_OBJECT_ATTRIBUTES supplied at time of queue creation.

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

ID: 852d986e-17ed-8ac1-6783-1a74aee7f043
Version Independent ID: 061518a3-b18b-d469-06f6-4e4d59aad210
Content: WdfIoQueueReadyNotify function
Content Source: wdk-ddi-src/content/wdfio/nf-wdfio-wdfioqueuereadynotify.md
Product: windows-hardware
GitHub Login: @windows-driver-content
Microsoft Alias: windowsdriverdev

Yes the execution level is respected. This should be clarified in WdfIoQueueReadyNotify, WdfIoQueueStop, WdfIoQueueDrain, WdfIoQueuePurge.

These changes are live.  See extra note on https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/content/wdfio/nc-wdfio-evt_wdf_io_queue_state and pointers to it on WdfIoQueueReadyNotify, WdfIoQueueStop, WdfIoQueueDrain, WdfIoQueuePurge.


Updated LeafletOsmMap to remove unSaved markers if a user clicks else…

Issue Number: 226
Issue Description: If you click on multiple points of the map, each location will get a pin without you hitting "save" on the pins. The expected behavior is that one pin will be created, and if you don't hit "save" the pin will be removed when you click elsewhere on the map.
Summary of solution:
Added "unSavedMarker" to components local state to track unsaved markers
When a new marker is created, the old marker is removed
Can this issue be closed?
Additional code needed to clear "unSavedMarker" in the state when a marker is successfully saved, that feature is throwing an error (in Chrome Canary) so testing was not possible
Should any new issues be added as a result of this solution?
Saving a marker throws an error
Uncaught (in promise) TypeError: Failed to fetch xhr.js....

@jkwening
I have replicated the issue in the code I pulled this morning (see attached). Without my code you get the "Before_new_Code" picture where you can see multiple markers

With my code (lines 175-178) you get the "after_new_code" picture with only one marker after 5 or so clicks on the map.

The comment I put in for on line 232 may not need new code since hitting the delete button does remove the marker. The comment at line 195 ( //TODO: delete temporary marker from unSavedMarker) is to write code to clear the unSavedMarker in state. I couldn't write/test the code since the "SaveBtn" wasn't working in the code I had.
Let me know if you have any further questions.

@steveone as I noted, the code in this PR resolves the multiple dropped pin issue. What I couldn't replicate is the issue you mention about "SaveBtn" not working. It's working fine on my end - this feature was completed a week or so. I'm able to save a newly dropped pin without any errors. Can you create an issue with the screenshot of the error or stack trace if you'r still getting this error after merging in the current development branch?
Regarding the to statements, if I understand correctly, this not actually a delete but rather setting the unSavedMarker state to null?

@jkwening I have the latest code as of 3/16 in the morning and get the following errors when I click on the "saveBtn" (it appears to not work since the button doesn't  go away). I am using Chrome Safari on mac OSx

You are correct that the "Todo" comments are intended simply to set {"unSavedMarker" : NULL} in state when someone hits the saveBtn.

I can't seem to replicate this one either, are you starting mongodb prior to starting the server?

@motosharpley yes, I have MongoDB running as well as the server and client.

I've updated the code in the "saveBtn" to clear the unSavedMarker and removed the //TODO comment from the "deleteBtn" as the code would have been unnecessary.

wonderful - going to go ahead and merge this in now. Thanks.


feat: SBML validation in PRs

Main improvements in this PR:
For PRs, it is required now to check the validity of the model at http://sbml.org/validator
I hereby confirm that I have:

[X] Tested my code with all requirements for running the model
[X] Selected devel as a target branch (top left drop-down menu)
[X] If needed, asked first in the Gitter chat room about this PR

@edkerk great idea, will create a new PR for it. Will not include validateFlag = 1 though, as already the default returns the existing errors, whereas with this option 6766 warnings are also returned, having to do with either missing units or initial concentrations (which don't really apply to our model).


[Transforms] initialization of static members done after class is exported

Expected:
    var C1 = (function () {
        function C1() {
            this.m1 = 42;
        }
        return C1;
    }());
    C1.s1 = true;
    exports.C1 = C1;

Actual:
    var C1 = (function () {
        function C1() {
            this.m1 = 42;
        }
        return C1;
    }());
    exports.C1 = C1;
    C1.s1 = true;

Failed tests:

es3defaultAliasIsQuoted.ts
amdImportNotAsPrimaryExpression.ts
tests\cases\compiler\systemModuleTargetES6.ts

Fix in latest commit

Still repros in RWC: Azure_ContactsExtension.

this is currently by design. since the ts transforms run before both module and es6 transforms.
there should not be any functional differences though. if you see instances where the code is functionally different please reopen.


There's quite a bit of warnings for missing documentation, we might want to jump on that.

Pull Request Test Coverage Report for Build 436

29 of 31 (93.55%)  changed or added relevant lines in 12 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+2.7%) to 78.807%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/seedu/address/logic/commands/LoginCommand.java
0
1
0.0%

src/main/java/seedu/address/logic/commands/layer/LayerAddCommand.java
2
3
66.67%

Totals

Change from base Build 435:
2.7%

Covered Lines:
1863

Relevant Lines:
2364

💛  - Coveralls

Codacy doesn't like underscores in test function names. I don't like Codacy.