Events

You can probably just get ride of the db and use NATS…
code will be simpler and perf / ha higher.

@gedw99 I can see how  transmitting of incoming events could possibly be compatible with NATS. But how would you handle requests for old events? Especially with a filter on author+kind etc.

Do you need old data ?
Use nats kv if you do.
If you need old images use nats onj store.
both as often use as a db.

https://docs.nats.io/using-nats/developer/develop_jetstream/kv

No worries - did not know you needed versioned data …
here’s some ways I do data versioning:
minio / s3 is a versioning data store.  straps using flight sql allows a db with the data residing on s3.


cannot refresh immediately

On Android, clicking on some widgets like buttons and calendars is not responsive enough, and you even need to click again somewhere else to respond. Overall, it doesn't refresh in a timely manner.

On Android, clicking on some widgets like buttons and calendars is not responsive enough, and you even need to click again somewhere else to respond. Overall, it doesn't refresh in a timely manner.

With these three lines of code
viewDialog->activateWindow();
viewDialog->raise();
QApplication::processEvents();

This solves the problem.
Why?
viewDialog->activateWindow();
This line of code sets the window as active. It sets the focus of the window to the current dialog, making it the window the user is currently interacting with. Normally, the window manager switches the focus to that window and places it on top of other windows.
viewDialog->raise();
This line of code places the window at the top of the stack, making it appear above the other windows.
QApplication::processEvents().
This line of code forces all pending events to be processed in the event loop, which is used by Qt applications to process user input, drawing events, and other asynchronous tasks. Typically, the event loop is processed automatically in the main loop of the application, but sometimes it needs to be forced at specific points in time to ensure timely responses and updates to the interface.
In practice, however, I think viewDialog->activateWindow() is the line that has a role to play, as can be demonstrated by a simple test.


Updates for Lacework v4.20

fix: removed policy_ui parameters for compatibility
fix: cleanup for HTTP 204 response on search endpoints
refactor: readability improvements for tests

Hey bud.  Sorry I missed this.  Looks good!


Add SIGINT handler in artichoke-frontend

Crate signal_hook.
In airb, CTRL-C should wipe the current input and write a new empty prompt line.

From GH-337:
ctrlc: Interrupt handling.
signalhook: Interrupt handling:
extern crate crossbeam_channel as channel;
extern crate signal_hook;

fn notify(signals: &[c_int]) -> Result<channel::Receiver<c_int>> {
    let (s, r) = channel::bounded(100);
    let signals = signal_hook::iterator::Signals::new(signals)?;
    thread::spawn(move || {
        for signal in signals.forever() {
            s.send(signal);
        }
    });
    Ok(r)
}

This was fixed a while ago in https://github.com/artichoke/artichoke/commit/08d4b502dfe219df24fb207045075f17e972f70a (it looks like before this issue was filed?)
I'm not sure if the intent of this issue was to support interrupting the VM arbitrarily. Closing.


X icons are not clickable bug

I just found out this component and it's really cool, thanks a lot! One thing missing was "X" buttons wasn't working, I was really confused but after some research I found the solution.
https://ui.shadcn.com/docs/components/button
There's a changelog at the bottom of the page which says
"2024-10-16 Classes for icons
Added gap-2 [&_svg]:pointer-events-none [&_svg]:size-4 [&_svg]:shrink-0 to the button to automatically style icon inside the button."
So yeah, "[&_svg]:pointer-events-none" this one is preventing from clicking to the "X" icons. So I added "[&_svg]:pointer-events-auto" to "Button" className, it's working same like in the demo website right now.
Pull Request: https://github.com/sersavan/shadcn-multi-select-component/pull/30

thanks bro @ccaner37, can confirm it works!

You could also wrap the XCircle and XIcon components with a basic button and move the onclick method from the "X" components to the button.

I encountered the same issue when using the MultiSelect component inside a Dialog, where the "X" icons weren’t working properly, even with the modalPopover={true} option enabled.
After some investigation, I managed to fix the issue by adding the [&_svg]:pointer-events-auto class directly to the MultiSelect:
<MultiSelect   modalPopover={true}   className="[&_svg]:pointer-events-auto"   {...props} />
This ensures that the "X" icons in the MultiSelect are clickable, even when placed inside a Dialog. I hope this solution helps others facing the same problem!

I’ve added the "[&_svg]:pointer-events-auto" class to the component. Thanks a lot for the suggestion and detailed explanation! 🙌
Close this issue


Few issues feedback

Moving along downloading the surface assets about 500 now,  using the earlier script it had the "KeyError: 'id' " see pic.
There are 4 id's that don't exist tried the "remove_asset_from_metadata" script but quit on error, missing but owned are;
wfgpebvaw
we2rbizaw
vktudjsaw
vktffapaw
Ran the "calculate_all_checksums" seemed to help with the ealier KeyError  maybe but will run checksum again if needed.
The "MemoryError" has halted the download script few time seems no issues restarting, been using the new versions when they come.
Not sure  Line 38  DownloadAllAssets  type -issue or not?
Just given feedback, works for me,  Thanks!

Hey there, thanks for the feedback!
The place the KeyError happens in would suggest that the server returned a 200 (success) code but not a valid response, which is unusual behavior for a server. Anything besides 200 is caught and retried.
Since the latest update which switched away from recursive function calls in the download script, I've noticed a big decrease in weird, unexplainable issues that I've been unable to diagnose properly and that usually crashed the script after a while. Let me know if you're still experiencing the issue on the latest code!
And thanks for the IDs! I'll check those and add them to the readme. Also, you mentioned that the remove_asset_from_metadata script quit on error? Which error?
As for the MemoryError, that's not an issue I've encountered myself. The complete metadata requires quite a bit of RAM to be loaded in initially - this memory usage does go down substantially as downloads progress, but I've seen it go as high as 4-5GB. If you don't have enough free RAM when you run the script, then (I assume) that error occurs.

Sorry can't remember the error, sure it would reproduce all i did was input an id like vktffapaw and no go.
Have 32GB on this machine with Python 3.12.6 64bit ram usage 40%.
Just after posted the above issues resurfaced;
Using the script just before the most recent, token expired input new token got this like above;

Closed and started python ran script received the mem error again tried newest script same.
Now running checksum calc did this the other day when had these issues all was good whenever it halted closed and restarted no problem but not sure if it was checksum py that helped but will see.

After I ran checksum py back to downloading, few hurdles all good, like you have a 10MB/s connection with the traffic now varies from half to full bandwidth lately.

All good...

Huh, it would surprise me if the checksum script would be able to fix the issues you're describing, since the download script only really (besides saving new checksums) uses the checksum file to figure out which assets have yet to be downloaded. Either way, if it works now, great!

My thoughts too just coincidence but...
Got up this morning with clear head and...
Oops!
The memory problem was user error, running in PyCharm, JM checked heap set 2048 and doubled it to 4GB.

Ah, gotcha!

Regarding for resuming "download_all_assets" for me have not had issue with that, shutting down when token expires or with the issues from my mem allocation problems, seems all is working great won't know if missing anything yet but looks good to me  ...Thanks for the great work!!
Just wish new about your script earlier people are hitting the servers, was utilizing full download bandwidth now last few days 6MB/s with moments of top speed of 13MB/s.  But been downloading "surface" material with no issues now and at about 1500 files at 2TB yah along way to got to 7352 files!!
Not worried now it doesn't effect the cat's interested in but took a break and tried the "remove_asset_from_metadata" again, maybe missing something before it just wasn't taking ID but now get this on start;


Fieldsets in blocks?

Is it possible to use fieldsets inside of blocks? If you wanted to really customize blocks, tabs would be useful for separating out data.

Hey @raymondtri, I want to say, why not? We didn't consider it in design and UX but I'm sure it technically works.

I tried using fieldsets in blocks and it gets really unhappy about fieldsets or sections inside of blocks.  I also tried injecting custom vue components into blocks and it doesn't work well when you inject multiple layers of vue components (parent->child->n). One works just find though, even though that feature is not fully supported yet. I used the information from another github issue on here.

@raymondtri For tabs I used css tabs and it works like a charm, also css-only so no messing around with any js :)

I don't think we intend to officially support this as our design system has no definition of how a fieldset should look like inside of a block. Closing as this hasn't been active in a while, feel free to open a new issue if you still need support with blocks customization.


Opening figures, simulink models, etc. in VS Code

Implements opening .fig, .slx and other MATLAB files through VS code's context menu.
Note! I'm brand new to developing in TypeScript, and I'm having some implementation issues (specifically, getting the menu option to occur in the context menu.) Still, I wanted to put this here in case @dklilley or any of the other maintainers want to help with the final steps!

Hi @Gusmano-2-OSU, thanks for working on this! I will plan to take a look at this soon (likely early next week).
Before I take a look, I just wanted to clarify - you are having some difficulty getting the "MATLAB: Open File" option added into the context menu?

Hey @dklilley, that's exactly right! The idea is, you right click any file supported by MATLAB's open command, and you get a context menu command that lets you run the command on that file. As someone who works a lot with figures and Simulink models, I'm hoping it can significantly increase the speed of my workflow!
My dream implementation of this is that a normal click would open these files as a tab in the current vs code window, but it would definitely be good enough if they opened in a separate MATLAB window.
Thanks for taking a look!

I believe that the issue is just with where the configuration for the context menu item was being added within package.json. Take a look at my comment and see if it helps!

I don't think there are any issues with the loop as you have written it. Instead, even if there are multiple files selected in the Explorer, only one URI is passed to the command.
Unfortunately, after some digging, I don't believe that this is functionality which is publicly available for extensions to leverage.
While there are some context menu actions which do work with multiple files selected (e.g. Open to the Side), these are commands provided my Microsoft and are implemented internally (e.g. the implementation of Open to the Side leverages an internal getMultiSelectedResources API).

That's too bad - maybe a project for another day if we could ever use the getMultiSelectedResources API. For now, I've reverted the commit and this should be ready to pull!

Agreed - hopefully they add some public functionality soon!
The changes look good to me! One of my colleagues will be reaching out soon with information about signing the CLA.

Hi. Thanks for the contribution! Can you contact me about signing the CLA? I can help from there. Thanks.

I sent you an email, @nothans!

Thanks for working on this!

Sure thing! I look forward to contributing more in the future!


localhost instead of thinkty.net in feed.xml

For some reason, the feed contains localhost instead of thinkty.net

Answer from the creator : https://talk.jekyllrb.com/t/jekyll-seo-inserts-localhost-urls-in-metadata/1861/2
When using the serve command, Jekyll replaces the specified url with localhost.
Therefore, before deploying, you must use the build command.


Move nginx-proxy service to top-level

nginx-proxy has been treated like any other service since the start of
this repo, but it's actually quite different because it has no stack and
no Makefile. It's also a top-level service that's depended on by all of
the app stacks. This moves it to the top-level docker-compose.yml file
to make it more visible and simplify writing tests for (other) services.
The downside of this is having to 'shove' the 'proxy.conf' file in the
'config' directory. Another way to approach this might be to nest all
the 'govuk' services in a directory with this name, but that would be a
bigger change that touches parts of every docker-compose.yml file.

