Feature level

This implements everything discussed in #341

The “Enable advanced features” item has been removed from the Command preferences
Proxy Objects are enabled by default
“Pull selection from front application instead of Finder” is enabled by default
All code that was conditional based on feature level has been made unconditional

That last one demands some elaboration. As a general rule, I searched the entire codebase for these strings and removed references to them.

kItemFeatureLevel
kFeatureLevel
kCuttingEdgeFeatures
betaLevel
alphaLevel
devLevel
isRestricted
fDEV
fALPHA
fBETA
fSPECIAL
meetsFeature

In some cases, this meant removing the if clause, making the code run all the time. In a few cases, it meant changing the condition to an #ifdef DEBUG instead. Please look them over.
Most of this stuff is well tested at this point, as it would have been active for any user with advanced features enabled. The notable exceptions are enableEntry and disableEntry in QSFileSystemObjectSource.m. The (now removed) first line of these methods effectively prevented them from ever being called. Now that they’re active, they still have a limited scope. As you can see, they only affect catalog entries that have “watchTarget” or “watchPaths” set. There are a couple of presets that have this (like ~, /Applications/, etc.) but that’s it. From some limited testing, the QSVoyeur stuff seems to work. Objects are immediately added and removed from the catalog as the filesystem is changed (which is pretty cool), so I’m going ahead with this pull request.
One final thing: The changes to the XIBs in 91224bcc were done with a text editor. I’m mostly lost in Interface Builder and could not find the references to alphaLevel anywhere. I haven’t experienced any problems with the change.

So as you can see, this now has a merge conflict. Anyone know if I can clean this branch up so it’ll go away?
I tried rebasing the branch from master, fixing the conflict, redoing the small change to the XIB, and pushing, but it doesn’t like that.
To git@github.com:skurfer/Quicksilver.git
 ! [rejected]        featureLevel -> featureLevel (non-fast-forward)
error: failed to push some refs to 'git@github.com:skurfer/Quicksilver.git'
To prevent you from losing history, non-fast-forward updates were rejected
Merge the remote changes (e.g. 'git pull') before pushing again.  See the
'Note about fast-forwards' section of 'git push --help' for details.

Should I cancel this request, delete the branch (on GitHub) and then push my modified local copy and make a new pull request? Or can this one just be updated somehow?

Non fast-forward error means you're trying to remove a more recent commit
from your branch. You can get past this error by using the git push -f flag
(f for force)
If it's easier with you, I'm happy for you to go ahead and issue a new pull
request, referencing the old one.
P.S. bloody quick with the triggers merge! :o
P.P.S. I'm working on crash protection as we speak. I think I have it sorted
now :)
On 24 October 2011 20:52, Rob McBroom <
<EMAIL_ADDRESS>
So as you can see, this now has a merge conflict. Anyone know if I can
clean this branch up so itll go away?
I tried rebasing the branch from master, fixing the conflict, redoing the
small change to the XIB, and pushing, but it doesnt like that.
To git@github.com:skurfer/Quicksilver.git
! [rejected]        featureLevel -> featureLevel (non-fast-forward)
error: failed to push some refs to<EMAIL_ADDRESS>skurfer/Quicksilver.git'
To prevent you from losing history, non-fast-forward updates were
rejected
Merge the remote changes (e.g. 'git pull') before pushing again.  See
the
'Note about fast-forwards' section of 'git push --help' for details.
Should I cancel this request, delete the branch (on GitHub) and then push
my modified local copy and make a new pull request? Or can this one just be
updated somehow?
--
Reply to this email directly or view it on GitHub:
https://github.com/quicksilver/Quicksilver/pull/479#issuecomment-2508498

P.P.S. I'm working on crash protection as we speak. I think I have it sorted now :)

I hope you aren’t adding to the (now merged) failedPluginLoad branch. :)

OK, git push -f seems to have worked and the proper commits are still showing above.

I hope you aren’t adding to the (now merged) failedPluginLoad branch. :)

Uuuuum... maybe :o
I've incorporated the failedPluginLoad branch into my new fixes. Basically QS now has a single .plist pref for  if it crashed or not. It then determines if it was because of a plugin or some other reason.
Hopefully I'll be able to re-push to the closed pull request?! :/

My guess is that you can open a new pull request from the same branch and it’ll just include commits that aren’t already in master. Sorry to be so quick. :)

Sorry to be so quick. :)

Don't be sorry - it's awesome! :D
On 24 October 2011 21:51, Rob McBroom <
<EMAIL_ADDRESS>
My guess is that you can open a new pull request from the same branch and
itll just include commits that arent already in master. Sorry to be so
quick. :)
--
Reply to this email directly or view it on GitHub:
https://github.com/quicksilver/Quicksilver/pull/479#issuecomment-2509252

I haven't started looking over the code properly yet, but what is the case with plugins here?
Previously, the list of plugins would vary depending on the app level e.g. 'pre' would show all the beta plugins.
Now, will we just be showing everything to everyone?

Now, will we just be showing everything to everyone?

Feature level no longer does anything, so yeah.

OK. In that case the plugins repo needs modifying to ignore the PRE/DEV level (that will no longer be given by QS) and to remove all the details of this in the database etc.
@tiennou - could you help with that?

I was wondering if we should put an #ifdef DEBUG in QSPaths.h so we could point to a different set of paths when testing the server-side. And now that you bring up the above, we could also use the alternate location to put up plug-ins that aren’t ready for release. (Although, I’m not sure we really need an easy in-app distribution method for these. If you’re testing such a plug-in, you’ll probably be building it from source anyway.)

If youre testing such a plug-in, youll probably be building it from
source anyway

Yeah, I'd say we wouldn't need to bother with this.
It may be worth coming up with another path now for testing purposes :)
On 25 October 2011 18:55, Rob McBroom <
<EMAIL_ADDRESS>
I was wondering if we should put an #ifdef DEBUG in QSPaths.h so we
could point to a different set of paths when testing the server-side. And
now that you bring up the above, we could also use the alternate location to
put up plug-ins that arent ready for release. (Although, Im not sure we
really need an easy in-app distribution method for these. If youre testing
such a plug-in, youll probably be building it from source anyway.)
--
Reply to this email directly or view it on GitHub:
https://github.com/quicksilver/Quicksilver/pull/479#issuecomment-2520445

I have set up a test plugins system which is just an exact copy of the current system at:
http://qs0.qsapp.com/test (as opposed to the now http://qs0.qsapp.com/plugins )
I'm not sure how much it will break (I think I got everything right...) so it's probably worth testing.
I'm off to bed :)

Dammit we really should have looked at this before doing all the plugins system stuff. Then we won't have needed to code all the PRE/DEV stuff into it.
I've made changes to qs0/test/ so it should work with this build now.
A few comments:

I still see release type stuff in the 'extras' preference pane

...OK just done a search for @"PRE" and I see it still exists.
Let me get this straight: have your changes JUST changed things to do with "advanced features" and have nothing to do with the 'final release' 'pre release' and 'developer release' settings?
If so - that's great! We don't need to change anything :D
...OK now this is REALLY confusing me... are feature level and application update level completely different things?
I've had a quick look through the code and it seems like this affects:
a) plugin & action loading (plugins can set the level for actions)
b) Proxies
c) a bit of catalog stuff you've mentioned

By 'I edited the .xibs by hand in a text editor' I'm wondering: how the hell did you know what to remove?!
Comparing the extras pref pane for ß61 and this branch, I see no differences. What exactly did you change in 91224bc ?
Seems good to me atm
I'm getting all the plugins showing which is correct, and it turns out the QS filters the plugins itself as opposed to stuff happening server side, so nothing needs to be changed with the plugins system (esp. as application update type is sticking around by the looks of things)

