Feature/layer option table range

Coverage decreased (-0.02%) to 53.303% when pulling ab45639f64b47e18f6a4f4d75a9f160130be546a on adreyfus:feature/layer_option_tableRange into 40f8b6f4febfb1409337532048005ecfed3b0e9b on chafey:master.

I've added a pseudo-color rendering pipeline that uses the modality and VOI LUTs before using the color lookup table to transform to RGBA. Could you check if that satisfies your use case?

Thank you @swederik ! Indeed I obtain the same result by changing the VOI of the layer, instead of using options.tableRange.

Great! One less PR!


[HUDI-2114] Spark Query MOR Table Written By Flink Return Incorrect T…

…imestamp Value
What is the purpose of the pull request
Fix the bug that spark query MOR tble written By flink teturn incorrect timestamp value.
Brief change log

Currently we convert  the  tableAvroSchema to requiredStructSchema first,  then convert it to requiredAvroSchema using SchemaConverters.toAvroType. In such process , the mill-second Timestamp avro type written by flink (Timestamp(3)) will convert to spark sql's Timestamp type first, then the SchemaConverters.toAvroType convert the sql's Timestamp type to micro-second Timestamp avro type finally. HoodieMergeOnReadRDD will use micro-second Timestamp to parse the mill-second timestamp value which result in incorrect value like '1970-xx-xx xx:xx:xx' .
In order to solve this problem, I get the requiredAvroSchema for the tableAvroSchema directly which can keep the origin timestamp type. And then convert the requiredAvroSchema to requiredStructSchema

Verify this pull request
(example:)

Add TestMergeOnReadSnapshotRelation

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Hi @garyli1019 , can you take a look this PR?

Codecov Report

Merging #3208 (14b39be) into master (01ad449) will decrease coverage by 2.47%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #3208      +/-   ##
============================================
- Coverage     52.19%   49.71%   -2.48%
+ Complexity     2659      405    -2254
============================================
  Files           335       67     -268
  Lines         14981     2985   -11996
  Branches       1505      320    -1185
============================================
- Hits           7819     1484    -6335
+ Misses         6536     1365    -5171
+ Partials        626      136     -490

Flag
Coverage Δ

hudicli
?

hudiclient
?

hudicommon
?

hudihadoopmr
?

huditimelineservice
?

