Shows Listable Bucket but access denied

Hi Guys,
I have a bucket that has been listed as being able to read the listings.

But when i try list the directory it says access denied.
root@robbie:~# aws s3 ls s3://coursera_assets

A client error (AccessDenied) occurred when calling the ListObjects operation: Access Denied

Hi @random-robbie,
The bucket is probably readable for authenticated users only, so you need to configure the awscli tool to use your credentials before you try to list the bucket.
This can be done easily by using this command:
$ aws configure
Please, let us know if this resolves the problem so we can close this issue.
Thanks!

Hi Guys,
I had already configured my creds with awscli which is why i am confused as i use the same keys in burp as i do with the awscli

Heya @random-robbie,
We believe that the bucket in question was still publicly readable when initially tested. But right after that, the bucket's configurations have been changed so that it's no longer publicly readable. This explains why you have been getting an "AccessDenied" error message from AWS CLI.
Thank you!


Add safe app request template

This will add the template on how to ask for changes for a safe app as requested in #2

Should we just merge dev to master?

@mikheevm we are going to remove dev branch for now so we do PRs to main


can't call git from a build.rs file

I have a build.rs file that calls git but cross build errors with:
fatal: unable to look up current user in the passwd file: no such user
Unexpected end of command stream

Maybe just passing --volume /etc/passwd:/etc/passwd:ro \ to docker would fix this?

That seems... probably too aggressive (this gives the container access to your hashed passwords and list of users).
If git is only running this to determine the current user, you might try calling the git config commands (in your container) before running the rest of your script, e.g. something like:
git config user.name "Cross Runner"
git config user.email<EMAIL_ADDRESS>

I actually think that using git from a build.rs file was a bad idea in the first place.


[HUDI-8141] Always use completion time to find begin Instant for incremental source

Change Logs
Existing Hudi incremental query would scan the entire timeline and handle hollow commits(commits that started but have not completed) along the way.
Hudi 1.x supports Instant completion time, providing a more elegant and intuitive completion timeline for incremental queries to leverage.
This PR is a part of effort of making incremental query use completion timeline by default
Impact
hoodie.read.timeline.holes.resolution.policy would no longer has effect on HoodieIncrSource, GcsEventsHoodieIncrSource and S3EventsHoodieIncrSource. These sources would always use completion time to find the start instant for incremental query.
Risk level (write none, low medium or high below)
low
Documentation Update
hoodie.read.timeline.holes.resolution.policy would no longer has effect on HoodieIncrSource, GcsEventsHoodieIncrSource and S3EventsHoodieIncrSource.

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

There is a test failure in azure CI but I cannot reproduce the issue locally, seems like a flaky test


swift 3 Xcode8 beta6 Open class

in last xcode version i got this error "Overriding non-open instance method outside of its defining module" in  setup method
override func setupView() {
super.setupView()
datasource = self
navigationBarShouldNotExist = true
view.backgroundColor = UIColor(red: 231/255, green: 231/255, blue: 231/255, alpha: 1)
}
any idea how to solve this?

I have the same issue, I tried to modify EZSwipeController.swift, setting the class as open instead of public ( c.f. : SE-0117 Allow distinguishing between public access and public overridability ).
But I still have the same problem.

This should be fixed in the latest release.


Remove public modifier from groovy methods

Groovy methods don't need the public modifier, as they're public by default. This commit removes the public from each method where it is not needed.

looks good to me. It is important not to remove the public keyword from e.g. field/property declarations but that seems to be observed.
The change makes the code more idiomatic, yet less explicit. I'm undecided whether that is an improvement.

I'm undecided as well. I hope this is not part of the Hacktoberfest event, in which case and if the contribution has merit then it'll be merged after Hacktoberfest has ended.

@Dierk  I agree that it does make it less explicit, although seeing public throughout 95% of the Groovy classes does make it far less idiomatic, and less (no pun intended) Groovy. I'm seeing more and more projects, especially new ones, that have adopted dropping the unnecessary public modifier, and was hoping that groovyfx will be able to contend with these going forward, as it looks like JavaFX is here to stay.


Adding a new member requires all original members to be up and in sync instead of a consensus

If you try to add a new member to a Raft cluster that has a down member, and the current Raft log entry has not been distributed to the down member (perhaps due to a leadership change), new members cannot be added. This is because https://github.com/logcabin/logcabin/blob/master/Server/RaftConsensus.cc#L1654 requires that all of the servers in the new configuration (this includes the downed member) to pass the isCaughtUp check instead of a majority. The Raft dissertation on page 33 seems to indicate that only a majority of the new configuration is required.
Additionally, it also looks like step 2 of the AddServer RPC is not being enforced. The routine is checking that all of _newServers are caught up but not the candidate specifically. This means that if we simply changed the check to be a quorum of staging servers, it would not guarantee that the new server is caught up.
Example:
Starting with a 3 node cluster (node1, node2, and node3) that has an in sync Raft log with node1 being the leader.

Stop node1
Leadership changes to node2 via election which increments the Raft log
Add a new node called node4

This will fail because node1 is never caught up.

Hi @mmarod, it's been a long time since I've looked at this, but I think that's true. I think the idea was that you probably wouldn't want to reconfigure into an already degraded cluster, as that might be a mistake in specifying the new configuration.
If you had additional unexpected failures during the reconfiguration, that could also get pretty messy. Theoretically only a bare majority of old servers and a bare majority of new servers needs to be available during a reconfiguration, but in practice you probably do want a bit more wiggle room to tolerate failures during reconfiguration.
In your example, if node1 isn't functioning and you want to reconfigure the cluster, you should probably remove node1 during that reconfiguration. You can replace it with a new node that is available, like node4. Of course, I can imagine wanting to have different behavior depending on your operational requirements. Are you just asking out of curiosity or are you actually using LogCabin for something? (The project isn't actively maintained these days.)
Since you linked to the dissertation, I should mention that LogCabin uses the joint consensus membership change algorithm described in section 4.3 there. Most of the rest of the concepts of the chapter do still apply or transfer over, but I just wanted to clarify.

Additionally, it also looks like step 2 of the AddServer RPC is not being enforced. The routine is checking that all of _newServers are caught up but not the candidate specifically. This means that if we simply changed the check to be a quorum of staging servers, it would not guarantee that the new server is caught up.

I'm a little confused because the AddServer RPC is described in the dissertation for the single-server membership change algorithm (not the joint consensus algorithm). What is "the candidate" in your question? A "quorum of staging servers" also seems a little sloppy (at least in an imaginary world where servers can be staging for various reasons). You probably mean a quorum of the new servers (a majority of the servers in the new target configuration).
Perhaps you'd want to change the check so that all new servers are up, but if a server was already part of the cluster, it doesn't need to be caught up. I'm not convinced this is better than the current approach, though (at least without a real-world use case).

First off thanks for the quick and thorough response for a question on an "unmaintained" project!
Taking the example -- I think you are right that it would make sense to remove node1 when node4 is added. My company's software that is using LogCabin only supplies initial bootstrap, add, and remove APIs. Perhaps it should also have a "replace" API which would seemingly get around this issue -- or to do a remove and then an add. The problem is that the software was initially designed with the assumption that if a member goes down, it will come back up at some point (ie: node1 will at some point come back online). This assumption does not necessarily hold in a Cloud environment however as node1 could be gone and lost forever (depending on the implementation of course) with node4 coming up as a replacement. So, when node1 goes down forever, adding node4 becomes impossible without removing node1 first.

A "quorum of staging servers" also seems a little sloppy (at least in an imaginary world where servers can be staging for various reasons).

Indeed -- I meant new servers specifically here.

Perhaps you'd want to change the check so that all new servers are up, but if a server was already part of the cluster, it doesn't need to be caught up. I'm not convinced this is better than the current approach, though (at least without a real-world use case).

In our specific case, node1 is never coming back so this wouldn't work. The workaround I was able to come up with checks:

That any servers in new servers, but not old servers, are caught up.
That a majority of new servers are caught up and online.

I also verified that if I brought node1 back online it caught up and membership was accurate.


[Feature] Add option to show previous/next month days

Is your feature request related to a problem? Please describe.
I'm facing challenges implementing our design using your library. Specifically, we have a Figma that displays previous and next month days to have a consistent padding all around the calendar widget. The design team added those days to avoid showing extra padding in cases where the month only takes up 5 weeks. Since the widget always shows 6 weeks, there are times when the padding looks off. Here is an example:
Figma Prototype

Currently in production (5 week month)

Currently in production (6 week month)

Describe the feature you'd like
It would be helpful to have a property in the configuration to show days from previous/next months.
CalendarDatePicker2(
  config: CalendarDatePicker2Config(
    calendarDisplayOption: CalendarDisplayOption.allDays, // default: CalendarDisplayOption.onlyCurrentMonth
  ),
)

Use cases

When you need to guarantee the padding around the calendar widget to achieve the desired design.
When you want the user to have more context into previous/next dates relative to the current month.

duplicated https://github.com/theideasaler/calendar_date_picker2/issues/161


Make sure afterTransitionLoading is set correctly

This fixes a regression most likely introduced in https://github.com/dlmr/react-router-redial/pull/7/commits/5c6f4a46250ab4f094bfe9c4daf71014cd7a702b
Without this change checks on afterTransitionLoading will always be undefined.