Do we have any docs on adding a service? It's not clear otherwise that you'd need to add the domain of an app to this list when someone in the future goes to add a new app/service. Be kind to your future devs!

@chao-xian we have a spec to ensure it gets done, and I'm currently writing the next "Learning GOV.UK Docker" tutorial that will cover nginx-proxy.

@benthorner awesome

@benthorner The downside of this is having to 'shove' the 'proxy.conf' file in the 'config' directory. if we needed to have a top level conf file for elasticsearch, would we need to do the same?

@chao-xian yup. I'm not a great fan of the 'config' directory because it's ambiguous what's inside. On the other hand, it doesn't seem to be causing any pain.

@chao-xian did you have any more comments?


Space Geek (how to live test and card function)

I have the Space Geek skill working (modified for my 'facts') and have several questions.

Is it possible to do live (physical) testing with my Amazon Dot when my skill is still in development mode?  If so how?
I'm using the Service Simulator, submitting my text questions and viewing the response (as well as using the "Listen" button to hear the response.  However I'm not seeing anything in my Alexa.Amazon.com companion app "card" function.  I've edited in the Application ID and based on what I can discern, I see a User ID (which I'm guessing if the ID for ME and my Alexa account/device....  Is the card functionality available while I'm in test mode?  What do I have to do to see my questions and responses in 'my card'?