hudiutilities
49.71% <ø> (-19.94%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ies/exception/HoodieSnapshotExporterException.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../apache/hudi/utilities/HoodieSnapshotExporter.java
5.17% <0.00%> (-83.53%)
:arrow_down:

...hudi/utilities/schema/JdbcbasedSchemaProvider.java
0.00% <0.00%> (-72.23%)
:arrow_down:

...he/hudi/utilities/transform/AWSDmsTransformer.java
0.00% <0.00%> (-66.67%)
:arrow_down:

...g/apache/hudi/utilities/schema/SchemaProvider.java
71.42% <0.00%> (-28.58%)
:arrow_down:

...in/java/org/apache/hudi/utilities/UtilHelpers.java
40.69% <0.00%> (-23.77%)
:arrow_down:

...s/deltastreamer/HoodieMultiTableDeltaStreamer.java
76.19% <0.00%> (-2.21%)
:arrow_down:

...hudi/utilities/sources/helpers/KafkaOffsetGen.java
88.32% <0.00%> (-0.46%)
:arrow_down:

...java/org/apache/hudi/utilities/sources/Source.java
87.50% <0.00%> (ø)

...apache/hudi/utilities/sources/AvroKafkaSource.java
0.00% <0.00%> (ø)

... and 293 more

Continue to review full report at Codecov.

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

Hi @garyli1019 , can we land this? The Ci has passed now.


Helm colors don't have enough contrast

Using doom-vibrant there is very little contrast in helm. I'd greatly appreciate if the active row could have a slightly lighter background color and maybe adjust the text color. If the use of bold is disabled in the theme, then some selected helm items are indistinguishable from unselected items.
Here the first item is selected (see "1/6" in the mode line):

Here the third item is selected (see "3/6" in the mode line):

So here you can see that filenames are very slightly dimmer than directories and that selected directories are indistinguishable from unselected directories.
The background highlight as seen in company-mode pseudo tooltips seems excellent:

I just wanted to clarify something: I didn't investigate the other doom themes, it's possible this may apply to others.

My bad, this was certainly an oversight (I don't use helm). This did affect all Doom's themes, but this should be fixed now. Let me know if that isn't the case!

You're awesome, thank you!

can I ask what font you are using? thanks.


Create sgsadoveanu.txt

@monkey-1344 Please provide us with:

the school official website URL
the school street address, including city and country
an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course
a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

@monkey-1344 You might miss my previous comment. Please react.

@monkey-1344 I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the aforementioned issue. Thank you for your understanding!


[HUDI-7881] Verify table base path as well for syncing table in bigquery metastore

Change Logs
Unless the tables in bigquery metastore are explicitly deleted & recreated, updates to basepath don't come into effect. Through these changes, any updates in table base path would be identified and the same will updated in bigquery metastore without having to delete & recreate it.
Impact
Any updates in table base path would be identified and the same will updated in bigquery metastore without having to delete & recreate it.
Risk level (write none, low medium or high below)
Low
Documentation Update
NA
Contributor's checklist

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

Azure CI is green.


Changing link for array methods chapter and adding link for advanced …

…objects chapter to new chapters from the cohort-30 branch

I did a quick scan and it looks good! I'm not super familiar with these new chapters, so you might want to see if someone else sees anything that's missing. 👍

👍


locker bind to scope doesnt work as expected

.config(function (lockerProvider) {
  lockerProvider
      .setDefaultDriver('local')
      .setEventsEnabled(true)
})

.run(function ($rootScope, locker) {
   locker.bind($rootScope, 'session')
})

I expected that to mean "root scope and local storage are always in sync for session key even across browser tabs", but it actually meant "setting root scope session also sets local storage session".
Firebase for example initializes values and updates them when things change (https://www.firebase.com/docs/web/libraries/angular/api.html#angularfire-firebaseobject-bindtoscope-varname).

Yes, I have understood the service as so too. First who have to locker.get the value and assign it to the variable you want to bind. Can someone confirm?

Apologies for the late response.
I'm not exactly sure what the issue is here. I have created a demo on codepen here.
Any chance you could provide more context. i.e. the code that is run in the controller or something?
Thanks

I think @aj0strow means that he/she expected that by calling bind you are also watching for changes on the sessionStorage and do an initial sessionStorage.getItem when binding a property. Is this the case?

@eolognt the initial set seems fixed http://codepen.io/anon/pen/PqZOxy

Ok, that looks really nice. But I tested if locker watched for changes on the storage as well as the scope. This doesn't seem to be the case (test yourself by modifying localStorage through the console) and thus the values aren't in sync across browser tabs. This also seems to be the primary topic of this issue.
The way to implement this I think would be to listen on 'storage' events, that triggers every time a value for a key in the webstorage is changed or created: https://developer.mozilla.org/en-US/docs/Web/Events/storage And of course separate storage event triggered by locker on the current tab and those who are not.
Btw, why can you only bind values to the scope? I would find it useful to have this in services as well.

@eolognt yeah cross tab sync was the other half and doesn't work yet.
I'd imagine the reason for scopes only is the $watch method.

Ok, thanks for clearing that up guys :+1: I now see the issue..
@eolognt I will see if I can implement storage events, as you mentioned, to make sure things are in sync.
This fix will likely be the final thing for the 1.3 release
Cheers!

Also.. regarding binding to non scope keys...
@aj0strow is correct, without the $watch method. I would need to add a Object.observe()/ Object.watch() polyfill, which is a whole other thing.
I'm not going to rule it out though, as there are some nice little shims, such as this one.
Just concerned about bloating things too much

Tried a couple of things with this.. not 100% happy with the implementation so far...
Just released version 2.0.0 as I didn't want to hold things up too much more.
Going to look at trying to create a more elegant solution


Don't require routes.go generation

Allow loading of routes.yaml at application runtime.

Actually; this probably isn't feasible due to the lack of dynamic invocation...


something wrong when run the test cases

Thank you for bringing this to our attention. We have already noticed the issue and have been able to narrow it down. It relates to specific combinations of the native extension. As a workaround, using <lattice=Lattice(..., use-native=False)> should resolve the issue in the meantime.


Detail view

create a standard view "detail". this view is intended to be for a models view/update page.
Details
build context object that is broken into tabs, sections and columns. then have the template build the page from the context.

[ ] View Name Display

Requirements

[ ] Named tabs
[ ] Section single column
[ ] section dual column
[ ] edit button (details tab)
[ ] url qs monitors tab
[ ] model specifies column fields

added 3m of time spent

started a discussion on detail-view.png

mentioned in commit 904234c5818d893d63fc152e5f7b86d37226e122

added 1 design

updated 1 design

added 9m of time spent

started a discussion on detail-view.png

started a discussion on detail-view.png

mentioned in commit e517c5fd761e9f84dc589468da96b26979f6b33f

In GitLab by @jasonpagetas on Jul 12, 2024, 03:05
Adjust spacing on Teams page so that Notes are not directly under permissions. It just looks clustered.

added 30m of time spent

page layout will eventually look similar to devices with two columns.

mentioned in commit a2a8e1204649a27481862e85f8292a229e85fa97

marked this issue as related to #81


Download to?

What I don't get is where it downloads the games too and why there isn't already the ability to choose the location yourself, example being to download it to a games folder so you know where it's at in case you want to uninstall.

Nevermind I think i understand now, I just wasn't reading when it said it required the original games


Updated "Caching Ports"

According to this: https://support.cloudflare.com/hc/articles/218411427

Ports 80, 443, and 8080 are the only ports where Cloudflare Caching is available.

But this page states:

Ports 80 and 443 are the only ports compatible with:
HTTP/HTTPS traffic within China data centers for domains that have the China Network enabled, and
Proxying of Cloudflare Apps
Cloudflare Caching

According to this page itself, Port 8080 MUST be able to cache as it is listed as "HTTP ports supported by Cloudflare":

HTTP ports supported by Cloudflare

80
8080
8880
2052
2082
2086
2095

and not in the "Caching is disabled for the following ports" section.

Caching is disabled for the following ports

2052
2053
2082
2083
2086
2087
2095
2096
8880
8443

So should be pretty clear that the statement "Ports 80 and 443 are the only ports compatible with:" (Cloudflare Caching) cant be right, as they are not the only ones for "Cloudflare Caching". Please doublecheck and fix this as this can cause confusion.

Hi @MartinHotmann. Thank you for bringing this to our attention! We will be improving this documentation in the future, for now please refer to Network ports


Add Goto Location Action

This PR adds goto_location() action which allows to send the vehicle to a specific WGS84 global position. It uses MAV_DO_REPOSITION

How does this differ from the intention of offboard control? ie should this be the unimplemented position setting part of offboard control?

@hamishwillee Offboard does not have GPS setpoints. It's in local frame. So, conversions need to happen. Also, the flight controller already provides this functionality  without much coding.

It would be more correct to use double precision for lat/lon.

It would be more correct to use double precision for lat/lon.

@mhkabir that's only possible in COMMAND_INT. This is using COMMAND_LONG.

@julianoes I am not sure if PX4 uses COMMAND_INT to parse MAV_CMD_DO_REPOSITION.
So, in summary, what is required to merger this PR?

So, this is what I have so far.
ActionResult ActionImpl::goto_location(double latitude_deg, double longitude_deg, float altitude_amsl_m)
{

    MAVLinkCommands::CommandLong command{};

    command.command = MAV_CMD_DO_REPOSITION;
    command.target_component_id = _parent->get_autopilot_id();
    command.params.param1 = -1; /* default speed */
    command.params.param2 = MAV_DO_REPOSITION_FLAGS_CHANGE_MODE;
    // command.param4 = NaN /* Yaw Unchanged */
    command.params.param5 = (float)latitude_deg * 1E7F;
    command.params.param6 = (float)longitude_deg * 1E7F;
    command.params.param7 = altitude_amsl_m;

    return action_result_from_command_result(_parent->send_command(command));
}

Let me know your feedback.

@mzahana it looks to me like command int should be supported:
https://github.com/PX4/Firmware/blob/96995852cb6a2e2e23894c7ea05dd8385c595172/src/modules/navigator/navigator_main.cpp#L349-L351

@julianoes CommandInt is used and tested in SITL. Works fine.

@mzahana would be good if you could rebase this on develop and force push it.

@mzahana I hope you don't mind that I rebased and force pushed your branch. I also fixed the style issues and added an integration test.

@TSC21 are you ok if we merge this for now, and then follow up with the firmware issues.


Confirm before replacing HomeController in make:auth

Change
Confirm before overwriting HomeController.php class, when php artisan make:auth is executed.
Output
$ php artisan make:auth
....
The [HomeController.php] controller already exists. Do you want to replace it? (yes/no) [no]:
>

That's it!

See #22947 and #15653

Opps my bad! Thanks @devcircus for letting know.


Logging message for update document missing _id value

Hi,
Thanks for greate work.
I think the mistake in this line:
                    _log.Write(Logger.COMMAND, "update document on '{0}' :: _id = ", colName, id);
There no second argument placeholder {1} after _id =
Should be
                    _log.Write(Logger.COMMAND, "update document on '{0}' :: _id = {1}", colName, id);
Example:
06:36:30.7073 [COMMAND] create new collection 'Person'
06:36:30.7265 [COMMAND] insert document on 'Person' :: _id = 1
06:36:30.7495 [COMMAND] update document on 'Person' :: _id =
06:36:30.7725 [COMMAND] delete document on 'Person' :: _id = 1
06:36:30.7815 [COMMAND] insert document on 'Person' :: _id = 1
06:36:30.7835 [COMMAND] insert document on 'Person' :: _id = 2
06:36:30.7845 [COMMAND] insert document on 'Person' :: _id = 3
06:36:30.7856 [COMMAND] insert document on 'Person' :: _id = 4
06:36:30.7907 [COMMAND] update document on 'Person' :: _id =
06:36:30.7917 [COMMAND] update document on 'Person' :: _id =
06:36:30.7917 [COMMAND] update document on 'Person' :: _id =
06:36:30.7927 [COMMAND] update document on 'Person' :: _id =
Best Regards
Abdul-Rahman Ahmed

Thanks! I'm fixing this in master branch


WIP: Simplistic user-/character system

This PR is still WIP
A simple and extendable User- and Character system preparing:

Multiple User-Login methods, either before first spawn or during a game
Guest users (default, when no login is provided)
Each user can have

Username
Own character

After checkout, Users are not authorized, but get assigned different characters:

Odd Connection-IDs get bot.glb
Even Connection-IDs get bot.glb wearing a hat.

Limitations:

This is not load-tested beyond 10 concurrent users
There is currently weird issues when adding <m-model> duck to example-mml.html.

If the duck is there, no new users can log in (stuck ad Loading scren).
If the Duck is not there, users can connect normally. if the duck is added (w/o restart) when e.g. 4 users are connected, the duck appears for those four users and they can continue to play normally, but no new users can connect.
After the duck is removed form example-mml.html again (without restart), new users can connect again.
Since the characters are defined via <m-character> my current suspicion is towards a f*ckup in DOM. To be investigated

Multiple character-updates during an active connection have not been tested yet (should be possible with minor changes, will follow before making this PR final)

What kind of change does your PR introduce? (check at least one)

[ ] Bugfix
[x] Feature
[ ] Refactor
[ ] Tests
[ ] Other, please describe:

Thanks for picking this up! I've had a few thoughts myself about how to do this.
I think the main notes I have at this point are:

I agree with your approach of making this system extensible with the option of anonymous/pre/during auth methods. The thing I had in mind is that it would be good if the server that renders the page with the client on it could be responsible for generating a connection token that is then sent to the websocket as the first message before any communication actually occurs. This means that the auth could happen before the client is rendered and can be decoupled from the experience. It's up to the network server how to handle the validation of that token.

I think we'd like to support using arbitrary MML document URLs for each user and also the ability to update that along with other parts of your identity such as display name / more complex payload. I think you're on the same lines already with the USER_UPDATE message.

Happy to chat some more about this 👍

Thank you for the swift comment @MarcusLongmuir !

Happy to chat some more about this 👍
I pinged you on Discord - do you prefer a quick 1:1 discussion or shall we discuss here in the PR?

@tbergmueller. Thanks for the discussion. I think the main flow to get working is:
Assume the user has already completed an authentication step before they arrive at the HTML page that includes the 3d-web-experience client.

The server that renders the 3d-web-experience client HTML page generates a token (likely a JWT) that includes a user id, display name, and an MML character string/url. This token is then included on the page as a window property that is accessible to the client bundle. (e.g. window.USER_AUTH_TOKEN = "SOME.TOKEN"). This page is currently served (without injecting anything) by this line.

The client bundle finds the window property when it starts and uses this token as the payload of a first message to the websocket server (likely injected around here). The protocol is therefore changed to expect the user to send this first token message. If the server is configured to allow anonymous users then this token could be empty, but the message is still expected.

The server responds to the client with a message indicating which user id this client has, and sends an update to all clients that this new joiner client has connected and has a particular display name and MML character string. I think this can just be an extension of the IDENTITY_MESSAGE here.

The connecting client (and all others) receive this message describing the identity of the new joiner and associate the display name with the user id and load the MML character string (potentially using a cache if another user had already used this same URL).

I did a complete rewrite considering our discussions here in the PR and following our call / written discussions.
It is available here: https://github.com/mml-io/3d-web-experience/pull/122
I will close this PR.


Add Redwood 2L model

Description
Adds Redwood Attn only 2L model from https://www.alignmentforum.org/posts/j6s9H9SHrEhEfuJnq/causal-scrubbing-results-on-induction-heads
Fixes # 180
https://github.com/neelnanda-io/TransformerLens/issues/180
Type of change

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

Usage
Load in with
unprocessed_model = HookedTransformer.from_pretrained(
    "redwood_attn_2l",
    center_writing_weights=False,
    center_unembed=False,
    fold_ln=False,
)

The flag must be (False, False, False) or (False, True, False), because I'm getting bugs when I put these as True. MWE here: https://pastebin.com/mCVNpUWT :( - I would LOVE if someone could look into what's up here!
Putting the PR up so it doesn't get left for longer undone, but I'm frustrated I can't fix the issue. Maybe it's something to do with how this architecture has layer norms but no MLPs? Or shortformer-related?

Thanks @ArthurConmy, I'll try to recommend to anyone I know filling PRs :)

Hmm, I'm guessing they need to be false because shortformer? I believe it
adds the pos embed after the layernorm. While center writing weights
assumes pos embed writes to the residual stream. Ditto fold ln fails
because adding pos embed is between the ln weights being used and the W_Q
being used
On Sun, 19 Mar 2023, 9:12 pm Joseph Bloom, @.***> wrote:

Thanks @ArthurConmy https://github.com/ArthurConmy, I'll try to
recommend to anyone I know filling PRs :)
—
Reply to this email directly, view it on GitHub
https://github.com/neelnanda-io/TransformerLens/pull/204#issuecomment-1475398976,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASRPNKJVQPIURGEHTR2J5VTW45ZD3ANCNFSM6AAAAAAWAEYTYY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I think the correct solution is to raise a warning when this is tried if
the config says shortformer is being used, and force it to be false
On Sun, 19 Mar 2023, 10:20 pm Neel Nanda, @.***> wrote:

Hmm, I'm guessing they need to be false because shortformer? I believe it
adds the pos embed after the layernorm. While center writing weights
assumes pos embed writes to the residual stream. Ditto fold ln fails
because adding pos embed is between the ln weights being used and the W_Q
being used
On Sun, 19 Mar 2023, 9:12 pm Joseph Bloom, @.***>
wrote:

Thanks @ArthurConmy https://github.com/ArthurConmy, I'll try to
recommend to anyone I know filling PRs :)
—
Reply to this email directly, view it on GitHub
https://github.com/neelnanda-io/TransformerLens/pull/204#issuecomment-1475398976,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASRPNKJVQPIURGEHTR2J5VTW45ZD3ANCNFSM6AAAAAAWAEYTYY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thanks, looks great!


Show if feedback is outdated/being generated/not producible

Is your feature request related to a problem? Please describe.
Currently the feedback generation process gives too little feedback to instructor. For example feedback should be marked outdated if the submission was regraded. Futhermore the feedback should have a generating and failed state.
Describe the solution you'd like
Change feedback_available to feedback_status which is an enum with following values:

not_generated: feedback is not generated
generating: feedback is being generated
generation_failed: feedback could not be generated
feedback_outdated: feedback is outdated
generated: feedback was generated
This database change requires an alembic revision in the persistence layer and code changes where submissions are being used.

We have chosen not to incorporate "feedback_outdated" status this time, as we haven't found a suitable use case. Should there be a need or user requests in the future, we will add this option.


Fix typos in tdweb readme

Fix typos in tdweb readme, improve formatting.

Thanks. I will merge the changes to the next release.


Version Packages

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
<EMAIL_ADDRESS>Minor Changes

23f59b3 Thanks @Blackman99! - fix: ts not supported in +page.svelte

Patch Changes

fa9330d Thanks @Blackman99! - chore: update deps

<EMAIL_ADDRESS>Minor Changes

23f59b3 Thanks @Blackman99! - fix: ts not supported in +page.svelte

Patch Changes

fa9330d Thanks @Blackman99! - chore: update deps

<EMAIL_ADDRESS>Minor Changes

23f59b3 Thanks @Blackman99! - fix: ts not supported in +page.svelte

Patch Changes

fa9330d Thanks @Blackman99! - chore: update deps

This PR fix: #191


Not working with asyncapi file

It's not working with asyncapi file.
File name: moch-schema.yaml (also tried with asyncapi.yaml, same error)
Command used: OpenAPI Lint
Version used: 1.2.0

The OpenAPI Lint and Validate commands only work with OAS 2.0 and 3.0 files.
As per the README, only intellisense (as you type) mode is supported (for now) for AsyncAPI.

Ok, yes, IntelliSense works.
It's good if we can skip the error (underline) for the asyncapi file until it supported.


bug fix - sort order of property options within a set (e.g. on article detail page)

Clean Version of https://github.com/shopware/shopware/pull/1251
1. Why is this change necessary?
Property options are not displayed in the order provided in the backend on article's detail page
2. What does this change do, exactly?
Add the missing order-by to the related db query
3. Describe each step to reproduce the issue or behaviour.
Set up a couple of properties in the backend and try to sort them in a different order
4. Please link to the relevant issues (if any).
5. Which documentation changes (if any) need to be made because of this PR?
6. Checklist

[ x ] I have written tests and verified that they fail without my change
[ x ] I have squashed any insignificant commits
[ not needed ] This change has comments for package types, values, functions, and non-obvious lines of code
[ x ] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-19760.
Please use this issue to track the state of your pull request.

Hi @mkreusch! I tried to reproduce your issue by sorting the properties in the backend and checking the filters of some categories in the frontend. But it looks like the sorting of properties in the backend still isn't reflected there, even with this PR applied. Am I doing something wrong?

This PR was closed due to inactivity. If this change is still important to you, feel free to create a new pull request.
For more information about our contribution guidelines, see https://developers.shopware.com/contributing/contribution-guideline/.


Maven project

It seems that currently, the only "build system" used for the server is an Eclipse project. I think this should be structured as a Maven project so that we get all the goodies like IDE independence, automatic dependendy downloads etc.

Hi
How to install buddycloud server using windows system.
Thanks and Regards,
Anbarasan S

Hi @anbumca afraid I can't help you, you'll need to determine how to run a maven/java project on windows, maybe this would help https://maven.apache.org/guides/getting-started/windows-prerequisites.html


kubelet cgroup driver: "cgroupfs" is different from docker cgroup driver: "systemd"

There is something has been broken in upstream, since kubelets are now require additional configuration to use systemd cgroup driver:
failed to run Kubelet: misconfiguration: kubelet cgroup driver: "cgroupfs" is different from docker cgroup driver: "systemd"

One of possible solution is to add
cgroupDriver: systemd

to kubelet config

fixed in v0.10.0 by introducing KUBELET_EXTRA_ARGS_* and hardcoding --cgroup-driver=systemd in values.yaml
https://github.com/kvaps/kubefarm/commit/e4a31a16134e360f5084865f9ecfdbadb3848606


Added feature to display the pieces which pieces have been captured

The current functions check the current FEN of the board, finds the missing pieces and then displays the pieces below the buttons.

@Prashanth-Chandra Wow! Thank you for your contributions. I appreciate your efforts a lot. Merged!


[newrelic-logging] Specify logtype via Kubernetes API object metadata

Is your feature request related to a problem? Please describe.
According to New Relic documentation, a logtype attribute can be set on logs in order to parse them in a certain way (e.g. to automatically extract structured information from Nginx logs): https://docs.newrelic.com/docs/logs/log-management/ui-data/logs-parsing-built-rules-custom-parsing#logtype
Currently there seems to be no way to specify the logtype for logs originating from containers running on Kubernetes.
Describe the solution you'd like
I would like to be able to set this logtype attribute in the object metadata via Kubernetes API (e.g. something like metadata > annotations > "newrelic.com/logtype" = "nginx").
Describe alternatives you've considered
I do not see any way to achieve the result of parsing structured logs for containers running on Kubernetes with current New Relic capabilities.
Additional context
Originally asked as a question, but received no reply with a solution that would achieve the desired result: https://discuss.newrelic.com/t/kubernetes-helm-nri-bundle-logtype/120712
This might be somewhat related to #78 (they both are about using Kubernetes object metadata to influence New Relic log ingest behaviour).

This is someone a basic feature. I would like to see implemented

To work around a setup a custom parsing in the application ui targeting the containers in kubernetes.
If you going to implement it make sure to ignore the start of the messages because is getting from the docker container and not from kubernetes, all messges get prefixed with a "tiimestamp stdout F ".
In order to parse json a setup the following:
%{TIMESTAMP_ISO8601:containerTimestamp} stdout F %{GREEDYDATA:message:json}


Documentation Feature Request

Issue type: Documentation Feature Request

Python version: 2.7 --> 3.5
**NetBox version: 2.10 **

Documentation of steps taken to migrate from Py2 to Py3

Already submitted a pull request on a brief MD.

Closed by #1355


[WIP] Spark Applications for Cloud Bigtable

As per conversation with @igorbernstein2 and @kolea2 I'm pushing this Spark applications project for code review (and further refinement).

As discussed offline, we will merge this PR into https://github.com/GoogleCloudPlatform/java-docs-samples/tree/bigtable-spark-example and continue iterating on that branch


Modularizing the docs and updating some content

This is an automated message:
You can preview this docs PR at http://361.docs-pr.validatedpatterns.io
Note that they get generated every five minutes, so please wait a bit.


[changelog] Add bootstrap listener implementation to after image changelog consumer

[changelog] Add bootstrap listener implementation to after image changelog consumer
This PR adds bootstrap listener on regular changelog consumer and as well as specific record support.
User can override the listener bootstrap completed notification behavior to perform any action
How was this PR tested?

Added an integration test to verify the listener is working.
Does this PR introduce any user-facing changes?

[x] No. You can skip the rest of this section.
[ ] Yes. Make sure to explain your proposed changes and call out the behavior change.

Hi @FelixGV  thanks for the review! As discussed with our customer, we think this listener implementation is too complicated for single user to use and is an overkill. Instead a simple change in #1016 should just work for them. I believe that new PR is fairly easily and has addressed some of the comment you posted - list Java doc. If possible could you take a look at that PR?
I plan to close the current PR now.


Sync problems between hue app and homebridge

Issue
I've synchronization problems between the homebridge/homekit state and the state in the hue app.
The problem is not always reproducible, seems to be a timing issue.

Switch a light / a group on via homekit (e.g. with 100% brightness) -> Works as expected
Open the hue app and switch to a scene like "tropical lights" -> Works as expected
A second later the lights (automatically) changed back to 100% brightness -> Should not happen / Expected: Last state (hue)

It seems that the external state (hue) is overwritten by the homebridge/homekit state.
Log Messages
[9.1.2022, 14:42:18] [Hue] Esszimmer: group xy changed from [0.4633,0.3604] to [0.3972,0.388]
[9.1.2022, 14:42:18] [Hue] Esszimmer: set homekit hue from 53˚ to 42˚
[9.1.2022, 14:42:18] [Hue] Esszimmer: set homekit saturation from 11% to 33%
[9.1.2022, 14:42:18] [Hue] Wohnbereich: group all_on changed from true to false
[9.1.2022, 14:42:18] [Hue] Wohnbereich: group any_on changed from true to false
[9.1.2022, 14:42:18] [Hue] Wohnbereich: set homekit any on from true to false
[9.1.2022, 14:42:18] [Hue] Wohnbereich: group xy changed by ct from [0.3966,0.3863] to [0.3972,0.388]
[9.1.2022, 14:42:18] [Hue] Wohnbereich: set homekit color temperature from 197 mired to 273 mired
[9.1.2022, 14:42:18] [Hue] Group 1: group all_on changed from true to false
[9.1.2022, 14:42:18] [Hue] Group 1: set homekit on from true to false
[9.1.2022, 14:42:18] [Hue] Group 1: group any_on changed from true to false
[9.1.2022, 14:42:18] [Hue] Group 1: set homekit any on from true to false
[9.1.2022, 14:42:18] [Hue] Group 1: group xy changed from [0.4633,0.3604] to [0.3972,0.388]
[9.1.2022, 14:42:18] [Hue] Group 1: set homekit hue from 53˚ to 42˚
[9.1.2022, 14:42:18] [Hue] Group 1: set homekit saturation from 11% to 33%
[9.1.2022, 14:42:18] [Hue] Group 2: group all_on changed from true to false
[9.1.2022, 14:42:18] [Hue] Group 2: set homekit on from true to false
[9.1.2022, 14:42:18] [Hue] Group 2: group any_on changed from true to false
[9.1.2022, 14:42:18] [Hue] Group 2: set homekit any on from true to false
[9.1.2022, 14:42:18] [Hue] Group 2: group xy changed from [0.6021,0.3781] to [0.3972,0.388]
[9.1.2022, 14:42:18] [Hue] Group 2: set homekit hue from 53˚ to 42˚
[9.1.2022, 14:42:18] [Hue] Group 2: set homekit saturation from 11% to 33%
[9.1.2022, 14:42:18] [Hue] Küche: group all_on changed from true to false
[9.1.2022, 14:42:18] [Hue] Küche: group any_on changed from true to false
[9.1.2022, 14:42:18] [Hue] Küche: set homekit any on from true to false
[9.1.2022, 14:42:18] [Hue] Küche: group xy changed from [0.2913,0.2215] to [0.3972,0.388]
[9.1.2022, 14:42:18] [Hue] Küche: set homekit hue from 53˚ to 42˚
[9.1.2022, 14:42:18] [Hue] Küche: set homekit saturation from 11% to 33%
[9.1.2022, 14:42:18] [Hue] Couch: group all_on changed from true to false
[9.1.2022, 14:42:18] [Hue] Couch: group any_on changed from true to false
[9.1.2022, 14:42:18] [Hue] Couch: set homekit any on from true to false
[9.1.2022, 14:42:18] [Hue] Couch: group xy changed from [0.2913,0.2215] to [0.3972,0.388]
[9.1.2022, 14:42:18] [Hue] Couch: set homekit hue from 15˚ to 42˚
[9.1.2022, 14:42:18] [Hue] Couch: set homekit saturation from 85% to 33%
[9.1.2022, 14:42:18] [Hue] Sideboard: group all_on changed from true to false
[9.1.2022, 14:42:18] [Hue] Sideboard: group any_on changed from true to false
[9.1.2022, 14:42:18] [Hue] Sideboard: set homekit any on from true to false
[9.1.2022, 14:42:18] [Hue] Sideboard: group xy changed from [0.4633,0.3604] to [0.3972,0.388]
[9.1.2022, 14:42:18] [Hue] Sideboard: set homekit hue from 53˚ to 42˚
[9.1.2022, 14:42:18] [Hue] Sideboard: set homekit saturation from 11% to 33%
[9.1.2022, 14:42:23] [Hue] Philips hue: request 185: GET /groups
[9.1.2022, 14:42:23] [Hue] Philips hue: request 185: 200 OK
[9.1.2022, 14:42:23] [Hue] Wohnzimmer: group ct changed from 197 to 273
[9.1.2022, 14:42:23] [Hue] Wohnzimmer: set homekit color temperature from 197 mired to 273 mired
[9.1.2022, 14:42:23] [Hue] Esszimmer: group ct changed from 197 to 273
[9.1.2022, 14:42:23] [Hue] Esszimmer: set homekit color temperature from 197 mired to 273 mired
[9.1.2022, 14:42:23] [Hue] Group 1: group ct changed from 197 to 273
[9.1.2022, 14:42:23] [Hue] Group 1: set homekit color temperature from 197 mired to 273 mired
[9.1.2022, 14:42:23] [Hue] Group 2: group ct changed from 197 to 273
[9.1.2022, 14:42:23] [Hue] Group 2: set homekit color temperature from 197 mired to 273 mired
[9.1.2022, 14:42:23] [Hue] Küche: group ct changed from 197 to 273
[9.1.2022, 14:42:23] [Hue] Küche: set homekit color temperature from 197 mired to 273 mired
[9.1.2022, 14:42:23] [Hue] Couch: group ct changed from 197 to 273
[9.1.2022, 14:42:23] [Hue] Couch: set homekit color temperature from 197 mired to 273 mired
[9.1.2022, 14:42:23] [Hue] Sideboard: group ct changed from 197 to 273
[9.1.2022, 14:42:23] [Hue] Sideboard: set homekit color temperature from 197 mired to 273 mired

Debug Files
homebridge-hue (1).json.gz

This part of the log shows no brightness change, neither by Homebridge Hue, nor by the Hue app (or another Hue client).  Do the lights change physically or does only the state in HomeKit change?
You're exposing groups to HomeKit, instead of individual lights.  Are you also looking at the group in the Hue app, or at the individual lights?  Except for all_on and any_on, the Hue bridge maintains no group state.  The action mostly echoes the state of the last light changed, instead of the average group state.

Next try:
[10.1.2022, 06:45:08] [Hue] Philips hue: 13 accessories
[10.1.2022, 06:45:08] [Hue] masked debug info dumped to C:\Users\xobit\.homebridge/homebridge-hue.json.gz
[10.1.2022, 06:45:08] Initializing platform accessory 'Philips hue'...
[10.1.2022, 06:45:08] [Hue] Philips hue: 2 services
[10.1.2022, 06:45:08] Initializing platform accessory 'Wohnzimmer'...
[10.1.2022, 06:45:08] Initializing platform accessory 'Terrasse'...
[10.1.2022, 06:45:08] Initializing platform accessory 'Eingangstür'...
[10.1.2022, 06:45:08] Initializing platform accessory 'Esszimmer'...
[10.1.2022, 06:45:08] Initializing platform accessory 'Wohnbereich'...
[10.1.2022, 06:45:08] Initializing platform accessory 'Group 1'...
[10.1.2022, 06:45:08] Initializing platform accessory 'Group 2'...
[10.1.2022, 06:45:08] Initializing platform accessory 'Arbeitszimmer'...
[10.1.2022, 06:45:08] Initializing platform accessory 'HWR'...
[10.1.2022, 06:45:08] Initializing platform accessory 'Küche'...
[10.1.2022, 06:45:08] Initializing platform accessory 'Couch'...
[10.1.2022, 06:45:08] Initializing platform accessory 'Sideboard'...
[10.1.2022, 06:45:08] Homebridge v1.3.9 (HAP v0.9.8) (Homebridge 689F) is running on port 51653.
[10.1.2022, 06:45:08] [Hue] Philips hue: event stream connected to https://<IP_ADDRESS>/eventstream/clip/v2
[10.1.2022, 06:45:09] [Hue] Wohnzimmer: set homekit supported transition configuration to {"configuration":[{"iid":12,"characteristic":1},{"iid":14,"characteristic":2}]}
[10.1.2022, 06:45:09] [Hue] Terrasse: set homekit supported transition configuration to {"configuration":[{"iid":12,"characteristic":1},{"iid":14,"characteristic":2}]}
[10.1.2022, 06:45:09] [Hue] Eingangstür: set homekit supported transition configuration to {"configuration":[{"iid":12,"characteristic":1},{"iid":14,"characteristic":2}]}
[10.1.2022, 06:45:09] [Hue] Esszimmer: set homekit supported transition configuration to {"configuration":[{"iid":12,"characteristic":1},{"iid":14,"characteristic":2}]}
[10.1.2022, 06:45:09] [Hue] Wohnbereich: set homekit supported transition configuration to {"configuration":[{"iid":12,"characteristic":1},{"iid":14,"characteristic":2}]}
[10.1.2022, 06:45:09] [Hue] Group 1: set homekit supported transition configuration to {"configuration":[{"iid":13,"characteristic":1},{"iid":15,"characteristic":2}]}
[10.1.2022, 06:45:09] [Hue] Group 2: set homekit supported transition configuration to {"configuration":[{"iid":13,"characteristic":1},{"iid":15,"characteristic":2}]}
[10.1.2022, 06:45:09] [Hue] Küche: set homekit supported transition configuration to {"configuration":[{"iid":12,"characteristic":1},{"iid":14,"characteristic":2}]}
[10.1.2022, 06:45:09] [Hue] Couch: set homekit supported transition configuration to {"configuration":[{"iid":12,"characteristic":1},{"iid":14,"characteristic":2}]}
[10.1.2022, 06:45:09] [Hue] Sideboard: set homekit supported transition configuration to {"configuration":[{"iid":12,"characteristic":1},{"iid":14,"characteristic":2}]}
[10.1.2022, 06:45:34] [Hue] Couch: homekit on changed from false to true
[10.1.2022, 06:45:35] [Hue] Wohnzimmer: set homekit on from false to true
[10.1.2022, 06:45:35] [Hue] Wohnbereich: set homekit on from false to true
[10.1.2022, 06:45:39] [Hue] Couch: homekit on changed from true to false
[10.1.2022, 06:45:39] [Hue] Wohnzimmer: set homekit on from true to false
[10.1.2022, 06:45:39] [Hue] Wohnzimmer: set homekit any on from false to true
[10.1.2022, 06:45:39] [Hue] Wohnbereich: set homekit on from true to false
[10.1.2022, 06:45:39] [Hue] Wohnbereich: set homekit any on from false to true
[10.1.2022, 06:45:44] [BuschJaegerSysAp] Updating accessory Raumtemperaturregler with uuid ABB7F5967846ch0000
[10.1.2022, 06:45:44] [Hue] Wohnzimmer: set homekit any on from true to false
[10.1.2022, 06:45:44] [Hue] Wohnbereich: set homekit any on from true to false
[10.1.2022, 06:45:46] [Hue] Wohnzimmer: set homekit on from false to true
[10.1.2022, 06:45:46] [Hue] Esszimmer: set homekit on from false to true
[10.1.2022, 06:45:46] [Hue] Wohnbereich: set homekit on from false to true
[10.1.2022, 06:45:46] [Hue] Küche: set homekit on from false to true
[10.1.2022, 06:45:46] [Hue] Couch: set homekit on from false to true
[10.1.2022, 06:45:46] [Hue] Sideboard: set homekit on from false to true
[10.1.2022, 06:45:47] [BuschJaegerSysAp] Updating accessory Raumtemperaturregler with uuid ABB7F4FB6A30ch0000
[10.1.2022, 06:45:49] [Hue] Wohnzimmer: set homekit any on from false to true
[10.1.2022, 06:45:49] [Hue] Wohnzimmer: set homekit brightness from 100% to 78%
[10.1.2022, 06:45:49] [Hue] Wohnzimmer: set homekit hue from 39˚ to 15˚
[10.1.2022, 06:45:49] [Hue] Wohnzimmer: set homekit saturation from 53% to 85%
[10.1.2022, 06:45:49] [Hue] Esszimmer: set homekit any on from false to true
[10.1.2022, 06:45:49] [Hue] Esszimmer: set homekit brightness from 100% to 78%
[10.1.2022, 06:45:49] [Hue] Wohnbereich: set homekit any on from false to true
[10.1.2022, 06:45:49] [Hue] Wohnbereich: set homekit brightness from 100% to 91%
[10.1.2022, 06:45:49] [Hue] Group 1: set homekit on from false to true
[10.1.2022, 06:45:49] [Hue] Group 1: set homekit any on from false to true
[10.1.2022, 06:45:49] [Hue] Group 1: set homekit brightness from 100% to 78%
[10.1.2022, 06:45:49] [Hue] Group 1: set homekit hue from 39˚ to 18˚
[10.1.2022, 06:45:49] [Hue] Group 1: set homekit saturation from 53% to 74%
[10.1.2022, 06:45:49] [Hue] Group 2: set homekit on from false to true
[10.1.2022, 06:45:49] [Hue] Group 2: set homekit any on from false to true
[10.1.2022, 06:45:49] [Hue] Group 2: set homekit brightness from 100% to 78%
[10.1.2022, 06:45:49] [Hue] Group 2: set homekit hue from 39˚ to 15˚
[10.1.2022, 06:45:49] [Hue] Group 2: set homekit saturation from 53% to 85%
[10.1.2022, 06:45:49] [Hue] Küche: set homekit any on from false to true
[10.1.2022, 06:45:49] [Hue] Küche: set homekit brightness from 100% to 78%
[10.1.2022, 06:45:49] [Hue] Couch: set homekit any on from false to true
[10.1.2022, 06:45:49] [Hue] Couch: set homekit brightness from 100% to 78%
[10.1.2022, 06:45:49] [Hue] Sideboard: set homekit any on from false to true
[10.1.2022, 06:45:49] [Hue] Sideboard: set homekit brightness from 100% to 78%
[10.1.2022, 06:45:49] [Hue] Sideboard: set homekit hue from 39˚ to 18˚
[10.1.2022, 06:45:49] [Hue] Sideboard: set homekit saturation from 53% to 74%
[10.1.2022, 06:45:58] [Hue] Wohnzimmer: set homekit on from true to false
[10.1.2022, 06:45:58] [Hue] Esszimmer: set homekit on from true to false
[10.1.2022, 06:45:58] [Hue] Wohnbereich: set homekit on from true to false
[10.1.2022, 06:45:58] [Hue] Küche: set homekit on from true to false
[10.1.2022, 06:45:58] [Hue] Couch: set homekit on from true to false
[10.1.2022, 06:45:58] [Hue] Sideboard: set homekit on from true to false
[10.1.2022, 06:45:59] [Hue] Wohnzimmer: set homekit any on from true to false
[10.1.2022, 06:45:59] [Hue] Esszimmer: set homekit any on from true to false
[10.1.2022, 06:45:59] [Hue] Wohnbereich: set homekit any on from true to false
[10.1.2022, 06:45:59] [Hue] Group 1: set homekit on from true to false
[10.1.2022, 06:45:59] [Hue] Group 1: set homekit any on from true to false
[10.1.2022, 06:45:59] [Hue] Group 2: set homekit on from true to false
[10.1.2022, 06:45:59] [Hue] Group 2: set homekit any on from true to false
[10.1.2022, 06:45:59] [Hue] Küche: set homekit any on from true to false
[10.1.2022, 06:45:59] [Hue] Couch: set homekit any on from true to false
[10.1.2022, 06:45:59] [Hue] Sideboard: set homekit any on from true to false
[10.1.2022, 06:46:02] [Hue] Couch: homekit on changed from false to true
[10.1.2022, 06:46:03] [Hue] Wohnzimmer: set homekit on from false to true
[10.1.2022, 06:46:03] [Hue] Wohnbereich: set homekit on from false to true
[10.1.2022, 06:46:04] [Hue] Wohnzimmer: set homekit on from true to false
[10.1.2022, 06:46:04] [Hue] Wohnzimmer: set homekit any on from false to true
[10.1.2022, 06:46:04] [Hue] Wohnbereich: set homekit on from true to false
[10.1.2022, 06:46:04] [Hue] Wohnbereich: set homekit any on from false to true
[10.1.2022, 06:46:04] [Hue] Couch: set homekit any on from false to true
[10.1.2022, 06:46:06] [Hue] Couch: homekit brightness changed from 78% to 98%
[10.1.2022, 06:46:07] [Hue] Couch: homekit brightness changed from 98% to 100%
[10.1.2022, 06:46:07] [BuschJaegerSysAp] Updating accessory Raumtemperaturregler with uuid ABB7F5967824ch0000
[10.1.2022, 06:46:08] [Hue] Couch: homekit hue changed from 15˚ to 251˚
[10.1.2022, 06:46:08] [Hue] Couch: homekit saturation changed from 85% to 5%
[10.1.2022, 06:46:10] [Hue] Couch: homekit transition control set to {"colorTemperature":{"iid":14,"transitionParameters":{"<IP_ADDRESS>":"C4F33DA963C94C0F8B896C36A33EEF9E","startTime":"2022-01-10T05:46:10.964Z","<IP_ADDRESS>":"73D8252359D93D1D"},"runtime":1,"curve":{"entries":[{"adjustmentFactor":-1.144444465637207,"mired":412.4444580078125,"offset":0},{"adjustmentFactor":-1.1333333253860474,"mired":407.3333435058594,"offset":830000},{"adjustmentFactor":-1.1888889074325562,"mired":395.8888854980469,"offset":1800000},{"adjustmentFactor":-1.2999999523162842,"mired":385,"offset":1800000},{"adjustmentFactor":-1.4222222566604614,"mired":375.22222900390625,"offset":1800000},{"adjustmentFactor":-1.5333333015441895,"mired":367.3333435058594,"offset":1800000},{"adjustmentFactor":-1.600000023841858,"mired":360,"offset":1800000},{"adjustmentFactor":-1.6555556058883667,"mired":355.5555419921875,"offset":1800000},{"adjustmentFactor":-1.6777777671813965,"mired":352.77777099609375,"offset":1800000},{"adjustmentFactor":-1.6888889074325562,"mired":350.8888854980469,"offset":1800000},{"adjustmentFactor":-1.6888889074325562,"mired":349.8888854980469,"offset":1800000},{"adjustmentFactor":-1.6777777671813965,"mired":349.77777099609375,"offset":1800000,"duration":3600000},{"adjustmentFactor":-1.6888889074325562,"mired":349.8888854980469,"offset":1800000},{"adjustmentFactor":-1.6555556058883667,"mired":350.5555419921875,"offset":1800000,"duration":3600000},{"adjustmentFactor":-1.6111111640930176,"mired":352.1111145019531,"offset":1800000},{"adjustmentFactor":-1.5555555820465088,"mired":355.5555419921875,"offset":1800000},{"adjustmentFactor":-1.4666666984558105,"mired":358.6666564941406,"offset":1800000},{"adjustmentFactor":-1.3777778148651123,"mired":364.77777099609375,"offset":1800000},{"adjustmentFactor":-1.288888931274414,"mired":371.8888854980469,"offset":1800000},{"adjustmentFactor":-1.2333333492279053,"mired":382.3333435058594,"offset":1800000},{"adjustmentFactor":-1.244444489479065,"mired":397.4444580078125,"offset":1800000},{"adjustmentFactor":-1.3111110925674438,"mired":416.1111145019531,"offset":1800000},{"adjustmentFactor":-1.4555555582046509,"mired":439.5555419921875,"offset":1800000},{"adjustmentFactor":-1.6333333253860474,"mired":463.3333435058594,"offset":1800000},{"adjustmentFactor":-1.8333333730697632,"mired":487.3333435058594,"offset":1800000},{"adjustmentFactor":-2,"mired":508,"offset":1800000},{"adjustmentFactor":-2.0888888835906982,"mired":520.888916015625,"offset":1800000},{"adjustmentFactor":-2.0333333015441895,"mired":520.3333129882812,"offset":1800000},{"adjustmentFactor":-1.9777777194976807,"mired":519.7777709960938,"offset":1800000},{"adjustmentFactor":-1.8777778148651123,"mired":515.7777709960938,"offset":1800000},{"adjustmentFactor":-1.855555534362793,"mired":518.5555419921875,"offset":1800000},{"adjustmentFactor":-1.8111110925674438,"mired":512.111083984375,"offset":1800000,"duration":10800000},{"adjustmentFactor":-1.755555510520935,"mired":503.5555419921875,"offset":1800000},{"adjustmentFactor":-1.6666666269302368,"mired":490.6666564941406,"offset":1800000},{"adjustmentFactor":-1.5777777433395386,"mired":476.77777099609375,"offset":1800000},{"adjustmentFactor":-1.4777777194976807,"mired":462.77777099609375,"offset":1800000},{"adjustmentFactor":-1.355555534362793,"mired":447.5555419921875,"offset":1800000},{"adjustmentFactor":-1.244444489479065,"mired":433.4444580078125,"offset":1800000},{"adjustmentFactor":-1.1555556058883667,"mired":419.5555419921875,"offset":1800000},{"adjustmentFactor":-1.144444465637207,"mired":412.4444580078125,"offset":970000}],"adjustmentIid":12,"adjustmentRange":{"min":10,"max":100}},"updateInterval":60000,"notifyIntervalThreshold":600000}}
[10.1.2022, 06:46:10] [Hue] Couch: set homekit transition control to {"colorTemperature":{"iid":14,"transitionParameters":{"<IP_ADDRESS>":"C4F33DA963C94C0F8B896C36A33EEF9E","startTime":"2022-01-10T05:46:10.964Z","<IP_ADDRESS>":"73D8252359D93D1D"},"runtime":1}}
[10.1.2022, 06:46:10] [Hue] Couch: set homekit active transition count to 1
[10.1.2022, 06:46:10] [Hue] Couch: homekit adaptive lighting color temperature changed from 367 mired to 298 mired
[10.1.2022, 06:46:10] [Hue] Couch: set homekit transition control to {"colorTemperature":{"iid":14,"transitionParameters":{"<IP_ADDRESS>":"C4F33DA963C94C0F8B896C36A33EEF9E","startTime":"2022-01-10T05:46:10.964Z","<IP_ADDRESS>":"73D8252359D93D1D"},"runtime":1}}
[10.1.2022, 06:46:11] [Hue] Couch: set homekit hue from 251˚ to 41˚
[10.1.2022, 06:46:11] [Hue] Couch: set homekit saturation from 5% to 38%
[10.1.2022, 06:46:11] [Hue] Couch: set homekit transition control to {"colorTemperature":{"iid":14,"transitionParameters":{"<IP_ADDRESS>":"C4F33DA963C94C0F8B896C36A33EEF9E","startTime":"2022-01-10T05:46:10.964Z","<IP_ADDRESS>":"73D8252359D93D1D"},"runtime":265}}
[10.1.2022, 06:46:16] [Hue] Couch: homekit on changed from true to false
[10.1.2022, 06:46:19] [Hue] Wohnzimmer: set homekit any on from true to false
[10.1.2022, 06:46:19] [Hue] Wohnbereich: set homekit any on from true to false
[10.1.2022, 06:46:19] [Hue] Couch: set homekit any on from true to false
[10.1.2022, 06:46:27] [Hue] Wohnzimmer: set homekit on from false to true
[10.1.2022, 06:46:27] [Hue] Wohnbereich: set homekit on from false to true
[10.1.2022, 06:46:27] [Hue] Couch: set homekit on from false to true
[10.1.2022, 06:46:29] [Hue] Wohnzimmer: set homekit on from true to false
[10.1.2022, 06:46:29] [Hue] Wohnzimmer: set homekit any on from false to true
[10.1.2022, 06:46:29] [Hue] Wohnbereich: set homekit on from true to false
[10.1.2022, 06:46:29] [Hue] Wohnbereich: set homekit any on from false to true
[10.1.2022, 06:46:29] [Hue] Couch: set homekit any on from false to true
[10.1.2022, 06:46:29] [Hue] Couch: set homekit brightness from 100% to 48%
[10.1.2022, 06:46:29] [Hue] Couch: homekit adaptive lighting color temperature changed from 298 mired to 357 mired
[10.1.2022, 06:46:29] [Hue] Couch: set homekit color temperature from 357 mired to 298 mired
[10.1.2022, 06:46:29] [Hue] Couch: set homekit hue from 41˚ to 39˚
[10.1.2022, 06:46:29] [Hue] Couch: set homekit saturation from 38% to 51%
[10.1.2022, 06:46:34] [Hue] Wohnzimmer: set homekit any on from true to false
[10.1.2022, 06:46:34] [Hue] Wohnbereich: set homekit any on from true to false
[10.1.2022, 06:46:34] [Hue] Couch: set homekit on from true to false
[10.1.2022, 06:46:34] [Hue] Couch: set homekit any on from true to false
[10.1.2022, 06:46:34] [Hue] Couch: set homekit color temperature from 298 mired to 357 mired

The lights change physically.
Now I can reproduce it reliably:

Switch any light on and change the brightness or color in Homekit
Change the setting in hue app
Hue setting is overwritten with homekit state (a second later). (at the end of the log above)

It seems that homekit always wins.

Next time, please attach a logfile.
You didn’t run Homebridge in DEBUG, so the API calls Homebridge Hue makes aren’t listed, but I think I see a hint of what’s going on.  You have adaptive lighting enabled on the groups.  So when the Hue bridge reports a change of the group, which is actually a change of the state of one of the lights in that group, Homebridge Hue adjusts the group accordingly.

Sorry. Do you need more information or can I just disable adaptive lightning for groups somewhere? I only need homekit for automations like "Good morning" and "Good night" and use the Hue app for the rest.

Adaptive lighting can only be enabled from Home, by activating the corresponding scene (preset).  It’s disabled by activating another scene in Home.  It is disabled automatically by Homebridge Hue when the light’s colour has changed, but Homebridge Hue currently doesn’t do that for a manual change in colour temperature.
Basically, exposing Hue bridge groups to HomeKit only makes sense, when all lights in that group always should have the same state.  I’m not sure even sure exposing adaptive lighting on groups was a good idea; tbh, I never tested this myself.

In case of automations like "good morning" all lights of a group should have the same state (on, 100%).
In case of hue scenes all lights of a group can have different states.
Would it fix the problem if I would change the automations from group to specific lights and disable exposing groups at all?

I think it would.  The problem is not so much exposing a group, as it is basing automations, or enabling adaptive lighting, on a group.  Especially when those automations act on the same group, and you might want member lights to have different states.
A Zigbee group is basically write-only.  Technically, it’s just a multicast address to which a light subscribes, rather than a virtual device that maintains state, as presented by the Hue or deCONZ API.
Likewise, a Zigbee scene is just an ID, under which each light stores its target state.  That’s why it’s so damn efficient: the bridge/gateway only broadcasts (multicasts) the scene ID, rather than having to sending the target state for each individual light.
The deCONZ API treats the group action pretty much as write-only, just echoing the last values written to it.  The Hue API, on the other hand, updates the group action with the most recently received changed (?)state of a member light.  This causes issues if you base HomeKit automations on the group “state” when it doesn’t reflect the state of each light in the group.  Especially when those automations subsequently update the group action, forcing the same state to all member lights.  And this is exactly what adaptive lighting does: updating the ct on changed bri (and periodically as well).

Sorry, wrong button.

Thanks for the detailed explanation.
I removed the groups but still got the issue, also with single lights.
After adjusting the scenes "good morning" and "good night" from adaptive lighting to "normal" on/off it works as expected and the hue state is not longer overwritten.
If I'm honest I wasn't aware of adaptive lighting before. I just configured any bright color to get awake in the morning and I don't need adaptive lighting at all.
Thanks for the quick feedback and help, really appreciate it.


Load content when accordion is pressed

Is it possible to show accordion content when it is pressed? I want to load some dynamic data on content. It seems its calling header and content every time when I press to any tab. Pls help @oblador

I have the same problem!

Currently no, the content needs to be rendered for the component to know the height. It would probably be possible with static content, but if you're loading it asynchronously that's a harder problem as the height will change, potentially mid animation.

Check #52

Hey, this issue has been inactive for long time and will be closed. If the issue still persists feel free to tag me to reopen.

Hi @iRoachie ,
I am facing same issue, i want to load dynamic content on header is pressed. can you please guide me how to do it.
Thanks in advance.

@preetampatil3d There's a PR #52 that supposedly fixed it but it needs some revisions. You can try using that fork and see if it works for you

Hi @iRoachie , Thanks for quick response. but #52 is about dynamic height. i am talking about content.
https://stackoverflow.com/questions/45541989/best-accordion-for-react-native-for-dynamic-content

If i’m not mistaken that PR is about recalculating the height of the collapsible with when the height of the content changes.


docs wrongly indicate baptiste preview is functional on repo list endpoints

I'm re-opening this ticket as this is a docs issue, not a support issue.
the apis simply do not operate as described in the docs.
the endpoints: GET /users/{username}/repos and GET /orgs/{org}/repos both do not respond with the template_repository in the real world.
Proof
Testing that the correct Accept header is used:
expected result: null values for is_template
http https://api.github.com/users/ahmadnassri/repos?per_page=100 "Authorization: token $GH_TOKEN" | jq .[].is_template

expected result: some repos will return true, the rest are false
This Works
http https://api.github.com/users/ahmadnassri/repos?per_page=100 "Authorization: token $GH_TOKEN" "Accept: application/vnd.github.baptiste-preview+json" | jq .[].is_template

so, now that we can confirm we're making the correct API calls, and setting the correct headers, now lets try to look for template_repository property:
here's an example you can run yourself, using httpie and jq
http https://api.github.com/users/ahmadnassri/repos?per_page=100 "Authorization: token $GH_TOKEN" "Accept: application/vnd.github.baptiste-preview+json" | jq '.[] | { name: .name, should_have_template_repository: .name | startswith("js-"), template_repository: .template_repository, should_have_is_template: .name | startswith("template-"), is_template: .is_template }'

this is relying on the naming schema I strictly follow for my repos, specifically, repos that start with template- are template repositories, and for the purpose of this test, repos that start with js- are repositories that were initialized with a template repository, and the GitHub UI correctly reflects this, however it's not present in the API.
I've run this on my own public repos, and anybody can see those same results, as well as on private orgs, so both documentation for orgs and users are wrong.
here are the results:
{
  "name": "js-restful-core",
  "should_have_template_repository": true,
  "template_repository": null,
  "should_have_is_template": false,
  "is_template": false
}
{
  "name": "js-restful-json",
  "should_have_template_repository": true,
  "template_repository": null,
  "should_have_is_template": false,
  "is_template": false
}
{
  "name": "js-restful-node",
  "should_have_template_repository": true,
  "template_repository": null,
  "should_have_is_template": false,
  "is_template": false
}
{
  "name": "js-restful-request",
  "should_have_template_repository": true,
  "template_repository": null,
  "should_have_is_template": false,
  "is_template": false
}
{
  "name": "js-restful-xhr",
  "should_have_template_repository": true,
  "template_repository": null,
  "should_have_is_template": false,
  "is_template": false
}
{
  "name": "template-docker",
  "should_have_template_repository": false,
  "template_repository": null,
  "should_have_is_template": true,
  "is_template": true
}
{
  "name": "template-js-lib",
  "should_have_template_repository": false,
  "template_repository": null,
  "should_have_is_template": true,
  "is_template": true
}
{
  "name": "template-node-lib",
  "should_have_template_repository": false,
  "template_repository": null,
  "should_have_is_template": true,
  "is_template": true
}
{
  "name": "template-template",
  "should_have_template_repository": false,
  "template_repository": null,
  "should_have_is_template": true,
  "is_template": true
}

The Issue
The docs clearly show the wrong example for listing user repos:

and again with listing org repos:

The API in the real world does not provide these functionality, so the documentation is wrong.
if you believe the API should be providing this functionality, then perhaps that's an internal discussion for your team ... asking me to contact customer support and report an issue is not the appropriate path, you're advertising capabilities in your API through the docs that do not exist... so the first place is to fix the docs so they are reflective of what is actually available ..
once that's done, we the users of your platform, would have a better understanding of what's available and what is functional, instead of doubting our sanity and wasting hours of in debugging our own work, because the docs clearly state something should work (but it doesn't)
thank you.

Thanks for opening a new issue and giving so much additional context @ahmadnassri! I'll triage this for the team to take another look 👀

@ahmadnassri Thanks for bringing this to our attention--and thanks especially for the detailed issue body! I have verified what you reported. I am confirming internally that this is the expected behavior and will let you know what I learn.

thank you both @janiceilene @skedwards88

@ahmadnassri I checked in with our engineering team, and the docs are incorrect. Only GET /repos/{owner}/{repo} returns template_repository. (The other examples that include template_repository are incorrect.) Additionally, all endpoints that include is_template in their example response require the baptiste preview. This needs to be fixed internally, so I will close this issue and open an internal issue. Thank you for catching this error! ✨

would you post here when the corrections have been made public?


how to convert Tewi for using as *.psf consolefont?

I know about bdf2psf tool but have problem with converting:
bdf2psf --fb Tewi-normal-11.bdf /usr/share/bdf2psf/standard.equivalents /usr/share/bdf2psf/useful.set 512 Tewi-normal-11.psf

/usr/bin/bdf2psf: Tewi-normal-11.bdf: the width is not integer number.

any advice? Thanks.

This apparently doesn't work anymore.

I had the same problem with my font miniwi, and I fixed it by hardcoding the font size in bdf2psf perl file.
This worked for me, and I maybe it could work for tewi font as well.

In adition, it may be possible to use the conversion toolchain from terminus font, generating the terminus font worked for me by following the readme (basically make command).
[Download]

@sshbio thanks

I got psf generation to work, and here is how I did (I will improve the psf version soon):

Downloaded bdf2psf
Extracted it
cd to the usr/bin/ path
ran this command:

./bdf2psf --fb ~/dot/fonts/tewi-font/tewi-medium-11.bdf ../share/bdf2psf/standard.equivalents ../share/bdf2psf/ascii.set 512 /tmp/tewi.psf

Then in text mode (TTY, linux console), I ran setfont /tmp/tewi.psf and it worked for the ASCII characters.
To add more than ascii characters (what I am currently doing).

I improved the psf font again and updated my previous message with the details in #18.
To build it, I cd to this dir, and then run this script.
One may need to adapt the path to run it on its machine.
tewi.psf

I may steal some of the scripts and put them in this repo.

Great, let me know if you need any kind of any help for anything,  :)


Receiving error when initializing new developer experience as of 02162017

was working fine the 15th. not sure what happened but the extension in vs code is no longer available.
2:48:36 PM New Developer Experience Installation succeeded
2:57:22 PM Read Settings
2:57:23 PM Import Modules
2:57:23 PM Downloading Visual Studio Code Setup Program
2:57:26 PM Installing Visual Studio Code
2:58:42 PM Remove and add http binding for local access using Windows Auth
2:58:43 PM Setup NetTcpPortSharing
2:58:45 PM Create Developer Service Tier
2:58:46 PM Download samples
2:58:47 PM install vsix
2:58:47 PM C:\DEMO\New Developer Experience\al-0.2.7308.vsix
2:58:50 PM WARNING: Promise with no error callback:12
2:58:50 PM { exception: null,
2:58:50 PM   error: [ [ [Object] ] ],
2:58:50 PM   promise:
2:58:50 PM    { _oncancel: null,
2:58:50 PM      _nextState: null,
2:58:50 PM      _state:
2:58:50 PM       { name: 'error',
2:58:50 PM         enter: [Function: enter],
2:58:50 PM         cancel: [Function: a],
2:58:50 PM         done: null,
2:58:50 PM         then: null,
2:58:50 PM         _completed: [Function: a],
2:58:50 PM         _error: [Function: a],
2:58:50 PM         _notify: [Function: m],
2:58:50 PM         _progress: [Function: a],
2:58:50 PM         _setCompleteValue: [Function: a],
2:58:50 PM         _setErrorValue: [Function: a] },
2:58:50 PM      _listeners: null,
2:58:50 PM      _value: [ [Object] ],
2:58:50 PM      _isException: false,
2:58:50 PM      _errorId: 12,
2:58:50 PM      done: [Function: done],
2:58:50 PM      then: [Function: then] },
2:58:50 PM   handler: undefined,
2:58:50 PM   id: 12,
2:58:50 PM   parent: undefined }
2:58:50 PM Create Desktop Shortcuts
2:58:50 PM Cleanup
2:58:50 PM Start VS Code with the Hello World app
2:58:50 PM New Developer Experience Installation succeeded

Does it work if you create a new VM from the official link aka.ms/navdeveloperpreview?

yep that works. thanks.


RTSP session issue with EvoStream

During the SETUPpart, the player, send two requests directly with no session. Then the server should open two separate session and the player will keep using one session per stream. Not sure if this is correct or not, but it doesn't work with EvoStream. In fact EvoStream wants only one session. If you try to open two sessions, the second request is never answered (even if we do the SETUP sequentially).
In order to make it work we should first SETUP one track, wait for the response, and use the session in this first response for all next requests (including the next(s) SETUP). This is at least how it is implemented in VLC and in Locomote.
I modified a little bit my fork to have only one session and it works great but I'm not sure if this will break the compatibility with other servers.
Do you mind if I create a PR to use only one session across all streams (tracks) ?

Yes, you can PR. I had noticed same behavior on somewhat other stream. But I thought it was fixed

It's really strange because when you look at the RFC2326 chapter 12, it's look like the Session field should not appear in SETUP. And at chapter 10.4 it is said that the server can refuse to bundle session. But by saying so, it means that we can bundle session... I'm a bit confused

PR is merged, I close this issue


Unwinds elasticsearch-http configuration by using List

Before, we had to pass around more state in order to set OkHttp
interceptors used in elasticsearch (ex AWS authentication). This
injects List<Interceptor> so that the process is a bit easier.

cc folks who might be curious @llinder @sethp-jive and @shakuzen who mentioned to me the list approach

whoohoo no test flake


Lot No. Information Table 6505 - add default fieldgroup DropDown

Good morning everyone,
can you please add the default dropdown fieldgroup to the lot no. information table, in order to add some custom fields?
Kind regards.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


moving to ReactJS

what reactjs slick lib could best substitute this one?

There is something called react-slick.

Can this kenwheeler slick-carousel be used with react though? I know they have an npm installation. Just checking in case I want to use this one instead of the react-slick one.


Null check operator used on a null value

After scanning the QR, I get this error in the console. Can you help me?
mobile_scanner: ^1.1.1

Thank you ✨


No FileBag in Request

Expected Behavior
Upload and Picture should return FileBag in Request so that can be retrieved for attachement via File($request->file('photo')); But It returns NULL
Actual Behavior

Specifications

ORCHID Version: 5.5.5
Laravel Version: 5.8
PHP Version: 7.3.8
Database Version: 8.0.16

Direct loading occurs through Ajax.
Both of these fields return attachment table entries.
You can get around this using:
Input::make('photo')->type('file')

But I see no reason to do so?
Do you want to process the file before downloading it?
Or why do you want to capture him?

Besides processing I want to capture it so that I can attach it to Attachement

To get attachment:
use Orchid\Attachment\File;

public function upload(Request $request)
{
    $file = new File($request->file('photo'));
    $attachment = $file->load();

}


detach opened program from felix

Hello, I thanks a lot for this really geat utility.
I've been using it a lot recently and the one disadventage that I find to it is the fact that the opened process depends on felix staying opened
i.e. : If I open some .pdf file with libreoffice or zathura using felix and then close felix, libreoffice is terminated as well.
This whether Enter or :o has been used to open the file.
I believe felix would be even more useful if either :

opened process "swallowed" felix instance, therfore hiding it, and not allowing it to be closed but I'm afraid this is a window manger feature
or
opened process was separated from felix process, therefore not requiring felix to run in the background. This is what happens with ranger (https://github.com/ranger/ranger) but not with joshuto (an another rust program)

I might have missed something in the config file and if so sorry for the annoyance, otherwise I am happy to help with some testing but my coding skills are non existent.
Thanks again for your time !

Hm, weird. In my environment, by setting [exec] in config.yaml like following...
exec:
  zathura:
    [pdf]

and by pressing o on the item you'd like to open by that command, the new window appears and even if felix/terminal is closed, that window remains open.
Could you tell me your environment and the version of felix (which you can check by fx --version)? Mine is below:
OS: Arch Linux x86_64
Kernel: 6.0.9-arch1-1
WM: i3
Terminal: alacritty

Hello, so here is my system and it appears that both are very similar, only signicative difference probably beaing wayland vs X11
OS: Void Linux x86_64
Kernel: 6.0.9_1
WM: sway
Terminal: alacritty
felix v2.1.0: Up to date.
So i I tried opening zathura and then closing felix on i3 WM, and issus is the same.
So issue probably comes from config,
here is the relevant part of mine
``
default: nvim
exec:
feh:
["jpg", "jpeg", "png", "gif", "svg"]
zathura:
["pdf"]
libreoffice:
["ods", "odt", "odp", "odg", "xlsx", "docx", "dotx", "pptx"]
``
so tried removing this part and only using
exec:   zathura:     [pdf]
And the issue remaines
No idea of what to do next for nom

Thanks for the detail!
The spawned process may wok differently in Wayland. I will look into it.

I don't have Wayland environment, but PR #152 may fix this issue. Could you test it?
git clone https://github.com/kyoheiu/felix
cd felix
git checkout feature-nix-fork
cargo run

Or if you have gh, gh pr checkout 152 just works.

Just got to testing it,
Using this method :
git clone https://github.com/kyoheiu/felix cd felix git checkout feature-nix-fork cargo run
it works perfectly using system described above, thanks a lot !

merged #152


guided diffusion with external guidance function

#158 This pr contributes a guided version of diffusion models. For example, classifier guidance.

It is annoying to have a pre-trained classifier as guidance. Nonetheless, a classifier is not a necessity. The key idea of guided diffusion is that the generation can be controlled by a function, which could be anything in essence, as long as it constrains the sample. I am experimenting this feature.

@pengzhangzhi hey this looks great Zhangzhi! graciously accept :pray:


Add workflow_call as workflow trigger

I want to run the CDK workflow as a job inside of another workflow. This should be possible by having a trigger workflow_callin the CDK workflow. However, it currently doesn't seem possible to add this via Typescript code.
I don't want to run the CDK workflow on its own, because I want to run e.g. tests first and do other deploy related things afterwards. All in a different existing workflow file which should not be coupled to CDK code.
This issue is also be possibly related to #293 which would allow for such customization I guess.

Hi @webjunkie! Yes, #293 escape hatching is my #1 priority in this module to allow for any such customizations. I'm a bit busy at the moment but I have this feature request ear-marked for when I have a bit of free time.

#340 should unblock this request, so I'm marking this as a p2. However, if you're interested in modeling this out in the workflows-model.ts file, I'd be happy to take a contribution. I think its just out of date and we don't have an automated way to keep up to date I don't think.


updated gitignore, the Dockerfile, the .yml and updated requirements.txt

did the things in the title

Nice! This compiles great on my machine


Problem when using the percentage sign %

Hello!
There seems to be a calculation issue when using % for decimals. (in engineering, strain is sometimes recorded as %)
I'm not sure if it's worth considering. The following image is provided for reference:

Hi!
Thank you very much for reporting this. It is a serious issue and is definitely worth paying attention to it.
I will take a look now and fix it.

Hi, Ned!
I did some quick tests and the problem is probably related to pow function:

I didn't check the code yet, but maybe it would be necessary to just change the % "unit" to its real value "0.01" before the calculation, no?

Hi! Thank you very much for your effort. The feadback you provided is very valuable to find where the problem is. Can you please also post the code you used to generate this output? This will save some time to me.

Hi! Here is the code I used:
a = 3.3%
b = 0.033
a - b
b - a
a ≡ b
a^1
b^1
a^1 - b^1
b^1 - a^1
a^1 ≡ b^1
sqrt(a)
sqrt(b)
c = 1‰
d = 0.001
c ≡ d
c^1
d^1

Great! Thank you so much! I will come back soon...

If you change the line 1689 of Calcpad.Core/BaseTypes/Unit.cs file to:
var result = (u*u.GetDimensionlessFactor()).Pow((float)d) / u.GetDimensionlessFactor();
or
var result = u.Pow((float)d) * u.GetDimensionlessFactor().Pow(((float)d)-1.0);
(or something like that)
Would that fix the problem? Of course you would need to do something similar to root function.
(I'm sorry. I can't test my suggestion at the moment...)

Hi!
I think I fixed it. Also added cbrt, root and everything that can be affected. It seems to me that everything works now, but please also try by yourself. I haven't still issued a release. You can use the source code or download and reinstall it from here:
https://github.com/Proektsoftbg/Calcpad/blob/main/Setup/calcpad-VM-setup-en-x64.zip
Uninstall the old version before that, just for case.

OK. I also tried to make a and b vectors and matrices and it also works. If you cannot find any other problems, I will issue a new release with these fixes. Even, if any, we can always fix them in the future. :)

It’s working fine now, thanks. :)