Good catch, thanks!

Released as 0.3.2 🎉


Merge message template and close issue references cause 500 error

Description
In a new repository

Create .gitea/default_merge_message/SQUASH_TEMPLATE.md with contents for example:

${PullRequestTitle}

Create an issue
Create a pull request with title Fix #1
500 error when going to the pull request page

It's crashing at services/pull/merge.go:101 while constructing $ClosingIssues for the template.
Can be seen here:
https://try.gitea.io/brechtvl/test/pulls/2
Gitea Version
5ae07d4 (main)
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Both self built and try.gitea.io.
Database
None

The fix seems to be adding a call to ref.LoadIssue(ctx) before closeIssueIndexes = append(closeIssueIndexes, fmt.Sprintf("%s %s%d", closeWord, issueReference, ref.Issue.Index))
						if err = ref.LoadIssue(ctx); err != nil { return .... err }
						closeIssueIndexes = append(closeIssueIndexes, fmt.Sprintf("%s %s%d", closeWord, issueReference, ref.Issue.Index))


Improve the fn pointer types

The current function pointer types have some downsides:

They assume that all functions are static code that lives forever. This isn't true for JITs or DLLs.
They are always non-nullable, safe pointers. This may not be what you want -- particularly the nullable aspect. This is connected to the previous point, because it implies that there is no place to attach a lifetime in the current syntax.

This is a "postponement issue". There have been various RFCs aiming to improve this:

#252 -- a fairly straight-forward scheme to add lifetimes to fn types.
#883 -- a simple scheme to change the syntax of fn to &'static fn for forwards compatibility.
#996 -- a more involved scheme which introduced a kind of unsized type.

It should be possible to adapt these schemes backwards compatibly.

I am currently of the opinion that if function pointers are not considered pointers by the language, then we'd better call them something else, like "function handles". This can be the first step towards improving fn types.
"Function pointers are not considered pointers" feels like a flaw in Rust's design, but "function handles are not considered pointers" doesn't.
Also, if later "true" function pointers are introduced, we need to disamiguate fns and "true" function pointers. Renaming fns to "function handles" is a good way to do so.
I wonder if such a renaming proposal should be an RFC? :)

We still need a way to specify lifetimes for fn types, and I don't feel like representing function pointers as actual borrows in Rust is really nessecary. I favour an approach similar to #252 -- fn 'a (A, B) -> R, where if the lifetime is omitted, 'static is assumed.
However, when it comes to DLL loading (see #15040), lifetimes of functions that are being used outside of the loaded code will be bound by the lifetime of the library (handle) itself, which the loaded code is unaware of. In this sense, 'static' in all the library code refers to the lifetime of the libray.
This means that when symbols are resolved from a DLL, a 'static lifetime needs to be translated into 'a, where 'a is the lifetime of the library handle. This also means the definition of 'static in Rust may need to be changed.
Additionally, there should be some similar way to specify lifetimes for Fn closures.


Bug fix: properly display execution time in frontend.

This is a very minor fix...

lgtm

Thx!

aa6b9c77b14f2619eec4b3578798201a5c2e1c20


Remember me checkbox in Login

How can I add a remember me checkbox in the login page? As in, how exactly can I remember the user for 30 days (for example)? Right now the session expires quite quickly when left idle, and it's become rather inconvenient to keep having to login.
Also it would be nice if the username field is pre-filled with the username that was typed in, when the login page reloads with the "Incorrect login" message.

I agree. The cookie right now expires rather quickly, right after closing
the browser.
On Mar 14, 2017 13:52, "ADTC"<EMAIL_ADDRESS>wrote:

How can I add a remember me checkbox in the login page? As in, how exactly
can I remember the user for 30 days (for example)? Right now the session
expires quite quickly when left idle, and it's become rather inconvenient
to keep having to login.
Also it would be nice if the username field is pre-filled with the
username that was typed in, when the login page reloads with the "Incorrect
login" message.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dignajar/bludit/issues/399, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKLvvMnrk6sCyblosAoE31sTkT7umSvks5rlislgaJpZM4McJ7S
.

I think it's only a session, not based on cookie. I guess I'll try to look for this. Any hints, @dignajar ?

I think cookies are involved. Without cookies, the site won't even let you
login. Also, it seems to me that the cookies expiration time is somewhat
inconsistent at some times. Sometimes time it expires when I left the tab
for a while, sometimes it last even after I closed the browser.
On 19 March 2017 at 00:26, ADTC<EMAIL_ADDRESS>wrote:

I think it's only a session, not based on cookie. I guess I'll try to look
for this. Any hints, @dignajar https://github.com/dignajar ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dignajar/bludit/issues/399#issuecomment-287557088,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKLvj597qacSeXEUQFIje7rUQ1Izxv9ks5rnAWpgaJpZM4McJ7S
.

@acrox999 indeed, there is a single cookie called Bludit-KEY (it expires with the session). When I deleted it, I was kicked back into the login page.
But logins can function without cookies based on session alone (though they would not be able to remember the login). I have programmed a website that does it. I also read that the session cookie (used by Bludit, just to store the session id) is not a standard cookie but a special cookie that expires with the session, and so you can consider it as "no cookies".

Implemented on v2.1-beta
https://github.com/bludit/bludit/tree/v2.1-beta


[BUG] Cant even screenshot but when you set classic cursors from 2006 or 2014 when you set to normal cursor iit do not changes back anymore

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[ ] I did not answer truthfully to all the above checkboxes.

What problem did you encounter?
i explained problem in title
Bloxstrap Log
No response

Nvm thanks for discord people

FYI: enable the "Force Roblox reinstallation" option if something like this happens


Drop adapter blink4home

https://github.com/Flashy-GER/ioBroker.blink4home/tree/master

No update since 3 years
A lot of complaints in the reviews
Never left beta state

https://github.com/ioBroker/ioBroker.repositories/blob/420e8f9a24c8cd4d7e4911a3241982f98ed6bdb2/sources-dist.json#L177-L181

agreed. @mcm1957 Could you please do that?
Should we also inform the dev via an issue in his repo?

oookkk ... repo now got transferred to community so we coouulld try to fix it also ;-)

oookkk ... repo now got transferred to community so we coouulld try to fix it also ;-)

Did you transfer it?
Who is / will maintain it?
There are severel adapters which need an maintainance urgently. At community. I tried to mark them at info list hoping that someone reacts. Take a lokk there. I will notebitcat meeting if i can attend. Othereise I will send a zelegram message once a month noting those communuty adapters which gave a serious problem.

it is in no case a complete transfer because noone updated URLs yet :)

Ähmm ...
Do not even see the repo within communit orga.
Where do youcsee some transfer?
Besides of this info do not spend to much time for this. I ll check after bathing holiday.

ahhhhh shit I mixed adapters ...sooory ... yes proceed as ppsted above. remove and inform dev. Sorry for confusion

Issue at adapters repo created:
https://github.com/Flashy-GER/ioBroker.blink4home/issues/50
Adapetr removed from Repo
https://github.com/ioBroker/ioBroker.repositories/pull/2293


Error in storing the certificate in a PFX file using a password that also comes from the key-vault.

Powershell throws error if you store the certificate in a PFX file using a password that also comes from the key-vault.
For example, the following code doesn't work. Is there a workaround?
$password = $(PFX_PASSWORD)
$protectedCertificateBytes = $certCollection.Export([System.Security.Cryptography.X509Certificates.X509ContentType]::Pkcs12, $password)
$pfxPath = $(Agent.TempDirectory)\MyCert.PFX
[System.IO.File]::WriteAllBytes($pfxPath, $protectedCertificateBytes)

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

ID: 69ff8e50-4187-3622-1beb-155f006af5f5
Version Independent ID: bc56fa96-bded-95f8-39a4-a9e5242db1bf
Content: Azure Key Vault task - Azure Pipelines
Content Source: docs/pipelines/tasks/deploy/azure-key-vault.md
Product: devops
Technology: devops-cicd
GitHub Login: @RoopeshNair
Microsoft Alias: ronai

Please accept our apology for the significant delay in addressing this issue.
It looks like you're working through an issue with the product itself, rather than an issue with the documentation. Here are a few options where you might consider asking your question:

Azure DevOps on Stack Overflow
Azure DevOps Support Bot


Provide the now required response object to the smtp exception

mail gem 2.8.0 added ruby 3.1 support[1] which added net-smtp as an explicit gem dependency because it had recently become an extracted gem.
Previously, we used the ruby stdlib version, which was using gem version 0.1.0 in ruby 2.7.0 and 0.2.1 in ruby 3.0.0.
Starting with net-smtp 0.2.2, the Net::SMTPError types now require a response object [2] and an optional message. :shrug:
[1] https://github.com/mikel/mail/pull/1472/files
[2] https://github.com/ruby/net-smtp/pull/26/files

I think this should be backported as far back as we'll pull in mail gem 2.8.0.

Seems like they broke semver?

@jrafanie We are locked to 2.7.1 on oparin.  Should we bump oparin to 2.8.0 and backport this?  I'm concerned it might auto-update on us and we might forget to backport this otherwise.