Thanks very much (This old PDP-11 assember guy is reading a tutorial on JavaScript.  Straaaannge but neat!

this can be closed as I figured it out.  You need to create your Alexa skill with the same account credentials as the account used to see up the Alexa (Dot) device initially.  It's working just fine.  I can ask Alexa questions and get responses.


Terraform is missing cloud-sql client permissions for service accounts

TL;DR
Service Accounts associated with Cloud run are missing a required Cloud-sql client permission that was available before.
The following config seems to have got removed causing cloud run services ro fail :
resource "google_project_iam_member" "exposure-cloudsql" {
project = data.google_project.project.project_id
role    = "roles/cloudsql.client"
member  = "serviceAccount:${google_service_account.exposure.email}"
}

/assign @sethvargo

@mikehelmick i submitted a PR with the fix if it will help.
#579

I commented on the PR, but the Cloud Run services should not need this permission. They communicate with Cloud SQL over a local VPN, and thus the Cloud SQL proxy (which is what requires the IAM permission) is no longer required for this setup.


ui: "upload permanode fail, expected blobRef not in response"

Got this when trying out a new Camlistore install on GCE using the launcher...
First blob uploaded:

It did seem to work on later uploads, though?

I've just tried with the launcher currently deployed and could not reproduce. Not sure what else to check.

I just got it again on a newly-deployed instance.
The server logs say:
Dec 30 17:36:48 camlistore-server.c.camlistore-gce-dev.internal systemd-docker[1475]: 2015/12/30 17:36:48 Got websocket message `{"tag":"q0","query":{"sort":"-created","expression":
" ","describe":{"depth":1,"rules":[{"attrs":["camliContent","camliContentImage"]},{"ifCamliNodeType":"foursquare.com:checkin","attrs":["foursquareVenuePermanode"]},{"ifCamliNodeType
":"foursquare.com:venue","attrs":["camliPath:photos"],"rules":[{"attrs":["camliPath:*"]}]}]},"limit":50}}`
Dec 30 17:36:48 camlistore-server.c.camlistore-gce-dev.internal systemd-docker[1475]: 2015/12/30 17:36:48 Added/updated search subscription for tag "q0"
Dec 30 17:36:55 camlistore-server.c.camlistore-gce-dev.internal systemd-docker[1475]: 2015/12/30 17:36:55 Client error: Error receiving blob sha1-6e4c2a3e81edbd9f5b8e6598c855c73d664
444b0: unexpected EOF

And on the second drag-and-drop, it worked (just like before):
Server says:
Dec 30 17:38:27 camlistore-server.c.camlistore-gce-dev.internal systemd-docker[1475]: 2015/12/30 17:38:27 Received blob [sha1-25b3887df787459017789df0cfec874605901e01; 548 bytes]
Dec 30 17:38:28 camlistore-server.c.camlistore-gce-dev.internal systemd-docker[1475]: 2015/12/30 17:38:28 Received blob [sha1-f9926c18c2c26e54bf33201f95a402f9b5f7b29a; 732 bytes]

I've been able to reproduce.
First thing I see is that the file blob is there, but no permanode:
% camtool list -describe
sha1-08112e627ef2ad29205c3f61ace3e1a9022efb27 74626
sha1-0b07e1a8f6705afb468842e9d03d8e753e6ad598 262144
sha1-15e0faf1b684841b3ca663acf91322ca1a035feb 81499
sha1-249501c5211d471819c4a125d512b34c65fb53f2 1319	file (automata.jpg size=1566105)
sha1-25ff99838f19ed9e0b8dd727a42690807c7b29ff 69145
sha1-295dcb3004a18c830e40d779410c5c40cb162561 65686
sha1-2dd44b0a30fddd8554f6f24c96f6261723c2d837 75506
sha1-302fedcd1c7fb98262e3a40d09c8f727e5bbbd7d 84282
sha1-33f0d4690e10eff03cbb19c930f9a1c520ba0ffe 659	bytes
sha1-3789b097b8c09a49dfa1114739a3c67c802ad474 <not described>
sha1-46c170af4a293861eaadabd201011d6b09ef6ef4 76531
sha1-47bb05fd0e276d3bb1de193bb70ea87cfb7c782d 71704
sha1-4830de63e4ff7880edcadee74b0a7e6adb6eb8ab 67275
sha1-497247ba04329c232b749a7bbec55d6831b5084e 6084
sha1-5bd54bd8cb308f0a60f18d1f45eeb24e26d36dde <not described>
sha1-7051f32bc8064f0be3e5f912c25c0cc2b1f84482 259	bytes
sha1-7926eb29374b34a2a8e3625d2e2ab1205a86d28a <not described>
sha1-7d5e0af6335995b83fad0c6a0c8eda669a194039 70852
sha1-8adc0c760b968c757c60b4a383b19ddc6eddb792 76102
sha1-8f7b142cbe0b570611bcfc7784f72ab25bb6a3ce <not described>
sha1-92a88dd2b2d5b66603f46ddebd20e7111061098f <not described>
sha1-98449826fed3ee77d34d28c7401ec75ab2c033f8 74779
sha1-a771cc4a0c4d5d73655015ef0dd7fa6dbecb3583 95752
sha1-ace5a37d7db21c682accc446fa53ae4e8b053c49 <not described>
sha1-ad0bea6a49fa364d6212b040b16257ec758711ac 76957
sha1-bea2d063353dc463ed263d1f4d65b0d7ee9545e0 <not described>
sha1-c5864c7a390d1845c1089bb28707e8f6f7bc2d1c 81873
sha1-c6ff837d67bba901368fd9325f48e0f620890f01 259	bytes
sha1-d8a02f324c28e42fb29e0c76c4b4c2d34ce435fc <not described>
sha1-da39818eb9d46516c296269166e993cb14cb5a1b <not described>
sha1-ea6d6d4b553afa09b5368f3d932019aadff0054f 84268
sha1-edee82cc2ebaf8d7ecb857c0f66244c07865f9bb <not described>
sha1-f3c0c80b643789879caf7ef24356ec21a8d24c94 71040
sha1-f4ec1d378d97d509f79dce1ed49936f942be1c2c <not described>

% camget sha1-249501c5211d471819c4a125d512b34c65fb53f2
{"camliVersion": 1,
  "camliType": "file",
  "fileName": "automata.jpg",
  "parts": [
    {
      "blobRef": "sha1-0b07e1a8f6705afb468842e9d03d8e753e6ad598",
      "size": 262144
    },
    {
      "blobRef": "sha1-302fedcd1c7fb98262e3a40d09c8f727e5bbbd7d",
      "size": 84282
    },
    {
      "bytesRef": "sha1-33f0d4690e10eff03cbb19c930f9a1c520ba0ffe",
      "size": 616790
    },
    {
      "blobRef": "sha1-f3c0c80b643789879caf7ef24356ec21a8d24c94",
      "size": 71040
    },
    {
      "blobRef": "sha1-2dd44b0a30fddd8554f6f24c96f6261723c2d837",
      "size": 75506
    },
    {
      "blobRef": "sha1-46c170af4a293861eaadabd201011d6b09ef6ef4",
      "size": 76531
    },
    {
      "blobRef": "sha1-c5864c7a390d1845c1089bb28707e8f6f7bc2d1c",
      "size": 81873
    },
    {
      "blobRef": "sha1-08112e627ef2ad29205c3f61ace3e1a9022efb27",
      "size": 74626
    },
    {
      "blobRef": "sha1-295dcb3004a18c830e40d779410c5c40cb162561",
      "size": 65686
    },
    {
      "blobRef": "sha1-4830de63e4ff7880edcadee74b0a7e6adb6eb8ab",
      "size": 67275
    },
    {
      "blobRef": "sha1-ea6d6d4b553afa09b5368f3d932019aadff0054f",
      "size": 84268
    },
    {
      "blobRef": "sha1-497247ba04329c232b749a7bbec55d6831b5084e",
      "size": 6084
    }
  ],
  "unixMtime": "2013-01-30T13:46:35Z"

and after a (successful) retry, the only difference I see are the new claim and permanode. So it would seem, at least in that case, that the permanode creation is where the problem lies.

For the record, the error comes from:
client-side: server/camlistored/ui/server_connection.js : uploadString_
server-side: pkg/blobserver/handlers/upload.go (handleMultiPartUpload)

Doing some experiments since the "debugging with prints" strategy doesn't play well with the rebuild/upload new image/deploy on GCE/ cycle...
Interestingly, on a fresh deploy, if I first camput -filenodes a file, not only does it succeed, but then the subsequent first upload through the UI succeeds as well at first try.
I wonder what's getting "unwedged" by a first upload...

The only lead I can think of, is that the server first needs to have the public key blob uploaded to it. But the sign handler does that automatically if needed nowadays.
I guess I could try and confirm the hypothesis by restarting an instance which already has the public key blob (and only that blob) in its bucket.

I then created a new instance through the launcher, and I didn't see the bug when I dropped my first image in the UI. Of course it could be some sort of coincidence, but I'm going to take that as an indication that it is not for now, and keep on following that hypothesis as a lead.

Again, it could be red herring, but with https://camlistore-review.googlesource.com/5690 (the current WIP docker image for the launcher has this change), I'm not seeing the bug.

ok, the good news is I can reproduce the problem with camlistored running on my server, so debugging will now be much easier.

systematic repro for that problem:
-on a remote server: start fresh camlistored (wipe blobs, run with -reindex)
-open new incognito window in chrome (otherwise there's apparently some caching preventing the problem)
-navigate to UI
-drop first image on UI

@bradfitz Just in case, I've just retried with an updated http2, and I can still reproduce that bug.

@bradfitz I have isolated the problem, but I have no better solution than this hack for now, PTAL:
https://camlistore-review.googlesource.com/5706
the WORKINPROGRESS docker image has this fix, in case you want to test a deploy with it.
Maybe you know someone who knows more about Chrome and could shed a light on this? I'm saying Chrome, because I haven't seen the problem on firefox so far.
CC @dotMR

additional: @bradfitz and I found more about the cause: for each "new" URL it seems the browser first tries an unauthenticated (no Authorization header) request, and if it gets a 401 it immediately retries with the (previously entered by user) Basic Auth for Authorization.
That usually works fine, except that in the uploadString_ case, we append a Blob to the form data, and Chrome apparently messes up that append in the retry, so we end up sending garbage instead (zeroes I think).
It is basically the same problem as described http://inedo.com/support/kb/1019/workaround-for-chrome-file-uploading-bug

@bradfitz I made https://gist.github.com/mpl/521b24fd5a802075c8c1 , which seems to show that the bug is indeed fixed when using the native implementation of XMLHttpRequest.
So I'm starting to suspect our (now dating) vendored closure implementation of goog.net.XhrIo.
I've started updating closure at https://camlistore-review.googlesource.com/5736 but I haven't tested yet either if that fixes the problem or if it doesn't break anything else on the UI.
Also I'd like to do a version of the gist mentioned above that uses our old closure to see if I can get a repro with it.

Oh! I didn't even know we weren't using the native XHR. Good to know. Promising updates.

Sad to report that updating closure does not seem to fix the problem. Now on to modifying my repro so that is uses closure instead of native, just to be sure.

ugh. I can't get my repro code to "misbehave" so far. My POST requests have an authorization header right from the start, so of course the actual problem can't occur. I don't know what it is with our UI requests which make them try a first time without authorization.

As an additional note: on firefox, the UI also sends its first requests - for each new URL or method - without any authorization (which I still can't reproduce in a simpler example, as all requests except the very first one have an authorization), but it doesn't mess up the resend of the Blob in the FormData.
(which is why the bug does not show up on firefox).

also, I've tried forcing the credentials so we'd get authenticated requests right from the start with something like (in uploadString_):
this.sendXhr_(
	this.config_.blobRoot + "camli/upload",
	goog.bind(this.handleUploadString_, this,
		blobref,
		{success: success, fail: opt_fail}
	),
	"POST",
	fd,
	null, // opt_headers
	0, // opt_timeout. 0 means no timeout, which is the default anyway.
	true // opt_withCredentials
);

which did not seem to work.

@bradfitz finally got a minimal repro that we can show at https://gist.github.com/mpl/dc5d285da61e78739e30
Any people in particular you want me to show it to, or shall I simply report it as a bug against chrome ?
I'll explain in chat/hangout why it took so long (partly because I'm an idiot), and why it doesn't really help us (yet) for Camlistore.

I think we can do two things in parallel:

report it & see if Chrome people care. It doesn't matter whether they do, because:

we can also just work around it: we can make GET /ui/ serve an auth token for XHR calls. We'll make sure "GET /ui" never serves CORS headers, and then for all XHRs, send HTTP request header "Authorization: Whatever XXXXXXXXXXToken". Because we set the Authorization header, XHR won't re-try requests.

Thoughts?

(I also like removing the ambiguity over whether the browser will be retrying things)

sgtm for 1). btw, the same behaviour can be observed when the server replies with a 307 to our POST: the client will follow the redirect and repost with a similar mangled body. Whereas firefox again does not have this problem.
I think 2) might be the answer to "what is the difference between our UI and my repro" that I could never find and that forced me to cheat to get that repro.
I'll try it and get back to you.

repro demo integrated to camweb: https://camlistore-review.googlesource.com/5747

And chromium bug filed: https://code.google.com/p/chromium/issues/detail?id=578914

people, we'll be making the plan described in 2) of  https://github.com/camlistore/camlistore/issues/660#issuecomment-172158005 anyway
but it looks like the underlying chromium bug has been fixed recently:
https://code.google.com/p/chromium/issues/detail?id=567692
so, just update your chrome!

e03d0af04f9e0e229d836786042d0744ff36a605


ROX-17702: temporary custom store implementation

Description
A detailed explanation of the changes in your PR.
Feel free to remove this section if it is overkill for your PR, and the title of your PR is sufficiently descriptive.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
TODO(replace-me)
Use this space to explain how you tested your PR, or, if you didn't test it, why
you did not do so. Valid reasons include, for example, "CI is sufficient",
"No testable changes". Feel free to attach JSON snippets, curl commands,
screenshots.
In addition to reviewing your code, reviewers must also review your testing
instructions and make sure they are sufficient.

Current dependencies on/for this PR:

master

PR #7136

PR #7137

PR #7138

PR #7160   👈
PR #7053

This comment was auto-generated by Graphite.


fix: improved detection of all peripherals

When the plugin scans for a new device, it configures a handler for Noble's scanStop event. However, the handler will only fire once, causing devices to not detect while using the plugin. This quick fix reuses your startDiscovery() function which will set the scanStop event handler again if not all devices are found.

Hi Eric,
Thank you for the PR! Have you tried this in a multiple device environment? I thought I was doing like this but I had multiple bluetooth and result in a endless loop of start and stop.
Please let me know if you have such environment to try.

I have 8 devices configured on my end, and the plugin wasn't detecting all of them until I modified those couple of lines. It stops scanning when all devices are found, and it would scan in an infinite loop until everything is detected.
Without this change, the plugin was unusable since it was only detecting ~3 devices at a time out of 8.


Cloud Build script

Motivation
After killing build_and_redeploy.sh, one functionality that deserves it's own script is cloud building
Proposal
Creating a script for cloud building
Test Plan
Ran the script, saw that the build completed successfully!

Current dependencies on/for this PR:

main

PR #1365   👈

This stack of pull requests is managed by Graphite.

Moving this to linera-infra


Added Lunar as adopter

This is a PR to add Lunar to the ADOPTERS.md file upstream. Please comment on the changes.

Nice 🚀  Are these number totals for all environments summed?
You can just create a PR from this branch to the upstream repo.

Nice 🚀 Are these number totals for all environments summed?
You can just create a PR from this branch to the upstream repo.

Numbers are prod only


Spam Domain Submission

Duplicate Domains

[X] Yes, I checked that the domain is not currently in the list
[X] I read the wiki explaining each different categories and examples before submitting

(Required) Spam Comment Direct Link
https://youtube.com/shorts/s2xB2fHEn0k?feature=share
(Optional) Screenshot of comments using the domain

Note - I tried to get the original video (which is still up as a ad) in here. However, as the video is unlisted and I can’t seem to get the ad up again I’m using this react video instead to show proof of the scam domain.
(Required) List of the spam domains
beast-prm.com

We can't really police what people put up on their own channels imo. If they were posting this elsewhere sure but on to their own video is a different matter.
I can still add if ThioJoe feels differently on this though.

I realize that adding this domain will probably do nothing as you said.


Update Nethermind executable name

We renamed the Nethermind executable from Nethermind.Runner to nethermind. This PR updates all references to those.
To be merged once the next version of Nethermind is released.

With the latest release of Nethermind, this PR needs to be merged.

With the latest release of Nethermind, this PR needs to be merged now.

Will do! Thanks for keeping an eye on this for us 🙏


Fix formatting and typo

Code blocks nested in an ordered list need to be indented for the list to keep its current item count. Removing the indentation will reset the list item number back to 1 after each unindented break in the list.

Might want to fix the following typo too
public $channelger;

@oyed Thanks, nice catch.

Thanks!


random.seed

I want to use the function display_data.py, I get the error:
Traceback (most recent call last):
  File "display_data.py", line 75, in <module>
    random.seed(args.seed)
  File "/Users/wangzhikai/.conda/envs/cogdl/lib/python3.7/random.py", line 126, in seed
    super().seed(a)
TypeError: unhashable type: 'list'

Hi @Cloudcatcher888 ,
Thanks for using our cogdl and pointing this out. For display_data.py, it only supports passing one integer to the seed. It seems that the value of seed is a list (default: [1]), which causes this error. We will deal with the inconsistent bug of the code immediately. Please accept my apologies for this mistake.


Passing user defined attributes to Vivado via EDIF

Steps to reproduce the issue
When creating code in migen for use with Vivado, the code is generated with custom attributes and then constraints applied in the XDC output.

Expected behavior
This works in Vivado and it would be nice for it to work when using Yosys as a replacement synthesis tool.
FYI The custom properties that migen uses are the follow;
        # While custom attributes are supported in yosys, neither
        # arachne-pnr nor icetime currently can take advantage of them
        # to add fine-grained timing constraints.
        "mr_ff": None,  # user-defined attribute
        "mr_false_path": None,  # user-defined attribute
        "ars_ff1": None,  # user-defined attribute
        "ars_ff2": None,  # user-defined attribute
        "ars_false_path": None,  # user-defined attribute

Commit 115ca57 adds write_edif -attrprop with this functionality.

Just confirming this seems to work!
hierarchy -top top
# proc; memory; opt; fsm; opt
attrmap -tocase keep -imap keep="true" keep=1 \
    -imap keep="false" keep=0 -remove keep=0
synth_xilinx -top top
write_edif -attrprop top.edif

Vivado is now seeing the custom attributes and the xdc constraints seem to be successfully applied to them!


Fixing minor issues in hub IDP

Purpose

Fixing minor issues in hub IDP

Codecov Report

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

@@           Coverage Diff           @@
##           master      #16   +/-   ##
=======================================
  Coverage   30.47%   30.47%
=======================================
  Files          29       29
  Lines         466      466
  Branches       70       70
=======================================
  Hits          142      142
  Misses        305      305
  Partials       19       19

Continue to review full report at Codecov.

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


Update to meshery-operator v0.5.4

Signed-off-by: Lee Calcote<EMAIL_ADDRESS>Description
This PR fixes #
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

@gr455 @MUzairS15 fyi

@MUzairS15  @gr455 something that one of you can take care of? https://github.com/meshery/meshery/runs/6327341377?check_suite_focus=true#step:5:222


Creating a rule to validate schema name casing.

My goal is to create a rule based on the schema's name casing like if I wanted to check the below to ensure its in CamelCase:
components:
  schemas:
    api-error:
      type: object

I have tried the following but it did not work as intended:
rules:
- name: casing-rule
  object: schemas
  description: reference components should all match regex ^[a-zA-Z0-9\.\-_]+
  pattern:
    property: name
    value: ^[A-Z][a-zA-Z]*$

Is this feature not possible or am I missing something from the documentation.  If I am missing something from the documentation, I would suggest adding this to the documentation for any one else who needs to do this as well.

We have a casing function in Spectral now.
https://stoplight.io/p/docs/gh/stoplightio/spectral/docs/reference/functions.md#casing

Closing this as we are using Spectral now and have not receive any responses related.


German translations of the "Process" section

@5k9m Is it ok to merge or you want to add more commits?
It'd be a better idea to mention @bagder or me in case you wanted to merge!

@inductor to tell you the truth, I am not perfectly sure what the policy on this is. Due to the fact that I can only work on these translations irregularly (mostly weekends), I tend to think that pushing these smaller PRs up here might help others to see the progress and join in when I am not working on it. However, as there is - to my knowledge - nobody else working on the german translation, it's quite pointless work ;)
How would you prefer me to push the next sections? I will try to translate a new section every weekend, as this is when I have time to do so.

When I was translating this into Japanese, I asked to merge once some section had been translated. It doesn't have to be perfect since it's an open source repository is my opinion as long as you have the responsibility for what you've done!
You can even send PRs for little fix(like typo). No pressure. Just tell me whenever you wanna merge so we can do that.

@5k9m

I merged it since the translation in this PR seems to be finished :)