asn1.go isPrintable func does not play well with @ char

I am currently working on porting an internal https based service that uses client certificates to establish secure connections and am running into problems where the client certificate fails to be parsed by tls.X509KeyPair(cert, key) because the char @ is used in the client certificate... With current master, X509KeyPair returns error PrintableString contains invalid character
Quick fix: (asn1.go isPrintable func)
b == '*' ||
b == '@'

But not sure how well this will be accepted. Please advice. Thanks.

ASN1 PrintableStrings must not contain @, https://en.wikipedia.org/wiki/PrintableString.
Can you please explain more about your problem, preferably showing code or a failing test case.

The client certificate I was given to use has a @ in the PRINTABLESTRING :commonName
e.g.
(output from openssl asn1parse -in client_cert.pem)
  367:d=3  hl=2 l=  32 cons: SET
  369:d=4  hl=2 l=  30 cons: SEQUENCE
  371:d=5  hl=2 l=   3 prim: OBJECT            :commonName
  376:d=5  hl=2 l=  23 prim: PRINTABLESTRING   :BLAH BLAH @US SOFT CA v3

It's interesting how other libs and langs handle this ugly issue gracefully. I've tried: curl, objective-c, nodejs, php, and openssl s_client and they all seem to be parsing the the cert without strictly validating the strings. I can easily change the encoding type in the binary blob from 0x13 to 0x0c but that will change the cert signature and decryption of data will fail at a later point. Any ideas?

