feat: Implement option to enable / disable sync of declined events

fmt: make the linter happy and add document starts to yamls
feat: add Accepted field to models.Event
feat(outlook): add ResponseStatus field and map to models.Event.Accepted
feat(google): check for Event Response and map to models.Event.Accepted
feat: add sync_declined_events field to config
feat: add SyncDeclinedEvents field to controller struct
test: modify tests for the newly introduced accepted field and controller property
feat: add function to remove declined events if config parameter is set
docs: add sync_declined_fields parameter to readme.md

I'm wondering whether it would be cleaner to implement the removal of declined events using an extended variant of the transformers. That way the filter/transform steps and the actual synchronization remain cleanly separated.

I'm wondering whether it would be cleaner to implement the removal of declined events using an extended variant of the transformers. That way the filter/transform steps and the actual synchronization remain cleanly separated.

Good idea. Approaching it like this we could also create the base for https://github.com/inovex/CalendarSync/issues/65

I'm wondering whether it would be cleaner to implement the removal of declined events using an extended variant of the transformers. That way the filter/transform steps and the actual synchronization remain cleanly separated.

@MichaelEischer i just pushed some new commits which introduced filters, analogue to the transformers we already have. Let me know what you think!


fix TimeDimExtractionFn.apply() under concurrency

Fixes #3983

Why not migrate to joda time?  Deprecate and add new one using joda time formatter which is thread safe.

@patelh this is only a test patch for verification, not mergeable in druid just yet.

@patelh a new one using Joda would be nice, but this one should still be fixed.
@himanshug I added this to 0.10.0 since it's a bug that seems straightforward and nice to fix.

@himanshug is this ready for merging or do you need to do more testing?

@gian i'm working to get this deployed on the user cluster and confirm that it fixes the issue. it most likely does from the local analysis so far.

@gianm ok, this fixes the problem on real usage.
I updated ExtractionFn doc also to mention Thread safety expectation.
I also tried to write an UT for concurrency, but it never failed even without this fix .. so the UT is unreliable and hence not added in this PR.

thanks @himanshug, this looks good to me 👍


Symmetry for Ratio::new_raw

A request to create a function (for now I'll call it Ratio::into_raw) which acts like this:
fn into_raw(self) -> (T, T) {
	(self.numer, self.denom)
}

This would be useful as a way to circumvent unnecessary cloning while maintaining the "weak invariants" of Ratio (mentioned in this issue). It would also be useful for "manually" implementing more efficient primitive operations on BigRational from outside of num-rational like so:
fn div_by_u32(rational: BigRational, primitive: u32) -> Option<BigRational> {
	(primitive != 0).then(|| {
		let (numer, mut denom) = rational.into_raw();
		denom *= primitive;
		BigRational::new_raw(numer, denom)
	})
}

This could solve issues that #38 tries to solve without making as much of a sweeping change, which hopefully will help it to be accepted more quickly.

Sorry I missed this -- I think into_raw sounds like a fine addition.


NIFI-6380: Introduced the notion of Parameters and Parameter Contexts…

… to the code base.

Added nifi-parameter module
Added Parameter to nifi-api
Added ParameterContext and ParameterLookup
Updated EL to support Parameters
Updated backend so that any property can make use of Parameters
Added web endpoint for Parameter Contexts
Updated Templates to make use of Parameter Contexts
Updated Versioned Flows to make use of Parameter Contexts
Updated Stateless NiFi to support Parameters and take Parameters as part of the configuration, not Variables.

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables X functionality; fixes bug NIFI-YYYY.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

Will review...

That is a huge pr for having an empty jira created about 10 minutes before the pr

I work fast :)

are you on slack?

The implication about the JIRA and PR speed is problematic.
If you look at the JIRA it is a child [1] of a parent [2] which links to a well written and detailed feature proposal laying out the full context [3].
[1] https://issues.apache.org/jira/browse/NIFI-6380
[2] https://issues.apache.org/jira/browse/NIFI-6276
[3] https://cwiki.apache.org/confluence/display/NIFI/Better+Support+for+Parameterizing+Flows

Thanks for pointing in the right direction @joewitt

@markap14 trying to run a full build I seem to consistently get these test failures:
[ERROR] Failures:
[ERROR]   TestStandardParameterContext.testChangingParameterForEnabledControllerService:204 Was able to remove parameter being referenced by Controller Service that is DISABLING
[ERROR]   TestStandardParameterContext.testChangingParameterForRunningProcessor:162 Was able to remove parameter while referencing processor was running
[ERROR]   TestStandardParameterContext.testUpdatesApply:69

Also some checkstyle violations in nifi-expression-language for unused imports.

Can we add a description field to the parameter context?

Does it make sense to add auditing history to parameter contexts?

@scottyaslan adding a description field to the parameter context makes sense to me. Will add that in. I created a new sub-task (NIFI-6384) to capture the auditing information. It's definitely a good call, but I feel like that should probably not hold up the PR.

OK I rebased against master and pushed 2 new commits. The first addresses all of your feedback thus far, I believe, @bbende. The second addresses your comment about parameter context description field @scottyaslan. Thanks!

Will also take a look...

I am a +1 at this point. Thanks for the contribution @markap14 !

How do we know if a parameter can be written based on the permissions of the components that reference them? Does a user have write privileges to modify a parameter referenced by a processor that the user does not have permission to edit???

@mcgilman good catch on the comments/TODO's left in the code. Will push another commit addressing these and with a few additional bug fixes around handling Parameter Contexts referenced by components that the user doesn't have access to

@markap14 Thanks for the update. I've left some follow up comments in my previous feedback. A couple of other items:

Asked earlier but did not see any response... What are your thoughts on automatically setting the parameter context on newly created Process Groups based on the currently bound parameter context in the parent Process Group? Since parameters are not inherited, this could be a convenient feature if users would expect this behavior. There is a downside to consider that changing the bound parameter context would be cumbersome but this downside would exist regardless if this convenience were implemented.
When updating a Process Group to bind a Parameter Context, I am able to even if I do not have access to that Process Group. I think we need to update this and perform this check.
When updating a Process Group to bind a Parameter Context, I am able to even if that Parameter Context has affected components that I do not have access to. I think we need to update this and perform these checks.
When updating a Process Group to unbind a Parameter Context, I am able to even if I do not have access to that Process Group. This check is questionable in my opinion. We do require permissions to a referenced Controller Service when it is being dereferenced. So I could see adding that check here too however with Controller Services they can be affected by the components referencing them. This is not really the case here but I still think it seems reasonable to add.
When updating a Process Group to unbind a Parameter Context, I am able to even if that Parameter Context has affected components that I do not have access to. I think we need to update this and perform these checks.

@mcgilman thanks for the review - again :) I am not opposed to the idea of automatically setting the Parameter Context to the same as the parent's when a Process Group is created. From a User Experience point of view, it's probably a good idea. The only real concern that I have is that in order to do that, we'd have to first receive the request, determine if the user has permissions to the parent group's Parameter Context, and if so, set it on the request before replicating. If any node then determined that the user doesn't have the READ policy for the Parameter Context (of course different nodes could see the permissions differently if they are periodically syncing with an external authority provider), then the result will be that the request is rejected. So the user has all permissions that they should, and the request still gets rejected due to insufficient permissions, because they don't have READ on the parent's Parameter Context. Now, this is certainly a corner case, so if you think we should go ahead and do this anyway I'm happy to make the change. But wanted to just run that scenario by you and get your feedback on that first.
Regarding permissions of Binding & Un-binding: you're right - the current approach is inconsistent with how it works with Controller Services. Have updated code. Will push a new commit. Good catch!

Been testing this the past couple of days and had two comments...

I think there is some inconsistency with the authorization hierarchy for an individual context (currently has parent of parameter-contexts, with parent of controller) vs the parameter-contexts resource (currently no parent).

I tested all of the parameter reference examples from the feature proposal...

When using a property that does not support EL, the results matched the expected results on the wiki.
When using a property that does support EL, there were a few weird results related to escaping.
Using a context with a parameter name param1 having a value of param1-dev:
###{param1} -> ###param1-dev (should be #param1-dev)
####{param1} -> ####{param1}####{param1}  (should be ##{param1})
#####{param1} -> #####param1-dev (should be ##param1-dev)

Thanks @bbende  - pushed a new commit that addresses the above. Added integration tests to verify behavior is consistent with those outlined above, regardless of whether or not property descriptor supports EL.

Re-testing the references looks like two of them are still slightly off when the property supports EL...
##{param1} -> param1-dev (should be #{param1})
####{param1} -> #{param1} (should be ##{param1})

OK I pushed an update to the PR. However, since we are changing the comparison logic, that has to be done in the nifi-registry project, so this is now blocked by NIFIREG-294.

@bbende I see. That appears to be due to the way that UpdateAttribute evaluates the Parameters. Will have a new commit up shortly to address. Thanks!

The parameter references look good with the latest commit, also tested all the standard operations in a secure instance and looks good. I'm a +1.

@markap14 Things are looking really good here. I am seeing one minor issue still.
For Reporting Tasks and Controller Services in the Settings cannot reference parameters. However, when I attempt reference one the validation error recognizes the parameter and states that 'no Parameter Context is bound to this Process Group'.

Thanks @mcgilman I pushed an update to the validation error text.

Thanks @markap14! This has been merged to master.

Thanks @mcgilman for all the effort you put into reviewing this and all the feedback! Definitely excited to have this feature added in!


Open donate page should be allowed to launch from external applications

Accessing donate URL from browser can help avoid granting internet permission on android. This can be beneficial for minimize permissions if App doesn't require connect internet.
I can submit a PR to implement this feature.

The new version should be on its way to pub.dev. I haven't tested anything, so if it breaks, pls open an issue.
And thanks a lot for the contribution, I appreciate it.


fix(ts/analyzer): Update normalize intersection condition about return never

Description:
        let is_str = types.iter().any(|ty| ty.is_str());
        let is_num = types.iter().any(|ty| ty.is_num());
        let is_bool = types.iter().any(|ty| ty.is_bool());
        let is_enum_variant = types.iter().any(|ty| ty.is_enum_variant());

        if u32::from(is_str) + u32::from(is_num) + u32::from(is_bool) >= 2 {
            return never!();
        }

        if u32::from(is_str) + u32::from(is_enum_variant) + u32::from(is_bool) >= 2 {
            return never!();
        }

number & SomeEnum is possible, but string & SomeEnum is impossible

Closes https://github.com/dudykr/stc/issues/174

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