thanks team (and yes @inductor I think you're exactly right, early merge is better than waiting for perfection!), I'm on vacation for the moment so I'm slow to respond here. @5k9m, please also add German to the LANGS.md file to make it also get rendered and become publicly available. (which then will trigger more help/reports from more users...)

please also add German to the LANGS.md file

Done in commit https://github.com/bagder/http3-explained/commit/d241079df2ebf2c333bcd508f51e863ab5416af7

Thanks. That looks correct, but gitbook doesn't seem to have generated anything german anyway! :-1:


Add support for Frozen Flame

https://store.steampowered.com/app/715400/Frozen_Flame/

It's an online game, has EAC, ban risk.

Looks like single player is okay :D


Manually enable cross-compilation on linux_aarch64

As done in https://github.com/conda-forge/gz-sim-feedstock/pull/8 and https://github.com/conda-forge/gz-gui-feedstock/pull/4 .

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender


Difference to revolsys/kong-plugin-upstream-auth-basic?

This is really confusing. Could you expand on when a user (me) wants to use your plugin instead of https://github.com/revolsys/kong-plugin-upstream-auth-basic ?
See also: https://github.com/revolsys/kong-plugin-upstream-auth-basic/issues/3

This plugin takes the username and password from the credentials stored with the consumer.  The revolsys plugin specifies the username and password as a property of the plugin.
So if you want to forward to a backend service which requires a fixed username and password, than the revolsys plugin is better suited.  If your backend service requires basic auth and requires that each caller is identified at the backend, this one would be slightly more suited.

thank you very much!


Typo

https://ice1000.org/2019/08-20-Cutt1.html#20127

The easist square is the constant path for p:
easist : p ≡ p
easist = reflEx _

'Easist' should be 'easiest.'

OP 真可爱，想日


Fix typos in readme

Summary
While I was setting up project locally, I found couple of typos. One of them actually caused an issue while setting up docker(I copied env as it is for host network mode. In that localhost is misspelled as locahost)
Fixes
Depends on
Test plan

Screenshots

Checklist

[ ] My code follows the code style of this project and passes make format.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] My change has adequate unit test coverage.

@src200 Thank you for fixing this. Are there any other recommendations/feedback regarding the README? I know it's a bit messy 😀

One more thing, the getting started video doesn't play(seems like it's just a gif).
But overall, the information is quite understandable!


save images during test to .test_dir/

I noticed the png files in my root directory since they're now saved to the current directory by default, so I made them leverage the existing pytest fixture.

needs rebase from head of #68 post-merge to dev in order to pass the type-checking test.


items-fields are being ignored

Looking into the code it seems that the getItemFields method isn't being called anywhere.

Comparing with getListFields


git compare leaves problem window open

Expected: No linting to happen at all in these windows, OR problems go away when closed.
Steps to reproduce [reproduces on both windows and linux]
Open a project with a git repo
Right click on a file and compare with previous revision

Extensions used Git Lens, vscode-lua, keyring.lua
Related  #32

I've taken a look at what APIs are available to me to detect if a document is a part of a diff window, and have come up short, unfortunately.
When vscode performs a diff, it does so with the showModifications URI scheme on the files, which lets the ext filter them out. Git Lens seems to use the built in diff command in vscode, but this just seems to report to the language server that two files were open with no indication that they're being used in a diff window (other than the fact that both files are in the TEMP directory).
I was somewhat puzzled by this, but confirmed that even the TypeScript language server has this same issue.
As for the problems remaining even after the window is closed, this seems to be because the onClose event is only fired for one of the files in the diff window, while two sets of onOpen and onChange events are fired. Maybe this is a bug in vscode's language client?

Would it be possible if the file is opened inside a temp folder to not lint
at all?  Possibly as something like a workaround option?
Also another related bug. deleting a file that is opened leaves the problem
window open for that file if there was problems in the file.
On Feb 4, 2018 3:22 PM, "Cam"<EMAIL_ADDRESS>wrote:

I've taken a look at what APIs are available to me to detect if a document
is a part of a diff window, and have come up short, unfortunately.
When vscode performs a diff, it does so with the showModifications URI
scheme on the files, which lets the ext filter them out. Git Lens seems to
use the built in diff command in vscode, but this just seems to report to
the language server that two files were open with no indication that
they're being used in a diff window (other than the fact that both files
are in the TEMP directory).
I was somewhat puzzled by this, but confirmed that even the TypeScript
language server has this same issue.
As for the problems remaining even after the window is closed, this seems
to be because the onClose event is only fired for one of the files in the
diff window, while two sets of onOpen and onChange events are fired.
Maybe this is a bug in vscode's language client?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/trixnz/vscode-lua/issues/39#issuecomment-362936428,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANUy4NwZgETvjTyZrCQpLrB93ECYJVm4ks5tRhGjgaJpZM4Rv5Ek
.

We could definitely ignore files in the temp directory as a workaround, as much as I dislike it 😛. As for deleting files, have you tried with version 0.10.1? I couldn't replicate the behaviour.

I will double check tonight.  I think it might be OS specific. I just can't
remember which OS
On Feb 5, 2018 1:18 PM, "Cam"<EMAIL_ADDRESS>wrote:

We could definitely ignore files in the temp directory as a workaround, as
much as I dislike it 😛. As for deleting files, have you tried with
version 0.10.1? I couldn't replicate the behaviour.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/trixnz/vscode-lua/issues/39#issuecomment-363172868,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANUy4A4Y9fpQJub5QIpTb7cFfYcpix_1ks5tR0X-gaJpZM4Rv5Ek
.

For ignoring in temp having a setting to toggle it would be a decent work
around for the workaround for people that don't want the workaround.
On Feb 5, 2018 1:18 PM, "Cam"<EMAIL_ADDRESS>wrote:

We could definitely ignore files in the temp directory as a workaround, as
much as I dislike it 😛. As for deleting files, have you tried with
version 0.10.1? I couldn't replicate the behaviour.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/trixnz/vscode-lua/issues/39#issuecomment-363172868,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANUy4A4Y9fpQJub5QIpTb7cFfYcpix_1ks5tR0X-gaJpZM4Rv5Ek
.

@trixnz I think ignoring files that start with Cache- and are in the Temp folder is a good workaround, even though this should probably reported as a problem upstream? What exactly would you need from them to make this better?


New cop: Style/DataClass

This was inspired by https://rubystyle.guide/#struct-new
But that looks a bit misleading to me. It's obvious that it suggests changing classes with only constructor and attribute accessors to Struct.new, but I'm not sure if it suggests so when class has other members, like this
class Person
  attr_accessor :first_name, :last_name

  def initialize(first_name, last_name)
    @first_name = first_name
    @last_name = last_name
  end

  def some_method
    # ... something
  end
end

into this
Person = Struct.new(:first_name, :last_name) do
  def some_method
    # ... something
  end
end

?
I'm proposing a cop, that suggest to translate dumb classes (only with constructor and accessors), with probably configured min number of accessors to have to get a violation, into Struct.new.
Real-life example of violation: https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/git/blame.rb#L61-69

Interesting suggestion.
I like using Struct, but I'm always frustrated when I do so because of some errors in design that probably can't be addressed.
The main reason I want to use it, is to avoid writing that initialize method. But the initialize method generated has very strict limitations: no default values, no keyword parameters or else it's all keyword parameters, again with no defaults. I also think that the existing of Struct#to_a was a design error. One example is Array(my_struct_instance)... I dislike Struct#members too. Finally, I'm leaning a lot towards immutable structures and prefer attr_reader to attr_accessor. It's not clear in your example if it is intentional that it's attr_accessor.
All that to say: could be useful to some, but definitely would be a Safe: false, Enabled: false cop imo.

All that to say: could be useful to some, but definitely would be a Safe: false, Enabled: false cop imo.

Yeah, it would be useful to me, as I prefer and it is more explicit to me when using Struct.new that this is dumb only data-like class.

Changed my mind regarding this style.


can make responsive the home page

I can make the images responsive
Please assign this issue to me.

I can make the images responsive
Please assign this issue to me.

Hey @jyotisoni24! Please go ahead. I'm assigning this to you.

i want to work upon this issue and make my beginners contribution in hacktoberfest!!

Can I work upon this issue?

please go ahead

can i please work upon this issue??

PLEASE CAN YOU ASSIGN ME I WANNA IMPROVE THESE


proposal: Deno Hunt

See the Discord discussion.

The first version of Deno Hunt was done in #106. Further progress will be tracked in #60.


Bump more dependencies

Tested using
cabal run --enable-tests -c 'lens-family-core ^>=2.1' barrier-data-generator -fexample -fgenerator /usr/share/fonts/truetype/dejavu/DejaVuSans.ttf

@philopon I would appreciate if you had the time to review this!


Fix compilation error by breaking up long line with &s

This fixes Issue #4

This should also fix Issue #6 now


Failing Authorization on one server pair