I think the go behaviour is correct, and arguments that other languages don't validate don't really feel appropriate where security is involved.
/cc @agl

I totally agree.

Can you get a valid certificate?
In general we don't want to cater to all possible ways a certificate might be broken. If this kind of thing is endemic in the wild then we might make an exception, but if it's just a one-time mistake, it's not appropriate for the Go standard library to sanction it.
It sounds like you know a workaround (recompile your version of Go).
Unless there is evidence this kind of problem affects many many users, I think we'll stick with spec compatibility.

Unfortunately, I can't get a valid certificate :unamused: But anyways, deff stick with spec compatibility... I don't expect an exception for a single anomaly. Thanks for the support.


Use dummy values in sample.env

Looked like we had legit values in our sample.env? Made some changes and reflected it in the README.
Also, I really think we should be closing: https://github.com/Shopify/example-ruby-app/pull/14

Is .env meant to live in the root, or in both Getting Started and Charging For Your App?

The .env file actually has fake credentials in it (there's no API client associated with that API key), I just put those in as an example.
.env is meant to live in root for now and the examples are meant to be invoked from the root directory like so ruby 01 Getting Started/app.rb
Everything else LGTM though!


CUDA error when installing with non-local pip install

This error does not occur with local install (pip3 install -e .), however, occurs with remote install (pip3 install tmu):
2023-04-17 06:40:30,320 - tmu.models.classification.vanilla_classifier - DEBUG - Initializing clause bank....
Traceback (most recent call last):
File "./examples/experimental/classification/IMDbWordPredictionConvolutionDemo.py", line 125, in
tm.fit(X_train, Y_train)
File "/home/oleg/.local/lib/python3.8/site-packages/tmu/models/classification/vanilla_classifier.py", line 148, in fit
self.init(X, Y)
File "/home/oleg/.local/lib/python3.8/site-packages/tmu/models/classification/base_classification.py", line 32, in init
self.init_clause_bank(X, Y)
File "/home/oleg/.local/lib/python3.8/site-packages/tmu/models/classification/vanilla_classifier.py", line 126, in init_clause_bank
self.clause_banks = [clause_bank_type(**clause_bank_args) for _ in range(self.number_of_classes)]
File "/home/oleg/.local/lib/python3.8/site-packages/tmu/models/classification/vanilla_classifier.py", line 126, in
self.clause_banks = [clause_bank_type(**clause_bank_args) for _ in range(self.number_of_classes)]
File "/home/oleg/.local/lib/python3.8/site-packages/tmu/clause_bank/clause_bank_cuda.py", line 92, in init
mod = load_cuda_kernel(parameters, "cuda/calculate_clause_outputs_predict.cu")
File "/home/oleg/.local/lib/python3.8/site-packages/tmu/clause_bank/clause_bank_cuda.py", line 55, in load_cuda_kernel
with path.open("r") as f:
File "/usr/lib/python3.8/pathlib.py", line 1222, in open
return io.open(self, mode, buffering, encoding, errors, newline,
File "/usr/lib/python3.8/pathlib.py", line 1078, in _opener
return self._accessor.open(self, flags, mode)
FileNotFoundError: [Errno 2] No such file or directory: '/home/oleg/.local/lib/python3.8/site-packages/tmu/clause_bank/cuda/calculate_clause_outputs_predict.cu'

Will investigate. I believe this is because the cuda kernels are not registered as assets during install, and is then simply omitted during install

Great :-)

@olegranmo Could you try the following:
create a MANIFEST.in in the root directory with the following contents:
recursive-include tmu/clause_bank/cuda *.cu

Inside setup.py, include the following argument include_package_data=True,

Solved the problem - thanks!


restart celery tasks on change

fixes #1110

Thanks! I added --autoreload in https://github.com/mozilla/olympia/pull/1119 but it doesn't seem to be working. I'll put more info in the issue.


fix: maintain dependabot config filename for existing configs

Pull Request

Proposed Changes

In order for us to handle existing configuration files properly, we need to ensure we are making a pull request against the existing configuration and not a new file. This is occurring currently when the file dependabot.yml has a slightly different extension (.yaml).
Minor Changes:
Updates to GitHub Token and Commit Message:

README.md: The GH_TOKEN description is updated to specify that it must also have repo:write and workflow privileges to create a pull request.
env.py: The default commit message is changed from "Create dependabot.yaml" to "Create/Update dependabot.yaml".

Most significant changes:
Changes in dependabot_file.py:

The function make_dependabot_config now takes an additional indent parameter to control the indentation of the generated dependabot.yaml content.
The build_dependabot_file function has been updated to calculate the indentation based on the existing dependabot.yaml file, if it exists.
The build_dependabot_file function now passes the calculated indent to make_dependabot_config when adding new package managers to the dependabot.yaml file. [1] [2] [3]

Changes in evergreen.py:

The main function now keeps track of the filename of the existing dependabot.yaml file, if it exists.
The filename of the dependabot.yaml file is now included in the issue body when creating an issue.
The commit_changes function now takes additional parameters for the filename of the dependabot.yaml file and the existing configuration. If the configuration exists, it updates the file; otherwise, it creates a new one. [1] [2]

Readiness Checklist
Author/Contributor

[x] If documentation is needed for this change, has that been included in this pull request
[x] run make lint and fix any issues that you have introduced
[x] run make test and ensure you have test coverage for the lines you are introducing
[x] If publishing new data to the public (scorecards, security scan results, code quality results, live dashboards, etc.), please request review from @jeffrey-luszcz

Reviewer

[x] Label as either fix, documentation, enhancement, infrastructure, maintenance or breaking

@jmeridth I ended up down a bit of a rabbit hole with this one. I re-requested your review because I changed more than I advertised.


[Bug]: Not able to use special keys in environment variables

Insomnia Version: Version 6.5.1
Operating System: Ubuntu 18.04

This issue is similar to #945, but in regards of being able to use the special keys in the environment variable definitions.
Details
We're returning JSON-LD data from our APIs, with keys such as @type, @context and @id.
Now I'd like to use the response attribute @id from one request as an environment variable, but I get the following error: Unexpected token @ in JSON at position 412
I'm using the workaround that was suggested in issue 945, but it doesn't seem to apply in the environment configuration.

... Since this problem basically only occurs in the response tag, we could also just add some logic to make the filter parameter use base64 (or some other encoding) always

Since this basically only happens in the response tag, we could also just update that tag specifically to always encode that parameter in base64 or something similar.

... Since this problem basically only occurs in the response tag, we could also just add some logic to make the filter parameter use base64 (or some other encoding) always

This is not ideal, but I wonder if we could workaround this by coming up with a special encoding for complicated tag arguments.
For example, we could prefix complex arguments with a special encoding function like this
{% response 'body', 'req_abc', '__b64:JFsnQGlkJ10=', 'never' %}

This, of course, would break compatibility with stock Nunjucks templating but it would solve the problem.

@gschier: Sorry, I didn't find the existing issue. I tried with the \"$['@id']\" both in the popup window and in the {%%} string format, but didn't get it to work... I'll continue trying to find a solution for that.
Thanks for your responses!


Export data in SQL format file split into files of max size

We have some big tables to migrate from oracle to postgresql.  The export to SQL 'INSERT INTO' format seems the best way to do.  However I ran into JDBC problems of the file being too large.  So I used the split option.  However, seems that the first file end without ';' and the following file starts with a comma.  Running these sql files to upload the data gives errors.  If we need to join these files again, we run into the problem of having too large files.  Better would be to structure every file with a starting insert into and ending with a ;

Fixed in DBeaver 22.0.3

Verified


[Autopilot] approval for rule kube-system/pool-rebalance-44fbba64-4b10-4fa4-974b-b6dcf491ed11 rule: pool-rebalance

This is a request to approve an autopilot action. The request was triggered based on an AutopilotRule pool-rebalance defined in your cluster.
What actions will be taken
Action: rebalance

ExpectedResult: Job summary:
-> Provisioned space balanced         0 B done, 60 GiB pending

Rebalance actions:
Replica add action
Volume:<PHONE_NUMBER>50442370
Pool: 4a8ec973-219b-48da-b0a1-b3f45e843789
Node: 6eec1f0a-2679-41a7-a541-bc5f9dec52d9
Replication set ID: 0
Start: Fri, 28 Aug 2020 19:15:47 UTC
End: -
Work summary:
-> Provisioned space balanced         0 B done, 30 GiB pending
-> Volume replicas balanced           0 done, 1 pending
Replica remove action
Volume:<PHONE_NUMBER>50442370
Pool: e24c4dbe-4f80-48db-8a1d-17ae2e459fcc
Node: 366acf86-96ec-499c-913d-f5455b1860a9
Replication set ID: 0
Start: Fri, 28 Aug 2020 19:15:47 UTC
End: -
Work summary:
-> Provisioned space balanced         0 B done, 30 GiB pending
-> Volume replicas balanced           0 done, 1 pending
Replica add action
Volume:<PHONE_NUMBER>08708188
Pool: 44fbba64-4b10-4fa4-974b-b6dcf491ed11
Node: a53dbf82-faca-40a2-a7bc-3f1c397f1516
Replication set ID: 0
Start: Fri, 28 Aug 2020 19:15:47 UTC
End: -
Work summary:
-> Provisioned space balanced         0 B done, 30 GiB pending
-> Volume replicas balanced           0 done, 1 pending
Replica remove action
Volume:<PHONE_NUMBER>08708188
Pool: e24c4dbe-4f80-48db-8a1d-17ae2e459fcc
Node: 366acf86-96ec-499c-913d-f5455b1860a9
Replication set ID: 0
Start: Fri, 28 Aug 2020 19:15:47 UTC
End: -
Work summary:
-> Provisioned space balanced         0 B done, 30 GiB pending
-> Volume replicas balanced           0 done, 1 pending
What objects will get affected

StoragePool kube-system/4a8ec973-219b-48da-b0a1-b3f45e843789 (4a8ec973-219b-48da-b0a1-b3f45e843789)

Object Owner(s):

portworx cluster: harsh-pks-demo-38

StoragePool kube-system/e24c4dbe-4f80-48db-8a1d-17ae2e459fcc (e24c4dbe-4f80-48db-8a1d-17ae2e459fcc)

Object Owner(s):

portworx cluster: harsh-pks-demo-38

StoragePool kube-system/44fbba64-4b10-4fa4-974b-b6dcf491ed11 (44fbba64-4b10-4fa4-974b-b6dcf491ed11)

Object Owner(s):

portworx cluster: harsh-pks-demo-38

How do I approve
Once you review the above,

To approve, simply approve and merge this PR
To declined, close the PR

Autopilot will be watching for the merged specs in the cluster and will proceed with the action if approved and declined the action if not.

[Autopilot] Closing PR as the approval kube-system/pool-rebalance-44fbba64-4b10-4fa4-974b-b6dcf491ed11 was deleted in the Kubernetes cluster.


Algorithm part

@reshnashrestha , Is it all okay with part 1?? Or do you still need to add some? Can I start the documentation part taking reference from your work?

I think its okay and there might be some missing and we can figure this out in the class today. I believe that task 2 is also almost done so you better start on.

@poojashresthacode @reshnashrestha Yeah task is almost done. I have to add graphs there.

yes. It is done.


Fixes populating of relationship fields.

field.getClass() is the wrong place to check for the Table
annotation. Must look at field.getType()
field must be accessible before we can set the object.

Thanks for the pull request @abscondment! A previous pull request (resulting in https://github.com/satyan/sugar/commit/348e3da5cccb22e0f370f684e05dc3678ae1ab61) that addresses this same issue has already been merged into master, so I'm going to close this one.


Host/port being added to relative URLs in 1.8.0?

I may have found a regression in the update from 1.7.0 to 1.8.0. When using with Capybara, Poltergeist 1.7.0 and 1.8.0 return different values for the call find_link("my link")[:href] when my link is a relative URL (meaning it declares no host/port; it's just a path).
Given a basic CMS type of application, see the following spec (this tests some javascript that causes links external to the application to open in a new tab):
it "makes all external open in a new window", js: true, focus: true do
  @blog_post = FactoryGirl.create(:article, body: <<-EOF)

This is an internal link

This is an internal anchor link

This is an external link

    EOF

  visit article_path(@blog_post)
  expect(find_link("internal link")[:href]).to    eq "/foo" # This line illustrates the problem
  expect(find_link("internal link")[:target]).to  eq("_self")
  expect(find_link("internal anchor link")[:href]).to    eq "/foo#bar"
  expect(find_link("internal anchor link")[:target]).to  eq("_self")
  expect(find_link("external link")[:href]).to    eq "https://example.com/omgbbq"
  expect(find_link("external link")[:target]).to  eq("_blank")
end

On pre-1.8.0 versions of Poltergeist, all expectations pass. On version 1.8.0, the expectations involving the links with relative urls fail with the following:
Failures:

  1) Articles (a.k.a. blog posts) post details makes all external open in a new window
     Failure/Error: expect(find_link("internal link")[:href]).to    eq "/foo"

       expected: "/foo"
            got: "http://<IP_ADDRESS>:59751/foo"

       (compared using ==)
     # ./spec/features/articles_spec.rb:49:in `block (3 levels) in <top (required)>'
     # -e:1:in `'

If I look at the page in Chrome dev tools there is no host/port added to the links... it seems like this is something that's only happening when run on Poltergeist 1.8. I've also verified that this does not happen when running without Poltergeist (though the checks for the proper target fail as you'd expect since the JS isn't being run).

This is due to the change mentioned in the changelog "Node#[] now prefers element properties over attributes when the property exists and is not an object. This is similar to the selenium driver behavior"  which brings #[] in line with Capybaras behavior when using selenium, in that hrefs are returned as fully normalized.  If you want to check the href attribute that is on the link as opposed to the property you should be using the have_link matcher which (IMO) reads better too.
expect(page).to have_link('internal link', href: '/foo')

Ah! Excellent, thank you! Just tried it and this worked.

@rdlugosz FYI -- using the have_link matcher also improves the resilience of the matching since it will keep retrying to find the link with the correct href, whereas the way you had it written would retry until it found a link with the matching text, but then verify the href and fail if it was wrong.  That means if the page is dynamically changing the href on a link (unusual but I've seen it), or is changing from a page with a link with the same text but wrong href to a page with the correct href, the have_link will work whereas your previous method could fail incorrectly.

Thanks!
On Friday, November 20, 2015, Thomas Walpole<EMAIL_ADDRESS>wrote:

@rdlugosz https://github.com/rdlugosz FYI -- using the have_link
matcher also improves the resilience of the matching since it will keep
retrying to find the link with the correct href, whereas the way you had it
written would retry until it found a link with the matching text, but then
verify the href and fail if it was wrong. That means if the page is
dynamically changing the href on a link (unusual but I've seen it), or is
changing from a page with a link with the same text but wrong href to a
page with the correct href, the have_link will work whereas your previous
method could fail incorrectly.
—
Reply to this email directly or view it on GitHub
https://github.com/teampoltergeist/poltergeist/issues/704#issuecomment-158447641
.


0.6.0 breaks tests for enums in decapi

This test: https://github.com/capaj/decapi/blob/rtti-wip/src/domains/enum/enum.spec.ts#L8
runs fine in jest when using 0.5.6, but breaks with this:
 FAIL  src/domains/enum/enum.spec.ts
  ● Enums › renders schema with an enum used in a query

    ReferenceError: StateEnum is not defined

      24 |       )
      25 |     }
    > 26 |     try {
         |                    ^
      27 |       registerEnum(Foo2, 'Foo2')
      28 |     } catch (err) {
      29 |       expect(err).toMatchInlineSnapshot(

      at RΦ (src/domains/enum/enum.spec.ts:26:136)
      at Object.a (src/domains/enum/enum.spec.ts:18:23)
      at Object.t (src/domains/enum/enum.spec.ts:185:53)
      at node_modules/typescript-rtti/src/lib/reflect.ts:1452:73
          at Array.map (<anonymous>)
      at ReflectedMethod.get parameterTypes [as parameterTypes] (node_modules/typescript-rtti/src/lib/reflect.ts:1451:69)
      at compileFieldArgs (src/domains/arg/compiler.ts:112:27)
      at compileFieldConfig (src/domains/field/compiler/fieldCompiler.ts:31:32)
      at src/domains/schema/rootFields.ts:38:30
      at Object.keys.forEach.__RΦ.f.__RΦ.m.n (src/domains/schema/compiler.ts:26:27)

When I update to 0.6.0.
The error goes away when I move the definition of these enums:
    enum IntEnum {
      one,
      two
    }

    enum StateEnum {
      Done = 'DONE',
      In_Progress = 'IN_PROGRESS',
      Finished = 'FINISHED',
      Cancelled = 'CANCELLED'
    }

    enum StateEnumUsingKeys {
      Done = 'DONE',
      InProgress = 'INPROGRESS',
      Finished = 'FINISHED',
      Cancelled = 'CANCELLED'
    }

to the module level.

OK, not unexpected that there would be some resolution issues with the new enum reflection. Similar to classes and interfaces, enum objects must be imported as part of their type reference. I should add the new decapi betas to corpus to catch  these issues as well, right now we're just doing the original version that doesn't use RTTI.

OK the core issue here is fixed, but there's still a failure in rtti-wip:
Summary of all failing tests
FAIL src/domains/enum/enum.spec.ts
  ● Enums › renders schema with an enum used in a query

    @ObjectType FooSchema.echoAsInferred: Could not infer return type and no type is explicitly configured. In case of circular dependencies make sure to explicitly set a type.

      37 |   let gqlType
      38 |   if (type) {
    > 39 |     // console.log(fieldName, '~ isNullable', isNullable)
         |                   ^
      40 |
      41 |     gqlType = resolveTypeOrThrow(
      42 |       { runtimeType: type, isNullable: isNullable ?? inferredType.isNullable },

      at compileFieldConfig (src/domains/field/compiler/fieldCompiler.ts:39:19)
      at src/domains/schema/rootFields.ts:43:16
      at fieldConfigGetter (src/domains/schema/compiler.ts:51:33)
          at Array.forEach (<anonymous>)
      at forEach (src/domains/schema/compiler.ts:49:33)
      at getAllRootFieldsFromRegistry (src/domains/schema/compiler.ts:76:19)
      at Object.<anonymous> (src/domains/enum/enum.spec.ts:141:33)

Test Suites: 1 failed, 27 passed, 28 total
Tests:       1 failed, 4 skipped, 1 todo, 122 passed, 128 total
Snapshots:   61 passed, 61 total
Time:        10.179 s
Ran all test suites.

Going to release a new RTTI for now to get all these fixes out-- unsure if the above is on RTTI or perhaps because you've been skipping the enum tests during dev. Will dig in more later

Actually the minimal spec I can repro this with is:
import { registerEnum } from '../..'
import { SchemaRoot, compileSchema } from '../schema/SchemaRoot.js'
import { Query } from '../schema/rootFields.js'
import { Arg } from '../arg/ArgDecorators.js'

enum IntEnum {
  one,
  two
}

describe('Enums', () => {
  it('renders schema with an enum used in a query', async () => {
    registerEnum(IntEnum, { name: 'IntEnum' })
    @SchemaRoot()
    class FooSchema {
      @Query()
      enumNullable(@Arg() input: IntEnum): IntEnum | null {
        return input
      }
    }
    const schema = compileSchema(FooSchema)
  })
})