@jrafanie We are locked to 2.7.1 on oparin. Should we bump oparin to 2.8.0 and backport this? I'm concerned it might auto-update on us and we might forget to backport this otherwise.

@Fryguy I'm comfortable with upgrading from 2.7.1 to 2.8.0 and pulling back this change to work with it.  The changes don't look that significant and I'd rather find out now.

https://github.com/mikel/mail/blob/2-8-stable/CHANGELOG.rdoc


fix(menu): alphabetical order for menu items

In oder to fix this problem:
https://github.com/Bonial-International-GmbH/MkRadar/issues/3
I am sending this patch

Maybe alphabetic ordering isn't the best option, I think the user would except to have the same order as in the config yaml file.

Huuum then I should think how we can apply that because it is not as easy as this one I think

Dear @nilsmull as you can see here we are creating the menu items based on the database rows and sadly by design there is no any option there to preserve the Item order based on the order of YAML configuration file:
https://github.com/Bonial-International-GmbH/MkRadar/blob/main/helpers/db_handler.py#L68
Also consider this fact, adding another column there is not enough because what if after the first compile user change the order of items in the YAML config file? Then we should detect and update all effected rows in the DB unless we make DB absolute and only use YAML file for everything!
What I can suggest is  let's bring the stability and consistency via alphabetical order for now and in future if we really needed it we can plan for bigger changes :)


refactor(@angular-devkit/build-optimizer): optimize purify plugin

This uses exec instead of replace and inserts only the pure annotation instead of a full replace.

LGTM, thank you.


[GSK-981] Better output from the pydantic decorator validate_arguments

It’s not clear for that we expect a wrapped model BaseModel instead of a clf

The method wrap_model is confusing as it return a BaseModel , maybe a WrappedModel would be less confusing

From SyncLinear.com | GSK-981

@rabah-khalek-khalek: is it solverd today? If yes, can you put the card as Done

Not done yet.

I didn't find the pydantic decorator to be super customizable, the other solution is to write our own decorator (which is tideous, a start is attempted here: https://github.com/Giskard-AI/giskard/tree/task/pydantic_decorator but not complete).
Maybe pydantic v2 would be already improved w.r.t the one we currently use (https://docs.pydantic.dev/latest/blog/pydantic-v2/).


Command Palette should return focus to terminal pane

VSCode Version: 1.43.0-insider
OS Version: Win 10 (10.0.18362 Build 18362)

Steps to Reproduce:

Open an integerated terminal (and give it focus)
Open the Command Palette with your keyboard shortcut
Select something (e.g. Clear Terminal) or even hit escape to close the Command Palette
Notice how your focus (and cursor) are now in the editor pane (previously, the terminal had both)

Similar to the closed issue #46961, but for a different command palette command.

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

Duplicate of https://github.com/microsoft/vscode/issues/93055 ?

/duplicate #93055


implement api.MulAcc in plonk frontend

in 1 constraint instead of 2.

I had a quick look at it when trying to optimise field emulation. I'm not sure but I feel that without custom gates cannot do. We would have to do o <- a + b*c, but we only have three wires.
However, if we could do in two wires, then it could help a lot :)

heh, it seems current version already does 1 constraint when c is a constant, so ... I can close this issue, nothing to do at the moment.


2 possible package resolutions

Since the last update, I have the following message:
Collecting package metadata (current_repodata.json): done
Solving environment: |
Warning: 2 possible package resolutions (only showing differing packages):
  - conda-forge/noarch::folium-0.11.0-py_0, conda-forge/osx-64::arosics-1.2.5-py38h50d1736_0
  - conda-forge/noarch::folium-0.12.0-pyhd8ed1ab_0, conda-forge/noarch::arosics-0.9.24-pyh9f0ad1d_0

I think this is solved in the pip version changing the requirement folium>=0.6.0,!=0.12.0 by folium>=0.6.0, but not in the conda-forge version, am I right?
Thanks!