but increase 2 extra_error;
I'll be back after I fix it

I think another PR would be also fine, if you prefer it

I'm happy. Because it's all over now.

Great, thank you!


crypto.createVerify('sha1').verify() failed in version 1.36.1

VSCode Version: 1.36.1
OS Version: Windows 10

Steps to Reproduce:

Run code in previous version of VS Code - verification passed: true.
Run code in current version of VS Code - verification passed: false.

Does this issue occur when all extensions are disabled?: Yes
I tried TestVerifier() on node.js versions 10.11.0 and 10.16.0 - verification passed OK.
I created simply extension to test:
crypto-verify-test.zip

Tested on Ubuntu 18.04.2 LTS - the same issue.

Electron 4.x shifted to BoringSSL from openssl which doesn't support DSA by default, please check https://github.com/electron/electron/issues/16458 for background on this issue. Is it possible for you to use RSA or is there a need for DSA in your project ? Thanks!

We strongly need for DSA in our project because of working with old computers that use OpenVMS.


Master -> Live

Docs Build status updates of commit dc62a4d:
:warning: Validation status: warnings

File
Status
Preview URL
Details

mixed-reality-docs/mixedrealityspatialdatapackager.md
:warning:Warning
View
Details

mixed-reality-docs/community.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mixedrealityspatialdatapackager.md

Line 4: [Warning] Invalid value for author: 'alfred-msft' is not a valid GitHub ID

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Update ForceManager CRM connector (bug fixes + add new actions and triggers)

Also this one can be deleted, if you want to add it to the basket of the other two closed pr, thanks.
@vmanoharas I tried to contact Github by my own but they told me only an admin can proceed, so let me know if you can do it or if there is another person I can ask for. Thanks a lot and apols again for the mess.
Here below Github support message:
Hi Filippo,
Thanks for reaching out!
For privacy and security reasons, only a repository admin can authorize the deletion of a pull request.
If you're able to get in touch with an admin directly, you could forward them the email version of this message and ask them to reply (from an email address associated with their GitHub account) giving us authorization. They could also reach out to us directly in a new ticket they create themselves, if that's easier.
If you're not able to contact an admin of that repository, please take a look at the following article for information about how to submit a content removal request:
Submitting content removal requests
Feel free to reach out if you have any additional questions about this!-
-Kind regards,
Lauren


Global: browser zoom maintaining from screen to screen, messing with visual layout

Not sure if this is possible, but disabling zoom will help avoid potential UX pitfalls. When the keyboard comes up on the screen and the player clicks done, the zoom from the keyboard still maintains its value upon moving to the next screen. This creates confusion for the player since the layout is not intuitive without scrolling.
I know this won't be an issue in the app wrapper,  but curious if there is a way to get around this in browser.

I notice that when this happens, content on top of the background is scrolling, but the background + logo remains in place.

confirmed fixed on iphone


Manage email subscription from user profile