P.S. as for the QSVoyer stuff, we need to start using that ;-)
Any ideas what the overheads would be if we added an option: rescan catalog: when files are changed, every 10 minutes, every 30 minutes... So QS used QSVoyer on every folder?

P.S. as for the QSVoyer stuff, we need to start using that ;-)
Any ideas what the overheads would be if we added an option: rescan
catalog: when files are changed, every 10 minutes, every 30 minutes...
So QS used QSVoyer on every folder?

I didn't even know that existed. But if it works and isn't too much overhead, I think there shouldn't be any rescan interval for folders/files. Instead "when files are changed" should always be used.
But this kind of seems off-topic for this pull request. :-P

Installing QS from scratch looks good. I see proxy objects etc. :)
I'll play with it on my normal install for a little to make sure it's OK
On 28 October 2011 18:56, Rob McBroom <
<EMAIL_ADDRESS>

Cool, sounds good. But you DID edit QSApplicationPrefPane.xib using IB?
That was just a matter of deleting and moving stuff up?

Correct. (Well, it wasnt IB cause thats gone, but you know.)

Just tried looking at the other two and... I don't have any ideas where
alphaLevel would have got in to that so... yeah!

Right? Its in the prevent this XIB from loading section, I suppose.

Looks good to me. I'll try and break those pref panes now somehow...
Have you been running with it fine even after the switch to the new
plugins system? As I've previously said, it shouldn't affect that at all,
but just incase :)

Yes, but not as long. I only merged the two together after the plug-in
stuff got pushed to master.
--
Reply to this email directly or view it on GitHub:
https://github.com/quicksilver/Quicksilver/pull/479#issuecomment-2559113

I couldn't break anything, and I've had a look through the code for the 3rd time - all good :)
The only thing that could be changed is removing the 'feature' key from all the actions etc of the CorePlugin-Info.plist file, but that's no biggy. It'd probably save the world a few 100kb and a few µJ :)

The only thing that could be changed is removing the 'feature' key from all the actions etc of the CorePlugin-Info.plist file, but that's no biggy.

For the sake of keeping it clean, that’s probably a good idea. Not exactly at the top of the list, though.


[proposal] Enhance Koordlet Resource Executor module for support new environments like cgroups-v2.

What is your proposal:
There will be more fancy features of higher-version kernels (e.g. cgroups-v2's iocost, psi, memcg QoS) or new hardware techniques (e.g. MPAM) adopted to achieve more robust and comprehensive QoS management. To smoothly support new environments such as CGroups V2 and higher-version of Linux kernels, the old Executor module and Resource type of the koordlet should be refactored and improved. What's more, we expect the cgroups operations can be covered in the new executor module to reduce the conflicts and abuse.
Is there a suggested solution, if so, please add it:
Refactor the old modules:

[X] executor module to support both cgroups-v1 and cgroups-v2. #834
[X] Add new system resource interface to unify the system file operations. #844

/area koordlet
/milestone v1.1


[CRITICAL] WORKER TIMEOUT errors in stderr (via Stackdriver)

From AppEngine logs -
A  GET 200 86 B 2 ms Chrome 64 / GET 200 86 B 2 ms Chrome 64
A  INFO: Rejected non-Cron request

A  GET 200 236 B 2 ms Chrome 64 /ingest GET 200 236 B 2 ms Chrome 64
A  INFO: Received cron request true

A  INFO: scheduling ingest of year=2016 month=02

A  INFO: Requesting data for 2016-02-*

A  [2018-02-21 05:04:42 +0000] [1] [CRITICAL] WORKER TIMEOUT (pid:15)

A  [2018-02-21 05:04:42 +0000] [15] [INFO] Worker exiting (pid: 15)

Looks like the server was being slow ... if the time to download the file exceeds 10 minutes, it causes deadline exceeded errors in app-engine:
https://cloud.google.com/appengine/articles/deadlineexceedederrors
If you run into this problem in your real-world application, you have a couple of alternatives:
(1) change your architecture to use Cloud Functions. Put all the ingest code in a Cloud Function and launch it off in response to the Cron.
(2) reduce the size of the file being downloaded by increasing the frequency of download. For example, instead of downloading monthly files once a month, download weekly files once a week.

This behavior is caused by gunicorn not by Google. Gunicorn has a 30 second default limit that can be overrided by setting the --timeout argument in app.yaml.
Example with 120 seconds timeout:
gunicorn -b :$PORT ingestapp:app --timeout 120

I was having the same issue with worker timeout error until I did this. Hope it helps!

Thanks! Do you want to issue a pull request with the above change (so that
you get the attribution), or do you want to me to simply make the change?
On Fri, Oct 26, 2018, 7:06 AM Cristobal Silva<EMAIL_ADDRESS>wrote:

This behavior is caused by gunicorn not by Google. Gunicorn has a 30
second default limit that can be overrided by setting the --timeout
argument in app.yaml.
Example with 120 seconds timeout:
gunicorn -b :$PORT ingestapp:app --timeout 120
I was having the same issue with worker timeout error until I did this.
Hope it helps!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/data-science-on-gcp/issues/9#issuecomment-433419486,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABqX5yHu2GijJJ_G88v3wijTqA8mpRwnks5uoxbLgaJpZM4SNFkm
.

Just did the pull request with the same timeout parameter as my previous post :)

thanks, Canas.  i don't see any pull request though

Sorry I was having issues with Google CLA, now it should be ready. Thanks!

Fixed by Canas in https://github.com/GoogleCloudPlatform/data-science-on-gcp/pull/30

@Canas Thank you so much!


CI fails on forked PRs

The permissions for fork PR workflow runs are read only and the CI workflow is attempting to write unit test results to the PR.

https://github.com/dorny/test-reporter?tab=readme-ov-file#recommended-setup-for-public-repositories


Gradient mode is changed when a color is selected

When the gradient mode is changed and a new color is selected for a existing point right after, the gradient mode return to the previous one.
This happens even in the demo
Cheers

Thanks, Release 1.3.0


Adding a link to purchase instructions

Why:
It is very unclear from the current page how to actually purchase additional GitLFS data packs. There's a correct link in Further reading section, but Upgrading Git Large File Storage does not always associate with Purchase.
Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

I've added link to purchasing instructions to Purchasing additional storage and bandwidth section.
The original text:

The updated section:

Check off the following:

[x] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

Forgot my password

sadafcrrazy

sadafcrrazy


Add code quality apps from the Github marketplace to the project

Current ones that are interesting (support Java and are free for open source):

CodeFactor
Codacy
LGTM
Snyk

When I enabled Snyk it only analyzed the pom.xml files. Looking at the settings, it seems to not support Java after all (even though the marketplace page suggests it does).

When I enabled Snyk it only analyzed the pom.xml files. Looking at the settings, it seems to not support Java after all (even though the marketplace page suggests it does).

It seems Snyk does support Java but you have to do something to make it look beyond the poms in multi-module Java cases. Will attempt to get this to work again later.


detect non-local sql tables

Fixes #1635.