We have a load-balancer that splits requests between two MS 2008R2 servers.  We can run a renewal on one of the web severs and get the certificate to install, but the other machine fails.  They are the same setup on each server.  Can't understand why it works for one, but not the other.  This is new...it worked in the past without issues.
Here is the log file output for the GOOD request on Machine A:
[DBUG] Config folder: C:\ProgramData\letsencrypt-win-simple\httpsacme-v01.api.letsencrypt.org
[VERB] Settings SettingsService {ConfigPath="C:\ProgramData\letsencrypt-win-simple\httpsacme-v01.api.letsencrypt.org", ClientNames=["win-acme", "letsencrypt-win-simple"], RenewalDays=55, HostsPerPage=50, ScheduledTaskRandomDelay=00:00:00, ScheduledTaskStartBoundary=09:00:00, ScheduledTaskExecutionTimeLimit=02:00:00}
[VERB] .NET Framework >=4.7 detected
[INFO] A Simple ACME Client for Windows (WACS)
[INFO] Software version 1911.1.6713.13067 (RELEASE)
[INFO] IIS version 7.5
[INFO] ACME server https://acme-v01.api.letsencrypt.org/
[INFO] Please report issues at https://github.com/PKISharp/win-acme
[VERB] Verbose mode logging enabled
[DBUG] Renewal period: 55 days
[VERB] Store renewals in registry HKEY_LOCAL_MACHINE\Software\letsencrypt-win-simple\https://acme-v01.api.letsencrypt.org/
N: Create new certificate
M: Create new certificate with advanced options
L: List scheduled renewals
R: Renew scheduled
S: Renew specific
A: Renew all
V: Revoke certificate
C: Cancel scheduled renewal
X: Cancel all scheduled renewals
Q: Quit
Please choose from the menu:
21: Trainos Marlton - trainoswine.com - renew after 2020/4/28 12:49:20 PM
C: Cancel
Which renewal would you like to run?:
[INFO] Renewing certificate for Trainos Marlton - trainoswine.com
[DBUG] Scanning IIS sites
[DBUG] Loading signer from C:\ProgramData\letsencrypt-win-simple\httpsacme-v01.api.letsencrypt.org\Signer
[DBUG] Getting AcmeServerDirectory
[DBUG] Send GET request to https://acme-v01.api.letsencrypt.org/directory
[DBUG] Loading registration from C:\ProgramData\letsencrypt-win-simple\httpsacme-v01.api.letsencrypt.org\Registration
[INFO] Authorize identifier: trainoswine.com
[DBUG] Send POST request to https://acme-v01.api.letsencrypt.org/acme/new-authz
[INFO] Cached authorization result: valid
[INFO] Authorize identifier: www.trainoswine.com
[DBUG] Send POST request to https://acme-v01.api.letsencrypt.org/acme/new-authz
[INFO] Cached authorization result: valid
[DBUG] Certificate folder: C:\ProgramData\letsencrypt-win-simple\httpsacme-v01.api.letsencrypt.org
[DBUG] Certificate store: My
[DBUG] RSAKeyBits: 2048
[INFO] Requesting certificate Trainos Marlton - trainoswine.com 2020/3/6 14:14:41 PM
[DBUG] Send POST request to https://acme-v01.api.letsencrypt.org/acme/new-cert
[INFO] Saving certificate to C:\ProgramData\letsencrypt-win-simple\httpsacme-v01.api.letsencrypt.org
[VERB] Converting private key...
[DBUG] Set private key exportable
[INFO] Installing certificate in the certificate store
[DBUG] Opened certificate store My
[INFO] Adding certificate Trainos Marlton - trainoswine.com 2020/3/6 14:14:41 PM to store My
[VERB] CN=trainoswine.com - CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US (DD598B91F42F0478D4CD103A149441094F77F92F)
[VERB] CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US - CN=DST Root CA X3, O=Digital Signature Trust Co. (E6A3B45B062D509B3382282D196EFE97D5956CCB) to CA store
[VERB] CN=DST Root CA X3, O=Digital Signature Trust Co. - CN=DST Root CA X3, O=Digital Signature Trust Co. (DAC9024F54D8F6DF94935FB1732638CA6AD77C13) to AuthRoot store
[DBUG] Closing certificate stores
[INFO] Installing with IIS...
[INFO] Updating existing https binding :443
[INFO] Committing 1 https binding changes to IIS
[INFO] IIS will serve the new certificates after the Application Pool IdleTimeout has been reached.
[INFO] Uninstalling certificate from the certificate store
[DBUG] Opened certificate store My
[INFO] Removing certificate Trainos Marlton - trainoswine.com 2020/3/4 0:37:56 AM from store My
[DBUG] Closing certificate store
[INFO] Renewal for Trainos Marlton - trainoswine.com succeeded
[INFO] Next renewal scheduled at 2020/4/30 19:14:43 PM
Here is the failed request on Machine B:
[DBUG] Config folder: C:\ProgramData\letsencrypt-win-simple\httpsacme-v01.api.letsencrypt.org
[VERB] Settings SettingsService {ConfigPath="C:\ProgramData\letsencrypt-win-simple\httpsacme-v01.api.letsencrypt.org", ClientNames=["win-acme", "letsencrypt-win-simple"], RenewalDays=55, HostsPerPage=50, ScheduledTaskRandomDelay=00:00:00, ScheduledTaskStartBoundary=09:00:00, ScheduledTaskExecutionTimeLimit=02:00:00}
[VERB] .NET Framework >=4.7 detected
[INFO] A Simple ACME Client for Windows (WACS)
[INFO] Software version 1911.1.6713.13067 (RELEASE)
[INFO] IIS version 7.5
[INFO] ACME server https://acme-v01.api.letsencrypt.org/
[INFO] Please report issues at https://github.com/PKISharp/win-acme
[VERB] Verbose mode logging enabled
[DBUG] Renewal period: 55 days
[VERB] Store renewals in registry HKEY_LOCAL_MACHINE\Software\letsencrypt-win-simple\https://acme-v01.api.letsencrypt.org/
N: Create new certificate
M: Create new certificate with advanced options
L: List scheduled renewals
R: Renew scheduled
S: Renew specific
A: Renew all
V: Revoke certificate
C: Cancel scheduled renewal
X: Cancel all scheduled renewals
Q: Quit
Please choose from the menu:
10: Trainos Marlton - trainoswine.com - renew after 2020/3/19 14:04:10 PM
C: Cancel
Which renewal would you like to run?:
[INFO] Renewing certificate for Trainos Marlton - trainoswine.com
[DBUG] Scanning IIS sites
[DBUG] Loading signer from C:\ProgramData\letsencrypt-win-simple\httpsacme-v01.api.letsencrypt.org\Signer
[DBUG] Getting AcmeServerDirectory
[DBUG] Send GET request to https://acme-v01.api.letsencrypt.org/directory
[DBUG] Loading registration from C:\ProgramData\letsencrypt-win-simple\httpsacme-v01.api.letsencrypt.org\Registration
[INFO] Authorize identifier: trainoswine.com
[DBUG] Send POST request to https://acme-v01.api.letsencrypt.org/acme/new-authz
[INFO] Cached authorization result: valid
[INFO] Authorize identifier: www.trainoswine.com
[DBUG] Send POST request to https://acme-v01.api.letsencrypt.org/acme/new-authz
[INFO] Authorizing www.trainoswine.com using http-01 validation (SelfHosting)
[DBUG] Writing web.config
[INFO] Answer should now be browsable at http://www.trainoswine.com/.well-known/acme-challenge/VIR4uondqp5f4gUDba2uZ0kDO8FFLFo-O57WmmIgs2M
[DBUG] Submitting answer
[DBUG] Send POST request to https://acme-v01.api.letsencrypt.org/acme/chall-v3/3201325803/pPu-1Q
[VERB] SelfHosting plugin serving file /.well-known/acme-challenge/VIR4uondqp5f4gUDba2uZ0kDO8FFLFo-O57WmmIgs2M
[DBUG] Refreshing authorization
[VERB] SelfHosting plugin serving file /.well-known/acme-challenge/VIR4uondqp5f4gUDba2uZ0kDO8FFLFo-O57WmmIgs2M
[DBUG] Send GET request to https://acme-v01.api.letsencrypt.org/acme/authz-v3/3201325803
[DBUG] Refreshing authorization
[DBUG] Send GET request to https://acme-v01.api.letsencrypt.org/acme/authz-v3/3201325803
[DBUG] Refreshing authorization
[DBUG] Send GET request to https://acme-v01.api.letsencrypt.org/acme/authz-v3/3201325803
[DBUG] Refreshing authorization
[DBUG] Send GET request to https://acme-v01.api.letsencrypt.org/acme/authz-v3/3201325803
[EROR] Authorization result: invalid
[DBUG] Deleting web.config
[DBUG] Deleting answer
[EROR] ACME server reported:
[EROR] [type] urn:acme:error:unauthorized
[EROR] [detail] Invalid response from http://www.trainoswine.com/.well-known/acme-challenge/VIR4uondqp5f4gUDba2uZ0kDO8FFLFo-O57WmmIgs2M [<IP_ADDRESS>]: 500
[EROR] [status] 403
[EROR] Renewal for Trainos Marlton - trainoswine.com failed, will retry on next run
Any ideas why Machine B is failing?

there's no way for the load balancer to know which server to send the port 80 request from let's encrypt during validation. I suggest you run the tool on one server and use central ssl store to make the cert available to both servers

@LBegnaud
Thanks for the reply and suggestion.  I did shut down the site on Machine A and the keepalive should send all the traffic to Machine B, but it doesn't look like it's working properly.  There must be  something wrong with the content switch config for that IP routing.
I can't use Central SSL Store since it's 2008R2.  We do have plans to upgrade soon...I guess we'll have to upgrade soon rather than later.

@jimromaine well alternative suggestion would be to use nginx with certbot to offload SSL and that would become your loadbalancer.
I use this for lots of customers with great success: https://github.com/linuxserver/docker-letsencrypt

You could also use DNS validation or host the /.well-known/ folder in a share accessible from both servers and use file system validation.

You can also use a top level URL redirect (on your load balancer) to redirect all /.well-known/acme-challenge/ requests to another server name like acme-auth.yourdomain.com, then have one of the servers in the pool also be the server for that.
Let's Encrypt have started validating from multiple network points, so your challenge response gets hit multiple times, which means sometime the wrong server will answer and the overall validation will fail. If you can pin all /.well-known to one server that solves it. Another solution is just stick cloudflare in front, then you don't really need Let's Encrypt at all (they do the certificate for you).

@LBegnaud Thanks for the suggestion.  I'll look into it when I get a chance.
@webprofusion-chrisc  Thanks for the suggestions.  I actually don't have access to the load-balancer.  It's configured by our datacenter and unfortunately, that are not that responsive.
@WouterTinus The folder IS in a central share and file system validation is the best option for now since both machines see it.  I tried it and it sort of worked.  I was able to see the files created and destroyed in the folder and I was able to see the the challenge response in the browser.  However, I saw this:

It said the preliminary validation failed.  I tried again and it failed again.  However, it then said it was valid and created the cert, but the one sans https binding I have for both http bindings wasn't updated and the old binding stayed.  I was able to manually change the cert on the binding.
Question...do you think that the renewal will change the https binding in the future?  I think I've seen that behavior before.

It said the preliminary validation failed.

Preliminary validation happens from the inside, it's possible that your network design doesn't route from the internal to the external IP. The real validation by Let's Encrypt is the only thing that matters though, preliminary is just a diagnostic.

Question...do you think that the renewal will change the https binding in the future? I think I've seen that behavior before.

It should change, but that said you're using a pretty old software version which might have bugs that have been fixed in more recent releases. It's also slowly reaching its end of life: https://github.com/win-acme/win-acme/issues/1357


Feature/98 integration tests for confluence data reading