Issues
Allow users to manage their email preferences directly from snapshot UI
Changes
This will be a new modal, containing a form with the email notifications settings.
If user is not subscribed yet, the 'SUBSCRIBE' link from the header dropdown menu will open a modal with the subscription form (implemented via https://github.com/snapshot-labs/snapshot/pull/3754)
If user is already subscribed, the modal will show the management subscription form
Modal will looks like:

Email subscriptions                  [x]
[] Proposal creation (<- checkbox)
[] Proposal closing
[] Weekly report
Select all | Unselect all (<- js event to select all checkboxes)
[UPDATE SUBSCRIPTION] (<- submit button)

On submit, we will ask the user to sign a message to prove he's the wallet owner.
How to test

Log in to your account
Open account dropdown menu in header
Click on 'Subscribe'
In the modal, edit the form
Submit the form
Sign the message
See error/success message

To-Do

[ ] Show the form in relevant places
[ ] Add modal/message when subscription is successful
[ ] Add error message on error

Self-review checklist

[ ] I have performed a full self-review of my changes
[ ] I have tested my changes on a preview deployment
[ ] I have tested my changes on a custom domain
[ ] I have run end-to-end tests yarn cypress:test:e2e, and they have passed

Todo
Since we're now opening 2 different modals with the same link, maybe we should rename this menu 'Email notifications'

Are the settings saved on the user profile or on envelope?

@Todmy, I noticed that the designs for subscription management haven't been included in the project pitch. Could you please provide some initial design or wireframes for us to review and agree upon before we proceed with the coding implementation?

User subscriptions are stored with envelop.
List of different subscriptions options are stored on envelop.
Both data can be retrieved with an api request to envelop.
There will be a rest api to update the subscriptions.

First post has been updated with the new specs

@samuveth what do you think about this?:

Let's start with this, and we can decide how it will look.

Check all should be a link

We should always use "Sentence case" not "Title Case"

maybe also add "Uncheck all"

Yes, these are our checkboxes although the design for them isn't set in stone yet. We could alternative use TuneSwitch component instead of TuneCheckbox

We don't need "Uncheck all" in this case

I have tried to consider all your ideas. What do you think?

@samuveth Why do you think we don't need the check/uncheck all ?

We should consider incorporating a dynamic button, as suggested in your design found here: https://github.com/snapshot-labs/envelop/pull/55#issuecomment-1544511596
This button's functionality would depend on the current state of the items. If more than one item is selected, the button should display "Uncheck All". And if less than two items are selected, the button should change to "Check All". WDYT?

@Todmy can you also add the sub text from the design I linked about?
"Selected the email categories you wish to receive:"
And also the sub text for each item too

Updated

If putting the check all button at this place, it should be a submit button, and the label should reflect that by saying "Subscribe to all".
If it's purpose if just to check the checkboxes, without submitting the form, it should not look like a submit button

I have updated the second button text.
Also, I would like to know how you want it to behave. When half or more than half of selected, then it should allow you to subscribe to all types of email, otherwise it will unsubscribe the user from all types of subscriptions. Does it correct?

That second button is still bothering me. I think we should just remove it altogether.
It's bad UX to have a submit button do different thing, depending on what is checked.
Either we have

Uncheck all | check all (simple link, above the blue submit button)
No second button nor links, just the blue one for update

Reproducing the second button from https://github.com/snapshot-labs/envelop/pull/55#issuecomment-1544511596 is not ideal, as the page is targeted toward user who already wants to unsubscribe, the page was introduced to try to retain them as last resort.
We should not have a button to facilitate unsubscription from snapshot side, because the emails are removed from DB, and they will be required to subscribe and verify email again. (if user can reactivate emails without all the hassle, it will be a different story).

I was thinking something like that

Let's just agree to remove it altogether, all of the site I've tested does not have this button anymore, and it makes sense only on an unsubscribe page, and not manage preferences page.

I think we should remove the "un/subscribe to all" button. we can handle unsubscriptions from the unsubscribe link in the email.

here is an improvement added to the task. We need to add an ability for a client to remove email from DB completely. This is the draft of design:

this checkbox appears only if all switches are turned off.

I can live with this design for now. Probably worth revisiting once we have a designer. As for the text in the last checkbox, maybe we could just make it a one liner by saying "Remove my email from Snapshot's database".
@samuveth might come up with better text though.

updated

Nit, but note that checkbox will only show if all toggles are switched off

@aurelianoB Yes, definitely.


Feature/setfithead multi target

I tried to solve conflict error and fix some error
please check this PR is what you intended.
also, some I failed some test...and I cannot figure out the reason...

I ran some experiments using the multiclass classification for the different heads.
Dataset
Dataset generation script
from setfit import SetFitModel, SetFitTrainer, sample_dataset
from datasets import load_dataset

dataset = load_dataset("SetFit/hate_speech_offensive")

def to_multiclass(sample):
    """
    from
        (0: 'hate-speech', 1: 'offensive-language' or 2: 'neither')
    to
        ([1, 0]: 'hate-speech', [1, 1]: 'offensive-language' or [0, 0]: 'neither')
    """
    label = sample["label"]
    sample["label"] = [1 if label == 0 else 0, 1 if label == 1 else 0]
    return sample

# Simulate the few-shot regime by sampling 8 examples per class
train_dataset = sample_dataset(dataset["train"], label_column="label", num_samples=8).map(to_multiclass)
eval_dataset = dataset["test"].map(to_multiclass)

I want to point out that this isn't a very natural use of a multiclass dataset. That said, I couldn't find an actual multiclass dataset on the Hub.
Training Scripts
Logistic Regression head
trainer = SetFitTrainer(
    model,
    train_dataset=train_dataset,
    eval_dataset=eval_dataset,
)
trainer.train()
metrics = trainer.evaluate()

Differentiable head
trainer = SetFitTrainer(
    model,
    train_dataset=train_dataset,
    eval_dataset=eval_dataset,
)

# Train and evaluate
trainer.freeze() # Freeze the head
trainer.train() # Train only the body

# Unfreeze the head and freeze the body -> head-only training
trainer.unfreeze(keep_body_frozen=True)

trainer.train(
    num_epochs=25, # The number of epochs to train the head or the whole model (body and head)
    batch_size=16,
    body_learning_rate=1e-5, # The body's learning rate
    learning_rate=1e-2, # The head's learning rate
    l2_weight=0.0, # Weight decay on **both** the body and head. If `None`, will use 0.01.
)

And the model for testing was "sentence-transformers/paraphrase-mpnet-base-v2".
Results

Model
Evaluation Accuracy

Multilabel Logistic Regression ("multi-output")
0.5550 (0.0000)

Multilabel Logistic Regression ("one-vs-rest")
0.5550 (0.0000)

Multilabel Logistic Regression ("classifier-chain")
0.5580 (0.0000)

Multilabel Differentiable Head
0.5849 (0.0044)

Notes:

Evaluation accuracy is displayed as mean and standard deviation between 5 executions.
The same seed is used in SetFitTrainer and sample_dataset between all executions, so all executions work on the same training data.
The Logistic Regression performance was identical between different executions (perhaps due to the same seed between executions)
For the differentiable head, there is no difference between the "multi-output" and "one-vs-rest" strategies, and "classifier-chain" is unsupported. So, I ran experiments only with "multi-output".

To me, this is indicative that the multilabel differentiable head performs equivalently to the logistic regression head. With other words, this PR seems to be successful in adding support to SetFitHead for with multi-label classification! 🎉

Tom Aarsen

I always feel thank you for your thoughtful comments and edits. (Also comment of previous Issues)
I will check your editing!
thank you!

@tomaarsen
I also think the readme should be edited.
I think it would be better to submit the edit of the readme in a separate PR.
how do you think?

I confirmed your change! thank you!
Also, I did a similar multi-label example and get a similar result.
So I think you can merge it into the main!
thank you

@tomaarsen I also think the readme should be edited.
I think it would be better to submit the edit of the readme in a separate PR. how do you think?

If the changes that you have planned to the README related to the changes from this PR, then I think the changes should be included in this PR. That way, the code and README get updated at the same time. I'm glad to hear that your experiments work too!

I got it!
I edited the readme to reflect our changes.
Since I am not a native English speaker, my written English might be strange.
So please rewrite the readme if my English is not correct.

I understand your concirm and agree with you.
I fix some code for what you want to do.


tls: Update the preprocessor macro check to check against boringssl version

Suggested by Boring SSL team (David), related comment

/assign @ggreenway

/coverage


Issue #15: Add Names to Full Schedule View

Display names for the appointment on the full schedule view

Closed with pr #158


Error on group chat message after awhile

Unhandled rejection Error: [object Object]
    at Object.ensureErrorObject (.../node_modules/facebook-chat-api/node_modules/bluebird/js/main/util.js:261:20)
    at Promise._rejectCallback (.../node_modules/facebook-chat-api/node_modules/bluebird/js/main/promise.js:469:22)
    at Promise._settlePromiseFromHandler (.../node_modules/facebook-chat-api/node_modules/bluebird/js/main/promise.js:513:17)
    at Promise._settlePromiseAt (.../node_modules/facebook-chat-api/node_modules/bluebird/js/main/promise.js:581:18)
    at Promise._settlePromises (.../node_modules/facebook-chat-api/node_modules/bluebird/js/main/promise.js:697:14)
    at Async._drainQueue (.../node_modules/facebook-chat-api/node_modules/bluebird/js/main/async.js:123:16)
    at Async._drainQueues (.../node_modules/facebook-chat-api/node_modules/bluebird/js/main/async.js:133:10)
    at Immediate.Async.drainQueues [as _onImmediate] (.../node_modules/facebook-chat-api/node_modules/bluebird/js/main/async.js:15:14)
    at processImmediate [as _immediateCallback] (timers.js:383:17)

Hi.
After a period of time, group chat messages (Not sure if it affects all the groups, but it's affecting an important thread) raise the above error on reception.
The script is running on commit 443aaac49aca426a4031affeb14d481cedc6af47 (pretty sure) - I'm not sure if any of the recent commits have fixed this

Can you please update and try again? And include a minimal working example of this issue.  Thanks!

@bsansouci pretty hard to get anything out of this stack trace.  I guess it's possible we're not catching an exception somewhere.  I guess in listen given the context of when it happens.  @bearbear12345 am I correct in understanding that this happens when the api receives a message?

@Schmavery I can't see how any part of my code would create this issue, so too am assuming that the error happens when the message is received.

update: right now still no error, but i'll leave this issue open for ahwile longer

Okay, I assume that the new version(s) have somehow solved this issue
Closing

Thanks for following up


want to add a another language Nl-NL

i have all files buildt for this language how to add it

nl-NL.zip
this are all they file
for nl-NL

@agalwood


support sudo #690

useradd -m -s /bin/bash -b /home/sealos
sealos ALL=(ALL:ALL) NOPASSWD:ALL
sudo sealos run labring/kubernetes:v1.24.0 labring/calico:v3.22.1 --masters <IP_ADDRESS> -p sealos -u sealos

This PR has tooo many conflict, and we may needs rethink how to support sudo.


Update README.md

🛠 Closes #74

👨💻 Add YouTube channel EatTheBlocks

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Add YouTube  channel EatTheBlocks in README.md

📷 Screenshots

Good PR but will prioritise Susmita's as she created the issue and wished to work on it so it is only fair. I see you have created another PR so you will still be a contributor :)

It's okey @ewainy.
Thank you for reviewing my first PR.I will be happy to contribute more.


Update wgpu (and ash, to avoid duplicate deps).

For updating wgpu, these backwards-incompatible changes required fixes:

https://github.com/gfx-rs/wgpu/pull/2698
https://github.com/gfx-rs/wgpu/pull/2786
https://github.com/rust-windowing/winit/pull/2376
https://github.com/gfx-rs/wgpu/pull/3236

The original hope was that with newer wgpu we'll get newer naga which might fix the bug breaking the mouse shader (likely https://github.com/gfx-rs/naga/issues/1977 - at least with SPIR-T) - but alas, no such luck
(however, replacing the for loop with a while loop, and turning off SPIR-T with RUSTGPU_CODEGEN_ARGS=--no-spirt works around naga bugs, and is enough for testing).

I've also took the liberty of tweaking a couple dependency versions and (selectively) running cargo update -p ... to reduce duplicates in Cargo.lock, hence the larger amount of changes than might be expected (and the dependency on https://github.com/EmbarkStudios/ash-molten/pull/71).

One thing I have not figured out yet is why the mouse shader (with the locally applied workaround) doesn't render new frames except on input events only with X11 (Wayland is fine) - there may be a "power saving" setting that has changed default in wgpu/winit?
EDIT: turns out that was us using winit as if we were a GUI application, in "only redraw after events" mode (not sure my workaround here is the best approach, but it works, and enabling VSync makes it acceptable).

This is incredible, the cargo-deny failure is because of something needed for font rendering.
Why would we need to render text? Well, we don't, except... Look at what winit needs to support Wayland:

https://github.com/rust-windowing/winit/issues/1802

(this issue was closed effectively as "wontfix" and does remain a problem)

So according to that, there's this "SCTK" (smithay-client-toolkit) which among other things handles CSDs on Wayland (where CSD is "Client-Side Decoration", i.e. letting an app have a custom titlebar).
But why would winit default to CSD? Surely custom window decorations are optional, right?
Well, GNOME appears to have forced the custom mode on everyone.
Not just that but some of them even posted to KDE venues proposing KDE also do the same (i.e. remove perfectly good WM-side window decorations and force everyone to use custom "CSD" ones).
My only hope is that I can turn this stuff off and maybe cargo-deny will then be happy but I have doubts.

All the stuff that was blocking this PR got merged, so does that mean that wgpu can be updated now?

All the stuff that was blocking this PR got merged, so does that mean that wgpu can be updated now?

@ValorZard To be clear, none of my links above have changed status since I posted them. I was linking already merged PRs, some of them just to describe why certain changes where needed.
The only blocker link AFAICT is there's no new release containing e.g. the crossfont->ab_glyph change (https://github.com/rust-windowing/winit/commit/f9b41fd8194903ac9d9db2728d39af2afa812f11 - note how GitHub doesn't list any tags as containing it).
You can also see it's still under the "Unreleased" section in the CHANGELOG right now:

On Wayland, wayland-csd-adwaita now uses ab_glyph instead of crossfont to render the title for decorations.

We're basically waiting for winit to release 0.28, which I'm not seeing a timeline for.

For now, this update is not that important, at least not for Naga, until these issues are fixed:

https://github.com/gfx-rs/naga/issues/1575
https://github.com/gfx-rs/naga/issues/1977#issuecomment-1318334723

We should just make it possible to use the raw SPIR-V (i.e. bypassing Naga entirely) until Naga improves.

winit 0.28 has since been released (and since then some further patch releases too).
I've further updated winit, wgpu (and a few other miscellaneous crates), but also changed how we handle wgpu's naga dependency, so that we don't have to update wgpu to get newer naga.
That was in part motivated by a desire to maybe try fixing naga bugs ourselves, and being on the the latest from git would make that much easier - but also we could try out e.g. wgpu raytracing support, before it lands.

Hmpf, Android build still fails, now with:
     = note: ld: error: duplicate symbol: ANativeActivity_onCreate
            >>> defined at lib.rs:159 (examples/runners/wgpu/src/lib.rs:159)
            >>>            /home/runner/work/rust-gpu/rust-gpu/target/aarch64-linux-android/debug/deps/example_runner_wgpu.8xz6nj4o9c8umeb.rcgu.o:(ANativeActivity_onCreate)
            >>> defined at glue.rs:736 (src/native_activity/glue.rs:736)
            >>>            android_activity-6c8fa8b2535fb42a.android_activity.84876fb1-cgu.0.rcgu.o:(.text.ANativeActivity_onCreate+0x0) in archive /home/runner/work/rust-gpu/rust-gpu/target/aarch64-linux-android/debug/deps/libandroid_activity-6c8fa8b2535fb42a.rlib

It's possible that me adding this feature-enabling dependency (to fix previous CI errors):
android-activity = { version = "0.4.1", features = ["native-activity"] }

is conflicting with... ndk-glue, maybe?
It's conflicting between android-activity's native_activity::glue and our:
#[cfg_attr(target_os = "android", ndk_glue::main(backtrace = "on"))]
pub fn main

So it's probably likely that the way Android "Native Activity" apps are supposed to be built has changed a lot.

@eddyb correct, ndk-glue has been deprecated and winit has a migration guide telling you exactly what to change to switch over to android-activity: https://github.com/rust-windowing/winit#converting-from-ndk-glue-to-android-activity

Got Android building (and WASM for that matter, but it doesn't work, I get a lot of errors I haven't looked into).
This is what I can get out of cargo apk run -p example-runner-wgpu --lib --target x86_64-linux-android, after starting the Android emulator with -no-snapshot -feature Vulkan,GLDirectMem:

I'm not sure what's wrong with the texture format, but the na-winit-wgpu example has the same problem.

Opened a separate PR with the the addition I was using to test the WASM path:

#1016

Which will have to wait until the massive problem with wgpu::backend::web is fixed:

https://github.com/gfx-rs/wgpu/issues/3430

So this PR is truly unblocked, just needs a review now!


Minor improvements

Fixes spelling errors, changes some values that were a bit odd. Hope it helps.

Awesome, thank you for these! Was definitely in a hurry making this :D

No problem. Cool project! :sparkles:


DO NOT MERGE - TESTING GINKGO FOR ISSUE #3114

Signed-off-by: Chris Evich<EMAIL_ADDRESS>

/hold

Note:

The A flavors: Add -debug
The B flavors: Remove -nodes 3

okay, so just running rootless + this notify_socket test is all green after Matt's patch.


[Move] Mint tiers based on time of AOS approval check

Mint flow is based on a preapproval by AOS (which collects and validates proposal for mint) and then at any point in the future, a fiat transfer triggers the actual mint event.
Previously, if we used the current time (of mint flow, triggered by fiat transfer) then AOS would have a hard time calculating how many approvals are needed. This change enforces chain to base check off of AOS' preapproval collection and verificaition.
Add some more tiered mint tests to ensure windowing checks work, and reset properly based on new time model.

Why are we using approval timestmap and not block timestmap?

@andll the timestamp here corresponds to the timestamp used by the client (in our case AOS) at the moment it determines the policy to be used for collecting the signatures. We can call this timestamp different things but the most important thing is that it'll be passed by the client as part of the transaction. Otherwise AOS and Libra would consider different time windows for tier calculation.

See PR description ^ - AOS needs to know which tier to mint in (and therefore how many signatures to collect). If we use blocktimestamp, AOS will run out of sync with chain and txns may fail often because of incorrect tier

Do we have any doc/spec that describes this tiered mint time usage?
E.g.

This is the goal
This is what client/aos/hsm/chain checks
This is why goal is achieved

I don't believe so but I can add it to https://fburl.com/ecdze5ur

One thing with the pre-approval timestamp: don't we also want to check that the provided timestamp is less than the current timestamp on-chain? This way mint tiers can't be artificially "elongated" by saying the pre-approval is in the future.

I think it would be good to have some description about how those timestmaps allow to achieve the goal - it is not obvious to me for example

@tzakian great catch. Yes, we should absolutely enforce that the given timestamp is smaller than the current time!

:umbrella: The latest upstream changes (presumably da6ce5e6f118bd89ceefacc7b76c35b6dce0f071) made this pull request unmergeable. Please resolve the merge conflicts.

:umbrella: The latest upstream changes (presumably 233e99713b70489e53a26ecbdaa08d883f7bd2dc) made this pull request unmergeable. Please resolve the merge conflicts.


404 Not Found when using .get_instances()

place.get_instances() Returns a 404 error for https://www.roblox.com/games/getgameinstancesjson?placeId=2534724415&startIndex=0
I was told to create a bug report by jmk

I'll work on a pr to fix this.

added in #101


docker / arifmyself.github.io

Problem description

Problem location

I saw a problem on the following URL:

I couldn't find the information I wanted. I expected to find it near the following URL:

Other:

Project version(s) affected

Suggestions for a fix

@arifmyself

Problem description
Problem location

I saw a problem on the following URL:
I couldn't find the information I wanted. I expected to find it near the following URL:
Other:

Project version(s) affected
Suggestions for a fix

#10499


remove unnecessary characters

removing the extra character which might have got added mistakenly

@amitmaskery good catch, thanks!


[SPARK-21070][PYSPARK] Upgrade cloudpickle

What changes were proposed in this pull request?
This brings in fixes and upgrades from the cloudpickle module. Notable fixes:

Import submodules accessed by pickled functions (https://github.com/cloudpipe/cloudpickle/pull/80)
Support recursive functions inside closures (https://github.com/cloudpipe/cloudpickle/pull/89, https://github.com/cloudpipe/cloudpickle/pull/90)
Fix ResourceWarnings and DeprecationWarnings (https://github.com/cloudpipe/cloudpickle/pull/88)
Assume modules with file attribute are not dynamic (https://github.com/cloudpipe/cloudpickle/pull/85)
Make cloudpickle Python 3.6 compatible (https://github.com/cloudpipe/cloudpickle/pull/72)
Allow pickling of builtin methods (https://github.com/cloudpipe/cloudpickle/pull/57)
Add ability to pickle dynamically created modules (https://github.com/cloudpipe/cloudpickle/pull/52)
Support method descriptor (https://github.com/cloudpipe/cloudpickle/pull/46)
No more pickling of closed files, was broken on Python 3 (https://github.com/cloudpipe/cloudpickle/pull/32)

How was this patch tested?
The test suite for cloudpickle tests the internal implementation. There are integration tests here in PySpark that use the CloudPickleSerializer.

Can one of the admins verify this patch?

This fails one test, looking into it now.

@rgbkrk, Do you maybe know if there critical issues that might block the Spark's release, and if it is easy to move to taking an explicit (pinned) dependency on cloudpickle (rather than keeping Spark's local copy of cloudpickle here)?
I remember @holdenk raised a similar issue before.

@HyukjinKwon thanks for bringing that up :) We had a PR to consider using py4j as a dependency rather than a copied zip file, @rxin was against the idea. For now I think simply upgrading cloudpickle as is makes sense, and we can revisit the dependency management  if the support burden of this approach becomes difficult (or as we start taking on additional Python libraries).

Yea, my only worry is, I think we already have some customized codes in Spark's copy and wonder if it is difficult to resolve the conflicts here (for me, IIRC, it took me a while to check out each conflict before). I would go +1 if it is easy for those changes. I will take a look at my best to help review.
cc @davies too.

I am not sure if this affects pyspark but any function object serialized with 0.2.2 or earlier cannot be deserialized with 0.3.0 or greater. I haven't investigated making this compatible because I am not sure if it is needed but I wanted to make sure you are aware.

Thanks for that point @llllllllll , since cloudpickle isn't used for any data which is persisted to be used between different versions of Spark we don't need the format to be backwards compatible.

Jenkins, ok to test. Jenkins add to whitelist.

Test build #78102 has started for PR 18282 at commit b84222b.

Test build #78102 has finished for PR 18282 at commit b84222b.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class _empty_cell_value(object):

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78102/
Test FAILed.

Note: I don't think I'll have time to finish this PR for a few weeks so this is freely available for someone else to take on.

@rgbkrk Shall we close this and reopen when it's ready?

Works for me, sorry I don't have cycles at the moment.


[terraform] Generate keys for full node networks

Create val and fn subdirectories for validator and full node
networks respectively. Generate keys for full node network (not actually
used yet). Support additional network keypairs in docker image. Remove
60 validator set which isn't used AFAIK.
Test Plan: Built validator docker image and ran locally. Applied changes
to mgorven workspace.

:umbrella: The latest upstream changes (presumably f36b4a9d5ac1aa613882b84ef24e3c5a6890b94b) made this pull request unmergeable. Please resolve the merge conflicts.

:umbrella: The latest upstream changes (presumably a6a1b86aeace19974d40cf8137d9e2fc18ff29eb) made this pull request unmergeable. Please resolve the merge conflicts.

:umbrella: The latest upstream changes (presumably 5d9ed1a868390cd9ce5959a05b753370de825577) made this pull request unmergeable. Please resolve the merge conflicts.

@bors-libra: delegate+

:v: @mgorven can now approve this pull request

@bors-libra r=phoenix-antigravity

:pushpin: Commit ffc532a has been approved by phoenix-antigravity

:hourglass: Testing commit ffc532ad1b6afe7cf99ef4743c06585fa0c6c796 with merge 99146a8084d640a4b970e24465ae19460388bc23...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: phoenix-antigravity
Pushing 99146a8084d640a4b970e24465ae19460388bc23 to master...


Add new header poster tool

Hey! I found this very useful,
It can be helpful to others also.
https://leviarista.github.io/github-profile-header-generator/

Hi
Can you create a PR and add the GitHub link - https://github.com/leviarista/github-profile-header-generator
Add this tool under the Miscellaneous section.


Using Alpaca prompt format crashes the app

it's happening with every model I have(shearedllama2.7b, stablelm3b), I'm running the latest app from actions

yeah im doing alot of work on core.cpp at the moment its likely unstable for the time being.
this build seemed to be more stable on my machine though so maybe give it a try
https://github.com/Mobile-Artificial-Intelligence/maid/actions/runs/7519009453

yeah im doing alot of work on core.cpp at the moment its likely unstable for the time being.
this build seemed to be more stable on my machine though so maybe give it a try
https://github.com/Mobile-Artificial-Intelligence/maid/actions/runs/7519009453

now it seems that with chatml prompt formating is crashing(I'm on Android btw) running stablelm3b based models, with sheared llama3b it generates a little bit and crashes on alpaca prompt format, on chatml it runs a little bit more but at the end of <|im_start|>user it crashes.

weird, it works fine on linux

I'm able to get it to prompt with calypso 3B (Alpaca) on my phone but it seems to crash after the second prompt.

minima-3b-layla-v2.q3_k_m.gguf runs weirdly doesn't stop talking but it hasn't crashed.

I noticed something similar on desktop with xwin-mlewd-7b, its almost like the format strings arnt being added. Another issue I noticed was sometimes the response would continue the users message.
So I'll definitely have to look into the format logic

minima-3b-layla-v2.q3_k_m.gguf runs weirdly doesn't stop talking but it hasn't crashed. On llama.cpp is working normal.

with chatml doesn't crash too but same strange output, and with raw prompt format it kinda leaks the system prompt.

I think ill move the logic that excludes the user input and system prompt to dart. For some reason I think that's a source of issues and moving it to dart will make it easier to debug

Haha yeah the only reason its stable now is because i reverted everything back to 1.1.8 and started again lol.
And yeah i can add that pretty easily but all the chat controls are already pretty cluttered so i will probably change them at some point.


Update sourceversion.py

Phases
MP
MM
MB
MR
JM
Total

ETA
0
0
0
0
0
0

Developing
0
0
0
0
0
0

Review
0
0
0
0
0
0

Total
-
-
-
-
-
0

ETA est.

0

ETA cust.
-
-
-
-
-
0

Problem description
Reported issues
Not-reported issues
Analysis
(Write here, if there is needed describe some specific problem. Erase it, when it is not needed.)
Problems
(Write here, if some unexpected problems occur during solving issues. Erase it, when it is not needed.)

That is true, it is not good like this. Would it be better to go without the timezone? Then we miss some information. Or should we just do it with timezone and without offset? That could be always correct, only not appropriate to OUR timezone.

https://docs.python.org/3/library/zoneinfo.html#module-zoneinfo or we can do this and make a condition for python version 3.9+


monitor: 0.13.0 -> 0.14.0

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

monitor: 0.13.0 → 0.14.0-ci2

[ ] Merge pull request #289 from stsdc/dev
[ ] fix dependencies in spec file for Fedora
[ ] fix  libX11-devel dep for Fedora
[ ] Merge branch 'master' into dev
[ ] Add gpg-agent dep
[ ] uncapitalize labels
[ ] fix changelog datetime entry
[ ] improve command sanitazation: support python commands
[ ] restores checks for  L2 and L3 cache
[ ] shows bash icon
[ ] add 16x16 and 48x48 bash icons
[ ] make bash icon more consistent with elementary style
[ ] make bash icon more consistent with elementary style
[ ] improve wording for disabling smooth lines option #298
[ ] Merge branch 'dev' of github.com:stsdc/monitor into dev
[ ] adds margin for the preventive action bar; fixes #304
[ ] hide search bar when avtive view is not a ProcessView
[ ] render charts for more than 36 cores
[ ] little refactoring
[ ] fixes #317: Sort list of opened files for easier reading
[ ] fix linting
[ ] update open files by process; cleanup
[ ] bump version and add changelogs Tagged: 0.14.0
[ ] Update release-launchpad.yml Tagged: 0.14.0-ci0
[ ] add missing deps Tagged: 0.14.0-ci1
[ ] try to use stable elementary docker image Tagged: 0.14.0-ci2

@ofborg build monitor


Unidentified team members

Hello @PSO-Dmitry @Raja-Mohanty @rajeshdesh @sonalijadhav96 @sonalk0209 @vimleshsgt ,
The six of you are using github enterprises licenses for Seagate but we are unable to map your github IDs to your seagate email addresses.  Please either reply here with your email addresses or email them directly to me.  Thanks!
FYI @mukul-seagate11 and @Saumya-Sunder with whom I'm working to properly ensure license consumption.

Hi @johnbent , @mukul-seagate11 , @Saumya-Sunder ,
My email ID registered with @rajeshdesh is<EMAIL_ADDRESS>What do I need to make the corrections?

You're good now.  Thanks!

From: rajeshdesh<EMAIL_ADDRESS>Sent: Friday, February 19, 2021 8:16 PM
To: Seagate/cortx<EMAIL_ADDRESS>Cc: John Bent<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Seagate/cortx] Unidentified team members (#785)
Hi @johnbenthttps://github.com/johnbent , @mukul-seagate11https://github.com/mukul-seagate11 , @Saumya-Sunderhttps://github.com/Saumya-Sunder ,
My email ID registered with @rajeshdeshhttps://github.com/rajeshdesh is: rajesh.deshmukh<EMAIL_ADDRESS>What do I need to make the corrections?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Seagate/cortx/issues/785#issuecomment-782548163, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAPT2PR7URQLT3GNNBN2CDLS74SPDANCNFSM4X45X2JQ.

Hi @John<EMAIL_ADDRESS>and @Mukul<EMAIL_ADDRESS>My mail id for my github id sonlak0209<EMAIL_ADDRESS>
From: John Bent<EMAIL_ADDRESS>Sent: Saturday, February 20, 2021 9:33 AM
To: Seagate/cortx<EMAIL_ADDRESS>Cc: Sonal Kalbende<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Seagate/cortx] Unidentified team members (#785)
You're good now. Thanks!

From: rajeshdesh<EMAIL_ADDRESS>Sent: Friday, February 19, 2021 8:16 PM
To: Seagate/cortx<EMAIL_ADDRESS>Cc: John Bent<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Seagate/cortx] Unidentified team members (#785)
Hi @johnbenthttps://github.com/johnbent , @mukul-seagate11https://github.com/mukul-seagate11 , @Saumya-Sunderhttps://github.com/Saumya-Sunder ,
My email ID registered with @rajeshdeshhttps://github.com/rajeshdesh is: rajesh.deshmukh<EMAIL_ADDRESS>What do I need to make the corrections?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Seagate/cortx/issues/785#issuecomment-782548163, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAPT2PR7URQLT3GNNBN2CDLS74SPDANCNFSM4X45X2JQ.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Seagate/cortx/issues/785#issuecomment-782554960, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMUUHAQSEKRZA7DEOQZR2UDS74YBZANCNFSM4X45X2JQ.

Replied internally.


xcode debugger doesn't work?

I'm running the SampleCocoaPodsProject and everywhere I'm trying to debug, I can't seem to be able to access local variables in the debugger (if I try to 'po some_local_var'). It gives some 'Couldn't materialize: couldn't get the value of variable --some var name goes here-- : variable not available
Errored out in Execute, couldn't PrepareToExecuteJITExpression' error.
I tried doing a separate project and it's the same issue, everything works in the debugger until i add this library and use it.
In the project settings, I looked at compiler flags, optimizations, stuff like that, to be set correctly (no optimizations etc), but didn't find anything wrong with them
Any ideas on why is this happening?

The Podfile does indeed set the compiler optimization level to -O0, and the sample project did not override that for debug builds. I pushed 249df43 to address your direct issue, if you pull down the latest it should fix the problem for you.
I need to look at if I can drop the optimization level from the Podfile altogether. That was set because we noticed a lot of strange crashes in CLucene that went away when we forced -O0 (rather than -Os).


Ocurrences fix

When multiples words are highlighted the status bar displays a misleading message.
For example... buffer contains
la
la
la
la

boo
boo
boo

When you select "la" and then with Ctrl key "boo" status bar should display:
"4 occurrences of "la", 3 occurrences of "boo" instead of '7 occurrences of "boo" '

This is a good catch, by the way. The current behaviour is obviously wrong. Thanks!

The current behaviour is obviously wrong.

Thanks for kicking me while I'm down...
But anyway, sorry about that, I don't use multiple selections very often so in my plugins I forget to support them.

Well, one of the reasons I called it a good catch is because I didn't notice it was broken either. The wrongness was something that became obvious once someone submitted a pull request to fix it :)

This just an exception, is not wrong. :)
adzenith you may want to try a different approach, I'm not sure right now.
Regards

BoundInCode,
I was reading this conversation again and it's clear that I said something that sounded mean and then gave a fake sort of apology. I just wanted to apologize for real. I'm sorry.

Tito,
I'm on holiday for the next three weeks. Should I just pull this, or would you rather we try a different method?

haha adzenith.  Don't worry about :)  I was just playing around.  I don't really mind.
But you should probably pull this.  Have a nice vacation.

Done and done.


can@exists in section name?

CUP/cup/util/conf.py
Like Baidu ubconf,
can @exists in section name as a array?

The anwser is yes.   @ CAN exist in section name as a array
[example]
 [.@section]
 [.@section]


struct (un)marshal

Hey, tiedot's great.
It would be good if tiedot supported direct struct marshal/unmarshal. There's no reason it shouldn't, as encoding/json supports it, and that's what tiedot's using.
I see that the reason the interface has map[string]interface{} is to add the id field. Is this necessary? Or, could reflection be used? (structs could include the id field).

Seems that these have been introduced in 3.2, is this stable to use or not yet ready?

@geoah This is a trivial feature and I forgot about it during 3.2, sorry! Actually the interface between 3.0 and 3.2 have not changed.
It should be really simple to write, let me see if I can get it done in the next several days.

Hi Houzuo,
I'm interested in using tiedot a little more and have a few questions on this subject. In reference to :

At the moment, two reasons exist for the document to be internally recognized as map[string]interface{}:
GetIn function traverses serialized JSON document structure to find values to be indexed/unindexed
To make use of query results, documents have their unique ID chucked in and then written to disk.

The method Col.ForEachDoc (https://godoc.org/github.com/HouzuoGuo/tiedot/db#Col.ForEachDoc) returns a []byte and in turn basically a json document that can quickly be unmarshaled using json.Unmarshal. I've found that using json to unmarshal is far better than something that does a map[string]interface{} -> struct conversion.
My questions: 1) how far along are you with any refactor to the API? 2) is the design final? 3) if not, and this []byte json document is indeed how the data comes off the wire. may I suggest creating a new data type of []byte that has a method to convert return a map[string]interface{}?
I think an API that allows both map[string]interface{} AND a JSON compatible struct in / out would be amazing.
A pain point I currently have is that for me to read from tiedot in to a struct I have to do something like this:
// convert each row back in to a Session type
	for id := range queryResult {
		doc, err := col.Read(id)
		if err != nil {
			Logger.Fatalln(err)
		}
		doc["Id"] = id

		ns := &Session{}
		err = mapToStruct(doc, ns)
		if err != nil {
			Logger.Fatalln(err)
		}
		s = append(s, *ns)
	}

In drivers such as mgo, there is a mechanism for unmarshaling the Id directly in the the given struct. You'll also notice that s had to be allocated ahead of time. If a type is returned that has the ability to convert its self to both map[string]interface as well as []byte, I can skip that and go right in to unmarshaling using my preferred package.

Thank you very much for the suggestions @kylewolfe and sorry I have not been active with the project development.
For your use case I'd like to propose four new functions:

An Insert function (doc interface{})(id int, err error)
An Update function (id int, doc interface{}) (err error)
A Read function (id int, destination interface{}) (err error)
Another Read function (id int, idAttrName string, destination interface{}) (err error)

I hope they'll cover your use cases. What do you suggest to be their names?

Thanks for the quick reply!
Your proposed methods would use json to (un)marshal?
What would idAttrName be used for?
Is the idea of a single return type that can do multiple things out of the realm of possibility? Or maybe just too much of a breaking change? Ideally an interface such as this would be better, so that Id is handled by (un)marshaling:
type Foo struct {
    Id int
    Foo, Bar string
}

f := &Foo{Foo: "foo", Bar: "bar"}
if err := col.Insert(f); err != nil {
    panic(err)
}
fmt.Println(f.Id) // has new id

f.Foo = "baz"
if err = col.update(f); err != nil {
    panic(err)
}

mgo behaves this way so that I do not have to take an extra step to populate Id, if it exists. What are your thoughts?
I'd be happy to start digging in and trying to make some updates to allow for this. I have a high need for embedded db usage, so it would probably be beneficial for me to poke around and understand a little more about tiedot at a lower level.

Going back to the new return type. If []byte indeed does come off the wire (as I see it in ForEachDoc) and you also need map[string]interface for indexing purposes, etc. Then A type something like this could be used across the whole application:
type Row []byte {}
func (r Row) ToMap() map[string]interface{} // allows you to do what you need for indexing

Then during ForEachDoc, both json unmarshaling and any existing functionality around map[string]interface{} can be used.

All right, I misunderstood your original use case regarding mgo. It will be a little difficult to support mgo style API, but I'll try my best to make the existing APIs more pleasant.
json.Marshal/Unmarshal uses JSON byte array instead of string, which happens to be compatible with the representation of JSON documents in the storage. However the higher level API in Col such as Col.Read() returns map[string]interface{} which is inconvenient.
So starting from Col.Read I propose two more functions (names are not final)
Read2(id int, destination interface{}) reads document at specified ID and deserialise it to destination, structure of your choice.
Read3(id int, idAttrName string, destination interface{}) is similar to above, but it also artificially introduces (or modifies) an ID attribute denoted by the idAttrName, so that deserialised structure will have the document ID as well.
And finally, to make Insert and Update easier to use, they will also take interface{} instead of map[string]interface{} as the document input. These two functions will convert the input into index-capable map[string]interface{} automatically, for maintaining indexes.
So in the end the new APIs behave similar to mgo API in terms of supporting any structure as document and treatment of document ID in the deserialised structure.
How does that sound?

I think I may have a crack at this tonight. Rather than what you describe in Read3, how about utilizing a structs tag feature within reflect?
type Foo struct {
    Id int `tiedot: id`
    Foo, Bar string
}

I'm assuming your looking to keep API comparability for awhile longer (before v4 if at all?)

it will definitely be ideal if tiedot can make use of the tag, although I do not know how. Please feel free to experiment with the feature and I look forward to hear from your findings.

Here's a little show and tell of what I have so far (not ready for a PR): https://github.com/HouzuoGuo/tiedot/compare/master...kylewolfe:api_break
I titled the branch api_break, thinking that I would write up what an ideal final API would look like, regardless of breaking changes, but then I realized you could actually switch to a format in which mgo uses (doc interface{}) and still keep backward comparability.
Insert now supports map[string]interface, the new type of Document, []byte and any pointer to a struct. If a pointer to a struct is given, it will search for a tiedot tag of Id, and update that struct directly, allowing for my earlier example.
Once tested (and other functions converted), this should allow for:
type Foo struct {
    Id int `tiedot: id`
    Foo string
}

f := &Foo{Foo: "bar"}
if _, err := col.Insert(f); err != nil {
    panic(err)
}
// f.Id now has the new id

f.Foo = "baz"
if _, err := col.Update(f.Id,  f); err != nil { // Ideally, the first argument wouldn’t be needed, but oh well
    panic(err)
}

That looks even better than I previously thought! well done!
I added you into collaborator list so feel free to push changes.

Excellent! I'll move my work in to a branch on the official repo and continue to play. Do you have a standard or thought on breaking changes? I realized that some more thought needs to go in to a few other methods (ForEachDoc, for example, I believe would have to receive a breaking change in order to support struct unmarshaling)

Well I think people are quite familiar with the idea that softwares evolve and breaking changes will occur . As long as the actual feature isn't taken away I wouldn't mind changing some function signatures.

Hi.. What is the status of this issue..?

@arafath-mk sorry, little progress has been made regarding this issue, although it should not be a difficult matter.
@kylewolfe hello! do you by any chance have a moment to take a look at this?

Unfortunately, I opted to use a different solution for my project. As a result I did not get around to finishing my work on this issue. My partial work is still available though (https://github.com/HouzuoGuo/tiedot/compare/master...kylewolfe:api_break) if someone wants to pick up the baton.

Hey there - any news on adding a function to directly insert a struct? :)

thanks for your interest in this project @phpfs , this project started as a short programming exercise, i'm very sorry that i didn't have a chance to take it higher :|


Support for switching between the claude 3 models? Perhaps auto switching when opus is out of quota!

I'd really appreciate that feature if it's not too much trouble

I actually have to figure out how to switch model from web interface, since this library relies on it.

I don't even necessarily care about switching, but how can I use claude 3 Sonnet and Haiku? As far as I could tell there is no way.

I found a way, I modified client.py to remove the lines if model_name is not None and model_name not in {"claude-2.0", "claude-2.1"}:             raise ValueError(                 "model_name must be either None or one of 'claude-2.0' or 'claude-2.1' strings"             )
        And initiated the model like that : `claude_client = ClaudeAPIClient(session, timeout=240, model_name="claude-3-sonnet-20240229")` I obtained the model name from the network tab in google chrome

        Do you mind if I add that change? I will have to figure out how cuz I am not a coder and I generally dont use github lol

Of course I will add the lines I removed back in but with the claude 3 models instead of claude 2

I also found a way to include images if you want a look at that

@mhd25112 That's great news!
Seems switching model was as simple as overriding the model_name parameter.
Removing the model name check may be a good idea afterall, i'll add this change for the next PR.

Yeah it's simple, would you like the code for image support? Because right now it supports files but that seems to be handled different from images

@mhd25112 Thing is that it should already support any type of file... I included a mimetype check feature in the api just for that.
How is that different from your code?

@st1vms In my testing text files worked fine, but images did not. Do images work for you without modification?

The model_name patch is already live on dev-0.3.2
Will test the image attachments...

@mhd25112 I finally was able to let file upload work, now it should successfully process images and other file types, changes are already live in dev-0.3.2 come check them out!

PR #22 should be ready for merge.
Please let me know if dev-0.3.2 works for you.

Awesome, will let you know when I have time to shift my code from the customized API I made to this one and if it works well

Also just a suggestion for accessibility, add to the read me which model names are allowed to be used, right now there is kind of no way someone will figure that out on their own without going to the website and inspecting packets. it is ""claude-3-opus-20240229", ""claude-3-sonnet-20240229", or ""claude-3-haiku-20240229"  right now but that needs to be updated periodically I presume.

Also just a suggestion for accessibility, add to the read me which model names are allowed to be used, right now there is kind of no way someone will figure that out on their own without going to the website and inspecting packets. it is "claude-3-opus-20240229", "claude-3-sonnet-20240229", or "claude-3-haiku-20240229" right now but that needs to be updated periodically I presume.

I think it's probably best if I don't check that parameter, as you've noticed it is subject to frequent changes...By default it will allow to use the latest Claude3 model (should be Sonnet). Also I can't seem to find a good reference to gather those strings...
Waiting for confirmations in order to merge dev-0.3.2

The strings are actually identical to their official API! found here:
https://docs.anthropic.com/claude/docs/models-overview#model-comparison
It can also be found by going to the website then opening the network tab
just before you click the send message button, you'll see the request pop
up and the payload will contain the model name used.
On Wed, 3 Apr 2024, 08:57 Stefano Raneri, @.***> wrote:

Also just a suggestion for accessibility, add to the read me which model
names are allowed to be used, right now there is kind of no way someone
will figure that out on their own without going to the website and
inspecting packets. it is "claude-3-opus-20240229",
"claude-3-sonnet-20240229", or "claude-3-haiku-20240229" right now but
that needs to be updated periodically I presume.
I think it's probably best if I don't check that parameter, as you've
noticed it is subject to frequent changes...By default it will allow to use
the latest Claude3 model (should be Sonnet). Also I can't seem to find a
good reference to gather those strings...
Waiting for confirmations in order to merge dev-0.3.2
<#m_4359065512113628_m_5387805196100742192_m_-782735049857138269_22>
—
Reply to this email directly, view it on GitHub
https://github.com/st1vms/unofficial-claude-api/issues/21#issuecomment-2033699400,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHNQ4IYIIP2S6JEVIAURBFTY3OR6FAVCNFSM6AAAAABFJ7N5ZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZTGY4TSNBQGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@mhd25112 I updated the README with that link, it's already in dev-0.3.2


Use local_now by default

In different locations, the macro timestamps does not work very well because of the timezone, and it causes a lot of problems for beginners. So we use the new api local_now by default.

Ecto is meant for the times to be stored in UTC in the database. Then, if you need to convert them, for example to format them in the UI, you do so in the presentation layer (in your views, templates, etc), while keeping the database consistent.


Requisitor changes

something weird happened where I thought I pulled but I didn't. So it says I reverted all the changes in commit 8ee4b9c, but then added them all back in commit e08509b.


Rename Fido2NetLib.cs file to Fido2.cs in order to match with the class name

Rename Fido2NetLib.cs to Fido2.cs in order to match with the class name

👍


Fixed error in UG regrading delete cardbill syntax

Fixed error in UG regrading delete cardbill syntax

Codecov Report

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

@@            Coverage Diff            @@
##             master     #242   +/-   ##
=========================================
  Coverage     29.55%   29.55%
  Complexity      572      572
=========================================
  Files           127      127
  Lines          6002     6002
  Branches        712      712
=========================================
  Hits           1774     1774
  Misses         4109     4109
  Partials        119      119

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 55ae2a8...ae53c79. Read the comment docs.


unable to find nextjs with Onepirate

Hello all,
I cant find any npm that working with nextjs and Onepirate thiming
Can you please provide one simple project?

Please provide more information on what you are looking for. I don't really understand the description.

I am looking for next js project with this template only


Added config.MongoDb. This way we only have to change config.json to …

…specify the mongoDB we would like to connect to.

Nevermind!!
Its already set
https://github.com/ch4ot1c/store-demo/blob/master/generate_merchant_wallet.js#L45


Formatting not working

I have the following layout:
{   "type": "TextView",   "data" : {     "name" : "Chris"   },   "text": "~Hey {{name}}",   "textColor": "#ffffff",   "textSize": "20sp" }
The output comes as ~Hey {{name}} but what was expected was - Hey Chris

I have the following layout:
{   "type": "TextView",   "data" : {     "name" : "Chris"   },   "text": "~Hey {{name}}",   "textColor": "#ffffff",   "textSize": "20sp" }
The output comes as ~Hey {{name}} but what was expected was - Hey Chris

The format is of the form @{<data-path>}. Please read the readme for examples.


Display dry-run generated files contents in verbose mode

From @wardbell on November 20, 2017 17:57
Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [x] feature request

Area
- [x] devkit
- [ ] schematics

Desired functionality

Current DryRun lists the files that will be created/touched but not their contents.
Proposing a verbose variant that would output the files themselves. The developer could scroll through the console log or (more likely) capture the stdout to file.
Maybe this happens with the flag combo --dry-run --verbose
Copied from original issue: angular/devkit#286

From @ssilvert on January 10, 2018 15:34
+1
Usually, you are just working on the output of one file at a time.  So perhaps another option would be to specify a single file.
--verbose would dump all modified files
--verbose=myPath would dump a single file

Closing since there is little to no interest in this issue from the community since it was opened in 2018 and therefore it doesn't warrant to be included as part of our API.
Let's reconsider this in the future if there is a bigger demand for this.


Rogue EIA Thermoelectric Cooling Water Archives?

I was trying to add all of our raw data archives into the Catalyst Cooperative community on Zenodo and noticed that the EIA Thermoelectric Cooling Water archive doesn't seem to be owned by the<EMAIL_ADDRESS>account -- I can't update the metadata to add it to the community. Strangely, the archive also supposedly dates from November 6th, 2022, even though (I thought) @e-belfer only created the new archiver a few weeks ago.
Did this archive somehow get created with a different Zenodo upload/publish token? Do we know who created it? There's no way to change ownership of archives, so maybe we'll have to ask Zenodo to delete this one once we've got an archive series started with the new archiver? Mostly just confused.

Ahh, I think I know what happened. One of our recent applicants was messing around with the old archiver code and probably created this using their own API key. Confusing.

Well, this is unfortunate and confusing, but I doubt we can get Zenodo to delete someone else's archive, so I guess I'll close this. At least it can serve as a reminder about what happened.


[stable/postgresql] Add ability to use foreign secret for postgresPassword

What this PR does:
Introduce the ability to provide and use a foreign Secret as the postgresPassword value, while maintaining backwards compatibility.
This is implemented in such a way that backwards compatbility is maintained:

nil: random string, encoded in secret template for this chart
string: value encoded in secret template for this chart
map: values will be templated based on these values, via _helpers.tpl

Valid examples:
postgresPassword: # nil

postgresPassword: sekrit #string

postgresPassword: # map[string]
  secret: external-secret
  key: some-other-key #optional

Why we need it:
At GitLab, we're using this pattern for our next generation of charts. @coreypobrien previously submitted PR 5013 so that we can observe our decision to never put sensitive information in ENV. This completes the process of removing the secret content from the environment, as well as removing it from the properties of the deployment itself. Secrets not pre-provisioned are then automatically generated as a Job within our charts.
I did not remove this chart's Secret template because custom-metrics.yaml is placed there. I'll admit I don't understand why it is in a Secret instead of the ConfigMap, but as that would be a change unrelated to this proposal, I have not altered it.
Which issue this PR fixes:
Relates to/alternative to https://github.com/kubernetes/charts/pull/3393
Due to the previously mentioned decision regarding ENV, 3393s secretKeyRefs implementation is not acceptable for us.
Special notes for your reviewer:
I don't immediately see a method of providing ci/*-values.yaml for the CI to run tests in multiple modes, as this change requires a pre-existing secret, or secret provided from outside the chart. I manually ran the following, and verified expectations were met in this charts Secret and Deployment template output.

helm template . --set postgresPassword=derp
helm template . --set postgresPassword.secret=external
helm template . --set postgresPassword.secret=external --set postgresPassword.key=other

cc @databus23

Looks fine, but you need to increase the minor version of the Chart in Chart.yaml before we can accept it.

/assign

/ok-to-test

/assign @databus23
As the Chart maintainer, can you take a look at this as well, please?

We need to find out which solution we want.
/hold

Nice to see another great idea how to add more flexibility to the secret referencing!
Personally I find the approach used in the redis chart more intuitive and easier to implement. It makes the values types more clear. So there are 3 ways of how to tackle the same feature request that I'm aware of:

The one from the redis chart: introducing a second values variable which might be used to override the secret-ref used to fetch the password from. This approach is doable with easy defaulting in the helm template

very easy to use by consumers
no need for a special helper

This PR: Using the same values key and differentiating over the values type how to handle the key

more complex, breaks with the value should have only one type or Nil

PR #3393: Using a generic secretKeyRefs

even more complex
does not make sense if it's used by just one chart - therefor it's to complex and to generic
not that easy to solve the requirement to not expose the secret via ENV; except by adding another key which marks it to be mounted or by adding another specific key (either way feels hacky)

So I would opt for 1. 🙂

Somehow missed this PR. I have implemented Option one in #5413.
I will be glad if this gets in, in whichever form 😄 .
On a side note neither PR currently moves the custom metrics out of the secret which I would also like to see land

@WarheadsSE what do you think about #5413? Would that be sufficient for your needs?

@cliedeman Correct. I didn't touch the custom-metrics.yml because it was unrelated to the changes I was making. I agree though, that I don't see any sense of this being in the secret. If there is something in this file that should not be in a ConfigMap, then it shouldn't be kept in such a format in the first place.
I believe that #5413 provides a means to run both a password and external secret in parallel, but I am not sure maintaining both is the best path forward. Admittedly, I am biased to never having as secret's content in a property or ENV setting, but what I have presented here is a path forward allowing migration to a new pattern.
I understand @tonyfahrion 's observations of more complex, breaks with the value should have only one type or Nil, however as a stepping stone, it is a straight forward path.

Hmm, as far as I understand #5413, it still allows setting usePasswordFile: true, which would enforce mounting the password and not exposing it via env

@tonyfahrion Yes, #5413 builds on the previous work that @coreypobrien did on behalf of GitLab for this chart. It is less about the ENV in that PR, than having two separate paths to the secret content.

Closing, as https://github.com/kubernetes/charts/pull/5413 is merged.


Crucibles being strange.

My Minecraft version is 1.12.2 my Ex Nihilo Creatio is version 0.3.1, and my JEI version is <IP_ADDRESS>.
Hello, I seem to be having an issue with the regular clay crucible, they don't show up in JEI, or the Creative search, I have to manually make one and cook it, but that's not the only issue.  When I go to place cobblestone in it, it doesn't do anything, so I try stone, netherrack, obsidian, gravel, none of it works, so I try pumping cobblestone into it via a transfer pipe from Extra Utilities, but all that does is crash the game and break the world, this issue is kind of important, I'm playing on a skyblock world and really need a good source of lava to continue.

Can you gist and send the crash please?
ZcanKal<EMAIL_ADDRESS>schrieb am Do., 20. Sep. 2018, 01:40:

My Minecraft version is 1.12.2 my Ex Nihilo Creatio is version 0.3.1, and
my JEI version is <IP_ADDRESS>.
Hello, I seem to be having an issue with the regular clay crucible, they
don't show up in JEI, or the Creative search, I have to manually make one
and cook it, but that's not the only issue. When I go to place cobblestone
in it, it doesn't do anything, so I try stone, netherrack, obsidian,
gravel, none of it works, so I try pumping cobblestone into it via a
transfer pipe from Extra Utilities, but all that does is crash the game and
break the world, this issue is kind of important, I'm playing on a skyblock
world and really need a good source of lava to continue.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/BloodWorkXGaming/ExNihiloCreatio/issues/117, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHwpZjWgJ-vSMHAW34m7CZPkk1aBUveSks5uctXPgaJpZM4WxJOh
.

Can you gist and send the crash please? ZcanKal<EMAIL_ADDRESS>schrieb am Do., 20. Sep. 2018, 01:40:
…
My Minecraft version is 1.12.2 my Ex Nihilo Creatio is version 0.3.1, and my JEI version is <IP_ADDRESS>. Hello, I seem to be having an issue with the regular clay crucible, they don't show up in JEI, or the Creative search, I have to manually make one and cook it, but that's not the only issue. When I go to place cobblestone in it, it doesn't do anything, so I try stone, netherrack, obsidian, gravel, none of it works, so I try pumping cobblestone into it via a transfer pipe from Extra Utilities, but all that does is crash the game and break the world, this issue is kind of important, I'm playing on a skyblock world and really need a good source of lava to continue. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#117>, or mute the thread https://github.com/notifications/unsubscribe-auth/AHwpZjWgJ-vSMHAW34m7CZPkk1aBUveSks5uctXPgaJpZM4WxJOh .

I honestly can't remember which one of these it was, so I got two here:
crash-2018-09-17_20.29.58-server.txt
crash-2018-09-17_20.31.51-server.txt

This might or might not be a bit embarrassing... ^^
I'll try to get a hotfix out tomorrow ^^
ZcanKal<EMAIL_ADDRESS>schrieb am Do., 20. Sep. 2018, 01:47:

Can you gist and send the crash please? ZcanKal<EMAIL_ADDRESS>schrieb am Do., 20. Sep. 2018, 01:40:
… <#m_2909353377053401899_>
My Minecraft version is 1.12.2 my Ex Nihilo Creatio is version 0.3.1, and
my JEI version is <IP_ADDRESS>. Hello, I seem to be having an issue with the
regular clay crucible, they don't show up in JEI, or the Creative search, I
have to manually make one and cook it, but that's not the only issue. When
I go to place cobblestone in it, it doesn't do anything, so I try stone,
netherrack, obsidian, gravel, none of it works, so I try pumping
cobblestone into it via a transfer pipe from Extra Utilities, but all that
does is crash the game and break the world, this issue is kind of
important, I'm playing on a skyblock world and really need a good source of
lava to continue. — You are receiving this because you are subscribed to
this thread. Reply to this email directly, view it on GitHub <#117
https://github.com/BloodWorkXGaming/ExNihiloCreatio/issues/117>, or
mute the thread
https://github.com/notifications/unsubscribe-auth/AHwpZjWgJ-vSMHAW34m7CZPkk1aBUveSks5uctXPgaJpZM4WxJOh
.
I honestly can't remember which one of these it was, so I got two here:
crash-2018-09-17_20.29.58-server.txt
https://github.com/BloodWorkXGaming/ExNihiloCreatio/files/2399062/crash-2018-09-17_20.29.58-server.txt
crash-2018-09-17_20.31.51-server.txt
https://github.com/BloodWorkXGaming/ExNihiloCreatio/files/2399063/crash-2018-09-17_20.31.51-server.txt
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/BloodWorkXGaming/ExNihiloCreatio/issues/117#issuecomment-422994004,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHwpZh382Vp2WGJkdo1kT_1ElAWFjuLaks5uctePgaJpZM4WxJOh
.

Waaait... The version from your reports are 0.3.0 not 3.1 where this bug is already fixed, please update to the latest version ^^


Add default minSize to TinyVGDrawable

Having tested the most recent version of TinyVG, it occurred to me that TinyVGDrawable should define its own minWidth and minHeight. This should be dictated by the unscaled size of the original TVG as the scale can be arbitrarily changed by the stage. Thank you for reviewing.

Thanks a lot for your help :)


(Hyundai) IONIQ und Tucson offline

Describe the bug
evcc cant connect to my hyundai cars anymore, hence not loading them
Steps to reproduce

open evcc in browser
select car
car is offline
...

Configuration details
confiugration did not change, nor login data for my cars. It was working 2 days before.
Standard template hyundai

Log details
sudo journalctl -u evcc --since "yesterday" | grep ioniq

[main  ] INFO 2023/11/01 10:48:03 evcc 0.121.1
[main  ] INFO 2023/11/01 10:48:03 using config file: /etc/evcc.yaml
[main  ] INFO 2023/11/01 10:48:03 starting ui and api at :7070
[db    ] INFO 2023/11/01 10:48:04 using sqlite database: /home/fox/.evcc/evcc.db
[site  ] WARN 2023/11/01 10:48:09 battery configured but residualPower is missing or <= 0 (add residualPower: 100 to site), see https://docs.evcc.io/en/docs/reference/configuration/site#residualpower
[site  ] INFO 2023/11/01 10:48:09 site config:
[site  ] INFO 2023/11/01 10:48:09   meters:      grid ✓ pv ✓ battery ✓
[site  ] INFO 2023/11/01 10:48:09     grid:      power ✓ energy ✓ currents ✓
[site  ] INFO 2023/11/01 10:48:09     pv 1:      power ✓ energy ✓ currents ✗
[site  ] INFO 2023/11/01 10:48:09     battery 1: power ✓ energy ✓ currents ✗ soc ✓ capacity ✗
[site  ] INFO 2023/11/01 10:48:09   vehicles:
[site  ] INFO 2023/11/01 10:48:09     vehicle 1: range ✓ finish ✓ status ✓ climate ✗ wakeup ✓
[site  ] INFO 2023/11/01 10:48:09     vehicle 2: range ✓ finish ✓ status ✓ climate ✗ wakeup ✓
[lp-1  ] INFO 2023/11/01 10:48:09 loadpoint 1:
[lp-1  ] INFO 2023/11/01 10:48:09   mode:        pv
[lp-1  ] INFO 2023/11/01 10:48:09   charger:     power ✗ energy ✗ currents ✗ phases ✗ wakeup ✗
[lp-1  ] INFO 2023/11/01 10:48:09   meters:      charge ✗
[lp-1  ] DEBUG 2023/11/01 10:48:09 phase timer inactive
[lp-1  ] DEBUG 2023/11/01 10:48:09 pv timer inactive
[lp-1  ] DEBUG 2023/11/01 10:48:09 guard timer inactive
[site  ] DEBUG 2023/11/01 10:48:09 ----
[lp-1  ] DEBUG 2023/11/01 10:48:09 charge power: 0W
[main  ] INFO 2023/11/01 10:48:10 new version available: 0.121.5
[site  ] DEBUG 2023/11/01 10:48:10 pv power: 4410W
[site  ] DEBUG 2023/11/01 10:48:10 battery soc: 100%
[site  ] DEBUG 2023/11/01 10:48:10 battery power: 8W
[site  ] DEBUG 2023/11/01 10:48:10 grid power: -618W
[site  ] DEBUG 2023/11/01 10:48:10 grid currents: [1.1 1.12 1.96]A
[site  ] DEBUG 2023/11/01 10:48:10 site power: -610W
[lp-1  ] DEBUG 2023/11/01 10:48:10 charger status: A
[lp-1  ] INFO 2023/11/01 10:48:10 car disconnected
[lp-1  ] DEBUG 2023/11/01 10:48:10 set charge mode: pv
[lp-1  ] DEBUG 2023/11/01 10:48:10 set min current: 6
[lp-1  ] DEBUG 2023/11/01 10:48:10 set max current: 16
[lp-1  ] DEBUG 2023/11/01 10:48:10 set priority: 0

What type of operating system are you running?
Linux
Version
evcc version 0.121.1

What was the fix @andig ? thx

No fix. Issue closed due to missing information, i.e. not log file that shows the error.


ci: Don't trigger for main pushes & run tests in release

Don't run CI when merged to main (as PR already did the same)
Run everything in Release mode, similar to release

It's good to note that tests always run in Debug anyway, as this is defined in Fake like this: https://github.com/maksimkim/SpanNetty/blob/a4ba4e6fe061b1bb6b40260248a373f3bf97ab45/build.fsx#L259-L261

I believe the primary difference we've noticed is that release pipeline was still on Incrementalist which ran tests differently and those were triggered in our CI as well.
Examples (release vs latest CI from main):

After checking, all failed tests are passing in CI so should be fine with this alignment. (although I can only test on release)


Can get invalid token to the APNS server？

APNS： feedback.sandbox.push.apple.com
feedback.push.apple.com

I'm sorry; I'm not sure what you're asking. Can you please elaborate?
Also, please note that the "feedback service" (the two servers you mentioned) are part of a much older version of the APNs protocol, and Pushy hasn't used them in years.

so，How do I know that the push message arrives at the iPhone?

It sounds like this isn't a bug report or a feature request, but a request for general support. As I asked you before, please send these kinds of requests to the mailing list instead of opening issues.
I'll make an attempt at answering here, but in the future, I will insist upon moving these discussions to the mailing list. APNs, as a protocol, does not provide any mechanism to tell us whether a push notification reached its destination. It will tell us if a notification was accepted by the APNs server, though; if the notification is accepted, the server will try to deliver the notification to its destination, but it makes no guarantees and offers no way of telling us what ultimately happened. That information is provided in the PushNotificationResponse that comes from the Future returned by the ApnsClient#sendNotification method.

Thank you.


[TACHYON-583] Update config docs with available remote block reader options

We will merge commits back from branch-0.7 back to master, so you need only one PR on this.

@apc999 feel free to close the one that didn't get picked, thanks for the heads up!


Experimental auto-scaling support

This change allows to specify auto-scaling information in executor configuration. Server component then figures out which machines could be provisioned in the cluster and tries to schedule for these dormant resources too. The jobs can be placed to these machines only if old enough (this is controlled by AutoscalingNodePlacementDelay server config value). The intention is that only if the jobs can't be placed anywhere else, or are sufficiently behind schedule, the auto-scaling will happen.
TODO:

[ ] Test this in public cloud cluster with autoscaling group.

Closing stale PR


upgraded Maven min version to 3.5.2

Please do not merge before: https://github.com/kiegroup/droolsjbpm-build-bootstrap/pull/825 was merged

why don't we upgrade to the latest available 3.5.4?

@mareknovotny We need to modify and rebuild slave nodes for that [1]. Let's do this just after 7.1 is out.
[1] https://github.com/kiegroup/kie-jenkins-scripts/blob/master/jenkins-slaves/ansible/kie-rhel7.yaml#L6

@pszubiak so even this upgrade to 3.5.2 should be postponed, right?

@mareknovotny we don't have to postpone it. Maven 3.5.2 is already installed on slave nodes. In fact, PR jobs are using Maven 3.5.2 and the rest of the jobs are using 3.3.9. So it's good to unify this.

@mareknovotny is the upgrade for 3.5.2 OK for you? Nothing else had to be done.

@mareknovotny @mbiarnes Wonder if we can merge this now as this PR will clean up maven version usage that we use for our builds in master.
Most of jobs (PR, dowstream and deploy) use Maven 3.5.2 defined in Constants [1]. Rest of jobs is using Maven 3.3.9.
We can bump version of maven to 3.5.4 in other PR. I think we should aslo unify maven version definition across all our jobs, I don't see reason to define it in so many places. What do you think?


Disable cargo / build caching for MIRI runs

Which issue does this PR close?
Next attempt t close https://github.com/apache/arrow-rs/issues/879
Rationale for this change
MIRI is still failing intermittently on Master in a way we can't reproduce locally. Last time in https://github.com/apache/arrow-rs/pull/892 changing the caching seemed to help. This time let's entirely remove the caching to try and confirm (or rule out) it causing the issue
What changes are included in this PR?
Disable all caching for MIRI CI run
Are there any user-facing changes?
No

Codecov Report

Merging #899 (6b235ef) into master (a7547d5) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #899   +/-   ##
=======================================
  Coverage   82.30%   82.30%
=======================================
  Files         168      168
  Lines       48031    48031
=======================================
  Hits        39532    39532
  Misses       8499     8499

Impacted Files
Coverage Δ

parquet_derive/src/parquet_field.rs
65.98% <0.00%> (-0.23%)
:arrow_down:

arrow/src/array/transform/mod.rs
85.33% <0.00%> (+0.13%)
:arrow_up:

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 a7547d5...6b235ef. Read the comment docs.

Well, MIRI has passed but given the experience last time I am not sure if that is relevant. Merging this in on the theory it can't hurt...


docs: replace remix dev with remix watch

I get the error Could not locate @remix-run/serve. Please verify you have it installed to use the dev command. when using remix dev. This should be replaced with remix watch.

It really all depends on if you're using the remix app server or not, so it's wrong for somebody no matter what we use so we'll leave it as it is. Thank you though!


Scipy Maximization

I have removed log_likelihood_ratio_approx. And the scipy maximization is not yet working.

We have to change conversion.py to use likelihood.calculate_snrs_from_summary_data for the case where relative binning is used, right?

We have to change conversion.py to use likelihood.calculate_snrs_from_summary_data for the case where relative binning is used, right?

Yes that's right Kruthi! I didn't have time to look into it in detail, but it there a quickfire way in which we can do this?

2a1dd91 closes #6.


Adding the missing method to the interface

<?php
/**
 * Zend Framework (http://framework.zend.com/)
 *
 * @link      http://github.com/zendframework/zf2 for the canonical source repository
 * @copyright Copyright (c) 2005-2016 Zend Technologies USA Inc. (http://www.zend.com)
 * @license   http://framework.zend.com/license/new-bsd New BSD License
 */

namespace Zend\Db\TableGateway;

interface TableGatewayInterface
{
    public function getTable();
    public function select($where = null);
    public function insert($set);
    public function update($set, $where = null);
    public function delete($where);
    public function getLastInsertValue();
}

Adding a method to an interface is a backwards compatibility break, as any implementations must update their code in order to be compatible. As such, I'm marking this for v3.0.
One thing we can do now is to add a new interface defining that method, and then have it composed into our own implementations; v3 would then wrap that functionality in the original interface and remove the new one (or extend the new one).
Feel free to submit one or more pull requests per my suggestions above.


Update usage docs re. how to install released version(s)

Expected Behavior
Users should easily be able to find docs that explain how to install released versions of build-pipeline:

The nightly release
The latest official release
Previous releases

It should be easy to find these docs from:

The landing page / README in the repo
The quickstart
Usage docs

Actual Behavior
Our docs don't talk about released versions, these closest we currently have is:

Installing with ko for development
Info in the related issue on where the releases live

Additional Info
Suggestion for tackling this:

We can update docs right now to talk about the nightly releases
Create a PR that's ready to merge re. the 0.4 release; we can merge it as part of the 0.4 release (doesn't make sense to add docs about official releases before we have any!)

/assign


New documentation approach

In devonfw we agreed on a new aproach to deal with documentation:

add docs as *.asciidoc files directly in the code repo in a toplevel documentation folder
do documentation changes as PRs. For easy access and low barrier this can be done on github web-ui with pencil to edit single doc file and immediately create a PR online.
have an automated process that syncs the documentation folder into the wiki git repo so that existing links stay intact and features such as sidebar navigation will still work.

With this issue we want to apply this to devon-ide.

PR #104 has been merged. Considered done.