Actually, this should be solved in the latest release (v1.2.5):
https://github.com/conda-forge/arosics-feedstock/blob/e36db03171580898ca2d9776e67b00cfa0a30189/recipe/meta.yaml#L27
Could you try to force conda to install arosics 1.2.5 by running conda install -c conda-forge arosics=1.2.5. I am not sure why conda´s package resolver suggests v0.9.24 at all (@ocefpaf do you see a chance to avoid this?).
Unfortunaly, there was a broken folium release (0.12.0), which was already patched on PyPI (0.12.1) but the 0.12.1 release is still missing on conda-forge (see https://github.com/python-visualization/folium/issues/1438). So the only way I see to work around this at the moment is to block folium 0.12.0 and to fall back to 0.11.0 in arosics.

I can do that, but everytime I do:
conda update --all

I get the same message. I didn't know about the broken folium release. I hope they can fix it soon.
Thanks!

I think resolver suggests v0.9.24 because if I have installed folium 0.12.0, it is the latest arosics version compatible (it doesn't have an explicit folium!=0.12.0)
I think everything will be solve with the new folium release.
Please, close this issue if your are fine with that.

The latest compatible version should be 1.2.3 because this does not block folium 0.12.0. Version 0.9.24 was simply the last noarch release but it is outdated now and should not suggested by the resolver anymore.
However, I guess conda update --all should work if you would create a completely new environment with conda env create -n arosics_env -c conda-forge arosics.

This seems to be fixed after updating some package metadata of the older conda-forge arosics releases here. Closing this for now.


[Backport] Adding null check to earliest and latest aggs

Backport of #15972 to 29.0.1.

@LakshSingla The fix #16165  would not fix the issue the CI issue in this PR :
Error:  Failures:
Error:  org.apache.druid.java.util.emitter.core.HttpEmitterTest.timeoutEmptyQueue
Error:    Run 1: HttpEmitterTest.timeoutEmptyQueue:82
Expected: a value less than <0.0>
     but: <2.0> was greater than <0.0>
Error:    Run 2: HttpEmitterTest.timeoutEmptyQueue:82
Expected: a value less than <0.0>
     but: <2.0> was greater than <0.0>
Error:    Run 3: HttpEmitterTest.timeoutEmptyQueue:82
Expected: a value less than <0.0>
     but: <2.0> was greater than <0.0>
Error:    Run 4: HttpEmitterTest.timeoutEmptyQueue:82
Expected: a value less than <0.0>
     but: <2.0> was greater than <0.0>

     ```

The http emitter is due to a flake.


Review who is assigned to the issues

This is a general feedback.
It happens very often that the issues are assigned to a user who is not active or her/his last contribution into this repository is more than year ago.
I'm almost 100% sure that those questions will be never answered.
Examples:
https://github.com/microsoftgraph/microsoft-graph-docs-contrib/issues?q=assignee%3AJeremyKelley+is%3Aopen
https://github.com/microsoftgraph/microsoft-graph-docs-contrib/issues?q=assignee%3Aabheek-das+is%3Aopen
I don't want to spam other users with "kindly reminders" but maybe if you can review the process who is the best person to provide the answer...

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

ID: e8a7f020-9903-7af9-7102-3bf26ff89c3a
Version Independent ID: 11dc19b6-ee12-b814-c871-f0df80adc8d3
Content: Microsoft Graph overview - Microsoft Graph
Content Source: concepts/overview.md
Product: non-product-specific
Technology: microsoft-graph
GitHub Login: @angelgolfer-ms
Microsoft Alias: MSGraphDocsVteam

Issues have been reassigned.


Chinese Traditional Encoding (Big5) Regex

Found by @nosekbk
Tested with moment.js 2.10.6

Make my browser use Chinese Traditional Encoding (Big5)
refresh site
see error in console Uncaught SyntaxError: Invalid regular expression: missing /
see file for Arabic Saudi Arabia (ar-sa) has a broken regex

Suggested fix: use String.fromCharCode(000) where 000 is the character code for all the unicode characters you're currently using as literals. Since javascript executes in UTF-16 this will ensure all your characters are transferred in ascii ie: the int param for fromCharCode and generated as unicode at runtime as expected.

missing closing bracked in regex ^ due to hard coded non-ascii string literals

Should we use fromCharCode only for chars that don't fit in 2 bytes, or for all non-ascii? People are using Unicode in js, so you're suggesting everyone should stop?

Thanks for this request.
Sorry this caused you trouble.
For now, we will not take this change.
Please re-open if you still have concerns.


Prefix primaryColor

Fixes #29

@robisaks @neokree this PR adds just another attribute, while the best solution is to read existing "primaryColor" attribute defined through support-library-v21

Also please do not forget that primaryColor is not the only problematic attribute. Same goes for accentColor and others.


Arbitrary properties can be set on resourceful collections

Example code
>>> contacts = currencycloud.Contact.find()
>>> len(contacts)
8
>>> type(contacts)
<class 'currencycloud.resourceful_collection.Contacts'>
>>> contacts.status = 'enable_no_trading'
>>> contacts.status
'enable_no_trading'

This is the Python way. It is even discouraged to disable this behaviour (like using slots) as it cripples functionalities like serialization.


mini_racer does not support TextEncoder when server renders react component

A bug is a crash or incorrect behavior. If you have a debugging or troubleshooting question, please open a discussion.
Environment

Ruby version: 3.1.2
Rails version: 7.0.3
Webpacker version: 6.4.0(shakapacker)
React on Rails version: 13.0.1
OS version: MacOS 12.2
Hardware version: Apple M1 Pro

Expected behavior
Try to create new app as the steps.
The difference is that I change the argument prerender in directory app/views/hello_world/index.htm.erb, like this <%= react_component("HelloWorld", props: @hello_world_props, prerender: true) %>
It should show the HelloWorld component when accessing http://localhost:3000/hello_world
Actual behavior
But it failed and shows some errors below,
ERROR in SERVER PRERENDERING
Encountered error:

Error evaluating server bundle. Check your webpack configuration.
===============================================================
Caught error:
ReferenceError: TextEncoder is not defined
===============================================================

when prerendering HelloWorld with props: {"name":"Stranger"}

code:

        (function() {
          var railsContext = {"railsEnv":"development","inMailer":false,"i18nLocale":"en","i18nDefaultLocale":"en","rorVersion":"13.0.1","rorPro":false,"href":"http://localhost:3000/hello_world","location":"/hello_world","scheme":"http","host":"localhost","port":3000,"pathname":"/hello_world","search":null,"httpAcceptLanguage":"zh-CN,zh;q=0.9,en-US;q=0.8,en;q=0.7","serverSide":true};
              ReactOnRails.clearHydratedStores();

          var props = {"name":"Stranger"};
          return ReactOnRails.serverRenderReactComponent({
            name: 'HelloWorld',
            domNodeId: 'HelloWorld-react-component-29970588-318b-4c7c-8540-32b5f05f3b98',
            props: props,
            trace: true,
            railsContext: railsContext
          });
        })()

eval (webpack://app/./node_modules/react-dom/cjs/react-dom-server.browser.development.js?:145:19)
eval (webpack://app/./node_modules/react-dom/cjs/react-dom-server.browser.development.js?:6733:5)
Object../node_modules/react-dom/cjs/react-dom-server.browser.development.js ((execjs):2012:1)
__webpack_require__ ((execjs):2586:42)
eval (webpack://app/./node_modules/react-dom/server.browser.js?:6:7)
Object../node_modules/react-dom/server.browser.js ((execjs):2045:1)
__webpack_require__ ((execjs):2586:42)
eval (webpack://app/./node_modules/react-on-rails/node_package/lib/handleError.js?:7:32)
Object../node_modules/react-on-rails/node_package/lib/handleError.js ((execjs):2177:1)
__webpack_require__ ((execjs):2586:42)
/Users/devin/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/mini_racer-0.6.2/lib/mini_racer.rb:223:in `eval_unsafe'
/Users/devin/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/mini_racer-0.6.2/lib/mini_racer.rb:223:in `block (2 levels) in eval'
/Users/devin/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/mini_racer-0.6.2/lib/mini_racer.rb:343:in `timeout'
/Users/devin/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/mini_racer-0.6.2/lib/mini_racer.rb:222:in `block in eval'
/Users/devin/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/mini_racer-0.6.2/lib/mini_racer.rb:220:in `synchronize'

Then I try to switch the JS engine of ruby to node, like export EXECJS_RUNTIME=Node.
It works.
It seems that the mini_racer(0.6.2) does not support the TextEncoder.
Is there something I missed?
Small, reproducible repo

I encountered the same issue. @justin808

Greetings, this was my solution for adding all the required polyfills for react SSR with mini_racer:
add this plugin to your webpack config:
const NodePolyfillPlugin = require('node-polyfill-webpack-plugin');

// need to polyfill certain node libs like `stream` and `util` (used by `react-dom/server`)
config.plugins.push(
  new NodePolyfillPlugin({
    excludeAliases: ['console', 'Buffer'],
  }),
);

serverPolyfills.js (import this file at the top of our server-rendering file b/c it needs to run before importing react)
//
// polyfills for mini_racer v8 runtime (which has less features than node.js)
//

// `URL` constructor
import 'core-js/actual/url';
// `URLSearchParams` constructor
import 'core-js/actual/url-search-params';

// polyfill TextEncoder & TextDecoder onto `util` b/c `node-util` polyfill doesn't include them
// https://github.com/browserify/node-util/issues/46
import util from 'util';
import 'fast-text-encoding';

Object.assign(util, { TextDecoder, TextEncoder });
``

Thank you @wyattades! I'm assuming we have different version though, because for me URL and URLSearchParams were in core-js-pure instead of core-js. Then I obviously also needed to install the fast-text-encoding package with yarn. So for anyone else having the same issue as me, I needed to make the following changes to @wyattades code:
// `URL` constructor
import 'core-js-pure/actual/url';
// `URLSearchParams` constructor
import 'core-js-pure/actual/url-search-params';

@wyattades I owe you big thanks.
I ran into this problem while working on https://github.com/reactjs/react-rails/pull/1290 & your solution is the only logic that didn't result in TextEncoder is not a constructor errors.


About LSTM pretrained model

Could you add LSTM pretrained model? I want to use it for some tasks. Thanks :)

Yes, we plan to, but we have to actually run the pretraining with the pytorch version, which will probably take a while (have to find some free compute then actually run it, so it’ll be at least a week or two).

Haven't been able to free up a lot of compute recently - so it'll take longer to get this than I anticipated. We'll definitely put it up at some point, but I can't promise a specific timeline.

Has the pre-trained LSTM model uploaded yet?

I haven't been able to justify using 4 GPUs for a week to train this model... Plausibly over the summer Berkeley compute will free up a little bit and I can train it then.

Hello, have you been able to work on the pre-trained LSTM model? Many thanks!

I've started training it. Should ideally finish in 1-2 days, but may take longer if there are issues during training. I'll try to have it uploaded in a week or two at most.

Hello again! any new about the LSTM model? thank you for your help and time!

Ok realistically this isn't going to happen, I don't have the time or compute to train this long enough and test it to make sure the weights are reasonable. If you really want an LSTM model I'd recommend using SeqVec from the Rostlab (here)


Add pornstars to pornhub extractor

Adds 'pornstars' as a dict item returned by _real_extract in pornhub.py.
Returns a list of unicode strings which are the names of credited pornstars.

Just random metafield can't be added to info dict it should be introduced first.
All introduced fields should be generic enough to be used with any kind of video. pornstars can only be used for porn videos thus not enough generic. cast or something sounds more generic.

A fair criticism, what is the process to request a new field? Cast would seem an appropriate suggestion. Might this be considered an official request for the cast field or would a pull request with the field name changed work? Thank you.

For accepting a new field a PR that explains the field here should be opened for discussion and opinions.


Search query

Create a model representing a query for cloudant

PR #17 was merged. will close this.


Clean up the dead branches

We don't need:
jared-integrate-with-sheets
jared-refactor-cards
rich-text-editor
jared-card-options
jared-intercom
jared-integrate-rte
jared-fix-header
jared-trigger-send

I removed every old branch except jared-trigger-send.


Dashboard with docker-compose still loading

I use your lastest build of parse-server, with the correction of the issue #22 of the Dashboard.
I use a LetsEncrypt SSL certificate to access via https to the Dashboard (because http is not accessible), and I saw indefinitly the Dashboard loading like this image :
http://goo.gl/UTjcWg
I remove the -d option of docker-compose command line, that's the log I have :

parse-cloud-code_1 | hello.js
parse-cloud-code_1 | main.js
parse-cloud-code_1 | twitch.js
mongo-data_1       | Error parsing command line: unrecognised option '--break-mongo'
mongo-data_1       | try 'mongod --help' for more information
parse-server_1     | npm info it worked if it ends with ok
parse-server_1     | npm info using<EMAIL_ADDRESS>dockerparse2_mongo-data_1 exited with code 2
dockerparse2_parse-cloud-code_1 exited with code 0
parse-server_1     | npm info using<EMAIL_ADDRESS>parse-server_1     | npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>parse-server_1     | npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>parse-server_1     |
parse-server_1     | ><EMAIL_ADDRESS>start /parse
parse-server_1     | > nodemon --watch /parse/cloud index.js
parse-server_1     |
parse-dashboard_1  | npm info it worked if it ends with ok
parse-dashboard_1  | npm info using<EMAIL_ADDRESS>parse-dashboard_1  | npm info using<EMAIL_ADDRESS>parse-dashboard_1  | npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>parse-dashboard_1  | npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>parse-dashboard_1  |
parse-dashboard_1  | ><EMAIL_ADDRESS>dashboard /parse-dashboard
parse-dashboard_1  | > node ./Parse-Dashboard/index.js & webpack --config webpack/build.config.js --progress --watch
parse-dashboard_1  |
parse-server_1     | [nodemon] 1.9.1
parse-server_1     | [nodemon] to restart at any time, enter rs
parse-server_1     | [nodemon] watching: /parse/cloud/**/*
parse-server_1     | [nodemon] starting node index.js
parse-dashboard_1  | The dashboard is now available at http://localhost:4040/
parse-server_1     | parse-server-example running on http://localhost:1337/parse (:1337/parse)                                                      57% 54/68 build modulesContainer#eachAtRule is deprecated. Use Container#walkAtRules instead.
parse-dashboard_1  | Container#eachRule is deprecated. Use Container#walkRules instead.
parse-dashboard_1  | Container#eachDecl is deprecated. Use Container#walkDecls instead.
parse-dashboard_1  | Node#removeSelf is deprecated. Use Node#remove.         31% 82/231 build modulesNode#before is deprecated. Use NHash: 85303ea680e020d55d40 parse-dashboard_1  | Version: webpack 1.12.14
parse-dashboard_1  | Time: 136083ms
parse-dashboard_1  |                                    Asset     Size  Chunks             Chunk Names
parse-dashboard_1  | img/cf0a48bbd61302f119a4576be8e01ed9.png   652 kB          [emitted]
parse-dashboard_1  |                      dashboard.bundle.js  3.55 MB       0  [emitted]  dashboard
parse-dashboard_1  |                              sprites.svg  99.3 kB          [emitted]
parse-dashboard_1  |     + 1243 hidden modules

I've reproduced. If you access dashboard from remote not localhost, you must access with basic auth via https only by the following command:
USER1=yongjhih \ # your username
USER1_PASSWORD=yongjhih \ # your password
APP_ID=myAppId MASTER_KEY=myMasterKey docker-compose up

ref. https://github.com/yongjhih/docker-parse-server#usage-of-letsencrypt-for-parse-dashboard
And I found browser blocked some scripts, click unblock it.

Thanks for your reply !
It don't work for me, I try with docker-compose-le.yml and it don't launch.
I deal with a http access, it works, great job !

You can update images by the following commands:
docker pull yongjhih/parse-server
docker pull yongjhih/parse-dashbard

And try again: https://github.com/yongjhih/docker-parse-server#usage-of-https-certificated-domain-with-letsencrypt


Consider switching to Codecov for online coverage reporting

The graphical user interface of Codecov looks more organized and intuitive than Coveralls.
Related issue: DART #806

👍 Codecov has a much nicer UI. I've always thought that Coveralls looks a bit like the Coveralls project page looks a bit like a ransom note. 😁
@psigen Thoughts?

Generally fine with this.  But let's try it out before we commit to it completely.
We should be able to add codecov support in a branch without removing the coveralls support, right?  I think they have non-overlapping configuration.  We can try that and see how it looks?

I've created a PR for this. Please take a look at it when you have a chance.


Install missing local dependencies

To be able to have an isolated system, all dependencies should be
installed locally. This way we can force the version we want, and
unexpected behaviour don't need documentation.

Nodemon is a perfectly fine choice, albeit not so modern. Libraries like these are oftentimes built with rollup and TypeScript. I'm more than happy to set up the environment if you'd like.
Also, with this being an open source initiative, I miss coding guidelines. These can be set with ESLint and Prettier (one or both), and can be enforced by GH Actions.


Supporting by Turnip Freedreno

Hi, can you add info in Wiki that Mesa (latest stable release, 23.1.2) Turnip Freedreno (Open-source drivers for Qualcomm Adreno GPU's) supporting? It working fine with Box64, Box86 + Wine

Android is not a supported platform and Linux on Qualcomm based laptops is exceedingly rare.

But here using same Turnip drivers as in another Linux systems

There's a difference between it working fine and actually being supported. It might work just fine for some games (probably not all, especially D3D11, but who knows), but that doesn't mean we're committing any resources to testing it, or specifically cater to it.


Feature/dotnet wrapper

Some refactoring and fixing up tests.  Also fixed a bug that meant that a custom rpc agent path was being ignored.

Closed as I'm about to resubmit a new one having upgraded to Thrift 0.10.0


Use UIImagePickerController insert Image from photo album

I save image to ducoment and  path is  file:///var/mobile/Containers/Data/Application/6A26C23E-E084-40DF-80EB-5D41D5AC994A/Documents/test_image_name.jpg
I insert image to RichEditorView
A. image is ok
editorView.insertImage("file:///var/mobile/Containers/Data/Application/6A26C23E-E084-40DF-80EB-5D41D5AC994A/Documents/test_image_name.jpg", alt: "pic")
B. image is not loaded
editorView.insertImage("test_image_name.jpg", alt: "pic")
How can i insert image use image name? not image full path.
Because documents path can be changed when Xcode build and install app.
Thank you!

Hi. How do you observe didFinishPickingMediaWithInfo to get those way (A) which as you telling inserts correctly?
I've tried different ways but nothing happens.

You're right, the path to the Documents directory changes when you restart your app.
You should never save the direct file URL to an image. Instead, you should be using the NSFileManager to get the location of the Documents directory, and then get the URL of your image file from inside there.
let manager = FileManager.default
let directoryPaths = manager.urls(for: .documentDirectory, in: .userDomainMask)
let documetnsDirectory = directoryPaths[0].path

This should give you the path to the documents directory. I will leave finding your actual image inside the Documents directory as an exercise for the reader :)


Additional method for installing emacs on Windows

A much simpler way of creating the emacs instance (especially if you have to use Anaconda environments)

I think this is redundant with the section below? https://github.com/SciCrunch/sparc-curation/blob/master/docs/setup.org#package-manager

I must have missed that. You ignore this.


Auto-Completion with Language Server does not find certain built-in modules when using import

I'm not a python expert, so I hope this is the an appropriate place to comment on this issue.
Environment data

VS Code version: 1.31.0-insider
Extension version (available under the Extensions sidebar): 2018.12.1
OS and version: Windows 10.0.17763.253
Python version (& distribution if applicable, e.g. Anaconda): 2.7.11
Type of virtual environment used: Not virtual, but using Python provided by Autodesk Maya

Expected behaviour
When using the Python Language Server for auto-completion, intellisense should be provided for built-in modules (eg: os, json, binascii, etc).
Actual behaviour
Intellisense is not shown for many (but not all) built-in modules. Examples of modules that don't have intellisense are os, json, and collections. Other do show intellisense, like binascii.
Pylint reports "unresolved import" for the 'missing' modules. However, scripts containing these modules run normally.
When using the Jedi auto-completion system, all these modules have the expected intellisesnse.
If scripts
Steps to reproduce:
I'm using Python distributed as part of Autodesk Maya. I've set up "python.pythonPath" and "python.autoComplete.extraPath" so that auto complete is working for my own modules and for the modules provided by Maya.

Create a python file in VS Code with the line "import os".
Attempt to us the os module in the file.
No intellisense appears. Pylint reports the modules as unresolved.
Switch to Jedi auto-complete. Reload VS Code.
Intellisense shows up for os module; Pylint no longer reports an error.

Logs
Output window doesn't mention anything other than the initialization message and pylint "rating".
Again, I'm not an expert, but from what I can tell, the Jedi auto-complete comes from modules that are stored in a zip file called python27.zip that resides in the same folder as the python executable (called 'mayapy.exe'). I wonder if the Jedi system is capable of extracting intellisense from modules stored in this archive while the Python Language Server is not.
In the image below, the module binascii has intellisense, but os, json, collections, and gzip were not able to be resolved.

@michaeldaw Please could you test this once again with the latest version of the extension. This will ensure you are using the latest version of the Language Server as well.

I'll do so as soon as I can. Thanks.

I'm currently on the latest version. 2019.1.0.
Should I bring this up on the Python Language Server repo?

Fixed upstream


Build Metadata tool

Two minor issues:

In the ScriptTool GUI for 'Build Metadata', it looks like the full list of values in the 'Sources', 'History', and 'Missing definitions...' arguments were not input (so Arc recognizes valid options in the code as errors).

As noted in the documentation, the fact that Arc doesn't set the PROJ_LIB environmental path can cause issues w/ the projection function.  Rather than try and redefine this absolute environmental path at the system level (which I worried would upset other environments), I just added the following to near the top of my 'GEMS_MetadataFGDC_AGP2.py' file (must be somewhere below 'import arcpy' line):

** edited to try and get code to format in markdown
  #In some ArcPro created virtual environments the path to the PROJ library (opensource projections) is not always created
  #This will cause a gdal/osr error when trying to transform coordinates to a new CRS.
  #This statement attempts to guess what the path should be
  #though there is no guarantee this will work w/ all environments

  import os

  if not('PROJ_LIB' in os.environ):
      arcpy.AddMessage('Could not find PROJ_LIB in environment path, trying to guess path to proj.db folder')
      proj_path = r'C:\ArcGIS\Pro\Resources\pedata\gdaldata' #You could specify this as an optional argument (w/ a default path)
      projdb_path = os.path.join(proj_path,'proj.db')
      if os.path.exists(projdb_path):
          arcpy.AddMessage('Found proj.db in expected directory, adding to working environmental variables')
          os.environ['PROJ_LIB'] = proj_path
      else:
          #Splitting warning message into multiple lines for issue format
          warningMessage = 'Could not find proj.db in expected directory: {} \n'.format(proj_path)
          warningMessage += 'Code expected to fail dur to an error in CoordinateTransformation_TransformPoint. \n'
          warningMessage += 'Please identify the correct location of proj.db'
          arcpy.AddWarning(warningMessage)

I have seen value lists stored in the parameter form be flakey like this elsewhere, getting overwritten when it's not clear why. I will reset them.
that's a good idea. Thanks for working it up. I will try it out.

Actually, I'd forgotten, some of those value list options are set in the validation class of the tool depending on other inputs. They work for me in that the list values change as I set and reset the dependent parameters. Do you have some parameter values that produce an error message?

Apologies Evan!  I had just checked the value list in the parameters tab after clicking through the options (with no inputs specified). When I actually specify input parameters the validations are working correctly and I can see the suite of value options.
Thanks for the quick response! I'll mark this as fixed.


Private IPs and Docker in SpaceStation

Description

Updated to use private network
Consolidated to a single VM / dev container
Mock Space Station is now a container with docker installed
Private network between Mock Ground Station and Mock Space Station is bandwidth constrained to match ISS
Applied latest production configuration to Space Station image
Miscellaneous notes update

Issue reference
#28 @cbrown101

@glennmusa updates made; successful test on Win10.  Good to go on this side.


Remove outdated samples

This PR removes samples that are no longer used after dotnet/docs#9551 is merged.
This PR must wait until that PR is merged.

Builds will start to warn us about that if they are 😄

Oh good :)