Maybe the feedback I have on this is for another issue. It is important to have the data from the Confluence in English. So we should think about testing this additionally.

@amela16 Thanks for the feedback! I think that would be part of the reading confluence data since I only do the integration test. Or do I misunderstood you? I see it too in supabase. Those German texts originated from the example pages in confluence. I thought it should be translated with the deepl_translator .py

For me it feels also a but like am other issue. Its a bit like the step after reading, but very importantly the step before using the readed data. Maybe @SaraElBrak and @tkonheiser could take that into account. @Kadi-7 mentioned in his pull request that there might be some problems with different data structures, like tables. Do you take this in account? That might be related to point 2 of the user story from that Issue.


Only send didChange when the buffer did change

Track the last sent change in a lsp_timestamp option, and only
send didChange (writing the buffer to a tempoary file) if this
does not match the current timestamp.

Thanks for contribution! Now I learned trick with try + echo "fail" =)


Add chat permission and activate chat by default for regions

Motivation

Right now every role can see the chat if it is activated for a region. In the old system the chat was only visible to the "Verwalter" role.
Proposed Solution

Add a new "chat" permission and give it to the "Verwalter" and all IG roles

The chat is already enabled by default:
https://github.com/digitalfabrik/integreat-cms/blob/839ceea71fae49654ab00155100473f41c3a0c56/integreat_cms/cms/models/regions/region.py#L245-L246

I updated the issue.

As we are already touching the chat widget we should also come up with an idea about how we handle the widgets if statistics and chat are disabled. Our current implementation leaves a big blank whole in the middle of the screen.


Release/fix the fix

Fixes a broken "fix" in the last release.

:tada: This PR is included in version 2.2.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat(CategoryTheory/ChosenFiniteProducts): Monoidal functors between categories with chosen products

Introduce a counterpart of Functor.toMonoidalFunctorOfHasFiniteProducts for categories with chosen finite products.

The given definition remains computable since every needed data are in the PreservesLimits and IsLimits instances around. Some of the conv blocks followed by simp/rewrite can be golfed with erw, but that is something to avoid if I understand correctly, so I down the longer but erw-free route.

Note that in the future, PreservesLimit may become a Prop (if someone does the refactor that maintainers would agree with), so that we should lose computability at some point.
In order to develop more API at the same time you get Functor.toMonoidalFunctorOfChosenFiniteProducts, I would suggest developing an API chosenProdComparison similar to the prodComparison in Limits.Preserves.Shapes.BinaryProducts. Under the assumption that F commutes with suitable colimits, we would get a chosenProdComparisonIso. Developing this API (and similarly for the chosen terminal object) should facilitate the proofs in the main definition here.

Right, it should be more elegant that way. Next revision will probably depend on #17691.

[ ] depends on: #17695
[ ] depends on: #17701


Fixed #3453

This pull request contains the following changes for #3453 :

New invoices directly get the state pending.
Admins can change the invoice state as long as the state is not set to paid.
Once the invoice state is set to paid the order status will change to processing.

@ghermans
Thanks for your contribution!
there is also needs to be changed in the Refund Process as refund only takes place when the invoice status is set to Paid, but while checking this PR, Refund comes in pending invoice status. https://prnt.sc/tqbyv7
Also need to fix the below:

able to save the blank value in invoice status https://prnt.sc/tqc5s3
if needed we can only show, shipping title here https://prnt.sc/tqcbfi & same in case of payment.

@vaishaliwebkul your requested changes have been pushed.

The refund button will only be visible if the invoice state is set to paid
The current invoice state is checked when the modal opens.

@jitendra-webkul conflicts have been resolved


UIKitThreadAccessExceptionUIKit while using Forms renderer

When I try to call "MyImage.GetImageAsJPG(100, 100)" in iOS I always end up with the following exception.
I'm sure I call it on the UI thread (even when I use Device.BeginInvokeOnMainThread()  for the call) the exception occurs.
UIKit.UIKitThreadAccessExceptionUIKit Consistency error: you are calling a UIKit method that can only be invoked from the UI thread.
Raw
  at UIKit.UIApplication.EnsureUIThread () [0x00023] in /Users/builder/data/lanes/2377/73229919/source/maccore/src/UIKit/UIApplication.cs:86
  at UIKit.UIImageView.get_Image () [0x00000] in /Users/builder/data/lanes/2377/73229919/source/maccore/src/build/ios/native/UIKit/UIImageView.g.cs:343
  at FFImageLoading.Forms.Touch.CachedImageRenderer+<GetImageAsByte>c__AnonStorey1.<>m__0 () <0x1eaf4790 + 0x0002c> in <filename unknown>:0
  at System.Threading.Tasks.Task`1[TResult].InnerInvoke () [0x00012] in /Users/builder/data/lanes/2377/73229919/source/maccore/_build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/external/referencesource/mscorlib/system/threading/Tasks/Future.cs:686
  at System.Threading.Tasks.Task.Execute () [0x00016] in /Users/builder/data/lanes/2377/73229919/source/maccore/_build/Library/Frameworks/Xamarin.iOS.framework/Versions/git/src/mono/external/referencesource/mscorlib/system/threading/Tasks/Task.cs:2523

Any ideas?

Are you using 2.0.3 which was released about two hours ago? It should be fixed :)

Awesome support! Thank you.
Indeed 2.0.3 fixed the problem.

:+1:


test: ci token permissions

Description:
check permissions of token

was checking permissions of the token, i was under the impression it still had access to upstream repsoitory. I was luckily wrong


Trusted Advisor no longer supports "fH7LL0l7J9" and "aW9HH0l8J6" service checks

When I try to implement the solution with a business support plan, I got the following error:
"[DEBUG]TA checkId could not be refreshed: fH7LL0l7J9 InvalidParameterValueException: Unknown ID: Account requires a Premium Support Plan for access to Trusted Advisor check: fH7LL0l7J9"
Later I found that we are checking for two service checks that are deprecated by AWS. Please remove the above two checks in the code.

Thanks for bringing this up @Naga-Abhilash We have added this to our backlog items for next release.

this is fixed in v5.3.4


fix(jsx-handler-names): properly substitute value into message

Currently the output is ESLint: Prop key for handleChange must begin with '{{handlerPropPrefix}'(react/jsx-handler-names)

Yup, looking into that right now :)

@ljharb have added a test - also did a basic rg search on the codebase for any other instances of this, and didn't find any.

Codecov Report

Merging #2975 (cad79bb) into master (495a4cf) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2975   +/-   ##
=======================================
  Coverage   97.60%   97.60%
=======================================
  Files         110      110
  Lines        7266     7266
  Branches     2650     2650
=======================================
  Hits         7092     7092
  Misses        174      174

Impacted Files
Coverage Δ

lib/rules/jsx-handler-names.js
100.00% <ø> (ø)

Continue to review full report at Codecov.

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


[DO NOT MERGE] Testing ephemeral environment

Summary
Draft PR just to test out a previous state of the repo in the ephemeral environment (which is currently failing to deploy).

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against 2c0061968ffdf3b7466752d067113f708733603e


[Certif] required OS tests

Since the "official" OS is Mac OS Lion ( :sweat: ) if we stay at QT4, we need to test the application on Lion.
It would be extremely complicated to certify an application based on a main SOUP which is not updated/followed on an other OS version. However, we have never tested MUSIC/inHeart on Lion. So... let's hope that the application works on it... :sweat_smile:

can we go into the details of this? I agree that one cannot install Qt4 to compile MUSIC on recent OSX, but this does not mean that an application compiled with Qt4 cannot run on it?
if the tests are run on a recent OSX and they go fine, what is the problem?

In fact, we can perhaps run a binary compiled on Lion with Qt4 on a recent Mac, but for now we don't compile on Lion, so we don't know if MUSIC compiles on it. And if we/i understood properly Cyrille and David, we should test the binary on the certified OS (which is the same as the OS used to compile the binary). After these tests on the certified OS, we can run tests on recent OS too.

we should test the binary on the certified OS (which is the same as the OS used to compile the binary)

this is what I question. I feel we could say that the certified OS is a recent OS where we run all the tests , independently of the compilation OS. If you sell software, the compilation OS is not necessarily the run OS.

I think it's not a compilation problem but a runtime one. QT specifies that its platform is not tested on newer OS's, so even if you compile on Lion, running it on El Capitan (for example) means you are using the library in an environment it is not supported for. Nothing guarantees that a future OS is compatible with the library.
If we could avoid this problem altogether I'm all for it, but I fear it's not the case.

Indeed. So, i think we need to select a mac on Lion. Do you have a ready computer on Lion in Sophia? If needed we have a computer on Lion ( @fcollot : "chewbacca") in LIRYC but it's not "our" computer: it's a shared one in a MRI console.

No Lion here in Sophia.

El Capitan has been chosen, i close


Logout btn is not in line with the rest of the menu

When I installed Yii2 with composer"
composer create-project yiisoft/yii2-app-basic basic 2.0.7
and I'm viewing the page
http://localhost/web/site/login and enter admin/admin
the next page, the redirected page (home), has the logout not in line with the others links from the menu.

Q
A

Yii version
2.0.7

PHP version
5.5.9

Operating system
Ubuntu 14.04

Moved to yii2-app-basic repo. Thank you


Add a check of the hash of aem.js as part of the git PR workflow?

Consider this an idea more than concrete proposal
I've run across a number of ACS and partner projects who are modifying aem.js as their default way of changing things, as opposed to doing it in scripts.js. I view modifying aem.js as not necessarily verboten, but to be avoided when possible.
But my thought would be to have the PR workflow check the hash against a known value, and if it doesn't match, print a message indicating to use caution when modifying, etc.
If the project really wants to or needs to, they can update the hash in the pr script and move on, but should at least encourage the right behavior.  thoughts?

If the project really wants to or needs to, they can update the hash in the pr script and move on, but should at least encourage the right behavior. thoughts?
It can also be more of a warning that can be overridden similar to PSI check today.


Configuring/building from git cloned repo does not produce an ollama executable.

Following the instructions in README.md file
go generate ./...
go build .
does not seem to end with an ollama executable code in the folder.
I am missing something? How does one build it and then install it?
From "go build ." I get the stuff below.


Should validate the filterOrder.After cannot be envoy.filters.http.router

Description:

Describe the issue.

Based on: https://github.com/envoyproxy/gateway/blob/main/internal/xds/translator/httpfilters.go#L214, should we validate the filter shouldnt be envoy.filters.http.router ?
cc @zhaohuabing
[optional Relevant Links:]

Any extra documentation required to understand the issue.

@Xunzhuo Good catch! I think we'd better validate at the API level to avoid misconfiguation. Router is a terminate filter and should always be the last one in the filter chain.

@Xunzhuo We already got validation here https://github.com/envoyproxy/gateway/blob/c78f427eb58228da66d64b225a91a2aa3b59515c/api/v1alpha1/envoyproxy_types.go#L156

This validation is weird, cannot we insert filter before router?

Yes, but you should be able to achieve the same with After key word.

Thanks, let`s close this one