We can probably refine a little with this change:
diff --git a/src/render.ts b/src/render.ts
index 926f24e1..4b2f2efe 100644
--- a/src/render.ts
+++ b/src/render.ts
@@ -59,7 +59,7 @@ if (location.pathname.endsWith("/")) {
 import ${preview || page.code.length ? `{${preview ? "open, " : ""}define} from ` : ""}${JSON.stringify(
     resolveImport("observablehq:client")
   )};${
-    files.size || data?.sql
+    files.size
       ? `\nimport {registerFile${data?.sql ? ", FileAttachment" : ""}} from ${JSON.stringify(
           resolveImport("observablehq:stdlib")
         )};`

and skip an unnecessary import of stdlib. It passes all the tests but at this point I'm wary of introducing a last-minute bug.

Okay, added. I tested, but I can’t load the Parquet file from blobs.duckdb.org anymore because of a CORS error, which is odd because I thought it worked before. The generated code looks fine though. 🤷

It worked before for me too, and now I also got the CORS error. But substituting a different URL confirms this works.
(We still have <link rel="modulepreload" href="./_observablehq/stdlib.c0fee887.js">, so maybe it isn't much better.)

I don’t think it’s possible to avoid loading the Observable standard library entirely; see src/client/main.js. Still fine to avoid the unnecessary import though and save a few bytes. 😁


chore (Report_Utils): add a conditon on columns_with_container

Do not add
 in filter html.
 should be part of report html


[Question] setLocale is not working

Here's the code to change the locale to English India for Google Drive. If you check the screenshot generated the language is still English UK
BrowserContext context = browser.newContext(new NewContextOptions()
              .setLocale("en-IN"));
Page page = context.newPage();
page.route("**", route -> {
  System.out.println(route.request().url());
  route.resume();
});
page.navigate("https://drive.google.com/");
Page newpage = context.waitForPage(()->page.click("xpath=//div[@class='drive__hero-buttons']//a[contains(text(),'Go to Drive')]"));
newpage.waitForLoadState();
newpage.type("#identifierId","invalis");
newpage.waitForResponse("**",()->  newpage.press("#identifierId","Enter"));
newpage.screenshot(new Page.ScreenshotOptions().setPath(Paths.get("screenshot-" + browserType.name() + ".png")));

I don't know what the page should be in en-IN, the problem likely has to do with the Drive localization (it might be that it just falls back to English for en-IN). It works fine with other locales, e.g. I tried with 'fr-CH' and the login page was in French:

If you think that it's because playwright doesn't properly override one of the locale-specific APIs in the browser please tell us which one, otherwise it seems that the problem is just how the drive page handles that particular locale.


high network traffic with periodic requests

Hi, JustPy is great, though now for the first time I run an app over a DSL line of less than stellar quality. The page is running periodic update() with 0.5 sleep in-between. Most the time, nothing in the page changes at all, but it is transferring 2MB/s continuously. The page itself is not complicated, only contains a large image with about 1MB worth of inline data (img=jp.Img(...), later img.src='data:image/jpeg;base64,'+base64.b64encode(...).decode('ascii')); the image almost never changes.
I am suspecting the image data are transferred with every update(). Am I correct? Is there a way to prevent that? There is a mention of use_cache but it is too terse for me to understand whether it is something to be used.
Could I just call update() method of only the components that actually changed, or is calling update() of the whole page necessary?
If what I write above does not make much sense, I will try to prepare a minimal example. If it does make sense, I will be happy for pointers how to decrease the traffic.

It makes sense, I understand what you mean. Yes, the page is transferred every update.

use_cache will not help you here because it does not stop the page being sent, only being rendered (meaning creating a JSON object from the JustPy representation) in the back end.
You can update just the component you need. Please see the following example: https://justpy.io/tutorial/pushing_data/#simple-message-board
I am not 100% this will work, but you could consider making the image a static file and getting it loaded via the src. So instead of having an inline image, have the src point to a static resource.  I think then the browser will cache the image for you. The update size would be smaller also. You could rewrite the image file when it changes to your static directory. https://justpy.io/tutorial/static/

I hope this helps, please let me know what worked best for you.

Alright, what works the best is 3 but modified with counter:
@jp.SetRoute('/current_image/{number}')
def get_image():
    return starlette.responses.Respose(content=jpgData,status_code=200,medita_type='image/jpeg')

and the image is change by setting img.src='/current_image/%d'%counter.
I also experimented without counter and reurning status_code=304 when the image did not change since the last request, but the browser would not try to fetch the image at every page refresh.
As to your point 2 (partial udpate). This MWE should put button to the "loading" state (with spinner) for 2 seconds of the callback, and the back again. It does not happen unless the whole page is updated. Am I misunderstanding something?
import justpy as jp
import time

@jp.SetRoute('/')
def main():
    wp=jp.QuasarPage(dark=True)
    butt1=jp.QButton(text='busy with button-only update',a=wp,color='red')
    butt2=jp.QButton(text='busy with page update',a=wp,color='blue')
    async def busy1(b,msg=None):
        butt1.loading=True
        await butt1.update()
        time.sleep(2)
        butt1.loading=False
        await butt1.update()
        return True
    async def busy2(b,msg=None):
        butt2.loading=True
        await wp.update()
        time.sleep(2)
        butt2.loading=False
        await wp.update()
        return True
    butt1.on('click',busy1)
    butt2.on('click',busy2)
    return wp

jp.justpy(host='<IP_ADDRESS>')

Yes, definitely a bug. You need to add butt1.add_page(wp)  after creating butt1 as components do not know which pages they are on, but even when I add that, this example does not work.

Strange bug. For some reason create_task does not work anymore. Change the object's update to the following and it works:
    async def update(self, socket=None):
        component_dict = self.convert_object_to_dict()
        if socket:
            # WebPage.loop.create_task(socket.send_json({'type': 'component_update', 'data': component_dict}))
            await socket.send_json({'type': 'component_update', 'data': component_dict})
        else:
            pages_to_update = list(self.pages.values())
            print(pages_to_update)
            for page in pages_to_update:
                try:
                    websocket_dict = WebPage.sockets[page.page_id]
                except:
                    continue
                for websocket in list(websocket_dict.values()):
                    try:
                        # WebPage.loop.create_task(websocket.send_json({'type': 'component_update', 'data': component_dict}))
                        await websocket.send_json({'type': 'component_update', 'data': component_dict})
                    except:
                        print('Problem with websocket in component update, ignoring')
        return self

And don't forget to add butt1.add_page(wp). It will work now. The changes to update are the lines commented out and the line added is just below them. I don't understand yet what stopped working.


Error after adding product list/collection in builder.io

I am new to using builder.io and also to next.js, all the setup went well and I was able to build the app and get it working.
But when I tried to add product list or collection from the builder.io portal, the next.js app started giving the below error:

I haven't deployed the app yet, its running on localhost:3000
I am not sure if I missed any step or its some other issue.
Any help is appreciated,
Thanks

Thanks @wanderingcoderr for reproting, addressed it in the pr above

hi @teleaziz thanks for the quick response, but I am still facing the same error.
I took the latest and run the application, still getting the same error as above

Hey @wanderingcoderr, should be fixed in the latest commit, please pull from master


Hide the waiting for new emails notification without losing notifications of actual emails

Checklist

[X] I have used the search function to see if someone else has already submitted the same feature request.
[X] I will describe the problem with as much detail as possible.
[X] This issue only contains a request for one single feature, not multiple (related) features.

App version
Latest Beta
Problem you are trying to solve
Getting rid of the Waiting for new emails notification while retaining the notification when emails actually arrive.
Suggested solution
I assume using a different notification channel might work but I am not altogether sure why it's there in the first place, other apps seem to be able stay running without (thinking of the Garmin app here)
Screenshots / Drawings / Technical details
No response

Just tap the notification and read the text that gets shown

Aight Samasung's wording is less than clear, it implies all notifications would disappear... Thanks a lot!


Grid that fits contents?

I want to use WaterfallGrid to contain some buttons which are laid out in a grid depending on the size available. WaterfallGrid is in a VStack with a List and some other views. I want the grid to just fit the buttons, so to fit the content as tightly as possible, and disable scrolling. Is this possible?

Hi @nrbrook, sorry the late reply!
I'm afraid is not possible to use the grid this way.
If the elements don't fit inside the grid frame, the grid becomes scrollable and the property cannot be disabled.


Aeronik ASO-12IL, ASI-12IL

Hi! Here is codes fore my climate device.
1001.json.zip

Thanks for your contribution. Added with device code 2000.


Support for '--interactive' option for 'boss init'

Deals with #74.
Changes:

Added Inquirer package
Created inquiries.py in boss/core to handle user interactions for the CLI
Minor refactors to initializer.py to allow for clean handling of interactive flag

I've left out validation for any of the fields that we get from the user. What do I need to add?
Open to suggestions about messages and anything else. 😄
EDIT: Added a better GIF.

@srishanbhattarai Great. Thanks. Looks all good :+1: .
Suggestion: can we add few more inputs?

SSH user [default = boss]
SSH port [default = 22]
Deployment remote base dir deployment.base_dir [default = '~/boss']

Check these config values

Deployment remote base dir deployment.base_dir [default = '~/boss']
@kabirbaidhya  Isn't this the 3rd option?

Yes, I didn't realized it earlier. My bad.

Looks good. Merging.


EH debugging: identify debug window through session ID

This issue is about enabling a multi-root workspace to launch and debug extensions via extension host debugging.
We have code in the extension host to broadcast messages to that window which launched the extension host. We use the simple extension development path as a way to find the target window. This cannot work anymore once you are in a multi-root workspace where you can have multiple paths (and you can have multiple windows with the same path).
After talking to @weinand we think that the best approach would be that the broadcast message is send to simply all windows and that it includes the debug session ID. With that information we can do the correct thing where we receive the message (in https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/parts/debug/electron-browser/debugService.ts#L162).
I have pushed the change to broadcast to all windows and I added some workaround for now to enable EH debugging by simply checking if a EH session is active. This unblocks us for now. Once we have the debug session ID, we can do the real fix.

I am now passing a __sessionId from the vscode debug to the debug adapter, the debug adapter then forwards this as --debugId to the extension host. Now extension host will always include this debugId in the broadcast payload.
Seems to work fine for all cases. I have removed the workarounds on the debug side but I am not sure if @bpasero added more workarounds on the extension host side which can now be removed

@isidorn very cool, the only place where I had a "hack" in was the one you seem to have taken care of: https://github.com/Microsoft/vscode/commit/0f731a79dfa8f3d14f6312ebef181697e7ad2dad#diff-4e8f1e1f9a43a95b525cbbe5abc3b2e8R169


secure derby

Add option to start the derby server in secure authentication mode, according to https://db.apache.org/derby/docs/10.13/security/index.html.
I have code that works and that I'd like to push to a branch here (if I get access) for the maintainter to decide if to accept.

I would change CMD to ENTRYPOINT, enabling you to provide custom arguments with Docker or Kubernetes. Would that help with your requirements?
This image was created for using Derby for tests. Therefore, I'm unwilling to secure the image by default or to maintain multiple variants of the image. You can easily roll your own version based on this image.
docker run --name docker-derby -Dderby.connection.requireAuthentication # ...

spec:
    containers:
      - name: docker-derby
        image: docker-derby
        args: ["-Dderby.connection.requireAuthentication", "..." ]

Ok, I agree that it probably is best not to change it to be more than intendet. Then I think i'll fork yours and make a secure derby db docker from there. Thanks for considering, you can see my changes here, comments are very warmly welcome ;-)


Disable port forwarding by default on stemcells

Issue #115
172972421

@krutten Since you provided the change, do you know who could check the release pipelines and cut a release? Have you considered the comment I made in the issue regarding whether this might break existing scenarios?

@krutten Have you tested that os-conf can re-enable port-forwarding?

Hi all,
great that os-conf-release will now offer to lock this down. Could one of you elaborate a little how you came to the decision for that solution? I assume changing the defaults on the stemcell seemed too risky? Would cutting a new major version would be a solution?

Hi @friegger,
Changing the defaults on the stemcell could affect features such as SSH Access and Tunneling.
We are then proposing a change on os-conf-release to achieve the same intent.


dartdevc testing failing on a testname containing hyphen "-".

Running test.py -cdartdevc -rchrome is failing on a test whose filename contains a hyphen, because the constructed HTML and JS try to use that filename as an identifier, I think, and the hyphen is the minus operator.  This happens with co19 strong_mode branch test LayoutTests/fast/selectors/specificity-overflow_t01.test. The test.html page that causes the error says:
(error on the line with >>>>> (added))
...
// Don't try to bring up the debugger on a runtime error.
window.ddcSettings = {
trapRuntimeErrors: false
};

A CL with a (hackish) fix for this is https://codereview.chromium.org/3001773002
@munificent

And dots are also changed to $46 by requirejs, so the line in the hack is
dartMainRunner(billbillxx["${testName.replaceAll('-', '$45').replaceAll('.', '$46')}"].main);

Can we just rename the test file?

There are thousands of them.  The change I have is more correct than the
current behaviour, I think.
On Aug 25, 2017 20:27, "Bob Nystrom"<EMAIL_ADDRESS>wrote:

Can we just rename the test file?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/sdk/issues/30450#issuecomment-325002195,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AErap5AmZeCR21GDA2Cjzk1kw3hgGT9zks5sbxIogaJpZM4O4q9p
.

dartdevc and dartdevk are still not executing tests from co19, but it doesn't seem to be a problem about hyphens anymore.

I think this is fixed now.


Add unbuffered examples to showcase

Pull request
Description
This PR improves the demo to add more unbuffered examples.
Changes made

Add unbuffered examples to the showcase tab.
Improve sample stream management (which was starting to become a bit messy to say the least).

Checklist

[x] Your branch has been rebased onto the main branch.
[x] APIs have been properly documented (if relevant).
[x] The documentation has been updated (if relevant).
[x] New unit tests have been written (if relevant).
[x] The demo has been updated (if relevant).

🌙 Available in TestFlight nightlies
The most recent state can be tested in the following builds:

Platform
Version

iOS
1.0.0 (122)

tvOS
-


Topic: to fork or not to fork

If you are building a product (open or closed source) and use an open source product to provide some basic functionality, you may find yourself in a situation where your usage of said product deviates from the evolution of the product itself. Perhaps you need a new feature that the maintainer of the open source project does not want.
At this point, you can either work around it, or you can fork and make the necessary changes yourself. This is sometimes a very difficult decision, and possibly something that could be discussed on the podcast.

I've personally once forked a project when I created @c-ares. Basically every Linux distro runs "forks" of many upstream projects when they collect and maintain an ever increasing number of local patches to save them from having to upgrade and yet fix bugs and security vulnerabilities.
But yes, forks is a fun topic!


Suggestions -- Visual Demo and Example File

idea for new user adoption

have a visual gif demo showing the usage of the tool
have an example file so someone can download an just run the script to see the output quickly to determine if they'd like to use it :)

Thank you for the suggestion, I've added it to the README now.


change upgrade to Upgrade as connection header value

Boost beast uses "upgrade" as the token for the "Connection" header, however rfc6455 defines otherwise.
https://www.rfc-editor.org/rfc/rfc6455#page-18
6.   The request MUST contain a |Connection| header field whose value MUST include the "Upgrade" token.

Confusingly other rfc's are not consistent in using it like this.
The server side should accept the value as case-insensitive but not all implementations honor this.
I've had issues with this in the field (Samsung TV's for example)
The other implementations I investigated all use "Upgrade".
C (libwebsockets)
https://github.com/warmcat/libwebsockets/blob/e8eb7d6bd66dde2156dbcd37b0e9048ed4006320/lib/roles/ws/client-ws.c#L168
Python (websockets)
https://github.com/aaugustin/websockets/blob/6dcac04c10c61dde9aa5be0374965c31f16e77f4/src/websockets/client.py#L118
Python (websocket-client)
https://github.com/websocket-client/websocket-client/blob/6ff442c6b11b56d98583056c4832d48f284246dc/websocket/_handshake.py#L112
Node.js (WS)
https://github.com/websockets/ws/blob/45e17acea791d865df6b255a55182e9c42e5877a/lib/websocket.js#L721

Looks correct to me. I'll need to fix the CI first though, but we'll have that in the next boost release.


Add OAuth2.Twitter

This exists: https://github.com/thoughtbot/yesod-auth-oauth2/blob/master/Yesod/Auth/OAuth2/Twitter.hs
However, I believe we should remove it:

I couldn't get this working in my project
Yesod.Auth.OAuth works with Twitter
Twitter's documentation claims they only support OAuth 1:

There are two forms of authentication in the new model, both still leveraging OAuth 1.0A.


Add promtail receiver to contrib v0.70.0

Would it be possible to add the promtail receiver to the next release?
It seems that the issues around it were resolved, so I wonder if a pull request adding it here would be welcome
Ping @mar4uk

The promtail receiver was removed due to issues w/ dependencies https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/18524.


How to run Donut Base and Finetuned-CORD-v2

I don't have the time to write on each issue, so I'll compile my findings here and you can do what you will.
To start things off, there are some quite specific requirements.
Start off with:
pip install build zss lit transformers==4.24.0 timm==0.5.4 protobuf==3.20.3
Any version of torch seems to work. Install the other requirements.
FOR DONUT BASE:
clone the MAIN repo, not the official one.
Run with code that imports a DonutProcessor and VisionEncoderDecoderModel from transformers,
as can be seen here: https://huggingface.co/spaces/nikhilba/donut-ocr/blob/main/app.py
FOR DONUT-FINETUNED-CORD-V2:
clone the OFFICIAL repo, not the main one.
pip install the repo so that you can import DonutModel from Donut.
This code can be seen here:
https://huggingface.co/spaces/naver-clova-ix/donut-base-finetuned-cord-v2/blob/main/app.py
If you run on CPU you might have to remove model.half(), and vice versa enable it if you run on GPU.
There's some sketchy if/else inside there depending on if you run on GPU or not defaulting to fp16.
If you run donut-base you might need to pad the image to get any output from it. Use PIL to pad quite a bit so as to make the text appear as on a paper.
If you get repeated bad characters you're probably trying to run the Donut-base by importing DonutModel.
If you get the 'init-weights' issue your requirements aren't on point, or you got the OFFICIAL or MAIN repo when you should've gotten the other one.
That's all I can remember for now, good luck.

Hi,
I tried the following:
sudo apt install git-lfs
git clone https://huggingface.co/spaces/naver-clova-ix/donut-base-finetuned-cord-v2
cd donut-base-finetuned-cord-v2
python3 -m venv .env
source .env/bin/activate
pip install -r requirements.txt
python3 app.py

But, I get the error you mentioned:
raise NotImplementedError(f"Make sure `_init_weights` is implemented for {self.__class__}")

NotImplementedError: Make sure _init_weights is implemented for <class 'donut.model.DonutModel'>
Is there something else I can try?

The link you provided only shows the main branch. I don't see an official branch there.

I tried the following:
git clone -b official https://huggingface.co/naver-clova-ix/donut-base-finetuned-cord-v2
git clone https://github.com/clovaai/donut.git
cd donut
Then I created a test.py file in the directory donut:
import argparse
import json
import os
import re
from pathlib import Path

import numpy as np
import torch
from datasets import load_dataset
from PIL import Image
from tqdm import tqdm

from donut import DonutModel, JSONParseEvaluator, load_json, save_json

parser = argparse.ArgumentParser()
parser.add_argument("--task", type=str, default="cord-v2")
parser.add_argument("--pretrained_model_name_or_path", type=str, default="../donut-base-finetuned-cord-v2"
)
args, left_argv = parser.parse_known_args()

task_name = args.task
task_prompt = f"<s_{task_name}>"
pretrained_model = DonutModel.from_pretrained(args.pretrained_model_name_or_path)

I just wanted to see if it would create the variable pretrained_model without any issues. However, I ran into the following errors:
raise RuntimeError(f"Error(s) in loading state_dict for {model.__class__.__name__}:\n\t{error_msg}")

RuntimeError: Error(s) in loading state_dict for DonutModel:
size mismatch for encoder.model.layers.1.downsample.norm.weight: copying a param with shape torch.Size([1024]) from checkpoint, the shape in current model is torch.Size([512]).
size mismatch for encoder.model.layers.1.downsample.norm.bias: copying a param with shape torch.Size([1024]) from checkpoint, the shape in current model is torch.Size([512]).
size mismatch for encoder.model.layers.1.downsample.reduction.weight: copying a param with shape torch.Size([512, 1024]) from checkpoint, the shape in current model is torch.Size([256, 512]).
size mismatch for encoder.model.layers.2.downsample.norm.weight: copying a param with shape torch.Size([2048]) from checkpoint, the shape in current model is torch.Size([1024]).
size mismatch for encoder.model.layers.2.downsample.norm.bias: copying a param with shape torch.Size([2048]) from checkpoint, the shape in current model is torch.Size([1024]).
size mismatch for encoder.model.layers.2.downsample.reduction.weight: copying a param with shape torch.Size([1024, 2048]) from checkpoint, the shape in current model is torch.Size([512, 1024]).
You may consider adding ignore_mismatched_sizes=True in the model from_pretrained method.


Can't connect to the graphic server behind a NAT network

As others have experienced, I am also incapable of launching spice from your App:
Unable to connect to the graphic server -

An weird thing is that no error message is printed after that last dash, as if no reason was given for the failure.
My intuition leads me to think this is due to the fact that my VMs are on a NAT network. Launching a SPICE instant from a file downloaded directly from proxmox works flawlessly though.
If it may help, here is a SPICE file that has worked:
[virt-viewer]
proxy=http://<IP_ADDRESS>:3128
type=spice
release-cursor=Ctrl+Alt+R
ca=-----BEGIN CERTIFICATE-----\nMIIFzTCCA7WgAwIBAgIUYrkTsekwtPrgtztG1EBjw7KSBRwwDQYJKoZIhvcNAQEL\nBQAwdjEkMCIGA1UEAwwbUHJveG1veCBWaXJ0dWFsIEVudmlyb25tZW50MS0wKwYD\nVQQLDCQ2YjVjYTI5Yi00YjMzLTQzZDItYmE3MC03MmE3MjgzMWNlYWYxHzAdBgNV\nBAoMFlBWRSBDbHVzdGVyIE1hbmFnZXIgQ0EwHhcNMjMwOTEzMTgzMzUxWhcNMzMw\nOTEwMTgzMzUxWjB2MSQwIgYDVQQDDBtQcm94bW94IFZpcnR1YWwgRW52aXJvbm1l\nbnQxLTArBgNVBAsMJDZiNWNhMjliLTRiMzMtNDNkMi1iYTcwLTcyYTcyODMxY2Vh\nZjEfMB0GA1UECgwWUFZFIENsdXN0ZXIgTWFuYWdlciBDQTCCAiIwDQYJKoZIhvcN\nAQEBBQADggIPADCCAgoCggIBALpZEEEw3eNRnGnfD2WjuGpls4qUJl+6N/11sHqA\nhDM6s2kh2xcvjXz6YlcKrFWtld+JRmLNp5QBizlslGhXNKMGTW5OTjobOLAesRdz\nXkDiZ4ZyZRFD0fkuIuuW8EbsiQU5QZZvYe18CjMlkJB6HccmtQzjVLRQ83UO0FUB\noTBfsbknyQNllW5TEFc4B7S93VAy8o62B8l7bQl1hnX3kAOfm062flJeXCrrUS6R\n5R99+Ccq7w2MtsM1fBHrgGZeFw2dzNnIZWT/LOgZodq6J27DRoAbv3LsAosGR98T\n8tOFAlg6zmLiW5uhdXuVV/Ilr6JGWFfABKxnnb/hPbk2FIy4pd7Z6HhKMTjc5C1I\n2glmp8f8sAKXJ24i78C/08DnTGjq9YXh397a6c0LteDSJhNCbJte+Jd2dT+Mj59U\nm/kaZREs8N9Ay42ifW6AkkTOmgp0Hg1/OAN7EcljDcoF3DkqE4gPGvNM3cDheGZK\nrBsj/URB1xIv6RnvkVFc2Tok1755Zqk/fLfDXl21EVBY2lBwj8M3VG4yxztBytNb\nf4Ko5TfFZN4RVpHfFnEUmU9J6GWArmvqnNHo/hbgDVvnzT3+qDIPTS8T2M6DY4vQ\nr4jM5MpeQYIuIdgEJD/Vjz0XogeQGvUZzDCAnD2X0xN3y41ro5VcjOEs8hHhkm0f\nlGKjAgMBAAGjUzBRMB0GA1UdDgQWBBTFIE803snsghgj+SmFiaLRoLzCxTAfBgNV\nHSMEGDAWgBTFIE803snsghgj+SmFiaLRoLzCxTAPBgNVHRMBAf8EBTADAQH/MA0G\nCSqGSIb3DQEBCwUAA4ICAQACq2Q0u6YK8PWlXp1RGk+ijEFl+EQrY+Yg6lH/Qe48\n7m8AHha1ziZpkuB/ydl+UMo3LEpR8/va5Jg+ZbL9ydB1t+2BZGiODza+uL68HF9t\nKkt0dBp0YmI566cTUW3GovfX9CPl7bKX3YgwQdlb7tVCpHeT/Rcahrq0X78alPNE\nypXRjH6UbhbpGw4KqFUzC+7eYkMfStodRsk1biNPU8OXEvhY6+3f9DGgw2R1ToWX\nHky777+MUBX6sP7DKRjIfkqO/+c8qOtFV5xtoJRsb/uQ++WcvLxvJ1Zt9PvuaEny\nB58f+jWEQcOGP5UyX3VbX4hYmlfx+IiAKqOGB8ISQQxs3j0gg3ZeLIrvMdmTBzHt\nayNrD/z5FnOyCGEa+clZKqNAp7NxIx1phLJ/yvAk0Fw+VqnzwAFC74mfoPz5lYiy\ntHsZ9Oidys56y+rwFt2TOoNCaK4gq1gM8qpMG4kQhrPBjQB0q/IX3mPM6SVFz86L\nn0Ekld5nzDAqzapyJkmAj84cyU89J1FZ/RsPUeImwGL/iquuhxHtlbV6C2NJp+On\ndzeMUMKwdqeoovyMahggr7cji5+ZvZZfmyI/6LAWxjvkpfMjC6axjyXODeDnwHgs\njeTl4CnVC2Ord1uQrjtgEiDRP3iH4gWa0m2tcMe5QKX8c775MIzij0tnKILdXnEM\nrg==\n-----END CERTIFICATE-----\n
password=2ae8cd8c72aa3401946f8506cf1d8a1dd0849bc5
toggle-fullscreen=Shift+F11
host-subject=OU=PVE Cluster Node,O=Proxmox Virtual Environment,CN=pve.gegi.usherbrooke.ca
title=VM 69420 - isoBuilder-11
delete-this-file=1
host=pvespiceproxy:6515a381:69420:pve::8fd1fe2e59109c1d64b062f58abb337a92cec9d9
tls-port=61000
secure-attention=Ctrl+Alt+Ins

And here is my current vdiclient.ini file:
[General]
# This is the title that is diplayed to the user
title = Connexion VDI
# This is the PySimpleGui Theme that is used. Run vdiclient.py with flag `--list_themes` for a list of themes
theme = LightGrey6
# Program Icon
icon = vdiicon.ico
# Logo displayed on all windows
logo = vdiclient.png
# Enable Kiosk mode, which does not allow the user to close anything
kiosk = False
# Enable/Disable Fullscreen mode (not applicable in Kiosk mode)
fullscreen = True
# Enable displaying SPICE ini file before opening virt-viewer
inidebug = False
# Select which guest types to display. Acceptable values: both, lxc, qemu
guest_type = both
# Show VM option for resetting VM
#show_reset = True
# Set Window Dimensions. Only use if window isn't sizing properly
#window_width = 800
#window_height = 600

[Authentication]
# This is the authentication backend that will be used to authenticate
auth_backend = pam
# If enabled, 2FA TOTP entry dialog will show
auth_totp = false
# If disabled, TLS certificate will not be checked
tls_verify = false
# User name (if using token)
#user = user
# API Token Name
# token_name = root@pam!python-vdi
# API Token Value
# token_value = 851f9426-f054-42f8-9b0a-c8a2ec578116

[Hosts]
# Hosts are entered as `IP/FQDN = Port`
<IP_ADDRESS>=8006
# pve1.example.com = 8006

# [SpiceProxyRedirect]
# The Spice Proxy provided by the Proxmox API may need to have its host/port rewritten
# These rewrite rules are written `IP:port = IP:port`
# 1. Use the inidebug and read the current proxy=pve1.example.com:3128
# 2. Add your proxmox ip to the right side e.g. <IP_ADDRESS>:6000
# pve1.example.com:3128 = <IP_ADDRESS>:6000
Can't connect to s
[AdditionalParameters]
# If you wish to define additional parameters to pass to virt-viewer you may define them here
# More parameter definitions here: https://www.mankier.com/1/remote-viewer
# Some Examples:
# Enable USB passthrough
enable-usbredir = true
# Enable auto USB device sharing
#enable-usb-autoshare = true

Here is my proxmox's server network configuration (VMs are all on vmbr1):
auto lo
iface lo inet loopback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
	address <IP_ADDRESS>/23
	gateway <IP_ADDRESS>
	bridge-ports eno1
	bridge-stp off
	bridge-fd 0

# BEGIN PROXMOX NAT TUTORIAL
auto vmbr1
#private sub network
iface vmbr1 inet static
	address <IP_ADDRESS>
	netmask <IP_ADDRESS>
	bridge_ports none
	bridge_stp off
	bridge_fd 0

	post-up echo 1 > /proc/sys/net/ipv4/ip_forward
	post-up   iptables -t nat -A POSTROUTING -s '<IP_ADDRESS>/24' -o vmbr0 -j MASQUERADE
	post-down iptables -t nat -D POSTROUTING -s '<IP_ADDRESS>/24' -o vmbr0 -j MASQUERADE
# END PROXMOX NAT TUTORIAL

Btw, this is a test machine on a closed network with no sensitive info on it. That is why I took no precautions with any IP address as I want to maximise the info available to help troubleshoot the issue.

So when you enable inidebug in the .ini file, you will receive a window
that you can copy the text of the INI file we receive from proxmox.
Copy that text and paste it here, I am convinced you need a
SpiceProxyRedirect parameter but I won't know until I see the output of the
inidebug
On Wed, Oct 4, 2023 at 2:04 PM Benjamin Chausse @.***>
wrote:

As others have experienced, I am also incapable of launching spice from
your App:
Unable to connect to the graphic server -
An weird thing is that no error message is printed after that last dash,
as if no reason was given for the failure.
My intuition leads me to think this is due to the fact that my VMs are on
a NAT network. Launching a SPICE instant from a file downloaded directly
from proxmox works flawlessly though.
If it may help, here is a SPICE file that has worked:
[virt-viewer]
proxy=http://<IP_ADDRESS>:3128
type=spice
release-cursor=Ctrl+Alt+R
ca=-----BEGIN CERTIFICATE-----\nMIIFzTCCA7WgAwIBAgIUYrkTsekwtPrgtztG1EBjw7KSBRwwDQYJKoZIhvcNAQEL\nBQAwdjEkMCIGA1UEAwwbUHJveG1veCBWaXJ0dWFsIEVudmlyb25tZW50MS0wKwYD\nVQQLDCQ2YjVjYTI5Yi00YjMzLTQzZDItYmE3MC03MmE3MjgzMWNlYWYxHzAdBgNV\nBAoMFlBWRSBDbHVzdGVyIE1hbmFnZXIgQ0EwHhcNMjMwOTEzMTgzMzUxWhcNMzMw\nOTEwMTgzMzUxWjB2MSQwIgYDVQQDDBtQcm94bW94IFZpcnR1YWwgRW52aXJvbm1l\nbnQxLTArBgNVBAsMJDZiNWNhMjliLTRiMzMtNDNkMi1iYTcwLTcyYTcyODMxY2Vh\nZjEfMB0GA1UECgwWUFZFIENsdXN0ZXIgTWFuYWdlciBDQTCCAiIwDQYJKoZIhvcN\nAQEBBQADggIPADCCAgoCggIBALpZEEEw3eNRnGnfD2WjuGpls4qUJl+6N/11sHqA\nhDM6s2kh2xcvjXz6YlcKrFWtld+JRmLNp5QBizlslGhXNKMGTW5OTjobOLAesRdz\nXkDiZ4ZyZRFD0fkuIuuW8EbsiQU5QZZvYe18CjMlkJB6HccmtQzjVLRQ83UO0FUB\noTBfsbknyQNllW5TEFc4B7S93VAy8o62B8l7bQl1hnX3kAOfm062flJeXCrrUS6R\n5R99+Ccq7w2MtsM1fBHrgGZeFw2dzNnIZWT/LOgZodq6J27DRoAbv3LsAosGR98T\n8tOFAlg6zmLiW5uhdXuVV/Ilr6JGWFfABKxnnb/hPbk2FIy4pd7Z6HhKMTjc5C1I\n2glmp8f8sAKXJ24i78C/08DnTGjq9YXh397a6c0LteDSJhNCbJte+Jd2dT+Mj59U\nm/kaZREs8N9Ay42ifW6AkkTOmgp0Hg1/OAN7EcljDcoF3DkqE4gPGvNM3cDheGZK\nrBsj/URB1xIv6RnvkVFc2Tok1755Zqk/fLfDXl21EVBY2lBwj8M3VG4yxztBytNb\nf4Ko5TfFZN4RVpHfFnEUmU9J6GWArmvqnNHo/hbgDVvnzT3+qDIPTS8T2M6DY4vQ\nr4jM5MpeQYIuIdgEJD/Vjz0XogeQGvUZzDCAnD2X0xN3y41ro5VcjOEs8hHhkm0f\nlGKjAgMBAAGjUzBRMB0GA1UdDgQWBBTFIE803snsghgj+SmFiaLRoLzCxTAfBgNV\nHSMEGDAWgBTFIE803snsghgj+SmFiaLRoLzCxTAPBgNVHRMBAf8EBTADAQH/MA0G\nCSqGSIb3DQEBCwUAA4ICAQACq2Q0u6YK8PWlXp1RGk+ijEFl+EQrY+Yg6lH/Qe48\n7m8AHha1ziZpkuB/ydl+UMo3LEpR8/va5Jg+ZbL9ydB1t+2BZGiODza+uL68HF9t\nKkt0dBp0YmI566cTUW3GovfX9CPl7bKX3YgwQdlb7tVCpHeT/Rcahrq0X78alPNE\nypXRjH6UbhbpGw4KqFUzC+7eYkMfStodRsk1biNPU8OXEvhY6+3f9DGgw2R1ToWX\nHky777+MUBX6sP7DKRjIfkqO/+c8qOtFV5xtoJRsb/uQ++WcvLxvJ1Zt9PvuaEny\nB58f+jWEQcOGP5UyX3VbX4hYmlfx+IiAKqOGB8ISQQxs3j0gg3ZeLIrvMdmTBzHt\nayNrD/z5FnOyCGEa+clZKqNAp7NxIx1phLJ/yvAk0Fw+VqnzwAFC74mfoPz5lYiy\ntHsZ9Oidys56y+rwFt2TOoNCaK4gq1gM8qpMG4kQhrPBjQB0q/IX3mPM6SVFz86L\nn0Ekld5nzDAqzapyJkmAj84cyU89J1FZ/RsPUeImwGL/iquuhxHtlbV6C2NJp+On\ndzeMUMKwdqeoovyMahggr7cji5+ZvZZfmyI/6LAWxjvkpfMjC6axjyXODeDnwHgs\njeTl4CnVC2Ord1uQrjtgEiDRP3iH4gWa0m2tcMe5QKX8c775MIzij0tnKILdXnEM\nrg==\n-----END CERTIFICATE-----\n
password=2ae8cd8c72aa3401946f8506cf1d8a1dd0849bc5
toggle-fullscreen=Shift+F11
host-subject=OU=PVE Cluster Node,O=Proxmox Virtual Environment,CN=pve.gegi.usherbrooke.ca
title=VM 69420 - isoBuilder-11
delete-this-file=1
host=pvespiceproxy:6515a381:69420:pve::8fd1fe2e59109c1d64b062f58abb337a92cec9d9
tls-port=61000
secure-attention=Ctrl+Alt+Ins
And here is my current vdiclient.ini file:
[General]
This is the title that is diplayed to the user
title = Connexion VDI
This is the PySimpleGui Theme that is used. Run vdiclient.py with flag --list_themes for a list of themes
theme = LightGrey6
Program Icon
icon = vdiicon.ico
Logo displayed on all windows
logo = vdiclient.png
Enable Kiosk mode, which does not allow the user to close anything
kiosk = False
Enable/Disable Fullscreen mode (not applicable in Kiosk mode)
fullscreen = True
Enable displaying SPICE ini file before opening virt-viewer
inidebug = False
Select which guest types to display. Acceptable values: both, lxc, qemu
guest_type = both
Show VM option for resetting VM
#show_reset = True
Set Window Dimensions. Only use if window isn't sizing properly
#window_width = 800
#window_height = 600
[Authentication]
This is the authentication backend that will be used to authenticate
auth_backend = pam
If enabled, 2FA TOTP entry dialog will show
auth_totp = false
If disabled, TLS certificate will not be checked
tls_verify = false
User name (if using token)
#user = user
API Token Name
token_name = @.***!python-vdi
API Token Value
token_value = 851f9426-f054-42f8-9b0a-c8a2ec578116
[Hosts]
Hosts are entered as IP/FQDN = Port
<IP_ADDRESS>=8006
pve1.example.com = 8006
[SpiceProxyRedirect]
The Spice Proxy provided by the Proxmox API may need to have its host/port rewritten
These rewrite rules are written IP:port = IP:port
1. Use the inidebug and read the current proxy:3128=pve1.example.com
2. Add your proxmox ip to the right side e.g. <IP_ADDRESS>:6000
pve1.example.com:3128 = <IP_ADDRESS>:6000
Can't connect to s
[AdditionalParameters]
If you wish to define additional parameters to pass to virt-viewer you may define them here
More parameter definitions here: https://www.mankier.com/1/remote-viewer
Some Examples:
Enable USB passthrough
enable-usbredir = true
Enable auto USB device sharing
#enable-usb-autoshare = true
Here is my proxmox's server network configuration (VMs are all on vmbr1):
auto lo
iface lo inet loopback
iface eno1 inet manual
auto vmbr0
iface vmbr0 inet static
address <IP_ADDRESS>/23
gateway <IP_ADDRESS>
bridge-ports eno1
bridge-stp off
bridge-fd 0
BEGIN PROXMOX NAT TUTORIAL
auto vmbr1
#private sub network
iface vmbr1 inet static
address <IP_ADDRESS>
netmask <IP_ADDRESS>
bridge_ports none
bridge_stp off
bridge_fd 0
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up   iptables -t nat -A POSTROUTING -s '<IP_ADDRESS>/24' -o vmbr0 -j MASQUERADE
post-down iptables -t nat -D POSTROUTING -s '<IP_ADDRESS>/24' -o vmbr0 -j MASQUERADE
END PROXMOX NAT TUTORIAL
Btw, this is a test machine on a closed network with no sensitive info on
it. That is why I took no precautions with any IP address as I want to
maximise the info available to help troubleshoot the issue.
—
Reply to this email directly, view it on GitHub
https://github.com/joshpatten/PVE-VDIClient/issues/74, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABIP64QUGHA5NLDTRQ53Q6DX5WXNHAVCNFSM6AAAAAA5TDCQEKVHI2DSMVQWIX3LMV43ASLTON2WKOZRHEZDMOBRGEYTQNY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

With the assistance you provided with here, I was able to figure the rest. Thank you sooo much.
This is what fixed my configuration:
[SpiceProxyRedirect]
pve.gegi.usherbrooke.ca:3128 = <IP_ADDRESS>:3128


Fix incorrect ordering in ci ExclusionPredicate

... that broke attempting to update vcpkg-tool in the normal repo.

My other PR indicates that there is no test coverage for skipped ports:

So this can happen again.


confirm delete existing tmp file before download

I encountered an error before where interrupting the tar download would cause subsequent install attempts to fail. Deleting the tmp file would make sure it gets download again.

Looking good! Would you mind applying the change also to all other downloaded files (Spark, Elasticsearch, and HBase), and submit the PR against the master branch instead? That way the change will be immediately deployed live to https://install.prediction.io/install.sh. Thanks!

how about i silently delete those files?
Best Regards,
Nicholas
On 12 March 2015 at 13:23, Donald Szeto<EMAIL_ADDRESS>wrote:

Looking good! Would you mind applying the change also to all other
downloaded files (Spark, Elasticsearch, and HBase), and submit the PR
against the master branch instead? That way the change will be immediately
deployed live to https://install.prediction.io/install.sh. Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/PredictionIO/PredictionIO/pull/74#issuecomment-78425690
.


Creating a bfloat16 numpy matrix shows different values than expected

Kindly have a look at the following:
>>> a = np.array([[1.0345,2.0000], [2.0101,3.0003]], dtype=bfloat16)
>>> a
array([[1.031250, 2.000000],
       [2.015625, 3.000000]], dtype=bfloat16)

The array was created with relatively small values, shouldn't they have remained the same?

Please look at the definition of bfloat16. What you are seeing here is type conversation from double (python's scalar float type) to bfloat16.


annotation numbers have disappeared from the stats

Not urgent, I don't need it imminently
https://curation.pombase.org/pombe/stats/annotation

Sorry, I broke that when I made this change: https://github.com/pombase/canto/issues/2261#issuecomment-650859852
Fixed now.


raidboss: remove unneeded tts entries

tts is automatic.  I think in most cases it's preferable to keep the tts
output the same as the on screen output unless it's dramatically longer
or it's something where it makes sense to have something very short in
tts because the mechanic is urgent.
This leaves unchanged o2 / o3 / o4 which are extremely verbose in their
triggers, which seemed a bit obnoxious to play over tts.

LGTM, with maybe the exception of Hyperdrive/Embrace for Kefka. Thoughts?

I'm curious why that is an exception for you.  In both cases for me, I think the important word still gets out first, but then it gets more information too.

Maybe just normalize Hyperdrive to tankCleave(), or tankBuster() on Normal? That would sidestep things altogether.

I'm going to be opinionated and say I think the embrace ones are fine as-is, and I'll just leave them.  I converted hyperdrive to be a response.


name=".entry" not available

Hi,
I am @SRIKAR-B-S-S
I made an Google Form and opened its Source Code...
And I was searching for entry, But I didn't found it.
When I searched on Google it says It no longer uses name attribution tag
And I even saw your YouTube video but it is very old( 2018 )
Hope you reply soon and solve it...
Thank You,
Regards,
B.S.S.SRIKAR

Hi,
I have already mentioned this in the ReadMe file. You can easily get entries entry codes by creating a prefilled link


android RefreshControl respects progressViewOffset only during pull-to-refresh and not on initial mount

"react-native": "^0.29.0"
progressViewOffset works when pulling to refresh, but when the 'refreshing' property is set to true when the component mounts, the offset does not seem to be recognized and it draws at the very top. From there, again, when pulling to refresh, progressViewOffset is respected.
Here, while NOT using pull, it is not respecting the offset:

Here, after pull-to-refresh, it is respecting the offset:

Thanks in advance!

@facebook-github-bot label Icebox

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/android-refreshcontrol-respects-progressviewoffset-only-during-pull-to-refresh-and-not-on-initial-mount
ProductPains helps the community prioritize the most important issues thanks to its voting feature.
It is easy to use - just login with GitHub.
Also, if this issue is a bug, please consider sending a PR with a fix.
We're a small team and rely on the community for bug fixes of issues that don't affect fb apps.

@facebook-github-bot close

How about this bug ?


Crash if lost connection to FTS server

2023-05-13 09:45:39,906 pytak INFO - Complete: <Task finished name='Task-4' coro=<RXWorker.run() done, defined at /usr/local/lib/python3.9/site-packages/pytak/classes.py:173> exception=IncompleteReadError('0 bytes read on a total of undefined expected bytes')>
ERROR:asyncio:Task exception was never retrieved
future: <Task finished name='Task-4' coro=<RXWorker.run() done, defined at /usr/local/lib/python3.9/site-packages/pytak/classes.py:173> exception=IncompleteReadError('0 bytes read on a total of undefined expected bytes')>
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/pytak/classes.py", line 179, in run
data: bytes = await self.readcot()
File "/usr/local/lib/python3.9/site-packages/pytak/classes.py", line 168, in readcot
return await self.reader.readuntil("".encode("UTF-8"))
File "/usr/local/lib/python3.9/asyncio/streams.py", line 629, in readuntil
raise exceptions.IncompleteReadError(chunk, None)
asyncio.exceptions.IncompleteReadError: 0 bytes read on a total of undefined expected bytes

Does this /always/ happen, or just happen if the FTS connection goes down?
If its the later, that's the expected behavior. Consider running as a systemd service so it restarts if it crashes (crashing is OK!): https://adsbcot.readthedocs.io/en/latest/running.html#as-a-background-system-service

like i remember only when FTS connection is down.


proof of concept micrometer instrumentation

adds metrics to the getOne catalog/timeseries endpoint see documentation: https://micrometer.io/docs/concept

@MikeNeilson This relates to contract W912HQ22F0193 Task 8 Topic B.


use TrackDependency instead of Track

TelemetryClient.Track usage is not recommended and results in a warning: This method is an internal part of Application Insights infrastructure. Do not call.

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

#sign-off


c# 7.2 read only struct support

This rebases #3456 onto Bridge v17.

This is a feature disclosed in #3491.


Updated Serverless module

Features:

Updated Serverless module to be able to use
Added make cmds: sls.plugins/sls.deploy/sls.destroy/sls.invoke
Added initial lambda module

Testing:
https://asciinema.org/a/AwglGbZK4gZenqc7sSmjk1d0r

 Find a way to clean up old ECS task definitions automatically