Binary redistribution with Chocolatey package

While Visual Studio Code source code is available under MIT license, the binary product is not and has its own license which disallows binary redistribution.
I'm maintaining the Visual Studio Code Chocolatey Package which currently downloads the installer from the website and runs it afterwards. This makes the package dependent on having an internet connection though, and also might be an issue in an enterprise environment. While Chocolatey Business Edition supports internalization of packages it would be easier if we were allowed to package and redeploy the Visual Studio Code installer in the package available from the Chocolatey community feed.
Would it be possible to get permission to redeploy the installer directly with the Chocolatey package?

@chrisdias Any news on this?

@chrisdias @kieferrm @egamma would any of you be able to provide some input on this question?
Thanks!

@egamma just wanted to follow up with this request again.  Could you provide some input?  Thanks.

@gep13 our goal is that all binary distributions of VS Code have the same quality and are smoke tested and sanity checked by team. Therefore we are careful in singing up for additional distros since this will increase our test matrix size.
@gep13 @pascalberger we haven't seen many requests for a chocololatey distribution since this issue got reported, therefore can you motivate, why you are suggesting this additional distribution channel?

@egamma said...
our goal is that all binary distributions of VS Code have the same quality and are smoke tested and sanity checked by team. Therefore we are careful in singing up for additional distros since this will increase our test matrix size.