disable propagation of PY_LIMITED_API to dependent targets

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

#232

I'm not too sure if removing this file would break things:
  cp -v ./tests/pysidetest/testbinding.abi3.so ${SP_DIR}

are you able to use the limited ABI in your package? it seems that more and more packages are moving in that direction. May I ask if there is 1 particular function that needs it or is it more wide spread?

are you able to use the limited ABI in your package?

not yet. Also I don't think the transition will happen for the next release.

May I ask if there is 1 particular function that needs it or is it more wide spread?

From looking at the build-errors it seems like it's used in more than one place.
I am wondering why the LIMITED_API is propragated to downstream packages? Is there any reason for this?

this addition changes in ${PREFIX}/lib/cmake/Shiboken6/Shiboken6Targets.cmake
this:
set_target_properties(Shiboken6::libshiboken PROPERTIES
  INTERFACE_COMPILE_DEFINITIONS "Py_LIMITED_API=0x03060000;NDEBUG"
  INTERFACE_INCLUDE_DIRECTORIES "${_IMPORT_PREFIX}/include/shiboken6"
)

to
set_target_properties(Shiboken6::libshiboken PROPERTIES
  INTERFACE_COMPILE_DEFINITIONS "NDEBUG"
  INTERFACE_INCLUDE_DIRECTORIES "${_IMPORT_PREFIX}/include/shiboken6"
)

In my mind Pyside6/Shiboken6 should not propagate the PY_LIMITED_API to downstram packages. At least it makes no sense for me.

it may be appropriate for us to patch that out and simultaneously issue a bug report upstream.

ps it may have been due to https://bugreports.qt.io/browse/PYSIDE-1775?jql=text+~+"PY_LIMITED_API"
i think it would be good if you could open an issue upstream, and we can "track it" even if for years to come...

done: https://bugreports.qt.io/browse/PYSIDE-2822

lets not patch, instead set FORCE_LIMITED_API can be set to OFF

see #241


Player/Device Volume Enhancement

Is your feature request related to a problem? Please describe.
Trying to use custom “slider” controls that update the volume in real time as you move your mouse controls the device volume correctly but spams the server with unneeded volume update requests.
Describe the solution you'd like
Ideally, there would be a simple way to control both the device volume and notify Spotify of the volume change separately (for instance, on a mouse up event).
Describe alternatives you've considered
I’ve attempted to use reflection to access the fields manually so that I can set the device volume myself and update the server after, but my quick and dirty tests didn’t seem to work well.  I could probably do it with enough effort but I’m not horribly familiar with the internal workings of the code yet.
Additional context
I’m using an instance of the Player class to do the majority of the work here which seems to work well, but doesn’t give me the fine tuned control (unless I’m missing it?) that I need.  The end goal is to let the user use a slider to change the volume in real time and then update the server after the user decides on the right volume (like I said, a mouse up event).
If I’m not clear, I can try to elaborate a bit more.

I guess it could make sense to have the client send the update to the server once the user has finished dragging the slider around and reflect the change only locally while it's dragging.
I'll play around with it to see how it behaves.

@MorningSage The volume update is now sent to the server after 500ms of the last volume change so that if the volume keeps changing it is reflected only locally.

That's perfect!
Thanks I think that will fix the issue I was experiencing.

This might be a bit late/unhelpful, but it may be worth adding a flag at either compile/runtime for this such as --buffer-events as iirc delays in UI updates of less than 100ms are generally not perceived, whereas updates that take longer than that can be noticeable and impact overall UX.

@sashahilton00 I tried playing around with the delay a bit, but at 200ms the updates were already going straight to the server because apparently the client is already spacing them auto a little bit. Secondly, this doesn't not affect the UX on the client you are changing the volume on because the slider stays in the position you moved it to and receives the update before it tries to go back to the original position. I guess you'd see the update delay if you were watching another client than the one you are using to change the volume.


chore(main): release 5.7.0

:robot: I have created a release beep boop
5.7.0 (2023-12-13)
Features

Add new /history command to show previously played tracks (bf461c2)
Add new /move command to move a track to specified position (100325b)
Add new config option to enable/disable button labels (47d3c36)
Added /back command to go back in history (e11df37)
Updated /remove command with options for range, queue, user and duplicates! (27d4c6c)

Minor changes and bug fixes

Add check on startup to see if ffmpeg is available (0b72e92)
Add new action buttons also to /history command (fac39e4)
await client.login, thanks to @Kriblin (64a709b)
change addNumberOption to addIntegerOption (6ca7ce3)
Small changes to new action buttons (981be70)
solve bug using getNumber after changing to addIntegerOption (4b630e2)
update default config value for button labels to true (ee54513)

This PR was generated with Release Please. See documentation.

let's gooo! ✨🚀

:robot: Release is at https://github.com/mariusbegby/cadence-discord-bot/releases/tag/v5.7.0 :sunflower:


tf.keras.backend.in_train_phase / tf.keras.backend.in_test_phase not documented

Tensorflow 2.4.1
tf.keras.backend.in_train_phase / tf.keras.backend.in_test_phase not documented.
Reference tf 2.4.1 docs here on the tf.keras.backend lib.  You will see neither function appears.
https://www.tensorflow.org/api_docs/python/tf/keras/backend

Docs are not generated intentionally for some of the tf.keras.backend functions.
See commit a37bf6c
tf.keras.backend.in_train_phase
tf.keras.backend.in_test_phase

@ymodak There is not documentation for differing behavior between test/train time despite the flag learning_phase() being provided and documented.

Tensorflow has documented only those backend functions listed at https://keras.io/api/utils/backend_utils/, rest all are undocumented.
However, you see see all the hidden functionalities with the code in the github here.
Closing this issue, feel free to reopen if you need further clarification. Thanks!


Relative paths resolving to unit test, not the schema

When using Laravel's packages we have JSON Schemas in multiple directories. Each one can be referenced and we're hoping to use it with relative paths. This works fine in Laravel with the validation on form request, it uses the relative path to the .schema.json
However with this package the relative path is of the unit test.

Yes, there is a bug in the UriResolver::combineRelativePathWithBasePath - I've written a test:
use JsonSchema\Uri\UriResolver;
use PHPUnit\Framework\Constraint\IsEqual;
use PHPUnit\Framework\TestCase;

class UriResolverTest extends TestCase {

  public function testcombineRelativePathWithBasePath(): void {
    $base = '/var/packages/flow-api/tests/UnitTests/DemoData/../../../schema/Customer/CustomerSchema_latest.json';
    $relative = '../../../schema/UuidSchema.json';
    $combined = UriResolver::combineRelativePathWithBasePath($relative, $base);
    $expectedPath =
      '/var/packages/flow-api/tests/UnitTests/DemoData/../../../schema/Customer/../../../schema/UuidSchema.json';
    $expectedRealPath = realpath($expectedPath);
    self::assertThat(
      $combined,
      self::logicalOr(
        new IsEqual($expectedPath),
        new IsEqual($expectedRealPath)
      )
    );
  }
}

Failed asserting that '/var/packages/flow-api/tests/UnitTests/DemoData/../../schema/UuidSchema.json' is equal to '/var/packages/flow-api/tests/UnitTests/DemoData/../../../schema/Customer/../../../schema/UuidSchema.json' or is equal to '/var/packages/schema/UuidSchema.json'.

I've yet to understand, why the Method combineRelativePathWithBasePath is so complicated. Can't you simply use a dirname($basePath) . "/$relativePath" ?

Yes, there is a bug in the UriResolver::combineRelativePathWithBasePath - I've written a test:
use JsonSchema\Uri\UriResolver;
use PHPUnit\Framework\Constraint\IsEqual;
use PHPUnit\Framework\TestCase;

class UriResolverTest extends TestCase {

  public function testcombineRelativePathWithBasePath(): void {
    $base = '/var/packages/flow-api/tests/UnitTests/DemoData/../../../schema/Customer/CustomerSchema_latest.json';
    $relative = '../../../schema/UuidSchema.json';
    $combined = UriResolver::combineRelativePathWithBasePath($relative, $base);
    $expectedPath =
      '/var/packages/flow-api/tests/UnitTests/DemoData/../../../schema/Customer/../../../schema/UuidSchema.json';
    $expectedRealPath = realpath($expectedPath);
    self::assertThat(
      $combined,
      self::logicalOr(
        new IsEqual($expectedPath),
        new IsEqual($expectedRealPath)
      )
    );
  }
}

Failed asserting that '/var/packages/flow-api/tests/UnitTests/DemoData/../../schema/UuidSchema.json' is equal to '/var/packages/flow-api/tests/UnitTests/DemoData/../../../schema/Customer/../../../schema/UuidSchema.json' or is equal to '/var/packages/schema/UuidSchema.json'.

I've yet to understand, why the Method combineRelativePathWithBasePath is so complicated. Can't you simply use a dirname($basePath) . "/$relativePath" ?

We've been using my fork in production for nearly 2 years now. This is a bug and without the fix our tests fail.
The dirname is just a string operation, it is not limited to file paths and also works for URLs. It doesn't work on the file system.


Controller container image not resolved

Hello,
I'm testing this out on OpenShift, and noticed that it is failing to pull the controller container image.
I had a look in the Deployment and noticed it specifies
          image: 'controller:latest'

Which is very vague. At a minimum it should be <project>/<image-name>:<tag>, and even better would be including the registry name as well docker.io/<project>/<image-name>:tag.
Where is the controller image hosted?
Cheers,
Alex

I've built and pushed it to quay.io incase anyone needs it
https://quay.io/repository/ahussey/freeipa-issuer-controller?tab=tags

Closing in favour of using the native ACME integration


Cargo intercepts --version flags in third party subcommands

If a third party subcommand registers a --version flag and uses the execute_main_without_stdin infrastructure, the cargo crate will intercept --version and print its own version, rather than passing it through to to the subcommand main.

Should be a relatively easy fix

The issue should be closed since it was fixed in #2336.


Maintain item order when joining ebaySearchResults

Currently we prepend each ebaypage (limit=200) to the result which flips the order of the pages

What we currently get is: (pseudo)
/api/search?s=example&size=590&page=2

{ items: [ [591,...,600], [801,...,1000], [601,...,800], [1001,...,1180] ] }


Fixed notation of ng-doc version

The ng-doc version resolver crashed while installing the packages. For some unknown reason it threw to 17.+ instead of the expected 16.X.X.

Thanks, merged


Ability in error handler to re-trigger the selection after showing a popup

As suggested I'm attaching to .on('error') to show a popup telling the user to hit Ctrl+C if execCommand fails for some reason. However the library that I'm using appears to do something which clears the selection when I show the popup. In other words, if i do a console.log within the error I can hit ctrl-c and get the text copied correctly, however if I show a html-popup it looses the selection and so Ctrl-C doesn't copy anything (I'm using the text: api to specify custom text)
I would suggest a workaround would be to extend the event object that is passed in to have a new bound function (like clearSelection) which is something like redoSelection() so I can trigger the popup to show and then redo the selection after the event (without it attempting a second copy and then success/error trigger).