A Chocolatey Package is simply a wrapper around the published, quality and smoke tested, distribution.  At the minute, the VSCode Chocolatey Package simply downloads the exe from the published URL during installation:

You can see more here:
https://chocolatey.org/packages/VisualStudioCode#files
The request here that @pascalberger was making was to allow the Chocolatey Package to be more resilient, by containing the actual installation file, rather than downloading it.  During the creation of the Chocolatey Package, the same download file, from the above URL would still be used, so I don't think this would add anything to your testing matrix.  At the minute, we the Chocolatey Community, can't embed the installer, since the license does not permit it.
To date, there have been 116,385 downloads of the VSCode Chocolatey Package, so I would say that it is a reasonably popular package.  It is certainly the way that I install VSCode onto any machine that I am using.
Please let me know if you have any questions.  Would be happy to Skype/Call, if you wanted to talk further.

@egamma Please note that the number of downloads @gep13 has mentioned only contains downloads of the package from the chocolatey.org server. In enterprise environments it's common to use an internal server which caches the packages and the actual number of installations of Visual Studio Code through Chocolatey is therefore propably much higher.

@egamma, can we get some answer to this ? Even negative one.
The reason for additional channel of distribution is because package that contains the binary can be cached in the company. This is typically done with tools like Nexus, Artifactory etc. This means that local developers have speed and stability and local security as it can be subject to local storage anti-x protections. You also keep protecting version that you developed with which may be important on given project (technical docs may depend on version of development tools and usually do).
Besides that, Chocolatey community gallery itself provides additional protection with integration with VirusTotal.
As stated, this is chocolatey automatic package which grabs the official Github release few hours after it is published by vscode team.

@majkinetor I'll look into this and will update the issue.

I would be interested to know the outcome of this also.  I would like to build an AppImage for VSCode, but I noticed that the binary license is far more restrictive than the license for the source...

@egamma Any updates on this?

Hi all,
Stepping in here to help.  With what is likely not great news.
Today (and we will keep reevaluating this) we would like to only distribute the binary for VS Code via our own web-endpoints.  So any package management should call those endpoints and request the latest version.
We want to do this to preserve maximum flexibility in shipping schedules [which helps us preserve our velocity] and help everyone keep on the latest, latest.  Any indirection (via distributing the package in another way) is something for the time being we would like to avoid.
As I say we can and will continue to evaluate this but for now distribution should be managed via those endpoints and the Linux packages we publish.
I'll close this issue for now - but we can re-open if there is more to discuss immediately.  Just let me know.
Sean
VS Code Team Member

@seanmcbreen thank you for getting back to us, even though the answer isn't the one that we had hoped for.
I do just want to point a couple of things though, just in case they had been missed...
The Chocolatey Package for VSCode is currently maintained on the Chocolatey Core Team Packages Repository.  This is a fully automated system, that checks the web endpoints for all the packages that are maintained by it every 6 hours.  As a result, a new Chocolatey package version for VScode would be available within at most 6 hours after it was shipped and published to the website.  So in terms of affecting your shipping schedules, and ensuring that everyone has the latest, latest, version, I don't see how this cause an impact.
For example, if you have a look at the release dates for VSCode:
https://github.com/Microsoft/vscode/releases
And compare them to when the corresponding Chocolatey Package was made available:
https://chocolatey.org/packages/VisualStudioCode
You will see that they very closely align.  NOTE: I am going to assume that the differences are due to things like there being a slight delay between the release being created on GitHub and the download actually appearing on the website.
Another suggestion, if you and the team would be interested, would be for the VSCode team to take ownership of the Chocolatey Package and you guys push the new package versions to Chocolatey.org as part of your build/release pipeline.  That way, there would definitely be no change in your velocity, and the new package version would be immediately available.
I just wanted to put these thoughts here in case they could add to your on-going discussions.  And I also wanted to add that 347,734 package installations from Chocolatey is not a small number of people who are actually making use of the package that is currently being made available.

@egamma @seanmcbreen - Is there a reason why you disallow binary redistribution in your license? How about allowing unmodified binary distribution? Perhaps that will solve @pascalberger's Issue.

@kirtangajjar great question - it really comes down to wanting to have some degree of control over the experience of distribution.  Our primary concern is to ensure that all users get the most up-to-date bits, bits that are auto updating and that we can adequately monitor how well that experience works (e.g. failures in downloads, network performance, ...).  We also know our users are most successful when they discover our website and the related docs.
To date we have been lucky enough to be able to encourage people to simply point to our endpoints (both within MSFT and outside of is).
Distribution in abstract is actually not something we are against and I can see how it can actually be a win-win-win for the distributor-our joint customer-and us.  so I'm sure we will continue discussing this.

@gep13 this is helpful context and I need to digest it a little.  I agree the install count is not a small number.  We actually love the fact the package exists and are very impressed at the speed of updates.
So thank you for the extra content, the key concern for now is the offline distribution [and packaging of the distro] that's the only part giving me pause.
Sorry, not much of substance in this response but I did want you to know I reviewed your response and we will keep thinking about it.  But for now our preference is to continue with the existing model.

@seanmcbreen said...
So thank you for the extra content, the key concern for now is the offline distribution [and packaging of the distro] that's the only part giving me pause.

Please let me know if you wanted more information.  I would be happy to jump on a Skype call, or similar, at some point to discuss any further points that you wanted clarification on.

Honestly, this decision really confuses me.  You say that it's to protect VSCode and ensure that quality binaries are being shipped to everyone, yet you have the license worded in such a way that anyone who would want to redistribute VSCode would have to redistribute a gimped version of it.  In my opinion, distributing a gimped version of VSCode without the extension marketplace would do much more damage to VSCode's image than redistributing the binary in the form you provide it without changes.
I really fail to see how repackaging your binary without changing it does anything to hinder your quality assurance process.  Most developers just say something like Hey, we didn't make that so we don't really support it, sorry instead of closing the doors completely like this.  It really boggles my mind how restricting the binary distribution helps anyone here.


Adding trusted Root CAs to activegate

Hello, i am following your guide here to connect my Dynatrace SAAS platform to our eks cluster: https://github.com/Dynatrace/dynatrace-operator, however on the last step in the Dynatrace UI, i am getting "There was an error with the TLS handshake: The specified certificate is not trusted". I know under normal circumstances on an Activegate i can do this https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-activegate/configuration/configure-trusted-root-certificates-on-activegate/, but how can i mount a keystore to my activegate pod? There does not seem to be an option to add a volume to it in the cr.yaml.

Hey @dm185372
the containerized AG as of now is not able to take a custom certificate.
We already implemented this and it will be released with the next release of the operator.
Please stay tuned until then

Thanks for the response @DTMad - do you guys have any ETA when the next release will be? I can work around it until then, i am just wondering.

We try our best to make it until end of Q3

This duplicates https://github.com/Dynatrace/dynatrace-operator/issues/102
Will be fixed with 0.3.0


[QUESTION] I used skiasharp version 1.68.0. But the quality of the generated PDF document is 7882kb. This is too large for saving. Is there a way to reduce the quality?

You can ask questions here, but there might be better places to do that as well:

If you have questions on how to use SkiaSharp with .NET, this is the best place.
If you have questions on how to draw a picture, but need some suggestions, there is the community to help:

StackOverflow: https://stackoverflow.com/questions/tagged/skiasharp
Xamarin Forums: https://forums.xamarin.com
Gitter.im Chat: https://gitter.im/xamarin/XamarinComponents

If you have questions on skia, or need to ask more advanced questions about the native API, the skia Group is the place to go: https://groups.google.com/forum/#!forum/skia-discuss

But... If you still aren't sure about where to ask your question, then go ahead and ask here! We will try and answer you, but if we can't, then we will help you get the answers you want.

Could you attach some sample code that is causing the PDF to be large? Or is even a blank PDF large for you?
What is the platform/OS and what are you putting on the PDF. A simple snippet of code that is causing the PDF to be large will help a lot.

Thank you for your reply.
Just the simplest text document. Documents similar to salary details. If there is no content, it is about 4kb. However, even if you draw a point, it will become about 7882kb. Very distressed!
The current framework does not support other advanced software! .net core 1.1

Closing this as a duplicate of #848


[BUG] Artefact (white line) on colored cards when wrapped in horizontal listview

Hi,
First, thank you very much for this amazing package !
My issue concerns a colored version of your flip card.
The cards are wrapped in an horizontal listview.
When in scroll horizontally (vertically it is ok), a white line appears sometimes.
Behavior

Flutter doctor
[✓] Flutter (Channel stable, 3.3.4, on macOS 13.1 22C65 darwin-arm, locale fr-FR)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.3)
[✓] VS Code (version 1.74.2)
[✓] VS Code (version 1.71.1)
[✓] Connected device (3 available)
[✓] HTTP Host Availability
Thanks in advance for your help!

I cannot reproduce this when running the sample app on MacOS, Chrome, Android or iOS.

I cloned the repo, installed dependencies and ran it, no further changes.
I'm using Flutter 3.7.3 via fvm.
You mentioned the issue only happens when scrolling horizontally. The example code won't let me scroll horizontally.
Reordering the cards doesn't produce the issue (except the reordering-animation is completely broken).
Flutter doctor output

[!] Flutter (Channel stable, 3.7.3, on macOS 13.3 22E5236f darwin-arm64, locale de-DE)
• Flutter version 3.7.3 on channel stable at /Users/ciriousjoker/fvm/versions/3.7.3
! Warning: dart on your path resolves to /opt/homebrew/Cellar/dart/2.19.0/libexec/bin/dart, which is not inside your current Flutter SDK checkout at /Users/ciriousjoker/fvm/versions/3.7.3. Consider adding /Users/ciriousjoker/fvm/versions/3.7.3/bin to the front of your path.
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision<PHONE_NUMBER> (7 weeks ago), 2023-02-08 15:46:04 -0800
• Engine revision 248290d6d5
• Dart version 2.19.2
• DevTools version 2.20.1
• If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
• Android SDK at /Users/ciriousjoker/Library/Android/sdk
• Platform android-33, build-tools 33.0.1
• ANDROID_HOME = /Users/ciriousjoker/Library/Android/sdk
• Java binary at: /Applications/Android Studio Preview.app/Contents/jre/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
• Xcode at /Applications/Xcode-14.2.0.app/Contents/Developer
• Build 14C18
• CocoaPods version 1.11.3
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio
• Android Studio at /Applications/Android Studio Preview.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
[✓] VS Code (version 1.76.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.60.0
[✓] Connected device (3 available)
• sdk gphone64 arm64 (mobile) • emulator-5554 • android-arm64  • Android 13 (API 33) (emulator)
• macOS (desktop)             • macos         • darwin-arm64   • macOS 13.3 22E5236f darwin-arm64
• Chrome (web)                • chrome        • web-javascript • Google Chrome 111.0.5563.110
[✓] HTTP Host Availability
• All required HTTP hosts are available
! Doctor found issues in 1 category.


[BUG]

Describe the bug

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior

Screenshots

Desktop

OS:
OS Version/Flavor:
CPU:

Additional context

Upgrade to 1.2.9 pops up message -"exchange" is not in the mnemonic...-


Rename quickstart.md to OWNERJUANDCHAVEZFCCIDIHDT56YN1.quickstart.md

Why:
Closes [issue link]

What's being changed:

Check off the following:

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

Writer impact (This section is for GitHub staff members only):

[x] This pull request impacts the contribution experience

[x] I have added the 'writer impact' label
[x] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

content/codespaces/getting-started/OWNERJUANDCHAVEZFCCIDIHDT56YN1.quickstart.md

Save data protect from others


Fix Bezalel contact details

Overview
Fix Bezalel contact details

pls fix the DCO with git commit --amend -s

thanks Bez :) I think we're going to centralize maintainers in kubescape/kubescape

Works for me, just I am not listed there for some reason.

pls fix the DCO with git commit --amend -s

it fixed only the merge commit for some reason


(bleachbit.install) fix installer removal