Hey @mzealey, this is a very specific use case, I would suggest you implement your own clipboard implementation, but thanks for your suggestion :)


Revert "(maint) Optimize adding tags"

This reverts commit 0412515e2f9d75f00687bc5c01915da5a51c58e3.
This change to tag filtering meant that a single tag like foo::bar
would be split on the :: seperator and expaned into:
['foo::bar', 'foo', 'bar']. This meant that an agent would sync more
resources than the used intended when tag filtering is in effect.
In order to fix this problem, revert the commit that initially made
this change to filtering behavior.

@kylog @hlindberg This seems to fix the problem, but I'm not sure of any other potential repercussions of reverting this change.

Yeah, but is that what we want to do (revert?) - If I understand the issue correctly it is the search that is wrong because the change ended up splitting what the user searched for (which it did not use to do).

If I'm following along correctly, what happened with 0412515e was that Puppet::Util::Tagging#handle_qualified_tags was factored out of existence, rendering the override supplied at https://github.com/puppetlabs/puppet/blob/3.x/lib/puppet/transaction.rb#L353-L358 as orphaned code (later removed in 8848171b).
The behavior before that was that there was different behavior on the compile side and the application side, thanks to transaction.rb overriding what handle_qualified_tags does.
If that's correct, I think this would work in 3.x, but would not work if we merged up to stable (because stable no longer has handle_qualified_tags in transaction.rb. Put another way, we'd want to revert 8848171b when this was merged up to stable.
If that all makes sense to everybody, my question would be whether we are losing any performance advantage that 0412515e2f may have introduced. The comment says "overall savings" but doesn't go into details.
Is there something we could benchmark that would shed light on that question?

the revert will have performance impact

the fix is really simple - add a method that answers if a tag should be split, override it in transaction.rb and make the splitting conditional - that adds one call per tag which is reasonable

the revert will have performance impact

Gotcha, but can we quantify / mitigate?

So I think you're saying that the overall savings came from avoiding building up this intermediate qualified array, and we could bypass that by just adding the method you're describing.

Performance was gained by not doing redundant work (searching with include, and then splitting) mostly by using a Set containing all tags (uniqueness guaranteed faster than checking with include).

Closing this in favor of a PR that makes the needed changes without reverting the entire commit :+1:

Adding a comment with PUP-4495 so it's easy to find in when searching PR's :+1:


Adding contributors to the README

Description
This issue involves updating the README.md file of the project to include a section for contributors. The purpose of this section is to acknowledge and credit individuals who have contributed to the project.
Steps to Implement

Open the README.md file for editing.
Create a new section titled "Contributors" or "Acknowledgements" at an appropriate location in the README.
List the names or usernames of the contributors, along with any other relevant information or acknowledgements, such as their contributions or roles.
If desired, provide links to their profiles or websites.
Update the README to reflect the changes made.

Expected Outcome
After implementing these changes, the README will include a dedicated section to acknowledge and credit the contributors who have contributed to the project. This will recognize their efforts and provide visibility to their contributions, fostering a sense of community and collaboration.
Screenshots
No response
🥦 Browser
Google Chrome
Checklist ✅

[X] I checked and didn't find similar issue
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (blank for no)

hey can I add all contributors in readme file

Hey @mkswagger , great idea but we won't be doing this as with 100+ contributors it would take a lot of space. And contributors would always be seen in the contributor's section.
Thanks for your thoughts, appreciate it ⚡

Got it !1 Thanks @tamalCodes


fix: allow to be lazy loaded on InsertEnter

fixes #229

Add a small comment explaining why we need to make that check

Actually it's clear enough as is

Oops, I just added the comment, the reason we miss the InsertEnter event is because we check if the binary is installed first. lmk if you want me to push the comment or if it's fine as is

Yeah feel free to push it on main


[WIP]feat: ddb refactor to TS, use cdk, eliminate EJS, overrides hook , centralized state management

Pending: unit tests, e2e tests, migration tests
High-level overview of the flow and refactor:

Video of this working and the flow:
https://user-images.githubusercontent.com/7247658/135663224-1ad65c14-e860-4536-a541-b162f3615ef2.mov

Codecov Report

Merging #8325 (be733a8) into extOverrides (ee1c49e) will decrease coverage by 0.00%.
The diff coverage is 80.00%.

@@               Coverage Diff                @@
##           extOverrides    #8325      +/-   ##
================================================
- Coverage         55.57%   55.57%   -0.01%
================================================
  Files               706      706
  Lines             38996    38998       +2
  Branches           7865     7865
================================================
+ Hits              21671    21672       +1
- Misses            16535    16536       +1
  Partials            790      790

Impacted Files
Coverage Δ

...amplify-cli-core/src/feature-flags/featureFlags.ts
83.70% <ø> (ø)

.../amplify-cli-core/src/state-manager/pathManager.ts
69.81% <50.00%> (-0.39%)
:arrow_down:

...ider-utils/awscloudformation/cfn-template-utils.ts
92.00% <100.00%> (ø)

packages/amplify-cli-core/src/cliConstants.ts
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Jupyter server should start automatically as jupyter does when opening a notebook

Opening a notebook and seeing this, I'm immediately wondering why it doesn't start.

Could we perhaps:

Have a button to start?
Have it auto start? (Maybe backed by a switch)

Both Jupyter Lab and Jupyter notebook auto start (well since the app itself is the server)

I like the idea, however it should be fine only when we know it'll work, e.g. if a user has prescribed a interpreter for Jupyter. This way we can start it silently in the background.
I.e. one wouldn't want prompts and messages displayed indicating Jupyter cannot be found or the like when opening a nb.

Will also improve perf in running a cell.

Propose closing in favor of more general #7232, but want to make sure that I'm not missing a difference. So no costing yet.

Probably after #8623 (to avoid re-work due to changes from #8623)

@rchiodo I agree with @IanMatthewHuff Closing this in favor of #7232


Do you have any plan to release pre-trained model ?

Hi, thanks for this great work. I wonder if you have any plans to release pre-trained models? I found some models in download_models.sh, but it seems that the model doesn't fit ( a lot of missing and extra keys)

Thank you for your attention. We have posted the weights on Kitti

Thank you for your attention. We have posted the weights on Kitti

------------------ Original ------------------
From: @.>;
Date:  Tue, Oct 17, 2023 05:14 AM
To: @.>;
Cc: @.***>;
Subject:  [HanLingsgjk/TPCV] Do you have any plan to release pre-trained model ?  (Issue #1)

Hi, thanks for this great work. I wonder if you have any plans to release pre-trained models? I found some models in download_models.sh, but it seems that the model doesn't fit ( a lot of missing and extra keys)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Event for starring/unstarring a message gets dropped

Repro:

Open the app. Then open a view of the same messages in another tab, or in the mobile app.
In that other client, star and unstar some of the messages.
Observe the messages don't get updated -- no stars appear or disappear.
Reload the tab; now the starred/unstarred state updates appropriately.

The cause seems to be a type error; server_events_dispatch.js has this call:
                ui.update_starred(message_id, new_value);

but the actual definition in ui.js starts like this:
exports.update_starred = function (message) {

and those names are accurate -- the implementation expects a message object and consults message.starred, but this caller is just passing a numeric message ID followed by a boolean for whether the message should now be starred or unstarred.
Found this while reviewing @jackrzhang 's zulip/zulip-mobile#2843 , which will add an implementation of this path to the mobile app.

@zulipbot claim


Are zlib development support files really required?

In e7c47565323ddcc08355fa1aa62432a9881ca706, you check whether zlib.h is present while no native code inside ext/ includes this header.
This for instance requires package zlib1g-dev to be installed on Debian (likely Ubuntu as well) while it seems only zlib1g (the actual library) is needed.

@gpakosz Unfortunately, the compilation of libxml2 does require zlib.h to be present:
libxml2 $ ack --type=cc zlib| fgrep include
nanohttp.c:68:#include <zlib.h>
tree.c:25:#include <zlib.h>
parserInternals.c:36:#include <zlib.h>
xlink.c:32:#include <zlib.h>
include/libxml/tree.h:563:    int             compression;/* level of zlib compression */
os400/wrappers.c:114:#include <zlib.h>
os400/wrappers.h:48:#include <zlib.h>
HTMLparser.c:30:#include <zlib.h>
xmlIO.c:36:#include <zlib.h>
xmlIO.c:1343:#include "xzlib.h"
xzlib.c:35:#include <zlib.h>
xzlib.c:41:#include "xzlib.h"
parser.c:81:#include <zlib.h>

This, of course, depends on whether you're compiling libxml2/lbxslt from source, but we only check for this header when --use-system-libraries is not enabled.
Can you help me understand exactly what you're doing when you see the zlib.h check fail? What are your arguments to gem install, what flavor of system are you on?

I commented on the PR at #1314. I'm still not convinced that what you're suggesting is suitable to be merged, since without zlib.h on the system, libxml2 will be compiled without zlib support.
Happy to discuss more here, if you like.

Going to close this. Again, I'm happy to have a conversation about this, if you like.


Chore: add cloud banner to website

Closes https://github.com/firezone/marketing/issues/167

Pull Request Test Coverage Report for Build e557e56096c603fa6b77d18cff0a5b46ca664a16-PR-1473

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 66.521%

Totals

Change from base Build 467d6c309528806766293b571f0507c48dc73ae5:
0.0%

Covered Lines:
1675

Relevant Lines:
2518

💛  - Coveralls


Fix queries against compacted files

Required for all non-trivial PRs

[x] Rebased/mergable
[x] Tests pass
[x] CHANGELOG.md updated

This fixes #5501 and #6925 so that running queries against files that are also being compacted does not cause the query to end abruptly.  This usually looks like large chunks of data just disappearing and then re-appearing the next time the query runs.  In grafana, a graph could look like the third image in #6925.  Queries should now be consistent as of the time they are executed with respect data on disk regardless if files are compacted.
To fix this, this PR uses a reference counting approach where queries register their usage of a TSM file and remove that reference when finished.  In the FileStore, if a TSM file is replaced, but is still in use, it is moved aside to allow the query to complete and then periodically the file is checked to see if it can be removed.  The new files being installed will be use by any future queries after Replace returns.
In order to not complicate or block compactions, the existing file is renamed to a temp file and the live file is removed.  The TSMReader then re-MMAPs this new file, using it's existing index and tombstone state.  This approach performs well in local testing and should also work on windows.  In the event of a crash, the moved aside files are cleaned up as part of startup like other temp files managed by the engine.
Fixes #5501
Fixes #6925
cc @benbjohnson

I think this is OK. I have one question since the code is complicated and I found two grammatical errors in the comments, but I think it's good otherwise.