Description
Changes $toolsPath to $toolsDir, because $toolsPath is not defined in this package.
Motivation and Context
Fixes #1850
How Has this Been Tested?
Installed in the test environment and ensured that the installer was removed.
Screenshot (if appropriate, usually isn't needed):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Migrated package (a package has been migrated from another repository)

Checklist:

[x] My code follows the code style of this repository.
[ ] My change requires a change to documentation (this usually means the notes in the description of a package).
[ ] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[ ] I have updated the package description and it is less than 4000 characters.
[x] All files are up to date with the latest Contributing Guidelines
[x] The added/modified package passed install/uninstall in the chocolatey test environment.
[x] The changes only affect a single package (not including meta package).

:white_check_mark: Package verification completed without issues. PR is now pending human review

@TheCakeIsNaOH awesome work! Thanks for your contribution!


Markdown code doesn't render in Kanban titles and Table column options

What happened?
When I create a kanban view and set the titles of the columns to be a certain property, and I have set those titles with the double * for bold for example, it doesn't render bold but instead shows as:
**text**

What did you expect to happen?
To render markdown everywhere
How can we reproduce it (as minimally and precisely as possible)?

Create a project from a folder
Create a new property
Check allow markdown to render
Add an "option"/some value with markdown code like bold or color
The drop down menu for the options won't render markdown code in table view
Create kanban view and set it to group by the previously created property
Titles for column title won't render markdown code as well

Anything else we need to know?
No
Plugin version
1.16.3
Obsidian version
1.4.5
OS
Windows

Thanks for sharing your usecase! I would consider this to be a feature request rather than a bug, as enabling rich text rendering is an optional feature initially introduced for the table cells in #319 .
Since the board column title is essentially also a field value, we can work on the proposal, but it will require some detailed design. For example, should we place the Enable rich text configuration in each view, or make it an option for the entire plugin? Also, how to let auto-complete ignore/render the rich text?
For now, if you enable rich text formatting in the field configuration (which can only be found in the table view) and include this field in the board/gallery view, you will see the rich text taking effect. This is explained in #372 . It seems that we need to find a better way to manage fields and field configurations.

This issue sound like #316 quite a bit.

Part of this request is implemented in #732. While the request on rich-text rendering in auto-complete requires a upstream change, or we should build an auto-suggest by ourselves. So I would mark this as resolved and open up another issue to track changes on auto-suggest.


Only do notifications when we actually have new paths

Just add some bookkeeping to better capture when this state mutates
@keybase/react-hackers

:mag_right: The commits 6fd1b8714510...a17bf13b4664 introduced some visual changes on linux:

Changed: unlock_folders-Success (before) (after)

retest this please

:mag_right: The commits 0ca480236e15...d9a200d7baa4 introduced some visual changes on win32:

Changed: unlock_folders-Single (before) (after)

Changed: unlock_folders-No_paperkeys (before) (after)

Changed: unlock_folders-Normal (before) (after)

retest this please

:mag_right: The commits 176e1f22c97d...a27eb4a51e49 introduced some visual changes on win32:

Changed: user_search-Normal (before) (after)

Changed: unlock_folders-Normal (before) (after)

:mag_right: The commits 1255e536f0ef...550e39ea9fe8 introduced some visual changes on win32:

Changed: unlock_folders-Normal (before) (after)

@keybase/react-hackers bump

👍


payara/serever-full

Expected behavior
Actual behavior
Information about the Issue
Steps to reproduce the behavior

...
...

No information provided or steps to replicate - Closing 😞


Revert "Revert "DA-3331: org affiliation changes switch list org to use platform service - Part 1 (#49)" (#50)"

This reverts commit 7344e4af1f3c5aff4c96da73af1e5990bef00798.
Raising this PR to deploy the org service changes on prod.
Related PR - https://github.com/LF-Engineering/dev-analytics-affiliation/pull/49 & https://github.com/LF-Engineering/dev-analytics-affiliation/pull/50

I have shared the secrets zip on slack


graphql-modules-preset is not adding interface and union resolvers to Module.Resolver

Describe the bug

When using graphql-module framework, the generated resolver is missing definition for interfaces and unions.
To Reproduce
Steps to reproduce the behavior:
Repo that reproduce the issue with readme for explanantion
https://github.com/laurent-lubino-roam/graphql-modules-codegen-resolver

Expected behavior

I would expect to be able to resolve types directly in the resolver using resolveType instead of isTypeOf
Environment:

OS: macOS
@graphql-codegen/graphql-module-preset:
NodeJS: 16

Additional context

HI @the-ult, the workaround we've used was to define each type (InterfaceImpl1, InterfaceImpl2 and InterfaceImpl3)  that implements the base interface (for you MyInterface)  in the resolver and define a __isTypeOf like so:
export const resolvers: DeviceModule.Resolvers = {
   InterfaceImpl3: {
       __isTypeOf: (obj) => {
           return obj.type === 'InterfaceImpl3' // or whatever helps you to identify your object type
      }
   }
}

instead of having one __resolveType in the base interface (MyInterface) resolver.
Also, we've stopped using union and the result types are using the base interface MyInterface, then in your queries, you can do something like:
query GetMyInterface {
    getMyInterface {
       id
       ... on InterfaceImpl1 { .... }
       ... on InterfaceImpl2 { .... }
       ... on InterfaceImpl3 { .... }
    }
}

Hope it helps.

Thanks gonna try it out tomorrow.
Would be great though, if this could be fixed/added to the graphql-modules-preset

@dotansimha is this issue a bug or a feature => intended?

I used to fix 🤔  it like this:
export const PersonResolvers: PersonModule.Resolvers | unknown = {}

But that way you'll lose all Typings.. 😳
Was trying it now like this:
export const PersonResolvers: PersonModule.Resolvers & { PersonUnion } = {}

Not much better, but at least this way we keep the types of all other PersonResolver properties.
Gonna try @laurent-lubino-roam way today.


Create tiqr lib for enrollment and registration

This issue is imported from pivotal
Create an java library to handle tiqr enrollment and registration. The Tiqr-flows and protocols are described here:

https://wiki.surfnet.nl/display/~urn%3Acollab%3Aperson%3Asurfnet.nl%3Ahavekes/Tiqr+protocol
https://github.com/Tiqr/tiqr-java-connector

The authentication URL will be changed to :
https://eduid.nl/tiqrauth/?u=&s=<session_key>&c=&i=<server_idenitfier>&v= (Peter Havekes - Apr 21, 2022)


[SKIP CI] Update the vDVS documentation

Addresses the issue #2003

@shuklanirdesh82 I have addressed your comments. Can you please take a look at it again?
Thanks!

@ashahi1 following comment (mentioned at https://github.com/vmware/docker-volume-vsphere/pull/2009#pullrequestreview-80401667) is still left to address.
Can you please correct the information for http://vmware.github.io/docker-volume-vsphere/documentation/faq.html#how-to-install-and-use-the-driver?


Missing endpoint input files

hello,where is the endpoints file .npy in experiments except abilene?

@stwerner97 What are the endpoint files about exactly? They are configured in the trace.yml even for the other networks but only added to the repo for abilene. Do you know?

@stwerner97 What are the endpoint files about exactly? They are configured in the trace.yml even for the other networks but only added to the repo for abilene. Do you know?

i know what the endpoints file about，it is used to sample the endpoints to create the request. i thought it was a part of the Specific datasets.without germany50.npy and other endpoints npy,the script.py can't run.i have solved the problem already,thank you

Great to hear that you solved the problem already. What did you do exactly to solve it?

As we had some issues finding suitable (and similar) trace datasets for each scenario, the Abilene data is used in all cases. For network topologies larger than Abilene, we first subsample endpoint nodes and use these as ingress / egress nodes. The arrival rates at these designated nodes then follows the pattern of the Abilene data.
Hope this helps!

Great to hear that you solved the problem already. What did you do exactly to solve it?
i find the file in another repository,(https://github.com/FreeeBird/Flow-By-Flow-Prediction/tree/main/dataset)  and change the data to make the sum of it to 1 by multiplying a factor.After that the program can run properly.i am not sure whether way is right or not,as i have not done the expriment yet.Can you give me some sugguestions？thanks!

As we had some issues finding suitable (and similar) trace datasets for each scenario, the Abilene data is used in all cases. For network topologies larger than Abilene, we first subsample endpoint nodes and use these as ingress / egress nodes. The arrival rates at these designated nodes then follows the pattern of the Abilene data.
Hope this helps!

thank you for your help!


Fix subgraph stacktrace

Fixes https://github.com/graphprotocol/graph-node/issues/3500.
Waiting on https://github.com/paritytech/wasm-instrument/pull/16 and https://github.com/paritytech/parity-wasm/pull/328 to  be merged and tagged, will fix revert to upstream once those are available.

I'm afraid we'll have to address https://github.com/paritytech/wasm-instrument/pull/16#discussion_r877962671, making sure that parse_names doesn't bubble up errors but rather fails silently with an unwrap_or_else.
Otherwise, this looks great. I'm sure Parity will take a closer look and find out if there's anything else we must fix.


Add production app build in main Dockerfile

The Dockerfile.dev can use the development server, but the production image should have a prebuild app, not the least for reasons of performance:

need production build, see https://reactjs.org/docs/optimizing-performance.html
maybe https://react-server.io/docs/guides/production ?

Related to #57

Use a multi-stage build to finally have an nginx-based image: https://docs.docker.com/develop/develop-images/multistage-build/

Use a multi-stage build to finally have an nginx-based image: https://docs.docker.com/develop/develop-images/multistage-build/

I have encountered a problem while fixin this issue.
I have created a multistage Dockerfile using nginx. And works in creating a production build And then deploying it with nginx.
At the moment it looks like this:

But when i start up the docker compose command. The ui container seems to be unable to the communicate to with the rest of the microservices. I get a 502 Bad Gateway when tying to access the usual localhost Port.
In the Terinal this error is thrown:
webserver_1      | 2021/01/11 08:41:55 [error] 30#30: *1 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: , request: "GET /favicon.ico HTTP/1.1", upstream: "http://<IP_ADDRESS>:3000/favicon.ico", host: "localhost", referrer: "http://localhost/"
The problem seems to be that something in the internal routing is not working. I have tried a few things with different ports and the nginx.conf file. But nothing worked.

I have encountered a problem while fixin this issue.
I have created a multistage Dockerfile using nginx. And works in creating a production build And then deploying it with nginx.
At the moment it looks like this:

But when i start up the docker compose command. The ui container seems to be unable to the communicate to with the rest of the microservices. I get a 502 Bad Gateway when tying to access the usual localhost Port.
In the Terinal this error is thrown:
webserver_1      | 2021/01/11 08:41:55 [error] 30#30: *1 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>, server: , request: "GET /favicon.ico HTTP/1.1", upstream: "http://<IP_ADDRESS>:3000/favicon.ico", host: "localhost", referrer: "http://localhost/"
The problem seems to be that something in the internal routing is not working. I have tried a few things with different ports and the nginx.conf file. But nothing worked.

Please commit your changes to a branch and open a work-in-progress pull request. Looking at screenshots of files makes it very hard to look at problems.
Also: Do you have no problems with the regular docker-compose configuration? Did you do a docker-compose down -v --rmi all to be sure that there are no mix-ups with the existing images of the compose configuration?

Please commit your changes to a branch and open a work-in-progress pull request. Looking at screenshots of files makes it very hard to look at problems.
Also: Do you have no problems with the regular docker-compose configuration? Did you do a docker-compose down -v --rmi all to be sure that there are no mix-ups with the existing images of the compose configuration?


docs: Fix operators table

Fixed table for the operator precedence in Operators.md

pow is part of https://github.com/PRQL/prql/pull/4125 !
Will merge tomorrow unless I get feedback.
Thank you for spotting though!

Will close since #4125 is merged. Thank you regardless!

@max-sixty I'm not sure of the state of this, but the table of Operator Precedence (https://prql-lang.org/book/reference/syntax/operators.html#operator-precedence) in the public Book is still messed up. Would you check? Thanks

Yes, we should do a release. (Generally we push docs-only changes to web, but here it was both docs and code...)
In retrospect I should have merged yours, backported to web, and then resolved the conflicts with mine. Sorry!

Ahah! I see now... Both code and docs. I shoulda made separate PRs. I'll do that next time... Thanks

Ahah! I see now... Both code and docs. I shoulda made separate PRs. I'll do that next time... Thanks

Yours was perfect! Because this was docs only. So mea culpa...

I don't do "blame". It's enough if it gets fixed when it's pointed out. See WPNTFIIWDKIB


Add kelvin characteristic

Setting the white temperature doesn't seem to work very well on the Superlegends Bulb and requires the setting to be done in the Magic Home Wifi app.

Solved by using the white LED when set to 0 Hue and 0 saturation and adding the purewhite option.


Improve logging tidiness and capability

Needed for Hyperion #910

Removes logging-level argument - various handlers are instantiated with default levels:

a TimedRotatingFileHandler set to INFO, keeping 30 days worth of logs
a MemoryHandler which will dump 200k DEBUG lines (~10-15 minutes) to file if it sees an event of level ERROR
a Graylog handler at INFO
DEBUG to stdout/err

Instructions to reviewer on how to test:

Confirm tests are not broken

Checks for reviewer

[ ] Would the PR title make sense to a scientist on a set of release notes
[ ] If a new device has been added does it follow the standards

Some tests are failing, but seem to be unrelated to this issue. Could you merge main again to solve those please?